I have a rooted Huawei Mediapad T5, running stock ROM. But 1 reason why I had rooted it, was because of it's annoying resolution. Everything is way too big which causes too much screen space to be filled.
I searched XDA and google to solve this problem. But everytime I boot, the tablet is back to it's orriginal screensetting.
I've found out that lowering the DPI works in my case. It seems to be set at 320 orriginally? At least this is the info I get from terminal and ADB commands. Other apps like CPU-Z tell me 255.
Well, let's say it's 320.Then lowering it to 280 or 300 makes a big diffrence for me and everything looks way better arranged on the screen. But again, after boot it changes back to 320...
Things I've tried (with no luck ofcourse):
- Changing dpi using my tab connected to my laptop using ADB (DPI settings get applied, but are gone after reboot).
- Changing dpi using a terminal-app on the tab itself (DPI settings get applied, but are gone after reboot).
- There was no "ro.sf.lcd_density=" in build.prop. So I added it and rebooted. But no change after reboot.
- I've tried some (root) apps from the app-store, for changing DPI-settings (DPI settings get applied, but are gone after reboot).
When I change DPI with the Terminal, and check display settings first. then it shows me the standard DPI settings of 320. When I use this same terminal to change DPI to 300, then it gives me 2 lines after checking again.
Physical density: 320
Override density: 300
So I was thinking, maybe I should look for a way to change this "Physical density" vallue to trick keeping it like this?
-------------------------------------------------------------------------------------------------------------------------
Edit:
I think something is off with my screenresolution.
Information in the terminal gives me: Physical size 1200x1920
Websites detect it as 960x600
and the physical dimentions are:
width 21,6 cm
height 13,5cm
diagonal 25,5 cm
-------------------------------------------------------------------------------------------------------------------------
Edit 2:
I've found that other tabs with similar screen size and aspect ratio have an resolution of 800x1280.
Tried to change this. And this setting is still saved after rebooting. But the screen looks way to big now.
What happens when you in build.prop make DPI setting persistent?
Code:
persist.ro.sf.lcd_density
jwoegerbauer said:
What happens when you in build.prop make DPI setting persistent?
Code:
persist.ro.sf.lcd_density
Click to expand...
Click to collapse
Should I add this line in build.prop?
Related
Ok... I am using LCD Density Changer to go from the standard size of 240 to 182 that part works great.
So to the question.. Is there a way to make this change with effecting the sound of the phone. When I make the change and the phone restarts I have no sound. I am not sure if I save it to default if I will have sound. Can anyone help with this.
I have this problem too. I can't change the density because when I do the temp/preview it reboots without sound. If I click save and then I reboot, it doesn't save the density.
edit: changed the build.prop manually and it works fine.
Hey guys I have been playing around with the Gingerbread leaks for the O3D and I am loving it so far, but I only have one problem with GB at this stage.
The problem being if I set the LCD Density to 167 (Got used to it on all my Android devices) the Rom only works until it locks. Once it locks the first time after the setup it goes into a boot loop and the only way to restore that would be to flash a ROM with lcd_density set to 240. Then the Rom works perfectly without any issues.
I have noticed that no LCD Density changer app works on the O3D, Ive used a few for different devices and they all worked. I have also seen that there are 2 entries for lcd_density in build.prop. Removing either changes nothing. Changing them both breaks the phone too.
Would there be anyone wise enough to be able to get this done, make the LCD desity either changeable or 167?
Edit : If I set the density lower in 20 increments with font changer (root) then i get it down to 200 before causing bootloops. I dont understand why, it worked fine in Froyo
I appreciate the help.
I cant believe everyone with an optimus 3D runs it at 240 LCD density...
Is there anyone that could help with this?
I have the same problem but didn't bother to ask since i don't think there is a solution until we get the official release.
I tried 160 with my TV and got the perfect resolution. But as you say, as soon as i reboot my phone i get into a boot loop.
I think that the only thing we can do at the moment is to restore the density to 240 if we reboot the phone and put it back to 160 or whatever when it has booted up again.
This is my problem:
I set the density to something below 240, then my phone gets stuck in a bootloop, so I enter CWM and make a factory reset, then i can get in to the phone with the new density. The phone works great until i reboot my phone which will get my phone in a bootloop. This time, the factory reset wont work. So i have to restore the system partition and start from the top.
As you say, it worked fine in froyo for me as well.
EDIT:
I will take a look at build.prop and manually change the settings.
Okay I found the problem and a solution.
I created a new thread so the discussion about the supported densities can be held there separately.
http://forum.xda-developers.com/showthread.php?t=1351420
Hi,
I've recently installed CM9 (stable) on my SGS2 i9100. All was good.
Then, all of a sudden, I got a "unfortunately, com.android.phone needs to close"-error whenever I tried to make a call. I've searched XDA and tried all suggestions listed (clearing data of phone, contacts storage, google services; wiping cache) without success. I subsequently changed my display density back to the original 240 DPI (from the 180 DPI that I've come to love) and the error was gone.
Lowering my DPI to 180 causes the error to re-appear.
I've used two different apps to change the DPI: "LCD Density Modder", and "resolution change / Density", ("LCD Density" doesn't seem to do anything) both with that same problem.
I really like the ability to make phone calls, yet I also like the high resolution and smaller text a lower DPI provides.
so:
- why does lowering the DPI cause that error?
- what alternative to above mentioned apps do I have in lowering my DPI?
- any other suggestions?
any help is greatly appreciated.
Hi, I haven't been able to find much information about it so... I am trying to run a game - FF IV - in full screen on my Nexus 5. Usually it runs with the soft keys on the edge, but I can get rid of them by forcing immersive mode, however the game remains the same width but is pillarboxed. I have seen videos and images of this game running on other android devices and can confirm it can run in true 16:9 so I am trying to work out a way to do that.
Is there some way to trick the app into thinking the phone has hardware keys? Or to change the default resolution of the app?
Any help would be appreciated if you know anything about thus, or even something similar to this.
Thanks!
DRL
Edit: I am using the Xposed module app settings to force immersive mode for this app(I have also tried universal immersive mode) and have experimented with the DPI settings as well, but with no success. Will keep thread updated as I try new things.
Edit 2: Well, just checked out build.prop, nothing that seemed promising other than the DPI is 480... will keep searching.
My app GMD AHSK (root) will turn on hardware buttons setting. Other than some advanced setting it is free to use:
https://play.google.com/store/apps/details?id=com.gmd.hidesoftkeys
I don't know if it will help with FF form factor.
Thanks for the reply! The app is able to hide the soft keys but the game still refuses to remove the black bars... I am wondering if it is some profile based on phone model? Well at least we know it's not a hard key issue.
qemu.hw.mainkeys in build.prop determines whether the device has hardware keys or not, 0 means it doesn't and 1 means it does.
You can add qemu.hw.mainkeys=1 to the end of build.prop to disable soft keys however you'll have to reboot and its not practical to do just for one app lol.
Thought I'd test it anyway to see if it worked... 3 reboots later and I'm still getting the black bars! I'm starting to suspect the images may have been stretched slightly... I might test on bluestacks or AVD tomorrow. *sigh* This is bugging me more then it should
Changed pmy DPI to 160 as per this post: http://forum.xda-developers.com/showpost.php?p=48859146&postcount=84
However, while everything on my phone is now tiny FF IV still has black bars.
On a hunch I disabled immersive mode on the game, as in tablet mode the soft keys are down the bottom of the screen in landscape mode.
What happened was that the game resized to have larger black bars(maintaining its original form factor) due to the loss of vertical resolution due to the soft keys.
So it appears the game's resolution is set, perhaps it's only the iPhone 5 version that's 16:9? I'm going to switch back the DPI now, before the tiny text destroys my eyes. If anyone else has any ideas, let me know.
I just stop using navbar and use Pie instead
I noticed that by default console mode output is set to 1080P, however since I have a quite old LCD TV I would like to change it to 780 (HD Ready) but it seems there is no way to change this through settings.
Does anyone had the same problem?
Do you think there is a possible solution?
Thanks
Degghi said:
I noticed that by default console mode output is set to 1080P, however since I have a quite old LCD TV I would like to change it to 780 (HD Ready) but it seems there is no way to change this through settings.
Does anyone had the same problem?
Do you think there is a possible solution?
Thanks
Click to expand...
Click to collapse
I have the same problem. I can connect the tablet to computer monitor and it works, but when I connect it to TV there is no signal (although cable connection is detected). Maybe there is some app that allows to change HDMI resolution?
nVidia really needs to release an OTA update with the ability to control the HDMI output resolution easily from the native ROM....
Has anyone been able to set a custom resolution, for XBMC for example, without loading a custom ROM?
If you are using a ROM, which one are you using?
You must be rooted but try this in a terminal window on the device (terminal emulator should work fine)
Code:
su
wm density 160
wm size 1280x720
or
Code:
su
wm density 160
wm size 1280x800
to reset it
Code:
su
wm density reset
wm size reset
sbdags said:
You must be rooted but try this in a terminal window on the device (terminal emulator should work fine)
Code:
su
wm density 160
wm size 1280x720
or
Code:
su
wm density 160
wm size 1280x800
to reset it
Code:
su
wm density reset
wm size reset
Click to expand...
Click to collapse
Unfortunately this does not work. Tablet resolution does change, but HDMI signal remains unchanged.
qrees said:
Unfortunately this does not work. Tablet resolution does change, but HDMI signal remains unchanged.
Click to expand...
Click to collapse
Then I can't help
Ok, In my case it was actually a cable problem. It seems to work now.
On the other hand I still don't know if changing the resolution does change anything about HDMI output.