Tuesday, 2010-11-23

RogueAgent[TP2]f22: the ones for the home key and the task switch00:08
F22yes, i have a b4=HOME cmdline option in my rootfs which will eventually get submitted.00:10
RogueAgent[TP2]what is b4?00:12
*** TheDeadCPU has joined #xdandroid00:13
F22front panel button 4, ie. the end call button00:21
RogueAgent[TP2]ah00:21
RogueAgent[TP2]i take it you just end calls by using the on screen button?00:21
F22two choices, that's one. the second is to enable power to end calls also.00:22
F22there is an option to set that in accessibility00:23
RogueAgent[TP2]hmm00:26
RogueAgent[TP2]so if ur on a call the power button will hang up00:26
RogueAgent[TP2]but all other times it turns the screen off?00:26
RogueAgent[TP2]also if u hold your end button now does it allow you to switch apps?00:27
F22yes00:30
F22to both questions00:30
F22http://www.mediafire.com/download.php?mxnppll067wxx2w  <--- if you want to try it out.00:31
XirXesare you saying you made the in call touch ui toggle through the startup.txt?00:32
F22no. i haven't touched the in call touch ui at all.00:33
XirXesi figured you just menu hitting menu00:34
F22there is an option in settings->accessibility named "Power Button Ends Call" that may be selected.00:34
F22that's already part of froyo.00:34
XirXesnice. didnt know about that00:34
RogueAgent[TP2]oh sweet00:36
RogueAgent[TP2]its the newest rootfs also00:36
F22yup00:36
RogueAgent[TP2]have you ever thought of making the make call button do that?00:37
F22do what? home/recent apps list? or end call?00:38
RogueAgent[TP2]home/recent apps00:38
F22not really, but it's theoretically possible, unless microp handles its three buttons differently. button 4 is handled by a different event from the first three. not sure why htc set it up that way.00:40
RogueAgent[TP2]ah00:40
F22the nice thing about mapping it to b4 is that i can have all the rhod's share the same layout files. the navi_pad layouts are all the same.00:43
F22they don't differ among the different models.00:43
F22the microp layouts however are all different.00:44
RogueAgent[TP2]ah00:44
F22os if we changed one of those, we'd need to create a new layout file for each model, of which we currently have nine in our repo.00:44
F22os=so00:44
RogueAgent[TP2]quick question f22 any other changes in your rootfs00:44
RogueAgent[TP2]just kinda strange its 2mb bigger then the stock one00:44
F22working symbol key, working control key in terminal emulator, a bunch of other new keys.00:45
RogueAgent[TP2]oh00:45
RogueAgent[TP2]nifty00:45
F22what model do you have?00:45
RogueAgent[TP2]rhod50000:46
F22haven't had someone with the verizon model test it yet, cool. i'll pull up the changelist for that model..00:47
RogueAgent[TP2]hmm00:48
RogueAgent[TP2]do i have to do something special to have your rootfs changes take effect?00:48
F22only if you want the end call button to behave as home/recent apps.00:49
RogueAgent[TP2]and whats the special thing?00:49
F22b4=HOME on cmdline in startup.txt00:50
RogueAgent[TP2]oh yeah00:51
RogueAgent[TP2]lol00:51
F22|  { } [ ] ` < > as fn-t a s z x q c and v.00:51
F22<tab> as fn-<space>00:51
F22it's a bit bigger than stock for two reasons, the more significant reason is that i compiled on a 64 bit system, so there's a bit more file overhead in the result. the second is that i decompiled the keymap binaries for which we had no sources and added the sources back in.00:54
F22everything i build myself is larger than stock, even with no mods.00:56
RogueAgent[TP2]ah00:56
RogueAgent[TP2]im consued about those sentences00:56
F22consued?00:56
RogueAgent[TP2]im guessing tey are waht u added00:56
RogueAgent[TP2]confused00:56
RogueAgent[TP2]sorry00:56
RogueAgent[TP2]so those symbols are now bound to fn- and those letters00:57
F22oh, yes. those are the new keys.00:57
F22yes.00:57
RogueAgent[TP2]and tab is fn-space?00:57
F22yes00:57
RogueAgent[TP2]rgr00:57
F22rgr?00:57
RogueAgent[TP2]Roger00:57
F22heh, ok.00:58
RogueAgent[TP2]wonder how far whatsit is on the kb backlight00:58
RogueAgent[TP2]so all i have to do is add b4=home into startup.txt?00:59
F22yup00:59
RogueAgent[TP2]ooo00:59
RogueAgent[TP2]I might have an issue00:59
F22i know that bit works because i'm using it myself right now.00:59
F22what's the issue?01:00
RogueAgent[TP2] just realized i didn't do my own startup.txt01:00
F22you have sov's startup utility?01:00
RogueAgent[TP2]yes01:00
F22well i've never used his utility. i always edit mine by hand. :P i can tell you how to edit it by hand if you want. i've heard there is a way to manually edit it in his utility also.01:01
RogueAgent[TP2]yea there is01:01
RogueAgent[TP2]im going to boot into android with his startup and save it01:02
F22ok01:02
F22fyi, here is a copy of my cmdline in startup.txt:01:03
F22set cmdline "lcd.density=240 b4=HOME clock-7x00.a11=500 acpuclock.oc_freq_khz=614400 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=2 force_cdma=0 physkeyboard=rhod210 rel_path=andboot"01:03
F22only overclocking to 600 MHz currently.01:04
RogueAgent[TP2]wait01:05
RogueAgent[TP2]is all that yuou need for startup.tx?01:06
F22there is more in the file01:06
F22that's just set cmdline01:06
RogueAgent[TP2]ah01:06
RogueAgent[TP2]whats the lcd.density and sleep mode do?01:06
RogueAgent[TP2]actually ill go look it up01:07
*** Ashar has quit IRC01:07
F22lcd.density is for all rhodiums is 240. not all XDAndroid handsets are wvga, nor are they the same size screens.01:08
RogueAgent[TP2]ah01:08
RogueAgent[TP2]and damn it startup.txt is all blank again01:08
RogueAgent[TP2]time to manually do it01:08
F22sleep mode is how deep asleep the handset falls while it's asleep, ie how much stuff gets turned off.01:09
F22even htc doesn't use sleep mode 0 apparently. sleep mode 1 can cause problems if you overclock, somethings your handset won't wake up. so if you overclock, sleep mode 2 is recommended.01:10
F22somethings=sometimes01:10
*** virsys has quit IRC01:10
RogueAgent[TP2]where can i find the rhod500 startup.txt?01:10
*** TheDeadCPU has quit IRC01:11
F22two places, there should be a link on reef's site to it, but there should also be a copy in the reference build. at least i know there is in the base package that the reference build was built from. i can dig it up.01:12
F22do you see a STARTUP CONFIG folder within andboot?01:13
RogueAgent[TP2]nope01:13
F22where is arrrghhh with his quick links when i need him. he's got them all bookmarked. :P01:14
F22give me a min, i'll dig it up.01:14
RogueAgent[TP2]found it01:17
F22http://htcandroid.xland.cz/configs.zip  <-- has the latest i think01:17
F22hmm...it's a generic file for all rhodiums01:18
F22really, the only thing that varies is the keyboard definition01:18
F22otherwise they're all pretty much the same.01:18
RogueAgent[TP2]hmmm01:19
RogueAgent[TP2]i have hte oone rom reef and the one from that zip01:19
RogueAgent[TP2]and they are different01:20
RogueAgent[TP2]msmts_calib=0x9f.0x39a.0x35c.0x7801:20
RogueAgent[TP2]what is this lien for?01:20
F22i think reef's is slightly out of date. but i don't think it does any harm either.01:20
F22the calibration line is no longer necessary i've heard.01:20
RogueAgent[TP2]ah01:20
F22i don't use it and mine works just fine.01:20
RogueAgent[TP2]his also doesn't have the clock line01:21
*** virsys has joined #xdandroid01:23
F22that sets the speed of the a11 chip, not sure why i have it and reef doesn't.  i think i copied it over after looking at one of the veteran dev's startups when i first started out.01:23
RogueAgent[TP2]ah01:24
RogueAgent[TP2]should i leave it at what its at?01:24
RogueAgent[TP2]clock-7x00.a11=50001:25
F22honestly, i have no idea. all i can say is that my phone is very stable right now.01:25
RogueAgent[TP2]:P01:25
RogueAgent[TP2]Do I still have to force hdware 3d?01:25
F22no, that's another one that i think is obsolete.01:25
RogueAgent[TP2]what about hte prox sensor?01:25
F22you mean gsensor? or are you seeing a prox sensor line in there too?01:27
RogueAgent[TP2]its in reefs list of cmdline switches01:27
F22i don't think it's in his rhodium 500 startup though.01:28
RogueAgent[TP2]its not01:29
RogueAgent[TP2]i just didn't know if the proximity sensor line is outdated or not01:30
F22http://reefermattness.scepterr.info/startdir/rhod500.txt01:30
F22i've never seen it any of the rhodium startup.txt's i've seen.01:30
RogueAgent[TP2]hmm01:30
RogueAgent[TP2]that one has a new line01:30
RogueAgent[TP2]i don't see anywhere01:30
RogueAgent[TP2]which is that pmem one01:31
F22ah, leave that out.01:31
RogueAgent[TP2]set cmdline "lcd.density=240 b4=HOME clock-7x00.a11=500 acpuclock.oc_freq_khz=786432 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 pm.sleep_mode=2 force_cdma=1 physkeyboard=rhod210 rel_path=andboot"01:31
RogueAgent[TP2]does that look good?01:31
F22change the physkeyboard= line01:32
F22you don't have a 21001:32
F22you have a 50001:32
F22you have a pretty high overclock there. has your phone run stable at that speed in the past?01:34
RogueAgent[TP2]yes01:34
F22ok01:34
F22clock headroom varies from phone to phone.01:35
F22i forget which gsensor_axis is recommended now. i think it's 2,1,3 or i wouldn't have used it. i researched them both when i started out. but it's been awhile.01:37
F22reef's is 2,1,3 too.01:38
RogueAgent[TP2]hmm01:38
F22out of curiosity, where did you get -1,-2,3 from?01:42
F22i -believe- they both work, there just may be some apps for which 2,1,3 works better. -1,-2,3 was the original setting people were using, then the recommendation got changed to 2,1,3 for the rhodium.01:44
RogueAgent[TP2]ah01:46
RogueAgent[TP2]um01:46
RogueAgent[TP2]i got that from the startup in that zip you gave me01:46
F22lol, it can be confusing with all the files and web sites floating around.  one site hears about some changes but not others, the other site hears about a different subset of changes...lol.01:50
*** tattrdkat has joined #xdandroid01:52
RogueAgent[TP2]hmmm01:52
F22reef was the best source for rhodium updates because he had one himself and was very closely monitoring development. but then he got a samsung galaxy s and he hasn't been around as much. blazn has languished. the maintainer of the official repo doesn't have a rhodium on the other hand.01:52
*** virsys has quit IRC01:52
RogueAgent[TP2]it doesn;t seem as smooth as it usually does01:52
F22you booted up with it?01:53
RogueAgent[TP2]yeah01:53
RogueAgent[TP2]I'm in android now01:53
RogueAgent[TP2]seems laggy01:54
F22give it 10 minutes, then tell me if it's still sluggish.01:54
RogueAgent[TP2]it has been 10 minutes :P01:54
RogueAgent[TP2]hmmm01:55
RogueAgent[TP2]its broke01:55
RogueAgent[TP2]:(01:55
RogueAgent[TP2]I'll restart it and see what happens, wasn't letting me download stuff01:55
F22too sluggish? or a different issue?01:56
RogueAgent[TP2]no01:59
RogueAgent[TP2]no downloading of market01:59
F22let me know how the restart goes02:00
F22do the keys work right?02:00
RogueAgent[TP2]yeah02:00
RogueAgent[TP2]yes02:00
RogueAgent[TP2]I'm also going to throw in that 3d hardware force02:00
F22the other option is to rename data.img to something else and see how it works with a fresh data.img. do you have titanium backup?02:01
RogueAgent[TP2]nope02:02
RogueAgent[TP2]was brand new install02:03
RogueAgent[TP2]ive just now started using it02:03
F22ah, so no real worries if you blow data.img away.02:03
RogueAgent[TP2]just recopying it over02:07
RogueAgent[TP2]i have a 1.5gig data.img02:07
RogueAgent[TP2]Seems to be working fine now02:08
RogueAgent[TP2]I'll be able to truly tell once angry birds gets installed02:09
F22xdandroid has some odd intermittent sluggishness issues, i wish we could determine the source of them.02:09
F22lol02:09
RogueAgent[TP2]hey it was playable before02:09
RogueAgent[TP2]with some glitches02:09
F22i've heard02:10
RogueAgent[TP2]if its non playable hw3d gets thrown back on02:10
RogueAgent[TP2]wish verizon would hurry up and get the desire z02:10
F22i hope they make it a full droid and don't bingify it.02:11
F22apparently they're going to make an angry birds lite now.02:12
F22for less powerful android platforms.02:12
*** Ashar has joined #xdandroid02:13
F22same playability, just a bit less taxing for more limited 7X00A chipsets...02:13
RogueAgent[TP2]oh god02:24
F22?02:24
RogueAgent[TP2]no graphics glitches02:24
F22cool02:24
RogueAgent[TP2]most of the time02:24
F22lol02:24
RogueAgent[TP2]but the fps is like 002:24
F22FRX03 may hurt you in angry birds even as it makes android more stable overall.02:25
F22no jit02:26
F22http://alturl.com/8un9o <--- check this out02:26
F22the tp's native msm7X00A brothers aren't officially supported either under the current angry birds release.02:27
F22G1, Magic, Hero, Droid Eris all unsupported...02:28
*** TheDeadCPU has joined #xdandroid02:31
F22a lot of people also seem to be complaining that the last update made the game unplayable.02:33
*** tattrdkat has quit IRC02:38
RogueAgent[TP2]http://xdandroid.com/wiki/Kernel_boot_command-line_parameters02:45
RogueAgent[TP2]also what is jit?02:48
*** tattrdkat has joined #xdandroid02:52
RogueAgent[TP2]F22 looks like your right the force hw 3d is depecated02:55
F22jit=just in time compiler02:56
F22it speeds up program execution in theory02:57
F22java is an interpreted language, not a compiled one.02:57
RogueAgent[TP2]oh02:57
RogueAgent[TP2]so why does it not have one?02:57
F22the jit has been desupported and is apparently buggy.02:58
RogueAgent[TP2]ah ok02:58
F22so it got dropped from xdandroid in frx03 due to the bugs and the fact that it was no longer being developed.03:00
F22hence xdandroid's stability has improved markedly, but it may behave a bit more slowly in particularly demanding applications like angry birds.03:01
F22btw, when i said that people were complaining that the last update made the game unplayable i'm referring to the last update of angry birds. apparently this latest update has made the game more demanding.03:07
RogueAgent[TP2]yeah03:07
F22so there are several factors involved here...03:07
RogueAgent[TP2]i read that03:07
RogueAgent[TP2]time to go find a 3rd party homescreen :P03:07
F22time for me to get some sleep. :D03:07
F22so all is well with my rootfs now?03:08
RogueAgent[TP2]yep03:08
RogueAgent[TP2]ty03:08
F22great :)03:08
RogueAgent[TP2]do you use the default screen or do u have one ud recommend?03:08
F22i have an image that i downloaded of a spiral galaxy that i use as my wallpaper. i'm fine with the google search widget on my default screen since we don't currently have a search button on the panel.03:12
F22oh, btw, your envelope key should also act as search now in that rootfs you downloaded.03:12
F22forgot to mention that one earlier. :D03:12
F22but you need the keyboard open to access that one.03:13
F22anyways, have a good night03:15
RogueAgent[TP2]hmm03:19
RogueAgent[TP2]is the rhodium a hdpi screen03:19
*** TheDeadCPU has quit IRC03:30
*** leobaillard has joined #xdandroid03:33
*** TheDeadCPU has joined #xdandroid03:38
*** aquaviva has joined #xdandroid03:57
aquavivahello all03:57
aquavivai have a issue on xdandroid 2.2 it not detects my sd-card (Internal Storage) on htc diamond, any advice?03:58
*** TheDeadCPU has quit IRC04:01
*** TheDeadCPU has joined #xdandroid04:08
*** TheDeadCPU has quit IRC04:13
*** Ascendedx has joined #xdandroid04:22
*** aquaviva has left #xdandroid05:00
*** TheDeadCPU has joined #xdandroid05:19
*** TheDeadCPU has quit IRC05:36
*** TheDeadCPU has joined #xdandroid06:01
*** hardwalker has quit IRC06:17
*** kalemas has joined #xdandroid06:18
TheDeadCPUI love the Desire Z.06:23
*** Ascendedx has quit IRC06:37
*** zycho__ has quit IRC07:02
*** balans has quit IRC07:03
*** L_miller has joined #xdandroid07:04
*** tattrdkat has quit IRC07:09
*** zycho has joined #xdandroid07:11
*** RogueAgent[TP2] has quit IRC07:18
*** RogueAgent[TP2] has joined #xdandroid07:18
*** tattrdkat has joined #xdandroid07:21
*** TheDeadPHONE has joined #xdandroid07:23
*** TheDeadPHONE has quit IRC07:25
*** tattrdkat has quit IRC07:27
*** balans has joined #xdandroid07:37
*** tattrdkat has joined #xdandroid07:38
*** tattrdkat has quit IRC08:01
*** tattrdkat has joined #xdandroid08:13
*** eR^zeRa` has joined #xdandroid08:42
*** TheDeadCPU has quit IRC08:55
xdandroidDonation received! Thanks, woody, who says: Thanks for all the hard work09:02
*** Kraln has quit IRC09:06
*** Kraln has joined #xdandroid09:07
*** kwoodyusa has joined #xdandroid09:10
*** arrrghhh has joined #xdandroid09:15
*** tattrdkat has quit IRC09:22
kwoodyusahi arrrghhh do you know the status of getting the audio dongle for the tilt2 working?  I looked around on the bug list and did not see it listed.09:22
arrrghhhoh you're one of those poor gsm folks09:23
arrrghhhthat has to use the usb dongle..09:23
arrrghhhno clue09:23
kwoodyusayep :(09:23
arrrghhhi don't think it's going to get fixed anytime soon.09:23
kwoodyusaok just wondering.09:24
arrrghhhit's on a few people's wishlist, but i haven't seen any devs take a serious look at it.09:24
arrrghhhworks on blackstone, so in theory it should be simple to get it working.09:24
arrrghhhbut nothing is simple if you don't know what you're doing ;)09:24
kwoodyusalol well if you could put in a good word i would be willing to "donate"  ;)09:25
arrrghhhlol09:26
arrrghhhyou should be willing to donate regardless :P09:26
arrrghhhand i've already put in a good word09:26
arrrghhhi have an actual 3.5mm jack09:26
arrrghhhso i'd like it working too :P09:26
kwoodyusaI wish i new more about software dev. I would love to do stuff like this.  I am just a netwoking guy... for now.  Thanks for all the help really.  and i have donated twice now09:28
arrrghhhhaha that's cool.09:29
arrrghhhi'm trying to get wistilt to look at it.  camro made it sound easy easy, but i tried... and failed.09:29
*** TheDeadCPU has joined #xdandroid09:29
arrrghhhnate said he was going to look at it again... not sure how far he'll get.09:29
arrrghhhwhat's up TheDeadCPU09:30
TheDeadCPUplaying with the Desire Z.09:30
arrrghhhnice09:31
arrrghhhbroke the kbd yet?09:31
*** uub11 has joined #xdandroid09:32
TheDeadCPUNop09:32
TheDeadCPUNope*09:32
TheDeadCPUNice and superstrong09:32
uub11arrrghhh, thanks for the reply about angry birds but i was just letting people know what i saw09:32
arrrghhhwell i was just letting you know the facts ;)09:33
arrrghhhno clue about this 'angry birds lite'09:33
arrrghhhbut i'm assuming it still requires opengles2.009:34
TheDeadCPUangrybirds lite is just angrybirds with less levels so it takes less space09:34
TheDeadCPUYup09:34
arrrghhhlol09:34
arrrghhhi don't get why people don't get that09:34
arrrghhhyou can't play angry birds on a g109:34
arrrghhhwhat makes you think it'll work on the tp2?09:34
arrrghhhrubes.09:34
TheDeadCPUBut.. They're making a Angrybirds for older devices.09:34
arrrghhhstfu09:34
*** tattrdkat has joined #xdandroid09:34
TheDeadCPUBut that's older as in Hero (Which is allready runs on )09:34
uub11i now it can't run smooth i just thought it had something to do with the memory card not being mounted09:35
uub11now = know09:35
arrrghhhno09:35
arrrghhhhardware limitations.09:35
TheDeadCPUhardware limitations.09:35
arrrghhhthe memory card not being mounted would have nothing whatsoever to do with performance....09:35
uub11even if the information isn't being properly read from the memory card?09:36
arrrghhh...09:36
arrrghhhwhat makes you say that09:36
arrrghhhthe memory card kinda has to be mounted09:36
arrrghhhdespite what android says09:36
arrrghhhif android is running, android has the sd mounted.09:36
TheDeadCPUThere is no memory card when you're running android.09:36
arrrghhhwell.  it's mounted as /sdcard09:37
arrrghhhlol09:37
uub11i know thedeadcpu but then why does the application give the option to transfer off of the sdcard?09:37
arrrghhhuub11, because native android allows you to do it09:37
arrrghhh2.209:38
arrrghhhandroid doesn't know it's running from an SD09:38
arrrghhhit was never technically designed to do what we're doing with it.09:38
uub11well then i am as much of a noob than....09:38
arrrghhhyou can't make assumptions ;)09:38
arrrghhhdont' be like that sherri102309:38
arrrghhhgood lord.09:38
arrrghhhdon't be like her.09:38
uub11true feel like an ass now.....09:39
arrrghhh:P09:39
uub11ok no more talking out of me i'll just lurk and test.....09:39
arrrghhhlol09:39
arrrghhhjust ask questions.09:39
uub11:P09:39
arrrghhhi don't mind answering questions.  just when people make assumptions09:39
arrrghhhlike our builds have a virus09:39
arrrghhhor our builds aren't rooted09:40
arrrghhhmakes me want to stab people.09:40
uub11well that was google marking reefs site wasn't it?09:40
arrrghhhi have no clue what she was talking about.09:40
uub11fine i have a question than......i tried that theme reefs made for his captivate using metamorph and everything worked except the top bar it's not transparent...any ideas?09:41
arrrghhhlol09:42
arrrghhhno clue, i haven't done anything like that.09:42
arrrghhhyou do craziness like that, you gotta figure out how to fix it :P09:42
uub11booooo09:43
uub11i know he had issues initially with the blazin theme and the top bar i think i'm gonna have to ask him09:43
uub11note i said ASK!!!!09:43
arrrghhhlol09:43
arrrghhhjust don't harrass him either.09:43
arrrghhhi'm trying to get him to help me build a new blazn for everyone.09:44
arrrghhhyou harrass the devs, i stab you.09:44
uub11lol09:44
uub11i'm a guinea pig not a nagger09:44
uub11tooooo much09:44
arrrghhhnagger09:44
arrrghhhlol09:44
uub11nagging would be saying "what's taking you so long to make a new blazin build"09:46
arrrghhhyes.  and doing it every day.09:47
uub11every hour.....09:47
uub11ok enough fun i got work to do before i get fired09:47
arrrghhhlol09:47
arrrghhhLOL did anyone see ftvm's "fix" for the battery stutter issue?09:53
arrrghhhhttp://forum.xda-developers.com/showpost.php?p=9374495&postcount=363709:53
arrrghhhclassic09:53
uub11why would someone offr a fix that would never allow a person to charge there phone?09:58
uub11offr=offer09:58
arrrghhhbecause they're insane.09:59
arrrghhh(french)10:00
arrrghhh:P10:00
arrrghhhcuz it supposedly fixes the sound stuttering10:00
uub11lol....ok10:00
uub11hhhhmmmm sound over charging......that's a tough one10:01
*** arrrghhh has quit IRC10:02
*** arrrghhh has joined #xdandroid10:03
arrrghhhdamn laptop.10:04
uub11lol10:04
*** zycho_ has joined #xdandroid10:17
*** RogueAgent[TP2] has quit IRC10:24
*** zycho has quit IRC10:24
*** RogueAgent[TP2] has joined #xdandroid10:24
*** TheDeadCPU has quit IRC10:24
*** arrrghhh has quit IRC10:31
*** emwe has joined #xdandroid10:36
emwehi10:36
*** TheDeadCPU has joined #xdandroid11:10
*** kwoodyusa has quit IRC11:19
*** Ashar has quit IRC11:37
*** Ashar has joined #xdandroid11:48
*** hamagc has joined #xdandroid11:49
*** kwoodyusa has joined #xdandroid11:52
*** kalemas has left #xdandroid11:54
*** arrrghhh has joined #xdandroid12:01
*** ftvm_DIAM100 has joined #xdandroid12:03
*** Naad has joined #xdandroid12:04
NaadArrrghhh: Any idea on the Rhod_100 boot issues?12:13
arrrghhhyou tell me dude12:13
arrrghhhi don't have a 100 :P12:14
Naadhaha, true.12:14
arrrghhhno body from that group has ever come in to hash it out.12:14
Naadwell.. the thing is, it does create a data.img, which is working..12:14
Naadwhen you boot with the 10/23 kernel12:14
arrrghhhwell i doubt that's the issue.12:16
arrrghhhwe need logs man!12:17
NaadWhat i mean is that the linux boot is going on, but doesn't show. (with new kernels)12:17
arrrghhhi now12:17
arrrghhhknow*12:17
Naadok.. how can i get you those :) does it create a log without booting completely?12:17
arrrghhhbut we need logs to determine what exactly is going on12:17
arrrghhhwell12:17
arrrghhhyou can make it :P12:17
arrrghhhso what happens12:17
arrrghhhi hear it freezes at the haret screen12:17
arrrghhhno?12:17
Naadyes12:18
arrrghhhoh.12:18
arrrghhhseems we may need haretconsole or some such thing...12:18
arrrghhhdamnit i don't get how that's a kernel issue12:18
arrrghhhhave we ruled everything out?!?12:18
TheDeadCPUwoop12:18
Naaddone format a few times with HP and panasonic12:18
XirXesif it wasnt a kernel issue you would still see some text12:19
arrrghhhi didn't think the kernel kicked off that quick... does it?12:19
Naadbut the weird thing is, a new, working data.img is created12:19
arrrghhhi thought initrd starts first, then loads the kernel.12:19
arrrghhhthat doesn't make sense12:19
XirXesthe first thing haret does is load the kernel12:19
arrrghhhit's gotta be booting12:19
arrrghhhhrm12:19
Naadbut not all the way, and doesn't display anything12:20
XirXeswell yeah but to show anything it has to load the kernel12:20
Naadbut it only creates the data.img when the kernel is loaded?12:20
XirXesit would have stopped before that point.12:21
XirXesif the kernel wasnt loaded. we deff need logs12:21
Naadit does create a data.img12:21
arrrghhhXirXes: do you know how we'd get logs if it's hanging at that point?12:22
XirXesnope12:22
arrrghhhyou can put an entry in the user.conf file12:22
arrrghhhbut i don't think that would happen if it's hanging where it is...12:22
arrrghhhwe've ruled out startup.txt files?12:23
Naadyes..12:23
Naadtried without overclock/hw3d12:23
arrrghhhi've talked with a few guys on xda12:23
arrrghhhwell is the zImage set correctly12:24
arrrghhhetc12:24
arrrghhhmatching the name, y'know12:24
Naadset KERNEL zImage right?12:25
Naadrel_path is also set correct12:25
Naadleft out pmem.extra msmts_calib12:26
Naadhow would you normally create a log? could try it at least.12:26
ftvm_DIAM100hello all12:28
arrrghhhNaad: does the kernel match that name?12:31
arrrghhhis the rootfs named correctly?12:31
Naadyes12:31
arrrghhhwell normally you'd get a log from adb12:31
arrrghhhbut i don't think that'll work since the boot process is hanging12:31
arrrghhhwhat's the last kernel that works on it12:31
arrrghhh10/23?12:31
Naadyeah12:31
Naadthe first 10/2312:32
Naadfrom the one posted later that day problems started12:32
uub11does it go past the bootanimation?12:32
arrrghhhhrm12:32
Naadno, gets stuck on haret.exe12:32
arrrghhhuub11: lol it never even makes it to the flying text dude... keep up :P12:32
arrrghhhwell12:33
arrrghhhthere were a lot of commits that day12:33
uub11just got back from lunch12:33
uub11=)12:33
arrrghhhadsp 6125 tables12:33
arrrghhhand autobl12:33
ftvm_DIAM100please ... what setting for avoid black screen of the death ???    ps sleep ???12:33
arrrghhhit's the rhod100 guy's fault for not testing this :P12:33
Naad10/23 014031 it is12:33
arrrghhhftvm_DIAM100: pm.sleep12:33
arrrghhhusually only applies to OC12:33
ftvm_DIAM100ok ....12:34
uub11we have all seen each rhod have it's own quirks does it even have autobl support?12:34
ftvm_DIAM100where do I put this ???12:34
arrrghhhstartup12:35
ftvm_DIAM100ok12:35
Naadthe rhod100_uk has autobacklight in windows mobile12:35
arrrghhhNaad: ...12:35
ftvm_DIAM100what command exactly, please ?12:36
arrrghhhdamnit jim12:36
arrrghhhread babijoee's thread.12:36
F22post 10/23 kernels are making new data.img's before they hang on the 100's? did i hear that correctly?12:36
Naadthey get visually stuck on haret.exe12:37
Naadbut do create a data.img12:37
arrrghhhF22: evidently.12:37
F22data.img creation is done by the init script12:37
arrrghhhi don't see how, it supposedly doesn't get that far in the boot process12:37
uub11maybe it's just visual?12:38
F22possibly people are confusing text mode with haret?12:39
uub11sometimes my screen goes black and i can't do anything, i act like i'm going to shut down the phone and back out of it and it starts working again12:39
uub11the i get a system force close12:39
uub11then12:39
arrrghhhuub11: not what we're talkin bout.12:40
uub11=p12:40
ftvm_DIAM100pm.sleep ... avoid black screen of the death ???12:40
NaadF22 what do you mean with confusing text mode and haret?12:41
F22linux doesn't need a gui to run, people may be assuming it's stuck on haret when the linux kernel is up.12:42
uub11technical version of what i meant ^12:43
Naadyes, that's what i said at first :)12:44
Naadmaybe it's just the display drivers (or something like that) not kicking in12:44
F22can you adb into it to get a dmesg?12:45
NaadI was asking before how to get a log.. sort of a noob xD12:46
F22hmm...not sure myself on what sorts of logs you can get at this point. adb might work if it's up. but if the problem occurs before adb comes up that might not work.12:50
*** kwoodyusa has quit IRC12:51
F22adb is part of the android sdk.12:52
F22which you can download from google12:53
Naadthnx. Downloading as we speak.12:54
arrrghhhyea12:54
arrrghhhadb would be interesting if you can get in12:54
arrrghhhotherwise we can try the user.conf trick12:54
arrrghhhsince it creates the data.img, maybe we'll get lucky.12:54
arrrghhhftvm_DIAM100: nothing solves that problem completely...12:54
*** Aks has joined #xdandroid12:54
arrrghhhi quite often have the urge to tell you to stick to winmo lol12:54
TheDeadCPUlol12:57
*** |Jeroen| has joined #xdandroid12:58
ftvm_DIAM100ok arrrghh ... but, what's the write ???13:00
F22=213:03
TheDeadCPUsudo rm -rf /*13:04
F22lol13:05
*** JesusFreak316 has joined #xdandroid13:10
arrrghhhoh god13:14
arrrghhhdon't listen to him13:14
*** |Jeroen| has quit IRC13:14
TheDeadCPUlol13:14
arrrghhhftvm_DIAM100: what's your question13:15
hamagcsudo rm -rf /system/*13:16
hamagclol thought that was funny13:17
hamagcmaybe rm -rf /data/* ?13:17
ftvm_DIAM100my question is ... please, what command line exactly ??? :(13:18
arrrghhhdid you read the thread?13:18
arrrghhhbabijoee goes thru most if not all of the commands available13:18
ftvm_DIAM100no, i no look the post ...13:19
ftvm_DIAM100sorry13:19
arrrghhhwell do it.13:19
arrrghhh:P13:19
*** L_miller has quit IRC13:25
F22arrrghhh, what's the user.conf trick you mentioned earlier?13:28
arrrghhhbasically putting a dmesg statement in there13:29
arrrghhhy'know that rm -rf /sdcard/*.rec statement we put in there?13:29
arrrghhhsame thing, just dmesg > /sdcard/dmesg.txt or whatever.13:29
F22ah13:29
arrrghhh:D13:29
arrrghhhnot pretty, but hey sometimes it gets us logs when phones don't boot.13:29
hamagclol13:30
arrrghhhdid he ever get adb to work?13:30
F22whatever gets done the job done. :D13:30
arrrghhhdude kinda disappeared.13:30
arrrghhhindeed13:30
F22dunno, last i heard he was working on downloading adb.13:30
arrrghhhja13:30
arrrghhhoh well.13:30
arrrghhhthose rhod100 guys13:30
arrrghhhwe need a committed tester from that group :P13:30
*** Reefermattness has joined #xdandroid13:30
F22that we do13:30
arrrghhhi thought we tested autobl on their damned phones.13:30
arrrghhhReefermattness!  what's up dude.13:31
ReefermattnessSup arrrghhh13:31
arrrghhhpeople are startin to bug be about blazn now :P13:31
Reefermattnessjust re-setting up my pc13:31
Reefermattnesslinux mint 10 is next13:31
F22startin? lol, they've been bugging you about it for awhile now. ;)13:31
Reefermattnessyeah F22 but now they are butting him not me  :P13:31
F22lol13:32
arrrghhhthat's the idea13:32
arrrghhhassuming i can start pumpin 'em out i have no problem13:32
arrrghhhbut i haven't even started really :P  you sound like you're pretty much done tho eh?13:33
Aksthere was a build yest for blazn ?13:33
NaadSorry guys, girlfriend interrupted haha. Don't have adb running... yet :) will take a bit for me to figure out how that stuff works. Working on osx.13:36
arrrghhhew.13:37
Reefermattnesswell pretty much done yeah but its still the same part ive been stuck on for a while now13:37
* arrrghhh stabs Aks in the eye13:37
ftvm_DIAM100 ok,  I'll get the post   arrrghhh !13:40
arrrghhh..13:41
Reefermattnessfigure out how to change the clock to white with out FC errors and we are done13:42
arrrghhhhrm13:49
arrrghhhsince i don't even know what you do to get blazn where it's at...13:49
arrrghhh:P13:49
ftvm_DIAM100hmmmmmmmmm sorry ...  i not found the post of babyjoe ... :(13:50
F22Naad: something else to try. rename your ts-calibration file. it would be interesting to see whether or not the calibration program gets run on boot, and if it does, whether or not there are any issues.13:51
NaadThanks, will try13:52
Naadhave gotten adb running with the working kernel :) I'll get there haha.13:52
Reefermattnessarrrghhh, i dont need you to finish it, thats the only 1 bug thats keeping it from release.  If you can do it on frx03 then we are set13:52
arrrghhhk13:52
Naadnow gonna try newest kernel, change calibration file13:52
Reefermattnessif we can just figure that out then ill theme it and throw it online.13:52
ftvm_DIAM100this post is on thread http://forum.xda-developers.com/showthread.php?t=71169213:52
arrrghhhftvm_DIAM100: it's in the first four posts of the main thread...13:52
Naadif that doesn;'t work i'll try adb13:52
F22ok :)13:53
ftvm_DIAM100euhhhhhhhhhhhhhhhhhhhh13:53
NaadI'll post here later tonight, pizza in between :) thanks!13:53
ftvm_DIAM100i'm stupid !!!13:53
arrrghhhyes, it's there ftvm_DIAM100..13:53
uub11arrrghhh did you fix the theme yet???13:53
uub11=)13:53
uub11sorry13:53
uub11back to work13:53
arrrghhhReefermattness: i'll play around.  not even sure how to change the color in the clock tbh.  i'm sure i need some metamorph magic.13:53
Reefermattnessno actually its hex editing and xml editing13:54
arrrghhhquit trolling dude... leave that to stinebd.13:54
Reefermattness:)13:54
arrrghhhah13:54
arrrghhhi can do xml13:54
arrrghhhi'm sure i can learn hex, i used to edit hex files all the damned time.13:54
arrrghhhbeen a while tho...13:54
*** Kraln has quit IRC13:54
uub11i said sorry!13:55
uub11couldn't resist13:55
F22the init script is responsible for handling both the creation of data.img which you've told us gets done, and for calibrating the screen, although data image creation is close to the beginning while screen calibration is near the tail end of it. but all that happens before init.android gets run.13:55
*** Kraln has joined #xdandroid13:56
uub11Hey reefs nice work on that gloss theme for the captivate, i tried on my touchpro2 and it's pretty decent just something's i'm gonna have to learn to fix13:56
arrrghhhlol13:57
NaadAah thanks F22, things start to make sense :)13:57
ReefermattnessThanks dude, how much actually worked on the tp2 from that MM?13:58
uub11honestly most of it except the dialer buttons and the top curtain13:59
uub11but i read somewhere metamorph won't change the top curtain14:00
Reefermattnessnice, i had not personally tried it but figured most of it would work since we switched to HDPI for the TP214:00
arrrghhhschweet.14:00
arrrghhhyea the old blazn build is so old... it was before the hdpi switch lol.14:00
uub11lol14:01
uub11so it looks like i'm gonna have to check the xml file like arrrghhh if i want to make changes?14:01
Reefermattnessxml or hex yeah depends on if you use apk tools to decompile it or not14:03
NaadDevice is recognised with adb i believe14:04
arrrghhhadb shell works?14:04
uub11ok14:04
arrrghhhyou get a prompt?14:04
F22how did you check?14:04
arrrghhhlol14:04
arrrghhhtag-team troubleshooting14:04
F22lol14:05
F22yup14:05
Naaduhm.. well if i type adb devices in terminal (osx) it recognises a device14:05
arrrghhhadb shell14:05
arrrghhhwhat does it do14:05
Naad#14:05
F22try sh--ninja'd :P14:05
arrrghhhawesome14:05
F22cool14:05
arrrghhhand your phone is currently at the frozen haret screen?14:05
Naadyes14:06
arrrghhhsiiiick14:06
arrrghhhexit out of that14:06
F22i assume the screen calibration worked too then.14:06
arrrghhh(just exit)14:06
arrrghhhand dump a dmesg.  you can just do adb shell dmesg > dmesg.txt14:06
F22screen calibration gets done beefore the adb server is set up.14:06
Naadi renamed the calibration file btw, so didn't even calibrate14:07
Naadso i typ 'adb shell dmesg > dmesg.txt'14:07
arrrghhhyes14:07
arrrghhhit'll output a file, dmesg.txt whereever you run that from14:07
F22well if adb is working, you don't need to worry about the calibration, that would be more of an issue if adb weren't working.14:07
F22*points to what arrrghhh said about the dmesg, "what he said". :P14:08
Naadget: 'cannot create dmesg.txt: read-only file system14:08
F22write it to /sdcard14:09
F22er /sdcard/dmesg.txt14:09
Naadok, done14:10
Naadbut.. now it's on the sdcard, how do i get there with a non functioning phone?14:10
F22adb pull14:10
F22exit14:10
F22adb pull /sdcard/dmest.txt14:10
arrrghhhoh i'm sorry14:11
F22it will pull the file from the phone onto your computer14:11
arrrghhhi thought adb would dump stuff to your local fs...14:11
arrrghhhmight want to spell dmesg right tho :P14:11
F22it will if he runs the command on the same line as the shell14:11
F22but once he shells on, it's all local to the phone.14:11
F22shells in14:12
arrrghhhi had it on one line :P14:13
F22that you did14:13
F22notice i used the word "he", not "you". ;)14:14
Naadhmm... doesn;t seem to work14:14
F22the pull doesn't?14:14
F22er, the command line i gave you wasn't spelled right.14:15
Naadyeah i noticed14:15
F22was that it? or did it still not work even after spelling dmesg.txt correctly?14:15
Naadho, it works now, forgot to exit14:16
F22lol14:16
Naad:) I'm learning14:16
Naadso, i should maybe post this file somewhere..14:16
arrrghhhhehe14:17
arrrghhhyes14:17
arrrghhhpastebin14:17
arrrghhhor you can file a bug14:17
F22no worries. we've all been there at one point or another. adb grows on you though. it's quick and easy to use once you're used to it and very flexible.14:17
arrrghhhand attach the .txt file to the bug14:17
arrrghhhuntil it breaks...14:17
F22that's because you're using it on windows... ;)14:17
arrrghhhdamnit i hate windows and the stupid way it handles hardware drivers.14:17
arrrghhhyea... not much choice here friend :P14:17
F22my condolences14:18
arrrghhhlol14:18
arrrghhheveryone tells me to just run a vm... doesn't work so well when the hardware is crap.14:18
F22true14:18
arrrghhhi just don't get why a driver that worked before, now no longer works...14:18
*** Jeff_XDA has joined #xdandroid14:19
Naadi'll file a bug :)14:19
arrrghhhi pointed it to this usb driver before...14:19
Naadit's kernel related right xD14:19
arrrghhhlol yes14:19
arrrghhhi would definitely say so14:19
F22it's moody? :P14:19
arrrghhhhahaha14:19
arrrghhhi think i am using a different usb port.14:19
arrrghhhand windows is stupid and doesn't handle it well14:19
arrrghhhi'm also being stubborn, i don't want to change usb ports.  seems i may have to bite the bullet.14:20
F22lol, the usb port matters?14:20
JesusFreak316According to me. :P14:21
arrrghhhwell i think JesusFreak316 is right in the sense that windows thinks it's a different device14:21
xdandroidNew XDAndroid Releases bug 64 filed...14:21
xdandroidBug http://bugs.xdandroid.com/show_bug.cgi?id=64 normal, Normal, ---, developers, NEW, Rhod100_xx not booting after 10/23 kernels14:21
arrrghhhas in if you install something to one usb port, it'll reinstall the drivers if you put it in a differen one14:21
arrrghhhi'm so closing that bug14:21
arrrghhh:P14:21
JesusFreak316That's not what I said...14:21
F22great, finally have a bug report for that.14:21
F22and even better, a dmesg to go with it.14:22
JesusFreak316I just know that fronst usb ports don't work as well as some devices as rear motherboard usb ports.14:22
arrrghhhJesusFreak316: well that is what seems to be happening.14:22
arrrghhhLOL14:22
arrrghhhthis isn't a desktop dude.14:22
JesusFreak316Well then, I'll take the credit. :)14:22
*** Jeff_XDA has left #xdandroid14:22
JesusFreak316Oh yeah.14:22
NaadWell, now i really have to get myself a pizza :) so i'll be gone for a bit!14:22
F22enjoy your pizza Naad.14:23
NaadThanks for talking me through all this :) I'll check in later (live in Netherlands, so won't stay so long xD 8.23 pm now)14:23
arrrghhhdamnit14:25
arrrghhhso far different port has turned up nothing.14:25
JesusFreak316I had a dream last night it was Christmas. :(14:25
arrrghhhi hate you windows.14:25
JesusFreak316adb drivers?14:25
arrrghhhyes.  nothing works for that XDA hardware14:25
arrrghhhthat's the only one we need to point the drivers to correct?14:25
JesusFreak316Does for me...14:25
arrrghhhthe other two cdc can ignore14:25
arrrghhhwell it did for me once14:26
arrrghhhbut now it's not.14:26
arrrghhhexact same driver i used before14:26
JesusFreak316You tried deleting the driver and letting windows redownload it?14:26
arrrghhhfawk.  always gives me the stupid "Cannot install this hardware" prompt when i point it to the drivers.14:26
Naadbtw, i can't call myself, so it doesn't boot so far./ now really pizza =D14:26
arrrghhhletting windows redownload it?14:26
JesusFreak316Via windows update.14:26
arrrghhhit's not a driver from windows.  you get it with the sdk.14:26
arrrghhhwindows update doesn't have the driver...14:26
arrrghhhi thought you setup adb on your windows machine before14:27
JesusFreak316Either way, it installed it automatically when I plugged it in.14:27
arrrghhhwtf?14:27
arrrghhhi've never had it install automatically14:27
JesusFreak316:)14:27
arrrghhhi am using xp at work and 7 at home.14:27
JesusFreak316I'm on 7.14:27
arrrghhhi'm calling BS.14:28
arrrghhheveryone get your broomsticks!14:28
JesusFreak316You do that.14:28
arrrghhhsorry that's schenanigans.14:28
TheDeadCPUwut14:28
F22logcat might be useful too, this seems to be happening while init.android is setting up services.14:28
arrrghhhlogcat probably would be useful...14:28
arrrghhheven if it does only show userland stuff.14:28
arrrghhhFFFFFFFFUUUUUUUUUU XP14:28
TheDeadCPUlolwut14:29
arrrghhhadb broke itself again.14:29
arrrghhhand i've followed like 100 guides to try and fix it.14:29
TheDeadCPUlol14:29
F22time to write your own... ;)14:29
arrrghhhone guide even had me download some usb driver tool that deleted some hidden drivers or some such nonsense.14:29
arrrghhhlol14:29
arrrghhhor just forget about working on my phone at work :(  then i might have to work!14:30
F22terrible thought14:30
arrrghhhisn't it tho?14:30
JesusFreak316I'm just saying go to device manager, go to properties for your device, uninstall the device, then let it search for drivers.14:30
JesusFreak316Works for me.14:30
*** MrObvious has joined #xdandroid14:31
arrrghhhJesusFreak316: i've tried that... tons.14:31
JesusFreak316Well then...14:31
arrrghhhif it was that simple, i would've resolved this instantly lol14:31
JesusFreak316Does that work at home?14:31
JesusFreak316on 7?14:31
arrrghhhc'mon i know basic troubleshooting.  i need advanced tatics here.14:31
arrrghhhyes...14:32
arrrghhhbut it used to work here14:32
arrrghhhon XP14:32
arrrghhhit's broken once before... i somehow fixed it.  i think i just reinstalled the drivers.14:32
JesusFreak316I don't have any xp devices left.14:32
arrrghhhyea well i don't have much choice :P14:32
arrrghhhwe'll probably go to 7 *eventually*14:32
arrrghhhugh.  it's so easy in linux.14:33
JesusFreak316Yep. If only it had Intel VRT.14:33
JesusFreak316Why can't you dual boot?14:33
arrrghhhwell.  i do occasionally work.14:34
JesusFreak316You need windows to work?14:34
arrrghhhi have a lot of downtime at work, but not that much :P  i gotta be able to fix crap immediately.14:34
arrrghhhyes.14:34
JesusFreak316Not much of an IT guy, eh? :P14:34
arrrghhhunfortunately.14:34
arrrghhh...14:34
arrrghhhseriously?14:34
JesusFreak316Real nerds use linux for everything.14:34
JesusFreak316jk14:34
arrrghhhnot at work...14:34
JesusFreak316I know...14:34
JesusFreak316:(14:34
arrrghhhi used to use linux at my old job14:35
arrrghhhmy boss hated it14:35
arrrghhhbut i didn't care, i could get around it14:35
arrrghhhhere... not so much.  there's too much here that requires windows.14:35
arrrghhhtrust me, if i could get around it, i would.  infosec would probably have a heart attack tho lol.14:35
arrrghhhthey won't even let me use linux at home.14:35
arrrghhhthey're dicks.14:35
JesusFreak316Can't you just hibernate windows every time you boot linux and be back in a minute though?14:35
JesusFreak316Oh.14:35
arrrghhheh perhaps14:36
arrrghhhi'd rather not deal with it tho.14:36
JesusFreak316Does droidexplorer install drivers?14:36
eR^zeRa`they wont you let use linux at home?14:37
eR^zeRa`wtf?14:37
arrrghhhit has drivers.14:37
eR^zeRa`what they care what you use at home?14:37
arrrghhheR^zeRa`: well... i have work from home privileges.14:37
arrrghhhand i need remote access because i'm on call sometimes.14:37
JesusFreak316Does droidexplorer just not work though?14:37
MrObviousOk so I have weird button mappings. I haven't used XDAndroid in a few months since I got a Droid Eris. I let my wife use it since her phone went pfffffffffftttttt. The button mappings are different it seems like.14:37
eR^zeRa`aha14:37
arrrghhhMrObvious: yes14:37
arrrghhhthey changed...14:37
arrrghhhread up :P14:38
MrObviousThe power key is a power key, and so is the call end button. And there is no menu button.14:38
arrrghhhlots has changed14:38
eR^zeRa`I thought they wont let you use linux for you own personal matters :D14:38
arrrghhhugh.14:38
arrrghhhnot this again.14:38
MrObviousarrrghhh: :p14:38
arrrghhheR^zeRa`: lol no that would be illegal... i'm pretty sure.  we don't live in the USSR :P14:38
JesusFreak316Menu is center, silly.14:38
arrrghhhJesusFreak316: on rhod14:38
MrObviousOh.14:38
MrObviousOk.14:38
JesusFreak316Oh, derp.14:38
MrObviousI'd read up if I knew where derr.14:38
eR^zeRa`well there's no USSR anymore14:38
eR^zeRa`:D14:38
arrrghhhderp indeed.  MrObvious there's several options14:38
arrrghhhwell where did you download your update?14:39
arrrghhhif it's a forum... i'm sure it's been hashed out there like 100x.14:39
MrObviousIt's the update you built yesterday.14:39
arrrghhhso you are on raph?14:39
Naadi read someone wanted logcat?14:39
arrrghhhNaad: may be helpful.14:39
MrObviousDIAM500.14:39
arrrghhhadb logcat > logcat.txt14:39
arrrghhhMrObvious: i'm sorry.14:39
JesusFreak316HAH, NOT DERP!!!14:39
arrrghhhbut i think JesusFreak316 is right in this case then.  center is menu.14:39
arrrghhhlol14:39
Naadok, i'll do and add to bugreport14:39
arrrghhhNaad: thanks14:40
MrObviousI think I got it now. :)14:40
MrObviouslol14:40
JesusFreak316Yeah, there's no select button anymore. :(14:40
MrObviousI know. Grr!14:40
arrrghhhtouch the screen?14:40
arrrghhhlol14:40
JesusFreak316On RAPH you can use enter on the HW keyboard but Diamond has no such luck.14:40
arrrghhhah crap.  i hope my server rebooted because it was supposed to...14:40
arrrghhh...tap the screen?14:41
MrObviousThat's what I'm gonna do.14:41
arrrghhh:D14:41
JesusFreak316Our screen is only 2.8 in.14:41
arrrghhhawwwwww14:41
MrObviousI wish Swype would work though in Android.14:41
JesusFreak316Sometimes zooming is painful.14:41
arrrghhhit does14:41
eR^zeRa`I was wondering14:41
arrrghhhi couldn't figure out swype tho14:41
MrObviousI got a beta account and I use it on my Droid Eris but I think the Diamond is VGA.14:41
arrrghhhsucked imho14:41
arrrghhhdiam is vga14:41
MrObviousIt only works on HVGA and WVGA.14:41
MrObviousI think.14:42
arrrghhhah.14:42
arrrghhhbummer14:42
MrObvious(last I checked)14:42
Naadcreating a logcat.txt takes a while right?14:42
arrrghhhi thought diam/raph could use swipe14:42
arrrghhhNaad: well it runs infinitely14:42
arrrghhhso kill it now14:42
eR^zeRa`I dont really have an idea about how things evolve around android and TP214:42
arrrghhhctrl-c14:42
Naadhaha ok14:42
arrrghhheR^zeRa`: people break stuff, others fix 'em...14:42
eR^zeRa`is there an ETA for NAND boot on tp2?:D14:42
arrrghhhtomorrow14:43
arrrghhhlol it's already out dude14:43
arrrghhhtp2 has had nand for... months?14:43
MrObviousIs battery life still bad on CDMA?14:43
arrrghhhit's not good for anyone MrObvious14:43
JesusFreak316Isn't the NAND incomplete though?14:43
arrrghhhbut it's significantly better.14:43
arrrghhhJesusFreak316: what is complete!??!14:43
arrrghhhlol14:43
eR^zeRa`I mean stable and fully working version :D14:43
uub11what isn't inicomplete14:43
arrrghhheR^zeRa`: what is stable... :P14:44
JesusFreak316I mean at least equivalen to the SD one.14:44
eR^zeRa`last time I checked there wasnt even the mic working when making a call14:44
arrrghhherm14:44
arrrghhhnand is probably ahead of haret at this point14:44
uub11i think acl has said they are up to date14:44
JesusFreak316Yeah, I don't understand the desire to run it as NAND currently.14:44
arrrghhhit just got .35 commit so in theory nand can run .35 now.14:44
JesusFreak316On HD2, sure since they have camera and stuff, but not on here yet.14:44
eR^zeRa`whats .35?14:44
arrrghhhkernel version14:45
JesusFreak316Linux kerne.14:45
arrrghhh2.6.3514:45
uub11hopefully they commit .35 next for haret14:45
JesusFreak316Man, I typoed and still got ninja'd.14:45
arrrghhhlol probably not.14:45
arrrghhhuub11: if it ever does, it'll be quite some time.14:45
uub11=(14:45
arrrghhhthat's the problem with this project14:45
arrrghhhthere's so many phones that it supports14:46
NaadE/libEGL  ( 1489): No EGLDisplay for hardware EGL!14:46
uub11ok now i'm really going back to work14:46
arrrghhhit's hard to keep every single change working on every single device.14:46
Naadis that normal?14:46
eR^zeRa`arrrghhh can you gimme a link to some forum that deals with end-user stuff around this ?14:46
Naadi post it now.14:46
uub11yeah i saw in the logs alex and acl talking about the whole process14:46
arrrghhheR^zeRa`: uhm... there's xda-devs and ppcg.14:46
arrrghhhuub11: so you know then...14:46
JesusFreak316How do people find this channel apart from xda? xdandroid.com?14:47
uub11yeah wishful thinking that's all14:47
arrrghhhJesusFreak316: i have no clue lol.  somehow everyone finds #htc-linux first too.14:47
eR^zeRa`yeah well I visit xda every day, but I'm getting a bit disoriented at times14:47
eR^zeRa`I mean in the android dev thread14:47
JesusFreak316Which one, lol?14:47
arrrghhheR^zeRa`: yea there's a bunch...14:48
Naadlogcat.txt is posted with BUG#6414:48
xdandroidBug http://bugs.xdandroid.com/show_bug.cgi?id=64 normal, Normal, ---, developers, NEW, Rhod100_xx not booting after 10/23 kernels14:48
JesusFreak316The Touch Pro/Fuze one is the main one.14:48
arrrghhhNaad: i see that, thanks.14:48
arrrghhhJesusFreak316: for you :P14:48
JesusFreak316Well, that's where most of the updates go.14:48
arrrghhhthanks to babijoee14:48
arrrghhhand partially me.14:48
arrrghhhreef is lazy updating his threads :P14:48
uub11lol14:49
arrrghhhi wish there was more information14:49
arrrghhhwhy can't you install this driver windows14:49
arrrghhhWHY14:49
arrrghhhugh.  nate is the windows whiz.  i need him to save my dumbass.14:49
JesusFreak316nate?14:50
arrrghhhnatemcutty or whatever14:50
JesusFreak316Oh, him.14:50
JesusFreak316So, what drivers ARE installed?14:50
eR^zeRa`arrrghhh what thread should I read first?14:50
arrrghhhJesusFreak316: afaik none14:50
arrrghhhi removed all of them (in theory)14:50
JesusFreak316:/14:50
arrrghhheR^zeRa`: uhm.. what device?14:50
eR^zeRa`TP214:51
arrrghhheR^zeRa`: probably that thread.14:51
JesusFreak316http://forum.xda-developers.com/showthread.php?t=62799714:51
arrrghhhreef's faq in that thread is awesome.14:51
JesusFreak316http://sites.google.com/site/androidport/faq14:51
arrrghhhyea that one :P14:51
JesusFreak316That whole google site is awesome.14:51
arrrghhhi've installed adb no problem on this machine before, so something is stuck in there.14:52
arrrghhhi just don't get what.14:52
arrrghhhi guess i should try a different profile14:52
arrrghhhi don't know what difference that would make with hardware, but knowing windows it'll make all the difference.14:52
JesusFreak316Have you tried droidexplorer? Just curious?14:52
arrrghhhoh yea14:53
arrrghhhthat's what i use to get adb...14:53
arrrghhhcuz i'm lazy :P14:54
JesusFreak316So it just doesn't connect?14:54
eR^zeRa`well maybe I wrote something else than I meant14:54
arrrghhhis there something specific i should be doing with droid explorer?14:54
JesusFreak316No devices found?14:54
arrrghhhJesusFreak316: yea.  0 devices found, every time.14:54
eR^zeRa`that thread is for SD boot via HARet14:54
arrrghhhwell, before it worked.14:54
arrrghhheR^zeRa`: you want the nand thread...14:54
arrrghhhthat's ppcg only14:54
JesusFreak316You're looking for NAND?14:54
eR^zeRa`yep14:54
arrrghhhwhich i can't get to load14:54
arrrghhhfor some reason14:54
JesusFreak316downforeveryoneorjustme.com14:55
arrrghhhhttp://forum.ppcgeeks.com/forumdisplay.php?f=17914:55
arrrghhhit's in that section whenever it's back up.14:55
eR^zeRa`k thx14:55
eR^zeRa`I'm using NRG roms atm14:55
eR^zeRa`but well ...14:55
arrrghhhok...14:56
eR^zeRa`I'm getting bored of it14:56
eR^zeRa`but I dont know what to expect14:56
eR^zeRa`I mean14:56
arrrghhhdon't jump into nand dude.14:56
arrrghhhit's really only meant for testing.14:56
arrrghhhjust like this entire project, don't expect it to replace winmo.14:57
arrrghhhi think that's everyone's mistake... they assume this is meant to replace winmo.14:57
eR^zeRa`well I thought it's too early for that14:57
arrrghhhindeed14:57
arrrghhhbah14:58
arrrghhhi guess i need to take a lunch.14:58
arrrghhhmust... fix... adb...14:58
*** LeTama has joined #xdandroid14:59
eR^zeRa`must... save... porn...14:59
eR^zeRa`what a resemblence14:59
arrrghhhlol14:59
eR^zeRa`http://newfunnypictures.net/data/media/11/Must%20Save%20Porn!.jpg15:00
eR^zeRa`in case you dont already know it :D15:00
arrrghhhah yes15:00
arrrghhhi just thought you wanted to save your porn.15:00
eR^zeRa`nope, I dont download that kind of stuff15:01
arrrghhhstupid.  windows always detects something there... just refuses to use the drivers i point at it.15:01
eR^zeRa`at least I dont keep it on my HDD15:01
eR^zeRa`:D15:01
arrrghhhdamnit unless it's about fixing my adb i don't care :P15:01
eR^zeRa`:D15:01
eR^zeRa`whats adb15:01
eR^zeRa`:D15:01
*** programmer8922 has quit IRC15:07
F22interesting, two microp lines in his dmesg that are not in mine, one clearly relating to bl. need to look at the kernel code to see why it's printing them.15:07
arrrghhheR^zeRa`: ever heard of google?  lol15:15
arrrghhhandroid debugging bridge15:15
arrrghhhF22: hrm... i swore we tested the 10015:15
arrrghhhperhaps we didn't.15:15
eR^zeRa`google? is it some sort of yahoo anwsers?15:16
arrrghhhinda15:16
arrrghhhkinda*15:16
eR^zeRa`just kidding :D15:16
eR^zeRa`it's like my homepage15:16
arrrghhhyea i know :P15:16
arrrghhhdick15:16
arrrghhhReefermattness: did you see that russian dude's post?15:17
eR^zeRa`is it just me or did you actually call me a dick? :o15:17
F22at least one of the lines he's getting that i'm not (haven't checked the other one yet) is printed by drivers/i2c/chips/microp-klt.c which was edited in the Oct. 23rd commit.15:17
F22it's a status report of some sort15:18
arrrghhheR^zeRa`: yes.  i called you a dick.15:18
arrrghhhF22: hrm...15:18
eR^zeRa`:/15:18
*** uub11 has quit IRC15:19
eR^zeRa`I think we cant be friends anymore.15:19
arrrghhhdidn't realize we were friend.15:19
arrrghhhs15:19
arrrghhhlol15:19
F22this one: [    2.142059] micropklt_spi_bl_status_print: light sensor auto=10=0x0a SPI=136=0x8815:19
* arrrghhh has no friends. and that's how /me likes it :P15:19
arrrghhhF22: you don't get that?15:19
F22nope15:20
F22not in my dmesg15:20
F22only in his.15:20
eR^zeRa`anyway15:20
arrrghhhhrm15:20
arrrghhhthat is odd15:20
eR^zeRa`Do you know that joke with "no" and "me neither"?15:20
arrrghhheR^zeRa`: we're trying to hash something out... do you mind?15:20
eR^zeRa`nope, go ahead15:20
arrrghhhF22: well i wouldn't know where to begin with wistilt2's commit on autobl.15:21
arrrghhhi'm sure that's the problem tho, based on the reports... and the dmesg seems to confirm it.15:21
arrrghhhi wonder if their sensor uses a different code.15:21
arrrghhhdifferent gpio that is15:21
F22hah! and the other line is defined in a different function within the same file!15:21
arrrghhhhm?15:22
F22the other line that is different: [    2.142364] micropklt_panel_resume15:22
arrrghhhhm15:22
Reefermattnessthats not quite.... correct15:22
Reefermattnessbut thats what i was gonna try if we couldnt fix it the right way15:22
Reefermattnessthats just a hybrid what he did there15:23
Reefermattnesslol15:23
arrrghhhlol15:23
arrrghhhhe claims it works15:23
arrrghhhi wonder what's messed up.15:24
arrrghhhpretty simple hack lol.  just grabbed your modded apk basically.15:24
F22so the story is that the 1st commit on the 23rd still works, but the 2nd breaks rhod100's?15:26
arrrghhhi believe that is the story, correct sir.15:27
F22that's a smaller edit.15:28
F22only changed that one file15:28
F22the earlier one was much larger.15:28
arrrghhhhm15:28
arrrghhhdid it enable something...?15:28
F22Add the possibility to change auto_bl setting on the fly through dbgfs15:28
arrrghhhyea15:28
*** L_miller has joined #xdandroid15:30
NaadSounds like you guys are getting somewhere!15:31
NaadIndeed the first commit from 10/23 works, second breaks15:31
arrrghhhnarrowing it down :15:32
NaadWell, at least it getting to the cause... should've come here earlier and file a bugreport right? :P15:34
arrrghhhprobably :P15:34
arrrghhhor been here to test autobl in the first place haha.15:34
arrrghhhi swear we tested the 100, but i have no clue who it was.15:34
arrrghhhthey don't come on very often.15:35
arrrghhhhrm15:35
arrrghhhi have these HTC XDA USB devices15:35
arrrghhhnever seen them before.15:35
arrrghhhi can't remember how it looks like when i'm at home tho...15:35
arrrghhhhrm.  removed 'em, didn't seem to fix anything.15:36
arrrghhhjust odd that the pc thinks there's a usb mass storage device available...15:36
arrrghhhhmmmmmmm15:37
F22damn, the blob history for that file is too large to view online.  i need to figure out how to do it manually.15:41
F22there have been a lot of edits to that file since.15:44
Naadif you need anything else from me then say so, will stay around for another hour i guess..15:45
emweauto-bl issues?15:48
emwe(too lazy to reread)15:48
arrrghhhemwe: yea15:49
arrrghhhrhod100 guys can't boot with the autobl changes15:49
emweas i just grasped the 2nd 20101023 commit breaks it?15:50
arrrghhhyes15:50
emwewhat means can't boot? device freeze?15:51
arrrghhhyes15:51
arrrghhhfreezes at haret15:51
emwehm. the thing is, that the auto-bl setup code in micropklt_panel_resume() looks really strange ;) at least the values15:52
arrrghhhlooks really strange15:52
emwei got the topaz values from very old haret i2c traces from Markinus and used them15:52
arrrghhhthat sounds promising :P15:53
arrrghhhnice15:53
emwewistilt siad he got them by ages of debugging and printks() in the kernel15:53
emwehttp://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/blobs/htc-msm-2.6.27/drivers/i2c/chips/microp-klt.c#line22315:55
emwetopa is pretty straigt forward and 0x00 twice as the data for the cmd15:55
emweand 0x01 for enable15:55
emwethe rhod values look strange.15:55
arrrghhhhm15:55
emweand ... rhod is the only device which uses cmd value15:56
arrrghhhwell all other rhods seem to work15:56
emwe0x24 instead of 0x22 IIRC15:56
arrrghhhjust the 100 is being a biatch.15:56
arrrghhhthat's why i'm wondering if the gpio on the 100 is different.15:57
arrrghhhthat would just be awesome.15:57
emwehmhm. nobody here to build a kernel with disabled gpio in the rhod panel code? ;)15:58
emweshall i?15:58
arrrghhheh if you want to15:58
arrrghhhjust to test?15:58
emwesomebody to test around?15:58
arrrghhhwell Naad was the guy15:58
F22Naad are you around?15:58
F22he said he'd be around for another hour about 15 minutes ago.16:00
arrrghhhReefermattness: If you just wait 2 years after graduating I'll get a job and pay you for this amazing work - LOL just wait 2 years.  all your money problems will disappear when this dude graduates.16:00
Naadyes, i'm around16:02
F22we have our tester emwe. :)16:03
arrrghhhk16:03
arrrghhhemwe is going to build you a kernel to test.16:03
Naadok, great16:03
Naadi'm having my pizza now, so won't be talking back fast xD but i'm online16:04
emweNaad: hi. just see if it boots. it's built from a local tree with some ehm... many modifications. :)16:04
arrrghhhlol16:04
emwei finally get my topa to survive nearly a day16:05
Naadhaha ok16:05
emwebtw, is there any rhod issues on first incoming call that mic is not working?16:05
F22without recharging? or without crashing? :P16:05
emweF22: without both. haha.16:05
F22:d16:05
emweF22: but mostly letting it idle. just wan't to make sure it's still able to receive calls. pm.sleep_mode=1 works for me without OC16:06
emweno timeshift. everything fine in that respect.16:06
emweNaad: http://dl.dropbox.com/u/12183048/htctopaz/rhod100-2010-11-23-no-panel-gpio.zip16:06
Naadthanks16:07
Naadwill try soon!16:07
emwenp. good luck.16:07
emweNaad: might be also an idea to dump the ramconsole after a crashy kernel boot experience :)16:08
emwei just did a package with HaretScripting for the topaz xdandroid forum thread.16:08
F22he posted a dmesg16:10
emweah ok. i said nothing. :)16:10
F22the kernel comes up, he was able to adb in.16:10
emweehm, didn't arrrghhh say it freezes?16:11
emweso the display just stays black?16:11
arrrghhhit does... visually16:11
emwekk16:12
arrrghhhit's acting like a startup.txt problem16:13
arrrghhhfrom what i've been told, it freezes at the haret screen.16:14
emwewe have some topazers reporting the last working kernel is 2010102316:14
arrrghhhhm16:14
arrrghhhwhich ones?16:15
emweno specific model16:15
arrrghhhweird.16:15
emwe100/160/...16:15
F22i'm running a wistilt kernel currently, not pure xdandroid, but there were two lines in his dmesg that weren't in mine which caught my eye.16:15
arrrghhhit just seems to be RHOD10016:15
F22[    2.142059] micropklt_spi_bl_status_print: light sensor auto=10=0x0a SPI=136=0x8816:15
F22[    2.142364] micropklt_panel_resume16:16
arrrghhhthat second one just reminds of the device coming out of wake from sleep16:16
emweF22: the first line is what i added. it prints the auto-bl status on boot gathered from SPI16:16
emwehmhm!16:16
F22so wistilt2's build is older.16:17
emweit reads from i2c address 0x24 ... and that is where wistilt writes his auto_bl data to, where we write to 0x2216:17
emwearrrghhh: my post about the recent topa non-boot issues: http://forum.xda-developers.com/showthread.php?p=9383124#post938312416:17
arrrghhhhm16:19
arrrghhhsame issue?  freezes at haret?16:19
emwearrrghhh: well, that's what it looks like. according to ramconsole/dmesg it's going until where i posted there .. mmcblk0p1 ...16:20
emweright after setting the sdcc controller frequency16:20
F22i wouldn't call the rhod100 issue freezing at haret.16:22
emwegetting confused. last known kernel for some of the topazers was 20101011, not 20101023. so usb gadget broke it for whatever reason.16:22
emweNaad: if the first one doesn't work, try this one with auto-bl codepath routed to the topaz one: http://dl.dropbox.com/u/12183048/htctopaz/rhod100-2010-11-23-no-panel-gpio-topa-autobl-codepath.zip16:23
F22if adb is available then the kernel is up and we're past the init script and into init.android.16:24
emweit's either the gpio or the auto-bl data written16:25
F22how did you disable the gpio in the board file?16:28
arrrghhhdamnit.  windows keeps finding this HTC XDA USB disk drive device.  i wonder if that's screwing it up...16:30
emweF22: just comment it?16:32
F22lol16:32
*** L_miller has quit IRC16:32
F22is that all? i take it nothing breaks if it isn't defined then.16:33
emweF22: when i said "disable" earlier, then it should have been "don't touch"16:33
NaadSorry was away for a bit.16:33
Naadfirst one did not work.16:33
emwekk16:34
F22ah16:34
emwebrb5. good luck with the second.16:34
emweaccording to dmesg it's micropklt_panel_resume() which is last in the log?16:34
emweanyway, brb5 ;)16:34
NaadWill test the second one, report what happens and then I'm off to sleep.. university calls tomorrow morning early xD16:37
F22[    2.142364] micropklt_panel_resume16:38
F22[    2.357147] microp-keypad: Initializing MicroP keypad driver16:38
F22[    2.358215] input: microp-keypad as /devices/virtual/input/input616:38
F22[    2.416290] microp_keypad_probe done16:38
F22[   29.303985] Something used micropklt_lcd_ctrl. This function should no longer be used.16:38
F22[   29.304168] Something used micropklt_lcd_ctrl. This function should no longer be used.16:38
F22^ emwe16:38
F22the rest of that stuff is present in my dmesg too however.16:39
emweF22: yeah, i should really get some rest. sorry...16:41
F22well then get some sleep, this problem has been around few weeks, another day or two isn't a huge deal in the cosmic scheme of things. :P16:43
Naadhmm.. havent booted yet, winmo is not working with me.16:43
NaadRemoving the microsd made it reboot xD16:43
*** VGear has joined #xdandroid16:43
Naadi'm gonna give it one try and also get some sleep.16:44
VGearhello16:44
NaadNo boot yet with second kernel16:45
Naadbut, there is something different. The screen normally faded a bit (backlight turned down) now it just hangs on full brightness, like it was16:46
arrrghhhsame deal?16:46
arrrghhhhangs at haret?16:46
Naadyeah, well, haret dialog (with the blue bar) just dissappears, then it hangs on explorer screen16:47
Naadwith haret standing in bottom16:47
*** programmer8922 has joined #xdandroid16:47
arrrghhhk16:48
NaadBut now at full brightness, so the brightness is not turned down anymore16:48
arrrghhhthat would make sense16:48
F22so it hangs at the very same place then?16:48
arrrghhhthe gpio is disabled so autobl shouldn't happen.16:48
F22right16:48
arrrghhhcan we get some more logs before you leave?16:48
VGearI have been reading a  XDA Raphael/Diamond thread at xda-developers about battery's life and I tried to install task manager with autokill, after that my Diam100  last at least 20hours. I thought you guys should to know16:48
VGearand thanks a lot for your work16:49
arrrghhhVGear: k16:49
Naadwhat logs do you need?16:49
arrrghhhNaad: same16:49
arrrghhhdmesg & logcat16:49
Naadok16:49
arrrghhhthanks dude16:49
arrrghhhVGear: we've had people get 36 hours.16:49
F22Naad: what's the very last thing you see pop up on the screen before the screen hangs?16:50
emwehmhm. when it stays at full brightness then rhod really uses a different i2c cmd...16:51
VGeararrrghh: I saw it, but now I don't want to spend my time in posting this at xda-developers, IRC is faster16:52
VGearalso if you nead some spanish support, I think I can do something16:52
arrrghhhwell no one will benefit from it here.16:52
arrrghhhwell, hardly anyone.16:52
arrrghhhfor the most part 'power-users' or devs hang out here.16:52
Naadi see the blue bar finish, the popup screen dissappears, and then it hangs16:53
Naadso on the explorer screen, with andboot folder opened16:54
F22so you're never seeing the command line stuff after haret hands over control. no wonder everyone says it freezes in haret. i follow you now.16:54
*** VGear has quit IRC16:57
arrrghhhF22: lol sorry i thought you got that.16:58
Naadhaha ok, clear. I never see the command lines no16:58
arrrghhhthat's the reason i keep thinking it was a startup.txt issue.16:58
Naadi posted the logs from the second kernel16:58
arrrghhhcool16:58
arrrghhhthanks Naad16:58
Naadbut it's definetely not startup.txt as adb is working fine16:58
arrrghhhyea.  i get that now :P16:58
arrrghhhit's just acting like a startup.txt issue.16:59
Naadgreat :)16:59
Naadbut I'm off to bed now!16:59
F22g'nite Naad16:59
NaadI'll read the logs in the morning, and test whats needed :016:59
Naadgoodnight!16:59
*** zycho_ has quit IRC17:04
NaadOne last thing, the phone does get hot when it hangs. Not sure if it's useful info.17:10
F22does it normally get that hot on boot-up?17:11
*** knchris has joined #xdandroid17:14
emwewatf... "Waiting for SD Card"...17:18
emwenever had that.17:19
emwelooks like my topa starts acting crazy.17:19
Naadit normally doesn't get hot i would say.. not that i can remember17:19
*** knchris has joined #xdandroid17:20
arrrghhhemwe: i've seen that a few times.  not sure what the solution is.  i always just told peoples to reformat their card.17:21
emwei just rebooted...17:22
emwe;)17:22
arrrghhhit works now?17:24
arrrghhhlol17:24
arrrghhhthat's troubleshooting step #1. :P17:24
F22#2 is delete data.img17:25
F22:P17:25
emweno, #2 is buy a desire z :P17:26
F22lol17:26
F22aside from t-mobile's g2, there aren't a whole lot of those available in the states. i suppose verizon's merge will be out soon...17:27
arrrghhhbah17:27
arrrghhhesire z17:27
arrrghhhi'm not switching networks for a phone lol17:27
emweluckily we can use our phones for any provider :)17:28
stinebdwhat's new folks17:28
emweconstant high cpu load with my bricked kernel?17:28
stinebdhow do you brick a kernel?17:29
emwemess with the code.17:29
F22lol17:29
emweand btw, the raph hasn't arrived, yet. ;)17:29
stinebdbut kernels aren't physical objects and thus cannot perform the duties of a brick!17:29
emweunderstood, papa. :P17:29
F22lol17:29
arrrghhhhahaha17:30
emwebut if you print out the kernel source and glue every sheet of paper, it's likely to have physicial properties of a brick.17:30
arrrghhhlmao17:31
arrrghhhi prefer to duct tape my sheets of kernel source thank you.17:31
*** LeTama has quit IRC17:32
stinebdhaha17:32
F22lol17:32
stinebdemwe: you think it's stuck in inspection or something? cause of the toner cartridge terrorism nonsense?17:32
F22maybe it's waiting in line for a patdown? :P17:33
arrrghhhit just wants a little love17:34
emwestinebd: toner cartridge terrorism?! i must have missed something. the next thing to happen is we open our rocket silo gates when a bag of rice turns over in china...17:35
arrrghhhsome yokels tried to blow up some planes using bombs hidden in toner cartridges.17:35
F22those bombs shipped from yemen were found inside toner cartridges from what i recall...17:36
arrrghhhyea17:36
arrrghhhsame material that freakin guy used last december on that flight to detriot.17:36
arrrghhhDetroit?17:36
arrrghhhde-riot17:36
emwebut that's not that "test bomb bag" thingy with the flights from africa, no?17:36
arrrghhhdunno17:37
emwewhere half europe was pissed about, because they didn't get notified17:37
stinebdany murricans here get one of those free gropes?17:37
emwebut honestly, i haven't watched news lately. a pitty.17:37
arrrghhhnot yet17:37
arrrghhhi haven't gone to the airport in a while tho17:37
arrrghhhi should ask my dad...17:37
F22haven't flown lately, not that i want to with all the crap i've been hearing.17:38
arrrghhhseriously17:38
arrrghhhi guess not everyone gets the pat-down/screening thing tho17:38
arrrghhhthey 'randomly select' people for the full body scanner, and if they refuse they get molested.17:38
emwestinebd: any hint as to why the "system_server" process might suck up all cpu?17:38
arrrghhhemwe: lol i'm glad you asked that question :P17:39
stinebdemwe: not yet. gotta attach strace to it when it happens17:39
emweoh, it's known with frx03?!17:39
stinebdi'm waiting for a hard drive for the machine i do most of my work on before i can do that though17:39
stinebdit's known which all froyo images17:39
stinebdwith*17:39
F22i've gotten reports of it happening with frx03.17:39
emwehm, first time i see it.17:39
emweafter i built frx03...17:40
F22hasn't happened to me yet, but i've only rebooted twice in the past 5 days. :D17:40
emweand i suspected my kernel *BRICKSTUFFTHINGY* to be the cause...17:40
F22i used to see it all the time though.17:40
arrrghhhi guess i should check older builds17:40
arrrghhhi just assumed it was always a problem...17:41
arrrghhhnow it doesn't always peg my proc tho.17:41
stinebdarrrghhh: no need, it happened randomly to those too17:41
arrrghhhwhen the phone seems to be crapping itself and wouldn't do anything, that's when system_server was stealing all the processor cycles.17:41
arrrghhhnot surprised stinebd.17:41
stinebdi've known about it for a while now, but haven't gotten around to looking through what's happening17:41
arrrghhhyea17:41
stinebdkilling jit got rid of a lot of heisenbugs so that's probably my next task17:42
emwestinebd: ok, what do i have to do ? "strace -p <PID>"?17:42
stinebdemwe: pretty much, yeah. failing that... find a way to strace it on startup and pray it doesn't "fix" the bug as you try to observe it17:42
emweProcess 1235 attached - interrupt to quit17:43
emweselect(19, [10 18], NULL, NULL, NULL17:43
stinebdwhat's fd 19?17:43
emwei have no idea what i am doing...17:43
arrrghhhlol17:44
stinebdnever straced before?17:44
arrrghhhpray it doesn't "fix" the bug as you try to observe it - seemed to work for us before :P17:44
emwestinebd: nope. and how to resolve what fd 19 is? i would think of lsof...17:45
stinebdnah17:46
stinebdmaybe /proc/PID/fd17:46
stinebddo we even have lsof on there?17:47
stinebdif we do you could use that too, but proc could work too17:48
*** Naad has quit IRC17:48
arrrghhhi think lsof is on there17:48
emwestinebd: no lsof. and fd 19 is not in the procfs. only goes up to 1817:48
arrrghhhi thought i used it before...17:48
arrrghhhdamn17:48
arrrghhhi lie17:48
stinebdmust be ipc or something then17:49
arrrghhhreboot17:49
*** arrrghhh has quit IRC17:49
stinebdno reboot we need his whacked out system alive!17:49
emweshit is what i am telling...17:50
emwebah.17:50
stinebdwuh17:50
emwelr-x------    1 1000     1000           64 Nov 23 22:49 19 -> pipe:[1968]17:50
stinebdwhat's 1968?17:50
emwewas looking at ppid17:50
stinebdwatch it be battery service or some crap17:51
stinebdi swear to god if it is...17:51
emwe1968 not existant in top17:51
stinebdawesome17:51
stinebdmaybe that's why it's freaking out17:51
F22it's lost its mommy and is scared...aaaawww...lol17:52
stinebdemwe: if you want you can ship your topaz to me and i'll check it out after it never gets here17:54
emwestinebd: good plan.17:54
stinebdtry to keep it turned on so the bug remains there though17:54
stinebdcustoms would enjoy that17:55
stinebdoh and find some clock app that makes a ticking noise17:55
F22lol17:55
emwe;)17:56
F22as i recall, both jonpry and acl had handsets shipped to them that they never received also.17:56
F22it sounds like an epidemic17:56
emwehmhm.17:56
stinebdmaybe a scam?17:56
hamagche got my tp117:56
hamagcacl did17:56
emwewow, nice thing that strace ;)17:58
*** AIdejjas has joined #xdandroid18:04
AIdejjasHi!18:04
AIdejjasWill it ever be 100%18:04
AIdejjas??18:04
hamagcnever!18:05
hamagcok maybe someday18:05
hamagcdefine 100%18:05
F22My magic 8ball says to "Ask again later." :P18:07
*** AIdejjas has quit IRC18:09
emwehm, incall mic fixed for topa. but it crashes afterwards in wakelocks print_lock_stat()... PITA.18:09
F22progress :D18:10
emweperhaps i should disable them again ;)18:11
F22lol18:14
*** knchris has left #xdandroid18:15
*** arrrghhh has joined #xdandroid18:15
arrrghhhstupid adb.18:16
arrrghhhi'm out of ideas, other than blowing up this xp box.  damnit.18:16
F22can't help, sorry. i've never tried to run adb on windows, that's what i have linux for.  pity "liberating" it isn't an option...18:17
arrrghhhlol18:18
arrrghhhwell at home it's fine.18:18
arrrghhhi guess i'll just deal with it.  i have more time to play with this at work then i do at home.18:18
arrrghhhthat's sad...18:18
arrrghhhbut true lol18:18
*** Aks has quit IRC18:18
F22no demanding gf at work... ;)18:18
arrrghhhindeed18:18
arrrghhhi tried every suggestion i could fine18:20
arrrghhhfind*18:20
arrrghhhof course it's all for native android devices.18:20
arrrghhhso i'm not sure if what i'm doing is even worth it... so far no go.18:20
F22what are you doing?18:21
arrrghhheverything i can lol18:21
F22lol18:22
arrrghhhthe best guide i found so far recommends using USBDeviewer18:22
arrrghhher USBDeview18:22
arrrghhhand basically remove any ADB or HTC related devices.  i tried that.  even tried removing all USB related stuff, still didn't work.18:22
arrrghhhthis last time i removed all the XDA/HTC stuff that's in there, and rebooted18:22
arrrghhhthe stupid driver install just keeps saying "cannot install this hardware" like i have the wrong driver for this...18:23
arrrghhhhm maybe i do.18:23
F22can you still mount it fine?18:24
arrrghhhmount... what?18:24
F22when you're in windows mobile18:25
arrrghhhoh18:25
arrrghhhyea winmo works fine18:25
arrrghhhand of course adb works fine on other machines, so it's definitely this PC.18:25
arrrghhhadb has worked on this PC before as well.18:25
F22so it worked before and now it isn't. No doubt you're kicking yourself wondering what's changed.18:26
arrrghhhi'm going to start over with the sdk18:26
arrrghhhlol well the only thing that's really changed, is i moved desks and therefore my dock moved... so the usb port it's using invariably changed.18:26
emwedid adb still work *after* the switch to usb gadget?18:27
arrrghhhi never used it before that switch TBH18:27
* arrrghhh is slow18:27
emwekk. so that's fine and can be excluded :)18:27
arrrghhhhehe18:28
arrrghhhyea, it's something on this pc18:28
arrrghhhadb works fine elsewhere.18:28
emweyeha. phone survived first incall ever for me.18:29
emweand even mic and earpiece worked.18:29
emwe;)18:29
emweis it "earpiece" actually? what's the correct term for the speaker above the screen?18:30
arrrghhhyea18:30
arrrghhhthat makes the most sense18:30
arrrghhhearpiece speaker18:30
emwethx18:31
emwegnight peeps.18:32
arrrghhhg'nite18:32
*** emwe has quit IRC18:36
hamagcyep me too18:48
hamagcgoodnight guys18:48
*** hamagc has quit IRC18:48
*** Reefermattness has quit IRC18:49
*** NeoMatrixJR has quit IRC18:50
*** eR^zeRa` has quit IRC18:54
*** JesusFreak316 has quit IRC19:02
*** leobaillard has quit IRC19:10
arrrghhhso what is our device considered by adb?  dream?  magic?19:13
arrrghhhoy.  i hate you windows.19:18
*** Reefermattness has joined #xdandroid19:26
arrrghhhi'm such a noob lol.  i just started my first thread on XDA :D19:31
MrObviousarrrghhh: lol19:42
arrrghhhi'm hoping i missed something stupid.19:48
arrrghhhbecause at this point, i have no clue.19:49
F22i didn't know adb cared.19:58
arrrghhhque?20:00
* F22 points towards your earlier comment asking what our device is considered as by adb.20:01
arrrghhhoic20:01
arrrghhhi was just looking in the inf file for the usb driver.20:01
arrrghhhi just stumbled on a guide for the incredible, it instructed people to add some lines to the inf for that device.20:02
arrrghhhi didn't have to do that before.20:02
F22sounds more complicated than it needs to be.20:02
arrrghhhindeed20:02
arrrghhhi'm at a loss.20:02
F22how did you get it working on the other windows machines?20:03
arrrghhhit worked on this machine previously20:03
arrrghhhdroid explorer is how i got it workin20:04
F22so why not continue to use droid explorer?20:04
arrrghhhi even tried reinstalling it.20:04
arrrghhhit just sets up the sdk really20:04
arrrghhhah well20:07
arrrghhhi'm off20:07
arrrghhhi'll cya on the flip side20:07
*** arrrghhh has quit IRC20:07
*** ftvm_DIAM100 has quit IRC20:14
*** hardwalker has joined #xdandroid20:42
*** Reefermattness has left #xdandroid20:54
RogueAgent[TP2]hey f2221:26
RogueAgent[TP2]your rootfs works perfect21:26
F22sounds good :)21:27
TheDeadCPUwoop21:28
F22barring a decision on final placement of { } [ and ] due to the fact that the italian and french keys have other stuff in the spots i've put them, i'm pretty much done on the rhodium side of things, aside from possible further expansion of the symbol palette.21:29
F22aside from the fuse, i haven't done the raph yet, nor i have even looked at the kovsky21:30
F22keys=keyboards21:31
stinebdyay21:53
stinebdfinally an attempted wiki spammer21:53
TheDeadCPUwhat21:58
F22lol22:08
TheDeadCPUlol22:20
F22the htc-linux wiki has been vandalized it appears.23:56
TheDeadCPUoh lol23:56
F22every single page has been replaced by an under construction message.23:57
TheDeadCPUI saw23:57
F22and a link to a site that google says is suspected of spreading malware.23:57
TheDeadCPUThe maintainer can just back it up lol23:57
TheDeadCPUWait, anyone can just set it back23:57
F22sure, but there are a lot of pages to set back...23:58
TheDeadCPUYup.23:58
F22and this person has been at it for 9 days it looks like. they need a life, or a bot... :P23:58
F22on second thought, the most recent changes appear to have been automated.23:59
F22it's just the first few that appear to have been individually done.23:59

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