heya,
I have a Nexus One, with 2.2 FRF83. I've been using it for a few weeks, installed a few Apps etc.
I also have another Nexus One, that I just bought for a friend, it also has 2.2 FRF83, but it's a fresh factory restore.
I've noticed that her's appears snappier, for instance swiping through home screen, opening up apps, the zoom effects when you go to Applications etc.
Is it somehow possible to find out why exactly this slowdown is occurring? I know Android, with the way it handles memory management and background processes is suppose to be quite clever, and it shouldn't matter what you have installed/running. But would uninstalling apps help? Or is it a misbehaving app? Or some setting I've set?
The apps I have installed are:
ACV
Adobe Flash Player 10.1
Astrid Tasks
ASTRO
Athg2sms V1.2
Barcode Scanner
CadreBible
Calculator
ConnectBot
Credit Usage
DNS Lookup
Dropbox
Gesture Search
Go! Sydney
GPS Status
GTD Timer
handyCalc
Maps [brut]
Maps
Meebo IM
Memory
MyBackup Pro
OI Countdown
OI File Manager
OI Safe
Pkt Auctions eBay
Replica Island
Shopper
Shuffle
SMS Backup & Restore
SNesoid Lite
StopWatch
SuperGNES Lite
Swype
SystemPanel Lite
Terminal Emulator
TwitPic Share
URL Shortener
White Noise
Using SystemPanel Lite, I have
/system - 145Mb capacity, 24.9Mb available
/data - 196.3 Mb capacity, 92.9 Mb available
/cache - 95.0 Mb capacity, 92.8 Mb available
/mnt/sdcard - 3831.5 Mb available, 1138.9 Available
In my Active Applications list right now, I have
Amazon Mp3 - Background - 9.3 Mb
Android Live Wallpapers - Visible - 8.8 Mb
Camera - Background - 11.0 Mb
Clock - Background - 10.0 Mb
Gallery - Background - 11.6 Mb
Gesture Search - Service - 8.8 Mb
Google Mail - Background - 9.6 Mb
Google Voice - Background - 8.9 Mb
Market - Background - 10.8 Mb
Messaging - Background - 12.3 Mb
Music - Background - 8.6 Mb
My Uploads - Background - 8.8 Mb
News and Weather - Service - 10.5 Mb
OI Countdown - Background - 8.7 Mb
Settings - Background 0 14.2 Mb
Swype - Visible - 16.4 Mb
SystemPanel Lite - Foreground - 12.5 Mb
Twitter - Service - 13.5 Mb
Voice Search - Background - 8.8 Mb
I also have around 2000 SMSes, but I'm not sure why that would affect say, scrolling through Settings, or swiping through home screens.
Let me know if there's any other info I can provide.
Cheers,
Victor
Same here
I have the lagginess issue too. My start to get lag after few hours of use. My mflop is 1.0 and im on froyo 2.2. I tried to uninstall all the apps but still doesnt help. I also tried all the Rom and Kernal and still have to same issue. Hopefully someone can point us to the right direction. Its getting real frustating..
vjoom said:
I have the lagginess issue too. My start to get lag after few hours of use. My mflop is 1.0 and im on froyo 2.2. I tried to uninstall all the apps but still doesnt help. I also tried all the Rom and Kernal and still have to same issue. Hopefully someone can point us to the right direction. Its getting real frustating..
Click to expand...
Click to collapse
Oh man, 1 MFLOP, that's no good, and didn't think it was possible on the N1. Wipe and start over and you should be fine.
vjoom said:
I have the lagginess issue too. My start to get lag after few hours of use. My mflop is 1.0 and im on froyo 2.2. I tried to uninstall all the apps but still doesnt help. I also tried all the Rom and Kernal and still have to same issue. Hopefully someone can point us to the right direction. Its getting real frustating..
Click to expand...
Click to collapse
1 mflop @ linkpack? 2.1 has 3-4 i think and 2.2 should have 35-40.
I would also do a complete wipe and start from scratch.
watercool said:
1 mflop @ linkpack? 2.1 has 3-4 i think and 2.2 should have 35-40.
I would also do a complete wipe and start from scratch.
Click to expand...
Click to collapse
I wiped and start from scratch numerous times. When i first using it, it would get around 38-40 mflop. Then it would go down the drain from there. Sometime i can't reach 1 mflop. Hope i dont have a hardware issue.
My galaxy s uses 273 MB out 326 MB when no user applications are running. I have not killed any default running services.
Is this memory usage normal?
Yep, this is pretty much normal - give or take 20mb or so. Android isn't like windows with how it deals with "closed" applications
Instead of closing and free all the memory an app uses when you close it stupid it to an idle state, just in case you want to reopen it in a short time.
There are also a number of processes that are always running like mail, gmail, clock, calendar that are using your ram.
Sent from my GT-I9000 using XDA App
StuBouyer said:
Yep, this is pretty much normal - give or take 20mb or so. Android isn't like windows with how it deals with "closed" applications
Instead of closing and free all the memory an app uses when you close it stupid it to an idle state, just in case you want to reopen it in a short time.
There are also a number of processes that are always running like mail, gmail, clock, calendar that are using your ram.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for the reply
Hello Can anyone help me out about OOM. What could be a great setting of OOM from Kernel Tuner in sensation XL? Can OOM save me battery/speed up my phone? Im using KingCobra Build 9 ROM. Is anyone using the same too?
Still no response
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
best memory settings depend on your RAM
jeffkian06 said:
Hello Can anyone help me out about OOM. What could be a great setting of OOM from Kernel Tuner in sensation XL? Can OOM save me battery/speed up my phone? Im using KingCobra Build 9 ROM. Is anyone using the same too?
Click to expand...
Click to collapse
I don't have much knowledge of these settings, but I tried the "Multitasking 512" profile, as my mobile phone's RAM is 512 MB and it seems to work fine. My only problem is that the Bluetooth headset disconnects some times as I speak on the phone.
As far as I have understood, each bar of the OOM settings represents a limit. If the available free amount of RAM drops below of that limit, then there should be a task killing procedure to free more RAM, according to process and category priorities etc.
So, for example if you choose "Aggressive" stance, then your system will be more fast and responsive, but you may have useful tasks being killed.
astral_cyborg said:
I don't have much knowledge of these settings, but I tried the "Multitasking 512" profile, as my mobile phone's RAM is 512 MB and it seems to work fine. My only problem is that the Bluetooth headset disconnects some times as I speak on the phone.
As far as I have understood, each bar of the OOM settings represents a limit. If the available free amount of RAM drops below of that limit, then there should be a task killing procedure to free more RAM, according to process and category priorities etc.
So, for example if you choose "Aggressive" stance, then your system will be more fast and responsive, but you may have useful tasks being killed.
Click to expand...
Click to collapse
Thanks for that I somehow got an idea about it. Cheers!
IMPORTANT: I think i reach the final build for this script. All in all i present two version of the script. One codename Balanced that is the initial script (and there for is the most balances i've got) and another codename Ultra Smooth as it is very smooth but may be too aggressive on background secondary services.
Balanced:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
https://mega.nz/#!NoJEXIiI!NXTetoxuwBMBzxsUCVIcrvEB_jxUSp3sE1z5e6VQIkc
Click to expand...
Click to collapse
Ultra Smooth:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
https://mega.nz/#!N4IiSboa!v4tSk1X_RZeGBJesrJbJUpJZvcdMiN2rTE4loTWHsYI
Click to expand...
Click to collapse
Hello, for all the Moto G users who have the crDroid ROM and have tried the Pink Kernel, i've made this topic so we can try to find the root from the performance issues with the combination of said ROM and Kernel.
For who follow my last post on both the thread of the ROM and Kernel, i had a theory about what was the issue.
After read the experience other users had with it and my own i came to the conclusion that the stability issue, force stop from heavy apps and even small reboots ("BSOD") came from a very different philosophy on the OOM (Out of Memory) configurations of the ROM stock Kernel (that don't have this issues) vs the Pink Kernel on this ROM.
With the Stock, i realize that we have much more free RAM (i got from 400mb free to 240mb free) then on Pink Kernel (that i was ranging from 280mb free to 144mb free). That is a big difference.
Our devices are amazing phones, but it RAM amount isn't the best now days, so i figured that heavy Apps (such as the Facebook one, the one who most had issues with the ROM+Kernel) just don't have much free RAM from the pool. So it hit the page file/swap (there for cause a very laggy experience and force closes) and if the page file/swap don't do the cut it reboot the phone.
On the stock kernel as it give much more free RAM it didn't had any of those issues (even though on my experience the Facebook App never run as smooth as the other apps, even on the stock kernel). So i tried my first attempt to remedy this issue.
As my Kernel management app of choice don't apply OOM settings after reboot (it go back to the stock one of the Kernel we have), and i like it as if it go wrong on boot it is ok again, i've made a simple script, so on every reboot it apply my settings and too that is a simple way that who don't use Kernel management apps can have this "fix".
I also don't like to use INIT.D for this as if it go wrong it will bootloop. With SManager (a free app on the play store) it is very safe if go wrong and if not.. it work just as INID.D in this case.
To who don't know how to use SManager, just get it on the play store. After open the app click on the menu button and choose new program. It will ask you to give a name, you can choose any one you like (i've choose OOM-FIX).
After give the name open it from the list within the app and click (to enable) the SU and BOOT option. After it click on the edit button so you can write the script.
On the script editor, here is the code of the script:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
Now save everything and either run it or reboot.
If you do use a Kernel Management app who apply OOM custom settings on each reboot, this settings on the script represent:
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
Click to expand...
Click to collapse
This was the best middle ground i found from the Pinky Kernel OOM vs the Stock (with my settings i'm getting from 386mb free to 244mb free).
I only tester for two days so far, but my experience on Facebook (the app who most gave me trouble) was very satisfactory. It isn't 100% perfect but for my use it is a good 85% (must remember that even on the stock kernel it wasn't 100% good).
The app don't lag as much, only if we spam commands such as click on the back button more then once at the same time it lag more then acceptable. But scroll down on the timeline, messages and person profile was very good.
Open too many pages inside the app lag a little too but nothing close to force boot or even force close the app for me.
But i'm not the most heavy FB user, neither the most heavy Phone user.
That is where you guys come in. If you guys who use the amazing crDroid ROM and love the Pink Kernel want to keep this combination, try this script/OOM settings i just shared, so if it need more tweaks (and if it really is the cause of the issue) we can do it. As for my use it is fine, but i want to know about on other phones and users/uses.
Just to share the full spec and config of my phone, it is a Moto G 4G LTE XT1040 using the latest crDroid with the latest Pink Kernel. I am not a heavy user and my GAPPS is the minimum pack. I greenify almost all apps on the phone (including many system ones), i have a big wakelock setting to not allow apps to wakelock and all in all i do the best to only let the apps i want to run (and usually are the foreground ones i've choose to use).
How ever i do use also Xposed and a lot of custom tweaks.
My Pink Kernel configuration (With 3C Toolbox) is a CPU profile that i'll share:
Profile:
Intelliactive @ min:300mhz and max 1,18ghz
All cores setup as free
TCP/IP Algorithm: Veno
SD Cache: 512
I/O: ROW
Double tap to wake: On
When the screen is off i have a userspace profile locked at 300mhz min and max frequency.
So there you go, who want to use the ROM and Kernel try this script or OOM out (you can try a Tune for profiles like mine too in case to emulate what my phone got as a result) and post the results, if it got better, worse or if it fix.
For me the phone is very present to use, VERY smooth and the Facebook App is manageable now.
NEW: INIT.D script Download:
https://mega.nz/#!N4IiSboa!v4tSk1X_RZeGBJesrJbJUpJZvcdMiN2rTE4loTWHsYI
(please do a NanoBackup before apply it, for test if it work open the terminal and type: cat /sys/module/lowmemorykiller/parameters/minfree).
Click to expand...
Click to collapse
CHANGELOG:
v0.1:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v0.2:
#!/system/bin/sh
echo "13312,17664,19968,37120,53248,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 208mb
Hidden Apps: 145mb
Secondary Server: 78mb
Visible Apps: 69mb
Foreground Apps: 52mb
Click to expand...
Click to collapse
v1.0:
#!/system/bin/sh
echo "8191,12544,19968,37120,53248,65536" > /sys/module/lowmemorykiller/parameters
Empty Apps: 256mb
Content Providers: 208mb
Hidden Apps: 145mb
Secondary Server: 78mb
Visible Apps: 49mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v2.0a-Codename-Balanced:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v2.0b-Codename-Ultra_Smooth:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
Click to expand...
Click to collapse
Pupet_Master said:
Hello, for all the Moto G users who have the crDroid ROM and have tried the Pink Kernel, i've made this topic so we can try to find the root from the performance issues with the combination of said ROM and Kernel.
For who follow my last post on both the thread of the ROM and Kernel, i had a theory about what was the issue.
After read the experience other users had with it and my own i came to the conclusion that the stability issue, force stop from heavy apps and even small reboots ("BSOD") came from a very different philosophy on the OOM (Out of Memory) configurations of the ROM stock Kernel (that don't have this issues) vs the Pink Kernel on this ROM.
With the Stock, i realize that we have much more free RAM (i got from 400mb free to 240mb free) then on Pink Kernel (that i was ranging from 280mb free to 144mb free). That is a big difference.
Our devices are amazing phones, but it RAM amount isn't the best now days, so i figured that heavy Apps (such as the Facebook one, the one who most had issues with the ROM+Kernel) just don't have much free RAM from the pool. So it hit the page file/swap (there for cause a very laggy experience and force closes) and if the page file/swap don't do the cut it reboot the phone.
On the stock kernel as it give much more free RAM it didn't had any of those issues (even though on my experience the Facebook App never run as smooth as the other apps, even on the stock kernel). So i tried my first attempt to remedy this issue.
As my Kernel management app of choice don't apply OOM settings after reboot (it go back to the stock one of the Kernel we have), and i like it as if it go wrong on boot it is ok again, i've made a simple script, so on every reboot it apply my settings and too that is a simple way that who don't use Kernel management apps can have this "fix".
I also don't like to use INIT.D for this as if it go wrong it will bootloop. With SManager (a free app on the play store) it is very safe if go wrong and if not.. it work just as INID.D in this case.
To who don't know how to use SManager, just get it on the play store. After open the app click on the menu button and choose new program. It will ask you to give a name, you can choose any one you like (i've choose OOM-FIX).
After give the name open it from the list within the app and click (to enable) the SU and BOOT option. After it click on the edit button so you can write the script.
On the script editor, here is the code of the script:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Now save everything and either run it or reboot.
If you do use a Kernel Management app who apply OOM custom settings on each reboot, this settings on the script represent:
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
This was the best middle ground i found from the Pinky Kernel OOM vs the Stock (with my settings i'm getting from 386mb free to 244mb free).
I only tester for two days so far, but my experience on Facebook (the app who most gave me trouble) was very satisfactory. It isn't 100% perfect but for my use it is a good 85% (must remember that even on the stock kernel it wasn't 100% good).
The app don't lag as much, only if we spam commands such as click on the back button more then once at the same time it lag more then acceptable. But scroll down on the timeline, messages and person profile was very good.
Open too many pages inside the app lag a little too but nothing close to force boot or even force close the app for me.
But i'm not the most heavy FB user, neither the most heavy Phone user.
That is where you guys come in. If you guys who use the amazing crDroid ROM and love the Pink Kernel want to keep this combination, try this script/OOM settings i just shared, so if it need more tweaks (and if it really is the cause of the issue) we can do it. As for my use it is fine, but i want to know about on other phones and users/uses.
Just to share the full spec and config of my phone, it is a Moto G 4G LTE XT1040 using the latest crDroid with the latest Pink Kernel. I am not a heavy user and my GAPPS is the minimum pack. I greenify almost all apps on the phone (including many system ones), i have a big wakelock setting to not allow apps to wakelock and all in all i do the best to only let the apps i want to run (and usually are the foreground ones i've choose to use).
How ever i do use also Xposed and a lot of custom tweaks.
My Pink Kernel configuration (With 3C Toolbox) is a CPU profile that i'll share:
Profile:
Intelliactive @ min:300mhz and max 1,18ghz
All cores setup as free
TCP/IP Algorithm: Veno
SD Cache: 512
I/O: ROW
Double tap to wake: On
When the screen is off i have a userspace profile locked at 300mhz min and max frequency.
So there you go, who want to use the ROM and Kernel try this script or OOM out (you can try a Tune for profiles like mine too in case to emulate what my phone got as a result) and post the results, if it got better, worse or if it fix.
For me the phone is very present to use, VERY smooth and the Facebook App is manageable now.
Click to expand...
Click to collapse
You did an amazing job! Yesterday when I tried the kernel everything was softrebooting, now the phone is smooth as butter! First time we got pink kernel working on a ROM! Have my thanks
Sparubens said:
You did an amazing job! Yesterday when I tried the kernel everything was softrebooting, now the phone is smooth as butter! First time we got pink kernel working on a ROM! Have my thanks
Click to expand...
Click to collapse
Thanks m8, anything you don't like feel free to tell and we tune it even more
New setup/tune.
I think this will be final, check out the new values and test
Final build release.
Straight to the fix
Low Memory Killer Settings
Foreground app: 50MB
Visible apps: 75MB
Secondary server: 125MB
Hidden apps: 200MB
Content providers: 300MB
Empty apps: 400MB
You should see an immediate effect, no reboot required (Which works great for testing).
The only downside is that it will (most of the time) kill idle apps, and you'll have to wait a little for it to open if you haven't opened it in a while.
How to change these values
You must have root. You do not need a custom kernel.
You can then change it through an app such as Kernel Adiutor or EX Kernel Manager (Don't forget to check "apply on boot").
Category Explanation:
The values for each setting act like an upper trigger. Once the memory falls below this limit, it starts killing things in its category (Feel free to correct and educate me if I'm wrong).
Foreground app - The app currently open and being shown to the user (We don't want this to die, so we set the limit very low)
Visible apps - Background application supporting anything visual to the user
Secondary server - Services that run in the background in case they're needed to support an open application
Hidden apps - Background application with nothing visual to the user
Content providers - Applications which provide and update data to the system, like Facebook syncing.
Empty apps - Applications which are stopped, but data is kept loaded.
HOW TO UNDO
Reboot your device. Changes are temporary until the next reboot.
Tell me if it worked for you! I'm just glad I could finally get my nexus to run like butter again.
Worked for me, UI elements feel more smooth now
Running AOSPA 6.0.3 for Nexus 5.
Thanks!
Thx for sharing....
I don't see any difference.
I'll test further
Thank you, now my nexus runs very smoothly without lags!
I'm using nitrogen os 7.1
Inviato dal mio Pixel utilizzando Tapatalk