Going to use this space to chat about general android stuff.
google is the worst enemy of full android watch
battery life is everything for full android watch compared to rtos
and google play service run in the background drain your battery collect your data and send it back
it is best if the system limit them or not have it at all
1 Like
It is - yes.
However, most customers will want to use gapps on these watches and it is curious and pleasantly surprising that at least there is a choice to use them or not.
It would be nice if it was possible to disable GMS for those who don’t want it. That’s an important option as you say. It will use battery all the time if allowed. So would be great if it could be disabled as a choice. It really depends on how they implement it as a system app and the related framework.
1 Like
What brand sells these w527 devices like yours @AILIFE
I’m interested in testing one. I’ll send you a message once I know what brand is selling it.
Cheers 
1 Like
it is way better to use microg, use less battery does more its that simple
the only device that used microg is so bad tho the system just kept crashing
1 Like
XTQ and CD
2 Likes
the thing is, disable play service is very bad idea, because the remains get detected by your apps, the apps will try to use it and fail, so the app just break, like whatsapp
2 Likes
True that…. I didn’t think it through, 
Looks interesting the w527 https://www.unisoc.com/en/product/SmartWearablesUS/W527
1 Like
Yes indeed…
I’ll see if I can persuade Wiite to use microG. It is a better choice for watches - for sure.
I’ll send you a message to see if you are interested in something I’m doing 
1 Like
it is benificial to have the microg as preloadapp insted of system app as it is not requiredd to be so user can delete it completely
1 Like
To be honest I’m guessing that they used a custom built version of Android Auto for this S99 device. They have access to it because so many cars are built with Android systems installed. That would explain why it is a) working fine for Google apps and b) why it is Android 8. I’ll have to get hold of one to be sure though.
Very interesting indeed…
Thanks
i heard s99 still do not have access to notification, so that mean it is just the same android go as any other 8.1, nothing to write home about really
the access to notification is the only real problem with these device, as of killing app the ones i have i run dontkillmyapp benchmark and it do ok in white ilst, as with the sensors i dont think i need to say a word
the user often mistake google service get killed with their app get killed, because play service must be killed, and that stop fcm push notification, the user thought it is really their app get killed when in fact that never hapenned
1 Like
Yep, notifications are always a nightmare and the way they mutilate the notication top bar is maybe the cause. Where you would normally see battery, comms and other icons in Android. It seems to be a serious issue that needs a lot of work if notifications are going to work properly. Ju guessing - but this was the main problem when we were developing with Android 10 on MTK. It was the last bit of dev work we did here to be honest.
So, you think this is Android Go and not the usual verion, that we would use for example?
That would also explain a lot.
the status bar is irelevent. the problem is in vendor ro.config.low_ram
Well, I’m just referring to a problem we found with A10 solution and their customisation - the status bar was indeed an issue back then. But this was a few years ago now.
What problem do you see in vendor ro.config.low_ram ?
1 Like
i dont think status bar on a round display is particularly useful.
ro.config.low_ram prevent granting BIND_NOTIFICATION_LISTENER_SERVICE on android 8 to 10, and afaik there is no way to bypass even with adb you write secure setting it still doesnt work