Related
Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?
did u manage to find more info about this? Anybody else knows some more details? 10q
zombiefly said:
Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?
Click to expand...
Click to collapse
I'll have a quick go at answering, If anything is wrong then please correct me
HTC have written their own Bluetooth stack that doesn't support AVRCP 1.3 (stupid really if you ask me). This stack will be found in the stock rom, as well as all sensed based custom rom's and possibly in some unofficial AOSP roms.
The Official CM roms should have the standard BT stack with AVRCP 1.3 drafted into it, meaning that it should push the track ID's to all receivers that support it.
To answer your question: Unless HTC's BT stack can be dissected and modded to support AVRCP 1.3, or the CM BT stack can be ported over to sensed based roms (both highly un-likely as HTC's BT stack is closed, and CM's BT stack wont work on sensed based roms) then this is not possible, unless you flash a CM rom on your One X
teky.co.uk has it covered above.
the htc BT stack is (as you would expect) half complete and doesn't support anything but basic connectivity and streaming. The cyanogen mod team added this functionality around cm7 (i think). so for phones that are supported by CM, you can flash a rom built around Cyanogen and you will have track ID.
Because we cant get S-OFF, we cant flash a pure CM mod, which presumably explains why there isn't one available. There is a port in the works by TripNRaver, however the last time I checked the BT streaming was on the issues list as not working, so regardless of it using AVRCP 1.3 or not, it wouldn't work anyway.
I'm quite frustrated by this. I bought the One X thinking it would be the best (and most up to date) Android phone available. Instead i'm stuck half way to removing the HTC crap from the phone for the first 3 months of owning it. I was able to get this functionality on my ageing HTC Desire (with custom rom)...
If you can get something to work, the music player pro application has recently added support for AVRCP 1.3 on phones that support it. So when we eventually get someone to implement a new BT stack in a custom ROM, or when HTC decide to support 1.3, we can actually use the feature!
This has been bothering me for some time; I actually sent an email technical support request to HTC for followup regarding this issue.
Maybe this will be fixed by the time Jelly Bean comes out? Or possibly that could be too adventurous.
I will reply back to this thread when I hear anything from the other side. I actually submitted a link to teky's great informative post in the ticket.
This is the response from HTC when I contacted them about it.
Thanks for your patience.
I can sadly confirm, after a long discussion with a senior technical agent, that Google have not yet implimented AVRCP in there Android O/S. It would seem to be avaiable for Windows based devices, possibly due to the amount of time Microsoft have been in the mobile firmware market. But, sorry to say, it is not yet part of Android.
The only advice I can offer, would be to post on the Google official forums about this as I'm sure you will not be alone with your requirement.
Thanks for your time and for contacting HTC.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium
help us cm9, you are are only hope.... bzzzzzzt
maybe a ROM developer could help re: porting the BT stack to a custom rom?
Here's what HTC sent to me, I have since followed up.
Thank you for contacting HTC.
With reference to your query, currenty we AVRCP 1.3 is not supported by One X. If you see that some of the function on your bluetooth is not working its because of the compatibilty of the phone and the bluetooth.
Sincerely,
Sammy
HTC
This is the best I could get out of them.
Thank you for contacting HTC.
With reference to your query, yes, HTC is looking forward to this. However, we cannot provide any definite detail at this time when will this be available to the phone. That is the reason why as well we are creating new and improve phone here for our customer. Plese refer to our website for any update to our product and service and we do apologize for the inconvinience.
So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!
trungvn1790us said:
So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!
Click to expand...
Click to collapse
if someone created a universal zip file to flash to any android phone, that would be awesome. How in the world did cyanogenmod do it? maybe if someone asks, they can tell you how to code it into any device's rom.
some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.
Really can't wait for this feature!
zombiefly said:
some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.
Click to expand...
Click to collapse
Yes, agree with u guys and really need a package that supported to install to stock ROM
Tks and appreciate for any Hero help to do this!
this functionality is now in CM10. i dont think it can be ported to other roms as i think it has some dependency on the kernel? (but what do i know?)
I've been running tbaldens CM10 for some weeks now and it's very stable
I also would like to have AVCRP 1.3.
As far as i understood the bluetooth stack must be compiled with the kernel. The blueZ stack does support AVCRP 1.3.
But we need a custom kernel compiled with it?
I now also wrote a support inquery to HTC. Perhaps they will implement the complete bluetooth stack if enough customers ask for it.
Regards
Kai
+1
need this feature, please...
makes2068 said:
+1
need this feature, please...
Click to expand...
Click to collapse
its in the main CM10 roms now.
Sorry to dig such an old topic. But has anybody been able to find some patch to get this feature on sense 5. I feel sense 5 is awesome, (sorry to sound selfish) cannot switch over to CM10.. is there anyway I can get it .
on ARHD 31.2
If HTC has been blaming google due to this feature not being available in android itself, I feel cheated.. because have seen this same feature on all other android devices.
Also this feature is there in HTC one , the current flagship with sense 5.. One of my friend has it. If only some dev can compare files and bring out some patch for OneX.
i'm not here to disappoint you , but want to reduce your expectations , this thread is not about my cm9 or anythin of mine , its simply common
Actually its impossible to make hw acceleration work in cm7 and cm9 for galaxy y,
that simply means that even if developed it wont be smooth and will be unstable with sw acceleration , simply unusable
Maclaw too pointed out the same that bcm gpu in galaxy y cant support hw acceleration (this applies for cm7 and cm9 , dont complain that ur phone has hw acceleration , yes ur phone does have hw acceleration with stock and aosp rom)
but u still can have hope with sw acceleration , as there is a way to make the rom smooth with sw acceleration but thats too demanding and nearly impossible .
on vivekalady's cm7, he is trying to make hw acceleration work , sw acceleration works already but low graphics performance
so i'm conveying to you people that , dont expect much in terms of cm7 and cm9 for sgy , also miui , but a gud news is that hw acceleration can work with aosp , so miui can be possible .
so u people need to settle with stock based rom's , but with this kind of attitude towards the dev who theme roms and make custom based roms(i'm not making one) , you are actually making the devs pull out of this forum.
this thread was made to reduce expectations and make people clear of the present situations .
edit: hw acceleration has slight chances to work with cm7 , but wont giv full gpu , around 60% is possible
i know very well that there will be trolls, flames for this thread too , but i dont care , i'm none to advice you
Bad news for all sgy users
I knew it
Thanks buddy
Be happy
I'm happy with the custom ROM I've got already. I'd like to have CM9 for my Y, but HCFroyd247's ChobitsDigitalisV2.0 is good enough for me
Press 'Thanks' if I helped!
Sent from my GT-S5360 using XDA Premium
ROFLkopter said:
I'm happy with the custom ROM I've got already. I'd like to have CM9 for my Y, but HCFroyd247's ChobitsDigitalisV2.0 is good enough for me
Press 'Thanks' if I helped!
Sent from my GT-S5360 using XDA Premium
Click to expand...
Click to collapse
Same feeling Its the best way to refrain yourself from cm7/9
What I don't get is why is Cyanogenmod 7 smooth on the Galaxy mini then ? That device also hasn't HW Acceraltion ...
GianniDPC said:
What I don't get is why is Cyanogenmod 7 smooth on the Galaxy mini then ? That device also hasn't HW Acceraltion ...
Click to expand...
Click to collapse
u mean doesnt have hw acceleration ? it has adreno 200 in it , and it gives full gpu acceleration even for ics
goutamniwas said:
u mean doesnt have hw acceleration ? it has adreno 200 in it , and it gives full gpu acceleration even for ics
Click to expand...
Click to collapse
Well the Y also has a gpu in it isn't 'Broadcom BCM2763' VideoCore IV LPDDR2 128MB (And if we really can't get CM 7 or 9 on this device I'll throw it out the window )
Sent from my GT-S5360 using xda premium
GianniDPC said:
What I don't get is why is Cyanogenmod 7 smooth on the Galaxy mini then ? That device also hasn't HW Acceraltion ...
Click to expand...
Click to collapse
if someone say sgy don't have hw acceleration then :
a. he/she don't know about hw acceleration, or
b. it's just excuse to make people stop ask him/her to port cynogenmod to sgy
if this device don't have hw acceleration you will get low fps in antutu 2d/3d benchmark. my home-brew animation app also easily reach 60fps. it's not possible if this device don't have graphic hw acceleration.
as far as I know our problem is not related the hw acceleration stuff. we already have a booted cm7. that's a prove that our device has possibility to has cm7. our main problem at this moment is that we don't have a complete source to build cm7 since the one comes from samsung is incomplete. don't ask me when samsung will release the complete source to public. they're getting more unfriendly to anyone who want to mod their product day by day. as you can see, they doesn't even let us replace their boot animation in their newest firmware for our device.
actually the stock rom can have hw acceleration also aosp , but cm7 and cm9 cant have , i'm not making any excuses , and i didnt say it by myself maclaw told this
kurotsugi said:
as far as I know our problem is not related the hw acceleration stuff. we already have a booted cm7. that's a prove that our device has possibility to has cm7. our main problem at this moment is that we don't have a complete source to build cm7 since the one comes from samsung is incomplete. don't ask me when samsung will release the complete source to public. they're getting more unfriendly to anyone who want to mod their product day by day. as you can see, they doesn't even let us replace their boot animation in their newest firmware for our device.
Click to expand...
Click to collapse
one thing , actually vivek has been tryin to make hw acceleration work for the past 3 to 4 builds , cm7 only boots up with sw acceleration with 0 o android , but not with hw acceleration
irfanbagus said:
if someone say sgy don't have hw acceleration then :
a. he/she don't know about hw acceleration, or
b. it's just excuse to make people stop ask him/her to port cynogenmod to sgy
if this device don't have hw acceleration you will get low fps in antutu 2d/3d benchmark. my home-brew animation app also easily reach 60fps. it's not possible if this device don't have graphic hw acceleration.
Click to expand...
Click to collapse
i wasnt so clear in my thread , stock and aosp is definitely havin hw acceleration , but when it comes to cm7 and cm9 this is not the case(due to numerous reasons)
i'm not here to offend u , or break ur hopes , if u people get gud cm7 and cm9 i'm happy with that , and this thread is made from my own experience in trying to make cm9 for sgy and also from the wrds of maclaw(developer-cm9 for mini,fit,ace,gio) and rom maru(developer -cm9 lg pe350)
GianniDPC said:
Well the Y also has a gpu in it isn't 'Broadcom BCM2763' VideoCore IV LPDDR2 128MB (And if we really can't get CM 7 or 9 on this device I'll throw it out the window )
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
every phone has a gpu , but whats it capable of matters
goutamniwas said:
every phone has a gpu , but whats it capable of matters
Click to expand...
Click to collapse
So, the Mini has a better chip than the Y dafuq Well I wish I bought the mini I would buy that device but than I thought the Y has a better cpu and is newer but yeah ... As I see if it's unable to port CM than it makes me :'(
I'm not referring to viveks build. what I mean is the one ported from ace. the phone is succesfully booted up but we don't have gsm, wifi, and bluetooth functionality since we don't have approriate driver for those stuffs.
actually the stock rom can have hw acceleration also aosp , but cm7 and cm9 cant have --- i didnt say it by myself maclaw told this
Click to expand...
Click to collapse
this one prove that hw acceleration stuff is definetely not a problem. if stock rom and aosp could have hw acceleration then cm7 is surely could have it too. maclaw might think that SGY doesn't support hw acceleration since he couldn't find the driver needed to enable hw acceleration in samsung's source code. well...it simply because samsung nor broadcomm doesn't release the code to public. we can try to make a global petition stuff for samsung to release all their newest source code to public but I doubt if they'll give them easily to us.
TRANSLATING : Galaxy Y Have GPU ( 99,9 % of smarths have it) and Support Hw Acceleration But Cant make it Work (At Moment) with CM7/CM9 Roms.
UNDERSTAND
why would we listen to you?
1. You failed to established a good reputation here.
2. because you have not finished a project.
basically, you haven't proved your worth here in our forum. Kept on skipping from one project to another without any known progress.
The fact here is that no one is relying on you to make this project a reality. If i were to expect this statement, i would be satisfied if it came from vivek. But from you?
HELL NO!!
Dont pretend like you care. Just to cover up what you can't achieve.
soraci said:
why would we listen to you?
1. You failed to established a good reputation here.
2. because you have not finished a project.
basically, you haven't proved your worth here in our forum. Kept on skipping from one project to another without any known progress.
The fact here is that no one is relying on you to make this project a reality. If i were to expect this statement, i would be satisfied if it came from vivek. But from you?
HELL NO!!
Dont pretend like you care. Just to cover up what you can't achieve.
Click to expand...
Click to collapse
EXACTLY
soraci said:
why would we listen to you?
1. You failed to established a good reputation here.
2. because you have not finished a project.
basically, you haven't proved your worth here in our forum. Kept on skipping from one project to another without any known progress.
The fact here is that no one is relying on you to make this project a reality. If i were to expect this statement, i would be satisfied if it came from vivek. But from you?
HELL NO!!
Dont pretend like you care. Just to cover up what you can't achieve.
Click to expand...
Click to collapse
Dude don't be so rude he just wanted to help it isn't his fault the samsung galaxy y source code is incomplete :banghead:
Sent from my GT-S5360 using xda premium
wooo HQ playback on youtube
Ganster41 said:
Hi, low-end devices users! I have good news for you
As you know, Qualcomm has ended support for their SoCs, based on ARMv6 core, and doesn't release OpenMax IL libraries for Android 4.0+. Someone was crying on Qualcomm's forum, someone try to understand, how to extend GB proprietaries to support new Google OMX extensions, but nobody try to modify libstagefright, and disable using new unimplemended functions...
I spent about a few weeks, learning stagefright architecture, and differents between GB and ICS OMX layers...and now I ready to show it to you
I have only ZTE Blade, and can make ROM only for it. You can download it here. In addition to worked hardware-accelerated video playback, and camcorder, it builded with Linaro GCC 4.7.1, and has a little UI speedup(if it not a placebo ). ROM based on KonstaT device tree, thanks him for it.
Oh, my Dropbox temporary blocked to public links. I upload ROM to letitbit too.
Modified framework's sources can be found on my github. Besides it, you need to add one global define to your device's BoardConfig.mk - COMMON_GLOBAL_CFLAGS += -DQCOM_LEGACY_OMX
UPD: I make same changes in CM10 sources tree, but it doesn't working, and I can't try to fix it, because haven't enough disk space to build CM10 ROM. I think, Google changes OMX API again, and it needs more fixes to get it working. You can download sources from here. For now I not interestid in CM10, because now it laggy and has some not good issues.
UPD2: Please, if you want my help with integration problem, attach logcat at the time, when you try to use vide playback/camcorder. I can't help without any information.
UPD3: If you trying to make port for your device, this post can be helpful. Thanks to cougarcougar for it.
UPD4: We still get errors, if trying to play videos from some apps(e.g. Android browser) in not-fullscreen mode. gralloc or mmap returns error, when try to map buffers from NativeWindow. If anybody have ideas how to fix it, please write it here, or to my PM...
Important addition!
Devices based on MSM7x27 chips has two different versions of OMX libs.
"Oldt"(for froyo?) has an unknown padding between color components parts of returning buffer. I have fixed that for most videos, but some strange resolutions are still gets broken colors with green line on top.
"New" version are present in Samsung/LG devices, who has official Gingerbread ROMs. It returns correct buffer in dfferent color format(YV12, instead of NV21), but it laggy on VGA+ videos. Now don't know why. May be it convert resulting buffer to YV12 on CPU... I will try to understand it later.
I think you can use "old" libs from ZTE Blade on any device, because "new" libs work on ZTE Blade too.
PS: If you want to thanks/support my work - you know where you can find button for it.
Click to expand...
Click to collapse
Yes it's Possible but our 3D Still isn't functioning ! So For now It will not work !
hmmm, that is an interesting problem lol,,
Hi!
I have great respect for the people that give us our great ROMs, and i KNOW that that is hard - but my question is: why exactly is it that hard?
This is just a question out of curiosity, because I would really like to understand the unerlying problems that cause all the other issues.
I was under the impression that the Android stack runs on top of the Linux kernel.
Usually, the Linux kernel is the Hardware Abstraction Layer, and apps and ROM, in theory, should be kind of hardware agnostic?
e.g. the Bluetooth Issue on our Captivate Glides: I would guess that Android communicates, through some API, with the kernel's BT stack/driver. There must be some (open or closed source) driver available (worst case: some .so module ripped out of an official ROM, maybe?). So why does the headset profile not work? Did the APIs change? Are custom ROMs forced to use another version of the driver?
It also happens to this 50$ chinese tablet i have here: some ROM screw up the touchscreen, some break audio, and so forth. Why can't there be some way of installing a generic ROM, and then side-loading the OEM's drivers?
Thank you again to all ROM developers! This is NO WAY a complaint. Just pure curiosity!
I may be out of my league when trying to describe this, but the processor in our phones is somewhat different to the processor in the bulk of other phones. This is where majority of the issues came from in porting ICS to the glide before ATT released it. Even after the first official ICS update, the modders here were the ones who fixed the keyboard lights... I changed up to JB because the GPS wasn't locking quick enough and PACROM had all the quick toggles and the speed/gps lock I needed.
Sure the kernel is the underlying part that pulls it all together, even still there is all the drivers that need to work with it. If there isn't a bluetooth/wifi/HW Video driver for the version of the kernel, then it gets really tricky and now its coding for a piece of software to speak with the hardware ..... We have things that partially work, but not fully ...as with everything computers, in theory things that "should" work, don't always... I'm an IT tech.. I run into weird **** all the time that "should" work ... takes time, but with persistence and the right skillset, majority of the time a resolution can always be found.
Since modifying OMX cores, ibstagefright, and the qdsp service were unsuccessful in enabling full hardware acceleration in videos, and camcorder...
How about if their leader (the adreno 200 drivers) is the culprit of all the sluggish hardware acceleration! on the ARMv6 phones like ours.
Going to the point, has anyone made a pursuit in modifying the drivers itself? like forcing the drivers to be compatible with the modified libstagefright and also OMX cores? coz it seems they function as a whole, i mean, there is some sort of unity going on when they're in operaiton. (just an opinion)
Since Qualcomm released these drivers, how about the connections going to the OMX cores, ligstagefright, or even the qdsp service? Did they modified it? or just remained the same, like the drivers in GB?
Coz I gotta feelin' that the drivers is the bug here...
From what I have read in this post "Fixing the OMX Driver problem in ICS"
scottrix said:
OK, I have put lots of tracing for all omx calls to the binary codec in the omxcore and got logs for this from both ICS and GB. There isn't any difference in the calls and there aren't any differences in the parameters passed to those calls. Looking at include files the structures used in these calls have not changed (which might make the tracing look OK, but the binary data different there by upsetting the GB driver when given ICS structures). My only conclusion is that the ICS drivers for hardware graphics acceleration (EGL, GLES, OpenVG) use more resources from the qdsp5, or affects the qdsp5 in a way that stops the GB OMX codecs working. I believe the ICS graphics drivers from QCom are:
vendor/qcom/msm7x27/proprietary/lib/libsc-a2xx.so
vendor/qcom/msm7x27/proprietary/lib/libgsl.so
vendor/qcom/msm7x27/proprietary/lib/libC2D2.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLES_android.so
vendor/qcom/msm7x27/proprietary/lib/egl/libq3dtools_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/libEGL_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/eglsubAndroid.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLESv1_CM_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLESv2_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/libOpenVG.so
vendor/qcom/msm7x27/proprietary/etc/firmware/a300_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/leia_pm4_470.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/leia_pfp_470.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/yamato_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/yamato_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225p5_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a300_pm4.fw
Of these files I could only find the following in GB:
system/lib/libgsl.so
system/lib/egl/libGLES_android.so
system/lib/egl/libEGL_adreno200.so
system/lib/egl/libGLESv1_CM_adreno200.so
system/lib/egl/libGLESv2_adreno200.so
So I deleted the missing ones and copied the GB ones over the ICS ones. This seemed to give me a "working" system, but with no display. Does anyone know how to get graphics on ICS working without using hardware graphics drivers ? If I could do that it would test my theory that the ICS hardware graphics acceleration libraries (EGL, GLES and VG) are stopping the hardware OMX codecs from working.
Click to expand...
Click to collapse
maybe from here there should be some very useful info in getting along the OMX cores and codecs, and the adreno drivers
Hopin' this could really help in improving ICS in our devices.
Can I ask one possibly silly question...? Video acceleration is flawles on jellybean, right? How can it be fully functional in JB and not in ICS...? I mean... Was any kind of driver released on JB and not on ICS...?
polfrank said:
Can I ask one possibly silly question...? Video acceleration is flawles on jellybean, right? How can it be fully functional in JB and not in ICS...? I mean... Was any kind of driver released on JB and not on ICS...?
Click to expand...
Click to collapse
After JB was released, there was no point to continue work on ICS. So our devs continued their work on JB and found a way to get it work.
4ndaKava said:
After JB was released, there was no point to continue work on ICS. So our devs continued their work on JB and found a way to get it work.
Click to expand...
Click to collapse
ooh. okay, that's odd. hardware video acceleration works on JB, while the adreno drivers are based on ICS? Afaik, the ICS drivers were used in JB and it worked, but when it comes to the OMX, like we already knew, HW acceleration works after some modding on the core libraries (right?)
If the ICS drivers are not used in JB, the devs might knew something about this (Driver - OMX).
man! I think it's time to reverse engineering the OMX cores, together with the QDSP service (I think, its his master) then )