Related
Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Edit:
This script is released to public domain, so it can be freely used for derivative works without permission!
Good thinking!
Thanks for sharing.
do we flash this in clockwork?
bradputt said:
do we flash this in clockwork?
Click to expand...
Click to collapse
Nope, it's just a init script for the ROM devs...
but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx
Awesome work you do
+10
This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!
bartito said:
but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx
Click to expand...
Click to collapse
You can push this script to /system/etc/init.d but it has some dependencies e.g. the interactive governor, perflock disabler when you want to underclock, ...
NeoPhyTe.x360 said:
Awesome work you do
+10
Click to expand...
Click to collapse
It was your idea, so same goes to you!
ivicask said:
This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!
Click to expand...
Click to collapse
That's the reason we are doing it this way: make the governor switching a bit more low level without SetCPU. But remember, this is not a update.zip and not flashable from recovery...
nice work. i really appreciate this. lets hope all the devs see this
FloHimself said:
Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Click to expand...
Click to collapse
Useless... Interactive governor sets low speed when idle.
sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
You are right, the interactive governor sets the lowest speed when idle. But idle != screen off.
sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
Applications and services can still ramp up the CPU speed during the screen being off, so not useless at all. Switching to the powersave governor for when the screen is off, will stop it ramping up during this time.
I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling
sfjuocekr said:
I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling
Click to expand...
Click to collapse
Nice, that`s something I`ve done later, too :
http://dl.dropbox.com/u/31174/android/90screenstate_scaling
Thought about extending it some more...
don't punch me, but... how can this be installed?
Kinda complicated, you`ll need a modified init.rc to run the scripts from /system/etc/init.d/ at startup, you have to push the governor modules and perflock_disabler module compiled for your kernel in /system/lib/modules/ the insmod scripts for the governors, perflock_disabler script and the script above to /system/etc/init.d/
FloHimself thank you very much for the scripts and the modules.
Is it me or is this script constantly looping with no breaks/sleeps?
I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?
sub0min0us said:
I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?
Click to expand...
Click to collapse
There shouldn't be any risks, but one of them will force its set freq, and the other one will be constantly changing it
Sent from my HTC Desire using XDA App
Thanks for clearing that out. I guess I'll have to uninstall it then not unless I install another rom. Thank you...
Post deleted.
New 2.1.1 advanced kernel working good here
Performance: interactive 806 - 1517
Normal: interactive 806 - 1517
Screen off: conservative 246 - 806
Powersave: conservative 246 - 806
Extreme powersave: conservative 246 - 476
Hope HTC will create a proper kernel dump, not one you have to modify that much to make it work
P.S. maybe change the VirtuousROM topic so that there is only a link to this topic for kernels? Maybe better to keep it al seperated?
Using new advanced kernel too,can`t find any problems at the moment.
Only sometimes short screen flicker if I press menu button and choose
"Background".
No wake issues!
Using:
Interactive governor: Max.1.4Ghz Min.368Mhz
Added extra profile for screen Off: Interactive both Max and Min set to 468Mhz
I'm gonna try both of you guys' settings and see if the wake /receiving call while screen off issues go away.
This was my setting as of last night:
2.1.1 Advanced Kernel
Normal: Ondemand 806 - 1497
Screen Off: Interactive 476 - 476
As of right now (10:30am ET), I'm using this:
Normal: Interactive 806 - 1497
Screen Off: Conservative 245 - 806
Wake issues, standard 2.1.1 virtuous 1.0.1 no setcpu or other profiles. Rarely screen won't turn off when hitting power button. I.press it and comes back on until the second or third try. Everyday, at least once ill have problems waking the screen up. Guess I'll have to go to advanced kernel with profiles and governors again, they never gave me issues.. Or stock kernel :/
Sent from my HTC Vision
Max / Min / Priority
Screen Off --> 245 / 245 / 100 (on demand)
[I have temp settings, which you can add on your own setting the prorities inbetween (interactive)]
Battery < 20% -> 245 / 245 / 75 (on demand)
Battery < 30% -> 368 / 245 / 70 (on demand)
Battery < 40% -> 691 / 245 / 65 (on demand)
Charging -> 1152 / 245 / 50 (on demand)
I have no wake issues or call receiving issues.
What governers do you guys use? I never really understood the governers much.. some people say use interactive.. others say on demand.. some conservative.. what are the differences? Someone could like me to a thread or whatever if they don't wanna explain.
But to be on topic I have the advanced kernel with screen on to 1gz/245 ondemand with screen off profile 245/245 ondemand. Going to start altering them to see what effects I receive (altering governers
Sent from my Rooted God-like HTC Vision.
Shaquiel Harris said:
with screen off profile 245/245 ondemand.
Click to expand...
Click to collapse
you haven't listened very well, it is BAD to set ANY profile to the same min/max level, especially that low... you will have wake issues, maybe not immediately, but overtime... rmk will tell you the exact same thing if you ask him, so it's not just me...
on demand is best for your regular (screen on) profiles, while interactive is best for your screen off profile... the reason for this, which I explained to you in the virtuous thread is because interactive doesn't constantly poll the cpu to see if it needs to be bumped up, it automatically scales as soon as the phone comes out of "idle" this helps prevent "lag" (that first couple seconds where things don't respond immediately even if the screen does come on instantly) when turning the screen on... not sure why you don't want to listen when others are trying to help you have a better experience...
What happens when i use this on stock sense 1.34 ROM (rooted)? Won't work?
Sent from my HTC Vision using XDA App
adipradana said:
What happens when i use this on stock sense 1.34 ROM (rooted)? Won't work?
Click to expand...
Click to collapse
rmk40 said:
These kernels are tested against Virtuous but should function on any Sense ROM based on RUU version 1.72 or newer.
Click to expand...
Click to collapse
sure , go ahead, give it a whirl... let us know what happens =)
The only thing that could make these kernels better is if they had Blast Processing.
benjamminzIS said:
you haven't listened very well, it is BAD to set ANY profile to the same min/max level, especially that low... you will have wake issues, maybe not immediately, but overtime... rmk will tell you the exact same thing if you ask him, so it's not just me...
on demand is best for your regular (screen on) profiles, while interactive is best for your screen off profile... the reason for this, which I explained to you in the virtuous thread is because interactive doesn't constantly poll the cpu to see if it needs to be bumped up, it automatically scales as soon as the phone comes out of "idle" this helps prevent "lag" (that first couple seconds where things don't respond immediately even if the screen does come on instantly) when turning the screen on... not sure why you don't want to listen when others are trying to help you have a better experience...
Click to expand...
Click to collapse
When did you explain that? I've never even seen a post like that. I logged into xda on my comp and noticed that the xda app doesn't see every single post like on the computer so maybe it didn't show me it. I listen a lot just I never seen/known you made a post about this so don't tell me what I do or don't do. Thanks a lot for the post, appreciate it.
Sent from my Rooted God-like HTC Vision.
Shaquiel Harris said:
When did you explain that? I've never even seen a post like that. I logged into xda on my comp and noticed that the xda app doesn't see every single post like on the computer so maybe it didn't show me it. I listen a lot just I never seen/known you made a post about this so don't tell me what I do or don't do. Thanks a lot for the post, appreciate it.
Click to expand...
Click to collapse
my apologies... apparently I was mistaken... I had gone over this so many times in the last 48hrs in virtuous rom thread, that I don't know which way is up anymore... lol... I didn't mean to be brash... it just gets tiring, because it seems sometimes, that no one reads anything past the most recent post... lol... I'm sure you can empathize to some degree... lol... again please accept my apologies =)
Hey guys, I've been experiencing wake issues on my G2, im currently running Virtuous rom 1.0.1 with advance kernel 2.1.1 SetCPU: Ondemand 998 - 1497 with no profiles...i've also tried other settings that are mentioned by other people here and avoided setting the minimuim frequency to 245, i always had it at 500 or higher and always using Ondemand governor with zero profiles....when i use standard kernel the waking issues disappear completely. any help would be greatly appreciated or if you need more info, please let me know, thanks
S&B
this is SB
Hi i just installed the advance kernel and everything works so far. How do i use setcpu? Is it an app downloadable via market? Thanks
Sent from my HTC Vision using XDA App
karlonicolas said:
How do i use setcpu? Is it an app downloadable via market?
Click to expand...
Click to collapse
Download it for free here ==> http://forum.xda-developers.com/showthread.php?t=505419
It's free for XDA forum members.
The support for this thread is AMAZING. Btw, car panel works great also. Cheers!
Sent from my HTC Vision using XDA App
If there was only a thanks button, thanks!
Sent from my HTC Vision using XDA App
karlonicolas said:
If there was only a thanks button, thanks
Click to expand...
Click to collapse
There is a "thanks" button. Find a thread that the person you want to thank wrote in, and click the big "THANKS" button in the bottom-right of that thread. Easy as pie.
I have a small question regarding setting a CPU Governor. I searched for a while but couldn't find any answer.
I am running AcesMod007-Lite, which has the cpu governor set to smartass. It seems to be okay, but especially when playing music it has some trouble, because it is trying to save too much battery. The music has a small click now and then. And i'm hoping changing the governor will help (if it won't please say so, then I can stop trying ).
So I want to change it to Interactive. This should be possible according to the ROM description (- Available Freqs: CPU interactive, smartass, powersave, ondemand, performance - by snq-)
What I tried to change it:
In recovery (after mounting system):
adb shell echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
(Here I got an error: The system can't find the specified path)
adb echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
(Same error)
adb pull /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor G:\
(This wrote a file with userspace? I changed it to interactive, then pushed it)
adb push G:\scaling_governor /sys/devices/system/cpu/cpu0/cpufreq/
(Upon reboot I checked it, and it was set back to smartass)
When the phone was on:
I tried thesame as in recovery, and got the same errors, only when using adb pull, the content of the file was "smartass".
Does anybody have an idea how to make this work?
I don't have Ace on my phone at the minute, but from what I remember I'm pretty sure there's a scaling script in the system/etc/init.d folder. Use root explorer or similar and long press, open with text editor, then change smartass to the governor you want.
Reboot the phone and it should now be using the one you selected, I hope
Use ondemand governor. Also had problems with music playing with smartass governor in other roms. After switching to ondemand they never occurred again.
Swyped from Oxygen with Transparent XDA App
@mick
Thanks! You were right. Now it automatically switches to ondemand (thanks MatDrOiD).
But for some reason the music still clicks . Should I increase the processor max freq for screen off, or does anybody know any other solutions?
I dont really know any other solution other than to ask, did you change both governors, screen on and screen off?
btw the screen off I use "min 128000" and "max 384000"
yes, try upping the max til the clicking stops
Yes I did changed them both.
My frequencies are for screenoff (in that same file):
SLEEP_GOVERNOR_FREQUENCY_MIN="245000"
SLEEP_GOVERNOR_FREQUENCY_MAX="384000"
So I think that should be okay.
Somewhere I read that it was an possible issue with every Sense HD ROM, because there was an error in the HTC code. Then it would be unsolvable.
I am going to try setting the min to 128, maybe that magically helps.
PerfectLight said:
Somewhere I read that it was an possible issue with every Sense HD ROM, because there was an error in the HTC code. Then it would be unsolvable.
Click to expand...
Click to collapse
I use insertcoin at the moment and don't notice it.
It might not be the cpu settings, I don't know what else is tweaked in the rom, but if there are other things then it could possibly be that, memory etc.
I'm pretty sure I read in the thread when I used Aces that installing setcpu would disable the scaling script. Maybe install it and see if your problem clears, nothing to lose
It has been solved! I now use a different build.prop, which seems optimized in some way.
The clicking is gone, and the entire phone seems more responsive .
Thanks for the great help!
I froze all of the DRM services as shown in the picture below, yet it is still hogging battery resources as shown below.
Does anyone know how this is possible and how to fix this?
I'm using SleeperRom 1.0.11 and Shadow Kernel 1.03+.
Thanks.
That doesn't help. Percentages don't mean anything. ALL your applications have to run through android system. Take off android from your phone and you can't run anything. To see what is using your battery check Betterbatterystats. What files have the most time on them? Check processes and partial wakes if your battery drains while your phone is in standby. Also get CPUSpy and make sure your phone goes into deep sleep when in standby and not on charge.
Just because it lists DRM in the android system does not mean it is using more than a second or two of quick checking services. This is why some apps screw up if it is removed instead of just frozen. It has to check if the files are still on your phone.
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
after checking betterbatterystats, I don't even see the DRM service anywhere within the app, so I guess that is good.
I guess my phone just doesn't agree with the update to sleeper 1.0.11 and shadow 1.03+
akuentzler said:
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
Click to expand...
Click to collapse
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
kennyglass123 said:
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
Click to expand...
Click to collapse
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
akuentzler said:
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
Click to expand...
Click to collapse
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
kennyglass123 said:
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
Click to expand...
Click to collapse
I think the major difference is the shadow kernel and the use of voodoo color. I was previously on samurai 2.0.6 or 2.0.8 i think.
I have always had auto brightness on. Betterbatterystats did not reveal anything out of the ordinary.
I guess i'll just try a new rom/kernel combo and see if I can get better results. Thanks for your help Kenny. Betterbatterystats is a nice tool i had not known about.
No problem. I did find that voodoo color and the voodoo control app use a little extra battery plus having to increase brightness a little with voodoo color used up a little more battery.
Sent from my SPH-D700 using XDA App
I'm running Dr.Ketans V3 Rom on my GT-N7100, I'm geting major stuttering during music playback when my screen is off, I've been told its a kernel issue, my question is; are there any kernels which support Dr. Ketan's V3 rom that i could try out?
Seriously?
Honestly it never happened to me! Think that's strange. BTW I think soon we'll get new kernels from the developers. By now Dr. Ketan said there's no possibility to change it, if I remember correctly, even in the Aroma Installer it says "new kernels coming soon"
thanks
iamiupa said:
Honestly it never happened to me! Think that's strange. BTW I think soon we'll get new kernels from the developers. By now Dr. Ketan said there's no possibility to change it, if I remember correctly, even in the Aroma Installer it says "new kernels coming soon"
Click to expand...
Click to collapse
thanks for the reply, I'll wait it out.
We won't get any custom kernels until Samsung releases 4.3 source code. (i.e. After 4.3 official release.)
Sent from my GT-N7100 using Tapatalk
Manjunath324 said:
We won't get any custom kernels until Samsung releases 4.3 source code. (i.e. After 4.3 official release.)
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thay all read have
Not yet happening to me. Wait for the official release instead.
I think there is some Google issue. I have used 2 4.3 ROM on my Note II and both the times my Google accounts vanished. All my data is synced with Google account and there is nothing i can do but sync everything again. I did read some place that this is the issue with the ROM. Aren't others facing this issue. I have no options but to go back to 4.1.2 XXDMG1 ROM.
Music playback stuttering / choppy with Dr. Ketan's V3 ROM / Android 4.3 leaked FW
evilgenius101 said:
I'm running Dr.Ketans V3 Rom on my GT-N7100, I'm geting major stuttering during music playback when my screen is off, I've been told its a kernel issue, my question is; are there any kernels which support Dr. Ketan's V3 rom that i could try out?
Click to expand...
Click to collapse
Yes. I had the very same issue. Music playback stutters upon screen-off with Dr. Ketan's V3 ROM. I discovered a work-around for this:
1) Try turning off 'Power-saving' mode and check whether the problem persists. If it does not solve the issue, you could proceed to step 2 below.
2) Download and Install 'System Tuner' app from play store. The app will need root access to be effective.
3) Launch the app and go to the 'Tweak CPU' screen. Make sure you note down the default settings for the CPU Governor Type and Min and Max values before making any modifications.
4) I had changed the Gov. type from 'pegasusq' to 'Ondemand' and set the min value to 1000 Mhz (1ghz).
5) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Governor-->Value should be "No governor changes"
6) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Max frequency-->Value should be "No governor changes"
7) Leave the app running in the background and then go back to your music playback. Now the stuttering/choppy should not appear again.
8) Post your music play back session, I would recommend using 'System Tuner' to revert back to the original / default values, just to be safe.
Step 5 and 6 are very important and is not to be missed.
It appears that the problem is because the CPU speed is scaled down to a very low value for conserving power upon Screen-off with this ROM. Not sure whether this is a problem with the ROM or if its a problem with the leaked Android 4.3 FW.
Important Note: Do this at your own risk. CPU governor changes if not done properly can lead to over-heating and even damage to your device. I take no responsibility for your actions and the consequences by following the above ideas/techniques.
If you would like to understand more on the CPU governor and their behaviour you can refer to http://forum.xda-developers.com/showthread.php?t=1736168
degakc said:
Yes. I had the very same issue. Music playback stutters upon screen-off with Dr. Ketan's V3 ROM. I discovered a work-around for this:
1) Try turning off 'Power-saving' mode and check whether the problem persists. If it does not solve the issue, you could proceed to step 2 below.
2) Download and Install 'System Tuner' app from play store. The app will need root access to be effective.
3) Launch the app and go to the 'Tweak CPU' screen. Make sure you note down the default settings for the CPU Governor Type and Min and Max values before making any modifications.
4) I had changed the Gov. type from 'pegasusq' to 'Ondemand' and set the min value to 1000 Mhz (1ghz).
5) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Governor-->Value should be "No governor changes"
6) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Max frequency-->Value should be "No governor changes"
7) Leave the app running in the background and then go back to your music playback. Now the stuttering/choppy should not appear again.
8) Post your music play back session, I would recommend using 'System Tuner' to revert back to the original / default values, just to be safe.
Step 5 and 6 are very important and is not to be missed.
It appears that the problem is because the CPU speed is scaled down to a very low value for conserving power upon Screen-off with this ROM. Not sure whether this is a problem with the ROM or if its a problem with the leaked Android 4.3 FW.
Important Note: Do this at your own risk. CPU governor changes if not done properly can lead to over-heating and even damage to your device. I take no responsibility for your actions and the consequences by following the above ideas/techniques.
If you would like to understand more on the CPU governor and their behaviour you can refer to http://forum.xda-developers.com/showthread.php?t=1736168
Click to expand...
Click to collapse
This works for me, thanks!!
degakc said:
Yes. I had the very same issue. Music playback stutters upon screen-off with Dr. Ketan's V3 ROM. I discovered a work-around for this:
1) Try turning off 'Power-saving' mode and check whether the problem persists. If it does not solve the issue, you could proceed to step 2 below.
2) Download and Install 'System Tuner' app from play store. The app will need root access to be effective.
3) Launch the app and go to the 'Tweak CPU' screen. Make sure you note down the default settings for the CPU Governor Type and Min and Max values before making any modifications.
4) I had changed the Gov. type from 'pegasusq' to 'Ondemand' and set the min value to 1000 Mhz (1ghz).
5) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Governor-->Value should be "No governor changes"
6) Navigate to 'boot settings' menu (icon next to Gov. speed control)------> 'Screen-off behaviour'---->Max frequency-->Value should be "No governor changes"
7) Leave the app running in the background and then go back to your music playback. Now the stuttering/choppy should not appear again.
8) Post your music play back session, I would recommend using 'System Tuner' to revert back to the original / default values, just to be safe.
Step 5 and 6 are very important and is not to be missed.
It appears that the problem is because the CPU speed is scaled down to a very low value for conserving power upon Screen-off with this ROM. Not sure whether this is a problem with the ROM or if its a problem with the leaked Android 4.3 FW.
Important Note: Do this at your own risk. CPU governor changes if not done properly can lead to over-heating and even damage to your device. I take no responsibility for your actions and the consequences by following the above ideas/techniques.
If you would like to understand more on the CPU governor and their behaviour you can refer to http://forum.xda-developers.com/showthread.php?t=1736168
Click to expand...
Click to collapse
thanks for helping !!
but is there's a permanent solution for this .. i feel that this App is affecting my device and sometimes the temperature goes over 40 ??
Ramyjelda said:
thanks for helping !!
but is there's a permanent solution for this .. i feel that this App is affecting my device and sometimes the temperature goes over 40 ??
Click to expand...
Click to collapse
As the poster said, do it only temporarily when you're listening to music, then change back
Ramyjelda said:
thanks for helping !!
but is there's a permanent solution for this .. i feel that this App is affecting my device and sometimes the temperature goes over 40 ??
Click to expand...
Click to collapse
Try the audio player "Player Pro". Within Player Pro there is an option to download and activate a DSP pack. Once the DSP pack is activated, it offers you the option to adjust the "Audio Buffer" and also set the "Audio Priority". I set both of these to the maximum values and that seems to solve the problem for me.Of-course this is an app specific solution.
You may need to buy Player Pro to get all the features. I can't remember whether the free version offers, DSP features, cos I bought it long time ago and find it to be one of the best audio player apps in the marketplace.
running hot
Ramyjelda said:
thanks for helping !!
but is there's a permanent solution for this .. i feel that this App is affecting my device and sometimes the temperature goes over 40 ??
Click to expand...
Click to collapse
my note2 feels like it could bake a cake sometimes. And running nothing but chrome.
victorfrank said:
my note2 feels like it could bake a cake sometimes. And running nothing but chrome.
Click to expand...
Click to collapse
You should immediately revert it to the original/initial settings. BTW: have you tried Dr. Ketan ver 6.1 ROM? I did not find the problem so much with the latest ROM. Also, do check whether you have power saving off.
degakc said:
You should immediately revert it to the original/initial settings. BTW: have you tried Dr. Ketan ver 6.1 ROM? I did not find the problem so much with the latest ROM. Also, do check whether you have power saving off.
Click to expand...
Click to collapse
Hi I am on Dr Ketan ver 6.0 with the patch to 6.1 he released. power saving is off and all settings are original. maybe its the battery, but it was fine on 4.1.2
---------- Post added at 08:30 PM ---------- Previous post was at 08:20 PM ----------
victorfrank said:
Hi I am on Dr Ketan ver 6.0 with the patch to 6.1 he released. power saving is off and all settings are original. maybe its the battery, but it was fine on 4.1.2
Click to expand...
Click to collapse
thanks will try, and yes im on 6.1
---------- Post added at 08:47 PM ---------- Previous post was at 08:30 PM ----------
degakc said:
You should immediately revert it to the original/initial settings. BTW: have you tried Dr. Ketan ver 6.1 ROM? I did not find the problem so much with the latest ROM. Also, do check whether you have power saving off.
Click to expand...
Click to collapse
found the problem, skype in the background
Hello guys, i have just donwloaded the dr ketan v11 n7100 nh2 rom for my note 2. I installed it but the phone is stuck on boot logo (samsung). im waiting to boot for 40 minutes now but nothing comes up... what seems to be the problem?