Related
Flashed with RUU of froyo after the update.zip failed (missing too many files like cityid) So its now back rooted and everything is working great from what I can tell. However I just mounted it to copy some files over to the SD card an noticed now 3 drives are there. The two normals, emmc and sdcard, plus a 3rd Virtual CDrom which what I assume is the install for 3g mobile hotspot or something.
So I really never plan on using that, anyone have an idea on how to remove that?
Remove cdrom.iso to avoid being prompted to install Verzion/HTC hardware when the device is connected via USB. This is what the Virtuous ROM did. I have not tested this without the Virtuous ROM: http://forum.xda-developers.com/showthread.php?t=765447
Cool, found it in /etc/CDROM.ISO I just renamed it and you are right, its not showing files, but it still has the CD drive itself, any ideas on that?
mims1979 said:
I just renamed it
Click to expand...
Click to collapse
What did you rename it to?
Aesir Rising said:
What did you rename it to?
Click to expand...
Click to collapse
CDROM.bak works, u can even just delete that file.
k.electron said:
CDROM.bak works, u can even just delete that file.
Click to expand...
Click to collapse
that's what I was trying to get at with the OP. If the file name was renamed, but not the extension, then the 'drive' would still mount.
This has been reported to work as well:
Dial ##7764726
Hit Call
Type Password 000000 (that's 6 zeros)
Hit Feature Settings
Choose CD ROM
Click Disable
Hit menu, commit modifications (it will say no item changed)
INTREPID-NY said:
This has been reported to work as well:
Click to expand...
Click to collapse
Makes sense. Some corporations I know wouldn't allow their employees to hook up their phones to their PCs if it was trying to mount CDs for app installs. Either way, I'm going to try that. Thanks for the info.
[Edit: That did work for me, btw.]
INTREPID-NY said:
This has been reported to work as well:
Dial ##7764726
Hit Call
Type Password 000000 (that's 6 zeros)
Hit Feature Settings
Choose CD ROM
Click Disable
Hit menu, commit modifications (it will say no item changed)
Click to expand...
Click to collapse
That worked great. Thank you.
INTREPID-NY said:
This has been reported to work as well:
Dial ##7764726
Hit Call
Type Password 000000 (that's 6 zeros)
Hit Feature Settings
Choose CD ROM
Click Disable
Hit menu, commit modifications (it will say no item changed)
Click to expand...
Click to collapse
Thank you works great.
crashdogy said:
Thank you works great.
Click to expand...
Click to collapse
no go for me... The Droid X doesn't have a "feature settings" section of th Programming Menu.
what am I doing wrong?
when I enter ##7767426 on the dialer it
just returns to its screen (waiting for a
call to be dialed).
Can the utility be directly called from the
shell prompt? in winmo the ## codes
were all dialer short cuts to various
functions (mostly call to epst.exe).
I figured something similar was done
here too.
(my environment is in sig)
INTREPID-NY said:
This has been reported to work as well:
Dial ##7764726
Hit Call
Type Password 000000 (that's 6 zeros)
Hit Feature Settings
Choose CD ROM
Click Disable
Hit menu, commit modifications (it will say no item changed)
Click to expand...
Click to collapse
That worked so well! Thank you so much! This was getting so annoying
I recently upgraded to Stock Froyo but rooted and every time I plug in my device I get the popup asking me about the virtual CD-Drive and if I want to install some drives. I do not want to do this and it is very annoying to have the pop-up and was wondering if there was a way to get rid of it without using a new custom rom.
Solved. Solution is:
Dial ##7764726
Hit Call
Type Password 000000 (that's 6 zeros)
Hit Feature Settings
Choose CD ROM
Click Disable
Hit menu, commit modifications (it will say no item changed)
Sent from my ADR6300 using XDA App
If you are like me you are not happy with the power button placement. I modded a few files that will allow any bluetooth keyboard to wake the screen from sleep. Very handy when the Xoom is docked. Requires Reboot.
Modded Files
Push the files via adb to /system/usr/keylayout/
Example:
adb remount
adb push Generic.kl /system/usr/keylayout/Generic.kl
adb reboot
Apple Keyboard (Vendor_05ac_Product_0239.kl) - Wake with eject key
Generic Keyboard (Generic.kl) - Wake with F1
Motorola Keyboard (Vendor_22b8_Product_093d.kl) - Wake with right ctrl key (Not Tested - Sorry do not have one)
Note:
After the keyboard and the Xoom have been asleep for a while, there may be a delay before the Xoom wakes. Bluetooth devices sleep to save power and it takes about 15-30 seconds to wake and sync again.
Thorough Explanation of Key Remapping:
Better explanation of this is here.
Getting back to default:
If you want to return things to default, download the default files and adb push them back to the Xoom.
Sweet! I'm going to give this a try later. Thanks!
Works great with the Motorola BT Keyboard...
edit: I did remap it back to the default CTRL_RIGHT and instead used the unmapped "reserved" key on the keyboard. It is the 4th key from the top right with 3 lines. Since this key is unused, it seemed more appropriate for now. It is key 226 in the mapping.
@triadX1
Sent from my Xoom using XDA App
Maybe someone in this thread can help me. I posted in other threads but nobody replied. I bought a generic BT keyboard with Apple keys. To remap the keys I downloaded a program to get the scancodes for each key and modified the Generic.kl. It di not change anything. The question is now, is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected? I hope I got my point across...Thanks everyone!
[sent with Xooming Android technology]
Just a heads-up: I have what must be an older version of the Apple Keyboard (bought in '97); the VID:DID are 05AC:022C :
Code:
apple 0005:05AC:022C.0001: input,hidraw0: BLUETOOTH HID v1.36 Keyboard [Apple Wireless Keyboard] on 40:FC:89:27:62:5C
I just copied your Vendor_05ac_Product_0239.kl to Vendor_05ac_Product_022c.kl and it works fine. Thanks for the mod!
funnycreature said:
is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected?
Click to expand...
Click to collapse
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
it was easy i just edited one file one line next to menu i put wake
Sent from my Xoom using XDA App
system/ust/keylayout/ and vrdb ....093 something then r/w then right click to edit text and scroll to 125 where it says MENU and make it look like this MENU WAKE and reboot and your good menu key is now wake one press wakes and two presses unlocks
Sent from my Xoom using XDA App
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I found out that the generic keyboard uses the Apple layout. I want to post a How-to soon but I have very little time lately Thanks for the info though; how would I find the information? I tried connecting the keyboard to my laptop via BT and opened the device manager. Is there any property that shows the VID:DID?
I'm curious as to why the key 226 isn't being used when there's actually no key used to open the app menu. I would have assumed the key used for menu (two keys to the right of the spacebar) would be used for the app menu and the unused key (three horizontal lines) would've been for the menu since most apps I've seen with the on-screen menu looks the same. Plus the icon for the Apps menu actually looks like what is on the Menu key for the keyboard.
What would I need to add to the keyboard file to make a key open the application menu? After looking over the keymaps in the file I couldn't see any key on the keyboard that would open the app menu.
Use 226 for whatever
You can remap 226 to be menu if you want, but i don't know the command to open the app "drawer" on honeycomb.
Just like they said above, the file you want to edit is in
/system/usr/keylayout/
I use root explorer because it lets me edit easily as well. If you want to do it the way i do just follow the steps below:
1- Mount R/W when you get in the folder
2- Long hold on "Vendor_22b8_Product_093d.kl"
3- Select "Open in Text Editor"
4- Scroll all the way to the bottom where it says 226 and edit the line to read
key 226 MENU (3 spaces between 226 and MENU)
if you simply want it to be another Menu key. (Before editing, it says unused or tbd or something, just erase all of that )
Alternatively try:
key 226 MENU WAKEif you also want it to wake up your tablet.
Personally, I edited key 125 to wake up the tablet as described above, and put
key 226 POWERso that i could also lock the screen, thus using the otherwise useless key.
As a sidenote, Root Explorer *should* automatically make a backup for you when you edit the keylayout file, but doing one manually (aka: copy and paste somewhere else on your sdcard) is always a smart move.
Good Luck!
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I tried this command and I get a "error: device not found" message. I am using my droid 1 and the blueputdroid app to use my hard keyboard as a bluetooth one. The keyboard works... I just would like to map some things out to open the app drawer and such. Thank you in advance for any help
Sent from my Droid using Tapatalk
That error means adb can't find your xoom. Make sure you have USB debugging enabled
sangreal06 said:
That error means adb can't find your xoom. Make sure you have USB debugging enabled
Click to expand...
Click to collapse
Hmm I have tried it from the zoom itself with a terminal app as well as from the PC and have made sure debugging is running and have gotten the same result each time :/
Sent from my Xoom using Tapatalk
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
B Dizzle said:
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Hmm it STILL doesn't see it. I know I am an unlocked and rooted xoom. I am running rooted apps just fine and browsing all my system files just fine on the computer with Droid explorer. I just can't get it to see my device in adb. Any ideas?
Sent from my Xoom using Tapatalk
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
SPIDERTECH said:
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
Click to expand...
Click to collapse
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
SPIDERTECH said:
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
Click to expand...
Click to collapse
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
ruvort said:
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks for that. It looks like the 226 key is STILL not being used. I'm curious now as to what the additional shortcuts were supposed to be.
Got a few questions specifically regarding the new aokp JellyBean rom for the Epic, and I thought I'd post them here since the original thread got shut down:
1. Is there any way to get the "enter" button to not send messages in the SMS application?
2. Is there any way to prevent the "mount your USB storage!" popup from coming up every time the device is connected to a computer?
3. Back on the samsung based roms, I was able to to type ##debug## to get to a menu where I could force 1xrtt mode for extremely low signal situations. In the new rom, I found you can get to that same menu by typing in *#*#debug#*#*, but any screen prompting for the msl code is now impassable. I know my msl code, but it gives me a "modem error" no matter what I type and asks "modem exception occurs", to which the only option is "yes" (clicking it just closes the application).
Any way to get around this?
Thanks
b
Bill720 said:
Got a few questions specifically regarding the new aokp JellyBean rom for the Epic, and I thought I'd post them here since the original thread got shut down:
1. Is there any way to get the "enter" button to not send messages in the SMS application?
2. Is there any way to prevent the "mount your USB storage!" popup from coming up every time the device is connected to a computer?
3. Back on the samsung based roms, I was able to to type ##debug## to get to a menu where I could force 1xrtt mode for extremely low signal situations. In the new rom, I found you can get to that same menu by typing in *#*#debug#*#*, but any screen prompting for the msl code is now impassable. I know my msl code, but it gives me a "modem error" no matter what I type and asks "modem exception occurs", to which the only option is "yes" (clicking it just closes the application).
Any way to get around this?
Thanks
b
Click to expand...
Click to collapse
1: press the function key before enter.
2: No idea.
3: Have you tried using voice search to access the menu? Also, you could buy ROM Control for this.
Sent from my SPH-D700 using Tapatalk 2
2. Turn on USB debugging in Settings - Developer Options. If you can't find it, go to Settings - About phone, tap Build number 7 times and return.
Sent from HTC Incredible S @ CM10.1
cq
nikon120 said:
1: press the function key before enter.
Click to expand...
Click to collapse
Sorry, I should've been more specific. I was actually aware of this, but I was hoping that there would be a way to change this functionality on the stock messaging application so that I don't have to hit the Fn key to get the enter button to do what it's supposed to do.
nikon120 said:
3: Have you tried using voice search to access the menu? Also, you could buy ROM Control for this.
Click to expand...
Click to collapse
It's not that I can't access the menus, it's that some parts of the menus prompt for my MSL code before I can access them, and for some reason, typing in my MSL code (000000) doesn't do the trick anymore, it just gives me that "Modem Error" and lets me know that a "Modem exception occurs". My only choice in the dialog is "Yes", but that just exits the menu completely.
AndyYan said:
2. Turn on USB debugging in Settings - Developer Options. If you can't find it, go to Settings - About phone, tap Build number 7 times and return.
Click to expand...
Click to collapse
I actually do have USB debug enabled already and a widget to easily toggle it off for use with computers that don't have the driver installed. I see the popup upon USB connection with USB debug enabled or disabled.
b
Bill720 said:
It's not that I can't access the menus, it's that some parts of the menus prompt for my MSL code before I can access them, and for some reason, typing in my MSL code (000000) doesn't do the trick anymore, it just gives me that "Modem Error" and lets me know that a "Modem exception occurs". My only choice in the dialog is "Yes", but that just exits the menu completely.
Click to expand...
Click to collapse
I'm not sure if you're saying your MSL code is 000000, or if you were using zeros as placeholders. If you are saying that your MSL is 000000, that would be very unlikely. To get your correct MSL, use a Terminal Emulator of your choice and type "su" and press enter, then "getprop ril.MSL" press enter again and you should see your MSL. Also, you wouldn't happen to be using a NS4G modem, would you? I'm not too sure on ways to fix this, because it hasn't happened to me.
Sent from my SPH-D700 using Tapatalk 2
q
jeffreyjicha said:
I'm not sure if you're saying your MSL code is 000000, or if you were using zeros as placeholders. If you are saying that your MSL is 000000, that would be very unlikely. To get your correct MSL, use a Terminal Emulator of your choice and type "su" and press enter, then "getprop ril.MSL" press enter again and you should see your MSL. Also, you wouldn't happen to be using a NS4G modem, would you? I'm not too sure on ways to fix this, because it hasn't happened to me.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Good question - My MSL is, as a matter of fact 000000, (I even doublechecked with the terminal on the off chance that something changed it) because I changed it to that to make it easier to access in CDMA workshop, qpst, and qxdm back when I was working to clone my old phone's service so that I could continue using my sprint sero $30 unlimited data plan.
As for the modem, I am still using the stock Epic EL30 modem. Would this be causing the problem? And if you don't mind sharing, which rom and modem are you using? What happens when you dial *#*#DEBUG#*#* at the dialer?
Thanks
b
Bill720 said:
As for the modem, I am still using the stock Epic EL30 modem. Would this be causing the problem? And if you don't mind sharing, which rom and modem are you using? What happens when you dial *#*#DEBUG#*#* at the dialer?
Click to expand...
Click to collapse
Like I said, I'm not sure what causes the modem exception error. I'm using Effsi's 0611 build of PACman ROM with didhiy's 0606 nitest, and the NS4G LF2 modem. And when I dial that, it prompts for the MSL, I put in my MSL and it goes to the debug menu with no problem.
Sent from my SPH-D700 using Tapatalk 2
*EDIT* This appears to only be working for people with NON-unlimited data plans. I apologize for the inconvenience...
Saw this over in the AT&T subforum, originally posted by @ExTREmE99 , just reposting here.
This will disable the carrier check on your Verizon G4 and allow you to use the native WiFi tether - no root needed!
1. Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2. Enable USB debugging under Settings -> Developer options
3. Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4. Start an adb shell: adb shell
5. In the adb shell, run these commands one by one:
settings put global tether_dun_required 0
settings put system tether_entitlement_check_state 0
reboot
When your phone comes back up you will have a fully functional native WiFi tether
i must be doing something wrong because i still get the "you need a subscription" popup
Worked for me, thanks! Needed this a few days ago and couldn't use it n was like "F***, wish I had root" hahaha. Oh and also shouldn't this be posted in General?
jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot
Congobongo said:
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot
Click to expand...
Click to collapse
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
I see it after i reboot and try using the hotspot app
jrc27 said:
I see it after i reboot and try using the hotspot app
Click to expand...
Click to collapse
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.
Tomyk89 said:
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.
Click to expand...
Click to collapse
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...
jrc27 said:
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...
Click to expand...
Click to collapse
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!
Tomyk89 said:
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!
Click to expand...
Click to collapse
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox
jrc27 said:
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox
Click to expand...
Click to collapse
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?
jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Should it be? I assumed stuff like this went under the Help section since it was helping people. Maybe I'm wrong. If a MOD would like to correct me and maybe move the thread, feel free.
Tomyk89 said:
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?
Click to expand...
Click to collapse
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!
jrc27 said:
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!
Click to expand...
Click to collapse
no problem dude. try some of my suggestions tomorrow and get back to me. feel free to PM and we can post the final solution up here as to not fill the the thread up with troubleshooting.
No Go...
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.
joebrady119 said:
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.
Click to expand...
Click to collapse
have you taken the latest OTA update?
Tomyk89 said:
have you taken the latest OTA update?
Click to expand...
Click to collapse
Have not taken any OTA.
This unfortunately doesn't seem to work for me either
I had to put my device in PTP mode in order for ADB to show the device, after the device was confirmed with adb devices, I issued the commands this is the output
Code:
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb devices
List of devices attached
VS986931(changed the last four for security) device
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb shell
[email protected]:/ $ settings put global tether_dun_required 0
settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
settings put system tether_entitlement_check_state 0
[email protected]:/ $
When I attempt to enable hotspot I am greeted with the "Use of this service requires a subscription..."
FoxFi seems to work, I just HATE having to change my lock screen in order to use the damn thing!
I'm willing to run further tests and commands if you would like, please just let me know.
I have NOT taken any over the air update. I used the Debloater tool and blocked/hid the app.
Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
Here's a screenshot of my terminal window:
I'm using the native tethering just like everybody else (Settings, More, flick the tethering switch to On and receive the service check). Haven't taken the OTA and have the service disabled via debloater tool. I appreciate the help!
At this point I'm not sure why some are reporting that this works while others aren't. I added a message on the original post warning that this isn't a for sure thing. I'll be sure to update if/when I find a fix or what is going wrong, but for now I think I have enough info to look into this. thanks for your help everyone and I hope that I can find a fix for this. Worst case - we have to wait until we have root to enable this.
-tom