yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] eushaun99:
Seriously?? Just because you didn't get a reply after 40 mins you conclude that this is a dead thread? You do realise that everybody here have a life outside of xda and they DON'T work for you. Not to mention you didn't give any info about your problem.
[Xposed Framework Modules] arrtoodeetoo:
So, as I understand it, this will let me move the nav buttons to the corners, correct? I'm planning to upgrade my Nexus 10 to KitKat, but not many of the ROMs have the option (which SHOULD be an option in Android for tablets out of the factory, IMHO) and it would be nice to be able to use the ROM of my choice and still have the option to have the buttons where they should be for a 10in tablet.
[Xposed Framework Modules] 089man:
I give info about my problem yesterday. Read any post before, not before 40 minutes. Smile

Again

I used beanstalk rom, have installed v1 with tablet stile on settings screens. Now I have dual display in rom settings. Ok

Now if I open example from left the beanstalk settings or loockscreen or halo entry, than FC and rom settings closed. It's not open the menu right side. Works only with example, sound, display and any other...

Hope now you know what I mean...

I9100 Tapatalk 4, Rom1 Beanstalk 4.4. 2
[Xposed Framework Modules] eushaun99:
You mean tablet UI, which has only one bar at the bottom right? Then unfortunately in KitKat Google disabled that code so its impossible to switch to Tablet UI in 4.4.
[Xposed Framework Modules] dolorespark:
As you've noticed, the problem is with the ROM's extra settings screens and not with the standard ones. This is something I fixed but it's possible that your ROM "un-fixed" it.

As a "security" measure, Google added a new method in KK that the system calls before it displays a settings screen. It asks the app "is this a legitimate screen?". The app is supposed to override the built-in method and respond "yes" if the screen is OK. If the app answers "no", or if the app's author failed to override the method (causing the original version to be called), the app force-closes.

I discovered this when I installed CM 11 and got FCs for CM's screens but not for Google's (with one exception). The AOSP version has a list of legitimate screens that their override scans before answering "yes". If CM or Beanstalk or whatever were to add their screens to this list, there wouldn't be any problem. However they didn't - and even if they did, there are still a gazillion versions of these ROMs, and not all of them would pick up this change. So, I ended up overriding the whole thing and always answering "yes" to avoid problems like you're having.

Note that the problem does not occur when Settings is using the phone-style layout. From what I could tell, that method doesn't get called so it's not surprising that CM and others didn't identify the problem. In KK, the tablet-syle is explicitly disabled in the Settings app - possibly as a workaround for what sure seems like a bug.

You can confirm the nature of the problem by opening Settings, selecting a screen that FCs, then going to the Xposed Installer app. Select it's "View log" option: the should be an error message and a stack trace at the end of the log. If the message says something about failing to override some method, that's the problem. Feel free to post or PM the end of the log where it shows the error.
[Xposed Framework Modules] arrtoodeetoo:
No. I know that they completely killed Tablet UI in KK. I just want the buttons on the left side.
[Xposed Framework Modules] dolorespark:
That's strange because there was no difference in the code between v0.99 and v1.0 - I just changed the way I digitally sign the app.

The cause is unexpected but the results aren't. onIsMultiPane() tells the app whether it is set up for single pane (phone-style) or multi-pane (tablet style). When the Settings app starts up, Phab7 hooks this so it can return the layout you selected (the default response in KK is "single-pane"). Your Beanstalk ROM did something to this method (removed or modified it) so Xposed can't find it. Whenever Phab7 encounters this kind of error, it stops and doesn't try to hook anything else. Consequently, it doesn't hook the method that says "this settings screen is OK" - and since the AOSP knows nothing about these add-on screens, it says "not OK" and the app crashes.

Bottom line: your ROM is incompatible with the multi-pane (tablet-style) Settings option and only the Beanstalk ROM people can fix it.
[Xposed Framework Modules] arrtoodeetoo:
[MENTION=5094650]dolorespark[/MENTION]

I just tried this out on my Nexus7 (KitKat). Please consider adding an option to scoot the nav buttons from the middle to the left or right. That would be MUCH appreciated. Thanks.
[Xposed Framework Modules] reversegear:
Bug report

Having this status bar widening problem in tablet ui while toggling Expanded desktop

Normal Tablet UI

After Expanded Desktop Toggle
[Xposed Framework Modules] HellDiv3r:
Hi there

I'm getting force closes on systemui when attempting to pull down the notification drawer. Quicksettings works perfectly fine and the navigation bar too but when I pull down the notification drawer and let go (does not happen if i pull and down and back up again) systemui crashes.

I'm running stock KitKat 4.4.2 on a Moto G. I've already attempted to resolve this by disabling any xposed mods that may be interfering with Phab7 but to no avail.

Any possible fix for this?

Thanks :)

P.S. any chance for a phablet mode where the navigation bar stays on the right side of the screen?
[Xposed Framework Modules] haget83:
phablet mode (on my 10" tablet, 4.1.2 ) miss quicksetting menù :confused:
[Xposed Framework Modules] arrtoodeetoo:
Exactly what I'm asking for. [MENTION=5094650]dolorespark[/MENTION] should check out ThunderKat for a good example.
[Xposed Framework Modules] cashif:
Thanks so much, working fine in Ultra Z but have a request.. Somebody has already mentioned it, i've lost the transparency since enabling Tablet UI. Have tried making transparent with GravityBox/Xblast/Status Tinted bar but nothing doing. Can you please add an extra option to customize the Navigation/Status bars in your module itself. Thanks again for the GREAT WORK!!
[Xposed Framework Modules] dolorespark:
Phab7 is unlike most Xposed mods: it does not add or replace anything nor does it do any drawing or layout. It tells SystemUI that the screen is wider or narrower than it really is, then lets SystemUI take it from there.

If you don't like the result, it's because you don't like the way your ROM does things. That's where GravityBox and 100 other mods come in: they're purpose is to add stuff, move things around, etc. Phab7 doesn't do any of this to avoid duplicating features other mods do better and to avoid the conflicts that inevitably arise.

For the foreseeable future, I plan to focus on one thing: providing alternate UIs without causing FCs. Given the number of devices that have problems when switching away from their native mode, this should keep me busy for quite a while. :)

First, open the Xposed Installer app and select "Logs"; if you see any error messages, send me a copy via PM. If there's nothing wrong there, I have to ask for a logcat taken when the FC occurs. Zip it up and send it via PM.

Someone using the same tablet as mine reported having this problem. He ended up wiping his system, reinstalling, then restoring most of his data. That seemed a bit extreme to me but he's a flash-aholic so he didn't seem to mind. Instead, what I'd try is to boot into Recovery, delete the /data/data/com.android.systemui folder, then reboot. If your ROM isn't odex'd, you may also want to try deleting dalvik-cache while you're in Recovery, just in case.
[Xposed Framework Modules] dolorespark:
I looked at your logcat and found that your crash "can't happen". This makes it a bit more difficult to debug :) You're getting a null pointer exception in a method that doesn't get called if the pointer in question is null. Either your ROM's code is slightly different than the AOSP version or some other Xposed mod is messing around in the same area.

You said you disabled Xposed mods that might interfere, but did you disable all of them except Phab7? If you haven't done so already, could you try that, then reboot and retest? For that matter, have you confirmed that disabling only Phab7 fixes the problem? Also, does this occur when your phone is set to its native UI mode or just when you switch to a different one?
[Xposed Framework Modules] HellDiv3r:
I have retested by disabling all Xposed mods other than Phab7 and the force close still occurs (after reboot). The force closing only occurs when using the "Phablet mode", default and "Phone" both work without issue.

My Moto G is running stock Android 4.2.2 (German update) so no custom roms and no custom kernels either.
[Xposed Framework Modules] theoneofgod:
Moto G, 4.4.2, no other modules, on phablet mode, notification bar stays up top and the nav bar gets lob side, aligning to the right.
[Xposed Framework Modules] dolorespark:
Normally in phablet mode, the navbar stays at the bottom but yours moves to the right the same way it does in phone mode - is that correct? Another difference between the two is that phone mode has a single pulldown from the statusbar that can be toggled between Notifications and Quick Settings while phablet has what are clearly two separate pulldowns. What are you getting?

If you're getting the phablet-style pulldowns but the phone-style navbar, it means your vendor replaced the phablet layout file with the one used for phone mode. Sadly, there's nothing this version of Phab7 can do about that. However, if phone & phablet are actually identical then it's something I'd like to investigate.

As you may have seen, in the last few posts I've been working with a German user who also has a Moto G running 4.4.2. He doesn't report any navbar issues but does get a force close when he tries to pull down Notifications and leave it open. If you have the phablet-style Notifications, could you try duplicating that action? I'm guessing (hoping, really) that you won't have any problem leaving it open. Thanks.
[Xposed Framework Modules] theoneofgod:
Here is a few screenshots with phablet mode enabled.
[Xposed Framework Modules] dolorespark:
If I'm understanding your screenshots correctly, you also get an FC when you open the Notifications panel. I'd like to think this is a Moto G problem but I found their open-source Android code on SourceForge and it doesn't look like they touched SystemUI.

So, it's on to the next steps: could you or [MENTION=3273754]HellDiv3r[/MENTION] send me a copy of your SystemUI.apk and SystemUI.odex via PM? (I assume that if you're running stock, this is still odexed.) Then too, I'd also like to send one or both of you a test version of Phab7 which will print some debug messages into the Xposed log so I can figure out why the seemingly-impossible is happening. Let me know if you're willing to test this.

If anyone else is running 4.4.2, it would be helpful if you could see if you get FCs in Phablet mode when you open the Notifications panel. The FC only happens when it is at its "natural" size. Pull it down a bit too far, then release and let it roll back up to the point where it should stay open - that's when the FC happens.
[Xposed Framework Modules] HellDiv3r:
I've sent you the files through pm.

And yes, I'd be happy to help with testing :)
[Xposed Framework Modules] theoneofgod:
Sent. I'll happily test a test version.
[Xposed Framework Modules] dolorespark:
Sorry to take so long to get back to you but I had to go out of town for a funeral. Anyway...

I decompiled the files you sent me and found that Motorola made significant changes to the method where the crash occurs. I can locate where the null pointer exception happens but not why. Because the app was odexed, references to the variable that causes the problem have been optimized in a way that makes it hard to identify what it is. I have a few ideas for getting around this but it will take a few days before I have anything that's worth testing.
[Xposed Framework Modules] HellDiv3r:
Great to hear that you found something of interest, if you need anything else that I may be able to provide please let me know.
[Xposed Framework Modules] theoneofgod:
Thanks. Keep up the good work.
[Xposed Framework Modules] sfex3best:
I love this mod been using it for a while now. The only thing it's missing is the icon notification. For example if you receive a whatsapp message the green whatsapp icon will not appear at the bottom. If this is fixed it would be amazing. Thanks for the mod
[Xposed Framework Modules] satankid:
tried putting this on my i9500 gave system ui error.... running thunder rom 4.5 with xposed installed... all other xposed modules working fine... please help
[Xposed Framework Modules] revolt3421:
Its works good for me but... i got bug with the clock on status bar and when i pulled down notifications. Its looks like cutted in half. I change from tablet mode to phablet. I running on 4.1.1. Tablet: Prestigio Multireader PER 5274B.
[Xposed Framework Modules] dolorespark:
If that ROM doesn't contain the needed resources (icons, layout, etc), SystemUI will crash when you switch to a UI mode that requires them. If you use a ROM that includes them, it will work as expected.

I see the time but I don't see any statusbar - plus, the navigation bar looks too big to me. Go into the Phab7 app and try using the scaling adjustment - see how it looks at 85%, 75%, etc.
[Xposed Framework Modules] satankid:
can u suggest any ROM for this ... or can u include those items in the zip so that we can flash ... just a query
[Xposed Framework Modules] Mypp:
allwiner A10 CM9 unoficial 4.0.3

using the ro.sf.lcd_density=120

tablet looks like tablet :good:

Phab7 v1.00 works on switching UI from tablet to smartphone, but this mode I do not need.

using the ro.sf.lcd_density=160

tablet looks like smartphone and does not show a panel with buttons :mad:

Phab7 v1.00 does not work on switching from smartphone to tablet.

after selecting a mode "Tablet" nothing happens and occasional error UI

I want to use density 160 and tablet UI

I know that the desired mode is supported by firmware, because I can turn it on at a low density.
[Xposed Framework Modules] tatinek2:
It works well.

[ROM] [4.4.2] AOKP :: Kitkat
[Xposed Framework Modules] danielzyy:
Is there anyway to get the good old Tablet status bar & nav together (like PA used to offer) with this ?

PA 4.1 b2 over here
[Xposed Framework Modules] fnctopx:
hey

works well on my JIAYU G4 (4.2.1.)

thanks and keep up the good work :)
[Xposed Framework Modules] wuith:
Works great in 7" RK3066 Energy Sistem S7 Dual Tablet.

I tried and worked:

- Stock ROM with Tablet Ui. I could change well to PhoneUI

- CM10.1 RK3066 by Oma with PhabletUI. I could change well to PhoneUI. In this UI there are volume buttons in navbar and they are kept. Perfect!

I only had one problem with CM10.1. The navrings shortcuts are cut in PhoneUI landscape (horitzontal notification bar and vertical navbar). The navrings showed like if navbar would be horitzontal (up left and right left from middle navbar) so I can just see half of the navrings (up right is out of screen).

I can change the navrings shortcuts with Gravitybox and they work but then i get FC from systemUI. But maybe is incompatibility from Gravitybox and CM10.1. Do you know a solution for this?

It also worked for me to get bigger notification bar and bigger icons there (before with phabletUI the clock was too small). I changed the framework size with Phab7 and then make navbar smaller with Gravitybox.

Thanks a lot for this Xposed module. It is exactly what I was searching for!
[Xposed Framework Modules] tashik19:
please do something for kitkat. :(
[Xposed Framework Modules] Dovidhalevi:
OK, I am only using tablet mode for settings. This works 100% on 4.4.2.
[Xposed Framework Modules] ae4evr:
Hi, i use Phab7 on my tab. But it increase the size of notification panel and the other panel(it cover the whole screen).I use phone navigation bar. Please add an option to not increase the size of the panel. Thank you.
[Xposed Framework Modules] dolorespark:
This would not be possible without a HUGE amount of work. Tablet mode involved more than just alternate layouts and icons: there were thousands of lines of code to support it because it worked differently than Phone/Phablet mode. Google removed all of that, then rewrote and simplified the Phone/Phablet code. Consequently, you couldn't just add the old code back in because the interfaces the two shared no longer exist. Even if someone went to the effort of getting it all working, you'd end up with an outdated UI that didn't support Quick Settings tiles and other stuff. It doesn't sound like it's worth the effort.
[Xposed Framework Modules] bobsponge012:
not working

its not working in my android taler what to do
[Xposed Framework Modules] Android-xp:
Unfortunatly it didn't work on my offical AOSP 4.2.1 :/ (Can't see changes)
[Xposed Framework Modules] dolorespark:
The notification panel is supposed to fill the whole screen in Phone UI mode. Remember, it's designed for small screens. If it didn't fill the screen - especially in portrait orientation - the panel wouldn't be wide enough to display the entire message.

Honestly, these two reports are pretty useless because you didn't bother to identify what you had done to get it working. Did you install Xposed? Did you enable Phab7 on the 'Modules' screen in the Xposed Installer app? Did you remember to reboot after everything was installed and enabled? Please ensure you've performed these simple steps, then post again if it still "don't work".
[Xposed Framework Modules] Android-xp:
Sorry, was my mistake. FYI:

I just forgot to reboot :D now its working fine, but it got not such a good layout :)

Thanks for the information
[Xposed Framework Modules] ussl:
when i reboot my device i need to apply phab 7 again

how to slove it?

galaxy s 3 lte with any rom that i had
[Xposed Framework Modules] MarcAntonyy:
Heya dolorespark, I'm posting in reference to the Nexus 7 WiFi (nakasi).

I would just like to confirm that in order run stock Android w/ Xposed and have tablet UI work on the N7, I need to flash 4.3 (JWR66Y). Is that correct?

TY
[Xposed Framework Modules] macia10:
Hi,

On my tab it looks like on the screen. Is there any way to make it look normal? Im talking about dual pane settings on kitkat.
[Xposed Framework Modules] dolorespark:
Tablet UI should work with any version of Android from 4.0.1 through 4.3.x. It was completely removed from KitKat (4.4.x) by Google, so it won't work there. However, dual-pane settings still works in 4.4.x.

Phab7 just tells the system to use dual-pane mode - it doesn't tell it how to lay it out. You'd have to contact whomever built your version of Omni to find out why the left column doesn't adjust to the width of the screen.
[Xposed Framework Modules] macia10:
Hi are there any sourcess available? As I tried to make dual pane in our port of omni rom but it just does not work and with your module it does but everything is cut. I just dont know how it's enabled in kitkat.
[Xposed Framework Modules] DARTHVAPOR:
My nexus 5 says thank you.

Sent from Darth's free throat hug machine
[Xposed Framework Modules] syamkumar.tpl:
Is there any way to keep navigation keys on right side in tablet mode..??
[Xposed Framework Modules] wuith:
I think not or at least I did not find (not for tabletUI and neither for PhabletUi. You can get the navigation keys on right side only in PhoneUI.
[Xposed Framework Modules] syamkumar.tpl:
I mean navigation keys and status bar on same navigation bar that is old tablet ui

Navigation keys on left side and status like time WiFi battery on right side..

I want to swap these. So that I can have softkeys on right side of navigation bar...
[Xposed Framework Modules] cmoG530:
Having some issues with 4.4.3. It makes my UI restart a lot. Didn't have that issue in 4.4.2. Can anyone else confirm or deny?
[Xposed Framework Modules] jacomail95:
10 sec aren't enough to restart systemUI in 4.4.3 i confirm

Inviato dal mio Nexus 4 con Tapatalk 2
[Xposed Framework Modules] bb2htc:
SystemUI FC on Galaxy Mega 6.3 upon selecting any of the UIs. I'm on Stock Samsung ROM 4.2.2. Any pointers?

Tablet UI in setting works though.

I have rooted my phone and installed Xposed just for this :|
[Xposed Framework Modules] tristan21:
Android L

Does anyone know if Android L brought back tablet ui?

I want tablet ui on my LG G2 specifically to get my notifications on the bottom.

If Android L does not support that, is there a rom that will?
[Nexus 4 General] rey.ginete:
Im already running 4.4 and got this alert.
[Nexus 4 General] DirgeExtinction:
What build are you on?
[Nexus 4 General] rey.ginete:
KRT16O
[Nexus 4 General] DirgeExtinction:
Ah, then yeah. There is an update. To KRT16S
[Nexus 4 General] rey.ginete:
Didn't know that. haha Thanks!
[HTC Wildfire S] Ox3:
Hello,

I installed the touchwized version of the CM10.1 by cup_cake (http://xdaforums.com/showthread.php?t=2365885&page=11)

The ROM works great with the exception of the GPS which is now not working, if I use an app. to display the satellites available it will display 4 or 5 satellites but it will never get a fix.

Is there any way I can fix this?

Thanks,
[HTC Wildfire S] Ox3:
Can anybody help me with this please?.... :(
[HTC Wildfire S] sojusnik:
I'm experiencing the same!

GPS was working fine with CM 7.2, but after installing a new CM 10.1 ROM the GPS fix takes literally ages, if it works at all. The Galaxy Nexus, for comparison, finds enough satellites for a fix within seconds, when the latest stock ROM (4.2.1) is installed.

Any ideas where to start?
[HTC Wildfire S] Shisco:
I had the same issue on my Wildfire S running Owl Project's Jellybean CyanogenMod 10,1

(http://xdaforums.com/showthread.php?t=2283549)

GPS did not lock even after half an hour, it only drained battery. But I tried this thing:

(http://xdaforums.com/showthread.php?t=1447593)

One of these flashable ZIPs made the GPS find satellites. The coordinates it gives me are off about 200 kilometers from my actual location but at least it locked, at least there is some progress. I am still trying to figure out how to make GPS show me my actual location and not some asshole place I've never been to.

But some others said it worked like charm for them, maybe it will for you, too.
[HTC Wildfire S] sojusnik:
Hey Shisco!

Currently I'm using TopNTP (you can find it in the Play Store), an app from the thread opener of your link. It does the same as the zip files there, but gives you the option to adopt the gps.conf settings to your needs. Give it a try, because IMHO this app improves GPS a little bit.
[HTC Wildfire S] Shisco:
Okay, the problem just disappeared by itself :) When on the move, more satellites appeared and GPS coordinates were now exact. The patch worked in the end :) I just had to give it some time
[HTC Wildfire S] sojusnik:
Same here, but it sometimes sucks to wait that long. Under CM 7 the GPS fix was much faster.
[Galaxy S 4 Active Q&A, Help & Troubleshooting] hrtendrup:
Hi All,

I have rooted, installed safestrap, and flashed a rom slot with the google edition that was reported to work here. I flashed the MF3 master patch and also the active call recording patch to resolve a speakerphone issue (here).

Almost everything seems to be working fine but for 2 issues:

1. my camera's viewfinder is very grainy/pixelated when in video mode (this apparently isn't an issue on some other ROMs, more research on my part needed here)

2. when booted in the Google edition ROM, I can't get my computer to mount the file system via USB. Windows device manager indicates the device cannot start When I boot back into stock, it connects to my computer just fine.

I'm going to try to reflash this because when I originally installed this, I jumped the gun and rebooted before wiping dalvik, etc.

I'm also going to try reinstalling the drivers, but it works when I use the stock ROM, so I think drivers are fine.

Any other thoughts on this?