IRC log for #htc-linux on 20110120

00:03.32*** join/#htc-linux ftoz (~root@gprs10.vodafone.cz)
00:11.42*** join/#htc-linux phantomcircuit (~phantomci@adsl-69-107-111-94.dsl.pltn13.pacbell.net)
00:11.46*** join/#htc-linux arrrghhh (~arrrghhh@c-71-237-40-111.hsd1.co.comcast.net)
00:28.08*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
00:31.09*** join/#htc-linux kubi1 (~Adium@e176087130.adsl.alicedsl.de)
00:33.58*** join/#htc-linux nineX_ (~nunya@63-252-104-233.ip.mcleodusa.net)
00:48.39*** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com)
01:25.08*** join/#htc-linux Esaa (~Esa@adsl-75-2-216-108.dsl.irvnca.sbcglobal.net)
01:28.04arrrghhhbzo, ping
01:28.37bzowassup?
01:28.55arrrghhhwell i still have a job for one :P
01:29.10bzothat's good right? ;)
01:29.10arrrghhhand i wanted to ask you about that gpio you found that was causing power drain?
01:29.16arrrghhhsomething about keyboard stealing it from bt and cam?
01:29.28arrrghhhlol yes it is a good thing.  i can still afford life :P
01:29.44arrrghhhshit is expensive, let me tell you.
01:30.18bzothe keypad gpio is a problem for the camera, which is fixed in jb's tree
01:30.26bzonot positive about power drain
01:30.31arrrghhhoic
01:30.42arrrghhhso it doesn't apply to the main GIT tree until cam code is committed?
01:31.51bzodoesn't have to wait, but no reason to apply it early unless there is a known positive aside from camera
01:31.58bzowhen I find a spare battery, plan to put in a current shunt to measure directly make questions like this easier to answer
01:33.02arrrghhhsounds like you're going down the path of camro :P
01:33.37bzonah, all I want to know is does a change cause more mA or less mA?
01:33.51arrrghhhhahaha
01:33.54arrrghhhgood info either way.
01:34.11arrrghhhi just don't want you to brick your device :P
01:34.21bzoobserving the battery % draw seems really random sometimes
01:34.27arrrghhhindeed
01:34.39arrrghhhespecially when periphials are running.
01:34.58arrrghhher peripherals
01:35.20bzoI am getting closer to wistilt's reported power though
01:35.48bzoI swapped batteries with a friend and realized that I'm running an 1100mah battery instead of the 1500ma
01:35.50arrrghhhyea, i heard you got almost 45hrs?
01:35.57arrrghhhlmao that'll make a difference.
01:36.28bzowith this battery I'm getting 1.5%/hr, which if it holds up will get me to about 65 hours
01:37.00bzothat's what I get for buying a cheap ebay battery
01:37.24arrrghhhholy crap
01:37.29arrrghhh65 hours?
01:37.32arrrghhhso that's radio on, sync off
01:37.35arrrghhhin sleep
01:37.36arrrghhhyes?
01:37.40bzoy
01:38.03arrrghhhdamn guy, that's amazing.
01:38.38arrrghhhi haven't talked to wistilt2 in a while, but i've seen him pop on now and again.  do you know how his AUO panel work is going?  i'd love to see his full power collapse committed.
01:39.39bzoI think he's trying to figure out the right things to power down on the various devices
01:40.33arrrghhhif only we had 2 more of him, 3 more of you and one dzo.  maybe another acl and jonpry.  this project would be done :P
01:41.14arrrghhhi'm seriously trying to find a way to get dzo a rhod and see if he's willing to lend a hand.
01:41.28arrrghhhi heard he's just recently got gb on the vogue lol
01:42.38bzoI think we're not in too bad of shape actually with JB on board now
01:43.05arrrghhhyea he's been workin his magic on that cam
01:43.14arrrghhhhe even seems close to a test for blackstone guys, which is amazing.
01:43.24*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
01:44.42arrrghhhi was also thinking dzo for his RIL expertise.  i keep thinking that system_server issue is related to netloc.
01:45.07arrrghhhplus, netloc doesn't work for CDMA at all.  speaking of which, how can we start tracing that?  i'd love to track that beast down.
01:45.38bzohaven't looked at it at all
01:46.06arrrghhhhrm.  i'm not even sure where to debug it
01:46.09arrrghhhif it is in the RIL, or what.
01:46.48bzoprobably is. One of the vogue guys passed us the info a long time ago, but no one has looked into it
01:47.17arrrghhhhrm.  i'd love to try to tackle it.
01:47.31arrrghhhi probably won't get anywhere, but if i can get a dev pointed in the right direction at least...
01:47.52bzoyou need to be able to build the ril to get started
01:48.45arrrghhhwell i've got a build enviro setup for the kernel and the system image
01:49.33bzoI've never tried building it, but should use the same tools
01:50.32plupkehttp://linuxtogo.org/~htcpxa/htcartemis/qtopia/   is this project fully dead or replaced by wing linux?
01:51.18bzoarrrghhh: also, another thing you could try is wrapping the htc ril for functions our ril doesn't handle
01:51.23*** join/#htc-linux Daevoq (~IceChat7@host99-98-dynamic.27-79-r.retail.telecomitalia.it)
01:51.29bzothat's what the leo guys did and you could probably crib the code
01:52.50stinebdit actually pretty much drops in for us
01:53.02stinebdi've used their ril wrapper in an xdandroid image
01:53.10arrrghhhi remember playing with that
01:53.16arrrghhhdidn't go so well as i recall :P
01:53.23stinebdcdma choked
01:53.33arrrghhhleo is gsm only
01:53.38stinebdexactly
01:53.44arrrghhhso probably won't help us much.  :(
01:53.57arrrghhhhrm.
01:54.03stinebdi also determined that there was no cdma/gsm android phone at that point
01:54.12stinebdso the ril must not have had support
01:55.52arrrghhhare there any android dual-mode phones now?
01:57.43stinebddont think so
01:58.01bzoarrrghhh: http://forum.xda-developers.com/showthread.php?p=5836166#post5836166
01:58.13bzoinfo on diam cdma, but quite possibly applicable to rhod cdma
01:58.15arrrghhhdamn there's all these rumors of vz getting a android world phone in sept.
01:58.51stinebdthose rumors were strange
01:59.00stinebdit was a 1.2GHz device and i think it was ugly as hell
01:59.02arrrghhhyea and never panned out based on what i'm reading.
01:59.12arrrghhhi've seen pics where it's uglier than sin
01:59.17arrrghhhand others where it's beautiful lol
01:59.28arrrghhhhttp://images.dailytech.com/nimage/16800_htc-android12.jpg
01:59.31arrrghhhgood lookin
01:59.49arrrghhhhttp://images.intomobile.com/wp-content/uploads/2010/08/htc-android-verizon-qwerty.jpg
01:59.51arrrghhhuglier than sin
02:01.36arrrghhhbzo, that info looks amazing.  i can try to integrate it, but it'll probably take me a month.  who built our RIL originally?
02:01.59bzoit originated from the vogue, it even still prints vogue in the log LOL
02:02.07arrrghhhyea i noticed that
02:02.11stinebdphh did it
02:02.11arrrghhhWelcome to Vogue Linux
02:02.28F22the droid 2 global on verizon is both cdma & gsm.
02:02.37stinebdmoto doesn't help us
02:02.41stinebdwe need an htc
02:02.44arrrghhhwas it modified from the vogue, or was it just taken from dzo and slammed in there?  surprised it works at all if it was just thrown in lol
02:03.00stinebdit was modified
02:03.06arrrghhh:P
02:03.07F22verizon & htc need to hurry up and release that merge/incredible hd or whatever they plan on calling it. :P
02:03.27arrrghhhyea, the merge was that rumor back in sept
02:03.36arrrghhhdunno why they're sitting on it, unless it's waiting for lte
02:03.39arrrghhhwhich may screw us.
02:03.47arrrghhhalthough, it still has to be compatible with 3g...
02:04.18arrrghhhsir phh are you around?
02:04.44arrrghhhmonsieur i should say.
02:08.30*** part/#htc-linux kubi1 (~Adium@e176087130.adsl.alicedsl.de)
02:11.52arrrghhhhrm.  well, i'll see what i can dig up on the RIL.
02:16.11*** join/#htc-linux opterz (~AndChat@114.217.174.12)
02:16.32arrrghhh"/* '6'=CDMA-only mode, '3'=GSM-only, '0'=world mode */" <----- world mode?  so is there a built in method to get both radios workin, it just doesn't work in practice...?
02:25.34arrrghhhhrm, trying to do the repo init on the git tree for the RIL, and it's failing.
02:25.47arrrghhhi was doing repo init -u git://gitorious.org/linux-on-qualcomm-s-msm/android-htc-ril.git
02:26.31arrrghhhgives me this "error: revision refs/heads/master in manifests not found"
02:27.35arrrghhhanyone?  bueller?
02:29.30*** join/#htc-linux mastermerlin1 (~Adium@p4FEE5D08.dip.t-dialin.net)
02:56.33*** part/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
02:59.58*** join/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
03:21.22*** join/#htc-linux DuperMan (Duper@109-186-69-206.bb.netvision.net.il)
03:40.18*** join/#htc-linux phantomcircuit (~phantomci@adsl-69-107-111-94.dsl.pltn13.pacbell.net)
03:55.30*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
04:12.51*** join/#htc-linux Termana (~bradley@122.151.118.129)
04:13.18*** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com)
04:19.28*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
04:25.49*** join/#htc-linux Padre (~Padre@intersoft-212.cust.smartspb.net)
04:26.00*** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net)
04:26.35WisTilt2arrrghhh: are you really in here or is this just a ghost?
04:27.06arrrghhhhey hey!
04:27.08WisTilt2[acl]: wake up!! we need to talk panel stuff
04:27.12arrrghhhit is me, in the flesh so to speak.
04:27.21arrrghhhbeen a while man, how you been?
04:27.49WisTilt2busy as all get out.  under the gun to get out device ready for certs
04:27.55WisTilt2out=our
04:28.03arrrghhhah
04:28.16arrrghhhcustomers pressuring you...?
04:28.49WisTilt2no, just that we have a deadline for getting certified and if we miss it we wait another 6 months, not good.
04:29.13WisTilt2so then yes, customers will be whining
04:29.23arrrghhhdamn
04:29.29arrrghhhdidn't realize you had to wait like that
04:29.43arrrghhhi can see why you don't want your radio guy looking at anything non-work related lol
04:29.54arrrghhhwhich, i think we might have a fix for netloc for cdma
04:30.04WisTilt2i think the fcc only has one person working for them now the way they take forever to get things done
04:30.05arrrghhhnot sure if it'lll help with the system_server issue, but i really want netloc :P
04:30.11arrrghhhlol
04:30.36WisTilt2netloc fix?  what was the problem?
04:31.05arrrghhhseems RIL
04:31.17arrrghhhnot even sure if it'll work, but bzo dug up a post for the CDMA DIAM
04:31.25arrrghhhwhich should in theory work for RHOD's RIL as well.
04:33.06WisTilt2i still think the system server issue is ril related so hopefully fixing netloc will surface that cpu problem.
04:33.33arrrghhhyes.  please!
04:33.43arrrghhhwell i'm no RIL expert
04:34.02arrrghhhbut this post definitely is related to the command to pass to the radio to get back LAT&LON
04:34.04WisTilt2btw, i ran my 300 for 5 days straight with no a single problem, lockup, nothing.  only charged it a couple times and averaged under 1% per hour consistently.
04:34.12arrrghhhdid you reboot?
04:34.40arrrghhhi usually get the system_server issue on boot.  i find it doesn't occur once the system is up (and i make that first call to voicemail lol)
04:34.41WisTilt2nope, never rebooted and used it quite a bit except over the weekend.
04:34.46arrrghhhhrm
04:34.54*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
04:35.18WisTilt2that is with my kernel so it has the full panel collapse also
04:35.50F22i've been getting occasional sod's with the git kernel.
04:36.07WisTilt2are you getting system server all the time or just now and then?
04:36.28F22pretty much every time i boot of late.
04:36.55arrrghhhF22, do you ever get it after clearing it on boot?
04:37.08arrrghhhi don't run android for days at a time unfortunately :(
04:37.14F22haven't really checked.
04:37.18arrrghhhbut i have run it for 10+ hrs
04:37.27arrrghhhand i usually never get the system_server issue again, just on boot.
04:38.08WisTilt2F22 when you get sod does kbd backlight still work or is device fully locked up?
04:38.14*** join/#htc-linux ftoz (~root@gprs24.vodafone.cz)
04:38.51F22fully locked. every time it's happened my device was fully asleep.
04:39.00F22no ability to adb in.
04:39.41WisTilt2is led green when locked up or does it happen when it goes amber after you try to wake it up?
04:40.28F22it's generally been connected to the charger so it's always been orange as far as i can recall.
04:40.52F22i suppose i should have qualified that "fully asleep" comment i made earlier.
04:41.14WisTilt2reason i ask is i had one of my techs run some tests last week on that sod and it seems to be happening when coming out of sleep and he thinks it is a problem with one of the clocks
04:41.42F22wouldn't be surprised at all, i don't recall seeing sod's on my handset before the clock update.
04:41.59arrrghhhWisTilt2, i've had SoD's when doing wifi tethering.  no kbd backlight, no adb... but for whatever reason the WAP stays up lol
04:42.26WisTilt2i looked into it a bit and i think there is a timing problem when one of the clocks are fired up during wakeup.
04:44.19WisTilt2i think there is a delay missing that allows the clocks to stabilize but havent gone through all the logic yet
04:44.52WisTilt2arrrghhh: so it happens even if its not in sleep?
04:45.15F22makes sense, i haven't had it happen to me while my handset was awake.  my panel has always been asleep.
04:45.36arrrghhhWisTilt2, seems to be
04:45.51arrrghhhyea the panel was off, but the phone wasn't sleeping
04:46.04*** join/#htc-linux st3alth (~ghosh@125.162.37.163)
04:46.25WisTilt2i know on the panel power up sequence it requires a minimum of 120ms after power on before you can send commands to any of the registers so clock pll's would be similar
04:47.04arrrghhhwell i'm glad you know that :P
04:47.18WisTilt2i know this problem was way before bzo fixed the pll's for sleep mode 1 so im leaning towards clocks
04:48.18WisTilt2what date was alex's clocks pushed?
04:50.58arrrghhhi uh... am not sure.
04:51.05arrrghhhlooking at git now, not jumping out at me.
04:51.52WisTilt2F22 did you happen to map and document the scan codes for all the buttons when you were messing with the kbd mapping awhile back?
04:52.27F22pretty much.
04:52.52WisTilt2do you have the mute button and ptt by chance?
04:52.57F22lol, i do.
04:53.55F22i'll be releasing a new test rootfs tomorrow with updated keymaps/layouts for all rhodiums.  but i can give you those now if you like.
04:54.43arrrghhhWisTilt2, found it.  12/23
04:55.14arrrghhhperipherals
04:55.16arrrghhher
04:55.23arrrghhhhttp://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/d15a722704763a5c797f4f9400454fd64477b549
04:55.37F22key 102   REAR_MUTE        WAKE_DROPPED
04:55.37F22key 212   CAMERA            WAKE_DROPPED     # Push To Talk
04:55.52F22both microp
04:56.06*** join/#htc-linux Elmstrom_ (~quassel@4807ds1-arno.0.fullrate.dk)
04:56.54WisTilt2ok thanks.  going to try and set one of those up for a hard hook that can hopefully run while in this locked up state.  wont be back on this until friday night though.
04:57.29arrrghhhWisTilt2, i forgive you so long as you have a test kernel for me next time :P
04:57.31WisTilt2arrrghhh:  well that was well after the system server issue appeared so maybe clocks arent where we need to be looking.
04:57.47arrrghhhhow long has been the system_server issue been around for?
04:57.54arrrghhha lot of poeples have been pointing at frx03...
04:58.12WisTilt2im thinking it was back early october or late september
04:58.28arrrghhhhrm.  that wouldn't be frx03.
04:58.37WisTilt2seems to be more prevalent the past couple months though.
04:58.41arrrghhhmaybe it was around when you guys got netloc :P lol
04:58.58arrrghhhyea, it definitely has gotten worse.
04:59.57WisTilt2F22 is your rootfs the same as the 11/15 one just with keymap changes?
05:02.11WisTilt2arrrghhh i dont remember if i asked or told you this but whenever the system server happens, if you look in your dmesg you should see a kernel divide by zero error right after some ril output.
05:02.23F2211/15 remapped end to home. 11/22 made it a command line option in startup.txt, ie. b4=home
05:03.20F22most everything since has been keymap changes, although there may some minor layout mods. i'd have to check the changelog.
05:03.44F22i think i added in rear_mute after 11/22
05:03.56WisTilt2so end is home by default now?  nice, i have been changing that in spare parts.
05:04.14*** join/#htc-linux Kasjopaja23 (~Tina@p578FFC66.dip.t-dialin.net)
05:04.26WisTilt2arrrghhh: problem was way before frx03 for sure.
05:04.33F22yes, and long press gives you the recent apps list.
05:04.40arrrghhhk
05:05.01arrrghhhif you're sure it was before frx03, it was definitely before the clock commit
05:06.20F22ok is ctrl. sym pops up the symbol palette. It's pretty minimal, but it will grow some once frx04 gets released.
05:06.59arrrghhhi'm sure that moniker is reserved for gb :P
05:07.34WisTilt2im positive it was before frx03.  im thinking i first started seeing it a couple weeks before i committed the autobl code and thought it was something in my code.  happened prior to that and that was committed sometime back in oct.
05:08.02WisTilt2F22: nice changes:)
05:08.11*** join/#htc-linux dharvey4651 (~dharvey46@c-69-254-236-232.hsd1.ks.comcast.net)
05:08.14WisTilt2ctrl is real nice
05:08.30F22i know for a fact that the system_server problem occurred before frx03.
05:08.31arrrghhhWisTilt2, there was a ton of battery maddness is oct...
05:08.48F22it bit me a number of times.
05:08.55F22much less common back then though.
05:09.07arrrghhhindeed
05:10.09WisTilt2my initial thought was something in camros battery code but i never pursued it
05:10.15F2211/15 and 11/22 both have ctrl. so that one hasn't changed. i put together a spreadsheet for all the new keys across 9 different keyboards which i'm about to release. keeping them all in my head was becoming daunting...
05:10.53F22http://www.mediafire.com/download.php?8kmaduk5usv3pnn
05:11.54F22i still can't believe the italian keyboard didn't have a ? on it... don't italians ask questions too? :P
05:12.35arrrghhhseriously?
05:12.43arrrghhhi thought it was lame that the 400 doesn't have a ctrl key lol
05:12.49F22totally.
05:13.16*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:13.24F22yes, the 400 has a combined sms/mms key instead.
05:13.51WisTilt2300 doesnt have ctrl key either
05:14.01F22nope, 300 has an ok key instead.
05:14.05F22mapped it to ok.
05:14.30WisTilt2i wonder how people that designed these devices function in their real life
05:14.40arrrghhhlol
05:14.44arrrghhhdisjointedly?
05:15.14F22btw, search is the shortcut key, that's been mapped to envelope. so for example, search+b opens up the browser, search+g opens up gmail, etc... they are user assignable/reassignable
05:15.39arrrghhhhow?
05:15.49*** join/#htc-linux phantomcircuit (~phantomci@adsl-69-107-111-94.dsl.pltn13.pacbell.net)
05:15.51arrrghhhas in, what interface does the user change them thru?
05:16.01WisTilt2voice commands:)
05:16.19arrrghhhlol
05:16.29arrrghhhright, that's how google does everything now :P
05:16.59F22settings>application settings>quick launch
05:17.15F22that will also tell you what they're all set to, as well as allow you to change them.
05:17.47arrrghhhoO why haven't you committed this yet?!?! :P
05:18.39arrrghhhi know, you had the plethora of rhod100's to sift thru.
05:19.19F22yes, the 100's were a bit of a pain to get some agreement on what keys should go where.
05:19.27F22from the native speakers.
05:19.46F22i got also distracted by other things. :-[
05:20.11arrrghhhhaha i'm just givin you guff
05:20.25arrrghhhi have yet to do anything useful, don't sweat it ;)
05:20.31F22lol
05:20.41*** join/#htc-linux cazh_ (~quassel@3007ds2-rd.0.fullrate.dk)
05:20.55*** join/#htc-linux Rexid (bestirc@vpn-91-211-19-103.didan.com.ua)
05:24.04arrrghhhF22, has that guy tried a different SD card?
05:24.13F22which guy?
05:24.14arrrghhhit almost looks like his SD is having issues in his dmesg
05:24.21arrrghhhy'know
05:24.22arrrghhhthat guy
05:24.25F22lol
05:24.27F22oh, him.
05:24.30arrrghhhhighlandsun
05:24.32F22no idea.
05:24.37arrrghhhyea him lol
05:24.50*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:25.07arrrghhh[   19.265106] mmcblk0: error -110 transferring data
05:25.14arrrghhh[   19.482788] mmc1: Data timeout
05:25.28arrrghhh[   19.491149] end_request: I/O error, dev mmcblk0, sector 5966096
05:25.36F22oh, hmm....could be another clock issue too...
05:25.43arrrghhhoh right
05:25.45arrrghhhthat too..
05:25.58arrrghhhi thought he said he tried that tho.... perhaps not.
05:26.03*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:26.07arrrghhhtoo many peoples & associated problems.
05:26.11F22quite a few people have sd cards that suddenly stopped working after that clock update.
05:26.17arrrghhhyea, i remember.
05:26.46F22clock update was i think 1245. didn't he say that nothing after 1232 worked for him?
05:27.27*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:27.48arrrghhhyea 1232 looks like the last kernel he was able to boot
05:28.52*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:29.17F22so yes, assuming he actually tried kernels between 1232 and 1245, then it's not the new clocks.
05:29.59F22so your suggestions sounds good.
05:30.04arrrghhhyea, and those guys with clock issues it would always say "Waiting for SD" AFAIK
05:30.09F22yup
05:30.24arrrghhhi'll post mah suggestion.
05:30.24F22although with his engineering sample hardware, who knows...
05:30.31arrrghhhindeed
05:30.33F22i've never seen a 210 with an auo panel before...
05:30.36*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:30.42arrrghhhvery odd indeed
05:31.20arrrghhhSamsunguy, no matter how many nicks you have in here, i still don't want a samsung phone.  or metropcs service.
05:31.20F22sounds good (on posting your suggestion)
05:31.32F22lol
05:32.06*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:32.45*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
05:33.32*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:35.17*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:42.12arrrghhhah well.  bedtime.  cya guys later.
05:42.35WisTilt2nite arrrghhh, im about to do the same.  back on friday night.
05:43.37F22g'nite arrrghhh
05:44.46WisTilt2F22 did you happen to try tiad8's froyox system.ext2?  dont know wth he did in there but my phone acted like it was on steroids, went into sleep in less than 1 second and everything was fast.  did get lots of lockups though so went back to frx03.
05:45.30*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:45.55F22nope, haven't tried it. i believe he's using git though, and we know that exascerbates the system_server problem while theoretically increasing speed.
05:46.03F22er jit
05:46.46*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:46.48F22errrgggh...i mean removing it made the system_server problem a lot worse while reducing the frequency of crashes significantly.
05:46.50WisTilt2its damn fast whatever he did.  gps lock was within seconds and data was so much faster.
05:47.25F22interesting. gps was always slow for us.
05:48.15*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:48.17WisTilt2i tested it with that market app called gps test and i got 9 sats within about 10-15 secs.  normal is a couple minutes.
05:48.37F22i know exactly what you mean by the couple of minutes...
05:48.51F2210-15 secs is impressive.
05:49.30WisTilt2yeah it is.  i couldnt believe how much fast data was and just navigating apps was noticeably quicker.
05:49.35F22i've grown used to updating quickgps all the time in winmo before hitting android.
05:49.49*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:50.10F22so it's probably more than just the jit, unless he's got some magical new jit we never saw. lol.
05:50.43*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:51.53*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
05:52.07*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:52.13F22i'll see about it giving it a try and see what's different. maybe there's something we can pull from his build that won't come with more crashes.
05:53.19WisTilt2i ran his system image with the standard 11/15 rootfs and my kernel so all his magic is in the system file alone.
05:53.35*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
05:53.53WisTilt2he took out userland autobl though which is a bummer.  i have my kernel autobl forced on though:)
05:54.02F22lol
05:55.36WisTilt2well ill catch ya later.  crazy day tomorrow so ill be back on here friday night to do some coding.  thanks for the button info.
05:55.56F22no prob. have a good night. see you friday
05:56.33WisTilt2[acl]: if you read this, ping me friday night if you can so we discuss a couple things in panel power.
06:04.56*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:06.09*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:07.39*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:09.06*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:10.18*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:12.25*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:13.57*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:15.38*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:26.01*** join/#htc-linux WP7InLoved (af8a416f@gateway/web/freenode/ip.175.138.65.111)
06:28.28*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:29.44*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:32.18*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:34.14*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
06:34.18*** join/#htc-linux DuperMan (Duper@109-186-69-206.bb.netvision.net.il)
06:42.33*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:43.52*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:44.54*** join/#htc-linux DuperMan (Duper@109-186-69-206.bb.netvision.net.il)
06:45.49*** join/#htc-linux plupke_ (~chatzilla@94-21-146-35.pool.digikabel.hu)
06:46.31*** join/#htc-linux ViLkA (ViLkA@87.110.169.93)
06:47.53*** join/#htc-linux rzk (~rzk@daemonet.ru)
06:48.16*** join/#htc-linux phantomcircuit (~phantomci@adsl-99-37-227-106.dsl.pltn13.sbcglobal.net)
06:52.02*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
06:55.11*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:56.26*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
06:57.58*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:01.07*** join/#htc-linux DuperMan (Duper@109-186-69-206.bb.netvision.net.il)
07:05.21*** join/#htc-linux Termana (~bradley@122.151.112.132)
07:08.46*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@82.76.238.105)
07:09.40*** join/#htc-linux kiozen (~kiozen@p5DDF2152.dip.t-dialin.net)
07:11.02*** join/#htc-linux hardwalker (~hardwalke@122-117-211-193.HINET-IP.hinet.net)
07:28.01*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:34.11*** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com)
07:38.12*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:39.32*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:42.08*** join/#htc-linux rob_w (~bob@ppp-188-174-104-149.dynamic.mnet-online.de)
07:42.09*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:51.52*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
07:53.21*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:55.57*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:57.26*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:58.57*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
07:59.05*** join/#htc-linux MacDrunk (~marper@201.164.175.17)
08:00.30*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
08:01.54*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
08:03.27*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
08:10.37*** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com)
08:11.34*** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com)
08:12.54*** join/#htc-linux mitsutaka (~mitsutaka@rt.miraclelinux.com)
08:13.42*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
08:21.49*** join/#htc-linux CazH (~quassel@3007ds2-rd.0.fullrate.dk)
08:33.54*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
08:38.37*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@82.76.238.105)
08:56.08*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:08.32*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:09.49*** join/#htc-linux arif-ali (~arif-ali@ip-81-23-53-226.ask4internet.com)
09:10.53*** join/#htc-linux BazGee2 (ident@cpc1-sund2-0-0-cust716.11-1.cable.virginmedia.com)
09:14.26*** join/#htc-linux Phally (~Phally@d28072.upc-d.chello.nl)
09:14.53*** join/#htc-linux Phally (~Phally@d28072.upc-d.chello.nl)
09:15.43*** join/#htc-linux Phally (~Phally@d28072.upc-d.chello.nl)
09:16.47*** join/#htc-linux darkhost (~darkhost1@178.137.12.110)
09:19.05*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@82.76.236.168)
09:20.53*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:35.07*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:36.05*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:37.39*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:39.15*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:43.08*** join/#htc-linux DuperMan (Duper@89-139-26-178.bb.netvision.net.il)
09:48.19*** join/#htc-linux shaq (c2aba2e1@gateway/web/freenode/ip.194.171.162.225)
09:48.22shaqHi
09:48.26shaqAnybody here?
09:48.48*** join/#htc-linux netson-ubuntu (~netson-ub@202.159.118.21)
09:49.01shaq..
09:51.16*** join/#htc-linux s (c2aba2e1@gateway/web/freenode/ip.194.171.162.225)
09:51.32*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:52.21*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:53.22*** part/#htc-linux Guest29884 (c2aba2e1@gateway/web/freenode/ip.194.171.162.225)
09:53.51*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
09:54.39*** join/#htc-linux kvaster (~kvaster@93.84.112.80)
09:56.47*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:00.20*** join/#htc-linux ViLkA (ViLkA@87.110.169.93)
10:00.24*** join/#htc-linux ViLkA (ViLkA@87.110.169.93)
10:02.10*** join/#htc-linux dareios (dareios@io.netbsd.org.pl)
10:06.07*** join/#htc-linux DaveZworka (~DaveZwork@ip-79-175-195-101.cable.smsnet.pl)
10:07.47*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:08.25*** join/#htc-linux rex (~quassel@ks31382.kimsufi.com)
10:10.30*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:12.08*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:13.41*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:17.53*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@82.76.236.54)
10:28.41*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:39.58*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:41.16*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:43.59*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:45.42*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:47.05*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
10:49.45*** join/#htc-linux Cees_heim (~Cees@p508DE04D.dip.t-dialin.net)
10:52.39*** join/#htc-linux Korand (~kvirc@port-150-adslby-pool45.infonet.by)
10:58.02*** join/#htc-linux dekar_ (~dekar@drms-590ce611.pool.mediaWays.net)
11:02.06*** join/#htc-linux a (b40b8ee3@gateway/web/freenode/ip.180.11.142.227)
11:08.48*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:15.23*** join/#htc-linux goxboxlive (~jrs@mail2.hjellnesconsult.no)
11:23.13*** join/#htc-linux Rob2222 (~Miranda@p4FFF2D93.dip.t-dialin.net)
11:28.59*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:31.58*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:34.57*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:35.11*** join/#htc-linux RaiderX (5b6e440c@gateway/web/freenode/ip.91.110.68.12)
11:37.39*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:38.44*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:40.38*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:52.09*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:53.29*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
11:55.14plupkehow commen is the problem of breaking of the usb port of the phones?
11:58.04*** join/#htc-linux arif-ali (~arif-ali@ip-81-23-53-226.ask4internet.com)
12:01.41*** join/#htc-linux akirax (akirax@181.Red-95-120-236.dynamicIP.rima-tde.net)
12:03.40*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:05.58*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:06.56*** join/#htc-linux eR^zeRa` (~zzeratul@88.103.98.168)
12:16.12*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:17.35*** join/#htc-linux Samsungu_ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:26.34*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
12:27.43*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:38.02*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
12:38.12*** join/#htc-linux kubi1 (~Adium@e176085055.adsl.alicedsl.de)
12:43.46*** part/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
12:47.41*** join/#htc-linux LordDeath (~Lord|Lapt@cable-81-173-164-173.netcologne.de)
12:53.15*** join/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
12:58.14*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
13:14.55*** join/#htc-linux ViLkA (ViLkA@87.110.169.93)
13:15.50*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
13:18.33*** join/#htc-linux Samsung__ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
13:20.10*** join/#htc-linux Samsun___ (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
13:21.44*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
13:40.13*** join/#htc-linux ocm (~ocm@200.34.14.6)
13:42.25*** join/#htc-linux ramconsole (~kmsg@108.109.133.168)
13:46.21*** join/#htc-linux Samsunguy (~Samsunguy@65.120.149.2)
14:03.43*** join/#htc-linux cheongsiu (~cheongsiu@112.95.15.154)
14:07.33*** join/#htc-linux Rexid (bestirc@vpn-178-217-163-71.didan.com.ua)
14:10.39*** join/#htc-linux Samsunguy (~Samsunguy@65.120.149.2)
14:24.11*** join/#htc-linux GNUtoo|laptop (~gnutoo@host19-55-dynamic.180-80-r.retail.telecomitalia.it)
14:25.11*** join/#htc-linux Markinus (~Miranda@212.255.26.108)
14:52.35*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
14:53.12*** join/#htc-linux netson-ubuntu (~netson-ub@125.161.202.247)
15:02.39*** join/#htc-linux Pr0z (~Proz@bzq-84-109-109-248.red.bezeqint.net)
15:16.52*** join/#htc-linux stickman89 (~stickman8@5e064b67.bb.sky.com)
15:17.02stickman89hello world
15:18.24stickman89is there an issue with the Eclair RIL by any chance? Unable to hear the caller until you toggle loudspeaker.
15:19.05*** join/#htc-linux ZESD (51c0ee74@gateway/web/freenode/ip.81.192.238.116)
15:29.34*** join/#htc-linux stickman89 (~stickman8@5e064b67.bb.sky.com)
15:43.20*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
15:45.45*** join/#htc-linux BbLugNut (~kvirc@184-213-107-86.pools.spcsdns.net)
15:56.43*** join/#htc-linux Kasjopaja (~Tina@p578FFC66.dip.t-dialin.net)
15:59.03*** join/#htc-linux vw (4463eeec@gateway/web/freenode/ip.68.99.238.236)
16:02.21*** join/#htc-linux vw (4463eeec@gateway/web/freenode/ip.68.99.238.236)
16:03.16*** join/#htc-linux noobhands (~noobhands@cpc2-hitc6-2-0-cust335.9-2.cable.virginmedia.com)
16:05.47*** join/#htc-linux [acl] (~abel@96.246.167.90)
16:07.23*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@82.76.236.54)
16:09.59*** part/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
16:13.31*** join/#htc-linux MN_ (568624fa@gateway/web/freenode/ip.86.134.36.250)
16:16.09*** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp)
16:20.45*** join/#htc-linux imilka (~kvirc@95-25-221-167.broadband.corbina.ru)
16:24.21*** join/#htc-linux Samsunguy (~Samsunguy@65.120.149.2)
16:24.33*** join/#htc-linux dan1j3l (~quassel@93-138-40-141.adsl.net.t-com.hr)
16:27.13*** join/#htc-linux Arash18k (~Arash18k@94.182.77.198)
16:27.59*** join/#htc-linux Samsunguy (~Samsunguy@65.120.149.2)
16:36.08*** join/#htc-linux b4d4 (~b4d4@did75-20-88-183-32-95.fbx.proxad.net)
16:40.27*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
16:45.44*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
16:54.02*** join/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
16:56.39*** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@89.32.146.153)
17:06.04*** join/#htc-linux rob_w (~bob@ppp-188-174-104-149.dynamic.mnet-online.de)
17:22.51*** join/#htc-linux toastcfh (~toastcfh@29-37.200-68.tampabay.res.rr.com)
17:28.35*** join/#htc-linux |Jeroen| (~jeroen@d5152B6A8.access.telenet.be)
17:28.36*** join/#htc-linux kubi1 (~Adium@e176085055.adsl.alicedsl.de)
17:29.43*** join/#htc-linux kubi2 (~Adium@e176085055.adsl.alicedsl.de)
17:29.51*** join/#htc-linux kubi1 (~Adium@e176085055.adsl.alicedsl.de)
17:33.48*** join/#htc-linux avinashhm (~avinash-h@192.163.20.231)
17:59.52*** join/#htc-linux Baeen1 (~Bane@ppp59-167-201-55.static.internode.on.net)
18:05.12*** join/#htc-linux rex (~quassel@ks31382.kimsufi.com)
18:12.31*** join/#htc-linux kiozen (~kiozen@rgnb-5d879acc.pool.mediaWays.net)
18:35.21*** join/#htc-linux r3dg4r (45e805f9@gateway/web/freenode/ip.69.232.5.249)
18:37.21*** part/#htc-linux Arash18k (~Arash18k@94.182.77.198)
18:40.33*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
18:46.47*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
18:58.06*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
19:10.14*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
19:10.43*** join/#htc-linux gauner1986 (~Miranda@p508C7F3A.dip.t-dialin.net)
19:10.54gauner1986hi guys
19:13.53crawlinghey gauner1986
19:14.24crawlingyou probably notice, but, did you see diem "fix" for your gps? it works flawless now (from the user reports)
19:14.38crawlingmaybe you can update your thread with that, or not. ^^
19:15.38gauner1986nope, didnt have much time :)
19:15.46gauner1986and whats that "fix"?
19:16.13crawlingusing native bravo files mixing it up with yours. wait a sec, i'll link it
19:18.05crawlinghttp://forum.xda-developers.com/showpost.php?p=10636518&postcount=125
19:18.08crawlingfound it :)
19:18.51gauner1986thx
19:19.48crawlingnp. altho i don't use the gps, im the one saying thanks for your coding work
19:20.32crawlingwith that from diem, gps no longer drops and the fix is way faster (at least, thats what the users claim)
19:34.43*** join/#htc-linux dusko_m (~dusko_m@93-86-167-113.dynamic.isp.telekom.rs)
19:39.00*** join/#htc-linux Pr0z (Proz@bzq-84-109-109-248.red.bezeqint.net)
19:52.31*** join/#htc-linux Pr0z (~Proz@bzq-84-109-109-248.red.bezeqint.net)
19:57.07*** part/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
20:02.03*** join/#htc-linux mastermerlin (~Adium@p4FEE5D08.dip.t-dialin.net)
20:11.57*** join/#htc-linux BbLugNut|2 (~kvirc@108.109.216.45)
20:14.40*** join/#htc-linux eugenb (~Adium@dslb-188-100-185-008.pools.arcor-ip.net)
20:20.28*** join/#htc-linux Pr0z (~Proz@bzq-84-109-109-248.red.bezeqint.net)
20:20.49*** join/#htc-linux bascore (5a010666@gateway/web/freenode/ip.90.1.6.102)
20:23.57*** part/#htc-linux dusko_m (~dusko_m@93-86-167-113.dynamic.isp.telekom.rs)
20:26.19*** join/#htc-linux L_miller (~Lmiller17@68-115-50-78.dhcp.eucl.wi.charter.com)
20:36.45*** join/#htc-linux Pr0z (~Proz@bzq-84-109-109-248.red.bezeqint.net)
20:39.59*** join/#htc-linux Ciochy (Ciochy@188.24.22.196)
20:45.15*** join/#htc-linux Pr0z (~Proz@bzq-84-109-109-248.red.bezeqint.net)
20:50.00F22[acl]: how goes?
20:51.24[acl]F22: it just goes bro.. it just does
20:51.55[acl]F22: sup with you ? still being fake glemsom ?
20:52.27F22lol, real f22, actually.  :P
20:53.11F22although, i'll be happy to let glemsom have it back so i can redirect the time to other projects.
20:53.40[acl]not sure when he will make his return
20:53.57F22i don't think glemsom was quite so involved in user triage.
20:54.34F22speaking of which, i have an odd report regarding the framebuffer upgrade.
20:56.07[acl]report? explain
20:56.48F22apparently his rhodium has been hanging ever since commit #1233, which is the one where you upgraded the fb to .35.  he's pretty sharp too, so i think he's for real. his device however is a bit odd...it's a 210, but an engineering sample, and it has an auo panel unlike all the other 210's we've encountered.
20:57.14F22he's managed to post a dmesg and logcat.
20:57.19[acl]where at?
20:57.32F22xda, grabbing the link for you...
20:58.13F22http://forum.xda-developers.com/showpost.php?p=10750600&postcount=488 <--- this post and onward should be good to read.
20:58.39F22convo goes back earlier than that, but the earlier stuff isn't really needed.
20:58.50[acl]weird. This is all sd card related
20:59.33F22well, arrrghhh pointed the sd card stuff out, but apparently it isn't what's hanging his device.
20:59.37F22keep reading
21:00.31F22post 493 has the dmesg and logcat
21:00.58F22last thing in logcat was: E/SurfaceFlinger( 1272): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake
21:01.44F22and in dmesg, we have 2 kernel oopses, and then lots of [  197.669555] msmfb_pan_display timeout waiting for frame start, 263824 263824
21:02.06[acl]ooo
21:02.27[acl]pan display timeout is evil but thats the error itself not the root cause
21:02.28[acl]need more logs
21:02.44[acl]or a way to replicate it
21:04.06[acl]oo i see the full dmesg now
21:05.20*** join/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
21:08.45[acl]F22: so you are sure this happened on the FB commit ? weird because the error has sound crap too.
21:08.54F22i saw.
21:09.59F22fb commit was 1233. yes. he's pretty adamant that 1232 (fps2d) works fine, but 1233 and later don't. and he sound rather savvy.
21:10.17[acl]ok.. thats all i need. ill reply back and look into it
21:10.59F22cool bro.
21:13.30[acl]F22: this dmesg looks different. Are you using a custom defconfig ? or the default one? or maybe i never payed attention to alsa being enabled
21:17.08*** join/#htc-linux Jbruneaux (4dc14439@gateway/web/freenode/ip.77.193.68.57)
21:24.43F22[acl]: i'm using the default defconfig.  but some people get their kernels from pixelwattstudios instead.  not sure if that one uses the default or a custom one.
21:25.45[acl]ahh ic
21:26.00[acl]ok, well we need to find out.
21:26.27[acl]ill ask
21:27.56F22ok
21:28.30[acl]F22: cant support custom kernels you know.. whole reason why we try to have autobuild. If you roll your own shit.. you better know what ur doing
21:28.49stinebdwell that leaves me out
21:28.58F22lol
21:30.47F22[acl]: yes, it adds to the variables we have to deal with, and thus makes troubleshooting potentially more complicated.
21:31.51[acl]F22: well the solution is simple actually.. just support your own stuff. :-)
21:32.20[acl]stinebd: bro peeps keep hounding me for this gralloc and lib. can i tell em you dont want to so its all on you ? :-p
21:32.30F22lol, problem is that he's using the same naming scheme i am. i was thinking about tacking an f22 or something on to my builds to distinguish them.
21:32.38stinebd[acl]: i don't want to what?
21:33.13F22i thought stinebd was ok with it, but we're waiting on the camera lib.
21:33.44[acl]stinebd: the gralloc and lib .. for wvga.. you remember
21:34.12stinebdi don't remember saying i wouldn't do something though
21:34.24stinebdi just can't test any of it
21:35.04*** join/#htc-linux NetRipper (~netripper@tikkie.net)
21:35.13stinebdif you give me stuff that works on rhod, i can test it to make sure it doesn't break others and push it
21:35.19[acl]stinebd: i'll have arggg hunt you down. Its only for wvga devices. So its your call if you want to deploy for all or just wvga
21:35.34*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
21:35.38[acl]stinebd: doesnt break raph since i have a raph.. so i can say that with confidence
21:47.44F22stinebd: http://www.mediafire.com/download.php?m856j1itzaapkt4  <--- ACL's libGLES_qcom.so
21:48.19F22stinebd: http://www.mediafire.com/download.php?xyncdi181abkyu4 <--- ACL's gralloc.msm7k.so
21:49.18[acl]F22: are these the good versions i take it? i released like 3 i think ..lol..
21:49.34stinebdto recap gralloc...
21:49.35[acl]well stinebd can make his own gralloc.. if he wants. it came from his source.
21:49.40stinebdALLOCATORREGION_RESERVED_SIZE = ?
21:49.43[acl]yup
21:49.48stinebd3600?
21:50.01[acl]i forgot the math.. 800x400x4x2 i think ?
21:50.11[acl]its on the logs .. let me check
21:50.52[acl]stinebd: (800x480x4x2) = 3000<<10
21:50.55F22[ACL}: lol, yes, those are the good versions, i distinguish them by date to keep them straight. 11/29 libGLES & 11/30 gralloc. your 11/29 gralloc was terrible. ;)
21:50.58stinebdok
21:51.23[acl]F22: it was a math error.. :-p .. as you can see above, i dont remeber the numbers at times
21:52.21[acl]stinebd: gles was modded to match that.
21:52.22F22lol, we'll keep you anyway.
21:52.37stinebd[acl]: understood
21:52.46stinebdi remember how it all happened, just never got the final figures
21:53.01[acl]F22: thanks.. now i feel accepted by the community
21:54.04stinebdfor frx04 i'll push that and look at the copybit speedup that i found for ginger, see if it applies to froyo too
21:54.26*** join/#htc-linux gauner1986 (~Miranda@p508C7F3A.dip.t-dialin.net)
21:54.29F22your work is much appreciated, as is stinebd's for that matter. i'm all for speedups. :D
21:55.11[acl]stinebd: sounds sexy..
21:55.39[acl]stinebd: question for you. Since the ginger launhcer is open. is the GL portion included in the source? or did google keep that for their own devices ?
21:56.03stinebd[acl]: it's included. iirc that part is all done in renderscript which we can't use
21:56.22stinebdogles2.0+ only
21:56.43[acl]fawk.. yeah i remember now
21:56.55[acl]render script
22:10.04*** join/#htc-linux RaiderX (5b6e440c@gateway/web/freenode/ip.91.110.68.12)
22:22.15*** join/#htc-linux F-D (~F-D@92.30.74.240)
22:24.25*** join/#htc-linux Markinus (~Miranda@212.255.26.108)
22:25.08*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
22:25.48*** part/#htc-linux smoku (~spectrum@xkh0g2.infr.xiaoka.com)
22:27.00*** join/#htc-linux Pr0z (Proz@bzq-84-109-109-248.red.bezeqint.net)
22:29.30*** join/#htc-linux Tinyboom (~nahh@194.84-48-106.nextgentel.com)
22:30.03*** join/#htc-linux Rexid (bestirc@vpn-91-211-19-7.didan.com.ua)
22:40.56*** join/#htc-linux g3rm (~germo@89-72-100-169.dynamic.chello.pl)
22:45.01*** join/#htc-linux Dave_Alternative (DaveZworka@ip-79-175-248-187.cable.smsnet.pl)
22:51.43*** join/#htc-linux EdLin (~EdLin@securabit/listener/edlin)
22:56.40*** join/#htc-linux ElFinLazz (~elfinlazz@112.154.189.103)
23:03.49*** join/#htc-linux Samsunugy_ (4cba3228@gateway/web/freenode/ip.76.186.50.40)
23:04.15*** join/#htc-linux Untouchab1e (~Untouchab@cm-84.215.29.184.getinternet.no)
23:07.36*** join/#htc-linux Wally__ (~wally@c-75-73-178-169.hsd1.mn.comcast.net)
23:15.51*** join/#htc-linux BabelO (~fcr@AMontpellier-554-1-93-112.w92-145.abo.wanadoo.fr)
23:15.51*** join/#htc-linux BabelO (~fcr@unaffiliated/babelo)
23:17.46*** join/#htc-linux furtardo (~mks@nat/yahoo/x-zhawicwmjpneleap)
23:18.51*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
23:22.59*** join/#htc-linux Samsunguy (~Samsunguy@cpe-76-186-50-40.tx.res.rr.com)
23:28.26*** join/#htc-linux Untouchab1e (~Untouchab@cm-84.215.29.184.getinternet.no)
23:32.00*** join/#htc-linux Pr0z (Proz@bzq-84-109-109-248.red.bezeqint.net)
23:32.43*** join/#htc-linux BabelO (~fcr@AMontpellier-554-1-6-38.w83-197.abo.wanadoo.fr)
23:32.43*** join/#htc-linux BabelO (~fcr@unaffiliated/babelo)
23:42.24*** join/#htc-linux Pr0z (Proz@bzq-84-109-109-248.red.bezeqint.net)
23:53.56*** join/#htc-linux Rexid (bestirc@vpn-91-211-19-7.didan.com.ua)
23:57.06*** join/#htc-linux nineX_ (~nunya@216-43-173-182.ip.mcleodusa.net)

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