Remote working but no library

  Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
thanamesjames Offline
Junior Member
Posts: 43
Joined: Jul 2010
Reputation: 0
Post: #101
Any updates?
My roommate has a DroidX stock, and library works fine for him, but not for me.
I'm on an Evo, Deck's Gingerbread (CM7 branch) and have all the symptoms addressed here. Thanks!
(This post was last modified: 2011-10-02 22:16 by thanamesjames.)
find quote
riplix Offline
Junior Member
Posts: 1
Joined: Sep 2011
Reputation: 0
Big Grin  Potential fix Post: #102
I've encountered the same issue on my Galaxy S2 (2.3.4 stock) as well as XBMC Constellation on Ipad so I figured it's not necessarily related to the app itself but potentially an API issue? May also be related to router settings though...

I've fixed it on both devices by changing the port from 80 to 8080 (and using a password although that's probably irrelevant).
find quote
thanamesjames Offline
Junior Member
Posts: 43
Joined: Jul 2010
Reputation: 0
Post: #103
So for those who are rooted and having trouble, it could very well be your kernel and not your rom. That was the problem for me.
find quote
CodeItAway Offline
Junior Member
Posts: 8
Joined: May 2011
Reputation: 0
Post: #104
thanamesjames Wrote:So for those who are rooted and having trouble, it could very well be your kernel and not your rom. That was the problem for me.
Thank you. This was the problem for me too. I was using the CM based GingerVillian rom with the kernel which ships with the rom on my Desire.
I am now using the Gingerbread-HAVS-AXI-CFS manu kernel, which can be found here.
find quote
NVivas Offline
Junior Member
Posts: 2
Joined: Oct 2011
Reputation: 0
Post: #105
I have the same problem.

Using Desire with the latest 3.1 GingerVillain.

Updated kernel to the havs one using Villain setup and now it connects, sometimes, but never updates any of the libraries.

Any help would be appreciated.

Despite these problems....Excellent software btw!
find quote
NVivas Offline
Junior Member
Posts: 2
Joined: Oct 2011
Reputation: 0
Post: #106
CodeItAway Wrote:Thank you. This was the problem for me too. I was using the CM based GingerVillian rom with the kernel which ships with the rom on my Desire.
I am now using the Gingerbread-HAVS-AXI-CFS manu kernel, which can be found here.

I can confirm that that particular kernel works! Puzzled!Tongue
find quote
clambert Online
Member
Posts: 61
Joined: Dec 2010
Reputation: 0
Location: East Coast USA
Post: #107
Found this thread after having similar issues. I'm running CM 7.1 Final with Incredikernel 2.6.38.8 on my original HTC Incredible.

I'll try another kernel and see how things go when I get some free time. Right now I just want to chill and watch some TV. Smile

Glad i found this thread though. It was driving me nuts. Good to know I have company.

XBMC Box
Shuttle XS35GT w/ 2 GB RAM (No HDD)
Openelec 3.0.2 / XBMC 12.2 Frodo
OS Running on: USB Stick
find quote
clambert Online
Member
Posts: 61
Joined: Dec 2010
Reputation: 0
Location: East Coast USA
Post: #108
clambert Wrote:Found this thread after having similar issues. I'm running CM 7.1 Final with Incredikernel 2.6.38.8 on my original HTC Incredible.

I'll try another kernel and see how things go when I get some free time. Right now I just want to chill and watch some TV. Smile

Glad i found this thread though. It was driving me nuts. Good to know I have company.

Just to touch back on this... I seem to be experiencing no issues with the default CM7 kernel for the Incredible. It definitely seems like the kernel has something to do with the problem.

Thanks for the heads up people. Smile

XBMC Box
Shuttle XS35GT w/ 2 GB RAM (No HDD)
Openelec 3.0.2 / XBMC 12.2 Frodo
OS Running on: USB Stick
find quote
Headcase_Fargon Offline
Senior Member
Posts: 152
Joined: Aug 2011
Reputation: 0
Post: #109
Latest CM7 nightly (Android 2.3.7) with Tiamat SBC kernel and I get this same issue. I'll try flashing the original CM7 kernel and see if that helps.
find quote
Mr. 47 Offline
Junior Member
Posts: 1
Joined: Oct 2011
Reputation: 0
Post: #110
I registered just to let you know about a temporary fix (sorry, didn't read through the 11 pages, so if it was already posted - I apologize).

I'm not the one who found it, I stumbled upon the fix on XBMC Remote development site, I think.

Anyway - the issue is with Gingerbread's implementation of network socket functions which are used by the remote. For some reason, when you use an IP address in the XBMC Remote, it will try to resolve it's ARPA notation through DNS instead of connecting directly. Why is it doing so, I have no idea, and it doesn't happen on Honeycomb, and hopefully also fixed on ICS.

For now, though, there are two workarounds:
1. Use the hostname (it's the cleanest solution, but unfortunately doesn't work for me).
2. Edit the hosts file on your rooted phone. The file /system/etc/hosts contains DNS resolutions which the phone tries to use before contacting a DNS server. Add the following line to it (supposing the IP address of your computer running XBMC is 192.168.0.111) :
Code:
192.168.0.111 [i]xbmchostname[/i]
Now you can use the hostname on your phone, and it will work. In fact, to my surprise (I still haven't figured that out, but what the hell), if you'll use the IP address after that it will work as well. So theoretically, you can write anything you want instead of xbmchostname, and it'll work (just don't write something real like google.com, or else you won't be able to access that from the phone).

P.S.: Editing system files is for advanced users, and you do so on your own responsibility.
find quote
Post Reply