- Joined
- Jan 9, 2018
- Messages
- 637
Sorry, didn't see the messages. I put _1559 back online. You can recover. Try holding the button for 30 seconds instead of 10. This will erase all flash and start the bootloader mode. If you really hit your limit, then email me for a no-hassle return. I feel bad about this one. I used to blow up at my guys when they pulled a stunt like that. I guess this is payback for trying to get something done at the last second.I think I may have hit my frustration limit here.. sorry Todd.
If you really hit your limit, then email me for a no-hassle return.
That is an excellent question sir! I only sell NEW units to people. If someone returns a unit to me, I add it to my collection of black-case units that I use for testing. In two cases, I sold used units offline to someone for an even more incredible deal than normal pricing. I have paid for shipping on every case of repair/return so far, even if it didn't really need repair (most cases). My goal is to be the best I can be at making EVERYONE satisfied that they purchased something from me. I doubt you will find anyone that disagrees with that. It might be the end of me, but that is the way I will continue to do things.@btt This is off topic but the above presented the opportunity. How are you handling devices that may be returned to you? Meaning, if and when I decide to place an order for a P25RX, I would like to think I am getting a unit that has only been in your hands and not the potential to get the unit @Cheeseburgers returns.
That is an excellent question sir! I only sell NEW units to people. If someone returns a unit to me, I add it to my collection of black-case units that I use for testing. In two cases, I sold used units offline to someone for an even more incredible deal than normal pricing. I have paid for shipping on every case of repair/return so far, even if it didn't really need repair (most cases). My goal is to be the best I can be at making EVERYONE satisfied that they purchased something from me. I doubt you will find anyone that disagrees with that. It might be the end of me, but that is the way I will continue to do things.
...People have to keep in mind that this is a living process that they are participating in. More firmware updates and enhancements have went out for this device in a short time period than any other manufacturer would even begin to think about...
up and running, I think I notice not missing the very start of the conversations with this version. but need to hear more.Version _1930 still going strong here without any issues. Please consider this a "stable" version and test. Let me know if you find any major issues (other than scanning related. I will work on improving scanning soon).
v 3-7-1930 I take it back. When on a system, it seems to take a 1/2 second or so to ID the TD and start audio, missing the very start. I can hear the full start on the SDS. I though it was because it was roaming on another system but I watched it for a couple TXs and it was on the system with the TX,. Delay seems on be on both the PC and BT audio. Once the TD has been identified the full response is heard. Its just the start of the initial TX that is missed.up and running, I think I notice not missing the very start of the conversations with this version. but need to hear more.
Running on a powered USB hub on the port which was giving issues yesterday, No garbage character issues with the powered hub on line. save the initial audio delay,Not your fault : ) That is on me.
--------
Results from today:
Based on today's experience, I am starting to come to the conclusion that some USB host ports will not allow more than 500mA peaks in USB 2.0 mode, even if they are capable of supplying more than 500mA current and the average current draw is less than 500mA. With the latest version (2021-03-07_1559), If you enable Bluetooth and you see garbage characters in the console and the console information stops, then you are experiencing this issue. You will need to use a different port or you can use a powered USB hub that will supply more current. This unit is similar (but different) to the one that I experience no issues with: https://www.amazon.com/AmazonBasics-Port-2-5A-power-adapter/dp/B00DQFGH80 Again, I'm not 100% sure that this is the issue and there may still be a firmware resolution possible.
While trying to figure this issue out, I believe many improvements were made to the firmware and software with regards to USB communications. Everyone should install the new "latest stable" version: 2021-03-07_1559. Let me know if you find any major issues (other than scanning related. I will work on improving scanning soon).
2021-03-08_0546 is available. This version has the voice-audio buffering delay set to the value recommended by the standards (from what I recall). The delay you are hearing may be due to issues with scanning. The scanning mode needs more work.v 3-7-1930 I take it back. When on a system, it seems to take a 1/2 second or so to ID the TD and start audio, missing the very start. I can hear the full start on the SDS. I though it was because it was roaming on another system but I watched it for a couple TXs and it was on the system with the TX,. Delay seems on be on both the PC and BT audio. Once the TD has been identified the full response is heard. Its just the start of the initial TX that is missed.
Can you give me an idea of what it is doing? Does it transfer the firmware?No luck with the method you sent in your DM or the 30 second method Todd, sorry to report.
Can you give me an idea of what it is doing? Does it transfer the firmware?
Which version are you loading?Okay got it to stop doing that... now it is just saying that the firmware is not up to date, and keeps cycling..
When you load the recovery firmware I sent a link to in the DM, does it load all the way and set the leds on?_1559