Related
NO LONGER SUPPORTED
ODIN 1 CLICK TO STOCK JF6 BEFORE FLASHING 2.0[/B
Added updated flashable zip to bottom of post which includes some theme updates, apk updates and themes, and some window animations. This post will be hopefully be updated tomorrow with a newer version, and this clockwork flashable .zip should hold off those who waiting on the rom update.
first boot will take a bit.
This is a brand new rom ive been working on for the last few days. Based on newest i9000 froyo release UGJK3 (build date 11/18) and tweaked from there.
-SetiroN 1.5 kernel -user configurable OC up to 1460/default is 1200(go to 1400's at your own risk
-haptic feedback works on ALL buttons
-OC/UV support-voltage control app installed to /data/app
-BLN added and required lights.so lib added to /data/app
-apps and framework deodexed and optimized
-zipaligned
-rooted, busybox and sqlite included
-extended power controls(reboot, recovery, download)
-Captivate dialer, camera, etc. (no video chat references)
-Completely themed with pieces from all of my favorite themes(pics of theme seen HERE
-Fixed build.prop so protected apps can be seen on the market
-Big APN file for instant inernet/mms access
-ad-blocking
-AOSP themed lockscreen
-HSUPA enabled -comes with UGJK3 modem(no need to do anything crazy to get 850 working-this modem works as is)
-this rom will not switch back and forth between H and 3g, the symbol should stay on 3g even if hsupa is enabled and working
-comes with SWYPE, dark Droid X multitouch keyboard, and samsung keyboard
-Launcher Pro and TWlauncher included in /system/app
it seems like Samsung took some advice from gtg with the twlauncher(never seen the stock launcher this fast or smooth)
-removed some junk apps
-added
voltage control 2.0
cyanogen MMS (switch background color-white/black)
updated maps and youtube
flash player will auto-install
Starting with v3.0, d1g1talphyre will be helping with all future versions of the rom. Im going to be extremely busy is in the upcoming weeks so this will help me get 3.0 out faster to you guys.
3.0 changelog-
http://forum.xda-developers.com/showpost.php?p=9876005&postcount=597
3.0.1-only difference is the power menu fix. there is a .zip for those who have 3.0 already around page 76 or so.
here is a link to a circle batt mod made by d1g1talphyre. this framework-res.apk will only change the circle batt and thats it. rest of the theme is the same.
http://forum.xda-developers.com/showpost.php?p=9946605&postcount=790
DOWNLOAD v2.5
version 2.5- http://www.multiupload.com/OTOQ25Z1RQ
version 2.5 w/ XT kernel- http://www.multiupload.com/FD2Z204LEB
version 2.5 w/ 1280 mhz kernel(the other two go from 1200 to 1360) http://www.multiupload.com/CQDGPI8BX2
version 2.5 w/ xcaliberinhand's kernel-full voodoo all partitions(untested by me but should be fast.) NO OVERCLOCK http://www.multiupload.com/JX166BH191
changelog for v2.5-
-theme update throughout whole rom
-few more themed apps
-new themed keyboard
-update build.prop so apps know phone is a captivate(apps like mobiTV and things like that should work now)
-updated swype for voice to text
-browser with user configurable user agent in settings menu
-kernel updated to setiron's v1.5 -OCable to 1460mhz, default is 1200 unless you change it(go to 1400's at your own risk-my phone runs fine with it-most will probably not)
-updated xan's voltage control to v2.0rc2
-all window animations added except for bounce-credit to [email protected]
probably some more small things that i forget right now.
When you apply your lagfix, choose option one when prompted "backup AND restore"
Install Instructions:
as always, its best to flash to stock JF6 with the odin one click downloader.
copy this rom to your internal sd card, and after flashing stock. flash this through Clockwork Recovery. thats it. no need to do anything with the jg8 modem or anything like that.
on first flash, all=ext4 is enabled by default-if you want to use something else, select go back to recovery then go to the lagfix options and enable whatever you want. when your prompted with the options about backing up, i suggest choosing option 1. this will do a backup and restore so you will not lose any apps(the other options you will lose the apps in /data)
credits:
SetiroN for his kernel
Reefermattness-used some of his icons for dialer and his setting icons
http://forum.xda-developers.com/showthread.php?t=813497
Demented71 for boot animation
[email protected]
samcrow-some images
Credit to xcaliberinhand-he made the original kernel for us to be able to use i9000 roms and hsupa modems
Been looking forward to this.
Thanks, I'll try it tonight.
+1
i hadn't planned on it, but it looks like i'll be flashing today
sweet! downloading and flashing @ work, excited to test.
I couldnt apply lag fix right away had to reboot first ... BUT it did tell me my configs changed ???? ... I chose option 1 and noticed it set up like this
ext4
rfs
ext4
false
false
false
false
?????
booting up was about 2 minutes on android logo
reboot to recovery then fix it to no rfs advanced ... ( all jfs )
looking good I previously dropped this rom because of modem giving me issue
will set my stuff and report back if needed .
PS why is the Fm app always in your rom ? do you hope it will work at one point ?
looks great yay launcher pro included
you few that download already, here is a better videoplayer.apk. it doesnt fix the problem, but at least youll be able to view your recorded videos from /sdcard-dcim-camera. still looking at problem and trying to find a fix.
from this point on this video player is included with the rom.(reuploaded)
DAGr8 said:
I couldnt apply lag fix right away had to reboot first ... BUT it did tell me my configs changed ???? ... I chose option 1 and noticed it set up like this
ext4
rfs
ext4
false
false
false
false
?????
booting up was about 2 minutes on android logo
reboot to recovery then fix it to no rfs advanced ... ( all jfs )
looking good I previously dropped this rom because of modem giving me issue
will set my stuff and report back if needed .
PS why is the Fm app always in your rom ? do you hope it will work at one point ?
Click to expand...
Click to collapse
some people have said if that app is removed it can cause problems. if you dont like it, remove it from /system/app.
first boot will take a while as it zipaligns and deodexes.
and btw this rom has nothing in common with my other di11is darkyy rom except my theme. this is my own base.
Ive been running your darky rom 2.0.1 for a day with the jk3 modem. Downloading now to check out the CM mms. I hope its the one with the notification vibration types like multiple long.
Athailias said:
Ive been running your darky rom 2.0.1 for a day with the jk3 modem. Downloading now to check out the CM mms. I hope its the one with the notification vibration types like multiple long.
Click to expand...
Click to collapse
It is
Dhfhdjdjd
did anyone notice or this only happen to me? home button doesn't function & no lockscreen.
akachay said:
did anyone notice or this only happen to me? home button doesn't function & no lockscreen.
Click to expand...
Click to collapse
I flashed this again before I uploaded and didn't have this problem. Let me reflash and try to recreate
di11igaf said:
I flashed this again before I uploaded and didn't have this problem. Let me reflash and try to recreate
Click to expand...
Click to collapse
thx bro. was planning on reflashing myself to verify.
My home button didnt work either, not sure about lock screen. Flashing back to stock now.
My home button worked fine. hmmm, also I can confirm the video player.apk in the first post for us couple who downloaded early is letting me play video. But just as stated, can only open it from file manager to view.
great rom so far, its fast. Yes, I did run benchmarks, not that they really matter anymore. can notice the difference in speed when deleting widgets, open anything. It screams, props di11igaf, awesomely quick rom.
akachay said:
thx bro. was planning on reflashing myself to verify.
Click to expand...
Click to collapse
just downloaded my own file, reflashed to stock put the downloaded file on my sd and flashed again with no probs. first thing i did though was apply lagfix and when the backup and restore options pop up make sure you choose the first option to backup and restore all data.
let me know if you do reflash this if you have the same problem.
d1g1talphyre said:
My home button worked fine. hmmm, also I can confirm the video player.apk in the first post for us couple who downloaded early is letting me play video. But just as stated, can only open it from file manager to view.
great rom so far, its fast. Yes, I did run benchmarks, not that they really matter anymore. can notice the difference in speed when deleting widgets, open anything. It screams, props di11igaf, awesomely quick rom.
Click to expand...
Click to collapse
thanks. im still looking for a fix for that. while i was trying to fix it i just accidentally deleted my whole damn DCIM folder lol. all pics and vids gone.
hopefully i have most of em backed up.
di11igaf said:
just downloaded my own file, reflashed to stock put the downloaded file on my sd and flashed again with no probs. first thing i did though was apply lagfix and when the backup and restore options pop up make sure you choose the first option to backup and restore all data.
let me know if you do reflash this if you have the same problem.
Click to expand...
Click to collapse
preciate it, will try later. problem probably because i apply lagfix "without backup and restore."
ahh ya i bet thats why. not sure why it really would matter(since the problem your describing would be an android.policy.jar problem) but im gonna try it that way and see if it makes a difference. thats the only thing different that we did though.
also i think if you apply the lagfix that way, any apps in the rom that are in /data/app by default will not be restored-at least this has happened to me in the past and why now i always do a backup and restore.
I did a yes without backup and restore, and the home button ain't workin.
This version is now discontinued. find the data2ext version or tmous version here
http://forum.xda-developers.com/showthread.php?p=10503046
RAFDROID HD 2.0 - NAND VERSION
Click to expand...
Click to collapse
--- FIRST OF ALL, PLEASE READ POST 2 FOR UPDATED FAQ. IF YOU HAVE QUESTIONS OR ISSUES, MOST PROBABLY YOU WILL FIND THE ANSWER THERE WITHOUT NEEDING TO POST A NEW MESSAGE ---
I'm not a dev. I'm just a curious user that want to learn, fail, search, retry, fail again and then succeed also thanks to people here that helped me with tips and knowledge sharing
This is a personal build made for my self, based on DESIRE HD.
Is 90% stock, % battery indicator and some animations/icons.
It's fully DEODEXED so you can theme it as you want.
I tried also to keep most of the apps, wallpapers and other stuff in it.
But most important it uses DATA.IMG on SDCARD so you dont have to worry about storage limite on LEO512
Please note: this, as happenend whe using Android from SD, could cause data corruption and causes a little lag during app installation. There is nothing I can do to solve those two issues. You are warned!
Credits and thanks:
-Cotulla and DFT for making all this possible
-darkstone for his big help
-mdeejay for initrd.gz (modified by me to support data.img) and kernel
-Kouno.Takaaki for his idea and init file
-Rajko
-crawling
-ocm
-Cass
-cedesmith
-domineus
-imilka for help me solving wifi issue
-all people on #htc-linux
and probably a lot of other people I'm forgetting
FEATURES:
- Deodexed and Zipaligned, not sqashfsed
- Latest kernel
- RMNET
- Multilanguage
- Rooted (SU app + permessi SU)
- AdFree
- 5mpx camera with face recognition + 800*400 camcorder
- HSDPA, GPS, Bluethoot, WiFi all working
- % battery icon and status bar icons changed (use original framework-res.apk to go back to stock attached in 2nd post)
- fonts changed (use original fonts to go back to stock attached in 2nd post)
- Working HTC-SENSE.COM (at least for me)
- data.img on SD support
WHAT'S WORKING
Everything except stock HTC Reader (removed)
CHANGELOG
Code:
2.0
New base Desire HD 1.72.405.3
RMNET
Rooted (su + Superuser APP)
Bootanimation changed
Bootsound changed (very very low, just a "beep")
Auto APN
AdsFree (updated)
New Advanced Power menu (credit to reef2009)
New initrd/data2sd system (credit to Takaaki.Takuno)
some minor tweaks & fixes
1.0 - Initial Release
Based on RUU 1.32.405.6
Removed HTC E-Reader
Removed SoundHound
Removed AmazonMP3
INSTRUCTIONS
- You need at least MAGLDLR 1.10
- Download the Data size package you want
- Unzip it and copy all the content to your SD root respecting the folder structure. Insert the SD in the HD2
IF YOU NOT DO THIS BEFORE, YOUR INSTALLATION WILL FAIL
IF YOU ARE ON A 1024 LEO YOU CAN AVOID THIS.
- Download the RAFDROID HD package
- Unzip it on your computer, enter in MAGDLR bootloader, choose USB flasher, connect your HD2 to your computer and use INSTALL.EXE
- Wait the rebooting. Keep always the SD inside.
- First install takes up to 5 min
- Enjoy
- As all HD build, initially this will be slugghis and lagging, specially if you select to restore your google settings. The build will become fast after some hours and a couple of reboots.
DOWNLOADS
Click to expand...
Click to collapse
WARNING 1) Data system changed between RafDroid HD1 and RafDroid HD2. Now you need a "config.txt" in the data2sd folder. I suggest to old 1.0 users to download the new packages here to be sure that all works.
WARNING 2) I assure compatibility only with 512 and 1024 data images. Using bigger images, specially more than 2gb, could cause issues (no boot, errors installing apps...)
WARNING 3) I suggest always to start with a fresh data.img. Anyway you can try too keep your old data.img but I cannot assure you that you will have no bugs. Important is to keep the "data2sd" folder with the config.txt inside.
DATA PACKAGE for RAFDROID HD 2.0 512MB -> http://www.multiupload.com/MA47VX8ALS
DATA PACKAGE for RAFDROID HD 2.0 1024MB -> http://www.multiupload.com/6BA2EZ49L0
RAFDROID HD 2.0 -> http://www.multiupload.com/CLK8LXQG0M
--------------------------------------------------------------------
DATA PACKAGE 512MB -> http://www.multiupload.com/F91OFAFDX7
DATA PACKAGE 1024MB -> http://www.multiupload.com/GWRDNTXALF
RAFDROID HD 1.0 -> http://www.multiupload.com/P2AWG7IRR7
If you need more space, you can replace the data.img with ones bigge but I NOT SUGGEST THIS. We have clues that data.img bigger than 2gb causes issues. So please, if you want to avoid bugs, stay with 1gb maximum that is plenty space for everything.
DONATE:
Click to expand...
Click to collapse
I dont think it's fair to ask for donations because all this was possible thanks to the people credited above.
Anyhow, because some one pm'ed me asking to donate, and becouse I spent a lot of time in this, if you want to buy me a coffee for all the time I spent, you can do this here DONATE
Anyway I would suggest to donate to Cotulla and DFT team and other devs.
BE ADVISED: THIS BUILD, CAUSE IT'S SIZE, WILL WORK ONLY WITH THIS METHOD OF DATA2SD. IT'S TOO BIG TO WORK WITHOUT IT. EXCEPT FOR 1024 LEO WHER IT *SHOULD*(MUST BE TESTED) WORK WITHOUT DATA.IMG
If you want DesireHD standard fonts, download this package and replace the entire /system/fonts content with the ones included, using droid explorer or adb, after first boot
http://www.multiupload.com/5EXLIPO3N4
If you want the stock look this is the stock framework-res.apk. i will not explain how to mess with it, google if you dont know. anyway be careful. messing with this file could cause loop reboots and you will have to reflash
RAFDROID HD 2.0 -> http://www.multiupload.com/EBTBFZV8F8
RAFDROID HD 1.0 -> http://www.multiupload.com/889C7U9B0T
FAQ - QUESTIONS and BUG FIXES
PLEASE READ
Click to expand...
Click to collapse
q) I'm having high battery drain
a) Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
q) It's really laggy!!!!
a) as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
q) I have no GPS or the fix is really slow
a) Firs fixt can take up to 5 minutes. just wait. If still not works, try to change the gps zone in the config.txt (read below)
q) I have low quadrant scores
a) yes, this is true. This is because data sync is enabled by default. You can try to disable it but this will give you more risks of data corruption.
q) Can I unmount the SD while in use or connect the phone as mass storage to my pc while in use
a) No. This will cause data corruption. Power down the pone and use an SD card reader to copy your files.
q) I have no SU permission!!!
a) Install z4root (google for it) and execute permaroot. Reboot.
q) It not boots
a) be sure that the ".config" file is in your SD on the root. and there is also the folder "data2sd" with "data.img" inside. If still no boot, try to reformat your SD card, copy the img again, and retry.
q) I have no data/3G/HSDPA
a) probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
q) How do I remove BOOTSOUND / How do I change bootanim
a) bootsound and bootanim are located in /system/etc/customer. Just delete android_audio.mp3 if you dont want sound
ABOUT THE CONFIG.TXT FILE
Click to expand...
Click to collapse
You can change some parameters directly in the config.txt before booting:
Code:
data_sd=0
- 0, default, use nand userdata, THIS WILL CAUSE NO BOOT for 512 LEO
- 1, enable external data.img support (/sdcard/data2sd/data.img)
data_size=512
- size of data.img, only work when data.img support enabled and first install if you dont have a data.img.. it will create for you. No need to specify it if you already have a data.img in the data2sd folder
data_sync=1
- 0, fast, default, disable sync option when mount data.img MAY CAUSE DATA CORRUPTION. I SUGGEST TO NOT USE THIS
- 1, safe, enable sync option when mount data.img, use this if experiencing data corruption
lcd_density=240
- size of icons
gps_zone=europe
- country string for better gps fix. you can find your country code here [URL="http://www.pool.ntp.org/zone/@"]http://www.pool.ntp.org/zone/@[/URL]
Having the DATA PACKAGE 1024MB now Waiting For the RAFDROID HD 1.0 now
Hey man, you're really rock Wonderful Rom, everything is work fine on my HD2 ! Now I'm having 2GB data.img on my sd card it works man, you are right now i got no worry about storage limite on LEO512
Thank you so much !!
Good to hear you fixed all those bugs, hope it's quick!
Nice, but could you also provide us with stock framework (so it can be 100% stock lol)?
and can we use Kouno's method of modifying /system with "update" folder on sdcard?
Thank you very much. I need it so
mmmm.. i wanna try this build.. mmmm
nice raf
oh.. why mdj kernel?
Krendelrus said:
Nice, but could you also provide us with stock framework (so it can be 100% stock lol)?
and can we use Kouno's method of modifying /system with "update" folder on sdcard?
Click to expand...
Click to collapse
not at the moment
I will check to update this in the next release
Wooooow
Fantastic HD2 scene!
Thanks Raf
PS: I would like too, in future a stock framework.
if you can provide some SCREENSHOTS also.i am looking forward to this,specially extra memory part is cool.
rafpigna said:
not at the moment
I will check to update this in the next release
Click to expand...
Click to collapse
thanks for replying
why you're not using latest Ace RUU (RUU_Ace_HTC_WWE_1.72.405.3)?
you can get it here http://forum.xda-developers.com/showthread.php?t=879375
isnt it better to have PPP rather than RMNET because RMNET is slower.
having said that, has there been a fix for PPP because im lossing network bar frequently.
BTW thanks for the build, will be testing it out soon
When is this boiled going to be out? I wanna try out this build as I can't seems to install much of applications on any otherbrom asnitbonly gives me less then 100mb. And nownthe current remaining soqcenisnlessnthen ten mb. Can't waitbto try out a new and a better rom. How aboutbthe cam coder is the quality better?
Krendelrus said:
thanks for replying
why you're not using latest Ace RUU (RUU_Ace_HTC_WWE_1.72.405.3)?
you can get it here http://forum.xda-developers.com/showthread.php?t=879375
Click to expand...
Click to collapse
guys, because initially I made this for myself.
Now that is released I will try to update it in the nexts
rafpigna said:
guys, because initially I made this for myself.
Now that is released I will try to update it in the nexts
Click to expand...
Click to collapse
ok, got it
rafpigna said:
guys, because initially I made this for myself.
Now that is released I will try to update it in the nexts
Click to expand...
Click to collapse
Good work Raf, been waiting for this. I've downloaded the data package and was wondering if it will be possible to use my old data.img file from another SD HD build and possibly use a 2GB data.img file too?
daysey said:
Good work Raf, been waiting for this. I've downloaded the data package and was wondering if it will be possible to use my old data.img file from another SD HD build and possibly use a 2GB data.img file too?
Click to expand...
Click to collapse
Dont know.. maybe there will be bugs, but try it.. if this not work or you have bugs, delete all things from SD, reflash NAND, and start again
about 2gb data, yes, you can. just replace the file. I will upload 2GB and 4GB for convenience, later as soon I have time
This build will be awesome when it runs correctly... Is it right, it uses for data the data.img on the sd card, when you release a new uodate we can safe our data and can make a update without loosing my apps ? This will be great news ?!
so will all my texts get saved to the sd card?
as on other NAND builds my phone can barely operate after a couple days use due to insufficient storage.
also, what determines whether I should get the 512MB or 1024MB data package?
manish2039 said:
isnt it better to have PPP rather than RMNET because RMNET is slower.
having said that, has there been a fix for PPP because im lossing network bar frequently.
BTW thanks for the build, will be testing it out soon
Click to expand...
Click to collapse
Not true,atleast not for me. (the build i use in my sig)
Sinds NAND rmnet is as fast for me as ppp,same up and download speed.
In the time with sd card builds ppp was faster for me,now not (for me)
Just test it with speedtest.net app in the market for free
first what i do when i flash a new rom.
1. i install system app remover,and uninstall all apps i dont use.such as radio,DSPmanager,voice dialer,voice search,email apk.
2.for speed improovement:if you know and want to overclock your phone its ok.but dont expect your battery to last two days.it will last one day,maybie lower.it depends on wich frequency you set.i think 710Mhz is the best frequency.juwe's ram script is also good,but use v6 supercharger.it blasts.i dont use overclock,but still i get 1200+ quadrant points.
3.battery save:use program fast reboot from market.it frees ram,and kills background running apps.undervolt-lowering cpu frequency.your phones battery usage will be much lower,but expect some lag and your phone will be slower.but overall its not worth it.
battery calibration.you can do it manualy,but i use a program from market.its all explained there.use juice defender,it helps a little.
4.for those who dont know how to use supercharger script!
1,download this attachment from this post: http://forum.xda-developers.com/showthread.php?t=991276 (third attachment,its called like this txt V6_SuperCharger_for_Android-update8.sh.txt
2. put it on your sd card,and rename it to v6.sh
3.run terminal emulator,type su,then enter,and you will be prompted for superuser permission.click allow.
4.type in this command: sh sdcard/v6.sh
5.then its easy later,choose an option you want.
If you brick your device with it,its not my problem.if you dont feel safe,dont use it.i never encountered any problems.
OVERCLOCKING!
ok it seems like every starter vonders how its done.so lets start.
1.download the attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1020313&highlight=overclock+module the attacment is called x8oc-v004.zip
2.copy the x8oc.ko from your sd card to system/lib/modules using root explorer.
3.now go to system/etc folder,and find file that is called hw_config.sh,long touch on it,then choose an option "open in text editor".
4.now when you opened it,put in this line in top- insmod / system/lib/modules/x8oc.ko # x8 overclocking
5.save changes,and go to setcpu app and choose how much you want to overclock it.for me the best frequency is from 710Mhz to 787Mhz.but you can go higher.
Tell me if i forgot something,and most importantly,dont TROLL!I am only here to help.
so here it is in short.i hope i helped
Thanx alot mate for your effort, here's what I do :
1. Advanced Task Killer
2. Memory Manager
3. Battery Booster
That's it... and I've found 40% boost in battery timing...
Use app called fast reboot.because task killers spend more battery.
xperiauser132 said:
2.for speed improovement:if you know and want to overclock your phone its ok.but dont expect your battery to last two days.it will last one day,maybie lower.it depends on wich frequency you set.i think 710Mhz is the best frequency.juwe's ram script is also good,but use v6 supercharger.it blasts.i dont use overclock,but still i get 1200+ quadrant points.
Click to expand...
Click to collapse
how to use it on x8??
1. post updated,check it out.
ok , I unistalled all those three apps and trying fast reboot , will check if it improves battery or not, but it's causing 1 problem though , whenever I hit fast reboot I got a notification on status bar "Data traffic Disabled" and 1 Missed called...
while I've already cleared those two notifications by using that clear button on status bar...
I did disable data traffic intentionally !! why is that ?
p.s by celebrating battery you mean wipe battery status after a month ???
I never had that issue with fast reboot.and battery calibration is somethong like this: charge the battery to 100%,then use it untill the phone shuts down,and charge it to 100% again.its the manual way.but download the program from market called battery calibration,its easier.
I tried the Supercharger script a week ago on my FroyoBread and choosing option 4 (balanced) would just make launcherpro loop-crash when i booted the phone and then after a while just reboot itself and repeat.. It totally broke everything... How come?
Some options dont work good with x8.try using agressive 1 or agressive two.try to experiment with various options.it cant harm you.for me,the best is agressive 1,or megaram.
xperiauser132 said:
Some options dont work good with x8.try using agressive 1 or agressive two.try to experiment with various options.it cant harm you.for me,the best is agressive 1,or megaram.
Click to expand...
Click to collapse
Yes, it does harm me because when it ****s i cant use xrecovery or anything... I have to reroot and everything all over again.
Sorry man,i didnt know.it never happened to me,and i tried all options.
sorry bro,but i never had that problem.
and now i have exactly the same problem..i cant boot neither to ROM or xRecovery or CWM..what can i do now??
Flash it again with seus.
i actually did the thing, just some hours ago no issues, i chose multitasking.
seems to be pretty good!
And how exactly will i update with SEUS?..as i said earlier i cannot boot to rom..i had floyo 2.2.5 v1.0..and i can't load to xrecovery..and the phone must be connected first to pc companion to recognize the phone and fw version..to do that, the phone must be powered on and functual..hmm..is there any way to bypass that and go straight to flash an x8? i thought about using another x8 but i cannot find any
sokopa said:
And how exactly will i update with SEUS?..as i said earlier i cannot boot to rom..i had floyo 2.2.5 v1.0..and i can't load to xrecovery..and the phone must be connected first to pc companion to recognize the phone and fw version..to do that, the phone must be powered on and functual..hmm..is there any way to bypass that and go straight to flash an x8? i thought about using another x8 but i cannot find any
Click to expand...
Click to collapse
Assuming your phone is off, hold the back button and connect it to the PC via USB. The green LED should light up. PC should recognize it as flash mode or some such thing. When you run SEUS and it says connect your phone to the PC just do this and proceed with it. Then re root, xrecovery bla bla youre good to go
As for supercharger, for minfrees to stick you have to run the script everytime you reboot and the best setting for daily use is Balanced 3 (option 6) Ive pretty much tested all of them.
@xperiauser132 there is a instalation problem on supercharger
correct installation for supercharger:
1.use script manager Download:Here
2.Press menu --> more --> Advanced options --> config tick Browse as root
3.Run v6.sh from sdcard dont forget to check run as root
4.choose an option you want
5.select reboot (number 16 on supercharger option)
6.re-run the script (v6.sh)
7.again choose an option you want
8.Type exit (17)
9.go to /Data find 99supercharger.sh --> open as script Tick run as root and run at boot Save (for stock only (2.1) )
10. reboot
Well, I've tried this supercharger thing, and for me, at least, there was no improvement, if anything, the phone was slightly worse - with quadrant giving me an average of 34 points less compared to how my phone normally runs - using GingerDX v010 at 710Mhz on Smartass.
Maybe i'm doing it wrong?
Backed up phone now to pre-supercharger status.
Impster
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!
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