IRC log for #htc-linux on 20110218

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.27jonpry[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.15jonprystrange kernel crash http://pastebin.com/jLeir7FB
03:14.28arrrghhh[   56.558807] Unable to handle kernel NULL pointer dereference at virtual address 00000000
03:14.35arrrghhhsee that a lot with these reboots
03:15.16jonpryyou see this on .27?
03:15.52arrrghhhthat error yes
03:16.01arrrghhhthere's a bunch of gunk that's not familiar to me tho
03:16.37jonpryafaict it is crashing in the memory manager
03:16.49jonprywhich kills it pretty bad
03:17.04jonpryweird thing is i got 3 or 4 boots today into froyo
03:17.13jonprynow i get that crash everytime
03:17.24jonpryi'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.59WisTilt2arrrghhh you here or is that just your ghost
03:23.41arrrghhhi'm alive
03:23.44arrrghhhbarely
03:25.59WisTilt2anyone reporting loss of phone service but data still works?  this would be for the 1258 git kernel not my new test ones.
03:26.36arrrghhhhrm
03:26.38arrrghhhi don't think so
03:26.54arrrghhhi keep having the same guy saying he gets SoD's when driving in and out of good/bad service areas
03:27.22WisTilt2had 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.58arrrghhhdamn
03:28.19jonpryare there any reports of strange things happening after android use? like next time android won't boot, or even winmo?
03:28.54WisTilt2yeah 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.53WisTilt2jonpry: 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.07jonpryharet
03:30.34ali1234i have seen winmo fail to boot after using linux, not on MSM hardware though
03:30.52ali1234then again, i have seen winmo fail to boot after a normal restart
03:31.31WisTilt2how far into winmo boot does it get?
03:32.45jonprywinmo seems to be working ok for me
03:33.07jonprybut i vaguely remember someone saying they couldn't power on until reset button was hit or something
03:34.09WisTilt2only 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.44jonpryyeah, i think memory map is not right
03:36.05WisTilt2im 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.21arrrghhhmore panel tests?
03:36.53WisTilt2yeah since last night was kind of a bust with your panel staying off.
03:38.06arrrghhhheh
03:38.47WisTilt2ok image ready, same name as last night
03:39.08arrrghhhkk
03:39.22WisTilt2if 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.39jonpryhi bzo
03:42.01bzohey jonpry
03:42.45jonpryits like i have bad ram running under .35
03:43.24bzowinmo and 27 run ok?
03:43.36jonpryyeah
03:43.45jonpryand .35 seems to work depending on the wind
03:43.53jonprypresumably the temperature
03:43.59bzoit's gotta be some bug then
03:44.06bzocan't imagine it is a hardware problem
03:44.10bzoif the other stuff works
03:44.24bzo.35 has only been exercised much with the topaz
03:44.29jonpryyeah some bug
03:44.56F22WisTilt2: 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.11F22WisTilt2: 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.18jonpryi think it is temperature correlated
03:45.49*** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net)
03:46.29stinebdWisTilt2: nice job on the keyboard leds for rhod. i was using one earlier, it rocks
03:46.54WisTilt2F22: 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.49F22WisTilt2: 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.01WisTilt2stinebd: yeah, too bad all rhods werent the same, the 300 is backwards can you believe it?
03:48.26stinebdoh it was a 300 actually
03:49.35F22lol, 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.38WisTilt2same 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.06WisTilt2F22 is that on that engineering 210?
03:50.13F22WisTilt2: yup
03:50.58WisTilt2well, you probably understand when I say "not worth fixing for just 1 phone on the planet" :)
03:51.04F22i appear to have a microp version that isn't in the list.
03:51.25WisTilt2ah, get the version and we can add it.  its not 0xa88?
03:52.42F22[    2.449188] microp-klt: This hardware is not yet supported: 0688
03:52.42F22[    2.466644] microp-klt: probe of 0-0066 failed with error -524
03:54.01WisTilt2do either of the leds come on when hitting those keys or does it just die?
03:54.10F22leds do not come on, it just dies.
03:55.06F22i 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.49pupnikthanks for the info on the key scan codes F22
03:56.37WisTilt2if you want to try it ill add that version and see if it responds on our normal microp addy?
03:56.38F22pupnik: you're welcome. planning on doing something with them? :)
03:57.44pupnikunfortunately i may have to now that nokia isn't producing linux phones anymore
03:58.24F22WisTilt2: ok, sounds good.
03:58.26pupnikin 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.41WisTilt2F22: 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.53WisTilt2image only btw
04:02.53F22WisTilt2: will do
04:02.57F22ok
04:03.07WisTilt2arrrghhh did i blow up your phone?
04:03.15arrrghhhWisTilt2, nope ;)
04:03.27WisTilt2red lines are gone now hopefully
04:03.37arrrghhhheh haven't seen 'em yet
04:03.39arrrghhhthat was freaky
04:03.44arrrghhhthen... nothing.  lol
04:05.02WisTilt2notice any difference waking with this one?
04:05.27jonpryever see this: mmc_sd_detect(mmc1): Unable to re-detect card (-110)
04:05.32arrrghhhhad one slow wake out of 3 so far
04:05.43arrrghhhkinda fades in nicely now
04:05.53arrrghhhand abruptly shuts off ha
04:06.28WisTilt2jonpry: happen every boot?
04:06.43jonpryno, that was when it worked
04:06.51jonpryi finally got power button hooked up
04:06.57jonpryso i hit it
04:06.59bzojonpry: you could be running into the sdcard problem with alex clocks
04:07.03jonprywhich was a bad idea
04:07.24jonpryare alex's clocks in htc-msm-2.6.35?
04:07.31bzoyeah, think so
04:07.53jonpryproblem happens during wake?
04:08.13bzopossibly, you could try overriding sdcard freq w/ boot param
04:08.26jonpryits at 49MHZ or something
04:09.22bzothat's high isn't it?
04:09.42jonpryits ok for sdhc cards
04:10.18bzothere may be something happening in clock-wince that is not correctly setting it
04:10.26jonpryit seemed to sleep and wake almost 3 times before it crashed this time
04:10.54bzoarrrghhh: remember what that SD card problem workaround was off hand?
04:11.16arrrghhhyea
04:11.20arrrghhhcmdline option
04:11.41bzoyeah, what was it though?
04:11.46arrrghhhmsmsdcc_1bit msmsdcc_fmax=14000000
04:11.48arrrghhhsorry
04:11.50arrrghhhfinding it :P
04:12.04bzothx
04:12.13bzojonpry why don't you see if that helps?
04:12.23jonpryhmm
04:12.46jonpry1bit at 14mhz?
04:13.56F22WisTilt2: 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.11F22s/speader/speaker/
04:14.27WisTilt2nice.  maybe its going to be same microp and everything will work!
04:16.09F22caps/fn lights work beautifully, no lock up. no oopses.
04:16.36jonprybzo: i put in some extra printks, and i think the problem is with sd slot power
04:16.41stinebdWisTilt2: ok. leds for raph now.
04:17.13F22WisTilt2: very nice. :)
04:17.15WisTilt2F22 good deal, that was easy
04:17.25bzojonpry: we do get sd vdd error messages in 27 ...
04:17.54WisTilt2will be a funny commit... added microp version for the only phone on the planet like this one.
04:18.20F22lol, it may not be the only one, just the only one we know about. :P
04:18.54stinebdthere are some others stashed away in bins at htc's offices
04:19.17WisTilt2stinebd: those leds dont work on raph at all?
04:19.26stinebdthey work, they just don't reflect reality
04:19.33stinebdgotta be hooked into the keyboard driver i guess
04:19.41stinebdor correctly hooked
04:20.41WisTilt2yeah 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.24WisTilt2is it just the state that is wrong like caps lock and such?
04:21.44stinebdyeah
04:21.52stinebdso when you hit fn, it just toggles it
04:22.12stinebdfn (light goes on), fn (light goes off, but fn is locked so still on the alternate keys)
04:22.46jonprybzo: doesn't this sd problem with the 1bit thing prevent it from booting in the first place?
04:23.11WisTilt2should 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.38bzojonpry: quite possibly, arrrghhh is more familiar with the problem
04:24.13stinebdWisTilt2: the stuff in microp_keypad_led_event()?
04:24.14arrrghhhjonpry, yes
04:24.20arrrghhhsays "waiting for SD" basically
04:25.00jonpryyeah, i boot just fine
04:25.24arrrghhhdoesn't effect everyone.  i never had a problem either :P
04:26.01bzoI seem to recall the 27 stuff being modded from what came from upstream
04:26.17bzodunno what 35 is using (as far as the sd card stuff goes)
04:26.27jonprythis mmc.c is just copied from .27
04:26.49jonpryhttp://pastebin.com/sa8asxFY
04:27.09jonprythis is not exactly what you want to go down when running from sd card :p
04:27.41arrrghhhheh we just need to get off of SD :P
04:27.52bzojonpry and you say nand is a gimmick
04:28.14jonprylol
04:29.12arrrghhhWisTilt2, wakes seem great
04:29.53WisTilt2stinebd: yes that is part of it, the rest is in microp-ksc
04:29.58F22jonpry: 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.28WisTilt2stinebd: led_event does the actual logic and holds the current state of each key.
04:31.47WisTilt2arrrghhh: more stable?  you like the quick fade in on wake?
04:31.57arrrghhhyea, it's nice
04:32.12arrrghhhwhat happened to quick fade out?  :P
04:32.12WisTilt2any failed wakes where you had to touch unlock?
04:32.26arrrghhhi don't think so
04:32.33arrrghhhthere was one where i touched the screen right away
04:32.38arrrghhhright when it booted
04:32.58arrrghhhhrm
04:33.10arrrghhhthat was interesting.  i saw a little white square in the left corner
04:33.17WisTilt2i change that long time ago so when you hit power button the panel is powered off immediately rather than fade down
04:34.05WisTilt2yeah that square shows up now and then, dont know what it is, probably big brother watching now and then
04:34.13arrrghhhlol
04:34.26WisTilt2has to do with timing and the fb im sure
04:35.04arrrghhhso that was one failure
04:35.11arrrghhhin 10 maybe 15 wakes
04:35.38WisTilt2where it went back to sleep without panel coming up?
04:36.43arrrghhhyea
04:36.59WisTilt2F22 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.05WisTilt2arrrghhh do you mind trying one more test?  i want to drop the timing down some more so we can find the bottom.
04:38.43stinebdheh poor test slave
04:39.13F22WisTilt2: it appears not to be going into power collapse. led never turns green.
04:40.50WisTilt2thats something else keeping it up then. gps and all that stuff is off?
04:41.01F22let me double check all that stuff.
04:42.02WisTilt2arrrghhh next image ready when you're ready
04:43.59arrrghhhheh
04:44.01arrrghhhsame name?
04:45.28bzojonpry: do you think userland rpc connections could trigger a wakelock?
04:45.44jonpryperhaps
04:45.57jonprybut the phone is sleeping just fine
04:46.17bzobeen looking at the gps problem that prevents sleep
04:46.32bzoit keeps an rpc server/client open the whole time
04:46.43arrrghhhWisTilt2, 9e8ba2a28fee6112611600aab10c2e9d?
04:46.51jonpryyou want to sleep while gps is running?
04:47.11bzothe current lib keeps the rpc open even when not active
04:47.21bzoor at least the end points
04:47.21jonpryoh
04:47.56F22WisTilt2: 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.12bzothe vogue gps implementation does that to, but there the rpc stuff is called from within the kernel
04:49.00WisTilt2arrrghhh yes correct.
04:49.32F22by 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.37WisTilt2F22 some other app keeping it up then.  might try rebooting again?
04:49.41jonprybzo, i suppose its possible that rpc holds a lock if any device files are open
04:49.48jonprybut that seems like strange design
04:50.01F22ok, will try a reboot. i do have one interesting item in my dmesg. dunno if it's relevant.
04:50.14F22[ 2121.820343] msm_i2c msm_i2c.0: error, status 63c8
04:50.14F22[ 2121.820434] msm_i2c msm_i2c.0: Error during data xfer (-5)
04:50.24WisTilt2normal, you must have autobl off
04:50.32WisTilt2i need to fix that
04:50.34bzojonpry: are rpc connections supposed to be able to survive suspend?
04:50.34jonpryF22, you make a phone call?
04:51.05F22jonpry: not since last boot
04:51.54jonprydmesg is from last boot?
04:52.07F22this boot
04:52.20F22yes
04:52.39WisTilt2timestamps are not right
04:52.48WisTilt2unless you had it up for 45mins
04:53.27jonprybzo: i'm not sure
04:53.50jonprybut its not like it is rebuilding the /dev entries after a wake
04:54.30bzois that how RPC is implemented on the userland side?
04:54.47bzothere is that funny dex stuff for a11 to a9 rpc
04:54.55jonpryyeah its just some ghetto library that opens up the file and blast bytes into it
04:55.04jonpryjust a char stream
04:55.52jonpryhowever the kernel side of it, is not normal
04:56.07jonpryoncrpc people would shit a brick
04:56.20bzolol
04:56.42F22oh hmmm....i'll post the dmesg. the timestamps do seem strange
04:57.25F22uptime does say i've been up 45 min now.
04:58.18WisTilt2turn autobl on and you shouldnt see that i2c error.
04:59.25F22lots of core.c mmc_wait warnings. hmmm....
04:59.44F22turning autobl off
04:59.44*** join/#htc-linux dekar (~dekar@drms-590c5c46.pool.mediaWays.net)
05:01.35arrrghhhWisTilt2, 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.56WisTilt2so these you had to touch unlock to bring it up?
05:03.46jonprybzo: i tried slowing down the sd and such
05:04.08jonpryno luck
05:04.34bzoblech
05:06.06jonpryanywho its pretty stable with only 128MB enabled
05:06.42arrrghhhWisTilt2, i just let the cycle go, never woke the phone
05:06.46arrrghhhbl came up
05:06.49arrrghhhled went orange
05:06.50arrrghhhno panel
05:07.15bzojonpry: I do recall needing some tweaks for 27 to be able to use the 2nd bank with stability
05:07.30bzowith holes config or something
05:08.25jonpryyeah i'm using the bottom 64 of each, and standard .27 pmem which has its fingers in ebi1 and ebi2
05:09.10jonpryi've also got something that *looks* like a resume
05:10.02MassStashgrrrr nand...
05:10.08F22oh, 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.40arrrghhhWisTilt2, other than those 2 failed wakes, it's been quick to wake.
05:13.05WisTilt2better than before?
05:13.13arrrghhhyea
05:13.27arrrghhhevery time it's waked it's been under 1s i'd say
05:13.34WisTilt2F22 can you get a dmesg while in that condition?
05:13.46WisTilt2like the fade in or no?
05:14.07arrrghhhyea it's cool
05:14.18F22grabbed a dmesg just before i rebooted
05:14.20arrrghhhthere'll be some that would prefer the cut in.
05:14.34WisTilt2they can code it themselves:)
05:14.37arrrghhhdoesn't really matter to me, so long as it wakes consistently quick... which it has so far :P
05:14.38arrrghhhheh
05:14.50jonprybzo: your accepting patches for 35?
05:15.12arrrghhhah well.  i need to go to bed.
05:15.30arrrghhhWisTilt2, if you decide to make a kernel pack shoot me an email as usual.  i'll run with this kernel tonight.
05:15.34bzojonpry: better to send them to emwe for now, I've hardly looked at the 35 tree yet
05:15.48WisTilt2ok thanks, yeah and check your battery drain with this one
05:15.56arrrghhhsure
05:15.57arrrghhhg'nite guys
05:15.59WisTilt2oh, put it in sleep mode 0
05:16.01WisTilt2not 1
05:16.03arrrghhh0?
05:16.10stinebd?
05:16.11arrrghhhcan i change that on the fly?
05:16.11WisTilt2yeah.  then see what battery is like
05:16.12MassStashwow
05:16.14MassStash?
05:16.23WisTilt2trust me
05:16.24stinebdWisTilt2: btw do you know the difference between 0 and 1?
05:16.42WisTilt2stinebd: yes, 1 is collapse, 0 is suspend
05:16.59F22WisTilt2: http://pastebin.com/crGns3a2
05:17.11jonpryWisTilt2, what does that mean precisely?
05:17.36MassStash...
05:17.50stinebdright, we know the name difference but i don't think anybody knows what is actually happening that's different
05:18.01WisTilt2jonpry: in mode 0 arm11 is put in suspend not powered down, mode 1 its powered down
05:18.15stinebdwe've never seen any difference in battery consumption between those two
05:18.36arrrghhhi g2g.  i'll try 0 in the morning.. cya!
05:18.49stinebdor if we have, it's been too small to notice because it was lasting like 4 hours on battery anyway
05:18.59MassStashnow i guess we need to figure the dif between panel suspended and powered down
05:19.25WisTilt2stinebd: about .2% per hour better in mode 0 for whatever reason and only since bzo's pll patch
05:20.36MassStashhuh, very intriguing...
05:21.30*** join/#htc-linux goxboxlive (~jrs@mail2.hjellnesconsult.no)
05:22.20MassStashperhaps 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.46WisTilt2F22 dont see anything in logs that indicates the problem.  kbd lights and everything still work?
05:24.30F22didn'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.56WisTilt2happened after you turned autobl on?
05:26.00F22hmmm...i put to sleep, it appears it doesn't want to wake up.
05:26.11F22yup
05:26.17F22didn't have the issue before i turned autobl on.
05:26.18WisTilt2and autobl is on right now?
05:26.53WisTilt2hit power button then hold near a light and see if panel comes up
05:26.57F22i 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.16F22haven't turned autobl off since turning it back on i mean.
05:27.26F22will do
05:27.45WisTilt2almost sounds like the ambient reference value is 0 on wake
05:28.01WisTilt2putting near a light should bring it up if thats the case
05:28.45F22doesn't seem to react to a light at all
05:29.09WisTilt2is the backlight on and just not displaying anything or is it black
05:29.45WisTilt2hang on here... is this the device with that 0x7 id?
05:29.52F22backlight is off
05:29.57F22yes
05:30.30WisTilt2crapola.. ok hang on ill build another kernel.  inits are not right for that device in this kernel
05:30.52WisTilt2when autobl is enabled that is
05:30.55F22ah
05:31.45MassStashanyone kno what cotullas up to...?
05:32.04jonpry.32 rhod
05:33.06*** join/#htc-linux stinebd (~bryan@gentoo/developer/battousai)
05:33.52WisTilt2F22: ok try this one
05:34.00F22will do
05:44.08F22that 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.35F22this was after putting the phone to sleep with the new kernel and autobl on.
05:44.51F22WisTilt2: ^
05:46.27WisTilt2might 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.50F22yep, i haven't needed to touch the screen yet however despite putting it to sleep and waking a good dozen times.
05:50.12WisTilt2wake up time within 1sec or so?
05:50.29F22yup, about right
05:50.52F22except when it gets stuck
05:51.19F22just had it get stuck a second time, didn't try pressing it a second time this time.
05:51.39WisTilt2thats 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.20F22i saw a single partial line once.
05:52.40F22every other time i haven't seen anything
05:52.57WisTilt2should be wide faintly black line from top to bottom as it fades in
05:53.11WisTilt2its pretty fast though so might not always see it
05:53.33*** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey)
05:53.41F22no, this was not vertical, it was more like a very brief horizontal artifact.
05:54.06WisTilt2well this kernel should work the same on the rhod100 AUO's now so maybe we'll be done with it finally
05:54.37WisTilt2yeah thats it, might not always be at top depending on where vsync is at the time
05:56.55WisTilt2bzo: got some interesting info for you regarding vregs and dex if you're not in the middle of something...
05:56.56F22haven'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.19bzoWisTilt2: what's up?
05:57.36WisTilt2F22:i dont think those occasional non-wakes can be fixed until we get acl to tweak the fb
05:58.43F22hmm...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.07WisTilt2bzo: 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.41WisTilt2just disabling gp4 gets us down to .5% or less consistently
06:00.32WisTilt2and another note, im not using the gpio power down at all
06:01.36WisTilt2F22: if you can, see what kind of battery drain you get overnight with that setup also
06:02.22F22ok, will do.
06:02.33bzoWisTilt2: hmm, that's interesting. I think jb's stuff is reversed from the rhod300 dlls
06:03.07WisTilt2might be why im seeing better battery than in winmo:)
06:04.04bzotrue, lol
06:04.37WisTilt2also, 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.18F22damn docs...lol
06:06.42WisTilt2yeah, 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.24bzoWisTilt2: btw, speaking of vreg, I noticed the other day that wifi power off is not implemented
06:07.34bzoonce you turn off, you can't turn off, lol
06:07.47bzoerr I mean once you turn on, you can't turn off
06:08.10WisTilt2huh? you mean when you power wifi on then off the power is still really on?
06:08.49bzoyeah, I guess the original author ran into problem turning it off, so it is commented out
06:08.55F22WisTilt2: btw, you need to treat caps/fn lights for 110's just like the 100's.
06:09.06WisTilt2is that missing in userland or kernel?
06:09.38WisTilt2what is a 110?? i only knew of 100,210,300,400,500
06:09.46F22110's are australian
06:10.00WisTilt2same 0x13 AUO panel?
06:10.51F22not entirely certain on the panel. i know the key layout is identical to the 100 uk
06:11.30WisTilt2should work as is then i think
06:11.54WisTilt2i only had to reverse the bits on the 300 and all others were normal
06:12.11F22wasn't 100 different?
06:12.22F22had a different value for fn?
06:12.41WisTilt2oh yes... i havent added that yet
06:12.55bzoWisTilt2: kernel mmc.c
06:13.01F22so for that one, treat 110 the same.
06:13.37WisTilt2ok, ill have to pull machine variant for 110 also.  need to make a note or ill forget
06:13.53WisTilt2bzo: whats the power drain with wifi on do you know?
06:14.30bzoWisTilt2: never measured it
06:14.32stinebdheh
06:14.49stinebdanother one of those things that nobody would've noticed before when battery was lasting 4 hours
06:14.56F22to 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.08F22s/100/110/
06:15.27stinebdWisTilt2: i can look up the wifi consumption on passion which has a 4329 if that helps to compare
06:16.06WisTilt2stinebd: yeah would be interested to know.  im sure lots of people use wifi then turn it off when done to save power
06:16.27stinebdthose bcms are very very good on power
06:16.51WisTilt2someone said wifi uses less power than 3g is that true?
06:16.56stinebdyeah
06:16.59bzoit's just the vreg not getting turned off, there are power gpios that are implemented
06:17.01stinebdi might've said that
06:17.21bzoso turning it off does something, perhaps even close to fully powered off?
06:17.43WisTilt2vreg will probably make a difference though if its the same gain we saw in the panel
06:18.32stinebd<PROTECTED>
06:18.35stinebd(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.23bzo4ma is pretty low
06:19.26WisTilt24ma idle is not much but adds up over a day. 120ma in use is up there.
06:19.26stinebdcomparitively   <item name="radio.active">300</item>
06:19.42WisTilt2arent they only 20-30milliwatt radios?
06:19.43stinebdso it does indeed use less than 3g
06:20.17stinebdradio.on = 3
06:21.17WisTilt2almost 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.35stinebdcrazy right?
06:21.45stinebdand you can definitely see the results on n1
06:22.56stinebdbluetooth 0.3 haha
06:24.01WisTilt2yeah for 30ft doesnt take much power at all
06:24.40stinebdwe should probably get that working at some point
06:25.14stinebdus americans are too lazy to be holding phones to our ear
06:25.28WisTilt2if 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.59stinebdso we should call and ask them to do that?
06:26.46WisTilt2just 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.00WisTilt2have you seen that stuff yet?
06:27.27stinebdcan that be hooked into nexus s's NFC somehow?
06:28.29WisTilt2dont 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.56F22as long as it doesn't give us brain cancer 10 years from now i'm up for that. :D
06:28.59WisTilt2cost could be a show stopper though
06:29.18stinebdso if the cancer waits for 11 years you support it?
06:29.45WisTilt2no cancer, no radio waves on your head, just sensors fed to a computer
06:29.58stinebdthat's what the government wants you to think man
06:30.09stinebdit's all a ploy man to get into your thoughts man
06:30.13F22stinebd: lol
06:30.25F22that's what the tin foil helmets are for...
06:30.46WisTilt2true, big brother wants to control everything now, why not our thoughts too
06:31.09stinebdwell it'll probably be mcdonalds first
06:31.17stinebdthink about it. commercials in your sleep. what a cash cow.
06:31.55stinebd</conspiracy,man>
06:32.15*** join/#htc-linux MacDrunk (~marper@201.165.161.195)
06:35.06WisTilt2well guys im out for the night.  F22 let me know what kind of battery results you get.  catch you all tomorrow.
06:38.13F22i'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.40stinebdheh 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.07jozefkhello. 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.08jozefkafter 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.23pupnikandroid -> #android :)
08:25.39jozefkis 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.09pupnikjozefk: 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.23visofhello
11:03.37visofi have installed android and want to add another fonts to /system/fonts in system.ex2fs
11:03.40visofhow can i do that
11:04.04visofhow can i extract the content of that file under linux ?
11:05.23visofi'm trying to use android under htc diamond
11:05.29visofplease 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.13SG~seen mdeejay
12:39.17aptmdeejay <~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.36L_millerMassStash!
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.47gauner1986hey 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.10NetRipper_seen cr2
13:18.13NetRipper_~seen cr2
13:18.19aptcr2 <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.19NetRipper_!seen cr2
13:18.52Cotullahi NetRipper_
13:18.59NetRipper_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.47CeesheimCotulla 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.29ali1234Ceesheim: you just did
13:51.34Ceesheim:(
13:52.16ali1234on irc it's generally prefered that you just ask the question :)
13:52.45ali1234either you'll get an answer or you won't
13:53.21Ceesheimok, 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.31ali1234i thought CID was a phone specific thing?
13:55.23ali1234however SD cards have a unique ID too, do you mean that?
13:55.37Ceesheimthen explane this (and it work for some people) http://forum.xda-developers.com/showthread.php?t=875991
13:55.58CotullaI don't know anyway
13:56.00ali1234ah gold cards
13:56.06ali1234yes, i am slightly familiar with that stuff
13:56.29ali1234you do need to know the SD card unique ID to make one, but that's not the same as the CID
13:56.38ali1234and it is possible to get it, but not with all SD card readers
13:56.45ali1234specifically, most USB ones cannot get it
13:57.25CeesheimI have an asus eee with a cardreader slot build in , will that work ?
13:58.27ali1234yes
13:58.37CeesheimLOL ,how ?
13:58.46ali1234there is some file in /sys where you can read it
13:58.56ali1234hang on, let me check
13:59.08Ceesheimcool ,thanks
14:00.21ali1234turns out the SD unique ID is also refered to as a CID, so it has two meanings related to goldcards
14:00.55Ceesheimthey are the same ?
14:01.22ali1234possibly
14:01.40ali1234i understand CID as in "CID locked" but maybe that means "locked to a specific SD card CID"
14:01.50ali1234never thought of it like that but it makes sense
14:02.09CotullaCID is Country ID dude :P
14:02.24jonpryor carrier id
14:02.31CotullaCountry
14:02.36Ceesheimso you do know something about it :)
14:03.24CotullaCeesheimok, is it possible to get the CID from a sd card without the use of a phone/android/wince
14:03.27CotullaI don't know this
14:03.28Cotulla:P
14:03.45Ceesheimbummer :(
14:04.41ali1234here we go
14:04.42ali1234/sys/class/mmc_host/mmc0/mmc0*/cid
14:04.59ali1234as long as you have a native sd/mmc controller it will work on any linux
14:05.10ali1234no doubt that the android tool uses the same interface
14:05.35Ceesheimand on windows ?
14:05.37Ceesheim7*
14:05.44ali1234i dunno, don't use it
14:06.08ali1234make a linux bootable usb flash disk
14:06.35ali1234or it's probably in the device manager somewhere
14:08.23ali1234you could try this: http://jo0ls-dotnet-stuff.blogspot.com/2008/12/read-secure-digital-sd-card-serial.html
14:10.22Ceesheimthanks 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.24Ceesheimnot 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.03dan1j3lhi
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.40Cees_heimjust 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.17jonpryCotulla, how is that .32 going?
16:54.11Cotullanice porting stuffs. currently microp
16:54.30Cotullamoved files to mach-msm for more conform
16:54.38Cotullafor 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.43Curious_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.36WisTilt2bzo: congrats, you're a good choice to have been added to git commit.
17:50.53bzothx Wis
17:51.37WisTilt2F22: so how did the test go last night?
17:55.06F22WisTilt2: 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.53WisTilt2that is well under 1% per hour, thats great. any wake up problems while being in sleep for hours?
17:56.58XirXesis that with sleep mode 0?
17:57.35F22nope, it woke immediately up
17:57.58F22i'm using sleep mode 1
17:58.03F22should i use 0?
17:58.14WisTilt2nice. try mode 0 and you'll gain another bit
17:58.43F22ok, will do
17:58.47WisTilt2im seeing .2% per hour better in mode 0, which is not logical but it is working that way
17:59.49WisTilt2your 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.14XirXesmy g2 has very similar panel wake issues to the rhod. tho much less often. ive seen it happen on an evo aswell
18:00.32Curious_ah tp2 spammers again
18:00.34*** part/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246)
18:00.35F22yup, caps/fn still work great
18:00.43*** join/#htc-linux cedesmith (~chatzilla@188.173.15.86)
18:01.09WisTilt2XirXes is that happening with the standard OS that came with it or with modified stuff?
18:01.59XirXesits sense which it didnt come with on the american version. but the evo i saw it happen to had sprints firmware
18:02.10XirXeswith on?
18:06.20*** join/#htc-linux Nautis (63a95379@gateway/web/freenode/ip.99.169.83.121)
18:08.35XirXeswhen 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.48XirXesits really weird
18:10.44XirXesi 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.02XirXesthat 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.05WisTilt2XirXes which kernel are you running?
18:16.36XirXesi 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.10XirXesill check
18:17.42*** join/#htc-linux GNUtoo|laptop (~gnutoo@host68-143-dynamic.54-79-r.retail.telecomitalia.it)
18:18.29XirXes2.6.27.46-01256-gfd8badc-dirty (root@wireless251)
18:18.56WisTilt2yeah 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.18XirXescan do
18:19.40WisTilt2and run sleep mode 0
18:20.05XirXeswhats the filename? i only have a link around for your kernel pack
18:20.29WisTilt2same url with filename zImage
18:25.29XirXesok 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.16XirXesso far no failed wakes. i like the fade in too
18:43.08*** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk)
18:44.08WisTilt2XirXes: is it waking up within 1 second most of the time?
18:44.14XirXesyea
18:44.43XirXesand just when i say that i have a failed wake
18:44.43WisTilt2i forget, you have 210 or 400?
18:44.47XirXes210
18:45.03WisTilt2on that failed wake can you still touch unlock and it comes up?
18:45.17XirXesiv 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.33XirXesyeah. i did before i opened the keyboard
18:45.54WisTilt2interesting... opening kbd grings it up with or without unlock screen?
18:46.01WisTilt2grings=brings
18:46.01XirXesi unlocked it without the screen coming up actually
18:46.12XirXesyeah
18:47.27XirXesi 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.12WisTilt2do you have autobl on or off?
18:49.39XirXeson
18:50.53WisTilt2can i get you to try this next kernel
18:51.01XirXessure
18:51.29WisTilt2you want the modules also or just zimage?
18:51.46XirXeseither way is fine
18:52.14WisTilt2go ahead and get the kernel pack just to be sure
18:53.02XirXesmd5 FC9CB37F425AA04CB879E0B3C2EDB5C8
18:53.20WisTilt2yep thats it
18:55.07*** join/#htc-linux dekar_ (~dekar@drms-590cf9d1.pool.mediaWays.net)
19:03.33XirXesi just did 10 wakes and everyone was good. 3 or 4 of them i waited till it slept then woke it
19:04.15WisTilt2is screen brightness ok after wake or too dull?
19:04.20XirXesit takes a bit longer to wake from sleep but its maybe a 1/4 second difference
19:04.58XirXesit fades to a good level id say. ill try turning on more light and try
19:06.00XirXesyeah its working fine with the auto bl
19:06.46WisTilt2ok 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.04XirXesyeah it seems to be working well now
19:07.31WisTilt2which rootfs are you running?
19:07.51XirXesid 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.04XirXesf22s most recent i think
19:08.42XirXesyup. his feb 13th
19:08.51WisTilt2same 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.07XirXesawesome.
19:10.25XirXesandroid 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.36XirXesnow its at 48%
19:10.49bzoWisTilt2: 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.49XirXesill let you know if i have any failed wakes with this kernel. but it hasnt happened yet
19:12.50Alex[sp3dev]hi poop crowd!
19:12.53WisTilt2bzo: 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.32WisTilt2seems the AUO panels are much more critical to timing when powering up
19:13.41WisTilt2hi alex
19:13.58Alex[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.00bzoWisTilt2: 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.08WisTilt2XirXes yeah the battery polling take awhile to get to the actual level
19:14.14bzoit just happens to be used on the rhod100
19:15.33WisTilt2bzo: 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.03Cotullahey Alex
19:16.06XirXesonce 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.24Alex[sp3dev]hey Cotulla. pretty unexpected of me to have kept the promise, huh?
19:16.49Cotullano why not. but looks to code need to be sure it's good
19:17.26CotullaMODULE_VERSION("0.2");? w00t?
19:17.40bzoAlex, you always say you are too busy, but you deliver new work anyways :P
19:17.41Alex[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.57Alex[sp3dev]Cotulla: version 0.1 was original microp driver
19:19.41jonpryAlex[sp3dev]: looks nice
19:20.10Cotullaow again chain of register drivers/devices
19:20.24Alex[sp3dev]Cotulla: i thought it was our mutual decision
19:20.28Cotullabut other looks nice
19:20.40CotullaI 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.16Alex[sp3dev]well, drivers should be put according to their subsystems.. or in the platform directory, but i'll kill you for that
19:22.17Cotullaheh
19:22.22CotullaI put all files there
19:22.25Cotullabcz it's nice!
19:22.51Cotulla166fail:
19:22.51Cotulla167while (i >= 0) {
19:22.51Cotulla168  platform_device_unregister(data->clients[i--]);
19:22.51Cotulla169}
19:22.53Cotullahere btw
19:23.02Cotullau call  platform_device_unregister() for failed device too
19:23.11Cotullaseems
19:23.16Alex[sp3dev]nope
19:23.22Alex[sp3dev]the goto is before the loop exits
19:23.34Cotullaso some i == 4 fails
19:23.41Cotullaand it go out via goto
19:23.45dan1j3lhi
19:24.12Alex[sp3dev]good catch
19:24.24Cotullaor it won't
19:24.47Alex[sp3dev]it will
19:24.57Cotullaanyway it's not intersting
19:25.11Cotullabut for me it's bad code, because reader need remember such things
19:25.28Alex[sp3dev]ok, i will rewrite that.
19:25.30Cotullait's why I put i--; after platform_device_unregister()
19:25.36Cotullaso it's clear for everybody
19:25.47Cotullawhen it decremented after function call and etc
19:26.01jonpryit 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.12Cotullaand anyway
19:26.20CotullaI looked to code and I lost execution flow
19:26.25Cotulla:D
19:26.47Cotullaand
19:26.59Cotullawill be probe of clients called during platform_device_register call or won't...
19:27.05CotullaI think it won't
19:27.09Alex[sp3dev]what do you mean
19:27.28Cotullau call platform_device_register() in probe() of microp
19:27.33Alex[sp3dev]yes
19:27.40Cotullawhen this probe() of clients will be called? :P
19:27.44Alex[sp3dev]you can do nested platform_device_register calls
19:27.44CotullaI have no clue
19:28.17Cotullaand who tell u that u can, btw? it may work but with errors
19:28.36Cotullalike if item added at the end of list - it will, but if item added before current item it won't...
19:28.49Cotullabut if u research it... ok
19:28.55jonprylcdc does it that way
19:29.03*** join/#htc-linux goxboxlive (~Adium@245.169.34.95.customer.cdi.no)
19:29.10Cotullalcdc drivers sucks
19:29.14Cotullathere awful code flow
19:29.20Cotullathey register second devices with different ids
19:29.26Cotullaso they call them in loop
19:29.45Alex[sp3dev]msm framebuffer logic is completely inverted
19:30.01Cotullalast time I just removed all this stupid calls
19:30.01Alex[sp3dev]it's actually the board should register fb and panel.. not fb looping through panels
19:30.10Cotullaand added one device for msm_fb
19:30.14Cotullawith all inits called from it
19:34.19Alex[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.41Cotullabb
19:40.00*** join/#htc-linux Curious_ (8bb3cff6@gateway/web/freenode/ip.139.179.207.246)
19:40.07Curious_Cotulla what does this mean rs30000048:00010000 rs30000048:00010000: setting system clock to 2011-02-18 19:36:12 UTC (1298057772)
19:42.07XirXesis there a reason why android cant be set up to use local time for the system clock?
19:42.34Cotullait 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.20Curious_got it
19:43.48Curious_do we need htc_ril.so for leo or is ril_wrapper is enough?
19:44.01Cotullaboth
19:44.24Curious_can the boot loop be because of one missing?
19:44.29Curious_or wrong file_?
19:44.51Cotullait's android. it can.
19:45.06Curious_heh
19:45.30Curious_i replaced all 2.2 libs with 2.3
19:45.34Curious_fun :D
19:45.41Curious_ah
19:45.43Curious_2.3 with 2.2
19:45.59*** join/#htc-linux dan1j3l (~danijel@93-141-23-74.adsl.net.t-com.hr)
19:48.38bzojonpry - your newer patch restores all the memory, was that intentional?
19:51.08jonprybzo: no
19:51.18*** join/#htc-linux Erikson (~Erik@i5E86D582.versanet.de)
19:51.22jonpryi don't understand how that is possible
19:51.39bzo?
19:54.31jonpryits like the patch is reversed
19:59.16jonprybzo: i fixed it :p -R apparently
19:59.33jonpryi guess default it tells you how to undo :p
20:00.17bzoseems 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.44Curious_Cotulla, what happens if i try to write 5mb to a 4mb partition
20:25.59Curious_does it warn?
20:27.40Cotullamaybe it will choose 5mb instead of 4
20:28.10Curious_so there isn't protection?
20:28.37Cotullait just will choose data size 5 mb or write 4 mb only instead of 5
20:28.50Curious_either way data corruption
20:29.32Curious_then it might be the reason of my kernel panic :D
20:30.14Cotullait wont' corrupt
20:30.23Curious_i am talking about via CWM
20:30.28Curious_i have 4mb boot
20:30.31Curious_partition
20:30.34Curious_but trying to flash 5mb
20:30.37Curious_just realized
20:30.51ali1234one thing is for sure, it isn't going to just magically work
20:30.52Curious_it says "successful"
20:31.04Curious_but fails epid
20:31.04Curious_epic*
20:33.08Cotullaoh
20:33.14CotullaI don't know how CWM works :)
20:34.17Curious_what is SMD?
20:36.04*** join/#htc-linux Jhinta (~Jhinta@s529c116e.adsl.wanadoo.nl)
20:36.39cedesmithShared Memory Device
20:41.57Curious_k
20:43.12*** join/#htc-linux arrrghhh (~arrrghhh@173-130-246-108.pools.spcsdns.net)
20:47.54Curious_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.04Curious_is clock daemon important?
20:54.22Curious_i get <3>init: cannot find '/system/bin/clockd', disabling 'clockd'
20:54.35arrrghhhyou've been clockd
20:54.36arrrghhhcold clockd
20:55.08Cotullahm
20:55.14Cotullaw00t
20:55.34Curious_i am trying to boot this gingerbread sense thing
20:55.41Curious_but no luck..
20:56.46arrrghhhgb sense?
20:56.49arrrghhhorly?
20:56.53Curious_http://forum.xda-developers.com/showthread.php?t=955680&page=13
20:57.45Curious_what lib is necessary to boot android other than libhtc_ril.so and libhtc_ril_wrapper.so
20:58.42Cotullau need run brain.sys via wine
20:58.52Curious_funny >x
20:59.07CotullaI am serious
20:59.15Cotullawhen u finish porting wine and etc
20:59.21Cotullau will able to port GB also!
20:59.25Curious_would you like me to be serious too?
21:00.44Cotulla?
21:01.32Curious_giant dick with a condom
21:01.52Cotullayeah u in ur own style
21:02.04CotullaI start afraid for u before  :o
21:02.36Cotullabut maybe gingerbread make from trolls people & developers
21:02.42cockdomnow i'm serious
21:02.48cockdomtell me
21:02.56cockdomwhat other lib is necessary
21:03.04cockdomor there isn't need for any other "specific" lib
21:03.06Cotullau got crash at boot in logcat?
21:03.07cockdomto just boot
21:03.16cockdomi got dmesg
21:03.20Cotullanot enough
21:03.24Cotullausually loop happen bcz u had bad permissions
21:03.28Cotullaand owners
21:03.34Cotulladid u try chmod 777 -R *
21:03.35Cotulla?
21:03.35cockdomlmc again
21:03.37cockdomyes
21:03.39cockdomdidn'T work
21:03.50Cotullau extract files undrer root from img?
21:04.15cockdomi mounted it and applied chmod
21:04.43cockdomi got logcat
21:04.56Cotullait may die at any problem
21:05.03Cotullalike wrong resolution for camera and etc
21:05.04cockdomlib.cso
21:05.06cockdomlibc.so
21:05.15cockdomit loops
21:05.35Cotulla?
21:05.41cockdom1mn
21:06.27cockdomhttp://pastebin.com/zCdtLWvh
21:07.42CotullaE/HAL     (  908): load: module=/system/lib/hw/gralloc.qsd8k.so
21:07.42CotullaE/HAL     (  908): Cannot load library: reloc_library[1312]:   849 cannot locate 'android_atomic_cmpxchg'...
21:07.42CotullaE/FramebufferNativeWindow(  908): Couldn't get gralloc module
21:07.45Cotulla:P
21:08.13cockdomwhy does it fail?
21:08.26cockdomi have it there
21:08.49Cotullanot compatible
21:09.02cockdomnot compatible with gingerbread
21:09.09cockdomor is it due to wrong binary of omap?
21:09.20Cotullamaybe also because
21:09.33cockdomwhat :D
21:09.36cockdom"maybe also because" ?
21:09.42Cotullaboth cases possible
21:09.46Cotullabut better replace
21:09.49cockdomhmm
21:09.56Cotullasystem libs hw modules from 2.3 leo build
21:09.59cockdomthen i should replace from a vanilla build
21:10.04cockdoma 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.16Homefixubuntu running on my evo! a few issues though
21:36.37arrrghhhuhm
21:36.45arrrghhhthis isn't so much a room for native android devices.
21:36.56Homefixnautilus cannot write to anything, however dolphin does
21:37.07Homefix?
21:37.09arrrghhhare you running it with sudo?
21:37.13Homefixyes
21:37.16arrrghhhthis room is for porting Android to winmo phones.
21:37.21arrrghhhso like hd2
21:37.22arrrghhhtp2
21:37.22arrrghhhetc
21:37.39arrrghhhspecifically kernel discussion related to porting
21:37.53Homefixk
21:38.11arrrghhh#android would be a better room probably...
21:38.15arrrghhhnot sure if there's an evo room or not
21:38.27Homefixno were to go :(
21:38.38*** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912)
21:38.44arrrghhhHomefix, google?  lol
21:38.49Homefixits really a ubuntu thing but #ubuntu told me to come here
21:38.51Curious_go to -chat
21:39.08Curious_heheh
21:39.12arrrghhhHomefix, hrm.  no clue why they directed you here...
21:39.16L_millerarrrghhh -Do you just want my lastest NBH to flash? That will get you started....
21:39.25L_millerlol wrong channel... ;)
21:39.28arrrghhhL_miller, lol
21:39.31Homefixhttp://forum.xda-developers.com/showthread.php?t=932754 this is why
21:39.53Homefixthis is what im doing and thishttp://forum.xda-developers.com/showthread.php?p=10584098#post10584098
21:40.07arrrghhhHomefix, so post in that thread!??!
21:40.26Homefixno one home
21:40.43Homefix!!
21:40.47arrrghhh...
21:40.56arrrghhhyou post your question and then wait.  crazy concept, i know.
21:41.03arrrghhhbetter yet, search the thread
21:41.07Homefixto hostile or stuckup for me
21:41.07arrrghhhperhaps others have ran into the same issue.
21:41.09*** part/#htc-linux Homefix (~Homefix@184-198-207-123.pools.spcsdns.net)
21:41.14arrrghhhlol
21:43.22bzothat's what you get for responding arrrghhh
21:43.39arrrghhheh
21:43.44arrrghhhno skin off my nose.
21:44.22Cotullalie to me
21:44.42arrrghhhyou're pretty
21:44.54Cotulla?
21:44.56Curious_lol
21:45.03arrrghhhyou said lie to you
21:45.10jonprylol
21:45.20Cotullaokay
21:45.23Cotullabut I mean other
21:45.34Curious_you are man
21:45.53Cotullaanyway black celebration now ;)
21:46.11*** join/#htc-linux tre9 (d0360432@gateway/web/freenode/ip.208.54.4.50)
21:46.32Curious_did u achieve smth
21:47.01Cotullayeah
21:47.33Curious_what? did you invent chocolate icecream?
21:48.26Cotullahttp://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.57Curious_eeww
21:55.08Curious_watch this
21:55.09Curious_http://www.youtube.com/watch?v=lZqrG1bdGtg&oref=http%3A%2F%2Ftwitter.com%2F&has_verified=1
21:56.06Cotulla~seen cockdom
21:56.14aptcockdom <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.22arrrghhha vanilla cockdom?
21:56.39*** join/#htc-linux fish1209 (~fish1209@unaffiliated/fish0912)
21:56.41Cotullawhat is cockdom?
21:57.01arrrghhhdidn't we just go over that?
21:57.05crawlinga cock dominatrix aka Curious_
21:57.44Curious_his port of  brain via wine is bad
21:57.50Curious_that is why he doesn't remember
21:57.52Curious_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.49tre9on 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.42arrrghhhtre9, -chat
22:14.17L_millerarrrghhh - 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.30arrrghhhkk
22:20.46L_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.46L_millerOk. It's in the Nates thread.
22:21.58arrrghhhat 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.20L_millerlol yup!
22:23.55[acl]L_miller: ok i see .. but what part specifically? fucking git.. i prob didnt sync bak .. :-(
22:23.56L_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.18arrrghhhthat would help tards like me :D
22:24.37arrrghhhnate probably just needs to update his guide.
22:24.38L_millerok 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.58L_milleryup.
22:24.59arrrghhhindeed.  if it works, they shouldn't care.
22:25.36L_millerI 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.15L_millerIt was just the dir and using rhod500 instoad of rhod...
22:26.29L_millerbut you have that taken care of.. ;)
22:26.30[acl]ok i see ur zip
22:26.49L_milleryup. those are one script does all.
22:26.58L_millerJust updated from what Nate had.
22:27.10[acl]so nate is up and running right ?
22:27.19L_millerNot sure?
22:27.35L_millerThink he was still playing around with the busybox... :)
22:27.48arrrghhhheh
22:30.40[acl]well i want to eliminate that beotch
22:31.48L_milleryeah.. Do we need to save that much room?
22:32.12L_millerSeems 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.54L_millerOhh... How much larger do you think it will get?
22:33.03L_millerlol yuppers. ;0
22:33.07arrrghhhit's like 1.6mb now methinks
22:33.12arrrghhh(kernel that is)
22:34.03L_millercorrect.
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.45L_millergreat. Me too. :) No camera yet... :(
22:36.09arrrghhhheh
22:36.14arrrghhhdon't be that guy L_miller :P
22:37.11L_millerwalks away with his head down...
22:37.35arrrghhhlol
22:40.44L_millerhey is there a way to clear out my modules folder?
22:41.03toastcfh[acl], any luck?
22:41.15toastcfhwith fps fix ;x
22:41.34arrrghhhrm?  lol
22:42.35[acl]toastcfh: ahh havent tried that much bro.. soon
22:42.47L_millerI have a bunch of links for old modules.
22:43.11jonpry2.12MB on .35
22:43.26arrrghhh[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.43toastcfhahh
22:46.12L_millerI 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.38toastcfhim working on opensource hdmi on theEVO
22:46.48toastcfhwhat a shit fest
22:46.50arrrghhh[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.58L_milleryup. Keyboard light didn't turn onn.
22:47.17[acl]arrrghhh: thing is i never get these SODs
22:47.19toastcfh~seen phh
22:47.20aptphh 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.37toastcfhheh
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.09toastcfhapt lart phh for being gone so long
22:48.09aptoffers 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.23arrrghhh[acl], well only RHOD properly powers down the panel.. no?
22:48.31arrrghhhit's not really an SoD thing
22:48.34phhtoastcfh: ?
22:48.35arrrghhhit's just a 'failed wake'
22:48.39toastcfh;p
22:48.47[acl]arrrghhh: nope. Topaz does it too
22:48.49toastcfhlol was just poking
22:48.51arrrghhhwhere the panel backlight comes up, LED goes orange... but panel never comes up.
22:49.08arrrghhhah so the panel collapse code was ported to TOPA as well?
22:49.14arrrghhhneed to get that to the rest of the devices.
22:49.22arrrghhhRAPH/DIAM users could really use it.
22:50.00toastcfhphh; u seen any open source hdmi api? >_>
22:50.08phhtoastcfh: ?!
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.28toastcfhhdmi out
22:50.43*** join/#htc-linux tailormoon (bestirc@vpn-178-217-160-117.didan.com.ua)
22:50.44toastcfhi got a working driver
22:51.02toastcfhjust 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.04toastcfhfound some 7x30 stuff on CAF that implements overlay . it suxx though because our hw doesnt support overlay >_>
22:52.19toastcfhevo has a crap gpu
22:52.59arrrghhh[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.08arrrghhhoic
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.39arrrghhhcrap
22:53.45arrrghhhsomething i was supposed to do before i leave work...
22:53.51arrrghhhhuh
22:53.57arrrghhhwell as long as it works.
22:54.18arrrghhhrhod100/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.47arrrghhhlol
22:54.58arrrghhhwell we try to care.  none of those schmos want to help test tho.
22:55.15arrrghhhor 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.42L_miller[ac] - side note but I always get a warning about "mount_opt" not being found... Line 222 of init.
22:55.50jonpry[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.44arrrghhh[acl], oh pull the .35 commit and test the panel collapse?
22:56.54[acl]arrrghhh: yeah why not.lol
22:56.55L_millerOk.
22:56.57arrrghhhyou'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.35jonprywe 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.54jonpryhaven't looked at it
22:59.07jonpryit 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.35bzo[acl] you should like at jb's tree for reference on the regime stuff
22:59.43jonprywell, i think we microp ksc first :p
22:59.50bzoI 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.34bzook, 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.27bzoso 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.19bzowell, by original plan I mean future of clocks for .35
23:03.33bzoyeah, I think we want Alex's stuff integrated back in
23:03.48[acl]what was so different again ? remind me please?
23:03.48arrrghhhquittin time, cya guys on the flip side
23:04.27bzo[acl] difference between what?
23:05.02[acl]bzo: between whats there now and alexes ? besides the enable case statements
23:05.29bzomostly the restructuring of the clock tables, and moving that stuff to the case statements
23:05.56bzothe logic is different though, alex had more specific handling in each case statement
23:06.12bzobut as you know there may be a couple of bugs
23:06.29bzothe 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.09MN_hey cedesmith did you ever get rmnet working on lk
23:58.17cedesmithnope but probably doable now
23:59.01cedesmithas it seams MPU (Memory Protection Unit) is off when SPL loads cLK
23:59.22cedesmiththo 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)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.