Hello,
I am new to this forum (even if I have been reading it for a few months already/ I am myself a software developer) and I have some questions concerning the port of ICS to the Desire HD.
I am mainly concerned about our options to implement GPU HW acceleration. As far as I know, the Adreno 205 driver source code is not public.
- Do we need to wait a new release from Qualcomm ?
- Is there a possibility to do some reverse-engineering and possibly hack the current driver to make it work with ICS ?
- Can we use the current driver and 'modify/hack' ICS source code ?
- I suppose we can wait for an official driver for a different phone using the same GPU and 'hack' it to make it work on our device ?
Thank you for any help or suggestions.
The status is, that freexperia cm9 sneak preview hs hw acceleration enabled and the xperia has the same gpu as the dhd. ( http://forum.xda-developers.com/showpost.php?p=19777780&postcount=2013 )
But the problem is that their git tree has not been updated with the hw acceleration patches and therefor contains nothing of use to the dhd port. ( https://github.com/freexperia and http://forum.xda-developers.com/showpost.php?p=19777780&postcount=2013 ) There are currently several Posts in the freexperia thread urging them to update their git.
Also there is the following status on how and what to do about drivers: http://rootzwiki.com/topic/10447-adreno200-source-code-userspace-driver/#entry54129
Thank you very much. A lot of devices use the MSM8255 snapdragon system so I guess as soon as one of them has HW acceleration working, it should be possible to implement it on the DHD too.
I cannot wait to know more about those patches for the xperia ARC
Related
I found this patchd version of google chrome over on the arc forum, it does install and sign me in but doesn't display web pages for me, the non patched version from the market will not run at all for me and i know is due to no hardware acceleration yet on ics builds for defy, but maybe a dev here can work with this version, maybe not but thought I'd post anyway,
I did not patch this and do not know who did but here is the post i got it from http://forum.xda-developers.com/showthread.php?p=22910621 ,
Download here
http://www.mediafire.com/?4df8r5djnahde60
Sent from my MB525 using xda premium
We'd still need HWA, wich we can't implement on gingerbread so all you can do is wait for CM9 to have it
CM7 + CM9 double boot
HWA will soon be implemented in Defy/Defy+ CM9 ...
lutch83 said:
HWA will soon be implemented in Defy/Defy+ CM9 ...
Click to expand...
Click to collapse
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
adiq_ambro said:
Where from you know that? Is it certain information or you just assuming?
Could someone competent introduce me to the HWA problem on AOSP ICS? Is there a need for new drivers for each GPU model or CM team is prepairing universal solution for this? I'm not very into Android architecture, maybe someone who is can answer?
Click to expand...
Click to collapse
Eppy and quarx are working on hardware acceleration for CM9 at the moment. They have got HDA working partially (3D accel.) But 2D acceleration is not yet working. And it's 2D acceleration that is needed in order for chrome to work.
It may be a driver matter, i don't know, but i'd make an intelligent guess on it
CM7 + CM9 double boot
Adreno 2xx, and 3xx User-mode Android 4.2 Jelly Bean MR1 Graphics Driver (ARMv7) [JB_VANILLA.04.02.02.060.053]Download (13.3 mb)
Updated 23 Apr 13
This release contains a developer preview of the user-mode driver binaries for Qualcomm's Adreno 3xx and 2xx GPU on Google Android 4.2 Jelly Bean MR1. It has been tested with the CAF AU_LINUX_ANDROID_JB_VANILLA.04.02.02.060.053 and supports any Adreno 2xx and 3xx GPU on Android 4.2 Jelly Bean MR1. This release is intended only for developers that work on Jelly Bean MR1 bring-up work, and does not meet our customer release quality. This release adds Adreno Profiler support for Nexus 4 devices with factory ROM JDQ39.
Click to expand...
Click to collapse
https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources
You need a developer account to download it from their site, but I also found it here: http://invisiblek.org/Adreno200-AU_LINUX_ANDROID_JB_VANILLA_04.02.02.060.053.zip
Has anyone tried these?
Needs a 3.4 caf kernel on the jb2 branch. Or at least the drivers from it
Sent from my One V using Tapatalk 2
simonsimons34 said:
Needs a 3.4 caf kernel on the jb2 branch. Or at least the drivers from it
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
I will take every folder and explain exactly what does.
In system/app you will find a apk named ProfilerPlaybackTools.apk wich makes 2d graphics response much faster (~ 2-3 fps more), then in bin folder you will find gpu_dcvsd wich is mandatory in JB MR1 to be better understood it makes the connection beetwen kernel and the libs. After that in etc/firmware are files wich gives the correct profile for our device 1s because those libs are for every 2xx and 3xx adreno chipset. And here we are now at lib folder where we can find the new improved "drivers" those basicly stops the connection with cpu and render the image directly with gpu this results maximum -1 fps in 3d because of no-cpu and +battery save and no more cpu overheating. And now in lib/egl :
- libEGL_adreno200.so (Adreno 200 lib for HW rendering)
- libGLESv1_CM_adreno200.so (same as above)
- libGLESv2_adreno200.so (same as above)
- libq3dtools_adreno200.so (same as above)
For more you can check qualcomm website.
Hi!
It has come to my attention that videos played in this ROM (VGA+) are getting less stuttter / lag. Even without the modified libraries.
As I have checked the date when the libraries (OMX) were created, it was way back 2008.
if I applied the updated libs of the Adreno 200 for ICS ARMv6, the lag is getting obvious, its like there is a sudden freeze in frames.
I don't know for now what's going on here (libstagefright, OpenMAX, and the Adreno 200 drivers) in the cm9.1 alpha 9 rom itself.
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
maybe there is a way on putting JDroid's and Gangster41's modified files here, but for now, I don't know what files to put and what's not, coz I'm no good at modifying the libraries. (No knowledge about linux / android programming)
Everytime I put the modified OMX libs, video acceleration gets worse.
Even the Adreno 200 Lib updates for ICS! :/
hope this info somehow helps the issue on the HW acceleration for ARMv6.
I hope the solution will be found soon, so we will have a fully functional cm9!
Where did you find adreno200 libs for armv6 ics?
thepastormarty said:
Hi!
Has anyone tried this ROM? (This came from google)
https://code.google.com/p/cm9-wildfire-s/downloads/list
Click to expand...
Click to collapse
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't understood something.
EdikNeznanov said:
ummmm... it's our CM 9.1 from modpunk, it's core of all (almost) ICS ROMs in dev thread. I think you just don't undertood something.
Click to expand...
Click to collapse
yeah you're right. Thanks anyway. I'll try to look deeper into the files then.
polfrank said:
Where did you find adreno200 libs for armv6 ics?
Click to expand...
Click to collapse
sorry for not replying.
somewhere in the xda afaik.
I have attached the necessary files for the ICS. (The adreno 200 drivers, dont forget to delete the libGLES_android.so.. they said, deleting that file will increase performace, as it now relies on hardware, and the OMX libraries done by gangster41)
As far from what I have read from the android devs on ics armv6, video recording was somehow possible, but in h263, ammb (vid/audio) format.
see here (http://forum.xda-developers.com/showthread.php?t=1860561&page=5)
Hello! Has there been any progress concerning this matter? I tried modifying things some time ago but I failed..
As I saw, thehacka1 has released a rom(icysnap) with better video playback(i hope it s not my idea).
Furthermore I thought that the owl project team could give a little help here, although they re focused on cm10.1 doing a good job...
Are there any chances of improvement or should I abandon hope...? :/
I copied system/lib folder from MIUI v4 by Henry_01 (which has working video playback) into SlimSandwich and video was working correctly. I just thought I should share. So, we have working video playback on ics!
any one here already know about interchangeable drivers? on my Brothers Xperia L we tested this Adreno Driver on CM11 and works perfectly and this driver is to XZ1 not to XL but works, and they use the same KitKat adreno driver about we use on CM11 and AOSP/PA releases([email protected])... i don't have time to test that now but if anyone here maybe try and if maybe WORKS it will be awesome :fingers-crossed:
http://forum.xda-developers.com/xperia-l/general/kitkat-adreno-v53-driver-t2777516
--
@deedwar / @Phantasm4489 / @perkabalo / @RaymanFX / @Apology11 / @abcdjdj // Major Dev's.. i'm noob about some sh## like that but if that works maybe be the solution to some problems like HDMI blue Flashes on AOSP KK and Low Render Power (without OC) to Games and Apps
I've been trying to update the kernel version on the HD 10 Suez 2017. I am using the sources from this link https://github.com/chaosmaster/android_kernel_amazon_suez/tree/lineage-16.0 on the master Branch I cannot get the the device to boot when building a kernel. However if I use the Android 16 branch, I can get the device to boot but I have an irregularity that I cannot seem to figure out. The screen will go black. It doesn't turn off it just goes black that's if you stop touching the screen or you stop moving the device. aside from that I have not been able to see if anything else is affected but I can get the kernel versions updated at least two 3.18.22 but I haven't continue further because of this the weirdness. I have not tried any other sources as of the moment but was wondering if anybody is run into this problem.
Would this help at all? It’s the googlesource for MTK kernel 3.18
Have you tried building lineage 17 or 18 yet?
https://android.googlesource.com/kernel/mediatek/
https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Mt8176 running Oreo 8.1. Supposedly project treble compatable too. Could this mean 8.1 for the HD10 and/or treble support too?
Fix MediaTek no display bug
MediaTek has a family of SoCs that are used in (among other devices) several Chromebooks, such as the MT8173 used in the Lenovo N23 Chromebook and Acer Chromebook R13, plus the MT8183 in the Lenovo IdeaPad Duet Chromebook. We are working hard to have better upstream support for these devices, especially Enric Balletbo, who has been involved in kernel and Chromebook upstream support for a long time. The displays on MT8173 based devices were not functional when using the mainline kernel, this has been rectified with this kernel release.
The cause of this defect was a conflict between the clock and DRM drivers. He found that two different drivers - the MT8173 clocks controller driver, and the MT8173 DRM driver were using the same compatible string mediatek,mt8173-mmsys. This is a problem since in such cases only the first matched driver will be probed. The other one, in this case the DRM driver, never gets probed and so the display was not made available for use. In a collaborative effort between Enric Balletbo and the MediaTek SoC maintainer Matthias Brugger, a top level mmsys driver (Multi-Media subsystem) was introduced to register the clock and DRM drivers. See 1, 2.
Linux 5.8 probably fixed your display bug. What is the chance of moving this tablet up to android 10/11?
source:
https://www.collabora.com/news-and-blog/news-and-events/kernel-5.8.html