Related
So i searched and found many posts saying to edit system/build.prop at the line
ro.sf.lcd_density=160
the point is, I do not have this line.
also lcd density changer did not appear to do anything when changing the value.
any clues chaps?
i'm on stock froyo build 318
crashDebug said:
So i searched and found many posts saying to edit system/build.prop at the line
ro.sf.lcd_density=160
the point is, I do not have this line.
also lcd density changer did not appear to do anything when changing the value.
any clues chaps?
i'm on stock froyo build 318
Click to expand...
Click to collapse
It's not in the stock build.prop. You must insert that line somewhere using the text editor in root explorer and change 160 to another number. The number must be in intervals of 20. Like 180, 200, 220 etc... Then restart your device and you're golden!
thank you very much mate I sort of imagined it myself but you know n00b to android etc, better safe than sorry
crashDebug said:
thank you very much mate I sort of imagined it myself but you know n00b to android etc, better safe than sorry
Click to expand...
Click to collapse
No problem! I like mine at 200 on the 318 build. Unfortunately on steve's builds 180 is the highest you can go without having the settings turn black when you hit the menu key. But anything is better than 160. Way too small at that setting.
well, i'm not saying that I regret 160, but I find 180 quite disappointing. too many words cut in icons and widgets etc. I reckon 170 would be optimal, that is, if it was a valid value ofc
ah, the perennial struggle for perfection....
looking for the same answer will 170 work ???
Steve's 1.7.0 has fixed the issue with LCD density of 200 and above. The menu works like it should. I can confirm this as I am running density=200.
I've been using a free program called "Incoming Call Plus" and it replaces the stock incoming call screen. This is good for LCD density of 180 and above, since you don't have the caller's name cut off.
Unfortunately, for me it's not fixed
I've tried 200 and 240 and same issue...
With 1.8 issue is now solved for me
Hey guys recently changed my DPI, I found using this app you can set your saved density as "240" and change your density via the "PREVIEW" button to "190" and still be able to use the market as per normal..
Although this got me thinking.. why cant we make this a permanent change ? So spoof the DPI to the market making it believe were on 240.. although in reality using 190..
Any ideas ? every a start up script which will detect if the current DPI is set to 240.. to put the device in LCD DENSITY CHANGERS "PREVIEW" state of the DPI to 190.. or better yet actually edit the Market app.. to force it to read the DPI as 240 all the time ?
Im new to the android scene.. so not sure if this is possible or not but would love to see this happen..
This was a duh moment for me, so learn from my fail.
If your having issues with apps not allowing you to update/install and the online market says your device is not compatible and you've modified your lcd density, comment out that line in your build.prop and reboot. Open the market after and poof, market works again. Likely the reason folks smarter than me (djsteve, etc.) comment this line out or exclude it by default in roms now...
Sent from my Dell Streak
Ic... understand now...
strvmarv said:
This was a duh moment for me, so learn from my fail.
If your having issues with apps not allowing you to update/install and the online market says your device is not compatible and you've modified your lcd density, comment out that line in your build.prop and reboot. Open the market after and poof, market works again. Likely the reason folks smarter than me (djsteve, etc.) comment this line out or exclude it by default in roms now...
Sent from my Dell Streak
Click to expand...
Click to collapse
Thanks for the information...
I was confused because this happened today after re-flashing the rom and adjusted the LCD density... (DS5 to 200, Galaxy 5 to 130) but should give up to adjust LCD density to suitable for me because of this market problem ?? Not easy to decide....
Is there any other solution ???
Thanks, anyway... help me to save my time a lot to find out the problem...
there are no known solutions to this problem except a couple cheap tricks (only one in fact: freeze the market updater, uninstall all market updates and manually install market v2.x, but you still wont be able to install from the website).
also it is nothing that rom chefs/devs can solve: it's a "feature" google implemented in the latest market versions. of course it's device independent, too.
the only good lcd densities are 160 (streak default) and 240 (big UI small estate, like all normal 4'' screen phones).
I run my streak @ 240 dpi and have occasional issues with the market, I use lcd density changer app to change the dpi, it's easy enough to reset to 160, install the app, then reset the lcd density....not a hassle, really (I wish it wasnt necessary but oh well, I guess if I want to tweak the device around, having to do that is part of the tweaks needed)
GT247 said:
I run my streak @ 240 dpi and have occasional issues with the market, I use lcd density changer app to change the dpi, it's easy enough to reset to 160, install the app, then reset the lcd density....not a hassle, really (I wish it wasnt necessary but oh well, I guess if I want to tweak the device around, having to do that is part of the tweaks needed)
Click to expand...
Click to collapse
weird, 240 dpi shouldnt be an issue (as a matter of fact, on mine it isnt) because it's a standard setting. most phones (like sgs2, sgs, sensation etc) use this value.
240 may be standard with most devices, but not the s5.
240 breaks the dialer, ui wise on 2.2, completely on 2.3
The default dpi is 160, why stuff doesnt show up on market might have to do with the way the app author published it, or it could be a bug
TheManii said:
240 may be standard with most devices, but not the s5.
240 breaks the dialer, ui wise on 2.2, completely on 2.3
The default dpi is 160, why stuff doesnt show up on market might have to do with the way the app author published it, or it could be a bug
Click to expand...
Click to collapse
yes, but it's a standard setting. hdpi has 240 mdpi has 160. Therefore publishing an app that isnt compatible with 240 would be overkill for a developer. Regarding this there is a bug report on google, link:
http://code.google.com/p/android/issues/detail?id=19744
the problem, it seems, is related mainly to a change of policies from google: now developers MUST explicitly declare compatibility with non-standard lcd densities whereas in the past it was simply ignored.
I recommend everyone to star the issue at the above link (but don't comment as every comment generates notif email)
Hi,
I found how to change android screen resolution through changing dpi no in build.prop file,
the problem I'm facing is that I can't save the file after I put the new dpi setting no.
I get error saving message on my Galaxy s4
could somebody help me with that please
Not A good idea
theniner said:
Hi,
I found how to change android screen resolution through changing dpi no in build.prop file,
the problem I'm facing is that I can't save the file after I put the new dpi setting no.
I get error saving message on my Galaxy s4
could somebody help me with that please
Click to expand...
Click to collapse
If you entered a non compatible DPI settings it will NOT boot up, so before changing please test the DPI settings first by using any dpi changer apps but do not set it to boot up permanently with every boot.(temporary dpi settings to see whether it work on that dpi)
cracktech said:
If you entered a non compatible DPI settings it will NOT boot up, so before changing please test the DPI settings first by using any dpi changer apps but do not set it to boot up permanently with every boot.(temporary dpi settings to see whether it work on that dpi)
Click to expand...
Click to collapse
Thanks for your reply,
the whole issue about screen resolution is when I open Firefox browser I used to log in express.paltalk.com which uses flash I could view log in screen big enough enough, after sometime I accidentally used a program called screen resolution changer then when I go to paltalk express log in flash webpage a message says that I am using low resolution and it recommends to click where it redirects to log in with lower resolution but viewing and typing log in user name and password is very hard to do because it isn't viewable normally like it used to be.
I did try change screen resolution and dpi setting several times with even factory default settings using mentioned program also cleared privacy and browsing history on Firefox browser nothing changed, still log in screen is small and can't even type in my user name and password.
By the way this happen also with other different browsers like chrome.
I think what I need is factory default resolution and dpi settings if I'm not mistaken.
your help is appreciated
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Brava27 said:
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Click to expand...
Click to collapse
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
wase4711 said:
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
Click to expand...
Click to collapse
Yes I know that and changing it in the build.prop is what textdroider does. I've done it with app and manually and it doesn't change anything.
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
wase4711 said:
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
Click to expand...
Click to collapse
Yes the new value shows after manual (and after textdroider) edit and save/reboot but the screen DPI doesn't actually change. The value is shown, but the screen is the same.
There are actually a few different values, the one that is 400 is the one I'd been changing. I wasn't sure what the two 640 values were and haven't changed them. Never seen a build.prop with multiple values. Didn't know if maybe those two values corresponded to the left and right edge screens since there are settings for them.
Have you found out any more info about this setting?
Has anyone tried running this via adb shell:
wm density 380 (or whatever density you want)
This worked fine without root on my Xperia phone. Just curious as I am thinking about getting this phone, but not setting density is a potential dealbreaker.
Alright so an update, it's the first 640 value that changes the DPI. The one under #system.prop for universal7420. I changed it to 580 and the attached pic is the result. I loaded google now launcher to test the scaling and it appropriately scales itself to use the whole screen whereas TW moved itself to the top left of the display. I guess the next challenge is to make TW properly scale.
I noticed that last night. I wonder what the other 2 dpi settings control?
adb works
I have successfully changed the DPI using adb on normal S6, though Play Store now believe it to be a tablet. Also, most of touchwiz hates it, not a big deal for most things, camera may be the biggest annoyance when its only taking up the upper right 60% of the screen.
Has anyone sucessfully changed the per app DPI, like you can with Paranoidandroid?
Look for "buil prop editor" on play store!! But the kamera and keybord looks like a#$
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
wikidavid said:
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
Click to expand...
Click to collapse
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
schollianmj said:
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
Click to expand...
Click to collapse
I'm just trying these things :
1) delete double post/overflow on the forum
2) give a solution anyway.
Don't be upset, there's no reason to... Have a nice day !
boosting1bar said:
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
Click to expand...
Click to collapse
I also tried the same thing with no results
Hi,
I changed my DPI successfully by changing the first occurrence of ro.sf.lcd_density from 640 to 540 in /system/build.prop using the built-in texteditor in root explorer (and rebooting afterwards ofcourse).
Then I noticed the camera didn't work properly anymore, so I created a fix for that (see this post).
Hope you'll get it to work, it seems the same to me as on earlier devices with as exception that the ro.sf.lcd_density occurs multiple times in the build.prop file.
Cheers,
Bane.
For testing different resolutions:
- have a functional adb
- enable USB debugging on device (developer options)
- connect device to your PC via USB cable. Then start a cmd in folder containing adb.exe. Type "adb devices" (without quotes) in the command prompt to check if adb recognizes the phone
- If is OK, type "adb shell wm density ZZZ" (no quotes) where "ZZZ" is the pixel density value you want to try (default is 640)
- no reboot needed, the change is on-the-fly
- check the programs (Samsung ones - dialler, calendar, camera, launcher, etc...)
- the change will disappear when you reboot your device.
per-app DPI...not; only with Xposed, when will be available.
Once you find the desired resolution it can be inserted in build.prop