The State of Affairs and Apps

Ok, so just got done with another night of extensive testing and researching about the problems with our new custom broadcast app….

As a review, we had no problem broadcasting from our Samsung S10 using our custom app USING ANDROID version 11. The exact time that we got the Android 12 version, that is when the bad audio clicking happened.

We have been trying to solve the problem. Two different developers have tried to duplicate the problem but they don’t have any devices that have updated to Android 12 yet. So, we have been doing plenty of test steams using a variety of devices and different apps. BTW, thanks for your patience during the many brief tests….

Ok, BEFORE we updated to version 12, we were able to stream using streamlabs, Youtube app, and our own app. Using the S10 with Android 2, and the Youtube android app, we can stream but get no audio at all. same with our own app. so the developer gave us a special developer app to stream directly to him, and no sound at all. Yes, I did check the mute buttons. I did also go in and check permissions to YouTube app and it shows camera, microphone, and location was enabled and allowed. The same with our custom app. and the developers app. It makes no sense that since 12 came out no audio can be streamed at all, but no sound issues with streamlabs, and if we use our own app audio is heard but with clicking. this obviously ISN’T an issue with my microphone or phone. Yes I checked everything with the external microphone both plugged in and out.

Want to help us figure this thing out? IF you have an android device that has been upgraded to Android 12, try a simple live stream to your YouTube channel using the YOUTUBE app. Try streaming with another broadcast app. Do you get any audio? is it clear? Or does it have terrible clicking like our custom app does? Try and test it out on your android 12 devices. Let me know your phone model, what streaming app you tested, and if you had audio issues or not. Be sure to test using the YouTube app. It very well could be a coding issue on YouTube’s side as well!