Update: I found an even better solution. Instead of setting "dalvik.vm.heapsize=256m" use "dalvik.vm.heapsize=128m"
Warning! Please make a backup of your /system partition using recovery incase you get a bootloop from changing vm heapsize. Don't go below 128m as it may cause a bootloop.
If you want additional memory you can download "Ram Manager Free" from the Google playstore and set up a disk swap. Within the app, go to swap and delete the given directory and set it to "/cache and use a value of 256 MB. It won't steal from your already limited storage as it will use the cache partition which goes mainly unused. Warning though as it may degrade your internal storage from constant writing. If you ask me I don't care about degradation of my Moto G as I plan to get a better phone soon. I only recommend you use swap with the stock kernel as there is virtually no lag. I tested with other kernels and there is noticeable lag.... Aero Kernel lags noticeably and so does faux kernel. Oh! and make sure you set it to balanced and check the apply at boot option to stick. I stopped using swap, but you can try for yourself to see if you like it.
This is for the Moto G XT1034 as I don't know if the build.prop is different for the other variants, but you can always check if you have the duplicate entries.
While going through the build.prop of the stock 4.4.4 ROM I found duplicate entries of the same value with different parameters. The culprit being "dalvik.vm.heapsize" seemed to have been causing my music apps force closing when there was "insufficient" RAM. Other apps running in the background can also be killed like night screen filters while browsing the web using Chrome just to name another. You'll find two entries called "dalvik.vm.heapsize=36 and dalvik.vm.heapsize=256." They are the same value, but with different parameters. I deleted the one for "36m" and my multitasking issues disappeared without changing the MINFREE TASKKILLER values. I used Performance Control that can be found here on XDA to edit the build.prop. When you delete "dalvik.vm.heapsize=36m" make sure you re-add the value "dalvik.vm.heapsize=256m" because deleting one deletes BOTH! My screen filter app "EasyEyes" has yet to be killed by low memory situations.
Why would Motorola include duplicate entries of the heapsize? I'd like to be enlightened on why they included both.
NOW, your music app may be killed if you run very low on memory, this happens when you use chrome and view heavy pages, so modifying your MINFREE TASKKILLER values may be of additional assistance. I attached a screenshot of MINFREE values if you want to use my values, although I'm not using them since I'm using stock values. At the end of the day you have to understand that 1GB is now "low-end" and is simply not enough for multitasking anymore on Android. Apps are becoming larger and browsers and websites are becoming more complex; more RAM is needed. As soon as you open Chrome expect your apps to be killed since it needs at least 200 MB to run adequately.
Any reports of success with this? I just sold my Moto G last week because of the multi tasking issue... if this solves 90% of the problem, that would be pretty awesome.
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Jorge_007 said:
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Click to expand...
Click to collapse
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
NextGenGTR said:
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
Click to expand...
Click to collapse
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Jorge_007 said:
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Click to expand...
Click to collapse
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
NextGenGTR said:
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
Click to expand...
Click to collapse
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Jorge_007 said:
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Click to expand...
Click to collapse
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work!!!
Suprisingly enough that worked and nothing has been deleted and everything is how it is suppose to be! I have all my applications and my backgrounds and files intact!!! Add this in your tutorial if anyone faces the issue, flash the system files.
NextGenGTR said:
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work
Click to expand...
Click to collapse
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Jorge_007 said:
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Click to expand...
Click to collapse
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
NextGenGTR said:
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
Click to expand...
Click to collapse
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Jorge_007 said:
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Click to expand...
Click to collapse
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
Well you can install RAM Manager free from Playstore https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree&hl=en Go to "Extra" and select VM Heap Size it should read 128m. Also, listening to music should not be killed when multi-tasking. Apps such as iHeartRadio would always get killed when browsing the internet with Chrome. It doesn't happen anymore on my end. Also if you're not worried about your phones internal ssd from degrading you can set up a swap file to disk. Under Extra select swap file and delete the default directory and type "/cache" without quotes and set it to 256mb. It'll use the cache partition, so you'll still have your disk space for apps. It may degrade the life of your Moto G because of the constant writes, so it's up to you if you want to set up a swap. AND set it on Balanced on the main tab and check set on boot. Only do this on the stock kernel as I noticed lag on other kernels. Anyways you don't have to use swap or the ram manager app after your verify vm heap is 128m. I don't use it as just setting 128m vm heap no longer kills my music apps.
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Jorge_007 said:
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Click to expand...
Click to collapse
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
NextGenGTR said:
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
Click to expand...
Click to collapse
Okay, let me know how thing go
Jorge_007 said:
Okay, let me know how thing go
Click to expand...
Click to collapse
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
NextGenGTR said:
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
Click to expand...
Click to collapse
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Jorge_007 said:
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Click to expand...
Click to collapse
Currently with your settings + a build.prop code for the launcher to keep it in ram i am not experiencing any issues, also i have installed Rom toolbox pro which comes with build.prop editor and many other cool features, one being the minfree value changer, others have reported using the aggressive min free values from minfreemanager helps out so i am using that in romtoolbox and everything is in one single app so its nice and tidy, i recomend you give it a shot
Seems to work on lollipop as well!
Sent from my XT1032 using XDA Free mobile app
Related
Since i had a lot of PM of people who want explanation to install this ROM
I make this little thread for you.
Notice that i don t make this rom i only test it and make the nandroid image
to know more about that you can read the Mioze7Ae thread here
And for those asking for the performance I try almost all the rom and this is for me the fastest and (with the sileshn theme include) it s also the most beautiful...
I had between 70 to 80 Mo RAM available without swap. With swap i reach the 95 100Mo!!! (I attach my boot.img files too but it s the first fjfalcons').
Here you can find a tutorial to fastboot boot.img to enable swap.
And it works in multilangage (i don t know which but in english spanish and french without a problem)
To enable app on sd and swap you must have your sd part in this way: a fat32 part for the media / a ext3 part / and a swap part
You can find a video guide here on his channel(you will have to search a little but i remember its called 8min Linux...) made by reverendkjr
I make another image and i test it 3times (from sbf to the end...) so all works !!!!!!
For the beginners i will come back to the sbf.
1. SBF
So I m using the Singapore SBF I think you don t need it to get it work but it s better for those who have problem to change it too (it seems to work in every country)
So you can find the singapore sbf here
And you install it wiht RSDlite (do a google search): first put your phone in bootloader mode (when the phone is off you hold the camera and the volume up button while powering up) then you select your sbf and flash it.
2. Recovery
Now you have a fresh new system
You have to install the recovery
First of all you will have to install a file explorer form the market (you can use the one you want it will be deleted when flashing...)
Now you have to move the two apk(universal and root and openrecovery) i attach to this post in your sd
you can now install with your file explorer the apks.
Start with universal and root. Intall it and root your device.
Install the open recovery now. (Install it and install recovery system)
Now you must install Androidiani OpenRecovery I think it will work with out but it s easy and the recovery work better with it... So you just have to extract this zip to your sd (overwriting the similar files)
Now you have a working recovery. To launch it just go to open recovery and click on recovery boot (don t forget to copy the nandroid image folder in the sd card/ nandroid/openrecovery before you go to the recovery)
3. Restoring the nandroid image
Now you have a working AOR (androidiani openrecovery) and you have extract the attach nandroid image to sd card/ nandroid/openrecovery folder
Don t forget that nandroid need a folder name with out any space and in this folder you can only have .img or .md5 files.
So in Open recovery you go to nandroid / restore /
And if you don t change the folder name you must have CyanogenTI0808allupdates in the list
You select it and launch an restore all operation.
After that you come back to the first menu and wipe dalvik cache/ cache partition and wipe data / factory reset
Now you can reboot system. And it s done. Don t forget that the first boot is very long (about 5 or 6minutes)
CyanogenTI0808allupdates (the nandroid image)
(made and posted the 08/08/2011)
With all the new update from the official post (until the 08/08)
And the Twisted Inception theme from sileshn (with the update for the white text and the new battery icon)
You have to change the hour color (in settings / Cyanogen Mod / user interface / status bar) (from black to white)
Known issues:
- Fm Radio not working
- Media Gallery button not working
- Recovery boot (from the restart menu) don t work (you have to reboot holding the volume up button)
- Led notifications from the Cyanogen mod menu don t work but Led Me Know works
- Some users have issues with installing payed apps... I never have so....
Just a reminder to new readers: do not flash the fjfalcon boot.img. You have to use fastboot boot boot.img over USB every time.
Mioze7Ae said:
Just a reminder to new readers: do not flash the fjfalcon boot.img. You have to use fastboot boot boot.img over USB every time.
Click to expand...
Click to collapse
Thanks i think i will make a step by step tutorial for fastboot too. Maybe this week
B_e_n said:
Thanks i think i will make a step by step tutorial for fastboot too. Maybe this week
Click to expand...
Click to collapse
I think this is a good idea too. There is already a thread but it is buried in here somewhere and has gaone, as they all do, away from the initial intentions.
does the rom have native support for app2ext?
islubio said:
does the rom have native support for app2ext?
Click to expand...
Click to collapse
Yes It also support the OC on boot with milestone overclock
just installed this n this is so much faster compared to steelblue rom.
N guide was easy to understand. Just awaiting ur swap guide. Thanks.
is the froyo modding in the recovery workable?
how u get so many free ram? i only get 45-50 using adv task killer..
secret_tidus said:
how u get so many free ram? i only get 45-50 using adv task killer..
Click to expand...
Click to collapse
Without my apps i have 95 100Mo of free ram (with out the app2ext I have so nearly 100 apps and it take some ram...)
But with all my apps and with the swap enable I can get between 70 to 80Mo
I don t use advtaskkiller anymore i think it use more ram that it can free
I use autokiller memory optimizer (it change the settup of the android task killer so no useless use of ram) and to kill my apps i use the Go task manager (a widget from the golauncher app)
wat u set at the autokiller memory optimizer?
secret_tidus said:
wat u set at the autokiller memory optimizer?
Click to expand...
Click to collapse
Optimum settings.
But maybe someone have others settings better?
I know some use minfreemanager (already in the rom) but it seems the same than autokiller
b4 reboot the cm6 room was pretty stable... y after i reboot thn it started to freeze?
my 1st fastboot was pretty stable.. can run asphalt6... but the next time ll freeze... bcuz i install chainfire3d have to reboot and i have to fastboot again
even with fast boot i m only getting around 50mb of ram
Here is my Autokiller settings (user set, not pre-set and no fastboot). The work for me after many days/weeks of trial, error and monitoring.
16
16
64
64
70
94
I don't do a lot of gaming but I do listen to quite a bit of online media.
I average around 65-75mb all the time and at the very least 55mb when running Tune-in or Jango radios or Poweramp (memory hog btw but really good media player).
Side note: keep you widgets to a minimum. They eat RAM.
i just encounter some prob when swaped... for the 1st time i swaped it work fine and smooth all the way and no freezing but later on i reboot and try to swaped again my xt started to freeze when run certain apps...
Woodrube said:
Side note: keep you widgets to a minimum. They eat RAM.
Click to expand...
Click to collapse
i don't know about that, I went without widgets for the longest time cause everybody always told me how they eat ram and battery. Now for the past month or so I have had 1-2 widgets on each of my home pages and I really don't see much change. I am keeping the same amount of ram available and battery seems to drain the same. Not much difference, but I could be wrong I would have to go back to no widgets for a day or 2 and monitor my ram to be positive. I do know it isn't nearly as bad as what people say that kept me from using them to begin with.
B_e_n said:
Optimum settings.
But maybe someone have others settings better?
I know some use minfreemanager (already in the rom) but it seems the same than autokiller
Click to expand...
Click to collapse
I use both minfree and autokiller and they seem to work together, I set my autokiller and minfreemanager automatically copies the settings. Don't know if it does much good but doesn't do any harm. It seems to work good
LibertyMonger said:
i don't know about that, I went without widgets for the longest time cause everybody always told me how they eat ram and battery. Now for the past month or so I have had 1-2 widgets on each of my home pages and I really don't see much change. I am keeping the same amount of ram available and battery seems to drain the same. Not much difference, but I could be wrong I would have to go back to no widgets for a day or 2 and monitor my ram to be positive. I do know it isn't nearly as bad as what people say that kept me from using them to begin with.
Click to expand...
Click to collapse
Think of it this way. Say you have a 4x2 or 4x4 widget that is oh say MSNBC or Reuters newsfeed or your Facebook/G+ feed. These not only tax you home screen memory but they are always "running" too. If you have something like Widgetlocker where you can customize your lock screen and put apps or link on it directly, I have found that it munches free RAM really bad (14-17mb). So much so that I don't use it anymore (paid app too).
All a widget is is really just a custom icon that either monitors a running app/service, in which case it itself is running. Or it is running on its own, like a clock or feed or some kind.
Something like mClock or Battstat isn't too harsh, but 3rd party Keyboards can be quite draining too (I use Better kb and it is around 11mb but I like it and have had it since day one).
Good way to check is to go to Settings->Apps->Running Services and each will have the MB on the far right. Anything in double digits is hungry for your RAM.
I know you use that Go widget. Check out how much RAM it is using by going into settings and see if it is worth having it on there. Might be. You seem to be getting good RAM so is it aint broken don't fix it.
Hi All,
I'm new here but have been reading the threads since I got a Nook Color last month.
I'm booting from a 16GB microSD card: [CM7.2-RC0] MiRaGe - KANG build of CyanogenMod ("encore_CM72-MiRaGe-12122011") and also installed "gapps-gb-20110828-signed"
I ran the Battery Calibration tool just yesterday when it was plugged in and at 100%
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
I also followed the thread's advice on installing V6 Supercharger (http://forum.xda-developers.com/showthread.php?t=1344873):
Nook Color with its large kernel with many features consumes the RAM rapidly and low memory becomes an issue where V6 Supercharger becomes useful.
Here is how I install, it takes only one minute.
- Download update 8 to sdcard root directory.
- Start Terminal Emulator and do the followings
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 9
- choose option 16 to reboot
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Thanks in advance to any advice or answers! And of course, if you have any suggestions on other things I should be installing/uninstalling I'd greatly appreciate it!
AngelWings8 said:
I have a couple questions that I can't ask in the dev threads since I just registered here.
How do you check if V6 Supercharger is working? I didn't install BusyBox or Script Manager like the original V6 Supercharger thread suggested...so is there a way to do this through the Terminal Emulator?
What do you recommend overclocking your CPU settings in CyanogenMod settings to? I have mine currently set to Conservative, Min: 300 MHz, Max: 1100 MHz, and Set on boot. Would 1200 MHz be pushing it too much?
I've read some questions and threads on here regarding the Wi-Fi turning off when it goes to sleep. When you press the side power button to turn off the screen, is that also putting the device to sleep? Is there a solution to the problem of the Wi-Fi turning off on its own when the screen is off?
Click to expand...
Click to collapse
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
2. OC as much or as little as you want. 1200 is safe but some people say that the increased battery drain isn't worth the slight increase in speed. You have to decide for yourself.
3. Yes, that is putting the device to sleep, yes, that will turn off your wifi. Most people prefer sleep to just screen off because it saves your battery. The old CM7.0.3 and earlier didn't have sleep mode and you lost 1-3% of battery per hour of standby. If you're ok with that then:
wireless & network settings > wi-fi settings > menu > advanced > wi-fi sleep policy>never
Thanks a bunch! I was wondering why there wasn't an "Advanced" option when I went to Wi-Fi settings...didn't even think to press the menu button! I chose to set the sleep policy to "Never when plugged in" and we'll see if that works for me. Is the default "When screen turns off"?
yup, it's been the default on every android device i've used. It allows you to put your device to sleep and then turn it back on when you need it without having to wait for android to boot. I can tell when an app kept my nook from sleeping because my battery is dead.
I installed the Nook Color USB Mass Storage utility so that I could access the SD card from my computer
Click to expand...
Click to collapse
I don't think you (we) need this step since I believe the feature has been integrated into the latest CM7 builds, assuming MiRaGe the same.
1. Open your app drawer, flick the screen, if it scrolls instead of stuttering then V6 is working.
Click to expand...
Click to collapse
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
votinh said:
Without even installing V6 Supercharger, I don't believe that I ever experience the stuttering. If that's the case, how do I know the V6 script is working/running/better performance?
Click to expand...
Click to collapse
You can tell it's installed Ok by running it again and using option 1 to show the status.
Not so easy to tell its immediate benefit as its real job is trying to ensure that the memory is kept free, so you have to compare operation over time as more apps get used / loaded.
You know, I'm not sure if I ever experienced the stuttering either. I'll have to check later today.
If I just used the Terminal Emulator, would I essentially do these steps?
- su
- cd /sdcard
- sh V6*
- choose option 0 (fastest scroll)
- choose 1 (to show status)
- choose option 16 to reboot
Also, just want to confirm that you need to keep the V6 file in the sdcard root directory right? I'm assuming if you ever delete or move the V6 file, V6 Supercharger would stop working?
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
AngelWings8 said:
Oh I'm sorry, when I wrote "sdcard root directory", I mean the root directory of what you can access when you plug it in via USB and not the partition where you're booting CM7 from. It's essentially where I save all my folders of wallpapers/music/videos/etc.
Click to expand...
Click to collapse
Oh, ok.
Did you run the script yet? How was it?
No offense to the person that suggested checking V6 by flicking the app drawer, but there are a couple more reliable options.
I am no expert, by any means, but from looking over the program, it looks like all it really does is prioritize your apps by whether they are foreground or back, a launcher or hidden and so on, then allocate memory to the apps following that priority. I think any response check would wholly depend on how many apps you have running (or being killed by the V6 task killer)
Either way, even if it turns out that I wholly misunderstood the program, I can tell you how to see if it is installed and running for sure.
This will work if you have already installed the V6 or not. the following are directions for terminals, if you are running the dev's Scripter app, I would imagine it is similar, if not automatic.
Open a terminal.
su
cd sdcard/
sh V6*
the menu then scrolls. option 0 is often recommended here, but that is just a value for the scrolling speed of theV6 script itself. you can increase this number if you errant to spend a little time looking over what you're running.
f you think you have already ran the V6 look below the 17 options to current minfrees. If you want option 9 (Mirage Kang's recommendation) the current minfrees should read 6, 12, 75,100,125,150 mb. if it does, then you are supercharged. if not, go ahead and select option 9.
Now before you reboot, I would recommend that you run option 15 if you are not using Scripter. that will run V6 through the terminal emulator. That way, should you ever want to check your values or mess with the options, you can open terminal, su, then bash V6, and it will run.
Even if you don't think you will ever want to readjust the supercharger again, it had the added benefit of yelling you your "installation was INCREDIBLY SUCCESSFUL" which is bound to make you feel supercharged.
Run option 16 to reboot and now you can feel secure, without relying on a subjective flick of the app drawer.
Thanks everyone! I'm going to try uninstalling the USB Mass Storage app I downloaded then, if I don't actually need it with the CM7.2 version.
I did run Terminal Emulator to see what the minfrees were and it was the same as option 9. I didn't even think of running option 15, but I've done so now. After I rebooted, I opened up the Terminal Emulator again and typed "su" and then "bash V6" and it says "bash: V6: No such file or directory". Am I doing something incredibly stupid or wrong?
Also, do I have to leave the V6 txt file on the sdcard or can you delete it after you've run it?
I would bet it was a problem with case. bash v6 and bash V6 are two different things. Capital V should fix the issue.
Save the txt file, it is the actual script that is being ran. Without it, nothing happens.
I used bash V6 (and tried bash v6 just to see if anything would happen) and I got the same message. I thought maybe I just didn't do it right first time around, so I went back in, checked the minfrees and entered option 15 and then 16 to reboot, but when it did, it booted to the stock Nook Color OS. I just shut down and turned it back on and it went into Cyanogenmod with no problem...but is that strange that it didn't boot into CM? And once I got into CM again, I checked the overclock settings and it was back down to 800 GHz (even though I set it on boot at 1200 GHz).
votinh said:
By definition, "root directory" of the bootable CM7 uSD card is the one that has 117MB where ROM/GApp zip files used to be. If that, I don't believe that we (or NC) can access that partition. If it does, I want to know too.
With CM7 runs off eMMC, root directory of "normal" uSD card is ......... ehh, not in any sub-folder.
Can someone who actually do run V6 script chip in for some info?
Big thanks
Click to expand...
Click to collapse
That's a partition, not a directory. Every partition has a separate root directory.
With emmc, it's simpler because there's only one partition on the sd card so there's only one root directory. You can copy it over using usb or a sd card reader and it'll end up in the same place.
If you are running off the uSD, transferring files via USB places them on the "SDcard" partition on the uSD. That way, CF3D can find the files.
**I have a ton of apps, which may be the cause of my app drawer stuttering on flick (where you try to swipe to the bottom of your app list in one flick).
Thanks for all the useful replies! I uninstalled Nook Color USB Mass Storage app, and it seems to be working fine!
I saw that there is a new build for [CM7.2-RC0] MiRaGe - KANG and was wondering if you guys could kind of walk me through doing my first update. I downloaded both of these files listed in his first post:
- ROM - 01132012 build: MD5sum: 41676325569e773340378ba886dd6bf6
- transparency theme with circular battery indicator for 01132012 build. MD5sum: 9fb6a03e91f01c162a2f8f37cfe8ac77 Flash this theme after booting once with the new ROM. Do not use this theme with earlier or later builds.
For installation, it says "Just follow the official CM7.1 installation via recovery guide (stable or nightly). The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe."
I do have Titanium and I backed up using the "all user apps and system data" option. Is that adequate or is there a different option I should be using? Also, since he mentions that the removed components will be retained on the NC if you don't uninstall those...how do you know which ones and how do you go about uninstalling those? I never actually used the uNooter or ROM Manager...so I'm trying to figure out how to make it work with the method I used the first time around (VeryGreen's: http://forum.xda-developers.com/showthread.php?t=1000957) What I've done is just renamed "encore_CM72-MiRaGe-01132012" with "update-" in the beginning, put it on the boot partition, and rebooted into recovery.
wrong button click, LOL
Anyway, that should be it.
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
AngelWings8 said:
Yeah, my NC seems to be working fine after just renaming it to "update-" in the beginning of the files and booting it into recovery, but the transparent battery indicator theme didn't seem to do anything
Also, this is a random question, but do your NCs' volume rocker thing seem kind of loose? I was just wondering if that's normal because mine you can move left and right (you can kind of wiggle the button itself).
Click to expand...
Click to collapse
My volume button does that too.
Oh good, I was hoping it wasn't some sort of issue with the button being broken or something.
Also, I asked this earlier, but could someone explain to me what to do since after updating a new [CM7.2-RC0] MiRaGe - KANG build, he says "The removed components will be retained on your NC from the previous ROM if you do not uninstall those (Titanium recommended) or do a clean wipe. If you don't need a clean wipe, i.e. current ROM is CM7.1, instead of step 5 in the guide, do wipe dalvik-cache only."
Is that what I should be doing? How do I go about it using VeryGreen's method (without using ROM Manager or ClockworkMod Recovery?)
I'm sorry if I just sound like a complete noob, but I'm trying to learn!
Updated tweaks are at bottom of this post
Here is a flashable zip of 3 scripts that when put together speed up your phone and make it faster.
The niftyconiptionstweaks was meant only for the HTC Evo 4g but if your phone supports "init.d" then try it out if you want to and please report back. It may not even flash in recovery because the phones are different but its worth a shot. If it works, please post saying it does and what kind of phone you have. The Legit Zip should work for any phone.
To determine if your phone supports "init.d", download a file manager like Root Explorer or ES File Explorer, go to "system", then "etc". If you come across a folder named "init.d" then your phone may support it.
I did not write these scripts, I just edited them to work like Car-O-Dopes tweaks. It basically has the same values as Car-o-Dopes tweaks. It is best to use this on a Sense rom. I used the S97ramscript, KickAssKernel, and 02sictweaks but I changed the values of each script to match what Car-o-Dopes tweaks do, and I wanted to share this with you all because it makes installing these tweaks easier and faster. Thanks to zeppelinrox for the kickasskernelizer, Juwe11 for the S97ramscript, Smokinl1337 for the 02sicktweaks, coffehandle for giving me the idea when he made his own tweaks, and Car-o-Dope for coming up with the ultimate combination of out-of-memory settings and sysctl tweaks that make your phone smooth as butter.
I use this on my HTC Evo 4g running Shooter E3D, with AnthraX kernel and it works like a charm.
I am in no way responsible if your device messes up or anything unwanted happens to it. Use at your own risk.
http://dl.dropbox.com/u/40376256/niftyconiptionstweaks.zip
Instructions: Follow Exactly
1) Make a nandroid backup incase something goes wrong or you want to revert.
2) Download a file manager like Root Explorer or ES File Explorer (I use Root explorer).
3) Open up root explorer and go to "system", then "etc", then "init.d". Click on the "Mount R/W" button so it turns to "Mount R/O" (that way you can delete files).
4) Delete any or move to a folder on your sdcard (incase you want to revert) any ram scripts or ram tweaks you may have that is in the "init.d" folder (examples of ram scripts or tweaks are 01sysctl, 06sysctl, 02sicktweaks, S97ramscript, 99supercharge, and 98Kickasskernel).
5) Also if you are running v6 supercharger, you need to un-supercharge. If you are running Kickass Kernelizer, you need to un-kernelize and do not run those scripts while you have the niftyconiptionsscripts installed.
6) Uninstall any ram manager apps or task killers and do not use these.
7) After you uninstall all of that, reboot your phone and verify that none of the scripts you had before are still installed. (it will mess with the scripts you are about to install).
8) Boot into recovery (preferably Amon Ra).
9) Once in recovery, you need to mount /system, then mount /data.
10) Find the niftyconiptionstweaks.zip you downloaded and flash it.
11) After you flash the zip, go back and unmount /system. Don't mess with the /data because after you flashed the zip, it automatically unmounted the /data for you.
12) Reboot phone and enjoy. Let your phone set at the lock screen for about 2 minutes, unlock and let it set for another 2 minutes to let it settle in. Your phone will become dramatically smoother after about an hour.
UPDATE:
Nifty Coniptions Tweaks
Updated niftyconitpionstweaks. Install just as you would before and follow directions as posted above. I got rid of some unnecessary settings in the scripts. Also your sdcard read ahead speed will change to 512kb which is the optimal value for the evo.
Sense Version
http://dl.dropbox.com/u/40376256/Nifty-v1.01/niftyconiptionstweaks-Sense-v1.01.zip
AOSP Version
http://dl.dropbox.com/u/40376256/Nifty-v1.01/niftyconiptionstweaks-AOSP-v1.01.zip
The Legit Zip
http://dl.dropbox.com/u/40376256/Nifty-v1.01/TheLegitZip.zip
Here is The Legit Zip I just put together. This has the same settings as the V6 Supercharger on option 8 and the Kickasskernalizer. I did not change any values to these so its the same as installing those two scipts manually. Again, I did not write these scripts, I just put them into a tweak bundle to make it easier to install. Thanks to zepplinrox for making the V6 supercharger and the Kickasskernalizer. To install this, follow the same instructions in the first post.
To see if the settings stuck, download Rom Toolbox Pro and go to the performance tab, Kernel tweaks or Sysctl Tweaks (depending on what version of the application you have) and see if it reads as Min Free KBytes - 4096, Dirty Ratio - 95, Dirty Background Ratio - 60, VFS Cache Pressure - 10. Then go to the Auto Memory Manager and see if it reads as 6,12,150,165,180,200.
If you would like me to add another version of the V6 Supercharger just let me know.
Have fun and hit that thanks button if you like it.
Your script are compatible with android 2.X or 4.X ?
2.x
Sent from my Nifty Shooters E3D 4g while sick with Anthrax. Hit that thanks button if I managed to help.
scottypeterson said:
2.x
Sent from my Nifty Shooters E3D 4g while sick with Anthrax. Hit that thanks button if I managed to help.
Click to expand...
Click to collapse
so that means I can use it on my GT-I9001 2.3.6 customROM ?
Work great, tks so much
Sent from my LT18i using xda premium
does this slow down internet or the phone usage?
and does it work on the lg optimus s?
amskhan1 said:
does this slow down internet or the phone usage?
and does it work on the lg optimus s?
Click to expand...
Click to collapse
This does not slow down your internet and this makes your phone run faster.
Sorry, as far as I know it won't work on the Optimus S but you can use The Legit Zip i just uploaded.
Just updated the tweaks and added a new one. The Legit Zip. Hope you all enjoy. Hit the thanks button if you do
scottypeterson said:
Just updated the tweaks and added a new one. The Legit Zip. Hope you all enjoy. Hit the thanks button if you do
Click to expand...
Click to collapse
I'm asking again if will work on sgs+ (GT-I9001) with a 2.3.6 custom rom?
Sent from my GT-I9001 using Tapatalk
chasemyass said:
I'm asking again if will work on sgs+ (GT-I9001) with a 2.3.6 custom rom?
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Like I said in the OP. Idk if it will work or not for any other phone besides the evo, that's why I have it in this section to find out what phones it will work for. If it does, please report back, The Legit Zip should work with no problems though.
Sent from my Nifty MikG'd up EVO 4g while eatin some Chop Suey.
Hit that thanks button if I managed to help.
Hey am I suppose to flash this or use terminal bkuz terminal is not working
via rebel W/ a cauze rebel rom 2.1
dswaggz said:
Hey am I suppose to flash this or use terminal bkuz terminal is not working
via rebel W/ a cauze rebel rom 2.1
Click to expand...
Click to collapse
Flash it
Sent from a Nifty Tomatoe
Hit that thanks button if I managed to help
OK an should I kill any other ram type scripts or apps b4 doing so
via rebel W/ a cauze rebel rom 2.1
dswaggz said:
OK an should I kill any other ram type scripts or apps b4 doing so
via rebel W/ a cauze rebel rom 2.1
Click to expand...
Click to collapse
Yeah, read the op. All instructions are there. Just make sure you follow step by step except skip steps 9 & 11 on these updated tweaks.
Sent from a Nifty Tomatoe
Hit that thanks button if I managed to help
EDIT: This doesn't work on ODEX ROMs! That would be stock ROMs, as most custom ROMs are deodexed. If it is an odex ROM, you can do the mod, but you have to do it manually (the web app doesn't work). Check out the second post in the supercharger thread for a how-to. But if you are on a custom ROM the method in the video will work!
Alright, so I have been reading about how to supercharge ICS for awhile, but the process looked daunting. However I figured it out, and it works great! This will work on ANY ROM, so try it out!
I have been using this for awhile, and it's just super smooth. I've been using it a lot lately, and it hasn't given me a bit of lag yet! It's just gone!
What is V6?
V6 supercharger is a script that manages the RAM memory. This makes multi-tasking much faster, and it knows when to kill off apps that are taking a lot of RAM. This makes your phone a lot faster and more efficient!
Here is the person who made the script: V6 Supercharger
Here is a dl link to the script: DOWNLOAD LINK
I'm in! So... How Do I Do this?
Well I made a video for you:
Here are instructions:
1. Download the supercharger script from the link above and put it on the root of your SD card.
2. Get an app called script manager from the market. It's free. Open it up and click on the supercharge script from the list of what's on your SD card. Click the SU button, then hit run.
3. Go through the setup. Set scrolling speed to 1. When they ask if you want to integrate it into the system, say yes. You will get to a list of about 30 options after a little bit.
4. Select number 6 (I know I said 7 in the video, but 6 has better multitasking) for this phone, and hit enter. It will go through a whole bunch of stuff.
5. It will ask you to superclean and restart. SAY NO. You'll do that inn a minute. Just hit the home button.
6. Open the browser on your phone and go to : android.mimic.ca and hit the upload button. There will be a popup, select root explorer (Install it if you don't have it already). Go into system/framework/ and select the services.jar file. It will take you back to the website. Hit upload. The page will reload. Now select the CMW flashable zip option and download it. Go to root explorer and move that to the root of your SD card.
7. Reboot into recovery, wipe cache and dalvic, then flash the zip. Reboot. Done! Enjoy the speedieness!
Click to expand...
Click to collapse
Let me know what ya think!
Alright, so enough questions have been asked that I should start giving answers to them here.
Q. Do I need to re-flash the file in recovery if I want to make changes?
A. Not if you make changes to the the supercharger script (ie. change options). The only time you have to flash it is if you upgrade/change ROMs. Just remember to make a new one, and don't flash the old file!
Q. Isn't option "X" better/faster/easier on battery?
A. Play around with them and see what works for you. I like option 6. Not too aggressive, but it still keeps control. Just use the options that are for your phone (ie 512HP for this phone because it has that much RAM. So option 5, 6, or 7). I also use the nitro-lagnullifier. It makes things even faster!
Q. Does it affect battery life?
A. Yes, in a good way! I get better battery life.
Q. How do I know if it worked??
A. Open up script manager, and go to the supercharger file. let it run, and once you get to the menu with all the options, it will tell you if you are supercharged or not right below that.
Those were the most commonly asked questions. If they don't answer your questions then post 'em!
battery life
so this looks promising but how does it the effect on battery life with ICS.
works great... noticeable difference
cloud7a said:
so this looks promising but how does it the effect on battery life with ICS.
Click to expand...
Click to collapse
This shouldn't hurt the battery. I used to use it on my Epic fairly often especially once the Gingerbread leaks started coming out. There are several different routes to go with the script too. It can also be used to improve multitasking such as when you have multiple apps open at once.
Sent from my SPH-D710 using xda premium
cloud7a said:
so this looks promising but how does it the effect on battery life with ICS.
Click to expand...
Click to collapse
If anything it makes the battery life better. It's really a win-win!
thanks for the quick tut. I was gonna try using it on aokp as well, then i saw ics you had to do something extra and i just stopped looking into it lol - It's much easier than i expected.
Btw rocket, you should try the touch cwm recovery personally I think it's easier to navigate and use
Sent from my Nexus S 4G using Tapatalk
Thanks for the .zip. I was going to do this earlier but the instructions on the page here in XDA was kinda hard to understand >__>
EDIT - Anyone have a edited odex file for stock rom?
kyouko said:
thanks for the quick tut. I was gonna try using it on aokp as well, then i saw ics you had to do something extra and i just stopped looking into it lol - It's much easier than i expected.
Btw rocket, you should try the touch cwm recovery personally I think it's easier to navigate and use
Click to expand...
Click to collapse
I looked into it awhile ago, and it was even more complicated. The web app made it really easy.
I'll try the touch recovery out. I'll flash it through fastboot in a bit. I'm just used to this one from my EVO.
jokkir said:
Thanks for the .zip. I was going to do this earlier but the instructions on the page here in XDA was kinda hard to understand >__>
EDIT - Anyone have a edited odex file for stock rom?
Click to expand...
Click to collapse
Sorry I don't. I just use custom ROMs!
just installed along with the KAK
haven't had it for long, but first impression's that there's quite a lot more ram available on boot, and pretty smooth
thanks for your instructions! they were helpful
Thanks for the writeup and video. I tried this on my Evo a while back, but the thread was huge and difficult to navigate.
Just ran the script, so we'll see how it goes.
Awesome. Thanks!
Sent from my Nexus S using Tapatalk
Phone still needs to redraw launcher..
Sent from my Nexus S using XDA App
Thank you so much man. The original thread is a mess but you made it easy!
phone went into infinite boot loop.. =[
had stock ics w/ root. tried to do the ics mod. I think odex file but when i tried running the one click script, i think something went wrong when i rebooted
can someone please explain to me why in the instructions it says for me to upload my services.jar file to this guy's website???? That just seems very fishy!!
Why can't we patch the file locally??? Why does your server have to do it for me when an app could easily be written to do it without me uploading my services.jar to some random website I don't trust!
kwantran said:
phone went into infinite boot loop.. =[
had stock ics w/ root. tried to do the ics mod. I think odex file but when i tried running the one click script, i think something went wrong when i rebooted
Click to expand...
Click to collapse
you can't use the web app for odexed roms http://forum.xda-developers.com/showpost.php?p=16635544&postcount=2
hp420 said:
can someone please explain to me why in the instructions it says for me to upload my services.jar file to this guy's website???? That just seems very fishy!!
Why can't we patch the file locally??? Why does your server have to do it for me when an app could easily be written to do it without me uploading my services.jar to some random website I don't trust!
Click to expand...
Click to collapse
You can patch it manually. Check out the link in the OP. However, it requires unziping the file, opening it in notepad++, editing the code, zipping it back up, putting it back in the phone, and editing some stuff with terminal emulator. It's a bit over most people's heads, and the website makes it easy by making the patched services.jar a flashable zip.
If you want to do it, be my guest. It's all in the second post of the supercharger thread.
phone went into infinite boot loop.. =[
had stock ics w/ root. tried to do the ics mod. I think odex file but when i tried running the one click script, i think something went wrong when i rebooted
Click to expand...
Click to collapse
I have only used it on custom ROMs. The web app doesn't work for odex ROMs (stock), but it will work on custom ROMs. Try one of them out, it should work then. just titanium backup, flash new ROM, and restore backup. Won't loose your apps!
I can confirm this is working on the cyberg rom...my min ram is 144mb now under performance setting...my phones seems snappier now!
Imppy said:
I can confirm this is working on the cyberg rom...my min ram is 144mb now under performance setting...my phones seems snappier now!
Click to expand...
Click to collapse
Sweet! I have 125 MB min free. What setting did you use on the supercharger?
For those that remember @EarlyMon posted how to disable Swap long ago when the 5x was on Lollipop.
Well since the 5x has been updated to Marshmallow this method no longer works. So I started looking around for a solution
and I found this >> https://forum.xda-developers.com/moto-g4/development/mod-disable-zram-t3435613
Turns out this works just fine on the Honor 5x on Marshmallow.
If you'd like to give it a try, I have updated the files from the post above and uploaded them to my AFH Here
Here is a copy / paste of the instructions from the post above by @redbeard1083 ...Thanks Go to him and EarlyMon
We hate zram. This easy mod will disable it on the stock Moto G4 rom. In our experiences with disabling zram we've been able to notice performance gains on devices from 1-3gb of ram (Moto E 2015, Moto G 2014, Honor 5X, Huawei GX8).
8/13/16 Update: Now flashable via TWRP.
1. Have TWRP and MAKE A NANDROID BACKUP BEFORE YOU DO ANYTHING. I am not responsible if you break your phone. If you don't already know how to restore your device to the way it was when you bought it, do not do any of this.
2. Flash via TWRP:
Zram Off: https://www.androidfilehost.com/?fid=24588232905722629
To return to stock (I cannot promise this is exactly the same as the G4 Plus. If any G4 Plus users want to send me a hastebin of the /system/etc/init.qcom.zram.sh file to compare that would help).
Zram On: https://www.androidfilehost.com/?fid=24588232905722630
Old instructions if you prefer to do it manually:
1. Be rooted.
2. Have a stock nandroid backup.
3. Backup /system/etc/init.qcom.zram.sh to some safe place.
4. Unzip MotoG4_Zram_Disable
5. Using root file manager of your choice (I like Solid Explorer) copy init.qcom.zram.sh to /system/etc folder and overwrite the existing file.
This has been tested working on the XT1625 and likely works on the G4 Plus as well. If this works for you on a different variant, please leave a reply and I'll do my best to update this post.
Links:
Disable Zram: https://www.androidfilehost.com/?fid=24588232905722479
If for some unholy reason you'd like to turn it back on, follow the same process copying your backed up init.qcom.ram.sh file back to /system/etc.
Thanks to @EarlyMon for his edits that allow us to keep zram disabled without having to run terminal commands at every boot.
Click to expand...
Click to collapse
Again you can use my files or the ones from the original post (they both work)
Also Remember on the H5x you can Boot TWRP recovery to do the flash
Code:
fastboot boot kiwi_twrp_recovery.img
Have fun !
Reserved
thanks, I will try it.
one question tho, how can I know that zram is now disabled? like will I see an improvement in ram management or phone will be more fluid??
in my knowledge, zram manages the background process by compressing the actual process behind, (when the app is not running , but stays in the recent apps) and decompressing the task when we choose it..so this causes some lag.. and if we remove zram, the phone will be much snappy??
please correct me if I'm wrong.. thanks for your work
one question tho, im on b370 kiwl22 now, (the firmware which causes bootloops for custom roms), can i flash it??
thilak devraj said:
thanks, I will try it.
one question tho, how can I know that zram is now disabled? like will I see an improvement in ram management or phone will be more fluid??
in my knowledge, zram manages the background process by compressing the actual process behind, (when the app is not running , but stays in the recent apps) and decompressing the task when we choose it..so this causes some lag.. and if we remove zram, the phone will be much snappy??
please correct me if I'm wrong.. thanks for your work
Click to expand...
Click to collapse
I use Ram Truth to verify the swap is gone.
theirs plenty of discussion on if you want to disable it or not, start with the links i posted and follow it to the h5x thread on disabling swap
most people see an immediate improvement in the phone. zram is a stupid waste of CPU cycles on a phone with more that 1gb or ram
thilak devraj said:
one question tho, im on b370 kiwl22 now, (the firmware which causes bootloops for custom roms), can i flash it??
Click to expand...
Click to collapse
yes it should work just fine
clsA said:
I use Ram Truth to verify the swap is gone.
theirs plenty of discussion on if you want to disable it or not, start with the links i posted and follow it to the h5x thread on disabling swap
most people see an immediate improvement in the phone. zram is a stupid waste of CPU cycles on a phone with more that 1gb or ram
yes it should work just fine
Click to expand...
Click to collapse
thank you for the info and letting me know about ram truth
working like a charm.. I can see some performance improvements