my always pulse function in the CM RC3 settings is not working, the actual notifications pulse for messages and everything is working but the always pulse when screen is on is not working , how can i fix this?
i'm also experiencing the same thing..
Are you guys thinking that the option is supposed to always flash when the screen is on, without any notifications waiting? Because that's not how I interpreted it.
I thought the option was for your regular notifications to continue flashing while when the screen turns on. Because originally you couldn't have colored notifications while the screen was on, they would stop when you turned it on.
What is that option supposed to do?
I thought its an always pulse while the screen is on option. In fact it was working for a few minutes wen i first flashed the rom but now its stopped. I think there must something conflicting with it. Dont kno wat tho
Sent from my Nexus One using XDA App
Related
I tried a bunch of searching and just keep finding stuff about trackball wake, trackball colors, etc.
My problems is that my trackball will only light up on an incoming call, nothing else. Not email, text (even with Handcent), or tweets.
I was previously running CM 5.0.6, which they all worked then. Of course I updated to Froyo this weekend (Thanks Paul!!), with a full wipe. I have also reflashed Pauls new Froyo with no radio this morning with no change.
Any ideas?
joshlusignan said:
I tried a bunch of searching and just keep finding stuff about trackball wake, trackball colors, etc.
My problems is that my trackball will only light up on an incoming call, nothing else. Not email, text (even with Handcent), or tweets.
I was previously running CM 5.0.6, which they all worked then. Of course I updated to Froyo this weekend (Thanks Paul!!), with a full wipe. I have also reflashed Pauls new Froyo with no radio this morning with no change.
Any ideas?
Click to expand...
Click to collapse
OK, evidently the trackball will only light up for me when the screen is off. So try this. Download handcent, send a test notification to your phone, but don't click ok, simply shut off the screen and see if the trackball lights up.
Also, I don't know how some people are managing to get it to light up with the screen on, because as soon as my screen powers on the notification dissapears. I remember in Cyanogen there was an option to pulse while the screen was on, but so far I've been unable to find it in the stock FroYo build. Anybody have any suggestions?
got it all worked out now.
I had to turn off quick reply in Handcent. It was turning on the screen and therefore not allowing the trackball to light up. I just sent a text with screen off and it worked ok. I guess the "test notification" in Handcent is not 100% yet. I havent seen an option to pulse while screen was on either...dont think its there, yet.
Hi!
I've trying to figure out why apps like Active Notifications and Floating Touched doesn't work the way it should.
I'm running stock and I'm rooted.
Floating Tougher has an option to lock screen when button is pressed on screen. However when this button is pressed the screen goes dark and flickers and then turns on again. At first I thought there was a problem with the app do I didn't think much about it.
NotifyX and Active Notifications etc. doesn't work either. When I lock my screen there's a brief moment, 6-7 seconds, under this moment the screen stays lock but then turns on to show the notification screen by the app.
I've uninstalled most of my downloaded apps but the problem still persists. I've checked wakelocks but couldn't find anything worth checking out.
Anybody else with the same problem or maybe even a solution?
Thanks!
Sent from my GT-I9305N!
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
Hi guys
Ambient display used to work for me and now seems to not ever show up.
I have a protector on the screen but it has a full cut away by the proximity sensor and so I dont think that is an issue. Also checked a sensor app and they are all working
I installed a notification app called edge colour notifications which I then removed. Issue seems to be timed with that but not sure.
Any ideas how to possibly get it working again?
Not rooted
Thanks
darrenkellum said:
Hi guys
Ambient display used to work for me and now seems to not ever show up.
I have a protector on the screen but it has a full cut away by the proximity sensor and so I dont think that is an issue. Also checked a sensor app and they are all working
I installed a notification app called edge colour notifications which I then removed. Issue seems to be timed with that but not sure.
Any ideas how to possibly get it working again?
Not rooted
Thanks
Click to expand...
Click to collapse
Since you're stock, you're kind of limited. Boot to recovery, select wipe cache, reboot.
Clearing cache didn't work but I think I figured it out.
I'm using a app called Automateit which runs phone actions off triggers. I turned it off within its settings and now ambient seems to work. Tested it twice now turning the app service on and off and seems to work. Hopefully that's sorted.
Have another strange issue as well where if I have screen lock enabled and reboot the phone, when it reaches the lock screen it goes into a weird loop on the lock screen and requires rebooting as you can't unlock. Have to reboot many times before it will let you in without this loop. Disabling the lock screen seems to stop this. Anyone else had this?
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.