Develop Bugs

[HOWTO] Detecting the LP Core + Disabling the other 4 (maybe)!

Nothing in this post should be considered gospel; These are simply conclusions I've drawn from testing. Everything written here could be (and probably is) very, very wrong!
Click to expand...
Click to collapse
YOU MUST BE ROOTED TO ATTEMPT ANYTHING IN THIS THREAD
I don't take full credit for this, someone posted information about the file I listen to but I can't for the life of me find the post. If someone locates it let me know so I can give credit where it's due!
Detecting the Companion Core
The 5th Core (Companion Core/Low Power - LP - Core) is invisible to the android system and cannot be controlled at the moment. However, the kernel can see the 5th core and can detect whether it's running or not.
This is a simple demonstration of this, nothing particularly interesting or useful yet!
Results with screen ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Results with screen OFF
So yeah, this is why we get such great screen-off battery life!
I know pretty much everything written here is already known I just thought it would be nice to see some proof!
For those of you that want to try this out yourself, make a service that runs in the background that reads from: "/sys/kernel/cluster/active". It will be either "G" or "LP" (G meaning it's running from the normal cores, LP is the Low Power core.)
Interestingly, while the screen is on but nothing much is happening on the device it will constantly switch between G and LP (like in the first screenshot) but when doing CPU intensive tasks it runs as G constantly. When the screen is off, it never switches to G which is giving us the insane screen-off battery life.
Disabling 4 Cores and just running the LP Core!
NOTE: This may not be the case. The phone kinda gets a bit screwy and reports different things. I'm pretty sure this is just the throttle that happens when the CPU hits 90°c but I'm not sure (it's hard to make it hit 90°c!). If anyone knows what else it does please let me know!
WARNING: This can, and most probably will, crash your phone after a while. When running CM9 I even had to reflash the ROM (This hasn't happened on Android Revolution yet). Basically PLEASE make a backup and don't blame me if you mess anything up!
This is a strange one. If you navigate to "/sys/kernel/debug/cpu-tegra" there's a file called 'Throttling'. Changing this file to '1' makes the system throttle CPU usage drastically.
Interestingly though, it also makes the "sys/kernel/cluster/active" file report nothing but 'LP' even when doing tasks, indicating that it's running solely off the LP Core. However, I'm using TegraStats to monitor what's active and what isn't and when throttling is enabled it reports that 'cpu0' is also active, contrary to what the "sys/kernel/cluster/active" file says.
If you apply this mod you will instantly see why I think it's running soley off the LP Core: It makes the phone almost unusable and I wouldn't recommend doing it for any great length of time!
Another wierd thing is that TegraStats also reports that CPU1 activates at random points while the phone stays as slow as ever.
Of course, CPU1 could indeed be active and just throttled to a low clock speed (102mhz is pretty much the average when doing anything. It can go as high as 304 though) but it still doesn't explain the LP Core results.
So, if this is running off only the companion core, what does it mean? Well, you could ultimately gain massive battery improvements. The only problem is, the mod renders the phone unusable as it stands. The throttle would probably need to be modified from kernel source to not be quite as aggressive or something, so not useful at the moment but it has potential
I hope you found this interesting!

Reserved for future info!

Nothing to add, sorry, but very cool.

how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him

kragnegrozor said:
how to disable lp core.
i need to disable it completly. it has ****ty performance
or maybe you know how to change governor on that core or something with him
Click to expand...
Click to collapse
it's not good to disable the core because after that you wont have good standy battery life.....and what do you mean with it has bad performance?

man, newest update in youtube APP uses only 1 core, and this core is this sh****ty fifth one. in 720p films there are stuttering and other sh** sometimes. If you demand something powerful from phone at this time, other 4 cores are ON and video is playing smoothly.

Lolwut? The companion core should only be used once your screen is off or goes into deep sleep. Not for the main system to use or for playing YouTube videos.
Sent from my HTC One X using Tapatalk 2

Well done on bumping a 7 month old thread that obviously isn't relevant any more, guys...

so can somebody tell me how to disable it or change governor? it is for research

kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
Try System Tuner or any similar app.

kragnegrozor said:
so can somebody tell me how to disable it or change governor? it is for research
Click to expand...
Click to collapse
neuTrue said:
Try System Tuner or any similar app.
Click to expand...
Click to collapse
no app can disable it until a kernel dev can something do for it ...also nothing else can disable it ...try to search for example for youtube a fix that it will work better ...because the 5th core doesn't work in youtube or other ...youtube is stuttering because of other things not the 5th core

Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.

XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
No it doesn't.
Sent from my HTC One X using Tapatalk 2

Learn about the topology of tegra3 unit. Different core technology, Different performance.
Wysyłane z mojego HTC One X za pomocą Tapatalk 2

XxVcVxX said:
Do people know that the lp core has the exact same performance as the other cores?
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so

One-X-master said:
it has only 500 mhz and it will be used for apps which wont take much or if the screen is off/deep sleep...it wont be used in apps like youtube and other ...
like messaging/sms app or e-mail or so
Click to expand...
Click to collapse
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.

XxVcVxX said:
It has the exact same performance.
It's still ARM Cortex A9, only manufactured with low power silicon. It doesn't scale well into high clock speeds so thus its limited to 500 MHz, but it still has the same performance at same frequency.
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
yes but it it isn't working while apps like youtube I have no problems when i use youtube he also had to write which kernel he use because some of the custom kernels or the stock don't know what it was have problems in some apps also figuered that out i had also with a kernel problems in youtube in other no problems...but don't know which because i don't have the phone here because of the f*cking repair center...

i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology

kragnegrozor said:
i am using kernels
,doing some research about performance.
Just some observations for now
i am need to know how to disable it.
Got some knowledge from many other phones\kernels\roms
But here is tegra3 topology
Click to expand...
Click to collapse
you know that EVERY android build has kernels because without they can't work? i meant with stock kernel that's the kernel in the stock RUU/ rom and custom kernels were edited by devs like faux etc...you CAN'T disable it try to ask a kernel dev you can see them in original development thread but like i know it's impossible because the 5th is for android unvisible ^^

i am gonna think about that.
i am seen somewhere OCed 5th core. Gonna find where and ask in that kernel thread.
thanks

Insane battery life and throttling the Companion Core (I think).

This doesn't represent real-world use. This is an extreme example of how long you can make the battery last by severely throttling the CPU!
I posted another thread about the method used to apply this mod (you can find it here) but I made this thread to concentrate purely on the side effect of it, which is insanely good battery life. Firstly, I'd just like to make this point clear: I would not recommend doing this mod. It makes your device get pretty screwy and renders it fairly unusable. It needs further development before it can be useful.
Yes, this mod gives you absolutely incredible battery life but it only does so by severely limiting the CPU speed and limiting the CPU to a single core (It might even just run off the companion core and nothing else. I've had conflicting results) which makes the phone insanely laggy. I believe, however, that this throttling could be made less aggressive and then toggled on and off at will. From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life (which is already pretty amazing). This isn't definite though and needs more tests
Anyway, less chit-chat, here are my results:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's right, 12 hours and 35 minutes screen-on time!
It would probably last about 4 or 5 days if the screen was off!
ROM: Android Revolution HD
Kernel: stock ARHD kernel
Screen on lowest brightness
No other modifications (apart from the throttling mod)

"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone

SartoriXX said:
"It makes your device get pretty screwy and renders it fairly unusable."
Ok then, i'll just charge when the battery gets low then and use it as a great phone
Click to expand...
Click to collapse

If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS

Might aswell do that!

I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.

Meltus said:
I'll repeat what I bolded in the first post:
From my tests it seems this also throttles the Companion Core, so you could even use this mod as-is to get better screen-off battery life
Is this really not something people are interested in
This could potentially double the battery life if we could modify how aggressive the throttling is. We can already toggle it on/off on the fly.
Click to expand...
Click to collapse
I think it sounds awesome and happy to see people like you try to developing the power consumption!
Sent from my HTC One X using Tapatalk 2

sure beats my battery life with only 30 minutes screen on time

ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse

ben_pyett said:
If I power off my device, then I find that they battery will last for several days, maybe more
Swyped from my DesireS
Click to expand...
Click to collapse
Comments like that are a complete waste, if they are on to something you should be more encouraging.

Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get

I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.

lamenramen said:
I wholeheartedly endorse your explorations. Find a way to salvage this phone; battery life currently makes the international version borderline unusable.
Click to expand...
Click to collapse
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA

Meltus said:
Done a bit more testing and it turns out that it does indeed throttle the LPCore, but not by much.
I've hit another odd contradiction though; I'm polling "sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq" to get the current frequency but even when the screen is off that file still reports that it's active. Does this mean that at least one core is always active alongside the LPCore or does the CPU0 display the LPCore's frequency when the rest are disabled? If CPU0 does indeed show the LPCore frequency when the screen is off then doesn't that mean that Android CAN see the companion core?
In any case, the CPU0 file reports frequencies between 51Mhz and 475Mhz (51mhz being the frequency it hits about 80% of the time) and with the throttling enabled it seems to be locked to between 51Mhz and 102Mhz (with it hitting 51Mhz about the same percentage).
So it does seem to limit the LPCore (or whatever core is running) but it also seems that it's pretty much as optimised as it's going to get. Throttling does seem like it would increase screen-off time, but by how much I have no idea.
I'll test it overnight and see what kind of battery life I get
Click to expand...
Click to collapse
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium

Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.

punyategar said:
Does throttling the compnion core means you're just using 1 core in a quad core device?
Maybe its wiser to not get a quad core alltheway.
Click to expand...
Click to collapse
The hox has 5 cores, 4 main cores and 1 super low power core.
What this does is turn off the main cores and run on the super low power core which is great for battery life but it only goes to 500 MHz and in respect to CPUs is slower at processing stuff then almost all CPUs price you pay for power saving.
Sent from my HTC One X using xda premium

Applaud your investigations, so many Haters on this forum!
This phone has masses of potential for some awesome custom Roms (and even a decent official Rom if HTC ever sort themselves out!). Battery life pretty much whole day for me but improvements always welcome.

xchasa said:
Huh? Borderline unusable? If you're serious then exchange your faulty phone. I'm getting 16 odd hours with 4-5 hrs screen time.
I agree about the explorations through mate.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
He is probably talking screen-on time. 4-5 Hours screentime is great, unfortunately you do not fall under the average hours of screen-on time. The average time would be anywhere between 2 and a half to 3 and a half hours.
Which in my opinion is nothing special, admittedly, it does get me through a day but hey! I wouldn't mind having more screen-on time. If 4-5 hours screen on time was the average than you wouldn't see many if anyone complaining at all.
Good day!

treebill said:
Android sees all cores as equal meaning it would assumes the lpcore is a ~1.5 core, so to get around this nvidia have made it transparent to android and the kerenel / low level drivers switch between the main and the lpcore but both show to android as the same CPU or as you've found shown as core 0. If it didn't do this when the main cores went off it wouldn't see a CPU at all.
Edit: as I can't post on your other topic from the app
I believe that file links to the throttle_table in the same folder, just did some tests
2 - limited too 1 core (i assume lp maybe a main core) 102 MHz
3 - 2 cores and 340 MHz
Then phone crashed so I went back to sleep lol I will do some more testing later.
Sent from my HTC One X using premium
Click to expand...
Click to collapse
Ah, that makes more sense
So, were you able to get the 'throttle' file to stick to anything but '1'?
I noticed the throttle_table and tried to use a few of them but they all just defaulted to 1.
It's a shame the 'throttle_table' file isn't editable too, that would make modifying it so much easier!
My first test failed miserably I'm afraid, I forgot to turn off an alarm and it rang out for about 3 hours and then ran out of battery! I'll remember to turn off the alarm next time

Bloody good effort. Despite the idiotic comments from those who clearly haven't grasped the idea behind this, it's impressive homework.
Research like this can only help improve custom-ROM's, which is kinda the point of XDA Dev's, no?
I think some people should focus on the comments section of sites like Engadget, where their funny pictures will be much better suited.

16 day battery life

Hi guys.
I am trying to find out what everything can be turned off keep basic phone functionality to reach battery life that this phone deserves with nearly 5000 mah battery.
Curently i downclocked gpu turned all cores except one core limited to 400 mhz (with free kernel auditor in store).
phone is bit lazy ( like old android phones but still usable for basic functionality like picking a call or responding to sms)
but every time i need reasonable work i enable 2 big cores. with just 2 taps and when done turn them off.
As for services i disabled pretty much everything and left only minimum 7 services running as seen on screenshots. also do not disable location services or phone will not boot. killing them after boot is enough it seems.
I enable google play services + play store + download manager just when i need to download/update some app and disable them afterwards
for fast enabling/disabling most used services i use free package disabler from store and keep them in his favorites. too bad his widgets dont work on my device. also it doesnt stop services after disabling so i stop them wih force stop helper.
in developer options i disabled background services and enabled gpu acceleration for 2d.
this is second time i am trying to reach 16 days and I am in the middle.
what would elevate battery life for a little bit longer is if I guess if I can lets say each 9min be on airplane mode with 1 min airplane off to catch missed calls sms.
i remember i did pulse airplane mode from cron with script and build in utils but i guess that would require cron running in background whole time which i dont like.
Is it possible to launch timed events based on hw timer without having an app running?
I love cpu tuner that has exactly that airplane pulsing but each time it pulses it crashes. if i only knew why.
Also is it possible to find out what service on folowing screenshots eaten how much cpu and why ?
thx guys. hopefully i will reach more than 16 days with your help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I just have one question... Why? This phone already has an amazing battery. Why kill functionality for a marginal increase in battery?

IndDoc said:
I just have one question... Why? This phone already has an amazing battery. Why kill functionality for a marginal increase in battery?
Click to expand...
Click to collapse
I am not sure I would call2 days fantastic battery life. Also I dont think I sacrificed that many functionality. If i need camera i enable it in one tap i need play store i enable it etc.
Now is this litle incovenience worth aditional 13 days for me definitely yes.
also how come phone lasts 2 days before and 16 days after ? this is definitely waste and governors are not equal to core shutdowns i guess
After some time when i will reach maximum . lets say 20 days ?
Only then I will start reenabling minimum common sense features like pulse wifi and email at specific intervals.
In the end when I will have more clear idea what services are draining battery unnecessarily I will try to code something that pulses wifi plus disables cores/services when screen is off.

neurall said:
I am not sure I would call2 days fantastic battery life. Also I dont think I sacrificed that many functionality. If i need camera i enable it in one tap i need play store i enable it etc.
Now is this litle incovenience worth aditional 13 days for me definitely yes.
also how come phone lasts 2 days before and 16 days after ? this is definitely waste and governors are not equal to core shutdowns i guess
After some time when i will reach maximum . lets say 20 days ?
Only then I will start reenabling minimum common sense features like pulse wifi and email at specific intervals.
In the end when I will have more clear idea what services are draining battery unnecessarily I will try to code something that pulses wifi plus disables cores/services when screen is off.
Click to expand...
Click to collapse
I don't understand you, what’s the problem by charging it every 2 days and no need to limit it.I prefer it fast and no missing any call or sms,I've just frezzed some apps that I use rarely and others to stay active in background.
Enviado desde mi MI MAX mediante Tapatalk

IndDoc said:
I just have one question... Why? This phone already has an amazing battery. Why kill functionality for a marginal increase in battery?
Click to expand...
Click to collapse
Albertkuba said:
I don't understand you, what’s the problem by charging it every 2 days and no need to limit it.I prefer it fast and no missing any call or sms,I've just frezzed some apps that I use rarely and others to stay active in background.
Click to expand...
Click to collapse
-1
The OP clearly has a project where he wants to maximize every joule of energy available to him - which is a very noble endeavor. We live in societies which are all too happy to waste the resources available to them - the case in point here is that we have two posters quoted above who think that wasting energy is somehow acceptable - and charging up the device more than necessary is perfectly fine.
Whatever the reason the OP has decided to pursue this endeavor, it is in the spirit of XDA that we encourage and help, if we can. It is not for us to batter the aspirations of another member, purely because we don't understand the motives of their pursuit. This is a community and the only way it will thrive is if we encourage the curiosity and passion that has driven us so far.

panyan said:
-1
The OP clearly has a project where he wants to maximize every joule of energy available to him - which is a very noble endeavor. We live in societies which are all too happy to waste the resources available to them - the case in point here is that we have two posters quoted above who think that wasting energy is somehow acceptable - and charging up the device more than necessary is perfectly fine.
Whatever the reason the OP has decided to pursue this endeavor, it is in the spirit of XDA that we encourage and help, if we can. It is not for us to batter the aspirations of another member, purely because we don't understand the motives of their pursuit. This is a community and the only way it will thrive is if we encourage the curiosity and passion that has driven us so far.
Click to expand...
Click to collapse
You may be right but from my point of view what for I need a movil phone if I can't receive a call or a sms at the moment?By removing the Sim, without using any app and turning off data and wifi you can get too about a week without charging but then it has no sense.
Enviado desde mi MI MAX mediante Tapatalk

I think enabling 2 big cores is unnecessary for your purposes, just allow the small cores to clock up to 0.8-1ghz when you need work done. If your phone is 'lazy' with 1 core clocked @400mhz you're wasting screen on power whilst waiting for the 400mhz to do its thing.

Updates?

panyan said:
-1
The OP clearly has a project where he wants to maximize every joule of energy available to him - which is a very noble endeavor. We live in societies which are all too happy to waste the resources available to them - the case in point here is that we have two posters quoted above who think that wasting energy is somehow acceptable - and charging up the device more than necessary is perfectly fine.
Whatever the reason the OP has decided to pursue this endeavor, it is in the spirit of XDA that we encourage and help, if we can. It is not for us to batter the aspirations of another member, purely because we don't understand the motives of their pursuit. This is a community and the only way it will thrive is if we encourage the curiosity and passion that has driven us so far.
Click to expand...
Click to collapse
:laugh::good:
Thx panyan for warm support. I also think that xda is fantastic place for all kinds of tinkerers and experimenters. who knows where most modern software in mobile phones would be if we had not places to evolve like XDA, a lot of features that are now in android or ios were firsp created and popularized by comunity as mods first. or firmwares that would not exist for older phones otherwise.

facepainter said:
Updates?
Click to expand...
Click to collapse
You are right. Thats great idea hopefully governor will be as efficient as manual throttling. Will definitely try that.
not much progress thou ;( can't push past 16th day.
Biggest drain right now is phone idle. are you guys aware of way to have finer power usage log ? ie what exactly is eating that cpu ?
Or mayby broadband chip is thirsty when sihnal is weak.
mayby airplane on for 5 mins when signal is weak would help. but right now I have not idea where the power is sinking. I am allready on 2g so maybe some 2g parameters to tinker with ?

currently I am getting 20~24 days of stand by time with network on, wifi off, no data. although I use the phone only as a back up and rarely use it. So the insane standby is expected

Batterry drain by Android system and stand-by

Does anybody else noticed the huge amount of batterry drain that goes on all day long. I got this phone for about half a year and I think it's worse than before. I'm not the only one with this problem, most of my family got this phone as well and are having the same problem.
In the screenshots you can see how it drained. The screenshots were made after a day of work where I barely used my phone. It seems like it won't get in the Android sleep or Doze.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried several things as hard restting my device and I tried ForceDoze, but all of this didn't work. What can I do?

Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.

matmutant said:
Stock or custom ROM ?
I got mine yesterday, flashed LineageOS right then..
And I do find battery life extremely poor compared to my older Moto G first gen.
But this might not mean anything for your case though.
Click to expand...
Click to collapse
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.

Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
As I didn't try stock rom for more than 5 minutes, I have no idea if it is better or worse on Lineage...
Only thing I can say is that I am very disappointed with the battery life, I could get 2 days on my old G where I can only get half one on this device with similar usage...
When I bought it (rushed buy as my G died), I didn't figure that doubling the screen res and and the CPU cores will cut by more than half the battery life with a only 35% bigger battery.
for your specific problem you might try to recalibrate your battery (cf : here)

Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.

trotter2000 said:
Stock is not configured the best. It's running in performance mode and not running BigLittle configuration even tho we have slow cores and fast ones. Latest lineage has a BigLittle setup that will help a lot. Battery still not the best tho but way better for sure.
Click to expand...
Click to collapse
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )

matmutant said:
Are you sure msm8937 really supports big.LITTLE configuration? I can't find it anywhere :\
If I remember well (but I didn't follow SoC dev since msm8926), Qualcomm way of running CPUs was using MPdecision and such to shut down unneeded Cores and work on the minimum needed active cores, instead of having four or eight cores powered at anytime (and at blazing 900-1094MHz -_- )
Click to expand...
Click to collapse
Well it seems to be working OK. Kernel auditer is showing big.LITTLE. Updated 2 days ago self compiled lineageos. If you set powersave on big you get loads of deeps sleep on the cores. On stock there was never any deep sleep they was always running.

well, that's interesting,
I'll try to investigate a little [no pun intended] more, but at first sight, touching cpu0 freq affects the whole 4 core cluster (0 to 3)

Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos

TheFixItMan said:
Iv never had any problems with battery
As the screenshot shows - Iv been using my phone pretty much constantly the last 7 hours & Iv still got 7 hours left
So with constant Internet usage as well as spotify/pandora YouTube games etc I get at least 14 hours use out of this phone and normally longer - I only charge once a day
Iv always been using lineageos
Click to expand...
Click to collapse
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)

matmutant said:
could you please post a screenshot of cpuZ showing CPU freq when idle?
what I have here, and that looks quite strange to me :
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
960000 1094400 1209600 1248000 1344000 1401000
Code:
cedric:/ # cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_available_frequencies
768000 902400 998400 1094400
which looks to me that the High perf Cores are 0 to 3 and low power ones 4 to 7...
but 4 to 7 seem stuck at 1094400Hz and 0 to 3 are 960000Hz when idle
I would expect that the High perf cores should turn off when idle, and that the low power ones go down to 768000... which would save quite some juice... isn't it?
I'm using LineageOS 14.1 by @wzedlare (lineage-14.1-20171018-UNOFFICIAL-cedric.zip)
Click to expand...
Click to collapse
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency

Add screenshot
TheFixItMan said:
Here are some screenshots
The lowest frequency the kernel is set to run at is 960mhz
You would need a custom kernel to play with the scailing & min frequency
Click to expand...
Click to collapse
I understand that the big are good to go with 960MHz as long as they should be off most of the time when idle,
But why the LITTLE cores are at 1GHz wen they could be much lower clocked when nothing is going on xD
from what I can see, it is possible to shutdown one or more core(s) manually :
Code:
echo 0 > /sys/devices/system/cpu/cpu3/online
So I hope we can implement some hotplug driver to save some battery life.

Aaapiie said:
It's just stock ROM. I considered flashing lineage os just for the battery. What do you think, is the bsttery life time better with lineage os?
And yes I got the first gen Moto G as well which had much better battery life.
Click to expand...
Click to collapse
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems

matmutant said:
Could you please post a screenshot of cpuZ like I did?
I'd like to have an idea of the stock behavior
Sorry to hijack this thread BTW, but that might help more than it seems
Click to expand...
Click to collapse
No problem at all, thanks for your thoughts.
Here are some screenshots, hope this is what you are looking for (the cpu core values may vary).

At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...

matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive

Aaapiie said:
Sorry for the late response. But what do you mean? You mean the field in the bottom of cpuz? Cuz that is saying interactive
Click to expand...
Click to collapse
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor

matmutant said:
At least we can see the core 4 to 7 aren't locked at max freq as it is on lineageOS, what does kernel adiutor say about governor for big and LITTLE clusters ?
But this does not explain the sudden drop in battery life as you seem to have...
Click to expand...
Click to collapse
matmutant said:
cpuZ fails to detect the two different clusters and assumes core 1-7 are slave of core 0
If you are rooted, the app "Kernel Adiutor" can tell us more about this by looking at CPU menu, and governor for the LITTLE cluster
Or
Code:
cat /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
Click to expand...
Click to collapse
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery

Aaapiie said:
I don't have root access. If I'm right I can run that command using an terminal app like Termux? If so see the result in attachment.
Edit: I think I'll try out lineage os tommorow or on Wednesday and I'll see what happens for the battery
View attachment 4312018
Click to expand...
Click to collapse
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?

matmutant said:
At least the governor is properly configured for the 4-7 cluster on stock ROM (that's something that I was starting to doubt about...)
If you ever install LinageOS in the next days (but I hope it will be fixed before) you may need to force the governor of the cluster 4-7 by 'echoing' it to core 4 (of use Kernel Adiutor for that matter)
did you search for any service that could be running in the background all time?
Click to expand...
Click to collapse
No I cannot point a finger to a specific app. I've done serveral factory resets, but no success with a clean reset.

Phone getting slow

I have had my OP3 for 2 years. I have noticed the battery life is much shorter, overall burn-in on the screen (screen is getting dim even on max brightness), and the overall performance is much slower than it was even a year ago. Am I the only one experiencing this? Is OnePlus doing similar to Apple where the CPU is throttling as the battery degrades?
Edit:
Using latest beta build, but the same issues persist regardless of using stock, beta, or custom roms. I am also rooted, but notice the slow speeds even with a fresh ROM reinstall with everything stock.

No OnePlus can't do what Apple did, we would notice in a second. You should try new kernels or go with stock if you aren't using stock already. Try different ROMs if you want to confirm your hardware condition. Other than that the decreasing speed is normal, the device is getting older and it is getting tired.

I've tried multiple different roms and kernels. The issue is close to the same across all ROMs. Just now opened a twitter notification and it took several seconds to open rather than instantly like you'd expect.
Was just wondering if it is worth a try with one of the $25 batteries on Amazon. Will likely just start looking to upgrade.

Highly doubt you have burn-in. Almost doesn't happen these days anymore unless you abuse your phone. Regarding that your phone is slow. Did you try a full reset yet? Have you done any tweaks or something? My phone is hitting the 2 year mark with only a new battery and camera (common focus problem). And it is still like it was at day 1.

It definitely has image burn in. If I put a full screen white image on the phone, it is all off-white except the middle part of the notification bar, I can even see burn in for the static icons like wifi, battery, LTE, etc...
I have done a full reset just a month ago, but didn't help. Even when completely stock including recovery then tried with a few different kernels. still very slow compared to new.
You did say you have a new battery, considering my battery life is crap right now, I may just give that a try. OEM parts are pretty cheap on witrigs.

I would definitely recommend using bluspark kernel on oxygen os. If you enable the fastlane feature and set both of the cores to 35 it will be blazing fast and no lag what so ever. Try that and let us know how your phone reacts.

Puddi_Puddin said:
Highly doubt you have burn-in. Almost doesn't happen these days anymore unless you abuse your phone. Regarding that your phone is slow. Did you try a full reset yet? Have you done any tweaks or something? My phone is hitting the 2 year mark with only a new battery and camera (common focus problem). And it is still like it was at day 1.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrmcshagbag said:
I would definitely recommend using bluspark kernel on oxygen os. If you enable the fastlane feature and set both of the cores to 35 it will be blazing fast and no lag what so ever. Try that and let us know how your phone reacts.
Click to expand...
Click to collapse
I reset and reflashed OOS and installed bluspark. Also limited the apps I installed too. It seems to be a bit faster. Will report back if I get any slowing.

Still no issues. I was thinking and realized my issue. I had two separate profiles on my phone, a home profile and work profile. I assumed that the inactive profile automatically shutdown whenever switching like on a PC when you sign out of one account and into another. I am guessing this isn't the case with android. The inactive profile continued to run in the background causing my slowdown and battery drain issues.
Moving forward, multirom is probably the way to go for me if I decide to go back to having separate work and home work spaces.

daggorlad said:
It definitely has image burn in. If I put a full screen white image on the phone, it is all off-white except the middle part of the notification bar, I can even see burn in for the static icons like wifi, battery, LTE, etc... .
Click to expand...
Click to collapse
I have the same . In addition, I have a burn in screen at the bottom (strip about 1 cm ) . I've noticed keyboard image burn in as well . Never amoled again .

daggorlad said:
Still no issues. I was thinking and realized my issue. I had two separate profiles on my phone, a home profile and work profile. I assumed that the inactive profile automatically shutdown whenever switching like on a PC when you sign out of one account and into another. I am guessing this isn't the case with android. The inactive profile continued to run in the background causing my slowdown and battery drain issues.
Moving forward, multirom is probably the way to go for me if I decide to go back to having separate work and home work spaces.
Click to expand...
Click to collapse
Did you get fastlane enabled on both cpu clustors and set to 35?

mrmcshagbag said:
Did you get fastlane enabled on both cpu clustors and set to 35?
Click to expand...
Click to collapse
I didn't see a fastlane using Kernel Auditor. It has been so long since I have adjusted kernel level settings, I don't really remember a lot of it.
Edit: I just did some more searching and found the settings. I enabled and set to 35 on big and little governers. Thanks for the advice.

daggorlad said:
I didn't see a fastlane using Kernel Auditor. It has been so long since I have adjusted kernel level settings, I don't really remember a lot of it.
Edit: I just did some more searching and found the settings. I enabled and set to 35 on big and little governers. Thanks for the advice.
Click to expand...
Click to collapse
No problem let me know how your phones running with that enabled ?

daggorlad said:
I reset and reflashed OOS and installed bluspark. Also limited the apps I installed too. It seems to be a bit faster. Will report back if I get any slowing.
Click to expand...
Click to collapse
Do you life in a area with alot of sun? Still don't have burn in, sad to see that you do tho.

Also keep in mind that once android gets above 50% storage performance starts to degrade.

I have same issues. My op3 overheating and lagging alot while playing pubg. Any solution?

Noob02 said:
I have same issues. My op3 overheating and lagging alot while playing pubg. Any solution?
Click to expand...
Click to collapse
There really is nothing you will be able to do about that. Those kind of games are really just pushing mobile hardware in directions that it just wasnt designed to go. Until we get a real cooling system (20 years or so before they shrink the liquid cooling small enough maybe) Gaming like that will always cause the device to heat up alot and lag. Its the nature of the beast.

zelendel said:
There really is nothing you will be able to do about that. Those kind of games are really just pushing mobile hardware in directions that it just wasnt designed to go. Until we get a real cooling system (20 years or so before they shrink the liquid cooling small enough maybe) Gaming like that will always cause the device to heat up alot and lag. Its the nature of the beast.
Click to expand...
Click to collapse
So buying new phone is the best solution? I can't effort new phone now. So is there any kernel configuration or tweaks?

Noob02 said:
So buying new phone is the best solution? I can't effort new phone now. So is there any kernel configuration or tweaks?
Click to expand...
Click to collapse
No, Not even a new phone will really help. Besides the hardware in the 3 and 3t will still be able to handle anything Google tosses at it for a few more years yet. You hear it all over the place on every device. No device has a proper cooling setup for gaming of that nature. Even the S9 with Fortnite is getting hot after playing for a while.
This is a side effect of trying to game on something that was not made to game like that. Ill be honest. If you want to game like that save it for the PC until the hardware can support it. Other wise you will just have to deal with the heat and the lag.

zelendel said:
No, Not even a new phone will really help. Besides the hardware in the 3 and 3t will still be able to handle anything Google tosses at it for a few more years yet. You hear it all over the place on every device. No device has a proper cooling setup for gaming of that nature. Even the S9 with Fortnite is getting hot after playing for a while.
This is a side effect of trying to game on something that was not made to game like that. Ill be honest. If you want to game like that save it for the PC until the hardware can support it. Other wise you will just have to deal with the heat and the lag.
Click to expand...
Click to collapse
I see. Thanks bro