yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] republicano:
I dont know if this ota zip will work but you can try?, assuming you dont want to lose your data by going with googles images

phandroid.com/2014/12/15/nexus-5-6-android-501-factory-image-ota-update-zip/
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
How is that the easiest solution?

Flash stock, then ota? Why not just flash 5.0.1 stock and NOT ota?
[Nexus 5 Q&A, Help & Troubleshooting] JayR_L:
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Its hard on a forum where punctuation isn't used often. I envisage that there should be a comma between "stock" and "flash". True, it could also be a full stop missing.

That said, I've seen many threads where people just say flash stock then ota so I've assumed this is the same..
[Nexus 5 Q&A, Help & Troubleshooting] MiSSigNNo:
With the NRT you just go back flashing to stock bootloader and then you can upgrade via OTA no-pain. After that you can reinstall back twrp (for example) and re-root device. No downloads required from external sources.

If you have to flash you have to go and pick the img and after that re-root. For me is a pain looking for the flash img every version! And worst part having to reboot for each image... boot, radio, system...

But I suppose it is a matter of preferences.

3 step method:

PD: BTW 5.0.1 only have boot and system for flashing?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Still though... Toolkits are bad. Use them at your peril and if you screw up, we're not wasting our time teaching the basics to fix it, that you would know if you did it properly the first time.

And reboot each time? What???

...and looking for image every time? Same place every time mate
[Nexus 5 Q&A, Help & Troubleshooting] JayR_L:
You shan't need a toolkit. For one, Google themselves have put instructions on how to flash a factory image directly. And again, you shan't use toolkits.

And you DO NOT reboot for every image. You flash all of them at once, then you reboot.

Anyway this thread has degenerated to, plain and simply, diarrhea.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] juxxan:
sorry if i publish here but i dont find my phone ;c and sorry for my bad english

i have a samsung galaxy s4 (SCH R970C) from cricket its a CDMA device from USA and i want to know if i can change the motherboard for other one (like sprint or a GSM motherboard) and which one will work? or if is impossible? and why? because is a samsung s4 e.e tell me please ;c
[Nexus 5 Q&A, Help & Troubleshooting] hsas.69:
I flashed the factory images for 5.0.1 and now have no mobile data. Can make and revieve calls as well as text messages but thats it. Tried fixing permissions through twrp and got a boot loop. Reatored back.... Dont have an option to change apn settings. Go to cellular network settings and no option there for apn. Thinking ill have to reflash factory images but hoping there was another option.
[Nexus 5 Q&A, Help & Troubleshooting] MrObvious:
I have an option for APN. I click settings, more, cellular networks, access point names.
[Nexus 5 Q&A, Help & Troubleshooting] hsas.69:
I have checked there and there is no option in the list for apn. Not sure why it isnt but other places i have looked on the internet said it should be in the same place you said.
[Nexus 4 Original Android Development] Cem0:
reserved
[Nexus 4 Original Android Development] robo4130:
Reserved
[Nexus 4 Original Android Development] arceangel:
Congrats on the new ROM. Looks nice. :thumbup::D
[Nexus 4 Original Android Development] mark_d87:
I ll give it a try ;)
[Nexus 4 Original Android Development] santi9604:
Downloading. Thanks for the work.
[Nexus 4 Original Android Development] Hunterzzz:
Great

Will try in a day.
[Nexus 4 Original Android Development] sn0wmis3r:
I cannot get Wifi to turn on with this rom. Anyone else have that?
[Nexus 4 Original Android Development] Cem0:
Not even once
[Nexus 4 Original Android Development] Pishtaz:
No LED notification settings ?
[Nexus 4 Original Android Development] Cem0:
Nexus7 testers needed!

We could build for flo/Nexus 7 2013 but we don't have the device so PM me if you wanna try it on your device (please experienced users only)

btw all features stated in OP [MENTION=4516429]Pishtaz[/MENTION] :)
[Nexus 4 Original Android Development] blttalas:
Good job guys !
[Nexus 4 Original Android Development] Pishtaz:
thanks [MENTION=5977233]Cem0[/MENTION] . I prefer AOSP based roms to CM based .

it's very fast , please add more features in next build (specially LED notifications customize)
[Nexus 4 Original Android Development] Pishtaz:
Dialer fc when calling a contact or USSD
[Nexus 4 Original Android Development] yashade2001:
NOTE FROM DEVS

Hey guys, we fixed dialer fc bug, it will be fixed in version 1.1 . or if you can't wait, just download fixed dialer.apk here http://www44.zippyshare.com/v/34562668/file.html . replace it with /system/priv-app/Dialer/Dialer.apk and give rw-r-r permission (or chmod 644).
[Nexus 4 Original Android Development] Gnome:
Nice! Woot! Woot! Project Disco!
[Nexus 4 Original Android Development] core720:
Please, notification led settings
[Nexus 4 Original Android Development] Cem0:
Happy new year guys.
[Nexus 4 Original Android Development] Cem0:
we got (semi-)nightly builds here: http://downloads.hostingsharedbox.com/mikecriggs/disco/

the latest 12.30 build runs fine on my mako.
[Nexus 4 Original Android Development] core720:
Changelog?
[Nexus Player Accessories] jaykresge:
The purpose of this thread is to illustrate what users can expect from various gamepads when used with the Android TV OS. Attached is the official Nexus Player Gamepad by Asus, which is identical to the gamepad used for the ADT-1 developers kit. We're going to consider this to be the official control scheme for Android TV, and all other gamepads will be compared to it. This is because games that tell you to press a specific button in game are intended to correspond to this scheme. Each button will have a command listed next to it. This command is how the Android TV OS interprets the button press. Additional gamepads will have their buttons compared to this gamepad's buttons, as well as having their OS interpreted command listed.

INDEX:

-ASUS Nexus Player Gamepad (this post)

-Xbox 360 Gamepad (Post #2)

-PS3 Gamepad (Post #3)

D-Pad (UP) = AXIS_HAT_Y(-)

D-Pad (DOWN) = AXIS_HAT_Y(+)

D-Pad (LEFT) = AXIS_HAT_X(-)

D-Pad (RIGHT) = AXIS_HAT_X(+)

A = KEYCODE_BUTTON_A

B = KEYCODE_BUTTON_B

X = KEYCODE_BUTTON_X

Y = KEYCODE_BUTTON_Y

L-Analog (UP) = AXIS_Y(-)

L-Analog (DOWN) = AXIS_Y(+)

L-Analog (LEFT) = AXIS_X(-)

L-Analog (RIGHT) = AXIS_X(+)

L-Analog (PRESS) = KEYCODE_BUTTON_THUMBL

R-Analog (UP) = AXIS_RZ(-)

R-Analog (DOWN) = AXIS_RZ(+)

R-Analog (LEFT) = AXIS_Z(-)

R-Analog (RIGHT) = AXIS_Z(+)

R-Analog (PRESS) = KEYCODE_BUTTON_THUMBR

L-Bumper = KEYCODE_BUTTON_L1

R-Bumper = KEYCODE_BUTTON_R1

L-Trigger = AXIS_LTRIGGER(+)

R-Trigger = AXIS_RTRIGGER(+)

Back = BACK

Home = HOME

Power (CENTER) = KEYCODE_BUTTON_MODE

Known Problems:

-Lacks start button (Soul Calibur cannot be played through)
[Nexus Player Accessories] jaykresge:
Xbox 360 Wireless gamepad was used for this test using the official Microsoft wireless USB dongle for PC connected to the Nexus Player with a USB OTG adapter. I make no guarantees that the wired controller will map exactly the same.

D-Pad (UP) = NOT USED (no equivalent button)

D-Pad (DOWN) = NOT USED (no equivalent button)

D-Pad (LEFT) = NOT USED (no equivalent button)

D-Pad (RIGHT) = NOT USED (no equivalent button)

A = KEYCODE_BUTTON_A (same as official gamepad)

B = KEYCODE_BUTTON_B (same as official gamepad)

X = KEYCODE_BUTTON_X (same as official gamepad)

Y = KEYCODE_BUTTON_Y (same as official gamepad)

L-Analog (UP) = AXIS_Y(-) (same as official gamepad)

L-Analog (DOWN) = AXIS_Y(+) (same as official gamepad)

L-Analog (LEFT) = AXIS_X(-) (same as official gamepad)

L-Analog (RIGHT) = AXIS_X(+) (same as official gamepad)

L-Analog (PRESS) = KEYCODE_BUTTON_THUMBL (same as official gamepad)

R-Analog (UP) = AXIS_RY(-) (function not used in official gamepad)

R-Analog (DOWN) = AXIS_RY(+) (function not used in official gamepad)

R-Analog (LEFT) = AXIS_RX(-) (function not used in official gamepad)

R-Analog (RIGHT) = AXIS_RX(+) (function not used in official gamepad)

R-Analog (PRESS) = KEYCODE_BUTTON_THUMBR (same as official gamepad)

L-Bumper = KEYCODE_BUTTON_L1 (same as official gamepad)

R-Bumper = KEYCODE_BUTTON_R1 (same as official gamepad)

L-Trigger = AXIS_Z(+) (corresponds to R-Analog (RIGHT))

R-Trigger = AXIS_RZ(+) (corresponds to R-Analog (DOWN))

Select = KEYCODE_BUTTON_SELECT (function not used in official gamepad)

Start = KEYCODE_BUTTON_START (function not used in official gamepad)

XBox (CENTER) = KEYCODE_BUTTON_MODE (same as official gamepad)

Known Problems:

-D-Pad is useless in official games (detected, can be mapped with third party software/root/emulators, etc.)

- R/L-Triggers cannot be used for accelerate/brake in official games (Beach Buggy Racing detects and uses the R/L-Bumpers for this controller)
[Nexus Player Accessories] jaykresge:
PS3 Dualshock 3 was tested by connecting via USB to USB OTG. Two gamepads were tested with the same results. This gamepad is unique in that the digital buttons also have analog functionality and can be depressed further, yielding dual-modes for each button. This will be explained below.

D-Pad (UP) = KEYCODE_DPAD_UP (digital) / AXIS_GENERIC_5(+) (analog) (functions not used in official gamepad)

D-Pad (DOWN) = KEYCODE_DPAD_UP (digital) / AXIS_GENERIC_7(+) (analog) (functions not used in official gamepad)

D-Pad (LEFT) = KEYCODE_DPAD_UP (digital) / no analog function (analog) (functions not used in official gamepad)

D-Pad (RIGHT) = KEYCODE_DPAD_UP (digital) / AXIS_GENERIC_6(+) (analog) (functions not used in official gamepad)

CROSS = KEYCODE_BUTTON_A (digital) / AXIS_GENERIC_13(+) (analog) (digital corresponds to A, analog not duplicated)

CIRCLE = KEYCODE_BUTTON_B (digital) / AXIS_GENERIC_12(+) (analog) (digital corresponds to B, analog not duplicated)

SQUARE = KEYCODE_BUTTON_X (digital) / AXIS_GENERIC_14(+) (analog) (digital corresponds to X, analog not duplicated)

TRIANGLE = KEYCODE_BUTTON_Y (digital) / AXIS_GENERIC_11(+) (analog) (digital corresponds to Y, analog not duplicated)

L-Analog (UP) = AXIS_Y(-) (same as official gamepad)

L-Analog (DOWN) = AXIS_Y(+) (same as official gamepad)

L-Analog (LEFT) = AXIS_X(-) (same as official gamepad)

L-Analog (RIGHT) = AXIS_X(+) (same as official gamepad)

L-Analog (PRESS) = KEYCODE_BUTTON_THUMBL (same as official gamepad)

R-Analog (UP) = AXIS_RZ(-) (same as official gamepad)

R-Analog (DOWN) = AXIS_RZ(+) (same as official gamepad)

R-Analog (LEFT) = AXIS_Z(-) (same as official gamepad)

R-Analog (RIGHT) = AXIS_Z(+) (same as official gamepad)

R-Analog (PRESS) = KEYCODE_BUTTON_THUMBR (same as official gamepad)

L-Bumper = KEYCODE_BUTTON_L1 (digital) / AXIS_GENERIC_9(+) (analog) (digital corresponds to L-Bumper, analog not duplicated)

R-Bumper = KEYCODE_BUTTON_R1 (digital) / AXIS_GENERIC_10(+) (analog) (digital corresponds to R-Bumper, analog not duplicated)

L-Trigger = KEYCODE_BUTTON_L2 / AXIS_LTRIGGER(+) (fluctuates, cannot be controlled, second function corresponds to L-Trigger)

R-Trigger = KEYCODE_BUTTON_R2 / AXIS_RTRIGGER(+) (fluctuates, cannot be controlled, second function corresponds to R-Trigger)

Select = KEYCODE_BUTTON_SELECT (function not used in official gamepad)

Start = KEYCODE_BUTTON_START (function not used in official gamepad)

Playstation Button = NOT USED (no equivalent button)

Known Problems:

-D-Pad does not use official mapping, hit or miss (Leanback launcher uses it, Soul Calibur and Beach Buggy Racing do not)

-Potential for issues with dual-mode (Soul Calibur and Beach Buggy Racing worked flawlessly for support buttons, no issues observed)
[Nexus Player Accessories] Magnesus:
Wow, thanks. This is really helpful since I develop games for Android and some button mappings are hard to find. It seems the axis and main button codes are the same, good.
[Nexus Player Accessories] jaykresge:
I'm going to add the Nexus Player Remote tonight or tomorrow after work. It was a stupid omission on my part, and some of its mappings are different from the official gamepad but mirror the PS3, which explains the Leanback compatibility.

Basically, Google has two sets of D-Pad mappings to allow for simple versus complex games. You can map to both simultaneously to support both devices, without any ill effects.

Example: You've already observed that the left analog stick and the 4 lettered face buttons perform identically on the above controllers. To use the D-Pad on both the official and the PS3 gamepad, you can support both mappings as neither gamepad uses the other mapping for something different. This would allow for enhanced compatibility without issues.

The problem comes in support the Xbox 360 gamepad as its buttons differ vastly from the official gamepad. To do so, you'd have to have a custom profile for it, but that would still neglect the D-Pad. Allowing the user to customize controls is still the best option (the D-Pad is detected, just not used by any designed function within Android TV).

Another good practice is to NOT require KEYCODE_BUTTON_SELECT and _START for any games, as Soul Calibur does. While the command is supported within the OS, it's not used on any of the official gamepads so far (ADT-1 and ASUS). Instead, use the Android BACK button to pause the game and bring up the desired context menu.

I still cannot believe that Google put the HOME button where they did on that gamepad. I've hit that so many times because it's in the instinctive position for START.
[Nexus Player Accessories] illuminerdi:
Agreed - this was a stupid oversight on an otherwise great controller. I have to use my Madcatz CTRLR for Soul Calibur because of this.

Is there a way to remap the buttons on the Nexus Gamepad? In theory there is - capturing the original button press and altering it would do it, I'm just trying to figure out the best way to make this happen.

I'm pretty sure it can be done via Tincore keymapper, but I don't know if that exists yet for Android TV, and it might require root (which I don't have), so I haven't yet tried to use it. Plus I kinda hate Tincore keymapper (most. overcomplicated. interface. ever.)

I know that there are keylayout files which, I think, define what "codes" get sent to the OS on certain button presses. In theory we could hack the gamepad's keylayout file so that it's Back and Home buttons send Start and Select instead, right? This too requires root, I believe, but it seems like the most bulletproof fix. I don't know if this will work or not though, my knowledge of these systems is limited - you seem to have better knowledge here, do you think this is a viable possibility?

Thanks!
[Nexus Player Accessories] illuminerdi:
FYI for anyone who is interested in my above post: it IS possible to hack the Gamepad to change the function of the buttons. It's not incredibly easy, but it's also not incredibly hard either. YOU MUST BE ROOTED TO DO THIS.

Example for Nexus Player Gamepad:

Connect to device (Nexus Player, etc) via ADB

Pull the keylayout file for the device you want to alter (the keylayout files are in /system/usr/keylayout) - the Key Layout file for the Nexus Gamepad is (I think, I'm doing this from memory) called "Vendor_0b05_(blahblah).kl"

Edit the file to change the function of the button that currently is "HOME" to "BUTTON_START" or alternatively, alter the "BUTTON_MODE" button (the big center power/circle button) to be "BUTTON_START" if you want to keep your home button as home. Or swap them or do whatever - the point is that if you want a button on the controller to be a start button, one of them needs to be changed to "BUTTON_START" (no quotes on any of these, btw)

Save the file.

Push the file back to your device

Reboot (? not sure if this is necessary, I did it as a matter of course)

Enjoy your start button

Note for anyone reading this who is interested: if you have an ADT-1 and you want to change your gamepad, it's NOT the same keylayout file. The keylayout file for the ADT-1's controller is "Vendor_18d1_(etc)" because the ADT-1's gamepad is considered a Google device, even though it's identical to the Asus one (save for some printing on the buttons).
[Nexus Player Accessories] cbwlkr:
Ouya controller works!

root needed! Unzip and place Vendor_2836_Product_0001.kl file in /system/usr/keylayout

OUYA button:

Short press - Back

Long press - Home

View attachment 3131703
[Nexus Player Accessories] Antar21:
I understand that the Xbox 360 controller maps differently than the np game pad, but can this be corrected in emulators that are currently available on the np? I'm trying to decide whether to buy a Bluetooth gamepad or a otg cable + wireless receiver for the Xbox. I'm only really concerned about player emulators, particularly Nintendo based ones.

If I get the wireless receiver will I be able to map the Xbox controller within the most popular emulators on np? Sorry if this is a dumb question, I'm new to emulators on android.
[Nexus Player Accessories] jaykresge:
You can remap them. The emulators found in my emu thread in the NP General forum all come with pre-configured profiles for the Xbox 360 gamepad, and can be remapped as you prefer.
[Nexus Player Accessories] Antar21:
Thanks for the quick reply, and for all your hard work!
[Nexus Player Accessories] tjsooley:
Modified Layout for Ouya controler

ouya button short menu

ouya button long is home

https://www.dropbox.com/s/wmyjyeldlw2fkdx/Vendor_2836_Product_0001.kl?dl=0
[Nexus Player Accessories] gotroot801:
So if I were to push this file into the proper location, would the Xbox 360 controller work?

In that case, I think I just found a good reason to root my NP.
[Nexus Player Accessories] bunny0007:
There is already a keyleyout for the wired xbox controller in the nexus player so no need for it.

I have modded it for the wireless controller in this file with dpad enabled.
[Nexus Player Accessories] ex0us:
Does this mean one can simply attach and start using the Xbox360 controller without rooting or setting anything up first? Sorry my straight otg cable is in the mail so I can't test yet myself.
[Nexus Player Accessories] jaykresge:
Correct.
[Nexus Player Accessories] koperniczx3:
the xbox360 wireless controller has been nothing but a pain so far.

Works fine in emulators but doesn't work in most games I've tried ..

Can't either move or shoot in Overkill 3, doesn't work with Modern Combat 5 :(
[Nexus Player Accessories] jaykresge:
That's because the button mappings aren't a match for Android TV, so a game has to either allow custom button mappings, or the game has to be written to support the Xbox 360 controller.
[Nexus Player Accessories] just4phil:
hi

this is great, but i am missing the Ids (string / name) of the devices.

what are the exact names of the controllers so that i can identify them on those platforms?

bye

phil
[Nexus Player Accessories] lee25furtado:
Nesxusplayer gamepadfor nexus 5

Hey I just wanted to know if I can use the Asus gamepad on my nexus 5 without purchasing the nexus player.. Please do let me know..thanks..
[Nexus Player Accessories] jaykresge:
Yup, it will work. It's viewed as any other Bluetooth HID gamepad.

I don't recommend it, however. It lacks a true start/select button combo. Games not adapted to Android TV aren't always aware of this. You're better off with a different gamepad.

I've heard questionable things on the quality, and the price sucks, but Razer's Serval looks to be the best gamepad for this purpose, and comes with a built in phone clip.
[Nexus Player Accessories] drakkan88:
Sorry to dig up an old post, but this is a good one. I'm looking for the nexus gamepad's native KL file. I do not own a Nexus Player. Could someone with access to it post the file? Or at least the correct full name?

EDIT - I extracted the original ASUS Gamepad KL file from the factory image, since I do not have access to a Nexus Player and modified the Back and "Mode" (power) buttons. The Back button is BUTTON_SELECT and Mode (power) is BUTTON_START. I have 4 of these controllers connected to a MINIX X8-H Plus that I use for emulators and some gamepad friendly games, such as GTA3, GTA:SA, Max Payne, and more. It was really annoying that the games played flawlessly yet I had no way to open the world map since it requires a "select" button. I was having to use my remote's Menu button and that was just a pain.
[Nexus Player Accessories] unvaluablespace:
Just a heads up, because im sure it will be asked at some point. Dualshock 4 controller works with nexus player via usb otg cable, but the face buttons are a little swapped. adding a kl file with the proper settings can fix that though (which i dont have, sorry.)

connecting dualshock 4 via bluetooth is next to impossible natively, and even if you do get it to pair, there is severe lag which is practically useless. works fine under root with sixaxis app, but this disables the current bluetooth, rendering the nexus remote and any other bluetooth devices useless until sixaxis is turned off again. Should be fine for some users, but this becomes an annoying problem sometimes if not cautious enough. restarting the player without disabling sixaxis renders bluetooth disabled altogether, eventually needing a factory reset or terminal commands. its kind of a hassle if accidents occur.
[Nexus Player Accessories] scottfree1:
Not sure if you still need this but had it open..

Vendor_0b05_Product_4500.kl

# Copyright (C) 2014 The Android Open Source Project

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.

# You may obtain a copy of the License at

#

# http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,

# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

# See the License for the specific language governing permissions and

# limitations under the License.

# Asus Gamepad

key 304 BUTTON_A

key 305 BUTTON_B

key 307 BUTTON_X

key 308 BUTTON_Y

key 310 BUTTON_L1

key 311 BUTTON_R1

key 316 BUTTON_MODE

key 317 BUTTON_THUMBL

key 318 BUTTON_THUMBR

key 158 BACK

key 172 HOME

axis 0x00 X

axis 0x01 Y

axis 0x02 Z

axis 0x05 RZ

axis 0x09 RTRIGGER

axis 0x0a LTRIGGER

axis 0x10 HAT_X

axis 0x11 HAT_Y

led 0x00 CONTROLLER_1

led 0x01 CONTROLLER_2

led 0x02 CONTROLLER_3

led 0x03 CONTROLLER_4
[Nexus Player Accessories] hartleyshc:
Im not sure if this is due to an update to Android 6.0 or not, but I was unable to get the keys to be recognized correctly by editing the Vendor_0b05_Product_4500.kl file for the Asus gamepad. But I had to edit generic.kl for the new keys to be recognized. I set up 172 Home as BUTTON_START, 158 Back as BUTTON_SELECT, then I set up the 316 Mode button as Home, but instead left it as BUTTON_MODE, and use the MODE button in emulators to exit the emu, and go back to Arc Browser.

The good thing is these buttons aren't used on the nexus remote, so changing one home key in generic.kl doesn't change the home button on both devices.
[Nexus Player Accessories] drakkan88:
Excellent! Thank you. This helps when adding support to other devices!
[Nexus Player Accessories] funjai:
Hi guys,

I have a problem with my wired XBOX 360 gamepad from Gamestop. For some reason my controller is recognized by Nexus Player as ''Logic 3'', and the problem is when I try to use controller with any android game (not the emulators) button mapping is always awkward.. For example in Walking Dead game analog sticks are not working at all, which makes game unplayable.

I already copy this file ''Vendor_045e_Product_0719.kl'' to my NP but the problem is still there..

If anyone can help, it would be much appreciated.

Thx