Related
Hi, everyone.
tl;dr: Phone calls kill the music player (presumably due to low memory), although the navigation keeps going. How can I stop it killing the music?
Bit of background.
I have a Milestone currently running CM7. I like Android 2.3, and I'd like to keep it if possible, but I would consider switching to any ROM that supports 2G/3G switching in Tasker (which means no stock ROMs) if it'll solve this problem.
I use my phone to provide music in my car because I use it almost constantly for navigation. I have a Tasker profile set up so that when I plug something into the headphone socket (including, for example, my tape deck adapter because I'm too poor to get a proper car dock) the phone asks if I want to go to car mode. On selecting this, it switches to 3G only (so as not to interfere with the speakers), turns off wifi, fires up GPS and starts Car Home, as well as activating some auto-respond and reading aloud profiles to deal with SMS. From there I normally hit Navigate and then get some music up either in the default player or Spotify.
So I was trying this out yesterday. Since updating to CM7 my phone seems to be able to more reliably keep music playing, whereas it'd often close the music app at the end of a song with CM6 (Spotify, oddly, was more reliable). Good. Until I get a phone call, at which point it kills the music player entirely, although the navigation does come back at the end of the call.
This makes sense. The call is more important than the navigation which is more important than the music so it kills the music. Thing is, I'd like to keep all three going. I hate driving without music and leaning over to fiddle with my phone while driving is going to get me killed one day.
I've used zeppelinrox's guide to supercharge my phone and I'm running with Auto Memory Manager at 6, 8, 24, 26, 28 and 30. I haven't bulletproofed the launcher... yet. Thing is I'd be happy for the launcher to die while I'm in my car so I'm not sure I want to do that. It's also running overclocked to 900MHz max on the interactive governor (or was, I've just this minute switched it to smartass but I doubt that matters).
My phone, incidentally, is doing nothing in particular right now and has 44MB free (I have a bunch of home screen widgets but I don't think I'm being excessive).
That's not a lot, it's probably not enough to run a music player, navigation and a phone call. I get that. But a phone with 256MB total RAM should be able to handle those three tasks simultaneously.
Here's what it does in my car that I care about (in priority order):
Taking calls.
Navigation.
Music (either the Android app or Spotify).
Tasker (sitting on my "in car" profile but not actively doing things unless I receive an SMS in which case it auto-replies).
Receiving text messages.
Car home.
Receiving emails.
Here's what I think it's doing that I don't care about:
Syncing Facebook/Twitter.
Software updates.
Home screen widgets.
Whatever else Android does when it's idle.
I've just had the notion while typing this that having Tasker disable sync while in the car might be a good move (to stop emails, Facebook and Twitter). This might free up extra memory. I don't know enough about Android to be sure of this, but I could give it a try. I'd rather not have to though because emails are sometimes important enough to pull over and deal with, or at least have my passenger read out. Facebook and Twitter aren't, obviously.
Any other tips? Would it be possible to build a script in Tasker to raise the priority of things I commonly use in my car and drop the priority of everything else? I'd also like to bulletproof my launcher while in normal use but not so much while I'm in the car.
Thanks.
First a workaround.
You can add a short cut to the music player in Car Home (the google car home you can, anyway)
So at least you have a big easy button to hit to run it.
You can also try and bulletproof the app with a gscript.
Yep, got the music apps in Car Home. I like the Google one, the Motorola one is useless.
I don't know how I missed that thread but I shall give it a go. Cheers.
It's hit and miss but apparently it works pretty good for the music app
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
gakio12 said:
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
Click to expand...
Click to collapse
On the new moto x? No, I just had a couple hour car ride with zero issues listening to Play Music and Slacker Radio. Made a few calls, no issues either.
This happened to me on a 20 mile bike ride. Horrible having choppy audio for almost a few hours
I just noticed this too. I do have a Moto 360 as well so maybe that is messing with the blueooth? I have gone a couple car rides and it's perfect, and others it's really choppy.
This does seem to be a problem with me too. Sometimes perfect and sometimes not. When connected to Bluetooth I notice that Google maps speaker goes in and out as well as moto voice while driving
I can confirm that if you have a 360 this is the cause. You can verify this by disconnecting the 360 through wear and the problem going away. For now what I have due is set up an IFTT to disconnect wear when by car's Bluetooth is connected.
I actually don't have anything else connected via Bluetooth and it still happens to me.
I figured it out. I was driving and I turned off Bluetooth completely and the voice worked perfectly. As soon as I connected back to Bluetooth the voice got choppy again...
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
I'm experiencing the same issue, really sucks.... I'll try disconnecting the Moto360 on my drive today and see if that fixes it - although I swear I've had the issue before while it wasn't connected.
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
SetCPU could possibly do this. You can definitely set the minimum CPU clock, but I'm not a 100% whether you can get it to do this WHEN a bluetooth device is connected. SetCPU has a profiles where you can define certain parameters based on conditions.
Of course, before you can get SetCPU working you'll need to root your phone and I have a suspicion that all other CPU clock apps will need root access too.
Has anyone had any luck resolving this?
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
I'm hoping that either an OTA or Android L will fix this. My Moto X is fine when I'm using my Motorola S11-HD headset, but when connected to my car it goes in and out every few seconds.
So it isn't the processor. So far i have it down to either Wi-Fi or active display. Will report more when i find it.
Turning Wi-Fi off while connected to my car Bluetooth has fixed the issue for me. At least, so far it has.
I'm using PowerAMP for playing music and when I enabled the "high priority" setting in the headphone/bluetooth settings it seems to have resolved the problem until today. This morning on the way from work it started to cut out every few seconds. grrrr...
I have 2 bluetooth adapters in my car, one which takes only phone audio and one which takes phone and media audio, the latter one continously drops and reconnects phone audio (even after forgetting the other device), which makes me believe it is some hardware compatibility issue
I have posted on the official Motorola Forums but I though I should re-post here as well becuase well....XDA fixes things.
So I just purchased a Moto X 2nd Gen Pure Edition as an upgrade to My 1st Gen Moto G. Both phones have the same problem with the Bluetooth Audio sounding like a scratched CD skipping and studdering and it seems to be way worse a problem on the Moto X than I ever had on the Moto G. It's not buffering it happens with music on the phone. It doesn't happen every time I'm in the car but I'd say 50% of the time.
I would think it's the car but before the Moto G I owned a Galaxy Nexus and never had the problem as far as I remember. I'm sure I would remember it's really really annoying. I have even tested with a friends HTC M8 over a long road trip and there seemed to be no issue there. In my car (2011 Subaru Impreza) with the G or X after a time it eventually starts skipping even if it takes a couple hours.
So I did some research before and have tried various things.
I have disabled the Wifi while connecting to BT as Motorola has recommended to owners of other phones. That didn't help them it doesn't help me.
I have removed all other BT devices from the phone while connected. Nope
I have removed the Phone in the profile so my car doesn't try to use it as a phone as well at the same time. Nothing
I have done all of the above at the same time stopped every other program other than Google Music and added the phone to my car fresh and I still have this issue.
During my research about my car the only complaints similar I found seem to come from someone else with Moto phones. I dont' know what they do special with their Bluetooth but it's not helping me out.
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
godutch said:
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
Click to expand...
Click to collapse
This is what fixed the audio in my Mustang with Sync. The Ford dealership did not charge me anything for them to do it.
Sent from my XT1095 using Tapatalk
The day I got my pure edition it got the update for lollipop, so I don't know if this happened in KitKat. When I stream music over Bluetooth and the moto active display kicks in, the music pauses for a split second. Kind of makes it useless for streaming. Anyone else? Stock, unrooted, locked boot loader
I have the same issue, didn't connect it to the active display tho. Works better after a recent reboot, but still will skip occasionally. I have noticed that it seems to be Google Play music that has the issue. Pocket casts hardly ever skips.
enochpc said:
I have the same issue, didn't connect it to the active display tho. Works better after a recent reboot, but still will skip occasionally. I have noticed that it seems to be Google Play music that has the issue. Pocket casts hardly ever skips.
Click to expand...
Click to collapse
i'm surprised no one else has noticed this. it happens with me on spotify.. its terrible in the car
I use Google play all access with the BT in my car with Dodge's Uconnect (2012 MY) and the only time I get skipping or stuttering with the music is if I connect, walk far enough away to loose connection while streaming music and then walk back in range. Like if I forgot something in the house. If I get a notification, the music volume will go down, but then I hear the notification though the speakers.
This is on a PE with 5.0
Interesting... I've used bluetooth to stream Google Music and Soundcloud a lot in my car, and I haven't noticed this issue (I'm really nit-picky on this stuff, so I'm not sure I would have missed it).
I'm also on Lollipop, updated back when I got my pure edition around new years.
I'm looking forward to 5.02 or 5.1, which ever we get next, as I have several annoying bugs (including bluetooth) that I hope are addressed. I am currently stock, 5.0, but am seriously ready to try cm12 now that they have bluetooth ironed out. Still love the active display tho, even tho it randomly goes off or won't work for no apparent reason.
Lot's of manual reboots on my phone, at least compared to my old M7, if it wasn't for the camera I would still have that phone.
I've only noticed skipping using Pandora. Google play music doesn't skip.
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
Hello everybody,
First of all : Happy new year !
I own a Pixel 4 XL running a stock ROM with the bootloader still locked (I actually don't flash my phones anymore since I'm a team Pixel member haha). I use Android Auto very often because of my job.
Here is my problem : Since the december update (I guess) when I disconnect my phone from my car (using the cable & bluetooth), and put my phone in my pocket, the song from the last music suddenly runs very loud (max volume) even if I manually stop the music player beforehand. I tried a lot of things to stop this problem that seems very random : I cleared the YT Music cache, I disabled motion sense gestures, I even did a factory reset but the problem is still here.
I have to think every time I get out of my car to low the volume before this bug comes out..
Have you encountered that problem ? Do you guys have any idea that could help me ?
Thanks in advance !
Nobody can help me ?
I don't know, what does team Pixel say?
I don't think there is a solution and you aren't alone. I don't use YT for audio, but all music apps have the same pain in the ass behavior because they don't close automatically and most often you have to use "recents" to kill them off. This is the same with Spotify and Pandora. I find myself having to close AA itself sometimes because it stays open long after I've left the car. Sometimes 20 minutes later I look down and notice it is still running. If it can start up automatically when BT connects, or even when "hearing" driving noises like the engine, the reverse should be true. You turn the car off, unplug, exit the vehicle WHY does it continue running? Not one of the top 3 music apps will kill itself.
Thanks for answering !
I actually didn't know anyone else would have the same problem so this is reassuring me hah
Yes that is so annoying having your phone waking up with music with the volume toaximum whereas 10 minutes ago you thought you did everything to shut it up
I think I've had this happen literally once and I do use YouTube Music. Have never had it replicated. Is it still happening with the happened with the January update?
EeZeEpEe said:
I think I've had this happen literally once and I do use YouTube Music. Have never had it replicated. Is it still happening with the happened with the January update?
Click to expand...
Click to collapse
Unfortunately, yes it still happens despite the last update. The only thing that seems help me avoiding the problem is when I manually stop the music in my car before unplugging the phone. Then, for safety I put the media volume to the minimum so if the music starts again in my pocket, I won't hear it.
!J2B! said:
Unfortunately, yes it still happens despite the last update. The only thing that seems help me avoiding the problem is when I manually stop the music in my car before unplugging the phone. Then, for safety I put the media volume to the minimum so if the music starts again in my pocket, I won't hear it.
Click to expand...
Click to collapse
Interesting, so you're connected via Bluetooth to your car, turn off the ignition, and it'll still be playing? At that point, that's when my YouTube Music pauses.
EeZeEpEe said:
Interesting, so you're connected via Bluetooth to your car, turn off the ignition, and it'll still be playing? At that point, that's when my YouTube Music pauses.
Click to expand...
Click to collapse
Actually no. I plug my P4XL to my car through USB then it connects via Bluetooth and Android Auto runs on my car's screen. Everything work fine. When I'm arrived, I unplug my phone, turn of the ignition and the sound normally stops and YTM pauses. But something like 10 minutes later, when I'm far from the car, the last song I was playing in the car restart through the phone with absolutely no interaction on it.
!J2B! said:
Actually no. I plug my P4XL to my car through USB then it connects via Bluetooth and Android Auto runs on my car's screen. Everything work fine. When I'm arrived, I unplug my phone, turn of the ignition and the sound normally stops and YTM pauses. But something like 10 minutes later, when I'm far from the car, the last song I was playing in the car restart through the phone with absolutely no interaction on it.
Click to expand...
Click to collapse
Ah okay. Thanks for the clarification. Yeah I use Android Auto just on my phone.
!J2B! said:
Thanks for answering !
I actually didn't know anyone else would have the same problem so this is reassuring me hah
Yes that is so annoying having your phone waking up with music with the volume toaximum whereas 10 minutes ago you thought you did everything to shut it up
Click to expand...
Click to collapse
I have a similar problem. I drive a lot throughout the day and Stream SiriusXM on my Phone through the BT on my work van. Very often, I get out and within an unspecified period of time, Sirius will start playing, full volume for no reason. It's as annoying as the Google Assistant suddenly responding to something I said without me using the OK Google prompt.
The fix is to close Sirius and swipe away the player controls in the status bar dropdown
HipKat said:
I have a similar problem. I drive a lot throughout the day and Stream SiriusXM on my Phone through the BT on my work van. Very often, I get out and within an unspecified period of time, Sirius will start playing, full volume for no reason. It's as annoying as the Google Assistant suddenly responding to something I said without me using the OK Google prompt.
The fix is to close Sirius and swipe away the player controls in the status bar dropdown
Click to expand...
Click to collapse
Thanks for your feedback ! I don't have the Google Assistant problem you have but the exact same problem for the media. So it's not due to YT Music or Sirius. It's an overall media problem.
Unfortunately, I can't close the app because when I unplug the phone, YouTube Music isn't even open. And swiping right the player controls doesn't seem to work.
The only thing that seems to work is to stop the stream through Android Auto before turning off the engine and unplugging. But I have to think every time I leave my car
!J2B! said:
Thanks for your feedback ! I don't have the Google Assistant problem you have but the exact same problem for the media. So it's not due to YT Music or Sirius. It's an overall media problem.
Unfortunately, I can't close the app because when I unplug the phone, YouTube Music isn't even open. And swiping right the player controls doesn't seem to work.
The only thing that seems to work is to stop the stream through Android Auto before turning off the engine and unplugging. But I have to think every time I leave my car
Click to expand...
Click to collapse
I haven't tried stopping it before I turn off the van, but that's an idea. I think when I turn off the engine, it pauses the stream on the device, sure, but what causes it to just start playing again??
TBH, that and the random dead spots around the edges of my phone since Android 11, I'm getting a little aggravated.
HipKat said:
I haven't tried stopping it before I turn off the van, but that's an idea. I think when I turn off the engine, it pauses the stream on the device, sure, but what causes it to just start playing again??
TBH, that and the random dead spots around the edges of my phone since Android 11, I'm getting a little aggravated.
Click to expand...
Click to collapse
I absolutely don't know what causes it to start the music again. But closing it before turning off the engine and then force closing the streaming app does help. That way, the phone has nothing to turn back on
Regarding the dead spots since the update I don't have this problem... Yet. But yeah, Android 11 is one of the worst major update the past few years. Hope they will fix these problems soon.
IsaacDavidson said:
Have you tried to write them in customer support? I think that it is a system bug
Click to expand...
Click to collapse
Yes I already tried but the support didn't even seem to understand the real problem. We were speaking in my native language though. Seems like french support sucks