**** BEGIN LOGGING AT Sat Jul 17 02:59:56 2010 Jul 17 03:36:46 mickey|zzZZzz: i can't compile libfsobasics with vala 0.9.3.1 because of vala_semantic_analyzer_get_actual_type: assertion failed: (instance_type != NULL) Jul 17 03:38:11 mickey|zzZZzz: (vala is from tarball from download.freesmartphone.org) Jul 17 04:38:38 mickey|zzZZzz: it's asyncworker.vala that fails Jul 17 04:50:56 Weird Jul 17 04:54:55 I have vala 0.9.3.1 from your tarball. But that is spoils all the fun, when i revert that commit, it compiles. Jul 17 05:04:22 But ~new vala is needed regardless of that because you use unichar.to_string. Jul 17 06:40:54 mrmoku|away: that's just damn strange, i have no idea how that can happen. My build is almost done, so we'll be on the same rev really soon. Jul 17 06:46:39 mrmoku|away: hehe, something happened and my UI is incompatible now. Jul 17 06:47:14 Hm, it's still not fixed wrt re-requesting the resource. Jul 17 06:47:16 Gotta file a bug. Jul 17 06:47:44 mrmoku|away: i now call SetFunctionality too early. Jul 17 06:49:26 Hm, how the hell should i do it properly? Jul 17 06:50:29 And @POFF shouldn't wait for a reply Jul 17 06:52:31 LOL, it tries to retry it 3 times :D Jul 17 07:25:51 mickey|zzZZzz: how come requesting resource is now kinda async for me and it returns before the modem left the initialising state? Jul 17 07:35:30 It was kinda hard to compile this latest fsogsmd version. And now i get an unexpected incompatibility, fun. Jul 17 07:37:57 But the change is logical i've to agree. Jul 17 07:58:19 mrmoku|away: is it not your problem mrmoku|away ? Jul 17 08:06:17 So now i have to wait for the DeviceStatus signal to complete the initialization (with SetFunctionality) once. So i need an additional flag to know if i did it already or not. Kinda inelegant. Jul 17 08:07:43 (defun fso-gsm-handle-device-status (s) Jul 17 08:07:46 (if (and (not fso-gsm-initialized) Jul 17 08:07:49 (eq (compare-strings s 0 nil "alive-" 0 nil) 7)) Jul 17 08:07:52 meh Jul 17 08:17:27 Hi! From I use , and MathiasZJ: hey. You message is truncated after shr-full. Consider using splintlong.pl or something :) Jul 17 08:18:17 ok Jul 17 08:18:43 But my FreeRunner says “drm:glamo_display_panic *ERROR* panic occured, switching back to text console” Jul 17 08:19:19 From I just use the newest jffs2, qi*.udfu and uImage*.bin. Jul 17 08:19:22 MathiasZJ: that's on a freshly flashed kernel+rootfs from the same source? Jul 17 08:19:31 PaulFertser: + Jul 17 08:20:02 MathiasZJ: probably JaMa has an idea what's happening. Jul 17 08:20:39 I try it again using the following files: Jul 17 08:20:44 http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-2.6.32.13-oe3.2+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0-om-gta02.bin Jul 17 08:20:54 http://build.shr-project.org/shr-unstable/images/om-gta02/qi-s3c2442-1.0.2-r3+gitr0+c38b062a609f1442e6a9e13005cfbdfd59a5ac0d.udfu Jul 17 08:21:01 http://build.shr-project.org/shr-unstable/images/om-gta02/shr-full-eglibc-ipk--20100714-om-gta02.rootfs.jffs2 Jul 17 08:21:22 MathiasZJ: this combination should be safe, do you have more logs before "panic occured" ? Jul 17 08:22:21 MathiasZJ: also try to boot with POWER button pressed (it will enable debug output) Jul 17 08:23:34 JaMa: +, I tell you after reflashing. Jul 17 08:23:43 Hm, uninspiring, probably should watch more of Garbage. Jul 17 08:24:03 What is the difference between qi and qi-ubi? Jul 17 08:24:54 MathiasZJ: do not use ubi Jul 17 08:25:01 PaulFertser: ok Jul 17 08:25:09 MathiasZJ: qi-ubi passes kernel params to mount flash as ubi Jul 17 08:25:21 MathiasZJ: JaMa says it's too fault-intolerant, so we have to avoid it. Jul 17 08:26:42 * JaMa is using it with 2.6.34 even with background thread enabled again.. but my main OS is on uSD so it will take long to test fault-tolerance on flash.. Jul 17 08:27:36 because I mount it only few times a month.. Jul 17 08:28:15 as 2nd recovery when first recovery also fails :) Jul 17 08:40:25 JaMa: you use UBI, that is? Jul 17 08:47:51 After reflashing again, it works. I am sorry for bothering you, but I did not work before for some days. Jul 17 08:53:59 Weiss: only on 3rd installation of shr.. Jul 17 08:54:50 Weiss: so not much and if I do I usually can shutdown correctly.. so haven't tested recovery after battery removal etc.. Jul 17 08:55:09 ah, ok Jul 17 08:55:15 * JaMa -> swimming pool, bye Jul 17 09:09:53 PaulFertser: (SetFunctionality) I moved that to GSM.DeviceStatus signal when seeing one of the alive-sim stati Jul 17 09:10:14 hrhr, https certificate on bugs.maemo.org is expired... Jul 17 09:10:28 PaulFertser: should read complete backlog first :P Jul 17 09:11:21 PaulFertser: and yes, I have builderrors with current libfsobasics too Jul 17 09:11:54 mrmoku: do you call it every time you see the ALIVE status? Is it something we're supposed to do? Jul 17 09:12:31 mrmoku: so i'm on a698ea6a133cdd59d40b4910212ee66ce6f4abf9 and it doesn't "magically" unregister. Jul 17 09:19:37 hmm Jul 17 09:21:51 PaulFertser: only on alive-sim-ready Jul 17 09:24:34 mrmoku: tbh i'm still unsure about the semantics. And unhappy about the gsm api. Jul 17 09:26:36 and frustrated with oeventsd bugs (auto-suspend when not on usb doesn't work for me reliably) Jul 17 09:31:29 PaulFertser: 0.9.3.2 is up. Jul 17 09:31:33 bbl, groceries Jul 17 09:32:50 PaulFertser: we handle suspend ourselves... Jul 17 09:36:56 mrmoku: is it flexible enough to prevent suspend on usb? Can you not use oeventsd at all then? Jul 17 09:37:20 anyway, /away Jul 17 09:37:40 yeah... me too later Jul 17 10:18:44 mickey|zzZZzz: yo, builds again - thanks :) Jul 17 10:45:53 hmm... but does not fix our problem :/ Jul 17 10:56:23 hmm Jul 17 11:18:04 time to reflash an older working image Jul 17 11:21:57 sicu: wait a moment... Jul 17 11:22:07 sicu: testing right now... looks good Jul 17 11:22:24 err Jul 17 11:22:29 no Jul 17 11:22:34 sicu: reflash :P Jul 17 11:23:46 mrmoku: hm, i wonder what might be the difference... Jul 17 11:24:17 mrmoku: are you really sure you're not missing some dbus error message? Jul 17 11:34:26 PaulFertser: it is something in the interaction between phonefsod and fsogsmd Jul 17 11:34:59 PaulFertser: now lunch though... Jul 17 11:35:01 bbiab Jul 17 12:06:13 PaulFertser: but what error should that be... it registeres fine... and a minute later is SOS only Jul 17 12:06:30 PaulFertser: if I call SetFunctionality including PIN with mdbus2 it seems to work Jul 17 12:07:21 PaulFertser: the difference is that phonefsod does SetFunctionality always without pin and handles pin via SetAuthCode Jul 17 12:07:57 mrmoku: hm, that might be the difference indeed, as i'm not using pin at all. Jul 17 12:08:54 hmm Jul 17 12:13:48 * mrmoku tries to simulate phonefsod via mdbus2 Jul 17 12:15:14 PaulFertser: hehe, yeah :) Jul 17 12:15:31 PaulFertser: SendAuthCode and then SetFunctionality without PIN does not work ;) Jul 17 12:15:34 mickey|zzZZzz: ^^^^ Jul 17 12:27:08 still no? Jul 17 12:27:11 strange Jul 17 12:27:47 registering fine and then SOS i don't understand at all Jul 17 12:30:10 btw., i'll experiment a bit with delaying the return of RequestResource even longer now Jul 17 12:30:41 mickeyl: tried with mdbus2 -si Jul 17 12:30:43 RequestResource Jul 17 12:30:46 this will make problems for people with unpatched dbus clients, but it's the right thing Jul 17 12:30:58 wait for auth needed signal Jul 17 12:31:01 SendAuthCode Jul 17 12:31:08 wait for unlocked signal Jul 17 12:31:18 SetFunctionality full 1 "" Jul 17 12:31:28 right Jul 17 12:31:28 registers and then looses registration Jul 17 12:31:35 that sounds completely unlikely Jul 17 12:31:40 but of course i believe you Jul 17 12:31:52 are you on a698ea6a133cdd59d40b4910212ee66ce6f4abf9 ? Jul 17 12:32:36 let me try with my external modem Jul 17 12:33:22 mickeyl: 1:0.5.0+gitr831+278e885cf938475301e4d5185c8db16227d39954-r2.2.5 Jul 17 12:33:52 good, that's head Jul 17 12:33:53 which is current HEAD Jul 17 12:33:55 :) Jul 17 12:34:13 ok, launching Jul 17 12:34:43 resource requested Jul 17 12:35:02 modem status locked Jul 17 12:35:08 sending pin Jul 17 12:35:26 auth status ready Jul 17 12:35:58 setting functionality Jul 17 12:36:21 registered Jul 17 12:37:09 ok, works fine on w/ the cinterion Jul 17 12:37:15 hmm Jul 17 12:38:32 honestly, moving from HOME to SOS Only can have only one reason Jul 17 12:38:40 well, rather two reasons Jul 17 12:38:55 one is actively trying to register with a forbidden operator Jul 17 12:39:18 2nd one is modem losing connection to your home operator Jul 17 12:39:24 the logs should tell exactly what happens Jul 17 12:39:34 they're up on trac, right? Jul 17 12:39:48 #577 Jul 17 12:39:55 that is with an older rev though Jul 17 12:40:30 if you need the libgsm log too I still have it from the same session... Jul 17 12:40:34 did not attach due to privacy Jul 17 12:45:18 ok, let me inspect #577 again Jul 17 12:47:27 you have lost connection to the operator Jul 17 12:47:47 yep Jul 17 12:47:51 or for some reason it threw you out of the cell Jul 17 12:48:22 i can't see how fsogsmd should be responsible for that Jul 17 12:48:31 everything in the log looks good Jul 17 12:48:31 hmm Jul 17 12:48:52 it happens to everybody with current SHR-U... Jul 17 12:48:59 and I have good reception here Jul 17 12:49:05 to everybody? Jul 17 12:49:38 yup Jul 17 12:49:45 MDBUS2> org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Network.ListProviders Jul 17 12:49:48 org.freesmartphone.GSM.DeviceFailed: +CME ERROR: 32 Jul 17 12:50:19 it still shows full signal strength with SOS Jul 17 12:50:40 what happens if you try registering again? Jul 17 12:51:15 MDBUS2> org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Network.Register Jul 17 12:51:18 org.freesmartphone.GSM.DeviceFailed: +CME ERROR: 32 Jul 17 12:51:52 it can't find your provider Jul 17 12:51:56 home provider, that is Jul 17 12:53:46 where is an image i can test for myself? Jul 17 12:54:39 http://build.shr-project.org/shr-unstable/images/om-gta02/shr-lite-eglibc-ipk--20100714-om-gta02.rootfs.jffs2 Jul 17 12:54:47 mickeyl: what is CCWA? Jul 17 12:54:51 call waiting Jul 17 12:54:58 enable Anklopfen Jul 17 12:55:01 2010-07-17T12:53:21.567535Z [INFO] libfsotransport <0710:3>: SRC: "+CCWA=1,1" -> [ "OK" ] Jul 17 12:55:26 and in my failed log Jul 17 12:55:26 2010-07-16T10:17:58.348208Z [INFO] libfsotransport <0710:3>: SRC: "+CCWA=1,1" -> [ "+CME ERROR: 100" ] Jul 17 12:55:37 which might just be a consequence... Jul 17 12:55:54 you can only enable call waiting once you have successfully registered Jul 17 12:56:02 yeah Jul 17 12:56:59 which kernel are you using with that rootfs? Jul 17 12:57:03 root@om-gta02 ~ # killall fsogsmd Jul 17 12:57:03 root@om-gta02 ~ # mdbus2 -si Jul 17 12:57:03 MDBUS2> org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource GSM Jul 17 12:57:07 () Jul 17 12:57:09 MDBUS2> org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Device.SetFunctionality full 1 3846 Jul 17 12:57:13 () Jul 17 12:57:15 works fine Jul 17 12:57:18 kernel is 2.6.32.13 Jul 17 12:58:12 ok Jul 17 12:58:18 http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-2.6.32.13-oe3.2+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0-om-gta02.bin Jul 17 12:58:20 * mickeyl removes dust from his FR Jul 17 12:58:23 :) Jul 17 13:01:02 argh Jul 17 13:01:05 dfu-util: not found Jul 17 13:01:25 mickeyl: if you prefer SD... Jul 17 13:01:35 http://build.shr-project.org/shr-unstable/images/om-gta02/shr-lite-eglibc-ipk--20100714-om-gta02.rootfs.tar.gz Jul 17 13:03:16 jffs2 is ok Jul 17 13:03:17 uploading... Jul 17 13:05:48 with the SetFunctionality including PIN it is still registered... Jul 17 13:06:09 hmm Jul 17 13:06:11 very very strange Jul 17 13:07:42 mrmoku: so when do we collectively switch to n900? ;) Jul 17 13:07:52 mickeyl: hehe :P Jul 17 13:08:08 * mrmoku started to think about where to scratch the money out ;) Jul 17 13:08:32 mickeyl: apart from the money... the only thing hindering me might be the company... dunno Jul 17 13:08:41 the device itself i find very attractive Jul 17 13:09:00 and DocScrutinizer is very satisfied with it Jul 17 13:09:01 *nod* feeling the very same Jul 17 13:09:06 which probably means something :) Jul 17 13:09:25 if we do our own software we don't need the company much though Jul 17 13:09:45 yeah... more about what _they_ do with our money :P Jul 17 13:09:52 hmm, true Jul 17 13:10:17 unfortunately i don't think supporting FSO & SHR is an incentive for Nokia Jul 17 13:10:30 otherwise i would have asked for a bunch of sponsored devices already Jul 17 13:10:37 hehe :) Jul 17 13:10:43 not really yes Jul 17 13:11:06 but it should be easier to get FSO/SHR running on it... compared to dream or pre Jul 17 13:11:19 hopefully Jul 17 13:11:38 after all the pain i've been through with these devices Jul 17 13:11:45 it'd be a welcome change Jul 17 13:11:51 heh, yes :/ Jul 17 13:12:02 still no bluetooth, no ad-hoc wlan, no compass, no acceleroemeter on dream Jul 17 13:12:14 and that for a device that comes with a sort-of-Linux kernel already Jul 17 13:12:16 tsss Jul 17 13:12:43 the only painfree thing was GSM & UMTS Jul 17 13:12:49 http://natisbad.org/N900/n900-commented-hardware-specs.html Jul 17 13:12:58 is quite promissing Jul 17 13:13:13 * mickeyl reads while dfu-util takes ages to pipe bits Jul 17 13:13:23 mickeyl: (do not wait for the POFF answer) should i file a ticket for you not to forget it? Jul 17 13:13:34 PaulFertser: yes, please. Jul 17 13:13:58 this needs infrastructure enhancements, so it's nothing i can do in a handwave :) Jul 17 13:14:28 mrmoku: excellent page Jul 17 13:15:18 mrmoku: is there a chance we could get some more SHR folks on board? Jul 17 13:15:24 i.e. are more people tempted? Jul 17 13:15:51 dos11: what do you think about n900? :) Jul 17 13:16:34 mrmoku: if you'll buy one for me, i'll work on SHR/FSO on it :D Jul 17 13:16:42 dos1: will allow you to cut your fingernails as it has a hw kbd :P Jul 17 13:16:45 done Jul 17 13:16:48 thanks Jul 17 13:17:27 argh Jul 17 13:17:35 kernel too large for NOR uboot Jul 17 13:17:37 *sigh* Jul 17 13:17:54 dos1: unfortunatelly I have to first find the money for mine ;) Jul 17 13:17:56 (excellent page) though not always entirely correct - but that's minor Jul 17 13:19:05 mickeyl: how exactly and when is an app supposed to call SetFunctionality? I used to do that immediately after requesting the resource, now it doesn't. Should i rather do that on any "alive" DeviceStatus? Jul 17 13:19:13 be aware though you got a signed bootloader on OMAP, so we *always* have to go with NOLO, until someone bruteforce breaks the signing key (there are efforts going on) Jul 17 13:20:07 DocScrutinizer: will many users be happy to switch from nokia's way of managing contacts, calls and messages to SHR's? Jul 17 13:20:14 I really doubt that. Jul 17 13:20:15 * DocScrutinizer hears the 'EEEW' and dropping the whole idea Jul 17 13:21:04 PaulFertser: I dunno about SHR current state - last time I tried to use opimd it was ... worthless Jul 17 13:21:18 PaulFertser: this depends on whether i change request resource to wait for ALIVE or not Jul 17 13:21:35 Nokia contacts app is closed source which is generally conceived as a real PITA Jul 17 13:21:35 PaulFertser: i'm toying with the idea of doing that Jul 17 13:21:40 same for dialer Jul 17 13:22:13 mrmoku: hmm, my bad FR charma didn't vanish the months i didn't use it... only thing i get is pages and pages full of alignment traps, I don't think it will finish booting Jul 17 13:22:17 mickeyl: what do other guys think? And how a proper app supposed to act currently (when request resource is not waiting). Jul 17 13:22:28 mickeyl: those are "ok" with latest shr. Jul 17 13:23:08 PaulFertser: if request resource is not waiting, then you're supposed to wait for one of the alive states before doing further actions Jul 17 13:23:25 mickeyl: yup, current OE gives us lots of alignment traps... should boot though Jul 17 13:23:29 DocScrutinizer: people like things that work. Opimd is working mostly as advertised, but i'm not sure anybody's really using it in a user-comfortable way. Jul 17 13:23:39 mrmoku: ok, i'll leave it there for some more minutes then Jul 17 13:23:54 mickeyl: what does theModem.watchdog.resetUnlockMarker do? Jul 17 13:24:43 mickeyl: yes but am i guaranteed that the state would be signalled only once? Can an up unconditionally do SetFunctionality whenever one of the alive- states signalled? Jul 17 13:26:29 mrmoku: resetUnlockMarker cleans the "we did not succeed unlocking the SIM with the PIN we have; to save the SIM don't try it again" and giving the watchdog another chance to unlock the PIN next time an appropriate state change occurs Jul 17 13:27:17 hmm Jul 17 13:27:31 well the major complaints about maemo are the closedness and general crappy functionality of dialer/contacts(/messaging). E.G no contact specific ringtones, no contact groups, call redirection basically nonexistent... same thing for calendar. If "somebody" would start a complete suite of dialer/contacts/calendar apps on opensource, I'm also sure you *could* get devel devices - they are basically handed out on recommendation of Jul 17 13:27:32 maemo community council, and council != Nokia (and even Nokia isn't entirely happy with closed apps, at least they encourrage community to develop alternatives) Jul 17 13:27:35 PaulFertser: yes (to both) Jul 17 13:27:56 if ( pin != "" ) Jul 17 13:27:57 theModem.watchdog.resetUnlockMarker Jul 17 13:28:04 mickeyl: ok, nice. Probably some guidelines in the api docs would help as well :) Jul 17 13:28:31 PaulFertser: for sure. once i'm done with the RequestResource experiment, i'll add more to make the semantics clear Jul 17 13:28:48 mickeyl: thanks a lot :) Jul 17 13:29:23 DocScrutinizer: i'm pretty sure they will not be interested when we tell them we will not use anything of Maemo Jul 17 13:29:29 Are there contact groups in SHR? Jul 17 13:29:43 or you go for meego development and do same over there, so you probably could get devices from Nokia directly Jul 17 13:30:01 mickeyl: they give a shit about maemo now Jul 17 13:30:15 so use maemo, SHR whatever - they don't care anymore Jul 17 13:30:25 maemo us bascally "EOL" Jul 17 13:30:43 PaulFertser: not yet :P Jul 17 13:30:51 *nod* Jul 17 13:30:58 luke-jr got a devel device for gentoo development Jul 17 13:31:04 whom did he contact? Jul 17 13:31:20 mompls lemme di out the url for you Jul 17 13:33:38 http://wiki.maemo.org/Fremantle_Developer_Device_Queue Jul 17 13:35:04 hmm, thanks Jul 17 13:35:13 then there's council (see wiki "community council") which is afaik jaffa, gan900, bt and... err dunno, on #maemo Jul 17 13:35:30 texrat? Jul 17 13:35:37 yep, prolly Jul 17 13:35:56 s/bt/lbt Jul 17 13:36:16 "This is a list of developers who are working on projects for Fremantle" Jul 17 13:36:40 yeah it's a it bitrotten Jul 17 13:37:00 i think i need to find a more direct contact Jul 17 13:37:16 still there are some links in there, and I started off there to get my devel dev Jul 17 13:38:24 chat with gan900 on maemo, tell him greetings of doc and be nice, he's not Nokia, he's the unpaid oncle of community :-D Jul 17 13:39:40 for my case he knew already about hostmode and bme projects. So I suggest you have a decent introductory website to explain to him what all your FSO is all about Jul 17 13:40:12 I think if there was a considerable (_any_) interest in getting FSO or ofono reasonable working on n900, it would have already been done. Jul 17 13:40:18 or SHR phone suite or whatever Jul 17 13:41:11 PaulFertser: interest threshold for starting own work is different from that for supporting other people doing same Jul 17 13:41:13 Provided ofono guys already opensourced the necessary bits for ISI communication, and as far as i heard, they did. Jul 17 13:42:10 Luke Dashjr Jul 17 13:42:11 Gentoo source-based meta-distribution Jul 17 13:42:47 got a devel device with last shipment - be prepared though for months of processing time to get this rolling once again Jul 17 13:42:57 took ~3 months for me Jul 17 13:43:03 iirc Jul 17 13:43:06 DocScrutinizer: FSO2 is running even on the old motorola EZXs nowadays. And ofono actually allows phone calls, so one has enough information. Jul 17 13:43:23 DocScrutinizer: not much longer than purchasing your first one then IIRC ;) Jul 17 13:43:28 PaulFertser: sorry you lost me Jul 17 13:43:49 mrmoku: correct :-D Jul 17 13:43:53 DocScrutinizer: i mean capable devs are not interested in n900 for some reason, i have no idea what that is exactly. Jul 17 13:43:54 PaulFertser: indeed, there is hardly any interest. but since when did that stop us? Jul 17 13:43:56 :) Jul 17 13:44:18 PaulFertser: see mickeyl ^^ Jul 17 13:45:14 i still don't have an open device that covers my needs :/ Jul 17 13:45:39 all the promising devices have issues Jul 17 13:45:42 and i mean really all Jul 17 13:45:52 i can open a museum these days Jul 17 13:45:56 *sigh* Jul 17 13:46:14 PaulFertser: the general conception is maemo is EOL (what's not exactly true as for development of any apps), and meego is pre-natal still, so no fun in developing for it, also meego not officially supported on N900 which might add to the confusion Jul 17 13:46:28 "exhibition of failed FOSS-capable hardware" Jul 17 13:46:35 adults 10 EUR Jul 17 13:46:36 DocScrutinizer: i ~know Jul 17 13:46:37 kids for free Jul 17 13:47:05 heh Jul 17 13:47:23 but anyway see gentoo luke-jr Jul 17 13:47:49 who is a notoric maemo&N900 basher also :-P Jul 17 13:48:11 and really hates Nokia XP Jul 17 13:49:13 for luke-jr even a device wth closed BT-firmware is hardly bearable Jul 17 13:50:26 so if he can get a device, why shouldn't SHR? Jul 17 13:51:21 and if he doesn't refuse to get his fingers dirty and contaminated by touching this awful crap hardware, why should you ;-P Jul 17 13:53:07 hmm Jul 17 13:53:17 wl1251 again Jul 17 13:53:17 but really part of that is about merits and public visibility. None of SHR guys ever shown up in #maemo or related domains yet, so don't expect the red carpet when dropping by asking for free devices Jul 17 13:53:20 no ad-hoc mode Jul 17 13:53:32 yep Jul 17 13:53:56 hmm, almost a deal breaker Jul 17 13:54:22 neopwn maybe has fixed that... not sure Jul 17 13:54:40 DocScrutinizer: hm, some luke-jr bashed me on #openmoko for linking a screenshot of my emacs ui. Jul 17 13:55:07 btw ad-hoc? err there's at least 2 apps to create an AP in N900 Jul 17 13:55:30 i think wl1251 is wrong Jul 17 13:55:32 wut? Jul 17 13:55:39 iirc the n900 has 1271 Jul 17 13:55:41 26-04-2010 00:32:34 < luke-jr!~luke-jr@2002:62b3:1d4c:0:20e:a6ff:fec4:4e5d: it's extremely immodest, and labelled 'hooker'... Jul 17 13:55:44 26-04-2010 00:32:40 < luke-jr!~luke-jr@2002:62b3:1d4c:0:20e:a6ff:fec4:4e5d: back and shoulders showing, even Jul 17 13:55:47 26-04-2010 00:32:55 > PaulFertser: I'm not muslim, right Jul 17 13:55:49 26-04-2010 00:33:39 < luke-jr!~luke-jr@2002:62b3:1d4c:0:20e:a6ff:fec4:4e5d: has nothing to do with islam nonsense Jul 17 13:55:52 PaulFertser: why didn't you call me to kick him? :-P Jul 17 13:55:52 26-04-2010 00:33:55 > PaulFertser: So i clearly labeled an immodest image with "hooker", should be a decent hint, no? Jul 17 13:55:55 26-04-2010 00:34:23 < luke-jr!~luke-jr@2002:62b3:1d4c:0:20e:a6ff:fec4:4e5d: it crossed my mind, but I assumed better of people here and thought it must refer to some phone terminology :( Jul 17 13:56:37 "shoulders showing", ha Jul 17 13:56:48 LOL Jul 17 13:57:01 arguing with luke-jr frequently Jul 17 13:57:37 DocScrutinizer: can you check which wifi chip exactly is used on n900 please? Jul 17 13:57:38 never realized he's on #om Jul 17 13:57:47 sure Jul 17 13:58:28 maybe you could do yourself, using the super-hires scans I published, plus the component placement in schematics? Jul 17 13:59:32 I'll try Jul 17 14:00:17 heh. were there every any super-hires scans of openmoko? ;) Jul 17 14:00:22 s/every/ever/ Jul 17 14:00:23 http://wiki.maemo.org/N900_Hardware_Schematic http://people.openmoko.org/joerg/n900/ Jul 17 14:00:24 lindi- meant: heh. were there ever any super-hires scans of openmoko? ;) Jul 17 14:01:01 lindi-: nobody asked for them, as basically not needed :-P Jul 17 14:03:34 mickeyl: maemo's defconfig says wl1251 module is used. Jul 17 14:03:55 hmm, interesting Jul 17 14:04:13 ok, perhaps different firmware Jul 17 14:04:39 i could not get it to work on the dream Jul 17 14:05:55 mrmoku: hmm, f248cb38db9f531393391984284de96e8ff4e264 is on this image i downloaded Jul 17 14:06:40 check out jokuspot and err... maemo-hotspot? Jul 17 14:07:28 not sure what they do as I never thought burning bat and heat for a AP is a nice thing to do with a cellphone Jul 17 14:07:51 sure Jul 17 14:08:05 anyway airodump 'works' with N900 - though has some weird bug just scanning chan6 Jul 17 14:08:06 nothing beats AP mode in terms of tethering though Jul 17 14:08:09 DocScrutinizer: do you know even modern intel softmac wifi cards do not support AP (iwlagn driver)? Jul 17 14:08:37 but ad-hoc is better than nothing Jul 17 14:08:54 esp. better than BT in terms of compatibility Jul 17 14:10:17 mickeyl: f248 should show it Jul 17 14:10:39 anyway if you're really starting a N900-shr project then let me join for low level consulting Jul 17 14:10:45 mickeyl: just stop phonefsod... kill fsogsmd and try with mdbus2 Jul 17 14:11:18 * mrmoku off for a short 'make him sleep' walk :P Jul 17 14:11:18 yes Jul 17 14:11:25 f248 has the problem Jul 17 14:11:33 but that should be fixed in head Jul 17 14:11:53 +CFUN was called too late Jul 17 14:11:56 that reset your PIN Jul 17 14:12:14 1f2ba4d85be15a75298dbe42ccbc3d45fd0e6bc8 is supposed to fix that Jul 17 14:13:28 lol - on a sidenote: I recently (finally!) enabled service codes on N900 (*#67#...etc), and - on testing it - entered 'change pin' cmd with wrong old pin. three times :-P Jul 17 14:14:56 ;] Jul 17 14:17:43 DocScrutinizer: möööp Jul 17 14:18:00 mööpmööp Jul 17 14:18:04 DocScrutinizer: had your PUK ready? Jul 17 14:18:20 mööpmööp? np: Prodigy - Voodoo People Jul 17 14:18:22 nah, incinerated it 2 years ago when flat burned down Jul 17 14:18:30 ouch Jul 17 14:18:50 but hotline was extremely easy on me Jul 17 14:19:02 took ~5 minutes Jul 17 14:28:00 * von_fritz had a lucky boot and now a working phone :) Jul 17 14:29:56 http://en.wikipedia.org/wiki/Optimism#Health Jul 17 14:33:17 mickeyl: hmm Jul 17 14:35:16 mickeyl: let me build current head, so you can upgrade? Jul 17 14:35:38 mrmoku, no response in oe-devel Jul 17 14:36:52 mrmoku: yes Jul 17 14:37:00 GNUtoo|laptop: :/ Jul 17 14:37:01 hi GNUtoo|laptop, did that compat_wireless work? Jul 17 14:37:02 mickeyl: ok Jul 17 14:37:32 mickeyl, I'll try today Jul 17 14:37:37 good Jul 17 14:37:53 n900 folks obviously can do ad-hoc with their wl1251 Jul 17 14:37:56 i wonder why we can't Jul 17 14:38:04 ahh nice Jul 17 14:38:08 I'll look Jul 17 14:38:14 n900 has wl1271_sdio Jul 17 14:38:15 btw Jul 17 14:38:20 not 1251 Jul 17 14:38:22 ah Jul 17 14:38:24 interesting Jul 17 14:38:26 that's what i thought Jul 17 14:38:27 did you mean n800 Jul 17 14:38:28 ? Jul 17 14:38:32 until someone else said otherwise Jul 17 14:38:55 mickeyl, do you remember oe enough? Jul 17 14:39:00 for waht? Jul 17 14:39:13 did you see initscripts and keymaps message in oe ml Jul 17 14:39:25 yes Jul 17 14:39:47 ah and you have no idea? Jul 17 14:41:37 the problem with IMAGE_INITSCRIPTS is that it is not defined unless you build an image Jul 17 14:42:10 ah ok Jul 17 14:42:17 so what should I do then? Jul 17 14:43:01 k peeps did all I probably can, to help kick off N900 SHR. Keep me on CC please Jul 17 14:44:07 DocScrutinizer: for sure Jul 17 14:44:25 GNUtoo|laptop: well, either remove that dependency from keymap Jul 17 14:44:32 or use the classical weapon for those cases Jul 17 14:44:38 GNUtoo|laptop: i looked at the rx51 defconfig and it had 1251 Jul 17 14:44:39 i.e. make initscripts-shr provide initscripts Jul 17 14:44:44 set the default provider for initscripts to initscripts Jul 17 14:44:49 PaulFertser, ah strange then Jul 17 14:44:50 or introduce a virtual/initscripts Jul 17 14:45:03 mickeyl, ok Jul 17 14:45:14 hmmm Jul 17 14:45:19 that is highly core Jul 17 14:46:10 so for virtual I'll look in the manual Jul 17 14:46:32 well Jul 17 14:46:45 i'd rather recommend just removing the dependency Jul 17 14:46:59 i don't think it's desirable to get initscripts dragged in, if you want keymaps Jul 17 14:47:09 and have some other form of init Jul 17 14:47:35 ok Jul 17 14:47:41 I send a patch then? Jul 17 14:47:45 try to get ACKs for that Jul 17 14:48:09 otherwise we need the big hammer Jul 17 14:48:44 lol Jul 17 14:48:44 ok Jul 17 14:49:34 will you ack it or are you too much involved for beeing impartial Jul 17 14:50:15 i would, yes Jul 17 14:50:27 we have tons of packages that come with an own initscript Jul 17 14:50:35 and none of that directly depends on initscripts Jul 17 14:52:40 mickeyl, fso-specs fails: Jul 17 14:53:04 http://pastebin.com/hkQN5tG2 Jul 17 14:53:29 hmm Jul 17 14:53:56 that's not fso-specs problem Jul 17 14:54:03 rather something in your build Jul 17 14:54:14 No such file or directory: '/home/gnutoo/embedded/oe/oetmps/htcdream/sysroots/armv6-novfp-oe-linux-gnueabi/shlibs/libgsm0710mux.list' Jul 17 14:57:19 DocScrutinizer: it's impossible to tell the wlan chip from the scans -- hidden under the shield. Jul 17 14:57:36 shit!! Jul 17 14:58:05 coords in comp plcmnt? Jul 17 14:58:10 partnr? Jul 17 14:58:57 mickeyl, ok maybe race condition Jul 17 14:59:14 DocScrutinizer: n6300 J10 Jul 17 14:59:21 k Jul 17 14:59:37 DocScrutinizer: but the defconfig pretty much says about it already. Jul 17 14:59:46 DocScrutinizer: or you can simply take a look at your dmesg. Jul 17 15:01:52 dmsg no problem Jul 17 15:02:06 I see, a fsckng module Jul 17 15:05:16 [ 6.527282] wl1251: loaded Jul 17 15:05:17 [ 6.527984] wl1251: initialized Jul 17 15:05:45 [ 49.100494] wl12xx spi4.0: firmware: requesting wl1251-fw.bin Jul 17 15:05:47 [ 49.347137] SCSI subsystem initialized Jul 17 15:05:48 [ 49.822601] Driver 'sd' needs updating - please use bus_type methods Jul 17 15:05:50 [ 50.248748] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 Jul 17 15:05:51 [ 50.264404] wl1251: firmware booted (Rev 4.0.4.3.7) Jul 17 15:05:53 [ 51.311401] wl1251: down Jul 17 15:05:54 [ 51.881530] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 Jul 17 15:05:56 [ 51.897247] wl1251: firmware booted (Rev 4.0.4.3.7) Jul 17 15:05:57 [ 52.889770] wlan0: direct probe to AP 00:13:49:e0:de:dc try 1 Jul 17 15:05:59 [ 52.892944] wlan0 direct probe responded Jul 17 15:06:00 [ 52.892974] wlan0: authenticate with AP 00:13:49:e0:de:dc Jul 17 15:06:36 hmm, we should diff the firmware Jul 17 15:07:02 mickeyl, libfsobasics: http://pastebin.com/Z761sPZf ( | ERROR:valasemanticanalyzer.c:2926:vala_semantic_analyzer_get_actual_type: assertion failed: (instance_type != NULL))] Jul 17 15:07:05 post to you anytime ... ooops didn't say that ;-) Jul 17 15:07:11 GNUtoo|laptop: which version does our wl report? Jul 17 15:07:12 gnutoo: pull Jul 17 15:07:13 mickeyl, what firmware? I was offline Jul 17 15:07:22 [ 50.264404] wl1251: firmware booted (Rev 4.0.4.3.7) Jul 17 15:07:23 mrmoku, ok Jul 17 15:07:30 gnutoo: bitbake vala-native Jul 17 15:07:39 (0.9.3.2 is up) Jul 17 15:07:43 I'll pull Jul 17 15:07:48 ah ok Jul 17 15:07:55 I've updated mine Jul 17 15:07:55 mickeyl: it built automatically for me :) Jul 17 15:08:03 I've taken it from cyanogen mod Jul 17 15:08:59 they still distribute proprietary firmware? Jul 17 15:09:14 old version only Jul 17 15:14:25 mickeyl: btw, the driver for wl1271 is available in mainline, but firmware is to be found nowhere :O Jul 17 15:15:48 PaulFertser, mickeyl firmware will be uploaded on ti's website soon Jul 17 15:16:45 gnutoo: that doesn't make the situation sound less stupid Jul 17 15:17:06 why? Jul 17 15:17:40 sure it's stupid Jul 17 15:17:48 but luckily everyone has access to it who needs it Jul 17 15:17:52 gnutoo: i see no sense at all in not providing your customers with the firmware. Jul 17 15:17:53 it's right on your NAND Jul 17 15:18:18 indeed Jul 17 15:22:22 It makes perfect sense, it's a corporation, they need to make profit Jul 17 15:23:12 thrashold: how on earth is that related? Jul 17 15:25:32 http://wiki.maemo.org/N900_ad_hoc_wifi_hotspot Jul 17 15:25:35 Providing customers with firmware for outdated hardware only hurts profits Jul 17 15:26:15 Providing customers with anything additional for free hurts profits Jul 17 15:26:28 thrashold: that's not outdated, and not additional Jul 17 15:28:19 Oh, that's a firmware for hardware of an HTC phone? Jul 17 15:28:41 Providing firmware allows tinkering Jul 17 15:29:41 thrashold: firmware for chipset, which you need to have to use it at all AFAIK Jul 17 15:30:00 mickeyl: build finally finished... you could upgrade Jul 17 15:30:06 ok Jul 17 15:30:20 dos1: Well, the proprietary OS that comes with it already has it, right? So if you don't tinker with it, it works Jul 17 15:31:00 it's on devices, but not on website Jul 17 15:31:20 Common practice Jul 17 15:31:37 ~seen morphis Jul 17 15:31:40 morphis <~morphis@p5489B196.dip.t-dialin.net> was last seen on IRC in channel #openmoko-cdevel, 15d 20h 42m 33s ago, saying: 'heyho'. Jul 17 15:31:40 and i think that's what mickeyl said "sure it's stupid" about Jul 17 15:33:06 Once you replaced the software of your phone, you can't get your WiFi working, so you have to revert to original software (is *that* available online?) Jul 17 15:33:25 Until some nice hungarian website puts the wl1251 firmware for public access Jul 17 15:34:03 thrashold: i think the firmware that comes on NAND is incompatible with the upstream drivers developed by the same corporation. Jul 17 15:34:15 Or else there weren't any problems. Jul 17 15:34:50 PaulFertser: don't you remember what's normal power consumption in mA while deep sleep is on? Jul 17 15:35:09 Q-Master: in suspend should be around ~4mA Jul 17 15:35:23 Q-Master: gives ~140hrs in suspend Jul 17 15:35:35 I've charged the neo today morning and now it has only 55% of battery while was in suspend Jul 17 15:36:03 It shows me 140mA now with 65% of backlight Jul 17 15:36:24 Q-Master: something sounds wrong (in suspend) Jul 17 15:36:44 yep. Jul 17 15:36:54 that started after a kernel switch Jul 17 15:38:03 I need to check the consumption in suspend. need to think of how to do so Jul 17 15:38:29 buy a proper PSU and hook it carefully to the battery terminal Jul 17 15:39:18 mickeyl: what psu? Jul 17 15:39:33 anyone decent one will do Jul 17 15:39:34 Proper Jul 17 15:39:36 :)))) Jul 17 15:39:38 :D Jul 17 15:40:01 Q-Master: absolute maximum is 5.5V though! Jul 17 15:40:05 i have a VLC2403pro Jul 17 15:40:09 and am satisfied with it Jul 17 15:40:10 I'll use an milliampermeter instead. Jul 17 15:40:33 Q-Master: you can try to suspend the device for some time, then read the current_now property immediately after that. Usually gives good enough results. Jul 17 16:06:23 mickeyl: can you reproduce it with current HEAD? Jul 17 16:06:24 or read out standby values Jul 17 16:19:32 PaulFertser: tried the last method you've told Jul 17 16:19:39 PaulFertser: very bad results Jul 17 16:20:15 PaulFertser: 52, 45 and 41 mA after resume. 8( Jul 17 16:21:27 Q-Master: what kernel? Jul 17 16:21:30 Q-Master: blame canada Jul 17 16:21:49 lindi-: 2.6.32 Jul 17 16:21:56 PaulFertser: ? 8/ Jul 17 16:22:22 Q-Master: please do report this as a bug Jul 17 16:22:23 Q-Master: that's from "south park" Jul 17 16:23:31 JaMa|Swim, mrmoku|dinner ^^^^ Jul 17 16:27:34 mrmoku|dinner: yes, the problem is Jul 17 16:28:05 CFUN=1 -> CME ERROR 100 Jul 17 16:50:46 mickeyl: I have a popup message that I need to delete some smses from sim or else I will not receive any other Jul 17 16:50:50 mickeyl: how? Jul 17 16:52:56 Q-Master: something along the lines of this: mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.SIM.DeleteMessage '1' Jul 17 16:53:11 replacing 1 with the number of the message you want to delete Jul 17 16:53:14 sicu: thnx Jul 17 16:53:37 Q-Master: yw Jul 17 16:53:52 Q-Master: you can use direct delivery with modern fsogsmd versions. Jul 17 16:54:11 PaulFertser: how? Jul 17 16:55:47 Q-Master: sim_buffers_sms = false Jul 17 16:55:50 in [fsogsm] Jul 17 16:55:57 ah. ok Jul 17 16:57:54 iirc SHR is using this already Jul 17 16:58:17 Yes, by default. Jul 17 16:58:33 so they probably left the message check by accident in Jul 17 17:05:07 mickeyl: deleted 7 messages Jul 17 17:05:21 excellent Jul 17 17:11:39 mickeyl: CME 100... unkown calypsoism? :P Jul 17 17:11:43 +n Jul 17 17:11:54 unknown error... fun, yeah Jul 17 17:12:33 i try to change that part to call it multiple times until it either OKs or errors out with an expected error Jul 17 17:12:42 that involves some more infrastructure though Jul 17 17:13:09 in the meantime, you could try to do it two or three times in a row Jul 17 17:14:22 mickeyl: hmm.. ok Jul 17 17:19:31 mrmoku: check the devel list and try the script plz. need some statistics. Jul 17 17:29:29 Q-Master: will do when GSM is working again Jul 17 17:31:57 thanks mickeyl Jul 17 17:32:51 gnutoo: how about going for the N900 instead of the Palm Pre? Jul 17 17:33:05 price should be more or less the same Jul 17 17:33:29 mickeyl, price is outrageous in arcachon Jul 17 17:33:50 400@ on ebay Jul 17 17:33:50 instead of 429E they sell it more than 700E Jul 17 17:34:14 mickeyl, the only advantage of palm pre is the ram Jul 17 17:34:18 it has 512M Jul 17 17:34:20 but... Jul 17 17:34:28 I prefer the huge screen of n900 Jul 17 17:34:36 800x480 Jul 17 17:35:27 anyway htcdream has gps etc... Jul 17 17:38:24 hmm Jul 17 17:38:29 let me try that again on mine Jul 17 17:40:41 ok Jul 17 17:40:57 hmm Jul 17 17:40:58 interesting Jul 17 17:41:01 need to go upstairs Jul 17 17:41:05 ok Jul 17 17:41:16 try: Jul 17 17:41:18 gps Jul 17 17:41:26 grep GPGGA /dev/smd27 Jul 17 17:41:33 but I bet you know that Jul 17 17:43:26 bbs Jul 17 17:45:11 hi JaMa|Swim Jul 17 17:59:48 mickeyl, http://natisbad.org/N900/n900-commented-hardware-specs.html says it's wl1251 Jul 17 18:01:05 hmmm Jul 17 18:01:07 hmmm Jul 17 18:01:11 where are nokia's sources? Jul 17 18:01:58 GNUtoo|laptop: http://meego.gitorious.com/ Jul 17 18:02:06 thanks Jul 17 18:02:25 for kernel http://meego.gitorious.com/meego-os-base/kernel-source Jul 17 18:05:25 # CONFIG_WL1271 is not set Jul 17 18:05:30 CONFIG_WL1251=m Jul 17 18:05:34 CONFIG_WL1251_SPI=m Jul 17 18:05:55 (from config-arm-n900) Jul 17 18:06:00 ah SPI Jul 17 18:06:01 ok Jul 17 18:06:04 so not used Jul 17 18:06:12 s/used/usable Jul 17 18:06:26 * GNUtoo|laptop will retry psm soon with a more recent wireless-compat Jul 17 18:06:37 trying now with an old compat wireless Jul 17 18:07:41 SHR: 03mok 07phonefsod * r28c6005d8653 10/ (4 files in 2 dirs): make PIN for the SIM configurable in phonefsod.conf Jul 17 18:08:59 I'll retry multiple times Jul 17 18:09:06 to see if I get the same error message Jul 17 18:09:24 mickeyl: I will do something different for now... people can put their PIN in phonefsod.conf and it will be sent with SetFunctionality Jul 17 18:09:51 mickeyl: next will be to send the PIN from the auth dialog to phonefsod, which will send it again with SetFunctionality Jul 17 18:10:07 mickeyl: maybe with a nice 'remember PIN' checker :) Jul 17 18:10:58 hmm... actually... bad idea if one is swapping SIM card :/ Jul 17 18:15:10 time for some relax Jul 17 18:19:28 mickeyl, http://meego.gitorious.com/meego-cellular/blts-ofono/blobs/master/blts-ofono/README Jul 17 18:19:33 there is a test app for ophono Jul 17 18:24:41 mrmoku|away: thanks for the temp workaround, it's working nicely apart from the initial slowness in getting a GSM fix Jul 17 18:54:45 mrmoku|away: sounds good Jul 17 19:14:32 freesmartphone.org: 03mickey 07utilities * rc541c41b90ef 10/android/rpc/ (4 files in 2 dirs): android-rpc: add pkgconfig file and install header files Jul 17 19:26:32 freesmartphone.org: 03mickey 07cornucopia * re5914489c0f3 10/fsodeviced/ (5 files in 3 dirs): Jul 17 19:26:32 freesmartphone.org: fsodeviced: add skeleton for htcdream_powercontrol Jul 17 19:26:32 freesmartphone.org: On the HTC Dream, GPS is exposed through the native ARM11/ARM9 RPC Jul 17 19:26:32 freesmartphone.org: interface, hence we need to walk an extra-mile hiding this behind Jul 17 19:26:32 freesmartphone.org: our abstraction. Jul 17 19:48:54 freesmartphone.org: 03mickey 07utilities * r72b90c4185c3 10/android/rpc/rpc/ (pmap_clnt.h rpc.h svc.h): android: rpc: make sure we don't mix headers with "that other" RPC implementation Jul 17 19:49:11 freesmartphone.org: 03mickey 07cornucopia * r1b87ece2a233 10/fsodeviced/ (5 files in 3 dirs): fsogsmd: htcdream_powercontrol: make it compile Jul 17 20:01:16 freesmartphone.org: 03mickey 07cornucopia * rd87dc2ede31f 10/fsodeviced/src/plugins/htcdream_powercontrol/ (gps.c plugin.vala): fsodeviced: htcdream_powercontrol: first sketch at implementation Jul 17 20:05:47 freesmartphone.org: 03morphis 07msmcomm * r4ab729811bd8 10/configure.ac: msmcomm: we do not depend on gtk+ any longer (was needed for msmsh) Jul 17 20:05:51 freesmartphone.org: 03morphis 07msmcomm * rc982761a01b5 10/msmcommd2/src/ (linklayercontrol.vala util.vala worker.vala): Jul 17 20:05:51 freesmartphone.org: msmcommd2: buffer incomming data until we have a complete frame Jul 17 20:05:51 freesmartphone.org: Some messages from the modem recives by more than one read operation. So we need to buffer Jul 17 20:05:51 freesmartphone.org: the data until we have all bytes for the complete frame. Jul 17 21:48:40 Hey Jul 17 21:48:46 Hm Jul 17 21:49:31 Amicer: so you got the htc dream (tmo g1) and want to run shr ? Jul 17 21:49:39 yeah Jul 17 21:49:52 Amicer: and you are using which files ? Jul 17 21:49:55 i got CM6 running allready, from what i see it will override it and thats the thing i dont want Jul 17 21:50:06 http://ftp.o2s.ch/pub/openmoko/htcdream/repo/images/htcdream/shr-full-eglibc-ipk--20100524-htcdream.rootfs.tar.bz2 Jul 17 21:50:11 Amicer: what is CM6 ? Jul 17 21:50:25 CyanogenMod6 Jul 17 21:50:29 haha Jul 17 21:50:30 ok Jul 17 21:50:40 Custom android mod, currently running on Android 2.2 Jul 17 21:51:03 so i has froyo on G1 Jul 17 21:51:03 Amicer: I find it funny they call it mod Jul 17 21:51:10 froyo ?!?! Jul 17 21:51:16 yeah Jul 17 21:51:17 you spill dessert on expensive device. Jul 17 21:51:29 meh Jul 17 21:51:36 moo Jul 17 21:51:50 the thing i dont like about froyo is launcher 2, looks strange Jul 17 21:52:06 Amicer: please explain how you installed your mod Jul 17 21:52:13 hm Jul 17 21:52:16 i dont really remember Jul 17 21:52:43 first was the Goldcard so i can get to lower firmware and root my phone, then installing custom recovery and flashing to cyanogen mod Jul 17 21:53:00 Amicer: leviathan wants you to format your sd card to extract the rootfs you linked above to it Jul 17 21:53:03 Amicer: http://wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream#Setup_the_rootfs Jul 17 21:53:30 ask him if i will be able to select system Jul 17 21:53:49 do you understand that ? Jul 17 21:53:55 yeah Jul 17 21:54:04 i allready got one vfat, ext3 and swap Jul 17 21:54:05 do you have multiple sd cards ? Jul 17 21:54:05 :p Jul 17 21:54:10 one Jul 17 21:54:28 does android live on ext3 ? Jul 17 21:54:41 nope Jul 17 21:54:51 internal storage Jul 17 21:54:51 then it won't be gone after you install openmoko. Jul 17 21:54:57 mm Jul 17 21:55:02 wait, how openmoko works Jul 17 21:55:07 you launch phone just normal Jul 17 21:55:17 or you launch with some key combination Jul 17 21:55:33 if its home+turn on then it'll replace my recovery Jul 17 21:56:06 Amicer: this is not specific to openmoko Jul 17 21:56:16 Amicer: question should be: how htc dream bootloader works Jul 17 21:56:42 ask leviathan Jul 17 21:56:46 he should know if he uses it Jul 17 21:57:17 Amicer: uhm Jul 17 21:57:27 hmm Jul 17 21:57:38 i actually found neat article on xda developers Jul 17 21:57:42 dualbooted Jul 17 21:58:02 it doesnt replaces the bootloader Jul 17 21:58:05 but rec image Jul 17 21:58:26 aaand wow Jul 17 21:58:29 openmoko is small Jul 17 21:58:38 :-) Jul 17 21:58:40 of course it's not bloated java piece of bullshit Jul 17 21:58:54 oh, hey Jul 17 21:58:59 i mean it is REALLY small Jul 17 21:59:16 native debian would weight much more x.x Jul 17 21:59:26 Amicer: yea Jul 17 21:59:36 leviathan, so you replace the bootloader yes? Jul 17 21:59:39 we stripped it down Jul 17 21:59:47 Amicer: we have fastboot Jul 17 22:00:03 you turn on phone holding 'red' phone and it boots it? Jul 17 22:00:08 or you NEED to use fastboot Jul 17 22:01:15 Hmm... actually THIS is interesting http://forum.xda-developers.com/showpost.php?p=5521417&postcount=5 Jul 17 22:01:28 OpenMoko with bootloader as recovery mage Jul 17 22:01:31 image Jul 17 22:01:36 old version to Jul 17 22:01:37 tho Jul 17 22:02:14 ok Jul 17 22:02:24 there are other people working on the same project? Jul 17 22:05:01 leviathan , if i install openmoko as on wiki, will i be able to get to android anytime? Jul 17 22:05:18 Amicer: uhm Jul 17 22:05:19 nope Jul 17 22:05:22 yeah Jul 17 22:05:33 will be broken Jul 17 22:05:34 totaly Jul 17 22:05:36 dead Jul 17 22:05:37 here what it does is install to sdcard (as on wiki) but uses recovery image as bootloader Jul 17 22:05:38 ex-android Jul 17 22:05:40 -_- Jul 17 22:05:54 so you can simply reboot to other OS Jul 17 22:06:59 leviathan : was it true or me not recornizing sarcasm Jul 17 22:07:17 hmm Jul 17 22:07:32 perhaps they tinkered around with this specific openmoko rootfs Jul 17 22:07:46 but android kernel image needed by android Jul 17 22:07:51 is unusable for gnu linux Jul 17 22:07:54 and vise versa Jul 17 22:08:07 if they would have used official kernel api Jul 17 22:08:12 it would not occur Jul 17 22:08:16 but we have this problem Jul 17 22:08:18 -.- Jul 17 22:08:29 :"I made myself a recovery image that would consist of the most recent OpenMoko kernel from gitorious AND FukTheRegister's ramdisk (I just glued them together and threw away some modules to make it fit into 5Mb - maximum for recovery partition images)" Jul 17 22:08:37 It means that they use other kernels Jul 17 22:08:40 :3 Jul 17 22:09:23 So, other for android and other for openmoko, because 2 other images boot, Jul 17 22:11:16 What i am not happy about is that it will replace my JF recovery image, but i think ill have 2 images at once and flash whenever i need. Jul 17 22:14:10 leviathan : is around 400mb good for openmoko? Jul 17 22:18:25 Amicer: what is openmoko? you mean SHR? Jul 17 22:19:17 yeah, on G1 Jul 17 22:19:33 Amicer: yea, its enough Jul 17 22:19:43 you'll need at least 200MB Jul 17 22:31:08 Got all files on my vfat (i use windows, i need to copy things twice...) ill format swap to ext3 and try to run it Jul 17 23:59:33 leviathan: maybe you should add more noob friendly walkthrough Jul 18 00:08:38 dcordes: yea Jul 18 00:08:44 I'll think about it Jul 18 00:08:46 :-) Jul 18 00:11:04 so I'll go sleep Jul 18 00:11:48 nn **** ENDING LOGGING AT Sun Jul 18 02:59:56 2010