yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
Also installed this ROM on my old OnePlus 3T (according to https://wiki.lineageos.org/devices/oneplus3/install , flashed "lineage-18.1-20210621-nightly-oneplus3-signed.zip" and "twrp-3.5.2_9-0-oneplus3.img" via "adb sideload $FILE") and works REALLY well. No FCs or other issues observed so far (although not tested thoroughly). WiFi, Bluetooth (Audio streaming), NFC, calls, GPS, AOD/inactivity display, fast charging, double tap to wake/sleep, camera light, screen rotate, auto-brightness, Widevine L3 (as on OOS?), SafetyNet check, Android TV streaming (chromecast), ...all perfect. And really smooth, Google Maps is even smoother than on OOS 9.0.6. Used MindTheGApps.

Note, however, when relocking the bootloader (command: "fastboot oem lock"), I had to factory reset first (?) and (more importantly), I had to click "NO" in the confirmation to lock it (seems incorrectly labeled by OnePlus :-D , see also https://forums.oneplus.com/threads/not-able-to-lock-oem.1020173/#post-20587482 ).

Nice work! :) Highly recommended ROM! Will report here if I experience any bugs or issues. And also if there's something I found working. ;-)

Links for reference:

- adb and fastboot (Linux): https://dl.google.com/android/repository/platform-tools-latest-linux.zip

- twrp-3.5.2_9-0-oneplus3.img: https://eu.dl.twrp.me/oneplus3/twrp-3.5.2_9-0-oneplus3.img.html

- lineage-18.1-20210621-nightly-oneplus3-signed.zip: https://mirrorbits.lineageos.org/fu...age-18.1-20210621-nightly-oneplus3-signed.zip

- MindTheGapps-11.0.0-arm64-20210412_124247.zip: https://androidfilehost.com/?fid=2188818919693781601

Edit: one question ...does anyone know if, given the nightly install and a re-locked bootloader, I can simply install or even automatically update LOS (without manually going through TWRP) if new nightly builds becomes available? And how does this relates to an encrypted phone, i.e., can it also be updated w/o issues?

Edit2: okay, I just upgraded to newest nighly (28-06-2021) and all went smooth and fine. Used the buildin LOS updater and all was done automatically - cool! Additionally, everything is working fine so far (especially GPS)! :)

PS: my phone is currently unencrypted (the default after install?).
[OnePlus 3 & 3T Cross Device Development] :
{Mod edit: Quoted post deleted}

Start a new thread on Q/A section, please.

I'd love to read that too, but this is LOS thread, not battery thread.
[OnePlus 3 & 3T Cross Device Development] Triggerfinger68:
Excuses, you are absolutely Right, I already started a new thread. Thanks.
[OnePlus 3 & 3T Cross Device Development] ranjeet choudhary:
Any suggestions on how to fix the bluetooth audio not playing on some device. Similar to what others have mentioned not able to play anything on VW polo android auto. Bluetooth connects but doesn't play. It is working fine with other ROMs
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Vulkan drivers isnt applying until now, in this rom rite?
[OnePlus 3 & 3T Cross Device Development] real_uplink:
Tried to upgrade from LOS 17.1 to 18.1 without factory reset. --> Bootloop/endless boot time

My Setup:

- Old System: lineage-17.1-20200425-nightly-oneplus3-signed

- New System: lineage-18.1-20210621-nightly-oneplus3-signed

- Firmware: OnePlus3T_9.0.6-(20-11-19)-FIRMWARE

I use(d) MagisK v23 and already tried the following:

1. Flash new lineage zip and flash MagisK.zip directly afterwards without reboot, then rebooted

2. Flash new lineage, reboot -> Bootloop/endless boot

3. Remove MagisK on LOS 17.1 and then flash new lineage and reboot

Upgrade tried via:

- Lineage Recovery lineage-18.1-20210621-recovery-oneplus3 with sideload

- TWRP-3.5.2_9-0-oneplus3 with zip from both internal storage and sideload

I also tried to perform a clean install, successful boot and then restore /data via nandroid but I end in the same behavior as with the direct upgrade (bootloop to recovery/endless boot time)

None of the variants worked for me.

Failure symptomatic:

- I always be able to surpass the device encryption password prompt

- Then it shows a long time the moving LOS logo (never stuck)

- Then it:

-> either reboots into recovery

-> or it does endlessly show the moving LOS logo. I wait at least 15 minutes on each of the above tests and also tried for more than 1 hour in some tests

Restore of old system:

- Somehow even a nandroid restore back to 17.1 behaves a little weird:

- After nandroid restore of /boot /data /system /system-image the system is not able to boot.

- I have to:

-> restore /boot /data /system /system-image from nandroid backup

-> zip-install the lineage-17.1-20200425-nightly-oneplus3-signed in order to successfully boot

-> delete /data/system/locksettings.db in order to bypass the lockscreen which otherwise does not recognize my correct password anymore.

=> Then the old system (lineage-17.1-20200425-nightly-oneplus3-signed) is fully working with active MagisK and all settings, apps and app-settings being restored.

I tried this procedure also with lineage-18.1-20210621-nightly-oneplus3-signed without success -> Bootloop/endless boot time

Exclude defective nandroid Backup:

I checked for a corrupt nandroid by performing two other nandroid backups on different days and trying to restore them.

Recent upgrades:

I already successfully upgraded from LOS16 to 17.1. (Could this be a problem because the partition usage/formatting/... changed?)

Is there any possibility to upgrade with my data?

Is there a possibility to debug the boot in more detail?

Would be nice if you can give me a hint.
[OnePlus 3 & 3T Cross Device Development] raulaguilare:
Always clean flash!
[OnePlus 3 & 3T Cross Device Development] real_uplink:
Upgrade with data is supported by both Vanilla Android and LineageOS:

Upgrade LineageOS on oneplus3 | LineageOS Wiki

wiki.lineageos.org

I want to find the bug in the upgrade process.
[OnePlus 3 & 3T Cross Device Development] isitmeor:
Does anyone else have a problem with lineageos-18-1 and backing up whatsapp?
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I am just upgraded my 3T. There isn't any Magisk.zip file. It is now an app that you sideload. Thereafter using the Manager you need do something (sign) the boot.img file.

You should always flash the ROM and the Gapps in 1 go and reboot ( Except may be for XiaoMi.). If all is stable then continues.
[OnePlus 3 & 3T Cross Device Development] parkedraccoon:
Dirty flashed all the way from LineageOS 15.1, went pretty smoothly!

One small issue I noticed - the Swap Capacitive buttons option doesn't properly persist after a reboot. Turn on, works fine. Reboot, goes back to default behavior, have to re-toggle the setting for it to work. This is on today's nightly, haven't tried any others.
[OnePlus 3 & 3T Cross Device Development] snyperius:
You can change the extension of the Magisk apk to .zip and install it from the recovery just like in the good old days
[OnePlus 3 & 3T Cross Device Development] moscic:
You can do that even without changing the extension :)
[OnePlus 3 & 3T Cross Device Development] snyperius:
Depends on the recovery. I use a bit older LOS recovery, last time I tried it only accepted .zip. If you change the extension, it will work with any recovery.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Anyone use Zoom here?

Zoom is unusable with Lineage 18.1, it freezes when I'm in a meeting and I have to force reboot the phone.

I tried to install 17.1 (I used that last year for zoom calls, no problem), but I discovered that also Los 17.1 has the same issue.

@dianlujitao could you look into it?
[OnePlus 3 & 3T Cross Device Development] a0b1c2:
Hi everyone,

For many weeks, at least once a week, I'm getting a kernel panic. Every week, I flash the weekly drop.

The issue has finally climbed up my priority list that I've finally captured a console-ramoops.

What I don't know is whether my previous kernel panics are the same issue as the captured log. Now that I know how to capture the logs, if need be, I can snarf them.

Attached is the tail end of the file. I've preceded the panic with, I hope, sufficient context.

This is the head of the attached file:

[60587.858258] synaptics,s3320: all finger up
[60589.444620] synaptics,s3320: all finger up
[60590.073706] state: 0
[60590.102542] q6asm_callback: payload size of 8 is less than expected.
[60590.102875] q6asm_callback: payload size of 8 is less than expected.
[60590.108820] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x
0d1300c8 OPER:0x00000090
[60590.108870] pn544_dev_write : i2c_master_send returned -107
[60590.111090] q6asm_callback: payload size of 8 is less than expected.
[60590.111887] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[60590.148152] trigger:1(0:stop 1:start)
[60590.149040] q6asm_callback: payload size of 8 is less than expected.
[60590.229394] pn544_dev_ioctl bad ioctl 1074325765
[60590.229880] Call trace:
[60590.259469] Call trace:
[60590.264927] Call trace:
[60590.265113] ffs_function_bind_config: ffs_function_bind_config(): usb_add_function() fails (err:-12) for ffs
[60590.265117] android_bind_enabled_functions: android_bind_enabled_functions: ffs failed
[60590.265142] android_enable: android_enable: usb_add_config failed : err: -12
[60591.288038] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[60591.288168] Call trace:
[60591.288471] ffs_data_clear: ffs:0000000000000000 ffs->gadget= 0000000000000000, ffs->flags= 2
[60591.288498] ------------[ cut here ]------------
[60591.288515] Kernel BUG at ffffffc00077b628 [verbose debug info unavailable]
[60591.288532] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[60591.288557] CPU: 3 PID: 10785 Comm: adbd Tainted: G W 3.18.124-lineageos-g04ff888 #1
[60591.288573] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
[60591.288592] task: ffffffc15d4ece00 ti: ffffffc011bb0000 task.ti: ffffffc011bb0000
[60591.288612] PC is at ffs_data_clear+0x130/0x138
[60591.288631] LR is at ffs_data_clear+0x98/0x138
[OnePlus 3 & 3T Cross Device Development] a0b1c2:
What rotten luck, another crash and to my untrained eye, it looks similar to the previous.

[131502.547406] synaptics,s3320: all finger up
[131504.149749] synaptics,s3320: all finger up
[131504.938613] state: 0
[131504.959312] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131504.965529] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[131504.965590] pn544_dev_write : i2c_master_send returned -107
[131504.974487] q6asm_callback: payload size of 8 is less than expected.
[131504.974841] q6asm_callback: payload size of 8 is less than expected.
[131504.982969] q6asm_callback: payload size of 8 is less than expected.
[131504.985766] trigger:1(0:stop 1:start)
[131504.986514] q6asm_callback: payload size of 8 is less than expected.
[131504.992872] enable_store: android_usb: already disabled
[131505.074898] pn544_dev_ioctl bad ioctl 1074325765
[131505.140175] Call trace:
[131505.155711] Call trace:
[131505.158738] Call trace:
[131505.158921] ffs_function_bind_config: ffs_function_bind_config(): usb_add_function() fails (err:-12) for ffs
[131505.158926] android_bind_enabled_functions: android_bind_enabled_functions: ffs failed
[131505.158949] android_enable: android_enable: usb_add_config failed : err: -12
[131506.176376] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131506.176437] Call trace:
[131506.176551] ffs_data_clear: ffs:0000000000000000 ffs->gadget= 0000000000000000, ffs->flags= 2
[131506.176565] ------------[ cut here ]------------
[131506.176570] Kernel BUG at ffffffc00077b628 [verbose debug info unavailable]
[131506.176576] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[131506.176585] CPU: 3 PID: 4721 Comm: adbd Tainted: G W 3.18.124-lineageos-g04ff888 #1
[131506.176590] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Nobody else seems to have this problem, so let's check the framework.

Have you installed the latest firmware?

Have you installed the latest TWRP?

Is your Bootloader locked or unlocked?

Is your device encrypted?

Which filesystem are your partitions formatted in?

Which GApps package did you install?

Did you do a clean install?

Do you have Magisk installed? If yes, which addons?

Do you have Exposed installed? Or something like this?

Which Apps do you have installed?

Which Modifications have you done?
[OnePlus 3 & 3T Cross Device Development] snyperius:
Same here, weekly kernel panic on my 3T.

I have the latest OOS firmware.

I use LOS recovery.

Bootloader unlocked because of Magisk (locking it used to cause bootloop).

Device is encrypted.

Filesystems: i have no clue. Whatever LOS recovery formats the partitions it uses to, plus whatever the factory used on the partitions that LOS doesn't format.

Gapps: MindTheGapps, whateverer version was available when LOS 18.1 came out.

Clean install. The issue started after the 2nd or 3rd OTA update (I only update when new security updates come out).

I have Magisk installed. Only have Google Phone Recorder addon installed.

No Exposed or anything like that.

No modifications done (I don't know if using Nova launcher prime counts as a modification. I've been using it for years without any issues).

The only thing different from when I used LOS 17.1 is I've ditched Chrome and started using Brave browser with Bitwarden.

Could it be battery-related? I still have the original one; I still get around 4.5 hrs of SOT, but have to charge daily.

I'll do a complete factory reset to the latest OOS (to get the original gps.conf file so that I can compare it with the one from LOS), maybe even with the unbrick tool, and do a complete clean install of LOS 18.1 when I have some time (hopefully next week)
[OnePlus 3 & 3T Cross Device Development] a0b1c2:
Thx for your response. I'm about to head out for the weekend so I'll respond in detail early next week.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I can confirm this, happened to me 2 days ago, but also with the 0705 ( - but I also didn't try out the new 0712 yet..)

Clean flash LOS 18 or dirty from LOS 17 (or even lower)?
[OnePlus 3 & 3T Cross Device Development] yy688go:
I flashed los 18.1 20210705, and there must be a random restart every day. I beg dev to pay attention to this bug and fix it. However, there is no log.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Did you just upgrade from LOS 17? If yes, best do a factory reset. Dirty flash major upgrade, is not a good idea.
[OnePlus 3 & 3T Cross Device Development] Gaurav Shahu:
I'm having screen wake up issues. I have to press power button several times to wake up the screen. And the wake up is random, sometimes the screen turns on fast sometimes it takes a long time to turn on. I came back to lineage OS today after using Arrow OS for months. This issue was there too. It was fixed once in an Arrow OS build in March. But after that build, the issue was in every single build and not fixed till date. I thought I will not have this issue here but it's here also. Some others were having this problem there too. Please fix it, it's really annoying at times when I have a call or something important I can't wake the screen on time. And if it helps some devs there told me a long time ago that it had something to do with the boot image??? Maybe... idk help plz🙏🙏🙏
[OnePlus 3 & 3T Cross Device Development] ankinapallih:
What is the battery life in lineage os 18.1 for oneplus 3t
[OnePlus 3 & 3T Cross Device Development] yy688go:
Of course not, I flashed it after a four wipe
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
This whole random reboot business reminds me of when my phone did that on OOS 8. Couldn't get to the bottom of it so I ended up nuking it with an unbrick tool, it's fine ever since. So your reboot issue might not be ROM related.
[OnePlus 3 & 3T Cross Device Development] kkovaacs:
I have serious battery drain issues with the latest nightly build (July 19, 2021) on a OnePlus 3. One full charge only gives me about half a day of operation...

I've installed BetterBatteryStats and it seems that the 'Awake' time is significantly larger than 'Screen On' -- that is, it's something keeping the phone awake when it's lying on the table.

I also tried to have a look at Kernel Wakelocks (since the rest of details shows no details of use), but BBS shows no data at all there:

The phone is rooted (Magisk) and according to the check in BBS it has all the required permissions.

Is there anyone else experiencing issues like this? Or maybe have any idea how I could fix BBS to show Kernel Wakelock stats?
[OnePlus 3 & 3T Cross Device Development] Nixeus2:
Hi people,

SInce some last updates i have a weird issues, my snooze doesn't ring some day...i have snooze each days...but sometimes, no snooze :(

Any ideas please ?

Thanks :)
[OnePlus 3 & 3T Cross Device Development] yy688go:
I contacted rom dev through Weibo, and dev said that he also encountered a random restart bug, but because the computer was not around recently, there was no way to capture the log, so this bug is temporarily unsolved
[OnePlus 3 & 3T Cross Device Development] JoeBar07:
Ah nice, I just wrote it because my issue gradually got worse and worse on a OnePlus3 which I configured exactly like my 3t which was fine. Clean flash, format ect, nothing helped. I had the Computer log over USB for many hours (way more than the phone was able to do without shutting down at this point), but the phone didn't crash then. So the unbrick tool was the last resort for me to make sure it wasn't a hardware issue.

Nowadays both phones don't have any issue like that (with recent LOS) but if the devs look into it thats great.
[OnePlus 3 & 3T Cross Device Development] yy688go:
Give dev some time, I think this bug will be fixed soon, be patient
[OnePlus 3 & 3T Cross Device Development] Tiggy_Drum:
Hi,

Since I have installed the LOS 18.1 ROM I cannot get LTE+ (LTE advanced) working. Phone is stucked to LTE.

I was previously on ArrowOS 11.0 ROM and it was working.

Is someone get a similar problem or have a solution ?

Thanks.

Edit : check connectivity with NetMonster, it seems that network is connected through LTE-A. It is probably a display problem on the LTE icon..
[OnePlus 3 & 3T Cross Device Development] ankinapallih:
Does this rom work for my OnePlus 3t which I recently replaced screen
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
You have to try out by yourself..

Do a backup before to be on the safe side...

Wireless Display / Miracast option isn't available in this rom, does anybody know how to enable it again?
[OnePlus 3 & 3T Cross Device Development] ankinapallih:
I have tried but no use display is not responding correctly can I hope a solution
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I'm curious, is it a cheap LCD? Did you try if it works on stock rom?
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I replaced my screen about 2 years ago. On first power up it hang. Gave the tech a shock.

Wiped the cache and it boot normally.
[OnePlus 3 & 3T Cross Device Development] ankinapallih:
Yes it works with stock rom
[OnePlus 3 & 3T Cross Device Development] ankinapallih:
yes it is lcd screen not amoled
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
Hi, Anyone encountering WhatsApp backup to G drive that never completes?

It just stuck on "Preparing for backup to Google Drive"

How did you manage to fix this?

TIA
[OnePlus 3 & 3T Cross Device Development] isitmeor:
i have the same issue it just takes a very long time

you just have to wait
[OnePlus 3 & 3T Cross Device Development] isitmeor:
is there a way to install twrp on LineageOS 18.1

i accidentally updated the cto the LineageOS LineageOS
[OnePlus 3 & 3T Cross Device Development] ChrisLane:
I updated to the 20210726-nightly-oneplus3 build yesterday and have been having touchscreen responsiveness issues since where some presses or swipes aren't registered at all.

This has made typing and scrolling news articles a bit frustrating. Beware! :P
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
Me too. The screen is not working well at all. Sometimes when you click an item it acts like a long press and selects it and when you click on an icon it shows the menu instead of opening the app. Rolled back to previous version and all works ok.

In the "changes to be included in next build" it states: "fixup! InputManagerService: Flag when an injected event is a real input". Maybe it fixes this issue.
[OnePlus 3 & 3T Cross Device Development] highdiver_2000:
I

WhatsApp backup job says 70MB backup for 2.5GB data. Did a test restore on another phone (Poco X3 NFC). So far looks like everything is going restoring.
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
I've seen the same problem description for OnePlus 6/6T with the 0729-build. Perhaps a generic problem, not device specific.
[OnePlus 3 & 3T Cross Device Development] pigeons9:
For those that are curious, or being forced to switch devices because of the 3G sunset, VoLTE is working fine for me on T-Mobile US with the latest LineageOS and I did not need to do any extra configuration. Beforehand I had installed the latest OxygenOS available for this phone (9.0.6).
[OnePlus 3 & 3T Cross Device Development] moscic:
Install earlier version: betterbatterystats_xdaedition_debug_2.3-248
[OnePlus 3 & 3T Cross Device Development] S_T_A_R:
Is Airtel (india) Volte work?
[OnePlus 3 & 3T Cross Device Development] Sjhingan:
I have just installed the latest nightly build of Lineage os 18.1 on my op3t. I did a clean install and flashed open gaaps nano and im rooted with MAgisk. I find certain apps crashing repeatedly ( evernote/asus download master) since i have been using this ROm. I dont want to change since i am loving using this rom. I would appreciate any help you can give me.
[OnePlus 3 & 3T Cross Device Development] Sjhingan:
Working for me
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Hey guys i just recently noticed the vulkan API is missing in 18.1

I´m quite sure it existed in 17.1 and the chipset surely supports it but for some reason it´s not bundled into this rom.

Tried to manually add (probably) compatible libs from snapdragon 625 which also uses a adreno 5xx but unfortunately it seems like the device simply ignores them.
[OnePlus 3 & 3T Cross Device Development] hanneshoch3:
Use mindthegapps gapps. Just wipe system, install rom and then install MTG gapps (and then magisk if needed).
[OnePlus 3 & 3T Cross Device Development] Sjhingan:
just to be sure, i do not need to wipe data, cache or delvik? simply wipe system and reinstall ROM and MTG? Thanks in advance
[OnePlus 3 & 3T Cross Device Development] hanneshoch3:
That should work and do no 'damage' to your data. Wiping cache and dalvik won't hurt either, so go ahead with that too.
[OnePlus 3 & 3T Cross Device Development] risheek7:
Not for me. I have been waiting for an year for this issue to get fixed. On Los 18.1 rn
[OnePlus 3 & 3T Cross Device Development] Ignass:
Is there a fix for screen wont waking from sleep?

Buttons illuminate but screen only turns randomly at 4-6 try. I can hear that screen is working when its black.

It worked on oos, tried another rom and its the same.
[OnePlus 3 & 3T Cross Device Development] sunnydepu:
I experienced the same issue with the previous builds. It seems resolved with lineage-18.1-20210809-nightly
[OnePlus 3 & 3T Cross Device Development] Ran94:
I recently installed LineageOS 18.1 on my Oneplus 3. Everything seems to be working well but there is no way to add VOLTE icon to status bar. I'm using Jio(India) Sim.

My question is how can i check if Volte is working since there is no indicator in status bar

If Volte is working, how can I add the indicator to status bar.

(Area in my network is very suspect. So Volte icon is quick indicator to move to some other area to make calls )

Thanks