llzel
Newbie
Yes MOSWIN AND SLATER and no alasesI'm a little too far to get anything on the MOSWIN. Is that what you're listening to?
Yes MOSWIN AND SLATER and no alasesI'm a little too far to get anything on the MOSWIN. Is that what you're listening to?
What is the result of "verify installation" when you check it?My current issue is that I cant even get the firmware to load onto my G5 after restoring the factory firmware in an attempt to reload the OTA firmware. I am beginning to think that it was never actually correctly loaded onto my device, even though it claimed to be successful and passed the verification. What leads me to think this besides the fact that i never received any OTA ID's on 2 systems known to have OTA Id's, is the fact that out of approximately 6+ attempts, it only was successful once. The initial attempt failed, the second claimed to be successful and all further attempts have also failed. I have tried both the Repair function and Restoring and re-installing the firmware, and haven't been able to have a successful install since.
Verification failedWhat is the result of "verify installation" when you check it?
ya no wonder it's not decoding anything... So in recap, you did a restore to 2.05....then verified the pager was going to qualify for the software, then tried to load it and what happened? did the install complete? Did you wait and leave it plugged up until it fully rebooted or?Verification failed
Preflight failed: full-ring tap is not loaded.
The install had successfully completed on my second attempt. It was reading as being successful and verified successful as well. After running for around 12 hours on one system and 6+ hours on another system, both with confirmed OTA Id's, the pager was still not displaying any.ya no wonder it's not decoding anything... So in recap, you did a restore to 2.05....then verified the pager was going to qualify for the software, then tried to load it and what happened? did the install complete? Did you wait and leave it plugged up until it fully rebooted or?
My first attempt failed (for some reason)but then I redid it all and it took the second time. What generation of G5 do you have?
What file do you need once I run this on my G5+ pager? Any what's the best way to get it to you? Thank you for your efforts with thisThis is a tool that you can run on the G#N and G#+ (If they are in fact different) and send me the report so I can make sure this works on those as well. I need a few reports so that I can get a broader overall "look" into the hardware. This is a read-only tool and makes no changes at all to the radio. The more I get the better.
This is only needed for those newer models, not the original hardware G4/5 "A" series.
My model number is exactly the same as yours. Below it I am showing: UNI-0001-190510Let's see these two screens.....
No that's ok. Shouldn't make a difference I just enclosed that to verify the 2.05 firmware.My model number is exactly the same as yours. Below it I am showing: UNI-0001-190510
For the firmware mine is also showing V2.05, and the Serial number is AG5V96****.
I know it wont, but if it makes a difference obviously i can give the full serial number.
Man I don't know what to tell you. When you try and load it do you have some logs pop up that showed what happened when you tried to load it ? I ended up with several on my desktop. I know you don't want to join the telegram thing and I didn't either but I went ahead and did it. If those logs are there maybe that might help.My model number is exactly the same as yours. Below it I am showing: UNI-0001-190510
For the firmware mine is also showing V2.05, and the Serial number is AG5V96****.
I know it wont, but if it makes a difference obviously i can give the full serial number.
And you're running the file in post 15 correct??Verification failed
Preflight failed: full-ring tap is not loaded.
Has it been determined this will work on the G4?? You may be the test case.my g4 updated to 2.05 fine and the alias software installed successfully and was verified yet no alias dhows up just numbers. Missouri MOSWIN and SLATER
Not a problem, we tried. Fighting through issues is part of the fun of experimenting. Just like when Todd was working on the P25RX and the Micro, I'm always willing to contribute with breaking things in order to make for a more stable final product.Man I don't know what to tell you. When you try and load it do you have some logs pop up that showed what happened when you tried to load it ? I ended up with several on my desktop. I know you don't want to join the telegram thing and I didn't either but I went ahead and did it. If those logs are there maybe that might help.
Yes, that is the one.And you're running the file in post 15 correct??
Not a problem, we tried. Fighting through issues is part of the fun of experimenting.
I had both, and neither worked. Both systems were set to Trunking Monitor. I have talkgroups with confirmed OTA equipped radios that were named and added to the scanlist, and some that were not included, that display as the Talkgroup number only, and i wasn't receiving Aliases from either.Just curious, as I'm noticing something on mine, but how are you listening to the traffic, as monitor/wild card traffic or as assigned TGs?
One thing I've noticed to is if I have a TG defined it will show the alias (most of the time), but if I do not have it defined when running a wildcard (65534) or monitor talkgroups I have not seen an alias displayed, maybe coincidence but...
It is working perfectly on my G4.Has it been determined this will work on the G4?? You may be the test case.
I’m not the author, but it appears this mod lets the pager decode talker aliases from calls it actually receives. It shouldn’t matter how the call is received (wildcard scan, TG monitor, or TG scan), as long as the pager receives a live transmission from a radio that’s sending an alias. The alias usually isn’t complete until late in the call, so it won’t show on the transmission that delivered it. The next time that radio keys up, on any TG you’re receiving, the pager should display the alias instead of the radio ID.May be hit and miss. This is from a non assigned TG in wild card scan.