Hi,
I’m experiencing a horrendous speed issue on my new Watch 6 Classic with Facer. Some faces are better than others, but those with a lot going on cause a slow down so bad it’s almost impossible to use the watch, dragging down quick settings is sluggish (1 second wait or more).
Same face on my old Gear 3 Frontier, is lighting quick, so it’s not the face/design.
I’ve tried uninstalling (twice), reboot, re-install and much testing, it’s clearly not my watch because if I scroll left to notifications, the watch becomes instantly fast again, for now that’s my solution to access quick settings or more.
Anyone else finding this?
If I can, I’ll list some faces which cause speed issues, most are slow, some are VERY slow - but it should not be the case if my 2016 Frontier Tizen is faster!
Until you get some results from others, you might consider sending @Facer_Official a message informing them of your issue. That will at least put it into their mind there might be something that needs worked on. You can message them here: https://help.facer.io/hc/en-us/requests/new .
Thanks, have already done so.
And just discovered it’s faces created on CREATOR that it’s doing this. Many of the premium or top10 faces seem fine (do people use things like SamSungs Watch Face Studio?), am curious to how/why it’s doing this.
As soon as I use a creator face, even a basic one, slow down occurs on Watch 6.
I know that @russellcresser has used Samsung Watch Face Studio in the past. But technically any Facer watchface Premium or Free has to be created on Facer Creator. There is a glitch in the Google Services using up the battery on GW6 Classic. There might be another one causing Facer to slow down on the GW 6 Classic also. I’m sure the guy behind the ALLSTARSPACE YouTube channel will hear about any issues or fixes long before they get published.
Yes . The Real Time 3D stuff must be made on a different platform . I think the Magic is .apk . Some are sideloading these onto watches like 4 and 5 . Nothing to do with Facer or WFS . The ground is shifting under our feet . The problems being experienced are not Hardware Problems and I know it will get better but When ? That is the question .
has there been any update to this?
i just tried to make my first watchface, and there’s barely anything on it, but it makes my watch lag so much, to the point of not worth using that watchface
Works just fine on my Galaxy 5 Pro and my Galaxy 6 Classic. If I were you I would turn the watch off and wait a minute or so and then turn it back on and try it again. It might only need restarting.
interesting… thank you for checking and the feedback
i did try that (again after you suggested it), but it makes my phone so laggy.
other facers are perfectly fine, even animated ones, but this simple one slows everything down
I was explaining this to someone else . Glow and stroke are Effects on the Text layers that cause Problems with our mor modern Watches . I would say it is best just to use it on Tizen Watches . Be aware that Having loads of faces on your watch acan slow things down . I clear my watch so there are just 2 Facer and 2 Google / WOS . Works perfect . Having said that I am on GW4.
I don’t understand the distinction you’re making here. EVERY face on Facer is made in Creator. There are no faces available through Facer that are made in any other way. (graphics can be made however/wherever, but the faces are assembled, coded, and published ONLY through creator)
So if you are saying non-facer faces are ok but ALL facer faces are slow that’s one thing and would suggest an issue with facer, but since you saying many “premium or top 10” faces are fine, sounds like you’re still talking about Facer faces there. So the issue would be specific to some faces and not Facer itself. Are you experiencing problems with any premium Facer faces or only some free ones? All premium faces go through a QA check before they get published, free ones do not.
I rarely use glow. I’ve only every used it on some of the Warp series I’ve made. But only a single layer in each instance. In any event, no problems whatsoever with that on my GW6 Classic.
@russellcresser & @kvansant
From my experience with stroke and glow, the problem doesn’t show up immediately. It takes a few hours and then the stroke/glow moves 5 to 10 pixels over and becomes a weird shadow instead of what it is supposed to be.