why are you testing it even!? :facepalm:
it cannot work correctly with Android 4+, because there where big changes in Android and the developer (Chainfire) stopped working on it for that reason
probably yes
it could be done with xposed and without
it's just so, that there is noone who wants to do it...
but do you really need it on newer devices
I don't think so
btw. did you know that you can enforce Antialiasing in the developer settings of cyanogenmod by now?
(atleast on Kitkat/CM11 on my Galaxy S I9000)
of course Chainfire 3d had more options
but most of these options where made to optimize performance on old devices
but too small textures look crappy, not always make the game run smoother and sometimes cause errors (in the menu)
night mode and stuff like that can be replaced
my Samsung Galaxy S runs CM11 Mackay Rom and has such color settings inbuild into the settings app
and I don't know whether you can still write plugins to emulate a certain gpu type and whether that still matters
all in all: no one really needs it anymore
antialiasing and stuff has to be included into the game by the app developers
Yes it would still be useful, plenty of "THD tegra only versions" That would run fine on my device with the tegra plugin.
Yes it would still be useful, plenty of "THD tegra only versions" That would run fine on my device with the tegra plugin.
Official thread
"[APP] GLTools (graphics optimizer) 01/21/2014"
http://forum.xda-developers.com/showthread.php?p=49978057
Oldish thread
"[APP][SHARE]GLTools:-Chainfire 3D Alternative for 4.1+"
http://forum.xda-developers.com/showthread.php?t=2604723
Maybe, possibly, an alternative to Chainfire 3d, installed ok on my jellybean rom, but make nand backup just incase if anyone decides to give it a shot, and read up
Apparently issues with some samsung devices, installed on mine before reading this but luckily it seems not ALL samsung devices, knocks on wood
The proper way to unistall is to use a recovery to flash the zip that gets installed upon install of the app
edit: it looks like the playstore version has a uninstal option in app, dont know if the xda version has it, should do
The "official" thread has a free version, and there is a payed version on the playstore, if this project is something you want to support, assuming it does what you want, think about donating if you can, but free is good too![]()
lol thanks ! i saw GLtools or something , didnt know exact name to enter for tegra 4 to get the effects!
Thank you for the info, app looks good so far. It's a shame chainfire hasn't shown any interest in updating this app to work like this other one does.
You have no idea whether or not I have any interest. In fact, I always have and still do.
The issue is that the method of hooking used by the old CF3D (and now GLTools, as I understand it) is extremely dangerous, and a massive cause of bootloops (as some of you have experienced) - that and that nightmode now had to work significantly different (but now covered with the new version of CF.lumen).
This didn't use to be a problem because OEMs didn't diverge much on their base drivers, so it wasn't difficult to write a single patch that worked on most devices, but around 3.x this became difficult and errorprone (also because no source for 3.x back then).
Building something like CF3D is not possible with Xposed (I wouldn't run that on my device anyway, as last I checked it breaks a lot of internal security measures in Android), though it might be possible with Substrate - and that is what I betted on over a year ago. However, both due to lack of time and Substrate not working on 4.4, I have not done anything.
By now I've given up on that approach as well, but I have since devised a new one, that might make CF3D properly possible again (at least 4.2+, maybe even 4.4+). However, now GLTools has just shown up and is slowly taking over the market, so I'm not sure I should even bother, as I personally have no use for CF3D outside of CF.lumen, so I'd be building it mostly for props and profit, neither of which really drive me.
Either way, statements such as that I've shown no interest or haven't done any work on this are quite frankly a **** move, you have no idea what I'm working on or thinking at any given moment.
I totally understand the lack of time....
By now I've given up on that approach as well, but I have since devised a new one, that might make CF3D properly possible again (at least 4.2+, maybe even 4.4+). However, now GLTools has just shown up and is slowly taking over the market, so I'm not sure I should even bother, as I personally have no use for CF3D outside of CF.lumen, so I'd be building it mostly for props and profit, neither of which really drive me.
...
and there it loops. Blank screen no bootanimation. But it loads ok up to there.W/SurfaceFlinger( 116): getting VSYNC period from fb HAL: 16666666
E/Adreno200-EGL( 116): <qeglDrvAPI_eglChooseConfig:757>: EGL_BAD_ATTRIBUTE
E/Adreno200-EGL( 116): <qeglDrvAPI_eglChooseConfig:757>: EGL_BAD_ATTRIBUTE
W/SurfaceFlinger( 116): no suitable EGLConfig found, trying a simpler query
I/SurfaceFlinger( 116): EGL informations:
I/SurfaceFlinger( 116): vendor : Android
I/SurfaceFlinger( 116): version : 1.4 Android META-EGL
I/SurfaceFlinger( 116): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_fence_sync EGL_ANDROID_image_native_buffer EGL_ANDROID_recordable
I/SurfaceFlinger( 116): Client API: OpenGL_ES
I/SurfaceFlinger( 116): EGLSurface: 5-6-5-0, config=0x1
I/SurfaceFlinger( 116): OpenGL ES informations:
I/SurfaceFlinger( 116): vendor : Qualcomm
I/SurfaceFlinger( 116): renderer : Adreno (TM) 200 / Chainfire3D
I/SurfaceFlinger( 116): version : OpenGL ES 2.0 2131267
I/SurfaceFlinger( 116): extensions: GL_EXT_CHAINFIRE3D GL_IMG_texture_format_BGRA8888 GL_OES_mapbuffer GL_EXT_debug_marker GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_AMD_compressed_3DC_texture
I/SurfaceFlinger( 116): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 116): GL_MAX_VIEWPORT_DIMS = 4096
E/cutils-trace( 116): Error opening trace file: No such file or directory (2)
W/SurfaceFlinger( 116): power module not found
W/SurfaceFlinger( 116): power module not found
D/SurfaceFlinger( 116): Screen acquired, type=0 flinger=0x3d5450
I/Netd ( 176): Netd 1.0 starting
I/Netd ( 195): Netd 1.0 starting
I/Netd ( 210): Netd 1.0 starting
I/Netd ( 222): Netd 1.0 starting
I/Netd ( 237): Netd 1.0 starting
I/Netd ( 253): Netd 1.0 starting
I/Netd ( 265): Netd 1.0 starting
I/Netd ( 278): Netd 1.0 starting