Not really features, I'd like to see more development on the basics. Two things that quickly come to mind:

1. Improved performance: less RAM usage.
2. Bugfree experience for the 3 listed core devices.

An adblocker in the webbrowser is something I really miss.

Good news. I was able to boot again and installed UBports eventually.

I tried many times, multiple variations, but in the end this combination finally worked:

• disconnect the phone from any cable (laptop, mains)
• hold volume up + power button for 12 seconds

Not sure if it was a fluke or the actual solution though. Hope this helps someone in the future.

@ziggutas It's always a phased rollout. This is mentioned in the release blogpost:

OTA-7 is appearing as a staged rollout for all supported Ubuntu Touch devices over the next 5 days, completing on Sunday, January 13.

@rocket2nfinity The little dots that make the circle are the days of the month, one of them indicates which day it currently is. The bigger, different size circles around it is the amount of the current selected option was used before. The bigger the circle, the more it was used.

It kind of works in your example with a dark background. But I still have the default white-ish background and think the text in the dropdown will become hard to read. Maybe post a screenshot of that too?

@Opolork said in Can open Reddit on PC but not on FP2 running UT.:

I'm using the uAdBlock app - could that be a possible cause?

Yes. I had the same problem after enabling the "StevenBlack Social Hosts" blocklist. May be others block it too.

@wgarcia Thanks for moving the discussion, but most of these issues are already reported on GitHub and I reported them here somewhere already some time ago.

1. LED: https://github.com/ubports/ubports-touch/issues/48
   A bit cumbersome to frequently enable the screen to see if there's a missed notification. The blinking green LED like the BQ would be great.

2. Call volume: https://github.com/ubports/ubports-touch/issues/137
   This can get very troublesome when there's some background noise in the room. Sometimes it's almost impossible to hear the other person properly.

3. Beep: https://github.com/ubports/ubports-touch/issues/49
   Just a small annoyance, although the beep can be very loud depending on where you are :-).

4. WiFi disconnects: I'll have to describe it properly and submit a bugreport
   This is a big issue for me. When the extender has stronger signal than the router, the phone disconnects and wants the password again. This means I can't move around the house without getting disconnected all the time (30+ times/day). The BQ would just seamlessly switch over. I see you even have issues without extender. After disconenction it should just autoconnect without requiring a password again (it is saved already!).

@vadrian89 It has to do with a couple of things as far as I know. The size and colour of the circle has to do with the amount and also time it happened. Last month is calculated as well.

Just type "what is my user agent" into Google, it'll tell you as well.

Do sites think that I'm visiting in with Linux Mobile or do they think it's Android OS?

Most will think you're running Android because they're either lazy, incompetent, or ignorant.

The user agent contains something like "Linux Ubuntu like Android". Devs just do a quick check, see that it contains "Android" and assume that's what's running.

@MrT10001 Ok, going through the updater in the system settings worked fine. Thanks, looks like I have a working up-to-date system now. Couldn't get it going through the installer though.

I've never came around to do the update, so I'm still running Xenial but it's probably time to take the plunge.

After reading a bit, it seems like going through the installer is the best route. However I can't get it to work. We all know about the reboot bug. This appears to be causing issues. In the installer, depending if you tick bootstrap, it'll either try to reboot the device in fastboot or recovery mode. The device switches off, but never comes back on. So I have to unplug, press vol-up+power and it boots again, but of course the installation is interupted.

How did everyone here did the update?

Just type "what is my user agent" into Google, it'll tell you as well.

Do sites think that I'm visiting in with Linux Mobile or do they think it's Android OS?

Most will think you're running Android because they're either lazy, incompetent, or ignorant.

The user agent contains something like "Linux Ubuntu like Android". Devs just do a quick check, see that it contains "Android" and assume that's what's running.

@Ian This is how I "fixed" it previously and was going to comment this as well I had the same issue right after switching phones, so I blamed it on the phone (OnePlus One) back then. It was only after a long time I found those clock settings.

@Hugehead I use the following script on my 6T with Xenial: https://github.com/JamiKettunen/lomiri-notch-hax

Icons are still hidden underneath the notch, but atleast it pushes the notification envelope enough to the left.

@MrT10001 That didn't work either.

However...

I was able to boot into fastboot mode by pressing power+vol_up+vol_down. No idea why it worked now. Then I just reinstalled through the installer.

Something weird though, the installer said the device "sdm845" isn't supported. So I manually picked it from the list.

Anyway, I'd like to thank you for the prompt replies. It's very much appreciated.

@MrT10001 I see the OnePlus logo and then always end up stuck at the bootloader screen (image found online).

Edit: pressing the power key as stated in that message does nothing.

@MrT10001 The problem is I can only boot to the (unlocked) bootloader. No matter the key combination. No fastboot and developer mode was not enabled in the settings. So the installer can't find the device.

@Moem @MrT10001 I tried this multiple times.

The device only shuts down with power+vol_up or power+vol_down, not with just power.

Then booting with either of the three combinations still results in the stuck bootloader.

I got a notification about OTA-25, clicked to install and the device rebooted. It went on for a few minutes on the update screen, I think, the one which looks like three connected circles which "pulse" a bit. It rebooted again and is now stuck on the bootloader screen. The one with the warning message about the bootloader being unlocked.

Any one else with this problem or even better, a solution?