The opposite works as well. You can use your phone as remote mic using ssh
pactl load-module module-pipe-source source_name=virtualmic file=/tmp/virtualmic format=s16le rate=44100 channels=1
ssh phablet@'phone-ip' [-i identity_file] "arecord -f S16_LE -r 44100" |cat > /tmp/virtualmic
I just flashed to stock android and the issue persists. I assume a hardware failure
After reading this article, I was wondering what is or can be done to protect devices running UT from this vulnerability. As far as my knowledge goes, UT uses an android kernel, which uses device specific and mainly closed source hardware drivers. The white paper says that the vulnerability can be mitigated through software or firmware updates, but older devices don't get firmware updates anymore.
My question is whether UT users will stay vulnerable to Kr00K as long as there is no firmware update available or can it be solved through software and is it just a matter of capacity and priority?
Basically the same question applies to Spectre, Meltdown and other bugs where the source is in the hardware.
I reinstalled Android, the SIM card still did not work properly. I was able to read the correct provider name in the phone settings. I tried different SIM cards from different operators, all had the same issue. I could read the operator correctly, but no cellular connection did not work.
Than GPS also started to show issues, in the first weeks I was able to get and hold a fix. But now the first fix was ok, but after a couple of minutes the GPS stopped working.
I opened the device, because previous owner said it got a new battery. half of the screw were missing. I needed my phone for work and had no time for further investigation.
In the end I bought a new Pixel 3a and am installing UT at the moment.
Screencasting and taking a screenshot of the desktop is a solution for scanning the QR code on the same device, if you don't have a spare phone.
The opposite works as well. You can use your phone as remote mic using ssh
pactl load-module module-pipe-source source_name=virtualmic file=/tmp/virtualmic format=s16le rate=44100 channels=1
ssh phablet@'phone-ip' [-i identity_file] "arecord -f S16_LE -r 44100" |cat > /tmp/virtualmic
My apologies, I replied to the initial post of @slowcyclist, and while re-reading my own post it is indeed not very clear.
I'm having the both mallooc and segfaults. Especially the segfaults result into freezing navigation apps.
Mar 07 09:42:25 ubuntu-phablet lomiri-location-serviced-wrapper[1708]: malloc(): unaligned fastbin chunk detected
Mar 07 09:42:25 ubuntu-phablet systemd[1]: lomiri-location-service.service: Main process exited, code=killed, status=6/ABRT
Mar 07 09:42:25 ubuntu-phablet systemd[1]: lomiri-location-service.service: Failed with result 'signal'.
Mar 07 09:42:25 ubuntu-phablet systemd[1]: lomiri-location-service.service: Consumed 6.437s CPU time.
Mar 08 20:48:56 ubuntu-phablet systemd[1]: lomiri-location-service.service: Main process exited, code=killed, status=11/SEGV
Mar 08 20:48:56 ubuntu-phablet systemd[1]: lomiri-location-service.service: Failed with result 'signal'.
Mar 08 20:48:56 ubuntu-phablet systemd[1]: lomiri-location-service.service: Consumed 3.987s CPU time.
@slowcyclist You're not the only one... I'm having the exact same issue, also on FP5. I'm running 24.04-1.2 stable
@arubislander said:
24.04-2.x
I'm referring to 24.04-1.x 
Today I received the update to 24.04-1.2 on my Pixel 3a, which is set to channel 24.04-1.x Stable
Checking the UBports news section, I found this article, but I could not find any announcement of the release of 24.04-1.2 on the forum. Was this missed?
Solved by first updating to 20.04 OTA-11 and than upgrading to 24.04-1.1
@lduboeuf
In the past I temporarily made root writable to install gpsd and lomiri-location-service-tests in an unsuccessful attempt to get the current gps location in a terminal
I tried to upgrade to Noble this week when the option was presented in the 'Updates' menu. The whole process took about 30 minutes and it did boot, however unlocking the phone would result into immediate restart of lomiri presenting me the lock screen again. Unlocking would result into the same restart of lomiri. I was able to open the top drawer and noticed new items like Display and Ayatana-bluetooth-indicator. But none of the buttons would respond.
I rebooted which took about 10 minutes, than interface seemed to respond properly. But due to missing mobile communications (no indicator in the top bar), I rebooted again.
After third boot interface looked ok, but when opening Cinny, I got a message that disk was full. If I recall correctly I started the upgrade with around 10GB free space.
Subsequent reboots took around 30 minutes again. But basically same status as during the first boot after upgrade as described above. I was able to ssh into the phone and noticed that no free space in /dev/mmcblk0p72 mounted on /userdata was available.
I tried reinstalling noble, by using the installer without success. Same performance as with the subsequent reboots.
Than I downgraded to Focal and the phone responded properly again. I was only missing Dekko2, which was solved by reinstalling. But I also got a message of 3% disk space remaining.
I found a 7 and 8 GB backup file in /userdata/backups (user-config-backup-20251003T161729Z.tar.gz and user-config-backup-20251003T164623Z.tar.gz) So I deleted the oldest.
This experience leads me to a couple of questions:
What is the purpose of user-config-backup files?
Is it safe to delete them all?
How do I upgrade properly to Noble
Inspired by this post, I'm wondering what the security implications are of using Matrix bridges. I assume that the bridge is as secure as the least secure medium involved, so bridges are by default less secure than communication within a single medium.
So the only reason to use a bridge, would be if the other user is not able or willing to use Matrix as medium. Is my reasoning correct?
Screencasting and taking a screenshot of the desktop is a solution for scanning the QR code on the same device, if you don't have a spare phone.