XDAndroid on HTC Touch Pro2

[headcronie]

Got my device a bit more stable. Disabled a bunch of startup apps, froze bluetooth as well as car mode. May try dropping my oc down a bit to see if that helps at all. Tho now I have forgotten what file that is in. Lol.

Sent from my Touch Pro2 using Tapatalk

[Mi An]

startup.txt. I understand the forgetting part though, I just had to regoogle a bunch of stuff I used to know when I started tweaking again.

I haven't finished re-enabling all my widgets since I rebuilt data.img, so I suppose once I do that, I could take a performance hit and lose stability, but so far things have been very pleasant. I'll probably wait until the weekend to lower my underclock to see if I notice the hit, but 650 is nice, doesn't cause me any battery issues -- it might run down quicker, but I've never been caught with an empty tank before my nightly charging, or even close.

In other news, I don't know how closely you watch over at xda, but while froyo development is invisible if present at all, work on gingerbread is agressive and there is actual anticipation of a very soon release of GBX01, which will include the new acoustic code, and should be friendly to the new .39 kernel (which I found to better all around, before it started requiring acoustic code that I didn't want to try to shoehorn into my build -- I prefer the paint-by-numbers releases). Development on the .39 kernel has been constant for most of November as well, I monitor that autobuild and it pops up with a new kernel every few days. I don't know what changes they're making, but they are making a lot of changes.

I'm less interested in NAND, but there has been a lot of activity for a build that isn't based on SD that past two weeks. Up until now, it all looked pretty pre-alpha. Not sure what they'd call their current testing setup, but the activity level of devs and testers is high.

Things have been silent and we have lost a couple of devs, but development ain't over for XDAndroid.

[Mi An]

There is a new gingerbread preview build here. [TESTING] New Acoustic GB 2.3.7 Build - xda-developers

I'll update the first post probably once there is an official build. This is rumored to be as stable as FRX07.1, in that devs have been using and refining it for some time, but the users have all been building it themselves from source. This is the first build with all the new updates released in a nice paint-by-numbers package.

Not sure exactly when I'll get this up and running, but I'll report back. I plan to start completely fresh, no restores from titanium or anything. I also plan to pare down how many programs I use -- my phone will now be game free, among other things, and I'll shift a lot of activity over to my tablet.

[Mi An]

I installed GBX0B today, and it works great. I did start completely fresh, completely cleaned off one sd card (with my highest random writes), installed only applications I need with me (offloading everything else to my tablet). I've made no tweaks of any kind (seems to be less need for them, GBX0B is supposed to be more stable than FRX was), am not currently over-clocking (was up to 650 I think) and don't plan on using adw again, though I might try zeam depending on whether I run into redraw or memory issues again. Also no games or window dressing of any kind. I might even keep just the stock browser.

And as a pleasant bonus, Groove IP works now. Always crashed in FRX. Don't know the delay yet, but so far I'm pretty happy with Syd's new year duds.

The other bonus is you can use a variety of kernel versions out of the box with this build, including .35, .39 and 3.0s. When I briefly used .39 before it forked from the stable FRX line, I found it capable of running my favorite dictionary when .27 kernels wouldn't. The current .39 iteration still doesn't have 3.5mm jack support, and each line has its own quirks and caveats, and I don't know the benefits of each, only that froyo and beyond wasn't really designed to run on .27 kernels, it's just what they started with and shoehorned into the early XDAndroid builds.

[headcronie]

You got my attention with this post. I will be following suit soon as I get home. I am super excited to try this. I have also been offloading my apps to my Fire. I will likely keep my device OC'd to 710mhz. *drool*

Sent from my Touch Pro2 using Tapatalk

[Mi An]

I'm pretty excited for you to try it too! Half the fun is in the sharing. I may well OC again once I've gotten a feel for things. I just had too many tweaks going that were each based on experiences with different versions of the build and earlier kernels etc. I'd forgotten what did what and why I'd needed it.

The whole crash after installs things is supposed to be completely gone now, and a lot of my tweaks were designed to ease strain from that. I suspect having a better sd card will ease some other difficulties, that and generally fewer programs and bloat.

With Groove IP functioning, even if I ever upgrade (or downgrade), I could keep Syd active as a dedicated home line of sorts for wifi calling while still enjoying her night-reading prowess.

[headcronie]

Ok, I think I've studied enough of the overwhelming posts to take the plunge to GB. I'm going to backup my SD, erase it all, and jump in... if all else fails, restore my SD and be on Froyo a bit longer until a straight forward tutorial comes out for GB install...

Wish me luck...

[Mi An]

Good luck!

Install process is the same as before, except for 1) moving all .csv files from \Windows to sd root. then old shoe: 2) extract gb folder to the sd root so you have haret, system.ext zimage modules etc at root. 3) move your rhod400 (you have sprint TP2, right?) startup.txt from the build folder to root then 4) move your old tscalibration file to root 5) profit!

Data.img will be built on the first boot. Sometimes you can bring your old one over, but probably not from froyo -> gb with all the other system changes they made.

I had a minor problem with my audio in alarms on the stock kernel, then I had a weird screen-shut off thing during a call on a .39 kernel (I think it was an error with prox sensor code). I think I have a 3.0 kernel now. Haven't tested it with calls yet. I should bug report the acoustic issue I had, I just don't feel like it ATM. Maybe this weekend.

There are issues (some related to build, some to kernels), so backups are a very good plan, but I still get better responsiveness from this than FRX7.

[headcronie]

This comes with kernel .27 right? Kinda needing audio. I don't need BT. I do need wifi.

This talk of kernels has me lost. I simply haven't kept up on my linux and don't fully understand all of it.

And yes, I'm on Sprint. Aaaaargh posted the csv files for the RHOD400 (Sprint) so I'll just take the lazy route and grab his.

[Mi An]

My audio worked fine in all instances except when my alarm app tried to play an mp3. YMMV. Also I think the build uploaded now has a few tweaks over the one I downloaded. I'm not up to speed on the progress of BT and specifically BT headsets, but it might actually be working in some kernels. I remember reading something about it.

My linuxese isn't so great either. So don't quote me (or mercilessly mock me) but, the kernel is linux itself and the closely associated modules are (perhaps among other things) drivers to interact with the hardware. Android is an environment that stands between the user and linux -- more than just a GUI (in addition to the shell, it has its own security procedures, apps are mostly java, but can be native code too, but are limited by Android restrictions), but it isn't an OS in and of itself.

So when you click "play" in an mp3 player, the player asks Android to help it access the file and output the audio, and then Android reaches out to the core of linux, the kernel and modules, to actually operate your device and get the output out there (or recieve the touchscreen input, etc). The userland files, or Android can be operating just fine and you can still not hear what's happening if the linux drivers aren't working. Or the drivers can be perfect and you don't hear the audio because it's improperly routed inside Android and it never makes it to the speakers in the first place.