[Magisk] Unspec:
Some testing I've done on Pixel 3 XL. Magisk is 18.1, Feb security update, latest ACC version, everything latest pretty much.

No

beta stuff.

onPlugged:

Max current isn't respected, don't bother

Max voltage (only tested for wireless chargers) is respected, but appears to cause issues with different wireless chargers. Cheapo ones appear to attempt to pull 9v, and I believe some kind of protection kicks in and the phone forces max_voltage back to 5v. It then attempts this over and over again. Lowering to 8v fixes the issue, so I've currently set it to 7.5v to be safe.

Pixel 3 series has the wireless DRM crap, so currently using ACC to bypass it. Pixel Stand works with 9v just fine, but it also pulls 9v by default, so I have a tasker task set to comment out onPlugged when at home, and to un-comment it out while away. If I'm at home, I'll either be charging wired or on the stand anyhow, so bypassing the DRM is moot for me.

Using accd command:

accd or acc -D restart seem to cause some issues on my phone, not sure if exclusive to me or not. I'll restart acc, and then I'll run acc -D a little bit later and it'll say it's no longer running. I've bypassed this by just doing acc -D stop and then acc -D start to restart. Works fine this way.

switch:

accd or acc -D restart complain about write error: device not found if switch is set, not sure why. I've tried providing the full path instead of ./ , but it doesn't seem to make much of a difference. This is only for actual restarts, if I use restart while daemon is stopped or manual stop/start, no error message. I'm providing switch the full path just to be safe, but not sure if the results will be the same with ./

input_suspend 0 1 actually "disconnects" the charger, as in the battery icon actually changes and the phone begins to discharge. Not ideal, as all animations and sounds play out as if you just plugged the phone in once the phone resumes charging, pretty distracting.

charge_disable 0 1 does not disconnect power flow. Using Ampere, it shows "Not charging", which means the phone is being powered completely by the power source. This is much better behavior since when the phone pauses charging, i.e during coolDown, the phone doesn't disconnect or play sounds/animations. Just does it silently in the background. Also means less wear on battery, since the battery doesn't constantly discharge/charge due to switch type 1 stated above.

Switch type 2 has a side effect of making the resume part of resume-pause irrelevant. Since the phone battery never discharges, the phone battery percentage will never reach the resume percentage, meaning the phone just sits at the pause percentage. Not sure if this'll have detrimental side effects, but in theory it shouldn't since the battery is just sitting idle.

resume-pause:

Not sure if this is a side effect of switch type 2, but when I set resume-pause to 90-95, the phone actually charges to 96% before going into bypass mode. I've since set the resume-pause to 89-94 to make it stop at 95% exactly because I'm a little OCD about numbers. Not sure how the algorithm calculates cut offs, but in theory this can be a bit of an issue if someone sets resume to 100, since it'll want to stop at 101, possibly causing constant charging. Perhaps due to a less than operator used where it should be a less than or equal? Not sure.