Jump to content

Recommended Posts

  • Replies 9.8k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I had a Sprint product development employee reach out to me this morning after reading this thread. His message says:   Robert via Samsung Note 8.0 using Tapatalk Pro

I am now the proud owner of a Nexus 5!       Sent from Josh's iPhone 5 using Tapatalk 2

Mine just arrived!!!  

Posted Images

Speaking for my devices, the problem is independent of the default messaging app. I mainly use Android Messages and Textra. In fact I reloaded the last factory image and used it stock to prove it wasn't any app or update.

Sent from my BBB100-3 using Tapatalk

  • Like 1
Link to post
Share on other sites

I had my Nexus 5 activated a couple of weeks ago while LG had my phone for repair and I didn't notice any SMS or MMS problems.

Sent from my LG-LS993 using Tapatalk

  • Like 1
Link to post
Share on other sites
I had my Nexus 5 activated a couple of weeks ago while LG had my phone for repair and I didn't notice any SMS or MMS problems.

 

Sent from my LG-LS993 using Tapatalk

 

 

Glad to hear something recent. Is yours a "Sprint" model (yes I realize they're technically all the same) or a Google Play model? There shouldn't be a difference, but I'm doing what I can to narrow it down.

 

Sent from my BBB100-3 using Tapatalk

 

 

 

Link to post
Share on other sites
Glad to hear something recent. Is yours a "Sprint" model (yes I realize they're technically all the same) or a Google Play model? There shouldn't be a difference, but I'm doing what I can to narrow it down.
 
Sent from my BBB100-3 using Tapatalk
 
 
 
Yes. It was purchased from Best Buy with a Sprint Sim preinstalled in the box.

Sent from my LG-LS993 using Tapatalk

  • Like 1
Link to post
Share on other sites

Thanks. I flashed one of mine with the last Lollipop build, since I've already tested both of them on Marshmallow and had problems. Maybe reflashing the modem will do it good. :/

Sent from my BBB100-3 using Tapatalk

Link to post
Share on other sites

I'm probably going to jinx it by posting this.. been on the N5 with Lollipop for about 36 hrs without experiencing SMS or MMS issues. Knock on wood... [emoji267]

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to post
Share on other sites
Quote

I'm probably going to jinx it by posting this.. been on the N5 with Lollipop for about 36 hrs without experiencing SMS or MMS issues. Knock on wood... emoji267.png

Please keep us updated. I don't mind restarting every now and then but honestly it always seems like "updates" always have more bugs then the phone did brand new. That's one of my frustrations about getting an update. It never seems to go through as much QA as they did for the initial release.

 

I picked up the G6 with the best buy deal but switched back because I didn't have a case or tempered glass protectors for the front screen and rear camera and didn't want to get any scratches.

 

The Nexus 5 is good enough for me. it has all the Sprint Bands and if someone is a small data user like myself where CA doesn't have any additional benefit then I don't see the advantage of switching from the 5 for now.

 

-J

Link to post
Share on other sites

Approaching three full days without issues. I activated it Tuesday evening. I'm going to keep going as long as it keeps working.

Sent from my Nexus 5 using Tapatalk

  • Like 2
Link to post
Share on other sites

It has now been a few hours short of one week with no issues. Considering I'd never gone more than 24 hours before, I'm calling it a success. Going to update to 6.0.1 and see what happens.

Sent from my BBB100-3 using Tapatalk

  • Like 1
Link to post
Share on other sites

About 24 hours on 6.0.1 and I just started having issues. Updating profile in network settings fixed for now... Same old same old. I wonder if it broke immediately on 6.0.1 it if one of the monthly updates did it..

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites
Thanks again for the update. I haven't had a bad text for about 10 days or so.  

I'm still behind on updates. Currently on the Oct 5, 2016 update. (Yes I know)

 

That IS the last update unfortunately. Well, I had two updates that were both marked Oct 5, 2016..maybe you're still on the first one?

Sent from my Nexus 5 using Tapatalk

 

 

 

 

 

Link to post
Share on other sites
Oh, I don't normally install updates and since it was a few years old I just figured it was way outdated - my bad.

No problem. I am rolling back to 5.1.1 and restoring the backup I made yesterday. I may try the 6.0.1 update with no monthlies, or just stay on 5 for a while.. It has been working fine for me.

Sent from my BBB100-3 using Tapatalk

Link to post
Share on other sites

I inadvertently bought a 16GB N5 last week that, as far as I know, has only been used on Sprint. I had the same experience with it - SMS and MMS worked fine on 5.1.1 but broke as soon as I updated it to 6.0.1. I explored one more possibility, by flashing the baseband from 5.1.1 over the 6.0.1 version. At first it seemed promising, but after switching back to my main N5 and doing the same thing, I still had issues with SMS and MMS, almost immediately. I cleared the cache partition last night and so far today it has been fine, but I'm not confident. If it happens again, I'll restore my 5.1.1 backup again and give up on 6.0.1. Slightly more out of date doesn't seem any worse off than just out of date. :/

 

Sent from my Nexus 5 using Tapatalk

 

 

 

 

  • Like 1
Link to post
Share on other sites
  • 3 weeks later...

I just looked at my Nexus 5 and realized it's been running for 550 hours (about 23 days) not a text issue at all in this time.

 

Not saying the problems or issues are gone just mostly just an FYI. (although it sounded like you put your Nexus 5 to other uses based another one of your posts)

  • Love 1
Link to post
Share on other sites
7 hours ago, sleet said:

I just looked at my Nexus 5 and realized it's been running for 550 hours (about 23 days) not a text issue at all in this time.

 

Not saying the problems or issues are gone just mostly just an FYI. (although it sounded like you put your Nexus 5 to other uses based another one of your posts)

And you're running 6.0.1?  Wow.  For me, the problems start almost immediately after updating from 5.1.1 to 6.0.1 - usually within an hour or two, but always within a day.  I had one hiccup on 5.1.1, but the phone was acting a little odd at the time, so I wrote that one off as a coincidence. I'm actually swapping back now to do some other testing with Ubuntu Touch, which I expect will fail too. :)

Link to post
Share on other sites

Yes I'm running 6.0.1

 

Some days I text a bit and other days not much.

 

When it finally decided to have the glitch I'll try to remember to post an update with hour long it went.

 

One thing I have been doing is keeping my data off. I turn it on if someone is going to text me a pic or if I'm going to send one but I just try to keep my data usage to a minimum.

Link to post
Share on other sites

Makes me wonder if I let it sit, if it would ever start working again on its own. I can't risk that on my line though, so I doubt I'll ever test it.

Sent from my BBB100-3 using Tapatalk

Link to post
Share on other sites
  • 1 month later...

Well my phone just died about an hour ago. I couldn't get it to restart. It tried holding the power button and all the usual tricks. It had changed overnight and was probably around ~70% battery so I know it wasn't a dead battery. Before it died I had pulled it out and sent a text and then left it on the desk. came back an hour later and it was dead.

I put it back on the wireless charger for a bit - nothing.

Then plugged it into the usb port on the computer (I had previously enabled USB debugging)- still nothing.

I was getting pretty worried and finally started looking up dead nexus 5 online.

I had gotten the boot loop issue a couple years back but heard the power switch gets defected and had pulled the phone apart and replaced the switch and things have been just fine for years so I was doubting it could be that. Plus I wasn't boot looping anyway - it was dead.

I did some reading online and someone suggested holding volume up and down and the power button. I did that and got a short vibrate.

After that a little while later I tried the power button line normal (it still wasn't showing any charging screen or anything as it was still plugged into the USB at this time) and it actually fired up.

Everything appears normal not.

I have no idea how long it was running but interpolating it from my previous post and being a little cautions as I'm not sure the exact time of day I posted etc. I'm guessing I had at least 1,318 hours on it since the last restart.

Still no bad texts or anything else. I'll keep my fingers crossed that it was just a random bug from being on so long.

 

But meanwhile I' have been daily checking to see if the LG G6's go on sale again at best buy as the two I picked up I gave to family so I'd still like to get another one for me. but I figured I'd at least the status regarding the Nexus 5  from my previous posts

Link to post
Share on other sites

I sold one of mine, then accidentally bought another one. :/ I can still only use 5.1.1 on Sprint if I want SMS to work reliably, which sucks, but I love switching to it once in a while. It's just the perfect size for me. And frankly, it's faster than my KEYone.

Sent from my Nexus 5 using Tapatalk

Link to post
Share on other sites
  • S4GRU changed the title to Google Nexus 5 by LG Users Thread!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

    • By danlodish345
      Even though Sprint doesn't have the best coverage in my area. I do have lots of memories and nostalgia with the company. I wonder who else here will miss Sprint besides me?
    • By nexgencpu
      First Pixel device im somewhat excited about in a quite a while..
       
    • By vanko987
      I'm new to this forum, and I've seen people mention cell sites with specific ID's (for example, SF33XC664). Is there any significance to these ID's, and is there a way to decode them? Also, how do I figure out what the cell site ID's are for towers near me?
      Thanks! I'm excited to start talking on this site more 😀
    • By lilotimz
      Samsung Network Vision equipment are highly distinct and fairly easy to spot compared to the equipment that other vendors are deploying. Sprint is Samsung's first extremely massive American contract (baring Clearwire) so there  should be no issues in confusing these equipment for another carrier which happens often with Ericsson NV equipment.

      Below are images of Samsung equipment which includes antennas, remote radio units, base stations, and their mounting configurations. 
       
      Samsung antenna with eSMR 800 RRU & PCS 1900 RRU

      A close look at a Samsung setup





      Next Generation Samsung Configuration
      RRH-P4 4T4R 1.9 GHz  | RRH-C4 4T4R 800 MHz| RRH-V3 2.5 GHz

      Next Generation 8 Port Dual Band Antenna Setup 
      4 port 800 MHz RRH-C4 800

      (source: dkyeager)

      (source: dkyeager)
      Narrow beam setup

      High Capacity Site with 2 Antennas & 3 RRUs (2x PCS & 1x SMR).
      Second antenna is PCS only for now.


      Canadian IBEZ (NO SMR)

      Special Case PCS Only Setup for Canadian IBEZ




      Close up of standard antenna connectors 

      Samsung Cabinets

       
       
      Powerpoint slides from Samsung / Sprint
      *disclaimer - all  powerpoint diagrams and images were found through public municipality online databases and is by no means misappropriated through malicious means*
      *Credit goes to those whom took pictures of these equipment. You know who you are*
  • Posts

    • I may have missed it, but what are the the benefits of moving over to TNX on a 5G device that would automatically have TNA (prefer the T-Mobile network). It doesn't seem like it would change the network experience all that much. My devices are all TNA, and on the T-Mobile network all the time except while near Sprint Keep sites. I'd prefer to keep the easy access to Sprint sites since Sprint have a bigger network than T-Mobile here.
    • Has anyone on eSIM switched to T-Mobile eSIM?
    • Unfortunately, I'm seeing the gaps in the customer experience for TNX and I'm wondering if I should just leave the "T-Mobile Unlimited Freedom Plan with Included Taxes/Fees" behind and bring everything over to a T-Mobile Plan/Account at a certain point for usability and management sake. iOS: The experience on iOS has been fine. When I upgraded my 3 iPhone 12 Pro's it was easy to update the E911 Address for Wi-Fi Calling right on the device. Quick and done. Google Pixel 5: The experience on a Google Pixel 5 on eSIM for Sprint was mediocre. I received conflicting information about whether the device was eligible for TNX. Chat said yes, so I ordered a SIM and installed it. The device threw an error and said to take it out. Chat then said that device wasn't eligible for TNX. Is this in fact the case? Has anyone here put a Google Pixel 5 on TNX? Samsung: The experience for two Samsung Galaxies on our account was actually terrible. For the S20+ 5G: I put in the TNX SIM and after I enabled Wi-Fi Calling, I wanted to update the E911 address on the device. Nope, the address update button in the device menu took me to the T-Mobile Login Screen. I contacted chat and they said I had to do it on the Sprint website. Ok, so I went to the Sprint Website and to Account Dashboard. I selected "Options" for the device, and selected the Update E911 Address link. I then got taken to an absolutely ancient portion of the Sprint website that hadn't been part of the recent redesign and I was able to update the address.... but the interface looked terrible and like it wouldn't actually work. I still can't update the E911 address on the device itself. Ridiculous. For the S21 5G, which was a device upgrade on that line from an absolutely ancient BlackBerry KEYone (Don't ask. They held on forever hoping keyboards would come back): After activating the device with the T-Mobile SIM Card that came with it, I went to activate Wi-Fi Calling on the device. I then went to update the E911 address on the device and the button took me to the same T-Mobile Login page as it did on the S20+. So I went to my Account Dashboard and it showed the S21 on the line and that it was on the T-Mobile network. It showed that Wi-Fi Calling was enabled under account services. I then went to Manage Device -> Options -> Update E911 Address for WiFi Calling, and the ancient content page loaded.... and it still showed the old device on the account. I contacted Customer Care via Chat and they removed the old device from the account and it then showed the S21 on the page. I then tried entering the address for WiFi Calling and it wouldn't accept it. When I hit "save" it threw an error for the address, which makes no sense since this was the valid shipping address for the device via UPS. So I put in a ticket with the Advanced Tech Support to have the Network Team go and manually try to enter the address on the backend or figure out what's going on here. C'mon T-Mobile..... TNX is good. The customer experience for account services management you're having Sprint run on the Sprint website actually stinks, and we're starting to see the cracks where Sprint's legacy content that was never updated (and probably never will be) or that customers get misinformation about device eligibility for TNX (Google Pixel 5) can negatively affect the TNX customer experience. In my case, I'm having a miserable time trying to update the E911 Addresses for Wi-Fi Calling on my Samsung devices and its because TNX broke Sprint's E911 Address management on Android devices. iOS devices however seem to work fine for these updates to be made on the device. Not sure why that is. Interested in what people think. UPDATE: Looks like the folks on the backend fixed the E911 Address issue for the line with the S21 as the Sprint Website is now accepting the address as valid.
    • This one I found particularly interesting. They filed to upgrade the T-Mobile (orange) to n71 and n41 a while back. Then this week, they filed to keep the two surrounding Sprint sites (blue). The T-Mobile one is very tall with a huge footprint, so I understand why they might want to use the Sprint sites, but just very interesting they filed to upgrade it and then decided against it (as best I can tell).
    • Oftentimes they're locked into contracts with their contractors, otherwise they would just cancel the T-Mobile site's upgrade. 
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...