Hello there,
In the last 2-3 weeks, after cleanly reflashing 32.2.A.5.11 with stock repacked kernel, I noticed that my phone is getting unusually hot. This was happening especially while using navigation (Waze) with data on, and consisted in the SoC getting to 50-55°C, apps getting closed (including foreground Waze) and phone being generally unresponsive.
Before this last reflash I used AndroPlus v42, with largely the same suite of installed applications, and with a slight difference in ambient temperature of maximum 5°C due to obvious reasons.
So the question rises: Has anyone seen this kind of difference in thermal behavior between stock and AndroPlus kernels?
Thanks!
PS: I didn't go too much into the details as I don't have them, especially about the previous kernel settings. So I only expect some rather generic answers. I might decide to switch between the two kernels in the next 1-2 weeks depending on available time.
PS2: I only switched to stock because I wanted to have full original functionality of the phone, but might decide to go back to AndroPlus as X-Reality and some camera de-noise functions are of minimal importance to me.
I recommend you use Zach's kernel (https://forum.xda-developers.com/z5...rnel-zachs-kernel-playground-z5c-wip-t3350690) by @zacharias.maladroit. Latest version for Nougat (2_12_2) is stable and runs quite cool. Last night I just disabled Core Control and enabled SOC temp toggle under Thermal using Kernel Adiutor. Currently testing if it makes a difference.
Anyways, give it a try.
Related
I've been keeping up on the changelogs for entropy's daily driver and I have noticed his evident concern for the bug starting in 2.6.35.12, and I was just wondering what the differences are between say 2.6.35.7 and 2.6.35.14? and whether or not that bug is really that big that I should worry about it or not?
on a separate note, right now I'm kinda struggling to figure out whether to use Siyah or entropy's daily driver? its definitely noticeable the difference when testing benchmarks I think Siyah is faster, but other than that theyre pretty similar for practicality's sake, however I do like the 100mHz CPU state in Siyah just for saving battery there...
Does anyone have one they prefer or real reasons for one or another?
Thanks
I think you just have to use the one you like the best. Entropy described it the best I think in another thread. He is a little more on the conservative side but focuses on stability. The siyah kernel is very good. I tried it for a day and had no problems. I just use entropys cause I know his work. Just go with the one your happy with.
Sent from my GT-I9100 using XDA App
I'll give you my theory on what I chose.
I've been using Entropy's since this board debuted. I've liked his work from back on the Infuse boards prior. He's very active around here and very knowledgeable. That right there goes a long way for me.
As to the actual kernels themselves, I tried Siyah for a few days and honestly had no issues other than the occasional issue where when locking my screen, it would take a screenshot instead. This might be fixed by now. But, as you said, it benched very well. With that said, the overall experience to me was the exact same with basic UI navigation along with watching videos and playing various games.
I have nothing against the Siyah kernel but from what I mentioned above, I'd rather use and help support Entropy with his kernel and report any issues that come about. Luckily, I've yet to report on a problem...
Like the others have said, it's really a matter of personal preference. Flash both and try them out.
I personally prefer Entropy's for the battery life and stability. But Siyah is also a very good kernel that places emphasis on performance. It can't hurt to try both.
It's not necessarily a bug that occurred in .12 - it's more like a bugfix that broke stuff dependent on the bug. It's a display-only thing - e.g. there are no known benefits OR drawbacks to .14 (that's why it's experimental - it's an unknown) other than that some forms of battery drain will no longer cause Android OS to be extremely high in the rankings in Settings->About Phone->Battery Usage.
e.g. it's harder to notice some causes of drain
As to Siyah vs mine - Siyah is for those that want to live on the bleeding edge - experimental CPU frequency governors, more aggressive application of patches - it leads to potentially better performance but can also lead to a higher likelihood of encountering a regression (something that broke).
Hello all,
I have a question for you all:
I have flashed a new rom today and have decided to NOT activate Google Now, and (after a few hours only), I seem to see a much better battery use?
Is it possible that this app, being monitoring so much all the time hoggs the battery quite a lot?
So, placebo effect or not?
Certainly possible I suppose, but I haven't noticed it drawing a significant amount of juice on my S3 or my Note 2.
I've had Now running in the background on my Note 2 for over 9 hours and the battery is still at 92% (minimal usage, just on WiFi), and while I'm getting tired of being notified about the ManU match, it doesn't seem to be drawing an inordinate about of power to run.
Is the new ROM you flashed using a different kernel or a newer revision of your previous kernel? In my experience, that's been the biggest factor in terms of power consumption.
devonck said:
Certainly possible I suppose, but I haven't noticed it drawing a significant amount of juice on my S3 or my Note 2.
I've had Now running in the background on my Note 2 for over 9 hours and the battery is still at 92% (minimal usage, just on WiFi), and while I'm getting tired of being notified about the ManU match, it doesn't seem to be drawing an inordinate about of power to run.
Is the new ROM you flashed using a different kernel or a newer revision of your previous kernel? In my experience, that's been the biggest factor in terms of power consumption.
Click to expand...
Click to collapse
Well, I am using temasek's CM10 Kang (70 I believe, latest anyway)
and with the kernel that came with it.
I ve tried other AOSP kernel, but no boot at all, so...
What I think is that XXDLIB modem does has a noticeable effect on good reception over here, so maybe that s the factor here?
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
That looks really interesting. Might be the reason I've been waiting for to upgrade to 5.1
Sent from my SM-G920F using Tapatalk
pa.ko said:
http://www.xda-developers.com/andro...every-car-through-updated-app-on-smartphones/
Looks like it may run on LP ROMs. Didn't tried yet.
Click to expand...
Click to collapse
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
m00n61 said:
Not installing on my LP unit running @dsa8310 October ROM. Starts the installation and after a few seconds - App not installed. At first I thought it's location-based but installed OK on my Samsung phone (Marshmallow)
Click to expand...
Click to collapse
i think you installed the arm64 version. You need the arm version. Mine is working. Make sure you installed the google app and google play music app before installing. Normally android auto is installing this in its installation, but than it goes in a loop (in mine case). So install them first.
For the rest android auto is slow, because it's using google maps, which is slow in the android 5.1 version. Spotify is working fine btw.
I'm working for a MAnufacture which produces HU for cars. Right now there is a native Android System for cars in discussion.
Source:
http://www.computerworld.com/articl...auto-making-your-car-a-big-mobile-device.html
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
try DSA room, its best 5.1 rom I used
dcdttu said:
I installed this on my Joying RK3188 running the latest Malaysk 5.1.1 ROM. Unfortunately, the ROM itself is so slow, Android Auto is almost unusuable. It does work, mind you, but the ROM seems to be the problem. Anyone know any bare-bones 5.1.1 ROMs that run quick? Thanks.
Click to expand...
Click to collapse
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
m00n61 said:
It's not exactly the ROM. It's the combination Google Maps + Google Now + Android Auto. I tried it on a clean ROM with only root and pretty much everything removed and it's unusable.
I also noticed that a 5.1 ROM will run OK as long as you only have either Google Maps or Google Now. When you have both it's barely working.
Click to expand...
Click to collapse
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
pa.ko said:
Don't know if it is only RAM related. These units have very poor CPU profile - throttling. stepup clock control settings which use highest clock only rarely so most of the time CPU is running slow so many processes suffer especially when multiple apps are running in background.
I'm not using 5.1 ROM (as I see still issues and people complaining) so I cannot test if and what apps mix causes issues.
You may try some kernel tools for testing different governors, CPU throttling (yes I would try also thermal throttling if you want to be on the safe side as rumours are Chinese used above mentioned downclocked setup in order to save CPU from overheating as there is no heat sink).
It would be interesting to open new thread for this. Much improvements may be achieved only by tuning kernel. And that needs some experimenting and practising.
Also, regarding 5.1 it is well known that it is 'heavy' and one of the main points of 6 (MM) was to reduce resource usage. So instead jumping to LP and having resource issues, I'll wait to see if there will be progress on MM which may resolve much of the problems around.
Click to expand...
Click to collapse
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
m00n61 said:
I agree. From monitoring resource usage under 5.1 I have to say that while RAM usage will rarely go over 700 MB CPU is aggressively downclocked. However, I need to first add a heatsink and then play with governors.
However, not sure how much would that really help with Android Auto, it's so damn slow it takes like 20 seconds just to start
Click to expand...
Click to collapse
Heatsink issue is to be investigated also. For instance many phones do not have heatsinks and still endure very heavy usage. So it may be not necessary. For instance, thermal throttling may be sufficient.
Thus, both governor and thermal control should be investigated. I believe it is possible with little effort to tune these units to work very nicely without much hw poking.
SW in these units is just so bad and poor it is almost unbelievable! Beside designers didn't have basic knowledge on architecture, they even 'tuned' many things in just opposite of what is needed. They could have better situation if only leaves everything by default in AOSP
What's your way to make your device be truly yours?
Me personally,
I am a power user and i don't really care about battery life much (1.5 days of battery life is enough for me), and i love to try out custom roms. I always loved the look and feel of pixel devices, especially the product sans font.
So my way of setting up my device is to install a font pack and a custom kernel.
I had mostly used the AOSCP Rom since it first came out, but recently the Liquid Remix rom is being my daily driver.
So my way to flash things is-
Liquid remix rom>Product sans font>Stormguard kernel
That does my job. and later on i install some apps like modded google cam and pixel 2 launcher and the Viper module from magisk for my sound mod..
So at the end of the day i have a device with super stock pixel look and full of raw performance.:victory:
But whats your way of doing things? Do you love stock miui or run a customised version of it? or are you a part of the modding community?
I like a balanced phone. Neither biased towards RAW performance nor too power saving.
What I find is you can increase performance and decrease battery consumption at the same time when you minimise the amount of automation in your system. Say for example an auto sync service which requires it own service to be running in the background, it's not much savings but when a considerable number of automations are reduced your phone might run smooth even on the powersave governor. I analyse evey automated process be it kernel related like Touch boost, a system automation like updates checking, an app automation like google sync and see if it is really necessary for me. Only the once I use and need get to run.
This is mostly why I root my phone in the first place. I want my phone's power where and when I need it. But never do I compromise on performance too, after all we're in the 21st century.
I use a well stable custom ROM( which most of times happens to be Lineage) topped with a well balanced kernel and of course Magisk. Once booted there's a lot of stuff I do to achieve that butter smooth power friendly UI.