Has anyone ran into problems with Opengl textures on Froyo 2.2, cant seem to get the textured triangle sample to display a texture on my 2.2 nexus one, works fine on the 2.1 emulator. But when I build and run the API demos from the SDK and select the texture triangle it works fine, this is driving me crazy why the same code doesnt display any textures if it’s built as a standalown app. I have tried adding ‘nodpi’ and ‘drawable’ dir’s with the texture images too.
Oh I'm pretty sure it worked fine when my nexus one was running 2.1.
Thanks
Think I solved it, i will post the fix later.
So what was the problem? I'm experiencing this to. I noticed the issue happens if I have ndroid:anyDensity="true" in my app manifest, but if I use anything else, I don't get the full 800x480 screen resolution available to me.
Same issue is happening to me as well. My little opengl 2D test app ran fine in my Nexus 2.1 and after upgrading to 2.2 textures are completely white. Would you please tell us what was your problem?
Thanks!
I think I have your solution.
First, as people may already know, to get the full resolution you want <supports-screens android:anyDensity="true" /> in your application manifest.
The textures are white because when you load them from a Bitmap, android has resized them and the resizing has made them a size that is not a power of 2, so it borks when you load the texture into opengl.
So how to you stop Bitmap from doing that?
create a folder in your "res" directory called "drawable-nodpi" and move your images in to that folder and the system will stop resizing them.
this is only an issue if you are using resources, if you load your images from assets or some other place, then I don't think the system resizes them.
Hope this helps, it worked for me.
-James
Hey James, thanks for your insight
However I just did as you said but I'm still getting the same result. I never used power of 2 textures and they were perfectly rendered; I'm guessing GLUtils.texImage2D already does the dirty work.
anyDensity is set to true, bitmaps are inside drawable-nodpi, all screens are set in SupportedScreens... dunno; I'll guess I'll try to load the texture from elsewhere, not the resources, and see if I can pinpoint the problem.
Hi,
I almost forgot to post here. All James said is true and doing as he said (and using power of 2 widths & height for textures) made it work, but a special circumstance was blurring my point of view here.
The circumstance is that NPOTs seem to be supported in Nexus One with Android 2.1, but not 2.2. Why this support was removed remains a mystery to me
Sorry about not posting what I found and I dont have thread update email reminders turned on. All I did was strip down the api demo (which works) to just a single project and used it as a template.
Let the ports commence
I would prefer to have CM7 Gingerbread stable finished so that we can have something. Porting Honeycomb will be a hard endeavor, and I think the manpower of the modding community of the Vega-ViewSonicGTablet-POVMobii-WhatsItsNameAgain is not too big. I'd rather encourage them to continue what they're doing right now and keep an eye open for a later chance to port the Bee.
bit worried about the scaling issues of 1024 x 600 ran in emulator
problems so far
- scaling on home screen (google search cut off at top)
- apps are a bit large in drawer
- adding widgets/wallpapers/shortcuts function does not scale properly in this res.
ps great fun with the emulator but my god does it run slowly on my laptop for some reason even assigned with 512mb ram :S
wobblydoggy said:
bit worried about the scaling issues of 1024 x 600 ran in emulator
problems so far
- scaling on home screen (google search cut off at top)
- apps are a bit large in drawer
- adding widgets/wallpapers/shortcuts function does not scale properly in this res.
ps great fun with the emulator but my god does it run slowly on my laptop for some reason even assigned with 512mb ram :S
Click to expand...
Click to collapse
Don't worry about the speed - it's due to the emulator emulating the arm architecture and more.
Also, the scaling problems are probably happening because the SDK image was created to a higher resolution - maybe 1280x800, which our tablet does not have.
If LCD density is set to 120 in emulator it works fine
OpenGL Configuration Guide
So how does one configure Chainfire3D the best way possible ? It is easy if you know what you are doing. By default, you want to enable as little as possible.
Basics
As stated, you want to enable as little as possible to make apps work the way you want, as the more you enable, the more CPU Chainfire3D will use to do the work.
IMPORTANT #1: Simply enabling all the options is counterproductive, unless you know you need them all.
IMPORTANT #2: Enabling both "Reduce texture quality" and "Unroll textures" is quite a silly thing to do. Read their descriptions, and think about it for a minute
Both options are available because performance-wise, on some hardware one is better, while on other hardware the other is better.
IMPORTANT #3: "Reduce texture size" is NOT compatible with a LOT of apps. If you are seeing weird things, this setting is likely the problem.
(1) When starting out, you simply shouldn't enable anything. When running an app, and it doesn't work as expected, first go into the configuration and see if there is a plugin (only) you can use to make it work better.
(2) If there is no plugin or you are not satisfied with it, try the "Reduce texture quality" option to see if it improves performance. This is the most "compatible" option to use. Though texture memory use is cut in half, often you don't see a big difference (or any difference at all even) in the end-result being displayed on screen.
(3) Alternatively, try the "Unroll textures" option. Be sure to UNcheck the "Reduce texture quality" option when using this.
(4) As last resort, use the "Reduce texture size" option. While this option greatly reduces memory usage and can have an awesome speed improvement as result, it is NOT compatible with a LOT of apps.
(5) If performance is adequate, try enabling the MSAA feature to improve visual quality.
Specifics - Free version
In the free version, you can only configure the "default" settings, so you'll likely be in the Chainfire3D configuration tool a lot. I strongly advise that when you are NOT using Chainfire3D for something specific, you disable all the options. This is better for system performance.
Specifics - Pro version
In the pro version, I strongly advise disabling ALL the options under "default" settings, and ONLY use "per-app" configuration. This will greatly reduce the chance of conflicting settings between different apps, which does actually happen a lot ! It is also the best possible configuration you can have performance-wise.
INSTALL ON HC/ICS/JB AT YOUR OWN PERIL ! - ITS NOT SUPPOSED TO WORK ON THOSE
SGS2 USERS: Upgrading to KG1 (2.3.4) or newer ROM will fix additional graphics glitches, if you are running an older SGS2 ROM.
About
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Features
- CF3D OpenGL driver
- NightMode (inspired by Jeff Sharkey, more info here)
--- Handy shortcut to toggle on/off
--- Supports red, green, blue, amber, salmon and custom (pro only) modes
- Global OpenGL manipulation
--- Reduce texture size
--- Reduce texture quality
--- Unroll textures
--- BGRA emulation
--- Load plugins
--- Replace shaders
--- (Pro) Disable Chainfire3D detection
--- (Pro) Dump all shaders
--- (Pro) Force depth buffer size (EGL)
--- (Pro) Force MSAA (MultiSample Anti-Aliasing) (EGL)
- (Pro) OpenGL manipulation on a per-app bases
- (Pro) Fix market settings
- (Pro) Manage installed plugins and shaders
- (Pro) Backup and restore settings, plugins and shaders
A bit more detail about some features
NightMode
NightMode reduces the number of colors on your screen, which on OLED screens saves a lot of battery. The various modes (especially red) are also great in low-light conditions, as they have less effect on your night-vision than a full-color screen
Generic note about textures
The features below are only used if a texture format is supported. Natively Chainfire3D only supports raw textures, but these can be extended through plugins.
Reduce texture size
This essentially cuts (supported) textures' resolution in half, which usually reduces memory use (4x) and improves performance, at the cost of slightly reducing texture quality. This is not compatible with all apps! For many 3D apps, this works, as the GPU stretches the graphics, but it does not work for many 2D apps.
Reduce texture quality
This converts 32-bit textures to 16-bit textures, reducing memory use (2x). This will lower texture quality, but for many games the difference isn't even visible. Whether this is actually faster or slower depends on your hardware.
Unroll textures
Converts non-32-bit textures to 32-bit. This should not influence texture quality, but it does use more memory. On some hardware this is faster than using 16-bit textures.
Disable BGRA emulation
Some GPU's do not support BGRA - in this case, Chainfire3D emulates BGRA support. Developers may not expect this (i.e., hardcode features for a specific GPU) and it may cause issues. If red and blue appear swapped in-app or in-game, enable this feature, and see if it helps.
Disable Chainfire3D detection
For compatibility reasons, Chainfire3D announces to applications that it is being used. Using this feature you can turn that off.
Depth buffer (per-app only)
Some apps expect a certain depth buffer size. Without setting this, they may not run (at all). This feature should only be used if an app specifically requires it - there is a good chance apps will NOT run if you change this setting the wrong way.
MSAA (MultiSample Anti-Aliasing) (per-app only)
Enabling MSAA drastically improves image quality at the cost of performance. Lines/edges become much smoother. Available options are automatic (the app decides), 4x, and 16x. Most apps don't enable MSAA themselves at all. The ARM Mali 400 MP (used in the SGS2) can even do 4xMSAA at no performance cost. Note that if your GPU does not support the level of MSAA requested, the app will likely not start at all.
Fix market settings
Plugins may add support for various features not normally supported by your hardware. Market, however, only reports the functionality your hardware provides. Using this feature, Chainfire3D will adjust Market so it also shows apps that require the features provided by the plugins. This is not useful without the plugins
Backup and restore settings
Backup and restore all app settings, plugins, shaders, etc to/from your SD card
Plugins / API
At the moment, the Plugin API is rather limited, but it does allow for some rather interesting plugins like Tegra2 / PowerVR / ATI texture emulation (see the API docs a post below). The idea is to further improve Chainfire3D so Plugins can manipulate the entire OpenGL data stream.
Shaders
From version v1.9, you can replace app's shaders with your own modified versions. See a few posts down for further details.
Pro version
As outlined above, the Pro version adds a little bit of functionality. Purchasing it will support my efforts.
Pro version - warez
Chainfire3D Pro is available from some warez sites, if you feel like ripping me off However I should warn you that none of those versions actually work as the real Pro version does.
Requirements
- OpenGL ES 2.0 (every 1ghz+ phone has this)
- SuperUser / Root
- Writable /system (it will try to remount system as read/write when needed, but the changes need to stick between reboots)
- S-OFF ?
- Having root access from recovery is a big plus to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
CF3D driver installation
There is some risk involved, so you should have either root access in recovery, a CWM backup, or a firmware to flash handy. Nevertheless, the driver has been tested and found working on the following devices:
- HTC HD2
- Samsung Galaxy S
- Samsung Galaxy Tab 7"
- Samsung Galaxy S II
- Samsung Epic 4G
- Motorola Atrix 4G
- Motorola Droid 2
- LG Optimus 2X
- Google Nexus S
It's likely to work on far more devices. So far nobody has reported a failed install, so that's good. Doesn't mean problems can't happen.
Download
Market link (mobile): market://details?id=eu.chainfire.cf3d
Market link (desktop): https://market.android.com/details?id=eu.chainfire.cf3d
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: If you were running the "CF3D :: NightMode" application earlier, you should uninstall it before installing this.
Plugins / API
Currently available plugins
There are currently no plugins available from my hand, but it appears somebody has compiled and released libGLEMU_NVIDIA, libGLEMU_QUALCOMM, and libGLEMU_POWERVR plugins. You may find them if you search for them
WARNING: I did not write, compile, or release these plugins, and thus I cannot vouch for their quality, or that they don't do anything evil to your device. You should also be aware that they may not be legal to use in your area.
Plugin installation
Plugins are .so files called libGLEMU_xxxxx.so . They should be wrapped in a libGLEMU_xxxxx.zip file. Simply put this zip file on your /sdcard, and use the "Install Plugin" option in Chainfire3D.
API
Attached is a zip file containing some information "by example" on how to build plugins. Read the README.TXT file!
Shaders
About
This might sound like voodoo to some of you, don't worry. Modern OpenGL bases apps and games run programs on the GPU (graphics card) to render the image on screen. These can be quite complicated, and they are not always compatible between different GPUs. Chainfire3D allows you to replace apps' built-in shaders with modified ones. This can potentially fix a number of issues with various apps.
Currently available shaders (ordered by release date)
SGS2 - Riptide GP - Modification by Chainfire. Disables Cube Mapping, makes the game playable
Desire HD - Riptide GP - Modification by scukoemo. Fixes rider lighting issues.
SGS2 - Backbreaker THD - Modification by Chainfire. Fixes error messages, does not fix actual display corruption
Desire HD - Riptide GP v1.1 - Modification by Pr0tEct0.
SGS2 - Riptide GP v1.1 - Modification by crypticc
Shader installation
Shaders are .shader files called xxxxx_xxxxx.shader . They should be wrapped in a shaders_xxxxx.zip file. Simply put this zip file on your /sdcard, and use the "Install Shader" option in Chainfire3D. Be sure to force kill the app you are installing shaders for - that app needs to be restarted for the shaders to be applied. TIP: Going into the per-app settings for an app and changing any setting (and back) will kill the target app.
Shaders - How to modify them (ADVANCED TECH USERS)
This post assumes you know a little bit about OpenGL and shaders. Not a lot, mind you, the shaders I modified I did with no prior knowledge of shaders.
Getting the original shaders
Chainfire3D will automatically detect shaders that do not properly compile, and dump that shader to "/data/data/eu.chainfire.cf3d/files/shaders/processname_crc32.error_dump" and "...error_log". This will generate quite a bit of output in logcat, so you know it happens. In (for example) DDMS, filter on "Chainfire3D" to see only these messages.
The error_log file contains the error message from the GPU, while the error_dump contains the shader source code. (Note that there may be too many newlines).
If the shaders do compile, but they do not actually work (or link - watch logcat to see this happen), the shaders will NOT be automatically dumped. You have to dump them manually. You can do this by going into Chainfire3D per-app OpenGL configuration and enable the "Dump all shaders" option. Chainfire3D will now dump every shader the target app attempts to compile. The file name is the same, but it's extension is ".dump" instead of ".error_dump".
Modifying the shaders
You can simply ADB pull the files out of the "/data/data/eu.chainfire.cf3d/files/shaders/" directory. Handy tip: if you do not specify a filename, ADB will pull the entire directory.
Now you can simply modify the shader files with a text editor. You may have to convert the files from unix-newline format to windows-newline format. Warning: See the limitations section, you also need to convert the files BACK to unix-newline format!
Testing the shaders
Obviously, you will need to kill the target app first, then you can push the shaders back to the device at the same location. IMPORTANT: replacement shaders need to have the ".shader" extension, instead of ".dump" or ".error_dump". Keep the rest of the filename exactly the same. If you do this correctly, Chainfire3D will replace the apps' shader with the one you just put on the device.
To let Chainfire3D be able to use the shader, note that you must also chmod 666 the file on the device.
Packaging the shaders
So you fixed issues with an app for a certain GPU by modifying a number of shaders. It'd be a shame if you kept it for yourself. Packaging them up is simple: just throw the ".shader" files in a ZIP file, and name the ZIP file as follows:
"shaders_device_targetapp_version.zip"
For example, the SGS2 shader fix for Riptide GP would be something like: "shaders_sgs2_riptide_gp_v1.zip"
Releasing the shaders
Simply post a new post in this thread, attach the shaders (or put them on a file hosting site and link them), and put the details about this shader in that post. Then PM me that you released said shaders (with a link to the post) and I can add them to the list.
Limitations
Please note the following shader limitations:
- Dumps are at most 64 KB. If the shader is larger, it will only be a partial dump
- Shader replacements must be < 64 KB
- Shader replacements must use unix-newlines
- Shader replacements must have < 16384 lines
- Each line in a shader replacement must be < 1024 characters
The awesomeness of this is so big that it almost makes bacon boring.
woot now that's cool stuff =)
Now if only somebody would be so nice to compile and post PVRTC / ATITC / S3TC plugins on an external host, you could play for example TegraZone games on your SGS2
Nice work...
You absolute legend!
This is something I'd like to try out,
too bad I'm a complete nobody when it comes to this stuff.
A step-by-step guide on how to get this running, and I say it's worth 10 bucks in donation!
EDIT:
Or wait a minute. This is no ROM? And it doesn't need any specific ROM? Just root and install? Then I'm rooting, I'm doing it!
booted without any problems on SGS2. much nice stuff here.thx .
Pro version bought! Thanks for all your hard work!
Paid for full too. Not sure how it works but guess we will have instructions when its features can be used. For now I love nightmode anyway. Thanks chainfire
bought pro an instant ago - installed fine on my sgs2
Thanks for another great app!
Gallery doesn't seem to like "Reduce texture size" option, but I use QuickPic most of the time.
SGS i9000, deodexed XXJVO
Is this compatible with voodoo?
Hm. Rooted and installed.
Some apps and games look f#cked up. Big squares instead of score windows, blue dots instead of digits... Fine example is Chuzzle. Anrgy Birds is totally unplayable, I only get the background working, nothing else.
I have tried all variations of settings possible. Even all boxes unchecked, but these games, and others, are still looking and behaving odd.
Edit;
Maybe I'm not using it right. Anyway, I uninstalled the drivers and it went back to normal. I'm waiting for thumbs up before I use this again.
Still, in theory, this is great work! Don't think I think anything else!
It doesnt even give me chance to click allow in superuser popup
and says could not acquire root cess!!
Chainfire you are awesome! I have bought the paid version immidiately and it rocks! I cant wait for tegra plugin to play some tegrazone games. Holy **** Im excited as much as I was when my first child was born! Nah kidding, even more!
Sent from my GT-I9100 using Tapatalk
Will all apps have to be updated to take advantage of GPU UI rendering, or will Android be able to render all apps via the GPU natively? I desperately hope every app won't require an update to stop using the CPU to render the app's UI with, but I'm afraid that is probably the case. Anyone know for sure?
Roland Deschain said:
Will all apps have to be updated to take advantage of GPU UI rendering, or will Android be able to render all apps via the GPU natively? I desperately hope every app won't require an update to stop using the CPU to render the app's UI with, but I'm afraid that is probably the case. Anyone know for sure?
Click to expand...
Click to collapse
If you look at honeycomb you have to enable hardware rendering in the manifest. But that was because some things don't work properly. Hopefully they've either fixed it so all hardware rendering works, or added a new manifest option to turn off hw instead of turning it on.
Ok; thanks.
HomerSp said:
If you look at honeycomb you have to enable hardware rendering in the manifest. But that was because some things don't work properly. Hopefully they've either fixed it so all hardware rendering works, or added a new manifest option to turn off hw instead of turning it on.
Click to expand...
Click to collapse
This is true, but just wanted to add a bit from what I understand the reason they put it so you had to manually enable it in your app was because HW acceleration caused slowdows on certain types of 2D drawing, especially lines. So this may not change for ICS. If the HW for 3D stuff is still designed around triangles, then the 2d stuff would still be slow.
Basically I think they wanted people to manually enable it to be aware of how and when to use it. If Android were to move to a 3D interface, then there would be more use for it on UI components.
Anyways this is basically what the Google engineers were telling me at the Developer Labs a couple weeks ago. (This is as far as I understood it, I'm no expert in this area, so I may be getting some bits wrong).
Basically this may not really be a "bug" that will ever get "fixed" so to speak. It may be intentional to not use 3d rending when lower-power, faster, 2d rendering would do.