Few more details just to get it out there:
-PC is running windows XP, x86 version.
-Freshly installed last night, updated enough to install the Java SDK (7) and Android SDK (12). Android SDK installed back to 2.3.3 from SDK manager & platform tools, but that's about it.
-installed Google chrome browser and adobe reader, HP USB Disk Storage Format Tool, Winimage 8.1, EASEUS 8.0.1, HTC Fastboot drivers, and HTC Sync.
-Tried to make the computer as sterile as possible before trying to program the phone, and hopefully eliminate possible problems in the S-OFF/Root process.
Okay, here's what i've poked around at since my last post:
-Un-installed "busybox installer" using File Expert. (3rd party app uninstall works.)
-Verified Root and Busybox once more with Root Checker, then uninstalled that as well. (/settings/applications/manage applications/ uninstall Root Checker. System uninstall works as well.)
-Power off/on
-Update Google Maps through the Google Market.
-Google Maps icon copied from the app drawer to the left space in the dock bar, right next to the phone shortcut.
-Built in browser moved back to center dock space.
-Settings icon from the app drawer moved to the right side of the dock bar, in the last space next to the app drawer.
-Various app icons spread over the desktops, with a few folders that have app shortcuts in them.
-Have not installed any other new apps yet, and also have not removed any apps the device came with.
-Gps:
+/settings/location services/ use wireless networks (has been off since right after factory reset, have not turned on)
+/settings/location services/ use gps satellites (has been on since the factory reset, have not turned off)
+GPS, Bluetooth, Wireless, and Cellular have been turned on the whole time.
+Added the myTouch Power Control widget to the desktop.
I walked around my neighborhood, on the outskirts of a major city, since shortly after my last post. Ran Google maps (current Google market version) on satellite view for the duration, and messed with the flashlight and turning bluetooth on and off a few times as well.
-GPS refused to lock the first time I ran Google maps.
-Hit the home key so maps was still running in the background, then turned GPS off and back on using the HTC power widget.
-Opened maps again, GPS locked. Prompted me to go to location settings, which I did, and just closed that back out. GPS lost lock again, seemed to be because I went to location settings. Turning off then back on with the widget made it lock again.
-GPS was about as accurate as i'm used to it being on foot. Have yet to test in a vehicle.
-Noticed that maps saved my starred locations from before the factory reset. (Is this linked to my account somehow, or did the settings survive on the device itself?)
So far i'm not seeing any change, positive or negative, with the GPS on this side of rooting.
One of the reasons I purchased this phone was to replace my old and dated standalone GPS unit, so i've been using the GPS abilities of the phone hardcore since I got it.
I'm impressed with the "out of the box" ability of Google maps, navigation, and places working together on the device, and rooting hasn't compromised that software set that I can tell.
I burned up 50% of my battery, to the nearest tenth, as shown in /settings/about phone/battery. This is since my last posting, where I started at full charge.
Up time says 02:32:14 & Awake time says 02:27:30
We really could have had a less cumbersome and more useful battery guage from HTC, i'm pretty disappointed with it's stock implementation.
For the time being, i'm trying to keep the device as close to it's stock + root state as possible, to minimize the amount of variables present in trying to see if it all works right. I can't wait to move on and really streamline the phone for how I want to use it. I'll try to hold off from doing what I want as long as I can to help test out any issues that pop up. But the longer I have the device on this side of Root, the further away from stock i'll get and my test data will become less universal.
I definitely think 4.0.0.9 is the right answer, I know I said before that not having to do a battery pull is far preferable. I really like this device, and it's my first smart phone, so i'd rather not expose it's internals as much as possible.
Also, if anyone sees a way I should be doing something different, or that i'm just doing something the terribly long or unhelpfully redundant way, please point it out to me. '
I'd like to say THANK YOU! to the devs that made this possible. I am extremely impressed with the whole process, it all went through great. The update of CWM right off the bat made it better, and the whole thing runs very well.
Root hasn't caused me any problems, other then the power button issue, but for a beta release of what this is, on a device this new, i'm truly surprised that there isn't more of a mess to clean up.
Your hard work has made my experience with the device much, much better already, and i've barely done anything with my newly granted root access yet. Just knowing that i'm finally in control of something I paid so much money for is comfort enough.
The developers responsible for this rooting process have shown us right here what kind of a level of quality and performance they hold themselves to, and I salute you all.
Thank You! Because it's worth saying again.
... As far as clearing the dalvik cache / cache, it never really hurts but there's probably not much point, either, unless you're altering something or updating a part of the UI/Framework or something where you'd need a fresh cache. It will take longer to boot after clearing the cache and, in my opinion, would most likely end up leaving it the same as before you cleared it... Just my 2 cents, however...
Are you experiencing a problem? The only thing clearing the Dalvik cache would do is fix issues booting (i.e. signature mismatch or such).
Thanks for the replies! Seems you both agree that it wouldn't be necessary, and if someone can come up with a reason why it should be done they'll post it here i'm sure. I just wasn't sure if i'd need to do that to flush out any old settings or anything that would cause problems on this side of rooting.
My experience with Android is rather limited and new, for the most part. My first Android device was a Nook Color, and this phone is my first smart phone.
You can do all this stuff to the Nook without actually overwriting the internal memory, so i've never actually used CWM directly in any flavor before, this is my first brush with it.
I appreciate responding to my query, as I was trying to test out different stuff on the device and didn't have the chance to read up on it. CWM and how to use it properly is the next thing on my required reading list, so I shouldn't have to ask such questions often moving forward.
I just can't get over how smooth the whole thing went down, and want to say Thanks! again - also to the other members of this board who have posted all the instructions and how-to's to get it running.
