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.
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 have had a few issues with my note 2 of late but these are now resolved. Basically everything is working fine and correct except bluetooth. I was running stock 4.3 and the bluetooth would note turn on, it flicks to on, then about a second later turns off.
I could get no where with this, so I rooted my device, this made no difference, then install CM10.2, again no difference, tried, CM11 also no difference.
So after alot of search there are a few forums explaining this issue but none with a real answer.
I decided I would run Terminal and enable bluetooth that way. But I got this as a reply. Can anyway please tell me what this means and what I then need to do.
It looks to be a permission issue from what I understand.
I ran this in terminal
su
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
Here is the response:
{
"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 the T-mobile One M8, and I'm using it on MetroPCS. The phone worked great until I sent it to HTC to get the screen replaced. After receiving the replacement, the location cannot "fix", so apps like google maps or waze just sit at "waiting for location" indefinitely. I tried some different GPS testing apps and it seems like the phone is finding between 12-24 satellites but not connecting to them. (screenshot attached)
So far Ive:
Reset the phone
Toggled: GPS, airplane mode, wifi, mobile data, high/device only location modes.
I even sent it back to HTC and it came back with the same problem.
Android Version
5.0.1
HTC Sense Version
6.0
Software Number
4.20.531.4
Any ideas before I loose the phone for another two weeks returning it to HTC.
{
"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"
}
Hi.
Since updating my Sony XPERIA Z5 Premium to Android 7.0 about a month ago, I've not been able to read any NFC tags that I was previously able to read. After dialling *#*#7378423#*#* and running the NFC diagnostics, I was presented with the following:
{
"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've tried scanning my bus pass but that doesn't do anything (it used to at least show at toast on my device).
Any ideas?
I got the same problem. version: 32.3.A.2.33.
I got the same problem, too.
version: 32.3.A.2.33, too.
Hi i have the same diag test, however I van use my NFC features but by pressing them well enough on other devices or tags also on my headphones. Kinda frustrating since the "one tap" features of it kinda turn to to "hard press". This happen after I repair my phone on Xperia companion on pc.