So 32 bit apps are not sounding like a cause. Mine still has them and it has been acting mostly good for two days. Others are reporting eliminating them doesn't fix it. (although my plan was more drasitic -- eliminate them, then do a DFU restore to fix all the files that may be screwed up)
Here is a clue that is highly puzzling to me. The phone will be fine or mostly fine for hours or days, then give a lot of grief in one day. Sounds like others have the same thing. So it causes us to try to correlate it with things and hypothesize causes like if I stand on one foot and pat my head it works, but if I don't it locks up. Obviously hogwash.
The phone is processing instructions a gazillion times a second. What would cause it to be "funny" only a small fraction of the time?
I'm imagining my coding days and that the main line of code is something like this:
1. Poll cell tower
2. Check for incoming signal
3. Check for data
4. Check for this
5. Check for that
And somewhere in there:
Check if screen input circuits are registering a voltage (or digital) change, indicating user input.
This user input leads to new lines of code, but the main line "interrupts" because it is higher priority. So sometimes while we are trying to do something, the phone pops out of accepting user input briefly (jumpy behavior) or for a long time (unresponsive screen) BECAUSE IT IS BUSY DOING SOMETHING ELSE!!!??!?!?!?! When running normally the processor is capable of jumping in and out of subroutines so fast, we notice none of the work it's doing in the background.
What is making it so busy? And what would only do it once in a while at seemingly random intervals (it can't be random -- computers don't do random)?
I'm at a loss to figure it out. I just wish we could get acknowledgement that Apple knows there is a bug and is working on it. I haven't called them I admit -- not sure what they'd say since my phone is 23 months old.