| Wizzup | arno11: ok, got it booted | 02:41 |
|---|---|---|
| Wizzup | will continue tomorrow | 02:41 |
| freemangordon | sicelo: do you have any idea if ofono supports both operator name and alternative operator name | 09:31 |
| freemangordon | I remember you said something about those two | 09:31 |
| freemangordon | Wizzup: simlock means there is at least one locked PIN, right? | 09:47 |
| freemangordon | or? | 09:47 |
| freemangordon | oh, no | 09:47 |
| freemangordon | it means phone is locked to carrier | 09:48 |
| freemangordon | so that should be a modem property in ofono terms, no? | 09:48 |
| sicelo | freemangordon: it reports just one name. This name can have a 2nd name embedded.. e.g. "opername (alt)" | 10:17 |
| freemangordon | yes, this alt name | 10:17 |
| freemangordon | is it processed? | 10:17 |
| sicelo | Yes, but as mentioned there's only one interface to get a name | 10:18 |
| sicelo | Why do you ask btw | 10:18 |
| freemangordon | because I am rewriting conn-ui | 10:19 |
| freemangordon | and it has support for alt name | 10:19 |
| freemangordon | so I wonder shall I drop it | 10:19 |
| freemangordon | given that ofono does not support it | 10:20 |
| freemangordon | so, if this alt name is not used/stored/accessible on ofofno | 10:20 |
| freemangordon | there is no point connui-cell to support alt name as well | 10:21 |
| sicelo | Ok. | 10:22 |
| sicelo | As long as you're showing name ... if it has an alt, it will show | 10:22 |
| Wizzup | I think I did get the showing of the names correct btw in the current code | 10:23 |
| sicelo | I guess in connui (i don't have a chance to look now) was trying to get the alt by looking inside the brackets? | 10:23 |
| Wizzup | no, they are separate | 10:24 |
| freemangordon | :nod: | 10:24 |
| sicelo | Oh, so it's the name embedded in sim? | 10:24 |
| freemangordon | dunno | 10:24 |
| freemangordon | but as you said ' can have a 2nd name embedded.. e.g. "opername (alt)"' | 10:24 |
| sicelo | Where's connui looking for the alt? | 10:25 |
| freemangordon | that's operator, not sim issuer | 10:25 |
| freemangordon | on fremantle it comes from the blobns | 10:25 |
| freemangordon | *blobs | 10:25 |
| freemangordon | in leste, it currently comes from nowhere and is not useerd | 10:25 |
| freemangordon | *used | 10:25 |
| sicelo | Ok. | 10:26 |
| freemangordon | thus my question - does ofono support it | 10:26 |
| freemangordon | if not, I'll drop as well | 10:26 |
| sicelo | In simple terms, no. There's only one name | 10:26 |
| freemangordon | ok, thanks | 10:27 |
| sicelo | Interesting the one about carrier lock. Not sure if it shows up in ofono | 10:28 |
| freemangordon | I *suspect* it shows up as various network pins required, like OFONO_SIMMGR_PIN_NETWORK | 10:34 |
| freemangordon | that's what I am going to implement - if any of those weird pins is required, assume sim is locked | 10:34 |
| freemangordon | umm... phone is loicked | 10:34 |
| sicelo | It's not a sim property | 10:36 |
| freemangordon | yes, but I was not able to find anything else | 10:36 |
| sicelo | So it's highly unlikely to show up as a required pin on that interface | 10:36 |
| sicelo | Maybe don't include it :-) | 10:36 |
| freemangordon | ok, but what is OFONO_SIMMGR_PIN_NETWORK? | 10:36 |
| Wizzup | that does sound like network lock | 10:37 |
| sicelo | Where's that in the ofono docs? | 10:37 |
| freemangordon | check PinRequired | 10:37 |
| freemangordon | https://github.com/maemo-leste-upstream-forks/ofono/blob/maemo-ofono/doc/sim-api.txt | 10:37 |
| freemangordon | besides "pin" and "puk", all others sound like netword/SP passwords to me | 10:38 |
| freemangordon | *network | 10:38 |
| freemangordon | "Phone-to-SIM PIN is required" | 10:38 |
| freemangordon | ? | 10:39 |
| sicelo | I'm not sure, but maybe it is :-) | 10:39 |
| freemangordon | so, until we hit an issue/example/#something, I will assume that if any of those pins is required, then we have a simlock | 10:39 |
| freemangordon | unless we have supported device with locked modem we can test that | 10:40 |
| freemangordon | at least I am not aware of any | 10:41 |
| sicelo | >> Wizzup: I think I did get the showing of the names correct btw in the current code ... yes, all seems to be working good lately | 10:41 |
| freemangordon | no worries, I will break it :p | 10:42 |
| freemangordon | I am implementing multiple modem support, along with major rewrite/cleanup | 10:42 |
| freemangordon | so no way everything to work as it should from the first try | 10:43 |
| sicelo | Allow me to add two items to your list | 10:45 |
| sicelo | 1. Improve handling for ModemRemoved signals. Sometimes d4 modem disappears. On ofono's dbus interface, the modem is gone, but on UI, network bars still show | 10:48 |
| freemangordon | ok, I think will be a side-effect anyways | 10:48 |
| sicelo | 2. Handle roaming indication. I could probably help with poor quality icons | 10:49 |
| sicelo | :-P | 10:49 |
| freemangordon | ah | 10:49 |
| freemangordon | we don't have that ion fremantle? | 10:49 |
| freemangordon | *in | 10:49 |
| sicelo | No | 10:49 |
| freemangordon | ok | 10:49 |
| freemangordon | makes sense | 10:50 |
| sicelo | We only don't do gprs when roaming | 10:50 |
| freemangordon | sicelo: any clue what PIN vs UPIN vs PIN2 is? | 10:51 |
| freemangordon | ah, seems upin is for usim | 10:53 |
| freemangordon | but, what is pin2? | 10:53 |
| sicelo | U* stuff is usually related to cdma/evdo networks | 10:54 |
| freemangordon | ok, so it seems this will appear in ofono as PIN | 10:55 |
| Wizzup | it is "pin2" in lib/sim.c I think | 10:55 |
| freemangordon | I am not convinced | 10:55 |
| freemangordon | because there *is* PIN2 | 10:55 |
| Wizzup | include/connui-cellular.h: SIM_SECURITY_CODE_PIN2 = 4, | 10:55 |
| freemangordon | which is related to security services | 10:55 |
| Wizzup | :q | 10:55 |
| Wizzup | I mapped this in lib/sim.c | 10:55 |
| Wizzup | in connui_cell_sim_verify_attempts_left | 10:55 |
| freemangordon | I know, but I think this is incorrect | 10:55 |
| Wizzup | they're both called pin2, but ok :D | 10:56 |
| Wizzup | good to check regardless | 10:56 |
| freemangordon | because I think imsi does not support pin2 | 10:56 |
| freemangordon | but supports upin | 10:56 |
| freemangordon | ah, it is supported | 10:56 |
| freemangordon | Wizzup: see https://pastebin.com/MTKAaC1Q | 11:00 |
| freemangordon | pin2 does not seem to be handlet at all | 11:00 |
| freemangordon | *handled | 11:01 |
| freemangordon | which kind of make sense to me, as it is not related to SIM phone services | 11:01 |
| freemangordon | "When the PIN2 code ON/OFF setting is set to ON, you are required to enter the PIN2 code when making user certificate operations. If the wrong PIN2 code is entered three times in a row, PIN Lock will be automatically activated." | 11:01 |
| freemangordon | from here https://www.docomo.ne.jp/english/support/trouble/password/pin/ | 11:02 |
| Wizzup | sure, I just mapped it to connui-cellular code | 11:03 |
| freemangordon | yeah, I know | 11:03 |
| freemangordon | I am on it ATM | 11:03 |
| Wizzup | :) | 11:09 |
| sicelo | btw,don't waste your time with any cdma/evdo support. ofono no longer supports it because such networks practical no longer exist. | 11:09 |
| freemangordon | ok | 11:10 |
| sicelo | something else to look at is how we handle cbs broadcast and class 0 messages.Irc,nl recently had scheduled tests for cbs. I think leste users did not get those messeges. | 11:19 |
| sicelo | i am not sure if this is connui's job/the dialer or something else | 11:21 |
| Wizzup | oh is this these annoying ALERTS that they mostly send out in error? | 11:21 |
| sicelo | yes | 11:22 |
| Wizzup | ugh :D | 11:23 |
| sicelo | lol | 11:24 |
| sicelo | but yes we need to handle them, since they'll contain emergency alerts someday | 11:26 |
| Wizzup | "do not come to the city center, it's already bursting with people partying. please stay at home" | 11:28 |
| Wizzup | :) | 11:28 |
| Wizzup | I have no idea how these work, do they really come over the regular cellular network? | 11:28 |
| sicelo | yes | 11:29 |
| Wizzup | as in, is it operator pushed? | 11:29 |
| Wizzup | I see | 11:29 |
| sicelo | CellBroadcast. ofono supports it. we had it in Fremantle, but I'm not sure which part handles it | 11:29 |
| sicelo | But seriously,do you actually gets such messages in those alerts? 😆 | 11:34 |
| Wizzup | yes | 11:37 |
| Wizzup | I never got them | 11:37 |
| Wizzup | in fremantle | 11:37 |
| Wizzup | fwiw | 11:37 |
| Wizzup | I wouldn't count on NL doing the right thing here, it's probably some android and ios specific protocol | 11:38 |
| Wizzup | https://en.wikipedia.org/wiki/NL-Alert hm | 11:38 |
| Wizzup | looks like it is cell broadcast then | 11:38 |
| sixwheeledbeast | They may only broadcast on some towers, only 4G for example. That would make it device dependant. | 11:57 |
| Wizzup | yeah iirc probably it is something like this | 11:58 |
| sicelo | or i am wrong and there's actually no cbs in Fremantle. | 12:01 |
| freemangordon | someone wrote an applet that hanles them | 12:02 |
| sicelo | the thing is ... class 0 messages behave similarly on ui side | 12:02 |
| sicelo | ah, that might be it | 12:02 |
| freemangordon | "cbs-boadcast" or someting | 12:02 |
| freemangordon | dammit, kbd is falling apart as I type | 12:03 |
| sicelo | :P | 12:03 |
| freemangordon | the old one was working properly for 15 years or something | 12:03 |
| freemangordon | this one is 1yo | 12:03 |
| freemangordon | WTF?!? | 12:03 |
| sicelo | n900 kbd? | 12:03 |
| freemangordon | no | 12:03 |
| freemangordon | my PC | 12:03 |
| sicelo | ah | 12:04 |
| freemangordon | I have to strike half of the keys to get the letter | 12:04 |
| freemangordon | the other half react ob outside wind | 12:04 |
| freemangordon | *on | 12:04 |
| Wizzup | maybe code on the droid4 | 12:05 |
| freemangordon | anyway | 12:05 |
| freemangordon | no, I'll just buy another one later today | 12:05 |
| Wizzup | btw I was wondering, shall I work around the firmware/kernel issues for d4 wifi? | 12:05 |
| Wizzup | I can just try auth/association again if it fails in <0.5s | 12:05 |
| freemangordon | no | 12:05 |
| Wizzup | for a number of three times | 12:05 |
| Wizzup | ok | 12:05 |
| freemangordon | please don;t, rather pester the maintainers to fix it | 12:05 |
| freemangordon | this is kernel issue, I can bet | 12:05 |
| Wizzup | so pester ourselves? :D | 12:05 |
| freemangordon | no, why? | 12:05 |
| Wizzup | that was a joke | 12:06 |
| freemangordon | wl1281 is supported | 12:06 |
| freemangordon | yeah, but still | 12:06 |
| sicelo | yes there's kernel team for wifi stuff, including wl*. some time ago, some kernel version broke the wl1251, and they fixed it when i reported the issue | 12:09 |
| Wizzup | ok | 12:12 |
| Wizzup | ok, channels render ok now in conversations | 13:26 |
| Wizzup | I will fixup the logging and then implement joining channels / sending to them, today hopefull | 13:26 |
| Wizzup | u | 13:26 |
| Wizzup | and then tag a new release | 13:26 |
| Wizzup | arno11: load on boot on n900 is quite high indeed | 13:40 |
| Wizzup | like 11 or something crazy | 13:40 |
| Wizzup | are we on 16 bit yet? | 13:41 |
| arno11 | Wizzup: unfortunately not with dec 24 img | 14:19 |
| arno11 | and no PA user mode | 14:20 |
| arno11 | the last img is 'old', i forgot that | 14:22 |
| arno11 | probably unusable ootb | 14:27 |
| Wizzup | arno11: ok, but do we have a leste-config change for 16bit? | 16:05 |
| freemangordon | Wizzup: yes | 16:16 |
| freemangordon | https://github.com/maemo-leste/leste-config/commit/e74754a27e08f53b59d43ed736776a59c5d4fd40 | 16:16 |
| Wizzup | ok, great | 16:23 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!