iphone 4s problem with airplay losing conection after few seconds ?????

Hey Phil from Clayfield,

Phil from Clayfield wrote:

OK here is what I found out today whilst testing this out for several hours. In a nutshell this problem appears to be problem with the 4S hardware.

I restored my old iPhone 4 running IOS 5.0.1 and this combination of hardware and software worked as expected for several hours this afternoon without any issues. I left the house for 15 minutes and was able to recommence playing music through my Zeppelin Air without a hitch upon my return.

Swapped over to my 4S running IOS 5.0.1 and it wouldn't play through the speaker even though it said it was connected and playing but there was no sound coming through the Zeppelin. I have managed to connect the 4S to the Zeppelin a few times but I have needed to restart my router, the Zeppelin Air and the 4S and then it wasn't guaranteed to work but I have had some success, if you can call that a success?

Not sure if the issue is with the processor in the 4S but it definetly appears to be a harware issue, hopefully Apple can get to the bottom of this and fix the issue with a firmware update if not then we could possibly be seeing a recall of the 4S to rectify the hardware at fault.

Thanks for your diagnosis. I am in exactly the same situation. So relieved to finally understand what the problem is. iPhone 4 for AirPlay it is lol (until a 4S update).

All the best for the holidays.

Richard from Brisbane

Just bought a new Router (FritzBox 3370) but still the same problem. Waiting for iOS 5.1 and if it will not work with iOS 5.1 I will return the iPhone 4S and the Zeppelin Air.

Well so far I want to chuck my iPhone 4S 64GB back at apple and shout 'Give me my money back!'

No end of issues with my ISP's router and you guessed it, its a Netgear. Well to be exact a Netgear DGN1000.

I dont see why I should have to buy another router to get this hunk of crap phone to play nice, are Apple just sitting on their butts on this issue? I basically can't use my phone on the network at home without it downing the router and all connected in the process.

From what I can see there is a ton of Netgear routers affected and the one I have is a major model deployed by Viriginmedia in the UK so its a fairly common model that a lot of people will have.

Please Apple get it sorted or give me another router/money for one because as far as I can see your phones got issues 😟

Haven't had any issues with my netgear router with normal connections to either my iphone 4s or pad 2 or macbookmair to my netgear router supplied by Virgin Media.

What exact model of router is it though? Not every Netgear router is effected, just a bucket load from the support sites I've checked. My router is for Virgins national BB service and not the cable services which is another router.

Ok, I've tested 4S to Zeppelin Air streaming on three separate routers:

Netgear WNR2000 - drop out in less than 30 seconds

Thompson Gateway - drop out in less than 3 minutes

Asus RT-N56U - drop out in 40-120 minutes

When I connected Zeppelin Air to Netgear WNR200 via LAN there was no drop out

No drop out with iPhone 4 and MacBook Pro on all three routers

No drop out with iPhone 4, iPhone 4S and MacBook Pro on all three routers streaming to AppleTV

So there's my findings guys. Hope it helps out.

I had exactly the same problems with my 4s and my new Zeppelin. After reading this thread I've upgraded my iPhone to 5.1 beta2 and it seems that the problem is solved (tried it 4 hours yesterday -> no hiccups. It worked like it should). My setup: iPhone 4s (5.1 beta2), Airport Extreme (7.6), Zeppelin Air (1.1.3). I'm really hoping that 5.1 solved the problem. I'll keep you informed.

How do we get 5.1 beta2 to try it out ? Is it only available to Apple developers or something? My phone is on 5.0.1 and says it is up to date.

Anyone thinking of going to airport express as a streaming alternative should bear in mind that airport express also have streaming issues as well occasionally dropping the connection and becoming unavailble. That said they are much less severe errors than those with iPhone 4s wireless networking which is much more frequent and requires the speaker to be re started.

I have airport express and the issue has been the same since I've had the iPhone 4s. This also doesn't seem to stream FaceTime and other apps which use a wireless network with signals dropping/cutting out.

I'm surprised this problem hasn't been resolved yet, I posted a thread 2 months ago when only a few people were experiancing this issue, now it's becoming alot more recognised apple still haven't found a fix. Quite poor!

someone thought about doing an

class action (Federal Rules of Civil Procedure, Title 28 United States Code Appendix Rule 23).

it´s an important missing feature of the iphone 4s over month now !

I've got a developer Account so i can already use the beta. I guess for non-devs there is no legal way testing the beta. As i wanted to keep you informed: i was streaming for six our this morning -> no problems. Had to recharge the phone an it's already streaming for 1 hour without any hiccups.

Thank you. That is really useful information. There is a ray of hope.

Just received an email from B and W North America. It says what Disneyland_East said. I'll copy it here:

We have identified an issue with the Zeppelin Air and iPhone 4S when trying to use AirPlay. I am pleased to say that the iPhone 4S Airplay streaming issue is now solved.

We have checked the iPhone 4S streaming with the latest iOS5.1 beta2 over a few days, and on different wifi environments.

It streamed audio to the Zeppelin Air for more than 24 hours, and the previous encountered issue (Zeppelin crashes) is fixed. The next step is to wait for Apple to issue an official release of iOS5.1

I guess I have something to look forward to in 5.1. I tried using an airport without an Internet connection and my issues are persisting. Incidentally I was able to get the amber light to quit blinking by using the airport utility app on my iPhone and telling it to ignore the problems it detected.

I can confirm that 5.1 beta 2 does seem to fix the problem.

It's now streaming for 3 hours.

Horray !