Related
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.
I'm running nscollab 1.60 with Franco kernel and was wondering if anyone's got some good custom voltage settings I can test out for a stronger battery life?
Essentially I'm a data user. Usually on the screen 4+ hours of the days, running market, fb and browser and of course texting.
Currently I'm messing around with smartassv2 200/800 deep idle off, BLN off, and kernel default voltage and I'm about to run my first battery calibration ...
Thanks on advance
EDIT: another side note is I've noticed my screen gets pretty hot now. When I'd run stock GB it wouldn't do that.
Hi, first to defend myself, I did search and found that everybody says good things for every kernel. So every kernel is best for Stock ICS?
I got confused. Yes I'am total noob and recently learned how to root and flash custom rom's.
I just want to hear your opinion for best kernel running on Stock ICS.
I need kernel that is good for the battery but also snappy for the system. I don't play games and I use my phone for calls, reading news, working on excel files, google maps, mail and taking pictures.
My phone is Nexus S GT-I9020T on Wind network.
IMO ezekeel kernels
Has lats of featured including voodoo color
http://forum.xda-developers.com/showthread.php?p=20520270
Sent from my Nexus S using xda premium
Thank you. Is this kernel stable?
Im just trying to set it up as we speak, will let you know how stable it appears once I figure it out
Stuck on trying to flash an unsecure boot image at the moment.
*shrugs* The stock kernel?
Unless you want the functions third party kernels bring to the table, I don't see a good enough reason to swap the stock kernel for another.
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Just managed to get ezekeels CFS on there and I get the reboot bug after going to standby.
Looking for updates but the thread is huge. Yet to try BFS.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Click to expand...
Click to collapse
You can try and turn off deep idle for your reboots.
Solves the problem 99% of the time (totally made up stat that could actually be true)
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
darko.baruh said:
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Deep idle gives more battery time under certain conditions (screen off but not completely idle, playing music for instance). It won't really give you more battery time if your phone is actually idle with the screen off.
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel.
Click to expand...
Click to collapse
Same here but not bad at least for me just one reboot since i installed yesterday when he posted. 2.1 kernel I never got any reboots
Sent from my Nexus S using xda premium
darko.baruh said:
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
Click to expand...
Click to collapse
The first post that you linked actually just confirms what I said.
Ezekeel said:
Since this is just theory and Morfic noted that his experience seems to indicate otherwise and that limiting the CPU frequency does actually decrease the battery drain, I put this theory to the test and logged the battery charge over 10h of FLAC playback in Airplane mode with the screen switched off.
Click to expand...
Click to collapse
1) Playing FLAC (not idle)
2) Screen off
Pre-requisites are met.
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
darko.baruh said:
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
Click to expand...
Click to collapse
Deep idle only shows savings if there is tasks running while the screen is off VS the same situation without deep idle.
So for someone doing commuting (like simms22 for example) and listening to music for around an hour, they'll lose less battery with deep idle than without.
You won't actually save battery if your phone is actually idle with deep idle enabled.
It's not some kind of magical function that makes your phone use less battery doing tasks with the screen on, deep idle disables certain components of the phone while executing tasks with the screen off, instead of having it "at full speed" as if the screen was on.
Now I understood. Thank you very much.
darko.baruh said:
Now I understood. Thank you very much.
Click to expand...
Click to collapse
No problem. I think Deep Idle is probably the mod by Ezekeel surrounded by the most misconceptions.
Most new users want it absolutely but don't seem to know why.
On His Glados kernel I noticed that Android OS was using 20%-21% of the battery and on the stock kernel 30%-31%.
Android System was using around 14% and on the stock around 19%.
Ok, have you decided to give the Glados 2.2 another go? I believe I have finally tweaked it so that it is stable for me.
Before I was getting restarts within 30 seconds of the screen turning off. I have cornered this (on my phone at least) to a problem with NSTools auto-setting the lower frequency to 100mhz. Changing it back to 200mhz and I have yet to see the system restart itself. Im not overclocked, because I dont see the point as everything is fairly snappy with this new kernel. I dont really play games on it so Im not fussed.
I did used NSTools and the frequency was set to 200mhz and I had system restarting on screen off. Using stock ICS with Glados 2.2
Also I had green annoying flickr on locking and unlocking the screen.
Can someone recommend or point me to a undervolting kernel that I can flash onto my rooted, unlocked Nexus 4 running the latest 5.1.1 LMY48T factory image?
I don't want to flash a new ROM and have to spend the time reinstalling all my apps, or gapps, just a new kernel would be great.
I have to undervolt this phone because I have a slow binned cpu, and the phone gets hot as hell and crashes to the red led of death when I perform any stress tests, and I have already installed the copper shim and thermal paste to help with the heat dissipation.
In order to reboot the phone I have to pull the battery.
Many thanks, Tony.
I managed to find some info on a good undervolting kernel called hells core. It has done wonders for my phone. I now don't get to 45°C whereas I used to see 70°+ during routine tasks (browsing, calls, messaging - forget games!). My phone clearly has a bug but this kernel has saved it. For anyone with a cooking Nexus 4, definitely download the hells core kernel. It's amazing. HC-B83.5-L.ZIP for the latest Lollipop.
Hi well like the title says any more battery tips for Nexus 5 have unlocked bootloader and have twrp installed, just wondering if there's a rom which isnt heavy on battery when not in use also any further tips on saving battery as I know the basics.i will be custom pretty soon just need some advice or personal suggestions
So far I already tried 5/6 Roms.
For Battery
If you prefer Nougat, go for PURE NEXUS with Franco Kernel
For Oreo, install DIRTY UNICORN with Stock Kernel
You can easily get 2.5/3 Hours SOT
(I got a Nexus 5 a month ago for $50 )
Battery Saving Tips:
Turn Off Google Location
Use GPS only when you need
Turn Off NFC
Install Kernel Auditor & choose "powersave" on CPU Governer
Iskander101 said:
So far I already tried 5/6 Roms.
For Battery
If you prefer Nougat, go for PURE NEXUS with Franco Kernel
For Oreo, install DIRTY UNICORN with Stock Kernel
You can easily get 2.5/3 Hours SOT
(I got a Nexus 5 a month ago for $50 )
Battery Saving Tips:
Turn Off Google Location
Use GPS only when you need
Turn Off NFC
Install Kernel Auditor & choose "powersave" on CPU Governer
Click to expand...
Click to collapse
I got my nexus 5 32gb for 10 pounds all boxed as well just aload of scratches to the screen but not deep ones.I flashed lineage 14.1 with elemental X kernal and its under clocked to 1.2ghz