This question is directed to anyone who knows the inner workings of the vending.apk and the android market itself. Through another post about density settings, it seems pretty apparent that, while having density set at 161 allows all the apps in the market to show up, there are still plenty of apps that won't actually RUN unless you are set at 160/159. So it turns into a Catch 22 situation. I know I have used device spoofing via an altered build.prop (or an apk that does the same) for getting apps to appear that are 'proprietary' to other, specific devices, but I'm wondering if it MIGHT be possible to spoof the market into reading our Nooks at being 161 devices, while we are actually at 160 while within our rom (I'm on CM7). This has probably been proposed somewhere else, but I couldn't locate a thread...Anyone have any input about this possibility? If something like this is NOT possible, please let the users know also, if you have a minute. Thanks for looking...(Idea..could we get a secondary "market161" .apk created that we could use indepedently of the one in the latest Gapps to achieve the desired effect?)
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
My Density is set at 200 and everything works just fine (including both Market and Maps).
Mine is set at 240 (need new glasses?) and everything seems to be ok
Trust me...there are enough that don't run at 200....otherwise I wouldn't have bothered posting. 160 seems to be magic for compatibility/scaling, and 160+X gets best market access.
Sent from my PC36100
ganovim said:
Mine is set at 240 (need new glasses?) and everything seems to be ok
Click to expand...
Click to collapse
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
Thanks...this is exactly what kind of info I needed...new project...sigh..will give it a shot after work tonight...Thanks.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
mazook98 said:
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Click to expand...
Click to collapse
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
It would be SO on....
Sent from my Nook Color (zoom2) using Tapatalk
mazook98 said:
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
Click to expand...
Click to collapse
It's a pain sometimes, since everything is buried under submenus. I don't think there's anything else comparable, though.
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
dalingrin said:
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
Click to expand...
Click to collapse
Thanks so much for saving me from making this a bigger issue than it is...I don't need " my apps " to populate since I'm tethered to my Evo about 95% of the time, where they naturally all populate ...I'll just bump it down to 160 permanently, and if ever it becomes something I absolutely need, Ill just bump it back....Thanks for all your amazing work..Donation on the way when I get home from work.
Sent from my PC36100
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
john10101 said:
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
Click to expand...
Click to collapse
There are just some apps that wont run / scale correctly unless its at 160... they will just hang and load 4 ever or force close unless they are set at 1 of the 3 native densities for android application development... at least that's what I can glean.. no difference though in appearance, unless you're a cyborg.
Sent from my PC36100
oh this is why my app list wouldnt populate. it doesnt bother me most of the time. everyone seems to have their dpi set for so low. i have mine at 132.33 if i remember it right. can't be any bigger than 140 for sure.
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
pxldtz said:
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
Click to expand...
Click to collapse
Here's one...Try "Fruit Slice" at 161....then try it at others if you want...then run it at 160.
Sent from my PC36100
Related
Info from this thread originally - http://forum.xda-developers.com/showthread.php?t=760805
Since we are using larger screens google recommends we change our dpi from 240 to 160, this probably looks fine for stock builds but on sense builds everything looks crazy. I currently have mine(on a sense build) at 210 however feel free to change it to what is best for you.
to perform this modification
pull the build.prop from /system/build.prop
open the file using a text editor and change ro.sf.lcd_density=240 to ro.sf.lcd_density=160(or whatever number you choose)
then push the file back to /system/build.prob
(i used a paid app called root explorer for this process)
if you want you use terminal emulator or adb here are the commands:
su
cp /system/build.prop /sdcard
then once youve edited the file
cp /sdcard/build.prop /system
you can use the same commands over adb by entering adb shell
download the spare parts app from the market and untick the compatibility mode then reboot (this fixes the issues some apps have with scaling)
the result of this mod is more things fit on the screen e.g. lists and web pages and games like raging thunder 2 look better as they arent being stretched out as much.
i recommend for a sense build: 200 to 220
for a vanilla build 160-220
if anyone has any better numbers please post
SCREENSHOTS ON NEXT PAGE
TO MAKE USE OF THE EXTRA SPACE ON THE HOMESCREEN INSTALL ADW LAUNCHER AND SET THE COLUMNS AND ROWS TO 6X6 (SCREENSHOTS ON PAGE 6) , THE SAME CAN BE DONE FOR THE APP DRAW
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
I've tried 200, looks ok. I've always thought that we need to up the dpi, at 240 its way too huge for our screen.
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Is there a way to do it without Root Explorer?
FreakyFerret said:
Is there a way to do it without Root Explorer?
Click to expand...
Click to collapse
Go to your windows mobile, then edit the same file from the same folder of the Android. (not sure whether this works on all build, Shu8i build does work)
jubeh said:
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
Click to expand...
Click to collapse
217 looks like 220 and leaving it blank sets it 160(thats what it looks like i cant tell really since it is blank)
pongster said:
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
Click to expand...
Click to collapse
would using a higher res wallpaper fix this?
Jragar said:
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Click to expand...
Click to collapse
160 on sense didn't mess up my status bar although some widgeds dissappeared. Which build are you using?
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
xkravenx said:
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
Click to expand...
Click to collapse
im on the same build as you with 210
copy out ur android folder onto ur hardisk as backup before u do the mod and u are safe if ur screen becomes black or u dun like it or it glitches badly and u cant modify it since u cant see the screen display properly..
This is sick,now my screen looks massive.Thx 4 the info..
"I pity the fool that owns an iPhone 4"
Sent from my HD2 using XDA App
please can you post before and after pictures
with 220 most of the apps doesnt scale properly and some doesnt work at all. Back to 240.
I set mine to 210.
It's hard to see the difference. I use MattC 1.5b with Froyo version...
The icons for "folder organizer" look smaller. But everything else seems to be the same. e.g. the htc sense applications, home, etc.
Maybe my mind is playing tricks on me.
here are some screenshots from the dpi changed from 240 to 200
xcooling said:
please can you post before and after pictures
Click to expand...
Click to collapse
This is what I've tried with mattcnexusleo1.1_512....
the 240 / 200:
I like the 200, it makes the keyboard smaller enough for me to type easier.
**mods please delete my post. JJbdoggg raced me to it...only sec's late sorry...
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
/android/root/system/build.prop
apeatan said:
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
Click to expand...
Click to collapse
You change build for that ? o-o
Shubcraft have cyanogen mod, wich is much more easier to make updates, no need to push anything and its great if you do a mistake see post above
-great tip thanks ! My screen looks really huge now at 200.. The appdraw is impressive too ... I'll wait for tomorrow to see if these smaller fonts are still readable with the sun.
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador
I find this odd.
Even though the screen is bigger, why does most things seems smaller?
I know how to text enlarge w/fonts...
though so many apps are TINY in writing and size in general.
Most of my apps display smaller than my Samsung Infuse.
One apps (Amazon is so tiny, i cant even see the text)
Does anyone have any ideas on how to manipulate?
I came from the Infuse also but don't notice the same problem. There are some apps, however, that aren't written properly and do have tiny fonts...but only a few that I've seen.
You could try Settings:Accessibility:Font size which will change the font size for the Calendar, Email, Contacts, Messaging apps.
someone told me about the app Fontsize....it increases the font size in pretty much all areas of the phone...its just under 2 dollars in the market. but it works great. i got it for my mom at one point when she got the note and was complaining about the same things.
Try adjusting your DPI to 340
that would def makes sense. ..cjanging dpi.
i didnt know there was am option for such.
question? How? Simple setting thing or a one to the world of mods? any add'l info...much alpreciated 4 sure....
Sent from my SAMSUNG-SGH-I717 using xda premium
You need to be rooted to adjust dpi. Then just download an app like LCD Density to set
Sent from my SAMSUNG-SGH-I717 using xda premium
I thought I read someone was having a similar issue and related it to certain apps seeing your phone as a tablet! I'll try to find a link to that thread for you. If you were rooted and not comfortable editing your build.prop then as mentioned in previous post the LCD density app would do it.
Sent from a phone suffering from an identity crisis!
wanted 2 say BIG UPS 2 both for as i d/l LCD Density. PERFECT! Fixed the prob for sure.i thought i was gonna go crazy ...quite a few apps dont size correctly and this ap sorted most out.
good looking out!
Sent from my SAMSUNG-SGH-I717 using xda premium
mrbogusbaxter said:
wanted 2 say BIG UPS 2 both for as i d/l LCD Density. PERFECT! Fixed the prob for sure.i thought i was gonna go crazy ...quite a few apps dont size correctly and this ap sorted most out.
good looking out!
Click to expand...
Click to collapse
If you start seeing problems with the market (apps not showing up), go back to default DPI, clear Market Data, reboot, hit the Market, do your thing, then set your DPI back. Repeat every N weeks/days.
Hello. Can someone help me learn about dpi settings?
I recall seeing a post in Beans thread that explained how to change the dpi globally to desired setting and then noted the app exceptions to be changed in the per app dpi; however, I've gone back 18 pages (and will continue to look) and still haven't found it.
I also titled search for dpi, read the majority of those threads and haven't found it there either.
I'd love to better understand what it does for me, such as applications opening in a tablet mode instead? I do realize it makes stuff smaller and sharper?
Thnx!
grimloktt said:
Hello. Can someone help me learn about dpi settings?
I recall seeing a post in Beans thread that explained how to change the dpi globally to desired setting and then noted the app exceptions to be changed in the per app dpi; however, I've gone back 18 pages (and will continue to look) and still haven't found it.
I also titled search for dpi, read the majority of those threads and haven't found it there either.
I'd love to better understand what it does for me, such as applications opening in a tablet mode instead? I do realize it makes stuff smaller and sharper?
Thnx!
Click to expand...
Click to collapse
Changing the DPI of apps is what ParanoidAndroid is famous for so if you want to see it in action the easiest way to see oer app DPI settings would be to watch some PA videos about it.
As for the Beans global app DPI changes I have no earthly clue, I run CleanRom and Vanilla Rootbox mostly, but if you want to mess around with it look up the Xposed Framework and the plugin for it that allows per app DPI changes. I would install that and play around with it if it was my first time using per app DPI settings.
I wish I could be more specific about Beans but seeing as how I dont run it I have no clue about it.... Maybe someone who does will be able to help a bit more.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Changing the DPI of apps is what ParanoidAndroid is famous for so if you want to see it in action the easiest way to see oer app DPI settings would be to watch some PA videos about it.
As for the Beans global app DPI changes I have no earthly clue, I run CleanRom and Vanilla Rootbox mostly, but if you want to mess around with it look up the Xposed Framework and the plugin for it that allows per app DPI changes. I would install that and play around with it if it was my first time using per app DPI settings.
I wish I could be more specific about Beans but seeing as how I dont run it I have no clue about it.... Maybe someone who does will be able to help a bit more.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Thank you. I'm familiar and have Xposed Framework installed along with App Settings and can change per app dpi. I'm just trying to better educate myself on what apps are good for "phablet" or tablet mode and how to get them there. Also, wondering about global changes. I have the below instructions but am just trying to read up what I can expect to see, etc...
"navigate to "system" and long press "build.prop", and choose to "open with - text editor". There should be 2 lines, 1 near the top, and 1 near the bottom that say something along the line of ro.sf.lcd_density=320, change that number to 240. Do that for both lines."
grimloktt said:
Thank you. I'm familiar and have Xposed Framework installed along with App Settings and can change per app dpi. I'm just trying to better educate myself on what apps are good for "phablet" or tablet mode and how to get them there. Also, wondering about global changes. I have the below instructions but am just trying to read up what I can expect to see, etc...
"navigate to "system" and long press "build.prop", and choose to "open with - text editor". There should be 2 lines, 1 near the top, and 1 near the bottom that say something along the line of ro.sf.lcd_density=320, change that number to 240. Do that for both lines."
Click to expand...
Click to collapse
As far as I understood build prop changes it for all your apps and can cause some to not work properly with the Play store hence why they came out with the work around with PA and Xposed.
A lot of apps have tablet mode that gets activated when you change the dpi, the best way is just to test really. I havent seen a definitive list of which apps work and which dont so....
Sent from my SCH-I605 using XDA Premium HD app
I changed mine to 480 and everything looks real good but as I figured most if not all of the LG/Verizon apps force.
Was wondering if there as any magic number that may allow these apps like contacts to work? I just don't understand why these manufactures create these big beautiful high-res display then blow everything up so people can read then from across the room.
Thanks
chooven said:
I changed mine to 480 and everything looks real good but as I figured most if not all of the LG/Verizon apps force.
Was wondering if there as any magic number that may allow these apps like contacts to work? I just don't understand why these manufactures create these big beautiful high-res display then blow everything up so people can read then from across the room.
Thanks
Click to expand...
Click to collapse
What is the code to get into the menu to get this?
i read another thread that had a code for the dialer but it didn't work for me.
chooven said:
I changed mine to 480 and everything looks real good but as I figured most if not all of the LG/Verizon apps force.
Was wondering if there as any magic number that may allow these apps like contacts to work? I just don't understand why these manufactures create these big beautiful high-res display then blow everything up so people can read then from across the room.
Thanks
Click to expand...
Click to collapse
530 seems to be working great for me. Read that anything lower messes with the LG apps. Some have used xposed to have per app dpi settings.
http://forum.xda-developers.com/showpost.php?p=54228904&postcount=80
Side note, I found that trickster mod works for changing the LCD colors. No gamma, but I think my display looks a little better now.
solidage said:
What is the code to get into the menu to get this?
i read another thread that had a code for the dialer but it didn't work for me.
Click to expand...
Click to collapse
I rooted my phone and edited /system/build.prop
Also 530 is the ticket. Looks way better
I have my system ui and android system at 390 with lg apps at 530 with minimum text size
Sent from my VS985 4G using Tapatalk
laxattack said:
I have my system ui and android system at 390 with lg apps at 530 with minimum text size
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Any help for a newbie? how do you do that?
Root, xposed installer, app settings
Sent from my VS985 4G using Tapatalk
for those that have changed their dpi... how does your lock screen clock look? i cant seem to get mine right. im using xposed and set the clock individually to 480 all the way to 640... no luck to get it to look right
Just changed clock widgets I had the same issue
Sent from my VS985 4G using Tapatalk