I keep setting reminders to pop up an on screen notification then after a reboot and not every time) it loses the settings and I have to go back into SOUNDS - NOTIFICATIONS and set reminders to have the ON SCREEN MESSAGE again.
Does anyone know how to make the permanent as it is driving me mad.
I too am having this problem - why does it do that????
I think I had this problem before updating to Rom 1.37.707.1 too...so probs not rom related
It is weird. It only resets sometimes as well. I cant work out what causes it.
wonder why not many ppl complaining about this issue? Its good having notification on
yes mine did it last night again but had not done it for a few days.
I wonder if it is to do with certain software configurations i.e. if you have something installed. I have not added that much to the standard build or even if it is noise specific i.e. a certain sound file.
Saw the option when flashing ElementalX Kernel. I kept everything as default. Just wondering what this is.
I searched but cold not find a definite answer.
Thanks!
Its something that happens to some people when they end a call. There's no harm in selecting it.
Sensor_ind is a pain in the ass.
It isn't just phone calls, so many things can trigger it
A fair few of us had issues where it would hold a Wakelock for hours on end, draining the battery considerably.
Being able to turn it off has been excellent for me, haven't had any negative effects either
Ever since updated to the Nov 1st update. When I turn my screen on there is a 1 in 3 chance that the screen will be at max brightness. The only way to fix it is to wait 5 seconds or turn the screen back on then on. Anyone else seeing this?
Yea it started happening to me about two weeks ago after I installed GravityBox , don't knowwhat to do it's very annoying .
Known issue. I've filed a bug, please star it. Here's the link where we discussed this in detail.
http://forum.xda-developers.com/showthread.php?t=3256165
Thanks @andr0idfreak. I was starting to worry I was alone. From the bug report seems a lot of people are seeing it.
I'm really stumped here. I haven't been able to find any solution to this issue through searching, so I figure I might as well post something about it.
For the past few months, I've been having an issue with my watch screen turning itself on then dimming after a few seconds. This seems to occur every few minutes or so even when theater mode is enabled and when always on screen and wrist gestures are disabled. This issue persists even after unpairing with my LG G4 and after a factory reset (on both the watch and phone). It should also be worth noting that I have recently rolled my phone back from the latest VZW Marshmallow OTA to a rooted 5.1 image in an attempt to resolve the aforementioned problem, but from what I can tell, it has only become worse.
From what I've been able to gather from battery/wakelock monitoring apps and bug reports is that the phone is regularly sending wake requests at semi-regular intervals. I have not installed any third-party wear apps and I've disabled pretty much every Google sync function but the problem persists.
I am at wits end here as to what I can do here. This coupled with my phone suddenly developing a severe wakelock problem has made me seriously consider switching to another manufacturer, and this time I may not exclude Apple as a choice.
Has anyone else experienced an issue like this that might have some insight as to what's going on?
Thanks!
PS: If needed, I can provide the full bug report along with a quick spreadsheet I made to organize the kernel wake source info found in the report.
It's not saved as one of the ringtone or notification sounds on my phone.
It does not do any type of notification I have already tried notification sniffers and it does not do any type of notification at all.
I kill all apps, turn of the screen, nothing can stop it from playing the entire toon for about 45 seconds.
I have posted on several boards but cant figure it out.
I've attached the audio that I recorded of it playing.
They did tell me to run a bug report directly after it happened which I did. They told me to upload it to battery historian: https://bathist.ef.lc/
But I can't figure out what to do once I upload it or how to parse the information.
audio sound:
Dropbox - File Deleted - Simplify your life
www.dropbox.com
Does the sound play at any specific time or is it at least once a day or something?
Usual practice is to see what your most recent apps were, as one of them may be causing this. You might even check for latest updated apps, because it could be something added by a new feature/update.
If that's not finding an issue, you might boot into safe mode and seeing if the noise stops happening - this would indicate that an app is causing it. Alternatively, maybe uninstalling all other apps is a good place to start. If it goes away, then add apps back (maybe a few at a time, to make it easier) and monitor for when it comes back.
I'm not familiar with that Battery Historian app, but it seems interesting. If you can identify when the sound happened, it should line up with the "audio" events shown in the graph. I assume there's some way to zoom in on that graph, so maybe you can see what happened during that time, and help narrow down a possible app that could be causing this.
thanks so much for your reply.
The sound happens so infrequently, the last time it happened was 2 weeks ago. Sometimes it might happen 3 or 4 times in 1 day. And the phone use and app use are static and have not changed. Same phone use every single day. It's impossible to figure out it seems.
It's so frustrating.
I ran the bug report directly after the sound played so the end of the historian file is when it happened and looking at the "audio" I do see something there that played for 59s which is about right for how long the audio is.
But I can't figure out any info about the audio besides what is on the tooltip.
Maybe someone knows more about this battery historian.
Bug report for who? If you're just throwing out a but report to an app or even the OS, chances are that it will be ignored as irrelevant, unless you can convince the place you're reporting it that this is something they are causing... I'm guessing that report is not going to do what you think it is.
I don't see how battery historian is going to help, so maybe you need to pursue the thread which recommended it. I did a quick search and I don't see how that app will help identify the problem.
One other idea I saw was that maybe a browser tab is generating the noise. Websites can sometimes provide notifications and such, if you allow them to. I never do, but I can imagine that as a source of noise.
In the end, this is likely an app that you have. You just have to remove as many as you can, and see if it goes away. If it doesn't then you can look deeper at your remaining apps. If it does, then the job is easier and you just need to add them back in (if you still want them) until it comes back. Since it's so infrequent, it's going to be difficult to have happen... but I doubt it's an OS-level problem otherwise others would have the same issue.
thanks for your response and I have been trying to do that but it has not worked so far and that is why I am posting here.
Something on my phone is firing this sound and if you are telling me there is no way for me to figure it out from some type of log, then I have to tell you that you are wrong.
Everything that is done on Android there is a record of I just need to figure out how to read this record.
Not everything is always logged with any OS or app. There are settings to set log-levels higher or lower. Most apps set only "warning" or "error" level logs, generally speaking. There are often ways to increase this, but it's not there by default for sure... I wouldn't expect a sound activity to be logged by default as it's not an error.
But, if you know better than me, then I'm sorry I can't be more helpful. I will stay out of it going forward. I would love to hear how you find it, because it's great information for anyone on XDA (and I would certainly like to know as well).