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

[Flak]

I have a sprint touch pro, haven't been able to get any AIO build after 3-31-2010 to work. 3-31-2010 seems to work ok. But when I try a new AIO build, whether it's on a fresh SD card or laid on top of 3-31-2010 one of two things happen:

Looping X (have let it sit for 30mins), deleting the data.img file lets the phone get as far as the google account part but then touch screen goes unresponsive and I start getting process failed to start/process hung errors.

Loads to desktop but touchscreen is completely unresponsive then the tp goes to sleep or standby until I pull the battery

[arrrghhh]

Originally Posted by Flak

I have a sprint touch pro, haven't been able to get any AIO build after 3-31-2010 to work. 3-31-2010 seems to work ok. But when I try a new AIO build, whether it's on a fresh SD card or laid on top of 3-31-2010 one of two things happen:

Looping X (have let it sit for 30mins), deleting the data.img file lets the phone get as far as the google account part but then touch screen goes unresponsive and I start getting process failed to start/process hung errors.

Loads to desktop but touchscreen is completely unresponsive then the tp goes to sleep or standby until I pull the battery

Well it sounds like you didn't go thru calibration.

You were correct in the diagnosis of the looping X problem, now if you have a ts-calibration file at the root of the SD (or /andboot, where haret.exe is) delete that and boot again. Watch for the calibration screen, it'll have little 4-square boxes. It may time out if you don't do it in time, which may very well be the cause of your issue. Do your best to hit the middle, and if you do it once well you can save that ts-calibration file and re-use it again and again. Hope that helps.

[sfhub]

Anybody experiment with the SUPL AGPS server settings?

I changed it to the one Sprint phones usually use and now I sometimes get 8 second GPS locks. Mostly 10-30 seconds. However sometimes it will be 30-90 seconds. With the default settings it always seemed like it took a long time to get lock, probably 60+ seconds, but I didn't try to isolate why. It might have been as simple as needing a data connection open first before starting GPS. I recall there might have been a bug in the callback where the Qualcomm stuff asks for the data connection to be opened.

The setting is in

/system/etc/gps.conf

and it gets copied into

/data/etc/gps.conf

at boot time, so you only need to change it once at the source (and reboot)

This is what I changed

SUPL_HOST=68.28.31.49
SUPL_PORT=4503

This is what Sprint phones usually have it set to (including Touch Pro stock WM ROM) I wouldn't experiment using these settings if you are on a different carrier.

Verizon probably has their on SUPL server settings which you could look up if you were interested.

EDIT:
There is a list of other SUPL AGPS server settings here:
http://forum.ppcgeeks.com/showpost.p...11&postcount=2
This from this 88fingerslukee post
http://forum.ppcgeeks.com/showthread...06#post1811306

[makkonen]

Thanks sfhub -- looks interesting. I'll check it out once I get around to GPS stuff.

(and you probably only need to change it at /data/etc/gps.conf, since the files under /system are read only... I think /data/etc might "mount --bind" at /system/etc to give the appearance that the files are there. Not totally sure.)

[mrkite38]

Originally Posted by sfhub

Anybody experiment with the SUPL AGPS server settings?

I changed it to the one Sprint phones usually use and now I sometimes get 8 second GPS locks. Mostly 10-30 seconds. However sometimes it will be 30-90 seconds. With the default settings it always seemed like it took a long time to get lock, probably 60+ seconds, but I didn't try to isolate why. It might have been as simple as needing a data connection open first before starting GPS. I recall there might have been a bug in the callback where the Qualcomm stuff asks for the data connection to be opened.

The setting is in

/system/etc/gps.conf

and it gets copied into

/data/etc/gps.conf

at boot time, so you only need to change it once at the source (and reboot)

This is what I changed

SUPL_HOST=68.28.31.49
SUPL_PORT=4503

This is what Sprint phones usually have it set to (including Touch Pro stock WM ROM) I wouldn't experiment using these settings if you are on a different carrier.

Verizon probably has their on SUPL server settings which you could look up if you were interested.

VZW'ers, try:
host: 216.198.139.92
port: 8889

[x4osw0n]

I downloaded zedge from the marketplace; good selections, and does ringtones too, though only non-copyright ones. worked perfectly. In fact almost every app I have gotten from the marketplace works, though everything is a bit slow at the moment. May try the overclock app mentioned in this thread.

[OvermindDL1]

EDIT: Ignore this post, it spontanously started working...

[hamagc]

you have a couple of options. there is a work-around for the boot loop, referenced on page one.

also there should be an updating coming soon (maybe today, maybe not) that i believe will fix the bootloop issue for most. we shall see.

[arrrghhh]

Originally Posted by x4osw0n

I downloaded zedge from the marketplace; good selections, and does ringtones too, though only non-copyright ones. worked perfectly. In fact almost every app I have gotten from the marketplace works, though everything is a bit slow at the moment. May try the overclock app mentioned in this thread.

Yea, I'm sure as you're aware the RAM situation on the RAPH500 is abysmal... Probably the reason for the sluggishness.

[arrrghhh]

Originally Posted by OvermindDL1

EDIT: Ignore this post, it spontanously started working...

I was going to say, delete your data.img, NOT the entire andboot folder. Hopefully there's a fix in the pipe, like hamagc said.