Related
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
legato89 said:
My phone is rooted and has s-off but I have a few issues. One is almost half the time when I hit the power button the screen doesn't turn on instantly but the soft buttons light up. It usually takes me hitting it 2-3 times swiftly to get my screen on. Another issue is sometimes wifi calling gets screwed up so it doesn't work and it drains my battery as a background task stuck on restarting. I really only want my phone overclocked so just have baconbits kernel. is there a newer version I should put on that fixes these issues?
Click to expand...
Click to collapse
Baconbits, to my knowledge, is the only OCd kernel available for the stock ROM. Your screen issue might actually be caused by underclocking though, do you have a screen off profile or a minimum set?
Sent from my T-Mobile G2 using XDA App
I just have it set to 368-1497. Should I up the minimum?
legato89 said:
I just have it set to 368-1497. Should I up the minimum?
Click to expand...
Click to collapse
Give the overclock widget a try. Its available free on the market. In the advanced setting, set your screen off profile to 245 min and 806 max. Scroll down and hit "save" before you exit settings. That will keep your phone running at stock speeds while the screen is off and should stop the wake issue you're having. When you're using the phone you'll be at the higher speeds.
I already had the widget. Did what you said but it still occurs.
legato89 said:
I already had the widget. Did what you said but it still occurs.
Click to expand...
Click to collapse
245 is *way* too low, especially if you have things running in the background ... just start raising the lower end up until it stops happening.
Sent from my T-Mobile G2 using XDA App
Setting it to stay at 800 while the screen is off seemed to fix it. Any ideas about wifi calling bugging out? It usually doesn't happen very often, I think when my phone has been on for a while without a restart.
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
dietotherhythm said:
overclock widget doesn't overclock anything.... it controls the speeds AFTER you've installed an overclock kernel. I highly suggest using flippys turbocharged 1.8ghz kernel. Just because it is capable of 1.8ghz doesn't mean that you need to run it at 1.8ghz. you can just do something like 1.1 or something in between. Give it a look.
Click to expand...
Click to collapse
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
EdKeys said:
Nobody said the OC widget overclocked anything. Did you read the OP's first post? It was suggested so as to enable a screen off profile because the OP is having a wake issue while using baconbits.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
set the off screen profile to the lowest speed 200/200mhz and 100% priority and he wont have anymore wake issues, don't know what I was reading hahaha
The screen on issue doesn't happen anymore but I'm not satisfied with my battery life. In the past something was causing my battery to drain insanely fast so I un installed a bunch of unused apps and started checking background tasks but when browsing the internet for 20 minutes on my way home I use 30% of the battery, bluetooth on.
Sent from my T-Mobile G2 using XDA App
Anyone know if it is possible to run Pershoot's kernel on the stock rom that comes with the device? Any side effects?
I don't know enough to say 100% one way or the other, but I read in a post I can't find right now that only BaconBits is made to work with the stock rom.
FWIW, I tried to flash the 1.8 GHz kernal on my stock G2 this morning, and got stuck in a boot loop.
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
legato89 said:
On AndroidCentral people are saying they have improved battery life with CM7 nightlies. I'd like to try running a ROM finally. Do I need to get rid of my Baconbits kernel before proceeding? I already backed up everything with Titanium.
Click to expand...
Click to collapse
NO. The first thing you need to do is flash clockworkmod 3.0.0.5, which is totally different than ROM Manager. As of right now the latest clockworkmod available through ROM Manager is 2.5.1.3. If you haven't flashed that yet (2.5.1.3) do that first through ROM Manager. The best way to flash 3.0.0.5 is to find the .img file, place it on your sd card and run the commands from terminal emulator. After that just wipe data/factory reset, wipe davlik cache and flash the latest nightly .zip, reboot, then the latest gapps .zip. Go to the development forum and the first post in the nightly vendor vision thread has all the links you'll need.
Syndicate 1.2
Genocide 2
This has happened twice now. Turn the phone on, it boots, plays my boot animation (helix) and then sits at the end of the animation, and never starts up. It gets really hot, cpu not battery.
Tried fixing permissions, wiping and reflashing. Only Odin works (what I did the first time)
Thinking it is genocide, as I didn't have any issues until I upped to version 2, from 1.1.
LunaticWolf said:
Syndicate 1.2
Genocide 2
This has happened twice now. Turn the phone on, it boots, plays my boot animation (helix) and then sits at the end of the animation, and never starts up. It gets really hot, cpu not battery.
Tried fixing permissions, wiping and reflashing. Only Odin works (what I did the first time)
Thinking it is genocide, as I didn't have any issues until I upped to version 2, from 1.1.
Click to expand...
Click to collapse
Are you overclocking or undervolting? If so, then don't....set them back to stock values and see if that fixes it.
kennyglass123 said:
Are you overclocking or undervolting? If so, then don't....set them back to stock values and see if that fixes it.
Click to expand...
Click to collapse
+1 on that
kennyglass123 said:
Are you overclocking or undervolting? If so, then don't....set them back to stock values and see if that fixes it.
Click to expand...
Click to collapse
I was OCed, not undervolted, on the first time. After odining, I did not OC and is still happened again today.
LunaticWolf said:
I was OCed, not undervolted, on the first time. After odining, I did not OC and is still happened again today.
Click to expand...
Click to collapse
Are you using SetCPU or Voltage Control? Make sure your maximum is 1000 Mhz and your minimum is 200 Mhz.
LunaticWolf said:
I was OCed, not undervolted, on the first time. After odining, I did not OC and is still happened again today.
Click to expand...
Click to collapse
Honestly, this has happened to me from time to time when the circle is going under Android Man. I just battery pull and reboot and all is well. Another reason why journal on can be your friend...freezing boot animations or shutdowns. I am always 1400 max but not under 200 minimum EDIT...for what its worth, I reverted back to Genocide 1.1 IAP from 2.0
Sent from my SPH-D700 using XDA Premium App
kennyglass123 said:
Are you using SetCPU or Voltage Control? Make sure your maximum is 1000 Mhz and your minimum is 200 Mhz.
Click to expand...
Click to collapse
Voltage control.
I had to odin to get my phone working again. Right now, no OC app is installed.
JohnCorleone said:
Honestly, this has happened to me from time to time when the circle is going under Android Man. I just battery pull and reboot and all is well. Another reason why journal on can be your friend...freezing boot animations or shutdowns. I am always 1400 max but not under 200 minimum EDIT...for what its worth, I reverted back to Genocide 1.1 IAP from 2.0
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I did that, and let it sit overnight when it first happened. Still at the android man after 8 hours.
Had it at 1400/200 with journaling as well. I went back to 1.1 as well. We will see what happens
LunaticWolf said:
I did that, and let it sit overnight when it first happened. Still at the android man after 8 hours.
Had it at 1400/200 with journaling as well. I went back to 1.1 as well. We will see what happens
Click to expand...
Click to collapse
If you have it happen again, pull battery, boot into recovery, wipe cache and Dalvik 3x and reboot. I know you did this already but give it one more shot that way. If it freezes, don't let it sit there fighting to boot. Have you been trying different boot animations? Maybe Odin to clean out some left over stuff in your system if you don't get it working. I have the exact same setup as you currently but with Nebula theme that has its own boot ani. Helix is on my all time fav list though
Sent from my SPH-D700 using XDA Premium App
If you Odin and restore everything, you still have a bad system somewhere. You should start fresh without restoring everything and see if it still happens. Then add a few things at a time to see what causes it. Before reinstalling the boot ani, wipe cache and Dalvik.
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)
Franco also has trinity settings you can play with
J
Sent from my Galaxy Nexus using xda app-developers app
Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).
That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
Sent from my Galaxy Nexus using xda app-developers app
cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
I have good flow with trinity kernels. No lag or unresponsivness
*Who needs a gs3 when you have a NEXUS*
simms22 said:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
Click to expand...
Click to collapse
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
cmstlist said:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
Click to expand...
Click to collapse
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:
http://pastebin.com/sSe9eFXT
In particular to trim out just the TKT lines and the last few lines before lockup:
Code:
D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED
So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?
simms22 said:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Click to expand...
Click to collapse
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
cmstlist said:
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
Click to expand...
Click to collapse
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
simms22 said:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
Click to expand...
Click to collapse
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
does your rom have its own cpu settings? maybe theres something enabled in there?
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.
simms22 said:
does your rom have its own cpu settings? maybe theres something enabled in there?
Click to expand...
Click to collapse
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
simms22 said:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
Click to expand...
Click to collapse
No I do not. I will try reinstalling now since I uninstalled it completely.
morfic said:
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Again, pure stock flashed straight from Google, except for Trinity.
I'm running jmz stock rom, no problems, but recently I've seen that my Cpu voltage has been kept at 1.4 (full over clock) and it won't come down unless in deep sleep. I've tried Cpu control apps, they don't seem to work. Not sure what the problem is.
Sent from my HTC One VX using xda app-developers app
Johann12911 said:
I'm running jmz stock rom, no problems, but recently I've seen that my Cpu voltage has been kept at 1.4 (full over clock) and it won't come down unless in deep sleep. I've tried Cpu control apps, they don't seem to work. Not sure what the problem is.
Sent from my HTC One VX using xda app-developers app
Click to expand...
Click to collapse
did you change the cpu governor to performace?
govenor is set to smartassV2. ive tried changing it to all of them, when the screen is on and the phone is not in deep sleep, it is running at full speed for some reason.
that used to happened to my inspire 4G
i had to reset it . that usually fix it .
lateral18 said:
that used to happened to my inspire 4G
i had to reset it . that usually fix it .
Click to expand...
Click to collapse
i wiped, reflashed, whatever there is i can do and it STILL is running on max cpu frequency. it makes the phone very hot, and uses quite alot of battery throughout the day. better battery stats just says that system is using the most, and that 1.4ghz has been running 100 percent of the time (unless screen off ((deep sleep)) )
Johann12911 said:
i wiped, reflashed, whatever there is i can do and it STILL is running on max cpu frequency. it makes the phone very hot, and uses quite alot of battery throughout the day. better battery stats just says that system is using the most, and that 1.4ghz has been running 100 percent of the time (unless screen off ((deep sleep)) )
Click to expand...
Click to collapse
if i remember correctly , it was an up doing it to my phone ,
you said you wipe and reflashed , did you installed the same apps .
honestly i dont see why using battery stats.
problem still persists, not sure why though. seems when i restart it sometimes it will do it, and other times it wont. Usually waiting for the phone to cool down, then restarting it fixes the problem. Not sure why.
Flash jmz linaro kernel and use any app to lower the cpu freq. That's how I have been using mine since v1. No heating or draining issues so far. I use smartassv2 as governor.
Sent from my HTC One VX using xda premium
Hi i'm getting random and frequent freezes, normally on WhatsApp and the last one on uTorrent app.
I've changed from ROMs first on uXylon, then on Illusion, Vanir and now on AOKP.
The phone is very fast and responsive but randomly freezes and i have to remove batt.
Also sometimes won't wake up and also have to remove batt.
I never had that behavior before and i have no idea what to do.
Thanks in advance.
Your best bet is to look into into the logcat, last_kmsg, and/or dmesg.
Try overvolting a bit.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Try overvolting a bit.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Can you explain better?
-=| Illusion + ASKP |=-
Idrito said:
Can you explain better?
-=| Illusion + ASKP |=-
Click to expand...
Click to collapse
Since you are on ASKP you can adjust the voltage settings. To do that you need to download Trickster Mod from the play store. Then go to the tab specific and scroll down to MPU Voltages. There is a little button with a + and a -. You press that and a pop up will appear. Press the + once and hit apply (big button in the upper right corner). If it is solved you need to set it on boot in the menu.
Sent from my Galaxy Nexus using XDA Premium HD app
cupfulloflol said:
Your best bet is to look into into the logcat, last_kmsg, and/or dmesg.
Click to expand...
Click to collapse
+1
mrgnex said:
Try overvolting a bit.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Before overvolting, OP could try to switch governor/scheduler/network algorythm combo. I couldn't find any quick info on SR' state on this kernel, but it would seem it's on by default, and that should take care of voltages automatically.
I'm having pretty much the same issue...
The phone will go to sleep and then never wake up. I'll get LED notifications, vibrations, sounds, etc that the phone is still working but screen will never turn on until I remove the battery and restart. The phone still works though, music will continue playing and all.
I've formatted everything, complete wipe, factory reset, SD card format, left performance control above minimum, changed lockscreens, wiped all caches, fixed permissions, flashed different ROMs, seem to always end up with the same issue.
Currently with "on demand" on SETCpu, what governor should I look into switching it to? And what would be the overvolt option for me to give it a go as well?
Thanks for all feedback.
blustosa said:
I'm having pretty much the same issue...
The phone will go to sleep and then never wake up. I'll get LED notifications, vibrations, sounds, etc that the phone is still working but screen will never turn on until I remove the battery and restart. The phone still works though, music will continue playing and all.
I've formatted everything, complete wipe, factory reset, SD card format, left performance control above minimum, changed lockscreens, wiped all caches, fixed permissions, flashed different ROMs, seem to always end up with the same issue.
Currently with "on demand" on SETCpu, what governor should I look into switching it to? And what would be the overvolt option for me to give it a go as well?
Thanks for all feedback.
Click to expand...
Click to collapse
Maybe your screen off clock is too low. Check in trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
Are you changing the animation speed in dev settings ? i used to and had freezes and blank screens, After leaving these settings on stock i never had another freeze.