Hello XDA community,
I have been on a break from the whole Android development thing for quite a while , I came back to XDA and some mediatek chipset tweaking a week ago or so , and I have noticed several people shouting about overclocking their CPUs and GPUs to gain performance Blah Blah Blah.... If you Don't want all the technical stuff , here's the short answer:
Overclocking has a 50-50 chance to give you better or worse performance
Now for those who still want how to know how overclocking works and affects the performance , Get a cup of coffee or something.So I will start with the most basic question ,
What is Overclocking?
Overclocking is the act of increasing the frequency at which a CPU operates , so it runs faster and hopefully gives us better performance.
For example , Let's take the Mediatek's MT6589 chipset , It has max frequency seen of 1209 MHz (@stock setting).
This means that the CPU can transmit 1200 0s and 1s in a second, to simplify things , lets use an imaginary runner here , the runner has to run on a 100 foot track , when he reaches either end , the CPU registers a 0 or a 1 , the only 2 numbers which our CPU industry works upon , now , at stock un-overclocked frequencies , the runner is easily able to run , 1200 times , in mt6589's case , this is the speed at which your CPU can think , or process , when we increase the frequency , we are telling the runner to increase the times it has to run to and fro from a 0 to a 1 , or vice versa , which in turn increases our hardware's processing power , but , this does not mean , you can go on increasing the frequency as long the device is under operatable temperatures , there are certain factors which matter while increasing the frequency , which leads us to the next topic ,
Voltages , and Overvolting
Voltage is the ingredient that grants greater stable MHz potential to our transistor based computer hardware. Our RAM, processors, video cards, and motherboard chipsets all see gains from overvoltage.
But what does voltage actually do? How much is really too much? What are some dangers to Overvolting? Are there numbers set in stone, or is each piece of hardware different? How can we accurately and safely determine safe overvoltage limits for our expensive hardware, without killing it?If you aren't interested in all the 'how it works' stuff ,feel free to skip this part.
So , to start , let's clear this doubt , overvolting DOES NOT provide extra current , or more juice to accomplish higher overclocks , it just increases the strength of the signal inside the CPU/GPU.
All of todays computers use two binary digits , as told earlier , 0 and 1 , these 0s and 1s occur , or get registered and processed through voltages , voltage high , for a 1 , and voltage low , for a 0 , 0v typically represents a voltage low , or VSS ,Voltage high , or VCORE , is variable for each processor , there aren't any details I could find about voltages of mobile processors , but most of the 28 nm based CPUs have anywhere around 1.2v to 1.5v , but what we need to know is that when our CPU sees a voltage NEAR to the VCORE , it registers it as a 1 , yes , a voltage NEAR to the VCORE , exact VCORE voltages are rarely seen , the part which determines how much near the voltage needs to be is the tolerance , lets say that a processor has a VCORE voltage of 1.4v , with a tolerance of 5% , so , if the voltage reaches 1.35v , the signal will be regarded as a 1 , because the tolerance allows for a 5% loss of voltage , the min. voltage to be seen as a 1 would be 1.33v. BUT , as soon as the voltage exceeds the tolerance threshold , our CPU starts to mess things up , For instance , if the voltage is not able to reach a minimum of 1.33v ,Our CPU will register it as a 0 , the signal strength , which we talked about earlier is not powerful/good enough to reach the VCORE , this is what is known as an unstable CPU. This is the part where you need to play around with voltages. But , wait , why do we need to do that ? , the answer is , if you are at stock speeds , you don't ,the SoC manufacturers have enough brains to set the right voltage for the frequency , and you don't need to do it unless you are seeing the symptoms of an unstable CPU , which includes FCs , failed benchmarks , anything abnormal. So to make things even easier , Let's go back to the runner example again :
If we tell the runner to complete 1400 rounds , which is our frequency , instead of 1200 , on a 100 foot track , we keep increasing the frequency , until we reach a point where it is impossible for the runner to complete the 95 foot-mark , which is necessary for our CPU to register a 1 , and is called back when it hits the 90-foot already , that is when our CPU registers a 1 as a 0 , a VCORE as a VSS , and that is all that matters.when we increase frequency , we shorten the time given to the runner to reach the 95 foot-mark , and depending on the strength of the signal , or speed of the runner , it might or might not be able to complete it .
This problem is solved by overvolting , basically , overvolting means increasing the strength of the signal , or the speed of the runner ,let's take two scenarios here
In this example, the measurement ‘feet’ represents voltage signal strength, and the measurement ‘time’ represents the transition period between VSS and VCORE. Runner #1 can run 100 feet in 20 seconds (Stock VCORE), Runner #2 can run 110 feet in 20 seconds (VCORE overvolted by 10%). Runner #1 can run 5 feet per second. Runner #2 can run 5.5 feet per second. Our overvolted signal switches slightly faster than our stock signal, in the same time period, just as runner #2 can run further in the same time period. Please keep in mind that this is a simple example for explanation, and that signal switching speed is not so linear as "10% overvolt=10% signal switching speed increase".
At a stock frequency, we have 20 seconds to get within transistor tolerance, say it’s 5%, or 95 feet. Both runners make it. Now we overclock our frequency, and shorten the amount of time in which the runners have to get within our transistor tolerance of 95 feet. We increase the frequency, and shorten the transition time to 18 seconds. Runner #2, running at 5.5 feet per second, makes it to the 99 foot mark in 18 seconds, he is within tolerance, and his run is correctly counted as a 1. Runner #1 isn’t fast enough. He makes it to the 90 foot mark in 18 seconds, and is not within the tolerance. Runner #1’s run is incorrectly counted as a 0, and we have instability. In this manner, increasing signal switching speed to directly increase signal strength, overvolting allow us to increase our frequency (overclocking).
Silicon lottery
I wouldn't go stressing too much on this topic , basically , every CPU , even of the same model , manufactured at the same factory , with the same machine can vary greatly , The die inside CPU are made up of silicon , the silicon is extracted from inside the earth in big blocks , the part of silicon which is at the center will give you more overclocking potential and generate less heat , unfortunately , it depends on your luck which chip you get and what is it's potential , for example , I had a AMD FX8320 Desktop CPU , to my surprise , is overclocked to +1100 MHz with appropriate cooling , seeing the performance , I bought another one (exact same model)for one of my other systems , and sadly it overclocked max to +430 MHz , in short , My first chip had won the silicon lottery , while this one was not so good.
In the conclusion , it depends on you if you are willing to take the risk , System boards on Mobile devices have power phases which pretty much only supply the voltage the CPU will need @ max on stock clocks , and without overvoltage , you are pretty much restricted to anywhere from 10-80 MHz , even if magically you are getting stable performance at something around +120 MHz , you will run into issues like heating , potential bottlenecks , battery over-heating , if you consider overvolting , AFAIK there aren't much options for mobile CPUs.the System boards don't have .. ummmm.. good power phases , this is to reduce the battery usage because the CPU won't use more than what is specified by mediatek , qualcomm or whatever.Overvolting also has the effect of increasing the rate of electromigration within our hardware , you can google it to find out more , If you'd like to overclock , Find a Kernel that supports OCing for your device , flash it and then download something like SetCPU , start in increments of 10 MHz , run benchmarks , look for abnormalities and FCs , as soon as you notice one , take one step down , that is the best you are going to get.
NOTEon't just overclock your CPU/GPU to something someone might have accomplished , each chip is different , has a different overclocking headroom and heat generation.
I WILL NOT BE RESPONSIBLE FOR ANY KIND OF DAMAGE TO YOUR DEVICE.
you didn't show how to overclock and modify a kernel, practice is more important than the warnings people often say. It's funny how many people just talk about overclocking and danger, then fear and prevention! But there is almost no presentation on how to guide overclocking!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
I've tried overclocking the cpu on my mini using pocket hackmaster. The fastest setting I've been able to use which was stable was:
CPU: 468(T), Bus: 117, Mem: 59, LCD: 59 (Mhz)
Has anyone else tried overclocking their magicians? What's the fastest speed you've been able to use?
On the other side of the coin, has anyone tried underclocking it? If so, any improvements to battery life with a slower cpu speed?
I think battery life would be improved on any pda when lowering cpu cycles. Make sure you have insurance on your phone too, I managed to kill one by overclocking.
Mine Mini is rock stable at 1073Mhz, 143, 36,72.
liusam said:
Mine Mini is rock stable at 1073Mhz, 143, 36,72.
Click to expand...
Click to collapse
Are you sure? Have U check w/ any benchmark program? 2 o/c program I know (Xcpu scaler, PHM) will report fake clock value at some point.
rocket said:
I've tried overclocking the cpu on my mini using pocket hackmaster. The fastest setting I've been able to use which was stable was:
CPU: 468(T), Bus: 117, Mem: 59, LCD: 59 (Mhz)
Has anyone else tried overclocking their magicians? What's the fastest speed you've been able to use?
On the other side of the coin, has anyone tried underclocking it? If so, any improvements to battery life with a slower cpu speed?
Click to expand...
Click to collapse
520MHz (
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
)
--> http://forum.xda-developers.com/viewtopic.php?t=24290
The Benchmark result fpor GXmark is 1352 when performed at 1073Mhz. :roll:
liusam said:
The Benchmark result fpor GXmark is 1352 when performed at 1073Mhz. :roll:
Click to expand...
Click to collapse
GXmark?
I personally found PHM to be a better overclocking program than XCPUScalar.
I added manually 618MHz (124,62,62,T) which gives an SI benchmark of 329, faster than all those over 900Mhz clock rates I got by PHM's automatic settings. Some of them might be fake but some of them just gives the same SI benchmark for the same bus speed no matter what the processor speed is.
I set my MDA Compact to 520Mhz, bus:130, mem:65, LSD: 65 with Pocket Hack Master 2005 v3.10.007! It runs stable and I think thet is pretty enough. :roll: 8) The battery life is shorter but still acceptable!
liusam said:
Mine Mini is rock stable at 1073Mhz, 143, 36,72.
Click to expand...
Click to collapse
!!!! :roll: :shock: liusam! Can you tell us what program you used or how did you succeed this? Because this settings are very strange!!! It's very "interesting" for me what this multiplayer is? :lol: I think a multiplayer like this: 7,5034965034965034965034965034965 is a quiet impossible! In my opinion the max. multiplayer is FSBx4!
I set my o2 mini to CPU: 620(T), Bus: 124, Mem: 61, LCD: 61 (Mhz) , It was running pretty good but sometime , somehow it slow down for a few sec . But anyway i think the good Speed is CPU: 512(T), Bus: 130, Mem: 65, LCD: 65 (Mhz) with this setting i can see it not fast as the 620 but more stable . Anyway i just get back to the normal speed because i did too many test and it freezing my o2 now , IF i see anything interesting i will tell you guy
HI
where can i get the software to overclock my Jam and also the benchmarking software ??
regards
reo
Are you guys gettings speeds higher than normal with or without the power lead attached? XCPUScalar says you only get 520mhz with power lead in (which it did, although it hard reset when I disconnected the power cable )
I wouldn't mind trying other overclocking software if they're more successful, 520mhz is lovely to use, so smooth.
What stable speed can you guys get without the power lead in, and with what settings?
V
S100 Stabel at CPU: 702, Bus: 117, Mem: 59, LCD: 59 (Mhz)
I run whit 6 scale config. from 208Mhz to 702Mhz
In Pocket Hack Master try "fast bus=on" and your bus speed increase without problems. For example, now I have 208 mhz bus:
CPU=520 BUS=208 RAM=52 LCD=104
I use following settings:
L=16 N=5 A=0 LCD_26=0 Turbo=on Halfturbo=off Fast Bus=on
if N=6 then CPU=624 - no problem for my S110
@truedim
It doesn't work for me with N=6.
But it works with
L=18 -> 585 MHZ, SI=367 [234:59:59:T].
Any higher speed resets my device. I believe it depends on components tolerance. Btw, your 520Mhz settings raised my SI from 313 (std 520) to 322.
Silver
how to set fast bus or choose L=18 -> 585 MHZ ? i can set only 1 stable frequency which is 520/133 can u tell me how to set higher one ?
ok i solved the problem : ) i just need to add manual speed :F
520:260:65:65 gives me a SI of 373. It's stable as well.
The Benchmark result fpor GXmark is 1352 when performed at 1073Mhz.
Click to expand...
Click to collapse
Ur Jam is running at 1073mhz? U must b joking dude. It will fried up ur proccesor b4 u even reaches 1000mhz
I am running 1073 too,and you should also check it
I suggest anyone who claimed they get a 700mzh+ clock magician do a testing w/ TCMP Player. Take a look at what clock speed it detected and a "REAL" benchmark testing w/ Video/auido.
I just got my Thunderbolt yesterday, and so far, I love it. But I've been seeing the battery drain far too fast. According to the stats, it's been awake for a little over 2 hours, not doing anything significant, and the battery is at 60%.
I think this might have something to do with the CPU usage.
If you look at this top screen on the device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The CPU is mostly idle, but the load is >6. I'm not sure what would case this, but I suspect it's related to the power drain.
Anyone have any ideas?
quick q. do you use a lockscreen with pattern lock or PIN or something?
your best bet would be to use system panel, the paid version unfortunately, to analyze a period of a few hours and it will show you a break down of each and every process that hits the CPU, and how much it used, etc all in a very nice graphical view. its similar to the top command, but much more helpful.
ddarvish said:
quick q. do you use a lockscreen with pattern lock or PIN or something?
Click to expand...
Click to collapse
I do (enforced by company policy). Do you think that's related?
Ahhh, I've seen stuff like this on Linux servers before.
In one case, all the system processes were idle, but the load spiked to 25.00 during intensive disk writes. As it turns out, all of this processing was packed invisibly into the kernel; I was using software RAID at the time, and the RAID5 subsystem has to calculate parity bits for written data. So that's what was hogging CPU -- that, and the fact that my stripe width was 1 MB, probably way too big.
In another case, there was a kernel bug with the development kernel I was using (I think it was an -rc of 2.6.32) where something in the kernel core was constantly awake -- an infinite loop or livelock or something.
There's certainly the possibility that HTC and Verizon might have both missed something as glaring as that, but then their testing would have revealed markedly low battery life -- could they ship the device in good conscience in that state? WOULD they?
Basically, you can get high "load" in top even when it doesn't correspond to a userspace process or a labeled kernel thread. Things that contribute to load include:
1. Context switches (between user and kernel)
2. I/O (i.e., network, disk)
3. Kernel activity, both within the main kernel binary and in modules
4. CPU activity in userspace processes
Unfortunately, the process list in top doesn't always jive with the numbers in the load, because not all of the things that contribute to load can be attributed to a single process.
For example, if there's a kernel bug, and a single syscall from a userspace process foo.bin costs an unreasonable number of context switches, the CPU will spend as much time as it can trying to context switch to satisfy the syscall. I suppose if there were a "kernel" task in top, you could attribute the CPU time to that, but it wouldn't be fair to blame it on "foo.bin" because all the work (the context switches themselves) is being done in the kernel. That's just one possible example.
Oh, I forgot to ask: are you root? If not, you may not see processes reported in top that are owned by other users. So you might not even be getting the full picture of the userspace processes running on the device, let alone kernel tasks and other less tangible effects.
Before I rooted, I had System Panel installed and everytime I checked my CPU was at 99% and full 1024 on the clock.
After root, my CPU drops into the 1 digit %'s all the time, CPU speed runs between 600 - 1000mhz.
edit: this is on the stock RUU and stock kernel
Adam B. said:
I do (enforced by company policy). Do you think that's related?
Click to expand...
Click to collapse
i dunno.. it may be. read the thread i started here on why..http://forum.xda-developers.com/showthread.php?p=12301209#post12301209
i am trying to run a couple experiments in the next day or two to figure it out. its crazy that battery life varies SO much for people.
allquixotic said:
Ahhh, I've seen stuff like this on Linux servers before.
In one case, all the system processes were idle, but the load spiked to 25.00 during intensive disk writes. As it turns out, all of this processing was packed invisibly into the kernel; I was using software RAID at the time, and the RAID5 subsystem has to calculate parity bits for written data. So that's what was hogging CPU -- that, and the fact that my stripe width was 1 MB, probably way too big.
In another case, there was a kernel bug with the development kernel I was using (I think it was an -rc of 2.6.32) where something in the kernel core was constantly awake -- an infinite loop or livelock or something.
There's certainly the possibility that HTC and Verizon might have both missed something as glaring as that, but then their testing would have revealed markedly low battery life -- could they ship the device in good conscience in that state? WOULD they?
Basically, you can get high "load" in top even when it doesn't correspond to a userspace process or a labeled kernel thread. Things that contribute to load include:
1. Context switches (between user and kernel)
2. I/O (i.e., network, disk)
3. Kernel activity, both within the main kernel binary and in modules
4. CPU activity in userspace processes
Unfortunately, the process list in top doesn't always jive with the numbers in the load, because not all of the things that contribute to load can be attributed to a single process.
For example, if there's a kernel bug, and a single syscall from a userspace process foo.bin costs an unreasonable number of context switches, the CPU will spend as much time as it can trying to context switch to satisfy the syscall. I suppose if there were a "kernel" task in top, you could attribute the CPU time to that, but it wouldn't be fair to blame it on "foo.bin" because all the work (the context switches themselves) is being done in the kernel. That's just one possible example.
Oh, I forgot to ask: are you root? If not, you may not see processes reported in top that are owned by other users. So you might not even be getting the full picture of the userspace processes running on the device, let alone kernel tasks and other less tangible effects.
Click to expand...
Click to collapse
Interesting info. I'm also a Linux admin, but I haven't really run into situations like this.
It is very odd that I see nothing in the user space that would cause this. http://pastebin.com/J4PwuMeZ Every process is sleeping, and nothing seems to be waiting on IO.
I suppose it could be an issue with the kernel. We'll have to wait and see what happens when the source is released and people start to release new updates.
I am root, btw.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Settings Optimilization
(Requirements: being literate, at least half a brain, common sense. If you don't meet these, listen to da song
and go away)Processor Tweaks
CPU Governor
A CPU governor in Android controls how the CPU raises and lowers its frequency in response to the demands the user is placing on their device
1: OnDemand Governor:
Main goal of the ondemand governor is to switch to max frequency as soon as there is a CPU activity detected to ensure the responsiveness of the system. Ondemand jumps to maximum frequency and decreases the frequency gradually when CPU is less loaded/apporaching idle.
2: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency.
3: Interactive Governor:
Can be considered a faster ondemand. Snappier with similar battery life.
4: Performance Governor:
This locks the phone's CPU at maximum frequency. Not very power efficient but God, it's fast.
Minimum and Maximum CPU Frequency
These are the values between which your cpu will scale it's clockspeed. The lower is Min value the less battery your phone should consume when not bothered. Max value is the border of how high you will let you CPU go.
The higher it goes the more battery it eats. Many people say it improves the performance, some that it doesn't. Too high values can cause freezes so don't be surprised when that happens
HTC Desire S values:
Min 245-368
Max 1024-1516
Experimental 1612-1804
I/O scheduler
I/O scheduler basically determines the order in which things get written to or read from storage. It will prioritize each block of data based on which process is requesting the operation or how much time it takes to complete each operation
1: Noop:
Inserts all the incoming I/O requests to a First In, First Out queue and implements request merging.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
2: Deadline:
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
3: ROW
The ROW IO scheduler was developed with the mobile devices needs in
mind. Favoring READ requests over WRITEs decreases the READ latency greatly.
Advantages:
Best READ values so very fast user experience
Disadvantages:
Not so good at WRITEing
4: CFQ:
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ.
5: BFQ
Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
Set on boot
This option sets your CPU values on boot. It's good to let your phone run on your settings for a while before doing that.
Memory management and miscellaneous
zRAM
zRam is a virtual memory, also known as swap space, which lives in the ram. Virtual memory is the part where the system stores memory fragments which are not accessed, making more room for apps to store information in the ram. From my experience makes phone faster.
Advantages:
More memory for you.
Disadvantages:
It uses CPU to compress/decompress so battery dies faster/might cause some lags.
Allow purging of assets
Purging of bitmap memory assets. Think of it as allowing stale items in RAM to be tossed out when you need more RAM.
Kernel samepege merging
Let's say that we have processes called "A" and "B". "A" needs "Y" data to be loaded in memory to run and "B" needs "Z" data. Assuming that "Y" and "Z" are identical kernel samepege merging merges those identical processes into "X" thus increasing available RAM.
16bit transparency & Surface iprovement
Some users claim better performence/smaller battery usage after enabling 16bit and disabling Surface improvement
Barebones
Some of the apps that come with your phone can be safely removed without causing stability issues. They take up space and use resources that could be used for other things. Removing unwanted apps will theoretically make your phone run faster and smoother, plus, you can configure your phone just the way you want it.
WE WANT YOUto help developing Barebones
How do I do that?
1. Click on the link.
2. Login to cyanogenmod wiki.
3. Click edit
4. You will see a list of templates. Click (edit) next to Template:Barebones cm10.1
How do I add an app?
You will see something like this:
! <apk name>
! <package name>
! Remove
! Description
! Version
|-
|Android keyboard
|com.android.inputmethod.latin
|{{yes}}
|Stock android keyboard. Safe to remove if replaced with something else for eg. Swype,Swift
|4.2.2
|-
Click to expand...
Click to collapse
These are columns:
! <apk name>
! <package name>
! Remove
! Description
! Version
Click to expand...
Click to collapse
This is how you start and end your row:
|-
Click to expand...
Click to collapse
Behind this you have to write your column content
|
Click to expand...
Click to collapse
Warning! You always have to make all columns even if you want to leave them empty.
Modding
Modding
So, Google IT guys are the best, they know everything better and magic rainbow is flowing out of their arses... Yet still some people find ways to improve Android:
V6 Supercharger:
Turbo Boost:
RTMixManager™
Looking for a real functioning game booster? Get one here!
CrossBreeder
Lag Reduce/Entropy/DNS+/Tether+/Adblock/Censor Bypass
Direct Injection Turbo
The end
What do you want from us?
1. Post your settings/OC/ideas on how to make Phone run Faster.
2. Help updating Barebones.
3. Post Mods you're using
Credits: droidphile, mj.vikram, http://androidforums.com/, http://rootzwiki.com/, http://wiki.cyanogenmod.org/, and others...
not bad.... here are some suggestions for post 3
http://forum.xda-developers.com/showthread.php?t=2076101
http://forum.xda-developers.com/showthread.php?t=2113150
http://forum.xda-developers.com/showthread.php?t=2158329
Sent from my GT-I9505 using Tapatalk 2
hisname said:
not bad.... here are some suggestions for post 3
http://forum.xda-developers.com/showthread.php?t=2076101
http://forum.xda-developers.com/showthread.php?t=2113150
http://forum.xda-developers.com/showthread.php?t=2158329
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Thanks! Updated.
Hi there is like this new setting in cm11, force high end setting. Anyone care to share their thoughts about that?
Hello M2 users, y'all probably wondering what did I mean by the thread title above so I'll get straight to the point nice and simple.
Using a stock kernel sucks, any CPU Tuner will go bonkers adjusting frequencies only to see it revert to stock again. So, while browsing for ways to optimise performance and battery in the Xperia, I came across this guide (now updated to this) on our Interactive governor. While it's on a different phone, the explanations are clear enough to tell anyone that yes, this can be adapted so long as you are rooted.
So read the whole post to give yourself an idea on the functions available for you. I use Kernel Adiutor for this as it seems most reliable.
But first, go into your build.prop files and edit this code:
Code:
ro.min_freq_0=300000
Set the frequency to 300000 (300Mhz) and restart or your phone will always be stuck on a higher frequency.
Also in the Kernel Samepage Merging, turn it off. There isn't much of an impact between battery and performance so this function is useless.
So now head into the CPU section, towards Tunables and add the following values according to the screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/img]
This gave me 50% battery usage over 26 hours, with 5 hours of Screen on Time used by chatting, gaming, and web surfing. Pretty good looking at all the times I've run the battery with less usage.
Anyhoo, I hope these settings are useful for y'all and if anyone has any modifications to these settings please do share it with your results. This may perhaps be the only guide where we control the governor on a deeper level rather than taking it as it is, so let's squeeze as much juice out of this phone as possible.
Update: These are the settings I've settled with, no negligible battery life and not much of an impact on performance. The voltage tables for the SD400 looks to be dynamic so you can't get an exact reading and anyone who looks at it will suggest you buy a new phone instead >.>
How do you add multiple values on one settings ?
I can't seem to be able to
FrWhyMe said:
How do you add multiple values on one settings ?
I can't seem to be able to
Click to expand...
Click to collapse
Right now you can only add multiples for above_hispeed_delay and target_load. Just tap the space bar each time you add in new values and the app will auto-arrange it for you. If it still doesn't work, what kernel are you using?
Can you repost the photo or write the values please?
basem_ym said:
Can you repost the photo or write the values please?
Click to expand...
Click to collapse
I'm not using this anymore, Sony's stock setting is fine unless you can somehow change the voltage.
AutumQueen92 said:
I'm not using this anymore, Sony's stock setting is fine unless you can somehow change the voltage.
Click to expand...
Click to collapse
I spent last week trying to study and understand those govenors.
Since yesterday, I was trying and tunning the stock interactive govenor
I didnt notice any major changes in performance but I was surprised by power consumption
Ex: I used to play Solitaire everyday more than 2 times a day, each time I spend like 1 hour and my battery drops like 10%
After tunning the interactive govenor my battery drops like 4-6%
Which means its much better than stock
I'm using EagleExperience rom which come with stock kernel
Anyway I just want to know your tunnables because the photo you posted is not opening
I want to compare them with my numbers
Thank you for this post and sorry for bad english
It's not my first lang.
basem_ym said:
I spent last week trying to study and understand those govenors.
Since yesterday, I was trying and tunning the stock interactive govenor
I didnt notice any major changes in performance but I was surprised by power consumption
Ex: I used to play Solitaire everyday more than 2 times a day, each time I spend like 1 hour and my battery drops like 10%
After tunning the interactive govenor my battery drops like 4-6%
Which means its much better than stock
I'm using EagleExperience rom which come with stock kernel
Anyway I just want to know your tunnables because the photo you posted is not opening
I want to compare them with my numbers
Thank you for this post and sorry for bad english
It's not my first lang.
Click to expand...
Click to collapse
These are my current settings, the 300Mhz and 787Mhz share the same voltage and any higher frequency has the same voltage too so it's more efficient to use Sony's settings. The only difference in here is I used Intelliplug to better control how they ramp up.
AutumQueen92 said:
These are my current settings, the 300Mhz and 787Mhz share the same voltage and any higher frequency has the same voltage too so it's more efficient to use Sony's settings. The only difference in here is I used Intelliplug to better control how they ramp up.
Click to expand...
Click to collapse
In target loads, you have frequencies that aren't supported on stock kernel (1.4GHz)
DavidMKD said:
In target loads, you have frequencies that aren't supported on stock kernel (1.4GHz)
Click to expand...
Click to collapse
That's because my kernel is overclocked.
above_hispeed_delay: 40000 998400:45000 1090400:50000 1190400:55000
boost: 0
boostpulse_duration: 0
go_hispeed_load: 99
hispeed_freq: 787200
io_is_busy_: 0
min_sample_time: 0
sampling_down_factor:1
sync_freq:300000
target loads: 80 600000:80 787200:90 998400:95 1090400:97 1190400:99
timer_rate: 60000
timer_slack: 480000
up_threshold_any_cpu_freq: 0
up_threshold_any_cpu_load: 0
Ksm off , no hotplug min:300 mhz max:1190 mhz
I am using this settings for now. I tried to lock 300-787 mhz for the my daily usage (whatsapp, youtube, cm browser, simple games like fun run) high frequences for heavy games, installing apps.
Is that config fine ? I tried semil's config its battery performance was great but i think it is slow config.
batuskas said:
above_hispeed_delay: 40000 998400:45000 1090400:50000 1190400:55000
boost: 0
boostpulse_duration: 0
go_hispeed_load: 99
hispeed_freq: 787200
io_is_busy_: 0
min_sample_time: 0
sampling_down_factor:1
sync_freq:300000
target loads: 80 600000:80 787200:90 998400:95 1090400:97 1190400:99
timer_rate: 60000
timer_slack: 480000
up_threshold_any_cpu_freq: 0
up_threshold_any_cpu_load: 0
Ksm off , no hotplug min:300 mhz max:1190 mhz
I am using this settings for now. I tried to lock 300-787 mhz for the my daily usage (whatsapp, youtube, cm browser, simple games like fun run) high frequences for heavy games, installing apps.
Is that config fine ? I tried semil's config its battery performance was great but i think it is slow config.
Click to expand...
Click to collapse
I try not to limit my frequencies since the point is to go high performance only when needed. I'm not sure about your config since I never turn off hotplugs.
DISCLAIMER: This is not professional thread. This is just a simple guide to increase FPS from a newbie to newbies like me.
I really love playing PUBG. I have seen many people discussing the performance of PUBG Mobile for our lovely Mi A1 and I wanted to share with you few non-root methods to improve your performance in PUBG Mobile. I have been testing and experimenting with it and I have made a REALLY SIMPLE and EASY list with my recommendations which can really give you about 50-60 FPS, none of these methods require root, custom ROMs or kernels:
1) Download GFXTool app from Google Play
This app allows you to completly edit graphics settings for PUBG Mobile. You can change resolution, graphics, AA and even shadows and more. First pick your server and then edit those settings. Just skip all the ads.
For the best result set this:
Resolution: 960x540
Graphics: So Smooth
FPS: 60 FPS
Disable shadows and let the style be Classic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: If you want some playble graphics, set Anti-aliasing to ENABLE to reduce the "pixelness" - it may cost you a few FPS
2) Overheating slows the device
It is enormously hot outside, especially now in summer. And so hot is your phone when you play PUBG. I recommend to take a break for your phone after every longer game. I have noticed small performance decreases after playing longer game, that's because it is really hot outside and our phone doesn't cool enough. Overheating decreases your phone's lifespan and performance. Just don't play while charging the battery. A smaller thing is to correctly hold the phone with your hands while playing, because if you don't give a colder air for your phone, it can't cool down. It is recommended to put off your mobile phone case while playing to let the phone cool down.
3) Overlay windows and bubbles
Don't use any chatting or notification bubbles on your screen while playing. The most famous one is Facebook Messenger, pop-ups decreases your performace a lot.
4) DND
DND means Do Not Disturb. You may laugh, but this can highly improve your performance in PUBG. Notifications jumping on your screen like Messenger really lags the game. By setting the DND your apps won't disturb you while playing, but the thing is, that you have no sound. Let's hope that in future updates will Xiaomi let us use sound from media while DND.
5) Don't play with low battery
My Mi A1 shuts down 4 cores of my CPU while it is somewhere under 25% of battery percentage. This can highly slow down your phone while playing PUBG.
6) Other smaller tweaks
Turn of microphone and voice in the game
Don't use any security software which can run in the background
Close your recent apps which may run in the background
Reboot your phone before playing
Disable automatic updates on Google Play to reduce the updating of your apps while playing the game
That's all from me. Feel free to criticise me or even correcting me. These were the simpliest methods to keep your game running at 60 FPS without any modifications or root.
Happy WINNER WINNER CHICKEN DINNER!
I thought the 4 cores thingy triggered at 10% ? Or did they change that in newer versions ?
Can someone plz make Tweeks for asphalt 9 graphics as well , it looks grains and not smooth. Thnx in advance .
gougous3 said:
I thought the 4 cores thingy triggered at 10% ? Or did they change that in newer versions ?
Click to expand...
Click to collapse
I remember it triggered already at 25%, but who knows how it works... maybe in current version of Android it triggers lately.
Sent from my Mi A1 using XDA Labs
Just wow, amazing ?
arjiyunandar said:
Just wow, amazing
Click to expand...
Click to collapse
Graphics look horrible but FPS go up my friend, up to 60 without any problem
Few things:
Pubg removed frame rate access on 0.7 will return in 0.8
Source: official gfx tool changelog and in-app faq.
For our device fps is maxed at 30-40 fps. Why? read above text
Four cores shutting down happens when andriod battery saver mode is activated which can be set to 5% or 15%. not 25%.
Note: fps thing might wring. Welcome corrections based on screenshot using a fps meter.
alkesh95 said:
Few things:
Pubg removed frame rate access on 0.7 will return in 0.8
Source: official gfx tool changelog and in-app faq.
For our device fps is maxed at 30-40 fps. Why? read above text
Four cores shutting down happens when andriod battery saver mode is activated which can be set to 5% or 15%. not 25%.
Note: fps thing might wring. Welcome corrections based on screenshot using a fps meter.
Click to expand...
Click to collapse
I dont know how to do that, but I definitely have 60 fps. And no, even if battery saver is off, 4 cores still shut down - I've tried this.
TrueMS said:
I dont know how to do that, but I definitely have 60 fps. And no, even if battery saver is off, 4 cores still shut down - I've tried this.
Click to expand...
Click to collapse
Just curious how can you say you definitely know it's 60 fps.
When there was option available fps was in 40-60 range and try proning or going through smoke fps goes 18-30.
4 cores won't automatically shutdown until Android system tells cpu to do so and that happens to save battery.
First measure fps and see. There's an app called gamebench it requires pc.
And show screenshot for fps and cpu offline.
PS: this is an educational argument.
alkesh95 said:
Just curious how can you say you definitely know it's 60 fps.
When there was option available fps was in 40-60 range and try proning or going through smoke fps goes 18-30.
4 cores won't automatically shutdown until Android system tells cpu to do so and that happens to save battery.
First measure fps and see. There's an app called gamebench it requires pc.
And show screenshot for fps and cpu offline.
PS: this is an educational argument.
Click to expand...
Click to collapse
Thanks for educating, but none of this is new for me. I don't have currently PC available for few weeks. Then I would record the FPS for this thread. This thread doesnt say that it gives all time 60 fps, everything throttles and is not stable 60, it is guide to reach, again reach 50-60 FPS, not to play on 60 stable. I know how 60 FPS look like and I can say, that it is really close to it, sometimes it is 60.
Of course Android system tells the CPU to turn it off, I dont know where is the problem.
And come on, this thread is "from newbie to newbie".
Sent from my Mi A1 using XDA Labs
TrueMS said:
Thanks for educating, but none of this is new for me. I don't have currently PC available for few weeks. Then I would record the FPS for this thread. This thread doesnt say that it gives all time 60 fps, everything throttles and is not stable 60, it is guide to reach, again reach 50-60 FPS, not to play on 60 stable. I know how 60 FPS look like and I can say, that it is really close to it, sometimes it is 60.
Of course Android system tells the CPU to turn it off, I dont know where is the problem.
And come on, this thread is "from newbie to newbie".
Click to expand...
Click to collapse
Okay just bear with me.
In pubg we have frame rate settings like this:
Low - 15 fps (guess)
Medium - 20 fps (guess)
High - 30 fps (fact)
Ultra - 40 fps (fact)
Extreme - 60 fps (fact)
Fps shown here are the maximum allowed by game when those settings are chosen.
This means that when you set fps at High your game will not cross 30 fps.
Now do you see ultra and extreme options in 0.7?
If yes. Is extreme selected?
If yes. Then congratulations you can play pubgmobile at 60fps and thats awesome.
If No to any of those two questions then you cannot play at 60fps in 0.7.
And i have never said that you are talking about constant 60 fps.
This post isn't to challenge your experience as i don't whether you are new or old to this. I am just pointing out some inaccuracies.
Thanks.
Fps60
this is the settings that works very smooth for me
here's the screenshot
https://ibb.co/BgX9Kj6
https://ibb.co/QKXNkYN