Develop Bugs

Phone not vibrating when receiving a text

Hey guys, first post here of many hopefully.
Been following this thread from near the beginning and have finally got my hands on a HTC Desire via Vodafone Twitter deal
Absolutely love this phone and it's the envy of all my friends which is never a bad thing. I'm constantly discovering new things which is awesome and I'm pleased I came and saw the Android side.
Anyway, I've come across a problem.
When receiving texts, I've noticed that the phone will not vibrate. I've made sure that vibrate setting in the Messaging settings is green ticked and that Notifications is ticked. But still not working. It works when i'm rang just not when texted.
Have tried using Handcent messaging app but had the same problem... What can I do?
Thanks guys

I've had the same problem since I got mine two weeks ago.

Have you resolved this in any way? It's bloody annoying!

Hmm, strange... seems to work on my phone ok.
Since you have already tried Handcent, try the app "Sound Manager," from the Android Marketplace. Use "vibrate settings" toggled "vibrate whenever possible," and it see if that works.
Other than that, backup your data and try a hard reset (also try without SD card inserted) to eradicate any potential software bugs.

Tried sound manager, still no help.
I can get calls and notifcations to vibrate when on the normal profile and set them to vibrate, but on my normal profile I want sound only, so have vibrate turned off. When I change to the vibrate only profile, it will only vibrate for calls and not notifications.

Check out this thread too.
http://forum.xda-developers.com/showthread.php?p=6331433

Text message notifications disappearing

For the last week or so I've noticed that when I get a text, I get the preview pop up of the text, and then it disappears - along with the notification of the text. It will either disappear immediately or soon after. Sometimes if I have multiple text notifications - and I touch one - the rest will disappear. It also removes the 'unread' badge count on my Nova Launcher bar. This has never happened before, and I'm unsure what could be happening now to cause it. I normally use Textra, but I switched to Android Messages to see if it was an app error but the same thing continued.
I was aware of the Oreo issue where text messages weren't being received, but I'm definitely receiving them. I'm on a Pixel 2 XL now, but this was happening with my Pixel XL last week also. I've tried turning off the battery optimization in case it was acting funky, but that hasn't changed anything. Any ideas?

I am having the same issue. I'm on a Verizon Pixel 2 XL. I get a text, the notification starts to play and then cuts off, not showing an unread notification. I'm getting the text, if I go into Textra it shows the new message, its just marked as read.
Coincidentally, I'm also having an occasional issue where my screen won't wake up and I have to reboot the phone to get the screen to turn back on. Haven't seen anyone having that issue yet either.

I have noticed the same thing on my Nexus 6. I haven't noticed an update to the messages app that corresponds to when this started, but the android wear app updated around the same time, so I was curious if it had something to do with that.
---------- Post added at 09:02 AM ---------- Previous post was at 08:48 AM ----------
I just uninstalled the wear app and my notifications don't disappear any more. Unfortunately, I can't use my watch now

Messages notifications are disappearing on my Pixel 2 (non-XL) also. Sometimes they disappear so quickly that I don't even get the partial sound, just a short vibration from the phone.
I also have a Wear device. Haven't tried removing the Wear app, because all other notifications are working correctly, and I depend on them much more than the occasional text I receive these days.

I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs

benmeroff said:
I'm getting this on my Galaxy S8 as well; I was finally able to track this back to the Android Wear app, but as I haven't told it to silence notifications on my phone when connected to my watch, I'm not sure exactly what is causing this bug...
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
I just noticed that I'm having this problem as well after a few people asked me why I hadn't responded to their texts. I'm sure this used to work fine. Maybe it was broken in a recent update of messages?
Good catch tracking it to Wear. I have figured out the following:
If the watch is on, the text notification gets "eaten up" by the watch and does not show on the phone
If the watch is off, the notification does remain on the phone
If the watch is on but I set it to ignore the "Messages" app notifications, the message shows on the phone
This is pretty annoying as I do like getting notifications on the watch, but of course I don't want them to disappear from the phone. It seems like for the moment, I have to choose between one device or the other.
I opened a bug report at https://issuetracker.google.com/issues/70808796

So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs

I have the issue on Nexus 6 and Android wear also. Any solutions to keep both going?

In the Wear app on the phone check to see if "Silence phone while wearing watch" is enabled.

benmeroff said:
So I actually think I may have figured out what's happening on my end but still don't know exactly why... I had AT&T NumberSync enabled for my LG Watch Urbane 2nd Edition, and after disabling that all my text notifications persist like they used to; basically my watch now functions tethered to my phone through a traditional Android Wear connection and will only get notifications once "passed on" from my phone, versus catching the texts via the AT&T network directly with NumberSync.
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
You are a genius! Thanks. This solved my problem (although I think the underlying issue might be different since you are on AT&T).
The winning combo for me (I'm using T-Mobile with "DIGITS with Paired Data") is:
On the watch, settings --> connectivity --> cellular --> advanced --> watch shares number with phone --> calls: on, text messages: off
On the watch, settings --> apps & notifications --> app notifications --> show all --> messages --> off
Since TMo already handles having the watch SIM share my main SIM's number on the network side, there's no need to tell the watch about this. I've confirmed that the following work:
Incoming texts appear (and stay in the notifications) on the phone and watch
I can reply to texts from either device and the "from" number is correct (my main number)
I do not get duplicate notifications on the watch (the watch's messages app's notifications are disabled)
I can place a call from the watch and the correct "from" number appears on caller ID
I can receive a call placed to my main number on either the phone or the watch

Notification sounds stop working randomly - pixel XL android 8.1

So this just started a few days ago, I noticed that the notification sounds stopped working. Locking the phone stops making a sound and all notifications are silent. Watching videos and incoming calls are audible however.
A reboot fixes the issue, but it returns soon after.
I didn't install any new apps recently. Updated some, but nothing new.
Any ideas?

Same thing happened to me upon upgrading to 8.1 If I reboot it solves it for a little, but shortly afterwards no notification sounds again. Not sure if anyone has found a solution or are having the same issue?

Same exact problem here. Very annoying. I'm thinking of trying a factory reset.

If you do a factory reset let us know if it works, I've been thinking the same, if I do I'll let you know.

I thought I was the only one having this issue. Randomly comes on and off.
Sent from my [device_name] using XDA-Developers Legacy app

crazyd1721 said:
I thought I was the only one having this issue. Randomly comes on and off.
Click to expand...
Click to collapse
I checked the sound settings after updating to 8.1. All of them had changed to silent or something else you couldn't hear. I reset every sound, alarm, ringtone, notifications, etc.
I have to do this after every update. This is due to the fact, that I use the factory image to update.

So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?

You may be on to something. I use the bt with my car everyday. Noticed the same thing.
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse

notification problem
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse
After 8.1 on my pixel XL notification sounds have stopped working. I determined that it has something to do with the bluetooth. After connecting bluetooth and then turning it off that is when the problem happens. But, oddly enough, notifications sounds do work again when bluetooth is turned back on and connected....but stop again after bluetooth is turned off. A reboot fixes the problem but it happens again once bluetooth is used and turned off again. Please fix it Google.

Same for me but I only lose the Google Voice text message notification and a reboot fixes it.

It happened to me connected and not connected to Bluetooth. It would also happen to calls as well, missed some important phone calls because of it.

I am having the same problem. I'll check to see if BT connectivity is the trigger.

Same thing happening to me.. I use bluetooth daily too.

I am having the same issue. Any fixes? Has Google acknowledged?

Still happening with me. I have to reboot every few days to fix it. Very annoying.

Happening to me as well, specifically for text notifications. Sometimes the sound is triggered, sometimes it isn't.

I rebooted more than a week ago and it hasn't returned and I use a Bluetooth headset and Bluetooth in my car daily. I haven't gotten the January security patch, wondering if they slipped a fix in there?
Sent from my BTV-W09 using Tapatalk

I was having the same issue. I think it started after one of the security patches. I contacted google's support. they had me put it in safe mode and then see if it comes back. I did that, and it seemed to not break in safe mode. In theory, that means it is not a google issue, (Im sure they will play it that way) but Im not sure if it is caused by bluetooth, or something else. Anyone having the issues using a smart watch connected to it?

This is very annoying. I am still having this issue that started shortly after 8.1. Notification sounds stop working. A reboot fixes is it but the problem comes back shortly thereafter,,sometimes within 24 hours. Interestingly, the notifications still work while bluetooth is connected...not sure what to make of that. I am loathe to do a factory reset but if anyone has done it with success please let me know. Thank you.

Same thing here. I'm contacting Google regarding the issue. I've noticed a similar symptom since I've been using an android watch:
my watch gets notifications on time but my phone doesn't react. When i clear the notifications from my watch, my phone sets off multiple notifications in a row. Example: text, text, email, email, email, email, email, text, calendar. It's very annoying.
Now my phone makes no notifications. I've changed all notification sounds to full volume, I turn off bluetooth completely and my phone only vibrates for calls and doesn't make notification sounds or turn on the display as they come in.
While connected to a bluetooth device, the notifications come through that device but nothing or vibrate only on my phone.

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls

Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
*Copy/pasted from the Pixel 2 forum. Whoops!*
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.

I have noticed a similar problem that has cropped up recently - I cant make consecutive calls. If I hang up from a call and then try to make another the phone sits there. The phone button animates but doesn't do anything. If I try 20 seconds later it will sit there for about 10 seconds and then make the call. If I wait about two or so minutes it will work. Incoming calls are different.. if I am in that "period" of time, the phone will ring and if I am not in the phone app - meaning the incoming call screen pops up - I can answer it. If its a heads up incoming call I cant answer it. I must turn the screen off and then back on to get to the full screen to answer it. I am on 17.0.186697879 which I believe is the latest.

I've had the delayed calling problem for almost 2 months. The problem also includes sometimes not being able to answer a call from the notification shade when the screen was already on. Toggling airplane mode alleviates the problem temporarily.
There's a lengthy thread in the OG pixel threads with the many users with the problem. Also a lengthy thread on one of the Google support threads. Someone there suggested it had something to do with the mlb at bat app. I think that has since been debunked. I haven't found a solution yet and Google hasn't made an official acknowledgement yet.

This issue suddenly appeared on my Pixel 2 couple of days ago. Tried all the hacks and solution, but even turning off all the knobs in the phone permissions screen didn't help.
I have android 8.1.0
Build OPM1.171019.021

Notification Sounds (Call, alarm, text, etc) not working

I have had the Pixel 3 XL since they were first released and up until now have had zero issues. Last week there was a security patch and since then (not sure exactly when) my notification sounds have stopped working. They work over bluetooth, media sounds work, changing the sounds in the settings menu produces a test sound but the notifications only vibrate. Its almost as if its in silent or a do not disturb mode. I did not notice until 2 days ago as I am a heavy sleeper and usually sleep through my alarms and at work often have my phone on vibrate or low volume.
Online searches have come up with nothing more than going back to factory image to which most threads I read people reported within 30 minutes the issue resurfaced. Has anyone else seen this or have any solutions that don't involve resetting my phone. I would like to find a root cause instead of a band-aid.
Thanks in advance for any help.