Related
Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?
Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?
Set dpi to 240, install apps and then set dpi back to desired custom dpi
For me it happens also with old market app.
Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App
App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)
Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.
I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.
doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)
You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Thanks for the heads-up - I had no idea it would have been from the DPI setting.
It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck
Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.
thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!
Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100
when I connect my laptop to my TV through HDMI for the 1st time it automatically connects to a certain resolution. and that's fine because then I can select a different resolution if I don't like it. for example if my laptop connects automatically to [email protected] which is my TV maximum resolution then I can change it to... let's say [email protected] which is lower quality but is waaaay smoother 60 Hz is smoother than 24Hz.
ok, my question is... how can I change the output resolution of Note3's. I haven't seen a menu yet allowing you to do that. I'd rather have [email protected] or even [email protected] instead of [email protected] which is so laggy. and don't tell me the Note3 can't connect to a different resolution than 1080p because it obviously can. I've connected it to another tv and on that one it connects at [email protected] and also I can't change the resolution to that one.
is there a workaround that you can do to allow selecting other resolution than the default one?
.....
and it's funny because both Note 1 and 2 connect on my TV automatically at [email protected] and as a consequence they show no lagginess while my Note3 which was supposed to be an upgrade is in this case a downgrade...
Sent from my SM-N9005 using xda app-developers app
!!WARNING!! Not my fault if you need to reflash. You're doing this on your OWN ACCORD!
Use a third-party launcher as TouchWizHome likes to crash. Open terminal if it's rooted (will only be able to change resolution with root) and use these commands:
NOTE: Do not use quotation marks when typing in terminal.
Resolution: Type "su", grant root, type "wm size 1080x1920" if you want 1080p, or 720x1280 if you want 720p
4.3 and 4.4 use "wm". Earlier versions of android use "am". Tablets are reversed and should need "1920x1080" as opposed to phones which needs "1080x1920".
PROTIP!!! This may mess with your Note 3 and you might have to reflash. Samsungs framework is NOT dynamic like Googles framework is. This might result in corrupted apps. If you want to change DPI without an app (AppSettings with Xposed works fine and lets you do it to individual apps) just change "size" for "density" and "1080x1920" for "480". 480 is default, so lower it to see how small you want things to be. 360 is the sweet spot for me.
ok... any other idea? I don't want to change the resolution of the launcher but the resolution of the output. I presume that method might change both and also requires root. I don't want to root it. any other suggestions?
Sent from my SM-N9005 using xda app-developers app
Please remember that questions and troubleshooting posts go in the Q&A/Troubleshooting section.
Thread moved.
Sent from my SM-N900T using Tapatalk
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
rchrdcrg said:
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
Click to expand...
Click to collapse
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Andy4Shurr said:
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Click to expand...
Click to collapse
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
rchrdcrg said:
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
Click to expand...
Click to collapse
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Andy4Shurr said:
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Click to expand...
Click to collapse
Yeah, I "borrowed" a Chromecast from Best Buy and could never get screen casting to work. You might want to see if changing the resolution fixes this issue with Miracast as well... I have a suspicion it will, and that might be useful to some folks. I sure wish I knew how to force the HDMI output to 1080p; it switches over when playing a 1080p video, so I know it's possible, but I don't know enough about development stuff to know how it's doing that, and forcing the resolution to 1080x1920 with the "wm size" command just displays a 1080p picture downscaled to 720p.
try vlc beta off the play store
here's a sort of rant and with a video playback only solution. Not sure how to hide the rant part. I don't forum anything much.
I bought a Belkin miracast adapter off amazon, and have had trouble getting videos playing properly in full screen. It would mirror the 1280x800 with videos played with regular video apps ( MX player, Archos player, stock) which would be 16:10, and would have those bars on either side on both my 1080p insignia tv and our pseudo 720p panasonic (actual res was 1024x768, but at 16:9, which should be illegal to market as a hdtv). I know from previous experience with my galaxy s4, which the samsung video app would mirror only the video at the correct tv resolution, leaving the phone as the remote. You could also use other apps while any video was playing through the samsung watchon (video) app. So randomly downloaded the vlc beta off the play store. It works for the tegra note 7 the same way samsung set up theirs, minus the multitasking(so far). It took me weeks on and off being frustrated with apps that wouldn't recognise that mirroring was enabled to take advantage of the external display. It's kinda whatever now seeing how much time I spent trying to get the video to play properly by itself, for my s4 I tried mhl cables, chromecast, dlna. this works a lot better
So if you just want videos to play, use the vlc player beta. you can use miracast or hdmi. works the same with both. Only if I could miracast surround sound. that would be nice.
I've just started using my tablet and a HDMI cable to run XBMC. This tip has saved me much frustration.
I already use Tasker which can send terminal commands as an action to make it easier. Tasker does have a HDMI plugged state which should allow this to be automated but for some reason tasker doesn't seem to detect it, not sure why yet.
So I've been fiddling a bit more to optimiser the HDMI experience. I've discovered an app called second screen that let's you sert display profiles and launch then the HDMI is plugged in. Thee app sets the size, resolution, dims the screen and force closes the UI to make sure the new settings actually come into effect. It will also revert the changes when the cable is removed. Does need to run on a rooted device but mine is already.
When it comes to screen Sony definitely tops the list above other manufacturers but our Xperia Z5 Premium doesn't always use 4K HD Resolution Screen, only when watching 4k video or things right? so why not to make it work in always 4K mode? more pixels- more fun
Warning: Note that on high brightness battery usage will be much more than 1080p screen mode
it requires Rooted device also
1.Download Terminal Emulator from play store
2. open app and write "su" without quotes
3. give it root access and write " wm size 2160×3840 " also without quotes
Screen will became "ugly", to fix it now type "wm density 820" also without quotes. after that all should work fine, play any video and you'll notice color changes and much More improvements, however there's always a way back to 1080p
to do it
wm size 1080×1920
wm density 420
Don't forget to click Thanks Button
感谢楼主的分享，支持楼主！
Just thank you! It gave it a different and nice appearance but I noted two things. First the phone works a little slower and the other thing is when I tried to make a call the caller interface didn’t open so I was not able to make the normal functions like turning off the microphone, hanging up the call, etc. Unfortunately I had to put it back to 1080p.
you don't need root for this, you can do it with adb command though a pc without root
"adb shell wm size 2160×3840"
"adb shell wm density 820"
cheers
Elfmirth said:
you don't need root for this, you can do it with adb command though a pc without root
"adb shell wm size 2160×3840"
"adb shell wm density 820"
cheers
Click to expand...
Click to collapse
its really good
Zur75 said:
Just thank you! It gave it a different and nice appearance but I noted two things. First the phone works a little slower and the other thing is when I tried to make a call the caller interface didn’t open so I was not able to make the normal functions like turning off the microphone, hanging up the call, etc. Unfortunately I had to put it back to 1080p.
Click to expand...
Click to collapse
Is there any way to solve the problem for now?
HD2killers said:
Is there any way to solve the problem for now?
Click to expand...
Click to collapse
Hi Guys! I know you have lurking about that unutilized 4k screen of our phone, Why not enjoy "1440x2560" density of 534 works perfectly fine the only down side are glitchy looking start-up since it was designed to in 1080p and multi tasking has no thumbnails on it about it looks and feels good!
Just do
adb shell wm size 1440x2560
adb shell wm density 534 <-----------IMO this is the density, fonts looks smaller but legible.
ENJOY!
"You can do the same also on your Z1, Z2, Z3, Z4 Tablet, Z5, Z5 Compact ..... and on your crapold device, because this is not changing the display resolution
Seriously guys..... this is changing the resolution of the VIRTUAL display (not the physical one), so like this you are getting 4k emulation on 1080p physical resolution.
To change the physical display resolution you need to do "quite a few more steps", which cannot be done in a simple way like this (and surely not without root).
Moreover, even if -- yes, there is a way -- it's not doable on stock ROMs, as it misses the required implementation.
I am almost done here so, on Open Devices, you will be able to get real [email protected] whenever you want."
Copied from this discussion...
I wana buy Xperia Z5 Premium only for VR to watch 4K videos. Is still good? Can I play UHD 180° videos smooth, without any reboot with this mod?
hi does anyone have issues taking screenshots with these settings enabled? every screen shot says error app does not allow?
crusader0071 said:
hi does anyone have issues taking screenshots with these settings enabled? every screen shot says error app does not allow?
Click to expand...
Click to collapse
I try resurrection os but disabled
One of the best things about Android Wear is the possibility to install phone apk's made for phones on the watch. The problem is that every apk i install keeps the original resolution and i can't make anything on it.
Is it possible to reduce the app or change anything on the screen to be able to see the whole app screen? I remember watching some videos on youtube where people installed clash royale on some android watches and the game was 100% visible.
I found this thread but i couldn't test yet.
https://forum.xda-developers.com/android/apps-games/app-screen-shift-change-screen-t3138718
Thanks and sorry for my bad english.
I tested it and it's possible to use the "wm density" on latest Wear OS. It's however global setting and it's not possible (AFAIK) to set it per app.
moneytoo said:
I tested it and it's possible to use the "wm density" on latest Wear OS. It's however global setting and it's not possible (AFAIK) to set it per app.
Click to expand...
Click to collapse
Very useful information.
Thank you!