Hi, I rooted my TB today and changed fonts, after I restarted it, my phone stopped after the booting sound.
so I went back to stock, and rooted again!
Now, I really want to change the font but I don't want my phone to brick.
What's the safe way to change the font?
When I changed the font first time, I downloaded XXX.ttf file and changed the name to "DroidSans.ttf" "DroidSansFallback" and "DroidSans-Bold" and copy them to "/systems/fonts/"
katsymoon said:
Hi, I rooted my TB today and changed fonts, after I restarted it, my phone stopped after the booting sound.
so I went back to stock, and rooted again!
Now, I really want to change the font but I don't want my phone to brick.
What's the safe way to change the font?
When I changed the font first time, I downloaded XXX.ttf file and changed the name to "DroidSans.ttf" "DroidSansFallback" and "DroidSans-Bold" and copy them to "/systems/fonts/"
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=1013013
doesnt belong in development
Hi,
I tried to change DPI through LCD density modder app to dpi 226 in my sgs2.
After that the phone dont boot-up and got stuck at yellow triangle screen
I can go to CMW mode but dnt have any backup in that.i flashed Cf root again to check if that work,but nothing happen
NOTE: it got bricked because of change in DPI.not because of flashing wrong kernel so Flashing kernel wont help me
What to do,please help me
Can you mount USB in CWM to change the kernel ?
Because some kernels, like Siyah (I THINK ! I don't use Siyah...) purpose to clear some folder including DPI section...
So you can try to take one of this kernels, flash one, and find this option...
I'm not sure, just a supposition
UlbaWan- said:
Can you mount USB in CWM to change the kernel ?
Because some kernels, like Siyah (I THINK ! I don't use Siyah...) purpose to clear some folder including DPI section...
So you can try to take one of this kernels, flash one, and find this option...
I'm not sure, just a supposition
Click to expand...
Click to collapse
Missed the part about it not being a kernel issue, did you?
hungryheart said:
Hi,
I tried to change DPI through LCD density modder app to dpi 226 in my sgs2.
After that the phone dont boot-up and got stuck at yellow triangle screen
I can go to CMW mode but dnt have any backup in that.i flashed Cf root again to check if that work,but nothing happen
NOTE: it got bricked because of change in DPI.not because of flashing wrong kernel so Flashing kernel wont help me
What to do,please help me
Click to expand...
Click to collapse
You should be able to connect to your computer in CWM recovery mode, and edit the dpi setting in your build.prop file.
failing that, worst case scenario, just copy a new rom to ya sd and flash it in cwm, a custom one
seriously, you got bitten my friend, next time, do a nandroid backup and backup ya efs folder, double protection, coz seriously if ya gonna mess with stuff like the build.prop then ya need a backup plan.
If you really want to alter the dpi, then check the lcd density changers on google play, theres a few, but i know a couple of them let you test the dpi out first to see if it works on ya phone, if it doesnt it reverts back.
ctomgee said:
You should be able to connect to your computer in CWM recovery mode, and edit the dpi setting in your build.prop file.
Click to expand...
Click to collapse
As above;
1. Download & instal Windows PC programs "Android Commander" and "NotePad++ "(not NotePad)
2. Boot into CWM Recovery
3. Connect to PC USB & allow/edit for any drivers to instal
4. Run Android Commander
5. Navigate to system/build.prop & copy to PC & edit ro.sf.lcd_density=240 with NotePad++. Check there are no entries added by the app (delete them if so) Save and exit
6. Replace build.prop with edited version
7. Exit program, connect USB and reboot
8. All else fails, wipe cache/Dalvik and reflash ROM.
Hope this helps
Edit: don't forget to remove/delete the LCD Modder app from data/app with Android Commander before rebooting, otherwise it may force your previous density changes and back to square one.
You can also extract the build.prop from your ROM download zip with 7Zip and use above method to replace it.
Sent from my GT-I9100 using xda premium
Thank you all for your help
when i flashed CF-ROOT,i didn't work,but when i flashed STOCK KERNEL,it worked
i saw the odin log,stock rom has factory image file which correct the DPI.i think so
Thanks for giving your precious time
I found this thread through google, so thought i might post my experiences for the next person that finds this the same way, maybe some of it will be relevant...
So i did the same thing with my galaxy Note: changed DPI with LCD density modder app, restarted and the phone wouldn't get past the white samsung screen.
I followed UpInTheAir's guide to step 7, but phone still wouldn't start. I hadn't made a backup of the EFS folder so i was getting pretty scared at this point as loading a new rom will wipe this folder and render the phone useless (as far as i understand)
I was reading elsewhere that the permissions need to be set to rw-r--r-- on the build.prop file, so i tried doing this with Android Commander with the phone in CWM recovery. Android Commander was spazzing out, error message when the program opens, constant "loading" bar going, but i just ignored all that. I went to /system/build.prop properties and tried to set the permissions to rw-r--r-- but after accepting that and going to properties again it hadn't updated the permissions.
I've never flashed a ROM before, or changed kernel, but i decided this might be a good time to learn.
I loaded franco.Kernel-r5 for galaxy Note (sorry if this is irrelevant in an S-II forum) but loading into CWM that is built into this kernel (i think it was a different version than i was using before) i was then able to update the permissions with Android Commander(tho it was still spazing out).
Restarted and BOOM she loaded. Understandably i was thanking God big time at that point
anyway, hopefully something in this mess of a post might come in useful to somebody , thanks for the good info UpInTheAir!
Hello, I had the same problem and had to re-flash the firmware.
I've seen on dpi changers comments on market that A LOT OF PEOPLE get the softbrick.
i want to change my dpi.
how am i supposed to do it ?
I can't believe my phone can't stand changing DPI.
Ive changed mine a few times by altering the build prop file but the icons were never centered properly. Eveything was smaller but moved towards top left of the screen. Since then i used Density Modder pro with no issues.
Sent from my GT-I9100 using xda app-developers app
I have the same problem but i cant even get into cwm recovet. what can i do?
"Unfortunatelly System UI has Stopped!"
Hello everyone!
I have a HUGE problem with my Galaxy S4 i9500 and I really need someone's help here... I changed the pixel density/screen resolution, with the "Density changer" from the "Pimp my rom" app (I'm root user) and I can't use my phone AT ALL(not even the status bar)!!. I can only access the Lock Screen and the Lock Screen shortcut icons(could because I tried formating the phone but nothing changed so now only lock screen)... Also lock screen is super small, because I think I clicked the 200dpi(I THINK) option.When I unlock the phone, to access to the UI the screen is total black and this 2 messages are being deplayed : "Unfortunatelly, System UI has stopped" and "Unfortunately,TouchWiz Home has stopped",I don't have CWM Recovery flashed. Please reply! :crying: HELP!
Yiannis Hadjittofis said:
Hello everyone!
I have a HUGE problem with my Galaxy S4 i9500 and I really need someone's help here... I changed the pixel density/screen resolution, with the "Density changer" from the "Pimp my rom" app (I'm root user) and I can't use my phone AT ALL(not even the status bar)!!. I can only access the Lock Screen and the Lock Screen shortcut icons(could because I tried formating the phone but nothing changed so now only lock screen)... Also lock screen is super small, because I think I clicked the 200dpi(I THINK) option.When I unlock the phone, to access to the UI the screen is total black and this 2 messages are being deplayed : "Unfortunatelly, System UI has stopped" and "Unfortunately,TouchWiz Home has stopped",I don't have CWM Recovery flashed. Please reply! :crying: HELP!
Click to expand...
Click to collapse
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Thanks for the reply
king_below_my_lord said:
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help!! My phone is ok now..
same issue
Having the same issue I'm using Asus memo pad smart 10. Stuck in the boot screen after I tried to change my LCD density through ROM toolbox. Been like that for days. Do I need to follow the same procedure?
Thx
If you can enter recovery then flash maybe some DPI changer or what
Sent from my GT-I9100 using xda app-developers app
can't use recovery when I try to, it gives me a android lying on its back with the message "error" managed to wipe data though, now I can boot it fully however when I get to my lock screen it says that UI launcher ASUS keyboard and audio wizard have all stopped
corrupted apps?
king_below_my_lord said:
First of all you will get better answers if you asked in your device's relevant thread, TouchWiz Home usually doesn't take too well to dpi changes, you need to install a custom launcher app like apex or Nova, try installing one via adb, and then reboot and select your custom launcher as default when the system prompts you to select a launcher.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
i have this issue two but i factory reset my tablet because that would fix it and now the setup doesn't work and i can't fix it and the only thing i can do is the recovery menu if that helps if you have some sort of solution please let me know
many thanks ben
Try resetting via adb
ben12345678901 said:
i have this issue two but i factory reset my tablet because that would fix it and now the setup doesn't work and i can't fix it and the only thing i can do is the recovery menu if that helps if you have some sort of solution please let me know
many thanks ben
Click to expand...
Click to collapse
Encountered the same error using screen shift (https://forum.xda-developers.com/android/apps-games/app-screen-shift-change-screen-t3138718) I may be too late but I hope It may help somebody
For JB 4.3 and above:
Code:
wm size reset
wm density reset
wm overscan reset
Below JB 4.3:
Code:
am display-size reset
am display-density reset
i have the same problem but with my rooted galaxy note 4, i used an app to change my dpi but i set it from 640 to 140 and now the phone doesnt do anything except show me "Unfortunately the system ui has stopped" and it doesnt even show any icons, just my wallpaper and the tiny little error,, i tried fixing it with adb commands but my pc isnt authorized to my phone and i dont have a way to authorize it but usb debugging was on but i dont thing that will help, what do i do???
3ryl said:
i have the same problem but with my rooted galaxy note 4, i used an app to change my dpi but i set it from 640 to 140 and now the phone doesnt do anything except show me "Unfortunately the system ui has stopped" and it doesnt even show any icons, just my wallpaper and the tiny little error,, i tried fixing it with adb commands but my pc isnt authorized to my phone and i dont have a way to authorize it but usb debugging was on but i dont thing that will help, what do i do???
Click to expand...
Click to collapse
Try booting your device into safe mode, it should boot without loading the app that you installed to modify dpi. If you successfully boot into safe mode, you can uninstall the app then reboot.
Sent from my LGL84VL using Tapatalk
I have found a good work around for those of you who may enjoy more usable space on your screen. With the screen the S4 comes with it only makes sense to use it. Only follow these steps after you are running on Hyperdrive ROM successfully (I am guessing this will work with other roms as long as Xposed Framework can be installed).
Background Work (no major changes yet)
1) Open the app Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Framework Installer
3) Click Install/Update
4) Select the tab 'modules' from the top
5) Check all the boxes you see (I had 3)
4) Click Reboot
Let's get started
1) Reopen Hyperdrive Control
2) Navigate Custom Settings > Advanced Mods > Per App DPI Settings
3) Select Google Keyboard
4) Turn the switch to ON
5) Enter 160 for DPI, 100 for Font and check the box labeled 'xlarge res'
6) Click save and click yes.
7) Repeat steps 4-6 with the apps Swype and Samsung Keyboard
8) Make sure you followed the above steps then continue
9) Now find an app called Android System from the list and select it.
10) Enter 280 and don't change anything else (I don't know what you would be doing so I stayed away)
11) Click save and click NO.
12) Restart and enjoy.
I went back and changed System UI to 340 as I didn't like how small the notification bar became. Also recommending ExDialer as the stock keypad won't 'stretch' and lastly as a must, look into a good launcher. I am using NOVA Prime.
If you want to undo changes you can simply turn everything 'Off' and click Save and No. Then restart.
Hopefully this helps some!
If I am missing anything or if anyone wants to add more detail let me know! Side note: random but AOSP helper was installed on my device also allowing easy toggle from 3G to 4G with JuiceDefender...
Colton
Mods can you list this as a [HOWTO]... sorry left that out.
awesome.. .thank you!
OMG thank you for this, i has given up on how to do anything on it. I did not know how to use Xposed frameworks, this is what i needed, than you very much:good:
Has anyone tried changing the overall system DPI and then changing just the misbehaving Samsung applications back to stock (i.e., Contacts/Dialer, Camera)? I pretty much manually set all of my apps to between 320 and 340, but the Notification dropdown is way too big. (Email and Gmail both at 320 in order to become usable).
This made my launcher grid super tiny and the keyboard is unusable it is so small. I can imagine how some slight DPI adjustment could be good, but this is aweful!
that being said, I will use this method to adjust things how I would like them.
I'm glad it worked well for you guys but both of those changes made things worse for me. I put it back on stock and am very happy with it.
I'm running 320 DPI in my build prop. To fix the dialer I went into the per app DPI and changed the contacts app and phone app to stock 480 DPI and also the calculator app as well. They all run just like stock now no problems at all
Forgot to mention gallery as well
Sent from my SCH-I545 using xda premium
im using 360 in my build.prop. and have had no problems. only thing i had to fix was my market. which i used this market found here
http://forum.xda-developers.com/showthread.php?t=1839871
using the correct version of the one in my current rom(hyperdrive). Dont ask me why this works. But someone else said they tried it and it worked. so i did and it worked. Sometimes ive noticed it will all the sudden on reboot, change to a different version of the market. But that has only happened a couple of times. and usually it didnt matter(most apps still showed up like normal). But i dont know that this will work the same way for everyone since it seems to be a semi flakey method.
It works fine in HyperDrive RLS 4. Don't try to change the build.prop for the first boot, though. Let it boot once, then change it. Let's just say that the results were a hung device first.
I added clock back to 480 because there are issues with it.. The year view in Calendar is a bit off, but that's the only screen that doesn't work right... The Market works fine at this resolution (360). This is much easier than what I was doing before...
Now Touchwiz can be somewhat usable as it isn't huge gigantic text everywhere (even on the Tiny selection in Screen)
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
kcellb said:
My system ui keeps crashing whenever I change anything related to Android System. Followed the directions but no luck so far.
Click to expand...
Click to collapse
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
jeffreycentex said:
That's why I just went the other way around and changed build.prop then made things larger as needed. Less problems this way...
Click to expand...
Click to collapse
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
colton22 said:
I will be the first to admit that I am not an expert at this in anyway. This is just how I got it to work...
You said Hyperdrive Build 4 is working for you? I flashed it and have had nothing but troubles so far. It always hangs at SAMSUNG Custom boot screen... I have tried everything and now once I went back to my Nandroid of 3.1 it boots up with no issue, Then I go to reboot through the power menu and it hangs on that screen again.
Colton
PS I guess an easier approach also to allow most programs to stay stock would be to allow the android system to stay stock and just change what you need like the launcher...
I had the same problem about system ui... make sure you are pressing NO to the option it gives you and then reboot. I also had some DPIs that the phone just didn't like (240)... everything kept fc'ing...
Click to expand...
Click to collapse
I had problems with the first two downloads. Then I was able to get one to work early this morning... Also note that it is supposed to be a wipe'd flash, so make sure you do the format data/cache 3 times, then format system... I generally do a flash of the rom first to make sure that there aren't problems, though, before I format system...
I only use 320, 360, and 480's as DPI's on the S4.
Your approach is the way I used to do, but I wanted everything smaller, so every time I installed a program, I changed it to 320/360.. But then I wanted 320/360 to be the overall and only make exceptions for the things that demand stock DPI.
Understood - I didnt wipe to flash as i never did before without an issue. I am downloading stock ODIN now as something is up with my data partition...? It hangs on every second+ boot from restore/install and will not even boot off an install. I will go to stock odin, root, recovery and then install. Also downloading a fresh copy of Hyperdrive RLS4... Thank you for the tips.
C22
Found a better way!
Okay so I am now on RLS 10.2.0...
Download some type of Root file manager... I paid for/use Root Explorer love it.
Navigate to /system and long press build.prop
Find the line that contains screen density =480 and change it to your desired DPI (I am using 280)
From there all apps/everything is changed to that dpi... some stock apps you will have to use xposed to change them back to 480 just to make it work because they show different resolutions horribly.
I followed these steps...
http://forum.xda-developers.com/showthread.php?t=2269483
works great! Enjoy.. Also on the Multi DPI stock app post, the only one that works with the Verizion phone is the Gallery S4 v2.zip file... The others I am trying to work with the dev on getting up and running for our phones.
Colton22
deleted
Thanks
Peace be upon you all. I am new here and I hope I am posting to the correct forum. I recently installed Cyanogenmod 11 on my galaxy S3 (I am new to rooting and it was my first custom rom ). I noticed that resolution didn't seem as crisp as on the stock firmware. Later on I noticed the same thing with AOKP. I checked the resolution and it was 780X1280 with a pixel density of 320 ppi, whereas the native resolution of S3 is 720X1280 with a pixel density of 306 ppi. I tried to change pixel density using rom toolbox, but still couldn't notice any difference. Any ideas? Thank you
babarali_47 said:
Peace be upon you all. I am new here and I hope I am posting to the correct forum. I recently installed Cyanogenmod 11 on my galaxy S3 (I am new to rooting and it was my first custom rom ). I noticed that resolution didn't seem as crisp as on the stock firmware. Later on I noticed the same thing with AOKP. I checked the resolution and it was 780X1280 with a pixel density of 320 ppi, whereas the native resolution of S3 is 720X1280 with a pixel density of 306 ppi. I tried to change pixel density using rom toolbox, but still couldn't notice any difference. Any ideas? Thank you
Click to expand...
Click to collapse
it probably didn't work. but to get sure: you have rebooted after the change? look into your build.prop (in system folder) for the value "ro.sf.lcd_density" if it is still 320. if yes then try to change it manually to the value you like. then save and close it and reopen the build.prop to look if the change sticks.
I often noticed that rom toolbox (pro) has a problem with the integrated superuser app, so that it don't get r/w permissions to system.
That is the reason why I switched to SuperSu by chainfire, with this Rom Toolbox and all other root apps never had problems
Darkened_Sky said:
it probably didn't work. but to get sure: you have rebooted after the change? look into your build.prop (in system folder) for the value "ro.sf.lcd_density" if it is still 320. if yes then try to change it manually to the value you like. then save and close it and reopen the build.prop to look if the change sticks.
I often noticed that rom toolbox (pro) has a problem with the integrated superuser app, so that it don't get r/w permissions to system.
That is the reason why I switched to SuperSu by chainfire, with this Rom Toolbox and all other root apps never had problems
Click to expand...
Click to collapse
Thanks for your reply friend. It probably did work, icons looked a bit small but, still the text seemed a bit blurry and wasn't as crisp as on the stock rom. I restored the backup of stock rom and checked pixel density and resolution. it showed a resolution of 720x1280 and ppi of 320. Whereas general specs of the phone say it is 306. Or I don't know that 306 is something else .... To sum it up, both the stock rom and CM show a pixel density of 320. But, stock has a resolution of 720 whereas CM had 780 pixels..... don't know what to do.
Things are working fine on Temasek's unofficial CM 10.2 rom. Maybe it was a problem with that rom I installed