Should it report as 2.5.0? Or is it reporting as it should?
No, pre-release still reports as previous version. Reason for that is if you are using pre-release, it will be automatically updated from Play store when actual release is live.
Just to make sure, please install RealDash-v250-prerel2.apk from Dropbox and send another debug log. Please note the date and local time when debug log is uploaded so I can verify that log is from you.
Just sent over two files. First around 7:30pm EDT, second a few moments later. First will have holley data using the modified old xml. Second will have the out of the box terminator/dominator xml.
Yep, confirmed. I can see now the two connection attempts and later one receives the frames.
The first one is using the old xml file with my ID added to it, this one works. The second one is the out of the box option from real dash list that does not work.
We are making some progress
- In the log, 18th of March there is no connection at all as Android 34 onwards requires different flags for permission. This was fixed.
- On 21st of march, first attempt connects to the adapter but there is no data.
- Second attempt later connects and receives some CAN frames.
The odd thing is that it almost seems that you are using two identical canable adapters. First one tied to /dev/bus/usb/002/007; and not receiving any data, and second one to /dev/bus/usb/002/010; and is receiving data. Unless you are really using two adapters at the same time, this does not make sense to me.
There are two adapters, one a dashbox that I converted to a usb via a rs232 usb adapter. Then a can usb adapter to the holley.
But only one Canable adapter, right?
Waveshare is the last time I tried it, but I also have a canable, only one of those adapters used at a time of course. That adapter is easy to get to. The dashbox however requires dash removal and my screen removal to connect/disconnect. I guess I could go into the garage and remove the connection and only pull the holley data that way.
I don’t think its required to remove the DashBox connection, but the datalof clearly shows that there is an adapter with name: “CANable2 b158aa7 GitHub - normaldotcom/canable2-fw”
Could you verify what are the adapter names on the connection settings?
I have a Waveshare USB-CAN-A adapter. Originally I had a generic canable adapter, I thought since I was having so many issues perhaps it was the problem so I replaced it with the waveshare. I’ll have to look at the settings tonight when I get home, but they do work from the head unit to the adapters. I believe it was just the default of 115200/8N1. Both will work with canbus monitor and realdash with the modified old xml. Neither will work with the newest xml on canbus monitor or real dash.
Confirmed, 115200, DTR none, RTS none. Between both adapters.
Standard can frame, 1000 kbs for can speed, normal can mode.
Using the holley_efi_can.xml edited to my ID allows real dash to see data from either adapters. Also can view data in can monitor. Change to the Holley: HP Dominator & Terminator X option from the list and there’s no data in real dash and timeout on the can monitor.
That just does not make any sense to me 
CAN Monitor does not load nor use the XML in any way.
I can create a video this evening if you want.
Please do, it may help me understand what is going on.
Thank you for the video, this will clarify the issue for me 
We do not have an actual Holley ECU to test on, we use CAN simulator; on which its working fine. I will try to build more of the same setup that you have with two connections and try to re-produce this issue.
It could be that we miss the 2.5.0 release, as there are so many good fixes pending that I do not want to wait much longer.
I’m fine with using the old xml as a work around.No reason to hold up fixing other issues on just my behalf.
Here’s a thread on another forum that has a lot of related info in it. Also post #16 has their simulator they used to mock up a holley canbus output.
Was that a ratchet shifter I heard you rowing? LOL