Has Tokyo 10.2.2 resolved bugs created in Berlin re Virtual Keyboard position on Android devices edit controls?

I was wondering if the problem of the Virtual Keyboard covering the active edit control has been resolved in Tokyo 10.2.2?

Prior to Berlin (It worked fine in Seattle and even APPMETHOD using the same code), when an edit control was active, you could workout where the Virtual Keyboard would be and scroll the active control into position so it was not obscured by the said Virtual Keyboard, but code that used to work simply doesn't work anymore. I was wondering if anyone had installed 10.2.2 and tested if it has been resolved, and if so, just what was fixed?

I am annoyed that after paying to upgrade to Berlin I have had to redesign all my data entry apps on Android to have just a few edit controls on screen so that the virtual keyboard doesn't block them, but this means extra work for the users, something they have complained about.

My subscription has just expired but I think that errors introduced into new versions that didn't exist before should be offered free of charge, for example, if my car engine developed a fault due to manufacturing issues and set on fire, the motor company would recall the car and resolve the issue at their own cost, not at the customers expense, so Embarcadero, you should do the same when you introduce bugs that previously didn't exist.