yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Nixeus2:
I think my problem is due to the use of the MadKernel !
[OnePlus 3 & 3T Cross Device Development] override182:
removed as advised
[OnePlus 3 & 3T Cross Device Development] :
Please read and honor the OP. Custom kernels arn't suppprted in this thread. This means: don't discuss custom kernels here, as well as only report bugs/issues if you are using the shipped kernel. Reporting issues with custom kernels is a lack of respect and wastes the time of all users participating here.
[OnePlus 3 & 3T Cross Device Development] override182:
alright sure. thanks np
[OnePlus 3 & 3T Cross Device Development] Shashank H:
Mobile network standby is taking lot of battery i think , I'm not getting good screen off time, can someone tell me what could be the issue? I had clean flashed the rom
[OnePlus 3 & 3T Cross Device Development] kousik:
In my attempt to enable volte there's no joy. Searched the thread and others, but unsure where did I go wrong. If someone can spot it, will greatly appreciate. My carrier is Airtel India, and they do support Volte and WiFi calling. What I did:

Clean flash stock latest OOS 9.0.6

Yay! Volte enabled (checked thru *#*#4636#*#*)

Kept stock recovery as suggested in another thread, but did fastboot oem unlock

fastboot boot recovery twrp-3.4.0.img

Flash Lineageos 17.1 nightly

Flash gapps nano

Flash firmware+modem 9.0.6 stable

fastboot oem lock

Reboot: No Volte :-(

Wondering if my flashing order is wrong?
[OnePlus 3 & 3T Cross Device Development] mobilityguy:
I've been running Lineage 17.1 on my OnePlus 3t for a couple of weeks now, after long experience running this and other Lineage and CM builds on older phones. I've encountered one problem I can't fix. I pair the phone with a Pebble Time watch. Under OOS 9.0.6 the watch drained about 10% every 2-3 days; under LOS 17.1 I lose about 20% per day. One time I looked at the connection on the watch and it said "No LE". I unpaired and repaired and the message went away, but it's still draining as if it was running Bluetooth at full-power. I went from recharging the watch about once every 10-12 days to once every three. Nothing has changed in the watch setup, I'm using the same face I always did.

Does LOS on this phone support Bluetooth LE, and is there anything I have to do to turn it on? Pebbles are getting hard to find and I don't really want to exhaust the battery on this one.

Overall, this is a terrific build. Battery life and overall performance are better than stock OOS and it's nice to be patched up to date once again. Thanks to everybody involved in developing this ROM and keeping the 3t alive.
[OnePlus 3 & 3T Cross Device Development] sammy9005:
Edit - Fixed this by installing Google dialer from the play store then setting it as the default phone app and disabling lineage dialer.
[OnePlus 3 & 3T Cross Device Development] :
The actual error is somewhere before the line starting with FAILED. On compile errors it's usefull to post the complete build log, because with multi-job make the actual error can ne somewhere else.
[OnePlus 3 & 3T Cross Device Development] ppajdek:
Workarounds for building Q on 8GB RAM environment:
1. At the start of the build:
[ 99% 138/139] /mnt/ssd/aosip/out/soong/.bootstrap/bin/soong_build /mnt/ssd/aosip/out/soong/build.ninja
This used to take around 30mins, after enabling zram now it takes around 30secs (thanks to [@kdrag0n] for the zram idea) which is on par with what happens in 16GB RAM building environments
sudo apt install zram-config for installing zram-config package
sudo nano /etc/fstab and add a # in front of the swap disk if you have one and then reboot
After booting cat /proc/swaps to check if zram is enabled or not
2. To avoid huge metalava compilation times, compile the api-stubs-docs and other packages manually first then continue with mka bacon etc
For example this is what I'm using now in aosip:
. build/envsetup.sh && lunch aosip_wayne-userdebug && mka api-stubs-docs && mka hiddenapi-lists-docs && mka system-api-stubs-docs && mka test-api-stubs-docs && mka kronic
Each of those api-stubs-docs, hiddenapi-lists-docs etc took around 4-7 mins
Increasing of heap from soong directory or other env exports are not required
Total combined build time in my system (ryzen 1600 with a 8gb ddr4 stick) is around 2hrs now compared to 5hrs previously

If you're building Q and getting metalava errors apply:

https://github.com/Magma-WIP/build_soong/commit/bcd1bb529132905cf55e72f5a2a6ba19a99f60ac
https://github.com/Magma-WIP/build_soong/commit/dc3365fbde3b2a5773e655f690bb073967100795
If build fails even with the commits applied try building SystemUI with -j1
It can also be a good idea to increase swap

Command:
cd build/soong && git fetch https://github.com/Magma-WIP/build_soong ten-metalava && git cherry-pick bcd1bb529132905cf55e72f5a2a6ba19a99f60ac^..dc3365fbde3b2a5773e655f690bb073967100795

Got the same error, im building on 12GB vm, installing zram fixes it.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION]

Interesting behaviour of 191231 (it didn't happen on previous versions): if I restore a TWRP backup the phone goes into a boot loop. I don't even get to the point where I'm prompted for the on boot password.

However, if I restore a system image backup it boots normally.

Unlike the issue with OOS, I get no errors when restoring a normal system backup.

I've tested this on both TWRP 3.3.1-0 and 3.3.1-1.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
This is caused by selinux, I just built a new TWRP with system-as-root to address the issue, check op for download link.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I noticed this too, luckily had a backup of the previous build and an NLOS backup. The OP says the new TWRP build doesn't work with pre Q Roms so I'm a bit hesitant to switch right now. I'm currently using the normal version of enhanced TWRP. The enhanced TWRP thread also had a system-as-root build published a few months ago with the same disclaimer.

I also found this in the OP of that thread but not sure why its the case.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks. With the 3.3.1-200107-SAR TWRP the backup and restore process works on Los 17 (I didn't try it on 16).

But...

This new version has broken open recovery script (ORS) backup and recovery for the system partition (logs attached).

And, since I do 90%+ of my activity in TWRP using ORS, I'm going to keep using the 3.3.1-0 version.

Ah, don't you just love fixing all these problems associated with Q? I REALLY appreciate the work you do!
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Unable to locate '/system' partition for backup calculations.

I guess you should replace /system with /system_root from your scripts. Old backups are not compatible with system-as-root recovery as well.
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
Yeah you were right. I already had 64 Gb of swap setup but what really fixed it was giving my VM extra RAM from 10GB to 13GB.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
ORS is a TWRP scripting language. See https://twrp.me/faq/openrecoveryscript.html for details.

You backup and restore one writes something like this:

backup BSD 200107-204828_los-17-191231

restore /sdcard/TWRP/BACKUPS/1ebc8e1b/200107-135022_los-17.0-191231 BSD

As you can see there's no specific reference to the location of the partitions being backed up or restored. Instead they are identified just by B (boot) D (data) or S (system).

TWRP internally then uses the correct address.

Clearly the code for ORS inside TWRP needs to be adjusted to cater for system-as-root.
[OnePlus 3 & 3T Cross Device Development] bfm.95:
Every time I want to add it using root browser it says operation failed

The phone is already rooted via magsik

How can I add this line??
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Indeed, I just fixed it and the download link is updated.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Had the same problem, try a different root browser / editor or just download the entire file and replace it using TWRP
[OnePlus 3 & 3T Cross Device Development] knpk13:
Sorry but could I have some clarification? The OP says the new system as root recovery is not compatible with pre-10 Roms. Does that mean backing up, restoring, and installing zips (and other functions like formatting or wiping partitions) will not work for pre 10 Roms?

Or does it just mean old files (rom and gapps zips and nandroid backups) are not compatible with the new recovery.
[OnePlus 3 & 3T Cross Device Development] bfm.95:
How to replace it using TWRP?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Use the built-in File manager under "Advanced"
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Unfortunately the latest version (md5: 108713850be03d2c3fe1528130d15077) doesn't boot and gives me a white led of death.
[OnePlus 3 & 3T Cross Device Development] bfm.95:
It's not working mate, the folder system is empty I can't see anything
[OnePlus 3 & 3T Cross Device Development] :
Have you mounted system partition?
[OnePlus 3 & 3T Cross Device Development] ranjeet choudhary:
even i have the same issue with airtel sim on 3t. for jio its working fine, let me know if you found any fix?
[OnePlus 3 & 3T Cross Device Development] server3249:
My phone is randomly going into silent mode without any action from my end. Its happening even when I'm actively using the phone. I didn't have this issue in stock rom. Running Lineage 17.1 latest on op3. Any ideas?
[OnePlus 3 & 3T Cross Device Development] moscic:
Maybe accidental Vol up+power?
[OnePlus 3 & 3T Cross Device Development] kousik:
Settings > System > Buttons > Additional buttons

Set None to all notification slider settings.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI:

1- https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/295790

2- https://review.lineageos.org/q/owner:dianlujitao%40lineageos.org+branch:lineage-18.1+

But ... https://review.lineageos.org/c/LineageOS/hudson/+/292619
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Would you mind explaining what all that means for our phone? I, and I expect many others, don't understand all this code building stuff.
[OnePlus 3 & 3T Cross Device Development] alleykat2561:
The advent of Lineage 18, just in time for Christmas.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
The first link indicates that LineageOS 18.1 with Android 11 will be released on christmas.

The second link tells that dianlujitao is working on this and

the third link shows that our oneplus3(t) will not at first get LineageOS 18.1, it will, for the first, stay on 17.1.
[OnePlus 3 & 3T Cross Device Development] maniacbb:
I have the same problem does anyone have any idea how to solve this problem?

I have the latest versions from December 21st
[OnePlus 3 & 3T Cross Device Development] trgowtham:
How did you enable voLTE for Jio?

I am getting just LTE but unable to make calls using jio on SIM 2 slot. I have just flashed Dec 21 build from stock OS after unlock/installing TWRP. Please help.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
So this is not only happening to me??

I imagined it was a hardware issue with my slider, every now and again I can feel a vibration and it's the phone thinking that I moved the slider on the top position, setting it on silent, I have had to set the top position to "none" but this confirms me that my device is totally ok, it's something with the software that's creating this issue.

Oh thank you!

Has anyone else noticed that in airplane mode the radio is still active? Just try activating airplane mode then open the notification shade and on the top right you will see the network indicator and name.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm also on 201221 and I have absolutely no issues with either DnD or airplane mode. Both work as expected.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI: TWRP 3.5.0 is available ... https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html

Download TWRP for oneplus3

Download TWRP Open Recovery for oneplus3

dl.twrp.me

Happy New Year 2021 !
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Well that's strange, I have performed a clean install and still have network showing up with airplane mode enabled, see the screenshot, top right corner.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Need help to run Banking applications on official lineage OS 17.1. Installed TWRP, Lineage OS and Gapps.

Did not root the device.

Few of banking applications fail to open saying they are not supported on Rooted Devices. Any way to overcome the problem? I have not rooted the device but still says the error. I assume that it is erroring because it detected a custom OS. Is there a way to mask the OS type for making these applications run properly?

Please note that some banking applications are working fine and a couple of them are failing.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Does Magisk mask the custom OS to app as well? Which magisk version to install on Oneplus 3?
[OnePlus 3 & 3T Cross Device Development] punio4:
Did you lock your bootloader?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Check your safetynet status (Safetynet Checker App etc.). I think it failed. Then you have to lock your BL or install an app like Magisk to hide BL unlock..
[OnePlus 3 & 3T Cross Device Development] christantoan:
Try renaming TWRP folder in your storage.
[OnePlus 3 & 3T Cross Device Development] malerocks:
Some apps consider a phone with a unlocked Bootloader with a custom rom as rooted. When you installed WhatsApp, I am sure you got a warning from WhatsApp that it has detected a custom rom and does not guarantee performance. The only way out is to actually root the phone using magisk and hide the root from such apps.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
No. The bootloader is left unlocked. Followed steps as in

Redirecting…

Have not done anything apart from above. Read that re-locking bootloader can cause issues. So left it in that state.
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Thank you. Will rooting phone using magisk and hide root from apps mask them from detecting custom ROM as well? How and which version do I install Magisk? Should I install the latest version from https://magiskmanager.com ? I hope it will not brick my device?
[OnePlus 3 & 3T Cross Device Development] malerocks:
Detecting custom rom is usually not an issue, but once you install magisk and hide the relevant apps on magisk manager, the apps work fine.

Installing is very easy. My preference is flashing the zip via TWRP. If you prefer, you can also install the magisk manager apk first and install magisk via that.

Read up the instructions if you want to be sure of doing this. Highly unlikely you will brick. If something does go wrong, at worst you might have to reset the phone.
[OnePlus 3 & 3T Cross Device Development] snyperius:
I use LOS 17.1 on my OP3T with the bootloader locked (only lock it after a fresh install, because it wipes the phone's data partition) without any problems. Still, there were a few apps that thought it was rooted. The only solution is to root the device with Magisk and then hide the root from those apps
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Thanks a lot. Followed your recommendation of flashing the zip via TWRP. Able to hide the apps and use them now (y)
[OnePlus 3 & 3T Cross Device Development] trgowtham:
Thanks for your input. Rooting with Magisk and hiding the apps worked.
[OnePlus 3 & 3T Cross Device Development] Darkestnoir:
Hey,

yesterday i updated my LOS with the nightly from 11.01.2021 (my version was ~4 month old) and today i experiencing a big problem. My mobile internet no longer working.

My phone shows 4G, but no network connection? (symbol has an X in it). I can do telephone calls, but can't use the mobile internet. When i reboot the phone it works for a minute or so then nothing. Switching airplane mode on/off does not solve it. Wifi works fine and when i use it the network symbol no longer has an X in it.

OnePlus 3T

LOS 17.1 from 11.01.2021 (wiped system before update)

Magisk 21.2

GAPPS

Any ideas?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Is Settings>Network and Internet>Mobile network>Mobile data enabled?
[OnePlus 3 & 3T Cross Device Development] Darkestnoir:
Yeah sure, when i turn it off, i also have the X when i am connected to Wifi.

Any other ideas?

Edit: I tried to modify APN settings without success.

Edit2: I fixed it somehow :)
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Maybe it was just a temporary problem with your cell tower or Tkom :)

I also already thought that I have broken my cellular settings, but after few hours, everything worked again fine without changing anything. Even a simple reboot sometimes did bring mobile data connection back...
[OnePlus 3 & 3T Cross Device Development] andrihps:
Hi, on lastest update 11 January 2021, my oneplus 3 can't make/receive a call without speaker. i only make a call/received with loudspeaker only. did you guys have solution for my problem?

thanks
[OnePlus 3 & 3T Cross Device Development] mobilityguy:
This is not meant as a bump, but as an update. I've been refurbishing Pebble Steel watches, mostly by putting in fresh batteries. I use my OP3Ts to test them. I have one with the current Lineage 17.1 and one with OOS 9.0.6. I connected a watch with a brand new, conditioned battery to the Lineage watch at 8AM and by 9PM the watch was under 10% battery. Charged the same watch and connected it to the 3T after letting it sit overnight in airplane mode. As of 10PM, about 24 hours after taking it off the charger and after 14 hours connected to the watch, it still reports 80% battery.

I don't want to buy a new phone and the 3T is still fine otherwise, but eating watch batteries is a dealbreaker for me. At this point I'll be replacing a battery a year. Does anybody have any idea how to get Lineage on this phone to play nice with Bluetooth LE devices?
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there,

Have you been able to update to TWRP 3.5 ? I wanted to do it with fastboot but nothing happens when I flash the file...

Thanks!
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Yes, without problems and I updated twrp from within twrp. :)
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Could you tell me how to do it, please? Thanks! :)
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
In TWRP: Install -> Install Image -> Select the file -> Recovery
[OnePlus 3 & 3T Cross Device Development] RKS96:
Does anyone else lose loud speaker when rebooting with 3.5mm jack plugged in? Second reboot with jack unplugged fixes issue. Might be a bug, but I don't think it is that important.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Screen lock seems to disregard delay after timeout, if "Power button instantly locks" is enabled.

I have screen timeout set to 1 minute.

Under screen lock, I have "lock screen after timeout" set to 2 minutes after timeout.

"Power button instantly locks" is enabled.

Every time the screen times out, I have to unlock the screen lock.

If I disable "Power button instantly locks", I don't have to unlock the screen lock during the delay.

It seems like screen timeout is considered the same as pressing the power button in this regard.
[OnePlus 3 & 3T Cross Device Development] snyperius:
Same here. It's been like that since the beginning. It's not that big of a deal, I got used to it. Still would be nice if it could be fixed, though
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Quick and dirty fix would be to hide and disable the "Power button instantly locks" option. Then all settings would do what they advertise.

It's not that big of a deal even though screen timeout and hitting power button tends to happen dozens of times every day. For me it was annoying enough to investigate why screen timeout instantly locked despite the delay I had set. I have learnt to go quickly to lock screen with power button, but losing that is less annoying for me. And that could be also achieved by setting the lock delay to immediate.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
I noticed that when I close an article on the google feed page on trebuchet, the phone freezes for 2-3 second.

I have this bug also on 18.1 (unofficial btw).

@dianlujitao where I can send you logs?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Hello together,

can we upgrade to latest Magisk, or won't it survive a LineageOS Update?

Does anyone know?
[OnePlus 3 & 3T Cross Device Development] snyperius:
I prefer having power button istantly locks on. If the timeout locks the screen, I just unlock it again with the fingerprint reader. It's quick and really not that bothersome.

I use an older version of the LOS recovery and have to sideload Magisk after every update. But I only update once a month, so it's not a big deal. I don't know if newer versions can install zips, but, as far as I know, you have to reinstall Magisk after every update
[OnePlus 3 & 3T Cross Device Development] malerocks:
I never used Magisk with the Oneplus, but I also have a Sony device with LineageOS and Magisk. Magisk stays every time I update that phone via OTA. Maybe its because its phone with A/B partitions and Magisk installs a bit differently on it?
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Stuck in a bootloop with the latest nightly (20210201) - anyone experienced the same? Eventually I get taken back to recovery with a RescueParty notice in the terminal.

The only thing I noticed that was out of the ordinary was that the usual flashing of Magisk that happens after flashing Lineage didn't happen this time.
[OnePlus 3 & 3T Cross Device Development] Flippiej:
I'm bootlooping since 11 January after a normal flash through twrp (3.5.0). I'm also guessing Magisk is at fault, since it happens with any recent LOS build after I've installed the new Magisk stable. There was one line out of the ordinary from the Magisk addon.d script, even though it seemed to be successful.

Dirty flash + gapps + Magisk or any combination or standalone always resulted in bootloop, only a clean install fixed it.

Same issue after updating to the 18-1 build, but I didn't want to try for some time afterwards so I'm not sure if my problem continues (but I bet it does)
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Sorry to hear this - that sucks. Guess we can't update Lineage anymore then?

Where did you get hold of an 18.0 build of Lineage for OnePlus 3T?
[OnePlus 3 & 3T Cross Device Development] Flippiej:
Lol no I was talking about the 18 January build with 18-1. There is no official build of 18.1 yet.
[OnePlus 3 & 3T Cross Device Development] :
Always store and check the recovery log. What did the "one line out of the ordinary" say exactly (stored recovery log is helpfull here). Is the manual update working, if you flash the magisk uninstaller before performing the dirty flash?

Hint: always keep a copy of a recovery log from a succesfull dirty flash to have something you can compare a recovery log from a failed flash to.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there,

Quick questions:

- my power button is dead... is there a way to boot the phone without this physical button on LOS 17.1? :/

- does this LOS 17.1 also work with the OnePlus 3T? I guess it does but would prefer to be sure.

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
Not that I know, but a phone repair shop can repair it for about 40 dollars/ euro's...

Much cheaper then buying a new phone and you can keep your great op3t with everything working ;-)
[OnePlus 3 & 3T Cross Device Development] :
Just read the thread title to be sure. To avoid running into problems reading - at least - the OP and the wiki is highly recommended before flashing anything.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Thanks for your answers! I will check it ouf for repair, of course, hopefully it will work.