Yuhfhrh
-
Posts
770 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Posts posted by Yuhfhrh
-
-
I know I'm beating a dead horse here, but take a look at Sprint's coverage map for the same area as above:
In nearly all the 0.50mbps areas on sensorly where B26 signal averages -115dbm to -125dbm(No Signal), Sprint shows Spark coverage available. In fact, Sprint is showing Spark coverage in some areas where 1X doesn't even reach.
Maybe Sprint hasn't bothered to properly cover the area, because they already think they do!
- 3
-
Going back to the original topic, I just saw what OP was referring to in the ever expanding subdivisions of greater Houston. Katy, TX has been growing at a rapid pace since the 90s and it doesn't seem to be slowing down anytime soon. If it wasn't for 1x 800, the entire area would have no native Sprint coverage. No LTE on most of my drive in that area and any scent of EVDO my phone caught was useless. If I had to guess, that area is serviced by one tower with no down tilt and with the new subdivisions, it is suffering from massive congestion. I'm sure this is a problem for all providers at the moment in that area.
I'm visiting the Katy area right now, and I have made my way around to most of the sites. I opened sensorly, and was suprised by the amount of activity in Katy/southern Katy.
These are rough locations, but blue stars are some Sprint sites, and purple stars are some Verizon/At&t only sites. Its funny to see the patches of thick green where B41 is available, and then all the red where there seems to be only fringe B26.
I would be surprised if Sprint didn't have any plans to expand where the duopoly already has. If these sensorly maps have any weight, there seems to be more traffic in the Katy area than in central Houston itself.
-
In my various wanderings throughout S4GRU, I have seen one, maybe two, WiWavelentgh "likes." I believe one may be lurking in the Really Bad Joke thread, but I may be mis-remembering.
AJ's "likes" are out there, but are very few and far between.
Here are two quality WiWavelength likes:
- 3
-
Well at least I haven't seen the "won't be able to penetrate a paper bag" comment...yet.
"Probably won't be able to penetrate a paper bag
That's for you @wiwavelength @s4gru" -maximus1901- 5
-
and not everyone wants to root their phone.
I would argue the vast majority of people who would even consider this, would rather root their phone than visit the Sprint website every day, add and remove the hotspot service, and pay ~$20/month.
Regardless, this should be fixed. When changing services, total hotspot usage should carry over. If you use 1GB and change to 2GB, it should show 1GB/2GB already used.
-
Probably should be addressed if possible. I could see this work around being abused and probably already is being abused.
I doubt many people would be abusing this, seeing it has an additional cost compared to using a free hotspot through a rooted phone.
-
So do they prorate the charges but not the data? One could activate it, use the 2GB and deactivate and only pay the proration?
Yes, it still works this way as of last week. You can get a fresh 2GB every day if you wait a couple hours in-between adding and removing the service, or alternatively flip between the 1GB/2GB/6GB option daily.
-
WiFi calling was working fine on my new GS5, then yesterday, it failed with connection errors. This has been reported by other members in the GS5 thread. Have other members with different phones experienced the same problem in the past 2 days??
This is happening today on my GS5. Worked 100% solid up until today. Now it has a connection error.
-
The question is, how is Dkoellerwx getting it normally....?
It sounds like Dkoellerwx is integrated with his Sprint number, and david279 is using his Google voice number.
If someone sends an MMS to your google voice number from Sprint or T-mobile, it will be forwarded to your gmail. If they send an MMS to your GV number from At&t or Verizon, it will never come to you.
If you use your Sprint number with Google voice, MMS behaves normally.
-
I wonder if it actually was rolled out? I haven't spoken to anybody that's received the update yet.
Sent from my SM-G900P using Tapatalk
It's still not available on Kies.
- 1
-
What was the Verizon LTE handset penetration rate 2 years in to their LTE deployment?
Sent from Josh's iPhone 5S using Tapatalk 2
I don't know, but they only had 5% after 1 year.
-
Wonder if this will be the Wi-Fi calling update? I'd like to see the s5 get Wi-Fi.
Sent from my SM-G900P using Tapatalk
This is in fact, the WiFi calling update.
-
Has anyone had any luck yet with HD voice while using Google Voice integration?
I haven't had any HD calls on my GV integrated line. (Galaxy Note 3)
On another line without GV, I do get HD calls. (Galaxy S4, Nexus 5)
I don't know if my experience is the norm though.
-
Any ideas why I'm not seeing a 1x800 signal worse than -104 in my market? It's as if that's the cutoff level. I have usable LTE down to -115 to -120 all the time....
From my experience 1x will not work at -107 or less. So that is about the cut off level.
-
The good thing about it is that it gets you simultaneous voice and data.
Sent from my SPH-L720T using Tapatalk
Well, the same can be accomplished using WiFi and 1x...
-
Just enable GV integration, then you can continue to send/receive text messages with your sprint number on wifi with the Google Voice app.
-
I get what you're saying. Since T-Mobile is GSM-based, in theory Google "shouldn't" need them to approve updates. This would be entirely true if T-Mobile didn't also sell the LG Nexus 5. Since T-Mobile does sell it, it does get a say in updates because T-Mobile has an obligation to ensure the phones it sells continue to work on its network and adheres to its own policies. Take for example AT&T, it never sold the LG Nexus 5, therefore it has no say in its updates. Just because a phone is GSM-based, it doesn't mean no carrier can interfere with updates.
My original point was if the carriers are giving Google problems, that is not a reason to end the nexus program. They could go back to play store only.
-
As can Sprint customers. I'm not seeing any distinction here.
Because Sprint doesn't allow phones on its network unless they have been white listed, they are the only carrier that Google would ever have to "make happy"
-
T-Mobile sells (or at least sold) the North American model of the Nexus 5, as do several Canadian carriers. So Sprint isn't the only carrier Google/LG needs to make happy.
But Google doesn't need T-Mobile nor the Canadian carriers to sell it. They can all just buy it from the play store.
-
The article says VoLTE will support handoffs to HSPA+ and Edge. Is there also a way for handoffs to 1x?
-
I wonder of pain gettiing the 5 acceptable to all the carriers is part of the reason they are rumored to be dropping the Nexus line for Silver models that I think are carrier specific.
Sent from Nexus 5
If they are making it acceptable to At&t and T-Mobile, that is Google's own decision. Sprint would be the only carrier Google would have to please, as At&t and T-Mobile won't do much about an unlocked device.
- 1
-
Interesting tidbit from that page:
"For a customer to make or receive a VoLTE call, both parties must have VoLTE-enabled devices and be in an area where VoLTE is available."
It kind of sounds like Verizon is making a type of their own Skype/Google hangouts. Doesn't really seem like what I thought VoLTE would be.
-
Spark Network
-
I think we're approaching ludicrous speed in this big phallus wireless challenge. I'd love to have 150Mbps on my home wired internet connection... but out and about, I'd be satisfied with a consistent 10-50Mbps with a low ping time -- there's nothing that I would do on a phone or tablet that would require 150Mbps...
But there are plenty of things 15 people would like to be able to do at 10mbps simultaneously.
- 5
Sprint LTE Coverage Maps via Sensorly
in Network, Network Vision/LTE Deployment
Posted
Here's a full screen snapshot of Sprint LTE I whipped up. (7-31-14)
I wish Sensorly had options to zoom out more.