I've had a Galaxy S8 for a few months now. Right from the first, notification vibrations have been intermittent, short, and perhaps even weak. I have vibration intensity turned all the way up and when I drag that slider I feel the vibration easily - but when I get a text message or an email, I usually don't even know it, even with my phone sitting right beside me on my desk. All of my prior Galaxy S phones (and other phones, too) had strong, lengthy notification vibrations. I've been through all the main settings multiple times with no success. Can anyone recommend an app or other solution to lengthen or otherwise strengthen my notification vibrations? Perhaps some secret Samsung menu somewhere? Sadly, I can't root this phone, so that's a limitation.
Related
Hi all
Does anyone know if there is a way to control the length of time that the phone vibrates for? I rarely use my phone with the sound on (meetings etc.) and I realise that it is easy to recognise the difference between an incoming phone call and a notification by the length (and repeat) of the vibration going on in the phone's holster....
The notification vibrate seems to go on for about 5 seconds, whereas the fone ringing vibrate is much shorter and repeats at reasonable intervals.
Is it possible to modify this so that it does short pulses instead of zzzzzzzzzzzzzzzzzzzzzzzzz!! I don't know what the battery consumption is like if one would receive say 30 notifications per day as opposed to just a few. It feels like a reasonably serious motor that is turning for this vibration.
I had the same thoughts, but little research as I am struggling with more serious issues of my TyTN...
Registry does not seem to have anything concerning vibration length.
It would be surely nice to control vibrations... some much less complex devices have such a feature from ages
Vibrate
Hi Rich,
This has been my number one bugbear since I first got this device. I've posted a couple of times here and on Modaco, but not a lot of feedback apart from the following:
http://forum.xda-developers.com/showthread.php?t=281543&highlight=vibrate
I've not tried it yet but let me know how you get on.
PaulB
Got my phone Thursday (ordered on launch day).
Basically with each notification from email, voice and maybe others, the phone vibrates twice. Even though I have vibration turned off in the notifcation settings for each app. I know this issue is not unique to Nexus 4, as my Galaxy Nexus began doing this as soon as I updated it to 4.2. It's pretty annoying though, and considering the Android team devs say they test the releases...I find it hard to believe something like this slipped through.
I'm pretty sure a bug report has been submitted to the android team, but wondering how you guys are dealing with this. Is there a workaround?
Loving the phone otherwise.
Thanks
-Mike
does it vibrate if the phone's on silent?
I am trying to use the phone on vibrate mode, but prior to 4.2 the settings in each app had an effect on which notification would vibrate and which wouldn't. In the gmail app I have it set to blink the notification LED and vibration is set to never.
It is widespread.
http://code.google.com/p/android/issues/detail?id=39592
All I want is "peeking" and the lockscreen notifications to work! Isn't this part of Marshmallow?
Anyone else find notifications to be not working/inconsistent? What I am looking for is to have the screen turn on with every notification...this phone is either sitting on my desk or in a car holder most of the time, so I want to see the notifications without having to handle the phone. I've tried some 3rd party heads-up notification apps that work pretty good, but I am having issues with the lock screen (sometimes I have to enter and pin AND use the fingerprint scanner, which is a bit much to just access the phone).
1. I seldom get peeking notifications even though "peeking" is selected. With some apps, peeking works sometimes and not others. I have never seen a Peek notification for gmail.
2. I find the notifications seldom turn the screen on, even though I have the ambient screen turned on. Perhaps this has something to do with problem 1.
Am I the only one?
I have the same issue. Did you find a fix?
There is already a thread on this topic, may be answers in there. However, its working fine for me, so its not an issue for all users.
Hi,
I noticed that I have this problem also. Someone managed to solve this?
Have you tried putting apps in the priority lane?
It seems an obvious omission that the AOD does not reveal basic handset status.
Flight Mode and Mute/Vinbrate status (and probably some other things) would be great stuff to know without having to activate the screen.
Is there a setting to display this info beside the Date Time and Battery?
I am probably missing something simple here as I find my way around my new S7 edge.
Yeah turn on your screen.
Sent from my Blackberry Bold
Will do for now.
Hopefully Samsung might add phone status when/if they update AOD.
Time and date on AOD is of little use to anyone who wears a watch.
I have to put my phone in and out of flight mode several times each day. I also set it to silent call in meetings quite ofter. A couple of icons displaying this status of this would be far more useful to me. This way I do not have to continuous toggle the screen on to see if calls will come in, or be audible when they do.
Before I even get started, I know CM13 is outdated/discontinued/insecure. I'm aware, I'm stuck with it for a while.
I've been trying to get the notification LED on my phone to work the way I want. I had no problems doing this with Light Flow on my old Samsung GS4. Things were not so peachy until I was reminded Cyanogenmod has built in controls for the notification LED. I have everything set up just the way I want it, it demos just fine when I'm punching in the settings. The problem is it won't work reliably when I set my phone down.
With my GS4, if the screen was off and I had notifications, the LED blinked accordingly. My N6P doesn't do that. I've caught it blinking a few times throughout my day, and had friends send me notifications while it's sitting on my desk, so I know it works sometimes. But the LED won't stay that way forever, eventually it just decides my notifications aren't important enough to me and stops blinking.
I'm having a hard time really pinning down it's logic because it seems to just work when it wants to. I have a theory that the way the 6P is really aggressive about saving battery, whatever service controls the LED is being woken up when a new notification comes in and eventually being put back to sleep, but I simply don't know enough to say. While I'm at it, I don't think I have any way of assigning priority to the different notifications (a text message is more important than an email, for example), so my color code scheme might as well go out the window.
I don't know why google seems to hate the notification LED so much, every time I try to google the issue I just get tons of pages telling me how Google hid it away and you can turn it back on in the settings for AOSP. Obviously none of that is helpful, maybe someone here has an answer?