[Q] Metro UI on lower resolution - Windows 8 General

Hi Folks,
As all of you know is, the Metro UI wont start an App when its on lower then 1024*768.. (My AT Tab = 1200*600)
Now i noticed that an already started instance of a Metro App CAN be started in 1200*600 and is also fully functional..
Could one of you by any chance have a solution for always enabling the Apps in 1200*600

I guess we will have patches and hacks like that when W8 gets released. But currently It's not worth, so for testing you can still use increasing resolution trock.

I was able to set the resolution on my Acer Aspire One netbook to 1024*700 by changing a line in the registry to allow the pixels to be squished together.
Basically it's going to look bad, but it's usable, and you can change your clear type settings to make it a bit more readable afterwords as well.
Sent from my T-Mobile G2 using XDA App

I think this is the key you are talking about. Enabling downscaling will allow you to set 1024*768:
-Change displ key for Metro UI: hklm\system\currentcontrolset\control\class\(4d36e968-e325-11ce-bfc1-08002be10318}\0000\Display1_Downscalingsupported to 1
-reboot
-set display to 1024x768

Related

dell streak icons size

size of streak icons.... is there any way to make them bigger?
Sent from my Dell Streak 2.2 using XDA App
Totally agree... why aren't they proportionate to the screen
They're smaller cuz of the lower dpi (160)
if it were set higher (which you can do buy editing the build.prop) it would just be like any other device stretched out.
By having the lower dpi the space on the screen is used better and more icons/lists/etc can be displayed
also if you want you can download adw launcher from market and adjust how many icons you want on the homescreen thus making them bigger or smaller to your liking.
head over to the android developer page to find out more at http://developer.android.com/guide/practices/screens_support.html
Where is the settting in the build.prop file. I dont see it
fone_fanatic said:
They're smaller cuz of the lower dpi (160)
if it were set higher (which you can do buy editing the build.prop) it would just be like any other device stretched out.
By having the lower dpi the space on the screen is used better and more icons/lists/etc can be displayed
also if you want you can download adw launcher from market and adjust how many icons you want on the homescreen thus making them bigger or smaller to your liking.
head over to the android developer page to find out more at http://developer.android.com/guide/practices/screens_support.html
Click to expand...
Click to collapse
Sent from my Dell Streak using Tapatalk
carhigh said:
Where is the settting in the build.prop file. I dont see it
Click to expand...
Click to collapse
Code:
ro.sf.lcd_density=160
change it to 240, thats what the EVO and most other devices with 4.x screens are set to.
Be careful when editing the file, as everything goes, i/we/us are not responsible if you brick your device.
fone_fanatic said:
Code:
ro.sf.lcd_density=160
change it to 240, thats what the EVO and most other devices with 4.x screens are set to.
Be careful when editing the file, as everything goes, i/we/us are not responsible if you brick your device.
Click to expand...
Click to collapse
My build.prop doesnt have it, weird. I even pulled a copy to the pc and searched it. root/system/build.prop, right?
So thats probably why lcd density changer didnt/doesnt work either. The icon sizes are fine for me with the stock launcher, but i installed launcher pro and the icons get even smaller. i just reset my phone cause ive done so much crap to it the last couple days. I still havent found out what way to use it that i can live with
Anybody have a solution to this, yet?
The official 2.2 build does not have this line in the build.prop
I also don't have that option in my build.prop
I'm on the 12821 Build, if that helps anyone.
try desktop visualizer, up to 4 x 4
or buy new glasses?
You can add it in your build prop file. I did mine today and worked. It was suggested in another thread. Let me see if I can find it
http://forum.xda-developers.com/showthread.php?t=874610
If u are rooted, try the LCD density app on the market
Sent from my Dell Streak using XDA App
PS: Yes, you can just add it.
It works fine and will make the adjustment. I'm having no issues with a dpi of 200 except for it cutting off names a bit short on the bottom with an incoming phone call. Rotating to portrait solves the issue just fine. It doesn't hinder performance, but somtimes can make it a bit tough to read who is calling you.
ADW.Launcher EX was just recently released ($3.28) which allows you to increase the size of the icons. It does a ton of new, really cool features. Here's a quick video explaining few of the app's features:
http://www.androidpolice.com/2010/1...eleased-transitions-to-a-whole-new-dimension/
Hope this helps.
This is the form that is the best way for increase the lcd dendity a 200

Has any one tried LCDdensity

Just wondering if any owners tried changing the density manually or with lcddensity. Wondering if touchwiz recognize any change in the density. Would love to change this to 200
Will definitely be playing around with the density when I receive mine.
I'm just curious as to what changing the density actually does. Since obviously you can't physically change the screen density, what is the advantage of tricking the phone into thinking it's different via software?
AXIS of Reality said:
I'm just curious as to what changing the density actually does. Since obviously you can't physically change the screen density, what is the advantage of tricking the phone into thinking it's different via software?
Click to expand...
Click to collapse
check this video out.
http://www.youtube.com/watch?v=9yrOAJJK-GY
Usually changing the density makes the screen look more high res by making everything smaller and fitting more information on the screen. If your still using your galaxy s try out lcddensity and change to 200. Touchwiz on 1st galaxy s didnt adjust well to changing the density. default is using 240
Was the first thing i did. Set mine to 202 out if habbit, as most devices get issues with wonky UIs at 200 or below.
Device looks great on 202. The only thing that distorts slight is the quick access tools ( sound and screen rotation only) in the notification bar.
The posituve outweighs the nefative for me.
Sent from my GT-I9100 using XDA App
risq said:
Was the first thing i did. Set mine to 202 out if habbit, as most devices get issues with wonky UIs at 200 or below.
Device looks great on 202. The only thing that distorts slight is the quick access tools ( sound and screen rotation only) in the notification bar.
The posituve outweighs the nefative for me.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
can you take a screen shot? im wondering what the app menu looks like.
+1 for screenshot. I run my DHD at 190. I use LCD Density Changer which has a compatibility mode to make problem apps run full screen, but it needs root

[Q] Phone UI at 160 dpi? (CM9)

So, today I decided to test my nook at 240 dpi, now that we can do that without a patch (huge thanks to leapinlar). Overall, I really liked the phone UI with the status bar being at the top and the soft keys at the bottom. My main issue is that all the apps (i.e. GMail, etc) show up in phone mode, which I believe is a waste of screen real estate (although it makes sense with everything being bigger and all).
What I'm wondering if there's any way to have the phone UI (i.e. status bar at top, nav keys at bottom) at 160 dpi, so the apps still show up in the tablet layout.
Does anyone know anything about how to go about doing this?
(I already know that the screen dpi is what defines whether the device considers itself a tablet or a phone (160+ means phone, 160 or less means tablet). Based on this information, I don't think it's possible, but I thought I'd ask anyway.)
It's not possible. The system automatically decides based on dpi. You can set it to 161 and it will be phone. However, each app decides for itself whether to display itself in phone gui or tablet gui. I have seen apps still display in phone even if the nook was in tablet and vice versa. They do their own calculations based on the dpi and other factors. Also some apps come in two versions, a tablet version and a phone version. So you can try 161 or there abouts and see how the apps respond. Be warned though that setting to a non standard dpi (120, 160, or 240) may make Market/Play Store not show all apps. I guess you could set to a standard setting temporarily to make market work right and then once your new app is installed, set it back.
I figured as much. Thanks!
On true ICS compatable devices there is also a setting in build.prop called ro.build.characteristics that can be set =tablet... I don't know if it is enabled in our builds or not.

accidentally found dpi change on stock 7.0 rom

So I have been having issues with apps, crashing, compatibility and seems to revolve around the text size inside display options. But having poked into developer options I have got something that gives me the cool custom ROM DPI change. Ok so here it is.
Go developer options.
Smallest width, will be 411 change to 510.
Images here so you can see the change.
I'm going to use 510 for a while. I know there's an option in display where you can change text size, but turns out it makes some of the apps I use just crash out when i launch. This however allows me to have both
I've been using 484 with no problem.
Sent from my Nexus 6P using Tapatalk

Have You Changed Smallest Width In Developer Options?

I have mine set to 525 dp. I prefer having really small icons and text. Most of all I like forcing the tabbed UI in Firefox. I haven't noticed any real disadvantages.
I am curious to know what settings you all use besides the default one.
Yes. Using 702 dp
Is there a standard set of sizes that can be used that don't cause any display abnormalities? I see 525 and 702 and that I'm running 454 as per smallest OOS visibility setting. These seem like random setting but I'm sure they aren't.
Funkameleon5 said:
Is there a standard set of sizes that can be used that don't cause any display abnormalities? I see 525 and 702 and that I'm running 454 as per smallest OOS visibility setting. These seem like random setting but I'm sure they aren't.
Click to expand...
Click to collapse
600 seems to be the point where it reads as a tablet, as Chrome starts to have tabs at that setting. There are some other settings the device doesn't seem to like and will jump to the next highest number it likes. Example: setting it to 598, will automatically make it set to 600. Did not notice any abnormalities other than icon placement, which can be adjusted.
I messed with it the other day and my launcher wasn't changing. Anyone else have that issue?
Sent from my ONEPLUS A6013 using Tapatalk
I have mine at 550. I can't stand the default ones.
crzycrkr said:
I messed with it the other day and my launcher wasn't changing. Anyone else have that issue?
Click to expand...
Click to collapse
You need to run a 3rd party launcher
That sucks. Thanks for confirming that for me
SirBindy said:
You need to run a 3rd party launcher
Click to expand...
Click to collapse
Sent from my ONEPLUS A6013 using Tapatalk
I use increments of 10 for some unknown reason, currently running 514p
I just changed display size to smallest option in display settings, and I prefer that
phr0zen said:
600 seems to be the point where it reads as a tablet, as Chrome starts to have tabs at that setting. There are some other settings the device doesn't seem to like and will jump to the next highest number it likes. Example: setting it to 598, will automatically make it set to 600. Did not notice any abnormalities other than icon placement, which can be adjusted.
Click to expand...
Click to collapse
Spotify calls my 6T as tablet even in smallest delault size. So I guess evvery app has their own definition of when a mobile becomes tablet.
phr0zen said:
600 seems to be the point where it reads as a tablet, as Chrome starts to have tabs at that setting. There are some other settings the device doesn't seem to like and will jump to the next highest number it likes. Example: setting it to 598, will automatically make it set to 600. Did not notice any abnormalities other than icon placement, which can be adjusted.
Click to expand...
Click to collapse
I always used to set my phones to tablet mode, but at the moment it seems to break Google lens so I've had to set it just below. I don't really like the full width notification shade and lockscreen notifications, and miss chrome tabs.
Also, how does it affect the status bar \ notch?
it's dpi and screen ratio the wm command is easy way or get app that changes it
I use 600 in developer settings, font smallest, and screen smallest... I still have the original swype apk and prefer the 'tablet' version of the keyboard. This, and the fact i have a lot more 'real estate' are the primary reasons I set it to 'phablet' mode.
i mistakenly increased it to 600 and my device isnt working
I have changed it to 1200 and now pocof1 cannot load anything. Is there a fix to this?
hi can someone help me I recently changed mine by accident and i put it to 200 and now my tablet is on black screen if i hold the power button i can see the options to power off restart and lock it , i restarted it multiple time and power it off and on multiple times too . can someone help me

Categories

Resources