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.
Related
Upgraded to froyo JPH last night and have noticed that autokiller doesn't work so well with it. When using autokiller with all the 2.1 fw's it did it's job and you could see which apps were the empty apps etc. However with froyo the empty apps don't show up and autokiller doesn't seem to be able to perform correctly, currently I have it set to aggressive but I can see my phone go to 70mb free. I have emailed the dev but no response as of yet, anyone else had this issue or know how to fix not being able to kill empty apps ? Cheers.
Sent from my GT-I9000 using XDA App
Daley87 said:
Upgraded to froyo JPH last night and have noticed that autokiller doesn't work so well with it. When using autokiller with all the 2.1 fw's it did it's job and you could see which apps were the empty apps etc. However with froyo the empty apps don't show up and autokiller doesn't seem to be able to perform correctly, currently I have it set to aggressive but I can see my phone go to 70mb free. I have emailed the dev but no response as of yet, anyone else had this issue or know how to fix not being able to kill empty apps ? Cheers.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Why you're using a autokiller app?
The phone got ram to be used. If theres no further ram available for apps android will clear it by itself.
I´m on JPH and there's 192 of 304 MB used.
There's 112 MB free ram!
because auto killer alters androids minfree settings unlike regular task managers that kill everything, also with a bit of use my phone is displaying just over 60mb free resulting in a slow phone.
Sent from my GT-I9000 using XDA App
i can't use my phone without autokiller...
jeanveupas said:
i can't use my phone without autokiller...
Click to expand...
Click to collapse
Maybe you should clean up your phone. I if u installed millions of apps its clear that your phone slows down.
Daley87 said:
because auto killer alters androids minfree settings unlike regular task managers that kill everything, also with a bit of use my phone is displaying just over 60mb free resulting in a slow phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
I hate to change the Android default settings for file system and minfree, however after applying the lagfix, absolutely no lag and my phone flies despite several days of excessive use with all possible apps.
If you don't need Lagfix, you could still use the apk for minfree settings and apply on boot.
60MB of free RAM should not cause you any slowness issues. RAM is there to be used, I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Prankey said:
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
Click to expand...
Click to collapse
Both programs do exactly the same. OCLF even refers to Autokiller as in "using the same names and values for defaults".
I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Click to expand...
Click to collapse
With "strict" setting I always have enough ram and still dozens of reportedly running apps. The Android way of multitasking is working really good, it just needs some fine tuning with the Galaxy S. Somehow, the default settings cause too much cleaning up right when you start certain apps, this it feels laggy even though the RFS factor has been removed (e.g. with Voodoo).
gpnda said:
Maybe you should clean up your phone. I if u installed millions of apps its clear that your phone slows down.
Click to expand...
Click to collapse
I have installed millions of apps, and it is running blazingly fast (using Autokiller to "strict" and Voodoo on JM8). Why shouldn't I? What else is nearly 2GB of user apps space meant for? Why are there so many apps in the store?
Prankey said:
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
If you don't need Lagfix, you could still use the apk for minfree settings and apply on boot.
60MB of free RAM should not cause you any slowness issues. RAM is there to be used, I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Click to expand...
Click to collapse
OCLF minfree settings, minfreemanager and autokiller all do the same thing - they change the same configuration file that controls Android's memory management tool.
I agree though, that the optimal amount of free RAM seems to be 60M-70M on our phones. The default configuration in the Samsung Froyo firmwares set it to about 40M-50M (the last 3 values in minfree are 40/44/48 by default).
And also, it is a misconception that "free" RAM in Linux is wasted. The free RAM is not unused, but is used by the OS to cache the disks, which is why the phone is faster with more free RAM. On our Samsungs this has a huge effect because RFS is slow and a big disk cache will help it a lot.
You can see this by doing:
# cat /proc/meminfo
cat /proc/meminfo
MemTotal: 311348 kB
MemFree: 16088 kB
Buffers: 12196 kB
Cached: 91344 kB
SwapCached: 0 kB
Active: 185192 kB
Inactive: 44792 kB
jeanveupas said:
i can't use my phone without autokiller...
Click to expand...
Click to collapse
5 big Widgets at Homescreen, 12 Apps opened (ICQ, Google Mail, Browser, MP3-Player, Touiteur, Titanium Backup, XDA, Market, ES File Explorer, YouTube and so on), 90mb free ram and the Phone is still running smooth.
Don´t know what you´re doing wrong.
Running JPH for 71 hours now without using autokiller and it has run great without much lag.
Mainly browsing internet, video, music, email and games without issue. And reply messages and calls.
Sent from my GT-I9000 using XDA App
PlanetJumble said:
Both programs do exactly the same. OCLF even refers to Autokiller as in "using the same names and values for defaults".
Click to expand...
Click to collapse
I agree, suggested as I felt "Autokiller" might not be working correctly in Froyo.
PlanetJumble said:
With "strict" setting I always have enough ram and still dozens of reportedly running apps. The Android way of multitasking is working really good, it just needs some fine tuning with the Galaxy S. Somehow, the default settings cause too much cleaning up right when you start certain apps, this it feels laggy even though the RFS factor has been removed (e.g. with Voodoo).
Click to expand...
Click to collapse
My experience was different. If I just use the OCLF 2.04 and do not tweak with file system and minfree settings, my phone is working perfectly no matter how many apps I load and how long I use (used alteast for 3 days without any lag issue)
PlanetJumble said:
I have installed millions of apps, and it is running blazingly fast (using Autokiller to "strict" and Voodoo on JM8). Why shouldn't I? What else is nearly 2GB of user apps space meant for? Why are there so many apps in the store?
Click to expand...
Click to collapse
I COMPLETELY agree. We are not talking of Windows 9x which could not manage memory well. We are talking of Linux which should work perfectly even when we have several apps running.
hardcore said:
OCLF minfree settings, minfreemanager and autokiller all do the same thing - they change the same configuration file that controls Android's memory management tool.
I agree though, that the optimal amount of free RAM seems to be 60M-70M on our phones. The default configuration in the Samsung Froyo firmwares set it to about 40M-50M (the last 3 values in minfree are 40/44/48 by default).
And also, it is a misconception that "free" RAM in Linux is wasted. The free RAM is not unused, but is used by the OS to cache the disks, which is why the phone is faster with more free RAM. On our Samsungs this has a huge effect because RFS is slow and a big disk cache will help it a lot.
You can see this by doing:
# cat /proc/meminfo
cat /proc/meminfo
MemTotal: 311348 kB
MemFree: 16088 kB
Buffers: 12196 kB
Cached: 91344 kB
SwapCached: 0 kB
Active: 185192 kB
Inactive: 44792 kB
Click to expand...
Click to collapse
I believe the cached portion shows as used memory. We may have to revisit this discussion. As whenever I use memory cleaners, I felt my system went worse if I keep more memory available (except for opening apps which uses the available memory instantaneously). So I doubt free memory (I am not talking of the default available memory on Android) can be used for cache when forcefully freed by these settings/apps.
Aery said:
5 big Widgets at Homescreen, 12 Apps opened (ICQ, Google Mail, Browser, MP3-Player, Touiteur, Titanium Backup, XDA, Market, ES File Explorer, YouTube and so on), 90mb free ram and the Phone is still running smooth.
Don´t know what you´re doing wrong.
Click to expand...
Click to collapse
xtrememorph said:
Running JPH for 71 hours now without using autokiller and it has run great without much lag.
Mainly browsing internet, video, music, email and games without issue. And reply messages and calls.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Completely agree, when I tweak with Minfree settings and the file system to "Deadline" it becomes more "jerky". Others might have different experience, however I strongly believe that while RFS definitely slows down write speeds, default minfree settings and the file system optimization should be optimum for "regular" use.
Every time I flash firmware, I try first without the lag fix, then with the lag fix, and finally, with autokiller, and every time autokiller has helped noticeably.
As things stand at the moment, its one app I wouldn't be without, lag fix or no lag fix.
Working well here. JPH firmware, autokiller set to strict, 91mb free. 3 days of uptime
Hi there XDA,
I've been using the custom rom DjangoManouche for some time now, and it's great! But while installing i'm usually guessing the settings. If someone can clarify it, it would be great!
Note that these settings are asked of you while you install DjangoManouch custom rom.
1. Available Kernels.
When installing the KoB kernel, you can chose between several options. NoOC or OC, with or without RamHack. I know that OC stands for over clocking, but what does the RamHack do (28 / 32 mb)?
2. Dynamic Fsync (active / inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?p=33381928
If i understand this correctly it means that you have a small lag when ending calls. But when your system crashed you won't lose data.
3. Frandom Optimazations (active / inactive)
I can find no information about this on the internet..
4. Zram (active 96/128mb or inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?t=2077072
If i understand this correctly it means that ZRAM is handy for devices with not a lot of RAM. But the LG 02x has 1gb of RAM(?). Wich raises the question what good does it do?
5. RAM Management (stock RAM values / Supercharger Free Ram values / SuperCharger Balanced Ram values)
I found this explanation: http://www.technorms.com/10319/boost-performance-android-phone-supercharger
Wich explains that supercharger script boost your phones performance. But doesn't explain what the difference is between 'Free Ram values' and 'Balanced Ram values'.
6. CRT Effect (enabled / disabled)
Is this the awesome animation that shows when you power on / off your phone?
7. Fast Dormancy (enabled / disabled)
I found this explanation: http://androidforums.com/samsung-galaxy-s2-international/674208-fast-dormancy-in-nutshell.html
In short you want to enable it if your provider supports it, correct?
8. Cronjobs (active / inactive)
I can find some javascript related information, but not connected to Android. So i'm in the dark here.
As last i want to add that I'm posting these questions here because flooding the original thread with these questions is just creating noise And i'm sure there are a lot of other people with the same questions.
Thanks in advanced!
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
SREEPRAJAY said:
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
Click to expand...
Click to collapse
Thanks for your reply!
It seems that cronjobs are actually really useful! But how do i give it permissions? Usually SU ask to give you permissions when the proces starts. (For example when you open Titanium Backup). But i can't manually add permissions.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
Thanks for your reply! So it means that your device is faster, but also drains your battery faster when screens is of?
SREEPRAJAY said:
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
Click to expand...
Click to collapse
Thanks for your reply! Let;s see what Greenify can do!
I'm gonna install the new DMX 1.6.1 in a few minutes with these settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
len.asdf said:
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
Click to expand...
Click to collapse
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
LilProphet said:
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Thanks for your reply! And we will find out today how smooth it goes
I've used my phone now for 2 days with these installation settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
But it's far from smooth. I'm installing Greenify now to see if it changes anything..
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
carburano said:
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
Click to expand...
Click to collapse
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
len.asdf said:
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
Click to expand...
Click to collapse
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
mpoumpis said:
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
Click to expand...
Click to collapse
I will try this out on my next install! I prefere to use a install for several days so i can test it out better.
And after installing Greenify things got a lot smoother! That app is just black magic
Guys, I need a help. Tried everything, but still facing big lag especially when I click on dialer, contacts or messages (waiting couple of secs until they show up). This is more obvious when I click right after I 'woke up' my phone from deep sleep.
I'm using stock 20b with Iodak v8 kernel (tried v9 as well, but due to bluetooth and fm radio issue on stock, reverted to v8). Also, I did everything what I could found to improve performace: disabled and then deleted MLT, did a full wipe of everything (clean install), installed only apps that I need, turned off 3g, data and gps (only WiFi is on), installed Greenify and so on..
My current setup of kernel is following:
Governor: interactive (tried ondemand, but was even worst)
Max: 1600000
Min/Max Screen Off: 760000
Scheduler: SIO
CPUQuiet Power: userspace (noticed that only 3 cores are online instead of 4)
I appreciate any help, but please, don't tell me to search, 'cause I did. As for the other custom roms, I tried CM, but I prefer more stock, mostly because of Gallery, Polaris and FM Radio Apps.
Guys, is there any way to fix this lag issue? I don't care much for the battery, since this lag drives me crazy.
Thanks in advance.
Vladimir
vladja10 said:
Guys, I need a help. Tried everything, but still facing big lag especially when I click on dialer, contacts or messages (waiting couple of secs until they show up). This is more obvious when I click right after I 'woke up' my phone from deep sleep.
I'm using stock 20b with Iodak v8 kernel (tried v9 as well, but due to bluetooth and fm radio issue on stock, reverted to v8). Also, I did everything what I could found to improve performace: disabled and then deleted MLT, did a full wipe of everything (clean install), installed only apps that I need, turned off 3g, data and gps (only WiFi is on), installed Greenify and so on..
My current setup of kernel is following:
Governor: interactive (tried ondemand, but was even worst)
Max: 1600000
Min/Max Screen Off: 760000
Scheduler: SIO
CPUQuiet Power: userspace (noticed that only 3 cores are online instead of 4)
I appreciate any help, but please, don't tell me to search, 'cause I did. As for the other custom roms, I tried CM, but I prefer more stock, mostly because of Gallery, Polaris and FM Radio Apps.
Guys, is there any way to fix this lag issue? I don't care much for the battery, since this lag drives me crazy.
Thanks in advance.
Vladimir
Click to expand...
Click to collapse
This is "normal" for system apps. Download custom apps from google store like ExDialer,GOSms.. That will resolve your lag.. When you install those apps from store, use titanium backup to freeze stock apps(dialer,contacts,messages).
@vladja10 http://forum.xda-developers.com/showpost.php?p=49272503&postcount=1986
Thanks guys, but neither of these two options helped. There's some improvements, but still pretty much laggy.
Think I found out what causing lag: synchronization. Every time when phone is synchronizing, everything is so laggy, otherwise is ok. Following accounts have sync turned on: Skype, Facebook, WhatsApp, Twitter and Google.
Does anyone of you have experienced similar problem? Is there solution for this?
vladja10 said:
Think I found out what causing lag: synchronization. Every time when phone is synchronizing, everything is so laggy, otherwise is ok. Following accounts have sync turned on: Skype, Facebook, WhatsApp, Twitter and Google.
Does anyone of you have experienced similar problem? Is there solution for this?
Click to expand...
Click to collapse
I have all those apps running in my phone, but I did not face those lags.
But ya I did felt those lags when I'm still using stock JB OS. Stock JB from LG is sucks man, you should instal another ROM.
Currently I'm using CM11 (Kitkat 4.4.2 based), its lag free and have more free RAM. (around 350 - 400MB). :good:
The difference is like heaven and hell compared with the stock ROM (I only have 150 - 200MB Free RAM).
bomerzz said:
I have all those apps running in my phone, but I did not face those lags.
But ya I did felt those lags when I'm still using stock JB OS. Stock JB from LG is sucks man, you should instal another ROM.
Currently I'm using CM11 (Kitkat 4.4.2 based), its lag free and have more free RAM. (around 350 - 400MB). :good:
The difference is like heaven and hell compared with the stock ROM (I only have 150 - 200MB Free RAM).
Click to expand...
Click to collapse
The ROM can make a difference, but it has nothing to do with "Free RAM". I wish people would stop perpetuating this myth.
Free RAM is wasted memory on an Android device. Unless you are getting below about 50MB there is not a problem as the device is designed to use as much as it can and then swap it out automatically.
I agree about CM11 though. I'm running the latest nightly and the only problem I have is the delay in waking when you press the power button
SimonTS said:
The ROM can make a difference, but it has nothing to do with "Free RAM". I wish people would stop perpetuating this myth.
Free RAM is wasted memory on an Android device. Unless you are getting below about 50MB there is not a problem as the device is designed to use as much as it can and then swap it out automatically.
I agree about CM11 though. I'm running the latest nightly and the only problem I have is the delay in waking when you press the power button
Click to expand...
Click to collapse
Well.. Sorry for my false statement and thank you for correcting it
4X HD is my very first android device. But that's what I really thought after I flashed the CM11.. Its like whoa, more free space on RAM, and it feels like I'm using a new phone
bomerzz said:
Well.. Sorry for my false statement and thank you for correcting it
4X HD is my very first android device. But that's what I really thought after I flashed the CM11.. Its like whoa, more free space on RAM, and it feels like I'm using a new phone
Click to expand...
Click to collapse
You might want a read of this;-
RAM: What it is, how it's used, and why you shouldn't care
Well, I’m afraid that I’ll be forced to get back to CM (used it once, but missed some apps such are: FM Radio, stock gallery app (couldn’t find good replacement that synced photos with google acc) and Polaris Office – these apps I use on a daily basis). Anyway, before install CM, I’ll give one more try to Stock.
I did what @ottomanhero told me, and that actually helped. But, since I used Trickstermod to tweak governors, after every single reboot, stock values would be back, so I had to use init.d script, and there comes a problem.
Here is what I did (followed instructions from Iodak's OP):
- Using ES File Explorer created folder /system/etc/init.d and set permissions to rwxr-xr-x
- Created new file in init.d folder and name it 1script (used Note++ instead of Windows editors to avoid leaving an extra space at the end of each line or an invisible invalid character)
- Then added following commands:
Code:
#!/system/bin/sh
echo "70" > /sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load
echo "70" > /sys/devices/system/cpu/cpufreq/interactive/midrange_go_maxspeed_load
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "20000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 200 300 400 450 500 600 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_overclock
- and finally set permissions to 1script rwxr-xr-x and owner to root group to shell
So, that should be it, but didn’t work for me. Then, I installed SManager to check what’s wrong with the script, and it stated that with first 4 lines error is: no such file or directory (which is strange because exactly that's the path), and for the last line is stated: permission denied.
Did I miss something? Apologize if this question is too noob for you guys, but I’m running out of ideas.
Thanks all for your help.
Regards,
Vladimir
SimonTS said:
You might want a read of this;-
RAM: What it is, how it's used, and why you shouldn't care
Click to expand...
Click to collapse
Oh, really?
Free RAM is NOT wasted RAM.
It directly effects smoothness of the phone.Why do you think android would have Out Of Memory values if it was created to just fill up the RAM with only apps? It still needs some RAM free for caching.
---------- Post added at 03:50 PM ---------- Previous post was at 03:46 PM ----------
vladja10 said:
Well, I’m afraid that I’ll be forced to get back to CM (used it once, but missed some apps such are: FM Radio, stock gallery app (couldn’t find good replacement that synced photos with google acc) and Polaris Office – these apps I use on a daily basis). Anyway, before install CM, I’ll give one more try to Stock.
I did what @ottomanhero told me, and that actually helped. But, since I used Trickstermod to tweak governors, after every single reboot, stock values would be back, so I had to use init.d script, and there comes a problem.
- and finally set permissions to 1script rwxr-xr-x and owner to root group to shell
So, that should be it, but didn’t work for me. Then, I installed SManager to check what’s wrong with the script, and it stated that with first 4 lines error is: no such file or directory (which is strange because exactly that's the path), and for the last line is stated: permission denied.
Did I miss something? Apologize if this question is too noob for you guys, but I’m running out of ideas.
Thanks all for your help.
Regards,
Vladimir
Click to expand...
Click to collapse
Code:
#!/system/bin/sh
echo "70" > /sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load
echo "70" > /sys/devices/system/cpu/cpufreq/interactive/midrange_go_maxspeed_load
echo "60000" > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo "20000" > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo "200 300 400 450 500 600" > /sys/devices/system/cpu/cpu0/cpufreq/gpu_overclock
I think the script didn't execute at boot due to last line, you forgot the quotes.And while using Smanager you gotta tick "root" or else it won't run.Try this one
ottomanhero said:
I think the script didn't execute at boot due to last line, you forgot the quotes.And while using Smanager you gotta tick "root" or else it won't run.Try this one
Click to expand...
Click to collapse
Well, you were right about the quotes (now, the new values are set), but as the other 4 lines, they still have the same error: No such file or directory, and all values are stock.
Do you have any idea what's going on? Why did it work for one, and didn't for the other lines?
http://forum.xda-developers.com/showthread.php?p=48042187#post48042187
ottomanhero said:
Oh, really?
Free RAM is NOT wasted RAM.
It directly effects smoothness of the phone.Why do you think android would have Out Of Memory values if it was created to just fill up the RAM with only apps? It still needs some RAM free for caching.
Click to expand...
Click to collapse
As I stated in my first post;-
Unless you are getting below about 50MB there is not a problem
Click to expand...
Click to collapse
Of course you need some free memory, but not hundreds of MBs of it. I notice that you pointed the same XDA quote that is used and linked to by lots of different sites when this is being discussed. To use someone else's quote - better written than I could do so myself;-
In the most simplistic terms, here is how it works, and why "free RAM is wasted RAM," but also, why you don't want all RAM in use at any given time.
If an application is not in memory when you try to open it, that application haa to be loaded into memory, thus triggering a "load time." Having the application in memory (prefetched) prevents this load time and has the application load near insantly. This is why a modern OS will preload our most commonly used applications into memory. The more memory that you have, the more applications that can be preloaded, the smoother your device will run. Clearing this memory gives you no immeidate benefit, and will actually slow your device. Idle applications in memory consume almost no resources (CPU cycles, battery power, etc.). If an application is consuming resources, that means that it is doing something. Closing it will only force the application to re-load. Using a task killer for this purpose will cause a "boxing match" where the task killer closes the application, the app reopens itself, and back and forth. THIS will consume resources.
However, you want to have some memory free. Your devices will not have enough memory to preload EVERY application, so it has to guess based on your actions. It needs to have enough memory available to quickly load an app that you may want.
Let's say that you want to load an application that requires 256MB of RAM, but you only have 128MB available. This means that the OS is going to try to clear 128MB of RAM to accomodate your app, and as your app loads, will try to clear another 128MB to return to its previous state. This clear/load/clear causes a longer load time and more slowdown than just loading an app not already in memory.
So, the ideal situation is to have most common apps in memory (pre-fetched), but enough memory available to handle 1-2 common apps that are not already pre-loaded. Touchwiz (Samsung) devices allow you to clear memory from the task manager. My S2 had about 870MB of user-available RAM, and if I trashed all apps, it would go as low as 300MB in use. This may look cool, but it is a complete waste of resources, and the OS is simply going to re-load those apps over the next 2-3 minutes anyway. And if you use a task killer to keep your device idling at 300MB of available RAM? This is simply going to slow down the device, harm the battery, and give you the same memory performance and availability that you would get with an HTC G1.
Click to expand...
Click to collapse
As the OP was stating that "I only have 150 - 200MB Free RAM" with the Stock ROM, that is definitely NOT what is causing a lag issue. If you have that much free memory (before Android goes caching stuff and not declaring it of course) then you are absolutely fine on any Android device there is.
vladja10 said:
Well, you were right about the quotes (now, the new values are set), but as the other 4 lines, they still have the same error: No such file or directory, and all values are stock.
Do you have any idea what's going on? Why did it work for one, and didn't for the other lines?
Click to expand...
Click to collapse
Maybe your partitions aren't mounted.I took these lines from pimp my rom init.d script.Create another script but it has to come before the governor tweaks script.
#!/system/bin/sh
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier =0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodir atime,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodir atime,barrier=0,nobh /cache
Click to expand...
Click to collapse
For example, name this script "93Mount" and name the governor script "94Governor" so the mounting script will be executed before governor script.
ottomanhero said:
Maybe your partitions aren't mounted.I took these lines from pimp my rom init.d script.Create another script but it has to come before the governor tweaks script.
For example, name this script "93Mount" and name the governor script "94Governor" so the mounting script will be executed before governor script.
Click to expand...
Click to collapse
Well, I did like you said and here's what I got:
Code:
exec /system/bin/sh '/etc/init.d/93Mount'
h '/etc/init.d/93Mount' <
failed: No such file or directory
failed: No such file or directorybh on /data
mount: mounting atime,barrier=0,nobh on /cache failed: Invalid argument
Any idea?
For the People who want Stock Gallery on CM and hate Aosp Gallery like Iam, check facebook offical cyanogenmod. They send a link to their new gallery next. Its in beta stase, so its not avaible yet. But if its stable itll be in play store. Its like the stock gallery app. Very beauty
Sent from my LG-P880 using xda app-developers app
vladja10 said:
Well, I did like you said and here's what I got:
Code:
exec /system/bin/sh '/etc/init.d/93Mount'
h '/etc/init.d/93Mount' <
failed: No such file or directory
failed: No such file or directorybh on /data
mount: mounting atime,barrier=0,nobh on /cache failed: Invalid argument
Any idea?
Click to expand...
Click to collapse
Well try this app https://play.google.com/store/apps/details?id=com.stericson.remount&hl=tr
EDIT : check this link out. http://forum.xda-developers.com/showthread.php?t=1381188
I'm not sure it's the right track or not, it does happen to me quite ago.
The problem is the SD (my case, luckily it's external). The system try to read files from card but it got error thus try again => laggy
I removed the card and it's alive. Try to check your internal sd. hope that help
App didn't help, I got the same error. Never mind, I give up Will use Trickstermod after every single reboot until finally find solution. Thanks @ottomanhero for all your help.
@GalaxyVolvoZ that app looks realy nice. Finally a good replacement for Stock Gallery.
@klbterminator I don't have any problems with SD, at least didn't so far
Thanks guys.
Regards,
Vladimir
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
*** Disclaimer
I am not responsible for any damage you made to your device.
Potential heat problems still there in this ROM.
If you unlock your bootloader from stock rom, be sure to backup your drm keys / TA partition in case you want to go back to stock ROM (otherwise drm keys are forever lost, and you may be missing camera features if you go back).
You have been warned.
Click to expand...
Click to collapse
I did a rebuild of LineageOS 18.1 with the sources of Berni-0815 and tarkzim, many thanks to them for their hard work!
SELinux: enforcing
Camera: Stock camera works ok at first glance (up to 8MP, camera.disable_zsl_mode=0 is set).
Small further tweaks in device/sony/kitakami-common/system.prop:
Spoiler
ro.config.hw_quickpoweron=true
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
power_supply.wakeup=enable
ro.config.hw_power_saving=1
ro.HOME_APP_ADJ=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
debug.performance.tuning=1
Flashing and tuning Instructions:
Clean flash advised.
From TWRP:
1. Flash ROM + optionally gapps in a row (read https://wiki.lineageos.org/gapps and https://forum.xda-developers.com/t/...-e6653-build-2022-11-18.4517491/post-87743699), Google app may cause high battery drain though (deactivate it if need be/Google Go being a possible alternative)
Click to expand...
Click to collapse
2. Optionally: Restart to recovery / TWRP, then flash magisk
Click to expand...
Click to collapse
Attached images showing sample setup with Google apps. MMApp is Magisk renamed apk.
Click to expand...
Click to collapse
Install Android System WebView Beta to get updates for WebView (or bromite webview and ff-updater app on F-Droid).
Install Google Google Go app if you want to use Google Assistant (Google app may cause high battery drain). Chimera seems to be possible to be disabled anyway: https://forum.xda-developers.com/t/...ry-drain-due-to-google-play-services.4406617/ (edit: disabling chimera seems to cause other problems in logcat, so better leave it as it is).
For temperature cooldown use a Kernel Manager like Smartpack Kernel Manager / Franco Kernel Manager by Franciso Franco / EX Kernel Manager by flar2 (root/magisk required) and set:
- CPU: set CPU governor of little CPU to "ondemand" - saves a bit of energy compared to "interactive" cpu governor. Don't change big CPU governor (especially if you set minimum of big cpu cores to 0), because Smartpack will crash then.
In CPU governor tunables optionally also set powersave_bias to something higher than 0 (up to 100), like 50 or even 100 works fine (reduces CPU upclocking a bit)
- CPU hotplug: minimum big CPU cores to 0. Edit: Set Busy Down threshold to 40 and Busy Up threshold to 70 or 80 to reduce the probability of big CPUs being activated.
- Thermal: turn on all three thermal drivers (seems to work despite the warnings).
Click to expand...
Click to collapse
- Edit: set GPU governor to "simple_ondemand" too, it's more balanced than msm-adreno-tz.
If you don't use graphics intensive apps, also set GPU max frequency to 180 Mhz - this makes a huge difference in Passmark PerformanceTest app - Open GL ES Unity benchmark (complex space game simulation), but the other 2D and 3D benchmarks in the same app are not much affected by this.
Click to expand...
Click to collapse
- i also changed I/O scheduler of internal/external sd card to deadline noop (simplest one / is supposed to save a little bit of energy). Passmark Performance Test didn't show much difference on them anyway. And disabled I/O stats for internal and external SD card.
Edit: see https://forum.xda-developers.com/t/...ng-camera-quality-guide.4515659/post-87794505
Click to expand...
Click to collapse
- Also turn on Battery saver mode (Extreme battery saver). Without it, little CPUs will clock high, with Battery saver, little CPUs will try to clock down
- and optionally Data Saver mode (quick settings)
- switch off NfC and Ambient display.
- Also enable Dark mode with pitch black Background and set a pitch black wallpaper (apps in Playstore for this available).
- Install naptime (with aggressive doze, disabling motion detection/enabling the first five options) helps for saving energy a lot. If you don't use Playstore, on F-Droid there also Doze alternatives to Naptime, like ForceDoze, beware who you give root though / or use adb to give the doze app the required permissions.
For further debloating: use the attached shell script sumirecleanapp.sh as root in adb shell or TWRP Terminal (TWRP Advanced section) with System partition mounted as writable (execute the script with "sh sumirecleanapp.sh" in the Terminal application). You can use the script direcdtly after flashing ROM and gapps in TWRP to shorten the first boot too (need to remount System partition as writable because other installscripts unmount it). Look at the comments in the script before you do so, to avoid deleting apps you might wanna use. They are backed up to /sdcard/sumirebackup/ and corresponding system subfolder though in case you wanna reinstall them. In case you reinstall an app make sure to chmod 755 to the dir and 644 to the apk files.
Click to expand...
Click to collapse
Sources (lineage-18.1 branches):
ROM: https://github.com/LineageOS/android.git
Kernel: sony msm8994 https://github.com/Professor-Berni/android_kernel_sony_msm8994
Vendor: https://github.com/Professor-Berni/proprietary_vendor_sony
Device-tree:
kitakami-common https://github.com/Professor-Berni/android_device_sony_kitakami-common
sumire https://github.com/Sony-MSM8994-Dev/android_device_sony_sumire
Local manifests: https://github.com/Professor-Berni/local_manifests (devices.xml modified to use tarkzim's sumire device sources)
Download:
ROM https://drive.google.com/drive/folders/1uq_O3lgPX4fjmzKpqnOoWIdxBvVch3bO
Issues:
Potential heat problems (tweaking advised/see instructions above,). If your phone crashes you're probably running too hot.
Edit: Stock Voice Recorder app is working
Audio/microphone recording of Whatsapp/Telegram should work
Edit: The screen brightness seems alright, no suddenly dimmed display
If you experience an app not starting (potential SELinux errors) please post a logcat with "avc: denied" errors (use MatLog app or adb logcat | grep "avc: denied")
Contributors
berni-0815, tarkzim
Thanks to LineageOS
LineageOS – LineageOS Android Distribution
LineageOS Android Distribution
lineageos.org
Build system:
Linux Mint 21, 8 GB Ram, 8 GB swap partition, ~170 GB SSD space used for the whole Linux partition with the compiled sources (repo option --depth=1), 4,5 GB ccache used.
Had to modify build/soong/java/droiddoc.go to avoid out of memory error while building the ROM, so there
after
cmd.BuiltTool(ctx, "metalava").
Flag(config.JavacVmFlags).
Click to expand...
Click to collapse
i inserted:
Flag("-J-Xmx6114m").
Click to expand...
Click to collapse
Using HedgeCam 2 (fork of Open Camera) as photo app recommended (camera2-API works there).
Also turning on some Autofocus bugfixes there may help (but test yourself).
To focus anew tap on the screen where you want the focus on.
Best results when you get a green circle and then take the photo.
Manual ISO mode makes the camera server crash on Camera2-API, so use Auto ISO mode (you can restart camera server in Hedgecam by switching the API back and forth also) or disable Camera2-API.
Note:
After using Hedgecam with Camera2-API and then builtin camera app, the latter one doesn't seem to work properly.
If you want to remove the internal Camera app, move the folder /system/system_ext/priv-app/Snap to somewhere else on /sdcard (as backup). To do so, in TWRP mount System partition, then use TWRP File manager or Terminal (advanced section).
Edit: Integrated the removal of the buitin camera app Snap into my debloating script (sumirecleanapp.sh)
Edit 2: Updated recommended camera settings, see below:
[ROM][11.0][UNOFFICIAL] LineageOS 18.1 [sumire/E6653] tuned rebuild 2022-11-23 + cooldown tuning + camera quality guide
*** Disclaimer I am not responsible for any damage you made to your device. Potential heat problems still there in this ROM. If you unlock your bootloader from stock rom, be sure to backup your drm keys / TA partition in case you want to go back...
forum.xda-developers.com
Overnight test (flight mode) of 11 hours with the above settings resulted in same accu battery percentage after the 11 hours (10% before/10% after).
CPU, CPU hotplug and GPU governor tuning suggestions updated in the first post (see also attached screenshots).
When surfing in Opera with deskop site mode, the temperatures stay like below 50 degrees at the moment with this.
Edit: For better surfing performance and battery life use mobile browser mode instead of desktop browser mode by default in your browser... complex websites (for example YouTube) suck up a lot of power for rendering in desktop mode.
Update for best Hedgecam 2 settings, giving more consistent good picture quality:
In Hedgecam 2 settings, Camera Controls, set Touch to Capture.
This enables you to click on a spot on the screen where you want the picture focus on, and take the picture immediately!
(instead of having to click on a spot in the picture to focus, and then press the camera button some seconds later - with the risk of losing autofocus, and iso auto mode changing in the meantime).
Also in Hedgecam 2 settings, Bug fixes, enable alternative flash method: Torch
These were the most consistent settings to get good picture quality in suboptimal lighting conditions for me, and also easy to use!
Note: picture quality will be best when the focus circle (where you tap the camera preview picture) turns green when (or shortly before) you take a photo.
So if you're intent to have a good quality picture just take 2 or 3 shots where Hedgecam 2 (for at least one of the pictures) gives you the green circle feedback. Focus and quality will be good then
See also the attached photo, and for comparison with HTC camera app 20MP and Open camera app 8 MP on sumire, see here in the crdroid 11 thread (same foto spot and similar lighting conditions):
[ROM+KERNEL][UNOFFICIAL][11.0] crDroid
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
For anyone interested in crDroid, i did a crDroid Android 11 / crDroid version 7.23 build for Xperia Z5/sumire, similar to this LOS 18.1 build:
[ROM+Kernel][11.0][UNOFFICIAL] crDroid 7.24 Android 11 - NOT STABLE [sumire/E6653] build 2022-11-18
*** Disclaimer I am not responsible for any damage you made to your device. Potential heat problems still there in this ROM. If you unlock your bootloader from stock rom, make sure to backup your drm keys / TA partition in case you want to go...
forum.xda-developers.com
Note: Flamegapps Device Health Services app (including Google Playstore app update for it), seems to break accu battery statistics in Settings.
Potentially SELinux or other permissions related.
So for the moment don't install Flamegapps Device Health Services (use config script).
Google app showing a lot of battery drain now, didn't use it much, just some Voice commands for Weather and Alarm clock with Assistant. Reasons could be Google Voice recognition machine learning (?). (i didn't activate the constant Google Assistant Voice listening by Hey Google). Or maybbe because i reinstalled english language(?)
A bit too much anyway.
Edit: Google Go app instead of Google app seems to work fine regarding battery usage.
W
psi78 said:
Note: Flamegapps Device Health Services app (including Google Playstore app update for it), seems to break accu battery statistics in Settings.
Potentially SELinux or other permissions related.
So for the moment don't install Flamegapps Device Health Services (use config script).
Google app showing a lot of battery drain now, didn't use it much, just some Voice commands for Weather and Alarm clock with Assistant. Reasons could be Google Voice recognition machine learning (?). (i didn't activate the constant Google Assistant Voice listening by Hey Google). Or maybbe because i reinstalled english language(?)
A bit too much anyway.
Click to expand...
Click to collapse
For comparison: the Google app doesn't show up anywhere near top on my Google Pixel 2 XL, despite i use Google Assistant Voice commands for Weather and Alarm clock there too.
Ok, Flamegapps Device Health Services app and Google app seem to be not working correctly.
Probably better follow the LineageOS advice regarding gapps (make sure to flash gapps directly after flashing the ROM):
Google apps | LineageOS Wiki
wiki.lineageos.org
Google App potentially causing high accu battery drain with Mindthegapps too though (experienced it on crDroid with Mindthegapps).
Little update to debloating script sumirecleanapp.sh (see first post), changing permissions of backup files for Security reasons.
The following qcom and other tweaks can be added to /system/build.prop (tested it on crDroid ROM version for sumire), phone is snappier and a bit cooler then (unless it's all placebo):
debug.gralloc.enable_fb_ubwc=1
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
#debug.qc.hardware=true
#com.qc.hardware=true
com.qc.hw=1
debug.qc.hw=1
ro.config.nocheckin=1
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.mm.enable.prefetch=true
persist.data.mode=concurrent
# buffers shared between Camera and Video
vendor.vidc.enc.dcvs.extra-buff-count=2
vendor.vidc.enc.disable.pq=1
# Bluetooth
debug.bt.lowspeed=true
net.bt.name=Android
See also https://androidforums.com/threads/qualcomm-speific-build-prop-edits.548317/
New build 2022-11-23 is up (download link in first post).
LOS 18.1 as of 2022-11-21
More tuning and possible battery optimizations:
- Kernel tuned for cortex-a57.cortex-a53 big.little setup (crashes on crdroid were crdroid related, not kernel related)
- VM optimizations for cortex-a57
- Using Open GL ES 3.2 now in build.prop (instead of 3.1 as wrongly stated there before, drivers were already 3.2)
- boot process limited to CPUs 0-3
- some more optimizations in /system/build.prop
Clean flash or semi clean flash at least recommended (wipe Dalvik, Cache, System partitions, or if possible also Data partition)
PS: I'm staying on LOS now because of crashes on crDroid still occuring under high load (even with standard kernel)
Edit: modified files regarding ROM version 2022-11-23 here:
LOS18.1_source_modifications - Google Drive
drive.google.com
My gf broke her phone and is using my Xperia Z5 now (my main phone is a Google Pixel 2 XL nowaday).
Regarding telephoning, i noted there are more crackling sounds with VoLTE in mobile settings on, and less crackling when VoLTE is switched off (german Telekom carrier). This may be also because of SmartPack throttling down the CPUs in my setup, but not sure of that.
psi78 said:
My gf broke her phone and is using my Xperia Z5 now (my main phone is a Google Pixel 2 XL nowaday).
Regarding telephoning, i noted there are more crackling sounds with VoLTE in mobile settings on, and less crackling when VoLTE is switched off (german Telekom carrier). This may be also because of SmartPack throttling down the CPUs in my setup, but not sure of that.
Click to expand...
Click to collapse
well as it happens, gf uses the phone in another way than me, and for some reason the keyboard reacted sometimes not or very slow.
in the end i deinstalled Smartpack to just deactivate all the CPU throttling and also installed Gboard.
(Extreme) Battery Saver mode and Naptime still do a lot for cooldown though - CPU cores 0-3 still throttling down to lower frequencies with Battery saver, and naptime putting unused apps quicker to deep sleep.
Ah, crackling noise, for some reason it occurs frequently with system sounds (ringtone, button presses, etc.)
I have bought my mom a new phone, so I can test things on Z5 now.
works well,thank you.
Hello, during videocalls via viber the person I am calling with is hearing himself as an echo. Has enyone such problem? I dont know if it is spec of this phone or is something wrong, I didnt use this phone with stock rom before lineageos. Thanks.
in regards to audio crackling i have been suspecting that it's rendering the audio via Software Rendering (CPU gets overloaded hence Audio Crackling) instead of utilizing the built-in Qualcomm DAC for Hardware rendering if this is not the case then you might want to look on the playback bitrate and frequency. As far as i remember tarkzim set the audio bitrate and frequency to 32-Bit/48KHz while on the previous build from sony it was only at 24-Bit/192KHz
Ramon111 said:
Hello, during videocalls via viber the person I am calling with is hearing himself as an echo. Has enyone such problem? I dont know if it is spec of this phone or is something wrong, I didnt use this phone with stock rom before lineageos. Thanks.
Click to expand...
Click to collapse
Don't have any experience with Viber, sry. In case you want to test it on stock Sony ROM, you can use Sony's Flash Tool "EMMA" to go back to stock ROM:
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
_harley said:
in regards to audio crackling i have been suspecting that it's rendering the audio via Software Rendering (CPU gets overloaded hence Audio Crackling) instead of utilizing the built-in Qualcomm DAC for Hardware rendering if this is not the case then you might want to look on the playback bitrate and frequency. As far as i remember tarkzim set the audio bitrate and frequency to 32-Bit/48KHz while on the previous build from sony it was only at 24-Bit/192KHz
Click to expand...
Click to collapse
Sounds plausible
Edit: Audio crackling may be a different issue than audio echos though?
There are some threads about voice echos here on xda, some attributing it to phone cases/covers, some to hardware problems, some to noise reduction, but i don't have a clue atm if it's possible to change that.
When i do video calls in home office (on PC with webcam) i sometimes experience the problem of hearing echos.of my voice when the other person isn't using headphones, and the voice coming out of the other person's speaker is loud and recorded by their microphone again. The other person using headphones is a workaround for that, but not sure if that's a similar issue there @Ramon111 . Does it work for you with other devices than the Z5?