03-06-2020 01:50 AM
Hi,
I have a Samsung S3 Frontier smartwatch and it recently updated on 29-May-2020 to:
One UI version: 1.5
Tizen version: 4.0.0.7
Software version: R760XXU2FTD4
One of the only apps I use on it, FITIV fitness app, will no longer load anymore.
After multiple troubleshooting attempts, I contacted the community of the FITIV app on their Facebook page.
They've advised the recent update removed a crucial library the app used called the "Samsung Access Protocol".
Without this library the app isn't useable and it crashes when trying to find it.
Does someone from Samsung have more information on this issue and how soon it will be fixed?
04-06-2020 09:15 PM
Hi,
I have a Samsung S3 Frontier smartwatch and it recently updated on 02-JUN-2020 to:
One UI version: 1.5
Tizen version: 4.0.0.7
Software version: R760XXU2FTD4
Since the update HRM, pedometer and GPS all stopped working. The battery drains within a day and the touch is very sluggish. I've done a factory reset and still not fixed the issues. Has anyone a fix for this, please? Very disappointed with this update.
03-07-2020 07:00 PM
I do have exectly the same problem since I' ve updated my Galaxy Gear 3 Frontier to Tizen 4.0.0.7.
No GPS, no pulse sensor and the entire firmware is much slower than the previous firmware.
I did several firmware resets and also reinstalled the relevant Samsung Apps on my phone.
I even tried it with several phones (i.e. Samsung Galaxy S10) without any success.
I was quite happy with my watch for 1,5 years but the last update is a disaster!!!!
@Samsung development team....kindly fix this issues!
03-07-2020 07:34 PM
Hey @Charly22 ,
I would suggest sending an Error report to get this looked at. You can do this by following these steps:
1. Long press Samsung Members icon on Apps screen and Tap Error reports
2. Tap OK on agreement popup for sending system log data
3. Select Symptom category
4. Describe the problem in detail and SEND.
25-12-2020 02:02 AM
Hello,
Recently uodatwd my watch to 4.0.0.7.
I also have the all sensor fails exactly since then. Any fix yet?
With kind regards,
TOM