Hi,
From some days ago, my S200 started restarting itself sometimes (like once or twice a day)..
I thought it was something to do with the ROM but 3 days ago I woke up and the phone was completely turned off. I tried powering it on with the Power On button but nothing happened.. Tried Soft reseting and hard reseting and nothing.. Removed the battery for 10 minutes and then it powered on but the screen started flickering (horizontally).
Then I saw at BatteryStatus that the CPU speed was jumping from 195 MHz to 91 and 52, randomly (195, 52, 91, 52, 195, 91..).
I searched the net and did found almost nothing, just a forum where they say that 195 Mhz is the normal mode, 91 Mhz big sleep mode and 52 Mhz deep sleep mode.
Even if I overclock it with BatteryStatus, it doesn't maintain the speed, and slows down to 195/91/52.. (Even with speeds below 195 MHz it goes to 195).
Other think I realized yesterday was the battery discharges much faster, and I think when the phone is at Standby Mode keeps discharging the battery as if it was fully On (It never discharged me the battery in one day..).
I plugged it in yesterday night and today morning the phone was charged (green light always on) and I pressed the button to power on the screen, and nothing.. Removed the power cord and the green light kept on. Reinserted the battery (the light gone off) and tried to turn it on, and nothing.. Resets did nothing, it was completely dead. Took the battery off and after one hour put it back, and it powered on and it's working right now (with screen flickering and that CPU changes..).
I think the problem is on the CPU.. Reflashed it yesterday (Aserg 3.3.13 ROM) just to be sure it wasn't from the ROM (although I used that ROM without any problems before).
One more thing I remembered, the WiFi isn't working (from some days ago..). It doesn't turn on most of the time, and when it does, it doesn't detect any network.
Sorry for this long post, any help appreciated.
Thanks in advance
when the cpu clock gets down, it could be the cpuscaler feature of batterystatus. disable it or adjust it!
my prophet's screen also flickers if i set the cpu speed below 169mhz. so i made this as the minimal clock of cpuscaler.
disable the cpu scaler and set stepwise locker clocks than 195mhz. then test each step for screen flickering. lowest cpu lock where the flickering doesn't happen, should be you lowest cpu scaler value.
CpuScaler is disabled.. Even if enabled and I set the Min. to 195 for example, it doesn't "fix" and slows down. It's like the CPU doesn't respond to BatteryStatus..
(Yesterday before reflashing I tried uninstalling BatteryStatus but it was the same..)
By the way, it flickers when booting too, on Qtek screen, but it doesn't flick when connected to the pc (and the cpu speed keeps constant.. 195 MHz). If I overclock it keeps the same speed too! If I remove the cable, it slows down immediately to 195 and start flickering
I'm starting to think the problem is the battery.. I hope it is, instead of the CPU
But it's only when connected to the PC, I tried it connected to the wall charger but it does flick and doesn't fix the CPU clock...
Battery now goes from 100% to 10% in 7 hours in standby
I will try with another battery tomorrow to check if the problem persists..
I've tried another battery and I do have the same problems..
Now it doesn't detect usb connection (wall charger or pc charge or sync)
What the hell is happening with it?
You updated new rom or reset machine try again !
It's charging now.. :S So weird..
I'll let it charge and then I'll change the rom..
Update:
Flashed with "ruu_prophet_220734_2207114_026121_qtek_wwe_ship" but the same problems occur..
The cpu still have the same problem.. (195 MHz, 91, 52...)
Anyone with the same problem?
but you know this becouse you intalled batterystatus plug in, if not correctly configured, it is the same. right?
good luck!
I guess your device is permanently damaged, I hope you're elligible to warranty..
One last thing you'd want to try, keep your device open (at least battery & sim off) & shutdown for at least a week, then...... try again
I guess it is permanently damaged too. I'll try to sell it to spare parts.. Thanks
So this problem has been going on for the past 2 days, and its very perplexing. Any help would be much appreciated.
For whatever reason, my phone has stopped automatically turning off after X minutes.
I'm talking about when you go into Start, Settings, System tab. There's options for automatically turning off the backlight after X amount of minutes (one option for when its using battery, another when its on AC Power).
The backlight auto off works just fine. After 1 minute, the screen goes semi-dark, but not blank.
What's not working is the Power setting, where you go to Power, then Advanced, and then both battery power and external power, you can have the device turn off if not used for X minutes. I've tried 1, 2 5, 10, and none of them seem to work.
The device only turns off the backlight, but then remains on, draining the battery at incredible speed. I need to manually keep hitting the hardware power button on the right side of the device to get the screen to go off completely.
Any help, ideas, suggestions? Thanks!
rajuabju said:
So this problem has been going on for the past 2 days, and its very perplexing. Any help would be much appreciated.
For whatever reason, my phone has stopped automatically turning off after X minutes.
I'm talking about when you go into Start, Settings, System tab. There's options for automatically turning off the backlight after X amount of minutes (one option for when its using battery, another when its on AC Power).
The backlight auto off works just fine. After 1 minute, the screen goes semi-dark, but not blank.
What's not working is the Power setting, where you go to Power, then Advanced, and then both battery power and external power, you can have the device turn off if not used for X minutes. I've tried 1, 2 5, 10, and none of them seem to work.
The device only turns off the backlight, but then remains on, draining the battery at incredible speed. I need to manually keep hitting the hardware power button on the right side of the device to get the screen to go off completely.
Any help, ideas, suggestions? Thanks!
Click to expand...
Click to collapse
Are you running custom or stock rom, have you thought about possibly doing a hard reset. besides adjusting those settings have you tried something else. Was anything instlled just before this started if so what....I know thats alot of questions but it might help..
I thought dimming the screen was the manufacturers idea of turning off....mine has done that since day one. I too have tried everything and thought that was normal.
Hmmm, Mine dimms then turns off IE: 1 Min to turn off I'd say 30 Seconds it dimms and 30 seconds later it turns off.....
I'm using a stock ROM, havent installed anything "new" in the past few days. I normally run a bunch of various programs though, but I wasnt having this issue before.
I did a hard reset. Everything was fine. Then I ran a backup and it reinstalled all my programs/files/settings, and issue returned.
So its obviously being caused by oen of the programs I use, I just dont know which I guess.
Edit- Upon further investigation, I *think* its Palringo. I removed it completely, and everything seems to be ok again
This thread is ONLY for people who already bricked..please post your information here in this format to help developers iron out the issue.
If you wish to discuss things use this thread:
http://forum.xda-developers.com/showthread.php?t=1042552
The purpose of the current thread is just so developers don't have to go through 20 pages to get information and organize the information.
----
Here is the template for me: (please try to follow it, if you can include more info then I did that would be great.include as much info as you can)
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling + On
Sd: stock
UV: BFQ - 1000-75,800-75,600-75,400-75,200-75,100-75
Programs installed: Stock ACS with some games
Programs running: Voltage Control?
Failure on: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? YES
Previous freezes from UV: Yes
Battery Life on failure: 30-35%?
Strange behaviors list:
1) When I was playing with UV, I noticed a weird thing that when I applied settings temporarily there was no freezes but when I applied it to boot there was a freeze as soon as I applied it.
2) I got a config where my phone didn't freeze, and battery life was good..I didn't use phone much but while of it went 7 hours only using like 3-5% battery...then when I left it over night to wake up and my phone was dead..I turned it back on via pulling the battery and notice battery life went from 91% to 45%
3) Same UVs with CFQ that I used for Genocide caused freezes, I eventually got good working on -75 all and no freezes for 24 hours+
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling + off
Sd: stock
UV: BFQ - 1000-25,800-50,600-50,400-50,200-25,100-0
Programs installed: Stock ACS with some games
Programs running: Pimp my CPU and set CPU and browser?
Failure on: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? no phone froze
Previous freezes from UV: Yes
Battery Life on failure: 40-45%?
Strange behaviors list:
Well I tried undervolting and my phone would only really go to 50 without freezes.
The phone bricked when I was browsing the web (google?) and it just froze, I tried to do the hard reboot but it didn't work so I did a battery pull... I put the battery back in and try to power it on and nothing lights up at all.
Later that night I went to the sprint store and tried to get it replaced and the "techinision" was there and the guy just tried to put a new battery in and charge it which obviously I already tried those... Now I can't bring it until Friday and hopefully they can't tell I was the problem or my tep won't cover it.
Rom: MidNight ROM v5.2
Kernel: Vision 1.2
FS: EXT4 + Journaling ON
Sd: Stock
UV: CFQ - 1000-25,800-25,600-25,400-50,200-50
Programs installed: Google Applications (Voice, Reader, Authenticator, etc.) , psx4droid, Facebook, Firefox
Programs running: VC service
Failure on: Reboot via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? NO
Previous freezes from UV: Yes
Battery Life on failure: ~88%
Strange behaviors list:
When I first flashed 1.2 the other day, I did a reboot to check bootup behavior at UV settings (mild as they were) and had a slight problem getting it to turn on. I took the battery out and hit power and nothing happened. Hit it a few more times, same thing. I did it again and this time it worked. I didn't really think much of it. I haven't touched a setting since then and was reading about people having bricked phones, so I gave it a shot - expecting about the same results. This time, nothing I do will get it back on. I'd originally flashed Vision because I was experiencing random hangs with SRF + Twilightzone 1.1. I've been running without hangups and was pretty pleased with performance. I'm going to try an extended battery removal, and hope that I can get it to download mode so that I can Odin to stock and go from there. But as of now... just a black screen staring back at me. Also, as a side note, I don't have the magic reset button - just a plastic filler that looks like a button. Besides, even if it is a ground plate instead of a physical button, it didn't fix the issue.
gTen said:
This thread is ONLY for people who already bricked..please post your information here in this format to help developers iron out the issue.
If you wish to discuss things use this thread:
http://forum.xda-developers.com/showthread.php?t=1042552
The purpose of the current thread is just so developers don't have to go through 20 pages to get information and organize the information.
----
Here is the template for me: (please try to follow it, if you can include more info then I did that would be great.include as much info as you can)
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling + On
Sd: stock
UV: BFQ - 1000-75,800-75,600-75,400-75,200-75,100-75
Programs installed: Stock ACS with some games
Programs running: Voltage Control?
Failure on: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? YES
Previous freezes from UV: Yes
Battery Life on failure: 30-35%?
Strange behaviors list:
1) When I was playing with UV, I noticed a weird thing that when I applied settings temporarily there was no freezes but when I applied it to boot there was a freeze as soon as I applied it.
2) I got a config where my phone didn't freeze, and battery life was good..I didn't use phone much but while of it went 7 hours only using like 3-5% battery...then when I left it over night to wake up and my phone was dead..I turned it back on via pulling the battery and notice battery life went from 91% to 45%
3) Same UVs with CFQ that I used for Genocide caused freezes, I eventually got good working on -75 all and no freezes for 24 hours+
Click to expand...
Click to collapse
Some things I need clarification on, first of all your phone still powers on correct? I see you said issue with recovery and that you had problems powering off via menu.
Some good questions to answer that will be helpful are as follows:
Are you able to get into download mode?
Do you see the Samsung logo if it is freezing on boot?
Does it power on at all?
If so is it intermittent?
Are you able to get into recovery?
If you ARE able to get into download mode or recovery let me know I may have a kernel that you can flash or install that may resolve your issue but only offering it to those that phones are affected but not completely bricked.
dyehya said:
Some things I need clarification on, first of all your phone still powers on correct? I see you said issue with recovery and that you had problems powering off via menu.
Some good questions to answer that will be helpful are as follows:
Are you able to get into download mode?
Do you see the Samsung logo if it is freezing on boot?
Does it power on at all?
If so is it intermittent?
Are you able to get into recovery?
If you ARE able to get into download mode or recovery let me know I may have a kernel that you can flash or install that may resolve your issue but only offering it to those that phones are affected but not completely bricked.
Click to expand...
Click to collapse
This thread is for people who are completely bricked...in this case its completely bricked...the only thing that was noticed was that the phone somehow does power on in some way or form as if you press the power button and leave the phone on for a few hours it will get a little warm...but there is 0 way to connect to it or see anything as screen is dead and usb is dead.
Anyways this is for the discussion section...this is purely for gathering data.
This was posted in the discussions thread so I am quoting it here so its organized:
autocon said:
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling + On
Sd: stock
UV: BFQ - 1000-25,800-25,600-25,400-25,200-0
Programs installed: Stock ACS with some games
Programs running: PMC
Failure on: 3 finger salute
Previous freezes from UV: No
Battery Life on failure: ~80%
Strange behaviors list:
1) Phone was running slow so was gonna reboot into CWM and flash the default ACS Twilight kernel again, but it wouldn't turn back on. Tried taking battery out and going into download mode, but it wouldn't do anything. Tried Mystery's suggestion about the hardware reset but that didn't work either. Got a replacement under warranty from Sprint
Before this, I had been running stock ACS for over a month, grabbed the 1.1 when it came out, had no problems. 2 days ago switched to the Vision kernel and everything seemed fine, until the slowdowns. Rebooted through Reboot option on power menu, everything was fine. Slowdowns again, rebooted again. 3rd time is when it bricked.
I'm not gonna blame the devs for this, we all knew going in that we could screw up our phones if we weren't careful. My phone was one that couldn't go to 1.4 at all, on any kernel I tried. It also didn't like 100mhz. I know I had one of the weaker phones. Heck, I've had lockups on Twilight at 1.3 on Angry Birds before. Dunno if the weaker hardware had any impact on the brick or not.
Click to expand...
Click to collapse
dyehya said:
Some things I need clarification on, first of all your phone still powers on correct? I see you said issue with recovery and that you had problems powering off via menu.
Some good questions to answer that will be helpful are as follows:
Are you able to get into download mode?
Do you see the Samsung logo if it is freezing on boot?
Does it power on at all?
If so is it intermittent?
Are you able to get into recovery?
If you ARE able to get into download mode or recovery let me know I may have a kernel that you can flash or install that may resolve your issue but only offering it to those that phones are affected but not completely bricked.
Click to expand...
Click to collapse
No
No
No
No
No
...She's a brick...house!
Rom: SRF 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling off
Sd: stock
UV: BFQ - 1300 -0, 1200 -0, 1000-50,800-50, 400-100,200-100,100-150
Programs installed: Random.
Programs running: Voltage Control
Failure on: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? No
Previous freezes from UV: Yes
Battery Life on failure: ?
Strange behaviors list:
1) Had to Odin to stock few days prior as internal memory was showing 0MB. Once this was done, manually installed rom+kernel, titanium backup for apps.
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling off
Sd: stock
UV: 200-1000
Programs installed: Stock ACS with some games
Programs running: SetCPU
Failure on: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? YES
Previous freezes from UV: Yes
Battery Life on failure: 89%
Strange behaviors list: Sometimes locks up on wakeup
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling On Writeback Journaling No barriers other flags I set myself
Sd: stock
UV: none
Programs installed: Pretty much stripped, twcrushdlauncher, linpack and smartbench... terminal emulator, xda, mybackup root, ghost commander and notepad
Programs running: twcrushdlauncher
Failure on: reboot via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? No
Previous freezes from UV: no
Battery Life on failure: 80ish
Strange behaviors list: Started acting like it was out of ram, I have custom transition animations installed and they were lagging really bad, so I decided to reboot...
I am able to get my phone to boot into normal, cwm3, or download mode periodically and it will run fine, if I can get it to boot. I switched kernels out and it hasn't fixed the booting problem, I've also odined and that didn't fix it either. My next step is to repartition it, as my newest theory is that the kernel somehow messed up the bml partition that the kernel resides in and that's why its have problems booting, and also why it won't charge when off... but it is actually charging, I tested that out.
Btw I can only get it on by leaving it on the charger about 20 mins until its hot, then pulling the battery, pushing power 2x, putting battery back in and holding power down...
Sometimes it won't work the first time, and sometimes I have to hit power 3 or 4 times with the battery out... its no science...
Sent from my SPH-D700 using XDA App
Thought I posted earlier, guess it didn't submit:
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling On
Sd: ADATA Class 10 16GB
UV: none
Programs installed: A ton, but it's the same general list of apps I've been running for weeks on tons of kernels.
Programs running: SetCPU
Failure on: Battery Pull(I read the brick was happening menu only - doesn't seem to be the case!)
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? Yep, was going to flash another kernel to avoid a brick D:
Previous freezes from UV: N/A
Battery Life on failure: 80%
Strange behaviors list: No strange behaviors, was running pretty awesome and flawless, but I read about the brick on XDA and thought I'd try to avoid it. I had rebooted/powered off with the menu multiple times before with 1.2, so of course being the unlucky guy I am, it bricks when I go to flash over it xD
All is well though, I had a new one in my hand in like 20 minutes
I've seen no mention of anyone trying to get to DOWNLOAD mode by holding the number1 key and power. Leave battery out for 10 minutes press power for 30 seconds. RE insert battery. ^^^^^ then post if you can not get into download mode. if you can then YOU ARE NOT BRICKED
SETCPU is not supported on the epic
A kernel can not brick a phone like that. BAD EQ. Return for overheat issues
Check out this thread for those who cant get my method to work
http://forum.xda-developers.com/showthread.php?t=1042746
chris41g said:
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling On Writeback Journaling No barriers other flags I set myself
Sd: stock
UV: none
Programs installed: Pretty much stripped, twcrushdlauncher, linpack and smartbench... terminal emulator, xda, mybackup root, ghost commander and notepad
Programs running: twcrushdlauncher
Failure on: reboot via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? No
Previous freezes from UV: no
Battery Life on failure: 80ish
Strange behaviors list: Started acting like it was out of ram, I have custom transition animations installed and they were lagging really bad, so I decided to reboot...
I am able to get my phone to boot into normal, cwm3, or download mode periodically and it will run fine, if I can get it to boot. I switched kernels out and it hasn't fixed the booting problem, I've also odined and that didn't fix it either. My next step is to repartition it, as my newest theory is that the kernel somehow messed up the bml partition that the kernel resides in and that's why its have problems booting, and also why it won't charge when off... but it is actually charging, I tested that out.
Btw I can only get it on by leaving it on the charger about 20 mins until its hot, then pulling the battery, pushing power 2x, putting battery back in and holding power down...
Sometimes it won't work the first time, and sometimes I have to hit power 3 or 4 times with the battery out... its no science...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
rjmjr69 said:
I've seen no mention of anyone trying to get to DOWNLOAD mode by holding the number1 key and power. Leave battery out for 10 minutes press power for 30 seconds. RE insert battery. ^^^^^ then post if you can not get into download mode. if you can then YOU ARE NOT BRICKED
SETCPU is not supported on the epic
Click to expand...
Click to collapse
I mentioned in the other thread..I tried both methods..the one you posted and the reset method..I also tried everything k0nane suggest..still bricked :/
If you press the power button, the phone still turns on as after an hour or so running I can feel warmth.but USB is no go and screen is no go..:/..so its running in "some" shape or form...but its still bricked with no way to recover.
rjmjr69 said:
I've seen no mention of anyone trying to get to DOWNLOAD mode by holding the number1 key and power. Leave battery out for 10 minutes press power for 30 seconds. RE insert battery. ^^^^^ then post if you can not get into download mode. if you can then YOU ARE NOT BRICKED
SETCPU is not supported on the epic
Click to expand...
Click to collapse
My apologies, I did skip over what I've tried to get my phone back in working order. My ultimate goal after it wouldn't turn back on was to get to download mode so that I could Odin back to stock. Here are some combinations I've tried get there (approximately in order of trying them):
1) Remove battery, re-insert, 1+Power = nothing
2) Remove battery, press power twice, re-insert, 1+Power = nothing
3) Remove battery, hold power for 1 minute, re-insert, 1+Power = nothing
4) Remove battery, press power twice, wait 10 minutes, re-insert, 1+Power = nothing
5) Attempt to perform a hardware reset using ME's instructions exactly = I have no magic button, or at least this method had no impact on phone's behavior = nothing
6) Remove battery, press power, re-insert battery, plug into wall charger, (phone doesn't charge, no LED), 1+Power = nothing
7) Remove battery, plug into USB, (phone doesn't "charge", no LED), 1+Power = nothing.
8) Remove battery, press power button, wait 1 hour, re-insert, 1+Power = nothing
9) Remove battery, press power button, wait 5 hours, re-insert, 1+Power = nothing
10) Remove battery, press power button, wait overnight (~9 hours), re-insert, 1+Power = nothing
11) Repeatedly and quickly remove battery, press power, re-insert battery, 1+Power = nothing
I'm sure there were a couple of one-off combinations in there, too, but I don't specifically remember every combination, as I tried pretty much every one except 9 and 10 multiple times. I can not get the phone to power on, or boot, or enter CWM3, or enter download mode, or charge, or connect to a PC using any instructions I've seen. Some others have even mentioned that the phone will get warm if plugged in for a while, but that also is not the case with mine, as the phone stays room temperature. And trust me, I know a kernel shouldn't brick a phone like this - which makes it all that much more bizarre. There are many things from which I can recover, but there isn't a whole lot I can do when the phone literally does nothing.
rjmjr69 said:
A kernel can not brick a phone like that. BAD EQ. Return for overheat issues
Check out this thread for those who cant get my method to work
http://forum.xda-developers.com/showthread.php?t=1042746
Click to expand...
Click to collapse
as mentioned in both threads.. and i was the first to mention this.. i monitor my temps closely and it never rose over 97F.. and never got unstable or FC.. I very well understand overclocking and also never UVed... it still runs 1.4 very well at under 97F with journaling on at 19.5 mflops.. this is def caused by the kernel... it just wont turn on reliably.. it never overheated.. i still have my entire battery monitor widget history for the last two weeks showing my temps...
ive tried diff kernels
ive tried odining..
ive tried repartioning
ive tried 3 diff recoveries
im still researching as to what would cause this, as i still dont think its hardware related.. it charges the battery, but isnt allowed access to the charging animations.. and it does power to some extent to warm the battery but not enough to init the phone enough to power on the screen...
Got me a brick:
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling On
Sd: Stock
UV: Lots of it
Programs installed: A ****load
Programs running: SetCPU
Failure on: Tried to make a Screen Off profile in SetCPU just out of sheer greed. Phone was running flawlessly @ 1400 with around 20 hours of battery life with moderate usage.
Previous freezes from UV: Yes
Battery Life on failure: 90%+
Strange behaviors list: None at all. I had the perfect phone until I got greedy with SetCPU's profile option. Ran SetCPU for about two days prior to it without incident.
Its funny because I woke up this morning and Mybackup Root randomly decided work and made a scheduled backup for me this morning. This is like the third time it has ever actually made a scheduled backup for me out of all time that I've had it insatlled I know I should stick with 1.1 until this is figured out but knowing myself I will probably be back on 1.2 by the end of the night. Maybe I'll give Genocide a try as I definitely saw the advantage of using Voltage Control to dial in the phone. I love Thomas' work though with the Vision Kernels though.
Could someone send me a data dump of their partitions and pbl,sbl, sbl backup, and param.lfs??
Code:
# Get Root access first
su
# Do this first to mount the /system R/W
mount -o remount,rw /dev/block/stl9 /system
# Dump the Primary boot loader
dd if=/dev/block/bml1 of=/sdcard/pbl.bin bs=4096
# Dump the Secondary boot loader
dd if=/dev/block/bml4 of=/sdcard/sbl.bin bs=4096
# Dump the Secondary boot loader backup
dd if=/dev/block/bml5 of=/sdcard/sbl.bin bs=4096
# Dump the PARAM.lfs
dd if=/dev/block/bml6 of=/sdcard/param.lfs bs=4096
# Dump the pit
dd if=/dev/block/bml2 of=/sdcard/partitions.pit bs=4096
I'm going to try some of the other methods in this thread, and hopefully I can just delete this post... But for now:
Rom: ACS 1.1
Kernel: Vision 1.2
FS: EXT4+Journaling + On
Sd: stock
UV: NOOP - 1200-50, 1000-50, 800-50 ,600-50, 400-50, 200-50
Programs installed: Lots.. Had Voltage control and Pimp My CPU, lots of games, etc
Programs running: None/Just the launcher
Failure on [When it started]: Power off via menu
If failure was on power off/reboot, were you trying to get into recovery via the 3 buttons? NO
Previous freezes from UV: Yes
Battery Life on failure [shut off]: 8%
Strange behaviors list:
1) It didn't 'fail' per say.. I was shutting off my phone to install a fresh battery (3 batteries FTW)
--I have done this numerous times already on the 1.2 Kernel, and that's why I'm so confused about this..
2) My phone won't turn on, no lights, nothing, period.
-3 finger CWM, booting into recovery, just holding the power button...
3) Everything has been fine up until now. The screen has frozen a few times when I tried bumping up the UV, or the OC higher than what I have now. I've been running my setup for a few days with no issues once I left it all alone
EDIT: Seems like I'm pretty similar to trumble117 up on post #14
rjmjr69 said:
I've seen no mention of anyone trying to get to DOWNLOAD mode by holding the number1 key and power. Leave battery out for 10 minutes press power for 30 seconds. RE insert battery. ^^^^^ then post if you can not get into download mode. if you can then YOU ARE NOT BRICKED
SETCPU is not supported on the epic
Click to expand...
Click to collapse
Download mode wasn't working, I tried every tip in the thread.
I also tried mystery's "button", but it was just a piece of plastic on my device, no button.
And I've used SetCPU since the day I got my Epic and never had any problems, I've heard of problems when you combine voltage control app and SetCPU, but never by itself.
Wondering why you're saying that.
rjmjr69 said:
A kernel can not brick a phone like that. BAD EQ. Return for overheat issues
Check out this thread for those who cant get my method to work
http://forum.xda-developers.com/showthread.php?t=1042746
Click to expand...
Click to collapse
But a kernel can cause the overheating which could damage memory or the device hardware, which in turn causes the brick....
You guys and your deflection... If you state something, it *HAS* to be true... And when the breadth of the community doesn't know enough, it takes these answers as truth...
Like this "super secret button"(that doesn't exist) find, that magically comes out when someone tries to place blame on your group for indirectly harming devices...
Instead of the safe route, "hey guys discontinue use of this kernel until we figure something out one way or the other.",
The chosen method was "Hey, nothing we did could do that.. The issue is only on this kernel and rom, but hey, its out of our control. We didn't do that."
Not to mention, a month ago when it came out, there were many people complaining that when they used the reboot control they lost system apps.
And then add a quip about "How you guys only deal in public."
Yes, in public, but with misinformation...
rjmjr69 said:
SETCPU is not supported on the epic
Click to expand...
Click to collapse
O RLY??????
The Nook is pretty good on battery life.
Sometimes, randomly it just drains the battery though.
I've been meaning to look into this for a while.
The start of this is posted in this general hardware thread.
There's a plot below.
It seems to indicate that there is some real problem with the Jorjin WiFi module.
The left side of the plot shows fresh booted with WiFi on.
The right side shows after it has been pinged.
The goal is to make the Nook be drawing only 10 mA all the time.
As far as the "40 mA square waves" go, what are they?
When running at 10 mA they represent a significant current draw.
With the WiFi off they run every 30 seconds for 5 seconds.
Wow, great work Renate! I hope this is a big step towards tracking down the Nook's random battery drains.
I don't have any good guesses about what would be running every 30 seconds, but I think seeing a timestamped power graph with the corresponding logcat output might be interesting.
I can't tell from the pictures, are you running this on a NST or NTSG and which firmware version?
Do you see the 30/5 waves when wifi is on, or only when it's off?
What does the power draw look like when the nook is in sleep mode?
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.
The logcat is boring, just occasional battery updates and not related to the square waves.
Oh, ClockworkMod Recovery runs at a solid 150 mA and no square waves.
Yes, I've tried power button off vs. timeout off many times and both of them go to a baseline of a mA or so.
It could be a random thing though.
To give it a real test I'd have to power it up/down 1000 times.
The power button push is no problem, but if I want to keep with an unmodified swipe I'll have to throw in a robotic finger.
Edit: Actually, if one of the side buttons is "Menu", then you can dismiss the slide dialog with that.
Still, since top does not report any real CPU activity I have to presume that this is a DC load problem.
The Jorjin is already suspicious.
I've checked the eInk power section during the square waves and that is not switching on then.
Note: The 60 second pulses on the chart are the time in the status bar updating.
The 5 second pulses do appear to be a display related activity with a timeout.
I made an app that would draw a few pixels every 10 seconds.
If it hit when there wasn't a square pulse it would start a square that would end exactly 5 seconds later.
If it hit in the middle of a square pulse the square would end at exactly 5 seconds from the start of the square, not the hit.
This is all a bit confusing because I can't detect the eInk power sections firing for all the squares (or even the full 5 seconds of any square).
The power management is complex, with 2 DC converters, 2 charge pumps, 2 LDO regulators.
The big supplies are the +/- 15V @ 120mA!
30V x 120mA / 3.7V = an Ampere or so!
Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
The WiFi when it's on, happy and doing nothing draws negligible current.
The WiFi when it's on, just woken up and not even pinged draws an additional 80 mA.
Ping it then and the current goes down to negligible.
Turn it off and the current goes down to negligible.
The USB host mode can be a really power sucker.
With just a OTG cable and no device in host mode it draws an additional 150 mA.
Put it back in peripheral mode and the total Nook drain goes to either 40 mA or 20 mA.
Put the Nook to sleep with the power button and it continues to draw 40 mA or 20 mA.
Code:
Powerdomain (core_pwrdm) didn't enter target state 0
I'm not sure how much this affects anyone else.
I am using S1 as the system console.
When you first boot the Nook, the console is in a normal mode.
It relays dmesg stuff and allows you to type commands.
If you go to sleep and then wake it up it's in a strange mode.
If you hit a console key, it only wakes for 5 seconds.
The next key that you hit will be actually registered.
This is the source of the 5 second square waves.
Type constantly and it's an additional 40 mA.
The thing is, I was seeing this before with nothing connected.
The level shifter has no pullups and was randomly triggering on noise.
A screen update is a major electrical incident that sets it off.
I'll be adding a pullup to my RX in on the console.
Safest way to save the battery (as far as I know right now):
If you reboot, don't use it immediately for long periods, sleep with the power button, then wake.
The safest for WiFi is to wake the Nook with WiFi on, then ping or connect to it.
Then turn it off. (Yes, I know that this is a bit impractical.)
The real wildcard is USB. After using USB host mode, do a power down reset.
Anybody have any insight into why this 5 second wakeup on the console?
From the current drain it must be doing a loop in software or something.
You can show your dmesg and logcat?
You do measurements with SD card?
I am confused by error after sleep
<3> [6439.043121] PM: Failed to prepare device omap3epfb.0 for power transition: error -16
I have a lot these errors. I think that the screen while drawing the screensaver is not the first time screen sleep.
I have deleted the system utility debuggerd. She is all the more load on the CPU.
Renate NST said:
Ok, a few interim observations.
The Nook happily sitting on a reading page doing nothing should draw ~8 mA
When the Nook is cold-booted it draws ~40 mA at rest.
Put it to sleep with the power button, then wake it, it will go to ~8 mA.
Click to expand...
Click to collapse
How does using the rear power button compare with long-holding the front 'n' button, or using Button Savior's virtual power button?
I always sleep with the power button.
I just checked, I removed long push of the "n" button entirely from my policy.jar
I didn't notice anything.
I may try that "sleep 1000 times" experiment.
jeff_kz said:
Is there any difference between "sleep" after pushing the power button versus sleep after an idle timeout? I've never noticed a difference and it would be nice to have some evidence to dispel one of this community's long-standing superstitions.
Click to expand...
Click to collapse
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!
Sparker_95 said:
Hello!
I've got a Nook Simple Touch running firmware v1.2.1 and rooted with NookManager, Nook Applications switched off by NookManager and max CPU frequency set to 300mHz. On this and other sites It was stated that Nook SImple Touch enters a bugged sleep mode after pressing the "power' button, consuming much more energy than after an idle timeout. Out of curiosity I took my NST apart and measured current directly through battery lines while setting NST into various states. I've found this thread and it turns out that very much work has already been done, but I'd like to share my measurements anyway - the more information there is the better.
ReLaunch, main screen - 11.5mA
ReLaunch, task manager - 53.5mA
Cool Reader - 12.5mA
Sleep mode:
power button - 0.8mA
screen time-out -0.8mA
default reader app time-out - 0.8mA
Start up - 250mA during ~35 seconds
So, all sleep modes consume the same amount of current.
Also, NST consumes very large amount of current during start up. Combined with rather long start up sequence, it makes one start-up equivalent to ~3 hours of sleep mode! If you're not going to turn it off for more than 3 hours, it's better to use sleep mode instead of turning it off completely.
I hope someone will find it useful!
Click to expand...
Click to collapse
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place
smeezekitty said:
Did you test sleep by long pressing the "nook" button? That is usually my method of choice since the power button is in an inconvenient place
Click to expand...
Click to collapse
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.
thenookieforlife3 said:
The problem with long-pressing the "n" button to ensleepify the Nook (at least for me) is that you have to hold it... and hold it... and hold it before it sleeps. Mind you, this observation is on an NSTG with "long press the n button glowlight toggle" enabled, so I don't know the exact number of ms. it is for the regular NST.
But I really prefer using the back button, because you just tap it once, and boom, it's asleep.
By the way, I tested the n button long-press method, and it gives the exact same results as the power button tap method.
Post thank for the testing?
Click to expand...
Click to collapse
Ok a good enough. The NST without glowlight you don't have to hold it so long