EvanA
-
Posts
1,775 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Everything posted by EvanA
-
Yeah I understand that, but my point is that I'm seeing less of 1xRTT and more of 1x800 almost all of the time despite being in a location where 1x800 is unnecessary. EDIT: I just tested with a phone call from LTE and it fell back to 1xRTT despite it picking up 1x800 if I switch to 2G/3G mode.
-
I am in an area with a lot of 1x800 deployed and my Nexus 5 always seems to jump on 800 when it falls off of LTE (B25). It seems like the network has started prioritizing 800MHz because this didn't really happen until recently. Does anyone else experience this?
-
It's an android bug. If you toggle wifi hotspot you can avoid having to reboot the phone. Sent from my Nexus 5 using Tapatalk
-
CSFB is an issue for upgraded towers, not old ones. I am almost certain you're seeing eCSFB issues. How long have you experienced this issue? Sent from my Nexus 7 using Tapatalk
-
There might be CSFB issues in your area, which is why the N5 won't connect. If you are on B25 there won't be anything extra to indicate that. Sent from my Nexus 7 using Tapatalk
-
Signal check should tell you the band by adding B41 or B26 after the sprint designation. Sent from my Nexus 7 using Tapatalk
-
The reason why there is a long delay sometimes is the scan time for LTE being set to 30 min intervals (at least on sprint). This means that the phone is only going to look for LTE every 30 minutes. I have a feeling this will be shortened in the future once sprint has more widespread LTE coverage. Sent from my Nexus 7 using Tapatalk
-
I'm inclined to believe your statements but you haven't given any proof of a reliable source so it makes me skeptical. Sent from my Nexus 7 using Tapatalk
-
Please, tell me how you would do it faster and better than full time experienced software engineers. Also, the modem software is most likely handled by LG/Qualcomm engineers, not Google. Sent from my Nexus 7 using Tapatalk
-
The problem is unexpected setbacks, especially when having to make sure the changes for spark don't negatively impact operation on other carriers. It's difficult for software developers to meet an ETA sometimes. Sent from my Nexus 7 using Tapatalk
-
I don't know where you guys are getting that the phone is advertised as supporting spark. The sprint webpage states "SprintSpark™ (Support coming soon, via update)". It doesn't say it currently has spark. Also, nothing was promised by the end of the first quarter. Sent from my Nexus 7 using Tapatalk
-
Doubt it. The build number on the sprint site matches with the leaks of 4.4.3 builds. Sent from my Nexus 7 using Tapatalk
-
It was listed in the leaked changelog. Nobody has received the update so no way to say for sure. Sent from my Nexus 7 using Tapatalk
-
T-Mobile doesn't want out, their parent company Deutsch Telecom wants out and need a buyer. In regards to the announcement, why not get rid of overage fees by offering unlimited data at a reasonable price? That seems like the smart move to attract customers with. Sent from my Nexus 5 using Tapatalk
-
No this is 4.4.3 as evidenced by the build number being the same as the one from earlier leaks. Sprint just put up the announcement early. Also, sprint has no control over updates for the Nexus 5. Only Google can push updates. Sent from my Nexus 5 using Tapatalk
-
Is HD Voice now on? Mine appears to be working
EvanA replied to Sim-X's topic in Network, Network Vision/LTE Deployment
Does anyone have a definitive answer on whether HD voice works with Google voice? I saw some talk about it a few pages back but there wasn't a solid conclusion. EDIT: According to this support page https://support.google.com/voice/answer/115119?hl=en it shouldn't affect quality but I'll have to do some testing and see if that is the case. Sent from my Nexus 7 using Tapatalk -
Who's to say you didn't make up the e-mail? Especially considering the spark icon comment. There's no way google would add a carrier specific modification to stock android. Sent from my Nexus 5 using Tapatalk
-
SMS/MMS is handled over LTE so that's not related to CSFB issues. It doesn't sound like CSFB issues because the phone wouldn't be connecting to LTE at all if that were the case. This seems to just be a problem with the tower or defective device. Sent from my Nexus 7 using Tapatalk
-
I can agree with the first paragraph. This is what really causes the difference, not anything system level. As far as the system is concerned 5th day of usage = 1st day of usage. The environment will always be the most important factor no matter how long you've have the device. Sent from my Nexus 7 using Tapatalk
-
Android doesn't do this. Sync occurs on a regular interval. Nothing is "tuned" to your usage. Sent from my Nexus 7 using Tapatalk
-
This is BS. Android is software. There is no "settle" time when you update because it's all electronic bits and bytes. You'll notice any differences within the first day and after that not much will change. Your usage habits affect the battery life more than any other factor.. Sent from my Nexus 7 using Tapatalk
-
Everyone needs to chill and stop worrying about the spark update. We already know it is coming. Furthermore, Google knows what they are doing and they do talk to Sprint because otherwise there would be no sprint nexus 5. Sent from my Nexus 5 using Tapatalk
-
It could be, but with CSFB issues the tower should kick you off on LTE. Does anyone else in your area have issues making of receiving calls? Sent from my Nexus 5 using Tapatalk
-
Google is definitely going to do a point update, most likely 4.4.3. For a major device like the Nexus 5 it doesn't make sense to roll out an update that only affects one carrier. Sent from my Nexus 5 using Tapatalk
-
I had to reboot mine before it updated the time as well. Sent from my Nexus 5 using Tapatalk
