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

[Coolin72]

Cant get my "exchange" company email on the new build. anyone else having issues? and also the push to talk app isnt working. has anyone tried that yet?

[JFettig]

Does anyone know how to retrieve or backup info for re-installing android? My android crapped out on me as i was trying to retrieve a new text message and I'd like to preserve that if I can. It won't boot anymore.

Thanks,
Jon

[makkonen]

if you don't mind getting your hands dirty, data.img is just an ext2 partition in a file. you can mount it as a loop device either from within android or from a suitable linux computer.

su
mkdir -p /mnt/data
mount -o loop /sdcard/andboot/data.img.old /mnt/data

I don't know if these precise commands work, but that's the idea.

Once you've done that, you've got to find where the SMSes are stored... unfortunately, I don't know where that is. Almost surely somewhere under /data/data (which'd be /mnt/data/data if you did it the way I typed up there). Titanium Backup suggests that it's in Dialer settings, but I haven't got my phone nearby to check on that.

That's as far as I can lead you. Good luck.

[JFettig]

Thanks,

I'm actually going to try to reformat the card and drop the data image back on and see what happens.

BTW, I haven't been able to run android for more than a few days at a time before the whole system crashes and it won't boot anymore. I'm running the XDANDROID.2.2.AOSP.29.7.10.RC2.1 package right now, it runs better than any other package until I rapidly decrease the volume or have these other problems(misc). One of the earlier releases that you released on the front page I was able to run for a few weeks before it wouldn't boot anymore.

Jon

[hamagc]

Ok makk I need your help.

Still batteling with mms. I think our ril may be ok. Playing with apks I was able to send myself an mms and caused com.android.mms to crash. This means its coming in through the ril but nothing is telling our regular mms.apk to get the msg but is on a modified one. The modified one crashes when opened period. Modified one aparntly only spoofed a bb8800 useragent.

I used a patched apk for a hero from 2.1. That's the one that crashed. 2.2 ones did nothing special.

Any ideas on what next? I still have a few things to bang my head on but this is the most progress I've made so far lol. Could this be a useragent thing?

Sent from my MSM using Tapatalk

[makkonen]

Hmm. at first blush... I have absolutely no clue.

On slight further consideration... are we even sure mms even works on a touch pro? I've heard it might not... Something to do with accounts? TP2 does, but something needs to be set on the backend, I think.

In WinMo, do you get mms via that weird picturemail app (which I think is just a clever web frontend) or something else?

[hamagc]

It works fine in winmo. Via stock apps or arcsoft. Vogue gets weblinks (that's why their mms works fine) but we have true mms. I've spoken with sprint about getting weblink mms but was told it is not something they can change on their end. I believe it is automatically setup in provisioning and activation with phone that don't have native mms.

Sent from my MSM using Tapatalk

[hamagc]

Also would you have any interest in a mostly working tp? Power button doesn't work but it will boot xdandroid and may be good for dev.

Sent from my MSM using Tapatalk

[makkonen]

Ah, ok. Good to know that the backend for MMS does work. As far as whether the ril is actually handling it correctly is still up in the air, I'd say. The fact that it gets far enough even to crash com.android.mms is a good sign -- means that whatever's coming in as an mms is at least getting recognized, though it might be getting mangled.

My next thought for where to look would be to load up the mms.apk that's crashing on receipt, send an mms, and check logcat as it comes in. See where things are coming apart. Then, if possible, compare that to a logcat output of a phone that has working mms.

I don't know if that will tell anything of interest, but it's all I can think of, in absence of real knowledge of the protocols.

I glanced through the ril code, and there's a lot in there to deal with SMS, but essentially nothing on MMS -- I'm just not knowledgeable enough to know if that's to be expected or not. I assume the parsing of the MIME enclosure is done by the mms app, but I'm not even sure of that.

I'm pretty sure nothing using our RIL has working MMS (gsm or cdma). Does anyone know if any network other than Sprint has Vogues that receive real MMS (instead of links)? I'm just wondering if anyone from the community android projects has tackled mms encoding.


As far as a mostly working TP, I can't really think of anything I would do with it. I guess turning it on and off is less annoying in xdandroid (once you enable navi.wake), which is a plus; do you have to reboot it to get it to come on if the screen goes off in WinMo?

If it's just going to sit in a drawer or go in the trash, I'll take it; but, really, getting a few bucks off craigslist for it is probably a more sensible choice than sending it my way. The meager development work I had done has pretty much stopped completely since I picked up an Evo, and I sold off my Touch Pro and my Touch Pro2.

Still got a diamond and a raph500, though. And still want to take a look at the memory layout of the raph500 a bit more. It'd be nice to get that extra 64mb and make it feel less like it's been dipped in molasses. Unfortunately, the last time I tried, all I got for my trouble were lots of early crashes.

[TOOL1075]

I just wanted to take time to thank those of you involved with the development of this Android port to the Touch Pro platform - good work.

I have a Sprint Touch Pro.

I put the files onto my storage card this weekend, and ran the Haret executable - and all went well. It seemed to freeze on the Android animation, so I deleted data.img and plugged in the phone to power, and tried again - and then it worked.

I've been running it all weekend - it's good. I have it set up to get my Outlook push-mail (only a month's worth though.... that kind of sucks), as well as my Gmail.

I've had a few stability problems, here and there. The main problem I have is sometimes the buttons (except for the power button) on the phone start to act ONLY like the "hang-up" button (which is subsequently the "sleep" button).

So, usually,

Home = menu or whatever
Phone = call
Back = back
Hang-up Phone = sleep
Power button = wake-up/home screen

but now (and more often than not after using for a little bit):

Home = nothing - seems to try to select items
Phone = nothing - seems to try to select items
Back = sleep
Hang-up Phone = sleep
Power button = wake-up/home screen

Also, it does not illuminate when I touch those buttons when it is in this condition (the capacitive led response ceases to work)

I'm assuming it has something to do with the way the OS communicates with that part of the hardware (the capacitive buttons)

Any ideas? Anybody know how to "reset" the button assignments without a reboot?

Thanks again for all your work!