Related
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
shinesthru said:
Between these 2 governors, has anyone noticed a significant advantage as far as battery life goes?
Click to expand...
Click to collapse
Hopefully more people respond to this, as I'd like to know more details around the msm-dcvs governor. I had it enabled in Clark's 0.0.6 ROM, and I noticed it was pretty much locked at right around 1000-1500mhz. It wouldn't scale below that. I don't know if it was something in the ROM or not, but I used Voltage Control to scale the min down to 352mhz or whatever it is.
I changed the governor to ondemand and set as boot as service (was getting errors creating the init.d script) and it seems to be functioning fine now.
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
EndlessDissent said:
I've been using the msm-dcvs governor in CyanogenMod, and I've actually been having the opposite experience. It seems to max out around 1134MHz most of the time, though CPU Spy shows that higher clock speeds are being used, but rarely. The rest of the time is spent mostly around 384MHz. I haven't really tested it fully yet, let alone against ondemand. I'm going to keep using msm-dcvs since Qualcomm made it specifically to take advantage of our processors' scaling and voltage features. I haven't had any problems.
Click to expand...
Click to collapse
What has your battery life been like?
jhavron said:
What has your battery life been like?
Click to expand...
Click to collapse
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
EndlessDissent said:
Well, I've actually been forced away from msm-dcvs because there is a bug in the AOSP Jelly Bean implementation, and none of the devs involved with either CM or other AOSP projects will acknowledge that the problem exists, let alone fix it. So, I've been using the Ktoonservative governor. It's working pretty well for now, but I'd prefer if msm-dcvs just got fixed instead
Click to expand...
Click to collapse
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
hayzooos said:
Out of curiosity, what problems were you having? I have Voltage Control set to apply noop/ondemand at startup, but I just temp changed it back to msm-dcvs for kicks to see how it goes. I know it's the stock governor that came with the phone, so I'd like to stick with that if possible.
I thought I remembered seeing the speeds always be towards the higher end before, but I'll run it again now and see what happens. I'm using FreeGS3, v0.1.1 right now for what it's worth.
Click to expand...
Click to collapse
With the stock CM10 kernel, as soon as I touch the screen, the frequency jumps to 1134MHz and stays there until you turn the screen off. Then, it drops to the min. speed until you turn on and touch the screen again, at which point it jumps back to 1134MHz and locks itself there.
With the KT747 kernel, the speed more-or-less limits itself to 702MHz, and it's nearly impossible to make it scale any higher. KToonsez refuses to acknowledge the problem, so it won't be fixed anytime soon.
I've gotten CPU Spy graph screenshots to illustrate the problems (comparing the stock ROM to AOSP ROMs while doing the same task), but all parties still deny the problems exist. I don't really know what to do to get them to fix it at this point, so I just gave up. I'm hoping it's just some JB driver issue and it'll be fixed when the official JB kernel source is released.
hello. I have a galaxys s2 hercules t989 known as tmobile. the problem is that the cell overheats me much when I use it and when charging too. the same load power cycled only takes 2 days to load. heats up like an oven. someone will know the problem this past me and I can help?
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
I have the original jelly bean I 4.1 and I've put several original and custom rom and is still overheating. I think it is problem of romsfirst
You guys need to check CPU usage
Install CPU usage app and load the timeline (also press the second button to see system apps). You can see which which one is using the most CPU power and terminate it. If that fixes it, you can uninstall or disable that particular app.
ok. result will do that and post them. thanks
JoeGrimm said:
I'm having the same problem, it's not as bad on stock roms as on custom roms not sure why.
Click to expand...
Click to collapse
Custom ROMS + kernels may have overclocked GPU and CPU for a performance increase. This will cause your phone to get hot. Hot Hot...If you're stock, there is something running in the background as others have suggested. If it's a custom ROM, install something like Trickerster MOD and check to see what your CPU and GPU are set at...Anything over 1512 (CPU) and 266 (GPU) will cause increase in heat due to the processors running past their stock settings.
Governor
If your capable of changing the governor like CM or other Roms with custom Kernal's, find a setting that doesn't use a lot of juice all the time. I keep mine on Smartass or conservative if i'm not using it or charging it. I had the same issue before because I had it set to ondemand or performance. Hope that Helps
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
NOPE
I have the same problem but it isnt the battery thats heating up, if you take the back cover off, and feel the battery, it is not heating up. I did get this problem when i installed a custom rom, i had issues with that one including the battery life so i switched back to official jellybean 4.1.2 or whatever, and the battery is fine, does still get hot though but not as much, or maybe were all huluscinating
--- ALIENS
Hey all,
I've been playing Star Trek timelines since it came out and I've had a lot of fun with it. It played pretty well on my M8 and Moto X Pure.
However, the 10 has been problematic with they have being laggy and stuttery on it. I've tried it with combinations of LeeDroid, Viper10, and the EX kernel. The phone runs great otherwise, it's just in this game I have issues.
Please note I'm not blaming any of the devs for the issue. I think it's either hardware or I need to tweak some things. I'm not sure that running at the 2k resolution is the issue add it was fine on my X.
Are there any tweaks I could apply, perhaps at the kernel level, to help improve performance? I have the kernel overclocking cpu and gpu. I also have the governors set at ondemand (cpu) and performance (gpu). The only thing that seems to help is putting it into performance mode in EX manager. And of course, it gets a bit warm in that mode.
I love the phone. It's just been a bit disappointing gaming. The SD820's been a disappointment I that respect.
Does anyone have any thoughts for getting better gaming performance?
Thanks!
Super
Sent from my HTC 10 using XDA-Developers mobile app
I recently rooted and installed a custom Rom and ElementalEx Kernel. I noticed that the default profiler for the Pixel XL is something called sched which appears to be a fairly conservative governor. I changed it to interactive which I normally use on other phones and battery life suffered considerably. I switched it back to sched and cpu frequencies are much lower but I don't notice any drop in performance. I tried researching sched but haven't found much. Anyone know how this governor works?
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
noidea24 said:
Sched is the most efficient governor for our pixel.
The real question is why do you want to change the governor? If you really want some things to mess with to increase battery and/or performance then check out "L speed (boost&battery)" in the play store. And No, this isn't shameless advertising either, the dev is right here in our forums.
Click to expand...
Click to collapse
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Pixel/XL Uses EAS so governors like Sched, Schedutil etc etc. Meanwhile every other Android device uses HMP your regular governors like Interactive, Ondemand, performance, conservative etc
So it's recommended to use Sched as the defualt but you can learn more about EAS here Also Freak07 has some great info on EAS and it's govenors here
jhs39 said:
It was a reflex reaction because I'm used to using Interactive and the CPU frequencies seemed really low compared with what I would see on the 6P. Those frequencies on the 6P would result in a noticable performance lag. But I guess the phone design is really different so you can't compare them that way. I'll check out L Speed. Never heard of it. Thanks.
Click to expand...
Click to collapse
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
noidea24 said:
Same. Coming from the 6p / 5x scene. The best governor was interactive, especially due to all the tweaks and changes that could be applied to the governor (like on ElementalX).
But no, pixel is almost dedicated to sched. I honestly don't think anyone else is running anything else and getting decent results from it
Click to expand...
Click to collapse
All kinds of us are running schedutil gov on custom kernels. It's the next iteration of EAS sched gov. Better performance than sched.
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Anyone on ElementalEx change any settings other than the governor to improve performance on the Pixel XL? A lot of the available settings are different than I'm used to.
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
lovetv said:
Hi, everyone I'm s7edge owner would like to use a the Google pixel governor, can someone show me the direction please? Thanks
Click to expand...
Click to collapse
Not possible without an EAS compatible ROM/Kernel
ithehappy said:
Yeah same here, I would always use L Speed or some different governor on previous phones than default, cause default was always not the most efficient, both performance and battery backup wise, but on Pixel there is no need. In fact devs have suggested us to use the default Sched governor, so I am sticking with it.
Click to expand...
Click to collapse
I think the devs suggest using the sched governor because they are either too lazy or not knowledgeable enough to create other governors that are compatible with the Pixel. The sched governor is far from efficient. It's clearly a performance based governor and it allows the Pixel battery and CPU to get very hot very quickly. The Pixel CPU can get to 130F just performing what most people would consider standard tasks on their phones. I'm not even talking about gaming or anything remotely CPU intensive. How long do you think these phones are actually going to last when they heat up so much?
What's the difference between sched and schedutil? I saw schedutil is default on the ElementalX for !y Pixel 2 XL.
I'm on Android 13 and was hoping this would sort out the overheating problem I had with Android 12 (I read in a few places that it would), but it did not. The phone gets very warm when charging, and hot when streaming video, and just generally through simple use, nothing particularly demanding. I haven't rooted this phone because I did not see the need, but I would consider it if it was the only way to fix the problem. Is anyone experiencing the same, and does anyone have a solution?
I could be wrong but generally speaking in my experience, going from one major upgrade to another the phone works a bit harder to re-train itself to your use patterns. I just did my upgrade yesterday and experienced some slight to moderate heat as well. I also noticed that battery is draining a bit faster which I think again is part of the process. I'm going to give it a week or so and if I'm right it should improve.
I'm biased because I've had my Pixel 6 Pro rooted (and updated every month) since last November, and I also use Kirisakura custom kernel with its companion apps and currently have the one app set to the maximum battery savings.
So I can't really compare to 100% stock unrooted with the stock kernel, as I'm only briefly on the stock unrooted kernel each month after I manually flash the latest update.
Several others have commented, and I've experienced too, that with Android 13, we've no longer experienced as severe higher temperatures when charging. I don't remember if the others were rooted and using the same custom kernel, or if these were general Android 13 comments, so your mileage may vary. Sorry I can't give you any more concrete information.
Good luck!
Granted this is for my 4a5g but I wouln't be suprised if/when I get a 6 that its battery performance would be less than stellar after a good days use of phone and/or screen and radio/network. i.e. stock. Before I went to Lineage on my 4a5g I think my battery would cut a good 30-50+ percent each day. I put lineage on it and I poop you not, can go from a 75% to around 20% in about 5-6+ days. I tend to have my screen brightness around a little less than 1/4th on the slider bar.
When I had an HTC M8, after around 2 or so years (this was around 2016/7 or so. got phone oct '14) on the stock firmware the phone couln't keep it on for more than a day. Ran ViperRom for a bit then switched to cm/lineage and that stretched my usability of the phone another 5 years. It got to the point where the phone would shut off when it got to around %50 charge and go ding dong and turn off--without pluggin it in I had about 8 hours run time on it. My battery was beyond gone and no way would I have gotten that usability on the stock rom.
So, to answer your question, yes, trying different roms and kernels (rooting) could be to your advantage to prolong the life and performance of your phone.
Even if you choose to run the stock OS, with root, you could disble any bloat running in background. Kill any programs/services leeching CPU (and hence battery) cycles. You could definately make it run more efficient for YOU. Maybe not for the next guy who needs his facebook, twitter, ticktok apis and stuff loaded and at the ready. Everyone is different. But they tend to make the phones (they think) for everyone. in mind and as a result, device performance and lifespan become affected.
I definitely have heating issues and this is on a warranty exchange. The 2 previous P6Ps had all the same issues as this current device.
My phone was hot on A12 (41/45°) and since i clean flashed A13 and wiped it is cold (32/35°) for the same usage.
Greetings.
Good topic.
I have bought this phone a day before. I'm facing device heating even under simple tasks like scrolling messengers, browsing etc.
Previously I had OnePlus 7 Pro (Snapdragon 855), that one was cold all time except while charging or playing games.
However, Pixel looks warm or even hot even upon light using.
I'm a bit confused about that.
Is it a common problem of this device? Or probably exactly my device is affected?
I haven't faced overheating or alerts about that, however, it feels hot for my hands that got used to feel a cold phone while low load.
Currently, I have about 37-38 degrees while browsing on XDA and writing this post.
Just wondering that digits you have?
I did a warranty exchange on my P6P for a different issue and I'm glad I did. My replacement device has much better thermals than my original. My original one would get quite hot while charging and restoring apps and was almost uncomfortable to hold and to the touch. Could always try a warranty exchange and see if the replacement device is better for you. Also, Kiri kernel has been reported to help with the thermals. I've seen several reports of users commenting that their device runs cooler. Good luck!
I had heating issues and battery issues when I first received my P6P. Once I got it out of the box, I set it up and restored backups, rooted it, updated to android 13 without wiping, rooted again, and then flashed the Kirisakura kernel. I decided to try and flash android 13 again but keeping the -w flag to wipe userdata and didnt restore my backups and I've had amazing battery life and no overheating. If you haven't yet, try doing a factory reset. As simple as it sounds it may very well help
My fully stock P6P (on A12) gave an overheat warning yesterday while we were having a day out, it was only 22°C although we were in and out of the sun as the clouds rolled by but the phone was showing 46°C after being sat in my pocket.
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
MrBelter said:
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
Click to expand...
Click to collapse
Try OnePlus 9 Pro
darkness4every1 said:
Try OnePlus 9 Pro
Click to expand...
Click to collapse
Thing is I have never experienced overheating on any phone (that i have owned) in UK before, using an Exynos as the basis of Tensor and then whacking an extra big core in it was a pretty bad idea unless you live in a fridge.