hi
Ok, so it looks like none of the overclocking apps I used works 100% on stock ROM
have to say that never had any issues with custom ROMs on my previous tablet (xoom) but on this SM-T310 Stock, just can't get it right.
Apps I used :
- SetCpu - totally not-compatible
- ROM toolbox - letting me sleep more, when used Profiles set to low CPU freq+powersave scheduler never turns on / with on-demand scheduler the CPU speed most of the time clocks 500 which eats a lot of battery and again Tab turned off in the morning
strange thing with ROM toolbox is that with or without profiles on, no matter how low the min slider freq is system always sets ( after a while ) min slider to 500 which again eats battery a lot
So I tried some other apps (no-frills / AnTuTu ) but can't tell how good they are with profiles available and because not all apps are free, maybe you can advise which one you use to overclock stock ROM ???
thanks
NONE of these tools are going to work in a 100% stock ROM because the kernel does not allow the user to mess with it's frequencies. There may be some that trick the device to do some really weird stuff but these methods are super buggy and they tend to work for a limited time until the governor/scheduler zaps what they try to do. Your only route is to flash a custom kernel the least.
VIRGIN KLM said:
NONE of these tools are going to work in a 100% stock ROM because the kernel does not allow the user to mess with it's frequencies. There may be some that trick the device to do some really weird stuff but these methods are super buggy and they tend to work for a limited time until the governor/scheduler zaps what they try to do. Your only route is to flash a custom kernel the least.
Click to expand...
Click to collapse
hey, yeah samsung doesn't like when users adjust devices, but they did good job with multi-windows and this is the only think still keeping me with stock kernel.
http://forum.xda-developers.com/showthread.php?t=2511683
Related
This guide on how to use the OC/UV beater app that is used to control my overclock daemon that is included in some roms, and is flashable here for advanced users : http://forum.xda-developers.com/showpost.php?p=21253167&postcount=38 . If you cant find the app, unfortunately its not available in market but installable here: http://forum.xda-developers.com/showthread.php?t=1207546
First of all you need to make sure that any apps like setCpu or other overclocking apps are uninstalled not just disabled. Once this is done you need to reboot for it to take effect.
In the app you will normally have 3 tabs, these can be used to create different profiles. You can set a profile name if you like or just leave them.
You then have 6 dropdown menus for the overclock settings, 3 for each phone state. Your phone has 2 states, awake and asleep, asleep is when the phone is screen off and nothing too cpu consuming is running in the background and awake is for any other time. When you open the app for the first time the will say !set this is normal.
For each state you have a governor, min and max setting. When choosing a governor dont choose smartass as this does not work properly with the daemon (see below for why). Personally i use the normal on demand for awake and conservative for a asleep. Other governors can be used though depending on your preference.
Next you set your frequencies. Normally for minimum its safe to choose the lowest value unless you are having issues. As for the awake maximum choose what ever is the highest your phone runs stable at, or if you dont know, try out the one above your current speed. For asleep maximum either choose the minimum again or the one above (message to all kernel devs- try and enable a speed around 120mhz for maximum battery life).
Now we want to test these speeds out to see if they work, hit save, then temp activate. Now use your phone for a while, preferably trying a few intensive apps. When you are sure its stable use perm activate to set it on boot.
This should be enough for most people, but the app has a couple more features like profile switching based on battery state and ill leave you to work them out if you want as they are fairly self explanatory.
About the smartass governor: this governor was designed to switch maximum speeds based on phone state like screen on and off however the daemon does this for you if you set it correctly and will conflict with each other.
For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM
barzhdu said:
For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM
Click to expand...
Click to collapse
Looks like its rom specific the app is rock solid normally. I think that the daemon config has gotten messed up in the mix of roms so ill try and see what is breaking it.
I cant seem to get the 460800mhz freq stable no matter what voltage i set. Is there a way to delete that crequency from ever being used, and how?
Works like a charm altho it seems the cm7 kernel does not support UV only OC or might be just me not understanding the UI. Antway i ll play around with it alot cuz so far it seems to ne runing alot better an utilising all freq properly.
Sent from my Wildfire S using xda app-developers app
I am by no means an expert and always thought SetCPU was useful - I don't use it to overclock - just use it primarily to limit the processor when the screen is off. However, with ICS and Jelly Bean and the improvements related to it, is there still a need for SetCPU? Again, not just to overclock, etc, but to limit the processor when the screen is off to attempt to save battery. Thoughts?
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
athakur999 said:
I personally have felt no need for SetCPU once I upgraded from my first Android device - a MyTouch3G.
The schedulers in most custom kernels nowadays already throttle back the CPU speeds when the screen is off. As for overclocking, it IMO doesn't make any noticeable difference anymore so I don't even bother.
Click to expand...
Click to collapse
But, what if you don't use the scheduler in the custom rom, is SetCPU still redundant?
I use it to set the voltages. If the hotplugx worked well with it I'd use it for profiles but unfortunately it'll crash.
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
herqulees said:
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
"Light version": do it yourself with a root-enabled explorer. Google and you'll know what system apps can be deleted.
OC&UV kernel: Nitest maybe.
Swap: IDK
Free up RAM and speed up: I personally use Autostarts and Advanced Task Killer (Pro), but Greenify seems easier to use. You get ~80MB free RAM after a clean install, but can get 190~220MB after heavily using these. I don't use gapps so YMMV.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
I've already deleted every system app I'm comfortable removing using Root Uninstaller. After having everything I have to have installed on the phone, with as many apps set to not run in the background that I can and Greenify helping too, I tend to have 10-70MB of RAM free, it tends to be 15-35MB free though. I don't use task killers since all they do is play cat and mouse and waste battery, and tried a few auto start managers but can't really get into using it with how complicated they are. Right now the main thing I want to figure out is getting a swap partition up and running since that sounds the most promising with how little RAM this phone has.
Did a backup and switched to the nitest-0721 kernel and so far it's doing good. Disappointed the OC only goes up to 1.2GHz but it's better than nothing (don't understand kernels that limit how much you can OC when it's up to you to find how much your phone can OC), hopefully I can find a way to get it to go higher, and the "voodoo color" is weird but I can install a different version of the kernel to remove that if my eyes don't adjust first. Anyways... my free RAM now stays between 100-200MB, usually about 160MB, with 18% zRAM, purging of assets, and samepage merging enabled which is amazing. Apps are opening faster and don't stutter anywhere near as much as before, so I'm happy but will see how things go tonight when I go to work and am playing with it on and off, along with need to find a way to really overclock it.
herqulees said:
EDIT: *lighter, forgot to check spelling. Lol
So my Evo 3D has finally called it quits and I have one month left till I leave Sprint so my friend gave me this phone that he doesn't use any more. For such an old phone I really can't complain about it, compared to my Evo 3D which runs CM 10.1 too it never crashes, always has GPS, 3G, 4G working fine and the battery lasts me all day. So I'm in love. But my one and only issue is it is extremely slow. And no I will not leave CM 10.1 as I use Google Now very often but if their are huge differences/opportunities for huge differences I'll go down as low as CM 10 or a different 4.0+ ROM.
So I was wondering is there a lite version of CM 10.1, recommended kernels that support both overclocking and undervolting, can someone explain how to make a swap partition on the SD card, and so on, just any ways to free up RAM, speed up the CPU/GPU, and lighten the load of the OS.
Click to expand...
Click to collapse
Try going with one of didhiy's nitest kernels and maybe a different AOSP ROM, like AOKP, PAC, etc. Or try out SuperNexus even. That's an extremely lightweight ROM with no customization options (Its straight up stock Android, just like a brand new Nexus phone), but its fast and quite stable from what I remember.
Sent from my LG-LS970 using xda app-developers app
Or find one of didhiy's nutest kernels, those have live oc, more free ram, and i believe it goes to 1.4 GHz. I'm not sure though. But it is less stable than nitest
Sent from my SPH-D700 using Tapatalk 2
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
herqulees said:
Well I've run this kernel for a week or so now with the smartassv2 governor and min/max at 100/1200MHz. Zero reboots unless I'm playing Minecraft the entire phone locks up other than the button lights, no matter what I do it crashes sooner or later but oh well I'm bored of that game just wanted to see if it'd play on this phone. ANYWAYS I've heard of it being done before but can't find any info on how to do it, how can I overclock past what the kernel allows (1.2GHz), I've seen reports of this phone handling 1.5GHz and want to see if I can reach 1.4.
Click to expand...
Click to collapse
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
AndyYan said:
The frequency is still limited by the kernel...
1.5GHz is history (too unstable and hot so that devs stopped including it), and only Gingerbread/ICS custom ROMs can get that frequency via flashing corresponding Sanders/Shadow/Samurai kernels and overvolting as well, which is definitely not good.
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Click to expand...
Click to collapse
I just seriously hate kernels that limit how high you can overclock instead of making OC options to unreachable levels letting you find your phones limits. People make kernels, roms, hacks, etc so we can get around limitations that the hardware vendors put up. So if we've managed to circumvent the manufacturers blocks why are the same people that got around them making their own blocks, they already put up silly warnings about anything you install/do could break your phone but if you're going to give that warning it needs to be true. Anyways ending my rant lol...
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
herqulees said:
I know their has to be a way to edit a kernel or file to add more options since the kernel creators can't do the job themselves, it's just finding out what and where these files are. Can anyone inform me on this and give me details on how this whole system of controlling clock speed works so it can be modded?
Click to expand...
Click to collapse
Uh, AFAIK, isn't these frequency decided only when the kernel is COMPILED (from source code)? I don't exactly know...
Sent from Google Nexus 4 @ AOSPA 3+ 3.99
Current settings:
Kernel: 3.4.94-QuantumKernel-6/17
Rom: Carbon-kk-nightly-20140617-0002
Freqs range: 384MHz - 1512MHz
Governor: interactiveX
and before this rom and kernel install I was running Liquid smooth and it's kernel, Deathly. I've done several clean flashes of both Roms and just recently did a dirty flash of the QuantumKernel again.
So it's an odd situation, because everything runs great at first. Navigating through settings and everyday apps seem great, the cpu correctly runs at the rate it should. But as soon as I launch Clash of Clans, the phone just drops to 384MHz and everything from then on just crawls. Sometimes it will run fine for 30 seconds or so but then just goes back to 384 on both cores constantly. I've tried installing and using kernel tweaker and overriding some settings. superuser notifications make it seem like there are actual changes being made but then it eventually ignores all tweaks I've made and goes back to running at 384. Had this problem with Liquid smooth last week and posted, no replies. So I found Carbon and a recommended kernel in the designated thread and eventually fell into the same situation. I know there are certain triggers where the GPU overrides the cpu clock speeds, maybe it's something with that since it seems to be triggered from Clash of Clans which is a huge cpu hog. I don't know. Any ideas or suggestions?
Thanks in advance!
Gil Prefect said:
Current settings:
Kernel: 3.4.94-QuantumKernel-6/17
Rom: Carbon-kk-nightly-20140617-0002
Freqs range: 384MHz - 1512MHz
Governor: interactiveX
and before this rom and kernel install I was running Liquid smooth and it's kernel, Deathly. I've done several clean flashes of both Roms and just recently did a dirty flash of the QuantumKernel again.
So it's an odd situation, because everything runs great at first. Navigating through settings and everyday apps seem great, the cpu correctly runs at the rate it should. But as soon as I launch Clash of Clans, the phone just drops to 384MHz and everything from then on just crawls. Sometimes it will run fine for 30 seconds or so but then just goes back to 384 on both cores constantly. I've tried installing and using kernel tweaker and overriding some settings. superuser notifications make it seem like there are actual changes being made but then it eventually ignores all tweaks I've made and goes back to running at 384. Had this problem with Liquid smooth last week and posted, no replies. So I found Carbon and a recommended kernel in the designated thread and eventually fell into the same situation. I know there are certain triggers where the GPU overrides the cpu clock speeds, maybe it's something with that since it seems to be triggered from Clash of Clans which is a huge cpu hog. I don't know. Any ideas or suggestions?
Thanks in advance!
Click to expand...
Click to collapse
I'm not so sure why that happens but I would suggest you try KT747. I've been using his kernel for quite some time now and have no issue with CoC.
BWolf56 said:
I'm not so sure why that happens but I would suggest you try KT747. I've been using his kernel for quite some time now and have no issue with CoC.
Click to expand...
Click to collapse
Thanks for responding! Just flashed this kernel and so far so good. Though I'm confident it'll stay that way. This kernel is amazing! So many options to consider tweaking but then not mess with in fear I'll break my phone. lol But seriously thanks, this is working great!
Gil Prefect said:
Thanks for responding! Just flashed this kernel and so far so good. Though I'm confident it'll stay that way. This kernel is amazing! So many options to consider tweaking but then not mess with in fear I'll break my phone. lol But seriously thanks, this is working great!
Click to expand...
Click to collapse
My pleasure, glad it worked out!
If you wanna make some tweaking, look at the scripts/profiles. There is a nice directory full of premade by users (as well as one from KT himself)!
Here is updated Thermanager, which could be flashed in recovery. I have made some changes after I played Asphalt game for about one hour. With this update, on performance governor the temperature never went higher than 58. And we are talking 1 hour straight. I doubt you can have that on stock. What was interesting that performance governor produced less heat than interactive, which supports my claim that when cpu jumps frequencies, it creates additional overhead.
Now, regarding myths and fiction about stock rom not overheating. There are some dudes on this forum who complain that their Z1 overheats to 70+ on custom roms when they play their beloved games; on stock, they say, there is no overheating.
Here is a short answer. You, guys, don't know what you are talking about.
Custom roms (and custom kernels) give you tools that are not available in stock. You just have to learn how to read/use them. Here is one example: some roms allow you to have internal cpu temperature on screen. Now that you have it, you watch. When it hits 70, you panic, but if you touch the back door, it will be barely warm. So, when you are on stock and without temperature reading, you think your phone is not overheating, while it can still have 65-70.
I used a modified version of M5 kernel compiled with GCC 5.2.1 Ubertc; CPU at 2457; performance governor, inteliplug balance with touch boost disabled; GPU overclocked to 600 with msm-adreno-tz idle wait 30 and workload 3; swapiness 10; enthropy 1024 read/write. That was on DU rom, but I bet the result would be the same on Jaguar and some other custom roms.
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
SuperLamic said:
I don't think that my phone won't reach 60 C on stock, but I like watching YouTube, so I can see how fast it warms. (I have xposed module that shows me cpu temp even on stock). And as much as I can say my phone warms faster on custom roms than on stock. No matter what governor I use.
Also all animations (like status bar showing) are kind of laggy on custom roms. I don't know it it got better in past 2 months, but last time I used custom rom my phone reached 50C even only with chrome.
Interesting thing is that this all (including animations) is not present on 3.10 kernel, but there are no usable roms at the moment with 3.10 kernel, so I have to use stock.
Click to expand...
Click to collapse
So, what's the temperature your xposed module shows on stock under stress?
optimumpro said:
So, what's the temperature your xposed module shows on stock under stress?
Click to expand...
Click to collapse
Usually after 20-30 minutes of YouTube it's around 53-54°C
SuperLamic said:
Usually after 20-30 minutes of YouTube it's around 53-54°C
Click to expand...
Click to collapse
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
ScatteredHell said:
lol, that dude is Me, and I will try this, in the stock rom I can see an process running as overheat manager or something, I think it might have to do something with it. I'm sure that my device got heated very much, I didn't meant to offense but you seems to got it wrong. btw I will try this. I use Jaguar atm.
Thanks
Click to expand...
Click to collapse
Overheat manager: whatever it is, all it does is throttling and thermanager does the same on custom roms. So, the trick is to throttle enough without you noticing any lags...
optimumpro said:
Which browser or is it a youtube app? I have similar temps on Firefox and about 44-48 when using Chromium (not chrome).
Click to expand...
Click to collapse
It's a YouTube app. Really? It's weird, maybe I'll try, but I can see the difference on battery time when I come home from school - on stock I have ~70% and on custom roms I have ~50. Anyway I'll try and report after few days.
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
OK. Nice to hear that about battery life and overheating. With regard to lagging: it is not cpu, but rather animations. Either disable them completely in developer options or in DU you can go to tweaks and pick and choose whatever animation you want. I just disable all animations and have absolutely no lag.
SuperLamic said:
Okay, I can say that custom roms are now ok for me when it come to battery life. I compared usual usage of mine on stock and custom roms and now it really gives me same battery life. The only change I made this time is that I used DU instead of Jaguar and this thermalmanager settings.
Though there are still two things that bother me on custom roms: laggy UI - I don't know what causes that, I tried changing lot of cpu/gpu thing to sort it out, but nothing helped. And the other one is headset connecting - I have to press and hold (for a little while) all the buttons on headset to get it recognized.
I'm returning back to stock, but I can say that now is overheating on custom roms gone.
Thank you, @optimumpro
Click to expand...
Click to collapse
Oddly enough, I find custom ROMs hae smoother animations than stock, in my phone. But I don't have good battery life when compared to stock..