Related
Is there any possibility of implementing AVRCP 1.3 or 1.4 on our own instead of waiting for google? I pair my Incredible to my car stereo via Bluetooth and it would be nice to see the track information appear on the head unit display. It looks like it currently supports AVRCP 1.3 in target role, just not source.
http://source.android.com/porting/bluetooth.html
I would love this feature! I'll be willing to test anything.
Even more so, I would love for my phone to pair properly with my Alpine BT. If the phone has had the BT turned on fresh, and I get in the car - it will pair up without interaction and I can initiate a call from the radio. If I stop the car, get out and do something (gas station, errand, whatever) and get back in, turn the car on - the phone looks like it's paired but I will not be able to initiate a call from the radio. I have to do it from the phone or wait for a phone call to come in before it kicks over to the Alpine BT... (no previous phone had this issue, including the Eris, HTC Touch running Android or Windows, and Moto Razr)
I second this request.
Agreed. Hoping for a fix daily, but understand this may be a serious challenge.
For now, I've been switching back and forth between stock ROM and Cyanogen, where Cyanogen bluetooth without sense UI works fine for me. Specifically, I use the Wii remote software to control various emulators.
Sent from my ADR6300 using XDA App
bump......
Bump as well..
I don't have a way to test this, but just a thought --
In CM6, the latest nightly,
edit /etc/bluetooth/audio.conf
At the very top under [General] you see this:
Code:
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
Try putting source under Enable.
Worth a try <shrug>
You'll need to reboot after making the change.
Did anyone try tdiman's suggestion? I'm currently reading up on AVRCP and the compatibility with my N1 (this DInc thread popped up on google).
I haven't bought my BT Head unit yet, but I'd be interested to see if we can get metadata via CM
I would love to see this implemented in CM Roms
I tied to edit my audio.conf changing the lines suggested above and it doesn't work. I'm guessing because the version of bluez included with android is only 3.69 and AVRCP 1.3 wasn't even a glimmer in the authors eye at that time.
Our only hope of getting this working is either someone compiles the latest version of bluez into a ROM or wait until google does it. Unfortunately from what I have read even Android 4.0 is going to have bluez 3.69 so it may be a long wait.
Total bummer
Edit: what it does do is make A2DP unstable, after editing this file my A2DP kept randomly disconnecting.
CarpeNoctem said:
I would love to see this implemented in CM Roms
Click to expand...
Click to collapse
My guess is that since bluez is part of the core android OS, CM won't have support for it either anytime soon. Hopefully I am wrong though.
No support in bluez, yet...
Well, currently bluez (the bluetooth stack of Android) does not support AVRCP 1.3. But I have started to work on this (google: Fixes for AVRCP 1.0 and preparation for AVRCP 1.3 bluez)
So, in the following months you will have the proper support in Android, which I'll eventually announce in my blog.
Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?
http://blog.gmane.org/gmane.linux.bluez.kernel
jiggytom said:
Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?
Click to expand...
Click to collapse
I have the X and I do not get any track info. My original Droid did display the song information on my head unit.
I have tried every music player on the market and each one says avrcp 1.3/1.4 coming soon...
Google? Bueller? Google? Bueller?
thanks for the amzing post
So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung
well some devs got it into their ics roms, but we are looking for avrcp support for jelly bean now
trungvn1790us said:
So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung
Click to expand...
Click to collapse
This is what im looking for, something universal that can be flashed over a rom to give it AVRCP 1.3 support. BTW, BlueZ now supports AVRCP 1.3
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 installed Cyanogenmod 10.1 B1 to my HOX 2 days ago. I've used CM 10 before.
At CM 10, it was possible to send ID3-Tag from the music on my hox to my car radio.
Now at CM 10.1 my car radio doesn't show me the title, album... anymore.
Maybe i have done something wrong at flashing? It's not included yet?
Thank you
z0nKerl
No, CM10.1 does not support this yet. As it seems, the BT stack was massively changed in AOSP and the fine devs @ CM have not found time yet to fix this. Unfortunately AVRCP > 1.0 appears to still be a niche thing so there is next to no public demand for this, or at least that demand is not visible to the CM devs.
Yes it's sad. For that very reason my S3 is still on stock ROM.
I Hope it will be included fast. I love this feature so much.
Thank you for your answer!
z0nKerl
I've found an interesting post on The Verge about some good chance we'll see BT 4.0 support in the upcoming release (credits: hecareth):
http://www.theverge.com/2013/3/20/4127594/bt-4-0-in-aosp-i-think-its-coming
What does this mean ?
- we will be able to use newer hardware with BT 4.0 BLE, which is alot more energy efficient
- having 4.0 support, we need a > 3.5 kernel, so we will get a new kernel
- next major release is coming to GN
*Of course those are speculations, so we can only wait and hope.
Fingers crossed
Sent from my Galaxy Nexus
Sadly not alot of people even care about this issue. There have been no news articles on engadget, cnet, gizmodo...anywhere to call out google to make this more public. Even here on XDA most people dont care, they just want to flash a new rom everyday. I care and try to keep up on this issue as much as i can but its hard when nobody else does. Its a big issue that google has yet to address.
I think there's kinda a chicken and an egg issue. There are tons of accessories and 3rd party hardware for the iPhone exactly because things like this are supported. Not for Android. Google has quite some work to do in the future releases.
Sent from my Galaxy Nexus using Tapatalk 2
Finally we will get support for bluetooth 4.0, Will this possibly improve the quality of streaming audio when paired with a non bluetooth 4.0 device?
msavic6 said:
Finally we will get support for bluetooth 4.0, Will this possibly improve the quality of streaming audio when paired with a non bluetooth 4.0 device?
Click to expand...
Click to collapse
Well, in that response from the G engineer he said they implemented a simple codec right now, but might come with newer codecs and better codecs later :
"BLE will be the next major feature we are going to add. Other a2dp codec can be added. We only implemented SBC because it's mandatory."
** I'd like if this thread was kept to ONLY contributing to the solution to the known issues, no asking for eta's feature requests in other ROM's **
Its been confirmed that the Audio issue is in the AudioLib's. So far numerous people have been swapping out libaudio's from different device trees has different results. Bluetooth hasn't been targeted yet - I personally believe that the hands free phone over bluetooth is connected to the libaudio.
************************************** EDIT *************************************
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx as found and posted here by lorddavid
The above link has some great insight to what the issue is, it talks about it being the sampling rate of the microphone and the speaker (input and output) being differnt. This is why the playback would change to slow motion .. It makes perfect sense! .. The only question now is how do we implement this into our ROMs to fix it ... I'm guessing there's an audio driver that needs to be modified from the source .. I haven't looked at the source code yet myself but following what was posted above into any of our roms with the audio issue may resolve.
Logcat confirms this :
Exxon02 said:
I can't post in the developer forums, but I have some input on the slow audio issues. I noticed the problem happening with Skype and the new TeamSpeak 3.0 beta, so I scanned for errors in the logcat when starting them. Both programs showed the same error.
E/AudioRecord( 6545): Unsupported configuration: sampleRate 48000, format 1, channelMask 0x1
Click to expand...
Click to collapse
So it appears our issue may be related to the sample rate as previously suggested.
Click to expand...
Click to collapse
********************************* UPDATE - AUDIO **************************
If you would like to test this patch by Adam77Root do a Nandroid backup first. It will get Skype working, however, it will start to use the back loudspeaker (think playing MP3's) for the regular cellular voice calls and for skype. The audio sampling rate is fixed in this patch but you'll be stuck with speakerphone type calls.
Adam77Root said:
Here comes the Skype fix! This also solves using microphone and speaker parallelly. The fix is actually using the stock libaudio from Galaxy Tab 10.1 and adding the necessary modifications to libmedia and libaudioflinger. Voice calls work fine.
Note: These libs have the Samsung audio bug! Sometimes volume settings are a bit weird, even though I have enabled the patch. Be aware of this.
Link: http://www.mediafire.com/?49u6ua55kbr1j6b
Click to expand...
Click to collapse
***************** UPDATE - BLUETOOTH *********************
tonyp said:
bubor contacted me via PM asking about the bluedroid -> bluez port which I recently did for my CM10.1 LG Optimus 2x ROM (Tegra2 as well).
I will answer it here publically to help as many devs on your phone as possible
I had been in contact with Andrei Emeltchenko who managed to properly port bluez for his company.
After my mail he kindly asked for permission to release the sources and published it completely at: http://gitorious.org/android-bluez
You can fork most repos from my Github profile - there's everything except frameworks/base and packages/apps/Settings, which aren't published.
With bluez bluetooth should work exactly the same as on Android 4.1!
Hope this information will help you to get bluetooth rocking on your device as well :good: :highfive:
Edit: of course you need to adapt your device tree to bluez as well.
Here's the commit where I did it for my device:
https://github.com/tonypp/android_d...mmit/b767cdbef5e262daf01d3bb38b13ab01d2cbc18a
You just need to restore the CM10 bluetooth stuff and add the bluetooth packages to the makefile.
Click to expand...
Click to collapse
For bluetooth theres fixes in different forums because bluetooth has been a big problem for other devices with 4.2.2. Even the nexus 7 was having problems on custom roms.
Sent from my SAMSUNG-SGH-I727 using xda premium
spitfire2425 said:
For bluetooth theres fixes in different forums because bluetooth has been a big problem for other devices with 4.2.2. Even the nexus 7 was having problems on custom roms.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I guess a linux box needs to be setup to compile a new kernel... thegreatergood left a link to the sources somewhere, this I recall... What other device are similar to ours in terms of chipset etc? ... S2 ?
yohan4ws said:
I guess a linux box needs to be setup to compile a new kernel... thegreatergood left a link to the sources somewhere, this I recall... What other device are similar to ours in terms of chipset etc? ... S2 ?
Click to expand...
Click to collapse
Again, no, the S2 has Exynos while our phone has Tegra 2, if you're looking for the device that resembles the most of the glides specs, the Galaxy R it's the closest one I think
Maybe is ther any possibilitie to ask for some help in the galaxy r forum? maybe someone can give a look to our roms or give us some hints
Source code for our kernel comes from google AOSP + the code supplied by Samsung here:
http://opensource.samsung.com/ (search for i927)
Samsung has only released ICS code and this is what has been applied against the JB source tree. If that's right or not I have no idea...
As for the sources for the kernels they are all in The-Covenant's github:
https://github.com/The-Covenant
The LiteKernel---Glide repository is thegreatergood's code and android_kernel_samsung_i927 is the source for The-Covenant's kernel.
I have built the LiteKernel source and have the environment setup here. I've just been concentrating on getting the ROM side of things down first. That's coming along well so if you guys can get some insight as to what needs to be changed in the kernel source I'm more than willing to give it a go.
I do own a glide so quick tests are really easy...
what about taking a look on the soruce for the kernel/rom form the offical cm10.1 for the i9103 who has the same tegra 2 chip?
yohan4ws said:
Its been confirmed that it's in the Kernel, so my question is are we missing a driver for the chipset in our phones ? (Broadcom something..)
Click to expand...
Click to collapse
Thanks for making this thread yohan.
I'm not convinced it's a kernel issue though. Maybe a first step would be to get logcats and dmesg from a working ICS system and a non-working CM10.1 or similar system? IMHO important points would be logs during boot, during HSP pairing, and during call initiation.
I can take doing the ICS logs this weekend (wife's phone is on ICS), if somebody can do the equivalent with JB.
Spyke can you point me in the direction of how to setup the build environment for the kernel source ? First thing I'm going to do is follow dmans how to compile and dl thee kernel sources thx for that info and the above.. I can post logcats and dmesg no problem from both...
Has anyone tried the Bluetooth fix for other devices?
Sent from my SGH-i927 using xda premium
yohan4ws said:
Spyke can you point me in the direction of how to setup the build environment for the kernel source ? First thing I'm going to do is follow dmans how to compile and dl thee kernel sources thx for that info and the above.. I can post logcats and dmesg no problem from both...
Click to expand...
Click to collapse
Which kernel you looking to build?
There are two source trees you can start from:
https://github.com/The-Covenant/LiteKernel---Glide/
or
https://github.com/The-Covenant/android_kernel_samsung_i927
I've figured out the Lite-Kernel so far. You follow dman's guide up to the point of the source downloads. Here you just need the kernel source, nothing else. Once that's done you also want to install Linaro for your distro, and then adjust the Build4.X/Build KERNEL.sh files with the path to your Linaro install. After that just go into the correct Build folder and run the Build KERNEL.sh file and you should end up with a flashable kernel.
I've not done The-Covenant kernel at all yet so can't comment there.
I have also done a AOSP + Samsung sources build for ICS in the past, so that may be a good place to start so you can compare the working sources to the other two trees.
Let me know if you need more details and I'll guide you through it.
sorry to bother, but which custom roms does have BT headset working? thx!
spyke555 said:
Which kernel you looking to build?
There are two source trees you can start from:
https://github.com/The-Covenant/LiteKernel---Glide/
or
https://github.com/The-Covenant/android_kernel_samsung_i927
I've not done The-Covenant kernel at all yet so can't comment there.
Click to expand...
Click to collapse
I have The-Covenant kernel running (and a current CM 10.1 userland), but I'm having general audio input issues. Was going to debug the Bluetooth stuff, but running anything requiring audio input hangs.
Logcat shows "AudioHardware: cannot open pcm_in driver: cannot set hw params: Invalid argument". Not very descriptive.
This seems kind of ALSA related. Do you see this with your LiteKernel builds?
I search a little about that error, and found this
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx
http://forum.xda-developers.com/showthread.php?t=1748873
Maybe help a little. Do you think that all the audio issue (bluetooth, skype, sound recorder, etc) is for the same problem?
lorddavid said:
I search a little about that error, and found this
http://e2e.ti.com/support/embedded/android/f/509/p/198799/790457.aspx
Maybe help a little. Do you think that all the audio issue (bluetooth, skype, sound recorder, etc) is for the same problem?
Click to expand...
Click to collapse
Great search, I'm willing to bet that this is the issue right here - audio sampling rate different between input and output. Everything makes sense.
Just have to dig in further now and compare source codes... anyone have the setup and feel like taking a stab at it ? I haven't had a chance to setup an ubuntu VM yet.
epsalmond PM'd me this info ...
epsalmond said:
Hi,
I saw your brainstorming post in the cap glide forum.
I can't post in Dev forums yet (damn noobs ruin everything) but I didn't see the info there so I'm sending a pm.
I have read in multiple places that google has dropped support for systems without NEON instructions
This includes tegra2.
I had the idea to merge kernel from the galaxy r which is basically our phone without a keyboard and diff the audio API to see what's changed. I know jb does have some new audio API's that have caused minor problems with some apps.
I'm travelling in south America so I've had trouble syncing all the sources I need for this, but I should have something in a week or so.
If you can update the thread with this so we have it in the cap glide forum maybe someone else can contribute as well.
Click to expand...
Click to collapse
yohan4ws said:
epsalmond PM'd me this info ...
Click to expand...
Click to collapse
So, that means all the issues may be related ? BT, Audio Recording with default Camera App and Skype/Anyothervoipapp ? If epsalmond it's right, that will mean that we only need to find one solution to solve all the problems, and then boom ! Fully functional JB on the Glide, that means that anybody with the knowledge to compile a ROM will be able to take all the "Unsupported" ROM's like PAC, PA, LS, SL, Vanilla RootBox, and incorporate the "FIX" on them, damn, that would be nice
santimaster2000 said:
So, that means all the issues may be related ? BT, Audio Recording with default Camera App and Skype/Anyothervoipapp ? If epsalmond it's right, that will mean that we only need to find one solution to solve all the problems, and then boom ! Fully functional JB on the Glide, that means that anybody with the knowledge to compile a ROM will be able to take all the "Unsupported" ROM's like PAC, PA, LS, SL, Vanilla RootBox, and incorporate the "FIX" on them, damn, that would be nice
Click to expand...
Click to collapse
I believe so, think about it .... The audio only slows down when the microphone is enabled ... Video Camera .. Skype ... Bluetooth .
Because its a sound issue, it also means its a kernel issue (corrected me if I'm wrong) ... so an updated Kernel will resolve the issues across all ROMs should this be correct.
I have built up an Ubuntu box now and a build environment... I have no frikin idea what I'm doing but I know that I need to find the source for the audio driver ... I believe I found it here :: https://github.com/CyanogenMod/android_device_samsung_i927/tree/jellybean/libaudio
I think that there is a variable set somewhere to the sampling rate and there will be multiple area's that need to be looked at in order to fix the input sampling rate.
Once this is fixed, the only real things left are Torch from the toggles ....picture orientation, and that some apps disappear on reboot unless they're "moved to SD"... and battery too, I guess...
other kernel
Hello,
Build kernel from https://github.com/CyanogenMod/android_kernel_samsung_n1 with our config, but still broken bt audio.
Installed official cm10.1 and PACman 20.1.0 build for galaxy r with litekernel, but broken bt audio too.
bubor said:
Hello,
Build kernel from https://github.com/CyanogenMod/android_kernel_samsung_n1 with our config, but still broken bt audio.
Click to expand...
Click to collapse
Maybe is not only kernel. Adam say in his thread, that he thinks that know what can be the issue, but never say anything more :/