Welkomen

How to install Android on N900 - Auto Install

2010-08-28T22:03:00.003+08:00

NITDroid repository

In Maemo open up the Application Manager, press the title bar and then Application catalogues. Click the New button and fill out the form with this info:

Name: NITDroid
Web Address: http://repo.nitdroid.com
Distribution: nitdroid/
Components:

Now press the save button, and wait for the catalogue to be updated Installation

First of all, to run commands as root in the terminal you need to have the rootsh package installed from the Application manager
Then make sure that the Application Manager is closed, other programs that manage applications might also interfere.

Now open up the X Terminal and enter these codes:
sudo gainroot
apt-get install nitdroid-installer

Wait for the installation of the NITDroid Installer to complete then enter this:
nitdroid

Answer any question you might be asked
Enjoy or Panic, whatever you might do now you are finished :)
Reboot to get access to Android

Kernel Power for Maemo

kernel-power is compatible with Multiboot from version 39 and onwards of kernel-power
To get access to the Enhanced kernel for Maemo please make sure you first have the newest version

Enter this in the X Terminal:
root
apt-get install kernel-power-bootimg

Now either make your own .item file for Multiboot or let multiboot handle it automatically:

dpkg -i /home/user/MyDocs/.nitdroid/multiboot-kernel-power_0.3_armel.deb

Updates

You will be notified of updates in Maemo by the means of automatic checks,
if you suspect that you have not been notified of the latest version you can manually query for updates by selecting Update in the Application Manager in Maemo.

Android 3G setting for Android phone

2010-08-11T09:05:00.000+08:00

Maxis APN
You just need only ONE APN. Fill only the fields specified here. Leave others as they are!
1) Home -> Menu -> Settings -> Wireless & networks -> Mobile networks -> Access Points Name
2) Menu -> New APN
Name = Maxis(3G)
APN = unet
Username = maxis
MMSC = http://172.16.74.100:10021/mmsc
MMS proxy = 202.75.133.49
MMS port = 80
APN type = default,mms

Thats all you have to do..It will automatically know which APN to use for what purposes :) Smart eh?

DiGi APN setting
1) Home -> Menu -> Settings -> Wireless & networks -> Mobile networks -> Access Points Name
2) Menu -> New APN
xxxxxxxxxxxxxxxxxxxxx
DIGI Data - Internet
xxxxxxxxxxxxxxxxxxxxx
APN: diginet
MCC: 502
MNC: 16
APN Type: default

The rest of the field is blank.
xxxxxxxxxxxxxxxxxxxxx

=========
DIGI MMS (WAP 2.0)
=========
APN: digimms
username: mms
password: mms
Proxy: 203.092.128.160
Port: 80
MMSC: http://mms.digi.com.my/servlets/mms
MMS Proxy: 203.092.128.160
MMS Port: 80
MCC: 502
MNC: 16
APN Type: mms
=========

Celcom APN setting
1) Home -> Menu -> Settings -> Wireless & networks -> Mobile networks -> Access Points Name
2) Menu -> New APN
Enter this
Name : Celcom 3G
APN : celcom3g
MMSC: http://mms.celcom.net.my
MMS Proxy : 10.128.1.242
MMS Port : 8080

slop.

2010-08-11T08:46:00.001+08:00

EchoLink for iPhone

2010-08-09T20:16:00.003+08:00

What is EchoLink for iPhone?

EchoLink for iPhone is an edition of the EchoLink software that runs on an iPhone or iPod touch. If you own one of these devices and are a validated EchoLink user, you can access the EchoLink system from nearly anywhere where WiFi networking is available. If you have an iPhone, you can also use it to access EchoLink over the cellular data (3G or EDGE) network. EchoLink for iPhone is available free of charge from Apple's App Store.

Does it have the same features as the EchoLink software for Windows?

The iPhone edition focuses on the basic features of EchoLink, such as managing the Station List, connecting and disconnecting, and transmitting and receiving voice and text. Unlike the Windows edition, you can be connected to only one node at a time, and there is no Sysop mode. The user interface has been re-designed to function smoothly on the smaller screen of the iPhone, and to take advantage of some of its built-in hardware features.

The app is prompting me for a password when I start it up. How do I get a password?

Before using EchoLink for iPhone, you'll need to become a validated EchoLink user first. To do this, you will first need to download, install, and run the EchoLink software for Windows as described on this Web site. Once you are validated for EchoLink, you can run the iPhone edition of the software by entering your regular EchoLink password.

If you have a Mac rather than a PC, you can download and install EchoMac instead to begin the validation process.

Can I use it without a microphone on an iPod touch, just to listen?

Yes, as long as you have installed version 1.1 or above. If no microphone is connected, the Transmit button is disabled.

Does it work with a Bluetooth headset or hands-free device?

On an iPhone, yes. Although the app uses the device's microphone and speaker by default, you can switch the audio source to either a paired Bluetooth device or the internal handset audio after startup, using the icon that appears just to the right of the audio-level meter on the QSO tab.

I see there are some Network Connection options on the Settings tab. How do these work?

EchoLink for iPhone has some special networking features to make it work more smoothly with different kinds of mobile and wireless networks.

Direct: With this setting, the app communicates with the Internet the same way the Windows edition of the software does. Choose this option only if you are using your own WiFi network and your router has been configured to forward UDP ports 5198 and 5199 to your iPhone or iPod touch.
Relay: The Relay setting uses a special set of Relay servers to reach other nodes in the EchoLink system. This mode gives the best performance on a 3G or EDGE network connection because it uses UDP. It's also convenient over WiFi because it requires no router configuration. However, please note the limitations of Relay in the FAQ item below.
Public Proxy: In this mode, the app automatically selects a Public Proxy from the current list of available EchoLink proxies. The system attempts to connect to the proxy that is geographically closest to your current location.
Custom Proxy:This mode lets you enter information to connect to a specific proxy, such as a private proxy you have set up yourself.
Automatic: When Automatic is selected, the EchoLink app will try to choose the most appropriate setting (Direct, Public Proxy, or Relay) by probing the characteristics of the network.
Are there any special limitations of the Relay networking option?

Yes. Although Relay is the default, and will generally give the best performance, the following limitations currently apply:

You can initiate a connection, but you cannot receive one; stations that try to connect to you will receive a "No route available" error message. This means that Phone users that are using the Relay mode cannot connect to each other.
Because there are only a small number of relay severs, you often cannot connect to the same conference or conference server that another node using the Relay mode is already connected to. This means that two iPhone users that are using the Relay mode often cannot join the same conference at the same time.
I'm having trouble connecting to other stations. Any advice?

Check to be sure you have a good, solid network connection. If you are on 3G or EDGE, look for 4 of 5 bars in the signal strength indicator; if you are on WiFi, look for a full-strength signal. Field tests have shown that the cellular data network is not always available even with a strong 3G signal in some situations.
If you are getting the message "No route is available to the station you selected", try connecting to a different station, try connecting later, or try Public Proxy instead of Relay. If you still get a similar message even via Proxy, the station you are trying to reach might be an iPhone user behind a Relay, who will not be reachable.
Do not try connecting to yourself. This won't work in most situations.
Do not use the Direct mode unless you have put in special port-forwarding rules in your router.
If you get a message like "Bye Bye", try again after a few seconds.

On the iPhone, can I use EchoLink when I see the "E" symbol at the top, instead of "3G"?

The "E" symbol means that your cellular data connection is using EDGE technology, rather than 3G. The EchoLink app will work on EDGE, but you may notice dropped packets and slow loading of the Station List. 3G networking gives better results.

Am I running up a bill with my carrier when using EchoLink on iPhone?

If you're connecting over 3G instead of WiFi, you are using your carrier's cellular data network to communicate with the Internet. If you have a flat-rate, "unlimited" data plan with your carrier (such as AT&T in the United States), you are probably not being charged extra, since streaming audio is permitted within the data plan. If you have any doubts, check with your wireless provider to be sure.

Any plans for creating other editions of EchoLink for other smartphones?

Users have asked about the possibility of an EchoLink app for BlackBerry, Symbian, PalmOS, Android, and Windows Mobile. Unfortunately, these platforms are all very different from each other, so developing software for each would involve five separate development efforts, in addition to iPhone. Development has begun on an edition of EchoLink for Android (with no release timetable yet), but there are no projects underway right

2010-07-30T00:06:00.001+08:00

PROTON EXORA VS GRAND LIVINA VS CHERY EASTAR VS NAZA CITRA VS KIA RONDO? PERBANDINGAN MPV DI MALAYSIA

2010-07-29T23:51:00.000+08:00

Many of us will be confused whether to buy the latest affordable Proton Exora 1.6litre CPS RM65k or the fuel economy Grand Livina 1.6l/1.8l from RM80k to RM100k or Chery Eastar with its Mitsubishi engine 2.4l from RM78k to RM88k or another cheapest MPV Naza Citra from RM65k with 2.0l engine or Luxury style Kia Rondo from RM83k with its 2.0l engine.

To be truth and to be fair, every MPV got its own speciality. Many people like to compare and comment this 5 MPV as if they got the best MPV in Malaysia. Just accept the facts and know that all MPV cannot be compared in terms of “what you want” to say other MPV is not good whatsoever.

I read many of car forumers arguing and protecting their MPV and beat other brand’s MPV. For what? It doesn’t make sense.

In Chery forum they said Livina is small, in Livina Forum they said Chery is low quality China made MPV, in Rondo forum they said Exora is underpower car.. Better don’t judge an MPV emotionally. If you want to buy, go test drive it yourself, compare the specification of MPV with what you want and what really suit your needs and buy it.

For example, if you want a big MPV that really can fit 7 people inside, go for Proton Exora or Chery Eastar. Rondo is ok than Livina and Citra 3rd row space. If you prefer performance and fuel efficiency best MPV fuel consumption, 1.6litre & 1.8litre Grand Livina is the solid answer instead of bigger engine capacity Chery Eastar 2.4 litre. If you want more luxury and nice interior finishing, go for Kia Rondo because the interior is very good with black leather and nice dashboard. If you want a cheap MPV but you also need a higher performance engine, get the Naza Citra. If you need a value for money MPV, go for Proton Exora with acceptable 1.6litre CPS engine, bigger space and good looking MPV.

N900-Autoinstaller

2010-07-28T13:43:00.000+08:00

Prerequisites

A MicroSD card, should be >=512MB.
A fully charged(or at least 50%) Nokia N900
The repository extras-devel added and enabled(read more here)
The package rootsh installed
A fast connection(Wifi / 3.5G)
You should uninstall Titan's Power Kernel

Getting to business

NOTE: Commands will be in "quotes", but you should not type the quotes unless it says you should.

1. Open Xterm. Run "root", then "cd /". Now you should run "apt-get install wget".
2. After that, run "wget http://downloads.nitdroid.com/autoinstaller/installer.sh" which will download the latest installer.
3. Now you should run "chmod 777 installer.sh", and at last "./installer.sh " where the FAT32 partition size is your choice.
It will be available in Maemo, but if you use too much the rootfs might not fit.

Now you're required to flash. Go here and download maemo_flasher-3.5_2.5.2.2.exe. Run it, and install the flasher to a path without spaces. A valid name would be "C:\flasher\", a non-valid name would be "C:\Program files\flasher".

You should then download this file to the folder where flasher is. Now, press Win+R and run "cmd". Assuming flasher is in C:\maemo\flasher\, type "cd\" followed by "cd maemo" followed by "cd flasher".

Now, turn off your N900. Slide out the keyboard, hold U and insert the usb cable. It will show a Nokia screen and a usb icon in the top right.
Now, run this command "flasher-3.5 --enable-rd-mode --set-rd-flags=no-lifeguard-reset,no-ext-wd -f -k NITDroid-N900-zImage-latest -R" in the open cmd window.
It should take between 1 and 5 seconds.
Booting

Your N900 will reboot. It will hopefully show you a white menu with three options. You can unplug the USB cable. Now go to "Android (MicroSD, partition 2)" item and press enter. Wait and ignore all errors you may see(unless the N900 stops entirely). After a while you should see a splash screen and you'll probably be presented with the Android lock screen. Press the Ctrl button a couple of times and you should see the desktop.
You're done!

List of Repeater Nationwide

2010-07-19T00:00:00.001+08:00

Note: T = Linked , L = Local
CALLSIGN LOCATION FREQUENCY OWNER
9M4RDA KOTA BHARU, KELANTAN 147.650 -0.6 203.5 MARTS
9M4RAB BACHOK, KELANTAN 147.725 -0.6 233.6 AKRAB
9M4RGT TUMPAT, KELANTAN 146.6125 -0.6 67.0 AKRAB
9M4RPT JELI, KELANTAN 147.750 -0.6 67.0 AKRAB
9M4RNK KUALA KRAI, KELANTAN 147.9875 -0.6 67.0 AKRAB
9M4RTM TANAH MERAH, KELANTAN 146.850 -0.65 167.9 ARECTMJ
9M4RTJ JELI, KELANTAN 146.950 -0.6 167.9 ARECTMJ
9M4RTG B. LAKIT, GUA MUSANG, KELANTAN 147.6125 -0.6 100 ARECTMJ
9M4RPS PASIR PUTEH, KELANTAN 147.825 -0.6 97.4 PUTRA
9M4RDD PASIR MAS, KELANTAN 146.6375 -0.6 186.2 RES’K
GUA MUSANG, KELANTAN 147.800 -0.6 100 PRAGA
KOTA BHARU, KELANTAN 147.675 -0.6 97.4 COBRA
9M4RBP B. PANAU, TANAH MERAH, KELANTAN 146.750 -0.6 85.4 ASTRA (L)
9WV347 B. BAKAR, MACHANG, KELANTAN 145.675 -0.6 103.5 ASTRA (T)
9M4RDF B. GUA SERAI, GUA MUSANG, KEL 146.8125 -0.6 103.5 ASTRA (T)
9M4RBK B. BAKAR, MACHANG, KELANTAN 147.7875 -0.6 123 MARES
9M4RNT B. BINTANG, BESUT, TERENGGANU 147.975 -0.6 203.5 MARTS
9M4RTA B. KUANG, CHUKAI, TERENGGANU 146.750 -0.6 203.5 MARTS
9M4RSC SETIU, TERENGGANU 146.600 -0.95 233.6 SCORE
9M4RBA B. BINTANG, BESUT, TERENGGANU 147.625 -0.6 123 PEMANCAR
9M4RBJ B. JERUNG, MARANG, TERENGGANU 147.800 -0.6 123 PEMANCAR
9M4RBG KUALA BERANG, TERENGGANU 145.000 +0.6 123 PEMANCAR
9M4RBT B. BAUK, DUNGUN, TERENGGANU 147.000 -0.6 123 PEMANCAR
9M4RTK B. KESING, SETIU, TERENGGANU 146.750 -0.6 103.5 ASTRA (T)
9M4RAS B. GELIGA, CHUKAI, TERENGGANU 147.925 -0.6 103.5 ASTRA (T)
9M4RAC B. BUBUS, BESUT, TERENGGANU 146.6875 -0.6 103.5 ASTRA (T)
9M4RCD B. PELINDUNG, KUANTAN, PAHANG 146.100 +0.6 118.8 PERAMAH
9M4RBS B. FRASER, RAUB, PAHANG 147.700 -0.6 118.8 PERAMAH
9M4RBI B. IBAM, MUADZAM, PAHANG 147.800 -0.6 118.8 PERAMAH
9M4RCA CAMERON HIGHLAND, PAHANG 147.000 +0.6 118.8 PERAMAH
KUALA LIPIS, PAHANG 146.000 +0.6 118.8 PERAMAH
9M2RUK G. ULU KALI, PAHANG 147.900 -0.6 203.5 MARTS
9M4RLG G. ULU KALI, PAHANG 147.125 -0.6 203.5 MARTS (T)
9M4RCH CAMERON HIGHLAND, PAHANG 145.450 -0.6 203.5 MARTS (T)
9MV338 B. SULAI, KUANTAN, PAHANG 147.675 -0.6 103.5 ASTRA (T)
9M4RGB G. BERINCHANG, PAHANG 146.625 -0.6 103.5 ASTRA (T)
9M4RGH B. GENTING, PAHANG 145.675 -0.6 103.5 ASTRA (T)
9M4RCF B. FRASER, PAHANG 146.9375 -0.6 103.5 ASTRA (T)
9M4RAA B. TELEMONG, KARAK, PAHANG 147.6375 -0.6 103.5 ASTRA (L)
9M4RES G. ULU KALI, PAHANG 147.775 -0.6 123 MARES
9M4RMP B. SULAI, KUANTAN, PAHANG 147.875 -0.6 123 MARES
9M4RGA B. GENTING, PAHANG 147.2375 -0.6 233.6 AKRAB
9M2RGL G. LEDANG, MUAR, JOHOR 145.525 -0.6 203.5 MARTS
9M2RGP G. PULAI, PONTIAN, JOHOR 145.725 -0.6 203.5 MARTS
9M4RMR MUAR, JOHOR 146.925 -0.6 203.5 MARTS
9M2RBP BATU PAHAT, JOHOR 145.475 -0.6 203.5 MARTS
9M4RLM G. LEDANG, MUAR, JOHOR 145.425 -0.6 203.5 MARTS (T)
9M4RPM G. PULAI, PONTIAN, JOHOR 147.825 -0.6 203.5 MARTS (T)
9M4RAM G. BUSAN, MERSING, JOHOR 146.750 -0.6 103.5 ASTRA (T)
9M4RGL G. LEDANG, MUAR, JOHOR 147.9875 -0.6 103.5 ASTRA (T)
9MX485 G. PULAI, PONTIAN, JOHOR 145.7375 -0.6 85.4 ASTRA (T)
9M4RAL G. LEDANG, MUAR, JOHOR 146.9375 -0.6 103.5 ASTRA (L)
9M4RSG SEGAMAT, JOHOR 147.675 -0.6 85.4 ASTRA (L)
9M4RAP G. PULAI, PONTIAN, JOHOR 147.7375 -0.6 85.4 ASTRA (L)
9M4RAM MERSING, JOHOR 147.8625 -0.6 103.5 ASTRA (L)
9M4RAK KLUANG, JOHOR 147.800 -0.6 103.5 ASTRA (L)
9M4RBN G. BANANG, BATU PAHAT, JOHOR 146.625 -0.6 103.5 ASTRA (L)
9M4RAJ SEGAMAT, JOHOR 146.6875 -0.6 103.5 ASTRA (L)
9M4RJB JOHOR BHARU, JOHOR 145.600 -0.6 203.5 JASRA
9M4RJN BATU PAHAT, JOHOR 145.675 -0.6 203.5 JASRA
9M4RLD G. LEDANG, MUAR, JOHOR 147.700 -0.6 127.3 JASRA
9M2RTB G. TELAPA BURUK, NEGERI SEMBILAN 145.625 -0.6 203.5 MARTS
9M4RNS SEREMBAN, NEGERI SEMBILAN 145.375 -0.6 233.6 NESRAC
9M4RHE BANDAR MELAKA 146.825 -0.6 203.5 MARTS
9M4RKA B. KATIL, MELAKA 146.750 -0.6 88.5 ASTRA (L)
9M4RMA B. BERUANG, MELAKA 147.925 -0.6 85.4 ASTRA (L)
TANJUNG BIDARA, MELAKA 145.990 -1.0 123 MARES
9M2RKK B. LANJAN, KUALA LUMPUR 147.980 -0.6 203.5 MARTS
9M4RKL B. LANJAN, KUALA LUMPUR 439.600 -5.0 203.5 MARTS
9M4RBC SHAH ALAM, SELANGOR 147.8625 -0.6103.5 ASTRA (L)
9M2RBB B. PENARA, PENANG 147.950 -0.6 203.5 MARTS
9M4RPP B. BENDERA, PENANG 439.525 -5.0 203.5 MARTS
9M4RPH B. BENDERA, PENANG 147.825 -0.6 203.5 MARTS (T)
9M4RBB B. BENDERA, PENANG 145.7375 -0.6 103.5 ASTRA (T)
9M2RKV G. KELEDANG, IPOH, PERAK 145.775 -0.6 203.5 MARTS
9M4RPK IPOH, PERAK 147.7125 -0.6 233.6 PARTS
9M4RPI PANDANGAN INDAH, GRIK, PERAK 145.6125 -0.6 103.5 ASTRA (T)
9M4RBK B. KELEDANG, IPOH, PERAK 147.6125 -0.6 103.5 ASTRA (T)
9M4RBL B. LARUT, TAIPING, PERAK 147.7375 -0.6 103.5 ASTRA (T)
9M4RSP B. LENGGONG, PERAK 146.8125 -0.6 103.5 ASTRA (L)
9M2RMK KANGAR, PERLIS 147.980 -0.6 203.5 MARTS
9M4RHP B. NGULANG, PERLIS 147.800 -0.6 103.5 ASTRA (L)
9M2RGJ G. JERAI, KEDAH 146.2625 +0.6 203.5 MARTS
9M4RGJ G. JERAI, KEDAH 147.6125 -0.6 85.4 ASTRA (T)
9M4RBD B. DEDAP, SIK, KEDAH 146.625 -0.6 103.5 ASTRA (T)
9M4RGR G. RAYA, LANGKAWI, KEDAH 145.6125 -0.6 103.5 ASTRA (T)
9M4RKG G. KERIANG, ALOR STAR, KEDAH 146.6875 -0.5 103.5 ASTRA (L)
9M4LGJ G. JERAI, KEDAH 146.9375 -0.6 85.4 ASTRA (L)
9M4RPN SUNGAI PETANI, KEDAH 145.375 -0.6 123 SPARC
9M4RKG ALOR STAR, KEDAH 145.525 -0.6 103.5 KSARC
BALING, KEDAH 147.825 -0.6 85.4 KARIB
9M4RBK G. KINABALU, SABAH 147.750 -0.6 203.5 MARTS
9M4RDV LAHAD DATU, SABAH 144.775 +0.6 203.5 MARTS
9M6RGK G. KINABALU, SABAH 147.900 -0.6
SIMPLEX
KOTA BHARU – V18, BACHOK – V22, TANAH MERAH – V38, TUMPAT – V20, GUA MUSANG – V40, DABONG – V65,
KUALA KRAI – V32 & V48, RANTAU PANJANG – V39, PASIR PUTEH – V30, JELI – V38, PASIR MAS – V56
KUALA TRG – 145.145, V26, V38 & V60, JERTEH – V19 & V50, CHUKAI – V30, KUALA BERANG – V47.
ROMPIN – V20, TEMERLOH/MENTAKAB – V48, BENTONG – V24, KUANTAN/PEKAN – V20, KUALA LIPIS – V24.
MELAKA – V25 & V32.
ALOR STAR – 146.900, V26 & V30, KULIM – 144.125, BALING – V18, KUBANG PASU/KOTA SETAR – V24,
YAN – V26, SIK – V28, SUNGAI PETANI – V30 & V44, KUALA NERANG – V48, CHANGLUN – V24, LANGKAWI – V16.
BUTTERWORTH/KEPALA BATAS – V32, PULAU PINANG – V34.
PARIT BUNTAR/KERIAN – V38, SRI MANJUNG – V32, IPOH/ULU KINTA – V30, LENGGONG – 144.550,
TAIPING – V20, KUALA KANGSAR – V28, GRIK – V24, PARIT – V22.
SUNGAI BESAR – V24, SEMENYIH/BERANANG – V47 & V66, DAMANSARA – V56, GOMBAK – V33,Sarang Burung ( Global ) V69, BANGI – V19
KEPONG – V42, CHERAS/SEPANG – V47, BAGAN LALANG/PUTRAJAYA – V38, KUALA LUMPUR – V17.
SEREMBAN – V22, NILAI – V22 & V66.
KLUANG – V51 & V56, BATU PAHAT – V44, V46 & V56, SEGAMAT/LABIS – V18, V26, V32, KOTA TINGGI – V61
JOHOR BHARU – V16, V18, V33, V47, MUAR – V26. ARAU/KANGAR – V22, 145.215
SANDAKAN – V24, LAHAD DATU – V17, TAWAU – V40
ECHOLINK GATEWAY
9M4GIE-L SHAH ALAM, SELANGOR 144.865
9M4GDD-L SELANGOR 144.725
9M4GKY-L KOTA BHARU, KELANTAN 144.865
9M4GAL-R TUMPAT, KELANTAN 144.8875
9M4GGM-L GUA MUSANG, KELANTAN 144.725
9M4GKK-L KUALA KRAI, KELANTAN 144.755
9M4GSM-L SRI MANJUNG, PERAK 144.865
9M4GOZ-L SUNGAI PETANI, KEDAH 144.825
9M4GOL-L PERLIS 144.7375
9M4GRK-L KUCHING, SARAWAK 144.725
DIGIPEATER
9M4RDG-1 BUKIT GENTING, PAHANG 144.390
AMPANG, KUALA LUMPUR 144.390
SUNGAI BULOH, SELANGOR 144.390
TAMAN DESA, KL 144.390
KEPONG, SELANGOR 144.390
SATELLITES FREQUENCY
ISS VOICE (REGION 2 & 3) DOWNLINK 145.800, UPLINK 144.490
ISS UHF/VHF REPEATER DOWNLINK 145.800, UPLINK 437.800
ISS VHF/UHF REPEATER DOWNLINK 437.800, UPLINK 145.990 WITH PL @ CT TONE 67.0
ISS APRS DIGIPEATER DOWNLINK 145.825, UPLINK 145.825
ISS SSTV DOWNLINK 145.800
AO-51 VHF/UHF REPEATER DOWNLINK 435.300, UPLINK 145.920
VO-52 UHF/VHF REPEATER DOWNLINK 145.900, UPLINK 435.230
SO-50 VHF/UHF REPEATER DOWNLINK 436.795, UPLINK 145.850 WITH PL @ CT TONE 67.0
HO-68 VHF/UHF REPEATER DOWNLINK 435.675, UPLINK 145.825 WITH PL @ CT TONE 67.0
NOAA 15 WEATHER IMAGE DOWNLINK 137.500
NOAA 17 WEATHER IMAGE DOWNLINK 137.620
NOAA 18 WEATHER IMAGE DOWNLINK 137.9125
NOAA 19 WEATHER IMAGE DOWNLINK 137.100
SIMPLEX
V17 145.2125 V35 145.4375 V53 146.4625
V18 145.2250 V36 145.4500 V54 146.4750
V19 145.2375 V37 145.4625 V55 146.4875
V20 145.2500 V38 145.4750 V56 146.5000
V21 145.2625 V39 145.4875 V57 146.5125
V22 145.2750 V40 145.5000 V58 146.5250
V23 145.2875 V41 145.5125 V59 146.5375
V24 145.3000 V42 145.5250 V60 146.5500
V25 145.3125 V43 145.5375 V61 146.5625
V26 145.3250 V44 145.5500 V62 146.5750
V27 145.3375 V45 145.5625 V63 146.5875
V28 145.3500 V46 145.5750 V64 147.4350
V29 145.3625 V47 145.5875 V65 147.4650
V30 145.3750 V48 146.4000 V66 147.4950
V31 145.3875 V49 146.4125 V67 147.5250
V32 145.4000 V50 146.4250 V68 147.5550
V33 145.4125 V51 146.4375 V69 147.5850
V34 145.4250 V52 146.4500

2010-07-03T11:33:00.002+08:00

Antenna model UC-4364-328
The UC-4364-328 is a compact Quadrifilar Helix antenna (8 cm/3" OD x 16 cm/6" H)
designed to operate through Amateur Radio satellites, without requiring an antenna
rotator. The goal of this product is to offer Amateurs with severe space or community
restrictions the ability to receive 70 cm HamSat signals, and communicate through
orbiting repeaters (transponders). Ham satellites operate cross-band: you will
generally need a VHF uplink transmit antenna for 2-way communications. A
companion VHF unit is envisioned in the near future.
This antenna is passive and designed mostly as a receive structure. An active version
of this product is upcoming, with a built-in Low Noise Amplifier (UC-4364-328xxA).
Frequency range: 436-438 MHz
Coverage: Omni-directional, Hemispherical
Polarization: LHCP (-Lx) or RHCP (-Rx) , AR 3 dB
Gain: +3 dBic
Nominal Impedance: 50 ohm (RF)
Input Power: 1 Watt CW
VSWR: 2.0
Connector: -xU: UHF, Male (PL-259)
-xN: Type-N, Male, on 3 m (10 ft) Coaxial Cable
Dimensions: Housing 8 cm (3") OD x 16 cm (6") h
Bottom flange 10 cm (4") OD x 10 mm (0.38") h
Mounting: 4 screws, M4 (#10-32)
Operating Temperatures: -40° to +85°
C C
Weight: 550 g / 1.15 lbs
Finish: PVC housing, standard color is Black

Tutorial Reflashing N900

2010-05-31T10:06:00.000+08:00

sudo dpkg -i maemo_flasher-3.5_2.5.2.2_i386.deb
sudo flasher-3.5 -F RX-51_2009SE_10.2010.12-9_PR_COMBINED_MR0_ARM.bin -f -R

Linux
Once you have downloaded the flasher and the firmware image, follow
these steps:

1.If you downloaded the .deb version of the Flasher, install it with:
sudo dpkg -i
If you are using 64-bit Linux, you'll need to force installation as follows:
sudo dpkg -i --force-architecture
If you downloaded the .tar.gz version instead, you should untar it
manually. The instructions below assume you have untarred it to the
current directory.
2.Turn off your device (make sure you unplug the charger or else the
device will not power down completely. You can plug the device back into
power once it starts flashing).
3.On your PC, run:
sudo flasher-3.5 -F -f -R
If you are using the .tar.gz package, use
sudo ./flasher-3.5 -F -f -R
4.It will say:
Suitable USB device not found, waiting
N900: Whilst holding the ‘u’ key, plug the USB back in. Wait until you
get a dark screen with the NOKIA logo in the middle and a USB logo in
the top right, and let go of the key.
N810, N800 and 770: Take your device, and hold down the Home/Swap button
(looks like a little house on the N800 and 770, and two overlapping
rectangles on the N810), and while holding down the Home/Swap button
press the power button to turn it on.
If it doesn't boot and start flashing, make sure the USB cable is
plugged in.
5.It should start flashing and then reboot. You can remove the USB cable
when the flasher program exits back to the shell prompt.
from README_Flasher-3.5_beta coming with the flasher dowload tgz:

For Nokia NXXX device with Fremantle image flashing mode can be enabled by
1. Turn on Maemo device USB cable connected to PC but not to Maemo device
2. After successfull startup press and hold key 'u'
3. Attach USB cable on your Maemo device, still holding 'u'
4. After ~3 sec the Maemo device is in flashing mode, you can release 'u'

You will see USB image in the upper right hand corner of the screen if
you did this correctly.

Maemo device will wait for flasher input indefinitely when it is in
flashing mode.

NOTICE: Make sure that device battery is charged before doing any sort
of flashing operation.

While we advise you to wait for the official release, if you are brave
enough to take the risk then go ahead and flash your N900 and risk your
warranty
http://www.rayfile.com/zh-cn/files/39306400-5536-11df-8581-0015c55db73d/
http://www.filedropper.com/rx-512009se10201012-9prcombinedmr0armrar
http://www.megaupload.com/?d=JTHRXCJS
http://thepiratebay.org/torrent/5526521/Maemo_5_PR1.2_Joshv06
http://rapidshare.com/files/382571020/RX-51_2009SE_10.2010.12-9_PR_COMBINED_MR0_ARM.rar
http://www.megaupload.com/?d=JTHRXCJS
http://www.mediafire.com/?gznnfzeylqk

Change Log according to the user who tried it
Smoother scrolling
Long key press gives numbers
FM transmitter still works even though HK models do not have the hardware.
Faster. Though this could be due to the reflash..
No stuttering while recording video
currently skype video chat seems to be still disabled
New application manager is awesome!
Flash version has been updated
USSD codes now work without requiring additional apps

GP300 Repeater

2010-05-30T19:31:00.001+08:00

PORTABLE REPEATER BASE ON PIC 16F84 MICROCONTROLLER AND GP 300 RADIOS

Abstract

The usage of transceiver / two-way radio is very essential especially for security and also emergency handling. It is not unusual that radiomen operate portable radio to support them doing their duties. Although the radio is very assisting, communication between portable radios has limitation since it can only be used for relatively short range. Therefore, the writer described about portable repeater using PIC 16F84 microcontroller and GP 300 radio transceiver in this research. The research covers about hardware and software to construct a portable repeater. It is inferred that, using certain algorithm and assembly programming, the PIC 16F84 microcontroller is able to control two units GP 300 which are connected electronically as a 5-watt portable repeater and enhance the communication range up to 8 km.

Keywords

Radio System, Microcontroller, Portable Repeater

I. INTRODUCTION

Experience is the best teacher. Taking experience from true crisis handling and know-how from some crisis simulations such as Tsunami Handling Simulation located at Sanur Beach and Crisis Handling Simulation located at Tanah Lot Beach, the writers obtained that radio communication problem was occurred during crisis incident as well as simulation event. Radio communication problem between crisis team may reduce their performance to handle the crisis and securing the spot. Limited by 5 Watt transmit power and short antenna are the weak points of portable radio. It can handle communication for less than 2.7 miles (4.34 km) away [1]. Repeater is a communication device that amplifies signal in order to extend the transmission range [2]. It is necessary to equip the crisis team with portable repeater in any emergency circumstance. Using portable repeater is an alternative way to expand radio communication range. The longer communication range, the better performance can the crisis team do. The solved problems in this research are how to construct a portable repeater hardware using PIC 16F84 microcontroller and GP 300 transceiver radios and also to design algorithm and assembly programming for PIC 16F84 to control portable repeater.

II. RESEARCH METHODOLOGY

2.1. Literature Study

2.1.1. Radio System

The primary components in a VHF or UHF radio system fall into three groups: transmitters, receivers, and antennas. In most modern radio tactical sets, the transmitter and receiver are contained in a single unit called a transceiver. The simplest transceiver must generate a modulated signal to the antenna and to receive a signal from an antenna, demodulate it, and feed the information to a headset, computer, or some other human or machine interface [3]. The transceiver provides both transmitting and receiving functions. The transmit function consists of modulation, carrier generation frequency translation, and power amplification, meanwhile the receive function consists of RF signal filtering, amplification, frequency down conversion, and demodulation [3]. Two-way radio police made by Motorola started operation in 1940 and in that same year Motorola delivered the portable radio AM transceiver to the U.S. Army [4]. In 1997, Motorola produced GP 300 radio and now still available due to its rugged construction and excellent performance. There are two types of GP 300 radio, i.e., GP 300 VHF type and GP 300 UHF type. Both types are physically similar but have different electronic circuits. GP 300 radio provided with antenna, 16 channel frequency knob, volume knob, battery pack and option jack for remote speaker microphone (RSM) [5].

Figure 1. GP 300 UHF and VHF Portable Radio

The RSM allows operator to talk and listen without removing the radio from the belt, case or charger. Ideal for high noise level environments. This water resistant compact unit has a coiled cord, PTT switch and back cover clip [5]. When the RSM is attached to the radio, the speaker in the radio is disabled, and receiver audio is connected to the accessory speaker. Similarly, the accessory microphone is connected to the transmitter, and the accessory PTT switch can now control the PTT function in the radio. The schematic diagram of RSM is shown in figure below [5].

Figure 2. RSM Model HMN9030A Circuit

2.1.2. Microcontroller

A microcontroller is an inexpensive single-chip computer. Single-chip computer means that the entire computer system lies within the confines of the integrated circuit chip. The microcontroller on the encapsulated sliver of silicon has features similar to those of our standard personal computer. Primarily, the microcontroller is capable of storing and running a program [6]. The PIC 16F84 microcontroller device has 13 input / output ports. The ports are grouped into PORT A and PORT B. PORT A consists of 8 ports, while PORT B consists of 5 ports. In addition to 13 port pins, the rest of 18 pins of the device are made up of the 5 Volt Power and Ground, the Reset input, and two pins for system clock [7].

Figure 3. The PIC 16F84 Pinouts

2.1.3. Repeater

Repeater is a communication device that amplifies signal in order to extend the transmission distance. Available for both electronic and optical signals, repeaters are used extensively in long distance transmission [2]. Repeater can listen on one frequency and transmit on another at the same time. It can receive and transmit on different frequencies at the same time. Portable and mobile radios use repeaters by transmitting on the repeater input channel and listening to the repeater output channels [2].

Figure 4. Repeater Basic Concept

The visible horizon observed at approximately five feet above a flat surface of earth is less than 2.7 miles (4.34 km) away. This is approximately the maximum radio range from a radio of a standing man to another radio of standing man [1]. It is clear that the elevation of both the transmitting and receiving antennas is crucially important. For example if the receiving antenna were mounted on a 26-foot (7.8 m) tower, the total line-of-sight distance would be increased to 9 miles (14.4 km). VHF and UHF waves are also attenuated with every mile of distance. However, for tactical applications, it is most often the shadowing effects of irregular terrain, buildings, and other objects that limit the effective range and not transmit power [3].

2.2 Hardware and Software Design

According to the literature, the portable repeater is built using 2 unit of GP 300 radio and each radio equipped by Remote Speaker Microphone (RSM). These radios and RSM are connected to an electronic circuit and controlled by PIC 16F84 microcontroller. Next step, the research continued by designing the algorithm and programming the PIC 16F84 microcontroller.

2.3. Data Collection and Assessment Method

The assessment is prepared to identify the ability of portable repeater to receive and retransmit signal from specified distance. The process of signal transmitting and receiving in this assessment are conducted using two units of ICOM V8 portable radio transceiver operated by two radio operators separated at certain distance. The ICOM V8 is selected as a tester due to its signal strength meter feature. The assessment takes place in Denpasar City in order to recognize the transmitting and receiving range by measuring it on map. Besides communication range, it is also test the repeated signal quality, including signal strength and signal readability. Therefore, communication range, signal strength and signal readability data are collected and analyzed to ensure the maximum radio range.

III. RESULT AND DISCUSSION

3.1. Hardware

As mentioned above, a portable repeater must able to retransmit signal from receiver unit to transmitter unit. For that purposes, 2 units of GP 300 equipped with RSM and a repeater electronic circuit are needed.

Figure 5. Portable Repeater Block Diagram

The circuit is controlled by PIC 16F84 microcontroller and provided with additional devices, such as Schmitt Trigger and Driver. The Schmitt Trigger applied here is IC 74LS14. It has six inverter gates and utilized to accept input from two units of RSM Model HMN9030A (RX RD1 and RX RD2) and output the appropriate logic to PA0 and PA1 (Pin 17 and Pin 18 of PIC 16F84 microcontroller). The IC 74LS14 pins connection is shown below.

Figure 6. IC 74LS14 Pins Connection

The UDN 2981 driver is used to activate transmitter unit. Pin 1 and pin 2 of the driver accept input from pin 6 (PB 0) and pin 7 (PB1) of PIC 16F84. Meanwhile output pin 18 and pin 19 are connected to two units of SPST (Single Pole Single Throw) relay. Each relay is provided with switch and connected to PTT switch (PTT A RD and PTT B RD) of RSM model HMN9030A. Ground signal must be also connected to RSM. The connection is exposed below.

Figure 7. IC UDN2981 Driver Connection

Besides electronics circuit, the portable repeater required two units of GP 300 radio (as a transmitter unit and a receiver unit) and two units of RSM model HMN9030A. Each RSM is connected to the GP 300 Option Jack and also to the electronics circuit. Both RSM are modified as picture following. The modified RSM will parallel PTT switch with SPST relay (PTT A RD and PTT B RD). While the SPST relay is on, this condition will force the radio entering transmit mode; otherwise, while the SPST relay is off, the radio keeps on waiting in receive mode. It also sends the audio signal (RX RD) to the Schmitt Trigger. The presence of audio signal will output Schmitt Trigger to high logic; otherwise, the absence of audio signal will output Schmitt Trigger to low logic. The GND RD is a ground signal and must be connected to electronics circuit ground.

Figure 8. RSM Modification

To define the function of both radios, whether as a transmitter or a receiver unit, two switches (SW RD1 and SW RD2) are used. Two debounce circuits are required by both switches and connected to pin PB0 and PB1 of PIC 16F84 microcontroller. The complete connection of portable repeater is shown below.

Figure 9. Portable Repeater Schematic

When SW RD1 switch is on, the circuit enables radio 1 to transmit; otherwise, when SW RD1 is off, the circuit disables radio 1 to transmit. Similar to this matter, when SW RD2 switch is on, the circuit enables radio 2 to transmit; otherwise, when SW RD2 is off, the circuit disables radio 2 to transmit. There are two indicator LEDs available in the circuit; TX RD1 and TX RD2. The led will blink at the same time as the appropriate radio is working in transmit mode.

3.2. Software

The algorithm needed by PIC16F84 microcontroller to control the portable repeater is described as follows:

1.	Set Port A as input.
2.	Set Port B as output.
3.	Blink the indicator LEDs twice
4.	Disable radio 1 and radio 2 to transmit.
5.	Check the audio signal from radio 1 and radio 2. If the audio signal occurs from one of the radio, then check the appropriate switch (SW RD1 or SW RD2). If the switch is on then disable this radio to transmit and enable the other radio to transmit. Activate the appropriate relay (PTT RD1 or PTT RD2) to force the radio entering transmit mode and blink the related indicator LED (TX RD1 or TX RD2). Repeat this step until the end of audio signal.
6.	If the audio signal is not detected anymore then disable the radio to transmit.

Figure 10 below shows detail information about the portable repeater algorithm.

Figure 10. Portable Repeater Algorithm

The appropriate assembly programming is listed as follows:

	LIST	P=PIC16F84
	INCLUDE	"P16F84A.INC"
			; SET PORT A AS INPUT
			; SET PORT B AS OUTPUT
	BSF	STATUS,RP0
	MOVLW	0X0F
	MOVWF	TRISA
	MOVLW	0X00
	MOVWF	TRISB

			;BLINK INDICATOR LEDS TWICE
	BCF	STATUS, RP0
	MOVLW	0X0C
	MOVWF	PORTB
	CALL	DELAY
	CLRF	PORTB
	CALL	DELAY
	MOVLW	0X0C
	MOVWF	PORTB
	CALL	DELAY

			; PTT RD1 DISABLED
			; PTT RD2 DISABLED
	CLRF	PORTB

			; PORTA0 - INPUT RX RD1
			; PORTA1 - INPUT RX RD2
			; PORTA2 - INPUT SWITCH RD1
			; PORTA3 - INPUT SWITCH RD2
			; PORTB0 - OUTPUT PTT RD1
			; PORTB1 - OUTPUT PTT RD2
			; PORTB2 - OUTPUT LED TX RD1
			; PORTB3 - OUTPUT LED TX RD2

START
	BTFSC	PORTA,0	; IS RX RD1 HIGH?
	GOTO	IS_SW_RD1_ON

PTT_RD2_DISABLED
	BCF	PORTB,1	; PTT RD2 DISABLED
	BTFSC	PORTA,1	; IS RX RD2 HIGH?
	GOTO	IS_SW_RD2_ON

PTT_RD1_DISABLED
	BCF	PORTB,0	; PTT RD1 DISABLED
	GOTO	START

IS_SW_RD1_ON
	BTFSS	PORTA,2	; IS SW RD1 ON?
	GOTO	IS_RX_RD2_HIGH
	GOTO	PTT_RD2_DISABLED

IS_RX_RD2_HIGH
	BTFSC	PORTA,1	; IS RX RD2 HIGH?
	GOTO	PTT_RD2_DISABLED
	BCF	PORTB,0	; PTT RD1 DISABLED
	BSF	PORTB,1	; PTT RD2 ENABLED
	BSF	PORTB,3	; BLINK TX RD2 LED
	CALL	DELAY
	BCF	PORTB,3
	CALL	DELAY
	GOTO	START

IS_SW_RD2_ON
	BTFSS	PORTA,3	; IS SW RD2 ON?
	GOTO	IS_RX_RD1_HIGH
	GOTO	PTT_RD1_DISABLED

IS_RX_RD1_HIGH	BTFSC	PORTA,0	; IS RX RD1 HIGH?
	GOTO	PTT_RD1_DISABLED
	BCF	PORTB,1	; PTT RD2 DISABLED
	BSF	PORTB,0	; PTT RD1 ENABLED
	BSF	PORTB,2	; BLINK TX RD1
	CALL	DELAY
	BCF	PORTB,3
	CALL	DELAY
	GOTO	START

DELAY
	MOVLW	D'100'	; THIS IS DELAY SUBPROGRAM
	MOVWF	2F	; TO BLINK INDICATOR LEDs
LOOP1
	MOVLW	D'255'
	MOVWF	2E
LOOP2
	DECFSZ	2E,F
	GOTO	LOOP2
	DECFSZ	2F,F
	GOTO	LOOP1
	RETURN

	END

3.3. Portable Repeater Test

The performance of portable repeater is tested by collecting signal strength and signal readability data from definite range. Two units of ICOM V8 portable radios (Radio A and Radio B) are used to acquire data. Signal strength is measured by signal indicator. It appears when the channel is busy and shows receiving signal strength as below.

Figure 11. ICOM V8 Signal Indicator

Meanwhile signal readability is measured using scale as follows.

1	=	not at all read
2	=	sometime read some words
3	=	can be read slightly
4	=	can be read without trouble
5	=	really can be read easily

The results are listed as Table 1 below.

Table 1. Portable Repeater Performance

Distance (km)		A to B		B to A
A to R	B to R	SS	SR	SS	SR
1	1	strong	5	strong	5
2	2	strong	5	strong	5
3	3	strong	5	strong	5
4	4	fine	4	fine	4
5	5	fine	3	fine	3
6	6	adequate	3	adequate	3
7	7	adequate	2	adequate	2
8	8	adequate	2	adequate	2
9	9	weak	1	weak	1

Table 1 description:

A to R	:	distance (km) from Radio A to Portable Repeater
B to R	:	distance (km) from Radio B to Portable Repeater
A to B	:	Radio A transmitting, Radio B receiving
B to A	:	Radio B transmitting, Radio B receiving
SS	:	Signal Strength
SR	:	Signal Readability

IV. CONCLUSION

As a result of portable repeater test, the research obtains some conclusions:

1.	PIC 16F84 microcontroller and GP 300 radios equipped with RSM are able to operate as a portable repeater.
2.	Using two units of 12-meter-height external antennas, radio communication between portable radio users can extend up to 8 km using this 5-watt portable repeater.

Install OpenWRT on x86 PC

2010-05-30T19:21:00.004+08:00

In order to get more familiar with the lightest and awesome distro that OWRT is, I had to install it on my PC or in VMWare.
And there are not much information for almost beginners like me... So I will write here what I do with 8.09 version.

Note : This HowTo is based on the Slitaz 2.0 distro, the next lightest distro after OWRT : http://www.slitaz.org
"SliTaz is an open source and free operating system providing a fully featured desktop or server in less than 30 Mb."
Great for old PC with 192 MB Ram min and small HDD. Thanks Slitaz (and Erjo how help me) !
Slitaz is also available as a core distro (without Xorg) : only 6 MB and only 128 MB Ram !
See the slitaz-2.0-base.iso version here : http://mirror.slitaz.org/iso/2.0/flavors/

[HowTo] Install OpenWRT on x86 PC

1 - Get the image here : http://downloads.openwrt.org/kamikaze/8.09/x86/

Some informations first : The openwrt-x86-XXX.fs files contain only the rootfs partition whereas the openwrt-x86-XXX.image.kernel files contain the kernel partition.

I download the openwrt-x86-ext2.image file. It produces a standard installation, like any Linux distro. Try this first !
(If you want to see how jffs with mini_fo works like in a router, you can use the openwrt-x86-squashfs.image. I didn't try yet the jffs2 files...)

Copy the image on a USB key.

2 - Copy the image on HDD :

For this, download the LiveCD Linux distro Slitaz : you don't need to install it.

Boot your PC with the Slitaz CD and login as tux (No PWD). The disk where to install OWRT (I'll say it is /dev/hda) will be detected automatically by Slitaz (Note : I don't have tested this with SATA HDD).
Insert USB key, it'll appear in the file manager (in the dir /media/USB2 or something like that, depends on your key)
Open a console and get root via "su -" and the root pwd which is : root.
Copy the image on HDD : "dd if=/media/USB2/openwrt-x86-ext2.image of=/dev/hda bs=1M count=100"
That's all folks !

3 - Boot on HDD and enjoy OWRT
:)

Now, for those who want to make a "LiveUSB Key" installation of OWRT, you need the ramdisk image of OpenWRT. It's not available in the download repository so you will first need to compile it. Here's my method :
[HowTo] Compile OpenWRT

1 - Install Slitaz 2.0 on a dedicated 4 GB min HDD (in a VM, for example) :

Boot your PC on the Slitaz CD and login as tux (no PWD).
Open a console and get root via "su -" and the root pwd which is : root.
Partition your HDD with "fdisk /dev/hda", type "n" to add a new partition hda1 and "w" to write the partition table.
Launch "slitaz-installer" as root and follow instructions. You can get help with Slitaz on forum (http://forum.slitaz.org).
Slitaz is now installed on /dev/hda1.

Now, you will need to install some more packages. Run this as root : "tazpkg recharge; tazpkg get-install slitaz-toolchain".
Do the same "tazpkg get-install XXX" for : bash, ncurses-dev, zlib-dev, gawk, flex, bzip2, python, tar, findutils, wget, patch, diffutils, perl, coreutils. Though it's not checked by prereq.mk, the m4 package is necessary to compile 8.09.1 sources (for the trunk compilation, no m4 package but you'll need the subversion package).

Note : you can also install sakura package (another xterm) to help copy and paste in console.

2 - Get sources of OpenWRT 8.09 and compile it :

Now you can get, configure and compile OWRT as normal user Tux :
Download and go into the extracted tar.bz2 sources directory (from http://downloads.openwrt.org/kamikaze/8.09.1/).
("svn co svn://svn.openwrt.org/openwrt/trunk owrt; cd owrt" for the trunk)
"make menuconfig"
Select in the target system menu, the X86 generic PC. Then in the target image menu, select generating a ramdisk file.
Save configuration before exit then run "make".

After a quite long time, the result of compilation is in /owrt/trunk/bin. The ramdisk file is a very little file called openwrt-x86-vmlinuz, containing the kernel and ramdisk rootfs.

Here is my own build :
stock 8.09.1 Ramdisk
(R15955 of the trunk)

Nota : You can find another HowTo here with Ubuntu/VMWare for WhiteRussian : http://forum.openwrt.org/viewtopic.php?id=8410.
You can also find generic help for building OWRT there, as usual : http://downloads.openwrt.org/kamikaze/docs/openwrt.html

3 - Install OpenWRT image on a USB key :
We're going to install Slitaz on an existing FAT USB key and add the OWRT image to it.
So in Slitaz, launch "tazusbbox" as root. Select the source to install (CDRom) and the USB key for destination (certainly /dev/sda1). Then generate.
That's it : Slitaz is installed on the key. Try it, that's great !

Next, copy the ramdisk file as vmlinuz in a OWRT directory on the USB key. Then modify the file boot/syslinux/syslinux.cfg as this :

Code:

display syslinux.msg label slitaz     kernel /boot/bzImage     append initrd=/boot/rootfs.gz rw root=/dev/null vga=normal autologin home=2C3F-6155  include common.cfg  label owrt     kernel /OWRT/vmlinuz     append console=tty0 reboot=bios  default owrt timeout 20

With this, Openwrt will boot as default after 3 seconds (Slitaz is still available). You can enjoy OpenWRT on any PC, boot in 2 seconds. But your modification will not remain after a reboot...

Next one, my method to :
[HowTo] Make "LiveUSB Key" OpenWRT

Needed : The steps above are supposed to be done.

1 - Create a rootfs addon to modify the stock ramdisk :

The modifications will be made via another initrd append to the first one (see here : http://www.mjmwired.net/kernel/Document … fs.txt#210). I called it modUSB.gz.

I create a modUSB directory in my home where will be the rootfs modifications.
Add an opkg directory where you can place all the packages you want to add to the stock ramdisk.
So I download (from http://downloads.openwrt.org/kamikaze/8 … /packages/) and place :
* In opkg/std, the packages needed to have the ext3 and loop support :
kmod-fs-ext3_2.6.25.20-x86-1_i386.ipk
kmod-loop_2.6.25.20-x86-1_i386.ipk
* In opkg/fat, all the packages needed to see VFAT partition on the key :
kmod-fs-vfat_2.6.25.20-x86-1_i386.ipk
kmod-nls-base_2.6.25.20-x86-1_i386.ipk
kmod-nls-cp437_2.6.25.20-x86-1_i386.ipk
kmod-nls-iso8859-1_2.6.25.20-x86-1_i386.ipk
* In opkg/usb2, all the packages needed to have USB2 support for the key :
kmod-scsi-core_2.6.25.20-x86-1_i386.ipk
kmod-usb-core_2.6.25.20-x86-1_i386.ipk
kmod-usb-storage_2.6.25.20-x86-1_i386.ipk
kmod-usb2_2.6.25.20-x86-1_i386.ipk

* And everything else you need...

Then I use this little script to create the modUSB.gz :

Code:

#!/bin/sh (cd modUSB; find . | cpio -o -H newc | gzip -9) > modUSB.gz

2 - Modify the init script to add the loop function :

The stock one is in the OWRT directory, there : target/linux/generic-2.6/base-files/init.
I made it a little more simpler, faster and add loop function and ability to use opkg added to the directory called "modUSB".

Code:

#!/bin/sh # Copyright (C) 2006 OpenWrt.org  ## ModUSB # Copie du rootfs initial mkdir /modUSB/tmp cp -a /* /modUSB/tmp 2>/dev/null rm -r /modUSB/tmp/modUSB/tmp  # Changement du clavier si besoin [ -n "$lang" ] && loadkmap < /modUSB/$lang.kmap  INITRAMFS=1  . /etc/preinit  # if we have no root parameter, just go to running from ramfs [ -z $rootfs ] && {   export NOMOUNT="No Root"   exec /sbin/init }  #if we have a failsafe boot selected, dont bother #trying to find or wait for a root mount point [ -z "$FAILSAFE" ] || {   exec /bin/busybox init }  # Chargement des packages presents dans /modUSB opkg install /modUSB/opkg/*.ipk >/dev/null opkg install /modUSB/opkg/*/*.ipk >/dev/null  # Load the modules we have in initramfs, this should # make the media accessible, but, it may take some time . /etc/functions.sh load_modules /etc/modules /etc/modules.d/*  #wait 10 seconds for the disc to show up #usb stick typically takes 4 to 6 seconds #till it's readable #it's quite possible the disc never shows up #if we netbooted this kernel COUNTER=0 while [ ! -e ${rootfs%-loop} ]; do   sleep 1; echo -e "\nWaiting for device ${rootfs%-loop}"   let COUNTER=COUNTER+1   [ $COUNTER -eq 9 ] && {     export FAILSAFE="NoDisc"     exec /bin/busybox init   } done  # Test si mode loop : rootfs=XXX-loop [ "$rootfs" != "${rootfs%-loop}" ] && loop=/tmp/mnt/FsOWRT  # now we'll try mount it, again with a timeout # This will fail if the inserted stick is formatted # in a manner we dont understand e2fsck -p ${rootfs%-loop} COUNTER=0 [ -z $loop ] || mkdir -p /tmp/mnt while ! mount ${rootfs%-loop} ${loop:+/tmp}/mnt; do   sleep 1   let COUNTER=COUNTER+1   [ $COUNTER -eq 9 ] && {     export FAILSAFE="MountFail"     exec /bin/busybox init   } done  [ -z $loop ] || { # Montage du filesystem en loop (apres initialisation si besoin) [ ! -f $loop ] && mke2fs -V >/dev/null && {   dd if=/dev/zero of=$loop bs=1024 count=49152   mke2fs -q -j -F $loop }  cp /modUSB/FsOWRT.bz2 $loop.bz2 [ ! -f $loop -a -f $loop.bz2  ] && {   cp $loop.bz2 $loop.1.bz2   bunzip2 $loop.bz2   mv $loop.1.bz2 $loop.bz2 }  COUNTER=0 while ! mount -t ext3 -o noatime,sync $loop /mnt; do   sleep 1   let COUNTER=COUNTER+1   [ $COUNTER -eq 9 ] && {     export FAILSAFE="LoopMountFail"     exec /bin/busybox init   } done  [ ! -e /mnt/etc/banner ] && rm -r /mnt/* && mv /modUSB/tmp/* /mnt  # Nettoyage for i in `ls /modUSB/opkg/e2fs | sed 's/_.*//'`; do opkg remove $i; done rm -r /modUSB/opkg }  rm -r /modUSB/tmp  #It mounted, lets look for a postinit file, again, give it time #I've seen this take 6 seconds to actually complete COUNTER=0 while [ ! -e /mnt/etc/banner ]; do   sleep 1   let COUNTER=COUNTER+1   [ $COUNTER -eq 9 ] && {     export FAILSAFE="No Openwrt FS"     exec /bin/busybox init   } done  unset rootfs loop  for i in proc dev "dev/pts" tmp sys; do   mount -o move /$i /mnt/$i done killall -q hotplug2 exec switch_root -c /dev/console /mnt /sbin/init

3 - Modify your OpenWRT installation on your USB key :

Modify the file boot/syslinux/syslinux.cfg to add the rootfs directive with loop : for example /dev/sda1-loop for a key that the system see in sda1. Add also the initrd directive to take the modUSB.gz into account. I also add a "lang" parameter (see below for the keyboard layout).

In bold, are the modifications :
label owrt
kernel /OWRT/vmlinuz
append initrd=/OWRT/modUSB.gz lang=fr-latin1 rootfs=/dev/sda1-loop console=tty0 reboot=bios

With this, Openwrt boot in 12 seconds from the USB key on my not so new notebook.
I can now enjoy OpenWRT on any PC, and all my modifications remain after a reboot...

You can find my modUSB.gz here.

[HowTo] Change keyboard layout in OpenWRT

When you have no network and have to use OWRT console, it's a pain to use the default US keyboard with a french one...

So you'll have to add the loadkmap utility to busybox via the .config located in the root of the OpenWRT sources. Search for the loadkmap word and change the line "# CONFIG_BUSYBOX_CONFIG_LOADKMAP is not set" to "CONFIG_BUSYBOX_CONFIG_LOADKMAP=y". Then launch the compilation of your ramdisk image as usual.
If you have already compile it, you can re-compile only busybox and get the new ramdisk image with :
"make package/busybox/clean; make package/busybox/install; make target/install"

The busybox package is only 0.1 Kbytes larger with this. Now add, for example, the fr-latin1.kmap to your rootfs (you can find it in the /usr/share/kmap dir of the slitaz distro). To use it, just try "loadkmap < fr-latin1.kmap". Et voila, no more headake ;)

If needed, I can provide the 8.09.1 ramdisk with loadkmap inside.

[HowTo] Add cpio archive creation in OpenWRT

Will be interesting for next step...
Like above, via the .config located in the root of the OpenWRT sources.

Search for the CONFIG_CPIO word and change the line "# CONFIG_BUSYBOX_CONFIG_CPIO is not set" to "CONFIG_BUSYBOX_CONFIG_CPIO=y". After this, add the line "CONFIG_BUSYBOX_CONFIG_FEATURE_CPIO_O=y".
Re-compile only busybox and get the new ramdisk image with :
"make package/busybox/clean; make package/busybox/install; make target/install"

The busybox package is only 0.75 Kbytes larger with this.

If needed, I can provide the 8.09.1 ramdisk with cpio and loadkmap inside.

Next HowTo to come, if I succeed it, I'll try next to had informations how to modify the ramdisk image in order to have a /jffs file on the USB key and save all your modifications there (based on this : http://oldwiki.openwrt.org/ReplaceJFFS2 … Media.html).

Malaysian Repeater Band Plan - CLICK THE IMAGE

2010-04-15T19:14:00.002+08:00

ASTRA Daerah Batu Pahat

2010-04-11T21:29:00.000+08:00

ASTRA Daerah Batu Pahat

Google Maps on Linux

2010-04-11T21:04:00.002+08:00

Open Source GPS HOW TO

Using a Garmin Edge to Plot Cycle Routes with Google Maps on Linux, Macs and Windows

By Martyn C Davis, 14-MAY-2006

On a recent organised cycling ride in the Test Valley down in Hampshire (I'm in the UK), a friend showed me his new toy; a Garmin Edge 305GPS-enabled bike computer. Being a bit of a gadget head I'd played around with GPS on bike rides before, but the old Garmin GPS 12 I'd had seemed almost the weight and size of a brick, it had a serial interface, and the best use I ever really got out of it was to tell me what my coordinates were, which I could then check back onto an OS map. It also had a hard time finding a signal when surrounded by tall buildings or tree cover.

I often find it quite boring riding around the same old familiar routes on my bike, but the alternative, which is figuring out a new route, then stopping every few miles to consult the sweaty OS map in my back pocket spoils the tempo of the ride. My ideal scenario would be to figure out a route beforehand, program it into a GPS, and let it lead me through the new ride. Seeing this new Garmin model rekindled my desire to get this working.

The Edge from Garmin is about the size of a SMALL mobile phone, it's light, and it's sensitive: it picks up a signal almost anywhere you are going to ride. Ideal, I thought. My friend's model was the 305, which does either heart rate or cadence, and has a barometric altimeter built in. The cheaper model, the 205, lacks the HR / cadence, and relies on GPS to calculate altitude, which is less accurate. I have a Polar watch which does all this, so I was happy to go for the 205.

First Impressions

My first impressions were pretty negative. After I'd ordered it from Wiggle I started looking around for information on the unit (OK, I know I should have done the research before ordering the thing, but I ordered it in a moment of gadget lust :). All the information I was getting back from my internet searches were people griping about how Garmin are using proprietary formats and weren't being very helpful (see, for example, this O'Reilly article on the subject).

So I received the unit and had a pretty fruitless few days trying to bend it to my will. The software that comes with the device is crap. For one, it's a Windows application. I use Linux, and Mac OS, and run Windows approximately never, but I do keep one machine (referred to in this household as the toy machine which dual boots to allow me to test stuff and run games). Installing the Garmin software on this machine allowed me to have a brief look, and I didn't like it. It's not intuitive and it looks horrible. There's no way THAT's going to tempt me to use it. Also it's designed more for training than routing.

What do I want?

So, what do I actually want? I had a half-conceived idea that firstly I wanted to be able to use Google Maps to define a route. This would be fantastic, because not only can you zoom right in and out, but you can also see satellite imagery, which is becoming more and more detailed. This allows you to check a spot, say, to see whether it's a junction or just a bend in the road. I then would like to perhaps save that route to a GPX file (GPX is becoming an XML-based standard for GPS data transfer), which I could somehow then upload to the GPS unit. The supplied software and its help files make absolutely no mention of GPX, so (thankfully, as it's Windows) I shan't be using that.

NB: There is a site which is quite popular with cyclists called "GMaps Pedometer" which offers the ability to define routes. It's good, but it has a somewhat different aim. You CAN get GPX out of it, but only through another site and the use of a bookmarklet - hence, for GPS, it's kludgy. Also you have no control over waypoint names etc.

The Linux Approach

Plugging the Garmin unit into my Linux laptop (running Ubuntu "Breezy") via USB, and checking the system logs by typing "dmesg", I see a heartening series of messages:

    [4309364.676000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Garmin GPS usb/tty     [4309364.682000] garmin_gps 5-1:1.0: Garmin GPS usb/tty converter detected     [4309364.726000] usb 5-1: Garmin GPS usb/tty converter now attached to ttyUSB0     [4309364.726000] usbcore: registered new driver garmin_gps     [4309364.726000] drivers/usb/serial/garmin_gps.c: garmin gps driver v0.23

Garmin USB support just works. Support is built into the kernel, so the device now sits on a pseudo-serial port called /dev/ttyUSB0. Hopefully I can find an application that will support it.

I tried a few applications without much success, and the one I kept coming back to was GPSBabel. The UNIX command-line-based version has about a million options and took a while to figure it out, but eventually I got it working. The command line required to transfer a GPX file to the unit is, assuming that your GPX file is called "foo.gpx":

    gpsbabel -r -i gpx -f foo.gpx -o garmin -F usb:

I've written a small script to wrap this call to make it a bit easier to remember. You can grab a copy here.

Generating the GPX File

Next problem: generating my own GPX files! The Google Maps API is fantastic - it's great that Google have allowed third parties to make their own applications around their mapping service. This is definitely the way forward, and it didn't take much hacking before I developed a small javascript prototype application which allows me to click on the map, define a set of waypoints, naming them as I went along, and then generate a GPX file from them, which uploads OK to the Garmin device. Here's an example, which, if you copy and paste into a file, you could use to test with GPSBabel and my script.

                               RICHMNDPK                                  1-START                                           2-RIGHT                                           3-RIGHT                                           4-END

The latest version of this application is now out. You can find it at www.marengo-ltd.com/map2

I welcome any feedback. Join the discussion at my blog: http://www.marengo-ltd.com/blog/. I'd love to hear from you even if it's only to tell me that you find the software useful.

Plans

My plans for the software are as follows:

Define routes (done)
Export as GPX (done)
Save to database (done)
Load from database (done)
Share routes with other users (done)

Conclusion

Well, reservations regarding the proprietary nature of Garmin aside, I have to say that now I've figured out how to plan routes and upload them to the device, I love it. It's got a quite loud beeper on it, to warn you of upcoming waypoints, and the battery life seems quite good. It charges via USB. If you are going on a long, multi-day trip, don't forget the charger, or your laptop and ITS charger. If you are going to be away from any electricity, there's always the USB Battery.

You can find the latest release of the GPX generation software at www.marengo-ltd.com/map

Like I say, if you want to feed back any comments, please join the discussion at my blog: http://www.marengo-ltd.com/blog/.

I'll be interested to see how it works with other GPS units too - drop me a note to tell me what you've got it working with.

Finally, you may also contact me at my gmail address. Use my full name (including middle initial) as quoted at the top of this article, separated by dots (like, for example, "hector.h.monro", except with my name :), and append "@gmail.com" to it. Queries will be given much more attention if you accompany them with a small donation (see the PayPal link at the end of this page).

UPDATE: I've been asked by many people whether this is going to work under Windows. Good news... I've tested GPSBabel under XP and it does appear to. You can test this yourself by installing GPSBabel for Windows, and then, from wherever you installed the software, you can issue a command from the command line the following (assuming you've got the sample GPX file saved as "foo.gpx"):

    gpsbabel.exe -r -i gpx -f foo.gpx -o garmin -F usb:

There's a windowed version of GPSBabel available from their site too if you are not comfortable with using the command line. There is a version for Mac OS X as well. All these work in the same way.

The only downside I see so far is that the current version of the Windows version of GPSBabel (1.2.7) doesn't seem to support the NAME of the route... all routes get imported with a name of "EMPTY", which is a bit confusing when you look at the route list, as you think "EMPTY" means "I have no routes", but that's the name of the route... I know that this has been fixed in the Linux 1.2.8 Beta release, so hopefully the Windows version will also be fixed.

So this means that the application should allow BOTH Linux users and their unfortunate Windows brethren to both easily plot routes via Google Maps for the Garmin Edge devices. Cool.

LCD4Linux-TUTORIAL

2010-04-11T20:47:00.003+08:00

Linux-Options:

lcd4linux [-c key=val] [-F] [-f config-file] [-i[i]] [-o output] [-q] [-v]

-c key=val	overwrite entries from the config-file (key and value have to be specified)
-F	do not fork and detach (run in foreground)
-f config-file	use configuration from 'config-file' instead of /etc/lcd4linux.conf
-i	enter 'interactive mode' (after display initialisation)
-ii	enter 'interactive mode' (before display initialisation)
-o output	write picture to 'output' (raster driver only)
-q	suppress startup and exit splash screen
-v	generate info messages
-vv	generate debugging messages
-h	print version number and a small help text, then exit
-l	list available drivers

Start automatically during boot:

You have to create the startscript "/etc/init.d/lcd4linux" and generate the necessary runlevel entries by hand, e.g. with the command "ln -s /etc/init.d/lcd4linux /etc/rc5.d/S99lcd4linux".

Example for a startscript:

#! /bin/sh # # lcd4linux # PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin DAEMON=/usr/local/bin/lcd4linux NAME=lcd4linux DESC=lcd4linux test -f $DAEMON || exit 0 set -e case "$1" in   start)  echo -n "Starting $DESC: "  start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON  echo "$NAME."  ;;   stop)  echo -n "Stopping $DESC: "  start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON  echo "$NAME."  ;;   reload)  start-stop-daemon --stop --signal 1 --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON    ;;   restart|force-reload)  echo -n "Restarting $DESC: "  start-stop-daemon --stop --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON  sleep 1  start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON  echo "$NAME."  ;;   *)  N=/etc/init.d/$NAME  echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2  exit 1  ;; esac exit 0

Alternatively you can invoke LCD4Linux within the file /etc/init.d/boot.local.

HD44780 Wiring

95% of all trouble with displays connected to the parallel port are due to wrong wiring! There is no "standard", whereupon the wiring should be carried out. Thus LCD4Linux supports the so-called "soft wiring", which means that you can use (nearly) any wiring you like. You just have declare it in lcd4linux.conf. A HD44780 display typically has 16 connections (if only 14 are available, then the connections for backlight are missing). The connections have the following meaning:

Pin	Name	Comment
1	GND	ground
2	VCC	supply voltage +5V
3	LCD_DRIVE	contrast voltage (0 .. +5V)
4	RS	Register Select (low=instruction, high=data)
5	R/W	Read / not Write (high=read, low=write)
6	ENABLE	starts data read/write
7	DB0	Data Bit 0
8	DB1	Data Bit 1
9	DB2	Data Bit 2
10	DB3	Data Bit 3
11	DB4	Data Bit 4
12	DB5	Data Bit 5
13	DB6	Data Bit 6
14	DB7	Data Bit 7
15	BACKLIGHT	backlight supply voltage
16	BL GND	backlight ground

The parallel port has 25 connections:

Pin	Name	I/O
1	STROBE	Out
2	DB0	I/O
3	DB1	I/O
4	DB2	I/O
5	DB3	I/O
6	DB4	I/O
7	DB5	I/O
8	DB6	I/O
9	DB7	I/O
10	ACK	In
11	BUSY	In
12	PAPEROUT	In
13	SELECT	In
14	AUTOFD	Out
15	ERROR	In
16	INIT	Out
17	SLCTIN	Out
18-25	GND	n/a

The data lines (DB0..DB7 on the display, DB0..DB7 on the parallel port) are always connected directly (unless you are using the 4-bit mode - but that is intended for experts rather, and these are not reading this tutorial anyway :-). The interesting part is, how the display's control signal is connected with the 4 possible output lines from the parallel port:

display:

Pin 4: RS (Register Select) Pin 5: R/W (Read/Write) Pin 6: Enable

parallel port:

Pin 1:  Strobe Pin 14: AutoFD Pin 16: Init Pin 17: SelectIn

For each control line you have to specify, which signal of the parallel port is used. This is done by the "Wire.xy"-entries.

E.g. if you are using the popular WinAmp wiring, it has to be defined like this:

Display Pin 4 (RS)     => Parallelport Pin 16 (Init) Display Pin 5 (R/W)    => Parallelport Pin 14 (AutoFD) Display Pin 6 (Enable) => Parallelport Pin 1  (Strobe)

The adequate soft-wiring entries have to be:

Wire.RW        'AUTOFD' Wire.RS        'INIT' Wire.ENABLE    'STROBE' Wire.ENABLE2   'GND' Wire.BACKLIGHT 'GND' Wire.GPO       'GND'

Wiring example:

If you want to connect a standard HD44780 display to the parallel port using the WinAmp-Wiring, do it like the following:

LCD	Parallel Port	Power Supply	contrast pot (10k)
Pin 1	Pin 18	GND	Pin 1
Pin 2	-	+5V	Pin 3
Pin 3	-		Pin 2 (slider)
Pin 4	Pin 16
Pin 5	Pin 14
Pin 6	Pin 1
Pin 7	Pin 2
Pin 8	Pin 3
Pin 9	Pin 4
Pin 10	Pin 5
Pin 11	Pin 6
Pin 12	Pin 7
Pin 13	Pin 8
Pin 14	Pin 9
Pin 15	-	100 ohm resistor to +5V
Pin 16	-	GND

TROUBLESHOOTING

Problems when compiling:

problems with user rights? install as root user
error in configure.log? try different configure options

e.g. errormessage

#error "gd.h not found!" make: *** [Raster.o] Error 1

workaround: configure --with-drivers=all,\!PNG

Problems starting LCD4Linux:

rights on /etc/lcd4linux.conf set correctly?
is the display initialised when starting LCD4Linux?
invoke LCD4Linux with the options "-Fvvq" and have a look at the debug-output
check syntax in lcd4linux.conf

USB Monitor

2010-04-11T09:59:00.004+08:00

Hardware
- A Linux based router/NAS/Plug Computer/PC with USB ports (e.g. Asus WL-500g Premium)
- USB keyboard (e.g. Keysonic ACK-3400 U)
- DisplayLink device (e.g. Samsung U70)
Software
- Binaries (extract to /)
  - OpenWRT 8.09 brcm-2.4
  - SheevaPlug
- Building for OpenWRT
  - gcc 4.1.2 as 8.09 compiler (with libboost, gcc 3.4.6 and 7.09 I got defined in discarded section while linking, with gcc 4.2.4 and trunk can't resolve symbol '_Unwind_GetIPInfo' at runtime if an exception happens; the SVN trunk package gave some compile error, too.)
  - packages: libstdcpp_4.1.2 (brcm*), libusb, libfreetype
  - modules: 2.4: input.o, evdev.o, hid.o; 2.6: input-core.ko, evdev.ko, usbhid.ko (for brcm-2.4 a patch is necessary, but even then hid.o doesn't get built for me.)
  - libboost_program_options-gcc41-mt-1_34_1.so.1.34.1, libboost_thread-gcc41-mt-1_34_1.so.1.34.1 from the Boost C++ library package from BTG
  - ROTE-256
  - SlugTerm and my modifications (based on tubecable; 26C3: Reverse-Engineering DisplayLink devices)
  - font: I recommend FNTs (FON2FNT). BDFs. PCFs don't have line drawing characters and are slow; no cache yet. Scalable fonts are not layed out correctly yet.

Command line switch help

root@OpenWrt:~# slugterm --help Options:   --help                show help message   -k [ --keyboard ] arg keyboard event source   -p [ --pid ] arg      USB product ID [4]   -i [ --init ] arg     initialization sequence [58]   -f [ --fpath ] arg    font   -w [ --fwidth ] arg   font width for scalable fonts   -h [ --fheight ] arg  font height for scalable fonts   -c [ --commands ] arg command(s) to run in terminal

You can grab the initialization sequence for yourself from the Windows driver with an USB sniffer and dldecrypt.c or use one of the dl_register_init_* in dldemo.c. Some modes I captured:

Samsung U70	800×480	`00203c7ac9f26c48f97053ffff2127032091f3fffffff901e00102c819`
Samsung 244T @ Lenovo 45K5296 (DL-195)	1920×1200	`00ca2115426c15f466c536ffff6c150780a335ffffffca04b004025078`

Example

root@OpenWrt:~# slugterm -k /dev/input/event0 -p 0103 -i 00203c7ac9f26c48f97053ffff2127032091f3fffffff901e00102c819 -f /usr/local/share/fonts/FON2FNT/dosapp_18.FNT -c "/bin/ash --login"4D Systems OLED version4-x64.

Maemo Extras, Extras-Devel, Extras-Testing: why, what for?

2010-04-02T13:15:00.003+08:00

The Maemo community runs three separate repositories: Extras, Extras-Devel, and Extras-Testing, each of them containing different applications.

Maemo Extras comes pre-configured on the N900 (and in current firmware it is disabled by default, so it needs to be enabled by the user by unticking the "Disabled" option) while the two remaining ones need to be added manually.

So what are they and why are they separate?

Maemo Extras is the main repository, meant to be used by end-users. It contains applications that have been tested and verified for compatibility, safety, proper functionality, "optification" (i.e. installation in the bigger /opt partition not to take space in limited rootfs), etc. If you are a person that does not like using applications which are still in "beta" stage, or you don't feel the need to test/have everything right as it comes, you may want to restrict yourself to only using this Extras repository.

In case you accidentally delete this repository, or if you need its details for any other reasons, they are as follows:

Catalogue name: Extras
Web address: http://repository.maemo.org/extras/
Distribution: fremantle Components: free non-free
...or simply click here on your Maemo device to install it automatically. --------

Extras Testing repository contains freshly created applications that haven't yet been tested/verified. And this is what this repository is meant for: it is for those who would like to test new applications. Using this repository, you can get all new apps right after they have been released, and additionally you can help with testing them against any problems, "improper behaviour", or any other issues. Once an application contained in this repository has been tested and found safe, compatible and properly working, it will get "promoted" to the above mentioned Extras repository for general use.

If you decide to use this repository, please be aware of two possible "risks":

applications contained there may NOT be correctly "optified". This means that some of them may NOT obey the rule to install larger packages in the large 2 GB /opt partition rather than the small (70 MB or so of free space on a "fresh" device) rootfs. This may lead to the "/" (root) partition getting filled. Of course, once you notice this, you may just unistall those applications, so it is not "irreversible"

apps in Testing may NOT pay too much attention to proper power management. This means that installing some of the applications from Testing may result in shorter battery life. Again, as above, if you notice such an issue, you can uninstal the "problematic" software.

The details of the Extras-Testing repository to be typed in Application Manager in order to add this repository are as follows:

Catalogue name: Extras-Testing
Web address: http://repository.maemo.org/extras-testing/
Distribution: fremantle
Components: free non-free

...or simply click here on your Maemo device to install it automatically.

Extras-Devel this is the "lowest-level" repository with applications that usually are on very early development stage, let's call them "alpha" versions.

If you are not used to dealing with alpha/beta software, or if you want to be sure that software you install won't mess with your phone, do not use this repository. It is not meant for end-users, but only for people who know what they are doing.

Repository details needed to add this catalogue to the App Manager are as follows:

Catalogue name: Extras-Devel
Web address: http://repository.maemo.org/extras-devel/
Distribution: fremantle Components: free non-free
...or simply click here on your Maemo device to install it automatically.

NYUMPIT LAGI

2010-03-24T14:34:00.004+08:00

Hanya yg ada asas buleh baco...... kalu x dop tekan START >>>>>

ITINERARY FOR SARAWAK TRIP:

-----------------------

ALIAS/SALANMR

DAY DATE STOPOVER CITY TIME STATUS SERVICES

--- ----- --- ------------------------------------ ---- ------------ -------------------------------

TUE 30MAR DEP KUALA LUMPUR INT 1140 MH 2510 NON-STOP

MAIN TERMINAL ECONOMY (V) BOEING 737-400 ARR KUCHING 1325 CONFIRMED 01HR 45MIN

ALIAS/SALANMR SEAT RESERVED 06C/CONFIRM

MH - MALAYSIA AIRLINES REF:KQZ9C

THU 01APR DEP KUCHING 1635 MH 3154 NON-STOP

ECONOMY (M) ATR 72 ARR SIBU 1720 CONFIRMED 00HR 45MIN

ALIAS/SALANMR SEAT RESERVED 05A/CONFIRM

MH - MALAYSIA AIRLINES REF:KQZ9C

SAT 03APR DEP SIBU 1510 MH 3266 ARR BINTULU 1545 CONFIRMED 00HR 35MIN

SIBU - BINTULU OPERATED BY: MASWINGS

ALIAS/SALANMR SEAT RESERVED 05A/CONFIRM

MH - MALAYSIA AIRLINES REF:KQZ9C

MON 05APR DEP BINTULU 1430 MH 2743

ARR KUALA LUMPUR INT 1635 CONFIRMED 02HR 05MIN

ALIAS/SALANMR SEAT RESERVED 05C/CONFIRM

MH - MALAYSIA AIRLINES REF:KQZ9C

freq scanning bkt larut

2010-01-31T19:20:00.004+08:00

Tawau - Joint Task Force Command Center Project - Ground, Sea and Air

2009-12-03T21:56:00.006+08:00

M3TR

Software Define Radio and HF Transceiver

Workacholic RSMY Multiracial Team - Contacting friends at World from Tawau, we have everythings from top to ptt

HF Dipole Antenna

Every Angle of HF Antenna

From Top to Ground HF Antenna

RTM Digital TV - Delivery RF cable to various site

2009-11-29T14:20:00.002+08:00

Gn Ledang

Ulu Kali

RF cable size 6"

December 2009 Schedule

2009-11-26T23:02:00.003+08:00

RTM Digital TV

Bkt. Tampalagus

27.11 Vessel arrive at Port KK
30.11 Travels from Johor Bahru to KK then to Sipitang
01.12 Transfer from warehouse drum feeder to individual truck or low loader
01.12 arrive noon - Bkt. Tampalagus (1 X 2.5m drum)
02.12Travel back to KK, then travel to Tawau Joint Task Force 2nd Command Centre
03.12 M&E Inspection at JTF2CC
04.12 Travel back from Tawau to KK
04.12 From KK back to Johor Bahru.

October and November 2009

2009-10-13T16:56:00.009+08:00

TM-AMP Antenna G.Pulai : Installation
Pulai 03.10 to 09.10 AMP Radio

Cyberjaya - MCMC 14/10/2009 DCMU PM

RTM Digital TV
1) 21/10/2009 - Gunung Ledang, Johor
2) 22/10/2009 - Gunung Pulai, Johor
3) 24/10/2009 - Gunung Palong, Kedah
4) 27/10/2009 - Gunung Penara, Pulau Pinang
5) 29/10/2009 - Gunung Ulu Kali
5) 30/10/2009 - Gunung Ulu Kali
6) 31/10/2009 - RTM Kota Bharu

back to JB - mati ooo...... 1hb nak meeting astra jb lagi

TM-AMP Antenna G.Pulai : Field Strength Measurements (FSM)
7) 02/11/2009 - Johor Bahru and Kulai Area
8) 03/11/2009 - Batu Pahat, Kluang and Paloh Area
9) 04/11/2009 - Kota Tinggi, Bdr Penawar and Tiram Area
10) 05/11/2009 - Segamat

Ulu Kali

04.11 Clearance customs, duty, etc at Port Klang

05.11 Transfer from containers to warehouse

09.11 Transfer from warehouse drum feeder to individual truck or low loader

10.11 low loader & 10 ton lorry wt crane travels in the morning

10.11 Travels to Ulu Kali

10.11 Feeder arrives noon - G. Ulu Kali (1 X 4m drum)

11.11 Travels to KB

Kota Bharu

11.11 Transfer from warehouse drum feeder to individual truck or low loader

11.11 low-loader travels at night

12.11 Feeder arrives noon, crane to be available at site - Kota Bharu (1 X 4m drum)

12.11 Travels back to KL

Ledang

16.11 Transfer from warehouse drum feeder to individual truck or low loader

16.11 low loader & 10 ton lorry wt crane travels at night

16.11 Travels to Ledang

17.11 Feeder arrives morning - G. Ledang (1 X 4m drum)

17.11 Travels to Pulai

Pulai

17.11 Transfer from warehouse drum feeder to individual truck or low loader

17.11 low loader & 10 ton lorry wt crane travels at night

18.11 arrives noon - G. Pulai (1 X 4m drum)

18.11 Travels back to KL

19.11 Travels to Penara

Penara

19.11 Transfer from warehouse drum feeder to individual truck or low loader

19.11 10 ton lorry wt crane travels at night

20.11 arrive morning - Bkt. Penara (1 X 2.5m drum)

20.11 Travels to Palong

Palong

20.11 Transfer from warehouse drum feeder to individual truck or low loader

20.11 10 ton lorry wt crane travels at night

21.11 arrive morning - Bkt. Palong (1 X 2.5m drum)

21.11 Travels back to KL

Bkt Tampalagus depends on the boat schedule from KL - KK but approximately

1-2 weeks from 04.11

For scheduling purposes*,

Bkt. Tampalagus*

04.11 Clearance customs, duty, etc at Port Klang

18.11 Vessel arrive at Port KK

19.11 Transfer of drum feeder to warehouse

23.11 Transfer from warehouse drum feeder to individual truck or low loader

24.11 Travels to KK then to Sipitang

24.11 10 ton lorry wt crane travels in the morning from KK

25.11 arrive noon - Bkt. Tampalagus (1 X 2.5m drum)

25.11 Travels back to KK, then to KL.

2009-08-17T16:19:00.002+08:00

DATE	TIME	SCHEDULE	REMARKS
8/9/2009	-	Traveling (KL – Kuala Terengganu)
9/9/2009	09:00 – 10:00 12:00 – 13:00	Site survey & Briefing at : a) Bukit Jerung (Celcom station) b) Bukit Besar (Telekom station)	Contractor / MPB Contractor / MPB / TM
10/9/2009	09:00 – 10:00 13:00 – 13:00 15:00 – 16:00	Site survey & Briefing at : a) Bukit Bakar (Telekom station) b) Mulong KBX stn (Celcom station) c) Peringat station ( MPB site)	Contractor / MPB /TM Contractor / MPB Contractor / MPB
11/9/2009	-	Traveling (Kota Bharu - KL)