Android OS Forum banner

JB market vs non standard DPI..How to Fix...Possible Fix

16K views 75 replies 21 participants last post by  philsfan 
#1 · (Edited by Moderator)
was running a fresh JellyBelly 3.7... I used AppBrain to reinstall all my apps from the Market. ( I had deleted my Titanium Backup Backups by accident).. A few apps said not compatible with device. Whatever, I get that.

After I was setup (about 63 apps installed) I set my dpi down to 250. Then the market showed only 23 apps installed. And i expected that due to nonstandard dpi...Few days later set up my dpi back to 320 to check for app updates...rebooted...cleared Google play cache and data...And it still showed 23..And apps like Facebook said not compatible.

With ICS I used LCD Modder to mod my market when using a different DPI.

I tried a modded Market apk on JellyBelly with no luck.. What's everyone else doing?
=========================================================================

Possible Fix.. Testing now.. 7/30 every now and then I lose apps and I just need to clear market app data and cache and reboot.

1. Manually open your build.prop and change your density
2. Reboot
3. Open up LCD Modder and download the modded market and gsk
4. Install mods
5. Reboot
6. After reboot I got allsorts of google app errors
7. Reboot into receovery and flash your gapps file for your rom
(this replaces your modded LCD modded market)
8. I then went back onto LCD modder and this time just installed the Modded market (phone will reboot)
9.Clear Google play data and cache

My thought on step 8 is that now we have the modded gsf installed and gapps overwrote the market, applying just the modded market again will give us both with no errors.

And I could be completely wrong....All as been good for me for 5 mins lol.
See less See more
 
#13 ·
cough, http://rootzwiki.com/topic/24275-jb-paranoidandroid-cm10hybrid-18-alpha-tabletphabletphoneui-fixes-mods/ ---gsm and sprint are also available

changing build.prop is a really, REALLY stupid way of getting what you want. that fix you have there will eventually break, they all do, works for a while and then breaks. the temporary fix is worse, that doesnt work at-all. PA is the only solution that exists right now that can deal with these things in a proper manner as you individually set apps to a dpi and to a display mode (phone, tablet, phablet-UI), or a whole bunch of em by settings user/system defaults. build.prop remains untouched, market works, other apps you dont want to shrink are not affected, you wont get keyboard troubles, non working phones and all that b/s. this is the reason cm never included a build.prop dpi feature, because it suckZZzz.
#15 ·
yes and no, depends what you change. it spans over the entire framework, even apps had to be changed. if its a safe zip modification or a theme it is fine, cm10 will eventuelly bring back the theming engine and that also will be file. people have modified it on xda, theres a couple of button related things floating around and dedicated themes aswell.
#36 · (Edited by Moderator)
[background=rgb(245, 245, 245)]sfreemanoh,[/background]

the real fun thing is the math behind it,

build.prop dpi changes the outcome of an internal formula which happen to read that value, DisplayMetrics.DENSITY_DEVICE. (320 for nexus) DisplayMetrics.DENSITY_DEFAULT is 160 always according to the sdk.

Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;<br />
mStatusBarCanHide = shortSizeDp < 600;
now the nexus has a shortest side of 720, so 720 * 160 / 320 = 360dp. thats why in phone mode apps will target their layoutcontainers up to 360dp.

if you change the dpi to 192, the formula will be: 720 * 160 / 192 = 600dp,
thats why the old play market went to tab UI at 192 dpi, because its higher res container lay at 600dp.
the new one needs 800dp (!!), so you will need 720 * 160 / 800 = 144 dpi in build.prop - it wont have 2 panes at 160 dpi.
600dp USED to be tabUI for systemUI in ICS, but google changed it. sysUI's tabUI is now at 720px, thats why you need 160dpi in jellybean.

you see how stupid it is? in lame ass build.prop tablet mode to make sure to get just about every UI there is you'd need to go as low as 90dpi for 1280dp, and apps can change it any day, just like google changed it for sysUI and jellybean. good luck with that.

whats worse though are the side effects:

- all apps shrink, most of them to unreadable mush, facebook and many others are almost unusable
- all apps are subjected to 720dp at 160 dpi, if they can swallow it or not. some apps break to pieces. you are fortunate that the market works, in ics at 192 dpi it did not.
- you cant get sane tabUI for most two-pane apps in jellybean because those get their definitions from framework-res and google introduced heavy margins that waste almost 40% of the screen. thats why your android settings look so dodgy
- overlapping, awful launchers, phone smashed, email app crashes

its sad, coz in reality,
what you call "tablet mode" is a single app, systemUI. that one displays bars (nav/status or combined systembar). because of that lousy little app you smash your entire phone. tablet mode for apps is something entirely different, they bring their own layout containers anyway. in android an app says, ok, i will switch to another UI if i detect a screen as big as 1280dp. its just coincidence that this build.prop tweaking happens to affect the packagemanager in such a way that it reads high res containers. in truth dpi does nothing but scaling, tablet UI has not so much to do with it. in truth tablet mode is not "small" and does not shrink apps, it wont smash apps, it wont project ALL apps into tabUI even if they work better in phoneUI like chrome, it does not overlap, etc., build.prop tweaking does that --- so yeah, im calling it a really shitty "solution." and now ask yourself why cyanogenmod has refused to include it into their rom.
#38 · (Edited by Moderator)
first thing you're doing is accusing me of baiting. are you not an asshole for being so meanspirited-if no then i am sorry.

i have used your density modder btw, more than that. i made your launchers work, i hacked your keyboards, i started petitions and wrote the makers of apex and nova to consider tabmode, sent them schemes and hacked examples, beta-tested their their prototypes, i hacked your marked, your phone, collected an entire pool of data concerning tabUI. its still on xda. who paved my way-everything that existed was a property tweak. even to this day, with the exception of a piece of work that i made for that very reason.

now if i see a guy asking about tablet mode on stock jellybean, why should i refrain from telling him that there is a true solution. and why would i not tell him that what he's getting himself into.

and that standalone app thing. you dont know what you are talking. you are clueless if you think you could do that. you have seen the images, you have seen the math. if you cant draw conclusions from it, your loss man.
#40 · (Edited by Moderator)
Know what...you're obviously a severely socially challenged individual. Who said anything about baiting? I said coming into a thread and talking about your ROM (which is fine) and saying how every solution throughout the last couple years has been crap (which is not fine, and then hocking your ROM, which is like used car salesman level sleezy) and only a temporary fix (which is not true...unless you meant temporary until I flash a new ROM, which was the only time I had to re-run LCD Density Modder) was classy (which was sarcasm).

Also...pretty pictures and math doesn't tell anyone anything about what can and can't be done as far as a programming solution. But as I already said, my problem isn't with your ROM or the work you put into it. And I'm damn sure not trying it now. My problem is with your crappy attitude.

And eman3316, saying "[background=rgb(245, 245, 245)]you will see he is not that much of an ass like he might appear" isn't really a glowing endorsement... And when he starts off 2/3 replies calling me an asshole, he's kind of proving you wrong.[/background]
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top