yashsingh1/xdaforums huggingface dataset:
[Nexus Player Android Development] dony71:
wowww, fast progress ..... can't wait to try it out
[Nexus Player Android Development] celebi23:
Official Lineage 14.1 at some point would be awesome :D :good: :fingers-crossed: Trying to get as much out of my ADT-1 as possible before I need to buy another AndroidTV device.
[Nexus Player Android Development] seapoint:
I wonder is there any possibility of getting Full Linux running on this? I'd love to repurpose it as a Plex/Torrent/TvHeadend server
[Nexus Player Android Development] mruno:
I am getting an error 255 when trying to install pure_nexus_molly-6.0.1-20160202.zip. I downgraded from Android 8 to 6.0.1 build mob30w. I have tried using TWRP 3.0.2.0 and 2.8.7.0

Edit: Found the issue being: ROM Firmware Required: 5.0.2 LRX22G
[Nexus Player Android Development] Whoareyou:
This still happening?
[Nexus Player Android Development] npjohnson:
Fixed that, Bluetooth now no longer works.

Am stumped on it. If anyone fixes Bluetooth, I can turn on builds.
[Nexus Player Android Development] sxrmafia:
Netflix stopped working on stock aswell. Is there a fix for it?
[Nexus Player Android Development] npjohnson:
Nope, sadly our cert was either revoked, or our DRM implementation no longer can handle newer content.
[Nexus Player Android Development] dony71:
so sad .... I sense ADT-1 starts dying now
[Nexus Player Android Development] terminal2000:
If someone can port Debian to ADT-1 this would be way way better than RPI for a lightweight desktop.
[Nexus Player Android Development] doctorjei:
If anyone is interested, I'm playing around in my free time with trying to get a basic Linux distro working on the ADT1. My first target is to get non-graphical boot with ssh, and I'll go from there. Drop me a line if you want to pitch in!
[Nexus Player Android Development] Dvalin21:
Not sure how I could, but i would. It would be awesome to have linux on here, that means have google chrome with Youtube Adblocker AWESOME!!!
[Nexus Player Android Development] doctorjei:
I've created a new thread (so that I don't just hijack this one) here: https://xdaforums.com/t/molly-seeking-collaborators-to-build-ubuntu-rom.4203209/
[Nexus Player Android Development] npjohnson:
doubtful - do you use 2fa?
[Nexus Player Android Development] npjohnson:
you said that already - not sure what's up
[Nexus Player Android Development] notherdai:
Any updates to this device I have one device I can donate to a willing developer
[Nexus Player Android Development] npjohnson:
Hasn't been touched for a long while, tegre 4 is pretty late stage and it's life, it's very hard to support at this point.

With that said mainline Linux is something we've looked into, if you'd like to donate the device feel free to DM me, I know several developers who would be interested in one.
[Nexus Player Android Development] wewewi999:
Hey I'm admittedly not a developer but I do am a major contributor over on r/AndroidTV and mod of r/ShieldAndroidTV; and I have a very modest YT channel;

I've been rounding up certified AndroidTV devices with every SoC for a big retrospect along with separate feature videos/posts..

(Importing the Shaks G1 from Korea was quite expansive, and its Realtek RTD1315C is proving to be .. not quite ready yet!) XD

Was poundering between putting a s hitload more of money on one of the few ADT-1s on eBay, or still putting a significant amount of money on a Madcatz Mojo and slap a ATV rom on it but hey.. actually came here to see what roms were available for each...

Anyhow. Now that I'm seeing your post, a donation would be most welcome! I swear you could hardly find a better place for it to finish its days.

Best regards!
[Nexus Player Android Development] wewewi999:
Sorry; just saw my own post signature.. how old school is that?! LOL

FTR the Archos 5 Internet Tablet was running native Android 1.5, later updated to 1.6.. and I ported AOSP up to 2.3.2 on that thing!!

Those were the days! =D
[Nexus Player Android Development] Dvalin21:
Still have my device, although put up in my closest. Would love to see linux put on here
[Nexus Player Android Development] benpage:
Thanks so much for this ROM. The ADT-1 is too powerful (and too free) for me to buy a Nexus Player. I have two of them in regular use and now they're finally up to date again.

BTW the instructions for flashing with TWRP, say to wipe the system after flashing the ROM. I did the wipe before, then a factory reset after flashing, and it worked perfectly.

Thanks again!
[Nexus Player Android Development] npjohnson:
I've jumped on the PureNexus boat. I am working on some cool things though. They'll be out soon enough.
[Nexus Player Android Development] bryantjopplin:
Yeah I'm running pn on np and n6. If he had if for HP touchpad, s4, and gnex that would be awesome.
[Nexus Player Android Development] Luxferro:
I just set this up on one of my ADT-1's. For the most part it's working great so far.

Some minor bugs I've noticed:

1) Device setup via phone/tablet doesn't work... phone sees the ADT-1 waiting for setup, tries to connect but never does.

2) The live channels app isn't showing on leanback launcher, even though I have Silicondust Homerun View installed. Everything works though, including live channels if launched via the settings, or optional launcher in PureNexus.

running the 12/18 build with the gapps from the 1st post.

edit: Just noticed the live channels function is there, it just has a diifferent icon & label.
[Nexus Player Android Development] npjohnson:
New build in the OP. Gives us a Source built (and functional) Power HAL. Thanks [MENTION=4112553]dhacker29[/MENTION] !
[Nexus Player Android Development] your_m0m:
Just installed, really good stuff. Only problem is almost no games are compatible. Could it be as simple as build prop tweak to fix it?
[Nexus Player Android Development] Robot Ross:
+1. Would be awesome if more games had support, since this ROM is awesome. Only problem I have had is random display corruption for about a second when launching some apps sometimes, but it always goes away. I had this problem in the stock ROM, so it might just be an Android TV bug at the moment.
[Nexus Player Android Development] npjohnson:
That's a somewhat common problem, on all ADT-1firmwares,s but I'd classify it as a minor annoyance, so, we'll take a look, but I doubt it'll get fixed.

No, not that simple. We are working on it.
[Nexus Player Android Development] knives of ice:
does the color wash out problem exist on this rom?
[Nexus Player Android Development] npjohnson:
Fixed! Thanks for catching this! Your welcome man. I love the ADT-1 just as much as my Nexus Player now.
[Nexus Player Android Development] Crash Stuntman:
I'm having some trouble getting Windows to recognize the ADT-1 when I select ADB Sideload in TWRP. I do have ADB functionality working correctly when not in sideload mode (and in the Android environment) but I get a device missing driver error when I attempt to use sideload.

I attempted to add hardware ID's to "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf"

;Google ADT-1
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&REV_0232&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&MI_01

As well as to "C:\Users\User\.android\adb_usb.ini"

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0xD002

This didn't work. Any ideas on a better driver than what's in Android SDK manager?
[Nexus Player Android Development] your_m0m:
Looks like your making headlines guys, nice job!

http://www.androidpolice.com/2015/12/24/xda-members-breathe-new-life-into-the-adt-1-with-android-6-0-1-pure-nexus-rom/
[Nexus Player Android Development] npjohnson:
That's awesome to see!!!! Thanks for linking it.

Honestly, it may be easier to use a mouse and actually navigate TWRP. ADB Sideload can be hard to get working. Gist of it it, you need to use an ADB Composite driver, not an ADB driver, but like I said, easier to just navigate TWRP.
[Nexus Player Android Development] Crash Stuntman:
What's tricky about that is that if I attempt to install the zip from TWRP (instead of ADB sideload) the recovery just appears to reboot rather than install.

Would you mind sharing the ADB Composite Driver you're using?
[Nexus Player Android Development] npjohnson:
Uh. That definitely should not be happening. Are you flashing or booting TWRP? (I'd rather avoid explaining the Composite ADB bit itlf at all possible).
[Nexus Player Android Development] dcarr622:
ROM works great! A few notes:

0.5x Animation speed makes everything look jumpy and not smooth. Consider reverting to standard 1.0x if there's no way to change from Developer Options.

Nearby Device Setup does not appear to work. This is a minor issue and who knows if it's even possible to get it working on the ADT, I'm not too familiar with it.
[Nexus Player Android Development] eyetek:
Installed Pure Nexus on one of my ADT-1, thanks for supporting the box.

I'm having problems with Kodi, if I click on the one click install icon it starts the download but never finishes. I've also tried sending the app directly from the Play store to the ADT-1 but it's never received.

I've side loaded the Kodi.apk file, installed it and once loaded it says unable to download obb file.

Any thoughts or suggestions?
[Nexus Player Android Development] npjohnson:
I agree. I'll be pulling the 1.0x Animation change into PN for Molly in Jan.

As for nearby devices, I've noticed this, and will take a look.
[Nexus Player Android Development] npjohnson:
Most likely is your internet. I just tried it and it works for me.
[Nexus Player Android Development] eyetek:
Thats what I thought at first but I was able to download and install other apps from the play store just not Kodi.

So I did a complete new clean install of the ROM and Gapps package after an advanced wipe this AM, it still would not work through the play store. So I side loaded the Kodi.apk file and it installed, I ran the app but once it downloaded the obb file it never opened, just a blank screen. If I try to reopen the app it just closes or hangs like before.
[Nexus Player Android Development] eyetek:
Got it working this evening, something wasn't right so I flashed the box back to stock rerooted and flashed TWRP and reflashed Pure Nexus ROM.

Now everything is working as intended and Kodi is installed.
[Nexus Player Android Development] dantrevino:
I installed the 20151221 build, and netflix still isnt working. Something i'm missing?

Edit: I should add. Cast work fine, as does Google Play Movies.
[Nexus Player Android Development] mattysiebs:
Download Leanback Launcher (chainfire i think?) and see if there is a netflix pre-installed with the OS. This is so for the CM12 ROM provided by r3pwn. My experience is that the netflix that you can download from the Play Store does not launch and for whatever reason bugs out when you try to uninstall it.

EDIT: Okay, no Netflix gives (-116) for me when i try to load it from the play store...thoughts?
[Nexus Player Android Development] toebee76:
This is really great. Thank you to all those involved. Breathed new life into my ADT-1. Gotta love the android community!
[Nexus Player Android Development] iamloco:
thanks for this rom I've flashed it this morning everything (Except the set up my device setup but this should not be a priority)

does the ROM support the shield Remote?

I would really love to use the audio jack or any other remote that have a jack in it if possible :)
[Nexus Player Android Development] npjohnson:
No. DRM is still broken in the last (really old) CM-12.1 Build we did.

Hm. Try the Play Store version, and, if you are using the play store version, use the preinstalled version.

I am using it on the 21-DEC build as we speak, BUT, I was logged in before I updated through the play store iirc.

Yeah. I'll add that to the known issues shortly.

Hasn't been tested, but I doubt it. I'll look into adding support (conveniently, [MENTION=671155]Gfunk117[/MENTION] just got a Shield TV, so if he has the controller, there's a much higher chance we'll end up getting it working ?)
[Nexus Player Android Development] npjohnson:
No problem. This has been a really fun project.
[Nexus Player Android Development] mattysiebs:
So color me just a little confused.

When I installed the ROM last night (btw, awesome!), I did not locate any pre-installed netflix. When I attempted to install the netflix from the play store, it does not load to the login screen and tells me that it cannot reach the netflix servers.

I did not see a preinstalled version, but I did not download leanback...
[Nexus Player Android Development] npjohnson:
My apologies, wrong ROM thread. Try fresh installing one more time, Netflix can be temperamental.
[Nexus Player Android Development] iamloco:
great both gamepad and controller have the aux jack :)

my guess is that it use bluetooth to get the audio
[Nexus Player Android Development] toebee76:
After a day of use I've noticed a few things. Haven't seen them mentioned yet. When my adt-1 goes to sleep the led doesn't turn off. It flashes intermittently. Like its trying to tell me something in morse code. I haven't tried playing with any of the led options mentioned in the op just yet. Casting works fine. I noticed HBO Go was already mentioned as having a issue. Showtime anytime seems to have a similar problem when attempting to cast.

Has anyone tried to format a usb drive to expand the storage yet? I don't know if I just had the misfortune of a usb drive die on me or possibly there is an issue with the format process. I plugged a usb stick in and it showed up fine. I clicked format. It showed the formatting screen, then gave me the typical warning about being slow. I clicked ok. It went back to the formatting screen. Suddenly it told me that the drive was no longer connected. It was. Drive seems to be dead now. Tried it in android and windows. Doesn't even light up. So I was just curious if anyone has had success before I try another drive.
[Nexus Player Android Development] dantrevino:
I wiped and reinstalled, still no luck. Then restarted for no particular reason and netfix now works great! ?? Random, but I'll take it.

Thanks!
[Nexus Player Android Development] npjohnson:
Huh. Could have been your internet/ISP. It has worked for almost everyone else. Great to hear!
[Nexus Player Android Development] npjohnson:
New build in the OP! Fixes the Play Store Games incompatibilities were seeing before. This was done by removing the CM code for DPI change, see changelog for further info. Thanks to [MENTION=4395895]BeansTown106[/MENTION] for tracking down the issue, and [MENTION=3288861]dhac[/MENTION]cker29 for the build!
[Nexus Player Android Development] allenpan:
My = ADT-1, Android 5.02, not- rooted, and i am trying to sideload from the recovery mode... also how do i root it?

i have problem, i got "E: signiture verification failed!" how do i fix it?
[Nexus Player Android Development] benpage:
The Rom is already rooted.

Try downloading the file again. It might be corrupt.

If that doesn't work rather than sideloading, you could try using TWRP to push the zip file and then flash it.
[Nexus Player Android Development] npjohnson:
Read the OP. It explains what you need to know. You can't use the stock recovery. You need to be in TWRP.
[Nexus Player Android Development] allenpan:
yea... i figure it after, ... new issue, i still can't pair use Bluetooth Mouse and my Nexus Remote no longer been detect by the ADT1.....
[Nexus Player Android Development] dantrevino:
Any update on game compatibility?
[Nexus Player Android Development] npjohnson:
Yes. Use the newest build, its written in the changelog.

As it states in the OP, the Nexus Remote doesn't pair on Stock, and will not pair to any ROM the ADT-1 runs. Your Bluetooth mouse will most likely pair fine. Try again after a reboot.
[Nexus Player Android Development] allenpan:
dam! really? well, now the Nexus Remote wont even been detect by ADT1. (with the PureNexus Rom).. when it was stock 5.04 it does detect...but wont pair

anyway, looking into other voice remote like MX3,... it should work with other one right?
[Nexus Player Android Development] allenpan:
is possible add USB webcam support? such Logitech C905... Microsoft LifeCam Studio
[Nexus Player Android Development] npjohnson:
No, the Camera HAL used on the Nexus Player was written by Intel for Intel Processors, and unfortunately, not updated for MM.

On MM, if a WebCam is ever plugged in, the device will bootloop if the WebCam is removed, so, all Nexus Player MM ROMs have it disabled due to that bug.

Even if the MM bug could be fixed, there is little to no chance we could get the Intel proprietary stuff to run on the ADT-1 (armv7a).
[Nexus Player Android Development] allenpan:
interesting... it (HAL) can not get from other NVIDIA Android platform?

---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------

i have the logitech and Microsoft webcam plug in on every boot, it did not get into boot loop
[Nexus Player Android Development] npjohnson:
On an MM build? As I said in the previous post, most ROMs have it disabled. If the ROM developer enabled it, it was under ill advisory. As I described above, the device will bootloop if the WebCam is ever Unplugged and the device is reboot.
[Nexus Player Android Development] allenpan:
ah...i wonder will it better to have someone to make a full android ROM for ADT-1 instead of the Android L
[Nexus Player Android Development] mattysiebs:
SUCCESS! Guys, don't know what this means, HOWEVER, I sideloaded the netflix application (not Android TV version) and it works flawlessly...minus a few controller things, but there you go
[Nexus Player Android Development] npjohnson:
Well. This isn't Android L (Lollipop). This is Android M (Marshmallow). It is an Android TV build, we are working on a PureNexus Tablet build right now.
[Nexus Player Android Development] npjohnson:
It's known. You can sideload any app you'd like. Most of not all ARMv7a apps that arent DPI/device dependany will work.

Why would you want to use the normal Netflix though? The Leanback one gets 1080p access, and the normal one doesn't....
[Nexus Player Android Development] pointdooly:
What is the differences between "[ROM][molly][6.0.1]★ Pure Nexus ★[12/14/15] ADT-1" and "[ROM][6.0.1]★ Pure Nexus ★[1/5/16]"? I could not find any explanation anywhere and it points to same changelog(googleDoc).

Are they using same Base ROM(Pure Nexus) but different various version by different developer?
[Nexus Player Android Development] mattysiebs:
I did not manage to get the leanback version working...sadly.

However, I am glad it works period. I tried installing many various versions of the leanback version and only the tablet version worked...
[Nexus Player Android Development] npjohnson:
Hrm. This is odd. It works here. What failed about it for you?
[Nexus Player Android Development] mattysiebs:
The application loads just fine from the play store but I am forever getting the - 116 error which Google has lead me to believe means that it's having trouble connecting to the servers... This is ironic because the non lean back version works just fine. Then again my wifi router is really not the best so it could be that is the problem.

Shall try with another wifi ap and see what happens. Honestly it bugs me just a little.

EDIT: No, tried with another Wireless AP and it still gives -116 error. I shall try using a less recent version of the app to see if that helps. Otherwise, I do not know.
[Nexus Player Android Development] Crash Stuntman:
Is it possible to customize the PureNexus version of the Leanback Launcher used on the ADT-1? I'd potentially like to create a few custom categories, much like the PureNexus apps row.
[Nexus Player Android Development] dantrevino:
Muted, No sound anywhere.

System seems to be muted. Cant figure out how to unmute. Kodi is showing me the little red mute icon in the top right. No sound in Sling, Youtube, Netflix, etc. TV sound is definitely working as broadcast TV works fine. Restarting doesnt change anything.

Edit: No sound via usb audio or Bluetooth audio either.

Any ideas?

TIA,

dan
[Nexus Player Android Development] npjohnson:
Reflash. It works for everyone else. There's a slim chance that it's truely a software issue.
[Nexus Player Android Development] stackdaddy:
Just tried this for the first time and took only minutes to get it updated to 6 great job! Maybe it is just the data and cache wipe but it is running fast.

The Android TV Remote app from Google is no longer able to connect. It did work on stock Android 5 for me. Is this a known issue before I go wiping and re-flashing?
[Nexus Player Android Development] celebi23:
Just wanted to say thanks for all the hard work that went into this. Finally took the plunge. So glad that I did. It's like my ADT-1 is brand new :D Thanks again!
[Nexus Player Android Development] mattysiebs:
Anyone have any thoughts on the Netflix issue I was having? My only other thought is hook the system to ethernet
[Nexus Player Android Development] stackdaddy:
Does that happen when opening Leanback Netflix or after logging in?
[Nexus Player Android Development] mattysiebs:
When opening Leanback Netflix. If I sideload the tablet version, it works fine.
[Nexus Player Android Development] stackdaddy:
It is working fine for me. If you already uninstalled and reinstalled it then I would wipe data cache and reflash rom and gapps. Which is exactly what I originally did. Unless you don't mind using the other version.
[Nexus Player Android Development] mattysiebs:
Hmm. I will look into that
[Nexus Player Android Development] Whoareyou:
Is A2DP functional in this build? I cannot seem to connect to my speaker system, it wont even see it...
[Nexus Player Android Development] kreegaa:
first of all thanks for bringing back the ADT-1 from its certain death!

quick q on bluetooth audio. I cannot seem to pair my bluetooth audio earphones to the ADT-1 on this rom. It shows up in the list of devices and when i click pair nothing happens. if i back out and come back in, i see my audio device paired but no audio goes to it. is it only me? or is it the rom?
[Nexus Player Android Development] npjohnson:
BT Audio works. Did the headphones work with stock? If not, they pry won't work. The ADT-1's BT chip is finicky (at a hardware level).
[Nexus Player Android Development] npjohnson:
All, please redownload and flash the newest 010516 build, it appears I linked directly to the 121515 build in the OP, and did not link to the folder where the new DL's would be.

Apologies.
[Nexus Player Android Development] npjohnson:
It works. Just the BT chip on the ADT-1 is finnicky (the actual hardware). If it doesn't pair on stock, not much hope.
[Nexus Player Android Development] stackdaddy:
Whats is CMTE version?
[Nexus Player Android Development] kreegaa:
thanks for responding! on the stock rom i could never see my bluetooth earphones.. on this rom they started showing up on the list when i go in to pair. so i assumed it was a bluetooth stack issue. if its the chip, i guess then there is no workaround like you mentioned.
[Nexus Player Android Development] ElfinJNoty:
CMTE stands for CyanogenMod Theme Engine.

Like a CM ROM for your phone, has its theme engine built in.
[Nexus Player Android Development] Quinny899:
[MENTION=5848265]npjohnson[/MENTION]

The link to the builds in the OP is malformed, it got caught by my uni's firewall as a suspected XSS attack, might still work for others though
[Nexus Player Android Development] stackdaddy:
I got the same thing but found you can just search for the build on Google or androidfilehost and the links will come up, you know they are legit by the developer who posted them. Just search for pure_nexus_molly and MAKE SURE YOU FLASH THE CORRECT BUILD if you do it this way. Not really directed toward you just want to help people find it and ensure they flash the correct img.
[Nexus Player Android Development] Quinny899:
Yes I know what you can do, I was just giving a heads up
[Nexus Player Android Development] npjohnson:
Hrm. I'll look into this tomorrow. Its the shortened link AFH provided. I'll change it out if there's a problem.

Thanks.