My NP remote keeps unpairing from the NP after a couple of days. If you leave the remote in that state, it will keep flashing the white LED on the remote (looking to be paired?) and drain the batteries.
Anyone else have that problem too, and is there a fix?
It is running the stock unrooted Android 8.0
Sent using Tapatalk
Nate2 said:
My NP remote keeps unpairing from the NP after a couple of days. If you leave the remote in that state, it will keep flashing the white LED on the remote (looking to be paired?) and drain the batteries.
Anyone else have that problem too, and is there a fix?
It is running the stock unrooted Android 8.0
Sent using Tapatalk
Click to expand...
Click to collapse
I think your bluetooth is disabled
if you have access to a usb keyboard of some sort and an plug into your nexus player, find and download (sideload) an android terminal app. in the command prompt, enter:
su
service call bluetooth_manager 8
service call bluetooth_manager 6
Related
I'm rooted and everything was going fine. I installed Sixaxis and was playing around with some emulators. When I disabled Sixaxis, it said it was restoring previous Bluetooth state. When it stopped, my Nexus Player remote wasn't working, so I went to Bluetooth devices and it wasn't listed. I clicked on Bluetooth to pair it again, but now the Nexus Player doesn't detect any Bluetooth devices (tried my phone and keyboard). Restarting the device still doesn't fix the issue so I'm now stuck with no Bluetooth devices being able to pair. Any ideas? I don't want to wipe since I just got Kodi all situated. Thanks
Yeah, the solution for me was to factory reset. You will have to use some other input method, since you can't pair via Bluetooth. I think what happened is the Bluetooth was turned off and there is no way to turn it on in the Nexus firmware.
Sent from my Nexus 4 using XDA Free mobile app
I had that happen also. Needed to factory reset. Then I did it again and it has been working great
sec6 said:
Yeah, the solution for me was to factory reset. You will have to use some other input method, since you can't pair via Bluetooth. I think what happened is the Bluetooth was turned off and there is no way to turn it on in the Nexus firmware.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I was thinking it was stuck also. So before I wiped, I figured to try turning Bluetooth off/on from terminal. That seemed to do the trick! Both devices showed back up under Bluetooth.
I used commands:
su
service call bluetooth_manager 8
then
service call bluetooth_manager 6
I'm having a similar problem after attaching a bluetooth dongle via USB OTG in an attempt to pair a SixAxis controller. Unfortunately doing so seems to have somehow bricked the internal bluetooth. I'm no longer able to pair anything, and attempting to do so just results in it the bluetooth service freezing and restarting. Even a full factory reset and reflashing the factory image I haven't been able to fix it. Does anybody have any idea what it could have possibly done that would persist even after restoring the factory image?
shadrach47 said:
I was thinking it was stuck also. So before I wiped, I figured to try turning Bluetooth off/on from terminal. That seemed to do the trick! Both devices showed back up under Bluetooth.
I used commands:
su
service call bluetooth_manager 8
then
service call bluetooth_manager 6
Click to expand...
Click to collapse
Cool. Good job. Put those commands in a sticky somewhere!
Sent from my Nexus 7 using XDA Free mobile app
shadrach47 said:
I was thinking it was stuck also. So before I wiped, I figured to try turning Bluetooth off/on from terminal. That seemed to do the trick! Both devices showed back up under Bluetooth.
I used commands:
su
service call bluetooth_manager 8
then
service call bluetooth_manager 6
Click to expand...
Click to collapse
So this worked? Were you able to gain control of your remote again after this?
If so, would you be so kind as to explain how you entered the commands you listed? I'm a bit confused as to where you entered them.
On your computer using ADB/Fastboot or using the Terminal App? A small step-by-step would be GREATLY appreciated.
Thanks in advance!
---------- Post added at 05:26 PM ---------- Previous post was at 05:10 PM ----------
taomun said:
So this worked? Were you able to gain control of your remote again after this?
If so, would you be so kind as to explain how you entered the commands you listed? I'm a bit confused as to where you entered them.
On your computer using ADB/Fastboot or using the Terminal App? A small step-by-step would be GREATLY appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Nevermind. I got it to work using the Terminal Emulator App directly on the device.
Those two calls brought the remote back Definitely deserves a sticky!
shadrach47 said:
I was thinking it was stuck also. So before I wiped, I figured to try turning Bluetooth off/on from terminal. That seemed to do the trick! Both devices showed back up under Bluetooth.
I used commands:
su
service call bluetooth_manager 8
then
service call bluetooth_manager 6
Click to expand...
Click to collapse
Would it be easy to make a script/Tasker app to do this right from the Sideload Launcher? I'm pretty new to tasker and can't figure out how to do command-based tasks.
shadrach47 said:
su
service call bluetooth_manager 8
service call bluetooth_manager 6
Click to expand...
Click to collapse
Thanks a bunch, worked great. Ran it from terminal
darker_slayer said:
Thanks a bunch, worked great. Ran it from terminal
Click to expand...
Click to collapse
I am having the same issue and looking into how to run these commands? Did you install an SSH terminal app on the NP? If not, what does "Ran it from terminal" consist of?
Thanks in advance
---------- Post added at 01:33 PM ---------- Previous post was at 12:40 PM ----------
unix4linux said:
I am having the same issue and looking into how to run these commands? Did you install an SSH terminal app on the NP? If not, what does "Ran it from terminal" consist of?
Thanks in advance
Click to expand...
Click to collapse
I figured it out. I installed Terminal Emulator for Android via the Google Play Store (web browser version) and selected Nexus Player, since it is supported. Then ran the commands listed.
Everything works like a charm now. I can switch between remote and PS4 remote with no issues.
unix4linux said:
I figured it out. I installed Terminal Emulator for Android via the Google Play Store (web browser version) and selected Nexus Player, since it is supported. Then ran the commands listed.
Click to expand...
Click to collapse
^ yep, this
Sixaxis issues connecting
I have sixaxis installed and was working like a charm, then out of nowhere the PS3 controllers no longer connect. The lights keep flashing and the nexus player doesn't find them.
Thoughts? Solutions? any help would be greatly appreciated.
mahoora said:
I have sixaxis installed and was working like a charm, then out of nowhere the PS3 controllers no longer connect. The lights keep flashing and the nexus player doesn't find them.
Thoughts? Solutions? any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried going through the pairing process again? Sounds like they are unpaired. If you go to settings, can you see the device still paired? If you do, try removing it and then go through the pairing process again.
Sent from my LG-D850 using Tapatalk
unix4linux said:
Have you tried going through the pairing process again? Sounds like they are unpaired. If you go to settings, can you see the device still paired? If you do, try removing it and then go through the pairing process again.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I've tried that along with uninstalling sixaxis app and re installing still not pairing
I have no idea how to fix this
mahoora said:
Thanks, but I've tried that along with uninstalling sixaxis app and re installing still not pairing
I have no idea how to fix this
Click to expand...
Click to collapse
I assume you also ran the stated commands from the terminal?
Sent from my LG-D850 using Tapatalk
unix4linux said:
I assume you also ran the stated commands from the terminal?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Ya, that got my nexus remote back working for me. PS3 controllers still wont connect at all through Bluetooth using the sixaxis app
mahoora said:
Ya, that got my nexus remote back working for me. PS3 controllers still wont connect at all through Bluetooth using the sixaxis app
Click to expand...
Click to collapse
Dang, sorry to hear that. I'm out of ideas. If I can think of anything else, I'll let you know.
Sent from my LG-D850 using Tapatalk
unix4linux said:
Dang, sorry to hear that. I'm out of ideas. If I can think of anything else, I'll let you know.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks, appreciate it.
mahoora said:
I have sixaxis installed and was working like a charm, then out of nowhere the PS3 controllers no longer connect. The lights keep flashing and the nexus player doesn't find them.
Thoughts? Solutions? any help would be greatly appreciated.
Click to expand...
Click to collapse
This happened to me also. I was able to reset the PS3 controller by briefly pushing and holding a paper clip in the small hole near the top-right corner of the label on the back. After I did that, I followed the instructions in the video at https://youtu.be/EKzwzlH1WAU and I'm happy to report that my PS3 controller works wirelessly again with my Nexus Player.
Thanks for this. It heller me alot.
I I know this has been asked to death already.. I'm sorry.. But I can't seem to pair the remote! Nothing came up automatically as it did in Stock to pair. And home + back button isn't working. How can I enable it without another device? Any ideas? Thanks!
I've tried factory reset, no go. It won't even reset my OS. It'll be exactly the same. Straight to home screen, no prompt to set up.
I've tried using that remote app, but that requires the two devices be connected on the same network, which isn't something I can do. I have absolutely no control over the player.
The remote works. I can pair it to my S3 and it'll work nicely. I can't get the NP to appear as a Bluetooth device. I think that might be the issue. Help!
I just reflashed and got the same thing. Bluetooth doesn't seem to work.. Flashed stock and got remote access back. Flash custom, lose it completely.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Do not create multiple threads for the same issue. Thread closed.
BACKSTORY: So I just got my Nexus Player about three days ago. I used stock for all of a day and had no issues. I decided I would try Lollirock v2.1. It loaded with no issues and I was able to get it working. I don't have an OTG adapter so I used ADB to configure the wireless and then found ADBControl to control the device through ADB. I got it working but found that it really didn't align with my desires. I also began having Bluetooth issues with the remote. The remote would randomly drop pairing.
I came home from work the other day and found that the box was not responding over wireless. I just reset power to it and, upon recovery, the wireless and Bluetooth were no longer responding (icons gone from status bar too). I decided this was some sort of Lollirock flakiness. I flashed the device to stock LMY47V. The device recovered and it was apparent that Bluetooth didn't work. I couldn't pair the remote and the device wasn't visible when I pressed the button on the bottom. I was able to pair the remote to my phone so this ruled out a remote issue.
I reflashed Lollirock so I had USB debugging by default and attempted to research in a root shell. I was unable to activate wireless. I saw a random suggestion that wireless issues could have been caused by the Use Network Time setting so I disabled that on Lollirock with no better results.
PROBLEM: Wireless doesn't work at all. In a shell, netcfg is not showing a wlan0. I can't seem to make progress because of this. I assume Bluetooth is trashed because of the same problem as with the wireless. I tried flashing an older stock package with no luck. It seems dead, Jim. Any suggestions?
Sent from my D6503 using Tapatalk
jawnah said:
BACKSTORY: So I just got my Nexus Player about three days ago. I used stock for all of a day and had no issues. I decided I would try Lollirock v2.1. It loaded with no issues and I was able to get it working. I don't have an OTG adapter so I used ADB to configure the wireless and then found ADBControl to control the device through ADB. I got it working but found that it really didn't align with my desires. I also began having Bluetooth issues with the remote. The remote would randomly drop pairing.
I came home from work the other day and found that the box was not responding over wireless. I just reset power to it and, upon recovery, the wireless and Bluetooth were no longer responding (icons gone from status bar too). I decided this was some sort of Lollirock flakiness. I flashed the device to stock LMY47V. The device recovered and it was apparent that Bluetooth didn't work. I couldn't pair the remote and the device wasn't visible when I pressed the button on the bottom. I was able to pair the remote to my phone so this ruled out a remote issue.
I reflashed Lollirock so I had USB debugging by default and attempted to research in a root shell. I was unable to activate wireless. I saw a random suggestion that wireless issues could have been caused by the Use Network Time setting so I disabled that on Lollirock with no better results.
PROBLEM: Wireless doesn't work at all. In a shell, netcfg is not showing a wlan0. I can't seem to make progress because of this. I assume Bluetooth is trashed because of the same problem as with the wireless. I tried flashing an older stock package with no luck. It seems dead, Jim. Any suggestions?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Same issue here, after restoring stock no bluetooth stack
barnesc64 said:
Same issue here, after restoring stock no bluetooth stack
Click to expand...
Click to collapse
I never resolved the issue and ultimately replaced the device with a FireTV instead. I'm much happier with the Amazon device.
Sent from my SM-G900V using Tapatalk
I have flashed probably 30 nexus players with lollirock never once had a problem! I wonder if you had the wrong file in folder or bad download. I left a root.img from nexus 6 in platform-tools and it booted but was acting crazy but remembered that it was for nexus 6 and reflashed was all good!
if you have access to a usb keyboard of some sort and an plug into your nexus player, find and download (sideload) an android terminal app. in the command prompt, enter:
su
service call bluetooth_manager 8
service call bluetooth_manager 6
i found that info here: http://forum.xda-developers.com/nexus-player/help/bluetooth-issues-sixaxis-app-t2987998
hope that helps.
Need some advice please...been trying to connect my LG G4 to my Nexus Player via the AndroidTV Remote app and haven't had any success.
I've tried connecting via WiFi and BT but neither work. I can see the device, but upon attempting to Connect via WiFi the screen pauses like it's trying to start a connection, but flickers back to the device list.
Trying via BT pairing I can connect my phone but the App won't launch (even with phone WiFi turned off).
Any suggestions here? The only thing I haven't tried doing is taking my old Logitech Revue off the network to see if there's perhaps some interference with the AndroidTV connector.
Doesn't look like anyone has experienced this issue, on the forums -- would definitely appreciate help as the Nexus Player on-screen keyboard is terribly slow!
Thanks.
Bump!
Same issue here with my Nexus 6p and Nexus player....
Please help!
oblivion0 said:
Need some advice please...been trying to connect my LG G4 to my Nexus Player via the AndroidTV Remote app and haven't had any success.
I've tried connecting via WiFi and BT but neither work. I can see the device, but upon attempting to Connect via WiFi the screen pauses like it's trying to start a connection, but flickers back to the device list.
Trying via BT pairing I can connect my phone but the App won't launch (even with phone WiFi turned off).
Any suggestions here? The only thing I haven't tried doing is taking my old Logitech Revue off the network to see if there's perhaps some interference with the AndroidTV connector.
Doesn't look like anyone has experienced this issue, on the forums -- would definitely appreciate help as the Nexus Player on-screen keyboard is terribly slow!
Thanks.
Click to expand...
Click to collapse
Same glitch here. Changed batteries but no luck. Was on beta, then reverted back to stock N. But still same problem.
Sent from my SM-G950U using Tapatalk
daftlush said:
Same glitch here. Changed batteries but no luck. Was on beta, then reverted back to stock N. But still same problem.
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
Yeah don't think I ever solved this one. Moved on to a Nvidia Shield TV, the Android TV remote app works reliably. Good luck!
When I try and cast apps using Chromecast, my V20 will either say it cant connect or connects but doesnt cast anything. This has never been an issue using my other android devices. Anyone else having this issue? Ideas of what might be going on?
Hi there, I just tried it and it worked fine for me.
It works fine with all three of my devices. Try rebooting the Chromecast and rebooting the phone.
bat8580 said:
When I try and cast apps using Chromecast, my V20 will either say it cant connect or connects but doesnt cast anything. This has never been an issue using my other android devices. Anyone else having this issue? Ideas of what might be going on?
Click to expand...
Click to collapse
Working fine here...
Sent from my LG-H918 using Tapatalk
Chrome cast is Google home now correct me if I'm wrong
Sent from my iPhone using Tapatalk
mobilecutzzfa said:
Chrome cast is Google home now correct me if I'm wrong
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Off topic, but no. Chromecast is still Chromecast. The app for it (which itself was never called Chromecast, but rather Google Cast) was redesigned and renamed Google Home with the introduction of Google's Google Home device. The app is now there to serve any "Google" device they release.
On my Sony Android TV the app is called Google Cast that's built in and I can cast from my phone or tablet like you normally would with a Chromecast dongle. It seems Sony broke the ability to cast with a recent update to the TV, which is unfortunate because Sony updates are few and far between. I'll just invest in the new Chromecast and bypass the built in app all together. It isn't the phone after all.
I have the same problem. I rebooted the Chromecast receiver and my LG V20 and it doesnt cast, even to a Chromecast 2.0 device. I tried with my old Galaxy Note 4 and it works fine.
I wonder if this has something to do with Android 7.0 Nougat?
I have h990ds and chromecast 2.0 and everything works well ?
Sent from my LG-H990 using Tapatalk
bat8580 said:
When I try and cast apps using Chromecast, my V20 will either say it cant connect or connects but doesnt cast anything. This has never been an issue using my other android devices. Anyone else having this issue? Ideas of what might be going on?
Click to expand...
Click to collapse
I just got my LG V20 and was having the same issue with Chromecast. One day it would work and then the next not. I found it only works if I have my wifi on my LG set to the 2.4mgz. It will not cast if logged on to the 5mgz. I assume most of us now have dual modems. When in my office my phone goes on the 5mgz. So have to change it to 2.4 to cast. has been working every time so far.
Works like a charm for me, both in ChromeCast and Nexus Player.
I have 3 Chromecast, and 3 Chromecast audio, some on 2.4GHZ, some on 5GHZ and they all work fine using my v20 no matter if it's connected to 2.4GHZ or 5GHZ.
Sent from my LG-H918 using XDA-Developers Legacy app
aerospacecase said:
I have the same problem. I rebooted the Chromecast receiver and my LG V20 and it doesnt cast, even to a Chromecast 2.0 device. I tried with my old Galaxy Note 4 and it works fine.
I wonder if this has something to do with Android 7.0 Nougat?
Click to expand...
Click to collapse
Not an issue with Android 7+. Works perfectly for me and many others. If you're still having trouble try some of the troubleshooting steps mentioned above, like rebooting your v20 and rebooting your ChromeCast. You could first try turning your WiFi on & off, as cycling your data connection often helps with connectivity issues (Either WiFi or carrier, depending on the situation. Though obviously it's Wifi in this scenario)
Sent from my LG-LS997 using Tapatalk