Invisible Shield - iPhone 3G

sealevel · 08-29-2007, 01:16 PM

Put Invisible Shield on iPhone and now get a message "this accessory is not compatible with the iPhone do you want to put in airplane mode?" Anyone had experience with this?

Otherwise Invisible Shield looks and works great.

RyanP · 08-29-2007, 01:56 PM

I'm not sure what Invisible Shield is--does it plug into the phone? That message is typically given when you plug an iPhone into an accessory that was made for an iPod. Some accessories can be affected by the fact that the iPhone iPod is also serving as a phone that can receive a cell signal (accessories like an FM modulator or stereo dock). So when you plug an iPhone into an accessory that's not specific to the iPhone, iPhone asks you if you want to turn on Airplane Mode (thus disabling the cell phone side of the phone).

sealevel · 08-29-2007, 02:12 PM

Quote:

Originally Posted by RyanP

I'm not sure what Invisible Shield is--does it plug into the phone? That message is typically given when you plug an iPhone into an accessory that was made for an iPod. Some accessories can be affected by the fact that the iPhone iPod is also serving as a phone that can receive a cell signal (accessories like an FM modulator or stereo dock). So when you plug an iPhone into an accessory that's not specific to the iPhone, iPhone asks you if you want to turn on Airplane Mode (thus disabling the cell phone side of the phone).

It's a clear plastic coating put on like tinting on car windows. Nothing plugged in that's why it seems strange!

Hawk · 08-29-2007, 02:26 PM

You're Joking, right? Unless you have your Bluetooth on and accidentally paired with something, there is no way a plastic wrap is going to cause that message.

*on a side note, I have the shield too, and I am sending my phone in tomorrow because of poor battery life. I checked the invisible shield's website and if I have to send the phone in, they say to remove the shield and send it back and they will send you a new one for your phone when it returns. It's part of the warranty. Schweet!*

sealevel · 08-29-2007, 02:30 PM

Quote:

Originally Posted by Hawk

You're Joking, right? Unless you have your Bluetooth on and accidentally paired with something, there is no way a plastic wrap is going to cause that message.

*on a side note, I have the shield too, and I am sending my phone in tomorrow because of poor battery life. I checked the invisible shield's website and if I have to send the phone in, they say to remove the shield and send it back and they will send you a new one for your phone when it returns. It's part of the warranty. Schweet!*

That's great. It's a good company. The only accessary other than that is Jawbone witch has always worked. It must be some other interference at the office. Only thing I can think of. Only coincidence that it happened at the same time the IS was applied.

RyanP · 08-29-2007, 02:56 PM

That is crazy that would happen! The other day I plugged mine into the dock that came with it and got that message (which was strange), but that was at least plugging it into something...it's strange it would happen just from a coating.

sealevel · 08-29-2007, 02:59 PM

I'm thinking it's got to be something else. Tonight I will un-pair the Jawbone and re-pair it and see if that corrects it. Thanks for the responses

sealevel · 08-30-2007, 08:11 PM

I restored the software and things are good again.

jlhollander · 02-10-2008, 05:40 PM

i just decided to take a stroll through memory lane and read through old posts, and i realized that the reason that your phone did that when you installed the invisible shield, is that some of the spray, or some particle in the air became trapped in the 30 pin receptor and caused two of the leads to connect, (might have been a small peice of metal) and the iphone didnt recognize it. One in a million occourance, but it happens. I had it happen to an old phone and it thought that it was charging all of the time, even when it wasnt. When you plugged your cable into the bottom of the phone, you moved whatever was touching and it fixed itself. The only problem is, is that it might still be in there, waiting to happen again, so you might want to clean out the port! Sorry for the multiple month delay, but i had not seen this post till now.

sealevel · 02-11-2008, 11:46 AM

Thanks for the heads up on that.