Closed GoogleCodeExporter closed 9 years ago
Other users have reported this too. It does not seem to happen to everyone
though as I cannot reproduce it. So there must be some trick to why it forces
repairing every time for some users but not others.
Original comment by mellowaredev
on 18 Nov 2011 at 2:32
my brother has the same issue with foo_remote win7 tmobile g2 2.3.3
Original comment by DeviantV...@gmail.com
on 1 Dec 2011 at 4:28
This happens when TunesRemote+ attempts to connect to a library with the wrong
GUID (code). Once it fails to do so, it asks the user to pair again.
Once the pairing is complete, the app will not update the GUID in its pairdb,
thus it will fail again next time.
Attaching possible patch to fix this issue, tested as working.
Incidentally, this was the result of another issue:
Using two similar devices (2 x Samsung I9100), whenever one pairs with iTunes -
it ends up overwriting the other's record in the iTunes DB, thus requiring an
endless cycle of re-pairing each device.
Had no time to look into this one beyond trying to:
1. Change the 'pair id' from 0000000000000001 to something unique - no go.
2. Change the device/remote name to something unique (both in RemN and
PAIRING_RAW) - also no go.
Original comment by oefr...@gmail.com
on 24 Dec 2011 at 2:33
Attachments:
Thanks for the patch! I have applied this and released TR+ 2.4.2 on the
Android Market.
If all goes well we can close this ticket!
Original comment by mellowaredev
on 24 Dec 2011 at 1:44
Android updated (although 'About' shows 2.4.1)
But now it is all working fine.. no requirements to re-pair
Thanks
Original comment by richard....@gmail.com
on 3 Jan 2012 at 10:51
Awesome! I forgot to update the about screen thanks for the heads up!
Original comment by mellowaredev
on 3 Jan 2012 at 11:25
Original issue reported on code.google.com by
richard....@gmail.com
on 18 Nov 2011 at 2:30