search

abhay123lp / tunesremote-plus

Automatically exported from code.google.com/p/tunesremote-plus
0 stars 0 forks source link

Foobar2k Pairing failure: Xperia Ray #77

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Q. What Android hardware device do you own?  (HTC Hero, Samsung Galaxy,
etc)

A: SonyEricsson Xperia Ray (ST18i) 

Q. On what Android operating system version? (2.1, 2.2, Honeycomb 3.0.1
etc)

A: 2.3.3, stock rom (rooted)

Q. What DACP server, OS, and version? (OSX iTunes 10.1.2, Windows 7
MonkeyTunes 1.5.1 etc)

A: Windows 7 / foobar2000 1.8.1 / foo_touchremote 0.2.7.2

Q. What TunesRemote+ version? (found on Menu->More->About)

A: No 'About' in the menu, but 2.4.1 according to App Store

Please provide any additional information below.

Pairing starts off good.
Finds the library.
Gives me the code.
Code is accepted.
According to fb2k console, pairing is successful - "TouchRemote: Successfully 
paired"
... wait a few seconds, and TunesRemote+ presents me with the code again :(

Among your payware competitors, 'iTunes Remote: Android' also fails,
while 'Remote for iTunes' succedes.

Firewall opened as per FAQ, router is some kind or another of recent Airport 
square brick. I gave it a firmware update a month or so ago.

Original issue reported on code.google.com by L.Valeri...@gmail.com on 22 Sep 2011 at 12:39

GoogleCodeExporter commented 8 years ago 
My guess is it might be a problem with FooBar plugin itself.  Because I test 
against MonkeyTunes and iTunes successfully before every build.

Might want to contact the Foobar developer and ask him to test TunesRemote+ 
against his server so he can debug.

Original comment by mellowaredev on 22 Sep 2011 at 2:36

GoogleCodeExporter commented 8 years ago 
Have you carefully read TouchRemote FAQ and set port to 3689 as it is stated 
there?  TouchRemote uses port 7000 by default, and not all clients take 
announced port number into account.

Original comment by PieceOfS...@gmail.com on 22 Sep 2011 at 2:45

GoogleCodeExporter commented 8 years ago 
marking this as WontFix as the suggested fix above was most likely the issue.

Original comment by mellowaredev on 6 Nov 2011 at 3:58