I just rooted my SGS3 international ver. i was wondering if anyone has experimented with the GHZ and found a solid sweetspot that gives great performance and equally great battery life.
thank you
I have been running at 1.5Ghz and at least -100ma undervolt for all frequencies using Siyah kernel, battery life is fantastic so far, perfectly stable and performance is a bit higher in benchmarks than stock. I am easily getting two days with light usage, so far today 30min music playback, 40-50min web browsing and 4 or 5 hours of standby has used about 17%.
Related
Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt
I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.
mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App
Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707
I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...
So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt
I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.
Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.
I'm looking for the fasted NS4G Rom/Kernel Combo...
I'm looking for something slim, but with Gapps. But will stay fast and be good on batter. (I know its a lot to ask). But it just feels like my phone is slowing to a crawl...I'm not looking to play any games on my phone (I have a N7 for that), just the basics, occasionally look things up on the web, text, call. I just want a fluid, fast experience.
I'm currently on the newest RasBeanJelly, willing to move or maybe just recommend me a Kernel, because I'm currently using stock.
Any help/tips/recommendations would be great!
Thanks.
CodeNameAndroid 3.6.6 with AIR Kernel is the fastest my phone has ever been. It is different for every handset and user though. Everyone uses their phone differently, and every handset isn't able to overclock, undervolt, or both at once, depending on how much better than the "standard" your specific chip happens to be.
I did overclock mine up to 1200mhz from the stock 1000mhz, but I was able to undervolt it to stock 1000mhz voltage (I believe it was 1250mv) at 1200mhz and remain stable with Ondemandx and Deadline. Was also able to knock -25 to -50mv's off of 1000 and 800mhz also and still stayed stable. I did get good battery life on that ROM too, but hard to say how much since the battery in mine is all but ruined (my kids play on it all the time so it's been charged like twice a day for a year and a half)
I know that overclocking/undervolting results vary from handset to handset depending on how well binned your chip is. In my experience, these things are almost always stable at 1200mhz with 1300mv with a ROM/Kernel combo that plays nice together. That is a 20% increase in speed with only a 3% - 4% increase in power. Well worth it IMO. I also loved Blackbean with Marmite and Crossbones with Matr1x. YMMV
Blackbean is my favorite looking, CNA was the best performing for me, and I've always liked Crossbones because it has always ran rock-solid on my NS4G with no reboots or lockups. Seems like I can always overclock higher and remain stable on Crossbones with Matr1x or AIR also (but it kills the battery so I stick to around 1200 because I dont even notice a difference)
Cm10 with marmite kernel
Slim 3.0 all the way. Its already got a great kernel!
Vs Nexus S4G using tapatalk2
Im running Viper XL and the reason i flashed it is because i heard it has above average battery life, but im getting maybe 10-13 hrs max. I've heard cases of 24 hr battery life, and I cant seem to achieve it. I am running Beast Mode Kernel and have the powersave governor. I am running Stock CPU frequency and have one core active. Am I missing something, because i got better battery life on paranoid android which kind of suprised me.
You really have to drill down on the tweaking and settings. Took me a bit to get what I wanted as well. I completely shut off Google Now, you can toggle off LTE and surprisingly, I raised my min cpu frequency to 594 and ondemand. Shut off HTC powersaver as well. Try a reboot after you tweak up all your settings. I think battery life was better on 2.4.1 but it's pretty well on 3.1 too.
Sent from my HTC One XL using Tapatalk 2
Viper Xl
Alphacall2 said:
Im running Viper XL and the reason i flashed it is because i heard it has above average battery life, but im getting maybe 10-13 hrs max. I've heard cases of 24 hr battery life, and I cant seem to achieve it. I am running Beast Mode Kernel and have the powersave governor. I am running Stock CPU frequency and have one core active. Am I missing something, because i got better battery life on paranoid android which kind of suprised me.
Click to expand...
Click to collapse
I'm assuming you're running ViperXL 3.1. In that case, I'm surprised you're seeing such poor battery life. But, usage and settings are everything. Things like Google Now and GPS are major battery hogs. Facebook, Google+ and other push applications can also hamper battery life. Check your background sync frequencies! How long is your screen running? At what brightness? etc.
That being said, what strikes me is your kernel. You should not be using Beat Mode Kernel (last I checked it's not even optimized for the latest android version). I recommend you use the stock ViperXL kernel or Elemental v1.5.
I've ran ViperXL 3.1 yesterday with elemental v1.5 for more than 24 hours, 3 hours screen time while syncing 3 e-mail accounts. YMMV but with proper set up it's definitely possible.
Give us more information about your usage!
Alright, thanks for the information on the kernel, its a shame because i heard good about it. But as my screen time i run low brightness and im pretty heavy on texting, I used LTE for about 40 mins total today. can you tell me the way you disabled google now? I've been tweaking the settings a bit and i guess i just havent found my sweet spot.
Edit: And im running 2.4.1 actually sorry should of put that in first post.
Complaining about 13 hours of battery life. O__o
Sent from my Nexus 7 using Tapatalk HD
Not a complaint! I'm Just saying i've heard of better
Battery life is a very elusive thing. There are simply too many variables. For every ROM, radio, etc. where people will say they have much better battery life, you will almost certainly find others that have worse. Its just a fact of life with modding phones.
I've gotten about a day and a half on a single charge ever since the phone was released, and over 48 hours with later firmware versions (stock and custom ROMs) as of 2.2X and newer. Some folks can't even get through a half a day.
Alphacall2 said:
Not a complaint! I'm Just saying i've heard of better
Click to expand...
Click to collapse
CleanRom 5.1 might get a little better, but I've had about the same battery life using Viper XL 3.1. A lot of the other things to look at are certain apps that seem to cause a lot of drain (depending on options). The most frequently mentioned are: Google Now, Facebook, and Maps. Other than that, lower brightness and shutting off LTE are the next biggest contenders.
Which radio are you gents getting good performance with decent battery life? I'm kicking around T989UVMC6 and it seems to be more power hungry but perhaps its just my area. I don't think this is very good battery life as I've barley used my phone today. I'm considering buying the battery for the nexus as it has a little more capacity and I've read it fits but I'm waiting on confirmation.
Anyways..I'm testing slimbean 3.1.0 build 3 with the T989UVMC6. I'm thinking of trying the LV kernel, what governor and I/O scheduler are providing good results for you guys?
And this battery: EB-L1D7IVZ
neal74 said:
Which radio are you gents getting good performance with decent battery life? I'm kicking around T989UVMC6 and it seems to be more power hungry but perhaps its just my area. I don't think this is very good battery life as I've barley used my phone today. I'm considering buying this battery for the nexus as it has a little more capacity and I've read it fits but I'm waiting on confirmation.
http://www.batteries4less.com/samsu...m_eb-l1d7ivz&gclid=CKKw3sC_-LgCFazm7AodGhYAyA
Anyways..I'm testing slimbean 3.1.0 build 3 with the T989UVMC6. I'm thinking of trying the LV kernel, what governor and I/O scheduler are providing good results for you guys?
Click to expand...
Click to collapse
As of now. I am using CM10 latest nightly. Using Bluelightning X2. SmartassV2 and SIO. Overclocked to 1728. Minimum is 192. Getting decent 16 hours of battery life.
xWolf13 said:
As of now. I am using CM10 latest nightly. Using Bluelightning X2. SmartassV2 and SIO. Overclocked to 1728. Minimum is 192. Getting decent 16 hours of battery life.
Click to expand...
Click to collapse
Is this the one your referring to? http://forum.xda-developers.com/showthread.php?t=2025488&highlight=bluelightning+x2
You running the standard JB one and not the GPU OC one? You seem to be playing with all the roms and kernels to..how would you compare it to LV kernel. Also, what radio are you using? Does it seem like my cell standby time is high in that screen shot? I have only made two phone calls and had the screen on a few times for a few minutes today. The phone was at 100% at the start of the morning and has been very idle so i'm surprised to see it so drained.
neal74 said:
Is this the one your referring to? http://forum.xda-developers.com/showthread.php?t=2025488&highlight=bluelightning+x2
You running the standard JB one and not the GPU OC one? You seem to be playing with all the roms and kernels to..how would you compare it to LV kernel. Also, what radio are you using? Does it seem like my cell standby time is high in that screen shot? I have only made two phone calls and had the screen on a few times for a few minutes today. The phone was at 100% at the start of the morning and has been very idle so i'm surprised to see it so drained.
Click to expand...
Click to collapse
On page 5 on that thread is the link for X2. Flash X2 then the GPU OC Zip.. Using UVMC Radio. Haven't flashed LZ in a while so i don't know.
I'm using BlueLightning with Conservative and SIO, minimum frequency is 348 max is 1188. It's not the best combinauon if you prefer performance, I get about 18 or 19 hours of battery life I'm also using the same radio as you BTW .
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
How much do you overclock and how stable is your tablet? I have mine clocked at 1400 constantly and so far only had a couple of hang-ups. I know from my experience that it's pretty unstable at 1700, but what about 1500-1600?
Beyond 1200 doesn't really gain you much and may even degrade performance, along with instability. Might give you better benchmarks, but real world, 1200 is probably the sweet spot for stability with modest performance increase.
1400MHz for years, tried 1500MHz but crashed fairly regularly
I've been sitting at 1400mhz for years as well. Noticable improvement in even the smoothness of the GUI.
Sent from my C6606 on 4.4.2 KitKat
Been using it at 1200 MHz -- while 1400 was ok, was using too much juice. Also, I don't see that much difference betwen both clocks, although I'm not a heavy gamer anyway.