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

Root [modification] Speed up your Rise while improving battery life at the same time

So, you paid a buck and a half for some app to seed /dev/random because $FOO and can't admit you're experiencing confirmation bias? No problem.

Edit /system/lib/egl/egl.cfg and remove only the line "0 0 android" from it. Save. Reboot.

You can pretend it was the $1.50 magic app if you want to. :p

What it does: Disable default CPU rendering in effect by only leaving GPU rendering as an option. Our GPU is actually pretty decent but it's not used to the fullest by default. But moreover, by offloading the rendering to the GPU where it belongs it frees up processor time, making the whole phone itself effectively faster and more responsive because that freed processor time can be put toward your apps!

I played a couple rounds of Speedx 3D and several levels of Angry Birds Rio and lost a whopping 1% of battery in that whole time. Additionally they both played much smoother, beyond just the interface. Previously simply checking email made the battery go down that far.

We've all concluded the Rise isn't very good about battery life, and compared to some it probably isn't. We've also concluded that it's on the low end, and again compared to some... But with this it doesn't appear to be as bad as we thought, the hardware is solid but the software config just kinda sucks.

Faster more responsive interface AND faster phone AND better battery life, with no incantations or dead chickens? What are you waiting for get editing!

Source is XDA, there are dozens of threads about it and as far as I can tell they all reference each other in an infinite loop so I'm not sure which to credit! Some contain BS information about build.prop too, telling you to add CM-specific entries to stock roms... derp.

This should also work for the Hydro but I don't have one to test. They're basically the same under the hood though.


Edit: You will need to make sure the permissions of egl.cfg stay the same as before, the permissions should look like "rw-r--r--", either use your root file browser to set it or the shell command to do it is "chmod 644 egl.cfg"
 
Another way to speed things up:

Edit /system/build.prop to add the following:

dalvik.vm.dexopt-flags=v=n,o=a,u=y

Tip: don't waste time with dalvik.vm.execution-mode because it's pointless, in 4.0+ JIT is on by default.

That's not quite enough though, now you need to open a terminal and do this:

su
cd /data/dalvik-cache
rm *

After that reboot your phone. Startup will take longer because the Dalvik cache will be rebuilt, this time according to the flags you had just added in build.prop in the beginning. After that you should notice it's a bit snappier. It won't be like night and day but it's noticeable.
 
Upvote 0
So, you paid a buck and a half for some app to seed /dev/random because $FOO and can't admit you're experiencing confirmation bias? No problem.

Edit /system/lib/egl/egl.cfg and remove only the line "0 0 android" from it. Save. Reboot.

You can pretend it was the $1.50 magic app if you want to. :p

What it does: Disable default CPU rendering in effect by only leaving GPU rendering as an option. Our GPU is actually pretty decent but it's not used to the fullest by default. But moreover, by offloading the rendering to the GPU where it belongs it frees up processor time, making the whole phone itself effectively faster and more responsive because that freed processor time can be put toward your apps!

I played a couple rounds of Speedx 3D and several levels of Angry Birds Rio and lost a whopping 1% of battery in that whole time. Additionally they both played much smoother, beyond just the interface. Previously simply checking email made the battery go down that far.

We've all concluded the Rise isn't very good about battery life, and compared to some it probably isn't. We've also concluded that it's on the low end, and again compared to some... But with this it doesn't appear to be as bad as we thought, the hardware is solid but the software config just kinda sucks.

Faster more responsive interface AND faster phone AND better battery life, with no incantations or dead chickens? What are you waiting for get editing!

Source is XDA, there are dozens of threads about it and as far as I can tell they all reference each other in an infinite loop so I'm not sure which to credit! Some contain BS information about build.prop too, telling you to add CM-specific entries to stock roms... derp.

This should also work for the Hydro but I don't have one to test. They're basically the same under the hood though.

That's one of the first things I do on a CM based rom, force gpu rendering. Thanks.
 
Upvote 0
EDIT: Nevermind what I posted, it was my faulty way of modifying the egl.cfg what caused my phone to lag and go crazy. Turns out that the permissions of the egl.cfg file were messed up and that caused my phone's behavior.

So it turns out that I did the modification of the egl.cfg file properly and it does work, I can clearly tell that my performance has been increased, draw something doesn't lag anymore for me. I am actually impressed because this is the first time that a tweak works for me.
 
Upvote 0
I'm sorry to burst you guys' bubble but I just tried this on my Rise and it made it almost 3 times more laggy. I was expecting to see no change whatsoever because nothing ever happens with these "tweaks" but I was quite surprised to see how my performance decreased. Also my settings stopped working because everytime I tried to access my Rise's settings it would automatically crash.
So just an FYI, this did not worked for me, and needless to say it did the opposite decreasing the performance of my phone greatly.

Whatever you do, make sure you don't tell us what you actually did. Better you stay upset than accomplish the original goal.
 
Upvote 0
I'm not upset at all, I was just stating what happened to my phone, chill dude!

lol, my not so subtle hint was to say what happened so it can be fixed. Something's screwy, because these two things I posted do work. If it didn't then I'd like to figure out why and make your device fast too.
 
Upvote 0
lol, my not so subtle hint was to say what happened so it can be fixed. Something's screwy, because these two things I posted do work. If it didn't then I'd like to figure out why and make your device fast too.

Well, what I did first was to make a copy of the egl.cfg into my sd card, then I erased the "0 0 android", saved, deleted my original egl.cfg that was on my /egl/ folder and pasted the modified egl.cfg from my sd card into the /egl/ folder (I did all this because it wouldn't let me edit the egl.cfg file right away)
Then I restarted my phone and it was lagging like hell, after noticing that the lag wouldn't go away and seeing that my settings wasn't working I proceeded to add the "0 0 android" line back to my egl.cfg file. I restarted my phone once again, with the egl.cfg file fixed, but everything is still the same, my settings are not working and the phone is lagging.
Thanks for your help :)

EDIT: I think I got it, I just noticed that the permissions were changed, luckily I remember how the permissions were arranged so I am working on it right now

EDIT 2: Yep, that was the problem, my phone is back to normal now. The permissions must have got changed when I copied the file over to my sd card
 
Upvote 0
Well, what I did first was to make a copy of the egl.cfg into my sd card, then I erased the "0 0 android", saved, deleted my original egl.cfg that was on my /egl/ folder and pasted the modified egl.cfg from my sd card into the /egl/ folder (I did all this because it wouldn't let me edit the egl.cfg file right away)
Then I restarted my phone and it was lagging like hell, after noticing that the lag wouldn't go away and seeing that my settings wasn't working I proceeded to add the "0 0 android" line back to my egl.cfg file. I restarted my phone once again, with the egl.cfg file fixed, but everything is still the same, my settings are not working and the phone is lagging.
Thanks for your help :)

EDIT: I think I got it, I just noticed that the permissions were changed, luckily I remember how the permissions were arranged so I am working on it right now

EDIT 2: Yep, that was the problem, my phone is back to normal now. The permissions must have got changed when I copied the file over to my sd card

Yep, sdcard is fat32 so permissions get lost. Try the edit again now with the permissions set.
 
Upvote 0
Curious... is doing this different from the 'Force GPU Rendering' option that can be accessed by going to Settings > Developer options ?

That option is for apps only, this is for everything. Not sure if there's any effective difference, but checking the box didn't have as much impact as this did for me.
 
  • Like
Reactions: Slayer72
Upvote 0
Being a newbie useing db2s in this thread advice + playing with some settings without having any issues with pimp my rom my phones peformace is pretty amazing now i know db reccommends nofrills cpu overclocker b4 i download that do u mind / shareing a good setup for no frills as to keeping batt life as good as ya can but also good cpu performance ill sacrifice a lil batt of cource for faster but wanna know ur input on best settings?
 
Upvote 0
Being a newbie useing db2s in this thread advice + playing with some settings without having any issues with pimp my rom my phones peformace is pretty amazing now i know db reccommends nofrills cpu overclocker b4 i download that do u mind / shareing a good setup for no frills as to keeping batt life as good as ya can but also good cpu performance ill sacrifice a lil batt of cource for faster but wanna know ur input on best settings?

1.024 GHz max
245 MHz min
Conservative governor
noop scheduler

The governor is the only change, it works like Ondemand (default) but opposite. Ondemand will jump right to max when under load and step down to min when idle. Conservative steps up to max under load and drops right to min when idle. Conservative should be better on battery and it's unlikely you'll really notice any speed changes.

I'd prefer the deadline scheduler, but Kyocera didn't build it in so it's not available right now.
 
  • Like
Reactions: Kritter888
Upvote 0
Another way to speed things up:

Edit /system/build.prop to add the following:



Tip: don't waste time with dalvik.vm.execution-mode because it's pointless, in 4.0+ JIT is on by default.

That's not quite enough though, now you need to open a terminal and do this:



After that reboot your phone. Startup will take longer because the Dalvik cache will be rebuilt, this time according to the flags you had just added in build.prop in the beginning. After that you should notice it's a bit snappier. It won't be like night and day but it's noticeable.

hi. thanks for your great insight. i've done the first tweak and works great, now i need to make sure i did the second tweak right lol.

after i type "rm *" and press enter/execute inside terminal, the prompt moves to the next line & nothing happens.

is this how it went for you? I reboot phone and it does take slower to boot up since it was updating the apps.
 
Upvote 0
hi. thanks for your great insight. i've done the first tweak and works great, now i need to make sure i did the second tweak right lol.

after i type "rm *" and press enter/execute inside terminal, the prompt moves to the next line & nothing happens.

is this how it went for you? I reboot phone and it does take slower to boot up since it was updating the apps.

Yep, that's how it works. Should only take a long time to reboot once.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones