Related
I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.
Just wondering what happened to that thread?
There is an issue with it regarding wifi (possibly others as am not a kernel guru) so it was removed from xda by dg. I hope that the issue gets fixed but in the meantime I have a changed one of my network configurations to wep, which it will connect to as well as open, and am loving the awesome battery life I am seeing.
I am sure dg will get it figured out repost it.
What was the topic, can someone explain? And can someone give me a link, so i can use Google Cache to view it?
Sh put up a kernel from Armand captivate source not at my computer so I can't get the link but you could try firebird armani xda. Bump this later if you don't get anything and I will try and dig up the dead link.
Sent from my ADR6300 using XDA App
Does anyone know or remember what the WiFi problem was?
geokilla said:
Does anyone know or remember what the WiFi problem was?
Click to expand...
Click to collapse
I don't know if this is what DG is referring to, but here is the post and here is the thread.
I hope he decides to also include Supercurio's Audio enhancements in the 2.0 release.
Git Dev resources
If you follow DG on twitter you get to hear all of the new information he puts out. The Firebird 2 Kernel is currently in the works. His latest tweet regarding the Firebird 2 Kernel reads
"TV Out is fixed! The kernel is now 100% working!"
And Supercurio's newest headphone sound tweaks...
Awesome! can't wait.
Hi
Since I'm a new user I can't post in the development forum, so imma ask here.
I have been following this thread for a long time:
http://forum.xda-developers.com/showthread.php?t=1293751
And I'm having a hard time finding a list of known issues for each ROM. I've been looking everywhere but still can't find if BT, HDMI output and 30fps video (just to name a few) are working with the ROMs that are listed in the thread.
I'm more interested in the Compiled CM7 for Infuse and MIUI for Infuse, but they only redirect to the CyanogenMod website and/or give half-answers.
Can anybody help?
Nope none of it works on CM7 or MIUI.
Bt and Hdmi will work when the source codes for gb come out for our phone. Hopefully soon since the last leak came out like last month and was pretty solid.
Not all that sure with the fps issue.
Sent from my SGH-I997
Thanks for clearing that one out for me.
Do you know if we'll be able to port CM9 to the Infuse once the source codes do leak? Or is this not compatible/irrelevant?
Bluetooth isn't waiting on source code, cyanogen mod uses a different Bluetooth stack than Samsung roms, the only thing that will fix Bluetooth is to find a competent developer who had the time, skill, and motivation to get the call audio working over Bluetooth.
So far we have all three, but not all in one developer
the current cm7 compile is otherwise working really well. as kies mini just hit for the infuse you gotta think the full release is right behind it.
Crossing our fingers for source code soon, HDMI and getting our video support back would be nice on custom kernels. Stock kernel is killing my inner child
"the current cm7 compile is otherwise working really well" - so, no HDMI output and no Bluetooth? Otherwise, no problems? I might give it a shot then.
What about CM9? Anybody has a clue?
DenisGuy said:
Hi
Since I'm a new user I can't post in the development forum, so imma ask here.
I have been following this thread for a long time:
http://forum.xda-developers.com/showthread.php?t=1293751
And I'm having a hard time finding a list of known issues for each ROM. I've been looking everywhere but still can't find if BT, HDMI output and 30fps video (just to name a few) are working with the ROMs that are listed in the thread.
I'm more interested in the Compiled CM7 for Infuse and MIUI for Infuse, but they only redirect to the CyanogenMod website and/or give half-answers.
Can anybody help?
Click to expand...
Click to collapse
Kinda shocked that nobody mentioned this.. but this should not have been asked in the development thread to begin with... thanks for choosing the right thread........
As for finding their issues.. just read the threads.. I'd recommend checking out the one with Zeus in the title.. my resources tell me it's a pretty good one...
Sent from my A500 using Tapatalk
DenisGuy said:
"the current cm7 compile is otherwise working really well" - so, no HDMI output and no Bluetooth? Otherwise, no problems? I might give it a shot then.
What about CM9? Anybody has a clue?
Click to expand...
Click to collapse
no cm9....10 chars
Yeah it sucks, it doesn't allow me to connect my Dual Shock 3 controller over bluetooth using Sixaxis Controller application. Official LG stuff really sucks. It used to work flawless when I was on CM7 GB. Now what? I've upgraded to ICS and won't go back to GB. Is there any custom ICS roms with replaced bluetooth stack yet? Can I change the bluetooth stack manually somehow? Does anybody know what I'm talking about???
If you use these tones, i guess it's really hard someone mentally sane will help you...
keep calm.
- Before to install a new rom or any file on YOUR phone, you should already try to know what you lose / what you gain
- ask help of support not mean to reverse all your anger on people which is not, in any way, responsible of your issue, YOU are responsible for the rom YOU flash on YOUR phone.
Clarified this: i am another which noticed some difference in bluetooth connection behaviour, especially in windows, but the most connection issue looks was resolved with the custom released by XBSA.
So i can just suggest to try the custom XBSA rom if you still not flashed it.
I'm just this close from throwing this phone to the wall. All i want is to have ICS on my phone and have the ability to play my emulators using my ds3 controller over bluetooth. Am I asking for too much? And I'm not mentioning the upside down camera problem, grrrrr. I'm really really mad at LG for not releasing the official ICS for P920 and making us try to find a way over these stupid issues...
By the way can anyone confirm being able to connect DS3 to P920 over bluetooth using the sixaxis controller app with the custom ICS rom by xbsall?
Again, getting mad won't help, nor throwing the phone against the wall. Poor bluetooth percormance is caused by a SU760 radio (baseband/RIL) being used in a P92x phone. It will only work fine when LG releases the official P92x (0/5/9) ICS update.
FFS this thread does not belong here.
FFS I know
How can I move the thread?
vpamir said:
I'm just this close from throwing this phone to the wall. All i want is to have ICS on my phone and have the ability to play my emulators using my ds3 controller over bluetooth. Am I asking for too much? And I'm not mentioning the upside down camera problem, grrrrr. I'm really really mad at LG for not releasing the official ICS for P920 and making us try to find a way over these stupid issues...
By the way can anyone confirm being able to connect DS3 to P920 over bluetooth using the sixaxis controller app with the custom ICS rom by xbsall?
Click to expand...
Click to collapse
Try this:
1. Learn a few programming languages - it may take 1 to 12 months to know everything you need to;
2. Study LG's source code for Gingerbread to figure out which parts of the code are specific to our hardware;
3. Download the stock ICS source code from Google and make all the necessary changes;
4. Test your custom Android and make every correction needed to work the way you intend it to.
If you still feel like throwing your phone against the wall, put it in a FedEx envelope instead, and ship it to me. I'd be a proud owner of two Optimus 3Ds. I can PM you my address.
Otherwise, just shup up and respect all the hard work that a lot of people have put into this, just so you can have something to play with on the weekends (including LG employees who have no fault about the corporate decisions that are made by ther employer).
:thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my LG-SU760 using xda app-developers app
Xbsa: "P.S Just like with every other ROM or modification once again i have to say that i don't take any responsibility if something happens to your phone by using this ROM..."
Nobody tell u that you have to flash this rom
Sent from my LG-SU760 using xda app-developers app
If Xbsa 's rom don't suit your needs, go back to stock gingerbread or learn how to develop and build your own version of ics.
First of all let me clear some things up before any more smart asses show up;
I'm not mad at xbsall or any other developers around here, he/she did a great job for the community of Optimus 3D owners and for that i respect her/him. And it's not his fault that the bluetooth stack on his port doesn't work for my intentions. He just ported it i know. It's god damn LG's fault to come up with such a bad bluetooth driver/software.
I won't throw my phone to the wall don't worry, but i feel i'm close to doing that sometimes. I have been struggling with this phone since i've bought it. First the ghost call problem, the delay of ICS, installing CM7 to be able to use bluetooth controllers with the cost of loosing 3D functionality which I've bought this phone for in the first place. And I just felt like that my patience is coming to an end.
nadameu, thanks for your advice but I already have a BS degree in computer programming but I don't have the time or motivation to work on this right now and your post is not funny.
And please don't tell me to go back to GB based CM7 to be able to do what I intend to do because I already know that.
I'm just trying to find out "if" there's anything i can do to make the bluetooth system work on this ICS port just as it did on the GB based CM7 that's all.
Lastly, If I offended anyone in any way then I'm sorry...
I'm sure that once we get cm9 or 10 then we'll be able to use 6axis I would like to use that as well but stock LG roms never worked properly with 6axis... we did get ICS I'm sure we'll get Cyanogen, its only a matter of time
Sent from the Ice Cream Sandwich Truck
vpamir said:
First of all let me clear some things up before any more smart asses show up;
I'm not mad at xbsall or any other developers around here, he/she did a great job for the community of Optimus 3D owners and for that i respect her/him. And it's not his fault that the bluetooth stack on his port doesn't work for my intentions. He just ported it i know. It's god damn LG's fault to come up with such a bad bluetooth driver/software.
I won't throw my phone to the wall don't worry, but i feel i'm close to doing that sometimes. I have been struggling with this phone since i've bought it. First the ghost call problem, the delay of ICS, installing CM7 to be able to use bluetooth controllers with the cost of loosing 3D functionality which I've bought this phone for in the first place. And I just felt like that my patience is coming to an end.
nadameu, thanks for your advice but I already have a BS degree in computer programming but I don't have the time or motivation to work on this right now and your post is not funny.
And please don't tell me to go back to GB based CM7 to be able to do what I intend to do because I already know that.
I'm just trying to find out "if" there's anything i can do to make the bluetooth system work on this ICS port just as it did on the GB based CM7 that's all.
Lastly, If I offended anyone in any way then I'm sorry...
Click to expand...
Click to collapse
No probs, no need to apologyze, but just keep present that this kind of aptitude make ABLE developers go straight away from here!
Developers wants collaborative people! Non people who just is able to flame, show anger and ask ask ask ask ask and pretend!
No offence, just, be careful of the kind of people you are talking about.
Hi, I have a question: In lots of rom there is a hotspot problem, and I want understand why! Is this problem only a kernel problem? In other words, if I change kernel I can solve the problem? Actually i'm using sabsa prime 14, and it's working fine. Mine is only a curiosity
Sent from my HTC Desire S using bad english (excuse me for this)
Re: hotspot problem...
Felix861 said:
Hi, I have a question: In lots of rom there is a hotspot problem, and I want understand why! Is this problem only a kernel problem? In other words, if I change kernel I can solve the problem? Actually i'm using sabsa prime 14, and it's working fine. Mine is only a curiosity
Sent from my HTC Desire S using bad english (excuse me for this)
Click to expand...
Click to collapse
Hi...
First - i'd recommend amidabuddha's kernel thread which gives the insight on the hotspot sproblems on sense 3.6 roms
To my understanding there is only so much kernel can do- but what it does is an important part of the process..
Kernel- is the heart of a system - bridge between hardware and software- "the governor"
, of all smaller (or lesser, specialised steering modules-as drivers-for example)
And the drivers- direct steering modules, are responsible for proper functioning of device's units like radio
, and all its activities like bluetooth, data transfer- to and from the device, gsm signal and many other...
To my understanding- and that is not the deepest one- in many cases, the drivers may be responsible, for poor functioning of a hotspot -as it- in some way- uses the radio module,
, but we all know full well that in most cases development is based on an original-rather limited sources from htc, and there is only so much that dev can do to tweak and improve it...
Another part of- the story of non working hotspots- may be due to the rom limitations as well as they are also containing their own drivers and kernels, but in my opinion- the most probable cause of problem is the driver
Then my answer to your question would be: this is the driver-not the kernel- that is responsible for such malfunction
And yes if you change the kernel for the one containing proper drivers
, is possible to solve hotspot problem that way
,
R: Hotspot problems in lots of roms
Thanks! I understood
Sent from my HTC Desire S using xda premium