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.
Related
Hello,
I habe a standard, unrooted S6, the only thing I've done is disable some of the Google apps and other apps that came with phone. I don't think this could cause the following issues?
I've noticed a rather annoying problem. Sometimes, and more often than not, when my phone screen is off and locked, I receive no notifications. Only when waking my phone does the notifications flood in. I've tried everything to fix, like the wifi sleep policy, cache clean, factory reset etc. Samsung support said they would repair the phone, but it feels like a software issue rather than a hardware one. I know I'm not alone with this issue, anyone have any advice?
Thanks for your help.
BryterMoon said:
Hello,
I habe a standard, unrooted S6, the only thing I've done is disable some of the Google apps and other apps that came with phone. I don't think this could cause the following issues?
I've noticed a rather annoying problem. Sometimes, and more often than not, when my phone screen is off and locked, I receive no notifications. Only when waking my phone does the notifications flood in. I've tried everything to fix, like the wifi sleep policy, cache clean, factory reset etc. Samsung support said they would repair the phone, but it feels like a software issue rather than a hardware one. I know I'm not alone with this issue, anyone have any advice?
Thanks for your help.
Click to expand...
Click to collapse
I am on T-mo and have the same problem.
Dont know what else to do myself.
We have been discussing this problem in this link if you are interested.
http://forum.xda-developers.com/tmo...otifications-wifi-t3095156/page2#post60632598
http://forum.xda-developers.com/galaxy-s6-edge/help/push-notifications-stop-screen-off-t3071248
hey, i've been using the Gear S3 since half a year now, after being disappointed by AW 2.0 ruining my Moto 360 2nd gen
since the 3.0 update, i often get an error using s-voice with simple commands like "set timer for ten minutes"
sometimes it works, but often getting an error after a few seconds, show either "an error has occurred. i'm unable to answer your question. please try again later" or "an error has occured, try again later"
has anyone else encountered this problem and found a fix?
i did a factory reset twice now, didn't help, not changing the s voice language from automatic to us english
the other stuff i wanted from the update also didn't happen, but i guess that's a different discussion
I am having the same problem. I had purchased the S3 Frontier when it 1st came out. I returned it due to problems with svoice. I just purchased it again last week and svoice is still garbage. Was hoping for it to be better. Will be returning again.
i did not have this problem with 2.x, voice commands like this never showed the error, for me it started after the 3.0 update
Same problem here can't reply to a message with voice and errors when simple commands like the OP stated.
I get around the message problem by setting the language to English UK
I still get the error message after the latest update on the gear update. I need to re-flash the stock Tezin on it hoping it will fix it.
Same issue with S3 Classic
Same issue here with my S3 Classic. Occasionally it works but most of the time I get the error. Reported it to Samsung but they were unaware of the issue and were non-responsive.
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Same x 2
My S3 Tmobile LTE failed in 6 days. They exchanged it for a new one at the store yesterday and that one failed also. So I returned it since it's a defective product. I'll buy again when the issue is fixed.
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
WaxysDargle said:
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Click to expand...
Click to collapse
how often to you have to clear out the s-voice ??
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
Every time you want it to work.
gboybama said:
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
Click to expand...
Click to collapse
I have the exact same experience Gboybama! Some contacts i can call, some produce an error message, some let svoice "synchronice contacts", which is never finished, letting the problem persist even after clearing cache, stopping the app, restart etc... **** this.
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
i only had to do it once. it has been working "fine" ever since.
s-voice never quite works properly. never has. i doubt it ever will. seems like samsung just doesn't care.
I just got my s3 today to go with my new s8+ having tons of iss6 with s voice. Looks like I'm not alone. Probably going to be returning this and researching other options.
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
I'm using Google fit because it tracks my daily steps\calories, is compatible with 99% of the watch faces, is free, and back ups online (or should). I haven't found any other app that does this, so if someone knows of one, PLEASE chime in. I'm pretty fed up with Google and their lack of support. Ever since I've had the watch (2 weeks), I have to go through some magical ritual of turning off BT\WIFI then turning it back on, then restarting my phone and\or my watch, and standing on one foot whilst singing "Mary Had a Little Lamb" backwards, just to get the fitness data to sync. When it FINALLY does sync, I loose literally thousands of steps and calories. Yesterday I lost 14,000 steps, and over 1,000 calories. Today I lose 16,407 steps, and over 400 calories. I've submitted feedback to Google 3 times with no response, started a post on their discussion forums, and left a bad review on the Google Fit app in the Play Store with NO response from them at all. I figured I should ask here and see if anyone else has run into this issue, and what they did to fix it...or if there is another app that I can use that will ACTUALLY work. Thanks in advance everyone.
How am I the only one with this problem? What could I be doing wrong?
Got that too, same problem with synchronized with watch. On watch all OK but on phone app not auto sync And only as You said restarting watch helps
The only Google Fit problem I have is that the app refuses to use the watch GPS if connected to phone. Not sure why you have that You may want to nuke it and start fresh on your phone and watch.
I have before, and it appears to be getting better with the Wear 2.9 update. There's a lot to be desired with this Fit app and support, hopefully it'll get better in future updates.
I gave up and just went with Runtastic. It reliably syncs to MyFitnessPal and that's enough synergy for me. It doesn't seem to know what to do with treadmill walking, but it still marks down a couple hundred calories burnt after the workout. Fiddling with Strava and GoogleFit and HuaweiHealth just proved to be an exercise in frustration for me.
Can you please join this thread and send a bug report for this issue? Thanks guys! https://issuetracker.google.com/issues/77606997
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.
Hello everyone,
My Galaxy Watch4 has been great. But I've come across a few occasions where my watch mysteriously disappears from the Galaxy Wearable app and the list of paired bluetooth devices. Unfortunately, the watch fails to recognize my phone as the same device and forces me to reset it.
I have debloated my phone and I did notice that it happened once after resetting network settings (although that could be an annoying but correct behavior). I wouldn't be bothered as much if I could just repair it as-is but this has happened about 3 times since I've owned the watch.
I did use a debloater script on my S22 but not the watch. The issue persists after reversing the debloat. Is this a known issue? Are there ways to locate logs/settings that may be causing this?
Alternatively, is there a developer/hidden option to bypass the erase requirement?
It happened to me when I cleared Google Play Services Data.
JazonX said:
It happened to me when I cleared Google Play Services Data.
Click to expand...
Click to collapse
I can't recall if that happened in my circumstance, but I know of one instance where it didn't and it happened back to back, requiring me to reset my watch 3 times. Could be user error on my part since I tinker with my phone but knowing that it relies on GPS is a step in the right direction
https://www.reddit.com/r/WearOS/comments/p7lhir