yashsingh1/xdaforums huggingface dataset:
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 2955732195:
Got some issuse when flashing the lineage os 16

I got a oneplus 5T with the latest verison of H20S and here is what i done :

1.download Gapps and twrp and Lineages OS 16 and Lineage OS addons-su from official site.

2.unlock the oem and flash the twrp and reboot to it.

3.wipe data and cache and system.

4.flash the Lineage OS ,then clean Davilk and cache ,then flash the Gapps,same clean ,then flash the root su addon.

5.after all this done i reboot the device but it automatically boot into twrp rather than the system.

i try redownload all things and reflash but nothing happen.what can i do ?

PS: I flashed a Oneplus 3T at the same time (my friend's device) and successed,but my 5T doesnt work.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] crakerjac:
You are likely encrypted and need to format system. Seems I have to format the disk whenever I change ROMs on an encrypted system. Just make sure you backup your 'SD card' as a format will wipe EVERYTHING.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 2955732195:
Thank for reply ,got some issues here:

today i wipe everything via TWRP but still doesnt work, what does it mean "encrypted" ? is it a fingerprint lock or something like this before i flash the system?but i surely disable and clean all these setting before i unlock the oem

---------- Post added at 04:33 AM ---------- Previous post was at 03:52 AM ----------

GOT SOME NEW SITIUALTION HERE :

IF I DONT FLASH Gapps i can boot to the Lineage OS boot-up screen(the first boot),but after a while it will auto reboot to recovery(i guess this is the phone finished the initial then trying to boot to system but failed ?)

i will try to change a diffrent version of lineageos ,then give the reply ,thanks

-----------------------------NEW FINDING-----------------

1. if i use adb sideload to flash the system, after flash , click "REBOOT--SYSTEM" it will warning you "NO SYSTEM INSTALLED "

2. i change a version of TWRP(unofficial, for encrypted device) , now using twrp-3.3.1-forencryptdumpling-codeworkx (in case of the encryption problem) , and try the following configure :

1. FLASH ONLY THE Lineage OS , it successed.

2.FLASH Lineage OS+Gapps, it failed as the same.

3.FLASH Lineage OS+AddonSU, it successed.

4.FLASH ALL THESE THREE THING, it failed and behave the same as the old version of TWRP.

so i guess its the gapps who cause this problem. but im using the right version of gapps,and it can successfully instaled to the phone.

The Problem here is that i need all these three thing to be installed ...What can i do for this ? (Gapps for Android9 stock arm64+AddonSU arm64)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] crakerjac:
[MENTION=9085714]2955732195[/MENTION], by default, Android is encrypting the device unless you specifically tell it not to. I don't know if it just encrypts the SD card or the system partition as well, but it's more than just the finger print lock. Older Android phones did not do this (by default) and it tends to lead to behaviors like what you are seeing.

For example, came from MSM Extended. When to migrate to LineageOS, I did a factory reset, flashed the FW, LineageOS then GAPPS. When I went to reboot, it brought me back to TWRP (same as you). I had to go into Advanced in TWRP and 'Format Data', which wiped my SD card (actually just user memory, but Android calls it the SD card). I then pulled the zip files back over via ADB, reflashed and I was up and running.

Is there any reason you are running AddonSU vs Magisk? Shouldn't you boot and run through the Android setup before flashing this anyways?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] 2955732195:
sorry for giving a such delayed replay.

Im busy these days but i found that use codexwork's encryption TWRP works for me . As the AddonSU, i just thought that its release by lineageos team ,and it may has more stability or so....and i remember the offical document for AddonSU says that : FLASH AddonSU before your first boot or the system will crash and bootloop unlease you do a factory reset in TWRP. so i flashed it at the very begining
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Martezgarki:
I faced the same issue with you. It wasn't caused by recovery version itself but it's broken Open GApps. I wasted a lot of time figuring out what's the cause, trying out variants of Open GApps to no avail, only to realize that some members mentioned you have to use older GApps (6th Oct release) few pages back. One of the reddit threads also mentioned this: https://www.reddit.com/r/LineageOS/comments/e6n0l4/warning_open_gapps_build_20191204_fails_to_boot. Sideloaded 6th Oct release instead and booted up fine. Would be immensely helpful if this was included in first post but I guess they should fix it soon.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] samnangseng:
Is the full screen gesture similar to OOS work on this rom? That's the only one feature that retain me from using this best rom.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] LV198:
Just Install the XDA "Navigation Gestures" app from Google Play. Works similar but has a lot more features for personalisation :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] angry_goldfish:
Today I tried upgrading from lineage-16.0-20190908-nightly-dumpling-signed.zip to both lineage-16.0-20200120-nightly-dumpling-signed.zip and lineage-16.0-20200122-nightly-dumpling-signed.zip. This failed with the system auto-rebooting to recovery when Linage failed to boot.

I think these recent nightly images are just broken or require a full data wipe/reset.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Prometheus:
If you tried it with 23rd GApps then GApps are the problem.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] angry_goldfish:
I actually did download the 23rd's pico gapps, but I don't think that's the problem because I flashed without gapps for testing and it still had the problem. Further yet, I believe I flashed my old image with the 23rd's gapps and it was okay. In all I tried upgrading something like four times before I gave up. I just went back to my old nightly image and it was fine.

I have had similar problems with gapps in the past, so I had that in mind when I was trying to install.

I'll try with another set of images in a few days and if that doesn't work I'll try and figure out what it is from my /data/data that's buggering it all up.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] gene2:
What is the difference between the official twrp and the other twrp from codeworkx? i had problems with the official one. after booting the stock rom twrp was replaced with the stock recovery. twrp has write permissions. After flashing magisk.zip before booting the stock rom for the first timesolved the problem. Then i flashed lineage os 16.0 with that official twrp, wiped cache/data but the custom roms isn't booting. it ends with the lineage boot screen, then twrp starts. is this because of the wrong twrp?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Lex_Michdeandroid:
I'm not sure if I'm old fashioned because I'm running Lineage 16 still, but I do so here I am.

This phone should have 4K DCI ability (or am I wrong?), but I only see 4K UHD. Also in OpenCamera I can't use DCI, just 4K UHD.

Does anyone know how to get the thing filming in DCI?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Mentor.37:
very low volume

Hi [MENTION=317165]giorgiosimeoni[/MENTION], same problem here, first calls with my 2nd hand opo5t with lo16 and the sound is way too low, obviously in the settings everything is already at max. Did you solved the problem? Is it an hardware or software problem?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] juan_rugge:
I just want to thank you. i'm really enjoying my phone again. ever since i update to stock Pie, my 5t felt like a mid-range, full of lag. LOS runs very fluid, and the battery it's AMAZING!!

BIG THANK YOU <3
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Lex_Michdeandroid:
So I wanted to backup my phone in twrp for the first time, but it gave me an error. (createtarfork 255 something)

It also asks me for the decryption pattern, but my usual pattern I use to open my phone doesn't work.

What is going on here?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] crakerjac:
Any reason night builds for this have stopped?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Specu3800:
They've just started releasing LOS 17.1 for other devices, so probably they are working on one for our phone (other OnePlus devices already have it)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] crakerjac:
The maintainer for the 5/5T has already said he is busy with other items and it will likely be a while before we get an official LOS 17.x.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Lex_Michdeandroid:
I'm getting the idea this phone isn't really popular in the community...
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] IanTester:
That's a shame. There has been an unofficial 17.x ROM but it hasn't been updated since mid January.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] InsaneNutter:
That's by codeworkx (the official maintainer for the 5T) and would eventually become the official rom when it meets the LineageOS charter, presuming development continues.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] JR Bautista:
there's a possible to get lineage os 17.1 for dumpling/cheeseburger?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
Delete
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Larsn_Rinnstroem:
Delete please
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] libove:
First, many thanks to codeworx, for this and everything else!

I switched my OnePlus 5T from OnePlus' OxygenOS to LineageOS 16.0 official for dumpling about two months ago.

Ever since, from time to time, when the screen will turn off either due to a natural timeout, or due to me closing the flip cover, when I turn the screen back on again (either by opening the flip cover, or tapping the power button), the screen will stay frozen at whatever was last displayed on it.

The phone is NOT frozen. It IS sensing and responding to whatever inputs that I'm (dangerously, since I can't see the results) making.

If I tap the power button to turn the screen off and tap it again to turn the screen back on, the screen displays what the phone is really currently doing, and responds normally again.

Interestingly, I saw a post just now in a thread about a very, very different, much older, much lower end device, also LineageOS 16.0, doing what appears to be the same thing - the Wileyfox "Swift" phone ("crackling" branch of LineageOS).

Here is a link to that thread and post: https://xdaforums.com/wileyfox-swift/rom-lineageos-16-0-wileyfox-swift-t3921639/page8#post82456639

Any ideas how to get LineageOS 16.0 on dumpling (and perhaps also on crackling) to fully notice when the screen has been turned back on and continue live updating?

thanks.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] droidsometimes:
I've been having that exact problem since ages, even before LOS 16, on most if not all of my LOS devices, including OP5T, and never managed to get to the bottom of it.

Some days it's happening a lot, other days not so much, some apps are affected, some are not.

Double tapping the recents button also 'unsticks' the screen for me btw.

Do you by any chance have OpenGapps (Pico?) installed?

Furthermore, did you freeze some or all of the Google Framework system apps?

Because that's what I always do, after I have installed all the apps I normally use, and I only ever unfreeze the Google system apps for updating apps via playstore.

And I got the feeling that it somehow is related to the stuck screen problem.

Do you have root on your device, and/or have you looked at the logcats when this is happening?

If so, did you see 'googlequicksearchbox' being mentioned?

Unfortunately, during my time with LOS 15.1/16.0 I never got around to installing LOS without Gapps, to see if it fixes things.

Also, I never let the Google Play services just run without freezing them, because I value my privacy more than a stuck screen from time to time.

About two weeks ago, I started migrating two of my phones to LOS 17.1, and I decided to ditch Google Play from now on, and so far - no stuck screen. Now that might be just coincidence, or because Android 10, but still...
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] libove:
Hi droidsometimes,

I flashed either OpenGApps pico or mini - I'm not sure which.

Next time it happens to me, I'll try double tapping 'recents' - depending on exactly what was on the screen (as in some apps those soft buttons do not appear until the screen is tapped somewhere) it may not be so easy to see/remember :-}.

The device is rooted; I had not thought to try a logcat. My developer years are so far in the past that I'm not sure what I'd look for, or notice if I did see something (especially as I wouldn't know what should/n't be there in the log).

I'm feeling like half of my brain is on holiday - I _may_ have frozen some GApps, but then again since I started quite small, I hopefully didn't have any junkware (like Google Play Music, Google Play Movies) TO freeze. How would I see what apps I have frozen? (Sorry for the stupid question).

However, the _Framework_ apps (Google Play Services, Google Pay, ..) I definitely have not frozen.

By the way, back over on the Wileyfox Swift (crackling) thread, we've determined that what the other user is experiencing on his Swift is NOT this issue. He's seeing a single app window freezing, not the whole screen like this.

cheers.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] libove:
So, the double-tap recents does work. Also, the problem occurred withOUT the screen ever having turned off; I'd not remembered that it could do that. (I have the developer option "Screen will never sleep while charging" enabled, and the phone was on my desktop, plugged in to a charger, with the flip cover open).

I got a logcat shortly afterwards.

The only occurrence of 'googlequicksearchbox' is this, which is probably 10 to 15 minutes before the issue occurred - though I don't recall how long before the issue occurred this time I had last actually interacted with the device, so that's not very diagnostic, I apologise:

05-02 18:19:10.606 1323 1349 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.speech.action.GET_LANGUAGE_DETAILS flg=0x10 } to com.google.android.googlequicksearchbox/com.google.android.voicesearch.intentapi.IntentApiReceiver

I'm hesitant to post a whole logcat, as I don't know whether it might contain sensitive data.

What might I look for to debug the problem?

thanks,
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] droidsometimes:
Maybe do what I did:

Configure the status bar clock to show the seconds, set a short screen timeout, and a long lock timeout.

Then keep using the device normally, but let the screen reach the timeout often, and try to wake up the screen immediately after it goes black - e.g. double tap to wake.

Once the screen gets stuck, memorize or write down the minute and the second of the status bar clock (immediately taking a screenshot might work too) - that way you should get a clue what timestamps to look for in the logcat.

After that has happened several times, compare the relevant sections of the collected logcats, and see if anything sticks out, or is similar across all the collected parts.

Regarding sensitive info in the logcats, for example the app SysLog (F-Droid store) has an option to 'scrub potentially personal information from the logs'.

I've never used that option though, so not sure if it's reliable.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] libove:
*grrr* Wouldn't you know it? The status bar does update - it's just the home page that forgets to update. So I don't get to see a timestamp of when stuff froze. The clock keeps ticking merrily along...

I did take another logcat, and if I have time I'll try to look for clues in there, though it's really needly-in-a-haystack at this point :(
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Thimoteo:
Frequent reboots without reason

I wonder if anyone can help me troubleshoot this problem.

With nightlies downloaded since late 2019 or early 2020, my OnePlus 5T reboots mysteriously, without any action on my part. It might go three days without rebooting this way, or might reboot three times in one day. It happens when the phone is idle, sitting on the table. No calls, no internet use. Just, all of a sudden: reboot.

No Gapps. I'm now on firmware 9.09 and nightly 20200421, version 16.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Thimoteo:
Update: I did a fresh install with the 0421 nightly, experienced new rebooting problems, then installed the 0407 nightly. It is still rebooting a couple of times a day, but now only does so when I'm doing something with the phone: looking at a web page or configuring a program.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
No sweat on my side.

FW 9.0.11 / latest official build / nano open gapps / magisk 20.4

I formatted data (to remove the encryption) then wiped cache, dalvik, vendor and system (ext4 for all) via TWRP (twrp-3.3.1-20190908-0-codeworkx) before flashing build + gapps + los addon su.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Thimoteo:
Thanks for the response, Eric. My steps were almost the same, but I hadn't formatted data or used the codeworkx recovery, so figured I'd start over and follow your steps exactly. I installed the codeworkx recovery, formatted data, wiped cache, dalvik, vendor and system. All ext4.

The codeworkx 20090908 recovery wouldn't install the 20200421 nightly; it insisted my phone is cheeseburger, a OnePlus 5, and not a dumpling, 5T! I checked the receipt and even measured the screen; my phone is definitely a dumpling 5T. First time I've ever seen anything like this. (Edit: the back sticker says it's a model A5010.)

I downloaded and installed the twrp.me recovery for the 5T. It installed the 20200421 nightly without problems ... but the phone started acting up again almost immediately, with a 'Phone is starting ...' loop during the boot.

If you have any ideas, I'd love to hear them.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
XDA for cheeseburger and LOS 16.0 : https://xdaforums.com/oneplus-5/development/rom-lineageos-16-0-pie-oneplus-5-t3843064

Recommended TWRP (codeworkx) : https://sourceforge.net/projects/ch...signed-forcedecrypt-cheeseburger.img/download

Firmware : https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/firmware/

PIS issue is well known and has been reported by several people on several phones (e.g. OP3/3T).

On my side, I was faced PIS more often with Magisk (OP3T and OP5T with LOS 17.1) than with LOS addon su (OP3T and OP5T with LOS 16.0).
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Thimoteo:
Thanks again for the efforts to help, Eric. I hadn't looked up the PIS issue. I'm not alone.

"About phone" also says that my cell is an A5010 5T, and not a 5. The screen dimensions match the 5T, and not the 5. I think I started with Lineage 15 on this phone before upgrading to 16, and never saw any messages before reporting that I'm actually running a dumpling. So I'm reluctant to install a cheeseburger TWRP or ROM.

I installed a Blu Spark TWRP, did a fresh install that way and will try some other steps on my own.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
OnePlus 5T = A5010 ... so your driver is a OnePlus 5T ... dumpling and not cheeseburger !

==> Don't install/flash TWRP and build for cheeseburger (OP5) ... only for dumpling (OP5T) ... of course.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Thimoteo:
I've got everything configured again with the Blu Spark TWRP, and will wait to see if it holds up without frequent crashes.

It's

weird

that the Codeworkx TWRP (twrp-3.3.1-20190908-0-codeworkx) insisted that my A5010 5T is actually a 5 cheeseburger.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
Awaiting the official builds to come back (https://status.lineageos.org/) :

No need to flash a migration_keys script.

Tested from official to unofficial (and vice-versa) on my OP5T (BL unlocked and encrypted) and my OP3T (BL locked and unencrypted).

From official build to unofficial build:

Boot to TWRP

Flash/install my unofficial build (https://androidfilehost.com/?a=show&w=files&flid=309544 - Not signed builds)

Restart to System

roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" />
<project name="LineageOS/android_device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_kernel_oneplus_msm8998" path="kernel/oneplus/msm8998" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>

From unofficial build to official build:

Delete your fingerprints and screen lock before flashing official build.

Boot to TWRP

Flash/install official build (https://download.lineageos.org/dumpling)

Restart to System

Edit : if your screen lock (for me, a pattern) and fingerprints are not restored after flashing official build, a well-known workaround using TWRP terminal or file manager if rooted, is to delete :

the lock screen files

/data/system/gatekeeper.*

/data/system/locksettings.*

and if using fingerprints,

/data/system/users/0/fpdata

/data/system/users/0/settings_fingerprint.xml
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] aftnoon2:
Hi

Where we can find out the latest firmware?

On Sourceforge the latest is 9.0.9, dated back on 2019...

Thanks!

PS Forget it, I've found out.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] ctag:
It looks like the build system is back up and running. Has anyone installed the latest? Is it good to go?
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Eric_Lev:
Yes, you can.
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] frazelle09:
Screen notification for incoming phone call

Is there a setting for this OS so that the screen will display a notification for an incoming phone call? i just set up this OnePlus 5T with the 16.0 and i thought that it came with the possibility of doing this, but i've been through the menus several times, including the developers options, and determine if it's possible or not.

Thanks for the super OS and be happy and ... stay safe! :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] frazelle09:
Dear Fred:

Check here for how to fix this: https://www.guidingtech.com/fix-incoming-call-not-showing-screen/ (i don't know if URLs are allowed so the place is called: guidingtech dot com forward slash fix-incoming-call-not-showing-screen) and basically what fixed it this time was, in storage, clearing cache and clear storage.

Have a radiant evening, stay safe and be happy! :)
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Ramme:
@-OP5t; Version: lineage-16.0-20200811-nightly-dumpling-signed, 2020-08-11

Do you also have the problem, you want to make calls with your headphones (AUX) and hear yourself? The microphone of your cell phone is on even though the headset is connected?

Then I have my solution to this problem:

Go to PlayStore, Download: "BuildProp" > Open the App, accept Root, Click the three stripes at the top left (Menu), Select file..., Go to Vendor and choose > build.prop > SELECT.

Now Search for: "ro.vendor.audio.sdk.fluencetype = fluencepro" and change it to "ro.vendor.audio.sdk.fluencetype = none". Reboot your Phone and enjoy =)

I hope it works for You. It definitely helped Me!
[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Shaneee:
Ok which repos are used for this build so I can check the commits.