I know that when a dev is populating the androidmanafest.xml they add the <supports-screen> filter and choose the size screen the app will support. If they do not choose
Code:
android:[URL="http://developer.android.com/guide/topics/manifest/supports-screens-element.html#any"]anyDensity[/URL]="true"
then the app will be filtered from any device that has changed screen density, since it checks the /system/build.prop.
Is there any way to spoof a 'normal' screen density while keeping the density you want, or prevent the market from checking that portion of the build.prop?
LCD density app
There's an app called lcd density which changes the screen density. It's experimental and I don't know if it'll do the trick but it seems like the answer you were searching for.
It requires root, and you can't set the density you want on boot, but first you should check out if it doesn't crash your phone before setting on boot.
Here's the link for it:
http://forum.xda-developers.com/showthread.php?t=765639
Hope it helps
Thanks, but that is not at all what I am searching for. I know how to edit the build.prop to change density and the various apps that change it for you. What I am looking for is a way to prevent the market from filtering apps that do not support screen density smaller than 240.
It seems that there have been many posts about this, but no solutions.
Sorry about that, misread your post. Now I see what you are saying.
I doud you can do any changes in the way the market behaves facing your build.prop well you can probably but it doesn't sound easy. If there is no problem after you get the app but the problem is to download the apk why not getting it else where, on another market or on the web if you find you're hurting the developer find a way to donate to his app developing.
Well just brainstorming (can't hurt ), I'll look around for some answers on that subject.
I could go find these apps in other ways, but I like using the market (less now that it's updated), but it is a pain to change the screen density and reboot just to update my market apps. Maybe I should forget the market and go back to using Appbrain...
I understand your problem, I've searched around and didn't find any answers, I got the market apk i'll mess around with it to see if I can find an answer. In the meanwhile appbrain seems like a good alternative, does the fast web installer work?
Related
So I'm on eclipse .6 but I also had this problem on .5. Whenever I change my density to 220, as apposed to the stock 240, my mobile data connection cuts off and wont connect. Why is that? lol
I don't even know what you're talking about. What is this "density" you're speaking of?
Pixel density. There's an app called lcd density that changes it.
I dont use lcd density anymore because of the way it reboots the phone to set the build property it is editing and because if you reboot, you have to do it all over again. I use JRummy's android overclock to edit the build properties. It isnt free, but it is a little easier than editing ur build.prop in my opinion....
https://market.android.com/details?id=com.jrummy.droidx.overclock
DAG425 said:
I dont use lcd density anymore because of the way it reboots the phone to set the build property it is editing and because if you reboot, you have to do it all over again. I use JRummy's android overclock to edit the build properties. It isnt free, but it is a little easier than editing ur build.prop in my opinion....
https://market.android.com/details?id=com.jrummy.droidx.overclock
Click to expand...
Click to collapse
Root tools, also by jrummy, is a better solution, I think.
Sent from my DROID X2 using Tapatalk
You can also edit the line in build.prop to make any LCD density change permanent.
ro.sf.lcd_density = (input your pleasure) I have mine set at 180.
I used the text editor in root explorer ...
Keep in mind though that modded density levels may create problems with the Market, as some have reported that certain apps may appear incompatible with your phone after the change. This is definitely an issue with the new market (3.1.3), so I restored an older version (2.4.5) and froze market updater to resolve this.
Hope this helps ...
Pj
Messing with the LCD Density always causes some kind of conflict regardless of how you do it, I just end up keeping it at default.
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)
thanks in advance
apps
I have seen a few apps that allow you to do this, but have never used them.
Search market for LCD Density. Your need to have root to use it.
This was on the front page of xda. Not sure if it will work on our devise but its worth a shot.
http://www.xda-developers.com/andro...-permanent-rgb-sharpness-and-contract-tweaks/
Those of us who have had our TrueSmart have learned that while this thing is crazy cool, there are a few quirks that need to be worked out.
For example, the YouTube app's Full Screen. The TrueSmart has a square, not rectangle wide screen, so the Full Screen wouldn't be quite full.
With the Xposed Framework Installed, you can install a Mod called "App Settings" and find the YouTube app, then you can make DPI (resolution) changes and click "Force Orientation > Portrait Mode". Now when using YouTube, expanding to full screen will allow for a more 'dedicated viewing experience'.
There are some apps (found in the Play Store) that you can't access without accepting the ToS (Terms of Service), and the "accept" and "decline" buttons are below the screen. In this case, you'd need to change the DPI, and possibly more settings. I even also had the same SuperSU issues that quite a lot of us had: http://forum.xda-developers.com/showthread.php?t=2656146 There are quite a few ways to fix the spillage.
Also, simply because I feel like saying something, why don't we have subsections for General, Q&A, Accessories, Development and such? meh :/
deedscreen said:
Those of us who have had our TrueSmart have learned that while this thing is crazy cool, there are a few quirks that need to be worked out.
For example, the YouTube app's Full Screen. The TrueSmart has a square, not rectangle wide screen, so the Full Screen wouldn't be quite full.
With the Xposed Framework Installed, you can install a Mod called "App Settings" and find the YouTube app, then you can make DPI (resolution) changes and click "Force Orientation > Portrait Mode". Now when using YouTube, expanding to full screen will allow for a more 'dedicated viewing experience'.
There are some apps (found in the Play Store) that you can't access without accepting the ToS (Terms of Service), and the "accept" and "decline" buttons are below the screen. In this case, you'd need to change the DPI, and possibly more settings. I even also had the same SuperSU issues that quite a lot of us had: http://forum.xda-developers.com/showthread.php?t=2656146 There are quite a few ways to fix the spillage.
Also, simply because I feel like saying something, why don't we have subsections for General, Q&A, Accessories, Development and such? meh :/
Click to expand...
Click to collapse
Thanks. If you want to make you post a [Guide] I'll add it to the Everything sticky.
Except for the rotation issue, qemu.sf.lcd_density=115 added to the build.prop also resolves the "fit" issue on almost every app as well and is the reason why I'm adding it back to the patch for all x201s.
Lokifish Marz said:
Thanks. If you want to make your post a [Guide] I'll add it to the Everything sticky...... (Cont.)
Click to expand...
Click to collapse
I'll consider turning it into a guide. Friendly tip: It may have been a mistake but please try not to quote the entire long post, it takes up extra unneeded room, a @deedscreen mention in reply or partial quote works just fine. It can make things a bit hectic. (Ex: you have a long development thread and someone quotes the long post to say "this is cool".) Nevertheless, the guide is a good idea - now if we can only figure out how to get the status bar to always show when using -say- Nova launcher. My attempts haven't gone the greatest so far. :cyclops:
Hi Loki
Don't you just love when guys learns developers how to quote OP...
BTW - request is already sent to moderators for sections inside of Omate section.
Sent from my C6903 using Tapatalk
It was before my first cup of coffee so blame it on the lack of caffeine.
The solution I've been using is Swipe Statusbar. It's not ideal but does free up the space a consistent status bar would use. A permanent status bar fix is going to most likely require the framework and related files be gone through and redone as they use a show intent versus a hide intent from what I've been told.
I do use my ppi edit and Force Orientation on my daily device. Hopefully I can make the need for the orientation lock unnecessary and have it active at all times for all apps. That would cover the majority of users and apps used and can't remember the last time I wanted an app to rotate on the x201.
I know what you mean, with that app I've tried and it covers some areas of apps and drives me insane, I can't quite win...
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