yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
I can't reproduce that. I've set all "Touchscreen gestures" to "Do nothing" and rebooted to system: no gestures work.

I'd suggest doing a clean flash with only gapps (nano or pico) and nothing more installed/restored. After first time setup, setup adb, increase logbuffer to 4 Mio and reboot. Then go to "Touchscreen gestures" and disable all. BEFORE rebooting get a complete logcat. Now reboot and test your gestures BEFORE unlocking the device, after unlocking and relocking the device and finally after viewing the "Touchscreen gestures" page (without touching anything, just check tje settings) and relocking. Now get a second time a complete logcat.

Show us both logcats of the clean flash, please.

EDIT: this can be done by everybody suffering from gesture settings don't persist and not only by [MENTION=2863653]vitorgatti[/MENTION]!!!

EDIT2: for the record: set up music controls, torch and camera; rebooted again; works like expected.
[OnePlus 3 & 3T Cross Device Development] vitorgatti:
Did you wait a few minutes? For example, reboot, wait 5 minutes and, with the screen off, swipe up with one finger. Torch should turn on.

Unfortunately this phone is my daily driver full of apps installed so I can't do a clean flash, but this install is recent, 1 month tops. I remember having this exact same issue back in LOS 15, then I went back to stock (for other reasons), and now again I'm at LOS 16. Everything works perfect but this small issue. For now I'm using a Tasker script to disable all gestures 5 minutes after reboot.

If you check the reddit post (inside the bug report), the issue is so weird that the values of /proc/touchpanel/down_arrow_enable and others are 0 as soon as the phone reboots, but after a few minutes they become 1 for some reason. Besides Tasker, I don't have any other app installed that could cause this behaviour.

This issue was bothering me because me phone reboots everyday (scheduled during my sleep), so every now and then I would start the music app or turn on the torch by accident. I don't like gestures :P

When I change gesture settings there's no relevant info in logcat, even in Verbose mode. Maybe with proper info I can provide a full logcat and the issue can be tracked down?

These are the settings I have to "echo 0" to disable the gestures via script:

su -c 'echo 0 > /proc/touchpanel/double_swipe_enable'
su -c 'echo 0 > /proc/touchpanel/down_arrow_enable'
su -c 'echo 0 > /proc/touchpanel/left_arrow_enable'
su -c 'echo 0 > /proc/touchpanel/right_arrow_enable'
su -c 'echo 0 > /proc/touchpanel/up_arrow_enable'
su -c 'echo 0 > /proc/touchpanel/up_swipe_enable'
[OnePlus 3 & 3T Cross Device Development] :
I can't just wait after reboot, or the phone would just sit at the secure boot passphrase screen and later on the sim pin screen. If I wait for 5 minutes after giving the sim pin It just works.

I've read through the gitlab issue and the reddit conversation linked there. I can't reproduce one simgle of the strange effects described there.

Without the possibility to reproduce this, and no traces of the issue in the both logs (as described in my previous posting) I don't know how to fix this. I'm willing to look into, but curtently I've run out of ideas and options to look into something I can't reproduce and leaves no traces in the logs.

On the other hand: if youexpirienced this in 15.1 and 16.0, but the vast majority of users havn't expirienced that neither in 15.1, nor in 16.0, prbability is high, that's no rom issue.

One idea (more out of desperation then deductive): if you auto reboot your phone each night, I'm assuming that you have no sim pin set - perhaps that's the problem. The next point: why is it necessary to rebbot the device that often? Do you work around an issue by that? If so, maybe that issue is causing the "gestures don't persist"-issue as a side effect.

All in all this is really strange...

EDIT: I've disabled secured boot and sim pin and repeated the all tests including 5 min wait before "gesturing". Everything works as expected. Last idea (other then clean flashing without restoring/installing anything, like described in one of my previous posts): why do you need to reboot you device that often? With each more test I'm more sure, that it's setup/configuration dependend.
[OnePlus 3 & 3T Cross Device Development] dmukhin:
It seems I resolved my screen doesn't switch on, it was my quite crazy guess but it might be right:) Well, what I did is to swap qcom,mdss_dsi_samsung_s6e3fa5_1080p_cmd and qcom,mdss_dsi_samsung_s6e3fa3_1080p_cmd nodes in device tree. There is kernel parameter that passed from bootloader that is used by kernel module to choose right panel model node thus I did nearly the same as changing that parameter (I won't change bootloader, of course). And it worked. It very likely means one of:

My cheapest display replacement is made from initially OnePlus 3 display somehow adapted to be in 3T assembly. Or whatever crazy engineer mind could produce:) It could be some other models not fully functional or not passed QA or who knows what

There are still some differences in commands LOS issues and what stock outputs and when applied to this semi compatible hardware it creates such results
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5188739]dmukhin[/MENTION]:

Great finding!

The problem is that the panel shows up as a5 and not as a3. I guess the reason why it's working on oos but not on los is not the remaining differences to the dtsis in oss, but the unification code, that selects the display blobs for each model on boot (https://github.com/LineageOS/androi...mmit/c6973d94fcba39c099cfb25d0d16044286e6ffe0 ).

Currently I've no idea, how to fix this. As long as the a3 panel shows up as a5, I don't know how to make the kernel select the a3 dsi commands. For now I think the best solution is building a kernel like you did for devices with a replacement like yours.

Again: great finding, it wouldn't have come to my mind, that the panel_info sysfs node has "lied" to us!
[OnePlus 3 & 3T Cross Device Development] dmukhin:
AFAIU what panel type used is completely defined by kernel parameter passed from bootloader (thus it is like hardcoded for T and non T phones). But differences in "controller" firmware could play significant role. No fix could be done in LOS I agree. When have time I'd like to create kernel patcher that could be flashed in TWRP
[OnePlus 3 & 3T Cross Device Development] :
How I remove all warnings in twrp terminal in NOS10:

rm -rf /system/etc

ln -s /system/system/etc /system/etc
[OnePlus 3 & 3T Cross Device Development] rohan164:
are we going to get android 10 for Oneplus 3t?
[OnePlus 3 & 3T Cross Device Development] :
Check gerrit (search for branch lineage-17.0 instead of android-10): https://review.lineageos.org/q/proj...e_oneplus_oneplus3+branch:%5E.*lineage-17.0.*

Please don't ask for eta. Please don't discuss lineage-17.0 in this lineage-16.0 thread.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
If I remember correctly we started discussing and testing Los 16 in the Los 15 thread until it was stable enough and then we switched to a new Los 16 thread.

But I'll happily let [MENTION=5091734]dianlujitao[/MENTION] dictate how we handle this when we have a Los 17 rom to play with.

But you are also correct in that we shouldn't ask for etas - ever.
[OnePlus 3 & 3T Cross Device Development] :
If I remember cortectly [MENTION=5091734]dianlujitao[/MENTION] made a beta thread, when his first unofficial build was ready for public, and the beta thread was renamed when 16 went nightly. Discussing any other unofficial build(*), asking for eta or status is just noise, that makes following the 16 related discussions harder. And yes, we had some noise in the 15 thread... ;)

(*) Every dev, providing an unofficial alpha/beta/preview/whatever build can open an own thread, if willing to support such a build.
[OnePlus 3 & 3T Cross Device Development] dmaster2016:
deleted

wrong thread sorry.
[OnePlus 3 & 3T Cross Device Development] rookuli:
Hello, today I run the LineageOS updater and now my Oneplus 3 phone won't start anymore, after displaying the LOS boot animation for a while the phone reboots to recovery and ask for a password to decrypt data. This is strange because the phone wasn't encrypted at all. I can't manually install the LOS zip file because I can't connect the phone my PC anymore. Please help me because I have no idea what to do :(
[OnePlus 3 & 3T Cross Device Development] Dirk:
When did you last update? What Firmware are you on? What TWRP build?
[OnePlus 3 & 3T Cross Device Development] rookuli:
This was the first update with the phone as I replaced the stock rom with LOS about a week ago. Everything worked fine since then.

I didn't changed the firmware at all, I only installed TWRP [3.3.1-0.] and then LOS with Open GApps.
[OnePlus 3 & 3T Cross Device Development] :
The latest twrp doesn't work together well/at all with internal Los updater, manual flashing Los in twrp is working fine.
[OnePlus 3 & 3T Cross Device Development] rookuli:
"Unable to mount storage" and I can't copy anything to the phone, it is invisible from my PC.
[OnePlus 3 & 3T Cross Device Development] :
Your data was encrypted (OOS ALWAYS!!! encrypts). OTA automatic flashing update with 3.3.1.0 on encrypted data (a thread search would have saved you). If you don't have an usb mass storage device and can't connect to a pc, you are lost.
[OnePlus 3 & 3T Cross Device Development] rookuli:
Well, I erased/format everything and now I have a freshly installed LOS ... again :) Thanks for the help.
[OnePlus 3 & 3T Cross Device Development] :
Great mews! I'm happy to read that.

Out of curiousity: how did you install LOS after formating data without pc connection? usb mass storage?
[OnePlus 3 & 3T Cross Device Development] rookuli:
After formatting data and a restart to recovery the pc connection was back to normal, I could copy the zip files with the usb cable.
[OnePlus 3 & 3T Cross Device Development] spaniard:
Install from OOS 5.0.8

I'm going to install LineageOS 16.0, actually on OOS 5.0.8, please correct me if I'm wrong with the installing steps.

Wipe data/factory reset

Flash FIRMWARE + MODEM only (NOT FULL ROM) OOS 9.0.5 - Pie 9.0 (8th August 2019)

Flash LineageOS 16.0

Flash the Google Apps addon package

Flash Magisk

Many thanks in advance
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
This can work - but doesn't have to.

As you wipe all your data the issue with the new firmware and the data gets corrupted isn't bad four you.

And it does not have to happen either (depends on whether your BL is opened or closed and if your /data is encrypted (as it is because OOS always encrypts data)): but if you cannot boot after this procedure because of "encrypted - and wrong password" - you need to format /data in TWRP.

Then it should boot again.

As always: do a backup..
[OnePlus 3 & 3T Cross Device Development] spaniard:
I'll take the format data way and load the files from my laptop, danke schön.
[OnePlus 3 & 3T Cross Device Development] :
Or you use https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 and only wipe data (no format to remove encryption needed).
[OnePlus 3 & 3T Cross Device Development] spaniard:
Already done, worked flawessly, I'll try OOS 9.0.5 a few days before swtching to LineageOS.
[OnePlus 3 & 3T Cross Device Development] Allan_Hun:
I was late for work today because lineageos clock missed my alarm.!

It seems I can not exclude clock from bat. optimisations because optimisation is not available for clock.

So maybe I will just have to get an oldstyle radioclock?
[OnePlus 3 & 3T Cross Device Development] MarcAnt01:
[MENTION=4405529]nvertigo67[/MENTION] I have seen your commit about display calibration from OB29, does that mean that Soft Mode is enforced as default calibration?
[OnePlus 3 & 3T Cross Device Development] :
Would you link the gerrit commit, please?

What do you mean by "Soft Mode"? (Please use the English names and paths [i.e,: Settings->Display->LiveDisplay->Color profile] for settings to avoid confusion)
[OnePlus 3 & 3T Cross Device Development] MarcAnt01:
Here's the link https://github.com/LineageOS/androi...mmit/7872ef0d85dd10c95c13fc06e694f364d690ad0d

(GitHub sorry but am not familiar with Gerrit).

Soft mode is the calibration introduced with some open beta, which is similar to DCIP3 but supports OP3 panel and not only 3T one and is more similar to standard mode. Some users complained so OP reverted old calibration and put it as "soft color mode" option in display calibration.
[OnePlus 3 & 3T Cross Device Development] :
You've linked the los-17.0 branch, it's abandoned for los-16.0 - I don't talk about los-17.0 in this thread: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/217577

srgb and dci-p3 are in the kernel's dtsis and not in the calibtation file. You can find all color profiles in Settings->Display->LiveDisplay->Color profile. Default (as per clean flash) is Standard. Nothing is forced - neither with the above commit, nor without.
[OnePlus 3 & 3T Cross Device Development] MarcAnt01:
Thanks for the clarification (you are right about LOS 17, but if you check 16 branch you'll see the same commit). Anyway, I will feature request in the appropriate place to port Soft Color Mode (it was in Omni Rom dts and HolyAngel ported it for Pie in SkyDragon OS, but LOS dts are totally different)
[OnePlus 3 & 3T Cross Device Development] :
Just saw we are talking of different commits. The one you are mentioning (https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/217578 ) is just about updated calibrations, which has been there before. The calibration has just changed from ob27 and ob28 (on los-15.1). I still don't umderstand, what this file has to do with "forcing dci-p3". Nothing is forced, everything is runtime comfigurable!

BTW: I don't know why the github interface jumps to branch lineage-17.0 even if selected from 16.0 or 15.1. Github web interface is ****, gerrit and local git is so much superior and much less misleading!
[OnePlus 3 & 3T Cross Device Development] dmukhin:
When back to this problem I think I understood real cause. There are five board types supported in stock and s6e3fa5 panel power on commands are different for 15801_DVT and for the rest. LOS command is different to all of them and your change makes it the same as for 15801_DVT on stock.

Bootloader chooses one device tree before kernel loaded according to hardware and qcom,board-id in device tree. There are five device tree blobs in stock kernel and two in LOS kernel but at least for display the same config used for all 15801 and 15811 in LOS. I believe in my case replaced panel doesn't work well with 15801_DVT command but somehow it works with command for s6e3fa3:) Therefore, the problem is in missing support for other boards, I think some replaced s6e3fa3 displays have this problem as well.

BTW: gonna test quick and dirty fix on weekends, let you know results

diff --git a/arch/arm/boot/dts/qcom/msm8996pro-pmi8996-mtp_15811.dts b/arch/arm/boot/dts/qcom/msm8996pro-pmi8996-mtp_15811.dts
index aa15bb5..d41c5c4 100644
--- a/arch/arm/boot/dts/qcom/msm8996pro-pmi8996-mtp_15811.dts
+++ b/arch/arm/boot/dts/qcom/msm8996pro-pmi8996-mtp_15811.dts
@@ -92,3 +92,23 @@
};
};
};
+
+&dsi_samsung_s6e3fa5_1080p_cmd {
+	qcom,mdss-dsi-on-command = [
+	05 01 00 00 14 00 02 11 00
+	15 01 00 00 00 00 02 35 00
+	39 01 00 00 00 00 03 F0 5A 5A
+	39 01 00 00 00 00 02 B0 04
+	39 01 00 00 00 00 04 B4 06 0C 12
+	39 01 00 00 00 00 03 F0 A5 A5
+	15 01 00 00 00 00 02 53 20
+	15 01 00 00 00 00 02 55 00
+	39 01 00 00 00 00 03 F0 5A 5A
+	39 01 00 00 00 00 02 C3 01
+	39 01 00 00 00 00 02 B0 18
+	39 01 00 00 00 00 02 C3 00
+	39 01 00 00 00 00 03 F0 A5 A5
+	05 01 00 00 60 00 02 29 00
+	];
+	qcom,mdss-dsi-post-panel-on-command = [05 01 00 00 00 00 02 29 00];
+};
[OnePlus 3 & 3T Cross Device Development] MarcAnt01:
Sorry for late reply, my feature request is just about implementing the calibration that was present in ob27 (later renamed to Soft Mode in Oxygen OS calibration settings from ob29)
[OnePlus 3 & 3T Cross Device Development] Itachi_Uchiha:
Anyway to get dark notifications without substratum?
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
try swift installer
[OnePlus 3 & 3T Cross Device Development] dmukhin:
Didn't work. Will try more when have time:)
[OnePlus 3 & 3T Cross Device Development] zadock:
Hi! I'm on OOS 9.0.5 with unlocked BL and encrypted device and I would like to flash LineageOS.

Do I need format user data to remove encryption or isn't necessary?

I need install last TRWP, wipe data/factory reset, flash rom and gapps?

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Just to clarify, I didn't add any hacks for safetynet, and didn't test safetynet status without magisk.
[OnePlus 3 & 3T Cross Device Development] sembraottobre:
mirroring ? it works ?
[OnePlus 3 & 3T Cross Device Development] legendavey:
I'm sorry if it came across as a statment that you added any hacks, I was just stating (very gratefully) that it works out of the box without any extra work. :good: :)
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Does somebody know why the Pixel Launcher crashes on LOS 16?

It doesn't matter whether I install it as system-app by flashing OpenGApps or as user-app by downloading the .apk from APKMirror.
[OnePlus 3 & 3T Cross Device Development] michie:
Please use the search function, I already explained why this happens. The rom does not contain the pixel overlay, you will need to flash any pie compatible pixel mod. Beware that you will alter system files so you can not report any bugs here as it will not be a clean install anymore. ?
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Whoops, you are right, I should have searched more in-depth. Thank you regardless.
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Okay, after few days trying I successfully upgrade from Oreo encrypted to Pie encrypted using the method below:

0. Remove any pin, pattern, fingerprint etc.

1. make nandroid backup on /data and transfer the backup to PC

2. manually backup /sdcard to PC.

3. Wipe data with "format data" in order to remove encryption.

4. clean flash Pie, and start up without login to google account

5. Go to system -->Security & location for encrypting the phone.

6. Reboot to Pie and check if the phone is really encrypted.

7. Reboot to recovery. Load the nandroid back up made in step 1 to /data.

8. Load remaining files made in step 2 to /sdcard.

9. Reboot to Pie. Be patient (~10min).

10. Pie is now loaded with dirty flash.

For anyone's interest
[OnePlus 3 & 3T Cross Device Development] alleykat2561:
At what point did you load gapps?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I don't understand why you had to do all of that. Since the 181117 build of this rom it has worked on Oreo encrypted data (FDE).

The error you were getting ("Decryption unsuccessful - The password you entered is correct, but unfortunately your data is corrupt.") only happened to me when trying to use a Pie rom that used FBE (such as NOS).
[OnePlus 3 & 3T Cross Device Development] knpk13:
The OP3/T supports FBE? I thought it only supported FDE.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's not a hardware question but a software one. You can use either one or the other depending on what the rom supports.

However, if you want to switch ROMs and are using encrypted data then you must either use ROMs that use the same encryption method or decrypt the data partition when changing ROMs.

Up to Oreo Android used FDE, but Android Pie started using FBE.

If you're building a custom Pie rom you can choose what encryption to use. And, given that the OP3/T was already using FDE, it makes sense to keep using FDE for Pie builds to avoid losing user data and to allow going back to Oreo (or older) ROMs.

Which is why I didn't start using a Pie ROM until they supported FDE rather than FBE. [MENTION=5091734]dianlujitao[/MENTION]'s Los 16.0 181117 was the first to do so to my knowledge.
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Right after flashing Pie to /system

---------- Post added at 07:59 ---------- Previous post was at 07:47 ----------

I used the source from github to build LineageOS (no code change/repo pick made).

In my past experience, [MENTION=5091734]dianlujitao[/MENTION]'s Los 16.0 build is different from the source from github. This may be the cause I have to make such complicated work - source from github not (yet) support FDE.
[OnePlus 3 & 3T Cross Device Development] :
Many people suffered from "The password you entered is correct, but unfortunately your data is corrupt." when switching from n to o about a year back. I wasn't able to pinpoint, but itnseems related to a combination of when and with which twrp the fprmating was dome, tne rom with which the encryption wasmdone and even a simple firmware switch on an running and encrypted setup could cause it.

I'm no NOS expert, but if I remember correctly, NOS doesn't use fbe but non-accelerated fde. The OP of NOS states that hw-fde is still a "known bug". Also: fbe can't be found with thread search and OP doesn't mention how to change encryption to fbe with fastboot (https://xdaforums.com/search/thread/3737654?query= --wipe-and-use-fbe ). Considering all that I reasonable guess NOS doesn't use fbe. It just doesn't use hardware accelerated encryption like LOS.

---------- Post added at 10:17 ---------- Previous post was at 10:12 ----------

For hardware accelerated full disk encryption you need to pull at least the topics pie-hw-fde and pie-fde-crash-fix as explained at least three times in this thread, i.e. here: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post78455876#post78455876
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Yes I read that, and I was thinking FDE was someting related to display hacks :p.

I only realized today this was related to encryption after [MENTION=2911853]BillGoss[/MENTION] mentioned on few posts back...:rolleyes:
[OnePlus 3 & 3T Cross Device Development] :
For hardware accelerated Full Display Encryption you need an external tool called "hammer"... ;) (SCNR)
[OnePlus 3 & 3T Cross Device Development] realtos:
i believe he makes some changes of his own, the ones he writes in op, all the stuff after repo sync is his changes since a direct build from repo isnt possible afiak
[OnePlus 3 & 3T Cross Device Development] :
Did you realize that the OP is updated and the former link for additional edits mentioned in OP some days ago are merged or abandoned?

If you consider [MENTION=4329165]ivanich[/MENTION]'s and other's postings you can build pretty near [MENTION=5091734]dianlujitao[/MENTION]'s builds. Just needs a bit experimenting... ;)
[OnePlus 3 & 3T Cross Device Development] jianwen03:
Is it just me or is android pie=android oreo with less corners, less useful features & new fancy animations?

what's going on at google?

just let me adjust my call/alarms volume quietly…
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Ikr? I wanted to adjust the alarm volume at night and I woke up everyone in the bus with the loud volume.

This is probably something that can be modified in custom ROMs but certainly not by Google yet.
[OnePlus 3 & 3T Cross Device Development] ivanich:
Hey [MENTION=4405529]nvertigo67[/MENTION] , I noticed that los started shipping Snap since yesterday https://review.lineageos.org/c/LineageOS/android/+/232785 , I compiled ROM with Snap included but unfortunately Snap FC's for me. Do you have the same FC's in your builds?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
No need to format user data.

Just wipe /data (or full factory reset) in TWRP 3.3.1, install los.zip and gapps (just as you already wrote)
[OnePlus 3 & 3T Cross Device Development] zadock:
Thanks a lot!

Can I change the button order? Left to back and right to change between apps?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Yes, there is an option to swap those buttons, don't worry, it's fully customizable
[OnePlus 3 & 3T Cross Device Development] zadock:
Ok, I just find the option, thanks!