Develop Bugs

[Q] Problem with #NCSIG# and #NCSIGN# on SGS3/Sprint

I have Zooper Widget Pro on my rooted/modded (CM 10.2.0-d2spr) Sprint Samsung Galaxy S3. I've noticed that when I'm on anything other than 4G/LTE, I get sensible values for #NCSIG# and #NCSIGN#. However, when my phone connects to an LTE tower, #NCSIG# jumps to/stays at 99, and #NCSIGN# jumps to/stays at 85 (positive, not negative).
Is there a reason for this, and any fix/workaround? I'm trying to use it to display a progress bar, but when the numbers go wonky like that it's not very helpful. Since my office and home both have varying degrees of LTE coverage, I usually end up with a useless progress bar most of the time
Thanks!

I have similar issues on VZW. NSIG is always 99 and NCSIGN is always 85.....Works for a short time after a reboot but eventually goes back to this.
VZW GNEX 4.22

A.L.2009 said:
I have similar issues on VZW. NSIG is always 99 and NCSIGN is always 85.....Works for a short time after a reboot but eventually goes back to this.
VZW GNEX 4.22
Click to expand...
Click to collapse
A.L.2009, what ROM are you running? Try turning off LTE (Settings > Wireless & Networks > More... > Mobile Networks > Network Mode) and select one similar to "CDMA/EvDo auto" (or another one that mentions CDMA but not LTE). If you get more sensible numbers after turning that off, then it's likely a problem with LTE specifically... if not, then I'm stumped
To the devs: I'd be willing to help debug this if you have any special tools to do so

Thanks..tried switching from LTE to CDMA, same problem.
Im running stock/rooted 4.2.2

Not sure if this is your issue but this is how I set up my WiFi and Cell progress bars:
For WiFi progress bar, under the 'Edit Progress Min/Max/Value' setting I have the Min set at 0, value is #NWSIG# and Max is set to 9.
For Cell progress bar, under the 'Edit Progress Min/Max/Value' setting I have the Min set at 0, value is #NCSIG# and Max is set to 31.
The reasoning is that the zooper fields for NWSIG field has values between 0 and 9 while NCSIG has values betwen 0 and 31. NCSIG also shows ASU as a value, but I have no idea what that is. Setting the max value to these settings makes the progress bar seem more usable to me than a setting of 0 to 100.

nukedawg said:
Not sure if this is your issue but this is how I set up my WiFi and Cell progress bars:
Click to expand...
Click to collapse
The progress bars work just fine on any other network (1x, 3g, ehrpd), but when the phone connects to 4g/LTE, the numbers go wonky. I get the feeling this is a CDMA-specific issue, since I'm on Sprint and A.L.2009 is on Verizon. I imagine if it occurred on GSM networks too, it would've gotten more attention by now.

I just posted about this in a thread and a wonderful themer kwerdenker pointed me here Android Source CellSignalStrengthCdma you will have to use #NCSIGN# as for the progress bar code it will look like this or at least its what i did...
Code:
min = $#NCELL#=Sprint?-100:0$ value $#NCELL#=Sprint?#NCSIGN#*-1:#NCSIG#$ max $#NCELL#=Sprint?-75:31$
That code should allow for either DBM (Sprint) or ASU (GSM) i did it on my nexus 5...hope that helps

BlueDrgBlade said:
I just posted about this in a thread and a wonderful themer kwerdenker pointed me here Android Source CellSignalStrengthCdma you will have to use #NCSIGN# as for the progress bar code it will look like this or at least its what i did...
Code:
min = $#NCELL#=Sprint?-100:0$ value $#NCELL#=Sprint?#NCSIGN#*-1:#NCSIG#$ max $#NCELL#=Sprint?-75:31$
That code should allow for either DBM (Sprint) or ASU (GSM) i did it on my nexus 5...hope that helps
Click to expand...
Click to collapse
Yeah, that source code highlights the problem:
Get the LTE signal level as an asu value between 0..97, 99 is unknown
Click to expand...
Click to collapse
Whenever I'm connected to LTE, the value comes up "99".

That's what I get also on my n5...I just gave up on the asu for CDMA for that reason. I'm sure someone a lot smarter than I has a way but I haven't figured it out yet.. Sorry

Yeah... I can't use dbm either, because it's supposed to be a negative value, but when I connect to LTE it goes to +85

Doktor Jones said:
Yeah... I can't use dbm either, because it's supposed to be a negative value, but when I connect to LTE it goes to +85
Click to expand...
Click to collapse
If you use the code i posted it will allow for a progress part to work....you have to basically make it negative. I saw the positive on my LTE on my N5 and that is how i got it to work with a progress bar. However i didn't check to see what the regular signal for voice would show up as...if that is already negative i will make modifications to my code and post it...going to check that right now.
EDIT: I just tested it and voice goes to a negative number so i will make changes to the code and re-post for you guys.
---------- Post added at 12:43 PM ---------- Previous post was at 12:18 PM ----------
Okay i got the new code for the value section on a progress bar that will allow for the change...my N5 only connects to LTE unless i need to make or get a call then it switches networks from Data to Voice network and thus why i didn't think about the issue you just brought up...
here's the code hope this helps....
Code:
$#NCELL#=Sprint && #NCSIGN#>-1?(#NCSIGN#*-1):#NCSIGN#$ $#NCELL#!=Sprint?#NCSIG#$

BlueDrgBlade said:
If you use the code i posted it will allow for a progress part to work....you have to basically make it negative. I saw the positive on my LTE on my N5 and that is how i got it to work with a progress bar. However i didn't check to see what the regular signal for voice would show up as...if that is already negative i will make modifications to my code and post it...going to check that right now.
Click to expand...
Click to collapse
That doesn't actually solve the problem; normally (1x, 3G, EHRPD) the values are already negative, ranging from -125 to about -60 (theoretically it could go much higher, but -62 is the best I've ever seen, standing within ~100yd of a tower with LOS). If I just use some math magic to make the invert the positive, it still doesn't resolve the fact that the 85 is an entirely invalid value. However, doing some more Googling, it looks more like it might be a ROM-related issue with Sprint LTE; in other words, ZW gets bad data, and just merrily runs along with it.

Doktor Jones said:
That doesn't actually solve the problem; normally (1x, 3G, EHRPD) the values are already negative, ranging from -125 to about -60 (theoretically it could go much higher, but -62 is the best I've ever seen, standing within ~100yd of a tower with LOS). If I just use some math magic to make the invert the positive, it still doesn't resolve the fact that the 85 is an entirely invalid value. However, doing some more Googling, it looks more like it might be a ROM-related issue with Sprint LTE; in other words, ZW gets bad data, and just merrily runs along with it.
Click to expand...
Click to collapse
I noticed that looking over more of the source code for android...but my last code post above should allow for this goof up in the system.

I have a similar issue with my Droid Turbo on VZW. ASU comes up as -3, but dBm comes up as around -119, which is not my real signal strength. It's breaking one of the indicators on my shiny new widget.

Tmobile Signal Acuracy

are the signal bars actually accurately reflect the signals strength? reason why i am asking is because i literally get 0 bars at home, yet data works and i can still surf the web and watch videos.
Sent from my SM-N900T using XDA Premium 4 mobile app

JoshuaFCB said:
are the signal bars actually accurately reflect the signals strength? reason why i am asking is because i literally get 0 bars at home, yet data works and i can still surf the web and watch videos.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
those bars are not indication of strength (not all the time)
this is a very iffy conversation some will say yes some will say no. me personally when i have 1 or 0 bars i have a bad connection with data/voice. when i have max bars there is no issue whatsoever. but you need to look at the dBm meter that is more accurate. and just self observation of itself it may vary in the place you are too. in my house with 1 bar on LTE I get 20Mb/s Down 5Mb/s Up. And at work I have 3 Bars and only reach 10Mb/s Down and 2MB/s Up. however my voice coverage wherever I been has been spot on.

I have one bar at home, just did the speed test: 16Mb down, 6Mb up. If you dial *#0011# you'll see your RSRP exactly (reference signal receiving power), mine shows about -105.
If calibration was done properly it should be something like this:
0 bar - 0- 20%
1 bar 20-40
2 bar 40-60
3 bar 60-80
4 bar 80-100%
So even at 0 bars you could have OK reception.
But there is more to it, you can have strong signal, but also strong interference and a lot of other users could jam up otherwise strong connection.
To be honest I'd much rather have zero bars and still connecting, than phone lying to me that I have good signal and not able to connect.

I have one bar at home also, which is about -110db for me. Speed test shows 5 down and 2.4 up then went into network communications issues.

[Q] Zooper Issue: dBm/ASU seems to be stuck

I have a widget which includes a cell signal strength progress bar. It worked fine initially, but now it seems to be "frozen". No matter how my signal strength changes, I get the same reading from zooper for dBm and ASU. It is stuck on -125 dBm and -6ASU (which is not correct for ASU anyway). Any idea on how to fix this? I think this happened after I went through an area that switched from 4G to 3G, and then back to 4G, but whatever the case, the zooper reading is not changing at all now from the above numbers.
update - Tasker seems to work, so that is what I am using for now. Possibly this is bug in Zooper similar to what some others have seen, although my numbers are different. It is strange however that it worked to start with.....

Cell and wifi signal strength bars

I'm new to Zooper, but have learned a lot since messing around with it. I found some icon sets with battery, wifi, and cell strength bars. The battery scalable icon set works perfectly, surprisingly. It shows accurate battery status with no advanced parameters at all?!? The wifi and cell strength sets are not as cooperative. I have tried adding in the #NWSIG# and #NCSIG# tags in the advanced parameters field, but no luck.
Can someone help me understand why the battery icon set would work and the others don't. And then, is there a way to get the wifi and cell strength scalable icon sets to properly display the signal strength?

ok, this is annoying as hell. There has to be a way to do this. With all the skins and icon sets out there, I can't believe that there isn't a way. How does the battery set work?

Control cellular network switching thresholds

As it is well known there are preset thresholds on each device to drop to the lower type of network. For example, if there is less than -125 dBm on 4G/LTE it will drop to 3G, and it the 3G signal goes to lower than -125 dBm it will drop to 2G. I know how to lock in one network through the hidden phone info menu, but I would like to know how can I edit these settings/thresholds on the Pixel 2XL. I'm guessing the values are in the radio image, but how do I actually manipulate them?
The reason being that I work in remote locations and I would like it not to switch to the slower network unless it goes to a lower value than the preset ones.
Would really appreciate anyone pointing me in the right direction.