yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Anyone facing issue with receiving WhatsApp calls? I read about an issue where screen remains off and no sound when receiving WhatsApp calls. Not sure if it is happening with all devices
[OnePlus 3 & 3T Cross Device Development] ashokmor007:
Can anyone confirm volte services works or not because its not working for me
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Maybe I failed to explain myself, I just wrote about my experience about realizing that LOS can (officially) be upgraded to a major version just like the Android ROMs shipped with the devices and, since I understand the value of a clean upgrade versus a dirty upgrade in such scenario and in a broader way too (I've been working in IT as a systems engineer since a few decades), I just asked why upgrading LOS this way seems to be riskier.

What I get from your answer is that it's risky in every scenario and with every ROM. Since I accepted the risk, I also know that, at the fist "just me" weird issue, a clean install will probably be the way to go and I will have to spend the few hours that I saved with the dirty flash upgrade, possibly without wasting other people's valuable time.

At the moment I'm running on 20190306 build and I will probably flash the next one when the AudioFX bug will be fixed (you have my full sympathy for all the times you've had to repeat how to workaround the issue, by the way), I suppose that flashing more often will just increase my chance of facing issues and wearing my device. By the way, my dirty flash upgrade to LOS 16 fixed a "just me" nasty issue I had on LOS 15.1 (https://xdaforums.com/showpost.php?p=78550475&postcount=4239).
[OnePlus 3 & 3T Cross Device Development] raphael.e:
I flashed 16.03 on top of nightly 15.03 and reverted to 15.03 after Bluetooth keeps crashing. Same experience with 17.03 hence back on 15.03

Basically immediately after repoot Bluetooth keeps crashing ans wifi won't work. Even headphones were switched off.

Please find attached the bug report. Any idea? What else should I check?

https://drive.google.com/folderview?id=1tMDcwiQq-j__LgUVEHG9Jd3LW7yi4igt

https://xdaforums.com/attachment.php?attachmentid=4725846&stc=1&d=1552848417
[OnePlus 3 & 3T Cross Device Development] :
Many of you words contradicting themself, what is exactly your reason here?

-You understand the value of clean upgrade yet you influence people by showing off your success story with dirty upgrade.

-You said clean flash will spend hours, a frequent flash will cause issues and weared off the device, yet you're proud of being an "IT System Engineer"

All i see is you're just trying to show off yourself. Congrulations, you just do the opposite.

So yeah, stop it before you do more damage. I'm sure you're a kind of person who really value about how others percieve about you.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
The OTA updater downloaded a file called "lineage-16.0-20190317-nightly-oneplus3-signed.zip".

I would say it's the right file. Its sha256 sum is b666c49a91eceb0dea8792a86f4e7ad298e900cbc78d7dfd78a4ef8989906006 .

That corresponds to what is shown here.

I would conclude the file is the right one.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No WhatsApp issue with the current build on my side.

Same behaviour (sound and screen) on LOS 16.0 (OnePlus 3T) and on Arrow OS 9.0 (Moto G4 Plus) with receiving WhatsApp calls.
[OnePlus 3 & 3T Cross Device Development] :
What do you mean by "bluetooth keeps crashing"? In an other posting it's "bluetooth stops"? Any message? Is the service switched off? Which devices/functions do we talk of I guess audio on bt headset? Which device exactly? What is "headphones switched off"? Do you mean the headset is hardwarewise in off state? What do you mean with wifi won't work? You can't switch it on? Or ist's on, but no aps could be seen? Is this always, or only after the bluetooth issue. What about the log? Basically just answer the question from my previous posting.

Details, details, details...

---------- Post added at 17:05 ---------- Previous post was at 16:59 ----------

If you want to help us on the failing automatic flash issue, please read the anaysis: it's not the download, what ismfailing, but the files needed to be created for twrp automatic flashing, if userdata is encrypted. This generation is blocked for some users by selinux.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
This is the right file!
[OnePlus 3 & 3T Cross Device Development] uttam.ace:
hey can I install over latest OOS without loosing internal storage. Or do I need to format that also .
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
While the raging debate on which ROM is better will continue for long, it is better to go with a ROM that meets your requirements. The Stock ROM is a better option for users who love security and warranty while the Custom ROM is a perfect fit for users who prefer customization and control.

And for you ?

A good read: https://dazeinfo.com/2017/04/10/android-stock-rom-custom-rom/

---------- Post added at 17:35 ---------- Previous post was at 17:27 ----------

You wish to update your firmware to OOS 5.0.8 ... Right?
[OnePlus 3 & 3T Cross Device Development] raphael.e:
Hi, I have attached a Screenshot also in my previous post. Is it sufficient or shall I try to add something else?

Yes Bluetooth hardware is switched off and Bluetooth setting on the phone is crashing as per the Screenshot. I have flashed the full zip 16.03 through the lineageos manager and today 17.03 manually through twrp. With both builds the issue occurs.

Thanks for your support and advice! Raphael
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=5251661]raphael.e[/MENTION]

After performing a nandroid backup (via TWRP), could you try a clean installation?

- Full wipe (cache/Dalvik/system/data)

- Flash only the last build

- Reboot system and check BT issue

---------- Post added at 18:47 ---------- Previous post was at 18:39 ----------

In the next build:

Revert "effects: fix volume burst on pause/resume with AudioFX"

* The original patch kills entire audio output on certain cases.

==> https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/241802
[OnePlus 3 & 3T Cross Device Development] :
The thumb shows the broken pic symbol. The link doesn't open.

Anyway, I give up. I'm just too tired of begging for information amd logs.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
[LOS 16, 20190317] Weird dot in status bar

[IMG="Dot in the task bar"]https://imgur.com/xy6tVlF[/IMG]

I've been suggested that there were too many icons. I think there's plenty of room for a few extra ones.

Any idea on what's that dot on the left of the WiFi?

I've never seen such a think on the same device running v15.1.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's like an overflow indicator: too many icons to show in the available space. I'm guessing it's got to do with supporting notches.

You could try putting the clock on the left hand side of the status bar, not displaying network traffic (or hiding it if no traffic), or just get used to it.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I'd say that there's plenty of room, isn't it?

Moving the clock on the left seems to work. I don't see more room in the bar, though.

Instead I see some extra blank room between the network traffic and the alarm clock icon.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
What's the point of being so rude and un-polite? Was I? Why going personal?

Anyway, my evil agenda does not include starting a flame war on XDA and going off-topic.

So please just allow me this last message where I can thank you for your free psychiatric help, apologize for anything that might have hurt anybody and please, before it's too late, a final statement about dirty flashing: easily influenced guys out there (if any), "don't try this at home".
[OnePlus 3 & 3T Cross Device Development] Uqbar:
A "dirty upgrade" is the documented way to go from 15.1 to 16.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
This traffic indicator in the middle of the status bar is very ugly, it appears to be clearly a bug.

But it is not... since the option of clock in the center was removed perhaps in favor of it so that they do not enter in conflict (as in the beta builds, I think I remember something like this).

Is there any chance of this being improved?
[OnePlus 3 & 3T Cross Device Development] Uqbar:
The available room can be enough for another 3 or 4 icons (in my case) along with network monitor. Wasting it makes no sense. But I understand that the "notch craze" have lead to the bar split...

Anyway I am with [MENTION=4745774]kryzeK[/MENTION]: that looks more like a bug.

Which I cannot file at the moment as there is no previous version where it was working.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/241802

https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/243651/2

With a bit of luck the AudioFX bug (spotify (and possible other audioplayers?) not working via bluetooth / aux etc.) will be fixed in todays build.
[OnePlus 3 & 3T Cross Device Development] :
The center option for the clock is only visible, if traffic indicator is disabled. If the clock is centered, the traffic indicator settings are grayed out. This makes perfectly sense to me.

---------- Post added at 10:21 ---------- Previous post was at 10:03 ----------

I think we have this changes in the aosp sources because of g's "notch craze" (in my very personal taste notches are one of the worst inventions g has brought to us - and from my personal preference is much worse then a bug, considering that bugs arn't implemented intentionally), too. Also: if it's a bug, we would have chances to get it fixed, but it is intentionally made thais way by g. So, sadly it's not a bug, but worse.

BTW: I've tried to go back to the notch free oreo code. It's so deep in systemui, that it wouod break merging further upstream update merges (i.e. autotranslation and security updates).

In the end yiu need to g to change it back... :(
[OnePlus 3 & 3T Cross Device Development] Uqbar:
In the end I'd like LOS dev team to keep doing what they have been doing in the past 10+ years:

making Android work better

.

The point is that the network monitor has been hard coded to stay in the center of an unnotched status bar: 3T has no notch.

IMHO, if there's not enough room for icons on either half of the bar, they'd be allowed to "overflow" on the other one.

Hard coded stuff is one of those things CM/LOS has been fighting against since their early days.

I'll keep LOS as I can live with that dot, though, as minor visual glitches are nothing when compared to the uncountable benefits.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Posted yesterday... https://xdaforums.com/showpost.php?p=79139464&postcount=1278
[OnePlus 3 & 3T Cross Device Development] :
I got your point the first time, too.

My points are:

Reality proofs that dirty flashing breaks things:

If users dirty flashing from 14.1 to 15.1 and dirty flashing from 15.1 to 16.0 have expirienced a crashing snap (with builds prior to 0305), but users that has done - at least - one clean flash instead doesn't have suffered from this.

It's exactly that attitude, that consumes quit some of my time:

I'm doing public custom los builds since cm-11 on galaxy tab s. When I sum up the time I needed to hunt phantom issues in the logs that were finally solved by a clean flash it's around 300h (60 times, ~3h each begging for logs and information and searching the logs, 2h to argue against "but xyz says clean flashing and factory resets are placebo"; "but on abc def reports it's working"; or one of my favorites "I've never need to do this before). This is not about the time you spend on your own installation... :(

I'm explicitly honoring your point of view:

Though you've never expirienced the need of a clean flash, nor ever heard/read of someone else needed a clean flash, concluding that a clean flash is never needed is no only tough, but also not matching reality.

EDIT:

Perhaps we can agree on: get a nandroid, dirty flash - if issues show up, clean flash.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Reality proves that

if you don't have stuff like magisk

, you follow the guide and [MENTION=5091734]dianlujitao[/MENTION]'s thread 1st post and it simply works as advertised.

I did it and it worked. Here it is how:

1. Download [MENTION=5091734]dianlujitao[/MENTION] version of TWRP and install it.

2. Download latest firmware and install it if needed.

3. Download LOS v16, opengapps v9 and addonsu v16 (if needed).

4. Wipe caches and system.

5. install rom+opengapps+addonsu (if needed)

6. reboot to system.

Your apps with their configurations are still there. Maybe some can complain about the OS being too new. You need to check.

I am not a guru, I just follow directions and merge some details from the maintainer, if any.

That's it. No need to fight.
[OnePlus 3 & 3T Cross Device Development] :
...but my example I'm reffering to doesn't involve magisk...:confused:

Can we agree on: get a nandroid, dirty flash - if issues show up: clean flash.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I wasn't mentioning magisk because you did (in fact you didn't).

It's been more for the general public.

In general, I agree with you: follow the directions from both the LOS dev team and the maintainer posts.

In case I get troubles, I usually take the decision for a complete wipe (I call it "wipe the universe").

I mean, I wipe any single partition and then reinstall TWRP, firmware, ROM and GApps (I don't need root).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
SU or not SU, if issues show up: clean flash.... It is obvious... The discussion is over!
[OnePlus 3 & 3T Cross Device Development] Opsdri:
I think audio fx is fixed in the latest build. Thanks to the dev. :)
[OnePlus 3 & 3T Cross Device Development] ABOURAIHANA:
Confirmed ? AUDIOFX issue fixed. Thanks LOS
[OnePlus 3 & 3T Cross Device Development] dbsoundz:
Hello world,

sorry for asking, but I'm confused while reading all the stuff about "format system with TWRP 3.2.3.0 on 15.1 before update to 16". My OTA doesn't work and I read it's a problem with TWRP and formatting. What do I have to do to fix that? Can I flash TWRP 3.2.3.10 and all is fine? No as far as I understand. Would be nice if someone could unscramble my data in the brain ;)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
First, please read this post: https://xdaforums.com/showpost.php?p=79104174&postcount=1179

Second, this post: https://www.lineageos.org/Changelog-22/
[OnePlus 3 & 3T Cross Device Development] dbsoundz:
Thanks a lot [MENTION=9708417]Eric_Lev[/MENTION],

So I need to install oos with my currently used TWRP 3.2.3-0?

-> my data + apps will be kept as I understand?

then encryption footer is back again

next install TWRP 3.2.3-10 and install regularly lineageos 16 with format system

-> now all should be fine and my data + apps are as before this procedure?

another question: my encryption isn't broken or? I still have to enter my encryption PIN on boot. Only Updater has a problem because of missing encrpytion footer? What is this encryption footer else good for while encryption is still fine?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For me, it's bedtime .... First, backup your personal data and your app (e.g. nandroid backup, Migrate - https://xdaforums.com/and...-tool-t3862763, …etc).

Good flash!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Your brain data is way scrambled. First, it sounds like you are Encrypted so there's nothing wrong with your Encryption Footer. (There would only have been a problem with it in the first place if you had ever Formatted using 3.2.3-1.)

You are on 15.1 by the sounds of it? LOS officially state the update can be down by Format /System before flashing ROM/Gapps. No /Data wipe needed. Most of us agree it's better to do a clean install though. No harm in trying the former, and if it doesn't work out do the latter.

Your first step should be updating TWRP to 3.2.3-10 and then do the above. Do backups before beginning and Nandroid your existing setup.
[OnePlus 3 & 3T Cross Device Development] xowzinho:
To expand on this:

I tried flashing the 18032019 build and with the same result:

Bluetooth, wi-fi and mobile don't work.

If I try to open or use any of them, they force close.

Had to go back, again, to the 15032019 build.

Is there anything else I can provide on helping finding the root of the problem?

How do I log this issue to post here?

Thanks!
[OnePlus 3 & 3T Cross Device Development] Dirk:
Are you on 5.0.8 Firmware? If no, flash it. If yes, flash it again and then try dirty flashing latest ROM build again.

Nandroid your working setup before doing anything. If doing the above doesn't help you need to clean flash the latest build. If that doesn't fix the problem you can take logs to help the OP and then restore your Nandroid. If you do clean flash, make sure you test everything before installing any Mods.

To get logs:

Enable USB Debugging on your phone.

Connect to PC.

Open ADB/Platform Tools folder.

Open Command Prompt. (Easiest way is to type CMD in the Address Bar)

Type 'adb devices'

Type 'adb logcat - logcat.txt.'

There will now be a logcat.txt in Platform Tools.
[OnePlus 3 & 3T Cross Device Development] jodel51:
Thanks for this rom, its working great so far. I have one issue: No battery usage data is shown. What Im talking about is the list at the end of the battery settings page that shows how much battery each app has used. Is that a known issue?
[OnePlus 3 & 3T Cross Device Development] Dirk:
It's there, just changed position. Open Settings/Battery/Overflow Menu (3 Dots)/Battery Usage
[OnePlus 3 & 3T Cross Device Development] raphael.e:
Are you using magisk? I am on the unofficial magisk builds from ianmacd and explored a bit by disabling all my audiomods like AML, sauron etc now Bluetooth is not crashing anymore and wifi is also working fine again with lineageos 18.03 nightly.

Not sure yet which module(s) exactly causing the conflicts.

Edit: I uninstalled now all audio mods from [MENTION=6037748]Zackptg5[/MENTION] in magisk and reinstalled them followed by AML at the end and rebooted. Bluetooth is not crashing anymore on 18.03 nightly :)
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
Flashed the 3/18 build and it kept rebooting to recovery. Flashed 3/17 and everything was fine. Anyone else get this?
[OnePlus 3 & 3T Cross Device Development] Stier16:
Not for me. It is working fine. Haven't had any of the critical issues which are discussed here since moving to the official build.

I did a clean install from unofficial build.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=6153294]xowzinho[/MENTION] and [MENTION=5251661]raphael.e[/MENTION]

The official LOS SU may also be a good alternative.

==> https://download.lineageos.org/extras
[OnePlus 3 & 3T Cross Device Development] dbsoundz:
I'm now on lineageos 16. I formatted system with 3.2.3-0 (NOT 3.2.3-1 !) before lineageos 16 update.

Encryption seems to work because I have to enter my PIN on boot, when going to recovery AND all my data is there. If the footer is gone my encrypted data should be unusable, correct?

Only problem is: I can't update with updater because TWRP boots to recovery (no encryption key required) but nothing happens there.

OK, update to 3.2.3-10. But oos should be unnecessary?!
[OnePlus 3 & 3T Cross Device Development] :
Please see my log analysis and suggested fix on failed automatic flashing: the issue is not twrp, but when the rom prepares the files for flashing (block.map and uncrypt_file) this is blocked on some setups by sepolicy. Flashing files, which just doesn't exist, can't be flashed, no matter of twrp version.
[OnePlus 3 & 3T Cross Device Development] alevy3457:
The music now plays with Spotify but the sound level is too low. When I listen in Shuttle player the loudness is normal. Does anyone have the same problem?
[OnePlus 3 & 3T Cross Device Development] :
The OP clearly states, that mods arn't supported in this thread. I would expect all users using this thread for help would uninstall all mods and reproduce the issue before reporting.

Your directions are surely usefull for users not honoring OP! Thanx for heads up!
[OnePlus 3 & 3T Cross Device Development] xowzinho:
This is probably it! I'll try it today when I get home. Thanks!
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Yes, but if the official directions and maintainer's ones says you don't need, then either it's a bug or something unofficial is lurking there.

In the former case we'd need to push for logcats and stuff.

In the latter we'd need to follow the OP rules: uninstall unofficial and unsupported stuff first.

Directions work if you follow them!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Constructive, we must be, so let's avoid tilting at windmills.... Please!
[OnePlus 3 & 3T Cross Device Development] Imnoa:
FLashed the latest OOS firmware already ?
[OnePlus 3 & 3T Cross Device Development] :
Is it working on oos? I'm on vodafone.de. Though my data plan is including volte it's NOT working on oos and therefor not working on los, either. I guess it's similar with 4G.
[OnePlus 3 & 3T Cross Device Development] JeffRijsJeff:
Well i have found the issue. Try to put the Sim in the other Sim slot. Than LTE+ (4G+) works
[OnePlus 3 & 3T Cross Device Development] alevy3457:
I found out that bass/visualiser functions are the culprit. When set to 0% the sound level is how it is supposed to be. When they are in use the volume goes down but only in Spotify, in Shuttle it works normally.
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
I have low volume on mx player with head phones. I will try your work around later.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Does the above still apply, or the bugfixes have made it to the official build by now?

Those who have switched from OOS to LOS16, is there any noticeable difference in battery life compared to OOS?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=5091734]dianlujitao[/MENTION] only knows!

New offmode charging animation is not yet pushed in official build.

Better with LOS on my side.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
New post: https://xdaforums.com/showpost.php?p=79159967&postcount=1342
[OnePlus 3 & 3T Cross Device Development] gon250:
Hey guys,

Its the first time I'm installing something in mi OP3t and I'm having some problems I dont know how to solve.

I'm following the steps of the official website to be more specific setting the adb and fastboot. wiki.lineageos.org/adb_fastboot_guide.html

The adb configuration is working properly but when I execute the command fastboot devices doesnt appear. Any idea how to solve this? thanks.

Note: Windows 10
[OnePlus 3 & 3T Cross Device Development] :
For fastboot the device must be in fastboot mode: power off and press vol up + power, or use the extended reboot menu.
[OnePlus 3 & 3T Cross Device Development] gon250:
I still getting the empty result in the console :(

Also when I am in fastboot mode the command adb devices doesnt find the phone.

In the device manager appears under Universal Serial Bus Devices > Android
[OnePlus 3 & 3T Cross Device Development] :
Remote OS? What does it show if you boot in fastboot mode and connect the device to the usb slot? For win mostprobably drivers, for darwin and linux it should work out of the box, otherwise errors should show up in dmesg.
[OnePlus 3 & 3T Cross Device Development] :
This is a general question though, put it on q/a section with much detailed of what you've done rather than just giving a link.. for god sake, i spend 10 seconds on that page and my mind was already blowned..........

Nobody have time guessing what you've done except [MENTION=4405529]nvertigo67[/MENTION] :p
[OnePlus 3 & 3T Cross Device Development] An68:
Have you made cmd as admin ?