PMS confused between two Plex Android clients - duplicate X-Plex-Client-Identifier causing havoc

OK, this blows my mind:

I have 2x Mini Neo U1 Android TV Boxes, connected via ethernet. I use the standard version of Android Plex client with the “TV” interface set. Each device has a unique IP address, MAC address, hostname and Plex client name. This problem only affects these two boxes - we have multiple Android and iOS devices in the house that don’t suffer from this issue.

Each plays media just fine streamed from my UnRAID/PMS 1.1.4.2757 server. However if I try and play (different) media on both devices at the same time they effect each other - usually switching the stream on BOTH devices to the same media. This has been happening on and off for months but haven’t had time to pull info together to report.

If you watch the video file I captured of the web interface you’ll see it showing only a single client but switching between two different movies continuously. In the real world what was happening was one client was playing Sponge Box just fine, the other was attempting to play Ghostbusters but sitting at the background art with busy spinner.

When I look at the log (around Oct 02, 2016 11:12:58.725) I find this:

Lounge client - 192.168.0.138 X-Plex-Client-Identifier => e4f515205bfc2ce-com-plexapp-android

Bedroom client - 192.168.0.188: X-Plex-Client-Identifier => e4f515205bfc2ce-com-plexapp-android

So BOTH clients have the same Plex-Client-Identifier

When I look in the transcoding directory there is only a single transcode - it appears that PMS is transcoding two different media for two different clients into the same transcoding directory: plex-transcode-e4f515205bfc2ce-com-plexapp-android-748fd978-743e-4b53-9427-db041f1c6b06

Please feel free to take a look at the supporting info here: drive.google.com/drive/folders/0B74Kimpwe3nYVzRabDRxaWhhcFk?usp=sharing

Thanks Andy, I’ll give that all a go later today. Looking at my backup directory seems like that DB may have been broken for a while - no new backups since July. Real pity to loose watched metadata for that period but I may be able to re-import from Trakt.

Still have exactly the same problem - which I’m assuming is because of the identical X-Plex-Client-Identifier => e4f515205bfc2ce-com-plexapp-android for box Android boxes.

Did this:
I repaired my DB as per: support.plex.tv/hc/en-us/articles/201100678-Repair-a-Corrupt-Database

No longer have any Uncaught exception running threadpool task error messages.

Uninstalled app, restarted, re-installed Plex on each Android box.

Removed all traces of the two devices from PMS / plex.tv and re-authenticated.

Help

suggest you also get both of the android app logs to go with server logs

See https://support.plex.tv/hc/en-us/articles/201573117-Android-Android-TV-and-Fire-TV-Logs

how were the android plex apps installed on the TVs?

I’ve updated the shared Google Drive folder in the OP with logs from both Android media boxes - as mentioned they are Minix Neo U1’s and the app was installed via Google Play Store

In this iteration of testing I had Ghostbusters playing in the bedroom, but was unable to play any media at all in the the lounge due to the dreaded An error occurred while attempting to play this video. Please try restarting both the Plex Media Server and this app

Regardless - both devices continue to claim the same X-Plex-Client-Identifier => e4f515205bfc2ce-com-plexapp-android and a check of the Devices section of the web client only ever shows a single device known (see devices screenshot on Google Drive).

drive.google.com/drive/folders/0B74Kimpwe3nYVzRabDRxaWhhcFk?usp=sharing

Thank you

I am raising this with the Plex Android Development team. It may be something specific on the NEO-U1 devices

any feedback to share @sa2000 ?

@akawoz said:
any feedback to share @sa2000 ?

Nothing yet. I am trying to find out. I suspect it is a problem with the Minix NEO-U1

EDIT: Ignore the below - confirmed as a packaging error for latest PMS version and since corrected as at PMS 1.2.1.2854

Just in case its related (can’t see how) I’ve also got a question on how my Plex Web is very out of step with PMS: forums.plex.tv/discussion/237503/plexweb-2-7-2-but-pms-1-2-1-2854

@sa2000 said:

@akawoz said:
any feedback to share @sa2000 ?

Nothing yet. I am trying to find out. I suspect it is a problem with the Minix NEO-U1

@sa2000 anything to report? Trying to decide if I get rid of one of these because unworkable right now - if only the Nvidia Shield TV devices weren’t so expensive (for us with $NZD)

@akawoz said:

@sa2000 said:

@akawoz said:
any feedback to share @sa2000 ?

Nothing yet. I am trying to find out. I suspect it is a problem with the Minix NEO-U1

@sa2000 anything to report? Trying to decide if I get rid of one of these because unworkable right now - if only the Nvidia Shield TV devices weren’t so expensive (for us with $NZD)

Google documentation on the Android Device ID

 * A 64-bit number (as a hex string) that is randomly
 * generated when the user first sets up the device and should remain
 * constant for the lifetime of the user's device. The value may
 * change if a factory reset is performed on the device.

So the advice is to see if resetting one of the devices (Factory Reset) would get it to pick a new Device ID

If the Device ID remains the same after the factory reset then your only option is to take it up with device vendor

@sa2000 anything to report? Trying to decide if I get rid of one of these because unworkable right now - if only the Nvidia Shield TV devices weren’t so expensive (for us with $NZD)

Google documentation on the Android Device ID

 * A 64-bit number (as a hex string) that is randomly
 * generated when the user first sets up the device and should remain
 * constant for the lifetime of the user's device. The value may
 * change if a factory reset is performed on the device.

So the advice is to see if resetting one of the devices (Factory Reset) would get it to pick a new Device ID

OK, you’re onto something here - just went to the play store via web to install a piece of software to allow me to see the device ID from the device itself and i noticed this:

There’s only a single Minix device listed there - assuming because they have the same Android ID. Will try the factory reset now and report back

OK, I’m pleased to report that a factory data reset resulted in one of my Minix Neo U1’s getting a new Android Device ID. This appears to have completely solved my problem. Each device now has a unique ID.

Will contact the Minix guys and see if this is known. Thanks for everyone’s help. Marking as answered.