Database Info

Vibrate mode stopped working!

I have the 750, upgraded to WM6.1 - however, after installing a couple of third party apps, it seems that my vibrate mode has stopped working. I disabled, then deleted all outside apps - no go. All settings are correct and I have checked everything that I can think of to fix it.
Anyone know of any problems related to the upgrade, or any other issues? Any help would be appreciated, since I love the phone, but really need the vibrate function.

Ummm, nevermind
Well, it seems that I have cleared up my own problem. I accidentally dropped the phone onto the floor from a short distance, and it fixed itself!! Hmmmmm. Clutziness to the rescue!!

Recurrent Set Screen Lock Message

I have an issue since I upgraded to Tizen 3 that I can't find the answer for. I keep getting a recurrent message saying EAS requires a PIN to access email content. The dumb thing is I already have a PIN and the phone is set to Gear Lock with Payments only. I type in the PIN I have and re-enter it only for the message to come back again in a few minutes.
This problem is very new for me since Tizen 3 and it happens even after a factory reset. It is so annoying.
I have a corporate email on my phone but I don't understand why it keeps coming up even though I have a PIN already on the watch.
Please help!!

I have the same issue its crazy frustrating how can we fix?

Is that a new issue for you since Tizen 3 update? This has never happened to me prior to the update.
As others have said before I'm pretty unhappy with this update. I have worse battery life, the Gear VR integration hasn't worked for me, and this PIN thing is crazy frustrating.

I'm having the issue as well, and I have no corporate email, just Gmail. This only started happening after the Tizen 3.0 update and has persisted through a device hard reset.
One thing I'm wondering is if my watch strap is causing the issue. It seems Tizen 3.0 is handling things differently with determining if you're wearing the watch by relying on the heart rate sensor. I think it relied on gyroscope before. All I know is my NATO strap suddenly prevents AOD entirely and notifications only work if I set it to show them even when I'm not wearing the watch. I'm guessing the strap running between the watch and my wrist might be causing the PIN issue because it thinks I'm taking my watch off.

The thought about the strap is an interesting one and one I thought may be at play as well. It would be a disaster if that is what is causing it because I don't know if there is a good fix for that.
Anyone recommend any straps that potentially could fix this problem?

arjuna_ said:
The thought about the strap is an interesting one and one I thought may be at play as well. It would be a disaster if that is what is causing it because I don't know if there is a good fix for that.
Anyone recommend any straps that potentially could fix this problem?
Click to expand...
Click to collapse
I just put a regular strap back on and AOD and notifications work normally now. Unfortunately it doesn't affect the issue in this thread. Even with a regular band that doesn't go between the watch and my wrist I'm still getting the EAS PIN issue.

Seems like there is NO solution to this problem. I'm about to sell this it's driving me nuts.

Knock on wood, I just updated to Beta 6 Oreo on my GS8+ and have not yet seen this error.

Clear your phone's app data
I fixed this problem a while back... I also had a problem with the gear app on my phone crashing repeatedly. I think it was by going to settings on my phone, selecting storage, internal storage, apps, Samsung gear, clear data. It will erase your steps, etc. But in my case fixed the problems. By the way, I got this fix by calling Samsung support.

Can't Answer or Make Calls

So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou

It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.

Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?

louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.

Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??

louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend

Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.

louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.

I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.

Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.

Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?

nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon

I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.

The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.

Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.

Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.

Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).

ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!

MMS and Notification issues on Note 10+

Hello, I've had the unlocked Note 10+ for a few weeks and have had chronic issues since day one and not really sure what to do about it. A lot of the issues seem to get worse over time. Not sure if the problems are related, but it feels like it.
First, I have MMS issues mostly with any other app but the built in messaging app and even that one isn't perfect. Using Textra for instance will get me MMS timeouts sending and receiving and sometimes messages don't send or come in. This seems to happen with or without wifi enabled.
Next, I'm getting delayed notifications on many if not all apps. Notifications will some in here or there, then all of a sudden I'll get all the notifications for the day all at once. So suddenly my phone is going crazy receiving 50 notifications from different apps all at once. Related to that, if I get a notification and click on it to open the related app, often nothing happens. Then like an hour or more later the app I clicked on for the notification will pop open in the middle of doing something else. It will also get hung up installing or updating apps. A reboot will usually clear this but at some point it get's stuck again and will take hours to install an app if it does at all.
I've done all the usual things like disabling battery optimization for the apps in question, set the phone to high performance mode. Uninstalled and reinstalled things, cleared the cache partition, reset network settings, checked APN settings, even now have factory reset the phone, twice, got a new SIM card. Talked to Samsung and they tell me I need to mail it to their repair depot in Texas if I think it's hardware.
So no idea where to go with this. Seems hard to believe it's a hardware problem and sending the phone away for a week or more doesn't seem like a great option, especially when they might just send it back as it works OK for awhile after a reboot.
Any ideas would be appreciated. Thanks

After you reset the phone, did you install apps manually from store or let it go off a backup?
Also, just an idea but maybe the tower servicing you is acting up.. Unless it's been happening in multiple areas.
Sent from my SM-N950U using Tapatalk

That is a good point, I did let it install automatically from the Google backup. It wasn't a true restore the way I would generally think of it as everything was installed from scratch, but maybe some settings are getting put back that are messed up. It happens out of the are as well, but I did talk to my carrier and they claimed the did some stuff at the tower that might help. I usually think that means they go get coffee then tell me to reboot the phone. Maybe this evening I'll try a fresh install with no restore. Sort of sucks of course as that's a lot more work to get going, but what the hell at this point. Thanks.

willp2 said:
That is a good point, I did let it install automatically from the Google backup. It wasn't a true restore the way I would generally think of it as everything was installed from scratch, but maybe some settings are getting put back that are messed up. It happens out of the are as well, but I did talk to my carrier and they claimed the did some stuff at the tower that might help. I usually think that means they go get coffee then tell me to reboot the phone. Maybe this evening I'll try a fresh install with no restore. Sort of sucks of course as that's a lot more work to get going, but what the hell at this point. Thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have a note 10+ myself now unlocked and seeing some texting issues where I don't receive text or mms from Apple phones. Hasn't happened with Android to Android though.
Sent from my SM-N975U1 using Tapatalk

So none of that reinstall stuff helped me. On texting I finally tried the Google Messages app with chat features enabled when it was leaked. Messages alone didn't work, but enabling RCS did and now it actually works better than ever. I hate giving up on textra, but I like the sheer speed of sending giant MMS messages now.
On the notifications thing, the thing that finally got that working right was disabling the Google app. As soon as I did that, all is working as expected. Of course that breaks some Google stuff, but at the moment that's what I have to do to make this work. Even upgrading to Android 10 betas didn't allow me to turn that back on.

Updates stuck at 100%, Gmail does not notify, and other issues.

I am desperate, I can't find the issue here. I have a S10 (Xfinity unlocked on Verizon) , I can't seem to update apps, they get stuck at 100% or 99%, AND some things like Gmail and Instagram do not seem to notify that I am getting messages.
Here's the kicker, I factory reset the phone some 5 times now, and still have the issue. The Reset fixes it for a few days (if even a day) and then the issue starts up again!
the phone was just upgraded to 10, but it was happening on 9 also!
no clue what the problem is ! it kills me! Please anyone have any idea? I even had an authorized Samsung dealer do a "software refresh" and then wiped out the phone again, and I'm still having the same issue..
HELP! please.
thank you

eatonjb said:
I am desperate, I can't find the issue here. I have a S10 (Xfinity unlocked on Verizon) , I can't seem to update apps, they get stuck at 100% or 99%, AND some things like Gmail and Instagram do not seem to notify that I am getting messages.
Here's the kicker, I factory reset the phone some 5 times now, and still have the issue. The Reset fixes it for a few days (if even a day) and then the issue starts up again!
the phone was just upgraded to 10, but it was happening on 9 also!
no clue what the problem is ! it kills me! Please anyone have any idea? I even had an authorized Samsung dealer do a "software refresh" and then wiped out the phone again, and I'm still having the same issue..
HELP! please.
thank you
Click to expand...
Click to collapse
Boot into safe mode, it will only load your system apps and not your user apps. Then try to update your apps, if it works then you know the issue is being cause one of your user apps. Then you just need to identify which user app is the offending app.
It also might be caused by a conflict between various settings or maybe you have some things disabled or turned off that are causing this.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Boot into safe mode, it will only load your system apps and not your user apps. Then try to update your apps, if it works then you know the issue is being cause one of your user apps. Then you just need to identify which user app is the offending app.
It also might be caused by a conflict between various settings or maybe you have some things disabled or turned off that are causing this.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
That kinda works.. but again, as said, I have reloaded the phone over and over, and it works fine, until a few days later and stars over.. And updating is not the only problem, Geolocating is slow, sluggish or not working sometimes, Push updates of emails are slower or not happening. just weird things..
I am not sure what it could be! its like the phone is the problem!

eatonjb said:
That kinda works.. but again, as said, I have reloaded the phone over and over, and it works fine, until a few days later and stars over.. And updating is not the only problem, Geolocating is slow, sluggish or not working sometimes, Push updates of emails are slower or not happening. just weird things..
I am not sure what it could be! its like the phone is the problem!
Click to expand...
Click to collapse
Ok, everything I posted went completely over your head, I'll try again.
If it is working like it is supposed to while in safe mode(which is only loaded with system apps and system settings and not any of your user apps or data) that tells you that the issue is caused by some user app that you have installed or something in your user settings. In other other words, it is very likely something that you, as the user, have installed or setup/selected, it is probably not the device. It keeps happening after resetting because you are not changing what you are doing that it is causing it, it is something that you keep returning to after resetting the device. You just need to figure out which user app is causing the issue or whatever settings are causing the issue.
The way to do that will be trial and error. Uninstall one of the apps that you have installed, then use the device for a few hours, if the issue continues, that wasn't the app causing the issue, reinstall that app then choose another user app to uninstall and then use the device for a few hours, if the issue continues, that is t the app, reinstall that app, and so on and so on, etc... Get the picture? When you uninstall an app and the issue stops, the last app uninstalled is probably the app causing the issue.
I suggest resetting the device again. Then, only install one of your usual apps but don't install any others and don't change any settings, use the device a while, if the issue does not occur, install another one of your usual apps but don't install any others, basically, install one app at a time until the issue occurs, when it does, the last app installed is probably the offending app.
Or, if you don't find it that way and you get all of your usual apps installed without triggering the issue during the trial and error process, then you need to go through settings by trial and error. Changing one setting at a time and using the device a while to see if the issue occurs, if it does, it probably has something to do with the last setting that you changed before the issue occured.
Slowly changing one thing at a time over an extended amount with time between each change, will allow you to isolate exactly which app or setting is causing the issue.
Or maybe you need to flash your stock firmware via PC tools to start over with a clean installation.
Sent from my SM-S767VL using Tapatalk