Database Users

[Q] Can't connect to Nexus Q after initial configuration [SOLVED]

Hello,
I bought a Nexus Q off eBay and it came in today. I got it plugged in to my TV but after the setup was completed, I'm unable to connect to the device through both my phone and tablet. The TV just outputs a blue circle. In the Nexus Q app, it has "Living Room" and underneath "Not available". When I try the "Update Network" option, it's unable to find it via Bluetooth although it sees it in the bluetooth device list as "3 Nexus Q" (#0099cc-#0099cc)
My phone is a Samsung Galaxy S3 running CM10.0.0 and my tablet is an Asus Transformer tf101 stock image (v4.0.1 iirc). I've even reset my router, an Asus RT-N12B1.
I've tried flashing with the factory image provided here developers.google.com/android/nexus/images#tungsten
and still nothing. I can reinstall the app and factory reset the device and go through the setup successfully, but once it's done, it doesn't see it.
Does anyone have any suggestions? Did I just buy a pretty paperweight?

Did you happen to try and reset the Q power the orb on and place your palm over the touch sensor. The ring should turn red hold your hand on it until the ring turns blue and release. It should now be reset to factory setting and you can try and repair with the phone.
Sent from my Nexus 7 using xda app-developers app

Yep, I've done that. I'm going to take it to work to see if it's my WiFi to rule one more thing out.
EDIT: Tested at work on a different WiFi and it's the same result.

I had this same issue.
I fixed it by removing the device from my account via the app on my phone or tablet.
A simple reset of the app won't remove it since it is tied to your Google account.
After successfully removing the Q from my account, I cleared data for the app, and restarted my device.
Before I repaired it to the Q, I preformed a reset on the Q by placing my hand over it and plugging in the power cord.
Lastly I repaired the Q with my device as if it was a brand new device.
I noticed that there were problems if trying to do an initial pair with 5GHz WiFi. I had my phone connected to the 2.4GHz band when I pro formed the pair.
I don't believe the Q supports the 5GHz band, so don't try to pair with it.
You can shift to it on your phone or tablet after you pair, but if you don't have a 2.4GHz network connected to the Q, it won't see your devices once paired.

matty3f said:
Hello,
I bought a Nexus Q off eBay and it came in today. I got it plugged in to my TV but after the setup was completed, I'm unable to connect to the device through both my phone and tablet. The TV just outputs a blue circle. In the Nexus Q app, it has "Living Room" and underneath "Not available". When I try the "Update Network" option, it's unable to find it via Bluetooth although it sees it in the bluetooth device list as "3 Nexus Q" (#0099cc-#0099cc)
My phone is a Samsung Galaxy S3 running CM10.0.0 and my tablet is an Asus Transformer tf101 stock image (v4.0.1 iirc). I've even reset my router, an Asus RT-N12B1.
I've tried flashing with the factory image provided here developers.google.com/android/nexus/images#tungsten
and still nothing. I can reinstall the app and factory reset the device and go through the setup successfully, but once it's done, it doesn't see it.
Does anyone have any suggestions? Did I just buy a pretty paperweight?
Click to expand...
Click to collapse
Some routers have a firewall built in that doesn't allow devices to talk to each other through the router, which the Q requires. I can also set mine up at work, but because of this firewall (which most workplaces implement) i couldn't actually play with the Q. Are you familiar with the "ping" command? In your tablet and your phone you should be able to find your ip addresses, hopefully something like 192.168.1.102. if you get an app from the market (terminal emulator will do i believe) try pinging one device from the other. Even if its successful you shouldn't see anything on the pinged device, just a response from the pinged device on your pinging device. If this says "response timed out" or something similar your devices cannot see each other across your wifi, and thusly not see each other once the bluetooth connection is terminated after initial set up.
If that doesn't work I'll buy it

brain dump on Q connectivity
Connectivity is a problem with the Q no question - but once you finally get it connection it's fine. I have 2 of them, and one seems to work much better than the other for some reason.
Here are some things I've done to troubleshoot these issues (some of this may be completely unnecessary but it works for me)
1 - Completely uninstall music, youtube, play movies, and nexus q app from your phone. It seems like this actually has some impact although I'm not sure why.
2 - Factory reset the Q - do this by placing your hand over it and then unplug and plug the q back in. Eventually it will do a factory reset.
3 - Check if your router supports DD-WRT by typing your model number in here: http://www.dd-wrt.com/site/support/router-database
If it does flash it! This was the single biggest improvement in connectivity I observed but this might just be an issue with my specific router.
4 - Try again and again and again. I've seen it not connect to the Q the first 25 times and then suddenly work. Ridiculous.
A note on DD-WRT - I am using a DLink DIR-615. I constantly have connection issues and also 'there was a problem with the network' when trying to play youtube videos at times. I tried tweaking settings in the router for hours and finally flashed DDWRT on my router. As soon as I did, the network connection errors went away and it seems to have made connectivity much better as well.

It's working! Thanks, everyone!
I flashed DD-WRT on my router, something I've been meaning to do for a while. I uninstalled the Nexus Q, Google Video and Music apps, and the updates for Market and Play Services on my phone. Factory-reset the Nexus Q and finally reinstalled just Nexus Q app, and let it prompt me to install the other apps. It worked the first time. I'm certain it was the router firmware as I've done everything else before.

I'm having similar issues. I've been trouble shooting now for a few hours and I have a headache from it all. Factory resets, uninstalls, nothing. I download terminal emulator to ping a packet and it looks good.
Sometimes the "My Home" collection is found sometime it's unavailable. When it's showing unavailable I click on the notice, and then click more, and it immediately says "the collection has been found on the network".
My bedroom nexus q is not available. I hate networking ****. I'm beginning to understand why they killed this thing, it's a shame it looks so beautiful.

Well I called the nexus support hotline, and they are all but incompetent. "If you tried a master reset and it's still not working the unit must be defective." The guy also tried to tell me the "My Home" collection was my wifi. I'm thinking about just throwing it back on ebay.

gunsarebad said:
I'm having similar issues. I've been trouble shooting now for a few hours and I have a headache from it all. Factory resets, uninstalls, nothing. I download terminal emulator to ping a packet and it looks good.
Sometimes the "My Home" collection is found sometime it's unavailable. When it's showing unavailable I click on the notice, and then click more, and it immediately says "the collection has been found on the network".
My bedroom nexus q is not available. I hate networking ****. I'm beginning to understand why they killed this thing, it's a shame it looks so beautiful.
Click to expand...
Click to collapse
what kind of reset? holding the mute during startup or just from the app?

animal24 said:
what kind of reset? holding the mute during startup or just from the app?
Click to expand...
Click to collapse
Both. I finally tried a cheap ass router and I no longer have any issues.

gunsarebad said:
Both. I finally tried a cheap ass router and I no longer have any issues.
Click to expand...
Click to collapse
Oh well.:angel:

Wifi Hardcoded - Fire 7 not expecting OTG Ethernet to bypass for other tasks

I have had a suspicion that the Fire 7 is hardcoded to recognise WiFi only for OTA updates and account registration etc. So I reset the device, set Amazon registration for later and did not join my local WiFi network. Plugged in my OTG Ethernet, opened a browser in Silk and went to BBC to confirm connectivity.
Since my device updated automatically the other day, even after a reset for this exercise the build is still FIRE OS 5.0.1 which is to be expected. I am unable to test if OTA updates will still kick in automatically when using OTG Ethernet?
Amazon account Registration is hardcoded to look for a WiFi connection only. Attempting to register with Ethernet does not work, the device simply prompts to join a WiFi network. [A Network Connection is required to complete this task. Please connect to a WiFi network].
System Updates button when pressed searches for an update - as there are currently no new updates again I am unable to test if this would automatically kick in via OTG Ethernet.
OK in the long run it is not feasible for the device to stay tethered via an ethernet cable, but it shows that the Fire 7 is expecting specific network tasks to automatically and manually to be carried by WiFi. Even though OTG Ethernet is working the device is simply not expecting it to be there!
As it currently stands I not going to join my device to my Amazon account again. Will leave it as standalone and install Google via the APKs that sd_Shadow so kindly pointed everyone in the right direction. Would be interesting to see if the next System Update is ignored if connected via OTG Ethernet.
Update 1: Aeroplane Mode enabled on the device and OTG Ethernet has full connectivity - was able to web browse. System Updates still searched and Amazon Account signup still prompted for WiFi connection. So it looks like Aeroplane Modes does not knock out the OTG Ethernet.
Update 2: Obviously with no Amazon sign in the device is restricted to the apps installed at factory default. So no ES Explorer donwload without Amazon signin to install the Google APKs. I know many of you have been using a ADB Shell to install your Google APKs. For this exercise of standalone device without Amazon Signin I simply connected my Fire7 via usb to my laptop, copied over the Google APKs to local storage (Fire 7 Device). Opened Amazon DOCS and browsed to Local Storage and installed them from there. Gave the tablet a reboot and all good.
Update 3: Google Play works fine on the Fire 7 via OTG Ethernet , in Aeroplane Mode and with no WiFi & Amazon account signin.
Update 4: Kindle App on Google Play shows as installed on the Fire 7 - opening the Kindle App prompts for Amazon Registration. I was hoping that this app would work without Amazon registration.
Update 5: I sent a dummy email support query from the device via [Phone & E-mail support] via OTG Ethernet in aeroplane mode to see if it would actually send and it did.
Update 6: I know sd_Shadow tried KingRoot already but the latest version came out the other day [4.5.2.928]. So I tried it but it failed to get root. But what was interesting is that when KingRoot went online to look for exploits as part of the rooting process, it would only do so if WiFi was enabled. It would not dial out when using OTG Ethernet. It was worth a go, just have to be patient for someone to find a root exploit out there.
Update 7: TowelRoot does not work either. tested it with the different codes - but it checked for exploits over the OTA ethernet.

Thank you Very much for this info
i wonder if someone could decode, the update signal Amazon sends to the fire.
because if so we may be able to use Apache (or something like it) to install CM (CyanogenMod)
VIA OTG Ethernet
just the product of my mental activity (AKA: a brain **** storm)
.
anyway for those who do not know what a OTG Ethernet is here is a video on it
https://www.youtube.com/watch?v=BkJBV82sj34
you can get one at Amazon here
http://www.amazon.com/Plugable-Ethernet-Compatible-Smartphones-AX88772A/dp/B00RM3KXAU
Peace
Ricci

Your'e welcome. I posted this into the Tips & Tricks thread the other day.
It seems the same OTA Update file [otacerts.zip] that is used on other Fire & Kindle models is being used as the config for the Fire 7 for the OTA Update - it can be found in /etc/security/otacerts.zip
As soon as root is available we will be able to deal with this file and stop any future OTA updates.

a1yet said:
i wonder if someone could decode, the update signal Amazon sends to the fire.
because if so we may be able to use Apache (or something like it) to install CM (CyanogenMod)
VIA OTG Ethernet
just the product of my mental activity (AKA: a brain **** storm)
Click to expand...
Click to collapse
You could use a local DNS server to the same effect as using an OTG Ethernet adapter, either creating a hotspot on your computer or pointing your router's DNS address at your local DNS server.
Even so, the update would still require Amazon's signature, so unfortunately this probably would not work. It's the same reason we can't use fastboot or adb in recovery mode to flash a custom ROM.

Google Play store Waiting for network.

Hello there all around.
Maybe already someone mentioned earlier...
Can't Downloading some games ( I presume big files) from store, it gives error - waiting for network, or not shown at all progres, or king of pending procedure. I'm feeding shield with Hotspot from phone, but I know definitely my provide have no restrictions, coz downloading constantly torrent, movies, big files etc on pc and phone it self on same network. I tried all kind of tests clear Google play store cash/ data, reset factory device all this things and non of them helps. Should I go and rooted and edit host file or any kind suggestions? Any other suggestions very appreciated.
Sent from my SM-G925K using XDA Free mobile app

I had the EXACT same problem. I was using my phone as a hotspot, and certain apps would download just fine, but one in particular, Minecraft Story Mode, just kept showing "waiting for network". The only way I got through it was to take my Shield to work. I plugged it into my ethernet at the office and it downloaded just fine.
I agree with you that the hotspot shouldn't have anything to do with it, but it seems it does. I tried clearing data in google play, clearing it in google play services, uninstalling updates, etc. In my research I found that when Sprint first rolled out the first 4G network in the U.S., people were having the same problem with the play store. It has to be something about the traffic. The only thing I would suggest is try a VPN with your hotspot if you absolutely can't get to a place with WiFi or ethernet.

bradleyw801 said:
I had the EXACT same problem. I was using my phone as a hotspot, and certain apps would download just fine, but one in particular, Minecraft Story Mode, just kept showing "waiting for network". The only way I got through it was to take my Shield to work. I plugged it into my ethernet at the office and it downloaded just fine.
I agree with you that the hotspot shouldn't have anything to do with it, but it seems it does. I tried clearing data in google play, clearing it in google play services, uninstalling updates, etc. In my research I found that when Sprint first rolled out the first 4G network in the U.S., people were having the same problem with the play store. It has to be something about the traffic. The only thing I would suggest is try a VPN with your hotspot if you absolutely can't get to a place with WiFi or ethernet.
Click to expand...
Click to collapse
Thanks for suggestion, somewhere i had kind of suspicious feeling about that all. Thanks
Sent from my SM-G925K using XDA Free mobile app

For what it's worth, I found some other people having a similar problem. But unlike us, they weren't tethered. https://forums.geforce.com/default/...few-apps-not-installing-waiting-for-network-/
May be a problem with the shield after all...

bradleyw801 said:
For what it's worth, I found some other people having a similar problem. But unlike us, they weren't tethered. https://forums.geforce.com/default/...few-apps-not-installing-waiting-for-network-/
May be a problem with the shield after all...
Click to expand...
Click to collapse
My opinion - shield native os...
Sent from my SM-G925K using XDA Free mobile app

Not sure if it's connected but the same thing happens on my Sony 2015 Android TV (permanently connected via cable to a perfectly working NAT router). The Play app received a major redesign recently but still seems to have its quirks.
The thread /r/AndroidTV/comments/3r572z mentions it as a bug in the latest play store build.

I had this problem since the start its only app over 50mb, then it was 60mb after an update, now with the new revamped play store for ATV the problem is fixed, for me at least
this update http://www.googlewatchblog.de/wp-content/uploads/android-tv-neu.jpg

Problem with Netflix and casting on my Shield PRO

Hi guys,
I have recently bought a Shield TV Pro and as much as the excitement was at the beginning, as much disappointed I am now. And that's because I have a few issues that from my research was fixed long time ago. But alas, it seems like I still have them and I was wondering if is this a case of returning the problem or waiting a little bit more for some fixes.
On short: Netflix cannot play anything. I can browse and do whatever I want but it cannot play. I get the message that the show cannot be played at the moment and to try a different one. But is the same for all. The message has a tiny code: AIP-703. On a little bit of google-ling I found that it might be a connection problem, or a vpn problem, but I don't have any vpn on my router, the internet connection is ok (also from the app internal testing) , and I also tried on another network, plus my phone as a Hot Spot for the shield. Same result. Netflix on my Chromecast works just fine, so somehow I exclude the network, although I keep hoping that it is a router problem, another reason to replace that and keep the Shield
And another big problem is that I cannot cast to the device. I can see the device on my phone (Samsung Galaxy s5 mini), but I cannot connect to cast from any of the apps that I have (including youtube and netflix). Casting to my Chromecast 2 works just fine.
What I did:
- Full factory reset (yeah, I know, waited for more that 2 hours for this one)
- tried to play with the device and apps not updated and with them updated
- sign out, clear app cache sign back in, sign out of all devices in Netflix account settings
- I even created another Netflix account to see if that was the problem
- router rebut
- tried again and again to see if the issues are gone for more than a week now. 2 days ago I also saw a netflix update and I thought that this is it, the fix, but still, the problem is still there.
So, any other ideas that I should try? Or should I give it back? If yes, should I try another one or I will get on the same results?
Thank you.

Voice commands via google assistant no longer working after switching out router

I replaced my old Tp-link archer c59 with an orbi mesh system. I use to be able to say commands to my google home like ''launch netflix on shield'' and it would work. After switching out the router, I just get ''I dont know how to do that yet''. I still see the shield in the google home app. Im still able to control it through the google home app with the ''play music'' function so I know its still linked. Casting works fine. If I set the shield as my default speaker, my hub will play music directly to the shield. Whats confusing is that its defiantly linked up.
Things I tried already are clearing data on google play services and chromecast built in on the shield. Clearing data on the google home app on my phone.
Side note: The shield is also no longer discoverable on a windows PC. I use to be able to access it under ''network''. I tried disabling and enabling sharing on the shield already.

Update. I was finally able to fix this issue after a month. I turned offer IPv6 on the shield, a now GA is able to launch apps with voice command. My PC is also able to see the shield under network. Ive always had IPv6 enabled before switching to the Orbi system and never had a problem. Not sure why a newer router would screw everything up.
However, there are couple of new problems Ive encountered. Casting from my PC lasts for a second and the picture freezes while the sound continues. Second, I can no longer connect to the shield with my phone or tablet with file manager apps. I can still connect to it with my PC just fine.