mrjeff
-
Posts
108 -
Joined
-
Last visited
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Everything posted by mrjeff
-
I installed android L but also had to revert back to 4.4.4. To many apps were not working but the worse was that Google maps kept freezing.
-
Hmm that's a bummer. I'm guessing that whatever issues people are having is related to their market. I've only seen my phone stay on 3g or 1x for at most 10 minutes before switching to LTE and the phone predictably will be on band 25 or 41 at the same locations every time. Sent from my Nexus 7 using Tapatalk
-
Have you flashed another ROM or are you running stock? Sent from my Nexus 7 using Tapatalk
-
I can't remember the last time I've seen EVDO. LA is a really large city tho.
-
Probably best to find and ask some of the Cyanogenmod developers who have worked on these issues in the past. Sent from my Nexus 5 using Tapatalk
-
My data has been really stable since the update and probably performing better than before. I don't have anything to compare to but I'm in a spark area and have been connecting to B41 pretty consistently. Sent from my Nexus 5 using Tapatalk
-
Yeah I just stepped out and got B41. 55 Mbps down. Not too bad.
-
Reading through this it seems nobody is getting B26/B41 on this radio. Perhaps the phone is not spark enabled yet.. Scatch that I connected to 41.
-
Does adjusting the priorities matter at all in terms of connecting to B41 and B26? Mine are all 1 1 1 right now.
-
Long pressing the power button will usually reset the device.
-
Lack of GPS lock makes me think there is something wrong with your phone. Does the G2 have GPS issues?
-
Not sure if it will interest anyone but here is the text of the linked FAQ from 2012. http://www.howardforums.com/archive/index.php/t-1772896.html
-
The article states that Sprint has started sending notices to their post-paid customers. Has anyone here received one?
-
I don't think 4.4.2 was pulled. 4.4.2 rolled out real quick after 4.4.1 however to fix an issue. The below article explains it better. http://www.androidpolice.com/2013/12/09/sprint-says-the-nexus-5-is-getting-an-update-to-kot49h-today-but-what-happened-to-kot49e/
-
Class action lawsuit is a bit too dramatic for me. As much as I'm hoping for the update, I'm in no way upset at Sprint or Google. I would have bought the phone either way.
-
Wishful thinking but I'm crossing my fingers that an update with a new build number is announced by Monday.
-
I'm still expecting the update before this month's end, just based on prior statements. Apparently the wearable SDK is going to be released/annouced/something in the next week or two so maybe the update will coincide with that.
-
This makes sense but I don't find this is always the case...at least not currently. One place I travel through in particular has really terrible LTE 1900 coverage for about a block but my phone remains connected to it despite that. When a call connects to CDMA1X 1900 in this spot I'll barely be able to hear the caller and will almost always have to hang up and try again.
-
Oh I didn't know calls would drop if you're switched to 800. This probably explains why no Sprint users that I know have really seen an improvement with 800. Pretty much everyone I know with sprint complains of dropped calls, and voice cutting in and out...hopefully Sprint is able to figure out a way to improve the experience. These issues weren't really issues until about 2 years ago so I'm guessing they are solvable but will just take time. Data is working better than ever tho.
-
I wonder if Sprint's network is able to detect when the voice is cutting in and out - if so they should switch you to 800. Otherwise I hope they are able to adjust the threshold of what a usable 1900 signal actually is. No point in connecting a phone call if I can only hear 50% of what the person says.
-
I tend to only to connect to 800 in places where I normally wouldn't have service. Like a parking garage or deep inside a building or something. I'm not connecting to 800 in places where I have a low signal or where the signal is barely usable with calls cutting in and out. It's still early and so I am hoping the user experience improves with time as it is currently less than what I expected.
-
On the Sprint site, the user said that Juni support told him that the repeaters are connected by fiber to either a base station or the closest tower. If this is true - I'd think the base station/tower could directly tell the repeater what signal to broadcast. Is it possible these these antenna's are all broadcasting there signals independently rather than just taking a weak signal and amplifying it and that the processing of data/calls is just done off site at the base station/tower that these are all connected to?
-
Working here too! I can also now set preferences on my account, block numbers, etc... About time! Maybe someone with connections to Sprint is reading this thread? Someone should try to activate a Tmobile Nexus again., maybe it'll work this time.
-
pictures can be found here: click me
-
FWIW, I got most my information from this currently unavailable sprint forum message (still on google cache tho). You can view it here. Some pictures of these guys are available in this thread here. They are spread out constantly through out the canyon on many of the turns.
