Friday, 2011-11-18

arrrghhhstinebd, you thar?00:28
arrrghhhwondering what rootfs to use00:28
arrrghhhor kernel for that matter00:33
arrrghhhnot even sure where i can dig up a .27 acoustic kernel... hrm...00:33
*** rpierce99 has quit IRC00:52
*** ^Tempest_ is now known as ^Tempest01:12
*** vinceweis_ has quit IRC01:44
*** d3tul3 has quit IRC01:50
*** kalemas has joined #xdandroid02:27
*** kalemas has left #xdandroid03:32
*** babijoee has joined #xdandroid05:20
*** hardwalker has quit IRC05:29
*** babijoee has quit IRC05:33
*** helicopter88 has joined #xdandroid06:49
*** fishhead2567 has joined #xdandroid09:15
*** helicopter88_1 has joined #xdandroid09:30
*** helicopter88 has quit IRC09:31
*** helicopter88_1 is now known as helicopter8809:43
*** rpierce99 has joined #xdandroid09:46
*** rpierce99 has quit IRC09:49
*** rpierce99 has joined #xdandroid09:52
*** helicopter88 has quit IRC09:57
*** kalemas has joined #xdandroid10:02
*** mgross029 has joined #xdandroid10:06
*** emwe has joined #xdandroid10:11
emwerpierce99: detule: the rootfs-unsecure i reference is just for pita-less adb debugging. superuser has been fixed to build with a specific (gp-api-compatible) revision a while ago.10:12
detuleemwe, quick question10:13
rpierce99awesome, thanks I must have missed that discussion10:13
detulepmem_gpu0 no longer needed?10:13
emwedetule: uh? wasn't that for framebuffer memory?10:13
emweand gpu1 for 3d? long time ago...10:13
emwerpierce99: don't ask how much i miss these times. i always have to reask because i forget in between ...10:14
emwemust be the age.10:14
detuleno idea but i don't see you registering those devices in .35, and the regions they are declared in pmem.c overlap hw3d device10:14
emweoh now let me go lock. pmem.c is quite comparable to the .27 one. i just cleaned up some defintion stuff at the top iirc.10:15
emwepmem_setting.pmem_gpu0_start=MSM_SMI_BASE+1024*1024;10:16
emwe    pmem_setting.pmem_gpu0_size=0x700000;10:16
emweat the very bottom. identical for every device.10:16
detulesure but in msm_add_mem_devices10:17
detulein devices_htc10:17
emweline 34210:17
detulert platform_device_register(&hw3d_device)10:18
detuleno platform_device_register(&pmem_gpu0)10:18
detuleno platform_device_register(&pmem_gpu1)10:18
detulehere it is in .27 https://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/blobs/htc-msm-2.6.27/arch/arm/mach-msm/pmem.c#line15710:19
emweit#s fetching the smi and ebi resource from hw3d_device and setting the values.10:19
emweand then it registers taht hw3d_device .. looks all fine to me10:19
detuleok but the way you have it do you have "/dev/pmem_gpu0" ?10:20
emwegood question. the thing is .. and that is why "my" pmem.c looks different is the fact that for .27 all that setup stuff has been copy-pasted in there allthough there is official code doing that.10:21
emweone sec.10:21
emwethat's why i cleaned up pmem.c to the bare minimum and have official code doing the setup as done for any other native device.10:21
emwei hate copy-paste for the sake of butchering things over and over again.10:22
detulei agree i was just grepping the userland source and i can't find where it calls /dev/pmem_gpu10:22
emwehmhmhm you now make me ehm... whonder...10:23
emwe/dev/pmem_camera10:23
emwe/dev/pmem_adsp10:23
emwe/dev/pmem10:23
emweahem.10:23
detulefor the record since .39 pmem is copy paste from .27 we are registering gpu0 and gpu1 as well10:23
emwe/dev/msm_hw3dc10:23
emwe/dev/msm_hw3dm10:23
detulebut the overlap with the hw3d makes me wonder10:24
emwe^^ those sound like conrtol and mem?10:24
emweand if this copy-paste actually leads to problems, my arguments regarding less-butchering and more pita to do it right initially gets food. :)10:25
detulewell i have no idea if it leads to problems or not, i am just curious what those devices get used for10:26
detuledoesn't look like userland is using them10:26
emweit's master and client device according to hw3d.c. i am no expert in how this works though ...10:28
detuleyea i think the hw3d setup is fine10:29
emwelibgralloc works with /dev/hw3d[c,m]10:31
*** helicopter88 has joined #xdandroid10:31
emweso, now to your sensors patch...10:31
detuleactually it probably doesn't matter those pmem_gpu* devices are 'name=pmem_gpu*' i don't think we are compiling a driver even that gets probed with that handle10:32
emwea grep agrees on what you said :)10:34
emwebtw, i can't really spot a difference jit or jitless10:34
emwebut i haven't had SODs in some days.10:34
emweno idea...10:34
emwewe'll keep it off and be done with it.10:34
stinebdarrrghhh: stock rootfs latest, and emwe had given me some .27+acoustic kernel at some point10:35
emwestinebd, hey.10:36
emwethe only thing i haven't pushed to rootfs is the updated brcm firmware because that is not backwards compatible to .27 bcm4329 driver.10:36
emwestinebd: i already mailed him the link again :)10:36
stinebdok thanks10:37
emwei should ideally be able to push that to .releng10:37
stinebdyeah you remember where to go with it right? xdandroid@maduin:/srv/www/files.xdandroid.com/htdocs/.releng/10:37
emwethanks for the pointer again. ;)10:38
detuleactually i lied, pmem_gpu devices are '.name=android_pmem' which is our pmem driver so it certainly gets probed10:38
detuletaking them out10:39
emwethe look like unused according to msm7k10:43
*** |Jeroen| has joined #xdandroid10:47
detulei need to look at pmem, but it must be equipped to register two devices sharing the same physical region10:57
*** |Jeroen| has quit IRC11:30
arrrghhhemwe, my apologies.  i went thru mah mails and i couldn't find a .27 kernel.  i might've deleted it (gasp)11:31
emwegeez! you delete my mails?! i am abandoning the project.11:33
arrrghhhlmao11:34
arrrghhhi saved most of 'em.  not sure why i couldn't find a .27 kernel tho...11:34
arrrghhhall i could find was mgross talking about them.  the tease11:34
mgross029arrrghhh: just sent the email to you..11:35
*** vinceweis_ has joined #xdandroid11:35
emwearrrghhh: uploading it to .releng11:36
mgross029It had gbx0aplus-2011-11-09 in the subject so you may of had it but now you have it again. :p11:36
arrrghhhmgross029, lol no biggie11:37
arrrghhhemwe already sent it along11:37
arrrghhhthrowing it all on mah phone now11:37
arrrghhhyes, i'm back to winmo.11:37
emweso, it's up on releng.11:38
arrrghhhhehe11:38
arrrghhhthanks11:38
emweyou're welcome (back to haret).11:39
emwexdandroid later tell GlemSom your new autobuild site suffers some outage?11:42
xdandroidemwe: The operation succeeded.11:42
NeoMatrixJRSo, what's the best "daily use" setup to use still?  FRX07.1 w/ .27 still?11:58
stinebdno, the best daily driver is atrix running atrix-aosp 2.3.711:58
arrrghhhlol11:58
arrrghhhNeoMatrixJR, yes11:58
NeoMatrixJRthought so, but figured I'd check.  I'm a bit behind on xdandroid's current state.11:59
arrrghhh.35/.39/3.0/3.1 are in the works12:00
arrrghhhbut they all have issues here or there, they are close to surpassing .27.12:00
arrrghhh.35/.39 especially12:00
NeoMatrixJRany better audio routing available/coming?12:01
arrrghhhcoming12:01
NeoMatrixJRto .35/.39? I take it .27 = abandoned at this point.12:01
arrrghhhit's getting bugfixes12:03
arrrghhhbut yea12:03
arrrghhhpretty much abandoned12:03
NeoMatrixJRok, I'll go back to lurking XDA and playing with my tab for now.  I'm trying to give them a hand with the .36 for my tab.  Having troubles with that same damn BT chip the TP2 has.12:05
arrrghhhhahaha12:05
NeoMatrixJRdon't suppose we have working BT in .35/.39 do we?12:06
NeoMatrixJRso I could compare notes...12:06
arrrghhh.35 yes12:06
arrrghhh.39 working on it12:06
arrrghhhyou mean steal code :P12:06
NeoMatrixJRhmmm...gonna have to look @ that!12:06
arrrghhh.35 has an odd bug tho12:06
arrrghhhBT has to be one12:06
arrrghhhon*12:06
NeoMatrixJRmaybe.  Not sure if we're missing kernel stuffs or userland right now12:06
arrrghhhliterally12:06
arrrghhhphone won't sleep if BT is off12:06
NeoMatrixJRwierd12:06
arrrghhhyea, you can thank emwe for that :P12:07
NeoMatrixJRhave rfkill pm turned on?12:07
NeoMatrixJRn/m I'll take a look a bit later I'm sure12:07
emwethanks :P12:07
*** fishhead2567 has quit IRC12:11
*** fishhead2567 has joined #xdandroid12:13
arrrghhhgb tiem12:20
emwegeez, that accel sensor is hammering userland like mad with updates.12:22
emweat least on the raph.12:22
emwe32 events a second... we need to slow that down sometime...12:23
stinebdif anything we need to speed it up12:35
*** vinceweis_ has quit IRC12:36
arrrghhhbooting gb12:49
arrrghhhnew data.img, w00t12:51
stinebdwith .27 acoustic?12:53
arrrghhhyessir12:54
arrrghhhhad a phone FC on boot12:54
arrrghhhi seem to usually get those tho12:54
arrrghhhon first boot *12:55
arrrghhhanyhoo, should i be focusing on acoustic routing?12:55
stinebdfocus on everything at once12:56
arrrghhhlmao12:58
arrrghhhalright, syncing12:58
arrrghhhgoing to go out and put it thru the ringer12:58
arrrghhhit's running pretty f-in fast tho.12:58
arrrghhhi am oc'd to 710, but still12:58
arrrghhhvery nice12:58
stinebdjit is disabled right?12:59
arrrghhhlemme check13:01
arrrghhhuh13:04
arrrghhhgetprop?13:04
rpierce99dalvik vm execution mode13:06
stinebdcmon arrrghhh you've been doing this for years13:06
rpierce99dalvik.vm.execution-mode13:06
arrrghhhstinebd, i know.  i can't remember anything either lol13:07
mgross029cat /system/build.poop13:07
mgross029arrrghhh has ics on the brain. :p13:08
rpierce99technically getprop would be more accurate, because you could have a user override prop file that sets it outside of build.prop13:08
mgross029tru13:09
arrrghhhgetprop13:09
arrrghhh[dalvik.vm.execution-mode]: [int:jit]13:09
arrrghhhseems jit is on...13:09
stinebduh ohs13:09
arrrghhhi g2g13:09
rpierce99yep, i was going to say when i did a new data yesterday with gb and jit off i got no FCs, first boot was super smooth13:09
stinebdprobably placebo13:10
arrrghhhi do want jit off tho13:10
arrrghhhi'll muck with it later, peace out guys13:10
stinebdoh i built that before the jit commit13:10
stinebdarrrghhh: i'll have another image tonight after i get home13:10
arrrghhhnp13:10
*** jONpRY has joined #xdandroid13:13
jONpRYstinebd, you got the ics going?13:14
*** rpierce99 has left #xdandroid13:14
*** rpierce99 has joined #xdandroid13:14
*** rpierce99 has left #xdandroid13:14
stinebdjONpRY: not gonna happen, even on atrix :(13:15
*** rpierce99 has joined #xdandroid13:15
jONpRYwhy is that?13:15
stinebdgraphics stack requires hardware composition13:15
jONpRYhow did you get the software compositor to work?13:15
stinebdobviously msm7k won't do it, but also atrix drivers don't have support for the extensions yet13:16
stinebdthe android software egl driver does composition but it's slow as goatnuts13:16
stinebd(as seen in the emulator)13:16
jONpRYevery time i try to use the software egl, its like gralloc flips out13:17
stinebdyeah that too13:17
stinebdeven if you get it to boot there are insane graphical glitches13:17
jONpRYwhat processor is atrix?13:18
stinebdtegra213:18
stinebdthe hardware is definitely capable and moto has committed to ics for it13:18
jONpRYi'm still battling the gralloc13:18
stinebdi like my androids to be right now and aosp though13:18
*** RoTiV- has joined #xdandroid13:19
jONpRYwho needs speed13:20
jONpRY3fps is fine. just need a libegl compat layer13:20
*** AndersG has joined #xdandroid13:21
phhstinebd: are you sure tegra drivers doesn't support composition ?13:22
phhstinebd: it does on "linux" at least13:22
phhjust it doesn't announce it13:22
stinebdphh: our android blobs don't work with it13:23
stinebdwith ics13:23
phhdon't work = ?13:23
phhif it tries to find the extension and fails, disable the check13:23
stinebdpretty sure someone tried that and got segfaults or something13:24
stinebdbut i might try anyway13:24
stinebdphh: why not announce it though?13:25
phhstinebd: god knows13:25
stinebdnvidia of course13:25
phhstinebd: linux tegra driver has several such flaws13:26
phhlike it doesn't support usual initialisation of EGL13:26
stinebdtheir android blobs are completely nuts in general, so i wouldn't be surprised if that was the same thing13:26
stinebdwe already have egl hacks to work around some of their crap13:26
phhlike what ?13:27
stinebdsorry13:29
stinebdhttps://github.com/atrix-aosp/frameworks_base/commit/795523de692eb13228cc08a128ea686c00a33d2713:29
stinebdthis kinda stuff13:30
*** RoTiV- has left #xdandroid13:32
*** rpierce99 has quit IRC13:36
*** rpierce99 has joined #xdandroid13:37
*** rpierce99 has quit IRC13:38
stinebdphh: anyway yeah, the egl driver at the very least doesn't advertise compositing, and i think it might not even support it because it's pre-honeycomb13:38
*** rpierce99 has joined #xdandroid13:39
phhstinebd: well, strings thedriver |grep nameofcompositingfunctions :D13:39
emwestinebd: i assume you synced everything before building the image? whonder why jit was still on. also the phone crash is still around. bummer... thought we ironed that out in packages/apps/Phone.13:42
rpierce99emwe: this FC is only on first boot13:42
stinebdemwe: i built the image on sunday13:42
rpierce99we fixed the other13:42
rpierce99and it's only with jit on afaict13:42
mgross029emwe: I've sync'd recently and jit is still enabled on my end13:43
emwestinebd: mgross029: i pushed jit-off on wednesday.13:43
stinebdyeah i know13:43
stinebdjust explaining why it's not in the current image13:43
mgross029rpierce99: I changed my setprop ro.telephony.default_network to 7 instead of 0 and I don't get the FC on first boot any longer.13:44
mgross029emwe: sync'd today still shows.  I will repo sync again.13:44
emwemgross029: git log on device/xdandroid/msm  > commit 787ecfafc0efc944d1b2e301c39cee7a03616fd813:45
emweany buildspec.mk override left?13:45
stinebdmake installclean and rebuild13:46
mgross029fatal: Not a git repository (or any of the parent directories): .git  ---- I must have run that command wrong13:48
mgross029Ha...  My sync just pulled the update13:49
stinebdmmhmm13:49
mgross029emwe: I see your commit but it does not change system.prop.  That is still showing dalvik.vm.execution-mode = int:jit13:55
stinebdmake installclean and rebuild13:56
mgross029Ok...  (think that was an echo I was supposed to pay attention to earlier) :p13:57
mgross029stinebd: Did ^^^  still seeing /device/xdandroid/msm/system.prop with dalvik.vm.execution-mode = int:jit, so won't the build have that in it?13:59
*** Tandyman100 has quit IRC14:01
stinebdthe built is jitless now14:01
stinebdbuild*14:01
stinebdas in dalvik is being built without jit14:01
emweoh, missed that one. stinebd shall i change it to int:fast as well?14:02
emwethe resulting imave has int:fast ..14:03
stinebdemwe: you can if you want but without jit support it won't use jit no matter how you set build.prop14:03
stinebdthe only result of changing system.prop now is to avoid confusion by inexperience users such as mgross029 ;)14:04
*** helicopter88 is now known as helicAWAY14:04
stinebdpoor mgross029, takes so much abuse here14:04
mgross029stinebd: Thanks for pointing out the obvious, but I was right.  In a way. :p14:05
emweof course we are obliterating the chance to enable jit for people trying to re-evaluate it.14:05
mgross029I'm good...  I'm old and tough.  heh14:05
stinebdemwe: for the people who matter, they know how to re-enable it14:05
emwebut that will only work if dalvik is built with JIT support from my understanding.14:05
emwebut if i WITH_JIT := false, then it won't i'd think.14:06
stinebdyeah and the people who matter all build from source anyway14:06
stinebdso they can change a flag in a makefile14:06
emweperhaps I am in the mood to tidy that up...14:06
stinebdwe're talking about the arrrghhhs and detules and bzos of the world14:06
stinebdnot the xda trash14:06
stinebdalso i guess hyc knows what he's doing14:07
mgross029Or could we set davlik back and make the change in the build.prop so the image wouldn't have to be rebuilt?  Just throwing that out there.14:07
emwethat's what i just said ^^14:07
mgross029Sorry emwe didn't catch it before hitting <Enter> :p14:07
stinebdi contend that xda people are so dumb they deserve to have their choice taken away14:08
stinebdthe instant anybody suggests jit is better (again) they'll all turn it back on14:08
phhwhy disabling JIT ? RAM ?14:08
stinebdstability14:08
mgross029stinebd: so you are saying like children if you give them too many choices they won't know the difference anyway. :p14:09
emwephh: some say it "feels" faster with int:fast14:09
emwei can't spot a difference. running jitless for some days.14:09
emwethe synthetic performance is worse jitless, ofc.14:10
stinebdsome say it crashes things less often too14:10
mgross029Honestly I don't even notice a difference between the two.14:10
emwethanks mgross029  :)14:10
emwelet's say i've been doing fine with jit. if those SODs where jit related is not entirely clear to me.14:10
emwebah, that htc bma150 driver is a bitch.14:11
emwenot registering an input device...14:11
*** Tandyman100 has joined #xdandroid14:19
mgross029emwe: you enabling gsensor in 35?14:21
emweyeah, lust looking at some alternate drivers.14:21
*** helicAWAY is now known as helicopter8814:22
mgross029Cool...14:22
detulerpierce99, ugh14:24
rpierce99inorite14:24
rpierce99what's the best v6 setting these days?14:34
rpierce99maybe i should ping arrrghhh about it :P14:36
detuledunno, haven't used v6, i am not sure if our rootfs override any oom and memfree values14:38
rpierce99yeah you have to use scriptmanager to reapply their values at every boot14:38
emwewe do override14:38
emwebut any script will override again14:39
emweit pushed out some lmk "patches" last week or so14:39
emwemight be finetuned as detule pointed out to me :)14:39
emwesomebody else can come up with a patch.14:39
Tandyman100Oh god everyone run for the hills it's me :P15:07
arrrghhhrpierce99, i like the 512mb "middle" setting15:18
arrrghhhi'm on the beta versions tho15:19
rpierce99i thought that's what you said, guess i'm just not sure why a setting designed for phones with "mega" ram would be ideal for our POS15:19
arrrghhhit's just aggressive15:20
arrrghhhhis beta has 'suggestions'15:20
arrrghhhand it suggests 256HP15:20
arrrghhhbut i say fuckthat15:20
stinebd256 horsepower15:23
arrrghhhboom15:24
arrrghhhcowpower15:24
detulehey now easy with the pos15:24
arrrghhhlol15:25
*** fishhead2567 has quit IRC15:26
detulemy phone is pretty sensitive 's all15:26
*** fishhead2567 has joined #xdandroid15:28
arrrghhhhrm15:28
arrrghhhBT enables15:28
arrrghhhwifi doesn't15:28
arrrghhh11-18 13:27:57.660 E/WifiService( 1341): Failed to load Wi-Fi driver.15:28
detulewhich rootfs?15:29
arrrghhhnewest autobuild15:29
arrrghhhper sir stine15:30
arrrghhhfrom 11/11 i think15:30
arrrghhhyup15:30
arrrghhhi guess i could try insmodding it15:30
rpierce99arrrghhh: you have to get the MODULES TOO :P15:30
arrrghhhbut why didn't it get loaded15:30
detulek, as long is it's not one of these ones that have the new firmware which seems not backwards compatible15:30
arrrghhhlol15:30
arrrghhhyes, i haz ze modules15:30
arrrghhhdetule, that didn't get pushed did it?15:31
detuleno don't think so15:31
arrrghhhhrm15:33
arrrghhhsays wlan.ko doesn't exist?15:33
arrrghhhit's not in /system/lib15:33
arrrghhhit is in /lib15:33
arrrghhher /lib/modules15:34
rpierce99find / -name wlan.ko ?15:34
detulearen't they symlinked tese days15:34
arrrghhhwtf15:34
arrrghhhinsmod: can't insert '/lib/modules/wlan.ko': No such device15:34
arrrghhhevidently my wlan card fell out of my rhod somehow.15:34
arrrghhhhate it when that happens15:34
stinebdrhod doesn't use wlan.ko15:34
arrrghhhorly15:34
stinebdit's bcm432515:34
arrrghhhok, so i'm retarded15:34
arrrghhhisn't that bt?15:35
stinebdit's a combo chip but the kernel driver for wifi is bcm432515:35
arrrghhhi have a bcm432915:35
stinebderr 4329 is the driver15:35
stinebdchip is 432515:35
arrrghhhi see15:35
emwearrrghhh: which kernel?15:35
stinebd27+acoustic15:35
emwehm.15:35
arrrghhh^^15:35
arrrghhhffs15:35
arrrghhhinsmod: can't insert '/lib/modules/bcm4329.ko': invalid module format15:35
arrrghhhthat means the modules don't match the kernel?15:36
stinebdright15:36
arrrghhhhrm15:36
rpierce99hah!15:36
arrrghhhthey definitely do.  even had a new data.img.15:36
emweadb shell rm -rf /system/lib/modules/15:36
detulerm -rf /system/lib/modules15:36
emwelol15:36
arrrghhhyea that15:36
detulewhat he said15:36
arrrghhhunless stine released a system image with modules in it?15:36
arrrghhhlol15:36
stinebdprobably15:37
emweno, they stay there from previous extractions15:37
arrrghhhgood times15:37
arrrghhhemwe, this is all new15:37
arrrghhhi started fresh w/everything15:37
arrrghhhhaven't done any kernel hopping etc15:37
emweis this bind mounted over, right?15:37
arrrghhhprobably15:37
emwehm... somehow i always have to do the afformentioned rm to get modules good15:37
stinebdcan we please get rid of rootfs?15:38
jONpRYhow did you build ics for msm7k?15:41
stinebdi didn't build no ics for no msm7k15:41
jONpRYoh. what about the 3 fps?15:41
stinebdthat was on tegra2 lol15:42
jONpRYic15:42
jONpRYso we are blazing a trail then15:42
stinebdics on msm7k would just be a static image15:42
stinebdupdates every half hour15:42
jONpRYcan't you turn off the eye candy?15:43
stinebdno15:43
jONpRYmaybe just not yet15:43
stinebdit's the same idea as honeycomb15:43
stinebdexcept more requirements15:43
stinebdnow, all that stuff is compositing, egl and a bit of renderscript mixed in15:43
jONpRYwell i think we can build a compositor for glesv115:43
stinebdif you can build one for ginger glesv2 that would be nice15:44
jONpRYcall it ghetto positor15:44
arrrghhhha15:45
*** mgross029 has quit IRC16:08
*** AndersG has quit IRC16:29
*** helicopter88 has quit IRC16:33
*** virsys has quit IRC16:52
*** kalemas has left #xdandroid17:00
*** jONpRY has quit IRC17:04
*** jONpRY has joined #xdandroid17:12
*** d3tul3 has joined #xdandroid17:42
*** fishhead2567 has quit IRC17:57
emwearrrghhh: btw, you managed to get wifi up with .27-acoustic?18:04
*** ImCoKeMaN has joined #xdandroid18:08
arrrghhhemwe, haven't yet18:09
arrrghhhi still need to rebootski tho18:09
arrrghhhbeen cleaning18:09
emweok.18:09
arrrghhhgf thought it would be 'fun' to have thanksgiving at our house this year18:09
arrrghhhand now she's freaking out that the house isn't spotless...18:10
emwehah18:10
emweenjoy18:10
arrrghhhgood times18:10
arrrghhhthanks18:10
arrrghhhrebooting now, will report back sir18:10
emweno hurries18:10
emweneed to get to bed soon18:10
emwejust got a new bma150 driver supported. what a pita.18:10
arrrghhhheh18:11
emwestinebd: i'd like to ask for a new build. :)18:11
arrrghhhat least it's working18:11
emwewell, orientation appears strange.18:11
arrrghhhhrm18:11
emweit switches when i hold to the left. don't care.18:11
emweor don't care, yet...18:11
emweit would have been ueber-pita to get that old micropklt-polluted microp-bma150.c going18:12
arrrghhhlol18:12
arrrghhhoh well, bbl if you're still on.18:12
emwelikely not :)18:12
emwehave fun!18:12
arrrghhhoh yea...18:12
xdandroidNew rootfs available (20111118-0baf994) at: http://is.gd/XBhoYG -- Changes at: http://is.gd/rJ5m5A18:13
d3tul3emwe, userland bma150?18:13
emwed3tul3: massaged in the "driver api" to evdevsensor18:14
emwelook at the .35 commits18:14
emwei wanted to take over microp-bma150.c and quickly realized i don't want to at all.18:14
emweyou still have it on .39 right d3tul3 ?18:14
d3tul3oh nice this is pretty vanilla18:15
emweand from BOSCH itself :P18:15
d3tul3cool, likelihood high it will get stolen18:15
emwewith pdata power hooks18:15
emwetook it from CA18:15
emwethey got it even hooked up via SPI (needed for TOPA) if i looked right18:15
emwetheir 3 board files have either GPIO or VREG power setup18:16
emweso we likely miss that apart from enabling/disabling the the sensor itself.18:16
emwewe got gpio49 for rhod18:16
emwedunno if it will save ultra-power if we toggle it like CA/qcom does it for their comet and qsd8x50 boards18:17
arrrghhhemwe, wifi still busted18:32
emwehmhmhm18:32
emweperhaps i should give it a testrun tomorrow18:32
arrrghhhi guess it's possible the modules are just completely not matched18:32
emwei just rebuilt the .27 acoustic again18:33
arrrghhhi extracted them straight to the phone.18:33
arrrghhhdunno.  i'll look at it later and let you know if i have any breakthrus18:33
emweoh noes, i inteded too. building now18:33
emwei am likely gonna md5sum and reupload if necessary to releng18:33
arrrghhhheh18:33
arrrghhhok18:33
emwewill ping here.18:33
emwearrrghhh: re-uploaded the .27-acoustic. the zips md5 changed... so perhaps a dirty module.18:48
emwenew md5: 133c4efd5081f81406bc157a22aa2b7118:49
arrrghhhemwe, thanks mate18:53
arrrghhhi'll check that out18:53
emwethis might also explain why i failed to get .27 with new bcm firmware going...18:54
arrrghhhlol18:54
emweone sec, let me update rootfs-unsecure.img .. i am sure you bookmarked. :P18:54
emweor well, you can use current state.18:55
* emwe whonders what dropbox delivers when file uploads are not done, yet.18:56
emwerootfs-unsecure updated. it contains the updated bcm firmware.18:59
*** NeoMatrixJR has quit IRC19:01
*** NeoMatrixJR has joined #xdandroid19:10
*** Kraln has quit IRC19:17
*** Kraln has joined #xdandroid19:20
emweehm, Failed to load wifi-driver? ...19:25
arrrghhheven with the new image you just built?19:28
emwelast time driver loaded but spit out errors about unknown packets19:28
emwei just wen't to stock rootfs with old firmware19:29
emweto verify if it's firmware or something else.19:29
arrrghhhhrm19:29
emwebut you know what i like? kexec.19:29
emwethis is such a relief. unbelievable.19:29
arrrghhhhah19:30
arrrghhhthink stinebd'll accept it?19:30
emweahem... you don't read commits on gitorious.org/xdandroid/ do you?19:30
emwei pushed it out this week.19:31
arrrghhhweird19:31
arrrghhhi guess it's not in .27 tho eh?19:31
arrrghhhi don't see the option in the menu.  thought i would regardless.19:32
emwesystem image is from last sunday19:32
emwei am still uploading "mine".19:32
arrrghhhstine just gave me one i assumed was freshly built19:32
emweit was from sunday he said earlier.19:32
arrrghhhdated 11/1719:32
arrrghhhd'oh19:32
emwehm19:32
arrrghhhyou put in some lmk's?  did you ever figure out the oom grouping poop?19:33
emwecreated on releng on 11/17 then perhaps :)19:33
arrrghhhah19:33
arrrghhhlooking at the build number19:33
arrrghhh11/1319:33
emwenope, not looked. but autobuld rootfs has basic lmk patches19:33
arrrghhhsunday19:33
emwei am running stock rootfs and stock userland apart from ro.secure=119:34
arrrghhhi see19:34
emweso everything out there is what is running here.19:34
arrrghhh+119:35
arrrghhhi need to grab that new acoustic .27 kernel you put up tho19:35
emwenope... WTF?!19:37
emwefailed to load wifi driver.19:37
emweey, what have i fscked up now...19:37
arrrghhhlol19:37
arrrghhhat least it's not just my stupid user error19:38
arrrghhhmakes me feel a little better.  rpierce99 was beginning to hurt my feelings thar :P19:38
emwei see no dmesg output whatsoever damnit.19:39
arrrghhhhum19:39
emweoh!19:40
emwei think i obliterated system/lib/modules19:41
arrrghhhthey didn't repopulate?19:41
emwei deleted the dir itself19:41
arrrghhhwhat would it take to integrate a newer busybox version...?19:42
emwei have not the slightest idea.19:42
arrrghhhstinebd, pls, i can haz?19:42
arrrghhhi assume it's trivial19:43
arrrghhhbut most things aren't..19:43
emwetell me why .27 feels snappier19:46
emwe<4>[  294.398773] wlan0: non-BDC packet received, flags 0x2019:47
emwe<4>[  294.398864] dhdsdio_readframes: rx protocol error19:47
arrrghhh.27 feels snappier?19:47
arrrghhhouch19:47
emwe.35 used to feel snappier :P19:48
emwedunno.19:48
emweup for another day19:48
arrrghhhplacebo effect19:48
emweok, so have you had the same errors?19:48
arrrghhhi didn't look at dmesg...19:49
arrrghhhlet me recreate and look19:49
emweadb shell md5sum /etc/wifi/bcm432x/bcm4325-rtecdc.bin19:51
arrrghhhi'm on the kernel that's slightly older keep in mind19:51
arrrghhh48a36f22412ec284088bc4ea1552e79519:52
emweok, that is the autobuild one.19:52
emweisn't the new firmware copied over again?19:52
emweah likely not...19:52
arrrghhhwtf19:52
arrrghhhnothing, like it's not even trying19:52
arrrghhhi guess i need to reboot19:52
arrrghhhmight as well grab this new kernel whilst i'm at it.19:53
emweworks19:53
arrrghhhshut down has been shutting down lately19:53
emweonly with old firmware...19:53
emwenot with new firmware19:53
arrrghhhah19:53
arrrghhhso will have to put a check in rootfs?19:53
emwelooks like19:54
arrrghhhif on shitty old kernel, use shitty old firmware....19:54
emweif somebody would be so kind to come up with a solution?19:54
emwei'd like to do other stuff :P19:54
arrrghhhthat's my best idea.19:54
emwenah, i meant a patch or seomthing19:54
arrrghhhoh19:54
emwefor the idea you had in mind :)19:54
arrrghhhi can try19:54
emwedunno what else to do19:55
arrrghhhi need to figure out how to make merge requests against the rootfs19:55
arrrghhhi have that blackstone layout to commit19:55
d3tul3ugh19:55
emweyou can also git format-patch and sent it over19:55
arrrghhhnever figured out that raph400/diam300 thingy for those german phones19:55
arrrghhhor was it diam200?19:55
arrrghhhi can't remember.19:55
emwediam200 raph300?19:55
emwebah...19:55
d3tul3copy pate how you fail me19:55
arrrghhhemwe, i usually just mount a rootfs and hack at it19:55
arrrghhhd3tul3, well there's your problem19:56
arrrghhhpate fails every time.19:56
d3tul3:)19:56
stinebd[19:42:28] <arrrghhh> stinebd, pls, i can haz?19:56
stinebdreasoning?19:56
emwearrrghhh: i wen't over to commit, use the buildscript for it and push19:56
arrrghhhstinebd, newer version is recommended for that stuperpooper script19:57
stinebdwhy would it matter?19:57
stinebdand what is "that stuperpooper script"?19:57
emwewe got changed lmk params in rootfs. don't need more :P19:57
arrrghhhi dunno.  it seems to work OK, but it says 1.16.2+ is recommended19:57
arrrghhhemwe, lies19:57
arrrghhh:P19:57
emwelol19:57
emweplenty of improvements left19:57
emwemakes the vast difference though19:58
d3tul3emwe, drop that last memfree19:58
arrrghhhstinebd, it's a script that modifies th internal android settings for lowmem, oom groupings, etc19:58
arrrghhhd3tul3, ?19:58
arrrghhhi set an even more aggressive memfree, why?19:58
stinebdsounds poorly conceived19:58
d3tul3what's your last memfree value?19:58
emwearrrghhh: it scans for nothing19:58
d3tul3currently it starts scanning entire /proc at <80MB free19:59
d3tul3which is _all_ the time19:59
emwei settle around 45~50mb free.19:59
emwed3tul3: still got your mail here... you runnign with these settings?19:59
emwealso with last oom-adj altered to what's out?20:00
arrrghhhyea i guess if you set it too aggressive it'll just constantly run lol20:00
d3tul3not only is it constatnly running, but it's finding nothing to kill20:00
d3tul3emwe, actually no i havent gotten around to changing them :)20:00
d3tul3disregard my comment if people want to change them, they can do it themselves20:01
emwed3tul3: so if you are inclined to drive some tests with what you proposed.20:01
emwetrying to do so here as well .)20:01
d3tul3sure20:01
d3tul3i'll give them a go -> i'll drop the last memfree and oom20:02
emwealso 14 > lower?20:02
d3tul3it's fine20:03
d3tul3i think20:03
d3tul3i occasionally notice things elevated past 1420:03
emweok20:03
d3tul3ok my change is in waiting for my kernel with the dumbest typo fix to build before i reboot20:04
emwelol20:04
d3tul3check this out https://gitorious.org/linux-msm-rhod/linux-msm-rhod/blobs/htc-msm-2.6.39/arch/arm/mach-msm/board-htcrhodium-audio.c#line23020:04
d3tul3in the disable20:05
emwedifferent constant, heh.20:06
d3tul3this is what i get for _not_ just copying over your boar-*-audio20:07
emwei think i assembled the .35 one from JBs acoustic kernel tree20:07
emwei don't remember.20:08
emwethink my sd is dying20:12
emwegetting 0 byte files20:12
emwestartup.txt just got fried20:12
emwerhod_ramconsole_last.txt which gets fired on every haret boot is 0 bytes as well20:13
emweat least from android side.20:13
d3tul3sounds like xdandroid needs to buy you a new one, i hear you can get one for free with a new phone....20:14
arrrghhhemwe, gps seems to work really well20:15
arrrghhhi need to set that led setting to see if it's actually sleeping tho20:15
emweit does, otherwise i wouldn't survice the night here20:16
emwei always got gps on.20:16
emwesame as with BT :P20:16
arrrghhhlol20:16
emwei hope to finally get around to get into acoustic again20:20
arrrghhhGPS lock in my basement Oo20:20
emwei got so quickly sidetracked somehow...20:20
arrrghhhyea, easy to get sidetracked with this stuff20:20
arrrghhhtoo many things to do :P20:20
emweexactamente20:20
emweacoustic is so sucky to test20:21
arrrghhhheh20:21
emweneed another phone... call.. put these things around your head, speak into mic and listen on the other phone, then switch around.20:21
emwei don't wanna know what my neighbours would say...20:22
arrrghhhyup20:22
arrrghhhmy gf always gives me funny looks when i do that20:22
arrrghhhi have a work phone, so i don't have to steal hers20:22
arrrghhhi guess i could just use gtalk20:22
arrrghhhyou non-US heathen :P20:22
emwegtalk?20:23
emweah voip, right?20:23
arrrghhhyea there's free calls to the US & Canada20:23
arrrghhhlittle phone built into gmail20:23
arrrghhhpretty schweet20:23
rpierce99that's gvoice not gtalk20:23
arrrghhhrpierce99, it's integrated to gtalk now -_-20:23
arrrghhhthat's my point20:24
arrrghhhi don't think you need a full blown gvoice acct20:24
rpierce99no it's in the gtalk area of gmail20:24
arrrghhhdon't even need to use gvoice20:24
arrrghhhsemantics20:24
arrrghhhbut ok20:24
rpierce99its not in gtalk in g+ or the gtalk app20:24
arrrghhhthat distinction really matters to someone that can't use it, i'm sure.  thanks.20:24
arrrghhhlol20:25
rpierce99haha yes emwe is the only one who will ever read those words20:25
arrrghhhwell, he's the one i was talking to about it.  yeesh.20:25
rpierce99some fool is going to go searching for how to make phone calls from the standalone gtalk app now20:25
arrrghhhlol20:25
emwei can call you for 1,2<whatever>20:25
emwehttps://www.google.com/voice/rates?hl=de20:25
arrrghhhall because of me20:25
arrrghhhah they're expanding it eh?20:25
emweis that a cent there or what?20:25
arrrghhhvery nice20:25
arrrghhhyea20:26
arrrghhhlooks like a penny20:26
emweah, didn't figure the currency toggle :)20:26
emweso, i got out all i wanted. 2:30am here... bedtime.20:27
emwenight everybody.20:27
arrrghhhg'nite20:27
arrrghhhstinebd, does AT&T flag older phones for tethering?20:28
arrrghhhi'd bet they do...20:28
d3tul3good night emwe20:29
stinebdflag?20:29
stinebdat&t doesn't know these phones are tethering20:29
arrrghhheh some guy complaining about getting nailed for tethering on his infuse20:29
arrrghhhorly20:29
arrrghhhhe was asking if he could fly under the radar using his tp2 basically20:29
stinebdthere's no way for them to tell if an aosp phone is tethering or just using absurd amounts of normal bandwidth20:29
arrrghhhi see20:30
stinebdtechnically there is a way but it's too resource intensive for that scale20:30
*** mgross029 has joined #xdandroid20:30
arrrghhhi see20:30
arrrghhhvery nice20:30
arrrghhhi'm sure he'll be happy to hear that20:30
mgross029emwe's burning the 1am oil it looks like. :p20:30
stinebdif he's stupid about it, they can speculate about him using too much data too quickly and still bust him for it20:30
stinebdand there's nothing he can do20:30
stinebdi'm up at 4 this morning to go to nyc again20:31
arrrghhhyea20:31
arrrghhhsounds fun20:31
stinebdbig zelda launch20:31
arrrghhhheh20:31
rpierce99 /drool20:31
*** emwe has quit IRC20:32
rpierce99i don't have nearly enough time for zelda too, so it will have to wait until skyrim is over with20:32
mgross029I may be out that way early Dec.20:32
stinebdtheir half-assed mario thing last week got an insane crowd, i fear to see what this turns into20:32
stinebdsome of them say zelda is even better than skyrim20:32
stinebdbut those people are probably all japanese20:33
rpierce99well at least with zelda i would get a small amount of excercise20:33
stinebdyeah, that is a huge minus20:33
arrrghhhlol20:33
rpierce99i'm not sure how i'm going to feel about the 1:1 sword play20:34
stinebdit was bad enough in the old days i had to move both my thumbs at once20:34
stinebdnow it's an entire arm20:34
arrrghhhdoes sound strenuous20:35
stinebdi'm just glad they didn't bring out GTA for the wii20:38
stinebdi'd have to actually hump and then beat the hookers20:38
arrrghhhzomg20:38
arrrghhhthat's awesome.20:39
arrrghhhok20:39
arrrghhhcloned rootfs20:39
arrrghhhprobably didn't need to.20:39
arrrghhhgit cloned that locally20:39
arrrghhhnow to make these changes and see what i can do20:39
arrrghhhs/do/break/20:40
jONpRYyou got a rhod startup.txt?20:41
*** jONpRY has quit IRC20:59
arrrghhhstinebd, i haz patch21:12
arrrghhhi wonder if it's good or not tho21:13
arrrghhhstinebd, pm21:13
stinebdgo21:13
arrrghhhdamnit21:14
arrrghhhthe from didn't get fixed21:14
arrrghhhif the rest of it looks good i'll fix that and resubmit21:14
stinebdwhat part of it aren't you sure about?21:15
stinebdkeycodes?21:15
arrrghhhi've never submitted a patch21:15
arrrghhhis it guten?21:15
stinebdyeah21:15
arrrghhhwow, i was sure i would've screwed something up21:15
arrrghhhlet me make another and i'll put a merge request up21:16
stinebdthat reminds me21:16
stinebdgithub has better merge requests21:16
stinebdyou can review and apply them on the site21:16
arrrghhhis the rootfs on thar?21:16
stinebdyeah but not live21:16
d3tul3oh that's nice21:17
arrrghhhhrm21:18
arrrghhhi guess i have to commit this change to my tree21:18
arrrghhhthen do some voodoo to get it to be a merge request on yours? lol21:18
stinebdscrew that shit21:18
arrrghhhlol21:18
stinebdjust email the patch to me and i can git am it21:18
arrrghhhok21:18
arrrghhhthere you go sir21:20
stinebdok, i'll get to it some time next week21:20
arrrghhhnp21:20
arrrghhhit'll probably take me that long to figure out the next patch, which will undoubtedly get shot down21:20
arrrghhhjust glad to get that one off my chest21:20
arrrghhhi'm thinking emwe was talking about init21:21
stinebdemwe was talking about buttsmurfs21:23
arrrghhhpossible21:23
xdandroidNew rootfs available (20111119-2ce1f82) at: http://is.gd/2iFPhD -- Changes at: http://is.gd/ldPFw521:23
arrrghhhhrm21:24
arrrghhhnow how do i commit this to my tree?21:24
arrrghhhi thought git commit was all i needed21:24
stinebdthe hell are you talking about21:25
arrrghhhi cloned the rootfs21:25
arrrghhhso i haz my own tree21:25
arrrghhhi want to play with the firmware logic21:25
arrrghhhsince it seems .27 needs a different firmware than .35+ for wifi21:25
stinebdsounds like you want to git push21:25
arrrghhhboom21:26
arrrghhhthanks ;)21:26
arrrghhhdamnit, should've given original credit to g3rm021:26
arrrghhhmy first commit, and it's a kang.  oh well.21:26
stinebdwell get used to it21:27
arrrghhhfyi: firmware is loaded from /data/etc/wifi/bcm432x/bcm4325-rtecdc.bin21:33
arrrghhhwth?21:33
arrrghhhfirmware is loaded from /data?21:33
*** virsys has joined #xdandroid21:37
d3tul3so what's your aim there, switch on uname? if *.*.3* then install new firmware21:40
*** AOSP_BUILD_HELP has joined #xdandroid22:08
AOSP_BUILD_HELPany devepoler here??22:08
AOSP_BUILD_HELPi need some help building22:08
d3tul3wrong channel, no developers here22:10
rpierce99IRC 101: Read the topic, Don't ask to ask22:10
rpierce99Lesson over, that'll be 32.5022:10
AOSP_BUILD_HELPwhich channel would hav dev except cyanogenmod ny help :)22:11
d3tul3rpierce99, if you are on 39 you may want to download the latest from the autobuild -> with the current one flicking spkrphone on/off may not help with the mic routing22:11
d3tul3(due to my error)22:12
rpierce99:) will do, I am on .39 but I haven't gotten any calls, it hasn't slowed down for me yet like 3.0 did22:12
d3tul3i feel bad about that, but even today i would've suggested trying 3.0 it's going strong over here since yesterday at noon22:13
d3tul3(though with a reboot or two)22:13
rpierce99i'm trying to give .39 a nice long test to make sure it's a difference between the two, because I've reproed it twice on 3.022:14
*** AOSP_BUILD_HELP has quit IRC22:16
*** rpierce99 has quit IRC22:32
arrrghhhd3tul3, i am actually hoping for some help/guidance on that22:33
d3tul3i am probably much worse at scripting than you22:35
arrrghhhwell do you know where the firmware is that emwe is talking about?22:38
arrrghhhis it in /data?22:38
arrrghhhfyi: firmware is loaded from /data/etc/wifi/bcm432x/bcm4325-rtecdc.bin22:38
arrrghhhi saw that in init ^^22:38
d3tul3i think that's misleading22:39
arrrghhhlol22:40
arrrghhhwouldn't be the first time i barked up the wrong tree22:40
arrrghhhi'll bbl, let me know if you find it.  i'm not quite sure what i need to do...22:40
d3tul3i think the firmware is in /etc/wifi/blahblah22:42
d3tul3but /etc is just a symlink for /system/etc22:42
*** TheSeven has quit IRC22:50
*** [7] has joined #xdandroid22:50
*** jonpry has joined #xdandroid22:55
jonprystinebd, is there some /sys entry or something that is used to turn off fb_console before surface flinger gets its turn?22:57
*** rpierce99 has joined #xdandroid23:04
arrrghhhhrm23:23
arrrghhhi wonder where i can get both firmwares from23:23
arrrghhhi guess this image has the newer firmware, and an older image will have the old firmware...23:24
arrrghhhhrm23:25
arrrghhhbcm4325-rtecdc.bin is the same in frx07.1 to the gb image i'm on now...23:25
arrrghhhstinebd, you thar?23:26
arrrghhhhrm.  methinks i'll have to resume this tomorrow.23:30
*** bzo has joined #xdandroid23:34
arrrghhhbzo, what's up23:35
bzonot much man23:35
bzojust beat from another week23:35
arrrghhhditto23:35
bzotoo lazy to do anything tonight23:36
bzojust coming by to admire all the progress23:36
arrrghhhheh23:37
arrrghhhjonpry got ics to boot23:37
arrrghhhit's dog slow, but hey it boots23:37
arrrghhhi'm trying to figure out something simple, but don't know what i'm looking for23:37
arrrghhhdo you know anything about the wifi firmware for 27 vs. .35/.39?23:38
bzoI'm amazed he was able to have something up so quick23:38
bzoyeah a little bit23:38
d3tul3hey bzo23:38
bzohi d3tul323:38
arrrghhhbzo, basically the firmwares required are different from .27 to .35+23:39
d3tul3have you given 3.0.9 a whirl yet?23:39
arrrghhhdo you know where they are?  /system/etc/wifi?23:39
bzod3tul3: no not yet23:39
bzoarrrghhh: lemme take a look, it's kinda confusing because they're either copied or binded to other spots23:40
arrrghhhlol okie23:40
arrrghhhthanks man23:40
arrrghhhi finally pulled the rootfs23:40
arrrghhhfeelin ballsy23:40
bzod3tul3: re your email on when to push the 39.4 stuff - I think whenever you think it's ready23:41
arrrghhhcommitted a basic keymap change, now i am thinking i can fix other things too.23:42
bzogo arrrghhh go! :)23:42
arrrghhhlol23:43
arrrghhhdoes this mean i get recognized developer status?23:43
arrrghhhwoo one commit that i didn't really even create myself, lol23:43
bzoheh, well a good chunk of our updates are just copied from elsewhere23:44
arrrghhhyea23:44
arrrghhhi'm just trying to help with pulling little things together23:44
arrrghhhblackstone users will rejoyce23:44
bzook, the firmware is in /init.etc/wifi/bcm432x in the rootfs23:44
arrrghhhah23:44
arrrghhhno wonder, i was barking up the wrong tree.  thanks23:44
bzowhat copies/binds it where, I have no clue23:45
arrrghhhlol23:45
arrrghhhi'm hoping init23:45
bzothat or something called from there anyways23:45
d3tul3bzo, by the way lmk was doubly (?) broken in 3.023:47
d3tul3well lmk and another memory shrinker23:48
bzois the old oom completely removed from 3.0?23:49
d3tul3no it was a different issue they changed the prototypes for the shrinkers, and google hasn't updated their code23:50
d3tul3well for one of them at least23:50
bzoso 3.0 is working as well for you as .39 now?23:52
bzoour topics seems to be mixed up today, kernel talk on xdandroid and ics on htc-linux23:53
d3tul3i would say so but in very limited testing day and a half, rpierce was having issues23:53
arrrghhhbzo, lol23:53
arrrghhhi know there's all this activity on the tp2 again.  it's awesome.23:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!