[G2 Original Android Development] dr4stic:
This was my original thinking, however since my background is more in web/scripting languages and not in c/java, I'm out of my depth when it comes to debugging this problem. Finding it is something I managed to do, fixing it is a different matter entirely. I have suggested trying to catch the error before a reboot has been triggered, but that's a more of a workaround to the real problem (which I'll discuss further in the email) than an actual fix. Right now we're trying for an actual fix.

From what I can tell it has nothing to do with volume of data. And, when I said data, I meant voice data as well, as in phone calls. The potential for the trigger comes with the cellular connection and the setting for "High Accuracy". I am not sure what you mean with the second point above, but I will say that after the first crash/soft reboot, my phone will much more easily begin to crash, even after I set the phone to device only. If I force a hard reboot after the crash my phone then is fine.

And here lies what I think is the problem. At some point rather quickly, the rabbit hole we go down does hit a wall with proprietary binaries.

I believe part of the problem is that we're using binaries from a different device that, on some level, has to interact with the radio. The dev's original thinking was that the hardware is similar and the interfaces should be the same, so it *should* just work. But I believe there are some nuances in the internal implementations that are causing the crash. I've managed to persuade our dev to go back and work with me to try and use the binaries that came from our phone and, at the moment, I'm sitting on a relatively native build on High Accuracy that hasn't crashed in a day and a half of operation and phone calls. I know it's been making AGPS calls because my map location kinda works and my GPS chip is at the moment inaccessible (and when I was driving I was lacking WiFi). Now all we need to do is figure out why GPS isn't working :)

I think this is gonna be the way to go. Whatever the complaint was that drove our dev to use the "better" bacon libloc is gonna be mooted by the stability that comes from going native. I just have to get his attention focused enough to finish figuring out this problem :)

And finally, the biggest problem we have: Time. Our problem is unique, by most rights we really shouldn't be experiencing it. I imagine the modifications to the infrastructure to enable this sort of solution would require quite a bit of time. It's also important to remember that it's already been over 2 years since these devices were announced, and in a few weeks it'll have been 2 years since they were released in the US. They're old, and I can tell you from experience that most devs get distracted easily and like shiny new things. By most measures the modding community for this device is small, and the subset that's willing to mod for CM is even smaller. We've really just got one dev and a thorn in his side (me) trying to poke him in the direction of fixing bugs. And honestly, I'm grateful we have that attention because CM12.0 was terrible on my devices and with this eventual fix I think 12.1 will just about be perfect.

School just started back and so getting some attention on this problem is difficult. I don't think it'll be forgotten, but we just need a little patience and time. It's being worked on, believe me.

---------- Post added at 02:42 PM ---------- Previous post was at 02:37 PM ----------

in my crash testing last night I noticed this too, on a video I tried to play. This was on a build I did that would probably match up with 20150825. The logs for my particular crash pointed to stagefright. I think the chrome thing is an internal CM thing.

Just a word of advice: At the moment, I think the stable builds are in the early 2015-08-20's. like 21 or 22. Just stay with those. I don't think enough is changing right now that would make it worth it to constantly upgrade. Marshmallow is about to be released and I think more work is going into setting up the infrastructure to make that transition easier than there is for new features and substantive bug fixes. I'll definitely be posting when it's time to try some fixes for the random crashes related to AGPS. So it may be a good idea to find a build you like and stick with it for a while.