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

[arrrghhh]

Originally Posted by natemcnutty

Double check your startup.txt file. This has happened a lot recently where people had two instances of the force_cdma option in their startup.txt. Delete the first one that says force_cdma=0, then use the droid launcher utility to force cdma.

Isn't MGJDroidUtil still not supposed to be used? It corrupts the startup.txt quite frequently... I know they were talking about updating it. I wouldn't use it ATM.

[natemcnutty]

Originally Posted by arrrghhh

Isn't MGJDroidUtil still not supposed to be used? It corrupts the startup.txt quite frequently... I know they were talking about updating it. I wouldn't use it ATM.

The update functions are broken and should not be used. As far as using it to select keyboard type, force CDMA, and force hardware 3D, I believe it can still be used. I tested it on my RHOD500, but my data connection has been somewhat flaky. I keep having to switch back and forth between airplane mode to get data back.

I'll give it a try just editing startup.txt, but I like to test things the way the majority of people are going to be using the phone as well. Since everyone is accustomed to using that startup tool, I prefer to use it as well and only edit startup.txt directly when I have to.

[Shott3r]

Does anyone actually have the Sprint Rhodium 400 working with the 9/26 package? If so, please post your startup.txt.

I have the same problem where it does not find a network. All previous builds work fine. I removed the extra force_cdma from my startup.txt and launch with haret.exe, but no dice.

[arrrghhh]

Originally Posted by Shott3r

Does anyone actually have the Sprint Rhodium 400 working with the 9/26 package? If so, please post your startup.txt.

I have the same problem where it does not find a network. All previous builds work fine. I removed the extra force_cdma from my startup.txt and launch with haret.exe, but no dice.

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod400 rel_path=Androids/TP2Ref north_am_dialing=1"
boot

Just ignore the rel_path and north_am_dialing statements. I also think there's some old stuff in there... like pmem.extra I don't think is used, pm.sleep_mode, or the clock-7x00 statements. I guess I should try to trim the fat from my startup, but if it works I generally just go with it.

[Shott3r]

Originally Posted by arrrghhh

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod400 rel_path=Androids/TP2Ref north_am_dialing=1"
boot

Just ignore the rel_path and north_am_dialing statements. I also think there's some old stuff in there... like pmem.extra I don't think is used, pm.sleep_mode, or the clock-7x00 statements. I guess I should try to trim the fat from my startup, but if it works I generally just go with it.

Not sure why, but it worked. Reduced the CPU speed to 604, and deleted the Rel_Path argument, and back in business! Thanks!

[udayse]

Hi Everyone,
Everytime I bootup android, I see a new FSCK file in the root of the storage card. This can get annoying, plus not sure if its safe to delete?
Anyone share their experience?
Thanks
Uday

[JWise1203]

Originally Posted by udayse

Hi Everyone,
Everytime I bootup android, I see a new FSCK file in the root of the storage card. This can get annoying, plus not sure if its safe to delete?
Anyone share their experience?
Thanks
Uday

I think this is related to Android thinking that it needs to check the file system (storage card) because the OS was not shutdown correctly. Are you actually powering off the phone when you switch back to Windows Mobile? Or are you pulling the battery? Those files should be safe to delete.

[udayse]

Originally Posted by JWise1203

I think this is related to Android thinking that it needs to check the file system (storage card) because the OS was not shutdown correctly. Are you actually powering off the phone when you switch back to Windows Mobile? Or are you pulling the battery? Those files should be safe to delete.

Yup, I always power off. Never taken the battery out.

Thanks

[udayse]

Originally Posted by udayse

Yup, I always power off. Never taken the battery out.

Thanks

I re-installed BLAZN, still i have the same problem. THis is very annoying. Wish there was a solution.

[natemcnutty]

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2497; U; en) Presto/2.5.25)

Originally Posted by udayse

I re-installed BLAZN, still i have the same problem. THis is very annoying. Wish there was a solution.

Solution: Comment out the code for file system check in init for eclair-rootfs and build.