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.
Related
So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
cmccollough said:
So I'm on a visionary temp root, overclocked with setcpu. Ive set up several different profiles but I've noticed that my battery life with the profiles isnt as good as other users have claimed.
I have noticed that when i open setcpu sometimes a little message will flash up saying that setcpu has been given superuser permissions. Does this mean that prior to opening the program, it didnt have permissions? If it in fact did not have superuser permissions, could that be why my battery life is less than expected? (i.e. The program didnt have permissions and thus couldnt use the profiles to slow down cpu speed upon screen off, etc.) The message does not come up every time I open setcpu, but it seems to come up when I havent opened the app recently.
Any ideas?
Click to expand...
Click to collapse
From my understanding, you only set it once. i had set a widget because i thought set cpu had to be running. But i deleted it because if you think about it....superuser app already has the permissions set, and when you open setcpu it shows the current speed.....if it wasnt working it would show 800mhz then KICK into 1 ghz?....thats what i think. You shouldnt need to worry.
Great, thanks for the response.
Sent from my HTC Vision using XDA App
same here. from time to time this popup comes.
anyway i cannot see any benefit from running setcpu as the profiles are not working for me.
i tried setting up screen off profile. this never triggers.
i leave setcpu deinstalled now. battery life is good so far
snudel said:
i tried setting up screen off profile. this never triggers.
Click to expand...
Click to collapse
How can you tell if it triggers or not?
cmccollough said:
How can you tell if it triggers or not?
Click to expand...
Click to collapse
Good question. Can't find anything in logcat.
set notifications.
on the magic you could see him switching profiles right after turning on the screen
you wont see it on the g2
I agree, something is fishy with this. EVERY time I open setcpu it gives me the su permissions granted window like its not being saved in memory
Sent from my HTC Vision using XDA App
EDIT: After shopping around on the market I came across an app called "CPU Tuner". The UI is nice and has roughly the same customization as setcpu if not more. It does take a bit of getting used too but i'm more than willing since the profile notification actually cycles with this app vs. setcpu. I'll give it a shakedown tomorrow as it's getting too late here to test.
cpu tuner doesn't work for me.
in profiles, it just shows 700mhz to 800mhz, which makes it useless as i want to underclock to 200 when screen is off.
That toast pop-up is nothing to worry about, its just something that has featured in the last couple of SU builds, it doesn't mean your app is not working.
I just turn the notification off in the SU settings.
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
cmccollough said:
I can now confirm that the screen off profile is not working correctly. Before going to sleep last night, my phone had a charge of 99%. I did not have anything running (no wifi, bluetooth, sync, etc.) and I woke up to 81% battery. It never killed that much overnight before overclocking. We gotta get this fixed.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
jark99 said:
i have mine set to 1ghz max 245 min profile screen off 245/245 priority--100..and put a widget on my main screen. My phone has been on screen off for the pat 5 hours....and drained only 2% battery life.....i dont understand why it doesnt work with some peoples phones??!!. is it different cause im using a desire z and yours a g2?...i HARDLY doubt that would be a problem :S..
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Running the setcpu widget on my phone caused instability issues at higher clocks (feeling ballzy w/ flippy's 1.8 kernel). After removing the widget my profiles were hit and miss for some reason.
As far as the battery issue goes, anyone running CM RC2 and earlier might want to check out nightly 36, apparently there was a memory leak causing battery drainage ( I don't know anything about what it means but common sense leads me to believe a leak is bad lol). If anyone is still not satisfied with setcpu I highly recommend CPU tuner.
jark99 said:
have you tried the widget?.when going to running services, my setcpu app has been running for ever. aka profiles and setcpu working.
Click to expand...
Click to collapse
Yes I have the widget on my homescreen. Weird that so many people get different results
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
cmccollough said:
Could the scaling be giving people varying results? I don't even really know what they do, I have mine set on ondemand. Would someone mind sharing what exactly the different scalings do?
Click to expand...
Click to collapse
http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html
Centered around the OG Droid but basic concepts still stand.
- Just picked up an app called SuperPower, had it a while back and had issues..but it's been update a lot since then. Looks like it's an all purpose battery management app that has the ability to govern cpu speed also. I'll test drive it and see how it works.
My battery life has improved markedly since installing CM nightly #36 and Pershoot's latest kernel. I've been using my phone pretty heavily over the last 8hours and still have over 50% left. Lots of texts, emails and websurfing etc.
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.
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.
chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake
Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?
Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back
My phone locks up 2-3 times a day when sleeping. When it locks up, the "SAMSUNG" splash screen briefly flashes, and the phone vibrates. If left alone, it gets warm. I have to hold the power button or pull the battery to restart it. I have been unable to adb into the phone to get logcat or dmesg after it locks up. Also, this never occurs while the phone is plugged in. I have tried Darkside v8 with both Venom and Faux 008 kernels, as well as Jedi Mind Trick 8/18 with Faux 009. With Darkside, I tried changing the screen-off governor with System Tuner to ondemand as mentioned at http://forum.xda-developers.com/showpost.php?p=29559002&postcount=8633, but it didn't help. Is there anything I may have done wrong, or any way to fix this? Thanks!
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
What happens if you don't touch the governor?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
MadMax3947 said:
With conservative governor and screen-off set to no governor change, it crashed this morning. Running Mind Trick 8/18 with Faux 009.
Click to expand...
Click to collapse
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Try on demand .
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
MadMax3947 said:
I set the governor to ondemand and rebooted. Phone locked up within 10 minutes. Also, if it helps, I had Venom clocked at 384/1512 and Faux at 384/1728 (since I can't lower the max because of DVFS). Darkside v8 ran fine for about a week before the crashes began.
Click to expand...
Click to collapse
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
When you say lock up you're talking about sleep of death correct? Have you logcat afterwards?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
I tried flashing Gideon's stock OC/UV script (http://forum.xda-developers.com/showpost.php?p=20946429&postcount=574), thinking that my phone may just be unable to handle the default UV with Venom and Faux, but this caused it to SOD (without the SAMSUNG splash) almost immediately. I went back to my Nandroid of Darkside v8 (since Mind Trick didn't help things), and flashed Faux 009 with the undervolt set with System Tuner to -12.5mv below stock for all stock frequencies. If this doesn't help, is there a possibility that my phone is faulty? I have had it since December. Also, could this be related to the GPU or L2 overclocks in Venom and Faux (but if so, why wouldn't it crash when the phone is awake)? Thank you for your time.
If it still crashes, I have a flashable zip of the stock ICS kernel and its modules that I can try, or if extremely necessary I can ODIN back to stock.
EDIT: manual Faux UV did not help, just flashed stock.
EDIT2: It just crashed with stock kernel as well (still using Darkside v8 ROM). Since it doesn't seem to be ROM or kernel related, I'm worried it may be the phone (perhaps whatever passes for a PSU in a smartphone? It'd explain why it doesn't crash on battery power). I'll probably try flashing AOKP ICS next in case it's a TouchWiz problem. Is there anything I'm missing here, or should I ask for a warranty exchange if AOKP or stock ODIN still crashes?
EDIT3: Uninstalled System Tuner to be completely sure nothing's affecting the governor/voltage/clock/etc. (still Darkside v8 ROM, stock UVLE1 kernel), crashed within 15 minutes of restart.
MadMax3947 said:
It only locks up when the screen is off, and never when plugged in. I tried Streamline kernel a while ago and got sleep of death basically every time the screen turned off (and I went back to stock immediately), but this seems different (in that it doesn't just not wake up like Streamline, the phone vibrates and displays the SAMSUNG splash before it won't wake up). I tried to get a logcat with adb when it last crashed, but the phone didn't even show on my computer's USB bus. I restarted it and took a logcat and dmesg until it booted, which I can send you if you wish.
Click to expand...
Click to collapse
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
I would put stock ROM back on it take it to a t mobile store and show them what's happening. If you have warranty they should replace it. Your CPU is shot. It won't go into deep sleep. And when running stock, it's not a software issue. It's hardware.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I was worried about this. I will ODIN back to stock tonight, but I won't be able to take it to a t-mobile store for a couple of days. Thank you for your help.
EDIT: I have been running stock UVLE1 (kernel and ROM) without root for almost a day now, and it has not locked up. According to CPU spy, the phone is able to enter deep sleep. Could there be something in the custom boot scripts used by Darkside and Mind Trick that my phone doesn't like? It's about the only thing I could think of that would not be fixed by the stock kernel. I might try re-rooting and/or flashing AOKP ICS in a few days if my phone holds up.
Been noticing this since last week. Every time I use my phone for like 1 or 2 minutes, the phone starts getting hot. Usually, it gets hot after an hour of use (Facebook, Messaging, Browser, Twitter, Play Store). Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
This hasn't happened to me before. Not sure if this is normal, but I just want to make sure.
My recent heat and battery drain was coming from an app. I didn't check the CPU.
I checked the battery area of the settings and found a locale add-on that was draining more juice than my screen.
sent from a secret underground bunker
It will happen if your signal is real bad or 3G is down in your area.
I don't think it's my signal. I get 2 or 3 bars almost all of the time at home with the FC09 modem.
Besides opening and/or using an app, it seems that the CPU clock will go max speed if I do something, such as scrolling. Battery is also draining quickly before this was happening to me.
Sent from my SPH-D700 using Tapatalk 2
InsaneHien said:
Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
Click to expand...
Click to collapse
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
AndyYan said:
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
Click to expand...
Click to collapse
Yeah, you're right. I even looked it up. It's part of Jelly Bean.
I'm going back to CM9 or The People's ROM.
You could try a different kernel, or lower voltage. Sorry not sure what phone this topic is for lol but that's some options. It takes a lot to get my phone hot, and I'm on jelly bean
Sent from my Galaxy Nexus using Tapatalk 2
I don't have this problem on nitest kernel with the ns4g modem
Sent from my SPH-D700 using Tapatalk 2
You likely have an issue with your settings.
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Ruedii said:
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Click to expand...
Click to collapse
It didn't help unfortunately.
I flashed CM9 earlier and the issue still exists. I'm now back on CM10 (11/22 nightly).
It's okay if this can't be resolved. I am probably gonna go back to a GB ROM.
EDIT: Issue still persists in GB. I'm guessing it could be a hardware issue? I have no idea. Back to JB. I'm still willing to try anything to resolve this. Thanks to those who posted some solutions.
Sent from my SPH-D700 using Tapatalk 2