| Sicelo009N | as freemangordon said, the 'emergency-ness' of the call is easily apparent on pin entry ... because at that point the phone should not let you do any calls via the SIM whose PIN you probably even do no know. but at least you can use it for life & death situations | 00:00 |
|---|---|---|
| jonwil | freemangordon: where is _connui_internet_status_menu_item_is_suspended? | 00:01 |
| jonwil | you missed that one | 00:01 |
| freemangordon | hmm, right | 00:02 |
| freemangordon | I wonder why -Werror didn't catch that :( | 00:02 |
| freemangordon | jonwil: going to add it | 00:03 |
| jonwil | ok | 00:03 |
| bencoh | Sicelo: my point was that nowadays phones are usually turned on but password-protected ... not protected by the sim's pincode | 00:06 |
| Sicelo | even then .. the emergency call is (should) still be possible | 00:06 |
| *** handaxe has joined #maemo-ssu | 00:16 | |
| freemangordon | jonwil: done | 00:17 |
| *** handaxe has left #maemo-ssu | 00:18 | |
| jonwil | great | 00:18 |
| jonwil | now we just need the debian packaging | 00:18 |
| freemangordon | I'll do it, probably tomorrow | 00:18 |
| freemangordon | still, why -Werror doesn't catch functions with no prototypes? | 00:19 |
| freemangordon | well, actually there is no warning at all | 00:19 |
| *** Pali has quit IRC | 02:37 | |
| *** LauRoman|Alt has quit IRC | 03:28 | |
| *** LauRoman has quit IRC | 03:28 | |
| *** futpib has quit IRC | 03:39 | |
| *** sparetire_ has quit IRC | 05:41 | |
| jonwil | I just cloned osso-systemui-modechange :) | 06:38 |
| Sicelo | :) | 07:19 |
| *** Sicelo009N has quit IRC | 08:24 | |
| *** Sicelo009N has joined #maemo-ssu | 08:36 | |
| *** Sicelo009N has quit IRC | 08:46 | |
| freemangordon | jonwil: why is that? https://github.com/community-ssu/osso-systemui-alarm/commit/ec77165f915698c96aede6796d8cdb1d4fb42531 | 08:50 |
| freemangordon | jonwil: those GtkWidget->GtkWindow are simply wrong, please revert those commits and use GTK_WINDOW(obj) cast when needed | 08:57 |
| freemangordon | s/are simply/changes are simply/ | 08:57 |
| infobot | freemangordon meant: jonwil: those GtkWidget->GtkWindow changes are simply wrong, please revert those commits and use GTK_WINDOW(obj) cast when needed | 08:57 |
| freemangordon | see https://github.com/community-ssu/osso-systemui-alarm/commit/ec77165f915698c96aede6796d8cdb1d4fb42531#diff-845e439430941a41c60246e333118df9R950 | 08:58 |
| freemangordon | gtk_dialog_new() returns GtkWidget*, if you want to use that object as anything else, you should cast it with gtk macroses like GTK_WINDOW(), GTK_DIALOG() etc | 09:00 |
| jonwil | ok, will undo the change | 09:00 |
| freemangordon | c-style cast is not a good idea, as GTK_XXX does a runtime checks if the object can really be converted to the required type | 09:00 |
| *** Sicelo009N has joined #maemo-ssu | 09:00 | |
| freemangordon | jonwil: just explaining why :) | 09:01 |
| jonwil | ok | 09:01 |
| jonwil | ok, I fixed it | 09:03 |
| freemangordon | jonwil: when you are sure everything works as it should, you may add "-DG_DISABLE_CAST_CHECKS" to CFLAGS, then runtime checks are not performed and GTK_XXX turns into a c-style check. see https://github.com/community-ssu/rtcom-accounts-plugin-gtalk/blob/master/configure.ac#L50 and bellow on a sane way this to be done :) | 09:04 |
| freemangordon | good | 09:04 |
| freemangordon | jonwil: btw, why did you do this change? | 09:05 |
| jonwil | I found clear evidence that those 4 systemui functions actually do take a GtkWindow and not a GtkWidget. More specifically, I found code that called those functions passing in GTK_WINDOW(blah) | 09:06 |
| jonwil | which wouldn't be appropriate if it was a GtkWidget going in | 09:06 |
| freemangordon | jonwil: hmm, a simle "git revert" should've been better, as commit description "more fixes" doesn't tell us much :), sorry to be picky, but in a month from now, we will have no idea what and why it was done :) | 09:07 |
| freemangordon | jonwil: then function should be declared as f(GtkWindow *) and all the callers should cast to GtkWindow | 09:08 |
| jonwil | all 4 functions are declared as f(GtkWindow) now | 09:08 |
| freemangordon | great | 09:08 |
| jonwil | the only mistake I made was not doing the right thing in osso-systemui-alarm | 09:09 |
| jonwil | I got confused because osso-systemui-alarm seems to be compiled with -DG_DISABLE_CAST_CHECKS | 09:09 |
| jonwil | and didn't realize I needed some macros in there | 09:10 |
| freemangordon | which we should use for all of the packages, but this is another story | 09:10 |
| freemangordon | jonwil: oh, and please, change debian/changelog files and put your name here, not mine or Pali's :p | 09:11 |
| freemangordon | *there | 09:11 |
| jonwil | oh sorry | 09:11 |
| jonwil | I used dch command to update changelog and didnt even notice the names | 09:11 |
| freemangordon | what is dch? | 09:11 |
| freemangordon | I always edit changelog files by hand | 09:12 |
| * freemangordon finds gtk type macros overly confusing sometimes :) | 09:13 | |
| jonwil | anyhow, osso-systemui-alarm is using the right things now | 09:14 |
| freemangordon | jonwil: on a side note, how it is the correc way (in english, for plural): macroses or macros? | 09:14 |
| jonwil | modechange, tklock and powerkeymenu are fine as they didn't use G_DISABLE_CAST_CHECKS and hence I didn't get confused with either of those | 09:14 |
| jonwil | macros | 09:14 |
| freemangordon | ok, thanks | 09:15 |
| freemangordon | oh, yeah, it is macro for single, weird, as in Bulgarian we say "macros" for single. however | 09:15 |
| freemangordon | jonwil: this define swithes *runtime* checks off, not compile time, iirc | 09:16 |
| freemangordon | or there are warning in compile time as well? | 09:16 |
| freemangordon | *warnings | 09:17 |
| jonwil | there are compile time warnings if you pass the wrong pointer (e.g. a GtkWidget when it wants a GtkWindow) | 09:17 |
| freemangordon | oh, good | 09:17 |
| freemangordon | jonwil: actually what this "modechange" plugin does? | 09:18 |
| jonwil | If you are in airplane mode and you do an action that goes out of airplane mode (e.g. trying to activate a data connection) it displays a box saying "are you sure you want to leave airplane mode" | 09:19 |
| jonwil | Which doesn't happen if you press the "exit airplane mode" button on the powerkeymenu | 09:19 |
| freemangordon | I see | 09:19 |
| jonwil | easiest way to see is to press powerkey, press "offline mode" then press status bar then press "internet connection" button | 09:20 |
| freemangordon | got it | 09:20 |
| freemangordon | jonwil: BTW, could you share you hildon-whatever-nsv-something IDA db, to see if I can RE it further | 09:22 |
| jonwil | https://drive.google.com/file/d/0B9idqO9KygGsM0FoUW1GU0RNbm8/view?usp=sharing | 09:24 |
| jonwil | does anyone know what "act dead" state is? | 09:24 |
| freemangordon | sure | 09:25 |
| freemangordon | :D | 09:25 |
| jonwil | what is it? | 09:25 |
| freemangordon | jonwil: when you turn you device off and connect a charger | 09:25 |
| freemangordon | it turns on end enters "act dead" state | 09:25 |
| freemangordon | or when an alarm is triggered while it is turned off | 09:25 |
| *** DrCode has quit IRC | 09:27 | |
| jonwil | why it needs a systemui plugin (especially one that has UI) I dont understand | 09:27 |
| freemangordon | who needs it? systemui? | 09:28 |
| jonwil | yes there is a systemui plugin for actdead | 09:28 |
| freemangordon | well, take alarmui for example - it has a dialog asking you whether you want to "turn on the device" | 09:29 |
| freemangordon | dunno what actdead systemui does, but I guess we can find that easy | 09:29 |
| freemangordon | jonwil: keep in mind that ACT_DEAD mode has almost everything up and running, including X, dbus, etc. only hildon-desktop is not started afaik | 09:31 |
| jonwil | Is there a difference between act_dead mode and the "battery is too low to run normal system" mode? | 09:32 |
| jonwil | the one you get when your battery dies and your phone switches off then you plug it into a charger and it goes into a charging mode | 09:32 |
| freemangordon | yes, those are different | 09:32 |
| freemangordon | you enter ACT_DEAD when there is enough battery to boot maemo | 09:32 |
| freemangordon | but for some reason (like alarm triggered while off) you don;t want to enter USER mode | 09:33 |
| jonwil | does ACT_DEAD mode turn on radios or does it act like airplane mode? | 09:34 |
| freemangordon | when your phone dies because of a flat battery and you connect a charger, it is NOLO that does the so-called precharging, until there is enough charge to boot maemo and enter ACT_DEAD | 09:34 |
| freemangordon | afaik radis are off | 09:34 |
| freemangordon | *radios | 09:34 |
| freemangordon | so yes, it is like airplane mode in that regard | 09:35 |
| jonwil | radios being off makes sense otherwise an alarm could cause your phone to switch on at a point where cellular radios are banned for some reason (e.g. on an airplane) | 09:35 |
| freemangordon | yeah | 09:35 |
| freemangordon | that is why you're presented with a dialog asking you if you want to turn the device on | 09:36 |
| freemangordon | acually, if you select "no", the device is not turned off again, iirc :) | 09:36 |
| *** Sicelo009N has quit IRC | 09:36 | |
| jonwil | anyhow, my next potential targets are the remaining osso-systemui pieces (main daemon, actdead, devlock, emergency, splashscreen) and also possibly osso-applet-devicelock, libdevlock and libcodelockui | 09:40 |
| jonwil | device lock UI would be useful since IIRC someone said it has problems in CSSU in portrait mode | 09:40 |
| freemangordon | isn't devlock == tklock? | 09:41 |
| freemangordon | or this is the one to enter the code? | 09:41 |
| jonwil | yeah devlock is the code entry | 09:41 |
| jonwil | for security code | 09:41 |
| jonwil | there is libdevlock which handles storing the code in CAL | 09:41 |
| jonwil | there is libcodelockui that displays the UI for it | 09:42 |
| jonwil | plus the systemui stuff for displaying the unlock dialogs | 09:42 |
| jonwil | and the control panel for setting the lock code | 09:42 |
| freemangordon | ok | 09:43 |
| jonwil | the same UI widget is used for pin code lock if your SIM is protected by a PIN I believe (connui-conndlgs-cellular does that bit) | 09:43 |
| jonwil | Not so sure the main systemui daemon is really worth reverse engineering actually | 09:49 |
| freemangordon | why not, it was a small binary iirc | 09:50 |
| freemangordon | what the?!? | 09:50 |
| freemangordon | jonwil: could you look at system_initialize in ...-nsv | 09:50 |
| freemangordon | I think there is a memleak | 09:51 |
| freemangordon | oh, no | 09:51 |
| freemangordon | my bad | 09:51 |
| jonwil | yeah systemui is a small binary but that doesn't mean its easy to RE | 09:52 |
| jonwil | I think the device lock stuff is a nice target to do next | 09:52 |
| jonwil | since there is a use for that (portrait mode device lock fixes) | 09:52 |
| freemangordon | yeah | 09:52 |
| *** mirda has left #maemo-ssu | 10:35 | |
| bencoh | freemangordon: how do you display g_debug/g_warning? I guess I'm missing some magic envvar or args | 10:47 |
| bencoh | (with this version of gtk/glib ...) | 10:47 |
| *** Pali has joined #maemo-ssu | 10:52 | |
| jonwil | ok, so I figured out that the list of emergency numbers obtained by libcodelockui is only used to determine whether to display the "emergency call" button and that pressing that button doesn't pass what you typed into the unlock code box (911/112/whatever) to the phone subsystem, it passes a special magic string urn:service:sos which dials the real emergency number (oops). So my hack to make... | 11:15 |
| jonwil | ...it think "12345" was a valid emergency number (so I could test pressing the button and see it dial the invalid number 12345) went wrong. | 11:15 |
| jonwil | So from now on I wont touch that button at all | 11:15 |
| jonwil | Although I just found out that if you e.g. use dbus-send via SSH to dial a regular non-emergency phone #, it will properly dial even with the phone in locked state | 11:35 |
| jonwil | that said, if someone has ssh access to a locked phone and knows how to send a "dial number" command, they can also find a way to unlock the phone that way | 11:35 |
| bencoh | jonwil: ooooooh | 11:41 |
| bencoh | so that's how it works. | 11:41 |
| jonwil | note that rtcom-call-ui has special UI if the phone is locked and you are dialing a non-emergency number to indicate its locked and give you an option to activate the unlock screen | 11:47 |
| jonwil | So glad we have a reverse engineered MCE to play with, so many of the cool things I am fiddling with are tied into MCE | 11:52 |
| *** jonwil has quit IRC | 13:22 | |
| *** futpib has joined #maemo-ssu | 13:38 | |
| *** sparetire_ has joined #maemo-ssu | 15:12 | |
| *** Sicelo009N has joined #maemo-ssu | 15:15 | |
| *** xes has quit IRC | 18:53 | |
| *** xes has joined #maemo-ssu | 19:13 | |
| freemangordon | bencoh: nothing special, besides syslog | 19:45 |
| freemangordon | keep in mind you have to reboot the device after installing syslog | 19:45 |
| bencoh | hmmm ... then I wonder why I dont see g_warning/g_debug messages in a custom gtk program (running from cli) | 19:46 |
| bencoh | oh ... how comes? | 19:46 |
| freemangordon | bencoh: you should use g_print, if you want those messages in the console | 19:46 |
| freemangordon | bencoh: device needs a reboot after installing syslog for the first time, bon't as me why :) | 19:47 |
| freemangordon | *don't | 19:47 |
| bencoh | but ... they're debug messages ... they shouldn't be displayed unless someone really wants it (?) | 19:48 |
| freemangordon | bencoh: usually you won;t see g_debug messages | 19:48 |
| freemangordon | thus you'd better use g_warning :) | 19:49 |
| bencoh | I dont see g_warning either | 19:49 |
| bencoh | that's what I dont understand | 19:49 |
| freemangordon | did you reboot? | 19:49 |
| bencoh | I guess I missed something :) | 19:49 |
| bencoh | launching from cli | 19:49 |
| freemangordon | no matter, did you reboot? | 19:49 |
| bencoh | what? | 19:49 |
| freemangordon | did you restart the device? | 19:50 |
| freemangordon | after installing syslog | 19:50 |
| bencoh | errr ... do you mean every single g_* message goes to syslog? | 19:50 |
| bencoh | and there is no way to override that? | 19:50 |
| freemangordon | there is a way | 19:50 |
| freemangordon | but yes, every g_... message goes to syslog, besides g_print() | 19:50 |
| bencoh | okay ... thx for the info :) | 19:51 |
| bencoh | I guess I really need syslog then | 19:51 |
| bencoh | (not just for this mafw debugging stuff) | 19:51 |
| bencoh | oh and ... not related to this, but what prevents us from shipping libgcc-4.7 in cssu (not just thumb)? | 19:52 |
| bencoh | is there some compat issue? | 19:52 |
| freemangordon | nothing afaik | 19:55 |
| freemangordon | we just need time and will | 19:55 |
| bencoh | okay | 19:57 |
| bencoh | do we have a non-thumb libgcc-4.7? | 19:57 |
| freemangordon | we have only non-thumg libgccc | 19:57 |
| freemangordon | hmm, typo day | 19:58 |
| bencoh | :) | 19:58 |
| bencoh | so we could just copy the package to -testing ? | 19:58 |
| kerio | can we have a thumb libgcc-4.7 | 20:05 |
| freemangordon | kerio: don't think so | 20:07 |
| freemangordon | or rather - don;t know how to do it | 20:07 |
| kerio | also can we have a thumb xorg compiled with 4.7 | 20:12 |
| freemangordon | why not? | 20:13 |
| freemangordon | I just need to find some spare time | 20:13 |
| freemangordon | and that's not easy :) | 20:13 |
| bencoh | setting up 4.7.2-thumb toolchain here :) | 20:16 |
| freemangordon | bencoh: you'd better find someone that can build toolchain, having 4.9 would be good IMO | 20:17 |
| bencoh | what do you mean by "can build toolchain"? | 20:17 |
| kerio | clang | 20:18 |
| kerio | clang is cool | 20:18 |
| kerio | fuck gnu | 20:18 |
| bencoh | kerio: errr ...not today(tm) :p | 20:18 |
| bencoh | freemangordon: "building" a toolchain isn't a real issue for me, but "packaging" it to make it work with sb is something else | 20:19 |
| bencoh | (oh, and we'd still need to apply err657417 patch to gcc) | 20:20 |
| bencoh | unless this has been worked around in 4.9? | 20:20 |
| freemangordon | вхат ис err657417? | 20:23 |
| freemangordon | sorry | 20:23 |
| freemangordon | what is err657417? | 20:23 |
| freemangordon | bencoh: ^^^ | 20:23 |
| bencoh | http://wiki.maemo.org/Community_SSU/Thumb#ARM_errata_657417 | 20:26 |
| freemangordon | bencoh: the errata workaround is in ld | 20:27 |
| freemangordon | and is there since 2.20 iirc | 20:28 |
| bencoh | hmm | 20:29 |
| bencoh | then why do we need a different toolchain? | 20:30 |
| freemangordon | because 4.9 has more ARM optimizations than in 4.7. also, auto-vectoriser actually works afaik | 20:30 |
| bencoh | I mean 4.7 vs 4.2 | 20:30 |
| freemangordon | because 4.2 has a couple of thumb-related bugs | 20:31 |
| bencoh | oh okay | 20:31 |
| bencoh | hm and looks like it shipped ld 2.18 | 20:31 |
| freemangordon | that one too | 20:31 |
| bencoh | anyway ... what would we need to build a 4.9 toolchain> | 20:32 |
| bencoh | ? | 20:32 |
| freemangordon | no idea, it was tricky | 20:32 |
| freemangordon | I tried once to build 4.7.2 as debs, but there was some problem when installed in SB | 20:33 |
| merlin1991 | crosstools-ng and some debian packaging for the easy route ;) | 20:33 |
| freemangordon | merlin1991: SB has that packaging already (or some HOWTO, can't remember) | 20:33 |
| freemangordon | but setting all the build dirs, root, etc is tricky | 20:33 |
| freemangordon | also, -ng don;t do it iirc, you need to do it by hand | 20:34 |
| freemangordon | don;t do it correctly I mean | 20:34 |
| freemangordon | also, one should statically link host computer glibc etc, otherwise it won't run in SB | 20:34 |
| freemangordon | etc, etc,... | 20:35 |
| merlin1991 | hm I got crosstols-ng built arm toolchain running in sb2 but then again sb2 works quite differnt to sb | 20:35 |
| merlin1991 | never tried to load a different toolchain into our trusty scratchbox | 20:36 |
| kerio | i thought it was karmic, not trusty | 20:37 |
| kerio | huehue | 20:37 |
| bencoh | krkr :) | 20:37 |
| Sicelo | fun times | 20:40 |
| Sicelo | Oct 25 20:38:41 fremantle kernel: [ 2438.567230] memory_sync_page: no page for 4395b000 | 20:40 |
| Sicelo | Oct 25 20:38:41 fremantle kernel: [ 2438.567260] proc_memory_sync: InValid address parameters 4395a800 e80 | 20:40 |
| kerio | i wonder what would be a decent way to modernize maemo | 20:43 |
| merlin1991 | upgrade alll the libs? | 20:43 |
| kerio | what do you do with the statically-compiled, closed stuff? | 20:43 |
| kerio | i guess you keep the old libs around | 20:43 |
| bencoh | if they're statically-compiled you dont need the libs ;) | 20:44 |
| kerio | er yea | 20:44 |
| bencoh | but I guess you meant "linked against old libs" | 20:44 |
| kerio | yep | 20:44 |
| kerio | i doubt there's much that's statically compiled | 20:44 |
| kerio | given that space was (and is) quite a premium | 20:44 |
| bencoh | you check ABI compat and symbol dependencies | 20:44 |
| merlin1991 | kerio: did I mention, re all the bits? | 20:45 |
| kerio | let's just move to freebsd | 20:46 |
| kerio | i bet the nokia stuff runs fine in the linux compat layer | 20:47 |
| bencoh | meh :D | 20:47 |
| drathir | sad that maemo isnt based at at alar, but on the debian... | 20:57 |
| drathir | alarm* | 20:58 |
| *** Sicelo009N has quit IRC | 21:26 | |
| *** jonwil has joined #maemo-ssu | 22:04 | |
| jonwil | hi | 22:12 |
| *** Sicelo009N has joined #maemo-ssu | 22:21 | |
| Pali | hi! | 23:08 |
| jonwil | Time to clone osso-systemui-devlock next I think, that and libcodelockui | 23:15 |
| jonwil | Then someone can add portrait device lock support to CSSU | 23:15 |
| jonwil | osso-applet-devicelock is on the todo as well | 23:16 |
| jonwil | Probably wont let you do portrait support for the other code lock stuff (i.e. sim pin codes) but who uses those anyway... | 23:16 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!