Could an Android TV App Change IPC-Color4K-T Camera Settings???

Let me explain what happened. I currently have three IPC-Color4K-T cameras that I view on a TV using an Android tv dongle running the TinyCam app. I have the second sub stream (1080p) enabled on the cameras and use that feed with the TinyCam app. In TinyCam I have the channel set to "3" to get the 1080p stream. Been working like this for over a year on multiple Android tv devices. A few days ago I decided to try some different Andriod TV apps for streaming the camera video. Specifically StreamShow and Onvier. If I remember correctly, one of those apps uses RTSP (and possible ONFIV) and the other offered both ONVIF and a Dahua connection. I added my "Front" cam to one of the apps and both my "Front" and "Driveway" cams to the other. After trying both apps I decided that neither was an improvement over TinyCam and uninstalled the apps.

The problem: I went to pull up the cameras on my TinyCam setup and was having issues with the "Front" camera feed. I then tried TinyCam on a different tv with my "high power" NVIDIA Shield running TinyCam and same issue. I eventually discovered the issue. In TinyCam I switched the feed channel from 3 to 1 on the Front camera and the feed started working. Somehow using TinyCam channel 1 became the 1080p feed and channel 3 became the 4K feed which is too much for TinyCam on the dongle to handle. The Driveway cam was unaffected. I had to swap channels on all of my TinyCam installations on multiple devices. I also use Blue Iris but those feeds were unaffected perhaps due to how BI gets the feed. I've rebooted the Front camera and gone through all the settings looking for something that might have been changed but couldn't find anything. Perhaps I didn't look in the correct location??

Any ideas on what might have happened and how to fix? I'd like to avoid a factory reset and re-setup if possible. And my OCD doesn't like having to run that one camera on channel 1 vs 3 on the other IPC-Color4K-T cameras that I use

Yes, I've been in and out of and on every page of the camera's webGUI (using IE) and have even opened up the GUI of one of my other Color4K-T cameras in a second browser window and compared the settings side by side and they are identical. This has me stumped!

To add some context in relation to TinyCam. The setup in TinyCam is fairly basic. Just enter IP address, select ONVIF camera type, camera credentials, RTSP protocol and select the channel number.

Here are the stream URL's. To reiterate the TinyCam settings, Driveway has "Channel number" set to 3, Front has "Channel number" set to 1.
Front: Stream - rtsp:/192.168.1.52:554/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
Driveway: Stream - rtsp:/192.168.1.53:554/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif

Looking at this it seems like a TinyCam issue but I promise TinyCam was working on 4 devices with the Front channel set to 3. Moments after I deleted those two apps, that were only installed on a single device, TinyCam on a different device started showing the 4K stream with channel set to 3 (I check other devices with TinyCam and they exhibited the same behavior) and after I changed the channel in TinyCam to 1 I got the 1080p stream.

The more I look into this the more it confuses me as to what in the heck happened!

TonyR said:

All stream "channel" numbers should be 1; it's the "subtype" number that determines which stream is used: 0 = main stream, 1 = substream

Click to expand...

I agree and it appears that nothing has changed with the IPC-Color4K-T camera.

TinyCam is using "channel" in it's GUI but in reality it is choosing the subtype.

This doesn't seem to be a camera issue but is strange in that a change made (assumed by one of those other apps) on device "A" is affecting devices "B", "C" etc. I think my original suspicion of a changed camera setting was due to the camera being the device that devices "A", "B", "C" etc. had in common. If only TinyCam on device "A" was affected I'd reset TinyCam on that device but since other TinyCam installs are also affected the issue seems to come from some upstream change which originally led me to a camera setting. Still stumped.