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

[arrrghhh]

Originally Posted by xgator

Formatted the SD card and copied 2010-05-11 andboot however phone/display shuts off for more than 15 minutes have to pull the battery out to restart the phone what can be the issue on the Sprint touch pro2 WM6.5 handset?

This is the thread for the RAPH800. I know for a fact there's a TP2 thread on Android... Heck, you TP2 guys have your own Android section on PPCG!

But, if it doesn't boot on first try do what I (and many others) have been endlessly suggesting. I'm just going to assume from your description that it's in a boot loop... Delete the data.img, try and boot again. If that doesn't work, boot a build from 3.31 or older, boot fully, reboot to WinMo and copy that data.img over to your newer build. Try again.

And look/think/search before you post please.

[88fingerslukee]

Originally Posted by dcd

re: gps, im also pretty sure that the raph800 isn't outputting nmea data like others thanks to an nv value that could be changed, but ive been down that road good luck finding it.

This was confirmed by Phh over at the XDAndroid thread. It's too bad that it isn't easier to mess with. It makes me sad knowing that you've worked on it with no results because there aren't that many more CDMA guys out there.

Sigh...why are always relegated to back-burner status? I'm seriously considering buying an unlocked GSM phone (the Milestone anybody?) and moving it to Bell. If only the EVO had a keyboard.

Can we push the HTC Vision for an earlier release?

[ChaosTheory]

So I have been using XDAndroid for a while now, currently trying to upgrade to 2.1 (21AOSP030510 release) but having a heck of a time doing so, particularly with audio through the USB port. So far these are my results:

Using 2.1 package as is gives me an endless boot, as does updating the zImage, rootfs, modules, intramfs files.

Installing the 2.0 package works (with all current files), and USB sound works.

If I copy the 2.1 package over the installed 2.0 package, it boots, but no USB sound. I can acheive similar results by putting just the data.img file into the 2.1 and the installing it.

To clarify what the USB sound is doing, I can start playing a song and hear it over the phone speaker, if I plug in the USB (earbuds or 3mm jack adapter) the sound gets quiter (indicating that the jack is being detected at least) but it is still coming out of the phone speaker, and no sound from the earbuds. If I pull the jack out it pauses, as normal.

So my questions are:

Anyway to fix the audio in 2.1, or is it a known issue?

Anyone know why the 2.1 package alone loops endlessly?

I have seen various things mentioning GPS working/not working reasons etc. To my knowledge the newest (2.1) release has GPS working, just not on the RAPH800, and the this is due to a hard to access/modify file. Is that about right? If so, is the GPS something that I shouldn't expect anytime soon? Not to worried about it, as I hardly ever use it anyway, just curious

On a side note, any one know what the status of getting the camera is? Anyone working on it, or are other things priority? Just trying to keep up on things I wish I had the time to contribute, but between family, work, and home I barely have time to do what little I do accomplish lol.

Thanks for any input, and many thanks to all those who are working on this project!

[arrrghhh]

I'll try to answer you questions, but keep in mind this is all experimental... there were some regressions.

I think usb audio is borked in 2.1. Not positive, but if you need it stick with 2.0.1... or WinMo, c'mon.

The 2.1 package alone loops endlessly because of an issue with building the data.img. Not sure why how or for what reason, that's just the conclusion that many have come to. I haven't seen any actual dev comment on it tho.

GPS is not working on the RAPH800 and a few other devices because of how the data is reported - devices that are working provide raw NMEA data, which is a standard. The devices that aren't working, like our 800's, don't provide this data and instead provide a different type of stream that they have to decipher before it can be passed onto Android.

Camera has been worked on from the beginning, not sure what you mean there. It may eventually work, as far as I know it's been in an almost workable state for a long time now, they're just missing a few key pieces to bring it all together. I could be totally off-base on that last comment, but I know that they have been working on it for a looooong time. Honestly, that should be their last priority.

I'd rather see a NAND and good battery life before the camera. It's all part of the puzzle, but it's a relatively minor piece in my eyes. Battery life is getting there, it's much better with these new builds. NAND, they still have a few pieces that are initiated thru WinMo, one of them being 2D (that's right, 2D. Not 3D...) From phh "But we rely on wimo to init usb, 2D, some clocks and I think that's pretty much it."

I hope that answered your questions in your gigantor post :P

[ChaosTheory]

Thanks arrrghh! And I apologize for the large post, don't get on here much so try to get it all out of the way when I do.

I definitely agree on battery life, I usually switch to WinMo when I will be out for a while just to ensure I will actually have a phone if I need it lol.

I realize the camera isn't that big of a deal, but part of the reason I bought a camera phone for the quick access to a camera if I need it :P (and with a little one it can come in handy lol)

From my understanding NAND would allow us to flash to XDAndroid just like any other ROM, right? Care to explain what it stands for and a little bit about it so I can add it to my glossary?

Thanks again! Guess I will have to decide if I want to run WinMo for audio (I listen to it on my drive to and from work) or revert to 2.0.1. Can anyone point out the differences between the two that could influence my decision?

[arrrghhh]

NAND is just a fancy word for flash memory... In a sense. See this Wikipedia article if you want to know more.

Yes, it would mean we could flash Android to our phones like any other ROM. It's a little ways off, but hopefully not far.

2.1 vs. 2.0.1... there's some differences, mostly under the hood. You can run 2.0.1 without a whole lot of noticeable differences. Can't think of all of 'em off the top of my head tho.

[shiverz26]

Seems Like the longer i run android the better it works, Ive had it up and running since last Saturday and have the little dual boot app so havent been into winmo since then, at first was getting like 2-3 hours of battery life but now have gotten up to 6 without dying.... the battery in these phones sucked in winmo as well so i cant complain and more and more apps seem to be working as well... even some that used to force close like google street view... thanks for ya'lls work on this so far, i hope the camera does eventually get worked out but its worth it not to have it to use Droid just my $0.02

[bfann21]

Have an issue that I searched high and low for. I imagine its most likely on the front page, but I seriously read through it like 12 times. I boot android and the first time it made me calibrate my screen, all was well and good, it gets out of the linux kernal and goes to the red blue yellow green dots creating an X animation and then sits there and loops. Anyone run into this? Suggestions? I let it sit for at least 15 minutes one of the times, have tried to reboot. Nothing working.

[Kevets]

Yeah, it's been answered on every page. Look at http://forum.ppcgeeks.com/showpost.p...postcount=2407

[hamagc]

actually i don't think much is on the front page for this but it's all throughout the thread.

in short, update zimage and rootfs, delete current data.img and try again. if still having a problem, use an older package (3/31) and update the zimage, rootfs, and system.sqsh.

for more info, do a search in this thread for bootloop or x loop.