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!
thanamesjames
Junior Member Posts: 43 Joined: Jul 2010 Reputation: 0 |
2011-10-02 22:14
Post: #101
(This post was last modified: 2011-10-02 22:16 by thanamesjames.)
|
| find quote |
riplix
Junior Member Posts: 1 Joined: Sep 2011 Reputation: 0 |
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
Junior Member Posts: 43 Joined: Jul 2010 Reputation: 0 |
2011-10-05 04:42
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
Junior Member Posts: 8 Joined: May 2011 Reputation: 0 |
2011-10-06 10:02
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
Junior Member Posts: 2 Joined: Oct 2011 Reputation: 0 |
2011-10-06 18:28
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
Junior Member Posts: 2 Joined: Oct 2011 Reputation: 0 |
2011-10-06 18:39
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 can confirm that that particular kernel works! Puzzled!
|
| find quote |
clambert
Member Joined: Dec 2010 Reputation: 0 Location: East Coast USA |
2011-10-14 03:38
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. ![]() 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
Member Joined: Dec 2010 Reputation: 0 Location: East Coast USA |
2011-10-17 03:10
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. 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.
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
Senior Member Posts: 152 Joined: Aug 2011 Reputation: 0 |
2011-10-18 03:53
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
Junior Member Posts: 1 Joined: Oct 2011 Reputation: 0 |
2011-10-20 19:57
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]P.S.: Editing system files is for advanced users, and you do so on your own responsibility. |
| find quote |



Search
Help