I am running Eclipse 2.0.3, with blooded theme, and v6 script. When I try to update ANY of my apps, I am getting an error that says package is invalid. But, when I try to update a second time, it updates fine. Is this a common issue?
Settings applications clear data for market. If not it, then clear same for google framework.
My 203 market is fine.
Did you by any chance change the LCD density on your screen? I found that changing it from the default 240 causes a LOT of apps to come up as "not compatible with your device". If you altered your screen density change it back to the default.
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)
I just got my One X+ yesterday.
Coming from a HD2 (Leo) this is a great leap forward! BUT: I need/want a lot of icons/text/pictures/... on my screen. (My hd2 used to be at 160dpi)
So; I rooted the One X+ and changed density to 240, which looks nice. I als installed ADW Launcher since a) I like it better and b) sense doesn't seem to work with other LCD density.
Now here's my problem: although I don't want/need sense anymore, it's off course still running in the background and is thus still producing quite a few error messages. ("HTC Sense was closed unexpectedly. ......"). Is there any way to solve this? I don't really mind Sense running in the background, but off course the error messages bother me a lot!
Can I a) block those errors somehow or b) get the 240dpi-look in another way than I got it now?
Thanks!
(also: I lost the htc flashlight app somehow and I can't install it back with the apk file (it just says: app not installed). any thoughts on that?)
I am running 250 dpi with go launcher. I don't have any sense related errors. where are you getting errors?
For reference: the errors occured just after bootup (after dialing pincode, two or three errors). Then, when I went into ES File explorer, or when I went to settings (every settings page concerning sense, like display settings etc...). Two subsequent (identical) errors.
Also, after restart, android didn't seem to remember my launcher app-preference, so I got the "Complete action using.." error. Chose "ADW Launcher EX" and tapped "always use". It remained ok untill next restart, so it didn't really bother me... Strange thing: when I chose Sense and tapped "always use" it DID remember after reboot....
Now, I first did a factory reset: nothing changed, same errors.
Then I reread your post, dashingdon, and thought: let's try some stuff...
I set the dpi to 250: no win...
I set the dpi back to 320, deleted ADW, rebooted, installed Go Launcher, set to 240 dpi: no win...
I then set the dpi to 250 and voilà: this seems to work! (need to fiddle a little more, but after 5 restarts I yet have to get my first error) I now hope play store won't mind the new lcd density...
Thank you for your help!
to all others: If you would know another solution, I'd still like to hear, since I like ADW better...
Zoomb said:
I then set the dpi to 250 and voilà: this seems to work! (need to fiddle a little more, but after 5 restarts I yet have to get my first error) I now hope play store won't mind the new lcd density...
Click to expand...
Click to collapse
If play store starts giving you incompatibility issues , just uninstall the updates for "Play Store" , clear cache and let android re-install it. that should fix.
Does everyone's Facebook app UI become like the screenshot I attached below? I found out that this is a DPI thing. With DPI set to 320 (stock value), then Facebook UI is messed up. IF screen DPI is set to 325 or above, then the layout becomes normal. The thing is, at 325 DPI., stock apps' UI (like Contacts) will be messed up. per-app DPI settings using an Xposed module doesn't help either. So catch 22. This annoying bug has persisted since v47 or around that number, I have filed several reports but still to no avail.
If enough Z Ultra users report this then maybe Facebook devs will fix it.
* I'm on Stock 5.1.1 latest firmware
Yup, FB is the same for me but I don't think it's a bug in Facebook. There is an app in system called "com.android.overlays_305dpi" or sth which I presume sets some apps to be displayed as if the phone had 305dpi set but that is just a wild guess.
Oi,
I'm currently at 540 dpi set via build.prop + a few apps modified by working (yay) AppSettings. When sleeping the phone, for the first second or two, everything looks okay, before the hour font goes crap. The date font stays fine tho, so do the notification icons. Trying to force stock (640) dpi setting on aod/clock, AodEx processes won't help. Has anybody noticed/figured out a way how to handle this?
I just did leave everything normal, and set stuff like systemui to the dpi i want with AppSettings, works fine for me.
I modified it through ADB and I see the same results. It looks like there is a differently sized black outline of the time that should be there.
I can live without always on display but i find alot of apps have enlarged resources. Most notably in the play store.