I think it’s due to some other setting, like “wipe the phone if password is entered wrongly ten times”. It’s possible to enter bootloader mode accidentally, but wipe the phone requires too many steps to be done multiple times in a row.

Backups and android always suck. They made it on the developer. It’s the developer that has to write a function to backup the settings on the Google servers. Not difficult, takes like a couple hours tops, but nobody is doing that.

Instead on iOS it works on the opposite way, the operating system backups everything and it’s the developer that has to waste a couple hours if they DON’T want their app data backupped on iCloud.

The result is that on iOS a backup restore gives you a almost 1:1 copy, while on Android a backup restore gives you a phone with all the apps resettled to zero

That wavelet suggestion must have been sponsored. There’s no way otherwise

Android Lollipop was first released in November 2014, nearly 10 years ago

False statement from Google, as they know that OEM started to slowly adopt it over months. They still sold Lollipop devices in 2018

With the state of wearos where both the os maker and the chipset maker aren’t believing in the platform, it’s difficult to blame them.

The best way to do a smartwatch is using an embedded dedicated os that uses minimal resources to save battery. It’s the reason a ten year old pebble smartwatch with 128k of ram and a 64 MHz CPU feels faster than a brand new wearos smartwatch with 2gb of ram and a 2 GHz CPU.

If for example you want to show a barcode for a membership card on the watch screen, you shouldn’t run a full 100mb app on your watch with a database, internet connection, 2mb high res PNG files for icons and other shit. There’s a powerful smartphone in the pocket that can do all the hard work like syncing, adding, editing or deleting cards and so on, and when a card need to be showed on the screen the phone just tells the watch “ok so using the embedded library just show this barcode, and to make it fancier use a green border because it’s Starbucks”

But when people are purchasing it they’re directly comparing it to the Apple Watch with beautiful display, fancy animations, and the numbers on the spec. “What? This watch only has 128k of RAM? LOL this other one with 16000 times more memory gonna be much better”

So, instead of doing it the right way and investing millions on an embedded os with fancy animations everyone took the shortcut of using wearos. “The chipset and the operating system is already done for us, just need to customize it!” And spend millions in customizing it.

But then, those Qualcomm “smartwatch” chipset are just ten year old smartphone CPUs in disguise and the operating system it’s the full android os with a different skin. Congratulations, you got a ten year old smartwatch sized smartphone with bad performance and short battery life! Good luck selling that shit. Ah, forgot to mention that the company that is selling you the operating system is directly competing with your sales and at the same time it’s holding exclusive features for themselves and/or delaying them for months. And they’re using an exclusive chipset that’s way better than whatever you can get. Yeah, customers gonna be pissed that your expensive smartwatch sized smartphone doesn’t have all the features of the pixel watch.