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
Changing DPI gives us some @#$%^&**( in mind. because some other apps are misbehaving and not working.
the question is can we have this app http://www.xda-developers.com/android/per-app-dpi-adjustment-for-the-galaxy-note-2/
BUT it is only available for galaxy note 2. yes a smart tablet. not a phone. can someone got this working on our devices, changing the dpi on build.prop automatically during opening an app then restarting the whole framework while opening the app.
EDIT: (someone used it on an s2 and it's working) there's still hope =')
zenesis said:
Changing DPI gives us some @#$%^&**( in mind. because some other apps are misbehaving and not working.
the question is can we have this app http://www.xda-developers.com/android/per-app-dpi-adjustment-for-the-galaxy-note-2/
BUT it is only available for galaxy note 2. yes a smart tablet. not a phone. can someone got this working on our devices, changing the dpi on build.prop automatically during opening an app then restarting the whole framework while opening the app.
EDIT: (someone used it on an s2 and it's working) there's still hope =')
Click to expand...
Click to collapse
Need android 4.0 +
Why editing build.prop restarts your framework?
Use apps like "lcd density " & "lcd resolution " its easier :beer:
This is Jay-z-s
[update-02/21/2013]
Although changing the "garmin pilot" dpi settings did nothing but make things smaller in the app, changing the "Android System" dpi setting to 240 or lower will force the program to run as a tablet instead of the crippled phone version. Not sure if this is the same for other apps as well but I figured I would put this out there for others with the same issue.
[update-02/21/2013]
I rooted my note 2 hoping to use garmin pilot in tablet mode. I installed Jelly 'Beans' - Build 9 [02/12/13] and also Xposed framework so I can change DPI settings. However this program seems unaffected by a simple dpi change. If there is any way to hack this one program to force it to install as a tablet I would be grateful.
djpurpose said:
I rooted my note 2 hoping to use garmin pilot in tablet mode. I installed Jelly 'Beans' - Build 9 [02/12/13] and also Xposed framework so I can change DPI settings. However this program seems unaffected by a simple dpi change. If there is any way to hack this one program to force it to install as a tablet I would be grateful.
Click to expand...
Click to collapse
I haven't ever had the framework not show some difference, usually it just screws up the layout if it isn't going to work.
Do you have the app settings module active in the xposed installer app?
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
AldenIsRad said:
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
Click to expand...
Click to collapse
Can anyone help please
AldenIsRad said:
Can anyone help please
Click to expand...
Click to collapse
Honestly I never could get certain system apps to set correct dpi using touchwiz. If i remember correctly the phone dpi was the big issue for me. I didn't play around with it 2 much. It was one of the reasons I switched to aosp so i'm able to set the dpi to 240 and everything works correctly.
I'm pretty sure when you set it to tablet apk it doesn't really do anything unless there is a seperate apk for tablet settings. I remember this from a few files I extracted from Moon ROM.
Some apps can't run in lower DPIs and will fc. It also sounds like if you have the tablet option, you may have an outdated version of xposed app dpi settings. The newer one doesn't have a tab for tablet vs non tablet.
AldenIsRad said:
Ok so I was running per app dpi settings and it works perfectly for non system apps. Although, when i try to set tablet mode for settings, it will Force Close. Is there any way around this?
Click to expand...
Click to collapse
Maybe im not understanding. When you say tablet mode is that simply a dpi and res that makes setting look like on a tablet or are you running a module that does this and then you have to manually adjust the setting dpi to get it to work?
At one point when I was using the tablet mod (not the flashable one) my setting fc'd. Im not sure which might work for your case, but I might try setting the dpi you think is supposed to work then reboot. Maybe it needs a reboot after each change. (or again im not sure your situation- make a save copy of system settings app, reinstall it and make sure you change it to have the same permissions as all other sysyem apps. This would be if say you had a mod on for tablet mode and now settings was fc)
Coming from N5, I've played around a lot with the DPI settings, to find the perfect spot (361).
Can you also change the DPI settings on the Z2? N5 has it via editing the build.prop but don't know how Sony does this. I'm yet to receive the phone (on Tuesday) but wanna know in advance.
You can simply edit the build.props to change the dpi
Something to know about xperias is they are extremly close to AOSP with the way the firmware works
Its how xperia FWs are, they are very light
Sent from my D6503 using XDA Premium 4 mobile app
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Oh, it's pretty much the same? Good news then!
On my N5, I use 361 due to issues that 360 causes with some apps, and hoping to do the same on soon-to-be-mine Z2, since it was the perfect spot. But if that won't work, and 370 works (as per above post), that's great! Cheers guys.
BanziBaby said:
I used DPI Changer
Click to expand...
Click to collapse
Thanks man, this works wonders!
BanziBaby said:
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Click to expand...
Click to collapse
I'm trying to figure out why DPI Changer doesn't work for me. I also tried Texdroider, which I previously used on an LG G2 with success. Both apps appear to go through the motions, but when I apply the changes and reboot, nothing is changed.
I'm running a D6503 rooted .402, locked boot loader and I installed SuperSU from the Play Store. Running Root Checker confirms I am rooted.
I'm hoping to be able to set the DPI so it can match the look and feel of the Z Ultra
Thanks in advance for any help!
Hadn't thought of changing DPI in quite a while, actually since my Xperia Z. I'm too going to play around with DPI till I find something a bit smaller but then again not too small. I've always thought that the interface had gotten unnecessarily big after the Xperia T.
Edit: Anyone happen to notice what the original DPI value was on the Z2? I changed mine a little too quick..
If anyone likes the ZU the exact DPI is 320
For Z2 Tablet it is 140
And for default it is 480
Sent from my D6503 using XDA Premium 4 mobile app
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
BanziBaby said:
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
Click to expand...
Click to collapse
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
sensei_sai said:
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
Click to expand...
Click to collapse
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
orbitalcomp said:
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
Click to expand...
Click to collapse
When changing DPI to 320 all apps load into phablet mode (aka ZU size) and some which dont support phablet load into tablet size
In other words... No problem
Sent from my D6503 using XDA Premium 4 mobile app
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
lyubor said:
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
Click to expand...
Click to collapse
with which DPI? If I remenber well I had the same until I switched to 320 DPI, which is just perfect.
With everything I randomly tried around 400. Rebooted twice after applying 320 and it actually worked!
Ended up using the DPI Changer app, since editing the build.prop directly didn't seem to work after multiple reboots, but 361 is doing the job so far.
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
orbitalcomp said:
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
Click to expand...
Click to collapse
Can confirm that also on Z3 is 320DPI for Home launcher just amazing
Xperia Z2 dpi change
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
pulizpunk said:
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
Click to expand...
Click to collapse
You need to reboot after editing.
Sent from my Sony D6503 using XDA Labs