Welcome, Guest
Please Login or Register.    Lost Password?

Upcoming release of a Chromecast Receiver on Android
(1 viewing) (1) Guest
Go to bottomPage: 123456
TOPIC: Upcoming release of a Chromecast Receiver on Android
#21779
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 11 Months ago Karma: 0
Started getting some IP errors on the UI and went to look at the logs and got the following:

Code:


06-16 12:29:46.019 I/JmDNSImpl(18603): intf[0]: name=rmnet_usb0, supportsMulticast=false
06-16 12:29:46.019 I/JmDNSImpl(18603): intf[1]: name=sit0, supportsMulticast=false
06-16 12:29:46.020 I/JmDNSImpl(18603): intf[2]: name=usb0, supportsMulticast=true
06-16 12:29:46.020 I/JmDNSImpl(18603): intf[3]: name=lo, supportsMulticast=false
06-16 12:29:46.020 I/JmDNSImpl(18603): ip: /127.0.0.1
06-16 12:29:46.020 I/JmDNSImpl(18603): intf[4]: name=wlan0, supportsMulticast=true
06-16 12:29:46.021 I/JmDNSImpl(18603): ip: /192.168.43.1
06-16 12:29:46.021 I/JmDNSImpl(18603): intf[5]: name=dummy0, supportsMulticast=false
06-16 12:29:46.021 I/JmDNSImpl(18603): intf[6]: name=r_rmnet_data0, supportsMulticast=false
06-16 12:29:46.022 I/JmDNSImpl(18603): intf[7]: name=r_rmnet_data2, supportsMulticast=false
06-16 12:29:46.023 I/JmDNSImpl(18603): intf[8]: name=r_rmnet_data1, supportsMulticast=false
06-16 12:29:46.024 I/JmDNSImpl(18603): intf[9]: name=r_rmnet_data3, supportsMulticast=false
06-16 12:29:46.024 I/JmDNSImpl(18603): intf[10]: name=r_rmnet_data4, supportsMulticast=false
06-16 12:29:46.024 I/JmDNSImpl(18603): intf[11]: name=r_rmnet_data6, supportsMulticast=false
06-16 12:29:46.025 I/JmDNSImpl(18603): intf[12]: name=r_rmnet_data5, supportsMulticast=false
06-16 12:29:46.025 I/JmDNSImpl(18603): intf[13]: name=r_rmnet_data7, supportsMulticast=false
06-16 12:29:46.025 I/JmDNSImpl(18603): intf[14]: name=r_rmnet_data8, supportsMulticast=false
06-16 12:29:46.026 I/JmDNSImpl(18603): intf[15]: name=rmnet_data0, supportsMulticast=false
06-16 12:29:46.026 I/JmDNSImpl(18603): ip: /10.97.223.117
06-16 12:29:46.027 I/JmDNSImpl(18603): intf[16]: name=rmnet_data1, supportsMulticast=false
06-16 12:29:46.027 I/JmDNSImpl(18603): intf[17]: name=rmnet_data3, supportsMulticast=false
06-16 12:29:46.027 I/JmDNSImpl(18603): intf[18]: name=rmnet_data2, supportsMulticast=false
06-16 12:29:46.027 I/JmDNSImpl(18603): intf[19]: name=rmnet_data4, supportsMulticast=false
06-16 12:29:46.028 I/JmDNSImpl(18603): intf[20]: name=rmnet_data6, supportsMulticast=false
06-16 12:29:46.028 I/JmDNSImpl(18603): intf[21]: name=rmnet_data5, supportsMulticast=false
06-16 12:29:46.028 I/JmDNSImpl(18603): intf[22]: name=rmnet_data7, supportsMulticast=false
06-16 12:29:46.051 I/JmDNSImpl(18603): mWifiIpAddress=null
06-16 12:29:46.051 I/JmDNSImpl(18603): mEthernetIpAddress=null
06-16 12:29:48.054 E/chromium(18603): [18603:18656:ERROR:mdns_service_util.cc(90)] Cannot initialize mDNS service.



By issuing a netcfg on the device I see my wifi interface has the 192.168.43.1 address, so not sure why it couldn't figure it out, see below:

Code:


shell@shamu:/ $ netcfg
rmnet_usb0 UP                                     0.0.0.0/0   0x00000041 00:00:00:00:00:00
sit0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00
usb0     DOWN                                   0.0.0.0/0   0x00001002 ee:27:b1:02:93:83
lo       UP                                   127.0.0.1/8   0x00000049 00:00:00:00:00:00
wlan0    UP                                192.168.43.1/24  0x00001043 92:68:c3:f0:bc:4c
dummy0   DOWN                                   0.0.0.0/0   0x00000082 92:09:d0:a3:54:ac
r_rmnet_data0 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data2 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data1 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data3 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data4 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data6 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data5 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data7 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
r_rmnet_data8 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data0 UP                               10.97.223.117/30  0x00000041 00:00:00:00:00:00
rmnet_data1 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data3 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data2 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data4 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data6 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data5 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00
rmnet_data7 DOWN                                   0.0.0.0/0   0x00000000 00:00:00:00:00:00

roberto.andrade
Junior Boarder
Posts: 23
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2015/06/16 09:42 By roberto.andrade.
The administrator has disabled public write access.
 
#21780
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 11 Months ago Karma: 86
Hi Robert,

the issue with a hotspot is known (it seems you turned wifi hotspot), fixing the issue, it should work in next build.

As for x86 vm, since they usually don't support low level decoding, so it's not working at the moment.

We will release a vm in a couple of month, it will be the best on the market, and will make sure our app works on our own Android vm.
huisinro
Moderator
Posts: 1567
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#21802
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 11 Months ago Karma: 0
I'm experimenting with something and was wondering if you guys had experienced that in your environments. I'm creating a port forward from one of my machines to the android device running the app (both 8008 and 8009) and republishing the Bonjour records as they are with the only difference being the IP (pointing to the machine that does the TCP/UDP forwarding).

It shows up fine in the list and connects successfully, but what I notice is that the rendering only shows up as a black screen.

Do you guys have any ideas as to why that might happen?
roberto.andrade
Junior Boarder
Posts: 23
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#21988
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 9 Months ago Karma: 86
This is the trial apk, which has full features, except this current apk will expire on August 31, 2015, so hurry up !

www.youmap.com/YouMapCastReceiver.apk
huisinro
Moderator
Posts: 1567
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#21989
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 9 Months ago Karma: 0
Does this build solve any of the issues above?
roberto.andrade
Junior Boarder
Posts: 23
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#21992
Re:Upcoming release of a Chromecast Receiver on Android 4 Years, 9 Months ago Karma: 86
(1) chrome tab mirroring works better, audio works too

(2) some improvement on bonjour registrations
huisinro
Moderator
Posts: 1567
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 123456