That be be true with non nexus devices, but it's my understanding that Google has final say on what gets pushed to nexus devices.
Sent from my Nexus 5 using Tapatalk
So I think I'm in the camp that Google is waiting for the next release of android to give us spark. To me, it would be foolish to mess around with 4.4.x this close to the speculated next release.
Sent from my Nexus 5 using Tapatalk
Still ongoing. I am also getting brief, but unusable LTE signals. I drove by the site near montgomery/eubank and could not pull a signal from it and there was no work truck there.
No we haven't yet. Idaho Falls is still on the table, but so are Sandia, Los Alamos, D.C., and another job in S.C.. Big decisions to make here soon.
Sent from my Nexus 5 using Tapatalk
We don't know that spark is the reason for the hold up. I would bet that it isn't and that some other bug is holding up the update, the planned delivery method for spark.
Sent from my Nexus 5 using Tapatalk
Now where would Ting get information than Sprint has? I'm not disagreeing with you it just seems strange that Sprint would post incorrect information, or if it was correct but Google pulled the update, that Ting would have this new information so quickly.
I think it's too early to know if that will happen. As you may know, there have been a few radio variants for the n5. Each seems to perform differently with holding into an lte connection. Let's hope the new radio will work well across the board.
Sent from my Nexus 5 using Tapatalk