I recently updated my stock HTC One to 4.3 via the ota update, and I now have some odd occurrences regarding how it syncs up with my car for media playback. I have a 2012 Toyota Camry which has a display that shows me song title, artist, etc. and before the update I had options for enabling random playback and repeat, which are now not there. Also, before if I had shuffle enabled it would advance the track numbers sequentially however now it skips around to random numbers between 1-16 I believe. It doesn't really affect the performance of anything, just my OCD does not like how that works now . For the record, I'm using the stock music player and have not downloaded any 3rd party players (yet, unless that's what is recommended).
Is this something that others experience? I've tried searching and I haven't found anyone with this specific issue (maybe because it's not really worth messing with to most), but it kind of irked me to update and have fewer options than I had before. I'm also curious as to what all needs to be in place for all of the possible information to be displayed in the car, as others have connected random devices and some will not display track information, some will not display where you are in the song, etc. I'm sure a lot has to do with the car, but anything that can be done on the device to make it more compatible with these sorts of things I'd be interested in knowing. Thanks!
Bump, or if there's already a discussion on this that my searching missed just let me know.
Related
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.
So, I just recently got a Samsung Galaxy S3 and I installed the same music application to my phone that I had before (HTC Desire). I never had a problem like this before. My problem is that, while playing music, the GPS interrupts the currently playing song (which is fine), but then there is an EXTRA interruption after this which also causes the song to play at a slight low volume, THEN return to normal volume shortly after. I remember that there was an option to enable/disable volume loudness protection or whatever and I THINK this is the culprit. BUT I CAN'T FIND THIS SETTING ANYMORE!! Does anyone know a solution to this problem? This has been bugging me for FOREVER. I use my GPS often because I often drive to locations I've never been for or barely go to, so this is a REAL pain in the buttocks. -- I also will be using it for the next few days!! :crying: So I would like to fix this, but if there's no fix, I guess I can bare through it for the next few days...
Running Serenity ROM v1.2 with Ktoonsez kernel.
EDIT: Forgot to also mention that this SOMETIMES happens with notifications and such, so I do not think it is the GPS's fault either.
EDIT2: Clarification: Want to get rid of that annoying second interruption that I mentioned earlier!! --I looked in developer options, sound, and EVERYTHING....still couldn't find it...
EDIT3: I searched online and nothing popped up useful (I think I wasn't searching with the right keywords. Kept getting results referring to headset not having any sound at all which is not right.)
I updated my phone to the new Jellybean, and everything works great except for one issue, which is a major one in my case:
I have an '11 Corolla with Bluetooth which has always worked great for me. It worked fine with my phone when it was on ICS. Everything came through the care stereo just fine. With JB, it works with some things, but not with everything like it did before. Phone calls still work fine, the stock music player works fine, and PowerAmp works fine. Problem is, that's the only things that still run through my car audio now. I listen to a lot of audio books on my commute to and from work. The app I have always used for this is Mort Player. Now, all I get when the bluetooth is on is silence. I have found this to be true with every other app I have tried as well. The music player in Motocast doesn't work. Google navigation doesn't work. I've also tried numerous other apps as well like Smart Audio Books, Akimbo, CoPilot, none of them work through the Bluetooth any more.
When I upgraded to JB, the only modifications I had made to the phone was rooting it, and I converted my Power Toggles app to a system app using Titanium so that I can use it as a one-touch switch for my GPS. However, before upgrading, I converted Power Toggles back to a standard app. So other than root, it was completely stock. I haven't found much useful information for this issue, probably because JB isn't widely installed on most RAZR's, but it is a little irritating. I've tried everything, including doing a complete factory reset, but it's always the same.
If I play another app while the stock music player or PowerAmp is playing, then the sound will come through mixed, but not on it's own. Another thing I noticed is that before, my stereo would just display a blank screen when something was playing, or "Pause" if nothing is playing, but now, it displays the name of the song that the stock player or PowerAmp is playing. If you pause it it on the phone, it continues to display the last song played. It only says "Pause" if you press the pause button on the car stereo.
Has anyone else had issues with their bluetooth audio with JB, or know of a fix for this issue?
EDIT: As an added note, I deleted the pairing from my car stereo before doing the factory reset, then re-paired the phone after the reset. Still the same result.
Same sort of issues
Well I could have tried to delve a little deep into this issue, as when ever i tried to pair my phone and send files to my fiance phone it would just not do anything and the issue of showing the same song that was last played shows up in on my sony ericsson blue tooth M600 as well.
But for now i am just complete stuck at the issue that i accidently pressed gsm band selection to USA or the gsm patch. which has caused my phone to just ignore the network completely now network is working.
I would suggest you should try to root and install safe strap 3.11 and then install a leaked jelly bean custom mod it might help but just check the details first and if you are not sure with any of the process let me know before trying. I had my share of issues so I can help you answer those before you try and make a mistake.
For now I am downloading unbrick and will see if i can get this phone to ICS and work again from there.
thanks
From my understanding, once you have upgraded to JB with the leaked OTA, you can't go back to ICS. I'm assuming that is because there has been an update to the bootloader. As a result, I'm hesitant to install any type of bootstrap because I'm not sure if the currently available ones (like Safe Strap) will be an issue and possibly brick my phone.
I'm on Android 9 and I've been trying to use the Youtube app to listen to music as I run deliveries for my business. I'm active on social media in between deliveries so I get frequent notifications, but getting notifications while I'm on the road listening to music is frustrating because the notifications lower my music volume for a second or two and completely throw off my groove! I understand WHY it does this, because as a communication device my phone's intent is to keep me updated on people messaging me, but I'd rather it just play the notification sound WITH the audio instead of trying to MAKE DAMN SURE I heard it.
I don't want to simply turn on Do Not Disturb mode or lower my notification volume as I still want to be able to receive notifications, especially phone calls if my boss rings me, I just want the music to keep playing as I get them.
I've looked through Android's and Youtube's app settings and been unable to find a solid solution to disabling the audio ducking effect, and browsed tons of other forums before coming back here to XDA since I remember having great success with you guys on another much older issue.
I came across an app called Don't Pause! during my searches which apparently solved the audio ducking issue for a lot of people flat-out, but it is no longer on the Play Store and I found an untrustworthy APK download of it that I didn't want to bother with. It's probably too old for Android 9 anyway.
TL;DR Can I get some straight-up solution to disabling the audio ducking effect (either completely, through Android, or locally for just Youtube at least) or an app similar in simple function to the old Don't Pause! app?
Don't Pause ( by XDA-member tpierce89 ) is available here.
jwoegerbauer said:
Don't Pause ( by XDA-member tpierce89 ) is available here.
Click to expand...
Click to collapse
God bless you this is the absolute best solution I could have hoped for. I knew coming here was a great idea. Gonna go one up tpierce's post too!
That app unfortunately doesn't fix the problem with audio ducking. I'm searching for a solution that really disables audio ducking, so that my music doesn't get lowered with every notification and every voice or music feedback of other apps (workout apps etc.).
Any ideas how to really disable audio ducking?
I just want to hear any notification and other audio feedback when I'm listening to music without my music volume getting lowered.
I know we had this issue before, and I don't want to revive old hostilities. I'd like to make this clean and objective discussion.
As you probable know by now, some time ago Google have decided to make android phones play *any* sound to *any* connected BT device, no matter if those devices are capable of playing those sounds or not, and no matter if the users are using (wearing) those devices or not. And this results, for example, in missing text messages, when your head phone is still switched on but you're not wearing it. It also will interrupt your favourite song that you're listening to on your car's radio, with a loud and nasty sound over your car's speaker. And it will also keep you from hearing medical alarm signals if your head phone is in your pocket.
As far as I know, this change in BT behaviour was introduced somewhere between Android 7 and Android 8 (LOS 14 and LOS 15), and as far as my programming knowledge goes, it should be possible to reverse these changes, to make a phone play system sounds over the phone's speaker, while music and calls are still routed to a paired and active BT devices.
So, my questions are these:
What is the big advantage of the present BT behaviour compared to the old behaviour?
How much work or effort would it take for LOS developers to re-code the BT behaviour from LOS 14 back into LOS 17 and above?
If you need help: how can normal people like me with no big development skills help you with this? Would it be a question of money?
How much (in)stability would current and future LOS versions gain through the necessary changes?
Would making these changes be illegal in any way? Would Google sue LOS developers, or would Google send their Men In Black, if LOS developers dared to undo Googles decision?
Although I do not understand the cleverness behind Google's decision, and frankly, no one I talked to about this did understand it, I'd rather make this a discussion about the possibility to undo these BT changes. It would be very obliging to get some useful answers to these questions. Thanks in advance!
Google and LineageOS devs are aware of it and don't see it as an issue:
https://gitlab.com/LineageOS/issues/android/-/issues/950
https://issuetracker.google.com/issues/123758732
https://issuetracker.google.com/issues/125166459
https://issuetracker.google.com/issues/139884122
I can't for the life of me understand why anyone would want it this way. I, for one, see notifications and media audio as separate things that serve different purposes. I regularly pull out my bluetooth earbuds or turn off my bluetooth-linked hi-fi system without remembering to disconnect them at my phone. It's one thing if I go to youtube or play music and can't hear it because of this, but another thing entirely to miss a day's worth of notifications.
A lot of people have been really vocal about this -- just read some of the stories -- but these devs are so sure of themselves that they won't even offer a toggle setting for this. I'm tired of the arguing... LineageOS is free software and I'll patch and build it to suit my needs. But like you, I am not an Android developer, and I don't even know where to start to look for what controls this. I'm sure it's just a couple of lines tucked away in some file, but all I can do is ask, please, for someone out there with greater skills than me to show me what to change!
So I've been digging into the source but it's really above my head... seems like there must be a config file or set of constants somewhere. I'll keep digging and share if I find anything.
Another approach that seems possibly doable is an app that routes the notification sounds through the alarm stream. I have a calendar app that is configured to sound through the alarm stream and that sounds the way I want -- through both the device speakers and any bluetooth or wired headphones.
Sorry about the delay:
htsmi said:
Google and LineageOS devs are aware of it and don't see it as an issue:
https://gitlab.com/LineageOS/issues/android/-/issues/950
https://issuetracker.google.com/issues/123758732
https://issuetracker.google.com/issues/125166459
https://issuetracker.google.com/issues/139884122
Click to expand...
Click to collapse
The answers given by Google's team are living arrogance, a disgrace to themselves and an insult to the users!
Any (good) news on this subject?