Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Interesting, Brian Klug on the All About Android show says that the N5 has the same panel as the Droid DNA, which is a JDI panel. An "LG" phone is shipping with a non LG panel.

 

What is a JDI panel and a non LG panel?

Link to comment
Share on other sites

The Nexus 5 puts my friends GS3 LTE to shame. -99-103 dBm vs ~108-116 dBm at the same spot.

 

Do you have any guesses as far as whether or not the lte radio on the nexus will also have a strong band 41 rf performance? I'd dislike for it not to. I'd imagine band 25 would take over lte replacing 41 on the phone.

 

 

Looking at the menus, there's no way to disable band 25, right.

 

 

Well, I'm still kinda hoping for some band 41 sceenshots on the nexus 5. 60+ mbps?!

Link to comment
Share on other sites

For anyone like myself that has the problem where the phone rings OK for an incoming call but you cannot answer and the phone then locks up I don't know why it is happening but I think I know under what conditions it happens. At home I only get 3g and never have this problem. At work I am continuously connected to LTE and this problem occurs often, maybe half the time. When my phone is set to 3g only the problem stops.

So, does anyone have an idea why when connected to LTE an incoming call cannot be answered? Both Google and Sprint do not know and Google wants to replace the phone. I suspect it is more of a software issue rather than the phones hardware but maybe someone more knowledgeable has an idea. Thanks

Link to comment
Share on other sites

I downloaded the Field Test App but when I try and change anything its asking for the code...how do you get around this? Does anyone know what bands are available in the Baton Rouge, LA area?

 

 

I did it this way......it was very simple and straight forward. After down loading the drivers the instructions in this thread got there "QWIKLY"

http://s4gru.com/index.php?/topic/4989-lg-google-nexus-5-users-thread/page-86&do=findComment&comment=238325

Link to comment
Share on other sites

For anyone like myself that has the problem where the phone rings OK for an incoming call but you cannot answer and the phone then locks up I don't know why it is happening but I think I know under what conditions it happens. At home I only get 3g and never have this problem. At work I am continuously connected to LTE and this problem occurs often, maybe half the time. When my phone is set to 3g only the problem stops.

So, does anyone have an idea why when connected to LTE an incoming call cannot be answered? Both Google and Sprint do not know and Google wants to replace the phone. I suspect it is more of a software issue rather than the phones hardware but maybe someone more knowledgeable has an idea. Thanks

 

 

This happens to a lot of people, but to get this glitch evaluated we need to make a runngin list of names that has this issue.

Link to comment
Share on other sites

N5 originally slated to ship on 11/22, got notice this morning that it shipped today!!!  Keep up the good work Google.

 

for 11/26 orders.I guess we are going to expect a tracking number by Saturday  

  • Like 1
Link to comment
Share on other sites

jamess32, on 14 Nov 2013 - 07:41 AM, said:snapback.png

 


For anyone like myself that has the problem where the phone rings OK for an incoming call but you cannot answer and the phone then locks up I don't know why it is happening but I think I know under what conditions it happens. At home I only get 3g and never have this problem. At work I am continuously connected to LTE and this problem occurs often, maybe half the time. When my phone is set to 3g only the problem stops.
So, does anyone have an idea why when connected to LTE an incoming call cannot be answered? Both Google and Sprint do not know and Google wants to replace the phone. I suspect it is more of a software issue rather than the phones hardware but maybe someone more knowledgeable has an idea. Thanks

This happens to a lot of people, but to get this glitch evaluated we need to make a runngin list of names that has this issue.

Could it be that when the phone is on LTE and it is paged by the network ,to tell the phone it has a call - it just doesn't fall back to 3G properly to connect?

Link to comment
Share on other sites

http://m.imgur.com/2zeTMXg

 

My phone seems to be having an issue in some places around Las Vegas.

 

When the setting is global I lose my connection every few minutes and it says searching for service, even though I am in a strong 3g area. It does this both at work (spotty coverage) and at home (great coverage). It doesn't do this at school, or at my brothers house.

 

If I set it to LTE it still does this. If I set it to 3g only the problem disappears.

 

When on global, I can get and use LTE when I am near an LTE tower.

 

If you look at the pic you will see the cycle of it losing service.

 

Anyone who is smarter than me could you please explain why this is happening?

 

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

http://m.imgur.com/2zeTMXg

 

My phone seems to be having an issue in some places around Las Vegas.

 

When the setting is global I lose my connection every few minutes and it says searching for service, even though I am in a strong 3g area. It does this both at work (spotty coverage) and at home (great coverage). It doesn't do this at school, or at my brothers house.

 

If I set it to LTE it still does this. If I set it to 3g only the problem disappears.

 

When on global, I can get and use LTE when I am near an LTE tower.

 

If you look at the pic you will see the cycle of it losing service.

 

Anyone who is smarter than me could you please explain why this is happening?

 

 

Sent from my Nexus 5 using Tapatalk

 

I see this in some locations around the Washington DC area too.  Since it doesn't happen everywhere, I am throwing in in the eCSFB bucket and am assuming it will fix itself as the network progresses.  I have only noticed this in areas without LTE coverage. 

  • Like 1
Link to comment
Share on other sites

After thinking about it for a bit, I wonder if this is the new single radio behavior for when it searches for LTE.  If there is only one radio path, it might need to drop the 1X/EVDO connection while it scans for LTE.  Then it reconnects when it can't find LTE... rinse and repeat.

Link to comment
Share on other sites

After thinking about it for a bit, I wonder if this is the new single radio behavior for when it searches for LTE.  If there is only one radio path, it might need to drop the 1X/EVDO connection while it scans for LTE.  Then it reconnects when it can't find LTE... rinse and repeat.

 

Ding ding ding!

  • Like 1
Link to comment
Share on other sites

Still looking for a way to manually update the PRL ourselves to a chosen one...any ideas on how to enable the DIAG port on the phone?

 

Try following the guide here.  I was able to flash my PRL through this method.

 

http://s4gru.com/index.php?/topic/5022-easy-method-to-obtain-your-msl-and-flash-a-prl/

Link to comment
Share on other sites

Yeah thats the problem...no idea how to enable the DIAG port enable to get basic-flasher to work.

 

I don't know how to get Diag mode to enable on a Nexus 5.  There has got to be a way.  Once you find out, please let me know so I can update the guide for Nexus 5 devices on how to enable Diag mode.

Link to comment
Share on other sites

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

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...