beta 4 working with sandhook 4.6 only issue is ambient display had issue at first i turned it off the edge i think. on OnePlus 7 pro os 10.0.1 thanks for the work
Attachments
-
168.8 KB Views: 772
Please, can you be more specific?The one thing though, turning off the ability to reoot on the locksreen gives my phone fits with 10.0.1.
What issue? Please, describe. I have Ambient Display turned on on my OP7Pro running OOS 10.0.1 and haven't noticed anything strange about it.beta 4 working with sandhook 4.6 only issue is ambient display had issue at first i turned it off the edge i think. on OnePlus 7 pro os 10.0.1 thanks for the work
No issues on both devices running Android 10 I currently have, but this reminds me of some EdXposed ART crashes related to status bar clock some people were experiencing, even on Pie.There's a problem with date format on the status bar's clock: I can't see the date, the month or the day of the week. Only the hour
Edit: 5 minutes after reboot, the date automatically appears on the status bar...I don't know why
Log taken during such bootloop would definitely give answers.Latest beta works just great with sandhook but it seems it doesn't get along with xposed edge, it just bootloops, anyone here has gravity box and xposed edge working at the same time? If so, would you mind sharing your exact setup?
I also have a pixel 2 xl on latest Android 10. I am running Magisk 20, Riru 19.5, EdXposed 0.4.6.0(yahfa) with GB . Occasionally, I get a soft boot after booting up but after it has completed everything runs smoothly with no issues.Hi,
I have a Pixel 2 XL and I'm wondering if EdXposed and the latest beta version of GB are stable for everyday use?
I also have the busybox, active edge, joypixels, Viper4android and YouTube Vanced Magisk modules installed. I'm still on Pie for now.
Can someone with the same setup on Q chime in please? Thanks!
If the device is turning off, that's probably a missing or corrupt boot image not a GB issue. If you have TWRP installed, boot in to recovery, then advanced and fix boot. If GB really is conflicting with something else on your device, boot in to recovery, then advanced and file manager to delete GB from data/app/After enable and reboot gb beta 4 my phone just powers off after boot. I'm on magisk 20 Riru 19.5 Ed exposed yafy 4.5 pixel dust for taimen. What kind of logs are needed
I'm having same issueOnePlus 5
Android 10 nitrogen OS
Phone does not complete proper boot with gravitybox enabled.
Phone seems to boot but screen is all black, when I hold the power button a garbled version of my reboot options are shown. (The normal ones from within the ROM not bootloader or recovery)
Leafing me to believe it's some sort of formatting or display issue?
I then must uninstall Xposed in order to boot properly.
Any ideas or anything I should try?
different device, but similar setup.. soft boot after booting up (not always) but after it has completed everything runs smoothly with no issues...pixel 2 xl on latest Android 10... running Magisk 20, Riru 19.5, EdXposed 0.4.6.0(yahfa) with GB... soft boot after booting up but after it has completed everything runs smoothly with no issues....
Which version of Edxposed are you using? You need to have one of these installed. I personally am using YAHFA from (2)I'm having same issue
I've tried both from (1). Neither boot up properly. (That is they both boot but once gravity box module is enabled they don't boot properly)Which version of Edxposed are you using? You need to have one of these installed. I personally am using YAHFA from (2)
(1) https://github.com/ElderDrivers/EdXposed/pull/354
(2) https://forum.xda-developers.com/showpost.php?p=80392829&postcount=30
The only other suggestion I can come up with is to enter recovery and delete data/adb/modules/riru-edxposed/post-fs-data.sh ....Others have had success with this after boot issues.I've tried both from (1). Neither boot up properly. (That is they both boot but once gravity box module is enabled they don't boot properly)
Guess I'll try the yahfa 0.4.6 from (2) ?
Yes I've done this.The only other suggestion I can come up with is to enter recovery and delete data/adb/modules/riru-edxposed/post-fs-data.sh ....Others have had success with this after boot issues.
thanks for this. i am using YAHFA... compiled last canary XPOSED with #354 pull... YAHFA is very more stable.. and even faster (faster boot/less lags).
I am all out of ideas. Must be ROM and/or kernel combination. I didn't have any issues from begining to end. I installed stock Android 10, then Magisk, then Riru, then EdXposed.... disabled resource hooks in EdXposed installer (per C3C076 requirements), then installed GB and everything works. (never had to delete post-fs file)Yes I've done this.
This was how I managed to boot with Xposed enabled to begin with.
The issue arose once gravitybox was enabled.
OnePlus 5
Android 10 nitrogen OS
Phone does not complete proper boot with gravitybox enabled.
Phone seems to boot but screen is all black, when I hold the power button a garbled version of my reboot options are shown. (The normal ones from within the ROM not bootloader or recovery)
Leafing me to believe it's some sort of formatting or display issue?
I then must uninstall Xposed in order to boot properly.
Any ideas or anything I should try?
Apart from what others already mentioned it could also be an incompatibility between ROM and GB module.I'm having same issue
Just thought I'd post an update here, the volume key curser control started working all of a sudden a few days ago. Don't ask me what I did though as I don't have a clue lol.It works on Nexus5x running pixel experience which is very similar to Pixel systems. Not sure about terminal apps. Most of them override volume keys for some special commands.
I'm on Pie but recently I have some issues too with that feature of GravityBox. Sometimes (I haven't pinpointed the exact circumstances yet, maybe after a reboot?) the moving of the cursor with the volume buttons stops working even though it's enabled in GB Settings. So when that happens and I want to make it work again, I have to open GB, change the option to disabled and then to move cursor again.Just thought I'd post an update here, the volume key curser control started working all of a sudden a few days ago. Don't ask me what I did though as I don't have a clue lol.
Sent from my Google Pixel 3a XL using XDA Labs