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

Search This thread
By:
Advanced…
neilrl79

neilrl79

Senior Member
Aug 15, 2010
816
222
Maryland
barrmulio said:
depends on what your definition of 'soon' is....i can say we're getting closer
we can both boot, but it's force closing system ui, ending up with no bar at all at this point :D

looking through some solutions on the KF dev forum, it may be more than one file that needs changing
Click to expand...
Click to collapse

There is a guy named lithium76 over there you should talk to.
 
barrmulio

barrmulio

Senior Member
Oct 5, 2010
357
359
neilrl79 said:
There is a guy named lithium76 over there you should talk to.
Click to expand...
Click to collapse

been digging through his git all day :) ... just dropped him a pm as well

the sgt7 rom has tablet mode as well, but i was spend too much time trying to track it down

based on what i can see from lithium76/0xD34D, he make edits to 3 other java files, including systemui, for that commit
 
K

kind3rgarten

Senior Member
Mar 17, 2011
96
13
Texas
philwaud said:
As in:

Display mode
- phone UI
- phablet UI
- tablet UI

Just tick and it sets it - surely thats the way to go?
Click to expand...
Click to collapse

Are you even reading the thread?

Sorry, but that's what they have been trying to do all thread long. They are trying to write a sort of switch that will use an integer value to determine what UI should be implemented. They are trying to implement the switch using that code, among other code, I guess. To 'just use check boxes' would be like building a house and just nailing on a plastic light switch without hooking any electricity up to it and expecting it to turn on the light in your room.

Sent from my Galaxy Nexus using xda premium
 
Last edited:
  • Like
Reactions: Saint Wacko and TedT100
barrmulio

barrmulio

Senior Member
Oct 5, 2010
357
359
S

spiff72

Senior Member
Apr 14, 2006
482
40
So will this likely be a patch to the current "stock" ROM, or will it be an entirely new ROM (built from the source)? Just curious!

I am excited to try this out. I tried the DPI change, but everything just got to small (the nav buttons, text, etc).

Thanks!
 
Q

qoncept

Senior Member
Feb 1, 2010
239
38
kind3rgarten said:
Are you even reading the thread?

Sorry, but that's what they have been trying to do all thread long. They are trying to write a sort of switch that will use an integer value to determine what UI should be implemented. They are trying to implement the switch using that code, among other code, I guess. To 'just use check boxes' would be like building a house and just nailing on a plastic light switch without hooking any electricity up to it and expecting it to turn on the light in your room.
Click to expand...
Click to collapse
This guy is describing what he thinks the UI element should look like, not saying he thinks that's all that needs to be done. Relax and save the ridiculously exaggerated similes.
 
barrmulio

barrmulio

Senior Member
Oct 5, 2010
357
359
spiff72 said:
So will this likely be a patch to the current "stock" ROM, or will it be an entirely new ROM (built from the source)? Just curious!

I am excited to try this out. I tried the DPI change, but everything just got to small (the nav buttons, text, etc).

Thanks!
Click to expand...
Click to collapse

it'll probably be both

if the patches above work, we (either I or if someone beats me to it) should release a flashable mod to just patch a deodexed stock rom first (i released a deodexer yesterday), and then we can tackle odexed stock

pretty soon devs will be releasing roms, like the sgt7 enhancements that +cdesai mentioned, that already contain the tablet ui patch and more - it's actually pretty crazy to think that the kindle fire got jb + these enhancements before many folks even got a N7 in their hands

my hope for this thread was to steer discussion around a solution for getting tablet ui and bring some dev talent to help solve the problem...seems like we're very close and i'm grateful for everyone who provided feedback and assistance to get us to where we are
 
K

kind3rgarten

Senior Member
Mar 17, 2011
96
13
Texas
qoncept said:
This guy is describing what he thinks the UI element should look like, not saying he thinks that's all that needs to be done. Relax and save the ridiculously exaggerated similes.
Click to expand...
Click to collapse

le sigh.
Another person that doesn't know what they're talking about.
That was not what he was saying. He responded to some underlying code and said "you're thinking too much, how about just some checkboxes" so no, that wasn't what he was saying.
And two, the analogy was in no way exaggerated, it was spot on.
To just add a UI menu without coding anything would be like nailing a switch onto the wall in your room without hooking any electricity up to.
I can't see how that's an "exaggerated similies."
Its called an analogy by the way.

Sent from my Nexus 7 using xda premium
 
K

kind3rgarten

Senior Member
Mar 17, 2011
96
13
Texas
barrmulio said:
it'll probably be both

if the patches above work, we (either I or if someone beats me to it) should release a flashable mod to just patch a deodexed stock rom first (i released a deodexer yesterday), and then we can tackle odexed stock

pretty soon devs will be releasing roms, like the sgt7 enhancements that +cdesai mentioned, that already contain the tablet ui patch and more - it's actually pretty crazy to think that the kindle fire got jb + these enhancements before many folks even got a N7 in their hands

my hope for this thread was to steer discussion around a solution for getting tablet ui and bring some dev talent to help solve the problem...seems like we're very close and i'm grateful for everyone who provided feedback and assistance to get us to where we are
Click to expand...
Click to collapse

So it will just be a flashable zip or are you going to modify the stock rom and just include this in a whole separate rom?

EDIT: nvm. Lol

Sent from my Nexus 7 using xda premium
 
M

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
Is the git from cdesai above the same project or is that just a pointer from someone working on a similar project?

It looks like the distribution method is up in the air, but I have a framework that could probably port the changes over other ROMs for the Nexus. It would just depend on what changes are included in your code.

If you have AOSP or CM10 with only the WindowManagerEdits (or, at least only edits related to UI changes) then we could likely put together a patch that could made into a flashable zip and applied over most ROMs for the Nexus 7 (at worst, we would need one patch set for AOSP, CM10, and possibly AOKP, if the demand necessitates it.)

Then users could just flash a zip with the UI changes applied, thereby having the UI choice in any ROM of their choice.

You can see the framework in the link on my sig. Works pretty well.

I ported Paranoid Android to Nook Color, and I am working on creating a patch set to apply PA to the Nook's nightlies. It is difficult since PA is closed source at the moment. But your project should be very doable, should you want to investigate this manner of distribution.

With PA, there are a bunch of changes that are device-specific, which limits the portablilty. We'll have to see what you come up with here, but since Nexus 7 has such a large user base, device-specific patches have a lot of value.
 
You must log in or register to reply here.

Similar threads

jamesst20
[ROM] [Nov 1][4.3.1][SmoothROM v5.3]Smoothest ROM-Deodex-Zipalign-Tablet UI-Stable
Replies
6K
Views
1M
zgreddo
zgreddo
AndDiSa
[ROM][NZH54D][2024/03/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP
Replies
5K
Views
1M
T
terho
A
[ROM][7.1.2_r24][UNOFFICIAL][grouper] LineageOS 14.1 for Nexus 7 2012
Replies
1K
Views
497K
V
Vrpghm
timmytim
[ROM][PORT][4.8.22]MIUI Tablet Edition for Grouper | KitKat
Replies
519
Views
239K
bogo69
bogo69
z1gackly
[ROM] [KANG] CM10 with Tablet UI
Replies
338
Views
77K
NoobNeutralizer
NoobNeutralizer

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 151
    barrmulio
    barrmulio
    [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

    The source code calculates a value for shortSizeDP, and compares it to
    • shortSizeDP < 600 = PhoneUI
    • 601 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:
    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
    Code: 
    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:
    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
    View
    59
    barrmulio
    barrmulio
    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:
    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
    2CpJE.png
    j47r7.png
    Ggbbs.png

    jLRI7.png

    pfChC.png
    View
    39
    Rsotbiemrptson
    Rsotbiemrptson
    Patch for 4.2 Stock Odex

    Here is a patch for 4.2 stock odex and deodexed, plus ones to revert. This doesn't include a modded launcher.

    Rsotbiemrptson
    View
    31
    Rsotbiemrptson
    Rsotbiemrptson
    Zips for stock 4.1.1

    Hello,
    I would like to say thanks for your work, it has brought my N7 much needed changes. I had to modify the files as I am still running stock 4.1.1(JRO03D odexed). I have it working for non deodexed roms incase anyone that hasn't flashed a custom rom wants to try it. I have also uploaded a zip to revert back to stock just incase. Both can be flashed through recovery, wipe cach and dalvik after flashing.

    TabletUI
    https://www.dropbox.com/s/e63uj4l2tynfrfc/TabletUI.zip?m
    StockUI
    https://www.dropbox.com/s/27btzfayophnd9h/StockUI.zip?m

    Rsotbiemrptson
    View
    15
    Rsotbiemrptson
    Rsotbiemrptson
    4.2.1 Patches

    Hello,
    Here are the patches for 4.2.1.

    Rsotbiemrptson
    View

New posts