i was just wondering if anyone knows a way to manually install more fonts on the vibrant.
I was wondering the same thing
Search for "FlipFont" in the market.
zinite said:
Search for "FlipFont" in the market.
Click to expand...
Click to collapse
appreciate it. will give it a shot. hopefully it works for non-root.
What if you want to use a font that flipfonts hasn't offered?
EDIT: NM got it, an app for Root users called Type Fresh can backup/ restore system fonts, and can install new fonts with proper permissions. Any TTF font file works, but picking ones that are designed for on screen viewing is best.
sent from my Samsung Vibrant
The_Chrome_Coyote said:
What if you want to use a font that flipfonts hasn't offered?
EDIT: NM got it, an app for Root users called Type Fresh can backup/ restore system fonts, and can install new fonts with proper permissions. Any TTF font file works, but picking ones that are designed for on screen viewing is best.
sent from my Samsung Vibrant
Click to expand...
Click to collapse
thanks! zinite and the chrome coyote
EDIT: i tried the app. i got to the point where i restart the phone but the new fonts do not apply. have you or anyone got this to work right on the vibrant yet? (the chrome coyote)
I tried it as well and also had no success. Font would not apply.
At least you Vibrant users got some "starter fonts" out of the box.
Captivates don't come with any besides the default.
I highly recommend the Helvetica Neue from the Market, btw, especially if you were fond of the Zune interface.
DJ! said:
thanks! zinite and the chrome coyote
EDIT: i tried the app. i got to the point where i restart the phone but the new fonts do not apply. have you or anyone got this to work right on the vibrant yet? (the chrome coyote)
Click to expand...
Click to collapse
creator2456 said:
I tried it as well and also had no success. Font would not apply.
Click to expand...
Click to collapse
Yes. I ran into this problem as well. You need to go to Settings and return your fonts to "Default" and reboot before you will see the changes.
The app works by replacing the default fonts, if the phone is already using a flipfont font then it wont work
The_Chrome_Coyote said:
Yes. I ran into this problem as well. You need to go to Settings and return your fonts to "Default" and reboot before you will see the changes.
The app works by replacing the default fonts, if the phone is already using a flipfont font then it wont work
Click to expand...
Click to collapse
I'll give that a try as it seems like a very reasonable reason why it wasn't working. Thanks for that.
Try my guide: http://www.xxthe3dmanxx.com/AndroidFonts/androidfont.html
It was written for the Moto Cliq but might work on the vibrant.
the3dman13 said:
Try my guide: http://www.xxthe3dmanxx.com/AndroidFonts/androidfont.html
It was written for the Moto Cliq but might work on the vibrant.
Click to expand...
Click to collapse
Just tried it. Did not work. Not sure if I did anything wrong, but I followed directions properly. Phone would not boot past initial Samsung Vibrant screen. Luckily I was able to ADB the .backup out and replace the original.
I just recently put this in the sticky in the general section. I listed the directory where to put the font, reboot, go to the settings and select the font, phone should reboot with the new font added.
I would LOVE IF you could test the directory for me. I bought helvatica through the system, do I think it's correct.
creator2456 said:
Just tried it. Did not work. Not sure if I did anything wrong, but I followed directions properly. Phone would not boot past initial Samsung Vibrant screen. Luckily I was able to ADB the .backup out and replace the original.
Click to expand...
Click to collapse
You need to adjust the permissions of the renamed font files to match the stock fonts or else you'll boot loop
sent from my Samsung Vibrant
The_Chrome_Coyote said:
You need to adjust the permissions of the renamed font files to match the stock fonts or else you'll boot loop
sent from my Samsung Vibrant
Click to expand...
Click to collapse
Ok...I followed the directions and did as they said. So, how does one go about doing this?
I use Root Explorer, as its one of the easiest ways to move system files around your phone.
To save you time looking in /system/fonts the permissions are:
User: Read-Yes, Write-Yes, Execute-No
Group: Read-Yes, Write-Yes, Execute-Yes
Others: Read-Yes, Write-No, Execute-Yes
Using Root explorer, you can navigate to your renamed DroidSans.ttf and DroidSans-Bold.ttf files, long press on them and select "permissions", then make sure the permissions match the stock font's listed above.
I cant express how effective the Type Fresh App was in doing this for me, and saves me a whole ton of hassle renaming everything. Plus its free.
The_Chrome_Coyote said:
I use Root Explorer, as its one of the easiest ways to move system files around your phone.
To save you time looking in /system/fonts the permissions are:
User: Read-Yes, Write-Yes, Execute-No
Group: Read-Yes, Write-Yes, Execute-Yes
Others: Read-Yes, Write-No, Execute-Yes
Using Root explorer, you can navigate to your renamed DroidSans.ttf and DroidSans-Bold.ttf files, long press on them and select "permissions", then make sure the permissions match the stock font's listed above.
I cant express how effective the Type Fresh App was in doing this for me, and saves me a whole ton of hassle renaming everything. Plus its free.
Click to expand...
Click to collapse
Thanks for that. Guess I'll give it a go again later today. I'll try Type Fresh again first, then move to doing it manually.
International Fonts
For more fonts and also international fonts, I did a tutorial on a Moto Droid couple months back, it should be exactly the same for "ROOTED" Samsung Vibrant:
http://nexusonehacks.net/android-hacks/droid-hack-how-to-install-thai-font-on-droid/
What I would like to know is how to write the AKP for flipfonts.
I wanted to pull one of the APKs from the Apps directory, but it seems to to work. I also tried making a backup of the APK with titanium backup, but the zip is empty. It seems the files are protected in some way.
I just wanted to take a look at the structure of the apk so I can use it as a template to create custom font APKs to side load.
If anyone can manage to make a backup of one of the flipfont APKs please explain how you did so.
I installed thai fonts by update.zip no root required.
Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
I have attached fascinate's live wallpapers.
The fascinate live wallpapers aren't found on any other variant(s) of samsung galaxy s including the vibrant.
push each individual APK to /system/app and also push lib to system/lib
you can push using root explorer or adb or any other file manager type of program
(root explorer is the best imo)
Again, not responsible if anything happens to your phone etc etc
ENJOY!!
No dice, didn't show up when I installed them.
wazmoo said:
I have attached fascinate's live wallpapers.
The fascinate live wallpapers aren't found on any other variant(s) of samsung galaxy s including the vibrant.
Download the zip and flash like you would any other files (rom manager etc)
Again, not responsible if anything happens to your phone etc etc
ENJOY!!
Click to expand...
Click to collapse
You update script is broken.
a proper working recovery update version...
http://www.androidpolice.com/2010/0...ive-wallpapers-leaked-available-for-download/
Why does this need to be flashed? Do they overwrite the stock ones or something? Oh yeah, my phone came with the luminence one.
Thanks for the link, the Fascinate looks just like our phone! Ha, anyway I'm going to just adb push the files, seems easier than a recovery flash
raduque said:
Why does this need to be flashed? Do they overwrite the stock ones or something? Oh yeah, my phone came with the luminence one.
Click to expand...
Click to collapse
No, it doesn't overwrite anything. You can open up the zip file and install the individual apk files, but you have to push the liblwfa-0.A.2-mng-p1.so file to your /system/lib/ directory before any of them will work.
wait.
where do i move the .zip to?
What I did was open up the zip file and went into the app folder and copied all the apk files over to my phone and installed them one by one. Work for me that way. BTW love the wallpapers!
any screen shots?
srqt said:
any screen shots?
Click to expand...
Click to collapse
I also would like to see some.
Ok so I tried flashing this, and the wallpapers didn't show up. So I tried copying the .so file to system/lib folder and installed each .apk individually, so now they show up, but force close when I try to use them.
Anyone have any idea how to get this working, cos it seems to me that out should be good one way or another now.
Thanks
___
Hi. My name is Jess, and I love my Vibrant. That is all.
Here are some screens I made. I think they're kinda "girly", but to each their own.
Oliver Face said:
Here are some screens I made. I think they're kinda "girly", but to each their own.
Click to expand...
Click to collapse
I have to agree with that statement sir.
theres plenty more Facinate live wallpapers that put the vibrant to shame.... can someone port from the facinate dump?
JessJames said:
Ok so I tried flashing this, and the wallpapers didn't show up. So I tried copying the .so file to system/lib folder and installed each .apk individually, so now they show up, but force close when I try to use them.
Anyone have any idea how to get this working, cos it seems to me that out should be good one way or another now.
Thanks
___
Hi. My name is Jess, and I love my Vibrant. That is all.
Click to expand...
Click to collapse
Jess, your problem is that the APKs need to be pushed into /system/app - you can't install them, they'll show up, but won't work. Try uninstalling them and push each file to /system/app.
just as rdauque says, push each individual apk to /system/app. DON'T INSTALL THEM OR FLASH.
also, some devices might need the lib to be push to system/lib.
you can use root explorer or adb to push these files.
works like a charm
*Purple* Spark lwp mod
Oliver Face said:
Here are some screens I made. I think they're kinda "girly", but to each their own.
Click to expand...
Click to collapse
Nothing wrong with girly wallpapers, some of us (admittedly nerdy) girls actually use android =)
Anyway, I really love the spark wallpaper, but honestly, I've always preferred purple over pink, so I colored the background for my liking.
Anyway, flash/push the original zip contents to your phone, or at least the .so file to /system/lib, then copy/push this to /system/app for my purple Spark mod.
Cheers,
=)
~ Jocelyn
Just move the apk files using root explorer to system/app and it will appear in your live wallpaper files.
Sent from my SGH-T959 using Tapatalk
There is a font on another rom that I like, how would I get that installed onto my Eris? I have the file from the other rom.
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
bftb0 said:
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
Click to expand...
Click to collapse
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
johnny quest said:
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
Click to expand...
Click to collapse
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
bftb0 said:
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
Click to expand...
Click to collapse
Ok, thanks I will give it a try.
johnny quest said:
Ok, thanks I will give it a try.
Click to expand...
Click to collapse
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
johnny quest said:
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
Click to expand...
Click to collapse
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
bftb0 said:
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
Click to expand...
Click to collapse
Thank you so much, I've been living on backups and restores. believe me I've learned my lesson. I will give this a try.
Your method worked great with the Root Manager. I bought it on the market. Ok, my biggest problem now is that my font is microscopic small. I don't know why. But I can't see the letters of which folder I'm in to take that font out.
I need a favor: can you post up screenshots or the number of folders to scroll down to get to the system/fonts/droidsans.tff
I can't see it, really its that small its the universal acc font.
Never mind I got it. Took a lot of squinting but I got it. Thanks.
Hi everyone,
can anybody tell me how I can change the font of the stock SE lockscreen? I don't want to use an app for this (lockbot, etc). Just want to change the font or the images the clock uses. Help me please!
G.
The font is in the framework-res in the assets folder.
And how can I edit that? It is in the framework, extract is ok, but how can create an .apk after change font? Thanks for help anyway.
garyarts said:
And how can I edit that?
Click to expand...
Click to collapse
By pulling the contents, modding, then pushing them back. Read the theme reference thread for tips.
Great! Thanks again!!!
And if i'm ready (change font, rename as an apk), should I paste over the original apk by RE for example? Is that all?
garyarts said:
And if i'm ready (change font, rename as an apk), should I paste over the original apk by RE for example? Is that all?
Click to expand...
Click to collapse
No need to be renaming anything. Just open the apk as you would any other zip and pull the files, after modding them just drag and drop them back into the framework.apk. Some say you can use RootExplorer to overwrite the original but I've done it twice in the past and both times the phone stuck at boot, so recommend using adb to push back to the phone and install.
That's why I asked, cuz last two times the same happened to me, device frozen in boot. May I use QtADB? It looks working easier for me.
garyarts said:
That's why I asked, cuz last two times the same happened to me, device frozen in boot. May I use QtADB? It looks working easier for me.
Click to expand...
Click to collapse
You can use whatever, so long as you can push and install files, like MrRusch's Mod Tool
Do you use it anyway? (x10ModTool)
garyarts said:
Do you use it anyway? (x10ModTool)
Click to expand...
Click to collapse
No, I prefer using adb directly.
qtADB should be ADB with a GUI, an user friendly version of it. Thanks.
done, but nothing changed. Is it sure those fonts to be changed? Is it possible to create a kind of a zip able to flash by x-rec?
I saw a post earlier on G+ about the G2 and Roboto. Basically you can only use normal and bold; italic, bold italic, Roboto Light, Roboto Thin, and Roboto Condensed don't work. The weight also appears to be off.
I did some looking around and all the fonts are present on the system. I made a quick test app to compare the fonts on the G2 and Galaxy Nexus and set to figure out how to fix it.
It's pretty simple, just copy the system_fonts.xml file in the zip to \system\etc. You'll probably want to backup and/or rename the existing file first and give it the same file permissions. You'll need root and a file explorer that can mount system. Reboot and you should be able to see the changes.
I copied the file over to internal storage and used Total Commander to copy the xml file after renaming the original file.
The weight is still wrong but at least if the developer wanted to use Roboto and italics, you'll now be able to see italics.
If rooted, u can use jrummys font app, and install any font the app has, it replaces the roboto font in stock font settings....
Sent from my LG-D800 using XDA Premium HD app
@noll5326, thanks for sharing. I'm a fan of the 4.2 bold font hours/light font minutes clock and your tweak fixed this issue on my G2.
sent from my GN2 / GS4
If you want to fix the weight issues, you can download Roboto directly from Google. Just click "Download Roboto" and extract the zip, then copy to your phone. In adb you can do this:
Assuming you put the roboto files at /sdcard/roboto
Code:
su
mount -o remount,rw /system
cp /sdcard/roboto/*.ttf /system/fonts
This will overwrite the ones from the stock rom, so if you're concerned about that, you can make a backup first:
Code:
mkdir /sdcard/roboto-stock
cp /system/fonts/Roboto* /sdcard/roboto-stock
After that and using your modded system_fonts.xml, I have nice proper typography in the Play Store and other Holo apps.
Thanks!
Thanks for posting this, this was (oddly?) one of my bigger concerns in researching this phone. Will give it a try when I get it.
noll5326 said:
I saw a post earlier on G+ about the G2 and Roboto. Basically you can only use normal and bold; italic, bold italic, Roboto Light, Roboto Thin, and Roboto Condensed don't work. The weight also appears to be off.
I did some looking around and all the fonts are present on the system. I made a quick test app to compare the fonts on the G2 and Galaxy Nexus and set to figure out how to fix it.
It's pretty simple, just copy the system_fonts.xml file in the zip to \system\etc. You'll probably want to backup and/or rename the existing file first and give it the same file permissions. You'll need root and a file explorer that can mount system. Reboot and you should be able to see the changes.
I copied the file over to internal storage and used Total Commander to copy the xml file after renaming the original file.
The weight is still wrong but at least if the developer wanted to use Roboto and italics, you'll now be able to see italics.
Click to expand...
Click to collapse
sefnap said:
If you want to fix the weight issues, you can download Roboto directly from Google. Just click "Download Roboto" and extract the zip, then copy to your phone. In adb you can do this:
Assuming you put the roboto files at /sdcard/roboto
Code:
su
mount -o remount,rw /system
cp /sdcard/roboto/*.ttf /system/fonts
This will overwrite the ones from the stock rom, so if you're concerned about that, you can make a backup first:
Code:
mkdir /sdcard/roboto-stock
cp /system/fonts/Roboto* /sdcard/roboto-stock
After that and using your modded system_fonts.xml, I have nice proper typography in the Play Store and other Holo apps.
Thanks!
Click to expand...
Click to collapse
Thanks for this guys, much appreciated. I combined both of these procedures and now have all stock android roboto system fonts that render perfectly everywhere, most notably in the play store. FYI: I ended up just using root explorer to move both the xml file as well as all of the stock font files to the proper directories, changed permissions and rebooted. Good as gold :good:
Followed the instructions and now everything looks as it's supposed to!
DashClock now looks great.
Much appreciated indeed !! Thanks vm.
can someone make a zip
thanks in advance
Um... is pasting a couple of files really that big of a problem?
I reckon it can be made, yes... I might just give it a go.
EDIT: okay, here it is.
NOTE: I have not tested this and I don't know whether it works properly! I am not responsible if you mess up your system or your phone. Do a nandroid backup first!
Download from attachment or this link.
Thanks, this works great?
Sent from my VS980 4G using Tapatalk
robogo1982 said:
Um... is pasting a couple of files really that big of a problem?
I reckon it can be made, yes... I might just give it a go.
EDIT: okay, here it is.
NOTE: I have not tested this and I don't know whether it works properly! I am not responsible if you mess up your system or your phone. Do a nandroid backup first!
Download from attachment or this link.
Click to expand...
Click to collapse
didn't work for me really want this to work
Do it manually, then.
I've tried it manually and it just screws up certain screens. On the password entry when making a purchase in Play Store, you only see a corner of a huge letter where it tells you to enter your password and you can't see what you're typing at all. The Tasker app is really affected, with the preferences window being a complete disaster; the fonts are massive and spread out like crazy even though my phone is set to the smallest font size. There are several other places here and there where it really messes up too.
When it works, it looks great. But for the odd screen that it screws up, it's just not worth it. I'm glad I backed up the stock files first.
Yes, I put the xml file in /system/etc/ and downloaded the fonts from Google and put them in /system/fonts/. I changed all the file permissions. I rebooted and could see the font changes, but in some places the font was just way too large and the spacing between lines was huge. Perhaps the modified xml file still needs more tweaking.
Sevael said:
I've tried it manually and it just screws up certain screens. On the password entry when making a purchase in Play Store, you only see a corner of a huge letter where it tells you to enter your password and you can't see what you're typing at all...
Click to expand...
Click to collapse
can confirm all that was said above. there are small graphical glitches here and there too, like in gmail upon selection half of the bar up top gets colored blue, etc.
edit: just restored the backup and noticed gmail still does it, perhaps it's not font related and i just haven't noticed that before but it's definitely shouldn't be there.
http://i.imgur.com/mE7EnLW.png
apparently other phones (like HTC One) suffer from this bug too. does anybody know what causes this?
Try switching to another font and then back to Roboto. I had to do that to make it fully operational. But yeah, in a few places there are minor glitches and inconsistencies.
Anyone using this mod experiencing soft reboots?
No reboots... Worked flawlessly for me
Sent from my LG-VS980 using XDA Premium HD app
after playing around with different fonts i think i found a combination that works perfectly on our phones:
- download "stock Roboto fonts from the 4.3 base ROM" from here. strangely enough, i think those are stock HTC One fonts.
(original thread it was pulled from where you can find tons of fonts, mind you most of them wouldn't work correctly:
http://forum.xda-developers.com/showthread.php?p=45437057
the easiest way to check if the font is "working" properly is going to the Call logs screen and check the date stamp as it appears broken with some. thanks alex72 for the thread tip!)
- use "system_fonts.xml" from this thread
and done. light, condensed, bold, italic, everything seems to be working and without the issues in the usual places.
Fixing font without rooting
The above method worked perfectly. I did not want to actually root my phone and trip any root checkers, so I accomplished everything via a temporary root adb shell (IOroot ftw!).
The following was done on a stock AT&T D800 with OTA (D80010o).
Make sure to switch to another font in Display settings before attempting this.
Get root adb access. IOroot should be able to help you out with that. Make sure to end the batch script at the point it warns you, so as not to push SU and trip anything.
Make backups.
Code:
adb pull /system/etc/system_fonts.xml
adb pull /system/fonts
Move these someplace safe, just in case.
Unzip RobotoFont_G2.zip to directory with adb (repackaged using xml from first post, and Roboto font from HTC One 4.3 base ROM - mannequin's post)
Push new files
Code:
adb shell mount -o remount,rw /system
adb push system_fonts.xml /system/etc/system_fonts.xml
adb push ./fonts /system/fonts
Fix permissions and reboot
Code:
adb shell
cd /system/etc
chmod 644 system_fonts.xml
cd ..
cd fonts
chmod 644 *
exit
adb reboot