Jump to content

LG Optimus G LTE Engineering Screen


Recommended Posts

Posted

What does the LTE Engineering screen look like for this phone? Does it show HEX SCID?

Posted

So basically if I want HEX SCID I need an HTC or iPhone....yuck....

Posted

It even goes landscape mode too.

 

Whoa, whoa, whoa. Is there something other than the legendary Galaxy Note 2 in the digiblur household?

 

AJ

Posted

So basically if I want HEX SCID I need an HTC or iPhone....yuck....

 

Or code an app that digs it out of the baseband on other phones. I guess I don't understand why it is that big of deal, the 3 digit IDs work just fine.

 

Whoa, whoa, whoa. Is there something other than the legendary Galaxy Note 2 in the digiblur household?

 

AJ

 

Nope, still only have the S3, Note2, and my handed down EVO LTE. That's a screen shot from jmuskratt's hunting.

Posted

Or code an app that digs it out of the baseband on other phones. I guess I don't understand why it is that big of deal, the 3 digit IDs work just fine.

Because I need the hex for the cheat sheet. Right now we have a mess with a site that is not correlating correctly to the cheat sheet so I am trying to get HEX SCID's from sites that are up and no one wants to volunteer. And I know absolutely nothing about creating an app and lordsutch's app didn't work for me.

Posted

It will work itself out. I had several anomalies on the HEX pattern that took me a while to figure out even with 40-50 sites active in the market.

Posted

You might be able to get HEX ids from the Android radio log. Use aLogCat or another logcat tool, watch the radio log (in aLogCat, it's under preferences), and look for DATA_REGISTRATION_STATE messages with 14 as the fourth value. I believe the Qualcomm RIL always provides the HEX ID on these as the third value - it does on my Evo LTE, and the same pattern shows up in pastebin output from phones from several different carriers and manufacturers.

Posted

You might be able to get HEX ids from the Android radio log. Use aLogCat or another logcat tool, watch the radio log (in aLogCat, it's under preferences), and look for DATA_REGISTRATION_STATE messages with 14 as the fourth value. I believe the Qualcomm RIL always provides the HEX ID on these as the third value - it does on my Evo LTE, and the same pattern shows up in pastebin output from phones from several different carriers and manufacturers.

How do I do that?

Posted

1. Get aLogCat from the market.

2. Open it.

3. In preferences, click on "Buffer?" and choose "Radio"

4. Tap back.

5. Tap the magnifying glass icon.

6. In the text box, type "DATA_REGISTRATION_STATE.*14" (no quotes).

7. Check the box labeled "Apply as regular expression?"

8. Tap Okay.

 

You should now see the LTE registration messages from the radio. If there's a HEX ID being reported by the RIL, it should be the third number in each message. It should look something like:

 

D/RILJ ( 1863): [0050]< DATA_REGISTRATION_STATE {1, 9d00, 0266b103, 14, 0, 20}

 

The part in bold is the HEX ID. I have no idea what the number before it is (possibly the TAC?).

Posted

1. Get aLogCat from the market.

2. Open it.

3. In preferences, click on "Buffer?" and choose "Radio"

4. Tap back.

5. Tap the magnifying glass icon.

6. In the text box, type "DATA_REGISTRATION_STATE.*14" (no quotes).

7. Check the box labeled "Apply as regular expression?"

8. Tap Okay.

 

You should now see the LTE registration messages from the radio. If there's a HEX ID being reported by the RIL, it should be the third number in each message. It should look something like:

 

D/RILJ ( 1863): [0050]< DATA_REGISTRATION_STATE {1, 9d00, 0266b103, 14, 0, 20}

 

The part in bold is the HEX ID. I have no idea what the number before it is (possibly the TAC?).

Will this work on GNex?

Posted

Try it and let us know.

 

Sent from my little Note2

That requires me to drive for about 45 minutes to the nearest LTE site....not driving out there again to just be disappointed or confused again.

Posted

See if you can see any data messages on Evdo then. You don't have a Qualcomm chipset though which makes that phone a totally different animal.

 

Sent from my little Note2

 

 

Posted

 

Try it and let us know.

 

Sent from my little Note2

 

I'll try it out in a few since I'm in an active LTE area right now with my Gnex.

 

Edit: So far, nothing. I'll keep an eye overnight and post again in the morning.

 

Sent from Josh's iPhone 5 using Tapatalk 2

Posted

I tried it on my Note2 and the logcat app doesn't seem to show what as much stuff as when connected to the PC using adb. Have a -118 barely signal outside my house and it doesn't show anything. I didn't drag the laptop outside though. Will try it tomorrow.

 

Sent from my little Note2

 

 

Posted

Try removing the .*14 part; if you're still not getting any messages (and you are in Radio mode, not Main mode), it may require a debugging mode to be enabled in your ROM. Seems to work out of the box on CM at least.

 

Of course, I posted the aLogCat advice on the basis that we were talking about the LG Optimus G, which has a Qualcomm radio just like the EVO's. I honestly don't know what a Galaxy Nexus with the VIA LTE chipset would report.

 

On the GNex, another place you might find the data is on the Radio Info screen, which you can access using the dialer code *#*#4636#*#* or via the menu in SignalCheck; the LTE info appears next to the "CellInfo" label, if available.

Posted
Try removing the .*14 part; if you're still not getting any messages (and you are in Radio mode, not Main mode), it may require a debugging mode to be enabled in your ROM. Seems to work out of the box on CM at least.

 

Of course, I posted the aLogCat advice on the basis that we were talking about the LG Optimus G, which has a Qualcomm radio just like the EVO's. I honestly don't know what a Galaxy Nexus with the VIA LTE chipset would report.

 

On the GNex, another place you might find the data is on the Radio Info screen, which you can access using the dialer code *#*#4636#*#* or via the menu in SignalCheck; the LTE info appears next to the "CellInfo" label, if available.

 

The VIA chipset is for the 1X and EVDO. There is a Qualcomm LTE chipset in this phone. I'll check your suggestions in a few.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Posted

The VIA chipset is for the 1X and EVDO. There is a Qualcomm LTE chipset in this phone. I'll check your suggestions in a few.

 

I've always read that the phone has a Samsung based LTE chipset. Otherwise it would would a Qualcomm for both CDMA and LTE tech.

Posted

 

I've always read that the phone has a Samsung based LTE chipset. Otherwise it would would a Qualcomm for both CDMA and LTE tech.

 

Then I must be mistaken. And that could be why nothing shows up. And doing the *#*#4636#*#* was a dead end. My LTE connection dropped after I opened it. Of course, with the phone being on Seasonal Standby that may have something to do with it.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Posted

The Note2 which has a Qualcomm chipset and does not show these messages so it is purely based on if the OEM decided to include them in the log.

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

  • Posts

    • Also a full system update, security update of about 500 or so MB
    • A new 60MB GP System update was waiting when I checked my S24+ tonight.  And bringing it to a November 1 date this time. 
    • Pixel 8a Dec system update over 800 mb is out for locked t mobile.
    • Drove by there and it definitely isn't on the Northlake property. It was very late, so I couldn't see much else though. Did some more sleuthing on GoogleMaps and I suspect it might be this powerline site nearby: Google Maps I will go by there in the next couple of days during the daytime and see if that's the case.
    • Vinegar Hill is getting the Brooklyn Heights treatment now with regard to small cells. I mapped two more small cells in the neighborhood in the past few days so now T-Mobile is up to 8 of them in such a tiny neighborhood. While it's cool they're doing this since it means outdoors you get a consistent 400Mbps+ almost everywhere, it sucks because they're obviously deploying so many of them to make up for their lack of a macro site in the entire neighborhood. Because there isn't a macro, the small cells have a greater coverage area than you see in other neighborhoods and you often connect to them while indoors but coverage and speeds fall off indoors much faster on small cells than on macros in my experience.  Even Dish has better coverage than T-Mobile in Vinegar Hill since they added the site on top of the Extra Space Storage building alongside AT&T and Verizon. T-Mobile needs to get in line with their competitors there.
  • Recently Browsing

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