yashsingh1/xdaforums huggingface dataset:
[Nexus Player Original Android Development] zulu99:
Just an info for Android TV users.

I see some Android TV fans that try to modify standard apk with leanback banner and publish many modified apk to sideload to Android TV.

Apart that also if you sideload, the app can't work well in most case because the default dpi of Android TV show the app with bad resolution and others problems like option menu, status bar etc. etc.

If you not know, when you change the signature from the apk, the app can't be automatically updated from Google Play, so you must create another apk to have the app updated. This cause that you have always an old version or the app became old in short time.

If you need to sideload an apk, i suggest at least one with the original signature.

The fact that an user change the original signature of an apk and publish it, is legal only if the original developer not complain. So take care to do this.

https://www.google.it/search?q=google dmca

Instead an apk with the original signature is legit.

So, my suggestion is to not lose time with this modified apk. If you need the original version, is better if you download it from apkpure.com

In full Android instead you can download and update directly from Google Play. In case some free apk show as not compatible you can download it from apkpure.com

If an user use Android TV as it was invented, all ok not problem, but if an user try to transform Android TV in full Android with sideload he lose only time.

Android TV is a player for movies and songs, full Android instead is a real Android OS where you can watch movies, listen songs and all others millions things that Android can offer and multi touch is not a problem but something that help you in interaction if you use the right input device.
[Nexus Player Original Android Development] shdware:
Amazon Video works great on my Galaxy S3 phone (AICP, running 6.0.1). I think Amazon looks to see if it's a competing device (Nexus Player, Shield TV) and doesn't allow it to work unless you spoof it somehow.
[Nexus Player Original Android Development] :
Great rom. It seems that Google has finally gotten around to fixing this issue with the last security patch update. Will there be an update to bring this rom in line with MMB29T?
[Nexus Player Original Android Development] twojalfons:
Hi

Video playback does not seem to work properly. I mean video playback in chrome and in some online players. Every few minutes it stops with an error and starts playing again from the beginning.
[Nexus Player Original Android Development] pointdooly:
Quick Update for your question:

Is not possible cast the video from your phone ?

=> I can't cast Amazon Video(From My phone) to Nexus.

As far as I know, there is no feature on Amazon Video App.

Other apps(ex: YouTube) can cast a video to Nexus Player without any problem as you already know.

or watch it directly in the chrome browser in desktop mode ?

=> I can't watch directly from Chrome Browser.

In somehow, Amazon.com website knows this is the Non-PC/Computer device types and re-direct to Amazon Video App download Page.

I will keep update as soon as I could try previous apps links I found and mentioned to you.

Update

Tested all apks from links. None of them worked. Either same symptom(just can't play)

or not possible to install the apk at the beginning.
[Nexus Player Original Android Development] zulu99:
Are just security patches, nothing else was changed in the code. So i will update when something useful and necessary will be added. as ever.

I not update when there are only security patches because we have root, with root if something happen, we can see the preces, kill and delete. We have the same permissions of the system. Security patches are useful for users that are guests inside their OS :)
[Nexus Player Original Android Development] :
I am not referring to the security patches that were included in MMB29T, but the fix to the critical bug that plagued the nexus player for months described in that issue report. It took Google a long time to acknowledge it, but they finally confirmed a fix in reply 41 of that issue that was said to come out in an OTA early in January due to Google not releasing things over the holidays. Reply 55 confirmed that the latest build resolves the issue as well as this discussion on reddit which links to the exact code change. I can confirm that the latest v1.2 of this rom exhibits this video range issue simply by using google cast and it would greatly benefit from being updated with this change.
[Nexus Player Original Android Development] SkOrPn:
That patch is one of the biggest complaints with the Nexus Players software and affects thousands of users. http://www.androidauthority.com/nexus-display-bug-colors-660093 and it isn't a security patch, its a video patch so that colors are more accurate, especially blacks which are super important. This patch for 6.0 is the reason I waited until now to purchase the NP, which finally comes in the mail today, yay, lol. The latest software finally fixes the washed out colors.

http://www.xda-developers.com/xda-e...hed-out-colors-on-the-nexus-5x-6p-and-player/

http://phandroid.com/2015/12/04/nexus-player-video-bug/

https://productforums.google.com/forum/#!topic/nexus/B9w14NuBv5U

http://wccftech.com/washed-out-colors-on-nexus-5x-6p-nexus-player-youre-not-alone/

http://androidtv.news/2015/12/washed-out-colors-on-nexus-player-fix-is-coming/

https://www.reddit.com/r/Android/comments/3zl7gd/washed_out_colors_bug_in_nexus_player_fixed_in/

http://xdaforums.com/nexus-player/general/washed-colors-t3275179
[Nexus Player Original Android Development] pisicuta:
Flash boot image for native vpn support in nexus player marshmallow causes boot loops

Before anything thank you for Lollirock and now Marshmallow:good:. May you live long and prosper!

As you know, when using the native vpn in android 6 for nexus player, it attempts to connect but quickly fails showing "unsuccessful". I tried many times what you said in the thread, but only causes endless boot loops for me, after successful flash. Had to go back and restore rom with TWRP, no problem but still no vpn. Any ideas? I have seen that for some colleagues it worked. References:

Try this boot.img https://goo.gl/R1lUCc

it worked for me with built-in Android vpn.

If for you all ok, I will update the firmware in the next days. ( I will change only the boot.img that have inside a new kernel )

to install:

unrar the archive and extract the boot.img

fastboot flash boot boot.img

fastboot reboot

You must re-root with supersu last beta with TWRP recovery if you need root.
[Nexus Player Original Android Development] zulu99:
I installed the new boot.img for vpn without problems and also others users tested.

The boot.img for vpn is linked also in second post. There are no problems.

I think that your problem is that you installed supersu in the system partition. In this case you must flash again also system.img if you change the boot.img

In Android 6 we are using the last supersu beta that use system less root. If you have supersu in system partition and use a not patched android 6 boot img is normal that you have boot loop. The boot img must be patched automatically from last supersu beta.

Read about it in ChainFire thread.

To solve install boot for vpn, system and wipe data and install the last supersu beta from twrp as i suggest in first post.
[Nexus Player Original Android Development] zulu99:
You have right thanks. I will update in short time.
[Nexus Player Original Android Development] pisicuta:
I think that you are right since for root I have used and older zip from Chainfire and not the latest beta. I will wait for you to update to the new 1.3 version of this ROM and then do a clean install of all.

You will include the vpn tweak in the new version, no?
[Nexus Player Original Android Development] zulu99:
yes
[Nexus Player Original Android Development] shdware:
Can I use TWRP to dirty flash v1.3? My computer has problems with fastboot.
[Nexus Player Original Android Development] zulu99:
New version 1.3 in first post

V.1.3

Based on Android 6.0.1 MMB29T

fix vpn

fix webcam in hangouts

P.S.

I like the update, better than before.
[Nexus Player Original Android Development] pointdooly:
zulu99, I like to ask you a question because you are "THE Pro",

Just wondering...

Is there any way we could load "Remix OS" to Nexus Player like this full android ROM?

They are even plan to release FREE OS package within few days(1/12/2016) for PC(Intel/AMD devices such as PC and Mac)

Related News on XDA : Jide Announce Multi-Window Android For PC and Mac

I love your Full Featured ROM, Android TV OS(overall interface wise, but still yours better for me) specially with this small/compact powerful hardware that I did not expect this much.

Remix OS seems great alternative Android based OS if we can load on Nexus Player for some people

like their Remix Mini Devices.

Again, just wondering and asking since you have the knowledgeable professional!
[Nexus Player Original Android Development] dabanhfreak:
thanks, I assume we update through fastboot as normal, without "fastboot -w"?
[Nexus Player Original Android Development] zulu99:
If i have to say the true, yesterday, before i made this new update for nexus player, i extracted some stuff from the remix os firmware for nexus 9.

I was playing a little bit...

We must see. I want see how it work on PC, if it have all base components of Android. How is different in the core from Android AOSP and expecially if it have the input part of Android standard. ( if it follow Google guidelines, that is very important for compatibility with apps and games in google play )

http://www.videomap.it/forum/viewtopic.php?f=4&t=1557&p=2969#p2969

I like the UI, but we must see also if all apps can adapt...

So many things, but my mind was already there yesterday.

JideAccount

JideAnalytics

JideFileManager

JideFileStatService

JideMultiWindow

JideNotes

Launcher3

remixos-res.apk

p.s.

Everyone, also now, can have android x86 Marshmallow on every PC, and also installed on a usb key. From vmware you can install in the usb key instead that on hard drive. So you can have a portable OS with everything already installed. And work also relatively well if your usb key is fast. BUt the nexus player firmware is better and you can have Netflix and drm apps that you can't have on not certified devices. The big problem is this. The problem is the Mafia inside Android, not development problems.

For this reason, now , i create firmwares only for certified devices. Otherwise you can't have all apps.
[Nexus Player Original Android Development] sweets55:
I've flashed a lot of Roms but never flashed a Rom on my Nexus Player. If anyone can help me send me a pm and or if anyone has a video that could help. Thanks
[Nexus Player Original Android Development] zulu99:
is like all others nexus devices and many others android devices.

adb reboot bootloader

and with fastboot you can do everything

you can go also in bootloader mode if you long press the only hardware button of the nexus player while you power on the device.

to navigate bootloader menu with the hardware button, one press to go down, long press to select. in case you want enter in TWRP recovery directly from bootloader mode..

when you are in TWRP recovery instead you need an usb mouse, so you need and usb otg cable to connect a regular usb mouse or an usb hub
[Nexus Player Original Android Development] Jhdoubleoseven:
Should the microphone on the Player Remote work? If not, are there any plans to (or definite reasons why we can't) make it work? Thanks!
[Nexus Player Original Android Development] scottfree1:
I know no one will know this one, but before I undo all my work and rollback to lollipop I thought I'd ask.

One of the things I use the nexus for is to run plex server, since they only make an android version of the client and not the server I use "linux deploy" to run a vm of debian jesse and run plex on that. A little out their but it worked.

So I decide to give marshmellow a try, backup the vm and config file install mm, reinstall linux deploy copy vm over import config, start vm and bam life is good debian running, plex running all is well ;)

That is until I try and mount the network shares that hold my media files, then it all goes south. I've tried moving up (strech, sid version of debian) I've started from scratch with a new vm and no matter I still get VV so anyone know how/why marshmellow would/could f-with cifs in a debain vm?

mount error: cifs filesystem not supported by the system

mount error(19): No such device

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

mount error: cifs filesystem not supported by the system

mount error(19): No such device

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
[Nexus Player Original Android Development] Jhdoubleoseven:
The mount issue is on Debian? In that case I'd think you're missing a package in Debian. Don't ask here, ask around in the Debian communities first and eliminate the VM as the issue first. Good luck!
[Nexus Player Original Android Development] scottfree1:
I copied over the virtual machine that was working great in lollipop to the new marshmellow rom and now no cifs. From what I've seen mm has some changes in the security and I wondering if it might be blocking access to the network.

I've rooted/su'd but see some strange behavior there, ie in es file explorer when I turn on root explore su comes up, I grant access es seems to have root then turns it off saying "root check failed" I wonder if linux deploy is not actually getting root also?

(I've tried 3 "root check" utils and they all say rooted)
[Nexus Player Original Android Development] zulu99:
not all apps support well supersu system less, the su binary now is in different partition. You can request the update of the app to support this new root, or you can install supersu in system partition to see if this solve your problem. take a look in the Chainfire supersu android 6 thread....

I updated some time ago my server to support also the system less root, i not know if others developer are doing that.

if is a root problem.

p.s.

tested es file explorer pro

no problems with root

no problems mounting windows shared folders.
[Nexus Player Original Android Development] scottfree1:
Thanks, I saw that there were multiple root options, I used fugu-mra58k-boot.zip not fugu-mra58k-boot-systemless.zip if that makes a difference?
[Nexus Player Original Android Development] zulu99:
sure, you don't have my kernel and ramdisk you have a complete different thing. you can't change the boot image without lose things, vpn, webcam, exfat and others things. you have stock boot image, that have inside stock kernel and stock ramdisk.

install my boot.img and use the last supersu beta to root. as i explain in first post. but i think that you must reinstall everything. boot and system with a wipe of user data

tested es file explorer pro

no problems with root

no problems mounting windows shared folders.

you can install also debian no root, wine and start windows apps :) this is an x86 device.
[Nexus Player Original Android Development] scottfree1:
I had problems when I installed su with your boot image, half hour and ballz still spinning, and thought the correct setup was to use the boot image from the su page (seemed right since that setup booted right away) so my issue is to get your boot.img to work with su, I'll go back to your boot.

My procede was fastboot your boot/system fb -w to clear out system, reboot straight into twrp, install su beta from zip, reboot into system, and it sticks there at the spinning ballz, I am doing something wrong in that?
[Nexus Player Original Android Development] zulu99:
you need my boot.img, my system.img

and this BETA-SuperSU-v2.66-20160103015024.zip that you can install from TWRP recovery

http://xdaforums.com/showpost.php?p=64161125&postcount=3

the last supersu beta, automatically patch your original boot.img. If you install the stock boot image patched, you lose half of functionalities on this firmware.

You need full Android boot.img, not stock image.

I thought this was very clear to everyone.
[Nexus Player Original Android Development] sam.balia1012:
I have to give credit where credit is due: You (zulu99) have done an outstanding job on this build (rom)

It is by far the best a nexus player and Android lover could ask for...for that: Thank you very much!

I've been using a paid vpn app to establish private connection (seems ok) but latest build vpn is supported natively...could you elaborate

on how to get vpn set up

I cannot thank you enough for this ROM:good:
[Nexus Player Original Android Development] scottfree1:
Took it back to bare metal and just did fastboot boot/system/-w/reboot and it stuck in the same spot, went back to 5.1 using exact same steps and it installs, runs and roots no problem. As far as wine, I've never had any luck with with it, well that's not entirely true, it's gotten me lucky, but that was more a "hardware" fix..
[Nexus Player Original Android Development] :
He already did that awhile back. I'm fairly certain he got that link from a google search which you could have also performed to reach the same end.
[Nexus Player Original Android Development] zulu99:
I do this:

fastboot flash boot boot.img (my boot image)

fastboot flash system system.img (my system image)

fastboot - w

I enter from bootloader menu directly in twrp and i flash the last supersu beta v2.66 without start android.

But you must be able to start the system also without root and after you can root.

I tested many times and i don't see others post with same problem, so be sure to have my original boot image and system image last version 1.3

Download it again.

P.S.

Is possible that you have an old TWRP recovery ?, or when you enter in TWRP recovery you rewrite the root with old method incluse in TWRP. Do not mount system and rewrite su with TWRP. I'm quite sure that this is your problem.

Read ChainFire android 6 thread for more info.
[Nexus Player Original Android Development] scottfree1:
What you describe their is exactly how I tried it the first time and I could not boot, swapped in chainfires boot.img (fugu-mra58k-boot) straight to twrp install from zip BETA-SuperSU-v2.52.zip based on the instructions given in the rooting thread and it booted in seconds (with yours/straight to twrp/install su2.52 went to dinner and still no boot).

From the way the 2 instructions read I assumed your boot.img was unrooted and chainfires boot.img was needed to gain root, but either way I'm back to 5.1 and after a couple hours in 6.0 the ui seemed pretty much unchanged, and under the hood no cifs, no deal so I'm gonna hold @ 5.1

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

Rooting procedure:

- flash/upgrade to Marshmellow

- flash modified boot.img

- flash/boot TWRP and sideload latest v2.50+
[Nexus Player Original Android Development] zulu99:
Sorry, but you have read my post ?

To have root in this firmware, you must root it with the last Supersu beta version 2.66 otherwise you have boot loop because my boot.img is not patched.

The last supersu beta 2.66 automatically patch the boot image.

And you need my boot.img because if you use another boot.img you don't have my kernel and ramdisk, so you lose many functionalities.

BETA-SuperSU-v2.66-20160103015024.zip

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[Nexus Player Original Android Development] scottfree1:
To root you can download the last BETA-SuperSU-v2.66+ and install with TWRP recovery:

http://xdaforums.com/apps...ellow-t3219344

http://xdaforums.com/nexu...overy-t3114717

First link leads here..

All discussion should go the SuperSU BETA thread

Which refers you to here..

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

And there you find

The latest test release is:

BETA-SuperSU-v2.52.zip

And, my bad I did not notice that the version number 3 links back was different, sucker that I am I assumed "The latest test release is" meant it was the latest test release..
[Nexus Player Original Android Development] zulu99:
many things changed about root in android 6, you need a patched boot image.

But fortunately the great ChainFire created a SuperSu that patch automatically the boot image.

Not worry, many users have confusions about this in the last times. you are not alone.

And i know that my english is very bad, but i know well Android and this is the only way how i can help.
[Nexus Player Original Android Development] scottfree1:
No problem, thanks for your hard work, most all issues here are user error, thanks for your help.

A big part of the problem is the xda board and their spiffy new design. For a place that possibly has the greatest amount of technical ability concentrated anywhere on the web, they have managed to produce one of the most convoluted, unfriendly and unreadable websites I've ever seen..
[Nexus Player Original Android Development] vilator:
for updating from 1.2 to 1.3, do I just have to flash new system.img?

thanks
[Nexus Player Original Android Development] zulu99:
boot and system as explained in the first post.

1) fastboot flash boot boot.img

2) fastboot flash system system.img

3) fastboot -w

To root you can download the last BETA-SuperSU-v2.66+ and install with TWRP recovery:
[Nexus Player Original Android Development] SkOrPn:
Thank you zulu99 for v1.3. I think I am ready to try full Android on this NP finally. I let the NP update all the way to January 2016, and I have already got TWRP installed. Going to make a backup of the stock rom and move it to the USB drive first. Then give this a whirl. Going to also try your DroidMote here soon. Thanks again...
[Nexus Player Original Android Development] dabanhfreak:
Google Cast Receiver has completely stopped working (for no apparent reason).

It just hangs on the Youtube logo screen, then disconnects.

Tried emptying cache, reinstalling updated version, and other usual suspects.

Is this unique to me or are others running to this problem?
[Nexus Player Original Android Development] SkOrPn:
Yeah mine stopped working after about 1 minute of video. Youtube casted to the TV and then the video just crashed with a message that Google Cast has stopped.

How are people fixing their Overscan? My TV has the "fit to screen" settings but none of the settings properly fit the screen from the Nexus Player. On Windows 10 and all Linux distros I used the drivers and just used the slider and it fits perfectly. On Android TV I used the normal "Overscan Launcher.apk" (similar to what Kodi does) to set the proper fit to my 1080p TV and that worked perfectly. However "Overscan Launcher" is crashing with a message "Unable to start" so I wonder if I have to have the Leanback Launcher installed in order for Overscan Launcher to work on full Android? lol I only need 7 clicks to get the screen to fit correctly, at least on all Linux and Windows distros anyway. Anyone know of a working but easy Overscan app on Play store that works on this ROM? Thanks

EDIT: Well the Overscan adjustment works great in Kodi, but it did not carry over to the actual rom/apps etc. As soon as I left Kodi the screen strecthed back to where you cant see the edges. Will keep searching for a solution.

EDIT 2: Well after 3 hours of fiddling with app after app, I finally found an app that works but takes forever to find the correct Overscan setting. UI Tuner with a Overscan of 54,36,56,36 starting from 0,0,0,0. Then I had to use the TVs remote and I set the Horizontal setting to -1. Took like two hours just trying every number from 0-99 just to find the proper 1:1 scan. Now I can see menus and the notification bar finally, and all video apps fit perfectly. Yay!