I've set my main to 800/200 conservative. Occasionally I go back into the application and see that it has changed to 1200/200 on its own.
I check time in each state and 1200 is showing up on the chart, so I know its not false or a glitch. Why is this happening?
I've updated my kernels, I've switched to Entropys from Siyahs and its still happening, I'm not too sure if its the kernels fault though, any ideas?
CollegeProfesor said:
I've set my main to 800/200 conservative. Occasionally I go back into the application and see that it has changed to 1200/200 on its own.
I check time in each state and 1200 is showing up on the chart, so I know its not false or a glitch. Why is this happening?
I've updated my kernels, I've switched to Entropys from Siyahs and its still happening, I'm not too sure if its the kernels fault though, any ideas?
Click to expand...
Click to collapse
Do you have an alternate profile set somewhere?
Also, unless you reset cpuspy counters after boot, there will be some 1200 MHz time, since SetCPU doesn't reset the limit until after boot.
You probably have, but I have to ask just to make sure...are you sure you checked the "set at boot" option?
Entropy512 said:
Do you have an alternate profile set somewhere?
Also, unless you reset cpuspy counters after boot, there will be some 1200 MHz time, since SetCPU doesn't reset the limit until after boot.
Click to expand...
Click to collapse
I have 2 profiles set, but theyre 500/200 for when the screen is off an for when im under 50% battery. Phone is still using 1200mhz though, even though its set to never do that.
raptor102888 said:
You probably have, but I have to ask just to make sure...are you sure you checked the "set at boot" option?
Click to expand...
Click to collapse
It is, thanks
Related
hi guys
For those that haven't heard of or seen an Sleep of Death (SoD) in action , it is where your phone does not respond to any user input whilst it's in sleep mode thus making the phone unusable since you are unable to wake the phone. The only way to recover is to either force reboot the phone, receive a call or call yourself from another phone.
I have encountered SoD four times til now, on KE2, KE7 and Now KF2 .
I don't think its got anything to do with the ROM, this has happened for me on Cognition, VillainRom , CF-root on stock Roms.
looking around the web it seems it might be a kernel/driver issue and remains unfixed (not sure)?
Anyone knows workarounds? Any Devs that are working on this?
Thanks
I haven't encountered this yet and I've also tried a bunch of different ROMs. Are you by chance overclocking or underclovking/UVing at all? If so, that could be the culprit. If not, then its hardto say what may be causing it other than an app the phone may not respond well with.
I had this happen once. I tried many ways to wake it up even charging, the charging sound comes up but the screen wont wake. Had to reboot.
Havent happened again though.
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
ke3pup said:
I haven't under/over clocked the CPU at all but from what I understand it has nothing to do with CPU frequency but more so a bug in kernel or in one of the drivers.
Its not easy to reproduce but its definitely there, I'm hoping it'll be addressed in cyanogen rom when its out given the fixed SoD somewhere in 7.0rc I think.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
On my ace this issue occured when the wifi was on. The phone goes into "sleep mode" and needs a reboot (press the power key for 10 seconds).
I was not able to find the exact conditions but it was more promient when 3g was also switched on.
Does your issue occur only when the wifi is on?
This has happened 4-5 to me
as well. I have found that a putting the phone on charge can free it. But its a real pain if it happens out and about, I had to take the battery out to get it to work
i got it 2-3 times while using "Green Power" app.
Again this has nothing to do with an app/rom..etc. you may think a certain app you installed its causing it but in case of SoD that's highly unlikely. The source of problem is else where.
"@cyanogen: @Bradart @1000hams try a nightly build if you are on 7.0. Google fixed bugs for 2.3.4 that can cause that (7.0 is 2.3.3)."
Click to expand...
Click to collapse
The above is a quote in response to SoD question (don't know which device, but android < 2.3.4) which to me suggests another bug in 2.3.3 that has been fixed in 2.3.4.
http://forum.xda-developers.com/showthread.php?t=1238478
Here's the solution I hope it helps... it worked for me
Bug Report - SGS2 (Sleep of Death)
Please use this link to report the bug:
code.google.com/p/android/issues/detail?id=21607&thanks=21607&ts=1320690472
I think I found a way to avoid SoD (Sleep of Death)
I'm new on the forum And that SoD problem annoyed me for so long and I kept searching.... But I think I finally found why we kept getting SoD.
Ok so I'M NOT SURE, but Try following those steps and be sure of every single thing and then tell me if you guys keep getting SoDs..
1- "Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state." - droidphile
2- I think some of us don't do "clean flash of our ROM", so you guys need to follow those exact steps from that link
http://forum.xda-developers.com/showpost.php?p=28395322&postcount=3
Or I will just write them again...
1- Reboot into recovery (Turn off your phone then press and hold the keys: Volume Up + Power + Home)
2- Wipe Data / Factory Reset
3- Install the Main ROM file
4- In AROMA installer select "Custom Installation"
5- Choose depending of your taste
6- When AROMA installer finish untick the "Reboot Now" option
7- When you're back on the recovery go to Advanced
8- Wipe Dalvik Cache
9- Fix Permissions
10- Wipe Cache Partition
11- Reboot
12- When you get the step for add your Google Account, if you don't have a WiFi enabled or you can' add it, skip it
13- When you boot into the system, it's probably that you don't have data enabled (3g, H+) just reboot the phone
14- When you boot again into the system, the data will be enabled and you can do the configuration of Google Account (if you don't do this step before)
This is the moment for install all the extras like themes, mods, fixes, kernels, etc.
3- ok and NOW After your "CLEAN Flash of ROM" When you use Titanium backup Root application to restore your applications, DONT restore the things with RED text color. Restore ONLY the things with green text color.
In other words, restore only apps with their data and NOT all system data.
4- Ok and Once you did that. About the Governor you use, I think we push the limits of the CPU and the phone just can't resist the tweaks we did and a SoD appears. So try these settings if you have Siyah Kernel
Minimum CPU frequency: 200 Mhz
Maximum Frequency: 1000 Mhz
Governor: luzactive
Default I/O sheduler: SIO
So try THAT and tell me if you guys keep getting SoD ...
lol I didn't get SoD since 2 days And I hope it could help. Because installing Wake My Android Pro, or WakeLock or Load Monitor just DIDN'T work for me -__-
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
screenager said:
i stumble upon this problem whenever i use too harsh UV settings(depends from kernel to kernel). also my device SoDs whenever i use 100mhz as the lowest step- again with some kernels it tolerates it. my guess is: every phone is slighty different, so you just have to experiment with yours and find the best settings for your specific hardware (you dont say xD)
Click to expand...
Click to collapse
I understand your point of view, but by the way, I read a lot of that forum, and putting minimum frequency at 100Mhz might be Bad for your phone for 4 reasons:
1) When you receive a call, the call might lag because it needs absolutely a minimum of 200Mhz, so setting your CPU minimum frequency at 100Mhz might cause probs for phone calls.. ( i read that somewhere on XDA but dont remember where...)
2) Moreover, "It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online."
3) "200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon."
4) "200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz."
Those 3 last reasons came from droidphile I'm not the author of this, but minimum frequency should stay at 200Mhz
i want reactivate this thread, because I think there are some users who still have this problem like me.
As far as I recognized there seems to be more reasons for SoD.
All seems to have begun with Android 4.1.2 and just keeps on until now.
I have tried some kernels and runs now Dori 9.33 and see how it works.
It seems that there are some kernel issues as well as some apps and some constellations of SD-cards.
But no one has a real solution.
I read about a "indish kernel" for the i9100g models, but also some who reported SoDs with this kernel.
But I found no real solution for our i9100.
I have attached a logfile (catched with Catlog) which I recorded until my last SoD.
In my case, I can also call my phone and the caller hears it ringing, but my phone stays black without sound and unresponible.
The only thing is to hold the power button for 10 seconds and reboot it.
just to tell:
nearly 24h without a SoD with my combination
BUT: I have not used my camera so far! And I think camera & media scanning has something to do with it.
If everything is running until tonight, I will try my camera and see the result.
after nearly 2 days
:good: nearly 48h working, so I will keep my combination.
But it is interesting, that nobody has any problems although you can read a lot about this problem.
after more than 2 days:
and here we go. SoD :crying: but 48h is better than nothing
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
you can run out of CWM and install as a zip.
So far it is recommended to run 1. GS2ROMClean, reboot, then 2. Fix Partitions to ensure you have clean partitions
Be patient! 2. runs very long, up to 2 hours and the phone becomes very hot. So I think power connection is absolutely recommended
BUT NOT TESTED COMPLETELY BY ME
what I do not know is, how often these scripts shall be used
You could run the ROM clean as often as you want. If the other doesn't fix it after one time, no point running it again. In saying that, I'm not sure if there would be any benefit from running the first one more than once anyway.
Sent from a galaxy far, far away
lavemetoo said:
a lot of things might come from corrupt files.
There are 2 scripts which will clean your partitions and try to fix broken files
1. GS2ROMclean made by hawkerpaul
2. Fix_Partitions_v1.0.2.zip made by Computoncio
Click to expand...
Click to collapse
1. runs very fast, took round about 10 seconds. Reboot was successful afterwards. All was working.
Now I run 2. - info will follow - would be great, if there were a kind of progress bar or a kind of information. So you don not know if it hangs or not.
script 2. ended after 1h with a warning. Now run again?
Code:
/dev/block/mmcblk0p10: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p10: ********** WARNING: Filesystem still has errors **********
/dev/block/mmcblk0p10: 11854/131072 files (5.4% non-contiguous), 524288/524288 blocks
Checking preload partition:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 544/32768 files (0.0% non-contiguous), 29992/131072 blocks
Automatic Fix Partitions finished at 30-07-2013 14:10:33
attached is the complete logfile
ATTENTION: My phone was connected to USB and lost 10% battery during this script operation!
I need to know wat setting wrk the best for TV with setcpu. My battery is worst since I've rooted and its making me want to unroot. Help please!
mi2gurlz said:
I need to know wat setting wrk the best for TV with setcpu. My battery is worst since I've rooted and its making me want to unroot. Help please!
Click to expand...
Click to collapse
Well, first thing first. Let us know what ROM, kernel, and radio you are using. Those things are the major factors that effect your battery life.
Also, what is your current setcpu settings?
1025MHz max/245MHz min are the stock frequencies. Setting the CPU above that will have an impact on your battery life. I really don't find a reason to overclock this phone.
If your using SetCPU, setting up a "Screen Off" profile is a must. Set it to 245min/max, so that when the screen is off, the CPU runs at a very minimal speed, saving you a lot of battery life.
I also recommend using Green Power. It is a free app in the market. It is a lot like Juice Defender, only I think it's simpler to use.
You can set the app to turn off data when your screen is off, and turn back on when you turn the screen on. Also, you can set it to turn data on (for example) every hour, for 1 minute to sync your data, then turn back off, this way you will still get your notifications.
I find it helps my battery a lot.
Thanks I will try that. I was using Ginger3dth3ory radio mr2 i think and i dont remember the kernel. I just flashed another ROM and its synergy_rls1-mecha kernel is [email protected] #1 and i assume the radio is the same since i dint get a new one. setcpu is set at 1024/245.
Hi I got this phone couple of days back. It came flashed with latest Android 4.0.3 (20120608-154131)
I have rooted it using zopoROOTby_Jaynes_android4.0.
It's working fine, but seems the battery life is ridiculous and the battery information is also not reliable, especially after restarting the device
(Sometimes it suddenly decreses a lot and vice-versa).
Also GPS, I tried it out in the open for like 15-20 mins it finds 4-6 sats but DOESN'T lock on.!
And then the market had some incompatible apps, I did the XML trick, didn't work...removed the 5 files again and then gave up, all of a sudden after a restart, market is fully accessible!! (Weird!)
I have backed-up my apps using Titanium free but I want to install CWM recovery. I do not know the exact procedure to follow for the same.
I just want to have the CWM recovery and not want to flash whole ROM again...How to do it???
Also please give me any important suggestions, tips if you have regarding this phone.
Thank you!
Anyone have anything to say?
NHS2008 said:
Hi I got this phone couple of days back. It came flashed with latest Android 4.0.3 (20120608-154131)
I have rooted it using zopoROOTby_Jaynes_android4.0.
It's working fine, but seems the battery life is ridiculous and the battery information is also not reliable, especially after restarting the device
(Sometimes it suddenly decreses a lot and vice-versa).
Also GPS, I tried it out in the open for like 15-20 mins it finds 4-6 sats but DOESN'T lock on.!
And then the market had some incompatible apps, I did the XML trick, didn't work...removed the 5 files again and then gave up, all of a sudden after a restart, market is fully accessible!! (Weird!)
I have backed-up my apps using Titanium free but I want to install CWM recovery. I do not know the exact procedure to follow for the same.
I just want to have the CWM recovery and not want to flash whole ROM again...How to do it???
Also please give me any important suggestions, tips if you have regarding this phone.
Thank you!
Click to expand...
Click to collapse
Is the phone going in deep sleep? (install cpu spy to check). This could be your battery problem. WiFi/3G/Bluetooth and some apps can keep the phone from going into deep sleep. You can try to edit build.prop to help it go into deep sleep.
The gps - theres some things you can edit in gps.conf and secgps.conf to get a faster fix (like changing time servers and how a-gps works).
kevinlekiller said:
Is the phone going in deep sleep? (install cpu spy to check). This could be your battery problem. WiFi/3G/Bluetooth and some apps can keep the phone from going into deep sleep. You can try to edit build.prop to help it go into deep sleep.
The gps - theres some things you can edit in gps.conf and secgps.conf to get a faster fix (like changing time servers and how a-gps works).
Click to expand...
Click to collapse
Thanks for your helpful reply! I installed CPU Spy and here's what I found!
Seems, it's keeping at 1001 Mhz all the time!! Am I right??
Are there any other ways around it than editing system files??
Thanks again!! About GPS I got it to work today, albeit not accurately...
NHS2008 said:
Thanks for your helpful reply! I installed CPU Spy and here's what I found!
Seems, it's keeping at 1001 Mhz all the time!! Am I right??
Are there any other ways around it than editing system files??
Thanks again!! About GPS I got it to work today, albeit not accurately...
Click to expand...
Click to collapse
Yep, looks like it is staying at 1ghz, you can install an app like setcpu to manage the cpu frequency. You will probably be limited by the kernel when it comes to governors (no undervolting either).
If you are not comfortable editing the gps.conf/secgps.conf there are apps for that I think. But it is quite easy with a file manager (root browser for example), the gps.conf tweak is to change the " NTP_SERVER= " to the closest server to where you reside from this site :
http://www.pool.ntp.org/en/
For example if it says NTP_SERVER=0.europe.pool.ntp.org , (edit: noticed you live in India, so you would do it like this):
NTP_SERVER=1.in.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=2.asia.pool.ntp.org
If you want to see more on these gps tweaks(I would just do the time server tweak since it works on all phones, I'm not sure if the secgps.conf tweak works with your phone), check out this thread (it's been updated at the bottom of the first post) : http://forum.xda-developers.com/showthread.php?t=1320626
I'm not sure about CWM, I think it has to be tailored to the phone itself because of the location of the recovery partition.
Edit2: I noticed in the picture that your phone has 1ghz , 500 mhz 250mhz and 166mhz. You can add a profile to setcpu to set the CPU to max 250mhz while the screen is off for example. This wouldn't fix your deep sleep issue, but would save battery. (Deep sleep is some parts of the CPU turned off, while some parts stay on)
Thanks again! I have set it to 250-1001 ondemand and apply on boot now. But 'deep sleep' is still unused as per CPU spy, Any clues as to how can it be enabled?
About GPS, I can do that. Just that I could live without it for now, but thanks for elaborating it! I will do it tomm. Morn, its 2:39 am.
NHS2008 said:
Thanks again! I have set it to 250-1001 ondemand and apply on boot now. But 'deep sleep' is still unused as per CPU spy, Any clues as to how can it be enabled?
About GPS, I can do that. Just that I could live without it for now, but thanks for elaborating it! I will do it tomm. Morn, its 2:39 am.
Click to expand...
Click to collapse
I posted second edit after you posted, will repost here in case you missed:
Edit2: I noticed in the picture that your phone has 1ghz , 500 mhz 250mhz and 166mhz. You can add a profile to setcpu to set the CPU to max 250mhz while the screen is off for example. This wouldn't fix your deep sleep issue, but would save battery. (Deep sleep is some parts of the CPU turned off, while some parts stay on)
Click to expand...
Click to collapse
The deep sleep issue is probably related to some apps keeping the phone on (could be kernel problem also, but I'm not an expert on that so can't say). You can check wake-locks with betterbatterystats. Also, rebooting the phone helps(rebooting after charging also helps I noticed). Edit: Some tips on wake-lock : http://forum.xda-developers.com/wiki/Wakelocks
kevinlekiller said:
I posted second edit after you posted, will repost here in case you missed:
The deep sleep issue is probably related to some apps keeping the phone on (could be kernel problem also, but I'm not an expert on that so can't say). You can check wake-locks with betterbatterystats. Also, rebooting the phone helps(rebooting after charging also helps I noticed). Edit: Some tips on wake-lock : http://forum.xda-developers.com/wiki/Wakelocks
Click to expand...
Click to collapse
Thanks for your reply. I think it is more of a Kernel problem only.
ust found out using Batterystats that As soon as I get a message or notification, It triggers LED light and a WAKE LOCK (Called 'Leds Wakelock' ) Which prevents phone from going into deep sleep, and it remains that way hogging battery! Only solution is to REBOOT and hope you don't get any notification!
BEFORE REBOOT
AFTER REBOOT
If your phone has a cyanogenmod rom (I haven't looked into the popularity of it), there is an option to turn off the LED notification in the cyanogenmod settings. Does Zopo release the source code for the kernel / rom?
I read in the other thread about the phone having issues when not in the performance governor, that is a shame, maybe the voltage is adjusted lower at lower frequencies causing the reboots.
kevinlekiller said:
If your phone has a cyanogenmod rom (I haven't looked into the popularity of it), there is an option to turn off the LED notification in the cyanogenmod settings. Does Zopo release the source code for the kernel / rom?
I read in the other thread about the phone having issues when not in the performance governor, that is a shame, maybe the voltage is adjusted lower at lower frequencies causing the reboots.
Click to expand...
Click to collapse
I don't know whether it is cyanogenmod (I don't even know what that is..) But my phone doesnt have ANY option regarding that. But
Here's a good thing, since I restarted to take screen shot I've had several notifications LED flashes, and the 'LEDS Wakelock' hasn't reared it's ugly-head!
ALSO I have again set the Governor to 'On demand' and now it seems doing better no Hang up for a good time played AB space. going good!
I think that LEDS Wake lock was root of all troubles. Will have to keep a lookout for it.
Thanks a lot for your guidance!
Have you come up with a solution that can kill that wakelock other than reboot? From my observation that leds wakelock only happen when the battery's going low (<15%) and it won't go away after that.
Dirty solution is to patch framework-res.apk and modify the level of battery low notification.
I am using a newer custom ROM 100500 v2 and no longer have any issues with wake locks!
Sent from my XT910 using Tapatalk 2
Hi, today I woke up and noticed that overnight (7 hours) my battery dropped from 99% to 47%. I looked in better battery stats and I noticed that my phone was running at 900CPU all the time. I really have no idea how can that be happening, until today everything was fine and I haven't installed any new app. I am running Omega 29 with Phenomenal normal kernel. Would full wipe and reinstalling ROM help?
Thanks
mystogans3 said:
Hi, today I woke up and noticed that overnight (7 hours) my battery dropped from 99% to 47%. I looked in better battery stats and I noticed that my phone was running at 900CPU all the time. I really have no idea how can that be happening, until today everything was fine and I haven't installed any new app. I am running Omega 29 with Phenomenal normal kernel. Would full wipe and reinstalling ROM help?
Thanks
Click to expand...
Click to collapse
Check your battery stats and see what it was doing, could be anything from Apps running in background (Sync, GPS...)
If there is an app there that drained it, you don't need to get rid of it, put your phone into Power Saving or download a 3rd Party app called Juice Defender. That will stop it. Also if you don't want to do that, you can just Force Close the App that used your battery at night and leave it at that.
Oddly tested mine overnight wifi and gps off 150 apps .
12 hours 2 % drain and that's the usual .
jje
Delete Facebook.. , Disable media server,
Two things to keep your CPU awake..
I checked all of that, but like I said, only thing I noticed was that phone was running at 900CPU all the time, and I don't know why.
mystogans3 said:
I checked all of that, but like I said, only thing I noticed was that phone was running at 900CPU all the time, and I don't know why.
Click to expand...
Click to collapse
Since it's Omega go into S Tweaks Scroll down the bottom to CPU Scaling and select one of the others on the Drop Down Menu, (pegasusq) try the others. Hopefully that will do the trick. Do not underclock the device under 800 as it will c*ck up the phone.
skrapi said:
Since it's Omega go into S Tweaks Scroll down the bottom to CPU Scaling and select one of the others on the Drop Down Menu, (pegasusq) try the others. Hopefully that will do the trick. Do not underclock the device under 800 as it will c*ck up the phone.
Click to expand...
Click to collapse
Isn't that for Siyah Kernel only?
I'm having similar issues of battery drain on Omega V29 and Siyah Kernel but its mainly when the screen is on, my current cpu scaling profile is set to 'lulzactive'. Could this be the cause of my drain?
skrapi said:
Since it's Omega go into S Tweaks Scroll down the bottom to CPU Scaling and select one of the others on the Drop Down Menu, (pegasusq) try the others. Hopefully that will do the trick. Do not underclock the device under 800 as it will c*ck up the phone.
Click to expand...
Click to collapse
I am not using Siyah kernel. Stweaks does not work with phenomenal.
YoungAceAtlanta: I don't have facebook, but like you said, my media server is going crazy. I am 100% it's the cause of drain, however I have no idea how to disable it.
Edit: Media Server is using 87% of battery...
mystogans3 said:
I am not using Siyah kernel. Stweaks does not work with phenomenal.
YoungAceAtlanta: I don't have facebook, but like you said, my media server is going crazy. I am 100% it's the couse of drain, however I have no idea how to disable it.
Edit: Media Server is using 87% of battery...
Click to expand...
Click to collapse
If in doubt Recovery Mode. Wipe data/cache then Calvin and fix permissions. Then flash Rom again. Check each app you download their permissions and comments
Check one of the multiple threads about battery drain
Well guys i installed SETCPU right after rooting, set the limit cpu frequency values according to my choice (UC) but to mu surprise it still peaks at 1.4ghz. I'd set the valut to 200min 1000max with pegasis governor but it doesn;t work. It never happened on any previous device i rooted. Already tried rebooting, nothing happens. So what can be the cause? I guess CF Auto Root just installed the root binaries bit not the busybox. Can it be the problem?
Does your kernel support OC?
Well bro i don't want to overclock and it's stock, so i guess it doesn't support overclocking. Besides, i want to underclock it(UC). But it doesn;t work even my profiles like battery less than, charging etc doesn't work either. Setcpu shows the limit defined values but cpu keeps running at 1.4 ghz
flash a custom kernel
Thanks for the suggestion but i just wanna keep it stock to avoid any problems whatsoever. It's just that setcpu always worked even on stock kernnels. Already tried on S2 and my ace, it worked great.