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

Root Speed Tweaks

A

AaronEmoBoi

Member
IF YOU HAVE BOOST MARQUEE DO NOT USE THE SHORTCUT WAY ENTER ALL THE LINES OF CODE MANUALLY

Okay guys so i stumbled onto a speed tweak technique and well it works i tried it and used it and i do see a noticeable difference in the marquee now im going to explain how to do it

If you have a sprint marquee and would like to have a shortcut to do this download the Attached build.prop and backup your and replace it with mine Boost cannot do the shortcut method since the Build.prop contains carrier info needed for the phone so if you run Boost's Marquee you have to type it all out sorry guys

Each one of these lines of code needs to be on a different line when your in the text editor it will change the :-) key into a enter key to give a new line so yeah

you need a File Explorer with root privileges perferably Root Exporer (attached below )
1. go to /system directory (open Root E and go to system folder )
2. mount R/W
3. Find in the system folder build.prop , its a file then long press it and click open in text editor
then you will have a long list of lines of code dont erase anything or add anything other than what i tell you too

Force Launcher into memory:
ro.HOME_APP_ADJ=1

Raise JPEG quality:
ro.media.enc.jpeg.quality=100

VM Heapsize; higher the RAM, higher the hp can be:
dalvik.vm.heapsize=48m

Render UI with GPU:
debug.sf.hw=1

Decrease dialing out delay:
ro.telephony.call_ring.delay=0

Help Scrolling Responsiveness:
windowsmgr.max_events_per_sec=150

Save Battery ( three of them each in a different line )
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0

Increase overall touch responsiveness:
debug.performance.tuning=1
video.accelerate.hw=1

Raise Photo and video capturing quality:
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000

Fix some application problems:
ro.kernel.android.checkjni=0

Disable boot animation for faster start up (optinal i havent tested it)
debug.sf.nobootanimation=1

so yeah type these into your build.prop then press menu button then save changes and it will make a auto backup of your current build.prop
View attachment 27541
build.prop
 
Since you've said you've already tested all except debug.sf.nobootanimation=1, I decided I would be the guinea pig.
It works on my Sprint Marquee. Shows the LG logo as normal, then proceeds to a black screen, then boots to lockscreen/homescreen. Took my phone about 25 seconds to boot.
 
I am not noticing any differences as of yet...just finished a few minutes ago. Typing all of that was not fun lol. Getting rid of the boost logo is nice though cause that was annoying.
 
I've been a Blackberry for some years now ... I a Network Engineer. Can someone post a simple how to root my Lg Marquee on Boost. I'm new to Android ... Thanks


Or can send it to me xxxx@xxxxxx.com
 
AaronEmoBoi said:
i notice that it was a bit smoother in certain circumstances and the batter lasts a little bit longer on it too
Click to expand...
I left my phone on all night...still have 14% left so the battery life DEF has become better because before I would have woke up to a dead phone. I will report my other findings later after I use the phone more. Thanks again for the tutorial.
 
If we back up the stock build.prop to try this out, is there any chance of bricking the phone with the new values? If so, how do you recover if it can't boot up for you to restore the stock build.prop? Can the stock recovery boot enable a USB mount of the phone file system so that we can hook it up to a Ubuntu or other Linux host and do a mount of that file system and restore the stock build.prop via that method? I ran the terminal app and noticed that the different partitions are ext4 mounts.

FYI, I'm able to get better launcher performance with LauncherPro Plus. I used Titanium Pro to freeze some of the stock Sprint bloatware so that the resources are freed up for user operation. I'm able to get around a day of usage by dimming the backlight, disabling roaming, and disabling bluetooth/gps.
 
This should not brick your phone even if you type it wrong the worst it can do is screw up performance i ask you to back up the file so you can go back to it if you type the code wrong and it messed up something but no bricking could come of this
 
What happens if you dont mount rw? i dont have root explorer as i dont want to purchase it so im using root browser lite.
 
Is there another option to "mount rw"? or am i just not understanding and your actually telling me to "read and write" this. lol sorry.


****under stand now and did it. Only question now is do i replace those codes with the new one. ie "VM Heapsize; higher the RAM, higher the hp can be:
dalvik.vm.heapsize=48m"

i have that code there, the number is 96. can i change it to 48? or add every existing code to whats already there?
 
tonytouch311 said:
Is there another option to "mount rw"? or am i just not understanding and your actually telling me to "read and write" this. lol sorry.


****under stand now and did it. Only question now is do i replace those codes with the new one. ie "VM Heapsize; higher the RAM, higher the hp can be:
dalvik.vm.heapsize=48m"

i have that code there, the number is 96. can i change it to 48? or add every existing code to whats already there?
Click to expand...


You should long press the build.prop and press open in text editor and make a new line and you can replace existing lines thought i would not touch the ones you didint put there and 48 is just fine for this phone if you want to go higher you can
 
I was wondering about the VM heapsize as well... my stock value was 96 also... would decreasing it 48 be better or should we leave it at 96?

More importantly, thanks for putting this together... I'm glad to see someone starting to tweak the marquee specifically!:)

tonytouch311 said:
Is there another option to "mount rw"? or am i just not understanding and your actually telling me to "read and write" this. lol sorry.


****under stand now and did it. Only question now is do i replace those codes with the new one. ie "VM Heapsize; higher the RAM, higher the hp can be:
dalvik.vm.heapsize=48m"

i have that code there, the number is 96. can i change it to 48? or add every existing code to whats already there?
Click to expand...
 
OK finally got the chance to try this. Not sure if I see a difference because I have tweaked some stuff myself. What the reason for rebooting a few times for it to take effect?
 
Not sure if you guys read this post on the other forum I posted it in (not sure if external links are allowed on this site), but there's a weird performance bug that actually seems to go significantly faster when plugged in to a computer, and set to debugging mode.

Its weird, benchmark scores are higher and the screen visibly responds faster. Unplug it, and it goes back to normal. I verified it with other users who noticed as well back when I found it. Its a very odd bug- perhaps someone should monitor what is changing internally when the phone is plugged in? Because if we could tap into that speed when unplugged, it would greatly increase the usability of this device!

Also, there as an Android display driver that causes some performance hiccups with our GPU. Removing it sped up certain accelerated graphic tasks (the moons test in Quadrant, for example, jumped from 20-something fps to 60 fps). I don't recall the file off the top of my head at the moment, and my Marquee is deactivated right now, but all this info can be found on other forums. Just wanted to make sure you guys are aware of it!
 
dishe said:
Not sure if you guys read this post on the other forum I posted it in (not sure if external links are allowed on this site), but there's a weird performance bug that actually seems to go significantly faster when plugged in to a computer, and set to debugging mode.

Its weird, benchmark scores are higher and the screen visibly responds faster. Unplug it, and it goes back to normal. I verified it with other users who noticed as well back when I found it. Its a very odd bug- perhaps someone should monitor what is changing internally when the phone is plugged in? Because if we could tap into that speed when unplugged, it would greatly increase the usability of this device!

Also, there as an Android display driver that causes some performance hiccups with our GPU. Removing it sped up certain accelerated graphic tasks (the moons test in Quadrant, for example, jumped from 20-something fps to 60 fps). I don't recall the file off the top of my head at the moment, and my Marquee is deactivated right now, but all this info can be found on other forums. Just wanted to make sure you guys are aware of it!
Click to expand...

thanks for the information....if you remember the site in reference to that display driver can you PM the site please
 
Knoxville363 said:
thanks for the information....if you remember the site in reference to that display driver can you PM the site please
Click to expand...
Honestly, I'm not sure if it against the rules to just go posting other sites, but if other members ask about it, I think I should allowed to share it with the public here.

It was based on some info for the Optimus Black on XDA, but here's the thread discussing it on a marquee:
Improve performance tweak - Android Forums at AndroidCentral.com

Also, here's the thread that points out the performance different when plugged in via USB:
Performance while plugged into USB. - Android Forums at AndroidCentral.com

Some very weird stuff going on here, maybe someone can poke around and get to the bottom of it all.

Meanwhile, mods, I hope I am allowed to post that here. If not, I apologize.
 
dishe said:
Not sure if you guys read this post on the other forum I posted it in (not sure if external links are allowed on this site), but there's a weird performance bug that actually seems to go significantly faster when plugged in to a computer, and set to debugging mode.
Click to expand...

I just tested this, and wow what a difference. I tried disabling the display driver as you suggested, but that didn't seem to make a difference. Plugging into USB on the other hand, is the difference between N64oid being playable or unplayable. In fact, you can see the difference in real time. Load up any demanding application (from Netflix to games) and you can see a 2x or 3x increase in performance every time the you plug into USB.

Also, whether USB debugging is on or off doesn't make a difference.
 
imfm said:
Plugging into USB on the other hand, is the difference between N64oid being playable or unplayable. In fact, you can see the difference in real time. Load up any demanding application (from Netflix to games) and you can see a 2x or 3x increase in performance every time the you plug into USB.
Click to expand...

Everything runs smooth when plugged into USB, but not wall charger. Playing reckless racing 2 is amazing. If only someone can figure out why this happens while charging using usb and incorporate it into a rom or kernel so we can always get this kind of performance. Goes to show this phone is quite good and has potential to be excellent, seems LG or Boost rushed the release and didn't put as much effort as they should have.:cool:
 
You must log in or register to reply here.
Back
Top Bottom