Default 275DPI results in market error? - Motorola Droid 3

One of the nice things about D3 is that they have 275 DPI(qHD in 4inch). When I fresh first installed Liberty rom, its fonts and UI were all too small and I did not like it at all. I went into the script files and saw that the DPI was set at 220. So I after I changed it to 275 and rebooted, Voila! it looked normal and beautiful. I guessed that 275 is what it supposed to look like in the first place since it is the default DPI for our phone. But as soon as I changed it, the market was screaming that the apps were not compatible with my phone and I noticed many UI windows were cut off.
So is this problem only occurring to Liberty rom? I'd like to use 275DPI as it is what it supposed to run at. I also tried to run compatibility mode off also.

Related

[Q] How to enable/disable Compatibility Mode?

I've had my prop.build changed for a while from the default 240 to 190 and love the high-res look it provides, but obviously some apps don't automatically scale right with the change.
I heard something about either turning Compatibility Mode on or off to fix the problem, but have no clue where to make this change.
TL;DR
How do I turn compatibility mode on or off?
There's no such thing. Once you change that file, the display driver will display everything at 190PPI. It's not an application based thing (which is what what you're talking about sounds like), so if you want to run an application that doesn't support the res hack, you'll just have to edit prop.build back to 240 and reboot. It's pain, and that's why I haven't bothered with it.
Edit: Just speculation; you capitalized 'Compatibility Mode' as if it were an actual setting somewhere. Just to make sure, the res hack is in no way supported by Samsung or default AOSP settings.
Yeah I assumed it was a setting somewhere but I guess I must have read something and misconstrued it to apply to what I was thinking about.
SG Pillar said:
Yeah I assumed it was a setting somewhere but I guess I must have read something and misconstrued it to apply to what I was thinking about.
Click to expand...
Click to collapse
I'd assume so. But yeah, just bear in mind that if you're editing files like that, then it's most likely not going to be very well supported, and normally there isn't going to be a fix (unless it's built into a ROM by a dev, in which case the dev probably wouldn't think to release a standalone fix anyway). But that's the joy of Android, right?
download Spare Parts in the market. its in there.

Is there a fix for the new market yet?

I'm running CM7 nightlies on my Nook, just wondering what I need to do in order to get the market work the way it's supposed to. (Hidden download buttons, can't update apps, etc)
set lcd density to 160 in build.prop
force stop market, clear cache
brings back functionality for ~ 1 day, clearing the cache again get's you another day, etc.
long term fix...?
NCKevo said:
long term fix...?
Click to expand...
Click to collapse
That's what I'm looking for
NCKevo said:
set lcd density to 160 in build.prop
force stop market, clear cache
brings back functionality for ~ 1 day, clearing the cache again get's you another day, etc.
long term fix...?
Click to expand...
Click to collapse
I've failed at this multiple times
Using ES File Explorer and giving it permissions, I can edit but not save the build.prop file.
Don't know if this matters, but I have CM7 on the sd card (no eMMC install).
Also, I suspect the /system folder is read only?
I thought the solution is
a. Stop (rename or uninstall) the MarketUpdater
b. Clear cache / data on the Market then uninstall "Updates"
Step b. above is a roll-back (old) version of Market (2.6.x.x?)
Step a. above is stopping the Auto Update of the Market.
There's some report of modifying the density to 160 in the build.prop.
you can also use a LCD density changer app from the market. the biggest problem is that none of the fixes are long term. you can change the lcd to 160dpi and clear cache but in a day or two you're back to where you started. the only long term fix for now is to go back to the old market and freeze or delete the updater. or at least until the old market becomes incompatible.
I know this sucks. why are we being CENSORED by google
I uninstalled market update then cleared cache and data, then in root explorer I deleted market updater.apk and now I have old market working just as it should. Thanks for the tip boxcar!
What am I doing wrong? I have cm7 on sandisk sd. Installed the latest nightly and installed gapp file for cm7. Installed lcd density changer app and set to 160. Force stopped market and deleted cache, but still not working right.
I don't understand how to set the market back to the old style.
kingston73 said:
What am I doing wrong? I have cm7 on sandisk sd. Installed the latest nightly and installed gapp file for cm7. Installed lcd density changer app and set to 160. Force stopped market and deleted cache, but still not working right.
I don't understand how to set the market back to the old style.
Click to expand...
Click to collapse
to get the old market back all you have to do is...
1) in settings / applications / manage applications / press all scroll down to market and uninstall updates.
2) with titanium you can freeze the market updater or with some kind of file manager app like astro or root explorer you can delete the updater. if you delete the updater and wish to get it back all you have to do is re-flash gapps
3) now you should have the old market back
4) enjoy
If I set my density to 160 or 240, then force stop & clear data in Market app (after reboot, before connecting to Market), the new market works fine for me. Works fine for many days at 240, seems to work for only a day or so at 160.
I change the density in build.prop using Root Explorer, so it stays that way every time I reboot. Running 177 from sd card.
If I also uninstall updates when I do the above, it reverts to the old market, and that works fine for a day or less.
If Google was really trying to prevent the Nook Colors from accessing the Market, they could probably figure out a more effective way to do it. I think this idea is paranoia, and the cause is just something weird in the rom's details. I could be wrong, though.
lynnji said:
If I set my density to 160 or 240, then force stop & clear data in Market app (after reboot, before connecting to Market), the new market works fine for me. Works fine for many days at 240, seems to work for only a day or so at 160.
I change the density in build.prop using Root Explorer, so it stays that way every time I reboot. Running 177 from sd card.
If I also uninstall updates when I do the above, it reverts to the old market, and that works fine for a day or less.
If Google was really trying to prevent the Nook Colors from accessing the Market, they could probably figure out a more effective way to do it. I think this idea is paranoia, and the cause is just something weird in the rom's details. I could be wrong, though.
Click to expand...
Click to collapse
How do you set the density to 160 or 240 or whatever? I downloaded the ROM toolbox, but I cannot find under which menu this lcd setting is?
Everybody is talking about setting the LCD density as if it is already taught at the kindergarden.
velizet said:
How do you set the density to 160 or 240 or whatever? I downloaded the ROM toolbox, but I cannot find under which menu this lcd setting is?
Everybody is talking about setting the LCD density as if it is already taught at the kindergarden.
Click to expand...
Click to collapse
Ha, that was my reaction too. I had to search a lot to find the procedure. The techies seem to assume that we all know this stuff, and have probably gotten tired of explaining it to every noob (understandable).
You can use the LCDDensity app, it's the easy way. You set the new density, it reboots into what you just set. However, reboots after that seem to go back to the default of 161.
I use the Root Explorer app, which allows you to go into build.prop and change the LCD density there.
Open Root Explorer.
Open 'system'.
At the top you need to change r/o, read only, to r/w, read/write, by pressing the box that says 'Mount R/W'. It'll change to 'Mount R/O'.
Long press 'build.prop'. Choose 'Open in Text Editor'
Scroll to line that says qemu.sf.lcd_density=161
Change 161 to 160 or 240, or whatever
Press menu>Save & Exit
Press 'Mount R/O' to change back to read only.
Voila.
I've had LCD Density at 240 for about 2 weeks now. No problems here with the market. =) Sometimes the apps dont show up in the list but you can still update them by manually searching, which subsequently adds the app to the list.
It's large, but surprisingly, I actually like the largeness.
PoisonWolf said:
I've had LCD Density at 240 for about 2 weeks now. No problems here with the market. =) Sometimes the apps dont show up in the list but you can still update them by manually searching, which subsequently adds the app to the list.
It's large, but surprisingly, I actually like the largeness.
Click to expand...
Click to collapse
The market seems to differentiate between tablet offerings at 160 and phone offerings at 240. In fact, on a freshly refreshed market at 160, you can find a category titled "editors picks for tablets" at the top. No such heading exists when the market is refreshed at 240. But even then, all previously downloaded apps can still be updated.
This is probably why you can't find some apps, but can still update them.
This seemed to work for me in Terminal Emulator:
1 su
2 pm disable com.android.vending.updater
If by chance things go wrong, you can just enable updating.
Axecaster said:
This seemed to work for me in Terminal Emulator:
1 su
2 pm disable com.android.vending.updater
If by chance things go wrong, you can just enable updating.
Click to expand...
Click to collapse
This does work pretty well, thanks
Sent from my NookColor using Tapatalk
Also the blade buddy app in the market has a tool to change LCD density and it holds after reboots.
Axecaster said:
This seemed to work for me in Terminal Emulator:
1 su
2 pm disable com.android.vending.updater
If by chance things go wrong, you can just enable updating.
Click to expand...
Click to collapse
Awesome! Doing that and then uninstalling the updates brought the old market back. Quick question, is this change persistant across reboots?
thereddog said:
I'm running CM7 nightlies on my Nook, just wondering what I need to do in order to get the market work the way it's supposed to. (Hidden download buttons, can't update apps, etc)
Click to expand...
Click to collapse
I had my Nook Color with 1.2 and 1.3 manually nooted go into endless boot cycles after a while because of the Market automatic updates.
I found that the automatic updates in Market screw up the latest manual nooter. Here's how I fixed the problem.
*IMPORTANT* You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
1. Wipe the device (8 failed boots) and clean the memory (press and hold n while booting and keeping the power key depressed).
2. Complete the B&N registration process.
3. Upgrade to the latest B&N firmware (I tried 1.2 manually)
4. Use CMW and manual nooter by following this http://forum.xda-developers.com/show...1054027&page=1 to root your Nook Color.
5. Use the Market to download Terminal Emulator (see https://market.android.com/details?i...roidterm&hl=en for details)
6. type
$ su -
# pm disable com.android.vending.updater
Check out
http://forum.oxygen.im/viewtopic.php?id=919 for more on this.
You have to do this before the Market first updates itself resulting in an endless boot cycle. This procedure will unfortunately also stop automatic updates to the Market. However, it also stops the Nook Color going into the endless boot cycle after the first Market update.
So you guys are telling me that you all will have to use the OLD MARKET for the rest of your life?
You guys not gonna tell me that you are waiting for the fix, aren't you?

[Q] Market 3.1.5 - app visibility

Hi guys,
I know this has been covered, but the info is rather fragmented and hard to follow for me.
I have a pretty fresh 1.3 rooted with MN (properly and working great).
I have the limited app visibility in Market (version 3.1.5). I have installed LCD Resolution, Root Explorer and LCDDensity. I've tried to tinker with the density in the LCD apps, but it seems my NC is already at 160.
I have looked at my build.prop file and I have the following lines that reference density.
# ro.sf.lcd_density=240
ro.sf.lcd_density.xdpi-169.33333
ro.sf.lcd_density.ydpi-169.33333
I would really like to get my market back so I can use this as a tablet.
Who can help me out with the steps? I'm not a super novice at this, but I'm not an 'expert' by any stretch.
Thanks
I have read numerous posts but have yet to find anyone with a rooted, stock 1.3 with a fully populated Market. At this point, I know of no known fix.
I am hoping that one of the developer types will take this issue on and find the key. My thinking is that now that there is a CM7 fix and fully working market with rooted, stock 1.2, that the answer is out there some where for a stock rooted 1.3.
I don't have a rooted NC but with my CM7 (nb200 or later), it set to 160 dpi by default.
All you have to do is clear Market (v3.1.5) data (not the cache, not the Market Updater) then get back in (sign in and re-accept their term).
That's it.
You should get fully functioning Market (Apps, Books, Games, Movies)
wonderbread51 said:
Hi guys,
I know this has been covered, but the info is rather fragmented and hard to follow for me.
I have a pretty fresh 1.3 rooted with MN (properly and working great).
I have the limited app visibility in Market (version 3.1.5). I have installed LCD Resolution, Root Explorer and LCDDensity. I've tried to tinker with the density in the LCD apps, but it seems my NC is already at 160.
I have looked at my build.prop file and I have the following lines that reference density.
# ro.sf.lcd_density=240
ro.sf.lcd_density.xdpi-169.33333
ro.sf.lcd_density.ydpi-169.33333
I would really like to get my market back so I can use this as a tablet.
Who can help me out with the steps? I'm not a super novice at this, but I'm not an 'expert' by any stretch.
Thanks
Click to expand...
Click to collapse
I just finished rooting a coworkers v1.3 Nook and have this same issue. There is about 95% market visibility. I have tried most everything imaginable (build prop edits, lcd density hacks, uninstalling the market update) and can't access that final 5%. This includes things like facebook, twitter and opera or dolphin browser to name a few. For now I have side loaded a few of these but it would be nice to have them in the market. Movies, books etc all show up fine. Its just this handful of apps that are a problem. I do not have this issue on my CM7 or v1.2 setups. Very frustrating.
1fzfe said:
I just finished rooting a coworkers v1.3 Nook and have this same issue. There is about 95% market visibility. I have tried most everything imaginable (build prop edits, lcd density hacks, uninstalling the market update) and can't access that final 5%. This includes things like facebook, twitter and opera or dolphin browser to name a few. For now I have side loaded a few of these but it would be nice to have them in the market. Movies, books etc all show up fine. Its just this handful of apps that are a problem. I do not have this issue on my CM7 or v1.2 setups. Very frustrating.
Click to expand...
Click to collapse
with the dpi at 160 my market 3.1.5 has been working fine. i can see all apps including facebook, twitter, opera and dolphin. have you try clearing market's data and cache? maybe this will help.
Are you running cm7 or 1.3? I tried clearing data / cache multiple times. I left the dpi at 160 for him. We will see if it populates appropriately over the weekend. I will check it again next week.
Sent from my CM7 NookColor using Tapatalk

[Q] Settings never save in many programs

Okay, bit of a weird one this. Several (and increasing numbers) of) programs never seem able to save any settings changes.
Every time they start, if they've been closed by the internal task manager, they'll show any initial splash screens and be using default settings.
It stated with jetvd, then Acontacts, zoom and even the internal bluetooth settings (loses paired devices and phone name).
Any ideas? Not sure if it's related, but the screen res seems screwy too. Zoom (custom widget designer) is all over the place, and launcher 7 sometimes displays icons too large for the screen when it starts up (variably so).
Currently running 9.6 darky rom, but happened with stock kernel too. Tried running permission fix from rom manager app, but nothing changed.
Getting rather irritating...
[ cruise / casual-tempest.net / xenogamous.com / quantum sufficit ]

resolution and market

i know this might have been posted yet but i haven't found anything about it...
i noticed that when you change the dpi on the tab, some apps in the market tend to tell you that you device is not compatible. any ideas on how to get by this? i mean i dig the wipping market and all then rebooting but it's kind of a hassle... any ideas?
You need to set your dpi to the values accepted by Market, i.e. 128, 160 or 240.

Categories

Resources