**** BEGIN LOGGING AT Wed Oct 17 03:00:01 2012 Oct 17 13:15:50 GNUtoo-desktop: you alsa distro feature merged with only one added PRINC, thanks Oct 17 13:15:56 s/you/your/ Oct 17 13:15:57 JaMa meant: GNUtoo-desktop: your alsa distro feature merged with only one added PRINC, thanks Oct 17 13:16:15 ok thanks a lot Oct 17 13:16:31 btw I pushed a commit to fix libsdl in the shr's oe-core repo on git.shr Oct 17 13:16:53 seen that, looks correct Oct 17 13:16:56 ok Oct 17 15:00:12 GNUtoo-desktop: hi, I get issues with ext3 on my g1 http://bpaste.net/show/51797/ Oct 17 15:00:28 every other boot or so it's mounted readonly Oct 17 15:00:41 hi Oct 17 15:01:10 ccxCZ, how did you install? Oct 17 15:01:43 kernel in recovery, ext3 on sdcard Oct 17 15:02:02 just mkfs.ext3 I believe, maybe upped the inode count a bit Oct 17 15:02:50 ccxCZ, hmmm Oct 17 15:02:54 retry Oct 17 15:03:06 because there is obviously a filesystem corruption Oct 17 15:03:10 like fdisk Oct 17 15:03:14 then mkfs Oct 17 15:03:31 also we are looking for a maintainer for the htc dream Oct 17 15:03:32 just taken it out so I can fsck it Oct 17 15:03:36 ok Oct 17 15:07:58 I assume there is no reasonable way to use fsck on the device, since one has to start X Oct 17 15:09:45 that said, is there simple way to boot into fbcon instead of x11? Oct 17 15:11:08 ccxCZ, there isn't yet Oct 17 15:11:24 Xorg and fbcon conflicts on that device Oct 17 15:11:50 so completely different kernel is needed, right? Oct 17 15:12:27 same kernel, compiled with fbcon option Oct 17 15:12:35 and one more question: how hard would it be to tweak fsodeviced (or whatever does that) to go to sleep and wakeup on keyboard slide in/out instead of timeouts/locks/whatever? Oct 17 15:12:47 well yeah, different compiled kernel binary Oct 17 15:12:52 it should be easy enough Oct 17 15:13:02 but we need to talk first Oct 17 15:13:12 because we're really looking for a maintainer for the htc dream Oct 17 15:13:46 what do you want to use on it? Oct 17 15:13:48 SHR ? Oct 17 15:13:50 debian? Oct 17 15:13:54 something else? Oct 17 15:14:15 gentoo preferably Oct 17 15:14:39 shr is fun too really, but not for my usecase Oct 17 15:15:02 ah ok you were the gentoo person Oct 17 15:15:04 I'd volunteer if I had some free time left - which doesn't seem to be the case atm Oct 17 15:15:37 basically you just have to work on what you want and make the port progress somehow Oct 17 15:16:25 since you want gentoo, you will probably want to contribute to fso+kernel only and not to SHR stuff Oct 17 15:17:31 the thing is that I don't really use the phone subsystem at all, so I can't tell if I break it horribly Oct 17 15:18:26 basically just make it work for your use case Oct 17 15:18:37 for instance in SHR there is JaMa Oct 17 15:18:54 he has nearly the same use case than you: he doesn't uses the phones as a phone Oct 17 15:20:08 basically we have suported and unsuported devices Oct 17 15:20:32 the only thing that is required for making a device supported or WIP is to have actual work done on it Oct 17 15:20:35 whatever it is Oct 17 15:21:00 there is no other obligations Oct 17 15:21:10 and if you stop working on it there is no issues either Oct 17 15:21:20 we would just put back the device to unsuported Oct 17 15:21:28 or rather "Looking for a maintainer" Oct 17 15:21:32 and I can even help Oct 17 15:21:56 basically we abandoned some devices because no one was working on them anymore and that I had too much devices to cope with Oct 17 15:22:56 ccxCZ, what are you trying to boot btw? Oct 17 15:22:57 well, I can't promise anything atm, but I want to get the device to useful state eventually Oct 17 15:22:58 gentoo? Oct 17 15:23:05 yes that's good Oct 17 15:23:12 I have shr + gentoo chroot atm Oct 17 15:23:17 ok Oct 17 15:23:40 wanted recent kernel and booting directly as a next step Oct 17 15:23:57 [48606.449615] mmcblk0: error -110 transferring data, sector 22477928, nr 40, card status 0xc00 Oct 17 15:24:01 recent kernel may be hard Oct 17 15:24:08 but doable if you have serial Oct 17 15:24:17 I do have serial btw Oct 17 15:24:32 maybe bad microsd card? Oct 17 15:24:46 sounds like soldering :] Oct 17 15:24:59 because the htcdream is known to support well microsds.... Oct 17 15:25:06 yes you have to solder a cable.... Oct 17 15:25:16 no soldering inside the phone required Oct 17 15:25:57 if there's some header or so inside it shouldn't be that much of a problem Oct 17 15:26:17 I'm not sure about the header.... Oct 17 15:27:30 well, should be doable at least, but not my concern atm Oct 17 15:28:03 I want to get current setup working and be useful before I'll go upgrading it Oct 17 15:28:41 ok Oct 17 15:28:44 try booting SHR Oct 17 15:29:08 note that you need to use a microsd reader on a computer to do the install Oct 17 15:29:19 and not trough the phone and exported by android Oct 17 15:29:32 but I guess you did it the right way Oct 17 15:29:36 according to your dmesg Oct 17 15:29:44 it's rather that your microsd card seem bad Oct 17 15:30:19 yes, the occasional fs failure and powermanagement not behaving the way I like are the main stoppers for me Oct 17 15:30:26 otherwise it runs well Oct 17 15:30:59 the microsd is a brand new one btw, the old one was indeed misbehaving Oct 17 15:31:50 ok Oct 17 15:31:59 the dmesg was with the brand new? Oct 17 15:32:25 yup. while rsyncing big directory tree in there Oct 17 15:32:52 but some fsck found some errors and corrected them, so hopefully it will be better now Oct 17 15:33:03 but I'm still concerned how they came to be Oct 17 15:33:15 ok Oct 17 15:35:08 booted and seems to work, will reboot once more to check Oct 17 15:38:57 ok. so this would resolve the fs stuff Oct 17 15:40:21 ok Oct 17 15:44:26 I'm ogling the dbus docs, but they only seem concerned with timeouts, whereas I want no timeout, just pure switch on keyboard state Oct 17 15:47:00 hrm, which fso repo is deviced in? Oct 17 15:50:25 I just don't see it http://git.freesmartphone.org/ Oct 17 15:51:15 ccxCZ, let me look again at what you want to do Oct 17 15:51:43 look at fsousaged Oct 17 15:51:57 and try to make a setting for resuming on keyboard slide Oct 17 15:52:04 that plugin more precisely: Oct 17 15:52:38 http://git.freesmartphone.org/?p=cornucopia.git;a=blob;f=fsousaged/src/plugins/lowlevel_android/plugin.vala;h=bf1204246b5515263f12a341db060a65111c2cf3;hb=HEAD Oct 17 15:53:09 404 Oct 17 15:53:50 so I should clone cornucopia, right? Oct 17 15:54:16 hmmm Oct 17 15:54:18 yes Oct 17 15:54:27 and the plugin has changed over time Oct 17 15:54:37 (to support newer android devices) Oct 17 15:56:37 actually that's probably the only fso daemon I have interest in running, but I assume they are interdependent Oct 17 15:57:04 you need fsodeviced and fsousaged Oct 17 15:57:05 not more Oct 17 15:57:14 that's the bare minimum I think Oct 17 15:57:18 ok Oct 17 15:58:15 out of curiosity, do you know if this style of wakeup has been merged into vanilla? Oct 17 15:59:28 not as-is Oct 17 15:59:36 but I think there is something Oct 17 16:00:12 but I don't remember its name Oct 17 16:00:23 (the name of the wakelocks mainline equivalent) Oct 17 16:03:15 looking at fsousaged/src/lib/lowlevel.vala Oct 17 16:03:36 also look at old versions of lowlevel_android/plugin.vala Oct 17 16:03:44 is ResumeReason.Slider what I want? Oct 17 16:05:02 how old? Oct 17 16:05:22 let me look Oct 17 16:05:34 just do a git log on lowlevel_android/plugin.vala Oct 17 16:06:21 25e38610c9c84e9fc50175255b1a0c8ae8f6f828 maybe Oct 17 16:07:05 now just to find what is revert called in git-speak :] Oct 17 16:09:08 git checkout 25e38610c9c84e9fc50175255b1a0c8ae8f6f828 -b htcdream -> checkout the right version Oct 17 16:09:09 or: Oct 17 16:09:21 thanks, got it Oct 17 16:09:23 git log -- fsousaged/src/plugins/lowlevel_android/plugin.vala Oct 17 16:09:42 what happened is that Oct 17 16:10:00 well, this file is indeed more interesting Oct 17 16:10:07 at some SHR meeting we decided to stop maintaining some devices, including the htcdream Oct 17 16:10:30 has the proper paths it seems, I might be able to implement it as a shell script even Oct 17 16:11:06 then morphis(Simon Busch) wanted to add support for a better phone: the nexus S Oct 17 16:11:58 so since the htcdream was not maintained anymore, he repurposed the htcdream suspend/resume plugin for the nexus S....without caring about not breaking the htcdream..... Oct 17 16:12:12 ic Oct 17 16:12:35 so now the thing to do is: Oct 17 16:12:45 1) look at the old version of the htcdream plugin Oct 17 16:12:53 2) find out how he did it for the nexus S Oct 17 16:13:07 3) adapt the old version of the htcdream plugin to the new way Oct 17 16:13:17 because in one of the commit he said: Oct 17 16:13:49 This removes the powerkey handling too. Handling system wakeup when the power key is pressed should be done somewhere else and the usage subsystem will be triggered via the org.freesmartphone.Usage.Resume method to completely wakeup. Oct 17 16:14:11 so we must find where this "somewhere else" is Oct 17 16:15:17 yeah, I've only seen keycode in a conf in the recent usaged Oct 17 16:16:23 found it Oct 17 16:16:25 here: Oct 17 16:16:43 fsodeviced/src/plugins/herring_quirks/resumehandler.vala Oct 17 16:16:50 in master branch Oct 17 16:17:01 that is to say you checked out a special commit Oct 17 16:17:05 that's after that commit Oct 17 16:17:12 so re-checkout master Oct 17 16:17:16 to see that Oct 17 16:17:50 I'll make separate dir for the new one so I don't confuse them Oct 17 16:19:21 ok Oct 17 16:25:42 I'm trying to strace the fsousaged to see how it gets the keyboard slide signal (seems to be from /dev/input/event* according to the old source) but I just don't see it Oct 17 16:26:47 yes it's from there Oct 17 16:27:01 if it's in the source.... Oct 17 16:27:09 but your source may not match your binaries Oct 17 16:34:03 gah, I'm only seeing some traffic on a pipe to itself, wakeup signal presumably Oct 17 16:34:30 it is quite possible the usaged doesn't really detect keyboard slide Oct 17 16:35:52 SYS_297 seems strace can't show recvmsg properly 0_o Oct 17 16:35:57 hmmmm Oct 17 16:36:23 try with evtest Oct 17 16:37:00 ousaged dont detect keyboard unless you tell him to I guess Oct 17 16:37:10 *fsousaged Oct 17 16:39:02 Event: time 3644.768405, type 5 (?), code 0 (?), value 0 Oct 17 16:39:04 Event: time 3646.802707, type 5 (?), code 0 (?), value 1 Oct 17 16:39:13 got them on /dev/input/event3 Oct 17 16:41:20 ok Oct 17 16:41:48 so usaged/deviced should be able to handle this definitely, just a matter of tweaking Oct 17 16:50:10 yes Oct 17 16:50:25 just write a quirks plugin.... Oct 17 16:54:00 bbl Oct 17 16:54:31 well, I have more urgent stuff now too, so I'll look into it later Oct 17 16:54:36 but thanks a lot **** ENDING LOGGING AT Thu Oct 18 03:00:01 2012