Related
first of all i would like to thank this forum and it's members, you have been a great source of G1 info for me, and i want to give something back .
this is a guide for installing fonts which will enable you to get rid of the annoying while boxes when you try reading something in a foreign language such as:
web pages
contacts
pretty much everything else
note that it does not alter your current English font, so no worries about font size not fitting buttons, etc.
this, of course, requires root access.
I haven't been able to find a comprehensive and full guide, so i made one:
1) download the DeJaVu fonts from here, they are freely licensed (so no worry about copyrights).
2) copy 'DejaVuSans.ttf' to your sdcard and rename it exactly 'DroidSansFallback.ttf'
3) start terminal emulator and type exactly (watch the Case) the following commands, followed by enter:
Code:
su (then wait for the superuser screen and press yes)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 4755 /system/fonts/DroidSansFallback.ttf
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot
your phone will now reboot, and vualla! you have your native language displayed! no more white boxes! Ha Ha Ha!!
note: if the dejavu fonts don't support your language, just find a font that does, and follow exactly the same procedure.
hope this helps someone, because I sure needed it...
cheers!
note: you might want to make this a sticky
Hi there
Thank you so much for the guide
Will this font work for Vietnamese?
Thanks
this will not support Arabic .. right ?
superxnova said:
first of all i would like to thank this forum and it's members, you have been a great source of G1 info for me, and i want to give something back .
this is a guide for installing fonts which will enable you to get rid of the annoying while boxes when you try reading something in a foreign language such as:
web pages
contacts
pretty much everything else
note that it does not alter your current English font, so no worries about font size not fitting buttons, etc.
this, of course, requires root access.
I haven't been able to find a comprehensive and full guide, so i made one:
1) download the DeJaVu fonts from here, they are freely licensed (so no worry about copyrights).
2) copy 'DejaVuSans.ttf' to your sdcard and rename it exactly 'DroidSansFallback.ttf'
3) start terminal emulator and type exactly (watch the Case) the following commands, followed by enter:
Code:
su (then wait for the superuser screen and press yes)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 4755 /system/fonts/DroidSansFallback.ttf
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot
your phone will now reboot, and vualla! you have your native language displayed! no more white boxes! Ha Ha Ha!!
note: if the dejavu fonts don't support your language, just find a font that does, and follow exactly the same procedure.
hope this helps someone, because I sure needed it...
cheers!
note: you might want to make this a sticky
Click to expand...
Click to collapse
It works great for me(Vietnamese fonts).
Thanks a bunch
h4ng0ver said:
It works great for me(Vietnamese fonts).
Thanks a bunch
Click to expand...
Click to collapse
These fonts 're different from Android fonts. Droidsans font family is a font pack which're specialy for Android phone.
wont open dd cant file
i paste the DroidSansFallback.ttf on sd root, and have problem on the last sentence
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
its says the file cant find
any help thanks
root access on G1 jesus frekes Dev1 Rc33
this will not support Arabic .. right ?
Click to expand...
Click to collapse
yes it will, enjoy
aacshar, try redoing it all over again, you probably mistyped some letter...
i have tried this several times and works like a charm, i am running jf1.41 RC33 also
Why can't JF put this in his releases, as a default font? I know that future android releases support locales, etc.... but why can't JF replace his release with this one so we don't have to redo this every time?
Thanks
Something went wrong, now "su" wont work, only flash black, then denied or something???
What now???
Trying to flash again, don`t want to wipe...
E: Reflash and works again...
But no help my fonts
ahmad.yousry said:
this will not support Arabic .. right ?
Click to expand...
Click to collapse
This will work for Arabic but the letters will be disconnected. I wrote about that solution in my blog a month ago:
http://dumpytips.blogspot.com/2009/01/arabic-on-t-mobile-g1half-solution.html
Read the comments if you are interested, we had an interesting discussion in there.
-Gus
I second the motion, JesusFreke - what do you say?
yochaigal said:
Why can't JF put this in his releases, as a default font? I know that future android releases support locales, etc.... but why can't JF replace his release with this one so we don't have to redo this every time?
Click to expand...
Click to collapse
why not?
Success
This works great thank you!
Edit - Now that this is working, we must ask how can we undo these changes? - Thanks!
you need to get hold of the original file, either by someone sending it to you, or by getting it out of an image.
these instructions just copy a file over an existing file, so use the same instructions again for the original font file.
JesusFreke: It would aid us all not native English speakers if you added this to your ROM. this is after all a feature. thanks
Thank you for your instruction. It's exactly what I need.
But my question is DejaVu Sans font comprises of 4 style: regular, italic, bold, bold-italic. The font has 4 files:
DejaVuSans.ttf
DejaVuSans-Oblique.ttf
DejaVuSans-Bold.ttf
DejaVuSans-BoldOblique.ttf
Why your instruction only use DejaVuSans.ttf file ? What if text in web page has italic, bold or bold-italic, how will it be displayed ?
Nathan Tran
I figured it out. Android will use DroidSansFallback.ttf for anything that it cannot display.
Nathan
1.5 gmail LTR
Hi, in the new version of JF 1.5 i tried it and the LTR isn't working on gmail application
just an FYI
superxnova said:
first of all i would like to thank this forum and it's members, you have been a great source of G1 info for me, and i want to give something back .
..........................
hope this helps someone, because I sure needed it...
cheers!
note: you might want to make this a sticky
Click to expand...
Click to collapse
cheers m8. brilliant (works fine on my HTC magic 1.5)
Just one question. So if I install someone's rom that doesn't have polish locale in it, all I have to do is to -dd this font file and I will have polish language in my phone? Or is it just for web browsing? Thanks in advance for any reply.
URGENT Pleeeeease
thank u for yr post but i'm sorry I dont understsnd the 3rd step...
3) start terminal emulator and type exactly (watch the Case) the following commands, followed by enter:
Code:
How to do ( start terminal emulator )???
And where i should type the code ????
NEED V.V. URGENT REPLAY
Thank u in dvance
g1lovermas said:
thank u for yr post but i'm sorry I dont understsnd the 3rd step...
3) start terminal emulator and type exactly (watch the Case) the following commands, followed by enter:
Code:
How to do ( start terminal emulator )???
And where i should type the code ????
NEED V.V. URGENT REPLAY
Thank u in dvance
Click to expand...
Click to collapse
Terminal means command prompt in Windows.
1. go to command prompt (window + R , type cmd , press enter)
2. cd to your androidsdk/tools/ (cd C:\AndroidSDK\tools\)
3. type this without quotes 'adb shell'
4. copy and paste this in command prompt
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. copy and paste this in command prompt
chmod 4755 /system/fonts/DroidSansFallback.ttf
before you do this
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
unmount OR turn off your sdcard
and then copy and paste this
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
6. reboot
That's all.
I have installed HTC ROM following this guide
http://www.karrderized.com/romguide/
so i think mine is already rooted. So when I type 'su', no problem for me.
Thanks to the person who posted this awesome tricks.
Cheers,
thihaz
Thanks to FollowingInsanity for editing the build.prop file to get it working corectly, and thanks to Maxisma for the Droid dump. Thanks to everyone else who pitched in on this whole thing. Really all I did was realize the exact line that needed to be changed....everyone else did the rest
Here are instructions on how I got the new maps w/ Navigation to work via adb. I'm running the official rooted 1.6 build, but this should work for anyone.
(if you don't know how you use adb, go to the here
Next, you need to uninstall the old maps.apk file and here's how I personally did it since you can't just go to "uninstall" from the Application Settings(these instructions start already in the ADB shell):
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd system
# cd app
# rm xxxxxxx (this is whatever your maps.apk is titled. sometimes is just maps.apk, but it could also be com.android.google.maps.apk or somethin like that)
# exit
Click to expand...
Click to collapse
Now you've uninstalled the google maps. You can then do these next steps outside of adb.(for instructions purposes i'm using my own Android location):
C:\android\tools> adb pull /system/build.prop C:\Android
C:\android\tools> adb pull /system/build.sapphire.prop C:\Android
The 2nd may not be may be build.trout.prop or something to that effect...build.xxxx.prop
Click to expand...
Click to collapse
Next, change those 2 file names on your PC from build.prop to build-backup.prop and build.xxxx-backup.prop(if you have one) so that you don't lose those files in case anything stupid happens in the mean time lol.
Make a 2nd copy of build.xxxx-backup.prop and rename it is build.xxxx.prop. So now you should have a build.xxxx.prop AND a build.xxxx-backup.prop
Now you'll need the build.prop file to use
build.prop
(IF you are running a sapphire build, you can also use the build.sapphire.prop file located there and skip down to "re-loading prop files")
I saved that file to the same location that I saved my original files.
open build.xxxx.prop in notepad. look for where it says:
ro.build.description=kila-user 1.6 DRC83 14721 ota-rel-keys,release-keys
ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys
# end build properties
Click to expand...
Click to collapse
you'll need to delete the line that says ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys but DO NOT delete the line that says #end build properties
replace the line you deleted with the following:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
Reloading Prop Files
next, back in your command line window do the following:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
then restart your phone
while the phone is restarting, go back and rename your build.prop and build.xxxx.prop files to build-update.prop and build.xxxx-update.prop, then change your build-backup.prop and build.xxxx-backup.prop to build.prop and build.xxxx.prop
After it restarts you'll want to locate your maps.apk file(the new one) and go back into your command line and type:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb install c:\android\maps.apk
(install crap...if it doesn't install correctly then don't do whats below)
Click to expand...
Click to collapse
Go check your google maps, type in two locations and click "go" and on the next screen you should see a button that says "Navigate"
go back to your command line screen and type:
Sorry if this is confusing, anyone who could make it more simple, please feel free to give it a try, but this is the best I could offer so people wouldn't have to go looking though the whole think tank thread to get everything they need to get it working
IF THE INSTALL GAVE YOU AND INVALID_UPGRADE ERROR THEN TRY THIS:
(again these instructions are using my own android sdk location, replace the
c:\android\tools with YOUR sdk location
from the command line type the following:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb pull /data/system/packages.xml c:\android\
Click to expand...
Click to collapse
BACK UP THIS FILE BEFORE EDITING IT
Once that's done, open that xml file in a text editor hit ctrl+f and search for maps, the first one will probably say auth.sitemaps, ignore that, keep searching untile you get to something to the effect of com.android.google.maps.apk or something like that. when you see that, you'll want to delete everything from "<packagename=" to "</package>" for the google maps app. BE VERY CAREFUL!!!! you don't want to accidentally delete something else, thus the reason for the back up.
after you've done that, go back to your command prompt and type:
c:\android\tools> adb push c:\android\ /data/system/packages.xml
c:\android\tools> adb install c:\android\maps.apk
Click to expand...
Click to collapse
it should then install perfectly fine. thats what I had to do to get it to work for me
I love you guys! will try this when I get home from work!
it does not appear to be 100% working....yet...
as posted by dwang, http://forum.xda-developers.com/showpost.php?p=4921655&postcount=275
dwang said:
If you push the old build.prop files back, after a while, the nav option disappears.
Click to expand...
Click to collapse
which I can confirm. About midnight last night it was working okay, and this morning it was gone.
followinginsanity says he will work on it today. http://forum.xda-developers.com/showpost.php?p=4921665&postcount=278
followinginsanity said:
Confirmed... will work on it tomorrow.....
Click to expand...
Click to collapse
may not want to rush to get it working only for it to not work a few hours later...but ..like most people here...that probably won't stop many
I edited the build.prop file...and now it will only work with Sapphire builds. For CM builds, build.prop file that FollowingInsanity created
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Takenover83 said:
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
Changed lol. thanks
where can i get the new maps apk? the old one fails to install
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
ahronzombi said:
where can i get the new maps apk? the old one fails to install
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4921092&postcount=196
That's the one I did, it also has all the needed files just grab the files from there and you should be able to use them for these instructions
ahronzombi said:
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Click to expand...
Click to collapse
When that happens you need to:
adb push <path to>/Maps.apk /system/app
adb shell
# install /system/app/Maps.apk
# exit
hey hey hey
could you or somone who got this to work try to make a video tuturiol on this so we can all clearly see how it works!!! please someone make an post it on youtube if possible thanks!!!!!!!!!
navigation doesn't work outside of the US at the moment right?
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
seaweeduk said:
navigation doesn't work outside of the US at the moment right?
Click to expand...
Click to collapse
Nope, not until the big G says so.
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
what rom are you using?
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
You might have to try editing your packages.xml file even though it didn't give you an install error. Also, if you push your original build.prop's back, you lose navigation after a few hours. I guess the quick solution to that would be to keep the new build.prop's, but I'm not sure what the problems that might or might not create for other apps.
I'm using CM-4.2.3.1 with the edited build.prop and the build.sapphire.prop files.
# mount -o rw,remount /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
A quick shortcut is to drop the device from this command. As you're re-mounting, the kernel knows the device name. Like this:
# mount -o rw,remount /system
Click to expand...
Click to collapse
Wow dude your the bomb, I did it a different way but it worked perfect. I just took a dount rom extracted it, deleted the maps.apk, then I took the droid dump maps app and put it into the donut rom. Then I made the changes to the build.trout.prop so that it recognized the g1 as the verizon phone, used your downloadable build.prop, of course I just deleted the original build.prop in the donut build, I resigned the donut rom, flashed it like it was brand new, and bingo everything worked perfectly. Wow good job dude. I would upload my rom but I dont want to get into any trouble.
I am using "AOSP1.6_r1.4+ADP DRD20 ROM". Maps on here is called "GoogleMaps.apk". I also do not have just a build.prop. I have a build.sapphire.prop and build.trout.prop. I modified both and replaced according to the first post. When I rebooted, GoogleMaps.apk was reinstalled, so I had to uninstall it again.
I did get the error described in post #8, but was able to get around it with the help of post #10.
But for some reason my network is completely down so I can't do nothing. Wifi and Cellular network. Hmmmm.
Edit: Replacing the files I backed up with the originals, brought my networks back.
I have looked and cannot find a solution.
I am a newb when it comes to this stuff.
Is their anyway to remove the HTC keyboard or touch input and use the standard android keyboard. I like the keyboard but it is too laggy.
I would prefer an .apk of the standard keyboard, But I am sure it won't let you install, but rather open up the HTC keyboard.
I think I can plug in and enable USB debugging, and then adb shell, rm touch input,
reboot?
Can someone please help me through this.
Partially correct.
it would be
adb remount
adb shell
cd system
cd app
rm HTC_IME.apk
rm Clicker.apk
reboot
thanks for the hep, really appreciate it, Is their anyway to reinstall the HTC ime touch input apk. that would basically reinstall the htc keyboard over the android one, if I wanted to?
Yes, there is.
Before you do the command I posted above, do this:
adb remount
adb pull /system/app/HTC_IME.apk C:\HTC_IME.apk
adb pull /system/app/Clicker.apk C:\Clicker.apk
That will backup those files to your C:\ directory.
http://www.mediafire.com/?qjymjydmw0m
flash from recovery then after boot long press an input field and change the input method. it will install 2 "android keyboard"s one is stock one is with voice
Make sure you do what andyriot posted above before removing the HTC keyboard... otherwise you'll be keyboardless until you get the new one flashed
mrinehart93 said:
Yes, there is.
Before you do the command I posted above, do this:
adb remount
adb pull /system/app/HTC_IME.apk C:\HTC_IME.apk
adb pull /system/app/Clicker.apk C:\Clicker.apk
That will backup those files to your C:\ directory.
Click to expand...
Click to collapse
andyriot http://www.mediafire.com/?qjymjydmw0m
flash from recovery then after boot long press an input field and change the input method. it will install 2 "android keyboard"s one is stock one is with voice
thanks guys
I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?
The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.
What does this do? does it make recovery stick?
watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.
TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?
Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.
Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.
any update to this?
thanks
joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?
I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!
I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets
I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762
watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks
to change the physical keyboards layout rename/copy umts_milestone2-keypad.kl to umts_jordan-keypad.kl, edit it with an editor to change key 21 with 44 and rename/copy umts_milstone2-keypad.kcm.bin to umts_jordan-keypad.kcm.bin
i do this via windows comandline tool:
1. get the umts_milestone2-keypad.kl file
Code:
adb pull /system/usr/keylayout/umts_milestone2-keypad.kl
2. edit line 43 and 65, change Z and Y
3. push the file to the sdcard as umts_jordan-keypad.kl
Code:
adb push umts_milestone2-keypad.kl /sdcard/umts_jordan-keypad.kl
4. open shell via adb and make /system/ writeable
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
5. copy the edited file to /system/..
Code:
cp /sdcard/umts_jordan-keypad.kl /system/usr/keylayout/umts_jordan-keypad.kl
6. copy umts_milstone2-keypad.kcm.bin as umts_jordan-keypad.kcm.bin in ../keychars/
Code:
cp /system/usr/keychars/umts_milestone2-keypad.kcm.bin /system/usr/keychars/umts_jordan-keypad.kcm.bin
7. set /system back to read-only and reboot
Code:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
not solved problem:
alt + z gets <
alt + y gets 6
Have you considered using files from qwertz froyo and renaming/pushing them with adb?
It may solve your alt+x problems.
I'm about to try this for my french keyboard. I'll keep you tuned.
I've been able to get the AZERTY layout.
First time i used the files from the azerty patch from argen2stone but my keyboard stopped working so i edited trough Root Explorer the files myself. Still got problems with the "." "<" "1" and "2"
atm i try to edit the umts_jordan-keypad.kcm.bin with a hex editior to change the bindings but if i restart with the new file the changed key´s don´t work^^
more or less we need the original *.kcm.bin ? Can't you take the kcm.bin for qwertz from the stock sbf?
Atomos33 said:
I've been able to get the AZERTY layout.
First time i used the files from the azerty patch from argen2stone but my keyboard stopped working so i edited trough Root Explorer the files myself. Still got problems with the "." "<" "1" and "2"
Click to expand...
Click to collapse
I've also been able to put my keyboard in AZERTY layout, but I have all the "2nd" (alt) keys that are melted
Could you send me your keypad files, please ? ([email protected] )
chibani said:
I've also been able to put my keyboard in AZERTY layout, but I have all the "2nd" (alt) keys that are melted
Could you send me your keypad files, please ? ([email protected] )
Click to expand...
Click to collapse
Which one do you need ? The one i modified or the originals? Right i'm on gingerbeta with symbol disorder...
I think i'm going to ask some people on a french forum to send me the original files from stock rom.
Sent from my MB722 using XDA App
yeah tried the original files but this ain´t help because the phone think that the keypad it is qwerty either. so the mapping is diffrent to the stock german one.
probably you get the same problems with azerty...
Atomos33 said:
Which one do you need ? The one i modified or the originals? Right i'm on gingerbeta with symbol disorder...
I think i'm going to ask some people on a french forum to send me the original files from stock rom.
Sent from my MB722 using XDA App
Click to expand...
Click to collapse
OK.
I think i'll try to fix my current file.
And if I succeed, I'll give it to frenchies
hi,
Did someone found a solution finally ?
I'm blocked with the same issues in CM7 and azerty...
You can try this http://forum.xda-developers.com/showthread.php?t=1729414