00:04.08 | *** join/#htc-linux Merculis (~Merculis@unaffiliated/merculis) |
00:04.39 | *** join/#htc-linux MassStash (~MassStash@c-67-175-41-173.hsd1.il.comcast.net) |
00:34.19 | *** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com) |
00:45.50 | *** join/#htc-linux Eodun (5532f3cc@gateway/web/freenode/ip.85.50.243.204) |
00:57.27 | jonpry | [RaphaelMemoryMap] |
01:04.14 | *** join/#htc-linux MassStash (~MassStash@c-67-175-41-173.hsd1.il.comcast.net) |
01:15.33 | *** join/#htc-linux Cass (~Cass@188-220-34-222.zone11.bethere.co.uk) |
01:16.37 | *** join/#htc-linux Berger (~noreply@c65wn1.wifi.halden.net) |
01:31.59 | *** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net) |
01:32.33 | *** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net) |
01:36.49 | *** join/#htc-linux SG (~SG@cpe-76-186-50-40.tx.res.rr.com) |
01:39.52 | *** join/#htc-linux HardDisk_WP (~marco@velirat.de) |
01:39.52 | *** join/#htc-linux HardDisk_WP (~marco@wikipedia/harddisk) |
01:48.07 | *** part/#htc-linux Cotulla (~opera@nat004-252-205-109.tvoe.tv) |
01:51.58 | *** join/#htc-linux hardwalker (~hardwalke@114-33-201-92.HINET-IP.hinet.net) |
02:05.03 | *** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk) |
02:31.05 | *** join/#htc-linux Cees_heim (~Cees@p548034D2.dip.t-dialin.net) |
02:38.28 | *** join/#htc-linux Curious_ (8bb3cfd0@gateway/web/freenode/ip.139.179.207.208) |
02:45.00 | *** join/#htc-linux mastermerlin1 (~Adium@p4FEE5759.dip.t-dialin.net) |
02:53.06 | *** join/#htc-linux arrrghhh_ (~arrrghhh@c-71-237-40-111.hsd1.co.comcast.net) |
02:57.19 | *** join/#htc-linux Cass (~Cass@188-220-34-222.zone11.bethere.co.uk) |
03:13.15 | jonpry | strange kernel crash http://pastebin.com/jLeir7FB |
03:14.28 | arrrghhh | [ 56.558807] Unable to handle kernel NULL pointer dereference at virtual address 00000000 |
03:14.35 | arrrghhh | see that a lot with these reboots |
03:15.16 | jonpry | you see this on .27? |
03:15.52 | arrrghhh | that error yes |
03:16.01 | arrrghhh | there's a bunch of gunk that's not familiar to me tho |
03:16.37 | jonpry | afaict it is crashing in the memory manager |
03:16.49 | jonpry | which kills it pretty bad |
03:17.04 | jonpry | weird thing is i got 3 or 4 boots today into froyo |
03:17.13 | jonpry | now i get that crash everytime |
03:17.24 | jonpry | i'm sure tomorrow it will boot again :p |
03:18.48 | *** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com) |
03:19.04 | *** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net) |
03:22.59 | WisTilt2 | arrrghhh you here or is that just your ghost |
03:23.41 | arrrghhh | i'm alive |
03:23.44 | arrrghhh | barely |
03:25.59 | WisTilt2 | anyone reporting loss of phone service but data still works? this would be for the 1258 git kernel not my new test ones. |
03:26.36 | arrrghhh | hrm |
03:26.38 | arrrghhh | i don't think so |
03:26.54 | arrrghhh | i keep having the same guy saying he gets SoD's when driving in and out of good/bad service areas |
03:27.22 | WisTilt2 | had it happen at least 5 times today. no one could call and i couldnt call out but data still worked fine. |
03:27.50 | *** part/#htc-linux Curious_ (8bb3cfd0@gateway/web/freenode/ip.139.179.207.208) |
03:27.58 | arrrghhh | damn |
03:28.19 | jonpry | are there any reports of strange things happening after android use? like next time android won't boot, or even winmo? |
03:28.54 | WisTilt2 | yeah i think that is a cause for setting up sod. weak signal or switching cells in a weak area seem to stop from registering on the network |
03:29.53 | WisTilt2 | jonpry: you doing nand or from haret? winmo should still boot no matter what happens in android, unless you kill microp like i did |
03:30.07 | jonpry | haret |
03:30.34 | ali1234 | i have seen winmo fail to boot after using linux, not on MSM hardware though |
03:30.52 | ali1234 | then again, i have seen winmo fail to boot after a normal restart |
03:31.31 | WisTilt2 | how far into winmo boot does it get? |
03:32.45 | jonpry | winmo seems to be working ok for me |
03:33.07 | jonpry | but i vaguely remember someone saying they couldn't power on until reset button was hit or something |
03:34.09 | WisTilt2 | only time i had probs like that was back when i was doing the microp stuff as you recall. hardspl fixed things back to normal every time. |
03:34.44 | jonpry | yeah, i think memory map is not right |
03:36.05 | WisTilt2 | im making another test kernel for arrrghhh to try then im going to jump back into this ring buffer with a clear head and see whats changing my data. |
03:36.21 | arrrghhh | more panel tests? |
03:36.53 | WisTilt2 | yeah since last night was kind of a bust with your panel staying off. |
03:38.06 | arrrghhh | heh |
03:38.47 | WisTilt2 | ok image ready, same name as last night |
03:39.08 | arrrghhh | kk |
03:39.22 | WisTilt2 | if this one doesnt keep your panel black, im hoping it will wake up out of sleep quicker and every time |
03:39.43 | *** join/#htc-linux bzo (~chatzilla@c-76-126-175-200.hsd1.ca.comcast.net) |
03:40.14 | *** join/#htc-linux stinebd (~bryan@gentoo/developer/battousai) |
03:41.39 | jonpry | hi bzo |
03:42.01 | bzo | hey jonpry |
03:42.45 | jonpry | its like i have bad ram running under .35 |
03:43.24 | bzo | winmo and 27 run ok? |
03:43.36 | jonpry | yeah |
03:43.45 | jonpry | and .35 seems to work depending on the wind |
03:43.53 | jonpry | presumably the temperature |
03:43.59 | bzo | it's gotta be some bug then |
03:44.06 | bzo | can't imagine it is a hardware problem |
03:44.10 | bzo | if the other stuff works |
03:44.24 | bzo | .35 has only been exercised much with the topaz |
03:44.29 | jonpry | yeah some bug |
03:44.56 | F22 | WisTilt2: Hiya, btw I figured out the answer to your question of a few days ago. Hardware key scan codes actually go through 2 mappings, once by the kernel to linux key codes, and a second time by android's java framework to android's key codes. The actual microp scan codes that you're using are mapped to linux key constants in drivers/input/keyboard/microp-keypad.c. microp_keypad_probe handles the assignment. |
03:45.11 | F22 | WisTilt2: So element 59 (ie. x3b) in the microp_keymap_rhodium array is assigned to KEY_FN and element 60 (ie. x3c) to KEY_LEFTSHIFT. All rhodiums are currently assigned the same mapping however. So element 59 (ie. x3b) is always treated as KEY_FN by our kernel (but not android), including on rhod handsets where it's something else like the 100 and 300. |
03:45.18 | jonpry | i think it is temperature correlated |
03:45.49 | *** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net) |
03:46.29 | stinebd | WisTilt2: nice job on the keyboard leds for rhod. i was using one earlier, it rocks |
03:46.54 | WisTilt2 | F22: thanks, glad we know whats going on now with those codes im using:) |
03:47.04 | *** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com) |
03:47.49 | F22 | WisTilt2: Those Linux key codes are defined in include/linux/input.h. There KEY_LEFTSHIFT is defined as 42 and KEY_FN is 0x1d0 (464). In android's key layout files, the decimal representation of these Linux key codes are then remapped to Android's key codes. Android's key codes are defined in frameworks/base/core/java/android/view/KeyEvent.java. |
03:48.01 | WisTilt2 | stinebd: yeah, too bad all rhods werent the same, the 300 is backwards can you believe it? |
03:48.26 | stinebd | oh it was a 300 actually |
03:49.35 | F22 | lol, your caps/fn led stuff is still blowing up microp on my phone. i had to comment it out or once i hit caps or fn, the keyboard & touch screen stop working. |
03:49.38 | WisTilt2 | same one i have. seems the 300 is the only one with the bits reversed in the hardware so had to add that logic. nice to have that whole keyboard backlight and leds out of my hair |
03:50.06 | WisTilt2 | F22 is that on that engineering 210? |
03:50.13 | F22 | WisTilt2: yup |
03:50.58 | WisTilt2 | well, you probably understand when I say "not worth fixing for just 1 phone on the planet" :) |
03:51.04 | F22 | i appear to have a microp version that isn't in the list. |
03:51.25 | WisTilt2 | ah, get the version and we can add it. its not 0xa88? |
03:52.42 | F22 | [ 2.449188] microp-klt: This hardware is not yet supported: 0688 |
03:52.42 | F22 | [ 2.466644] microp-klt: probe of 0-0066 failed with error -524 |
03:54.01 | WisTilt2 | do either of the leds come on when hitting those keys or does it just die? |
03:54.10 | F22 | leds do not come on, it just dies. |
03:55.06 | F22 | i also have an issue with the speaker led. had to comment that out just to get past the boot ani. all my issues seem led related. |
03:55.49 | pupnik | thanks for the info on the key scan codes F22 |
03:56.37 | WisTilt2 | if you want to try it ill add that version and see if it responds on our normal microp addy? |
03:56.38 | F22 | pupnik: you're welcome. planning on doing something with them? :) |
03:57.44 | pupnik | unfortunately i may have to now that nokia isn't producing linux phones anymore |
03:58.24 | F22 | WisTilt2: ok, sounds good. |
03:58.26 | pupnik | in particular my interest is in seeing android kernel run in a user-mode jail under linux |
04:00.22 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
04:02.41 | WisTilt2 | F22: go ahead and try this kernel and see if they at least come on now. |
04:02.44 | *** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com) |
04:02.53 | WisTilt2 | image only btw |
04:02.53 | F22 | WisTilt2: will do |
04:02.57 | F22 | ok |
04:03.07 | WisTilt2 | arrrghhh did i blow up your phone? |
04:03.15 | arrrghhh | WisTilt2, nope ;) |
04:03.27 | WisTilt2 | red lines are gone now hopefully |
04:03.37 | arrrghhh | heh haven't seen 'em yet |
04:03.39 | arrrghhh | that was freaky |
04:03.44 | arrrghhh | then... nothing. lol |
04:05.02 | WisTilt2 | notice any difference waking with this one? |
04:05.27 | jonpry | ever see this: mmc_sd_detect(mmc1): Unable to re-detect card (-110) |
04:05.32 | arrrghhh | had one slow wake out of 3 so far |
04:05.43 | arrrghhh | kinda fades in nicely now |
04:05.53 | arrrghhh | and abruptly shuts off ha |
04:06.28 | WisTilt2 | jonpry: happen every boot? |
04:06.43 | jonpry | no, that was when it worked |
04:06.51 | jonpry | i finally got power button hooked up |
04:06.57 | jonpry | so i hit it |
04:06.59 | bzo | jonpry: you could be running into the sdcard problem with alex clocks |
04:07.03 | jonpry | which was a bad idea |
04:07.24 | jonpry | are alex's clocks in htc-msm-2.6.35? |
04:07.31 | bzo | yeah, think so |
04:07.53 | jonpry | problem happens during wake? |
04:08.13 | bzo | possibly, you could try overriding sdcard freq w/ boot param |
04:08.26 | jonpry | its at 49MHZ or something |
04:09.22 | bzo | that's high isn't it? |
04:09.42 | jonpry | its ok for sdhc cards |
04:10.18 | bzo | there may be something happening in clock-wince that is not correctly setting it |
04:10.26 | jonpry | it seemed to sleep and wake almost 3 times before it crashed this time |
04:10.54 | bzo | arrrghhh: remember what that SD card problem workaround was off hand? |
04:11.16 | arrrghhh | yea |
04:11.20 | arrrghhh | cmdline option |
04:11.41 | bzo | yeah, what was it though? |
04:11.46 | arrrghhh | msmsdcc_1bit msmsdcc_fmax=14000000 |
04:11.48 | arrrghhh | sorry |
04:11.50 | arrrghhh | finding it :P |
04:12.04 | bzo | thx |
04:12.13 | bzo | jonpry why don't you see if that helps? |
04:12.23 | jonpry | hmm |
04:12.46 | jonpry | 1bit at 14mhz? |
04:13.56 | F22 | WisTilt2: good signs! we're out of the boot ani, and the speader led is orange instead of green, just like on my production 210. |
04:14.11 | F22 | s/speader/speaker/ |
04:14.27 | WisTilt2 | nice. maybe its going to be same microp and everything will work! |
04:16.09 | F22 | caps/fn lights work beautifully, no lock up. no oopses. |
04:16.36 | jonpry | bzo: i put in some extra printks, and i think the problem is with sd slot power |
04:16.41 | stinebd | WisTilt2: ok. leds for raph now. |
04:17.13 | F22 | WisTilt2: very nice. :) |
04:17.15 | WisTilt2 | F22 good deal, that was easy |
04:17.25 | bzo | jonpry: we do get sd vdd error messages in 27 ... |
04:17.54 | WisTilt2 | will be a funny commit... added microp version for the only phone on the planet like this one. |
04:18.20 | F22 | lol, it may not be the only one, just the only one we know about. :P |
04:18.54 | stinebd | there are some others stashed away in bins at htc's offices |
04:19.17 | WisTilt2 | stinebd: those leds dont work on raph at all? |
04:19.26 | stinebd | they work, they just don't reflect reality |
04:19.33 | stinebd | gotta be hooked into the keyboard driver i guess |
04:19.41 | stinebd | or correctly hooked |
04:20.41 | WisTilt2 | yeah we really need to get userland state hooked up with the kernel. i have all the logic for the led states in the kernel, which is temporary for now |
04:21.24 | WisTilt2 | is it just the state that is wrong like caps lock and such? |
04:21.44 | stinebd | yeah |
04:21.52 | stinebd | so when you hit fn, it just toggles it |
04:22.12 | stinebd | fn (light goes on), fn (light goes off, but fn is locked so still on the alternate keys) |
04:22.46 | jonpry | bzo: doesn't this sd problem with the 1bit thing prevent it from booting in the first place? |
04:23.11 | WisTilt2 | should be able to take the same state code i have for rhod and stick it in raphs code. ill have to take a look at that, shouldnt be that hard |
04:23.38 | bzo | jonpry: quite possibly, arrrghhh is more familiar with the problem |
04:24.13 | stinebd | WisTilt2: the stuff in microp_keypad_led_event()? |
04:24.14 | arrrghhh | jonpry, yes |
04:24.20 | arrrghhh | says "waiting for SD" basically |
04:25.00 | jonpry | yeah, i boot just fine |
04:25.24 | arrrghhh | doesn't effect everyone. i never had a problem either :P |
04:26.01 | bzo | I seem to recall the 27 stuff being modded from what came from upstream |
04:26.17 | bzo | dunno what 35 is using (as far as the sd card stuff goes) |
04:26.27 | jonpry | this mmc.c is just copied from .27 |
04:26.49 | jonpry | http://pastebin.com/sa8asxFY |
04:27.09 | jonpry | this is not exactly what you want to go down when running from sd card :p |
04:27.41 | arrrghhh | heh we just need to get off of SD :P |
04:27.52 | bzo | jonpry and you say nand is a gimmick |
04:28.14 | jonpry | lol |
04:29.12 | arrrghhh | WisTilt2, wakes seem great |
04:29.53 | WisTilt2 | stinebd: yes that is part of it, the rest is in microp-ksc |
04:29.58 | F22 | jonpry: the sd card issue that arrrghhh and bzo are talking about first appeared when alex's cocks were committed in 1243. So newer kernels with the possible exception of 1258 express it. As already pointed out, it only effects some sd cards, not all of them. It's possible it may allow some to boot, but then experiences timing issues afterward. The severity of the issue may depend on the card. not entirely sure since my cards are all clas |
04:30.08 | *** join/#htc-linux Rob2222 (~Miranda@p4FFF2A10.dip.t-dialin.net) |
04:31.28 | WisTilt2 | stinebd: led_event does the actual logic and holds the current state of each key. |
04:31.47 | WisTilt2 | arrrghhh: more stable? you like the quick fade in on wake? |
04:31.57 | arrrghhh | yea, it's nice |
04:32.12 | arrrghhh | what happened to quick fade out? :P |
04:32.12 | WisTilt2 | any failed wakes where you had to touch unlock? |
04:32.26 | arrrghhh | i don't think so |
04:32.33 | arrrghhh | there was one where i touched the screen right away |
04:32.38 | arrrghhh | right when it booted |
04:32.58 | arrrghhh | hrm |
04:33.10 | arrrghhh | that was interesting. i saw a little white square in the left corner |
04:33.17 | WisTilt2 | i change that long time ago so when you hit power button the panel is powered off immediately rather than fade down |
04:34.05 | WisTilt2 | yeah that square shows up now and then, dont know what it is, probably big brother watching now and then |
04:34.13 | arrrghhh | lol |
04:34.26 | WisTilt2 | has to do with timing and the fb im sure |
04:35.04 | arrrghhh | so that was one failure |
04:35.11 | arrrghhh | in 10 maybe 15 wakes |
04:35.38 | WisTilt2 | where it went back to sleep without panel coming up? |
04:36.43 | arrrghhh | yea |
04:36.59 | WisTilt2 | F22 is that 210 waking up out of full sleep ok with this kernel? just dawned on me the timing i have set should be freaking that thing out |
04:38.05 | WisTilt2 | arrrghhh do you mind trying one more test? i want to drop the timing down some more so we can find the bottom. |
04:38.43 | stinebd | heh poor test slave |
04:39.13 | F22 | WisTilt2: it appears not to be going into power collapse. led never turns green. |
04:40.50 | WisTilt2 | thats something else keeping it up then. gps and all that stuff is off? |
04:41.01 | F22 | let me double check all that stuff. |
04:42.02 | WisTilt2 | arrrghhh next image ready when you're ready |
04:43.59 | arrrghhh | heh |
04:44.01 | arrrghhh | same name? |
04:45.28 | bzo | jonpry: do you think userland rpc connections could trigger a wakelock? |
04:45.44 | jonpry | perhaps |
04:45.57 | jonpry | but the phone is sleeping just fine |
04:46.17 | bzo | been looking at the gps problem that prevents sleep |
04:46.32 | bzo | it keeps an rpc server/client open the whole time |
04:46.43 | arrrghhh | WisTilt2, 9e8ba2a28fee6112611600aab10c2e9d? |
04:46.51 | jonpry | you want to sleep while gps is running? |
04:47.11 | bzo | the current lib keeps the rpc open even when not active |
04:47.21 | bzo | or at least the end points |
04:47.21 | jonpry | oh |
04:47.56 | F22 | WisTilt2: i did have gps on, turned both that and wifi off. still doesn't seem to be going to sleep, the led stays solid orange. never had a problem before. |
04:48.12 | bzo | the vogue gps implementation does that to, but there the rpc stuff is called from within the kernel |
04:49.00 | WisTilt2 | arrrghhh yes correct. |
04:49.32 | F22 | by never had a problem before, i mean i'm using the same set-up on my sd card i was using on my other 210. |
04:49.37 | WisTilt2 | F22 some other app keeping it up then. might try rebooting again? |
04:49.41 | jonpry | bzo, i suppose its possible that rpc holds a lock if any device files are open |
04:49.48 | jonpry | but that seems like strange design |
04:50.01 | F22 | ok, will try a reboot. i do have one interesting item in my dmesg. dunno if it's relevant. |
04:50.14 | F22 | [ 2121.820343] msm_i2c msm_i2c.0: error, status 63c8 |
04:50.14 | F22 | [ 2121.820434] msm_i2c msm_i2c.0: Error during data xfer (-5) |
04:50.24 | WisTilt2 | normal, you must have autobl off |
04:50.32 | WisTilt2 | i need to fix that |
04:50.34 | bzo | jonpry: are rpc connections supposed to be able to survive suspend? |
04:50.34 | jonpry | F22, you make a phone call? |
04:51.05 | F22 | jonpry: not since last boot |
04:51.54 | jonpry | dmesg is from last boot? |
04:52.07 | F22 | this boot |
04:52.20 | F22 | yes |
04:52.39 | WisTilt2 | timestamps are not right |
04:52.48 | WisTilt2 | unless you had it up for 45mins |
04:53.27 | jonpry | bzo: i'm not sure |
04:53.50 | jonpry | but its not like it is rebuilding the /dev entries after a wake |
04:54.30 | bzo | is that how RPC is implemented on the userland side? |
04:54.47 | bzo | there is that funny dex stuff for a11 to a9 rpc |
04:54.55 | jonpry | yeah its just some ghetto library that opens up the file and blast bytes into it |
04:55.04 | jonpry | just a char stream |
04:55.52 | jonpry | however the kernel side of it, is not normal |
04:56.07 | jonpry | oncrpc people would shit a brick |
04:56.20 | bzo | lol |
04:56.42 | F22 | oh hmmm....i'll post the dmesg. the timestamps do seem strange |
04:57.25 | F22 | uptime does say i've been up 45 min now. |
04:58.18 | WisTilt2 | turn autobl on and you shouldnt see that i2c error. |
04:59.25 | F22 | lots of core.c mmc_wait warnings. hmmm.... |
04:59.44 | F22 | turning autobl off |
04:59.44 | *** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net) |
05:01.35 | arrrghhh | WisTilt2, http://pastebin.com/tgXuecct <--- had two failed wakes in a row. last wake was good, then i plugged into adb and pulled a dmesg. |
05:02.56 | WisTilt2 | so these you had to touch unlock to bring it up? |
05:03.46 | jonpry | bzo: i tried slowing down the sd and such |
05:04.08 | jonpry | no luck |
05:04.34 | bzo | blech |
05:06.06 | jonpry | anywho its pretty stable with only 128MB enabled |
05:06.42 | arrrghhh | WisTilt2, i just let the cycle go, never woke the phone |
05:06.46 | arrrghhh | bl came up |
05:06.49 | arrrghhh | led went orange |
05:06.50 | arrrghhh | no panel |
05:07.15 | bzo | jonpry: I do recall needing some tweaks for 27 to be able to use the 2nd bank with stability |
05:07.30 | bzo | with holes config or something |
05:08.25 | jonpry | yeah i'm using the bottom 64 of each, and standard .27 pmem which has its fingers in ebi1 and ebi2 |
05:09.10 | jonpry | i've also got something that *looks* like a resume |
05:10.02 | MassStash | grrrr nand... |
05:10.08 | F22 | oh, hmm...didn't reboot, led never turned green, but now i can't wake the panel, if i long press the screen it vibrates however. |
05:12.40 | arrrghhh | WisTilt2, other than those 2 failed wakes, it's been quick to wake. |
05:13.05 | WisTilt2 | better than before? |
05:13.13 | arrrghhh | yea |
05:13.27 | arrrghhh | every time it's waked it's been under 1s i'd say |
05:13.34 | WisTilt2 | F22 can you get a dmesg while in that condition? |
05:13.46 | WisTilt2 | like the fade in or no? |
05:14.07 | arrrghhh | yea it's cool |
05:14.18 | F22 | grabbed a dmesg just before i rebooted |
05:14.20 | arrrghhh | there'll be some that would prefer the cut in. |
05:14.34 | WisTilt2 | they can code it themselves:) |
05:14.37 | arrrghhh | doesn't really matter to me, so long as it wakes consistently quick... which it has so far :P |
05:14.38 | arrrghhh | heh |
05:14.50 | jonpry | bzo: your accepting patches for 35? |
05:15.12 | arrrghhh | ah well. i need to go to bed. |
05:15.30 | arrrghhh | WisTilt2, if you decide to make a kernel pack shoot me an email as usual. i'll run with this kernel tonight. |
05:15.34 | bzo | jonpry: better to send them to emwe for now, I've hardly looked at the 35 tree yet |
05:15.48 | WisTilt2 | ok thanks, yeah and check your battery drain with this one |
05:15.56 | arrrghhh | sure |
05:15.57 | arrrghhh | g'nite guys |
05:15.59 | WisTilt2 | oh, put it in sleep mode 0 |
05:16.01 | WisTilt2 | not 1 |
05:16.03 | arrrghhh | 0? |
05:16.10 | stinebd | ? |
05:16.11 | arrrghhh | can i change that on the fly? |
05:16.11 | WisTilt2 | yeah. then see what battery is like |
05:16.12 | MassStash | wow |
05:16.14 | MassStash | ? |
05:16.23 | WisTilt2 | trust me |
05:16.24 | stinebd | WisTilt2: btw do you know the difference between 0 and 1? |
05:16.42 | WisTilt2 | stinebd: yes, 1 is collapse, 0 is suspend |
05:16.59 | F22 | WisTilt2: http://pastebin.com/crGns3a2 |
05:17.11 | jonpry | WisTilt2, what does that mean precisely? |
05:17.36 | MassStash | ... |
05:17.50 | stinebd | right, we know the name difference but i don't think anybody knows what is actually happening that's different |
05:18.01 | WisTilt2 | jonpry: in mode 0 arm11 is put in suspend not powered down, mode 1 its powered down |
05:18.15 | stinebd | we've never seen any difference in battery consumption between those two |
05:18.36 | arrrghhh | i g2g. i'll try 0 in the morning.. cya! |
05:18.49 | stinebd | or if we have, it's been too small to notice because it was lasting like 4 hours on battery anyway |
05:18.59 | MassStash | now i guess we need to figure the dif between panel suspended and powered down |
05:19.25 | WisTilt2 | stinebd: about .2% per hour better in mode 0 for whatever reason and only since bzo's pll patch |
05:20.36 | MassStash | huh, very intriguing... |
05:21.30 | *** join/#htc-linux goxboxlive (~jrs@mail2.hjellnesconsult.no) |
05:22.20 | MassStash | perhaps its better than power on/off because it's not powering on n off, yet somehow better than "2" or "3" or somthin |
05:23.46 | WisTilt2 | F22 dont see anything in logs that indicates the problem. kbd lights and everything still work? |
05:24.30 | F22 | didn't check. but i do know that the problem happened far more quickly after the reboot. i wonder if it's related to turning auto-bl on. |
05:25.42 | *** join/#htc-linux avinashhm (~avinash-h@203.101.61.10) |
05:25.56 | WisTilt2 | happened after you turned autobl on? |
05:26.00 | F22 | hmmm...i put to sleep, it appears it doesn't want to wake up. |
05:26.11 | F22 | yup |
05:26.17 | F22 | didn't have the issue before i turned autobl on. |
05:26.18 | WisTilt2 | and autobl is on right now? |
05:26.53 | WisTilt2 | hit power button then hold near a light and see if panel comes up |
05:26.57 | F22 | i haven't turned it off since turning it back on. so unless it turns itself back off on reboot, i'd say that's an affirmative. |
05:27.16 | F22 | haven't turned autobl off since turning it back on i mean. |
05:27.26 | F22 | will do |
05:27.45 | WisTilt2 | almost sounds like the ambient reference value is 0 on wake |
05:28.01 | WisTilt2 | putting near a light should bring it up if thats the case |
05:28.45 | F22 | doesn't seem to react to a light at all |
05:29.09 | WisTilt2 | is the backlight on and just not displaying anything or is it black |
05:29.45 | WisTilt2 | hang on here... is this the device with that 0x7 id? |
05:29.52 | F22 | backlight is off |
05:29.57 | F22 | yes |
05:30.30 | WisTilt2 | crapola.. ok hang on ill build another kernel. inits are not right for that device in this kernel |
05:30.52 | WisTilt2 | when autobl is enabled that is |
05:30.55 | F22 | ah |
05:31.45 | MassStash | anyone kno what cotullas up to...? |
05:32.04 | jonpry | .32 rhod |
05:33.06 | *** join/#htc-linux stinebd (~bryan@gentoo/developer/battousai) |
05:33.52 | WisTilt2 | F22: ok try this one |
05:34.00 | F22 | will do |
05:44.08 | F22 | that was interesting, took a second press of power to fully come back on. but at least it worked. first press of power changed the led from green to orange. now it seems to work fine. |
05:44.35 | F22 | this was after putting the phone to sleep with the new kernel and autobl on. |
05:44.51 | F22 | WisTilt2: ^ |
05:46.27 | WisTilt2 | might still get occasional non wakes where you have to touch it but panel should come up pretty quick now from sleep? and should be a quick fade in |
05:48.50 | F22 | yep, i haven't needed to touch the screen yet however despite putting it to sleep and waking a good dozen times. |
05:50.12 | WisTilt2 | wake up time within 1sec or so? |
05:50.29 | F22 | yup, about right |
05:50.52 | F22 | except when it gets stuck |
05:51.19 | F22 | just had it get stuck a second time, didn't try pressing it a second time this time. |
05:51.39 | WisTilt2 | thats as fast as it is capable of waking up i think. are you seeing the quick draw lines from top to bottom as it comes up? |
05:52.15 | *** join/#htc-linux r3dg4r (18884af8@gateway/web/freenode/ip.24.136.74.248) |
05:52.20 | F22 | i saw a single partial line once. |
05:52.40 | F22 | every other time i haven't seen anything |
05:52.57 | WisTilt2 | should be wide faintly black line from top to bottom as it fades in |
05:53.11 | WisTilt2 | its pretty fast though so might not always see it |
05:53.33 | *** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey) |
05:53.41 | F22 | no, this was not vertical, it was more like a very brief horizontal artifact. |
05:54.06 | WisTilt2 | well this kernel should work the same on the rhod100 AUO's now so maybe we'll be done with it finally |
05:54.37 | WisTilt2 | yeah thats it, might not always be at top depending on where vsync is at the time |
05:56.55 | WisTilt2 | bzo: got some interesting info for you regarding vregs and dex if you're not in the middle of something... |
05:56.56 | F22 | haven't seen any lines since. it wakes very quickly (except when it occasionally needs a 2nd touch). |
05:57.08 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
05:57.19 | bzo | WisTilt2: what's up? |
05:57.36 | WisTilt2 | F22:i dont think those occasional non-wakes can be fixed until we get acl to tweak the fb |
05:58.43 | F22 | hmm...sometimes it takes more than 2 touches, but if you let it go back to sleep, it wakes up just fine if you press power again. |
05:59.07 | WisTilt2 | bzo: hey, i did some extensive testing on those vregs on powerdown. it seems the dex commands jb is using costs us close to 1.5% per hour more power in sleep. vreg gp2 does nothing for power in sleep while gp4 is the magic power saver all by itself |
05:59.41 | WisTilt2 | just disabling gp4 gets us down to .5% or less consistently |
06:00.32 | WisTilt2 | and another note, im not using the gpio power down at all |
06:01.36 | WisTilt2 | F22: if you can, see what kind of battery drain you get overnight with that setup also |
06:02.22 | F22 | ok, will do. |
06:02.33 | bzo | WisTilt2: hmm, that's interesting. I think jb's stuff is reversed from the rhod300 dlls |
06:03.07 | WisTilt2 | might be why im seeing better battery than in winmo:) |
06:04.04 | bzo | true, lol |
06:04.37 | WisTilt2 | also, the docs are wrong for the sleep-out timing. it says 120ms minimum needed but its actually supposed to say 20ms. ive tested it down to 5ms and it works fine. |
06:05.18 | F22 | damn docs...lol |
06:06.42 | WisTilt2 | yeah, our 7201a docs had close to 30 correction pages and we still get them from time to time. i guess when you put out docs with close to 1500 pages there will be errors |
06:07.24 | bzo | WisTilt2: btw, speaking of vreg, I noticed the other day that wifi power off is not implemented |
06:07.34 | bzo | once you turn off, you can't turn off, lol |
06:07.47 | bzo | err I mean once you turn on, you can't turn off |
06:08.10 | WisTilt2 | huh? you mean when you power wifi on then off the power is still really on? |
06:08.49 | bzo | yeah, I guess the original author ran into problem turning it off, so it is commented out |
06:08.55 | F22 | WisTilt2: btw, you need to treat caps/fn lights for 110's just like the 100's. |
06:09.06 | WisTilt2 | is that missing in userland or kernel? |
06:09.38 | WisTilt2 | what is a 110?? i only knew of 100,210,300,400,500 |
06:09.46 | F22 | 110's are australian |
06:10.00 | WisTilt2 | same 0x13 AUO panel? |
06:10.51 | F22 | not entirely certain on the panel. i know the key layout is identical to the 100 uk |
06:11.30 | WisTilt2 | should work as is then i think |
06:11.54 | WisTilt2 | i only had to reverse the bits on the 300 and all others were normal |
06:12.11 | F22 | wasn't 100 different? |
06:12.22 | F22 | had a different value for fn? |
06:12.41 | WisTilt2 | oh yes... i havent added that yet |
06:12.55 | bzo | WisTilt2: kernel mmc.c |
06:13.01 | F22 | so for that one, treat 110 the same. |
06:13.37 | WisTilt2 | ok, ill have to pull machine variant for 110 also. need to make a note or ill forget |
06:13.53 | WisTilt2 | bzo: whats the power drain with wifi on do you know? |
06:14.30 | bzo | WisTilt2: never measured it |
06:14.32 | stinebd | heh |
06:14.49 | stinebd | another one of those things that nobody would've noticed before when battery was lasting 4 hours |
06:14.56 | F22 | to my knowledge the 100 owners aren't complaining about the panel, so whatever they have currently should probably be fine unless they start complaining. |
06:15.08 | F22 | s/100/110/ |
06:15.27 | stinebd | WisTilt2: i can look up the wifi consumption on passion which has a 4329 if that helps to compare |
06:16.06 | WisTilt2 | stinebd: yeah would be interested to know. im sure lots of people use wifi then turn it off when done to save power |
06:16.27 | stinebd | those bcms are very very good on power |
06:16.51 | WisTilt2 | someone said wifi uses less power than 3g is that true? |
06:16.56 | stinebd | yeah |
06:16.59 | bzo | it's just the vreg not getting turned off, there are power gpios that are implemented |
06:17.01 | stinebd | i might've said that |
06:17.21 | bzo | so turning it off does something, perhaps even close to fully powered off? |
06:17.43 | WisTilt2 | vreg will probably make a difference though if its the same gain we saw in the panel |
06:18.32 | stinebd | <PROTECTED> |
06:18.35 | stinebd | (mA) |
06:18.57 | *** join/#htc-linux furtardo (~mks@nat/yahoo/x-soajmtiwahxswctj) |
06:19.01 | *** join/#htc-linux Rajko (~Rajko@wan.rajkonet.info) |
06:19.23 | bzo | 4ma is pretty low |
06:19.26 | WisTilt2 | 4ma idle is not much but adds up over a day. 120ma in use is up there. |
06:19.26 | stinebd | comparitively <item name="radio.active">300</item> |
06:19.42 | WisTilt2 | arent they only 20-30milliwatt radios? |
06:19.43 | stinebd | so it does indeed use less than 3g |
06:20.17 | stinebd | radio.on = 3 |
06:21.17 | WisTilt2 | almost 1/3 the power as 3g thats a big difference. of course 3g is putting out much more power than wifi but still |
06:21.35 | stinebd | crazy right? |
06:21.45 | stinebd | and you can definitely see the results on n1 |
06:22.56 | stinebd | bluetooth 0.3 haha |
06:24.01 | WisTilt2 | yeah for 30ft doesnt take much power at all |
06:24.40 | stinebd | we should probably get that working at some point |
06:25.14 | stinebd | us americans are too lazy to be holding phones to our ear |
06:25.28 | WisTilt2 | if cell towers could get their receiver sensitivity to like -120 instead of -106 or so, our devices could transmit at a lower power level |
06:25.59 | stinebd | so we should call and ask them to do that? |
06:26.46 | WisTilt2 | just bypass BT and lets be the first to implement that new brainwave reading technology and we'll just think to command the phone |
06:27.00 | WisTilt2 | have you seen that stuff yet? |
06:27.27 | stinebd | can that be hooked into nexus s's NFC somehow? |
06:28.29 | WisTilt2 | dont know the cpu powered it needs but its amazing technology to see in action. i wouldnt believe it if i hadn't seen it myself |
06:28.56 | F22 | as long as it doesn't give us brain cancer 10 years from now i'm up for that. :D |
06:28.59 | WisTilt2 | cost could be a show stopper though |
06:29.18 | stinebd | so if the cancer waits for 11 years you support it? |
06:29.45 | WisTilt2 | no cancer, no radio waves on your head, just sensors fed to a computer |
06:29.58 | stinebd | that's what the government wants you to think man |
06:30.09 | stinebd | it's all a ploy man to get into your thoughts man |
06:30.13 | F22 | stinebd: lol |
06:30.25 | F22 | that's what the tin foil helmets are for... |
06:30.46 | WisTilt2 | true, big brother wants to control everything now, why not our thoughts too |
06:31.09 | stinebd | well it'll probably be mcdonalds first |
06:31.17 | stinebd | think about it. commercials in your sleep. what a cash cow. |
06:31.55 | stinebd | </conspiracy,man> |
06:32.15 | *** join/#htc-linux MacDrunk (~marper@201.165.161.195) |
06:35.06 | WisTilt2 | well guys im out for the night. F22 let me know what kind of battery results you get. catch you all tomorrow. |
06:38.13 | F22 | i'm out also for the night. stinebd, i'll get that rhod400 shipped out to you when i wake up in the morning. |
06:38.40 | stinebd | heh thanks. night. |
06:38.58 | *** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com) |
06:42.25 | *** join/#htc-linux hardwalker (~hardwalke@114-33-201-92.HINET-IP.hinet.net) |
06:56.46 | *** join/#htc-linux bob_ (62cf5cd9@gateway/web/freenode/ip.98.207.92.217) |
07:23.02 | *** join/#htc-linux gauner1986 (~Miranda@2.209.103.72) |
07:23.29 | *** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk) |
07:40.43 | *** join/#htc-linux kiozen (~kiozen@p5DDF3E87.dip.t-dialin.net) |
07:53.53 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
08:08.02 | *** join/#htc-linux jozefk (~jozefk@unaffiliated/jozefk) |
08:09.07 | jozefk | hello. I don't know if this is a right channel to ask but anyway: is it possible to upgrade android 2.1 to android 2.2 on HTC Desire phone? |
08:12.08 | jozefk | after googling it seems it's normal thing :) |
08:13.29 | *** join/#htc-linux Drakh_ (Drakh@190.42.25.245) |
08:15.14 | *** join/#htc-linux GPFerror (~GPF@ip72-208-193-231.ph.ph.cox.net) |
08:16.23 | pupnik | android -> #android :) |
08:25.39 | jozefk | is this the only htc channel? |
08:26.19 | *** join/#htc-linux rob_w (~bob@ppp-188-174-68-231.dynamic.mnet-online.de) |
08:30.56 | *** join/#htc-linux Drakh_ (Drakh@190.42.90.144) |
08:33.09 | pupnik | jozefk: i don't know, sorry |
08:36.20 | *** join/#htc-linux Erikson (~Erik@i5E86D582.versanet.de) |
08:47.49 | *** join/#htc-linux skodde (~skodde@unaffiliated/skodde) |
08:57.27 | *** join/#htc-linux thepace (thepace@cable-178-148-12-118.dynamic.sbb.rs) |
09:03.05 | *** join/#htc-linux gauner1986 (~Miranda@p5B382C19.dip.t-dialin.net) |
09:09.14 | *** join/#htc-linux Phally (~Phally@dhcp-077-251-163-183.chello.nl) |
09:20.41 | *** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk) |
09:38.45 | *** join/#htc-linux BazGee (~BazGee@cpc1-sund2-0-0-cust716.11-1.cable.virginmedia.com) |
10:07.43 | *** join/#htc-linux MN_ (568620c6@gateway/web/freenode/ip.86.134.32.198) |
10:15.45 | *** join/#htc-linux crawling (~crawling@a94-132-163-181.cpe.netcabo.pt) |
10:20.22 | *** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk) |
10:22.31 | *** join/#htc-linux dekar_ (~dekar@drms-590cf9d1.pool.mediaWays.net) |
10:25.00 | *** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net) |
11:02.19 | *** join/#htc-linux visof (~visof@unaffiliated/visof) |
11:02.23 | visof | hello |
11:03.37 | visof | i have installed android and want to add another fonts to /system/fonts in system.ex2fs |
11:03.40 | visof | how can i do that |
11:04.04 | visof | how can i extract the content of that file under linux ? |
11:05.23 | visof | i'm trying to use android under htc diamond |
11:05.29 | visof | please anyone help me on that |
11:20.43 | *** join/#htc-linux GNUtoo|laptop (~gnutoo@host68-143-dynamic.54-79-r.retail.telecomitalia.it) |
11:36.04 | *** join/#htc-linux MN_ (~yaaic@host86-134-32-198.range86-134.btcentralplus.com) |
11:41.35 | *** join/#htc-linux malizmaj (~thepace@cable-178-148-12-118.dynamic.sbb.rs) |
11:49.14 | *** join/#htc-linux isikil (52311039@gateway/web/freenode/ip.82.49.16.57) |
11:51.21 | *** join/#htc-linux |Atom| (~atom@82.194.234.249) |
11:51.50 | *** join/#htc-linux Ceesheim (~Cees@p548034D2.dip.t-dialin.net) |
12:02.54 | *** join/#htc-linux skodde (~skodde@unaffiliated/skodde) |
12:03.05 | *** join/#htc-linux tomaw (tom@freenode/staff/tomaw) |
12:04.56 | *** join/#htc-linux MN_ (568620c6@gateway/web/freenode/ip.86.134.32.198) |
12:05.00 | *** join/#htc-linux SG (~SG@cpe-76-186-50-40.tx.res.rr.com) |
12:07.26 | *** join/#htc-linux L_miller (~IceChat7@bs.americas.lc.americanstandard.com) |
12:08.28 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
12:12.50 | *** join/#htc-linux Markinus (~Miranda@212.255.18.217) |
12:20.27 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
12:22.18 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
12:24.32 | *** join/#htc-linux dekar_ (~dekar@drms-590cf9d1.pool.mediaWays.net) |
12:38.25 | *** join/#htc-linux Cotulla (~opera@nat004-252-205-109.tvoe.tv) |
12:39.13 | SG | ~seen mdeejay |
12:39.17 | apt | mdeejay <~mdeejay@46.182.128.248> was last seen on IRC in channel #htc-linux, 15d 21h 38m 55s ago, saying: 'git://github.com/CyanogenMod/android_device_htc_leo cool'. |
12:42.36 | L_miller | MassStash! |
12:48.40 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
12:51.58 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
12:55.06 | *** join/#htc-linux Drakh_ (Drakh@190.42.25.245) |
12:55.24 | *** join/#htc-linux LordDeath (~Lord|Lapt@cable-81-173-166-52.netcologne.de) |
12:59.47 | gauner1986 | hey cotulla |
13:00.14 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
13:09.12 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
13:17.30 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
13:17.49 | *** join/#htc-linux NetRipper_ (bccd57ea@gateway/web/freenode/ip.188.205.87.234) |
13:18.10 | NetRipper_ | seen cr2 |
13:18.13 | NetRipper_ | ~seen cr2 |
13:18.19 | apt | cr2 <n=cr2@ip-109-84-74-80.web.vodafone.de> was last seen on IRC in channel #htc-linux, 391d 16h 57m 26s ago, saying: 'MrPippy: where is this source ?'. |
13:18.19 | NetRipper_ | !seen cr2 |
13:18.52 | Cotulla | hi NetRipper_ |
13:18.59 | NetRipper_ | hey cotulla |
13:21.13 | *** join/#htc-linux emwe_ (~emwe@cable-86-56-10-158.cust.telecolumbus.net) |
13:32.56 | *** join/#htc-linux Pr0z (Pr0z@bzq-84-109-104-106.red.bezeqint.net) |
13:45.47 | Ceesheim | Cotulla can I ask you one Quick question ? |
13:48.36 | *** join/#htc-linux Pr0z (~Proz@bzq-84-109-104-106.red.bezeqint.net) |
13:50.29 | ali1234 | Ceesheim: you just did |
13:51.34 | Ceesheim | :( |
13:52.16 | ali1234 | on irc it's generally prefered that you just ask the question :) |
13:52.45 | ali1234 | either you'll get an answer or you won't |
13:53.21 | Ceesheim | ok, is it possible to get the CID from a sd card without the use of a phone/android/wince |
13:53.55 | *** join/#htc-linux jonpry (~jonpry@63.245.31.4) |
13:54.31 | ali1234 | i thought CID was a phone specific thing? |
13:55.23 | ali1234 | however SD cards have a unique ID too, do you mean that? |
13:55.37 | Ceesheim | then explane this (and it work for some people) http://forum.xda-developers.com/showthread.php?t=875991 |
13:55.58 | Cotulla | I don't know anyway |
13:56.00 | ali1234 | ah gold cards |
13:56.06 | ali1234 | yes, i am slightly familiar with that stuff |
13:56.29 | ali1234 | you do need to know the SD card unique ID to make one, but that's not the same as the CID |
13:56.38 | ali1234 | and it is possible to get it, but not with all SD card readers |
13:56.45 | ali1234 | specifically, most USB ones cannot get it |
13:57.25 | Ceesheim | I have an asus eee with a cardreader slot build in , will that work ? |
13:58.27 | ali1234 | yes |
13:58.37 | Ceesheim | LOL ,how ? |
13:58.46 | ali1234 | there is some file in /sys where you can read it |
13:58.56 | ali1234 | hang on, let me check |
13:59.08 | Ceesheim | cool ,thanks |
14:00.21 | ali1234 | turns out the SD unique ID is also refered to as a CID, so it has two meanings related to goldcards |
14:00.55 | Ceesheim | they are the same ? |
14:01.22 | ali1234 | possibly |
14:01.40 | ali1234 | i understand CID as in "CID locked" but maybe that means "locked to a specific SD card CID" |
14:01.50 | ali1234 | never thought of it like that but it makes sense |
14:02.09 | Cotulla | CID is Country ID dude :P |
14:02.24 | jonpry | or carrier id |
14:02.31 | Cotulla | Country |
14:02.36 | Ceesheim | so you do know something about it :) |
14:03.24 | Cotulla | Ceesheimok, is it possible to get the CID from a sd card without the use of a phone/android/wince |
14:03.27 | Cotulla | I don't know this |
14:03.28 | Cotulla | :P |
14:03.45 | Ceesheim | bummer :( |
14:04.41 | ali1234 | here we go |
14:04.42 | ali1234 | /sys/class/mmc_host/mmc0/mmc0*/cid |
14:04.59 | ali1234 | as long as you have a native sd/mmc controller it will work on any linux |
14:05.10 | ali1234 | no doubt that the android tool uses the same interface |
14:05.35 | Ceesheim | and on windows ? |
14:05.37 | Ceesheim | 7* |
14:05.44 | ali1234 | i dunno, don't use it |
14:06.08 | ali1234 | make a linux bootable usb flash disk |
14:06.35 | ali1234 | or it's probably in the device manager somewhere |
14:08.23 | ali1234 | you could try this: http://jo0ls-dotnet-stuff.blogspot.com/2008/12/read-secure-digital-sd-card-serial.html |
14:10.22 | Ceesheim | thanks looking at it now |
14:11.39 | *** join/#htc-linux Pr0z (~Proz@bzq-84-109-104-106.red.bezeqint.net) |
14:24.35 | *** join/#htc-linux Pr0z (~Proz@bzq-84-109-104-106.red.bezeqint.net) |
14:30.55 | *** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com) |
14:31.49 | *** join/#htc-linux Padre (~Padre@intersoft-212.cust.smartspb.net) |
14:33.24 | Ceesheim | not working :( |
15:01.28 | *** join/#htc-linux thepace (~thepace@cable-178-148-12-118.dynamic.sbb.rs) |
15:11.55 | *** join/#htc-linux dekar_ (~dekar@port-92-193-21-206.dynamic.qsc.de) |
15:14.14 | *** join/#htc-linux Markinus (~Miranda@212.255.18.217) |
15:21.28 | *** join/#htc-linux kiozen (~kiozen@p5DDF3E87.dip.t-dialin.net) |
15:22.05 | *** join/#htc-linux detule (~gjoneski@bender.math.duke.edu) |
15:25.04 | *** join/#htc-linux Cees_heim (~Cees@p548034D2.dip.t-dialin.net) |
15:30.51 | *** join/#htc-linux |Jeroen| (~jeroen@d5152B25B.access.telenet.be) |
15:33.00 | *** join/#htc-linux Kasjopaja (~Tina@p578FFA56.dip.t-dialin.net) |
15:35.39 | *** join/#htc-linux GPFerror (~GPF@ip72-208-193-231.ph.ph.cox.net) |
15:40.06 | *** join/#htc-linux dan1j3l (~danijel@93-138-107-227.adsl.net.t-com.hr) |
15:44.03 | dan1j3l | hi |
15:52.53 | *** join/#htc-linux balans1 (~Gebruiker@82-170-217-205.ip.telfort.nl) |
15:59.03 | *** join/#htc-linux rob_w (~bob@ppp-188-174-68-231.dynamic.mnet-online.de) |
16:17.40 | Cees_heim | just want to say that it is working now , it was the sd cast (still the old sd card worked on a tp) now I used a 256mb card and all was good ali1234 |
16:17.56 | *** join/#htc-linux arrrghhh (~arrrghhh@173-130-246-108.pools.spcsdns.net) |
16:18.43 | *** join/#htc-linux arrrghhh_ (~arrrghhh@173-130-246-108.pools.spcsdns.net) |
16:18.49 | *** join/#htc-linux gauner1986 (~Miranda@2.209.103.72) |
16:23.04 | *** join/#htc-linux imilka (~kvirc@95-24-174-73.broadband.corbina.ru) |
16:32.55 | *** join/#htc-linux MN_ (568620c6@gateway/web/freenode/ip.86.134.32.198) |
16:44.01 | *** join/#htc-linux visof_ (~visof@41.238.233.11) |
16:49.26 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
16:53.17 | jonpry | Cotulla, how is that .32 going? |
16:54.11 | Cotulla | nice porting stuffs. currently microp |
16:54.30 | Cotulla | moved files to mach-msm for more conform |
16:54.38 | Cotulla | for fast access ;) |
16:55.18 | *** join/#htc-linux rob_w (~bob@ppp-188-174-68-231.dynamic.mnet-online.de) |
17:04.37 | *** join/#htc-linux GNUtoo|oeee (~GNUtoo@host68-143-dynamic.54-79-r.retail.telecomitalia.it) |
17:06.19 | *** join/#htc-linux furtardo (~mks@nat/yahoo/x-qarfbuvorlpvibni) |
17:09.17 | *** join/#htc-linux surgex (surge@pool-98-118-157-221.bflony.fios.verizon.net) |
17:10.49 | *** join/#htc-linux rob_w (~bob@ppp-188-174-68-231.dynamic.mnet-online.de) |
17:11.26 | *** join/#htc-linux csy7551 (~Anon@198.84-48-193.nextgentel.com) |
17:12.13 | *** join/#htc-linux akoma1s (quasselcor@metadosis.gr) |
17:12.14 | *** join/#htc-linux akoma1s (quasselcor@unaffiliated/akoma1s) |
17:12.30 | *** join/#htc-linux toastcfh (~toastcfh@29-37.200-68.tampabay.res.rr.com) |
17:13.35 | *** join/#htc-linux noellenchris-zzz (~kvirc@pool-173-61-114-241.cmdnnj.fios.verizon.net) |
17:15.02 | *** join/#htc-linux DuperMan (~Duper@93-173-182-97.bb.netvision.net.il) |
17:24.55 | *** join/#htc-linux t3g (~kvirc@62.158.88.61) |
17:25.57 | *** join/#htc-linux gauner1986 (~Miranda@p5B382C19.dip.t-dialin.net) |
17:31.00 | *** join/#htc-linux pupnik_ (~pupnik@unaffiliated/pupnik) |
17:38.04 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
17:42.27 | *** join/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
17:42.43 | Curious_ | does our "init" file for leo builds need to be replaced in other builds? or should i use their "init" file, i am talking about "init" executable |
17:42.49 | *** join/#htc-linux bzo (~chatzilla@netblock-68-183-234-14.dslextreme.com) |
17:49.25 | *** join/#htc-linux WisTilt2 (~wisgreg@wireless251.wirelesstcp.net) |
17:50.36 | WisTilt2 | bzo: congrats, you're a good choice to have been added to git commit. |
17:50.53 | bzo | thx Wis |
17:51.37 | WisTilt2 | F22: so how did the test go last night? |
17:55.06 | F22 | WisTilt2: In 12 hours i dropped from 93% to 85%. Not quite the amazing numbers you're getting, but i started above 90%, so i dunno. |
17:56.53 | WisTilt2 | that is well under 1% per hour, thats great. any wake up problems while being in sleep for hours? |
17:56.58 | XirXes | is that with sleep mode 0? |
17:57.35 | F22 | nope, it woke immediately up |
17:57.58 | F22 | i'm using sleep mode 1 |
17:58.03 | F22 | should i use 0? |
17:58.14 | WisTilt2 | nice. try mode 0 and you'll gain another bit |
17:58.43 | F22 | ok, will do |
17:58.47 | WisTilt2 | im seeing .2% per hour better in mode 0, which is not logical but it is working that way |
17:59.49 | WisTilt2 | your caps/fn leds still work in that last kernel correct? im going to commit that change by itself since there might be other devices with that weird microp version number. |
18:00.14 | XirXes | my g2 has very similar panel wake issues to the rhod. tho much less often. ive seen it happen on an evo aswell |
18:00.32 | Curious_ | ah tp2 spammers again |
18:00.34 | *** part/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
18:00.35 | F22 | yup, caps/fn still work great |
18:00.43 | *** join/#htc-linux cedesmith (~chatzilla@188.173.15.86) |
18:01.09 | WisTilt2 | XirXes is that happening with the standard OS that came with it or with modified stuff? |
18:01.59 | XirXes | its sense which it didnt come with on the american version. but the evo i saw it happen to had sprints firmware |
18:02.10 | XirXes | with on? |
18:06.20 | *** join/#htc-linux Nautis (63a95379@gateway/web/freenode/ip.99.169.83.121) |
18:08.35 | XirXes | when i wake it up sometimes the screen doesnt come up with it. i can still unlock it tho. when i press the power button again i see the screen come on for a small moment then it shuts off cause i just put it to sleep |
18:08.48 | XirXes | its really weird |
18:10.44 | XirXes | i just left winmo on my rhod with a 42% battery reading. when i booted into android i went and checked it it said 76% |
18:11.02 | XirXes | that has since dropped to 62% |
18:11.15 | *** join/#htc-linux balans2 (~Gebruiker@53543918.cm-6-5a.dynamic.ziggo.nl) |
18:12.07 | *** join/#htc-linux balans1 (~Gebruiker@53543918.cm-6-5a.dynamic.ziggo.nl) |
18:14.01 | *** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk) |
18:16.05 | WisTilt2 | XirXes which kernel are you running? |
18:16.36 | XirXes | i think its your button led test kernel. im a bit behind i think |
18:16.46 | *** join/#htc-linux kiozen (~kiozen@rgnb-5d865f3e.pool.mediaWays.net) |
18:17.10 | XirXes | ill check |
18:17.42 | *** join/#htc-linux GNUtoo|laptop (~gnutoo@host68-143-dynamic.54-79-r.retail.telecomitalia.it) |
18:18.29 | XirXes | 2.6.27.46-01256-gfd8badc-dirty (root@wireless251) |
18:18.56 | WisTilt2 | yeah get the current 1258 at least. i have some other changes in a test kernel but have only had arrrghhh and F22 try it so far. if you want to try it go ahead and dl the zImage, no kernel pack with this yet. you should see much improved panel wakes with this one. |
18:19.18 | XirXes | can do |
18:19.40 | WisTilt2 | and run sleep mode 0 |
18:20.05 | XirXes | whats the filename? i only have a link around for your kernel pack |
18:20.29 | WisTilt2 | same url with filename zImage |
18:25.29 | XirXes | ok its booting now. ill be testing batt life in airplane mode since this phone has no sim. should be interesting |
18:27.37 | *** join/#htc-linux balans2 (~Gebruiker@53543D1D.cm-6-5a.dynamic.ziggo.nl) |
18:29.16 | XirXes | so far no failed wakes. i like the fade in too |
18:43.08 | *** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk) |
18:44.08 | WisTilt2 | XirXes: is it waking up within 1 second most of the time? |
18:44.14 | XirXes | yea |
18:44.43 | XirXes | and just when i say that i have a failed wake |
18:44.43 | WisTilt2 | i forget, you have 210 or 400? |
18:44.47 | XirXes | 210 |
18:45.03 | WisTilt2 | on that failed wake can you still touch unlock and it comes up? |
18:45.17 | XirXes | iv found that when i have a failed wake opening the keyboard wakes the panel |
18:45.18 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
18:45.33 | XirXes | yeah. i did before i opened the keyboard |
18:45.54 | WisTilt2 | interesting... opening kbd grings it up with or without unlock screen? |
18:46.01 | WisTilt2 | grings=brings |
18:46.01 | XirXes | i unlocked it without the screen coming up actually |
18:46.12 | XirXes | yeah |
18:47.27 | XirXes | i just had a wake that took a tiny bit longer than the others and the black square was in the corner when it did |
18:49.12 | WisTilt2 | do you have autobl on or off? |
18:49.39 | XirXes | on |
18:50.53 | WisTilt2 | can i get you to try this next kernel |
18:51.01 | XirXes | sure |
18:51.29 | WisTilt2 | you want the modules also or just zimage? |
18:51.46 | XirXes | either way is fine |
18:52.14 | WisTilt2 | go ahead and get the kernel pack just to be sure |
18:53.02 | XirXes | md5 FC9CB37F425AA04CB879E0B3C2EDB5C8 |
18:53.20 | WisTilt2 | yep thats it |
18:55.07 | *** join/#htc-linux dekar_ (~dekar@drms-590cf9d1.pool.mediaWays.net) |
19:03.33 | XirXes | i just did 10 wakes and everyone was good. 3 or 4 of them i waited till it slept then woke it |
19:04.15 | WisTilt2 | is screen brightness ok after wake or too dull? |
19:04.20 | XirXes | it takes a bit longer to wake from sleep but its maybe a 1/4 second difference |
19:04.58 | XirXes | it fades to a good level id say. ill try turning on more light and try |
19:06.00 | XirXes | yeah its working fine with the auto bl |
19:06.46 | WisTilt2 | ok ill leave it where it is. thats about as fast as i can wake the panel up without making it go nuts. |
19:07.03 | *** join/#htc-linux gauner1986 (~Miranda@p5B382C19.dip.t-dialin.net) |
19:07.04 | XirXes | yeah it seems to be working well now |
19:07.31 | WisTilt2 | which rootfs are you running? |
19:07.51 | XirXes | id rather have it a little dim on wake and have to adjust (which it does) then have it come on at full bright when im in the dark |
19:08.04 | XirXes | f22s most recent i think |
19:08.42 | XirXes | yup. his feb 13th |
19:08.51 | WisTilt2 | same rootfs here. ok going to get back on this battery code. thanks for the tests. i email arrrghhh with the new test kernel pack to have the masses try. |
19:09.07 | XirXes | awesome. |
19:10.25 | XirXes | android gets closer to acurate with battery % when its been on a while. winmo said 40% when i installed the new kernel but when i booted i looked and it said 84% |
19:10.36 | XirXes | now its at 48% |
19:10.49 | bzo | WisTilt2: to fix the rhod100 panel stuff, was that just supporting a certain panel, or did you need to detect rhod100 differences as well? |
19:12.39 | *** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-12-212.bb.netbynet.ru) |
19:12.49 | XirXes | ill let you know if i have any failed wakes with this kernel. but it hasnt happened yet |
19:12.50 | Alex[sp3dev] | hi poop crowd! |
19:12.53 | WisTilt2 | bzo: what i found through trial and error was the rhod100 uses the same setup as the others with the exception of timing when you wake the panel up. not 100% on that though until we get a few more tests. |
19:13.32 | WisTilt2 | seems the AUO panels are much more critical to timing when powering up |
19:13.41 | WisTilt2 | hi alex |
19:13.58 | Alex[sp3dev] | jonpry, Cotulla: here is my rewritten microp. kill me for that, but it works on X1 ;) http://gitorious.org/linux-on-qualcomm-s-msm/alex-linux-xperia/commit/38dbb63ef31894df512647fd23537b1b0d869623 |
19:14.00 | bzo | WisTilt2: the reason I ask is the email I sent to the ml. Sounds like in your case you just need to know about the panel |
19:14.08 | WisTilt2 | XirXes yeah the battery polling take awhile to get to the actual level |
19:14.14 | bzo | it just happens to be used on the rhod100 |
19:15.33 | WisTilt2 | bzo: yeah just read your email. i think going with the model would be best since that can all be detected at mddi probe one time then used from then on. |
19:16.03 | Cotulla | hey Alex |
19:16.06 | XirXes | once it does it seems "fairly" accurate. 5% is more like 2 or 1% in my experience tho. i saw the 5% indicator then a minute later the phone was off without being able to turn on |
19:16.24 | Alex[sp3dev] | hey Cotulla. pretty unexpected of me to have kept the promise, huh? |
19:16.49 | Cotulla | no why not. but looks to code need to be sure it's good |
19:17.26 | Cotulla | MODULE_VERSION("0.2");? w00t? |
19:17.40 | bzo | Alex, you always say you are too busy, but you deliver new work anyways :P |
19:17.41 | Alex[sp3dev] | not sure it's very 'clean'.. was written in great hurry. right now the only limitation is that you cannot have more than one microp host (sounds reasonable. since we'll be using a separate driver for keypad) |
19:17.55 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
19:17.57 | Alex[sp3dev] | Cotulla: version 0.1 was original microp driver |
19:19.41 | jonpry | Alex[sp3dev]: looks nice |
19:20.10 | Cotulla | ow again chain of register drivers/devices |
19:20.24 | Alex[sp3dev] | Cotulla: i thought it was our mutual decision |
19:20.28 | Cotulla | but other looks nice |
19:20.40 | Cotulla | I mean who needs "htckovsky-microp-leds" device/driver |
19:20.48 | *** join/#htc-linux dan1j3l (~danijel@93-138-107-227.adsl.net.t-com.hr) |
19:21.16 | Alex[sp3dev] | well, drivers should be put according to their subsystems.. or in the platform directory, but i'll kill you for that |
19:22.17 | Cotulla | heh |
19:22.22 | Cotulla | I put all files there |
19:22.25 | Cotulla | bcz it's nice! |
19:22.51 | Cotulla | 166fail: |
19:22.51 | Cotulla | 167while (i >= 0) { |
19:22.51 | Cotulla | 168 platform_device_unregister(data->clients[i--]); |
19:22.51 | Cotulla | 169} |
19:22.53 | Cotulla | here btw |
19:23.02 | Cotulla | u call platform_device_unregister() for failed device too |
19:23.11 | Cotulla | seems |
19:23.16 | Alex[sp3dev] | nope |
19:23.22 | Alex[sp3dev] | the goto is before the loop exits |
19:23.34 | Cotulla | so some i == 4 fails |
19:23.41 | Cotulla | and it go out via goto |
19:23.45 | dan1j3l | hi |
19:24.12 | Alex[sp3dev] | good catch |
19:24.24 | Cotulla | or it won't |
19:24.47 | Alex[sp3dev] | it will |
19:24.57 | Cotulla | anyway it's not intersting |
19:25.11 | Cotulla | but for me it's bad code, because reader need remember such things |
19:25.28 | Alex[sp3dev] | ok, i will rewrite that. |
19:25.30 | Cotulla | it's why I put i--; after platform_device_unregister() |
19:25.36 | Cotulla | so it's clear for everybody |
19:25.47 | Cotulla | when it decremented after function call and etc |
19:26.01 | jonpry | it just occurred to me that microp-ng is next generation |
19:26.03 | *** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com) |
19:26.12 | Cotulla | and anyway |
19:26.20 | Cotulla | I looked to code and I lost execution flow |
19:26.25 | Cotulla | :D |
19:26.47 | Cotulla | and |
19:26.59 | Cotulla | will be probe of clients called during platform_device_register call or won't... |
19:27.05 | Cotulla | I think it won't |
19:27.09 | Alex[sp3dev] | what do you mean |
19:27.28 | Cotulla | u call platform_device_register() in probe() of microp |
19:27.33 | Alex[sp3dev] | yes |
19:27.40 | Cotulla | when this probe() of clients will be called? :P |
19:27.44 | Alex[sp3dev] | you can do nested platform_device_register calls |
19:27.44 | Cotulla | I have no clue |
19:28.17 | Cotulla | and who tell u that u can, btw? it may work but with errors |
19:28.36 | Cotulla | like if item added at the end of list - it will, but if item added before current item it won't... |
19:28.49 | Cotulla | but if u research it... ok |
19:28.55 | jonpry | lcdc does it that way |
19:29.03 | *** join/#htc-linux goxboxlive (~Adium@245.169.34.95.customer.cdi.no) |
19:29.10 | Cotulla | lcdc drivers sucks |
19:29.14 | Cotulla | there awful code flow |
19:29.20 | Cotulla | they register second devices with different ids |
19:29.26 | Cotulla | so they call them in loop |
19:29.45 | Alex[sp3dev] | msm framebuffer logic is completely inverted |
19:30.01 | Cotulla | last time I just removed all this stupid calls |
19:30.01 | Alex[sp3dev] | it's actually the board should register fb and panel.. not fb looping through panels |
19:30.10 | Cotulla | and added one device for msm_fb |
19:30.14 | Cotulla | with all inits called from it |
19:34.19 | Alex[sp3dev] | ok, pushed the fix for that loop index. but anyway, gotta go. need to do some homework to be free on weekends (actually want to finish 35 port this weekend) |
19:34.41 | Cotulla | bb |
19:40.00 | *** join/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
19:40.07 | Curious_ | Cotulla what does this mean rs30000048:00010000 rs30000048:00010000: setting system clock to 2011-02-18 19:36:12 UTC (1298057772) |
19:42.07 | XirXes | is there a reason why android cant be set up to use local time for the system clock? |
19:42.34 | Cotulla | it means cockpoo's android got cockpoo's time from cockpoo's RTC via cockpoo's RPC and put it as cockpoo's linux time? |
19:43.20 | Curious_ | got it |
19:43.48 | Curious_ | do we need htc_ril.so for leo or is ril_wrapper is enough? |
19:44.01 | Cotulla | both |
19:44.24 | Curious_ | can the boot loop be because of one missing? |
19:44.29 | Curious_ | or wrong file_? |
19:44.51 | Cotulla | it's android. it can. |
19:45.06 | Curious_ | heh |
19:45.30 | Curious_ | i replaced all 2.2 libs with 2.3 |
19:45.34 | Curious_ | fun :D |
19:45.41 | Curious_ | ah |
19:45.43 | Curious_ | 2.3 with 2.2 |
19:45.59 | *** join/#htc-linux dan1j3l (~danijel@93-141-23-74.adsl.net.t-com.hr) |
19:48.38 | bzo | jonpry - your newer patch restores all the memory, was that intentional? |
19:51.08 | jonpry | bzo: no |
19:51.18 | *** join/#htc-linux Erikson (~Erik@i5E86D582.versanet.de) |
19:51.22 | jonpry | i don't understand how that is possible |
19:51.39 | bzo | ? |
19:54.31 | jonpry | its like the patch is reversed |
19:59.16 | jonpry | bzo: i fixed it :p -R apparently |
19:59.33 | jonpry | i guess default it tells you how to undo :p |
20:00.17 | bzo | seems like a reasonable assumption for that use case |
20:19.17 | *** join/#htc-linux arrrghhh (~arrrghhh@173-130-246-108.pools.spcsdns.net) |
20:25.44 | Curious_ | Cotulla, what happens if i try to write 5mb to a 4mb partition |
20:25.59 | Curious_ | does it warn? |
20:27.40 | Cotulla | maybe it will choose 5mb instead of 4 |
20:28.10 | Curious_ | so there isn't protection? |
20:28.37 | Cotulla | it just will choose data size 5 mb or write 4 mb only instead of 5 |
20:28.50 | Curious_ | either way data corruption |
20:29.32 | Curious_ | then it might be the reason of my kernel panic :D |
20:30.14 | Cotulla | it wont' corrupt |
20:30.23 | Curious_ | i am talking about via CWM |
20:30.28 | Curious_ | i have 4mb boot |
20:30.31 | Curious_ | partition |
20:30.34 | Curious_ | but trying to flash 5mb |
20:30.37 | Curious_ | just realized |
20:30.51 | ali1234 | one thing is for sure, it isn't going to just magically work |
20:30.52 | Curious_ | it says "successful" |
20:31.04 | Curious_ | but fails epid |
20:31.04 | Curious_ | epic* |
20:33.08 | Cotulla | oh |
20:33.14 | Cotulla | I don't know how CWM works :) |
20:34.17 | Curious_ | what is SMD? |
20:36.04 | *** join/#htc-linux Jhinta (~Jhinta@s529c116e.adsl.wanadoo.nl) |
20:36.39 | cedesmith | Shared Memory Device |
20:41.57 | Curious_ | k |
20:43.12 | *** join/#htc-linux arrrghhh (~arrrghhh@173-130-246-108.pools.spcsdns.net) |
20:47.54 | Curious_ | when did you sneak out and did photon |
20:51.29 | *** part/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
20:53.44 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
20:53.57 | *** join/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
20:54.04 | Curious_ | is clock daemon important? |
20:54.22 | Curious_ | i get <3>init: cannot find '/system/bin/clockd', disabling 'clockd' |
20:54.35 | arrrghhh | you've been clockd |
20:54.36 | arrrghhh | cold clockd |
20:55.08 | Cotulla | hm |
20:55.14 | Cotulla | w00t |
20:55.34 | Curious_ | i am trying to boot this gingerbread sense thing |
20:55.41 | Curious_ | but no luck.. |
20:56.46 | arrrghhh | gb sense? |
20:56.49 | arrrghhh | orly? |
20:56.53 | Curious_ | http://forum.xda-developers.com/showthread.php?t=955680&page=13 |
20:57.45 | Curious_ | what lib is necessary to boot android other than libhtc_ril.so and libhtc_ril_wrapper.so |
20:58.42 | Cotulla | u need run brain.sys via wine |
20:58.52 | Curious_ | funny >x |
20:59.07 | Cotulla | I am serious |
20:59.15 | Cotulla | when u finish porting wine and etc |
20:59.21 | Cotulla | u will able to port GB also! |
20:59.25 | Curious_ | would you like me to be serious too? |
21:00.44 | Cotulla | ? |
21:01.32 | Curious_ | giant dick with a condom |
21:01.52 | Cotulla | yeah u in ur own style |
21:02.04 | Cotulla | I start afraid for u before :o |
21:02.36 | Cotulla | but maybe gingerbread make from trolls people & developers |
21:02.42 | cockdom | now i'm serious |
21:02.48 | cockdom | tell me |
21:02.56 | cockdom | what other lib is necessary |
21:03.04 | cockdom | or there isn't need for any other "specific" lib |
21:03.06 | Cotulla | u got crash at boot in logcat? |
21:03.07 | cockdom | to just boot |
21:03.16 | cockdom | i got dmesg |
21:03.20 | Cotulla | not enough |
21:03.24 | Cotulla | usually loop happen bcz u had bad permissions |
21:03.28 | Cotulla | and owners |
21:03.34 | Cotulla | did u try chmod 777 -R * |
21:03.35 | Cotulla | ? |
21:03.35 | cockdom | lmc again |
21:03.37 | cockdom | yes |
21:03.39 | cockdom | didn'T work |
21:03.50 | Cotulla | u extract files undrer root from img? |
21:04.15 | cockdom | i mounted it and applied chmod |
21:04.43 | cockdom | i got logcat |
21:04.56 | Cotulla | it may die at any problem |
21:05.03 | Cotulla | like wrong resolution for camera and etc |
21:05.04 | cockdom | lib.cso |
21:05.06 | cockdom | libc.so |
21:05.15 | cockdom | it loops |
21:05.35 | Cotulla | ? |
21:05.41 | cockdom | 1mn |
21:06.27 | cockdom | http://pastebin.com/zCdtLWvh |
21:07.42 | Cotulla | E/HAL ( 908): load: module=/system/lib/hw/gralloc.qsd8k.so |
21:07.42 | Cotulla | E/HAL ( 908): Cannot load library: reloc_library[1312]: 849 cannot locate 'android_atomic_cmpxchg'... |
21:07.42 | Cotulla | E/FramebufferNativeWindow( 908): Couldn't get gralloc module |
21:07.45 | Cotulla | :P |
21:08.13 | cockdom | why does it fail? |
21:08.26 | cockdom | i have it there |
21:08.49 | Cotulla | not compatible |
21:09.02 | cockdom | not compatible with gingerbread |
21:09.09 | cockdom | or is it due to wrong binary of omap? |
21:09.20 | Cotulla | maybe also because |
21:09.33 | cockdom | what :D |
21:09.36 | cockdom | "maybe also because" ? |
21:09.42 | Cotulla | both cases possible |
21:09.46 | Cotulla | but better replace |
21:09.49 | cockdom | hmm |
21:09.56 | Cotulla | system libs hw modules from 2.3 leo build |
21:09.59 | cockdom | then i should replace from a vanilla build |
21:10.04 | cockdom | a vanilla one? |
21:23.18 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
21:25.50 | *** join/#htc-linux crawling (crawling@a94-132-163-181.cpe.netcabo.pt) |
21:28.11 | *** join/#htc-linux ElFinLazz (~elfinlazz@112.154.189.103) |
21:34.42 | *** join/#htc-linux Homefix (~Homefix@184-198-207-123.pools.spcsdns.net) |
21:36.16 | Homefix | ubuntu running on my evo! a few issues though |
21:36.37 | arrrghhh | uhm |
21:36.45 | arrrghhh | this isn't so much a room for native android devices. |
21:36.56 | Homefix | nautilus cannot write to anything, however dolphin does |
21:37.07 | Homefix | ? |
21:37.09 | arrrghhh | are you running it with sudo? |
21:37.13 | Homefix | yes |
21:37.16 | arrrghhh | this room is for porting Android to winmo phones. |
21:37.21 | arrrghhh | so like hd2 |
21:37.22 | arrrghhh | tp2 |
21:37.22 | arrrghhh | etc |
21:37.39 | arrrghhh | specifically kernel discussion related to porting |
21:37.53 | Homefix | k |
21:38.11 | arrrghhh | #android would be a better room probably... |
21:38.15 | arrrghhh | not sure if there's an evo room or not |
21:38.27 | Homefix | no were to go :( |
21:38.38 | *** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912) |
21:38.44 | arrrghhh | Homefix, google? lol |
21:38.49 | Homefix | its really a ubuntu thing but #ubuntu told me to come here |
21:38.51 | Curious_ | go to -chat |
21:39.08 | Curious_ | heheh |
21:39.12 | arrrghhh | Homefix, hrm. no clue why they directed you here... |
21:39.16 | L_miller | arrrghhh -Do you just want my lastest NBH to flash? That will get you started.... |
21:39.25 | L_miller | lol wrong channel... ;) |
21:39.28 | arrrghhh | L_miller, lol |
21:39.31 | Homefix | http://forum.xda-developers.com/showthread.php?t=932754 this is why |
21:39.53 | Homefix | this is what im doing and thishttp://forum.xda-developers.com/showthread.php?p=10584098#post10584098 |
21:40.07 | arrrghhh | Homefix, so post in that thread!??! |
21:40.26 | Homefix | no one home |
21:40.43 | Homefix | !! |
21:40.47 | arrrghhh | ... |
21:40.56 | arrrghhh | you post your question and then wait. crazy concept, i know. |
21:41.03 | arrrghhh | better yet, search the thread |
21:41.07 | Homefix | to hostile or stuckup for me |
21:41.07 | arrrghhh | perhaps others have ran into the same issue. |
21:41.09 | *** part/#htc-linux Homefix (~Homefix@184-198-207-123.pools.spcsdns.net) |
21:41.14 | arrrghhh | lol |
21:43.22 | bzo | that's what you get for responding arrrghhh |
21:43.39 | arrrghhh | eh |
21:43.44 | arrrghhh | no skin off my nose. |
21:44.22 | Cotulla | lie to me |
21:44.42 | arrrghhh | you're pretty |
21:44.54 | Cotulla | ? |
21:44.56 | Curious_ | lol |
21:45.03 | arrrghhh | you said lie to you |
21:45.10 | jonpry | lol |
21:45.20 | Cotulla | okay |
21:45.23 | Cotulla | but I mean other |
21:45.34 | Curious_ | you are man |
21:45.53 | Cotulla | anyway black celebration now ;) |
21:46.11 | *** join/#htc-linux tre9 (d0360432@gateway/web/freenode/ip.208.54.4.50) |
21:46.32 | Curious_ | did u achieve smth |
21:47.01 | Cotulla | yeah |
21:47.33 | Curious_ | what? did you invent chocolate icecream? |
21:48.26 | Cotulla | http://www.youtube.com/watch?v=U2BSHNeQntY |
21:48.54 | *** join/#htc-linux [acl] (~abel@96.246.167.90) |
21:51.29 | *** join/#htc-linux MN_ (~yaaic@host86-134-32-198.range86-134.btcentralplus.com) |
21:54.57 | Curious_ | eeww |
21:55.08 | Curious_ | watch this |
21:55.09 | Curious_ | http://www.youtube.com/watch?v=lZqrG1bdGtg&oref=http%3A%2F%2Ftwitter.com%2F&has_verified=1 |
21:56.06 | Cotulla | ~seen cockdom |
21:56.14 | apt | cockdom <8bb3cff6@gateway/web/freenode/ip.139.179.207.246> was last seen on IRC in channel #htc-linux, 46m 10s ago, saying: 'a vanilla one?'. |
21:56.22 | arrrghhh | a vanilla cockdom? |
21:56.39 | *** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912) |
21:56.41 | Cotulla | what is cockdom? |
21:57.01 | arrrghhh | didn't we just go over that? |
21:57.05 | crawling | a cock dominatrix aka Curious_ |
21:57.44 | Curious_ | his port of brain via wine is bad |
21:57.50 | Curious_ | that is why he doesn't remember |
21:57.52 | Curious_ | full of bugs |
22:05.57 | *** join/#htc-linux tre9 (d036044e@gateway/web/freenode/ip.208.54.4.78) |
22:06.07 | *** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@89.32.146.153) |
22:09.49 | tre9 | on hd2 ubuntu, I enabled BTUSB in kernel. the HID keyboard pairs but when I type on it it seems to crash bluetoothd. the LDE on the dongle flashes quickly. any suggestions? |
22:10.13 | *** join/#htc-linux L_miller (~IceChat7@68-115-50-78.dhcp.eucl.wi.charter.com) |
22:10.42 | arrrghhh | tre9, -chat |
22:14.17 | L_miller | arrrghhh - The file i sent is also overclocked.... |
22:14.23 | *** part/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246) |
22:14.30 | arrrghhh | kk |
22:20.46 | L_miller | [acl] - did you see my post about the build scripts for tinboot-linux-msm being off. |
22:21.07 | [acl] | nahh |
22:21.12 | [acl] | i shall read right away |
22:21.19 | [acl] | thank you my good man |
22:21.37 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
22:21.46 | L_miller | Ok. It's in the Nates thread. |
22:21.58 | arrrghhh | at least my horrible failures help in some way :P |
22:22.17 | *** join/#htc-linux BoTToEsP (~maximo@212.21.250.251.dyn.user.ono.com) |
22:22.20 | L_miller | lol yup! |
22:23.55 | [acl] | L_miller: ok i see .. but what part specifically? fucking git.. i prob didnt sync bak .. :-( |
22:23.56 | L_miller | [acl] - do you think we should have just one script does all? |
22:24.18 | [acl] | L_miller: nahh.. let the autobuild handle it.. |
22:24.18 | arrrghhh | that would help tards like me :D |
22:24.37 | arrrghhh | nate probably just needs to update his guide. |
22:24.38 | L_miller | ok sounds good. |
22:24.41 | [acl] | cookers dont need to get involved with this stuff.. we know how to do it thats all that matters |
22:24.58 | L_miller | yup. |
22:24.59 | arrrghhh | indeed. if it works, they shouldn't care. |
22:25.36 | L_miller | I guess if you are just using autobuild to handle it then they will not need to be changed... |
22:25.53 | [acl] | yeah because the nasty part is already done.. |
22:26.15 | L_miller | It was just the dir and using rhod500 instoad of rhod... |
22:26.29 | L_miller | but you have that taken care of.. ;) |
22:26.30 | [acl] | ok i see ur zip |
22:26.49 | L_miller | yup. those are one script does all. |
22:26.58 | L_miller | Just updated from what Nate had. |
22:27.10 | [acl] | so nate is up and running right ? |
22:27.19 | L_miller | Not sure? |
22:27.35 | L_miller | Think he was still playing around with the busybox... :) |
22:27.48 | arrrghhh | heh |
22:30.40 | [acl] | well i want to eliminate that beotch |
22:31.48 | L_miller | yeah.. Do we need to save that much room? |
22:32.12 | L_miller | Seems 1.5 - 1.8 don't really hurt that much... |
22:32.20 | [acl] | well the kernel will grow |
22:32.40 | [acl] | but i think we are safe for now |
22:32.52 | [acl] | this is nates everest.. he wants to conguer |
22:32.54 | L_miller | Ohh... How much larger do you think it will get? |
22:33.03 | L_miller | lol yuppers. ;0 |
22:33.07 | arrrghhh | it's like 1.6mb now methinks |
22:33.12 | arrrghhh | (kernel that is) |
22:34.03 | L_miller | correct. |
22:34.43 | [acl] | i have more bullshit so im pushing 1.7 or so .. |
22:34.51 | [acl] | need to remove useless poop |
22:34.58 | [acl] | but im good.. solid boots.. solid everything actually |
22:35.05 | [acl] | just listening to pandora |
22:35.21 | [acl] | its like my dj device |
22:35.45 | L_miller | great. Me too. :) No camera yet... :( |
22:36.09 | arrrghhh | heh |
22:36.14 | arrrghhh | don't be that guy L_miller :P |
22:37.11 | L_miller | walks away with his head down... |
22:37.35 | arrrghhh | lol |
22:40.44 | L_miller | hey is there a way to clear out my modules folder? |
22:41.03 | toastcfh | [acl], any luck? |
22:41.15 | toastcfh | with fps fix ;x |
22:41.34 | arrrghhh | rm? lol |
22:42.35 | [acl] | toastcfh: ahh havent tried that much bro.. soon |
22:42.47 | L_miller | I have a bunch of links for old modules. |
22:43.11 | jonpry | 2.12MB on .35 |
22:43.26 | arrrghhh | [acl], not sure if you know but wistilt2 seems pretty positive that the issue with panel wake is the .35 fb. |
22:45.11 | *** join/#htc-linux Jhinta (~Jhinta@s529c116e.adsl.wanadoo.nl) |
22:45.13 | [acl] | hmm |
22:45.41 | [acl] | L_miller: have you had any panel SODs? |
22:45.43 | toastcfh | ahh |
22:46.12 | L_miller | I had one about a week ago. :) |
22:46.13 | [acl] | arrrghhh: we could always revert back to .27 :-p |
22:46.36 | [acl] | L_miller: u sure it was SOD and not system_server? |
22:46.38 | toastcfh | im working on opensource hdmi on theEVO |
22:46.48 | toastcfh | what a shit fest |
22:46.50 | arrrghhh | [acl], heh i didn't say that :P |
22:46.50 | [acl] | i know that when my system server is eating up the cpu, panel doesnt respond |
22:46.58 | L_miller | yup. Keyboard light didn't turn onn. |
22:47.17 | [acl] | arrrghhh: thing is i never get these SODs |
22:47.19 | toastcfh | ~seen phh |
22:47.20 | apt | phh is currently on #htc-linux (2d 3h 36m 51s) #kde (2d 3h 36m 51s) #openmoko-cdevel (2d 3h 36m 51s). Has said a total of 35 messages. Is idling for 1d 2h 10m 20s, last said: 'Alex[sp3dev]: yes'. |
22:47.37 | toastcfh | heh |
22:47.40 | [acl] | arrrghhh: so its hard to even look into right now. But any theories ? would help to pin point this down |
22:47.48 | [acl] | arrrghhh: also isnt this only affecting rhod? |
22:48.09 | toastcfh | apt lart phh for being gone so long |
22:48.09 | apt | offers phh some herring for being gone so long |
22:48.16 | [acl] | im sure emwe would have told us about SODs if it was affecting topaz as well |
22:48.23 | arrrghhh | [acl], well only RHOD properly powers down the panel.. no? |
22:48.31 | arrrghhh | it's not really an SoD thing |
22:48.34 | phh | toastcfh: ? |
22:48.35 | arrrghhh | it's just a 'failed wake' |
22:48.39 | toastcfh | ;p |
22:48.47 | [acl] | arrrghhh: nope. Topaz does it too |
22:48.49 | toastcfh | lol was just poking |
22:48.51 | arrrghhh | where the panel backlight comes up, LED goes orange... but panel never comes up. |
22:49.08 | arrrghhh | ah so the panel collapse code was ported to TOPA as well? |
22:49.14 | arrrghhh | need to get that to the rest of the devices. |
22:49.22 | arrrghhh | RAPH/DIAM users could really use it. |
22:50.00 | toastcfh | phh; u seen any open source hdmi api? >_> |
22:50.08 | phh | toastcfh: ?! |
22:50.22 | [acl] | arrrghhh: interesting stuff . also JB knows about this as well> wondering if this is affecting his builds. He has his own panel down process. |
22:50.28 | toastcfh | hdmi out |
22:50.43 | *** join/#htc-linux tailormoon (bestirc@vpn-178-217-160-117.didan.com.ua) |
22:50.44 | toastcfh | i got a working driver |
22:51.02 | toastcfh | just the mirroring in android is the bitch |
22:51.25 | *** join/#htc-linux fish_Hd2 (~yaaic@74-61-45-246.war.clearwire-wmx.net) |
22:52.04 | toastcfh | found some 7x30 stuff on CAF that implements overlay . it suxx though because our hw doesnt support overlay >_> |
22:52.19 | toastcfh | evo has a crap gpu |
22:52.59 | arrrghhh | [acl], jb has different panel collapse code? didn't know that. |
22:53.01 | [acl] | arrrghhh: the panel collapse code was around the topaz for a long time. before rhod actually. I think markinus wroet that bad boy |
22:53.08 | arrrghhh | oic |
22:53.35 | [acl] | arrrghhh: yeah dood.. jb reverse off the gsm dll. I reversed off the cdma dll.lol.. same stuff but the inits differ a bit.. |
22:53.39 | arrrghhh | crap |
22:53.45 | arrrghhh | something i was supposed to do before i leave work... |
22:53.51 | arrrghhh | huh |
22:53.57 | arrrghhh | well as long as it works. |
22:54.18 | arrrghhh | rhod100/auo panel folk seem to be reporting better results with wistilt2's newest test kernel. |
22:54.31 | [acl] | poor rhod100 |
22:54.33 | [acl] | no one cares |
22:54.34 | [acl] | :-p |
22:54.47 | arrrghhh | lol |
22:54.58 | arrrghhh | well we try to care. none of those schmos want to help test tho. |
22:55.15 | arrrghhh | or at least they're never around when we need them :P |
22:55.32 | [acl] | but in all seriousness. someone should revert the .35 fb and test. this way we can narrow it down |
22:55.42 | L_miller | [ac] - side note but I always get a warning about "mount_opt" not being found... Line 222 of init. |
22:55.50 | jonpry | [acl] you gonna help me flush out this sd card crap? |
22:56.19 | [acl] | L_miller: i think we can reomove that since we arent mounting on the init anymore. I'll look at it tonight |
22:56.44 | arrrghhh | [acl], oh pull the .35 commit and test the panel collapse? |
22:56.54 | [acl] | arrrghhh: yeah why not.lol |
22:56.55 | L_miller | Ok. |
22:56.57 | arrrghhh | you're just pulling yourself in too many directions at once bro :P |
22:57.13 | [acl] | jonpry: still some clock stuff to wrap up then i can help |
22:57.17 | [acl] | but yeah i should have time |
22:57.35 | jonpry | we might need better clocks on .35 |
22:58.31 | [acl] | jonpry: well i dunno if you saw JBs regime |
22:58.47 | [acl] | jonpry: still trying to merge tht into .27.. |
22:58.54 | jonpry | haven't looked at it |
22:59.07 | jonpry | it is the reversed winmo poop right? |
22:59.16 | [acl] | so once we finalize that i guess i can work on .35 clocks.. i know alex has some ideas. ooo also he finished a microp driver so we need to check that out |
22:59.19 | [acl] | yeah reverse |
22:59.35 | bzo | [acl] you should like at jb's tree for reference on the regime stuff |
22:59.43 | jonpry | well, i think we microp ksc first :p |
22:59.50 | bzo | I stripped out some stuff that looked like wip |
22:59.54 | [acl] | bzo: yeah i did.. studied it well. |
23:00.16 | [acl] | bzo: its good referece like i said.. but its hard to implement because of the way wince uses that shit. |
23:00.34 | bzo | ok, just wanted to check that you weren't looking at my sanitized version |
23:00.54 | [acl] | nahh.. i want to use his set rate more.. thats why im interested |
23:01.27 | bzo | so I guess it's back to the original plan or pulling what we want directly into clock-wince? |
23:02.42 | [acl] | bzo: nahh.. we can leave it alone for now but didnt you say that you wanted alexes clocks bck ? |
23:03.19 | bzo | well, by original plan I mean future of clocks for .35 |
23:03.33 | bzo | yeah, I think we want Alex's stuff integrated back in |
23:03.48 | [acl] | what was so different again ? remind me please? |
23:03.48 | arrrghhh | quittin time, cya guys on the flip side |
23:04.27 | bzo | [acl] difference between what? |
23:05.02 | [acl] | bzo: between whats there now and alexes ? besides the enable case statements |
23:05.29 | bzo | mostly the restructuring of the clock tables, and moving that stuff to the case statements |
23:05.56 | bzo | the logic is different though, alex had more specific handling in each case statement |
23:06.12 | bzo | but as you know there may be a couple of bugs |
23:06.29 | bzo | the offset raph800 screen and maybe sdcard |
23:06.48 | *** join/#htc-linux Ceesheim (~Ceesheim@p508DF525.dip.t-dialin.net) |
23:06.59 | [acl] | ahh yes |
23:07.06 | [acl] | anyways i gotta go.. so we will talk bout this lata |
23:07.08 | [acl] | thanks fellas |
23:53.03 | *** join/#htc-linux apt (~apt@rikers.org) |
23:53.03 | *** topic/#htc-linux is Welcome to the HTC Linux project | Community portal & WiKi http://htc-linux.org | For IRC logs, HaRET & kernel mailing lists etc. see http://htc-linux.org/wiki/index.php?title=Contact | The htc-linux.org project is not affiliated with the HTC Corporation | This channel is for development purposes - Join #htc-linux-chat for offtopic |
23:56.49 | *** join/#htc-linux MN_ (~yaaic@host86-134-32-198.range86-134.btcentralplus.com) |
23:57.09 | MN_ | hey cedesmith did you ever get rmnet working on lk |
23:58.17 | cedesmith | nope but probably doable now |
23:59.01 | cedesmith | as it seams MPU (Memory Protection Unit) is off when SPL loads cLK |
23:59.22 | cedesmith | tho i don't know what cotulla did to make it work |
23:59.48 | *** join/#htc-linux GPFerror (~GPF@ip72-208-193-231.ph.ph.cox.net) |