From the incident report it seems the impact was limited to VMs in one DC in one region to be stopped, as the power was lost. And some service degradation in the region.
So not that much impact. Of course resources in this DC would stop working, but the rest of the region was still working properly. If you built your infra in this region in a resilient manner, your services should not have been impacted that much
Not sure about the latest Android version, but I managed to unlock and bypass a phone which had factory reset protection, and as far as I know a lot of vendors like Samsung have their own exploit available.
Using this you can manage to get to the settings app (while still locked, waiting for the previous owners google account) and remove the account, add your own or disable the security.
Done!
I did not yet upgrade to the latest version, but to migrate to compose I only had to copy the volume paths and the environment variables from Synology.
I can share my compose yaml by the end of the day if you need.
Before I upgrade I will try putting the cache on a SSD instead, seems it can improve performance quite a bit
Okay chief. What do I use to play YouTube videos, local tv news, Netflix or pirated movies on my tv then ? I have to have a laptop or a computer on the side to play the content? That computer has to be able to playback 4k HDR. It also has to use edge to get 1080p out of Netflix (scratch that I have a 4k subscription). It has to consume less or the same then my TV.
I’m curious about what real alternative you got, that is as useful and user friendly as using the android tv directly ?
Thanks for taking the time to explain it. Indeed the new runtime method does not guarantee when the resource will be cleaned, so something like that Drop trait would be quite useful