My heartbeat sensor will turn on whenever it's covered. Almost like a proximity sensor in a reversed fashion.
In the one call I've placed since the update I've also noticed the front proximity sensor having a major delay in turning the screen off after putting the phone to my face to talk.
Anyone having these issues? Any fixes?
I've used S health to measure my heart rate in an attempt to correct the issue like one guy mentioned but I think he spoke to soon as it is not a fix.
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
phobia09 said:
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
Click to expand...
Click to collapse
I did a factory reset, and have yet to launch S Health again since. So far, the sensor has not lit up again. I'm afraid to start S Health though. I will just use Runstastic for now
I don't have this issue. Before I updated to lollipop I did do a factory reset.
Sent from my SAMSUNG-SM-N910A using xda premium
To report back: I backed up, flashed back to 4.4.4 via Odin, took OTA to 5.0.1, factory reset, then restored data and signed into all my accounts again. It seems the solution lies in waiting for AT&T to clean up their mess. The problem has come back for me.
Sent from my SAMSUNG-SM-N910A using Tapatalk
phobia09 said:
To report back...The problem has come back for me.
Click to expand...
Click to collapse
Thanks for tanking one for the team!
At least we have gained the knowledge that going through a full wipe won't help :good:
i noticed this today when i was wearing gym shorts. restarted the phone and it disappeared, for now.
i use the sensor a couple times a day out of curiosity.
please report back if you find a fix
update: after reboot it went away, then i noticed as soon as i plugged it in to charge, it came back. i used s-health to check heart rate, then it went away again. unplugging/replugging into charger did not make it come back.
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
So are u guys with the sensor issue. Was Google fit installed with lollipop update?
Sent from my SAMSUNG-SM-N910A using xda premium
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
phobia09 said:
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
Click to expand...
Click to collapse
Uninstalled Fit, opened S Health, checked pulse, then had hr light stay on lol
But I like the idea of removing the app that causes it, I just think it's S Health, I tried disabling S Health and so far so good (but I'm pretty skeptical)
Related
This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app
So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
_MetalHead_ said:
So my first N7 had dead pixels and when I returned it I had to open 3 others in store to find one that was perfect. Or seemingly perfect. Twice now I've woken up to find my N7 off. The first time it happened I thought maybe I turned it off but last night I know I left it on. I did some searching and found that I am not the only one with this issue, but I haven't found any recent threads about it or any known fixes. Now I'm still on 4.3 and really don't want to update to 4.4 but if this bug was addressed I'll update it. Anyone here have this issue, found a fix, or updated and had the issue disappear? I really don't want to exchange it yet again but I will if it's the only way to get one that doesn't do it. Any insight would be appreciated.
Sent from my Moto X
Click to expand...
Click to collapse
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
username4this said:
Why don't you want to update to 4.4.2? It might solve the problem.
Anyway, the only device I had that had random reboots was my Nokia Lumia 520 which I straight away replaced.
I would advise you to do it aswell incase 4.4.2 doesn't fixe it.
Click to expand...
Click to collapse
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
_MetalHead_ said:
I don't like the way 4.4 looks. I am a big fan of the blue/holo theme of 4.3. I have 4.4 on my N5 and that's enough for me. 4.4 really doesn't bring much to the table (for me anyway) that would compel me to update.
My N7 isn't rebooting, it's turning off. Never had a device that did that before. I'll probably update just to see if it stops it, and plus I have some bad stuttering when watching embedded videos in chrome and from what I've read, 4.4 solves that too. I really don't want to have to exchange it again, and I'm sure the manager at Best Buy doesn't want me to either lol.
Sent from my Moto X
Click to expand...
Click to collapse
Obvious question here but have you tried a factory reset?
username4this said:
Obvious question here but have you tried a factory reset?
Click to expand...
Click to collapse
I'm going to tomorrow if it does it again tonight. But the tablet is only a few days old and I already did a factory reset before I set it up initially.
Ok it just did it again right in front of my face. It didn't just go black in the middle of use, I picked it up to use it and before I could do anything it powered down, but did so as if I had deliberately done it. Meaning, the Power Off pop up was on the screen and it said "shutting off" the same way it does when you turn it off manually. That would lead me to believe it would be a software bug as opposed to a hardware one... am I correct in that assumption? Or can some hardware defect actually trigger the normal power down sequence?
after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys
i noticed the same thing...i had to reboot the phone few times...
Same issue here!
You can wait till christmas, but nothing works to get your keyboard back..except booting..
Yes same issue here. I've mentioned it not long after the Developer Edition received the OTA.
It's not even something that we can recreate, it's just completely random. It stays that way until a reboot and then it's fine again. Very irritating.
try to clear data in app settings, that work for me :/ 4 days no problems
vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
do other keyboards work?
vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
not an expert here; can you explain how/where/what?
Donky1973 said:
not an expert here; can you explain how/where/what?
Click to expand...
Click to collapse
go to ;
settings-apps-all-htc sense input- clear data
mxisme said:
do other keyboards work?
Click to expand...
Click to collapse
They've never worked for me... unfortunately.
vahica said:
go to ;
settings-apps-all-htc sense input- clear data
Click to expand...
Click to collapse
ah...the sense-input thing...makes sense...thanx!
No problems here.
Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..
Donky1973 said:
Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..
Click to expand...
Click to collapse
Hello, the same problem with the keyboard .On any firmware, I have 6 different firmware problem persists.
p . s . TEL Verizon
Still having this damn problem.. Anyone know if it's isolated to Verizon phones? I'm on Verizon 5.0.1 stock, both the HTC and Google keyboard do it. Completely random, about once every day to 2-3 days. So annoying.
I'm having trouble with my HTC one M8
vahica said:
after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys
Click to expand...
Click to collapse
I had a problem with the keyboard lagging which got worse after the lollipop update, I was considering a warranty claim or rooting the phone and then the microphone packed in and the decision was made, I called the network who advised me to send it to HTC for repair which I did, it also had a few sync problems too, I asked the technical support guy about this problem and he said it would have to be reflashed, I sent it to them and they did the work, replacement microphones, replacement receiver, replacement lower board, replacement rubber something or other which I was told is something under the screen, replacement camera and a few others and of course it was flashed, I got it back after 8 days expecting my otherwise brilliant phone to be as it should be as I have come to expect from HTC, I switched it on and did the initial stages of making it work, I let it restore the last backup I made (off the phone with faults) which reported had failed but it started to restore the backed up apps, settings and my contacts, everything restored to how I had it before minus a couple of apps and a few notification settings, I have been using it for 2 days now however the keyboard has not been fixed by flashing it, unless the errors could have been brought in by the restoration? I have experienced the screen freeze and start jumping, jumping to the all open apps page, keyboard lag, keyboard is inaccurate, I went into the EE shop and they said that it should go back to HTC again, I haven't tried to hard reset it and go back to the factory settings and not restore the backup image this time, I've never had any problems with the 3 HTC phones I've owned, it is a good phone otherwise
Damn, I just went back to Dev Edition and sure enough it happened to me. Has this ever been fixed? This is way too annoying for me.
Possible Fix
For what it's worth, I went into App Manager to clear the Sense Input data as suggested by a previous poster (thank you) but did not have a 'Clear Data' button. There was a 'Settings' button though where I was able to turn off HTC Sense Input, after which my Swype keyboard immediately started working again. First time I've been able to resolve this SUPER annoying issue without rebooting the phone. Time will tell if it's a real fix; I'll update this post if not.
Phone is a brand new M8, still on stock 5.0.1
Have had the Huawei Watch for a few days and it seems to have a deal-breaking bug. Frequently, after the watch has been in ambient mode for a while, it won't come out of it. If I touch the screen, the ambient display gets brighter, but that's all. No response from swiping or button presses. Sometimes, after a very long pause (a minute or so) it'll come back to life, but usually I have to hold the button until it restarts. Anyone run into this before? Ideas? Any help is greatly appreciated.
Using it with a Nexus 6. Android wear version 1.3.0.2176821.
Thanks!!!
Sent from my Nexus 6 using XDA Free mobile app
Forgot to mention that the time sticks at whatever time it freezes and so it doesn't even tell the correct time. Sigh.
Have tried a factory reset. Didn't fix it.
Sounds like it's maybe in need of replacing. Like any new product release, there's bound to be a certain percentage of failures. Depending on how you look at it, you're either really lucky, or really unlucky
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
gyromiterob said:
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
Click to expand...
Click to collapse
I have absolutely same issue. In ambient mode it freezes from the first day I bought this watch. Thank you for investigation and info.
got my hwatch and experienced the ambient mode freeze. to unfreeze, i enter and exit theater mode. it works. but now i'm never sure if the ambient time i'm glancing at is accurate or not...
Similar problem with an HTC M8. I'll try the theater mode to see if that helps. I still can't trust the time any more.
+1 on the Huawei Watch freeze. Sometimes after 15 minutes, sometimes after several hours. It has frozen with ambient mode disabled and with wrist gestures disabled as well.
Sent from my LG-V500 using Tapatalk
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
brizey said:
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
Click to expand...
Click to collapse
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
lukhof said:
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
Click to expand...
Click to collapse
Good to hear you got it fixed!
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
maximus96 said:
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
Click to expand...
Click to collapse
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
lukhof said:
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
Click to expand...
Click to collapse
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
maximus96 said:
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
Click to expand...
Click to collapse
None of them had red-tint issue. It seems this is not related with the freezing ambient mode.
Thanks, that solve my problem as well.
Happening to me too. Was using 3rd party skymaster watch face.
Got a replacement from amazon and it hasn't froze yet in the past two days of using it. The last one froze several times a day