Magisk Wifi

[Magdalen Dano]

Ihave a OnePlus 7 Pro. I had LineageOS 17 (Android 10) with microG, magisk, and vanced on it running just fine for almost a year. I upgraded the Android version to 11 first (which LineageOS documentation says is a pre-requirement) then I upgraded to LineageOS 18, and everything seemed to work just fine. I can confirm that my recovery and wifi worked.

A few days later I wanted to open Vanced YT, but it was no longer installed, then I noticed that magisk was no longer installed. So I installed it according to it's instructions which was basically using the app to patch the boot.img I got from the extracted files (from a payload-dumper) and then installed the produced magisk_patched-24200_Y0Qmv.img.

Ever since then is my problem. I can no longer turn on my wifi, I no longer have recovery mode, and every time I turn on/reboot the device I am greeted with a "System UI Crashed" error message. I can hit ok and everything else seems to work as expected. With the exception to my wifi not being able to turn on

After that when it rebooted, everything worked as expected with one exception; GCam. But I think this is related to the LinageOS upgrade. I was able to fix this by re-installing microG and upgrading to a newer version of GCam. All other original issues where cleared though. Wifi, phone, etc.

When I saw that my bank application was not working I tried to remove the permission to unlock the bootloader, which was not greyed out in the developer settings. This did not solve the problem, but to reactivate the permission to unlock the bootloader I was asked for the special code again and I was afraid that I would have to erase all my data again, so I left it like that. Later I noticed the option had become greyed out.

First I updated the Magisk app when I saw update notification. Then I directly install Magisk and reboot as usual. After that I saw that the Magisk application had disappeared and that each time I tried to reinstall it, it disappeared again when I wanted to run it. Then I gradually discovered the other malfunctions: wifi, heating, sound.

And indeed, booting any image other than current will not only break wifi (that one I knew already), but also sound and likely more. Thermal issues might just stem from some process going haywire and constantly trying to start, never ran from a fastboot booted image long enough to notice anything like it.

What I want is to be able to stream from my Android phone to pulseaudio. There are individual apps with chromecast support, but then you're stuck with the app, and you need to be running something like Kodi on the desktop to receive it.

To send audio via a network connection from Android to Ubuntu you always need a renderer on your Ubuntu desktop and a streaming application on the android device. Android does not use pulseaudio as a sound server. We therefore depend on an additional app to send audio to the desktop.

It has some buffering issues which makes unusable for me (once in a while it skips a few words on my audiobook), and has a high delay even on USB, but on some cases that doesn't matter. I have just tried it.

I think a way better trade-off than the enormous stress with BubbleUpnp would be SoundWire. This will not stream to pulseaudio but to SoundWire server running on your Computer. But it will stream all audio from your Android device to it after and it can run in the background.

I was able to do this using audiorelay, works both ways, over wifi. It's kinda choppy but as far as I've seen, reliable enough. And the setup is pretty simple, install the app and program on both systems, and just connect with the automatic discovery.

3a8082e126