**** BEGIN LOGGING AT Tue Feb 23 02:59:58 2010 Feb 23 11:33:08 hi all Feb 23 12:22:56 while I understand the point of that "smartphone security" report, I don't quite understand how it qualifies as "research" to demonstrate that you can run bad programs on a smartphone Feb 23 12:24:09 * JaMa agree Feb 23 12:25:27 the same point would be that with enough time every computer can spy on it's users, but only change that desktops usualy don't have embedded gps to inform spying agent about position.. but that can be secretly plugged too :) Feb 23 12:25:50 hmm yeah Feb 23 12:26:07 not much science about that Feb 23 12:26:19 some of this type of research is interesting because it describes interesting new types of vulnerability or so on, but I don't see what this tells us that we didn't already know Feb 23 12:26:49 (maybe I'm just jealous because of the amount of work I have to do in my own science to do something new) Feb 23 12:28:25 "Also, features such as Bluetooth receivers and text messaging make it easier to deliver rootkits to phones." wrt "E-mails, l-users running every received exe named hot-pics.img.exe and all types of worms, makes it imho much more easier on desktop than on phones. Feb 23 12:28:50 And I have much more personal information stored on computer than phone Feb 23 12:31:04 whole story is returning me "UnicodeEncodeError", but from that www.technewsdaily.com article I don't see how they deliver their rootkits.. Feb 23 12:31:45 if they install it over usbnet having root account and phone physicaly.. then it's really nothing new Feb 23 12:32:40 that's what they say.. see my quote on OM-Community Feb 23 12:33:54 there are no interesting vulnerabilities, classes of attack, trojan delivery, or anything like that Feb 23 12:38:35 slightly more interesting is the flash vulnerability Feb 23 12:38:47 most phones you can flash without any passwords Feb 23 12:39:40 also, +1 for Al Johnson's post just now, thinking sensibly about "root=bad" Feb 23 14:36:12 hi im interested in buying a phone but kinda turned off by the 400mhz cpu and 128mb ram Feb 23 14:36:18 isnt that very little today? Feb 23 14:36:32 how fast is android/shr/and qtopia Feb 23 14:38:05 when will the next gen come out? Feb 23 15:21:46 hey Feb 23 15:22:09 how can i delete all user-based settings from my moko? Feb 23 15:22:15 where are they hided? Feb 23 15:22:22 (want to reset a bit ;)) Feb 23 15:25:37 hey dos Feb 23 15:25:39 :=) Feb 23 15:25:50 can i ask you something? Feb 23 15:55:55 Hardy_: what are looking for? Feb 23 15:57:40 i already rewrited my moko ^^ so its to late ^^ but thanks :) Feb 23 15:58:29 got problems with gsm Feb 23 15:58:33 wouldnt start Feb 23 15:58:42 eather after reflash Feb 23 15:58:58 (like it seems atm) Feb 23 16:00:37 Hardy_: ok Feb 23 16:03:56 no wouldnt start Feb 23 16:04:02 is there any tweak? Feb 23 16:13:02 Hardy_: what distro? Feb 23 16:13:29 shr Feb 23 16:15:56 couldnt start gsm antenna Feb 23 16:16:12 sometimes he ask me for pin Feb 23 16:16:15 Hardy_: try to plug the neo on power and rboot Feb 23 16:16:27 i already tryed Feb 23 16:16:37 in my case, this helps in most cases Feb 23 16:16:58 i also rebootet a lot of times Feb 23 16:17:03 sometimes it works Feb 23 16:17:14 but just in 1 of 10 situations Feb 23 16:20:00 Hardy_: latest shr? Feb 23 16:20:01 retty much the same here... :( Feb 23 16:20:01 pretty Feb 23 16:21:32 yeah latest shr Feb 23 16:21:40 got the same issue?` Feb 23 16:22:02 i note that ticket as critical Feb 23 16:33:32 awesome, it worked vanous123 Feb 23 16:33:42 after 15 reboots xD Feb 23 16:34:12 but massages flushes again wtf xD Feb 23 17:13:55 [FYI] I just have seen that the high resolution Version of the Video "Talk about Openmoko by Sean Moss Putz at FOSdem" has been removed from rapidshare Feb 23 20:03:55 larsc: hi, i tried to find where is the problem with modem not powering up, but havent found anything Feb 23 20:05:50 hm Feb 23 20:06:02 is there anything in dmesg? Feb 23 20:08:07 nothing interesting Feb 23 20:09:07 to me it seems that gsm_on_off() is called properly, because it block a second when i write to power_on Feb 23 20:09:32 i do it like this now: Feb 23 20:09:34 echo 1 > /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1/gta02-pm-gsm.0/power_on Feb 23 20:10:21 but tried to talk to modem then, even with cu and socat, but it always blocks Feb 23 20:10:43 previous versions answered "AT interpreter ready" or something like this Feb 23 20:10:54 hm Feb 23 20:12:42 what does /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1/use_count say? Feb 23 20:16:03 hmm i have just "modalias" and "uevent" files in that dir Feb 23 20:23:35 oh right Feb 23 20:23:43 but there is a link to regulator.11? Feb 23 20:24:10 yes Feb 23 20:24:22 use_count should be in there Feb 23 20:24:35 i have only "num_users" with value 1 Feb 23 20:25:01 name of that regulator is "GSM" Feb 23 20:25:12 ok looks good Feb 23 20:25:21 and status is enabled? Feb 23 20:26:12 IIRC yes Feb 23 20:26:17 * radekp needs reboot Feb 23 20:26:18 hm Feb 23 20:26:19 hm Feb 23 20:26:21 hm Feb 23 20:27:59 "state" says "enabled" Feb 23 20:33:21 @ DocScrutinizer51 & Paul Fester : thank you for helping me yesterday, i was really confused that day, now if got it working. Feb 23 20:37:53 radekp: if you set 0 to power_on, how does state and num_users change? Feb 23 20:38:47 num_users=0 state=disabled Feb 23 20:46:10 can someone using shr perhaps tell me in which package the python module "bz2" can be found? (or perhaps help me finding this information on the web) Feb 23 20:55:57 radekp: i think i found it Feb 23 20:56:07 larsc: nice :) Feb 23 20:57:01 larsc: i can test it Feb 23 20:57:27 radekp: http://pastebin.com/jTWygUPG Feb 23 21:03:22 * radekp is compiling Feb 23 21:03:42 in fact my computer is compiling - i am waiting :) Feb 23 21:04:31 :) Feb 23 21:04:56 lol Feb 23 21:06:54 the times where you have to compile by hand are gone, I guess Feb 23 21:06:55 larsc: great it works :) Feb 23 21:07:11 radekp: was a pretty stupid bug... Feb 23 21:07:36 in fact i was going to ask where the 7 is written to gpio :) Feb 23 21:11:33 larsc: thanks for help, i will try to figure out now why it does not wake from suspend on incomming call Feb 23 21:11:51 larsc: but i think i will leave it for tomorrow :) Feb 23 21:12:06 radekp: the irq is not configured Feb 23 21:12:28 larsc: is it difficult to fix it? Feb 23 21:13:38 nope Feb 23 21:14:32 adding 5 lines maybe Feb 23 21:15:26 oki, btw i am using 2.6.32 kernel as daily phone for 2 weeks now Feb 23 21:15:41 :) Feb 23 21:16:03 except the wake on call and occasional WSOD it seems it's good :) Feb 23 21:16:31 but the WSOD here i recoverable - by plugging USB cable Feb 23 21:17:14 so it's a bit different WSOD from older 2.6.29 kernels Feb 23 21:23:10 yeah.. it's not really a WS"oD", just a WS Feb 23 21:24:12 lets name this WSOW White Screen On Wakeup) Feb 23 21:25:30 do you get it also when blanking/unblanking? Feb 23 21:26:38 Weiss: hmm how can i test it? Feb 23 21:30:05 just wait for the screen to blank (but not for the FR to suspend), then tap to wake it Feb 23 21:32:03 this works fine in QtMoko, but i guess it's not the same blank as in SHR, i think it just adjusts brihtness... Feb 23 21:52:26 radekp: i just added modem wakeup, but it's untested Feb 23 21:52:55 larsc: thanks, i will test Feb 23 22:02:24 larsc: it works, nice Feb 23 22:03:33 larsc: and strange thing is that i am not getting the white screen on resume anymore Feb 23 22:09:16 * radekp has to go sleep, good night Feb 23 23:08:21 :) Feb 23 23:50:33 It's more like scaring you don't get a WOSD anymore Feb 23 23:52:16 * DocScrutinizer wonders if there are any timing issues/races during startup of screen, like e.g init of JB6K7foo starting too short after enabling the LDO, so voltage hasn't stabilized yet Feb 23 23:53:17 Sounds not insane. Feb 23 23:53:29 larsc: ...or init too short after glamo startup, so init of glamo hasn't finished yet while video if starts to init Feb 23 23:54:00 s/if/IF/ Feb 23 23:54:02 DocScrutinizer meant: larsc: ...or init too short after glamo startup, so init of glamo hasn't finished yet while video IF starts to init Feb 24 00:14:59 btw I have to mention my results listed on WSOD bug. IIRC we tweaked each and every timing and delay to at least limit*2 to give plenty of headroom to jtb7k chip --> no results. So a WOSD (the vanishing of) on new .32 kernel is very likely caused by a new scheme to handle LCM resume not present in old kernel 15 months ago. Like LDO powerup timing wrt LCM init Feb 24 00:40:49 Weiss: you added the "joerg's recommendations" mods, no? Do these comprise of switching down LDO and resuming it, as well? Are there any measures taken to delay init of jbt6k LCD controler chip until LDO voltage has stabilized after re-enabling LDO? Feb 24 02:15:20 nope Feb 24 02:15:40 it's enable regualtor and assume it it's on **** ENDING LOGGING AT Wed Feb 24 03:00:02 2010