yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Dirk:
Oh, so it does happen here? I'm surprised it isn't mentioned more. On some ROMs/Devices people are getting very frustrated. It's beginning to show in their posts. The lack of feedback from Devs doesn't help of course. Getting a bunch of Logs from random people is like herding cats, (especially on the OP5/T where the spirit of cooperation and will to hunt down the source of problems is sorely lacking), yet having done that no dev has even mentioned looking at the logs. Makes me wonder why i bothered.

I wonder if we'd have better luck here trying to get to the root of the issue. It's been around since Pie Day 1. Here are a couple of posts with Logs, including my own:

https://xdaforums.com/showpost.php?p=79134549&postcount=1341

https://xdaforums.com/showpost.php?p=79219741&postcount=1375

I seem to remember the Livedisplay entries seeming to coincide with the time the 'Phone is Starting' appeared, which made me consider a causal link.

[ 03-17 01:16:19.681 1361: 1412 W/ServiceManagement ]
Waited one second for vendor.lineage.livedisplay@2.0::IPictureAdjustment/default. Waiting another...

Anyone else getting the 'PIS' bug who has never mentioned it?

Edit: Yes...

:)

---------- Post added at 13:18 ---------- Previous post was at 13:00 ----------

That zip fix, btw. It worked 100% for months on my OP5. Not one reoccurence of the bug. The one time i forgot to flash it after a ROM update, i ran straight into the PIS message on the first boot.

Also, the erroneous attribution of Magisk as the cause. A lot of people use LOS. A lot of people use Magisk. Correlation does not equal causation. 'I was breathing and then it started to rain. So breathing causes rain'. Nope, try again. :D
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=1763460]Dirk[/MENTION], Do you know more about this fix?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Oh that was a bug? I've encountered it several times before but I assumed it was my launcher (Nova Launcher) and rebooted, because I've never seen that on Android before.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
On LOS or NLOS ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
I extracted the zip and did some research on it's contents. Found some official Android dev pages that explained what the file was. Didn't help me understand anything even a little bit. :D

Take a look at the contents yourself. It's a list of stuff that means nothing to me.

I once explored the possibility of the Launcher being to blame. That was when i was still trying to find a common cause among all affected. (Again, everyone uses a Launcher, but correlation is not causation). The reason i liked it as a theory was because the PIS message and hang happens at the point when the Launcher Homescreen appears.

Another popular theory is that lockscreen security/fingerprint causes it, with some people reporting the issue resolved by removing security measures. There are PowerHal errors in the logs. I've seen one that always preceeded a Livedisplay error. Like the two were linked.

Of course it's all supposition. Saying 'i did this and it fixed it' is the same as saying 'i started whistling and the rain stopped'. Ergo, whistling will stop rain. You would have to test that theory over a long period of time to be certain.

It only happens to me when i flash something, but then i only reboot when i flash something, and it only happens after a reboot. Did the flashing cause it? The cache wipe? Probably just the reboot was enough.

This issue has defeated every attempt to explain it.
[OnePlus 3 & 3T Cross Device Development] :
At least we have the best prcondition here.

Deduction: Let's assume the two op3ts are hardware wise equally made and arn't broken in any way. If the hardware is equal, the difference has to be the software. Comparing each and every aspect of the the sofware setup, will - at least - lead us up to the trigger, if not to the cause...

[MENTION=9708417]Eric_Lev[/MENTION]: I know thats a pain in the arse - but it's consequential. I'm crossing fingers for your patience!

[MENTION=1763460]Dirk[/MENTION]: for what rom and device is the zip originally made for? To tell, how the zip fixes this, I need a base to compare it to (the differences in the /vendor/e4c/vintf/manifest.xml are quite massive to los' version). EDIT: I'll compare against the one in restore.

A word on frustration by unresponsive devs: though I completely understand the annoyence of users: show a heart for devs! It's - let's say - not very comfortable to admit to have no clue what's causing that, after looking through the requested logs. I know only very few devs doing this.

I've compared the two manifest versions:

colordiff -u /mnt/export/data/Downloads/incoming/manifest.xml /mnt/export/data/Downloads/incoming/manifest-fix.xml
--- /mnt/export/data/Downloads/incoming/manifest.xml 2019-03-29 18:55:00.000000000 +0100
+++ /mnt/export/data/Downloads/incoming/manifest-fix.xml 2019-03-29 18:56:00.000000000 +0100
@@ -469,6 +469,7 @@
</interface>
<fqname>@1.0::IDisplayPostproc/default</fqname>
</hal>
+ <!--
<hal format="hidl">
<name>vendor.lineage.livedisplay</name>
<transport>hwbinder</transport>
@@ -484,6 +485,7 @@
<fqname>@2.0::IDisplayModes/default</fqname>
<fqname>@2.0::IPictureAdjustment/default</fqname>
</hal>
+ -->
<hal format="hidl">
<name>vendor.lineage.power</name>
<transport>hwbinder</transport>

Is LiveDisplay still working after flashing these? including Display modes and Picture Adjustment? Or does this remove these two options from LD?
[OnePlus 3 & 3T Cross Device Development] Dirk:
The zip fix was posted on the OP5T forum. (I posted the link earlier). I've been using it my OP5. I did try finding the crDroid version of that Manifest.xml file to do a comparison myself but failed miserably.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
:D

I confirm the hardware is equal, the difference is probably the software.

On my side, the 'Phone is Starting' bug occurs hardly ever so it is not a real problem and, in addition, it is enough to restart to solve it.

About the dvs, it is well known that they do a dream job... :D
[OnePlus 3 & 3T Cross Device Development] :
Would you please check the settings for LiveDisplay->Picture Adjustment and LD->DisplayModes on both devices? (See above, I've added some findings)
[OnePlus 3 & 3T Cross Device Development] :
+1 for me the same on my OP 3T
[OnePlus 3 & 3T Cross Device Development] Dirk:
It's infrequent for me too, but then so are reboots. I've done a lot more flashing recently and consequently i'm suffering it more.

Some people were so badly hit that it takes them several reboots to get a working one. One guy couldn't get past the message, flashed the zip fix and Bingo, he was in.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
On both devices:

- Picture Adjustment (by default)

See below for Display Modes

Please note that my son often changes his phone settings.

Edit 1: We only flash if Changelog is not empty. As a result, an update almost daily and, as already mentioned, the "Phone is Starting" bug occurs hardly ever on both phones.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Do you use the s-RGB colour profile ? ... Because since I'm back in default colour profile (Standard), I feel the "Phone is starting" bug has disappeared... To be confirmed.
[OnePlus 3 & 3T Cross Device Development] :
I'm using s-RGB colour profile too ...
[OnePlus 3 & 3T Cross Device Development] Dirk:
I've only ever used 'Standard'.

You can see how this bug has a habit of leading you down a primrose path? The biggest issue diagnostically is how infrequent and random it is. Very hard to pin down.

Also this might have nothing to do with Livedisplay. It's just the theory-of-the-week.

Can open, worms everywhere. And don't get me started on Pandora's Box!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I'm delirious.......... So I'm going back to Pandora to extract unobtainium.... :silly:
[OnePlus 3 & 3T Cross Device Development] Dirk:
:D

Take a look at this. The dev seems pretty convinced that removing Livedisplay fixes the PIS issue:

https://xdaforums.com/showpost.php?p=79614388&postcount=975

In the usual XDA tradition he doesn't explain any more than that. When did fixing problems become akin to state secrets? Is the attitude now 'i know something but i'm not telling you...'?

Anyway, he's not the first to think he's fixed it and will probably be proved wrong. Time will tell.
[OnePlus 3 & 3T Cross Device Development] :
...nobody would hand you Pandora's box - you doesn't look like Angelina... ;)

Welcome to my world the both of you. If you start feeling dizzy, I recommend another 2 Mbs of logcat... ;)

Back to business.

I'd like to find the code with the message. Since I've never expirienced this, can one of you give me the exact string, please?
[OnePlus 3 & 3T Cross Device Development] Dirk:
The message is literally 'Phone is Starting' with a progress graphic.
[OnePlus 3 & 3T Cross Device Development] cokesucker:
I have had this issue as well using any profile but Standard. Phone is starting message and the bootlogo color is in srgb or whatever mode.

The bombshell is that I'm on RR Pie! The plot thickens...
[OnePlus 3 & 3T Cross Device Development] Dirk:
All LOS/Based ROMs are afflicted. Only on Oneplus phones though. (Which should be diagnostically useful also). Never seen a report of it outside of that combination.

If the problem were Livedisplay i'm less inclined to believe that a particular mode is at fault, rather that the whole thing is broken. I seem to recall that LD was heavily reworked for Pie? Perhaps what we need are test builds with some other implementation. Start excising large chunks of the OS until we find the cancerous bit.
[OnePlus 3 & 3T Cross Device Development] cokesucker:
I have tried to recreate the issue just now to confirm, set SRGB and rebooted. The phone booted into safe mode this time. Set back to standard rebooted again and some of my settings are messed up like default launcher and default keyboard reset. Hope this helps.
[OnePlus 3 & 3T Cross Device Development] cokesucker:
Does it happen directly while finishing boot, or is it shown as soon you try to login. [MENTION=4405529]nvertigo67[/MENTION]

For me the RR bootlogo color is in SRGB mode, i don't think that's normal? Haven't seen that before.
[OnePlus 3 & 3T Cross Device Development] :
I've set Color profile to sRGB and rebooted: working like charme.

If this is related to LD, LD is a necessary condition, but not the sufficient condition. Our best chance is [MENTION=9708417]Eric_Lev[/MENTION] with equal devices, one suffering the other doesn't.
[OnePlus 3 & 3T Cross Device Development] cokesucker:
My phone is 3T if it makes any difference.

And I'm on latest beta firmware 9.02
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Have you enabled both of these in Play Store?

Notifications are working fine for me.
[OnePlus 3 & 3T Cross Device Development] :
Jio VoLTE is working fine but Airtel VoLTE is not working for me. Any solution?
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
I think this would be for the LineageOS team to solve. Do you know whether that's supported for other phones on official LOS16?
[OnePlus 3 & 3T Cross Device Development] legendavey:
Airtel VoLTE is broken on all Pie ROMs, other developers have tried adding Airtel's MCCs and MNCs but it does not work.

It looks like it will *not* work until Airtel works with our OEM to support VoLTE on Pie.

Luckily you can still make calls without VoLTE so waiting for it will not be an issue. ;)
[OnePlus 3 & 3T Cross Device Development] werxer:
That is a good question. Unfortunately I don't know and I don't have other phones to test.

I only know the opposite, that there are other ROMs for OP3 supporting it.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
I don't think this missing option is device-depending.

Some Lineage features (su, weather provider) are yet to be added.

https://github.com/LineageOS/android/blob/lineage-16.0/snippets/lineage.xml
[OnePlus 3 & 3T Cross Device Development] Viktorrr:
Will I have to make clean install (with wiping data/factory reset) again when los16 start officially if I install this unofficial los 16 now?
[OnePlus 3 & 3T Cross Device Development] :
Nice finding.

Though quite pointless, to fix it: most helpful - regarding the goal to get this fixed in los16 - would be a link to the gerrit or git commit, which fixed it on "other ROMs for OP3 supporting it", next useful would be a link to the actual postings about this lte issue in the "other ROMs for OP3 supporting it"-thread, usefull - but at least polite - would be a link to the "other ROMs for OP3 supporting it" threads.

Not even mentioning the names of "other ROMs for OP3 supporting it" is less than polite - and less than smart, if the goal is fixing this at soon as possible.
[OnePlus 3 & 3T Cross Device Development] lutherkingmartin:
Is this roms support encryption ? As far as i know, OP3 don't support it on Pie. But this is not in "know Bugs".
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Yes now most of the Pie ROMs support OOS based encryption. Now you don't need to do a format data if you're on OOS/Oreo in order to taste Pie ;)
[OnePlus 3 & 3T Cross Device Development] werxer:
I see a lot of passive aggressiveness there. I am sure you always get new users to be more helpful this way. Very polite (bitterness) indeed.

First, I was not talking about an LTE issue, it's about the traffic indicator in the status bar (upload/download).

Second, I don't know of any posts in other ROM threads talking about this. The ones I tested just had it working.

Third, these are the last two ROMs I tested and which had working traffic indicators:

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-skydragon-os-t3858177

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-aosip-pie-t3850374
[OnePlus 3 & 3T Cross Device Development] trentonite:
Just flashed and wanted to give my experiences thus far.

Quick note: Everything is working great after a few random things along the way.

1) At setting up the phone I received a number of FCs but was able to get through it all.

2) Once in the phone, it spammed me with a notification sound for about an hour while the phone was recovering apps from a backup. I assume this was some sort of play store notification but I couldn't find where it was coming from. What was even more weird was that the volume of the notification was independent from any setting. It was loud no matter what my ring/media/alarm slider was at. Once the backups restored I rebooted, got the sound once on reboot, and haven't heard it since.

3) Pixel launcher was an option when I hit the home screen button, but would FC every time I selected it. I assume this was part of gapps, probably flashed the wrong one (micro) when I should've pulled nano. Selected to always use the LOS and it's happy now

4) Notifications for Gmail and a few other apps aren't showing up when the phone screen is off. Of the screen is on they push immediately and I get a sound. With it off I never get a sound or notification until I launch the app. Only was able to find this out bc my old phone was on wifi and I heard the notifications going off. I suppose I can try waiting some time and see if maybe they're just delayed.

5) Phone notification that my sim card is HD sim capable. Can't figure out how to get rid of it.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Firstly, if you actually read through some of the pages here you would have realised [MENTION=4405529]nvertigo67[/MENTION] is nothing but helpful to new users and even contributes to LOS for the OP3/T. Best to keep that in mind before you make any insinuations.

Secondly, if you "don't know of any posts in other threads", you should probably use the search function before posting.

Thirdly, it is considered rude to compare other ROMs in the thread you are currently in. Those ROMs have forward ported those features from Oreo while LOS will take their time to enable them properly. If you urgently need those features, you are free to use those ROMs.
[OnePlus 3 & 3T Cross Device Development] werxer:
I am already using another ROM, I just came here to report that it is not working.

I think it's only natural to mention, that this isn't an unsolved problem in the OP3 ROM community.

It's only rude because you make it this way. I neither insulted anybody nor I demanded that it has to work in this ROM.

It's an interesting problem if you shouldn't compare ROMs but get demanded to name and link them or their fixes.

This problem isn't mentioned in the Sykdragon OS thread and in the AOSiP thread there is only a mentioning that it got added, without links to changelogs, commits or something like that. I don't think that is more helpful to link.

And don't worry, I won't give any more feedback here. Certainly I am not fit for it, reporting a bug and don't behave like expected for the first time doing it, by just mentioning that there are other ROMs, without even advertising them or demanding anything.
[OnePlus 3 & 3T Cross Device Development] :
My bad, I mixed that up, I thoight it relatws to the lte issue.

I wouldn't call that pasive aggressive, but for sure some frustration. Nonetheless, droping such a sentence without even mentioning zhe working roms IS frustrating for people trying to improve the rom. Some devs withdraw at this point, some tell the usres, what is frustrating, why it is and how to improve collaboration. If you think that is passive aggresive I need to be more clear on this the next time.
[OnePlus 3 & 3T Cross Device Development] realtos:
thx we appreciate that
[OnePlus 3 & 3T Cross Device Development] Naman Bhalla:
umm. weird but airtel volte is working absolutely fine here. I did flash https://www.mediafire.com/file/64mb...-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip/file though (Source: https://xdaforums.com/oneplus-3/how-to/x-s-s-s-t3858254) .
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
Just to clarify: This thread is about LOS16 OP3-specific issues. If it's a feature that is working on other phones on LOS16 then, yes, this is the right place to ask questions. If it's a feature that is not working in general or has not been implemented yet, then you'd have to go to the LineageOS 16 team. Just off the top of my head I'd say it hasn't been implemented yet. If it has in other ROMs then I think that it's not a big issue to add / the LOS team made the decision not to implement it. I'd love that feature too but I don't hink this is the right forum to ask for it - again: only device specific stuff please...
[OnePlus 3 & 3T Cross Device Development] Siddk007:
fyi, Airtel VoLTE works perfectly on Havoc OS. So, not all Pie roms have this issue
[OnePlus 3 & 3T Cross Device Development] legendavey:
Hmm, I must have missed their last cherry picking spree. :laugh:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I didn't write that, but

- On the latest build (20190601), my son's device had the bug and not mine !?

- We only flash if Changelog is not empty. As a result, an update almost daily and, as already mentioned, the "Phone is Starting" bug occurs hardly ever on both phones.

So both suffer from the bug but not at the same time .... and, interestingly, their settings are almost identical.
[OnePlus 3 & 3T Cross Device Development] :
Then my wish was stronger then my ability to read. That means our best chance to track this down has vanished. :(

Let's go ahead:

When does "Phone is Starting" show up? Directly while finishing the boot process, even before sim pin is requested, or on first unlock attempt?

Is "Phone is Starting" the exact string?

Any more ideas, how to reproduce? Just setting sRGB doesn't reproduce this on my device.
[OnePlus 3 & 3T Cross Device Development] Dirk:
[MENTION=4405529]nvertigo67[/MENTION]

It happens as soon as you unlock. The Homescreen appears and the message is instantly apparent. The power menu can be used but nothing else will respond to input. Widgets won't load. Hangs on the message until reboot.

I was going to say, one approach would be to find someone who isn't affected and find out what makes them special! You aren't affected. Assuming you use your own ROM, the obvious question would be does anybody on nlos have the issue? If not, how did you accidentally fix it? :p

---------- Post added at 19:01 ---------- Previous post was at 18:56 ----------

Perhaps there is some issue in the ROM that prevents it from applying the user defined profile until the system had booted? Or at least stuck in sRGB until booted up?

Must make my Boot Logo's look like total crap. That makes me sad. Well it would if anybody were using them! :p
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=7134312]knpk13[/MENTION] is on NLOS ... isn't it ? ... https://xdaforums.com/showpost.php?p=79644188&postcount=780

I await his answer...

==> https://xdaforums.com/showpost.php?p=79649588&postcount=2161
[OnePlus 3 & 3T Cross Device Development] :
Then it's finishUserUnlocking in UserController.

Have you configured an additional user?
[OnePlus 3 & 3T Cross Device Development] Dirk:
And by such methods we inch closer to the truth. Be great if we did find an entire ROM that had avoided the issue. Could be very helpful, although i'm skeptical.

Why oh why is my good friend nvertigo not afflicted such? What is unique about his device that he is blessed so?

:)
[OnePlus 3 & 3T Cross Device Development] :
In my experience it does not happen when I wait with unlocking till network connection (4G) is established. I am not using fingerprint or whatever, just swipe to top to unlock.
[OnePlus 3 & 3T Cross Device Development] Dirk:
No. It's just me.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No additional user on my side.
[OnePlus 3 & 3T Cross Device Development] :
No additional user on my side
[OnePlus 3 & 3T Cross Device Development] :
Karma... it's all about karma... *lol*

Interesting! That could lead to a timing issue - if so, I've some bad news: hard to track the cause, if timimg is relevant...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
My son flashed your great NASA Boot Logo & Animation... maybe the source of the PIS bug ... :D

==> https://xdaforums.com/showpost.php?p=79637436&postcount=46
[OnePlus 3 & 3T Cross Device Development] Dirk:
Your good karma is well deseved. As is my bad karma. :p

Where does the zip fix fit into all of this? If we only knew what the hell the damn thing did! Whatever it is, it worked.

:D

You honor me by using my NASA tribute. My heart is gladdened. It's just a little too big to attach to the thread so i have no way of telling if even one person downloads it. Well i know of one now. Thank you.

Perhaps we need some NASA techs to help us?

I have a nice combo in the bag but i'm sitting on it for now. Been making them faster than people can flash them! Also i'm breaking new ground on the idea of using a Boot Animation like a slideshow. Ten images at 1fps. Done one already and working on another tonight.
[OnePlus 3 & 3T Cross Device Development] :
If this is true, this could explain the timing differences. The nlos bootanimation has an extremely long last part... (@Dirk: ok, in that case it wouldn't be karma related... ;) )

Workaround would be: after entering the sim pin, wait till screen blanks + 10 seconds before unlocking.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Remind me next year to make a Bootanimtion that looks like a PIN request with numberpad. It will scramble the numbers every second and confuse the hell out of people. Bake it into your ROM and release it on April 1st. :p
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
A question: the PIS bug only occurs after flashing a new release ... Right?