Database Info

[Q] My device keeps powering off when the I put the screen to sleep.

For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?

supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Ok thanks. What is sod by the way???

supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

oh lol im learning slowly but fa showly.

supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Question about uv. is less best ie -25? and what does disabling the various clock speeds do?

Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.

Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50

jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)

You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation

supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.

Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)

Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.

Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.

Unresponsive Screen (Screen Freeze)

Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!

recDNA said:
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
Click to expand...
Click to collapse
It looks like that most people that end up with this problem (sleep of death, blank screen of death, or whatever you want it to be called) were either underclocking to low or undervolting to low, some governors have also been the culprit on some devices. Not all of our thunderbolts are the same, guess solder joints are weaker or something that makes this such a random problem. Your best solution is to try different kernels, cpu settings, and governors to find out what your phone likes. I personally haven't had this issue with eternity. However, some others have! Good Luck

Yes, what the above poster said. Like for my phone it does not like smartass gov. It will work but the screen will freeze as you have experienced also. Also overclocking, i can overclock to 1.7ghz but will also freeze randomly as you experienced.
Sent from my HTC ThunderBolt using xda premium

I think (but could be mistaken) this is more like the opposite of black screen of death. I believe that is when the phone wont wake from sleep.
My problem occurs only when phone is awake and being used heavily. The screen isn't black nor blank - I see whatever screen I am on when it happens: lock screen, an app, home screen, keyboard, etc. I see all the icons but screen becomes totally unresponsive to touch. Wide awake.screen but no matter how you tap, slide, or use capacitive buttons nothing works.
Only way out is to pull battery or hold down up volume, down volume, and power key simultaneously to force a restart.
There is someone out there who understands this phenomenon better than I and can suggest approaches but I must be clear - this is.not a black or blank screen and doesn't occur when clock speed is low.
I would.guess cpu is operating at full 1 ghz when screen freezes occur in my tbolt. I am not overclocking at the moment but I do believe overclocking makes it worse but not sure.

Mine was doing that at being underclocked too low keep it at say, 368 mine never did it again, also don't undervolt too much it can cause phone to power down. I use ondemand and keep you lowest speed to 368 and you should be fine. Using battery saver mode for kernel in speedtweak may be undervolting your phone to much if you are using that.
Try this kernel working great for me. http://db.tt/QqkRvtjm jdk newest kernel.
Sent from my ADR6400L using XDA App

I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?

recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That might be the case if we all used the exact same set up. We don't some change fonts, some use different apps, and there are so many variables.

Nothing unusual going on in my tbolt. 1.0.9 cubed with no unusual apps or settings. I seldom add.an app to my bolt unless it has 1000's of downloads in the market with high ratings. I learned that back before I rooted. I bet someone who writes.kernels understands this phenomenon and could point me in the right direction. Imagine if your computer was bonked up and advice was to randomly try changing settings?

recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That sounds more like your phone doesn't like whatever voltage is set for your top end frequencies. Might want to try IncrediControl from the market and increase the vdd levels a little. I think a lot of the kernels floating around are under volted a little. Could be the cause.
Sent from my ADR6400L using Tapatalk

Its worth a try. I never tried that. Thanks.

You say it only happens when using your bolt, maybe the processor is just maxed out. How long do you wait to see if it comes back around?

I have waited as long as 10 minutes but usually ibjust restart within 30 seconds based on experience. Once "frozen" it has never recovered on its own.
What's interesting is the processor is still working whilebthe screen becomes unresponsive. I know this because I was streaming a r radio into a jawbone earpiece and when I switched apps the screen froze yet the radio continued to play. I HAD to restart to stop the music since the screen wouldn't respond to touch.

I flashed Imo's lean Sense Kernel and haven't had a freeze yet. I hope this has solved the problem. There is a little lag now when I hit a widget or app shortcut but no more freeze.

Your lag is prob due to being in safe made, put in normal mode in speed tweak to rid yourself of lag.
Sent from my ADR6400L using XDA App

No, I'm in standard mode. I chose #1 in speedtweak. I varified at 1.4 ghz max/ 254 min
I couldn't figure out how to raise min value in speedtweak so I reinstalled set cpu and set min to 368. Seems to reduce the lag.
Still a slight lag but most importantly no screen freeze since installation.

This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?

mkitchen said:
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing a stock ruu in fastboot? You may try to go back to completely stock and then go from there. You could try a different rom too and wipe the system partition as well as the usual stuff first.
Sent from my ADR6400L using Tapatalk

I went back to the stock ROM using clockwork mod recovery, and the problem persists. I am wiping system partition now, but I did some of the stuff that has worked for me in the past such as dalvik, user data, and cache.

Wiping system may help but if that doesn't I'm not sure what else for you to try except fastboot flashing an ruu.
Sent from my ADR6400L using Tapatalk

Actually wiping system worked, I may have not done it in the correct order the first time I tried to flash back to stock. I really appreciate the help.

[Q] With LiveOC I must change also the voltages?

Hi there!
I'm not allowed yet to post in the development section, so I decided to put my question here... Please don't shoot me
I have read many threads from the Development Section (when got the time), tested a few Roms and Kernels. All of the developers are doing a great job, every day (my donations are going to eugene373, mathkid95 & peter alfonso).
I had no idea how a Nexus S can "move" with a custom Rom or Kernel.
I'm kinda new in this "root affair" with my phone, and i found a superb combination between Bugless Beast Rom & Matr1x 15 Kernel. For that i have posted some screen shots.
In order to achieve those results, i used LiveOC to 105 but i didn't changed the voltages. Oh, and Lulzactive/Sio. When i put the phone to charge, i had a freeze, and a battery pull was needed.
So, can someone tell me if i need to change the voltages too for that combination to be stable? If so, which are the best voltages?
Thank all of you in advance!
P.S.: I use i9023 LCD. With eugene373's Speedy 7 & stock ICS i had no reboots or freezes, but the battery is not that great. Although, the phone is unbelievably fast.

They're decent results, the i9023's screen generally uses more power due to the backlight. Matr1x kernel is undervolted and some phones don't like it. For LiveOC i would DEFINITELY pump up the voltages (say +25mV across the board, except 100mhz and 200mhz as matr1x has them stock). Keep messing around with the voltages until you find the lowest voltage that is happily stable and not overheating.
Your phone may be fine, though. But as the frequency goes up AND matr1x is already undervolted, you'll probably be better off taking it up to 110% and finding somewhere stable there since i believe the minimum voltage change is 25mV.

Thank you very much for your answer.
I'll will try to do what you adviced me, but I'm a little bit afraid not to mess up things because I'm just a begginer, as I said...
Best of luck!

You'll be fine mate, just don't push it too hard until you know what your phone is capable of and make sure heat isn't a problem. Some chips just aren't as lenient as others, but yours seems to take undervolting fairly well which is a good sign.

Also, as you're bumping it up and testing, don't check set on boot. Unless you have a current working nandroid at least.
Sent from my Nexus S 4G using xda premium

Harbb said:
They're decent results, the i9023's screen generally uses more power due to the backlight. Matr1x kernel is undervolted and some phones don't like it. For LiveOC i would DEFINITELY pump up the voltages (say +25mV across the board, except 100mhz and 200mhz as matr1x has them stock). Keep messing around with the voltages until you find the lowest voltage that is happily stable and not overheating.
Your phone may be fine, though. But as the frequency goes up AND matr1x is already undervolted, you'll probably be better off taking it up to 110% and finding somewhere stable there since i believe the minimum voltage change is 25mV.
Click to expand...
Click to collapse
i think your statment about screen is not completely right.
yes , based on SA screen functionality , it's saves more power then Super Clear LCD screen because SA lights its up by itself , but SC LCD screen needs additional light lay.
but that also depends on color , SA runs brilliant color costs same , or even more juices as SC LCD , but it do save power when shows dark color like black.
this is why android 2.3 status bar color has changed from grey to black , also default wallpaper for Nexus S is dark color.
------------
to OP , about voltages , you only have to change it when you OC and your phone become unstable , live OC usually are able up to 115% or 120% , if you don't OC over 1.0 G but use live OC up to 1.15 G or 1.2 G , you won't be needing change voltage.
but if you use both OC and liveOC , for example by Matr1x, CPU can set up to 1.46G and 115% of LiveOC , max to 1.67 G , in that case you may need change voltage...
yes... this is max i've done , i was afraid that i would get CPU fried...

I said generally for the amoleds, I'm very aware of how they work. Unless you're staring at an all white screen all day it is quite rare for it to use more power. This is why it is a great technology for mobile phones.
Anywho, it certainly needs additional voltage with liveoc. Please don't misinform others. At 110%, 1GHz becomes 1.1GHz which is plenty to cause instability on many cpus. This is especially true with matr1x and other undervolted kernels.

with all due respect , but i think little bite OC doesn't really need change voltage , because usually , generally , mostly , kernel default setting is enough...

When you live oc an undervolted kernel yes you do need to raise voltages
Regardless if you regular oc or not because if you live oc by 10% you are ocing by 10%. Its not complicated.
Harbb is right.
I know, I'm a tester for matr1x and in being a tester that means I have to test all aspects of it and put it under different strains, overclocking etc.
To the OP:
Live oc by 110% and if you have problems with reboots then raise voltages by 25mv as harbb said already.
And he also gave good advice regarding unchecking the set at boot option in nstools.
Disregard all other comments.

Thank you Harbb and Nodstuff!
Very good advices, I've followed them and seems to work ok so far. Seems like I didn't read that much as I thought, because I didn't know that the Matr1x kernel is undervolted. I have to read more infos from here, wish I'd had the time... I was just looking for a good combination between a Rom and a Kernel, because I had terrible battery life on stock ICS. Now I'm pretty happy with the combo mentioned above, thank you again for your help.
I wish you all the best and good luck!

[Q] Massive reboots while charging.

Hi i have never encountered such a problem before, been using my phone for about a year now.
When i updated my ROM to CyberGR-MOD|NS.NGN ICS v.8 HYBRID+ICUP Speedy7|CM9-AOKP|MODS++|STORMY 3 and switched to Matrix 17.5 kernel i get massive reboots while my phone is charging.
the thing is the phone works flawlessly while on battery but once i plug in the charger i'll get random reboots. i am running at stock kernel settings. ondemand, cfq scheduler. no OC no Undervolt. any idea whats the cause of this??
thanks!!

Matr1x is undervolted by default, so try setting them to default values in NSTools or something. I believe INT is undervolted too. Defaults are:
ARM:
Freq (MHz) Voltage (mV)
100 950
200 950
400 1050
800 1200
1000 1250
INT:
Freq (Mhz) Voltage (mV)
100 900
200 950
400 1000
800 1050
1000 1100

Sorry I forgot to mention that I have raised the voltages to original stock voltages as well. Double checked and my phone is running at those voltages when I get the reboots. Would you suggest raising them even more?

No, the phone should run perfectly well at stock voltages (as long as you raised arm AND int). Any higher is wasteful. Did you do a dalvik cache wipe before installing matr1x? And if you did, did you do a thorough wipe before flashing the new ROM? That would mean doing a data/factory reset and formatting /system at least (formatting /boot too, preferrably). If you can't find any other reason, i'd probably start with reflashing the kernel and then the ROM too, as many weird and wonderful things can happen if there are remnants of old system files.

Yupp that's what I usually do every time I update my ROM. I even did it once to try and fix this problem. I'm beginning to suspect that it's an issue with my ROM and the kernel. Though nobody on the thread seems to have the same issue. Eagerly waiting for an update. Anyways thanks for the advice.

Not sure what else it could be aside from the typical try a different kernel/rom/governor/whatever. Hopefully an update or something clears it up for you, but until then i'd definitely try to find something that doesn't go ape**** when you start charging

Minimum CPU Not Sticking on SetCPU with ElementalX Kernel

Wasn't sure if I should comment this on the ElementalX kernel thread or not, so I made a topic...
I bought SetCPU, and its working great. Other than the fact that changing minimum CPU isn't sticking at all. When I set the max (I undervolted it to 1.5 ghz for regular use) it sticks fine, but the minimum just seems to be locked to 300 mhz. Even if I change it, it goes back to 300 mhz.
Anyone know what's up with this?

bump. Need a solution bros.

That is mpdecision at work. Google it, you will find everything you need to know. Once you disable mpdecision (some custom kernels come with it disabled or give you the option to disable it) you min/max cpu freqs should stick

derukun said:
bump. Need a solution bros.
Click to expand...
Click to collapse
Man, this is OLD news. It is working. You ae only seeing the MPD values, that keep your device from having wake or sleep of death issues. Personally I (even Flar, ElementalX's creator) prefer mdp. It is pretty reliable & since implementing it on the N7 & N5, I certainly haven't had any SOD issues.
At any rate, what those apps report as the voltage is a snapshot based on proc data. It is only as accurate as what the exact voltage is at the instant of that report & hasno effect on what actual device screen on/off minimum voltage really is.