Then you've either been lucky, don't use many apps or are blind, considering you stated that you support Android devices from a technical standpoint I'm guessing you're blind because there is no way you did not come across this issue.Κracus wrote:I've never run into that problem... The only issue I've ran into is one where the keyboard won't show up to let you type in a password to unlock the phone. Definitely a bug in the samsung OS. Recently though I obtained an adaptor that allows me to plug a USB cable into the charge port of the phone and by plugging in a keyboard I was able to bypass the bug and send the user on his merry way. I'm assuming it'll be patched.
As an example, my s5 was absolutely brutalised by it, the poor thing could barely unlock itself thanks to an update in Android 5.0. I swapped this phone for another (octacore) s5 hoping I could power out the issue with sheer CPU power and that was on top of the wakelocks from apps that I was experiencing. My next phone (and current) is an s7 and although this handles better thanks to being more powerful I still get niggling issues with it where it will throw resources away so I have to perform some maintenance in tracking down problem apps to try and get it corrected from time to time. This can be caused my anything n all, including an update by FB, Snapchat or something just as popular. Then there's issues with mounting, apps disappearing along with your keyboard and such, these being the minor problems. Android when looked after can perform well, but like gardening I really can't be fucked with that shit.
If you want access to the backend and like fiddling with your phone, customisation, installing ROMs or whatnot then Android is by far the choice for you, it's what I thought I wanted, but if you just want a phone with similiar functionality out the box that you can leave without it fucking itself then it has to be Apple. I don't use a lot of apps either, it's not like my phone is littered with them and I know others with varying devices (notes / moto's etc) who have had it. That keyboard issue has plagued all Android devices for a good few years n all, it's not Samsung specific, a few restarts and clearing cache usually fixes it, that can also be an issue associated with allocated resources and the KB not having enough.