Using a file system manager I had a look at the build.prop. I found the DPI to be set at 240.
Has anyone tried a different DPI?
vinokirk said:
Using a file system manager I had a look at the build.prop. I found the DPI to be set at 240.
Has anyone tried a different DPI?
Click to expand...
Click to collapse
some info on DPI changes on android wear I found - https://medium.com/@jwoglom/running-android-applications-on-android-wear-8c04159764a8
Related
can anybody install Font Changer (root) and tell me what's the default value, I've reset my device and forgot to uninstall it first
240.
10 char
finally, thanks a lot!
Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex
Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.
thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!
The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App
Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.
LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App
I was playing with DPI and after reboot it just get stuck in black screen.
I have tried to adb push a stock build.prop I found in the forum, but it doesn't help.
I would not really like to have to reflash the phone.
I believe the only file changed with the DPI programs is build.prop. Should I look somewhere else? Can somebody upload me an stock build.prop file?
thanks
EDV11 said:
I was playing with DPI and after reboot it just get stuck in black screen.
I have tried to adb push a stock build.prop I found in the forum, but it doesn't help.
I would not really like to have to reflash the phone.
I believe the only file changed with the DPI programs is build.prop. Should I look somewhere else? Can somebody upload me an stock build.prop file?
thanks
Click to expand...
Click to collapse
You might look here to fix it with adb http://forum.xda-developers.com/showthread.php?t=1927198 or here http://forum.xda-developers.com/showthread.php?t=1797864 , haven`t used it myself. Good luck.
Thanks, you were right, it was a permission problem
Sent from my iPad using Tapatalk
You can change the fonts on this phone but it doesn't seem to be as easy as it was with the Galaxy 3. I tried installing font APKs and also font apps but they don't show up. I also tried putting a fonts folder on the SD card but no luck. Anyone know how to add additional fonts?
I use Font Installer from the Play Store. Works great.
Thanks Devs. From my VZW G2.
Ifont from store
Sent from my LG-D803 using Tapatalk 4
do you need root
Well, I've tried installing a couple fonts on my rooted G2 with both iFont and Font Installer, but they don't show up. Any ideas?
ANDROID 3G said:
You can change the fonts on this phone but it doesn't seem to be as easy as it was with the Galaxy 3. I tried installing font APKs and also font apps but they don't show up. I also tried putting a fonts folder on the SD card but no luck. Anyone know how to add additional fonts?
Click to expand...
Click to collapse
There are lots of flashable fonts but be careful cause you cant revert back when you flash those fonts
Ponsonby_Britt said:
Well, I've tried installing a couple fonts on my rooted G2 with both iFont and Font Installer, but they don't show up. Any ideas?
Click to expand...
Click to collapse
After you install the font, you can go into settings>display>fonts and set the font to Roboto and it will show your custom font.
In Font Installer, you can also pick one of the other fonts from the list to install over, and keep doing that until you have a whole list of custom fonts in settings. They will still have the original names but if you look at the preview you can tell what font it is.
Ponsonby_Britt said:
Well, I've tried installing a couple fonts on my rooted G2 with both iFont and Font Installer, but they don't show up. Any ideas?
Click to expand...
Click to collapse
With ifont for me it works. Choose,download install reboot done
Sent from my LG-D802 using XDA Premium 4 mobile app
AyDee said:
After you install the font, you can go into settings>display>fonts and set the font to Roboto and it will show your custom font.
In Font Installer, you can also pick one of the other fonts from the list to install over, and keep doing that until you have a whole list of custom fonts in settings. They will still have the original names but if you look at the preview you can tell what font it is.
Click to expand...
Click to collapse
You're right, once I set Roboto, the custom font --helvetica neue --was applied. Now my phone has a bit of "Apple flavoring" to it
im using hebrew language as my default language.
the problem is that only the English language is changing.
i tried to change the font on HellFire rom and its workd
can someone tell me y its working on HellFire and not working on stock rom?
Not replacing all fonts
Hi,
I downloaded iFont and Font Installer. Find a proper font and install to system. Yes its affected and changed font, however it didn't affect system wide. For example; unread mailsnare showed up with new font but read mails still showing with another font which is not newly installed.
Donyou have any idea to solve this problem and aplly font system-wide?
Using MagMa 6.0.1, with RR DPI Changer system app.
I changed the dpi, and the phone immediately said System UI has stopped. Now I can't get use it. The last backup was a while ago.
Any way to use TWRP to remove the effects of the RR DPI Changer app?
I tried deleting the app, but I'm not sure a) if I'm deleting the right files, b) if I'm deleting all the files, and c) if just deleting the app is all I need to fix it anyway, since this obviously affects System UI.
Tried dirty-flashing. No help.
Other posts in similar scenarios suggest reflashing only System, but that doesn't seem to help here since I changed dpi through an app, not just through build.prop.
Is there any way to revert the dpi without just doing a clean flash?
O's said:
Using MagMa 6.0.1, with RR DPI Changer system app.
I changed the dpi, and the phone immediately said System UI has stopped. Now I can't get use it. The last backup was a while ago.
Any way to use TWRP to remove the effects of the RR DPI Changer app?
I tried deleting the app, but I'm not sure a) if I'm deleting the right files, b) if I'm deleting all the files, and c) if just deleting the app is all I need to fix it anyway, since this obviously affects System UI.
Tried dirty-flashing. No help.
Other posts in similar scenarios suggest reflashing only System, but that doesn't seem to help here since I changed dpi through an app, not just through build.prop.
Is there any way to revert the dpi without just doing a clean flash?
Click to expand...
Click to collapse
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
QuoPrimum said:
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
Click to expand...
Click to collapse
I wasn't sure if a dpi-changer app would override manual build.prop edits, but, worth a try. Thank you! Will report back.
QuoPrimum said:
You could copy and edit the build prop file to your desired dpi. The default is 560, I think.
Click to expand...
Click to collapse
ETA: Negative. Changed build.prop dpi to ro.sf.lcd_density=560 — no help. Used TWRP File Manager to delete as many dpi changer files I could find from system/app-priv and data/data, and wiped cache/dalvik — all no help. I have no idea why it wouldn't have reverted the dpi by now. There must be something else.
O's said:
ETA: Negative. Changed build.prop dpi to ro.sf.lcd_density=560 — no help. Used TWRP File Manager to delete as many dpi changer files I could find from system/app-priv and data/data, and wiped cache/dalvik — all no help. I have no idea why it wouldn't have reverted the dpi by now. There must be something else.
Click to expand...
Click to collapse
Sorry about that. Perhaps you could replace systemui itself?
QuoPrimum said:
Sorry about that. Perhaps you could replace systemui itself?
Click to expand...
Click to collapse
Not your fault, of course. Any thoughts welcome. I've tried to replace System UI with other UI mods, to no avail. I'm trying different combinations of wiping and restoring between this backup and past one from before the dpi debacle. Nothing so far, but it's a mission now. If it's fixable, I'm gonna do it.
you could do a dirty flash of same rom. After backup of course.
There is a guide on XDA to change dpi using adb, assuming your phone still boots.
I had the same issue in the past, cannot remember if I fixed it or just reflashed from zero : now I don't modify (whole system) dpi's anymore.
Any chance you can grab the RR DPI changer apk, and share it, to know the method used to change the dpi ?
Do you get bootloop ?
Or since SystemUI is "broken" it does finish boot, but ROM is unusable (notification bar appears, then disappear in loop ? Or lockscreen keep restarting ?)
Or is it the persistent "SystemUI has stopped working" that is preventing you to do any actions ?
May be flashing a dpi changer from TWRP could work... I know most of them just re-update the build.prop, but may be try the stock 480dpi from here :
https://forums.oneplus.com/threads/flashable-zips-to-change-your-dpi-on-android-6-0.401639/
Hope you'll solve this issue !