Is there any way beside to reboot with the standard density ti fix the no supported device issue in markte with low density?
audino said:
Is there any way beside to reboot with the standard density ti fix the no supported device issue in markte with low density?
Click to expand...
Click to collapse
No - the market checks it and it only takes effect at startup.
is there any risk that i may not see some apps if i use 160 in dpi or is it just as compatible as 240?
Related
I have a Dell Streak 5, but I bought a Galaxy S II last night. I realize the screen is a bit smaller, but I find the resolution or density extremely poor...I like a lot more on my screen, and it seems everything is too large. It's a show stopper for me. Is there anything I can do to change this before I return back to the Streak?
There isn't really a viable software fix for this, so just return the phone and get a Galaxy Note (1280 x 720 at 280 something PPI, 5.3inch screen).
1. Get your device rooted
2. Download "LCD Resolution" from Market.
The lower the number, the higher the resolution.
NOTE: Apps may not be fully optimized for this kind of resolution such as Phone, where the keypad is smaller than the screen. Market works with this DPI modification.
Also click on "Always Set On Boot" in the app so that it would automatically adjust your desired Density at boot.
Im making a tablet rom for the ray and i have faced one problem, if i lower the screen density in the build.prop to 160(like a tablet) when i call someone or get a call the phone says the process com.android.phone has stopped.
i thought maybe i can change the phone.apk to a tablets one and then which one?
Thank you for the help.
Why not use screen density 240?
When you lower the pixel density more things fit in screen with the modding i did to the framework-res in 240 not everything fits the screen for example the lock screen.
The Ray has a small screen, why do you want to make it smaller?
I doubt that what you are doing has any practical usage.
Hi - Easy DPI Changer app... Good rating in Android store, very few reports of it bricking phones, but I have a very important, but basic question:
Is it possible to set the resolution DPI too high or too low, making the phone unusable?
For example, if I set the DPI to 1 might the phone become impossible to use because the buttons appear off the screen?
Supposing I set it to 1000? Might the phone crash and boot loop before being able to set it back to a safe DPI?
I'm not looking to set crazy DPIs and brick my phone, but I just don't know what sensible DPIs are!
Any thoughts appreciated, Ta!
So i changed my dpi to 540 and deleted the mini clock app to avoid fc and everything looks great and runs fine except my primary display is cutting into the secondary and secondary display notifications are slightly cut off.I've changed the dpi of the secondary display back to 640 through appsettings but the problem still remains.
Any ideas?
jass65 said:
So i changed my dpi to 540 and deleted the mini clock app to avoid fc and everything looks great and runs fine except my primary display is cutting into the secondary and secondary display notifications are slightly cut off.I've changed the dpi of the secondary display back to 640 through appsettings but the problem still remains.
Any ideas?
Click to expand...
Click to collapse
Reboot your phone
I changed the digitizer and display in my phone. The digitizer seems to think its resolution is larger (1080x1920) than the real display resolution (720x1280), so my touch is misplaced. I know how to change the display (physical) resolution using wm size, but that scales the digitizer resolution proportionally.
How do I change the digitizer resolution?
Output of dumpsys SurfaceFlinger: pastebin.com/gXnfxJKv
Output of dumpsys display: pastebin.com/bwkjXHxH
(The phone is Lenovo A7000, but that shouldn't matter. The error persists after upgrading firmware, rebooting etc. I haven't flashed/rooted - yet.)
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
ramiabouzahra said:
After using adb shell wm size ----x---, did you try adb shell wm density ---? Density is basically the dpi of which the device will utilise
Good luck.
Click to expand...
Click to collapse
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Xellos0 said:
Thanks, but yeah, I tried and it doesn't affect the digitizer resolution either, none of the wm options do anything worthwhile.
It seems I need something like a way to change sizes of SurfaceFlinger layers.
Click to expand...
Click to collapse
SurfaceFlinger is integrated into the GPU if I am correct, so good luck with changed that
Other than that, at the time of writing, I can't come up with a solution.
Wish you best of luck
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
OJKLLC said:
Just going to add that I have a similar yet different problem to you.
The similar part is I too also need means to change digitizer resolution but instead of going from 1080p(FHD) down to 720p(HD). My scenario needs to go from 1080p(HD) up to 2160p(UHD)
So I'm just adding more traffic in hopes people know of commands specific to the digitizer or a method to locate & modify files which report the device as only 1080p to most apps
See I've tried Shell/ABD commands but unlike most phones giving my phone a command to report itself as 4K to apps is creating an issue because seemingly even though the device knows it's 4K it reports to itself/apps as 1080p so my the digitizer is running itself as 1080p even though the hardware is sending a 4K signal to light the screen even if most times what's displayed is simply 400% 1080p
If anyone knows what files to get to (as well as how) I as well as OP can manually add the appropriate values to use the correct amount of our screens whilst utilizing the correct resolution, because like he said the PDI stuff isn't related to digitizer only display scale, we need digitizer scaling
Click to expand...
Click to collapse
& to clarify when in 4K all the time mode with the ABD/Shell command it's not like I can use the whole screen to touch but it'll scale that touch to 1960 by 1080, not the touch for my case is 100% accurate to where I place my finger, issue is that its only sampling 1960 by 1080 of the pixels aka just 1 corner so only useable quarter of the touchscreen with the other 75% completely dead