yashsingh1/xdaforums huggingface dataset:
[Nexus Player Android Development] Link_of_Hyrule:
Well after a night if mostly hassles I've decided to just go back to cm12.1 since it's buggy and it has no real advantage over cm12.1 anyways. Would be nice to see the extra codec support backported although I'm not sure it'll benefit me at all. I'm still hoping for the remote's microphone to get fixed as well as webcam support in Hangouts ?.
[Nexus Player Android Development] Action123:
Just took the 5/29 nightly and I'm getting pretty bad screen tearing on scrolling. Doesn't affect media playback, but god is it annoying. Any ideas?
[Nexus Player Android Development] 1den:
Hi dhacker29,

if possible ported to Official CM-12.1 (with android tv ui and gaps vs) for intel cpu based tv box? Nexus player also intel cpu, except gpu :D
[Nexus Player Android Development] nunyabiznas:
if you switched from full gapps to leanback you have to do a full wipe including data/media and install using adb sideload. that app and some others update and store data to /data and /data/media and the data is incompatible.
[Nexus Player Android Development] pyrotechr:
so i followed all the instructions and got cm12 loaded on my nexus player BUT now when i am enable USB debugging from settings... i can not see an ADB confirmation on my devices... i am stuck at unauthorized on my cmd panel... can anyone help?

edit: I have also tried revoking old permissions

and i have also been getting a strange error...whenever i plug in my USB otg cable... my system UI starts throwing non stop errors until i unplug it

---------- Post added at 04:37 PM ---------- Previous post was at 04:22 PM ----------

Ok so i figured out that when you unplug and plug power cable on the nexus player and hold the sync button at the bottom of the player... it goes into bootloader mode.. fastboot works for me... i can reset everything now
[Nexus Player Android Development] :
sorry, but i tried searching this thread and having a hard time understanding. i have some major overscan issues with my tv and i see people are flashing an overscan.apk. i did a google search for it and it seemed like it was apart from the downloads on here.

i know i need to root but if i flash this rom, it will give root, i get that. so i may go this rom, but i want to make sure i dont need a mouse to use the nexus player after flashing. i looked at the screen shots and it looked like normal but then had a launcher on 2 other screen shots.

my tv is downstairs and pc upstairs. id have to carry the tv and player upstairs and i dont feel like doing that if i dont have to. so could someone answer a few questions for me please?

will i be able to fix my overscan issues unrooted and with just an app? if not, using this rom with the overscan apk? i dont want to get into xposed crap tbh

will i need to have a mouse connected to the nexus player to use it due to the launcher?

sorry, im fairly new to android. only been using one for about 1.5months.
[Nexus Player Android Development] danigraham:
Ahhh, a new Android user! Awesome ?

We had over scan issues in ours too but the TV settings menu cleared that right up. Just a thought.
[Nexus Player Android Development] insanedrunk:
Settings> display> overscan calibration at least on this rom, some tV's allow to adjust to over scan auto magically.
[Nexus Player Android Development] red5pade:
Sounds good to me. I'll work on it some time. Thanks
[Nexus Player Android Development] :
can someone do a install guide.

i have everything downloaded but i dont know what to do with it.

i dont like to flash roms through a computer... much rather put it on the device itself and flash from there but i guess i need a custom recovery. i downloaded the custom recovery but the minimal adb fastboot thing is stuck at waiting for device when i enter the fastboot flash recovery fugu_cm_recovery.img command. please give a little help. thanks

---------- Post added at 12:57 PM ---------- Previous post was at 12:51 PM ----------

found a video on youtube, so i may be good. i found it on the cm recovery thread.
[Nexus Player Android Development] insanedrunk:
On cmd type fastboot devices it should list your device on it if it's good to go, it will say unauthorized user or blank if something's wrong. If unauthorized user appears, go to your computer, and plug in the np while it's turned on and make sure you authorize the computer it's connected to when it's prompted. If blank, your device isn't recognized by fastboot, could be because your drivers aren't installed right, or your adb usb debugging is not on, to do so, go to settings> about build number and click it about 5-6 times, or whatever yours counts backwards from, and back out from the settings menu, go back in and find developer options and check usb adb debugging. Try fastboot devices again, your device should be listed then resend the fast boot command you need, make sure your files I the same folder as your fastboot tool, and you should be good to unplug your device while holding your bottom button under nexus player until you see the Google splash logo then let go, you'll see an option for reboot, recovery, boot loader, press the bottom button of nexus player to cycle through your options until you get to boot loader, press and hold your bottom button for about 5 seconds or more, release and it should take you to fastboot mode then send you command again.
[Nexus Player Android Development] red5pade:
That's weird. Adb was recognizing and then I tried it again when I got home and tried again and now its not working. Try reinstalling drivers and nothing. I at least have the boot loader unlocked I think haha. I'll try again some other time. I'm running windows 10 dev so I always have troubles with drivers. When I rooted my oneplus one and flashed a ROM, I lost connection to adb mid ROM flash and phone was bricked for 12hrs till I finally found a driver that worked. Gotta figure out the driver issues and then maybe do this ROM
[Nexus Player Android Development] insanedrunk:
Sounds dumb, but try a different cable, some cables just have the a ability to send power and not data. Some are vice versa. If course the nexus didn't need charging, just a thought.
[Nexus Player Android Development] red5pade:
Hmm, could actually be it. I took the cable I was using to charge my phone when I drove to San Antonio. When I got back I took the cable out of my wife's truck cause its longer and all of a sudden nothing worked.

I'll try tomorrow with my nicer cable
[Nexus Player Android Development] danigraham:
Hey I live in San Antonio! ✌
[Nexus Player Android Development] jschill31:
Hello,

I have had this happen a lot. Nothing seems to keep this from happening on my system except leaving it in an app like Netflix. Changing DayDream or sleep settings has had no effect. Even with leaving it in Netflix I always have to hit the remote twice... I do think it is more to do with whatever the player is hooked up to than the player itself. I run mine through an Onkyo amp which looks for a HDCP handshake. The first press of the remote to wake unit actually causes video output to stop...the second wakes the unit and I am back in Netflix. Those of us having waking issues are more likely caused by HDCP handshakes rather than the player itself. I design and build retail showrooms using 50+ monitors.,,,HDMI actually sucks to work with and it all revolves around HDCP.

Cheers
[Nexus Player Android Development] insanedrunk:
I got mines to not get locked up by ticking the option to stay awake in developer options, but it's always on, till it's fixed that's how I prevent mine from going into deep sleep
[Nexus Player Android Development] Link_of_Hyrule:
I don't use any other HDMI devices and don't have wake issues.
[Nexus Player Android Development] insanedrunk:
It mostly happens when you leave it alone about 12 hours, maybe less. I don't switch tv inputs, nor HDMI ports as it's in my spare room, nothing else connected to it.
[Nexus Player Android Development] Link_of_Hyrule:
Yeah I'm hoping once the Android M Preview source code drops some of the stuff can maybe be back ported but I guess we'll see what happens.
[Nexus Player Android Development] Link_of_Hyrule:
Anyone have the new Google Play Store 5.5.15-leanback APK?
[Nexus Player Android Development] xaudiblex:
I've been patiently waiting. And by patient, I mean constantly updating and force checking for an update..
[Nexus Player Android Development] xaudiblex:
APKMirror has uploaded it to their site if your still interested

http://www.apkmirror.com/apk/google...roid-tv-5-5-15-leanback-android-apk-download/
[Nexus Player Android Development] Link_of_Hyrule:
Yeah I figured they would eventually. Going to test it out now :)
[Nexus Player Android Development] 123421342:
I have a BT keyboard/mousepad combo device. I paired it and the keyboard works but the mousepad does not. Any ideas?

edit: might have fixed it by setting the current keyboard to my "virtual" one.

Has there been any progress on getting speech to text working?
[Nexus Player Android Development] tkideneb:
I also have the "system UI has stopped" constant errors.

I have it as soon as i attach an external keyboard ( fullsize usb cord keyboard And micro bluetooth keyboard).

So pull out the usb keyboard And your error Will be fine.

Ps: is there a way to run leanback gapps And normal gapps both together?
[Nexus Player Android Development] Link_of_Hyrule:
[MENTION=4112553]dhacker29[/MENTION] anyway you can make the app to external usb storage also move the obb files natively? That would be handy to remove the need for a third party app.
[Nexus Player Android Development] insanedrunk:
Are your guys otg cable short and extension cable along with it? Or? I have no errors with just a short otg(micro usb to female usb) with just a nano sized usb receiving dongle for a 2 in one keyboard by Logitech. I had system ui errors with a non powered 4 port hub.
[Nexus Player Android Development] lK0N:
Version

Is there anyone running the lastest version? I'm on 04-30 and everytime a try a newer version I get a system ui crash or google+ needs to be reinstalled. what can I do to run the latest version without any issues?

Thanks in advance,
[Nexus Player Android Development] tkideneb:
[MENTION=1297380]insanedrunk[/MENTION]:

I use powered USB hub. But the problem was gone when using leanback gapps instead of normale gapps (cm build 03/06/2015)

The system ui error also appeared with bluetooth keyboard so use leanback gapps with this build

[MENTION=2137182]ik0n[/MENTION]:

I also had the "reinstall google+" constant errors. (04/06/2015 with leanback gapps).

Just revert tot 03/06/2015 build and you'll be fine :)
[Nexus Player Android Development] Ambious:
In the stock (non-TV) settings under "developer options" there's something called "Disable USB Audio Routing".

Could we get access to that setting in the Leanback settings as well?

It could be useful for people using USB wireless remotes suffering from this issue.

Thanks!
[Nexus Player Android Development] Action123:
Just a quick PSA: The Hausbell H7 mini keyboard is fantastic for the Nexus Player. I've been able to walk upstairs with the 'board and it still has connectivity. Definitely better than my Rii i8. Amazon has it here: http://www.amazon.com/HausBell-H7-W...=1433522262&sr=8-1&keywords=hausbell+wireless

The search for a less expensive alternative of the Logitech has ended.
[Nexus Player Android Development] lolwatpear:
can someone tell me how they are rooting this? I've tried installing the super user zip in recovery, but then it just hangs on the boot animation. Same thing when I use the root.img file method.

edit: nevermind. got root access through developer settings. forgot cm does it like that now.
[Nexus Player Android Development] philweser:
Hey guys. Loving this so far. But what method are you guys using to get all the apps to show up in the play store? I have tried the Market Helper app that worked on the player originally. Now I have have edited my build.prop to Nexus S and samsung, still no Netflix or any of the TV apps or Yidio.
[Nexus Player Android Development] Link_of_Hyrule:
The newest play store update expands the app selection quite a bit of you don't have it be sure to install it.
[Nexus Player Android Development] insanedrunk:
Nightly 6-05-15 fixed the deep sleep issue I had, and super snappy
[Nexus Player Android Development] shadrach47:
Has anyone been able to get the DD 5.1 sound option to work for the new Netflix app? I"m on the newest update and my receiver supports DD+, but I get no option for 5.1 for sound. Wanted to see if anyone on 12.1 has been able to get it to work. Thanks
[Nexus Player Android Development] denflow:
Mine Wont Cast

mine wont cast anything any help with this ?

screen says in youtube "There was a problem connecting to %1$s"

and scren casting says connecting then doesnt connect at all
[Nexus Player Android Development] mkl23:
Mic still not working?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus Player Android Development] metaljr81:
Anyone else getting video tearing? Plex, Kodi and VLC all pixellate for about 2-3 seconds every five minutes or so. Seems to happen with any video I throw at it.
[Nexus Player Android Development] insanedrunk:
I did, but I had to clear my previously open apps that run in the background to fix it, my screen tears turned into buffering problems if I didn't clear my open apps, like for example after I played nba jam and exit, watched some Netflix, then some YouTube, and tried to watch kodi after my screen would tear then continuously buffer.

https://play.google.com/store/apps/details?id=com.tni.TasKiller

This one worked great with out the use of a keyboard.
[Nexus Player Android Development] Wyldfire:
Seconded. Mine is doing this as well.

OP, have you had this issue as well? Any word on the Netflix issue? Thanks for your hard work!
[Nexus Player Android Development] Link_of_Hyrule:
You could probably change the one setting to kill apps when they are visible.
[Nexus Player Android Development] nunyabiznas:
evidently wiimotes work on android again or at least on this rom
[Nexus Player Android Development] brolic925t:
Really wish voice would work.. Realllyyy love this rom
[Nexus Player Android Development] OathYvne:
Thanks for the suggestion. How good is the battery life on it?
[Nexus Player Android Development] Action123:
Really good. I use it for almost a week and a half before it starts to give me the red light.
[Nexus Player Android Development] xaudiblex:
The build from 6th caused my bluetooth to be wonky. It erased my bluetooth profile for my logitech harmony remote and kept on crashing. Todays build feels more stable so far...
[Nexus Player Android Development] darksabre_x:
I had the casting issue at the same time as my Netflix issue. Its not a rom related bug but a leftover data related one.

I fixed it by wiping all of the storage on the Nexus player, flashing stock, wiping everything again, and then reflashing CM12. It seems there are some files left that interfere with casting and Netflix if you only wipe system and the caches.
[Nexus Player Android Development] Action123:
06/11 nightly update completely destroyed my UI. No USB control or Bluetooth. Have to wipe/reinstall.
[Nexus Player Android Development] Ambious:
Seems people with nVidia Shield are having this as well, and it's the program's fault.

For some ungodly reason it doesn't recognize Surround unless your receiver is HDMI 2.0 compliant, which most aren't.
[Nexus Player Android Development] mastafunk:
Im noticing the CM settings apk does not show ethernet options.... just picked up an OTG ethernet and it is working great, but i can only see, configure it from the leanback launcher settings. I use a different launcher and would love to see the settings in the standard settings apk so they could be accessed without switching the launcher.
[Nexus Player Android Development] BenjiHansell:
[MENTION=4112553]dhacker29[/MENTION]

looking like a really nice piece of work

any ideas on whether the Nvidia Shield will see this kind of official CM support?

PS: sorry to hijack the thread, I didn't know where else to ask
[Nexus Player Android Development] jsdecker10:
Well daggone...that surrre does stink ! ! [emoji53] One would think that as big of a company as Netflix has grown to be, it would want to create an even more competitive product that doesn't shut current subscribers/customers out of existing, as well as potential newly introduced "premium" offerings, such as this new Dolby Digital audio experience. It just seems to me that by Netflix enabling this feature only for HDMI v2.0 compatible devices, it's effectively "restricting" this newly added Dolby Digital to the "newest of the new" devices out there, which MOST people just simply do not have...yet. I just feel as if Netflix should make this feature available to anyone that has a device capable of playing DD audio, not just for the latest and greatest devices out there with the newest codecs, hardware, etc. Maybe I'm completely wrong in my opinion here, but what could possibly be the limiting factor in Netflix's implementation of this DD to where it ONLY works on devices with a HDMI v2.0 port?
[Nexus Player Android Development] raolleel:
On clean install I can not use Netflix ( -120 player not compatible)
[Nexus Player Android Development] Cuzz1369:
Oddly enough Netflix works great on the latest build for me, Plex and playstore can't seem to connect to the internet though.
[Nexus Player Android Development] Ambious:
I don't think it's intentional.

Never attribute intentional malice to something that can be more easily explained by stupidity.
[Nexus Player Android Development] Wyldfire:
Still having issues

I've tried this twice and still have had no luck. I realize the problem may indeed be mine. Can you give me the exact process you used? Did you wipe files from recovery, or from within each rom?
[Nexus Player Android Development] darksabre_x:
From within the rom? Didn't realize that was an option. I've heard a few other people say that this didn't work for them, so i'm not sure what I did differently. Anyway, here's what I did. (complete with missteps)

Started out with stock. Netflix was working. Then CM12 was released and I had to have it!!!!!

I rooted the NP and then flashed the CM recovery. I used the CM recovery wipe options as I was used to doing to clean wipe the system. I then installed CM12 and the leanback gapps. After booting CM12 I tried to install Netflix from the play store. Kept getting an error while trying to stream. Also had issues trying to cast anything to the NP.

Booted back to recovery and this time selected each wipe option twice just to be sure everything was wiped. I then proceeded to re install the stock rom. This also restored the stock recovery. I then went back to the stock recovery and chose all the wipe options that it offered me, again performing them twice.

I then of course had to re install stock again because I just deleted everything from all of the partitions. Then I rooted it. Performed the initial setup in the stock rom so I could reenable ADB. Re-flashed CMrecovery and then wiped all the partitions again just to be safe. Installed CM12 again and haven't had any Netflix or chromecast issues.

Hopefully something in there can help you find a resolution.
[Nexus Player Android Development] Link_of_Hyrule:
If you wipe everything from storage and system and install it everything works just fine.
[Nexus Player Android Development] nickhaven:
Such a great project. Can't wait for the remote mic fix.
[Nexus Player Android Development] Wyldfire:
Problem with nightlies?

Just a quick question. I noticed the nightlies for this rom stopped a couple of days ago. Is it still being developed? Is there any problem we should know about?

Thanks again for all the hard work. Just wanted some info.
[Nexus Player Android Development] WhiteWidows:
I haven't seen any commits or device specific merges from [MENTION=4112553]dhacker29[/MENTION] in a while. I hope this wasn't abandoned :confused:
[Nexus Player Android Development] Cuzz1369:
Don't think there is a whole lot to do at this point, not saying the project is dead but he has made one heck of a functioning ROM here.

I know, I know everyone wants the mic fixed but common people its not that great of a feature anyways. And looks like its one of those things you'll have to learn to live without.

On the other hand I am a git watcher and have noticed many major ROMs out there starting to keep packages_apps_TV_Settings updated and liquid recently released a ROM. So it looks like thanks to ALL of the work [MENTION=1555922]dhacker[/MENTION] has put in has convinced others to start as well. More people that know what they're doing on this project the better.
[Nexus Player Android Development] TheLoonyRebel:
Honestly I'm thinking that now we're getting more ROM support that sooner or later we'll get mic working on AOSP/CM based ROMs. Thanks [MENTION=4112553]dhacker29[/MENTION] for all the hard work you've put into the Nexus Player. :)
[Nexus Player Android Development] RootRook:
Forgot about gapps when updating

I tried updating a few days ago. I was in a hurry and spaced gapps. Now I keep getting google+ didn't install properly and it doesn't work. I tried adb commands to try and push gapps with no prevail. I somehow lost Internet connection and can't get past google+ error to turn it on. I'm assuming that the usb debugging is turned off that's why adb doesn't work. Is there anything I can try besides buying something new?
[Nexus Player Android Development] Cuzz1369:
Buying something new? Device is fine. Factory reset from recovery. Flash ROM and gapps. If that doesn't work restore the factory image. Its a nexus, there is ALWAYS a way out.
[Nexus Player Android Development] TheZero-0:
Hello everybody.

I have a question. I would like to cast from my Android devices on the Nexus Player. Just as when Chromecast Stick. Does it work?
[Nexus Player Android Development] TheShamsMan:
Yes. Very well.
[Nexus Player Android Development] Wyldfire:
Some luck...

First- updates! So glad to see nightlies again. The ROM keeps getting better. Thanks dhacker29!

As to the issue I've been chasing, I've had some luck finally. After multiple wipes (both from the stock recovery and CM recovery), the NP is letting me use it's cast feature! Unfortunately, Netflix is still stubbornly refusing to work- it keeps telling me "This version of Netflix app is not compatible with your device (-102)."

Any ideas? Thanks!
[Nexus Player Android Development] RootRook:
I've been trying for a few days now and I can get the adb fastboot tool to connect to the nexus player but only in recovery. It won't let me push gapps or the factory image threw to my sd card. Is there another way I'm not finding to do this or what am I doing wrong? Any ideas or help would be greatly appreciated
[Nexus Player Android Development] Cuzz1369:
I went through 2 Linux and 1 windows PC, non of them worked with adb/fastboot. Finally used my girlfriends win8 laptop and it worked. Need to update to the latest fastboot and adb drivers. You don't need to push the factory image, just reboot to bootloader and fastboot flash-all.bat.
[Nexus Player Android Development] npjohnson:
FYI, last 3 nightlies in conjunction with the Full GApps = SystemUI crash loop. I think the cause is the prop that dictates it has a status bar (Which I believe is set by the Full GApps?) is conflicting with something else
[Nexus Player Android Development] nickhaven:
I just clean installed 20150625 with leanback (note: leanback gapps includes the cm launcher) and I have not had any issues at all.

So much better with crashing than stock. My daughter loves Crossy Road on the TV and with stock it was crash almost once every 20 minutes or so. With this build no crashes. Keep up the great work D.