Develop Bugs

[GUIDE] [MOD][ICS][XPOSED] Tweakbox(Volume Button Skip) w/ Working INSTAGRAM!!

As some of you may know....... Many people are frustrated that you can't have the volume button Skip hack and have ability to use the Instagram App.......:crying: Well, I've found a quick work around without having to DL an add-on or additional script to get it to work....
If you don't have them already.... you just need the simple following:
Xposed Installer
And
TweakBox
Please click the links above for installation instructions......
1) Once, you have installed Xposed Installer and Tweakbox (Again Please Click the Links above for the directions) you would proceed with the install and selecting what you what Tweakbox to do.
2) After You Install .... YOU MUST REBOOT!
3) After the reboot, Go back to Xposed Installer and Click "Uninstall (restore app_process)"
4) DO NOT REBOOT.... IT WILL SAY YOU NEED TO REBOOT FOR CHANGES TO TAKE PLACE.... Ignore that and go about you way... You now have the ability to Skip Songs with the volume buttons with the screen off and YES you can use Instagram..
5) Enjoy and Share instagram pics!
I do not take credit for the TweakBox or Xposed Installer but just to help the fellow community out on getting these 2 apps to work.... Below is my cheesy video showing that this works.... Enjoy and don't forget to hit that Thanks Button :laugh::good:
http://www.youtube.com/embed/0sKvJWGywAw

Installed xposed apk, but got a bootloop after reboot... Running 4.1.1 stock.
Also, wouldn't this break if we reboot the phone later on. So we have to do this everythine our phone is turned off or reboot??
sent from my JB GS3

Xposed tweakbox only works on ics afaik
Sent from my SGH-T999 using xda app-developers app

Papote3 said:
Installed xposed apk, but got a bootloop after reboot... Running 4.1.1 stock.
Also, wouldn't this break if we reboot the phone later on. So we have to do this everythine our phone is turned off or reboot??
Click to expand...
Click to collapse
Actually, there's a version that runs on both ICS and JB: http://forum.xda-developers.com/showthread.php?p=34609290#post34609290
It's still not the final 2.0 version as some adjustments are being done by rovo and myself. A permanent fix to the Instagram insue should be part of that final release as well.

HI, just adding that this also crashes the Reddit News App but your solution "fixes" it.:victory:
Please Tungstwenty, fix this.
:good:

[ROM] Marshmallow for Nexus 10

Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10

My nexus 4 and nexus 10 are happy today thanks to you.

dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.

jase33 said:
Had soft reboots when using browser. Wiped, re-flashed and same issue.
What gapps package did you use? I made a quick one with play services and gmail.
Click to expand...
Click to collapse
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.

dmitrygr said:
Go into permissions and issue all permissions to the browser, or just install chrome - it supports 6.0 better
I am not going to talk about GApps, sorry
Try the marshmallow for nexus 4 thread - people there might have answers.
Click to expand...
Click to collapse
thanks

For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root

Used these gapps, follow the instructions though, use "touch 'filename' " in TWRP terminal for the file creation. Gapps on 6.0 is struggling right now, but these instructions worked for me.
EDIT: Forgot the link. http://forum.xda-developers.com/and...le-apps-minimal-edition-t2943330/post63226314

Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.

billyx1 said:
Same problem with soft reboots. Often just after starting Android before or after login. Even if I don't install gapps.
Click to expand...
Click to collapse
did you erase all data and cache when flashing?
if no, nothing i can do - i do not support that
if yes send me logcat

peachpuff said:
For gapps i used this package https://www.androidfilehost.com/?fid=24052804347833783 its pretty basic but gets you what you need, make sure to do a factory reset after flashing it otherwise the setup wizard will fc.
Now all we need is root
Click to expand...
Click to collapse
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.

it is a userdebug image, so at least in adb you have root

Amazing piece of work. Gonna try it as soon as a reliable gapps package is out!

dmitrygr said:
Get it while it's hot. All works. AOSP rom
Also included: directions how to build one of your own, TWRP images to flash right now, and a description of a VERY VERY cool hack i undertook to make GPS work
http://dmitry.gr/index.php?r=06. Thoughts&proj=03. Android M on Nexus10
Click to expand...
Click to collapse
Woot nice!
Could you share your device tree ?
edit thx for sharing :
I was having the bootloop at google logo and couldn't figure out what to do.

great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?

phonetec said:
great job on the rom, no idea why people are having issues, i found the gapps package in the nexus 4 forum....no bootloops here, everything seems to work......I was able to enable google now on tap however i do not know how to use it, instructions say to hold down the home button to launch, however we do not have a home button, any ideas?
Click to expand...
Click to collapse
home softbutton in systemui (the middle one)

dmitrygr said:
home softbutton in systemui (the middle one)
Click to expand...
Click to collapse
Ok I tried that and nothing happened, maybe I was using it wrong, I'll try again later when I get home
Sent from my SM-G925P using Tapatalk

I think I might cry. Flashing now.
---------- Post added at 11:12 AM ---------- Previous post was at 10:42 AM ----------
corumuk said:
Thanks, that worked for me.
Also tried flashing supersu 2.52 beta from twrp but that seems to make it stick at the android loading screen so I guess there's no root at the moment.
Click to expand...
Click to collapse
Maybe we need a kernel that supports root. That's how it is on the Nexus 5 anyway. I don't know if any of the lollipop kernels would work on this. Maybe I'll try that sometime soon.

Just an FYI.....
Updating Google Play Services (required for YouTube) sends it into a FC loop.

Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?

fifthelement said:
Hey guys, Have you noticed any kind of performance improvement after installing marshmallow ?
Click to expand...
Click to collapse
I've noticed it has been pretty quick. Did a full wipe and used the system.img from his website. Used these gapps. https://github.com/XorgMC/gapps-mm/releases/download/v1-mini/gapps-mm-mini.zip
Also, if you use those gapps it will say it failed if you try to restore your apps. Hit skip and it will say restoring. It will take a long time to install the apps. If you lock the screen and then unlock it swiping from the side to open the google app you can use the device while it restores your apps.
I havent had any issues related to the rom, just the gapps. Google app fails when i try to search something.

Gravity box running on marshmallow 6.0.1

Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?

cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot

cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)

I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.

cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.

C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?

cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs

C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.

cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.

C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end

deleted

[ROM][NWD1.171016.002] NegaSt33v Huawei-Rom

I decided to update the optimized stock rom that @negamann303 made and some of you are a fan of.
Features:
Based on NWD1.171016.002 - Wear 2.0 - Android 7.1.1
Stock kernel
Optional root/busybox package that will install root and busybox 1.28.1
Same build.prop additions as NegaLite Huawei-Rom NX 2 v 1.2 (including ADB debugging pre-enabled)
Removed Google Fit from /system (download from Play Store if you want it)
Removed the tutorial that appears when you enable wrist gestures (but not the tutorial that happens when you first set up the watch)
Changelog:
v 0.2
Actually installs stock kernel instead of the rooted kernel I accidentally put in v 0.1
v 0.1:
Initial release
Install Instructions:
Factory reset in TWRP (optional, but recommended)
Flash rom
Flash root/busybox package if desired
Note: The first boot takes a looooong time.
Note 2: The SuperSu/Busybox package tells you that it's installing an older version of busybox than what I listed. Don't pay attention to it. If you want to make sure I'm honest just do adb shell, then su, then busybox.
Download v 0.2: https://www.androidfilehost.com/?fid=962187416754467969
Download SuperSu and Busybox package: https://www.androidfilehost.com/?fid=962187416754466211
Download Busybox only package for those who want to use Magisk (personally, I don't see the point of using Magisk on a watch that doesn't need to pass safetynet, but to each their own): https://github.com/yashdsaraf/bb-bot/releases/tag/v1.28.1-YDS-201803061707 (flash the universal zip)
Requests are welcome. Keep in mind that since Android Wear is not fully open source, our power to change it is relatively limited.

TheSt33v said:
I decided to update the optimized stock rom that @negamann303 made and some of you are a fan of. Right now it's a work in progress. I'm pretty sure that everything works, but please test and report back.
Features:
Based on NWD1.171016.002 - Wear 2.0 - Android 7.1.1
Stock kernel
Optional root/busybox package that will install root and busybox 1.28.1
Same build.prop additions as NegaLite Huawei-Rom NX 2 v 1.2 (including ADB debugging pre-enabled)
Removed Google Fit from /system (download from Play Store if you want it)
Removed the tutorial that appears when you enable wrist gestures (but not the tutorial that happens when you first set up the watch)
To do:
Update Gapps
Move more system apps to /data for easy deletion
Include Root Essentials and Advanced Settings (download from Play Store if you want them for now)
Install Instructions:
Factory reset in TWRP (optional, but recommended)
Flash rom
Flash root/busybox package if desired
Note: the first boot takes a looooong time.
Download v 0.1: https://www.androidfilehost.com/?fid=673956719939825513
Download SuperSu and Busybox package: https://www.androidfilehost.com/?fid=962187416754466211
Click to expand...
Click to collapse
Good job! Feel free to pm me if you ever have any questions. I will try my best to answer them
Sent from my SM-G935P using Tapatalk

It's really nice to see the new rom for HW1!
If this rom can have lower brightness for ambient mode, I would love to test the rom!!!

Amazing rom

Thanks for the effort.
I will give it a try when I find some free time.

lentm said:
It's really nice to see the new rom for HW1!
If this rom can have lower brightness for ambient mode, I would love to test the rom!!!
Click to expand...
Click to collapse
According to the quick Google search that I did, it looks like this is controlled by the Android system framework. It's not as easy as changing a build property or telling settings to do something different. So unfortunately it doesn't look like it's something I can change, but if anyone finds any other information on it I'll definitely take a look.

Thanks a lot for continuing his work. Will be testing out on my watch soon.
Sent from my LG-H932 using Tapatalk

Thank you very much for doing this rom, look forward to using my watch again as I haven't used it in months.

It seems this build still installs the "rooted kernel" (that contains SuperSU binaries and configurations), which in turn blocks installation of Magisk (same as the original NX rom), as the two root solutions aren't compatible.
Guess I'll have to work around it using the hard way for now. It's better if the kernel can be made rootless so one can choose to install either SuperSU or Magisk.
EDIT: Got everything working: ROM, Magisk, and Busybox (installed using this one).
EDIT 2: It seems the Daily Tracking is working on this version, as on Explorer watch face the steps and kcals are properly registered just like on Android Wear 1.5.

LSS4181 said:
It seems this build still installs the "rooted kernel" (that contains SuperSU binaries and configurations), which in turn blocks installation of Magisk (same as the original NX rom), as the two root solutions aren't compatible.
Guess I'll have to work around it using the hard way for now. It's better if the kernel can be made rootless so one can choose to install either SuperSU or Magisk.
EDIT: Got everything working: ROM, Magisk, and Busybox (installed using this one).
EDIT 2: It seems the Daily Tracking is working on this version, as on Explorer watch face the steps and kcals are properly registered just like on Android Wear 1.5.
Click to expand...
Click to collapse
Oops. You're right. Sorry about that. I'll fix it this evening.

Source?
Where did you get the source?
i want to start making roms with the AOSP.

Omg. You are the man negast33v. Thanks for keeping this watch alive.

jayjar said:
Where did you get the source?
i want to start making roms with the AOSP.
Click to expand...
Click to collapse
I didn't get the source. In fact I didn't do much at all. I took the stock rom, put negamann's build.prop tweaks in it and put together the optional root package. That's about it, because that's about all that was done to negamann's original rom.

When you say the first boot takes a long time, how long are we talking? I'm testing something with my watch, so I already expect it to fail. I want to know so that I don't wait for hours when it should have been done in 20 minutes, which would mean my test has failed.

TheSt33v said:
I didn't get the source. In fact I didn't do much at all. I took the stock rom, put negamann's build.prop tweaks in it and put together the optional root package. That's about it, because that's about all that was done to negamann's original rom.
Click to expand...
Click to collapse
This is correct! That is why I typically spent more time on the kernel.
Sent from my SM-G935P using Tapatalk

CVertigo1 said:
When you say the first boot takes a long time, how long are we talking? I'm testing something with my watch, so I already expect it to fail. I want to know so that I don't wait for hours when it should have been done in 20 minutes, which would mean my test has failed.
Click to expand...
Click to collapse
Definitely not hours. 5-10 minutes I'd say.

Does someone want to try using the negamann kernel with this rom? It might work. I'm not sure and I don't feel like testing it.

TheSt33v said:
Does someone want to try using the negamann kernel with this rom? It might work. I'm not sure and I don't feel like testing it.
Click to expand...
Click to collapse
Hey,
I tried it, it doesn't work, it just hangs on the Android logo, waited over an hour, rebooted, nothing. Will not boot.
Edit: this is what I tried: negalite_kernel_HW_dffc4c0-2.0.zip - 6/7/2017
Edit 2: Just tried again, this time I cleared cache/dalvik and even so its just been on the Android animation for over an hour, and the watch has become really hot...Going to go back to stock kernal.

RumpSteak01 said:
Hey,
I tried it, it doesn't work, it just hangs on the Android logo, waited over an hour, rebooted, nothing. Will not boot.
Edit: this is what I tried: negalite_kernel_HW_dffc4c0-2.0.zip - 6/7/2017
Edit 2: Just tried again, this time I cleared cache/dalvik and even so its just been on the Android animation for over an hour, and the watch has become really hot...Going to go back to stock kernal.
Click to expand...
Click to collapse
Damn. Thanks for trying.

Thanks for updating this rom. Much appreciated : ).

Questions about running stock rooted ROM / XPosed (Gravity Box) / Substratum

Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:

Ghisy said:
Hi guys,
After months of hesitation, I finally ordered a Pixel 2 XL. Now after a few years of running custom ROMs, I'm thinking of running the stock Google ROM with tweaks. But I haven't done that in a while so I have some questions, after rooting and installing TWRP:
- is it safe to install the latest Xposed framework beta? (bootloop/crashes)
- does Gravity Box work fine (no crash/bootloop)?
- can I apply Substratum themes on rooted stock?
- which kernel would you choose between Flash and ElementalX? I've been using the latter for a long time but curious about Flash.
- how do you handle monthly OTAs? Can they be installed running all of the above?
Thank you! :good:
Click to expand...
Click to collapse
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!

rickysidhu_ said:
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Click to expand...
Click to collapse
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.

Ghisy said:
Hi,
Thanks for the comprehensive reply, it's appreciated and it does help!
I'm not sure about your last answer about OTAs though. So we have to flash the whole factory image every month? Isn't it possible to sideload the OTA? And what about Magisk and Xposed, do they have to be flashed again every time? I guess Substratum themes have to be compiled again as well? I guess I've been so used to custom ROM and dirty flashing that I got somewhat lazy
Does the unlocker for Gravity Box add more options? Or is it just a way to donate money to the dev?
Thanks again.
Click to expand...
Click to collapse
Unlocker is to support dev as well as it unlocks the ultimate notification controls which has a trial period
Ota are fine but we all prefer to flash the whole image because it is recommended and hardly comes up with errors
If you install magisk module for xposed then you would only need to re install magisk zip and your previous modules would be still installed
For substratum you need to disable overlays before updating and just re enable them after updating to latest update
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs

rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
Click to expand...
Click to collapse
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!

Ghisy said:
Hey,
I can't seem to be able to boot after flashing the xposed zip. My device shows a corrupted system error and boots back to the bootloader.
Is there anything I'm missing here?
Thanks!
Click to expand...
Click to collapse
Which version of Xposed did you flash? And which version of the Xposed installer did you install?

rickysidhu_ said:
Like you, I have always run custom ROMs and this is my first time running stock with tweaks like you mentioned.
1- yes, as far as Xposed goes for me and my device, I've had 0 issues. If there is any lag, just choose the "optimize apps now" option in the Xposed installer.
2 - gravity box works flawlessly for me and gives so many features. I had to support the dev and bought the unlocker!
3 - you can use substratum, but since the March update, you have to reboot after building overlays to see them in the overlay manager.
4 - I've tried almost all kernels available for our device, and I don't know why, maybe it's a placebo, maybe not, but Flash has been the best for me. Virtually no slowdowns in terms of performance, and solid battery life as well.
5 - most people flash the factory images, editing the flash-all file, removing the "-w" to prevent data from being wiped. Me on the other hand, I do the most overkill option which is fastbooting the factory images to both slots, leaving the "-w" intact, and basically starting fresh every month it ends up being a few hour process but I don't mind because I have a bit of OCD and like having a clean slate to start from when new updates release.
Hope this helps!
Click to expand...
Click to collapse
Ditto.

rickysidhu_ said:
Which version of Xposed did you flash? And which version of the Xposed installer did you install?
Click to expand...
Click to collapse
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.

Ghisy said:
I flashed xposed-v90-sdk27-arm64-beta3.zip. But I ended up installing XPosed through Magisk and it actuallly worked.
Are we not supposed to flash the .zip? It's what broke everything. I managed to flash the factory image and got my phone back to normal.
Click to expand...
Click to collapse
Glad you got it working.
I downloaded the Xposed APK in the Magisk thread and installed Xposed within the app; after reboot everything seems to work normally for me.
The way you did it is also fine though:good: