Related
This question is directed to anyone who knows the inner workings of the vending.apk and the android market itself. Through another post about density settings, it seems pretty apparent that, while having density set at 161 allows all the apps in the market to show up, there are still plenty of apps that won't actually RUN unless you are set at 160/159. So it turns into a Catch 22 situation. I know I have used device spoofing via an altered build.prop (or an apk that does the same) for getting apps to appear that are 'proprietary' to other, specific devices, but I'm wondering if it MIGHT be possible to spoof the market into reading our Nooks at being 161 devices, while we are actually at 160 while within our rom (I'm on CM7). This has probably been proposed somewhere else, but I couldn't locate a thread...Anyone have any input about this possibility? If something like this is NOT possible, please let the users know also, if you have a minute. Thanks for looking...(Idea..could we get a secondary "market161" .apk created that we could use indepedently of the one in the latest Gapps to achieve the desired effect?)
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
My Density is set at 200 and everything works just fine (including both Market and Maps).
Mine is set at 240 (need new glasses?) and everything seems to be ok
Trust me...there are enough that don't run at 200....otherwise I wouldn't have bothered posting. 160 seems to be magic for compatibility/scaling, and 160+X gets best market access.
Sent from my PC36100
ganovim said:
Mine is set at 240 (need new glasses?) and everything seems to be ok
Click to expand...
Click to collapse
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
Thanks...this is exactly what kind of info I needed...new project...sigh..will give it a shot after work tonight...Thanks.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
mazook98 said:
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Click to expand...
Click to collapse
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
It would be SO on....
Sent from my Nook Color (zoom2) using Tapatalk
mazook98 said:
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
Click to expand...
Click to collapse
It's a pain sometimes, since everything is buried under submenus. I don't think there's anything else comparable, though.
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
dalingrin said:
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
Click to expand...
Click to collapse
Thanks so much for saving me from making this a bigger issue than it is...I don't need " my apps " to populate since I'm tethered to my Evo about 95% of the time, where they naturally all populate ...I'll just bump it down to 160 permanently, and if ever it becomes something I absolutely need, Ill just bump it back....Thanks for all your amazing work..Donation on the way when I get home from work.
Sent from my PC36100
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
john10101 said:
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
Click to expand...
Click to collapse
There are just some apps that wont run / scale correctly unless its at 160... they will just hang and load 4 ever or force close unless they are set at 1 of the 3 native densities for android application development... at least that's what I can glean.. no difference though in appearance, unless you're a cyborg.
Sent from my PC36100
oh this is why my app list wouldnt populate. it doesnt bother me most of the time. everyone seems to have their dpi set for so low. i have mine at 132.33 if i remember it right. can't be any bigger than 140 for sure.
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
pxldtz said:
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
Click to expand...
Click to collapse
Here's one...Try "Fruit Slice" at 161....then try it at others if you want...then run it at 160.
Sent from my PC36100
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador
I used this app to set the pixel density at 170 on my tab 8.9
I think it looks awesome, give it a try.
(you need to be rooted, and I am using the latest overcome rom)
goenieg said:
I used this app to set the pixel density at 170 on my tab 8.9
I think it looks awesome, give it a try.
(you need to be rooted, and I am using the latest overcome rom)
Click to expand...
Click to collapse
Thanks for the sharing. I am considering to change the LCD density but not comfortable to root yet (still reading and learning....).
1) Can you help post the screenshot on home screen, app folder screen. If possible, can you install the CNN News and post this app home screen etc. Due to original 160 setting, the font on CNN News is extremely small.
2) Can you help posting the above with 240 setting.
3) Any problem install app thru market (i heard market can only install with 160 or 240 LCD)? Anyway I am prepared to reinstall the old mkt version as it does not has this limitation.
Sorry to trouble you and appreciate your helps and sharing.
Hi,
Rooting is actually quite easy. Give the link below a try, so you can see it for yourself
http://forum.xda-developers.com/showthread.php?t=1287205
goenieg said:
Hi,
Rooting is actually quite easy. Give the link below a try, so you can see it for yourself
http://forum.xda-developers.com/showthread.php?t=1287205
Click to expand...
Click to collapse
Been one of the more fast and easiest devices that I've rooted.
Sent from my Nexus S 4G using Tapatalk
goenieg said:
I used this app to set the pixel density at 170 on my tab 8.9
I think it looks awesome, give it a try.
(you need to be rooted, and I am using the latest overcome rom)
Click to expand...
Click to collapse
thanks for the app recommendation. But my tab went crazy after switching density. gmail force closed, calendar force closed... it because quite unstable. Reset back to default density, and removed program. All good again.
kernel 2.6.36.3_motley_v2+
android 3.2
Strange, did you set it to 170?
not sure if I can tell a difference.. icons seem to look larger on the screen...
market and apps will act up if you change density. switch back to the default values to fix this.
orlandoxpolice said:
market and apps will act up if you change density. switch back to the default values to fix this.
Click to expand...
Click to collapse
What is the default?
MagicMan3 said:
What is the default?
Click to expand...
Click to collapse
I believe it's 170, at least according to the specs listed at GSMArena.com.
I'm not sure I understand the advantage of doing this. My display looks beautiful as it is.
Now that we've got root (yay!)
The LCD density seems rather low- I'm coming from a Dell Streak 5, and it seems the icons and fonts are quite a bit larger.
I can't fit as much on the Note's home screen as I could on my Streak's homescreen, despite being both larger and higher resolution.
Which density settings are "safe" to try with minimum risk of causing market issues?
Interesting, most people lower the density. I have no idea what it is on the note now but 240 and 320 are safe
itsjusttim said:
Interesting, most people lower the density. I have no idea what it is on the note now but 240 and 320 are safe
Click to expand...
Click to collapse
Yeah, I know, it's odd.
My old Streak 5 would comfortably fit all the widgets I use and icons. The Note, however, despite having the same number of rows and columns defined, has overlap. Also, the BW clock skin I use has to be sized physically larger than it is on the Streak, otherwise it gets cut off. Fonts seem much larger, too.
Granted, it makes it easy to read, but I honestly expected MORE screen real estate- not less.
Note uses 320. I set mine to 240 and everything seems ok. The keyboard does still seem a bit large, but ok. Also the default browser is broken a bit as well as the phone app. Keypad is off and browser tab page is messed up along with address bar.
xzKinGzxBuRnzx said:
Note uses 320. I set mine to 240 and everything seems ok. The keyboard does still seem a bit large, but ok. Also the default browser is broken a bit as well as the phone app. Keypad is off and browser tab page is messed up along with address bar.
Click to expand...
Click to collapse
I've got mine at 280 now. Same dialer issue. Using Swype for input, so no issues there. I use Opera so the browser isn't an issue.
Haven't hit any market issues yet, but haven't tried downloading anything either.
whats the default value?
cmjkxa said:
whats the default value?
Click to expand...
Click to collapse
It's 320!!
cmjkxa said:
whats the default value?
Click to expand...
Click to collapse
320. Which I believe the largest common value supported by android.
thanks! I tried 240 and messed up the home screen.
Streak used a 160 setting, but it was only 800x480.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I'm going to just leave it at 320. I'd rather take the time to get used to it and have everything function properly.
Maroon Mushroom said:
I'm going to just leave it at 320. I'd rather take the time to get used to it and have everything function properly.
Click to expand...
Click to collapse
Good idea.
Im sure all the apps that break with the different density can be fixed using spare parts or installing modified ones. [There are many modified ones in the int Note forum]
The last days I was playing a little bit with the density on my phone. At first you want to know which ROM I'm using. > CM9 latest build. I would like to set my density to 178 or also to 170, these are densities, the phone can show without a blurred screen, or blurred icons. Everything works fine and looks bombastic! But the problem is, that the phone.apk keeps crashing.
Everything is working until a density of 190. Below this value, phone.apk crashes everytime you start a call, or are called.
I know this problem is not new, but other threads are not answered and very old.
So... Anyone knows, whats the problem? Why it is. And how we could fix it?
I will try to disable compatibility mode in spare parts, but I don't think that it will work.
Anyone knows a workaround or maybe has a modded phone apk for ics?
Thanks in Advance!
EDIT: As I thought, compatibility mode won't change anything.
Silberpfeil3110 said:
The last days I was playing a little bit with the density on my phone. At first you want to know which ROM I'm using. > CM9 latest build. I would like to set my density to 178 or also to 170, these are densities, the phone can show without a blurred screen, or blurred icons. Everything works fine and looks bombastic! But the problem is, that the phone.apk keeps crashing.
Everything is working until a density of 190. Below this value, phone.apk crashes everytime you start a call, or are called.
I know this problem is not new, but other threads are not answered and very old.
So... Anyone knows, whats the problem? Why it is. And how we could fix it?
I will try to disable compatibility mode in spare parts, but I don't think that it will work.
Anyone knows a workaround or maybe has a modded phone apk for ics?
Thanks in Advance!
EDIT: As I thought, compatibility mode won't change anything.
Click to expand...
Click to collapse
I don't know how to solve your problem man,but I suggest you give exDialer a go.It's as smooth,functional and cool-looking(even has an ICS theme available) as the ICS dialer.It'd make for a good alternative until you find the solution.
i'm using 185 on cm9 and phone.apk is working great for me.
Sent from my GT-I9100 using XDA
tolis626 said:
I don't know how to solve your problem man,but I suggest you give exDialer a go.It's as smooth,functional and cool-looking(even has an ICS theme available) as the ICS dialer.It'd make for a good alternative until you find the solution.
Click to expand...
Click to collapse
The problem is that it isn't the dialer that crashes, but InCallScreen. exDialer still uses the default InCallScreen, so it still crashes.
supermult said:
i'm using 185 on cm9 and phone.apk is working great for me.
Click to expand...
Click to collapse
I believe it breaks once you go below 182. If you were to drop your density to 180, you'd see the crashes, too.
hi,
i read very often about reducing density from twohundred and xxx to one hundred and xxx.
but nobody explained, whats the advantage of reducing this.
can somebody explain to me please?
regards - sui
As everything's a bit smaller, more stuff fits on the screen.
its a problem which isnt even fixd in the latest cm9 build so no, wait for fix!
But when everything is smaller, the widgets wont fit on the homescreen... ?
... sent by my SGS2 tapatalked ...