• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] 2.08.651.2 ROM updates - post 'em here!

EarlyMon said:
Mine was whacked until I remembered I had profiles set for setCPU that were good for netarchy's kernel - not this one.

So, I was running *slow* until I realized that it had reset things to the minimum for the profiles that made no sense.

Does that apply in your case?
Click to expand...

I wish, I'm still using the stock kernel (hence my questions about Silverneedle over in the other thread), so no SetCPU for me. I've been unable to reproduce the slowdown this morning, so...hoping maybe that just ironed itself out? I can see how that would have messed things up though...heh, so thanks for the idea.

Edit: Argh, spoke too soon. Have it plugged in now, and after scrolling up and down through my app drawer as fast as I can roughly 5 times, the drawer is now very unresponsive. In five attempts to scroll down, two registered nothing, two launched the app where my swipe ended, and one moved down 1 drawer screen.

Really frustrating, thinking of going back to 2.3.3 and just dealing with the icon bug and such. Lock ring is sluggish as well, just took me three tries to get it to follow my finger up to the center of the screen. I'd say it might be something to swap the phone if I was still in my first 30 days (unfortunately not), but I didn't ever have any issue like this in 2.3.3, so...
 
By the way - the stock rooted rom update reset my proxy settings back to the Sprint defaults.

PS to Jackietreehorn - I did a Dalvik wipe from CWM on mine, just force of habit.

Give that a shot - or please mention (if again, sorry) whether you did any wipes.

Also - if you're on CWM 4.0.1.4, go to 4.0.1.5 - everything seemed magically better when I installed that one.
 
EarlyMon said:
By the way - the stock rooted rom update reset my proxy settings back to the Sprint defaults.

PS to Jackietreehorn - I did a Dalvik wipe from CWM on mine, just force of habit.

Give that a shot - or please mention (if again, sorry) whether you did any wipes.

Also - if you're on CWM 4.0.1.4, go to 4.0.1.5 - everything seemed magically better when I installed that one.
Click to expand...

Just to tick these off quick. I wiped both the cache partition and Dalvik in CWM before I flashed, but not after. I'll give it another try, can't hurt anyway.

Those were the only wipes I did, as it's going to be a pain re-setting up everything if I completely wiped, but may try that this weekend as a last ditch effort before just deciding to forgo the update and stick with 2.3.3.

I am on 4.1.0.5, although may not have been if I hadn't read a post by you about the charging problems you had with 4.0.1.4. Thanks for that. :D

Edit - I'm just grasping for anything here, but trying that modified stock kernel couldn't possibly help, could it?
 
It does help, but the problem is still there. The thing that gets me is that it only seems to happen when plugged in. If I unplug, the problem is instantly gone, and I can't reproduce it (until plugged back in).
 
Dumb question but could I install this using Rom Manager?
I'm electing not to because I want to be sure everything works out. Not counting WebOS, I've been rooted for about 2 hours now ;)
 
I think your best bet on this go-round is to just follow the procedure exactly as given earlier in post #9 by Recoil1.

You'll be done in no time. ;)
 
Jackietreehorn said:
It does help, but the problem is still there. The thing that gets me is that it only seems to happen when plugged in. If I unplug, the problem is instantly gone, and I can't reproduce it (until plugged back in).
Click to expand...

I'll bet if you have Process Monitor/System Tuner or SystemPanel and you scroll just the process lists, you're going to find that you're maxing out your CPU.

What could be possibly be configured to run more aggressively during charging?

Hmmmm..... (thinking)

Do you have something like Open Signal Maps set to share all background only when plugged in?

Something like that??...
 
Yep just noticed it, I will delete the 2nd one since you posted already, I had not noticed, sorry


EarlyMon said:
Merged - as the title asked, (please) post 'em here!

Plus - all of the install details on the second one are already in this thread. ;)
Click to expand...
 
EVOlution3 said:
Ok, for the MD5 Checksum I get:

bcea75347f8194eb1c10b2711e98a225

Dumb question, but how do I know if that's good or not? I renamed it exactly PG86IMG.zip. After re-downloading again and renaming it still aborts when I try to install it through clockwork mod recovery.
Click to expand...

It's on the root of your SD card right ?
 
EVOlution3 said:
Just finished reading through that thread. Does anyone know exactly what the carrier spyware that is removed is? It says cIQ, but I have no idea what that is, or what it does..
Click to expand...

I understand it comes in two parts - failure reports, and usage statistics based on what you're running and what it's accessing.

Anyway - that's not exact, just my understanding after reading about it a little only in the last few weeks.

steam374 said:
It's on the root of your SD card right ?
Click to expand...

Wasn't - fixed now.
 
EarlyMon said:
I understand it comes in two parts - failure reports, and usage statistics based on what you're running and what it's accessing.

Anyway - that's not exact, just my understanding after reading about it a little only in the last few weeks.
Click to expand...

So it doesn't disable any of the stock apps or anything then? If not I may went to flash it. Have you tried it yet?
 
EarlyMon said:
I'll bet if you have Process Monitor/System Tuner or SystemPanel and you scroll just the process lists, you're going to find that you're maxing out your CPU.

What could be possibly be configured to run more aggressively during charging?

Hmmmm..... (thinking)

Do you have something like Open Signal Maps set to share all background only when plugged in?

Something like that??...
Click to expand...

Haven't seen anything in SystemPanel, and checked Open Signal Maps, but didn't find anything. The only things that used much CPU were things that I had been using. I'm also only able to reproduce the problem sporadically in my 2.3.3 nandroid restore.

The only other time the touchscreen goes so unresponsive is using the MHL adapter...which would be charging it as well, so at least I have a common theme. Seems to happen with the OEM charger, and with my old Touch Pro 2 charger/microusb cable.
 
Hey all,

I applied 2.08.651.2 over stock after wiping dalvik, then updated the PRI and RPM on my phone and my girlfriend's phone. However, both are having an unsual amount of wake time with the screen off even after restarts, and we use mostly different apps anyway. Is there a way to figure out what's keeping the phone awake?

Thanks
 
I've been investigating that myself and will post findings later today or tomorrow.

The wakeups in my case are staccato like - brief but fairly often.

Battery life is quite decent, but I have seen better.

Edit - interrupted by a call.

SystemPanel is likely your best bet to monitor processes, I'm using Process Monitor/System Tuner to see if it might be something deeper under the hood.

EVOlution3 said:
So it doesn't disable any of the stock apps or anything then? If not I may went to flash it. Have you tried it yet?
Click to expand...

Planning to later today.
 
EarlyMon said:
I've been investigating that myself and will post findings later today or tomorrow.

The wakeups in my case are staccato like - brief but fairly often.

Battery life is quite decent, but I have seen better.
Click to expand...

Yeah the wakeups are very short and uniform. Battery life seemed fairly unaffected but I'm still confused by what keeps waking the phones.
 
You must log in or register to reply here.
Back
Top Bottom