[APP][R][XPOSED] GravityBox v11.0.5 for Android 11 [08/08/2021]

[i5lee8bit]

I have been trying to figure out my camera issue for 2 days now and here you come along and solve it! Awesome!
I had a feeling it was edxposed and not magisk. Great find bro!

[At least on Pixel 4 and 4 XL:] Camera v8 doesn't work with EdXposed, unless blacklisted as of recently (same with Google Recorder app). Uninstalling updates reverted you back to v7.x, which works whether you blacklist camera app or not, and likely more the reason why it's working now. If you wanna try v8 camera (I actually think it brought very significant improvements this time around), try updating the app again now that you have the camera app blacklisted. Like I said before, same with the Google Recorder app. (Edit: whoops, I see that was already mentioned that you updated back to v8. I actually already posted about this a few pages back though, lol)

Edit:

Sorry for the noob question but where do u find option to blacklist apps in Edxposed? By the way if or when you blacklist the apps do you lose functions in GB 11 after reboot

Oh wow I'm sorry dude! This totally flew under my radar... You gotta go into EdXposed Manager settings and first enable app list mode. Then you can choose whether you want black or white list mode. See OP's first posts for more details on what is recommended to add for best compatibility with GB. And no, GB functions are not lost after blacklisting those apps (assuming you didn't blacklist something that OP specifically said you need whitelisted... obviously).

----------------------------------------------------

EDIT: I'm assuming this will eventually be brought up in this thread, so to save everyone some time, there is a new SafetyNet fix for now. Explanation copied and pasted from the Pixel 4 XL GPay thread, where I've cross-posted this. Hope yall don't mind, and this is useful for you guys:

YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Explained very well here, as to why it's failing again: https://github.com/ProtonAOSP/andro...mmit/15633a3d29bf727b83083f2c49d906c16527d389

tl;dr - even if BASIC hardware attestation is being reported, it is still actually running HARDWARE-based test, at least under the hood. Please go and thank the original creator of this method: https://github.com/kdrag0n/safetynet-fix, as well as where I found the original info: https://xdaforums.com/t/unable-to-pass-safetynet.4192073/post-84282209

The Github release files are just raw files in the zip, so you'll need to download, unzip, then rezip (without compression) into the proper Magisk file/folder structure.
For your convenience, I've also uploaded v1.2 of kdrag0n's Magisk module to AFH, already ready to be flashed in Magisk Manager: https://www.androidfilehost.com/?fid=17248734326145715249

kdrag0n already updated the module to support earlier versions of Android, plus some code changes to make it more reliable. Go get it from his Github; the .zip's are now flashable-ready! Here: https://github.com/kdrag0n/safetynet-fix/releases
I'm sending a donation over to him right now to show my appreciation... I hope others do the same!

Obviously flash at your own risk - it worked perfectly fine on my P4XL, on January 2021 patch, running latest Magisk 21.2, Riru Core 23.3, EdXposed (4655), etc.

 

[pa.pn2]

Quick info about EdXposed. If possible do not update beyond 0.5.1.4_4662.
4663 onwards might have some serious performance impacts.
More info here: https://github.com/ElderDrivers/EdX...16c0c0baeb08e1f5310d37#commitcomment-45769749

Is this problem still present in latest edxposed 4667?

 

[C3C076]

Is this problem still present in latest edxposed 4667?

I had a discussion and have to admit that performance impact is not that serious I thought might be. Problem about too chatty log that makes EdXposed log files grow in size still stays, though.

Following on this. I just sent a pull request against EdXposed repository which contains some optimizations for feature I was worrying could have some negative performance impact. Hopefully it gets merged.
Details here: https://github.com/ElderDrivers/EdXposed/pull/806

 

[C3C076]

EdXposed build 4668 with patch I mentioned in the previous post seems to be alive.

 

[AlDollaz]

Anyone having trouble keeping the clock and tiles settings to permanently stick? The clock setting will stick for a second, but if I pull the notification menu down, it'll go back to default. I'm also trying to get 7 quick tiles, but 6 only show.

Running Riru 23.3 and EdXposed 0.5.1.4_4668 and using a OnePlus 8.

(Apologies if this has already been answered)

 

[C3C076]

Anyone having trouble keeping the clock and tiles settings to permanently stick? The clock setting will stick for a second, but if I pull the notification menu down, it'll go back to default. I'm also trying to get 7 quick tiles, but 6 only show.

Running Riru 22.3 and EdXposed 0.5.1.4_4668 and using a OnePlus 8.

(Apologies if this has already been answered)

Oneplus compatibility is expected to be improved as soon as I have official android 11 update on my Op7Pro.

 

[pa.pn2]

Someone with pixel 4xl in here who can confirm that it's save to flash edxposed on it?
I don't want to risk a bootloop lol

 

[AlDollaz]

Someone with pixel 4xl in here who can confirm that it's save to flash edxposed on it?
I don't want to risk a bootloop lol

If you flash it with Magisk, you'll be fine.

 

[Pandemic]

Great job
Works fine on Xperia 1 with Android 11

 

[daddylonglegs]

How important is the whitelist thing? What does it do, help with battery life? Only asking because I also use MinMinGuard and they don't mention any whitelist info on their site and I don't want this breaking MinMinGuard.

 

[Pandemic]

@C3C076
Skip track for music aint work when screen is off and unplug turns on screen also not.. you will fix that ?

nvm its fixed.
Xperia 1 users need todo this to add to the whitelist and it works flawlesly:
- Android System (android)
- System UI (com.android.systemui)

 

[i5lee8bit]

@C3C076
Skip track for music aint work when screen is off and unplug turns on screen also not.. you will fix that ?

nvm its fixed.
Xperia 1 users need todo this to add to the whitelist and it works flawlesly:
- Android System (android)
- System UI (com.android.systemui)

From the OP:

Required whitelisted packages
In case you use blacklist/whitelist functionality of EdXposed make sure all the following packages are whitelisted (not blacklisted respectively) for full GravityBox experience.
- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)
- Phone (com.android.incallui) (OxygenOS only)
It is strongly recommended to use Whitelist functionality for better performance as EdXposed hooks only smaller amount of processes.
In case of running multiple Xposed modules consult their whitelist requirements with the devs of module.

It's mentioned in the first post. I would also make sure those other packages are whitelisted as well, if you haven't already.

 

[Pandemic]

From the OP:


It's mentioned in the first post. I would also make sure those other packages are whitelisted as well, if you haven't already.

Yes i readed that

 

[i5lee8bit]

Yes i readed that

Lol, well it's all good. I didn't even bother with White List mode before, as I''ve been using Black List mode. There were some VERY STRANGE instances to get some of my banking apps 100% working, where for some reason I needed to SPECIFICALLY Black List (but the default blacklisted status of being left alone on the White List for some reason never worked, freaking weird man) and/or add to Compatibility mode, or a combination of both or one or the other. TD Bank (which has since started working again), Chase app (Compatibility mode, if I want to be able to see bonus cash back offers section show up), and Wells Fargo app were among the weird ones.

Plus, along with a bunch of these banks finally updating their biometrics API integrations, it's also less annoying to need to WhiteList each app, one by one, that still need FingerFace to use Face Unlock. I'm now only down to 2 of them - PayPal (c'mon PayPal, seriously??? get with the times!!) and Capital One - yet Capital One's CreditWise app uses the new biometrics API while their main banking app still uses the old fingerprint API - really Capital One? Who's in charge of your mobile development team??

ANYWAY, with all that said I finally switched to White List mode. And along with that, I lost having the [volume key cursor control] mod working. So I did some quick investigating. C's source code for GB shows that the mod is tweaking the functionality of android.inputmethodservice.InputMethodService. So I took a quick look at the Android source: https://developer.android.com/reference/kotlin/android/inputmethodservice/InputMethodService. Which ultimately turned out to be a waste of time, because the solution was a lot simpler than that (at least the solution for me, and hopefully for everyone). At first, I tried to whitelist Input Devices (com.android.inputdevices), reboot, but it didn't work. I then tried to whitelist both Input Devices as well as Gboard, reboot again. Volume key cursor control worked immediately after reboot. It turns out com.android.inputdevices had nothing to do with it. Only the keyboard app being used (although I'm assuming - I don't use any other virtual keyboards on my phone) needs to be whitelisted for this option to work immediately upon reboot. Do note that removing Gboard from whitelist does not make the mod stop working (at least until reboot), nor does enabling the app in whitelist make the mod start working before rebooting (even if you toggle the setting on/off in GB). For those who don't know, it was a limitation in GravityBox [Q] that on some devices the option needed to be toggled off and back on to work, after reboots. The behavior seems to have changed in Android 11 - and furthermore it seems that the behavior is invoked upon sometime in the boot process. For whatever reason, the virtual keyboard app / input method targeted by the mod needs to be whitelisted and read by the EdXposed module during the boot process.

So, @C3C076, I believe the solution to:

Current issues
***
***
- Key actions: Volume key cursor control not working (most likely EdXposed related)
***
***
***

is to simply whitelist whatever your "input device" method (virtual keyboard app) is. In my case, whitelisting Gboard. I would assume if you have multiple keyboards installed, you would want to whitelist each one but I haven't tested this at all (see next post). Hopefully all this word barf helps you clear this particular issue out of your list. I dunno, maybe with your ninja coding magic skills you can come up with something more elegant, or something that better directly targets the issue.

PS: Pixel 4 XL on Android 11 (duh). Oh, and I can't liiiiiiive without my volume key cursor control baaaaeeeee~~~~!!!

 

[i5lee8bit]

Just tested on my Pie and Q devices - no more need to toggle off and back on after rebooting, in order to use volume key cursor control. Just needed to add Gboard to the whitelist. Interesting. Both devices (HTC U12+ stock Pie and Galaxy Tab S6 Lite with LOS 17.1 [Q]) now on EdXposed White List mode, and cursor control works immediately upon boot after adding Gboard to whitelist. Yes, I know LOS has the mod built-in, but I keep it default in LOS system settings and just use GravityBox.

My HTC U12+ also has TouchPal (HTC keyboard) installed - switching to this keyboard causes volume key cursor control to fail. Whitelisting TouchPal makes it work. So yeah, I would recommend whitelisting all of your keyboard apps!

 

[winjer]

Maybe I got misled by an independent variable, but...seems like it didn't work when I tried using Sandhook 4655, and started working when I switched to YAHFA 4655. Or maybe I was accidentally using the debug release and that was the problem? Pixel 4a, January image.

 

[C3C076]

So, @C3C076, I believe the solution to:

is to simply whitelist whatever your "input device" method (virtual keyboard app) is. In my case, whitelisting Gboard. I would assume if you have multiple keyboards installed, you would want to whitelist each one but I haven't tested this at all (see next post). Hopefully all this word barf helps you clear this particular issue out of your list. I dunno, maybe with your ninja coding magic skills you can come up with something more elegant, or something that better directly targets the issue.

PS: Pixel 4 XL on Android 11 (duh). Oh, and I can't liiiiiiive without my volume key cursor control baaaaeeeee~~~~!!!

Great find. Thanks for looking into it. What I was trying was that I disabled whitelist/blacklist feature completely just to see if the feature works or not. But it didn't. One would expect that it is the same situation as when you whitelist keyboard app just like you did. This is strange. For now I'll update the list of apps that need to be whitelisted for full support.

 

[MaXAiRO]

Great find. Thanks for looking into it. What I was trying was that I disabled whitelist/blacklist feature completely just to see if the feature works or not. But it didn't. One would expect that it is the same situation as when you whitelist keyboard app just like you did. This is strange. For now I'll update the list of apps that need to be whitelisted for full support.

Well, on GB 10.1.0 I also use that feature with SwiftKey which is already whitelisted / not blacklisted and the feature doesn't survive reboots. I have to disable it and enable it again to make it work.

 

[murti52]

Hi, @C3C076 I am getting this error on OP7 Open Beta 1 Oxygen OS 11. Never got it on Android 10. Can you help me out..?


Edit : saw the update in the play Store. Everything works fine. Strange it didn't auto updated it. Thanks anyways

 

[C3C076]

Well, on GB 10.1.0 I also use that feature with SwiftKey which is already whitelisted / not blacklisted and the feature doesn't survive reboots. I have to disable it and enable it again to make it work.

Which EdXposed are you using? If v0.4 consider updating to the latest v0.5.2 along with Riru v23