Hopefully there is an APP and some new firmware for the x36s in the works. Expectation of that long promised APP is the only thing keeping me from selling the 536. And based on complaints from others who applied the last (only) firmware update to the 436, I haven't (never found a need to say that for any other radio in the past - until now).
So two simple questions (and only UPMan need reply since the rest of your don't know)
1. Will we ever see that long promised APP?
2. Is there a firmware update coming anytime soon for either the 436 or 536?
I don't expect to receive an answer ... but I'm asking anyway.
We should retitle this thread "Questions Paul Can't/Won't Answer" LOL...
For the firmware update, I'd say we're probably going to see one soon. The HP-1 just got an update recently, so we x36 owners can't be too far behind for the fixes and features we've been waiting on.
As for the app, that mess is currently back in the laps of the dongle manufacturer with no ETA for a fix that Paul can share with us - that's all the info anyone here has,
including Paul. What would be better anyway, to wait for an app that WORKS or release one that has known issues? We all saw the fecal-to-fan that happened when the scanners were sent out with stuff not working. Can you imagine the backlash over an APP that also has problems? I don't blame Paul for not wanting to even respond right now given the absolute mess this has been. Besides, what can he say that we don't already know? It's not like he's building dongles in a back room somewhere or writing firmware updates himself. He's literally waiting on someone else to finish the work, just like the rest of us.
If you really want an update on the app, find out who makes the dongle and ask them for an ETA. Maybe if they start getting inundated with emails from angry Uniden customers, they'll take notice and try to fix the damn things sooner.
If I had the money, I'd buy a 536 right now and start working on my own app for it. What if the dongle isn't really the issue? I've worked with plenty of developers who insisted that something was happening because of a hardware failure, and in reality it was a bug in the software. In another instance, the hardware was causing the problem because we were asking it to do something it couldn't, so in the end we were able to work around it in code and ask the hardware to do something it
could do. Has anyone here tried tinkering with that dongle to see what can be done with it?
-AZ