Related
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
paulgildea said:
Okay folks, I wonder if anyone out there can help... My One is randomly vibrating once, with no notification, and I can't figure out why.
Other threads point to similar issues but not the same problem I have. I've been troubleshooting a lot, but can't narrow it down much. What I know so far:
Appears random. Not a particular time, battery level etc
No notifications appear in the bar. It can happen even when I'm looking at the phone and there is no visual indicator.
I have a Pebble watch, so most notifications can and do come through to the watch - no notifications on it when the vibrate happens.
It also doesn't seem to be any kind of dropped Bluetooth connection with my Pebble, as the Pebble doesn't notify of a lost connection like it normally would.
I have also read threads for other HTC phones where it pointed to nfc being switched on. While I do usually leave NFC on, the vibrate still happens even when I disabled NFC
.
I was holding off until Vodafone decide to release the Sense 6 update, but I'm not holding my breath there...
Is there anything that I could investigate? I was trying to avoid rooting or modding the phone for as long possible, but would be prepared to do it. However, I don't really fancy going down that road if the problem will still be there.
Suggestions appreciated!
Click to expand...
Click to collapse
If your phone is not modified in any way, the best thing to do is take it to service
Can't think of a good sig
I rooted my Samsung Galaxy S5 Mini G800F yesterday using Odin method. It rooted without any problems & everything seemed fine. I switched off my phone overnight & this morning I turned it on & while it was loading up I left the room for about 10 mins, And I heard this what I thought was a passing Police car, then I come back to my room & you can imagine my shock when I realize it's coming from my phone! Funny thing was that I don't know where it came from,no indicators/notifs of where it was from or which app,I checked some apps but it was not any of them. There was nothing I could do to stop it,only turn down the volume. Then Thank God after a while it ceased.
Think has never happened before,only happening after I rooted yesterday. I know it don't seem bad as I make it but this is not OK! What on earth have I done to my beautiful phone?
Anyone have any ideas about this & what's going on? Could it be some virus or malware as a result of the root? I dunno please please help.
Hey, have you got any third party mail apps such as yahoo as it might be a notification problem. It sounds like an anti theft software was triggered but I'm sure it shouldn't have. Type *#0*# into your dialer and test the low frequencies if you have anymore problems. I have no idea why but I was told it helps.
SilSien
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
Well ,it has happened before but I didn't want to exaggerate it ,so I left it just as it was until today .It's completely stock ,with custom recovery .It has happened to me since 5.0 and up until now 5.1 .
It doesn't happen always ,just "occasionally" when there is an incoming call ,Nexus 6 turns off itself .It happened now that I didn't even hear that it rang ,it just turned off ,but I know that my dad called me .
Has anyone ever experienced such issue ,is there a fix ?
To mention that it also gives an odd sound befire turning off :/
Same thing happening for me also with Nexus 6
And this keeps happening more frequently over recent months. This also happens when battery is below 30% and I am taking HDR+ photo. Maybe related to aging battery and apps getting more and more power hungry..?
@pauliusz: First, kudos for actually searching for a thread related to your problem. Too many don't bother. Second, replace your battery, as the shutdowns are in fact a direct result of the battery's age.
My Nexus 6 keeps forgetting my Bluetooth pairs. I'll wake up and notice that my pairs are gone. Which is an annoyance with my car and Android Wear watch. It happened once before but then when it happened last night I know there is an issue. It started after I upgraded to Marshmallow. I'm running the MRA58R build. Any ideas?
I have the same issue...ever since marshmallow...both 6.0.0 official and 6.0.1 official, both times before installs the phone was wiped...but never the less it always forgets my bluetooth pairs
it seems to correlate to when the phone fully dies. If the phone fully dies 1-2 out of 5 times it will boot back up without the bluetooth pairings.
Also if I don't pair my Wear watch(original 360) this does not seem to happen either
I'm having this issue as well. My phone will randomly ask to pair with my car, even though it's been paired already. And sometimes it will just ask me to allow it to share Messaging, which was also already set. It's frustrating. I've only noticed it with Marshmallow.
For me it doesn't seem to correlate with charge level.
Having the same problem here and now that you mention it, it does seem to happen when it fully dies. Until someone comes up with a solution I'm going to see about backing them up and restore if it happens again.
Allowing your phone to completely die is a bad idea. The sudden shut down is what is corrupting it.
Also restoring that type of system data is just asking for other random issues, also not a great idea.
While I run an AOSP based rom I have never had my device forget any of my 5 BT pairings.
I agree don't let phone die.
Also if low battery plays a role (before phone dies), it could be related to battery saver features that can activate at low batteries level. (Adjustable in settings)
For the android wear app, turn off battery optimization (to prevent it from being interrupted by doze. )
I have had zero disconnection between my n6 and my moto 360 g1 android wear watch in the last month.
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
My phone has done this now twice in three days on N Preview 3. Has anyone found a solution?
mine does it too. but it will forget ALL my paired devices. it's pretty annoying
This is happening to me as well. Nexus 6 is forgetting all paired bluetooth devices.
Most annoying is the Android Wear issue because I've been having to factory reset the watch to get it to pair again. Some of this might be the watch because I'm running a Samsung Gear 2 with Android Wear but I also have several other devices that I have to repair every time.
Also seems to correlate with the battery dying.
There has to be a common bug. As all my devices have no issue remembering the pairing. Mind you I also dont pair to my car.
Also keep in mind that it was found long ago that OEM put in lists of cars that it will not work with in their roms. We found it on samsung devices years ago where it would block all connections to BMW, Audi and a few others.
N6 running 6.0.1 (no root)
This just started happening to me yesterday but has happened twice so far in two days. My phone has not died as seems to be a symptom for others here. It did get below 10% today but I charged it up without issue. it wasn't until several hours later that it wiped all of its paired devices. below is a list of my paired devices:
Samsung ATIV book 8 (windows 10)
UE Mobile BoomBox
Moto360 2nd Gen
2014 Infiniti Q50
2015 Nissan Murano
After it wiped everything yesterday I re-paired the following:
Samsung ATIV book 8
Infiniti Q50
Moto 360
After the first wipe today I paired the watch and the car.
If anyone has any ideas I would be grateful. This is a GIANT PIA!
Does not look like there is a solution to this forthcoming... is there anyone with this problem that's recently updated to N? And has it gone away? I get this usually after a forced reboot... all bt settings gone. Totally a problem.
Any update on this. I think it started happening after I updated to 7 and then went back to 6 after having battery issues?
rkshack
Giant PIA
Blown 89 said:
I have the same problem with my car pairing. I never let the battery for or get into battery saver mode so it's definitely not battery related for me.
Click to expand...
Click to collapse
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5. I drive a lot for work, and need my phone paired to a JVC headunit (listed as JVC UNIT on my phone) in my van so I can take phone calls handsfree, and listen to podcasts. Every now and again, maybe once a day, with no rhyme or reason that I can discern, I get into the van and notice that my phone is not paired. It's a pain to have to pull over and re-pair the phone, and then set it up a a trusted bluetooth device again (so as to avoid entering my passcode whenever unlocking the screen).
- Definitely nothing to do with battery levels. My phone is normally fully charged and plugged in to a charger.
- I don't lose all paired devices, as my UE Boom 2 (not often used) is still listed as a paired device, whereas the JVC UNIT drops off fairly often.
Please could someone sort this issue out! It sounds like quite a few people are experiencing it.
thanks,
Phil
Phil in NZ said:
I have this same problem too. Running Android 6.0.1 on a Samsung Galaxy A5.
Click to expand...
Click to collapse
Not likely to get sorted for your phone in this N6 thread. [emoji6]
I am on Android 11 and it still happens to me, my car pairing is being forgotten from time to time. Happens to any of you?