My nexus 10 froze two times today ( pretty normal, it usually freezes about 5 times a day) but today, a strange sound came out of it ( "rrrrrrrrrrrrrrrrrr" )
I don't know if it were the speakers or if it came from somewhere inside the tablet... I am very disappointed, I sold my transformer tf101 because it froze 3 times in a week, that was already to much for me. Why can't Google just fix it ? Or are they working on a fix ?
Inse
Sent from my Nexus 10 using XDA Premium HD app
Are you on a custom kernel? That sounds similar to the CPU crashing and hanging, thus the repeated noise
try setting your cpu governor to performance if you have a custom rom or kernel. solved the issues with rebooting for me (for the most part)
Well, you have to determine why the tablet is rebooting. If the device is getting noticeably hot and there is a "slideshow" effect then it is a indicator that it is being thermally throttled. Changing the governor won't necessarily fix this and in some cases can exacerbate it.
If you are indeed on a custom kernel, then then the kernel crashed. If its a reoccurring event then I would look at flashing a different kernel (Ktoonz or another) and seeing if that fixes the issue.
I haven't installed a custom kernel or custom rom, I not even rooted. On the left side of the camera ( when holding in landscape) the tablet gets very hot while playing simple games like pudding monsters. Is that normal ? Happens it to anyone else ?
Send from my lovely Sensation XL,
If I succeed helping you (rare) don't forget to hit the thanks button
There is currently a theory (tested by members and mostly supported by gathered data found in this thread) that the CPU does not have a temperature sensor and instead estimates temperature based on an equation. According to the member who did some testing, the equation is way off from the actual temperatures. This can cause freezing (due to lag from thermal throttling) which would account for the sound or the random reboots as the temperature equation reaches a critical point and reboots the device.
I would pay attention to the KT Manta kernel thread as there's some interesting research going on over there. I can say having used that kernel from day one, 100 MHz to 1.7 GHz and extremely undervolted I haven't experience a single instance of throttling or rebooting. The only reboots I've had were when I was dialing in my undervolts. I tried messing with the GPU voltage, but mine appears to be somewhat picky and I really couldn't undervolt the GPU much. The CPU on the other hand undervolts like a champ.
However, if the theory that Samsung uses an equation to determine temperature and not an actual sensor, undervolting will have zero effect on "temperature" though it will save battery. Having never encountered thermal throttling (even after significant game play and other activities) I can't speak to that issue. Though I can say that with my undervolt settings, the battery lasts a crazy long time and I have absolutely no performance issues.
Related
According to the System Tuner app, my CPU went up to 75 degrees Celsius while I was playing a track on Google Earth. I was running Earth for only a few minutes before it reached 75. I'm not sure if that's the peak yet...maybe it can go even higher.
I've seen several other threads about heat, but most people talk about 50s and 60s. Anyone reach 75C? The front and back of the phone, the top around the camera, were both very hot. It was almost uncomfortable to touch.
Again, I'm talking about 75 Celsius, not Fahrenheit. And I'm referring to CPU temperature according to System Tuner app, not battery temp. Anyone reach this?
picture plz.
the reason is bc someone did a stress test on the N4 and found that the device shuts down at ~57-59C (correct me if im wrong) to prevent damage to the hardware.
Edit: found the link http://www.youtube.com/watch?feature=player_embedded&v=koLJ4BU9tgc
75ºC on a quad core?
I thought it was supposed to be more efficient than a dual core... 167ºF just seems like it's way hotter than any electronic device should ever be.
Sent from my SPH-D710 using xda premium
My first gaming laptop was an ASUS Republic of Game first generation. They did a horrible job cooling the machine. During the 2 months before the machine failed, the GPU would reaches 110 - 140 C if I played games (then, of course, the machine turned the GPU off and still ran as everything else was still about 70-80 C)
When the machine did fail, I opened it up, and found 2 fried thermal unit, a fried GPU and a nearly fried HDD) Amazingly, the machine stills runs, as long as I don't load GPU driver
Well, that's the story. Back to OP, as you see, if the temp is too high, you device can be literally fried. So if you turn off the thermal throttle, please enable it back on and do you best to keep your device cool
I tried to replicate just now and could only go up to 63c. I don't want to keep trying based on the comments here so far. If it happens again I'll be sure to get a screen shot and be aware of what's running.
Where would the thermal throttle toggle exist, if I have the capability at all? I'm running faux123 kernel and use trickster mod and trinity kernel tools for tweaking. I don't see anything about throttle control.
On a similar note, faux123 seems to default to 1ghz minimum cpu frequency. Does that seem right? I've flashed lots of kernels before on previous phones and they always default to the lowest value. When I force the setting down to 384mhz, it automatically changes back to 1024mhz the next time I go in my tool apps. Does this seem normal?
denimjunkie82 said:
Where would the thermal throttle toggle exist, if I have the capability at all? I'm running faux123 kernel and use trickster mod and trinity kernel tools for tweaking. I don't see anything about throttle control.
Click to expand...
Click to collapse
I haven't seen a Nexus 4 kernel that has thermal throttle toggle, or have it disabled yet. I am just checking if you're running one that I am not aware of
denimjunkie82 said:
On a similar note, faux123 seems to default to 1ghz minimum cpu frequency. Does that seem right? I've flashed lots of kernels before on previous phones and they always default to the lowest value. When I force the setting down to 384mhz, it automatically changes back to 1024mhz the next time I go in my tool apps. Does this seem normal?
Click to expand...
Click to collapse
Minimum cpu frequency enforced by kernel is normal. I am not certain if faux123 default to 1 ghz min, but if it's the case, it seems weird for me too. Definitely not good for the battery. If there's no other CPU control apps, I recommend double check the settings, then find an update for faux123, or use trinity kernel
I just flashed a new kernel and my minimum cpu now seems more normal. I hopefully that alleviates the crazy temperatures too.
I'll try to test again tomorrow to see if my temps still go bonkers. It's time to sleep now. Thanks for the help, everyone.
I'm having issues when playing certain games with the phone rebooting. The phone back seems to get progressively warmer and finally the phone will reboot. Has anyone else experienced issues like this with their N4?
If I load the game back up after the phone reboots it'll reboot in a much shorter period. Almost like the CPU is overheating.
anamin said:
I'm having issues when playing certain games with the phone rebooting. The phone back seems to get progressively warmer and finally the phone will reboot. Has anyone else experienced issues like this with their N4?
If I load the game back up after the phone reboots it'll reboot in a much shorter period. Almost like the CPU is overheating.
Click to expand...
Click to collapse
When the nexus 4 reaches a warmer temperature something called thermal throttling kicks in and it clocks down the CPU and GPU to handle the heat. Your games will start to run slower and you will see FPS drops. If the temperature still continues to increase the phone will shut itself down to save itself.
A lot of nexii 4 get hot but most users can fix the problem by flashing a custom kernel and undervolting the phone. A few popular options are faux, franco, trinity and matrix you can try those out first.
Sent from my Nexus 4 using a toaster
Hi,
My LG P500 (Rocking 512MB!) has a custom recovery since february, now. Since then I've been switching ROMs a lot, the first being CM11 which I switched really quickly to CM7, rock stable and fast, still one of the best ROMs I've tested. Also tried CM12 (KitKat), AOKP, VoidForever and Oxygen.
Using Oxygen at the moment, being the lightest and fatest, really stable.
Naturally I've been playing around with CPU frequencies since february too which was really useful in the long run. Underclocking and underclocking, while I did not kept the LG overclocked 100% of the time.
I did more benchmarks and stuff on Oxygen, testing out more overclock frequencies stability - people complaining of fried CPUs are rare to my knowledge (Well, didn't read much), and anyway, I can now find the LG P500 for 30-50$ used. My LG starts rebooting from 787 MHz, so I generally can use 729-768 MHz for a few time. I always depend on which factors, how much times does it actually takes before the device reboot due to unstability/unstable overclock, which I would like to know why, the hardware logic behind the reboot.
729 MHz has been really stable since a long time - I don't know if it's just me, but I feel like the CPU might be weakening after all this time, if it's possible at all? Not sure. But it does happend that it randomly reboot on 729 MHz still, pretty rare. Doesn't matter thought, if the CPU happens to die, I'll just buy another cheap one I guess.
But what is the actual cause of these reboots, overclocking sure push the CPU more than it should, so in theory it shorten battery life, and CPU lifespan too, also produce more heat. Which makes senses that when the phone get too hot, it reboot due to a thermal protection, same thing goes for computers.
Still sometimes, battery isn't that hot anyway, 32 degrees? 30? I've never exceeded 40 (Which is really rare, while charging - at this point I stop using the phone for a while) Apparently, LG P500 does not support showing the CPU temperature, tried, no succeed.
So is the CPU going too hot in that case? I'm aware I couldn't do anything to, hm, make overclock more stable, impossible besides lowering the frequency, but I'm just curious, would just like to know the logic, why does the phone choose to reboot? Just simply crashing? Hm, may I ask, what causes this crash? Entirely hardware related, right? I've tested overclocking with different kernels, while Android 4.0 had a worse tolerance to higher overclock, doesn't matter which kernel, my device can never get above 768 MHz without an instant crash. Why is the crash instant ?
Would like to know the logic behind overclocking affecting stability, please. Is that explainable? Exclusively hardware crashing? Or hm, does the software report any kind of alert at some moment, I don't know?
(On a side-note, never managed to overclock my PC CPU, Intel Core i3-2350M Sandy Bridge, apparently locked. Not ready to do this (Not the same price value obviously!), just wanted to see if that was possible on my laptop and so, how. Never figured that out, well, doesn't matter)
Thanks
Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app
Denhot said:
Hello,
I have a peculiar problem with my OnePlus Two
The faster A57 cores don't get activated, I have tried using Antutu, played Asphalt 8 And NFS NL for hours.
But the cores just won't get triggered
I'm using A1 CPU tool to monitor the same.
Even CPU Z wouldn't show me any activity on the other 4 cores while Antutu was running.
Any ideas? It's brand new can be returned
Oxygen OS - 2.1.1
A2003_14_151011
Sent from my C6602 using XDA Free mobile app
Click to expand...
Click to collapse
I just installed A1 CPU to verify your issue.
It shows cores 0,1,2,3,4 are used at 1344ghz for me as well.
When i check with synapse (i'm on AK kernel) it shows all cores are used.
I guess it's a limitation with A1 CPU tool. Try with other tool that supports such architecure.
I was sceptical on the same but, out of the box I remembered seeing 1777 MHz frequencies.
Thanks a lot
I shall try more tools and get back.
Though I think if you're on a different kernel and had the A1 CPU tool been correct it would be redundant, Because core allocation would be done on kernel level (in my knowledge).
Sent from my iPad using Tapatalk
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.
ollimi1 said:
With a battery level of 19% I was not able to get the 4 A57 cores online...
Click to expand...
Click to collapse
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.
jemcik said:
It looks like some system configuration files with kernels activation policy have to be edited,
but I haven't found yet which files exactly.
Click to expand...
Click to collapse
I've never experienced such a function!
CPU power depending on battery voltage!? 62k with full battery, 49k with 20% battery both with same CPU temps!
Hopefully not a general problem on our side with the motherboard Voltage Regulator or something.
Have you been to a kernel thread and asked this question? If not, I will ask this in AK's kernel thread. Maybe he knows more about it!
The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.
jemcik said:
I know that it was already discussed but maybe someone has found a solution.
The problem is that performance of device gradually decreases proportionally to the level of the battery.
For example:
- battery is 90%, Real Racing 3 runs perfectly,
- battery is 45%, some lags appear during gameplay
- battery is 10%, heavily FPS drop, almost impossible to play
Battery saver is turned off, device is cold in all tests.
If I would like to save my battery level - I will turn on battery saver manually,
but I WANT to have good game experience not depending on battery level
This is really crazy.
Tested on stock OOS 2.1.1, with stock kernel, with Boeffla an AK, tested on Exodus ROM - everywhere I can see this weird behaviour.
May be some system files must be edited to overcame this issue?
Click to expand...
Click to collapse
Hi,
would like to share I don't have a similar experience, with NFS NL or Asphalt, phone was consistent with no lags even when it got unbearable to hold.
I as playing and simultaneously screen mirroring over to a TV.
Going from 65 to 25% over a long course.
I normally won't let my battery fall below 20%.
So the thing about Li-ion/pro is that as you go lower voltage decreases so to provide same power draw current increases.
Basically it would heat up faster.
That can be a reason combined with that their might be inbuilt measures to save battery like you said, nor as an engineer I would recommend you to stress your phone at those levels.
I can't explain the lag at 45%, didn't find it might try real racing 3 later to check.
Sent from my iPad using Tapatalk
trapistasajt said:
The 4 high performance cores will only be activated when needed. What app are you using to check the core usage? Every now and then you should see 2 of the high performance cores sometimes coming to life every now and then, with the other 4 power efficent cores being more busy. Use CPU-Z to check.
Due to the way Oxygen OS's stock kernel works, only 2 of the high performance cores will ever be active, alternating between the 4 cores in an attempt to keep the phone cool and not throttle as often. If you want all 4 high performance cores to be active as well as overclocking it back to its original speeds, you'll need to flash a custom kernel.
Click to expand...
Click to collapse
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk
Denhot said:
This is consistent with what I've noticed. The time It didn't, a simple reboot helped solve it and it hasn't occurred since.
Also these tools can't monitor the other cores, if you're rooted why not try synapse as helkat suggested
Sent from my iPad using Tapatalk[/QUOTE
Thanks man!
I know how the S810 should work!
But I thought the performance issues have only to do with the temps. But now it seems it have also to do with the battery level.
It would be good if someone tries to reproduce the following to verify it:
1. One run Antutu benchmark with fully charged battery and room cool temps.
To be sure the conditions are the same, shut the display off for one or two minutes, than start display again, kill all recent apps and run Antutu test and note the results.
2. Than wait or do something until your battery is down to 20%, shut the display off for the same time, kill recent apps and start Antutu test run again and compare the results.
I've also tried the same after a reboot, with always the same results.
With 100% I get scores between 60 and 66k and with lower capacity (20%) I get only 48 till 50k!
I am not interested about the benchmark results, but I need to know if this only occurs on my side.
Click to expand...
Click to collapse
So, guys!
I have tested it the last few weeks and it is a fact that the performance in benchmarks is dependent by the battery level.
We have tested it with 3 devices and it is always the same.
But thank God, it seems on the devices perfomance themselves (in apps/ui) this has no effect!
But each one can replicate this behavior very easy!
ollimi1 said:
Hi Jemcik, hi Denhot!
I'm facing the same issues on my new device and it's definately not normal!
With a battery level of 19% I was not able to get the 4 A57 cores online, which results in lower system performance. Have you found a solution?
@Denhot!
Maybe we should rename the thread into: IS OPT PERFORMANCE REALLY DEPENDENT ON BATTERY STATUS AND IS IT A ROM FEATURE OR AN ISSUE!?
I think, one of the kernel devs should be able to answer this question.
Click to expand...
Click to collapse
I have the same issue! When battery level goes lower than 20%, my A57 kernels become offline. I checked this with CPU-Z and PerfMon. And this is the same on stock or custom kernel. Now I am using Boeffla kernel. The most frustrating is that my UI suffer from this. I have lot of lags in simple apps, such as calculator or some messengers.
Same issue here, there are threads in one plus forums.
I think the threashold level is at 40 % ?? They made this to keep the battery up. You can also see faster battery drop till the 40-30% mark then it is harder to kill the battery.
I am also dissapointed in this, maybe we can search the kernel sources ? Or is there a daemon app that triggers this?
I received the phone with 20%-30% battery, started an antutu knowing how powerfull 810 chip is, then boom 45k same as the previos phone i had with 801 chipset...i was like what the fxck....runing antutu again with full battery - 66k.
well i have run benchmark in back ground with few game and apps .. and checked with cpuz max that i have notice was around 50-60% cpu load still 2 off those a57 cores were off using this device for 2-3 days it always turns off 2 cores for me rest 6 is working most of the time :/ Even in battery saver mode .. i am not sure if this is a cpuz issue as i have not rooted my device yet so cant say properly ..
Also i face some freq. benchmark issue like in benchmark it scores around single core - 690 multicore - 2.6K .. and if i restarts device it scores normal - 1.1K and 4.5K .. i have no idea whats wrong with this :/
20% Battery Mark
The drop in performance at 20% Battery is standard behavior of the Rom and Stock Kernel. The Big Cluster (A57) is completly shut down to save Battery. If you dont want this you have to use a custom Kernel which is able to switch this Battery saving strategy off. Boeffla Kernel for example can do that.
Read http://www.anandtech.com/show/9828/the-oneplus-2-review/2.
They "optimized" the soc.....
No they just turned off some cores so there is no heat problem.
So I think this is my first and latest oneplus.
they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|
Killer2k8 said:
they've hit the mark! What the hell, i think they must be sued for false marketing. Its just like buying a car with 400 hp and those hp are only there when i'm parked or listen to music, if i'm on the highway or on the ridge the car has 100 hp...wtf :|
Click to expand...
Click to collapse
Calm down lol it's actually good on their part. Shutting down A57 cores on low battery is a good thing because the A53 cores use much lesser battery. If you're out on a trip and have 10% battery, with the A57 cores this will probably drain off within an hour of intermittent usage. When only the A53 cores are active, the battery life will increase greatly.
Companies design phones for average users, not just gamers. If you don't want this feature, root your phone, flash boeffla's kernel and disable the BCL Battery Driver. It's as simple as that
Phone: VS995 Rooted running WETA rom + Werewolf Kernel.
Issue: Phone heavy CPU throttling when charging, gaming or even just booting. The CPU throttles to 652mhz on the small cluster and 1036mhz on the big cluster whenever I do something cpu intensive for a couple minutes. Obviously this causes a lot of stuttering and lag. I have to let it sit untouched and it will go back to normal.
I've monitored the temps and CPU doesn't go above 50c when playing games and my battery temp is below 25c. Even if the cpu temps go back down to 35c, it takes a while for the frequencies to ramp back up to max.
I'm using EX kernal manager and have disabled core_control and msm_thermal but doesn't help.
I've tried the stock WETA kernel and Werewolf kernel but they both don't seem to affect the heavy throttling at all.
Wondering if there is a kernel or a fix for this, kinda like the lg g3 thermal mitigation setting, or the CTTMOD found on other devices? Or maybe my device needs to replace thermal paste?
Thanks!
Holyman007 said:
Phone: VS995 Rooted running WETA rom + Werewolf Kernel.
Issue: Phone heavy CPU throttling when charging, gaming or even just booting. The CPU throttles to 652mhz on the small cluster and 1036mhz on the big cluster whenever I do something cpu intensive for a couple minutes. Obviously this causes a lot of stuttering and lag. I have to let it sit untouched and it will go back to normal.
I've monitored the temps and CPU doesn't go above 50c when playing games and my battery temp is below 25c. Even if the cpu temps go back down to 35c, it takes a while for the frequencies to ramp back up to max.
I'm using EX kernal manager and have disabled core_control and msm_thermal but doesn't help.
I've tried the stock WETA kernel and Werewolf kernel but they both don't seem to affect the heavy throttling at all.
Wondering if there is a kernel or a fix for this, kinda like the lg g3 thermal mitigation setting, or the CTTMOD found on other devices? Or maybe my device needs to replace thermal paste?
Thanks!
Click to expand...
Click to collapse
I've noticed this as well on WETA but only when charging. For some reason on WETA on stock kernel this phone slows down dramatically when plugged in. I just thought it was LGs method of thermal control but on MEGAROM V4 it doesn't slow down at all for me when plugged in so idk but would like to know how to fix cause I have it plugged in during driving a lot and switching back and forth between music and navigation becomes frustrating because of how laggy it gets
KUSOsan said:
I've noticed this as well on WETA but only when charging. For some reason on WETA on stock kernel this phone slows down dramatically when plugged in. I just thought it was LGs method of thermal control but on MEGAROM V4 it doesn't slow down at all for me when plugged in so idk but would like to know how to fix cause I have it plugged in during driving a lot and switching back and forth between music and navigation becomes frustrating because of how laggy it gets
Click to expand...
Click to collapse
Yes! That's exactly what I'm experiencing too.
Having it plugged in throttles the cpu immediately. Doesn't matter if it's a quick charger or a slow charger. The battery and CPU temps are both low so that's not an issue. Even when it reaches 100% battery and just trickle charging, it still throttles randomly.
I'll start a different rom and see if it helps.
Holyman007 said:
Yes! That's exactly what I'm experiencing too.
Having it plugged in throttles the cpu immediately. Doesn't matter if it's a quick charger or a slow charger. The battery and CPU temps are both low so that's not an issue. Even when it reaches 100% battery and just trickle charging, it still throttles randomly.
I'll start a different rom and see if it helps.
Click to expand...
Click to collapse
Yeah I recommend MEGAROM V4 although I'm on the T-Mobile H918 variant and not sure if there are any discrepancies to be accounted for but give it a shot and see
Having the same issue
My phone always stay Cool even when charging but cpu frequencies keep changing.
Even when i set the cpu max to 2105mhz it automatically slow down to 1036mhz , which makes the device super laggy and shuttering.
I've tried stock rom,weta,and some other roms and also tried some kernels nothing seems to be fixing the issue but Resurrection remix rom fixed it, no frequencies changing no lag no shuttering but i also has a problem that second screen doesn't work at all :/
yep same issues stock here.. just made a topic and realized you made this lol. stock rooted fwiw. I can't stand it. this phone has become such a lag fest that the galaxy s6 I was given for work seems faster, and that's two years old.
Sent from my LG-US996 using Tapatalk
maxi65 said:
My phone always stay Cool even when charging but cpu frequencies keep changing.
Even when i set the cpu max to 2105mhz it automatically slow down to 1036mhz , which makes the device super laggy and shuttering.
I've tried stock rom,weta,and some other roms and also tried some kernels nothing seems to be fixing the issue but Resurrection remix rom fixed it, no frequencies changing no lag no shuttering but i also has a problem that second screen doesn't work at all :/
Click to expand...
Click to collapse
jayochs said:
yep same issues stock here.. just made a topic and realized you made this lol. stock rooted fwiw. I can't stand it. this phone has become such a lag fest that the galaxy s6 I was given for work seems faster, and that's two years old.
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
I think I found a fix!
Here's a link to my thread: https://forum.xda-developers.com/v20/themes/mod-fix-cpu-throttling-charging-gaming-t3650705