| 00:06.38 | *** join/#neo900 AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 01:18.06 | *** join/#neo900 Humpelstilzchen (erik@x50ab65ab.dyn.telefonica.de) |
| 02:26.44 | *** join/#neo900 cybiko123 (~cybiko123@unaffiliated/cybiko123) |
| 03:32.04 | *** join/#neo900 HylianSavior (~mafuyu@2607:5600:c6:1d::3d64) |
| 03:47.20 | *** join/#neo900 l_bratch (~l_bratch@212.9.8.20) |
| 05:30.55 | *** join/#neo900 itbaron (~kvirc@a88-115-8-208.elisa-laajakaista.fi) |
| 06:22.31 | *** join/#neo900 chainsawbike_ (~chainsawb@unaffiliated/chainsawbike) |
| 06:31.35 | *** join/#neo900 tomeff (~tomeff@ip-78-102-111-158.net.upcbroadband.cz) |
| 08:42.08 | *** join/#neo900 tomeff (~tomeff@ip-78-102-111-158.net.upcbroadband.cz) |
| 09:00.02 | *** join/#neo900 Nitunse (~Nitunse@ANantes-654-1-226-212.w81-50.abo.wanadoo.fr) |
| 09:06.09 | *** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali) |
| 09:30.21 | *** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali) |
| 09:42.23 | *** join/#neo900 SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl) |
| 10:34.07 | *** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire) |
| 10:48.02 | *** join/#neo900 tomeff_ (~tomeff@ip-78-102-111-158.net.upcbroadband.cz) |
| 11:03.28 | *** join/#neo900 Kabouik (~quassel@65.76.93.92.rev.sfr.net) |
| 12:00.35 | *** join/#neo900 tomeff (~tomeff@ip-78-102-111-158.net.upcbroadband.cz) |
| 12:54.37 | *** join/#neo900 paulk-tereshkova (~paulk-fre@cachy.fdn.org) |
| 14:59.56 | *** join/#neo900 dal (~dal@99-14-172-79.lightspeed.ftwotx.sbcglobal.net) |
| 15:03.56 | *** join/#neo900 SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl) |
| 18:36.17 | DocScrutinizer05 | *sigh* http://www.gemalto.com/training-site/emea-site/catalog/Understanding_BIP_T1017S.pdf |
| 18:37.16 | DocScrutinizer05 | Neo900DOWN PAYMENT Neo900 complete device-184 |
| 18:37.17 | DocScrutinizer05 | NeoNDOWN PAYMENT NeoN bare board-103 |
| 18:37.19 | DocScrutinizer05 | +1EURDown Payment top up-7919 |
| 18:38.26 | DocScrutinizer05 | 2/3 of our own goal already reached |
| 18:43.05 | Arch-TK | what was the goal again? |
| 18:43.31 | DocScrutinizer05 | well, we based calculations on 400 orders |
| 18:43.41 | Arch-TK | right |
| 18:45.29 | DocScrutinizer05 | unrelated background (about modem): https://developer.gemalto.com/threads/phs8-atscsl-customer-sim-lock-permit-all-lock |
| 18:49.41 | *** join/#neo900 AndrewX192 (~andrew@unaffiliated/andrewx192) |
| 18:53.44 | *** join/#neo900 xes_ (~xes@unaffiliated/xes) |
| 19:06.03 | Arch-TK | so if I understand this right... You can lock the modem to prevent it from accepting certain sim cards? |
| 19:06.33 | Arch-TK | or lock it to allow certain sim cards |
| 19:06.39 | Arch-TK | but you can't lock it to allow all sim cards? |
| 19:07.19 | DocScrutinizer05 | yes |
| 19:07.59 | Arch-TK | well that's silly. |
| 19:08.08 | DocScrutinizer05 | yes ;-) |
| 19:08.27 | Arch-TK | is this how sim lock is implemented or is that something separate? |
| 19:08.40 | DocScrutinizer05 | that's SIMlock |
| 19:09.25 | Arch-TK | so if these pins are held by the manufacturer, how do phone shops offer sim unlocking? Where did they get the pins? |
| 19:09.39 | Arch-TK | (I have always wondered about all of this.) |
| 19:09.56 | DocScrutinizer05 | no idea, usually that's done by rewriting the "filesystem" |
| 19:11.19 | DocScrutinizer05 | which exploits the manufactuer's master key to enable writing data to the "filesystem" where simlock and a lot of other stuff gets stored |
| 19:14.17 | DocScrutinizer05 | anyway we obviously don't want any SIMlock on Neo900, but alas we can't lock down that feature |
| 19:15.09 | DocScrutinizer05 | or disable it. So we will ship the unlock codes to our customers, just in case they accidentally engage the SIMlock |
| 19:16.19 | ZetaR | Can you simlock using wildcards? You could create a simlock that matches all sim cards. |
| 19:16.24 | DocScrutinizer05 | (they would need to read out and apply the code aka password anyway, but I've seen myself forgetting such 'passwords' after 3 minutes when playing around) |
| 19:16.47 | DocScrutinizer05 | ZetaR: please read the original set of 4 posts. can't get done |
| 19:17.15 | DocScrutinizer05 | I suggested adding a wildcard in next firmware version |
| 19:18.10 | ZetaR | Oops. Should have read before commenting. |
| 19:42.17 | *** join/#neo900 n9how (~user@213.152.161.40) |
| 20:00.29 | *** join/#neo900 knittel (~knittel@dyndsl-091-096-187-183.ewe-ip-backbone.de) |
| 20:00.51 | *** part/#neo900 knittel (~knittel@dyndsl-091-096-187-183.ewe-ip-backbone.de) |
| 20:01.09 | *** join/#neo900 knittel (~knittel@dyndsl-091-096-187-183.ewe-ip-backbone.de) |
| 20:01.44 | knittel | hey. if i order today. will it still be in the first batch? :) |
| 20:02.31 | knittel | if its a complete device? |
| 20:08.10 | *** join/#neo900 dal (~dal@82.221.107.179.adsl.inet-telecom.org) |
| 20:28.13 | DocScrutinizer05 | yes :) |
| 20:28.21 | DocScrutinizer05 | afk |
| 21:08.28 | *** join/#neo900 dal (~dal@82.221.107.179.adsl.inet-telecom.org) |
| 21:11.44 | DocScrutinizer05 | knittel: you noticed we even attached a audio-in line to the IR-RX? ;-D |
| 21:12.08 | DocScrutinizer05 | a *lot* of funny things you could do with that |
| 21:13.11 | DocScrutinizer05 | from thunder lightning detection to RPM counting of fans and analyzing PSUs of LED illumination |
| 21:15.40 | DocScrutinizer05 | just thinks about scanning huge barcodes. Bur meh, we got cameras for that |
| 21:45.42 | *** join/#neo900 lobito (~lobito@190.177.215.161) |
| 22:04.11 | *** join/#neo900 dal (~dal@178.162.222.41.adsl.inet-telecom.org) |
| 22:09.19 | knittel | DocScrutinizer05: not yet. but i just found it in the h-bus spcecification :) there are a lot of more or less "usefull" applications for this :D |
| 22:48.53 | *** join/#neo900 jonsger (~Thunderbi@2a02:8070:7cb:c200:6ce8:fd7b:566e:e7a7) |