View Single Post
  #455 (permalink)  
Old 03-14-2011, 03:13 PM
fishingmedic's Avatar
fishingmedic
VIP Member
Offline
Location: Patriot Nation
 
Join Date: Apr 2009
Posts: 2,368
Reputation: 5305
fishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the communityfishingmedic is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] Updated 3/11/11 New Kernel - TONS of changes!!

Quote:
Originally Posted by arrrghhh View Post
Bleh...

Might ask you to start over clean, formatted SD card, whole schebang.

You can feel free to backup all your stuffs, but for testing just to make sure you can get a build running again, starting clean might be the best method.

If you want, start with a new data.img, that's basically starting clean from a user perspective.

I don't understand how it could persist after a reboot like that... data.img seems suspect.
Deleted the data.img and set it all up again, reduced OC too but still acting funky. Just had another sod, blinking green light, but KB lights never lit up, couldn't get it to wake at all, even after just leaving it for a few minutes. Rebooted to winmo and that's it. Now if that's happening at home I could just hook it up to adb and take a look and see what it's doing correct? Not near my computers right now so can't, but I'm gonna try later at home and see what happens.

Quote:
Originally Posted by ndno View Post
It's running good for me again I uninstalled SetCpu, I wondered if that was the culprit (maybe screwing up the system clock when it went to sleep - I had a profile to clock it at 122mhz when it went to sleep). Anyways, I installed SetCpu again but this time, I only have a couple profiles under SetCpu and I'm not creating one for when my TP2 goes to sleep, gonna let the system do its own thing; so far so good, run on 5 hours now... smooth as butter! Good thing is that I haven't seen any SOD lately... Insta sleep/wake works great!

Is it just me or does it seem like charging under Android is very very slow?
Yeah I think that Set CPU app may have caused some issues, my phone was acting funky with it on so I removed it without changing anything else and seemed to stabilize.
Reply With Quote