Develop Bugs

maps app problem

I'm doing an android application that uses google maps android api v2, it's all good when I run it on my emulator (target: Google APIs 17), but when I use it on my lg p500 I get "the app has stopped unexpectedly":

[Q] Any Pdf Annotation app +Palm rejection?

Hi guys,
Are there any apps that's good for pdf annotation and comes with palm rejection for our tab s? i have just tried lecture notes but the palm rejection doesn't really do anything.
Thanks a lot

Game controller Remapping

I have two game controllers, the Ouya Controller and the Logitech F710. Both are excellent for the Fire TV, but I continue to have issues with game compatibility. Some games work flawlessly, others certain buttons do nothing in the game. I've also got the Ouya system apps setup and working well, but there seems to be a lot of controller issues with it. I figured that having the Ouya Controller with the Ouya system apps would reduce controller compatibility. This is not the case. I'm looking for ways to remap the game controllers. I've tried Tincore Keymapper and it works for onscreen controls fairly well. What about actually remapping a controller. Ideally, if I could trick the FTV to thinking one of these controllers was an actual FTV controller, I think that would be the way to go. I'm looking for ideas or apps to try and accomplish this.

Most apps that do not have a keymap setting use default buttons for that app. Lets say you have a game and the controller works, it does not mean the contoller will be setup the way you like. Most games do not even have gamepad support, which blows my mind this day in age. It is not the controller that doesn't work for the game, it is that the games do not have support for gamepads. Just look in the Amazon app store on your Fire TV and it tells you the games that have gamepad support, keyboard support, fire tv controller support and fire TV remote support, and you will see that some apps do not even support gamepads at all including the fire TV gamepad. My advice is if you can use your controller with a game, get used to the configuration and over time it will not be that bad. If you have a game that does not work at all with your controller then it probably never will. There is another solution though, buying a controller that works in different modes. There are gamepads that have different modes for android so that it can be used as a keyboard, touchpad, gamepad and Icade. So if your game requires touch or keyboard you just change the controllers mode. The G910 gamepad seem to be popular with people that need to use gamepads with different input modes, google it to learn more on the subject, better yet watch a youtube video of the controller to see how it works, and if it is what you are looking for.

porkenhimer said:
Most apps that do not have a keymap setting use default buttons for that app. Lets say you have a game and the controller works, it does not mean the contoller will be setup the way you like. Most games do not even have gamepad support, which blows my mind this day in age. It is not the controller that doesn't work for the game, it is that the games do not have support for gamepads. Just look in the Amazon app store on your Fire TV and it tells you the games that have gamepad support, keyboard support, fire tv controller support and fire TV remote support, and you will see that some apps do not even support gamepads at all including the fire TV gamepad. My advice is if you can use your controller with a game, get used to the configuration and over time it will not be that bad. If you have a game that does not work at all with your controller then it probably never will. There is another solution though, buying a controller that works in different modes. There are gamepads that have different modes for android so that it can be used as a keyboard, touchpad, gamepad and Icade. So if your game requires touch or keyboard you just change the controllers mode. The G910 gamepad seem to be popular with people that need to use gamepads with different input modes, google it to learn more on the subject, better yet watch a youtube video of the controller to see how it works, and if it is what you are looking for.
Click to expand...
Click to collapse
I'm well aware of games that do or do not have controller support. That's not my issue. My issue is that between the two controllers I have, some games with controller support are not getting used correctly. For instance, Shadowgun. The L2 button does not function the way it is supposed to which means I can not play the game correctly. This one in particular is for the Ouya, and granted, I'm hacking the ability to play it on the FTV, but still, all other buttons work fine. I seem to recall reading another person having an issue with the R2 and L2 buttons not working right on a game. I want to remap how the FTV uses the controller, not how the games buttons are mapped on a controller.

I have found an interesting situation. So I have the Logitech F710 and the Ouya controller and have testing many different games using both controllers. Some worked fine, some didn't and this was independent of the controller. Many had have some issue. I also have the Logitech K700 Wireless Keyboard/Trackpad, which works wonderfully, by the way. Someone mentioned having an issue with Modern Combat 5 from the Google Play Store not working with the controller, but found that if they disconnected their keyboard, then it worked. I have found this to be true for me, and for several games. An example is Shadowgun. With the keyboard connected, the L2 and R2 buttons do nothing. If I disconnect the keyboard, then start the game, it just works. I've been trying to identify these differences in other games too. This seems to be an odd thing to me. Why should the functionality of one device be dependent upon if another is connected or not? Oh, I also have a simple BT mouse, but that doesn't seem to be affecting anything. I'm wondering if a dongled USB device supercedes a BT connected device in some manner. I'm looking for others that have experienced these differences in controller functionality. I would like to put together a list of games and which controllers work best.

The only way that I know of to remap keys for a device in Android is by creating a .kl file for the controller, which requires root. Sideload keytest.apk to your FTV and use that to determine what the scan codes are for each button on the controller, and then from a shell prompt input "cat /proc/bus/input/devices" without the quotes. That will give you a list of devices and various information on them, so find your controller in the list and pay attention to the vendor and product IDs. Copy the contents from /system/usr/keylayout/generic.kl into a blank text file that you will name Vendor_0000_Product_0000.kl with the zeroes replaced with your device's appropriate vendor and product IDs. From there it's just editing the scan codes to match whatever keys you want them to represent, mount /system r/w, copy the .kl file to /system/usr/keylayout and reboot. Voila, your new keymappings should work.
This might not be the right way to do this, but it does work. I've used this method to reconfigure a Sony DS3, a wireless X360 pad and an aftermarket remote (Mele F10 Deluxe) and it's worked great every time. It should be pointed out that it's a really terrible idea to edit generic.kl directly since a change there changes that keymapping in the software keyboard as well, so if you get something wrong you might not be able to undo your changes.

dismissthesky said:
The only way that I know of to remap keys for a device in Android is by creating a .kl file for the controller, which requires root. Sideload keytest.apk to your FTV and use that to determine what the scan codes are for each button on the controller, and then from a shell prompt input "cat /proc/bus/input/devices" without the quotes. That will give you a list of devices and various information on them, so find your controller in the list and pay attention to the vendor and product IDs. Copy the contents from /system/usr/keylayout/generic.kl into a blank text file that you will name Vendor_0000_Product_0000.kl with the zeroes replaced with your device's appropriate vendor and product IDs. From there it's just editing the scan codes to match whatever keys you want them to represent, mount /system r/w, copy the .kl file to /system/usr/keylayout and reboot. Voila, your new keymappings should work.
This might not be the right way to do this, but it does work. I've used this method to reconfigure a Sony DS3, a wireless X360 pad and an aftermarket remote (Mele F10 Deluxe) and it's worked great every time. It should be pointed out that it's a really terrible idea to edit generic.kl directly since a change there changes that keymapping in the software keyboard as well, so if you get something wrong you might not be able to undo your changes.
Click to expand...
Click to collapse
Thanks for the detailed suggestion. When I get the time, I'm going to try this. I wonder if doing it both with the keyboard plugged in and with it unplugged would yield different codes given that at least the L2 and R2 buttons are affected.
If someone has an official Fire TV controller, I would appreciate it if they could generate that scancode list for it. My goal is to make the Ouya controller 100% copy the Fire TV controller buttons.

xm41907 said:
Thanks for the detailed suggestion. When I get the time, I'm going to try this. I wonder if doing it both with the keyboard plugged in and with it unplugged would yield different codes given that at least the L2 and R2 buttons are affected.
If someone has an official Fire TV controller, I would appreciate it if they could generate that scancode list for it. My goal is to make the Ouya controller 100% copy the Fire TV controller buttons.
Click to expand...
Click to collapse
Vendor_1949_Product_0402 (found in that same keylayout directory) appears to be the kl for the Amazon controller and it will have all of the scan codes for it. If I were you I'd just use that as a template instead of generic.kl. Using generic.kl is going to give you a ton of scan codes being active that you're not going to use, since it's for a keyboard, so it really makes a lot more sense to just start with a gamepad with a similar configuration.

xm41907 said:
Thanks for the detailed suggestion. When I get the time, I'm going to try this. I wonder if doing it both with the keyboard plugged in and with it unplugged would yield different codes given that at least the L2 and R2 buttons are affected.
If someone has an official Fire TV controller, I would appreciate it if they could generate that scancode list for it. My goal is to make the Ouya controller 100% copy the Fire TV controller buttons.
Click to expand...
Click to collapse
Would probably be impossible, cause there are some games that will only recognize the fire TV controller and will not let you use any other gamepad. I guess its Amazons way of saying "if you wanna play this game you have to buy our controller before hand."
---------- Post added at 10:45 PM ---------- Previous post was at 10:28 PM ----------
xm41907 said:
I'm well aware of games that do or do not have controller support. That's not my issue. My issue is that between the two controllers I have, some games with controller support are not getting used correctly. For instance, Shadowgun. The L2 button does not function the way it is supposed to which means I can not play the game correctly. This one in particular is for the Ouya, and granted, I'm hacking the ability to play it on the FTV, but still, all other buttons work fine. I seem to recall reading another person having an issue with the R2 and L2 buttons not working right on a game. I want to remap how the FTV uses the controller, not how the games buttons are mapped on a controller.
Click to expand...
Click to collapse
The problem is that you did not understand my reply. I gave you a solution to your problem and you did not wanna hear it. if you would have googled the controller I told you to google you would have found an app called BitGamesClient. After you install and open the app, click on my joystick and it will install another app called Open Pad Union. After installing it you might be able to remap the buttons for a lot of games, but only if you gamepad is detected by the Open Pad Union app. Some of my gamepads are and some aren't, but you won't know til you try. If your gamepad is detected, when you open games that are compatible with Open Pad Union a controller mapper will popup so that you can map the buttons for that game. Then when you open another game that is compatible the same mapper will popup and let you map the buttons for that game. Not all games work and not all gamepads work, like I said, you won't know what games and gamepads work til you try.

porkenhimer said:
Would probably be impossible, cause there are some games that will only recognize the fire TV controller and will not let you use any other gamepad. I guess its Amazons way of saying "if you wanna play this game you have to buy our controller before hand."
---------- Post added at 10:45 PM ---------- Previous post was at 10:28 PM ----------
The problem is that you did not understand my reply. I gave you a solution to your problem and you did not wanna hear it. if you would have googled the controller I told you to google you would have found an app called BitGamesClient. After you install and open the app, click on my joystick and it will install another app called Open Pad Union. After installing it you might be able to remap the buttons for a lot of games, but only if you gamepad is detected by the Open Pad Union app. Some of my gamepads are and some aren't, but you won't know til you try. If your gamepad is detected, when you open games that are compatible with Open Pad Union a controller mapper will popup so that you can map the buttons for that game. Then when you open another game that is compatible the same mapper will popup and let you map the buttons for that game. Not all games work and not all gamepads work, like I said, you won't know what games and gamepads work til you try.
Click to expand...
Click to collapse
That was because purchasing another controller is not a solution when I currently have spent about $60 on controllers already. In your first response you did not mention apps that might work with my current controllers, but only recommended trying a different controller with multiple modes. I will look into the two apps you just mentioned though. Perhaps they will detect one or both controllers I currently have. Thanks for the input too. Don't take my response against buying another controller a negative against you. I just don't want to spend more money on it.

I am having a similar issue. I've tried the information above already.
Devices:
Nyko Playpad Pro - Vendor 1d79 product 0009
GameStop controller - Vendor 0000 Product 0000
Open Pad Union didn't see either controller.
Keytest.apk doesn't show a keycode when the left and right triggers are used on the Nyko Playpad Pro.
Games:
Dungeon Quest : Nyko does fine except the right and left triggers (which aren't vital to the game) don't work. Gamestop controller works correctly, including triggers.
GP Riptide 2: Nyko works correctly. Gamestop controller triggers don't work (and acceleration and braking are done via triggers).
Oddly, neither have a KL file. I copied the Vendor_1949_Product_0402.kl to each of the above vendor/product numbers and rebooted. No change in behavior.
Is there a way to determine which KL a particular device uses (since neither HAD a KL file before I copied the default amazon controller KL file to look like theirs).
The Nyko controller says it is HID compliant. The Gamestop controller is anyone's guess. The Gamestop controller works like the ipega controllers (same trigger behavior).

ractar28 said:
Is there a way to determine which KL a particular device uses (since neither HAD a KL file before I copied the default amazon controller KL file to look like theirs).
Click to expand...
Click to collapse
Yeah, oddly enough there's a description of how to do that a whole 5 posts up from yours
dismissthesky said:
The only way that I know of to remap keys for a device in Android is by creating a .kl file for the controller, which requires root. Sideload keytest.apk to your FTV and use that to determine what the scan codes are for each button on the controller, and then from a shell prompt input "cat /proc/bus/input/devices" without the quotes. That will give you a list of devices and various information on them, so find your controller in the list and pay attention to the vendor and product IDs. Copy the contents from /system/usr/keylayout/generic.kl into a blank text file that you will name Vendor_0000_Product_0000.kl with the zeroes replaced with your device's appropriate vendor and product IDs. From there it's just editing the scan codes to match whatever keys you want them to represent, mount /system r/w, copy the .kl file to /system/usr/keylayout and reboot. Voila, your new keymappings should work.
This might not be the right way to do this, but it does work. I've used this method to reconfigure a Sony DS3, a wireless X360 pad and an aftermarket remote (Mele F10 Deluxe) and it's worked great every time. It should be pointed out that it's a really terrible idea to edit generic.kl directly since a change there changes that keymapping in the software keyboard as well, so if you get something wrong you might not be able to undo your changes.
Click to expand...
Click to collapse
Edit: So sorry for the snarky response. Apparently I misread what you'd said since you already have the product and vendor IDs. Maybe give this a go instead? I believe if your device gives all zeroes for the IDs like that it probably defaults to Generic.kl, which you CAN edit, but you really shouldn't unless you're certain you know what you're doing. My NES30 gives all zeroes as well and I haven't found a way around it.

ractar28 said:
I am having a similar issue. I've tried the information above already.
Devices:
Nyko Playpad Pro - Vendor 1d79 product 0009
GameStop controller - Vendor 0000 Product 0000
Open Pad Union didn't see either controller.
Keytest.apk doesn't show a keycode when the left and right triggers are used on the Nyko Playpad Pro.
Games:
Dungeon Quest : Nyko does fine except the right and left triggers (which aren't vital to the game) don't work. Gamestop controller works correctly, including triggers.
GP Riptide 2: Nyko works correctly. Gamestop controller triggers don't work (and acceleration and braking are done via triggers).
Oddly, neither have a KL file. I copied the Vendor_1949_Product_0402.kl to each of the above vendor/product numbers and rebooted. No change in behavior.
Is there a way to determine which KL a particular device uses (since neither HAD a KL file before I copied the default amazon controller KL file to look like theirs).
The Nyko controller says it is HID compliant. The Gamestop controller is anyone's guess. The Gamestop controller works like the ipega controllers (same trigger behavior).
Click to expand...
Click to collapse
Interesting that neither controller was detected in Open Pad Union. I've not taken the time to check that app out yet myself, but I would think that if the FTV was recognizing the controller, then it would've captured the button presses. I did play a bit with the KL file for my OUYA controller. I remapped one button which was causing a Home issue. It wasn't from my own tinkering though. I found it on a forum, but can't recall which one.

For Nyko Playpad Pro, here is the KL file I use. This is modified from the original. Note, on Fire TV, there is no original file, as Amazon did not include a KL file for this device. As such, you MUST have root access to make changes.
File location: /system/usr/keylayout
File name: Vendor_1d79_Product_0009.kl
Steps:
1. MUST HAVE ROOTED DEVICE
2. Using ADB
Code:
adb connect <ip address of firetv>
adb shell
su
mount -o remount,rw /system /system
How you GET the file from your computer to the FireTV is up to you.
File contents:
Code:
# Copyright (C) 2010 The Android Open Source Project
# Copyright (C) 2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.
#
# 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.
#
# Nyko Playpad Pro
#
# Buttons
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 315 BUTTON_START
key 158 BACK
key 172 HOME
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 103 DPAD_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN
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
axis 0x09 GAS
axis 0x0a BRAKE
Verified working in Riptide GP2, Minecraft PE, Fields of Battle
The differences seem to be that some games look for "RTRIGGER" and some look for "GAS" and same with LTRIGGER and BRAKE
Edit: It seems that Amazon decided they would rewrite how controllers work and they want the apps to use GAS and BRAKE instead of RTrigger/LTrigger, which means that if the game is "written for" Fire TV, then they use gas/brake. If it was written for other platforms, they look for Rtrigger/Ltrigger. From the above, it would appear that the last entry "wins" in the KL file, so even though I had 0x09 as Rtrigger and Gas, it only send "gas" to the game.
The only choice I see at this point is two different controllers (not same make/model) or start changing keylayout files based upon which profile you need. Absolutely UGLY approach, IMHO.

ractar28 said:
For Nyko Playpad Pro, here is the KL file I use. This is modified from the original. Note, on Fire TV, there is no original file, as Amazon did not include a KL file for this device. As such, you MUST have root access to make changes.
File location: /system/usr/keylayout
File name: Vendor_1d79_Product_0009.kl
Steps:
1. MUST HAVE ROOTED DEVICE
2. Using ADB
Code:
adb connect <ip address of firetv>
adb shell
su
mount -o remount,rw /system /system
How you GET the file from your computer to the FireTV is up to you.
File contents:
Code:
# Copyright (C) 2010 The Android Open Source Project
# Copyright (C) 2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.
#
# 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.
#
# Nyko Playpad Pro
#
# Buttons
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 315 BUTTON_START
key 158 BACK
key 172 HOME
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 103 DPAD_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN
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
axis 0x09 GAS
axis 0x0a BRAKE
Verified working in Riptide GP2, Minecraft PE, Fields of Battle
The differences seem to be that some games look for "RTRIGGER" and some look for "GAS" and same with LTRIGGER and BRAKE
Edit: It seems that Amazon decided they would rewrite how controllers work and they want the apps to use GAS and BRAKE instead of RTrigger/LTrigger, which means that if the game is "written for" Fire TV, then they use gas/brake. If it was written for other platforms, they look for Rtrigger/Ltrigger. From the above, it would appear that the last entry "wins" in the KL file, so even though I had 0x09 as Rtrigger and Gas, it only send "gas" to the game.
The only choice I see at this point is two different controllers (not same make/model) or start changing keylayout files based upon which profile you need. Absolutely UGLY approach, IMHO.
Click to expand...
Click to collapse
Good to know, but sucks for us. I've been wondering if an Xposed module could be made to switch KL files based upon which game is played.

[Q] Nexus 7 Multi Channel/Surround Sound with USB DAC

Hi.
I want to playback sound from my Nexus 7 2013 (Flo) in a fixed install environment on a Mutli Channel USB Audio DAC. It is a 7.1 Channel device and has a CMedia CM6206 chip. I currently use the stock Android 5.1.1 build LMY47V.
From what I've read a multi channel source, e.g. a movie, should play fine, but the difficult part seems to be the spreading of stereo sound onto multiple channels. After reading through different articles related to ALSA I finally found an example configuration which does exactly what I need:
http://drona.csa.iisc.ernet.in/~uday/alsamch.shtml
Sadly it is for Linux Desktop Editions and Android seems to be quite different (Driver Layer, Configuration ...). After figuring that out I came across this thread:
http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-surround-sound-t2964809/post57310487
Where I finaly found the place the mixer configuration would probably go to. But now I'm stuck on translating the .acoundrc file into the right XML statements. This is where I want to ask the experts here on XDA Developers...
What I got so far:
- Device is rooted
- Alsa Mixer is installed
- Example .asoundrc
The USB DAC enumerats (with alsa_aplay -L) as "default:CARD=Device" or as (with alsa_aplay -l) "card 1".
Thanks and best regards,
Martin.

SHIELD TV FULL Casting Hack Fix {Casting WatchESPN Now Works Like A Charm}

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable FULL Casting Functionality, WatchESPN App Now Works, When Casting It To The Shield TV Console.
Notice The Line Of Code In The Above Shield TV Build.Prop "ro.buld.type=user" This Line Of Code As It Is Kills/Block/Prevents
Casting The WatchESPN App From Any Android Smartphones/Tablets.
The Correct Line Of Code Should be "ro.build.type=eng"
HOW TO ENABLE CASTING THE WATCHESPN APP TO THE SHIELD TV CONSOLE
Casting ALL Apps That Has The Casting} Functionality/Feature AFTER YOU HAVE ROOTED YOUR
SHIELD TV Using {"Root Browser"} Found At The Link Below With Leanback Launcher Code. It Will Also Lock The Code Change
Via The Save Option. {EXCEPTION} This Tool Will Not Unlock The Change, When You Reboot Your Device. I Had Unlocking
Issues With Other Root Explorers After Rebooting The Shield TV Box.
EASY INSTRUCTIONS USING THE ABOVE TOOL
Go to System> Build.prop, click on Build.prop, a drop menu will appear, click on "Open with", another pop up menu will appear ...
Next, click on "RB Text Editor", your device Build Prop will appear, go down to "ro.build.type user" and change "user" to "eng" without quote marks ...
Click on "SAVE" in the upper right corner, follow screen prompt, now go back into your build.prop to make sure the changes are still there, if it's still there, just back out, reboot your device ...
Give it a test run ...! If you should encounter any issues, get back with me ASAP 24/7, enjoy.
<MOD Edit - Link Removed.>
PLEASE NOTE: MY ANDROID TV APPS WORKS WITH JUST ABOUT ALL ANDROID TV BOXES, BACKWARD/CROSS READY COMPATIBLE WITH CHINESE MADE ANDROID TV BOXES ALSO, RK3188/RK3288/RK3368 {No Install Error Message}!

I've tested casting youtube and mirroring my Smartphone display after the 2.1 update. All functions are working as they should without root and any modification on my shield tv.

Casting For Me Now Works
scorpio16v said:
I've tested casting youtube and mirroring my Smartphone display after the 2.1 update. All functions are working as they should without root and any modification on my shield tv.
Click to expand...
Click to collapse
A lot of people are having issues after they updated to the 2.1 upgrade today, saying their casting functionality is broke. I for one could not cast WatchESPN app or YouTube. All I can say you are very lucky, I wish I could see your build.prop.

That's no problem. But I doubt, that the build.prop contains something special.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=LMY47D.35739_609.6420
ro.build.version.incremental=35739_609.6420
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Oct 8 13:57:46 PDT 2015
ro.build.date.utc=1444337866
ro.build.type=user
ro.build.user=NVIDIA
ro.build.host=mobile-u64-396
ro.build.tags=release-keys
ro.build.flavor=foster_e-user
ro.product.model=SHIELD Android TV
ro.product.brand=NVIDIA
ro.product.name=foster_e
ro.product.device=foster
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=NVIDIA
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=foster
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=foster_e-user 5.1 LMY47D 35739_609.6420 release-keys
ro.build.fingerprint=NVIDIA/foster_e/foster:5.1/LMY47D/35739_609.6420:user/release-keys
ro.build.characteristics=tv
# end build properties
#
# from device/nvidia/soc/t210/system.prop
#
# opengles.version is 16.16 (maj.min) fixed point
ro.opengles.version=196609
persist.tegra.nvmmlite=1
persist.wlan.ti.calibrated=0
ro.sf.override_lcd_density=1
# glcomposer composition
persist.tegra.compositor=glcomposer
persist.tegra.decompression=cde-client
# WAR for bug 1536227: Restrict all ZBC clears to transparent black:
persist.tegra.AF73C63E=0x80007ffd
# disable input resampling
ro.input.noresample=1
#enable Miracast game mode support
nvwfd.gamemode=1
#max resolution supported for Miracast is 1080p, represented interms of macroblocks
nvwfd.max_macroblocks=8160
# usb vendor and product ID definition
ro.nv.usb.vid=0955
ro.nv.usb.pid.mtp=B430
ro.nv.usb.pid.mtp.adb=B431
ro.nv.usb.pid.rndis=B434
ro.nv.usb.pid.rndis.adb=B435
ro.nv.usb.pid.ptp=B432
ro.nv.usb.pid.ptp.adb=B433
#Set audioflinger resampler quality to DYN_HIGH_QUALITY
af.resampler.quality=7
#
# from device/nvidia/platform/t210/system.prop
#
wifi.interface=wlan0
wifi.Xinterface=xlan0
ap.interface=wlan0
# boot animation property
persist.bootanim.preload=1
#pbc properties
pbc.log.on=0
pbc.hist.size=5
pbc.step.period=700
pbc.polling.period=100
pbc.throttle.depth=0
persist.sys.pbc.enabled=1
persist.sys.pbc.hyst=5
persist.sys.pbc.psys.cap=10000
persist.sys.pbc.ibat.cap=4000
persist.sys.pbc.pbat.cap=30000
persist.sys.pbc.inf.game.mode=1
persist.sys.pbc.inf.socthres=20
persist.sys.pbc.pbat.slope=1.5
persist.sys.pbc.pbat.intercept=-7
persist.sys.pbc.over.cfboost=true
persist.sys.pbc.cfboost.floor=800000
persist.sys.pbc.gfboost.floor=300000
#disable Eco mode with charger
persist.sys.NV_ECO.IF.CHARGING=false
#playback type device, for cec
ro.hdmi.device_type=4
#used to enable adb over tcpip on port 5555 from Settings app
persist.system.adb.tcp.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.media.avsync=true
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=448m
ro.build.version.ota=2.1(22.18.61.16)
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.com.google.clientidbase=android-nvidia
ro.sf.lcd_density=320
ro.nrdp.modelgroup=SHIELDANDROIDTV
ro.nrdp.audio.otfs=false
ro.radio.noril=true
ro.tegra.tz3.sorting=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.features=div
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

scorpio16v said:
That's no problem. But I doubt, that the build.prop contains something special.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY47D
ro.build.display.id=LMY47D.35739_609.6420
ro.build.version.incremental=35739_609.6420
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1
ro.build.date=Thu Oct 8 13:57:46 PDT 2015
ro.build.date.utc=1444337866
ro.build.type=user
ro.build.user=NVIDIA
ro.build.host=mobile-u64-396
ro.build.tags=release-keys
ro.build.flavor=foster_e-user
ro.product.model=SHIELD Android TV
ro.product.brand=NVIDIA
ro.product.name=foster_e
ro.product.device=foster
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=NVIDIA
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=foster
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=foster_e-user 5.1 LMY47D 35739_609.6420 release-keys
ro.build.fingerprint=NVIDIA/foster_e/foster:5.1/LMY47D/35739_609.6420:user/release-keys
ro.build.characteristics=tv
# end build properties
#
# from device/nvidia/soc/t210/system.prop
#
# opengles.version is 16.16 (maj.min) fixed point
ro.opengles.version=196609
persist.tegra.nvmmlite=1
persist.wlan.ti.calibrated=0
ro.sf.override_lcd_density=1
# glcomposer composition
persist.tegra.compositor=glcomposer
persist.tegra.decompression=cde-client
# WAR for bug 1536227: Restrict all ZBC clears to transparent black:
persist.tegra.AF73C63E=0x80007ffd
# disable input resampling
ro.input.noresample=1
#enable Miracast game mode support
nvwfd.gamemode=1
#max resolution supported for Miracast is 1080p, represented interms of macroblocks
nvwfd.max_macroblocks=8160
# usb vendor and product ID definition
ro.nv.usb.vid=0955
ro.nv.usb.pid.mtp=B430
ro.nv.usb.pid.mtp.adb=B431
ro.nv.usb.pid.rndis=B434
ro.nv.usb.pid.rndis.adb=B435
ro.nv.usb.pid.ptp=B432
ro.nv.usb.pid.ptp.adb=B433
#Set audioflinger resampler quality to DYN_HIGH_QUALITY
af.resampler.quality=7
#
# from device/nvidia/platform/t210/system.prop
#
wifi.interface=wlan0
wifi.Xinterface=xlan0
ap.interface=wlan0
# boot animation property
persist.bootanim.preload=1
#pbc properties
pbc.log.on=0
pbc.hist.size=5
pbc.step.period=700
pbc.polling.period=100
pbc.throttle.depth=0
persist.sys.pbc.enabled=1
persist.sys.pbc.hyst=5
persist.sys.pbc.psys.cap=10000
persist.sys.pbc.ibat.cap=4000
persist.sys.pbc.pbat.cap=30000
persist.sys.pbc.inf.game.mode=1
persist.sys.pbc.inf.socthres=20
persist.sys.pbc.pbat.slope=1.5
persist.sys.pbc.pbat.intercept=-7
persist.sys.pbc.over.cfboost=true
persist.sys.pbc.cfboost.floor=800000
persist.sys.pbc.gfboost.floor=300000
#disable Eco mode with charger
persist.sys.NV_ECO.IF.CHARGING=false
#playback type device, for cec
ro.hdmi.device_type=4
#used to enable adb over tcpip on port 5555 from Settings app
persist.system.adb.tcp.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.sys.media.avsync=true
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=448m
ro.build.version.ota=2.1(22.18.61.16)
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.com.google.clientidbase=android-nvidia
ro.sf.lcd_density=320
ro.nrdp.modelgroup=SHIELDANDROIDTV
ro.nrdp.audio.otfs=false
ro.radio.noril=true
ro.tegra.tz3.sorting=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.features=div
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Yes it does, this line of code "ro.build.type=user" is the same as mine was, before I made the change. Can you cast
WatchESPN to your Shield TV?

WatchESPN is not downloadable in my country and is flagged as "not compatible with my devices" in the web interface of playstore.
So, my guess is, that people reporting problems, have sideloaded this app ?

Casting WatchESPN Confirmed To Work Via Build.Prop Hack
scorpio16v said:
WatchESPN is not downloadable in my country and is flagged as "not compatible with my devices" in the web interface of playstore.
So, my guess is, that people reporting problems, have sideloaded this app ?
Click to expand...
Click to collapse
I retested it again last night to confirmed, the only way you can cast the WatchESPN app to the Shield TV Console is with the above modified build.prop hack. It will not work
via the Shield TV Console any other way. Actually the above build.prop hack opens up full casting functionality to the Shield TV Console.

The Build.prop Edit Above Should Be On Your Device Anyway By Default
A lot of people are having the casting bug with their Nexus TV Player and Shield TV Console. That's why I highly recommend to all owners of these devices to root your device. When I tell people to root their device, they give me all kinds of excuses like rooting is the death of their device, the great myth.
Rooting you devices gives you the advantage to do great exploits with your device in times like this. Another myth, I might brick my device, your chances of getting hit by a car today is higher, than you bricking your device.
I tell everybody the above build.prop edit is suppose to be in your build.prop anyway by default. That's the reason you are having the casting issues, because it's not in your build.prop by default.

Wow thanks a lot

The Google Cast Receiver File Current Version Is Corrupt
If you are not seeing a cast sign on your Shield TV/Nexus TV, it's due to a corrupt Google Cast Receiver file, which was released on Oct. 13, 2015.
The above build.prop edit will not work without a legit non-corrupt Google Cast Receiver file on the Nexus TV Player or Shield TV.

AndroidTVTech1 said:
A lot of people are having the casting bug with their Nexus TV Player and Shield TV Console. That's why I highly recommend to all owners of these devices to root your device. When I tell people to root their device, they give me all kinds of excuses like rooting is the death of their device, the great myth.
Rooting you devices gives you the advantage to do great exploits with your device in times like this. Another myth, I might brick my device, your chances of getting hit by a car today is higher, than you bricking your device.
I tell everybody the above build.prop edit is suppose to be in your build.prop anyway by default. That's the reason you are having the casting issues, because it's not in your build.prop by default.
Click to expand...
Click to collapse
I used to think like that, i still kinda do...but my major concern these days with root, is hoping for a much more secure less vulnrable way to have admin access.......what you open up with your own device, you also open up to malicious apps........im hopping to see one day a very thorough verification process before root is granted, verification process that cant be hacked, which would keep android unrooted until verified vice versa, root when needed then turned off......major work probabably on the OS level if its even possible.......and you'd still be somewhat vulnerable......but hopefully, from user error rather then exploit...........one, you can be carefull, the other, not much choice
Stagefright, with so many devices out there thats likely to never get a patch, an update or even a mention, just feels like a "you know what waiting to hit the you know where" waiting to happen

Hey guys,
I've been having this problem ever since the upgrade! google just released an update to fix it.
I tested it, working great after the install!
http://www.androidpolice.com/2015/1...-receiver-apk-update-fixes-them-apk-download/

Casting The WatchESPN App Still Requires The Hack Build.Prop Edit In Post #1
Yes, the corrupt Google Cast Receiver File Has Been replaced with a new version, as you recall, I told you what the exact cause was for the casting functionality going down.
Sports fans to cast the WatchESPN app to the Shield TV, you still need the hack build.prop edit in post #1. Actually it's better
to install the build.prop edit on the Shield TV and Nexus TV player. This will gave you first class casting functionality via
all apps with the casting feature.

Sports Fans, Yahoo Sports A Awesome Casting Sports App, Works On The Shield TV
BEST SPORTS APP HANDS DOWN {ChromeCast Now Supported}!
Sports Fans You can cast the Yahoo Sports app to the SHIELD TV/Nexus TV Player/Razor Forge TV!
YAHOO SPORTS UPDATED {Leanback Launcher Code} And {ChromeCast Now Supported}!
Buffalo Bills vs Jacksonville Jaguars
Yahoo Your Ticket To The NFL {Download Below}
Sunday Oct 25th, 9:30am EDT {ONLINE}
Live from London {Watch For Free$ On Yahoo}
Locating The Apps At Google+!
All of my Leanback Launcher apps on Google + are located in one place under "ALL POST" go to "LeanBack Launcher Code Apps Bank" ..! You can scroll down through the apps and pick the ones you want to install on your device.
Download Here https://plus.google.com/communities/103510820500984874818 !
*Don't forget to check out newly released hottest apps with leanback launcher code, that may not be posted on this site yet at the above link!
PLEASE NOTE: MY ANDROID TV APPS WORKS WITH JUST ABOUT ALL ANDROID TV BOXES, BACKWARD/CROSS READY COMPATIBLE WITH CHINESE MADE ANDROID TV BOXES ALSO, RK3188/RK3288/RK3368 {No Install Error Message}!
"I have used pretty much every sports app there is for iphone and this one by far is my favorite.” – Adro!

The New Just Released WatchESPN App Still Cannot Be Casted To The Shield TV
Now On The LeanBack Launcher
A All New Total Sports Network App With Enhanced Picture Pixel Crystal Clear Video Resolution Quality!
The Newly Just Released WatchESPN App Still Cannot Be Casted To The Shield TV Console without the build.prop edit
l{Hack} located in post # 1.
WATCHESPN {ALL NEW} TOTAL SPORTS APP NFL, NBA, MLB, NHL, THE MASTERS, GRAND SLAM!
ESPN, ESPN2 ESPN3 ESPNU ESPNEWS, SEC NETWORK {Download Below} HOT!
The free WatchESPN app lets you keep up with your sports anytime, anywhere on your Android phone and tablet. Watch live games and studio shows with 24/7 access to ESPN, ESPN2, ESPN3, ESPNU, SEC Network, SEC Network Plus, ESPNews, ESPN Deportes and Longhorn Network. You can also watch on-demand clips of the latest news and highlights.
Access to live streaming video from ESPN, ESPN2, ESPN3, ESPNU, SEC Network, SEC Network Plus, ESPNews, ESPN Deportes and Longhorn Network is determined by your TV provider. The providers below offer access to WatchESPN live video:
- AT&T U-verse
- Bright House Networks
- Charter
- Comcast XFINITY
- Cox
- DirecTV
- DISH
- Google Fiber
- Midcontinent Communications
- Optimum
- Time Warner Cable
- Verizon FiOS TV
Please check back regularly as new TV providers are added. Access to on-demand highlights and news is available to everyone regardless of provider.
The WatchESPN app offers live streaming access to thousands of games and events on the ESPN networks, including:
- NFL Monday Night Football (tablet only)
- NBA Regular Season and Playoffs
- Major League Baseball
- The Masters and The Open Championship
- College Football and the College Football Playoff
- Men’s and Women’s College Basketball
- Grand Slam Tennis Events
Get up-to-the-minute news, highlights and analysis with live streaming of your favorite ESPN shows, including:
- SportsCenter
- First Take
- PTI
- College GameDay
- Mike & Mike
- SportsNation
- Baseball Tonight
--
Locating The Apps At Google+!
All of my Leanback Launcher apps on Google + are located in one place under "ALL POST" go to "LeanBack Launcher Code Apps Bank" ..! You can scroll down through the apps and pick the ones you want to install on your device.
<MOD EDIT - Link Removed.> !
*Don't forget to check out newly released hottest apps with leanback launcher code, that may not be posted on this site yet at the above link!
PLEASE NOTE: MY ANDROID TV APPS WORKS WITH JUST ABOUT ALL ANDROID TV BOXES, BACKWARD/CROSS READY COMPATIBLE WITH CHINESE MADE ANDROID TV BOXES ALSO, RK3188/RK3288/RK3368 {No Install Error Message}!

Casting Monday Night NFL Football Via WatchESPN To The Shield TV, Seeing Is Believing
WHO SAID YOU CANNOT CAST WATCHESPN MONDAY NIGHT NFL FOOTBALL TO THE SHIELD TV CONSOLE,
THAT'S WHY I DON'T LISTEN TO WHAT THEY SAY!

Possible to get directtv and xfinity go working?

DirecTV And XfinityGo
chienb said:
Possible to get directtv and xfinity go working?
Click to expand...
Click to collapse
Both of those apps works like a charm, you get those apps at my Google + Leanback Launcher App Bank {Worlds Largest Android TV App Bank}!