Hello,
I am having a problem where Touchwiz crashes after about half an hour to an hour of listening to Bluetooth audio through my car stereo.
The problem does not occur with the stock music player (or hasn't yet in the timeframes I've been testing it). However it occurs with pretty much any other player I've tried (thus far PlayerPro, Poweramp, and Audible). The symptoms are pretty much always the same. Audio works perfectly for quite a while, then it stops, phone kind of freezes for a couple of seconds, then Touchwiz resets. Often after it restarts I have trouble either connecting to or playing audio through Bluetooth. Sometimes that fixes itself, sometimes I have to do a full reboot.
I have had the device replaced in case it was a Bluetooth hardware issue but I'm having the same issue on the new handset. So far the issue is 100% reproducible.
It's an unrooted, stock phone running IMM76D.I9300XXALF2. I'm on Three UK. At this stage I am not planning to root the device. However if there was a clear reason why doing so might fix this issue then I might.
Has anyone experienced this issue?
If someone has time to have a look, I have managed to record an ADB log from the crash. I believe the crash happens at 20:29:36 - based on there being a lot of information about a Fatal Signal 11 at that point (although I did think that was just related to specific apps crashing), and then all the services die very soon after.
At some point, I will try with another Bluetooth stereo to see if it's specific to my current one. But I don't have any available, so was hoping someone might be able to help narrow things down in the meantime.
I've also gone to Samsung with the issue, and sent them the log, but who knows if they'll ever get back with anything useful.
Touchwiz crash with Bluetooth
Hi.
I have the same problem with an S2 LTE (not S3) from Rogers in Canada and a JVC radio except mine crashes after 30 minutes. It worked fine before upgrading from 2.3 to 4.0.4.
Model SGH-I727R
Version 4.0.4
Baseband version: I727RUXLF3
Kernel 3.0.8-perf-I727RUXLF3-CL611724 [email protected] #1. Compiled Sat Jun 9, 21:24:26 KST 2012
Build number: IMM76D.RUXLF3
When playing a podcast (BeyondPod) or audiobook (Audible) for 30 minutes, the phone freezes and a few seconds later the screen locks and all the status icons disappear. They all come back as if the phone just booted but it's not the long boot you would get if you powered off and on so it must be Touchwiz crashing. I also see a notice saying it's safe to remove my SDCard and then it re-mounts.
For me it is 30 minutes +/- 1 minute and it's consistent. If I shut off Bluetooth and immediately turn it back on after 25 minutes, I will have another 30 minutes without any problems.
I tried manually unmounting the SDCard while streaming over Bluetooth and it gracefully shut down the application and unmounted the card without any issues.
Others have had this issue too. Google for 'Issue 28006: ICS Bluetooth and Sony car headset'
I contacted Samsung support but so far they haven't helped. Their first response was to take it back to the carrier.
Have you find a solution for this? If not can you submit a support request with Samsung? If they get enough reports maybe they'll do something.
richjhart said:
Hello,
I am having a problem where Touchwiz crashes after about half an hour to an hour of listening to Bluetooth audio through my car stereo.
The problem does not occur with the stock music player (or hasn't yet in the timeframes I've been testing it). However it occurs with pretty much any other player I've tried (thus far PlayerPro, Poweramp, and Audible). The symptoms are pretty much always the same. Audio works perfectly for quite a while, then it stops, phone kind of freezes for a couple of seconds, then Touchwiz resets. Often after it restarts I have trouble either connecting to or playing audio through Bluetooth. Sometimes that fixes itself, sometimes I have to do a full reboot.
I have had the device replaced in case it was a Bluetooth hardware issue but I'm having the same issue on the new handset. So far the issue is 100% reproducible.
It's an unrooted, stock phone running IMM76D.I9300XXALF2. I'm on Three UK. At this stage I am not planning to root the device. However if there was a clear reason why doing so might fix this issue then I might.
Has anyone experienced this issue?
If someone has time to have a look, I have managed to record an ADB log from the crash. I believe the crash happens at 20:29:36 - based on there being a lot of information about a Fatal Signal 11 at that point (although I did think that was just related to specific apps crashing), and then all the services die very soon after.
At some point, I will try with another Bluetooth stereo to see if it's specific to my current one. But I don't have any available, so was hoping someone might be able to help narrow things down in the meantime.
I've also gone to Samsung with the issue, and sent them the log, but who knows if they'll ever get back with anything useful.
Click to expand...
Click to collapse
That's quite interesting. Mine is also a JVC stereo so I wonder if that's related. Mine could be exactly 30 minutes - I've not actually checked that. I will next time.
Out of interest, have you used PowerAmp before? The log I attached is from using PowerAmp, but since a recent update it actually seems to be fixed in that! But it still happens in Audible and other audio apps. I'd be interested to see if it works for you as well.
Samsung haven't been particularly helpful, other than saying they will look at the ADB log and release an update (for the SIII) if "it turns out to be a real issue" (which annoyed be, because it obviously is a real issue).
The Audible developers on the other hand are very interested and I have provided them quite a bit of info on the problem. I will pass them this thread too. I should try out the shutting off Bluetooth thing as a work around. Surprised I hadn't until now.
I haven't used PowerAmp but I did try the stock Android music player and it also crashed. I played a one hour podcast and after around 35 minutes it crashed as usual. At first I thought it was going to keep working as it's usually right around 30 minutes but it did eventually crash.
Did you report the problem to the PowerAmp author or was it just luck that the new version had a fix for it?
Samsung sent me an RMA shipping label. I have no plans on sending back my device for a software bug only to get back someone else's defective/fixed unit back with the same bug.
If this really is a bug in Touchwiz on ICS then we should ask others to test it in a general forum. I don't think this happens when playing music, only when playing one stream over 30 minutes. We need to find more people with a Samsung, ICS and bluetooth receiver to test..
That's very interesting information. I will try a single audio stream on the stock player and power amp. But it does happen for me with multiple streams in other apps (PlayerPro for example), but it could be related to how it plays them - perhaps it combines them into a single stream.
In fact, thinking about it, it could well be that. I don't think the previous version of PowerAmp showed the song title over Bluetooth, so it may have just combined multiple songs into a single stream as far as the Bluetooth stack was concerned. But now it does, so that might break the stream each song.
And I had not informed them about it, it was just luck. And they haven't responded to my queries regarding what they changed (which of course, may not matter).
I have already replaced mine (through Amazon), and of course the problem didn't change at all. Meaning it's the software (and perhaps the specific Bluetooth devices), not the individual phone.
I am going to test mine with a different Bluetooth receiver at some point, and might also get other people to try their phone with my stereo. According to the person I've been in contact with at Audible, it is only affecting Verizon customers in the US (that they know of), and haven't been able to reproduce it themselves.
Related
[Q] How to make the stock music player work "properly" with car bluetooth...
My main issue with the stock music player is that when the car shuts off, the player should pause the music. Instead, it resumes playing but over the phone's external speaker.
-Samsung Galaxy S2 international model, bone stock (no root), latest available firmware through Kies.
Just giving this one final bump. I can't be the only person who uses this phone for music
i dont have this problem... as soon as i turn off my car the music player pauses... actually even when im listening to podcast on dog catcher it pauses when i turn of the car. im using 2.3.5 flashed to villainrom 3.0
try updating the firmware
willfred2011 said:
try updating the firmware
Click to expand...
Click to collapse
Thanks for the suggestion, but I am on the latest official firmware.
try a different rom then... it depends how much does this issue bug you? a solution has been offered with Villain ROM, but now you have to decided if you want to root your device to fix it or not?
bunnybash said:
try a different rom then... it depends how much does this issue bug you? a solution has been offered with Villain ROM, but now you have to decided if you want to root your device to fix it or not?
Click to expand...
Click to collapse
Appreciate the help. Was looking more for the "hey idiot, you missed this setting" from someone else who may have experienced this. I've installed Google Music, which seems to be working fine. If TW Music starts to annoy me by popping up, I'll root and freeze it.
After trying various software combinations, I'm starting to believe that this was a hardware issue. The phone seems to think that a headset is being plugged in and unplugged rapidly when I disconnect Bluetooth. I can't find anyone else with a similar issue. I decided to return the phone.
Since it was a Latin America model from Amazon, I decided to instead purchase the UK model from Expansys. Same price, but also a $20 coupon code to help reduce the cost. Expansys also gives me the full 2-year warranty, and Amex gives me a third year on it. I can refund my Squaretrade warranty if I so choose, so this saves me even more money.
Just received my new SGS2. This one's from the UK (last one was Latin America). Seems to have a slightly newer Samsung build, but is still 2.3.4. However, still experiencing the same issues with Bluetooth audio. Sometimes the music stops when I disconnect, other times it resumes over the phone's speaker. Yet other times still it seems like the phone is in a fight with itself where it will pause, then resume, and sometimes go back and forth a few times. When this occurs, the music will be playing but the music player will have the play button up as if it's pause (so I'll have to hit it twice to actually pause the music).
Currently on latest available UK unlocked firmware, stock music player, although I have observed this occurring with ANY music player that I install. Just wanted to see if anyone else is experiencing this and if so, what solution(s) you may have come up with.
Thankfully, 2.3.5 is right around the corner for UK unlocked, and I'm hopeful that it will address this.
I havent seem to run in to anyone with this issue.
I pair my phone to my car stereo fine in the stock GB rom. Play music and talk on the phone endlessly.
But with any ICS version so far, even official. It causes reboots, randomly.
Am I the only one suffering from this?
Not the same, but something similar.
I can connect with my car stereo, have to do it twice (once for music streaming and once for handsfree). Once connected, i can stream music fine. Even the controls on my steering wheel work. When I receive a phone call sound is muted and i can talk fine as well.
After I hang up the phone, the music doesn't come back, only a 0.5 second stutter every 2-3 seconds. On my phone, in the music player I can see that it's my phone that has the problem; the visualisation displays exactly how i hear the sound.
This behaviour also occurs when I turn off my car and turn it on again.. there doesn't seem to be a single thing that i can do to get music to play again, just some fiddling usually gets it to work (but then i have to stop my car first before i can have music..)
If anyone has any ideas for troubleshooting let me know!
I honestly think ics has compatibility issues with certain bluetooth devices.
We can only hope they realize this and take measures to correct it.
Gingerbread is flawless.
Sent from my GT-I9100 using XDA
Just a notice that this seems fixed for me now.
I've upgraded to the 4.0.4 Rom found here: Click!
Next to this i'm using the app "doubleTwist"
ICS talks a different language then gingerbread when it comes to A2DP, especially for the play/pause commands, which seem important to me..
A2DP issues
I find I have similar issue. I have a SONY bluetooth deck in my car and my phone will lock up and force restart mid song or mid phone call.
Anyone have any ideas apart from flashing that 4.0.4 Rom
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'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.
Hi,
Whenever my phone connects to my car's bluetooth, it will automatically start playing the last media I played. The problem, is that I will go DAYS without ever using media on my phone so I will resume a podcast from last week despite the fact that the podcast app is closed. I notice that even when I force stop the app, I can go into the Menu, go to Media, and still see it sitting there with no way to close it. Also, if I pause the media...after a while my car will disconnect from the bluetooth and then reconnect...which then resumes the media again. Oh, and if I get a notification about something like an email...you guessed it, the media will resume again. This is beyond frustrating because I often like to go on quiet car rides...and again this happens even when I force close the app (podcast, spotify, whatever).
This was also an issue with my S10, but not my Pixels. This has to be a OneUI or Galaxy specific issue. I have seen mentions of this bt/media issue in other boards when searching but the only thing I have seen to semi fix the problem is by setting up Tasker.
I'm wondering if anyone else has this issue and has resolved it. I am also wondering if there is a way to switch to a vanilla android os ROM so I don't have to use OneUI anymore. To clarify, I have been using Nova, but that doesn't change how the phone handles media.
Thank you for your help.