Sunday, 2011-11-06

*** d3tul3 has quit IRC01:07
*** virsys has quit IRC03:24
*** virsys has joined #xdandroid03:54
*** SytheZN has joined #xdandroid04:06
SytheZNGreetings etcetera04:07
*** SytheZN has quit IRC04:10
*** SytheZN has joined #xdandroid04:10
*** SytheZN has quit IRC04:24
*** SytheZN has joined #xdandroid04:26
SytheZNSo I've been reading through the aos documentation04:30
SytheZNApparently there's a tool called makecharset which builds the binary file04:31
SytheZNThey say it's created to speed things up but it should run without it04:32
SytheZNonly prob is I don't have a pc to run it on04:34
SytheZNAnyone want to volunteer to build and e-mail?04:34
*** AndersG has joined #xdandroid05:22
*** AOSP_BUILD_HELP has joined #xdandroid06:16
*** SytheZN has quit IRC06:16
AOSP_BUILD_HELPcan nyone help me... tryin to build frm aosp06:16
*** AOSP_BUILD_HELP has left #xdandroid06:29
*** turbolapin has joined #xdandroid06:49
*** d3tul3 has joined #xdandroid08:02
*** helicopter88 has joined #xdandroid08:17
*** SytheZN has joined #xdandroid09:06
SytheZNHouston we have a problem...09:06
helicopter88SytheZN: Are you exploding in the space?09:07
SytheZNSomething like thay :P09:08
SytheZN*that even09:08
helicopter88what's the problem? failing with the key layout or?09:09
SytheZNNah, I'm getting somewhere with the key layout09:10
SytheZNApparentley there's a tool called makecharset that creates the bin file on build to speed up the text entry procedd09:11
SytheZN*process09:11
helicopter88and?09:12
*** SytheZN has quit IRC09:12
*** SytheZN has joined #xdandroid09:12
SytheZN###'ing network09:13
SytheZNApparentley there's a tool called makecharset that creates the bin file on build to speed up the text entry procedd09:13
SytheZN*process09:13
helicopter88yeah,i've read this,but,use that tool..09:13
SytheZNYeah well, prob is I don't have a pc atm09:14
helicopter88i have ubuntu,if it doesn't take 2-3h,i can try09:14
SytheZNI'll work on it when I get into the office, but thanks :)09:16
helicopter88I'm fighting with make,so i have time now to build everything09:16
SytheZNTa09:17
SytheZNBbl.. green lantern's calling09:17
*** SytheZN has quit IRC09:17
*** corein has joined #xdandroid09:46
*** d3tul3 has quit IRC10:07
*** rpierce99 has joined #xdandroid10:17
*** rpierce99 has quit IRC10:25
*** rpierce99 has joined #xdandroid10:42
stinebdthe tool to make a .kcm.bin is kcm10:47
stinebdit ends up in the host binaries in the build tree10:48
stinebdthere are also makefile rules to generate a .kcm.bin from a source .kcm10:48
stinebdhope whoever that was reads logs10:48
rpierce99xdandroid later tell SytheZN read the logs for 11/6 9:45AM CST for stinebd's instructions on creating a .kcm.bin10:49
xdandroidrpierce99: The operation succeeded.10:49
*** msaraiva has joined #xdandroid11:25
msaraivaHi. Any kernel/android experts around?11:26
phhhere ? god no11:27
rpierce99lol11:27
msaraivaOk.11:29
msaraiva:)11:29
msaraivaThanks anyway.11:29
rpierce99why don't you just ask your question and see if someone can help11:29
rpierce99even a non-expert can have an answer once in a while11:29
msaraivaIt's about ICS and changes to the display subsystem.11:30
msaraivaI was wondering if there are any changes that prevent Gingerbread drivers from working.11:30
msaraivaMe and a bunch of guys are trying to "port" the Galaxy Nexus dump and are stuck with display problems.11:31
arrrghhhmsaraiva, without source11:47
arrrghhhit's kinda pointless.11:47
msaraivaYeah, i know that.11:47
arrrghhhk...11:48
msaraivaStill, we're trying just for the sake of it.11:48
arrrghhhgood luck11:48
msaraivaA little bit of ICS a few weeks earlier would be nice. :)11:48
msaraivaThanks.11:48
arrrghhhyou're going to have crazy display issues11:48
arrrghhhfrom what i hear, the gralloc has changed quite a bit.11:48
msaraivaThat's what i was wondering.11:51
msaraivaWe've pinned down the problem to be with gralloc.11:51
arrrghhhlol11:51
arrrghhhyou're welcome :P11:51
msaraivaWell, it's nice for someone with knowledge to confirm things.11:51
msaraivaSo, indeed, thank you.11:51
arrrghhhi don't really have much knowledge.11:51
arrrghhhbut honestly11:51
arrrghhhthose that do11:51
arrrghhhwon't really be able to do much w/o source...11:51
phharrrghhh: bah it's possible11:52
arrrghhhhence why SDK ports are junk.11:52
arrrghhhphh, then do eeeeet11:52
arrrghhhlol11:52
phhbut so fucking annoying for what 3 weeks ?11:52
msaraivaWell, it's not SDK per se.11:52
phhmaking it work from NG dump it will take 3 months -_-'11:52
arrrghhhROM dump11:52
arrrghhhSDK11:52
arrrghhhmeh11:52
*** ProtX has joined #xdandroid11:52
msaraivaNope.11:52
msaraivaGalaxy Nexus rom dump.11:52
arrrghhhi get that.11:52
arrrghhh^^11:52
msaraiva:)11:53
arrrghhhbut as phh said, the source will be out soon11:53
arrrghhhsupposedly when the device drops11:53
msaraivaI hope so.11:53
arrrghhhwhich would be less than 3 weeks...11:53
msaraivaIt's been a long time since last major source release...11:53
arrrghhhi know11:53
arrrghhhthey kept hc all to themselves...11:54
msaraivaYep. Probably to keep chinese cake factories out of the loop. :P11:54
phhi've been  told it's to keep modders out of the loop11:54
arrrghhhlike CM?  lol11:55
msaraivaLike everyone that loves to tinker.11:55
*** ProtX has left #xdandroid11:55
msaraivaStill, it bothers to see other devices running it just "fine".11:55
arrrghhheh?11:56
arrrghhhwhat device runs ICS "fine"11:56
msaraivaICS, i mean.11:56
msaraivaNexus S.11:56
arrrghhhhrm.  well i guess that's expected lol11:56
detulearrrghhh, mgross has rhod500?12:09
arrrghhhyessir12:09
detuleso him and wistilt2 have no issues with the mic on acoustic12:10
detuleyou me and rpierce99 with our 400s are all seeing the same mic issue12:10
arrrghhhhum12:10
arrrghhhthat's odd... but i guess not unheard of.12:10
*** msaraiva has left #xdandroid12:11
arrrghhhon a sidenote12:12
arrrghhhi have SERIOUS issues on .3912:12
arrrghhhi can't get it to work long enough to really test it.12:12
rpierce99hm, i had no problems testing phone calls on .3912:12
rpierce99didn't do much else12:12
rpierce99.39 + gb that is12:12
arrrghhhit kept freaking out on me and locking up hard12:12
arrrghhhyea, .39 + GB12:12
rpierce99i had more problems with .35 because of the USB SOD12:12
arrrghhhlol12:13
arrrghhhi just didn't plug it into USB12:13
arrrghhhfor whatever reason, AC is fine.12:13
arrrghhhi think mgross said if you leave it to "always on" when plugged in, no SOD.12:13
rpierce99yeah no sleep = no sleep of death12:13
stinebda novel concept12:14
arrrghhhlol12:14
detulethere's way too many kernels around, but i'll shoot you a .39 with the new acoustic from my tree, arrrghhh you seem to be the perfect .39 candidate as your phone hates .3912:18
detulethe advantage here is that prox and color leds work out of the box12:18
arrrghhhlol12:19
arrrghhhokie12:19
arrrghhhi did miss that on NAND12:19
detulearrrghhh, rpierce99 http://dl.dropbox.com/u/38520332/39/39KerModPackage11-06.tar.gz <- should be status quo in terms of what works and what not for acoustic12:27
arrrghhhokie12:27
arrrghhhi haven't jumped to CM7 yet :P12:27
arrrghhhso i'll give this a spin12:27
detuleit's only a matter of time before CM7 runs on .35 / .3912:28
detuleon the rhod that is12:29
detulenot sure what kind of voodoo there is in .39 but i have maybe zero failed wakes12:29
arrrghhhacl's still stuck on .27 :P12:29
detulehe's got .27 humming pretty nicely though12:29
arrrghhhi know12:30
arrrghhhi'm actually amazed12:30
arrrghhhno failed wakes12:30
arrrghhhi haven't really had many SoD's12:30
arrrghhhthere have been a *few* reboots12:30
arrrghhhwhich i fear are going to be nearly impossible to troubleshoot.12:30
arrrghhhbut prox works wonderfully on NAND12:32
arrrghhhnot sure if it's .35 or what, but the prox doesn't seem to work so well on SD.12:32
detuletry it on .39 it's pretty much fault free for me...12:34
arrrghhhwell12:36
arrrghhhi'll see with yours12:36
arrrghhhfrom wistilt2's tree... it was a disaster.12:36
arrrghhheven tried with a fresh data.img12:36
arrrghhhi don't know why, but the font in .39's console makes me giggle12:40
arrrghhhshoulda put it in comic sans :P12:40
arrrghhhor better yet, wingdings so stinebd can read it.12:41
arrrghhhthat is one thing i've always loved about wistilt2's kernels12:45
arrrghhhdata comes up SO fast12:45
arrrghhhlol...12:46
arrrghhh.39 really doesn't like mah phone12:46
arrrghhhi wonder if it's the SD...12:46
detulestill broken?12:46
detulethat's so strange12:46
arrrghhhwell12:47
arrrghhhit's broken in a worse way12:47
arrrghhhit was so painfully slow12:47
arrrghhhjust opening the app drawer took minutes12:47
arrrghhhthen i swiped a few pages12:47
arrrghhhand it hung12:47
arrrghhhscreen went black with only the notification bar12:47
detuledamn12:47
arrrghhhthen bootani...12:47
arrrghhhvery odd12:47
arrrghhhit was just running .3512:47
arrrghhhi didn't change anything but the kernel...12:47
arrrghhhmaybe some app was trying to do something it didn't like.12:48
arrrghhhi'm still in shock how fast data comes up in wistilt2's kernels.12:48
arrrghhhwhatever he did to make that happen, should be patched everywhere.  cuz damn.12:48
arrrghhhmaybe droidwall?12:49
detuleperhaps, reboot to bootani doesn't quite sound like kernel issue12:50
arrrghhhwell12:50
arrrghhheverything is just painfully slow12:50
arrrghhhand i've let it sit...12:50
arrrghhhperhaps it needs to sit longer lol12:50
arrrghhhi mean this is unusually slow12:50
detulesame kernel i just booted over here, and it runs fine pretty much as soon as the desktop shows up12:51
arrrghhhwtf...12:52
arrrghhhnewest .35 from the autobuild is fine12:52
arrrghhhi haven't seen any of the apps on startup that need su12:53
arrrghhhdoes .39 need a bigger init_offset?12:54
arrrghhhlol12:54
detulei have it 0x00a12:54
arrrghhhi'm running the same poop from the thread... i made.12:54
detule:)12:54
arrrghhhand i fail.  hehe12:54
arrrghhhit's getting better12:54
arrrghhhbut damn12:54
arrrghhhseems its STILL doing the startup thing12:55
arrrghhhthis isn't on a new data.img.... poop.12:55
detule'ts ok i wonder if somehow .39 is sensitive to your sd card more than other kernels12:55
arrrghhhyea12:55
arrrghhhthat's the only thing i can think12:55
arrrghhhthis SD has seen a lot12:55
arrrghhhi think i have a sandisk around here.  i hear those are some of the best and random write performance12:56
arrrghhhyea, it's running good now12:57
*** GlemSom has joined #xdandroid12:57
arrrghhhwow.  that was the worst startup i've had in a long time.12:57
arrrghhhhrm12:57
arrrghhhseems its still starting up12:57
detuleif you grab the xdaledregime.apk for .39 from that thread12:57
detuleand verify that it's sleeping ok12:58
detulethe crap with the clocks12:58
detulewhen that would happen, the device would not fall asleep12:58
detulethough i doubt that's what you are seeing12:58
arrrghhhhrm12:58
arrrghhhok12:58
detuleor just echo i mean12:58
arrrghhhseems to be working well now12:58
detulesys/module/htc_rhodium_led/parameters/led_regime (i think)12:59
arrrghhhboard_htcrhodium_led13:01
arrrghhhso led_regime = 013:01
arrrghhhwhat should that be?13:01
arrrghhhaw fuck13:01
detuleif you set it to "2" it will do sleep debugging13:02
arrrghhhSOD13:02
detulelol your phone really hates .3913:02
arrrghhhprob the same as .3513:02
arrrghhhif i let it sit13:17
arrrghhhhum13:17
arrrghhhwakes take foreverf13:17
arrrghhhpanel seems to take days to wake13:17
*** bzo has joined #xdandroid13:17
arrrghhhbzo, curse you13:18
bzowat?13:18
arrrghhheh i dunno13:18
arrrghhhjust having problems13:18
arrrghhhand blaming you cuz you just came in13:18
bzowell, I did put that arrrghhh detection in the kernel a while back...13:19
arrrghhhlol13:19
arrrghhharrrghhh!13:19
arrrghhhi think it is a conspiracy against me.13:20
bzosome of the seemingly phone specific problems is really weird13:20
arrrghhhthis is slow on a whole new level13:21
arrrghhhi mean  i'm used to the RHOD's slowness13:21
arrrghhhbut damn.13:21
phh(when does someone put an omap4 in rhod ?)13:21
bzojonpry is a expert at smd hardware prototyping13:22
arrrghhhphh, gimmie13:22
bzolet's convince him13:22
arrrghhhgive up on the prypad13:22
arrrghhhmake the pryrho's13:22
bzoyeah, because I'm sure he'll make a fortune on that13:22
bzothe pryrhos that is13:22
arrrghhhjust needs a new screen13:23
arrrghhhmebbe moar RAM/ROM13:23
bzoso once you swap the screen, soc and ram, what is left over?13:23
arrrghhhthe fantastic keyboard13:23
arrrghhhand the tilt panel13:24
arrrghhhabout the only good things about the RHOD :D13:24
bzomaybe we should focus on transplanting that on a nexus prime13:24
arrrghhhyea13:24
arrrghhhprobably easier :P13:24
bzojust takes a bit of duct tape13:24
arrrghhhlol13:24
arrrghhhwhat doesn't13:24
bzoso what is different on detule's .39 vs the regular one?13:25
arrrghhhbesides the led_regime stuff13:26
arrrghhhi'm not sure13:26
arrrghhhwas there some clocks stuff that was different too detule ?13:26
detulebzo, Alex's clocks vs. JB's13:27
bzoany noticeable differences by running Alex's?13:27
arrrghhhthey seemingly all suck for me.13:27
detulewell when in froyo it upped my neocore score from 15.5 to + 2013:27
arrrghhhalthough these might be worse.13:27
detuleand it wasn't outliers, consistently13:27
bzowonder if Alex overclocked the gpu by default, I remember him experiementing with that13:28
detuleis the gpu tied to PLL1?13:28
bzoprobably, not sure though. Most thing are related to pll113:29
bzopll0 tends to be for the a9, and pll2 is for the top clock on the cpu13:29
bzois emwe using Alex's clocks as well on .35?13:31
detuleyes13:32
bzodetule, I suppose we ought to convince WisTilt2 to merge your changes in then13:32
detulethat would be nice13:33
bzoI would love to see us converge down to just a couple of kernels again13:34
bzoI think we are at 5 or more now :/13:35
arrrghhhlol13:35
arrrghhhyea, there's people doing a lot of testing things13:36
arrrghhhstarfox had some changes in his that really pepped things up too13:36
arrrghhhoff the top of my head i have no clue exactly which ones helped from his test kernel13:36
bzoimproved speed?13:36
bzoand what kernel is he branched off?13:37
arrrghhh.2713:37
arrrghhhmainline13:37
arrrghhhhe also did some crazy things like backported ext4 to .2713:37
bzoso is the main problem with .39 vs .27 the slowdown?13:39
bzoand I guess the cam and bt are not completely working yet?13:39
arrrghhhseemingly13:39
*** GlemSom has quit IRC13:41
bzoI'm going to try using .39 for a while then13:41
bzois the latest on autobuild?13:41
detulebzo,  i am curious if you experience this slowdown as well13:41
detulebzo, with 39 you will likely not get any sound unless you are new_acoustic enabled13:42
detulei can send you the libs if you want to mount them13:42
bzothat would be great13:43
detulebzo, http://dl.dropbox.com/u/38520332/acoustic_libs/new_acoustic_stock.tar.gz13:48
detulea kernel from my tree: http://dl.dropbox.com/u/38520332/39/39KerModPackage11-06.tar.gz13:48
bzothx!13:49
bzois bind mounting the libs sufficient?13:49
detuleit is13:51
bzodo I need to mount the csv files as well?13:56
detuleall .csv files to the root of the sdcard13:58
bzoit reads them directly from there?13:58
bzonot sys/etc?13:58
detuleno the new acoustic libs read them from /sdcard/*13:59
bzok13:59
bzodoes it expect the files: AudioFilterTable.csv, AudioPara3.csv and AudioPreProcessTable.csv?14:01
detulehm it expects a few files don't know which off the top of my head14:03
detulei have maybe 6 .csv files14:03
detuleall copied straight from /Windows in winmo14:03
arrrghhhbzo, if you wish, i can send all you need14:04
arrrghhhincluding emwe's latest gb build14:04
arrrghhhwith all the acoustic stuffs14:04
arrrghhhso then we're all on the same platform14:04
bzosure, was planning on checking the gb stuff next14:04
arrrghhhit's pretty good14:04
arrrghhhemwe's been cranking on it14:05
bzodetule, you on gb or froyo?14:05
arrrghhhon .35, you HAVE to have BT on tho.14:05
arrrghhhit's... a feature.14:05
arrrghhhi'm not sure how that works on .3914:05
detuleBT doesn't work on .39 so no need to worry about that14:05
arrrghhhlol14:05
arrrghhhok14:05
detulebzo, i am interchanging between 06+ (froyo) and gb14:05
arrrghhhbzo, incoming PM14:05
*** emwe has joined #xdandroid14:08
detulethere's the man14:11
arrrghhhit's his fault!14:12
arrrghhhbah, i just flashed CM7 sorry guys14:12
*** SytheZN has joined #xdandroid14:19
*** raymonddull has joined #xdandroid14:19
emwehuh? :P14:20
SytheZNWhat's huh backwards?14:20
arrrghhhwhat's up emwe14:20
arrrghhhwhat's race car backwards14:20
rpierce99rac ecar14:20
arrrghhhboom14:20
emwenada. sorting some mp3...14:21
rpierce99SytheZN: did xdandroid send you a message just now14:21
SytheZNrpierce99: ty for the info14:21
SytheZNYeah, thanx14:21
rpierce99thank stinebd, just a messenger14:21
arrrghhhSHOOT THE MESSENGER14:21
SytheZNWill do :D14:21
* SytheZN whips out an AK14:22
* SytheZN then stands there kile bruce willis looking all awesome and stuff14:22
arrrghhhmmmmhmmmm14:23
arrrghhhkile... i'm sure.14:23
SytheZNoi *like even14:23
SytheZNLmao :D14:23
arrrghhhoh well14:23
arrrghhhso in-call volume with speaker/earpiece is functional now emwe ?14:24
arrrghhhor was this always a .27 issue14:24
SytheZNForgive me, I'm lysdexic14:24
arrrghhhheh14:24
emwearrrghhh: it's was an overall kernel issue on .27/.35 with alex' acoustic snd endpoint setup. the CURRENT snd device id was moved from 256 to match the one from IDLE which apparently broke incall volume change.14:25
SytheZNSpeaking of volumes... I get random bugs when receiving calls where I can't be heard unless I hit loudspeaker14:25
detuleemwe, perhaps if you put IDLE as 256 as well that will fix my mic :)14:25
emwearrrghhh: or perhaps it's an userland thing which is just circumenvented by changing back the CURRENT snd device id back to 256.14:25
emwedetule:  did we ever have IDLE 256 some point in time?14:26
emwebut my mic is fine :P14:26
detuleand you have a rhod40014:27
emweapart from some sponatenous SODs.14:27
detuleso the only other thing i can think of is those MUTE calls on the RIL side14:27
arrrghhhsome CDMA thing?14:27
detulethere's an xml parameter send_mic_mute_to* that would supposedly force the mic mute calls that are currently routed through the RIL to be routed through the acoustic libraries14:28
detuleyeah i am not sure if those MUTE calls appear in gsm radio logs14:28
emweah btw.. as you mention... mic mute doesn't work :P14:29
emweand you meant this: <bool name="send_mic_mute_to_AudioManager">false</bool> ?14:29
arrrghhhthis seems to be a new issue as well14:29
arrrghhhi don't remember any incoming call issues with the mic14:29
arrrghhhon acoustic14:29
SytheZNI'm on a raph btw14:30
detuleright, this would entail small changes to the acoustic libs14:30
SytheZNWhat can I do to help?14:30
emwedetule: confused... that phone ui button in the middle says "sound off" literally for me... what is it supposed to do? disable mic or disable earpiece/speaker sounds?14:30
detulei thought there was a mute button somewhere on the phone ui14:31
arrrghhhthere is14:31
arrrghhhit's the middle button14:31
arrrghhhon the bottom14:31
* raymonddull wonders if he should keep his mouth shut about a bug14:31
detulemust be some kind of a german dialer translation thing14:31
detule:)14:31
detuleit should be muting14:31
arrrghhhraymonddull, some native android bug?14:31
detulethose calls are currently routed through the RIL14:31
detule(i think they work over here btw)14:31
raymonddullyeah,having to toggle speakerphone on and back off for sound to work was a major bug that affected most of the galaxy s series for the first year of having aosp roms14:32
emwedetule: it says "Ton aus" ... so literally "Sound off" which is kinda stupid translation.14:32
raymonddulland still does kind of14:32
emwedetule: would need to retest if that is actually broken or not.14:32
detuleemwe, if you change that xml value you need to comment this block https://gitorious.org/xdandroid/hardware_msm7k/blobs/e5f7c1bebcfd0d6d0af9ae576de282a0d0a53b4d/libaudio_wince/AudioHardware.cpp#line76314:32
SytheZNMy mic doesn't work unless speakerphone's on...14:33
SytheZNWhen I switch it back off again it stops again14:33
raymonddullhmm14:34
raymonddullon those you had to turn it on and back off and it worked14:34
raymonddullyou could hear them,but they couldn't hear you until you did that14:34
raymonddullit was like the mic was muted14:35
arrrghhhSytheZN, you're talking about a different build too14:35
arrrghhhmost of us are testing on the new acoustic code14:35
SytheZNI am?14:35
emwedetule: well, do we need it toggled/switched in case it works fine for us?14:35
arrrghhhyes, see above ^^14:35
SytheZNI updated to the latest builds last neght14:36
SytheZN*night14:36
arrrghhhgb+.35?14:36
emwearrrghhh: then it's a driver/kernel bug then, no? detule?14:36
arrrghhhemwe, is the acoustic lib stuff in the repo?14:36
detuleemwe, i have no idea i've been racking my brain with the mic issue all weekend and I am grabbing for straws here14:36
SytheZN20111019 if I'm not mistaken14:36
emwedetule: if you can confirm it working, we can toggle it. i still need to test actually.14:37
detuleemwe, both arrrghhh and rpierce99 see it on rhod40014:37
arrrghhhSytheZN, are you building?14:37
SytheZNNah, I downloaded from the nightly build service14:37
emwedetule: on .35 from arrrghhh, ok, rpierce99 on which kernel?14:37
detuleboth14:37
emweok14:37
emweseems i need to provide a newer build then :)14:37
arrrghhhlol14:38
detuleif i could only build gb...14:38
SytheZNI just got my pc back tho...14:38
detulemute button works fine here btw14:38
detulei just checked so those RIL calls are obeyed nicely14:38
arrrghhhnightly build service?  lol14:39
emweand what was broken again? incall mic defunct until speaker toggled?14:40
emwetoo much info.14:40
emwesorry guys...14:40
SytheZNyeah... http://files.xdandroid.com/rootfs/14:40
detuleincoming calls only happens mostly when phone in silent, however i've had it happen a few times when phone not in silent too14:40
detulei am not sure if it's a kernel driver btw, i built a kernel with JB's dump/debugging functions, and dumped the memory at the mic_offset14:41
arrrghhhSytheZN, that's just the rootfs -_-14:41
detuleit's the same both when it's working and not working yet it should.....14:41
SytheZNAlthough I guess I'm still using FRX0714:41
SytheZNAh lol14:41
detulei guess it could be some sort of an amp issue, i don't understand the audio hardware at_all14:42
* SytheZN install ubuntu as we speak14:42
emwedetule: i haven#t stepped through all of it either...14:42
* SytheZN revels in his own awesomeness14:48
*** mayday_jay has quit IRC14:50
*** mayday_jay has joined #xdandroid14:51
bzodoh, user.conf still isn't working in .39 is it?15:00
detulethat's actually a good question, i've been pushing all the libs lately15:03
bzoyeah, looks like it never got fixed15:04
detulenot sure why that wouldn't get processed -> what the kernel would have with processing the conf file15:04
detuleperhaps it errors out somewhere early15:04
bzohaven't noticed any pauses yet15:05
bzohow often does it happen?15:05
*** GlemSom has joined #xdandroid15:11
detuleit doesn't for me, at least not since i brought alex's clocks over15:14
bzoI'm running yours, so maybe that is why15:15
bzohmm, seeing the slowdown now15:33
SytheZNNow for the question which's been asked a million times and more...15:56
SytheZNWhere do I begin?15:57
SytheZNI mean, I've worked with linux for years, but I haven't really done any dev work on it15:59
SytheZNDo I start with a git repo? And if so, where?16:00
* SytheZN feels all n00by and stuff16:02
*** corein has quit IRC16:04
*** GlemSom has quit IRC16:17
*** ringer has joined #xdandroid16:19
*** SytheZN has quit IRC16:21
*** bzo has quit IRC16:30
*** emwe has quit IRC16:33
*** ringer has quit IRC16:52
*** SytheZN has joined #xdandroid16:55
*** AndersG has quit IRC16:57
*** helicopter88 has quit IRC16:57
arrrghhhSytheZN, the wiki has several pages on getting/building the system image16:57
*** SytheZN has quit IRC16:59
arrrghhhoh well16:59
*** SytheZN has joined #xdandroid17:00
arrrghhhSytheZN, the wiki has several pages on getting/building the system image17:01
*** turbolapin has quit IRC17:01
SytheZNTa, I'll take a look...17:01
* SytheZN generally prefers the human interaction part of learning17:02
SytheZN:-P17:02
arrrghhhbah17:02
SytheZNOn a more random note, what's with the temperature increase when charging?17:15
arrrghhhstuff gets warm when being charged?17:15
SytheZNAnd the clock drift?...17:15
arrrghhhFFS17:15
arrrghhhread the FAQ17:15
arrrghhhclock drift --> clocksync17:15
SytheZNLol oki17:17
SytheZNThe q with charging is more along the lines of the major difference between charging in wm vs android17:18
arrrghhhwm was made for the phone17:18
arrrghhhandroid isn't17:18
arrrghhhthere's probably still a couple of bugs left in Android... especially since there's basically 0 developers actively working on the RAPH17:18
arrrghhhmost of the big breakthrus happened on the RHOD...17:19
arrrghhhsorry17:19
SytheZNYeah I know... but why should that affect the charging?17:19
arrrghhhpower management?17:19
SytheZNLol no prob17:19
SytheZNAh... i'd figured power management was more to do with the other components than the charging circuitry17:20
arrrghhhffs17:20
arrrghhhit's not a problem with "the charging circuitry"17:20
arrrghhhpower management on that device isn't so great17:20
SytheZNI realise it's not17:21
arrrghhhi noticed when wistilt2 started tweaking with that stuff on the RHOD, it ran a fuckton cooler17:21
arrrghhhsooooo17:21
arrrghhhyea17:21
SytheZNI see...17:21
SytheZNSoz for the blonde questions17:22
arrrghhhwell i think part of the problem is no one "knows" the answer to your questions17:22
arrrghhhi had a shitload of the same questions17:22
arrrghhhbut how can anyone know the answer for sure?17:22
SytheZNAh...17:23
arrrghhhso much of this project is based talented reverse engineering17:23
SytheZNTrue...17:23
arrrghhhwe have 0 information on how the camera hardware works17:23
arrrghhhevidently our cam libs are just hacks17:23
SytheZNI just figured that charging was autonomous if you get what I'm saying17:24
SytheZNI see...17:24
arrrghhhit's not17:25
arrrghhhwould be nice if it was completely software independent17:25
arrrghhhand charging "just happened" 100% in hardware17:25
arrrghhhbut in reality, it doesn't.17:25
arrrghhhnot on our phones at least...17:25
SytheZNYeah I got as much from before17:26
SytheZNSo basically were building an autopilot system for an invisible airplane17:27
arrrghhhuhm17:27
arrrghhhsure?17:27
SytheZNWell you're watching the pilot to figure out what the wings are doing17:28
arrrghhhenough with the metaphors17:28
* SytheZN takes a hint17:28
arrrghhhlol17:29
arrrghhhi just don't see the need17:29
SytheZNNah, I know the feeling of dealing with newbs17:29
SytheZNPlease forgive me tho17:29
SytheZNI'd really like to learn as much as I can17:30
arrrghhhread17:30
arrrghhhlots17:31
arrrghhhand lots17:31
arrrghhhof reading17:31
SytheZNI do... it just drives me nuts when I'm itching to know something that just isn't being answered17:31
arrrghhhlol17:32
arrrghhhdude17:32
arrrghhhthe clock drift problem is in the FAQ17:32
SytheZNYeah I know... I was just wondering if there was anything I could do besides syncing continuously17:32
SytheZNI'd like to understand the problem17:33
arrrghhhwell, if there was another answer17:33
SytheZNMore than get the "answer"17:33
arrrghhhlol17:33
arrrghhhif the problem was understood17:33
arrrghhhit would've been fixed17:33
SytheZNTrue lol17:33
arrrghhhsomeone said they seemed to notice additional drift when swiping around the screens/menus17:34
arrrghhhnow fix the problem17:34
SytheZNLmao17:34
SytheZNI get the point17:34
SytheZNLots of could be's but not too many is's17:35
arrrghhhyea17:36
arrrghhhCDMA also seems to provide consistent NITZ updates17:36
arrrghhhwhich I don't think GSM carriers do on a consistent basis.17:36
SytheZNI suppose id doesn't really help that I'm useng a 'dead in the water' device17:36
arrrghhhprobably not17:37
arrrghhhit's not like the RHOD is that hot17:37
SytheZNYeah well I,m in south africa... network operators here transmit the wrong date, let alone time17:37
arrrghhhlol17:37
SytheZNWhy do you say that?17:38
SytheZNI love this brick17:38
arrrghhhi love my RHOD17:39
arrrghhhbut it's slow17:39
arrrghhhand there's not many devs left17:39
arrrghhhalthough it seems we're resurging again17:39
arrrghhhit ebbs and flows i guess17:39
SytheZNAs do all great things...17:39
SytheZNWhat're the rhod specs? More or less I mean17:40
phhmsm7201 528MHz, 256MB RAM + 32MB17:40
arrrghhhpretty much the exact same as the fucking RAPH17:40
arrrghhhscrew you HTC17:41
SytheZNSo much the same as the raph17:41
arrrghhhalthough i guess RAPH doesn't have that 'turbo mode'17:41
SytheZNLmao :D17:41
SytheZNTurbo mode?17:41
arrrghhhnot sure17:42
arrrghhhsupposedly it makes a difference17:42
arrrghhhand the rhod always felt faster than the raph17:42
arrrghhheven in winmo17:42
arrrghhhin android i don't think it's a fair comparison17:43
SytheZNAh...17:43
SytheZNProbably just like "hyperthreading"17:43
SytheZNOr just a larger l2 cache17:43
SytheZNI'm interested to know how much of the other hardware is different...17:45
SytheZNI wonder if HTC would help if I asked really nice17:47
arrrghhhLOL17:47
* SytheZN rolls his eyes17:47
arrrghhhgood luck with that17:47
arrrghhhask qualcomm too while you're at it17:47
arrrghhhthey're small mom & pop shops that really care about devices built in 200817:47
phharrrghhh: turbo mode is RAM going from 133MHz to 166MHz17:47
SytheZNlmao :D17:48
arrrghhh133 to 16617:48
arrrghhhwow17:48
arrrghhhTURBO17:48
SytheZN20%17:48
phhoverclocking RAM has greater benefits than overclocking CPU imho17:48
SytheZNMore or less17:48
SytheZNYeah well... cpu's waiting most of the time17:49
SytheZNThat's exactly why hyperthreading "works"17:49
arrrghhhphh, lets push it harder then17:50
arrrghhhi want snapdragon speeds outta mah RAM17:50
phharrrghhh: that's what i told bzo two days ago :p17:50
arrrghhhlet's blow it up17:50
arrrghhhhahaha17:50
arrrghhhyea, i know.17:50
SytheZNAnyways... gotta catch some half-blinks... cheers17:51
arrrghhhcya17:51
*** SytheZN has quit IRC17:52
*** raymonddull has quit IRC18:23
*** hardwalker has joined #xdandroid20:20
*** raymonddull has joined #xdandroid20:38
*** d3tul3 has joined #xdandroid21:34
*** ringer has joined #xdandroid21:49
*** raymonddull has quit IRC21:55
*** [7] has quit IRC22:05
*** TheSeven has joined #xdandroid22:05
*** virsys has quit IRC22:17
*** ringer has quit IRC22:22
*** d3tul3 has quit IRC22:48

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