My brother has a OP3T and I have a OP3 that I just bought used a few days ago, my first non-nexus phone. We have noticed on OS 4.0.3 (and now OS 4.1.0) that missed calls don't show the how long ago the call was, whereas other notifications show how many hours/minutes the event that prompted the notification occured. This is on the lock screen as well as in the normal environment - see imgur album for some screenshots. I did a few searches on google and found at least one other person experienced this but people just responded to change the settings, and we can't find any settings anywhere that would be preventing this information from being displayed.
If there is a setting that can be adjusted to fix this, where is it? If not, can anything be done about it?
Related
I'm using a custom made homescreen. I'm using the missed calls plug in and I have it set up to be visible all the time to display:
"0 Missed Call(s)"
Yesterday I started experiencing some problems with it. But I don't think it has to do with the homescreen. Since I have tried others and I experience the same issue. Here is my problem:
Every time I turn off my phone and turned back on. The number that indicates how many missing calls I have, just goes away. Instead of reading: "0 Missed Call(s)" it reads " Missed Call(s)"
Now, when somebody calls me and I don't pick up the phone. That number comes back and my phone indicates how many missed calls I have, for example: "2 Missed Call(s)." Also, If I access the "Call History" the indicator comes back. At least I know when I get a missed call. It's just very annoying to be doing that all the time I turn on my phone.
I've tried to soft reset my phone a couple of times but that didn't help. I haven't made any changes to my phone recently. A while ago I was having this problem. But I ended up removing MyFavs from the startup folder and that fixed the problem. Now I don't now what the problem is.
I would like to know if any of you knows how to fix this problem without hard reseting my phone. And if there's no way. Would any body please tell me if there is a way to backup all the text-messages (without using dashwire.com).
Thank you!
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.
Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
mblancoc said:
Hi there, I was wondering if anyone might have any suggestions on how I could disable the Android Marshmallow doze/deep sleep mode that is default on new devices to save battery. I have a OnePlus 3 and have made every effort to check that all my notifications for calendar, whatsapp, emailing, etc. are set to both vibrate and make a sound, disabled all battery optimization features for apps, tried using screenlock wake apps to avoid missing notifications, and more. However, I am still unable to get notifications for whatsapp, emails, calendar reminders and events once my screen goes to sleep or I lock then phone and it's idle (so after about 15-30 minutes of it sleeping), but calls and texts seem to come through fine (or at least I haven't noticed these being an issue as much). This is a HUGE inconvenience, as my main reason to have a smartphone is so I can check emails, calendar events and such right as I receive them, and not only when I wake up my screen (which then bombards me with all my previous missed notifications from hours before). I have a feeling this is an android 6.0 issue and not due to the OnePlus 3, because it's been reported in other sites and by people with phones also using either this OS or lollipop. My older Samsung galaxy S4 running kitkat never had these problems, and at this point I'm very keen on going back if I can't get my new phone (or this OS, as I predict) to notify me right away even when my screen is locked and phone asleep (I can't always remember to check it especially if I'm busy at work). I am willing to root the phone and change settings if that's an option, but I would please like to see if you guys have any other suggestions for allowing my phone to receive notifications right away even when in sleep mode/idle/dozing. Thank you for your time in advance. Oh last thing, I also posted this question in other forums because I am honestly quite desperate to find out what I can do to resolve this issue, so I'm sorry if that's an inconvenience...
Click to expand...
Click to collapse
Here is over 900 posts on this issue for your reading pleasure.
https://forums.oneplus.net/threads/push-notification-issues.451149/
Problem solved
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
mblancoc said:
Oneplus just released a new oxygen OS update which takes care of the notification issues. But to resolve this before this OTA came out I rooted and disabled the doze mode with dumpsys deviceidle. So all is good now!
Click to expand...
Click to collapse
Problem was NOT SOLVED with 3.2.1 OTA you still need to disable Doze in order to fix it.
Sent from my SM-T810 using XDA-Developers mobile app
Since Wileyfox migrated from CyanogenMod to plain Android they have allowed a really annoying bug to creep in: SMS alerts are played at full volume in the earpiece during an active voice call.
Apart from being super annoying it might be dangerous in some cases as depending on the volume of the chosen tone, it might damage someones hearing.
Our device is running the stock 7.1.2 ROM which is the first release in which we noticed it.
In previous release, and almost every other device we can think of, the SMS alert during a voice call is either a simple pip or nothing at all.
Are you affected by this too? Have you found a solution (apart from a custom ROM or new phone)?
There seems no way around this in the phone setup and it seems to us that WF need to fix it. If you agree then please take a look at this FB post and vote it up - it may be we can get an update issued:-
https://www.facebook.com/officialwileyfox/posts/1872330073078309
Thanks for reading.
SOLUTION: SMS Alert during voicecall.
For anyone interested we have found a solution: Replace the stock messaging app with Google Messages.
This can be downloaded from Play Store here:-
Google Messages
It seems the stock messaging app somehow gets around or ignores the "Override Do Not Disturb" setting as shown in the attached screenshot.
Hope this helps. :good:
Long story short, I changed my text message sound to Pulse Beam as soon as I got the Z Fold3 in August. I cracked it, and got a replacement mailed to me in early February. I transferred everything, and it was pretty much a success (for the most part).
So last night I wanted to change Pulse Beam to something else. I went to my Messages, Settings, etc. and changed it to something else (let's use Nebula as an example). Well, I hear the Nebula sound when I press it, and see that it is set. I exit out, and when someone texts me, it's still Pulse Beam. I go back in Settings and see that it's still on Nebula. I have tried about 10 different sounds (even from Zedge) and while it appears to be working (let's me set whatever), it's still the same old Pulse Beam when someone texts me.
Now, I can still set individual text messages and that will work (say I set Joe to Nebula, it will be the Nebula sound when he texts me), but that is a pain. I don't want to set 200+ new contacts.
I don't know what happens if someone not in my contacts texts me, but I'll try and find out later today at work. Anyway, how weird is this? Any ideas?
Zap! said:
Long story short, I changed my text message sound to Pulse Beam as soon as I got the Z Fold3 in August. I cracked it, and got a replacement mailed to me in early February. I transferred everything, and it was pretty much a success (for the most part).
So last night I wanted to change Pulse Beam to something else. I went to my Messages, Settings, etc. and changed it to something else (let's use Nebula as an example). Well, I hear the Nebula sound when I press it, and see that it is set. I exit out, and when someone texts me, it's still Pulse Beam. I go back in Settings and see that it's still on Nebula. I have tried about 10 different sounds (even from Zedge) and while it appears to be working (let's me set whatever), it's still the same old Pulse Beam when someone texts me.
Now, I can still set individual text messages and that will work (say I set Joe to Nebula, it will be the Nebula sound when he texts me), but that is a pain. I don't want to set 200+ new contacts.
I don't know what happens if someone not in my contacts texts me, but I'll try and find out later today at work. Anyway, how weird is this? Any ideas?
Click to expand...
Click to collapse
Have you tried clearing data and cache on the message app?
m_w_clarke said:
Have you tried clearing data and cache on the message app?
Click to expand...
Click to collapse
Edit: It's all good now. I was changing Message General Notifications instead of New Messages. Always the easy fixes lol.
Yes Android has changed notification sounds so the are linked to notification events instead of settings inside the app.