Tuesday, 2011-02-15

« Monday, 2011-02-14 Index Wednesday, 2011-02-16 »
*** rpierce99 has quit IRC00:04
*** T_D_H has joined #xdandroid00:25
*** GPFerror has joined #xdandroid00:35
*** ndno has joined #xdandroid00:36
*** Barry_ has joined #xdandroid00:55
Barry_I have a VZW Touch Pro 2 Using CDMA trying to use XDAndroid and when I try to run Haret I my start menu moves to the bottom and the system freezes Any advise?00:57
ndnoAre you overclocking in WinMo?  You need to be running in stock speed under WinMo before launching haret.exe01:04
*** programmer8922 has quit IRC01:28
*** Nautis has quit IRC01:39
Barry_wow did not see the response sorry for the delay02:37
Barry_Not overclocking win mobile02:37
Barry_I am a complete Noob when it comes to trying to get android to run on winmo, per install instructions I added the "set rel_path=andboot" (without quotes) into the Startup.txt and put it before the phys keyboard group of settings, and now I get a Line 6 Unexpected input "=andboot"02:41
*** ndno has quit IRC03:40
*** Barry_ has quit IRC03:46
*** kalemas has joined #xdandroid04:54
*** hardwalker has quit IRC04:58
*** XirXes has quit IRC05:39
*** L_miller has quit IRC06:52
*** GPFerror has quit IRC07:08
*** L_miller has joined #xdandroid07:17
*** rpierce99 has joined #xdandroid07:48
*** nilu has joined #xdandroid08:01
niluhi08:01
nilubuzz08:01
niluany buddy08:01
niluthr08:02
*** nilu has quit IRC08:02
*** rpierce99 has quit IRC08:05
*** GPFerror has joined #xdandroid09:01
*** programmer8922 has joined #xdandroid10:00
*** programmer8922 has quit IRC10:06
*** LENINred has joined #xdandroid10:08
LENINredhello10:08
*** LENINred has left #xdandroid10:09
*** emwe has joined #xdandroid10:32
*** MassStash has quit IRC10:48
*** kalemas has left #xdandroid11:17
*** GPFerror has quit IRC11:36
*** Erikson has joined #xdandroid11:40
*** mighty has joined #xdandroid12:00
mightyhi12:01
*** mighty has quit IRC12:07
*** T_D_H has quit IRC12:33
*** Bear_ has joined #xdandroid12:37
*** Nautis has joined #xdandroid12:41
*** SpecR_ has quit IRC12:49
*** phh has quit IRC12:49
*** stinebd has quit IRC12:49
*** balans has quit IRC12:49
*** lodtank has quit IRC12:50
*** L_miller has quit IRC12:50
*** xawen has quit IRC12:50
*** zycho__ has quit IRC12:50
*** crispee has quit IRC12:50
*** paccer_ has quit IRC12:50
*** Erikson has quit IRC12:50
*** xdandroid has joined #xdandroid15:15
*** James093 has joined #xdandroid15:17
James093Hello15:17
*** kwoodyusa has joined #xdandroid15:23
*** balans1 has joined #xdandroid15:24
*** stinebd has quit IRC15:27
*** balans has quit IRC15:27
*** James093 has quit IRC15:27
*** Erikson has joined #xdandroid15:29
*** MassStash has quit IRC15:32
*** kwoodyusa has quit IRC15:58
*** Nautis has quit IRC15:58
*** Bear_ has quit IRC15:58
*** Kraln has quit IRC15:58
*** Fudge has quit IRC15:58
*** Krazie has quit IRC15:58
*** purefusion has quit IRC15:58
*** leobaillard has quit IRC15:58
*** hyc has quit IRC15:58
*** F22 has quit IRC15:58
*** virsys has quit IRC15:58
*** Agin has quit IRC15:58
*** NeoMatrixJR has quit IRC15:58
*** SpecR_ has quit IRC15:58
*** drakaz has quit IRC15:58
*** phh has quit IRC15:58
*** lodtank has quit IRC15:58
*** L_miller has quit IRC15:58
*** xawen has quit IRC15:58
*** Erikson has quit IRC15:58
*** balans1 has quit IRC15:58
*** zycho__ has quit IRC15:58
*** crispee has quit IRC15:58
*** emwe has quit IRC15:58
*** paccer_ has quit IRC15:58
*** CazH has quit IRC15:58
*** Erikson has joined #xdandroid16:08
*** balans1 has joined #xdandroid16:08
*** kwoodyusa has joined #xdandroid16:08
*** drakaz has joined #xdandroid16:08
*** leobaillard has joined #xdandroid16:08
*** NeoMatrixJR has joined #xdandroid16:08
*** Kraln has joined #xdandroid16:08
*** L_miller has joined #xdandroid16:08
*** zycho__ has joined #xdandroid16:08
*** SpecR_ has joined #xdandroid16:08
*** xawen has joined #xdandroid16:08
*** CazH has joined #xdandroid16:08
*** paccer_ has joined #xdandroid16:08
*** phh has joined #xdandroid16:08
*** lodtank has joined #xdandroid16:08
*** crispee has joined #xdandroid16:08
*** virsys has joined #xdandroid16:08
*** Agin has joined #xdandroid16:08
*** hyc has joined #xdandroid16:08
*** F22 has joined #xdandroid16:08
*** Fudge has joined #xdandroid16:08
*** Krazie has joined #xdandroid16:08
*** purefusion has joined #xdandroid16:08
*** emwe has joined #xdandroid16:08
*** Nautis has joined #xdandroid16:08
*** Bear_ has joined #xdandroid16:08
*** stinebd has joined #xdandroid16:16
*** virsys has quit IRC16:25
*** Agin has quit IRC16:25
*** L_miller has quit IRC16:30
*** virsys has joined #xdandroid16:32
*** Agin has joined #xdandroid16:33
*** manekineko has joined #xdandroid16:33
*** InternetToughGuy has joined #xdandroid16:42
*** TheDeadCPU has joined #xdandroid16:55
*** kwoodyusa has quit IRC17:08
stinebddrakaz: our sleep of death was liblights-related (the backlight not being reactivated on wake) -- probably not the same issue as you're seeing.17:14
*** emwe has quit IRC17:19
*** bs123 has joined #xdandroid17:23
*** Erikson has quit IRC17:41
Bear_My Vzw Touch pro 2 keeps getting stuck on the HaRET: Booting Linux.... screen, tried multiple times any recommendations?18:17
TheDeadCPUCheck that you have the correct Startup.txt18:18
Bear_tried removing files and reinstalling, added the rel_path=andboot to the set cmdline section of the startup.txt made sure physkbd is the final command on there18:18
Bear_the Rhod 50018:18
TheDeadCPUk18:18
TheDeadCPUTry updating your zimage and modules18:18
TheDeadCPUThen rootfs if that doesn'w work18:19
TheDeadCPUdoesn't*18:19
Bear_ok will try thank you , its weird, i have the XDAndriod app that allows you to select model and download update, when I select the rhod500 and hit boot my start menu moves to the bottom of the page and I get the Haret booting linux and nothing happens the phone freezes18:20
Bear_I installed using the cab file18:20
TheDeadCPUYEa18:22
TheDeadCPUAfaik, the .cab version is broken now18:22
Bear_I have had the SoD issues forever with this phone, love the hardware hate the software,18:22
Bear_so I should download the compressed files and unzip into the and boot and hope that works, or replace the files you recommended and try just launching the haret18:23
Bear_or still use the launcher,18:24
Bear_the version I dl was the froyo 2.2 blazn cab18:24
manekinekoouch that's doubly outdated, both blazn and cab are outdated18:24
manekinekoI think you should just restart from a good build18:24
manekinekolike this one: http://forum.ppcgeeks.com/tp2-android-development/140848-build-complete-froyo-bundle-frx04-stable.html18:24
*** programmer8922 has joined #xdandroid18:25
*** arrrghhh has joined #xdandroid18:26
Bear_thank you very much I will replace the files and try again18:26
manekinekonp18:26
manekinekohey arrrghhh18:26
manekinekohow's it going?18:26
stinebddo it go go go18:27
arrrghhheh y'know18:27
arrrghhhlivin the dream.18:27
arrrghhhstinebd, wanted to pick your brain on gallery3d.  is that still busted or is it just on the back burner?18:28
stinebddont care busy18:28
arrrghhhlol fair enough.18:28
arrrghhhi just can't remember where we left that problem.18:28
TheDeadCPUarrrghhh, living the dream eh?18:29
arrrghhhyou know it18:29
TheDeadCPUNic18:29
TheDeadCPUNice*18:29
stinebdmaybe18:30
stinebdMAYBE18:30
stinebdgps might build18:30
arrrghhhheh18:30
manekinekonice18:30
stinebdeven maybier it might work18:31
manekinekoarrrghhh how much do you get on what ACL and them are doing with NAND?18:31
arrrghhhsome18:31
arrrghhhwhy18:31
stinebdOH GOD YES18:31
TheDeadCPUarrrghhh, I've got quite a nice place to work now18:31
arrrghhhlol.18:31
manekinekothat sounds good18:31
stinebdit built, shipping it.18:31
arrrghhhTheDeadCPU, oh yea?18:31
arrrghhhstopped selling drugs?18:31
TheDeadCPUno?18:31
TheDeadCPUarrrghhh, Bowling Alley :D18:31
arrrghhhlmao18:31
arrrghhhnice18:31
manekinekono particular reason, just I'm pretty confused on how the whole NAND thing works and was hoping to pester you with questions =P18:31
TheDeadCPUIt's like, sit there and do nothing for 6 hours lol18:32
TheDeadCPUI only get like $70 a day though18:32
arrrghhhmanekineko, it's not ready yet so what's your question.18:32
arrrghhhTheDeadCPU, for 6 hrs?18:32
manekinekooh my questions are real basic18:32
TheDeadCPUYa arrrghhh18:32
arrrghhhthat's almost $12/hr18:32
arrrghhhnot bad to do nothing.18:32
TheDeadCPUTrue18:32
arrrghhhconsidering my gf makes like $9/hr and works her ass off.18:33
TheDeadCPUBut, $12/hr is minimum wage here :p18:33
manekinekoso I see from the spec sheets that rhods  have 512MB of ROM, i.e. NAND18:33
arrrghhhyea your standard of living is a little higher.18:33
arrrghhhours is like $7.26 i think18:33
arrrghhhmanekineko, ok18:33
manekinekoso in order to get the split between what WinMo called internal memory and the part where we flash the OS, we partition the NAND, is that right?18:33
arrrghhhsame part18:34
arrrghhhwinmo internal memory = NAND in this case18:34
manekinekoso it's not even partitioned apart?18:34
arrrghhhit is18:34
arrrghhh4 partitions i believe18:34
manekinekookay, so ya we partition it up18:35
arrrghhhafaik we're using a similar partition table to winmo18:35
manekinekoare the partition sizes totally arbitrary, you just set them to how you want to split the space?18:35
arrrghhhbut not identical.18:35
arrrghhharbitrary in the sense that they can be anything18:35
manekinekoya ok18:35
arrrghhhbut to work correctly, we have to parition them very specifically18:35
arrrghhhwhich is why they were talking about stuff getting blasted out18:35
arrrghhhand not being able to fit the initrd, etc.18:35
manekinekoso why is it that we can modify the "Internal Memory" portion whenever we want, the same as a flash drive18:36
manekinekobut in order to modify the OS partitions, we need to blast out all partitions?18:36
arrrghhhuhm18:36
arrrghhhwhat18:36
arrrghhhwe can't modify the 'internal memory' portion at all18:37
arrrghhhunless you mean just moving data around it18:37
arrrghhhwhich is drastically different than flashing an OS18:37
manekinekoI mean modify it like copy files onto internal memory18:37
arrrghhhyea, kinda different from paritioning and installing an OS...18:38
manekinekobut if we wanted to copy on a new set of kernels, it seems like we need to blast out everything18:38
arrrghhhnot if we partition correctly18:38
arrrghhhand place the kernel in a separate partition18:38
arrrghhhafaik that's how the vogue guys do it, but i'm not positive.18:38
manekinekohmm must have misread a post somewhere, that makes sense18:40
arrrghhhaw18:40
manekinekowhat kept up from just formatting the whole thing as a giant FAT partition or something, and sticking our Android builds there18:41
arrrghhhthey're still hashing it all out18:41
arrrghhhhence the reason it's not ready for public consumption.18:41
manekinekoyeah, I know, I'm just curious about how this stuff works18:41
arrrghhhlike bacon grease18:41
arrrghhhwith butter18:41
manekinekobacon grease with butter?18:42
arrrghhhever had it?18:42
manekinekocan't say that I have18:42
manekinekosounds good though18:42
*** jonpry has joined #xdandroid18:42
stinebdmanekineko: internal nand is not like sd where you have a controller emulating an actual disk18:42
arrrghhhlol18:42
stinebdso you can't use fat18:42
F22hmm..touchscreen calibrates with 1258.  bzo wiping out alex's clocks may be a good thing in some ways.18:42
F22i wonder if the sd card issues went away too.18:43
arrrghhhF22, oh yea?18:43
arrrghhhOoOo18:43
manekinekowhat's the file system of the "Internal Memory" partition?18:43
stinebdin winmo? tfat18:43
manekinekoso what would have kept us from just loading everything in there and using it like an internal SD card?18:44
stinebdlinux doesn't support tfat18:44
*** SpecR_ is now known as SpecR18:44
manekinekooh so even post NAND, we'll never see user-useable Internal Storage space like we did in WinMo18:44
manekinekointeresting18:44
manekinekocouldn't we just format it ext2 or something?18:44
stinebdyaffs2, yes18:45
stinebdor similar18:45
stinebdof course that will destroy winmo18:45
F22arrrghhh: yup, i tested it myself just now. given that those problems all started with 1245 when alex's clocks got committed, i figured it was worth testing.18:45
manekinekohmm, but no shared filesystems I suppose prevented us from just sticking haret on the SD card and loading everything else into Internal Memory, answering my question18:45
F22pity i don't have a "problem" sd card to test too.18:45
manekinekowere there ever any concrete upsides to the clock fixes?18:46
arrrghhhF22, cool.18:46
arrrghhhF22, i'll ping someone who did.18:46
arrrghhhmanekineko, we also needed drivers to access the internal memory.18:47
manekinekoall making sense now18:47
manekinekothanks18:47
stinebdnand is a pain eh?18:48
stinebdshould've just used tape drives18:48
manekinekoheh18:48
manekinekohow does the partitioning of NAND work with the fact that there are special areas of NAND, such as where touch calibration is stored, or where GPS data is stored?18:48
arrrghhhtape drives18:48
arrrghhhlmao18:48
manekinekoor parts that if you write to, it'll brick your device18:48
stinebdyou avoid those18:48
arrrghhhindeed18:48
arrrghhhi thought those were in sections of the ROM tho18:49
manekinekoso when you flash the whole NAND and partition it, it doesn't wipe those?18:49
arrrghhhlike BIOS18:49
arrrghhhnot positive tho18:49
manekinekowell, I have heard about devs who were working on NAND flashing, and bricked their devices, so there are some important things stored somewhere on NAND18:49
arrrghhhwozz somehow bricked his device.18:50
arrrghhhnot sure what he did, but that was way before we had drivers.18:50
manekinekoyeah, and ACL and crew seemed concerned about writing to certain parts of NAND18:51
manekinekocalculating offsets to avoid it18:51
arrrghhhindeed18:51
manekinekoI'm kinda unclear on how that fits into the whole partitioning thing though18:51
arrrghhhthere's also a certain number of badblocks shipped with every device.18:51
manekinekoseeing as when they partition, it seems to wipe the whole NAND18:51
manekinekowe access NAND at a level where the hardware doesn't handle badblocks for you?18:51
F22manekineko: alex's clocks as a set were considered superior to what we had previously by the kernel devs, -but- that's as a set. individualy it would appear some of them were worse than the old ones.  not sure what if anything they improved. i'm more familiar with what they broke. ;)18:53
arrrghhhlol18:54
arrrghhhi tried hq youtoobs, status quo.18:54
manekinekoanyone ever ask bzo what he did that fixed hq toutube?18:54
manekinekosince I heard on his kernels with the right setup it works18:54
arrrghhhhe thought it was clocks18:55
arrrghhhhe said he tried it again and it didn't work18:55
arrrghhhso there was a small window where the cam testing kernel worked on hq youtoobs18:55
manekinekoheh well maybe there's something the clocks fixed then18:55
manekinekoso are all the special NAND parts concentrated somewhere in particular, like the beginning of NAND?18:56
manekinekootherwise, how is ACL talking about not knowing where touch calibration is stored in NAND while simultaneously avoiding clobbering it?18:57
arrrghhhmagic18:57
manekinekolol, yeah, that's where my understanding of this was before18:58
TheDeadCPUGnite ppl<318:58
*** TheDeadCPU is now known as TheDeadSLEEP18:58
manekinekoso how are they avoiding the badblocks on the NAND?19:01
arrrghhhnot sure.19:02
arrrghhhthere might be some hardware that does that for them...19:02
manekinekocool19:02
arrrghhhbut they might have to write an algo to do it for them as well.19:02
arrrghhhusing mtty you can easily identify bad blocks.19:02
stinebdheh19:14
stinebdat least part of the gapps problem is that i never cleaned the install tree19:14
arrrghhhlmao19:14
arrrghhhmight be a problem19:14
arrrghhhso am i pumping out a new gb build?  :P19:15
stinebdnot yet19:15
stinebdi'd also prefer system images only until we get to the rc stage19:15
stinebdthat one bundle should be good enough until then19:15
*** NeoMatrixJR has quit IRC19:15
arrrghhhfine.19:16
arrrghhhtake all my fun away19:16
stinebdis that fun?19:16
arrrghhheh19:17
arrrghhhgets me all the ladies19:17
TheDeadSLEEParrrghhh, anyone complained that I stickied that thread? lol19:29
stinebdthey made you a mod?19:30
arrrghhhTheDeadSLEEP, nope19:30
arrrghhhyou should sticky the other ones in the TP section too :D19:30
stinebdxda is really going downhill19:30
TheDeadSLEEPlol19:30
arrrghhhand unsticky reef's thread...19:30
arrrghhhand sticky my FRX04 build too :D19:30
TheDeadSLEEPstinebd, I've been a mod since August lol19:30
arrrghhhheh19:30
arrrghhhbeen going downhill for a while19:30
manekinekoI asked them to unsticky the old thread on PPG, and they actually turned me down19:30
manekinekoguess they like the obsolete thread19:30
arrrghhhmanekineko, wtf?19:30
manekinekoI asked them again though19:30
arrrghhhwho did you ask?19:30
TheDeadSLEEPBecame a senior mod 2 weeks ago or so19:30
manekinekosammich19:30
arrrghhhhrm19:30
arrrghhhi don't have any mod buddies @ ppcg.19:31
arrrghhhkinda beginning to hate the site...19:31
manekinekoI figured maybe he didn't really get what was going on in the threads19:31
manekinekoand sent him a reply explaining it19:31
manekinekohopefully he'll see the light and take down the outdated thread19:31
arrrghhhheh19:31
manekinekoreally? I kinda like it better than xda19:31
arrrghhhreef is a great guy, but he's just not keeping it updated.19:31
stinebdxda is awesome19:31
stinebdplus i got hidden clout19:31
arrrghhhit's the users @ ppcg.  there's idiots at xda-devs, but for some reason they seem more tolerable there.19:31
manekinekoreally? seem to same to me everywhere19:32
manekinekohaha19:32
arrrghhhi get more retarded questions @ ppcg, by far.19:32
TheDeadSLEEPstinebd, clout? oO19:32
stinebdi get the worst ones via facebook friend requests19:32
manekinekohah, you get support requests via facebook friend requests?19:32
stinebdyes19:32
stinebda lot19:32
arrrghhhreally?19:33
arrrghhhi never do.19:33
arrrghhhbut no body has my failbook page.19:33
manekinekoI can only imagine the quality of minds that are drawn to use that for support19:33
stinebdyou don't use your real name19:33
arrrghhhnope19:33
arrrghhhi am anon!19:33
arrrghhhnot really, but i try.19:34
TheDeadSLEEPI can edit your signature on xda arrrghhh. Put your real name, adress, e-mail and such19:34
arrrghhhTheDeadSLEEP, i have no sig on there.19:34
arrrghhhand i'll be sure that i never do :D19:34
arrrghhhyou don't have my address.19:34
arrrghhhi know you have my real name... but not my address.19:34
TheDeadSLEEParrrghhh, ummm.. The picture of your truck. WITH your license plate.19:34
TheDeadSLEEPSo yea, I don't have your address, but I can easily get it :D19:35
arrrghhhmeh19:35
TheDeadSLEEPteehee19:35
arrrghhhi don't live at the house it's registered at... so have fun!  :P19:35
TheDeadSLEEPdamn19:35
TheDeadSLEEPI couldn't be bothered anyways :D19:35
TheDeadSLEEPI'd have to like.. Look throught my IRC logs for that link to your gf's blog lol19:36
TheDeadSLEEPNOW, I shall sleep19:36
arrrghhhlol19:36
arrrghhhah laziness wins again.19:36
arrrghhhg'nite, you half-assed stalker you.19:36
TheDeadSLEEPLOL19:37
TheDeadSLEEPhttp://www.youtube.com/watch?v=vZ5P6RUvbVM19:37
TheDeadSLEEPI lol'd.19:37
TheDeadSLEEPShe had a stroke LOLLOLLOLL19:37
TheDeadSLEEP!summon sleep19:37
arrrghhhdanit19:38
arrrghhh@work19:38
TheDeadSLEEPlol19:38
manekinekoarrrghhh, you notice more color banding on stine's GB build than on FRX?19:40
manekinekoI was chatting with a guy on htc-linux the other day, and he seemed to think it might be an issue19:40
manekinekoat the time I didn't notice anything19:40
manekinekobut now I do notice that when you scroll to the end of the list and it lights up orange, the orange is extremely color banded19:40
arrrghhhcolor banded...?19:41
arrrghhheh?19:41
manekinekoyeah, something like this: http://en.wikipedia.org/wiki/Colour_banding19:41
*** rpierce99 has joined #xdandroid19:41
manekinekoscrolling to the bottom of the list looks like the left one19:42
arrrghhhoh wtf dude who cares.19:42
arrrghhhlol19:42
manekinekothe guy in htc-linux said it happened to all graphics19:42
manekinekobut this is the first time I've noticed it19:42
manekinekodunno if that's expected behavior or not19:42
TheDeadSLEEPmanekineko, It's like that on my Desire Z.19:42
manekinekohmm, is it a porting issue or a GB issue?19:42
manekinekoonly phone with real GB is Nexus S right?19:43
TheDeadSLEEPPorting I think19:43
TheDeadSLEEPAnd on every GB ROM I've seen on any device except the Nexus S19:43
TheDeadSLEEPYea, and the chinese HTC Huashan Android19:43
TheDeadSLEEPOr well, at least a ROM leaked from said Huashan Android19:43
arrrghhhin the grand scheme of things19:43
manekinekoyou try out stinebd's GB build? since he made it himself I think19:43
arrrghhhthat thing could never get fixed and it'll be just fine19:43
TheDeadSLEEP(Yes, it is named Huashan Android)19:43
arrrghhhmanekineko, he has no device to test.19:43
arrrghhhhis RAPH died.19:43
arrrghhharen't you sleeping dude?  lol19:43
TheDeadSLEEPdamn it19:44
* TheDeadSLEEP minimizes irc19:44
*** hardwalker has joined #xdandroid19:44
manekinekoheh well obviously it's not key, but if it is corrupting all graphics, it is at least a somewhat noteworthy bug19:44
arrrghhhheh19:45
arrrghhhmanekineko, but why?19:45
arrrghhhwhy is it noteworthy.19:45
manekinekoyou don't find graphical corruption on everything (it's not just the scrolling highlight) even noteworthy as a bug?19:46
manekinekoI wouldn't call that trivial19:46
arrrghhhi would.19:46
arrrghhhwell...19:46
manekinekolol ok19:46
arrrghhhok19:46
arrrghhhwhere else is it occurring19:46
manekinekoapparently all graphics19:46
arrrghhhif you say angry birds, definitely tirival.19:46
manekinekoI never really noticed though19:46
arrrghhhtrivial19:47
arrrghhhyea i haven't noticed it19:47
arrrghhhmaybe some slight issues with the top and bottom hightlight like you said19:47
manekinekoI guess backgrounds and image display are affected19:47
arrrghhhbut it's barely noticable19:47
manekinekoweb browsing19:47
arrrghhhuntil i see it, meh.19:47
*** MassStash has joined #xdandroid19:58
*** arrrghhh has quit IRC20:03
*** hardwalker has quit IRC20:05
*** hardwalker has joined #xdandroid20:07
stinebdheh20:09
stinebdhad to do a blind calibration20:09
MassStashuh oh20:31
manekinekouh oh?20:32
MassStashblind?20:34
manekinekooh stine's line?20:34
manekinekoheh I had to do that when I installed GB too20:35
manekinekokernel 1253 you can't see the calibration points20:35
stinebd1258 too20:37
manekinekothat's funny20:37
manekinekoF22, said it worked earlier20:37
*** XirXes has joined #xdandroid20:37
manekinekoon 1258 that is20:37
manekinekoon account of the clock fix being broken by 125820:38
stinebdnot for me, got some oopses or something that wiped out the squares20:38
F22for me the screen blank didn't work, so i still saw the boot text, nevertheless the calib squares appeared and i was able to click on them.20:39
F22hmm...i do have panic on oops turned off though.20:40
F22that might be it.20:40
stinebdit didn't panic20:40
stinebdjust couldn't see the squares at all20:40
stinebdexcept the upper right i saw about a quarter of20:40
stinebdnooooooo20:43
stinebdgps thread was running and bombed20:43
hycF22: http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/72aea17d0daf6b41615771ce26de72f1c354ffa820:49
hycboard-htcrhodium-panel.c lists the display IDs20:50
hyclines 43-5020:50
hycand yet the init code only handles 3 of the known IDs20:52
*** MassStash has quit IRC21:02
*** NeoMatrixJR has joined #xdandroid21:04
*** zycho_ has joined #xdandroid21:05
*** zycho__ has quit IRC21:08
*** arrrghhh has joined #xdandroid21:18
arrrghhhF22, seems that SD card issue is fixed.21:21
arrrghhhi wouldn't say "absolutely", but a few users that were having the issue are no longer having it.21:21
*** arrrghhh has quit IRC21:28
*** bzo has joined #xdandroid21:43
*** MassStash has joined #xdandroid21:46
*** bs123 has quit IRC21:56
*** jonpry has quit IRC22:08
Bear_So reinstalled everything Fresh, and still cannot load droid on my VZW Touch pro 2 earlier i was advised to DL updated files and replace the ones I have, and verified that my startup is set for the rhod500\22:40
Bear_loading screen goes across the screen and start menu appears at the bottom, phone never reboots and goes to the droid loading screen or etc22:41
NeoMatrixJRanyone know what arrrghhh ment by sd card issue fixed?22:46
NeoMatrixJRBear_ that usually happens if you're missing zImage I think22:47
manekinekoBeaar_ did you copy in your appropriate startup.txt?22:48
NeoMatrixJRor if it's not named exactly the same (case and all) as it is in your startup.txt file22:48
manekinekoNeoMatrixJR: He means how some SD cards weren't working with the clock fix from a few builds back22:48
manekinekolatest build broke the clock fix, fixing the SD cards22:48
NeoMatrixJRoh :( I hoped there was a dismount fix so my card wouldn't keep corrupting22:48
Bear_I have z image22:48
Bear_dated 2/10/11 1/57 mb22:49
manekinekoaccording to stinebd, a dismount fix isn't possible until NAND22:49
*** Fudge has quit IRC22:49
NeoMatrixJRyeah... :(22:50
manekinekoBear_, did you copy in a startup.txt?22:50
NeoMatrixJRI was going to check with [acl] to see if he's ever experienced data corruption on NAND22:50
manekinekoNeo: http://bugs.xdandroid.com/show_bug.cgi?id=8922:50
xdandroidBug 89: normal, Normal, ---, developers, RESOLVED LATER, File system errors build up over time22:50
NeoMatrixJRI *MIGHT* just switch if it works fine22:50
NeoMatrixJRsounds like it won't then.  I think they still have rootfs on SD even for the NAND guys.22:52
manekinekoI guess at that point they might start looking into the problem it sounds like22:52
NeoMatrixJRdoes it even need the rootfs once a data.img is created?22:52
manekinekoyeah, it does22:52
NeoMatrixJR(unless there's a new one)22:52
manekinekoI'm not an expert on the details, but at the very least, it references it on every boot22:53
manekinekoto run scripts and copy relevant files22:53
NeoMatrixJRyeah.  I thought that system.ext3 and rootfs.img basically coppied into the data.img22:53
NeoMatrixJRoh well...  Thanks for the info manekineko.  it's sleep time now.22:54
manekinekonp22:54
rpierce99Bear_: make sure your startup.txt has a rel_path= statement if your zImage isn't in the root of your sd card22:55
*** NeoMatrixJR has quit IRC22:56
*** arrrghhhTP2 has joined #xdandroid22:58
arrrghhhTP2zomg search button.  You are the shit F2222:59
arrrghhhTP2crispee: duuuuuuuuuuuuude23:02
hycno, the rootfs and system.ext are all mounted live23:15
hycnot copied into data.img23:15
arrrghhhTP2F22: ask crispee if he still gets the screen alignment issue on his raph80023:15
arrrghhhTP2Crap did I miss something?23:15
manekinekowhat was the purpose of splitting the rootfs and system?23:16
F22arrrghhh: if i see him, i will.23:16
F22arrrghhh, btw, i take you're enjoying the search button? :P23:16
arrrghhhTP2Hell yes23:17
arrrghhhTP2Let's me autocomplete in andchat finally :D23:17
hycI think the system.ext2 contents are relatively vanilla from the android build system23:17
hycwhile the rootfs is all custom to these MSMs23:17
manekinekomakes sense23:17
hycso mainly it's a bunch of scripts and shims to get between kernel startup and android system running23:18
F22hyc: the auo panel is a recent add. but apparently there may be more than one auo panel id. i need to look at the camera tree, i hear all the panels are coded in there.23:18
hycyeah, I see a couple IDs for each panel23:19
hychaven't looked at the camera code tho23:19
arrrghhhTP2F22: wistilt2 has done just that AFAIK23:19
arrrghhhTP2g2g23:21
*** arrrghhhTP2 has quit IRC23:22
*** rpierce99 has quit IRC23:24
« Monday, 2011-02-14 Index Wednesday, 2011-02-16 »

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