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

Root Tested Build Prop Edits.

ShinySide

ShinySide

Extreme Android User
So I played with alot of build prop edits on my Ascend and they helped tremendously. I came across a post on XDA of build prop speed tweaks edits and so far Ive tried 2 or 3 on my Esteem didnt notice that much difference. Except for one. When I added an edit I played with it and if I didnt notice a difference I deleted it and added another so I would know that it was that particular edit and not ones working together. So far this is a good to go edit that works for the touch responsiveness of the phone. Im on the stock launcher and it made a huge difference as I see. I can make like a little 1/8 inch-1/4 swipe on the screen and it flies to the next home screen.

debug.performance.tuning=1

I added that line towards the top half of the build prop right under "debug.sf.hw=1"

Try it out.


Im still playing with them and will post any that actually make an improvement on this phone. Like I said I did this edit and others on my Ascend and I was actually the 1st one to break 1000 on Antutu with the POS Ascend. My top score on the Ascend is a 1025 on CM7 with this and some other edits. I shared these with someone else and he hit 1040's on CM6 in Antutu.

**Added-
*Helps scrolling responsiveness (added both to the bottom of the prop)-

windowsmgr.max_events_per_sec=150
video.accelerate.hw=1


*Decrease dialing out delay (Added to the bottom of the prop)

ro.telephony.call_ring.delay=0
 
Thanks. I can just never leave sh*t alone ahahaha On the Ascend I never had a problem when I did edits with anything they either worked or didnt, thats the only reason I even started editing it with no recovery ahaha

The only thing thats a "pain" is actually seeing if they work because you actually have to play with things instead of running Antutu or Quadrant because i know a few that will give them false readings but really improve nothing especially in quadrant. Dont know if you ever heard of stagefright or seen the libs in the rom but enable certain ones it will give quadrant a score that is obviously fake and really doesnt improve anything.
 
Welcome to my world lol...
I've been changing a setting, waiting 12 hours, writing results, rinse, repeat for like 2 weeks. That's how I made the optimizer app. There's so many settings to do stuff on. A lot of them very cryptic or totally the opposite of what you think.

Good info, i'll see what it does to battery life. If it doesn't affect it, mind if i stick it in my app as a little checkbox or something?

Yeah, stagefright is kind of shrouded in mystery a bit. From what i've seen, turning it on for stuff makes it faster at the risk of bugginess and gfx glitches etc..
 
kanaida said:
Welcome to my world lol...
I've been changing a setting, waiting 12 hours, writing results, rinse, repeat for like 2 weeks. That's how I made the optimizer app. There's so many settings to do stuff on. A lot of them very cryptic or totally the opposite of what you think.

Good info, i'll see what it does to battery life. If it doesn't affect it, mind if i stick it in my app as a little checkbox or something?

Yeah, stagefright is kind of shrouded in mystery a bit. From what i've seen, turning it on for stuff makes it faster at the risk of bugginess and gfx glitches etc..
Click to expand...

Na go for it dude. I have a whole list of things things that I'll continue to add more if they work and doesnt kill the battery or whatever. I would credit who ever put it together but Ive found like 4 different versions of it so I dont know who Ahaha But theres a bunch of build prop and init.d edits anything from responsiveness to battery life to wifi scan intervals to signal (which I think may be a croc havent tried them yet tho)
 
same thing i did with cm6/7 when i edited the build.prop to get the sound working for boot but that was yester years ago, lol :cool:
 
Added another for decreasing the dial out delay. Makes it so as soon as you hit the green call button it with out a little pause at a black screen it goes straight to the call screen.
 
windowsmgr.max_events_per_sec=150 this value seems really high. The screen updated at 60fps so this is more than double what can actually be seen.

I'd try 60 and see if you get the same result.

I'm wondering if there's just one big list of build.prop descriptions. It's not really secret, just terribly scattered.
 
kanaida said:
windowsmgr.max_events_per_sec=150 this value seems really high. The screen updated at 60fps so this is more than double what can actually be seen.

I'd try 60 and see if you get the same result.

I'm wondering if there's just one big list of build.prop descriptions. It's not really secret, just terribly scattered.
Click to expand...


One of them, I'm thinking that one was FC the LG home launcher but only when I opened the widget drawer and when it was opened for about 5-10 seconds.
 
I'm using root explorer and trying some of these edits but after I save and exit, the line I added is nowhere to be found. what am I doing wrong?
 
I had that problem when I was trying to change the heap size from 96 to 48, even after reboots it still wouldnt change then I left it be and after a couple reboots and I dont know if it had anything to do with it but also after I got the RE update it allowed me to change it and make it stick after a reboot.
 
**Added-
*Helps scrolling responsiveness (added both to the bottom of the prop)-

windowsmgr.max_events_per_sec=150
video.accelerate.hw=1
Click to expand...

how is this running or did you switch it back to what it was before?
 
I deleted windowsmgr.max_events_per_sec=150, for some reason when I opened the widget drawer and only the widget drawer it would bring down LG home into a force close. Why only a fc would happen with the widget drawer I have no clue, maybe the value was to high I just didnt have time to mess with it at the time.
 
turns out:

windowsmgr.max_events_per_sec=150 <--had no noticeable effects.

video.accelerate.hw=1 <-- not sure if it works, maybe already internally enabled. supposed to enable hardware acceleration for camera/video

debug.performance.tuning=1 <--- seemed to make the phone a little laggy, but could have been a few things I was testing at the time.
 
You must log in or register to reply here.
Back
Top Bottom