Related
I did my first ROM and battery update with NonS3ns3 V2.0. All went fine.
I was surprised to see less than 200MB of memory free after the upgrade. I thought one of the benefits of this ROM was that I would be seeing closer to 300 MB of memory free.
I am not using ADW. Currently I have Go Launcher for my front end. Could that be the issue?
Any suggestions?
swieder711 said:
I did my first ROM and battery update with NonS3ns3 V2.0. All went fine.
I was surprised to see less than 200MB of memory free after the upgrade. I thought one of the benefits of this ROM was that I would be seeing closer to 300 MB of memory free.
I am not using ADW. Currently I have Go Launcher for my front end. Could that be the issue?
Any suggestions?
Click to expand...
Click to collapse
Unused memory is wasted memory. The goal is to use as much as possible while keeping a reserve free for any app that might be opened.
Go launcher is not the issue. I have near 350-400mb on boot with CM7 and I use it (and it's set to stay in memory).
However, as stated previously, if you're not using your ram it's going to waste and I still wouldnt' care if I only had 200mb free. It's not like on windows where you have to start closing stuff to get the ram back. If you start running out, it'll just start closing apps you're not using for you. I wouldn't worry about it. As much as my ram miser instincts want to kick in (because I started out on computers when 8-16mb of ram was a lot ), I just tell that urge to STFU because it's a dumb idea.
I usually have about 240MB free right after boot and that quickly dwindles down to about 140MB to 160MB. That really is plenty for just about anything you're going to make the phone do at any particular moment. When you think about it, an entire Sense ROM couldn't fill all the memory available, much less AOSP. There's caches and other files taking up the rest of the space, which is good because that's less data pulled from eMMC. Addressing eMMC eat a lot of power. Some of the kernel devs have some good info on how their kernels work and how to tweak them to free up more or less memory. It is possible to script the kernel to much more aggressively free up memory, but typically that will hurt performance.
Thanks for the replies. I am new to Android (2 weeks) so still trying to figure out a few things. I am coming from the old school where more free memory was always a good thing so that new apps would start faster.
I am really surprised by how many apps are running in the background on there own such as Whitepages, News, XDA, Weather, Amazon App store, My Verizon, etc. Why are all these apps running? I cant see why the Amazon App store app needs to be running unless I am using it.
I have seen some tools that can be set up to automatically kill some of these apps. Is it worth it? Which one do you reccommend?
I use this and its fantastic. http://forum.xda-developers.com/showthread.php?t=991276
Sent from my ADR6400L using xda premium
swieder711 said:
Thanks for the replies. I am new to Android (2 weeks) so still trying to figure out a few things. I am coming from the old school where more free memory was always a good thing so that new apps would start faster.
I am really surprised by how many apps are running in the background on there own such as Whitepages, News, XDA, Weather, Amazon App store, My Verizon, etc. Why are all these apps running? I cant see why the Amazon App store app needs to be running unless I am using it.
I have seen some tools that can be set up to automatically kill some of these apps. Is it worth it? Which one do you reccommend?
Click to expand...
Click to collapse
Amazon apps, in general, are abuse to resources. Not sure what to tell you about killing it, because killing it is just going to make it restart again, and that's going to eat more battery than letting it just suck up space.
It's not so much the apps on Amazon as the Amazon App itself and how they implement things. Amazon has some crappy DRM for their apps (if the developer decides they want it). Basically means it checks a lot to see if you're online and allowed to use the application (but does so way more than it needs). Some apps have problems or did with working in airplane mode because of that.
It also thinks you have a new phone nearly 100% of the time when you flash a new rom or update your current one. You can log into your amazon account on your PC and find out how many "phones" you have under your account settings for their apps. Each added phone basically causes the app to flip out more and cause more problems, so deleting the extra ones is a good idea.
Other apps will not work without the Amazon store installed, which is a poorly coded piece of crap as well that won't work if you try to modify the contents of the apk.
Also, a lot of those apps running in the background are not really taking up resources, they're just keeping a bare minimum loaded into memory and the rest is cached. They do that so they can load up quickly (like the browser, maps, etc).
I've been on BAMF forever for a few days now, and I typically have only 90-100MB of free RAM. It has been absolutely smooth as can be with no lag. I can open an app, use it for a bit, and then hit home so I can open another app to check on something, and the first app stays in memory just as it should.
Sent from my HTC Thunderbolt
Thanks for the feedback. I have removed Amazon from my Tbolt.
It still bothers me to see all those other apps being loaded in the background without asking first. It's like my 17 yo daughter leaving her stuff around the house. It just seems disrespectful of the common spaces.
swieder711 said:
Thanks for the feedback. I have removed Amazon from my Tbolt.
It still bothers me to see all those other apps being loaded in the background without asking first. It's like my 17 yo daughter leaving her stuff around the house. It just seems disrespectful of the common spaces.
Click to expand...
Click to collapse
you'll get used to it. just pretend they're not really open (well most really aren't open, so I guess you dont totally have to pretend, haha)
Hi Guys,
I am on ICS 4.0.4 and my S3 shows 779 MB, which is always busied by 680 or so!!!
I checked an S2 with ICS 4.0.4 and the memory is 830, and is busied by 450 on average. (S2 has larger memory than S3 on ICS4.0.4???)
So what is wrong with the S3 memory? i keep on killing apps all day and night to bring it to 450 or around, I dont have too many programs, and, i am not using except two widgets, checking on the background processes annd programs, most of the system's stuff is running on its own, even if i freeze some using Titanium pro.
Anyone has the same problem (if i can call it a problem?!) is that normal??!
Why would you consider it as a problem? Android is best at multitasking. You don't have to kill apps, its the nature of the beast so to speak to have a semblance of the apps running in the background for your convenience.
Sent from my GT-P3113 using XDA Premium HD app
Bigger screen and stuff like Smart stay and S voice eat up extra Ram.
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Okay, i got it, No more killing APPS , now the question is, how come the S2 has more overall ram than the super S3, on ICS4.0.4??? considering the 779MB to the 830? its just a noob question
gennoz said:
Q: Whats up with the ram?
Click to expand...
Click to collapse
Q: What's up with searching the forum?
Why are people asking the same questions over and over again?
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
goodie said:
i flashed mine with stock I9300XXALF2 now my average ram usage has dropped by at least 150mb & is much snappier on the home screen redraw
Click to expand...
Click to collapse
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Click to expand...
Click to collapse
Bullied?
Try reading the rules before posting. Rule number 1 is search before asking a question. Now you're asking the difference between odexed and deodexed... Do you seriously think you're the only person who has asked this? It's discussed EVERYWHERE!
gennoz said:
Thanks for the tip, im kinda new here, i am trying my best to read on before getting bullied by someone like up there but, eh, still not doing it right.
Anyways, i found two posts, one about a stock ALF2, and the other talking about deoxed and oxed .
What is the difference between :
GT-I9300_WanamLite.Stock.Deodexed.XXALF2.NO-WIPE.zip
GT-I9300_WanamLite.Stock.Odexed.XXALF2.NO-WIPE.zip
Click to expand...
Click to collapse
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
The search on the site is horrible. I use Google and type xda after anything I'm looking for
Sent from my LG-P999 using XDA App
Roastario said:
Deodexed ROMs have their .apk's (which are basically the application packages) repackaged in a certain way. An "odex" can be thought of as a collection of parts of applications that have been pulled out and optimized before booting. This speeds up the boot process - in a way, it preloads part of the applications - but it also makes hacking those apps difficult because part of the original code is already extracted somewhere else.
Deodexing is just a process of putting those pieces back into the original applications. It takes a while to extract those parts and build the .dex cache (aka Dalvik cache), but only because the relevant parts aren't in an easy-to-access place for the system. The advantage of this is that an app can be modified effectively and the developer doesn't have to worry about conflicts from the separate odex part of the code.
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
Wow, seriously thanks for your time
Query on RAM....
norpan111 said:
Yeah it's really dumb to kill apps and clear ram the whole time, phone will feel sluggish because it needs to fore up stuff all the time that would normally sit kindly and wait for you in ram... You are making your phone slow and killing your battery
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Dude... My s3 ram in task manager is showing 883..... previously it was 779mb.... i donno wat would b the cause for this.... i have updated to jelly bean.... please ans my query....
Roastario said:
So, short version: "Deodexed" ROMs have all their apps put back together. If an app can be themed, for example, a deodexed version of that app will not get messed up when the modified .apk tries to mesh with the odex of the original un-modified .apk. Because it's not there.
If you want an aftermarket theme, you need a deodexed ROM. I'm not sure if deodexing can be done to individual apps within a non-deodexed ROM.
Click to expand...
Click to collapse
I suppose "standard ROMS" have no apps or anything in the "Dalvik cache" ? (as all apps have "stand-alone" APK's ?) ... correct ?
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
noobee1 said:
well, I guess its widely know how android manages memory, and clearing ram is more of a performance inhibitor than a booster. I gave up all hope when I took my s3 to the service center and was given the solution of clearing the RAM repeatedly to solve the horrible ram issue.
the problem i was and still am facing is, the ram usage increases automatically within few hours of usage with hardly any apps installed. its extreme as it crosses 790mb and stays in that range. whats bad is apps keep on restarting in the background, phone slows down terribly ( switching between apps, moving out of an app just to stare at the app drawer 3-4 secs for all the apps to load, even the keyboard takes time to pop up). So moderate ram usage is good, but high ram usage is bad especially when it causes to slow down basic use. now what problem i am left with is deciding whether to root and flash a custom ROM and void the warranty on my one month old device, as both the times i revisited the service center the only thing the guy did was format and reload the firmware, which didn't solve anything. this was prevalent on stock ICS as well after the JB update via kies. as a last resort I am thinking of trying an official firmware from another region. as Indian one was causing the issue. my friend got his s3 from saudi and he hasnt had such severe problem(certain sluggishness is acceptable on a bloated stock firmware). so i am thinking of flashing that firmware. is it safe to do that? and i wouldnt need root access for that right, only odin and the firmware correct?
Click to expand...
Click to collapse
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
corleno said:
Generally RAM usage depends a lot on running widgets.
I personally use only one widget on screen at all times. (Google search) which is enough to get the job done for anything. And I run only 3 home screens
I would usually have about 200 free ram
Also Im on Omega 34 rom which is by far best (In my opinion for RAM management). It automates in such a way that 200mb ram is free at all times.
I really dont care much about warranty ,the first thing I do when I get an android device is to root it. (You do know you can unroot right ?)
So if RAM is really so important to you its best to root.
Click to expand...
Click to collapse
yes I am well aware of rooting/un-rooting and other basics, had done all that on my S2(i9100), also found it more fun and efficient than stock but time is the only factor that's stopping me from experimenting. and thanks for the omega tip. I am certainly going to flash a custom ROM, after trying out few official ones, When I do, I would definitely go for Omega, alot of people recommending that one.
Omega is good as is WanamLite, Foxhound and Hyperlight. Smoothest I've used were Foxhound and Omega although I'm running WanamLite at the moment. Smoothest version I've used.
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
try flash custom kernel..the memory management is very good with custom kernel
Sent from my Nexus 9 using Tapatalk
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Choochter said:
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Click to expand...
Click to collapse
Firstly, you need to face the fact that 2GB was a bad decision by Google for this tablet. There is nothing that we can ever do about that. :crying:
If you want to stay on stock, Chrome is the main culprit in consuming Ram. Switching to Habit Browser makes things better as well as changing your DPI to 288. Do a search on XDA regarding this. Whilst it improved things, it was still not enough for me.
I snapped a week ago and have now rooted and flashed CM13 and stuck with Habit. I've been using a few days now, and for the first time, I can keep my 3 Fantasy Premier League Tabs open, (they are huge,) without constant refreshes, redraws and lag. :victory: Right now, I feel for the first time, I'm getting what I paid for and the Nexus Experience. The only bug so far, is that always listening doesn't work.
If you've just bought this tablet, I'd consider returning it if you are not prepared to root. The performance will never be acceptable on stock.
arminvm said:
My Nexus 9 is running slow most of the times and it takes while to I switch between apps or open an app most of the times...what is the fix for that? I have been trying clearing the dalvick cache several times but no help...and I really don't have lots of apps. Thanks for your help in advance.
Click to expand...
Click to collapse
Clearing dalvik cache will do precisely ONE thing and ONLY one thing; make it take a long time to boot next time as it regenerates it.
Ignore the amount of available memory. People who are concerned about the amount of free memory are trying to apply bad mswindows knowledge to Android. Totally different and no comparison. UNUSED MEMORY IS WASTED MEMORY!!!
So here is how memory management works in Android; it *preloads* everything that it thinks you are most likely to actually use, so that when you DO use it, it is more likely already loaded and starts up very quickly. If you are switching to something that is NOT already loaded, then it just needs to dump lower priority programs out of memory, which basically only takes a few nanoseconds (billionths of a second). So that is NOT it.
If your device is acting slowly, then you need to figure out what the actual cause is. Trace the CPU utilization with something like the "top" command (the one with busybox is a lot nicer than the one that comes with Android) while you are experiencing slowdown. You can also look to see if there is excessive I/O happening (i.e. read/write to the internal storage), and of course, some software will require a network exchange before it will start up -- nothing you can do about network lags.
kacang87 said:
try flash custom kernel..the memory management is very good with custom kernel
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Thanks. I am still on the official rom, I probably should switch.
Choochter said:
Try tapping on 'Memory used by apps' on that memory settings screen, should let you know what the culprit is
Click to expand...
Click to collapse
I have done it several times. As I said, I really have not so many apps and just the very common google apps are installed.
Masteryates said:
Firstly, you need to face the fact that 2GB was a bad decision by Google for this tablet. There is nothing that we can ever do about that. :crying:
If you want to stay on stock, Chrome is the main culprit in consuming Ram. Switching to Habit Browser makes things better as well as changing your DPI to 288. Do a search on XDA regarding this. Whilst it improved things, it was still not enough for me.
I snapped a week ago and have now rooted and flashed CM13 and stuck with Habit. I've been using a few days now, and for the first time, I can keep my 3 Fantasy Premier League Tabs open, (they are huge,) without constant refreshes, redraws and lag. :victory: Right now, I feel for the first time, I'm getting what I paid for and the Nexus Experience. The only bug so far, is that always listening doesn't work.
If you've just bought this tablet, I'd consider returning it if you are not prepared to root. The performance will never be acceptable on stock.
Click to expand...
Click to collapse
Thanks for your reply. Yeah, most of the times, the slow down happens while I am in chrome and browsing..it actually is not snappy at all in internet browsing...however, I remember it was back in the days that I had bought it.
No, I have this Nexus 9 since last May I think, but have not yet found the time to root it and flash a custom kernel and rom . Anywyas, I have done it previously for my other devices, so not that much rookie in it. Probably will give it a try,
doitright said:
Clearing dalvik cache will do precisely ONE thing and ONLY one thing; make it take a long time to boot next time as it regenerates it.
Ignore the amount of available memory. People who are concerned about the amount of free memory are trying to apply bad mswindows knowledge to Android. Totally different and no comparison. UNUSED MEMORY IS WASTED MEMORY!!!
So here is how memory management works in Android; it *preloads* everything that it thinks you are most likely to actually use, so that when you DO use it, it is more likely already loaded and starts up very quickly. If you are switching to something that is NOT already loaded, then it just needs to dump lower priority programs out of memory, which basically only takes a few nanoseconds (billionths of a second). So that is NOT it.
If your device is acting slowly, then you need to figure out what the actual cause is. Trace the CPU utilization with something like the "top" command (the one with busybox is a lot nicer than the one that comes with Android) while you are experiencing slowdown. You can also look to see if there is excessive I/O happening (i.e. read/write to the internal storage), and of course, some software will require a network exchange before it will start up -- nothing you can do about network lags.
Click to expand...
Click to collapse
Thanks for your kind reply and explanation.
I think that is exactly the problem as even sometimes switching between the apps that I have just opened is also so slow and the nexus lags badly....Yes, I am aware of the network lags, but the problem I was talking about does not have anything to do with it...I will try the command you said, but can I run it on stock rom? I have not yet rooted my nexus nor flashed a custom rom.
Thanks
arminvm said:
Thanks for your kind reply and explanation.
I think that is exactly the problem as even sometimes switching between the apps that I have just opened is also so slow and the nexus lags badly....Yes, I am aware of the network lags, but the problem I was talking about does not have anything to do with it...I will try the command you said, but can I run it on stock rom? I have not yet rooted my nexus nor flashed a custom rom.
You can do some investigation by watching the processes and seeing which are taking the CPU and memory on stock. The problem is, when you find out, there isn't much you can do about it.
Thanks
Click to expand...
Click to collapse
You can do some investigation by watching the processes and seeing which are taking the CPU and memory on stock. The problem is, when you find out, there isn't much you can do about it.
Its quicker and easier to just install a custom rom where this type of work has already been done for you. :victory:
Lately, I've discovered that loading Chrome immediately raises my CPU temp by 30+ degrees. Sometimes that's enough to make things run really slow
Yeah, I agree...I will try to fimd sometime amd go over flashing a custom rom. ??
Yes! I habe noticed that these slow downs mostly happen when I am browsing in Chrome...
Web browsers are DEFINITELY a source of slowdowns.
The problem, more often than not, is actually *javascript* that is written by MORONS. Even on a desktop machine, you can watch the web browser for CPU and RAM utilization, and it just grows and grows and grows until you finally kill the process and start a new one.
What this may come down to is actually quite simple; the CPU in the Nexus 9 is actually more suitable for use as a stovetop than an actual CPU. These things get way too hot way too fast. If you beat on them with a web browser, they'll get hot and throttle down to low/verylow frequency, which will make them generally unresponsive. So if that is what is happening to you, there really end up being a few options to deal with it;
1) disable javascript in the browser,
2) don't use the browser,
3) improve the ability to disperse heat from the CPU.
For #3, you may note that when it gets hot, it is pretty localized to the corner of the device up near the power button. An easy solution to distribute heat better might be something simple, like adding a layer of copper foil to the inside of the back cover. The thicker the copper foil the better. Copper is very good at conducting heat, so this would spread the heat around over the entire area covered by that foil. http://www.ebay.com/itm/Copper-Foil...nductive-Adhesive-Ship-from-USA-/162018486132
I also found chrome was slow starting up, switching tabs etc. Found that logging out of my Google account in chrome improved this. Seems that synching tabs etc triggers the pause. This might be an acceptable workaround for some but I appreciate it isn't a great fix if you want to use that feature. Actually I'm not bothered as I think Google know too much anyway. �� But the underlying problem is this tablet... I don't have this problem on my phone.
doitright said:
Web browsers are DEFINITELY a source of slowdowns.
The problem, more often than not, is actually *javascript* that is written by MORONS. Even on a desktop machine, you can watch the web browser for CPU and RAM utilization, and it just grows and grows and grows until you finally kill the process and start a new one.
What this may come down to is actually quite simple; the CPU in the Nexus 9 is actually more suitable for use as a stovetop than an actual CPU. These things get way too hot way too fast. If you beat on them with a web browser, they'll get hot and throttle down to low/verylow frequency, which will make them generally unresponsive. So if that is what is happening to you, there really end up being a few options to deal with it;
1) disable javascript in the browser,
2) don't use the browser,
3) improve the ability to disperse heat from the CPU.
For #3, you may note that when it gets hot, it is pretty localized to the corner of the device up near the power button. An easy solution to distribute heat better might be something simple, like adding a layer of copper foil to the inside of the back cover. The thicker the copper foil the better. Copper is very good at conducting heat, so this would spread the heat around over the entire area covered by that foil. http://www.ebay.com/itm/Copper-Foil...nductive-Adhesive-Ship-from-USA-/162018486132
Click to expand...
Click to collapse
Yeah, they do get hot...and the browser is the problem, I agree...however, I think they are not the main reason...there is something wrong with low memory or maybe some apps...
astralbee said:
I also found chrome was slow starting up, switching tabs etc. Found that logging out of my Google account in chrome improved this. Seems that synching tabs etc triggers the pause. This might be an acceptable workaround for some but I appreciate it isn't a great fix if you want to use that feature. Actually I'm not bothered as I think Google know too much anyway. �� But the underlying problem is this tablet... I don't have this problem on my phone.
Click to expand...
Click to collapse
Haha, I agree...google already knows a lot!..thanks
arminvm said:
Yeah, they do get hot...and the browser is the problem, I agree...however, I think they are not the main reason...there is something wrong with low memory or maybe some apps...
Click to expand...
Click to collapse
I don't agree with that.
We use our N9's *all of the time*, and there is never any perceptible slowdown. Possibly with the exception of straining them with web browsers, but web browsers are... poopy... on EVERY platform and device, so that doesn't really stand out. Typically just minimize the use of web browsers and all is well.
Web browsers were good in 1996 when they were simple things to display an html website. Since then, they've added all kinds of useless crap to them that bloat them out, hog up tons of memory, and just generally make them into a useless waste of space.
doitright said:
I don't agree with that.
We use our N9's *all of the time*, and there is never any perceptible slowdown. Possibly with the exception of straining them with web browsers, but web browsers are... poopy... on EVERY platform and device, so that doesn't really stand out. Typically just minimize the use of web browsers and all is well.
Web browsers were good in 1996 when they were simple things to display an html website. Since then, they've added all kinds of useless crap to them that bloat them out, hog up tons of memory, and just generally make them into a useless waste of space.
Click to expand...
Click to collapse
I know..but everyone knows that N9 should be faster!...
Sent from my HTC One_M8 using XDA-Developers mobile app
Update:
I think I have kind of find the problem of low speed of my Nexus 9...I uninstalled an app that was for weather prediction and from that time on my Nexus 9 is very fast and responsive...No problem so far. I also uninstalled some other apps alogaide that which I was never using them,so I am not sure if the weather app was exactly the reason of the slow downs...but the other apps where just some games or some simple apps....well, I hope this information helps! Let me know your idea. Thanks everyone
Sent from my HTC One_M8 using XDA-Developers mobile app
Did a fresh install on my X1m3 and was quite surprised to find I could watch the battery life trickle down before my eyes despite a 4500 mAh battery. AccuBattery reports 96% estimated health, estimated capacity 4327 mAh, which is within acceptable tolerances, and I've just done a 0% to 100% charge to train the charge algorithm.
Even with 60 Hz mode on the screen and brightness between 40% and 50%, I still think battery drain is higher than it should be on the shipped Android 11 update. I have about 100 apps total, most of which are passive / load-then-close things (small utilities etc). Minimal social media apps, the usual IM apps. Nothing extravagant. SOT seems to literally bleed battery life and I've already had a few device overheat / service stop thermal protection / camera app shutdown warnings in just two days of use.
Is the Snapdragon 888 really that bad? Reviews I read prior indicated that while not stellar, the SOT and battery life in standard suites of usage tests showed that the device seemed broadly on par with most current gen handsets, give or take an hour or two.
Battery life at the moment only seems marginally better than my three year old S9 with about 80% battery health and severe screen-on drain (per AccuBattery and a separate Samsung diagnosis); that is to say, slightly disappointing. Does anyone else's experiences reflect this? Anything you did with a boxfresh device that improves its battery life from what I've experienced, or is this partly the woes of early Android 11 adoption?
Find the apks running in the background and deal with each on a case by case basis.
With internet/phone connected the drain should less than 1%@hr when not in use.
My 10+ with less efficient ram gets that with AOD on, but it was a battery guzzling hog before it was optimized.
blackhawk said:
Find the apks running in the background and deal with each on a case by case basis.
With internet/phone connected the drain should less than 1%@hr when not in use.
My 10+ with less efficient ram gets that with AOD on, but it was a battery guzzling hog before it was optimized.
Click to expand...
Click to collapse
Indeed, that's what I was expecting. I'm close to 1.7%/hr with screen off. When the screen's on, I can quite quickly decrement the battery just with it sat idling or with an empty Chrome window open.
I read elsewhere on xda that some Samsung users who upgraded to Android 11 were suffering from excessive drain in Chrome until they forcibly suspended it, is that a bug which was subsequently fixed or is there another reason behind that behaviour? Weird background sync issues?
I've gone through again tonight, disabling and force muting notifications from any apps I suspect to be hogs, and I've permission granted BBS through ADB to see if I can nail any more details. Unfortunately looks like BBS needs some work to be more compatible with Android 11 or the Xperia OS build.
christopherwoods said:
Indeed, that's what I was expecting. I'm close to 1.7%/hr with screen off. When the screen's on, I can quite quickly decrement the battery just with it sat idling or with an empty Chrome window open.
I read elsewhere on xda that some Samsung users who upgraded to Android 11 were suffering from excessive drain in Chrome until they forcibly suspended it, is that a bug which was subsequently fixed or is there another reason behind that behaviour? Weird background sync issues?
I've gone through again tonight, disabling and force muting notifications from any apps I suspect to be hogs, and I've permission granted BBS through ADB to see if I can nail any more details. Unfortunately looks like BBS needs some work to be more compatible with Android 11 or the Xperia OS build.
Click to expand...
Click to collapse
Be careful with the edits... dependencies.
Names can be deceiving. Make your own list and know exactly what you're disabling.
I prefer to use a Package Disabler as it gives you on the fly control. PM if you want a link for that (some knucklehead FM here thought I was a salesperson for posting the link).
Likely suspects; any cloud apk, Google play Services, Google backup Transport, Framework and Google Firebase. Playstore is another one that constantly pecks away at the battery.
Clear system cache, Google play Services, Transport and Framework data.
Try disabling Google play Services at night see what that does. It kills a lot of birds with one stone. Normally unless I need to use one of it's dependencies, I leave it disabled.
Go through -all- the Google settings. Disable Google, carrier, app and Sony feedback. Use Karma Firewall to lock down apps that don't need internet access. Set Gmail to manual sync.
Use the setting below to kill ads globally.
Sheesh, if I have to stop/delete/uninstall/disable all this stuff I might as well go back to a land line with an answering machine. I mean didn't he say he has 100 apps? What in the world are 100 apps used for? How long has he actually had the phone in his possession? Maybe a few days are needed to let the battery settle down? Instead of stopping all the so-called necessary Google stuff, why not stop/uninstall about 90 apps and see how it goes?
That is not normal. Battery life is solid for me and have minimal drain. Try resetting and see if phone is like that with no apps installed for a day
jaseman said:
Sheesh, if I have to stop/delete/uninstall/disable all this stuff I might as well go back to a land line with an answering machine. I mean didn't he say he has 100 apps? What in the world are 100 apps used for? How long has he actually had the phone in his possession? Maybe a few days are needed to let the battery settle down? Instead of stopping all the so-called necessary Google stuff, why not stop/uninstall about 90 apps and see how it goes?
Click to expand...
Click to collapse
Each user and Android device is unique.
So is its optimization.
This is no plain Jane iPhone.
You get what you put into Android.
That's why kids do so well with them... they play with it.
jporter396 said:
That is not normal. Battery life is solid for me and have minimal drain. Try resetting and see if phone is like that with no apps installed for a day
Click to expand...
Click to collapse
Unless you have uninstallable malware or did a major firmware update a factory reset doesn't find the root cause. Meaning it's likely to reoccur.
It's preferable to find and correct the cause... and you learn this way.
Running in Safe mode will give a good idea if it's a 3rd party app causing the issue.
Occasionally poorly written apps will change hidden settings not normally accessible to the user. These will remain even if you uninstall it.
If you can't find (sometimes reloading the app and changing the setting there, then uninstalling it works) and correct, factory reset.
Meh, never load a bunch of unknown apps at once. Load, observe, then decide if it's doing what you want.
Make installable copies of all your trusted apps for future use and archive them. Sooner or latter you will need those...
blackhawk said:
Each user and Android device is unique.
So is its optimization.
This is no plain Jane iPhone.
You get what you put into Android.
That's why kids do so well with them... they play with it.
Click to expand...
Click to collapse
Well, I understand that...this is not my first cell phone, and I usually do NOT have all the issues so many others have. And when I ask myself WHY??? I can only conclude that my 25 years as a Systems Engineer certainly helps, as well as the fact that I use my cell phone primarily as a communications device...you know as they were originally intended. But I also do a number of other things such as banking, internet access, mapping, etc., etc. However, I highly doubt that the problem with overheating, or rapid battery drain is attributable to Google's services (though once in awhile a rogue update can cause problems) but rather the problem inevitably lies with all the 3rd party apps that many load up on their phones. Another leading contributor is not setting the phone up properly out of the box. A recommendation that I always offer when setting up a new phone is this: NEVER allow Google to reinstall all your apps from a backup! NEVER!!!
Just bite the bullet and install them from scratch yourself! This way you are getting a CLEAN/Pristine start! Windows has allowed "upgrades" from one OS to another for years, and while you may have no real problems on your home PC, doing an upgrade on a server will get you fired! That is a MAJOR no-no. Why not, when it would save so much time and effort? Because you are dragging all the detritus left over form the previous version into a new build. Then, if and when problems arise, and they certainly will, you may NEVER be able to determine the cause! Now if this happens on your phone the worst thing is to do a factory reset - YUK - but it's not the end of the companies business, or your livelihood! Try to do this on a server that has already been deployed and I would rather get a root canal without Novocain while actively charged electrodes were anchored to my feet!
So then, NEVER allow Google to reinstall your apps from a backup. Start clean, learn what to turn off/adjust in settings, and load your apps one at a time. Give your battery a few days to settle in, that is to learn your habits of use and you should be OK. YMMV
jaseman said:
Well, I understand that...this is not my first cell phone, and I usually do NOT have all the issues so many others have. And when I ask myself WHY??? I can only conclude that my 25 years as a Systems Engineer certainly helps, as well as the fact that I use my cell phone primarily as a communications device...you know as they were originally intended. But I also do a number of other things such as banking, internet access, mapping, etc., etc. However, I highly doubt that the problem with overheating, or rapid battery drain is attributable to Google's services (though once in awhile a rogue update can cause problems) but rather the problem inevitably lies with all the 3rd party apps that many load up on their phones. Another leading contributor is not setting the phone up properly out of the box. A recommendation that I always offer when setting up a new phone is this: NEVER allow Google to reinstall all your apps from a backup! NEVER!!!
Just bite the bullet and install them from scratch yourself! This way you are getting a CLEAN/Pristine start! Windows has allowed "upgrades" from one OS to another for years, and while you may have no real problems on your home PC, doing an upgrade on a server will get you fired! That is a MAJOR no-no. Why not, when it would save so much time and effort? Because you are dragging all the detritus left over form the previous version into a new build. Then, if and when problems arise, and they certainly will, you may NEVER be able to determine the cause! Now if this happens on your phone the worst thing is to do a factory reset - YUK - but it's not the end of the companies business, or your livelihood! Try to do this on a server that has already been deployed and I would rather get a root canal without Novocain while actively charged electrodes were anchored to my feet!
So then, NEVER allow Google to reinstall your apps from a backup. Start clean, learn what to turn off/adjust in settings, and load your apps one at a time. Give your battery a few days to settle in, that is to learn your habits of use and you should be OK. YMMV
Click to expand...
Click to collapse
I've played with my 10+ extensively*.
My issues and solutions may not apply to you.
No free rides; you get what you put into it.
WYSIWYG.
Enabling power management of any kind isn't needed, will likely cause erratic behavior degrade the speed and stability in extreme cases even cause boot loops. On my device global power management uses more battery even after a week or more... it does not adapt. It ain't Borg.
Can you really expect a random collection of apks, services and versions to be compatible out of the box? Absolutely not. The shotgun approach will not work well here. Sweat is always the price of freedom...
Developer options>standby apps
All buckets should show as active and their status unchangable, otherwise power management is active.
*factory resets should be only after major firmware updates, malware you can't eliminate, system damage by a app and boot loops *giggle*.
Otherwise track down the root cause and correct otherwise it will likely reoccur... then you'll be right back were you started. The equivalent of rinsing with the wash water.
blackhawk said:
Each user and Android device is unique.
So is its optimization.
This is no plain Jane iPhone.
You get what you put into Android.
That's why kids do so well with them... they play with it.
Click to expand...
Click to collapse
jeez...."plain Jane iPhone"...that's right, there's not a single setting you can change on the iPhone
Morning all. My pixel 6 (non pro) is being delivered today and I've been looking through the forum, as I always do for a new phone, to try and see what recommendations people have. Despite seeing lots of issues in the 'press' with battery life and Android 13 (downgrading / bricking), I can't see what the general consensus is here and peoples experiences seem to differ.
Is upgrading to Android 13 worth it? Does it actually fix the battery life issues?
Thanks in advance for any advice.
Just look here reddit
Best way is make a clean, fresh install - flash.android.com
carlo497 said:
Just look here reddit
Best way is make a clean, fresh install - flash.android.com
Click to expand...
Click to collapse
Socialist media sites here are frowned upon.
Plus the site rules say so...
carlo497 said:
Just look here reddit
Click to expand...
Click to collapse
Reddit? Where 90% of problems are user-made. Not a good advice especially when you are in a forum where specialist are really here to help.
Cheers
thermomonkey said:
Morning all. My pixel 6 (non pro) is being delivered today and I've been looking through the forum, as I always do for a new phone, to try and see what recommendations people have. Despite seeing lots of issues in the 'press' with battery life and Android 13 (downgrading / bricking), I can't see what the general consensus is here and peoples experiences seem to differ.
Is upgrading to Android 13 worth it? Does it actually fix the battery life issues?
Thanks in advance for any advice.
Click to expand...
Click to collapse
Intermediate level rooter/phone tinkerer here. First thing I did when getting my P6 was to unlock, upgrade to A13, and root, so I have no context for what A12 was like. What I can say is battery life has been amazing for me. Albeit I am not a heavy user (only play COD mobile every once in a blue moon). Most of the time it's just phone, text, browser, music and YouTube use. I am actually testing the battery right now, and I am at 27% since unplugging at 100% 40 hours ago, so I am completely happy. On pace to be a 2 day battery for me. YMMV.
In regards to how I like A13, I am coming from A11 on a Oneplus device, and I have to say I miss the old style quick toggles personally. But I am also one that doesn't mind getting used to new software. I know this can annoy others quite a bit. The rest of the OS issues I have are not version related, they are me missing OxygenOS features like screen gestures to play/pause music, turn on flashlight, modify status bar icons, ect. I really miss them, but have turned my back on Oneplus due to their recent decisions (constant lack of IP ratings, no wireless charging, removing the alert slider, constant price creep, subpar cameras) so the only easy to root alternative that addresses my above frustrations is the Pixel line.
That being said, any Pixel you buy brand new is gonna start with A12, which is very close to A13. So again, YMMV with how you acclimate to the new OS version.
Hope this helps
Also, the fingerprint reader on this phone is way better than the one on my Oneplus 8T, that thing was absolute garbage IMO...like 30-40% success rate. This P6 one is completely satisfactory for me, rarely have a failure. When I do, it's usually due to moisture or dirt. But any in screen reader has these issues, not isolated to P6. Only solution is to have a physical reader like the Sony Xperia or the like.
I know I probably seem like the minority here, it seems most people have horrible experiences with the P6 reader, just saying me personally it has been great. Also, my above great experience is WITH a tempered glass protector on and have NOT increased the touch sensitivity like the instructions seem to indicate a need for.
centifanto said:
Intermediate level rooter/phone tinkerer here. First thing I did when getting my P6 was to unlock, upgrade to A13, and root, so I have no context for what A12 was like. What I can say is battery life has been amazing for me. Albeit I am not a heavy user (only play COD mobile every once in a blue moon). Most of the time it's just phone, text, browser, music and YouTube use. I am actually testing the battery right now, and I am at 27% since unplugging at 100% 40 hours ago, so I am completely happy. On pace to be a 2 day battery for me. YMMV.
In regards to how I like A13, I am coming from A11 on a Oneplus device, and I have to say I miss the old style quick toggles personally. But I am also one that doesn't mind getting used to new software. I know this can annoy others quite a bit. The rest of the OS issues I have are not version related, they are me missing OxygenOS features like screen gestures to play/pause music, turn on flashlight, modify status bar icons, ect. I really miss them, but have turned my back on Oneplus due to their recent decisions (constant lack of IP ratings, no wireless charging, removing the alert slider, constant price creep, subpar cameras) so the only easy to root alternative that addresses my above frustrations is the Pixel line.
That being said, any Pixel you buy brand new is gonna start with A12, which is very close to A13. So again, YMMV with how you acclimate to the new OS version.
Hope this helps
Click to expand...
Click to collapse
Thanks for your replies, much appreciated. Can I ask why you root? I used to routinely do this many years ago and infact did it recently to my Poco F2 bit that was purely to enable call recording. I find the lack of being able to properly use banking apps / Google pay too big a price to pay.
I've not got my sim card in yet so using WiFi only. My phone seems to be getting quite hot? Not doing much very intensive, just downloading and installing apps. It's been off a few minutes now and it's still warm. Battery drain also seems a little high albeit I've been downloading lots of programmes.
thermomonkey said:
Thanks for your replies, much appreciated. Can I ask why you root? I used to routinely do this many years ago and infact did it recently to my Poco F2 bit that was purely to enable call recording. I find the lack of being able to properly use banking apps / Google pay too big a price to pay.
I've not got my sim card in yet so using WiFi only. My phone seems to be getting quite hot? Not doing much very intensive, just downloading and installing apps. It's been off a few minutes now and it's still warm. Battery drain also seems a little high albeit I've been downloading lots of programmes.
Click to expand...
Click to collapse
Absolutely! Reasons I root:
1. Adaway - block all ads system wide,
2. Vanced YouTube - block YT ads, extra customization like swipe controls
3. Did I mention I HATE ads with white hot passion??
4. Tasker root required modifications
5. Ability to nuke any bloat app I want
6. Call recording
7. Other Magisk modules that I have used in the past but have not tried/not supported on A13 yet.
8. I just personally like having control over software I use. Any future mod I could possibly desire I would have the access required to implement
No concern with apps blocking you due to rooting, that is fixed by USNF and Zygisk denylist
In my experience, anytime I am setting up a new phone they get warm. Also to note, these newer builds of Android require about 5-7 day "break in" period, where the OS is optimizing based on your usage. After that period is when battery life settles down.
If I'm not mistaken with the P6/P6P once you upgrade to A13, you cannot downgrade back to A12. So something to consider.
centifanto said:
Absolutely! Reasons I root:
1. Adaway - block all ads system wide,
2. Vanced YouTube - block YT ads, extra customization like swipe controls
3. Did I mention I HATE ads with white hot passion??
4. Tasker root required modifications
5. Ability to nuke any bloat app I want
6. Call recording
7. Other Magisk modules that I have used in the past but have not tried/not supported on A13 yet.
8. I just personally like having control over software I use. Any future mod I could possibly desire I would have the access required to implement
No concern with apps blocking you due to rooting, that is fixed by USNF and Zygisk denylist
In my experience, anytime I am setting up a new phone they get warm. Also to note, these newer builds of Android require about 5-7 day "break in" period, where the OS is optimizing based on your usage. After that period is when battery life settles down.
Click to expand...
Click to collapse
Thanks!! Sorry for my slow reply.
Just FYI, Vanced works without root and surprisingly, so does call recording.
Interesting about the USNF though, I was unaware of that and wondered how people lived without access to all the banking type apps.
centifanto said:
2. Vanced YouTube - block YT ads, extra customization like swipe controls
Click to expand...
Click to collapse
What vanced are you using?
palopaxo said:
What vanced are you using?
Click to expand...
Click to collapse
Take a look at AfterVanced on Reddit
thermomonkey said:
Interesting about the USNF though, I was unaware of that and wondered how people lived without access to all the banking type apps.
Click to expand...
Click to collapse
USNF for me isn't about the banking apps but tap and pay. I could give two s***s about the banks, as if I really needed to I could just access their services through the browser. I like the convenience of tap and pay, not going to lie, but can function without it easily enough, as I do carry my cards on me in a Ridge-style wallet even though I have the phone as an option. You never know when Google will suddenly update the Wallet or GPay apps and cause the USNF to not work for a few days.
thermomonkey said:
Morning all. My pixel 6 (non pro) is being delivered today and I've been looking through the forum, as I always do for a new phone, to try and see what recommendations people have. Despite seeing lots of issues in the 'press' with battery life and Android 13 (downgrading / bricking), I can't see what the general consensus is here and peoples experiences seem to differ.
Is upgrading to Android 13 worth it? Does it actually fix the battery life issues?
Thanks in advance for any advice.
Click to expand...
Click to collapse
I just got a Pixel 6 myself a couple weeks ago after being an iPhone user for a few years. I have to say I haven't really put it through the wringer yet, but so far I've had zero issues with it. Nothing like I've seen discussed at length in multiple threads on Reddit.
My biggest issue thus far is trying to figure out what browser to use, as I have the freedom to actually choose.
novafluxx said:
I just got a Pixel 6 myself a couple weeks ago after being an iPhone user for a few years. I have to say I haven't really put it through the wringer yet, but so far I've had zero issues with it. Nothing like I've seen discussed at length in multiple threads on Reddit.
My biggest issue thus far is trying to figure out what browser to use, as I have the freedom to actually choose.
Click to expand...
Click to collapse
I like Brave Browser, Firefox, or Chromium.
Glad to hear no issues with the 6.
I'm holding out for the 7.
However my 5 is still running like a champ.
andybones said:
I like Brave Browser, Firefox, or Chromium.
Click to expand...
Click to collapse
I read that Firefox for Android isn't as secure as on desktop. I'm finding Brave to be pretty great though. I've got issues with it on desktop but I don't really need it in desktop as I have Firefox and ublock origin.
novafluxx said:
I just got a Pixel 6 myself a couple weeks ago after being an iPhone user for a few years. I have to say I haven't really put it through the wringer yet, but so far I've had zero issues with it. Nothing like I've seen discussed at length in multiple threads on Reddit.
My biggest issue thus far is trying to figure out what browser to use, as I have the freedom to actually choose.
Click to expand...
Click to collapse
I use Opera on my P6. Blocks ad and is smoother than Chrome (which I suppose most browser are).
Back to the original topic, I can't really comment on the difference between 12 and 13, but I can say my experience on 13 has been good. No notable issues, excellent battery life, and support from Magisk addons like AOSP Mods is catching up.
Just make sure you know what you're doing if you do upgrade to 13, especially if you're a root user. TL;DR - the phone has two "slots" for everything but data (bootloader, system, etc.), and flashing the OTA of 13 updates one of those slots. After that happens, if anything happens that causes your phone to boot from the un-updated side before you've updated at least the bootloader on that side, you've got a brick. There are guides around for getting both sides updated that're better than I can, though the rootless (sideload) method for updating both sides can have issues with USB >2.0.