I have been working on a mobile application for the iPhone/iPod that needs to be installed on the user’s device in “fullscreen mode.” Naturally, I wanted to prevent the user from being bothered by the little magnifying/selecting controls, as well as any long-touch menus. So, I thought that I would make a global CSS declaration:
* {-webkit-user-select: none; -webkit-touch-callout: none;}
Worked a treat until I about went bald trying to figure out why my form elements would not accept user-input. If I touched on a textarea, for example, the keyboard would pop up, and keyup/keydown events would fire, but nothing would get inserted into the element, and no cursor appeared. I put -webkit-user-select: text; in the form element’s css declaration, and everything started working great again.
So not only does AT&T not have good service, and make you PAY for an option to have cell service in your home, they also don’t make it very easy on you to actually use the thing. So I plug this unit in that I picked up off of Craigslist, and I get the following error, even though the guy I bought it from said that he deactivated it.
FTC007: Device serial number is currently associated to another subscriber. Please check the number and try again. If device was recently acquired from another subscriber, please contact that subscriber and ask them to disconnect the device by visiting att.com/3GMicroCell, selecting “Manage your AT&T 3G MicroCell”, logging into their account, and following the online steps for “Disconnect Your 3G MicroCell Device”. If the problem persists, please call 1-800-331-0500.
So, I called AT&T; who really doesn’t know anything more about this than I do, and they tell me that they will have some sort of resolution in about a week. Nice.
In an excellently written article, Steve states clearly why Apple is embracing the future, and not relying on flash.
http://www.apple.com/hotnews/thoughts-on-flash/
So you have your new iPhone®, sync it up to your corporate Exchange® server, and go on your merry way. Later that day, you go to take a picture of that adorable pose your daughter is in. “Ha!” you think, “The iPhone has a great camera for times just like this!” You smile as you pull your sleek little device out. Your smile quickly fades as you frantically search in vain for the camera app. You flip violently through the pages of apps, and finally succumb to your stupidity, and search for camera in spotlight. No Go. Your daughter is long gone, and you’re still there trying to figure out what is wrong. You go through every setting, making sure the restrictions are off in the settings panel. Yep, all’s good there… Hmm. As a last ditch effort, you get on the phone, and call your IT manager, asking if there is anything that he knows of to make a camera disappear in your iPhone.
“Oh, yeah,” he says. “I didn’t check the box to allow your camera in Exchange. I’ll be right on that.” “Nice,” you think silently.
Ok, so nice story. But you want to know how to get your camera back. Here’s the lowdown:
I found a solution to the problem.
Exchange 2007 has active sync policies. One of the options is to disallow the camera.
To resolve the problem do the following.
- Open Exchange Management Console
- Click “Organization Configuration”
- Click “Client Access”
- On the right you should see your active sync policies. Right click the policy and chose “Properties”
- Click the “Device” tab
- Check “Allow camera”
You should be all set. For those of you who are NOT connected to an Exchange server, check the restrictions pane under Settings > General > Restrictions