I'm confusing myself I think. I have my DPI set at 133 and now I'm having incompatibility issues with the market. I know this isn't a new problem and I know its been discussed before. But info is scattered and nothing I set DPI at fixes the issue. I've tried 160 and a million others but no success. The thing is my DPI was always set at 133 and I have downloaded apps that now say are incompatible. Can anyone help me straighten this out?
Change the dpi back to 160 with :
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en
Open up Rom tool box lite , select :
Performance >build.prop.tweaks>LCD density> set to 160.
APPLY and reboot.
Yeah see. This is why I'm confused. I have that app and that's how I've been changing the DPI. It will change the DPI but won't fix market incompatibility.
Edit: This is going to get annoying really quick lol. I got the apps I needed to download by changing DPI to 320. Now set back to 133 and all is good. Sort of.
Related
halo
i don't see so well and the Resolution in the one s is to high to me
i raise the DPI Through rom toolbox to 260
but i get some error of the system ui "Unfortunately system UI has stopped"
for example when i enter to "recent up" i got this erorr and i can't enter there....
there is a way to fix it ??
thanks
If I'm not totally wrong raising the resolution will result in smaller letters. You should lower it instead. So please try it.
And you can change letter size within settings -> display & gestures -> font size. By default it is medium, so you can change to large or extra large.
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
rootrider said:
At least under accessibility there is an option named TalkBack, which will activate a spoken feedback to what you touch, choose or activate. I hope your ability to see is not that bad!
Click to expand...
Click to collapse
I just checked that out.
What's with the notification about it "collecting" info? Collecting it where? And what? I didn't go any futher.....
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Haven't tried it on this phone, but at least on every sense Rom I've used for the hero changing LCD density has always messed up everything. One of the reasons I allways used aosp
Sent from my HTC One S using XDA
usrbrv8 said:
Tomney,
I am not sure if this will actually work but if you have root you can edit your build.prop file. In that file there is a line that refers to ro.sf.lcd_density. By adjusting that number up or down you can change the dpi of the screen. Now that does not necessarily mean that all of your apps or even the Sense UI will work correctly, but it might be worth a try.
If you want to easily do this I would download the BuildProp Editor app from the market.
Click to expand...
Click to collapse
as i said i did it with romtoolbox. it is the same , i raise the dpi to 260....
it makes some problems with system ui and i got some errors
i now replace the rom to miui and the dpi change doesn't Affects the system ui
dpi change can be on a rom without htc sense ui and i think even regular ice !
but..... now there is some problem with the market because Resolution Compatibility i think... there is some app i can't download .....
for now i need to come back to 240 dpi for download some apps and its Annoying
maybe if could change the Resolution to Exactly 800\480 i wouldn't get the market-app-Compatibility issue but i dont know how... maybe someone know how to do it?
my vision isn't so bad and i know the regular options aka font enlarger Etc ...
dpi change is the best choice for me .
Double whammy question. Is there any way to enable hold back button to kill current app on any rom? I know that it's on most AOSP roms and Viper rom but I'm running King Cobra and miss it coming from AOKP. I would just use viper rom as it's the better rom between the two imo but currently changing the dpi causes system ui to fc and I need my 200 dpi, 320 seems huge and ridiculously wasteful after being on 200 for so long. On Viper it's 320 or nothing, no 241,240,200 or 192 (tablet mode) just 320. I usually just use root explorer and edit the build prop but that kills system ui. Unfortunately so does the app "lcd modifier pro" I know they all essentially do the exact same thing but maybe there's an app out there unbeknownst to me that tricks the system into thinking the density has been unchanged while actually allowing you to change the resolution. Any feedback is appreciated.
Tell me whether it is possible to make a tablet mode with a density of 160 CM10, I know that you can set the DPI 133 and will be a tablet but then a lot of software in Google Play write "Not Available on your device .." (put firmware from AOKP in there you can select the tablet mode CM .. but I like more =)
Not without modifying the source and building it yourself.
imnuts said:
Not without modifying the source and building it yourself.
Click to expand...
Click to collapse
Ok, then how to solve the problem with Google Play .. at 133 many applications write "Not Available on this device" ...
Because Google Play does not support the 133dpi. It will likely only work at a dpi setting of 120 (maybe), 160, 240, and 320.
imnuts said:
Because Google Play does not support the 133dpi. It will likely only work at a dpi setting of 120 (maybe), 160, 240, and 320.
Click to expand...
Click to collapse
and CM10 is scheduled to tablet mode for table 2? as in the firmware of the AOPK .. very unusual in phone mode ..
Are there any TW roms that work well with LCD density set at 240? Specially the dialer. Thanks
You can try Galaxy Mod, http://forum.xda-developers.com/showthread.php?t=1953008
--------------------------------------
Multi-DPI support
--------------------------------------
This ROM has been modified to support different DPI settings, however don't expect it to be at the level of Paranoid Android. I still have yet to figure out per-app DPI, but as of right now you should not get any force closes or unexpected behavior when changing the DPI. There may be graphical glitches. Be careful, in my testing the phone would NOT boot with a DPI lower than 165. To be safe, I would suggest using a DPI of 180-220 if you plan on changing it. Make sure you do not set the DPI above the max which is 320. Doing so would result in a non-booting device.
To change the DPI open the build.prop using an app like Build.prop Editor and edit the following:
Code:
ro.sf.lcd_density=320
Change "320" to whatever value you want, but be careful. Reboot the device when you have made the changes.
Do not post a bug report if you changed the DPI. Some apps may not work with well with a DPI lower than 320.
Click to expand...
Click to collapse
So Yesterday I Was Testing An Oreo ROM On My Onyx.
Since The Display Size Was Odd. So I Decided To Change The DPI to 400 But Accidentally Changed It To 4000.
Now My Screen Going On And Off & system UI getting crashed too.
Just Being Curious That Where Are Those DPI Values Stored ? build.prop Doesn't Have Those Values Though
Any Solutions Or Clean Flash ?
Kewal9821 said:
So Yesterday I Was Testing An Oreo ROM On My Onyx.
Since The Display Size Was Odd. So I Decided To Change The DPI to 400 But Accidentally Changed It To 4000.
Now My Screen Going On And Off & system UI getting crashed too.
Just Being Curious That Where Are Those DPI Values Stored ? build.prop Doesn't Have Those Values Though
Any Solutions Or Clean Flash ?
Click to expand...
Click to collapse
Solved By Fetching The Developers Setting xml file and push it back to system using ADB.