Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you
BFSilva said:
Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you
Click to expand...
Click to collapse
I am having the same issue! This update has been a headache so far haha
It's been like this ever since I jumped on the first beta. Surprised it's still broken....well.....not really.
Aerro47 said:
I am having the same issue! This update has been a headache so far haha
Click to expand...
Click to collapse
AndrasLOHF said:
It's been like this ever since I jumped on the first beta. Surprised it's still broken....well.....not really.
Click to expand...
Click to collapse
Thank You very much for your answers!
Are you on Android 9.0 final release?
Have you guys tried to factory reset?
Thanks
Yeah, it hasn't worked for a while. I've been using P since beta 2 and I factory reset every single beta update including the now released final Pie.
Don't bother factory reseting, it won't fix it.
Mr Patchy Patch said:
Yeah, it hasn't worked for a while. I've been using P since beta 2 and I factory reset every single beta update including the now released final Pie.
Don't bother factory reseting, it won't fix it.
Click to expand...
Click to collapse
Thanks man! I was getting worried it might be some kind of bug during the update process, and I was on the verge of factory reseting the phone!
:good:
Have you noticed any battery improvements since the update?
Since Oreo 8.1.0 that I've noticed that the battery doesn't last as long. In my case I've noticed a 25 to 30% decrease in battery life!
BFSilva said:
Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you
Click to expand...
Click to collapse
Really mines works...I can't get it to turn off
plokm said:
Really mines works...I can't get it to turn off
Click to expand...
Click to collapse
Screw you.....joking lol
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
BFSilva said:
Thanks man! I was getting worried it might be some kind of bug during the update process, and I was on the verge of factory reseting the phone!
:good:
Have you noticed any battery improvements since the update?
Since Oreo 8.1.0 that I've noticed that the battery doesn't last as long. In my case I've noticed a 25 to 30% decrease in battery life!
Click to expand...
Click to collapse
I haven't noticed battery improvements for any phone that ever claimed better battery. I always have to top up every phone I've had after work. I'm a heavy user tho, but no phone has ever given me "amazing" battery. This phone is no different. I've had A LOT of different phones too.
I'm experiencing the same issue. Also experiencing double notification sounds for some incoming messages. Mostly annoying but would like to see a fix.
Messages version: 3.4.048, last updated 8/7/18
I've been running the beta from the start without this problem on my Pixel XL. Just updated my wife's Pixel XL and she reported the problem to me. It wasn't until I enabled and disabled this feature that I had this problem. Now I can't turn it off. It seemed to start after installing the Digital Wellbeing Beta. Wouldn't that be ironic.
I got an update for Messages last night and now I'm finally seeing suggested replies in the notification shade. Also...now the notification sound when sending is working but it's not using the 'swoosh' type sound and instead is using the sound I have picked when receiving messages.
Yeah I just got the pie update on my phone (Pixel 2 XL) and I can't seem turn off outgoing notifications. I went to settings and clicked that setting off. It still will not turn off. I never even knew my phone had this function until this update but it is driving me crazy.
Just switched to Pie on my Pixel 2 XL two days ago and got the messages update as well.
I have the same issue as a few others have mentioned, I now have an outgoing sound when previously I did not and there is no way to turn it off. The switch in Messages to turn it on/off does nothing and it is the same sound as the 'received' message notification.
Well I got it to stop but can't get it to turn back on. I went into settings -> apps -> messages (app) -> storage and cleared both the storage and cache. Now it no longer sends out going message sounds. The problem is I can't turn it on or off. Lucky for me I just want it off.
Silly question: does clearing cache and storage delete all of your messages? This happened immediately after I upgraded my Pixel 2 XL to Pie....like everyone else.
Sadly it was only a temp fix. Today the outgoing sound came back.
jwjames83 said:
Silly question: does clearing cache and storage delete all of your messages? This happened immediately after I upgraded my Pixel 2 XL to Pie....like everyone else.
Click to expand...
Click to collapse
No it doesn't. They will all reload. Done this numerous times.
i can not get mine to turn off
This is getting old!
This is getting really really old!
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
I wonder if a replacement SMS app would have the same issue?
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
I just installed a 3rd party messaging app. No outgoing notification issue or double notifications on incoming messages.
UserDave said:
This is getting really really old!
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
I wonder if a replacement SMS app would have the same issue?
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
I just installed a 3rd party messaging app. No outgoing notification issue or double notifications on incoming messages.
Click to expand...
Click to collapse
Textra works great. With outgoing sound :good:
Related
Hi friends,
when I turn on my huawei watch it doesn't receive notifications from phone but it is connected.
Sometimes I resolve with the phone restart.
Have you some ideas?
Many thanks.
Same here. Need to reboot watch to get them again.
Mike
Is it a problem of the watch?
Dang just came here for same issue. Only way to get it back is reset watch. It's happened 3-4 times. Not sure what causes it. My watch was in theater mode before I go to sleep, maybe being in theater mode to long causes it,? Just reset phone yesterday, today no notifications......dang everything was perfect on this watch. Now this....bummer.
Sent from my Nexus 6P using XDA-Developers mobile app
---------- Post added at 07:01 PM ---------- Previous post was at 06:52 PM ----------
OK just put watch into airplane mode then took it off. Started working again. First time. Usually that doesn't fix it.
Sent from my Nexus 6P using XDA-Developers mobile app
After reset watch same issue
Ideas?
Hello, i find out that if you set in android wear SILENCE PHONE WHILE WEARING WATCH to on, every notifications are working. If its off then no notifications are on the watch. I am on ANDROID WEAR 2.0 / 3
bricca said:
After reset watch same issue
Ideas?
Click to expand...
Click to collapse
We see that you have tried a factory reset, yet your problem with your Huawei smartwatch persists. We suggest you call Huawei support at 1-888-548-2934 for further assistance. (SP)
Problem showed up after google play services update. You need to install older version to have it working again.
Mike
Hi friends, since few days my smartwatch is working fine.
What do you think?
Google fixed a bug.
bricca said:
Hi friends, since few days my smartwatch is working fine.
What do you think?
Click to expand...
Click to collapse
http://forum.xda-developers.com/huawei-watch/general/bad-battery-life-read-factory-reset-t3474948
---------- Post added at 04:18 PM ---------- Previous post was at 04:11 PM ----------
sp5it said:
Problem showed up after google play services update. You need to install older version to have it working again.
Mike
Click to expand...
Click to collapse
this works, but temporarily ... Google Play Services updates invisibly sneak in and there's no way to block them ... you can install older version, but a few days or hours later the update will find you again ... you know when they sneak in because battery life drops and you get lots of connection hiccups until they are done AND you've rebooted your phone+watch a few times for the updates to settle in comfortably with everything their roots tap into. (warning: interrupting this process with uninstalls or factory resets starts the process over = ugly cycle and unhappy owner)
expect your phone or watch (or both) to 'have sick days' after flashing AND every month or so when Google Play Services gets updated on watch or phone (or both)
Huawei connection problem
I had the same issue, but i think It is related with the face i was using, uninstalling any 3rd party face apps and only using the Factory ones solved the problem for me.
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
angka8 said:
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
Click to expand...
Click to collapse
I found it wasn't great in the dark, I assume it uses the light sensor to determine if in pocket etc
Sent from my Google Pixel XL using XDA Labs
I have noticed the same thing. It isn't 100% consistent.
FWIW: Mine seems to be very consistent if I triple tap. Perhaps the first tap wakes it up if it's in a deep sleep?
Hopefully fixed in the December update.
JAYNO20 said:
Hopefully fixed in the December update.
Click to expand...
Click to collapse
No change for me.
cam30era said:
No change for me.
Click to expand...
Click to collapse
Has been working consistently for me so far. Will post back if that changes.
---------- Post added at 03:07 PM ---------- Previous post was at 02:26 PM ----------
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
JAYNO20 said:
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
Click to expand...
Click to collapse
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
cam30era said:
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
Click to expand...
Click to collapse
Makes no sense. I'm glad we are seeing the same issues though, at least it's consistent there
I'm having the same exact issues. Tap not working consistently and sometimes the lift doesn't work either. Hmm.
It's worth noting I had the same issues with the Elemental kernel before this ddtw option was available. The ddtw option was just as inconsistent for me.
Neither working at all for me.
Update: Seems to be working fine now.
if you have a screen protector that might cause the issue
if it still doesnt work without screen protector reflash the factory image
The update seems to fix the issue.
Update: the issue still there. But much less frequent
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
I have noticed that is works better if the screen is locked. So if your phone doesn't lock for 5 or so minutes, it may not work until after that time. Try to set your phone to "Power button instantly locks" and then try it. Mine was not working at all, but when I locked the device sooner, it started to work consistantly. Might not help you, but fixed it for me.
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
GCbard said:
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
Click to expand...
Click to collapse
It's an option with the newer OTA.
clockcycle said:
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
It's an option with the newer OTA.
Click to expand...
Click to collapse
Where is this option located? I'm on the November update. Is this with the December update?
GCbard said:
Where is this option located? I'm on the November update. Is this with the December update?
Click to expand...
Click to collapse
December OTA. Same location as other Moves/ gestures.
FWIW: what I've noticed is that if my phone is sitting on something, DTTW works 100% of the time. If I have it in my hand, it's very sporadic.
Running total stuck with latest updates. Anyways, whenever I end a call I notice a loud beep which sounds like its coming from speaker phone but the phone is not on speaker. Also, callers on the other end are always like "huh" when I talk. Some say it sounds muffled, but not always.
mrwicked said:
Running total stuck with latest updates. Anyways, whenever I end a call I notice a loud beep which sounds like its coming from speaker phone but the phone is not on speaker. Also, callers on the other end are always like "huh" when I talk. Some say it sounds muffled, but not always.
Click to expand...
Click to collapse
Are you using any kind of screen protector or case that could be interfering with the microphone? If not (I know people don't like to hear this) have you tried a factory reset? Whenever things start acting wonky on your phone a factory reset should always be near the top of the things that you try. It's easy for drivers to get corrupted over time and an accumulation of updates and a factory reset ends up solving a lot of issues, even if it is inconvenient.
I to get that beep when i end my call. I am on the latest DP4.
jhs39 said:
Are you using any kind of screen protector or case that could be interfering with the microphone? If not (I know people don't like to hear this) have you tried a factory reset? Whenever things start acting wonky on your phone a factory reset should always be near the top of the things that you try. It's easy for drivers to get corrupted over time and an accumulation of updates and a factory reset ends up solving a lot of issues, even if it is inconvenient.
Click to expand...
Click to collapse
Using a glass protector and a peel case that is super thin. I once had the phone rooted and running a custom rom. Was having troubles with people always saying "huh". I bought the HTC u11 and set this pixel xl back to stock to sell it. Decided the u11 wasn't for me and took it back and started using the pixel and took the latest update from a factory reset. Now getting the loud beep!
Same here. DP4
Yes this is happening to everyone who is using Snapchat. Just go to permission settings in Snapchat and untick the telephone / phone permissions. It will get fixed. Weird but just give a try it will work. Or uninstall Snapchat. Please reply if this helps you.
---------- Post added at 06:59 PM ---------- Previous post was at 06:47 PM ----------
Yes this is happening to everyone who is using Snapchat. Just go to permission settings in Snapchat and untick the telephone / phone permissions. It will get fixed. Weird but just give a try it will work. Or uninstall Snapchat
Can confirm. This happens on my stock Pixel running 7.1.2. It's like the phone switches to speakerphone for the last .25 seconds of the end call beep.
EDIT:
Yes this is happening to everyone who is using Snapchat. Just go to permission settings in Snapchat and untick the telephone / phone permissions. It will get fixed. Weird but just give a try it will work. Or uninstall Snapchat
Click to expand...
Click to collapse
Can also confirm that the fix stated above works ^^
rawalgaonkar7 said:
Yes this is happening to everyone who is using Snapchat. Just go to permission settings in Snapchat and untick the telephone / phone permissions. It will get fixed. Weird but just give a try it will work. Or uninstall Snapchat. Please reply if this helps you.
---------- Post added at 06:59 PM ---------- Previous post was at 06:47 PM ----------
Yes this is happening to everyone who is using Snapchat. Just go to permission settings in Snapchat and untick the telephone / phone permissions. It will get fixed. Weird but just give a try it will work. Or uninstall Snapchat
Click to expand...
Click to collapse
Thanks for this. I uninstalled Snapchat as I could not find the setting you are referring to? The uninstall did take the loud beep away. I installed it back and beep is back lol..just a test. But I looked through permissions and seen nothing with a tick for phone?
Sent from my Pixel XL using Tapatalk
mrwicked said:
Thanks for this. I uninstalled Snapchat as I could not find the setting you are referring to? The uninstall did take the loud beep away. I installed it back and beep is back lol..just a test. But I looked through permissions and seen nothing with a tick for phone?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Settings-apps-snapchat-permissions> phone or telephone
rawalgaonkar7 said:
Settings-apps-snapchat-permissions> phone or telephone
Click to expand...
Click to collapse
Yeah I figured out lol. For some reason I was looking in the snapchat app settings. But yeah I can confirm this fixed the loud beep. Thanks!
Like everybody has realised this is not a problem in the phone, it's because of the Snapchat update, so best solution is to disable the 'Telephone' permissions for the Snapchat app.
Unfortunately, the beep came back and the phone permission is unchecked. Must be just snapchat. I'm going uninstall it for a few days and see what happens!
Pixel XL here, unchecked Telephone permission for Snapchat took the beep away for me. It hasn't returned ...yet
The beep has returned for me, I'm thinking it's because there may have been an update. The telephone permission was still unchecked so I've uninstalled Snapchat and the beep has disappeared again.
I haven`t Snapchat, but i have f***ing beep on my phone.
I've got the beep on original XL and now XL2. Contacted Google and they are going to RMA the XL2. I guess we will see if new one still has beep. Google customer service is clueless. The first girl said they are working on it and fix will be in next update, I asked her where she is getting her info. from and she couldn't come up with anything. BTW never had Snapchat so that's not the issue with my phones.
Hey guys on a Pixel 2 here and having this issue. It's extremely annoying. Uninstalling Snapchat did nothing for me.
I had this issue when i was on att. Had to call them and tell them turn off volte. Then the beep went away. Just my two cents. Att doesn't support volte on pixels so something was happening between the device and their network.
bartolo5 said:
Hey guys on a Pixel 2 here and having this issue. It's extremely annoying. Uninstalling Snapchat did nothing for me.
Click to expand...
Click to collapse
Same. This is very annoying.
bartolo5 said:
Hey guys on a Pixel 2 here and having this issue. It's extremely annoying. Uninstalling Snapchat did nothing for me.
Click to expand...
Click to collapse
Try posting in the Pixel 2 forum.
With my phone set to silent, using Find My Device / Android Device Manager from another phone or PC, is unable to remotely force a ring of the phone, rendering this functionality useless. This is a real problem, and I wanted to make sure this issue wasn't just isolated to me.
Many thanks in advance!
Zwitterion said:
With my phone set to silent, using Find My Device / Android Device Manager from another phone or PC, is unable to remotely force a ring of the phone, rendering this functionality useless. This is a real problem, and I wanted to make sure this issue wasn't just isolated to me.
Many thanks in advance!
Click to expand...
Click to collapse
Just tested. Set phone to silent (No vibrate. Ring volume off). Executed find my device from PC. Selected Play Sound. Phone started ringing loudly immediately...
Google Pixel XL. Verizon. Android 9.0. Stock Rom. Unlocked. Rooted with Magisk 16.7 (1671) / (Magisk Manager 5.8.3)
To clarify, you set it with the Do Not Disturb function? That's where I'm having the issue.
Zwitterion said:
To clarify, you set it with the Do Not Disturb function? That's where I'm having the issue.
Click to expand...
Click to collapse
Nope - sure didn't. I'll retest that scenario now...stay tuned.
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
sb1893 said:
Nope - sure didn't. I'll retest that scenario now...stay tuned.
Click to expand...
Click to collapse
Just retested and my phone immediately started ringing. This time I used the Do Not Disturb function to silence the phone. (Verified that setting worked by calling the phone and no vibration or ring.) But the phone immediately rang on command via Android Device Manager / find my phone.
Also - probably not relevant but I upgraded to September security release this morning as well. My first test was on the initial Pie (August) release. DND test was on September release.
Many thanks for the effort and detailed response. Glad to hear it's just me, and probably a glitch that the September release hopefully captures.
When I got my device, the vibration was strong. Now I have no vibration whatsoever. All settings are good. I can't even get haptic feedback. I searched in Google and saw a couple others with this problem. Sounds like a hardware issue to me. Anyone else experiencing this yet? SM-N975F/DS
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
pete4k said:
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
Click to expand...
Click to collapse
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
awakener777 said:
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Click to expand...
Click to collapse
You mention "hearing" about many more cases... Where?
big_ipaq said:
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
You mention "hearing" about many more cases... Where?
Click to expand...
Click to collapse
There's a lot of you look through here
https://us.community.samsung.com/t5/Note10/bd-p/Note10
Any answers?
So my note 10+ started doing this this morning. I do the phone test and it vibrates, but is weaker. Keyboard vibrate doesn't work. Notification vibrate doesn't work, nothing else vibrates. Not sure what is going on.
Edit: looks like something turned my vibration sensitivity way down. Working now!
No problem on my N975F/DS with vibration after official Android 10 update. Vibration test, keyboard feedback, vibrate on phone call also work as before...
@OnnoJ same problem, after update, vibration stop working... altough it could be that it didnt work before i am not 100% sure