![]() |
Re: [Announce] Cellnet-Info for N900
Quote:
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 :) |
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
Quote:
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. Quote:
Quote:
Quote:
|
Re: [Announce] Cellnet-Info for N900
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.
|
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
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. Quote:
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 |
Re: [Announce] Cellnet-Info for N900
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? |
Re: [Announce] Cellnet-Info for N900
Quote:
https://www.privatepaste.com/b991906197 |
Re: [Announce] Cellnet-Info for N900
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 :rolleyes: /Estel |
Re: [Announce] Cellnet-Info for N900
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) Ade, sorry for meddling ;) |
Re: [Announce] Cellnet-Info for N900
Stupid mistake of course :)
Just uploaded version: 0.0.1-9 to extras-devel. Changes: * added signal strength % based on max -50dBm * fixed bug in display of networktime Should be downloadable within a few hours. |
Re: [Announce] Cellnet-Info for N900
Providcer tab does work now, and network time half-work - date, hours and seconds are OK, but minutes are not.
For example, at 9:54:36 local time, network time shows 8:12:36. Suprisingly, at 9:56:48 local time, it is 8:12:48. As you notice, seconds switch OK, but minutes are stuck. Hours are either stuck too, or (as I suspect) presented as UTC (I'll check after 10 AM, if it changes to 9 AM network time). I have NFC how network time protocol works, but for me, it always update device time correctly (including minutes, so I suspect some hiccup in displaying it). Cheers, /Estel |
Re: [Announce] Cellnet-Info for N900
Quote:
Edit: Version 0.0.1-10 in extras-devel: * introduced use of secondary theme color * fixed minutes in networktime |
Re: [Announce] Cellnet-Info for N900
0.0.1-10
Code:
Error calling slot "cellinfoButtonPressed" Seems to only happen with "Access Internet enabled" |
Re: [Announce] Cellnet-Info for N900
I got the same:
Code:
~ $ /opt/cellnet-info/cellnet-info |
Re: [Announce] Cellnet-Info for N900
Me too :)
Looking at the error it is opencellid.org that is responding with unrecognized answers. I will see what they are, and handle unusable answers in a way that is does not give errors on the background. Edit: The response of opencellid.org seems to be correct again. Changelog 0.0.1.11: * better error handling when receiving invalid coordinates |
Re: [Announce] Cellnet-Info for N900
What's the assertion failure at the very beginning? Can it be ignored?
|
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
Is there a reason for having different loading indicators?
Mobile Networks has a nice maemo style loading bar dialog but Operator Info has an odd swirly browser style loading icon. Just wondering, why? |
Re: [Announce] Cellnet-Info for N900
Quote:
By creating a simple test program, I can make it work. But as soon as I call it from another place than the mainwindow class, it does not work anymore. So I looked for alternatives. |
Re: [Announce] Cellnet-Info for N900
Not keen on google's formatting for Location information compared with opencellid's.
Is there anyway to use a different service or make the services optional? |
Re: [Announce] Cellnet-Info for N900
Quote:
As noted in the latest changelog, openCellID no longer accepts a dummy api key for location information retrieval. I am not sure if they provide developer/application keys, so users should probably have to register themselves to obtain a key. That could be implemented, but the most easy/user friendly way was to switch to a service without mandatory api key. That was google in this case. But this switch should not have affected the formatting of the location information, as this part has not changed. The coordinates are no longer obtained from openCellID, but the location text is (and was) always retrieved from google, as openCellID does not have this info. Do note that the location information is always kinda random, meaning it can be just a postal location, or a more precise point (street). Don't know if google made some changes there. |
Re: [Announce] Cellnet-Info for N900
Quote:
It didn't include the "UK administrative area" before the switch and it does now. I find UK administrative areas annoying and pointless, it also means the Location string is so long it goes off screen. Anyway I thought I'd ask, I wasn't sure if there was another FOSS service or a way we could get our own API key for opencellid. |
Re: [Announce] Cellnet-Info for N900
Quote:
The site mentions maemo but has no apps listed. |
Re: [Announce] Cellnet-Info for N900
New version in extras-devel (0.0.1-13).
Changes: Code:
* added settings screen To save a few bytes, you can remove the old config file (/home/user/.config/cellnet-info/cellnet-info.cfg) if it is an upgrade. |
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
Seem to be having trouble since the last update.
Current Cellular Info hangs for ~20 sec before the banner message "no info or incorrect api key." Can't seem to get Google working either. pastebin.com/x4FiR7QL It seems OpenCellID will register any information without validating it and issue a API key, so is there a reason the application can't use one key for everyone? |
Re: [Announce] Cellnet-Info for N900
Quote:
Quote:
|
Re: [Announce] Cellnet-Info for N900
Quote:
I'll keep an eye on it for now. Quote:
|
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
One problem:
Today while cheking my sim data, i checked the ICCID and i discovered that cellnet-info fails reading it in a "funny" way. It swaps every pair of numbers! Example: iccid printed on the sim: 1234567890 cellnet-info reported iccid: 2143658709 if you plan to make a number portability request and you need the iccid....pay attention! |
Re: [Announce] Cellnet-Info for N900
Quote:
What kind of refurbished chinese SIM card are you using :D ? As I have no device left with a sim card, I can't test/confirm this. cellnet-info should do (a python equivalent of): Code:
dbus-send --system --type=method_call --print-reply --dest=com.nokia.phone.SSC /com/nokia/phone/SSC com.nokia.phone.SSC.get_iccid |
Re: [Announce] Cellnet-Info for N900
@ade
Thanks! :) Nah, a good sim that i'm using without problems since 8 years. Anyway it seems that also dbus-send request produces the same wrong result. Then, AT+ICCID gives only ERROR... No idea if there are other ways. Sorry, for my previous post, it's clear that is not a problem with your app. Anyway, it could be a warning for others to doublecheck the info returned by the N900. |
Re: [Announce] Cellnet-Info for N900
Quote:
|
Re: [Announce] Cellnet-Info for N900
Well, the iccid should be 18 digits long
In my device and sim the iccid appears to be long 20 digits where the first 18 digits are swapped pairs and at the end there is a "F0" that doesn't exist anywhere. Checking this: http://www.forensicswiki.org/wiki/SIM_Cards should be easy to guess when the results is completely wrong. Maybe something like if first 2 digits are 98 instead of 89 (every iccid should start with 89) swap all digit pairs and cut after 18. Anyway, yes we need other checks and confirmations, i have no idea if it's just my device behaving in that way. Then |
Re: [Announce] Cellnet-Info for N900
My ICCID is 20 digits long and starts with 35 (ending with 86) :eek:
Cellnet-info and dbus give the same output. So it is not only your device but all... That puzzled me during a walk. But I found no matching swap. packed BCD, binary representation or whatever that would explain my numbers! ICCID may be 18/19/20 (even 22) digits. But should always start with 89 for GSM SIMs. Followed by the calling code of issuer country (e.g. Germany 49, England 44, America 1, Slovakia 421, ...) http://en.wikipedia.org/ICCID#ICCID http://en.wikipedia.org/Binary-coded-decimal http://en.wikipedia.org/ISO/IEC_7812 So another mysterium of our beloved gem. (btw.: my N9 spits out a 19 digit ICCID starting with 89 followed by calling code of 49, so absolutely correct. I may test my N900 with similar SIM as of N9 but only in a few days/weeks.) |
Re: [Announce] Cellnet-Info for N900
I just inserted a decatived sim card, but I can still use it for ICCID queries it turns out.
It has the last 8 digits engraved. And those are indeed swapped as Xes described. And it is ending with "f8". The country code etc. are also reversed. So in my case I could "fix" it by swapping the number pairs and removing the last two characters. @peterleinchen: are you sure you do not have the same number swap issue? |
Re: [Announce] Cellnet-Info for N900
For me cellnet-info cannot start I am getting a segmentation fault.
With dbus I get a twisted pair ICCID 20 digits long starting with 9894... I will look if qt mobility can read out this information. |
Re: [Announce] Cellnet-Info for N900
Yup swapped here too, both cellnet-info and dbus.... with the f6 termination.
|
Re: [Announce] Cellnet-Info for N900
Thanks for all the responses.
Just uploaded version 0.0.1-14 (can take a while before available). It swaps the number pairs and removes the "f". I still needed the number behind the "f" as last number. Let me know how it looks after the update. |
All times are GMT. The time now is 04:57. |
vBulletin® Version 3.8.8