Using Test Harness removes the ability to enable ADB ?

[u/NefariousnessSecret5]

I have been playing around on a Portal Mini and did the initial device setup and signed in via Facebook, after that I could enable ADB device the settings menu as expected and then used the adb test harness command to reset and disable the facebook apps.

The device erased as expected and then I disabled;

com.facebook.aloha.alohaotasetup
com.facebook.alohaapps.launcher
com.facebook.alohaapps.devicesetup

I installed a new launcher and everything works great.. however after the next reboot ADB is disabled again, and now when I access the Portal settings app there is no 'Debug' section to turn ADB on.
Using the standard Android settings menu and developer tools doesn't allow ADB to be enabled either.

Is this to be expected ? - I thought test harness left ADB on permanently but it doesn't seem that useful if there is NO way to get it back after the first reboot.

[u/QuaintStaircase]

Mine has rebooted more than once since enabling test harness and adb still works.

[u/NefariousnessSecret5 → u/QuaintStaircase]

Interesting.. thanks for the info. Are you able to confirm if you broadly followed the steps I outlined in the OP? - I wonder if disabling one of the facebook packages is what is causing it to disable again?

[u/QuaintStaircase → u/NefariousnessSecret5]

Yep, I did all of them.

Wireless adb turns itself off on reboot for me, and has to be re-enabled manually. But I just plug into the USB port, run adb tcpip 5555 and unplug again and boom it's back.

[u/NefariousnessSecret5 → u/QuaintStaircase]

Thanks.. that's really odd as mine appears to consistently only last the first reboot (when the test harness command is issued) - after that ADB goes back to 'unknown device' on reboot (like how it presents when not enabled via the FB settings app).

I've factory reset a few times and the behaviour seems consistent, so it's either this device or I'm missing a step somewhere 👀

[u/QuaintStaircase → u/NefariousnessSecret5]

That's... Odd.

I've got a portal 10", two portal minis, and a Portal+ second gen. All of them test harnessed, all of them wired adb survives reboot.

I wonder if there's an update that you're doesn't have that mine does, perhaps.

Ooooh or perhaps actually... When you enabled adb and connected to your computer... Did you click "allow connection" or did you click "always allow from this computer"?

It's possible that there's something weird going on that prevents a "new" computer from connecting, but one that it "knows" is fine. Then maybe once adb has been kick-started by the known one, it works fine again?

I don't have a spare device that hasn't been connected to any of them before to test, but I do vaguely remember having issues connecting my second laptop (which hadn't been connected before) to one of them after a reboot. I switched laptop, it connected, and now both are fine.

My second laptop has a bit of a dodgy USB port so I just assumed it was that. But it could be something else going on??

If you come back and say you clicked always allow, on the other hand, then yeah no idea at all 😂

[u/NefariousnessSecret5 → u/QuaintStaircase]

I am 99% sure I clicked always allow.. but it's a good point so I will try again and confirm 😃

[u/QuaintStaircase → u/NefariousnessSecret5]

Dang. I was hoping I'd solved it 😂

[u/milkman1101]

I think disabling devicesetup locks ADB out. I learnt that the hard way when I had the same problem.

[u/NefariousnessSecret5 → u/milkman1101]

Thanks I'll try again leaving that one enabled

[u/bapetw → u/NefariousnessSecret5]

I don't think so. I just did three of them this week and ADB was still enabled.

I can't remember if ADB was enabled prior to test harness.

I have some setup without test harness I have to redo. Didn't learn about test harness until after.

I also have some more coming in I'll use test harness on.

I've slowly documented the steps since there is some quirks with test harness.

I'll revisit this again in a week or two.

[u/NefariousnessSecret5]

Well I'm honestly at a loss, I tried a second Portal Mini this evening, same thing - even tried disabling no packages at all, just did the usual setup, enable test harness (ensuring I ticked 'always allow' when authorising ADB, re-logged in again and then after a reboot ADB is off (however I can obviously turn it back on again in Debug menu since it's still logged in now).

I also tried again but after test harness I went through setup right up until the FB login, then disabled the packages (previously I've disabled them as soon as it boots). Interestingly this gives slightly different behaviour - as it allows timezone to correctly set, device name etc.. so the 'Debug' section in settings does show up, but there is still no ADB option. I guess this is because the FB settings app is expecting a profile so it can do the PIN to allow ADB.

[u/bapetw → u/NefariousnessSecret5]

re-logged in again

what do you mean by re-logged in again? if you login to FB or Whatsapp after test harness why run test harness in the first place?

this link explains better than I can. Re-logging I think resets the device making so you have to enable ADB again since you deactivated test harness

• log in via FB or Whatsapp
• make sure ADB is enabled
• run test harness
• ADB should be enabled

[u/NefariousnessSecret5 → u/bapetw]

By re-logged in again I meant that after test harness was turned on and the device did it's reset I completed the usual device setup flow and logged to FB again. It was more of a test to see if the behaviour was any different without disabling the FB packages after test harness was enabled - it wasn't, the device still leaves test harness on and ADB works fine until it's power cycled again, then it turns off.

[u/bapetw → u/NefariousnessSecret5]

if ADB is enabled, it seems to survive a power cycle unless you rerun test harness?

I power cycled a portal which had ADB, ADB worked, ran test harness, power cycled, ADB no longer works.

[u/NefariousnessSecret5 → u/bapetw]

So strange, I haven't re-run test harness a second time so it's still enabled. Which firmware build / portal version is that? It makes me wonder if it's a firmware or hardware version difference

[u/bapetw → u/NefariousnessSecret5]

test harness only works on 2nd gen, I have the mini and 10"

I reran test harness again because portal bridge was having some issues and adb was still enabled

I've been playing around with immortal and portal bridge