Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
183.amir said:
Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
Click to expand...
Click to collapse
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
imminentwill said:
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
Click to expand...
Click to collapse
I think this should either be provided by Google Hangouts app or we need to use a custom framework.
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Okay, so you changed the Emoji in your conversation to match your keyboard. What if I wanted to go the other way ’round and skin my keyboard Emoji to match what’s in the conversation?
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
herwegan said:
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
Click to expand...
Click to collapse
Well... I don't know. In my post, I basically just remove the emojis that HTC put in the Android system and let it fall back on the original emojis in KitKat, which is the same as the Hangouts.
If there is an emoji font inside the whatsapp APK, then it might be possible to rename it to "AndroidEmoji-htc.ttf", and put it in /system/fonts/. This way, your phone would think it's loading the HTC emojis, but in reality it would be the whatsapp emojis. Might be possible with any emoji font pack actually.
thank you this worked perfectly!
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
is there a way to do this without having root?
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
robgee789 said:
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'd love to find a non rooted solution as well. Anyone got any ideas?
IIIMik3 said:
I'd love to find a non rooted solution as well. Anyone got any ideas?
Click to expand...
Click to collapse
I also need a non rooted solution for my HTC One M8. This is driving me crazy.
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
Obviously I have not rooted yet. What type of root does this require to have permissions to do this? Thanks in advance.
Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
still hoping for a non-root solution to this. :fingers-crossed:
Me too mate but I don't think it's gonna happen
Sent from my HTC One using Tapatalk
Just run the weaksauce root for your HTC One M8 guys and you'll have no problems following the OP's instructions- literally takes 1 minute to root, 30 seconds to change the emoticons and you are good to go!
I rooted on my first day picking up the M8 and it's been awesome since
JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
IIIMik3 said:
still hoping for a non-root solution to this. :fingers-crossed:
Click to expand...
Click to collapse
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
trjlive said:
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
Click to expand...
Click to collapse
Ah, thanks for this! I'm glad I was able to get it to work with root explorer before this, but I'm glad I know how ES works now.
Hello everyone
I just want to get feedback on something... I use Go SMS Pro, but people using hangouts that I speak with, because I use the emoji provided by the app (iPhone emoji), they don't get most of them, which is very annoying... has anyone faced this? Is this happening just because of the emojis not being integrated? (If I press the button for emojis on the app, I get iPhone' s emojis, but not if i use the SwiftKey shortcut...)
Btw, I tried sending about 50 emoji. Hangouts got 25... :S
Sent from my GT-N5110 using XDA Free mobile app
I'm trying to stop the tethering check by editing the build.prop.
Everytime i edit (using numerous editors on my mac, including the terminal via vi) my device hangs on the google logo.
Stock Rom, rooted.
Any thoughts on why this would be?
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
Tried this too an nothing!
I can't figure this out for the life of me.
You need to copy the build.prop out to your SD card, edit with a proper editor, copy it back into place replacing the current file, and then change permissions to 755 I believe. I suggest keeping an unmodified version of the build prop on your SD card also
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
This thread should help a bit. I know its for the g3 but same premise. the permissions appear to be 644 not 755.
http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693
mhennigan1377 said:
Tried this too an nothing!
I can't figure this out for the life of me.
Click to expand...
Click to collapse
You set the partition to R/W using the little button at the top before making the edits?
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
Evo_Shift said:
You set the partition to R/W using the little button at the top before making the edits?
Click to expand...
Click to collapse
The whole partition or just the file? I was setting the file. Should this be R/W for Group and Other ?
mhennigan1377 said:
The whole partition or just the file? I was setting the file. Should this be R/W for Group and Other ?
Click to expand...
Click to collapse
In root explorer, explore to /system. Make the /system r/w (it'll have a r/o next to it so press the "Mount R/W"). Long press the build.prop file and select Open in Text Editor, make your changes and save & exit. Press "Mount R/O" at the top to change the /system back to read only. Reboot.
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
yup. just used this app this morning to edit the build.prop. no issues here
Got it that time, must have been not the system partition changes.
Thanks!!!
Hi amazing people, I need to change a line in /system/build.prop
Ive tried using Root Browser and ES file explorer but no joy, when I save it it doesn't actually save.
What am I doing wrong?
ScuzUK said:
Hi amazing people, I need to change a line in /system/build.prop
Ive tried using Root Browser and ES file explorer but no joy, when I save it it doesn't actually save.
What am I doing wrong?
Click to expand...
Click to collapse
Sony has a filesystem protection called RIC. You need to disable that. On unlocked bootloaders is easy, on locked i don't really know.
The only thing that kills RIC process is the @Nut XZDR recovery.
ScuzUK said:
Hi amazing people, I need to change a line in /system/build.prop
Ive tried using Root Browser and ES file explorer but no joy, when I save it it doesn't actually save.
What am I doing wrong?
Click to expand...
Click to collapse
do a factory reset from settings menu to fix the root acces problem . That's how i fixed it
At android 5.1 I can find it in path sdcard/android/obb but when upgrade to android 6.0 I find nothing. Can you guys show me where it located, please!
Thanks for watching!
huypq said:
At android 5.1 I can find it in path sdcard/android/obb but when upgrade to android 6.0 I find nothing. Can you guys show me where it located, please!
Thanks for watching!
Click to expand...
Click to collapse
It's still there just use a different file manager.. I use root Explorer and it's in /sdcard/Android/obb if you are using the stock file manager, it may not let you see it.
MrMike2182 said:
It's still there just use a different file manager.. I use root Explorer and it's in /sdcard/Android/obb if you are using the stock file manager, it may not let you see it.
Click to expand...
Click to collapse
I did use some file manager ex: Es Explorer, solid explore, root explorer but still can find this type of file. :crying:
huypq said:
I did use some file manager ex: Es Explorer, solid explore, root explorer but still can find this type of file. :crying:
Click to expand...
Click to collapse
Well we can just make it then! Lol.. What did you need the obb type for?