Nathaniel van Diepen
Nathaniel van Diepen
> Oxide seems to be failing while upgrading due to fret. I did a fresh install of oxide 2.6-3 from the stable toltec repo and had it working fine. Then...
This is very odd as the `oxide` package no longer depends on `fret`. It's been removed and replaced with `oxide-extra`, as expected. What does `opkg info oxide` output? As well...
So there are two `oxide` entires, likely one for each repo. The one that's marked as installed doesn't depend on `fret` though. This may be an `opkg` bug that wont...
> I commented out the toltec repos and no longer see the error, that seemed to work. Alright, so users will not encounter this. It's rather annoying to properly test...
I've gone through a fresh install of 2.15 and toltec on my rM2 and then ran through an update and double-checked `rm2-suspend-fix` and `rmfakecloud-proxy`. This should be good to merge.
> Happens after a sleep long enough to cut the WIFI, and a wake up. ... @gullradriel I'm a little confused by this statement. By default in toltec, wifi is...
I've been unable to replicate with manual suspend or waiting for both xochitl or remux to automatically suspend after inactivity.
What will make this a little awkward to deal with is that every time you reconnect the folio, it will create a new `/dev/event*` node.
This is not tested yet.
I can replicate this in the run-in-remarkable test action: https://github.com/Eeems-Org/run-in-remarkable-action/actions/runs/8041803942/job/21961567916