<freemangordon>
besides "pin" and "puk", all others sound like netword/SP passwords to me
<freemangordon>
*network
<freemangordon>
"Phone-to-SIM PIN is required"
<freemangordon>
?
<sicelo>
I'm not sure, but maybe it is :-)
<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
<freemangordon>
unless we have supported device with locked modem we can test that
<freemangordon>
at least I am not aware of any
<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
<freemangordon>
no worries, I will break it :p
<freemangordon>
I am implementing multiple modem support, along with major rewrite/cleanup
<freemangordon>
so no way everything to work as it should from the first try
<sicelo>
Allow me to add two items to your list
<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
<freemangordon>
ok, I think will be a side-effect anyways
<sicelo>
2. Handle roaming indication. I could probably help with poor quality icons
<sicelo>
:-P
<freemangordon>
ah
<freemangordon>
we don't have that ion fremantle?
<freemangordon>
*in
<sicelo>
No
<freemangordon>
ok
<freemangordon>
makes sense
<sicelo>
We only don't do gprs when roaming
<freemangordon>
sicelo: any clue what PIN vs UPIN vs PIN2 is?
<freemangordon>
ah, seems upin is for usim
<freemangordon>
but, what is pin2?
<sicelo>
U* stuff is usually related to cdma/evdo networks
<freemangordon>
ok, so it seems this will appear in ofono as PIN
<freemangordon>
pin2 does not seem to be handlet at all
<freemangordon>
*handled
<freemangordon>
which kind of make sense to me, as it is not related to SIM phone services
<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."
<Wizzup>
sure, I just mapped it to connui-cellular code
<freemangordon>
yeah, I know
<freemangordon>
I am on it ATM
<Wizzup>
:)
<sicelo>
btw,don't waste your time with any cdma/evdo support. ofono no longer supports it because such networks practical no longer exist.
<freemangordon>
ok
<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.
<sicelo>
i am not sure if this is connui's job/the dialer or something else
<Wizzup>
oh is this these annoying ALERTS that they mostly send out in error?
<sicelo>
yes
<Wizzup>
ugh :D
<sicelo>
lol
<sicelo>
but yes we need to handle them, since they'll contain emergency alerts someday
<Wizzup>
"do not come to the city center, it's already bursting with people partying. please stay at home"
<Wizzup>
:)
<Wizzup>
I have no idea how these work, do they really come over the regular cellular network?
<sicelo>
yes
<Wizzup>
as in, is it operator pushed?
<Wizzup>
I see
<sicelo>
CellBroadcast. ofono supports it. we had it in Fremantle, but I'm not sure which part handles it
<sicelo>
But seriously,do you actually gets such messages in those alerts? 😆
<Wizzup>
yes
<Wizzup>
I never got them
<Wizzup>
in fremantle
<Wizzup>
fwiw
<Wizzup>
I wouldn't count on NL doing the right thing here, it's probably some android and ios specific protocol
<sixwheeledbeast>
They may only broadcast on some towers, only 4G for example. That would make it device dependant.
<Wizzup>
yeah iirc probably it is something like this
<sicelo>
or i am wrong and there's actually no cbs in Fremantle.
<freemangordon>
someone wrote an applet that hanles them
<sicelo>
the thing is ... class 0 messages behave similarly on ui side
<sicelo>
ah, that might be it
<freemangordon>
"cbs-boadcast" or someting
<freemangordon>
dammit, kbd is falling apart as I type
<sicelo>
:P
<freemangordon>
the old one was working properly for 15 years or something
<freemangordon>
this one is 1yo
<freemangordon>
WTF?!?
<sicelo>
n900 kbd?
<freemangordon>
no
<freemangordon>
my PC
<sicelo>
ah
<freemangordon>
I have to strike half of the keys to get the letter
<freemangordon>
the other half react ob outside wind
<freemangordon>
*on
<Wizzup>
maybe code on the droid4
<freemangordon>
anyway
<freemangordon>
no, I'll just buy another one later today
<Wizzup>
btw I was wondering, shall I work around the firmware/kernel issues for d4 wifi?
<Wizzup>
I can just try auth/association again if it fails in <0.5s
<freemangordon>
no
<Wizzup>
for a number of three times
<Wizzup>
ok
<freemangordon>
please don;t, rather pester the maintainers to fix it
<freemangordon>
this is kernel issue, I can bet
<Wizzup>
so pester ourselves? :D
<freemangordon>
no, why?
<Wizzup>
that was a joke
<freemangordon>
wl1281 is supported
<freemangordon>
yeah, but still
<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
<Wizzup>
ok
akossh has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
<Wizzup>
ok, channels render ok now in conversations
<Wizzup>
I will fixup the logging and then implement joining channels / sending to them, today hopefull
<Wizzup>
u
<Wizzup>
and then tag a new release
<Wizzup>
arno11: load on boot on n900 is quite high indeed
<Wizzup>
like 11 or something crazy
<Wizzup>
are we on 16 bit yet?
sch has quit [Remote host closed the connection]
arno11 has joined #maemo-leste
<arno11>
Wizzup: unfortunately not with dec 24 img
<arno11>
and no PA user mode
<arno11>
the last img is 'old', i forgot that
slep has joined #maemo-leste
<arno11>
probably unusable ootb
f_ has quit [Ping timeout: 276 seconds]
Pali has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
arno11: ok, but do we have a leste-config change for 16bit?