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
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
Hey guys...
I can't help but notice fps/crack/lag/stutter when i scroll through settings and i think it's time i share this because no matter what i do it's still there.
When i'm in the launcher,everything's so smooth but in settings it's bad..especially when comparing to cm10/10.1 where scrolling through settings is a breeze...
Have anyone else noticed this?How did you fix it?
Thanks.
Btw i'm on Ultima 8.1.2 and [email protected] cpu+640mhz gpu but it doesn't matter really,the kernel/rom combo doesn't affect this.
nfsmw_gr said:
Hey guys...
I can't help but notice fps/crack/lag/stutter when i scroll through settings and i think it's time i share this because no matter what i do it's still there.
When i'm in the launcher,everything's so smooth but in settings it's bad..especially when comparing to cm10/10.1 where scrolling through settings is a breeze...
Have anyone else noticed this?How did you fix it?
Thanks.
Btw i'm on Ultima 8.1.2 and [email protected] cpu+640mhz gpu but it doesn't matter really,the kernel/rom combo doesn't affect this.
Click to expand...
Click to collapse
Try activating "disable hw overlays" and "force gpu rendering" from developer options....it helps me...
Sent from my GT-I9300 using xda app-developers app
You want the settings for best smoothness?
1.install siyah
2.change governor to lulzactiveq andchange scheduler to cfq
3.enable gpu rendering + disable hardware overlay in developer options.
4.set the minimum gpu clock to 266mhz in stweaks.
5.set touch boost to 1000 mhz in stweaks.
Now I guarantee you an ultra smooth experience.
Note : disable/kill media scanner or downloads provider service if it's using too much cpu.
《posted from s3》
Please ask in the correct section
Stop flooding threads with bulls*it!
We had enough of you already!
Help people or remain silenced!
celeronix said:
Stop flooding threads with bulls*it!
We had enough of you already!
Help people or remain silenced!
Click to expand...
Click to collapse
If you're okay with having no respect for the rules, you're not welcome here
bala_gamer said:
You want the settings for best smoothness?
1.install siyah
2.change governor to lulzactiveq andchange scheduler to cfq
3.enable gpu rendering + disable hardware overlay in developer options.
4.set the minimum gpu clock to 266mhz in stweaks.
5.set touch boost to 1000 mhz in stweaks.
Now I guarantee you an ultra smooth experience.
Note : disable/kill media scanner or downloads provider service if it's using too much cpu.
《posted from s3》
Click to expand...
Click to collapse
Bala, is it not idiotic n funny to do all the above even after paying £400.00 / rs.30k to actually buy the damn phone itself.. The reason we paid so much to Samsung was to make all d above and we use it straight away out of d box...
Sent from my GT-I9300 using xda app-developers app
celeronix said:
Stop flooding threads with bulls*it!
We had enough of you already!
Help people or remain silenced!
Click to expand...
Click to collapse
Wrong you are not wanted .
Do you not give a thought for XDA Developeres forum and mods that have to move countless wrongly posted items .
Just because you don't want them in the correct section and is totally against what XDA exists for its not some fix my phone forum that you and other school-kids can mess about with .
No wonder so many senior experienced members steer clear of this forum .
jje
bala_gamer said:
You want the settings for best smoothness?
1.install siyah
2.change governor to lulzactiveq andchange scheduler to cfq
3.enable gpu rendering + disable hardware overlay in developer options.
4.set the minimum gpu clock to 266mhz in stweaks.
5.set touch boost to 1000 mhz in stweaks.
Now I guarantee you an ultra smooth experience.
Note : disable/kill media scanner or downloads provider service if it's using too much cpu.
《posted from s3》
Click to expand...
Click to collapse
And what does this have to do with the topic? You can lock the CPU to 1400MHz and the GPU to 800MHz, kill your battery, and it will still lag in the aforementioned situation.
If you actually pay attention while scrolling in the Setting page, you will see that the lag/hickup will only happen once any of the On/Off switches come into display and get rendered, if you scroll without any of the switches in view it will be smooth. I can already imagine what causes this; they're fetching the status of the switches in the rendering thread and it simply causes an overhead on the rendering fluidity. No matter what you do you won't be able to get rid of that design problem. Hundreds of other apps are completely fluid in the meantime.
AndreiLux said:
And what does this have to do with the topic? You can lock the CPU to 1400MHz and the GPU to 800MHz, kill your battery, and it will still lag in the aforementioned situation.
If you actually pay attention while scrolling in the Setting page, you will see that the lag/hickup will only happen once any of the On/Off switches come into display and get rendered, if you scroll without any of the switches in view it will be smooth. I can already imagine what causes this; they're fetching the status of the switches in the rendering thread and it simply causes an overhead on the rendering fluidity. No matter what you do you won't be able to get rid of that design problem. Hundreds of other apps are completely fluid in the meantime.
Click to expand...
Click to collapse
Nice find AndreiLux.
I really didn't think it was a kernel or settings issue because i run at 200-1704 for cpu and 266-640 for gpu both with reasonable scaling settings so i think i'm fine.
Also true,in almost any other app everything is smooth as it should be...
So in conclusion a dev or sammy must fix the settings apk not to lag?
gaspernemec said:
Try activating "disable hw overlays" and "force gpu rendering" from developer options....it helps me...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that.
Well,force gpu rendering sticks but disable hw overlays doesn't stick after reboot and i really don't know if it actually does something!
Welcome to android!
Sent from my GT-I9300 using xda premium
@nfsmw_mr
Oops,my mind totally ignored the word "settings" in your post.
@andrei
Nice find Andrei. Any solutions for that?
《posted from s3》
The settings need to be reprogrammed. I tried to get rid of that lag because I thought it was because of the kernel, but then I saw that it only happens when the switches come into display. It's stupid but you don't do anything about it. I don't even know if AOSP has the same issue or if it's a Samsung thing.
It's the same problem as with Tapatalk, it's a badly designed pile of crap and that's why it's so laggy, no matter the performance of your phone.
Take Flipboard, Reddit News, much more complex apps, but they are properly coded and thus fluid.
@Bala
It's ok man...
@Andreilux and all
I see...
I think on AOSP scrolling is smoother in settings..
Anyone to confirm this?
What should we do now?
Report to sammy?Ask an experienced developer to try to fix it?
AndreiLux said:
And what does this have to do with the topic? You can lock the CPU to 1400MHz and the GPU to 800MHz, kill your battery, and it will still lag in the aforementioned situation.
If you actually pay attention while scrolling in the Setting page, you will see that the lag/hickup will only happen once any of the On/Off switches come into display and get rendered, if you scroll without any of the switches in view it will be smooth. I can already imagine what causes this; they're fetching the status of the switches in the rendering thread and it simply causes an overhead on the rendering fluidity. No matter what you do you won't be able to get rid of that design problem. Hundreds of other apps are completely fluid in the meantime.
Click to expand...
Click to collapse
+1 , investigating
nfsmw_gr said:
@Bala
It's ok man...
@Andreilux and all
I see...
I think on AOSP scrolling is smoother in settings..
Anyone to confirm this?
What should we do now?
Report to sammy?Ask an experienced developer to try to fix it?
Click to expand...
Click to collapse
yes, i can confirm. AOSP is 100,000 times smoother than Sammy.
edit
What i have found FIXES this issue is to run a LIVE WALLPAPER not a very graphic intensive one, but something like phase beam, or nexus 4 LWP. What this does is, it keeps the CPU fresh and instantly ready to render. Try it if you don't believe me.
download this LWP just for a test: https://play.google.com/store/apps/...2lkd2FzYWJpLmxpdmV3YWxscGFwZXIubmV4dXNkb3QiXQ.. and in settings put everything on MAX. and set the LWP. Now go try to find some lag