[11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T

Search This thread

debby_

Member
Jan 14, 2011
32
9
Download an app that allows you to see the amps/volts being pumped into the phone. Haven't tried under 18.1, but 17.1 never said it was Dash charging but it was.
Hey, I got a charging problem too. sometimes it doesn't pour a dash charger or a decent one. it happens at random. it's after restart.
 

luckiKA

New member
Apr 10, 2021
1
0
thanks to all your efforts keep getting lineage better and up to date!
I'm struggling at the moment with the internet connection. browser is working fine, but system time is not getting updated and system updater can't find an internet connection.
I did a clean installation / no update.
Any Ideas?
 

diziet_sma

Member
Feb 19, 2015
15
1
One plus 5 - latest update 12/04:
no reboot to recovery option
setting ringtones from the music app cause it to freeze
setting ringtones from the phone app, some mp3 files don't show up - all files that I used as ringtones under 17.1

diziet
 

humpty321

Member
Jun 12, 2015
14
1
Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":
IMG_20210413_204323.jpg


I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
Anyone else?
 

mgmeulen

Member
Jul 27, 2015
5
2
Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":View attachment 5278115

I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
Anyone else?
Same here. Happened three times since I'm on 18.1. In all three occurences I plugged in the charger directly after I had a usb audio dac connected while using the usb audio player pro app. I use this dac and app regularly and normally the phone charges fine afterwards, so not sure if there is any relation.

For the rest very happy with 18.1!
 

Solidgrue

Member
Jun 26, 2010
17
0
I'm noticing an IPv6 problem over WiFi. My home LAN has a Tunnelbroker IPv6 prefix. The router broadcasts a Route Avertisement (RA) packet every 30 seconds. All the other v6 enabled devices on my LAN are picking it up, including other Android devices on 9 and 10.

This device, OP5T (dumpling) on 18.1 picks up the advertisement and an IPv6 address when it connects to the WiFi, but then drops it after about 30 seconds. This used to work under 17.1, but it seems to have stopped since I upgraded.

Of course, my LTE network interface is picking up its IPv6 assignment and holding it, so its not platform-wide. That other Androids are also working has me thinking its the new wifi stack on the 5t.

Any suggestions on where to look next?

edit to add: I just noticed the WiFi advanced screen refreshes real time, and that the IPv6 addresses are appearing for 30 seconds, disappearing for 10 seconds, and then reappearing. I looke at the firewall rules for IPv6 and I see some odd terms that seem to drop packets talking to the prefix picked up thru RA. Is this intended?
 
Last edited:

T1mb3

Senior Member
Feb 14, 2016
690
788
Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":View attachment 5278115

I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
Anyone else?

Same here. Happened three times since I'm on 18.1. In all three occurences I plugged in the charger directly after I had a usb audio dac connected while using the usb audio player pro app. I use this dac and app regularly and normally the phone charges fine afterwards, so not sure if there is any relation.

For the rest very happy with 18.1!
Issue was caused by CAF change in kernel a while back.
It should be fixed in next weekly.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I always prefer doing adb sideload and I'm using TWRP as well. I'm just hoping adb sideload does similar things across recoveries.

    I don't think you can reasonably call something OTA update if (on average) every third install requires you to plug in usb to reflash.
    If things go wrong with TWRP, you don't get any support from the maintainer, that's all.

    You don't get any support from the maintainer when using LOS recovery either, because if you're flashing magisk (which anyone who uses their phone in the real world must, to fix props) he won't help. But the difference is, with twrp, you can rescue your phone by manually reflashing zips when it dies. With LOS, you'll need to power up your laptop and ADB sideload. That's just awful.
    I'm no way recommending any recoveries here, just getting people to reply so it's easier for maintainer to evaluate situation.

    I do personally find TWRP more versatile but I have seen many many reports over reddit about TWRP not playing that well with LOS 18.1
    Until someone can tell me what exactly LOS recovery does that TWRP does not, I will not believe it. In my experience from the world of tech support people repeat unfounded myths that other people say with no evidence or reason. "It worked for me with LOS recovery" suddenly becomes "twrp causes problems with flashing".
    2
    No more updates after 7th June,has it stopped
    If you look, even before there were the updates every 7 days
    2
    As shared by @T1mb3 over the telegram group, the front camera issue with camera API1 now has a fix.

    Also mentioned was that the fix seems to fix the shutter lag.


    The patch set is currently merged and is expected in the next nightly build.

    In the meantime, you can apply the fix by setting the following in /system/build.prop:

    Code:
    camera.disable_zsl_mode=1

    Thanks @T1mb3!
    1
    Hi folks, sorry if this has been asked, I searched and could not find a definitive answer.
    As you all know for magisk 23 to install you need a ramdik image.
    I read somewhere that you can not just use the ramdik.img that's in the root folder of lineage 18.1.

    So how do you root lineage 18.1 with magisk 23?
    Sorry for the basic question I might be missing something obvious.

    Thank you in advance.
    You can change the magisk file extension to zip and flash with TWRP, it's covered in the magisk Wiki.
  • 13
    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 repo. 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:
    - Official instructions
    - In short: sideload in Lineage recovery (suggested) / flash in TWRP

    HOW TO UPDATE LINEAGEOS:
    - Download update from Updater app
    - Install update

    DOWNLOADS:
    LineageOS 17.1: Official Oneplus 5, Official Oneplus 5T
    Google Apps: MindTheGapps
    Recovery: Suggested: Lineage recovery for Oneplus 5, Oneplus 5T | Alternative: TWRP

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

    Android version: Android 11
    Kernel version: Linux 4.4.y
    Required firmware: OxygenOS 10.0.1 (shipped with ROM, no need to install manually)

    Telegram group: https://t.me/los_op5
    13
    LineageOS 18.1 is now released for officially supported devices:
    Upgrade guide from official to official: https://wiki.lineageos.org/devices/cheeseburger/upgrade
    Upgrade guide from unofficial to official:
    - Wipe data
    - Install LineageOS & GAPPS

    Unsupported method:
    Migration tools by Codeworkx: https://androidfilehost.com/?w=files&flid=254680 (Unofficial->Official, Official->Unofficial)
    - Flash before updating
    - Read more: https://wiki.lineageos.org/signing_builds.html#test-keys-to-official-or-vice-versa

    NOTE: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them.
    12
    UPDATE:
    * Synced LineageOS sources
    * EAS is here to stay
    * Upstreamed kernel to 4.4.258
    * More detailed changelog

    Download for Oneplus 5 or Oneplus 5T.
    10
    UPDATE:
    * Synced LineageOS sources
    * Fix USB file transfer
    * Kernel: Merge tag 'LA.UM.9.2.r1-02500-SDMxx0.0' of https://source.codeaurora.org/quic/la/kernel/msm-4.4 into HEAD
    * Removed some 30 mb of unused camera blobs
    * Detailed changelog

    Download for Oneplus 5 or Oneplus 5T.
    9
    Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":View attachment 5278115

    I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
    Anyone else?

    Same here. Happened three times since I'm on 18.1. In all three occurences I plugged in the charger directly after I had a usb audio dac connected while using the usb audio player pro app. I use this dac and app regularly and normally the phone charges fine afterwards, so not sure if there is any relation.

    For the rest very happy with 18.1!
    Issue was caused by CAF change in kernel a while back.
    It should be fixed in next weekly.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone