Related
Sometimes I'm in areas where I don't get the best reception (i.e. some lecture halls during school hours) and I choose to put my phone in airplane mode so as to conserve battery when the class is over. However I find after trying to come out of Airplane Mode my Revo always reboots. As far as I can remember this issue has also happened in Decrapped 1.0. The same thing happens when I turn on GPS and choose to go to Google Navigation I get rebooted. After the reboot occurs I can turn on the gps/airplane mode etc without any problems. But does this issue happen to anyone else or is it perhaps just my phone? Thanks!!
I find that my revo does the same thing with google nav beta, it will sometimes hang and reboot too. I am running stock rom with a root. When I rotate phone the landscape view is sometimes corrupted with tiny blocks instead of the maps drawn correctly. I have to exit nav app and reload
I've had the same thing happen with airplane mode. I don't really use it often so I figure I can live with it.
Same here. The Revo doesn't seem to like hardware mode changes at times. I get reboots when switching into Bluetooth occasionally.
[I'm Revolting -- are you? Beamed directly into your brain by Revolt 1.3]
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Cryofalcon said:
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm only adding this due to the fact that I was constantly having issues when tethering with the Verizon 4g Hot Spot app. When running it, I found myself needing to reboot because the data connection would get lost and sometimes go into 3g, causing all sorts of headaches with doing things on my computer, such as redesigning websites, including my own.
What I found, though, related to this post, is using the airplane mode to kill the data connection and restart it, was getting me 4g and a few minutes to a few hours of Internet again until the next glitch.
Overall, modded, ota updated, downgraded, whatever, using that method never rebooted my phone. My thoughts are that it's possible some app might be causing that. I don't use Nav anymore, except as a last resort because it is so buggy, it would cause my phone to crash over and over, and rebooting. So, as for LG or Verizon coming up with a fix for this issue, I don't know if they would see it as one because it's not something everyone is experiencing and with as much as I use(d) that method, it never once happened to me. Please don't take that wrongly, just wanted to point out that it might be a certain app and allow those having this issue to seek another solution, maybe comparing apps installed to see a common denominator.
And, because I see a lot of posts relating to tethering issues with Internet freezing or dropping out, I found, on my LINUX machine (so far), that setting the MTU to 1300 seems to have solved that issue. I know this last part isn't directly related to the original post, but is the reason I kept using the airplane mode method and thought this added information might help someone doing what I was...
-Cybie
Sorry for the bump, but as of flashing Revolt 1.5, the issue in my original post seems to have been corrected as I was able to go from airplane mode to google nav multiple times and didn't reboot at all. so whatever the issue was seems to have been corrected. Thanks MT!!
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.
I don't know what might have happened, but this morning, I tried to connect my Phone to WiFi, and for some reason, it wouldn't. The WiFi toggle button that you see when you pull down the Notification Bar, now that WiFi button keeps turning on and off constantly. The time it takes between each toggle (on to off or off to on) is just about 0.5 - 1 sec. This is crazy. I can't connect to my WiFi.
I googled for solutions, no luck. I hard reset my Phone, no luck still. I wiped Partition Cache too. I entered into the Safe Mode, the same behavior happened. It's weird. It's like my Phone is possessed or something. A virus maybe?
Any input would be much appreciated. My phone is running the latest Firmware from T-mobile. And I got the update maybe 1-2 weeks ago and it had been working fine until this morning the issue started.
My phone just started doing this as well. Wifi keeps turning off and on. If I want to keep it off I have to restart my phone. If I want to use the wifi I have to manually toggle it from the wifi settings. Just weird it started doing this just recently. Maybe an app we both have installed?
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
febzz88 said:
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
Click to expand...
Click to collapse
Haha I was about to post this solution as well! Turning off the wifi in location accuracy fixed it. You're right about probably some Google app is causing this as this hadn't happened before yesterday. Sorry you had to format your phone to find this out...hopefully google or samsung can fix this from their end.
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
I just uninstalled wear and same issue persist. Last app from Google that I did an update on was Google home...formally known as chromecast.
---------- Post added at 10:30 AM ---------- Previous post was at 10:04 AM ----------
I just uninstalled Google home and the issue went away.
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
febzz88 said:
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
Click to expand...
Click to collapse
Yup that was me leaving a comment haha
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
androidschmandroid said:
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
Click to expand...
Click to collapse
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
alanmv567 said:
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
Click to expand...
Click to collapse
no, i do not.
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Go to location>improve location>unchecked wifi scanning. It just worked for me
Uninstalling android wear seems to have worked for me.
febzz88 said:
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Click to expand...
Click to collapse
Definitely not the compass, been through the calibration process. Attempted many fixes including special GPS settings and utilities. At times the phone can sit there with screen on for over 10 minutes without acquiring a single satellite. I'm thinking hardware issue, possibly contacts for the antenna. In any case, not relevant to this thread...
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
DirtySant0 said:
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
Click to expand...
Click to collapse
I had tried this prior to reformatting my phone and it didn't help. I then wiped the cache again and reformatted the phone; in fact I reformatted and cleared cache 3x because the issue kept coming back after I reinstalled apps again. This is weird, the situation and resolution vary a lot from one user to another. Then I simply turned off WiFi Scanning under Improve Accuracy in Location, and the issue went away.
WHEW! Uninstalling Wear and Home did it for me. For now, anyway. I "fixed" it this morning by toggling Ultra Power Saver on and off, and it worked all day until I came home from work. Then nothing helped until I found this thread. Changing GPS settings didn't do it for me, but I'm still on Lollipop so my location settings are a little different.
Thank you, Febzz and Alan!
Google home was the issue!!
Sent from my SM-N910T using Tapatalk
Changes in router's Wireless Security had caused it in my case
This is old thread but still I am posting this solution as it could be useful tip for someone in future.
I had this issue and was causing me real headache. I initially thought it was hardware failure of my phone but later I found reason is something else.
For some reason I had changed Wireless Security of my WiFi router from WPA2 Personal to something else (I guess WEP).
That was causing my phone (intex cloud 4g) often to turn on and off WiFi on its own. I changed the Wireless Security back to WPA2 Personal and phone is now back to normal (not turning WiFi on and off on its own)
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.
Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.
Post deleted
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?
I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.
As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk
I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).
Don't google test their sofware?
This is a poor show by them.
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?
Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?
@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk
I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.
@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once
semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
Thanks
i have x527, when bt is connected i have no ringing sound on smartphone.The same happens and in android 10.Is there any fix for this?
No notification on the bt device?
The phone shouldn't "ring" while on bt.
blackhawk said:
No notification on the bt device?
The phone shouldn't "ring" while on bt.
Click to expand...
Click to collapse
On bt device i have notification,on the phone i see that someone is calling but no sound "ring".I dont have always bt on ears.
jimm1969 said:
On bt device i have notification,on the phone i see that someone is calling but no sound "ring".I dont have always bt on ears.
Click to expand...
Click to collapse
So it's ok with bt turned off?
See if you can modify notifications...
blackhawk said:
So it's ok with bt turned off?
See if you can modify notifications...
Click to expand...
Click to collapse
With bt off all is ok.What exactly in notifications?
jimm1969 said:
With bt off all is ok.What exactly in notifications?
Click to expand...
Click to collapse
Not sure for that... look around.
Probably hidden somewhere.
Try googling it.
blackhawk said:
Not sure for that... look around.
Probably hidden somewhere.
Try googling it.
Click to expand...
Click to collapse
ok.thanks
jimm1969 said:
ok.thanks
Click to expand...
Click to collapse
Sorry I can't be more specific. After over a year I'm still finding "hidden" settings on my 10+.
Just poke around and you usually will find it.
Sometimes I use the pull down notifications to help point me where to look and what's triggering it.
Notifications make simply be misconfigured.
Try clearing the system cache first... that can cure a lot of strange erratic behaviors.
Was it always like that? If not a 3rd party app or an update might have screwed it up.
If so this could be a real pain... as some apps don't do clean uninstalls and leave altered settings that are impossible to conventionally access. I had to reinstall a Google reader I had uninstalled once to fix a display setting it altered. Lucky I realized what had done it.
Most times it's best to track down the root cause. Even though a factory reset may solve the issue, many times it will reoccur.
blackhawk said:
Sorry I can't be more specific. After over a year I'm still finding "hidden" settings on my 10+.
Just poke around and you usually will find it.
Sometimes I use the pull down notifications to help point me where to look and what's triggering it.
Notifications make simply be misconfigured.
Try clearing the system cache first... that can cure a lot of strange erratic behaviors.
Was it always like that? If not a 3rd party app or an update might have screwed it up.
If so this could be a real pain... as some apps don't do clean uninstalls and leave altered settings that are impossible to conventionally access. I had to reinstall a Google reader I had uninstalled once to fix a display setting it altered. Lucky I realized what had done it.
Most times it's best to track down the root cause. Even though a factory reset may solve the issue, many times it will reoccur.
Click to expand...
Click to collapse
I shall try,thanks again.