Version 2.0.2.0 support

[FiloSottile]

Firmware version 2.0.2.0 has now rolled out to my device, and unfortunately I didn't rollback the webui_invincibility patch before updating, assuming it would just overwrite everything.

Now the UI for the web interface is stuck on Off and changing WebInterfaceEnabled to true gets overridden at process start.

Not really sure how this happened. Maybe the update is a binary diff, and the patch stuck around, still breaking the UI but not working fully?

This is my current xochitl, if anyone could confirm it's not the stock one.

75b0c179e9b3facf7cacef2cd9ae748a08a2695306bb2b8a978c98160602df3c  /usr/bin/xochitl

[CTXz]

@FiloSottile That's unfortunate to hear, and odd as well since I'm almost certain that 2.0.2.0 has altered xochitl in some way or another and should thus override the entire binary. I'll attempt to get my hands on the stock binary in the coming days.

[vinipsmaker]

@FiloSottile, I haven't applied this patch that you mention. Either way, webUI stopped working here since I upgraded to 2.0.2.0. So, I don't think the problem is that you forgot to rollback the patch before the update.

[benneti]

I wrote the support and apparently you need to be connected via usb to enable it.

[Martinif]

I just discovered that WebUI immediatly pauses when the USB Connection gets disconnected. Therefore I can not use the WiFi network address. To reproduce ssh to the remarkable, run 'ping 10.11.99.1', dis- and reconnect the USB cable.

Did anyone experience this as well/has found a solution?

[FiloSottile]

Ok, figured out what was confusing me. Here are the change in the new firmware:

• The Web UI toggle won't turn on at all unless the usb0 interface has an address (either because it's plugged in, or because you assigned one manually). This is very confusing and led me to think it was broken initially.
• The Web UI now only binds to 10.11.99.1, and not to 127.0.0.1 (so even if it's still running after you unplug, it won't be reachable).
• webui_invincibility of course doesn't work anymore.

So now my procedure every time I reboot the rM is:

1. SSH in and manually assign an IP to usb0

ifconfig usb0 10.11.99.1 netmask 255.255.255.248 up

2. Go into settings and enable the Web UI

At which point I have a Web UI on 10.11.99.1:80 until you reboot, or plug in and out (which will drop the interface IP).

It would be great if we could find a way to do (2) programmatically, so my scripts could assign the IP if needed and then start the Web UI automatically. Maybe it'd be enough to update the webui_invincibility patch, and restart xochitl after assigning an IP to usb0?

[nickmooney]

Hey folks,

I'm attaching a bspatch (zipped, as GitHub won't allow bspatch uploads) for the same behavior (force web UI on) for firmware 2.0.2.0. I haven't been able to test the new OS since my tablet is now on 2.1.1.3, but I've patched the same function as former versions.

Please let me know if you'd like an actual PR against the invincibility script. I didn't modify it mostly because I didn't have a new Google Drive link for the up-to-date xochitl binary, heh.

xochitl-2.0.2.0-webui-enabled.bspatch.zip

[CTXz]

Great work! Since I unfortunately still don't have access to a remarkable table after mine broke, and due to the fact that I'm a little busy working on other projects at the moment, I'd be very happy if you could provide a PR. I'm glad to see that the documentation efforts proved to be useful 👍 !