I have my DPI Set to 450 as minimum yet every time I reboot it seems to revert back to 423.
Is there a adb shell command that can change this permanently without root?
Just out of interest maybe there's something that can be done with adb about the annoying auto brightness setting up with every reboot.
ADB shell wm density 450 && ADB reboot ... This doesn't make it permanent it reboots to 423 again.
Have you tried settings database editor?
I looked and can see several reference to dpi.
On my device the string values are set to 480.
zolaisugly said:
Have you tried settings database editor?
I looked and can see several reference to dpi.
On my device the string values are set to 480.
Click to expand...
Click to collapse
There's no way to set in this app, nothing in the table and Android settings are not editable I tried setting up the auto brightness with different values but when i reboot it reverts back and nothing is changed.
Darkat70 said:
I have my DPI Set to 450 as minimum yet every time I reboot it seems to revert back to 423.
Is there a adb shell command that can change this permanently without root?
Just out of interest maybe there's something that can be done with adb about the annoying auto brightness setting up with every reboot.
Click to expand...
Click to collapse
I wonder, does the value you set matter much? For example, does it matter if I enter 384 or 376 as dpi? Must the dpi you select, be able to be devided by a certain number or such? I want the dpi to be somewhere between 375 and 385.
Sorry for the noob question, but. What's DPI for? I mean, I've noticed it changes the way things look on the screen, but other than that?
Related
I'm using LCD density changer and have ticked the save as system density-box. Despite this, the correct density doesn't load on boot. Any ideas on what might be the problem? Using 200 as saved value.
Rooted KE2 kernel with GINGERBREAD.XWKE1 build.
Sent from my disappointing GT - I9100
load lcD density, click bottom left menu to see settings page, choose "default density" and set it in there, then apply this same density in the main page, it should now keep it.
I stopped using this though as it causes camera problems and dialler and other progs dont fit on screen properly, I am hoping this is going to fixed in a cooked ROM, I'd leave it until then dude.
Thanks for the reply but selecting default density only fills in 240 in the number box. It's not a new menu or anything. I've tried reapplying the density several times and even Superuser says the app is granted access and then I get a window that says it's saved and will automatically load on boot.
Still, it doesn't work.
Sent from my disappointing GT - I9100
Probably worth asking the developer of the APP.
I've found some apps that set LCD density to be a little flaky too.
I just use Root Explorer now and manually edit the build.prop file, which is very simple. If you want to know how to do that then let us know.
Nitrality
Use Nitrality, it is working great! I also recommand a 200 dpi value.
So the thing that's bugging me like crazy right now is that even though I deleted the LCD density line in build.prop, my tablet defaulted to 220 DPI after reboot.
Also, I don't know if this is a bug with Chrome or my tablet, but ever since I messed with DPI a while ago, I've been getting the button that displays the number of tabs next to the address bar. This button is only for phones and devices that don't show the tab bar on top, and pressing it does nothing.
So two questions:
1) Is there some other file somewhere that stores the default DPI to go back to when there's no LCD density line in build.prop?
2) Is anyone else seeing the tabs button in Chrome? Is this a DPI problem or a Chrome problem?
Why did you delete it??? If you want to change it, change the number. Deleting it will do nothing. Just add it back to where it was
Code:
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
ro.opengles.version=196609
[B]ro.sf.lcd_density=320[/B]
ro.hwui.texture_cache_size=72
2) Not seeing it, your DPI is probably not what you think it is currently. The default DPI is 320
Hello everyone, I hope you guys can help me solve this issue
I change my Z2 DPI to 360, everything is fine except Incoming call interface when I get a call, the swipe to answer bar and the button don't fit the screen, I tried to use Per App settings module of Xposed but useless, can someone give me a solution to make these things fit the screen , thanks in advance!
thode1226 said:
Hello everyone, I hope you guys can help me solve this issue
I change my Z2 DPI to 360, everything is fine except Incoming call interface when I get a call, the swipe to answer bar and the button don't fit the screen, I tried to use Per App settings module of Xposed but useless, can someone give me a solution to make these things fit the screen , thanks in advance!
Click to expand...
Click to collapse
that should be an easy one with tasker, executing 'wm density xxx' whenever call comes in
(xxx stands for numeric dpi value)
and exit with 'wm density 360' when call ends
bgumble said:
that should be an easy one with tasker, executing 'wm density xxx' whenever call comes in
(xxx stands for numeric dpi value)
and exit with 'wm density 360' when call ends
Click to expand...
Click to collapse
Thank you for give me an idea but can you show me detail about the procedure to set that with tasker ?, I got the app but I don't know how to make a task as you said
thode1226 said:
Thank you for give me an idea but can you show me detail about the procedure to set that with tasker ?, I got the app but I don't know how to make a task as you said
Click to expand...
Click to collapse
On profile add App, select Phone, new task (name it), add shell, enter command 'wm density 424' (without quotes), add exit task (name it), add shell, enter command 'wm density 360'
Not exactly, but you'll figure it out.
Give feedback :good:
bgumble said:
On profile add App, select Phone, new task (name it), add shell, enter command 'wm density 424' (without quotes), add exit task (name it), add shell, enter command 'wm density 360'
Not exactly, but you'll figure it out.
Give feedback :good:
Click to expand...
Click to collapse
I've try as you said but when a call comes in, the screen still like above , i tried to check all service involved to phone, but nothing changes.
thode1226 said:
I've try as you said but when a call comes in, the screen still like above , i tried to check all service involved to phone, but nothing changes.
Click to expand...
Click to collapse
you may execute the script as root user.
Other than this I have no idea.
I've already execute the shell with root user, but I think the problem here is "Phone" app is incorrect, it must be another app, but anyway, thanks for your help
Not exactly what you want, but if you use 320dpi instead all apps works fine and adapt perfectly to the screen size.
Maybe try it and see if you like how it looks.
On profile add Status, select Calls (both incoming and outgoing), new task (name it), add shell, enter command 'wm density 424' (without quotes), add exit task (name it), add shell, enter command 'wm density 360'
Thanks to both of you, I decided come back to stock dpi and set specific app I want to 320dpi, that makes me breath easily
I am late to the Dell Venue 8 7840 party as I just bought mine three days ago. What a beautiful tablet and absolutely gorgeous display. However, I think that the text is just a little too small for my likings so I wanted to do something about it. Well, you first have to root your device which is kind of a nightmare if you ask me (after updating to Lollipop 5.1).
My first attempt at changing the resolution was through editing the build.prop and adding a value of "ro.sf.lcd_density=360" since the default density is 320. Anyways, every time you reboot it just is completely ignored.
I take no blame for anything that goes wrong with this.
So here's how you change the DPI:
1) Get root by following this most recent root tutorial. You will need to install "Busy-Box" as mentioned in that tutorial.
2) Install a terminal emulator such as "Terminal Emulator" or "Termux" from the Play Store
3) Start the terminal program
4) Type "su" and press enter. NOTE: You will need to grant your terminal emulator root access after you press enter.
5) Type "wm density" and press enter. You will see the default density of "320".
6) Type "wm density xxx" where xxx is the density you want to switch to such as 360. Basically anything above 320 is larger, anything below 320 is smaller.
Once you type the command such as "wm density 360" it instantly applies it. It also survives a reboot so please be careful to type the command exactly as it is supposed to be typed and do not use too small or too large of a change. If you change the density to 390 and utilize Google Now you will see that it changes format from a dual column to a single column. I prefer this look and feel plus tabs in Chrome are more normal sized to myself. Some DPI's cause text to shift off the sides of the display so it's just a matter of trying to increment or decrement by one until you reach the sweet spot.
If you want to reset it back to normal you can simply type "wm density reset".
Good luck and hopefully this helps someone.
Awesome. Looks a tad bigger but still sharp. So that's a plus.
Quick question. Do you know how to swap the menu and back soft keys? I tried switching with the..kl files and no luck.
joeminati said:
Awesome. Looks a tad bigger but still sharp. So that's a plus.
Quick question. Do you know how to swap the menu and back soft keys? I tried switching with the..kl files and no luck.
Click to expand...
Click to collapse
I haven't looked into this myself and couldn't be of any help. I'm use to the positioning and never tried to swap them on my own.
With other high-res tablets such as the Samsung Tab Pro it is much easier to do this with one of the many apps available on the Play Store. However Texdroider and some of the others do not work; the change is not applied on reboots. By trial and error I stumbled upon Easy DPI changer, which works perfectly. It is probably applying the same change "automatically" that the op applied manually.
Any ideas?
I have "smallest width" in Developer Options set to 500. Tinkering with ADB, I have found that this is equivalent to 345dpi. You can actually change the "smallest width" in real time by changing DPI in ADB and they have an inverse relationship - as dpi goes up, smallest width goes down.
There is no way to make either change persist on reboot on an unrooted device.
However it seems to me that since there is no root required to set "smallest width" there should be some way to run a script or do something to change the smallest width setting in developer options on each boot up. It doesn't matter if it happens late in the booting process.
I would just about have my device exactly how I want it if I didn't have to go into developer options and reset the dpi on each reboot!
Any suggestions?
I'm not rooted and the setting stay for me in developer options. My android TV is the same. I changed the dpi setting of that, and that stay after a reboot and that's not rooted either. Although the the TV settings were changed via adb rather than in developer options.
Thanks... well, I wish I knew why the setting change won't stick on my phone. It's not the biggest deal in the world and I don't reboot much (except lately to test hosts files and finally get spotify working properly with ad blocking.)
Since you said it works for you, I have had another few goes at it, and it definitely doesn't stick on my Mate Pro 10.
I have done it two ways - via ADB with:
Code:
adb shell wm density 345 && adb reboot
and in Developer Options, setting Smallest Width to 500.
Also tried different values for both. It never survives a reboot. Oh well.
anthropoidape said:
Thanks... well, I wish I knew why the setting change won't stick on my phone. It's not the biggest deal in the world and I don't reboot much (except lately to test hosts files and finally get spotify working properly with ad blocking.)
Since you said it works for you, I have had another few goes at it, and it definitely doesn't stick on my Mate Pro 10.
Click to expand...
Click to collapse
It does not stick on my Mate 10 either...
is there any solution? Maybe an app to restore the setting on each reboot?