Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Miracast autoconnect

OP unknownprotocols

26th April 2013, 11:40 PM   |  #1  
OP Member
Flag Sherman
Thanks Meter: 12
 
97 posts
Join Date:Joined: Mar 2012
More
Okay, I have Tasker, and my hope is to make my Nexus 4 autoconnect to my ptv3000 miracast adapter. I can manually connect just fine, but I want to find a command that will make the Nexus connect to the miracast automatically instead of having to navigate to display, wireless display, and then click on the adapter name... Quite tedious everytime I start my car... Even a shortcut directly to the wireless display section in settings is a start. I ran logcat recording while I manually connected, but I didn't see what I was hoping to.




04-26 16:18:56.362 I/wpa_supplicant(10288): p2p0: P2P-DEVICE-FOUND 22:e5:2a:71:00:eb p2p_dev_addr=22:e5:2a:71:00:eb pri_dev_type=7-0050F204-1 name='Push2TV 7100EB-PTV3000' config_methods=0x88 dev_capab=0x25 group_capab=0x0 wfd_dev_info=0x000006015d022a0032
04-26 16:18:58.244 I/wpa_supplicant(10288): p2p0: P2P-FIND-STOPPED
04-26 16:18:58.244 I/WifiDisplayController(10176): Connecting to Wifi display: Push2TV 7100EB-PTV3000
04-26 16:18:58.274 I/WifiDisplayController(10176): Initiated connection to Wifi display: Push2TV 7100EB-PTV3000
04-26 16:19:01.117 I/wpa_supplicant(10288): p2p0: P2P-INVITATION-RESULT status=0 22:e5:2a:71:00:eb
04-26 16:19:02.819 I/EventLogService(10647): Aggregate from 1367009342688 (log), 1367009342688 (data)
04-26 16:19:02.919 I/ServiceDumpSys(10647): dumping service [account]
04-26 16:19:03.830 D/HeadsetPhoneState(12798): sendDeviceStateChanged. mService=1 mSignal=3 mRoam=0 mBatteryCharge=2
04-26 16:19:07.123 I/wpa_supplicant(10288): p2p0: Trying to associate with 22:e5:2a:71:00:eb (SSID='DIRECT-Xb' freq=2412 MHz)
04-26 16:19:07.224 I/wpa_supplicant(10288): p2p0: Associated with 22:e5:2a:71:00:eb
04-26 16:19:07.224 I/wpa_supplicant(10288): p2p0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success)
04-26 16:19:07.234 I/wpa_supplicant(10288): p2p0: WPA: Key negotiation completed with 22:e5:2a:71:00:eb [PTK=CCMP GTK=CCMP]
04-26 16:19:07.234 I/wpa_supplicant(10288): p2p0: CTRL-EVENT-CONNECTED - Connection to 22:e5:2a:71:00:eb completed (reauth) [id=2 id_str=]
04-26 16:19:07.244 I/wpa_supplicant(10288): p2p0: P2P-GROUP-STARTED p2p0 client ssid="DIRECT-Xb" freq=2412 psk=96402cc994e104e7f7f6686715510a91eacf149f127b62 cd3098903db915bf77 go_dev_addr=22:e5:2a:71:00:eb [PERSISTENT]
04-26 16:19:07.254 I/wpa_supplicant(10288): wpa_s->ifname p2p0 cmd SET p2p_group_idle 10
04-26 16:19:07.564 D/HeadsetPhoneState(12798): sendDeviceStateChanged. mService=1 mSignal=4 mRoam=0 mBatteryCharge=2
04-26 16:19:10.697 I/wpa_supplicant(10288): wpa_s->ifname p2p0 cmd P2P_SET ps 1
04-26 16:19:10.697 I/WifiDisplayController(10176): Connected to Wifi display: Push2TV 7100EB-PTV3000
04-26 16:19:10.707 E/MonoPipe(9945): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
04-26 16:19:10.707 I/AudioFlinger(9945): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
04-26 16:19:10.707 I/AudioMixer(9945): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
04-26 16:19:10.707 I/AudioFlinger(9945): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
04-26 16:19:10.707 I/AudioMixer(9945): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
04-26 16:19:10.707 D/ALSAStreamOps(9945): setParameters(): keyRouting with device 0x0
04-26 16:19:10.707 D/ALSAStreamOps(9945): setParameters(): keyRouting with device 0x0
04-26 16:19:10.717 I/AudioFlinger(9945): AudioFlinger's thread 0x40082008 ready to run
04-26 16:19:10.717 I/AudioFlinger(9945): AudioFlinger's thread 0x4121e008 ready to run
04-26 16:19:10.717 I/r_submix(9945): out_standby()
04-26 16:19:10.717 I/WifiDisplayController(10176): Listening for RTSP connection on 192.168.157.100:7236 from Wifi display: Push2TV 7100EB-PTV3000
04-26 16:19:13.981 I/NetworkSession(9945): incoming connection from 192.168.157.1:52634 (socket 34)
04-26 16:19:13.981 I/NetworkSession(9945): added clientSession 2
04-26 16:19:13.981 I/WifiDisplaySource(9945): We now have a client (2) connected.
04-26 16:19:14.041 I/WifiDisplaySource(9945): Using AAC audio.
04-26 16:19:14.061 I/WifiDisplaySource(9945): Initiating HDCP negotiation w/ host 192.168.157.1:1189
04-26 16:19:14.071 I/WifiDisplaySource(9945): Deferring SETUP trigger until HDCP initialization completes.
04-26 16:19:14.081 D/QSEECOMAPI: (9945): QSEECom_start_app sb_length = 0x480
04-26 16:19:14.091 D/QSEECOMAPI: (9945): App is not loaded in QSEE
04-26 16:19:14.091 E/QSEECOMAPI: (9945): Error::Cannot open the file /system/etc/firmware/dxhdcp2.mdt
04-26 16:19:14.091 E/QSEECOMAPI: (9945): Error::Loading image failed with ret = -1
04-26 16:19:14.091 D/QSEECOMAPI: (9945): QSEECom_start_app sb_length = 0x480
04-26 16:19:14.091 D/QSEECOMAPI: (9945): App is not loaded in QSEE
04-26 16:19:14.181 D/QSEECOMAPI: (9945): Loaded image: APP id = 1
04-26 16:19:14.301 D/DxHDCP (9945): AKE_SEND_CERT received
04-26 16:19:14.321 D/DxHDCP (9945): AKE_RECEIVER_INFO received
04-26 16:19:14.401 D/DxHDCP (9945): AKE_SEND_RRX received
04-26 16:19:14.461 D/DxHDCP (9945): AKE_SEND_H_PRIME received
04-26 16:19:14.471 D/DxHDCP (9945): AKE_PAIRING_INFO received
04-26 16:19:14.481 D/DxHDCP (9945): LC_L_PRIME received
04-26 16:19:14.511 D/DxHDCP (9945): REPEATERAUTH_STREAM_READY received
04-26 16:19:14.561 D/DxHDCP (9945): REPEATERAUTH_SEND_RECEIVERID_LIST received
04-26 16:19:14.611 D/DxHDCP (9945): RECEIVER_AUTHSTATUS received
04-26 16:19:15.272 I/wpa_supplicant(10288): wlan0: CTRL-EVENT-DISCONNECTED bssid=68:7f:74:97:25:10 reason=65534
27th April 2013, 06:38 PM   |  #2  
Junior Member
Thanks Meter: 1
 
3 posts
Join Date:Joined: Feb 2009
I too have been trying to get this to work in Tasker but so far no luck. A few months back I ran across a thread on Reddit from a user who was able to get Tasker to work along with an add-on package. At the time I tried the same technique but couldn't get it to work. Unfortunately, I can't seem to find that thread again. Once my Google-Fu regains full strength and I find the thread again I will post it and it might give you some clues.
Tim
27th April 2013, 11:14 PM   |  #3  
OP Member
Flag Sherman
Thanks Meter: 12
 
97 posts
Join Date:Joined: Mar 2012
More
If this goofy slimport adapter wasn't so marked up right now... Bought miracast for cheaper! Now I almost wish I would have paid the $80 for slimport
14th May 2013, 01:52 AM   |  #4  
Junior Member
Thanks Meter: 4
 
28 posts
Join Date:Joined: Feb 2011
Quote:
Originally Posted by tschallb

I too have been trying to get this to work in Tasker but so far no luck. A few months back I ran across a thread on Reddit from a user who was able to get Tasker to work along with an add-on package. At the time I tried the same technique but couldn't get it to work. Unfortunately, I can't seem to find that thread again. Once my Google-Fu regains full strength and I find the thread again I will post it and it might give you some clues.
Tim

Is it possible that the WiFiDisplay.APK might launch Miracast connection more efficiently when combined with Tasker?

Here's a Reddit thread that discussed stripping the APK from the ROMs that use it.

Apparently, it's pretty simple to do.

There's also Android Transporter, which may provide the same thing as WiFiDisplay.APK.
Last edited by smayonak; 14th May 2013 at 02:36 AM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes