[Announce] Cellnet-Info for N900 - Page 5 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 3 hrs, 49 mins ago
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 2 days ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 12 hrs ago
n770 youtube video (0)
to General by nmdv - 6 days, 11 hrs ago
more...

Page 5 of 9

Thread Tools

ade	2013-12-14 , 15:35
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#41

Originally Posted by Estel

My provider does supply network time, so I'll test it and report back as soon as autobuilder chew new version of cellnet-info (no update available here, yet).

No problem, I was suggesting, only Just keep in mind that current values are really misleading, and your tests confirmed it - stating CSQ 17 as 100% signal is laughable, to say at least (of course it's not your fault, bullet at Nokia[?]).

In case you would like to fix it *without* query'ing CSQ from modem (which gives a little strange replies, anyway), I've prepared a simple algo to calculate CSQ from dBm (which you have access to, already). It is cellular variant, the most commonly used one (at least in cellular network communities):
Code:
CSQ 0 = 113dBm
CSQ 1 = 111dBm
....
CSQ X = 113-(X*2) [dBm]
Then, remaining thing to get % values is to assign percents to corresponding values (CSQ 32 = 100%, CSQ 16 = 50%, CSQ 0 = 0%, etc) and in-between things.

Thinking about that, you may skip calculating CSQ entirely - just check lowest and highest dBm values from algo above, and assign percents, from best to worst.

/Estel

I will see what I can do with this info.

And yes, version 0.0.1-8 is still not downloadable from extras-devel. Perhaps cron schedule time intervals from the autobuilder have changed, as lately it takes longer that it used to

Quote & Reply |

The Following 2 Users Say Thank You to ade For This Useful Post:
Estel, sixwheeledbeast

ade	2013-12-14 , 16:10
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#42

Originally Posted by ade

I will see what I can do with this info.

And yes, version 0.0.1-8 is still not downloadable from extras-devel. Perhaps cron schedule time intervals from the autobuilder have changed, as lately it takes longer that it used to

Edit: it is available now in extras-devel

Quote & Reply |

The Following 2 Users Say Thank You to ade For This Useful Post:
Estel, handaxe

	pichlo	2013-12-14 , 20:03
	Posts: 6,447 \| Thanked: 20,981 times \| Joined on Sep 2012 @ UK	#43

Originally Posted by Estel

Just keep in mind that current values are really misleading, and your tests confirmed it - stating CSQ 17 as 100% signal is laughable, to say at least (of course it's not your fault, bullet at Nokia[?]).

I wouldn't be so harsh. There may well be a reason for the current allocation. For example, the signal level is measured not in absolute strenght but in reliabiliy - and CSQ 17 is plenty to provide 100%. Just a speculation (I don't even know what CSQ is

), but it might be a good explanation for why it kept jumping from 48% to 72% and anywhere in between while I was typing this missive - all the while the dBm value stayed fixed at 92 (edit: now it jumped to 100%, 82 dBm. Go figure).

I would vote for keeing the current info as it is as it matches what people see in the bar meter. Perhaps, to keep Estel happy, find a way to provide both but keep the current number.

Originally Posted by ade

Remarks/questions:
My operator does not supply network time AFAIK, so can anyone who does receive this, check if a (valid) time is displayed using "Provider info"?

No network time for me either

My primary device has 112/911/999 as emergency numbers, while my backup device shows 112/911/118/119/000/110/999/08. Can't relate it to regional or device settings. Any clue why they differ? Only difference is that my backup device has no SIM card, perhaps that's the cause.

112/911/999 here. Possibly related to the SIM (my device has one). Although I've never tried if 911 works here (and have no intention to try). 112 and 999 do.

opencellid.org is giving me issues retrieving cellinfo (failed to lookup cellid). Most likely opencellid.org related. This version should deal with that without errors, and you can always disable the internet lookup. So far, I have not heard they have changed their API.

I am happy to report that the location was fixed for me. It used to pin me some 13 km from the actual location, now it is within the same street.

Quote & Reply |

The Following 3 Users Say Thank You to pichlo For This Useful Post:
ade, Estel, peterleinchen

	pichlo	2013-12-14 , 21:46
	Posts: 6,447 \| Thanked: 20,981 times \| Joined on Sep 2012 @ UK	#44

Emergency numbers are definitely related to the SIM. Just took mine out and got the long list including 08. I wonder where that one is used.

Quote & Reply |

The Following 3 Users Say Thank You to pichlo For This Useful Post:
ade, Estel, sixwheeledbeast

ade	2013-12-14 , 22:56
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#45

Originally Posted by pichlo

Emergency numbers are definitely related to the SIM. Just took mine out and got the long list including 08. I wonder where that one is used.

Thanks for testing. Did a bit of search on the web on that. Without a SIM, these numbers should be reachable. With a SIM, it is narrowed down to relevant numbers. I see 08 mentioned twice in http://en.wikipedia.org/wiki/Emergency_telephone_number, so it is not very common.

Quote & Reply |

The Following 3 Users Say Thank You to ade For This Useful Post:
Estel, misiak, pichlo

	Estel	2013-12-15 , 05:53
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#46

I've tried to check network time option, but "Provider" tab doesn't work for me, *at all*. "Loading" circle spins indefinitely (left it for 15 minutes), and only way to stop it is closing the application (although, via normal X, not killing from Maemo or terminal). After trying "Provider" tab, other tabs are non-responding, until restart of cellnet-info.

If I don't touch "Provider", everything else works OK - emergency numbers with SIM inserted seems approriate for my location.

Originally Posted by pichlo

I would vote for keeing the current info as it is as it matches what people see in the bar meter. Perhaps, to keep Estel happy, find a way to provide both but keep the current number.

I don't think that keeping me happy is worth changes to cellnet-info

If it would be for me only, I can calculate ~signal power from -dBm. Hoever, I think that some more meaningful readings could be useful for people trying to get better signal in worse reception areas (via antenna coupleing-adaptors now, or via external antenna after repl. body gets finished), or for general cellular signal troubleshooting.

As you said, the "Nokian" signal strength is already visible via bars on status menu, thus I don't see much reason to clone them in cellnet-info - while "objective" signal strength isn't available anywhere, unless someone calculate dBm in own head. But, maybe it's only me, so I'm not pushing it by any means.
---

The thing about "Nokians" signal strength % fluctuating during same -dBm value bugges me, though - may it be only about different refresh intervals, so they don't "meet" on screen? Or their signal level meter have access to some other reports from modem, about signal quality (!= strength, at least not directly)? If the latter, I wonder, if we can access it too, directly?

Indeed, there is a different "meter" for signal quality, next to signal strength, in most community software for cellular modems. It is queried by different AT comand, normally, and shouldn't be merged with overall "signal strength" %, as those two values are more useful as separate entities - it helps nailing down antennae issues or filtering in noisy enviromnents. But I doubted that we can read it in N900, up to date.

/Estel

__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!

Quote & Reply |

The Following User Says Thank You to Estel For This Useful Post:
ade

ade	2013-12-15 , 09:46
Posts: 1,100 \| Thanked: 2,797 times \| Joined on Apr 2011 @ Netherlands	#47

The reply should take about 17 seconds, so there is something wrong. Maybe it is the networktime that I could not test.

Could you start cellnet-info using:
/opt/cellnet-info/cellnet-info

from the terminal and see if any error messages are generated?

Quote & Reply |

The Following User Says Thank You to ade For This Useful Post:
Estel

sixwheeledbeast	2013-12-15 , 12:57
Posts: 2,290 \| Thanked: 4,134 times \| Joined on Apr 2010 @ UK	#48

Originally Posted by ade

The reply should take about 17 seconds, so there is something wrong.

I am having Provider button issues too.

https://www.privatepaste.com/b991906197

__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -

Before posting or starting a thread please try this.

Quote & Reply |

The Following 2 Users Say Thank You to sixwheeledbeast For This Useful Post:
ade, Estel

	Estel	2013-12-15 , 14:19
	Posts: 5,028 \| Thanked: 8,613 times \| Joined on Mar 2011	#49

I got exactly same output as sixwheeledbeast's, it appears something like ten seconds after pressing button.

Sorry forf not providing log 1st time - something must have clouded my mind

/Estel

Quote & Reply |

	pichlo	2013-12-15 , 15:09
	Posts: 6,447 \| Thanked: 20,981 times \| Joined on Sep 2012 @ UK	#50

Looks quite straightforward. Can one of you try wrapping yy, mm, etc on line 508 in /opt/cellnet-info/cellnet-info with str(), like this:

Code:

networktimeVal = str(yy)+"/"+str(mm)+"/"+str(dd)+" "+str(hh)+":"+str(mm)+":"+str(ss)

I would have tried it myself excxept it's pointless since my network does not provide the time.

Ade, sorry for meddling

Quote & Reply |

The Following 2 Users Say Thank You to pichlo For This Useful Post:
Estel, sixwheeledbeast

Page 5 of 9

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)

The N900 is now 15 years old! (6)

F(x)tec Pro1x (QWERTY) for sale (0)

n770 youtube video (0)

Notices