I (and several friends that I asked) noticed a mark increase in UI response (laginess) when coming out of sleep, opening app drawers, initializing the keyboards, scrolling between launcher screens, etc. Having random lags is annoying, but having 2-3 second lag spikes when using the keyboard is downright frustrating.
I know that lab benchmarks are way up with the new release, but frankly I don't care about those if my day-to-day functions suffer.
I first began to notice this when I made the stock upgrade to Froyo. 2 days ago, I flashed the EViO 1.5 ROM on my phone, and it seems to be 4x as bad. Paring down the window launcher helps marginally. ADW -> Sense -> Launcher Pro in order of most to least lag. I am currently using Launcher Pro just because it's responding a little better than the others.
In a somewhat related post, one of the developers offers that a lot of lag is due to aggressive garbage collection:
(unfortunately, I am not yet verified so I can't post the link)
I also wonder if the overhead from the JIT compiler or lack of proper memory caching isn't the culprit ... or perhaps this is to what the aggressive garbage collecting is referring.
Who else has noticed this? Can anyone offer up an explanation?
I would be willing to reflash to a new ROM if someone can suggest a custom ROM that they recommend as having faster normal UI response time.
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
DirtyShroomz said:
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
Click to expand...
Click to collapse
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
None of these issues using Myn's 2.2 rls3 Rom and ziggys 11/5 kernel. I DON'T use setcpu. It can cause instability issues. Like the lag time in wake up. Some phones don't like 245mhz when sleep. Try boosting to 384 screen off. Also, overclocking can be beneficial but clocking too high can cause poor responsiveness. It can also affect benchmarking scores negatively if clocked to high. Try ziggys 11/5 kernel, its doesn't support overclocking, but it honestly feels like it is overclocked using this Rom/kernel combo
Sent from my DAMN Evo!!
lag what lag ? my 6.1 is lag free
moodebony said:
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
Click to expand...
Click to collapse
If your setcpu governer is set on something like conservative, it can defintely cause intermittant lag. get away from setcpu and use a havs kernel.
Currently mine is instant, no lag at all, but I had this problem about a week ago. I am running Fresh 3.4.0.1 with Netarchy's 4.2.1 cfs/havs kernel.
What caused my problem with lag was a lack of internal memory. I was down to about 64 MB of internal memory left and it would lag on wake or when exiting apps, and I noticed that it would often have to reload the UI whenever I exited an app. The fix was easy. I moved what apps I could to the SD card and used titanium Backup to remove a bunch of stuff that I do not use. Once available internal memory was over about 100 MB (134 MB is what it was when I was finished) the lag totally went away.
Problem Partially Solved!
SetCPU was indeed the main culprit. I was under the impression that overclocking too much would just cause instability. It seems that moving the ceiling from 1228.8mhz down to 1113.6mhz solved most of my new lag issues with the EViO ROM.
Indeed, upping the screen-off throttle-down from 245 to 386 also seems to have helped the wake-up lag time, though I'm still doing some more testing on this one.
Would I need to set all floor values up to 386 as well, or is that just for the screen off value? What scaling setting do you guys in setCPU? Conservative? Performance? On-Demand? Does anyone happen to know exactly what the differences are in the algorithms that they use?
So can anyone offer up an explanation as to why overclocking would result in lag? Is there some kind of hardware throttle-down that's happening? I had a catch for if the battery got too hot that would throttle back to normal speed, but I never seemed to reach it. Is there a known heat limit where the hardware automatically throttles down?
As for the seemingly normal, random Froyo lag spikes, I'll be monitoring that over the next few days.
Thanks again in advance for any information.
I've been having a recurring problem where my phone will lock up in a deep sleep, leaving the phone completely off. In order to restart the phone, I have to hold Power and Vol Down which takes me to a charging logo, and then hit power again. This generally happens overnight when the phone is charging, but I've also had it happen once while making a VoIP call. I thought I resolved the issue by wiping the phone and flashing the stock 4.2 ROM. However, the issue just occurred last night after 4 days of bug-free usage.
My question is whether this is some sort of weird software bug or a hardware issue. I haven't seen others report identical behavior but I've seen lots of complaints about freezing and random reboots that seem to be due to software. Should I request an RMA?
+ 1 . I am having the same issue. I would say hang tight. Call the support team and let them know you are having issues. If atfer a few weeks the problem persists perhaps go through an rma. I suspect it is software related. Lets say you did RMA still had the issue then had a dead pixel or other problem? It would suck and you would have to go through the whole process again. rinse and repeat. Only if you want to return the device for a full refund, then I would say hurry up and make that call. My .02 Good luck.
NexUsandThem said:
+ 1 . I am having the same issue.
Click to expand...
Click to collapse
+1
Having the same issue. Although no clear pattern is visible. Sometimes I find the phone dead-locked after putting it aside for 10 minutes and sometimes it seems to run for a day or even two without issue. Running _motley kernel right now without any change on this front.
I rather think it's a software issue than hardware. So I am not going to RMA it.
Strangely when I power off the phone on such a lock-up and then reboot it I will see a substantial drop in battery after the reboot. So the phone seems to be in some state where it still drawns more battery than in normal operation. E.g. with _motley kernel and limited clocks I typically see 3-5% battery drop over night only. When it locks up during the night and I reset it in the morning then battery usually drops much more (e.g. 30-50% is gone). Maybe it's caused by some hanging/deadlocked driver.
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
shotta35 said:
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
Click to expand...
Click to collapse
In fact I got the device in dec 2012. Started to set it up and then decided to root it (including full factory reset). I only have a very minor amount of system-level applications installed. Actually the main reason to root was to use Voltage Control as I intended to limit clock rates and (if possible) voltages the same way I was used to do it on my Galaxy Tab 7 (P1000) where I was very pleased with 6-days battery lifetime.
Initially I found the minimum clock rate was set to 1GHz and I have reduced it to 304MHz (minimum with stock kernel). When I discovered first freezes/lock-ups then I reverted to default settings and found it still locking up occasionally. Meanwhile I am using _motley kernel which seems to include some voltage mod as well. Although Voltage Control does not show options to modify voltages. Then I found Trickster MOD which shows some voltage control but it seems to have no effect (at least I was used my galaxy tab to crash when undervolting too much and it's pretty "strange" to be able to set all clock voltages to 0.6V while still running stable; so I guess the settings won't have any effect right now).
I have also tried to remove all modifications and applications and/or profiles which could cause the issue without any difference. Even when run stock settings it occasionally completely locks-up the device.
Edit: I was wrong regarding voltages. In fact I found my device happily works at 1134MHz using 600mV. Since I am used to limit max clock rates to 810MHz I could simply put all voltages to 600mV without seeing a crash/reboot.
CAUTION: This does not necessarily have to apply to all devices. My one is "faster" binned Rev. 11 device. Some voltages of different users are collected here: https://docs.google.com/spreadsheet/ccc?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc#gid=0
Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!
So, as the title says, there may be a way to prevent your device from freezing due to unlocked bootloader. Here are 2 things I've discovered:
1) Most of you may already know of this: If you switch off cores 3 and 4 of your CPU in the app Kernel Adiutor you can prevent the freezing issue. However, you lose half your CPU power, and if you leave it that way for long you can't switch those cores back on for some reason, and you'll have to reboot your device(else your battery will drain out if left as is, from my experience), so it's quite a cumbersome task.
2) If you play games that require little more than average ram and CPU power(even games like hill climb) your phone won't freeze while playing. I play this game called Vainglory, and after having played for over 10 hours, I can say for sure it didn't freeze even once.
From these two things I can draw up a vague conclusion that the phone freezes when the CPU isn't doing anything much. When we switch off 2 cores, the workload increases on the CPU, this making it busy(which also leads to quick drain). Same goes for gaming.
So how do we work on that? I'm not sure. Anyone have any ideas? Maybe someone can create a kernel compatible with RR and other cm13 roms which has what's needed. Or maybe try a different CPU governor? Well, just wanted to put it out there.
I tried all what you're trying to do and I understand that. The thing is that it will freeze no matter what.
Of course you can try but don't expect too much.
Goodluck!
I am facing this same issue suddenly
there is no connection between ifwi and cpu core
paktepu said:
there is no connection between ifwi and cpu core
Click to expand...
Click to collapse
Who said there is?
Another thing I found:
When you use kernel adiutor to switch off cores 3 and 4, and use your phone normally, the instant when your phone would have frozen if it weren't for the app, is when your phone gets much slower suddenly. At this point, you'll no longer be able to switch those cores back on, and only a reboot will resolve that.
I've mentioned this so-called "method" of preventing Z5 freeze long ago. I can confirm that switching off cores 3 and 4 somehow halts the phone's urge to freeze. I could've lived with limiting my "power use" as I'm not really a fan of entrusting your phone with large tasks. However, what turned me off was that disabling either one of cores 3 and 4 also disables the camera somehow (Ring a bell, Z5 users who lose their cameras whenever their bootloaders are unlocked?)
No one really replied with certainty back then and up to now, that thread is still collecting cobwebs.
Question: is battery drain a characteristic of disabling cores? I disabled only core 4. Cores 1, 2, and 3 are up and my ROM (Lineage 14.1) runs perfectly without freezing.