I've never had luck getting fonts changed on ICS and now Jellybean for this device. Every time I attempt I bootloop and give up. Granted I'm only using the ROM Toolbox method as of now, but other program methods changed nothing as far as I could tell.
Is there a process that I'm missing? Attached is a zip containing the orgininal font and the modified version (to remove the [][][] boxes that were popping up)
Any insight would be greatly appreciated, as this font is gorgeous on smaller screens!
Try font changer in the play store. I havent used it with ICS or Jelly Bean. But I used it on Gingerbread and it worked perfectly.
jsgraphicart said:
Try font changer in the play store. I havent used it with ICS or Jelly Bean. But I used it on Gingerbread and it worked perfectly.
Click to expand...
Click to collapse
I guess I forgot to add, I used both that program and ROM Toolbox on Gingerbread (CM7) and it worked wonderfully. I didnt know if there was something else thats different about the install process. Or maybe due to the Alpha nature I shouldnt get my hopes up?
For the love of God, Mother Mary and all the saint's of the church, never use ROM Manager.......ever. That's like the golden rule. (for the X2, that is)
Well if font changer doesnt work, I dont know what else to say. Thats the only method I have used but like I said, I havent tried it on ICS or JB. ICS and JB might have a different method for fonts which may cause Rom Toolbox and font changer not to work. Do some google searches. I found this that might work for you. I would backup your rom before trying though.
http://forum.xda-developers.com/showthread.php?t=1821743
tallyforeman said:
For the love of God, Mother Mary and all the saint's of the church, never use ROM Manager.......ever. That's like the golden rule. (for the X2, that is)
Click to expand...
Click to collapse
Rom Toolbox =/= Rom Manager
magimog said:
Rom Toolbox =/= Rom Manager
Click to expand...
Click to collapse
For the Droid X2, either ROM Toolbox or ROM manager isnt recommended. These two apps can make changes to the ROM that our device doesnt support. Like stuff that requires an unlocked bootloader, which our device doesnt have. People have said that changing fonts or a boot animation will work fine but anything other than that, it can potentially cause big problems. So bottom line, be careful with what you do with it.
jsgraphicart said:
Well if font changer doesnt work, I dont know what else to say. Thats the only method I have used but like I said, I havent tried it on ICS or JB. ICS and JB might have a different method for fonts which may cause Rom Toolbox and font changer not to work. Do some google searches. I found this that might work for you. I would backup your rom before trying though.
http://forum.xda-developers.com/showthread.php?t=1821743
Click to expand...
Click to collapse
jsgraphicart said:
For the Droid X2, either ROM Toolbox or ROM manager isnt recommended. These two apps can make changes to the ROM that our device doesnt support. Like stuff that requires an unlocked bootloader, which our device doesnt have. People have said that changing fonts or a boot animation will work fine but anything other than that, it can potentially cause big problems. So bottom line, be careful with what you do with it.
Click to expand...
Click to collapse
I was pointing out that Rom Manager is in no way the same thing as Rom Toolbox. The former deals with rom downloads, mods and recovery installation, whereas the other is a collection of root tools. Toolbox is just a hub for the multitude of JRummy apps. I've only used it to have a one-stop for adblocking, root browser and animation/theme changing. Those 3 tasks work perfectly in CM9/10.
I will just try manually switching out the fonts to see if that changes anything. I was looking to see if there were other X2 users who were successful in performing this task within a CM9/10 environment. I'll assume no one has for now.
Well I havent seen anyone else ask about changing fonts in ICS or JB. I wouldnt know how to do it if the other two methods dont work. Again, I would search around for a Universal method rather than one specifically for the DX2. I think the usual methods not working are more due to the change of the way ICS and JB handle things than our ROM not being complete though.
Related
I saw this thread a few weeks ago, but now i wanna ask you guys that will this method works for our O1? I personally hate the clock font a lot!
http://forum.xda-developers.com/showthread.php?t=1061483
And if it works, do i need to root?
or just directly fire up the adb?
hon kin said:
I saw this thread a few weeks ago, but now i wanna ask you guys that will this method works for our O1? I personally hate the clock font a lot!
http://forum.xda-developers.com/showthread.php?t=1061483
And if it works, do i need to root?
or just directly fire up the adb?
Click to expand...
Click to collapse
adb cannot communicate to your device if your device is not rooted. it needs SU (super user)permission.so rooting is a must.
then how to....http://forum.xda-developers.com/showthread.php?t=1007244.
before you play with anything please install custom recovery and take a back up( i mean a nadroid backup)
before theaming it check that the rom you are using is deodexed unless you cant see the changes.
Just use Widget Lock it does all you want without flashing ****, use ClockR for different clock fonts.
Hi,
I recently installed a custom ROM in my phone.
What I noticed is that the problem is either that my phone drivers can't be installed for some reason (I have a SGS being treated as a Google Nexus S), or I just can't implement applications.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
Which one is it?
anyone?
spyshower said:
Hi,
I recently installed a custom ROM in my phone.
What I noticed is that the problem is either that my phone drivers can't be installed for some reason (I have a SGS being treated as a Google Nexus S), or I just can't implement applications.
Which one is it?
Click to expand...
Click to collapse
What do you mean by "I just can't implement applications"?
Do you mean you cannot install apps from the market? If so, are you sure you installed a ROM for the Samsung Galaxy S? Have you manually changed your screen DPI or is the ROM modified in any way regarding the screen DPI?
polobunny said:
What do you mean by "I just can't implement applications"?
Do you mean you cannot install apps from the market? If so, are you sure you installed a ROM for the Samsung Galaxy S? Have you manually changed your screen DPI or is the ROM modified in any way regarding the screen DPI?
Click to expand...
Click to collapse
I didn't describe my problem, my bad.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
I am pretty sure there is a simple answer and tons of people know if developing apps on custom roms is available. I dont get why none answers
spyshower said:
I didn't describe my problem, my bad.
I mean that when I try to build an application on Eclipse, my phone is not recognized, like I don't have it plugged in.
Click to expand...
Click to collapse
spyshower said:
I am pretty sure there is a simple answer and tons of people know if developing apps on custom roms is available. I dont get why none answers
Click to expand...
Click to collapse
Install the drivers for your device.
Comes up I had the drivers. I tried reinstalling them and it didn't work again.
I also tried it in another PC with no luck
Not sure if it matters but the custom ROM I have is Dark Knight 3.
Hello Developers!
I work with Jrummy Apps Inc, the company and developer who brought you Rom Toolbox, Root Browser, Ultimate Backup, Busybox Installer, and many other root apps.
First, some background:
ROM Toolbox combines all the great root apps into one monster app with a beautiful and easy to use interface. ROM Toolbox has every tool you need to make your Android device fast and customized to your liking. ROM Toolbox has been featured on LifeHacker, XDA-Developers, Droid-Life, Android Central, RootzWiki, Android Police, DroidForums and other popular sites. ROM Toolbox has one of the highest ratings in the top 100 paid apps. Over 12,000 people gave it a full 5 star review! ★★★★★
ROM Toolbox combines apps like Titanium Backup, ROM Manager, Root Explorer, SetCPU, Ad Blocker, MetaMorph, Autorun Manager, Terminal Emulator, Script Manager, SD Booster, BuildProp Editor, Font Installer, Boot Animation Installer & many more apps into an all-in-one app!
The Revamped Rom Manager includes support for OTA updates!
Here’s where you come in:
We want your rom in our app. All roms will be *completely* free to download through our Rom Manager.
Why should you want to put your rom in our app?
Because your rom would be available to a much larger audience with more potential downloads and donations for you.
We want this to be as easy as possible for you.
To get the rom on ROM Toolbox, please do the following:
1) Fill out the file below with the roms/zips you want to have.
2) Save it in JSON format. I recommend using the free program called Notepad++ to modify and save json files.
3) Upload this file to your server. That way you can be in control of what ROMs show up at all times. Otherwise we can host it ourselves.
4) Send us the link to this file on your server.
5) Send us a summary of the ROM.
6) Send us the name of the ROM.
7) Send us the devices you support.
Code:
{
"version": "1", /*Keep this here, do not change or modify*/
"homepage": "http://forum.xda-developers.com/showthread.php?t=...",/*link to website or original thread*/
"donate": "https://www.paypal.com/...", /*donation link*/
"roms": [
{
"name": "NoWizAOSPmod v.1.4.2 (7/22)",/*Name of Rom*/
"product": "NoWizAOSPmod",/*Name of series*/
"summary": "NoWizAOSP is a rom without wiz, and mimicking aosp...", /*Description of rom, and as updates begin, you will want to put changelogs here.*/
"device": "d2spr", /*device id*/
"url": "http://xeoduxus.com/downloadable/nowizaosp.zip" /*Direct download link, no goo.im please.*/
}
]
}
Note: you can add as many zips/roms as you want.. just add another section right under the "rom" entry. If you need any assistance filling this out feel free to ask and we can help you!
If you'd like to use addons, optional, flashable downloads with your rom, please let me know and I'd be happy to explain how to do it.
Ideally we would love for you to maintain your own download link. If this is not possible, please contact us and we'll do our best to help out.
ROM Toolbox is going through a major overhaul currently and has been completely rewritten. We want you to be a part of this!
Thanks!
~ Master Ramy
Jrummy Apps Inc.
(Mods, wasn't sure if this should go here or in development. Feel free to move it.)
Now is your chance, developers! Get in on this!
I recently uninstalled the paid version of ROM Toolbox as almost none of the functions worked in the Note 2.
Is the new version going to have all the functions available for the Note 2??
Yeah I cant even get Rom Toolbox to boot on this phone
If only there was a dedicated place here at XDA to find ROMs to download. Complete with support threads, change logs, and donation links to the Dev ....
Sent from my SCH-I605 using Tapatalk 2
jmorton10 said:
I recently uninstalled the paid version of ROM Toolbox as almost none of the functions worked in the Note 2.
Is the new version going to have all the functions available for the Note 2??
Click to expand...
Click to collapse
Strange. I have the paid version also. Rom toolbox works fine on my Note 2. Everything I have used with rom toolbox works. I even installed the updated twrp 2.3.3.1from this app. They do need to get the latest 2.3.3.2 which has been out 5 days. As long as rom toolbox can stay updated I will always use it.
Have you tried changing the status bar icons??
I never used it for things like updating TWRP, once you have that installed its pretty simple to update anyway.
jmorton10 said:
Have you tried changing the status bar icons??
Click to expand...
Click to collapse
it does let you change some of the just not the 4g icon. ive changed the battery,vibration,wifi,usb with rom toolbox. the boot animations, fonts and some other things work as well. its as great app and i will always use it. everything work but a few icons. its even replaced titanium backup for me.
It must depend on what ROM you're running as none of the icons I tried worked with beans ROM (unless its been updated just recently)
Actually, all I tried to change where 4g and battery and it didn't work for either one so I gave up.
There where quite a few posts about this a few weeks ago, it wasn't working for anybody.
As far as Titanium BU, I never use that myself. i just BU quite a bit with CWM.
jmorton10 said:
It must depend on what ROM you're running as none of the icons I tried worked with beans ROM (unless its been updated just recently)
Actually, all I tried to change where 4g and battery and it didn't work for either one so I gave up.
There where quite a few posts about this a few weeks ago, it wasn't working for anybody.
As far as Titanium BU, I never use that myself. i just BU quite a bit with CWM.
Click to expand...
Click to collapse
for the battery you will have to filter out everything but the 1% icons and that will give you all the icons you can use on beans rom. the 10 and 20% icons will not work cause beans is 1% increments
neckbonest said:
it does let you change some of the just not the 4g icon. ive changed the battery,vibration,wifi,usb with rom toolbox. the boot animations, fonts and some other things work as well. its as great app and i will always use it. everything work but a few icons. its even replaced titanium backup for me.
Click to expand...
Click to collapse
I have done the same with my backups. Rom toolbox has been busy lately. I'm happy to see this.
I luv beans also!
Dakota0206 said:
If only there was a dedicated place here at XDA to find ROMs to download. Complete with support threads, change logs, and donation links to the Dev ....
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Maybe this list will help you a little.
Up-to-date ROM List for Galaxy Note 2
:angel:
You missed the dripping sarcasm of his post somehow grant. He's saying we already have that
Sent from my SCH-I605 using xda app-developers app
While XDA is excellent for all these functions, it is not as accessible as an app for people who wanna get things done directly on their mobile device. XDA also does not offer the ability to directly backup and flash the rom, change icons, etc.
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.
Hey,
i´m just wiondering if i can change font using rom toolbox on a samsung stock firmware? Will it work?
spartanier7 said:
Hey,
i´m just wiondering if i can change font using rom toolbox on a samsung stock firmware? Will it work?
Click to expand...
Click to collapse
Im not familiar with "rom toolbox", but all font changers work the same, by renaming a font to be the name of the default font, so in theory it should work.
I just use this though.
https://play.google.com/store/apps/details?id=com.jrummy.font.installer
But I am on AOSP anyway
To anyone who is trying to change it with rom toolbox or this tool (it actually is an part extracted from the toolbox). DON´T! On AOSP it works but it will shredder your Sammy system .
Lucky enough i had a backup!
If you're on stock ROM, why didn't just changed the font on settings?
I dont really like the preinstalled ones and if i install another one from store it always says : font not available.. even though its already instaled
spartanier7 said:
To anyone who is trying to change it with rom toolbox or this tool (it actually is an part extracted from the toolbox). DON´T! On AOSP it works but it will shredder your Sammy system .
Lucky enough i had a backup!
Click to expand...
Click to collapse
it is only partially true: i already changed my fonts many times with rom toolbox on sammy roms. and it worked everytime except for one time when it bricked my rom. The same was it on my old sammy phone. the first time it worked the second time... well I guess you know the answer (and that taught me the lesson: always have a working backup before doing any changes on a rom)
so I can confirm it can work, but there is a chance that it bricks your phone. so maybe on the second try it works.