Develop Bugs

Google Nav crashing with flashing white/black screen

got an issue with the google nav app crashing on me.
a little background first though.
had this issue on the std rom, and tried flashing the current ARHD 31.3 rom in the hope of fixing it, it hasnt!
from a fresh boot, i can go into the google maps app, choose a location and then use the nav app go to there, no issues at all.
next time, i open maps, no issues at all, choose my location, and as soon as i hit start navigation, the nav screen opens, showing the next turn to make at the top, the voice is telling me where to go, but the main map screen, is flashing black and white.
it flashes like that for 5 or 10 seconds before crashing, the only way to restore navigation to a working state is to reboot the phone.
its getting rather annoying now, as i dont use the nav very often, i tend to need it occasionally, and its irritating to have to reboot the phone just to get the nav working.
as far as i am aware, the GPS works fine in everything else, (Maps, strava, gps test) it just seems to be nav thats causing the issue.
i've already tried clearing the cache from settings, apps, clear data, but i still get the same issue
any ideas on what might be causing this
cheers

sning said:
got an issue with the google nav app crashing on me.
a little background first though.
had this issue on the std rom, and tried flashing the current ARHD 31.3 rom in the hope of fixing it, it hasnt!
from a fresh boot, i can go into the google maps app, choose a location and then use the nav app go to there, no issues at all.
next time, i open maps, no issues at all, choose my location, and as soon as i hit start navigation, the nav screen opens, showing the next turn to make at the top, the voice is telling me where to go, but the main map screen, is flashing black and white.
it flashes like that for 5 or 10 seconds before crashing, the only way to restore navigation to a working state is to reboot the phone.
its getting rather annoying now, as i dont use the nav very often, i tend to need it occasionally, and its irritating to have to reboot the phone just to get the nav working.
as far as i am aware, the GPS works fine in everything else, (Maps, strava, gps test) it just seems to be nav thats causing the issue.
i've already tried clearing the cache from settings, apps, clear data, but i still get the same issue
any ideas on what might be causing this
cheers
Click to expand...
Click to collapse
Had this too on CM, thought it had something to do with the ROM but after reverting to stock exactly the same issue. You're not alone
http://forum.xda-developers.com/showpost.php?p=46517908&postcount=15438

Any update on this issue? I have exactly same issue on stocked One X with Sense 5.0, Android 4.2.2.

I have exactly the same problem. I'm wondering if it's a Sense or app issue. Either way, I submitted a bug report.
Sent from my HTC One X using Tapatalk

I turned off the hardware overlay in the Developer section, and it seems no problem anymore... Not thoughtfully tested yet, tho...

Still flashing and crashing HTC One X+
Google maps to navigation is still flashing and crashing - even after turning off hardware overlays.
Works 1st time after reboot. If I swipe the app away from recent apps screen, then it starts failing.
3rd time I start it, working again, but I figure it's going to happen again.
AT&T HTC One X+ phone,
Android 4.2.2, Sense 5.0,
SW number 2.15.502.1,
HTC SDK API level 5.41,
Kernel 3.1-10-gf4d5f91
build number 2.15.502.1 CL280456
Anyone ever get an answer to this? Last post I found was December 2013 and still nothing.

delete this

I think I've found a kind of workaround to prevent this problem.
When you search the location you want to reach, and you are faced to the tile with these info:
8 min (3,1 km)
some info about trip
[MAP]
Start navigation
Instead of click on "Start navigation", click on "8 min (3,1 km)", then when the map is open, click on "Departure" and maps should not crash.
I hope the explanation is enough clear, I've translated texts from the italian app so I'm not sure if I've did it in the right way.

fez vrasta said:
I think I've found a kind of workaround to prevent this problem.
When you search the location you want to reach, and you are faced to the tile with these info:
8 min (3,1 km)
some info about trip
[MAP]
Start navigation
Instead of click on "Start navigation", click on "8 min (3,1 km)", then when the map is open, click on "Departure" and maps should not crash.
I hope the explanation is enough clear, I've translated texts from the italian app so I'm not sure if I've did it in the right way.
Click to expand...
Click to collapse
Totally works! Thanks!
HTC One X
Cyanogen 10.2.1
I was so annoyed with this...

I have had this problem for the last year using the stock, rooted AT&T Rom for my HTC One X + My wifes phone that is an HTC One X does not seem to do this. I found when I removed the maps update it worked well. When it updated it seemed to work a few times then the flickering and crashing started up again.
I tried the other suggestion above.
Finally I noted that when I clicked on start nav and as soon as it tried to open the map if I hit the power button and waited a second and turned it back on the image was stable. Sometimes I couldn't catch it before it crashed but if I did it would do the trick.
Why doesn't google fix this?

Same here. One X with rooted stock ROM.
When the flickering starts, i turn off the screen and then back on. This works for me in most situations. Still really annoying.

GPS Issue on stock 4.5.0

Since upgrading to OOS 4.5.0, my GPS has been having issues locking in. When I start navigation, the GPS does not seem to lock a location and it navigates as if the GPS is turned off (every few minutes it moves my location but not to my exact location). If I reboot and start navigation again, it starts working sometimes. Lots of GPS threads but none that I saw depicting an issue similar to mine. Anyone else have this issue?

shobuddy said:
Since upgrading to OOS 4.5.0, my GPS has been having issues locking in. When I start navigation, the GPS does not seem to lock a location and it navigates as if the GPS is turned off (every few minutes it moves my location but not to my exact location). If I reboot and start navigation again, it starts working sometimes. Lots of GPS threads but none that I saw depicting an issue similar to mine. Anyone else have this issue?
Click to expand...
Click to collapse
I have the same issue on latest beta, and I think it already started some beta versions ago. Sometimes going into airplane mode, waiting a minute, and switching all back on helps, sometimes a reboot is needed. If I'm stuck in "GPS not working"-state, I can see with GPS helper apps that satellites are detected, just never locked onto, regardless of signal strength. I just started rebooting my mobile each morning, this has at least mitigated the problem a bit. Nevertheless, I had situations where I was in a hurry and just needed navigation or my present position, and it was very annoying that Google Maps thought I was 250m away (positioning me without GPS) and never locked onto my position.

TheMaster17 said:
I have the same issue on latest beta, and I think it already started some beta versions ago. Sometimes going into airplane mode, waiting a minute, and switching all back on helps, sometimes a reboot is needed. If I'm stuck in "GPS not working"-state, I can see with GPS helper apps that satellites are detected, just never locked onto, regardless of signal strength. I just started rebooting my mobile each morning, this has at least mitigated the problem a bit. Nevertheless, I had situations where I was in a hurry and just needed navigation or my present position, and it was very annoying that Google Maps thought I was 250m away (positioning me without GPS) and never locked onto my position.
Click to expand...
Click to collapse
I forgot to mention that rebooting resolves the issue. That said, if I reboot and get the GPS to work and navigate somewhere, when I use the GPS again, say 20 minutes later, it has the same issue and has to be rebooted again. So for me, a single reboot per day does not seem to work.

this issue has been present for months, on both stable and beta builds, on OOS and custom ROMs
used to think OP3/T was a great phone, but now it's not even great for what you pay given GPS navigation is nonfunctional

Hey, a user posted a gps fix. Works great for me so far. Have a look in this thread. Hope it helps!

Dabarr said:
Hey, a user posted a gps fix. Works great for me so far. Have a look in this thread. Hope it helps!
Click to expand...
Click to collapse
One of my friend had this GPS issue but now it is fixed.I guess the OTA update fixed that

Dabarr said:
Hey, a user posted a gps fix. Works great for me so far. Have a look in this thread. Hope it helps!
Click to expand...
Click to collapse
This is not a fix, this is a workaround and it requires an unlocked bootloader

shobuddy said:
Since upgrading to OOS 4.5.0, my GPS has been having issues locking in. When I start navigation, the GPS does not seem to lock a location and it navigates as if the GPS is turned off (every few minutes it moves my location but not to my exact location). If I reboot and start navigation again, it starts working sometimes. Lots of GPS threads but none that I saw depicting an issue similar to mine. Anyone else have this issue?
Click to expand...
Click to collapse
Yes, same here. [emoji20]
Gesendet von meinem ONEPLUS A3000 mit Tapatalk

Hi, i have same problem, Yesterday i flash the rom freedom et and i can use the gps 3 hours without problems

It's been around for months, sadly. Every update I'm hopeful that it will get fixed

Mi 5s MIUI 7.12.28 - WiFi automatically turns on

Hi guys,
I've updated the phone to the last global beta - 7.12.28 and noticed one big issue and a few other smaller ones. I hope someone might have ideas on how to fix them.
The WiFi turns on as soon as the screen is off. What I've done so far is to make sure no app has permission to turn the WiFi on (using the built in permission manager). I've cleared cache and rebooted the phone several times.
Another issue is the MIUI memory optimization is always disabled, no matter if you change it to something else or not.
And the third one that I can think of right now is the region - it always reverts back to China. Now this has been outgoing for a while, so it might be something with my phone.
What I've done on the phone is to root it and have Xposed install and active. I've also ran Unbloatmi, great script to get rid of apps you don't need. I haven't tried alternative roms like Lineage.
Recently I installed floppy kernel, but the wifi issue remains with the stock kernel too.
I'm open to suggestions

Issue resolved with the next update.

I suggest to you to use global stable. It's old, but global dev is always bugged for this phone. Do what you want, but my experience is bad

Yeah it's always preferred to use stable roms on phones in production environment. But I like to live on the edge And I got into the routine to remove most of the unnecessary apps right after the update. So overall - the phone is quite stable. But now it has the same MAC as my wife's phone. Go figure...

Strange [and serious] lag issue, please help

I had my Pixel 2 XL since first release, running stock releases updated each month, stock kernel, and using Magisk. I also have a Pixel 2, configured exactly the same way as the 2 XL and the exact same apps. Apps are updated at the same time, same for patch releases. I carry both and use them interchangeably each day. They provide carrier/coverage diversity and allow for a longer day without charge.
A few days ago, with no known reason, my 2 XL started exhibiting a very strange lag behavior. In trying to resolve the issue, I have tried clearing Dalvik, flashing back to February, re-flashing March, and today flashing to April. I have also cleared certain app data and tried a custom kernel Nothing has helped. The problem does not exist on P2.
The lag I have observed so far:
1) I use the Google Calendar "agenda" widget. On boot, the widget is blank and shows "loading" and can take 10 or 15 minutes for the agenda items to populate (as opposed to immediately upon start up).
2) Playstore app updates: It downloads the app, but seemingly hangs and the update is VERY VERY slow.
3) On flashing the April patch, on first boot, the "Completing Android update" notification progress bar took about 45 minutes to complete (as opposed to a few seconds like it should).
4) I use Lightflow. On launching the app, I keep getting "app not responding" message. If I keep tapping "wait", it will eventually load. It is just loading VERY slowly.
I firmly believe that all of these issues are related to a single problem, like a system resource that causing these lags. At this time, I cannot update apps because it would take hours just to update one app.
I really don't want to do a factory reset if I can help it. Too many things to reconfigure, even with TiBu. Does anyone have any idea as to what might be the cause? I would really appreciate any input.
Thanks.

snovvman said:
I had my Pixel 2 XL since first release, running stock releases updated each month, stock kernel, and using Magisk. I also have a Pixel 2, configured exactly the same way as the 2 XL and the exact same apps. Apps are updated at the same time, same for patch releases. I carry both and use them interchangeably each day. They provide carrier/coverage diversity and allow for a longer day without charge.
A few days ago, with no known reason, my 2 XL started exhibiting a very strange lag behavior. In trying to resolve the issue, I have tried clearing Dalvik, flashing back to February, re-flashing March, and today flashing to April. I have also cleared certain app data and tried a custom kernel Nothing has helped. The problem does not exist on P2.
The lag I have observed so far:
1) I use the Google Calendar "agenda" widget. On boot, the widget is blank and shows "loading" and can take 10 or 15 minutes for the agenda items to populate (as opposed to immediately upon start up).
2) Playstore app updates: It downloads the app, but seemingly hangs and the update is VERY VERY slow.
3) On flashing the April patch, on first boot, the "Completing Android update" notification progress bar took about 45 minutes to complete (as opposed to a few seconds like it should).
4) I use Lightflow. On launching the app, I keep getting "app not responding" message. If I keep tapping "wait", it will eventually load. It is just loading VERY slowly.
I firmly believe that all of these issues are related to a single problem, like a system resource that causing these lags. At this time, I cannot update apps because it would take hours just to update one app.
I really don't want to do a factory reset if I can help it. Too many things to reconfigure, even with TiBu. Does anyone have any idea as to what might be the cause? I would really appreciate any input.
Thanks.
Click to expand...
Click to collapse
I don't have a good answer for you my friend other than trying to run it in Safe mode for a while to see if it helps. Other than that, only other thing you probably can do is a factory reset, which, I know, bites the big one!

Badger50 said:
run it in Safe mode for a while to see if it helps.
Click to expand...
Click to collapse
Thanks for that suggestion! The only condition I was able to test was to update apps. It went fine in Safe Mode. I rebooted back into regular mode and app update would hang. Based on what I read, the culprit would be a 3rd-party app?
I looked through all the apps that were updated in the past few days and do not see an app that would have the sort of large impact. There is no abnormal CPU utilization. Keep in mind that my Pixel 2 has the exact same apps and are updated at the same time. It has no such issues. I'm still lost.

The only update that could have an impact is Google Play Services. I'm on beta 12.5.21. Again, no issues w/ Pixel 2. I assume others don't have issues, we would otherwise heard about it by now.
Edit: Does safe mode run the ROM version of the Google Play Services?

snovvman said:
The only update that could have an impact is Google Play Services. I'm on beta 12.5.21. Again, no issues w/ Pixel 2. I assume others don't have issues, we would otherwise heard about it by now.
Click to expand...
Click to collapse
Yeah the only slowdown I've ever had was I think right before the February update. I never restart my phone or let it die so I had been 25+ something days of uptime. Restart was all I needed and it was the only 25+ days uptime that had any slowdown. I'm stock and only beta app I'm running is LastPass.
Sent from my Pixel 2 XL using Tapatalk

My phone lags BADLY when I use Snapchat and facebook.

Considering the affected apps (Google Calendar agenda widget, Lightflow, Playstore "install" process, etc.). What do all these have in common?

snovvman said:
Considering the affected apps (Google Calendar agenda widget, Lightflow, Playstore "install" process, etc.). What do all these have in common?
Click to expand...
Click to collapse
Did you ever figure this out?
I'm still on March and have started having this issue. It's related to charging the device. Whenever I charge (and even after pulling off the charger) Lightflow becomes extremely laggy. Also, installing apps from the Play store exhibits the behavior you described in OP. Interacting with notifications is very laggy as well (i.e. - tap a notification to open the corresponding app, and the notification disappears and nothing happens...then 2 minutes later the app opens). This goes on until a reboot. After that, everything is fine until I charge again. Which, fortunately for me, is only once every 3 days.
Was not having this issue until recently and have been on March for a few weeks.

Str0ntium said:
Did you ever figure this out?
I'm still on March and have started having this issue. It's related to charging the device. Whenever I charge (and even after pulling off the charger) Lightflow becomes extremely laggy. Also, installing apps from the Play store exhibits the behavior you described in OP. Interacting with notifications is very laggy as well (i.e. - tap a notification to open the corresponding app, and the notification disappears and nothing happens...then 2 minutes later the app opens). This goes on until a reboot. After that, everything is fine until I charge again. Which, fortunately for me, is only once every 3 days.
Was not having this issue until recently and have been on March for a few weeks.
Click to expand...
Click to collapse
I have not, unfortunately. The Playstore app install has, for the most part, resolved itself, but the hang does return from time to time. Lightflow is still a problem. I wrote the dev but there is no response. The other issue is the Google Calendar agenda widget. It takes 10-20 minutes to load on reboot. Mind you, the month widget works just fine.
Take a look at these threads:
https://forums.androidcentral.com/moto-z-force/803793-calendar-widget-doesnt-load-data.html
https://forums.androidcentral.com/google-pixel-pixel-xl/855985-screen-widget-loading-8-1-boot.html
They describe similar issues. I've also found other, similar observations but with no resolve.
I am on April and have tried a custom kernel. No joy.
Edit: Since I cannot test the calendar widget nor Lightflow in Safe Mode, I don't know if it actually is a system-related issue.
Edit 2: I do see a strange connection with charging, especially with Playstore installations and lags.

snovvman said:
I have not, unfortunately. The Playstore app install has, for the most part, resolved itself, but the hang does return from time to time. Lightflow is still a problem. I wrote the dev but there is no response. The other issue is the Google Calendar agenda widget. It takes 10-20 minutes to load on reboot. Mind you, the month widget works just fine.
Take a look at these threads:
https://forums.androidcentral.com/moto-z-force/803793-calendar-widget-doesnt-load-data.html
https://forums.androidcentral.com/google-pixel-pixel-xl/855985-screen-widget-loading-8-1-boot.html
They describe similar issues. I've also found other, similar observations but with no resolve.
I am on April and have tried a custom kernel. No joy.
Edit: Since I cannot test the calendar widget nor Lightflow in Safe Mode, I don't know if it actually is a system-related issue.
Edit 2: I do see a strange connection with charging, especially with Playstore installations and lags.
Click to expand...
Click to collapse
The only widget I use is the Fit step counter. That has always taken a minute or so to even show up on the home screen after a boot (8.0/8.1) for me. I don't feel it's related to my issue as that has persisted through all software versions I've used so far.
I'm beginning to think the lightflow issue is just that....a lightflow issue and it is affecting notifications, globally. And, it is somehow tied to charging state. I've seen lightflow do some weird crap over the years. I remember a simple gmail update caused lightflow to send my then device (htc tbolt) into constant reboots.

Str0ntium said:
I'm beginning to think the lightflow issue is just that....a lightflow issue and it is affecting notifications, globally. And, it is somehow tied to charging state. I've seen lightflow do some weird crap over the years. I remember a simple gmail update caused lightflow to send my then device (htc tbolt) into constant reboots.
Click to expand...
Click to collapse
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.

snovvman said:
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.
Click to expand...
Click to collapse
Light Manager might be a viable alternative for you if LF doesn't play nice for you. Works great without any lag issues :good:

snovvman said:
Well sir, you are EXACTLY correct. Based on your ideas, I disabled Lightflow and rebooted my phone. All was back to normal. Once I re-enabled LF, the problems came back. Thank you very much for pointing out your observations. I would have not considered LF to be the source of the problem, but it is now so clear. Again, I can't thank you enough (I'll "thank" both of your posts)!
I will try clearing the LF data to see if that solves the problem. I will report back.
Click to expand...
Click to collapse
Well, that's not exactly the news I wanted to hear lol.. I've tried light manager before and didn't like it at all. Light flow is kind of a crucial app for me. I guess I will just charge the device in the off state. Everything works fine until it gets charged overnight.
Now that you've sort-of confirmed light flow as the cause, I wonder if it might have to do with the charge state hooking. Do you have charging/charged profiles set up in light flow? If it's as simple as removing those, I could deal. I'm at work so can't really afford to test it right now.

Str0ntium said:
Well, that's not exactly the news I wanted to hear lol.. I've tried light manager before and didn't like it at all. Light flow is kind of a crucial app for me. I guess I will just charge the device in the off state. Everything works fine until it gets charged overnight.
Now that you've sort-of confirmed light flow as the cause, I wonder if it might have to do with the charge state hooking. Do you have charging/charged profiles set up in light flow? If it's as simple as removing those, I could deal. I'm at work so can't really afford to test it right now.
Click to expand...
Click to collapse
I first endured the slowness and made a LF backup. Then 1) I cleared the data and rebooted the phone without launching LF, the phone restarted normally, calendar widget was fine, 2) launched LF and granted notification access, restarted phone, all was well, 3) restored from LF backup, restarted, all is still well and LF launches fine. Corrupted data?
At least I'll know what to do next time. For your similar issue, just make a LF backup, clear data, reboot, restore, and hopefully it resolves the issue for you. Let me know.
Edit: Regarding your question on charge state hooking--I had LF running for many years and on the Pixel 2 XL since new. The problem only surfaced recently. My Pixel 2 is also fine. I would guess that there was bad data somewhere. Like I wrote above, a reset/restore brought everything back as before.

snovvman said:
I first endured the slowness and made a LF backup. Then 1) I cleared the data and rebooted the phone without launching LF, the phone restarted normally, calendar widget was fine, 2) launched LF and granted notification access, restarted phone, all was well, 3) restored from LF backup, restarted, all is still well and LF launches fine. Corrupted data?
At least I'll know what to do next time. For your similar issue, just make a LF backup, clear data, reboot, restore, and hopefully it resolves the issue for you. Let me know.
Edit: Regarding your question on charge state hooking--I had LF running for many years and on the Pixel 2 XL since new. The problem only surfaced recently. My Pixel 2 is also fine. I would guess that there was bad data somewhere. Like I wrote above, a reset/restore brought everything back as before.
Click to expand...
Click to collapse
Yeah, I went through all of that last week. I went from the newest version back to the last known stable (for me) version. I always keep a back up of the settings txt file as well as a TiBu file. My current version (previous stable) was installed from scratch.
Everything was fine for the first two or so weeks on March build. This just started after I applied the libs from the multi-touch fix. I removed that as I had hoped it would be related to the phantom swiping when scrolling (I don't game on the device) but it doesn't seem to be related the swiping. At first I thought that module was causing the issue as it started the day or two after adding it. That's the only change I have really made since setting up the March build. Not sure why it would just start out of the blue when it had been working fine for at least 2 weeks before.
I'll try some things over the next few days. First thing is going to be removing the charging profiles from light flow and see if that makes a difference.
Have you tried hooking up the charger since cleaning your data?
If removing charging profiles doesn't help, I'm going to reflash March build (removing -w from batch file) to both slots, redo twrp, elx kernel, magisk. I may do this anyway, even if removing charging from light flow fixes it.

Str0ntium said:
I'll try some things over the next few days. First thing is going to be removing the charging profiles from light flow and see if that makes a difference.
Have you tried hooking up the charger since cleaning your data?
If removing charging profiles doesn't help, I'm going to reflash March build (removing -w from batch file) to both slots, redo twrp, elx kernel, magisk. I may do this anyway, even if removing charging from light flow fixes it.
Click to expand...
Click to collapse
I have connected/disconnected a generic charger twice and once connected to a PC (slow charge). So far, still all good. The problem began in late/mid March. The April patch did not solve the problem. I am using Magisk. Stock/ElementalX made no difference. I will see if the problem resurfaces.
The likely cause that there are code issues with LF. I had LF slow down regardless of charger connection so I'm curious to know if removing the charging hooks help. I'm on the latest version.
Just curious--what not go to the April patch?

snovvman said:
I have connected/disconnected a generic charger twice and once connected to a PC (slow charge). So far, still all good. The problem began in late/mid March. The April patch did not solve the problem. I am using Magisk. Stock/ElementalX made no difference. I will see if the problem resurfaces.
The likely cause that there are code issues with LF. I had LF slow down regardless of charger connection so I'm curious to know if removing the charging hooks help. I'm on the latest version.
Just curious--what not go to the April patch?
Click to expand...
Click to collapse
I'm an "if it ain't broke" kinda guy. Everything except the phantom swipes has been perfect on March build. At this point I'm convinced the swiping issue is due to LG and therefore nothing to be done about it. I'm getting too old to flash a new ROM every week like I used to

Str0ntium said:
I'm an "if it ain't broke" kinda guy. Everything except the phantom swipes has been perfect on March build. At this point I'm convinced the swiping issue is due to LG and therefore nothing to be done about it. I'm getting too old to flash a new ROM every week like I used to
Click to expand...
Click to collapse
Gotcha! Since my last post, I have connected/disconnected charger five times. Each time with several minutes of wait time in between. I have also tested functionality while the charger is plugged in. All still good.
One side note, I have noticed, with many phones, that strange and undesirable things happen when you connect the charge while the phone is mid-boot. In my situation, the LF problem may have surfaced because of that.

snovvman said:
Gotcha! Since my last post, I have connected/disconnected charger five times. Each time with several minutes of wait time in between. I have also tested functionality while the charger is plugged in. All still good.
One side note, I have noticed, with many phones, that strange and undesirable things happen when you connect the charge while the phone is mid-boot. In my situation, the LF problem may have surfaced because of that.
Click to expand...
Click to collapse
Well for me I was just charging normally. Hope it holds up for you. If so I'll do a clean install again and setup from scratch.

Try clearing excess text messages and cache for apps. A friend of mine had thousands of text messages and social media buildup, and the phone got very slow and buggy, especially the camera app. After deleting thousands of texts, switching to Textra, clearing the app cache for frequently used apps, the phone is back to very fast again.

Constant/Excessive Crashing

My phone can have a habit of crashing constantly, but I never get any ANR dialogs or warnings, (at all,) that could help me pin point the reason for the crashes. This has been driving me insane, I've switched ROMs, factory reset, even factory flashed my device, but it will still eventually start crashing again. So, my question is: Which logs would I need in order to pin down what is happening, and how would I obtain them?

Based on the things you've tried, I would suspect a worn out battery. Does the "crash" tend to occur at around the same battery level? You could try a complete discharge followed by a complete charge to see if it improves any.

spam3234 said:
My phone can have a habit of crashing constantly, but I never get any ANR dialogs or warnings, (at all,) that could help me pin point the reason for the crashes. This has been driving me insane, I've switched ROMs, factory reset, even factory flashed my device, but it will still eventually start crashing again. So, my question is: Which logs would I need in order to pin down what is happening, and how would I obtain them?
Click to expand...
Click to collapse
Check to see if it could be a combination of software or some setting that is crashing with each other. You need to cover more info. Are you rooted? What monthly patch are you on?
Sent from my Pixel 3 XL

Since first submitting this thread, I have started to suspect it is related to WiFi, at least partially. I rarely, if ever, use WiFi. However the few times when I clean flashed my ROM as a solution, I used WiFi to reinstall all my apps. After finishing the downloads I would disable WiFi, yet immediately after a crash, WiFi would be enabled, and the "WiFi will automatically turn on when you are near..." notification would be present, (leading me to believe WiFi enabling itself is what triggered the crashes.) Though not all crashes demonstrated these factors, so I don't think WiFi is exclusively to blame.
ktmom said:
Based on the things you've tried, I would suspect a worn out battery. Does the "crash" tend to occur at around the same battery level? You could try a complete discharge followed by a complete charge to see if it improves any.
Click to expand...
Click to collapse
I'll have to keep an eye on that. Currently, I don't know where the batteries charge has been each time.
Eudeferrer said:
Check to see if it could be a combination of software or some setting that is crashing with each other. You need to cover more info. Are you rooted? What monthly patch are you on?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I apologize for not including this information in my initial post. Yes, I am rooted. I'm running Magisk v20.3, Magisk Manager 7.5.1. I'm currently on Android 9, though I believe when I tried Android 10, the problem persisted. I'm running Bootleggers ROM 4.3 Stable from 03-sep-2019 (I had run both stock and Dirty Unicorn, however Bootleggers appears to be the most stable.) Build Number PQ3A.190801.002. I can't think of any other particular info to include.
Edit: My phone also reliable crashes when opening System Settings>>Apps & Notifications>>(Selecting any particular app,) and I have crash logs for those crashes which I'll share in the even that they may shine light on the issue.
https://del.dog/rivipecafi.txt
https://del.dog/inamitycor.txt
https://del.dog/dapahycoxa.txt