Jump to content

SignalCheck Beta Crew Forum


mikejeep

Recommended Posts

6 minutes ago, RAvirani said:

I’d recommend against using 0 because It’s actually possible to assign a TAC of 0 (in LTE the range is 0 to 65535 and in NR the range is 0 to 16777215).

My thought process with -1 was that some sort of error could in theory cause a blank or an empty value to end up in an upload file. A -1 feels a bit more intentional.

No problem, I hadn't looked too closely but you are right, 0 is valid (and recognized by the app as such) -- internally, I set it to -1 unless a valid value is returned anyway, so that shouldn't be too bad.

 

6 minutes ago, RAvirani said:

I’ll see if I can get the backend up and ready to go this weekend (hopefully before the app update is released). 

Let me know when you get your side ready, no rush. The current alpha build I'm working on is half-broken as I try to implement this new TelephonyCallback stuff I'm working on.

  • Like 2
Link to comment
Share on other sites

1 hour ago, mikejeep said:

No problem, I hadn't looked too closely but you are right, 0 is valid (and recognized by the app as such) -- internally, I set it to -1 unless a valid value is returned anyway, so that shouldn't be too bad.

Let me know when you get your side ready, no rush. The current alpha build I'm working on is half-broken as I try to implement this new TelephonyCallback stuff I'm working on.

Awesome!

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Ever consider an Android Auto app?  Even if it just showed the same data as on the SCP app on phone?  Just something real simple.  Man, I would dig that. Not have to look at my phone.  Displayed at eye level on a much larger infotainment screen.  It would be safer.  Just throwing the idea out there.

Robert

  • Love 2
Link to comment
Share on other sites

1 hour ago, S4GRU said:

Ever consider an Android Auto app?  Even if it just showed the same data as on the SCP app on phone?  Just something real simple.  Man, I would dig that. Not have to look at my phone.  Displayed at eye level on a much larger infotainment screen.  It would be safer.  Just throwing the idea out there.

I looked into it a few times, but it was never allowed per the Android Auto guidelines. AA apps had to be related to media, messaging, or navigation. I can understand why they wouldn't want to explicitly permit an app like SCP that encourages users to look at their dash instead of the roadway.

With the increased reliance on in-dash apps, I wonder if the rules have been relaxed at all. I'll look into it again.

  • Like 1
Link to comment
Share on other sites

On 5/20/2022 at 10:29 PM, S4GRU said:

Many of these sites I am uploading are for sites that do not exist, yet.  Although, I suppose I could go into NR only mode every time I connect to a new site, and then switch back, allowing all the TAC NR trails that occur to now have a home.

Ideally, I would love to ne able to add the TAC's myself.  I have the NR Trails CSV file downloaded, and I see all the TAC-less NR entries.  Is there any way I can edit and manually upload them myself?  Maybe create a portal for such an upload?  Or at least give me a way to create at least one manual entry for every new site?

I am still thinking about both of these.

My idea is to try to match points without a TAC to an existing site if possible. In the case an existing site can’t be found, I can list the TAC as unknown and allow the user to enter an “unconfirmed” TAC until someone maps the site correctly (with a TAC). Then the “unconfirmed” TAC will be overwritten with that TAC. 

How does that sound?

  • Like 3
Link to comment
Share on other sites

On 5/21/2022 at 12:11 PM, mikejeep said:

Let me know when you get your side ready, no rush. The current alpha build I'm working on is half-broken as I try to implement this new TelephonyCallback stuff I'm working on.

Support for the -1 TAC is good to go now, so I'm ready whenever you are!

  • Like 1
Link to comment
Share on other sites

A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes:

New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this.

New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working.

Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing.

Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact.

Feedback welcome as always!

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

1 hour ago, mikejeep said:

A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! 

Update just showed up for both of my phones. So far I don't notice any difference, LTE TA is still reporting as 0, I was hoping the new routine might fix that. I sent a diag report from both phones in case you need any of that info. I'll let you know in a day or so if its crashing as frequently or not. 

  • Thanks 1
Link to comment
Share on other sites

n7 still appearing with latest version on samsung galaxy a32 5g with android 12. Swipe feature works. Log sent.

Samsung s21 ultra does show solid n41 connection on T-Mobile through Boost Mobile.

Note: fixed typo by removing "not".

  • Thanks 1
Link to comment
Share on other sites

14 hours ago, RAvirani said:

I am still thinking about both of these.

My idea is to try to match points without a TAC to an existing site if possible. In the case an existing site can’t be found, I can list the TAC as unknown and allow the user to enter an “unconfirmed” TAC until someone maps the site correctly (with a TAC). Then the “unconfirmed” TAC will be overwritten with that TAC. 

How does that sound?

Sounds great!  Let's give it a go.  Thank you.  It should add a lot of data points of mine up there going forward. 

Robert

  • Like 1
Link to comment
Share on other sites

9 hours ago, mikejeep said:

Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing.

Thank you so much for this one.  I'll be giving this a try--this is something that has caused me a ton of grief in the past.  When you're running 9 or 10 phones like I am, it's hard to make sure they're all getting updated locations.  This should be massively helpful.

Let me know what information I can prove to help you optimize this.

- Trip

  • Like 2
Link to comment
Share on other sites

8 hours ago, dkyeager said:

Samsung s21 ultra does not show solid n41 connection on T-Mobile through Boost Mobile.

Could you elaborate on this, not sure what you mean?

 

7 hours ago, S4GRU said:

Sounds great!  Let's give it a go.  Thank you.  It should add a lot of data points of mine up there going forward.

Try going into Preferences > Beta Crew Settings > Web Data Timestamp and setting your timestamp in the past to re-upload entries missing a TAC and see what happens!

 

4 hours ago, Trip said:

Let me know what information I can prove to help you optimize this.

I just need to improve it more on my end. It's just a crude "if location hasn't changed in 10 min, restart" at the moment which uses unnecessary resources when your device is legitimately idling in one spot. Going to try making it a little smarter moving forward. Please keep an eye on it though, because I rarely see the issue myself and I want to make sure this actually solves it.

  • Like 1
Link to comment
Share on other sites

4 hours ago, mikejeep said:

Try going into Preferences > Beta Crew Settings > Web Data Timestamp and setting your timestamp in the past to re-upload entries missing a TAC and see what happens!

I reuploaded 26,000 points.  I do not see any of them appearing yet on the map.  Including some tracks I made this morning that are on already identified cells.

Robert

Link to comment
Share on other sites

9 minutes ago, S4GRU said:

I reuploaded 26,000 points.  I do not see any of them appearing yet on the map.  Including some tracks I made this morning that are on already identified cells.

Did the app report any errors, or did it seem to go through ok? Be curious to see what @RAvirani sees on the server side.

Link to comment
Share on other sites

1 minute ago, mikejeep said:

Did the app report any errors, or did it seem to go through ok? Be curious to see what @RAvirani sees on the server side.

It said all but a few hundred of approx 27k didn't go through.  And there would be thousands of NR points that wouldn't have a TAC.

Robert

  • Thanks 1
Link to comment
Share on other sites

I am also having a lot of Force Close errors with the update today.  Is it just me and my device?  I have done a hard reboot and it doesn't help.

Robert

Link to comment
Share on other sites

I'm noticing a spike in instability while driving around testing the app today also.. more freeze-ups than crashes, but it's probably all related. Hopefully any crash reports that are collected can shed some light on it for me. I'll be looking into it later tonight.

  • Like 2
Link to comment
Share on other sites

I appreciate the feedback today -- another new is SCP beta rolling out right now! It should resolve the force closes that started with yesterday's beta release; I also made additional improvements that hopefully(?) will reduce ongoing issues with overall app stability.

  • Like 1
Link to comment
Share on other sites

22 hours ago, dkyeager said:

n7 still appearing with latest version on samsung galaxy a32 5g with android 12.

I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung.

EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.

  • Like 1
Link to comment
Share on other sites

7 hours ago, mikejeep said:

Did the app report any errors, or did it seem to go through ok? Be curious to see what @RAvirani sees on the server side.

Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked.

Robert

Link to comment
Share on other sites

7 minutes ago, S4GRU said:

Actually, I notice it says whole clusters were skipped because of invalid TAC values.  It says "File exported for inspection."  I do have Log Sites with Missing TAC checked.

Robert

Let me take a look tonight. 

Link to comment
Share on other sites

11 hours ago, mikejeep said:

EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.

How do you report an issue to Samsung? I'd love to report the LTE TA issue on the S22s but I had no idea how. 

Link to comment
Share on other sites

2 hours ago, mdob07 said:

How do you report an issue to Samsung? I'd love to report the LTE TA issue on the S22s but I had no idea how. 

They've become far more responsive on the Samsung Developer portal than they had been in the past; they now have a support ticketing system that they actually utilize. It's usually tricky for me to pursue anything unless I have the device in question in-hand, but I can try submitting something on your behalf if you can provide me with what they might ask for. Or you can check out https://developer.samsung.com/dashboard/support and try yourself.

FYI I reported TA=0 on the A32 last night; I'll add a note that it happens on your device as well, I have all the info I need from your diagnostic reports.

  • Like 1
Link to comment
Share on other sites

14 hours ago, mikejeep said:

I was able to figure this out by looking at your diagnostic reports -- you're seeing n7 because your Galaxy A32 is reporting it natively as n7.. Samsung will have to fix that on their end unfortunately. Do the engineering screens report it correctly? I have an A32 test device but I have not seen it connect to n41 (or "n7") yet. If I do, I'll try to troubleshoot and nag Samsung.

EDIT: After I installed the new Android 12 update, I'm now seeing the n7 bug too -- I will reach out to Samsung. They were very responsive when I reported some related glitches with the initial A32 software.

On 5/23/2022 at 11:33 AM, mikejeep said:

Could 

Thanks. Yes the engineering screen shows n41.

The S21 ultra works fine. Removed typo "not".

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

    • 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...