Display link barely works on linux desktop last I checked, was super bummed out by the bad proprietary drivers
Posts
-
RE: USB C to HDMI on Pixel 3a
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack I've completed the endurance test. Not sure how to post an image, but uptime is at 7 days.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
Rip, I accidentally let the 6p run out of power on day 6 and a few hours.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@Flohack I'm looking at 2 log files which I think are from that time (October 11th), but they're .OLD files for some reason. When I open them with notepad they don't seem to be functioning log files. Here's an example of the contents of one:
2020/10/11-13:37:37.233 60e4 Reusing MANIFEST C:\Users\Admin\AppData\Roaming\ubports-installer\Session Storage/MANIFEST-000001 2020/10/11-13:37:37.236 60e4 Recovering log #3 2020/10/11-13:37:37.238 60e4 Reusing old log C:\Users\Admin\AppData\Roaming\ubports-installer\Session Storage/000003.log
The files it's referring to seem to be gibberish, I don't know what to do from here. I would reinstall on windows to replicate the error, but I'm on day 5 of the Endurance test. (I think it was mentioned in the ubports podcast as "silently failing?" But I don't trust my memory.)
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
@MrT10001 the current version of the windows 10 installer is bugged I had the same thing happen to me. You have to use the linux installer as far as I know. Maybe you could use windows subsystem for linux. Or perhaps the mac installer works. If you can't do either then maybe you can use the manual method described at the beginning of the thread or simply wait for the next installer release.
-
RE: Call for testing: Google/Huawei Nexus 6P (angler) owners
I experience frequent crashes preceded by lockups; is that what you guys are experiencing? (The other day, it crashed 3 times over the course of dinner, I thought it was because I was on developer channel). I suspect it has to do with ram usage. I downloaded gnome system monitor from libertine because htop wasn't working for me and it seems that the lockups happen at high ram usage when the 32 mb of cache are filled. I can avoid them by manually limiting my app usage to two to four apps at a time tops.