Trying to debug an issue with my N10. Possibly started with 4.3 but I cannot confirm this.
After about a day of use my N10 becomes laggy with apps restarting and very low available memory. Everything restarts indefinitely including the keyboard and whatever controls the navigation soft keys (they stop working). Sometimes I am able to get into a terminal and look at the list of processes with "ps".
What I find is there are MANY instances of "system_server". Somewhere near 10 or so instances. I wont pretend to know what it does but this is always consistent when my N10 becomes unstable. The quickest way to get my N10 to be stable again is by killing the process with "kill" and the process ID. This causes an extremely fast soft reboot starting with the nexus logo.
Other notes:
I suspect that only one of the system_server processes is actually active and the rest are just memory leaks that should have been closed. This is because I can kill several of these processes without the system rebooting but the second that I restart one that is in use...BAM.
It interesting that, prior to 4.3, my N10's performance slowly degraded until it restarted. With 4.3, my N10 is very fast and fluid up until the point of failure (apps begin to restart). Which is probably OK if I just remember to restart my N10 every night.
4.3 was installed via the TWRP with a factory reset.
So....has anyone else experience something similar? Is this new with 4.3 or has always been one of the possible many memory leaks with this tablet?
bntran02 said:
Trying to debug an issue with my N10. Possibly started with 4.3 but I cannot confirm this.
After about a day of use my N10 becomes laggy with apps restarting and very low available memory. Everything restarts indefinitely including the keyboard and whatever controls the navigation soft keys (they stop working). Sometimes I am able to get into a terminal and look at the list of processes with "ps".
What I find is there are MANY instances of "system_server". Somewhere near 10 or so instances. I wont pretend to know what it does but this is always consistent when my N10 becomes unstable. The quickest way to get my N10 to be stable again is by killing the process with "kill" and the process ID. This causes an extremely fast soft reboot starting with the nexus logo.
Other notes:
I suspect that only one of the system_server processes is actually active and the rest are just memory leaks that should have been closed. This is because I can kill several of these processes without the system rebooting but the second that I restart one that is in use...BAM.
It interesting that, prior to 4.3, my N10's performance slowly degraded until it restarted. With 4.3, my N10 is very fast and fluid up until the point of failure (apps begin to restart). Which is probably OK if I just remember to restart my N10 every night.
4.3 was installed via the TWRP with a factory reset.
So....has anyone else experience something similar? Is this new with 4.3 or has always been one of the possible many memory leaks with this tablet?
Click to expand...
Click to collapse
Same issue on my nexus 10. New system_servers keep spawning, making the device lag. As a temp fix you can manually kill all but the one with the lowest PID.
Another note to add is that the spawning of system_server is sudden and not gradual. This makes me think that something, perhaps a buffer, fills up after a day of use which starts the spawning
Does anybody knows if there is already a topic for this in official google's forums? if not, How can we create a report of this or what is the proper process to formally do it?
1. anybody care to try their hand at writing a script that kills all system_server processes except the one with the lowest PID?
2. is anyone else using Greenify? I'm starting to think this app does more harm than good on 4.3. when the app is disabled, Android will properly free up memory after a few hours of non-use. I go from about 200 MB free back to about 530MB. with Greenify active, this never happens, making the memory leakage problem happen WAY earlier than it normally would.
nalf38 said:
1. anybody care to try their hand at writing a script that kills all system_server processes except the one with the lowest PID?
Click to expand...
Click to collapse
I was thinking about that, but I'm not sure exactly how someone would do it. I have no doubt it's possible though.
Sent from my Nexus 10 using Tapatalk 4
Matthileo said:
I was thinking about that, but I'm not sure exactly how someone would do it. I have no doubt it's possible though.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
It's probably basic bash scripting, if the ps command has switches to output the pids of one particular process name (or use grep to parse the output of PS), and then it's just a matter writing a simple if/then loop. maybe I'll figure something out when I have time.
nalf38 said:
1. anybody care to try their hand at writing a script that kills all system_server processes except the one with the lowest PID?
2. is anyone else using Greenify? I'm starting to think this app does more harm than good on 4.3. when the app is disabled, Android will properly free up memory after a few hours of non-use. I go from about 200 MB free back to about 530MB. with Greenify active, this never happens, making the memory leakage problem happen WAY earlier than it normally would.
Click to expand...
Click to collapse
Using Greenify but in my Nexus 4 with 4.3, working well as always.
rootusr said:
Does anybody knows if there is already a topic for this in official google's forums? if not, How can we create a report of this or what is the proper process to formally do it?
Click to expand...
Click to collapse
It would either be http://code.google.com/p/android or the Android product forums. Not sure which.
Edit: https://code.google.com/p/android/issues/detail?id=58664
Star the issue and add relevant info, including logs.
Matthileo said:
It would either be http://code.google.com/p/android or the Android product forums. Not sure which.
Edit: https://code.google.com/p/android/issues/detail?id=58664
Star the issue and add relevant info, including logs.
Click to expand...
Click to collapse
Thanks!
I can't reproduce this here. Would someone please be so kind to provide a logcat, an complete output of the systems ps (not the one from busybox) and perhaps an output of dmesg?
nvertigo67 said:
I can't reproduce this here. Would someone please be so kind to provide a logcat, an complete output of the systems ps (not the one from busybox) and perhaps an output of dmesg?
Click to expand...
Click to collapse
I will but it might take a while. I flashed the unofficial CM10.2 a day ago and haven't had the issue come back yet. Perhaps it's a problem with stock 4.3. Once I have adequately tested that the issue doesn't exist in CM10.2 then i'll flash back to stock to find the logcat but this may take a week depending on weather or not the problem even exists.
bntran02 said:
I will but it might take a while. I flashed the unofficial CM10.2 a day ago and haven't had the issue come back yet. Perhaps it's a problem with stock 4.3. Once I have adequately tested that the issue doesn't exist in CM10.2 then i'll flash back to stock to find the logcat but this may take a week depending on weather or not the problem even exists.
Click to expand...
Click to collapse
Even if the issue exists in CM Google will ignore logs from custom roms
Sent from my Nexus 10 using Tapatalk 4
---------- Post added at 01:43 PM ---------- Previous post was at 01:38 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it looks like when the device starts to lag.
---------- Post added at 02:04 PM ---------- Previous post was at 01:43 PM ----------
Alright, I'm using Tasker to execute this code every hour as root.
Code:
pgrep system_server |awk 'NR >= 2' | xargs -n1 kill
So far it seems to kill the spare processes, without hurting the initial one.
WARNING: This could be very bad for your system to kill these processes. I have no idea to tell you the truth. I just added this myself so I don't know if it works yet.
Matthileo said:
Even if the issue exists in CM Google will ignore logs from custom roms
Sent from my Nexus 10 using Tapatalk 4
---------- Post added at 01:43 PM ---------- Previous post was at 01:38 PM ----------
This is what it looks like when the device starts to lag.
---------- Post added at 02:04 PM ---------- Previous post was at 01:43 PM ----------
Alright, I'm using Tasker to execute this code every hour as root.
Code:
pgrep system_server |awk 'NR >= 2' | xargs -n1 kill
So far it seems to kill the spare processes, without hurting the initial one.
WARNING: This could be very bad for your system to kill these processes. I have no idea to tell you the truth. I just added this myself so I don't know if it works yet.
Click to expand...
Click to collapse
I will have to try that later. Thanks!
Matthileo said:
---------- Post added at 02:04 PM ---------- Previous post was at 01:43 PM ----------
[/COLOR]Alright, I'm using Tasker to execute this code every hour as root.
Code:
pgrep system_server |awk 'NR >= 2' | xargs -n1 kill
So far it seems to kill the spare processes, without hurting the initial one.
WARNING: This could be very bad for your system to kill these processes. I have no idea to tell you the truth. I just added this myself so I don't know if it works yet.
Click to expand...
Click to collapse
I was just thinking of something. The leak appears to happen pretty quickly. So an hourly timed trigger may not work if the leak occurs right after the script is ran. Then you'll have apps restarting for 59 minutes until the script is ran again. Perhaps it should be modified to run when memory is low.
bntran02 said:
I was just thinking of something. The leak appears to happen pretty quickly. So an hourly timed trigger may not work if the leak occurs right after the script is ran. Then you'll have apps restarting for 59 minutes until the script is ran again. Perhaps it should be modified to run when memory is low.
Click to expand...
Click to collapse
That might be a good idea
Sent from my Nexus 10 using Tapatalk 4
bntran02 said:
I will but it might take a while. I flashed the unofficial CM10.2 a day ago and haven't had the issue come back yet. Perhaps it's a problem with stock 4.3. Once I have adequately tested that the issue doesn't exist in CM10.2 then i'll flash back to stock to find the logcat but this may take a week depending on weather or not the problem even exists.
Click to expand...
Click to collapse
To be honest: if the problem does not exists in cm - stay with it. If the problem is fixable in non proprietary code I'm glad. Google is not intrested in supporting n10. The cm and aokp people (and lots of other developers) are happy supporting n10. So let us help them in eliminating theses issues...
So: don't flash back to stock to hunt this Issue down, but post a process table if it appears in whatever costum rom you choose. But please send a processtable with ppids, memory sizes and all the nice infos and not this colotful screenshots - they missing to much infos... Thanx.
It happens on factory image as well
I think this is the reason my homescreen starts redrawing itself after using any other app if the device hasn't been rebooted in the past 12-24 hours. I was just thinking about this and then I bumped on the thread on reddit.
I am not 100% sure system_server processes are the main issue. I've been diligently killing them, and they stopped duplicating after a few hours. Fast forward 24 hours later and I'm still out of memory with apps dying that absolutely should not die, like Google Keyboard.
Related
Hi all,
So, this problem appears common on other phones as well, and appears to be a Gingerbread issue. Drilling down further using Watchdog Lite on the phone, it appears to be a process called Suspend causing the high CPU usage.
There are a few threads on this:
http://code.google.com/p/android/issues/detail?id=11126#makechanges
http://code.google.com/p/android/issues/detail?id=15057
http://forum.xda-developers.com/showthread.php?p=10004299&posted=1#post10004299
http://forums.t-mobile.com/t5/myTouch-4G/quot-suspend-quot-linux-process/m-p/605813
Personally, I'm getting pretty terrible battery life out of my S2, and I can confirm that in the Battery Status menu, Android OS appears extremely high at around 40% (a friends Nexus has this sitting at around 2%).
Not sure there's much we can do about it but wait and hope for a fix from Samsung (or Google)... People are reporting that rebooting the phone can help, but it's only temporary.
Anyway, just something to check if you're having issues.
+1 second that.
Android os eats the most of the battery
Reboot helps temporarily.
Sent from my GT-I9100 using XDA Premium App
My os is at 79% i have no idea whats going on? but i am running launcher pro plus?
OK. So now we have identified an "issue".
Could you guys post juiceplotter logs while phone is asleep and draining, and while in use?
For asleep, i mean literally not touching it for half an hour. On, just occasional tap to keep screen on.
What we are after is an idea of what is causing system to use the power. Can we compare configurations of push email etc, to see if anything differs?
Are we rooted? Etc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is a screen print of my usage.
How do you do the log thing ?
http://imageshack.us/photo/my-images/59/sc20110509160954.jpg/
pulser_g2 said:
OK. So now we have identified an "issue".
Could you guys post juiceplotter logs while phone is asleep and draining, and while in use?
For asleep, i mean literally not touching it for half an hour. On, just occasional tap to keep screen on.
What we are after is an idea of what is causing system to use the power. Can we compare configurations of push email etc, to see if anything differs?
Are we rooted? Etc
Click to expand...
Click to collapse
Hi mate,
I rooted my phone yesterday, but I don't think that's a cause as it was just as bad before. In fact I rooted it just so I could freeze some apps
At the moment, I only have my google account set to sync (calendar, mail, contacts), and I have gmail pushing through emails.
All the stock Samsung apps are frozen. No widgets are running (I'm trying to run it fairly barebones to see how long I can get out of it).
I don't have juiceplotter installed, I'll look into that. I do have Watchdog though, and from all the other threads on this issue the problem seems to be the Suspend process (confirmed by a Google employee).
I don't think there's much we can do aside from wait for a fix. The problem appears to have been around since at least September last year.
I had this the first few days I had the phone, my battery was being wiped out in hours.
I formatted both my mem cards and hard reset. Since then my battey life has been amazing (got through the whole day yesterday only using 25% battery), and os use has dropped to about 18% (still a bit high but better than 40%).
Same issue here, both new flashed roms and my own slim roms suffer from same issue. I have a look tonight if i can find any solution.
simonk83 said:
Hi mate,
I rooted my phone yesterday, but I don't think that's a cause as it was just as bad before. In fact I rooted it just so I could freeze some apps
At the moment, I only have my google account set to sync (calendar, mail, contacts), and I have gmail pushing through emails.
All the stock Samsung apps are frozen. No widgets are running (I'm trying to run it fairly barebones to see how long I can get out of it).
I don't have juiceplotter installed, I'll look into that. I do have Watchdog though, and from all the other threads on this issue the problem seems to be the Suspend process (confirmed by a Google employee).
I don't think there's much we can do aside from wait for a fix. The problem appears to have been around since at least September last year.
Click to expand...
Click to collapse
OK. I will see if I can think of anything, as I remember we fixed a similar issue when popping 2.1 onto it, when some binary was giving us trouble...
Root or no root don not affect this issue. Only time i dont get it: fresh flash of new rom without anything installed.
Same issue here and I rooted freezing load of Apps but still drain
*edit*
It seems to stop drain when using reboot the phone.. not yet confirmed just a speculation... Btw these processes eat a lot of battery never got these problems on sgs1 custom gingers rom
Sent from my GT-I9100 using Tapatalk
Seem that ginger on SGS 2 has this bug present:
http://phandroid.com/2011/03/04/android-2-3-3-gingerbread-update-killing-nexus-one-battery-life/
Did anyone tried this? I had a similar issue with Gingerbread on SGS1 and it was fixed after clearing the data for System Update.
http://forum.xda-developers.com/showthread.php?t=1021711
Haven't encountered the problem yet with pretty heavy use plus a few resets. It's probably a specific app or settings that you're turning on/using after each hard reset that causes it.
I'm still on the original firmware though, haven't flashed a new one yet. Might be related.
this is not universal, i don't have this problem. sgs 2 rooted with insecure kernel by chainfire.
*subscribing*
I also have the same drain issue. I have the S2 setup exactly the same way my Captivate was, and the battery life isn't the same.
I got better results after disabling background data in accounts ans sync (settings)
More testing ongoing.
DocRambone said:
I got better results after disabling background data in accounts ans sync (settings)
More testing ongoing.
Click to expand...
Click to collapse
Not really relevant I think - all Android users are going to have background data enabled in accounts and sync. Mine is enabled without the issue, anyway. I am only syncing a single gmail account though.
Have you tried what the linked thread recommends - going into manage applications and clearing data for the update system? You might want to try clearing data for all of the android system tasks.
RyanZA said:
Not really relevant I think - all Android users are going to have background data enabled in accounts and sync. Mine is enabled without the issue, anyway. I am only syncing a single gmail account though.
Click to expand...
Click to collapse
Yes, but this 2.3.3 bug eat 5-10% battery/h in idle!... so all solutions is good.
I tried a number of "solutions", none helped. The background data seems to help
MaelstromXC said:
Did anyone tried this? I had a similar issue with Gingerbread on SGS1 and it was fixed after clearing the data for System Update.
http://forum.xda-developers.com/showthread.php?t=1021711
Click to expand...
Click to collapse
I just tried this, gonna charge to 100% then unplug it and let juiceplotter run to see what happens. Also I have the Samsung account app frozen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Smooth like Butta
Follow on G+: Team Vanir
Vanir Team:
NuclearMistake
Sonicxml
DHO
PrimeDirective
Not all features are available yet.
Features:
Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android with subtly improved versions of the features you love to as many devices as possible. we've tried to incorporate and improve our features in a way that makes them more cohesive to improve the overall user experience while correcting any performance regressions and improving functionality..
What to expect:
- This is not a McCopy ROM. What goes into our build is well thought-out and not a bunch of stuff duck taped together because we could.
- maximum optimization. We do our research. We test hard. We build -fstrict -O3 globally and include a massive array of code optimizations and memory leak fixes that we write ourselves and eventually submit to AOSP or Linaro.
- originality in our source. We generate a lot of new commits being features or general code improvements. We are open source to share and improve the community but we also try to make sure we offer a unique experience.
- aesthetics.. hopefully in your opinion
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
UI and graphics improvements
custom navbar, navring, and hardware key features
improved notification handling (active display & halo are in review also)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
yatta yatta yatta
more to come when i feel like updating the op
Changelog:
**Vanir Open Status
**Vanir Merged Status
Vanir Downloads (nuclearmistake):
**Nightlies
Recovery Downloads:
**TWRP 2.7
**CWM
Vanir Github:
**VanirAOSP Git
Gapps:
**4.4.2 PA Gapps
Installation Instructions
Make sure your using twrp above it's required
Full wipe
Install ROM
Install Gapps
Thanks
TeamVanir
Meticulus
Everyone here for keeping me inspired
Too many to thank. You know who you are who stood by since day 1
Reserved
Awesome Job Unjustified Dev! Another New Great ROM to add to the list. It's definitely smooth like butter! Thank you!
Sent from my SGH-T599X using XDA Premium 4 mobile app
Thanks for this ROM which someone can fix the BT audio in call but thanks I will use this one I like thanks again
Sent from my SGH-T599N using xda app-developers app
Tethering
Nice to see a few ROMs for the T599! I am testing on the T599 T-Mobile variant.
Maybe there is an issue with Bluetooth.
Bluetooth tethering is not working.
But, WiFi tethering is working fine. :good:
Installed smoothly once I updated CWM. Will post on how it goes from here.
ps That's a bad ass boot image lol
Edit: Not a fan of how you put Vanir over the space bar, but I guess it doesn't matter because I'm not going to be using the stock keyboard anyway.
Edit2: Phone seemed to turn off randomly in the middle of the night, other than that it's working great so far.
Edit3: The music app combined with DSP Manager is pretty neat. If the music is distorting, the music app will pause to avoid damaging your system.
Edit4: Screen recording completely freezes the phone.
Kennehisftw said:
Installed smoothly once I updated CWM. Will post on how it goes from here.
ps That's a bad ass boot image lol
Edit: Not a fan of how you put Vanir over the space bar, but I guess it doesn't matter because I'm not going to be using the stock keyboard anyway.
Edit2: Phone seemed to turn off randomly in the middle of the night, other than that it's working great so far.
Edit3: The music app combined with DSP Manager is pretty neat. If the music is distorting, the music app will pause to avoid damaging your system.
Edit4: Screen recording completely freezes the phone.
Click to expand...
Click to collapse
Screen recording doesn't work on these devices. I am removing the option that shows that to prevent device freezing.
I've redone the device tree and device is now codinalte. I made this change so that the assert checks won't allow flashing of older recoveries which would lead to device bootloops if used with the new j4fs and param setup.
Make sure you see the new instructions.
Changelog
-Used gcc 4.8 instead of 4.7 now that it's been tested.
-Removed all device asserts to prevent use of older recoveries.
-Disabled the use of screen record
-Switched device name to codinalte to cause less confusion with ace 2 users
-Upstream Vanir changes
-Philz cwm , cwm , and twrp now available for codinalte enabled builds only
Excellent ROM
Sent from my SGH-T599N using XDA Premium 4 mobile app
To everyone wondering this is the initial release of codinalte. I made this change to ensure everyone would be on the correct recovery and if you are on an older one it wouldn't let you install it . It would cause a bootloop due to the mismatch of j4fs and param module. This is the only way I can think of to ensure everyone is safe.
Unjustified Dev said:
To everyone wondering this is the initial release of codinalte. I made this change to ensure everyone would be on the correct recovery and if you are on an older one it wouldn't let you install it . It would cause a bootloop due to the mismatch of j4fs and param module. This is the only way I can think of to ensure everyone is safe.
Click to expand...
Click to collapse
What bugs does this have other than the Bluetooth audio? Same as Omni Rom?
Cogra147 said:
What bugs does this have other than the Bluetooth audio? Same as Omni Rom?
Click to expand...
Click to collapse
Yes , we should all have the same bugs. The only ones that will make a difference are rom specific issues.
Unjustified Dev said:
Yes , we should all have the same bugs. The only ones that will make a difference are rom specific issues.
Click to expand...
Click to collapse
Here are some bugs I'd experienced recently with VanirAOSP ROM latest build.
1. Last night I had set my alarm clock to wake up this morning but the alarm didn't go off because I found my phone shutdown or powered off. Apparently the randomly shutdown in the middle of the night.
2. Yesterday I had two occasions where my Network was lost completely. I had to reboot the phone to get it back.
3. I noticed that when I receive a call or make a call the volume sounds like is half way down. I always have my volume set all the way up. When someone calls me I have to hit the volume down one or twice and then back up to fix the loudness of the call. Something is not right.
4. I noticed that when ever I play and embedded YouTube Video whether in a Browser of any kind or an RSS Reader it FCs the application before the video starts. All the time. Here is an example. I recorder this LogCat for you....https://www.dropbox.com/s/aaf7wgywrf66b7a/2014-03-17-14-15-24.txt I try playing a YouTube video on this website.. http://sploid.gizmodo.com/here-are-7-facts-about-superheroes-you-probably-didnt-1541767101 on the AOSP Browser and same thing happens with other Browsers and apps with YouTube Video embedded in them.
Sent from my SGH-T599N using XDA Premium 4 mobile app
DJVargas said:
Here are some bugs I'd experienced recently with VanirAOSP ROM latest build.
1. Last night I had set my alarm clock to wake up this morning but the alarm didn't go off because I found my phone shutdown or powered off. Apparently the randomly shutdown in the middle of the night.
2. Yesterday I had two occasions where my Network was lost completely. I had to reboot the phone to get it back.
3. I noticed that when I receive a call or make a call the volume sounds like is half way down. I always have my volume set all the way up. When someone calls me I have to hit the volume down one or twice and then back up to fix the loudness of the call. Something is not right.
4. I noticed that when ever I play and embedded YouTube Video whether in a Browser of any kind or an RSS Reader it FCs the application before the video starts. All the time. Here is an example. I recorder this LogCat for you....https://www.dropbox.com/s/aaf7wgywrf66b7a/2014-03-17-14-15-24.txt I try playing a YouTube video on this website.. http://sploid.gizmodo.com/here-are-7-facts-about-superheroes-you-probably-didnt-1541767101 on the AOSP Browser and same thing happens with other Browsers and apps with YouTube Video embedded in them.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could try this for low call fix http://forum.xda-developers.com/showthread.php?t=2676518
Use the onlyincallfix.apk it should work to fix volume please confirm this.
The video problem is due to the patches we used not supporting a certain function required for the video playing. The phone randomly dying is something i know nothing about as of yet.
Does it work on the international version and does it have random reboots like in the latest CM11?
LMH1998 said:
Does it work on the international version and does it have random reboots like in the latest CM11?
Click to expand...
Click to collapse
This is not for s3 mini. Please wait some time for me do a test build. I don't have the s3 mini but it's a similar device. If you want I can send you a pm of the test build. Please continue this conversation in a private message.
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
wilbigdaddy2000 said:
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
Click to expand...
Click to collapse
I am looking into it. I haven't noticed why it did that yet. I can add back dvfs limit if you think it's the voltage. Basically you won't be able to use performance control it will stay at 0 for min and max.
Unjustified Dev said:
I am looking into it. I haven't noticed why it did that yet. I can add back dvfs limit if you think it's the voltage. Basically you won't be able to use performance control it will stay at 0 for min and max.
Click to expand...
Click to collapse
wilbigdaddy2000 said:
Phone died overnight even though on charger. I believe its the performance function. Installed voltage control. Still testing. Will post results.
Sent From DWil's Magic Carpet t599n
Click to expand...
Click to collapse
The same thing happened to me, but while running Beanstalk. I have been running Vanir for the past few days and I have not seen any issues with FC or reboot yet. Battery life appears to be excellent, lasting 48 + hours with light use.
I am running the T-Mobile variant.
Wakelocks are the bane of battery life and ever since stock rom, there has been a single wakelock that for the life of my I couldn't shake.
Diagnostic.Client.Wakelock !!!!
This wakelock is brought up everytime in ROM threads only to be buried with answers such as drain your battery to empty and reboot, that fixes it!!!111
However the issue runs deeper. Remember the controversy a few years ago about spy software on our phones? Does carrier IQ ring a bell?
Ever since stock rom, as well as any derivations of the stock rom, I've always seen this wakelock with hundreds of wakes. No amount of googling helped until this week, when I stumbled on another thread about Carrier IQ. Our Note 3 has Carrier IQ in it and it's the source of Diagnostic.Client.Wakelock. Innocent looking name for a wakelock huh?
However the fix for it is quite simple really, remove any Android OS calls to any carrier IQ libraries/frameworks. Instructions:
1) You need Root.
2) Download System Tuner from the play store. I can't link urls as a new user but the play store link should contain this "details?id=ccc71.pmw"
3) In System Tuner go to "App Manager".
4) At the bottom filter your Apps by "System".
5) Find "Android System" in the list, and press "Open" at the bottom.
6) Choose "Details"
7) Go to the "Activities" tab and uncheck the following:
Code:
com.carrieriq.iqagent.service.ui.UserPage
com.carrieriq.iqagent.service.ui.ShowMessage
com.carrieriq.iqagent.stdmetrics.survey.android.QuestionnaireLaunchActivity
com.carrieriq.iqagent.stdmetrics.survey.android.QuestionnaireActivity
8) Go to the "Receivers" tab and uncheck the following:
Code:
com.carrieriq.iqagent.service.BootCompletedReceiver
com.carrieriq.iqagent.service.receivers.EnableTogglelmpl
9) Go to the "Services" tab and uncheck the following:
Code:
com.carrieriq.iqagent.service.IQService
10) Reboot your phone.
You will never see Diagnostic.Client.Wakelock ever again. It's been 3 days for me and I'm on Firenote ROM and I dont see this wakelock showing up anymore. And the battery difference is very noticable. No more 1% drain while screen is off.
If you found this advice helpful consider buying me a coffee: Bitcoin Address: 1MXubhXjxCNGxzTLpRttgr6w1YWXQeo5ei
BONUS: If you want to cleanup after Carrier IQ consider removing its library files from /system. Voodoo Carrier IQ can tell you where they are located and deleting them gave me no problems: As a new user I cant link so google: "org.projectvoodoo.simplecarrieriqdetector"
Just curious what Firmware are you currently on with your AT&T Note 3 ?
I've read alot about Carrier IQ and there tracking way's and there company still denies what the software is truly intended to do..But nonetheless it's a invasion of privacy and I like your post...
I'm currently on 4.4.2 Dynamic Kat 3.2 and I did download Voodoo's app to verify if Carrier IQ exist...When I ran the test it came up with 0 hits (NO Carrier IQ)...Which is no where to be found in this Rom, But I used this app before on other devices and found it...
View attachment 2792180
I'm using FireNote ROM v? not sure if it was version 7,8 or 9. Doesn't matter, because it's still a derivation from the stock rom, and I remember staying on Stock ROM for the longest time and not being able to get rid of this wakelock.
I don't know where 4.4.2 Dynamic Kat 3.2 originally was derived from, but if it was derived from stock rom, then odds are it will have traces of Carrier IQ. AFAIK tablet roms such as XNote should be free from Carrier IQ, because cell phone service providers only wanted to monitor your phone use and data mine your activity.
While Carrier IQ may not be fully active in the sense of sending actual data back to whomever designed it, it's still active as far as running on your system, hence the wakelock. Not to mention what kind of a bogus wakelock is called Diagnostics? Diagnostics of what, my mileage or disk space, or tethering use???
The easiest way to check for Carrier IQ is to run some of these Carrier IQ detection apps, OR manually browse the /lib folder for carrier IQ ".so" files. For the ROM I was on (FireNote), I found two .so files named carrier IQ:
DO NOT DELETE THESE FILES. SOME USERS ARE REPORTING A SOFT BRICK. However I assume booting into recovery you can readd these files from another rom.
Code:
/system/lib/libiq_client.so
/system/lib/libiq_service.so
Again it all depends on where your ROM was derived from, if stock, then yes you probably have it.
Edit:
Dynamic Kat is a stock THEMED Kit Kat rom based on the international build NC2.
Click to expand...
Click to collapse
Probably because the ROM is an international ROM and not US based, explains why there is no carrier IQ. WTF USA???
Thanks for the find. I have been experiencing this wakelock since the OTA in Jan/Feb. I had great battery life before the OTA. I tried almost all of the custom roms in this forum. The only one that did not produce these wakelocks was X-Note. I had assumed that result because it was an international rom. I also liked FireNote but got the wakelock.
This fix should let me try out AT&T stock based roms now.
Again, thank you very much.
Scanned my phone and it looks like the official KitKat is infected with Carrier IQ, but it's not active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My awake time hasn't gone down significantly, but I'm getting more battery with the tweaks from OP.
Yeah since the root cause of Diagnostic.Client.Wakelock is coming from Carrier IQ, the only roms affected by it should USA based roms meant for cellphones. International roms or roms ported from tablets should not have this issue.
Although I haven't installed any KitKat roms it makes sense that it contains it, and also that XNote which was ported from a tablet does not have this issue.
I just used this instruction last night and no more battery drain from client wakelock. Thx op
Sent from my SAMSUNG-SM-N900A using Tapatalk
Any way to help this wakelock op?
AudioOut_2
Sent from my SAMSUNG-SM-N900A using Tapatalk
Netrunner157 said:
Yeah since the root cause of Diagnostic.Client.Wakelock is coming from Carrier IQ, the only roms affected by it should USA based roms meant for cellphones. International roms or roms ported from tablets should not have this issue.
Although I haven't installed any KitKat roms it makes sense that it contains it, and also that XNote which was ported from a tablet does not have this issue.
Click to expand...
Click to collapse
Yeh, I give you credit Netrunner157...Not many users are even aware of this wakelock....Good Find Bro.. :good:
Very strange...I used several apps to detect "Carrieriq" Every app I tried said there were NO TRACES Of this wakelock (Spyware)...But I decided to use your method and look through "System Tuner" and sure enough it's there...I posted a pic above showing no traces...But it's inaccurate for me..Because it exist in the Android System...See pic below...
View attachment 2799625
wish777 said:
Very strange...I used several apps to detect "Carrieriq" Every app I tried said there were NO TRACES Of this wakelock (Spyware)...But I decided to use your method and look through "System Tuner" and sure enough it's there...I posted a pic above showing no traces...But it's inaccurate for me..Because it exist in the Android System...See pic below...
View attachment 2799625
Click to expand...
Click to collapse
Indeed. The System Tuner software shows how stealthy the CarrierIQ software is, hiding within the main Android System process. I am quite glad to have it deactivated. Nasty piece of garbage.
Also don't delete the libiq because if you do and restart the phone it will get stuck on the att logo
Sent from my AT&T Galaxy Note 3
Beware
Wish I saw that already. Now I'm soft bricked and rocking the touch pro 1 again
Ilkinansr92 said:
Also don't delete the libiq because if you do and restart the phone it will get stuck on the att logo
Sent from my AT&T Galaxy Note 3
Click to expand...
Click to collapse
These tips were fantastic! I was on the NC2 bootloader so I just was able to have root yesterday. I applied these changes re-booted and then guess what, it indicates that I am now custom. LOL! BFD! Thanks for the tips, much appreciated!
jhollow3 said:
Wish I saw that already. Now I'm soft bricked and rocking the touch pro 1 again
Click to expand...
Click to collapse
Just pull the lib files from a zipped ROM put them on microSD card go to recovery mount system and go to advanced file manager and copy the files over then fix permissions
Sent from my AT&T Galaxy Note 3
Heh, I actually posted this back in may and in a reddit thread, after finding out about the carrier IQ process in the LG G2 forums.
http://forum.xda-developers.com/showpost.php?p=52807274
Not only did it get rid of the wakelocks, but I no longer have GPS disconnect issues.
Synapse777 said:
Not only did it get rid of the wakelocks, but I no longer have GPS disconnect issues.
Click to expand...
Click to collapse
Are you by any chance using the Xposed Disable Location Constent module? I occasionally lose GPS while using maps, and have to toggle GPS on/off/on from the QuickTiles occasionally and I wasn't sure what that was related to.
So Carrier IQ was probably polling for GPS and breaking it?
What other tweaks do you have for removing other wakelocks, or other improvements? It's good to see people researching the same issues that one can solve.
Now for some reason System Tuner can't open my Android System process...
Anyone have any ideas about that?
Very Nice!!!!!....Thanks a lot!!...Usually my battery drain is higher overnight..if I leave it at 90% before sleep I used to have 50% in the morning. I applied this wake lock fix and slept with 61% baattery and in the morning I still see 55%...Woww!!...I have almost 100 apps installed
Rcv'd back from S-off service June 9.
Root-happy app uninstalling since.
Old firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I broke it.
Thoughts? Ideas?
Forgive me.
I thought folks were on 1.30.xxx or even higher by now.
And my battery life is pathetic.
And i keep getting notifications about having connected to my home network without ever leaving the house, I get good signal clear to my car.
Many things to love about HTC 10. A number of things... not so much.
I don't understand your problem. Looks like your phone has the most recent Verizon OTA already.
I swear, I thought I read that a 1.30.xxx was available.
You're right, it appears I have the latest from Verizon.
I thought the newer versions I must have imagined (or maybe other carriers released) would solve all my stock HTC 10 woes.
I sincerely apologize to the forum for my version oversight. I expected to have another OTA by now, restoring my confidence in my flagship phone's ability to function as one would expect.
Don't go by software version numbers for OTA's; the numbers are for internal control, not external tracking. Currently the Verizon 10 is on 1.19.605.22. The 605 means Verizon (Spring is 651). The Unlocked and I believe possibly the Sprint versions are at 1.80 or something. As a sometimes software and hardware tester for HTC I can assure you, the numbers don't mean anything. I see issues with my later test builds that I never see on my retail handset, and the OTA's don't come down until the carriers have approved them, long after HTC is done building and testing.
hgoldner said:
Don't go by software version numbers for OTA's; the numbers are for internal control, not external tracking.
...
As a sometimes software and hardware tester for HTC I can assure you, the numbers don't mean anything.
...
the OTA's don't come down until the carriers have approved them, long after HTC is done building and testing.
Click to expand...
Click to collapse
I appreciate your advisement.
Why am I not surprised that carriers drag their feet to push valuable updates while urgently putting more bloatware and spyware on my phone...
pidzero said:
I appreciate your advisement.
Why am I not surprised that carriers drag their feet to push valuable updates while urgently putting more bloatware and spyware on my phone...
Click to expand...
Click to collapse
Every Verizon 10 owner, whether rooted or not, should go into Settings--> App Manager and DISABLE DTIgnite. It's nothing but a bloatware engine. Disable it, remove whatever bloatware you can (or disable it) and you will be rid of it. I disable: Verizon Cloud; Verizon Navigation; CallerID and DTIgnite. I confess, I prefer Messages+ over the default messaging app.
hgoldner said:
Every Verizon 10 owner, whether rooted or not, should go into Settings--> App Manager and DISABLE DTIgnite. It's nothing but a bloatware engine. Disable it, remove whatever bloatware you can (or disable it) and you will be rid of it. I disable: Verizon Cloud; Verizon Navigation; CallerID and DTIgnite. I confess, I prefer Messages+ over the default messaging app.
Click to expand...
Click to collapse
Already annihilated DTIgnite in every way I could find. Man, it was stubborn! I've disabled all Verizon apps except "My Verizon Mobile", instead stripping it of every permission.
I use Signal as my default messaging app, as recommended by Edward Snowden himself! lol
I literally ripped out every bit of software I don't use/need. The default mail app, Zoe, NFL Mobile, Visual Voicemail, all the Amazon apps, the list goes on. Battery has been so poor, however, I thought maybe I broke it.
I unplugged 40 minutes ago and i went from 100% to 94% in that time.
Any idea what app populates /data/system/dropbox ? i found files there logging practically all usage. i have since emptied the folder and changed its permissions so that "system" user no longer had access.
adding that my remedy seems to have worked, and no weird errors have presented themselves
pidzero said:
Already annihilated DTIgnite in every way I could find. Man, it was stubborn! I've disabled all Verizon apps except "My Verizon Mobile", instead stripping it of every permission.
I use Signal as my default messaging app, as recommended by Edward Snowden himself! lol
I literally ripped out every bit of software I don't use/need. The default mail app, Zoe, NFL Mobile, Visual Voicemail, all the Amazon apps, the list goes on. Battery has been so poor, however, I thought maybe I broke it.
I unplugged 40 minutes ago and i went from 100% to 94% in that time.
Any idea what app populates /data/system/dropbox ? i found files there logging practically all usage. i have since emptied the folder and changed its permissions so that "system" user no longer had access.
Click to expand...
Click to collapse
Well, I'd like to actually use the phone, so I don't go quite so far. Zoe I keep active, My Verizon I keep to monitor data usage, Visual Voicemail is now free and actually useful; Amazon apps are definite battery sucks but can be tamed. I didn't to into the way you can fix permissions using App Manager....that was not the point of the earlier post. I'm relatively content with my battery life, but I also run a custom kernel.
hgoldner said:
I'm relatively content with my battery life, but I also run a custom kernel.
Click to expand...
Click to collapse
I didn't know you could have a custom kernel on stock ROM.
I'm patiently waiting for CM13. A thread was created to promote its development http://forum.xda-developers.com/showthread.php?t=3410009
pidzero said:
I didn't know you could have a custom kernel on stock ROM.
I'm patiently waiting for CM13. A thread was created to promote its development http://forum.xda-developers.com/showthread.php?t=3410009
Click to expand...
Click to collapse
Sure, why not? If you're bootloader unlocked and rooted, go for it. Elemental X 0.6 is the last version for the current retail firmware. The later version(s), I think it's up to 0.9, are for the 1.8x base. I wouldn't run it on Verizon until post whenever the OTA drops.
hgoldner said:
Sure, why not?
Click to expand...
Click to collapse
I lack a proper education of how the software actually works at that level in a *nix-like environment, especially Android.
I have intermediate experience with *nix. I've set up DHCP servers and Apache servers, SMB servers and proxy servers. I use CLI or GUI, on x86, x64, and RPi (arm). Rarely, if ever, have I required modifying the kernel of an installation. Not since compiling Gentoo completely from source 10 years ago.
I would benefit from a "for dummies" video when it comes to the many aspects of low-level Android customization.
pidzero said:
I lack a proper education of how the software actually works at that level in a *nix-like environment, especially Android.
I have intermediate experience with *nix. I've set up DHCP servers and Apache servers, SMB servers and proxy servers. I use CLI or GUI, on x86, x64, and RPi (arm). Rarely, if ever, have I required modifying the kernel of an installation. Not since compiling Gentoo completely from source 10 years ago.
I would benefit from a "for dummies" video when it comes to the many aspects of low-level Android customization.
Click to expand...
Click to collapse
Well, there are plenty of threads on XDA for that. Bottom line is that once the devices are unlockable, some developers like to cook ROMs, others like to do kernels, still others focus on recoveries. If you stick around long enough, you recognize developers who move from device to device the same way users will through time. The developer of Elemental X kernel, @flar2 is a long-time kernel developer who has done solid work in the past, so I have absolute faith in running his kernels on my handset. The Elite kernel developer, @buckmarble, is also a great kernel developer.
I wouldn't presume to write or code myself. The most I ever do is put things in or take them out of custom ROMs before flashing, but lately I have stuck with stock ROMs until devices are "end of life," (which is why I'm running a custom ROM on my One Max, and will soon probably have to flash a custom ROM to my Nexus 7 FHD). And now that you can run Xposed without modifying system, I can do many of the mods that custom ROMs do.
Well, that was easy.
Elemental X 0.06 has been installed.
I'll report back on battery in a little bit.
changing kernels had no effect on the battery drain. still discharging just as quickly.
Hi,
Since I purchased it, my new Moto G5 Plus started acting weird at times, usually once a day with the battery getting nearer to 30%. RAM Usage shoots up, reaching critical levels quickly, and making the phone literally unusable. Only a reboot fixes the issue, and the phone gets as snappy as usual once this is done.
I was lucky enough to screenshot the RAM usage just before the reboot. Two times of three, due to the RAM issue, the screenshot wouldn't even get saved, or it would get covered by FC messages.
I'm aware of how Android RAM management works, I know that unused ram is wasted ram, but this is beyond any limit and does not need any clarification or dismission. Is it a problem of the firmware, the phone, or the OS in general? The model is the European (compass-less, with NFC) 32 GB/3GB variant, bootloader unlocked without root (just booted in TWRP without flashing once, but the issue was present before). Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just got the US 32gb/2gb variant today. I'll keep an eye on the memory and let you know if i see anything. Nothing yet but would expect it more on my lower memory model. Not sure how much variance there really are in these devices yet either.
Sent from my Moto G (5) Plus using Tapatalk
Hello mate! I'm facing a same problem even after flashing a NPN25.137-35 ON 3GB indian Varaint! Hope Motorola will figure out and fix this in next update! Pls see my thread : https://forum.xda-developers.com/g5-plus/help/ram-usage-apps-t3582585
Same issue on NA retail version. Frustrating.
I'm experiencing the same issue on my freshly reinstalled NA potter stock ROM.
After doing some research, it seemed that for some G5+ owners out there, enabling automatic night mode in System UI Tuner was the cause of the excessive RAM usage and lag. There's a reddit thread about this called moto_g5_plus_ram_issue but I am unable to post link.
Unfortunately, that was not the root cause for my phone, since I never enabled that feature. I even found it, enabled it, and disabled it just to make sure. Still having to reboot phone at least once a day when it reaches 3.4/3.6 GB RAM usage. Otherwise, the lag causes the phone to be unusable.
2 GB variant here, no issues.
I usually close recent apps too, but i guess you did so too and the ram usage is still high..
I get 80% RAM usage and 704MB free RAM, leaving the system using only 642MB and the apps 517MB. So there is a problem in your device, have you tried custom ROM's? Or you may prefer staying stock in case you have to send your device to repair.
Also, at least in my variant, there is no "Automatic NIght Mode" in system UI tuner, not in stock at least
Qwilava said:
Hi,
Since I purchased it, my new Moto G5 Plus started acting weird at times, usually once a day with the battery getting nearer to 30%. RAM Usage shoots up, reaching critical levels quickly, and making the phone literally unusable. Only a reboot fixes the issue, and the phone gets as snappy as usual once this is done.
I was lucky enough to screenshot the RAM usage just before the reboot. Two times of three, due to the RAM issue, the screenshot wouldn't even get saved, or it would get covered by FC messages.
I'm aware of how Android RAM management works, I know that unused ram is wasted ram, but this is beyond any limit and does not need any clarification or dismission. Is it a problem of the firmware, the phone, or the OS in general? The model is the European (compass-less, with NFC) 32 GB/3GB variant, bootloader unlocked without root (just booted in TWRP without flashing once, but the issue was present before). Any ideas?
Click to expand...
Click to collapse
I'm experiencing this too. Android OS is the app that is the problem. It takes up a freaking 2GBs of RAM!
Thanks for your reply. I do try to keep recent apps cleaned up periodically, but yes, this has been an issue since I bought the phone. I watch Android OS go from 800 MB of RAM usage at first reboot up throughout the day to 2.7 GB, until there's about 200 MG free RAM. That's when the lag hits and phone sometimes spontaneously reboots.
I did actually try flashing the unofficial Lineage 15.1 ROM, but my SIM (Sprint) wasn't recognized when I booted, so I shied away from messing with it further. Still pretty new at this. Might try again when I feel up to redoing phone. Haven't been able to use TWRP to make a backup because it doesn't see the internal SD card, so would have to start over completely...
M1810 said:
2 GB variant here, no issues.
I usually close recent apps too, but i guess you did so too and the ram usage is still high..
I get 80% RAM usage and 704MB free RAM, leaving the system using only 642MB and the apps 517MB. So there is a problem in your device, have you tried custom ROM's? Or you may prefer staying stock in case you have to send your device to repair.
Also, at least in my variant, there is no "Automatic NIght Mode" in system UI tuner, not in stock at least
Click to expand...
Click to collapse
No such thing here. The only 3 apps I keep running are Chrome, WhatsApp and XDA. I do occasionally use other apps but I swipe them when I'm done with them. Here are some screenshots.
PS: If you're wondering why my nav bar buttons are closer, that's coz I used the OP5T nav bar mod which was posted in XDA news a couple of days ago, no root needed tho
Swiping away unneeded apps helps, but RAM was still overused overnight
Hey psychopac, since your post, I have started being much more diligent than before about swiping away apps that I'm done using. It has made a noticeable difference, so thank you. The phone's been lag free.
However, there still seems to be a problem with RAM usage when I'm not actively maintaining it. Last night, I went to sleep with about 750 MB of free RAM, but this morning it dropped back down to 165 MB. I just had Hangouts, Messages, Settings, and Firefox in recent apps open.
For now I'll keep on swiping away apps, since it's much easier to do that than to mess with another ROM or reboot when it lags too badly.
psychopac said:
No such thing here. The only 3 apps I keep running are Chrome, WhatsApp and XDA. I do occasionally use other apps but I swipe them when I'm done with them. Here are some screenshots.
PS: If you're wondering why my nav bar buttons are closer, that's coz I used the OP5T nav bar mod which was posted in XDA news a couple of days ago, no root needed tho
Click to expand...
Click to collapse
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
Okay, so another tip. I have disabled some Google apps that I don't use. They include: Duo, Google Play Movies & TV, Motorola Notifications (the recently added one) and Google app (search).
And one important one which a lot of people might not agree with but it should make a difference on low RAM devices. Out of the three apps I most commonly use, instead of pressing home button, I press back key till I'm on the home. What (I think) that does is it closes the app and frees some memory if not all taken by that app. Now I may be wrong here. Please feel free to correct me. But if that's how it really works, then you can save just a bit more battery than when you keep all the apps that you actively use in the background by pressing home button to minimize all go directly to home without pressing back.
Again, feel free to correct as I may be wrong. Or not? But personally, that's what I do. Some of you may think that what I do closes the app and when I switch back to it, it reloads again which some may think is equal to swiping away an app and opening it again after some time so that it reloads everything from the ground up instead of picking up from where you left off when you just press home button and that app goes into the background but is still working and resumes from the point where you left when you open it again.
So,
1. I always close all the tabs when I'm not using chrome.
2. I always close XDA app (not XDA labs) by pressing back till I'm on the homescreen also because it's better this way as whenever I open it, it loads up new info so I don't have to refresh everything.
You can also see which apps are using exactly how much memory but going into the Settings>Apps>Your app>Memory and keep a check
Opinions?
Hey psychopac, I've been trying your tips to use the back button to close out of the apps, then swiping apps away from recent, as well as disabled the system apps that I don't use.
Still reaching 97% RAM usage on a daily basis.
It looks like what is using the most RAM is Android OS. It will go up from 1.2 GB to 2.6 GB or higher over the course of the day. That seems to push the phone over the edge.
psychopac said:
Okay, so another tip. I have disabled some Google apps that I don't use. They include: Duo, Google Play Movies & TV, Motorola Notifications (the recently added one) and Google app (search).
And one important one which a lot of people might not agree with but it should make a difference on low RAM devices. Out of the three apps I most commonly use, instead of pressing home button, I press back key till I'm on the home. What (I think) that does is it closes the app and frees some memory if not all taken by that app. Now I may be wrong here. Please feel free to correct me. But if that's how it really works, then you can save just a bit more battery than when you keep all the apps that you actively use in the background by pressing home button to minimize all go directly to home without pressing back.
Again, feel free to correct as I may be wrong. Or not? But personally, that's what I do. Some of you may think that what I do closes the app and when I switch back to it, it reloads again which some may think is equal to swiping away an app and opening it again after some time so that it reloads everything from the ground up instead of picking up from where you left off when you just press home button and that app goes into the background but is still working and resumes from the point where you left when you open it again.
So,
1. I always close all the tabs when I'm not using chrome.
2. I always close XDA app (not XDA labs) by pressing back till I'm on the homescreen also because it's better this way as whenever I open it, it loads up new info so I don't have to refresh everything.
You can also see which apps are using exactly how much memory but going into the Settings>Apps>Your app>Memory and keep a check
Opinions?
Click to expand...
Click to collapse
5xonlineage said:
Hey psychopac, I've been trying your tips to use the back button to close out of the apps, then swiping apps away from recent, as well as disabled the system apps that I don't use.
Still reaching 97% RAM usage on a daily basis.
It looks like what is using the most RAM is Android OS. It will go up from 1.2 GB to 2.6 GB or higher over the course of the day. That seems to push the phone over the edge.
Click to expand...
Click to collapse
As you said it yourself that Android OS is using most of the RAM, at this point I'd do a reboot if I were you just to see if it helps or not. BTW, how much memory is Android OS taking? Are you on the latest 1st Jan Patch?
Reboot helps but not for long
psychopac said:
As you said it yourself that Android OS is using most of the RAM, at this point I'd do a reboot if I were you just to see if it helps or not. BTW, how much memory is Android OS taking? Are you on the latest 1st Jan Patch?
Click to expand...
Click to collapse
Rebooting helped but only for about 18 hrs. Android OS starts out using about 700 MB but goes up to at least 2.6 GB before the day is done. That's while closing apps and swiping them away...
I actually am back on Lineage 14.1 so didn't get to try the Jan patch. RAM usage is much better, hovering around 1.6 GB/3.6 GB.
5xonlineage said:
Rebooting helped but only for about 18 hrs. Android OS starts out using about 700 MB but goes up to at least 2.6 GB before the day is done. That's while closing apps and swiping them away...
I actually am back on Lineage 14.1 so didn't get to try the Jan patch. RAM usage is much better, hovering around 1.6 GB/3.6 GB.
Click to expand...
Click to collapse
I'm surprised that Android OS is taking almost more than half the entire RAM space. This is wierd because if you're actively maintaining your recent apps, this shouldn't happen at all