yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] kousik:
A quick confirmation is appreciated: if I need to flash latest 17.1 I'll need new twrp, but if I need to go back to stock later, I need to switch back to older twrp too?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
You're welcome:

https://xdaforums.com/showpost.php?p=81427905&postcount=230

https://xdaforums.com/showpost.php?p=81429359&postcount=232

https://xdaforums.com/showpost.php?p=81420207&postcount=224

So... yes, and... yes.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
[MENTION=5091734]dianlujitao[/MENTION]

Are you using TheMuppets vendor files or any other source for this LOS 17.1?

Thanks.
[OnePlus 3 & 3T Cross Device Development] :
Sadly, no nlos-16.0 user seems to have access to a DualShock 4. As stated: without any confirmation I don't push it.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
yes
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
OK thanks, that's weird, I used it also and qti-telephony-common.jar was not good. My phone did not recognize my SIM. I used another one and it worked.

ROM is not LOS though (MagmaOS, AOSP based), but I used your LOS 17.1 kernel and device tree with success.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
The 12.1.2020 os the last update?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes
[OnePlus 3 & 3T Cross Device Development] Mohammed Gabr:
Any chance for kernel 4.4 ,, Lenovo z2 has the same processor and got kernel 4.4 ,, are you trying with it ?
[OnePlus 3 & 3T Cross Device Development] :
Considering the attempts to get a stable 4.x kernel running with op3/t (which failed all and was given up), I guess: no.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I had a similar question at the beginning, our dev hero has already been working on it, here the last state from 4.4 Kernel

https://github.com/dianlujitao/android_kernel_oneplus_msm8996
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
I think it's as good as dead for now.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is there an advantage to using the 4.4 kernel?
[OnePlus 3 & 3T Cross Device Development] :
What so good about it though other than being "the latest" ? A quick search about 4.4 mostly about sound improvement, which won't matter with my 1$ headphone

I rather have a slighly worse (on a paper) audio quality rather than losing dash charging
[OnePlus 3 & 3T Cross Device Development] :
The advantage is upstream support: 3.18.y is eol; 4.4.y is still supported. Most other development is just not used and therefor not relevant for us. e.g. the raid5 code is improved regarding reassambling speed if a disk has been replaced (this has been improved on the 4.x.y sources), but who cares with an op3/t? Though this has been a real advantage on my server...

For audio improvements: it may sound better on a 4.4.y kernel, but I'm pretty sure factors like source (e.g. flac instead of 128Kbit mp3), bt stack and bt codec (e.g. aptx HD or LDAC instead of sbc w/o HD) and the output device itself play in much more hearable.

In the end: if we'd have the choice between similary stable and compatible 3.18.y kernel and a 4.4.y kernel, I'd go for 4.4.y - as long as stability and compatibility differs, I'd go with the more stable and compatible kernel: 3.18.y. I'm not the most gifted kernel dev, if excellent kernel devs fail on making 4.4.y as stable and compatible as 3.18.y, I highly doubt there will be a break through in the near future.
[OnePlus 3 & 3T Cross Device Development] :
So as you said, we'd agree that there's no noticable advantages for op3/t with 4.4 kernel then ;)

Users also often misunderstood about sound improvement too, they think it's about bass middle treble etc, lol that's equalizer, sound improvement should be about the clarity of sound frequencies, which wont matter if you play compressed sound files in a 1 dollar devices :silly:
[OnePlus 3 & 3T Cross Device Development] msmita:
[MENTION=6948251]ppajdek[/MENTION] what about how to skip the metalava api check?, on havoc i use "export WITHOUT_CHECK_API=true" and its completely work. but on lineage that without check api doesnt work anymore...
[OnePlus 3 & 3T Cross Device Development] ppajdek:
Sorry, i have no idea, never got that issue.
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Maybe that's too bold claim, but it seems that on LineageOS 17.1, phones with Exynos SoC are having issues too: https://xdaforums.com/samsung-a-series/orig-development/unofficial-lineage-os-17-1-a3-2016-t4036121
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've been checking Android Q ROMs looking for ones that support encryption and NFC tap and pay. NOS was the only one that had a working NFC solution, but it doesn't support encryption. And none of the ROMs that supported encryption had a working NFC tap and pay solution.

Then [MENTION=6339757]PlayFriik[/MENTION] (unofficial PE) got it working based on work by [MENTION=5422618]xyyx[/MENTION] (NOS), followed by [MENTION=8029593]Gaurav24[/MENTION] (DerpFest)(thanks guys!).

So I thought I'd try copying the NFC files from one of these ROMs and copy them to Los 17 and see if that helped.

And ...

It worked! Tap and pay over NFC using Google Pay worked!

I've attached a zip file containing the files I copied and the script to install them. Note: this is NOT a flashable zip.

1. Extract the zip file

2. Boot into recovery (using TWRP 3.3.1-20200107-SAR)

3. Mount system

4. Using Terminal, navigate to the directory containing the extracted files

5. Run the nfc.sh script using

source ./nfc.sh

6. Reboot the system.

Hopefully all Android Q ROMs will soon be built with a working NFC tap an pay solution.
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Interesting find :)

Maybe [MENTION=5091734]dianlujitao[/MENTION] can explain why currently NQ NFC stack is being used - it would be good to know whether it has some advantages that I'm not aware of.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Is anybody else deeply concerned about the loss of Privacy Guard in LOS? I don't use Root and know of no other way to restrict Bootup and Run In Background permissions.

It's a real bummer.

Fortunately my Pie setup is perfect so i'll just stick with it for however long my 3T survives.
[OnePlus 3 & 3T Cross Device Development] blue-gem:
Dear [MENTION=5091734]dianlujitao[/MENTION] ，The TWRP version of my 3T device is 3.3.1.1. Why do I get “No system installed” after flashing into Los17, or restarting into REC, or unable to flash into magisk, I have already formatted.No one can answer my question.
[OnePlus 3 & 3T Cross Device Development] helderfp:
no more updates for this rom?

Why no news from lineage?

latest official news from lineageOS was on July 02, 2019, what is happening whit lineage?
[OnePlus 3 & 3T Cross Device Development] :
It has been answered allready. The answer is in OP.

First of all: official los release is 16.0.

You can always get the latest status of 17.1:

https://review.lineageos.org/q/branch:%5E.*lineage-17.*+OR+branch:%5E.*master.*

[MENTION=1763460]Dirk[/MENTION]: let's wait for official 17.1. Maybe....
[OnePlus 3 & 3T Cross Device Development] blue-gem:
“It has been answered allready. The answer is in OP.”Sorry,I don't understand what you mean, can you give a specific link?
[OnePlus 3 & 3T Cross Device Development] :
Use the twrp recommended in OP. Search the thread for recommended gapps and procedures (don't ask me to search and read for you, my name is nvertigo67 - my name is neither "ok google", nor "alexa").

BTW: always search/read a thread before posting.
[OnePlus 3 & 3T Cross Device Development] blue-gem:
1.Thank you for your reluctant reply.

2.English is not my mother tongue.
[OnePlus 3 & 3T Cross Device Development] :
That doesn't mean you don't need to stick to forum rules: https://xdaforums.com/announcement.php?a=81
[OnePlus 3 & 3T Cross Device Development] Naudiz:
Yes, that sucks big-time. LOS is becoming more and more a barebones vanilla Android. We already lost theming engine and support for blacklisting phonenumbers in the past.

With every new version another feature is lost.
[OnePlus 3 & 3T Cross Device Development] blue-gem:
I don't need your answer that can't solve the actual needs, what else can you do besides complaining?The only twrp I can find at the moment is "system-as-root", but it doesn't solve my problem, so I came here to find the answer.Leaving my question out, don't complain like a blame, it's a failure.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
First flash SAR TWRP, then the ROM. Link is in OP
[OnePlus 3 & 3T Cross Device Development] blue-gem:
thank you for your reply.I have tried many times, not only need to flash in the specified twrp, after entering rom, remember to select "say later", otherwise the problem remains.
[OnePlus 3 & 3T Cross Device Development] unimke:
+1
[OnePlus 3 & 3T Cross Device Development] Az Biker:
* * * Thread Cleaned * * *

Please follow Forum Rules when posting and make sure your comments are HELPFUL, RESPECTFUL, and directly related to developing this Rom.

Any further comments violating the rules will be deleted and the accounts posting them will be reviewed for restriction or removal.

Let's treat each other with respect and do our best to be helpful. Anything outside of the rules is best left outside of Xda.

Thanks for everyone's cooperation.
[OnePlus 3 & 3T Cross Device Development] :
As soon as this commit is merged https://review.lineageos.org/c/LineageOS/hudson/+/267517/20/lineage-build-targets oneplus3 will still be 16.0 (but set to weekly). Official los-17.1 builds for oneplus3 currently arn't part of this commit. Watch https://review.lineageos.org/q/project:LineageOS%2Fhudson to have the latest status news at hand.

BTW: For me it's ok that the devs do development instead of writing blogs. I'm pretty sure the los team will happily accept help - for developing as well as for documentation. Since los is a volunteer driven community project you may want to consider to help instead of complaining about missing blog posts.
[OnePlus 3 & 3T Cross Device Development] :
Yes, I'm concerned, too. Privacy Guard is surely a "need to have" nowadays, when really a lot of apps are commercial data collectors. Especially the permission to read contacts and calendar are used to generate user profiles. This doesn't only effect the spied user her-/himself, but also otjer people mentioned in comtacts/calendar.

I think it's the increasing complexity: when I've build my first rom from source (aokp jellybean 4.1) it takes about 40 minutes without ccache. A los 16 build takes nearly 4 hours without ccache (75 minutes with ccache) on the very same build host. More soft- and hardware features leads to more lines of code, of course. This does not only to longer build times, but also to more complex tasks to add a feature, here: from p to q g has added some more control over permissions - this makes adding Privacy Guard more complex (may be it would require a complete rewrite). This adds time to development.

Of course this is accumulative: each version requires more effort to add the same feature, while new features are added.

Since the frequency of new android versions stays the same the gap increases; leading to "barebone" roms.

I'd be greatly interested in number of devs working on android at g for cupcake compared to r.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI, oneplus3 has just been added ... Now let's wait for merging.

https://review.lineageos.org/c/LineageOS/hudson/+/267517

# LineageOS build target list
# <device> <build_type> <branch name> <period ("N"ightly, "W"eekly, "M"onthly)>
# Nightly lineage-17.1
beryllium userdebug lineage-17.1 N
chiron userdebug lineage-17.1 N
d850 userdebug lineage-17.1 N
d851 userdebug lineage-17.1 N
d852 userdebug lineage-17.1 N
d855 userdebug lineage-17.1 N
dipper userdebug lineage-17.1 N
discovery userdebug lineage-17.1 N
enchilada userdebug lineage-17.1 N
f400 userdebug lineage-17.1 N
fajita userdebug lineage-17.1 N
gts4lvwifi userdebug lineage-17.1 N
guacamole userdebug lineage-17.1 N
h830 userdebug lineage-17.1 N
h850 userdebug lineage-17.1 N
h910 userdebug lineage-17.1 N
h918 userdebug lineage-17.1 N
h990 userdebug lineage-17.1 N
I01WD userdebug lineage-17.1 N
jactivelte userdebug lineage-17.1 N
jflteatt userdebug lineage-17.1 N
jfltespr userdebug lineage-17.1 N
jfltevzw userdebug lineage-17.1 N
jfltexx userdebug lineage-17.1 N
jfvelte userdebug lineage-17.1 N
kirin userdebug lineage-17.1 N
ls997 userdebug lineage-17.1 N
mermaid userdebug lineage-17.1 N
nash userdebug lineage-17.1 N
[B]oneplus3 userdebug lineage-17.1 N[/B]
pioneer userdebug lineage-17.1 N
polaris userdebug lineage-17.1 N
rs988 userdebug lineage-17.1 N
sagit userdebug lineage-17.1 N
us996 userdebug lineage-17.1 N
vs985 userdebug lineage-17.1 N
vs995 userdebug lineage-17.1 N
z2_plus userdebug lineage-17.1 N

Thank you [MENTION=5091734]dianlujitao[/MENTION] !

Edit: about addonsu package and PrivacyGuard ... https://www.xda-developers.com/line...-addonsu-implementation-favor-magisk-manager/
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Are you guys able to get hold of a Logcat after attempting to (And failing) to Screen Cast? It might help in getting it resolved. I don't doubt this is an issue because I've used previous ROMs which suffered the same. I'd try it out for myself, but I lost my Miracast Adapter last year!

It is Miracast we're talking about here actually? Not Chromecast? I still have a Chromecast about somewhere.
[OnePlus 3 & 3T Cross Device Development] remedya:
I'm picking up daily builds from here.
[OnePlus 3 & 3T Cross Device Development] knpk13:
How did you find that and who's building that? Couldn't find any info on the website or an XDA thread.
[OnePlus 3 & 3T Cross Device Development] helderfp:
i gess is [MENTION=4244522]pitrus-[/MENTION]

see this post https://xdaforums.com/nexus-7-2013/...xus-7-2013-t3673103/post77781628#post77781628
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Thanks. This is what has kept me on Oxygen Os until now, and with nightlies about to start it looks like I'm coming around at just the right time.
[OnePlus 3 & 3T Cross Device Development] remedya:
The builder is [MENTION=4244522]pitrus-[/MENTION] . I've been getting the Nexus 7 (flo) builds from there for the last 3 months and recently noticed he now has OnePlus 3 builds. It is mentioned in the long Nexus 7 thread that [MENTION=4244522]pitrus-[/MENTION] stepped in when the OP stopped building. I'm currently on 17.1-20200309-UNOFFICIAL-oneplus3 and it seems stable but VoLTE on the UK Three network has not worked since I moved away from OxygenOS.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
There's also a Magisk module for this here https://xdaforums.com/oneplus-3/one...es-apps--mods/fix-nfc-tap-pay-module-t4058889
[OnePlus 3 & 3T Cross Device Development] knpk13:
Thanks. Works well for me, dirty flashed it over dianlujitao's build. I think volte doesn't work for me because of regional model differences (4g bands). I don't feel like flashing OOS to check but I need to do it to make sure. I did notice the size of the icons in settings seemed a little smaller which was weird though.
[OnePlus 3 & 3T Cross Device Development] xuser_:
Are these builds enforcing?
[OnePlus 3 & 3T Cross Device Development] remedya:
Yes, SELinux Enforcing.
[OnePlus 3 & 3T Cross Device Development] TheAvengingTITAN:
Do we know what sources he's using?

I find it quite fascinating that he builds literally everyday, I wonder why he doesn't have a thread of his own / way to communicate with the broader 3/3T users.
[OnePlus 3 & 3T Cross Device Development] :
1. It's a build bot

2. XDA isn't the only place to get a custom rom, XDA enforce "Ethical" rules where some doesn't like it
[OnePlus 3 & 3T Cross Device Development] BillGoss:
He's using the official LineageOS sources.
[OnePlus 3 & 3T Cross Device Development] TiagoEsteves:
Can anyone confirm the operation of the Android Auto when attached to the car?
[OnePlus 3 & 3T Cross Device Development] nucleerz:
This looks ominous though..

https://www.androidpolice.com/2020/03/11/safetynet-improvements-kill-magisk-hide/

Hopefully the dev can fix it once again because I rely on my banking app and Google Pay.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I agree. The future is looking grim at the moment.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Will this change break safetynet even if we are not using magisk and just lock the bootloader?
[OnePlus 3 & 3T Cross Device Development] :
If you read the link you've quoted your question is answered. Or is your posting just rethorically. If the latter: you are right.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
I did read the article but my understanding is very limited in this area. As per the article safetynet checks for unlocked bootloader and magisk won't be able to hide that from safetynet. But for OP3, we can lock the bootloader if we are using TWRP 3.3.1-0. So I was unsure if locking the bootloader will be sufficient after this change or safetynet will be able to detect that we are not on the stock rom.
[OnePlus 3 & 3T Cross Device Development] :
Currently magisk hide works. For the future magiks hide may not work anymore. Locking the bl may be sufficient.

If you want to use custom rooted roms and need to use apps that require to pass safetynet, I highly recommend you work on getting your technical knowledge to match the demands of the setup you want to run.

BTW: maybe the good old kernel patch for throwing away the tripped verity flag can be helpful.

All the safetynet stuff is subject to change. See the changes regarding build fingerprint and sec patch date: it can happen every second out of a sudden...
[OnePlus 3 & 3T Cross Device Development] EigenWijsheid:
Cannot receive SMS messages

Hi,

I rooted my oneplus 3t and installed this rom. Evertything seems to work fine (thanks!!), except sms. At first, I couldn't receive or send at all. I Googled and tried several solutions. Now, I can send sms messages using the Textra app, but I cannot receive sms messages no matter what I try. So I can't use Telegram and some other apps that use sms for verification.

I read somewhere that reinstalling modem firmware for the 3t may help, but I cannot seem to find a file.

My technical knowledge is limited. I hope someone can help, I'd really appreciate it!
[OnePlus 3 & 3T Cross Device Development] :
This seems setup dependent, since no one else is expiriencing this. Without detailed setup description no one can help you.

I recommend you clean flash without root and only gapps (pico or nano) installed and check sms. If it still doesn't work: increase logbuffer to at least 1 Mio, reboot, send an sms from a web service to your device and get a log (adb logcat -d). Include ALL versions of used software together with the log in the issue report.

A firmware archive can be found at: https://github.com/nvertigo/firmware-3t/tree/master/archive Most probably you want: https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip Detailed information on the different flavours of fw packages in the archive can be found here: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] EigenWijsheid:
Hi, thanks for replying.

update: flashed the firmware ]https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip

Didn't make a difference.
[OnePlus 3 & 3T Cross Device Development] remedya:
Have you checked the APN setting for your network?
[OnePlus 3 & 3T Cross Device Development] EigenWijsheid:
Thanks, Yes I did, but only a few things need to be filled in apparently for Tele2 in the Netherlands.

---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------

I will try installing different Gapps, maybe that'll help.
[OnePlus 3 & 3T Cross Device Development] :
Your posting is so misquoted, that I can't quote it properly.

For needed information on setup dependend issues: exact version of ALL used software, how it was installed (e.g. backups), default settings related to issue (e.g. which default app is used fpr sms), mcc/mnc and a logcat as described before.

EDIT: did it work on los-16?
[OnePlus 3 & 3T Cross Device Development] Roman91:
how does it works?

I mean, now devs are fixing and adding devices to the hudson repo (i guess its the codename for los17.1), but there's a goal to reach or a deadline?
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
"Hudson" is the original name of the build system that's preparing the nightly-builds, LOS moved to "Jenkins" - a fork of Hudson - and currently their nightlies are running on buildkite.org. But the config files for that process are still named "Hudson" in the LOS repos ;).

... and: sure, there's a goal ... when the devs think it's reached, they will commit the config and nightly LOS17.1 will start ;).

Gtz

Kurt
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
I always found this weird, considering LineageOS is basically a perpetual BETA. None of the official releases are labelled as "Stable" after all.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
All custom ROMs are basically beta, you can however consider the last nightly of each major version of LOS a kind of stable. Aside from OEM stable ROMs, all custom ROMs marked as "STABLE" are just stable enough for daily use, unless the beta version gets tested and validated by loads of people for long enough.
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
That's what I mean, so I wonder why they haven't just started making official builds yet? The last Blog post was over a year ago, so without getting in contact with anyone involved with the project, it's hard to tell what their agenda is.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
As nvertigo said a couple of posts ago
[OnePlus 3 & 3T Cross Device Development] Hazbelll:
Yeah, I saw that, but it still doesn't give a clear indication where they're at or what they intend to do from here. It looks like they're just wrapping up all the initial 17.1 devices for launch right now, so I guess they'll just announce something and begin official builds, but that's mere speculation as they might have other plans after. No, I'm not complaining, just saying it would be nicer if they reached out to the community now and again. If they're looking for volunteers to take care of that, where do I sign up? lol
[OnePlus 3 & 3T Cross Device Development] TheFacepalm65:
Known issues

Hey, I would like to know a few things before flashing this ROM if you don't mind.

Are there any major issues?

Can I use this ROM as a daily?

Is OTG working?

Is FaceUnlock working?

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] Timmmmaaahh!:
[Thread Cleaned]

Also in times of need – especially in times of need! – it is imperative that we keep respecting one another. Be nice, be compassionate and be safe.

-Timmy
[OnePlus 3 & 3T Cross Device Development] EigenWijsheid:
Solved

Hi, different gapps didn't work.

I finally wiped and reinstalled everything and sms works again. Very happy. Great battery usage now.

Only thing that does not work on my phone is receiving calls from contacts with a star during silent hours. Thanks for this rom and help!
[OnePlus 3 & 3T Cross Device Development] knpk13:
I have been using the normal official TWRP till now without any problems. I got a new device so I decided I'd transfer everything from my OP3T and then clean flash it to start over. And I thought I might as well switch to SAR TWRP while I'm at it. So I flashed SAR TWRP and formatted (not wiped) my data. Now whenever I boot TWRP, I get a red line of text in the log "E: Unable to decrypt FBE device" and I'm losing my data when I flash custom roms. ROM and gappa files I copy over to my phone just disappear after a successful flash. I formatted data again and booted TWRP and took a log and a screenshot. Am I not using SAR TWRP properly? Since the OP3 doesn't even use FBE for encryption (and I formatted data which removes encryption), I'm pretty confused.