Database Users

Non-English language support

Stock Android currently doesn't support Sanskrit/Hindi (Devnagri lipi Character Set). I see Square boxes like ☐ instead of characters अ आ इ ई उ ऊ on Unicode or UTF8 compliant Hindi websites. Even Google Hindi website doesnt open properly through my HTC Hero's stock Android 1.5 browser or any other browser like Dolphin, etc.
Has anyone figured out how to support Non-English fonts like Devnagri lipi (Sanskrit/Hindi) fonts in Android OS? I want to change my default font to see Devnagri numerals: ०,१,२,३,४,५,६,७,८,९ instead of Roman numerals: 0,1,2,3,4,5,6,7,8,9. I want my clock to use Devnagri numerals instead of Roman numerals.
Can someone please help?

prateekandroid said:
Stock Android currently doesn't support Sanskrit/Hindi (Devnagri lipi Character Set). I see Square boxes like ☐ instead of characters अ आ इ ई उ ऊ on Unicode or UTF8 compliant Hindi websites. Even Google Hindi website doesnt open properly through my HTC Hero's stock Android 1.5 browser or any other browser like Dolphin, etc.
Has anyone figured out how to support Non-English fonts like Devnagri lipi (Sanskrit/Hindi) fonts in Android OS? I want to change my default font to see Devnagri numerals: ०,१,२,३,४,५,६,७,८,९ instead of Roman numerals: 0,1,2,3,4,5,6,7,8,9. I want my clock to use Devnagri numerals instead of Roman numerals.
Can someone please help?
Click to expand...
Click to collapse
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
http://www.wazu.jp/gallery/Fonts_Devanagari.html
Click to expand...
Click to collapse

pseudoremora said:
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
Click to expand...
Click to collapse
Thank you for a prompt reply. The website you suggested is very helpful and I think Mangal or Arial Unicode MS are the best bet. It took me a while to find these fonts, sorry for a little late response.
Unfortunately, I could only find Mangal.ttf (201 KB) & ArialUni.ttf (22 MB) but not their respective "-Bold.ttf" fonts as you mentioned.
I can use Mangal.ttf in MS Office 2007 to write in Sanskrit/Hindi and it lets me format the text (bold, italics, resize, etc.).
Would it be enough to push this one font? Since Mangal-Bold.ttf is not available specifically.
Also, does pushing a font to ADB means that it overwrites the new font over the existing font in Android? Since we'll be renaming new font to already existing DroidSans.ttf. Or does it merge the two fonts?
I have attached Mangal.ttf (in a zip) to this post since that has a smaller size (201 KB) than ArialUni.ttf (22 MB). Would really appreciate if you could please create an Update.zip with proper files?
Thanks for your help!

prateekandroid said:
Thank you for a prompt reply. The website you suggested is very helpful and I think Mangal or Arial Unicode MS are the best bet. It took me a while to find these fonts, sorry for a little late response.
Unfortunately, I could only find Mangal.ttf (201 KB) & ArialUni.ttf (22 MB) but not their respective "-Bold.ttf" fonts as you mentioned.
I can use Mangal.ttf in MS Office 2007 to write in Sanskrit/Hindi and it lets me format the text (bold, italics, resize, etc.).
Would it be enough to push this one font? Since Mangal-Bold.ttf is not available specifically.
Also, does pushing a font to ADB means that it overwrites the new font over the existing font in Android? Since we'll be renaming new font to already existing DroidSans.ttf. Or does it merge the two fonts?
I have attached Mangal.ttf (in a zip) to this post since that has a smaller size (201 KB) than ArialUni.ttf (22 MB). Would really appreciate if you could please create an Update.zip with proper files?
Thanks for your help!
Click to expand...
Click to collapse
It's fine that you only found the regular font without it's bold counterpart. What can be done is that we'll use Mangal.ttf twice and rename it Droid-Sans.ttf as well as Droid-Sans-Bold.ttf. The system will accept it, though if you can find a font with both the regular and bold files, that would be nice.
Also, when you adb push the new renamed fonts into the /system/font folder -- they will indeed overwrite the previous fonts that were there. They will NOT be merged.
In anycase, I've created an update.zip file for you to flash. Tell me what happens.

pseudoremora said:
It's fine that you only found the regular font without it's bold counterpart. What can be done is that we'll use Mangal.ttf twice and rename it Droid-Sans.ttf as well as Droid-Sans-Bold.ttf. The system will accept it, though if you can find a font with both the regular and bold files, that would be nice.
Also, when you adb push the new renamed fonts into the /system/font folder -- they will indeed overwrite the previous fonts that were there. They will NOT be merged.
In anycase, I've created an update.zip file for you to flash. Tell me what happens.
Click to expand...
Click to collapse
Thank you for the file pseudoremora. Really appreciate it.
So if these new fonts will overwrite the previous fonts, I hope I don't loose my current stock fonts & style. Just for knowledge purposes; Did you manually merge "Mangal" font into stock fonts?
As far as I know, I would need to root my phone for flashing this file. I have never done it before. But I found steps for it on Unlockr (don't know if I can mention other websites on this forum). I am mentioning the steps below for other people's references, assuming these haven't changed:
Code:
1. Download the following file and then unzip it.
AsRoot2
2. Take the unzipped file and save it into the Tools folder of your AndroidSDK.
3. Plug your phone in via USB and do NOT mount the SD card.
4. Open the Command Prompt and type the following (hitting enter at the end of every line):
cd\
cd AndroidSDK\Tools\
adb devices
And make sure your phone’s serial number pops up (if not setup ADB & USB drivers).
5. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
6. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Although, I don't know how to unroot the phone after rooting it.
pseudoremora, I have been searching for steps on how to flash a file like "Mangal_font-signed.zip". But since "flash" is such a term that most search results are for Adobe Flash. Do you know any place with step by step instructions to do it for Sprint HTC Hero?
Also, if these fonts don't work. How do I go back to stock condition? Do I need to take some backup?
Thanks for your help.

prateekandroid said:
Thank you for the file pseudoremora. Really appreciate it.
So if these new fonts will overwrite the previous fonts, I hope I don't loose my current stock fonts & style. Just for knowledge purposes; Did you manually merge "Mangal" font into stock fonts?
Click to expand...
Click to collapse
You should have rooted first before thinking about anything else, but that's alright. Also, I did NOT "merge" the fonts... you can't do that. I overwrote the previous font with the Mangal one. Even if you flash a new font, getting the stock font back on is just as easy as adding a different one.
prateekandroid said:
pseudoremora, I have been searching for steps on how to flash a file like "Mangal_font-signed.zip". But since "flash" is such a term that most search results are for Adobe Flash. Do you know any place with step by step instructions to do it for Sprint HTC Hero?
Thanks for your help.
Click to expand...
Click to collapse
Before we go any further, its imperative that you root your phone and understand the in's and out's of flashing, using command prompt, and the installing recovery image. Also, you do own a CDMA Hero, for the Sprint network, correct?
All of the information you are trying to find can be found right HERE on XDA. The link will provide step-by-step guides that will walk you through everything you are trying to learn. I would advise reading them, following the steps the best you can, and then asking questions when you get stuck.
I can give the answers, however... with anything new, it's always best to let ones own curiosity invoke the learning process. Myself and others here are more than knowledgeable to help you any way, but even a beginner is capable of rooting there own phone.
prateekandroid said:
Also, if these fonts don't work. How do I go back to stock condition? Do I need to take some backup?
Click to expand...
Click to collapse
Upon rooting your phone and installing a recovery image, you will have the option to backup your phone and ALL its data. Secondly, if for some reason, you do in fact mess up and get to a point where you would like to start from the beginning (Go back to Stock), there is also an application for that.
So, for the time being -- don't worry about backing up your phone or even going back to stock, you need to focus on rooting your phone, installing a recovery image, making your first Nandroid backup, and then hopefully installing your first user created ROM.
As always, I'm here to help. Oh, one more thing... before you ask me, try to search the CDMA Hero threads, you'll more than likely find your answer. Otherwise, you can ask.

pseudoremora said:
You should have rooted first before thinking about anything else, but that's alright. Also, I did NOT "merge" the fonts... you can't do that. I overwrote the previous font with the Mangal one. Even if you flash a new font, getting the stock font back on is just as easy as adding a different one.
Before we go any further, its imperative that you root your phone and understand the in's and out's of flashing, using command prompt, and the installing recovery image. Also, you do own a CDMA Hero, for the Sprint network, correct?
So, for the time being -- don't worry about backing up your phone or even going back to stock, you need to focus on rooting your phone, installing a recovery image, making your first Nandroid backup, and then hopefully installing your first user created ROM.
As always, I'm here to help. Oh, one more thing... before you ask me, try to search the CDMA Hero threads, you'll more than likely find your answer. Otherwise, you can ask.
Click to expand...
Click to collapse
Thanks pseudoremora. Will do.
In case of an issue, I may have to bug you again.
PS: Yes, I do have CDMA Sprint HTC Hero with Google written on its back cover

prateekandroid said:
Thanks pseudoremora. Will do.
In case of an issue, I may have to bug you again.
PS: Yes, I do have CDMA Sprint HTC Hero with Google written on its back cover
Click to expand...
Click to collapse
Hope my last post didn't come as asshole-ish. That wasn't my intention. I'm just trying to get you in the mindset to always think about searching for the answer(s), before I step in and give them to you.
Also, you're not bugging me at all, I'm more than happy to help.
Good luck!

pseudoremora said:
Hope my last post didn't come as asshole-ish. That wasn't my intention. I'm just trying to get you in the mindset to always think about searching for the answer(s), before I step in and give them to you.
Also, you're not bugging me at all, I'm more than happy to help.
Good luck!
Click to expand...
Click to collapse
Na dude. You're fine.
So I am now rooted, recovered (v1.6.2), nandroid backed up (stock v1.5) & running DC v2.07.2. I flashed Mangal.zip. Good news is that I can now read Devnagri on Dolphin bowser. Glyphs are messed up. So instead of शिवाय it is showing शविाय. But its Ok, at least its readable. Better than ☐☐☐☐☐.
However, the bad news is that English characters are all bigger & spacier than normal. It looks so weird. Will attach a screenshot tomorrow.

prateekandroid said:
Na dude. You're fine.
So I am now rooted, recovered (v1.6.2), nandroid backed up (stock v1.5) & running DC v2.07.2. I flashed Mangal.zip. Good news is that I can now read Devnagri on Dolphin bowser. Glyphs are messed up. So instead of शिवाय it is showing शविाय. But its Ok, at least its readable. Better than ☐☐☐☐☐.
However, the bad news is that English characters are all bigger & spacier than normal. It looks so weird. Will attach a screenshot tomorrow.
Click to expand...
Click to collapse
Excellent! Seriously, that's amazing that you were able to accomplish everything I stated without having me helping you (not that I wouldn't have), but I'm sure you know that you get a great feeling once you accomplish each one of those things (I know I did when I first did it).
Again, great job!

pseudoremora said:
Excellent! Seriously, that's amazing that you were able to accomplish everything I stated without having me helping you (not that I wouldn't have), but I'm sure you know that you get a great feeling once you accomplish each one of those things (I know I did when I first did it).
Again, great job!
Click to expand...
Click to collapse
Dude, I am sorry for being MIA. I have been trying for a few days the merged font that I created using FontLab but it makes English characters so bloated that two lines start overlapping each other. For eg. if you are looking at a specific contact in people App, "Call mobile" text overlaps the cell number right below it.
Wats weird is that FontLab doesn't bloat Devnagri characters but only English characters. I dont know FontLab very well so dont know how to stop it from scaling.
I had to revert to stock font. S**ks!
Do you have any suggestion of some way to merge Stock font with Mangal font?

prateekandroid said:
Dude, I am sorry for being MIA. I have been trying for a few days the merged font that I created using FontLab but it makes English characters so bloated that two lines start overlapping each other. For eg. if you are looking at a specific contact in people App, "Call mobile" text overlaps the cell number right below it.
Wats weird is that FontLab doesn't bloat Devnagri characters but only English characters. I dont know FontLab very well so dont know how to stop it from scaling.
I had to revert to stock font. S**ks!
Do you have any suggestion of some way to merge Stock font with Mangal font?
Click to expand...
Click to collapse
I've never had to merge any fonts; but then again I've only had to read English.
I've never worked with Fontlab, so I'm not sure where to even begin. The reason however I think you keep having problems is because maybe the phone isn't understanding how to handle the merged font... so the Devnagri characters are okay, but the English ones aren't scaled correctly because they were merged or merged incorrectly? Again, I don't know, those are just my ideas.
I hate to say it... but it looks like you're either have to bare with it, choose one font or the other, or what I would do is contact HTC and see if they have native font or any font that they could recommend. I'm all out of ideas, so I don't know what to tell you. Sorry.

Try this
http://forum.xda-developers.com/showthread.php?t=798380
Replace only Fallback font. Do not touch DroidSans.ttf
Hope it helps

But there are issues in having hindi support in this way.
There is Samsung Galaxy phones with perfect hindi support in 2.1 and 2.2 versions of Android. Is there any way to get the Language pack or Hindi IMI from them. And have heard Android 2.3 has bulit-in Hindi language support. But I don't know how to install it.

Opera mini can read hindi font
Opera mini can read hindi font
click here

pseudoremora said:
The problem is obviously with the font and Android being unable to recognize it -- which leaves me to believe that the fonts you're trying to use are UNI-CODE and actually should be TTF (True Type Face). However, I would try different variants of the font you're looking for. I did some searching and this is what I've found (below). I don't know what characters I'm supposed to look for, but the site I found seemed somewhat helpful and apparently they might have the fonts you're looking for. If so, you need to push the font files you find to your /system/fonts/ folder of your phone -- but HAVE to rename the the font files. One needs to be called DroidSans and the other DroidSans-Bold -- Case sensitive for both.
If you'd like -- I can make an update.zip file for you instead. All you would need to do however it tell me which font you are considering and either upload the font here or give me a link where I can download and package it. Hope that helps.
Just remember that IF and when you find the font file you need, that it has an .ttf extension -- which is where I think your problem is.
Click to expand...
Click to collapse
Problem is most of the world has now moved to the unicode fornts from google transliteration which has become defacto standard due to ease of use. If that helps. Any help would really be very useful.

[Q] Swype with voice icon

Has anyone ported or got a version working on the vibrant. I have seen it on the droid x and on one of the newer HTC's

If you can get me the swype apk from one of those devices i can bring it over no problem at all i just havnt found a system dump for either but to be fair i havnt really been looking.

I have been looking but posting the file has been banned. I was hoping it was possibly included in the new froyo build or perhaps some of the newer European builds. I might be able to get a copy off a droid x or evo 4g if you can pull it with titanium backup, would I be able to just straight load it up with apploader?
Thanks for all your help I am just learning so will of course have lots of questions

adm1jtg said:
I have been looking but posting the file has been banned. I was hoping it was possibly included in the new froyo build or perhaps some of the newer European builds. I might be able to get a copy off a droid x or evo 4g if you can pull it with titanium backup, would I be able to just straight load it up with apploader?
Thanks for all your help I am just learning so will of course have lots of questions
Click to expand...
Click to collapse
Ahh that is right i forgot all about that lol, if you wanna hit me up on skype or anything pm me i'll give you my info i may have it on my profile.

anyone get this working?

th3fallen said:
If you can get me the swype apk from one of those devices i can bring it over no problem at all i just havnt found a system dump for either but to be fair i havnt really been looking.
Click to expand...
Click to collapse
Here you go
http://forum.androidcentral.com/sprint-epic-4g/29804-epic-4g-system-dump.html
This has the swype version with the voice button

Eazail70x7 said:
Here you go
http://forum.androidcentral.com/sprint-epic-4g/29804-epic-4g-system-dump.html
This has the swype version with the voice button
Click to expand...
Click to collapse
There's another thread about this, but it had a non-obvious title. I posted some stuff in there, but I'll repost here as people are more likely to find it.
Get the Swype.apk from the dump, no I can't post it here for you. The Swype company has asserted their copyright and XDA won't violate it.
Open a text field and change keyboards so Swype isn't active.
adb pull /system/app/Swype.apk Swype.backup
Don't install it, just copy it over the one on your phone. I used this:
adb push Swype.apk /system/app/
Root explorer, SUFBS, etc. can do it. Yes, you need root. Just do it, it's drop dead simple.
Now, switch back to Swype keyboard using the long-press on a text field. You have a voice button. The down side I found, was that the popup window with word choices is yellow with white text. Talk about hard to read. I'll attach a MetaMorph that fixes that.
Just download my Morph, then go to the Market and download the MetaMorph application. Launch Metamorph and let it do its checks. You should have a mostly empty screen with 2 buttons at the bottom. Select "Unzip/Extract new theme". Now use the file browser to find the file you downloaded. It's probably in /sdcard/download if you downloaded in the browser. Select the ZIP and it will tell you about the morph. Just hit "apply all" at the bottom and let it do it's thing. Now your Swype popup will look stock with the black background.

Weird, I'm running Vibrant6 and the epic swype does not work as outlined here. The kb opens, but the 2 lower left and 2 lower right buttons are blank. The kb doesn't respond to input either, showing the blue error outline around the kb.

Actually, when I reverted back to the stock swype, I had the same missing buttons and lack of functionality. I then installed the epic swype (by executing the apk), uninstalled it, and the old Swype started working again.

ttabbal said:
There's another thread about this, but it had a non-obvious title. I posted some stuff in there, but I'll repost here as people are more likely to find it.
Get the Swype.apk from the dump, no I can't post it here for you. The Swype company has asserted their copyright and XDA won't violate it.
Open a text field and change keyboards so Swype isn't active.
adb pull /system/app/Swype.apk Swype.backup
Don't install it, just copy it over the one on your phone. I used this:
adb push Swype.apk /system/app/
Root explorer, SUFBS, etc. can do it. Yes, you need root. Just do it, it's drop dead simple.
Now, switch back to Swype keyboard using the long-press on a text field. You have a voice button. The down side I found, was that the popup window with word choices is yellow with white text. Talk about hard to read. I'll attach a MetaMorph that fixes that.
Just download my Morph, then go to the Market and download the MetaMorph application. Launch Metamorph and let it do its checks. You should have a mostly empty screen with 2 buttons at the bottom. Select "Unzip/Extract new theme". Now use the file browser to find the file you downloaded. It's probably in /sdcard/download if you downloaded in the browser. Select the ZIP and it will tell you about the morph. Just hit "apply all" at the bottom and let it do it's thing. Now your Swype popup will look stock with the black background.
Click to expand...
Click to collapse
Where is that other thread located? Whats the title?

I am having the same problem as the previous poster that gets the keyboard, but no swype buttons, input, or typing ability. I attempted to overwrite the swype.apk with the epic swype.apk using Root Explorer. What do I need to do differently?

iamosborne said:
I am having the same problem as the previous poster that gets the keyboard, but no swype buttons, input, or typing ability. I attempted to overwrite the swype.apk with the epic swype.apk using Root Explorer. What do I need to do differently?
Click to expand...
Click to collapse
Add another to this list. Exactly the same. It wouldn't let me push the file back
Code:
C:\Users\TJHart85\Desktop\Vib_Phone\_REPLACEMENT_FILES>adb push Swype.apk /system/app/
failed to copy 'Swype.apk' to '/system/app//Swype.apk': Permission denied
C:\Users\TJHart85\Desktop\Vib_Phone\_REPLACEMENT_FILES>adb push Swype.apk /system/app
failed to copy 'Swype.apk' to '/system/app/Swype.apk': Permission denied
I then used Root Explorer to copy the new APK to /system/app/
I then got the same keyboard as others have that doesn't accept any input.
Putting the original file back didn't make it work again either, so I'm doing a nandroid restore back to a few hours ago (luckily I replaced a few system files earlier and had decided to make a nandroid just in case).
The only non-stock part of my phone is that I have SIM-unlocked it & applied the lagfix ...lagfix makes it take forever to restore too :-(
Restarting did not make a difference.

Eazail70x7 said:
Where is that other thread located? Whats the title?
Click to expand...
Click to collapse
Something like "why can't we do this"... Not sure why they used that.
Note that I am using the EVO swype, NOT the Epic one. And you have to REPLACE the existing Swype. DO NOT USE THE PACKAGE INSTALLER. You have to place it with adb or something like root explorer should work. It must OVERWRITE the existing one. Make a backup of your Swype so you can get back to it. There should be no reason to have to restore a Nandroid with this mod.
If adb push gives you a permission denied, you have the system mounted read-only or don't have root. Try the JAC kernel, that's what I'm using, and it worked fine. I don't know or care if it works with the stock kernel, the JAC is that much better.

Can you tell me which version of the EVO swype has the speech to text feature? I have a 1.56 apk, but i believe there are more recent versions.

I am using 1.57.32.7688 from evo and it works perfectly

Wow... I have just been through the whole process of adding this to my phone and I must say I have learned a lot! So I figured i'd share for anyone who might benefit:
The main reason it was so hard for me is because I am running eugene373's vibrant7 rom and in that rom swype is removed by default. This allows you to just install the swype file (swype-evo-tts.apk) using package installer without any troubles. *BUT* It makes the Swype_No_Yellow.zip not work. This is because when swype is installed stock it's in the system/app folder but when it's just installed as a regular app it's in a different folder(data/app).
Sooo I went and taught myself how to edit .apk files! Yay!
This thread was AMAZINGLY helpfull: forum.xda-developers.com/showthread.php?t=503007
So basically I followed the steps in that thread except I moved the files in Swype_No_Yellow.zip to the corresponding folder in swype-evo-tts.apk using 7-zip. Then I used the auto-signing tool and tada! I have swype tweaked perfectly for me!
[rant] It sure would be nice if I could just post up the file I created and save y'all the trouble. But I understand the forum rules. I just think everyone coming to this forum has vibrant and has payed for swype! We sure as heck can tweak it as we please, but why can't we upload those tweaks and share amongst ourselves?! The real question is why didn't swype just include a text to speech button on the vibrant?!?! [/rant] Oh wellz
Good luck!

Yes, the morph looks for it in /system/app as that's where I told people to install it.
You could have just modified the morph xml file to point to /data/app, but understanding apk files is very useful if you want to play with the phone at this level.

tt, I've been looking with no luck for the evo swype. Got a link?

ytj87 said:
tt, I've been looking with no luck for the evo swype. Got a link?
Click to expand...
Click to collapse
I don't, sorry. I downloaded it from an XDA thread before the mods caught it. I don't think we are even supposed to link from here. Irritating.
I'd host it myself, but I don't feel like joining Cyanogen in the C&D club.

This didn't work for me I tried to use Vibrant1.zip version of swype to revert back with root explorer and that didn't work so I had to do a nandroid restore, I wouldn't try this you would think it would just work but guess not.

[Q] MMS.apk missing?

I have a stock Nexus 4, not rooted. I'm trying to update the MMS.apk to a version I found online, to customize the app to my liking.
I'm told to use Root Explorer, go to /system/app, and replace MMS.apk.
I went there to try it, and can't even find MMS.apk. My stock messaging app works perfectly fine, so I know it's somewhere...
What am I doing wrong?
I've attached a picture of what things look like.
EDIT: I found a search function on Root Explorer, which tracked down the file in /system/priv-app.
I apologize for making this thread. I did plenty of research before posting here, but never considered the search function. (I don't use Root Explorer normally. I downloaded it just for this.)

Mellowmarrow said:
I have a stock Nexus 4, not rooted. I'm trying to update the MMS.apk to a version I found online, to customize the app to my liking.
I'm told to use Root Explorer, go to /system/app, and replace MMS.apk.
I went there to try it, and can't even find MMS.apk. My stock messaging app works perfectly fine, so I know it's somewhere...
What am I doing wrong?
I've attached a picture of what things look like.
Click to expand...
Click to collapse
First question would be, what version of Android are you running? Secondly, which might be the most important point is, unless you are trying to install a third party app from the Play Store, the mms app is normally installed as a system app. Since you are not rooted, you won't have access to it.
Sent with my Nexus® 10 minus 3

Building first ROM for G900V

Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake

jake5253 said:
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
Click to expand...
Click to collapse
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app

elliwigy said:
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the response!
It seems perhaps I didn't quite make clear what I've done versus what I'm trying to accomplish.
Firstly, I wouldn't go so far as to say I'm "having so many issues". Everything in my ROM is in perfectly fine working order. I just have these few quirks that I would like to address both so I can learn, and to make this and future projects better.
While I appreciate the recommendation to use bean's base, I have taken a look at his and there seems to be nothing in his which copies data into /data/data/com.whatever.package (or at least there's nothing in his zip in the /data/data folder -- not sure if his ROM has the toggle activated?)
I have the Apps working correctly in my ROM -- they just go in /data/apps, /system/app or /system/priv-app, respectively.
What I need, is to get /data/data/com.whatever.package/ copied With Correct Permissions when the ROM is installed; I do not want a second zip to update things after install, especially for a toggle and a couple shortcuts, seems silly.
For instance, when you boot your phone up with the default [stock] samsung launcher, it has a list of default apps and widgets on the first screen you see such as phone, messages, a clock widget, etc, etc. Since I've replaced the stock launcher with Holo Launcher HD and some other default apps have also been replaced, there's very few shortcuts on the main launcher screen.
** Holo Launcher does have a list of default apps it adds to your main page, but many of those have been removed in my rom.
The solution I've come up with basically waits for the system to boot up to the point that Holo Launcher actually creates the default (mostly blank) /data/data/com.mobint.hololauncher.hd/databases/launcher.db and then my script uses sqlite3 to update the DBs with a list of different shortcuts -- ones to apps that actually exist.
The Hotspot Toggle is the same way as above.. Hotspot works fine in my rom if you go through settings!
I just cannot add the notification panel pull-down toggle to /data/data/com.android.providers.settings/database/settings.db until after the system boots up at least ONE time, and then update the DB to include WiFiHotspot in notification_panel_active_app_list and notification_panel_active_app_list_for_reset
As for the zipalign and deodexing, I will have to try those again now that I have a fairly stable rom.
****EDIT****
I think I figured it out. I can just use busybox to kill the systemui after I update the databases during the first boot. I also figured out how I can add the SetupWizard without it locking up on activation.
Thanks anyways, guys.
Look for my rom, coming soon!
=P

Please add support for more languages
I found a mod for Motorola latest 4.4 please port it
Sent from my SM-G900T using XDA Free mobile app

How to get IOS emojis on xt1575?

Is there a way yet to get the IOS emoji set system-wide on the xt1575? I don't ever want to see the built in android emoji set. I'm running stock rooted marshmallow 6.0.

kettir said:
Is there a way yet to get the IOS emoji set system-wide on the xt1575? I don't ever want to see the built in android emoji set. I'm running stock rooted marshmallow 6.0.
Click to expand...
Click to collapse
You can replace your emoji's to look however you want if you can find a properly formatted ttf file for it. You just backup and replace /system/fonts/NotoColorEmoji.ttf with your new font file, make sure permissions are set right (644), and reboot.
I've done some meddling with emojis on the 6.0 stock ROM, but not ios ones. This thread looks like it might have what you need.

Thanks for the advice. I did take a look at that thread and tried copying the .ttf file into system/fonts with the appropriate permissions, but it didn't seem to change anything. I took a chance and ran emoji switcher, and it seems to have done the trick. I went for the ios 7 emoji set, rather than the later set(s), due to the multiple colors of some of the later set icons that don't look right on a non-ios phone.