Related
The major thing I look at with roms is the smoothness of the rosie scroll. A lot of roms are perfect but I can't stand the laggy/slow scrolling. I noticed that even if there's a smooth/ultra smooth rosie option on some of these roms, it is still slow, but on other roms like Prime XL, it's smooth as butter ( I don't use prime because of all the random reboots). Is this because some ROMs don't have GPU rendering? If that's the case, how would I go about enabling it or forcing it?
Find a Rom that has it check the build.prop copy it (it should be labeled) past it into your build.prop if you can't do it I can do it for ya
Sent from my mom's Nexus S 4G..... It's True lol
Nevermind, I found the build.prop. debug.sf.hw = 1 enables GPU rendering right? Is that it?
I'd be willing to bet that a tweak such as forced gpu rendering would maybe make the scrolling smoother, but I can't imagine it being more stable or safe than without.
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 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
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