Related
What resolution do you use, and describe your user experience in google maps, etc
berardi said:
how do you do it? lol
I really gave it a try and in google maps I cannot see the smaller roads and overall it is just close to impossible for me to see. I don't have the best vision but I do wear contacts and I can see the 240 x 320 120 so much clearer!
So how do you do it and why? just wondering!
Click to expand...
Click to collapse
Well, I do use 320 x 480 @ 160 because I can see the whole Market. For things like Maps, you can always zoom. I do that a lot. I should say that I am nearsighted and take off my glasses to read. (Or I just look below the lenses.) You might try a pair of +1.00 or +1.25 readers. It might make all the difference for you, since you are wearing contacts. Obviously you can't take your contacts out. (I suggest this solution for you as a former optician.) Another solution for just reading things on your Touch is to increase the font size in Spare Parts.
Having said the above, if I could see the whole Market at 240 x 320 @ 110-120, I'd probably change. I have in the past used 240 x 320, but it seems like a pain to be switching. Also, AFAIK, you have to delete your data.img when changing resolution, and that is a real PIA. You lose so much stuff that way AND it takes a long time to boot while building a new data.img. I have been running Android on Fat32, ext2, ext2, booting from Haret. I haven't tried the NoMoRootfs yet, and plan to at least try that this weekend. My next step will be to try unlocking my phone and installing on NAND.
smarcin said:
Also, AFAIK, you have to delete your data.img when changing resolution, and that is a real PIA. You lose so much stuff that way AND it takes a long time to boot while building a new data.img.
Click to expand...
Click to collapse
you do not have to delete your data.img when changing resolutions .. .
tatnai said:
you do not have to delete your data.img when changing resolutions .. .
Click to expand...
Click to collapse
How do you get the Market to detect the resolution if it's locked at 240x320? The only way I was able to get it to change after I changed my resolution to 320x480 was to start a new data.img file.
berardi said:
What resolution do you use, and describe your user experience in google maps, etc
Click to expand...
Click to collapse
Well, I guess it depends. Running Myn's build on NAND, I found that 240 x 320 at 110 density was best for the BUUF theme, but I was having issues with google apps, in particular voice and maps were F/Cing on my every time I tried to open them, so I change to 320 x 428 at 160 and it worked well, but still got the F/C. Running at the same resolution and density with his new theme (hero), the widgets I have don't fit and overlap each other a bit, so I now have moved to 320 x 480 with density at 160 and everything fits better on the screen, but the wallpaper now seems stretched horizontally. I guess it's a series of compromises and it really depends on how easy it is to read the font, but also how much real estate you want on your homescreen.
Carrick1973 said:
Well, I guess it depends. Running Myn's build on NAND, I found that 240 x 320 at 110 density was best for the BUUF theme, but I was having issues with google apps, in particular voice and maps were F/Cing on my every time I tried to open them, so I change to 320 x 428 at 160 and it worked well, but still got the F/C. Running at the same resolution and density with his new theme (hero), the widgets I have don't fit and overlap each other a bit, so I now have moved to 320 x 480 with density at 160 and everything fits better on the screen, but the wallpaper now seems stretched horizontally. I guess it's a series of compromises and it really depends on how easy it is to read the font, but also how much real estate you want on your homescreen.
Click to expand...
Click to collapse
My sweet spot is now 240 x 320 with lcd density of 121, but I'm not using any theme. Google Maps was force closing on me at 120 for some reason. The only problem I have is the new dialers everyone uses are getting cut off 1, 2, 3
tatnai said:
you do not have to delete your data.img when changing resolutions .. .
Click to expand...
Click to collapse
You are correct, but if you want to get the Market to show you all the apps, I think you DO have to write a new data.img. You don't have to delete the old one, just back it up. Then, after signing into the Market at 320 x 480 one time, you can change to 240 x 320 and use your backed up data.img. What some people say is that after some days the Market resets so that you can only see apps that will work at 240 x 320. I can't confirm this as I just use 320 x 480 and avoid the whole issue.
smarcin said:
You are correct, but if you want to get the Market to show you all the apps, I think you DO have to write a new data.img. You don't have to delete the old one, just back it up. Then, after signing into the Market at 320 x 480 one time, you can change to 240 x 320 and use your backed up data.img. What some people say is that after some days the Market resets so that you can only see apps that will work at 240 x 320. I can't confirm this as I just use 320 x 480 and avoid the whole issue.
Click to expand...
Click to collapse
Exactly. This is the workaround I use that is linked in my FAQs.
On res I prefer 240x320, lcd of 110 to 114. Currently at 110. I don't think lcd.density is responsible for programs not working or force closes, I think a number of other things are more likely to be causative.
Wow apparently it doesn't take long for the Market to detect you did the 480 data.img and reflash to 320. I did mine on Friday night, and today (monday) the market is back to hiding market apps. I've already downloaded what I need but this could get annoying! In the past it took longer for the market to detect. (that or I reflashed a new build quicker)
Recently changed my dpi to 200 and unticked compatability in spare tools. Question is the apps that dont automatically scale is there a way to manually make them fit the screen? Cant live without my full screen papertoss but dont want to go back to the ugly large 240 dpi
I'd bump this because I can't find the answer anywhere, maybe my search terms suck.
I noticed the same annoying thing.
BUMP, for an answer...
Sent from my HTC HD2 using XDA App
Im confused ... I use 200 DPI and all my apps do rescale perfectly full screen after spare parts compatibility un-check and a reboot. Even paper toss... Only thing i noticed with papertoss was that I had to uninstall it and download it again from the market...
bigblanko09 said:
Im confused ... I use 200 DPI and all my apps do rescale perfectly full screen after spare parts compatibility un-check and a reboot. Even paper toss... Only thing i noticed with papertoss was that I had to uninstall it and download it again from the market...
Click to expand...
Click to collapse
Some apps are simply developed with 240 dpi in mind. Typically, it appears that they use Android APIs to draw bitmaps unscaled. Even though the Spare Parts setting allows them to "see" the higher logical resolution, the bitmaps are not scaled correctly.
Most of these apps can still be used (or played). There's not much to do except making the app developers aware of this problem.
Here are some apps with issues:
- Abduction
- GOTO lock screen
- Hyperactive Ninja
- Hello Kids
- Tower Bloxx
- Mini Shot Basketball
Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?
Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?
Set dpi to 240, install apps and then set dpi back to desired custom dpi
For me it happens also with old market app.
Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App
App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)
Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.
I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.
doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)
You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Thanks for the heads-up - I had no idea it would have been from the DPI setting.
It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck
Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.
thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!
Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
Seems everyone is having a lot of market compatibility issues lately on CM7 or stock rooted and I'm wondering if the way the market works has changed. In the past, it seems that it simply used the build fingerprint. But now it seems to be using the actual build model.
Has anyone looked at this or made a similar determination one way or the other?
I believe LCD density is now a factor, too.
Yeah, most of the recent problems people are having with the new Market aren't due to the model/fingerprint stuff, it's because the Market now seems to REALLY care what your LCD density is set to. I don't fully understand the logic of that, but it is what it is.
I think DPI is a problem, too.
Changing the /system/build.prop to 160 DPI changes lots of problems, but some things like Hacker's Keyboard get overly large keycap images because that's not the correct value. The value most of our rooted Nook Colors have in this file is 161 DPI for some unknown reason. It's probably really measuring the screen, but on an embedded device, it should not be measured but set to a static value like 160 or 170 and that's that.
The Nook Color is 170 DPI or 169 DPI depending on whom you ask.
This breaks the Android Market. It should not, but it does.