-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify rooting via webusb instead of webserial #163
Comments
This could also allow us to determine rooted state and evolve the UI to hold the users hand more. |
Ah yeah, right - now I can remember why I did not use it in the first place - this has actually been an issue with my other configurator too: there are no remove and connect listeners, I submitted a patch which was not merged and the maintainer did not yet implement their intended clean solution. We could technically use my temporary fix branch... |
The
|
Presumably you made sure nothing else is claiming the iface? Anything in device-logs? Or maybe some udev bullshit? |
Yes, I did check that nothing else is claiming the interface. device-logs seem fine, nothing out of the ordinary. I am not the only one having this "issue" though. You could cross check by running the demo.html from the webserial polyfill repo. As far as I understand the problem is that the system has a driver for the USB Serial device and thus can not be wrapped with the polyfill... |
Same, with "Interface 4 uses driver "usbser" instead of WinUSB." in device-log. So I guess without having the user involve Zadiq, we're boned? Don't want to do that, as then Assistant would break. |
Yup, I see it the same way. I don't want to involve external (non cross platform) tools at all. |
|
r.i.p. |
As suggested by @D3VL-Jack the webserial polyfill for webusb could be used instead of webserial. This would allow us to have the user only interact once with the device selection dialog for both rooting and wtfOS related things.
The text was updated successfully, but these errors were encountered: