Related
So, I sent back my dead S2 to Samsung for repair. They stated that they changed the motherboard. Now, I find that my battery drains much slower and the CPU seems to run cooler. The back doesn't feel as hot anymore. I'm wondering if there's any apps that can help to identify the CPU?
Strange my phone doesn't get hot, battery doesn't drain fast,
Maybe because I'm not on some custom ROM, kernel with issues..... Lol.
System Tuner Pro gives you various details about the CPU under 'tweaks' like:- cpu implementer, cpu architecture, cpu variant, cpu part, cpu revision, hardware/revision & serial number but these values are in hex so you'd need to find a source for what these values correspond to.
I noticed that all kernels I tried are with kernel_max set to 1 making the second CPU core disabled. If you go to /sys/devices/system/cpu and do a cat online it will appear 0, doing a cat offline will show 1 indicating that cpu 1 is disabled and if you do a cat /proc/cpuinfo it will show informations only for cpu0. If it's a dual core phone, why to put the second cpu offline?
I stumbled into the "cpu1" issue in proc yesterday while doing some comparisons between my S2 and my S3. My S3 has its original ROM (heck, I only just got it yesterday...) and cpuinfo e.g. shows me only cpus 0,2 and 3. /proc/cpuinfo of my S2 shows me only cpu0. To me it looks like as if /proc/cpuinfo ignores existing cpu1. (/proc might be depricated, but then why is it still there on ICS 4.0.3/4 ?)
/sys/devices/system/cpu/online on the other hand will ALWAYS show the correct amount of online cpu's. In my case on S2 (litening ROM/ litepro kernel) the output of /sys/devices/system/cpu/online is 0-1, on my unflashed S3 0-3.
My tip. Reboot your smartphone and look then at /sys/devices/system/cpu/online. I have the impression that either some app, the kernel itself or a bug turns a core off at somepoint. It happened to me yesterday (S2) which is what brought me into the search in the first place. I was having issues with my dialer/contacts freezing when trying to call. Something that should never ever happen (It's still a phone god damn it!! Imagine you need to do an emergency call and have to reboot the thing first!)
The core isn't permanently disabled, it's only disabled at that time to conserve battery performing an operation that only requires one core. Depending on the hotplug settings the phone with use core 1 when it needs to, which naturally the people who create kernels try to keep to a minimum to conserve battery. There are very few situations at this time that honestly require 2 cores. 1000 Mhz on 1 core can handle 99.9% of tasks.
Since i got my GSIII i've been tweaking and experimenting with the best setup to give myself a nice experience without draining the hell out of the battery (especially now that my battery is an aged piece of s**t that won't last more than 6 hours, maybe because of my own actions )
I've gone through many different ROMS, official test builds, kernel configurations, etc... but a thing that has ALWAYS caught my eye is the fact that every single CPU tweaking mod i've ever used only lists 3 cores on the device
I should point out that i own an international SIII (GT-I9300), which comes with the Exynos 4412, it's not the best, but it does it's job pretty well, even with the default PegasusQ governor, personally, i just switch the I/O Scheduler to SIO for better performance, since i have a ton of media on the phone
If the 4412 is a quad core why is that 4th core never listed? i might be overlooking somthing completely obvious and stupid, and i probably should have figured it out by now, it's been a while since i've been using android phones, but this question has bugged me since i bought the phone over a year ago... can someone please explain this? i'll be forever grateful
Do you have power saving enabled or any app to save battery installed?
Modelistis said:
Do you have power saving enabled or any app to save battery installed?
Click to expand...
Click to collapse
Neither of them... power saving disables two cores and makes the phone feel sluggish, and everybody knows battery saver apps are BS
Cores are numbered from 0, not one. So the four cores would be 0,1,2,3. Making the total number of cores to be 4
Aleycat said:
Cores are numbered from 0, not one. So the four cores would be 0,1,2,3. Making the total number of cores to be 4
Click to expand...
Click to collapse
Somebody told me about this some time ago... but even the CPU usage display option in the developers menu only lists 3 cores (separated by slashes) it seems as one core is system reserved... for usage by the phone itself... not for user needs
However... i switched CPU governors yesterday... and i noticed number 3 popped up... i might have been the reason that core was missing in SetCPU... but the built in meter still shows 3 cores... not 4
What governor are you using? Also i noticed mine also show only 3 cores.
had the same bug on my s3 with cm 11 just now but it went away after reloading the governor (there is a different governor than what i was using that only has 3 core enabled, so it might just be a bug with the phone using the wrong governor or bugged governor setting)
edit: just did some more testing and the pegasusq governor i am using dynamically disables cores if usage is low (at least on cm 11, it just sets them to "stopped" on stock 4.3 with the same governor)
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
buntybauva said:
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
Click to expand...
Click to collapse
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
DespairFactor said:
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
Click to expand...
Click to collapse
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
I am giving snapdragon battery guru a try, it's for Qualcomm processors. But I'm not very experienced in this stuff. I think it has helped but if someone with more experience wants to give it a try. Maybe they can shed some new light on this subject.
This is the result with on-demand governor settings when phone is idle. with stock kernel and stock frequencies.
Ondemand has always been my fvorite for all past phones. in op2 however it always reverts back to original after interactive. the best battery saver for any phone is swithching to 4.4.2. Azimg batteru life. unfortunately notpossble with op2
buntybauva said:
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
Click to expand...
Click to collapse
Being rooted alone will prevent OTA updates. You have to flash the full stock ROM when there's an update anyway which would overwrite the kernel.
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
If thats true, thatd be a heartbreaking, the first thing I look to before choosing a device, is clock speed
Unlock the game optimization
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Linux User said:
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Click to expand...
Click to collapse
You mean game optimization in settings/battery? I think we do not have that option in custom ROMs (I am currently trying Aicp 12.1) and never changed it in stock. I will try going back to stock to disable that option and see if the frequency table changes... If it does, it will be a pre-requisite before flashing custom ROMs in our device. Still, it is something the kernel should handle.
I would underclock the device on my own, as I did with my good old G2, but not having the option for the CPUs to scale as intended is not cool...
Well, frequency table shows no change with stock, but somehow, CPUs 3 and 4 scale up to 2150mhz now.
I guess LG did not cheat in the strict sense of the word, but just does not want us to have control over our devices...
Sent from my LG-H850 using Tapatalk
Floodland said:
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
Click to expand...
Click to collapse
So... I was freaked out after reading this thread, so i rushed to check using cpu Z and it turned out that mine is clocked at 2.15, so i don't know what is wrong u
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Android_420 said:
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Click to expand...
Click to collapse
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Floodland said:
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Click to expand...
Click to collapse
old versions of kernel auditor are buggy with the g5, they see it as a single quad core instead of big/little dual 2 cores. You need the newest kernel auditor.