Hi there,
i tried searching and couldn't find an answer/solution for my problem so im going to post a new thread,
my s3 wont stream to my Bluetooth headphones (Jabra blue-tooth sport) correctly (it cuts in and out all the time) ever since i went away from stock Samsung ROM to CM10, i originally went to CM10.1 but went back to 10 in an effort to see if blue-tooth would work, it doesn't work on either of the builds, i have tried editing the audio conf file and no luck has been had.
Is there any fix for this or do i simply have to go back to stock rom or CM9 for now, i really cant stand touch-wiz but i need blue-tooth headphones for my workouts
any help is much appreciated!
Flash a stock is rom. Boot in and turn on blue tooth. Wait a few seconds. Reflash jb rom and it may now be fixed. I doing this sorted issues I had with BT and my car.
Sent from my GT-I9300 using xda app-developers app
Flashing any touchwiz ICS rom and turning bluetooth on will fix this. You can even backup your current Rom, flash stock ICS over and restore the CM backup.
You'll probably notice the default name for your phone is "BlueZ" and after you do this it will change to "GT-i9300"
Related
Running newest OTA ROOT ROM now but ever since I rooted to 2.1 the BT ausio works but not the Handsfree for phone. I am also running a leaked 2.1 eris and it to wont connect to phone. My Moto headset will work but not the Pioneer hed unit. Any one else having this issue or found a resolution???
I'm having a similar issue. When I connect to my Jabra Cruiser, this voice says it's connected, the phone reads that it's connected, but when I check it in the settings, all it says is that it is connected to phone media, and doesn't stream anything through the Cruiser. I can't use it for phone calls and it also won't stream my music like it did prior to the flash.
I'm running
Firmware - 2.1
Baseband - 2.41.05.02.03
Kernel - 2.6.29-564a4a15
[email protected] #1
Build - 2.6.605.4 CL140744 release-keys
Software - 2.26.506.4
any ideas on how to get the ability to use bluetooth back?
I use my bluetooth handsfree in my 2008 Accord every day. I've NEVER had an issue with it until the new 2.1 rooted roms. It would connect to my phone and dial the number, but the audio would come out of the phone instead of my car speakers. This also only happened sometimes, not all the time..
However, I recently flashed Evil Eris v1.1 and I have yet to experience any issues with it. Bluetooth has been working flawlessly for me. I'm still unable to transfer my contact list to my car though. I thought this was supposed to be possible with 2.1?
hopefully a dev will read this and be able to give some input on my idea.
Since I'm not 100% sure how to do it, I want to give my idea and see if it will work...
I downloaded the milestone 2.1 apk dump file that I found floating around and was seeing what apps were worth anything. The only one I may use is the MotoPortal app. It seems to launch on the Eris, I just haven't been able to try it out fully yet... Anyways... Back to issue... I noticed that there was apk files for bluetooth.
Is there any way to rip the bluetooth apk from another ROM and replace the bluetooth stuff on the Eris? Like maybe revert back to the bluetooth apk from 1.5 so we can fix the bluetooth issue with 2.1?
Just a thought. i'll be a guinea pig if someone could give me a how-to.
So... I tried dumping in the Milestone 2.1 bluetooth file into a zip of the eris official 0.5.4 ROM I had to see if maybe replacing the file would work. Well, after wiping my phone, I tried the install, and here is what it gave me.
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:Wrong digest:
system/app/Bluetooth.apk
E:Verification failed
Installation aborted.
Does anyone have any other ideas on how to get bluetooth working correctly on 2.1?
BT audio is working for me but calls will not. I had the same problem on 1.5 though. My wife's Moto Droid works perfect on the same unit.
This worked for me.
I had the same problem when I rooted with Grdlock's Rom. I switched to SENSE-ABLE and was able to get both phone and music to BT with my Sony car radio. Could just be a coincidence...but it works great!
I tried the Sense-able rom, and my phone is still doing the same thing as before. Hopefully since the update for the Droid is out, we aren't too far behind.
I ran the Vanilla Rom the other day after a wipe and now I am having no bluetooth issues. I'm not sure if it is just the other roms or if any of the nexus stuff was causing it but I'm good to go now.
I'm only using the nexus lock on my phone. no live wallpapers or nexus theme anymore.
Sent from my Eris using the XDA mobile application powered by Tapatalk
I originally posted in the JB update thread, but realize posting a separate one is best.
Looking for some help from the experts (but I think waiting for JB fastboot files may be my only option).
I installed the JB leak last night, and restored my apps using TiBU. All was well until I re-booted, and got stuck in the startup animation. Then it hit me.... I selected restore apps AND system data (stupid).
I found a thread elsewhere that got me out of that, into recovery, and, and allowed the phone to boot. Root stayed intact, and all appeared to be well, but now I realize several problems:
1) No notifications, alarms, or ringtones. (Startup sounds that did work prior to the fiasco are now silent, as well.)
2) All sound during phone activity emanates from the speaker. When Bluetooth is active, sound comes from the earpiece AND the speaker. Headphones inserted into the headphone jack have no effect.
3) MP3 files will not play with the stock player.
UPDATE: MP3 files will play with PowerAmp, but again, only through speaker. The system knows headphones have been plugged in (I get a "high-volume" warning) and un-plugged (audio stops), but will not play through them.
I have performed FDR and re-installed the update to no avail.
ANY help will be greatly appreciated!
Thank you,
Andy
Just "thinking out loud." here.....
If I install Safestrap, and load another ROM (like spc_hicks09 -
BDH JB 98.72.8) would this be a work-around?
Andy
Well seeing as the leak is an update then yea you might just have to wait until something official comes out.
edit - suggested something you already tried.
Thanks for the reply.
I'm limping along with vibrate turned on for all alerts and ring, and put a piece of tape over the speaker so I can use my Bluetooth headset. (Still hear the other person talking, but it's a lot quieter.
If anyone has other ideas how I can fix this (I. E. Load another ROM via SS, maybe?) I'm all ears.
In the meantime..... C'mon fastboot files!!
Andy
EDIT: Oh, another symptom: streaming music services like Pandora and Jango won't play. Song titles just flip from one to the next as if of played the entire song in one second.
i don't see where it would hurt to run another rom in safestrap to see if its localized to the jb ota or if it's something bigger.
Look for a rom built for the jellybean kernel, load it up, and come back with results.
It's what I would do anyways.
Hope all goes well, let us know how it goes.
I'm curious to find out as well. I don't want to steal the thread, but are the hardware drivers for stuff like audio open? If so then yea it would probably be no problem, if not then not sure. Yes, please do let us know.
SUCCESS!!!!!!
AHHH-HAHAHAHAHAAAAAA!!!!!!!!! :laugh:
I installed SafeStrap, loaded up Rage, and am now rockin' a fully-functional Droid Razr MAXX!!! :victory:
I had a weird situation for awhile where no audio would play from the speaker (exactly the opposite of my original problem), but I used the JB vibrate/sound-on lockscreen slider to switch back and forth, and now I appear to be running at 100% functionality.
A BIG thanks to CamoMike over at droidforums for posting the method to escape the perpetual boot animation (before my battery went TU), and to spc_hicks09 for a great JB ROM!
Andy
AndreXX said:
AHHH-HAHAHAHAHAAAAAA!!!!!!!!! :laugh:
I installed SafeStrap, loaded up Rage, and am now rockin' a fully-functional Droid Razr MAXX!!! :victory:
I had a weird situation for awhile where no audio would play from the speaker (exactly the opposite of my original problem), but I used the JB vibrate/sound-on lockscreen slider to switch back and forth, and now I appear to be running at 100% functionality.
A BIG thanks to CamoMike over at droidforums for posting the method to escape the perpetual boot animation (before my battery went TU), and to spc_hicks09 for a great JB ROM!
Andy
Click to expand...
Click to collapse
help this just happen to me I had X-mas Jelly Bean build of 98.72.8 everything was working fine I decided to upgrade to 98.72.16 today downloaded the 98.72.8 to 98.72.16 patch transfer over to my phone but by mistake i put the file on internal memory did not notice i still had 98.72.8 on the SD thinking it was the .16 release that I just transfer I reinstall leak 98.72.8 on my phone again I thought everything was running great until I notice ringtone is not working but speaker & earpiece & bluetooth also working {{{{ one thing I discover just now if on a call I hit the speaker button and then try to go back to earpiece sound will continue coming out of back speaker no matter what }}}}}} and I don't know why youtube videos are not working then I check the build and it was still 98.72.8 tried re-flashing 98.72.8 in hopes that it will start working again nothing factory reset nothing.
Finally I flash 98.72.16 hoping it will kick start something nothing help!!!
I still have root under 98.72.16 tried what you did safestrap 3.11 but Rage rom link is currently dead tried other jelly beam roms to see if sound was working on them but can't get to boot they just reset thinking is the kernel difference
haven't tried flashing the full 98.72.16 release yet afraid to brick it since it's for ICS to Jelly beam
another thing I just found testing when I make calls everything get send to back speaker but when I receive a call I can use the earpiece until I hit the speaker button then I can't go back
tried 5 roms with safestrap none of them boot phone keeps reseting
DiaBiTis.SE.JB.ROM.v2.0.0-R3Ds
Eclipse-RazrJB-v1.1
JellyHaters-V3-98.72.8-XT912
PNuT.BuTTa.SE.JB.ROM.v2.0.0-R3Ds
Aokp422_R03
Fixed my search took me to this http://www.droidrzr.com/index.php/topic/11894-soak-test-starting-with-download-files/
DROID RAZR Utility 1.90
option one flash ICS to Leak JB sound is back to normal
Hey guys, i'm new as far as posting on the forum is, but i have been flashing ROMs for quite a while now. Now, i have a peculiar problem that should probably be shared on Omega ROM thread, but as a newbie i can't post there, so i'll try here...
I started having problems as soon as i flashed Omega 50.1, when in call, and putting that person on the speaker, as i often like to do. Usually, it doesn't take more then 20 seconds to lose the connection, and both me and the called person get the squelchy noise. Now, when i flash the ROM it works perfectly, so i figured it had to be a Modem, one of Mods i'm using, or perhaps the Moto theme. After flashing (full wipe) several modems and Moto theme, everything was fine. Moving on, as I use a few Mods that can be downloaded for the ROM, and after installing and testing each and every one of them, it seems that when i install Modded Camera 1.52 the problem with speaker noise comes to life. So when modded camera installed, you can't put a caller or a person you called on a speaker without losing the connection and getting weird noise out of speakers.
Having this in mind, can someone try to replicate the problem, cause to me it really seems it might be a bug.
Mitrandir011 said:
Hey guys, i'm new as far as posting on the forum is, but i have been flashing ROMs for quite a while now. Now, i have a peculiar problem that should probably be shared on Omega ROM thread, but as a newbie i can't post there, so i'll try here...
I started having problems as soon as i flashed Omega 50.1, when in call, and putting that person on the speaker, as i often like to do. Usually, it doesn't take more then 20 seconds to lose the connection, and both me and the called person get the squelchy noise. Now, when i flash the ROM it works perfectly, so i figured it had to be a Modem, one of Mods i'm using, or perhaps the Moto theme. After flashing (full wipe) several modems and Moto theme, everything was fine. Moving on, as I use a few Mods that can be downloaded for the ROM, and after installing and testing each and every one of them, it seems that when i install Modded Camera 1.52 the problem with speaker noise comes to life. So when modded camera installed, you can't put a caller or a person you called on a speaker without losing the connection and getting weird noise out of speakers.
Having this in mind, can someone try to replicate the problem, cause to me it really seems it might be a bug.
Click to expand...
Click to collapse
first thing never flash more than one mod at a time. Always reboot when you flash any mod. Now what you have to take out the camera.apk from the omega rom zip file and put it in your preload/symlink/system/app by replacing the modded camera then set oermission and reboot. Hope it works otherwise reflash the rom again.
Good luck
Hi guys!
I've a problem but not sure it's pacman (the rom im using atm) fault..
It seems I can't make works the vocal commands on the phone while I'm connected with bluetooth (im using the one on car)..
With original cable headset and from phone I've no problems and Google now works.. But when I try to activate from car it isn't initialising and it stuck, freeze and sometimes reboot the phone
I spend lot of time in car for work.. Could be so nice if I can fix it.. Any suggestions?
i was reading around theres an app called "bluetooth launch" and saw on some phones u can solve the problem with this app using it to make launch com.google.android.googlequicksearchbox.voiceseachactivity, but on my sg2 seems isnt working..
i should try with diff setup but ive no idea how to, i can just keep try quite randomly..
any1 have an alternative solution or found wich one of the several option i should pick up?
for real none of you have this problem or can help me?
can u tell me atleast some rom where u know for sure there isnt such problem?
whazi said:
for real none of you have this problem or can help me?
can u tell me atleast some rom where u know for sure there isnt such problem?
Click to expand...
Click to collapse
Well buddy never used any 4.3 roms because of lots of bugs. But you will never face this issue in Stock 4.1.2 jb roms. You can try Neatrom if you want.
Sent from my iPhone using Tapatalk
so its a bug with all 4.3?
i'll have a look into Neatrom, was just hoping i could fix it withouth have to downgrade android
To be honest, I don't use bluetooth, although I am on a 4.3 ROM. Do you use dorimanx kernel? Or stock pacman kernel? I know dorimanx users are having troubles with bluetooth audio currently. So if you are using dorimanx, give it a go with stock pacman kernel.
If you are on pacman kernel, may as well try dorimanx (counter intuitive I know), and apolo kernel, you may as well give it a shot. Make sure you read the OP in each case to make sure you get the appropriate kernel version for your ROM.
Sent from a galaxy far, far away
I use dorimanx come i need bln!
BT in general is working, I can transfer files I can stream audio and make calls in my car
It's just the voice command part that isn't working on BT, but actually works with BT off
I use dorimanx come i need bln!
BT in general is working, I can transfer files I can stream audio and make calls in my car
It's just the voice command part that isn't working on BT, but actually works with BT off
any1 can suggest me a rom that works with bt voice commands?
if 4.2.2 - 4.3+ better.. but well i could think to downgrade even more if theres a chance to get this sorted
My RAZR worked perfectly with CM12, but ever since I started using CM13, my Bluetooth begins to stutter or will not remember paired devices. I will need to reboot, then my paired device is not present, I need to Repair. I turned OFF Smart Lock (Trust Agent) from Google, this seems to make it worse.
When I do have BT working, it will work for a while ( < 15 min ) then it will start to stutter, and will not reconnect when I turn off BT then back on, I need to reboot.
I tried Clean Flashing numerous times, with no luck, It's definitely a coding error since I tried my phone on numerous BT devices, and it does it every time.
I turned off Smart Lock (Google Trust Agent) since this was always asking to setup every time I pair my device and I thought this was the problem but the problem remains.
My last build was 20160304-Nightly-spyder, (Yesterday's build).
I had the same problem on latest CM13 umts spyder. I was fed up and went back to stock ROM (ICS), which works perfectly not only with bluetooth, but in every other respect as well. It's a much smoother experience to CM13.
EDIT: Oh man. 4.0.4 doesn't support TLS 1.1 or 1.2.
I think I might go back to CM11/12/12.1.
EDIT2: I'm going to try MoKee ROM: http://forum.xda-developers.com/showthread.php?t=2596176
I'll get back to you and see how bluetooth is.
EDIT3: MoKee ROM killed itself (it started doing weird things from the get go, like asking me for my google account during the welcome phase after I had already logged in), and I didn't have enough time to test bluetooth with my cars headunit, which is where your symptoms occur for me, but I was able to test it on my PC's bluetooth dongle, where it showed the exact same symptoms as CM13 did. That is, I would have to reinitiate the pair every single time my phone connected, and not only that, but I would end up in a pairing loop, where as soon as I'd accept the pair, it would ask me again to accept a new pair, ad infinitum. Given this, I'm going to conclude that MoKee ROM's bluetooth is not the answer for our problem. By the way, the next time I booted MoKee ROM it reinitated the updating apps thing at startup, like I had just wiped cache (which I hadn't), and after I let it finish, it never booted properly.
The latest CM13 has an interesting commit: http://review.cyanogenmod.org/#/c/137459/
It might just solve one aspect of our problem so I'm going to test it and come back to you.
EDIT4: Nope. Same problem with headunit and dongle. FYI headunit is Pioneer MVH-X380BT (not old).
EDIT5: I'm on LiquidSmooth KitKat and I've called it a day. Bluetooth works as it should.