I just recently installed SHOstock2 1.0 (Updated from CM7.2 RC1) and when I use bluetooth devices, whether it be a headset, in-car hands free, or a BT speaker dock, the bluetooth connection fails after about 60 to 90 seconds.
What's odd is that the phone's bluetooth status icon appears as if it were connected to a device, but I am unable to reconnect the phone or any devices until I power cycle and/or reboot the BT device and, often times, the phone itself.
I searched through the fourms and it doesn't appear that many others are having such an issue. I'm assuming it must be something unique to my environment, but I can't imagine what.
Could it be a side effect of coming from CM7 without first flashing back to stock? Do I need to run a utility to clean up the phone? (I've seen discussions of a kernal clean-up script, for example)
The rest of the SHOstock2 installation appears to be functioning properly. Wifi is good, Email/Gmail works great, phone calls are loud and the sound quality is excellent. Camera works well.
Any ideas of what I could try to remedy this? Thank you!
I'm currently using shostock as well but I have no bluetooth devices to test this on. However I believe the kernel cleaning zip can be found here: http://forum.xda-developers.com/showthread.php?t=1428530 . I think it mostly just wipes your cache / dalvik cache a couple times though.
Related
Anyone ever have connectivity/inconsistent connectivity with Bluetooth on the Vibrant?
I never use it, but another XDA user mentioned they were having issues.
If you have had issues, what suggestions can you make?
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Me and my wife have both had the same issue with a paired device not connecting and you have to turn Bluetooth off and then back on and all is well. Doesn't happen often but can be a little annoying when it does. By the way my wife's vibrant is completely stock and I'm on cm7.
Sent from my SGH-T959 using XDA App
oka1 said:
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Click to expand...
Click to collapse
I quit reading when I saw m35. Love that car. Oka, want to hire a NC boy for cheaps? ha.
I use Jawbone Era and it randomly disconnects even when phone is in my pocket and bluetooth in ear. It reconnects a few times but mostly I have to turn the headset off/on to reconnect. Froyo 2.2.1 is better with Bluetooth than 2.2.0
It might be the headset though, our phonen is one of the FEW devices that has Bluetooth 3.0
Even the new LG G2X has 2.1 and not 3.0
I use bluetooth headset regularly on bionix 1.3.1. No disconnections, but the signal strength seems week as there is lot of distortion if the phone is in my pocket. So I have to always hold phone in my hand.
Sent from my SGH-T959 using XDA App
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
I connect to my car stereo and sometimes I hear skipping. With my plantronics headset sometimes the signal gets weak if the phone is in my pocket
Sent from Glensta's phone
It is a weak signal in the phone. I have had several phone over the years and my old nokia flip phone was the only one that could do more then 3 feet without issues. My HTC kieser, HTC Shadow, N1 and my current SGS all have issues with my BT headset if the phone is in my pocket on the opposite side of my body from the headset. My old Nokia would let me use the same headset a room away so go figure.
One thing I have noticed is I if I try and transfere a file to any phone(other then the nokia) the file transfere always fails. It works to and from a PC but not to another phone of any kind(except the nokia).... very odd.
my bluetooth has been inconsistantly connecting since I started using 2.2.1 ROMs. it always worked fine previous to that on all the 2.2 ROMs I used.
zaphod_fl said:
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
Click to expand...
Click to collapse
After turning bluetooth off on my phone or turning off my headset once or twice I frequently lose all sounds as well. Glad i'm not the only one.
I have the problem of sound not switching back to the speaker if I turn off either the headset or Bluetooth on the device.
How does Samsung screw something as simple as this up and it not be fixed after 4 official updates?
Nothing about Samsung's top notch screen is worth dealing with the headaches that come with their software. I'm trying to wait for the second generation dual core devices but, if I see good reviews on the Sensation, I am jumping off the Samsung emotional rollercoaster.
Sent from my SGH-T959 using XDA App
I have been back and forth with Samsung over the past 6 days attempting to troubleshoot this.
I have used a Motorola H117 and a Rocket Fish Stereo Headset that I have used with the phone. The following *almost* replicates the sound system crash every time.
1. Turn on Bluetooth headset
2. Press button
3. Voice Dial a contact
4. Phone conversation for 25 - 30 minutes
5. Disconnect phone conversation
6. Bluetooth remains connected for another 20 - 30 minutes
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
I am running STOCK 2.2 KB5 right now. Factory Reset, No root, on the 5th Phone replacement from T-Mobile. I have an open case with 2nd Level support with Samsung however they have given me every excuse from "It's your headset" to "We don't replace phones". I have not asked for a phone replacement and I am earnestly trying to troubleshoot this problem with them.
If anyone has any additional information, please add it to this thread. I have passed the URL for this thread on to Samsung (I do not know if they will bother with hitting it) but I am cross posting at the T-Mobile forums as well as publishing on Twitter.
My only issue is that I have to manually connect bluetooth every time I get in the car. I don't know if this is a problem with my phone or with the bt-fm transmitter our both. otherwise, once I'm connected, music plays great.
Sent from my SGH-T959: Trigger 3.2, Overstock 2.4.1
Basically, my BT has been pm'sing on any 2.2.3 and up ROM.
zaphod_fl said:
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
Click to expand...
Click to collapse
I have the same problem. I found an alternative to rebooting your phone to hear your sound again. Just play a visual voice mail message and hit the speakerphone button in the UI. Your sound will return. You can also play a google voicemail message and hit the speakerphone. It's not a fix but it will keep you rom rebooting your phone several times a day.
I use 2 Bluetooth devices on my phone.
Sony bluetooth headset:
Skips a lot, depending on what I have running. It's worse the more apps I have. To get the best performance, I usually need to end task everything that's running, clear all RAM, then run the music app again. I use the stock music app. I have had better performance out of several ROM's. I think it might be tied to the kernal used, depending on how much space is left (i.e. Bullet's 339mb kernal that I'm using with Simply Honey). Almost like there's a buffer issue.
Kenwood headunit:
I only use the bluetooth connection for handsfree while I'm driving. The only issue I've encountered is that the bluetooth connection is not always automatically restored everytime I get in my truck. If I go into Wireless and Network>Bluetooth, I can get the connection working again. It seems to always be a phone issue, not the headunit.
If you want a beta tester for something, let me know. I use both the headphones and headunit quite frequently.
We just got a '12 Honda Odyssey.
My Sensation works perfectly with the car's bluetooth but the wife's Vibrant is crap for connecting. Very disappointing. Came here hoping rooting her phone and installing CM7 would fix the problem, but that appears to not be the case.
Shame.
No more Samsung phones for us....
I use trigger 8/22 and the Bluetooth works better than ever. Stock gave me head aches
Sent from my SGH-T959 using xda premium
+1 for Vibrant bluetooth problems. I have a garmin nuvi in my car and sometimes it works, sometimes I get the connect-disconnect-connect, and sometimes it doesn't even try to connect.
I've tried stock, bionix 1.2, 1.3.1, and NextGen 2 and only bionix 1.2 seemed to work reliably.
When it works it is fine.
When it does the connect-disconnect-connect thing it sometimes works for phone calls be most often the audio is going through my handset even though the phone claims a BT connection has been made.
Finally in the case where the BT stack is so f'ed up that it doesn't even try to connect it seems like there's some serious battery drain that doesn't show up on the battery stats screen. I suspect the BT is stuck in some kind of loop that causes it to fail and burn lots of power.
The inconsistency is probably the most aggravating part of the whole thing...
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
I have this odd issues related to Bluetooth on my phone. The head unit in my car speaks A2DP. When I turn the car off and the bluetooth disconnects the phone always mutes my media volume. There's a secondary issue where it occasionally takes my phone out of vibrate mode but haven't pinned down how to recreate that one yet.
Had anyone experienced either of these issues and/or know of a fix?
What I'm running:
I recently reflashed my phone to stock 2.3.4 and let it OTA update to 2.3.5. After the OTA I did a full wipe of data/cache with CWM to start from a clean slate.
I do have AutomateIt Pro and specifically have some triggers setup for the cardock (not BT just cardock) but I disabled AutomateIt completely and tested before posting here (this was my 1st thought).
Thanks
Chris
I think that is a feature of Android, like if you were blasting death metal, the next time you use it you wouldn't be blasting it again and be surprised.
I see where it is a pain in the butt. Have you torn through the BT settings?
I have and I can't find anything. Today I discovered that it also does this when I unplug headphones as well. (I don't often use headphones with my phone).
Running Nightly 4.4.2 4/17
1) About 50% of time connecting to any bluetooth device, connection is labelled (no media). I have to disconnect, turn off bluetooth, turn it back on, and reconnect (not sure if all that is necessary, but that's my process). Sometimes I have to do that multiple (up to 6-7 times) to get Connected phone & media. Never had an issue with ShoStock (JB), also had this issue on Render's CM ROM, so assuming this is a KK issue?
2) PacMan, listening to audiobooks (using MortPlayer Audiobooks) in car over bluetooth just fine. Calls comes in over bluetooth just fine. Call ends. Audiobook should resume playing but instead I get (screenshot attached) When this happens, even turning bluetooth off/on doesn't work (bluetooth will say connected but sound will play through phone speaker) - the phone needs to be rebooted.
NePanicPas said:
Running Nightly 4.4.2 4/17
1) About 50% of time connecting to any bluetooth device, connection is labelled (no media). I have to disconnect, turn off bluetooth, turn it back on, and reconnect (not sure if all that is necessary, but that's my process). Sometimes I have to do that multiple (up to 6-7 times) to get Connected phone & media. Never had an issue with ShoStock (JB), also had this issue on Render's CM ROM, so assuming this is a KK issue?
2) PacMan, listening to audiobooks (using MortPlayer Audiobooks) in car over bluetooth just fine. Calls comes in over bluetooth just fine. Call ends. Audiobook should resume playing but instead I get (screenshot attached) When this happens, even turning bluetooth off/on doesn't work (bluetooth will say connected but sound will play through phone speaker) - the phone needs to be rebooted.
Click to expand...
Click to collapse
Correction - this happened again, not listening to any media. Phone idle, received a call, answered it using car's bluetooth. Upon hang-up, bluetooth abended.
Sorry I can't be of any help, as I don't use Bluetooth. Sounds to me like you've diagnosed it pretty well; I would agree it's probably a KK bug. Does it still persist across the newer nightlies?
Maybe it's time to roll back to 4.1.2 - if I remember right even 4.2.2 had BT troubles.
SteveMurphy said:
Sorry I can't be of any help, as I don't use Bluetooth. Sounds to me like you've diagnosed it pretty well; I would agree it's probably a KK bug. Does it still persist across the newer nightlies?
Maybe it's time to roll back to 4.1.2 - if I remember right even 4.2.2 had BT troubles.
Click to expand...
Click to collapse
Tried 5/8 last night and experienced severe audio issues with calls that made my BT troubles pale by comparison. I don't think it's endemic to all KK ROMs as I never had the problem on Render's CM build. Guess I'll try Resurrection. Thanks anyway.
I've been having problems with my car's parrot (mki9100) bluetooth. My Redmi Note 2 seems to pair fine with it, but then it just keeps connecting and disconnecting every few seconds. It doesn't share contacts, it doesn't work for calls and it doesn't work for a2dp. I've disabled permission management but the issue persists. I don't seem to be an isolated case as there are people complaining about this on MIUI's forums. I'm running 6.7.5 from en.miui.com.
I've tried the usual stuff, clearing cache/dalvik, even reinstalling the rom; nothing helped.
Any ideas on how to troubleshoot this?
kritonas said:
I've been having problems with my car's parrot (mki9100) bluetooth. My Redmi Note 2 seems to pair fine with it, but then it just keeps connecting and disconnecting every few seconds. It doesn't share contacts, it doesn't work for calls and it doesn't work for a2dp. I've disabled permission management but the issue persists. I don't seem to be an isolated case as there are people complaining about this on MIUI's forums. I'm running 6.7.5 from en.miui.com.
I've tried the usual stuff, clearing cache/dalvik, even reinstalling the rom; nothing helped.
Any ideas on how to troubleshoot this?
Click to expand...
Click to collapse
I was just about to start a thread myself then I saw your post.
Sadly I'm having trouble too. In my case stereo Bluetooth A2DP is awful. I'm constantly having skips and stutters on both devices I have tested so far (a Samsung HS3000 and a Logitech Boombox). I'm currently using the MIUI dev ROM from September 11th. If you're using MIUI 6 then clearly the problem spans numerous ROMs. Poop.
My problems happen regardless of whether or not I'm doing anything else on the device. It also doesn't seem to matter whether or not WiFi or data are enabled.
As a kind of aside, I also can't get my Moga Pro to connect in Mode A. It appears to pair OK but then just won't connect. Searching around for answers, this also something that at least the MiPad suffers from too (since last year!). Looks like Xiaomi has Bluetooth issues full stop.
I like this device, but some of its quirks of both hardware and software are making it more and more likely to end up on an auction site.
I can't wait for a more stock-like rom to be out.
This might be of help to someone: Someone suggested replacing the bluetooth app from /system/data with an older one (needs root).
I wasn't successful in replacing the app. Instructions here:
http://en.miui.com/thread-122323-3-1.html
kritonas said:
I can't wait for a more stock-like rom to be out.
This might be of help to someone: Someone suggested replacing the bluetooth app from /system/data with an older one (needs root).
I wasn't successful in replacing the app. Instructions here:
http://en.miui.com/thread-122323-3-1.html
Click to expand...
Click to collapse
Thanks for the link.
I tried it too on the developer ROM. It doesn't work (it breaks Bluetooth completely).
A2DP doesn't seem to stutter with music for me after the 17th/18th update. I've only tried a few songs. It's possible that the actual bitrate has decreased though. Apart from the stutters I'm sure it sounded better before. Maybe I'm imagining it.
Briefly tested 6.7.7 and it seems to work! Contacts synced for the first time, A2DP and calls worked. I'll let you know on the audio quality as soon as I have the chance to listen for a longer period of time.