Kudos to you Wes

[VA2WE]

Good morning Wes,

 

I just discovered your App RepeaterPhone.

 

Fantastic!

 

I t works with the Inrico B2 Speaker Mic as well. Marvelous audio as well.

 

I will make sure I spread the word to all of my ham buddies using iPhone and Allstar-Echolink.

 

I had your app work super well on my iPhone (latest firmware).

 

I have programmed favorites but for some reasons, when I try to connect to 2 different favorite repeaters, the App crashes.

 

What do I need to do to correct this?

[VA2WE]

Please disregard. Was a programming issue with one node. Working A1.

[VA2WE]

Wes,

I realize that what makes RepeaterPhone crash is -sometimes, not always- the usage of my Inrico B2 speaker Mic.

Can you confirm that RepeaterPhone is compatible with the Incirco B2 speaker Mic?

I  am willing to help with data colelction if it can help ypu.

Thank you.

[Weston Bustraan]

What you are likely experiencing there is a known bug with Bluetooth connections in iOS. 

A simple explanation of what happens is this:

- RepeaterPhone asks the OS for the sampling rate of the active audio device.

- Let's say it returns 48KHz

- Armed with this information, RP attempts to start an audio session using 48KHz

- At this point, iOS says "WRONG! That device only supports 44.1KHz. Crash!!"

..... but, but you told me... 

The problem is that, from inside RepeaterPhone, I have no way to determine that the OS is effectively lying and that the value is actually wrong.

This only seems to happen when Voice Processing is enabled, so the workaround is to disable Voice Processing in settings. This has the upside of not crashing, but the downside of losing things like noise cancellation.

Quite often, if you disable Voice Processing and then successfully connect, you can go back in and enable Voice Processing because iOS will have suddenly realized that it had the wrong information and start giving you the correct sampling rate. This is generally why it sometimes crashes and sometimes not.

- Wes W8WJB

--
You received this message because you are subscribed to the Google Groups "repeaterphone-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repeaterphone-u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repeaterphone-users/1836a3b1-7559-41c3-a2f3-04d527574df3n%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Patrick Perdue]

It's worth pointing out that, when a Bluetooth device is connected, noise/echo canceling is then handled by whatever processing does or doesn't exist on that device. The phone doesn't care at that point. Airpods may be an exception, especially considering the up-coming changes in iOS18 and subsequent related Airpods firmware, but I'm not sure exactly how that will work.

I point this out, because I know for a fact that my Enrico speaker mic doesn't attempt to do any of this, other than a hard highpass filter on both the RX and TX audio.

If a sound comes in to the speaker, the microphone will acoustically pick it up. Very often, you can instantly tell someone is using Repeaterphone and one of these Bluetooth microphones, because the PTT sound is heard quite loudly at the start of every transmission being picked up by the microphone, as heard from the speaker.

This is one reason I don't often use mine. AFAIK, you can't turn that sound off, and I need a lot of volume in order to hear things not using headphones. The louder your device is, the louder that sound will be when you start transmitting.

To be fair, it is at least not as annoying as the Echolink PTT sound on an Android device. You don't hear this with iOS users, because it doesn't start transmitting until after the sound plays. Sounds a bit like you're being bonked in the head with an empty beer can any time an Android Echolink user not using a headset keys up.

Same goes for any audio that is sent to a node while you are transmitting. It will be heard acoustically through you, because there is no echo canceling on the Enrico speaker mic. This would also be the case if audio processing is disabled, and you use the internal phone mic and speaker, though both RX and TX will be very quiet in this mode. I often use a wired headset with no built-in microphone and the iPhone's mic with processing disabled, and the gain set higher, as I've found this to have the best audio I can get from Repeaterphone, but I acknowledge that most would probably not want to do that.

73

N2DYI

To view this discussion on the web visit https://groups.google.com/d/msgid/repeaterphone-users/CAEeLBeUvLAZxLRNo9P8SYRZRXShenvhxfmQd%2BN1UO2rqcVVU%2Bw%40mail.gmail.com.

[VA2WE]

Thank you Wes for your explanation.

I think that in addition to what you describe, what complicates the process is that the Inrico B2 Bluetooth Speaker Mic uses 2 Bluetooth connections: 1 for Rx and 1 for Tx (see attached capture).

In order to have both Bluetooth connections working at the same time, you need to press the PTT on the Inrico and look for it in the RP menu. Once "B02PTT-0F52" is checked, you can choose which repeater to connect to and achieve full Rx and Tx with the Inrico.

You need both connections for the Inrico to work in Tx and Rx, otherwise only Rx (speaker) and not the microphone (Tx).

As you describe, Wes, sometimes it works and sometimes it doesn't.

But the beauty of it is that when it works, it works really, really well: RP stability and audio quality. It is very handy to have a Bluetooth speaker microphone to work A1 with an iPhone (see attached capture).

So thanks again Wes for bringing RP to iPhone users.

[VA2WE]

Wes,

Is is possible that IO18 fixed this know bug?

I quickly tested it today and seems that this bug was not happening again under iOS 18...

I'll do further testing and shre my results here.

On Friday, June 28, 2024 at 1:36:38 p.m. UTC-4 Weston Bustraan wrote:

[VA2WE]

RepeaerPhone is not crashing anymore with my Inrico speakermic 👍🏻