[12.1][OFFICIAL] LineageOS 19 for Oneplus 5 & 5T

Search This thread

Digitalralf

Member
Jun 20, 2013
25
4
I am running a stock install of OOS 10 with the bootloader unlocked (OP 5T).
The instruction on https://wiki.lineageos.org/devices/dumpling/install says I have to clear the internal storage, but the instructions are made with Lineage Recovery.
Can I just do a wipe of System,Data,Dalvik and Cache on TWRP without the internal storage and then just flash or isn't that possible because of th Android 12 encryption?
 

RomThu

New member
Jun 21, 2022
3
0
I am running a stock install of OOS 10 with the bootloader unlocked (OP 5T).
The instruction on https://wiki.lineageos.org/devices/dumpling/install says I have to clear the internal storage, but the instructions are made with Lineage Recovery.
Can I just do a wipe of System,Data,Dalvik and Cache on TWRP without the internal storage and then just flash or isn't that possible because of th Android 12 encryption?
I did somehow the same from LOS18 to 19
Wiped everything except internal storage, it kept my movies just fine.
 

digger16309

Senior Member
Jul 17, 2014
462
168
OnePlus 5
Google Pixel 5
I just revived my OP5 with this ROM and I'm using it as a backup phone/device. I'm rooted and also installed the latest working TWRP recovery. I've been on stock ROM on a Pixel 5 for awhile and haven't kept up.

I see the link to the update instructions but they don't mention root. Can I take system updates of LOS 19.1 without affecting root or sending me into bootloop? Or do I need un-root first and then update and manually patch the boot image, etc...?
 

Ssmiles

Senior Member
Nov 19, 2015
125
61
France
https://forum.xda-developers.com/t/12-1-official-lineageos-19-for-oneplus-5-5t.4353295/post-87026601


 
Last edited:
  • Like
Reactions: digger16309

scruffy1

Senior Member
my problem is that i accidentally turned the screen brightness so low that i can't see the slider to turn it back up!!!

can get into recovery, and reflashed hoping it would reset that, but after the initial splash screen it's darkness as usual

how do i get the screen up if i don't know where the slider is?????
 

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
my problem is that i accidentally turned the screen brightness so low that i can't see the slider to turn it back up!!!

can get into recovery, and reflashed hoping it would reset that, but after the initial splash screen it's darkness as usual

how do i get the screen up if i don't know where the slider is?????
Did you ever get adb setup with the phone and trust some computer? If so you can maybe use something adb to change brightness
 

scruffy1

Senior Member
thanks for the comment

i knew vaguely where the slider was, but was trying too high on the screen, and eventually discovered that it is pretty much level with the lower end of the alert slider (on the left), a bit lower than where i thought

alacazam! lights are back

what i don't understand is why the minimum brightness is not locked to a visible level, albeit very dim

making the screen completely dark serves no purpose other than to cause a predictable problem
 
Last edited:

Badtz-Maru

Member
Aug 13, 2016
21
5
Oh man, I don't get it! When rebooting, the time is always 08:11:30. No matter what I set! If I set it to "set time automatically" after the reboot it is first briefly at 08:11:30 and then at wlan system time.
The problem, I don't have WiFi in the car, I would have to make a hotspot with my DalyDriver Phone (Nord2) every time so that the time in the dashcam app is up to date.

Why is that ? Is that a bug?
 

InsaneNutter

Senior Member
Jun 26, 2010
182
116
Yorkshire
Thank you for all your hard work T1mb3, I've just updated from LineageOS 18 to 19 following the official instructions.

Everything went well, my LineageOS 18 install was an upgrade from LineageOS 17, so its been good upgrading through multiple versions without having to wipe anything.

I had to uninstall / re install Google Pay after upgrading from 18 to 19 and setting Magisk up again. Pay got stuck saying the app was updating, even after clearing the data / cache. However all was fine after re-installing from the Play Store.

For anyone who's wanting to pass SafetyNet to play games such as Pokemon Go or use Google Pay, I've updated my tutorial for cater for Magisk 25.1 using the Universal SafetyNet Fix and MagiskHide Props Config plugins: Play Pokemon Go with a Custom Rom or Root - LineageOS 19 / Android 12 How To.
 
  • Like
Reactions: Badtz-Maru

scruffy1

Senior Member
thanks for the above

can you point me to a resource that explains why i might like magisk on my phone?
i am no noob, and although i see magisk getting a lot of love and mentions, i am still a bit gormless as to what it actually does

my best guess is that it lets me add features to a custom rom while retaining that rom otherwise intact

is that right?
 

InsaneNutter

Senior Member
Jun 26, 2010
182
116
Yorkshire
@scruffy1 in some ways it would be nice not to need Magisk, however Magisk is essentially a way of allowing installed apps to obtain root access. This for example can allow apps to do things they couldn't normally, such as to backup the data of other installed apps. You can also load modules with Magisk which add functionality otherwise not possible, this could be something simple like changing the emoji font, or something more complex like tricking Google's SafetyNet checks so your device can pass them.

For me personally I need Magisk to pass Google's SafetyNet checks, this is because I play a game (Pokemon Go) which refuse to work if the device fails to pass SafetyNet. In addition I also use Google Pay for contactless payments, which also requires been able to pass SafetyNet. Many banking apps implement SafetyNet checks also.

Hopefully that's some insight on why people might use Magisk anyway, if you don't need Magisk then that's not a bad thing at all.
 

Ssmiles

Senior Member
Nov 19, 2015
125
61
France
UPDATE lineage 19.1 ADB OnePlus5 Cheeseburger Encrypt WINDOWS

1) Reboot into TWRP recovery
2) Flash lineage-19.1-20220704-recovery-cheeseburger.img
3) Reboot into lineage recovery
4) Apply update
5) Apply from ADB
6) Copy paste lineage-19.1-20220704-nightly-cheeseburger-signed.zip and Magisk- v25.1.zip and twrp_op5_op5t_3.6.2_12.1-test-v6.img files in adb folder in C:\adb
7) Open CMD in administrator mode
8) cd C:\adb
9) adb devices
10) adb sideload lineage-19.1-20220704-nightly-cheeseburger-signed.zip
11) adb sideload Magisk-v25.1.zip (if error force install)
12) Reboot OnePlus 5

Install TWRP Recovery FASTBOOT WINDOWS

13) Reboot in fastboot mode
14) Open CMD in administrator mode
15) cd C:\adb
16) fastboot devices
17) fastboot flash recovery twrp_op5_op5t_3.6.2_12.1-test-v6.img
18) Always from fastboot mode on the OnePlus 5 reboot in recovery mode

TWRP is back ;-)​

To be redone with each lineage 19.1 update to keep the TWRP recovery mode


 
Last edited:
  • Like
Reactions: digger16309

Gaukler_Faun

Senior Member
Aug 10, 2012
701
1,435
Germany
github.com
I just revived my OP5 with this ROM and I'm using it as a backup phone/device. I'm rooted and also installed the latest working TWRP recovery. I've been on stock ROM on a Pixel 5 for awhile and haven't kept up.

I see the link to the update instructions but they don't mention root. Can I take system updates of LOS 19.1 without affecting root or sending me into bootloop? Or do I need un-root first and then update and manually patch the boot image, etc...?
Hi,

I'm also new on this phone. I'm rooted with Magisk am I'm on latest TWRP. Yesterday I just applied a system update via the internal updater in the settings. All worked fine. After the update root was NOT lost.

And even if you loose root, you can flash Magisk again via TWRP to obtain root again.
 
  • Like
Reactions: digger16309

InsaneNutter

Senior Member
Jun 26, 2010
182
116
Yorkshire
When split screening apps using a 3rd party launcher upon returning to the home screen and pressing the task switch button, the top and bottom half of the screen show the top pinned app's icon, however the app switcher UI seems to render in the tiny bar dividing the two screens.

However if setting Trebuchet as the default launcher again then its possible to cycle though the app switcher and split screen apps ok.

This doesn't always happen, however I've managed to replicate this a few times in recent days on various 3rd party launchers. It seems possible to swipe up and close all running apps, which then seems to restore functionality to the app switcher.

Screen recording of the issue here:


Edit - This only seems to occur when using 3-button navigation and a 3rd party launcher. Changing to 2-button navigation seems to resolve the issue with split screening and using a 3rd party launchers.
 
Last edited:

AdamWill

Senior Member
Jan 23, 2009
289
47
Vancouver, BC
www.happyassassin.net
I noticed a slight niggle after running this version for a few days. Since the upgrade, the camera app stores pictures in the Pictures folder, not DCIM/Camera like it used to. But the Gallery app will only show pictures from DCIM/Camera in the "Camera" album.

I can't find a way to change either where the camera app stores pictures, or where the gallery app's "Camera" album looks for them. Has anyone figured out a solution to this? Thanks!
 

avuman

Member
Jan 10, 2012
37
4
Sorry, this is a noob ass question. Does LineageOS 19 able to de-encrypt the hard drive? I use my OP5T for work (with a work profile), and it requires me to encrypt the hard drive.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I've been having a lot of random freezes. It seems to happen no matter what app I'm running, and happens up to several times per day. The whole phone will just lock up for several seconds, and after it resumes, it acts like it thought the app itself was crashing and gives you the option to force close the app, but since it happens on every app, it doesn't seem to be related to any app. So I was wondering if this was an OS thing, or possibly a MindtheGapps thing. I have been having this issue ever since I installed LOS18, and I was hoping upgrading to 19 would solve it, but the same issues are happening. I was able to grab a logcat shortly after it happened, and this appears to be the relevant section, since it shows how it was assuming the facebook app was not responding:

    Code:
    07-08 16:45:13.075  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
    07-08 16:45:13.077  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
    07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.078  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
    07-08 16:45:13.079  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
    07-08 16:45:13.080  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
    07-08 16:45:13.082  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
    07-08 16:45:13.082  1486  5343 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
    07-08 16:45:13.083  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
    07-08 16:45:13.114     0     0 W [20220708_16:45:13.114251]@7 healthd: battery l=95 v=4040 t=32.9 h=2 st=3 c=644000 fc=2878000 cc=0 chg=
    07-08 16:45:13.172  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604736
    07-08 16:45:13.174  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684926
    07-08 16:45:13.175  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.178  1486  8913 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286683780
    07-08 16:45:13.180  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657286684638
    07-08 16:45:13.182  1486  4518 W AppOps  : Noting op not finished: uid 10105 pkg com.google.android.gms code 79 startTime of in progress event=1657311604922
    07-08 16:45:14.411     0     0 E [20220708_16:45:14.410288]@4 synaptics,s3320: all finger up
    07-08 16:45:18.905  1486  2212 I WindowManager: ANR in Window{58f11e7 u0 com.facebook.katana/com.facebook.katana.activity.FbMainTabActivity}. Reason:58f11e7 com.facebook.katana/com.facebook.katana.activity.FbMainTabActivity (server) is not responding. Waited 5001ms for MotionEvent(deviceId=2, eventTime=245003958749000, source=0x00001002, displayId=0, action=MOVE, actionButton=0x00000000, flags=0x00000000, metaState=0x00000000, buttonState=0x00000000, classification=NONE, edgeFlags=0x00000000, xPrecision=1.0, yPrecision=1.0, xCursorPosition=nan, yCursorPosition=nan, pointers=[0: (800.0, 1242.0)]), policyFlags=0x62000000
    07-08 16:45:18.943  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10107; state: DISABLED
    07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10107; state: DISABLED
    07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10107; state: DISABLED
    07-08 16:45:18.944  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10107; state: DISABLED
    07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10107; state: DISABLED
    07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10199; state: DISABLED
    07-08 16:45:18.945  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10199; state: DISABLED
    07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10199; state: DISABLED
    07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10199; state: DISABLED
    07-08 16:45:18.946  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10199; state: DISABLED
    07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042980; UID 10193; state: DISABLED
    07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 181136395; UID 10193; state: DISABLED
    07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 174042936; UID 10193; state: DISABLED
    07-08 16:45:18.953  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 184838306; UID 10193; state: DISABLED
    07-08 16:45:18.954  1486  2212 D CompatibilityChangeReporter: Compat change id reported: 185004937; UID 10193; state: DISABLED
    07-08 16:45:21.902  1486  4518 W ActivityManager: Missing app error report, app = com.facebook.katana crashing = false notResponding = true
    07-08 16:45:21.905  1486 21220 I ActivityManager: dumpStackTraces pids={2747=true, 2899=true, 3340=true, 3366=true, 3637=true, 3639=true, 4039=true, 4076=true, 4989=true, 9573=true, 10461=true, 10486=true, 10582=true, 10686=true, 10852=true, 11293=true, 11524=true, 12229=true, 12264=true, 12279=true, 13724=true, 13863=true, 13986=true, 14098=true, 14752=true, 15057=true, 16365=true, 16595=true, 16600=true, 17252=true, 18902=true, 19018=true, 19160=true, 19222=true, 19462=true, 20948=true, 21038=true, 21077=true, 23830=true, 24484=true, 25610=true, 26989=true, 30766=true, 32624=true} nativepids=[582, 609, 615, 766, 767, 853, 894, 933, 937, 938, 940, 979, 1034, 4989]

    Is this an issue anybody else is having? I tried searching the thread but didn't see anything. Is it possible that there's something wrong with my phone itself?

    Another, possibly related, possibly unrelated issue will happen sometimes, the home button / fingerprint scanner will become completely unresponsive for a few seconds, but everything else about the phone works perfectly normal.

    Here's the full logcat in case additional context is needed:
    2
    i just installed paypal and i have no problem on the latest update
    2
    I'm sorry, but if you react like that, nobody will probably ever help you.
    1
    My and the current users observations related to this:
    • No such issue on LOS 18.1 and before (with dirty upgrade from LOS 16 and LOS 17.1) using OpenGApps on 16 & 17.1 and NikGApps on 18.1.
    • On LOS 19.1 using NikGApps (fresh install after upgrade due to new user), some kind of hanging when using the quick access top menu and swiping it back up. The quick access menu remains visible half for a bit.
    • Not anymore reproducible (yet?) since update to latest LOS 19.1 build today.
    Could there be an issue with MindtheGapps? Perhaps I should try OpenGapps. I used to use that on my old device, but I noticed the recommendation changed on the wiki when I decided to switch from OOS to LOS on my OP5.

    As for LOS, I'm on the June 20th nightly, and the same date MindtheGapps, but like I said this was something I experienced in 18.1 as well. I can certainly try the new LOS nightly.

    My freeze issue affects the whole phone. Can't tap the physical buttons, cant tap or swipe anything on screen, and any animation that was playing hangs until the the freeze is over. Although sometimes I can still swipe the top menu down while everything else is frozen, but it usually freezes shortly after as well if so. The whole phone hangs for maybe 10 seconds or so, sometimes less, sometimes more.
    1
    Checked with the current user and the described - not reproducible at the moment - behavior was:
    • Screen not responsive.
    • Home button responsive - and way out of situation.
    So, seems to be different from what you describe.
    "and way out of situation"? I'm not sure what that means.
  • 39
    2okPze5.png

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    HOW TO INSTALL LINEAGEOS:
    Coming from stock or other ROM
    * https://wiki.lineageos.org/devices/cheeseburger/install
    * https://wiki.lineageos.org/devices/dumpling/install

    HOW TO UPDATE LINEAGEOS:
    From ealier LineageOS 19 build to newer
    * https://wiki.lineageos.org/devices/cheeseburger/update
    * https://wiki.lineageos.org/devices/dumpling/update

    HOW TO UPGRADE LINEAGEOS:
    Coming from LineageOS 18.1 or earlier
    * https://wiki.lineageos.org/devices/cheeseburger/upgrade
    * https://wiki.lineageos.org/devices/dumpling/upgrade

    DOWNLOADS:
    LineageOS 19 + recovery: Oneplus 5 | Oneplus 5T
    Google Apps: MindTheGapps

    DEVELOPER RESOURCES
    LineageOS source code:
    - https://github.com/LineageOS @ lineage-19.1
    Device tree:
    - android_device_oneplus_cheeseburger @ lineage-19.1
    - android_device_oneplus_dumpling @ lineage-19.1
    - android_device_oneplus_msm8998-common @ lineage-19.1
    Kernel:
    - android_kernel_oneplus_msm8998 @ lineage-19.1

    Android version: Android 12
    Kernel version: Linux 4.4.y

    Telegram group: https://t.me/los_op5

    Thanks for @robertogl @Maitreya29 !
    25
    Updates will be official builds from now.

    Upgrade from unofficial to official:
    * Flash migrate tools zip (https://androidfilehost.com/?w=files&flid=254680)
    * Flash new LineageOS zip

    Upgrade from official to official:
    Please read upgrade instructions:
    14
    14
    Update:
    * February security patch
    * Dual SIM mobile data is fixed
    * BPF is re-enabled (https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8998/+/323455)

    Downloads:
    cheeseburger | dumpling
    11
    Update:
    * April security patch
    * New app icons

    Downloads:
    cheeseburger | dumpling