Locale & Language Support in G1 Android - G1 Q&A, Help & Troubleshooting

Hi everyone, this is my first post here and would appreciate any help or advice from you guys.
I have a G1, running on jesusfreke and rooted, with latest cupcake. When I go to settings and language, and want to add a new locale, I only see "English". Does anyone know if it is possible to add a new "locale" or language so that I can see Thai words when people send me smses in Thai or Thai words on the browser? (Currently, they appear as blocks).
I think the HTC magic in Thailand does display Thai words and has "Thai" in the option under "add locale". (Here is the site I saw it from: http://www.droidsans.com/node/231)
Anyone has any idea how to add the locale on my G1 set? Any help much appreciated!!

Hmm.. does anyone have any idea? thanks!

You need to replace the system fonts with fonts that have the Thai characters embedded in them (they aren't in there in the custom ROMs). droidsans.com has the details on this, but basically you need to overwrite a bunch of files in /system/fonts. You don't need the libsgl.so update with 1.5.
As for the locale setting, all that does is adjust the default resource files used by applications (for names, strings, views and such) if they exist (which they don't in Thai for any ROM I've seen so far)

neufnoof said:
You need to replace the system fonts with fonts that have the Thai characters embedded in them (they aren't in there in the custom ROMs). droidsans.com has the details on this, but basically you need to overwrite a bunch of files in /system/fonts. You don't need the libsgl.so update with 1.5.
Click to expand...
Click to collapse
They aren't actually in the stock ROMs either (except for the AIS phone (HTC Magic), but ... as far as I can tell, they didn't actually localize it, they just added the Thai characters to the system font. Which doesn't make much sense, but hey... I hope they at least fixed the webbrowser link outline bug)
For a fallback font that contains Thai (and Vietnamese), http://www.megaupload.com/?d=WB3EDVC8
Log in to your device (somehow)
Become root (if not already)
Somehow copy DroidSansFallback.ttf to /sdcard (only this font needs to be replaced, but if you want bold as well pull the DroidSansBold.ttf out of the droidsans.com pack and repeat below as Android won't fake-bold the fallback font)
mount -o rw,remount /dev/block/mtdblock3 /system
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot (if you don't reboot, the phone will crash very quickly as the font changes out from under it)
You can also adb shell the remount, and adb push right over the existing fonts. adb shell sync a couple times then adb shell reboot
I have done this on both my G1(s) and the Magic that I have, works fine and avoids issues with changing a significant portion of the typeface by swapping for another font. This should work on more or less any ROM assuming there's about 600KB free on /system (as that's how much bigger this different fallback font is)

THANK YOU!!!
neufnoof said:
They aren't actually in the stock ROMs either (except for the AIS phone (HTC Magic), but ... as far as I can tell, they didn't actually localize it, they just added the Thai characters to the system font. Which doesn't make much sense, but hey... I hope they at least fixed the webbrowser link outline bug)
For a fallback font that contains Thai (and Vietnamese), http://www.megaupload.com/?d=WB3EDVC8
Log in to your device (somehow)
Become root (if not already)
Somehow copy DroidSansFallback.ttf to /sdcard (only this font needs to be replaced, but if you want bold as well pull the DroidSansBold.ttf out of the droidsans.com pack and repeat below as Android won't fake-bold the fallback font)
mount -o rw,remount /dev/block/mtdblock3 /system
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot (if you don't reboot, the phone will crash very quickly as the font changes out from under it)
You can also adb shell the remount, and adb push right over the existing fonts. adb shell sync a couple times then adb shell reboot
I have done this on both my G1(s) and the Magic that I have, works fine and avoids issues with changing a significant portion of the typeface by swapping for another font. This should work on more or less any ROM assuming there's about 600KB free on /system (as that's how much bigger this different fallback font is)
Click to expand...
Click to collapse
Thank you VERY MUCH! for reuploading to MegaUpload
I've been looking on the net for a long time for those fonts.
The droidsans.com link is down, the site remove that page and also the files. The instructions are outdated too.
DO not follow instructions in droidsans.com
The instructions above work beautiful. Im adding some instructions with a backup option if you need to restore or you've made some any at some point.
I recommend you make a nandroid backup before performing this. (Nandroid backup is included in Cyanogen recovery image and Amon recovery image)
1. reboot into recovery
2. make nandroid backup
3. reboot
4. connect by usb
5. mount the SD card (the fat32 partition) on your computer, decompress the tar.bz2 archive and copy the desired fonts to the SD card
6. Eject or unmount the SD card,
7. Remove and reconnect the usb cable.
8. run these commands assuming you have ADB tool
adb shell
mount -o rw,remount /dev/block/mtdblock3 /system
cp /system/fonts/DroidSansFallback.ttf /sdcard/DroidSansFallback.ttf.bak
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot
I also re-hosted those Font files on my server as appreciation. Better than wait for megaupload.
newfonts.tar.bz2
File size = 2.1MB
MD5 (newfonts.tar.bz2) = d625090ea50e8f0312a1d1d4c1a0e717
Thanks again.

Hi, need spanish language, can you help me..
Hi, i need spanish language, can you help me please...

Related

How to replace fonts without USB?

I like to use Helvetica, so every time I flash a new cyanogen ROM, I find myself having to hook up USB and copying over the ttf files from my desktop.
Code:
adb remount
adb push ~/android/fonts/Helvetica/DroidSans.ttf system/fonts
adb push ~/android/fonts/Helvetica/DroidSans-Bold.ttf system/fonts
adb shell reboot
Can someone help me figure out how to do this directly on the phone?
I have the ttf files on my SD card, but I can't figure out how to copy them over to /system/fonts.
I tried using Better Terminal Emulator (a) but it's a pain to type it all, and (b) it doesn't allow it.
Is there a way to create a script to do this?
Can the script be made into an app/icon on my home screen?
It would be great if someone wrote up an app that could change fonts in general.
Thanks!
d0g said:
I like to use Helvetica, so every time I flash a new cyanogen ROM, I find myself having to hook up USB and copying over the ttf files from my desktop.
Code:
adb remount
adb push ~/android/fonts/Helvetica/DroidSans.ttf system/fonts
adb push ~/android/fonts/Helvetica/DroidSans-Bold.ttf system/fonts
adb shell reboot
Can someone help me figure out how to do this directly on the phone?
I have the ttf files on my SD card, but I can't figure out how to copy them over to /system/fonts.
I tried using Better Terminal Emulator (a) but it's a pain to type it all, and (b) it doesn't allow it.
Is there a way to create a script to do this?
Can the script be made into an app/icon on my home screen?
It would be great if someone wrote up an app that could change fonts in general.
Thanks!
Click to expand...
Click to collapse
Is there a way to post in the correct section?
Anyways, have them on the root of your sdcard and
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/*.ttf /system/fonts
reboot
That should change the fonts.
Gscript
d0g said:
I like to use Helvetica, so every time I flash a new cyanogen ROM, I find myself having to hook up USB and copying over the ttf files from my desktop.
Code:
adb remount
adb push ~/android/fonts/Helvetica/DroidSans.ttf system/fonts
adb push ~/android/fonts/Helvetica/DroidSans-Bold.ttf system/fonts
adb shell reboot
Can someone help me figure out how to do this directly on the phone?
I have the ttf files on my SD card, but I can't figure out how to copy them over to /system/fonts.
I tried using Better Terminal Emulator (a) but it's a pain to type it all, and (b) it doesn't allow it.
Is there a way to create a script to do this?
Can the script be made into an app/icon on my home screen?
It would be great if someone wrote up an app that could change fonts in general.
Thanks!
Click to expand...
Click to collapse
ever heard of "gscript" .. it's pretty simple to create a script to do whatever you want it to do .. ie. "cp /sdcard/*.ttf /system/fonts" .. no USB needed .. come to think of it i don't use a USB connection for any of my G1 needs
Thanks! That worked!
I found this handy app -- GScripts (on the market) -- that let me set up the script to run with one click.
PS: I'm sorry -- which section should this go in? Regular Q&A?

Changing fonts on a rooted phone

Hi,
I need help updating the fonts on my rooted Incredible. The way I understand it, all that needs to be done is to replace the font(s) in /system/fonts with something else. Easier said than done...
I opened an SU shell via "adb shell", and then tried to remount the /system in "rw" mode, I also updated the permissions for the font files so that I can override them. So good so far...
But when I try to copy or replace the files, I run into all kinds of problems:
* First of all, the rooted phone doesn't have "cp" so I can't do the usual copy operations like a regular *nix machine (did I miss something during the root process).
* Then I saw examples of using the "cat" command to replace the old files, but that resulted in "write: No space left on device" error, which I think has to do with how the memory image is loaded/packed??
* Then I saw examples of using the "dd" command, to copy the new files over the old files. This went further, since I can see the new timestamp when using "ls -l /system/fonts". However, when I reboot the phone, the old fonts show back again.
* I also saw an example in another thread titled "Hebrew support" in this forum (sorry, don't know how to cross-post URLs), but I didn't know how to follow the instructions there.
I would really appreciate it if someone can help me out.
- how can I update the system image? (do I really need a signed ZIP file?)
- is it too late for me to add "cp" to my rooted phone?
- the 10 minutes rooting video had us copy the "busybox" file to the sdcard, but it didn't say what to do with it. can I use it as a replacement for "cp"? (do I have to go back to "adb recovery"?)
You can only modify /system while in clockwork recovery after you're rooted and have run the unrevoked recovery flash tool
Yea, you have to push them to the phone in clockwork recovery.
you can put them in your tools folder where adb is located or put them on your SDcard and push them from there.
I attached the fonts I used. I used these on my Moto Droid I used to have and now they are on my dInc. This font is not as bold as the stock font and a little smaller. This font i believe is the "Droid" font. It looks pretty nice, see my screenshot and look under icons and at the clock and then compare to your phone.
Here is the commands you would do at command prompt, not from ADB shell.
For these commands to work, you have to place the fonts in your tools folder where ADB is.
Code:
adb push Clockopia.ttf /system/fonts/
adb push DroidSans.ttf /system/fonts/
adb push DroidSans-Bold.ttf /system/fonts/
adb push DroidSansFallback.ttf /system/fonts/
adb push DroidSansMono.ttf /system/fonts/
adb push DroidSerif-Bold.ttf /system/fonts/
adb push DroidSerif-BoldItalic.ttf /system/fonts/
adb push DroidSerif-Italic.ttf /system/fonts/
adb push DroidSerif-Regular.ttf /system/fonts/
you might be able to try this command
adb push *.ttf /system/fonts/
Im not sure if that would work or not, maybe someone else could confirm.
Thank a lot for the reply...
So is this the correct thread that I should follow now: "Unrevoked team: Recovery reflash tool (updated!)" to install the "clockwork recovery"? I am assuming this will allow the phone to start recovery with adbd running, so that I can connect to it from my PC while in recovery. Correct?
It took me forever to get the adbd running in recovery as part of rooting my phone, and I am not sure that I can replicate these steps again (at least not easily). I was this close to copying the font files while in "adb recovery" mode, but then I chickened out, because I didn't want to risk the rooting process by doing something that doesn't match the root instructions.
yes, as long as you have actually gained root and have the superuser/busybox properly installed. just follow that thread and you'll have new fonts in no time, and I can assure you that it will work because I changed mine too.
If using clockword recovery, dont forget to mount system.
Put them all in a folder named fonts. Put the folder in tools. Boot into recovery, mount system. Then: adb push fonts /system/fonts. Unmount system then reboot.
Sent from my ADR6300 using XDA App
TNS201 said:
Yea, you have to push them to the phone in clockwork recovery.
you can put them in your tools folder where adb is located or put them on your SDcard and push them from there.
I attached the fonts I used. I used these on my Moto Droid I used to have and now they are on my dInc. This font is not as bold as the stock font and a little smaller. This font i believe is the "Droid" font. It looks pretty nice, see my screenshot and look under icons and at the clock and then compare to your phone.
Here is the commands you would do at command prompt, not from ADB shell.
For these commands to work, you have to place the fonts in your tools folder where ADB is.
Code:
adb push Clockopia.ttf /system/fonts/
adb push DroidSans.ttf /system/fonts/
adb push DroidSans-Bold.ttf /system/fonts/
adb push DroidSansFallback.ttf /system/fonts/
adb push DroidSansMono.ttf /system/fonts/
adb push DroidSerif-Bold.ttf /system/fonts/
adb push DroidSerif-BoldItalic.ttf /system/fonts/
adb push DroidSerif-Italic.ttf /system/fonts/
adb push DroidSerif-Regular.ttf /system/fonts/
you might be able to try this command
adb push *.ttf /system/fonts/
Im not sure if that would work or not, maybe someone else could confirm.
Click to expand...
Click to collapse
Where can I get/download these font files?
EDIT im a retard and didnt see the .zip sorry
so where can i go to download other font types?
Perhaps this is an obvious questions to some... Can I use any TTF font? I have a font I created that is my own handwriting. This would be pretty cool to have available in my Phone... It is a standard TTF font.
Possible? I tried to search but didn't see anything specifically mentioned if a font has to be a specific type or if I can use anything.
Thanks!
compnird said:
Perhaps this is an obvious questions to some... Can I use any TTF font? I have a font I created that is my own handwriting. This would be pretty cool to have available in my Phone... It is a standard TTF font.
Possible? I tried to search but didn't see anything specifically mentioned if a font has to be a specific type or if I can use anything.
Thanks!
Click to expand...
Click to collapse
it should work fine, you just need to rename the file to DroidSans.ttf and DroidSans-Bold.ttf and replace the ones that are in /system/fonts
Thanks for the help seanhassars and TNS201: I am using the ClockworksMod recovery, and I was able to update the fonts (using the "update from ZIP" option).
I can see Arabic letters, but unfortunately, they don't look correct (they are disjoined, when they actually should be connected together). Now I am looking around for patched libwebcore.so to fix this issue, and thanks to nandroid backup, I can experiment with changing the libraries as much as I can.
shamidude can you please let me know which fonts you used? I am desperately needing to install arabic on my phone and could use the help. If possible could you upload the proper ones? Also which libwebcore.so did you use?
I tried to install Arabic fonts from another website but my phone froze on the splash screen and wouldn't boot. Please let me know what works for you, especially if you get the reshaper working.
edit- also if you could post general instructions of what you did to push the fonts onto the phone, how you mounted/dismounted, etc would be good
I don't think that was supposed to be an update.zip he just zipped the fonts he's using for easier access, you still have to push them manually.

[Q] Keyboard

Greetings,
How do I add my keyboard support into SGS?
Norwegian (Norway/Norsk)
For a second there I thought you were wanting beta testers for a new keyboard you were developing.
Posting in Q&A would be a start.
Do you think about something like this?
http://forum.xda-developers.com/showthread.php?p=10403672
qtJz said:
Greetings,
How do I add my keyboard support into SGS?
Norwegian (Norway/Norsk)
Click to expand...
Click to collapse
Create a complete ROM with DocRambones romkitchen, there is options for keybords that include norwegian, you could also buy swiftkey it's discounted right now, and it's a great keyboard, once bought you could redownload it in any ROM you choose to install in your phone.
qtJz said:
Greetings,
How do I add my keyboard support into SGS?
Norwegian (Norway/Norsk)
Click to expand...
Click to collapse
Try this! (Your phone needs to be rooted)
[APPS]Working keyboards for most EU countries (JPY)
It is at:
http://forum.xda-developers.com/showthread.php?t=896042
It includes normal and swype (not ginger) keyboard for SGS.
READ the instructions BEFORE doing anything!!!!
If you don't have rootexplorer, you need rooted phone, busybox, Superuser and "Terminal Emulator" (or similar cosole app).
Step 0. Change keyboard you are using to something else than Samsung-keyboard (if you have that). Otherwise you might not be able to replace the files.
Step 1. Type 'su' in the console app and allow root access to that app.
Step 2. Type 'mount'
Step 3. Find line(s) that contains /system
Step 4. Look what block it is (it should be /dev/block/stl9)
Step 5. Type 'mount -o remount,rw /dev/block/stl9 /system'
Step 6. Now your /system is mounted as read-write. Backup original files.
Step 7. Extract the zip file and then copy new files - file 'AxT9IME.apk' in 'EU GalaxyS Keyboards/sys-app' to /system/app/ and two files from 'EU GalaxyS Keyboards/sys-lib' to /system/lib/
Now it is done.
Change keyboard back to Samsung-keyboard and it should work.
I mean SHOULD, not 100% sure. It works on my "Darky's v8.1 Gingerbread Edition ★ JPY ★"
"REMEMBER.. you can do serious damage to your rom if you delete or move essential system files.
This is at OWN risk!"
If you pm me I can send you swype jpa.zip or you can create a Doc-rom with this keyboard and samsung euro.
Sent from my GT-I9000
K4P1 said:
Try this! (Your phone needs to be rooted)
[APPS]Working keyboards for most EU countries (JPY)
It is at:
http://forum.xda-developers.com/showthread.php?t=896042
It includes normal and swype (not ginger) keyboard for SGS.
READ the instructions BEFORE doing anything!!!!
If you don't have rootexplorer, you need rooted phone, busybox, Superuser and "Terminal Emulator" (or similar cosole app).
Step 0. Change keyboard you are using to something else than Samsung-keyboard (if you have that). Otherwise you might not be able to replace the files.
Step 1. Type 'su' in the console app and allow root access to that app.
Step 2. Type 'mount'
Step 3. Find line(s) that contains /system
Step 4. Look what block it is (it should be /dev/block/stl9)
Step 5. Type 'mount -o remount,rw /dev/block/stl9 /system'
Step 6. Now your /system is mounted as read-write. Backup original files.
Step 7. Extract the zip file and then copy new files - file 'AxT9IME.apk' in 'EU GalaxyS Keyboards/sys-app' to /system/app/ and two files from 'EU GalaxyS Keyboards/sys-lib' to /system/lib/
Now it is done.
Change keyboard back to Samsung-keyboard and it should work.
I mean SHOULD, not 100% sure. It works on my "Darky's v8.1 Gingerbread Edition ★ JPY ★"
"REMEMBER.. you can do serious damage to your rom if you delete or move essential system files.
This is at OWN risk!"
Click to expand...
Click to collapse
You can download the 'EU GalaxyS Keyboards.zip' -file from:
http://dl.dropbox.com/u/10258973/EU GalaxyS Keyboards.zip
It is 23.8 M file!
I have nothing to do with this file. I just downloaded it drom XDA developers -forum, but somehow I can't remember were
Oh. A typo
'EU GalaxyS Keyboards/sys-*' should be 'EU GalaxyS Keyboards/Samsung/sys-*

Nook Touch friendly Better Keyboard skin

I hope this is the right place to post this. I installed Better Keyboard 8 on my rooted Nook Touch. It works great, but the skins all leave something to be desired on E-Ink. What I'm looking for is a simple skin with white keys and black text. I know Better Android (the developer for BK8) had exactly what I'm looking for free on the market, but I guess they got kicked off the market at some point (glad I had backup .apks!) and I can't seem to find what I'm looking for. Googling around usually just brings up broken links for the Better Android one.
Can anyone help me out? Maybe there's a skin that fits my description, some way I can edit a skin to get what I want. I believe SwiftKey's skins work on BK8 as well.
Here's essentially what I'm looking for. I apparently can't post links yet due to posts so you'll have to copy/paste.
fs03.androidpit.info/ass/x89/495189-1274726992951-160x284.jpg
Any help would be greatly appreciated.
i use the GO Keyboard, that include the white theme, and that work great
chriscsh said:
i use the GO Keyboard, that include the white theme, and that work great
Click to expand...
Click to collapse
That theme does look great, indeed. I'm wondering if GO Keyboard will let one get around the keyboard "drop-off" problem that Google Voice/Talk has on the N2E (i.e., the last row of the keyboard simply drops off the screen rendering the apps useless). Anyone try them both together?
Short question, does prediction show up in GoKeyboard? Or in any even?
domi.nos said:
Short question, does prediction show up in GoKeyboard? Or in any even?
Click to expand...
Click to collapse
I don't believe any predictive keyboard routine works with the N2E.
We need to try out all the keyboards and find which works the best.
A key thing for me is do they have tab key completion for ssh, also what about alt, ctrl and f keys?
To try out a keyboard apk you need:
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push keyboard.apk /system/app/
adb shell chmod 644 /system/app/keyboard.apk
then NookColorTools to select one of the new keyboards
Anyone know how I can activate GoKeyboard on my N2E?
Follow the instruction above your post.
Or download the file you want, rename it to keyboard.apk.
Using root explorer, make a copy of keyboard.apk from /system/app. Put it somewhere safe (sd card or computer).
Get the downloaded keyboard.apk and put it in the same directory as above (first, press the r/w button on top of the screen when on /system/app).
change properties to 644 (read/write for user, all others only read) using properties of file.
Reboot (not sure about this part, but it never hurts).
PROFIT!
apeine said:
Follow the instruction above your post.
Or download the file you want, rename it to keyboard.apk.
Using root explorer, make a copy of keyboard.apk from /system/app. Put it somewhere safe (sd card or computer).
Get the downloaded keyboard.apk and put it in the same directory as above (first, press the r/w button on top of the screen when on /system/app).
change properties to 644 (read/write for user, all others only read) using properties of file.
Reboot (not sure about this part, but it never hurts).
PROFIT!
Click to expand...
Click to collapse
actually no need to rename the apk
install the gokeyboard from market
move the gokeyboard.apk from /data/app to the system/app (i use ES file explorer cause this is FREE ),
restart your device
open NookColour Tools, choose keyboard

Key Ring Rewards App - Modified for Nook Touch

I modified the Key Ring Reward Cards app for use on the nook. The e-Ink screen of the nook touch means that even old scanners will be able to scan the barcodes that are displayed.
The attached apk is the latest version (as of 2011.11.30) of the Key Ring Reward Cards app. I reverse-compiled the code via apktool, then modified the android manifest so that the camera feature is no longer required. I recompiled it, and signed it with a newly generated certificate (because the nook won't install an app if it isn't signed; it doesn't seem to care who signed it though).
To install this app on your rooted nook touch, you first need to copy over a couple files to your system partition. These two can be obtained from the latest gapps zip file. These two files are required by the application. Even though they are for embedded google maps, they are NOT installed when you install the google maps app and must therefore be installed manually.
Download the latest gapps file. Search google for "gapps" (I can't link because I'm a new user)
Extract the following two files from the gapps zip
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Connect to your nook touch via adb
Remount your system partition as read-write
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Push the two files to their respective locations
adb push com.google.android.maps.xml /system/etc/permissions/
adb push com.google.android.maps.jar /system/framework/
Reboot your nook
Install the attached apk (via adb install or copying to an sd-card and opening the apk from es file explorer)
Note: the app freezes if you try to add a new key card. Use their web interface or your phone to add a card. Viewing and editing the cards on the nook should be fine.
I hope I'm not violating any rules by attaching the apk, since this app is completely free and I am simply removing the restriction of a built-in camera.
Works great!
Thanks
yerlizard said:
Works great!
Thanks
Click to expand...
Click to collapse
Glad to help out.
Modified App No Longer Needed
It looks like they developers have changed the program in order to accomodate users lacking a camera. This means the Android Play (Market) version installs natively on a rooted nook now!
When you add a card with the nook, it simply asks for the barcode number,whereas on a camera-equipped device it would let you scan a barcode. Thank you so much, developers of this app! I was really happy to find out today that this works.

Categories

Resources