Related
I didnt want to root my phone HTC WILDFIRE because I am a little noob at these things a I thought I would totally destroy my phone.
But I found out that it is not so hard to root it as I thought, so today I succesfully rooted my phone. Than I wanted to overclock my procesor from 528 Mhz to I think 768 by downloading new kernel etc... Everything went good. I succesfully installed(or what, I said I am a little noob) that new kernel and was happy that my Wildfire will be faster.
But now I can see that my phone is lagging more, sometimes it freezes what i couldnt see before when It had original kernel.
HOW IS IT POSSIBLE?
Pls help
Do you have SetCPU installed? Then turn it a bit down, till 690~710 Mhz
Maxing it totally out can make your phone unstable. Think about it like a car, when it has 100 hp's and you tune it to 150 hp's things might break.
From stock 528 to 768 isn't a walk in the park, it's +45%
Yes I have setCPU and when I set my procesor to about 710 Mhz it lags and freezes. When I set it to about 580 it is doing the same. The only one solution of this I think is to reinstal the kernel.
Now I have 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1.
That is the full name of it. And in setcpu info it shows me before the version ( 2.6.32.21-HCDRJacob-ga91 e 73b- [email protected] 1) Linux versio... Maybe thats the problem???
And I have to find some solution as fast as possible because sometimes when somebody calls me I cant answer because of a biiiig lag. And then I cant do anything.
Thx for help
What id the minimum speed set to? I wouldn't go below 160. And my max is 672mhz.
Are you running different profiles or just the main profile in setCPU? Mine used to lag when i had a few profiles running but i have removed them all and only using the main profile and the lag has now gone.
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
I tried many options and at last its OK. firstly I had a big difference between max and min of my procesor at setCPU, so I tried to set it to min about 630 and max about 700.
Now it is OK I dont know how, but I am happy the ****y problem is somehow solved and everytjing now goes very smoothly, thx u all
ephbee said:
when i went to wildpuzzle i found whatever speed i set my processor through set cpu it froze about 4-5 times a day. after flashing the kernel to remove overclocking it has not frozen in a week. everything really responsive, checking auto detect speeds with set cpu shows max 528mhz min450mhz
Click to expand...
Click to collapse
So what kernel did you flash it to?
I'm getting about 1-2 days battery life after rooting.
I've removed Phone.apk and the other one (can't remember what it's called).
I think the short battery life is because certain apps are trying to download in the background, even when WiFi is disconnected, I can't see what else it could be:
- market
- various rss readers
- widgets
- more?
I think this is happening even when these programs are not shown in a basic task manager (the task manager resulting from the n button long press rework).
I should add, how much battery life do you get after rooting?
About 1 month but I charged it only twice
I read that some had battery drain after a month I'm still waiting to figure it out :-$
NookTouch 1.0 rooted with touchnooter 1.6. 24
Sent from my GT-P1010
What do you have in Nook Color Tools > Settings > Battery use ?
thanks mdall,
it's 48% wifi (not worried about that)
43% phone idle
& 8% display, system 2%
I have 85% for Cell standby, is this normal?
why do I have something like that on a non-phone device?
MOD: I've found a thread about it: http://forum.xda-developers.com/showthread.php?t=1189047
glezmen said:
I have 85% for Cell standby, is this normal?
Click to expand...
Click to collapse
If you keep the NST on for long periods of time without reading, then the answer is yes. Otherwise, I couldn't tell you.
glezmen said:
why do I have something like that on a non-phone device?
Click to expand...
Click to collapse
Well, there might development considerations for not excluding the culprit files (mainly: Phone.apk and TelephonyProvider.apk) but, then again, after rooting they can be removed with no apparent damage to the device so...
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Disabling phone apps for good: How?
GabrialDestruir said:
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Click to expand...
Click to collapse
Sweet...
So, how we disable those apps for good, so they wont't suck the battery dry??
Awaiting your kind reply,
Sebástian,
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with, and it won't add to wifi download - even though I notice that wifi traffic is heavier that from my phone, but I have much experience with android, so I can't really tell.
Disabling phone apps for good: How?
apeine said:
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with
Click to expand...
Click to collapse
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
sarmasm said:
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
Click to expand...
Click to collapse
And if it isn't there, other parts of the system are wasting CPU cycles trying to find and start it. Been there before, done that, learned that removing things without having good reasons to do it can lead to wasting a lot of time.
Looking at how much the Nook stays on each cpu state, I have found some strange issues.
It seems, that without modifying anything, it stays a whole +1 minute at 800mhz after the last touch to the screen, and then comes back to 300mhz and stays there, this is not desirable at all, even for just reading.
Can someone install any program as cpuspy to check if it is a common issue?
Here is a link to the market, its free:
https://market.android.com/details?id=com.bvalosek.cpuspy&hl=es
Do something, open an app, close it, and w8 3 minutes, if the cpuspy reports +1 or more minutes of 800mhz state, then the issue is there.
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
I need someone to check what I'm saying to look further into this issue.
Setcpu is free for xda members, http://forum.xda-developers.com/showthread.php?t=505419
Allthough if you can buy it, its a grate app, and devs need donations.
eded333 said:
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
Click to expand...
Click to collapse
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
ros87 said:
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
Click to expand...
Click to collapse
That makes sense, and is what I thought about the gobernors.
The problem still resides on the time the cpu stays at max state after it has stopped being used.
I'm taking a look at sys/devices/system/cpu/cpu0/cpufreq/ at the moment, strangely under cpuidle I found a folder named conservative..... could that have been introduced by SetCpu, or am I talking bull**** ?
It seems the kernel supports the tipical gobernors: conservative, ondemand, userspace, performance, can't find any trace of the one the extra one that uses the Nook Touch, so it must be somewhere else.....
---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
eded333 said:
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
Click to expand...
Click to collapse
Sorry, I don't have any in-depth knowledge about this.
And maybe I misused the term "service", I wasn't really referring to a daemon.
There are some hints in init.rc
Code:
# Enabling sleep in idle path
write /sys/power/sleep_while_idle 1
# Enabling OFF mode
write /sys/power/enable_off_mode 1
# Enabling Voltage OFF in idle path
write /sys/power/voltage_off_while_idle 1
# Enablig DVFS with conservative governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
# Enabling SmartReflex for Zoom3 OMAP3630
write /sys/power/sr_vdd1_autocomp 0
write /sys/power/sr_vdd2_autocomp 0
I guess you have to grep your way trough the sources to find out what B&N modified for this particular platform.
Here's some platform documentation from TI (Gingerbread related, but still)
http://processors.wiki.ti.com/index...t-2.1_PortingGuides#DVFS_-_CPU_Freq_framework
Thanks ros87, I'll look into it.
Thanks - the link to the processor wiki is very helpful for a newbie like me to learn how these things work. I never understood that the userspace governor had to be set before the cpu frequency could be set.
Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?
Can anyone please test 9505 (the 4 core version of S4) on following two applications ?
1.) Droidfish (chess engine with UI)
a) settings -> threads -> 1
b) back to chessboard -> click "M" -> select mode = "Analysis mode"
c) keep it running for at least 30 seconds (from the starting position) and write down the "nps" (nodes per second) number - mine is showing 137k which is the same as on my old galaxy S2 at 1.2 GHz
2.) Counting Benchmark
a) Count To -> 10 Bilion
b) Threading -> Single-Threaded
c) Start Benchmark and write down number of seconds it took, mine is 62.76s which is very close to what I get on my old SGS2 (74.418s)
When I check how much time the CPU spent in which state (with CPU spy plus) - it shows me that:
On S4 during the "droidfish" test it spent 100% in 918MHz state (and 0% in 1890MHz state ???) - while on S2 it shows of course 100% of time being in 1.2GHz state (max for S2)
On S4 during the "Counting Benchmark" test it spent like 2/3 of time in 918MHz state and and 1/3 of time in 1890MHz state
PS: I have turned off all power savings & smart scroll / air gestures etc. features I know of (and even tried the tests while charging)
SHOULDN'T S4 RUN EVERYTHING MUCH FASTER THAN OLD GALAXY S2 ??? - that is including the single threaded performance ?
Maybe the app doesn't work properly on S4 and doesn't know how max out the CPU on S4, thought about that?
Single threaded performance is the same on S2 and S4, you say? I might have understood you wrong?
mkrmec said:
Maybe the app doesn't work properly on S4 and doesn't know how max out the CPU on S4, thought about that?
Single threaded performance is the same on S2 and S4, you say? I might have understood you wrong?
Click to expand...
Click to collapse
Yes single threaded and most likely even 2 threded performance is the same in doridfish.
In "Counting benchmark" it's only marginally better - it should be much higher if for nothing else then just due to the difference in frequency (1.9GHz vs. 1.2 GHz)
Are there any other integer benchmarks / test apps (for non - floating point arithmetics) where I can select number of threads ?
Btw the droidfish app is the latest one from Google Play on both phones - and I even tried installing it directly to clean (factory reste) S4...
Edit: found this thread http://forum.xda-developers.com/showthread.php?t=2258210
Kapitein187 said:
Ran it on 4 cores (i9505) and saw for the first few turns values of arround 680 but i think when there are more difficult turns it will get higher.
Click to expand...
Click to collapse
That is aobut 2x more I see when I run the test from start position with 4 threads enabled on my S4 i9505
Was your device warm/hot when you started it? Could be a throttling issue.
shox22 said:
Was your device warm/hot when you started it? Could be a throttling issue.
Click to expand...
Click to collapse
No it wasn't - it was close to room temperature before and also during the droidfish test ( but it gets warm after running some GPU intense benchmarks / games etc. )
Minor update: I've run all the benchmarks they used here:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/4
and had similar results in all of them - yet the droidfish seems to perform so badly...
Please can anyone try the droidfish test on i9505 under the conditions mentioned at the beginning of this thread and report the results ?
I just don't understand if this is a hardware issue or a firmware issue or droidfish application issue (the last thing is highly unlikely as it simply uses one CPU core to 100% - failure to do so on the application side would seem quite absurd)
And btw kies reports my device as having the latest firmware (the one that ends with MDE)
comrad said:
Minor update: I've run all the benchmarks they used here:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/4
and had similar results in all of them - yet the droidfish seems to perform so badly...
Please can anyone try the droidfish test on i9505 under the conditions mentioned at the beginning of this thread and report the results ?
I just don't understand if this is a hardware issue or a firmware issue or droidfish application issue (the last thing is highly unlikely as it simply uses one CPU core to 100% - failure to do so on the application side would seem quite absurd)
And btw kies reports my device as having the latest firmware (the one that ends with MDE)
Click to expand...
Click to collapse
Pls check my thread: http://forum.xda-developers.com/showthread.php?t=2451001
Same issue also on LG G2 - which probably indicates Snapdragon hw issue or droidfish sw need to be optimized for snapdragon. I sent emails for LG & Droidfish programmer to comment on that...
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
To be honest, I've never seen this before, have you tried flashing the stock firmware to see if it helps?
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
Check the problem from a command shell over adb. Try this with the screen off and no apps running in the foreground.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Repeat a few times to verify the cpu isn't scaling down. If you have superuser access and busybox installed, you can prefix the command with 'busybox watch -n 1' and it'll print every second until cancelled (CTRL+C). If the frequency never drops below 787200 kHz, use the 'top' command to work out which process is using most cpu time.
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
on /etc/init.qcom.post_boot.sh scaling_min_freq is set to 787200 :
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown -h system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# add read permission to max cpu frequency interface
try to set it yourself to 300000 after booting and see afterwards if it sticks, if it does you could just modify the script ...
Solved (or not)
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
Do you have an SD card in? I'm wondering if you still see this symptom with the card removed. I say symptom because I seriously doubt the governor has a scaling bug.
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
i just noticed i have exactly the same behaviour, thanks for pointing it out. waiting for lollipop and hope it wil fix this problem
same 787 min value
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
vaisakmct said:
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
Click to expand...
Click to collapse
In kernel ramdisk the cpu is setted to be between 787Mhz and 1.2 GHz, I don't know why opening the camera change this. BTW if you are rooted you can change it using apps like trickster mod and similar
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
I have unrooted new moto g .how can i underclock the cpu of this phone?
Sent from my XT1068 using XDA Free mobile app
You can't without root
Sent from my XT1028 using XDA Free mobile app
lollipop 5.02 have not solved this problem
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
i am from india and MOTO g2 updated to lollipop 5.02 in XT1068 and this issue is not yet solved.
I also have this issue on 4.4. Good that there is a work-around. I raised a problem with Moto Support and I suggest more people go this route, so they are aware that this is something they really should fix
I get the impression that is actually by design, rather than oversight. Given the ridiculously aggressive LMK settings, the reduced number of hidden apps (12? On a phone with 1GB of RAM? Really?!) and this scaling issue, it rather looks like Motorola tuned the software for the phone to appear snappy on first use. It looks good in reviews but sucks balls during intensive/extended use.
rufflove said:
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
Click to expand...
Click to collapse
thanks for this tip, works well! in kernel adiutor there are other settings to change for better performance?