Mon Jun 26, 2017 5:41 pm
Personally I don't have issues with this as I know how to bypass this, but it still remains lazy development not following Android standard procedures...
It was said that the May release should fix it, then the next release, but you see, it's still there in some parts. And this is an issue kjnown since more than 10 months, just too lazy to learn how to do things right.
In my former company - Europes largest software company - the responsible developers would have been fired after two anouncements of bad work. Or sent to clean the toilets or something else where they can't harm the companys reputation as this software with Kindergarden errors does to Blackview.