[ROM][AOSP][Full Android 6.0.1][v.1.3]

[zulu99]

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?

you need my boot.img, my system.img

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

http://forum.xda-developers.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.

 

[sam.balia1012]

you need my boot.img, my system.img

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

http://forum.xda-developers.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.

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:

 

[scottfree1]

you can install also debian no root, wine and start windows apps this is an x86 device.

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..

 

[r3t3ch]

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

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.

 

[zulu99]

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..

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.

 

[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://forum.xda-developers.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+

 

[zulu99]

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://forum.xda-developers.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+

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://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

 

[scottfree1]

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://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

To root you can download the last BETA-SuperSU-v2.66+ and install with TWRP recovery:
http://forum.xda-developers.com/apps...ellow-t3219344
http://forum.xda-developers.com/nexu...overy-t3114717

First link leads here..
All discussion should go the SuperSU BETA thread
Which refers you to here..
http://forum.xda-developers.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..

 

[zulu99]

To root you can download the last BETA-SuperSU-v2.66+ and install with TWRP recovery:
http://forum.xda-developers.com/apps...ellow-t3219344
http://forum.xda-developers.com/nexu...overy-t3114717

First link leads here..
All discussion should go the SuperSU BETA thread
Which refers you to here..
http://forum.xda-developers.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..

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.

 

[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..

 

[vilator]

for updating from 1.2 to 1.3, do I just have to flash new system.img?

thanks

 

[zulu99]

for updating from 1.2 to 1.3, do I just have to flash new system.img?

thanks

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:

 

[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...

 

[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?

 

[SkOrPn]

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?

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!

 

[zulu99]

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!

Many new TV adapt automatycally or there is a button on menu of TV to fit to screen.
However, was already discussed in other posts, if your TV is old or don't have this functionality you can use the app Screen Shift to correct the overscan
https://play.google.com/store/apps/details?id=com.sagar.screenshift2

For Chromecast i will see, i tested it and worked very well. It have the same lib and apk of the stock firmware.
To have Chromecast working well, you must have the last bootloader from Android 6.
Usually i install full Android boot and system starting from a fresh install of the last stock firmware. So i have always the bootloader updated.

 

[SkOrPn]

Screen Shift did not work, but like I said earlier UI Tuner worked. Screen shift refused to keep the settings after reboot even after setting it to restore after reboot. I called Sony and they said my TV does not have 1:1 pixel mapping so I have to use overscan settings inside the OS. But other sources said my TV does have it and my TV was already set for dot to dot. Apparently Sony is correct.

Oh well I have it set up, so I'm happy. Thanks

Sent from my SM-T700 using Tapatalk

 

[zulu99]

Screen Shift did not work, but like I said earlier UI Tuner worked. Screen shift refused to keep the settings after reboot even after setting it to restore after reboot. I called Sony and they said my TV does not have 1:1 pixel mapping so I have to use overscan settings inside the OS. But other sources said my TV does have it and my TV was already set for dot to dot. Apparently Sony is correct.

Oh well I have it set up, so I'm happy. Thanks

Sent from my SM-T700 using Tapatalk

i don't want insist, i don't have the nexus player in my hands in this moment. But in Screen Shift you have an option to restore the settings on boot. Is in a place not more intuitive to find. but there is. i will test today later.

All my samsung TV and LG adapt to screen automatically. On the Samsung remote i have also a button, fit to screen.

 

[pim]

Hello
I'll try to install this rom at the end of the week.
But I'd like to know if I can play games with the original nexus player gamepad using this rom ?
I mean to play games. To control android I have a bluetooth keyboard
Thank you

 

[zulu99]

Hello
I'll try to install this rom at the end of the week.
But I'd like to know if I can play games with the original nexus player gamepad using this rom ?
I mean to play games. To control android I have a bluetooth keyboard
Thank you

if the game support a controller sure you can play with your controller. The nexus player controller is a standard bluetooth controller not like the nvidia shield controller that is not standard and use a proprietaru wifi-direct protocol.