Is the bluetooth stack in the kernel or the ROM? I'm running the latest AOKP nightly and I get no ID3 info over bluetooth, and my Pandora app won't connect to the Pandora app on my car stereo. So I'm thinking it's a stack issue. So, before I start flashing random kernels to try to fix it I thought I'd ask to see if that was even a viable option.
Thanks in advance!
Sent from my Nexus 5 using Tapatalk
Anyone have any input? I'm on a different kernel now and still same issue.
Sent from my Nexus 5 using Tapatalk
my95z34 said:
Anyone have any input? I'm on a different kernel now and still same issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Bluetooth, Wifi and Mobile radio are all in the baseband, neither the kernel, nor the ROM.
kangelov said:
Bluetooth, Wifi and Mobile radio are all in the baseband, neither the kernel, nor the ROM.
Click to expand...
Click to collapse
Correct, to an extent. I believe the stack is in the ROM or the kernel. Just like the jump from 4.2 to 4.3 brought many bluetooth features on the exact same hardware / baseband.
Sent from my Nexus 5 using Tapatalk
I don't know how much this helps but when I was on the s3, I was told the reason custom kernels couldn't boost bluetooth audio was because it was controlled by the radio itself
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Any other input?
Thanks!
Sent from my Nexus 5 using Tapatalk
It depends. On the nexus it should be in the ROM.
I say in the ROM but the Bluetooth stack should be a kernel module/binary.
On other devices kernel modifications required modified sets of modules to work with their kernels but I don't think this is an issue with the nexus line.
You will usually know if a kernel uses modified binaries because firstly it will be a flashable zip rather than a boot.img and secondly because they will usually include a revert zip for changing back to a default one.
Now I know this doesn't help you much but I can't comment certainties because I haven't got my n5 yet
Sent from my Nexus 4 using xda app-developers app
Related
make phone call have sound problem!
anyone know what problem, i tried cm and miui have same problem
Do a little searching would ya.
Sent from my LG-P999 using Tapatalk 2
There's a Q&A section for this type of thread
Sent from my Hellfire Kindle using Tapatalk 2
me too
i flash v21j.kdz
and restore cm7 by recovery
and issue in call
my god
i go there, didn't find out anything with this problem.
This is a known issue.
Problem is with the baseband. It affects all known ROMs. If you want to make phone calls, you'll have to revert back to the older baseband, or go with stock 2.3.4 that was pushed.
nobody can fix that? may be just need cm or miui find out fix.
Where's the mod for this forum?
buru898 said:
Where's the mod for this forum?
Click to expand...
Click to collapse
Lol right!?
Sent from my LG-P999 using Tapatalk 2
Flash v21e baseband. Problem solved game over
Sent from my Galaxy Nexus using xda premium
The fact that two threads have been made here that shouldn't be here and the thread that was titled "Farewell" lasted this long (I messaged the mod and asked them to lock the "farewell" thread cause of that guy) makes believe even more than ever, not only has T-Mobile given up on this phone but so did our mods LOL.
Sent from my LG-P999 using xda premium
To those with the new baseband and with custom ROMs, have you tried to update your RIL using getRIL? https://play.google.com/store/apps/details?id=com.sibbor.getril&feature=nav_result#?t=W251bGwsMSwyLDNd
Mods here don't give a ****.
Sent from my LG-P999 using Tapatalk 2
Alakratt said:
To those with the new baseband and with custom ROMs, have you tried to update your RIL using getRIL? https://play.google.com/store/apps/...getril&feature=nav_result#?t=W251bGwsMSwyLDNd
Click to expand...
Click to collapse
Even with matching RIL/Baseband it still does the same thing on a custom ROM...verified that yesterday when I manually pushed the RIL to my phone...after submitting the RIL to Rob so he can update his app...
Sent from my LG-P999 using Tapatalk 2
i did, but getril nothing ril match new baseband
Have any of you tried using soundabout pro from the market as a temp fix for the Cm7 Bluetooth calling issue?
Sent from my LG-P999 using Tapatalk 2
Bluetooth works fine man.
Sent from my LG-P999 using XDA Premium App
nicdub said:
Bluetooth works fine man.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Incorrect.
If you are on the March 2012 baseband, BT CALL AUDIO does NOT work. Media audio does. This applies to ANY ROM that's not stock LG 2.3.4. There is the option to run a "modded" stock ROM such as BuRom & kewes (sp?) rooted, modded stock 2.3.4. Pair up with faux's GB specfic kernel and it's not terribly bad
You can also attempt to downgrade to an older baseband via kdz method.
As for G2Xer's question, I have not used it, I'll take a look at it, but I think it's more of a driver issue or something like that causing the problem.
Sent via my Sosei "II" Bakedbean Iconia A100.
justjackyl said:
Incorrect.
If you are on the March 2012 baseband, BT CALL AUDIO does NOT work. Media audio does. This applies to ANY ROM that's not stock LG 2.3.4. There is the option to run a "modded" stock ROM such as BuRom & kewes (sp?) rooted, modded stock 2.3.4. Pair up with faux's GB specfic kernel and it's not terribly bad
You can also attempt to downgrade to an older baseband via kdz method.
As for G2Xer's question, I have not used it, I'll take a look at it, but I think it's more of a driver issue or something like that causing the problem.
Sent via my Sosei "II" Bakedbean Iconia A100.
Click to expand...
Click to collapse
What's up Jackyl. Thanks for your reply. I came up on this app thinking that it would reroute call audio into media audio. I'm going to try and downgrade my baseband soon per neowaves directions on the Hellfire forums. Just waiting for my sis to return my USB cable lol?
Sent from my LG-P999 using Tapatalk 2
G2xer said:
What's up Jackyl. Thanks for your reply. I came up on this app thinking that it would reroute call audio into media audio. I'm going to try and downgrade my baseband soon per neowaves directions on the Hellfire forums. Just waiting for my sis to return my USB cable lol?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
When you downgrade successfully post a link to the method you used. I am tired of waiting for this to be fixed.. I am running Cm7 nightly .. and Cm10 seems a dream - most devs have moved on now.. so I should at least get the best working phone I can
James
justjackyl said:
Incorrect.
If you are on the March 2012 baseband, BT CALL AUDIO does NOT work. Media audio does. This applies to ANY ROM that's not stock LG 2.3.4. There is the option to run a "modded" stock ROM such as BuRom & kewes (sp?) rooted, modded stock 2.3.4. Pair up with faux's GB specfic kernel and it's not terribly bad
You can also attempt to downgrade to an older baseband via kdz method.
As for G2Xer's question, I have not used it, I'll take a look at it, but I think it's more of a driver issue or something like that causing the problem.
Sent via my Sosei "II" Bakedbean Iconia A100.
Click to expand...
Click to collapse
Sorry didn't know there was an issue with Bluetooth and that baseband. I myself never found a good reason to upgrade. Glad I didn't!
Sent from my LG-P999 using XDA Premium App
nicdub said:
Sorry didn't know there was an issue with Bluetooth and that baseband. I myself never found a good reason to upgrade. Glad I didn't!
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Be thankful. Lol any update on whether or not this method worked?
Sent from my LG-P999 using xda app-developers app
Update: I emailed the developer but he said there's no way to reroute the Bluetooth call into the media. He's tried but said he and others have hit a couple blocks.
Additionally, I tried again to downgrade with no avail. For some reason my XP machine does not recognize my G2x when in SW mode. I know were all awaiting for CM10 BUT Im crossing fingers that our great dapharoah will take a look at fixing Bluetooth (no he never stated anything im just assuming since he's working on cm7 still).
Any ideas gentlemen?
Sent from my LG-P999 using Tapatalk 2
G2xer said:
Any ideas gentlemen?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Let's try comparing logcats from a g2x with v21y baseband and stock gingerbread connecting to a Bluetooth device and making a call, to a cm7 device doing the same thing. We should be able to find some sort of discrepancy correlation in the logs if we look hard enough.
Sent from my LG-P999 using xda app-developers app
BuddhaTeh1337 said:
Let's try comparing logcats from a g2x with v21y baseband and stock gingerbread connecting to a Bluetooth device and making a call, to a cm7 device doing the same thing. We should be able to find some sort of discrepancy correlation in the logs if we look hard enough.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I can help with that if you'd like.
I have everything set up with ADB, was doing some private cm10 testing, for a private developer, so I'm set to get logs.
I am on 21y, CM7 weekly, but can flash and go stock in 5 min to logcat both.
G2x-CM7 Weekly 12/09/12 Build, Faux v54 Kernel
Now, this is a thread worth watching
Sent from my LG-P999 using xda app-developers app
sunster said:
Now, this is a thread worth watching
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I don't think it will get fixed though.
The story I've always been told is LG needed to release something, maybe code, and it's something they didn't have to under open source.
Something like that.
Sent from...I can't tell you, the Nazi XDA Moderators will shut it down.
lol i have been following googles code site pertaining to this problem and it seems like even the CM team has ignored it since cm7 came out right after the v21y baseband release by LG that "fixed gps signal"....well it also broke radio usage until owain92 fixed it. but still nobody has solved the cell over bluetooth issue. media plays just fine, just not phone calls. im hoping that by mazout360 and king-nai compiling themselves and incorporating hard fixes into their rom, that they will not overlook the bluetooth issue. i have a feeling that their rom wil be phenomonal when its finished.
---------- Post added at 11:52 AM ---------- Previous post was at 11:44 AM ----------
justjackyl said:
I can help with that if you'd like.
I have everything set up with ADB, was doing some private cm10 testing, for a private developer, so I'm set to get logs.
I am on 21y, CM7 weekly, but can flash and go stock in 5 min to logcat both.
G2x-CM7 Weekly 12/09/12 Build, Faux v54 Kernel
Click to expand...
Click to collapse
now that i got my rant out of the way...
yea, that would be great. i dont have any bluetooth devices to connect to besides my car and i dont want to be that guy sitting in his car playing with his phone and laptop in the parking lot of an apartment complex. lol iwould use catlog but it doesnt work worth a crap for me.
I am new to all this and am trying to understand the kernel, I installed jellybam 3.2.0 and now 3.3.0, when I did that would I have automatically installed a new kernel, or is that not replaced?
From what I have read the kernel allows the jellybam ROM to talk to the hardware, so that said is it possible that the kernel I am using could be what is causing my Bluetooth to keep connecting and disconnecting BUT also my proximity sensor not to work? Sorry if this is the wrong place to ask
I have done a quick search but couldn't find anything to confirm my suspicion.
My kernel at the moment is 3.0.053-g099c572
Sent from my Sensation using xda app-developers app
bluetba said:
I am new to all this and am trying to understand the kernel, I installed jellybam 3.2.0 and now 3.3.0, when I did that would I have automatically installed a new kernel, or is that not replaced?
From what I have read the kernel allows the jellybam ROM to talk to the hardware, so that said is it possible that the kernel I am using could be what is causing my Bluetooth to keep connecting and disconnecting BUT also my proximity sensor not to work? Sorry if this is the wrong place to ask
I have done a quick search but couldn't find anything to confirm my suspicion.
My kernel at the moment is 3.0.053-g099c572
Sent from my Sensation using xda app-developers app
Click to expand...
Click to collapse
Yes every ROM usually includes a kernel, which is supposed to work well with the ROM. Maybe it's the kernel causing bluetooth problems, but it may also be the ROM itself which is buggy, or you firmware which is outdated. You'd better ask in the ROMs thread for more info. There are a lot of things which could cause problems and it's difficult to find out the cause sometimes. If they can help you in JellyBam's thread you could try another ROM and see if problem persists
Sent from my HTC Sensation Z710e using Tapatalk 2
Thanks for taking the time to explain that - it is appreciated and confirms my thoughts
Sent from my Sensation using xda app-developers app
I have an deactivated Nexus S 4G that I am testing roms on. Can I use standard Nexus S roms on it. I do not need use of the cellular radios.
x10knight said:
I have an deactivated Nexus S 4G that I am testing roms on. Can I use standard Nexus S roms on it. I do not need use of the cellular radios.
Click to expand...
Click to collapse
It's more than just radios... There are other small differences that cause compatibilities to be different..
Sent from my Nexus S Dinosaur
You'd need to swap the boot.img inside the crespo ROM with one from the crespo4g in order for it to boot, don't expect everything t work flawlessly though, and don't expect to get a working kitkat ROM either lol
Sent from my Nexus 7 using xda app-developers app
Whats up guys, i been using xda site since my Beloved Nexus One, im saying thanks in advance for the effort of all de Developers working here, take my hat off to all of you... :good::good:
Now my Question, i been using custom roms for my Nexus 5, and im having the same response from all the roms i have try, the Business Look Up enhancement on the dial / Phone app that comes with the new Kit Kat doesnt work, im starting to think that maybe is just some configuration, now i have look in to all the configuration of the app and settings, that i can possibly check and same thing, loving the roms, cant complaint but i really will love to have that feature available since is one of the main features that i probably use the most for what i do for living. Really appreciate if you are using a custom rom right now that all the features are working mainly the Local Business Look Up from the Phone app, please tell me the name...
y try so Far
droidkang
Cataclysm rom
kangakat
on few more..
NOW USING PXS WITH FRANCO KERNEL, AND LOVING IT... BUT IF THERE IS SOMETHING I COULD DO TO FIX THAT I WILL BE SET.THANKS FOR READING...
Pls give me a hand here just check the rom that u using and if u able to type any business name from ur phone app and appears let me know which one u are using
Sent from my Nexus 5 using Tapatalk
First off any ROM you use are you using the Google dialer? If you flashed gapps check the op and make sure the dialer was not replaced by aosp dialer. If your using Google there is a menu button in the corner you can select nearby places in the settings menu.
Sent from my Nexus 5 using Tapatalk
It never worked for me on stock until I updated to 4.4.1
If it helps, rom name in signature
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit