Android/Linux for CDMA Touch Pro 2 Rhodium Updated 5-20-2010

[bytethegroove]

Ksaxe

Great News....Bill Gates just called me,
Microsoft wants to donate some money to send you back to school.
obviously you can't read.....so we all thought this was a great idea.

Sometimes it helps to read the whole post....but we understand if reading isnt your strong point!

[jtaylor13]

WIN 7. Will be the same garbage we have now.The reason they claim not to run win 7 on 6.5 phones is no time to make it backward compatible.OL PLEASE.Microshaft. is going down.Let's see. VISA(FAIL)internet explorer (FAIL) and fallen behind. Microshaft still wants us to have office on each machine.Hummm. NOPE.I have win 7 machine.But i had to pay for it after being screwed with vista.No wonder people steal there software.It is for revenge for being screwed.Microshaft is still thinking in terms of old ways.They sit around scratching there heads and have no idea they are on fire and going down.

[k6squid]

aaaaaand... with all that said, I can't wait till this thread is closed like all the others.

Someone should just create an "Android sound" thread, thats what everyone is waiting for anyway. I could'nt care less about any of the changes that have been made to the build since data was fixed.

Yes, Im entitled to sound in Android. Fix it already!

[goofy]

Originally Posted by k6squid

aaaaaand... with all that said, I can't wait till this thread is closed like all the others.

Someone should just create an "Android sound" thread, thats what everyone is waiting for anyway. I could'nt care less about any of the changes that have been made to the build since data was fixed.

Yes, Im entitled to sound in Android. Fix it already!

If you fixed already post instructions on how too...that ll be great for other to fix it....lol thnxs

[steveholtam]

What is with all the off topic crap? People need to stick to news and questions about Android on our Touch Pro 2's. Take your OS pissing matches to another thread already...

[k6squid]

OS/X 2 Warp pwn3z...

please close this useless thread.

(and get sound working for gods sake.)

[blckout99]

Anyone else have a quiet concern that dev will slow or come to a screeching halt when the EVO 4g is released next month ? Android, 4.3" Screen, Sense, .50" thick, and Snapdragon. Why would anyone need their Rhodium anymore ?....

[chelss alviaa]

Originally Posted by cflynt

Android for CDMA Touch Pro 2 Rhodium (RHOD400/RHOD500)

We decided to go ahead and restart this thread so that maybe we can keep things more updated. I myself have a more than full-time job and large family, so my time here is in and out all the time, but I definitely am here often. And I know there are some other contributors that are here much more that should be able to help with questions and such.

This is NOT just a Development thread. The original thread wasn't meant just for development either. I don't know where that started. But it is here so that people that want to try something new can. And hopefully we can keep things updated as to the new things that are happening with it etc. So feel free to post questions, I no doubt won't know all of the answers, but hopefully other people browsing the forum might. As well as PLEASE check the 2nd Post for the FAQ. There are questions that get asked over and over, and most of them get put in the FAQ if you just look. If you need me to modify the Question/Answer to better explain, please let me know. Other than that. ENJOY IT!

Note: This is work in progress. If you don't like it, figure it out on your own or read a different thread!

Note: I own a Sprint Touch Pro 2, currently till Supersonic comes out heh. So I really can only tell things that I know from first hand. But others own other Carriers, and hopefully can help contribute, and we can have an informative thread for all versions of CDMA Rhodium. In time, hopefully we can have an all in one GSM/CDMA thread. Once more things are merged together. Lots of stuff in here has been duplicated from other threads out there to try and give you proper information. Thanks to all those Ops for their information.

First things first. Let it be known there are tons of Developers that have made what we have available to us today happen. I am not a developer myself, I am a tinkerer, you know from Tinker Bell! So I take no credit for anything you find in here. There might be times I will update something for you and make it available to you when you wouldn't be able to get it otherwise, that is tinkering! I am not the brains behind the scene. So you need to definitely thank the many developers who all I am sure I won't mention, but to name a few:

phhusson, enatefox, dzo, zenulator, Chamonix, Stinebd, Makkonen, MrPippy, cr2, Markinus, Babijoe, Reefermattness, DracoLX, kstephens98, elroy944, davidebeatrice, chkms, eval-, 95Civic and anyone else who contribute to get this so far. There are tons more no doubt. These are names I have dealt with among ones that I have heard about.

Links will be in the 2nd Post to other threads of importance. Not that I might miss some, so don't feel bad. If I/and or anyone feels I should link a thread in here, by all means let me know.


Installation Changelog
2010-04-20: Updated charging status
2010-04-05: Updated support for Rhodium 500 Keymapping
2010-03-31: Updated link to newer XDAndroid build.
2010-03-31: The special CDMA RIL Changes we needed for CDMA Rhodiums has now been merged with the Autobuild Rootfs.img, so now we all use the same rootfs! Thanks MrPippy!
2010-03-23: Start of New Thread
2010-03-22: Updated USC data issues. Seems there is a fix now.
2010-03-20: Updated rootfs for support of Wifi Tethering.
2010-03-09: Updated rootfs to fix arrow key mapping.
2010-03-08: Updated startup.txt to fix g-sensor and virtual keyboard issues.
2010-03-07: New version of the RIL: should be more reliable (i.e. not booting into Airplane mode as often), and Market now works! Also thanks to NeoMatrixJR, some keymap fixes

Feature Status

What's Working

• Vibration
• Touchscreen
• Navigation buttons, refer to the FAQ for details
• CDMA Radio: Phone calls, SMS
• CDMA Data: Sprint and Verizon for sure. USCC needs a workaround for now, refer to the FAQ. Others I haven't gotten latest reports on.
• Earpiece/mic (only for phone calls)
• WiFi (Networks with WEP encryption do not work, unprotected and WPA networks are fine)
• Hardware Keyboard, works for most all devices
• Backlight control: turn off auto-dimming in WinMo if you want it to work
• Market
• Charging for the most part. Battery meter and temp readings not 100%

Semi-Working

• Battery status, the battery meter is working but the calculations aren't proper. So it will show a status but won't be 100% proper by any means.
• Power management: Definitely a work in progress, don't expect more than maybe 8 hours on a charge.
• Charging, with latest kernel, they have updated the vbus settings to see power applied and show proper charging status. As mentioned though the meter isn't 100% so I don't know that it will shut off charging so don't leave hooked up for extended periods would be my recommendation.
• GSensor. Works fine for games, but for standard desktop usage it is quirky, so best to disable Auto Rotation, refer to FAQ. But it will always rotate for you when you slide the keyboard open, so no loss.
• Hardware 3D accel, iffy, but does work, but does cause some things not to. Refer to FAQ for how to enable.

Not Working Currently

• External Speaker Sound (music, ringtones, etc.)
• Full Speakerphone, External Speaker works in-call but Mice doesn't currently
• Bluetooth
• Camera
• GPS
• USB Mass Storage
• MMS, at least that I have heard, I haven't tried myself.
• Proper battery meter, it won't show you your battery life properly as mentioned above. Work in progress.
• Proper charging, again, as mentioned above, works, but wouldn't trust leaving plugged in till the meter is functioning properly.
• Battery temperature readings. Not calculated properly just yet.

Just because something isn't listed here doesn't mean it doesn't or does work. These are things I have found myself as well as known from other threads and forums. As I know more it will be updated. And things are being worked on all the time.

Instructions to get you started

• Refer to Post #3 for Mackie's all in one zips for you if you want a hopefully all in one updated package.
• First you need an Android Build. Download babijoee's latest XDANDROID stable release, which is based on 2.01 Eclair and unzip it to the root of your SD card.
• Next, I recommend you delete the zImage and modules files that are part of that release and update to the latest explained next.
• Download the Latest Kernel Package from Glemsom's Kernel Autobuild Site. Download by clicking on the Package Icon and then Unzip the Tar file, 7-zip in windows can do this as well as WinRAR. Rename zImage.xxxxxxxxx to just zImage with no extension, and put zImage and the modules file untouched in the root of your storage card.
• Download the Latest rootfs from the XDAndroid Eclair rootfs Build Service. Unzip it and rename it to just "rootfs.img" and replace the one on your Storage Card.
• Download the Latest initrd.gz from the XDAndroid Eclair initramfs Build Service. This one, DON'T unzip, just rename to "initrd.gz" and replace the one on your Storage Card.
• Download the startup.txt attached to this post, and copy it into the root of your SD card. This should get you started with some basic options. Refer to the FAQ for other options you can add. This by default is setup for Sprint Rhodium Keyboard (Rhodium 400), If you want a Rhodium 500 Keymapping make sure to edit the startup.txt and change physkeyboard=rhod500 ie. for Verizon's mapping.
• From Windows Mobile, use File Explorer, navigate to the Storage Card and run HaRET.exe to boot Android.

MrPippy and 95Civic are who started getting CDMA working for us. No doubt that others have contributed in many ways. But it was requested that we keep the donation links up for MrPippy to help him in rough times. And being as he got us to the current spot, I feel it is definitely in order:

Quote from MrPippy

So everytime i run haret . it says, the super block could not be read or does not describe a correct ext2 . filesystem . if thedevice is valid and it really contains a filesystem (and not swap or ufs or something else) : then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -bb 8193 (device) the further down it says can't access tty; job control turned off. the it has a # blinking and it doesnt do anything for about 2 minutes. everytime i try to run haret. it takes about 4 hours and it never ends-up working. uhh what should i do?

[rushco]

Originally Posted by blckout99

Anyone else have a quiet concern that dev will slow or come to a screeching halt when the EVO 4g is released next month ? Android, 4.3" Screen, Sense, .50" thick, and Snapdragon. Why would anyone need their Rhodium anymore ?....

Because people don't feel like paying $40 more for the same plan they have now.

[kain125]

hey its saying that i have 3G but datas not working

cant get on browser or market