Understanding OBD2 Diagnostic Phone App

A coworker recently purchased a used appliance that was also due up for an emissions test. While there was no CEL, it failed on the cats and O2 sensors. His OBD2 diagnostic app on his phone has two sets of readouts. One is for the current drive cycle, the other is for the "emissions readiness". Originally both sets had the same errors. He swapped out all 4 O2 sensors. Having driven it a bit since then, the emissions readiness errors have disappeared, but the current drive cycle still errors out on the current drive cycle for 20 miles or so for the emissions controls before they go 'green'. This leads us to believe that he may be good to go for his emissions test if they're only looking at the readiness and not the current cycle for this, but does anybody know if that's actually the case?  Also, while monitoring each bank in real-time both sensors in one bank very closely mirror each other continuously during both idle and free revving, while the two sensors for the other bank only partially do while free revving but not really while idling...So he is concerned that something may still be amiss. He gets only gets one free retest, so he wants to make sure he understands what the readout is telling relative to what the test facility is looking for.  Any insight that can be provided would be greatly appreciated.

What app is he using ?

He's using car scanner, gauge pro, and torque lite. They differ on whether they call the issue a 'fail' or an 'imcomplete', but they're faulting on the same set of items. Here's a slightly blurry shot of what one is showing.

I'm pretty sure that it's the readiness monitors that are checked for emissions testing.

If a rear sensor follows a front, that generally indicates a week cat.

A monitor is basically a test of a system's function. Each monitor will only run under certain conditions. Some conditions are common, some arent, so it's possible to drive for quite a while without hitting the conditions to run certain monitors. Generally if all the monitors have completed and there are no stored codes they should be able to test it.

Streetwiseguy said:

If a rear sensor follows a front, that generally indicates a week cat.

That's a long cat.  Then again, I'm not sure how to tell the difference between a 1 sec, 1 min, 1hr, 1day, and 1 week cat...  How long is a week in the physical world?  Where's Einstien to tell us...  

LOL.  

Vigo said:

A monitor is basically a test of a system's function. Each monitor will only run under certain conditions. Some conditions are common, some arent, so it's possible to drive for quite a while without hitting the conditions to run certain monitors. Generally if all the monitors have completed and there are no stored codes they should be able to test it.

And for what is pictured, all of the monitors have run enough to say that the system is ok.  The upper part of that is if the monitors have run on that particular drive cycle- which isn't not required to do every single time you drive- just that the test is done at some point.

In other words, as APEowner posted, the car is ready for inspection, and there are no codes that will cause it to fail.

Thanks for confirming my suspicions.