[windev]

That's great news although I've never really experienced that problem.

[rockstarzzz]

If I don't get 1314, I am getting an iPhone 5. Enough is enough!

Meh, who am I kidding! My Pikachu isn't going anywhere! ;)

[windev]

If I don't get 1314, I am getting an iPhone 5. Enough is enough!

Meh, who am I kidding! My Pikachu isn't going anywhere! ;)

Isn't the 1314 for AT&T branded phones only?

[rockstarzzz]

Isn't the 1314 for AT&T branded phones only?

It shouldn't have been though. The connectivity issues are there for non-AT&T bunch. Oh well, I will just buy an iPhone 5 (not!)

[justop26]

That's great news although I've never really experienced that problem.

It was annoying. Having full bars and having to figure out why, oh why did my pone didn't receive any WA messages, e-mails, etc.

TBH, an iPhone 4S and a Galaxy phone lose data connections, too. So it must have been a combo of poor network + phone issues?

Not happening anymore, that's the important part anyway :)

[zokstar]

It shouldn't have been though. The connectivity issues are there for non-AT&T bunch

I agree! Ive got a unlocked handset from clove and im in Australia. I struggle to get 4G at all now with 1308 :(

[FBirraque]

Yesterday I got 1308 with "configuration id" 146999 on my L920 CV GB (GLOBAL) and I believe that LTE had been enable now.

[BIGPADDY]

I got the config ID 146999 as well I'm part of something.

[muvig]

GOT 1308 Friday, no issues, battery improved, i have this application (Battery) which warns me if the battery is draining quickly, now its silent after this update.

[IceCrush]

Had the update yesterday, after testing .. Proximity sensor dust issue completely fixed and don't ask me how, dust is there and i can see it clearly on the FFC but the sensor just works!!

[windev]

Proximity sensor has been fixed on mine since the last update as well.

[MDak280]

Yeah, before the update the proximity sensor used to work on and off; sometimes it did and sometimes it didn't. Now it works all the time!

However, I think my battery has gotten worse. It might be too soon to tell but that's the impression I got after a couple of days.

[robnewton]

Yeah, before the update the proximity sensor used to work on and off; sometimes it did and sometimes it didn't. Now it works all the time!

However, I think my battery has gotten worse. It might be too soon to tell but that's the impression I got after a couple of days.

Gotta agree about battery life. My phone comes off charge about 7am & will last until about 11-12pm under my normal usage. Since the update I'm struggling to make it home from work about 5pm without running out of battery. I'm hoping it'll settle down before long & get back to normal.

[rockstarzzz]

Anyone on EE, find themselves suffering from tunnel syndrome? Somewhere between the call, person on the other side feels like you are shouting from a tunnel far far away? It seems that happens when we have 3G+ full bars! - same as not having internet when we have full 3G+ signal. I think phone loses signal and becomes terrible in connectivity and the logo doesn't change. So call quality becomes really poor for about 45-50 seconds in the call and then goes back to normal and keeps doing that the longer you talk! Tried and tested a few times in last couple of days.

[MF73]

I'm on EE and had to change my phone, kept getting people telling me they could not hear me, despite holding the phone next to my mouth, it was a known problem. Your problem sounds very similar.

[rockstarzzz]

I'm on EE and had to change my phone, kept getting people telling me they could not hear me, despite holding the phone next to my mouth, it was a known problem. Your problem sounds very similar.

Was this after or before update? My phone was totally fine till 1308 update! Now I have 2 of my Lumias on 1308 and the other two still on 1249. Both on 1308 magically developed "I can't hear you" issue!

[MF73]

It was before, back in January. Quite a few people at the time were having the same issue, there are a few threads on it. I believe in my case it was a hardware issue, so may be different than your problem if yours is software related. Do you get the same problem when using Bluetooth? Mine was fine then, only occurred when using the phone direct.