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
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Hi, I've been trying to track down the issue with BetterBatteryStats+ and Wakelock Dectector FULL and found that the issue is with the bluetooth_pm wakelock. I've been googling about and people only mention it but nothing gets resolved. There's only one mention of it on XDA but no reply:
http://forum.xda-developers.com/showpost.php?p=63955981&postcount=29777
What makes it's annoying is that when it goes away randomly and I get to enjoy the damn Doze feature but only to have it come back randomly. And this is when bluetooth is on. I haven't not factory reset the phone and restarting the phone may or may not have temporarily fixed.
What's is the damn "bluetooth_pm" wakelock? There's not a lot of info on this wakelock and I can't use Amplify or DisableServices to reduce or get rid of outright. I hope someone has a solution this issue.
EDIT: It's a Kernel wakelock.
Sorry for bumping this again. I have still not found the reason of why it happens aside from disconnecting from my devices (I have my phone connected to my lg tone headphones, motorola headset, my car, and my android wear watch).
Is there a way to get into the kernel and just kill it manually or set a timeout setting to kill it. The only way for me to fix it is to restart my phone; I shouldn't have to restart to get rid of this annoying wakelock.
I really hope to hear a response soon. Thanks in advance.
Bumping one more time, now with logs if ANYONE is just willing to look into this and find out what's wrong: http://forum.xda-developers.com/showpost.php?p=66119017&postcount=30423
In this post attachment, it happened again just 15 minutes ago. Please, someone has to be technical to read the logs better than what I can come up to determine what's wrong with it or provide an app to find and kill this wakelock without having to restart the bloody phone.
I know this is super old but I found out that GasBuddy of all things was causing the damn bluetooth wakelock. Not a damn clue aside some saying it uses bluetooth for location but REALLY?
Luckily, using Greenify fixed the problem
I had the exact same symptoms and phone, did the same steps and found the same thing is as you. GasBuddy for some reason causing bluetooth wakelock. Greenify, as you experience, 'cured' the problem. Interestingly, after dealing with this issue for months, after only a few hours of verifying a fix, GasBuddy updated (with new logo) and while somewhat improved the wakelock issue, it's still an issue. Unfortunately, Greenify seems to have a more difficult time hibernating the new version...
This is kind of a big bump, but I'm having the bluetooth_pm wake lock on my G6 and Google doesn't show me much except for this thread. I don't have GasBuddy on my phone. Has anyone experienced the bluetooth_pm wakelock and figured out a way to get rid of it?
xPhantom said:
This is kind of a big bump, but I'm having the bluetooth_pm wake lock on my G6 and Google doesn't show me much except for this thread. I don't have GasBuddy on my phone. Has anyone experienced the bluetooth_pm wakelock and figured out a way to get rid of it?
Click to expand...
Click to collapse
I am having same issue on my Verizon g6. I lose about 10% battery per hour when screen is off. Phone wake locks through the roof.
Yes, this time old issue still exists for me, and it makes it where I cannot trust the phone. I've wanted to use my Nexus 6 as a daily carry, but have to use my LG G3 instead.
The N6 completely drops cellular signal after the screen turns off and goes into deep sleep. After waking the phone, it requires a reboot 90% of the time to get it to reconnect to cellular service. Rare occasions I can leave it for a few minutes, toggle airplane, and get it to reconnect, but by then a reboot is faster. Obviously, a phone that drops cell service when the screen is off is no good.
The fun thing is not ONLY is it dropping cell service, it maxes out the cell radio searching. If I don't notice it dropped service, the phone gets hot and the battery dies very quickly, this also happens in AIRPLANE MODE. Yes, even when airplane mode is on, I turn the screen off, cell service "dies" and the radio kicks on and searches for signal, gets hot, kills battery, all while in airplane mode. The battery information page shows blank for the signal meter while in airplane mode screen on, but turns red and shows indication the radio comes on when the screen is off.
The only "solution" I have is to constantly play music, or have it plugged in. Currently I have an 8 hour mp3 of pure silence playing on repeat. Naturally this keeps the phone locked at 300Mhz while the screen is off and never sleeps, but the cellular radio works as normal, stays cool, and battery drain is minimal, never disconnects. The problem is: doing anything that causes said silence to pause and not noticing/remembering. Watching a video, casting something, rebooting, etc. Also the phone never sleeping is generally not good, but I can't trust the media player not to sometimes stutter and then the signal drops out. You see my trust issues. While the phone is plugged in, which also prevents deep sleep, the phone is fine as well.
Oddly enough SOMETIMES the phone does as it should. I might check the phone and notice music is *not* playing, but the signal is fine, and the device has been in deep sleep with no problems. I've yet to isolate what causes it to stabilize, but after a reboot, it's back to its old ways.
Things I've tried:
Flashed ALL the official images. (Problem exists across them all.)
Tried a few custom roms
apps that hold a wakelock. (trying to keep it from sleeping, which worked, but signal still disappeared)
Removing, downgrading, upgrading, etc Google Connectivity Services.
Different basebands
Different carriers.
Other things I can't think of now.
Current Setup:
Pure Nexus (latest)
System mode root + Xposed system mode
Bootloader: moto-apq8084-71-21
Baseband: D4.01-9625-05.39+FSG-9625-02.113
Attached a logcat of it dropping signal after screen off, and luckily caught it regaining signal as well in the same logcat.
EDIT: Alright, can I get a moderator to move this threat to Q&A. I posted in Q&A and it appeared in General... Guess that's what I get for having multiple tabs open.
sim issue
yes, this seems to be issue with N6.. (issue is somewhat related to SIM card). Can you try without SIM card inserted?
Just sell the phone. Dont waste nerves trying to devug it.
I had similar issues, but switching to 2G helped.
To be honest, these smartphone issues have been things i have experienced with all brands.
From random reboots with samsung, cellular issues with LG to phantom clicks with sony. Not acceptable given the price.
So far, every smartphone has caused issues.
shadowcore said:
Just sell the phone. Dont waste nerves trying to devug it.
I had similar issues, but switching to 2G helped.
To be honest, these smartphone issues have been things i have experienced with all brands.
From random reboots with samsung, cellular issues with LG to phantom clicks with sony. Not acceptable given the price.
So far, every smartphone has caused issues.
Click to expand...
Click to collapse
I'm not the type of person to sell something with a known issue, that's as bad as selling a car that you know the transmission is about to go out. Since it's not my main phone, I don't let it really get my nerves, instead I use it as a brain teaser. Finding new and interesting ways to get it to keep working, but at the same time I would like to find an actual fix. In case I ever want to... y'know... sell it. I'm not going to sell a defective product. I have the experience and knowledge to actually use it, and on Fi it's a good backup. The wifi doesn't cut out so it still works if I'm around wifi.
Also, replying with "Meh just sell it" is a very unprofessional and indecent response on a large forum dedicated to helping people and making their lives with their phones easier, and learning new things along the way.
Skreelink said:
Also, replying with "Meh just sell it" is a very unprofessional and indecent response on a large forum dedicated to helping people and making their lives with their phones easier, and learning new things along the way.
Click to expand...
Click to collapse
I never said that you shouldnt disclose that the phone is defective.
I assume that goes without saying.
Secondly, my experience has been that such issues are unfixable.
When i had an LG phone with issues, the solution was to sell it as scrap/defective device.
From the looks of it, your issues are unique. I also have issues with connectivity and the solution was to switch to 2G.
However, it only happens with one network operator.
Also, this is a forum, you asked for advice, i gave it to you. You dont have to like it.
Oddly enough without any system changes or anything and with how long the problem has stood... It seems to be acting correctly now. Doing some tests with reboots, etc and it seems to be going to sleep fine and not losing signal. Will continue to monitor this oddness and if I figure anything out, I'll update this thread for any of those who might still have this issue.
Every time I turn location on, which I normally have off, I get two pop-ups for consent. It is really annoying. Is there any way to prevent those?
It's all stock, on Verizon.
I know this isn't the answer you're looking for, but I had the same problem, and I simply ended up... leaving Location on all the time, and never turn it off. In my experience, it automatically activates whenever it's needed and is shut when not in use. I didn't notice any impact on battery life (maybe it does but it didn't trigger my annoy-o-matic) and on the plus side, I don't ever have to toggle it and answer those silly popups anymore. Also, maybe this is "bad" for your privacy, as you don't control precisely when you want to be tracked or not but, and maybe that's what they're pushing people to do with those stupid popups but... oh well I guess we are already tracked anyway, and it's just a matter of "accepting" it instead of thinking that we can actually refuse and prevent it