yashsingh1/xdaforums huggingface dataset:
[Nexus Player Original Android Development] Idan73:
thats because archived netflix is different from mainstream one, different signature etc, and it is specially made for android tv.it can only be launched from leanback launcher and it works fine. in your case you never actually ran an archived netflix and only improvement you saw on your original post is a placebo , or most likely netflix just improving to 720p when connection gets faster and it buffers enough.

with the archived neflix, if one can live with controls (they are a pain for me) ,you do get full 1080 streams

it can only be controlled with arrow keys or original remote once launched.

the same thing and fix for drm applies as the videos will be black till the workaround from dev option is enabled.

you uninstalled the mainstream netflix therefore you cant see the android tv version with regular launcher.

i mentioned before in this thread, only plex has unified app that automatically recognises if itc been launched from leanback or regular launcher and acts accordingly. they should all be written like this, so kudos to plex devs, sadly none of them are, including google ones.

Yeah I realize my post is missing capitals. That's because I'm so used to typing on the phone, that using pc keyboard I forgot about shift key ?

Periods are fine though. ?
[Nexus Player Original Android Development] danigraham:
There is no link, changelog, but no link ?.... still uploading I guess.
[Nexus Player Original Android Development] zulu99:
The link is in the first post installation description.

In the changelog there are the link of old versions.
[Nexus Player Original Android Development] dhacker29:
I wasn't trying to be rude when I asked about kernel source I was only asking so I could share any commits you made in my efforts to bring CM to fugu. Also is there a change you can link the rar of the device tree in the OP? I have searched pages and pages but haven't found it yet. Thanks for the had work on this.
[Nexus Player Original Android Development] zulu99:
I'm full open to share all, what i want is only restore original Android on all devices with AndroidTV inside.

Because i think that AndroidTV is the invention of sellers of movies and songs to lock the users in a "walled garden".

Many others restriction will come, step by step.

I'm against piracy, but i not accept that big company ruin the future of information technology to protect their economic interests.

Especially if they advertise as security, the imposed restrictions.

The previous device tree + vendor is this http://goo.gl/cVWmwB

When i have time and reorganize the work, i will share also the last version, but the changes are only bluetooth a2dp support and new google apps stuff.

For bluetooth a2dp stuff, you can use also the 3 audio lib precompiled inside my rom for now.

libatv_audio.so , libaudiopolicymanager.so , audio.primary.fugu.so

From device tree, you can see also the changes to have volume + / volume - unlocked in overlay folder and all others stuffs to transform the Nexus Player in a real Nexus device.

I love cynogenmod and i'm not interested particularly in firmware development, in the sense that i not like this work also if i can do this very well.

My only interest is to restore full Android.

AOSP or Cyanogenmod is not important, the important fact is that users can do what they want with their hardware.

Thanks for CWM recovery can be very useful in some scenarios.

I'm a friend of Cyanogenmod firmwares, because have very good source code inside,

i'm againt all Chinese crap firmwares and derivations for android tv box and hdmi sticks because source code is ruined and not respect Android standards.
[Nexus Player Original Android Development] danigraham:
If you are having Ethernet problems, my husband posted a possible fix in the Q&A for LolliRock. I will link to it below. It seems to be working great for us, as we have had problems with Ethernet dropping out in the past.

http://xdaforums.com/showthread.php?p=60334888
[Nexus Player Original Android Development] Radeon1337:
Is there any way to make the Youtube app to show 1080p/1440p ?

I'm only able to play videos at 720p.
[Nexus Player Original Android Development] zulu99:
Maybe Google want save bandwidth :) I'm joking

On the firmware part all ok, maybe a strange google decision that will be solved in near future. I hope.

The stupid fact is that on my galaxy s6 rooted without widevine keys and nexus 7 rooted i can have 1080p that is not so useful cause the little screen.

Is not a protection, neither a bug in the firmware. Maybe someone in Google is making use of drugs. :)

1080p work very well with all others services and apps.
[Nexus Player Original Android Development] Radeon1337:
Heh, luckily i don't have any restrictions on my bandwidth :)

I tried extracting the youtube apk from my Nexus 6 just to get the latest update, but that didn't change anything.

The weird thing is when i'm casting from my phone if i change the resolution i can clearly see the difference between 720 and 1080p so there is no problem viewing full HD.

No biggie, love your work :good:
[Nexus Player Original Android Development] roebling:
Run Nexus Player Netflix v1.0.3 on LolliRock

Figured out how to run the higher resolution Nexus Player/Android TV version of Netflix on Lollirock:

1) Uninstall the Play Store Netflix, if you have it.

2) Download Netflix v1.0.3 (http://xdaforums.com/nexus-player/general/ref-collection-nexus-player-apks-t2976537) or v1.0.4 (http://www.apkmirror.com/apk/netflix-inc/)

3) Install.

As noted in previous posts, after installation the "Run" button is grayed-out. Yet, when trying to cast Netflix from an Android device, Netflix opens the local app, the v1.0.3 (or v1.0.4) installed above. Go figure, right?
[Nexus Player Original Android Development] TheShamsMan:
Nice work around.. A bit of a pain, no? You're saying that Netflix on the NP will only run if I cast it from my phone?
[Nexus Player Original Android Development] zulu99:
For Netflix Leanback app you can try this:

Download and install Netflix Leanback http://www.apkmirror.com/apk/netflix-inc/

Download and install QuickShortcutMaker from Google Play https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut&hl=it

Open QuickShortcutMaker and create a shortcut fot the netflix leanback activity.

After creation, you will find a netflix icon on your desktop. on your desktop not on apps drawer.

Click on this icon to open Netflix leanback.

Let me know, the app open, but i not have an account and i can't test all. I'm in italy, netflix not work in italy. And i prefer movies in my original language :)

In short, QuickShortcutMaker create Shortcuts also of Leanback apps. So you can use some of this Leanback apps also without Leanback Launcher, but with a regular icon like all others android apps inside Google now launcher. Some apps have both activity, regular activity and leanback activity. If you prefer the leanback one, you must create a shortcut of the leanback activity. You can heva both worlds with regular launcher.
[Nexus Player Original Android Development] roebling:
Getting decent Nextflix picture on LolliRock'd NexPlayer, pt. 2

It's a pain, absolutely. If you're watching on a TV & use a TSR to fix the overscan, turn it off or it squishes the video.

Previous poster said Netflix v1.0.3 required the stock LeanbackLauncher to run. I tried to install it (http://xdaforums.com/nexus-player/general/ref-collection-nexus-player-apks-t2976537) but it wouldn't install for me.

Anyway, I suspect that changing the right setting in the app's manifest would enable it to run on more platforms but, as I live in a country that litigates, assesses fines & imprisons people for such crimes, I didn't look into it. But, if I did want to look into it, I'd start by searching the Play Store for something like "APK Editor..."
[Nexus Player Original Android Development] zulu99:
test my suggestion above about QuickShortcutMaker
[Nexus Player Original Android Development] roebling:
Zulu the Guru, it worked!

I installed QuickShortcutMaker, found Netflix v1.0.4, tested it, made a shortcut, and tested it. All good!

When you install & open QuickShortcutMaker, it displays four tabs. The first, "Applications," is just a list of all the apps listed in the stock launcher. As Netflix for Android Tv isn't a normal Lollipop app, it wasn't in that list. The second tab, "Activities," lists all of each app's activities without checking to see if the app's in the stock launcher list, and QuickShortcutMaker will make a desktop shortcut to any activity there. Netflix vs 1.0.3/1.0.4 aren't in the "Applications" column but its two activities are listed under "Activities" along major components of the regularly installed applications. QuickShortcutMaker's special sauce is that it will create a shortcut not just to an app but also to just single activity/part of an app. Netflix v1.0.4's activities, called Netflix Ninja and Netflix Main, both started v1.0.4 of Netflix when I tested them. Then sign-in, just once like with regular Netflix, and then every time you start it, it goes directly to the videos menu, as usual.

Perfect!
[Nexus Player Original Android Development] zulu99:
Try also with Google Music that have both activity, Leanback and normal.

You can have both UI.

So you can understand the next level.

Open the leanback version of google music more than one time because it need to rewrite cached informations. After 3 try you will have forever also the leanback version.

But with my DroidMote i prefer always the standard version. More accessible and fast
[Nexus Player Original Android Development] Idan73:
Lol. I told him all this few days back in not so direct hand holding way. Not even a thanks.

Just kidding. ?

Glad he got it working.

Note 4 ?
[Nexus Player Original Android Development] TheShamsMan:
You're a genius dude.

Followed your steps and the app launched, but none of the buttons for the app are responsive.

I've uninstalled, rebooted, repeated your instructions. Still no button access. All other apps work, just not this Netflix. Any ideas? Thanks!
[Nexus Player Original Android Development] M3drvr:
Anyone else tried streaming mkv files in latest build? They seem to cause all video players to crash after roughly 15-20 minutes. And then after that they will crash within 5 minutes. On the other hand I've tried webm videos and zero issues. 3 hour movies play without a problem. I have not tested mp4 yet which I know is fairly identical to mkv.
[Nexus Player Original Android Development] npjohnson:
Could someone please post up their build.prop from this ROM? I need to see how LolliRock identifies itself in the build.prop.
[Nexus Player Original Android Development] zulu99:
You can try with the touchmouse of DroidMote.

Touchmouse is for apps that not have mouse support.

In client settings select touchmouse and select your 1080p rotation 0 touch profile.

Server screen 1920x1080 orientation 0

From http://www.videomap.it/download.htm
[Nexus Player Original Android Development] janjan:
Thanks a lot for version 2.0. It runs smooth without any issue. Is it possible to uploade the LeanbackLauncher.apk with necessary files in case if any one want to use the LeanbackLauncher. Acually it is not possible to run yuuptv apk from google play any more. I really appreciate your help zulu99.
[Nexus Player Original Android Development] roebling:
Thanks for alerting me to the importance you thought the alternate launcher used by stock Nexus Player, the "Leanback Launcher," had. I found it interesting, though, that the leanback launcher was not required of the HuluPlus app of stock the Nexus Player and so I suspected, based on my limited Android programming experience, that the leanback launcher had no unique capabilities and that the Nexus Player/Android TV Netflix app could be easily switched to allow it to run on full Android. In investigating the poor performance of the Play Store Netflix app on my LolliRock'd NexPlayer, I read that the app perceives my system to be "mobile" and so limits it to lower quality playback. The Android TV/Nexus Player version of the Netflix app has no such limitation AND IT'S SMALLER, half the size of the Play Store version. To old programmers like myself, raised on computers with RAM measured in thousands and hard drives in millions, smaller code is better code.

So, to repeat, THANK YOU for all your help and insight.

You were wrong about the Leanback Launcher being required, BTW. Without installing the Leanback Launcher I was able to get the stock Android TV/Nexus Player version of Netflix, v1.0.4, running. I did so by casting from my smartphone or by employing zulu99's tip about creating a shortcut to an activity within the Netflix app and now I can enjoy the higher resolution image that the made-for-tv app provides instead of the lower quality that the "mobile" version of Netflix limits users to.

Thanks, again, for all your help

---------- Post added at 08:47 AM ---------- Previous post was at 08:23 AM ----------

"None of the buttons are responsive..." ?

The AndroidTV/Nexus Player apps are controlled by arrow keys, tabbing (laboriously) from selected item to selected item, and by "Enter". Plus a back key function which, for some reason, is mapped to "ESC" on the Logitech K400r keyboard. On DroidMote the arrow keys page works perfectly for such "lite" apps. Or, that's how it works here.

---------- Post added at 09:00 AM ---------- Previous post was at 08:47 AM ----------

Leanback Launcher apk is in the .zip file linked at the bottom of the page under "All Nexus Player default (system) apps"

http://xdaforums.com/nexus-player/general/ref-collection-nexus-player-apks-t2976537
[Nexus Player Original Android Development] Idan73:
Oh. I was typing as I was doing it so just drew conclusions. I did it same way as Zulu suggested, except I got shortcut from Nova as it has same capability built in.. Got the shortcut for leanback launcher, I guess I could have used shortcut for Netflix directly. In Canada we do not have working Hulu, which is why I claimed that only Plex auto recognises which platform it is launched from.

Just to clarify. If v. 104 is launched, not testing now, can I use mouse, or is that version also controlled by player's remote and/or arrow keys + esc on keyboard just like the original?

Starting Netflix cast for that app, in order to get full resolution is a good find.

Note 4 ?
[Nexus Player Original Android Development] zulu99:
you can install it manually with the apk. some apps require also portrait functionality from google play. this firmware have only landscape as it must be. but you can install the apk manually without problem if the app can run in landscape. 97% of the apps :)
[Nexus Player Original Android Development] gullatec:
ADT-1

Any upcoming love for the ADT-1?
[Nexus Player Original Android Development] KalenXI:
Has anyone else been having bluetooth issues with this firmware? It started for me last night and persists even after a full reset with the factory image. The only thing I've found that can occasionally solve it is to reflash the kernel but that doesn't always fix it and when it does it only fixes it for 10-15 minutes.

From the logs it seems like the bluetooth IC keeps freezing and not responding to commands after which the OS restarts the bluetooth controller:

E/BTLD ( 2376): ######################################################################
E/BTLD ( 2376): #
E/BTLD ( 2376): # WARNING : BTU HCI(id=0) command timeout. opcode=0x200c
E/BTLD ( 2376): #
E/BTLD ( 2376): ######################################################################
E/bt-hci ( 2376): Num consecutive HCI Cmd tout =2 Restarting BT process

But it does this every 30 seconds or so and so I can't get anything to pair.

Does anyone have any ideas as to what could change that would survive a factory reset and reinstalling the factory firmware?
[Nexus Player Original Android Development] zulu99:
Bluetooth stuff in kernel and in firmware is pure AOSP. I not have problems with bluetooth, but i not use frequently the bluetooth.

If you have flashed also the stock firmware, nothing remain of the old one.

Can be your bluetooth external device the problem ? or dead batteries that cause strange disconnections and provocate this bug ?
[Nexus Player Original Android Development] KalenXI:
I don't think it's the bluetooth device cause it won't pair with any device I've tried. I'm beginning to think something's gone wrong with the bluetooth chip itself.
[Nexus Player Original Android Development] zulu99:
I would not want to advertise myself, but you give me the assist. I don't have bluetooth problems with any android tv box because i use DroidMote. When i want connect an hardware controller because in some games the soft gamepad is not sufficient, i connect it to the bluetooth of the phone or via otg cable to the phone and the command of the hardware controller are forwarded from droidmote client to droidmote server like the controller was connected phisically to the server without lag. Is implied that your hardware controller is already working on the client device, regardless DroidMote Client. In this way i can play with games with controller support and also with games that accept only touch actions.

sorry for this ads, but can be useful for someone. :)

however, your problem is strange.
[Nexus Player Original Android Development] KalenXI:
Yeah I actually already bought DroidMote. That's how I was able to debug the bluetooth so I could have ADB connected via USB and control via DroidMote since I couldn't get the bluetooth to connect. I didn't know it could forward input commands from a hardware controller on the client to the server though I'll have to check that out.
[Nexus Player Original Android Development] midnightzak:
Do LolliRock and unleashed kernel play together?
[Nexus Player Original Android Development] zulu99:
a boot.img is composed ramdisk + kernel + commands

my ramdisk is the aosp version + libhoudini stuff + mtp,adb support. Then i proposed to defconoi to chose the better collabotation. the kernel can be used and i'm also happy that other can do part of the work. But ramdisk is necessary to have things in the firmware. i 'm fully open to all kind of collaboration. i'm not the classic firmware developer, i work only to have a better nexus device for TV. My work is the work of all.
[Nexus Player Original Android Development] zulu99:
I read in others threads some people with bluetooth problems on stock firmware. One thing is sure, the android tv firmware, handle the bluetooth with a non standard bluetooth app to permit things with the little hardware remote. Instead LolliRock based on AOSP handle the bluetooth in the standard android way. i propose to you do do other tests, because you are able to do and then i can see also the bluetooth drivers part if need some additions / corrections like the audio part already freed.

But my priority for now is:

the hwcomposer overlay problem

webcam video HAL

But let me be clear, the serious work will begin on January 2, 2015. Now it's time to celebrate the new year, for me, for you and for all.

Happy new year to all.
[Nexus Player Original Android Development] defconoi:
I'm not sure I haven't tried, if there is ramdisk modifications I'll have to add that to unleashed
[Nexus Player Original Android Development] zulu99:
if you want you can make two versions, one with stock ramdisk, one with my ramdisk.

my ramdisk is the AOSP version + mtp,adb in init.fugu.usb.rc and i added ro.dalvik.vm.native.bridge=libhoudini.so in default.prop

but you know how to extract the ramdisk from my boot.img and add it to your kernel.

i explain for others: the ramdisk can be decompressed and all files inside can be readed.

But if you prefer, i can get also your kernel and add to my ramdisk. It is not useful to do two jobs in the same direction.

If you like work on kernel, i'm very happy and i trust your work.
[Nexus Player Original Android Development] defconoi:
feel free to use my kernel for the next release, I'm out of a computer atm mobo died, awaiting newegg shipment for next update ;)
[Nexus Player Original Android Development] midnightzak:
I'm finding some app compatibility issues on LolliRock, for instance Hearthstone launches and crashes, and World of Warriors (which sort of worked on stock) also crashes. Any ideas or am I just expecting too much too quickly?

Either way, thank you for your time and work on this build!
[Nexus Player Original Android Development] zulu99:
​

Don't forget that the Nexus Player is an x86 device, thanks to houdini can work also arm-only app because translated, but we can't do miracles. In little time, many more apps wil be updated to support intel 64 bit cpu devices but also now the compatibility with this firmware is very good.
[Nexus Player Original Android Development] zulu99:
Good news for the hwcomposer overlay problem, that in some apps make a popup menu black etc. Aka when you install Chrome and you see the first popup completly white etc.

If in developer options, you check "Disable HW overlays - Always use GPU for screen compositing" the problem disappears.

This problem is present also in the android tv firmware, but in android tv you can't check this option in developer settings i think. But now we know the problem and will be solved.

Someone with better english can report also the bug in AOSP bug reports.

Attention the checked option restore the default value after reboot but when is checked all work without this annoying problem.
[Nexus Player Original Android Development] KalenXI:
I wonder if it could be related to this bug report: https://code.google.com/p/android/issues/detail?id=32564

Sounds like hardware overlay over HDMI requires 3rd party driver support and without that it will just fail to render. Doesn't look like there's much hope for it being fixed though since the bug has been open since 2012 and is apparently an issue in the HDMI drivers rather than AOSP itself. Though they should at least detect if HDMI is attached and disable the overlay if it's not compatible.
[Nexus Player Original Android Development] zulu99:
For World of Warriors and some others unity games arm-only get the linked file libEGL.so and copy in the folder /system/lib/arm/nb/

assign 644 permissions to libEGL.so

with es file explorer you can assign the permissions like others .so files from more -> properties -> permissions

will be added to the next version. Thanks for your post.

https://mega.co.nz/#!nAYjTIpK!TXMqVjTchcRqVOSKVlSUlrU5TRgjEi5MKJQJFeh_Acc

Sorry this was my forgetfulness :o
[Nexus Player Original Android Development] KalenXI:
I found a more permanent way to disable HW overlays. You can either use Tasker and the Secure Settings plugin to set it on boot. Or use Tasker's shell action to run "service call SurfaceFlinger 1008 i32 1" as root on boot.
[Nexus Player Original Android Development] mattrb:
On my plasma TV. I cannot see the top pull down menu bar. How can I perform scaling?
[Nexus Player Original Android Development] zulu99:
Idan73 thank you for all your suggestions.

In this thread i want only solutions and not controversy.

With my suggestions, I do not want to show what I know, but just help, if possible.

Every one can suggest better than me. I'm just a small developer like many others.

Sorry if i misunderstand your words.
[Nexus Player Original Android Development] zulu99:
YuppTV for Android Set-Top Box seem to work https://play.google.com/store/apps/details?id=com.yupptv.stbtv

This is the app you are talking about or is another ?

Leanback Launcher was posted by the friend roebling in previous post, but as you know I love Google Now Launcher. Fast, customizable and more usable.