Hello together,
I'm owning a xperia V and until two or three days ago everything was working fine.
Then I came up with the idea of a nice tasker-profile which should say wake-up, 15mins after I disabled the alarm.
When testing it I noticed that TTS wouldn't work. After 15mins waiting (yes I enabled continue task) no sound when the lockscreen is on.
When the screen is unlocked, this works.
Then I also noticed, that my alarm isn't working. My cell doesn't wake me up in the morning. The alarm is set up correct and it sais that it'll be active in some minutes. Then I lock the screen. If I do that: no alarm, nothing. just a black screen. It's the same for other alarm-apps. They do not react when the lockscreen is active. Only when the screen is on, everything works.
I do not know what caused this. I also did reset my device and after that it was working. Then I restored my apps and it worked still. Then however some minutes later it happened again and doesn't work since then. I don't know which setting I might have changed but I really need to fix this. I don't know what's wrong...
Cell: rooted, unlocked BL, relevation ROM.
Thanks a lot!!
Elarion
Edit: Some other things:
Let's say I set an alarm for 4pm. When I look at the display with lockscreen on it still shows the alarm, but the clocks (center and in bar) are already at 16:01.
What does that mean?
Edit2:
Also other apps like Snapdragon battery extender get closed immediately when I enter the lockscreen...
Related
I am not sure what is going on, but for whatever reason, certain features of the stock alarm app simply don't work. e.g the option for setting side keys to snooze does absolutely nothing! This is probably my biggest issue as the other could be written off as me doing crazy things in my tired waking up state. It has simply never functioned as it should for me. From the out of the box telco rom, to unbranded stock rom and now KA04.
The UI of the app is quite nice when setting alarms, but just terrible for actual alarms. I seem to dismiss them easily as-well :|. Somehow my partner is getting to the home-screen and opening other apps when trying to snooze (no idea how she is pulling that off though). Sonic Jump's title screen at max volume at 3 am is quite horrendous to the ears
I've set every possible setting to avoid the alarm just dismissing itself yet it's still a pretty frequent occurance.
So either, does anyone know a fix and/or are you experiencing this? OR can you recommend a really solid 3rd party replacement? I've had good experience with AlarmDroid in the past but recently on my GS2 it was having some compatibility issues. With an alarm you don't really wanna risk that it might not go off though lol.
I tried the timer once to boil eggs, it shut down as soon as I locked the screen for some reason. As soon as I unlocked the screen the timer resumed from where I'd locked the screen.
Downloaded Timer instead, it's always served me well.
Gentle Alarm is my alarm clock. Been using it for 2+ years now. love it. Love to be woken slowly by nature sounds.
rage77 said:
I tried the timer once to boil eggs, it shut down as soon as I locked the screen for some reason. As soon as I unlocked the screen the timer resumed from where I'd locked the screen.
Downloaded Timer instead, it's always served me well.
Gentle Alarm is my alarm clock. Been using it for 2+ years now. love it. Love to be woken slowly by nature sounds.
Click to expand...
Click to collapse
I think the alarm app is buggy, agree the side button does nothing (code probably ported from another Experia and not checked) pretty poor
and when the alarm actually activates and I miss the screen slider to turn it off - when I activate the home screen and pull down the notification bar to turn off the alarm - it's not always there, the only way I can turn off the alarm is to turn off the phone
Geoffxx said:
I think the alarm app is buggy, agree the side button does nothing (code probably ported from another Experia and not checked) pretty poor
and when the alarm actually activates and I miss the screen slider to turn it off - when I activate the home screen and pull down the notification bar to turn off the alarm - it's not always there, the only way I can turn off the alarm is to turn off the phone
Click to expand...
Click to collapse
Lol well at least I'm not crazy then. You can never be sure who's fault it is that early in the morning .
no problems with alarm here except the early morning syndrome hitting the slider
I have a problem with the alarm. Say I've set up an alarm that is supposed to repeat every day of the week.
But every time I dismiss it when it goes off, it disables itself, so I have to enable it again manually in order to be woken up the next day.
does it work the same way for everybody?
trbr said:
I have a problem with the alarm. Say I've set up an alarm that is supposed to repeat every day of the week.
But every time I dismiss it when it goes off, it disables itself, so I have to enable it again manually in order to be woken up the next day.
does it work the same way for everybody?
Click to expand...
Click to collapse
I was late for work the other day because I snoozed the alarm and it didn't come back, at all!... Not Sony's fault, I had set max. number of background processes to 1, and when the lockscreen process starts, that means the launcher becomes the 1 background activity, and the clock gets bumped from memory.
Oops.
-Soen
I've had my Turbo for a few days now, and I'm really liking the wave to snooze alarm feature, but today when I waved to snooze, instead of the screen going back off, the phone went to my homescreen, so I had to reach over, grab it and hit the power button, completely defeating the idea of touchless control. The second time it went off I noticed the unlock sound right before the alarm sound, meaning that for some reason the alarm is unlocking the phone. I tried clearing Clock data, toggling lock screen types, and rebooting the phone, but the issue still persists. The same thing happens using the active display notification to snooze. The alarm really shouldn't be unlocking the phone when snoozing, but I haven't changed any setting or installed any new apps since yesterday when it was working fine.
Edit: Factory reset didn't even stop the alarm from unlocking the phone, but I'm 100% positive it did not unlock it the first 3 days I had it.
I exchanged the Turbo for a new one as Motorola recommended, but this one is having the same problem from the get go. Is this not a problem for anybody else?
Moto Actions > Wave to Silence ON
Set an alarm
Wave to snooze or swipe to snooze from active display
Does the phone unlock or turn back off? What software version?
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
1. if you dont have a lockscreen then it cant show you notifications on it. duh, lol.
2. we all have known about this since before lollipop came out.
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
budorat said:
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
Click to expand...
Click to collapse
if you dont have a lockscreen, then it has nothing to show the incoming message on. if no lockscreen, then it would just show in the status bar.
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
budorat said:
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
Click to expand...
Click to collapse
yea, the way the code is written, there needs to be a lock screen to be displayed. i dont really use it anymore, but i found it to be around 90% as well.
Just to re-iterate, Ambient display is displaying the Lockscreen notifications, not SystemUI notifications, so to show the lockscreen notifications, Lockscreen must be on.
budorat said:
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
Click to expand...
Click to collapse
I totally agree. I upgraded from my 2013 Moto X, with Moto DIsplay, to the N6. I NEVER used a lock screen on the Motox, and enjoyed being able to just glance at the phone to know what was incoming.. its quite annoying that I can no longer get my notifications to show up on my screen without turning the phone on, and pulling the shade down. I'm on the computer all day, and have my phone setup next to me and use it to get a quick view of incoming work emails, with out taking my hands off the keyboard, or even stop typing for that matter.
If I would have known that the N6 was unable to work in this matter I would not have gotten it. I would have gone with the Moto X 2 instead.
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
tr3mm0r said:
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
Click to expand...
Click to collapse
I dont think it works with any.
That's what I was afraid of. Sticking with stock locker then since I love the new feature.
Sent from my Nexus 6 using XDA Free mobile app
I've searched far and wide and can't find a solution for this issue.
Here is what happens: for no reason that I can see (no new notifications), my screen turns on its own. My phone is just there on the table when this happens and I haven't touched it.
This happens whether the phone is plugged in or not. It happens in the middle of the night and wakes me up.
Things I came tried:
- turn on do not disturb and remove all exceptions.
- disable always on display.
- disabled all lock screen notifications.
- disabled a notifications.
Other things I've tried:
Lift to wake and all other things that could wake the screen.
Did a factory data reset and re setup my phone from scratch.
Nothing works. Can anyone please help me?
Thanks in advance.
I had the very same problem until a few days ago when this behaviour suddenly stopped. What changed? I had shutdown my Pebble watch and connected a Wear OS watch to my phone.
I don't know what the Pebble did, but it looks like it woke up my phone at random intervals.
Maybe it a bluetooth device you've connected?
I'm expeciencing sometimes this behaviour when listening to the music on bike with phone in pocked on back. I disabled all "smart" funcions like smart lock, pocket detecting, wearing detection etc and it stopped.
I think it is caused by new type of proximity sensor used in whole S10 line (so I think it is hw related). I read somewhere than it detects skin proximity even thru several layers of cloting.
It is behaving strange even during phone calls - when put phone down from my ear, it tooks several seconds until screen lights on.
it's one of the things that bothers me a lot about otherwise great phone.
facing same issue
I always loved Samsung galaxy s10. I bought it from my friend who used it for 10 months. I am facing the same issue first I thought it is because he used it for 10 months and some bug appeared but now I came to know its not just me. if anyone knows how to fix it then please post a reply. I really need to fix this
I haven't noticed that on my S10. It sounds like something is triggering it, but what. Do all of you use Bixby because I don't.
Hi,
Love my S21 Ultra, but I have one issue that im failing to solve.
I use Google Clock, and the alarm function works perfectly - never had it fail on me.
However the countdown function doesnt go off (ie, no sound or vibrate) if I leave it running in the background with the screen off.
If I turn the screen on after its supposed to have gone off, it then goes off, with a minus number of seconds on the screen.
Ive been through all the Samsung 'background app power saving' stuff, and made sure the Google Clock app is excluded (although if it was that id expect the alarm to fail too).
Handset is the 256Mb UK Three branded one, with latest official firmware, no rooting or anything like that.
Anyone come across this please?
thanks, George
How are the Do Not Dusturb and Sound settings during these issues?
Have you exempted Google clock to allow Notifications while sound is off or when DND is activated?