Related
I just bought Tablet Talk for 2.50 and the only way it works is via WiFi. When I try to use Bluetooth, I get a connection error code 1. Please help me.
Sent from my Nexus 7 using xda app-developers app
If no one knows or replies, you could try contacting the developer. They are meant to be very quick at replying.
Sorry I couldn't help you further.
(Think I explained what I meant better this time )
Sent from my Xperia Arc
Make sure. Both devices have their Bluetooth turned on then open tablet talk on both devices and make sure Bluetooth connection is selected. On the phone hit the red Bluetooth button and select enable discovery, on the tablet it should ask u to setup devices and find the phone via Bluetooth
What Rom are you on? You might want to test it using a different Rom. There were a couple of times out there in which Tablet Talk doesn't work.
I am currently running CodeAndroid and both Bluetooth and Wi-Fi connections work.
j.a said:
What Rom are you on? You might want to test it using a different Rom. There were a couple of times out there in which Tablet Talk doesn't work.
I am currently running CodeAndroid and both Bluetooth and Wi-Fi connections work.
Click to expand...
Click to collapse
I am on cm 10 and I have all Bluetooth on...
Sent from my Nexus 7 using xda app-developers app
I'm on the latest cm10 and I had it working the other day with blue tooth just fine but I can't get it to connect today. I was able to unchecked the option to share Internet over blue tooth before in bt settings but it won't unchecked now. The only consistent connection I have been able to maintain is off the hot spots on my galaxy nexus but it won't reconnect without me manually pushing the connect button. Has been inconsistent for sure but just attribute it to the romantic and flashing nightly.
Sent from my Nexus 7 using Tapatalk 2
I ran into this this weekend... I ended up UNpairing through the the bluetooth settings in the ROM itself (not the app) clearing cache / data on tablet talk on both phone and n7, then repairing through the ROM and setting up through the app. Pain in the *** and took me a few tries but now it's working great.
Unpairing and pairing again works for me.
An alternative for the app but works a different way is TabletSMS by koush. I use it more often than tablet talk https://play.google.com/store/apps/details?id=com.koushikdutta.tabletsms
mach0boi said:
Unpairing and pairing again works for me.
An alternative for the app but works a different way is TabletSMS by koush. I use it more often than tablet talk
Click to expand...
Click to collapse
I can vouch for TabletSMS. It works very well. I also have tablet talk but I use that for car connectivity by tethering it with my phone when in my car. The tether connect is flawless.
Tablet talk working fine for me.
I ran into the same issue
The only way it works for me is to press the connection button on both devices
I haven't found a way to trigger the connection from one device only (CM9 phone / stock JB tablet, bluetooth tethering on)
Email the developer, he helped me out. Awesome service.
Sent from my Nexus 7 using xda app-developers app
For those having a problem with Tablet Talk relating to pairing/connecting your devices, here's a quick fix reply from the developer posted on Androidcentral.
I am the original creator and main developer of Tablet Talk. Someone emailed about this thread, which prompted me to make this account so that I can offer better support and obtain feedback.
First, mrgdr57: the app is for Android tablets and phones. Please send an email to [email protected] with the subject "Refund." Either send it from or provide the email address your order is under so that I can locate and take care of it right away!
Next, if you have not done so already, please install the update which was released very early this morning. It will help with the connection problems.
Regarding port: this setting only affects Wifi.
Wifi
If Wifi is not working, then please do the following:
Change the port to 8080 on both devices. It can be found under "Setup."
Under "Setup" on your tablet, enter your phone's IP address. Your phone's IP is displayed inside the phone app ("Phone IP: 192...."). Almost always the app finds your phone automatically; however, sometimes it is unable to. The tablet app keeps track of each network separately, so you should not have to do this every time.
Bluetooth
Sometime when Bluetooth is not working, a simple restart of either the tablet or phone fixes the problem. Once Bluetooth is setup, it should work without any problems. The previous version appeared to be having Bluetooth problems, and this morning's update (1.5.3) should help with these.
If Bluetooth has not yet worked for you, then uninstall and reinstall the app on both devices to get a fresh start.
When the app first opens, it detects whether you are using a phone or tablet. A popup appears asking you to confirm. Make sure that you confirm the correct device type. You can always change the device type in Tablet Talk's settings ("Misc" in phone, "Appearance & Behavior" in tablet). If you are texting from a Galaxy Player linked to a phone, then you will need to tell the app that the Galaxy Player is a "tablet." Also, if your phone is a Galaxy Note, the app might think it's a tablet, so be sure to identify it as a phone.
The standard solution for when Bluetooth setup is not working is to do the following:
Open Android's Bluetooth settings on both devices. If they are already paired, unpair your phone and tablet from each other.
Toggle Bluetooth off and then back on (both devices).
Pair your phone and tablet within Android's Bluetooth settings.
Phone: open Tablet Talk and press the connect button. If it asks you to enable discovery, press accept.
Tablet: open Tablet Talk and press the connect button.
Quick & Automatic Connecting
Once Tablet Talk is setup, connecting can be made much quicker and automatic for future use. Check out the Automatic Settings on both devices for the options. There is also a widget. You can tailor it to your specific needs.
Also, whenever you connect, the app will sync any newly sent or received messages on your phone from the last use.
Example configuration: When you get home from work, simply enable Wifi or Bluetooth on your phone, and then turn on your tablet. The app will take care of the rest. Automatic settings:
Tablet: auto start when app opens. Auto enable Wifi or Bluetooth.
Phone: auto start when Wifi or Bluetooth is enabled.
I will be subscribed to this thread and try to reply to new posts as often and quickly as possible. You can also email [email protected]. Feel free to send questions, feature requests, comments, etc. Feedback--good and bad--is always appreciated!
Click to expand...
Click to collapse
I managed to get it working by creating an ugly workaround with tasker: my tablet sends a connection request (via the autoremote plugin) to the phone who launches tablettalk (with auto-connect at startup turned on) and then the tablet launche tablettalk too with the same autoconnect option. As the two devices are trying to connect simultaneously, the connection is established correctly. That's the only way I found to get a connection (other than manually pressing 'connect' on both two devices)
contact names not consistent between phone and tablet.
This may sound strange but when I send a message on my phone and a tablet syncs, the contact name on the tablet does not match the contact name on the phone.The phone shows the name, but the tablet just shows the phone number and also when I have two people with the same last name in my contacts the phone shows the correct name but the tablet shows the other person's name, even though the phone's contact list contains completely different different information for each of the contacts
joep229 said:
This may sound strange but when I send a message on my phone and a tablet syncs, the contact name on the tablet does not match the contact name on the phone.The phone shows the name, but the tablet just shows the phone number and also when I have two people with the same last name in my contacts the phone shows the correct name but the tablet shows the other person's name, even though the phone's contact list contains completely different different information for each of the contacts
Click to expand...
Click to collapse
Had some conflicting issues in my contact list. Solved most.
For Nexus 7 (2013) owners:
Lets discuss <any> working methods for using Display Settings, Wireless Display, on Android 4.3+ with Nexus 7 (2013).
1) I want to explore what happens when Wireless display is turned on - and what it takes for wireless displays to be found.
Fine if you use Google Chromecast, or any other devices as wireless displays.
2) What types of data can be pushed/streamed by "wireless display" - e.g. video, audio, VNC, RDA, files, etc?
You get the idea.
-----------
Check this post below. The Netgear PTV3000 works on new Nexus 7 (2013) out of the box.
Bob Smith42 said:
For Nexus 7 (2013) owners:
Lets discuss <any> working methods for using Display Settings, Wireless Display, on Android 4.3+ with Nexus 7 (2013).
1) I want to explore what happens when Wireless display is turned on - and what it takes for wireless displays to be found.
Fine if you use Google Chromecast, or any other devices as wireless displays.
2) What types of data can be pushed/streamed by "wireless display" - e.g. video, audio, VNC, RDA, files, etc?
You get the idea.
Click to expand...
Click to collapse
turned it on, doesnt see either of my 2 chromecast or my tv (not smart or google, just has a ethernet connected which usually allows things to be sent though very limited via dlna)
NyPlaya513 said:
turned it on, doesnt see either of my 2 chromecast or my tv (not smart or google, just has a ethernet connected which usually allows things to be sent though very limited via dlna)
Click to expand...
Click to collapse
Good info. Thanks
I *assume* the feature does *something* in Android 4.3+, and maybe *something* specifically on the Nexus 7 (2013).
Of course this assumption might be wrong, e.g. I'm not sure what Wi-Fi, three dots menu, Wi-Fi Direct accomplishes either. LOL
So please inform us if anyone has knowledge of what happens with Wireless Display turned on, or how to make it work.
I'm assuming it's for Miracast. I don't have any Miracast receivers though.
I was hoping it would work with my Apple TV but when I switch on wireless display, it finds nothing.
gksmithlcw said:
I'm assuming it's for Miracast. I don't have any Miracast receivers though.
Click to expand...
Click to collapse
You are likely correct. I just found this article with some info:
https://en.wikipedia.org/wiki/Miracast
The Wi-Fi Alliance maintains a current list of Miracast-certified devices, both source devices and display devices. The technology and certification is fairly new with the first devices being certified in September 2012. As of January 19, 2013, only just over 100 devices in total were certified.
Nvidia announced support for it in their Tegra 3 platform,[8] and Freescale Semiconductor, Texas Instruments, Qualcomm, Marvell Technology Group and other chip vendors have also announced their plans to support it.[9] Support for Miracast was added to Android in version 4.2 on October 29, 2012.
Both devices (the sender and the receiver) need to be Miracast certified for the technology to work. However, to stream music and movies to a non-certified device there will be Miracast adapters available that plug into HDMI or USB ports.[10]
On 29 October 2012, Google announced that Android version 4.2 (updated version of Jelly Bean) will support the Miracast wireless display standard, and by default will have integrated features for it.[11] As of January 8, 2013, the LG Nexus 4 and Sony's Xperia Z, ZL, T and V officially support the function,[12][13] as does HTC One and Samsung in its Galaxy S III and Galaxy Note II under the moniker AllShare Cast. The Galaxy S4 uses Samsung Link for its implementation.[14]
Microsoft also added support for Miracast in Windows 8.1, and announced this in June 2013. This functionality first became available in the Windows 8.1 Preview, and is available on hardware with supported Miracast drivers from hardware (GPU) manufacturers such as those listed above.
Click to expand...
Click to collapse
And, found this:
Nov 2012
http://phandroid.com/2012/11/19/psa-nexus-7-and-nexus-10-do-not-support-miracast-wireless-display/
PSA: Nexus 7 and Nexus 10 do not support Miracast wireless display
There’s been an ongoing discussion over on Google’s mobile support forum and after much debate, a Googler took the time to weigh in on the issue confirming:
Just wanted to confirm that Nexus 4 is currently our only Nexus device that works with Miracast wireless display on Android 4.2. There was a reference to wireless display on our Help site for Nexus 10, but we’ve since removed that reference. Our apologies for any confusion that may have caused.
Click to expand...
Click to collapse
I'm not sure but this appears to show a Google fail on Miracast (old postings):
http://productforums.google.com/forum/#!topic/mobile/DK-P8Tlnrow[1-25-false]
http://productforums.google.com/forum/#!topic/mobile/DK-P8Tlnrow
Nexus 10, Miracast and Netgear Push2TV 3000
Nexus 4 can see PTV3000, but never connects.
Click to expand...
Click to collapse
-------------------
If anyone has Miracast working on the new Nexus 7 (2013) using <any> method, whether or not including Wireless Display - please post your results here.
Bob Smith42 said:
...
If anyone has Miracast working on the new Nexus 7 (2013) using <any> method, whether or not including Wireless Display - please post your results here.
Click to expand...
Click to collapse
Here is one possible solution using Netgear PTV3000:
Published 07/04/2013 04:17 AM | Updated 07/04/2013 04:19 AM
http://kb.netgear.com/app/answers/detail/a_id/23705
How to connect Google Nexus 4 to PTV3000?
If anyone has the PTV3000 it would be great if you could test on new Nexus 7 (2013) and/or any device running Android 4.3.
The latest firmware update to the PTV3000 is now PTV3000-V2.2.16
From PTV3000_V2.2.16_FW_Release_Notes:
Supported Intel Wireless Display platforms:
Windows 7, Intel Wireless Display V3.1.29.0, Wifi driver V15.1.1
Windows 7, Intel Wireless Display V3.5.41.0, Wif driver V15.3.1
Windows 8 (systems upgraded form Windows 7), Intel Wireless Display V3.5.41.0, Wifi driver V15.3.50
Windows 8 (with Win8 preinstalled), Intel Wireless display, V3.5.41.0, Wifi driver V15.5.7
Windows 8 (with Win8 preinstalled), Intel Wireless display, V4.0.18.0, Wifi driver V15.6.1
Supported Miracast platforms:
Samsung Galaxy S3 (Android 4.1.1 or above)
Samsung Galaxy Note II
Samsung Galaxy Note 10.1
LG Optimus G (Android 4.0.4 or above)
Google Nexus 4 (Android 4.2.1)
Sony Xperia (various models with Android 4.0.4 or above)
Enhancements & Bug Fixes:
Preliminary support for WiDi Gen4 low latency mode. A new option should appear in the WiDi application for prioritizing speed over quality. The “AVSYNC” uboot variable also has new functionality, though it is still currently set to “1”. Change customer_pre_script.sh appropriately if you would like to change the default behavior.
NOTE-1: AVSYNC automatically changes from 1 to 2 when entering “low delay” mode in WiDi, and similarly from 2 to 1 when exiting “low delay” mode.
NOTE-2: Audio is currently not working in low delay mode.
AVSYNC = 0: Disabled.
AVSYNC = 1: Video FW uses Audio PTS for AV sync operation
AVSYNC = 2: Video FW uses STC, System Clock, (ignore audio and decode as fast as possible) for AV sync operation.
AVSYNC = 3: Combined mode. AVSYNC = 1 for DECODER_LATENCY > 75, AVSYNC = 2 in the rest of cases.
Nexus4 Android 4.2.2 compatibility issue – Fixed a rare connection issue related to RTSP.
Improved low power usage for EU region, by suspending to DDR. DC power usage was measured at 290mW. With a 70% efficient A/C adapter it should be around 440mW.
Fixed incorrect setting of decoder latency which was causing video to be early by a couple frames (A/V Sync issue).
Known Issues:
Audio does not work with WiDi 4.x Low Delay mode.
Samsung S3 occasionally does not connect. We are working with QCA on the issue. It appears to be a WiFi driver/firmware bug.
Nexus4 streaming issues:
Phone stops sending data abruptly while streaming high definition video. Air sniffer captures show phone stops sending video packets and goes back to scanning. As result dongle waits for at least 10 seconds for the phone to respond and goes back to ready screen if the phone does not respond.
Samsung Galaxy S3 4.1.1 phone bugs:
Connection will fail if this is done: Start Allshare cast app on phone. Lock the screen and let the phone be idle for 10 minutes. Unlock the screen. Remedy: Toggle WiFi switch on phone settings.
Connection halts after playing a video from Video Player application.
Sony Experia Tsubasa (version 7.0.A.3.185) the mirrored video does not show up until there is activity on the handset screen. Fixed in 9.0.D.1.126.
[Intel] Win8 WiDi 3.5.40.0 application hangs sometimes on reconnection, requiring a laptop re-boot..
Installation Procedure
Push and hold the WPS button on the side of the PTV3000 unit for more than 5 seconds.
PTV3000 goes into firmware update mode. Firmware update procedure shows up on TV screen (also shown below on steps 3 to 7).
Use your PC or mobile device to navigate to http://support.netgear.com/product/PTV3000 to check for and download the latest firmware.
Once you have downloaded the latest firmware zip file, please unzip it and locate the ".sbin" file that it contains.
Using the wireless network manager utility on your device, search for "Push2TV" wireless network name (SSID) and connect.
Open a web browser on your device and type http://192.168.3.1 into the URL bar of the browser.
Follow the steps on the web page to upload the firmware image and complete the installation.
Working Device (Netgear Push2TV PTV3000)
Found a working device. The Netgear Push2TV PTV3000.
Plug the PTV3000 into a mini-USB 5v for power. Connect the HDMI to a TV or monitor. The device displays waiting status.
In new Nexus 7 (2013) go to Settings, Display, Wireless Display. Turn on. Press SEARCH FOR DISPLAYS.
The Push2TV <serial #>-PTV3000 appears in the list of Available Devices. A few seconds after selecting the device the projector shows the entire Nexus 7 (2013) display on the TV or monitor screen.
Note: I took the PTV3000 out of the box and did not apply any firmware updates (yet).
I have lots more questions and things to test. My initial questions are:
1) How does it work with portrait and landscape orientation?
2) Does sound get broadcast to the TV or monitor?
3) Since it works on new Nexus 7 (2013) will it also work on 1st generation Nexus 7 (Android 4.2.1 through 4.3)?
4) How do movies look on the TV?
5) Verify this really Miracast, or is there a second mode on PTV3000?
6) What is the firmware level on PTV3000?
I don't have time to do further tests now. But, ask if you have further questions I can test.
Thanks for the suggestions and help so far... especially gksmithlcw
I tested with this over the weekend and it worked like a dream.
http://www.netgear.com/home/products/hometheater/media-players/PTV3000.aspx
I beg to differ on the PTV 3000
I find it to be useless. It projects an image in the middle of the screen. You could never really watch a movie or anything due to the black bars on the sides. It also does not pass through DTS or Dolby Digital Surround Sound. You are far better off using a media server app like BubbleUPNP to stream media. This is just a little toy. It is light years from being serviceable.
Pancake345 said:
I tested with this over the weekend and it worked like a dream.
http://www.netgear.com/home/products/hometheater/media-players/PTV3000.aspx
Click to expand...
Click to collapse
hi dudes,
i tried widi with new n7 with mk808b android tv stick. it hassame problem like the n4.
Nexus4 streaming issues:
Phone stops sending data abruptly while streaming high definition video. Air sniffer captures show phone stops sending video packets and goes back to scanning. As result dongle waits for at least 10 seconds for the phone to respond and goes back to ready screen if the phone does not respond.
but with bubbleupnp n7 works well to stream movie, pics or music. so with kitkat widi dosent work. maybe with another kernel and rom??
Bob Smith42 said:
Good info. Thanks
I *assume* the feature does *something* in Android 4.3+, and maybe *something* specifically on the Nexus 7 (2013).
Of course this assumption might be wrong, e.g. I'm not sure what Wi-Fi, three dots menu, Wi-Fi Direct accomplishes either. LOL
So please inform us if anyone has knowledge of what happens with Wireless Display turned on, or how to make it work.
Click to expand...
Click to collapse
It scans for Miracast supported device whenit's turn on. If you have a Miracast device connected to the same network, it will show up and you can display your whole screen on the reciever.
Miracast is not Apple's AirPlay and they are totally different. Although they do similar things.
It's also not DLNA. Most of the time files are being sent through DLNA, so you cant see your contacts, messages, homescreen etc. through DLNA. Miracast send your screen feed to the TV.
Miracast need a Miracast sender and reciever to work just like DLNA needs a DLNA server and reciever and AirPlay needs a server and reciever too.
My Nexus 7 (2013) has Wireless Display (I think its Miracast) since 4.3. I think it will work if you have a reciever. I tried it before with Note 2 to my friend's TV which have Miracast support.(I never try it with N7 before because I dont have a reciever). AOSP have support for Miracast as sender since 4.3 (I think)
You need a very fast network to stream smoothly.
The display will change orientation when you rotate your device.
BubbleUPNP is a using DLNA not Miracast.
Miracast still can't work properly in real life.
ALL OF THIS IS ONLY MY THOUGHTS. CORRECT ME IF I'M WRONG
Does anyone else have issues with N7 2013 filling up the screen when connected via miracast? My moto x and N5 fill the screen just fine but the N7 is cropped around the edges.
this device has been working great for me, picked mine up at Wlally-World.
http://www.actiontec.com/303.html#soft
I am also trying to figure out how the miracast feature works or supposed to work with our Nexus 7 2013 model- 5.02 lollipop.
1)My miracast enabled tv (lg model) detects the device.
2)Under cast screen tab in notification panel, tv is not detected but if you enter the more settings options then lg tv is then detected.
3)trying to connect (either from tv menu or nexus menu) results in notification that there is an invitation for connection, then authentication and when the tv shows "miracast is waiting for connection" my nexus stop detecting the lg tv for a few seconds then shows up again but no connection is established. If i insist a couple of times to connect then nexus wifi despite being connected to my home network it cannot connect to the internet.
If someone has an update from miracast feature please post.
cheers
Hi,
I'm using Tablet Talk on Nexus 4 phone and Nexus 7 tablet installed in my car dash. The application works totally fine except for one strange issue: it appears to cut off internet to other apps installed on Nexus 7. Internet connection is shared by the phone via Bluetooth.
When Tablet Talk is connected, Youtube shows connection error, Waze navigation cannot reach its servers most of the time (though not always), Chrome browser either works extremely slowly (loading google search results for about 3 minutes) or don't work at all.
Everything works fine as soon as I disconnect Tablet Talk.
I was unable to google similar issue reported by other Tablet Talk users, so maybe I'm doing anything wrong?
Any ideas are most welcome.
MausL said:
Hi,
I'm using Tablet Talk on Nexus 4 phone and Nexus 7 tablet installed in my car dash. The application works totally fine except for one strange issue: it appears to cut off internet to other apps installed on Nexus 7. Internet connection is shared by the phone via Bluetooth.
When Tablet Talk is connected, Youtube shows connection error, Waze navigation cannot reach its servers most of the time (though not always), Chrome browser either works extremely slowly (loading google search results for about 3 minutes) or don't work at all.
Everything works fine as soon as I disconnect Tablet Talk.
I was unable to google similar issue reported by other Tablet Talk users, so maybe I'm doing anything wrong?
Any ideas are most welcome.
Click to expand...
Click to collapse
If you are using Bluetooth to connect to tablet talk, and to share internet.... Then there is your problem, I think u can only have one device connected with Bluetooth at a time.
Try setting phone as mobile hotspot, and connect the nexus 7 via WiFi. Then use tablet talk in WiFi mode. And forget about Bluetooth and its narrow bandwidth.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
If you are using Bluetooth to connect to tablet talk, and to share internet.... Then there is your problem, I think u can only have one device connected with Bluetooth at a time.
Click to expand...
Click to collapse
I would agree if there is no internet at all - either Tablet Talk or internet. However, there are two things that make me believe that there's another reason: first, there is internet connection, yet somewhat flaky, in Waze navigation app, and some others, while Tablet Talk is connected. Next, Tablet Talk uses the same bluetooth connection - no extra [virtual] device or BT profile appears in the bluetooth connection list, as far as I remember.
I've asked the Tablet Talk developer about this; still awaiting their response.
MausL said:
I would agree if there is no internet at all - either Tablet Talk or internet. However, there are two things that make me believe that there's another reason: first, there is internet connection, yet somewhat flaky, in Waze navigation app, and some others, while Tablet Talk is connected. Next, Tablet Talk uses the same bluetooth connection - no extra [virtual] device or BT profile appears in the bluetooth connection list, as far as I remember.
I've asked the Tablet Talk developer about this; still awaiting their response.
Click to expand...
Click to collapse
Yup its still one connection but 2 data feeds, therefore 2 connections through Bluetooth. it makes sense to me this issue. That's why I never ran tablet talk this way. I know Bluetooth don't have much bandwidth.
I would be curious of the answer too. I use tablet talk just not in this configuration.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
I know Bluetooth don't have much bandwidth.
Click to expand...
Click to collapse
Sure, but yet it's always been sufficient for any youtube video and other tasks. I don't believe that Tablet Talk in standby mode consumes all the bandwidth... but who knows, maybe you're right. I'll try to find a tool that'll allow to monitor BT bandwidth/load, if it's technically possible. Thanks for the clue!
I would be curious of the answer too.
Click to expand...
Click to collapse
I'll post it here. Today I've received the developer's acknowledgement for my support inquiry - they've escalated it to 2nd level support for review.
Hello all.
So I got my Note 7 last week and when I got it home I found that i had major issues with my home WiFi. Now I have a ton of devices ganging from laptops to TV' Phones and Tablets and none of them have any issues getting on the net via the WiFi. But for some reason my Note 7 is another story. The Firewall I run at home is a Sophos UTM 9 virtual appliance. I like it because it provides all the features I need and then some. I have already spent many hours tweaking, Tuning and trying to figure out why my Note simply does not want to play on my network. In order for me to have a reality check I installed and Untangle firewall appliance on my VMWare server and switched my firewall over to that. After making the switch my Note seems to work fine. Now if the Untangle firewall offered all the features I wanted in a firewall I would just say what the heck and stay with it however it is not as robust and does not fully meet my needs.
Has anyone else has similar issues with their Note 7 and if so have you been able to resolve them. I did post in the Sophos forums and so far only had one reply with someone having the same issue but has been unable to resolve it.
Many Thanks
Hi -
I'm having a weird issue trying to cast on my Pixel 2 XL. Although all my other devices can see and cast to all 3 of my chromecasts (1 Chromecast and 2 chromecast audio), my Pixel 2 XL can only cast YouTube. The home app is able to setup a chromecast, but then either tells me it can't discover the device it just configured, or that it doesn't see it, but this should be resolved shortly.
Home app shows no compatible devices.
Settings > Connected devices shows devices.
All other apps will cast to alternate devices (Roku 4, Roku Stick), but no chromecast devices.
I have called and opened a ticket with Chromecast support, who told me I'm all alone with this issue (search results in general would prove this inaccurate).
Does anyone else have this problem? Fix?
Running 8.1, rooted with Magisk 15.1, flash kernel 2.05.
Yep. Same problem here. No fix yet, though.
KKenna said:
Hi -
I'm having a weird issue trying to cast on my Pixel 2 XL. Although all my other devices can see and cast to all 3 of my chromecasts (1 Chromecast and 2 chromecast audio), my Pixel 2 XL can only cast YouTube. The home app is able to setup a chromecast, but then either tells me it can't discover the device it just configured, or that it doesn't see it, but this should be resolved shortly.
Home app shows no compatible devices.
Settings > Connected devices shows devices.
All other apps will cast to alternate devices (Roku 4, Roku Stick), but no chromecast devices.
I have called and opened a ticket with Chromecast support, who told me I'm all alone with this issue (search results in general would prove this inaccurate).
Does anyone else have this problem? Fix?
Running 8.1, rooted with Magisk 15.1, flash kernel 2.05.
Click to expand...
Click to collapse
I'm able to cast to all my Chromecasts (2 Chromecasts plus a JBL-connected speaker). Sometimes, if I'm in an app and it's not showing the devices I have to hit refresh and they show up.
I just tested it with Plex. I'm on 8.1 using the ElementalX kernel.
EMcTx said:
I'm able to cast to all my Chromecasts (2 Chromecasts plus a JBL-connected speaker). Sometimes, if I'm in an app and it's not showing the devices I have to hit refresh and they show up.
I just tested it with Plex. I'm on 8.1 using the ElementalX kernel.
Click to expand...
Click to collapse
I had to shotgun my Eeros, install another router, and place my Eeros in bridge mode to get this to work correctly.
I've always had problems with my Android devices and the Eeros anyway...
Every once in a while my Chromecast won't show up if I open the app I'm going to cast before I change the TV input(even though the Chromecast is powered up). This is rare and closing and reopening the app always resolves it.
Same issue on Pixel XL (2016)
Did you ever resolve this one? I have exactly the same issue. Most of the time my Pixel XL can't see any of my Chromecasts. Occasionally it can see them and sometimes just a subset of them. My old Nexus 5 however can see them fine every time. The only way I've found to get them visible again on the Pixel is to restart the phone, but even that isn't 100% reliable. Very frustrating...
Pixel 2 XL on 8.1.0 -
Will cast via Youtube using the icon, however no devices found when going to settings, connected devices, cast.
Is this still an unresolved issue?