Develop Bugs

[Q] random calls...anyone else have this issue ?

I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?

Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk

Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.

Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?

Moto 360 does not notify incoming calls

Hi
My moto 360 (1st gen) does not notify incoming calls since yesterday, but notifies other notifications perfectly.
Whats wrong?

First step try rebooting your watch and phone, see if that sorts it.
Have you changed any settings since yesterday, or upgraded to Marshmallow? I found that Marshmallow and more specifically Doze really messed with notifications on my watch, in the end I had to switch off Doze to fix the issues.
If all that fails do a factory reset on your watch.

Zammo76 said:
First step try rebooting your watch and phone, see if that sorts it.
Have you changed any settings since yesterday, or upgraded to Marshmallow? I found that Marshmallow and more specifically Doze really messed with notifications on my watch, in the end I had to switch off Doze to fix the issues.
If all that fails do a factory reset on your watch.
Click to expand...
Click to collapse
I'm having the same problems as well following update to Marshmallow (Moto 360 1st Gen). I've already restarted watch and phone with no success. On a side note I note that there is no longer an option to restart on the watch only power off (am I missing something here?) Similarly not seeing the factory reset option either. You mention that you had to switch off Doze to fix the issues. Sorry if I sound naive, but I'm not seeing how to do that either. My phone is a Galaxy S3 on Android 4.4 which obviously doesn't have dose so I'm not familiar with that feature otherwise. Any help would be appreciated as incoming phone call notification is one of the 'must have' features in a smart watch for me.
Regards.

Doze is part of the Marshmallow update, on phones. Its conserves battery by putting applications into sleep mode, which basically stops them being able to communicate with the phone unless you authorize it or the phone has been woken up. For me this was stopping a lot of Android Wear functions from behaving properly, namely call notifications.
If your S3 isn't running Marshmallow my fix, doesn't really apply to you.
Restart and Factory reset are under Settings on the watch.
If your still having issues email Motorola customer service, I've found them to be quite helpful.

Mine started doing that BEFORE the Marshmallow update. It would ring AFTER I got the call.

I have same problem (the calls appears in the watch as "unknown caller")
The phone operator (TIM) send number info of local calls in this format: XXXXX-XXXX
I already modify my phonebook, I used all possible number formats...
Moto Maxx: 5.0.2
Moto 360 1gen: 6.0.1
Android Wear: Latest
Brazil

sforde said:
On a side note I note that there is no longer an option to restart on the watch only power off (am I missing something here?) Similarly not seeing the factory reset option either.
Click to expand...
Click to collapse
Zammo76 said:
Restart and Factory reset are under Settings on the watch..
Click to expand...
Click to collapse
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.

Zammo76 said:
Doze is part of the Marshmallow update, on phones. Its conserves battery by putting applications into sleep mode, which basically stops them being able to communicate with the phone unless you authorize it or the phone has been woken up. For me this was stopping a lot of Android Wear functions from behaving properly, namely call notifications.
If your S3 isn't running Marshmallow my fix, doesn't really apply to you.
Restart and Factory reset are under Settings on the watch.
If your still having issues email Motorola customer service, I've found them to be quite helpful.
Click to expand...
Click to collapse
alryder said:
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.
Click to expand...
Click to collapse
Thanks Zammo for the info.
Calls started to appear on the watch once more after a couple of days. Didn't do anything else, so I can't say why.
May try suggestion to unpair phone soon. Phone itself is taking very long to respond to basic operations and battery life is getting pathetic. Going to do a factory reset, clear cache etc (may even try another ROM).

alryder said:
I have the same issue, after the 6.0.1 update I no longer have a "Restart" or a "Factory reset" option under settings. It was suggested in another thread that using the "Unpair with phone" option will perform a factory reset. I'm going to try that tomorrow.
Click to expand...
Click to collapse
Just to confirm, using the "Unpair with phone" option does perform a factory reset.

Hi alryder,
Just wanna know "Unpair with phone" fix the call notification issue you had?

Weird Phone app glitch with the keypad

I'm getting a weird stock Phone app glitch with the keypad when on a call. If I dial a number and select keypad, the animation for the keypad coming up is nice and smooth. If, however, I put my ear next to the earpiece for the proximity sensor to turn off the display, move my head away so the display turns on again, and select the keypad again, the animation becomes much slower and looks choppy. I tried to replicate this on my wife's Pixel 3 and her phone doesn't do it. I cleared Phone app storage data and cache, restarted my phone, and I can still reproduce the bug. I'm on the latest March OTA. Would you guys please test it and see if you're able to reproduce the same weird glitch?

is your wifes phone also on themarch OTA?
3 or 3XL?

virtyx said:
is your wifes phone also on themarch OTA?
3 or 3XL?
Click to expand...
Click to collapse
Her phone is still on the February update and it's the Pixel 3. After further testing, it only happens after the proximity sensor is used to turn the display off and then back on. If I use the power button to turn the display off and then back on it doesn't happen. I also tested in Safe Mode and I can still replicate it. I sent feedback to Google. Not sure if anyone will care but it's a very unsual glitch.

I switched to Android Q beta 1 and it was still doing it. I ended up having to wipe everything to go back to Android P, and I didn't restore from the cloud. To my surprise it wasn't doing it, but now after some time passed, it's back to acting up. I'm on the latest March OTA. Would you guys please test it and see if you're able to reproduce the same weird glitch?
VIDEO LINK: https://photos.app.goo.gl/9U4WQXnLdHG1RSke8

System UI Not Responding

Does anyone else get intermittent freezing where the entire phone becomes unresponsive for like 30 seconds? It's not affecting any specific apps, but it does seem to happen often when I'm pressing the home or back button on the navigation bar. Also happens when pressing send in messaging apps. Sometimes it results in ANR, other times it will unfreeze without giving a crash dialog.
Could it possibly be tied to battery optimization and putting apps in deep sleep? I've had this problem on both my Note 10+ and S20 Ultra. Did not have an issue on my Note 8.
Steps taken to remedy situation (but did not fix the problem):
Factory reset
Clear partition cache
Running phone in safe mode (worked, but did not help with determining exact problem)
Setting battery settings to High Performance
Wiping app caches
Stopped using SwiftKey (but still seeing crashes on Samsung Keyboard and Gboard)
Unchecked "Put unused apps to sleep"
Unchecked "Adaptive Battery" setting

YES. This has been happening to me for 6 months now and its trying me crazy. On my ATT Note 20 Ultra. Even after factory reset it eventually came back. I feel like its a hardware problem to be honest because it seems to happy when the CPU or Memory is overloaded or working hard. For example, 2 times I can make it happen is when I update 10+ apps from the playstore and try to do anything else, or when I first turn on my phone and its launching all the startup apps.
Not sure what to do, maybe get a replacement from Samsung or ATT? Just hate having to format yet again.
On thing that did help is yesterday I bought the cloud version of Samsung Package Disabler (i bought these thing like 4 times over the years but thats another story) and I disabled 50 apps that I dont need to run but I dont like the hassle of uninstalling and then reinstalling and the passwords etc. Anyways it def has lessened the issue. Which again is why I think its a hardware problem. Since I lessened the apps running in the background it has lessened the issue.
Anyways if you have any updates on your end please let me know, thanks!

Redmi note 8 notification sound problem

Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.

Hamza_note8 said:
Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.
Click to expand...
Click to collapse
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.

Pavello said:
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.
Click to expand...
Click to collapse
Hello,
Thanks for you response. I've already done what you did sggest to me but still the samething always late notification sound.
It's not added to game turbo i don't even use it and it's disabled. Google play services and framework don't have any kind of restrictions whatsoever. I don't want turn off miui optimization cuz it mess up with a lot of visuals.
I think it's a software issue. Because sometimes when i want to change the ringtone and i tap on a different one it took a lit bit of time to play it same thing when changing the notification. This problem is happening when the phone is locked only.
I'm cuurently waiting for the new update with a hope that it will fix it.
Thanks again.
have a nice day.