I have been working on this issue for most of the day over in the Vibrant forums.
I am posting here in hopes of getting someone who knows more about apk editing and fonts then I do to help out.
Link to the post on the XDA Vibrant forum here
Please post your response there. Once the issue is solved I will repost a walk-through on all Galaxy S forums.
Here is the start of my thread, please read the link to see the progress.
I am aware that there are other ways to edit the fonts on our phone, by replacing renaming the default font. This is NOT what I would like to accomplish.
Since the Galaxy S is the first android phone to use Flipfont, I think we should take advantage of it. It gives us a nice preview of the font in the built in menu option and is thus superior to the other methods.
I originally purchased the Bauhaus font from the market and made a backup of it through ASTRO. After pulling the file from my phone and putting it on the computer I started editing the file with Apk Manager 4.8 found here
Steps preformed
Copied original apk into place-apk-here-for-modding folder
Run script.bat and choose option 9 ***this maybe where the issue is as I may need to choose option 10 and include the dependancy if there is one for the flipfont apk.
replace bauhaus.ttf with a .ttf font of my choosing
edit all XML, yml and smali files to include the font name or font.ttf depending on the entry in the original file *** I did not change any of the other coding so again this maybe where the problem is, as I may need to change something else to have the font act properly.
Edit the last folder name in the smali folder tree from bauhaus to the name of my font
Replace font with custom font and replace the preview image with my own
Compile apk
Sign apk
Rename apk
install apk on my phone
After putting the apk on my phone and installing the file, it shows up as expected in settings>Sound and Display>Font style. The font thumbnail shows up properly as does the font preview. The preview does show up a little larger then the other fonts and may be a sign that the font is not optimized properly or that I missed something in the XML.
After applying the font and restarting, the phone is extremely slow, freezing quite often and the font does not show up, it shows the default font instead.
If anyone that knows more about XML or apk editing/creation can help it would be great.
I have included the edited font apk if you would like to download it and run it through Apk Manager 4.8. If you want to try it with the bauhaus or one of the other fonts you will need to buy it from the market and back it up. (trying not to break any rules here.)
[EDIT][More info] Ok I took a closer look at the font that came with the Bauhaus akp
In the discription of the font it list:
OpenType Layout, Digitally Signed, TrueType Outlines
I know that opentype is a new format and that alot of the fonts for OpenType that I find are made by Monotype, the same people that make the fonts available for download. I think this may have something to do with it or maybe Im just grasping. :ºp
Any font guys out there have any info on this?
CAUTION THE FOLLOWING FILE IS NOT MEANT FOR USE AND WILL CAUSE YOUR PHONE TO RUN SLOW!!!
Download Font APK
Related
I would like to create a theme for htc desire, my idea is just to change the colors of the background applications and change the color of the keyboard, I would have everything with black background and white text.
you can extract the original files and edit them android on htc desire?
you can then apply a skin on the original release of android, I would not installing any ROM.
There are themes for htc original unmodified desire?
My HTC is ROOTED.
sharkboy_torino said:
I would like to create a theme for htc desire, my idea is just to change the colors of the background applications and change the color of the keyboard, I would have everything with black background and white text.
you can extract the original files and edit them android on htc desire?
you can then apply a skin on the original release of android, I would not installing any ROM.
There are themes for htc original unmodified desire?
My HTC is ROOTED.
Click to expand...
Click to collapse
You would need to change
system/app/HTC_IME.apk
system/framework/com.htc.resources.apk
system/framework/framework-res.apk
I don't know how to change the colour of font though, but changing the images is easy, they are all in res/ in the apk
And that's if modifying the original rom is possible
Thanks..
If I can extract them from the phone, this apk files, can I change it with the framework sdk and then install the new apk as a simple application or should I create an update file for use in recovery mode?
sharkboy_torino said:
Thanks..
If I can extract them from the phone, this apk files, can I change it with the framework sdk and then install the new apk as a simple application or should I create an update file for use in recovery mode?
Click to expand...
Click to collapse
Make an update file for use in recovery or push them using adb, they won't install like normal apps
I have take the apk files from HTC, now how can i edit it? If I open apk as if they were zip archive, the files are corrupt, if I open XML files do not see them properly, but they have garbled characters! how can I do?
After opening the apk, go to res/drawable-hdpi folder where you can find all the images/icons.
perfect, I read your fantastic tutorial for images and icons.
But I would change the colors, the background and the text, the size of the text.
I know that these settings are written in XML files, but they are encrypted in the file that I take from my phone or files on any apk.
you have an idea how can I do?
i have this question too...the xml files are all with special characters not readable....i tried utf-8 and ANSI
Fantastic!
I found this tool on the net, the name is android-apktool at http://code.google.com/p/android-apktool/ .I tried it and it works, now I see the XML file! Incredible!
Let me know if you know it and if it is reliable.
I have been working on this issue for most of the day over in the Vibrant forums.
I am posting here in hopes of getting someone who knows more about apk editing and fonts then I do to help out.
Link to the post on the XDA Vibrant forum here
Please post your response there. Once the issue is solved I will repost a walk-through on all Galaxy S forums.
Here is the start of my thread, please read the link to see the progress.
I am aware that there are other ways to edit the fonts on our phone, by replacing renaming the default font. This is NOT what I would like to accomplish.
Since the Galaxy S is the first android phone to use Flipfont, I think we should take advantage of it. It gives us a nice preview of the font in the built in menu option and is thus superior to the other methods.
I originally purchased the Bauhaus font from the market and made a backup of it through ASTRO. After pulling the file from my phone and putting it on the computer I started editing the file with Apk Manager 4.8 found here
Steps preformed
Copied original apk into place-apk-here-for-modding folder
Run script.bat and choose option 9 ***this maybe where the issue is as I may need to choose option 10 and include the dependancy if there is one for the flipfont apk.
replace bauhaus.ttf with a .ttf font of my choosing
edit all XML, yml and smali files to include the font name or font.ttf depending on the entry in the original file *** I did not change any of the other coding so again this maybe where the problem is, as I may need to change something else to have the font act properly.
Edit the last folder name in the smali folder tree from bauhaus to the name of my font
Replace font with custom font and replace the preview image with my own
Compile apk
Sign apk
Rename apk
install apk on my phone
After putting the apk on my phone and installing the file, it shows up as expected in settings>Sound and Display>Font style. The font thumbnail shows up properly as does the font preview. The preview does show up a little larger then the other fonts and may be a sign that the font is not optimized properly or that I missed something in the XML.
After applying the font and restarting, the phone is extremely slow, freezing quite often and the font does not show up, it shows the default font instead.
If anyone that knows more about XML or apk editing/creation can help it would be great.
I have included the edited font apk if you would like to download it and run it through Apk Manager 4.8. If you want to try it with the bauhaus or one of the other fonts you will need to buy it from the market and back it up. (trying not to break any rules here.)
[EDIT][More info] Ok I took a closer look at the font that came with the Bauhaus akp
In the discription of the font it list:
OpenType Layout, Digitally Signed, TrueType Outlines
I know that opentype is a new format and that alot of the fonts for OpenType that I find are made by Monotype, the same people that make the fonts available for download. I think this may have something to do with it or maybe Im just grasping. :ºp
Any font guys out there have any info on this?
CAUTION THE FOLLOWING FILE IS NOT MEANT FOR USE AND WILL CAUSE YOUR PHONE TO RUN SLOW!!!
Download Font APK
You only can use .ttf (true type font) any other type will not work,if you have a font u want to use but is not in .ttf then you need to convert it to .ttf, btw i prefer the Type Fresh app to manage and change my fonts is easier than the method you described.
Also, make sure the font has a full latin library. I learned the hard way from the TypeFresh app (which is a way better solution IMO). In its instructions which I only read the second time, one font (i believe its called DroidSansFallback.ttf) needs to have a COMPLETE set, including latin, I believe for certain coding going on somewhere. I bricked my phone within two hours of rooting it. Took three to get it back. (Backup people!)
Anyways, now I use TypeFresh, it gives you options on which system font to replace, and I never replace that one.
Hope this helps.
Hi All,
This is a small guide or may just information to most devs out there.. But this is for people who wanna mess around with thier fonts..
But they end up using Font Changer or Font Installer or ROM Toolbox to change the fonts.. And still end up stuck with Roboto Bold coming here and there..
And changing would cause a bootloop in ICS (Trust me. .Nandroid backup will be ur friend once you start changing the Roboto Bold Font)
So i googled and saw this RootzWiki thread..
[How to] Make Font Packs that Work on ICS/JB
Well essentially after reading that thread I found out that in ICS.. The Fonts actually read meta data unlike in GB.. So that why changing Roboto Bold/Bold Italic/Italic Fonts give a bootloop.. We need to change the fonts at metadata level for ICS to accept it..
So in order to over come this.. We need to change the metadata of the Font using any Font Changer App..
Here are the steps from the Rootzwiki thread in a nutshell
1.) Open the .ttf file
2.) Go to Format > Settings
3.) Under the Classification tab, make sure the weight is correct
Normal(Regular) for Regular and Italic
Bold for Bold and Bold Italic
4.) Make sure the Font Design (Windows) and Mac Style are correct
Regular for Regular,
Bold for Bold,
Italic for Italic,
Bold AND Italic for Bold Italic
5.) Click OK.
6.) Go to Format > Naming.
Make sure all the fonts you want to use use the same Font Family ("Roboto" in the case of Roboto, etc).
Make sure Full Font Name and Postscript Name are correct ("Roboto Regular" for Roboto Regular, etc., "Roboto-Regular" etc. for Postscript Name)
And after that is done. We just need to create a folder called system and then we need to create another Folder named fonts and place the fonts that you have edited under these names
Roboto-Bold.ttf
Roboto-BoldItalic.ttf
Roboto-Italic.ttf
Roboto-Regular.ttf
So its like Normal font in Regular, Bold font in Bold, So on and so forth..
Put the "system" folder in the same folder as your META-INF folder (use an updater-script made for ICS).
Zip up the META-INF and system folders into a normal ZIP file.
Flash the zip using CWM..
And Viola.. You're new font is here..
For some fonts you get a Symbol '[]' like this in some places.. The guy in the rootzwiki thread also gave an answer to this (Awesome Guy ).. Its cause of the glyph for .notdef. It will show up in places where the item gets abbreviated.
So once you're making mods for your fonts.. Make sure to remove that glyph. (For better user experience)
And there you go.. You're own custom fonts.. Entirely.. :good::good:
Credits to ThugEsquire from RootzWiki
EDIT:: If you want to modify the clock that comes in the lockscreen. then you should modify the AndroidClock*.ttf.
But make sure you fonts are proper, otherwise it will cause a distortion in the lockscreen. Specially if you use AOKP and have the carrirer label.
I attached one of my Font Mods. Its only normal font without Italics. So if you like Italics, then i suggest you dont use this.
The Font is Romance Fatal Serif
If you found this post helpful.. Please hit thanks
Hello I created custom header image to use with omnistyle. But I realised I need a full apk to get it work. There is no option in pure nexus ROM to use custom header image (my own image). So how do I create an app (like this https://play.google.com/store/apps/details?id=com.dirtyunicorns.headers&hl=en )for omnistyle? I tried googling but could not find an answer. I am not a developer but some guidance or template would help.
Hello, i don't know if you still need this? I can make a template for Android Studio with a little guide if this is still relevant.
PONYMODZ said:
Hello, i don't know if you still need this? I can make a template for Android Studio with a little guide if this is still relevant.
Click to expand...
Click to collapse
Do you happen to know where to go to change the OmniStyle QS image collection names? For example, I've replace all of the "Nature" images with pictures of sharks. That was easy enough and the new images show up and work, but the image collection in the list still says "Nature." I would like to change it to say "Sharks." I've dug through the OminStyle.apk up and down, but I can't find where those names are set. I see them in the AndroidManifest.xml, but changing the android:label in the androidmanifest.xml has no effect.
sharkie405 said:
Do you happen to know where to go to change the OmniStyle QS image collection names? For example, I've replace all of the "Nature" images with pictures of sharks. That was easy enough and the new images show up and work, but the image collection in the list still says "Nature." I would like to change it to say "Sharks." I've dug through the OminStyle.apk up and down, but I can't find where those names are set. I see them in the AndroidManifest.xml, but changing the android:label in the androidmanifest.xml has no effect.
Click to expand...
Click to collapse
The names are set in the androidmanifest.xml i have no clue why it does not work for you. But it would be easier if you just add your images with an apk or add them directly to the Omnistyle.apk if you need help with that just contact me.
PONYMODZ said:
The names are set in the androidmanifest.xml i have no clue why it does not work for you. But it would be easier if you just add your images with an apk or add them directly to the Omnistyle.apk if you need help with that just contact me.
Click to expand...
Click to collapse
I've already added my images to the OmniStyle.apk, and that works. I just want the image group text to say what the actual images are rather than whatever the text is by default.
I'd rather work it out in the thread, if that's alright. This way others can find it should they need it.
I'm about to go to bed now, but tomorrow I can upload the AndroidManifest.xml, or the APK I'm working with, if you want to have a look. Let me know how to proceed.
Thank you so much for being willing to help me out with this!
Sent from my moto g(6) using XDA Labs
So here's what I have so far:
- You can see in the attached screenshot (AndroidManifext-xml_Changes.png) that I've changed the text in the "android:lable" section of each activity.
- You can see in the attached screenshot (Screenshot_MiXplorer_20190612-122940.png) taken from the OmniStyle.apk on my phone that the AndroidManifest.xml is there on my phone with my new text changes.
- However, you can see in the attached screenshot (HeaderImageCollectionTitle-NoChange.png) that the changed labels did not actually change anything.
More Information:
- This is the OmniStyle.apk from the 6-4-19 release of the Havoc ROM for the Pixel 2 XL. I've also check this ROM's Setting.apk and SystemUI.apk in case the text was set there, but I don't see any reference to those words anywhere in Settings or SystemUI. The link to that ROM is: https://forum.xda-developers.com/pixel-2-xl/development/pie-havoc-os-t3851780
- Here's a link where you can download my already modded apk as well in case you wanted to have a look at it (It's too big to upload directly): https://drive.google.com/open?id=1N-ivQSa3In1LbD8LZ4QrVrzo1HAB0giT
Let me know what else you need, if anything.
@sharkie405
So i have checked the apk and the Androidmanifest.xml is correct but when i tested the apk, for me it wasn't working at all. I use the same ROM as you on my S7(herolte) and when i replace my apk with yours there it cant be loaded at all i just see my custom Headers, maybe it's an issue with your ROM or the apk itself. Try to update your ROM and edit the new apk again, but best would be to restore your Omnistyle.apk and make custom headers with the Android Studio Template from me, if you need help with it just ask
I'd like to add a font to my device for use with apps like Tasker and Minimalistic Text. From what I have read on the forum it looks like a matter of adding the font file to /system/fonts and (perhaps) rebooting.
Of course this does not work or I would not be writing this thread. Font files (I'm using TTF) handled in this manner do not appear anywhere. I cannot access them through Tasker (I can access each of the stock fonts that are present in the folder). Minimalistic Text is probably a separate issue and I may need to try and contact the developer on that one.
So...is there something else? Is there a font "table" somewhere that needs to be updated? Is there something special about TTF fonts for the NST/G which makes TTF fonts from other sources unrecognizable to the system?
I'd have to look how those apps access their fonts.
Normally in Android you only have serif, sans-serif, monospace.
They get mapped through /system/etc/system_fonts.xml
For fallback there is /system/etc/fallback_fonts.xml
For older B&N Reader, the fonts are selected directly by path in /system/fonts from a preset list of fonts.
For newer B&N Reader, the fonts are selected from raw resource assets (in Vendor.apk) from a preset list of fonts.
Renate NST said:
I'd have to look how those apps access their fonts.
Normally in Android you only have serif, sans-serif, monospace.
They get mapped through /system/etc/system_fonts.xml
For fallback there is /system/etc/fallback_fonts.xml
For older B&N Reader, the fonts are selected directly by path in /system/fonts from a preset list of fonts.
For newer B&N Reader, the fonts are selected from raw resource assets (in Vendor.apk) from a preset list of fonts.
Click to expand...
Click to collapse
Yes, on the original NST there is no /system/etc/system_fonts.xml, just the fonts in the /system/fonts folder and, I guess, some mysterious fixed list somewhere.
What I discovered by trial and error is that one sure way to get a new font is to rename the new font as one of the existing fonts. This, of course, eliminates the original font. I learned this the hard way when a "font installer" app did it without warning. Luckily I have two NSTs so I was able to restore the font.
Tasker cannot access anything but the three basic font types unless the text is in HTML format, but even there it can only access the fonts in /system/fonts and only those in the secret list. So no just dropping the font into the folder and rebooting.
Minimalistic Text turned out to be more amenable. Its issue is a generally poor install on the device. Perhaps there are permissions that need fixing. I corrected initial problems when I first got it by copying the settings.xml file from an installation of the same version on a KitKat device. The file from installation on the NST seemed to be malformed in some way. With the fonts (which are simply dropped into any folder you like), it would not create a global.xml file where the "where are they?" information was stored. So I did the same trick again and now that is fixed. In the end, this is an acceptable result for me because the purpose of the custom font is for a widget and the only remaining app through which this ancient version of Tasker can actually make a widget is Minimalistic Text.
Someone asked in another thread about adding fonts. This thread was first in the search I guess as one of the recent about this issue. I know that problem exist with limited choice of fonts for this device that people circumvent by renaming the font of their preferred choice as already existing one on device after safely backing up existing font. Just out of curiosity did someone tried adding these recently published fonts from respected source?