I bought one of those Bluetooth Media buttons of ebay. It looks something like this [Attached photo].
It gets recognized as input device and works fine on Android 5.1.
The problem is when it goes to sleep mode, the bluetooth disconnects, and the active application (Youtube, Spotify or GPS) pauses or closes.
I can press Play again, but after 1-2minutes it will stop again...
This is really annoying, is there a way to override this ? My device is rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seems like i found a solution... \o/
I've followed the Tasker steps on this thread.
https://www.xda-developers.com/how-to-disable-bluetooth-automatic-playback-on-any-android-phone/ (How to Disable Bluetooth Automatic Playback on any Android Phone)
I didn't have a problem with automatic playback, but it seems these steps force Tasker to take control of bluetooth devices, so no action is taken on connect/disconnect.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is anyone else STILL getting this? More importantly, has anyone found something to resolve it.
My theory is: it's Jelly Bean..
I was able to pair my phone with the Bluetooth Receiver in my car before (and periodically, it still works..... for about 30 seconds), but I always end up getting this message.
I've tried resetting Bluetooth Share but that didn't work. After searching the web, I've seen that this is a common problem but no one has a consistent solution.
I'm open for suggestions. Thanks.
I was searching for a solution for the same problem.
Until I found someone that's written the following (which's work great with me)...
Steps I took where to put the headset into pairing mode (Hold down call button until red and blue lights flash)
Then go to Bluetooth and search for new devices.
Click on PLT_M50
should pair right up. If prompted for a password try all zeros.
So i've been using NFC Tags to launch car mode when I put my phone in my car's phone cradle, which activates bluetooth and GPS, as well as brings up Google's Car Home App.
Up until recently, it has been working flawlessly. This morning however I noticed that when I click on the X to exit car mode, there is an ongoing notification on my phone telling me that car mode is disabled, and to touch the notification to re-launch it.
The only way to get rid of this is to reboot my phone.
I can't think of anything that I did between last night (used car mode without this problem) and this morning (problem first appeared). Anyone else run into this issue?
Here is a screenshot of the notification:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this isnt a real fix but you could try disabling notifications for the CarMode App
Hi all,
I've a Moto Z Griffin with the latest nightllt installed (14.1+20170905-NIGHTLY-griffin and I've been experiencing a problem with Bluetooth: it just doesn't turn on. If I slide on the right the slider, it stays there but greyed out and where there should be the paired devices I still see "When Bluetooth is turned on, your device can communicate with other nearby Bluetooth devices" (see attachment). If I exit from the Bluetooth page and go back, I see the slider in the off position.
This has been happening since...well, I can't remember, should be 3 or 4 month and I've been using LineageOS on this device for longer and Bluetooth was working properly. I've experienced even on the Samsung S5 with CyanogenMod.
I've tried clearing the cache, adding the line "qcom.bluetooth.soc=smd" or "qcom.bluetooth.soc=rome" to the build.prop file, I've even done a factory reset, but nothing
Has anyone else had this problem and has resolved it?
Thanks,
Andrea
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have same issue on Moto X Force (Kinzie). I will try full revert to stock.
This happens randomly, sometimes even after boot. It's related to android auto mode, do you have any suggestion to prevent it?
More details, please. What do you mean it's related to Android Auto mode? I use Android Auto extensively and I don't have this problem at all.
Do you have a DnD schedule set for Driving? If so, delete it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine does this...
I only have these two modes set
Sleep is from 23:30 until 07:30 and entirely muted bedtime is from 23:00 until 08:00 and mostly muted
I also have driving mode when moving only
I think there's something wrong with the driving mode that causes it to turn on at random. Possible is from jumping location if can't get a GPS lock (I have: always-on WiFi scanning disabled)
Cheers all
Hi all,
I've got an issue I haven't seen anyone else posting about for this phone.
I have YouTube music and whenever I hop in the car and my phone connects to my head unit over Bluetooth, it automatically starts music playback.
I've turned off the relevant options for both YouTube music and android auto (which my head unit doesn't support anyway) and still it does this.
Anyone have any ideas or experiencing the same? It drives me nuts. I don't want my music to autoplay when it connects to my car.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That’s not device’s problem, that’s app problem. You should able to setting in app
Mr-Zhag said:
That’s not device’s problem, that’s app problem. You should able to setting in app
Click to expand...
Click to collapse
I provided screenshots and explained that those settings have already been adjusted in the app. That's why I made this post to reach out for further ideas.