Search results

Thanks. I have OP5t, stock kernel, Nikita GC 1.9 (eng version) Followed steps and had exact same problem. Repeated whole clean install, and left XML at basic (rather than loading Nik-1.9 xml). Works flawlessly. I have not yet explored other xml packages, but will do so as it seems the problem...

Downloaded and installed. Gcam (Nikita v 1.9) now force closes after a few seconds displaying black screen within viewfinder area. Tried uninstalling GCam and reinstalling. No luck.

Here it is https://github.com/engstk/android_device_oneplus_cheeseburger/releases/tag/v9.101

Your twrp is massively out of date. Update to latest (v 101). Worked perfectly for 9.05 to 9.06 for me (also encrypted - make sure all magisk modules disabled)

I have used beta, and do not find the auto brightness in stable is problematic. In particular, I do not have problems with display becoming too dim after a while.

I am not seeing this problem in 9.0.4 (and didn't have it in 9.0.3 either). Have you checked in contacts for duplicates? ---------- Post added at 16:53 ---------- Previous post was at 16:51 ---------- I do not see this issue. Display is painfully bright at maximum setting. I have it at...

The hotfix referred to in this post is 9.0.2

Working perfectly for me on 9.0.1 , switches automatically with designated app, remains monochrome till app exits. I know there was a bug in 9.0.0, but I didn't try it while on that version.

Or just use the latest blu 9.91 twrp, which removes the need to worry about compatibility. . . . . . https://forum.xda-developers.com/devdb/project/dl/?id=31102

Simply not true. It may have caused you problems, but my dirty flash worked perfectly using standard procedure that I have followed with Nougat and Oreo.

r136 for OOS Treble (as 5.1.6 is a treble enabled release)

Same for me: no need for uninstaller, installing full zip and Magisk 17.3 (and in my case blu_spark kernel) without reboot to recovery between, worked fine. YMMV if you have any active Magisk modules - I don't

All perfectly fine for me. Usual flash of ROM, Magisk, blu-spark kernel, and reboot. No freeze/restart etc.

Decrypts fine with screen pattern for me (as it has for many earlier versions of the bluspark recovery). Are you using version 8.83 of recovery?

5.1.5 installed fine with latest TWRP, and reboots into recovery with (obviously) no more /vendor errors. 128 treble kernel installs and runs perfectly ---------- Post added at 11:26 ---------- Previous post was at 11:17 ---------- And for latest stable 5.1.5 as that is also treble ready

Sorry you're having problems. Text have continued to work fine for me after update to 5.1.4, so not something inherent in the update

This has been so useful and interesting in the past - thanks! Should I give up hope for 5.1.2 and, now, 5.1.3? I do hope not . . . . :fingers-crossed:

See screenshot

The system boot after flashing ROM is not necessary. Provided Magisk modules have been removed, flash ROM + Magisk 16.0, then reboot to system. All will be well, and root retained. Then you can install Magisk modules if you want.

It's now openly available on the oneplus site. http://downloads.oneplus.net/oneplus-5t/oneplus_5t_oxygenos_5.1.1/

Odd. I had the problem once only - on first boot. On every subsequent boot, Smart Lock has just worked as normal.

I have also had problem with Smart Lock being completely blank after first boot after flashing. However, I merely rebooted, without disabling, and it's working fine now.

Latest stable version (16.0) is working fine for me, as it did with 5.0.4

Sorry you are having a problem. Safetynet is passing fine for me, after dirty flash from 5.0.4. Google Pay also working fine.

I can confirm that these steps worked this morning for me (although I am using Magisk 16.0 (stable) rather than 16.3 (beta).

Yes - replaced by tilt to wake.

I had the same issue with the camera. I gave up after the second reboot, so can't confirm that it then worked. Is it now working normally for you?

Sorry, I did not express myself clearly enough. The Lineage persistent SU works for all official builds that exist (and there is not YET one for the SM-T520 / n2awifi) as well as for unofficial builds such as the one this thread is about. Persistent SU seems like an obvious bonus to me - means...

And if you use the persistent SU from lineageOS, there's no need to reinstall after each new zip. Works perfectly with these unofficial builds as well as the official ones.

Me too. I have never yet had a problem dirty flashing within one level of Android. Indeed I went from CM13 to 14 without wiping (other than cache and dalvic). Always ready to clean flash if necessary, but my so far successful approach has been "why bother"

Does the Lineage root zip work on a once only install? Instructions at Lineage say it does with official builds: "Root will be a downloadable zip based install similar to gapps installation (only need to flash it once)." Their root zip is on the downloads site. If no-one has checked it, I shall...

I have same build and gapps - but no sign of the video or sound stuttering problems EDIT: I take it back. I do have the zoom problem in the Netflix app.

Took android and titanium backups, just in case, then flashed over CM13 with no wipe/factory reset. Been running perfectly for 24 hours. I'm massively impressed, and very grateful!

Yes, but its title includes "New Official N(7.0) Update" Make of that what you will. It's there for OTA anyway

Official update is out Downloading now. Only 118 MB from OB8 :)

SIM and network settings / SIM 1 (or 2) sent from my Oneplus 3

Oh yes - see it's still there in the FAQ. Nevertheless, I can definitely confirm that it is not necessary to unlock bootloader to sideload the community build using stock recovery and the instructions on the download page

The instructions used to say you had to be unlocked, and it put me off for quite a while. When I queried it, the instructions were changed. So, moving to a community build is simple and doesn't lose apps or data or settings. However, it is still suggested that moving the other way does wipe...

white43 Not so. Unlocked bootloader is not needed to flash community builds by adb sideload. And remaining locked has the advantage that Android Pay continues to work.

You can unstall it using ADB sideload on a totally stock phone, without rooting or unlocking the bootloader. I did this, with no adverse consequences, no loss of data, or any problem. Instructions are here

I used to have this problem with my dual sim HTC M8 - because only one sim could be run in 3G/4G. Be reassured, I now can run a 3 sim happily as second sim, the OP3 allows the second sim to run in 3G.

As it does on mine, but not sure that's relevant. The line surely relates to VOLTE, rather than LTE. As EE haven't enabled VOLTE for handsets they haven't sold themselves, I can't check whether it's working OK.

Mine are unchanged from 3.2.1 to 3.2.2: all - priority - silent

And now I can confirm, you are not alone! After reporting that I was no longer having problems, during the course of a 1000km drive in the last 24 hours I had three occurrences of the 'lost SIM' phenomenon. :( Unfortunately, as I was driving it was not possible to take any logs - but I can...

Can't say if you are the only one, but I've not had this problem since the new blobs were incorporated into the build. If you are updating to the latest nightlies, then can't explain your problem. Of course, if you wanted devs to look at the issue, a starting point would be to post a log from...

Hard to prove the absence of an intermittent problem, but if the new blobs were in the 26 May nightly the signs are good. All working faultlessly so far - but I'm not travelling so conditions are different . . . .

Thanks very much. During 600km drive yesterday my 24 May lost SIMs irretrievably three times. Eventually I gave up and re flashed with 17 May. All has been fine since. Sorry no logs - hard when driving and relying on phone for navigation. Hopefully the new blobs will resolve - although problems...

That'll be interesting. I've also been losing SIM contact recently - always sortable by rebooting, but irritating nevertheless. Thanks for the continuing work!

If you check your baseband version, it should be 1.24.30336021.13G_30.69.336021.00_F

Ah yes, I see the radio didn't change between 5.0.2 and 6.0