Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS! - Page 141

**arrrghhh** · #**1401** (**permalink**) 03-04-2010, 08:24 PM

Nvm, a reboot fixed my data issues. New rootfs fixes data for me, FYI.

DrUnKeN_TiGeR · #**1402** (**permalink**) 03-04-2010, 09:13 PM

seems all im getting is "waiting for sd card" i dled XDANDROID.01.03.10.7z and unzipped it to the sd card when i run HaRET.exe it has a few lines of code then just "waiting for sd card"

tom6433 · #**1403** (**permalink**) 03-04-2010, 09:19 PM

Quote:

Originally Posted by DrUnKeN_TiGeR

seems all im getting is "waiting for sd card" i dled XDANDROID.01.03.10.7z and unzipped it to the sd card when i run HaRET.exe it has a few lines of code then just "waiting for sd card"

did you find the appropriate startup.txt file and also put it on the root of the card?

hussmanne · #**1404** (**permalink**) 03-04-2010, 10:01 PM

I did the pull battery out/squeeze on space bar/back of space bar area as hard as possible and the keyboard issue seems to have improved for now. No telling how long this will last!

[SP]JESTER · #**1405** (**permalink**) 03-04-2010, 11:45 PM

Newest rootfs, No 3g on Glossy 1.9. 10-20 secs of loading then dies out

166486 · #**1406** (**permalink**) 03-05-2010, 10:35 AM

Quote:

Originally Posted by tom6433

did you find the appropriate startup.txt file and also put it on the root of the card?

which will be the appropiate file for me if i have a Touch Pro Verizon CDMA

**makkonen** · #**1407** (**permalink**) 03-05-2010, 10:57 AM

Quote:

Originally Posted by [SP]JESTER

Newest rootfs, No 3g on Glossy 1.9. 10-20 secs of loading then dies out

Sorry, having trouble keeping track -- did you ever have data working with Cellular South? i.e. is this a build problem or a network problem (lots of people are having trouble with lots of non-sprint networks)?

If it's the latter, I don't have a good response. Haven't figured out where the authentication process fails (which is what I suspect the problem is).

Quote:

Originally Posted by 166486

which will be the appropiate file for me if i have a Touch Pro Verizon CDMA

Unfortunately the appropriate files for the RAPH500 (VZW Touch Pro) are not here. There's a link in the first post to a thread on Connect-UTB that's got some, but they are disappointingly dated. Until someone with a RAPH500 can tear into the kernel source and figure out what's causing the startup to fail, new kernels will not work.

[SP]JESTER · #**1408** (**permalink**) 03-05-2010, 01:30 PM

Quote:

Originally Posted by makkonen

Sorry, having trouble keeping track -- did you ever have data working with Cellular South? i.e. is this a build problem or a network problem (lots of people are having trouble with lots of non-sprint networks)?

If it's the latter, I don't have a good response. Haven't figured out where the authentication process fails (which is what I suspect the problem is).

Newest Post: It did work a LONG time ago back when android was to slow to use, i use to download from market all the time. Cellular South should not have network problems seeing how they have the hero. Maybe the settings are different i havnt got a chance to check my friends hero yet. But cellular south is a #777 dialing out company so im not sure what the problem is. WinMo the 3g is fine, Android connects then works (Sometimes) for a few seconds, then it hangs and eventually will reset the phone. Im not sure whats going on but its driving me over the edge

ha

Also March 5th RootFS just came out. Going to check it out

Creates APN: CDMA Generic
Results:
Without force_cdma=1 / 3G status, still failed. Works for same amount of time then does Arrow down a few times like its downloading but doesnt send anything out. Its like somethings getting hung up.

With force_cdma=1 / Same Result

Cellular South = WTF?

**makkonen** · #**1409** (**permalink**) 03-05-2010, 02:02 PM

force_cdma does nothing for us. It's for the RHOD400/500, which have a cdma and a gsm mode; it tells them to ignore the gsm and identify as cdma.

All cdma carriers I know of use #777 to dial data... the problem might be with requiring a username and password to log in (Sprint does not). But if it worked at some time in the past, I'd imagine that's not it.

Maybe play around with deleting and recreating your APN (instructions in post #2); but that's a shot in the dark. It shouldn't have any effect... but that doesn't mean it won't.

[SP]JESTER · #**1410** (**permalink**) 03-05-2010, 02:30 PM

Quote:

Originally Posted by makkonen

force_cdma does nothing for us. It's for the RHOD400/500, which have a cdma and a gsm mode; it tells them to ignore the gsm and identify as cdma.

All cdma carriers I know of use #777 to dial data... the problem might be with requiring a username and password to log in (Sprint does not). But if it worked at some time in the past, I'd imagine that's not it.

Maybe play around with deleting and recreating your APN (instructions in post #2); but that's a shot in the dark. It shouldn't have any effect... but that doesn't mean it won't.

I have tried the APN recreate since every rootFS and zimage released. When i had a blackberry i use to tether it. The login was phone#@csouth3g.com or something like that. Your password was your ESN number in all caps i beleive. But the thing is these phones dumped that as well as blackberry and went to MM or something like that. It just dont work i guess