I am writing to get some details or clarification on the LCD Density of the Droid X2.
I have noticed on several sites that the lcd density is ~256 ppi pixel density. PhoneArena and GsmArena both list this. Wikipedia has useful information, but not in this aspect, or it is nested under a subject somewhere. I noticed in the standard stock Verizon rom in the build.prop that it is set to 240, I also noticed this is the same setting for the CM7 build also.
My conclusion is that it is set this way for app compatibility? I understand that it can make the resolution smaller or larger depending on the setting. I have with other phones, changed the density and some looked and performed better (Possibly my imagination?), but it broke some apps and thoroughly pissed off Android Market. By The Market statement I mean that many apps were reported as "not compatible with your device".
*The easiest thing would be a explanation of the pros and cons of this setting/adjustment.
*Also a tip on how to fix the market, along with apps that get cranky when adjusting this setting. (It may be possible that the market and app issues are gone now, but making sure of this) I have skimmed some resources but none that were detailed enough or were just too excessive. The threads here, what few that are related get turned into an app fest discussion.
(Point is not what app to use or not to use to adjust density).
Please be simple and to the point, unless you truly know what you are talking about. I thank everyone who contributes to this discussion.
It's interesting you point this out. I have long suspected app issues are with the odd PPI of the X2.
In calculating the true density, I come up with 256.7 PPI. That means it falls into the hdpi catagory. However, you are right about the build.prop saying it is 240 PPI. I think this is just set as the minimum for the app to appropriate the correct layouts.
I doubt this actually has to do with the issue you are having. A lot of developers do not allow certain apps to work on devices for which they have not tested- although they shouldn't be appearing in our market in the first place.
To fix the market freeze the market auto updater with your favorite bloat freezer. Boot into 240 dpi. Go into settings then manage apps then the market and clear data. Go into market and click accept and back out. Then boot into preferred dpi. This should fix any issues. If they arise, repeat. This worked for me.
Sent from my MB870 using xda premium
Hey there. I'm very curious as to what the proper steps to change this setting are. I don't want to just go into my build.prop and screw some things up. I found the line. Should I just backup my phone, backup the build.prop and then edit the line and reboot my phone? Thanks for anty help.
Sent from my MB870 using XDA App
Reservation 1
.......Reserved for possible future usage on this thread
Related
Hi all,
I was wondering whether anyone had any theories why some apps I've paid for disappear when using different ROM's / Phones.
The Apps I can use as an example, are as follows:-
1. Exchange by Touchdown Key by NitroDesk, Inc
2. RootTools by JRummy16
3. 360 Live by Juan Xavier Larrea
For example, while using Lite'ning ROM v6.0 on my SGS2, all those apps were available. But when I changed ROM's to the SensatioN ROM by Crysis, they disappeared.
Similarly, on my X10i when I upgraded to 2.3.3 they all disappeared. And because this happened without any tweaking, i.e. it was using Sony's release without ROOT'ing, I contacted Android Market Support and this was their explanation in relation to the Touchdown Key.
"Thanks for writing back. It appears in a recent update by the developer,
they changed the screen requirements of the app, it now only supports
Normal, 160 (density) screens. The specs on your device show as Normal 240
(density). So to continue using this app you will need to contact the
developer and request the 240 be added into the app."
So with that response in mind, I'm trying to figure out why there is a difference on my SGS2 when I switch between Lite'ning ROM and the SensatioN ROM.
Any thoughts? Does anyone know why I am seeing these differences between two ROM's? Is this something to do with tweaks within these ROM's and the density that Market Support is talking about above? Or the old problem of footprinting?
There's no way to definitively answer your question, unless you know the particular applications as well as the developers.
Yes, a lot of ROMs have different LCD Density values. If it is just down to LCD Density then that's a very simple fix. Try setting it back to 240 (default value) and see if the application reappear. I've never heard of apps not showing in the Market due to LCD Density though. I think you've just been fobbed off there, but I'm not 100% sure - just about 99%.
In case you don't know, to set LCD Density you need a rooted phone. Edit /system/build.prop and find the value in there. You can do this manually with something like Root Explorer (my personal choice), or there are apps that set LCD Density available on the Market, but lots of them don't persist the change for long.
Thanks for the reply mate.
Yeah, my phone(s) is rooted. I'll do a few tests with an App I saw on the market (LCDDensity for Root) and see if that makes any difference to the market content...
Funnily enough, I stumbled across this post from searching for that app in Google...
http://forum.xda-developers.com/showthread.php?t=1183444
I'll report back whether it does fix the problem...
Grevane said:
Funnily enough, I stumbled across this post from searching for that app in Google...
http://forum.xda-developers.com/showthread.php?t=1183444
I'll report back whether it does fix the problem...
Click to expand...
Click to collapse
I'm surprised by that, but if that's what it does then that's what it does! Have you tried browsing for apps in the market on your PC? Obviously your PC doesn't know what your current LCD Density setting is on your phone, so it may not be relevant.
Maybe remote install from the website is the way to go.
Different ROMs are based from different builds, which can also include for which device as well.
So if the rom you are using announces itself as htc sensation, your samsung only apps goes missing in market, and vice versa!
Android market allows the developer to choose which brands/model phones they want the app to be used by.
LiFE1688 said:
Different ROMs are based from different builds, which can also include for which device as well.
So if the rom you are using announces itself as htc sensation, your samsung only apps goes missing in market, and vice versa!
Android market allows the developer to choose which brands/model phones they want the app to be used by.
Click to expand...
Click to collapse
Is that relevant though? I thought that all the ROMs for the S2 were based on the Samsung ROMs. There's certainly no HTC ROMs available for it.
Of course, the developer can put in the build.prop (I believe) whatever they want, but why would they do that?
Well, so far, as far as I can tell, the LCD Density hasn't helped....
I also cannot install "remotely" from the market website as the market website says "This item is not compatible with your device".
I've also tried this... without any success...
http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425
ViralCipher said:
I found the solution to the market downloading problem! For anyone who has been having the Market Downloading issue with this ROM do the following and it should fix your issue. It fixed the issue for me and a co-worker.
To fix the market you go in manage applications:
1. Find Google frame work, clear all data and then force stop
2. Find Market.apk – then clear cache & data, then force stop.
3. Then, open ROM manager and fix permissions.
4. After the permissions have been fix, boot into Clockwork from ROM manager. And then format the Cache Partition.
5. Now reboot and test.
Click to expand...
Click to collapse
Hmmm... strange...
I'm surprised to see I am the only person I have seen with this issue; either that or I'm looking in the wrong places. About a week or so ago, my android market was updated to the newest version, ever since then it has been a nightmare. apps that I have been using for over a year now say there not compatible, when I know for a fact they are. I recently flashed the latest CM7 nightly and when I brought the market back up, some of my apps said they were already installed when they in fact were not, however there was no way to override this so I just seemed to be sol.
The final straw was this; I wanted to install "multiling keyboard", so I went to the market and there was no download button to be found. So I went to the market on my PC and found that it listed my EVO and my modded HD2, it said the app was compatible with both handsets believe it or not. However it said the the app was already installed on my EVO, which at the time it was not. I searched for hours and found no way around this. So I tried a different Google account, thinking maybe it was linked with that account. I then searched for the app again, and believe it or not, It then told me that the app was not compatible, log back into the other account, and the app is listed as compatible but also listed as already installed with no way to override.
So now I find the only way to install certain apps is to uninstall the market updates so it goes back to the old market, then I can download whatever I want no questions asked. However its only temporary because within 15min it will automatically update itself again.
Get titanium, freeze market updater. Had the same issue
Sent from my SPH-D700 using XDA App
Ok I froze the market updater, and then downgraded the market app from 3.0.27 to 2.3.6. It seems to be working, I'll post back if I have any issues.
However even though this is a fine workaround for now, does anyone know of a way to just fix the issue? obviously we all cant just stay at an older version of the market forever.
Google has been rubbing me the wrong way for about a year now, but this has really got my blood boiling. I don't need someone telling me what they think is already on my phone what whats not. I also don't need someone telling me whats compatible and whats not. I can fully understand licensing restrictions, don't like 'em, but i get it. but as for these new checks they implemented, there needs to be a bypass feature. Either have a "I am not an idiot" setting in your account, or just a button that says "I understand the risk, Install anyway". But this is ridiculous, something has to be done. I have already sent Google a letter, doubt anyone will read it, but i sent it.
I would also love for a solution to this... not a reversion...
Anybody out there have any clue where to start? I have been searching high and low and cant find much of anything.
ITS THE LCD DENSITIES! lol. Do you change your lcd density to? Because when I change mine back the market works fine
I never thought of that, but yes I do change my LCD density, I have it set to 200 instead of 240. That explains the incompatible issue. I'm still sol though, I'm not going to change my build.prop every time I want to use the market. Also I'm still having issues with it saying that apps are already installed on my phone when they are not.
Thankfully ugothakd's suggestion is working great for now. I hope we can get this figured out. If not its just going to end up being one of those things we will have to wait forever for Google to fix.
android market compatability issues
Thank you ugothakd! I change my density from 200 to 240. Now I have access to google maps and youtube. Really sucks though I like my density set to 200. I am surprised that people are not having more problems with this dumb market.
I don't mean to bring this back from the dead. But has there been any word on this issue? I'm still stuck at an old version of the market. I've tried updating and every time I still have the same issues. Its all over my screen density, if I change it from 200 to 240 the market works fine.
I have the same issue my self i have a htc desire and now with new market to apps that are missing
if i click on link in google to point to market for app all i get is this app ain't compatible with your device when i know for fact that it do
im starting to get pissed off with it as i used the new market before it was released over here in uk and now after i update my cm rom this is all i get or the app don't show in first place
google really need to add an option to disable this feature ie under options for people who know the risks of trying to run apps that may not be intended for the device as i personally have found nearly all apps work on my phone rarely come across any that don't even all the old apps tend to work if anything this new feature is a pain in the rear so so annoyed at this
P.s screen density has nothing to do with it with me i found new market added a new device to my list yet it's the same phone i leave my screen at 240 its default hope this gets sorted soon
Sorry to bring up an old thread but has anyone resolved the issue. I love my LCD density at 180 and setting it back to 240 just to install an application really irks me.
Has anybody else had trouble with the Photon being incompatible with a lot of apps from the market?
Specifically, the market is showing the "Sprinkle" game as incompatible even though it wants a Tegra processor and that is what we have.
If anybody has had this problem have they managed to find a solution to allow us to install these apps?
Thanks,
Koriel
I have run into this with one app. The market says it is compatible with the ogEVO but not the Photon. I'm sure it would probably run just fine on it but can't download to find out. Must be something the developer does when posting the app to the Market?
The app might have been compiled to use Sprint's "Evo" SDK to interact with the front camera, Wimax, etc. I'm pretty sure that the "Evo" and "Epic" SDKs became moot around the time the Epic (finally) got 2.2, and Android itself acquired phone-neutral ways to deal with secondary radios and extra cameras. AFAIK, the only phone-specific APIs left for Sprint phones are Kyocera's (for functions specific to dual screen use) and the Evo3D's (for functions specific to 3D).
I haven't had that problem in general, and specifically I have Sprinkle installed on my Photon right now. So, doesn't seem to be a general problem, and I have no idea why a specific Photon wouldn't be able to install a specific app.
Sent from my Transformer TF101 using Tapatalk
Did you modify the build.prop?
When I look up Sprinkle in the market I get
"This app is compatible with some of your devices.
Photon"
That's a possibility. Does anybody have a default build.prop from a "post-update" Photon that they could upload? Ideally, one where you have managed to get "Sprinkle" to download and play
Finally solved this, I had changed the LCD density from 200 to 240. Changed it back again, rebooted and no difference.
Finally I conceded and performed a hard reset, when the phone came back again I could download "Sprinkle" at last!
koriel said:
Finally solved this, I had changed the LCD density from 200 to 240. Changed it back again, rebooted and no difference.
Finally I conceded and performed a hard reset, when the phone came back again I could download "Sprinkle" at last!
Click to expand...
Click to collapse
You do not have to do a hard reset. Only have to clear the Market app data/cache under Manage Applications.
Had the same problem and resolved by resetting to 240, rebooting, and clearing market app.
Hi all.
Noticed that recently I've had a lot of Market apps claim that they are not compatible with my phone.
I tracked this down to my display density. I use a setting of 200 instead of the phone default of 240 and this stops apps being flagged a compatible. It's a pain to have to keep switching resolution just to instal them and they invariably work fine at the higher resolution setting. Is there a way to stop the Market checking?
Sent from my GT-I9100 using Tapatalk
Google is really dropping the ball with this issue. As far as I know the only fix right now is what you posted, change to 240 and reboot.
You also can't update these apps with custom dpi as they don't show up in "My Apps"
Please report the "Applications missing from My Apps" bug here
http://www.google.com/support/androidmarket/bin/static.py?page=known_issues.cs
Good point on the update.
This is pretty annoying.
Sent from my GT-I9100 using Tapatalk
I tried to download ShadowGun onto my TP running CM9, and it says that my device is incompatable.........why?.....
Also tried it with Need for Speed Shift.....
Oh, btw, both are on sale for $0.49
The touchpad is not running official android so some apps, usually games, don't recognize it as compatible even when it is. You will want to change the build.prop file to an official android device with similar hardware, if I was on my desktop id give u the exact device
Sent from my DROID3 using Tapatalk
Build.prop file??????.......lol......let me go search it up......thx for the reply.....
Downloaded fine for me. Plays pretty smooth too. Running cm9 alpha 2.
Sent from my SPH-D700 using XDA
Worked for me I'm on cm7.
Sent from my android touchpad.
Followed the instructions in this post, and all is well.......
http://www.everythingabouttablets.net/2012/01/02/get-asphalt-6-hd-running-on-your-cm7-touchpad/
Also, if you've changed your LCD density, a lot of apps will show up incompatible. You can either change it back to 160, or use an app like lcd density pro to download a modded market apk that will work with your custom screen density, while making the market think you are still running 160.
mike-y said:
Also, if you've changed your LCD density, a lot of apps will show up incompatible. You can either change it back to 160, or use an app like lcd density pro to download a modded market apk that will work with your custom screen density, while making the market think you are still running 160.
Click to expand...
Click to collapse
Thanks for recommending lcd density pro I was a little skeptical about paying ~$3 for it but it seems to work great with the app market where I change my DPI to 132 the native DPI of the Touchpad.
You may want to try the "rohan" update here in the Dev section. It changes a bunch of stuff in your build.prop file. I was able to download and start Shadowgun last night (I didn't really try playing). I still had problems with Dead Space, and haven't tested any of the Gameloft games yet.