With great enthusiasm, I downloaded the firm-ware
Because running the older sep2020 - I could not bare
Hooking up the watch to flashtool was required
Rebooted the watch - onto a new system I was thrown
Everything was fine for a few mins until wifi was acquired
Alas, suddently everything stopped, I thought it had blown.
Oh no, the screen went completely black,
Please, oh please, can I have my KP2 back?
(poetically speaking)
https://play.google.com/settings
scroll down, edit the device to a better name.
you are welcome
I thought a better user experience was strived for, but I sense unwillingness to change things we are used to overcome. It has become so normal to overcome ‘this’ by adding ‘that’ app, that we no longer strive for a watch which is perfect out of the box.
I do recognize that this new firmware is a great achievement 
Mine says kospet prime 2 registered on may 2nd
Yep, sorry that was correct but the newer version of services app does not have it.
I will edit the OP 
The name is what it is.
Forget about it 
As I said in the first post, this is a taste before the OTA.
We will see.
For now let’s stay on topic.
Thanks
Ok now or are you having problems?
Kospet requested that the icons are in this order as stock
As @G1NT0N1C says UL will let you do this but it is still a work in progress on stock
@Colin_Green
Mr Ticks is making a video about the firmware at the moment but flashing is already on our yt channel and also Mr Ticks channel.
I strongly urge you to take time to check out this stuff because it is quite scary reading above…
Thread cleaned
Sorry but we really need to keep this thread for feedback so I will move these posts to the Prime 2 support thread.
I know it didn’t read pretty but believe it or not I was more than 51% sure it would be ok at all times. Lol
Feed back. Yes! it is muuuuch purtier and cleaner than previous. More to follow when I have had a proper play. Cheers all.
I just discovered that the AutoNotification plugin for Tasker causes reboots in the new fw. I also had two reboots yesterday but I don’t know the cause for those. Despite that the fw does seem more stable.
If possible, please provide a logcat when this happens.
Sure. How do I do that?
adb logcat > debug.txt
Not sure this one goes back to the last crash but here you go anyway: debug.txt - Google Drive
I’ll try to be more timely next time.
If you are using the universal launcher, could you re-do this test with the default launcher as well?
Do you mean try AutoNotification with standard launcher?
Ok. But it was kind of hairy. I was in a reboot loop and just managed to uninstall AN before it happened again. Do you mind if I wait to try tomorrow?