Related
So far, I've settled on Sense-Able as the ROM I like the best. I really don't like the dialer's theme though... Black text on blue gradient background isn't the most contrasting choice, IMO. I'm color-deficient with shades of darker colors too so that doesn't help.
How can un-theme this dialer ? I'm guessing that's not practical, so replacing the dialer is my next option (?). How do I do that ?
Download Dialer one off market its free. you can theme that. its awesome. I am using ivans. there is a thread someone made a zip that delete the old dialer and replaces with dialer one, its great
Deletes the HTC dialer?
No, based on what I read (likely the same thread), it doesn't delete it. People said that the HTC dialer still comes up after a call is placed, i.e. when you hit the "keypad" button so you can input numbers when prompted.
I do have Dialer One already. I have no general complaints about HTC's so I'd rather un-theme it or replace the Sense-Able version.
Have you tried pushing phone.apk and changing the permissions? I did this with a new rosie to an old version of aloysius and it worked fine after I changed the permissions with root explorer.
I've tried nothing. I don't have a clue where to start, hence my thread here.
Do you have root explorer? If so, make sure you have a nand before you experiment. What I did with my rosie was basically copy the new one to my sd card from my computer that I had earlier pulled from a new version from a rom. So, with the new version copied, open root explorer, copy the new phone.apk. navigate to your system/app and remove the old phone.apk and paste the new one. Long press new apk and open permissions. Set all that apply and then reboot when done.
If you dont have RE you can use adb shell. Same process really, push new apk to sdcard (can also be pushed from tools folder also). rm old apk from system/app. push new apk from sdcard or tools. next thing is the chmod command that I am not sure of. Something like adb shell chmod 755, but im not sure since I used RE. Hopefully someone else can chime in that knows this part.
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.
This version has no ATT, White notification text, fixed signal bars, and no FC's! Based on Adeo, so you keep the reboot functionality. This works for me on the new 1.5.2 SBF as well as Adeo. the "newbackup" framework apk is NOT deodexed, and from the new 1.5.2 SBF.
I still need to take new screenshots without the ATT and white notification text, but nothing else changed, so you should be able to use your imagination
New Black Browser (still unfortunately black text and a white text box until I can get apktool to actually build the browser apk).
For those who would like to know, I'm using Launcher Pro Plus, Light Grid LWP, and Beautiful Widgets with the small Super Clock and Simplicity theme with no background. Androdena weather icons.
If you want to revert, please follow the instructions with the framework-old and services-old files renamed to framework-res.apk and services.jar (remove .zip).
For the Black Browser, please just re-run with the backup browser apk.
To install the Browser, copy (cp) your current /system/app/Browser.apk to /mnt/sdcard, then adb push the downloaded apk to your phone in a directory of your choosing, and with root, run cp /path/to/Browser.apk /system/app/Browser.apk and reboot.
If you are deodexed, and you follow these instructions to a tee, there shouldn't be issues. No guarantees if not, though I'm running the new SBF non-deodexed, and no issues.
Here are modified instructions copypasta'd from Designgears (thanks man!):
First, Rename the downloaded services.zip to services.jar (due to xda's upload restriction on .jar files).
[/B]
run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your framework file:
mkdir /data/framework
Exit shell:
exit
Then from the directory of the downloaded files, run:
adb push framework-res.apk /data/framework
adb push services.jar /data/framework
Enter ADB Shell:
adb shell
Copy your new files to their proper location:
cp /data/framework/services.jar /system/framework
cp /data/framework/framework-res.apk /system/framework
Reboot:
reboot now
Phone will flash a red led. Just let the phone reboot (it will take up to a minute, so just be patient!).
IF YOU GET ANY READ ONLY ERRORS WHILE INSTALLING, MAKE SURE YOU'RE IN A ROOT SHELL (IF NOT, TYPE SU), THEN RUN THE FOLLOWING BEFORE TRYING THE FAILED STEP:
mount -o rw,remount /dev/block/mmcblk0p12 /system
nice
i want it
but dammmn its alot of work
I think fastboot might be unnecessary, however for some reason, I've had the best results using super one click every time.
Really, it takes 5-10 minutes, and some copy pasting...I've already done the hard stuff.
Im planning on releasing a shell script to be run in the folder with the files on the phone with terminal emulator, but want to polish the theme a bit more.
Sent from my MB860 using XDA App
thanks, i'll be bookmarking this page for updates.
synergye, you can remove AT&T from the status bar if you change framework-res.apk/res/layout/status_bar.xml, and carrier length and padding to zero on line 5.
Also, the phone will reboot itself with the reboot now command, it just takes a bit (45-60 seconds). Do that instead of pulling the battery.
Good luck on getting the white text and removing AT&T from the task bar.
Can't wait
shawnbuck said:
synergye, you can remove AT&T from the status bar if you change framework-res.apk/res/layout/status_bar.xml, and carrier length and padding to zero on line 5.
Also, the phone will reboot itself with the reboot now command, it just takes a bit (45-60 seconds). Do that instead of pulling the battery.
Click to expand...
Click to collapse
Thank You very much Shawn! I'm going to change the original post, and remove ATT ASAP.
synergye said:
Thank You very much Shawn! I'm going to change the original post, and remove ATT ASAP.
Click to expand...
Click to collapse
Glad to help
Also, this theme won't mix with Adeo because of the reboot option it uses.
shawnbuck said:
Glad to help
Also, this theme won't mix with Adeo because of the reboot option it uses.
Click to expand...
Click to collapse
I'm actually using Adeo with it right now and still have the reboot option. I would assume this is because I modified the framework-res apk from Adeo.
Thats great, going to install this right now.
Shawn, I've tried droiddraw, microsoft's xml editor, excel, eclipse, wordpad, and notepad won't actually open the status bar xml. What am I missing?
It's a proprietary compiled XML format. To unpack it, you need to use apktool.
http://code.google.com/p/android-apktool/
Use:
apktool d framework-res.apk framework-res
apktool b framework-res.apk framework-new.apk
IMPORTANT:
Make sure you have the META-INF files inside the new apk. The easiest way of doing this is repacking the apk as something new, pulling out the compiled XML files, then adding them into the original apk.
On a side note, its nice to see an honest representation of what data connection the phone is getting.
I have a question. The data/framework folder we create, is there any reason why we cannot do it from a folder on our sdcard like how we pushed the deodex file over from designgears? Is this just your preference to have it in data or is it 100% required? Just curious cuz after we do all this we will have an empty data/framework folder just sitting there.
There's no reason it can't be in an already existing folder, or just data.
@Sean, thanks for the help, didn't know I'd be using apktool for that.
Sent from my MB860 using XDA App
synergye said:
There's no reason it can't be in an already existing folder, or just data.
@Sean, thanks for the help, didn't know I'd be using apktool for that.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks. There is a minor typo in your instructions. You forgot a space between CP and / for the service.jar line. You will get a directory does not exist without that space
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp/data/framework/services.jar /system/framework
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp /data/framework/services.jar /system/framework
Some reason my signal icons are not showing up properly and stays on white even though i have full bars. also the signal part is still black
NguyenHuu said:
Thanks. There is a minor typo in your instructions. You forgot a space between CP and / for the service.jar line. You will get a directory does not exist without that space
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp/data/framework/services.jar /system/framework
Copy your new files to their proper location:
cp /data/framework/framework-res.apk /system/framework
cp /data/framework/services.jar /system/framework
Some reason my signal icons are not showing up properly and stays on white even though i have full bars. also the signal part is still black
Click to expand...
Click to collapse
Thank you for your correction.I believe this is because I replaced only one set of radio icons, so.if you're roaming, etc, they'll revert. Ill unify them later today. Also, the data portion stays white as if it's uploading and downloading until.it connects.
Sent from my MB860 using XDA App
Another note: after you push framework it will auto reboot, no need to enter in a command. So you push services.jar first, then push framework or else it will reboot before you can do it. Not sure if it will also auto reboot if you push services.jar, but it does with framework-res.apk.
I also noticed that graphics were replaced that were unrelated to the status bar such as graphics for various menu items and popups. It made them have white text on light grey background, which was hard to see. I went through the original framework and compared it with the gingerbread one and only moved over miles that were related to the status bar.
it looks better now, just missing the icons for the signal bars for normal state and also getting rid of the at&t text. Thanks for the mod!
@synergye
Would changing the images in the framework file work? Or would we need to take any special care? I mean, if we update the images only in the framework file and push that to our phone, would it work?
diablo009 said:
@synergye
Would changing the images in the framework file work? Or would we need to take any special care? I mean, if we update the images only in the framework file and push that to our phone, would it work?
Click to expand...
Click to collapse
yeah that's what i did too to replace the images that were misplaced. just change up the images in framework-res, then follow the directions in the OP to push it back in. i did it several times today.
you still gotta be wary of making your own though cuz some of the pngs are .9 extensions, those are tricky. but if you just copying and pasting images from other frameworks over, that should be fine.
NguyenHuu said:
yeah that's what i did too to replace the images that were misplaced. just change up the images in framework-res, then follow the directions in the OP to push it back in. i did it several times today.
you still gotta be wary of making your own though cuz some of the pngs are .9 extensions, those are tricky. but if you just copying and pasting images from other frameworks over, that should be fine.
Click to expand...
Click to collapse
I only want to change the status bar to something dark, and the battery icon to be one with numbers so I can take off the battery level app.
The stock battery icon on Galaxy wifi 5.0 is not very inspiring and it doesn't tell you the battery level. It is quite easy to replace them on other phones with Clockwork Recovery. You just need to go to UOT kitchen http://uot.dakra.lt/kitchen/ , pick the icons you like and it will give you a flashable zip file.
Without Clockwork Recovery on Galaxy wifi, it can still be done but with a bit more manual operations.
Prerequisites:
1. A rooted device.
2. Clockworkmod Recovery (optional).
Step 1:
Use Titanium backup (pro version needed) to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. For example converting Flash player and google map to user app free up enough space for me.
Step 2:
Backup the following apk files from your stock rom. You can do that by using some file manager like File Expert. These files will be needed by UOT kitchen
/system/app/SystemUI.apk
/system/framework/framework-res.apk
/system/framework/twframework-res.apk
Step 3:
Go to UOT kitchen http://uot.dakra.lt/kitchen/ and cook your custom UI. Make sure you read their how-to here first http://uot.dakra.lt/how_to/
Step 4a: (follow this if you have Clockworkmod Recovery)
Copy the zip produced by UOT kitchen to your internal SD card. Reboot to CWM Recovery and flash the zip file using the option "Install zip from sd card". Then reboot and you are done.
Step 4b: (follow this if you don't have Clockworkmod Recovery)
Extract the 3 modified apk files from the zip package produced by UOT kitchen and put them into a convenient location on your sdcard, say /sdcard/
Step 5:
The system directory is by default read only. You need to remount it as r/w. I do that through adb shell
Code:
su
mount -o rw,remount /dev/block/mmcblk0p13 /system
Step 6:
Copy your new apk files into /system directory
Code:
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/framework-res.apk /system/framework/
cp /sdcard/twframework-res.apk /system/framework/
Step 7:
Restart your device. The /system directory should remounted as read only and the new UI will take effect.
Disclaimer:
Certainly there are risked involved and I did corrupted my rom on several occasions when trying this out. So make sure you have a functional ROM around before you give this a try.
thanks for the tips.
hey I wanna ask you about is it can fully modification from http://uot.dakra.lt/kitchen/
I mean don't just modify battery icon but every option that site provide.
thanks in advance.
" Step 1:
Use Titanium backup to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. The flash. For example converting Flash player and google map to user app free up enough space for me."
How do you do that with titanium backup? Do you have to get pro?
aillez said:
thanks for the tips.
hey I wanna ask you about is it can fully modification from http://uot.dakra.lt/kitchen/
I mean don't just modify battery icon but every option that site provide.
thanks in advance.
Click to expand...
Click to collapse
I have only experimented with icons so far. Other mod may be possible because UOT kitchen does support gingerbread. Since this device is new, we need some brave soul to try that out
iJimaniac said:
" Step 1:
Use Titanium backup to free up some spaces in /system directory (There are 0 byte free in stock rom). You can delete some unused system apps or convert some of them to user app. The flash. For example converting Flash player and google map to user app free up enough space for me."
How do you do that with titanium backup? Do you have to get pro?
Click to expand...
Click to collapse
Yes, you will need the pro version. If you have the pro version, long press an app will give you the option to do the conversion.
Well, while deleting apps with TI, I decided to get rid of "phone", figuring I didn't need it, but it turns out Google voice needs it! Trying to "restore", but just hangs forever. If someone could give me the "com.sec.android.app.dialertab.apk" located in /system/app/ I would really appreciate it!
EDIT; I just reinstalled voice from market, seemed to fix it, I wouldn't advise removing phone from the apps though!
can you make the display of battery accurate to 1%?thank you!
First make it accurate to 5%, then work on 1%
I think the accuracy of the battery level is deeper down in the system, may be in the kernel?
If you try different types of battery widget on Galaxy Player, they all have very bad accuracy.
I want to edit the framework-res.apk manually, instead of using the kitchen. Do the files need to be deoxed? Would flashing a framework-res compiled with apk manager brick the device?
nice guide!
I've used UOT Kitchen to get ICS transitions, change icons, battery, fonts, and customize the status bar and they all work on my galaxy player 4.0 US.
what are those different icons you have on your notifications like the wifi icon and what launcher is that ADW?
azoller1 said:
what are those different icons you have on your notifications like the wifi icon and what launcher is that ADW?
Click to expand...
Click to collapse
I am using the "Color pack V8 animated" icon set on UOT kitchen. The launcher is GO Launcher.
Stale_bread said:
I want to edit the framework-res.apk manually, instead of using the kitchen. Do the files need to be deoxed? Would flashing a framework-res compiled with apk manager brick the device?
Click to expand...
Click to collapse
There is still an odex file in the system directory. I suppose it is not deoxed but UOT kitchen doesn't seem to bother with that file. I guess it is because these apk files don't contain any executable code.
from OP
Disclaimer:
Certainly there are risked involved and I did corrupted my rom on several occasions when trying this out. So make sure you have a functional ROM around before you give this a try.
Click to expand...
Click to collapse
Two things, if you please:
When you say "corrupted my rom", you can't boot your device but you can still go to dl mode, correct?
"functional ROM" is the fw/md5 file we usually flash via odin/heimdall?
I'd like to try this out (& then some...) but, in the absence of a custom recovery, I don't wanna have to go through the lengths of "resurrecting" my sgp. TIA!
maxq1 said:
from OP
Two things, if you please:
When you say "corrupted my rom", you can't boot your device but you can still go to dl mode, correct?
"functional ROM" is the fw/md5 file we usually flash via odin/heimdall?
I'd like to try this out (& then some...) but, in the absence of a custom recovery, I don't wanna have to go through the lengths of "resurrecting" my sgp. TIA!
Click to expand...
Click to collapse
In my case, it couldn't boot beyond the samsung start up screen, but I can still boot into download mode. Since we are only modifying a file within the file system, it is very unlikely that it will destroy the download mode.
If you can get to download mode, you can flash one of the firmwares you found in this forum using odin. You need to be sure you have the correct firmware for your device though, because there are so many variant of Galaxy Player. What is the version of your device?
nvm that (i was thinking on the same lines too though) but thanks anyway! appreciate it.
thanks to your guide, was able to change my fonts and added that flying in pop up animation as well. for these two, however, i don't think we need the kitchen though and for that matter, we don't need to modify systemui & twframework.
for fonts (you could use font changer apps, but i hate doing so for such things), take any you fancy from anywhere here in xda (WARNING: only extract the downloaded file to your device/pc) then rename (case sensitive) font files accordingly: Clockopia.ttf, DroidSans.ttf, DroidSans-Bold.ttf. copy these to sd & push to /system/fonts/ using similar cp command/s from OP.
for pop up animation, you could follow this guide. no need to sign after replacing files in /res/anim. copy modded framework-res.apk to sd then push to device via same commands in OP.
btw, wouldn't issuing "reboot" within adb shell be more convenient & safer after changing system files while booted to android? it's what i did instead of rebooting via power button, as you'll most likely see an FC fiesta after replacing these files.
maxq1 said:
nvm that (i was thinking on the same lines too though) but thanks anyway! appreciate it.
thanks to your guide, was able to change my fonts and added that flying in pop up animation as well. for these two, however, i don't think we need the kitchen though and for that matter, we don't need to modify systemui & twframework.
for fonts (you could use font changer apps, but i hate doing so for such things), take any you fancy from anywhere here in xda (WARNING: only extract the downloaded file to your device/pc) then rename (case sensitive) font files accordingly: Clockopia.ttf, DroidSans.ttf, DroidSans-Bold.ttf. copy these to sd & push to /system/fonts/ using similar cp command/s from OP.
for pop up animation, you could follow this guide. no need to sign after replacing files in /res/anim. copy modded framework-res.apk to sd then push to device via same commands in OP.
btw, wouldn't issuing "reboot" within adb shell be more convenient & safer after changing system files while booted to android? it's what i did instead of rebooting via power button, as you'll most likely see an FC fiesta after replacing these files.
Click to expand...
Click to collapse
Theses are good suggestions, will definitely give them a try.
As for changing system fonts, I like to use the Font Installer app on the market
https://market.android.com/details?id=com.canvs2321.font_installer&hl=en The nice thing is I can preview the fonts before changing them.
As for the reboot, actually I did try using the reboot command once but it toasted my rom on that occasion. That's why I didn't mention the method in the guide. May be I should give that another try next time.
Hopefully, we will get CWM soon then it will be much easier to flash these mods.
WT Ho said:
I think the accuracy of the battery level is deeper down in the system, may be in the kernel?
If you try different types of battery widget on Galaxy Player, they all have very bad accuracy.
Click to expand...
Click to collapse
Kernel battery driver is very simplistic and only has 5% increments in the numbers it returns.
On my list to look at once I finish CWM - no guarantees.
thhhhhhhhhhhhhhanxx
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