Related
Hey guys,
I've tried to change my density with lcd density changer (phone is rooted). After restart I've got a bricked phone which I was able to recover.
So I was wondering if there is any possibility to change the density, because 240 is to much for me
Greetings Nico
NicoBD said:
Hey guys,
I've tried to change my density with lcd density changer (phone is rooted). After restart I've got a bricked phone which I was able to recover.
So I was wondering if there is any possibility to change the density, because 240 is to much for me
Greetings Nico
Click to expand...
Click to collapse
hi, i do manually, root the phone, then with a root explorer or es explorer go to /system and search a build.prop, open it and search a line "ro.sf.lcd_density=240" and modify, be careful because its a start-up file
if you have a lg home, its no compatible with other resolutions, i recommends adw home
regards
You can use a App called LCD Density Change or another called LCDDensity
You need root on phone and busybox.
I don't understand the meaning of change the LCD density... can you explain it to me?
Huexxx said:
I don't understand the meaning of change the LCD density... can you explain it to me?
Click to expand...
Click to collapse
LCD Density controls the resolution of the screen. Smaller density means Bigger resolution and Bigger density Smaller resolution.
Yeah, the question is why anybody want worse resolution in a lcd.
As far as I know, lcds are optimized to native resolution, and using other doesn't offer the same quality.
Huexxx said:
Yeah, the question is why anybody want worse resolution in a lcd.
As far as I know, lcds are optimized to native resolution, and using other doesn't offer the same quality.
Click to expand...
Click to collapse
It's supposed to make your LCD look better.
I've tried it on Wildfire before, it does help a little if your screen res is really low.
But on OB, i think it's already good enough.
I've set my resolution from 240 to 170 because I needed 6 lines and rows on my launcher an I really don't like the huge icons an fonts on 240 resolution
Help Please
NicoBD said:
Hey guys,
I've tried to change my density with lcd density changer (phone is rooted). After restart I've got a bricked phone which I was able to recover.
So I was wondering if there is any possibility to change the density, because 240 is to much for me
Greetings Nico
Click to expand...
Click to collapse
I seem to have bricked my phone after changing my density too. How were you able to recover. When the device is on, it doesn't recognize correctly in Windows. I can't seem to boot into recovery. Not able to view device as a hard drive. Any advice? Thanks.
I'm using 200 on Zeus right now, font and icon is too big on 240
Sent from my LG-P970 using xda premium
Use lcd density modder pro from play.
I'm using the pro version because Google play would have compatibility issues if i wouldn't :what:
So if you want to change use that one
LCD Density Modder Pro: http://market.android.com/details?id=com.birdapi.android.dpipro
Boot in recovery usind adb
(Search how to)
Or reflash everything as if it was new
Sent from my LG-P970 using xda app-developers app
What are you doing exactly when you lower it, and what do you get from it?
I saw a few threads about it but they're all procedures and instructions.
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.
nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
dchsub said:
It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.
Click to expand...
Click to collapse
So also I guess that's why a lot of the "lower DPI"-related threads are about looking for compatible apps. Thanks!
Do many people tweak their DPI? Can you share examples of significant advantages of doing so that's worth the hassle of looking for apps/themes that would work on the adjusted DPI? Thanks again!
nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
You're everywhere, nobnut! (Sorry for the off-topic)
Anyway, I hope soon everything will be smooth when changing dpi (maybe CM port or ICS). It's really useful for us with good sighting, I've been using my HD2 at 160 dpi instead of 240 and it's not only neater on the homescreen but very useful in some apps (and a less toyish aspect )
I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O
rerp said:
I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O
Click to expand...
Click to collapse
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240
rerp said:
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
Click to expand...
Click to collapse
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.
AzureD said:
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240
Click to expand...
Click to collapse
nobnut said:
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.
Click to expand...
Click to collapse
Thanks for the link but I don't think that changing the DPI itself is any difficult. It's cleaning up the possible mess after, with changing the incompatible apps. I've heard some of them won't work right on different DPIs. Is there a thread for that around here?
Also, I read one about S-Memo not working nicely, and I use that app a LOT, so I guess I'll be monitoring what they do in that thread too.
I do like how it looks like though. Makes me feel the phone is even bigger.
At 240 (default DPI for 800x480) "all" (can't tell for sure) apps will work. Everything also looks good since, again, it's the default Android DPI and some UI elements will look like crap if you set it to 260 or so. Try out the app and see if you like it. If not just reboot the phone and it'll be back to normal.
Sent from my iPad GT-N7000 using xda premium
Wait... Need some clarification about this... I've gotten some games in the market before and I uninstalled them because they didn't go full screen. They left like a fourth of the screen unoccupied and simply black. If I switched to 240, you think they would take the full screen?
Sent from my GT-N7000 using XDA App
no. for example, live holdem pro looks the same crap on 320 and 240 too
Sent from my GT-N7000 using XDA App
That's not nice. Are there any workarounds for such apps? I thought DPI would be a solution.
I recently installed CM9 a1 on my touchpad and one thing that has been really confusing is the dpi settings and market compatibility. I found that flashing the 120 dpi zip makes the texts really small and even unreadable due to the low pixel density of tp. I tried changing the font size setting to large but unfortunately it only affects system ui and apps but not the third party ones.
My question is, if I change my dpi from stock 160 to 120 or 132 (by editing build.prop) What happens to my installed apps? Do they get updates as usual? And what happens to the apps that are not compatible with the new dpi, do they show up as "unsupported on your device" or just disappear from the market?
Overall, what configuration do you guys recommend?
Thanks
Apps would still run on lower DPIs. Some apps/games need you to toggle the screen stretch to work. You probably won't get updates for many apps. You can fix it by pushing the modified market into system/apps and then fixing its permission. The problem with the modified market is that sometimes it will update, in that case you'll have to clear the app data for the market. Its pretty easy to spot if your market has reverted because the layout is different. Or you can just change the DPI every time you want to install something and reboot and change it back when you're done.
I've been running on 132dpi since the ICS was available. I always change the build.prop in the zip before I flash. I even put the movies market in the gapps zip.
Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel
I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.
chicle_11 said:
I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.
Click to expand...
Click to collapse
I tried the modder pro, but eventually market get's stuck again. the native dpi for the TP is 132 (that's what it is in webos). Wish next to 120 and 160 Dalingrin would also give us a dpi132 patch for the newest builds.
Why doesn't Google just add 132dpi into the next market app so its all official
Beanchimp said:
Why doesn't Google just add 132dpi into the next market app so its all official
Click to expand...
Click to collapse
Because of the variation in screen sizes and resolutions on various devices.
Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?
ArmanUV said:
Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?
Click to expand...
Click to collapse
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.
derausgewanderte said:
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.
Click to expand...
Click to collapse
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.
ArmanUV said:
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.
Click to expand...
Click to collapse
the problem is that market doesn't care what launcher you use. It's trebuchet that needs to be modded to get it to work. Look inside Dalingrin's dpi fixes and you will see two files - trebuchet. apk and build.prop.
Maybe somebody can tell us how to mod trebuchet and we can build our own fix.
Bought a Galaxy Tab S 8.4 LTE 2 days ago. Beautiful device with great screen, but:
First thing you realize is the small font size in several apps, such as Facebook. Barely readable.
Tried to use larger font size in settings. That did some effect on some fonts, but no consistent result.
Same with the Big Font app - font sizes and overall appearance becomes inconsistent.
So the only way seemed to change DPI Settings. Which required rooting.
I did the CF autoroot thing. And fiddled with DPI settings using Texdroider app. Originally was 220 DPI. I tried 420 DPI.
Unfortunately after reboot, I was stuck at "systemui angehalten" error message, and touch screen did not respond to input.
Unfortunately I could not switch off the device (to reboot), pressing power button for ever gave no effect.
Since you cannot remove the battery on this device I had to let it run down completely over night. Then booting into Recovery (or Download Mode) was possible again.
Tried a full wipe in Recovery an rebooted. But endless systemui crash loop remained.
Will try to re-flash via Odin to get it back working.
So this thread is firstly a warning if anybody wants to change DPI settings on the Tab S.
Then some questions:
* Did anybody overcome the small fonts problem by changing DPI and which DPI setting is advisable?
* any way to force reboot in such case?
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
edan1979 said:
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
AppSettings works well.. I changed the overall DPI to 240 because all the fonts were way too big for me.. I then reset certain apps back because some of the stock apps don't work right at different DPIs (camera, etc).
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Appsettings works great!
pibach said:
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Click to expand...
Click to collapse
I have rooted my galaxy for using exposed framework just to be able to use app settings! It then works great. You can set the font size (or dpi I guess) individually for any app. I use different settings ie for Gmail, Facebook messenger, Chrome, Tapatalk... You have to try a bit to find the perfect setting but it's a must.
Without you have tiny fonts!
ok, I installed xposed framework via its installer and then added the app settings module. For those willing to follow this route: you find instructions here: http://www.xda-developers.com/andro...tom-stock-roms-and-hello-to-xposed-framework/
Then it is possible to set DPI (or change font size) for each app individually. Text size and rendering was fine for me with 400DPI for Facebook, Tapatalk, or Nova Launcher. Tried with some other apps as well. Seemingly all look better and are more touch friendly with DPI >= 400. For comparison: stock DPI is set to 320 while real DPI is some 500+.
However it is rather inconvenient to set up each and every app individually via app settings module.
Tried to change the global DPI settings with build prob editor, but that somehow did not succeed, 320 DPI remained unchanged.
Tried with DPI changer to no effect. DPI cannot be changed via these apps. Very strange, have to investigate further.
Then tried again with textdroider, just to check - and device hangs again
No chance of rebooting or anything...but...yeah, found a trick: insert a SIM-card into the slot and then get asked to restart! Works. You can boot into recovery or download mode. Will try with adb to restore the build.prop backup...
Meanwhile - has anyone been able to set global DPI to something like 400-500 successfully? How?
If you look carefully I n the build.prop there usiually got 2 same dpi line... change both or disable one of it.
Sent from my SM-T705 using Tapatalk
Appsettings module is the best option,going in to build.prop is for overall and sends you in to a boot loop .be sure to have a backup
Nexus 5 via Tapatalk
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Unfortunately I don't, I just know what happened the first time I did it.
Appsettings is the best option though
Nexus 5 via Tapatalk
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
the UI will crash since it was build for the original dpi and the ui setting as well... just install another launcher first and clear the Touchwiz data. It wont crash any longer but if you use touchwiz it wont be good looking... and some other touchwiz related apps will crash as well... that one can be settle using app setting to original dpi.
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Samsung is too lazy to support multidpi for their apps that's made for specific DPI values.
I did not use Touchwiz. It is SystemUI that crashes...
pibach said:
I did not use Touchwiz. It is SystemUI that crashes...
Click to expand...
Click to collapse
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
kenkiller said:
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
Click to expand...
Click to collapse
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
pibach said:
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
Click to expand...
Click to collapse
Not really. I change DPI systemwide on my Nexus devices, they don't crash so easily - they are pretty much unified in terms of software.
Samsung really doesn't like to make a one size fits all firmware for the dozens of devices they release, so you get "problems" like this - to be fair, they don't really anticipate the average user to go around fooling with the DPI values.
Probably Samsung has set 320 DPI on all their devices?
pibach said:
Probably Samsung has set 320 DPI on all their devices?
Click to expand...
Click to collapse
Who knows...who cares? Their assets probably isn't made for all the existing DPIs.
Anyway, xposed app settings works fine for most apps, just gotta live with the systemUI being stuck in that.
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
pibach said:
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
Click to expand...
Click to collapse
Sure....Flash Cyanogenmod for it, if it exists and you don't mind losing all of Samsung's features.
Has anyone updated to the newest version of MM (MMB29S) and managed to change their LCD Density setting? I've tried through a number of apps and also tried to manually update the file, but can't get it to work. :crying: The N6 looks awful with the stock setting.
"The N6 looks awful with the stock setting."
Wow, you have really really high standards... QHD is rubbish?
dahawthorne said:
"The N6 looks awful with the stock setting."
Wow, you have really really high standards... QHD is rubbish?
Click to expand...
Click to collapse
I've always had it smaller so it looks awful to me. I just like having extra icons on the screen that's all.
Maybe you should look at Nova Launcher, which allows you to make icons really small and allows you to put a really large number of icons on the screen. I haven't really tried any other launchers because this one is so exceptionally good - you can define icon size, number of isons vertically and horizontally. I'm sure if I tried I could get a lot more on my home screen(s).
dunjamon said:
Has anyone updated to the newest version of MM (MMB29S) and managed to change their LCD Density setting? I've tried through a number of apps and also tried to manually update the file, but can't get it to work. :crying: The N6 looks awful with the stock setting.
Click to expand...
Click to collapse
Have you rooted? If you have, have you used system less root? That won't let you modify dpi, since it can't modify the system partition.
dunjamon said:
Has anyone updated to the newest version of MM (MMB29S) and managed to change their LCD Density setting? I've tried through a number of apps and also tried to manually update the file, but can't get it to work. :crying: The N6 looks awful with the stock setting.
Click to expand...
Click to collapse
in a terminal emulator:
Code:
su
grant superuser to terminal emulator
Code:
wm density 560
replace 560 with whatever number you want 560 is default
aand reboot for full effect.
This can also be done w/o root using ADB on a computer:
Code:
adb shell wm density 560
That's brilliant! Cheers mate!
dpi/pixel density of the nexus 6 is 493, that's why 560 looks like rubbish
buschris said:
dpi/pixel density of the nexus 6 is 493, that's why 560 looks like rubbish
Click to expand...
Click to collapse
384 dpi. Font size 'huge'. The N6 turns to tablet mode.
There is an app called 'build.prop editor'
493 is the density of the screen. Confirmed on the main XDA Nexus 6 page
Sent from my Nexus 7 2013 using Tapatalk
I always go with a density of 440
Khizar said:
Have you rooted? If you have, have you used system less root? That won't let you modify dpi, since it can't modify the system partition.
Click to expand...
Click to collapse
With systemless root I have no issues editing the build.prop, deleting system apps, etc, all of which are stored in the system partition. The only difference between normal root and systemless root is the SuperSU apk and other files are stored outside of the system partition. When installing SuperSU it doesn't modify the system partition, but that doesn't mean you can't modify it.
dunjamon said:
I've always had it smaller so it looks awful to me. I just like having extra icons on the screen that's all.
Click to expand...
Click to collapse
If you're talking about changing your DPI, I use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
I have mine at 480 which is really nice. Requires root btw