[PATCH] True Tablet UI (Apps+GUI) w/o DPI Change for Stock & CM10 - Update Oct11

---

Recent Changes
10/11 - Updating CM10 nightly links - see next post
9/6 - Added nighly CM10 builds - see next post
8/1 - Cleaning to OP out a bit

Downloads
If you don't care about all the technical stuff, skip down to post 2 for downloads

Intro
Goal of thread is to share details around how the trigger for Phone UI/Phablet UI/Tablet UI works, and provide a dpi independent patch for tablet ui. Hopefully this also eliminates the misinformation that changing lcd density is the only way to get Tablet UI.

What's "true" tablet UI vs what is called tablet UI in many roms? The Tablet UI actually defines how some apps work (e.g. dual-paned settings like in the screenshots below) vs the other solutions that simply draw the standard Nexus UI with tablet navigation/system bars.

The 'Triggers'
In 4.1.x, there are two files that need to be modified:
PhoneWindowManager.java, located in frameworks/base/policy/src/com/android/internal/policy/impl contains the code that determines which UI to present. During compile this is a part of android.policy.jar
WindowManagerService.java, located in frameworks/base/services/java/com/android/server/wm contains code that specifies the lowest DP settings and has the system select from either sw600 or sw720 presentations. It is a part of services.jar

PhoneWindowManager
Click below for details regarding the source code to edit, and modifications for these releases

 

The source code calculates a value for shortSizeDP, and compares it to

• shortSizeDP < 600 = PhoneUI
• 601<shortSizeDP < 719 = PhabletUI (Phone/Tablet - ie what we have as stock)
• shortSizeDP > 720

shortSizeDP is calculated as follows:
take the short size of the screen resolution (our screen is 1280x800, so use 800) * DENSITY_DEFAULT (a constant of 160) * LCD Density (ro.sf.lcd_density value in build.prop)

example: on stock: 800 (N7 short resolution) * 160 / 213 (stock lcd_density) = 600.9
since 600.9 > 600 but less than 719, we get Phablet UI

using 170 as ro.sf.lcd_density: 800 * 160 / 170 = 752.9
since 752 > 720 we get Tablet UI

this explains why the threshold on our device is between 177 and 178

original source code:

        // SystemUI (status bar) layout policy
        int shortSizeDp = shortSize
                * DisplayMetrics.DENSITY_DEFAULT
                / DisplayMetrics.DENSITY_DEVICE;

        if (shortSizeDp < 600) {
            // 0-599dp: "phone" UI with a separate status & navigation bar
            mHasSystemNavBar = false;
            mNavigationBarCanMove = true;
        } else if (shortSizeDp < 720) {
            // 600-719dp: "phone" UI with modifications for larger screens
            mHasSystemNavBar = false;
            mNavigationBarCanMove = false;
        } else {
            // 720dp: "tablet" UI with a single combined status & navigation bar
            mHasSystemNavBar = true;
            mNavigationBarCanMove = false;
        }
        }

Modification
Given the code above, there should be many programmatic ways to force TabletUI:
Editing the values of 600 or 719, removing the Phablet UI mid section, or just commentting everything out and set mHasSystemNavBar = true; mNavigationBarCanMove = false;...and plenty of other options

Current Alphas are hardcoded to

mHasSystemNavBar = true;
mNavigationBarCanMove = false;

WindowsManagerService
Click below for details regarding the source code to edit, and modifications for these releases

 

Changing the values above we enough to try and force the UI to use tablet features, but since the Nexus 7 uses tvdpi (same as google TV when displaying 720p) with a fallback to xhdpi, SystemUI did not contain the requisite framework files (xml and pngs) and was force closing. Further, the sizing was mapped to the sw600 folders, which do not contain any of the tablet pngs/xmls.

Thus, we needed to edit the code that defined what the minimum screen size was to force apps to show in tablet form.

original source code:

private void computeSizeRangesAndScreenLayout(boolean rotated, int dw, int dh,
            float density, Configuration outConfig) {
        // We need to determine the smallest width that will occur under normal
        // operation.  To this, start with the base screen size and compute the
        // width under the different possible rotations.  We need to un-rotate
        // the current screen dimensions before doing this.
        int unrotDw, unrotDh;
        if (rotated) {
            unrotDw = dh;
            unrotDh = dw;
        } else {
            unrotDw = dw;
            unrotDh = dh;
        }
        mSmallestDisplayWidth = 1<<30;
        mSmallestDisplayHeight = 1<<30;
        mLargestDisplayWidth = 0;
        mLargestDisplayHeight = 0;
        adjustDisplaySizeRanges(Surface.ROTATION_0, unrotDw, unrotDh);
        adjustDisplaySizeRanges(Surface.ROTATION_90, unrotDh, unrotDw);
        adjustDisplaySizeRanges(Surface.ROTATION_180, unrotDw, unrotDh);
        adjustDisplaySizeRanges(Surface.ROTATION_270, unrotDh, unrotDw);
        int sl = Configuration.SCREENLAYOUT_SIZE_XLARGE
                | Configuration.SCREENLAYOUT_LONG_YES;
        sl = reduceConfigLayout(sl, Surface.ROTATION_0, density, unrotDw, unrotDh);
        sl = reduceConfigLayout(sl, Surface.ROTATION_90, density, unrotDh, unrotDw);
        sl = reduceConfigLayout(sl, Surface.ROTATION_180, density, unrotDw, unrotDh);
        sl = reduceConfigLayout(sl, Surface.ROTATION_270, density, unrotDh, unrotDw);
        outConfig.smallestScreenWidthDp = (int)(mSmallestDisplayWidth / density);
        outConfig.screenLayout = sl;
    }

Modification
To work around this, in Alpha 1 we hardcoded WindowManagerService.java to force a Widthdp of 721 rather than 600, forcing the UI to use the sw720 folders from frameworks/base rather than sw600.

outConfig.smallestScreenWidthDp=721

Downloads

---

An now on to the part folks care about, please read the below in full

Credits:
I want to thank +aaronpoweruser, +lithium76, +cdesai for all their help and coding guidance; +Racer Of All for the zips; +the3dman for the Launcher2 fix, +z1gackly and +Nark.GA60 for their help with the CM10 patch, +Rsotbiemrptson for the odexed version

Disclaimer: I am not responsible for damaging your brand new nexus 7. Do not do this if you're not willing to brick it. Usage of the following files can cause a rift in the time-space continuum, the appearance of 20 foot android monsters in your town, turn your first-born into slime, change the gender of your significant other, tsunamis on mars, etc etc etc

Pre-requisites:
1. This is designed for Stock or AOSP JRO03D or Based CM10 (tested on Sep 6 nightly). Many folks are trying other roms that will either not boot or work. Please use the search above for your rom name before posting. Note: My development will focus on a patch to AOSP. I'm more than willing to work with devs on their roms, but the information above should suffice for them to bake the tweaks in however they want to.
2. You SHOULD BE DEODEXED. If you don't know what that means, then you likely aren't - so run a deodexer like mine or do it yourself . Update: Sept 7 - Rsotbiemrptson released a odexed version post 514
3. You MUST WIPE CACHE AND DALVIK. Formatting system and data/factory reset is not needed

READ BEFORE FLASHING List of Issues / Add Bug Reports:
Please report your issue here with all the information above.
https://docs.google.com/spreadsheet/...lNFVzFYR29CQkE

Latest Downloads:
10/11 - CM10 Nightly - credits z1gackly and Nark.GA60 post 534
Download: goo.im

8/1 - Alpha 3 for STOCK ROM JRO03D: fixed launcher (patch Launcher2.apk), adds lockscreen rotation (patch framework-res.apk)
Download: Mirror 1 Mirror 2
Alpha3 creates a backup during install, restore using the following script: Mirror 1
Issues Resolved: Patched Launcher has huge borders on bottom/top fixed
Note: these new changes will likely cause compatibility issues with CM/AOKP roms and customized roms. Alpha 1 may be better for you

Reporting Issues:
Many people are not fully reporting problems. If I don't have enough details, then it's very hard or impossible to help.
Please provide:
Rom: (e.g. Stock version JRO03D, JRO03H, j5, etc) - this is found in system/about tablet
Kernel: stock or modified - this is found in system/about tablet (you will know if you modified it)
Issue Description: Exact issue, exact error message, steps to replicate, screenshot (power + vol down at same time) for visual issues. Words like 'many', 'a lot', 'often' are not helpful. If there were a lot of issues then it wouldn't have been released. If you are on another rom/kernel, please verify that any play store issues are not sourced by that rom/kernel combo first without the mod.
Bootloops, Crashes: I *need* a logcat - see my signature

Next Steps:
- Settings toggle (WIP)
- Hybrid UI (stock UI in portratit, tablet in landscape)

Prior Versions:

 

7/26 - Alpha 2 - thank you +Racer Of All
Download: Mirror 1 Mirror 2
MD5: 1c85cc5fe772f687ce9beaa8dab57130
Issues Resolved: credit the3dman - Stock launcher width is too long due to mods and cause overscan of ~half icon on either side. Use Apex, Nova, Go Launcher.

7/21 - Alpha 1 released - thank you again +Racer Of All
Download: Mirror 1 Mirror 2
MD5: dbf20c71544dc19ac87c5d59a03c6f12

Alpha 1 does make a backup of your original files, if something goes wrong, flash the zip below to restore the files:
Mirror 1 Mirror 2

Screenshots

I hope someone runs with this. I'm running a tablet ui JB rom on my Fire and love it but I didn't want to screw around with dpi changes on the N7 that make everything smaller and bork the market.

just run the nova launcher

Originally Posted by patterone

just run the nova launcher

Launchers allow homescreen rotation, which is NOT the same as tablet ui.

Originally Posted by patterone

just run the nova launcher

tablet ui is more than just a launcher or rotation...it changes how apps interact with the system, e.g. dual-pane in settings

Originally Posted by neilrl79

I hope someone runs with this. I'm running a tablet ui JB rom on my Fire and love it but I didn't want to screw around with dpi changes on the N7 that make everything smaller and bork the market.

no clue where you heard it borks the market.. i am running 160 dpi and everything is perfect. 10x better than having a 7 inch galaxy nexus.

Originally Posted by oasis9389

no clue where you heard it borks the market.. i am running 160 dpi and everything is perfect. 10x better than having a 7 inch galaxy nexus.

Every thread that discusses dpi change to allow tablet ui also has people posting how some apps begin to show as incompatible after the change, that, imo,borks the market.

Would love to have a notification bar like the tablets do, the one they have now is ok, but I like the other one way better. Tried 160 DPI but it did not look good to me.

Holy cow what a stupid way for Google to determine which UI to display. Fixed:

 
       // SystemUI (status bar) layout policy

        if (layoutType == 1) {
            mHasSystemNavBar = false;
            mNavigationBarCanMove = true;
        } else if (layoutType == 2) {
            mHasSystemNavBar = false;
            mNavigationBarCanMove = false;
        } else {
            mHasSystemNavBar = true;
            mNavigationBarCanMove = false;
        }

The alternative would be "screenSize"

Manipulating values, multiplying by meaningless constants and using values that are derivatives of the number that actually matters? Google's code was just stupid. Write the code so developers can tell it what they want, not so it enforces your recommended layout.