S4GRU Posted April 29, 2023 Share Posted April 29, 2023 (edited) I have the same error on my Pixel 7 Pro. When I first go to Upload Web Data, it gives me an error and it takes me manually sign in, which I never have to do typically. It always remember my credentials in the past. That initial error says "Account validation error: g3.g: Abstract classes can't be i..." and the rest is truncated from there. The error disappears really fast. And then I attempt to sign in as being asked and I get another quick error flash on my screen, "Login error: g3.g: Abstract classes can't be instantiated! R...". And then I am back to my normal monitoring screen. Robert Edited April 29, 2023 by S4GRU Add images 1 1 Quote Link to comment Share on other sites More sharing options...
PedroDaGr8 Posted April 29, 2023 Share Posted April 29, 2023 Same thing for me, though I might have accidentally sent you like half a dozen diagnostics by holding down for too long. Edit: I was able to get the full text of the error via Samsungs NiceCatch. All of the errors are the same, just with either Authentication Error or Login Error Abstract classes can't be instantiated! Register an instance creator or a TypeAdapter for this type. ClassType: m0.f5 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted April 29, 2023 Author Share Posted April 29, 2023 Thanks all, I was able to figure out the issue, it was a compiler problem -- new beta update is rolling out now that resolves it! 3 1 2 Quote Link to comment Share on other sites More sharing options...
PedroDaGr8 Posted April 29, 2023 Share Posted April 29, 2023 16 minutes ago, mikejeep said: Thanks all, I was able to figure out the issue, it was a compiler problem -- new beta update is rolling out now that resolves it! Can confirm, that fixed it. 4 1 Quote Link to comment Share on other sites More sharing options...
mdob07 Posted April 30, 2023 Share Posted April 30, 2023 23 hours ago, mikejeep said: Thanks all, I was able to figure out the issue, it was a compiler problem -- new beta update is rolling out now that resolves it! Confirmed fixed for me as well. 3 Quote Link to comment Share on other sites More sharing options...
Grabber5.0 Posted May 17, 2023 Share Posted May 17, 2023 Is there a known issues log or post somewhere? I don't want to report a known issue. Edit: also I'm probably dumb for not sending a report while triaging. Quote Link to comment Share on other sites More sharing options...
mikejeep Posted May 17, 2023 Author Share Posted May 17, 2023 8 minutes ago, Grabber5.0 said: Is there a known issues log or post somewhere? I don't want to report a known issue. Edit: also I'm probably dumb for not sending a report while triaging. The website (https://signalcheck.app) has a Known Issues page on the Wiki tab. If you want to report a bug, the Issues tab is a good place to check to see if it's already reported. If not, you can report it there. You can always just post, PM, or email too.. I get to it all eventually. Sending diagnostic reports when you see an issue is definitely helpful. Feel free to share info even without a report, you can always send it next time you see an issue. 1 Quote Link to comment Share on other sites More sharing options...
Grabber5.0 Posted May 17, 2023 Share Posted May 17, 2023 1 hour ago, mikejeep said: The website (https://signalcheck.app) has a Known Issues page on the Wiki tab. If you want to report a bug, the Issues tab is a good place to check to see if it's already reported. If not, you can report it there. You can always just post, PM, or email too.. I get to it all eventually. Sending diagnostic reports when you see an issue is definitely helpful. Feel free to share info even without a report, you can always send it next time you see an issue. I don't see this one there, though I suppose I could be related to the one about no signal strength in the signal icons. This morning I had two signal icons, both without signal strength, and one apparently stale. I had an LTE and a 5G icon, and when I opened the app from the notification (there were two notifications, one empty and one populated - I've seen that before) it only showed LTE and WiFi. I threw away and reopened the app a couple times with no change, then used exit from the app menu and everything returned to normal when I reopened the app. Quote Link to comment Share on other sites More sharing options...
Trip Posted August 6, 2023 Share Posted August 6, 2023 Mike, Got myself a Moto Edge 2022 which I am in love with for logging. Supports every feature as far as I can tell, including band locking without any external apps! More on that on Reddit ( https://www.reddit.com/r/Dish5G/comments/15h46le/comment/juyssk6/?utm_source=reddit&utm_medium=web2x&context=3 ) and I'm about to cross-post in the Motorola forum here. One question, though, is whether or not it's possible to get a System Shortcut (and thus the lightning icon) to the *#*#4636*#*# menu, which is labeled "Testing," or the sub-menu that actually does the band locking. I briefly tried to find a shortcut to it with a shortcut app and didn't immediately find it. If there's something specific that might help in tracking it down, let me know. (And I know it may not be possible to get a shortcut, but the Radio Info one does work, just that it's not the screen I want to be on...) - Trip 2 Quote Link to comment Share on other sites More sharing options...
dkyeager Posted August 6, 2023 Share Posted August 6, 2023 11 hours ago, Trip said: Mike, Got myself a Moto Edge 2022 which I am in love with for logging. Supports every feature as far as I can tell, including band locking without any external apps! More on that on Reddit ( https://www.reddit.com/r/Dish5G/comments/15h46le/comment/juyssk6/?utm_source=reddit&utm_medium=web2x&context=3 ) and I'm about to cross-post in the Motorola forum here. One question, though, is whether or not it's possible to get a System Shortcut (and thus the lightning icon) to the *#*#4636*#*# menu, which is labeled "Testing," or the sub-menu that actually does the band locking. I briefly tried to find a shortcut to it with a shortcut app and didn't immediately find it. If there's something specific that might help in tracking it down, let me know. (And I know it may not be possible to get a shortcut, but the Radio Info one does work, just that it's not the screen I want to be on...) - Trip It would be totally awesome if we could input what we wanted the system shortcut to be which SCP would then do. 3 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted August 6, 2023 Author Share Posted August 6, 2023 I'm not sure if I can make an option to pick any shortcut the user wants, but I will look into it. I'm happy to add anything anyone wants, but dialer codes were blocked several Android releases ago. I need the actual name of the shortcut (using one of those apps is the best way to find that). 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted August 14, 2023 Author Share Posted August 14, 2023 A new SCP beta is rolling out now! The most notable addition is 5G-NR Timing Advance (TA) display on compatible Android 14 devices. It is not displaying on the latest Android 14 Beta release on my Pixel 7, but when the functionality is added, the values should appear in the app. It will probably take some time before it is displayed on most devices. Beyond that, there are many bug fixes and improvements, including ongoing dual SIM improvements (slowly getting there!) and numerous changes in preparation for the upcoming launch of Android 14. Full changelog is available here as always, or inside the app. Look forward to feedback! 4 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted August 19, 2023 Author Share Posted August 19, 2023 Another SCP beta is rolling out now. It includes more bugfixes for web uploads and Android 14 hiccups. Thanks for your support! 2 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted August 21, 2023 Author Share Posted August 21, 2023 Another SCP update rolling out now.. beta-only for the moment, but pending any last-minute hiccups, the same version will roll out as a public release within a day or so. The only change for beta users is a minor bugfix related to the Recent Apps screen. Appreciate all the feedback! EDIT: Google Play pushed the public release out with the beta and there's no way for me to pause it.. hopefully all is well! 1 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted August 29, 2023 Author Share Posted August 29, 2023 A SCP beta update is rolling out now.. bugfix for Android 14 devices crashing when Location permission is not granted and the background service is enabled. Will roll out to the public soon as long as it proves to be stable. 3 Quote Link to comment Share on other sites More sharing options...
RAvirani Posted September 13, 2023 Share Posted September 13, 2023 It looks like Dish n66 is showing up as n1. I sent a diagnostic this past weekend. 2 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted September 13, 2023 Author Share Posted September 13, 2023 14 hours ago, RAvirani said: It looks like Dish n66 is showing up as n1. I sent a diagnostic this past weekend. Thanks, should be resolved in next update, which should be out today. Thankfully in July the Android development team reported that the 5G-NR band identification bug was finally resolved on Pixel devices, hopefully similar patches make it to other devices soon. 4 Quote Link to comment Share on other sites More sharing options...
PedroDaGr8 Posted September 13, 2023 Share Posted September 13, 2023 2 hours ago, mikejeep said: Thanks, should be resolved in next update, which should be out today. Thankfully in July the Android development team reported that the 5G-NR band identification bug was finally resolved on Pixel devices, hopefully similar patches make it to other devices soon. That's great news! 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted September 13, 2023 Author Share Posted September 13, 2023 A fresh SCP beta update is rolling out now.. includes bugfixes mostly targeting Android 14 and app stability, which is slowly improving. 3 Quote Link to comment Share on other sites More sharing options...
Trip Posted September 23, 2023 Share Posted September 23, 2023 Mike, Until yesterday, I hadn't locked my newest phone, the Moto Edge 2022, to an LTE band. I'd only ever used it on NR, where it works basically fine for logging purposes other than the modem reset issue I flagged in the thread I made on the Motorola forum, which is entirely unrelated to SCP. (For the record, it happened once yesterday about 25 minutes into our outing, and then not again the rest of the day.) I was out and about and had it looked to n41 and B41 for the first time, and encountered something new on it. Sometimes, when changing sectors or going in/out of service on the LTE side, where other phones would give bad GCIs with no TAC or something, this phone apparently flashes the previously-seen GCI/TAC but with an RSRP of -44 and an RSRP of -3. You can guess what this did to the log. I tried to screenshot it but it was too fast to catch; here's a picture of what the log looks like sorted by last_time: https://imgur.com/a/LBehfrW Much as I hate to ask you for another work-around, it would be nice have an option to be able to tell SCP not to log in that circumstance, much like how it has an option to not log when the TAC is missing. Separately, it also has a bad TA value that the checkbox only partially fixes. I'm going to do more investigation on that and see if I can figure out what the proper correction factor should be for this device. It may be necessary to consider providing multiple options for adjusting the TA. That said, I can already tell that won't completely help as it shows 0 TA a lot longer than my other devices do. I'm almost wondering if it's off by a constant rather than a coefficient, if that makes sense; I'll follow up on this after some investigation. - Trip 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted September 23, 2023 Author Share Posted September 23, 2023 17 minutes ago, Trip said: Sometimes, when changing sectors or going in/out of service on the LTE side, where other phones would give bad GCIs with no TAC or something, this phone apparently flashes the previously-seen GCI/TAC but with an RSRP of -44 and an RSRP of -3. You can guess what this did to the log. I tried to screenshot it but it was too fast to catch; here's a picture of what the log looks like sorted by last_time: https://imgur.com/a/LBehfrW Much as I hate to ask you for another work-around, it would be nice have an option to be able to tell SCP not to log in that circumstance, much like how it has an option to not log when the TAC is missing. Yuck! Obviously there's a bug with the phone itself, but I'll get on a workaround. Hopefully you can repair some of your bogus data.. that is annoying. If you haven't already, can you send a diagnostic from that phone with a reference to the bug? Doesn't have to be when it's happening, I just want to capture the device info. 17 minutes ago, Trip said: Separately, it also has a bad TA value that the checkbox only partially fixes. I'm going to do more investigation on that and see if I can figure out what the proper correction factor should be for this device. It may be necessary to consider providing multiple options for adjusting the TA. That said, I can already tell that won't completely help as it shows 0 TA a lot longer than my other devices do. I'm almost wondering if it's off by a constant rather than a coefficient, if that makes sense; I'll follow up on this after some investigation. Let me know what you find, happy to help however I can. 1 Quote Link to comment Share on other sites More sharing options...
Trip Posted September 23, 2023 Share Posted September 23, 2023 13 minutes ago, mikejeep said: Yuck! Obviously there's a bug with the phone itself, but I'll get on a workaround. Hopefully you can repair some of your bogus data.. that is annoying. If you haven't already, can you send a diagnostic from that phone with a reference to the bug? Doesn't have to be when it's happening, I just want to capture the device info. Let me know what you find, happy to help however I can. Done. I'll send you another later when it's actually connected. Bonus points if I can catch it at -44. And regarding the TA value, I will. Not sure I'll be able to investigate more before Monday, but as soon as I can I'll try to get you some data. - Trip 1 Quote Link to comment Share on other sites More sharing options...
Trip Posted September 23, 2023 Share Posted September 23, 2023 Mike, We ended up going out this morning to do errands in spite of the tropical storm. I locked the phone on LTE B41, turned off the TA correction checkbox, and watched it carefully while out and about. I have four screenshots for you. https://imgur.com/a/kCPTCnB First, I happened to get a screenshot of it doing the -44 dBm thing. I also tried to send you at least one set of diagnostics showing the -44 dBm but I don't know where precisely in the process it collects the diagnostics. Hopefully there's something useful in them. The rest of the screenshots are far more interesting. All three were taken within seconds of each other in the CVS parking lot. The phone's diagnostic screen shows a TA of 17, and oddly, the SCP diagnostics screenshot also appears to show a TA of 17. But SCP's normal display is showing 0. Not entirely sure what to make of that. It looks like SCP won't show me a value other than 0 until I hit about 19 according to the phone diagnostic screen. It also appears that when SCP is showing a TA of 1263, that's the equivalent of a null value for the TA--no TA is calculated. The phone diagnostic screen appears to show just "12" when that's happening; the SCP diagnostic screen shows 1282 in the TA section when that happens, a difference of 19, which is highly convenient given what I noted above about the TA value. (I can't test that the phone diagnostic screen is limited to two characters and is thus truncating 1282 to just "12" as I suspect given where I am right now. Had I known to be looking for it, I'd have tested in the middle of nowhere yesterday.) Anything catch your eye? Anything I can do to help more? - Trip 1 Quote Link to comment Share on other sites More sharing options...
mikejeep Posted September 23, 2023 Author Share Posted September 23, 2023 4 minutes ago, Trip said: First, I happened to get a screenshot of it doing the -44 dBm thing. I also tried to send you at least one set of diagnostics showing the -44 dBm but I don't know where precisely in the process it collects the diagnostics. Hopefully there's something useful in them. I received the reports, thanks! You didn't catch it happening (it captures the diagnostics as soon as you hit send or long-click the connection banner on the main screen), and I had sent you an e-mail to clarify which value was -3.. but your screenshots confirmed my hunch that you meant RSRQ! 4 minutes ago, Trip said: The phone's diagnostic screen shows a TA of 17, and oddly, the SCP diagnostics screenshot also appears to show a TA of 17. But SCP's normal display is showing 0. Not entirely sure what to make of that. It looks like SCP won't show me a value other than 0 until I hit about 19 according to the phone diagnostic screen. It also appears that when SCP is showing a TA of 1263, that's the equivalent of a null value for the TA--no TA is calculated. The phone diagnostic screen appears to show just "12" when that's happening; the SCP diagnostic screen shows 1282 in the TA section when that happens, a difference of 19, which is highly convenient given what I noted above about the TA value. I know exactly what is happening here. Somewhere along the way, I learned that TD-LTE bands (33-53) needed a TA correction of -19 applied, and I confirmed it on several devices. Perhaps that is no longer universally true.. but what you're seeing SCP display matches that correction. Below 19 you see nothing, at 19 you see 0, and above that you see TA-19. The upper limit is 1282, which is why you see 1263. Your phone must report 1282 when the TA is unknown, which is not technically safe but I can work around that. Funny enough, I had a change to TA coming in the next update that had nothing to do with your issues.. TA:0 will be hidden moving forward, since several devices report 0 when it cannot be identified. I'll have an app update out shortly that addresses all of this, let me know how it works for you and thanks for the detailed feedback! 1 Quote Link to comment Share on other sites More sharing options...
Trip Posted September 23, 2023 Share Posted September 23, 2023 4 minutes ago, mikejeep said: I received the reports, thanks! You didn't catch it happening (it captures the diagnostics as soon as you hit send or long-click the connection banner on the main screen), and I had sent you an e-mail to clarify which value was -3.. but your screenshots confirmed my hunch that you meant RSRQ! I know exactly what is happening here. Somewhere along the way, I learned that TD-LTE bands (33-53) needed a TA correction of -19 applied, and I confirmed it on several devices. Perhaps that is no longer universally true.. but what you're seeing SCP display matches that correction. Below 19 you see nothing, at 19 you see 0, and above that you see TA-19. The upper limit is 1282, which is why you see 1263. Your phone must report 1282 when the TA is unknown, which is not technically safe but I can work around that. Funny enough, I had a change to TA coming in the next update that had nothing to do with your issues.. TA:0 will be hidden moving forward, since several devices report 0 when it cannot be identified. I'll have an app update out shortly that addresses all of this, let me know how it works for you and thanks for the detailed feedback! In order: This is very helpful to know. Thanks. That makes a lot of sense, though it's showing me zero rather than nothing; it looks like if it's calculating a negative number, I'm seeing zero instead. It makes me wonder how many devices you've tested against which use the MediaTek chipset. This is only the second one I've used, and the first one was very, very old (didn't have B41), so it's possible that the MediaTek chip doesn't need the correction while others do. Separately, I doubt that a real world case will ever see 1282, so I imagine any value above 1281 could be ignored. I would ask you to please not hide TA values of 0, or if you hide them by default, add an option to not hide them. I am aware that, for example, the S22 doesn't report a valid TA value and always reports zero, but zero is a legitimate value and is useful to know when trying to identify sites. I'll look forward to your impending update, and I'm going to send along another donation if I can find the link. Thanks so much, as always! - Trip 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.