[Shield Android TV Android Development] dismissthesky:
I ran into two more problems I can't get past. I'm not sure if they're specific to this rom, or to Android 5.x, or if I'm just plain doing something wrong, but on the off chance that they are this rom's doing I figured this wouldn't be a bad place to ask.

First, I can't seem to get my network share to mount. On my old Fire TV I used the following script, but it doesn't want to work now and I have no idea why:

#!/bin/bash
# script for mounting an SMB share for the firetv
# this script can be run in the following methods
# Directly from a script manager on the fireTV with Root Access
# This script can only mount 1 share, if you have multiple shares you wish to mount create multiple copies of this script - sorry for the inconvienience

#######################################################
# Configuration Section #
#######################################################

#### FireTV Information ###
# These variables should reflect the settings of your fireTV

ftvip='localhost'	#ip address of firetv
adb_id='emulator-5554'	#adb device id, likely correct but verify with adb device (should reflect name of device from output)

#### Share information ####
# Below configure your share settings, this script only supports 1 share per script

share_ip='(my nas ip here)'	#ip address of samba server
share_smb='NAS'	#samba share name
share_path='/mnt/obb/nas/'	#mount point for share, include trailing /, this directory should not exist and should remain in /mnt/obb/
share_usn='(my username here)'	#username for share access
share_pwd='(my password here)'	#password for share access

#######################################################
# Script Functions #
#######################################################
function adb_connect {
adb connect $ftvip
sleep 3
}

function mount_share {
adb -s $adb_id shell "su -c mkdir $share_path"
adb -s $adb_id shell "su -c mount -o noperm,unc=\\\\\\\\\\\\\\\\$share_ip\\\\\\\\$share_smb,username=$share_usn,password=$share_pwd -t cifs none $share_path"
}

function adb_disconnect {
adb disconnect
}

#######################################################
# Main Code #
#######################################################
adb_connect
mount_share
adb_disconnect

I'm thinking it has something to do with adb device id? I've tried several other options, including "foster" and the shell output of "settings get secure android_id", which gave me "687772b827674a1c", neither of which work. The way I've done this in the past is to run this script through Rom Toolbox Lite's scripter app, but if there's a better way to do this I'm all ears. Do I need to have busybox installed to get this done?

The other problem that I'm having is getting the Shield to recognize my customized .kl keymaps. I have an aftermarket remote and several game controllers that I've written customized .kl's for, and I can mount /system r/w and transfer the maps into /system/usr/keylayout just fine, but on reboot they don't make any changes at all. Editing generic.kl just breaks keyboard functionality all around. These were written and used perfectly on my fire tv, so they should be completely functional for Android 4.2.2, but I'm not sure if there were any changes to the handling of .kl files in 5.x. I've checked permissions and have tried everything from 0666 all the way to 0777 without any change whatsoever. Any ideas?