I've had some problems with really long lags (few seconds to bring up the home screen etc.) after using my phone for a few days without rebooting, and noticed the memory usage is very high - the system is often using 700 mb or so, with the kernel being 500 mb of that. This is much higher than the ~150 mb on my Nexus 7 on 6.0
Are other people having this issue or seeing such high memory usage by the kernel? Any ideas on what could be causing this or how to fix it?
I'm on stock firmware, version
24.11.18.victra_tmo
and the kernel version is
3.4.42-g389e46b
Thanks!
Could anyone else on stock MM let me know their kernel memory usage (settings -> memory -> memory by app -> Android OS) and kernel version (settings -> about phone), and maybe uptime as well (for comparison)?
Trying to just see if this is normal or if i should try a factory reset or OS reinstall....
Thanks!
It's 130MB in the last 3hours
ice20978 said:
Could anyone else on stock MM let me know their kernel memory usage (settings -> memory -> memory by app -> Android OS) and kernel version (settings -> about phone), and maybe uptime as well (for comparison)?
Trying to just see if this is normal or if i should try a factory reset or OS reinstall....
Thanks!
Click to expand...
Click to collapse
My kernel usage is at 352 mb with about 12 hours uptime. The kernel version 3.4.42-ga9982b3-00002-g389e46b.
Related
i have a motorola droid and it is rooted.i flashed a new rom and then i flashed sprecovery,i let it run its course and i disconnected the phone.when the phone turns on it starts up and then a red light comes on and my phone says please connect charger.it keeps saying android process is not responding and then the phone shuts itself off.ive tried to boot it into recovery mode and do a restore,it keeps giving me an error that says nandroid exited with status 20 and its also not reading my sd card.can somebody tell me whats happened and if it can be fixed???please and thank you
Well, seems as if you need to reflash or restore because of bad flash. If you try flashing again make sure you wipe data and cache. As far as not reading sdcard I have same problem not sure why but when I'm in recovery and I choose install zip which I used clockworkmod recovery, if it fails then it reboots automatically after couple seconds not sure if this happens with sprecovery. After sdcard mount fail it shuts down and reboots so before it reboots I pull the battery and wait a minute or two before trying again. It may take me 3 to 4 times of doing this but eventually it will mount sdcard in recovery. I recommend keep trying till it allows you to apply recovery file and then flash to either clockworkmod or sprecovery which ever one you not using and then flash back to the one you want. I'd also recommend try if after all this you flash rom again and same thing happens redownload it and try again. Good luck.
Sent from Droid using, Sapphire v1.0.0/ 928Droid Black Glass 2.2 Theme/ Sholes 1.0 Ghz 7 Slot Kernel.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
fadimck said:
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
[*]Auto Kill Level --> Safe
[*]Auto Kill Frequecny --> Every One Hour
[*]Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Click to expand...
Click to collapse
Okay, I didn't know this info as I've Milestone with stock OS 2.1
Sent from my Milestone using XDA App
Picture tells everything , 2-3 days ago there is some "android OS" draining my battery like hell...over night when phone is in sleep mode it went from 100 to 10% any fix ??
Uploaded with ImageShack.us
Try this:
System settings - applications - Applications - (rider) ALL software update - "delete data"option.
Wifi police to Sllep when screen off
Enable debugging Modus
If thi sdon't work take Chainfires Kernel
Bangdoo said:
Try this:
System settings - applications - Applications - (rider) ALL software update - "delete data"option.
Wifi police to Sllep when screen off
Enable debugging Modus
If thi sdon't work take Chainfires Kernel
Click to expand...
Click to collapse
can't find this "(rider) ALL software update - "delete data"option."
I am current on supercurio kernel and juwe 2.3.3
System settings - applications - Applications - (rider) ALL -- software update - "delete data"option.
You must go to Apllications then All then srearch for Software update and than delete data
Bangdoo said:
System settings - applications - Applications - (rider) ALL -- software update - "delete data"option.
You must go to Apllications then All then srearch for Software update and than delete data
Click to expand...
Click to collapse
ok did will see results thx m8
And? it's better now?
Bangdoo said:
And? it's better now?
Click to expand...
Click to collapse
No i still got that problem...when i put on charger its get normal and use 3% battery for some time and then get back again ~70% and drain battery over night...
For most people,this kind of sudden battery drains have disappeared after a few cycles of charge/discharge,maybe 5 or 6?
maybe you should recallibrate your battery.
here the link:
http://forum.xda-developers.com/showthread.php?t=1024867
it worked! just recalibrate ur battery and the OS prozess is again under 5%
support the guy!
thank you I'll try it
Hi guys, im having same problem, Android OS uses the most battery of all processes, but it is in use only when screen is off. Drain is about 1% / 3 minutes! I had it before on JVK but i fixed it by cleaning dalvik cache. Now on JVB nothing works. I tried to clear dalvik cache, deleted ota update apps, cleaned cache partition, fixed permissions, deleted batterystats, changed kernel, turned off autostart for most apps and the battery drain is still there, even after reboot
I'm on Juwe's Smart Edition 4.1 with DamianGTO beta 6 kernel. Please help.
Hey, Recalibration really worked out in such problem. Thank you, very much.
I just installed this JB rom (Evervolv Jellybean w/ nightly builds) and now some apps that I could move on 2.3.7 Is not possible anymore (like WhatsApp)
What's wrong? What should I do?
I have some apps that I could before, now I'm unable, the button stays disabled.
Thanks
saulob said:
I just installed this JB rom (Evervolv Jellybean w/ nightly builds) and now some apps that I could move on 2.3.7 Is not possible anymore (like WhatsApp)
What's wrong? What should I do?
I have some apps that I could before, now I'm unable, the button stays disabled.
Thanks
Click to expand...
Click to collapse
In terms of running apps off of an sd-ext partition, I've found that my best results so far have been using the Mounts2SD script instead of the built in A2SD solution. The settings I have for mine are:
Current Status:
-------
* Mounts2SD [loaded]
- Apps []
- Data [loaded]
- Dalvik []
- CmDalvik [loaded]
- Cache [loaded]
- SWAP []
- RMount [loaded]
The performance has been pretty good, totally useful for daily driver. Best thing about using the reverse mount (RMount) is that you get a more accurate # when looking at free internal memory in System Settings -> Storage.
There are other folks out there using different options.. those other options gave me a WAY higher Quadrant score but the system really seemed sluggish so I've setting on this.
As a new user i cannot post in the right topic.
This is about frequent reboots and ram issues.
This is my last_kmsg-log.txt which i generated adb shell cat /proc/last_kmsg > last_kmsg-log.txt
after a reboot not sure if it says anything interesing
My reboots happen quite often, also the RAM under settings in working apps grows a bit each minute. Now its about 80 MB
Phone history:
0) updated to stock 4.3
1) Unlocked
2) flashed kernel
3) recover apps from copy -> stock backup app
If you need anything else feel free to write.
Rafus
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english