I have a Android One version of the X4 and I am attempting to leave the rom stock (be a first for me in almost 10 years). I have it unlocked and the stock settings only allow you to move the DPI or Display size so small and I would like it smaller. I booted to TWRP and and added the line ro.sf.lcd_density to the build.prop file (didn't see it listed). Now when I boot the "Display Size" setting shows Custom (408), no matter how low I make the density setting in build.prop (currently at 300). Is there another config file that controls the minimum value somewhere?
Thanks
sjgieson said:
I have a Android One version of the X4 and I am attempting to leave the rom stock (be a first for me in almost 10 years). I have it unlocked and the stock settings only allow you to move the DPI or Display size so small and I would like it smaller. I booted to TWRP and and added the line ro.sf.lcd_density to the build.prop file (didn't see it listed). Now when I boot the "Display Size" setting shows Custom (408), no matter how low I make the density setting in build.prop (currently at 300). Is there another config file that controls the minimum value somewhere?
Thanks
Click to expand...
Click to collapse
Have you tried to control it via developer settings> smallest width if that settings appears in your x4?
You may have to undo that build.prop however.
Broadcasted from Zeta Reticuli
Wow you are a genius! I was way over complicating this one. Thank you. That did it, I never new that was thing. Hopefully someone as silly as myself will see this and not go down the path I did.
Gravemind2015 said:
Have you tried to control it via developer settings> smallest width if that settings appears in your x4?
You may have to undo that build.prop however.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Related
Hello everyone!
I just rolled back to Official GB V20S (Finland) and i was wondering if there's mod or something which allows user to change UI scale like in Pdroid ICS/JB rom.
GB scale is so "large" and if possible i would like to know how i can change UI scale in whole setup.
Thanks in advance!
You can't get tablet mode on gingerbread but you can change the pixel density. Edit the line in /system/build.prop ro.sf.lcd_density= 240 to ro.sf.lcd_density= 161 experiment with the values to get the desired results.
And oh, don't forget to reboot and clear cache! Also clear the data of market.
C0D3N1N3R said:
You can't get tablet mode on gingerbread but you can change the pixel density. Edit the line in /system/build.prop ro.sf.lcd_density= 240 to ro.sf.lcd_density= 161 experiment with the values to get the desired results.
And oh, don't forget to reboot and clear cache! Also clear the data of market.
Click to expand...
Click to collapse
Well thank you for fast respond. Do i use Terminal to do this change or i just go to the file location and "it can be changed from there"?
Edit: Ok i think i got it now. btw how i clear market cache? from google play settings?
Yes, my bad I meant google play cache!
I really loved on my 10" tablet Swype layout, with the keyboard off to one side, you can type with one hand easily.
But the full stretched layout sucks, you either have to use two hands or you have to reach far across, the screen - it is very inefficient and annoying.
Here is the tablet mode UI for Swype:
s19.postimg.org/np4crxxmb/tablet_mode_1.jpg
s19.postimg.org/kwb57wx9v/tablet_mode_2.jpg
I found some code around online, and I tried it (but it didn't work).
First I had tried using the File Manager,
but now I realize I really had to use root explorer, because the data folder in file manager is not the same data folder as in root explorer, which is why it didn't work the first time.
So I tried making a local.prop file containing the code qemu.sf.lcd_density=160 and putting in the data folder using root explorer,
...but it didn't work. Swype still did not have the tablet option.
I noticed in system/build.prop file, that there was this line:
Code:
ro.sf.lcd_density=213
I also noticed that there was no "qemu" prefix, but instead everything in the build.prop file has an "ro" prefix.
So I tried adding the line:
Code:
ro.sf.lcd_density=160
to the file data/local.prop ...
FAIL.
Then I tried modifying build.prop directly and changing the 213 that I saw in there, to 160.
(now the line in system/build.prop says this: ro.sf.lcd_density=160
rebooting...
SUCCESS!! AT LAST!!
So I wanted to isolate exactly what was causing the issue...
My guess is that local.prop is not doing anything, so I deleted it to see if Swype is still in tablet mode.
SUCCESS!!!
✓ CONCLUSION:
Open Root Explorer
Open the folder named "system"
Find line: xx.sf.lcd_density=###
a. Where xx = the prefix (in my case ro; in your case maybe qemu or something else),
b. And where ### is any number
c. Change ### to 160
If no line exists containing .sf.lcd_density=, then create it, as follows:
a. xx.sf.lcd_density=160
b. Where xx is the same prefix as the rest of the lines in the file (in my case the prefix is ro).
c. Example: In my case, the full line is: ro.sf.lcd_density=160
NOTE:
Changing the tablet DPI settings in Paranoid Android settings, did not affect whether or not the tablet mode showed in Swype.
HOWEVER, the Swype buttons looked better with I gave it 160 DPI. (if I used 213 DPI for applications then the keys were narrow and tall in tablet mode).
MY SPECS FOR REFERENCE:
DEVICE: Nexus 7 (v1)
ANDROID VERSION: 4.2.1
KERNAL VERSION: 3.1.10-g22b4fcd
ROM: ParanoidAndroid 2.99 build pa_grouper-userdebug 4.2.1 JOP40D eng.agascoig.20130114.131633 test-keys
SWYPE VERSION (BETA): 1.4.9.13905 (latest beta version as of 08-08-2013)
in other word you just enabled system wide tablet ui that everyone has done for over a year now.
dilldoe said:
in other word you just enabled system wide tablet ui that everyone has done for over a year now.
Click to expand...
Click to collapse
Well obviously not everyone has done this.
You should have bought the full version when it was 99¢. After using the beta for years I was happy to pay for it.
Sent from my Nexus 7 using Tapatalk 4
It doesn't put the navbar as one on the bottom though. It only makes the navbar smaller and enables dual panel.
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
psm510 said:
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
Click to expand...
Click to collapse
Good work. Been seeing people trying to do this. hopefully you found the correct fix. Thanks for letting the community know.:thumbup:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Druss81 said:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Click to expand...
Click to collapse
You would change SystemUI, that changes the notification bar/panel as well though among other things and makes having your dpi lower pretty much pointless in my opinion.
Sent from my SM-G900A using Tapatalk
Hello. I just upgraded to dev preview 3. And i wanted to ask if we can reduce the display size lower than the smallest offered in settings. And if there is any option in developer settings to do that. There is a setting under drawing tab with smallest width currently with value 484 dp. Thanks
Edit: it works. Successfully changed display size. It says custom in display settings now.
akholicc said:
...And if there is any option in developer settings to do that. There is a setting under drawing tab with smallest width currently with value 484 dp. Thanks
Click to expand...
Click to collapse
When rooted:
Terminal emulator: su -> wm density 384, or
Build.prop editor: value of 'lcd_density'.
In M the value 384 switched the N6 in tablet mode. The settings menu appears with 2 columns.
In Android N that doesn't happen. For me there is no need to set a lower dpi-value.
There is this menu under drawing in developer settings i am talking about. Can we change this to get custom display size? See attachment
akholicc said:
There is this menu under drawing in developer settings i am talking about. Can we change this to get custom display size? See attachment
Click to expand...
Click to collapse
I use a lite Stock rom on my N6 and do not have that item.
But I don't think you can change the DPI value in the dev.menu.
You need to edit the build.prop file or use a a terminal command. And root access is needed.
NLBeev said:
I use a lite Stock rom on my N6 and do not have that item.
But I don't think you can change the DPI value in the dev.menu.
You need to edit the build.prop file or use a a terminal command. And root access is needed.
Click to expand...
Click to collapse
Yes we can. And this option is available to me on N preview 3. And i can change my DPI by changing it. No root or editing build prop required. Its super easy. I have set that option to 595 and in display settings my display size shows as 387. So, we can set custom DPI by changing that value.
akholicc said:
Yes we can. And this option is available to me on N preview 3. And i can change my DPI by changing it. No root or editing build prop required. Its super easy. I have set that option to 595 and in display serrings my display size sgiws as 387. So, we can set custom DPI by changing that value.
Click to expand...
Click to collapse
Not flashed P3 yet. Thx for the good news.
Dear helpful XDA-devs,
I ran into some weird display bugs which I did not experienced before. I've had the N5 and other phones and did often change my dpi without any side effect. However when I did it with my new Nexus 6 now I discovered some icons in the Play Store and "Locus Maps", for example, being oversized (see attachments).
What I did was to try to change my DPI using "Texdroider DPI" which let to an instant bootloop. So I reflashed /system from the stock image. Then I used the Nexus Root Toolkit to change the dpi via adb, what I thought worked perfectly back then (I changed it from default 560 to 530 in the end but tried a few other values as well). However, now I discovered these weird display issues in these two and one or two other apps. Any ideas what might be the reason, if it is DPI related at all, or if it worked fine when you did it yourself? Changing it back to default now does not solve the issue for me now, of course.
I'm on MOB30I, by the way. And I use TWRP+SuperSU on it. I did allow TWRP to make the /system partition writable to prevent Android from replacing TWRP. Might that be a reason why the adb-DPI-change let to bugs? Thanks for the help! :good:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
zelendel said:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
Click to expand...
Click to collapse
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
karlo12 said:
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
Click to expand...
Click to collapse
No not completely. That maybe your best bet. Also could try deleting the cache files.
You need to also change the dpi in build.prop, or you'll get those large icons.
Or if you want to go back to the old dpi, just do what you did in NRT, but change it to 560 this time.
change it in your build.prop file, then reboot for it to take affect. anyways, you will probably see other bugs with the dpi changed properly(but maybe not).