HRTuning please respond whenever you're able. Anyone else, feel free to help as well if possible.

chipped pr4 running crome pro, p30 base, datalogging obviously added.
1990 honda prelude (the chassis is already obd1 including ecu plugs, from the factory, so there is no conversion harness)
turbo b20a5/b21a1 running 14psi on e85, gm 2bar map sensor,
LC-1 wideband to factory d14 o2 input, running open loop at all times
brand new moates bluetooth module with cn2 connector option

newest download of tunerview app on both my phone and tablet. the below described situation occurs identically on both my phone and tablet
purchased the Crome QD2 protocol
app is set to Crome QD2 protocol.
connects fine to the module.
datalogs flawlessly through crome pro when connected to my laptop via the Xtreme Hulog at 38400 baud rate
it will only register readings if the engine is running, it does not register anything if key on engine off.

Before connecting, when the ignition is on, the BT module's blue LED flashes consistently rapidly. Once connected to Tunerview App, the blue LED goes out for approx 2 seconds, flashes 2 times rapidly, then goes out again for another 2 seconds, then flashes again 2 times rapidly, and just continues this process the entire time it's connected. if I shut the ignition off, the LED goes out. If I disconnect from the app with the ignition still on, it goes back to continuously flashing again.
Could this be an indication of a fault code with the Moates BT module?

the only sensors/gauges that read accurately are the TPS and MAP sensor, and they are rather laggy.
VSS stays at 0
RPM stays at 56 or 57
BATTVolt stays at 0
ECT stays at 284
IAT stays at 280.
AFR stays at 10.0

I have configured the MAP and o2 correctly
I have tried the protocols for Crome QD2/Demon and Crome QD3 and it doesn't respond at all. so that option has been eliminated.

 

This is a screenshot with the engine running and holding throttle at 6%. The engine is cold, around 75*F, and is at about 2600rpm. Ambient temp is about 48*F.
Sorry for such a large pic, it's a screenshot from my phone, I couldn't resize it lol

 

edited first post to add potentially important info in bold

 

I finally got it to work, but it's still nothing like what some make it sound to be. it's incredibly slow, and it doesn't log anytime the engine is under fuel cut conditions, or with key on engine off. It also disconnects and reconnects completely randomly.
Personally, I don't understand why it's so incredibly slow. If crome can datalog at 38400 through the Xtreme Hulog and be instant and super smooth, why can't a modern smartphone react the same way with a BT module that transfers at a true 38400 as well.

 

While there is latency with Bluetooth that should be expected when compared to direct USB, it's definitely not slow. See videos from others as a comparison.

 

I have. And I was able to tell the difference between those using QD2 and QD3 after doing the following: The interesting thing is after all of this I went into the logs I had recorded and played several back to see if they were equally as slow as my live data and they were. Then I decided to play the sample logs that came with the app, and sure enough the QD2 log was suuuuuper slow and laggy, identical to my recordings. but the QD3 log played nice and smooth and fast.

I sent my bin to peter after he stated he hasn't done much with QD2 protocol and said that was part of why it was so slow, and asked me for my bin. haven't heard from him since.

 

QD2 should be slower. QD3 was the best option Crome offered.