Jump to content

SignalCheck Beta Crew Forum


Recommended Posts

Samsung devices not the network gear OEM, I'm in Ericsson market.

Np. Just trying to tell Mike what works so he knows not every aspect has issues with latest beta.

 

Sent from my LG-LS997 using Tapatalk

  • Like 1
Link to post
Share on other sites
  • Replies 962
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Beta crew.. assemble!   A new update is finally published.. if you're special   -Mike

Already started working on something along those lines, great minds think alike! I have a busy few days coming up but I should have another update ready by mid-week.   I appreciate everyone's feedba

Just a quick update for the Beta Crew, yes I am still hacking away at the new Alerts.. it is a lot of work trying to get everything working well on Oreo+ devices while not breaking pre-Oreo devices. I

Posted Images

You should still see whatever you had before, except some T-Mobile users who will need EARFCN data in order to see a band. Many users will now see more info. Where is AWS missing from? Are you seeing any EARFCN stuff (guessing not, on a Samsung)? Is it showing any band info at all?

 

-Mike

It's missing from the main screen where it used to say: LTE AWS it now just says LTE. I don't get any EARFCN info on my Note 5. :-(

Link to post
Share on other sites

To clarify, where it just says LTE used to say LTE AWS. 751c6d8a44e2a10ff5df4575c707df44.jpg

 

Sent from my SM-N920V using Tapatalk

  • Like 1
Link to post
Share on other sites

Hmmm clearly I broke something with "LTE xxxxx" display. You're all still seeing band information in the provider line so it's not your device. I gutted those routines so I expected some hiccups. I overhauled a lot of code; much of this used to be hard-coded, now it's dynamic. I'll look into it tonight!

 

-Mike

  • Like 2
Link to post
Share on other sites

Hmmm clearly I broke something with "LTE xxxxx" display. You're all still seeing band information in the provider line so it's not your device. I gutted those routines so I expected some hiccups. I overhauled a lot of code; much of this used to be hard-coded, now it's dynamic. I'll look into it tonight!

 

-Mike

The notification bar and the provider information right below rsrp and snr values i.e. Sprint B26 are correct, but yeah for whatever coding reason the LTE  XXXX isn't displaying (which is a nice feature as the large text is easy to take a quick glance at). Your earfcn fix with this beta is much appreciated though.

  • Like 2
Link to post
Share on other sites

Just pushed out another beta, please let me know if that LTE frequency display is fixed. It was likely only observed on devices that weren't getting the EARFCN natively.

 

Finished up a lot of other loose ends that I had been working on too. Did somebody say neighbor LTE bands...

 

Getting very close to tackling everything I had planned for the next public update. Thanks for all of the feedback!!

 

-Mike

  • Like 1
Link to post
Share on other sites

Mike,

 

New version crashes on start-up on my Moto G3 and Moto G4 devices, all of which are rooted.  It gets as far as asking for root permissions, then crashes before I can grant them.  I used the "Report" button to send a report from one of each device.

 

Works on my HTC M9 and my LG G5, both of which are on Nougat.  Didn't have a chance to test my BLU R1 this morning.

 

- Trip

Link to post
Share on other sites

nTelos B26 "Provider" line text is messed up. It shows "Provider:B26 (310470)". Most likely where your saving your provider variable is just missing nTelos. B25 is good shows nTelos B25. B41 is unknown if B41 I will post again other wise it woulx be good.

  • Like 1
Link to post
Share on other sites

Can confirm the same on my note 5.3e3f6f276af29b9ad100ac9b3e6d06ce.jpg

 

Sent from my SM-N920V using Tapatalk

Link to post
Share on other sites

Failing to load on my rooted LG G2s.  Sent a report from each one.

Link to post
Share on other sites

Failing to load on my rooted LG G2s.  Sent a report from each one.

 

Are any other users here running rooted devices?  Your report makes me wonder if our crashes are related--the app attempting to use the root method to read the neighbor EARFCN or something before permission is granted, or something along those lines.

 

- Trip

  • Like 1
Link to post
Share on other sites

:banana::urock: Really excited by bands for the neighbor list. Could we get it to optionally display earfcns instead and also limit them to one earfcn? I am referring to small cell hunting, which has a unique earfcn where we have seen them. Else we will also need to find all magic boxes and airaves in our market to get their PCIs (we have most everything else). Magic Boxes also have there own earfcn.

 

Alternatively allow us to plug in the earfcn for SC, MB, and AR which would then appear in the neighbors list. The ability to truncate or change the font size for the neighbors list would also be great so we can fit more on the screen. :thx:

  • Like 1
Link to post
Share on other sites

Works fine on my unrooted Photon 4G (Wimax) Android 2.3.5

  • Like 1
Link to post
Share on other sites

Well these aren't what I wanted to wake up to.. none of my test devices are having these issues and a couple are rooted. I'll go see what I can come up with, but for now nobody else should bother updating yet. If I can't find those crash reports I'll reach out to you guys.

 

-Mike

  • Like 2
Link to post
Share on other sites

New version crashes on start-up on my Moto G3 and Moto G4 devices, all of which are rooted.  It gets as far as asking for root permissions, then crashes before I can grant them.  I used the "Report" button to send a report from one of each device.

 

Works on my HTC M9 and my LG G5, both of which are on Nougat.  Didn't have a chance to test my BLU R1 this morning.

 

Failing to load on my rooted LG G2s.  Sent a report from each one.

 

Are any other users here running rooted devices?  Your report makes me wonder if our crashes are related--the app attempting to use the root method to read the neighbor EARFCN or something before permission is granted, or something along those lines.

 

Trip, you were close -- I saw the reports from you guys, it's the neighbor EARFCN routine crashing on Android 4.2-6.0. If you enable Airplane Mode (or leave LTE coverage) and then disable "Show Neighbor Cells" you should be able to use the app for now. I will be working on it this morning, hopefully I'll have an update pushed out shortly.

 

-Mike

  • Like 1
Link to post
Share on other sites

I can confirm the missing LTE XXXX on my note 5 as well. Additionally, and it is to be somewhat expected with Samsung, the neighboring cells are all showing B1.

Link to post
Share on other sites

I really like seeing the Neighbor Cell Bands. I no longer have to go over to Cellmapper or Network Signal Guru to see neighbor bands. Awesome. Works great on my Nexus 6 Project Fi and Nexus 6P on T-Mobile.

 

cc16204cdbc97d51c247dafa96d62851.jpg1b12634beeba5fc3a11e108fdf68d62e.jpg

 

US Cellular on N6 Project Fi too

bae4891dfb1183e23b6a305ae29f6d38.jpg

 

Sent from my Nexus 6 using Tapatalk

  • Like 2
Link to post
Share on other sites

Still crashes on LG G2 after using airplane mode, removing modem commands, exiting, removing airplane modem.  Same with rebooting.  Same with removing root privileges. Sent two reports.

Link to post
Share on other sites

Still crashes on LG G2 after using airplane mode, removing modem commands, exiting, removing airplane modem.  Same with rebooting.  Same with removing root privileges. Sent two reports.

 

I don't think it is related to the modem or root, it's the neighbor cell display. Disable neighbor display and let me know.

 

-Mike

  • Like 1
Link to post
Share on other sites

I don't think it is related to the modem or root, it's the neighbor cell display. Disable neighbor display and let me know.

 

-Mike

 

 works.  will try adding back in root and modem. Those work as well.  Neighbor list is the problem.

Edited by dkyeager
  • Like 1
Link to post
Share on other sites

Another update is done and should be available shortly. Hopefully the crashes and LTE display bugs are fixed. There is also a new option to display neighbor EARFCN info. It is disabled by default, so go into Preferences > Display Settings > Show Neighbor EARFCNs.

 

-Mike

  • Like 3
Link to post
Share on other sites

Another update is done and should be available shortly. Hopefully the crashes and LTE display bugs are fixed.

-Mike

The word LTE is back on my Note 5, but no band indication in the header.

scpbeta_zpsk2x5uwzc.jpg

  • Like 1
Link to post
Share on other sites

The word LTE is back on my Note 5, but no band indication in the header.

 

 

Also, I notice your Neighbor Cells say Band 1.

Link to post
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

    • Columbus Sprint conversion site to T-Mobile update: tower hands arrived before sunset and unloaded. Said Sprint stuff will be demoed first, but Microwave and b25 will remain. Will only be adding AWS. Said no n41, 600 or 700.  So I took pictures of antennas but not a big pile under tarp. Personally think they are not allowed to admit and 5g equipment. Lots of wackos out there. Checking on the visible antennas, there are three Nokia VBNAEHC-01, which are AirScale MAA 64T64R 192AE B41 320W AEHC (AAEHC) capable of 5g.  There will also be larger racks with plenty of room for them to stand on.
    • *#0011# - This code shows the status information of your GSM network such as registration status, GSM band, etc.;
    • Rather than upgrade all my lines from Magenta to Max I stayed on Magenta 2.0 and when I need UHD or more HotSpot I just add the $15/mo GoMax AddOn when I need it and remove it when I'm done. That costs me $15 for the month. Rather than taking the $30/mo hit permanently to upgrade the entire account (7 Lines/3 Paid). Since I'm paying for all the lines I don't care if any of the other ones have UHD etc. 🙃
    • Pretty incredible. Of course, I wonder what percentage of Magenta Max Plan users forget to activate (or don't activate) UHD streaming on their devices.
    • I couldn't stay away for long, gonna return the iPhone I told myself I wouldn't do this but iPhone just doesn't work for me, tried giving it a weekend but being back on my Ultra feels natural iPhone is slow and laggy lol oh well. 
  • Recently Browsing

    No registered users viewing this page.

×
×
  • Create New...