Motorola
This is the forum section where we discuss current and upcoming Motorola smartphones of interest to S4GRU members.
61 topics in this forum
-
- 4 replies
- 155 views
-
- 1 reply
- 481 views
-
- 0 replies
- 292 views
-
- 3 replies
- 808 views
-
- 8 replies
- 1.6k views
-
- 6 replies
- 1.5k views
-
- 0 replies
- 653 views
-
- 2 replies
- 938 views
-
- 48 replies
- 3.3k views
-
- 12 replies
- 2.3k views
-
- 885 replies
- 55.3k views
-
- 10 replies
- 1.3k views
-
- 0 replies
- 971 views
-
- 23 replies
- 4.6k views
-
- 339 replies
- 25.3k views
-
- 44 replies
- 5.1k views
-
- 3 replies
- 2.5k views
-
- 6 replies
- 1.6k views
-
- 28 replies
- 7.9k views
-
- 246 replies
- 24.5k views
-
- 76 replies
- 10.7k views
-
- 16 replies
- 5.8k views
-
- 1 reply
- 1.4k views
-
- 22 replies
- 4.2k views
-
- 16 replies
- 2k views
-
-
New Topics
-
-
Recent Posts
-
Just installed the update, and it's good! As you recommended, I turned off both TA adjustments, and turned on displaying it when it's zero. The value is basically spot-on. It's bouncing between 18 and 19 for the Cameron Valley site, and it is in fact between 0.87 and 0.92 miles, as displayed in the app. This is probably a better estimate of the TA values than any other device I own provides. As far as the -44 goes, I'll have to take it out and verify that it no longer records those cases. If this device didn't have that annoying reset problem, and got the Android 14 update (and in so doing supported TA on NR and continued to allow band locking), it would easily be the best device I own. Easily. And would be the device I standardize on for the 5G era. I'll probably have to wait for a future device to come out with Android 14 and then see what happens. And I know I didn't have to, but I love SCP. It is my primary tool for tracking the goings-on of the various networks and is very easy to use and work with across my 10 phones. I am very happy to send a token of my appreciation your way now and then. Thanks again! - Trip -
Sorry, I misread your message -- yes, the app would show 0 if an invalid value was being reported. I don't think I had any MediaTek devices myself, but the beta testers have had a decent variety of devices over the years. Sorry, I didn't word that very well in my last post -- I added an option to control display of LTE TA when it is 0. By default it will now be hidden (sadly a lot of devices do not show it) but anyone who wants to display it can adjust accordingly. There will be 3 user-selectable options related to LTE TA now -- the existing correction option, correction on LTE-TDD (which is independent/in addition to the existing correction option), and TA:0 display. In your case, I'd disable the TDD option and enable the TA:0 option; the defaults will be the opposite of what I think you need. You did not have to do that, but I sincerely appreciate it, thank you! Beta update is rolling out now, let me know how it goes. -
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
-
-
Recently Browsing
- No registered users viewing this page.
