Code:
This guide is just something to give you choices, anything you do it's your job, but just get some inspiration;)
WARNING!!! I am not responsible for anything you do to your phone, just try not get too fuzzy with it, or you will brick your phone!!!
Most the thing here will be for rooted phones, if something not working don't blame me, blame GOOGLE...
This only Applies to stock GB and CM 7.1 by mik_os, any other ROMs may not be supported, sorry.
READ©Up There!!!
Any extra info and apps are welcome
* - No danger, definitely go for it!!!
** - This may make your phone unstable, but if you find the solution in time, you are fine...
*** - May make your O1 un-start-able...
**** - Can brick the phone, can destroy it forever!!!
Install CyanogenMod, it will save at least 100MB of your internal storage(as all apps are on ROM, LG apps are on internal memory in stock).
Also, may do much more better things to your phone, but be careful.
Try custom kernels by franco for overclock!!!
First of all, lets start with the CPU****
Use SetCpu
I will tell the frequencies, and what I recommend for, any other advises are good, for any frequency, or atleast the major ones(122-480-600-729-768-806-864)
122MHz** - Lowest, but there are some things:
- Use this if you don't use your phone, only for rare talking and stuff...
- If you have 2% battery drops in 2 mins after you turn the screen on, this is the problem of 122 min...
- If you use your phone more than 1 time/hour (no matter how much), don't use this as min...
245MHz* - Avoid it at all costs, it does nothing good, takes same battery as 480, but it is slower, finish tasks slower, don't use...
320MHz* - This is not good for anything...
----------------------------------------------------------------------------------------------------------------
480MHz* - My favorite, 90% of my use, will save battery, fast response, maybe it will work as max a bit, some apps work like a charm on 480
- Anyone using the phone for anything else other than calling... this is the best!!!
----------------------------------------------------------------------------------------------------------------
600MHz* - use it if no need for OverClock, as I noticed, only Angry Birds and Facebook app gets boosted...
729MHz** - Best Overclocking for battery, will not affect any of your phone, battery is as much as 600, no way you shouldn't use it, no heat up also!!!
768MHz** - best performance without affecting hardware, it will heat up a bit...
806MHz**** - Last one that will not burn it in 5 minutes, I would not go any higher...
864MHz**** - If this works on your phone, it is 100% new and 100% perfect!!!
MENTIONS, VERY IMPORTANT: It depends on your phone, manufacture errors, your phone may go stable @864MHz, or it may not go higher than 600... mine goes at 768MHz, any higher gets me KP...
If you don't need profiles, just get No Frills***
Governors
minmax - like the name, goes to min or to max, it is horrible!!!
Scary - a modified conservative, a bit weird... try it you may like it, better at battery than conservative, worse at gaming, non-gamers, try this!
SmartassV2 - Good, try, great... a better version of smartass, use this if you have it, great for fast gaming, but not good for long use...
SavagedZen - WTF IS THIS???????
smartass - it changes the frequency very good, it really is smart, see v2↑
conservative - goes up and down in stages, not 122→729, but 122→320→600→652→…, really good for long uses and short uses, not taking battery like others, but it has a lower start when gaming, lag in 1st 2 minutes, but then it is no more lag, tested on "Diversion", a really cool highend game.
ondemand - this is what you had when the phone came!!!
userspace - WTF IS THIS??????
powersave - keeps at minimum frequency...
interactiveX - modified version of interactive, which goes to max in second... it is same as SmartassV2, a bit stabler on my phone.
performance - stays at max...
SmartassV2 and InteractiveX have build-in sleep profiles, it saves battery when standby-ing and best performance at gaming, while scary gets you best battery and a usable phone, and conservative the best performance/battery.
Next, VM heap(RAM allowed for an app):*
This will take more RAM, but will boost the CPU and more things...
On CM7, go to performance settings-VM heap
On stock ROM, install VM heap tool from the market...
Set it to 32MB*, this is already done in CM7, but on stock ROM it is easy and then then BOOSTED...
24MB will slow apps...**
48MB will fill the RAM fast, making system autokill kill too fast...**
OR just change the value in build.prop
Use a simple launcher, that may save battery and use low CPU... Here are my recommends:***
Nemus Launcher*
- Looks a bit like LGHome, and takes less battery
- Very smooth, look at the video it has on the market...
- It really is fast response and quick launch, a new experience
- Very simple, smooth and
LauncherPro*
- Very good, my personal favorite, will save battery and keep options, will need to be updated if ICS comes, tho...
- Smooth, but no horizontal drawer...
ADW*
- I hate that this is hard control, not very smooth, YOU have to chose it, but if you tried more, you will see it is not the smoothest, not the most customisable, but a pretty good combination...
- You can get used to it, but if you used LGHome for more than a month, you won't need this, you will quit it!
Zeam*
- This one gets updated, and really fixes the bugs it had... it is not an usual one, but minimalistic, like it says
- Most of the big launcher won't get updated anymore, abandoned...
- This one is good, but it is not exactly smooth, but power save
GO Launcher**
- With the right combination, they say you have it smooth, I didn't
- Did 2 factory resets because of the corrupted data after a few glitches that made me remove the battery...
- DO NOT SET default if you want this, dangerous... only thing that did something bad when I was not rooted, got me bootloops((((((
Watch out the setting you enable, maybe you don't need all kinds of gestures, anything you don't use, DISABLE!!!*
APPS TO USE OR NOT TO USE, YOUR OPINION IS BETTER, THIS IS JUST MY ADVICE:
NO TASK KILLERS(ATK, ATM, TasKiller). Use minfree, set the values you need, the other tweaks you need and enjoy!
Juice Defender will only help you... really when does it help?????
Link2SD - easiest way to manage, freeze, uninstall, move2sd, any app management that requires root, except backup!!!
Just uninstall any app you don't need!
Data on Demand - Really good, try it
Freeze system apps (Link2SD above!!!) with ugly UI and slow, like the Browser and Gallery (YOU MUST), but get a better app before that, with all those missing functions...
Replace Gallery with QuickPic and Browser with Dolphin, which is the only one with cool UI, fast startup and FULL, Opera Mini and Mobile are NOT full, but they are fast
If you want to save your eyes, use Screen Filter*
Yahoo Mail and Gmail are huge hogs!!! If you don't need instant notifications, use stock for that, it refreshes automatically when you start it, takes 2 seconds to refresh, and no battery lost...
Disable profiles in SetCpu if you don't need, that takes battery too!
Use Autostarts, this is your problem, your apps, good luck, but watch out...*** If you want, google autostarts.apk, I got it that way
Disable unused settings, never use high quality in games and apps, that are made for hdpi, O1 is MDPI...*
Don't use wifi when it is not there, just hogs battery, I know some people use it everytime, everywhere, just get it on when you use it, or if you have at home...*
GPS* - This only works OUTDOOR, don't enable it in the house
Get brightness to minimum, will save your eyes and trust me, get it to max in sun and you see it perfect, get it off when at home and see it the same...*
AutoSync* - Disable sync for crappy apps, some things just sync without working at all...
Data* also takes lot of battery(very much, actually), so disable it when not in use, if you want it off when screen off, use Data on Demand
Also, empty your screens, don't use 10 widgets per screen, I use 1 and I am happy, they don't inform you that much, you know...
*Disable setting you don't need( like the high quality images in cm7 menu, what is it good at Optimus one?), eg: I never use gestures, I type Facebook faster than making an "f" in gestures, and that takes some of the CPU, disable everything you don't need or that doesn't help!!!
Angry birds(not seasons and Rio, only the classic) has an option to disable the background, that will make it 2x faster...
Disable history you don't need, flash when you don't need...*
Useful links:
ROOT O1 worked for me without a hard reset
CM7 by mik_os
Kernel for Gingerbread and mik_os 6.6.1
Kernel for stock FroYo and 6.5.x by mik
New baseband(if you want cyanogenmod and you upgraded to 2.3)
SetCpu
FEEL FREE TO CONTRADICT ME OR GIVE ME MORE APPS AND ADVISES, TELL ME IF ANYTHING IS OUTDATED, AND FEEL FREE TO PRESS THANKS!!!****
suggestion #1 - lower the font size!
SetCPU - runs as a service, instead I'd suggest a boot script or No Frills
VM heap tool - just change the value in build.prop no need for an app
SD Cardbooster - use init.d script or add your desired value to init.local.rc
Autostarts - take it or leave it, most of the startup processes end up cached and not actually loaded into memory. It will improve boot times though.
Advanced Task Killer - Most experts don't suggest task killers... they're not needed.
Turducken said:
suggestion #1 - lower the font size!
SetCPU - runs as a service, instead I'd suggest a boot script or No Frills
VM heap tool - just change the value in build.prop no need for an app
SD Cardbooster - use init.d script or add your desired value to init.local.rc
Autostarts - take it or leave it, most of the startup processes end up cached and not actually loaded into memory. It will improve boot times though.
Advanced Task Killer - Most experts don't suggest task killers... they're not needed.
Click to expand...
Click to collapse
OK this may help, but no average user can do them, they will just brick there phone...
In thinking about it, I hate Task Killers, Androids memory management is actually pretty good. Instead search "minfree" on the Market and play with the settings. It's safer and more effective.
Task killer + noob = disaster.
vlt96 said:
Don't use 806, hogs battery and give you kernel panics...
Click to expand...
Click to collapse
Ammm....no Hogs Here on 806, running smooth and hardly made a difference from 729-806 wrt battery draining FOR ME.
just make sure u dont keep all your apps open in the background.
and About the Task manager
i use TaskKiller its got a nice 1 button end apps widget that runs in 1x1 mode. And u can add running services to the ignore list, like DSP manager, Google Services, Messages etc that wont flood the Running apps list, And Whenever u use other apps like Market,Maps or the Browser and wont use it soon again u can end those apps and get some free ram over there.
Specially after Playing some games and browsing pics using a PicManager.
Anyways gr9 Tips
gnsxp said:
Ammm....no Hogs Here on 806, running smooth and hardly made a difference from 729-806 wrt battery draining FOR ME.
just make sure u dont keep all your apps open in the background.
and About the Task manager
i use TaskKiller its got a nice 1 button end apps widget that runs in 1x1 mode. And u can add running services to the ignore list, like DSP manager, Google Services, Messages etc that wont flood the Running apps list, And Whenever u use other apps like Market,Maps or the Browser and wont use it soon again u can end those apps and get some free ram over there.
Specially after Playing some games and browsing pics using a PicManager.
Anyways gr9 Tips
Click to expand...
Click to collapse
I cannot recommend a task killer, everyone knows about them, but memory managers are only for root, so they must get known, I will recommend no task killer, sorry(to avoid noobs getting lower performance just because.they can't make an ignore list...)
What should I do with cache, does it speed it up or just make some stuff slower, or cached data may even boost?
Sent from my LG-P500 using XDA App
I disagree saying 806 or whatever is a battery hog. there is no recommended frequency, as everybody uses their phone differently. Some may use CPU intensive apps or functions that are only good for battery at maybe 806mhz. For those light users, overclocking isn't very good, as their need for CPU is less and overclocking just drains more battery.
terratrix said:
I disagree saying 806 or whatever is a battery hog. there is no recommended frequency, as everybody uses their phone differently. Some may use CPU intensive apps or functions that are only good for battery at maybe 806mhz. For those light users, overclocking isn't very good, as their need for CPU is less and overclocking just drains more battery.
Click to expand...
Click to collapse
I mean 806 is bad for phone, you can use it, but you need to br carefull...
Sent from my LG-P500 using XDA App
Nice tips matee..I disagree with your point saying frequencies below 480 drain no less battery.(have read Franco n fserve sayn d same as you ) but fore me-
With 122-729 interactivex I lose 1% in 2hours .but with 480-729 interactivex I lost 2-3 % in 1 1/2 -2 hours on standby.
And I feel no lag at all while unclocking..
Sent from my LG-P500 using xda premium
androidusero1p500 said:
Nice tips matee..I disagree with your point saying frequencies below 480 drain no less battery.(have read Franco n fserve sayn d same as you ) but fore me-
With 122-729 interactivex I lose 1% in 2hours .but with 480-729 interactivex I lost 2-3 % in 1 1/2 -2 hours on standby.
And I feel no lag at all while unclocking..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't know what to say, the 480 and 122 have same voltage, and the battery it takes works in SmartAssV2, interactiveX is made for gaming and using it, but I don't think it will keep at lowest, I will add that interactive governors are better at 122 min, but Amy others, I think best is 480, it depends so much on the governor, try scary, that is cool.to see how the frequencies change very odd...
Sent from my LG-P500 using XDA App
aah... good one.. but a lot of other things uve mised here !! the real normal ones.. like brightness, sync, etc.. n also , i would like to give the phone n iphone type smoothess n cool animations.. (only for adw n cm7)
first from spare parts, make windows animation 'slow' or 'normal' n make transition animation 'normal' n from adw settings > screen prefference > in the end there is a setting to adjust screen transition speed. keep it somewhere in the centre.. this'll give u amazing smoothness !
harshdoshi25 said:
aah... good one.. but a lot of other things uve mised here !! the real normal ones.. like brightness, sync, etc.. n also , i would like to give the phone n iphone type smoothess n cool animations.. (only for adw n cm7)
first from spare parts, make windows animation 'slow' or 'normal' n make transition animation 'normal' n from adw settings > screen prefference > in the end there is a setting to adjust screen transition speed. keep it somewhere in the centre.. this'll give u amazing smoothness !
Click to expand...
Click to collapse
I will get that when I go on PC, but will the smoothness take off the performance?
Sent from my LG-P500 using XDA App
vlt96 said:
I don't know what to say, the 480 and 122 have same voltage, and the battery it takes works in SmartAssV2, interactiveX is made for gaming and using it, but I don't think it will keep at lowest, I will add that interactive governors are better at 122 min, but Amy others, I think best is 480, it depends so much on the governor, try scary, that is cool.to see how the frequencies change very odd...
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
I don't think so. I think 122 Mhz is using a different voltage, only 245,320 and 480mhz are the same voltage. However 122 mhz is slow and unresponsive so...
terratrix said:
I don't think so. I think 122 Mhz is using a different voltage, only 245,320 and 480mhz are the same voltage. However 122 mhz is slow and unresponsive so...
Click to expand...
Click to collapse
It is much batter to have fast responsive doing something in a second at 480 than having to reboot just to get rid of the 122 lag...
Sent from my LG-P500 using XDA App
igivecandy said:
thx for the tips
Click to expand...
Click to collapse
I will try making this just to give you advices, but making your own choices, knowing what exactly are you doing, making an O1 just the way you want, for example I am gonna say what is every frequency good for, but I will tell you what are the risks, but does anyone have a voltage list for every frequency( up to 864, if you can...).
So I will thank you, I need more help...
Sent from my LG-P500 using XDA App
Should mke the thread as "discussion", as this topic os quite subjective.
But very good topic!! Im happy to see this topic, as a noob, this give me a lot understanding to enhance my O1.
Sent from my LG-P500 using XDA App
just wanna add something.. .
DONT PUT TOO MUCH WIDGET ON YOUR HOMESCREEN coz it will affect your scrolling speed..
JastaPein said:
just wanna add something.. .
DONT PUT TOO MUCH WIDGET ON YOUR HOMESCREEN coz it will affect your scrolling speed..
Click to expand...
Click to collapse
This was just what I was gonna do now
What I do:
1. Install Titanium Backup, QuickPic, and another browser that's meant to be kill-able.
2. Freeze Android's default browser and Gallery.
3. Set the 2 things I downloaded as default.
Browser and Gallery had been the culprits of a lot of my battery leaks for the past 7 months. How'd I know? Watchdog. Install Watchdog. It's a lifesaver.
Also, no problems with GO Launcher
(Help )got myself autokiller memory optimiser(minfree) from market ..what should my settings be to keep minimum ram at 280?
Sent from my LG-P500 using xda premium
Im having the same issue with every launcher that Ive tried based on 4.0+, terrible, terrible stability.
Some days I will have no issues, but more often then the launcher will frezee up, and sometimes FC. Usually after after I force stop the app from settings, the problems continues soon there after. This has been happening on the stock launcher, Nova launcher, Trebuchet and Apex launcher, but never on Go launcher or ADW Ex. I thought it may be the widgets I use, but removal of the all my widgets doesnt change a thing.
Is anyone else having similar issues or know of a fix?
Have yet to have my first launcher crash... 3 screens with various widgets. Stable as hell here.
SteveCheeseman said:
Im having the same issue with every launcher that Ive tried based on 4.0+, terrible, terrible stability.
Some days I will have no issues, but more often then the launcher will frezee up, and sometimes FC. Usually after after I force stop the app from settings, the problems continues soon there after. This has been happening on the stock launcher, Nova launcher, Trebuchet and Apex launcher, but never on Go launcher or ADW Ex. I thought it may be the widgets I use, but removal of the all my widgets doesnt change a thing.
Is anyone else having similar issues or know of a fix?
Click to expand...
Click to collapse
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Don't have any issues w/ ADW except for scrolling widgets.
a Mandroid said:
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Click to expand...
Click to collapse
Changing the I/O scheduler to CFQ is not needed. My prime stock launcher is very stable on stock noop I/O scheduler. That CFQ mode doesn't make as much a difference as some make it to seem. I've tried them all in ATP tweaks. Stock noop does the best for "Me".
OK..edit..nvm...I thought you was saying to put it on CFQ. You right, noop is the most stable. Which is the stock, out the box method, noop.
a Mandroid said:
Thats quite strange - I haven't come across any prime that shows this symptom.
Have you done any customisation or removed any system apps?
Is "Force GPU Rendering" turned on? (in settings > developer options)
Is the CPU scheduler set to CFQ ? (you can check it with antutu cpu free version)
You may want to do a fresh install of the 11.1 firmware and see if it fixes your issue.
If it doesn't try installing the ATP tweak from development thread and switch between different scheduler to see if it fixes the issue. (noop is the most stable).
Hope you resolve this issue and enjoy your prime.
Click to expand...
Click to collapse
I am currently using ATP tweak with my scheduler set to cfq, but I did have the issue before on noop. I havent removed/modified any system apps. Only thing Ive done with system apps is install in the launchers as such. and yes i do have force gpu rendering
Had the same Problem
My Launcher also crashed very frequently, in the end it was nearly unusable. But after a factory reset everything is fine now and it seems to be fixed. My Prime was rooted but I never messed with any Schedulers or anything else!
So far the Stock Launcher never crashed and was never unresponsive! I think the HC to ICS upgrade somehow messed it up.
SteveCheeseman said:
I am currently using ATP tweak with my scheduler set to cfq, but I did have the issue before on noop. I havent removed/modified any system apps. Only thing Ive done with system apps is install in the launchers as such. and yes i do have force gpu rendering
Click to expand...
Click to collapse
Ehm, I actually think force gpu rendering should be turned off...
changing force gpu rendering doesnt seem to change anything, so a factory reset it lookin to be my best shot.. i was hoping i didnt have to do that though
haven't had a single hiccup with spb shell, and it seems like it would be pretty taxing on the cpu/gpu. I think you're going to have to just bite the bullet and factory reset.
Force GPU Rendering yields mixed results for some. In some apps you get better performance, and some apps become unstable (e.g. random crash or start showing random drawing artificats) - as they were not designed to work with GPU rendering.
Any apps targeted for Android ICS will have GPU turned on by default, regardless of this setting. As app developers update their apps for Android 4.0, that option should not be needed anymore. Most games use GPU regardless of this setting.
Also note that, GPU rendering can have adverse affect on memory and battery usage. GPU consumes way more memory than CPU for certain types of operation, that is why Android has disabled GPU rendering for the different parts of launcher (e.g. System bar) as it would need to wake the GPU each time and it will use more power and memory.
So I highly recommend turning it off for consistency and reliability - and wait for app developers to update their apps for ICS. That option is really meant for developers to test their apps. Forcing Android to use GPU rendering for everything may produce unpredictable behavior and higher battery usage.
If you do change it, please do a cold boot (shutdown and then volume down+power button together to boot), and clear the data for launcher (Settings > Apps > All > Launcher) [Note you will lose your shortcuts and widget layouts]
has anyone ever bothered to go into developer options in settings and turn off transition animations scale or windows animation? to see if things are speeded up even more so. I noticed with windows animation off, the setting screens just pop onto the screen vs. a more gradual appearance of it. I'm trying it with those off to see if any noticeable increase in UI speed. although my UI was fast n lag free before, I'm just curious to see if speed increased even more. Someone brought up a point before that one reason IOS UI is fast because they don't have fancy transition animations n such like android. so cutting those off "should" theoretically improve ICS UI.
I just use the app "spare parts" to speed up the window and transition animations.
krispy521 said:
I just use the app "spare parts" to speed up the window and transition animations.
Click to expand...
Click to collapse
I have that app also. but instead of just speeding them up, you can completely shut them off. things do move alot faster as far as ui goes. if you put the transitions to 10x you get this cool slow mo fading effect when switching to certain tasks or apps. but going into developer options and cutting off windows animation and transition animation does speed things up. they pop on the screen that much faster.
I might try out the spare parts thing to see how that fares. reminds me of an app I had on Ipad, jailbreak needed, that was like a fake gpu accelerator. all it did was speed up window animation and transition animation. it worked well so ill take a look at this. I'd still think completely shutting them off is the fastest method vs. speeding them up.
edit update: I just tried out spare parts like you said. Do you know what speeding up the windows n transitions animations really does in that app? lol all it does is change the developer animation settings. I compared it. OK for example stock developer settings has windows and transition set at 1X by default. now if you go into spare parts app and put those animations to fast, all it did was change developer options animations to .5x speed. so really that spare parts app is not even needed for that. you can go straight into developer options and change this without needing that app. I did it a few times and looked back n forth at spare parts settings then developer options and all it does is change developer option speed. which I can do within Asus settings itself. even in the app description it says cutting them off brings fastest device performance.
I still wish we could find out a more technical answer on if Forcing GPU rendering helps or not. and if it does, is there extra battery drain? only seen mixed answers. nothing concrete yet. I have noticed in the developers section there's a custom rom calles WSG rom. one of his features is that he basically cut off CPU rendering and forced GPU rendering full-time. been hearing good things about how fast it is. I wonder if its the same as going into developer options and forcing gpu rendering. Anyone has any technical insight into this?
I think I was the one who mentioned the screen transition in a thread where someone was calling the TFP laggy.
I have mine set to none. I don't see why anybody would use screen transitions. Isn't instant screen changes what everyone wants?
theandies said:
I think I was the one who mentioned the screen transition in a thread where someone was calling the TFP laggy.
I have mine set to none. I don't see why anybody would use screen transitions. Isn't instant screen changes what everyone wants?
Click to expand...
Click to collapse
cutting off those animations does bring instant screen changes. I think I will leave them off. UI is even faster than before with them off. everything, as far as UI. launching apps, etc..is instant.
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
demandarin said:
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
Click to expand...
Click to collapse
Is this how iOS does it? Are there any drawbacks to full GPU rendering, more crashes..ect?
demandarin said:
here is technical info on what happens when you Force GPU rendering. I asked the developer MasterZen about it in his thread. He isbthe Creator of WSG Rom, where he added the feature of removing software(CPU) rendering and forcing GPU rendering full-time. here's his quote:
" FULL GPU rendering puts our tablets into a state where all the rendering steps, both rasterization and scene composition, are handled by the GPU. The rasterization step in the rendering phase takes all the display list objects, either vectors and bitmaps, and creates textures to be rendered. Then the textures are copied on to the buffer. Thus freeing up our CPU for more excessive task"
Click to expand...
Click to collapse
That's how apple does it! I am telling you guys why do you think they use extensive amounts of VRAM and also why they leave their CPU clocked so god damn low!
We should start forcing that in all roms and send a letter to Andy Rubin if we find it helps a bunch!
Sent from my PG86100 using Tapatalk
aypanthony said:
Is this how iOS does it? Are there any drawbacks to full GPU rendering, more crashes..ect?
Click to expand...
Click to collapse
I'm not noticing any drawbacks at the moment on full gpu rendering. MasterZen said in his thread that he will put together a beta team to see if it has any drawbacks or improvements to battery performance.
Wordlywisewiz said:
That's how apple does it! I am telling you guys why do you think they use extensive amounts of VRAM and also why they leave their CPU clocked so god damn low!
We should start forcing that in all roms and send a letter to Andy Rubin if we find it helps a bunch!
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
good idea. plus people should definitely go into developer options and cut off the windows and transition animations, tablet is Wahhabi more snappier now. add force gpu rendering and UI n everything becomes really fast. mines was already great before but cutting off those animations took it to another level. I'm forcing gpu rendering also to see how that fares also. we might be on to something
Wow... i just changed the Windows and transition animation setting to 0.5 instead of 1.0 and enabled the force gpu option. There is a Noticeable improvement in GUI speed for the interface. I like the eye candy so didn't want to completely turn them off.
Thanks for the tip!
Def a speed boost when turning off animations.
MadmanJay said:
Wow... i just changed the Windows and transition animation setting to 0.5 instead of 1.0 and enabled the force gpu option. There is a Noticeable improvement in GUI speed for the interface. I like the eye candy so didn't want to completely turn them off.
Thanks for the tip!
Click to expand...
Click to collapse
no problem
demandarin said:
good idea. plus people should definitely go into developer options and cut off the windows and transition animations, tablet is Wahhabi more snappier now. add force gpu rendering and UI n everything becomes really fast. mines was already great before but cutting off those animations took it to another level. I'm forcing gpu rendering also to see how that fares also. we might be on to something
Click to expand...
Click to collapse
Benchmark it like that!
Sent from my PG86100 using Tapatalk
Wordlywisewiz said:
Benchmark it like that!
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
OK. ill do it tonight. I doubt the animations would affect anything but forcing GPU rendering could have dramatic effect for the positive in the benchmarks. as far as gpu side of things goes.
Hi everyone,
This is the first time owning a Samsung device, so the pegasusq governor is a new thing to me, I read about what it actually is on a thread but I wanted to ask to fellow S3 owners what are they using for great battery life - performance ratio?
I'm running Omega 6.0, slipstreamed loads of crap that is not needed (from the "safe to remove" thread) with Apex Launcher. I'm only using 2 homescreens, dark wallpaper, etc, the typical works to try and improve battery life.
Now the thing is, with SetCPU I'm running the default pegasusq governor ranging from 200mhz -1400mhz. Is the pegasusq governor the right choice here? Isn't it basically a variant of the OnDemand governor but Samsung proprietary for quadcore CPUs? I also recall reading a mention of S3's freezing or not waking up when it's set from the lowest underclocking point (200mhz), is that right? I've been using this for a few hours and no problems yet, but just wanted to know what are everyone elses experiences and what's the best configuration that has worked individually for you!
Cheers! Hope I complied with the rules, I did do a search but didn't find anything of this nature apart from a few separate questions!
I use the same governor, 100Mhz - 1704Mhz. No issues. Works great.
Siyah kernel is using pegasusq so i think it is the best governer there is. if you're on stock kernel or lowest underclocking is 200mhz but in custom kernels you can use 100mhz.
I have set my SetCPU to 100mhz - 1200mhz and undervolting all 18-steps to -50mv. I seldom reboot my phone but not encounter any freeze on boot
You should try tweaks for improving the battery life and peformance. Like supercharger, zipalling , random build.prop tweaks.... Etc xD but yeah use the samsungs "for quad core"
Thank you for the prompt replies everyone!
I remember with my Desire the whole development community was pretty much "set in stone" if you will, so it was really easy to choose a kernel etc.
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
I use Siyah clocked 100-1704 screen on. 100-300 screen off. No issues.
Sptz said:
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
Click to expand...
Click to collapse
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
Sptz said:
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
Click to expand...
Click to collapse
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
bordikun said:
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
Click to expand...
Click to collapse
Nah, Autokiller isnt a task manager.
Basically, Android automatically kills empty processes (etc) at specified RAM levels. It does this anyway. But on High end RAM packed devices, these values are too low to be of any use as the phone will seldom hit that low a level of free RAM.
Autokiller simply adjusts these values to be more useful for high end devices.
Actually, you don't need autokiller to do this. You can do it in an init.d script although I've not tested this on the SGS3 as I haven't seen a need.
Here is an example I wrote for my Desire AOSP ROM:
Code:
#!/system/bin/sh
echo "8192,16384,19200,23040,25600,30720" > /sys/module/lowmemorykiller/parameters/minfree
Default SGS3 is:
Code:
8192, 10240, 12288, 14336, 16387, 25600
These are for:
Foreground App, Visible App, Secondary Server, Hidden App, Content Provider, Empty App
Hi all, I would like to have opinion from you guys.
Under Development Settings, There Is a Force GPU rendering option
Force GPU Rendering []
Use 2D hardware acceleration in applications
Is it good to enable it or not ?
Some of my friends say Yes, some say No.
Well, I would like to have opinion from you guys now
YeoZy96 said:
Hi all, I would like to have opinion from you guys.
Under Development Settings, There Is a Force GPU rendering option
Force GPU Rendering []
Use 2D hardware acceleration in applications
Is it good to enable it or not ?
Some of my friends say Yes, some say No.
Well, I would like to have opinion from you guys now
Click to expand...
Click to collapse
Graphics are handled in one of two ways, "software", which means the primary CPU does the heavy lifting, and "hardware" which means the GPU does the lifting. Hardware rendering is better because it frees up CPU clock cycles for other stuff, so the phone moves faster/smoother (plus GPUs are designed to excel at the types of calculations graphic intensive applications do). This feature supposedly forces programs to use the GPU to paint 2D objects on the screen (2D was previously unsupported, so most apps and the base UI were software accelerated, 3D should be hardware by default), but it can cause crashing, bugginess.
Devs have the option to enable hardware acceleration with a simple line of code (according to Google at least.) If they choose to enable it, the app will be hardware accelerated regardless of what you set in there.
source-http://pocketnow.com/2012/05/25/what-is-force-gpu-rendering-in-ice-cream-sandwich/
Thanks for your info, mate
So that's why some app behaves weirdly, right?
My camera behaves weirdly. And the black background of apps tends to have a white gradient from bottom up.
so, you enable it or not?
Your Sound Mod rocks too, waiting for Clear Audio+
YeoZy96 said:
Thanks for your info, mate
So that's why some app behaves weirdly, right?
My camera behaves weirdly. And the black background of apps tends to have a white gradient from bottom up.
so, you enable it or not?
Your Sound Mod rocks too, waiting for Clear Audio+
Click to expand...
Click to collapse
No mate I dont have those problems
Yeah i enabled it
Are you using Chainfire3D?
You can try to compare and contrast with GPU rendering on and off.
Eg the back ground of root explorer. There will be LIGHT WHITE GRADIENT from bottom up.
No, I'm not using ChainFire3D. But I've tried it before. It ruins my graphics, games don't function properly even.
#Using STOCK 431 fw
YeoZy96 said:
You can try to compare and contrast with GPU rendering on and off.
Eg the back ground of root explorer. There will be LIGHT WHITE GRADIENT from bottom up.
No, I'm not using ChainFire3D. But I've tried it before. It ruins my graphics, games don't function properly even.
#Using STOCK 431 fw
Click to expand...
Click to collapse
YOU HAVE TO INSTALL PLUGINS FOR THAT
You can run tegra games on ray
Yeah, I know. But it still don't function properly. Sheesh...
I only use it while I'm gb where everything works fine.
Mate, spare our poor Qualcomm S2...
Playin Tegra games on ray it's like pushing it to the limit ouch
If it's Qualcomm S4 with Dual Core 1.5GHz Krait Processor. You're good to go