yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I suggest a clean install.

Backup your personal data (from device to PC)

Boot to recovery.

Wipe cache, Dalvik cache, system and data ... Optional: internal storage

Reboot to recovery

Copy the latest build + Gapps (pico or nano only) + SU (if needed - LOS su addon for example) on internal storage (from PC)

Flash build + gapps + su (if needed)

Reboot system.

Enjoy ... ;)
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Well, I did a clean install yesterday. The clean install gave me the not working camera, so that's when I started flashing the other firmware and so.

But if there is a chance, that I can get it to work when I do a clean install of Lineage OS with the Pico Gapps and then flash the OxygenOS 5.0.8 firmware, then off course I will....

Google restore the apps and data?
[OnePlus 3 & 3T Cross Device Development] cultofluna:
I'm Using the 9.0.3 firmware without issues
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Ok ... clean install with only build ... not gapp and su... for testing camera.
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Trying this now, but to be sure: no firmware, no gapps, no su?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Full wipe + only flash build
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Okay, did this and checked the camera.

Same, camera doesn't open first time, second time I get the 'camera stops, App-info, Close App' window
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
To be sure:

TWRP = 3.3.1-0 or 3.2.3-10

FW = 5.0.8

all partitions have been wiped before flashing the build ... ?

If right, it's probably a hardware issue

To confirm it, flash OnePlus official build ... https://www.oneplus.com/support/softwareupgrade/details?code=6 ... if OP3T.

Edit : OnePlus 3 Rear-Facing Camera Replacement

==> https://www.ifixit.com/Guide/OnePlus+3+Rear-Facing+Camera+Replacement/72752
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
TWRP - 3.3.1.0

no special FW, just the Lineage OS 16.0 rom file

I'll try again

and then try flashing the oneplus build

Thanks for your time! I'll report back later this evening
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
So after another faulty flash, I flashed the OnePlus Build you suggested and yes, it isn't a hardware problem. Camera is working in this build.
[OnePlus 3 & 3T Cross Device Development] :
LineageOS does not contain any fw. You are respomsible to have amcompatible fw installed prior to flash OS.

Read the OP and keep in mind what has been the latest fw at the date of last editing OP: 5.0.8.

So YOU NEED TO MAKE SURE THIS FW IS INSTALLED BEFORE FLASHING THE ROM!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4624630]-Fedde-[/MENTION]

Did you really flash 5.0.8 fw ???

Because you have written :
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
I think I did... but for now? Now that OOS 5.0.8 is flashed so with the 5.0.8 firmware, can I now flash Lineage OS again?

Do I have gapps right after it? (it's explained like that in the tutorials)

Or do you think it is better to update to OOS Pie? And then flash Lineage OS?

(I know another bunch of questions, but I want to do this right! So thanks again)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
As you have just installed the latest version 5.0.8 of OOS, you have 5.0.8 fw on your device.

Follow the OP instructions or https://wiki.lineageos.org/devices/oneplus3/install .... as previouly suggested by [MENTION=4405529]nvertigo67[/MENTION]

As reminder:

Even if not specified in OP,

1- You need OxygenOS 5.0.8 firmware, 9.0.x firmware is not recommended. ... DO NOT UPDATE TO OOS PIE !

2- Open Gapp pico or nano is strongly recommended to avoid modifying system files.

Boot to recovery.

Wipe cache, Dalvik cache, system, data and internal storage

Reboot to recovery

Copy the latest build + Gapps (pico or nano only) + SU (if needed - LOS su addon for example) on internal storage (from PC)

Flash build + gapps + su (if needed)

Reboot system.

Enjoy ... Hope so !

Edit: don't forgot to encrypt your device ... Settings > Security & location > Encryption & credentials
[OnePlus 3 & 3T Cross Device Development] :
Just found the edit. Sorry for the delayed response. The PIS is not from bootdevice directory is not ready. BTW: the commit doesn't make sense. The commit message is misleading: the symlink command ALWAYS waits till the source of the symlink is ready. The correct message should have been "symlink bootdevice in 'on fs" instead of 'on init'. This may(!) shorten the time of booting, because on "on fs" there is no time for "wait", because dev fs is ready long before on fs.

Since it's changing the boot timing (if at all, only by some split secomds), this may have generated the hope to fix PIS, but the longer I look at this, I guess something completely differnt has been addressed by this commit.

Do you have any news on the other attempt to fix PIS you mentioned? Or did I misunderstood, that som other dev has some super secret insights, which will fix PIS?
[OnePlus 3 & 3T Cross Device Development] Dirk:
The problem with super secret insights is that they're super secret. If anybody knows, they ain't telling! Except for the one ROM which removed Livedisplay, the PIS bug is alive and well.
[OnePlus 3 & 3T Cross Device Development] :
GPS

May I ask to try this:

disable all 4 google location ****s

Energency Location Service

Google Location Accuracy

Google Location History

Google Location Sharing

use the QS tile to "set device only"

activate a widget using location (i.e. chronus from playstore with weather activated and "Geolocated usimg network"

reboot

What do you see in the status bar? Is the location icon always displayed?

While the QS tile is on "Device only", deactivate location by tapping once on the tile

reboot

activate location by tapping once on the tile

go to homescreen

pull down QS again

In which mode is the location service running now?

Can you activate high accuracy using the QS tile, while Google Location Accuracy is disabled?
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Too bad... same problem, camera crashes again.

Is there a way to read out the firmware version I have now?

Does it solve the problem to reflash the 5.0.8 firmware?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
5.0.8 FW for OP3T :

https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/

5.0.8 FW for OP3 :

https://www.celsoazevedo.com/files/android/oneplus3-modem-firmware/

Boot to recovery

Flash 5.0.8 fw

reboot to recovery

then clean install ... again

Edit: OP3 or OP3T ?

---------- Post added at 20:54 ---------- Previous post was at 20:50 ----------

disable all 4 google location ****s ==> Done

I use Chronus.

Step 1:

What do you see in the status bar? Location icon

Is the location icon always displayed? Yes

Step 2:

No location icon when disabling location service

Step 3:

Device only

Yes I can enable High accuracy
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
3T

Flashed firmware OnePlus3T_5.0.8-13-12-18-FIRMWARE-flashable.zip

Rebooted to recovery

Did a clean install, now only the lineageos rom (no gapps, no su) to be sure (lineage-16.0-20190614-nightly-oneplus3-signed.zip)

Camera crashes...

(it must something noobish I'm overlooking, but I can't think of anything - anyway thanks!)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Boot to recovery

Flash 5.0.5 fw

Boot to recovery

Flash 5.0.8 fw

Boot to recovry

Flash only build

and ?

Edit: you must to reboot to recovery after flashing the firmware
[OnePlus 3 & 3T Cross Device Development] simmeone:
Sounds strange with the camera issue... No problem here.
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Still no luck!

I did exactly as you're saying. Downloaded the older FW and rebooted after flashing the fw's.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Boot to recovery

Wipe > Advanced wipe

Format cache, data and system as ext4

Reboot to recovery

Copy build on external storage (from PC)

Flash build

Reboot system

And ?
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Nope.. still a crashing camera
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Sorry, I don't know why your camera doesn't work.....
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Okay, once again thanks for your time and effort!

I think it's better for my phone to go back to Oxygen OS
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
One last attempt:

Please, could you perform a clean flash with the latest version (20190615)?

==> https://mirrorbits.lineageos.org/fu...age-16.0-20190615-nightly-oneplus3-signed.zip

because you've always used the same build (20190614) in all your previous flashes... Unless I'm mistaken.
[OnePlus 3 & 3T Cross Device Development] -Fedde-:
Thank you! I will try this evening, but I came to the Lineage OS rom after trying the /e/ foundation rom.

So my hopes are not really high.

(I thereby think it's not rom related)

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Your camera works fine on OOS 5.0.8 ... as you said (see above) ?

If right, it is not a hardware issue .... so, it should work on LOS 16 ... IMHO.

(check this evening that the 5.0.8 fw flash doesn't generate error messages before rebooting to recovery)

Edit: Important change ... see the post just below (https://xdaforums.com/showpost.php?p=79736966&postcount=2382)

Download 9.0.3 fw ==> https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/.

Reboot to recovery and flash 9.03 fw.

Reboot to recovery and wipe all the partitions.

Reboot to recovery, flash the

latest

build and so on.

if necessary, see this post ... https://xdaforums.com/showpost.php?p=79737571&postcount=2385
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Notification on firmware migration

It's been several months since OP released official Pie. Despite the infamous data corruption issue with unlocked BL, there's no evidence they'll gaf. Now that OOS "stable" is released, there's no reason to keep waiting for them to fix their firmware, and most likely that won't happen. I'll pull in new blobs from OOS 9.0.3 in the next nightlies, and the minimum FW requirement is OOS 9.0.2.

Since lineage started supporting locked BL few weeks ago, if you're already on locked BL just simply flash the new FW without concerning on losing data.

For those using encrypted data and unlocked BL, my personal suggestion is temp relock bl, upgrade FW and unlock again (if you really hate locked BL). If TWRP is installed you won't be forced to factory wipe, so don't be warried about losing data.
[OnePlus 3 & 3T Cross Device Development] ivanich:
Thanks for the explanation, could you please add info on how to flash build with new blobs/fw for those who use unlocked BL and unencrypted data(without data loss)?
[OnePlus 3 & 3T Cross Device Development] caryle:
Dirty flash? Try to make a clean flash. Everything you mentioned is working fine on my phone.
[OnePlus 3 & 3T Cross Device Development] mumapizza:
Could someone please check if we can block private calls? natively
[OnePlus 3 & 3T Cross Device Development] hauckk@sfreserves.org:
Idk about natively but hiya app on playstore does that
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes it does and it works fine.

Edit: I tested blocking a phone number and it blocks both calls and SMS messages. Is that what you wanted to know? I'm a bit confused as to what you meant be "private calls".
[OnePlus 3 & 3T Cross Device Development] jerryhou85:
Dear all,

I have removed some off topic posts from this thread. Please discuss in civil manners and respect each other's opinions. Thank you.

Regards

Jerry
[OnePlus 3 & 3T Cross Device Development] uttam.ace:
Thanks for ROM, working fine here.
[OnePlus 3 & 3T Cross Device Development] :
build from source

[MENTION=5091734]dianlujitao[/MENTION]:

If I follow the OP source code instructions by picking https://review.lineageos.org/q/proj...plus_oneplus3+status:open+branch:lineage-16.0

I get:

ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep permissive *mk
BoardConfig.mk:BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive
ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $

Since you've written in the 12/05 changlog that selinux is running permissive now, I guess I missing something, havn't I?

Also: the resulting build is booting up to the point the encryption password is requested, after showing the dialog for hlf a second the devices shuts down (including shutdown toast) and reboots to recovery. I guess I've missed something.

console-ramoops attached.
[OnePlus 3 & 3T Cross Device Development] mumapizza:
I mean when someone calls with unknown number. Can unknown number calls be blocked?

Im asking because i read this article: https://www.xda-developers.com/android-p-blocking-calls-unknown-private-pay-phone-numbers/?ampcf=1

but thought maybe its google dialer exclusive
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Ah, that's functionality isn't available in the stock dialler.
[OnePlus 3 & 3T Cross Device Development] :
One of the problems here seems to be libcryptfs_hw is missing compared to [MENTION=5091734]dianlujitao[/MENTION]'s build. Additionally cherry-picking topic pie-hw-fde builds libcryptfs_hw, but the reboot stays the same.

Does anybody know what I need to get a working build, like 1205?
[OnePlus 3 & 3T Cross Device Development] ivanich:
Currently have this in my build script

repopick 235128 235402 235270 235271 235388 235389 235398 235403 235934 234980
repopick 236381
repopick -t pie-linked-volumes
repopick -t pie-fde-crash-fix
repopick -t pie-qcom-sepolicy

I'm not using encryption though
[OnePlus 3 & 3T Cross Device Development] :
Booting 16 on encrypted f2fs without autoreboot to recovery!

In addition to your cherry picks I've picked pie-hw-fde (of course, sic!). I've completely missed the topic pie-fde-crash-fix. Thanx a lot!

EDIT: just for completeness: since libcrypt_hw is commented out in snippets, you need to place

<project path="vendor/qcom/opensource/cryptfs_hw" name="LineageOS/android_vendor_qcom_opensource_cryptfs_hw" />

somewhere in .repo/local_manifests/*.
[OnePlus 3 & 3T Cross Device Development] unimke:
Guys can this ROM be used as a daily driver. Is the latest build okay?
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Yes.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Just to confirm, I know it may just be my impression. But does anyone feel that the system is not as fluid when compared to other Pie ROMs? I have some minor lags in the animations and app switching.

I have already checked my RAM consumption and it is normal as it always was (about 2.5/3GB free).
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
OP has mentioned that the caf kernel which is used in all msm8996 (SD820/821) devices is not supported well enough by caf, compared to say, SD660 devices. So we'll either have to wait for the kernel source drop from op3's official pie update, or switch back to oreo's kernel. For now lineage devs for msm8996 devices are still using CAF's but it may change in the future if things don't improve in CAF's side
[OnePlus 3 & 3T Cross Device Development] knpk13:
Do the other Pie ROMs use a different kernel then? I thought they were based on Lineage.
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Some do have a custom kernel, but after nougat, the only pie / oreo ROM I've tried is lineage 16 so I can't speak for other ROMS.
[OnePlus 3 & 3T Cross Device Development] caryle:
Will 3t get a kernel support EAS for custom ROM? I saw a kernel support EAS for oxygen.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
[MENTION=5091734]dianlujitao[/MENTION]

Updates weekly, monthly or if necessary?

Thank you for the very stable und smooth rom!
[OnePlus 3 & 3T Cross Device Development] helderfp:
I have unencrypted data unlocked bootloader and latest firmware working without problems.

Just flash firmware than flash rom, wipe dalvik and cache, reboot, done
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I am encrypted on ext4 and unlocked BL... After several attempts, I ended up peforming a clean install.

I downloaded 9.0.3 fw here : https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/

Procedure

First step : I made a backup of my personal data and used Migrate app to backup my apps and sms (play store - see my signature)

Second step : I performed a clean install

1. reboot to twrp (3.3.1-0)

2. flash 9.0.3 fw

3. reboot to twrp , if userdata is not decryptable anymore, hit "cancel"

4. wipe system, cache and dalvik

5. advanced wipe ... format data by changing file system (ext4 for me to remove encryption)

6. reboot to twrp (optional : format on ext4 or f2fs and then reboot to twrp)

7. flash the latest build + gapps (pico or nano ... recommended !) + su (if needed)

8. reboot to system

9. enjoy ... hope so !
[OnePlus 3 & 3T Cross Device Development] Cogitoate:
Back button not working, no back button options in the settings

I'm using the 15th June nightly on a oneplus 3T, the hardware back button on my phone has stopped working, and there are no settings for the back button in the settings menu, this has been happening since the 12th June build, is this a known issue?
[OnePlus 3 & 3T Cross Device Development] :
Back button is still working for me.

There hasn't been settings for the back button, but "long press to kill foreground app", which is still available in devopts.

EDIT: s/back button/hardware back button/g
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
+1 ... Back button is still working for me.
[OnePlus 3 & 3T Cross Device Development] Cogitoate:
So, there aren't any extra settings under the 'buttons' menu in systems for the back button the same way they are for the recents and the home buttons?

Really? I remember having customizable options for long press and double tap for each of the capacitive buttons.
[OnePlus 3 & 3T Cross Device Development] LorBer13:
Where we can find the firmware 9.0.3? Is it safe to flash it on locked bootloader without brick?
[OnePlus 3 & 3T Cross Device Development] :
Honestly, Idon't know for sure - I've always used only the long press kill function.

From a logical point of view (compared to the recents button customization): short press isn't comfigurable, because you would loose the back function; long press can't be configured, because it's reserved for long press kill in devopts. At this point you run out of options that are unused and free to be configured. So I reasonable guess it wasn't there, but I may be wrong.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
OP3T : https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/

OP3 : https://www.celsoazevedo.com/files/android/oneplus3-modem-firmware/
[OnePlus 3 & 3T Cross Device Development] knizmi:
Just FYI - I used to have an unlocked BL with encrypted data and I tried dianlujitao's suggestion to lock BL, upgrade FW and unlock again. After locking the BL, however, I was unable to boot into system or recovery. I am not writing this to complain, but to warn other people that this can happen and that they should only try to perform the upgrade when they have enough time to recover from an unbootable phone in case it goes wrong.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
It is obvious that many people will have similar problems... :(

It would therefore be wise to detail the different procedures for updating the PIE firmware via OP because the next build will need at least OxygenOS 9.0.2 firmware :

==> https://www.lineageoslog.com/16.0/oneplus3

and it's coming soon

==> https://builds.lineageos.org/devices/

IMHO, it would be wise to recommend a clean install.
[OnePlus 3 & 3T Cross Device Development] :
Native Oxygen pie blobs and firmware

As [MENTION=5091734]dianlujitao[/MENTION] has explained, it's questionable if and when Oneplus will fix the bootloader issues.

The recommended directions (relock bootloader->update firmware->optional: unlock bootloader again) doesn't work as expected for some useres, I strongly recommend to reformat and reencrypt the userdata partition. This is the time for a clean flash incliding reformating userdata.

That being said, I can offer a (quick'n'dirty) temporary solution for updating. Since the updated bootloader (9.x.x) doesn't like being installed when the old bootloader (5.x.x) is unlocked, why not just keep the old bootloader and keymaster from 5.0.8, and take everything else from 9.0.3?

For reference see:

https://xdaforums.com/showpost.php?p=79542744&postcount=517

https://xdaforums.com/showpost.php?p=79690946&postcount=592

Modded firmware

Prerequisite:

Only use, if all three points are true:

you are on 5.x.x firmware (or - very unlikely - you are on a previous version of this modded fw)

the bootloader is unlocked

your userdata partion is encrypted (aka "device is encrypted")

Proofed to work with OOS 9.0.3 (needed to be flashed after(!) the rom for OOS, of course) and nlos pie-blobs-alpha builds. Proofed to work for chaging between 9.0.3 firmware and 5.0.8 firmware on unlocked bootloader and encryption without any flaws.

OP3: https://github.com/nvertigo/firmwar...op3/oxygenos-9.0.3-bl-km-5.0.8-firmware-3.zip

OP3T: https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.3-bl-km-5.0.8-firmware-3T.zip

Happy flashing
[OnePlus 3 & 3T Cross Device Development] kryzeK:
I've clean flashed LOS 16 and userdata on last week. I'm decrypted, unlocked bootloader and coming from OOS 9, I need reformat any thing in future builds?

(Downloading your modded fw)
[OnePlus 3 & 3T Cross Device Development] :
If you come from OOS 9.0.3 and havn't flashed any other firmware or if you're unencrypted (remember OOS force encrypts, no matter if a secured boot pasphrase is set), just go ahead - no need for modded fw.
[OnePlus 3 & 3T Cross Device Development] :
Maybe a good moment too for switching to 3.18.140 kernel? ;):good:
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Oh nice! Downloading official fw then, thanks for explain it to me
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Latest official TWRP works with locked bl. Also I'm curious about why you were unable to boot to the system.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
NEVER
[OnePlus 3 & 3T Cross Device Development] :
Haha, that's clear! :good:

May I ask you why [MENTION=5091734]dianlujitao[/MENTION]; I am sure you have a good reason for this ;)
[OnePlus 3 & 3T Cross Device Development] knizmi:
That explains TWRP - I was still using an older version.

Not sure what went wrong with system (I was at one of the last week's builds), but I couldn't decrypt data - android kept refusing my password at startup. All I did was locking the bootloader with "fastboot oem lock".

Also, I didn't check the state of "Allow OEM Unlock" before I locked the phone (and of course it was disabled), so I had no easy way of getting to system or recovery (fastboot boot twrp-3.3.1-0-oneplus3.img gives you "FAILED (remote: unlock device to use this command)")

Yeah, I know I didn't really do any preparations before the update, but I expected to get into system without any hassle. I'll sure remember to double check my settings next time.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I downloaded and flashed 9.0.3 fw a few hours ago. After several attempts, I ended up performing a clean install (i.e. build 20190615 + pico + LOS su).

See this post: https://xdaforums.com/showpost.php?p=79737571&postcount=2385

My setup: FW 9.0.3 / TWRP 3.3.1-0 / ext4 / unencrypted / unlocked BL

Fyi, I just flashed the latest build (20190616 = new blobs from OOS 9.0.3) with Lineage Downloader app (as OTA updater).

==> No sweat … for now.

[MENTION=5091734]dianlujitao[/MENTION] : Thanks for the job !
[OnePlus 3 & 3T Cross Device Development] ivanich:
Flashed today's build, update fw booted fine but locksreen pin was broken, rebooted to twrp and delete /data/system/locksreen.db after that I was able to unlock device, however I can't setup FP after that, it just asks to put finger to scanner but never recognizes it.
[OnePlus 3 & 3T Cross Device Development] simmeone:
Same here!
[OnePlus 3 & 3T Cross Device Development] helderfp:
Had you tried clean flash?