Upgrade to Android 11 to fix slow device - Pixel C Q&A, Help & Troubleshooting

Have Pixel C 64GB which is completely stock 8.1.0. No unlock,root,twrp or anything. My only complaint is that it is slow. Full reset helps for sometime, but then becomes slow again. Only using it for browsing, emails, occasional videos/plex. Old interfaces does not bother me.
Would going through the process of upgrade to Android 11 be beneficial for me in terms of fixing slowness? Or I better stick to original and keep resetting every 3 months?

bogdatov said:
Have Pixel C 64GB which is completely stock 8.1.0. No unlock,root,twrp or anything. My only complaint is that it is slow. Full reset helps for sometime, but then becomes slow again. Only using it for browsing, emails, occasional videos/plex. Old interfaces does not bother me.
Would going through the process of upgrade to Android 11 be beneficial for me in terms of fixing slowness? Or I better stick to original and keep resetting every 3 months?
Click to expand...
Click to collapse
Simply, root your device to boost performance.
After rooting, you can debloat your phone and remove all the trash apps that came pre-installed, you can use root apps like Greenify to hibernate unused apps and you can use kernel tweaks like franko kernel to boost cpu/gpu performance

Related

Note 4 Sprint 6.0.1 Baseband PC1 lags

I bought a used Note 4 Sprint and since I flashed marshmallow using odin on it it gets laggy or reboots from time to time.
Is it something with my Baseband? Like should I install a different Frimware or it's a marshmallow issue?
The battery is okay and the screen is all good as well.
And finally do you recommend me any stable ROM or stock ROM ? Thank you I'm advance
You could likely do better with later Marshmallow releases and possibly custom ROMs if that's your thing. I'm on the PJ1 update running UN7 (Note7) port.
Between, Samsung, Google and Sprint, there's enough bloat on a stock Sprint Note 4 to sink a ship. And Samsung can't optimize the RAM caches well enough to suit individual preferences because it favors its native apps that are baked in as well as other system apps from Google.
This optimization may not favor the apps you prefer to run at will so you need to understand how to deal with it. There's Samsung's version of Doze and there's Android's version of Doze on your Marshmallow Touchwiz firmware. Samsung's version will routinely shut your apps down and doesn't do a good job of real time RAM management while sleeping. It's based on a 3 day run theory but it doesn't my user apps use at all; it shuts apps down that haven't been used in three days. This favors apps that it runs in the backgrounds continually.
So turn that of and focus on Android Doze is my advice. You can find both methods in battery management. Smart Manager may a shortcut to battery management but you can use Settings to find it too. You may see App power monitor on first battery screen; I advise turning that one off. Android doze can be found by tapping Battery usage then tapping 3 dot menu button in top right to goto Optimize battery usage. Once there, the dropdown menu will allow you optimize doze by showing all apps. I disable ones I don't want running continually but enable those that may be impacted by doze with screen off only. If you ever wonder why your music or downloads stop with screen off, here's a place to start. Push notifications should happen anyway with doze active so those may not need enabling to run continually.
You may consider freezing apps that show as running when you don't prefer them to even you're checking running apps. You can use Smart Manager often to optimize RAM or get an app that allows you white list some apps and dump cache for non white listed apps on a scheduled basis.
Personally I find Marshmallow Touchwiz poor for RAM management. The UN5 Lollipop ports managed RAM better without having doze. Somehow I think even the Note 5 may not have good RAM management on Marshmallow. Maybe Nougat is a different story? But I do know that Marshmallow proved to be a bigger challenge than Lollipop did, especially the ports. Why would I run Marshmallow? I guess its inherently faster than Lollipop. But only when optimized, IMO.
I also use Boost+ by HTC found in Google Play Store to free up RAM. Samsung thinks many apps I use regularly aren't being used. HTC Boost+ can discern app use better and logs freed RAM so you know it's working.
As a user, you can discern if these suggestions help or not. Just lag, preferred running apps and battery management advice. They may not be every user and YMMV.
Edit: pay close attention to battery capacity at reboots; bad batteries do have a tendency to shutdown, possibly reboot as well. Last time I had a bad battery, it was on a lollipop ROM; phone shutdown at 30% and plugging in charger showed 0%. Marshmallow may be different; battery is suspect for reboots in Marshmallow. I haven't experienced reboot issues with Marshmallow or have a bad battery to add to this suspicion though.
Sent from my SM-N920P using Tapatalk
You couldn't have got a better answer very concise and thought out. I can only add that a bad battery will have the same results as far as shutdowns in marshmallow. Never had a reboot issue. However many have with the earlier builds.
Sent from my SM-N910P using Tapatalk

[SETUP] Share your Current Rom Status Honestly?

This is a general discussion thread. You can share your Current setup of Robin, it would be helpful for us to know which ROM can be used as Our daily driver.
_____________________________________________________________
I'm currently using OmniRom's last build with Magisk module cross-breeder lite edition.
It's giving me Quite decent performance and Battery life.
Normally on continuous usage, it lasts almost 5-6 hrs on single charge.
_____________________________________________________________
If anyone getting a better Battery life, don't hesitate to post below.?
Post-Credit: @me ?
Thanks for sharing, I cannot give screenshots for everything here. I might have them but have to dig into the folder of screenshots but for now here is my battery experience over all.
I have used PA, Carbon and Omni extensively. So everything below is not a ROM review but its battery usage over all with them.
P.S. : For all ROMs, I use Greenify and Doze mode (within ROM, if not available then via NapTime).
PA for me has always been close to stock nothing great maybe a bit better. But because of its roaming issue I stopped using it. And switched to carbon.
Carbon is far better than PA and has very little standby/idle drain but it started giving me a weird 20-25% battery cut off issue and device used to shut down randomly anytime below 25% so I switched to Omni.
Omni has fared pretty well for me. Unlike other ROMs I get consistent battery life i.e. 3-4hrs SOT over a period of 10-15hrs. The ROM seems far more stable and there aren't any random battery drains. Omni sometimes behaves a bit erratic when using new camera apps i.e. first few times it would drain battery a lot but later it works fine. Its the device or ROM I don't know.
For Duo video calls it isn't so great after 30-40mins of call the battery is down by 30% maybe. But that is fine I guess the video call is on data too. So Robin isn't so great for that sort of heavy use in general I guess.
Here is my most heavy use day (on all ROMs) for which 10-12hrs is most the device can sustain.
Morning (for the device) starts at about 6:30-7am.
Its day starts with 96-100%; no matter how much juice it has I make sure I unplug anywhere above 95%.
My usage isn't heavy but I use data(3G/4G) 90% of the time,
Location/GPS is ON for about 40-80mins,
Voice calls ~30-90mins in total, (Most are cellular, 5-10mins VoIP calls)
60-90mins podcast/music, Podcasts which I listen are downloaded before but music is streamed via NewPipe ,
Mail, Twitter, Excel, Pocket app, Camera is used in between randomly.
I don't watch much YouTube on the device maybe a couple of 2-3mins clips, I mostly scroll YouTube to add them to watch later for watching on desktop,
SOT ~3hrs
I have to plug the device by 6-7pm with all that usage. Because by that time its about 15%. And for me Robin at 15% means about 10-15mins of use.
For not so heavy use days the device lasts from 7am to 9pm with SOT of ~3-3.5hrs + voice calls of 30-60mins + 40-60mins GPS/location.
Since Android N I haven't touched 4hrs+ SOT over a period of 10-15hrs of usage sadly.
That only happens if I unplug the device and use it continuously for 4-5hrs reading maybe with no waste in idle drain or data or wifi or push notifs etc. But that isn't a case of regular use for me so I will disregard that.
I have recently started using interactive governors like GlassFish and FairPark but can't say they have helped much. Standby/Idle drain is as low as 1-2% over 4-5hrs.
If you are getting 4hrs+ SOT over a longer charge time of 10-12hrs, I am all ears and want to know what different do you do.
I use Omni with Unicornblood kernel and Hawktail profile in Ex Kernel manager. I also use greenify and naptime. I'd say on average I can get between 3 and 4 hours SOT. On the lower end will be days where I'm out and about a lot so I'm on data, lots of idling, random browsing, reddit, messenger, etc. Usually have spotify running in my car through bluetooth. On the higher end will be days where I'm playing on my phone most of the day, with little screen off time, I can probably push over 4 hours on those days.
Today I've been off the charger for 10 1/2 hours, I have 1 1/2 hours of SOT. I spoke on the phone for about 15 minutes, browsed the internet a bit, some instagram, messaging, etc. and I still have 54% left.
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Luisalejandroqi said:
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Click to expand...
Click to collapse
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
/root said:
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
Click to expand...
Click to collapse
Omni, however, doesn't have Qualcomm's hotplugging solution, so both big cores are always on all the time and draining battery whenever your screen is on. Gandalf also messed something up with the kernel sources and broke NFC, requiring you to flash a kernel from an Omni weekly from around June-ish or July-ish to restore that functionality.
If you're patient enough, javelinanddart and Sultanxda will soon figure out how to fix the wake-on-plug lag in LineageOS. Hopefully, they'll also start on figuring out the power-button-not-waking-device issue afterwards.
EDIT: oops. Though javelinanddart proooobably found what might be causing the power-button-not-waking-device issue? Haven't had it happen on his LOS 15.1 unofficials yet so...
I am currently using Lineage 14.1-14.1-20180321 and eagerly awaiting the 'official' release of 15.1. I typically do not update to every weekly build. I usually watch the change logs and update only when the new security patches are released. Provided that update is stable (i.e. fast, everything works, no crashes) I will continue on with that build until the next security patch is released. More often than not, there are no issues, as I have found Lineage to be stable and fast.
I am running non-rooted, and I re-locked my bootloader. As a result, Google Pay is working well, without the use of Magisk.
I run Nova Prime launcher, and do not have a vast amount of apps installed:
Music - Google Play Music, Spotify, Amazon Music
Email and Calendar - Outlook, GMail, Google Calendar
Assistant - Google Assistant
Office Suite - Docs, Sheets, Drive, MS One Drive, Word, Excel, Google Keep, One Note
Camera - Stock lineage OS camera, Snapseed (editing)
Messaging - stock AOSP / Lineage OS messaging app
Video - YouTube, Netflix, Hulu (I only use YouTube to be honest... have the other two because of Chromecasting)
Misc - Google Home, Amazon Kindle
I list all those apps to say that given the relative few apps I use, I have all day battery life, for the most part. I am not a heavy user, but I check email multiple times a day, as well send/receive a LOT of MMS/SMS messages throughout the day. I generally only watch video on my phone (YouTube mostly) at home, and I generally cast it to my TV so that the Chromecast does the heavy lifting.
Overall, I have been very happy with Lineage. I finally settled on Lineage after growing disgruntled with AOSPA. The stock ROM (I gave it a good, honest shot at one point) could not cut it because of the lack of stability, heat issues, Bluetooth issues, and no updates.
I have only run into one issue (on a previous build) where by no doing of my own, the screen went blank on a full battery and would not turn on. I though the phone was essentially bricked. Held down power + volume down for 60 seconds (actually had to do this a few different times) and all was resolved. Still do not know why this happened.
Hopefully this helps someone...
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am running non-rooted, and I re-locked my bootloader.
Click to expand...
Click to collapse
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
/root said:
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
Click to expand...
Click to collapse
I do not have any detailed battery metrics, but I will start tracking this and get back to you.
Regarding your question about re-locking the bootloader... I am still running TWRP, just with a locked bootloader. I did not flash back to the stock recovery. After unlocking the bootloader, installing TWRP and ROM of choice, it is simply a 'fastboot oem lock' command. I cannot remember off hand, but I do believe that the OS was reset when I did that.
My setup. Works very well. I think omni is the best ROM available.
EAT_CHICKEN said:
My setup. Works very well. I think omni is the best ROM available.
Click to expand...
Click to collapse
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
/root said:
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
Click to expand...
Click to collapse
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
EAT_CHICKEN said:
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
Click to expand...
Click to collapse
Not using xposed.
Does using EXKM for CPU governors constitute to being a /system modification? Then I guess that would be the cause.

Pixel XL laggy since Pie OTA update

Been running stock Android ever since I got my Pixel XL and have been happily running the phone since it came up with each Android update and security patch. Never an issue.
Since a couple of weeks ago when I got the OTA update for Pie, ever since I have noticed the phone to just be laggy. Switching apps and launching stuff, things just take longer to happen. Sometimes they take seconds sometimes less. Games that would play fine now seem to have low frame rates.
My partner who has the Pixel (not XL) is in the same boat as me but having a worse time with the whole phone becoming unresponsive and locking up all the time.
Now the only reports I've seen regarding Android Pie is fast charging issues but neither of us are suffering those issue. All our PD USB-c chargers continue to fast charge fine. I have also seen some high profile Pixel 2 XL users have lag issues but no lag issues with Pixel XL.
Anyone else having lag issues, low framerates and system lockups with Android Pie on the original Pixel phones?
We have yet to factory flash but want to hold out before having to set everything up again.
A theory I have to why my phone is laggy is that I think the system is throttling back my CPU due to battery health. I know Google put some new smarter battery management in this version of Android but I think it is working too hard to a point where the phone is getting very irritating to use.
Thoughts?
No lags on Android 9 here but also flashed clean with factory image.
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
same problem here a lot of lag and freez in my og pixel xl when using ordinary apps like IG, gallery, clock and even xda apps but strangely it run smoothly when playing heavy game like asphalt or PUBG
---------- Post added at 04:30 PM ---------- Previous post was at 03:31 PM ----------
wingman021280 said:
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
Click to expand...
Click to collapse
I've turn off adaptive battery on my pixel xl but the problem still persists
Phone runs smooth on 9.0 for me. Clean flashed factory image. Maybe you guys too need a clean flash? I do understand that formatting should not be required for a phone to run smoothly after each update but looks like that is the solution for now.
I would agree that Android 9 is not as smooth as 8.1. When I first updated, it ran really bad - I eventually did a factory reset, and while it's not as smooth or fluid as 8.1, there's far less freezes or frame drops.
Went back to 8.1. Pie runs like garbage. It was taking 4-5 seconds to open my texting app. Everything back to normal on Oreo.
Pie was lagging my v1 Pixel XL. Seriously bad and huge battery drain. Did a factory reset and that resolved all my issues. Except for the PITA having to log back into every app and resurrect Google Authenticator for 2FA (make sure to right down all the auth sites and have backup codes ready). But as the other poster mentioned a clean install seems to be the only way to get Pie to work. Just bite the bullet and factory reset Pie.
Same-laggy original pixel XL and fast draining battery+ brightness issue
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Relamine said:
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Click to expand...
Click to collapse
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
My pixel xl was lagging too. I noticed my Zooper widgets were not loading. I went into the Zooper widgets app and was prompted with a message about it not being tested on 9 yet. After I acknowledged the message, runs without any lag. Widgets loaded on home screen too. Maybe you have a hanging app in the background.
tiny4579 said:
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
Click to expand...
Click to collapse
I've had adaptive brightness off so that can't be it. But thanks
how do i disable the pie update notification on my android 8.1 pixel XL?
Can't. Not without root.
My camera was seriously lagging. Sometimes 6-7 seconds to open and then 3-4 seconds to take a pic. Someone mentioned adaptive battery and it occured to me that maybe Accubattery was somehow causing problems with the adaptive battery settings in Pie. I uninstalled Accubattery and now my phone is back to normal. No shutter lag at all, camera opens in a fraction of a second.
Bought it a few days ago with Oreo, updated to Pie, and got one bug fix update after - no lag or something, runs super smooth.
There's really no reason to use things like that anymore, especially with newer versions of Android. It used to be necessary back in the day, hell Greenify was like mandatory lol. But really if you're going to use anything , you'd want a program to turn off GPS while screen is off, stuff like that , but it doesn't honestly make a dramatic difference with the optimization in Pie. I get roughly 4 hours screen on time and about 20% battery life left at the end of a cycle. That's 20% drain per hour and I never turn ANYTHING off. GPS always on, most of my day not on wifi, Facebook, Twitter , I just kill it.
To enjoy pie, its best to format data and flash factory images
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
murso74 said:
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
Click to expand...
Click to collapse
Did you OTA update or start fresh flashing an image with fastboot?

Samsung Galaxy S20 - Fast Battery Drain..

Hello.
I bought my S20 few days a go, with device everything is great but, my battery is terrible,
I use it every half hour to see do i have new notifications, messages, new posts on instagram and thats it.
I dont play android games or etc.
But with this minimal usage im losing 50% of battery @ work, and i use phone max 1h SOT in 7h of work time.
I tried Naptime but naptime only save my battery when phone is locked, but when im using phone im losing % very very fast.
My settings: Location , bluetooth, NFC disabled. Facebook in hibernation, and i disabled all bloatware with ADB uninstall.
And im using 120hz.
Normally with my settings on other phones i get very good battery life.
I do not want to root my phone, but is there any solution how to get more battery life on S20?
Thanks
Disable all power management except the screen setting which should be set to Optimize.
Disable all cloud apps, all device feedback, Google Transport, Goggle Transport Framework and Playstore. All autoupdates.
See my other posts on this ( good luck with that).
A package blocker is more effective for troubleshooting on the fly. I'm running Pie and Q gives you less tools to see what's going on.
Karma Firewall* is useful to lockdown Goggle Play Services* (a known serial offender) and others.
Nonetheless you need to find the troublemakers as you're burning up the battery.
Play with it... this may take a while.
*you lose its logging ability with Q I believe. A major hit if so.
**toggle on/off as needed.
blackhawk said:
Disable all power management except the screen setting which should be set to Optimize.
Disable all cloud apps, all device feedback, Google Transport, Goggle Transport Framework and Playstore. All autoupdates.
See my other posts on this ( good luck with that).
Click to expand...
Click to collapse
I looked up every aplication, service and everything is ok, maybe device need to adapt to my usage.
*Device is 2 days old*
But, i did not fully discharged battery on my first use. Can that be the problem?
I know i had to do it but i forgot that.
I had S10+ before this device.
Im using same settings and apps. But difference in battery life is big.
Talentooman said:
I had S10+ before this device.
Im using same settings and apps. But difference in battery life is big.
Click to expand...
Click to collapse
Unfortunately you'll need to track it down; no one size fits all. You need to figure out which system and 3rd party apks are responsible.
Use what tools are available and ones you can find for that OS.
Even with all syncing disabled on my 10+ Goggle Play Services relentlessly connects 4 times a minute with the internet. Blocking it toned it's battery usage down.
Brave browser is a hog and will run in the background unless forced stopped; closing its window does nothing.
Fun times... Google did nothing to address this and in fact has been making troubleshooting harder with each new OS using security as a ploy.
I ran Kitkat until last year. In 6 years I've never been forced to reload due to malware... bite me Google. Yeah viruses, trojans, etc are real and can/do infect Androids but almost always it's the user's fault. Transparency is what's needed not scoped storage and more user/apk inaccessibility.
Talentooman said:
I looked up every aplication, service and everything is ok, maybe device need to adapt to my usage.
*Device is 2 days old*
But, i did not fully discharged battery on my first use. Can that be the problem?
I know i had to do it but i forgot that.
Click to expand...
Click to collapse
Let it settle in for a week. You shouldn't need to disable any packages to get good battery . My s20 gets 6.5-7hr sot without disabling anything and just using the 120HZ medium power saving Bixby routine trick , 5.5-6 hrs on optimized . Don't listen to those who say you have to disable a **** ton of stuff and basically cripple your phone...you absolutely don't .
digitaljeff said:
Let it settle in for a week. You shouldn't need to disable any packages to get good battery . My s20 gets 6.5-7hr sot without disabling anything and just using the 120HZ medium power saving Bixby routine trick , 5.5-6 hrs on optimized . Don't listen to those who say you have to disable a **** ton of stuff and basically cripple your phone...you absolutely don't .
Click to expand...
Click to collapse
Depends on the device, the firmware and what's loaded including carrier and Sammy junk.
I've tried it every which way and now have about 86 apks blocked. Some like Playstore and Galaxy updates get toggle on as needed which isn't often.
Every time with power management when it was used it seemed to work but within a few days it became the problem with excessive power consumption.
Plus and even worse it will screw up phone functionality constantly and inexplicably at times.
Android will manage power and go into deep sleep with all buckets active; no power management needed... at least on my configuration.
Because of the time and trouble invested as well as trash features like scoped storage I refuse to go to Q. This 10+ will most likely run happily on Pie and many of its factory loaded google apks.
Yes updates can and will screw things up; update one or two at a time, observe.
Having a fast, stable, predictable system that runs well with good battery life and does what you want is all that really matters with Android.
Security is very rarely an issue even on ancient software if you aren't inept.
As is I'm ready to do a full reload if needed, be back and running in 2 hours and 99% fully configured by that day with bare minimal internet connection required.
My S20 (Exynos) battery life seems to have improved since the Android 11 / UI 3.0 update.
For sure it isn't perfect but : about 4h SOT and 25% left.
gilzve said:
My S20 (Exynos) battery life seems to have improved since the Android 11 / UI 3.0 update.
For sure it isn't perfect but : about 4h SOT and 25% left.
Click to expand...
Click to collapse
Im still waiting for update..
Talentooman said:
Im still waiting for update..
Click to expand...
Click to collapse
Disable all power management except for screen/power mode.
Android does nicely by its self.
The only thing you should have toogled on is fast charging if you use it. Try it.
Once you got it running well be very careful of updates especially firmware. At least wait a while to see if it blows up the phones of others using it.

Question about 2021 s20 exynos heat

Hello everyone, im going to choose a phone for my cousin and i was looking to s20+ exynos. Its a great phone but when i bought it in 2020 summer, it was heating up a lot even when doing normal tasks like using chrome or watching youtube. For comparison, when using zoom s20+ got up to 42-43 Degree battery and was really hot, same conditions s10+ was something like 31battery. After 2 days i returned the phone. Now i suspect this was due to software problems and wanna know if phone still heats up like this during normal use.
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
blackhawk said:
My Note 10+ Snapdragon was a hot running battery hog when I first used it. Today it's a fast, stable, cool running platform. Same firmware but I optimized it over time.
If you expect an Android to run perfectly out of the box you're having Apple delusions
Click to expand...
Click to collapse
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
theblitz707 said:
I suppose its okay for it to not be perfect but it shouldnt be that bad either. I wouldnt return it otherwise. That was definitely not a case where it would fix itself with user optimizations and a week of 'phone getting used to your patterns' bs. You clearly had a different problem if you achieved it without updates.
Click to expand...
Click to collapse
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
blackhawk said:
Doesn't matter what the problem is most times because with Android there's always a work around even on stock Androids.
Each device and user are different... we're not all the same lame Apple
It's time consuming... until you work it out.
If you're waiting an update solution you're going to wait... and maybe still not get what you want.
That's why Gookill can jam Q and especially 11 up someone else's auxiliary port.
No real improvements and lots of useless cpu cycle robbing big sister bs. 12 will likely be worse... so I'm not throwing my money or time at it. I have that luxury.
Dead cats, dead rats
Can't you see what they were at?
Click to expand...
Click to collapse
just out of curiosity, what did you do to stop your phone from overheating?
theblitz707 said:
just out of curiosity, what did you do to stop your phone from overheating?
Click to expand...
Click to collapse
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
blackhawk said:
A whole lot.
First step was to disable all power management.
Then go after each offender on a case by case basis. Rogue 3rd party apps either get firewall blocked or deleted especially if they're are startup apps that don't need that privilege.
I use Package Disabler and Karma Firewall a lot.
I clear the system cache and use as needed the old Device Care powered by 360° (firewall blocked) to clear system caches and logs.
Disable all cloud junk, and other Google trashware.
Simply disabling Google play Services and Playstore when not needed gives you another 1-2%@ hr of battery life. They are hogs that tend to run needlessly.
Disable all feedback... it's data mining at your expense.
Sometimes I turn off battery background usage to certain apks like Android Services.
It all adds up... play with it.
Each device, OS and user are different, so what works well for me might puke on you.
Don't make too many changes at once and be aware of possible dependencies for the apps you alter. It's a learning curve... and sort of fun.
&
It's almost impossible to crash and burn* a stock Android. So get after it!
*always be ready for a crash. Backup all critical data redundantly and be ready to reload at any time. While very rare Android crashes give little or no warning. Slight system instability and lag are many times the only warnings you will get on a fast platform... then bam, boot loop.
Click to expand...
Click to collapse
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
theblitz707 said:
Im pretty sure your note 10 would be completely fine without any of those. If you updated a few times. But if you have to stay at initial firmware for some specific reason then fair enough. (Btw, I also used to disable google play and google services but at the time my phone had 834MB ram so it was really important, i dont think saving %1 battery is worth it at all)
When i had my S20+, phone didnt heat at all when idling so some bloatware/feedback/google services/rogue app etc. wasnt the issue. I learned from someone else it was fixed after november update. Anyways have a good day
Click to expand...
Click to collapse
That's a minimum. When Gookill is misbehaving it's battery usage far exceeds that and extends into when the screen is off.
My battery usage when sleeping with AOD on touch demand is 2-3% for 6 hours.
That 1 or 2% is also after much of the Gookill junkware was disabled.
Google and Samsung apps are the prime suspects... as usual.
My stock 10+ is heavily reconfigured, I have no quick fixes for you because none of mine were quick
As for updates, they ain't got nothing for me. Last thing I want is Q loading on this device.
It would gut Karma Firewall's functionality and destroy trusted overlay apks... for what?
I've already archieved all my favorite apks so I'm not longer dependent on Playstore. Playstore will eventually alter or delete them.

Categories

Resources