Related
Hi... I have rooted my Samsung GS2 and payed for the OC app TEGRAK ..
But every time I go over 1400mhz the phone gets very unstable.
It even feezes at 1400 mhz when i use my navigon app...
I have tested it at 1500 mhz.. But reboots in a kind of save mode.,,,
At 1400mhz i runs Quadrant smooth with 4200 in score
And 56 MFLOPS in Linpack
But why is my phone so unstalbe?
But why is my phone so unstalbe?
Click to expand...
Click to collapse
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
BlueScreenJunky said:
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
Click to expand...
Click to collapse
At 1.4ghz the phone will also get hotter and it decreases the lifetime if you run 24/7 at 1.4ghz
Ok.. I know about the x86 cpu's.. But didn't think it was the same in ARM cpu's-
But I see ALOT SGS2 that runs 1800mhz..
I guess that I just have one of the not so OC lilkes...
Overclocking won't always work for everyone at same levels.
I've also seen evidence to suggest that OCing significantly reduces the life of the SGS2. Nobnut had his phone vastly overheating even on stock speeds, and constantly rebooting... He overclocked. A number of others reported similar.
Overclocking is not simple and it is not that you just click on 1400/1500 MHz and you are Overclocked. A lot of things matter here. When we overclock in our Desktops then we have to test it very thoroughly, setting up the right VCore, Bus voltage, Multiplier, checking the stability and temperature etc. etc. Tegrak OC is a nice and simple software to use, but it can't be perfect when you can't set all the settings manually other that just higher the clock rate. Personally I'd always stay with stock speed as incorrect OC could harm my CPU and GPU.
Regards.
If you know anything about overclocking then you'll understand that there are a variety of factors that affect the overclocking of a system. The overclock headroom you get from a processor varies, add to that the variables in component tolerance in the circuit board and you have a huge variety of factors that can limit the maximum frequency that you can overclock your system to.
I'll give you an example using my computers. Click on the images below:
Both processor overclock similarly on using the same components and that was the maximum I could get out of them. Now when I bought an EVGA X58 Classified motherboard and overclocked the Xeon W3520 I got it up to 4704 MHz with less vCore and less CPU VTT. All of this was done with aircooling.
My point is that not all systems will overclock the same even though they share the same model components.
I do not yet have a Nexus 7 to test this with. You use this at your own risk!
This is the first real kernel work I've done, so don't be surprised if it doesn't work. I've only provided a boot.img as fastboot is easy enough to use on the Nexus 7.
Features (If it works):
CPU OC to 1.7GHz maximum
CPU over volt to hopefully reach 1.7GHz
GPU OC to 600MHz
Simple IO scheduler
SmartAssV2 CPU governor
The boot.img is attached. Source can be found at my github.
If anyone here has a Nexus 7 it would be very helpful to know if it works. I should have mine soon though. If it works well, enjoy. Feedback is always welcomed, as are benchmarks. Thanks.
Removed link until fixed!
This is scary looking, an untested Overclock that's never been run on the hardware before.
I'm guessing that the T30L is just a speed binned T30 and as such this shouldn't damage it. The same overvolt (and higher) has been successful on the T30 to get even higher clocks (1.8GHz). I would test this given hardware, however I don't yet have my Nexus 7.
ben1066 said:
I'm guessing that the T30L is just a speed binned T30 and as such this shouldn't damage it. The same overvolt (and higher) has been successful on the T30 to get even higher clocks (1.8GHz). I would test this given hardware, however I don't yet have my Nexus 7.
Click to expand...
Click to collapse
This sounds interesting. Especially the 600mhz gpu OC but may I ask if you are thinking of implementing some kind of app interface to control gpu clock and voltages etc like Extweeks on google play please? As I am guessing a lot of people won't be able to go to 600mhz stably, so a way to change the OC to something like 520mhz (to bring it to T30 speed) would be a good option
I've seen voltage tweaks controlled from userspace on other devices but not the GPU clock. I'd like to get it working first, then I guess I'll look at such things, especially if there is interest.
Cel1084 said:
This is scary looking, an untested Overclock that's never been run on the hardware before.
Click to expand...
Click to collapse
you go first!
bencozzy said:
Glados kernel on the galaxy nexus allows gpu oc control.
Click to expand...
Click to collapse
Siyah kernel for the galaxy s2 and galaxy s3 both let you control gpu clock speed and voltages, might be cool to have something similar
I don't even have my Nexus yet, and i'm already downloading things to flash to it, hahah. Will report back once Google ships to the US!
if this kernel works can we control the clocks with antutu or similar?
The CPU clock should be controllable, and I'm working on making the overvolt controllable. The GPU clock is not yet controllable, and I'm not so sure where to start on that.
ben1066 said:
The CPU clock should be controllable, and I'm working on making the overvolt controllable. The GPU clock is not yet controllable, and I'm not so sure where to start on that.
Click to expand...
Click to collapse
you should put the gpu clock to 520mhz arnt t30l 413mhz stock and kai would be even slower assuming its the budget tegra3 soc
Right, here's the thing. I've spoofed the SoC speedo ID to be that of the standard T30, however, without looking through with a fine tooth comb, it seems that the top that that id goes is 600MHz. In usage, it may be 520MHz, but I'm not sure. In addition I'm fairly sure these are just speed binned, and can probably run at the higher clocks if we just add a bit more voltage, or they get a little hotter. If anyone can tell me if this actually works, then I can adjust either way.
Look at tegra3_dvfs.c, line 256-262. It seems to indicate a maximum of 600MHz.
This should be helpful to you. tegra3 technical reference manual. everything there is to know about all variants of the chip. how it works, what its capable of, schematics, diagrams, chip layout, etc,,
http://db.tt/vWWou2Fu
Thanks but I already have access to NVidia's Tegra portal, which includes the TRM for Tegra 2 and Tegra 3. I'm hoping I shouldn't have to mess with it that low level
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
When I feel the need the need for speed owww.
_thalamus said:
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
Click to expand...
Click to collapse
Our Tegra 3 CPU is a lower clock version that the normal T30, it's the T30L. I have no doubt that this will not damage your device, the voltages used are still less than used by some TF201 ROMs (the TF201 uses the T30). I included Simple IO scheduler since it is something that seems popular, latency isn't the only thing that matters (read http://www.vincentkong.com/wiki/-/w...42041E#section-Android+IO+Schedulers-Deadline). I have seen benchmarks that show both SIO and deadline as better than each other, it depends what metric you record. I didn't remove CFQ, it's not that I've added it. The scheduler can be changed if you so desire anyway.
I have not provided a simple flash package and I've clearly stated in red writing that this is UNTESTED. I do not have the device, and it is yes untested however I didn't see the point on keeping something potentially useful private. If you have the knowledge to use fastboot to flash a boot.img, you probably know how to flash back the old one too.
_thalamus said:
I don't understand why anyone would want to overclock a Tegra3, which is plenty fast enough already, especially when they have never even touched the device.
Also, I don't understand why anyone with any sense would use Simple IO scheduler, which has a higher latency and lower throughput than deadline, or even the bloat that is CFQ for that matter.
And finally, I don't understand why any real 'developer' would release something like this without testing it, especially with possibly dangerous overclocking and overvoltage settings. Only on XDA...
With all due respect, you should remove it until you have tested it *yourself* and confirmed that it doesn't make your Nexus 7 vanish in a cloud of smoke.
Click to expand...
Click to collapse
seriously harsh man, just because you don't understand doesn't mean its wrong, or right for that matter
ben1066 said:
Our Tegra 3 CPU is a lower clock version that the normal T30, it's the T30L.
Click to expand...
Click to collapse
I take it you understand why similar chips are rated at various speeds for different devices? Because they are designed with a lower thermal output and / or the cooling characteristics / power characteristics of the device are different. The T30L has lower speed apps processors, lower speed GPU and lower speed memory. All in all, it will pump out much less heat than a T30.
I have no doubt that this will not damage your device, the voltages used are still less than used by some TF201 ROMs (the TF201 uses the T30).
Click to expand...
Click to collapse
You don't *know* that it won't damage someones device, you are assuming that it won't. The likelihood is that it probably won't, but would you stake your life on it? I wouldn't, and I've been doing Android kernel development for some time.
Also, this isn't the TF201, and it isn't the T30. It is a different device with different thermal characteristics and a different SoC, you can't compare them like that.
I included Simple IO scheduler since it is something that seems popular, latency isn't the only thing that matters
Click to expand...
Click to collapse
Latency of reads and writes and throughput are the only 2 things which matter (and I mentioned both), and SIO is poor at both of them. Justin Bieber is popular, but he's still ****, so including something which is popular isn't really a good reason.
---------- Post added at 06:44 PM ---------- Previous post was at 06:33 PM ----------
foxorroxors said:
seriously harsh man, just because you don't understand doesn't mean its wrong, or right for that matter
Click to expand...
Click to collapse
Harsh perhaps, but I prefer honest. Necessary, most certainly.
It is stupid and irresponsible to release something which is untested and potentially dangerous as it isn't fair on the poor muppet that flashes it and then f**ks their device up.
It has only been released because some 'developer' wants to make his epenis bigger by releasing something for a brand new device on XDA. Not that I am saying that he is the only one, there's plenty of others that do it, but as I have one of these on order I am taking an interest in these threads and was quite surprised with what I saw.
As someone who has done kernel development for some time now, I would never dream of releasing something I haven't tested thoroughly myself, or which I have got a trusted tester to thoroughly test, but hey, this is XDA and the standards are low.
ben1066 just out of curiosity may I ask how the gpu scales frequencies on the Tegra 3 t30l please? As I am used to the galaxy s2 and s3 where you have numerous frequency steps like 166mhz, 260mhz, 350mhz and 440mhz and you have an up and down threshold to govern whether you jump up or down the available frequencies, is this similar to how the gpu in works on the tegra 3 please?
Also when you say overclock the gpu, is it replacing 416mhz with 600mhz or is it adding an extra gpu frequency step after 416mhz, so 416mhz is still available to be used if needed? Sorry one last question, if the gpu does have frequency steps like other gpus, what ones are available for use please?
I am sorry to ask, I am just so curious about these questions, and I can't find them anywhere on the internet, so any help would be greatly appreciated. Thank you so much
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
buntybauva said:
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
Click to expand...
Click to collapse
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
DespairFactor said:
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
Click to expand...
Click to collapse
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
I am giving snapdragon battery guru a try, it's for Qualcomm processors. But I'm not very experienced in this stuff. I think it has helped but if someone with more experience wants to give it a try. Maybe they can shed some new light on this subject.
This is the result with on-demand governor settings when phone is idle. with stock kernel and stock frequencies.
Ondemand has always been my fvorite for all past phones. in op2 however it always reverts back to original after interactive. the best battery saver for any phone is swithching to 4.4.2. Azimg batteru life. unfortunately notpossble with op2
buntybauva said:
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
Click to expand...
Click to collapse
Being rooted alone will prevent OTA updates. You have to flash the full stock ROM when there's an update anyway which would overwrite the kernel.
I've looked everywhere and can't find a root nor any threads can someone help me out
Just rooted mine with http://kingroot.net
It's just root, no recovery or bootloader so far, but after deleting bloatware and installing Sense 7, it's a perfect and snappy phablet ☺☺☺
I unlocked my bootliader on my Fierce XL 5045n, now what?
I just noticed a "allow BootLoader to be unlocked" option in developer options. Still can't get root though. But that should definitely help getting a custom recovery done. I still can't get root, tried numerous times, apk and with Windows. I'm stock lollipop 5.1.1 and have the box checked to allow bootloader to be unlocked in developer options but still nothing. Any ideas?
LazMike, did you try Kingroot?
nyttliv7 said:
LazMike, did you try Kingroot?
Click to expand...
Click to collapse
Yes, I did, thanks, didn't work at first but a newer version did the trick but some apps are denied permission from Kinguser even though I grant it and it shows they are granted, it also made my phone super laggy. Cant wait for a recovery and some custom ROMs.
That's weird? My phone got even snappier... But I deleted quite a bunch of apps though. My ram is showing like 1gb free most of the time. I'm using greenify, maybe that helps as well? But of course, it will be great when the real development starts for this phone ☺
LazMike said:
Yes, I did, thanks, didn't work at first but a newer version did the trick but some apps are denied permission from Kinguser even though I grant it and it shows they are granted, it also made my phone super laggy. Cant wait for a recovery and some custom ROMs.
Click to expand...
Click to collapse
What version did you use?
I think it's the newest. 4.5.2, a older version wouldn't work, I keep getting permission denied for certain apps, even though they are granted and shows they are as well. I also keep losing root and Kingo has to redo it.
Ok so here's some tips for people who wanna root:
>-Download Kingroot 4.6.0 and use that to root. It may take a few tries but it'll root
>-In general settings, turn off smart authorization so it won't constantly ask for permissions that you already granted
>-If you want your Fierce XL to be faster and less battery consuming, download Kernel Auditor from the Play Store. When it's installed, grant root permission for it, go to the menu, tap where it says "CPU", and where it says " CPU Governor", click on it. It should have an option that says "powersave". Click on that one and you're good to go
>REMINDER: You need to root first to do all of this
psycho_deth6 said:
Ok so here's some tips for people who wanna root:
>-Download Kingroot 4.6.0 and use that to root. It may take a few tries but it'll root
>-In general settings, turn off smart authorization so it won't constantly ask for permissions that you already granted
>-If you want your Fierce XL to be faster and less battery consuming, download Kernel Auditor from the Play Store. When it's installed, grant root permission for it, go to the menu, tap where it says "CPU", and where it says " CPU Governor", click on it. It should have an option that says "powersave". Click on that one and you're good to go
>REMINDER: You need to root first to do all of this
Click to expand...
Click to collapse
It's of course a matter of personal taste and needs, but I don't agree with the choice of Powersave Governor. I use 3C toolbox Pro to change OOM settings to a level were most services "dies" after a set time of non use, which gives a bit snappier experience and less pressure on battery. Of course you need to be careful with OOM (ram) to not "kill" to fast, loosing more multitasking power.
My battery got better and better, and now after a week of heavy use from 100% down to 5%, it lasts from 8 to 14 hours, depending on usage. Fairly good for a midrange phone.
And I do prefer the built in Cpu Governor (interactive). It's a good balance between snappiness and battery. Powersave on the other hand, will obviously save battery, but for sure also make the system slower. But as I said before, it's all up to the user and his needs and expectations.
"Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above."
nyttliv7 said:
It's of course a matter of personal taste and needs, but I don't agree with the choice of Powersave Governor. I use 3C toolbox Pro to change OOM settings to a level were most services "dies" after a set time of non use, which gives a bit snappier experience and less pressure on battery. Of course you need to be careful with OOM (ram) to not "kill" to fast, loosing more multitasking power.
My battery got better and better, and now after a week of heavy use from 100% down to 5%, it lasts from 8 to 14 hours, depending on usage. Fairly good for a midrange phone.
And I do prefer the built in Cpu Governor (interactive). It's a good balance between snappiness and battery. Powersave on the other hand, will obviously save battery, but for sure also make the system slower. But as I said before, it's all up to the user and his needs and expectations.
"Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above."
Click to expand...
Click to collapse
You're kinda right, powersave does kinda suck sometimes. I wish they had the "Conservative" governor. That works for me
Anyways, this phone has all we need to become a perfect one, as soon as we get our custom recovery ☺
I'm searching through alcatel and MSM8909 forums to see who's behind their recoveries ☺☺☺
DO NOT TRY TO INSTALL XPOSED
YOU WILL BRICK YOUR PHONES
Sent from my 5054N using Tapatalk
yea kingroot is being a pain I have 1 GB internet speed i can download anything fast except this stupid 15.3mb file when i finally got done realized it was the chinese version now have to wait another hour hope it works though
Is anyone familiar with the built in recovery mode? What limitations does it have?
I'm not sure, but if the following similarities are enough, then maybe this thread can help us experimenting?
Fierce xl:
Qualcomm MSM8909 Snapdragon 210
Quad-core 1.1 GHz Cortex-A7
Adreno 304
PIXI 3 (5) 4g:
Qualcomm MSM8909
Quad-core 1.1 GHz
Pixi 3 (5.5) LTE:
Qualcomm MSM8909 Snapdragon 200
Quad-core, 1.1 GHz Cortex A7
Adreno 304
http://forum.xda-developers.com/showthread.php?t=3193624
Can someone upload the stock dialer apk and odex for this phone?
Sent from my 5054N using Tapatalk
Remove kingroot entirely so my xl is stock again can anyone help me
I'm trying to remove the kingroot root entirely from my phone everything I get or send a picture message it does not download and open or send ever since the I ingrown was installed also emojis worked at first but no long show up please help with removal of all kingroot settings apps and return to store bought settings
mamirie2015 said:
I'm trying to remove the kingroot root entirely from my phone everything I get or send a picture message it does not download and open or send ever since the I ingrown was installed also emojis worked at first but no long show up please help with removal of all kingroot settings apps and return to store bought settings
Click to expand...
Click to collapse
were you using the newest version of kingroot? I've had none of these issues
AesopRock127 said:
were you using the newest version of kingroot? I've had none of these issues
Click to expand...
Click to collapse
As far as I know I was but I unrooted my phone but still can't download incoming pix or see emojis the emojis keyboard is there just don't show them
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
If thats true, thatd be a heartbreaking, the first thing I look to before choosing a device, is clock speed
Unlock the game optimization
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Linux User said:
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Click to expand...
Click to collapse
You mean game optimization in settings/battery? I think we do not have that option in custom ROMs (I am currently trying Aicp 12.1) and never changed it in stock. I will try going back to stock to disable that option and see if the frequency table changes... If it does, it will be a pre-requisite before flashing custom ROMs in our device. Still, it is something the kernel should handle.
I would underclock the device on my own, as I did with my good old G2, but not having the option for the CPUs to scale as intended is not cool...
Well, frequency table shows no change with stock, but somehow, CPUs 3 and 4 scale up to 2150mhz now.
I guess LG did not cheat in the strict sense of the word, but just does not want us to have control over our devices...
Sent from my LG-H850 using Tapatalk
Floodland said:
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
Click to expand...
Click to collapse
So... I was freaked out after reading this thread, so i rushed to check using cpu Z and it turned out that mine is clocked at 2.15, so i don't know what is wrong u
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Android_420 said:
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Click to expand...
Click to collapse
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Floodland said:
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Click to expand...
Click to collapse
old versions of kernel auditor are buggy with the g5, they see it as a single quad core instead of big/little dual 2 cores. You need the newest kernel auditor.