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

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

Note: I am no longer maintaining releases due to time constraints. If someone would like to pick up the op, please pm me.

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

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

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/ccc?key=0Aq1C5kjO0c_tdDFrbWVsOF9ROXJOblNFVzFYR29CQkE

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:

Screenshots

patterone said:

just run the nova launcher

Click to expand...

Click to collapse

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

guys - kindly keep all lcd_density dpi discussion, complaints and issues to the existing threads in Q&A or general, so this thread can focus on code change development...the whole point of this thread is to offer an alternative to that already...thanks!

qoncept said:

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

Code:

       // 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.

Click to expand...

Click to collapse

that's the direction i was thinking as well - define a new global variable, and let devs build a toggle to set it into the settings (for user selection) or as a constant (if they just want their rom one way)

bsw11 said:

If I was to make the change myself, can someone tell me what app(s) to use and just where framework folder is located? It does not seem to be in / using ES File Exp.

Click to expand...

Click to collapse

java file edits are made before they are compiled into files our phones/tablets use, there are plenty of great threads out there on building android

update on development

my nexus doesn't like the the android.policy.odex that i'm compiling from aosp, even without any changes to any of the files from the repo...it will just stay on the nexus X boot screen (after the Google bootloader) until i copy the original android.policy.odex back and then it finishes booting up within a few seconds

if anyone has succesfully built a mod or otapackage from aosp for grouper (i've been using full_grouper-eng), let me know if there were any special settings for compiling that are needed to get it to boot