yashsingh1/xdaforums huggingface dataset:
[Nexus Player Android Development] npjohnson:
It works amazing (With Leanback GApps)! And I initially liked the direction DHacker/CM was heading with Android TV (That being that props could set either the TV or the Full Android Experience.

[MENTION=4112553]dhacker29[/MENTION] The Full Android GApps package linked in the OP breaks the ROM, the only fix is to remove this prop: ro.cm.statusBarComponent=<component>

As I read in this (Merged) commit (http://review.cyanogenmod.org/#/c/96393/), choosing Trebuchet as your Default Launcher through LB Settings is now the way to enable the statusbar/enable the ability to activate the navigation bar via prop (qemu.hw.mainkeys=0), as stated by this (Merged ) Commit (http://review.cyanogenmod.org/#/q/I03871d2c3fd26658f5d99bc40a3916ad0e5674f0,n,z).

I clean flashed the newest (6/25/15) build, and the full GApps which resulted in constant UI FC's until I pushed a modified Build.prop to /system (via ADB) that did not contain the line ro.cm.statusBarComponent=Phone.StatusBarActivity (not the correct prop, but something similar was there). Then the device functioned as expected, but without status/navigation bar, which makes it hard to use. I tried to activate the Navy. bar with qemu.hw.mainkeys=0, but it had no effect.

I tried a clean flash with LB GApps, and then added those two props manually, however, the result was identical.

Thank you for your work on this ROM. The LB GApps Package in conjunction with this ROM runs very well (Small Bug: The latest Trebuchet defaults to vertical scrolling App Drawer, which the NP remote can't select).

Also, I have the ADT-1 (molly), which is an Android TV Device, and we have a fully functional CM12.0 device tree/vendor tree, but are having serious issues getting CM12.1 to build with it. I was wondering if you may be able to help debug that, as not many people know how the CM-TV config works.

Thank you ahead of time.
[Nexus Player Android Development] halfluck:
+1 this would be amazing, It looks like some hard work has gone into getting a good working Custom Recovery, The last step is getting CM12.1 to build working, Looking forward to using the CM App Draw :)

Cheers Rob.
[Nexus Player Android Development] x7uc0x:
Does someone konw about the mic issue?, Do we have any news about it?
[Nexus Player Android Development] Link_of_Hyrule:
I haven't really seen much work being done with this ROM in general lately hopefully we'll see some progress soon. Unfortunately the latest build doesn't even get past the starting Android screen so I had to downgrade a couple builds back I was able to get 6/29 to work. Hopefully whatever the problem is gets fixed soon.
[Nexus Player Android Development] _Dennis_:
Mine did the same thing, stuck at starting apps. But I hard restarted the box, worked fine. Not sure what happened but if next time you upgrade it does the same thing try unplugging it, then re-plugging it in.
[Nexus Player Android Development] Link_of_Hyrule:
Yeah I'm sure if I wiped then it would have finished but I wanted to watch stuff and not deal with that.
[Nexus Player Android Development] WhiteWidows:
The maintainer [MENTION=4112553]dhacker29[/MENTION] hasnt been on xda or done any device specific fixes in over a month. Without proper support nightly will begin to have issues.

I'm glad he got this working for us but he seems to have abandoned the fugu. Hopefully someone else can pick it up.
[Nexus Player Android Development] oakieville:
every build i have test has stuck at starting apps or at finishing boot. reboot then it boot ups but i have many issues running this. for one trebuchet main screen flashes sometimes, sometimes just black background but never just normal background. wifi has reset itself twice. and few other issues. with some tweaks here and there got it running smooth wallpaper working seemed no more issues rebooted back to same issues.

when it does run its fast and kodi runs great.
[Nexus Player Android Development] Ambious:
I've experienced that too but only after upgrading. Regular reboots work fine here (I'm using Leanback though).
[Nexus Player Android Development] oakieville:
how did you get wallpaper and stuff working for me anytimei get things working like wallpaper it will stop after reboot

this is my run first at android on x86 as well and im trying to build a flashable package but need it stable enough to run reliable

its seems my issue are due to status well build.prop edits for status bar. im using full gapps not leanback i removed the edits to build.prop for status bar now i dont have status bar (didnt work correctly anyway), and have no more issues as far as i can tell.
[Nexus Player Android Development] Link_of_Hyrule:
I have faith that dhacker29 is just taking a small break and that he hasn't abandoned us. He hasn't worked on any devices for a while so I'm sure he was just tired after spending so much time on it.
[Nexus Player Android Development] Ambious:
I'm using Leanback Launcher so wallpaper isn't an issue since there isn't one.
[Nexus Player Android Development] xaudiblex:
Out of curiosity, is anyone having issues with losing bluetooth device profiles after a deep sleep? Every morning, I have to reboot to get my bluetooth devices back.
[Nexus Player Android Development] oakieville:
full or leanback gapps? that was one of the problems i had and many others on full gapps until i removed status bar.
[Nexus Player Android Development] xaudiblex:
I am actually on leanback. I also get crashes from the Bluetooth Share & Leanback launcher at least once a day now as well.
[Nexus Player Android Development] n00bpwner:
I just installed this. works pretty good so far. netflix volume was super low so i connected via chromecast on the phone and increased that way.
[Nexus Player Android Development] brolic925t:
Go to settings then sound then volume. Duhh. In regular settings. Not netflix or leanback
[Nexus Player Android Development] qtotter:
Just a question. Why is VPN in the settings menu left blank??
[Nexus Player Android Development] TheLoonyRebel:
The only thing I noticed is when I try to search on say Play Store it won't search after I type in my search and then hit enter. This is happening on the 7/16 nightly. Anyone else having this happen?
[Nexus Player Android Development] ste_mir:
Any updates on whether the ROM is still supported or not?
[Nexus Player Android Development] lolwatpear:
is netflix actually working for anyone? every nightly has given the 'incompatible error.'
[Nexus Player Android Development] mattspew:
How are people finding this ROM? I can handle a few bugs in full Android, but Leanback must operate as reliably as stock; Netflix, Kodi, YouTube and voice search must work perfectly for me to ditch stock.

Does it tick those boxes for everyone?

Not as important, but does Xposed with YouTube Adaway work on the NP and does it work on Leanback YouTube app?

I'd love to ditch stock and open up full Android, but I don't want to introduce complexity/bugs to the non-techie users in my house. Thanks for your input!
[Nexus Player Android Development] lolwatpear:
Netflix and voice search doesn't work. Honestly, this has been an annoying experience. So much for being a Nexus device
[Nexus Player Android Development] mattspew:
Can you expand on that; is Netflix and voice search broken inside the Leanback launcher, full Android or both?
[Nexus Player Android Development] lolwatpear:
The leanback version of Netflix is broken for me. I get '....is not compatible' with your device error. This has always happened for me since I installed CM and updated it (freshly) every time. One time I did install the Sony Netflix apk from their tvs and it worked temporarily, but eventually gave me the error.

As for voice search, it just doesn't work system wide using the remote. It doesn't detect your voice.
[Nexus Player Android Development] mattspew:
Right, thanks for the input. I'll stick with rooted stock for now.
[Nexus Player Android Development] ajbiz11:
[MENTION=4112553]dhacker29[/MENTION] [MENTION=3150613]bkjolly[/MENTION] Is there any chance you could point me to which config actually enables the framework to compile as Leanback and not as standard phone/tablet?

I may or may not want to work on porting Leanback to another device to use for development and or work on porting Android TV to other devices
[Nexus Player Android Development] xaudiblex:
You can use APK studio to decompile an apk. Then you would just need to add the leanback code launcher to the androidmanifest.xml file. nVidia has a good guide on how to do it:

https://developer.nvidia.com/android-tv-developer-guide

Code added to androidmanifest.xml:

<category android:name="android.intent.category.LEANBACK_LAUNCHER" />

I usually add it following this line of code:

<category android:name="android.intent.category.LAUNCHER" />

Hope this helps.
[Nexus Player Android Development] ajbiz11:
This seems to be the opposite of what I want

I'm looking to enable Leanback features at a framework level in the ROM at compile time, not make an app work on the existing set top box.
[Nexus Player Android Development] joser916:
Fresh install of cm 12.1 20150723 nightly full gaaps that was provided in the op from this form.

Runs ok but as soon as I connect any usb mouse or a wireless usb mini keyboard mouse combo, I'll get this message pop up: unfortunately, the system ui has stop. Disconnected mouse and runs normal so How do I fix this?

And installed kodi x86, didn't matter what version I get same issue, kodi opens I see loading screen and it stops and end up on home screen of nexus player, tried side load kodi, tried kodi from play store, tried older kodi and it won't load after first time run screen. Please help. Tried another fresh install of this Rom and nothing.
[Nexus Player Android Development] fzurita:
I'm having issues installing CM 12.1. I'm getting this error when trying to install using the custom recovery:

"can't install this package on top of incompatible data"

Any ideas?
[Nexus Player Android Development] Cuzz1369:
Uhm, wipe ur data...
[Nexus Player Android Development] fzurita:
OK, this must be new. It didn't seem to be required before. Thanks
[Nexus Player Android Development] Cuzz1369:
Are you updating cm12.1 or installing on top of another ROM?
[Nexus Player Android Development] fzurita:
I'm installing on top of stock. My usual procedure was usually to install then wipe data. But this failed this time.
[Nexus Player Android Development] Cuzz1369:
Must've added a check or something...
[Nexus Player Android Development] fzurita:
The latest nightly build has some issues. The system UI keep crashing over and over when I have the mouse or keyboard plugged in. The problem with that is that I need those plugged in for the initial setup.

Also, the system ui didn't crash before I installed the GAPPS, only after.

What's the latest nightly that worked for the most part?
[Nexus Player Android Development] -blacknight-:
I brought a nexus player, updated 5.1.1, how to root? Use mskip soft? Or wufesh?

Gửi từ SM-G7102 của tôi bằng cách sử dụng Tapatalk
[Nexus Player Android Development] WhiteWidows:
The CM maintainer has abandoned this ROM but the CM build bot continues to build. This ROM will get progressively worse unless some one does device specific fixes for it.

I would stay away from it as nothing has been done with it in over 2 months.
[Nexus Player Android Development] prozack1983:
I'm using 7/18 and it seems to work well as far as I can tell.
[Nexus Player Android Development] NiN39Z:
Can someone tell me which build has everything working except the mic issue? So far it seems like the 6/20 build is the golden build with everything working except mic. Is this the build that even Netflix is working on too?
[Nexus Player Android Development] npjohnson:
Does Status Bar work in this build? I'm trying to track down what change broke this.
[Nexus Player Android Development] lasphyxial:
I'm on 7-27 w/ leanback gapps no issues..
[Nexus Player Android Development] ellopr:
I tried to do a search but didn't find anything about this. I am using the nexus player in a 4K samsung tv, I had a 1080p tv previous to this and everything was working right.. And although the interface works pretty well (full screen) and after using the overscan it fit the whole screen correctly. Once I start to play a movie through Play Movies, Hulu Plus, Netflix or any video player they don't show right. I have a border all around the movie frame. It happen on youtube videos too. So it is frustrating cause they look awful with that grey band all around the videos. Applications like Chrome does the same, but if I play a video on full screen from chrome it does fill the entire screen.

Any suggestions?? I am thinking about resenting the Player and going with the stock rom or Android M just to see if is the same. Anyone with a 4k tv that does not has this problems??

Thanks in advance.
[Nexus Player Android Development] Ambious:
I've had this happen to me too, but I overcame it by adjusting the overscan to under-compensate a little. Didn't find a 'one fits all' solution, and mostly it's up to the app developers to allow for some padding outside the app's borders, but unfortunately it doesn't always work or apply for playback so you have to manually over-adjust.
[Nexus Player Android Development] ellopr:
THANKS. Have you used the Nexus Player with the stock rom and had the same problem??
[Nexus Player Android Development] tjsooley:
I just switched back to stock and the developer options has a menu for hdmi resolution I did not check it out. BTW stock is so much faster than cm12.1 and I forgot how usefully the remote voice search is.
[Nexus Player Android Development] Link_of_Hyrule:
Are you coming back [MENTION=4112553]dhacker29[/MENTION]? we miss you :'(
[Nexus Player Android Development] mattspew:
Just noticed I can't get Dolby Digital 5.1 on Netflix since replacing stock with CM12.1...

Bugga!
[Nexus Player Android Development] Ambious:
I couldn't get it on stock either. It's Netflix's abysmal app.
[Nexus Player Android Development] mattspew:
I just restored my stock backup and Netflix is outputting DD+ again.

Will stick with stock for now; I didn't look at the build number of Netflix, but the version number is the same and there isn't a newer version in the store.

Honestly don't know if it was CM or Netflix.
[Nexus Player Android Development] Haiallus:
Bluetooth Audio Lag Issue

This ROM is great, but I found bluetooth audio lag when using bluetooth headset.

Can you please check and provide fix, thank you.

FYI, I tested with Anriod M and LolliRock there is NO bluetooth lag.
[Nexus Player Android Development] ste_mir:
I dropped it.

Back to rooted stock.

Without support this ROM is pretty useless.
[Nexus Player Android Development] pbanj:
most videos wouldnt play and when looking at the thread for the addon it seems to be an issue people living in the us have so i just removed it.
[Nexus Player Android Development] thunderthumbs02:
I see, I guess I haven't used it enough yet. I've just watched TV episodes and have had no problems.
[Nexus Player Android Development] xaudiblex:
I am having the same issues playing videos in the kodi plugin. Can't seem to get most videos to work...
[Nexus Player Android Development] bkjolly:
Kodi works great for me. What addons are you using?
[Nexus Player Android Development] pbanj:
we where talking about the amazon prime video addon
[Nexus Player Android Development] bkjolly:
There's an addon for that in Kodi that works great.
[Nexus Player Android Development] pbanj:
do u have a link as the only one i found has issues with people who live in the us
[Nexus Player Android Development] lafester:
It works great as long as the shows you want to watch will play. I just use the app
[Nexus Player Android Development] bkjolly:
I got it from Super Repo there are 2 one just says amazon on says amazon instant video. The Amazon instant one is the one that works for me. Honestly I use the Genesis video addon more than anything.
[Nexus Player Android Development] colafloat:
thanks so much i'll try tonight
[Nexus Player Android Development] jschill31:
Hello,

Just wanted to take a minute and say thanks... The only thing I noticed is the stock CM root did not play nice for me while in leanback. I downloaded supersu from the play store and updated binaries and now good to go. Seems to be snapier when using the remote and virtual keyboard. I assume we are ok to use your device tree if we want to build at home?

Cheers
[Nexus Player Android Development] tomalak007:
What are the adb commands to install this in recovery? I tried to sideload but it said "no protocal" or something. Sorry for the dumb question if its obvious
[Nexus Player Android Development] parkerlreed:
A2DP audio seems to still not be working even in this CM 12.1 build. Is there some routing that has to be changed? I tried SoundAbout but still couldn't get audio out of my headset.
[Nexus Player Android Development] dhacker29:
The ui for apop's is a little off for the SU requests but it does work. And yes you can build from the cm tree for yourself not a problem. I submitted to start nightlies. I will post a new build based on 5.1.1 tomorrow have made quite a few changes.

I am adding what I "think" is needed for a2dp in the new build. You can let me know after I post it later today.
[Nexus Player Android Development] dhacker29:
Just FYI cm-12.1 nightlies will start tonight after the first build is out I'll update the thread to show the download link and only post unofficial builds for test features.
[Nexus Player Android Development] pbanj:
nice, is 5.1.1 going to still be 12.1?
[Nexus Player Android Development] dhacker29:
Yes the api didn't change
[Nexus Player Android Development] nachunsa:
Bluetooth a2dp external headsets and speakers support please....

LolliRock v.2.0 ROM is Bluetooth a2dp external headsets and speakers supported.

Be "Unofficial CM-12.1 for Nexus Player (fugu)" ROM Be ROM support please....

Thank You.:)
[Nexus Player Android Development] dhacker29:
:D ok

04-25 06:52:58.563: I/audio_a2dp_hw(171): a2dp_command_data: A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 0

04-25 06:52:58.563: I/audio_a2dp_hw(171): skt_connect: connect to /data/misc/bluedroid/.a2dp_data (sz 10240)

04-25 06:52:58.568: D/A2dpStateMachine(2699): A2DP Playing state : device: 0C:E0:E4:74:D7:9A State:11->10

04-25 06:52:58.568: V/HeadsetService(2699): Received BluetoothA2dp Play State changed

04-25 06:52:58.568: D/HeadsetStateMachine(2699): A2dp Play State Changed: Current State: 10Prev State: 11A2pSuspend: false

04-25 06:52:58.568: D/HeadsetStateMachine(2699): A2dp Started 10

04-25 06:52:58.996: I/str_params(171): key: 'a2dp_sink_address' value: '0C:E0:E4:74:D7:9A'
[Nexus Player Android Development] WhiteWidows:
[MENTION=4112553]dhacker29[/MENTION] Thank you so much for getting a recovery and CM12 on our neglected fugu!

I would like to pick you brain on something if have been working on here and there but have been failing to accomplish. I was working on getting ffmepg built into android but never could on 5.0. The reason being I hoping to get MPEG2 HW decoding working so that streams from my HDHomerune Prime could be used in the Live Channels application. Streams can be opened in the HDHomerun View app but its using software decoding due to the NP not having the licencing in the xml. When trying to enable MPEG2 HW Decoding in setting is fails on CM12 as well. I thought CM had this built in.

Next is getting DTS and AC3 output from Plex and other apps using Androids default media player. As of right not Plex will transcode and output PCM to my Onkyo receiver and I believe this to be a limitation with androids default media player. Can you confirm CM12 has the external codecs needed for DTS and AC3 if not could it be possible to incorporate this in future builds via device specific merges?

Heres a thread I started a while ago...

http://xdaforums.com/nexus-player/general/dev-thinktank-t2960700

Thanks again for getting CM12 on the Fugu
[Nexus Player Android Development] belrik:
So, this is now unmaintained? Shame cos the stock ROM doesn't perform great.
[Nexus Player Android Development] mattspew:
Interesting, I find stock to be smoother and it boots much faster.
[Nexus Player Android Development] belrik:
I meant relative to other devices. This nexus player on stock firmware is less smooth than almost all my other devices and I was hoping that a good CM port could improve that. Really hope someone is able to take on this port.
[Nexus Player Android Development] mattspew:
I had the same hopes, but I literally came onboard as support vanished.

However unless you want full Android, stock has everything you need for the big screen experience; simple interface and remote, runs Kodi, can do digital audio and so on.
[Nexus Player Android Development] gdsbalaji:
Does any1 know if USB webcam/mic works in stock lolli or M?

Sent from my Nexus 5
[Nexus Player Android Development] koivth:
Stock runs great for me but I've had to use CM builds on my nexus player due to having an old TV with few overscan correction tools. On stock the overscan was always too much to use comfortably. Any way I can somehow merge CM's overscan settings into stock build??

Edit: UI Tuner on the play store worked for me to adjust overscan.
[Nexus Player Android Development] nurunet:
Do we know for certain that support has stopped?
[Nexus Player Android Development] koivth:
Nightlies are still being released for this device on cyanogenmod's website - leads me to believe it is still being officially supported.
[Nexus Player Android Development] jacoghi:
Has anybody ever tried Vanir for the Player?

http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/fugu/

There are nightlies and they are considered to be stable (non experimental) by the team.

EDIT: Tried it myself. Works pretty well if you are looking for a stable CM 12.1 for AndroidTV. This doesn't have the full play store netiher the navbar as we do in Lollirock, so will be sticking with that one for now.
[Nexus Player Android Development] koivth:
In the OP of this thread there is a link to full Android experience gapps (not lean back).

I haven't tried it myself but should give you experience similar to lollirock?

Edit: I reread op and still no status bar even with full gapps
[Nexus Player Android Development] Rektifying:
Hello,

I recently purchased a Nexus Player and I really like it over my Apple TV gen 3 that I sold. I am making the move to Android from Apple. I have been using iPhones far to long and I am bored with them. I plan to get a new Nexus 5 upon release this year.

Anyways, my Nexus Player is having an issue where it will not wake from sleep. I have to unplug it and plug it back in to make it usable again. It is fully updated and factory reset. Does CM12.1 for the Nexus Player have any issues with waking from sleep? I planned on rooting my Nexus Player anyways. I already purchased a USB OTG cable and Logitech K400 because I really want to be able to use Google Chrome browser on my TV. :D Any info on this would be greatly appreciated! Thank You!

Also, if I root, unlock the bootloader, and install CM12.1, will I still be able to update my Nexus Player to Android M when it is released by Google? Will I have to revert to stock and unroot? How do I or do I need to make a backup of the stock firmware so I can re-flash it back to stock?

Sorry for all of the questions, but just one more! lol. What is the BEST rooting method? Would prefer to keep the stock kernal if possible. Thank you for your time!
[Nexus Player Android Development] Link_of_Hyrule:
If you want to keep using CM you'll have to wait for them to release CM13 (I'm guessing this is what it's going to be called) if you want to be Android M based and CM other wise there should be a stock rooted version of M I'm sure.
[Nexus Player Android Development] dhacker29:
What "support" is there to be done? I have fixed everything that I know how to fix. I don't plan on doing anything more with this other than keep it building until M source is out.