Jump to content

LG Optimus G LTE Engineering Screen


lilg740

Recommended Posts

It even goes landscape mode too.

 

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

 

AJ

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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?).

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

 

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

Link to comment
Share on other sites

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

 

 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

 

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

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

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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