IRC log for #htc-linux on 20110226

00:00.30[acl]MassStash: and it has later kernel too.. so thats whats diff
00:01.13[acl]MassStash: since arrg was able to boot.. did u test it ou?
00:02.33arrrghhhOo later kernel
00:02.40jonpryhttp://imagebin.org/139943
00:02.43jonpryWisTilt2, check it out
00:05.15WisTilt2jonpry: nice. so thats battery percentage as it drops?
00:05.41jonpryyeah thats your data set. red is simple voltage to charge%. blue is output of the model
00:06.06WisTilt2what did you use for the 100% value, 4200?
00:06.22jonpry4117
00:06.34MassStash[acl], yea tested and working - service
00:06.45jonpry4171
00:06.58WisTilt2so it extrapolated that num?
00:07.40[acl]MassStash: good to hear.. ur on 400 or 5?
00:07.42jonpryumm, no that is from standard open circuit li-ion curves
00:07.45MassStash400
00:08.19jonpryWisTilt2, key here is we can use open circuit voltage cause we can calculate what the battery voltage would be if it were hypothetically unloaded and relaxed
00:09.10jonpryit actually takes a while for the algorithm to train up to a bad start like we will always get
00:09.17WisTilt2so the fact we're tracking close to the model means this should be fairly accurate across the board
00:09.46jonprythere are problems
00:10.03jonpryits a machine learning thing, so the fact that it predicts well on the training data is not surprising
00:10.37jonpryi also do not understand why SOC starts taking a dive at 80%
00:11.19WisTilt2very curious to see the output with a heavier load on the same device
00:11.40jonpryyes, we can try with model derived from this data set to see how accurate it is
00:11.51jonpryor visa versa
00:12.47arrrghhhWisTilt2: don't mean to interrupt, but did the move of ramconsole mess up the SYSTEM_LAST_KMSG files...?
00:13.42WisTilt2arrrghhh, moving ramconsole isnt in that test kernel, only the one im messing with here
00:13.53jonprythe original authors used slightly different model based on SOC. i don't have a plan on how to derive that from the data
00:14.08WisTilt2are all those kmgs files empty?
00:14.10[acl]aite fellas .. need to get back to helping for this wedding.. laters
00:14.20arrrghhhWisTilt2: hrm.  well, all the SYSTEM_LAST_KMSG's I'm getting from everyone are empty...
00:14.23arrrghhhyea
00:15.12bzoarrrghhh: have you looked at them with a hex editor/viewer?
00:15.19WisTilt2hmm, i did have klog disabled in one of my many tests, maybe i didnt turn it back on when i built that one
00:15.30arrrghhhbzo: the SYSTEM_LAST_KMSG files...?
00:15.51bzoarrrghhh: nvm, thought you were talking about dumping ramconsole
00:15.54arrrghhhWisTilt2: huh.  sounds like it might do it :P
00:15.58arrrghhhbzo: sorry no ;)
00:16.45WisTilt2bzo: moving ramconsole to ebi1 is working nicely so far.  i cant get it to crash msm_fb at all now and waking every time without any vsync errors.
00:17.15Alex[sp3dev]WisTilt2: crashing msm_fb? huh?
00:17.43WisTilt2well, causing pan_display errors with vsync timeouts, thats crashing in my book:)
00:17.47bzoWisTilt2: weird stuff, guess we shouldn't be playing in qcsbl
00:18.17Alex[sp3dev]WisTilt2: let's agree that crashing is either a null pointer or data abort.. don't make me feel nervous ;)
00:18.47arrrghhhWisTilt2: orly now?
00:18.51WisTilt2why does gpu0 have to be in SMI?
00:19.00Alex[sp3dev]WisTilt2: speeeeed
00:19.24bzoAlex[sp3dev]: is 1mb the minimum size granularity for pmem?
00:19.35bzoWisTilt2: I think the qcom libs are hardcoded for it
00:19.51Alex[sp3dev]bzo: no idea. who told you that? iirc jb is using half meg somewhere
00:20.11bzoAlex[sp3dev]: just a dumb assumption on my part
00:20.23bzoguess it would be more logical to be a page size or something?
00:20.36Alex[sp3dev]i would think so
00:20.45jonprynot like mmu is involved
00:21.42bzoanyways, I guess it is no big deal to relocate ramconsole to ebi if we can use only 128k or so
00:22.04Alex[sp3dev]honestly, i do not like the vreg api. when we'll finish 35 and nand, i'll either convert it to voltage regulator framework or make it lookup vregs by numbers. android and wince names don't match at all
00:22.28bzoWisTilt2: what size did you make your ebi ramconsole?
00:22.41WisTilt2ok dumb question here, what is using the 1st meg of SMI? gpu0 starts from 1meg up
00:22.51WisTilt2bzo: left it at 128k
00:22.56Alex[sp3dev]WisTilt2: spl. told you already today
00:23.00bzoAlex[sp3dev]: yeah, the way we use non matching vreg names is dumb
00:23.02Alex[sp3dev]and it is mmued
00:23.05Alex[sp3dev]mpued
00:23.28WisTilt2:( too many things today to remember.  thanks alex
00:23.41Alex[sp3dev]no problem
00:24.00Cotullawtf
00:24.01Cotulla:D
00:24.09jonprylooks like SMI is probably edram
00:24.11CotullaI come back and u still discussing SMI
00:24.29arrrghhhlol
00:24.33Alex[sp3dev]a law of smi. whenever Cotulla comes, people are discussing SMI
00:25.36bzojonpry: either that, or on the same package
00:25.52jonpryeither way, edram slow :(
00:26.37bzoit seems more likely to be the latter, because there are versions with different amounts of smi
00:26.58Cotullait's DDR wtf
00:27.04bzoalso, do they do edram that large?
00:27.06Cotullawtf
00:27.56*** join/#htc-linux GNUtoo|laptop (~gnutoo@host157-58-dynamic.116-80-r.retail.telecomitalia.it)
00:28.12jonpryi dunno. qcom uses it though
00:28.33jonprythen there is qsd, they have vreg for edram?
00:32.44*** part/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
00:32.56*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
00:33.10*** join/#htc-linux LuHe (~LuHe@91-118-62-204.dynamic.adsl-line.inode.at)
00:36.10WisTilt2arrrghhh: are you in nand or can you try this kernel and see if it blows up your phone?
00:36.13*** join/#htc-linux MethoS-- (~clemens@134.102.106.250)
00:36.22*** join/#htc-linux mobidev_ (~i-sat@wmod.net)
00:37.25arrrghhhWisTilt2: bring it on
00:37.28arrrghhhi'm running your kernel
00:37.35arrrghhhno data in nand still, can't have that :P
00:38.12arrrghhhWisTilt2: i was actually just saying to the peoples the reason last_kmsg's were blank heh.
00:38.16WisTilt2booting right now.  want to see if kmsg log is back to normal first
00:39.00WisTilt2bootup time has been ranging 75-90secs every boot
00:39.25arrrghhhkk
00:39.28arrrghhhnice!
00:44.00GNUtoo|laptophi dcordes_
00:44.14Alex[sp3dev]GNUtoo!!!
00:44.38Alex[sp3dev]GNUtoo: hi, could you send me your attempts at bringing wl1251 on dream?
00:47.30WisTilt2arrrghhh: kernel with your name on it -> 6fe6504b5dcda4aeb1bc9aa52659c9ff
00:47.39arrrghhhkk
00:47.54WisTilt2i changed the ramconsole to 256k for kicks also
00:48.22WisTilt2might be a placebo effect but in ebi memory it seems snappier
00:48.30arrrghhhheh
00:49.34*** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk)
00:51.25*** join/#htc-linux FlawlesStyle (~LOL@unaffiliated/flawlesstyle)
00:55.31*** join/#htc-linux g3rm (~germo@89-77-81-175.dynamic.chello.pl)
00:56.23*** join/#htc-linux arrrghhh_ (~arrrghhh@c-71-237-40-111.hsd1.co.comcast.net)
00:57.00WisTilt2arrrghhh: go to the app menu, back to main screen, switch apps, tell me this isnt noticeably faster!
00:57.19*** join/#htc-linux cazh_ (~quassel@3007ds2-rd.0.fullrate.dk)
00:57.43WisTilt2lol, just hit the app menu then back button, wow
00:57.55arrrghhhheh
00:57.58arrrghhhcalm down there
00:58.04arrrghhhhaven't booted yet.
00:58.20WisTilt2this is way faster than my sons iphone he keeps bragging on being faster screen
00:58.21*** join/#htc-linux Nautis (4cda4629@gateway/web/freenode/ip.76.218.70.41)
00:58.27arrrghhhlmao
00:58.31arrrghhhthat's what i'm talkin about
00:58.37arrrghhhtrash talkin iOS
00:59.33rpierce99no no WisTilt2 you're doing it all wrong, it goes like this: APPS: BLAZING FAST, MARKET: SUPER FAST, 3G: SPIZEEEDY, ITS BEST BUILD EVER
00:59.58arrrghhhlol
01:00.04WisTilt2lol, got a ways to go but getting there
01:00.08arrrghhhi don't think he's had the privelege of reading any of those threads.
01:00.43arrrghhhthis boot is soooo much less verbose.
01:00.49arrrghhhi almost miss the flying text, odd :P
01:00.58arrrghhhit likes to sit at the prompt too
01:01.00arrrghhhteasing me
01:01.01WisTilt2yeah everything fits on the screen so you can read it
01:01.09arrrghhhi know it's wacky :P
01:01.57*** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk)
01:03.15WisTilt2bzo: just an fyi if you want to mess with it... i moved ramconsole to the base of EBI and allocated 256k.  definitely quicker and so far no errors, but arrrghhh will come up with some im sure:)
01:03.36arrrghhhhrm
01:03.40*** join/#htc-linux arif-ali (~arif-ali@88-111-128-250.dynamic.dsl.as9105.com)
01:03.47arrrghhhit's... worse for me so far.  just had a competely failed wake...
01:03.59arrrghhhmaybe it was the startup jitters...
01:04.07WisTilt2did you let it fully bootup and settle down?
01:04.25bzoWisTilt2: ok, let's see how it goes with your next test kernel
01:04.30WisTilt2it does weird things until data stuff gets situated ive found
01:05.06arrrghhhindeed
01:05.39WisTilt2mines been up 22mins and my fingers are getting tired of pushing on/off, no failed wakes or errors yet
01:05.49*** join/#htc-linux Dinde (kayser@sur-internet.net)
01:06.11arrrghhhlol
01:07.20*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
01:07.23WisTilt2arrrghhh: if you get a failed wake like that where backlight comes on only, hit power and wait for it to fully sleep then it will come back up.  if you can look at dmesg right after that, see if there are any pan_display errors during the wake sequence
01:07.35*** part/#htc-linux Cotulla (~opera@nat004-252-205-109.tvoe.tv)
01:07.57WisTilt2most likely it will be the msm_fb dma timeout
01:09.36WisTilt2arrrghhh im out of here, need to go by the bank then home so ill be back on in an hour or so for your list of bugs:)
01:28.49*** join/#htc-linux surge (surge@pool-98-118-157-221.bflony.fios.verizon.net)
01:28.59jonpryis feeding the kernels battery from userland actually a bad idea?
01:29.26jonpry*kernels battery driver
01:36.02*** join/#htc-linux ftoz (~root@cst-prg-164-28.vodafone.cz)
01:59.00*** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net)
02:06.19jonpryhi WisTilt2
02:06.22*** join/#htc-linux mastermerlin (~Adium@p4FEE5DE0.dip.t-dialin.net)
02:06.52arrrghhhWisTilt2: so far so good
02:07.02WisTilt2yo.  friday night, drinks in hand, life is good
02:07.07fakkersnifffs
02:07.11fakkersniffs WisTilt2
02:07.12jonpryi'm stoked about this battery thing, i think it is finally working :p.
02:07.17WisTilt2fakker lol
02:07.17fakkersniffs jonpry
02:07.25fakker:D
02:07.30jonpryfor the last time
02:07.33fakkeri need some 2am entertainment
02:07.35fakkerjonpry, you wish
02:07.41fakkeri just started
02:08.30WisTilt2jonpry: i took one of our phones from the office and set it up with the heavy load test.  4hrs run should be done in about 2.5hrs and ill email it to you.  i really want to see how much different that reports
02:08.30jonpryWisTilt2, what do you think feeding the userland results back into the kernel, so they can be presented on /sys/class/...
02:08.34arrrghhhWisTilt2: i did get one [  212.721618] msmfb_pan_display timeout rerequest vsync
02:08.42WisTilt2arrrghhh: fast screen now huh?
02:08.46arrrghhh200s in tho, that was probably the failed wake at the beginning
02:08.57arrrghhhbut yea haven't had a failed wake since
02:09.01arrrghhhmade a bunch of phone calls
02:09.06arrrghhhhope i don't go over my work phone's minutes lol
02:09.15WisTilt2jonpry: sounds good.  what all would need to be passed back?
02:10.00WisTilt2arrrghhh: did it do the partial panel wake thing at that time and came back up after full sleep again?
02:10.21arrrghhhyup
02:10.26arrrghhhand it was just that once, early in the boot
02:10.38WisTilt2yeah things were still getting situated i think
02:10.53arrrghhhswiping desktops is incredible
02:10.54jonpryWisTilt2, i think just capacity, and maybe voltage
02:11.01arrrghhhthat used to be kinda painful until you did it a few times
02:11.19WisTilt2arrrghhh, instant isnt it?
02:11.30arrrghhhyup
02:11.33WisTilt2switching menu back to desktop is crazy
02:11.54arrrghhhit really is starting to feel like a native android phone
02:12.01WisTilt2jonpry: so userland would just pass that and kernel just stores it back in the class?
02:12.02arrrghhhthis 30s sleep thing is frustrating.
02:13.07WisTilt230s continuously?
02:13.16arrrghhhnot at first
02:13.29arrrghhhbut i seem to have gotten stuck in it after a little while
02:13.33arrrghhhi called it a whole bunch
02:13.38WisTilt2its never going back to the 5ss now once it started?
02:13.41arrrghhhput it in deep sleep and called it again and again :D
02:13.46arrrghhhnope, not yet at least.
02:13.53jonpryWisTilt2, i think what happens is batteryd will block on read for more data, and battery driver will open up the flow whenever phone is awake. then when algorithm gets a hunk, it will immediately write a new result back to the driver, which just caches it for the /sys/class/attribute reads
02:14.04XirXescan i get in on this fun? it sounds awesome
02:15.32WisTilt2jonpry: sounds good.  you do the userland side and tell me what you need on the kernel side and ill set it up, unless you want to code the whole thing
02:15.50jonprynot really :p
02:16.03WisTilt2XirXes, going to have arrrghhh put it up for testing as soon as I fix the manual backlight problem.
02:16.13jonpryhow are you reading the ring buffer out now?
02:16.17XirXessounds good
02:16.27jonpryyou have an app for that?
02:17.16arrrghhhlol
02:17.33WisTilt2jonpry: im doing it all inside the kernel right now. need to setup zalloc instead of this char buffer really.
02:18.49WisTilt2we need to layout how things need to happen in the kernel.  do we wake it up at some interval, store in ring buffer and wait.  i guess you're going to need the kernel to make the whole ring buffer available to userland or what?
02:19.11arrrghhhWisTilt2: this thing is a beast.  have a fix for those who use manual bl?
02:19.27arrrghhhis it in this one, should i test that?  i'm guessing no.
02:19.50WisTilt2yeah going to fix that right now then you can put up the new kernel pack for mass testing with this new stuff
02:20.20jonprywell i figure when phone is sleep or almost sleeping, we don't need userland to do anything, so theres no reason to give it data, hence need for buffer. but i'm not sure how to differentiate "woke up for level reading" and "woke up for code/phone/whatev"
02:21.29jonprybut events could be transferred to userland one at a time as far as i'm concerned
02:21.31WisTilt2i can make it only pull data on its planned read interval so if something else wakes it up it wont skew the timing
02:21.34jonprymaybe blocking ioctl
02:21.51jonprythat would be good
02:22.46WisTilt2but when you request the data from userland, will the whole ring buffer be sent or do i need to keep a pointer to the next value to send?
02:23.33jonpryit depends
02:23.46jonpryioctl are fixed size, so if we do it that way, it one at a time
02:24.15jonprychar stream could in theory pipe lots of stuff, but it is trickier, cause you have to worry about incomplete reads
02:24.49WisTilt2ioctl would be cleaner and exact
02:25.28XirXesdoes anyone know the name of the prox/ light sensor in the rhod?
02:25.50arrrghhhO.o WisTilt2 just had a failed wake, simply hitting the power button.
02:26.03arrrghhhi will pull dmesg as soon as it sleeps again and i can wake it back up.
02:26.03jonpryWisTilt2, that sounds good to me, so then you definitely need read ptr
02:26.10WisTilt2nice. let it sleep then wake it and check dmesg for that error
02:26.54WisTilt2brb, wife has groceries again:(
02:31.06arrrghhhWisTilt2: odd.  i didn't get another pan_display error at all.
02:31.08arrrghhhWisTilt2: http://pastebin.com/XRMEAk7Q
02:32.34rpierce99arrrghhh: there is this though: msmfb_start_dma 35110.000 ms after vsync request
02:33.16arrrghhhOo
02:33.19arrrghhhgood catch
02:33.33rpierce99don't know what it means but 35s doesn't sound good
02:33.40arrrghhhlol no
02:33.51arrrghhhthat's right around the issue took i believe
02:43.13*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
02:44.21*** join/#htc-linux crawling (crawling@a94-132-169-99.cpe.netcabo.pt)
02:46.27arrrghhhwth just had another one
02:46.28arrrghhhhttp://pastebin.com/5VSWdZcc
02:52.04*** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com)
03:00.11WisTilt2arrrghhh: ok back from unloading and eating something.  so looks like theres still a problem with vsync. thats where the non wakes seem to always occurs
03:01.17arrrghhhWisTilt2: what about that last one?
03:01.31arrrghhhi didn't see any of those errors, but i don't really know what i'm looking for.
03:01.48WisTilt2dont see anything at all in that one.  did it come back after going into sleep again?
03:02.41arrrghhhyup
03:02.51arrrghhhand as soon as it did, unlock plug in adb pull dmsg...
03:03.13WisTilt2are the kmsg logs still empty btw
03:03.28arrrghhhi think i need to reboot to see those, right?
03:03.32WisTilt2yep
03:03.34arrrghhhkk
03:03.46arrrghhhsee anything about the 30s sleep?'
03:11.13WisTilt2yeah looks like a wakelock on evdev holding it.  need to see why that would have changed to that long
03:11.47arrrghhhk
03:11.57WisTilt2i added output to show when arm11 sleeps/wakes exactly so its easier to have starting points
03:13.17arrrghhhcool
03:17.48WisTilt2arrrghhh: which rhods dont have proximity sensor?
03:18.43XirXesall have them
03:19.16XirXesthe light and prox sensors are the same chip afaik
03:19.42WisTilt2interesting.
03:19.43arrrghhhi don't know about what chip they're on
03:19.55arrrghhhbut AFAIK all RHOD's have prox sensor.
03:20.30phhyes
03:20.33phhand it's an isl something chip
03:21.59WisTilt2phh: proximity not working obviously but was the code that maps it to an input always in the code or added a few months ago?
03:22.25phhfew months ago
03:22.31phhiirc the code was totally wrong
03:23.03WisTilt2hmm, this wake lock hanging things might be that input
03:23.10phh"oops"
03:23.50*** join/#htc-linux CIA-62 (~CIA@208.69.182.149)
03:24.22WisTilt2code is wrong, i have the proximity stuff already but havent implemented it yet.  but this wake lock points to that input being the possible cause
03:24.36arrrghhhheh
03:25.00phhjust drop that code
03:25.23WisTilt2going to do that now and see
03:26.33*** join/#htc-linux netson-ubuntu (~netson-ub@125.161.198.91)
03:26.47*** join/#htc-linux crawling (crawling@a94-132-169-99.cpe.netcabo.pt)
03:29.27XirXesi just found the ir blaster in the tp2. its right above the htc logo on the front. inpossible to see without it being on and with a camera
03:29.28jonpryWisTilt2, i defined some ioctl's and structures for our project. this file would go in linux/include
03:29.29jonpryhttp://gitorious.org/scbs/scbs/blobs/master/scbs.h
03:30.12jonpryvery complicated :p
03:36.31*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
03:38.21AstainHellbringhow goes it
03:38.29AstainHellbring~seen cr2
03:38.33aptcr2 <n=cr2@ip-109-84-74-80.web.vodafone.de> was last seen on IRC in channel #htc-linux, 399d 7h 17m 40s ago, saying: 'MrPippy: where is this source ?'.
03:38.38arrrghhh399d
03:38.39AstainHellbringdamn
03:38.42AstainHellbringlong time ago
03:38.45arrrghhh~seen cr2_
03:38.46aptcr2_ <~cr2@ip-80-226-0-1.vodafone-net.de> was last seen on IRC in channel #htc-linux, 37d 5h 55m 23s ago, saying: 'kiozen: i can run userspace x11/gtk apps, but it is not possible to access the hardware. so it's more or less useless'.
03:38.48phh.
03:38.50arrrghhhlol
03:38.51arrrghhhsorry
03:38.54arrrghhhapt was smart
03:39.00phhyeah
03:39.03AstainHellbringvery
03:39.14AstainHellbringphh know if anything has happened on athena dev?
03:39.28phhathena ? :D
03:39.42AstainHellbringyah aka htc advantage aka x7500
03:39.53phhdoesn't really help :p
03:39.57AstainHellbringlol
03:40.06phhi'm not *that* old
03:40.06AstainHellbringguess thats a no from you
03:40.11AstainHellbringcr2 was doing some stuff on it
03:40.15AstainHellbringathenas not that old
03:40.23AstainHellbringwell I guess in phone terms it is
03:40.36phhhow much ? 5 years ?
03:40.44AstainHellbringsomething like that
03:40.53AstainHellbringran intel xscale proc
03:41.02phhwo
03:41.02phhw
03:41.13AstainHellbringwas a sweet device
03:41.22AstainHellbring5" screen detachable magnetic keyboard
03:41.31phhoO
03:41.59arrrghhhwth?
03:42.06AstainHellbringhttp://pdadb.net/index.php?m=specs&id=691&c=t-mobile_mda_ameo_htc_athena_100
03:42.10AstainHellbringthats a version of it
03:42.41phhmotorola atrix is late ! :D
03:42.57AstainHellbringphh you ordered one?
03:43.06phha what ?
03:43.08phheither way it's no
03:43.12AstainHellbringatrix
03:43.15AstainHellbringyou said its late
03:43.26phhi mean their idea
03:43.31phhcompared to htc athena
03:43.36AstainHellbringahh gotcha
03:43.54WisTilt2arrrghhh: try this one and see if you can get it to do it. 8c5ef1d2ae42da275d8911fa9ee55db5
03:44.03arrrghhhkk
03:44.16dcordes_hi
03:45.35WisTilt2jonpry: dont know if i can handle that, very complicated stuff:)
03:46.42WisTilt2what time value you need?
03:51.00dcordes_Login error
03:51.01dcordes_Htc-linux uses cookies to log in users. You have cookies disabled. Please enable them and try again.
03:51.08dcordes_NetRipper: ping
03:53.18arrrghhhWisTilt2: failed wake.  pulling logs...
03:53.59arrrghhhhttp://pastebin.com/SgcbyUwQ
03:54.01arrrghhh^^
03:54.49jonpryWisTilt2, i'm guessing milliseconds
03:55.08dcordes_somebody knows where the photon kernel is ?
03:55.09jonprylike somebody could set 5000 sleep, 1000 awake for the updates
03:56.35arrrghhhbrb
03:56.39jonpryand then samples would need to be labeled. its not important if sleep==awake
03:57.04jonpryi think voltage,current,capacity, 16.16 fixed point
03:57.14*** join/#htc-linux bzo (~chatzilla@c-76-126-175-200.hsd1.ca.comcast.net)
03:59.40jonpryi wish android had STL
04:00.20AstainHellbringSTL?
04:00.40jonprystandard template library
04:03.06*** join/#htc-linux kubi (~Adium@miranda/user/kubi)
04:04.33WisTilt2jonpry: in going to be adding the logging timestamp correction to show actual time since boot instead of timestamps freezing in suspend, then continuing from that point.  that way logs will be actual uptime logging and the battery readings can match time since boot.
04:05.35jonprythat sounds like an important step
04:05.59WisTilt2yeah, been bugging me how timestamps in logs are real with actual uptime
04:06.10WisTilt2arent real i mean
04:06.27jonpryespecially since you've got 99% sleep
04:07.01WisTilt2arm has a register that tracks that so sleep time can be correct to actual runtime
04:07.30jonprywould it be cool if sleep/collapse was some kind of dynamic thing
04:08.30jonpryi guess thats not really how phones are used
04:15.12*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
04:16.13jonprysomehow or another the integral of those 1 second current measurements is not fubar
04:16.35jonprywe will see about 5
04:18.09WisTilt2we need to do 5s intervals instead of 1s on these tests we're doing now or you mean later?
04:18.23jonprylater i think
04:18.32jonprywe need all kinds of data
04:19.11WisTilt2this 4hr test under load looks like it will be done in about 15mins or so.  they are at 1s intervals like before
04:19.36WisTilt2man that phone is much warmer than the previous test
04:19.47jonprycool. i don't think 5 seconds will work off the bat and we will end up needing the adaptive time thing
04:19.54jonpryare you taking it to zero?
04:20.45jonpryadaptive learning rate with adaptive time will be way cool too
04:20.46*** join/#htc-linux Rob2223 (~Miranda@p4FFF3EE7.dip.t-dialin.net)
04:20.50WisTilt2? just running 14400 polls 1sec apart
04:21.32jonpryoh i though you were watching the meter or something and taking the log when it gets too low
04:21.40*** join/#htc-linux arrrghhhTP2 (~arrrghhh_@107.29.229.114)
04:22.45WisTilt2ah, no i have it in the console outputting each 1sec reading.  when it finishes the last one it saves the data to the sd card with the filename i sent you
04:23.48WisTilt2damn, arrrghhh you must try this next kernel my friend:)  found the sucker holding up the show and now we have true full sleep in about 1second.
04:24.05jonpryi wonder if there is a way to identify individual batteries. in case people change it
04:25.03arrrghhhTP2WisTilt2: Oo?
04:25.16WisTilt2arrrghhh -->> 096154f32b61f2e654884459123925a8 awsome:)
04:25.21arrrghhhTP2Heh
04:25.25arrrghhhTP2Kk
04:25.42WisTilt2jonpry: cant we read and match the battery id to a manufacture table of some sort?
04:26.13jonpryyeah there is a resistor in each battery
04:26.17jonprythat is read via adc
04:26.38jonpryand if its in some range you can tell like what capacity it is
04:26.47jonpryor was made to be
04:27.24WisTilt2ah i see what you mean.  yes that would be nice so we could reset on a battery with different characteristics
04:27.28jonpryi dunno if that number has a lot of entropy or something that could be exploited
04:27.39jonpryyeah like that
04:29.06arrrghhhTP2Hrm I don't have dns in console
04:29.06arrrghhhTP2Odd
04:29.49jonprybut internet works?
04:30.23jonpryjust echo 8.8.8.8 > /etc/resolv.conf
04:30.39arrrghhhTP2Heh
04:30.53phhecho nameserver 8.8.8.8 > /etc/resolv.conf
04:31.02jonpryor listen to him
04:31.12phhwait, he is not on android ?
04:31.18jonpryhe is
04:31.22jonpryand your right
04:31.22phhon android it's more like setprop net.dns1 8.8.8.8
04:31.34jonpryhrm
04:31.41phhyeah you love that i know
04:31.48jonpryno resolv.conf for busybox stuff?
04:31.57phhmmmmmmmmmm
04:32.07phhi'd say busybox uses bionic
04:32.10phhwhich uses properties
04:32.22phhbut perhaps busybox is statically built
04:32.37phhok, time to sleep.
04:32.44jonpryso one of the two?
04:33.10arrrghhhTP2Lol
04:33.49WisTilt2phh: you know that unbalanced irq 154 (or whatever it was), it was the proximity device.  no longer erroring
04:33.55jonprycome on arrrghhhTP2 fix your internet
04:34.44arrrghhhTP2:(
04:34.56arrrghhhTP2is confused
04:35.11arrrghhhTP2Internet working, not in terminal.
04:35.43jonpryarrrghhhTP2, did you do the echos?
04:35.59arrrghhhTP2Not the setprop
04:36.38jonpryyou did phh's nameserver one?
04:36.59arrrghhhTP2Yea didn't work
04:37.10jonprydo setprop
04:37.10arrrghhhTP2Unless I need to cycle something?
04:37.13arrrghhhTP2Kk
04:37.33jonprywhen will android get bash?
04:37.56WisTilt2thats not right, dont think resolv.conf is in /etc like regular linux
04:38.12jonpryphh says bionic doesn't use it
04:38.38arrrghhhTP2Just keeps telling me "ping: bad address"
04:38.52jonpryprobably ipv6
04:39.15arrrghhhTP2Heh
04:39.20arrrghhhTP2Modprobe ipv6?
04:40.14jonprytry ping 2001:4860:c004::68
04:40.48arrrghhhTP2I can ping 8.8.8.8
04:41.09jonprycan you go to that address in android?
04:41.45arrrghhhTP2I just wanted to wget in the terminal
04:42.48jonprywget with the ip :p
04:43.09arrrghhhTP2Heh
04:43.16arrrghhhTP2Damnit..
04:47.41arrrghhhTP2Victory
04:47.52arrrghhhTP2Had to use a pc to find ip tho, sad lol
04:48.40arrrghhhTP2Alright reboot time.
04:51.56jonpryWisTilt2, is it done?
04:52.25WisTilt2yep, about to pull it off onto the laptop and email it
04:54.04jonprycool
04:56.37WisTilt2jonpry: in your mailbox
04:59.39*** join/#htc-linux arrrghhhTP2 (~arrrghhh_@107.29.229.114)
04:59.58arrrghhhTP2Wis
05:00.11arrrghhhTP2Damnit keep hitting the wrong key
05:00.31WisTilt2hurry up, im one kernel ahead of you:)
05:00.36arrrghhhTP2WisTilt2: sleeps fast!  Had a failed wake already, getting dmesg now
05:00.38arrrghhhTP2Lolut
05:00.45arrrghhhTP2lolwut
05:01.18WisTilt2yeah need to see log on the fails now.  like that quick sleep and it really is shutting down that quick now
05:01.22jonpryhrm, that is seriously not linear towards the end
05:02.40jonpryhttp://imagebin.org/139972
05:05.24WisTilt2looks like when it got in the 3530 range it hung in that same area.  do these batts do that when they're nearly discharged?  dont know what the voltage is that is considered discharged on them
05:06.03WisTilt2i never see my normal phone below 3700 or so then i charge it so 3500 sounds like its almost dead
05:06.38jonpryit should go lower
05:06.54jonpryand capacity should drop off faster, unless it is throttling the phone somehow
05:07.13arrrghhhTP2WisTilt2:
05:07.25arrrghhhTP2Crap
05:07.47WisTilt2what happened?
05:07.54arrrghhhTP2http://db.tt/P5KF51V
05:08.00arrrghhhTP2^^
05:08.07arrrghhhTP2I suck at using my phone :P
05:08.39WisTilt2what am i looking for?
05:08.52arrrghhhTP2Failed wake
05:09.02arrrghhhTP2I didn't pull it with adb
05:09.09arrrghhhTP2Same cycle tho
05:09.11jonprythe model generated from new data set is close, but not the same. and yields this http://imagebin.org/139975
05:09.26arrrghhhTP2Failed wake, then successful wake & logs pulled
05:09.28WisTilt2seems like you get them shortly after booting mainly?
05:09.30*** join/#htc-linux opdf2 (~asdfsd@c-67-173-70-13.hsd1.il.comcast.net)
05:10.00arrrghhhTP2WisTilt2: I swear the phone had settled down...
05:10.41arrrghhhTP2Maybe not
05:10.43WisTilt2but sleeps are fast now and wakes nearly everytime after that one?
05:10.49arrrghhhTP2I can sign off and test more
05:10.51arrrghhhTP2Yup
05:11.00arrrghhhTP2Didn't test too extensively
05:11.08WisTilt2ok hit it numerous times
05:11.24arrrghhhTP2Let me continue to test, unless you have some more madness?
05:11.45WisTilt2i have one more change for you but go ahead and hit that one for a few first
05:11.59arrrghhhTP2Heh ok
05:12.11jonpryWisTilt2, http://imagebin.org/139976 seconds model on first dataset
05:12.12WisTilt2jonpry: is that blue line the model still?  looks pretty close but not as close as without the heavier load
05:12.25jonpryblue is model
05:12.52jonpryi don't know that we are looking for close
05:12.56WisTilt2i think its closer to the model on the second one
05:12.59jonprylooking for correct
05:13.15jonpryso for instance we know that correct is monotonic
05:13.29jonprywhere as the red line is not even close
05:14.07jonpryand it should also be linear?
05:14.14arrrghhhTP2Not sure if it's this app or what but it's taking 5-6s to sleep
05:14.46jonpryi think the model from your second data set it *way* better
05:15.02WisTilt2sleep should always be around 1s now unless a background task is keeping it up
05:15.40WisTilt2jonpry: yes i think if we were all over the map compared to the model we'd have a problem.  i think this, with some fine tuning, should work pretty well
05:15.56jonpryWisTilt2, was it fully charged when you started?
05:16.15WisTilt2on that second test it was showing 96% in winmo
05:16.31WisTilt2i think the previous was 89%
05:18.03arrrghhhTP2Let me quit then.
05:18.28jonpryWisTilt2, do you know if charge current is registering correctly?
05:18.51jonprylike it should go down with system load and such
05:18.52*** join/#htc-linux Kasjopaja23 (~Tina@p579C1226.dip.t-dialin.net)
05:19.44WisTilt2havent looked at what it reads with charger plugged in. is that what you mean?  i can run it with charger and see what kind of current values it shows
05:21.17jonpryyeah with charger
05:22.54*** join/#htc-linux arrrghhhTP2 (~arrrghhh_@107.29.229.114)
05:23.21jonprytrouble with numerical code is the fine tuning
05:23.35arrrghhhTP2WisTilt2: http://db.tt/hPBUuGGh
05:23.53WisTilt2interesting.  panel on im seeing the similar current values as the last data but when i plug in charger after about 5secs current goes to zero and never changes.  unplug charger and few secs later it shows values again
05:24.07jonpryyeah its in two different locations
05:24.20jonprypositive one place, negative another :p
05:24.22WisTilt2oh
05:24.30*** join/#htc-linux GhostMan (~Duper@46-116-51-174.bb.netvision.net.il)
05:24.30WisTilt2arrrghhh: invalid paste
05:24.50WisTilt2ill have to find that other location then
05:25.36arrrghhhTP2Crap
05:26.31arrrghhhTP2http://db.tt/hPBUuGG
05:26.42arrrghhhTP2I guess I hit h lol sorry
05:26.44*** join/#htc-linux ImCoKeMaN (~imcokeman@pool-96-249-148-95.hrbgpa.fios.verizon.net)
05:26.51*** join/#htc-linux kvaster (~kvaster@93.84.112.82)
05:27.01arrrghhhTP2Anyhoo, closed the app and sleep was fast again - awesome
05:27.10WisTilt2try this kernel while i look over that one fecc2ed534bd251769f9be95fe683b9a
05:27.17arrrghhhTP2But one complete failed wake, then a realllly slow wake
05:27.27arrrghhhTP2And pulled logs
05:27.38arrrghhhTP2Crap, I must go to bed dude...
05:27.55WisTilt2ok np.  its up there when you get a chance
05:28.01arrrghhhTP2goin on vaca for the next week
05:28.08arrrghhhTP2Gf is not happy lol
05:28.19arrrghhhTP2I'll check it out tomorrow, thx dude.
05:28.21WisTilt2damn, going to be weird without the super tester in here
05:28.30jonpryWisTilt2, you have htc_battery_smem.c?
05:28.34arrrghhhTP2I'll still be around methinks.
05:28.50WisTilt2k, image is on the server when you can
05:28.51arrrghhhTP2Just goin on a snowboard trip, so days will be busy :D
05:28.55arrrghhhTP2Thx dude
05:28.59arrrghhhTP2Peace guys
05:29.00WisTilt2ill be around tomorrow until noon or so
05:29.07WisTilt2jonpry: yes
05:29.20jonpryso in htc_get_batt_smem_info()
05:29.31jonpryit extracts the data from the smem region
05:29.44jonpryi dunno what our smem_field_size is
05:30.25WisTilt2ours is 4
05:30.40jonprybut topaz is 2?
05:30.51jonprysame amss
05:30.57WisTilt2yep and diamond also
05:31.22WisTilt2wait, battery smem size you mean...
05:31.23jonpryso batt_32->batt_discharge is other one
05:31.37WisTilt2on rhod its 4
05:31.40jonprysmem_field_size
05:33.14WisTilt2so batt_discharge is what we read during charge?
05:33.15jonpryi dunno what your setup looks like, but discharge is just the u32 after charge
05:33.24jonpryyeah i think they are backwards
05:33.28WisTilt2figures
05:34.48jonpryand if your using code from htc_battery, it fails to copy that value from smem to its little voodoo buffer
05:35.06rpierce99WisTilt2: I know you and arrrghhh have a good thing going, and I don't even want to do all the crap he does, but if you just need to bounce a kernel off a rhod400 feel free to hit me up
05:35.46WisTilt2thanks rpierce99, you've tested a few of them yourself:)
05:36.20rpierce99i've tested all of them, just filtered my feedback through arrrghhh until recently :)
05:36.30WisTilt2you have the url to get the test image still?
05:37.03rpierce99never have, always got the public build
05:42.34jonpryhttp://imagebin.org/139984
05:42.47jonpryWisTilt2, graph of calculated and measured voltage
05:43.22jonpryits almost totally linear. i guess the distortions in the other graphs were from my linearizer
05:43.36WisTilt2i like
05:44.42jonpryi do not understand :p
05:45.18jonpry0% is 3.186 volts :p
05:47.34WisTilt2that cant be right? isnt that way too low.  maybe i just dont let mine get discharged that much, always charge when its no lower than 40% or so and voltage is still in the 3500 range i thought
05:48.46jonprywell its apparently not. the curves i got from ds2746 are just distorters
05:51.05jonpryit looks like bulk capacitance is constantish until 3.7V
05:51.26jonpryand its all over but the shouting at 3.4
05:52.45WisTilt2are there any specs for these batts that show soc voltages?
05:52.59jonpryno
05:53.06jonpryits a figure it out game
05:53.09*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
05:53.54jonpryWisTilt2, i'm pretty sure we could analyze it out of a battery, but people would have to run it down. just fully charge, and let it die
05:54.20*** join/#htc-linux BoominSVX (421f78ad@gateway/web/freenode/ip.66.31.120.173)
05:54.28jonprybut it might be constant for whatever chemistry is in them
05:54.55BoominSVXMaybe thats why I have to let my phone charge for 10 minutes if the batt dies before it'll turn on.
05:55.02jonpryand we could also ask cotulla to download curves from hd2's ds2746
05:55.32jonpryBoominSVX thats because the phone draws more current than the charger can supply
05:55.32WisTilt2i can do that and pull data until it dies.  just need to output to sd card as i go so i dont lose the data
05:56.12jonpryi don't think its worth it for now. its like another layer of regressions
05:56.44jonprywe need to get something confirmed correct before we can start using the data for more stuff
05:56.46BoominSVXjonpry: when it dies in winmo, i can plug it in and turn it right on. Just seemed to me that android discharged it lower.
05:56.57jonpryoh it does
05:57.02WisTilt2jonpry: that brings up a question... why are the current numbers only in the less than 100 range under load.  certainly these devices draw more than 100ma with everything on dont they?
05:57.38jonpryi would think so
05:57.52jonprybut you just have panel on, not processor maxed out
05:58.00WisTilt2yeah true
05:58.08jonpryi mean panel is 20ma @ 27V?
05:58.30WisTilt2so the current values we're seeing are probably about right you think?
05:58.49jonpryis backlight on max?
05:58.54WisTilt2yes
05:59.01jonprymight be low
05:59.14WisTilt2thats why this last test got the phone so warm after 4hrs
05:59.41jonpryand 4 hours @ 80ma, only 320mah
05:59.47jonprybut battery almost dead
05:59.53BoominSVXjonpry: BTW, I have a confession. The carribean does not eat TP2's
06:00.04WisTilt2lol
06:00.16jonprywhat about wozzer's?
06:00.16BoominSVXMy computer chair does.
06:00.22BoominSVXNo idea
06:00.30jonpryhmm
06:00.40jonpryyou didn't send it?
06:01.07BoominSVXNo. I killed it.
06:01.19jonpryi thought the 18 wheeler did that
06:01.27BoominSVXThat was the other one
06:01.36BoominSVXYou were getting the horse trailer one
06:01.50jonpry?
06:02.10BoominSVXI crushed it in the door of a horse trailer. :)
06:02.57jonpryso you lost 2 tp2's to mass destruction?
06:03.16BoominSVXThere was nothing left of the Industrial Park Demolition Challange 2010
06:03.44jonprymy god
06:03.48BoominSVX3 actually, and I'm on boost so no service plans or insurance
06:04.19jonprythats horrible
06:04.56WisTilt2rpierce99: did that kernel blow up your phone?
06:05.04jonpryWisTilt2, it does not actually matter if the current is off by some factor. just model capacitance comes out different by same factor etc.
06:05.05BoominSVXanyway, sorry buddy. I feel like a d!ck, but it's been eating me up. I feel better now having confessed.
06:05.22jonpryyeah its ok
06:05.28jonprywe fixed the sound anyways
06:05.37rpierce99WisTilt2: haha, being that this is the first that I've downloaded from you, when it didn't boot I assumed it was me doing something stupid
06:05.44BoominSVX:) I know!
06:06.15WisTilt2forgot to tell you about the bootup, makes it look like phone locked up
06:06.24jonpryWisTilt2, thing is we need same units on charge and discharge, although we may be able to infer the relationship
06:06.36rpierce99WisTilt2: no it's not that, I'm on one of those now, haret hangs
06:06.37WisTilt2should get to the unlock screen in about 90secs or so though
06:06.51rpierce99so i'm pretty sure I"m doing something dumb
06:07.10BoominSVXWisTilt2: kernel-pack.zip? I've got about 15 mins before I have to leave, but I can check it out tonight.
06:07.16WisTilt2jonpry: got zero out of that location with and without charger
06:07.26jonpryf$%^&*
06:07.45WisTilt2BoominSVX you have the url right?
06:07.57BoominSVXjust need to know whats it's called
06:08.26WisTilt2wistilt2-kernel-pack.zip
06:09.00WisTilt2rpierce99: do you get the vibrate from haret or does it not get that far?
06:09.07rpierce99nope
06:09.54BoominSVXWisTilt2: got it
06:10.00WisTilt2thats not the kernel its something else then.  it works with the posted stuff ok though?
06:10.37jonpryWisTilt2, what do we do then?
06:10.39WisTilt2rpierce99 get the kernel pack and try it
06:10.52jonpryPMIC can measure this. why don't we have it?
06:11.15rpierce99I think the transfer off my VM onto the phone botched it somehow, downloaded directly from the mac and put it on there and it worked fine
06:11.17WisTilt2jonpry: im going to make sure that is the right smem addy, might not be correct
06:11.30rpierce99that's why I wasn't saying anything, I knew it was something on my end
06:11.42jonpryneed to find catptnoord
06:11.52jonpryer captnoord
06:13.00bzohaven't seen him in many months
06:13.01jonprymaybe somebody on xda can tell us if there is winmo app with negative currents
06:13.44jonpryhey bzo
06:13.57bzonice progress on the battery algo
06:14.03jonprythanks
06:14.19jonpryi think it will work for us
06:14.56bzoso what is left to do?
06:15.11jonprywell we are missing a linearizer
06:15.16jonpryi thought i had one :p
06:15.21rpierce99WisTilt2: do you want logs for failed wakes?
06:15.40jonpryand it is hard to turn some algorithm into an actual application
06:15.47WisTilt2maybe one, they'all be the same
06:16.11jonpryit needs to have code for reading configs and command line crap
06:16.37jonprydo logs, read save state...
06:16.40jonprymaybe UI
06:16.59rpierce99[  232.396484] msmfb_start_dma 6940.000 ms after vsync request
06:17.05bzomeh it's always this way, exciting intial work, then the mundane task of making it usable
06:17.40rpierce99full log http://pastebin.com/uS29a7cn
06:17.41WisTilt2rpierce99: same error.  if you dont get any different ones we're good
06:18.29rpierce99WisTilt2: but the sleeps and wakes are amazing
06:18.32rpierce99very fast
06:18.34jonpryWisTilt2, i'm using some stupid app on winmo, battlog. it has current while charging and not
06:19.02jonprybut its much higher while charging
06:19.19WisTilt2is it showing negative while charging?
06:19.29jonpryno
06:20.12WisTilt2rpierce99 yeah fast sleep now and as fast wakes.  boot up time should be much faster too.  try switching to app menu then back to desktop, should be instant
06:20.54WisTilt2jonpry: i can have it display that part of smem and see which offset is changing when charger is plugged in to find it
06:21.07jonprysounds like a reasonable plan
06:21.09WisTilt2i know one goes to zero
06:21.14jonpry:p
06:21.25WisTilt2cant be too far off address wise
06:21.40jonpryi wouldn't think so
06:21.44rpierce99in zeam it doesn't seem much different, it's animated though so I'm not sure it would be different
06:21.53jonprybzo, devil is in the details
06:22.52bzojonpry, it sure is. Just like at the camera stuff, it started 2 months ago, and it may finally get committed this weekend
06:23.17bzoerr, started working 2 months ago
06:24.48bzowonder if jb knew what he was getting into. He must be relieved to finally hand it off
06:24.51rpierce99found an option to turn off the animated app drawer, it is very quick
06:24.59WisTilt2rpierce99 what kind of battery life you getting with that last posted test kernel?
06:25.38jonprybzo i'm excited to get camera anyways
06:25.44rpierce99I'm usually on the lower end of the rhod400s with all the apps I have syncing, with light use I can go 12-14 hours
06:26.14WisTilt2overnight in sleep with sync should get you under 1% per hr
06:26.22WisTilt2this kernel will get a bit more
06:26.32jonpry4 days?
06:26.58bzoWisTilt2: are rhod400/500 testers reporting < 1% per hour?
06:27.24manekinekoyeeah, I see that power consumpmtion
06:27.27manekinekoon my rhod400
06:27.33WisTilt2yes several.  one reported .3% over a 10-12hr period in sleep
06:27.40rpierce99I'll do a drain test tonight, i'll charge it now and when I go to sleep I'll leave it off the charger, should I boot back to winmo to get the final battery reading?
06:27.43bzoany auto syncing of apps manekineko?
06:27.47WisTilt2i average around .5
06:28.07manekinekoI have all Google Sync on
06:28.12bzodamn, I've never gotten better than 1.7%
06:28.24manekinekoGmail, calendar, tasks, reader, uhh everything I guess
06:28.29manekinekocontacts
06:28.30rpierce99talk?
06:28.32manekinekotalk
06:28.36manekinekochrome2phone
06:28.38rpierce99reader?
06:28.40manekinekoyup
06:28.44manekinekoI like the Google apps hehe
06:28.49rpierce99as do i
06:28.51manekinekonothing non-Google though other than ClockSync
06:28.53bzowow, that's great with all that network activity
06:29.01WisTilt2rpierce99: after you take it off charge, use data a bit and get the battery down a bit then let it sit until it doesnt change and calc from there
06:29.01bzoway better than winmo
06:29.03manekinekoyeah, I get better battery life in Android than WinMo
06:29.17manekinekoit is a bit erratic though
06:29.19bzowho would have though that even a few months ago
06:29.32manekinekosometimes battery life is phenomenal, sometimes not so much
06:29.52WisTilt2manekineko which kernel you running?
06:30.00manekinekoyour test kernel, latest posted by arrrghhh
06:30.11rpierce99WisTilt2: so start the test the moment it says it's fully charged in android, and get the final reading in the morning from android also?
06:30.55WisTilt2ok. that one is good on power.  this one is better by a little bit and arrrghhh will post it tomorrow.  other enhancements in this one too
06:31.08manekinekosweet
06:31.12manekinekoI don't suppose netloc is one of them? hehe
06:31.56WisTilt2rpierce99 no, after charger is off do browsing or play sound or whatever for a few then let it settle until it stays on the same value and go from that point
06:32.12WisTilt2its really not accurate until below 90% anyway
06:32.20rpierce99ok so I just want to get a stable reading
06:32.26WisTilt2correct
06:33.03rpierce99so should I not charge it all the way up if >90% is inaccurate anyways
06:33.11rpierce99i'm sure I won't need all 100% for 8 hours
06:33.11WisTilt2manekineko nope not yet
06:33.32WisTilt2close to 90% should be perfect
06:33.42*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
06:33.51jonprybzo: have to get it built for arm too :p
06:34.23bzojonpry: lol, your userland code is running on x86?
06:34.34jonprywell yeah :p
06:35.15jonprythats the beauty of userland
06:35.50bzotru, could be said about any modularized code
06:36.08WisTilt2z80, thats serious stuff
06:36.28WisTilt2or 8080?
06:36.31jonpryrun on z80?
06:36.38jonprywould never get done
06:36.51jonpryits like teraflop
06:36.51WisTilt2just thinking about the good old days
06:37.04bzowhat was that consumer pc that ran on the z80, the sinclair or sth?
06:37.15jonpryi had a kaypro
06:37.28jonprybut nes was z80
06:37.37WisTilt2vector graphic or dont forget the good old trs-80
06:38.01bzoah, here it is: http://en.wikipedia.org/wiki/ZX81
06:38.03jonpryc64 was 8080
06:38.05WisTilt2vector graphic with cpm os was the thing
06:38.11bzowas thinking we had come full circle with the chicklet keyboard
06:38.11jonpryoh yeah
06:39.10jonpryoO
06:39.18bzolol, 1kB memory, 64kB max
06:40.35jonpryram/rom?
06:41.02bzoram I would think
06:41.37bzogood ol c64 was probably the first computer I really used though
06:42.08jonprysomewhat before my time :p
06:42.20WisTilt2did you ever see the print spooler program for the c64?
06:42.46WisTilt2or sargon chess?
06:43.13bzoeh, only remember programming in basic on the c64
06:43.50manekinekohah, speaking of eratic battery life, my phone just got hit by the bug that drains it out while connected to the charger...
06:44.31WisTilt2selling back to the grid huh?
06:44.42manekinekolol yup
06:44.45manekinekothat's the pro side
06:44.50manekinekonot having to pay for electricity anymore
06:44.51bzojonpry: is the original mac more in your time?
06:45.00jonprynope
06:45.15jonprythat's like 1976
06:45.29jonprybut all mac's are too old for me
06:45.34bzonah, mac is more current than that
06:45.38bzoeven lisa
06:45.41jonpryalways like last years hardware
06:46.10jonpryer 1986
06:46.30jonpryapple IIe
06:46.57jonpryfirst computer i saw
06:47.14*** join/#htc-linux cazh_ (~quassel@3007ds2-rd.0.fullrate.dk)
06:47.25BoominSVXI've still got a commador 64 7 floppies for oregon trail was the best
06:47.45jonpryit is 1976
06:47.45bzoloved the apple iis, hate apple now
06:47.46jonpryhttp://en.wikipedia.org/wiki/Apple_I
06:48.40WisTilt2i feel old now. my first computer was one i built, Heathkit H8
06:48.52WisTilt2late 70's
06:49.12jonpryat least its newer than apple I
06:49.32bzohaha, almost the analog age of computers
06:49.57rpierce99my first computer was an 386SX, I was in the 4th grade, we had to buy a DX2 upgrade chip and cache seperately
06:50.19manekinekoman that was a sweet machine when it came out
06:50.21bzoheathkit was awesome though
06:50.28manekinekoI was so jealous of my friend that had one and its EGA graphics
06:50.29jonpryto get that floating point that rhod doesn't have?
06:51.17WisTilt2yeah heathkit was great.  i got my ham radio license in 1965 and heathkit had all the goodies for amateur radio back then
06:52.37bzounfortunately heathkit was in the process of shutting down when I was a kid
06:53.09WisTilt2BoominSVX: you get that kernel booted?
06:53.30jonpryok, must sleep, ttyl
06:53.36bzogn
06:53.44WisTilt2nite jonpry, we'll work on the charge number tomorrow
06:53.50BoominSVXyes. i seem to be lacking in dropbox though
06:54.19WisTilt2you mean log info not there?
06:54.43BoominSVXno last kmesg. Thats what i get for running a no vanilla build
06:54.58rpierce99BoominSVX: have you rebooted? I don't think dropbox populates until the next book, it reads in the old kmsg
06:55.08WisTilt2i had it disabled but thought i turned it back on in this kernel
06:55.24BoominSVXjust 316b last kmesg
06:55.40BoominSVXand system-tombstones
06:55.48BoominSVXyes, i rebooted to check
06:55.52*** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk)
06:55.59rpierce99oh ok
06:56.15WisTilt2i must still have that disabled then.  what do you think about the sleep wake times now?
06:57.13BoominSVXWisTilt2: It's beautiful. Even on a backlight on/blank screen, it comes right back... and quick
06:57.31WisTilt2sleep happening within 1second?
06:57.50BoominSVXI use ADW so it may be hindering the speed.
06:57.57BoominSVXsleep almost instant, yes
06:58.01WisTilt2what phone?
06:58.13BoominSVXRhod 400
06:58.30WisTilt2should work the same on all rhods hopefully
06:59.00BoominSVXI can't wait till your stuff gets in the autobuild
06:59.31BoominSVXwe all appreciate you friend.
06:59.50WisTilt2wont commit it until i get the damn occasional non-wake issue completely squashed.
07:00.49BoominSVXyea, perfection is seldom achieved, but your closer than ever now.
07:00.54WisTilt2bzo: will we gain anything by having a 256k ramconsole?  its working very nice, especially in ebi instead of smi
07:01.41bzodoesn't seem like having a 128k buffer has been a problem for anyone
07:01.47bzobut hey, what's another 128k?
07:02.20WisTilt2we dont have anything at ebi base i guess?  thats where im running it and nothing stepping on it at all now
07:02.44bzowe do need to explicitly carve out a region for it
07:02.46BoominSVXWisTilt2: I do have one tiny little suggestion though. The keyboard bl... does it time out a little quick or is it just me?
07:02.56bzoyou've probably just been lucky nothing is writing there
07:03.17WisTilt25seconds, which was the default when i started in all this
07:04.08*** join/#htc-linux Noellenchris (~kvirc@pool-173-61-114-241.cmdnnj.fios.verizon.net)
07:04.32WisTilt2could increase that timeout to 10s
07:04.48BoominSVXI know, I don't mean anything by it. Just seems that 10 or 15 wouldn't hurt anything
07:05.19BoominSVXI time out quiet a bit, but maybe i'm just a slow texter.
07:05.31WisTilt2it resets when typing but i think 5s might be too low if you pause while typing
07:06.18WisTilt2let me change that to 10s... then when arrrghhh puts it up for the masses we'll see what kind of response we get
07:07.24BoominSVXyea, its not exactly a power hog, I guess we'll see what the masses say then
07:08.12WisTilt2ok get this kernel pack.  10seconds timeout now
07:08.32BoominSVXI'll play with this kernel tonight and let arrrghhh know if I can find anything useful. Gotta get out of here.
07:08.41WisTilt2ok sounds good.
07:09.05BoominSVXThank you sir!! g'night
07:09.36*** join/#htc-linux MacDrunk (~marper@201.165.161.195)
07:10.27XirXessame place as usual right WisTilt2?
07:11.07*** join/#htc-linux cazh_ (~quassel@3007ds2-rd.0.fullrate.dk)
07:11.34WisTilt2yep
07:20.32WisTilt2XirXes: if you run with autobl off, you might want to dl the kernel pack i just put up that fixes it when in manual mode.
07:22.50XirXesi do run with auto bl on but ill dl the newest one anyway
07:23.14WisTilt2k.  thats the one arrrghhh will put up so you'll match that one
07:24.21XirXeswhat was all the stuff that isnt in the flying text anymore?
07:25.03WisTilt2wasted cpu cycles as i like to call it
07:25.12XirXeslol indeed
07:26.01WisTilt2just kernel boot that you cant read anyway as it flys off the screen and cant scroll back.  its all in dmesg still
07:28.54XirXesit boots so much faster now
07:29.40WisTilt2yep.  wait until you see sleep
07:30.14XirXesi just barely let it sleep. pretty much instant
07:30.33XirXesdidnt really get the oportunity to blink
07:31.14XirXeswhen i woke it back up it was instant too. i saw the black square tho
07:31.34WisTilt2black square in upper left corner?
07:32.09XirXesthats the one
07:32.35WisTilt2dont know what that is yet as its not always there
07:33.16XirXesi never noticed it before the move to 35 framebuffer so i assume its related but idk
07:33.16WisTilt2if you get a non-wake just put it back to sleep and it will wake on next attempt.  still working out this pan_display problem that happens now and then
07:37.03XirXesyour really getting this thing running nice. i definitly feel like it does better than my g1 these days
07:37.05*** join/#htc-linux rpierce99_ (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
07:37.10XirXesnot my g2 tho
07:37.21XirXesbut that cant be helped
07:38.57WisTilt2should be a bit more stable now.  well see how it goes and let arrrghhh or myself know if there are any strange things we dont already know about.
07:39.12WisTilt2im going to bed.  catch you guys later
07:39.25XirXesnight
07:46.50*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153)
07:53.01*** join/#htc-linux Termana (~bradley@122.151.90.7)
08:15.15*** join/#htc-linux Zeman4323 (~Zeman4323@CPE-65-30-190-208.wi.res.rr.com)
08:18.17*** join/#htc-linux MacDrunk (~marper@201.165.161.195)
08:31.10*** join/#htc-linux venom00ut (~venom00@unaffiliated/venom00)
08:35.51*** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk)
09:05.07*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
09:07.47*** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk)
09:12.34*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
09:23.14*** join/#htc-linux rob_w (~bob@ppp-188-174-88-17.dynamic.mnet-online.de)
09:23.46*** join/#htc-linux rob_w (~bob@ppp-188-174-88-17.dynamic.mnet-online.de)
09:25.44*** join/#htc-linux kvaster (~kvaster@93.84.112.82)
09:35.13*** join/#htc-linux _twitch (~burning_a@64.112.96.58.static.exetel.com.au)
09:36.34*** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net)
09:53.05*** join/#htc-linux greg- (greg-@port-4488.pppoe.wtnet.de)
10:07.18*** join/#htc-linux balans1 (~Gebruiker@82-170-217-205.ip.telfort.nl)
10:09.03*** join/#htc-linux cazh_ (~quassel@3007ds2-rd.0.fullrate.dk)
10:13.17*** join/#htc-linux venom00ut (~venom00@unaffiliated/venom00)
10:41.44*** join/#htc-linux camro (~camro@89-104-29-101.customer.bnet.at)
10:50.46*** join/#htc-linux Erikson (~Erik@p54B76F26.dip.t-dialin.net)
10:57.55*** join/#htc-linux bja (~bja@c-24-1-253-181.hsd1.il.comcast.net)
11:19.04*** join/#htc-linux MN-- (~yaaic@host86-134-32-198.range86-134.btcentralplus.com)
11:19.17*** join/#htc-linux HD2Owner (57f54144@gateway/web/freenode/ip.87.245.65.68)
11:19.32*** join/#htc-linux jameschurchman (u220@gateway/web/irccloud.com/x-yowbbswivngulaxh)
11:40.31*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
11:53.17*** join/#htc-linux venom00ut (~venom00@unaffiliated/venom00)
11:55.52*** join/#htc-linux kiozen (~kiozen@rgnb-4d053f3a.pool.mediaWays.net)
12:03.41NetRipperdcordes_, pong
12:03.42NetRippersup?
12:05.09NetRipperdcordes_, if it's about Photon.. Cotulla worked on that and just tar.gz'd his source of both haret and the kernel
12:05.17NetRipperdcordes_, http://forum.xda-developers.com/showthread.php?t=952996
12:06.57NetRipperdcordes_, if it's about htc-linux wiki.. the spamming has stopped, but i can't find a decent automated way to clear the wiki of all spam
12:30.13*** join/#htc-linux dekar_ (~dekar@drms-590ed8af.pool.mediaWays.net)
12:36.23*** join/#htc-linux LordDeath (~Lord|Lapt@cable-81-173-166-52.netcologne.de)
12:41.57*** join/#htc-linux MassStash (~MassStash@c-67-175-41-173.hsd1.il.comcast.net)
13:04.03*** join/#htc-linux D3tul3 (~Oliver@cpe-174-109-223-235.nc.res.rr.com)
13:06.36*** join/#htc-linux GNUtoo|laptop (~gnutoo@host157-58-dynamic.116-80-r.retail.telecomitalia.it)
13:09.52dcordes_NetRipper: yoo just chilling :) is the NL weather as nice as the Bavarian today ?
13:10.04NetRipperyou mean gray and depressing?
13:10.04dcordes_NetRipper: the cookie thing was temprary it works now
13:10.05NetRipperthen yes
13:10.09dcordes_NetRipper: thanks a lot :)
13:10.16dcordes_:(
13:10.44NetRipperyea you have to allow session cookies for captcha to work
13:10.56NetRipperit's allowed by default on any browser
13:11.06dcordes_did you create the custom captcha ?
13:11.29dcordes_ya that's why I was wondering.. think I had it enabled. I'm using firefox 4 beta
13:11.37dcordes_maybe that caused the problem
13:11.46NetRipperyea modified some existing php captcha to make it custom.. it's not a popular captcha so it's not auto-cracked or auto-send-to-chinese-that-get-paid-for-decipheering
13:11.52dcordes_updated the [[Photon]] page with kernel and haret source link
13:11.52unili882http://htc-linux.org/wiki/index.php?title=Photon
13:12.03dcordes_and tweeted it
13:12.06NetRipperk
13:12.14NetRipperbeen there a while though :P
13:12.28dcordes_nvm
13:13.14NetRipperi had updated the main page news thingy for it
13:13.35dcordes_ah I thought it was Cotulla
13:13.44*** join/#htc-linux LuHe (~LuHe@91-118-60-155.dynamic.adsl-line.inode.at)
13:13.48NetRippercotulla made the photon and photonstatus pages
13:14.12dcordes_ok
13:15.14dcordes_hmm
13:15.49*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
13:16.39dcordes_GNUtoo|laptop: didn't manage to prepare SHR for the HD2 yet
13:17.07GNUtoo|laptopdcordes_, hi
13:17.09GNUtoo|laptopok
13:17.13GNUtoo|laptopbut did you get the image?
13:17.14*** join/#htc-linux RaiderX (5b6d2a71@gateway/web/freenode/ip.91.109.42.113)
13:17.28RaiderXhi
13:19.55*** join/#htc-linux phh (~quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
13:20.38dcordes_GNUtoo|laptop: 5d8d3a722cb6ae192a5e8e3a31d5ecab  full-htcdream.tar.gz
13:20.45dcordes_GNUtoo|laptop: is it the correct md5 ?
13:21.31GNUtoo|laptopdcordes_, no
13:22.02dcordes_GNUtoo|laptop: ok then I should download it again
13:22.04GNUtoo|laptopdcordes_, the images was supposed to come from my server and to be a bit customized for the nexusone
13:22.32dcordes_GNUtoo|laptop: is it compiled for cortex-a8 ?
13:22.52dcordes_GNUtoo|laptop: we need to convince cotulla ;) the cortex image booted in < 10 secs for me
13:22.58GNUtoo|laptopdcordes_, yes, for n900
13:23.04dcordes_cool
13:25.00GNUtoo|laptopdcordes_, I'll PM you for the address of the file
13:25.20dcordes_GNUtoo|laptop: thanks
13:34.02*** join/#htc-linux RaiderX_ (5b6d2a71@gateway/web/freenode/ip.91.109.42.113)
13:49.08*** join/#htc-linux gauner1986 (~Miranda@p5B382CEE.dip.t-dialin.net)
13:50.46dcordes_bbl
13:52.43*** join/#htc-linux Christie (~Esa@adsl-71-156-47-62.dsl.irvnca.sbcglobal.net)
13:58.26*** join/#htc-linux jonpry (~jon@63.245.31.4)
14:06.09*** join/#htc-linux Daevoq (~IceChat7@95.235.99.246)
14:06.46*** join/#htc-linux _bukington (~bukington@fac34-2-82-228-151-145.fbx.proxad.net)
14:10.28*** join/#htc-linux D3tul3 (~Oliver@cpe-174-109-223-235.nc.res.rr.com)
14:14.10*** part/#htc-linux HD2Owner (57f54144@gateway/web/freenode/ip.87.245.65.68)
14:16.48*** join/#htc-linux MN-- (568620c6@gateway/web/freenode/ip.86.134.32.198)
14:33.18*** join/#htc-linux tyween (~tyween@pool-71-163-117-57.washdc.fios.verizon.net)
14:36.51*** join/#htc-linux MassStash (~MassStash@c-67-175-41-173.hsd1.il.comcast.net)
14:39.02*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
14:56.04*** join/#htc-linux arrrghhh (~arrrghhh@c-71-237-40-111.hsd1.co.comcast.net)
14:59.11*** join/#htc-linux localhost (~Chris@cpe-76-188-107-188.neo.res.rr.com)
15:03.39*** join/#htc-linux Sanitoeter (freenode@unaffiliated/sanitoeter)
15:04.21*** join/#htc-linux kvaster_ (~kvaster@93.84.112.82)
15:10.35*** join/#htc-linux Erikson_ (~Erik@p54B74A30.dip.t-dialin.net)
15:13.15*** part/#htc-linux Sanitoeter (freenode@unaffiliated/sanitoeter)
15:15.26*** join/#htc-linux Segnale007 (~Segnale00@host57-255-dynamic.35-79-r.retail.telecomitalia.it)
15:18.15*** join/#htc-linux rpierce99_ (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
15:41.46*** join/#htc-linux RaiderX (5b6d2a71@gateway/web/freenode/ip.91.109.42.113)
15:42.38*** join/#htc-linux Cotulla (~opera@nat004-252-205-109.tvoe.tv)
15:46.02*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
15:46.29*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
15:48.26Cotullabdh
15:48.27Cotullahey
15:51.08*** join/#htc-linux g3rm (~germo@89-77-81-175.dynamic.chello.pl)
15:52.49*** join/#htc-linux rpierce99_ (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
15:53.35arrrghhhbdh to you too
15:55.15jonpryYeah putting fb in SMI will make big improvement
15:55.53*** join/#htc-linux onen|openBmap_ (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
15:56.09Cotullawtf u still on it ? :)
15:56.21jonpryjust until you implement it
15:56.32*** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-12-212.bb.netbynet.ru)
15:56.47CotullaI implemented my battery driver, dunno how precision is it, but it doesn't want charge :(
15:56.50Cotullastrange...
15:56.58Cotullasame GPIO stuffs works inside MAGLDR
15:57.07Cotullalinux at start up clear GPIO configurations?
15:57.09jonpryCotulla, can you dump the regs from ds2746 on leo?
15:57.13Alex[sp3dev]Cotulla: maybe it's just not updating the status
15:57.31jonpryi found the datasheet settings are really bad for htc battery
15:57.47Alex[sp3dev]jonpry: which kind of battery you have?
15:58.23Cotullajonpry, u can use datasheet only as reference. I think HTC use changed scheme of layout.
15:58.50Cotullabut yes I can dump, not now however. tomorrow will dump it.
15:59.14CotullaAlex[sp3dev, which status?
15:59.30CotullaI mean I setup two GPIO inside MAGLDR and it charging. in the kernel it discharge...\
15:59.52Cotullabtw who got this stupid idea to use spinlock in dexcomm?
15:59.59Alex[sp3dev]Cotulla: you get that it's discharging from registers, right?
16:00.11Alex[sp3dev]Cotulla: dunno. maybe it was copied from proc_comm?
16:00.44jonpryAlex[sp3dev], i dunno an htc battery that fits :p
16:01.11CotullaI got data via dex
16:01.14CotullaCUR < DCUR
16:01.20Cotullain MAGLDR CUR > DCUR
16:01.34CotullaI removed all charging GPIO references inside kernel and it still discharge
16:01.42Cotullait's stupid to use spinlock there
16:01.50Cotullamutex must be used :)
16:01.57Alex[sp3dev]Cotulla: do you know what register we can monitor during dex init to check if radio is inited? for example, to be able to boot off nand and instead of mdelay(6000) wait for it?
16:02.37Cotullahm it's interesting question, my first DEX inside MAGLDR also fails with timeout, but smsm already inited
16:02.43CotullaI will look
16:03.23*** join/#htc-linux surge (~surge@pool-98-118-157-221.bflony.fios.verizon.net)
16:03.27Alex[sp3dev]Cotulla: maybe spinlock is there to allow using dex calls from interrupt context? (but who the fuck will do it?)
16:03.41Cotullaactual problem: (I saw some kind of workarounds in somebodies git)  dex battery need more time, because it make a lot of operations inside, so there udelay() cause 100% cpu load
16:04.01Cotullait will make effects on high resource tasks
16:04.05Cotullalike audio & video
16:04.25Alex[sp3dev]Cotulla: you mean, dex response takes more time?
16:04.39Cotullafor battery yes...
16:04.57jonpryis that a problem on battery_smem?
16:04.57Cotullaanyway I make separate dex_command_battery in my 32 tree
16:05.08Cotullawhich execute only 8A
16:05.34Alex[sp3dev]then yes, try using a mutex and see if it is better. it is a good idea, as it will allow us to sleep while dex is coming from arm9
16:05.43Cotullanot only mutex
16:05.44jonprywhere are you getting charge current from. wistilt2 said it is not located right after discharge, where is should be
16:05.55Cotullafor irq-off it must be separate version
16:06.06Cotullait can be without spin locks at all
16:06.09Alex[sp3dev]Cotulla: why do we need to disable irq at all?
16:06.09Cotullabecause irq already off
16:06.17Cotullafor example PM sleep
16:06.20Cotullathere DEX call used
16:06.27Alex[sp3dev]Cotulla: but we can make a separate call
16:06.30Cotullaand I think there no irq-enabled
16:06.37Alex[sp3dev]just disable interrupts inside the pm function, not in dex
16:06.48Cotullamutex will fail :)
16:06.49Cotullayeah
16:06.54Cotullaseparate funtioncs
16:07.02Cotullajonpry, DEX8A
16:07.12Alex[sp3dev]yes, i will look into it after finishing most work on 35
16:07.12Cotulla5 words
16:07.31CotullaAlex, so u know why it still discharging?
16:07.46Alex[sp3dev]Cotulla: no, i'm getting data via i2c. maybe dex is lying
16:08.16Alex[sp3dev]or maybe arm9 or linux toggles some gpio on boot and you're not setting it to the correct value
16:08.35Cotullabut MAGLDR show all right :P
16:08.36Cotullaokay
16:08.38jonpryCotulla, we are doing 8a
16:09.21Cotullaokay I gotta do sound now I think
16:09.23Cotullaor microp
16:09.57Alex[sp3dev]and i'm back to some java stuff :(
16:10.08*** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com)
16:13.08*** join/#htc-linux siulmagic (~IceChat7@24.54.255.153)
16:18.37jonprywhat is the magic command to make a modules tarball?
16:19.33Alex[sp3dev]find ~/foo/modules -name "*.o" | xargs cp -t . and then tar cvf ~/foo.gz .
16:19.41Alex[sp3dev]but maybe directly feed list of files to tar
16:19.43Cotullahh
16:20.04Cotullahm got 85 ma charge current
16:20.13Cotullalooks like it's USB 100MA
16:20.34Cotulla<4>[  100.707611] [BATTERY] LEVEL=47, VOLT=3755, TEMP=238, CUR=86, DCUR=279
16:25.43Alex[sp3dev]generally, mkdir x; find modules -name *.ko; cd x; tar cvf ../modules.tar .
16:26.06Cotullacopy by hands & press Pack to TAR
16:26.27Cotulla:P
16:26.34Alex[sp3dev]Cotulla: btw. smem battery was rather buggy on kovsky
16:26.46Cotullakovsky 2746?
16:26.52Alex[sp3dev]yes
16:26.57*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153)
16:26.58Cotullaso it's from different world
16:27.11CotullaRHO & TPZ have not control chip
16:27.13Alex[sp3dev]yes. it's a better device
16:27.21Cotullathere level got from ADC
16:27.38Cotullaand "smem battery" sounds crazy
16:27.44Cotullawtf smem. just i2c only
16:28.02Alex[sp3dev]yeah, using i2c and no problems
16:28.03CotullaHTC Ace have DS2746
16:28.10Cotullabut there some hard parameters
16:28.33Cotullabasic problem that u doesn't know real FL
16:29.13jonpryAlex[sp3dev] how are you getting battery info over i2c?
16:29.18Cotullaold htc devices assume that FL decreased for 2% (don't remember number) every full charge
16:29.45Cotullau may implement not-very-user-friendly algo
16:29.46Alex[sp3dev]jonpry: just reading it via i2c. on x1 ds2746 is at 0x36
16:29.56Cotullaadd some kind of calibration
16:29.59jonpryoh, can you read out the params?
16:30.08jonpryi need ds2746 data points
16:30.11Alex[sp3dev]jonpry: yes, raw access to ds2746
16:30.24Cotullaadd special mode - battery calibration
16:30.37Alex[sp3dev]maybe just disassemble winmo driver properly?
16:30.53Cotullaturn on all devices and got current about 400ma when measure real capacity of battery
16:31.20Cotullabut users ofcourse need do this operation several times in year
16:32.35Cotullabut I think better for u get HTC Ace driver and try to find right values
16:33.08jonprybleh, my driver is way cooler :p
16:33.09Alex[sp3dev]later. first need to finish implementing microp, bt, wifi and sound on 35
16:33.34Alex[sp3dev]jonpry: no it is not. HTC Ace driver has DWORDs in it ;)
16:34.18jonpryjonpry driver has fortran
16:34.21Cotulladoubt it
16:34.58jonprythe powell algorithm is more or less the output of f2c
16:35.04Cotullau have one/two devices with half died battery (?) and no professional testers & equipment
16:35.15Cotullaas well u have limited time to test it
16:35.45Cotullaas well same device may have different batteries
16:35.48Alex[sp3dev]https://github.com/Kali-/htc-kernel-ace/blob/master/drivers/power/ds2746_param.c DWORD ftw
16:35.55jonpryyeah working on battery switch problem
16:36.00Cotullawhich have different parameters
16:36.25jonpryi'm hoping battery id has entropy
16:36.50Cotullaand at the end: if it was so easy, htc implemented such algo long time ago and used it on all devices, because it doesn't need calculating parameters
16:36.58Cotullafor every new device
16:37.07jonpryyour just jealous
16:37.16Cotullano..
16:37.22CotullaI just understand things...
16:37.34Cotullalimited of hobby abilities
16:37.39*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
16:37.42jonpryits not my fault i can write new better code, faster than you can try all the broken htc crap
16:37.54Cotullamake it at first :)
16:38.00Cotullaand let it work on all batteries
16:38.28Cotullaif such algo existed, they was implemented long time ago before u, I am sure.
16:38.44Cotullasame true for camera, u never got nice shoots using datasheet only
16:39.16Alex[sp3dev]Cotulla: i never got to see the datasheet in first place.. oh, i did, but after copying wince driver ;)
16:39.29jonprylook nobody has made this before. its based on paper written in 10/10 and vastly extended
16:39.51CotullaI think they use some equipment, like few batteries connected to discharge scheme, which collects data, monitor values, build curves and etc
16:40.19Cotullamaybe as well have few batteries which are somekind of dead
16:40.37jonpryand then use one curve for all of them
16:40.39jonprygenious
16:40.43jonpryand it works so well
16:40.55Cotullaat least it works for new battery during 1- 1.5 year
16:41.18CotullaI remember Toshiba G900 - there was also ADC based level detection and there it SUCKS
16:41.28jonpryjust remember folks, when your meter give you bad readings, its because the battery is bad
16:41.30Cotullathere 20% means 0
16:42.13Cotullaas well I saw few parameters for different batteries in dlls
16:45.41Cotullahey
16:45.52CotullaGNUtoo search u, dcordes
16:46.55Cotulla"look nobody has made this before. its based on paper written in 10/10 and vastly extended' <---- u sure it's working??? maybe there fatal mistake inside
16:48.29CotullaAlex, ur sound works great? or should I port from 27 myself?
16:49.02Alex[sp3dev]Cotulla: it works on rpc part, but you need to port sound routing and audioparams from 27
16:51.13Cotullahm
16:53.33Alex[sp3dev]Cotulla: i'm listening to sapphire now ;)
16:53.50Cotulla?
16:54.08Alex[sp3dev]Cotulla: a track by Andy Hunter.. said it to confuse you
16:54.14Cotullaokay ;)
16:55.08Cotullaheh
16:55.48Alex[sp3dev]i should say that my loox 720 has better sound than my laptop
16:55.55CotullaI am coding under "Bach Toccata & Fuge d-moll" now :)
17:01.14*** join/#htc-linux mastermerlin (~Adium@p4FEE5DE0.dip.t-dialin.net)
17:06.20Cotullahm maybe I need gpio_request
17:06.26Alex[sp3dev]you do
17:06.34Cotullawtf??
17:06.39Cotullait's not working without?
17:06.42Alex[sp3dev]it will work
17:06.46Alex[sp3dev]but print a huge warning
17:06.54Cotullait doesn't pring
17:06.55Cotullaprint
17:07.04Cotullafor gpio_set_value
17:07.50Alex[sp3dev]maybe on 32 it won't... in 35 and later they've added a lot of debugging messages and tests to make sure gpios are used properly and drivers don't fight for them
17:08.38Cotullait show only at direction config
17:08.59Alex[sp3dev]anyway, it's just a warning
17:10.33Cotullau sure...
17:10.38Cotullawtf it's not working
17:11.16Cotullafunny
17:11.23Cotullaso much code
17:11.24Cotullafor gpio
17:11.37Cotullawtf
17:11.44Cotullaand it located in 3-4 different place
17:11.50Alex[sp3dev]yes, but now there's a generic gpio framework for all SOCs and a sysfs interface for it
17:12.06Cotullawhy not put it to one folder?
17:12.20Cotullaas well put there readme.txt
17:12.22Alex[sp3dev]and simple drivers like gpio keys and bitbang i2c are used without changes across different SOCs
17:12.24Cotullawith small description
17:12.28Cotullaof call flow
17:12.28ali1234because then people would go "herp derp why isn't sysfs code all in one place"
17:12.30Alex[sp3dev]Cotulla: there is a readme
17:12.49Alex[sp3dev]it is in Documentation/gpio.txt
17:13.08Cotullalet me guess? outdated?
17:13.11Alex[sp3dev]nope
17:13.27Alex[sp3dev]not yet ;)
17:13.39Alex[sp3dev]because all this gpio stuff was written not so long ago
17:13.56Cotullahm
17:13.57Cotulla<4>[    1.344116] [BATTERY] charge(1, 0)
17:13.57Cotulla<4>[    1.344940] [BATTERY] charge 0 1 1
17:14.09Alex[sp3dev]what do the numbers signify?
17:14.13Cotullabefore request it was zero
17:14.24Cotullathere CHGEENABLE
17:14.29CotullaAC_SPEED
17:14.32CotullaUSB_SPEED
17:14.38ali1234it was over 18 months that the gpio system was rewritten to allow drivers to request gpios
17:14.50Alex[sp3dev]ali1234: 18 months is not much
17:15.17Alex[sp3dev]it was around 23-25 kernel iirc
17:15.44ali1234it didn't start showing up in arm drivers until about 2009
17:16.16Cotullawtf enable is 1
17:16.18Cotullait must be 0!
17:16.27Alex[sp3dev]whaat?
17:16.37Cotullaprintk("[BATTERY] charge %d %d %d\n",
17:16.37Cotullagpio_get_value(RHO_GPIO_CHG_AC_SPEED),
17:16.37Cotullagpio_get_value(RHO_GPIO_CHG_USB_SPEED),
17:16.37Cotullagpio_get_value(RHO_GPIO_CHG_ENABLE));
17:17.17Cotullahttp://pastebin.com/grSVYjys
17:17.22Cotullawhole code of this function
17:18.01Alex[sp3dev]maybe set direction as input first? or i dunno
17:18.32Cotullait's done already in probe
17:18.43Alex[sp3dev]but it may be reset when you do set_value, right?
17:18.55Cotullano...
17:18.57Cotullait just pins
17:19.06Cotullain MAGLDR I setup them and it's working!
17:20.18Cotullaassembler code looks normal
17:21.04*** join/#htc-linux GNUtoo|nexusone (~GNUtoo@host157-58-dynamic.116-80-r.retail.telecomitalia.it)
17:22.21Cotullahm or maybe this gpio used somewhere without my clue
17:22.48Alex[sp3dev]well, it's your code :P
17:23.41Cotullabut I doubt in it
17:27.38*** join/#htc-linux greg-hd2 (~yaaic@port-4488.pppoe.wtnet.de)
17:30.52Cotullathat is looks nice in linux - modules params
17:31.20Alex[sp3dev]just don't overuse them when not needed. but great for testing
17:49.01*** join/#htc-linux greg-hd2 (~yaaic@port-4488.pppoe.wtnet.de)
17:49.25*** join/#htc-linux kvaster_ (~kvaster@vpn-e0.bas-net.by)
18:07.17*** join/#htc-linux lolmensch (d955bb13@gateway/web/freenode/ip.217.85.187.19)
18:09.34*** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net)
18:11.47Cotullawhere dalvik elf located?
18:12.07Alex[sp3dev]in /system/xbin, i guess
18:14.29Cotullawtf this shit still not charging\
18:14.30Cotulla%)
18:14.40Alex[sp3dev]the world is against you
18:19.08*** join/#htc-linux bja (~bja@c-24-1-253-181.hsd1.il.comcast.net)
18:19.52*** join/#htc-linux venom00ut (~venom00@unaffiliated/venom00)
18:21.56*** join/#htc-linux Segnale007 (~Segnale00@host57-255-dynamic.35-79-r.retail.telecomitalia.it)
18:30.17Cotullawtf
18:30.18Cotullareally
18:30.34CotullaVOLT: 3728 TEMP: 341 CUR: 411 DCUR: 303 LVL: 38
18:36.01jonpryare current and dcurrent in different units?
18:36.18Cotullain same
18:36.31Cotullain MAGLDR it's charging, in the kernel - no
18:36.34jonprylike my battery is fuly charged and i have cur=1709, dcur=340
18:36.42Alex[sp3dev]maybe something's draining more power in kernel?
18:36.54Cotullawait
18:36.56Cotulladata from dex
18:37.02Cotullashow that there no charging current
18:37.07Cotullaand voltage go down
18:38.10Cotulla<4>[    0.692718] [BATTERY] DEX DATA T=60E V=D65 C=38 D=1AE R=1264
18:38.10Cotulla<4>[    0.693176] [BATTERY] LEVEL=30, VOLT=3717, TEMP=358, CUR=13, DCUR=276
18:38.10Cotulla<6>[    0.693420] batt:  30%, 3717 mV, -263 mA (-263 avg), 35.8 C
18:39.00Cotullahm then
18:39.01Cotulla<4>[   50.707397] [BATTERY] DEX DATA T=618 V=D5E C=175 D=1B5 R=1264
18:39.01Cotulla<4>[   50.707824] [BATTERY] LEVEL=27, VOLT=3710, TEMP=356, CUR=86, DCUR=280
18:39.01Cotulla<6>[   50.708068] batt:  27%, 3710 mV, -194 mA (-194 avg), 35.6 C
18:39.11Cotullalooks like USB speed not setuped
18:39.38*** join/#htc-linux DuperMan (~Duper@93-172-20-227.bb.netvision.net.il)
18:40.33jonpryi wonder how mine negotiated 1.7amps
18:40.46jonprybattery is *hot*
19:07.55*** join/#htc-linux bzo (~chatzilla@c-76-126-175-200.hsd1.ca.comcast.net)
19:16.00*** join/#htc-linux greg-hd2 (~yaaic@port-4488.pppoe.wtnet.de)
19:23.20*** join/#htc-linux |Jeroen| (~jeroen@d5152B25B.access.telenet.be)
19:24.49*** join/#htc-linux localhost (~Chris@cpe-76-188-107-188.neo.res.rr.com)
19:58.53*** join/#htc-linux _twitch (~burning_a@64.112.96.58.static.exetel.com.au)
19:59.19*** join/#htc-linux Elmstrom (~quassel@4807ds1-arno.0.fullrate.dk)
20:06.52*** join/#htc-linux tp2Probs (590c01fb@gateway/web/freenode/ip.89.12.1.251)
20:07.02tp2Probshi @ all
20:07.32tp2Probssome1 here?
20:14.42*** join/#htc-linux crawling (crawling@a89-152-195-220.cpe.netcabo.pt)
20:15.18*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
20:18.36*** join/#htc-linux surge (~surge@pool-98-118-157-221.bflony.fios.verizon.net)
20:19.06tp2Probswhen i boot android on my rhod400_de the internet browser open and want me to install LauncherPro
20:22.07*** join/#htc-linux MN-- (~yaaic@host86-134-32-198.range86-134.btcentralplus.com)
20:30.31Alex[sp3dev]ok, time to implement microp keypad and optical joystick :P
20:36.19bzohi Alex[sp3dev]
20:36.48Alex[sp3dev]bzo: hello
20:37.17bzowanted to ask your opinion: is board model id detection better in devices as atag or htc_hw?
20:38.42Alex[sp3dev]bzo: atag.. then we can just parse board name from userspace.. but we can do it on board early init and patch from there probably.. anyway, i dunno.. luckily, there's only one X1 board. unless some dude with a prototype comes in
20:39.35bzook, thanks. we'll probably having something in htc_hw anyways to service userland
20:39.50bzobut for kernel use, it seemed better to me to do atag, like emwe did for the monodie detection
20:40.19Alex[sp3dev]i want to get rid of htc_hw anyway. so better use atag. we can patch haret, it can get board name from wince. and we'll come up with something for nand bootloader then
20:41.07bzoI'll probably pull it from spl like the nand kernel is doing
20:42.12Alex[sp3dev]bzo: i'm afraid we'll have to overwrite spl with our bootloader in ram, so probably it'd be better to pull it off nand. but that's long before that
20:43.22bzo<PROTECTED>
20:43.31Alex[sp3dev]atag
20:43.37bzoyeah
20:43.56Cotullawtf ppl? read from smem model name and parse it by fixed list?
20:44.07Alex[sp3dev]Cotulla: is it guaranteed to be there?
20:44.15Cotullawhy not?
20:44.18Cotullaor in drv_glob
20:44.29CotullaSPL reads model id to some locationm
20:44.53bzothe nand kernel uses MSM_SPL_BASE + 0x81068
20:45.01bzothink that will still be there for nand boot?
20:45.25*** join/#htc-linux mastermerlin (~Adium@p4FEE5DE0.dip.t-dialin.net)
20:45.47Alex[sp3dev]i'm afraid that if we come up with our own loader, it will overwrite the spl in ram. or can we have interrupt vectors at 0xffffxxxx something?
20:46.02Cotullaand why u want remove htc_hw
20:46.20Cotullauserspace drivers can detect it nice
20:46.46Alex[sp3dev]Cotulla: because it is a dirty mess. vibra can be moved out of there, audio should be implemented as acoustic, and board type should be parsed from /proc/cpuinfo
20:46.58Cotullait's not mess
20:47.18Cotulla<PROTECTED>
20:47.30Cotullahtc_hw can contain data in any format
20:47.45Cotullalike model, version, revision
20:48.01bzoCotulla: so you think we should just keep model detection in htc_hw?
20:48.10Cotullawhy not?
20:48.11Alex[sp3dev]ok, we can limit htc_hw only to that. other stuff like audio and vibra should be moved out of there
20:48.27Cotullaandroid userspace drivers may need to check which model
20:48.33Cotullalike common led drivers and etc
20:48.49bzoyeah, userland needs model for keyboard map
20:48.50Alex[sp3dev]led drivers should be detected by probing /sys/class/leds
20:48.54bzoright now it is passed with module param
20:48.58Cotullaand it can contains more info
20:49.00Cotullalike model name
20:49.05CotullaRHO TPZ KVS .. etc
20:49.08Cotullarevision
20:49.12Alex[sp3dev]but yes, we need to export model revision to userspace
20:49.16Alex[sp3dev]like, rhod400, rhod200
20:49.18Cotullaversion like RHO300 and RHO100
20:49.28Cotullarevision I mean board version
20:49.45Cotullait may contains size of ram / rom
20:49.48Cotullaalso
20:50.00Cotullabut htc_hw bad name :P maybe hw_info better
20:50.22Alex[sp3dev]Cotulla: sorry, but size of ram is already exported in many places, and rom size - via mtd subsystem. don't go htc way, don't duplicate existing stuff
20:51.42Cotullawhy not
20:51.48Cotullanext version will have new mtd interface
20:51.51Cotullanot compatible
20:51.54Alex[sp3dev]it will not
20:52.00Cotullawhile we will still able to use our own
20:52.15Alex[sp3dev]<PROTECTED>
20:52.16Cotullaas well we can put this values in our own format
20:52.28Alex[sp3dev]but i don't want to argue with you
20:52.36Alex[sp3dev]because it is counter-productive
20:52.57bzoanyways, time to get back to playing with SMI anyways :P
20:53.11Alex[sp3dev]yeah, two times anyways is even more anyways
20:53.13Cotullaown interface <<--- it means it already will be how we want
20:53.29Cotullaand we don't need worry about other things
20:53.35Alex[sp3dev]don't suffer NIH
20:56.31Cotullaat the end it will be easy
20:56.34Cotullajust open read close
20:56.36Cotullaand job done
20:56.58Alex[sp3dev]Cotulla: open /proc/meminfo, read first line - and you get memory size
20:57.07Cotullayeah and parse it
20:57.16Cotullaas well I talk about total memory size
20:57.19Cotullaincluding pmem and etcf
20:57.23Cotullalike 128 256 and etc
20:57.33Alex[sp3dev]why do you need that?
20:58.19Cotullamaybe adjust memory sizes
20:59.14Alex[sp3dev]Cotulla: anyway, userspace can only adjust depending on usable ram size. pmem stuff is fixed.. just don't add any code until you know you need it. never add something you *might* need in future
21:03.20Cotullaheh
21:04.01Alex[sp3dev]what are you working on at the monent?
21:04.14CotullaI am doing homework in MathCad :P
21:04.17*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
21:04.23Cotullawhile RHO charging
21:04.39Alex[sp3dev]which kind of homework? which subject?
21:04.45Cotullasome with matirx
21:04.54Cotullathen I continue with sound or microp
21:05.08Cotullaor will try to run desire sense
21:05.23Alex[sp3dev]doesn't it depend on gles 2.0?
21:05.42Cotulladon't know
21:05.44Cotullayet
21:05.54Cotullabut version from 2.1 worked on 7200 right?
21:06.03Alex[sp3dev]i just think that if it were not, it would have been ported already
21:16.05Cotullahm maybe)
21:16.22Cotullaanyway sound is important part
21:16.43Alex[sp3dev]i will finish keypad and joystick first, and then come to sound
21:30.11*** join/#htc-linux kiozen (~kiozen@rgnb-4d053f3a.pool.mediaWays.net)
21:47.44*** join/#htc-linux JesusFreak316 (~JesusFrea@pool-173-65-106-39.tampfl.fios.verizon.net)
21:50.58*** join/#htc-linux ftoz (~root@cst-prg-96-7.vodafone.cz)
22:02.48*** join/#htc-linux rpierce99 (~rpierce99@71-82-139-28.dhcp.roch.mn.charter.com)
22:28.48*** join/#htc-linux Curious_ (8bb3cffd@gateway/web/freenode/ip.139.179.207.253)
22:28.58Curious_does anyone have experience of "qsub" ?
22:30.46Curious_paralel processing?
22:30.48Curious_anything?
22:30.51Alex[sp3dev]nope
22:33.27*** part/#htc-linux Curious_ (8bb3cffd@gateway/web/freenode/ip.139.179.207.253)
22:37.46*** join/#htc-linux BoTToEsP (~maximo@212.21.250.251.dyn.user.ono.com)
22:47.00*** join/#htc-linux D3tul3 (~Oliver@cpe-174-109-223-235.nc.res.rr.com)
22:56.55*** join/#htc-linux RaiderX (5b6d2a71@gateway/web/freenode/ip.91.109.42.113)
22:57.25*** join/#htc-linux JesusFreak316 (~JesusFrea@pool-173-65-106-39.tampfl.fios.verizon.net)
22:57.34RaiderXhey
23:08.14RaiderXCotulla
23:47.21*** join/#htc-linux siulmagic (~IceChat7@24.54.255.153)
23:49.31*** join/#htc-linux Segnale007 (~Segnale00@host57-255-dynamic.35-79-r.retail.telecomitalia.it)
23:50.04*** part/#htc-linux Cotulla (~opera@nat004-252-205-109.tvoe.tv)

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