yashsingh1/xdaforums huggingface dataset:
[Nexus Player Original Android Development] georgecarstoiu:
I've tried to approach this problem in the past but nobody has said anything.

Is it me or the HD content (youtube, Kodi, whatever other video) is soft and not as sharp as it should? Tried it with several sources and both direct HDMI connection from computer and Chromecast streaming are sharper. Any ideas?
[Nexus Player Original Android Development] zulu99:
yes this can be improved. i will work on this. the camera hal is not definitive, is just the start.
[Nexus Player Original Android Development] drilus:
I only notice what you describe on a few applications, but not with any you've listed. They all look clear and crisp to me.
[Nexus Player Original Android Development] drilus:
Thanks zulu99! Again, such a great rom!

[emoji2]
[Nexus Player Original Android Development] ecsnead69:
Deleted
[Nexus Player Original Android Development] The Rubenator:
I'm still having the same problem when I try to flash the system.img, is giving me an error saying FAILE (data transfer failure <to many links>

I try changing the USB port to another and that did not work, please help once again and thanks in advance.
[Nexus Player Original Android Development] Otisrhw:
bluetooth

Is Bluetooth broken or did I install something that is conflicting? Pair and connect OK, no audio or file transfer.
[Nexus Player Original Android Development] midnightzak:
The OP says that pairing the original remote can cause that, but a repeat pair solves it.
[Nexus Player Original Android Development] Otisrhw:
Tried took batteries out just to be sure no luck. Can someone check if Bluetooth headphones have audio and mic?

---------- Post added at 05:59 PM ---------- Previous post was at 05:54 PM ----------

Also I'm using a tronsmart 2.4g fly mouse with keyboard, audio and 3.5 mm jack that does work in full. I will get a mouse and try maybe that is conflicting with audio and mic.
[Nexus Player Original Android Development] midnightzak:
To my knowledge, audio pass thru on Bluetooth isn't working for anyone. Something that is still in development.
[Nexus Player Original Android Development] JLine05:
Make sure you are using the latest version of fastboot. Older versions will give this error.
[Nexus Player Original Android Development] n1gh7mar3:
I had the same problem... as mentioned earlier make sure you're using the latest fast boot. Also this problem comes up with certain USB cables. This is the exact problem I had. Tried a new USB cable and it worked perfectly fine afterwards! Hope this helps!!!
[Nexus Player Original Android Development] infernix:
This is working quite well for the most part, but i noticed that when i am casting YouTube to it, it's not in immersive mode which causes black bars to show up all around. Is there something that can be done about that?
[Nexus Player Original Android Development] TheShamsMan:
I I know this has been asked to death already.. I'm sorry.. But I can't seem to pair the remote! Nothing came up automatically as it did in Stock to pair. And home + back button isn't working. How can I enable it without another device? Any ideas? Thanks!

I've tried factory reset, no go. It won't even reset my OS. It'll be exactly the same. Straight to home screen, no prompt to set up.

I've tried using that remote app, but that requires the two devices be connected on the same network, which isn't something I can do. I have absolutely no control over the player.

The remote works. I can pair it to my S3 and it'll work nicely. I can't get the NP to appear as a Bluetooth device. I think that might be the issue. Help!

I just reflashed and got the same thing. Bluetooth doesn't seem to work.. Flashed stock and got remote access back. Flash custom, lose it completely.

Just flashed the Unleashed kernel. Also, no go.
[Nexus Player Original Android Development] midnightzak:
Only way to initiate pairing with the remote is the back and home buttons. Only thing I can think of is that you're not holding them long enough, or not in the Bluetooth screen.

You really need a USB keyboard / mouse for this rom. If your dongle is plugged in prior to booting your NP it should automatically be recognized.

Also, the 13th post in this thread points out that a USB mouse and keyboard are required to set this rom up.

http://xdaforums.com/showpost.php?p=57772252&postcount=13
[Nexus Player Original Android Development] roebling:
LolliRock'n, Day Two

Just a quick note for old, lazy DOS'ers like myself who may be pulling their hair out wondering why they're getting no error messages but, instead of success, are getting the bloody green Android, splattered on his back and with red Alert triangle spilling out.

DOS'ers don't retype in CMD, we Fn3, right? Especially when typing a long Windows path, hitting function#3 retypes the last entry, correctly. What I did wrong & maybe someone else will do was to not notice that instructions #1 and #2 below are different NOT JUST IN FILENAME, but also in the instruction before the file name. I Fn3'd and changed boot.img to system.img, several times, and got the locked-up computer with the road-kill, bleeding green 'droid every time. I re-downloaded the files and even tried a new USB>microUSB cord but no joy. Then I noticed the word "boot" before boot.img changed to "system" before system.img, re-ran the instructions CORRECTED and all is swell!

Instructions (copied from post):

1) fastboot flash boot boot.img

2) fastboot flash system system.img

3) fastboot -w

On Day Two with LolliRock & I'm loving it! It's pretty hard to tell the difference between this and Google's factory-original Lollipop. If I had to name a difference it would be how drama-free this o.s. is, compared to any stock version this new.

The following are a couple of observations that other newbies may be interested in:

Of course Google's stock browser Chrome (still) doesn't do Flash so I loaded Puffin to watch my local TV news station's live feed and for MeTV's great oldies. Puffin worked well with the local news channel but the MeTV shows were a little jerky & sound wasn't synchronized well. The problem was probably at MeTV's server but, to be sure, I installed Dolphin and tried watching on it.

Dolphin is a no-go on the LolliRock'd Nexus Player. It put the Nexus in portrait mode and, as I couldn't find a setting to force landscape mode, I downloaded a widget to do it. Then, when I tried Dolphin again, it crashed, no warning.

FlashFox browser also crashes immediately but, unlike Dolphin, FlashFox does give an excuse. An info screen advises that FlashFox doesn't currently run on Intel's processors.

As noted in earlier posts, LolliRock v.1.5 doesn't itself have functionality to eliminate the over scan built into TVs back in the days when screens were cathode ray tubes. That dinosaur tech, as it aged, shrunk the images displayed on it. Over scan was the industry's remedy for image shrinkage. Sixty years later the reason for over scan, CRT displays, no longer exist but the "cure" continues, for some reason. Some new LCD TVs can fix over scan with a visit to settings, mine couldn't. But a free download, "UI Tuner" by Bassel Bakr, fixes it.

"UI Tuner" works flawlessly, in my experience, but it is a little short on instructions. So, here are mine: download it, open it, change over scan from "0,0,0,0" to "32,16,32,16". Then drop down and check the box beside, "Set on boot..." That's it!

LolliRock is TERRIFIC! Three thumbs up!
[Nexus Player Original Android Development] bkdg100:
5.1 ?

any chance we will see 5.1 updates to this rom ?

http://www.xda-developers.com/android-5-1-details-whats-changed/
[Nexus Player Original Android Development] zulu99:
Sure, if i have time, i will try in this weekend.
[Nexus Player Original Android Development] frigidazzi:
Delete
[Nexus Player Original Android Development] zulu99:
Android 5.1 is coming. I'm working on it.....
[Nexus Player Original Android Development] bkdg100:
yeaaaaaaaaa!!!!!!!
[Nexus Player Original Android Development] Mandulli:
someone has already tried if Xposed running?
[Nexus Player Original Android Development] npjohnson:
No custom Recovery for he NP yet, so nope, and you can't move the files in place while the system is booted.

---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------

Huh. These seem odd. Strange question, but does your router run at 2.4 GHZ, or 5 GHZ? And does it use b. g, a, or n frequency? I had to disable all but the a frequency to get Google services to work for me, as the "n" standard that my router gives has serious issues with SSL and therefore Google logins.

Another question, would you be willing to share the vendor and device tree files you use to build AOSP? I'd like to see if we can start CM nightlife for this device.
[Nexus Player Original Android Development] zulu99:
On official Lollirock 1.5 firmware android 5.0.2 all work well with my router.

The problem came from the fact that the new 5.1 firmware have inside something that not permit the nexus player to complete well the first boot and not send BOOT_COMPLETED well every time the device boot. Infact i have problems also with all apps that rely on boot complete, like my droidmote or also chromecast media shell.

I'm looking at this file https://android.googlesource.com/pl...android/server/am/ActivityManagerService.java in the method final void finishBooting() {

at line 6149 that was changed in 5.1

i will share the device tree, but i want also update the google apps inside. i will share as rar package because i not have time to maintain a github. so also others developers can work on it. i already tested cyanogenmod and it compile and boot.

i will upload the device tree + vendor folder working version that is inside the 5.0.2 firmware.
[Nexus Player Original Android Development] danigraham:
Is loss of sound randomly in apps because of the Nexus Player remote? (As I read in the OP) Seems to happen to us in Kodi more often than not, does anyone know why the remote would cause audio to cease existence? ?

New to the thread, thanks for Lollirock!!
[Nexus Player Original Android Development] zulu99:
Lollirock 5.0.2 device tree + vendor folder. Useful to compile your firmware or build a cyanogenmod.

Read the file note.txt inside fugu folder after compilation.

If you use this package not forget to mention me.

http://goo.gl/cVWmwB
[Nexus Player Original Android Development] ruZZ.il:
Kudos on the device/vendor work.

We also had to do some work with libaudio. You did a thorough job :good::) . Google did some annoying hacks. They seem to have gone out of their way for the Nexus Player to have limited functionality.

kudo++ on the camera work.

I notice in your notes you state what to add to default.prop. Those can be added to ADDITIONAL_DEFAULT_PROPERTIES in your BoardConfig.mk
[Nexus Player Original Android Development] npjohnson:
Thank you. Credits will always be given. :)
[Nexus Player Original Android Development] zulu99:
For information, for note and future development. Today 15.03.2015

On Android 5.0.2 - LolliRock 1.5 i updated all Google apps from Google Play.

I updated manually Google Play Services to last version 7.0.96 (1785884-470 from here http://www.apkmirror.com/apk/google...ices-7-0-96-1785884-470-android-apk-download/

I updated manually Google Cast Receiver to last version 1.12.28389 from here http://www.apkmirror.com/apk/google...ast-receiver-1-12-28389-android-apk-download/

All work well.

What this mean ?

That new Google apps not block chromecast functionality. But despite this in Android 5.1 that i'm testing, chromecast not work with the same google apps. Maybe there are some problems on android 5.1 for now, because the problems are also others. Can be also possible that are related to closed binary. I'm testing, but not relevant error from logcat help me to understand.

I see strange behaviour of wifi and block of the ui when i try to login to google play. Some time instead i can login in google play but i must correct the wifi behaviour that does not connect early to the router when the device boot.
[Nexus Player Original Android Development] npjohnson:
This can definitely all be related to an old binary, as 5.1 changed alot in the modem/WiFi area. What WiFi Chipset does the NP Use? Its possible that we can just Kang a 5.1 binary from another device on 5.1.
[Nexus Player Original Android Development] zulu99:
bcm4354, the nexus 9 if i remember well have similar wifi module, but is connected to the board in different way. Have different configuration but some firmware files. We can investigate on this.

The wifi in 5.1 work, but create very strange problems....

I need others testers, in next days i will post the test 5.1 build, so also others can help me to understand well the problem.
[Nexus Player Original Android Development] bwells88:
I'll be ready and willing to test when you are ready... 8)
[Nexus Player Original Android Development] roebling:
I'll test it

I'll help, whenever you are ready.

Until then, I'm loving 1.5!
[Nexus Player Original Android Development] Otisrhw:
I have nexus 9, 6 and player let me know if ya need something.
[Nexus Player Original Android Development] zulu99:
As i promised in the link below the test Android 5.1 version.

This is only for advanced users and developers to understand why the login process in Google Play create problems.

Also the wifi not start fast at boot,

but to solve this bug go in Settings -> Wifi -> Advanced -> Scanning always avaiable swith to ON

Help me to understand where are the problems.

link removed because i have a new version.

UPDATE:

solved with new kernel and binary.
[Nexus Player Original Android Development] ruZZ.il:
:good::good:

I haven't got a device with me over w.end..

Will try play with it next week.

P.S

This doesn't solve the wifi scan root issue, though I see def_wifi_scan_always_available = 0 in f../b../packages/SettingsProvider/res/values/defaults.xml

You could override it in device/asus/fugu/overlay.. (Or, do it once manually..)

Not sure of the implications of always available. Shouldn't be a problem as long as it's not hopping around wifi channels scanning while already connected to an AP.
[Nexus Player Original Android Development] zulu99:
UPDATE:

The factory image and binary of 5.1 Android TV are in the usual link. Thanks
[Nexus Player Original Android Development] ke5pcv:
*slightly off topic* Has anyone grabbed the OTA .zip yet?
[Nexus Player Original Android Development] zulu99:
On 5.1 firmware with new kernel (compiled from new source) and with new binary files almost everything is solved.

For now what not work is only chromecast functionality.
[Nexus Player Original Android Development] zulu99:
UPDATE

Thanks for your interest in Netflix, I have identified a problem of compatibility with arm apps. Arm translation is new for me.

Installing this new boot.img you can install the standard netflix app from google play (not the specific android tv version) and many other arm apps should work.

To install decompress the rar archive and extract the boot.img, put the device in bootloader mode:

fastboot flash boot boot.img

fastboot reboot

Now you can install also Skype, and from the next firmware version, make voice calls with hangout and skype.

Let me know if all ok with netflix, i opened the app but i not signed in because i'm italian and i not use netflix.

To scroll the video list in Netflix you can use two fingers very close with DroidMote, if you use it. I know this fact from some US friends.

UPDATE:

new firmware with all inside is avaiable.
[Nexus Player Original Android Development] zulu99:
I have both working. Maybe i added also something to the rom.

Now i reinstall all fresh on my device to be sure and i'll inform you.

Thanks. I solve today.
[Nexus Player Original Android Development] zulu99:
Thanks KalenXI, i found the problem.

Today i will upload a new firmware version to have netflix, skype and more apps working.

Is not only the boot.img but also some files in the firmware.

Only with tests of friends i can see problems and solve. Because when you are in development you can have something in the experimental firmware not present in the official version.

http://oi61.tinypic.com/w1r4tl.jpg

http://oi60.tinypic.com/qnv78h.jpg

http://oi57.tinypic.com/2rp8yzr.jpg
[Nexus Player Original Android Development] zulu99:
New firmware 1.2 in first post. Let me know with your tests.....

✔ Arm translation to be compatibile with arm-only apps. Like Netflix and Skype

✔ Support external microphone from usb webcam.

(tested with Logitech C525 for voice call in hangout and skype, voice search in google now, sound recording )
[Nexus Player Original Android Development] KalenXI:
Netflix works great now. Thanks for your work. Only bugs I'm noticing that are still there from previous version is some pop-up overlays will appear with content briefly but then go black. So far I've noticed it in the Pushbullet settings menu, the Nova launcher swipe action menu, and the Plex video info window. Unfortunately there aren't any errors in the log so I'm not sure what could be causing it but I'll keep looking to see if I can come up with anything. If you dismiss the window then the content again displays for a brief second before the window dismisses.

I've also noticed that the sound occasionally stops working and I need to turn my TV off and back on to get it back. Though from what I've found so far though this seems like it might just be a bug in Android's HDMI or HDCP implementation and not something specifically with this rom.
[Nexus Player Original Android Development] zulu99:
pop-up overlays stuff for some apps is present also in the stock rom, i will work on this problem, but is not very big problem for now.

I'm also interested in this problem, because also when i use two fingers for the first time with DroidMote, i can see some strange shadow around the mouse cursor. But another pinch to zoom with two fingers makes the problem disappear. (also in stock rom is so) I think that there is a problem in the hwcomposer about overlay stuff. i'm not sure.

the sound should have problems only if you connect the NP hardware bluetooth remote for now. but this remote is not very useful with this firmware. only for very basic things especially because you can't control the volume also if you can now with other remotes. also an hdmi input change, get the sound back and the problem disappear forever from my tests.

Thanks for your tests, I'm here to fix everything that is fixable. I used a large number of Chinese Android mini PC, but the quality of the hardware and software of the Nexus Player is unbeatable with a full version of Android inside. I am really enjoying with some benchmarks and video tests, but the real quality of a device can only be seen in everyday use.

Do not forget, that the Nexus Player is also the first Nexus device x86 and the development on this device is also very important for the future of many others x86 devices.

i will share all, not worry for this.
[Nexus Player Original Android Development] LecheConCarnie:
I downloaded the image, wrote it to the NP and then booted up. Went to plug in my OTG cable to plug in a mouse and realized that my OTG cable is a right angle cable so I can't have it and the HDMI cable plugged in at the same time. Fail.

I then realized that I have a powered OTG cable from when I rooted some Chromecasts a few months back. I used a USB mouse to pair a bluetooth mini keyboard and everything looks good so far.
[Nexus Player Original Android Development] sidepart:
Are you able to get 5.1 with it?
[Nexus Player Original Android Development] KalenXI:
Yeah that's what I was thinking too. There's a lot of "W/hwcomposer( 161): bool android::intel::HwcLayerList::checkCursorSupported(android::intel::HwcLayer*): cursor layer is not on top of zorder" warnings being thrown for some reason.

Also I can confirm the firmware works with the mic and webcam (USB) on a Logitech c920 as well. Works great for triggering Google Now from across the room, hopefully going to use it for some voice controlled home automation stuff.

My TV won't do DD+ passthrough to my receiver and the Nexus Player won't do audio unless I plug it into the TV directly so I can't really tell. But there isn't a 5.1/Stereo option in the Netflix UI so I would imagine not.
[Nexus Player Original Android Development] dabotsonline:
Does Netflix work at 1080p?
[Nexus Player Original Android Development] KalenXI:
Apparently not. Even after relocking the bootloader and reinstalling it still won't go above 480p on the Example Short for me.
[Nexus Player Original Android Development] myshyak:
Would appreciate your rom, but with standard leanback launcher.is it possible?
[Nexus Player Original Android Development] zulu99:
Yes yes, we are on the same line. This error is present also in the stock firmware and is from hwcomposer. Fortunately the source code is available and we will investigate with calm. But this is a bug of the original code. I hope that also Intel and Google will investigate on this problem.

For me the webcam mic is useful also to make hangout and skype call from my couch.

But apart this, after some stress tests i can say that this firmware/device Rock :)

With 2GB of ram could be the best Android TV Box that I used.

And i have many many android tv boxes.

I say this not to praise myself, but because the problem of so many Chinese devices, is that the software is not certified and this creates many incompatibilities with apps and also the hardware not have the same quality of the Nexus Player.

In other words, if you install an app made for Android and the device have a firmware that is a thing that is not Android what happen ? :confused: This is valid also for FireTV and FireStick and in this case the simil android version is also very old, therefore not compatible with the new applications.

Android is one and should be the same also on the TV, i not like the fragmentation. Android for the tablets was unified to that for phones just for this reason. Applications and launchers can be differentiated and made more accessible even without touch screen, then the users can choose what to download from Google Play, in this way any Android device could become an Android TV when connected via HDMI or slim port to TV.
[Nexus Player Original Android Development] midnightzak:
My logitech k400 and various other logitech won't work with the OTG cable to allow me past the first screen :(

Guess I'm done for tonight...

EDIT: Bad connection, K400 works great!
[Nexus Player Original Android Development] VannMann:
I just got my otg cable tonight, and my k400 and logitech wireless mouse work fine, keep trying. I do have the problem with the play store not letting me install a lot of the apps I want, like twitch tv and various others.
[Nexus Player Original Android Development] bdkoepke:
Hey Zulu99, I'm interesting in giving you a hand with the usb uvc webcam as well. Defconoi sent me a patch here: http://xdaforums.com/showpost.php?p=57667329&postcount=34 that looks like it should work after some re-working.

Also, thank you for the work you have done here.
[Nexus Player Original Android Development] g0ldenchild562:
Does chromecast work?
[Nexus Player Original Android Development] zulu99:
Thanks, I am very happy to receive the help of all those who want to work together. I'll watch the patch you've reported.

I focused before on the audio, because many things were blocked intentionally.

Now is time for the video part.....

We need more recent code, because Lollipop change also the base structure of the HAL for webcam. In my first attempt, already compiled also in the firmware as experiment, I was watching this code http://git.android-x86.org/?p=platf...heads/lollipop-x86;hb=refs/heads/lollipop-x86 that compile well, but not work for now, in reality I have not yet analyzed the problem.