yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Sorry, forgot to mention. NLOS. Also no it hasn't happened to me exclusively after flashing a new build. I thought it was normal (phone just taking longer to boot) and just rebooted the phone and it fixed itself. It's been random, and I can't find any way to reproduce it. Also what happens to me is exactly as [MENTION=673308]dirk d[/MENTION]escribed it. I didn't bother reporting or trying to fix it because it happened very occasionally, so I just rebooted.
[OnePlus 3 & 3T Cross Device Development] Flippiej:
Lol I've encountered the PIS bug today for the first time and didn't even think it could be spread among more people. Had my own 'solution' that probably doesn't do a thing, since I thought I broke something myself.

I was trying some things in Titanium backup to make Android Auto work again (making it a user app - back to system app) and after a reboot the PIS message showed up after putting in my screen pattern. A forced restart afterwards resulted in the same bug so I thought I broke something in my Opengapps. I reflashed a week old version of Opengapps I had ready and my phone booted up normally.

Haven't restarted my phone since to confirm actual succes rather than chance. Since you guys are pointing fingers at other stuff I don't really feel like trying ?

LOS build: 28-5
[OnePlus 3 & 3T Cross Device Development] Dirk:
Nope. Seems to strike on any random boot, regardless of whether anything was flashed. I think most of us only reboot to flash something, leading to the impression that one thing leads to the other.

Finished my new slideshow:

https://xdaforums.com/showpost.php?p=79481003&postcount=29

:)

---------- Post added at 23:26 ---------- Previous post was at 23:05 ----------

So my impression that the OP5/T was worst affected was wrong. It's only because everybody there has actually mentioned it. Everybody here thought they were the only one and didn't say anything. Kinda funny. :D
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Im not sure if this is related, but I got a phone is starting message Friday. No other symptoms, just phone is starting with a progress bar, it was only on the screen for a second or two and then the phone acted normally.

This was just after I reflashed the 0504 build. (I uninsulated Spotify while it was still running and I couldn't control the volume of any media with any Amp and it wouldn't switch to the phono output when I plugged in an aux cord. Weird issue but an easy fix, so I didn't think too much of it). The phone started normally until I input my pin then it showed phone is starting for a second then it was gone and all was normal.

1+3T, sRGB, 0504 build, TWRP 3.2.3-10, FW 5.0.8, addon SU, no other mods.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Interesting. I don't recall ever seeing the message and not have to reboot to clear it.

Do we think there's anything to be gained from gathering more logs? Easy enough to ADB Logcat while the message is on the screen. Thats what i did last time. I keep USB Debugging enabled now just in case.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Questions for users with the Android is starting bug.

Which launcher do you use?

I've also seen this message multiple times but it disappears after a time (and progress bar finishes).

And I'm using Nova launcher and can use it normal directly after boot (widgets are loading etc.)

So I didn't assume that this is a bug - I thought this is a normal Android message.

And for me I also think it happens after flashing a new ROM. (For this I clear always the cache & art cache in TWRP.)

But it's right - you won't reboot the phone if it's working perfectly ;) - and so only for flashing an update
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Nova here as well.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
My bad. I didn't hit refresh on the updater screen and ended up downloading the 29 may build.
[OnePlus 3 & 3T Cross Device Development] :
LOS with default Trebuchet launcher..

As said before, for me it seems an timing issue. When I wait till network connection is established before unlocking, I do not have the PIS message after flash.

Did someone tried that also?
[OnePlus 3 & 3T Cross Device Development] Flippiej:
Nova, for me it does not finish loading and I have to restart my device (I waited for 10 minutes). I'm not sure if a 4g connection is already stable upon unlocking, next times I restart I'll make sure to wait.

WiFi connection does not load during the PIS for me though.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
The PIS bug

Unless I'm mistaken, the PIS bug doesn't seem to depend on the launcher, a flash of a new build, the s-RGB profile mode ... etc.

It occurs randomly and not often on LOS/Based ROMs.

With Nova launcher, a reboot is not necessarily useful to bypass it but a little patience (to be confirmed ?)

It seems to be related only to OnePlus devices (see Dirk's posts) and LiveDisplay would be the culprit.

A question: What are the common elements of all OnePlus devices?

May the Force be with the developer(s)... ;)

For [MENTION=1763460]Dirk[/MENTION]: my son flashed your new slideshow ... :cyclops:
[OnePlus 3 & 3T Cross Device Development] Dirk:
I like your son. He's becoming a firm favourite of mine. :good:

The Oneplus factor in this bug has to be a clue. If Livedisplay, why is it only an issue on OP devices? I've asked a question here: https://xdaforums.com/showpost.php?p=79654405&postcount=1019

We should keep an eye on that thread to see if removing Livedisplay has worked or not. There has to be a reason the dev feels so confident about it. Perhaps he was replacing Livedisplay anyway and just noticed that the bug had stopped? I reckon it occurs once every ten or so Boots for me. I wouldn't be confident that it was gone until i had done at least twenty or more without issue.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I will try to capture a logcat the next time.

But it's very hard because of the randomness factor. And I'm not always at the PC anyway.

But I'll try.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For info: https://www.reddit.com/r/LineageOS/comments/bw9ffj/livedisplay_feature_was_removed_in_los_160_june/
[OnePlus 3 & 3T Cross Device Development] :
This is not limited to nova. We need to verify or falsify, that waiting till screen goes off +10s avoids this issue.

We also need to confirm weather commenting out (or deleting) the complete livedisplay block from /vendor/etc/vintf/manifest.xml solves the issue.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
anybody thinks the padding between the signal icon and battery(text) is a bit too much esp. on white background
[OnePlus 3 & 3T Cross Device Development] Dirk:
Yep. Something ain't right! Here's mine on crDroid:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
+1 ... The first time, I'm sure I waited several minutes before rebooting OP3T.
[OnePlus 3 & 3T Cross Device Development] :
It's NOT about waiting before reboot, nor about switching off (@pedritopl). It's about waiting after entering the sim pin till the screen goes off by itself and add about 10 seconds (just to be sure) before UNLOCKING the device.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
All right. Now I understand the procedure, and I most certainly did not proceed in that way as at that time I wasn't even aware of this bug :)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I confirm .... I waited several minutes after entering the sim pin till the screen goes off before unlocking the device ... because I don't spend my time looking at my OP3T to make sure everything is working fine. ... I usually do something else more interesting ... an old-fashioned procedure... :D
[OnePlus 3 & 3T Cross Device Development] :
What do you confirm? Waiting helps or waiting doesn't help?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
waiting doesn't help ... unless my mind is playing tricks on me !

Edit1 : I hope to face the problem again to be 100% sure.

Edit2: I just performed about twenty five successive restarts (with some random power off) without PIS issue (latest build).
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
selecting night light to auto "turn on from sunrise to sunset" and it didn't work untill location was turned on but live display was working good without turning on the location. have anyone faced this?
[OnePlus 3 & 3T Cross Device Development] :
I was forgotten to mention one thing in my procedure to prevent the PIS message on boot.

After flash, on first boot, as said I wait for network connection to establish.

But I do this with screen keeping on, so moving my finger a little over the screen to prevent it to go to sleep.

Sounds strange may be but for me it works with OP3T, LOS, default Trebuchet Launcher, no Google stuff installed.

So, in fact you have to keep looking to your screen and moving your finger over the lock screen to prevent it to go to sleep till network connection is established (no cross anymore in the signal icon at the taskbar).

Sorry for the misunderstanding.
[OnePlus 3 & 3T Cross Device Development] Dirk:
People have often said it's the flash/cache wipe that leads to a PIS boot. I've thought the same thing myself. I'm uncertain because i'm aware of logical fallacies and try to avoid falling into the magical thinking traps that they create. I mostly reboot to flash something but it doesn't automatically follow that one thing leads to the other.

That said, there is that nagging doubt. I've flashed a lot of Boot Animations recently without issues. But no cache wipes. I've done restarts without entering recovery at all, with no issues. When i flash ROM builds and clear cache, i run into PIS.

Does anybody remember the old 'Android is Starting-optimising apps 1 of 52', messages? I think it was ART/Dakvik, right? If you cleared Cache/Dalvik you would go through that rebuild again. Sometimes it would hang and the advice at the time was always 'clear cache again'. Is 'Phone is Starting' the new 'Android is Starting'? Is clearing Cache/Dalvik causing something to need rebuilding, and then hanging?

Perhaps that then explains why unlocking too fast could be a problem. Something is busy rebuilding cache and gets interrupted?

Just a thought.

Edit: Also, thank you for doing so much laborious and systematic testing for us. On this issue and all the times. You're an absolute champ. And everyone here who contributes their theories and experiences in such an altruistic fashion. It all helps. Really.
[OnePlus 3 & 3T Cross Device Development] Andrea224:
Ok, fine. Btw I still notice that this setting sometimes turns on and, because there's no way to change it, I have to deal with this "bug". Also, if I search it into the setting, it still shows up, but it redirects to the Livedisplay settings without seeing it anyway.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I daily flash the latest build (if Changelog is not empty) and clean caches (via an option of Lineage Downloader app).

Since 20190529 or 20190531, I don't run into PIS .... (and hardly ever before).

[MENTION=1763460]Dirk[/MENTION]: The old altruistic man thanks you.

PS: I just flashed your Nebula Boot Logo & Animation and then cleaned cache ... without PIS issue ... ;)

(https://xdaforums.com/showpost.php?p=79513074&postcount=31)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Yeah, the cache wipe theory could be a red herring. Like every other theory so far. :D

I've been toying with the idea of doing a Boot Logo & Animation using an LED Readout font. Like an old calculator. Will play with some designs when i get home from work!

Regards to Eric Jnr.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
+1 ... https://www.reddit.com/r/LineageOS/...ew_circle_battery_icon_options_how_to_reduce/

---------- Post added at 11:19 ---------- Previous post was at 10:57 ----------

I've tried... and thank you for your time and effort in finding a solution.
[OnePlus 3 & 3T Cross Device Development] Dirk:
There is precedent for the timing theory. Neobuddy, the crDroid OP5 Maintainer and one of the core team, has had a go at the issue from the same starting premise, i believe. When he released a new build some time ago, with mention in the changelog of an attempted fix i had a good look at the recent commits. In one there was a comment about delaying something-or-other until later in the Boot sequence. My memory is sketchy, but i think that's accurate.

If two devs have arrived at the same conclusion independently there must be something in it!

Thank you for your efforts and travails thus far. I'm sure a breakthrough will come. I wonder what the OP makes of all this? He can't be unaware of the PIS issue, i'm sure.

---------- Post added at 13:43 ---------- Previous post was at 13:29 ----------

On a different subject i need a small favour. If anybody does a clean flash, or a nandroid restore, could they time exactly how long in seconds the Boot Animation takes from beginning to end on that initial boot-up for me? It's been a while since i've done either, but if memory serves there's a significantly longer Animation phase before initial setup begins. (In the case of a clean install anyway). I'd like to know exactly how long.

It's not mission critical or anything. Just be helpful if somebody remembers to put a clock on it the next time they are able.

Thanks.

(I did a Cache/Dalvik wipe in Recovery earlier and that only added three seconds to the time).
[OnePlus 3 & 3T Cross Device Development] cokesucker:
I updated to the latest RR 04/06 build and the PIS issue is gone tested with all LD profiles.

Also Night Light was added which wasn't there in previous builds on RR at least.

Perhaps next LOS build will be the same.
[OnePlus 3 & 3T Cross Device Development] :
los has already the kill-livedisplay-temp topic merged. It has been discussed here and [MENTION=9708417]Eric_Lev[/MENTION] has posted a link to a very good explenation on that changes. The PIS issue has been reported with kill-livedisplay-temp applied. Not related.
[OnePlus 3 & 3T Cross Device Development] cokesucker:
Ok i see, sorry about that.

Just thought I'd share since my PIS/safemode issue was caused exclusive by setting LD profiles other than standards and nothing else.

So it seems my device is not affected by whatever is being discussed here.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
First step (logo) :

Boot logo = 12 s

Second step (animation) :

with the LOS Boot Animation (2 tests):

- Reboot = 15 s

- Re-install or update (flash build + wipe Dalvik and Cache) = 44 s

- Nandroid (wipe Dalvik/Cache/System/Data + Restore) = 18 s​

with your Nebula or Planets Boot Animation (2 tests):

- Reboot = 12 s

- Re-install or update (flash build + wipe Dalvik and Cache) = 38 s

- Nandroid (wipe Dalvik/Cache/System/Data + Restore) = 13 s​

Standard deviation: ca. 1 s

Note that I used Lineage downloader app as updater.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Just wow. Thank you so much. I didn't expect anyone to put themselves out to do that. You went above and beyond! Much appreciated my friend. :good:

Looks like a boot after nandroid restore doesn't add much, but after new install it's much longer. That's just what i needed. Thanks again.

(Next time you visit my thread, the reason for all this may become apparent)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
De nada !

To be noted:

The data of my previous post were performed with builds 0602, 0603 and 0604.

However, I just performed a new test: an update from 0529 to 0603 (with the LOS Boot Animation) is 17 seconds longer than from 0602 to 0603... Strange or expected !?

(I think I guessed it... and that's why I did the tests so quickly....)
[OnePlus 3 & 3T Cross Device Development] :
So PIS is fixed on crdroid? Woukd you take a closer look at the recent crdroid commits and give a pointer, please?

Or is it something similar to https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/248353 ?

EDIT: this is the very same on crdroid:

https://github.com/crdroidandroid/a...mmit/d6915c5315d7a3272860f8fc940aab8ba076d6e3
[OnePlus 3 & 3T Cross Device Development] Dirk:
While boot times and therefore animation times seem to be very consistent on normal reboots, i need to allow for big variance at other times. I had to figure out what to do if a ten second countdown animation completed and the system wasn't ready to launch. No point looping the countdown. It would be stoopid. :laugh:

I think you already saw one solution earlier. :D

No, not even close to fixed. It defies all attemps so far. I'll try and track down the commit that was 'an attempt' to fix it. I'm not sure it's the one you linked. Might be something else.

It was in the Changelog (Cheeseburger) for the 30th April build. Previous build was 25th April. Commit hunting need only be confined to those dates. I'm out to dinner for a while now.

Edit: [MENTION=4405529]nvertigo67[/MENTION]

I think it was this one... https://github.com/crdroidandroid/a...mmit/164e7c1ebbaec3e7a9867d4bffc784a42a438711

Of course, nothing was fixed. Maybe it helps shine a light on his own thought process regarding the issue?
[OnePlus 3 & 3T Cross Device Development] FiveZeroes:
Hi, so I've been troubleshooting with this for a few days and had no luck, but has anyone managed to get wifi calling to work? On T-Mobile if that matters.
[OnePlus 3 & 3T Cross Device Development] :
Does it work on OOS? If so: mcc/mnc (in apn settings) and logs, please.
[OnePlus 3 & 3T Cross Device Development] FiveZeroes:
Not sure about OOS, I've been on Lineage for over a year now, but just moved and realized that wifi calling didn't work. I did notice that VoLTE seems to work fine, so its just VoWiFi.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About the PIS bug:

As previously mentioned, my son and I have the same phone: an OP3T.

Contrary to what I thought, the settings of both devices are identical.

Since 20190529:

I didn't run into PIS .... (and hardly ever before).

my son ran at least (begging a teenager for information is not easy) three times into PIS ... (clean flash on 20190529)

What is the difference between the two OP3T? Unlike me, my son has installed several applications that generate a myriad of notifications (i.e. instagram, snapchat, clash of clans...) as soon as the device is unlocked.

Maybe it will help you...

Edit: If it makes sense... How to delay some auto start apps (e.g. snapchat, instagram... ) to test the PIS bug on LOS 16? Because no such option in Private Guard … only Allowed, Ignored or Always ask.
[OnePlus 3 & 3T Cross Device Development] Dirk:
It's a useful case study for troubleshooting. The same reason Twin studies are so important. Two of the same thing so where do the differences lay? A thought experiment.... if you switched phones and each set them up the same way you usually do, would you now have all the PIS boots, or would Eric Jnr still be getting the Lions share?

My own Twin study. My OP5 and OP3T on the same ROM and set up exactly the same seem to be affected the same amount. I also debloat and restrict Boot permissions. My setup is minimal with a minimal number of Apps. I imagine your setup is likewise pretty minimal and well pruned. Same for Nvertigo67. Then your son, who i imagine is no different than many here, has all the things you mentioned and probably doesn't give much thought to how many are running at Boot.

I wonder if someone who was badly affected by it were to restrict all the Boot permissions, whether it would reduce the frquency of bad boots?
[OnePlus 3 & 3T Cross Device Development] fhloston:
You're on tmobile and volte works ootb on lineage for you on op3?
[OnePlus 3 & 3T Cross Device Development] FiveZeroes:
As far as I can tell, yes. My connection doesn't drop below LTE during calls and IMS settings page says voLTE is working.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
What do you debloat from the ROM? Do you have a script to do it upon updates?

How are you restricting boot permissions, just through privacy guard's advance menu or something else?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Saw "phone is starting" dialog briefly (about 2 seconds, shorter than usual, and it resolved itself) after a reboot and upgrading to Magisk 19.3, didn't wipe anything. Attached logs captured via Matlog, though I'm not sure it captures the boot process or the PIS part.

Edit: I've rebooted several times in the past week (not just to flash something), and this is the first time I saw PIS.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Just Privacy Guard and gapp-config.txt. The best way to avoid bloat is to not install it in the first place of course. :)

[MENTION=7134312]knpk13[/MENTION] Thanks for the Log!
[OnePlus 3 & 3T Cross Device Development] Dirk:
The 'Phone is Starting' bug so far hasn't been reported on the LOS Issue Tracker (Gitlab). I doubt a report from someone using a LOS Based ROM will garner too much interest from them, so would someone running stock LOS like to do the honours? At least you'll have all the required build info etc that the report needs. We have Logcats already.

Before everybody goes off half-cocked and tries to do one, is anybody up for it? [MENTION=9708417]Eric_Lev[/MENTION] or [MENTION=4405529]nvertigo67[/MENTION] would seem to be the obvious choices considering their obvious talents. Are either interested, or have the time to do it? I'd understand if both give it a pass with all that you're both already committing to this hobby of ours!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Thank you [MENTION=1763460]Dirk[/MENTION], but [MENTION=4405529]nvertigo67[/MENTION] is much more competent than me to report an issue on the LOS Issue Tracker (Gitlab) and he is a Recognized Developer.
[OnePlus 3 & 3T Cross Device Development] :
I havn't expirienced PIS. That's why I can't provide a log. I havn't seen a op3/t log so far.

Nobody, who has expirienced PIS has done a proper issue report, so far (with logs), and you ask me (I'm using a los based rom, which isn't plain los, and having never seen PIS on my device) to make a proper issue report on gitlab...
[OnePlus 3 & 3T Cross Device Development] Dirk:
I don't think the LOS devs care much about XDA titles. ;)

nvertigo67 is right though. We do need a Log from the OP3/T first. Preferrably from a full hang with the message on screen. (I don't know why in a few cases the message clears itself, but i'm not sure a log in that case would be representative of the issue).

Once we have the log, we'll go from there. :good:
[OnePlus 3 & 3T Cross Device Development] :
I'm a senior member. I'm not a recognized developer.
[OnePlus 3 & 3T Cross Device Development] James Bottomtooth III:
Sadly I have had to perform a clean flash after experiencing the Rescue Party screen after an OTA update.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Fully agree !

For me, you are...

About the end of one of my previous posts (https://xdaforums.com/showpost.php?p=79664624&postcount=2243)

==> Edit: If it makes sense... How to delay some auto start apps (e.g. snapchat, instagram... ) to test the PIS bug on LOS 16? Because no such option in Private Guard … only Allowed, Ignored or Always ask.

---------- Post added at 22:16 ---------- Previous post was at 22:11 ----------

About Rescue Party issue, did you have time to run tests?
[OnePlus 3 & 3T Cross Device Development] Dirk:
I dislike the change to the wording in LOS 16. It was clearer before. 'Ignored' is what used to be 'Never'. i.e 'Don't start at Boot. Of course 'delaying' could mean something else and there's no method i know of to actually set a delay. Anything you set to 'Ignored' can be opened manually after Boot is complete and it will of course continue to run until next Boot, unless you 'Kill' it in the meantime.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I will try "Ignored" on my son's OP3T .... :cool:

I hope he'll agree ... :confused:
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Same here for the 0603 build

Was using TWRP 3.3.1-0 , Magisk 19.2
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Did your try without Magisk ?