Unfortunately I don't currently have the coding skills to fork/update/maintain uReadIt, as it seems like a good base for a reddit app (and personally is quicker to navigate on my PinePhone than reddit.com in Morph).
Really this post is just a request for someone to take over maintenance and updates of the app and to see if others on the forum are interested in a dedicated reddit app on Ubuntu Touch.
@foust No, the Nexus 5X is not currently a supported device. You can find supported devices here: https://devices.ubuntu-touch.io/.
Here is a forum thread where the developer who was previously working on it mentions the issues that he was having at the time: https://forums.ubports.com/topic/971/nexus-5x-development/10.
Assuming you are talking about the initial installation steps, just long enough to get the phone to boot into the bootloader.
It seems to work pretty well on my Community Edition Pinephone, I haven't tested video playback yet.
I don't have a screenshot to share, but text is pretty small on the main page posts--going in to the comments for a particular post the comment font size is easily readable, but the post font size stays small. This may be more of a Pinephone issue than a Quickddit issue though, as I've noticed other apps displays to be pretty zoomed out (e.g. Axolotl) on the Pinephone.
ETA: No luck playing back a Youtube video in the app.
Already noted in the issue tracker here: https://gitlab.com/ubports/community-ports/pinephone/-/issues/138.
@flohack When I renamed both files to .bak and then followed the steps to flash Ubuntu Touch the phone booted, gave the Google logo for a brief second, then entered the bootloader with the message "ERROR: LoadImageAndAuth Failed: Load Error".
@flohack From a fresh Android install renaming the files to .bak boots into Android with no issue.
@flohack Similar issue to before, after flashing and executing "adb reboot" the phone boots to the Google logo, sits there for 10-15 seconds, then enters a bootloop that eventually stops after 6-10 times in the bootloader with the message "ERROR: Slot Unbootable: Load Error".
dmesg -w did seem to see the device, here is a sample of the last few lines of output.
Device= 1.00
[ 1873.652354] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1873.652358] usb 1-2: Product: Android
[ 1873.652361] usb 1-2: Manufacturer: Google
[ 1873.652363] usb 1-2: SerialNumber: HT7B91A02053
[ 1928.488153] usb 1-2: USB disconnect, device number 18
[ 1934.316312] usb 1-2: new high-speed USB device number 19 using xhci_hcd
[ 1934.466876] usb 1-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.04
[ 1934.466882] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1934.466885] usb 1-2: Product: AOSP on walleye
[ 1934.466888] usb 1-2: Manufacturer: Google
[ 1934.466890] usb 1-2: SerialNumber: HT7B91A02053
[ 1988.502910] loop: module loaded
[ 1988.556171] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[ 2202.191956] usb 1-2: USB disconnect, device number 19
[ 2596.561839] usb 1-2: new high-speed USB device number 20 using xhci_hcd
[ 2596.710679] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[ 2596.710686] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2596.710690] usb 1-2: Product: Android
[ 2596.710693] usb 1-2: Manufacturer: Google
[ 2596.710695] usb 1-2: SerialNumber: HT7B91A02053
@foust No, the Nexus 5X is not currently a supported device. You can find supported devices here: https://devices.ubuntu-touch.io/.
Here is a forum thread where the developer who was previously working on it mentions the issues that he was having at the time: https://forums.ubports.com/topic/971/nexus-5x-development/10.
@Flohack is this helpful information? I can check other things with some guidance.
@flohack In one of the last reboots it did show up under dmesg -w, before then nothing. This is the output I get:
[ 1406.708600] usb 1-3: new high-speed USB device number 14 using xhci_hcd
[ 1406.861398] usb 1-3: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[ 1406.861403] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1406.861406] usb 1-3: Product: Android
[ 1406.861409] usb 1-3: Manufacturer: Google
[ 1406.861411] usb 1-3: SerialNumber: HT7B91A02053
[ 1438.401554] usb 1-3: USB disconnect, device number 14
After that, I get a message in fastboot to the effect of "Slot unbootable".
No luck installing on my Pixel 2 (walleye). I started with the August 2019 9.0.0 factory image, installing from Debian 10. The system never booted into Ubuntu Touch after following @Flohack's instructions in the "Call for testers" thread.
I would get the Google splash screen for ~30 seconds-2 minutes, and then the phone would reboot ad infinitum (well past the 2 reboots threshold).
Any suggestions or success stories Pixel 2 (walleye) installs are appreciated!
@ragz I have used Ubuntu Touch on and off for the past year or so on different devices, although I am not currently using it (I am running CalyxOS on a Pixel 4a).
Phone functionality worked fine for me on an AT&T MVNO when I had my SIM card in a Nexus 5 and later a OnePlus 3 running Ubuntu Touch. The biggest hurdle to get over is the limited applications available on Ubuntu Touch.
Your best bet is to buy a well-supported phone (like a Nexus 5 for something cheaper, or a OnePlus 3/3T for something newer and more powerful), install Ubuntu Touch on it, and try it out.
Is the app still available to download? I admit I am not the most familiar with GitLab but I can't find the click files. 