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)
LCD Density is the single best thing i've changed on my phone. Cannot live without it. Default is 240 and I have mine set to 200.
All apps work great except for the native Samsung apps. It looks like all the native Samsung developed apps are hard coded in terms of dimensions, while everything else scales nicely.
Is there a work around to make Samsung native apps play nicely?
This works with some apps but not all.. but it is worth a shot.
DL Spare Parts from the market
Turn off Compatibility mode. That got a few things to resize themselves appropriately for me.
you talking about the DPI setting? I run at 184. Be sure to do something divisible by 8 if you want your icons to resize right.
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
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.
I created a bounty thread for this tool in the i717 Galaxy Note General forums but wanted to make it know to the n7000 users too as it should work on all Galaxy Note models (And hopefully many other phones).
The Goal: A tool to spoof DPI at a per-app level to enable use of both Tablet and Phone apps without changing the default system DPI
Please keeping pledging in the original thread...
http://forum.xda-developers.com/showthread.php?t=1594559
Thanks
Why would you want to use an app not designed for a certain dpi to work in a crippled way ??
It would be much wiser to find a way to change the dpi 'on the fly' as you can do in windows for example. Maybe Google will make it possible one day, as we can already run apps in 'window mode' in ICS
friedje said:
Why would you want to use an app not designed for a certain dpi to work in a crippled way ??
Click to expand...
Click to collapse
You're looking at it the wrong way around.
Telling apps like Gmail, YouTube and tablet specific Apps you have a Tablet DPI enables UI layouts specifically designed for tablet viewing, they are not crippled, they are enhanced.
The Note's display resolution makes it a perfectly capable mini tablet that can run UI layouts designed for tablets. Samsung insist the Note is a phone and have gimped the system by removing tablet support despite the device having a 1280x800 screen.
Some may prefer using tablet mode, others may say it's too small, this tool is for the former rather than the latter.
I have attached pics of the awesome tablet views of Gmail, Youtube and BeyondPod running on my Note.
yes but it makes no sense to run them in tablet ui if you are set on a dpi of 320 even in 1280x800...
friedje said:
yes but it makes no sense to run them in tablet ui if you are set on a dpi of 320 even in 1280x800...
Click to expand...
Click to collapse
In Android DPI is an arbritrary measurement, dont get it mixed up with PPI, all you have to do is tell the App you are at 200 DPI and it will display that way
If that were true, then there would be no need to reboot when changing dpi, it could be done on application level which is, as far as i know, not possible.
However I could be mistaking, i will catch up on it....
As I see it now you would just only get your Gmail in tablet UI, displaying only half of it's content because the rest will fall beside the screen.
I think its a great idea +1
Gmail tablet UI is awesome.
Sent from my GT-N7000 using Tapatalk
DOGSofDOOM said:
I think its a great idea +1
Gmail tablet UI is awesome.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Don't get me wrong, i think it is a great idea as well.
But i doubt it is actually possible in the current android architecture
I don't care about UI differences. I want the stupid apps to install from the market.
So, far, they all look the same even when they're "incompatible". Typical lame crap.
It is done in the Asus Padfone, so it can't be impossible.
And how do you cope when the apps try scaling to the different LCD Density and half of the display is off the side of the screen, or things are bunched up in the corner of the display?
Wow, this is extremely needed thing! I realy like Tablet Mode on my Note, but can't use it because of many FCs. Sometimes I prefer Tablet Mode (Opera Mobile, Apex Launcher, File managers, Aquamail, Youtube official app and others), and sometimes standart "Phone" mode (Phone apps, S Memo, some small script apps, some games and others). Don't listen to those fools who say that this program is not needed.
This is exactly what I'm longing to see but I don't think it's possible for now as it's rather an OS related issue then just a software issue. I belive Asus padfone works only in low tablet dpi too. Apps only open in tablet mode . You can't change resolution on the fly
Sent from my GT-N7000 using xda premium
The problem is not changing the resolution on the fly,
but changing the dpi on the fly, keeping the same resolution
Totaly agree. I'd love to use those apps in tablet mode with spoofed DPI:
- Poeple
- Calendar
- Mail
- Music
- Calculator
- Settings
But the rest ? I really prefer phone UI for messaging, lockscreen, homescreen and the keyboard cause tablet keyboard is a nightmare to use.
There are some mods to force Settings.apk to work in tablet mode while in phone ui - but that's just wrong cause everything is ugly-huge and not readable. Would be great to force those apps to work AND display like in 180-200dpi while the phone ( and the rest ) works in 320dpi.
But is that even possible ?
That's it!
That is exactly waht I want for the Note!