yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] bschmidy10:
Out of curiosity has anybody heard when new builds will be back? No rush at all, I understand there were multiple issues causing the stoppage...just curious is all ☺️

* Also I understand this is basically asking for an ETA which is considered horrible but even info about whether it's "days, weeks, unknown"
[OnePlus 3 & 3T Cross Device Development] santacrab.it:
Thank you very much. One last question: what about the banking apps? Can I lock the bootloader back after the flash?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=82204597&postcount=710 ;)
[OnePlus 3 & 3T Cross Device Development] 666biker:
Hello all, can someone help, why when my home or another wifi is connected, then I go outside of wifi range, come back to range after a while and wifi is not connected automatically, it's connect when I unlock phone. What should be an issue? (network 5GHz and has not hidden SSID)

thanks
[OnePlus 3 & 3T Cross Device Development] :
Because it was a little quiet about the recent hack and the process to get everything working again, I was looking for some recent information.

https://www.reddit.com/r/LineageOS/comments/gfudkv/build_status/ is giving some info from Haggertk, where he writes that they hope to have the system up and running at the end of the weekend.

As he is saying; they are in a process of 'rebuilding the entire world', which I think is a hell of a job.

Hope the will manage to get the job done.

All people envolved deserve respect for the work they are doing.
[OnePlus 3 & 3T Cross Device Development] kousik:
Yes I have the issue everyday. Phone automatically drops to silent mode. However I faced the problem in lineageos 16 too, so I started thinking it is some sort of hardware problem as my phone will soon be 4 years old. But if it is a software issue and have a workaround I'd like to hear about it.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Never experienced this. My phone is 4 years old too.
[OnePlus 3 & 3T Cross Device Development] MarkMRL:
I'm on 16 with MicroG. I see that they aren't adding any updates for the MicroG builds. Should I wait for them to publish some builds with 17.1 and MicroG? Or update my phone to this one, and should I still factory reset even if I'm coming from 16?
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I don't have this problem. At least you can disable the notification slider from the settings. You can still control everything like any normal phone without a notification slider.
[OnePlus 3 & 3T Cross Device Development] brianyukc:
Hi everyone, I'm on latest build. The signal the bars didn't make sense from what I saw. Comparing them over a few minutes, signal goes up, bars can go up or down, signal goes down, bars can go up or down.
[OnePlus 3 & 3T Cross Device Development] :
You may want to have a look at [MENTION=7929484]MSe1969[/MENTION]'s hardened los builds: https://xdaforums.com/oneplus-3/one...m-hardened-lineageos-16-0-oneplus-3t-t4034869 is still updated, under active development and with support from the dev on xda (no telegram sh!t).
[OnePlus 3 & 3T Cross Device Development] remedya:
I've not heard anything. It's still possible to build from source and some people are building daily Also my own signed builds are temporarily shared here.
[OnePlus 3 & 3T Cross Device Development] :
As I mentioned here they do expect to have the build platform running again after this weekend.

Did not know Wickenberg.nu; are those builds signed also?

And what when the official build, your build and/or the Wickenberg build are used through each other.... isn't this asking for trouble?

As I expect it will be a matter of days till we have the official builds back and the latest build from the 23th is just a three weeks old.

This is still very very very up to date.... ;)
[OnePlus 3 & 3T Cross Device Development] remedya:
The wickenberg builds are using test keys. My builds are signed with my own keys so the builds are interchangeable with the official builds. As you said, you can wait for next week's official builds.
[OnePlus 3 & 3T Cross Device Development] :
For who wants to know; as "test" I just installed the build of [MENTION=4801280]remedya[/MENTION] (dirty flash).

I can confirm it replaces the official one without any issues in a setup where bootloader is locked, setup is encrypted and twrp with official Lineage 17.1 installed.

So when you really can not wait, this one can do the job for you. Thanks for sharing ;) :good:
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Your bulid was removed
[OnePlus 3 & 3T Cross Device Development] felagund:
I had trouble with GPS on the latest builds the last few days. turns out it was mi home app (someone else on the thread pointed to mi fit).

I was getting good connection and visibility to satelites but no fix. When I deleted it GPS started working ok again. Reinstalled with location and phone permissions debuted and it doesn't cause a problem no more. No idea why this happens.
[OnePlus 3 & 3T Cross Device Development] remedya:
I just checked, the link is still working.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Yep this one works, good.
[OnePlus 3 & 3T Cross Device Development] ΦDroid:
I've been doing some research but cannot find the answer. Does anyone know exactly why the build from the 30th was deleted? The last statement by LineageOS states that the attacker did not tamper with builds and they were breached after the 30th, so why would it be removed? Is there any more recent news on the subject that I can read up on?
[OnePlus 3 & 3T Cross Device Development] punio4:
Sorry for spamming this, but are there any updates on why the microphone stops working?

Might actually roll back to 16.0 because of this.
[OnePlus 3 & 3T Cross Device Development] OP3Ts:
I guess you missed reddit from your search results buddy:)

Goto one of the post on their official Reddit Page

You will get answer for all your queries there. The officials are active there most of the times.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Call & video works for me, u must forgot to cleaning somethin'
[OnePlus 3 & 3T Cross Device Development] ΦDroid:
So it seems the builds were removed for unrelated issues, but pose no security threat. Just checking because I was using the build from the 30th for a bit before I learned about the attack.
[OnePlus 3 & 3T Cross Device Development] Odraci:
Hi. Is ant+ working on LOS 17.1. I know it was working on 16 as I used it regularly. However, ant+ tester shows that the service is not running (SS attached). Can anyone confirm?
[OnePlus 3 & 3T Cross Device Development] remedya:
See attached test on today's build of 17.1
[OnePlus 3 & 3T Cross Device Development] Odraci:
I had the same status until I downloaded the radio service so it looks like it is still not working. Thank you for testing.
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Today's build? I've not seen a build since the 23rd of April.
[OnePlus 3 & 3T Cross Device Development] acetone802000:
you can build an 'unofficial' lineage every day with the official repo

perhaps it's his today build
[OnePlus 3 & 3T Cross Device Development] remedya:
Yes, it's my own signed build using these instructions.
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
He might mean the microphone cutting out on non-phone calls, like if you're trying to use Google Assistant or a recording app. Seems that it cuts out intermittently/unexpectedly for a few of us.
[OnePlus 3 & 3T Cross Device Development] punio4:
Another thing that might be related: The audio often starts skipping after a while when playing back over bluetooth on my car stereo. So it probably has something to do with resource starvation in the audio stack.
[OnePlus 3 & 3T Cross Device Development] PTuT:
+1

I also experience brief stuttering/skipping at the beginning of songs, more pronounced on bluetooth.
[OnePlus 3 & 3T Cross Device Development] drsudarshanbk:
Hi,

After recent update my pixel launcher is crashing.

Also after unlock emergency dialer opening..

Plz guide me
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
May I ask a question. I didn't flash in a while for time reasons.

Now i read in the opener the following:

Shall I use this TWRP version or the "recovery.img" which is placed besides the builds? (whats the difference anyways). I would appreciate an insight ;)
[OnePlus 3 & 3T Cross Device Development] remedya:
Go with TWRP SAR as everyone uses it...its got more features. I have provided Lineage recovery.img as it gets built automatically but I have never installed it on my OP3.
[OnePlus 3 & 3T Cross Device Development] :
The image on the los download isn't twrp but los recobery, of course. Read this thread: los recovery vs. sar-twrp vs. official twrp is discussed in depth in this thread.
[OnePlus 3 & 3T Cross Device Development] kallest1100:
Is there already information how to proceed with lineage?

So far the news is rather sparse.

Lg
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
I installed it a couple of weeks ago and immediately reinstalled TWRP SAR. The Lineage recovery is pretty bare-bones, very few options and no backup option that I could see.
[OnePlus 3 & 3T Cross Device Development] 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 OP3T (BL locked and unencrypted) and my OP5T (BL unlocked and encrypted)

From official build to unofficial build:

Boot to TWRP

Flash/install unofficial build :

- https://lineageos.wickenberg.nu/oneplus3/ - Not signed ... Credit: [MENTION=4244522]pitrus-[/MENTION]

- https://onedrive.live.com/?authkey=!ABqHkg3uGuf_PzE&id=5AA409E7833475FC!6649&cid=5AA409E7833475FC - Signed ... Credit: [MENTION=4801280]remedya[/MENTION]

- https://androidfilehost.com/?w=files&flid=313466 - Not signed ... Credit: [MENTION=9708417]Eric_Lev[/MENTION]

roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-17.1" />
<project name="LineageOS/android_device_oneplus_oneplus3" path="device/oneplus/oneplus3" remote="github" />
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
<project name="LineageOS/android_kernel_oneplus_msm8996" path="kernel/oneplus/msm8996" remote="github" />
</manifest>

Restart to System

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/oneplus3)

Restart to System
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
thanks again, you image works perfectly fine :) Like a new phone now with a half broken battery :D
[OnePlus 3 & 3T Cross Device Development] :
Still learning... I though that unsigned builds were not possible with BL locked.

Or is that encryption related? My setup is BL locked and encrypted, so tested with the signed builds from this link as posted some pages back.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
With locked BL only signed ROMs or ROMs signed with a certain signing key are allowed to boot, depending on how open minded the phone makers are. Luckily Oneplus is very open minded to other developers creations and allows all signed ROMs.

I can't answer if the locked bootloader on the OP3 allows unsigned builds, most probably not as that would expose the phone security wise.
[OnePlus 3 & 3T Cross Device Development] :
But as this post from [MENTION=9708417]Eric_Lev[/MENTION] suggests, it would be possible to dirty flash an unsigned build over a signed build without issues, even with BL locked. That was what I was wondering.... I thought this would not be allowed and lead to an unbootable device....
[OnePlus 3 & 3T Cross Device Development] :
To use the bl unlocked all bootable partitions needs to be signed. For op3/t this is boot and recovery. los, lps recovery and twrp are signed with the aosp berity keys, which allow them to work with a locked bl.

The zip file flashing los is signed as zip files, apks or jars are signed: to verify the integrity of the file itself (together with a checksum file you can ise the verify feature of twrp).

The parts contained in the flashed rom (e.g. apks, jars, apk data) are signed with platform keys, presigend keys (quite some blobs) or whatever is defined. Roms with different platform keys will give trouble if dirty flashed over each other. Obviously the official nightlies and the unofficial build in question use the same platform keys.

As you can see the term "signed rom" is ambigous and just creates bullsh!t if used together with "locked bl" or "dirty flashed over xyz-build" without specifying which signature is meant... ;)
[OnePlus 3 & 3T Cross Device Development] Tolyan009:
"gcam man" - that sounds interesting ;) yes, thanks.

Thanks a lot dianlujitao for supporting LOS for OP3.
[OnePlus 3 & 3T Cross Device Development] vssu:
Hi, can someone confrim if this rom for 3T has the option to adjust volume immediately with the volume buttons with a working multitask UI for landscape usage?
[OnePlus 3 & 3T Cross Device Development] xuser_:
Sar which gcam best for LOS16/17 please...
[OnePlus 3 & 3T Cross Device Development] :
It means that selinux is running in permissive mode (just log violations, but don't enforce rules).
[OnePlus 3 & 3T Cross Device Development] Andrea224:
Guess by yourself :)

I give you a hint: it came out recently with a new version
[OnePlus 3 & 3T Cross Device Development] calos9999:
Rom doubt

What are the differences beetwen this, and official one, when it's ready?

The dev is still the same
[OnePlus 3 & 3T Cross Device Development] BillGoss:
As far as I can work out, Los 17 is still being worked on. So this is not yet "official". Once Los 17 is officially available for our device, this will become the official thread.
[OnePlus 3 & 3T Cross Device Development] :
Look at the los-16 cycle: as soon as los-17 goes official nightly the thread is renamed. As soon as los-17 is build nightly, there will be no experimental builds and no experimental thread (renamed) any longer.
[OnePlus 3 & 3T Cross Device Development] ZZZOOONNNTTT:
Good day! is it possible to use at the same time always on display with double tap to wake up? A very important thing for me, no one of the roms is this possible. is it possible to add this?
[OnePlus 3 & 3T Cross Device Development] Cullub:
Yep, that's a feature you can enable in LOS 17. Can't remember for previous versions, but I have it enabled right now.
[OnePlus 3 & 3T Cross Device Development] ZZZOOONNNTTT:
Are you sure? I checked on version 17, for some reason, double tap worked for me once and no longer. this is strange.

Example: block screen - double tap - screen on, good. - double tap again - screen off, and that’s it. More than double tap did not work until you unlock the screen and all over again.

UPD. it's all with always on display! It's important. Without Aod double tap it's working all time
[OnePlus 3 & 3T Cross Device Development] Simone98RC:
I've two things to report:

SELinux is Permissive as default, so it works properly. However, for security reasons I prefer to enforce it (setenforce 1 from TWRP or terminal app).

By installing Magisk v20.1 I get a CTS Profile Mismatch, the issue maybe related to kernel. I've installed OpenGapps Nano 20191114-BETA, I've tried to hide Magisk and reboot unsuccessfully.

Thanks for the attention :)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
1. It's still in the experimental stage so you expect it to be permissive.

2. CTS issue is the same as any custom rom. There's lots of discussions about this. You can use the attached file to fix the problem. Rename the extension from .txt to .sh and then follow the installation instructions in the file.
[OnePlus 3 & 3T Cross Device Development] Simone98RC:
Thanks much.

Just a question: the mismatching CTS profile will break compatibility with apps that relies on SafetyNet?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
A failed CTS check results in a failed SafetyNet check.
[OnePlus 3 & 3T Cross Device Development] :
Would you be so nice to check this flashable zip, please?

https://xdaforums.com/showpost.php?p=81000651&postcount=3510
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Zip patches Los 17 build.prop correctly.
[OnePlus 3 & 3T Cross Device Development] felixchris:
So I have installed the newest build too. Great update pace, thanks!

I have been observing the problem that quick settings become slow and stuttery up to an unusable point a little more. From my impression it just happens over time until I have to reboot. After reboot it is snappy and then will gradually get slower again. Anyone else experiencing this?

Did NFC get fixed in this build?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
If I flash it now in experimental stage, when it become official will the 17 nightly update on top of it or not?

I'm on 16 and want to flash this one but it's really annoying to set all bank and secure apps on every clean flash..
[OnePlus 3 & 3T Cross Device Development] geiszla:
Have you tried Migrate? It backs up all your application data. Usually works with security apps (although I need to set up my bank app every time).
[OnePlus 3 & 3T Cross Device Development] :
Thanks for this clear information [MENTION=4405529]nvertigo67[/MENTION]; input like this is really helpful to understand the story behind signed builds, signed recovery etc.. thanks again! :good:
[OnePlus 3 & 3T Cross Device Development] jk2207jk:
I'm having issues with Google Assistant using OpenGapps Nano. It's working when I open it from the app drawer, but does not activate with "hey Google" o̶r̶ ̶w̶h̶e̶n̶ ̶I̶ ̶p̶r̶e̶s̶s̶ ̶a̶n̶d̶ ̶h̶o̶l̶d̶ ̶t̶h̶e̶ ̶h̶o̶m̶e̶ ̶b̶u̶t̶t̶o̶n̶.̶ Anyone else have similar issues?
[OnePlus 3 & 3T Cross Device Development] aijazexplores:
+1

This is happening to me too, I am on the official build from 29.04. Audio recording stops while using the camera app and in WhatsApp etc.
[OnePlus 3 & 3T Cross Device Development] aurelieng:
Dual SIM issue here:

System:

- Hardware: OnePlus 3T

- Firmware: 9.0.3

- Recovery: TWRP 3.3.1-1

- Software: LineageOS April 25, 2020

Symptom:

Dual SIM issue: SIM1 (in slot1) works as expected. SIM2 (in slot2) never connects to its network. I use SIM1 mainly for calls, SIM2 mainly for data.

Tried:

- to update firmware to 9.0.6, no change

- to swap SIM1 and SIM2, SIM1 still works in slot2, SIM2 does not work even in slot1, no change

- to remove SIM1 and keep only SIM2 (slot1 or slot2), no change.

- to use different bands GSM/WCDMA only for SIM1 (was GSM/WCDMA/LTE) and LTE only for SIM2 (was GSM/WCDMA/LTE), no change

Hints:

- when I installed LOS17.1, SIM2 was probably locked (I only unlock it when I used mobile data)

- at boot, only PIN1 is asked, not PIN2

- in SIM2's menu, choosing "Advanced > Access point names" crashes `Settings`.

- when SIM1 is not inserted, only SIM2, the `Mobile data` icon in `Quick tiles` does nothing

I looked in this XDA thread dedicated to LineageOS 17.0/17.1 on OnePlus 3/3T, and found several messages complaining about SIM cards not being detected. The problem seems different and the solution suggested is outdated, since the line is now already in `init.qcom.rc`.

The most similar issue is this thread, I cross posted in reddit. I searched gerrit for `dual sim` in the lineage-17.0 and lineage-17.1 branches as well `sim` in the oneplus_oneplus3 tag, without success.

Any idea?
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
So basically, just flash as you normally would?

I hope all's well with the Lineage folks, seems it's taking them a while to rebound.
[OnePlus 3 & 3T Cross Device Development] :
Yes. Have used this build some days, dirty flashed over bootloader locked and encrypted setup without any issues.
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
Good to know, thanks!

I'm BL unlocked, I assume no problems there with the unofficial build?
[OnePlus 3 & 3T Cross Device Development] :
no ;)
[OnePlus 3 & 3T Cross Device Development] aurelieng:
Just in case someone else needs that, at some point:

Summary: `/data/system/radio` seems to be broken. Should be replaced with the same directory from a clean install. This breaks PIN auth, which means that

`/data/system/locksettings.db` has to be removed as well, and the PIN reconfigured.

Steps

0. reboot in TWRP

1. backup broken `data` partition

2. wipe data partition

3. adb sideload `lineage-17.1-20200423-nightly-oneplus3-signed.zip` and `open_gapps-arm64-10.0-nano-20200516.zip`

4. reboot in system

5. make sure that both SIM cards are unlocked and working

6. reboot in TWRP

7. backup working `data` partition (or copy `/data/system/radio` somewhere)

8. restore broken `data` partition

9. move `/data/system/radio` to `/data/system/radio_broken`

10. put instead `/data/system/radio` extracted at step 7, either by gunzip/untar backup, or from the "somewhere" you selected

11. delete `/data/system/locksettings.db`

12. reboot into system

13. unlock both SIM cards

14. set a PIN

Done :)
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Not bad! :good:
[OnePlus 3 & 3T Cross Device Development] Hemuli:
I wonder if this is related or not but I've noticed continuous clipping sounds in video recordings from the bottom (main) mic's channel. Does anyone else have this or is it just my device? Sounds almost like some power rail cutting on and off constantly.
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Greetings everyone.

Can anyone suggest me a kernel for balanced battery and performance, I'm using LOS 17.1 on my OP3T. There's not much options or maybe I couldn't find them.

I haven't rooted my device yet.
[OnePlus 3 & 3T Cross Device Development] :
Default kernel is great, no reason to switch kernels.

Only one other kernel available I guess, which is Mady's kernel, but I am almost sure you will not see much difference with default.
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well very much thank you

Seems like you're using default kernel so can you share your SOT, it feels like my device is draining battery more than usual.

I'm getting around 1-2 hours of SOT.
[OnePlus 3 & 3T Cross Device Development] :
Then your battery is dead or you have services/ app's running which are draining your battery.

For stats and screenshots see:

link1

link2

link3

or my over-night no-drain screenshot:

link4

Just a simple search on 'drain' 'battery stats' etc.... will give you a lot of information... ;)
[OnePlus 3 & 3T Cross Device Development] :
That means in the first place: clean flashing completely avoids this issue.

Always remember the recommendation: on major version bumbs or rom change a clean flash ist recommended.

EDIT: if you talk of "wipe data partition", what do you mean? You can wipe data (meaning all settings (incl. persist props), apps and app data is deleted, but sdcard is omitted) or you can format the data partition (which creates a new fs on the data partition).
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
I haven't experienced this myself.
[OnePlus 3 & 3T Cross Device Development] arunkumarts:
Noobie here. Is los 17.1 stable for OP3t? To use it as a daily driver. Or please direct me to a stable LOS version. Please and thank you.
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
It is, yes.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Slightly OT but formatting /data in TWRP does not actually format anything as it would also wipe Internal Storage (/data/media). To really format /data in TWRP you have to change fs to some other type (Internal Storage will get wiped too).
[OnePlus 3 & 3T Cross Device Development] knpk13:
Huh? Don't think that's true. How do you know that?
[OnePlus 3 & 3T Cross Device Development] :
I think there is a misunderstanding between the wipe and format function in twrp.

Wipe is only erasing the stuff in /data but not your sdcard, the 'Format Data' function, where you have to type 'yes' is actually doing a complete format of /data including the sdcard.