• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

May fix some freezing issues

imdabest

Lurker
I found this thread on XDA Here is the link Click Here

Worked for me about a week no freezing phone fast on apps you can reverse if you dont see improvement. i saw improvement even though im sure its not really meant so our phones.

Here's a little tip that would give you more RAM on your device.

AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.

This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.

1) Open Terminal Emulator on phone or adb shell from PC and type the following.
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot


2) Add these to the /data/local.prop or build.prop. Add manually to build prop.
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=v

(Copy local.prop or build.prop to SD and edit them. Copy back afterwards. If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already, please modify them as above. Also type following in adb shell or terminal emulator.
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot


Advantages:


  • More free RAM.
  • Faster launch for system & user apps during the second launch.
  • Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
  • Smoother app switching.

Disadvantages:
  • Might break some apps.
 
I found this thread on XDA Here is the link Click Here

Worked for me about a week no freezing phone fast on apps you can reverse if you dont see improvement. i saw improvement even though im sure its not really meant so our phones.

Here's a little tip that would give you more RAM on your device.

AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.

This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.



Thank you so much. I haven't even tried this yet, but I'm glad someone else is trying to find a fix. I'll try this tonight, and if I get some substantial data, I'll post about it. :D Again thanks, and have a great night.
 
after i type rm /cache/dalvik-cache/* it says something about the directory not being found...whats up with that?
 
after i type rm /cache/dalvik-cache/* it says something about the directory not being found...whats up with that?

I had the same issue. I also had a bootloop on the first reboot. I seem to be over that. No issues so far; I'll let you know if anything cool happens.
 
I had the same issue. I also had a bootloop on the first reboot. I seem to be over that. No issues so far; I'll let you know if anything cool happens.

I got the same thing. Well without the bootloop. Anyways, I hope this works for you guys. :)
Oh also I'm running Reppards 092011 CM7 Rom.
I'm not sure if that might cause issues.
 
I had the same issue. I also had a bootloop on the first reboot. I seem to be over that. No issues so far; I'll let you know if anything cool happens.

so did you guys just try it again? and im on the sense rom
 
Mine just reboot again. The first time since last night. And after doing this.
I'll try it again. But if it reboots by tomorrow, I'll flash a different rom or go back to stock and try it with that.
Hope it works, I'll post what I've found.
Have a good day.
 
after i type rm /cache/dalvik-cache/* it says something about the directory not being found...whats up with that?


Mines said same thing but it still worked i think it would be better to do it from android sdk so you can just copy and paste whole thing at once. also don't forget to add to build props manually as in get you build prop file and edit it.
 
So I think I did this right. :confused:
Idk, but my phone hasn't reboot in two days.
Like I've turned it off once in the past two days.
So It has ran for 24hrs straight, twice now. :rolleyes:
I guess that's good, mostly just to test stability.
Dolphin sometimes crashes on Facebook though, but it happens.
(Anyways, they're always releasing updates)
So I'm going to keep testing.
Do you guys know any good productive apps?
Thanks.
 
Okay so the last 2 commands rm /data/dalvik simply delete the dalvik cache. I recommended using a2sdgui for those who had problems with this and just select rebuild dalvik. Make sure to mod the build properties and then delete the dalvik BEFORE REBOOT or you'll keep getting boot loops and strange results. Thanks for the finding this amazing little trick :) its severely improved performance of process draining apps like FPSE (psx emulator). I'm using Reppard's CM7.1 but I'm gonna use this from now on.

Note: This whole process is much easier with adb shell since you can enter the commands, adb pull the props and edit, then push the props back and reboot
 
Okay so the last 2 commands rm /data/dalvik simply delete the dalvik cache. I recommended using a2sdgui for those who had problems with this and just select rebuild dalvik. Make sure to mod the build properties and then delete the dalvik BEFORE REBOOT or you'll keep getting boot loops and strange results. Thanks for the finding this amazing little trick :) its severely improved performance of process draining apps like FPSE (psx emulator). I'm using Reppard's CM7.1 but I'm gonna use this from now on.

Note: This whole process is much easier with adb shell since you can enter the commands, adb pull the props and edit, then push the props back and reboot

I'm assuming you had the reboot issue. Has this 'fix' made a significant difference? Like how many days have you had this fix? and with out the reboots? Sorry about the questions, but I too am trying to fix my issue. I am also running the latest Reppard Cm7.
Thanks, have nice day.
 
I'm assuming you had the reboot issue. Has this 'fix' made a significant difference? Like how many days have you had this fix? and with out the reboots? Sorry about the questions, but I too am trying to fix my issue. I am also running the latest Reppard Cm7.
Thanks, have nice day.


Don't apologize for wanting to know...lol. Okay I've been rocking this fix HARD for about 2 days now. I did have the boot loops which is how I found the solution. It has improved performance on the gaming side of things. My quadrant scores improved by about 300pts without overclocking. So far its been very nice and when combined with the lowmem killer from a2sd its even sharper. You're very welcome and I hope this helps. I'll post anything I notice with this but I honestly think its stable now.
 
i did this last night and my RAM immediatly got worse lol...not much worse but worse none the less. Im pretty sure that i did this wrong. So where exactly do you find the build.prop? I am running the sense rom and I opened Root Explorer and went into system/build.prop and opened it in text editor and edited and saved it, then went into a2sd and clicked "rebuild dalvik" and then rebooted. Anything that can clarify this for me?
 
i did this last night and my RAM immediatly got worse lol...not much worse but worse none the less. Im pretty sure that i did this wrong. So where exactly do you find the build.prop? I am running the sense rom and I opened Root Explorer and went into system/build.prop and opened it in text editor and edited and saved it, then went into a2sd and clicked "rebuild dalvik" and then rebooted. Anything that can clarify this for me?

Build. prop is located in /system. You found the right file but I noticed we're actually supposed to replace the line dalvik.vm.dexopt-flags= with the new one. I think what's happened is both values are still present in build.prop and that's what's reducing your RAM. I believe the original line was dalvik.vm.dexopt-flags=m=y. Delete that one and replace it with dalivk.vm.dexopt-flags=v=n,o=v, then reboot into recovey, delete the cache and dalvik-cache, then reboot and everything should be good to go. Just make sure when you finish editing the build props with root explorer or move the .bak file to either the sdcard or just delete it.
 
yes the original line was dalvik.vm.dexopt-flags=m=y there were two lines that were exactly the same that said that so i changed both of them. Is there supposed to be two? and what about the other line dalvik.vm.verify-bytecode = false? do i still add that one? And is there a space on either side of the = because i cant really tell lol.
 
Yes you need both of the new command lines. No there's only supposed to be one dalvik.vm.dexopt-flags value. There are no spaces in any of the new values and they need to be seperate lines. Don't worry about messing up the build props on accident cause they're stored in the roms zip file that you flashed...they can be extracted with root explorer and copyed over :)

NOTE: You don't need to re-enter the terminal commands. They are set until you flash a new rom.
 
ok i extracted the build.prop from the zip of the sense rom and i am editing it from root explorer right now. Whenever i try to type it keeps changing things like "0" to an "I"...and the word "dalvik" to "symbol"...should i just let this happen?
 
No...that's your keyboard disobeying you. Its a little off topic but there's a sweet keyboard known as Hackers Keyboard on the android market. You should look into it as it offers a full PC keyboard in the palm of your hands.
 
Back
Top Bottom