Bugzilla – Bug 17792
Local devices not found when clicking "Go".
Last modified: 2012-03-06 00:36:58 UTC
Logitech Squeezebox Controller 1.1.2 on Android 4.0.1. The Android virtual keyboard features a "Go" button. When the app is initially installed, you are prompted for your Squeeze Network username and password. After entering your details, if you click the "log in" button in the app, things works as expected. However, if you click the "Go" button in the virtual keyboard, things do not. You login details are accepted and it's possible to control players that are connected to Squeeze Network. However, devices on the local network are not detected.
The button has nothing to do with local player detection, but only with submission of the mysb.com credentials. Most likely this is either a temporary glitch, or the mobile not being connected to the same network as your players/servers.
Created attachment 7585 [details] Failure screenshot
I can confirm this is a real bug and not some temporary glitch or network issue. With the device in airplane mode and only connected to the same local wifi network the Logitech app fails to detect the players. A paid controller application in the market on the same device with the same connection finds the players without issue. I have attached a screenshot of the failed discovery attempt in airplane mode on wifi-only. Please confirm this bug. The app rating on the market is taking a beating because of it, and as more devices get Ice Cream Sandwich the rating will only get worse.
Haven't tested myself, but here's the feedback I got from a buddy: "I have manually installed Android 4.0 on my Nexus S but I think it is performing same as the OTA one. I just tried all major functions of the app but I didn't see anything wrong with it... Please let me know if there was a specific problem." Could you please verify again you're connected to the same network as your player/server, and it's not working with airplane mode _off_? Just because a different app does behave better doesn't mean the Controller App was broken: they do some smarter stuff than we do :-).
Created attachment 7589 [details] Test connecting to duet receiver with airplane mode ofd Michael attaching the other test case per your request. This also demonstrates the password box not properly clipping or hiding. These devices were absolutely on the same unrestricted LAN.
Created attachment 7604 [details] Error log from local device discovery Michael, it appears the port field is being corrupted when parsed from the response packet. It should read 9000, but doesn't appear to be ASCII at all past the 9.
Seems to be an issue in Android 4: http://code.google.com/p/android/issues/detail?id=24748
Created attachment 7614 [details] Android issue 24748/Logitech Media Server test case (In reply to comment #7) > Seems to be an issue in Android 4: > http://code.google.com/p/android/issues/detail?id=24748 I disagree.
Created attachment 7615 [details] Eclipse project from the previous screenshot
== Auto-comment from SVN commit #8573 to the player repo by mherger == == http://svn.slimdevices.com/player?view=revision&revision=8573 == Bug: 17792 Description: fix udp packet corruption as document in http://code.google.com/p/android/issues/detail?id=24748
== Auto-comment from SVN commit #8574 to the player repo by mherger == == http://svn.slimdevices.com/player?view=revision&revision=8574 == Bug: 17792 Description: fix udp packet corruption as document in http://code.google.com/p/android/issues/detail?id=24748
Created attachment 7638 [details] Eastman using fixed discovery Please give this build a try. It should fix the discovery on ICS.
The attachment fixed the network discovery problem for me on my Asus transformer TF101, but the app forces a portrait view and cuts off half the screen. Thanks for fixing the network error. (In reply to comment #12) > Created an attachment (id=7638) [details] > Eastman using fixed discovery > > Please give this build a try. It should fix the discovery on ICS.
> The attachment fixed the network discovery problem for me on my Asus > transformer TF101, but the app forces a portrait view and cuts off half the > screen. Thanks for fixing the network error. Could you please open a new bug report for this issue and attach a screenshot? Thanks for the confirmation of the main issue fixed.
I'm not sure how to open a new bug referencing the experimental apk listed in this thread instead of the apk that is available in the market. After restarting, the only problem is that the app is locked in portrait view on my tablet. (In reply to comment #14) > > The attachment fixed the network discovery problem for me on my Asus > > transformer TF101, but the app forces a portrait view and cuts off half the > > screen. Thanks for fixing the network error. > > Could you please open a new bug report for this issue and attach a screenshot? > > Thanks for the confirmation of the main issue fixed.
(In reply to comment #15) > I'm not sure how to open a new bug referencing the experimental apk listed in > this thread instead of the apk that is available in the market. Just create a new bug, attach a screenshot and describe what you're doing with what exact Android revision, device details etc.