Devo f12e fpv stops working after deviation

Hello guys, after installing any of the latest nightlys of deviation the fpv of the devo f12e freezes when i connect to the frequency my 5.8ghz transmitter is broadcasting. I would report this as a bug but www.deviationtx.com/mantisbt/login_page.php does not let me log in even though I have an account here. Ive tried this on 3 different f12e and they all have the same problem so I am 100% sure that the problem is the firmware. So right now I will tell you exactly how to reproduce the bug which happens every time you connect to the frequency your 5.8ghz transmitter is broadcasting. So first i turn on my fpv transmitter, then i turn on my devo, go to the menu for fpv, set the switch for turning on fpv, turn on the switch, scroll through the channels to the one my fpv is broadcasting, and when i get to it the devo freezes completely will i turn it off and turn it on. At the moment deviation is making the devo f12e and fpvless controller. Please fix the bug as i have 2 other friends who own f12e. Awaiting a prompt response.

please keep in mind that all of the developers that contribute to deviationtx are volunteers who give their time/expertise freely to the project. while i'm sure that if one of them has an f12e in hand they will look into the issue as/when their free time allows, but i'm also sure the guys have lots of other projects/interests to work on with said free time so i'd suggest the best plan of action is to have a bit of patience, not "awaiting a prompt response"

Bonemaster please tell me a little more what you are doing to have this issue.

I have no problems with the 5,8 video transmitter

I turn on my fpv transmitter, turn on the devo f12e, go to the frequency my fpv tranmitter is broadcasting and there the image freezes and slowly turns to grey. I have 2 other friends that have this same problem on their f12e so I'm sure that its the deviation firmware that causes this problem. When i reflash walkeras firmware i have no problems with the fpv freezing. You probably have a different deviation firmware that is not up to date, any way you can post your versions so i can download it?

Prepare for lots of ridiculous F12E questions as some freaking idiot from walkera got on Rcgroups today and told everyone how the "people over at deviation now have their FW running on the devo 12e and F12E"

I will look into it when I have time and energy. I have the same effect on my F12E, but as I bought it defective and replaced LCD I can't make it work good enough with stock Walkera firmware either, so I have no ground point. I need to make more experiments with it.

If someone has info on exact point in time when it worked, it would help. Someone mentioned specific version - it does not exist neither on GitHub nor on Bitbucket.

Vlad i just tested the version you attached and it has the same problem. Screen freezes when i hop on the channel my 5.8ghz transmitter is broadcasting and then slowly turns to a grey screen. If anyone has any other versions them I'm willing to test them. Will be getting on here once a day to check.

OK, I plan to load all Walkera F12E firmware versions we have and see will it restore my F12E to reasonable state. If it will, I'll trace real exchange over I2C with the video chip - may be we're initializing it incorrectly, or it requires tune-ups.

Alright, that would be great, I wish someone had an older version of the deviation firmware. Maybe have an area where old nightlys are stored so that way when we have these types of problems we can have other firmwares as backup to see if the problem always existed or if the bug was introduced at one point.

Vlad you are the boss man, that versions fpv worked. I hope this reference point helps out the newer versions fpv

That version doesn't let me create new models but as a reference point its great.

I guess but you say on newer F12e transmitter. So do you mean the older version of the F12e doesnt have this problem? My friends F12e is very old, most likely one of the first ones that came out and his still has the same problem.

Approximately how long would it take to fix this?

These changes did something, they're not arbitrary. We can't just revert them - we need to integrate useful changes. We need people for whom Deviation works on F12E now, I suspect that they have newer hardware. We need to keep it working for them also.

I can revert these specific changes and test on my (supposedly older) F12E. It does not mean that it starts working for everyone.