XDAndroid on HTC Touch Pro2

[Mi An]

You can wait to look until it's convenient, I'm in no hurry. In the end, I guess if running winmo in airplane mode before booting doesn't work I'd look at trying one of the two recent decently rated kernels: 10/17 or 9/14.

It's not a solution that is likely to make your life better, but I have seen people switch kernals, and even though there's no particular bug fix in the new one or particular known bug in the old one, it makes their life easier. When you have lots of different contributors to a project working casually, sometimes kinks are harder to track.

whoops, you beat me to it. I don't see an october 3rd kernel in the autobuild, so before you take any advice on switching kernels, might you have at some point installed a special kernel, maybe one of starfox's or someone else's to address some specific problem? I don't want to take you away from a past fix.

[mabbas]

thank you Mi An .. .. that was really helpful

[RickAgresta]

HC, Mi An -- I haven't gone thru the whole thread, so apologies if this has already been discussed...

iirc, HC is using a Sprint-branded TP2, Mi An is using a VZW-branded TP2. Given that what you all are doing ought to get around any carrier-installed software, are there any substantial hardware differences you know of? and how likely is it that the network the phone accesses is part of the problem?

I'm asking, in part, because once my Droid X is out of warranty, I may start tinkering.....

[headcronie]

You can wait to look until it's convenient, I'm in no hurry. In the end, I guess if running winmo in airplane mode before booting doesn't work I'd look at trying one of the two recent decently rated kernels: 10/17 or 9/14.

It's not a solution that is likely to make your life better, but I have seen people switch kernals, and even though there's no particular bug fix in the new one or particular known bug in the old one, it makes their life easier. When you have lots of different contributors to a project working casually, sometimes kinks are harder to track.

whoops, you beat me to it. I don't see an october 3rd kernel in the autobuild, so before you take any advice on switching kernels, might you have at some point installed a special kernel, maybe one of starfox's or someone else's to address some specific problem? I don't want to take you away from a past fix.

Not that I know of, but.... I did have that issue using the default install where I couldn't get incoming calls. I forget what we did to fix that... Likely in this thread, or another of mine where we tackled that issue.

HC, Mi An -- I haven't gone thru the whole thread, so apologies if this has already been discussed...

iirc, HC is using a Sprint-branded TP2, Mi An is using a VZW-branded TP2. Given that what you all are doing ought to get around any carrier-installed software, are there any substantial hardware differences you know of? and how likely is it that the network the phone accesses is part of the problem?

I'm asking, in part, because once my Droid X is out of warranty, I may start tinkering.....

Yes, there are differences. Seems as though HTC caved and provided slightly modified versions of this device to each carrier. Don't know that it would have as much to do with the network, but I really can't say for sure. At the very least, it is known that Sprint has a crazy setup for MMS, vs the other carriers...

[Mi An]

I noticed from the other thread you're overclocking HC. First rule of OC is if you experience instability, dial it back a little (also, don't talk about OC ). It might not be the cause of your reboots, but I'd wager it's the most likely culprit of what we've covered so far. Every piece of silicon is a tiny bit different with slightly different tolerances. Of course, if the slow down is less tolerable than the reboots, maybe it's worth the tradeoff, but it still might be helpful to know for sure if that's where the issue is so you don't waste too much time trying other things. Airplane mode in winmo is easy, might do that anyway. I'd downclock it some, maybe even run it at stock for x days if you have a very good idea of how often you crash. If that amerliorates the problem, then you can slowly clock it up until you reach a sweet spot where you get a tolerable number of reboots at a tolerable speed.

iirc, HC is using a Sprint-branded TP2, Mi An is using a VZW-branded TP2. Given that what you all are doing ought to get around any carrier-installed software, are there any substantial hardware differences you know of? and how likely is it that the network the phone accesses is part of the problem?

I can't really explain the details, but model (mine is rhod500, HC's is rhod400) is an issue for the rhodium, if only because the developers of XDAndroid don't test on all phones equally. In all honesty, the Sprint version tends to be the least stable. If a problem comes up that isn't solved by a visit to the FAQ, it's probably a sprint. It wasn't well represented among developers, and CDMA generally was less used by them, which is why 3.5mm support didn't happen until very recently.

There is a slightly different processor in some models (Same speed, but qualcomm had some patent issue it had to address while new TP2 models were still rolling out and released a reversion to address their litigation), and perhaps some other slight tweaks in the hardware that contribute to the issue. Obviously the radios are different. CDMA has 3.5mm and GSM doesn't.

I don't know much about the droidx, but of course xdandroid is only for the rhodium, hd1, tp1, and the diamonds (i think that's all of them). I assume you're wondering about tinkering with miui or cyanogen? I'd wager you'd have dramatically better stability and support since your device started life with android. And droidx roms will be developed for the droidx exclusively, not for a boatload of differing models and sub-models.

[RickAgresta]

While I haven't seriously read up on how to do what (w.r.t. custom ROMs, rooting, etc.), I have been reading a few of the threads here, and somewhere in the process (probably when the bottom 3/4 of the screen looked like the snow on a color TV) I found the Droidx forums. Not exactly BH, but not too rough-and-tumble, either. Should be interesting, when the time comes

[Tom LaPrise]

I have it running on my T-Mobile TP2 (RHOD100) but without my SIM, just seeing how well it might work as a backup to my Defy. My biggest hiccup is forgetting it's a resistive screen and not having pinch-to-zoom. Otherwise, not bad!

[Mi An]

I doubt I'd be as content with my setup if I'd had a more powerful, less hacky android device first. My experience has mostly improved over time as I've learned to cope with quirks one tweak at a time, but even now, I've been getting a little frustrated with some hangs. I've missed two calls in two days because my system locked up just as it was ringing. That's new. Maybe a little coincidental, or maybe a sign I'm experiencing some degradation.

After I let xdandroid start with a new data image and restore, I might just start overclocking a little. Maybe shoot for 600mhz and see if it helps at all.

[headcronie]

I did some cleanout, and cleanup on my device. Today, no crashes. But, I was also home sick most of the day, and my phone simply sat on my coffee table as I tried to sleep the sickies away.

Tomorrow will be another test, as it's back to the stone castle, with minimal signal at best. I often wonder if my device gets messed up from searching for signal so often...

[headcronie]

I find that the OC is nice, but what really set things working better is setting the governor to 100% all the time. I don't get lockups unless I'm running some crazy app like Angry Birds where there just isn't enough horsepower to try to background the app and get the phone call. No waiting for the processor to ramp up to grab calls, it is just at 100% all the time.