@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?

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.

@lakotaubp sorry about that. I cleaned it up a bit more.

The phone had enough charge, over 70% and connected to the laptop. To be sure, I plugged it into the mains.

I might have messed up here...

Got a new OnePlus 6T in the mail today. It has Android 9 on it. I enabled developer mode and USB debugging. The UBports installer (on a Ubuntu host) picked up my device and restarted it into fastboot(?). It asked me to unlocked the phone and I agreed, but failed.

I can't select/copy/paste, but the relevant parts are: cmd: fastboot oem unlock and Flashing Unlock is not allowed

I searched a bit how to get into fastboot myself. Restarted the phone and booted into Android without issues. I Installed locally android-tools-adb android-tools-fastboot and adb devices listed the phone.

Then shut it down to try the vol up + vol down + power button combination, but it doesn't respond to that. In fact, it doesn't respond to any button presses at all anymore. Not the normal power button, no combintion, nothing. Just a permanent black screen.

What might have gone wrong, or better, how can I recover from this?

Since the update to OTA-24 on my OnePlus One, some websites are very laggy. It takes a lot of time and choppiness to scroll down.

The most obvious pages and easy to reproduce are on IMDb. Every page of an actor/actress has the same issue as mentioned above. It's only until a bit further down the page, the scrolling behaves normal again. I think after the header(video) is out of screen. Similar for pages of movies, only the other way around. It starts off fine, but gets laggy further down, around the reviews section.

I've noticed the same problem on pages where a Twitter post with a video is embedded. Like in a news article.

Does anyone else experience the same? I guess WebView had an update, as I see other small changes as well. Like the background color being white in incognito mode, even if the system's theme is dark. Also in Quickddit when a video is loading the background is now completely white.

@hekathegreat I have only "StevenBlack Unified" enabled and it seems to work pretty good.

Note that this choice was made more by chance than knowledge.

For me it's the other way around, it's too loud. My BQ4.5 and then Nexus 5 were fine, but not the OnePlus One I bought last year. The volume is two clicks (taps/levels) up from completely off, and I always jump a bit when the alarm goes off for example. Also the vibrations are much more powerful than the other phones, which is sadly not configurable last time I checked.

@danqo6 One other thing: videos from Youtube and Streamable don't work anymore.

Since the UBports OTA-16 update, emojis seem to be rendered in the wrong location. Maybe due to the Qt update? They show up higher and perhaps a bit more to the left than they should be.

It also seems that NSFW subreddits aren't shown anymore when browsing /r/all. Maybe an idea to add a toggle/switch to the settings to allow them.

Another feature/idea: let the user enter a subreddit to go to. The search sometimes doesn't list them, even though they exist. So there's no way to visit a subreddit that's not found.

I recently switched from a Nexus 5 to a OnePlus One. The vibration intensity is much higher, if that's what it's called actually. It can get pretty annoying. Is there a way to change this?