Related
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
erasure1969 said:
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
Click to expand...
Click to collapse
what ur experiencing is SOD(sleep of Death), u can change ur kernel to Siyah v4.1.2 and see
I had similar problem on CM10 experimental (20120825). When I woke up the phone was turned off, but I couldn't turn it on. I found that the battery discharged to 0%. >.<
Now, I'm on stock.
erasure1969 said:
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
Click to expand...
Click to collapse
that's Sleep of Death bro. Flash another kernel, and don't mess what you don't understand
Swyped from Samsung Galaxy SII
Sleep of death!
I was on siyah 4.0.1 and it happened using that now i'm on Dorimanx v5.70 and the same this moring, Extweaks = default cpu governor: lulzactiveq, Deep-sleep cpu governor = ondemand.
I now it's not a real problem and the roms fine but just thinking it's the sgs2!
Thanks guys
erasure1969 said:
I was on siyah 4.0.1 and it happened using that now i'm on Dorimanx v5.70 and the same this moring, Extweaks = default cpu governor: lulzactiveq, Deep-sleep cpu governor = ondemand.
I now it's not a real problem and the roms fine but just thinking it's the sgs2!
Thanks guys
Click to expand...
Click to collapse
Luzactive as default governer unless tweaked properly might cause issue's, try the default "pegasusq' governer by resetting the extweak profile once and see
Sun90 said:
Luzactive as default governer unless tweaked properly might cause issue's, try the default "pegasusq' governer by resetting the extweak profile once and see
Click to expand...
Click to collapse
Ok Sun90 done that thanks, but the first time it happened using siyah that battery was dead in the morning and using Dorimanx the juice was 100% but phone was off, didn't have to take the battery out just used the power buttong to get it on
change kernel and restore default option for exTweaks using clokworkmod
vitalianoleone said:
change kernel and restore default option for exTweaks using clokworkmod
Click to expand...
Click to collapse
I've reset Extweaks in clockwork, cleared cache etc, Governor = HYPER and Deep-sleep, ondemand
no problems with jelly king 1.5
Hello Everybody.
So this is one of rare place where i can post to tell everyone who use this ROM that it's works like a charm in my S2 with Siyah 4.1.4 Modem XXLPX.
sources i use to :
http://forum.xda-developers.com/showpost.php?p=31218484&postcount=436
Extweaks from
http://forum.xda-developers.com/showthread.php?t=1875573
and
http://forum.xda-developers.com/showpost.php?p=31202456&postcount=1752
have a look for services.jar optimized :
http://forum.xda-developers.com/showthread.php?t=1869663
and
http://forum.xda-developers.com/showthread.php?t=1617219
I only want to share my experience ans perhaps help....
Hope this help too.
les fautes ? i'm French . c'est pour ça.
Whoaaaa V 1.6.2 is just MAGNIFIQUE !
http://imageshack.us/a/img24/9696/jellykingv162.jpg
I do not know what is causing this, but no matter what current JellyBean rom I flash, I cannot adjust my MIN and MAX cpu power. As soon as I toch it it defaults to 100/100 and I can't adjust it anymore. Anyone know what is going on?
nafeasonto said:
I do not know what is causing this, but no matter what current JellyBean rom I flash, I cannot adjust my MIN and MAX cpu power. As soon as I toch it it defaults to 100/100 and I can't adjust it anymore. Anyone know what is going on?
Click to expand...
Click to collapse
Just outta curiosity, are you by any chance using devil kernel with the JB roms that you are trying?
If this is the case, I've noticed that the devil control app tends to override any changes made with say nstools...
I'm not sure if this is the case, since I myself have done very little testing on JB roms...but food for thought.
Also, how are you changing your values exactly? Nstools? Voltage control? Baked in settings? Some other app?
Yeah it its the Devil kernel. Can you point that out in the HEllyBean thread, because doesn't seem anyone believes me.
I can adjust max in performance settings but it won't let me change minimum.
Edit: just figured this out, if you have cpu when screen off set in dkc app, it will not let you set CPU min in performance to anything other than that minimum setting.
sent from the depths of helly bean
samsgun357 said:
I can adjust max in performance settings but it won't let me change minimum.
Edit: just figured this out, if you have cpu when screen off set in dkc app, it will not let you set CPU min in performance to anything other than that minimum setting.
sent from the depths of helly bean
Click to expand...
Click to collapse
That's what I thought!
Thanks for confirming dude
Let me first apologize for not posting in the correct dev thread, for that I do not have permissions to do so. Also like to thank all the devs for their hardwork, time, & commitment to helping others.
I have recently flashed my LGOG E970 to SnowJB's (Team Carbon) CarbonRom. However, I notice extreme battery drain (~1% every 2-3minutes) using the default Kernel. I tried to adjust the performance control settings to lower the min setting from 1026 to 384 but the settings will not save /stick.
I ended up flashing to Houcha's geeb kernel based on someone's post of a similiar battery drain problem. However, unlike that user I am still experiencing major battery drains. Once again i tried to adjust the Performance Control settings and still have the problem of it not "sticking".
Any ideas on how to get the settings to stick or resolve this crazy battery drain issue?
FYI: LGNPST to JB 4.1.2 -> Rooted -> Unlocked -> Flashed CarbonRom with CWM v6 per OP directions
Thanks in advance
Disable performance control with titanium backup. Download trickster mod app or similar and use that. I had the best battery performance using houstonn's modded 192 mhz kernel.
Sent from my LG-E970 using xda app-developers app
thank you
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
bamboochimp81 said:
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
Click to expand...
Click to collapse
I too experience this, however as mentioned above with houstonn's 192mhz kernel, the settings will stick; verified working on my CarbomROM LGOG.
I'll try it out
croozah said:
I too experience this, however as mentioned above with houstonn's 192mhz kernel, the settings will stick; verified working on my CarbomROM LGOG.
Click to expand...
Click to collapse
I will flash the 192mhz ROM and let you know if it resolves my issue the same as it resolved yours. ty
bamboochimp81 said:
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
Click to expand...
Click to collapse
If you find your settings to be stable after continuous use, in Trickster if you hit menu, there's a set on boot option. Just enable it, and I think you can also ask for a notification from Trickster when it does start.
Hi all!
I don't have a lot of free time, but i just fell in love with CM12, and i wanted to use it daily.(and i want to help for those who wants to use it daily aswell)
We all met with the deepsleep problem, it only happens when screen is off, and cpu governor is not powersave.
As in ALL the google API talks about powersaving mode when phone is in sleep mode etc... i think there is a major problem with CM12 framework, that android not going to powersaver mode.(as it should)
So what i have done is just coded a "couple of minute sollution". It is an apk, and it is only uses one service, and one broadcastreceiver to be able to SET CPU to powersave mode when screen is off.(And ofcourse back to interactive when screen is on, to avoid lag)
HOW TO USE: (ROOT NEEDED!!!)
1) Download apk from here(attached down)
2) Install it
3) Start the application from menu
4) Wait until SuperSU(or any root) asks for permission, allow it!
5) Reboot phone.
After the first start of the application, the icon will be removed from menu not to disturb the user
So when you open it, take care for wait SuperSU to ask permission, and when you give it, then reboot.
If you messed up something, just delete app from settings menu, and do steps from 2).
If you want to be sure that it works use adb shell command to check governor:
After reboot turn the screen off and type in adb:
Code:
adb shell
su
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
it will show powersave, and when you turn the screen on it will show interactive!
One more thing! To avoid SuperSU make toasts of granting permission, you can turn it off in SuperSU settings!
Peaceful life with lollipop btw!
WAITING FOR FEEDBACKS
It needs to be performance not power save right?
wooolfgang said:
It needs to be performance not power save right?
Click to expand...
Click to collapse
This can be right but i am using it on powesave and works like a charm.
Btw i make another option then, for those who need perf. Gov.
Even i can make it to 300mhz when sleep via performance governor to avoid battery drain.
trapacska said:
This can be right but i am using it on powesave and works like a charm.
Btw i make another option then, for those who need perf. Gov.
Even i can make it to 300mhz when sleep via performance governor to avoid battery drain.
Click to expand...
Click to collapse
No need bro this first one is good. Not using performance governor and there are no deep sleep problems.:good:
trapacska said:
This can be right but i am using it on powesave and works like a charm.
Btw i make another option then, for those who need perf. Gov.
Even i can make it to 300mhz when sleep via performance governor to avoid battery drain.
Click to expand...
Click to collapse
You made this app? If not where did you find it? Which commands does it do?
trapacska said:
So what i have done is just coded a "couple of minute sollution". It is an apk, and it is only uses one service, and one broadcastreceiver to be able to SET CPU to powersave mode when screen is off.(And ofcourse back to interactive when screen is on, to avoid lag)
Click to expand...
Click to collapse
siracuervo said:
You made this app? If not where did you find it? Which commands does it do?
Click to expand...
Click to collapse
So if you read the actual post he indicates he has indeed made this app.
Sent from my LG-D620 using XDA Free mobile app
steffenbakke said:
So if you read the actual post he indicates he has indeed made this app.
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
I want to know the intructions that the app implements to make it work natively and fix the issue
siracuervo said:
I want to know the intructions that the app implements to make it work natively and fix the issue
Click to expand...
Click to collapse
Hi.
It is really simple, i don't really think you can fix the issue if you don't know how to set a cpu scaling governor.(it is very basic thing since android is out, and even on PCs)(if you don't mind i am declaring this)
On this site you can find instructions:
http://bamboopuppy.com/android-cpu-frequency-using-cpufreq-ondemand-governor/
What i used is checking screen state(via BroadcastReceiver), and when screen is on i set it to interactive, when screen is off i set it to powersave, that's it really.
I even posted in OP how you can check:
Code:
adb shell
su
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
To write governor:
Code:
adb shell
su
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Work this app on latest CM12 build ?
simo14 said:
Work this app on latest CM12 build ?
Click to expand...
Click to collapse
yes =)
I've tried but not work
Installed apk but still have problems with deep sleep sometimes. Can I do something else?
this is no longer needed since i fixed deepsleep in the rom
invaderjohn said:
this is no longer needed since i fixed deepsleep in the rom
Click to expand...
Click to collapse
so, with the last release, does the deep sleep work fine?
tecno789 said:
so, with the last release, does the deep sleep work fine?
Click to expand...
Click to collapse
Indeed
invaderjohn said:
Indeed
Click to expand...
Click to collapse
Just another question. Is the ROM incompatible with Ds battery saver? Because, it doesn't work, it can't switch off the network, why? Can i fix it?
tecno789 said:
Just another question. Is the ROM incompatible with Ds battery saver? Because, it doesn't work, it can't switch off the network, why? Can i fix it?
Click to expand...
Click to collapse
Lollipop has a built-in battery saver. U dont need a 3rd party app for that
invaderjohn said:
Lollipop has a built-in battery saver. U dont need a 3rd party app for that
Click to expand...
Click to collapse
But it doesn't work as battery saver..
tecno789 said:
But it doesn't work as battery saver..
Click to expand...
Click to collapse
It does for me. Anyway i have like 1,5-2 days of batt life, and if the batt life gets low i turn on batt saver. And it works. Its not a bug.
invaderjohn said:
It does for me. Anyway i have like 1,5-2 days of batt life, and if the batt life gets low i turn on batt saver. And it works. Its not a bug.
Click to expand...
Click to collapse
But u mean the batt saver that turns on under 15% of battery or other one?
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?