yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Uqbar:
In the case of electromechanical issues, you'd see also the relevant icons appearing and disappearing.

What I have noticed is that if I flash a nightly with the earpiece plugged in, then the built-in microphone and speaker don't work any more. I reboot with the earpiece unplugged and I fix it.

Sounds more like a SW issue to me.
[OnePlus 3 & 3T Cross Device Development] :
los hasn't updated the blobs to 9.0.4, yet.

It's no pronlem to update your fw from 9.0.3 to 9.0.4. The only problematic fw update is 5.0.x to 9.0.x.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Good news, I'll try it later. Thanks!
[OnePlus 3 & 3T Cross Device Development] :
Please keep us posted with your combination of f2fs and encryption and updating fw from 9.0.3 to 9.0.4 - thx.
[OnePlus 3 & 3T Cross Device Development] psc-m3:
Well.... I tried to reproduce the issue to get the log. But its working with the latest Build: lineage-16.0-20190707 :silly:

Just flashed latest los successfully.

Just for curiosity I tried it once again with lineage-16.0-20190704-nightly-oneplus3-signed.zip and here we go: (relevant twrp recovery log)

writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
writing 1024 blocks of new data
Decompression failed with BLOCK_LENGTH_1
missing 3771664 bytes of new data
failed to execute command [new 2,116564,117588]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 33 second(s).
Error installing zip file '/sdcard/flash/lineage-16.0-20190704-nightly-oneplus3-signed.zip'
Updating partition details...
I:Data backup size is 5031MB, free: 7263MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done

Changelog from 20190704 to 20190707 seems at a glance not that exciting but its TL;DR

Thanks for your attention! :good:
[OnePlus 3 & 3T Cross Device Development] :
Did you check the sha256 hash? This looks like an error in the zip archive:

Decompression failed with BLOCK_LENGTH_1
missing 3771664 bytes of new data
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Worked fine here.

First I flashed the 9.0.4 firmware in TWRP 3.3.1. Then LOS OpenGapps and Magisk.

Now I have the LOS from today with 9.0.4 FW (still BL unlocked & encrypted F2FS - of course)

Magisk is working - SafetyNet Status is passed. No need to reinstall fingerprints or a new pin.

NFC working. SELinux enforcing

So: Everything is as before with firmware version 5.x updates...
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the feedback.

Sidenote: on an rom update (aka dirty flash) it's recommended to just flash the rom and not gapps and magisk. gapps and magisk have placed scripts in /system/addon.d, which backup all necessary files before system is patched unconditionally and restore/reflash them after the system is flashed.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I always format /cache /system and Dalvik Cache before a system upgrade. So /system/addon.d is also new. Therefore I always flash Magisk and OpenGapps :)
[OnePlus 3 & 3T Cross Device Development] :
This is the recommended way for cyanogenmod prior to 12.1 (or 12.0 - not sure). this has changed with cm-12.1, because of issues due to eventually downgrading the playservices db: since play services are autoupdated (no matter of play store update preferences) this can lead to an sqlite update in the automatic play services update, which is replaced by an older sqlite db version from your gapps zip. On the first reboot the (older) just flashed play services expect an older db format, which leads to problems. The addon.d script saves the currently running (aka already updated) version of all files, which avoids this errornous situation, That's why the recommendation has changed after addon.d was supported.
[OnePlus 3 & 3T Cross Device Development] psc-m3:
You are right. The checksum missmatches. I transfered it two times via "adb push" and even tried "adb sideload" on friday. But both files on the phone show different checksums.

Time to throw away a usb-c cable.

btw. why is the .zip not signed?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Ah. Interesting. Then I performed it since four or five years wrong. Lol.

I think I never ran into issues as I always use also the newest OpenGapps.zip - with the newest Play Services version also.

I'll change my wrong behaviour, thanks :angel:
[OnePlus 3 & 3T Cross Device Development] :
Partly - the other part is pure luck. Since opengapps updates it's content from pixel factory images and not from playstore... I've seen quite a couple of times that playstore has updated playservices directly after a clean flash's first boot (of course that doesn't mean that the settings db version was updated, but it's possible...).

---------- Post added at 20:07 ---------- Previous post was at 20:00 ----------

If I run "unzip -l" the second line says "signed by SignApk".
[OnePlus 3 & 3T Cross Device Development] psc-m3:
Indeed, same for the package name "lineage-16.0-20190707-nightly-oneplus3-signed.zip "

But as soon as I tick the box "Zip signature verification" I get:

I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/sdcard/lineage-16.0-20190707-nightly-oneplus3-signed.zip'
Checking for Digest file...
Verifying zip signature...
I:Zip signature verification failed: 1
Zip signature verification failed!
Error installing zip file '/sdcard/lineage-16.0-20190707-nightly-oneplus3-signed.zip'
Updating partition details...
I:Data backup size is 4906MB, free: 7317MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done

Am I ticking it wrong? :cyclops:
[OnePlus 3 & 3T Cross Device Development] :
The phrase used by twrp is [euphemism] a bit misleading[/euphemism]. I.e. if you place a md5sum file with the same name as the rom plus .md5sum in the directory then the rom, the md5 hash is checked. For nlos I ship these checksum file (see: https://drive.google.com/drive/folders/1bV5ViyIhh-AwZcjWQDTfHOy2zBSqNVRK?usp=sharing ). I guess this works with sha256sum, too (havn't tested with sha256, because my build system generates the md5 file automatically).
[OnePlus 3 & 3T Cross Device Development] unimke:
Changing this setting from "vibrate" to "do nothing" should fix it.

Go to settings>gestures
[OnePlus 3 & 3T Cross Device Development] pijen:
anyone having issue with time difference showed on status bar and cLock widget like me? the correct time is in the cLock widget

I did activate aggressive doze mode using franco's naptime
[OnePlus 3 & 3T Cross Device Development] :
I guess you've already tried uninstalling naptime and rebooting. Would you like to share results?

This was on "vibrate" on my tests here: https://xdaforums.com/showpost.php?p=79860202&postcount=2825
[OnePlus 3 & 3T Cross Device Development] :
Hi [MENTION=1763460]Dirk[/MENTION],

As I remember correctly, I alsof had THE PIS error if there is no launcher at all (when I remove this after installing rom but forgot to install another launcher). Seen that way, it could indeed be a launcher issue. No other OS is using Trebuchet, no other OS is getting this error...

Could it be timing where launcher is simply not ready or is crashed on startup because of some missing files after update?

Just thinking.... ;)
[OnePlus 3 & 3T Cross Device Development] realtos:
ola again, just wanted to throw a request feature in which is in OOS, the option to manually set MB usage in data counter so if you install later month you can edit according to actual and not the 0MB reset using providers info

maybe others thougt of this too and could be useful

keep everything cool :)

---------- Post added at 10:01 AM ---------- Previous post was at 10:00 AM ----------

thx , got it all sorted :)
[OnePlus 3 & 3T Cross Device Development] :
When we discussed the launcher (I'm using nove and never expirienced pis), someone else using nova reported pis is still present.

The funny thing with the pis discussion in this thread is, that it comes up every 4 weeks with the very same assumptions just from another user. (last launcher mention is only a few pages back...)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It would be helpful if you explained how you fixed the problem.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Hello matey!

Livedisplay has been confirmed as the culprit now. If you substitute 'Trebuchet' for 'Livedisplay' in the line, "No other OS is using Trebuchet, no other OS is getting this error...", then it makes sense. Whether it can be fixed without removing Livedisplay entirely is yet to be seen. (At least one ROM has done exactly that).

The timing part certainly seems to be something that people have looked at. nvertigo67 explained why that might be some time ago, using technical words that i will never understand. I'm happy with the word 'timing'. :)

I had my first one in a while just a few days ago. Seems to be about one a month for me. I can live with that! Is it any more frequent than that for you?
[OnePlus 3 & 3T Cross Device Development] realtos:
sorry i did what he said i should do and havent noticed it yet upon reboots sofar :)
[OnePlus 3 & 3T Cross Device Development] :
It's fixed on playstore (fpr lineage-16.0:
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Yeah! Just noticed that today. Any idea where the fix came from? Was it on LP's end or on someone else's end?
[OnePlus 3 & 3T Cross Device Development] :
For me the issue is gone after switching launcher, but before I had it a few times a week because I updated with every change in the changelog including cleanup of old items.

These days I only update about once a week but even then with cleanup etc...., no PIS anymore.

So happy with my setup.

Btw, switched to Librechair yesterday instead of Lawnchair.

A little off-topic but worth to read the background I guess..

Already pretty stable btw, removed Lawnchair and is my new daily driver as launcher ;)
[OnePlus 3 & 3T Cross Device Development] karkiankit:
Strange things happened to me today

Was using stock OOS 9.0.4 with MCD kernel.

Couldn't play pubg, phone over heats, lagging was high in PUBG, I swoched roms, kernel and tried everything.

Then I decided to go with lineage. Result was amazing

Pubg was super smooth 60 fps in HD MEDIUM, gameplay was smooth

I used arcade booster to measure fps , it always displayed 60 most of the time with occasionally dropping to 57 in rare case , gameplay felt smooth on median fps setting as well.

Was that FPS app shaddy? Or PUBG performance in this Rom is awesome???

Played 20 minutes classic match and CPU temperature was around 56 only, ( would have reached around 70 in havos and stock OOS)

Any thing happened to you ?
[OnePlus 3 & 3T Cross Device Development] pijen:
yes i've tried to disable naptime and it's fine now

it's just a bit strange that system clock get dozed/stopped
[OnePlus 3 & 3T Cross Device Development] rlees85:
I found some time and got to the bottom of this. In my case it looks like it was the persist partition as I restored a backup of it from when I brought the device 3 years ago, seems OK now running LineageOS 08/07 and firmware 9.0.4 (locked bootloader).

Another observation is the 9.0.x bootloader does not like being unlocked, data loss aside in my case it won't lock again. Had to use EDL to go back to 5.0.8 and make sure the bootloader was properly locked before proceeding to 9.0.x firmwares. Lucky us the LOS / TWRP devs managed to get things working nicely on a locked bootloader ;)
[OnePlus 3 & 3T Cross Device Development] jmadiaga:
Hi.

I just flashed with the July 09 nightly.

The recent button (short tap for recent) is not working.

However the long press for the menu works. I hope this is just on my 3t but any pointers as a work al around this will be appreciated. TIA.
[OnePlus 3 & 3T Cross Device Development] jmadiaga:
Hi.

Flashing with the latest firmware solved the problem.cheers
[OnePlus 3 & 3T Cross Device Development] Ressurected16:
Does the latest build have android Q featutes? Like the Q battery icon?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Had this issue some day ago, too.

Thaught it's my screen (because it's cracked there)

But after a restart (and pressing harder the button) it disappeared.

Did you try to reboot?

Edit:

I don't think that the firmware solves an issue with the buttons. I think it's just the reboot that fixed it (and maybe only temporary)

Anyone else has this problem?

(recent button (short tap for recent) is not working sometimes)
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
I faced it once yesterday. Restart fixed it. I am still on 12-Jun build and never faced this issue other than this one time.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
What makes you think that?

As far as I know there are zero Android Q features in LOS16
[OnePlus 3 & 3T Cross Device Development] realtos:
why? its android pie, not Q
[OnePlus 3 & 3T Cross Device Development] Ressurected16:
Havoc,Colt os are pie roms but they have android Q features.
[OnePlus 3 & 3T Cross Device Development] k1chy:
If they have those features then use them. Don't have to harass the devs for features which are not available. LOS has their own philosophy of OS development, they don't need your negativity here.
[OnePlus 3 & 3T Cross Device Development] Ressurected16:
I wasnt being negative i was just asking if latest build has something new.
[OnePlus 3 & 3T Cross Device Development] :
Change log: https://download.lineageos.org/oneplus3/changes/
[OnePlus 3 & 3T Cross Device Development] Ressurected16:
Great ROM!

First cycle.
[OnePlus 3 & 3T Cross Device Development] :
Do you want to kill your battery?

Try to keep it between 40-80% and never discharge below 20%. Much better for your battery ;)
[OnePlus 3 & 3T Cross Device Development] Maheshzx:
HD medium is not 60 FPS. Extreme Smooth is. This device cannot handle this game in future, so don't worry about gaming performance
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
My frequently contacted persons in the Telephony app (with the star in the tab) gets random wiped.

It's not connected to cache wipe, dalvik cache wipe or updates.

It appears really random.

Anyone else have this issue?
[OnePlus 3 & 3T Cross Device Development] Dirk:
I noticed this myself recently. I assumed it was because i hadn't used that contact for a while. It would be in keeping with the sort of dumb logic that Google applies to things like frequent contacts or frequent used apps. It doesn't matter if you only have one of each, if you didn't use it in the last 5 picoseconds it must be removed pronto. :rolleyes:
[OnePlus 3 & 3T Cross Device Development] :
I think indeed it is a Google issue. Not using Google services myself and never had or have this issue....
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI, LOS addon su (arm & arm64 - 15.1 & 16.0) have been updated .... 20190709 ... Changelogs ?

==> https://download.lineageos.org/extras
[OnePlus 3 & 3T Cross Device Development] :
Most proberbly everything since the last build up to 20190709 from here:

https://github.com/LineageOS/android_vendor_lineage/commits/lineage-16.0/addonsu
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Okay guys, I did it. Yesterday I upgraded two 1+3T to the latest bootloader, etc.

I listened to your advice only to use OpenGapps pico or nano. I've chosen nano. These packages should be better than bigger ones because bigger ones replace some system files.

Well, in the past I've ever used the stock variant and never(!) experienced problems with that.

Now that I use the nano variant I am facing the problem that I am not able to use the Google assistant as usual. What do I have to do to get it back within the Google alarm clock for example? :confused:
[OnePlus 3 & 3T Cross Device Development] generalprobe:
[MENTION=4405529]nvertigo67[/MENTION]

I found a (semi) official document about the NFC capabilities of certain smartphones when it comes to "extended length"

http://www.die-online-ausweisfunkti...ie-mobile-nutzung-der-online-ausweisfunktion/

Sorry that the site is German, but the "OP3" is listed in the left column with "good to very good" support.

So either my phone is defective or it has something to do with lineageOS.
[OnePlus 3 & 3T Cross Device Development] ayamstr:
How did u update Bootloader ?
[OnePlus 3 & 3T Cross Device Development] jakito:
He's probably referring to updating the firmware
[OnePlus 3 & 3T Cross Device Development] Subho1999:
Is Google assistant set as default assistant app? You can check from, settings->apps and notification->default apps ->assist and voice input

If not, set it to Google
[OnePlus 3 & 3T Cross Device Development] :
Is this the issue with setting the pin on German personal id card?

The extended length patch is in and it's working (before that patch the complete communication failed with a frame length error). For the pin setting a user (you?) claimed it's to less power in sending - I can't verify that, so I have to belive.

I've suggested, to verify that pin setting works on oos. And only if it's working on oos, it makes sense to compare (all, not only the two, los is using) the libnfc* config files.

The unsorported extend length is fixed for weeks now.
[OnePlus 3 & 3T Cross Device Development] thomas2403:
The German ID-Card works perfect for me with the AusweisApp2 from F-Droid. I'm on lineage-16.0-20190629 with the original firmware 9.03.
[OnePlus 3 & 3T Cross Device Development] :
Can you change the id-card's pin? After applying the extended length fix, everything was working for the other user, too. Only the changing the pin gave an error indicating the power of the signal wasn't strong enough.
[OnePlus 3 & 3T Cross Device Development] thomas2403:
Yes, it works. I've just changed my pin. One problem is the app, I think. You have to hold the card absolutely still over the whole process. And the position of the card seems to be very important too. My first attempt failed exactly the way you described. Then I changed the position, tried again and it worked. Maybe writing to the card is more sensitive.
[OnePlus 3 & 3T Cross Device Development] rg_gapa:
Is there any known solution for NFC?

It worked well at 20190615 build with 5.0.8 firmware.

It stopped working at 20190701 build with 9.0.3 firmware, now I'm using 20190713 build with 9.0.4 firmware, NFC still can't be enabled in LOS settings.
[OnePlus 3 & 3T Cross Device Development] :
The name of the nfc device has changed with the native OnePlus pie blobs. Fix has been discussed more then once. Search the thread before posting.

Delete /data/nfc/nfaStorage.bin1 from within recovery.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Are you using the stock Kernel?
[OnePlus 3 & 3T Cross Device Development] :
Thanx for testing!

Writing is for sure a more expensive operation then just reading (not limited to nfc).

Maybe this thread is helpful to find a good position for the nfc device: https://forums.oneplus.com/threads/where-is-nfc-chip-in-one-plus-3t-mobile.717392/
[OnePlus 3 & 3T Cross Device Development] rg_gapa:
I've seen posts about NFC but somehow I missed that about nfaStorage.bin1 file.

Removing file didn't helped, but removing custom kernel did the job.

Thank you for your help, I should figure out that myself...
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Interesting, why is the OP3 left in "very good" but the OP3T in "middle" column.

It's the same software and the same NFC hardware. Very interesting. I cannot understand this ^^

---------- Post added at 21:53 ---------- Previous post was at 21:49 ----------

All kernels before Jun 16 don't include the new nfc device name "nq-nci" (see change here: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8996/+/244364) and so nfc will stop working with kernels without this commit but a newer los version.
[OnePlus 3 & 3T Cross Device Development] Naudiz:
I can confirm that changing the Pin of a German ID card through NFC is indeed impossible. Or at least so hard that I never managed to get it to work. I blame the crappy AusweisApp2 though. And I don't care enough to flash OOS just for testing. I'm just glad I'm not the only one.
[OnePlus 3 & 3T Cross Device Development] Dirk:
PIS Update

Remember this post?

"The error is due to LOS livedisplay. Proper fix unknown.

Someone has posted a workaround in our telegram group - this workaround fixes PIS issue at cost of livedisplay."

https://xdaforums.com/showpost.php?p=79854602&postcount=1568

We now have:

"the issue resides in LiveDisplay implementation

if you can live without some LiveDisplay options, flash the "fix" attached below"

https://xdaforums.com/showpost.php?p=79885756&postcount=2029

That post contains a .zip. I hope [MENTION=4405529]nvertigo67[/MENTION] can take a look and decode the contents. There are specific entries that reference msm8998 so i assume it's not suitable in it's current form for the OP3/T. (Maybe can be adapted...?)

I flashed the .zip on my OP5. The attached screenshot shows what is left of the Livedisplay options in Settings. I was using the 'Standard' colour profile before and it still looks the same to me, so perhaps it now defaults to that with the Profile options removed.

It this .zip can be adapted for the OP3/T, and if it works, i would use it on this device. I personally don't need any of the Livedisplay options that are removed. The feedback from people using the fix is positive so far.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=1763460]Dirk[/MENTION]:

Thanx for the heads up.

The zip is easily adjustable. Just replace msm8998 with msm8996 in the script. I won't spend effort in this. Since I'm not suffering from pis, I will not use it myself and don't want to support this script.

My priority is fixing libedisplay, but I've seen no logs other then op5t's. (BTW: From those logs, I still doubt it's livedisplay alone - if at all. But it makes no sense to go through all this again.)

My next priority: If it's really livedisplay, I would prefer a workaround like you described in the previous conversation: Removing livedisplay and replacing with something else. Sadly I have no more information on the replacement (git changes or - even better - gerrit topic).

I'd also like to fix the ota automatic flashing. (JFYI on what I plan to spend time on - not related to pis, I think cuttently.)
[OnePlus 3 & 3T Cross Device Development] Dirk:
I've posted logs from both the OP5 and OP3T and in both cases the same Livedisplay entries existed on a bootup that ended in a PIS hang. In both cases on a subsequent bootup without the hang, the logs were free of those Livedispay entries.

I'll make the modifications to the script and test myself. :good:
[OnePlus 3 & 3T Cross Device Development] :
When you post it here, we can also do the testing/ use it... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Still need [MENTION=4405529]nvertigo67[/MENTION] to help with this:

existlinecount=$(grep -c 'livedisplay' /vendor/etc/vintf/manifest.xml)
if [ "$existlinecount" -gt 0 ]; then
ui_print " installing ";
ui_print " ";
linecount=$(sed -n '/<name>IPictureAdjustment<\/name>/=' /vendor/etc/vintf/manifest.xml)
startlinecount=$(expr "$linecount" - 9)
endlinecount=$(expr "$linecount" + 5)
sed -i "$startlinecount","$endlinecount"d /vendor/etc/vintf/manifest.xml
ui_print " done! ";
elif [ "$existlinecount" -eq 0 ]; then
ui_print "your rom doesnt need to fix";

I've changed msm8998 to msm8996 in all cases. The above is the problem. When flashing the zip it ends with "your rom doesnt need to fix". It's checking for something in the manifest.xml and aborting if it doesn't exist.