Has anyone seen an issue with late calender announcements like I have? I have the pre-rooted Black Hat Team .596 and for some reason my announcements for calender seem to randomly run late.
At first I thought this was a "battery saver" issue, because they basically announced themselves late right after I unlocked the phone after about2-3 hours of non-use. So I went to the battery saving options and found my phone running under performance mode, so I know that can't be the problem. Anyone else have this issue / a solution?
Thanks!
Related
Ok, so I've done some searching and I've found my problem is pretty widespread over a few different devices. However, it seems like no one has come up with a solution. My problem is this, SO a couple weeks ago I had the sync icon pop up in my notification bar. But then it didn't go away. I've tried looking on other forums for this solution but nothing yet. Thought I'd see if anyone here has the same problem and if possible, how to fix it. I can't help but think my battery life is suffering since it seems that since this started happening I notice the battery drain a bit faster than it used to.
I've tried several different possible solutions, except a reset. I loathe the idea of a reset, but if that's what I have to do then I will.
Running stock version. 2.2
Solution...
I decided to give up on my weeks long search for an answer online and called support today. Figured out it was the ooVoo application I had installed for video chat. It seems to keep your device in this perpetual sync mode even though you're not in that application. Once I deleted it the damned thing went away. My Tab, now with more battery power for Angry Birds.
I've been using back to future for quite some time, and just recently I have noticed strange behaviour.
My wife called me from a meeting, and while the phone rang in the background I could hear chatter from the meeting. I noticed this before but I thought I imagined that or something but this time it was so obvious.
Anybody else notice this?
P.S. Best and the most stable custom ROM on HD2 ever.
So I was about to enable Do Not Disturb mode till next alarm like I do everyday and I found that option is gone. Rebooted it twice and the option is still missing. No clue what's wrong. Am I the only one?
Im running completely stock 6.0.1
andr0idfreak said:
So I was about to enable Do Not Disturb mode till next alarm like I do everyday and I found that option is gone. Rebooted it twice and the option is still missing. No clue what's wrong. Am I the only one.
Im running completely stock 6.0.1
Click to expand...
Click to collapse
Many reports online of this same thing happening to others. Do a Google search or check out any android or xda related twitter account and you'll find them.
ohlin5 said:
Many reports online of this same thing happening to others. Do a Google search or check out any android or xda related twitter account and you'll find them.
Click to expand...
Click to collapse
Hmm. So it's widespread as per various reports and it started happening just today. I use this feature everyday and it was there till yesterday night. And it's reportedly happening only on devices running 6.0.1.
Woah, AP picked up the news too.
http://www.androidpolice.com/2015/1...e-is-weirdly-disappearing-from-6-0-1-devices/
Looks like the bug is gone after the 1st of January:
According to Android Police:
After a little feedback from our commenters, we've found that 1) the problem is affecting more than just Android 6.0.1, going all the way back to 5.1 in some cases, and 2) it's possible to work around it. If you turn off the automatic date function in the Android settings menu and return the date to something either before December 25th or after January 1st, the Until Next Alarm option returns.
That would seem to indicate that this is definitely a bug, and it should return to everyone on New Year's Day. Google will probably patch it in the next incremental release.
Nexus 6.0.1 MMB29Q + root SuperSu 2.66 + xposed 80.
The feature is not there. Tried to bring back dates in airplane mode but didn´t work.
I'm running 4.4.4 on a Samsung Verizon S5 paired with a Moto 360 2nd Gen running 6.0.1.
My notifications seem to be very unreliable. The biggest pain is that I can't seem to find any pattern to what happening. Here's what might happen after any notification comes in:
Vibration on the watch, followed with NO notification showing on the watch display.
Vibration on the watch, followed by notification displayed as I would normally expect.
Vibration on the watch, followed by a displayed notification, but the display comes 4-6 seconds AFTER the vibration.
Vibration on the watch, followed by a display of the PREVIOUS notification, which then flips to the current notification after about 4-6 seconds.
As I said, it's really annoying because I just can't seem to pin down exactly what's causing the issue or any sort of pattern for when it works, when it sorta works, or when it fails totally. This happens with all notification types to varying degrees. GMail, Outlook, CloudMagic, Hangouts, SmartThings... to name the programs I regularly get notifications from.
The only non-standard thing I'm running on my watch would be WatchMaker Premium. I don't have any app launchers running on my watch.
I've tried uninstalling outlook (as someone in the Android Forums suggested). I've tried a factory reset on the watch. I've tried uninstalling, reinstalling Android Wear on the phone. I've tried re-syncing apps... Just not having any luck figure out what's going on.
Anyone else experience anything like this? Anyone have any suggestions/thoughts?
100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.
sirrelevant said:
100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.
Click to expand...
Click to collapse
I suppose it's comforting to know I'm not the only one experiencing this. What phone/os are you running?
I'm wondering if upgrading to a new version on my phone would help at all. An 'expert' in the official forum said it shouldn't make a difference, but at the same time it shouldn't be acting like it is, so I dunno.
Just really frustrating cause "glancable" notifications is one of the big pluses of a smartwatch and right now it just isn't working.
Another question: Which service are you using? I'm on Verizon. If you aren't that would eliminate service as an issue.
(Yes, I know that service shouldn't be an issue... but maybe whatever programs/radio/whatever Verizon pushes on the phone might somehow screw with things??)
FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.
RedRamage said:
FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.
Click to expand...
Click to collapse
Same issues with my Verizon S5 and 360. How did you downgrade the moto 360 from 6.0 to 5.0? I saw the forum about it but it wasn't clear.
hello,
as the title says, i get these notifications all day long..
they appear for half a second and are gone before i can click on them.
the attached notification log shows that they pop up in irregular intervals, sometimes several times a minute.
i tried to disconnect and reset the watch, but the issue remains.
the problem came up just recently, but i didn't notice any updates.
any ideas what i can do?
watch: misfit vapor (fossil brand), android 8.0, wear os 1.5 (idk why it's not labled 2.something anymore, but it's definitely not the old 1.5 without playstore and so on..)
phone: sony xperia x compact, android 8.0
seems like a secomd reset made it a bit better.. now i get the notifications about 20 times a day..
what can that be? how often is normal?
could someone please check his log?
to get access you might have to enable developer options, then place a homescreen widget for settings -> notifications log
nobody?
xda isn't what it used to be...
I noticed the same. I belive it started after recent update of Google Wear.
I just installed Notification Saver app (my phone does not have notifation log option) and will revert back once I collect some information...
armsel said:
...will revert back once I collect some information...
Click to expand...
Click to collapse
Yeh, it is checking a lot sometimes, sometimes not that much (6 times a day yesterday!).
But today a lot more (attached picture)!
This is not normal...
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
A.D.I.O.S said:
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
Click to expand...
Click to collapse
I just did - although today it had only checked twice (so far), let's see...
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
A.D.I.O.S said:
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
Click to expand...
Click to collapse
Nope, noting and I don't think they will ever revert back...
I didn't use my watch the past week or so... let me see next week if the problem persists.
just updated to wear os 2.0..
still the same..