Seite 1 von 1

Textinput on HTC Sense 5.0

Verfasst: Do 23. Mai 2013, 08:04
von ANILE8
Previously I owned a HTC ONE XL and using the standard email app everything worked perfectly.

With my new HTC ONE (M7) running Sense 5.0, I cannot use Textinput to type into the email body area.

However, the To, Cc and Bcc fields work fine on Sense 5.0 only the email body field is not responding.

Does anyone know what has changed?

Verfasst: Do 23. Mai 2013, 15:53
von FJ
What does happen when you try to type ?

Verfasst: Do 23. Mai 2013, 22:28
von ANILE8
The Textinput screen is just greyed out when it comes to the e-mail body area.

Other e-mail app's like K-9 Mail, G-Mail and MailDroid work fine but they have other issues that make them unacceptable for my use.

I would like to use the standard mail app V 6.0.565089



Bild

Verfasst: Sa 25. Mai 2013, 23:20
von FJ
I do not have the HTC One so i cannot reproduce the issue. What happens with the Soft-Input-GUI of MyPhoneExplorer on the phone when you reach the email field ?

Verfasst: So 26. Mai 2013, 01:39
von ANILE8
It looks just like normal.


Bild

Verfasst: Sa 1. Jun 2013, 23:36
von ANILE8
Still getting the below screen when in the email body area.

Hope there is a fix soon :(


Bild

Verfasst: Do 27. Jun 2013, 21:23
von FJ
Does the Info-Bar of MyPhoneExplorer's soft keyboard appear when you reach the email field ? Does other soft keyboards (not from HTC) work correctly with this field ?

Verfasst: Do 27. Jun 2013, 22:09
von ANILE8
No, the Info-Bar on MyPhoneExplorer's soft keyboard does not appear when you reach the email field.

It works find in the To, CC and BCC fields though.

However, MPE's soft keyboard works fine with everything else such as Aqua Mail, G-Mail, K-9 Mail and MailDroid.

I have been using WiFi Keyboard by Ivan Volosyuk when i need to type an e-mail as a work around.

Verfasst: Do 27. Jun 2013, 22:49
von FJ
Is your phone connected via USB to the PC ? If yes then please contact me via Skype-Chat (zillertaler6). I want to do some tests...

Verfasst: Sa 29. Jun 2013, 00:56
von FJ
We have found a workaround for this issue. In the next version of the client it will work partially