Related
I didn't see a thread on how to do this anywhere in the MT4G forum, so I thought I would share.
If you want swype, but are not on their beta test program, do not want to muck about with their "installer" app, or deal with the reminders of beta status and app expiration; you can pull swype from a stock ROM and use it on your device.
As per the rules, you should not do this on a phone that does not have swype installed stock.
Also, this involves messing around in the "system" partition. While the risk is very low, you do this at your own risk.
First you will need to extract the needed files from a stock ROM. If you are still running the stock software, you can use a file explorer app to make a copy onto your SD card. Just copy and paste. You can also pull the files from the stock image or from the Iced glacier ROM. Pulling from Iced Glacier is the easiest method. Just unzip the ROM file and find the needed files.
There are two files, both in the system partition. The first is "Swype.apk" and is in /system/app folder. The second is "libSwypeCore.so" and is in /system/lib/ folder.
Edit: 7/25/11
It seems you must also conciser the source ROM and destination ROM when obtaining the files. Swype does a device/licence check when running, and if it fails the check then Swype will not work. The build.prop lists "t-mobile/htc/ect" as product.brand and Swype seems to check this before running. So use a version of Swype from a ROM with the same build.prop or edit the build.prop manually.
Now to install Swype:
There are two ways to do this, ADB or root explorer. (or other file manager with RW)
Any extra info to help explain what is going on for any new guys will be in green text.
For ADB:
First put the files you extracted into the tools folder of the android SDK, then open an ADB shell to your phone. When that is done, use the following commands. (each line is a separate command)
Remember Linux commands are case sensitive.
First is to mount /system as RW. (this allows you to save files to /system)
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Then you need to push (save a copy) the files to the correct locations.
Code:
adb push Swype.apk /system/app/Swype.apk
adb push libSwypeCore.so /system/lib/libSwypeCore.so
It may give the files the wrong permissions. (how much access to the system they have) Just to be safe we need to give the files the right permissions.
Code:
chmod 644 /system/app/Swype.apk
chmod 644 /system/lib/libSwypeCore.so
sync
reboot
Your phone will reboot and then you are done.
For Root Explorer:
Extract a copy of the needed files and put them on the SD card.
Then open root explorer and open the "sdcard" folder.
Next find "Swype.apk" and long press it and select "copy" (or if you have already completed this step once, copy "libSwypeCore.so")
Use the back button to go back to the root of the folder tree (up top where it shows your current location, it will show "/" this is where you started from when opening the app)
Locate and open the "system" folder.
You then need to tap the button up top marked "Mount R/W" (this will allow you to make changes and copy the files to the right locations) (this step should not be needed if you have already done so before)
Next open the "app" folder. (or if you are moving "libSwypeCore.so" open the "lib" folder)
Hit the "paste" button to copy the file.
Next long press the file you just copied "Swype.apk" and select "permissions" (or "libSwypeCore.so" as appropriate)
You will see a bunch of check boxes. The will be labeled "read" "write" "execute" across the top and "user" "group" "others" down the left side.
For "user" select the "read" and "write" boxes
For "group" and "others" select the "read" box only. Then select "OK"
When done with the first file, repeat the above steps again with the second file. Observe any changes to the steps that are in orange text.
Next open up a "terminal emulator" app and then run the following commands.
Code:
su
sync
reboot
Your phone will reboot and then you are done.
Hope this helps someone.
When I pushed the files to CM7 I completely forgot about checking permissions when it didn't work.
I do however prefer the newest Swype from the beta program since it has speech recognition. Your information should help me porting my Blackout Swype themes over to the MT4G with creating a proper flashable zip that will work with any ROM, and for that I thank you.
creator2456 said:
When I pushed the files to CM7 I completely forgot about checking permissions when it didn't work.
I do however prefer the newest Swype from the beta program since it has speech recognition. Your information should help me porting my Blackout Swype themes over to the MT4G with creating a proper flashable zip that will work with any ROM, and for that I thank you.
Click to expand...
Click to collapse
No problem, I was thinking of creating a flashable zip for my cousin, he doesn't like to mess around with this stuff... but he lives on the computer, go figure. I just need the signing app, actually its not needed with the new recoveries that allow unsigned zips to be flashed, but it would be nice.
I cant get the swype from iced glacier onto cm7. I follow all the steps perfectly and can select the swype keyboard but when I try to type nothing happens except a flashing blue border around the keyboard. Its pretty annoying.
Jacezo said:
I cant get the swype from iced glacier onto cm7. I follow all the steps perfectly and can select the swype keyboard but when I try to type nothing happens except a flashing blue border around the keyboard. Its pretty annoying.
Click to expand...
Click to collapse
Thats odd, I used this to get it on to CM7 and it works fine. Where did you source the files from? Permissions are rw-r-r?
Thanks so much for this! I don't use the voice feature and I always hit it on accident, so I've been missing the stock version. I also didn't care for the blue all that much.
I am new to this. Could I use this technic for the others stock apps (calendar, clock/weather widgets...)? Thanks!
A23E said:
I am new to this. Could I use this technic for the others stock apps (calendar, clock/weather widgets...)? Thanks!
Click to expand...
Click to collapse
No, the apps you are speaking of are HTC apps. They are integrated into the HTC Sense framework.
Moving default apps between ROMs that have custom UIs, like sense, can be problematic. Many default apps have been setup to work with the custom UI and framework only.
Marine6680 said:
Thats odd, I used this to get it on to CM7 and it works fine. Where did you source the files from? Permissions are rw-r-r?
Click to expand...
Click to collapse
I took the files from an iced glacier rom and fixed the permissions. I'm on cm7 rc1 with the dumguq smartass kernel.
Sent from my HTC Glacier using XDA App
Jacezo said:
I took the files from an iced glacier rom and fixed the permissions. I'm on cm7 rc1 with the dumguq smartass kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
All I can think to do is try again. It may be the kernel as well.
great help and easy to follow, thanks
Glad it helped.
hav'nt tried your way, but what i did was got those 2 files form new mytouch 2.3.4 (swype 3.7) and copied it to panache stock custom then cooked and flashed, but now it says wrong licence.....
atifsh said:
hav'nt tried your way, but what i did was got those 2 files form new mytouch 2.3.4 (swype 3.7) and copied it to panache stock custom then cooked and flashed, but now it says wrong licence.....
Click to expand...
Click to collapse
Probably has a device check, and the ROM you are using is giving the wrong device.
I believe the panache is the Canadian version, so it may be that the licence is regional as well.
License issues for me.on virtuous unity 1.29 and fauxkernel
Sent from my HTC Glacier using XDA Premium App
valve timing said:
License issues for me.on virtuous unity 1.29 and fauxkernel
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Same, I wonder if it's something to do with our build.prop?
Sent from my HTC Glacier using XDA App
Sadness i want swype guess ill go.back to beta
Sent from my HTC Glacier using XDA Premium App
valve timing said:
Sadness i want swype guess ill go.back to beta
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I figured it out for us (those of us on Virtuous Unity)!!! Haha, I'm so stoked. K, so I changed my build.prop of ro.product.brand to =tmobile, I think it's originally htc_wwe or something (This was after extracting my system backup for stock froyo and comparing the differences). Then uninstalled swype, rebooted, and then followed the terminal steps listed in the OP. Good luck.
Sent from my HTC Glacier using XDA App
eliasadrian said:
I figured it out for us (those of us on Virtuous Unity)!!! Haha, I'm so stoked. K, so I changed my build.prop of ro.product.brand to =tmobile, I think it's originally htc_wwe or something (This was after extracting my system backup for stock froyo and comparing the differences). Then uninstalled swype, rebooted, and then followed the terminal steps listed in the OP. Good luck.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I can confirm that this works
Ok I've done a little research on this but can't find what I'm looking for exactly.
I really don't like the Blur Contacts app. I have figured out how to filter things correctly so I only get my usual Google contacts but I'd still like to get one feature back that I had on CM - direct dial and direct text message shortcuts. They were supported through the AOSP Contacts app from what I can figure out. The Blur Contacts app has something similar but it doesn't work consistently. Does anyone know if it's possible to install the Contacts.apk and ContactsProvider.apk extracted from CM 6.1.1 (what I had on my EVO) and bring them over to my rooted Atrix?
I'd like a different contacts manager as well. This one combines services which is not what I want/need. Any suggestions that are similar to CM contacts on N1 would be appreciated!
+1 more here for a different contacts app.
+1
Bump
I'd also love the AOSP dialer
phobos512 said:
install the Contacts.apk and ContactsProvider.apk extracted from CM 6.1.1
Click to expand...
Click to collapse
I tired this few days ago, nothing worked. =/
Click install throws an error and says it can't be installed. Pushing the apk to /system just has no result.
Moto's contacts are terrible.
How to Install Android AOSP Apk, in any system.
Find the AOSP apps from a CM6 build by unzipping and pulling the .apk file like browser.apk. Install "File Expert" (Free and amazing file browser with full root access and alteration capabilities application)
Copy the .apk you wish to have on to your phones SD Card
Run File Expert,
hit menu/more/File Explorer settings. Then check "Root Explorer" on the bottom.
hit menu/more/mount/Mount As Read Write
Browse to /System/Apps Find the App you wish to replace with the AOSP version.
Hold Down on the App and when the options come up choose file operations and rename to something like application name.apk.bak
Browse to your SD Card find your app. hold down to choose file operation then choose copy.
Go back to /System/Apps then hit Menu button and choose paste.
Locate the app you just pasted and hold down on it and in file operations choose "permissions" Check Everything and exit out of File Expert
Note: You may need to redo the shortcuts for the app on your desktop and or launcher.
Note: Must have a rooted phone.
Note: 2.3.3 apps may or may not work on 2.2 Android Roms and vice versa.
Note: if this causes errors or failures delete the new apk and rename the old apk to its original name.
Good luck!!
can someone upload the contacts apks?
Sent from my MB860
Download the latest Cyanogen mod for your phone or any. Unzip on your pc and go to the folder labeled system/apps. Get the apps you want from there and pass them to your phone via USB to your phone then follow my previous instructions.
I have already tried to install a different dialer/contacts app. I had no luck, I think that the stock dialer/contacts are to deeply tied into motoblur and the phone system. It won't break your system but you just will not have a dialer or contacts.
Did you try it to my exact instructions. Making sure to you the cyanogen mod that corresponds to your version of android? If it didnt show up on your list you may have tried the 2.3.3 instead of s2.2 dialer.
Oh, I would love to hear the solution to this. I have been trying to figure this out for a couple days now. I pulled Contacts.apk from a Liberty backup I have and have been trying to replace BlurContacts.apk with it to no avail. I believe someone above may have touched on it. Possibly to change when other things look for BlurContacts, and instead refer to Contacts.apk?
I have tried several different contact apps. None work I think that the blur apps are to deeply tied into the system to allow a change.
Bump
any progress ??
sent from my gingerblur 3.1 atrix. with 1% mod & clock delete
I've actually been using GoContacts. It seems to work like how I want my contacts to work(I.E like ASOP) plus allows for a little bit more tweakability.
I've seen it asked quite a few times now, so I thought I would share how I've been creating my own themes for the Nook. This is a quick and dirty guide as I've almost got it down to a science for quick, keyboard shortcut, theming.
Things you'll need
Photoshop or The Gimp for editing files
Android SDK so you can push and pull files to/from the Nook.
draw9patch app in the Android SDK /tools folder for creating 9.png files
APK Manager (http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1)
Notepad++ or some other text editor for editing XML files. After using Notepad++ on this, I'd highly recommend it though
An attention span
Some restraint
This is a rather good guide that helped me get started. My only complaint is that it is almost to complicated and includes more information than what is needed for a basic theme.
http://forum.xda-developers.com/showthread.php?t=916814
Getting Started:
Download the Android SDK and get it installed.
Download APK Manager
ADB pull /system/framework/framework-res.apk
Make a copy of the framework-res.apk files as a back-up in case you need to revert
Copy the framework-res.apk file to the /place-apk-here-for-modding folder under the APK Manager folder
Launch the APK Manager Script.bat file
Type in 22 to select the default project
Type in the number next to framework-res.apk in the list to select it as your project
Select 1 to extract the files
Select 9 to decompile (this is what makes the XML files readable)
Go to the /projects/framework-res/res folder under the APK Manager folder to view all the files from the theme
Images are located in the /drawable-mdpi folder. XML files are located throughout, but the files specific to layout are under the /layout folder. To change global settings, such as color codes and strings, edit the XML files under the /values folder.
Creating custom PNG files: If you are using Photoshop, use the Save For Web feature when saving. Save the image as PNG-24. Select None under the Matte option. Select None under Metadata.
A word on 9.png files: 9.png files are files that can be stretched by the OS. There is a 1 pixel border all the way around the image. In that 1 pixel border, you'll notice solid black lines here and there. The black pixels indicate which portions of the image are to be stretched. You can add this border and the black pixels in Gimp or Photoshop, or you can open the file the draw9patch app under the Android SDK /tools folder. The draw9patch app will actually display how the image will look when stretched as you add the black pixels around the border, so it can come in handy and it's what I prefer to use. You can open and edit .9.png files in draw9patch and edit the border even after you save the file.
Once you have all your files edited, recompile the APK package with APK Manager
Option 11
y
y
It will tell you to delete the files under the /keep folder that you have edited. Delete any images and XML files, from the /keep folder, you edited under the /projects folder. If you edited XML files, delete the /keep/res/resources.arsc file as well
Press any key to continue and let the script finish
In a separate command line window, mount your Nook's /system folder (adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system)
back in APK Manager, select 8
/system/framework/framework-res.apk
Reboot your Nook
Boot Loop: If you messed something up and are stuck in a boot loop, most of the time you can still mount your Nook, push the original framework-res.apk to it and reboot. Or, you can use an unedited version of the CWM flashable zip file from the link below.
NOTE: it is not smart to push your framework-res.apk file to the Nook. I've learned the hard way that you can only do this about 10 times before you run out of memory and can no longer boot your Nook until you reflash Froyo again.
I'd recommend only a few flashes on a bare bones copy of Froyo until you feel comfortable with working on the framework theme. After that, I'm attaching a base, flashable zip for you to use in CWM so you can flash the theme instead of pushing. This will prevent you from getting stuck in a boot loop (unless you do something wrong yourself).
To add your framework-res.apk file to the zip, just open the zip and replace the /system/framework/framework-res.apk file (I'd recommend 7zip).
A Few Goodies
I'm including all of the PSD files I use to edit and create themes. If you want to create your own, custom theme, these will get you started. The only downside to these PSD files is that they are at the MDPI scale. If you want to create an HDPI theme, you'll need to increase the sizes.
Link to PSD files for creating your own theme, plus the flashable CWM zip file:
http://jjis.me/android-theme-templates
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
PMDColeslaw said:
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
Click to expand...
Click to collapse
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
wretchedlocket said:
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
Click to expand...
Click to collapse
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment updater-script.zip
PMDColeslaw said:
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment 546902
Click to expand...
Click to collapse
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
PMDColeslaw said:
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. I had too many things to do with the family yesterday.
If you haven't got this working yet, I'd suggest trying to start with removing just the /system/app/Vendind.apk file via the updater-script. If it works, then go back in and add each additional line until you run into problems again. At that point, you'll know what your problem is.
Since everything else (framework-res.apk, services.jar, etc.) gets replaced successfully, leave those lines alone. I'd just start with the basics of replacing the Vending.apk first and then work your way back up from there.
Is there a way to get rid of the annoying arrows on the HTC keyboard. Im running the ViperLTE 2.2.0 rom and there is a option in venom tweaks to get rid of the arrows but it doesn't work.
please have a nandroid before doing this. if you break the keyboard you will need to install on from the market to rename it back to apk if you choose to do the second method.
push via adb
$ adb push HTC_IME.apk /system/app/HTC_IME.apk
$ adb reboot
or if you use a file explorer app go to /system/app
find HTC_IME.apk and rename it to .bak
place new one in spot
change permissions to RW*R**R**
reboot.
let me know if you need anymore help, i can make this a zip to flash too if you like.
edit: This should work on any sense 4.* ICS rom for the inc 4g but i only tested it on viper. Will not work on CM10.1 sorry
first keyboard i broke the predictive text. if anyone has downloaded this please delete the one that was around 4mb.
the new one i just uploaded is working 100% and should be about 4.5mb
should have fully tested it. sorry for any confusion.
My computer doesn't work and my phone won't let me use file manager. It would be great if it was a flash able zip file so that it can be easier.
Sent from my ADR6410LVW using xda app-developers app
sorry for the delay, i've been busy setting up my buildbox so i can start building cm again.
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