AT&T Note 3: Soooo ummmm still waiting for 4.4.2

[skyrocketeer]

Re: Soooo ummmm still waiting for 4.4.2

Aside from the minor issues with 4.3 I'm not sure why some are so anxious to update? I know kit kat is supposed to improve performance.. But I never notice lag or wish my Note 3 was faster. Perhaps it's just me? I kind of like the green battery icon on the status bar.

Sent from my SAMSUNG-SM-N900A using Tapatalk

Ya this is a consistent thread on every phone I have had. " When is XYZ going to get the new twinkie update????" I'm with you...I am loving the note 3 with JB...it is very stable. As soon as the update comes out , we will get flooded with "How do I UNDO the update and go back....." posts.

 

[daviddlt]

Until some of my favorite apps stop working on 4.3 I'm not updating.

Sent from my SAMSUNG-SM-N900A using Tapatalk

 

[acostapimps]

They just hear the word kit kat and people immediately think the world of possibilities, then when issue arise they'll say, I should of stayed on JB 4.3, Just like with every fresh new update. The same happened with updating to ICS from GB.

Sent from my SAMSUNG-SGH-I317 using Tapatalk

 

[DCBamBam]

+1

Posted via Android Central App

 

[Matt Behnken]

The GPS dropping issue is probably being rolled in with the 4.2 update. That means more testing. It's only the att note 3s that are affected so they don't want to rush this and screw it up.

Posted via Android Central App

 

[NoTe3]

So talked with AT&T this morning.. Only info they would give me is that the update was 800mb..

Posted via Android Central App

 

[Reggie]

So what are the advantages of Kit Kat? To be honest I have stopped following the updates as the OS out now seem to be pretty good and the improvement are minor.

 

[Gary02468]

The GPS dropping issue is probably being rolled in with the 4.2 update. That means more testing. It's only the att note 3s that are affected so they don't want to rush this and screw it up.

"Rush"? The folks on xda-developers developed and posted a fix for the AT&T N3's GPS bug months ago.

I'm not confident 4.4.2 will even address the issue. But we'll see.