yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mchouaibi:
I also have this issue. For me it is because of whatsapp contacts. So every contact who has whatsapp has a duplicate. And if somebody has telegram, it is third duplicate.

I fixed this by installing Google contacts app from the playstore and merge them by going to suggestions. The duplicates are shown there and you can merge them one by one.

P. S. There are a numerous of merge apps in the playstore. But the didn't worked for me like they should.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Yeah very extrange and annoying, I see people with the same issue, for me ir happens in some roms and not in others.

I try nearly every merge apps and they didn´t work for me also and yes, whatasapp is causing this issue in my case.

I install Google Contacts and seems that I can solve my issue but I must do it 1 by 1 and I have nearly 235 contacts to merge...... I also was thinking about trying the Google Dialer + Contacts module for Magisk.

Thanks!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Interesting. So you experienced the exact same crackling we tried to reproduce earlier on OOS? And once you switch NFC off, its gone? I must confess, NFC is one of the first things I switch off - I simply have no use for it.

Please let us know if you test the same on this ROM. Also you mentioned earlier, you didn't have the crackling on all ROM versions and sometimes it started after a while without crackling. Can you match those claims to switching NFC on and off?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Yeah it was present in Oxygen OS when NFC was turned on but it went away as soon as I turned it off. I'll back up my phone, flash LineageOS and turn of NFC and see what happens.

It would be nice to have LineageOS with no crackling noise lol.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
it would be nice to know, where the crackling noise comes from :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Is encryption not working at all with this ROM? I read in the thread that it wasn't working at all no matter if ext4 or f2fs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hassan_1000:
Sorry my bad, I had clean flashed but used a weird gapps because opengapps was taking too long to download (2 hours for 120mb file!). Clean flashed again withoutapps and everything is working perfectly.

Those who don't already know, root is included in advanced settings so no need to flash SuperSU
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
hi. maybe you have the answer for my question? have this build working sRGB mode or not? and you on f2fs or ext4?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hassan_1000:
sRGB seems to work and I was on F2FS
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Try and tell us: if I enable it there is a slight change, I don't know if thia is what you expect. I also don't know if you need to disable livedisplay or set color mode to default in order to get sRGB.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are welcome! I meant something like 5 minutes, perhaps 6; but surely not 15. Something went wrong. What do you see on the display?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hassan_1000:
It was just the bootanimation but it's fixed now. It was because I used a weird Gapps package

Am I allowed to make a small suggestion? Would it be possible to include the notification ticker in this ROM? I love that feature and many 3T ROMs have it. If not, then it's no deal breaker, I'd rather have a solid ROM
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
thanks ))
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
I'm on ext4, and I'm willing to check sRGB for you if you tell me what you like to know. How can I test this for you?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
its so simple. like i sayd already, when you switch it on, colors will be less saturated. just switch it on, and than look at yours icons or maybe photo, it will have more natural colors.

anyway thanks))

upd

don't need to check. im already did this ..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
so i try it. and its really very good, fast and smooth build. :good: thanks for your work.

but, sRGB dosent work..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
What is the hotfix boot.img do? Should I flash it after the ROM?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Well, in that case ... it's not working. I see no difference at all and the setting is not persistent. Every time I open the developers menu again, it's set to off again.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
sRGB is not working as it's not working on any Laos based ROM currently. Maybe a challenge for [MENTION=3456089]nvertigo[/MENTION] to get this working here.

F2fs should work. I use ext 4 for obvious reasons, but I am pretty sure f2fs will work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
So, my first experiences.

I came from stock, ext4 and encrypted, did a wipe (except media) in TWRP and flashed the ROM according to instructions. After that the boot.img hotfix.

Flawless boot. I was up and running in no time!

But, the notification slider on the side was not working. No response from the OS at all. I remembered reading somewhere that a quick solution was to backup and restore the data partition. I don't know what that does exactly, but it worked for me. After that, slider worked and kept working even across reboots. This is probably a LineageOS issue, not specific to this ROM.

I tried flashing the blu_spark kernel (version 41 for custom roms), but that made the system unbootable. A re-flash of the hotfix boot.img restores this situation. I guess this kernel is not compatible or the installation doesn't like the hotfix required for this ROM.

To those who wonder: sRGB is not working, fingerprint sensor is working fine, dual-sim is working but LineageOS lacks the option to temporary disable a single SIM.

I've not been able to gather enough data to comment about SOT or other battery quirks and I've also not used F2FS.

First impression is: this is a keeper! Thanks [MENTION=4405529]nvertigo67[/MENTION] !
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Exactly. It just fixes a minor issue with notification light. Just go to TWRP -> install -> image, choose boot.img and choose boot partition.

---------- Post added at 10:40 PM ---------- Previous post was at 10:35 PM ----------

Interesting what you say about alert slider not working and the workaround. I had no issue when installing koenkk's build the first time and flashed this build dirty. But good to know this is an issue for fresh installs.

About fingerprint, it's working like on stock. On koenkk's build it always was slightly laggy.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
It is very interesting, also because I can't think of a way where a TWRP backup/restore cycle changes something in a way that make the notification slider work again.

I read about this workaround somewhere on this forums in the 3T section. I don't remember where exactly, but it was days before this ROM was released so I can't be related to it. Maybe [MENTION=7896746]koenkk[/MENTION] remembers something about this particular issue and is willing to share his knowledge? :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mad Medik:
Stuck in TWRP

Hi all,

Looking for some guidance where I have gone wrong. I'm using an OP3T which was locked and stock 4.0.2 OOS. I have unlocked the bootloader, and installed TWRP 3.0.4-0. I got a warning in TWRP on launch about not being able to mount storage. I entered my PIN code and AFAIK as evidenced by my being able to create a backup and then transfer it to my PC for redundancy.

All good so far I think.

From the OP:

Wipe data/factory reset - Done & successful.

Wipe system (go back to twrp-home and check if system is UNmounted; if not reboot to recovery before continuing) - I think the way to check this is to go into the Mount menu and if system is checked, that means it is presently unmounted?

Flash LineageOS - Installed using TWRP Install zip file. Indicates successful

Flash boot.img - Installed using TWRP Install image. Indicates successful.

Install the Google Apps addon package (Optional. Use opengapps nano package from 20170120) - Assuming this is the one that you link to in the OP, this fails, saying the operating system is not compatible.

Reboot (as usual: first boot takes looooong ) - I cannot reboot. I have tried all options in the TWRP reboot menu, but they just take me back to the TWRP logo and then TWRP main menu. I have tried holding power but get the same result.

I repeated the process starting back at the Wipe Date/Factory reset but this time, unchecked the box beside System in the Mount menu. Same results proceeding from there.

I have restored my backup and am going to disable the PIN code (thins shouldn't be it but just to remove variables) and try again.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
It failed because the linked Gapps are for lollipop.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Oh ****, really? I had to read that post for typos and other corrections. I missed that. Holy ****. Should get fixed ASAP.

---------- Post added at 11:53 PM ---------- Previous post was at 11:48 PM ----------

Install ROM again and take right gapps. Big sorry for missing that. On opengapps.org, choose arm64, Android 7.1 and any package. Small ones usually have less issues. Then it should work.

No need to disable PIN btw. You should never be unencrypted except you have a very good reason. Encryption on an unlocked device is the only thing that prevents a thief from accessing your data. PIN code, fingerprint, all can be bypassed on unlocked phones without encryption.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mad Medik:
No problem regarding the gapps thing. Its a separate install anyhow. My concern is just getting the phone back running again. After restoring the backup, it booted up but with "No SIM card". The odd thing is that when I check the status, it says No SIM - Bell (which is my network) and under settings, SIM says SIM 1 Active. Anyhow, I'm hoping that is just an APN issue or something that we can fix.

I am now downloading Arm64/7.1/Nano and trying again from the Wipe Data/Factory reset step onward. Can you confirm a couple things for me please - when you say flash the OS and Install the Boot image, in both cases you mean to use TWRP Install, correct? (ie not adb fastboot flash). Im just making sure because you say flash for two things and install for the other.

Next, you say to make sure the system is UNmounted. Do I do this by looking in the Mount option and see that there IS a checkmark beside the system partition (as well as Data and Cache) or there should be no checkmark?

Another confirmation - This is a silly question but I'm grasping at straws now... When I install the Boot.img - I'm assuming that is installed to the Boot partition? (ya, i know it silly but I'm running out of possible problems it could be...)

____

Update:

ARM64-7.1-Nano indicates a successfull install.

Unfortunately, I'm otherwise still stuck at TWRP and cannot reboot into the ROM. If I restore, I am back to the unlocked, rooted OOS 4.0.2 but with no sim card detected. I tested the SIM in another phone and it works. Sigh... I guess I will look to flash back to stock and see if that fixes the no sim error.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If you use the buildin contacts, there's a "merge contacts" item in menu. this allows you to merge all contacts at once, or select which should be merged. No need to do it one by one.

BTW: I'm using whatsapp beta without that issue.

Which gapps are you using?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
I do one by one but in other roms/phone with this issues the builtin contacts app never solves it to me. It´s a really strange issue that I never can find a precise answer or fix for it. Now seems that´s solved. I´m using the latest whatsapp available in Play Store (I always keep all my apps updated) and open gapps nano, the recommended package.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Encryption is working just fine.

---------- Post added at 10:36 ---------- Previous post was at 10:30 ----------

I've been happily doing builds on my own system but have no clue how to update the TZ setting to work with the latest firmware which came in the last build from [MENTION=4405529]nvertigo67[/MENTION]. Can anyone help me figure this one out? Do I need to extract the proprietary bit from the phone again?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'll update cm-14.1, when the last build has proved to be stable. Look at the commits (lg1): cm-14.1 is still on 4.0.2 blobs and therefore on the old TZ. For a current build from cm-14.1 you need the 4.0.2 firmware - but this is completely transparent in the commits.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Can someone give a comment on safetynet compatible, especially if Pokemon go works without fiddling around?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
It is indeed, I've encrypted and everything is fine.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Thanks! FWIW I've been running on your current build since the day it dropped with no issues. Lots of calls. Drove about 1300km while streaming Pandora, some of that with a tablet tethered as well. Solid.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Frosty89:
i done everything by the faq, instal,gaps, etc.

but i have hardcore lags, random app freeze, not working fingerprint sensor, and in the end soft brick, my phone not turn on...

for the 4 or 5 th time i am able to go in the reco, now my phone is formated and restored to OOS... i dont know what i **** up but this was bad....
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
I think, you made something wrong. Maybe twrp, wrong gapps, corrupted zip.. Because no one of us, didn't have this lags or issue.. Its on your side
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Frosty89:
as i say i do everything by the faq, lastest twrp, gaps is open_gapps-arm64-7.1-nano-20170120, original kernel

maybe one of my programs is ****ed up, google photos or Magisk for root

sad because the battery life is really good :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
I will say this.. I has twrp 3.0.4.0 working, and tried upgrading to 3.0.4.1 and I got a failed error message, so I had to actually upgrade the recovery through flashfire (couldn't do it through fastboot because I left my cord at home). After I did this, the recovery flashed properly. I made a backup, and flashed the new rom and rebooted (I didn't flash gapps in the same instance). After I booted into the system the first time after I went through the initial config, I rebooted into recovery and then I flashed gapps and everything is fine. I have noticed some apps are a little sluggish for me at times, and my system froze once. It might be because I installed action launcher from playstore. It froze a couple times, but after I rebooted it seems to be fine now.

I'll test this out further and let you know if I run across any issues.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
To avoid chaosnwith TZ, I put cm-14.1 to the same commit then 141-work: builds expecting now a TZ of TZ.BF.4.0.1-83199.

To get the firmware with TZ=TZ.BF.4.0.1-83199, you have three options: flash oos 4.0.3, flash this rom with "firmware" in the filename or use the flashable firmwaremzip from OP.

To go back to firmware corresponding to TZ=TZ.BF.4.0.1-76917, just restore the bootloader and modem/radio (two checkboxes) from your twrp nand, or flash oxygenos-4.0.2.

I hope this shines some light on this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Ok I installed the rom, and with the unroot zip provided by laos i can run safetynet fine! so far the rom is stable and i had no Problems what so ever besides one:

i tried installing google camera besides snapcam, because i like the panorama feature, and wanting to compare both. BUT here is the problem, the double press to launch camera from offscreen feature does not launch any camera. If i use the feature with unlocked device i can set a prefered action and it works. But it does not if the device is off and locked!

I did set snap cam as prefered camera to launch not the user installed google cam!

(I am on the recommended gapps without anything else on system)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I know, that some people was successful with this method - but in general it's not a good idea to flash gapps out of sequence: Imagine gapps aa part of the rom. Ideally I would like to pack gapps with the rom, but I'm not allowed, since this rom (and laos for that matter) is not google approved.

If you think of the initial setup (aka firsttimesetup), there is a laos part and a gapps part. The latter is nesseccerry not only to setup your google account, but also to initialise the google settings being part of google's additinally installed framewoeksmand services. To accomblish this, laos setup "sees" that gapps are peesent, and starts gapps setup as part of initial setup. After both(!) setup parts are completed, the system (laos) and gapps are setup properly.

If you go through the laos setup before flashing gapps, the complete google setup is skipped, and you can only configure your google acount, but the part of setting up services and frameworks is skipped. This may lead to all kind of trouble.

For twrp: I use the dd method (dd if=twrp.img of=/dev/block/bootdevices/recovery) - no additional app needed, done in less then 2 seconds (excluding the typing... ;) ).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What setting/feature are you talking about? double press what? If you mean the configurable options of the capacitive buttons: they are not supposed to work when screen is off. But just saying "double press", without telling us, what you double press and what setting you are refering to, makes my answer just a speculation...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
sorry my bad :D, i typed this up quickly on my phone! i was talking about the double press on power button to launch the camera! a non 3t specific feature! so probably has nothing to do with your rom, but could be a lineage os bug!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Yes, it does! BUT: Encrypting an unencrypted device does not.

At least it didn't end of January. If anyone wants to test this, go ahead. I was the last guinea pig. If you know what you are doing, all that is required is some time.

I see 2 flaws here:

- Original kernel: You refer to the weeks old kernel for the first build that you flashed seperately? If that is what you are saying, there is your problem.

- Magisk for root: Why would you do so? We have a built-in root solution. You don't even have to enable it like for other LaOS ROMs.

It's not a LaOS bug. It's your error. Once you install a new camera app, you gotta tell your system, which is your default app. This app picker cannot be displayed on lockscreen. So AFTER you picked the default camera, double pressing the power button - even on lockscreen - does work.

If you think about it, its very logical.

Edit: also great to hear that Pokemon GO/SafetyNet works, once you install LaOS root disabler. Perfect! [MENTION=4405529]nvertigo67[/MENTION]: that patch was worth it :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Frosty89:
No, i refer to this: lineage-14.1-20170210-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip this build comes with the firmware. for me this is the original kernel, the one what comes with the rom

and the magisk , is for the magisk hide
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Ok i think i have to rephrase the issue:

1. stock install status: only snap camera is installed. double press power to launcher camera (snap) works both, when unlocked as well as when the screen is locked or off. camera is launched in sandbox mode.

2. install google camera side by side to snap camera, as user application.

3. unlock phone and double press power: choose either snap or google as default.

4. double press power when phone is unlocked: the previously set camera application is launched and works properly.

5. double press power when phone is locked(fingerprint/pattern), screen off or on does not matter: no camera is launched in sandbox mode but the unlock pattern screen shows. Once unlocked no notification to set a prefered camera application shows.

6. after a few tries of launching the camera from screen off state the launch camera option showed up and can be set.

an additional bug i found investigation this issue is when only snap cam is installed and launched in sandbox mode is a white screen before the camera is loaded.

further i have a design improvement proposition: in reference to my screenshot, i think it would clear up things a bit if the hardware button option would have a header.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I just double tested it. Once you press the power button twice, you are asked to unlock. Once you do, you have to choose which camera to use. Choose it, set it to always (might require a second run) and next time you double press power button on lockscreen, it works without issues.

Thats exactly what I would expect it to do.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Ah, I stand corrected. If no one else gets to this by the weekend when I have a little free time I'll give it a try, too much time of the road this week to indulge in a science experiment....
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Just to get this straight:

encryption: the process of changing an unencrypted fs to an encrypted fs.

decryption: reading and writing an allready encrypted fs.

On my last test (long before switching the blobs, decryption was working fine), but encryption was broken. Do you have encrypted an unencrypted fs successfully with our rom? If so I can strike the part in #4.

EDIT: [MENTION=5226211]cmattern[/MENTION]: wrote this the same time you was answering - thanx for offering to test this!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
I'll try to find some time to wipe my data partition down to the bare disk and build up an unencrypted data partition. I found and fixed the problems with encryption on the m8 before getting my 3t so I'm very familiar with the processes. However on the m8 there was an selinux context missing that would break the encryption process as well as prevent decryption of an encrypted data partition, since we can decrypt a properly encrypted data partition we know this is a different problem.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Never tried, but perhaps you have to flash lineage unroot zip before flashing magisk - just an idea.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I've become quite good at making a sepolicy rule from deny messages. If you find a deny being in your way, just drop me the line beginning with "avc: denied" and I put it in a rule.

Keep in mind, if you only change sepolicy, it's enough to buils only the boot.img (make bootimage) and flash it to check tze new rule/s.