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

No ringtone with incoming calls

Strange problem:
After i booted the Oneplus3 (with OxygenOS 3.0.2) i get no ringtone when someone is calling me.
After deep research i found out that moving the "silent-slider" up and down again (forcing the OPO3 to switch from "all" to "silent" back to "all" again), ringtones do sound again.
Anyone else?

Ah, found the solution on a different (oneplus) forum.
Its a bug.
Solution:
Put notification-slider to: "Priority only"
Go to settings -> slidersettings.
Go to Priority-settings
Change Messages to "from everyone"
Change Calls to "from everyone".
Put slider back to "all"
Strange bug. But this should solve it, for now that is.

Ringtone issue
I have just the same problem and contacted Oneplus. They told me to perform a hard reset, although I told them moving the ¨silent slider¨ up en down solved the problem, but only for a short period of time. So I did as they told me, which of course took me a lot of time, and after a few hours again there was no ringtone for incoming call. So I have send them another mail on friday and am waiting for a reply.
After moving the ¨silent slide¨ a few more times on fridaynight, the problem did not reoccur over the weekend, but I just don´t trust the phone in doing what it should do: ring when somebody is calling me
QUOTE=stoerebink;67451532]Strange problem:
After i booted the Oneplus3 (with OxygenOS 3.0.2) i get no ringtone when someone is calling me.
After deep research i found out that moving the "silent-slider" up and down again (forcing the OPO3 to switch from "all" to "silent" back to "all" again), ringtones do sound again.
Anyone else?[/QUOTE]

Im. said:
I have just the same problem and contacted Oneplus. They told me to perform a hard reset, although I told them moving the ¨silent slider¨ up en down solved the problem, but only for a short period of time. So I did as they told me, which of course took me a lot of time, and after a few hours again there was no ringtone for incoming call. So I have send them another mail on friday and am waiting for a reply.
After moving the ¨silent slide¨ a few more times on fridaynight, the problem did not reoccur over the weekend, but I just don´t trust the phone in doing what it should do: ring when somebody is calling me
QUOTE=stoerebink;67451532]Strange problem:
After i booted the Oneplus3 (with OxygenOS 3.0.2) i get no ringtone when someone is calling me.
After deep research i found out that moving the "silent-slider" up and down again (forcing the OPO3 to switch from "all" to "silent" back to "all" again), ringtones do sound again.
Anyone else?
Click to expand...
Click to collapse
The workaround @stoerebink has posted should work. Please try it out. I had a chat with a Support staff who mentioned that the fix is coming in next update (probably 3.1.4).

I take a deep bow. So much honor from my simple discovery.
Thank you, thank you.
BTW: I use 3.1.3 (the beta of the forthcoming 3.1.4) some days now. I'll let you know if the problem is gone. Haven't had it yet, which is hopegiving.

I have to say thank you as well. Your solution has made the ringtone sound ever since.
Now slowly I start to think the oneplus 3 is maybe not so bad after all
stoerebink said:
I take a deep bow. So much honor from my simple discovery.
Thank you, thank you.
BTW: I use 3.1.3 (the beta of the forthcoming 3.1.4) some days now. I'll let you know if the problem is gone. Haven't had it yet, which is hopegiving.
Click to expand...
Click to collapse

No ring tone after alert slider tiggle
Problem still persists on OOS 3.2.1.. Come on OnePlus.. Missing important calls here.. Please fix alert slider bugs

flybiker said:
Problem still persists on OOS 3.2.1.. Come on OnePlus.. Missing important calls here.. Please fix alert slider bugs
Click to expand...
Click to collapse
Same here. I was about to post a thread about this. I am on 3.2.1 and I keep missing calls and incoming texts because the notification sounds just randomly stop working. Switching to "Priority Notifications" and back to "All Notifications" solves the problem for a little while but over time the issue comes right back. I've also noticed that occasionally I'll get the "Priority Notifications" notification next to the cell signal indicator in the status bar, even when the slider is set to "All Notifications".
It's quite annoying.

No ring tone after alert slider tiggle
I too face this issue from time to time (on 3.2.1). At times if the Alert Slider toggle doesn't work, post making changes suggested by stoerebink, and toggling the alert slider between the three settings, I reboot the phone, which seems to temporarily solve the issue.
Hope Oneplus comes up with a fix for this soon.

In my case all sound gets disabled (media player, notifications, alarm, ring tone). Haven't tried the slider trick..usually reboot the phone, but it's getting on my last nerve...not a fun feeling going to bed, not knowing if the alarm will wake me up for work.

Now people at xda have started to talk about bugs in OP3...these have been discussed numerously in oneolus forums but the oneplus team is not doing anything about these issues.

Model A3003. OS version 3.2.8;latest version updated yday. Ring vol has become silent. Done reboot, changed priority setting to anyone for calls n messages, changed ringtone, tried every single thing. I changed the settings to vibrate for calls. Even that doesn't work.

nexus 5x ringtone and notification tone not coming

i have bought nexus 5x 3 months back before android 7.0 update my phone was working fine not facing any issue. but after upgrading to 7.0 my phone faces an issue that some time ringtone and any notification sound or tone won't come, Vibration is working fine. I hav to restart my phone every time to resolve this issue. Now is this due to some bug or due to latest upgrade...please help...what can be cone to resolve this.

Same here ... I cant find solution ....

Okay so my sister has the same phone as me which is the nexus 5x, yesterday she told me that she won't get notification sounds when she received texts and I took her phone and looked around. What I found was that for some contacts in the messenger, when you go to 'people and option' for a specific contact and try to change the notification tone for that contact, I saw that it was set to 'default notification tone' and when I clicked on it, it had no sound. So I switched it to a different one like 'Ariel' and then I texted her phone and she got a notification with sound. Try this, that just might fix it for you. It did for her, although I didn't restart her phone or anything to try to fix it that way.

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

Question Can someone help me with some Do Not Disturb issues?

Lately I've never remembered to post and ask, surely will be a lot easier than endlessly thumbing through the phone to try and find the right settings. Hoping someone here may have been through this recently and has it fresh on their mind.
With my alarm set, it does activate audibly the way it should while Do Not Disturb is active. However, the screen remains on the dimmed Always On screen. I guess technically speaking, the alarm does not come on top when in Do Not Disturb mode.
I have starred contacts which are allowed to ring through my Do Not Disturb, one of which is my work. When I take a phone call, I can see who is calling me, but have to unlock the phone and sometimes bring the phone app up before I can answer. The actual answer button is not shown on the display.
I guess the most critical is needing help with #2. It might sound petty, but when you are in deep sleep and work calls you at 3am and you miss their call........its rather frustrating on both ends. If I didn't have self-control I would have snapped a few phones in half already.
FWIW, this was prevalent on my S20 Ultra as well (G988U), and my current device is the S20 Ultra (S908U).
Any help or suggestions are much appreciated!

not sure if this will work, but try adding "clock" or whichever alarm app you are using as the Exceptions to the DND.
As for the contacts, try to reproduce it by purposefully starting the DND and have someone call you... if the issue is reproduced, then report it to samsung members app > get help > error report asap so that samsung engineers can look into why you are not getting the notification for that caller.

So I've tried everything suggested so far. I even just recently wiped my phone, and paid close attention to this detail with DND. Eveb freshly wiped, it is still not working as it should (or I should say, as I want it to).
Bumping again in hopes someone else might see it now and know where I need to go. Thanks in advance!

Currently using One UI Beta 5 on my S22.
I have issues with Modes & Routines, specifically the driving mode.
Even after turning the "driving mode" off / deleting it, while in transit the mode pops back and enables on its own.