What is wrong with ADB in developers settings in any 9 ROM?

[comunity]

Hi to all v9 users.
I tried several ROMs version 9 from here and found that all of them have the same bug(?) - allowed ADB debug over USB in developers settings is lost after reboot. In both cases - rebooting to the system or, what more important for emergency cases, in recovery.
Also must be mentioned, that immediately after reboot, ADB debug is allowed and the device is visible from PC for several seconds. But when lockscreen will appear - ADB will be lost.
I'm always flash at once ROM+GAPS+Magisk and always have the same result. Even when Magisk is running in MagisCore mode.

What I'm doing wrong if I do? How it can be fixed? How to get constantly present ADB over USB? Wich of existing 9ROMs haven't this bug now?

 

[PGKiD]

This does not happens to me. I am on AEX Pie by subham.

 

[comunity]

This does not happens to me. I am on AEX Pie by subham.

Tried this one right now. ADB is allowed by default! And not switching off, but... till some moment or event.
So, my path: flashed ROM+GAPS+MAGISK, installed MagiskManager, installed BusyBox Magisk Module, installed LuckyPatcher, block ads and apply 3 android patched, installed Titanium - and it suddenly told me that I must turn on ADB after this moment ADB is permanently lost after reboot.
I understand that the reason may be in some of these apps or conflicts between them. But I used the latest versions and can't refuse any of them (
Looking forward for solution...

 

[PGKiD]

Yeah I lost adb debugging every reboot too. But it does not matter to me as I did not consider it to be always on myself.
As extra, I use DevTiles to makes it easier to turn adb debugging.

 

[comunity]

new Havoc 2.2 from 19.02.2018 correctly working with ADB in rebooting to a system and/or recovery, but, unfortunately, LED is not working. waiting for completely working rom...

 

[comunity]

Old, but working TWRP

Found old TWRP version 3.2.1-0 which is properly working with ADB in recovery mode and under regular android.
I'm not sure when and where I downloaded it, but it's working well for me.

 

[sm00th4f3]

CrDroid is working great. ADB doesn't reset for me.

And btw this is the wrong section.

Sent from my Lenovo P2 using XDA Labs

 

[comunity]

working great. ADB doesn't reset for me.

As I found, it depends on TWRP version and ROM itself. Maybe you are lucky to have working pair )
Allowed ADB may not be lost when you reboot your system. However, there are a lot of cases, when you reboot from system to TWRP and the device becomes invisible for ADB under TWRP ((
Another case that was found - in some ROM device becomes visible via ADB only when in USB settings I chose "Charge only" and disappears when select "File transfer" (or vice versa).
In any case, it's software incompatibility, which can be fixed, bcz on AICP v8 and mentioned above TWRP everything is working fine in any mode. So, still looking forward to completely working pair OS9 and TWRP...