This is what happens if you employ QA-morons that tests your software on production environments. And you pay them that little that they don't even understand the fuckup, they're stepping into! :>
And mummy was always saying... never test anything on prod! :>
Here you have 3,5 year old post that counts eighteen points to prove you that MTP protocol is a huge shit. Three+ years later nothing changed except for the fact that Microsoft and Google itself finally realized what they've invented:
It's error coming from MTP protocol-based file transfer and description of the protocol itself in one!
Seeing such error in a buggy Android 7.1 isn't very surprising...
...until you find out that this application is...
...disabled and should never be run by Android!
Now, let's do some math. Android is made / sponsored / supported by Google. YouTube is Google subsidiary. Two plus two gives four. Guys at Android dev team made their homework, titled "I don't give a shit what user wants", very well!
There are two ways of deleting a message in Gmail. You can delete entire thread (by using Delete button) or just one message in it:
The second delete won't be replicated in mobile Gmail. You will see this message still appearing in given thread, just as you would ever delete it. You must purge Bin folder in order to get this message delete in mobile Gmail.
Another fuckup discovered in Android... and in mindless heads of Google dev fucks.
There are many, many huge fuckups in Android 4.0. About most of them I wrote in a separate article. But dropping the native-USB support in favor of some lame shit and extreme useless stupidity, called MTP (Mobile Transport Protocol), seems to be so devastating fuckup, that it surely deserves for a separate article.
...continue reading "Android and a shit called MTP"
Google managed to waste and fuckup even such simple thing, like calendar!
Extremely basic, every-day-use tool that should offer maximum comfort, actually pisses off with many small, irritating bugs. Bugs, that Google calls "features" and is not going to fix then at all.
We all know that kind of approach, right? Google-thinks-user-is-a-shit(tm). They know better what you need or want. They think, you're a useless shit.
...continue reading "Mobile Google Calendar fuckups"
There are new, enhanced security settings in KitKat, which causes, that you (the device owner) can't copy files directly to
Downloads folder. Well... you can, only these files are not visible on your device once you access this folder. This is first of fuckups on Android 4.4 KitKat. And so... the Google Android Fuckup Saga continues.
...continue reading "KitKat Fuck — The Fuckup of the Year 2014"
Android 4.2 JellyBean has come to my phone this night, so Android Fuckup saga continues. Of course, again, I have lost my nearly entire data plan, during middle of the night, because on of the biggest Android 4.2 fuckups is, that it again download system updates via GPRS, giving a damn shit, whether user decided to update everything via WiFi only.
...continue reading "Android 4.2. Next child in fuckup-saga!"
This short post contains some fuckups I found in mobile Dropbox. Both in Android app and in mobile website version of dropbox.com.
Two of them are just tiny and many users will probably ignore them. But third one is a big mother fucker, which in certain situations may lead you to data lost. All these were found in Dropbox for Android 2.1.8, running on Galaxy Nexus with Android 4.1.1.
...continue reading "Stupid bugs in mobile Dropbox"
I've started to play Optime Software's Chess (website, Google Play, iTunes) on my Android device and I actually liked that game. I was happy to find out that they've released an iOS version for my iPad as well.
The dream has come to an end when I realized that this is one of the worst chess engines in the world, with many stupid errors and huge fuckups included.
...continue reading "A chess engine that don’t know chess rules?"
Android 4.1 came down to my hands, so Android Fuckup Saga continues. Here, you'll find only fresh cookies. I'm not repeating old ones (which you can find here), since this is quite boring. But, yes, there are certain things wasted in 4.0 or even 2.3 and still not fixed up in 4.1. This article is the smallest one in Android Fuckup Saga, because even before finishing and publishing it, an Android 4.2 was released. Thus, most of the bugs (still not fixed in 4.2) went there.
...continue reading "Android 4.1 on Google Nexus is also a shit"
This problem is mentioned in following sources:
In short: after update to Android 4.1 you have two voices in Google Navigation:
- clearly sampled, human voice, giving you driving directions,
- ugly, crapy, TTS (Text-to-Speech) computer voice, trying to read nearly everything.
What is the worst, the second voice does not rely on driving or location data received from Navigation. Instead, it tries to read everything, what it "sees" on screen. So, if you have 350 meteres to turn, you'll hear "turn left in 350 em" (yes, "em", not "meteres", just "em")!
...continue reading "Two voices in Google Navigation"
...and why do I hate Google?
Samsung Galaxy Nexus phone is my first mobile device equipped with Android 4.0. I have never used that system before, so here is a bunch of my first-minute discovers and opinions. Keep in mind, that I'm using a "pure", Google-like Android 4.0. If you're using some modded version of Android or a vendor-specific version, provided by other producer than Samsung, you may not find some of these problems on your phone.
...continue reading "Why Android 4.0 on Samsung Galaxy Nexus is a shit…"
Nullsoft, Inc. has finally fixed a bug that caused Mobile Winamp Pro to stop working at all under Android 4.1 JellyBean.
I think this is the first such situation in the entire history of IT, that a major, world-wide know company needs TWENTY SEVEN DAYS (since initial report) to fix a bug that was causing their paid application to be completely useless.