"I have deleted the wake lock detector app, after which the device would at least sleep"
What?
No, let me try again:
Whaaaat?
That's gotta get the "best comedy" award at the Oscars.
I did not claim it was logical or explainable. If it was funny, well, please enjoy! Who do I complain to that my Oscar has not arrived?
Maybe my post has lost or gained something in Russian? I doubt it, and wish my Russian had been a tenth as good as your English!
Clearly what I reported as a consequence was more likely a coincidence.
I found several problems after the update, but none with AM:
+ a few apps had 'android robot' icons instead of the right ones.
+ a few apps had two icons - one correct, one android robot.
+ opening a file or attachments for example .doc files resulted in the appearance in the list of several icons for the same app, including four for the printing app I referred to.
A reboot did not change any of this. I eventually uninstalled every app that appeared several times in his way.
+ the battery charger seemed suddenly to not be able to keep up with power drain.
As part of this last problem, I looked at the battery usage graph and found the device APPARENTLY "awake" 100% while the device was on charge but not in use for some hours. I had not then spotted the fact that charging current was also low.
I uninstalled wake lock detector app, as I had never intended to keep it. I only got it while some people were commenting about aqua mail keeping the device awake, but for me this was not a problem. WLD also had a robot icon so was uninstalled because of that, too. After I had uninstalled it but not, perhaps, BECAUSE I had uninstalled it, the battery usage graph showed the device no longer always awake.
After uninstalling several apps, and reinstalling them, the icons are now correct again, there are no duplicate entries in the 'open using.....' List.
I never reinstalled the wake lock detector app. Probably innocent of all charges but I don't need it anyway. So please laugh away. As a kid I avoided the bears by avoiding the cracks on the pavement. Seemed to work - no bears! That was not logical either, and looking back, quite funny.
The one outstanding problem is that the charger runs at a too low current, unless I unplug the usb cable from the charger end and replug it. Never seen this before the update. Seen consistently since. For this I can only assume the update has somehow influenced the negotiation between the charger and the device. Timing is the only thing I can think of (based on looking at the USB spec). Even so, I expect this to be in hardware, so still mysterious...
I have a nice screenshot that shows the slope of the charging curve suddenly about five times steeper (or more) after unplugging and replugging the charger cable.
