Benefits/disadvantages to developer GPU options? - Nexus 5 Q&A, Help & Troubleshooting

What are the advantages and/or disadvantages of enabling "force GPU rendering" and "disable HW overlays"?
Sent from my Nexus 5 using XDA Free mobile app

Hi,
You can test easily by yourself and see if you see any advantages and/or disadvantages, right? Just tick/untick and even no need for a reboot... It tends to make some old apps smoother.
If it helps you, here are two quotes that summarize well.
About "force GPU rendering":
Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.
I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.
offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.
Click to expand...
Click to collapse
About "HW overlays":
molesarecoming said:
... hardware overlay allows the renderer to take a couple of regions aside and treat them optimized. then theres the cpu and gpu. usually android decides which abstraction is best for each view, taking things like transparency into account and what not. you switch hw overlays off, project butter goes out of the window but cpu and gpu still do the job. you force gpu, the composition will be done by your gfx chip. just don't touch it - its meant for developers picking up debugging output.
Click to expand...
Click to collapse
I have force GPU rendering enabled since years, it helps about smoothness in XDA app for example, on my side never encountered any side effects, at least for me.

Thanks, that was exactly what I was looking for. I usually keep force GPU rendering on as well but always had mixed results with disable HW overlays. The definitions helped make sense of that.
Sent from my Nexus 5 using XDA Free mobile app

Hi. I'm rooted with xposed- stock os. I know that I can no longer enable art so i am wondering if this is the same.... Can I enable the GPU HW and rendering without a brick or bootloop
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
Hi. I'm rooted with xposed- stock os. I know that I can no longer enable art so i am wondering if this is the same.... Can I enable the GPU HW and rendering without a brick or bootloop
Click to expand...
Click to collapse
Hi,
No, it's not the same thing, about ART: http://forum.xda-developers.com/goo...dicated-runtime-thread-art-vs-dalvik-t2516646.
And yes you can enable them without any issue, nothing related to Xposed (unless an Xposed module breaks something related to those options but I highly doubt). If you want to be sure then make a Nandoid backup before (in any case the "Disable HW overlays" doesn't persist at boot).

Related

Hardware acceleration at Launchers

Guys, I know NOTHING about any kind of programing, development or Android.
I am experiencing it for less than a month! (And I loved it)
The only downside from ipad2 (Yeah.. I said it) is feel of GUI.
I read a lot of xda and rooted my device, loaded clockwork, installed tiamat 1.4.4 and clocked it to 1.6 (interactive), and loaded Launcher pro.
So I think it is as far as I can get close to THAT feeling of smoothness.
In my last week of massive Googling I found out that at Android 3.x,
there is 2d hardware acceleration for apps that have the proper code. And GUI is not using it currently.
Is it possible to write down a Launcher app that have actual 2D Hardware Acceleration at GUI?
Sent from my Xoom using Tapatalk
Turkawa said:
Guys, I know NOTHING about any kind of programing, development or Android.
I am experiencing it for less than a month! (And I loved it)
The only downside from ipad2 (Yeah.. I said it) is feel of GUI.
I read a lot of xda and rooted my device, loaded clockwork, installed tiamat 1.4.4 and clocked it to 1.6 (interactive), and loaded Launcher pro.
So I think it is as far as I can get close to THAT feeling of smoothness.
In my last week of massive Googling I found out that at Android 3.x,
there is 2d hardware acceleration for apps that have the proper code. And GUI is not using it currently.
Is it possible to write down a Launcher app that have actual 2D Hardware Acceleration at GUI?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Who says the stock launcher has hardware acceleration off? Have you checked the AndroidManifest XML to verify?
ydaraishy said:
Who says the stock launcher has hardware acceleration off? Have you checked the AndroidManifest XML to verify?
Click to expand...
Click to collapse
What is that?
I only tell you what I remember from heaps of reading I did..lots of them junk probably..
But it makes sense.
I can play a 3d game flawlessly and my icon jitter and stutter when I scroll from A screen to B screen?
Sent from my Xoom using Tapatalk
Here it is..
Romain Guy wrote
" It is not turned on by default for compatibility reasons. Not 100% of the Canvas API is supported when turned on (although the missing parts are very few and rarely used) and there might be bugs in the new implementation. There are also new constraints (for instance if you try to draw a bitmap larger than the maximum OpenGL texture size, it will fail.)
The new rendering pipeline also uses native display lists for each View, which triggers bugs in some apps. For instance, if a View relies on its parent to invalidate() to redraw itself, it's a bug in the app, but it "works" without hardware acceleration. It will however not work with hardware acceleration on.
Our goal is to make hardware acceleration on by default as soon as possible but we do not want to break apps. That said, apps using standard views and APIs should work just fine."
Much more detailed at
hxxp://android-developers.blogspot.com/2011/03/android-30-hardware-acceleration.html (cant post links yet)
I dont know If ADW ex or Pro launcher uses 2D_HWA.
But as far as i know both these apps are not optimized for honeycomb yet.
And i hope thats true. Couse if they are, that means thats all we can get from xoom on "Sliding icons" department.
Turkawa said:
Guys, I know NOTHING about any kind of programing, development or Android.
I am experiencing it for less than a month! (And I loved it)
The only downside from ipad2 (Yeah.. I said it) is feel of GUI.
I read a lot of xda and rooted my device, loaded clockwork, installed tiamat 1.4.4 and clocked it to 1.6 (interactive), and loaded Launcher pro.
So I think it is as far as I can get close to THAT feeling of smoothness.
In my last week of massive Googling I found out that at Android 3.x,
there is 2d hardware acceleration for apps that have the proper code. And GUI is not using it currently.
Is it possible to write down a Launcher app that have actual 2D Hardware Acceleration at GUI?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
I agree.....UI seems very laggy to me compared to my iPad 1....its not even close to being on the same level of the iPad 2.

hw acceleration

As you know our android devices did not use that from the beginning to the ics. Our devices was not smooth as iPhone coz it didnt use gpu instead of cpu in transitions as i hear. But ics uses hw acceleration and it is smooth on even i9000. Now i ask you, is it possible to port hw accelaleration to our gingerbread devices as a mod or tweak?
Ps: i am a noob about these things for now sorry if i am wrong but i said these as i understood
dorukc said:
As you know our android devices did not use that from the beginning to the ics. Our devices was not smooth as iPhone coz it didnt use gpu instead of cpu in transitions as i hear.
Click to expand...
Click to collapse
It's not true.
1. We have acceleration. But this is not requirement. IE developers can use hw acceleration and can not use it. For iPhone they should use only accelerated API.
2. In iPhone the user interface process has realtime priority. When user made some action, all background processes stopped and only process processed user action will work: try open some page in browser and while it is loading try to move the screen. The loading will stopped. In Android UI process is usual process. When you will move the page in browser it will continue loading the page. But because not all CPU used for work with UI process it can be lesser smooth than iPhone one
It's just different logic of UI. That's all.
Sent from my GT-I9003
Ya but I have used iphone 4. And believe me guys our phone looks really a piece of crap infront of iphone. Its really smooth like silk. Our phone lag like hell when we want to do some heavy multi tasking (only 3-4 apps). But with nearly 11 open apps still iphone run so much smooth. I accept that its not open source bla bla bla...but remember guys still android has to learn a lot to reach level of smoothness of iphone.
The advantages of Android will be on multicore CPUs. This is because of logic. While one core will be executing UI process, others will execute other processes. On IOS all other processes will be frozen
Sent from my GT-I9003
vishal24387 said:
Our phone lag like hell when we want to do some heavy multi tasking (only 3-4 apps). But with nearly 11 open apps still iphone run so much smooth.
Click to expand...
Click to collapse
That tends to happen when you have 3-4 processing apps and compare it to 11 frozen apps. Try having a few apps idle in the background on the i9003 and it's smooth as silk too.
Are you sure about GPU ? I don't think our i9003 use that.
A made a test : Opera mobile is the best browser ever because of he uses GPU acceleration. And the GPU acceleration is so awesome wich some big websites are more smooth in i9003 than iphone 4. If all the UI use the GPU, I don't think the phone laggy.
Ryryoku said:
Are you sure about GPU ? I don't think our i9003 use that.
A made a test : Opera mobile is the best browser ever because of he uses GPU acceleration. And the GPU acceleration is so awesome wich some big websites are more smooth in i9003 than iphone 4. If all the UI use the GPU, I don't think the phone laggy.
Click to expand...
Click to collapse
I am agree with Ryryoku, the smoothness of opera mini/mobile gives as same experience as we get in iPhone , so i think his point is valid, this is the reason why Opera is smoother than any other browser of android...

[Q] What do you want to see in a custom stock ROM?

'Sup everyone, Lime here.
I'm working on a custom stock ROM based off of the 1.55.531.1 update and was wondering what sort of things you didn't like from the stock ROM. This will be my first ROM I've worked on, and I'm making a custom stock ROM to learn my way around Android.
What I've done:
- Hidden Kidzone to the depths of the earth
- Hid the redundant Camcorder icon
- Unhid all of the default HTC applications
- Deodexed for theming purposes
- New boot animation (Nexus One's boot animation, mostly because I think it looks cool and is simple)
- Changed the default layout of the homescreens (the clock's on the default screen, like it is on most other versions of Sense)
- Added bash, nano, sysro/sysrw
What I plan on doing:
- Removing a lot of the mostly unused apps
- De-pinking the icons
- Remapping the Genius Button to search
- Changing the launcher to have 7 homescreens instead of 5
- Enabling CRT Animations
- Modifying the MyTouch Power Control's brightness control to 11/55/100 instead of 40/60/100
What else would you like to see?
EDIT:
Things I want to make happen:
- Extended Power Menu
- Extended Quick Settings
- DEATH TO T-MOBILE APPS (Debloat)
- Less useless battery icon in the notification bar
- CRT Animations
- GPU Acceleration
- Rosie mods (7 homescreens)
- Port the stock Sense lockscreen to MT4GS
- romann's Tweaks
Things that users want:
- AOSP apps
Things I can't really do:
- OC/UV Kernel (source is for 1.28.531.9 so a kernel is out of the question unless it happens to be compatible with 1.55.531.1 [will test soon])
Perhaps an extended power menu, and a built-in screenshot function ? those are some things stock is missing.
To be honest, I haven't used any stock ROM in ages. But I'm sure we could make a stock ROM look nice with some theming.
You may also want to remove themes that people don't use, there's a couple themes that come with the Stock ROM.
Also have the option of the
-aosp music player
-Aosp gallery.
-Extended power menu
-All T-Mobile bloat removed too.
A BIG THANKS TO YOU FOR ADDING ANOTHER ROM TO THE FORUM!
sent from a Nokia 3210
Remove all of tmobiles bloat except for wifi calling
Sent from my myTouch_4G_Slide using XDA
Remove the recent used apps that shows up in the notification bar, change the battery icon to a icon that accurately shows battery percent, personally i perfer the notification bar found on the droid x2. Oh yeah and built in or an app similar to setcpu.
Sent from my myTouch_4G_Slide using XDA
Set up a kernel with overclock (1.5 GHz would be sufficient.)
Oh, and whatever you do... don't get rid of the stock camera
overhauling said:
Perhaps an extended power menu, and a built-in screenshot function ? those are some things stock is missing.
You may also want to remove themes that people don't use, there's a couple themes that come with the Stock ROM.
Click to expand...
Click to collapse
- Extended Power Menu acknowledged. I know it's useful, I just forgot to put it on my to do list.
- Theming is something I'll have to learn how to do; I've no clue where to start but the default theme could be changed. I'm also not much of an ARTISTE but I can pretend to be one
cybot_x1024 said:
Also have the option of the
-aosp music player
-Aosp gallery.
-Extended power menu
-All T-Mobile bloat removed too.
A BIG THANKS TO YOU FOR ADDING ANOTHER ROM TO THE FORUM!
sent from a Nokia 3210
Click to expand...
Click to collapse
- We'll see about the AOSP applications, I'm rather fond of having a unified interface (all AOSP, all Sense, or all MIUI if you get what I'm saying), but I'll see if I think it's worth the time to add it in.
- Power Menu acknowledged, as I said earlier. It's very useful.
- I'm removing everything and likely putting My Account in as a flashable zip with a new icon. It's actually somewhat useful compared to trying to use their website, in my opinion. The icon is a joke though.
ac3theone said:
Remove all of tmobiles bloat except for wifi calling
Remove the recent used apps that shows up in the notification bar, change the battery icon to a icon that accurately shows battery percent, personally i perfer the notification bar found on the droid x2. Oh yeah and built in or an app similar to setcpu.
Click to expand...
Click to collapse
- I'm definitely keeping wifi calling in because I need it to use my phone over in middle-of-nowhere-college-town.
- Yeah, I definitely want to figure out how to put a number overlay on top of the battery marker similar to how CM7 does it. It's amazingly useful. That being said, I am going to add in the HTC Battery widget by default because I think it's great at what it does and doesn't look half bad.
- I'll see about trying to add in Tweaks, because I know you can get rid of the notification bar with them.
- SetCPU is not allowed to be packaged in with a ROM. You can get it here for free though.
overhauling said:
Set up a kernel with overclock (1.5 GHz would be sufficient.)
Oh, and whatever you do... don't get rid of the stock camera
Click to expand...
Click to collapse
- I will try flashing Blue's kernel and seeing if it is compatible with the 1.55.531.1 base after I have more time (i.e after finals). Unfortunately, the kernel source for 1.55.531.1 has not been released yet(?).
I've been looking into theming lately, it seems quite complex and time consuming but hopefully I can help you make some themes. Let me know when you're near done building the ROM.
Also, I guess we can worry about the kernel after we have a nice working ROM.
Love your idea, I'd love to see an updated version of cedde's doubleshot lite, basically remove all bloatware, gpu rendering and a super smooth rosie. Maybe even add tweaks and crt animations. Hey how bout a different lockscreen???
Sent from my HTC myTouch_4G_Slide using Tapatalk
ac3theone said:
Remove the recent used apps that shows up in the notification bar
Click to expand...
Click to collapse
Please nooo, I actually love this :s
Sent from my HTC myTouch_4G_Slide using Tapatalk
masterkamon842 said:
Love your idea, I'd love to see an updated version of cedde's doubleshot lite, basically remove all bloatware, gpu rendering and a super smooth rosie. Maybe even add tweaks and crt animations. Hey how bout a different lockscreen???
Click to expand...
Click to collapse
- Bloatware will be done, don't worry about that.
- I have no idea where to start with GPU acceleration, but I definitely want to add it in. My inexperience will hopefully turn into experience.
- I definitely want to mess with Rosie.
- Will probably be adding in romann's Tweaks.
- I'm working on CRT animations shortly (after finals). The "off" animation seems easy to pull off, but the "on" animation takes a ridiculous amount of editing.
masterkamon842 said:
Please nooo, I actually love this :s
Click to expand...
Click to collapse
- Well, if I can integrate Tweaks, the option will be there to toggle it on/off. I *personally* don't ever use recently used apps, but to each their own.
Limewirelord said:
- Bloatware will be done, don't worry about that.
- I have no idea where to start with GPU acceleration, but I definitely want to add it in. My inexperience will hopefully turn into experience.
- I definitely want to mess with Rosie.
- Will probably be adding in romann's Tweaks.
- I'm working on CRT animations shortly (after finals). The "off" animation seems easy to pull off, but the "on" animation takes a ridiculous amount of editing.
- Well, if I can integrate Tweaks, the option will be there to toggle it on/off. I *personally* don't ever use recently used apps, but to each their own.
Click to expand...
Click to collapse
FYI, when it comes to "GPU acceleration", there seems to be a misunderstanding among some amateur developers. Do you really think HTC would not utilize the GPU abilities that the processor has? By default, all of the GPU acceleration allowed by the Gingerbread operating system is already ON. There is a switch available in the build.prop that only turns on GPU acceleration when in debug mode. When the operating system is run in debug mode, the default is to have GPU acceleration off, this switch will force it on. But in normal operation, GPU acceleration is always on.
ICS enables the use of the GPU for much more than Gingerbread. When we finally get ICS for this phone, it will use the built in GPU much more.
Now, as to your ROM. Why not include Bloater so the user can choose what he/she wants to remove. For instance, I like and use the Genius features, so I would not want that removed. But other things, like Netflix, Group Messaging, etc. I have no use for, so I remove those using Bloater. I'm currently using the DS_MOD_1.55.531.3 ROM and it runs very well. There are certain tweaks (like extended quick settings) I would like.
Fuzi0719 said:
FYI, when it comes to "GPU acceleration", there seems to be a misunderstanding among some amateur developers. Do you really think HTC would not utilize the GPU abilities that the processor has? By default, all of the GPU acceleration allowed by the Gingerbread operating system is already ON. There is a switch available in the build.prop that only turns on GPU acceleration when in debug mode. When the operating system is run in debug mode, the default is to have GPU acceleration off, this switch will force it on. But in normal operation, GPU acceleration is always on.
ICS enables the use of the GPU for much more than Gingerbread. When we finally get ICS for this phone, it will use the built in GPU much more.
Click to expand...
Click to collapse
Yep - listen to what was said here. Gingerbread uses hardware acceleration for a lot of what happens on the screen already - it's always been a weighing of how many cycles it takes with or without, so Gingerbread was inefficient when it came to using the GPU for some things.
ICS has been a while in coming, and has been improved to take advantage of much more integration of the GPU and making you have to weigh less choices between using the GPU or not.
That all being said, there is an issue with either the hardware for the GPU, the TV-out function itself, or most likely the part where it down-converts the HDMI signal to analog to pass it over the RCA connection (most likely) that causes the skipping for some video when output to TV.
We were doing a study on that a bit ago, I don't want to derail your thread with it but you mentioned looking into the GPU so here's what you should be looking into about it. We can keep your thread here on topic by sending people to this thread for discussion on that one:
Media Player Problems
Limewirelord said:
- Bloatware will be done, don't worry about that.
- I have no idea where to start with GPU acceleration, but I definitely want to add it in. My inexperience will hopefully turn into experience.
- I definitely want to mess with Rosie.
- Will probably be adding in romann's Tweaks.
- I'm working on CRT animations shortly (after finals). The "off" animation seems easy to pull off, but the "on" animation takes a ridiculous amount of editing.
- Well, if I can integrate Tweaks, the option will be there to toggle it on/off. I *personally* don't ever use recently used apps, but to each their own.
Click to expand...
Click to collapse
Sounds like a dream come true to me
Sent from my HTC myTouch_4G_Slide using Tapatalk
My list:
Functional bluetooth (including sixaxis)
Overclockable (maybe UV)
No SenseUI
Is it possible to update the Android version to 2.3.7? What would it involve?
sent from a Nokia 3210
Blue6IX said:
That all being said, there is an issue with either the hardware for the GPU, the TV-out function itself, or most likely the part where it down-converts the HDMI signal to analog to pass it over the RCA connection (most likely) that causes the skipping for some video when output to TV.
We were doing a study on that a bit ago, I don't want to derail your thread with it but you mentioned looking into the GPU so here's what you should be looking into about it. We can keep your thread here on topic by sending people to this thread for discussion on that one:
Media Player Problems
Click to expand...
Click to collapse
I think, and it is just my opinion after reading several things about this issue, is that the way the TV-OUT is really just mirroring the screen, so essentially it is driving two screens and, as you say, downconverting the signal at the same time. That's just too much overhead for the GPU and thus the stuttering. Maybe if we had an MHL instead of just the TV-OUT it would be better, it wouldn't have to drive two screens at once. Given that the Sensation has essentially the same chipset, and it has MHL, I wonder if it is just that we don't have the driver/library files for the MHL in our ROM? I would guess you've probably investigated that, though. Also, has anyone tried the DLNA properties available? This device does support DLNA but I've not seen anyone utilize it for anything.
OOPS, sorry, didn't mean to derail
Kanerix said:
My list:
Functional bluetooth (including sixaxis)
Overclockable (maybe UV)
No SenseUI
Click to expand...
Click to collapse
6Axis won't work with the Sense kernel.
Sent from my HTC myTouch_4G_Slide using Tapatalk

Force GPU rendering?

Should I have this checked in my settings? What does it necessarily do? Does it effect battery life? Just don't know to much about it....thanks
Sent from my HTC VLE_U using xda premium
+1
i am interested in an answer to. I believe on stock this option was checked.
However TempleRun was running better without forced gpu rendering...
Gesendet von meinem HTC One S mit Tapatalk 2
Hi, as many people and advanced users / dev' recommend it enable, I did. Here are also some explanations about this setting in ICS :
http://pocketnow.com/2012/05/25/what-is-force-gpu-rendering-in-ice-cream-sandwich/
Other sources are available too (Just google for it ).
My humble experience with it :
- a better smoothness of graphical effects and global's UI (but may be just a "psychological" effect lol)
- didn't got any problem with the feature forced on
- didn't performed so much benchmark, I'm not sure it has a "real" effect on performance
This feature is usually set off in stock roms to avoid "old application compatibility problems" - but even with older applications, I didn't got any problem. You could enable it without risk so
Note that this setting is generally set to "on" by applications (eg. games, videos ... set the setting to "on" while running, and goes back to your system settings on exit) : That's what I understood. No visible effect for those apps'
Hope this will help a bit!

Tried my luck about poor scrolling perf. on Beta Feedback, They actually DID cared!

Guys!
We all want our phones to be Nexus smooth right? Lets make this happen! I just sent a feedback regarding scrolling performance disappointment, and they look like really care about it! So please take some profiling screenshots of your apps stuttering while scrolling, using "show gpu profiling" on screen as bars option in developer settings and send them in Samsung Members App.
Here is my ss attached for feedback you can use it as a template!
This is more issue of the option it self then the performance of the device, when i turn on gpu profiling, i get mass stutters which are NOT present without it.
dazed1 said:
This is more issue of the option it self then the performance of the device, when i turn on gpu profiling, i get mass stutters which are NOT present without it.
Click to expand...
Click to collapse
Interesting... But still I believe its worth a shot, we are way behind stock android.

Categories

Resources