yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Disclaimer: I'm no official los device-maintainer. These are just my two pence on issue quality:

If I look at the first issue in the list: https://gitlab.com/LineageOS/issues/android/issues/891 and read the comments, I understand that no official device maintainernwill deal with. I also highly appriciate that no mental resources are spent on this issue!

Not updating the fw in favour of removing the fw requirement and complaining about hardware not working any longer is ignorant enough. But promoting the removal of the fw requirement as a fix to Error 7 is so far beyond any resonablity, that I've no words for...

BTW: this is not related to the ota issue we've discussed here in this thread lately.
[OnePlus 3 & 3T Cross Device Development] punio4:
Yea not all of them make sense. These should at least be closed.

I believe that my report for the night mode acting wonky compared to other ROMs has some merit to it.

My point is, why even have a public issue tracker if you're not gonna read the issues? How else does the LOS team expect to get bug reports? XDA is definitely not the right platform.

How it seems from my end is that the maintainers only act on issues that they themselves notice.
[OnePlus 3 & 3T Cross Device Development] :
I'm with you - the tracker needs some love. The rubish should be wiped out, the reasonable ones should be acknowledged. I just want to promote understanding a voluntary dev's time is limited and he has to decide how to spend it...

[MENTION=9350973]All[/MENTION]: I've read many times (not only in this thread), that people want to help with roms, but don't do it because they are no devs. I'm pretty sure the los team (or any others rom's dev team, for that matter) would happiöy accept help in pre-sorting issues, improving documentation and many other things. This is your chance to pay back to tje community!

One personal note: If you look at my problems getting logs for i.e. the current ota update issues (ask 4 times ober a period of 5 weeks with no results, so far), you'll understand it's much more fun, less timely effort and much more straight forward to debug and fix an issue I'm expirience myself...

As matter of fact: there is more demand for resources then resources.
[OnePlus 3 & 3T Cross Device Development] felagund:
Slight offtopic but

By rule of thumb I try to go through at least the 10 most recent pages before a major action like upgrade from Android 8 to 9, etc. so I can see if there are major worries like the OTA bug, firmware problems, etc.

Fiddling with custom ROMs is dangerous for your data unless you know very well what you are doing and even then you can make a mistake.

Back in the old days there were also dangers to lose efs partition and to need to restore or generate IMEI for example which was a bit of a hassle as the tools would be removed from XDA for complianceand if you don't read you risk your phone.
[OnePlus 3 & 3T Cross Device Development] punio4:
Ideally the first post should be updated and the poll removed.
[OnePlus 3 & 3T Cross Device Development] sky321:
OTA

So, finaly I updated my op3 and ran also in the OTA problem. suprise, suprise :)

my config is twrp 3.3.1, FW9.0.4 from [MENTION=4405529]nvertigo67[/MENTION], open BL

No problem, I now how to help my self on this rescue party. Just want to bring some things together in this topic.

Using SU could help as I read. I didn‘t use root but if I get it right it might be helpful.

Not shure if this is the reason one need SU but interesting to explore.

——— wrong qoute deleted——

My solution on this rescue party was that I wiped system and flashed Los16 and gapps again.
[OnePlus 3 & 3T Cross Device Development] :
What [MENTION=9708417]Eric_Lev[/MENTION] has descrined is somethimg completely different and has been fixed months ago. What you've "solved" is something different introduced weeks later. Please, look through the thread, I'm still waiting for a simple test and a logcat (depending on the test). Mixing these two different issues is very confusing.
[OnePlus 3 & 3T Cross Device Development] sky321:
Sorry, for been unclear. My solution was not meant for f2fs problem. Good to know that it is solved.
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
I have a issue I which if I switch on Hotspot, the network meter on the status bar gets stuck on 0/0 UL/DL. Just a minor bug.
[OnePlus 3 & 3T Cross Device Development] Fritzy62:
I'm still traveling. Back home next week Friday (9th of August) and that's when we'll do the steps you described to create the logs.
[OnePlus 3 & 3T Cross Device Development] chaosjug:
I have a OnePlus 3T with LOS 15.1, unencrypted data and unlocked bootloader.

I'm reading through this thread to 1. find out what the recommended setup is at the moment, and 2. how to get there.

From my understanding, this is what is recommended:

current twrp

current OOS fw

current LOS 16.0

locked bootloader --> is this really the case? I use custom roms since many years and and this was never recommended (but desired of course)

I tried to find out how to update but everybody talks about encrypted data which I don't have.

My strategy would be:

backup everything (especially sdcard)

update twrp

reboot to twrp

wipe everything except data

install oxygenos-9.0.4-firmware-3T.zip

install LOS + su

reboot

lock bootloader

encrypt data

My understanding is: as data is not encrypted i should not loose data.

Does it matter if I lock the bootloader before encrypting, or should I do it the other way round?

Is there anything I need to do before locking the bootloader?
[OnePlus 3 & 3T Cross Device Development] :
My experience; do not lock your bootloader and do not encrypt data, use EXT4 for all drives and you can switch, upgrade and do what you want without any issues.

Although encrypted data is safer when loosing your phone ofcourse....
[OnePlus 3 & 3T Cross Device Development] legendavey:
You're right about the last part. Using a phone unencrypted with an unlocked bootloader is never a good idea.

Clean flash LOS + GApps, lock bootloader, format data, reboot and set up and then encrypt again. Manually downloading the update (there are free apps that do it for you) and flashing once a week is a reasonable price to pay for peace of mind, imo.
[OnePlus 3 & 3T Cross Device Development] chaosjug:
Why can't I use the updater? Even if the automatic install does not work, downloading should, right?
[OnePlus 3 & 3T Cross Device Development] :
Because people are ignorant towards details, too lazy to write what they mean (saving three words seems more important, then precission and technical correctness), too much in a hurry to read and understand all postings regarding an issue or a combination of these...

You are right: currently broken is automatic flashing an ota update!

But people love claiming "Updater is broken" instead of "automatic flashing an ota update is broken".
[OnePlus 3 & 3T Cross Device Development] sky321:
OTA

Auto OTA update in twrp3.2.3-0 work without problems. Used the same LOS / FW / BL

With twrp3.3.1 following procedure fails.

1. download update

2. start logcat

3. update with OTA app

4. reboot

5. adb logcat lost

6. bootup normal

7. twrp normal

8. twrp updates -> OK

9. auto reboot

10. boot normal

11. decrypt with pattern

12 boot never comes to an end

at step 6 & 7 I tried to start logcat again but it's not possible.

I'm not able to start adb logcat in twrp mode, sorry

in the attempt twrp log is witten

"/sbin/sh: logcat: not found"
[OnePlus 3 & 3T Cross Device Development] :
Great finding! Thanx for testing! That means it's not the Updater app (or missing permissions in the rom) this time, but twrp.

The least annoying recovery seems to be 3.2.3-10 for now... Hopefully this commits will fix it:

https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34338/
[OnePlus 3 & 3T Cross Device Development] Shashank H:
Signal strength of sim1 is very low as compared to other roms i have cleaned flashed the ROM, last rom used was Havoc os
[OnePlus 3 & 3T Cross Device Development] :
I don't know about havoc, but if you compare los to oos regarding signal strength, you'll find something funny: if you look at the bars in the status bar, you'll find the signal strength on oos is better. If you look at the dbm value for the signal they are absolut identical (in the same comdition/location, of course). Maybe the icon differences of los and havoc are the same.
[OnePlus 3 & 3T Cross Device Development] Niob24:
Dear all,

i recently encountered a problem with Lineage 16.

The problem is, that irregular the system is freezing. More precisely it is not freezing but stops to refresh the screen(picture).

For example: I unlock my phone and try to swipe up to see my appdrawer. But nothing happens. Screen stays at my homescreen. But when i touch my screen, an app from my drawer opens (its like the screen does not refresh, but the system does what i tell it to do in the background). I don't encounter the problem in every app (for the moment i had the problem with trebuchet, spotify, boost for reddit). I never had it with chrome i use quite regular.

Another strange part is, that i can swipe down statusbar when i encounter the problem and can see and interact with it. But when i close statusbar the appdrawer for example still does not work. I have to open an app to fix it. Same with spotify, to fix the problem i have to blindly scroll and select another song to get the screen to refresh again.

I first encountered the problem with NLOS 16 (clean flash). So i changed to Lineage 16 (again i performed a clean flash) but it happened again (I updated Lineage a few time till the beginning. Still same problem)

My setup right now: Lineage 16 (20190728), opengapps nano, stock kernel, twrp 3.3.1-0, firmware 9.0.4 with bootloader an keymaster 5.0.8, data: f2fs, system: ext4

Now I don't know to proceed next? I tried to perform a logcat with MatLog. Started it and left it recording till after i encountered the problem again. I hope it is useful.

If anyone has an idea what causes the problem I would appreciate any help.

Thank you in advance for your help!
[OnePlus 3 & 3T Cross Device Development] Shashank H:
Sometimes the bar gets too low as zero and it changes very frequently , should i flash the oos 9.0.4 firmware and then flash lineages os again?
[OnePlus 3 & 3T Cross Device Development] :
No. You should compare the actual signal values instead of the icon across different roms. oos shows more bars in the icon on the same signal strength value. To compare the signal strength across different roms, you can't rely on the icon but you need to compare the signal strength dbm values (Settings->About phone->SIM status (sim slot 2)->Signal strength).

---------- Post added at 19:25 ---------- Previous post was at 19:17 ----------

The log is not from a clean flash! I suggest you clean flash (rom+happs; no additional restores or installs) and reproduce the issue. If the issue doesn't show up anymore, you can install/restore your apps/mods one by one to identify the missbehaving app(s).

If the issue shows up on a clean flash again, get the log and dmesg with adb. It's helpfull to increase the log buffer to 4 Mio in devopts as soon as the first time setup is completed.
[OnePlus 3 & 3T Cross Device Development] Shashank H:
When on full brightness the blacks near those area gets whitish (you may not able to see it if you are using different ROM) I'm using standard profile for colour configuration

Also after lowering the brightness it remains like that

*Ignore this image watch it below the post*
[OnePlus 3 & 3T Cross Device Development] Shashank H:
Here
[OnePlus 3 & 3T Cross Device Development] anavarro8794:
It mattered to me when I used this build. I have updated since then and now it does not. thank you
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
Are there people have freeze (notification led white and phone totally blocked with screen off) with efficiency battery profile ? Every time I use it, after a random time (between 10min to 2h) i have this. Only solution is to force reboot with power button.

No problem with "balanced". (I don't use others profiles)

Firmware 9.0.4 + clean install build lineage-16.0-20190803 + magisk + encrypted data + lock bootloader
[OnePlus 3 & 3T Cross Device Development] Shashank H:
Cannot hear audio with headphones on in the Poweramp app
[OnePlus 3 & 3T Cross Device Development] k1chy:
Use the work around suggested in previous posts. One quoted below for easy reference.
[OnePlus 3 & 3T Cross Device Development] op3fo:
Phone Dialer App freeze and crash

I need some help, I tried different things, but can't solve my problem: Everytime I call any number, the dialer app freezes and after about 30s until 60s the phone first freezes completely and than reboots. I did tried two different SIM and both SIM slots.

I was using CM13 before and since a few weeks my phone had already some issues. The internal headphone and the microphone didn't work properly. After a reboot both worked for some time again. I'm thinking this is a software issue, because after a reboot it works again and I'm not sure but thinking the problems started after I did some experiments with Xposed. So I tried to do a fresh start with LOS16.

This Monday I first tried to upgrade to LOS 16. Because of the old firmware I cant install LOS16 (At this in first place I tried to use "lineage-16.0-20190730-microG-oneplus3.zip"). After some fast searching I found the advice too disable the checking of firmware version (https://************/status-7-error-on-android/) and could sideload the image. But I got the explained problem. After reading about the new firmware I tried to sideload the original OS 16 OTA. Same Problem and it ended in a bootloop. Now I did hard format all storage and did sideload original LOS16. Same problem. Last I flashed this firmware (https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164) and sideloaded LOS16 again.

Now my setup is:

twrp-3.3.1-0

lineage-16.0-20190807-nightly

open_gapps-arm64-9.0-pico-20190806

addonsu-16.0-arm64

Does someone have any ideas what I could do?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
What I would do:

1. Install latest TWRP: LINK

2. Reboot to TWRP

3. Install latest stable Firmware v9.0.5 (be SURE to pick the right one - there are variants for OnePlus 3T and OnePlus 3!!!): LINK

4. Reboot to TWRP

5. Format Data as ext4

6. Reboot to TWRP

7. Wipe everything (everything except USB)

8. Install LineageOS: LINK

9. Install OpenGApps (the right package is preselected for you!): LINK

10. Install the SU arm64 addon (root): LINK

11. Wipe Dalvik & Cache

12. Reboot system
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Go to settings > apps > advanced settings > default apps > choose dialer as the default phone app. Even if it's already set as default

(kind of like this: https://www.youtube.com/watch?v=BXg7k75sVc8 )
[OnePlus 3 & 3T Cross Device Development] knpk13:
So the problem is with the gapps package? I got an FC from Android setup as well when I installed Pie and tried to go through the setup wizard, but everything after that seems to work. Is the gapps (play store notification) bug simply cosmetic or are there any functional bugs as well?

Also what does disabling that package you specified do (and the other package you warned us not to disable as well)? I just switched to Pie and I'm trying to get everything set up.
[OnePlus 3 & 3T Cross Device Development] ele95:
hahahahaahahha NOT FUNNY
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
I haven't tried LOS16 yet as I'm waiting for it to mature a bit more. Plus I just switched to 15.1 and don't want to set everything up again.

I would need to see a log with that crash to hopefully figure the issue and get a fix to OpenGApps. But that's if it's confirmed to be on the OpenGApps side.

As for the packages:

"com.google.android.SetupWizard" is the setup part one goes through to sign into their Google account and such.

"com.google.android.apps.restore" is to restore data after a factory reset, during setup.

As for disabling SetupWizard, I'm not sure what would happen if someone disables it after setup.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Works fine for me. And I also don't have problems with Play Store downloads.

Fyi, I use Delta gapps from here https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368/post58047099
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
I would like to first trying to debug myself, but where is the build log？ My best guess would be build.trace but that file is just a json file without concrete error message I could see...

Thanks in advance!

ADDED:

BTW What I found in web was that the error seems platform dependent. It had a higher chance to be seen on AMD CPU. I compiled the build in a Phenom II X4 B40 with mentioned error. I am now compiling in a Virtual Box with i5-4460 and progress is over 96% (i.e. already passed the progress as in AMD CPU). As I could compile Oreo in AMD CPU, I guess there should be a fix for mentioned error.
[OnePlus 3 & 3T Cross Device Development] realtos:
sorry but buttin in on this convo but just a quick question. theres bootanimation avail for our device from 6t maclaren and say rename zip to bootanimationand move to system media but theres no folders in system here and got magisk runnin and see all folders in root but media i cant find. please help. would be cool to use that boot
[OnePlus 3 & 3T Cross Device Development] :
The build log is, where you put it. i.e.:

brunch oneplus3 2>&1 | tee make.log

The line beginning with FAILED Is just the complete command line statement that failed, you can't see which command in this line is actually failing. Typically it's a few lines before (rare: after) the FAILED line beginning with "error:". It's always a good idea to save a build log, because you can search the file.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
If you link me the bootanimation, I can provide for a twrp flashable zip and (to be tested yet) a magisk module.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The folder is /system/media and it's there. I also have Magisk running, but that that's not important.

Where are you looking for the folder?
[OnePlus 3 & 3T Cross Device Development] realtos:
https://androidfilehost.com/?fid=11410963190603875320

in trwp, i see system but theres no folders or anything

---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------

https://androidfilehost.com/?fid=11410963190603875320

https://androidfilehost.com/?fid=11410963190603875320
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Here are a magisk and a flashable bootanimation using the OP6T McLaren bootanimation :cowboy:

https://drive.google.com/open?id=1g--ubtIsP14tBgurLZyirtYQfRydJ3Rr for the flashable file.

Reboot device in TWRP and flash the zip file. Wipe dalvik/cache and reboot.

It must be reflashed anytime you flash a ROM, as you may know.

https://drive.google.com/open?id=10nWBolYF5JOJ7S-W-KuA1yYWtHRQ6D0H for the magisk module.

BEWARE: it is a magisk module and it has not been tested yet. Take a backup before flashing the mod.

It has been created editing a Sony Xperia XZ2 bootanimation magisk module. Credits go to [MENTION=4916555]okij[/MENTION].

As far as I know the module is not working along with any Dolby Atmos / Dolby Digital mod, I assume due to config.sh to be fixed.

Any feedback is very appreciated. Feel free to use and develop both templates, I am just reposting someone's else job.

Thanks to [MENTION=9554680]realtos[/MENTION], who provided for the bootanimation file.

As usual, flash at your own risk. ;)
[OnePlus 3 & 3T Cross Device Development] knpk13:
When do you need me to take the log? While downloading an app from the play store? (And reenabling the SetupWizard app)

And what crash? I thought it was just a cosmetic issue.

Thanks for the information btw.

And just switched to Oreo? Why were you on an older version for so long? Oreo has been pretty stable and mature for a long time now I believe.

I forgot to mention I'm on NLOS 16 btw. But it has the same issue and it's based on LOS.
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
Take it when ever you see the FC. I'm referring to whatever "crash" this is as the FC.

On Pie, when installing OpenGApps on it, there's two apps named Android Setup, with different package names. You can see this in Settings > Apps > See all > Show system apps. One package name ends in ".SetupWizard" , the other ends in ".restore".

.SetupWizard is the first thing you see when you set up the phone.

.restore is called during .SetupWizard when it asks you if you want to restore data, and is also shown in Settings at the very top, in a suggestion box asking you to finish setting up your phone.

If you get the FC during setting up the phone, grab the log when you're able to. If you get it while trying to restore or finishing setting up the phone from the Settings suggestion box, get it.

As for ROM history, I've been on a custom Oreo ROM, just not LOS 15.1, until now.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Do as [MENTION=7009345]vivian&ondine[/MENTION] said, or use a file manager when your phone is booted (assuming you have root). My screenshot was from my file manager.
[OnePlus 3 & 3T Cross Device Development] NoobOellie:
I came from the OnePlus Beta build July 2018 (Open Beta 39). This LineageOS 16.0 works great for me. WLAN is more powerful and stable. Bluetooth works more stable. Twitch works more stable. YouTube works great. Internet works faster. Everythings feels smooth.

I can even do phone calls [emoji16].

Battery life did also increase.

I will check if the navigation apps still work fine.

I am very happy so far. Thanks for the great work!

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] uday aero:
Phone call sound is not routing to earphones when we receive or dial a number

Issue Description: When we have earphones inserted into jack and receive a phone call, not able to hear the sound through earphones but if we remove earphones then we are able to hear using ear piece

Same thing is happening when we do a call
[OnePlus 3 & 3T Cross Device Development] legendavey:
Damn, dunno how I missed this. It only happens on earphones with a built-in microphone. It goes into DND mode and disabled the microphone and there's no audio on the other end. Works fine on earphones without a built-in mic. Will try to capture logs when I'm home.
[OnePlus 3 & 3T Cross Device Development] legendavey:
I should also add that I'm using a pair of Mi Buds in-ear earphones to test the issue. It has a single button for call control and works fine with LOS 15.1 - this seems to be a LOS 16 issue for now.

Also this doesn't seem to be an issue on my daily-use wireless Sennheiser BT earphones (aptX) that work properly with all phone calls and media.

Here's a log, with only W and E messages. I can send a more complete log (all messages) to either [MENTION=5091734]dianlujitao[/MENTION] (or [MENTION=4405529]nvertigo67[/MENTION] or someone else) privately, if this log is not enough to help pinpoint the microphone issue. :o
[OnePlus 3 & 3T Cross Device Development] :
In this commit some mic stuff is added: https://review.lineageos.org/c/Line...lus3/+/232828/2/audio/audio_platform_info.xml

Perhaps something got lost when going LA.UM.7.5.r1-03100-8x96.0??? But honestly I don't really understand that commit... :(