Can't pair with Itunes using HTC Desire /android 2.2

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Manually enter IP address. 
2. Code is presented in tunesremote. 
3.No devices show up in Itunes. 

What is the expected output? What do you see instead?

Expect Itunes to ask me to enter the code that was presented in tunes remote. 

What version of the product are you using? On what operating system?

Using android 2.2 and Itunes in osx. 

Please provide any additional information below.

Original issue reported on code.google.com by ste...@gmail.com on 26 Sep 2010 at 8:34

[GoogleCodeExporter]

It is a known issue that is a bug in the HTC Desire WIFI driver in Android 2.2.

Long explanation is here:

http://code.google.com/p/android-cookbook/issues/detail?id=8

It works on all other Android hardware except so far the HTC Desire and 
possible Evo 4g.

Specifically this post...

I now have 3 "devices" I'm testing from against iTunes 10: (I'm a glutton for 
punishment)

Android Emulator on the PC w/ iTunes 10: Sends/receives mDNS packets and can 
see the iTunes 10 library (from the local machine).

HTC Hero (CDMA): Sends/received mDNS packets and can see the iTunes 10 library.

HTC Evo 4g: Sends but does not receive mDNS replies.

HTC Desire 4g: Sends but does not receive mDNS replies.

My earlier captures do show a slight difference in packets between the iPod 
Touch and the Evo in the transmission, but given the same build was running on 
the Hero, I may have been in error early pointing at JmDNS. (For that I 
apologize - and unfortunately I don't have the captures handy.)

At this point I have confirmed the wireless driver on the Evo does indeed 
filter packets not unicast or network broadcast to the phone. Multicast on the 
Evo is not going to work out of the box. I'm currently looking at the CM kernel 
which has some patches around the filtering on the wireless driver but that's 
another story...

Speaking to the original post, failure on the HTC Desire - The Desire and Evo 
share the same wireless chipset, and, though I haven't confirmed it via kernel 
source, I would expect the same driver implementation and filtering.

My apologies on taking the long way around this bug but at this point, the 
failure to get the library to appear on the Desire / Evo does appear to be 
OS/Build related, and not software related. (Later problems of failing to pair 
w/ iTunes 10 is an entirely different issue.)

Original comment by mellowaredev on 27 Sep 2010 at 12:33

• Changed state: Accepted

[GoogleCodeExporter]

The previous incarnation of tunes remote (minus) worked fine with the same 
device/computer.

"HTC Desire 4g: Sends but does not receive mDNS replies."  --After manually 
entering the IP address of the computer into Tunesremote(plus) on the HTC 
desire device nothing appears on the computer.  This doesn't seem to be more of 
a  problem of sending mDNS on the device...and this was not the case with 
Tunesremote(minus).

Original comment by ste...@gmail.com on 27 Sep 2010 at 6:52

[GoogleCodeExporter]

I opened this ticket with the JmDNS team.

http://sourceforge.net/tracker/?func=detail&aid=3059323&group_id=93852&atid=6057
91

Original comment by mellowaredev on 27 Sep 2010 at 10:27

[GoogleCodeExporter]

I just uploaded v 2.0.2 to the Android market can you download and try it.  I 
reverted back to JmDNS 2.0 which appears to have fixed the pairing issues.  can 
you try and let me know?

Original comment by mellowaredev on 28 Sep 2010 at 5:04

[GoogleCodeExporter]

it seems to pair fine now!

Original comment by ste...@gmail.com on 28 Sep 2010 at 8:36

[GoogleCodeExporter]

I just downloaded v2.0.2. Using monkey tunes 
(http://melloware.com/products/monkeytunes/) now I'm able to see device (HTC 
Desire 2.2) in MediaMonkey. As soon as I pair device app again propmts another 
pair screen. Also device id in mediamonkey changes and pairing window is again 
showed. I hope this could be helpfull to resolve this issue. I paired manualy. 

Original comment by mrese...@gmail.com on 28 Sep 2010 at 9:39

[GoogleCodeExporter]

are you sure you entered 5309 as the pairing code?

If not do the Manual steps for MonkeyTunes listed here:

http://code.google.com/p/tunesremote-plus/wiki/MonkeyTunesInstructions

Original comment by mellowaredev on 28 Sep 2010 at 10:13

[GoogleCodeExporter]

Stelb hopefully you won't mind doing a quick Android Market review of 
TunesRemote+?

Original comment by mellowaredev on 28 Sep 2010 at 10:14

[GoogleCodeExporter]

Hi
I've Managed to connect my HTC Desire (Froyo) with Itunes using Tunesremote+
At first I tried using 0000 as Code but of course was then promted with 5309 as 
code. 
Also i entered that code before connecting in the itunes-settings under 
Sharing-> password. Not sure if that helps anything. Anyway when I used 5309 as 
code it immediately showed up in iTunes and accepted 5309 as code. Now even 
Playlists and searching also works. Really great work you Guys who took over 
the project. 
I just noticed that when you're searching for something and it returns some 
results it still prints "No search results found" underneath. 

Original comment by b.wuerk...@gmail.com on 28 Sep 2010 at 10:39

[GoogleCodeExporter]

I will fix that bug with the No Results Found issue.  Glad you like it, don't 
forget the Android Market review!

Original comment by mellowaredev on 29 Sep 2010 at 12:50

[GoogleCodeExporter]

hi should the problem 'mresetar' reported (endless try to pair with desire 
android 2.2) be fixed ?
cause i've just the same problem

Original comment by flying.d...@gmail.com on 29 Sep 2010 at 9:30

[GoogleCodeExporter]

The Desire is the one with the WIFI driver chipset issue described in this 
thread...

http://code.google.com/p/android-cookbook/issues/detail?id=8

Look at all of brian.rozmierski posts he dug really deep into this on his HTC 
Desire and found the root of the problem.

Original comment by mellowaredev on 29 Sep 2010 at 10:38

[GoogleCodeExporter]

Hi, as i wrote I paired manually. I tried to pair with code "1" as instruction 
said. Also I have tried 5309 as pairing code numerous times. Maybe this is HTC 
desire issues but in comment No 9 someone did it together with iTunes. Maybe 
some wifi fix app could help? 

Original comment by mrese...@gmail.com on 29 Sep 2010 at 12:00

[GoogleCodeExporter]

Pairing Manually with the code "1" only works in MonkeyTunes.  If you are using 
Itunes use this code...

0000000000000001

It has to be 16 digits with at least 1 number not 16 0's.  try that!

Original comment by mellowaredev on 29 Sep 2010 at 1:00

[GoogleCodeExporter]

Did it work for someone with the desire on 2.2? At least for me it doesn't, no 
matter what I enter as a pairing code. I'm kind of stuck in the pairing 
procedure.

Original comment by ben.wi...@gmail.com on 4 Oct 2010 at 4:18

[GoogleCodeExporter]

i also had this problem with 2.2.   kill tunesremote with taskkiller, clear the 
list of remotes in itunes, and then start over.  that seemed to work for me.  

Original comment by ste...@gmail.com on 4 Oct 2010 at 4:32

[GoogleCodeExporter]

Doesn't work for me. I also tried reinstalling TunesRemote and iTunes, with no 
success. tcpdump shows that iTunes responds to pairing request with "503 
Service Unavailable":

GET /login?pairing-guid=0x5309 HTTP/1.1
viewer-only-client: 1
User-Agent: Dalvik/1.2.0 (Linux; U; Android 2.2; HTC Desire Build/FRF91)
Host: 192.168.2.2:3689
Connection: Keep-Alive

HTTP/1.1 503 Service Unavailable
Date: Mon, 04 Oct 2010 17:15:42 GMT
DAAP-Server: iTunes/10.0.1 (Windows)
Content-Type: text/html
Content-Length: 3

Same result with a different code (0000000000000001).

Original comment by pecnika...@gmail.com on 4 Oct 2010 at 5:20

[GoogleCodeExporter]

@pecnikales: Did you activate remote controlling in iTunes? Otherwise i can't 
understand this answer

Original comment by b.wuerk...@gmail.com on 4 Oct 2010 at 7:30

[GoogleCodeExporter]

You should always use a 16 digit code when pairing with Itunes like 
0000000000000001).

But yeah the 503 is bad.  It means the Itunes web server is running but it 
denied that request.

Original comment by mellowaredev on 4 Oct 2010 at 8:31

[GoogleCodeExporter]

I finally made it work - I ran iTunes as administrator, then paired it with 
TunesRemote+. (Using Win 7, 64 bit)

Original comment by pecnika...@gmail.com on 4 Oct 2010 at 9:19

[GoogleCodeExporter]

Sweet!   Although that is definitely an odd fix as Itunes shouldn't need Admin.

Hope you enjoy TunesREmote+ and do a review on the Android Market!

Original comment by mellowaredev on 4 Oct 2010 at 9:28

[GoogleCodeExporter]

I'm also having the same problem with any code.  I tried all the suggestions 
here but no fix.  It worked before I upgraded to get the playlist option 
working, now can't connect at all.

Original comment by randomut...@gmail.com on 13 Oct 2010 at 11:55

[GoogleCodeExporter]

Did you try the Manual pairing where you enter your IP address and then a 16 
digit pin like 0000000000000001?

Original comment by mellowaredev on 13 Oct 2010 at 11:57

[GoogleCodeExporter]

It worked for me. Htc Desire 2.2
As Pairing Code I Used "0000000000000001", and put 5309 as pairing code on 
itunes and as sharing password on Itunes preferences 

Original comment by ppass...@gmail.com on 16 Oct 2010 at 3:54

[GoogleCodeExporter]

I'm trying to pair my Desire (Froyo) with Mediamonkey. After entering the local 
IP manually and using 1 as pairing code, the device appears in MM. But the code 
shown on my Desire is always 0000. When I enter it in MM, the window showing 
this number will pop up again on my phone.

I guess the connection between phone and MM works but there's a problem with 
the codes...

Original comment by domenico...@gmail.com on 18 Oct 2010 at 8:51

[GoogleCodeExporter]

 domenico.paonessa if it shows 0000 then you are using TunesRemote and not TunesREmote+.   TunesRemote+ will show 5309 in that window and not 0000.

Original comment by mellowaredev on 18 Oct 2010 at 10:35

[GoogleCodeExporter]

Issue 11 has been merged into this issue.

Original comment by mellowaredev on 15 Nov 2010 at 3:17

[GoogleCodeExporter]

Issue 13 has been merged into this issue.

Original comment by mellowaredev on 15 Nov 2010 at 3:17

[GoogleCodeExporter]

I just uploaded 2.0.5 to the Market with a new Bonjour implementation.  Can you 
guys test and report back?

Original comment by mellowaredev on 16 Nov 2010 at 12:46

[GoogleCodeExporter]

Awesome! My HTC Desire connects to iTunes 10.0.1.22, and can fully control it. 
BUT, it is still having problems connecting to foobar with foo_touchremote 
component, which is the main reason I would use this app :(

Original comment by brooks...@gmail.com on 16 Nov 2010 at 2:15

[GoogleCodeExporter]

booksaar for that you need to contact the foobar developer directly.  Because 
this has been tested thoroughly against iTunes and MonkeyTunes so foobar must 
be doing something different or is actually throwing an error somewhere in a 
log that you are not seeing.....

Original comment by mellowaredev on 16 Nov 2010 at 4:26

[GoogleCodeExporter]

anyone else get a chance to test this with their Desire 2.2 besides brooksaar?  
I would love to close this ticket.

Original comment by mellowaredev on 17 Nov 2010 at 11:43

[GoogleCodeExporter]

Hi. I can connect to itunes manually but have input the ip address
every time I want to reconnect.

Original comment by r.floydw...@gmail.com on 18 Nov 2010 at 7:42

[GoogleCodeExporter]

Does your IP change every time you reboot or are you entering that same IP 
Address everytime?  Because once you pair once Itunes stores your device and he 
device stores your itunes and it should reconnect every time after that.   I 
have never seen that behavior in any system before.  When you wake up 
TunesRemote+ it immediately calls /login to the iTunes server with  the 
previous login.

Original comment by mellowaredev on 18 Nov 2010 at 11:37

[GoogleCodeExporter]

Hello, same for me. I have a Desire running Froyo and I must manually input the 
IP every time I want to reconnect. And then the pairing code in iTunes.
My PC always have the same IP: it is set by my internet box (checks the MAC of 
the NIC).

Original comment by eric.bon...@gmail.com on 22 Nov 2010 at 6:18

[GoogleCodeExporter]

I need to get a hold of one of these HTC Desires because they seem to act 
differently than every other Android device I have worked with or tested on.  
Maybe someone will donate one when they upgrade to a newer android phone!

Original comment by mellowaredev on 22 Nov 2010 at 8:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It looks like there has been quite a bit of debugging to determine that the WPA 
supplicant is the problematic binary.  The problem is that I have the same 
issue with WEP.  I haven't heard anyone mention that so I just wanted to let 
everyone know it's a bit more widespread than just WPA.

Just to make sure that the problem I was observing was the the one described 
above, I decided to remove my custom broadcast discovery mechanism and replace 
it with JmDNS.  I did, and have the same problem, no receiving broadcasts.  

Here are a few details:
Android Version: 2.2
Kernel Version: htc-kernal@and18-2#17
Baseband Version: 2.15.00.09.01
Wireless Security: WEP
Phone: HTC EVO

Original comment by WesGils...@gmail.com on 4 Dec 2010 at 10:28

[GoogleCodeExporter]

Thanks for the update.  I keep getting hammered on Android Market reviews about 
how it doesn't work on some HTC devices and people don't believe me like it 
must be a bug in the code and I keep explaining it is not a bug in the code but 
with the device.

Original comment by mellowaredev on 4 Dec 2010 at 11:13

[GoogleCodeExporter]

Sure thing, if you can, ask your users to open a ticket with HTC using the 
following address:
http://www.htc.com/us/support/e-mail

Please have them reference "UDP broadcast/multicast not functional" and perhaps 
the name of your application.  With some organization, we can get them to fix 
the problem.  Are you aware of other applications that use UDP for device 
discovery?  If so, I'll try to get them to refer their users to htc as well.

Original comment by WesGils...@gmail.com on 5 Dec 2010 at 3:47

[GoogleCodeExporter]

Wes, Basically any app trying to use JmDNS or mDNS service discovery will be 
affected by this bug.  All of my Android apps at Melloware.com use this 
technology so HTC Desire users constantly write me and say it doesn't work!

http://www.melloware.com

I am going to that link you provided right now to submit it.

Original comment by mellowaredev on 5 Dec 2010 at 3:57

[GoogleCodeExporter]

Crossposted from 
http://code.google.com/p/android-cookbook/issues/detail?id=8#c30

As for the comment in #38, the WPA supplicant is active even if WEP is used, so 
the problem behavior is expected.

On to better news, for EVO owners at least, flips Fresh EVO ROM, as of 3.5.0, 
is now working with mDNS. (And thus, TunesRemote). The 3.5.0 mod is based off 
the latest Sprint/HTC OTA update, which gives some home for those running a 
stock ROM. (The OTA is version 3.70.651.1, and may differ slightly depending on 
your hardware version.)

If you're running a stock ROM, and have the OTA (check for Swipe keyboard), let 
us know if TunesRemote is working (or at least finding the library) for you.

Original comment by brian.ro...@gmail.com on 21 Dec 2010 at 9:34

[GoogleCodeExporter]

Great app!
Unfortunatelly, I have exactly the same problem as brooksaar in comment 30 - 
works fine with iTunes, but can't pair with foobar (my main pleer). Phone - HTC 
Desire.

Original comment by volobuev...@gmail.com on 1 Jan 2011 at 10:13

[GoogleCodeExporter]

From other Foobar users I have talked to apparently that Foobar plugin is still 
buggy and has not been updated since Feb 2010.

Original comment by mellowaredev on 2 Jan 2011 at 2:52

[GoogleCodeExporter]

Thank you for quick response.
You are right, it seems Foobar plugin's fault. I've just tried tunesremote-plus 
with MediaMonkey player and MonkeyTunes plugin - works fine, without any 
pairing problem.
It's a pity, that such popular and convenient player as Foobar doesn't have 
reliable DACP plugin. 

Original comment by volobuev...@gmail.com on 2 Jan 2011 at 3:16

[GoogleCodeExporter]

I have had many of my MonkeyTunes users asking about Foobar support if you want 
to read this thread.

http://forum.melloware.com/viewtopic.php?f=16&t=8919

Original comment by mellowaredev on 2 Jan 2011 at 3:18

[GoogleCodeExporter]

foobar developer said he had the wrong version posted on his website.  He asked 
if you Foobar guys could download his latest and try again!

Original comment by mellowaredev on 6 Jan 2011 at 5:34

[GoogleCodeExporter]

With latest version of foo_touchremote (dated sept29), Foobar even don't start 
properly and shows message "Failed to load DLL: foo_touchremote.dll".
I've tried different versions both Foobar and foo_touchremote. All of them have 
connecting problem, at least with Windows XP and HTC Desire (Android).

Original comment by volobuev...@gmail.com on 7 Jan 2011 at 12:51

[GoogleCodeExporter]

Issue 28 has been merged into this issue.

Original comment by mellowaredev on 30 Jan 2011 at 1:38

[GoogleCodeExporter]

[deleted comment]