I have a nexus 4 16GB, rev_11, fast bin alongside Franco kernel r34 with cm10.1 13th Jan build!
Every night after a long day of using my phone I charge it, I have a remaining 20% every time I go to do so. It charges fine but every time when I wake up in the morning, my phone is turned off? How? I charge it while on and am lost on how it turns off? I have to the power button to get it on again; I'm afraid that I maybe damaging it, it's a long shot but am curious.
I have searched the forum for an answer but couldn't find one, hoping you guys could help me off!
Thank you in advance:thumbup:
..sent from space.
Nothing people? Please help? /
..sent from space.
What are your CPU frequencies? Also, what governor and I/O are you using?
Sent from my Nexus 4 using xda premium
Max 1512 and Min 384 with interactive governor and row I/O; these were the default settings from the kernel :thumbup:
..sent from space.
amarb70 said:
Max 1512 and Min 384 with interactive governor and row I/O; these were the default settings from the kernel :thumbup:
..sent from space.
Click to expand...
Click to collapse
Try changing your governor
Sent from my Nexus 4 using xda premium
But interactive is the strongly recommended one the kernel and in general? :S
..sent from space.
amarb70 said:
But interactive is the strongly recommended one the kernel and in general? :S
..sent from space.
Click to expand...
Click to collapse
Not really.... Just try changing it and see if it fixes your SOD problem.
Sent from my Nexus 4 using xda premium
I will and will report back) thank you my friend, is that what my problem is? Screen of death? I thought that was something else, how is a screen of death possible on Franco's kernel? it only does that btw while on charge, no other time..
..sent from space.
I'm just curious if anyone has encountered this.
I tend to UC my processor when I am casually browsing the web and whatnot; my settings stick until my screen turns off. Then when it wakes back up the frequencies are at the default values? Tried updating busy box but that didn't fix it
Sent from my Nexus 10 using xda app-developers app
duarian said:
I'm just curious if anyone has encountered this.
I tend to UC my processor when I am casually browsing the web and whatnot; my settings stick until my screen turns off. Then when it wakes back up the frequencies are at the default values? Tried updating busy box but that didn't fix it
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I know this thread is from the way back...
Have you tried installing from APKMirror the "Kernel Adiutor (ROOT) 0.9.73 beta (Android 4.0.3+)" has allowed me to lower CPU MAX Frequency and have it stick after BOOT!
com.grarak.kerneladiutor_0.9.73_beta-241_minAPI15(nodpi)_apkmirror.com
Cheers
Anyone else getting the sleep of death with this ROM and kernel combo?
Sent from my Nexus 4 using xda premium
I get sod with harsh kernel too, ever since it changed to 4.2.2. It happens every time the screen goes off for a minute when not on charger. I never get sod with any other kernel.... shrugs
Yep same here been happening here all morning since I installed it. Pushing the eject button on this one
Sent from my Nexus 4 using xda premium
Never happened to me
Tapalked with a Nexus⁴
Maybe your voltages are too low? Or maybe try a different governor/scheduler combo such as Ondemand and CFQ or ROW or something. Still, I'm not sure ...
Switched to orca......loving it
Sent from my Nexus 4 using xda premium
Okay,so i made this thread so that development thread become less spammed with your questions.
Please,share your opinions here and ask questions,someone will answer you,and share your screenshots of battery life.
I personally use PegasusQ+VR,it gives great performance and good battery life.
My second choice would be Abyssplug+SIO,especcialy for the hotplug feature.
(In case you dont know what Hotplug is,its the feature that turns off the second core when your phone is not in use.)
I cant decide wich is better,tommorow ill test Hotplug+sio,and ill post screenshots of both tommorow.
Please,ask any questions here,dont spam Benz's threads.
Thank you
DeHuMaNiZeD said:
Okay,so i made this thread so that development thread become less spammed with your questions.
Please,share your opinions here and ask questions,someone will answer you,and share your screenshots of battery life.
I personally use PegasusQ+VR,it gives great performance and good battery life.
My second choice would be Abyssplug+SIO,especcialy for the hotplug feature.
(In case you dont know what Hotplug is,its the feature that turns off the second core when your phone is not in use.)
I cant decide wich is better,tommorow ill test Hotplug+sio,and ill post screenshots of both tommorow.
Please,ask any questions here,dont spam Benz's threads.
Thank you
Click to expand...
Click to collapse
OnDemand + CFQ (Like in stock ROM) the only way that don´t dry my battery.
With that combination my phone is slow like hell..have you tried those that i wrote.
Sent from my GT-I8190 using XDA Premium 4 mobile app
DeHuMaNiZeD said:
With that combination my phone is slow like hell..have you tried those that i wrote.
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, but my batteryd doesn't like them very much
Sent from my GT-I8190 using Tapatalk
thats odd
Sent from my GT-I8190 using XDA Premium 4 mobile app
Hi, can you tell me the best combination of governors to use. I'm using latest cm
10.1 maclaw build with hotplug and noop, but i think CPU its not sleeping cause i loose about 5% battery in 2hours withought using my fone at all. Thanks
Sent from my GT-I8190 using xda app-developers app ?
Hotplug governor is indeed a joke, at least in Maclaw's CM (not surprised). There is no way to set it up for low battery drain /and/ reasonably smooth functionality. Right now I am using Ondemand + CFQ while playing with the powersave bias and up threshold parameters. The only thing I wish I had from Maclaw/Benz's kernel is the vr/sio schedulers.
You have VR and sio schelduer in Benz's kernel,and Abyssplug governor with real hotpulg feature,when you dont use the phone cpu shuts down one core and the remaining core runs on 200Mhz and 1% usage.
Sent from my GT-I8190 using XDA Premium 4 mobile app
I would gladly use that kernel if it didn't have the dirty flickering fix. And if it didn't require CM10.1 reboot edition.
Also, when I was on CM i ran a logcat with hotplug activated. The second core would often reactivate even if the phone wasn't doing anything, with the screen turned off, then soon turn off and after a few seconds repeat the process. Maybe this phone really needs the core.
What flicketing fix? I got no flickering on the latest Maclaws cm and benzs kernel..and it shuts down the core,you can see with system monitor when your screen is on..dunno for screen off,but i get like 1% drained for a hour with screen off
Sent from my GT-I8190 using XDA Premium 4 mobile app
The 63 fps refresh rate, which "fixes" the UI flickering.
And yes, I saw the second core turning off myself. However, I am not sure if it keeps being off enough time.
Well in maclaws rom i dont have flickering,but in olivers i had. I dont know,i got decent battery life. Not good as stock,but its ok
Sent from my GT-I8190 using XDA Premium 4 mobile app
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Nemo1984 said:
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read this. It will help you to decide which is the best for your needs:good::good:
P.S: BTW, @DeHuMaNiZeD, if you want, add this link to your OP, so people can read it & learn.
Nemo1984 said:
Which is more battery friendly? Abyssplug or Pegasusq?
Sent from my GT-I8190 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Pegasusq said to have hotplugging but doesnt seem to work with screen on
Based on what I read, my best guess would be Abyssplug. I'll run some tests and will post my results.
Sent from my GT-I8190 using XDA Premium 4 mobile app
AssToast said:
Pegasusq said to have hotplugging but doesnt seem to work with screen on
Click to expand...
Click to collapse
Yes, it only turn off one core when the screen off. I'm testing pegasusq + sio
For the next days, I'll be on abyssplug + sio.
Sent from my GT-I8190 using XDA Premium 4 mobile app
metalboy94 said:
The 63 fps refresh rate, which "fixes" the UI flickering.
And yes, I saw the second core turning off myself. However, I am not sure if it keeps being off enough time.
Click to expand...
Click to collapse
And what exactly is so wrong with 63 fps refresh rate? Will your screen fry because of it? No it won't because it can't. Will your phone explode while being used? No it won't because it can't. What's the issue here then? Tell me.
Benzonat0r said:
And what exactly is so wrong with 63 fps refresh rate? Will your screen fry because of it? No it won't because it can't. Will your phone explode while being used? No it won't because it can't. What's the issue here then? Tell me.
Click to expand...
Click to collapse
Have you considered the battery drain implications? The battery is weak enough as it is, a higher than normal refresh rate only wastes more GPU power thus more battery.
Hi, recently i noticed, this annoying popping/ticking noise while listening to music and talking on the phone using headphones. Anyone had this problem before? It only appears when the screen is off.
Using PA with franco kernel. N4 16gb.
Can you try raising your screen off frequency a few notches?
Sent from my Nexus 4 using XDA Free mobile app
I could try, but then my battery life would surely get worse :/ are you sure that's the reason?
To be honest i don't even have an app to change it, any suggestions?
Qbsti said:
I could try, but then my battery life would surely get worse :/ are you sure that's the reason?
To be honest i don't even have an app to change it, any suggestions?
Click to expand...
Click to collapse
You'd change it in settings, display
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You'd change it in settings, display
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Oh, the screen off timeout, i though he was talking about cpu frequency when the screen is off. Well having my screen on the whole time is not a solution when im daily listening to music for ~4h.
Sorry for the miscommunication. I was actually referring to the max screen off frequency, the setting adjustable in most kernel managers (I believe the Franco kernel manager has this setting, as does trickster, etc). It might reduce battery life slightly, but its worth a shot to try to fix the issue. I am not 100% sure that this is the reason for your problem, though, just trying to give you suggestions.
Sent from my Nexus 4 using XDA Free mobile app
Thanks, ill try it next time it occurs and report back here if it solves the issue.