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.
Related
Hey guys I have my nexus 7 OC to 1.6ghz? MIN and MAX. It runs on 60C is that too hot? I'm using motley's kernel 520mhz GPU ?
iTzTrevor said:
Hey guys I have my nexus 7 OC to 1.6ghz? MIN and MAX. It runs on 60C is that too hot? I'm using motley's kernel 520mhz GPU ?
Click to expand...
Click to collapse
its a little warm, but normal for 1.6ghz if youre using the device.
What is considered too hot? 70C ? I do have a gaming PC and do the same rules apply to what is considered too hot? For me 80C is too hot for my GPU on my PC. Is it fine to have the same mindset when it comes to my N7?
iTzTrevor said:
What is considered too hot? 70C ? I do have a gaming PC and do the same rules apply to what is considered too hot? For me 80C is too hot for my GPU on my PC. Is it fine to have the same mindset when it comes to my N7?
Click to expand...
Click to collapse
stock thermal throttle is 85C(some custom kernels set this higher or lower). at that point the device will lower the cpu speed to cool itself off. safety shutdown is at 100C. if at 1.6ghz, and gaming, its probably normal to go into the 70C's if its a cpu intensive game. it also depends on the outside temp, the cooler its outside, the cooler the device will be.
Any way to revert back to the stock kernel settings? I reflashed the Stock kernel for the nexus 7 but i want to know its governor and voltage and etc back to full stock settings.
iTzTrevor said:
Any way to revert back to the stock kernel settings? I reflashed the Stock kernel for the nexus 7 but i want to know its governor and voltage and etc back to full stock settings.
Click to expand...
Click to collapse
if you didnt change anything, it would boot up at its default settings. or if you have set something with a cpu app to boot, unset it and reboot.
Thanks. I wanted to do a comparison of different kernels and see which fits best for my everyday usage.
72° is when system panics
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
72° is when system panics
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
depending which kernel youre using and what temp the thermal throttle is set for. you can even remove tbermal throttle when building a kernel, but the phone would just shut down when reaching the safety temp.
iTzTrevor said:
Hey guys I have my nexus 7 OC to 1.6ghz? MIN and MAX. It runs on 60C is that too hot? I'm using motley's kernel 520mhz GPU ?
Click to expand...
Click to collapse
You might want to buy this...
http://www.amazon.com/Cooler-Master...UTF8&qid=1356771776&sr=8-1&keywords=hyper+212
iTzTrevor said:
Hey guys I have my nexus 7 OC to 1.6ghz? MIN and MAX. It runs on 60C is that too hot? I'
Click to expand...
Click to collapse
Nobody can answer your last question unless you post a screenshot of your system info.
Rcoil73 said:
Nobody can answer your last question unless you post a screenshot of your system info.
Click to expand...
Click to collapse
He got an answer like 4 months ago.
Sent from my Nexus 7 using xda premium
Hey guys, touch booster is really annoying on this phone. It pushes the phone to 1.06GHz everytime I touch it, and is starting to bug me.
Is there anyway to keep it scaling up properly?
I'm no expert at this stuff, but isn't this fast jump in CPU clock what pretty much makes Project Butter possible?
If I understand right (and I probably don't), I think this might have to do with with governor in-use. If your rooted; try using a different governor and then touching the screen.
Great, so now people are complaining about Project Butter's features... ok
How exactly does something like this bug you?
People are getting way too picky with this phone now. Relax, its a phone guys
Sent from my E4GT by using THE FORCE
Next thread will be " This phone is too fast, how do I slow it down to keep up?"
Sent from my Nexus 4 using xda premium
The CPU goes up when you touch it so it can be responsive and quick to your inputs. How is this so annoying?
If you root it you can lower the max or change the governor buy chances are you will lose much of your responsiveness.
I understand that it is good for us to discuss issues and problems but some of the things I am seeing here are just really nit picking and complaining about things that are not bad at all. We are a spoiled society of humans, some more than others i guess.
sent via xda premium with nexus 7
Monk4Life said:
Next thread will be " This phone is too fast, how do I slow it down to keep up?"
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
you joke but there's a surprising amount of people that underclock their cpu thinking it will save battery...
qwahchees said:
Hey guys, touch booster is really annoying on this phone. It pushes the phone to 1.06GHz everytime I touch it, and is starting to bug me.
Is there anyway to keep it scaling up properly?
Click to expand...
Click to collapse
Get some CPU control app and change the minimum frequency from 1GHz to 384MHz.
/thread
neotekz said:
you joke but there's a surprising amount of people that underclock their cpu thinking it will save battery...
Click to expand...
Click to collapse
Under clocking will save battery in most cases but ot will also make your phone sluggish and slow depending on how much.
sent via xda premium with nexus 7
---------- Post added at 12:07 AM ---------- Previous post was at 12:05 AM ----------
richteralan said:
Get some CPU control app and change the minimum frequency from 1GHz to 384MHz.
/thread
Click to expand...
Click to collapse
That will make your phone run so slow and crappy... Why have a decent cpu if the plan is to chop it? This defeats the entire purpose of having a 1.5ghz clock speed..
sent via xda premium with nexus 7
Richieboy67 said:
That will make your phone run so slow and crappy... Why have a decent cpu if the plan is to chop it? This defeats the entire purpose of having a 1.5ghz clock speed..
sent via xda premium with nexus 7
Click to expand...
Click to collapse
You have no idea what you are talking about.
Check the meaning of "MINIMUM CPU FREQUENCY".
P.S. O and btw I'm changed it to 384MHz on my Nexus 4. AND........wait for it........my nexus 4 is not slow and crappy........woo mind blown!
What I find interesting is on the nexus 4 the governor is on demand , and the scaling range is 0mhz- 1026mhz ( you can check using CPU spy +)
However on the nexus 10 , the governor is interactive and the scaling range is 0mhz -200mhz
I wonder why that is
Sent from my Nexus 10 using Tapatalk 2
italia0101 said:
What I find interesting is on the nexus 4 the governor is on demand , and the scaling range is 0mhz- 1026mhz ( you can check using CPU spy +)
However on the nexus 10 , the governor is interactive and the scaling range is 0mhz -200mhz
I wonder why that is
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
that app is broken.
Try No-frills CPU control, or even AnTuTu CPU Master.
Is it interactive on the nexus 4 then? I just checked on my n10 smd it still says interactive
Sent from my Nexus 10 using Tapatalk 2
italia0101 said:
Is it interactive on the nexus 4 then? I just checked on my n10 smd it still says interactive
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
I'm using no-frills and the default is ondemand, scaling from 1GHz to 1.5GHz.
What I changed is only the minimum frequency from 1GHz to 384MHz. Nothing more.
The scaling...
Sent from my Nexus 4 using XDA Premium HD app
richteralan said:
I'm using no-frills and the default is ondemand, scaling from 1GHz to 1.5GHz.
What I changed is only the minimum frequency from 1GHz to 384MHz. Nothing more.
Click to expand...
Click to collapse
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ask Google.
I have no idea. And I don't have a Nexus 10.
italia0101 said:
Yea that's cool I get that . I just wonder why the governor is different on the nexus 10
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Nexus 10 is a dual core tablet, not a phone. Check your PC some time or laptop. They scale totally differently than a phone does.
sent via xda premium with nexus 7
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
Is it ok for me to have a task in Tasker that changes the governor everytime the phone sleeps and wakes? Is that harmful to my device?
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
QUIETLYloud said:
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Brendan12695 said:
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Click to expand...
Click to collapse
You have it clocked at 28.8 GHz? Pretty sure you're going to melt your phone. (I kid)
I believe he meant 288 GHz. He's from the future and is trolling us.
Sent from my Nexus 4 using xda premium
Branden pls
Sent from my Nexus 4 using xda app-developers app
Totally fine, but you might encounter stability problems.
Lol. My bad, was just copying what Trickster Mod said.. :/ I have the min at 288 MHz so when power save is on it underclocks to that.
I just don't want to screw up the hardware by jumping back and forth between ondemand and powersave.
Sent from my Nexus 4 using Tapatalk 2
Try out this Tasker script : http://forum.xda-developers.com/showthread.php?t=1018245
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.