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

[arrrghhh]

Originally Posted by natemcnutty

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

I just added a line to delete all of the .rec files... Isn't the fsck a good idea to run? It probably doesn't make that much of a difference... Not sure TBH.

[udayse]

Originally Posted by arrrghhh

I just added a line to delete all of the .rec files... Isn't the fsck a good idea to run? It probably doesn't make that much of a difference... Not sure TBH.

Hi,
Where do i add the line and what line do i add to delete?
Uday

[natemcnutty]

Originally Posted by udayse

Hi,
Where do i add the line and what line do i add to delete?
Uday

Quick and dirty way would be to add rm /sdcard/*.rec to your froyo.user.conf on the sd card under /andboot/conf. Just put it in the custom run at the end.

[arrrghhh]

Originally Posted by natemcnutty

Quick and dirty way would be to add rm /sdcard/*.rec to your froyo.user.conf on the sd card under /andboot/conf. Just put it in the custom run at the end.

I put a -rf on that rm command... but since they're all files, the -r probably isn't necessary. The -f isn't either.

So udayse, just put that command in your froyo.user.conf, like nate said.

[shawndoc]

I also had the problem on the newer builds with the force-CDMA no longer working. I edited the startup file, launched directly from haret.exe, not the startup utility, no dice.

My way of solving it was to remove the SIM card. Once I did that everything works. No idea why I have to do this on the newer builds when I didn't have to on the older builds.

[arrrghhh]

Originally Posted by shawndoc

I also had the problem on the newer builds with the force-CDMA no longer working. I edited the startup file, launched directly from haret.exe, not the startup utility, no dice.

My way of solving it was to remove the SIM card. Once I did that everything works. No idea why I have to do this on the newer builds when I didn't have to on the older builds.

You can't have a SIM with CDMA... Perhaps with WinMo you can roam on the SIM, but I don't think both radios work in Android. It's one or the other - GSM or CDMA, choose wisely

[shawndoc]

Originally Posted by arrrghhh

You can't have a SIM with CDMA... Perhaps with WinMo you can roam on the SIM, but I don't think both radios work in Android. It's one or the other - GSM or CDMA, choose wisely

Right, that's what the force CDMA option did. It allowed you to leave the SIM in, but force Android to use the CDMA radio. That function is no longer working.

EDIT: Seems to be working in the latest build. Haven't tested it fully though.

[demonlordoftheround]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

Even with Force CDMA=1, it seems like Android will find the SIM and you will have no service after a few boots. I just keep it taped to the inside back cover just in case.

[m_reyna_16]

hey guys i am new to all of this and i just installed the "Android v2.2 Froyo: BLAZN" cab from THIS site and installed it to my sd card.... i soft reset and use the link it creates in my programs menu and select the RHOD 400 from the list....

doesnt boot! am i doing something wrong?

[arrrghhh]

Originally Posted by m_reyna_16

hey guys i am new to all of this and i just installed the "Android v2.2 Froyo: BLAZN" cab from THIS site and installed it to my sd card.... i soft reset and use the link it creates in my programs menu and select the RHOD 400 from the list....

doesnt boot! am i doing something wrong?

I find it interesting people post in the thread with an older date on it...

No matter, why doesn't it boot? In other words, what happens? Do you see the flying text? Do you see the boot animation? Is it just playing over and over?

Rule of thumb, first boot can take up to 10 minutes. If longer, soft reset to winmo, delete your data.img (it's where you run haret.exe from) and try try again. I don't encourage usage of the cab or the startup utility, and you definitely need to read the FAQ.