Not moving up message/chat keyin window on my Lumia 930 on from build 14390

[GeslinkDK]

Am I the only one with this very annoying problem?
I reported such on from 15-08-2016 by the Windows Mobile feedback hub under Problem > Calls and messages > Sms-, mms- or rcs-messages but no one upvoted til now.

Here is what I reported:
Writing Sms/chat in upright position on my Lumia 930 has become impossible because the new sms/chat input window is not moved upwards over the keyboard any longer but remains at the bottom of the screen. In case of sms I have to rotate to horizontal position for keying text in, but that doesn?t work for apps which can?t rotate as fx Wordfeud.

It happens in fact on all chat apps. Problem doesn't appear on my Lumia 920 which, for the time being, stays at version 1511, build 10.0.10586.494 although it is on English in the fast ring.

This very annoying problem is not solved in the update to build 10.0.14393.82; please fix it now!

Regards GeslinkDK.

 

[Indistinguishable]

I've had this problem before. But usually closing out the messaging app fixes it. The few times that it persists past that, i usually soft reset and that does the trick. Now this doesn't happen to me often.

How often does it happen to you?

 

[GeslinkDK]

Thanks, but nothing of what you mentioned and I executed again helps; it's for the first time and on from build 14390 the problem appears and it is there all the time.

 

[GeslinkDK]

Thanks, but nothing of what you mentioned and I executed again helps; it's for the first time and on from build 14390 the problem appears and it is there all the time.

I got on 23-08-2016 fixed the problem by a hard (factory) reset which did not affect the latest Windows 10 build 14393.82, but causes, in spite off backup, a lot of restore work.
I assume that the problem was caused by an malicious upgrade.

 

[John Brown24]

I have exactly the same problem. Can't believe there are so few of us.

I'm due a free upgrade in March but I will probably ditch Windows in favour of Android if there is no solution

:crying:

 

[Niel A]

Yes, do reset. It will fix the issue