Browser issue Smileys don't work : Android / Chrome

[Rob]

Hi,

I'm running Android 4.4.4 and using Chrome 42.

When I click the Smiley in the editor to open the list of smileys and then click on a smiley, it does insert it into the editor.

However, once you post the reply the smiley isn't there it's gone.

This happens right here on Xenforo.com

 

[MattW]

Confirmed.

 

[Liam W]

Testing:

Unconfirmed...

Liam

 

[MattW]

New test

EDIT: My phone has just updated to Android 5.0.2, but on the previous version (Xperia Z3), smilies were blank when inserted.

 

[Martok]

It worked for me.

However, I've always had an issue with adding smilies on my Sony Xperia devices. If I try adding them and word prediction is enabled on my Xperia keyboard, the smiley is immediately removed after adding it. The workaround has been to add the smiley using the smiley code or to disable word prediction.

 

[Rob]

I'm on xperia device. It's not word prediction because the smiley is actually inserted in-line, at the cursor within the editor but it's not there when saving.

 

[Martok]

I'm on xperia device. It's not word prediction because the smiley is actually inserted in-line, at the cursor within the editor but it's not there when saving.

Mine inserts and then immediately removes the smiley and I see obj in the text prediction.

 

[Daniel Hood]

Mine worked.
Samsung note3

 

[imthebest]

Testing on Chrome (latest stable) on Android 4.4.2 in Note 3.

Smiley:

 

[Rob]

Actually, yes I see the same issue regards OBJ. Its a PITA as there are loads of xperia devices, very common.

 

[MattW]

Mine inserts and then immediately removes the smiley and I see obj in the text prediction.

View attachment 104546

This is exactly what I was having before the phone updated.

 

[Rob]

I have a lollipop update to apply soon.... hopefully that fixes it - I'll report back.

 

[Martok]

I've not installed my update as it's Lollipop 5.1 which has a memory leak bug. Waiting for 5.1.1 which is supposed to fix it.

 

[Mike]

Is that keyboard Sony/Xperia specific? That may be related.

I can't reproduce this on a Nexus 5 running 5.1, either with the standard keyboard or SwiftKey. It sounds like this is specific to the Xperia line. Can you confirm with a different keyboard?

 

[Martok]

Is that keyboard Sony/Xperia specific? That may be related.

I can't reproduce this on a Nexus 5 running 5.1, either with the standard keyboard or SwiftKey. It sounds like this is specific to the Xperia line. Can you confirm with a different keyboard?

In my case, yes it is a specific Xperia keyboard. I do believe it's an issue with the keyboard and by the looks of it it's fixed in the next Android update on Xperia going by some posts above.

I've not reported this before as I didn't think this was a XenForo issue. I was only responding to the OP to say that I could get smilies to work (albeit by typing in the smiley code) and to point out my issues relating to the keyboard. It appears that the OP is also using an Xperia device and no-one else in the thread using other devices is having the issue. So I'd say that this is a device/keyboard issue that is resolved with the latest firmware update. I'll be waiting for Android 5.1.1 though as that's supposed to have the memory leak fixed.

 

[Rob]

I am definitely convinced it is keyboard / xperia specific as non of my other android devices have this issue. I too am waiting for 5.1.1 release in order to upgrade and I'll confirm this is resolved then. Thanks for looking at this though Mike.

 

[Liam W]

Do any of you people affected have rooted affected devices?

If so, could you upload the APK for the IME included to see if I can test it?

Liam

 

[Rob]

Can you run that by me again with a little more instruction?
You could just download any of the official xperia roms and extract it.
I'm not currently rooted, but I may be able to help if I knew exactly what I was looking for.

This might be it
http://www.devfiles.co/download/POL9cJ4M/Xperia_Keyboard_6.4.A.1.24.apk

 

[Mike]

I'm going to call this a keyboard/OS-customization issue then. (I don't think there's anything we really could do about it anyway.)