| *** d3tul3 has quit IRC | 00:10 | |
| *** ryannathansSLEEP is now known as ryannathans | 00:14 | |
| *** helicopter88 has joined #xdandroid | 04:50 | |
| *** cal2_phone has joined #xdandroid | 05:17 | |
| *** xdandroid has joined #xdandroid | 05:29 | |
| raffadna | Hi guys could some body help me with my HtC touch pro ?I've installed FroyoB Thunderbolt v1 but Haret does not run... | 05:29 |
|---|---|---|
| helicopter88 | raffadna: this isn't the proper channel for non-xdandroid builds,come on #neopeek to get help | 05:30 |
| raffadna | I would like only to know the best version for my device,I used an xda builds but now il does not work anymore and I don't know why... | 05:33 |
| *** cal2_phone has quit IRC | 05:35 | |
| *** cal2_phone has joined #xdandroid | 05:35 | |
| helicopter88 | I'm currently using frx07 or neofroyo,first one is more stable,the second one is faster,but there are more bugs | 05:35 |
| raffadna | could you suggest the best builds for my HtC touch pro raphael?? | 05:44 |
| *** helicopter88 is now known as heli_bf3 | 05:51 | |
| *** hardwalker has quit IRC | 06:10 | |
| *** cal2_phone has quit IRC | 06:24 | |
| raffadna | is there somebody that have HTC TOUCH PRO RAPHAEL?? | 06:24 |
| *** d3tul3 has joined #xdandroid | 06:43 | |
| *** heli_bf3 is now known as heli_AWAY | 06:49 | |
| *** raffadna has quit IRC | 06:56 | |
| *** emwe has joined #xdandroid | 07:22 | |
| *** mgross029 has joined #xdandroid | 07:39 | |
| mgross029 | emwe / detule / arrrghhh... My radio dropped this morning just randomly... I was able to grab a radio log for your reading pleasure... :p http://pastebin.com/LbUx0CcY | 07:40 |
| mgross029 | This is similar to what has been happening with the latest .27 + acoustic... Typically after a call | 07:41 |
| emwe | mgross029: this was with what components running? kernel and userland version. | 08:06 |
| emwe | apart from that off to a meeting soon anywa.y | 08:06 |
| mgross029 | modules-2.6.27.46-01358-g9d1b587.tar.gz this is the .27 kernel | 08:07 |
| mgross029 | This was on Froyo btw... | 08:09 |
| detule | that PDSS command is mysterious | 08:29 |
| detule | or rather those responses | 08:30 |
| *** helicopter88 has joined #xdandroid | 08:30 | |
| detule | not sure what prompts those but i don't see it in the log, maybe something before the log started | 08:31 |
| detule | mgross029, here's some conversation about it http://xdandroid.com/irclogs/%23xdandroid.20110404.log.html | 08:34 |
| detule | sounds like it's something location related - were you using the maps app? (going by what i am reading in the irc log here) | 08:36 |
| mgross029 | detule, Thanks... I was using WAZE yes... | 08:37 |
| detule | with gps on | 08:37 |
| mgross029 | Correct... | 08:37 |
| mgross029 | It's happened after a call too... | 08:38 |
| emwe | re | 08:42 |
| *** d3tul3 has quit IRC | 08:42 | |
| emwe | always when i look into radiolog it's like a pig looking into a clockwork. | 08:43 |
| detule | not even sure if that's what choked your radio.... | 08:43 |
| detule | same here | 08:43 |
| emwe | detule: regarding new toolchain, what was your question? | 08:43 |
| detule | oh does the make command differ? | 08:43 |
| detule | i saw there are some parameters you could issue, but is the need for those negated by whatever patches on make in the config files | 08:44 |
| emwe | yap, there's either that make param to produce alligned code assignes, or rather forbid unaligned, or you can disable a kernel config option which disables the sw alignment trap and does it in hw | 08:45 |
| emwe | i got a .35 patch it. it's dead simple. | 08:45 |
| emwe | detule: http://dl.dropbox.com/u/12183048/htctopaz/dot35/patches/0001-defconfig-disable-sw-alignment-trap-with-codesourcer.patch | 08:46 |
| detule | k so kernel config and then same make command | 08:46 |
| mgross029 | emwe, great job on the latest .35 kernel... Really runs weill... Only tried it in Froyo so far... | 08:47 |
| *** cal2_phone has joined #xdandroid | 08:47 | |
| emwe | mgross029: that .35 isn't really different what was before | 08:47 |
| emwe | only calmed down smd rpcrouter debugging... whcih might have an impact. dunno. | 08:48 |
| mgross029 | Yeah I noticed there wasn't much changed but it seemed to run faster... | 08:48 |
| mgross029 | Possibly... | 08:48 |
| emwe | mgross029: perhaps the very verbose debugging had its effects | 08:48 |
| emwe | detule: you are gonna test performance with new toolchain? | 08:49 |
| detule | well i tried to build 39 with your 35 patch and same make command i was issuing as before and it wouldn't boot (This a week or so ago) | 08:49 |
| detule | i was trying to figure out what i did wrong | 08:49 |
| detule | by the way found a missing clock commit on 39 | 08:49 |
| emwe | which explains that slowness? | 08:50 |
| mgross029 | detule, how far did you get on the boot? | 08:50 |
| emwe | regarding toolchain: either new toolchain+patch+no make switch or old toolchain+nopatch+makeparam | 08:50 |
| detule | emwe, no idea if it's going to cure it or not, but i am running with the patch now and if it survives the next 48 hrs without the bug cropping up i'll declare myself the savior of 39 | 08:50 |
| emwe | lol | 08:51 |
| detule | emwe, your clocks are way different | 08:52 |
| detule | than 27 | 08:52 |
| detule | er different to my untrained eyes that is | 08:52 |
| detule | "these non-aligned | 08:58 |
| detule | fetch/store instructions will be emulated in software if you say | 08:58 |
| detule | here, which has a severe performance impact." | 08:58 |
| emwe | detule: that's alex' clocks, and yeah, a tad bit different. | 09:25 |
| emwe | never touched it. | 09:25 |
| emwe | time to rebase ... no time. | 09:25 |
| detule | rebase to what | 09:26 |
| detule | emwe, it doesn't matter that your prox_en and prox_int_n gpios are switched from what's in acl's tree? | 09:40 |
| detule | er nevermind didn't see his later patch -> corrections for gpio my bad | 09:51 |
| emwe | yeah, but what made me whonder is, that his original patch had it like mahimahi board file | 09:56 |
| emwe | if you film the sensor area with another camera you see the blueish light flickering/blinking | 09:56 |
| emwe | does here as well | 09:56 |
| emwe | like in abels youtube vid | 09:56 |
| emwe | having the gpio inverted does not enable it. so it seems correct as it is. just doesn't fire the irq so the isr isn't triggered in the driver. | 09:56 |
| emwe | detule: rebase to alex' tree and start on over. i am tired off cherry picking in his stuff | 09:57 |
| emwe | detule: will have to redo most of the upstream patches and "daily use" fixes. | 09:57 |
| emwe | bbl | 09:58 |
| *** emwe has quit IRC | 09:58 | |
| *** cal2_phone has quit IRC | 10:06 | |
| detule | emwe this more elaborate disable_irq/enable_irq that acl has in the enable function of the driver -> that wouldn't make a difference? | 10:07 |
| *** helicopter88 has quit IRC | 10:39 | |
| *** ryannathans is now known as ryannathansSLEEP | 11:24 | |
| *** GlemSom has joined #xdandroid | 11:43 | |
| mgross029 | detule, still around? | 11:45 |
| detule | in and out | 11:46 |
| mgross029 | Remember when I talking about getting the FC in gb on com.android.phone? | 11:46 |
| detule | yeah | 11:47 |
| mgross029 | Well I put the new .35 kernel on from emwe and now I don't get the FC message, but instead my screen goes black then it goes back to the home screen and the radio gets disabled which disconnects me... | 11:48 |
| mgross029 | Wonder if it has something to do with the prox sensor stuff he is working on... | 11:48 |
| detule | the radio business/back to home screen sounds same as before no? | 11:49 |
| detule | the black screen , dunno that could be prox related i guess, but i was under the impression the proximity sensor wasn't actually working | 11:49 |
| detule | couple of ways you could test this i gues | 11:49 |
| mgross029 | Not exactly... I never get the FC message on my screen... | 11:49 |
| detule | "cat proc/interrupts" | 11:50 |
| detule | see if you see anything about "prox" there | 11:50 |
| mgross029 | While making the phone call right? | 11:50 |
| detule | no before | 11:50 |
| mgross029 | Ok... | 11:50 |
| mgross029 | I have seen prox info in my logcat before... | 11:51 |
| detule | this is different | 11:51 |
| detule | counts how many times the prox interrupt has fired | 11:51 |
| mgross029 | Ok... I'll pull that... | 11:51 |
| detule | so basically read the number once | 11:51 |
| detule | then make a call try to activate the prox sensor and coax it into action | 11:51 |
| detule | and read the number again | 11:51 |
| mgross029 | Yep... How many times it is tapping it on the shoulder... :p | 11:51 |
| detule | if the two numbers differ the interrupt has fired | 11:51 |
| mgross029 | K... | 11:52 |
| *** SpecR has joined #xdandroid | 11:52 | |
| detule | (take all this with a grain of salt, i am no expert on this) | 11:52 |
| mgross029 | NP... Good start... Thanks... I'll post a pastebin when I'm done... | 11:53 |
| detule | i wonder if there is a prox sensor app on the market that will let you do this without using the phone app which already seems faulty | 11:54 |
| mgross029 | Well there is Androsensor which monitors multiple sensors on the phone.. | 11:54 |
| detule | yeah do that or sensor test | 11:55 |
| mgross029 | Ok.. | 11:55 |
| arrrghhh | zDeviceTest as well | 11:56 |
| mgross029 | arrrghhh lives... :p | 11:57 |
| mgross029 | Thought you were sleeping over there... heh | 11:57 |
| arrrghhh | lies | 11:57 |
| arrrghhh | eh, working. same difference. | 11:57 |
| arrrghhh | lol @ elesbb | 11:58 |
| mgross029 | Yeah... Me too... Swamped but always time for some xdandroid fun... :p | 11:58 |
| arrrghhh | hehe | 11:58 |
| arrrghhh | i have soooo much crap to do today. probably won't be around much. just caught up on the logs | 11:59 |
| arrrghhh | i saw prox stuff and got excited :P | 11:59 |
| mgross029 | Our next Disaster Recovery test starts Monday... Bleh... | 12:00 |
| arrrghhh | hhe | 12:01 |
| arrrghhh | joy | 12:01 |
| arrrghhh | we've gotta do one of those soon | 12:01 |
| arrrghhh | disconnect cables, shutdown servers, see what explodes. | 12:01 |
| mgross029 | We go rebuild everything in NJ... | 12:02 |
| arrrghhh | ouch | 12:02 |
| arrrghhh | we have a facility in another state | 12:02 |
| arrrghhh | that is quickly becoming an exact mirror of our data center here | 12:02 |
| mgross029 | Luckily I don't have to go up there this time... Manager and Director are going, so that should be interesting... heh | 12:02 |
| arrrghhh | nice | 12:02 |
| mgross029 | I keep pushing to insource ours, but no money... | 12:03 |
| arrrghhh | yea, that's always the problem | 12:04 |
| detule | er mgross029 which gb are you running? | 12:04 |
| arrrghhh | we're spending a shitton of money to have this alternate data center mirror our DC up here. | 12:04 |
| mgross029 | emwe's acoustic version... | 12:04 |
| detule | the prox stuff in libsensors, that's pretty recent | 12:04 |
| detule | chances are whatever you are running doesn't have userland support for prox | 12:05 |
| arrrghhh | yea, i don't think emwe put that in our image... i can't remember. | 12:05 |
| arrrghhh | so many images. | 12:05 |
| detule | (it wouldn't/shouldn't even be polling the sensor) | 12:05 |
| mgross029 | It isn't... | 12:05 |
| mgross029 | Actually just lost connection to it from ADB and I can't turn the screen back on... | 12:06 |
| *** emwe has joined #xdandroid | 12:07 | |
| arrrghhh | how goes it emwe | 12:07 |
| mgross029 | He was listening... | 12:07 |
| mgross029 | heh | 12:07 |
| mgross029 | detule, actually I think I was wrong... 154: 0 msmgpio capella_cm3602 | 12:09 |
| mgross029 | That shows up on /proc/interrupts | 12:09 |
| detule | right interrupt hasn't fired | 12:10 |
| mgross029 | That was when the phone was idle... | 12:10 |
| *** emwe has quit IRC | 12:10 | |
| mgross029 | Interrupt probably won't fire until I make a phone call right? | 12:11 |
| detule | i have no idea how that sensor is polled -> might fire on just changes in proximity? | 12:11 |
| mgross029 | Ok... Yeah... Didn't even get to the market before it locked up on me... rebooting now... | 12:12 |
| detule | i think the market exercise is pointless as is the phone apk business neither of those are looking for proximity if you don't have the right libsensors | 12:12 |
| mgross029 | Understood... | 12:13 |
| detule | (it's probably the case that the prox sensor isn't even powering on) | 12:14 |
| *** emwe has joined #xdandroid | 12:15 | |
| emwe | ehm.... init: no such service 'dhcpcd_wlan0' | 12:15 |
| emwe | damnit. | 12:15 |
| mgross029 | detule, emwe 154: 2 msmgpio capella_cm3602 It fired twice when trying to make a call... | 12:19 |
| emwe | that's the enable and disable, yes. but it should fire "constantly" when light condition changes. | 12:20 |
| emwe | only then it will trigger reporting | 12:20 |
| mgross029 | Ok... I was pulling a logcat -v time, logcat -v time -b radio and a cat /proc/kmsg plus the cat /proc/interrupts at the same time... I'll look through those to see if anything reported around when the call was made | 12:22 |
| emwe | will likely get an image out later for you guys to test. | 12:26 |
| emwe | supper time. | 12:27 |
| mgross029 | Ok... Thanks emwe... Enjoy... | 12:27 |
| mgross029 | I'll pastbin portions of these logs where the problem occurred... | 12:27 |
| *** caliban2 has joined #xdandroid | 12:28 | |
| arrrghhh | emwe, good eats. new test image for.. prox? :D | 12:28 |
| arrrghhh | hrm | 12:36 |
| arrrghhh | i think my SD card has been thoroughly slaughtered. | 12:36 |
| arrrghhh | it doesn't want to boot any build lol | 12:36 |
| mgross029 | arrrghhh, been seeing 8GB Class 10 on sale for around $10 like crazy lately... | 12:38 |
| *** programmer8922 has quit IRC | 12:39 | |
| caliban2 | yeah arrrghhh, buy a class10 and still be unable to boot any build :D | 12:40 |
| arrrghhh | lol | 12:41 |
| arrrghhh | mgross029, yea i don't know if a c10 card is a good idea | 12:41 |
| mgross029 | I think that is what I am running on... Checking to see what I ordered... | 12:41 |
| mgross029 | Haven't had a problem with booting... | 12:42 |
| arrrghhh | you didn't read teh forums | 12:42 |
| arrrghhh | hyc killed a c10 card after a few months | 12:42 |
| arrrghhh | and some can't use 'em at all | 12:42 |
| arrrghhh | seems to be a crapshoot. | 12:42 |
| arrrghhh | besides, c10 cards are really only good for HD video, like a camcorder. | 12:42 |
| detule | emwe, can you use gpio_to_irq before gpio_direction_input in _setup? this seems erroneous | 12:42 |
| arrrghhh | hrm | 12:43 |
| arrrghhh | i wonder what a defrag would do | 12:43 |
| arrrghhh | i guess it's worth a shot. | 12:44 |
| mgross029 | arrrghhh, well I haven't had any problems... Maybe they are not Class 10... Can't remember where I ordered them from now... | 12:47 |
| arrrghhh | heh | 12:47 |
| arrrghhh | well, there's a lot of people that said c10 cards are bad juju | 12:47 |
| arrrghhh | besides, there's no benefit in our phones... | 12:47 |
| arrrghhh | so why buy c10? | 12:47 |
| mgross029 | Yeah... I saw that after I bought these... | 12:47 |
| *** caliban2 is now known as cal2_afk | 12:47 | |
| mgross029 | I just remember reading it now... | 12:47 |
| *** helicopter88 has joined #xdandroid | 12:48 | |
| mgross029 | C10 is what I've seen on sale lately... Maybe for a good reason... heh | 12:48 |
| arrrghhh | eh like i said they're good in camcorders | 12:49 |
| arrrghhh | downright necessary depending on the quality of video you're shooting. | 12:49 |
| arrrghhh | well defrag seems to be doing something... just retardedly slow | 12:54 |
| arrrghhh | this card probably has had it. couple of years running Android, gawd knows how many formats and reshufflings... | 12:55 |
| detule | arrrghhh, can you use .35 with froyo? | 12:58 |
| arrrghhh | i would assume so | 12:58 |
| arrrghhh | mgross029 said he did... why? | 12:58 |
| arrrghhh | (you'll need an acoustic build, i have a link if you wish) | 12:58 |
| detule | that's ok no sound is fine for now thanks | 12:59 |
| arrrghhh | k | 12:59 |
| arrrghhh | np | 12:59 |
| mgross029 | Finally found it... Bought them back in the beginning of July and they are Class 4... heh | 12:59 |
| arrrghhh | ah | 12:59 |
| arrrghhh | you didn't just look at the card itself? lol | 13:00 |
| mgross029 | detule, Yes... .35 works well with froyo actually... Just sysfs is missing so parts... | 13:00 |
| arrrghhh | you and the ... | 13:00 |
| arrrghhh | i thought i overused it :P lol | 13:01 |
| mgross029 | Tried but the writing was too small and did not have a magnifing glass... | 13:01 |
| mgross029 | some* not so... | 13:02 |
| *** spiker has joined #xdandroid | 13:26 | |
| emwe | detule: can you elaborate a bit more? | 13:29 |
| *** rpierce99 has joined #xdandroid | 13:40 | |
| detule | emwe, http://www.mjmwired.net/kernel/Documentation/gpio.txt#360 | 13:41 |
| detule | might be only a design specification... | 13:46 |
| emwe | detule: ok, i don't understand though, yet, why i'd request a irq from that gpio and then don't use it to request_irq() ... | 13:46 |
| emwe | going to try it just in case for the power gpio. | 13:46 |
| *** cal2_afk is now known as caliban2 | 13:48 | |
| emwe | detule: if you got htc_ls_microp.c at hand... either i need a holiday or... get_ls_adc_level() the for-loop. how the hell does it ever reach a high adc_level value? am i just braindead (today)? | 13:50 |
| detule | that loop returns values between 0 and 10 right? | 13:51 |
| *** spiker has quit IRC | 13:51 | |
| detule | emwe, then you map them to lux values in sensors? | 13:51 |
| detule | when i wrote it in dbgfs i had it return adc_level*255/9 to map it on notches between 0 and 255 | 13:53 |
| emwe | detule: yeah, but lets say i get 0x3ff (1023) reported the break conditions is if (adc_value <= levels[i]) ... so if (0x3ff <= 1) the first case. how does adc_level ever get that high then? | 13:53 |
| emwe | oh lol. brainded. haha. | 13:53 |
| emwe | oh boy. | 13:53 |
| emwe | forget. ignore. erase chatlogs. plz. someone. | 13:54 |
| emwe | sheesh. | 13:54 |
| arrrghhh | lol | 13:54 |
| arrrghhh | the damage has been done emwe | 13:54 |
| emwe | unbelievable arrrghhh. | 13:55 |
| arrrghhh | :P | 13:55 |
| rpierce99 | don't worry emwe, arrrghhh has no idea what you just said | 13:56 |
| arrrghhh | are you assuming that because you have no idea what he just said? lol | 13:56 |
| emwe | nah, he just plays dumb for not having to maintain userland. | 13:56 |
| rpierce99 | no i'm assuming that because you don't write code arrrghhh | 13:56 |
| arrrghhh | you forget i used to | 13:57 |
| arrrghhh | and i still poke around.. yeesh. | 13:57 |
| rpierce99 | i'll believe it when I see it :) | 13:57 |
| arrrghhh | i've done some rootfs modifications | 13:57 |
| arrrghhh | nothing fancy. | 13:57 |
| arrrghhh | who cares? i never pretend to be a developer. | 13:58 |
| rpierce99 | i'm not judging | 14:00 |
| rpierce99 | no need to be sensetive | 14:00 |
| rpierce99 | it was a joke because you made it seem like you were judging emwe, which was also a joke I'm sure | 14:01 |
| emwe | it was not funny i pulled the idiot card ;) | 14:02 |
| arrrghhh | whole lotta judging going on | 14:02 |
| arrrghhh | i don't see any swimsuit models | 14:03 |
| *** helicopter88 is now known as helicAWAY | 14:08 | |
| detule | ugh 35 boots in landscape | 14:08 |
| detule | i can't flip the kbd open | 14:08 |
| arrrghhh | in FroYo? | 14:08 |
| detule | yeah | 14:08 |
| arrrghhh | hit the back button | 14:08 |
| detule | that worked thanks | 14:09 |
| arrrghhh | np | 14:09 |
| emwe | what? landscape? | 14:10 |
| emwe | i should be silent for today. it's for sure a totally obvious thing why it boots in landscape. just to dumb to grasp it. sure. | 14:11 |
| detule | well i can't test anything on the sensor because it doesn't even power up for me....which i guess makes sense, it powers up on enable/disable from userland right? | 14:14 |
| emwe | detule: yes. fire up AndroSensors or zDeviceTest | 14:15 |
| detule | emwe on froyo? | 14:16 |
| emwe | ah eh | 14:16 |
| emwe | ;) | 14:16 |
| emwe | i think it just reads without any enable/disable | 14:16 |
| emwe | don't care that much for froyo honestly. | 14:16 |
| detule | sure....i didn't see it power on in _probe | 14:17 |
| detule | i tried putting that gpio_to_irq after gpio_direction for p_out | 14:18 |
| emwe | doesn't it say it's common error calling gpio_direction_input() without doing gpio_to_irq() before? and that is already done. | 14:20 |
| *** caliban2 is now known as cal2_afk | 14:21 | |
| detule | emwe, i think it says that it is an (unchecked) error to call gpio_to_irq without calling gpio_direction_input first | 14:22 |
| detule | this is what i see happening in the _setup function in the driver | 14:22 |
| emwe | that's how abel has it on .27 nand and htc on ace-.35 | 14:23 |
| emwe | ok, that gpio.txt wording leaves room for mine and your interpretation honestly. | 14:25 |
| detule | i don't know it makes sense though to declare the gpio as input before requesting an interrupt for it.....dunno perhaps my ignorance is showing....not worth much but microp-keypad is setup the way i am saying | 14:25 |
| detule | what's a good driver to check? | 14:25 |
| emwe | one not touched by htc and us? ;) | 14:26 |
| detule | right | 14:26 |
| detule | something generic :) | 14:26 |
| *** helicAWAY is now known as helicopter88 | 14:28 | |
| detule | though if acl's driver is setup the same way , and his seems to be working properly, than in all likelihood this is not an issue | 14:31 |
| arrrghhh | did prox actually work for him? | 14:35 |
| arrrghhh | i think he said it partially worked, but the numbers seemed skewed | 14:36 |
| emwe | detule: moved the gpio_to_irq below the gpio_direction_input(). no help. | 14:37 |
| detule | emwe, thanks for entertaining my ideas on a busy day | 14:38 |
| emwe | it was an idea, so why not try it. | 14:38 |
| *** raymonddull has joined #xdandroid | 14:45 | |
| detule | btw the clock commit on 39 was a fruitless labor | 14:45 |
| arrrghhh | aw | 14:45 |
| *** raymonddull is now known as ray|sleep | 14:49 | |
| *** cal2_afk is now known as caliban2 | 14:56 | |
| *** raffadna has joined #xdandroid | 15:14 | |
| *** NeoMatrixJR has joined #xdandroid | 15:38 | |
| emwe | detule: got varying - userland conrolled - keyboard backlight going. buttons don't do varied, as liblights just does on/off. you think it's worthwhile making it varied as well? think so that would be good. | 15:44 |
| *** elesbb has joined #xdandroid | 15:46 | |
| *** f00bar80 has joined #xdandroid | 15:47 | |
| f00bar80 | i have FRX07_Full_Bundle_20110715 on RHOD210 for more than 3 weeks now, today i can't boot in , on screen keep throwing duplicate definition for service, any idea what's wrong ? | 15:49 |
| arrrghhh | f00bar80, i'd guess data.img blasting would be in order | 15:50 |
| f00bar80 | arrrghhh, so i need to replace data.img ? | 15:51 |
| arrrghhh | just as a test | 15:51 |
| arrrghhh | rename it | 15:51 |
| arrrghhh | data.bak | 15:51 |
| f00bar80 | arrrghhh, renamed it to data.bak , tried to boot, got the new data created and again getting the same errors on the screen , init.rc: #: iginred duplicate definition of service .. | 15:56 |
| arrrghhh | wth | 15:57 |
| arrrghhh | you're not running anything special? | 15:57 |
| arrrghhh | just FRX07.1? what kernel/rootfs? | 15:57 |
| arrrghhh | i had this issue when i was testing acoustic and .35 | 15:57 |
| arrrghhh | i figured it was related to one of those two things... | 15:57 |
| f00bar80 | which comes with this bundle , didn't get any custom kernel or fs | 15:57 |
| arrrghhh | wow | 15:58 |
| detule | emwe non-varied i think is fine | 15:58 |
| arrrghhh | that's... odd. | 15:58 |
| arrrghhh | i guess backup all your data on the card and format it with the HP tool...? | 15:58 |
| arrrghhh | i don't know what would cause that duplicate definition error. | 15:58 |
| detule | emwe, i have the CAPS/FN patches ready....you bored from working on other things? | 15:58 |
| *** caliban2 is now known as cal2_doom2 | 15:59 | |
| emwe | detule: i think i was too fast waiting for your answer... | 15:59 |
| emwe | detule: can keep it gb for now. | 15:59 |
| f00bar80 | arrrghhh, FRX07.1_Full_Bundle is the last release ?? | 15:59 |
| emwe | detule: patches for froyo or gb? | 16:00 |
| emwe | and no.. i am not bored. | 16:00 |
| arrrghhh | f00bar80, full bundle, yes. | 16:00 |
| arrrghhh | there's been some minor updates to the incrementals | 16:00 |
| detule | emwe kernel patches are for 27 | 16:00 |
| arrrghhh | but nothing major. nothing that would effect RHOD | 16:00 |
| f00bar80 | arrrghhh, then i have to reinstall :S | 16:01 |
| arrrghhh | f00bar80, ? | 16:01 |
| detule | emwe, the userland patches are built for froyo but i suspect they might be identical i just copy pasted cyano | 16:01 |
| emwe | detule: send them along so i can look and see what you did. ;) | 16:01 |
| arrrghhh | f00bar80, backup the card, format it, restore the data. | 16:01 |
| arrrghhh | unless you want to start over... i don't care. | 16:01 |
| f00bar80 | arrrghhh, is there no upcoming 2.3 ? | 16:02 |
| detule | emwe, for the record this needs to be tested on RAPH and whatever other devices have caps/fn led | 16:02 |
| arrrghhh | f00bar80, we've had a gb build for months now. Since March. | 16:02 |
| arrrghhh | it's just not as stable | 16:02 |
| emwe | arrrghhh: you must admit that olg gb build isn't on par how gb is now. | 16:03 |
| arrrghhh | emwe, but you must admit, even with the newest changes you've made the GB build still isn't as good as FroYo... | 16:03 |
| emwe | arrrghhh: i don't use froyo. wouldn't dare to go back honestly. | 16:04 |
| emwe | i can't complain. still waiting your jitless experiments. | 16:04 |
| arrrghhh | data flakiness is especially maddening. i was running it for a few days there, and now i can't get a data cxn at all. | 16:04 |
| arrrghhh | i needs mah data. | 16:04 |
| emwe | hm. | 16:04 |
| arrrghhh | yea, i was running with JIT on. seemed fine. didn't try to recreate the bug tho | 16:04 |
| arrrghhh | the reason we disabled it so long ago... | 16:04 |
| emwe | going to google a bit for the data issue. | 16:04 |
| arrrghhh | but i'm on a conference call. bbl. | 16:04 |
| f00bar80 | arrrghhh, from where i can get the gb bundle ? | 16:04 |
| arrrghhh | probably some PPP differences emwe | 16:05 |
| arrrghhh | f00bar80, the forums? | 16:05 |
| arrrghhh | same place you got the FroYo build from... | 16:05 |
| emwe | f00bar80: don't try it. stick to froyo unless there's a new gb build, honeslty. | 16:05 |
| arrrghhh | lol | 16:05 |
| arrrghhh | mister i won't go back to froyo :P | 16:05 |
| emwe | that old build compared to the new is imho comparing apples and carotts. | 16:06 |
| arrrghhh | no offense, but other than GPS what's fixed on the new? | 16:06 |
| emwe | ok, i am exagerating a bit :P | 16:06 |
| f00bar80 | arrrghhh, url ? | 16:06 |
| arrrghhh | f00bar80, i don't have time, you can't search!@?!!? | 16:06 |
| arrrghhh | GBX0A | 16:06 |
| emwe | arrrghhh: ok, i am biased. | 16:06 |
| arrrghhh | emwe, :P | 16:06 |
| *** elesbb has quit IRC | 16:07 | |
| emwe | whonder what i was committing the last months to gb when it didn't improve. | 16:07 |
| arrrghhh | dunno. new gb release would be nice, but stine doesn't want to release until the BT blocker on TI is resolved. | 16:07 |
| emwe | ok, could replicate the crash with topa and .27-acoustic kernel | 16:10 |
| emwe | (acoustic doesn't matter here) | 16:10 |
| detule | emwe, sent, let me know if you have feedback | 16:10 |
| emwe | detule: might need till tomorrow. | 16:10 |
| detule | WHAT?!?! | 16:10 |
| arrrghhh | lol | 16:10 |
| detule | :) | 16:10 |
| emwe | arrrghhh: here's the likely gb-ti-bt fix: https://github.com/CyanogenMod/android_frameworks_base/commit/748b1df8fc2bbd8877cbdaab50695641c860ff88#core/jni/android_server_BluetoothEventLoop.cpp wasn't hard to find with some google translate of a chinese site :) | 16:26 |
| arrrghhh | lol | 16:26 |
| arrrghhh | pass it on to stinebd | 16:26 |
| arrrghhh | or try it yourself, you haz raph | 16:26 |
| emwe | and topa on which i just replicated. | 16:27 |
| arrrghhh | ah, i forgot TOPA is TI as well. | 16:27 |
| arrrghhh | so it's fixed it on TOPA...? | 16:27 |
| arrrghhh | or you recreated the BT bug on TOPA? | 16:27 |
| emwe | bug recreated. just found the patch.... but not the patch download button on github. WTF. | 16:28 |
| arrrghhh | ah | 16:29 |
| arrrghhh | lol | 16:30 |
| emwe | it#s a fucking one liner. nevertheless wan't to give credit. | 16:30 |
| arrrghhh | hum | 16:31 |
| arrrghhh | well i would test the patch, to see if it indeed fixes the problem. | 16:32 |
| arrrghhh | then worry about giving credit... | 16:32 |
| detule | emwe, | 16:32 |
| detule | on github | 16:32 |
| detule | add .patch | 16:32 |
| detule | to the commit URL | 16:32 |
| detule | it will spit out the .patch | 16:32 |
| emwe | thank you detule :) | 16:33 |
| arrrghhh | heh. that's a cute trick. | 16:33 |
| f00bar80 | arrrghhh, i think you have a RHOD210 or maybe i'm wrong, this GBX0A has any issues on RHOD210 ?? | 16:34 |
| arrrghhh | i have a 400 | 16:34 |
| arrrghhh | the issues are listed in the thread. | 16:34 |
| emwe | detule: you are keeping up to date with froyo repo? | 16:37 |
| detule | er that's a good question, not in a month or so damnit, do i need to rebuilt those patches | 16:38 |
| emwe | detule: thinking about pushing the varied button thingy also to froyo so we keep the two trees in sync. if we don't like it, we can go back later on, or just fix up the overlay config.xml. | 16:38 |
| arrrghhh | are you going to un-patch the kernel as well...? | 16:38 |
| arrrghhh | remove wistilt2's hack for getting it to work is what i mean. | 16:38 |
| emwe | not looked at the patches. i do assume that went out. :) | 16:39 |
| detule | emwe, by the way i found a small one-line change that allows the PowerManager to make light adjustments on-the-fly rather than only on screen on | 16:39 |
| detule | emwe, i don't quite understand, the varied button backlight -> that's just an overlay change right? | 16:39 |
| emwe | detule: it's a liblights change as well. we can change what values go to kernelland via the overlay table, though. we can make it all 255 if we like. | 16:40 |
| emwe | detule: just don't wan't the code between the branches identical | 16:41 |
| emwe | going to push the little thingy. likely someone needs to "fixup" froyo overlay config.xml like i did for froyo. | 16:41 |
| emwe | (if that is yet perfect is written on another paper) | 16:41 |
| *** cal2_doom2 is now known as caliban2 | 16:42 | |
| detule | emwe, you don't want the code between the branches identical? man i am slow today | 16:42 |
| emwe | detule: no, i wan't it identical. and i already pushed the liblights patch to gb. and then you said you'd like to keep buttons fixed, not varied. but i just pushed to froyo as well as like them to be identical. if we don't like it, we revert on both branches. | 16:43 |
| detule | oh looking at the patch now...whew understood - i think what you are doing is just fine | 16:45 |
| emwe | i can only guess it's fine :) | 16:45 |
| *** NeoMatrixJR has quit IRC | 16:46 | |
| detule | k i may need to rebuild those liblights patches i sent you against this current tree | 16:46 |
| * emwe keeps secret that button backlight isn't even added for rhod on .35 | 16:46 | |
| emwe | detule: i haven't tried. perhaps they are just fine. | 16:46 |
| emwe | detule: you can rebase quite easily | 16:46 |
| *** mgross029 has quit IRC | 16:46 | |
| detule | "git rebase" is on my "to learn" list | 16:47 |
| emwe | git branch -t froyo-rebase-test; git checkout froyo-rebase-test; git rebase gitorious/froyo -i and then look what happens. | 16:47 |
| *** vw has quit IRC | 16:47 | |
| emwe | (initial command done from your local froyo branch tracking gitorious/froyo) | 16:47 |
| emwe | you can throw all stuff away if it doesn't work out good. worst you need to fixup with a manual merge. | 16:48 |
| detule | magic happens | 16:52 |
| detule | thanks emwe it took me to some sort of a text shell initially that i just ":q" exited out of, then did the rebase | 16:52 |
| stinebd | emwe: that does not fix ti bt btw | 16:53 |
| emwe | stinebd: ouch. you crash my hopes. | 16:56 |
| stinebd | sorry | 16:57 |
| stinebd | just didn't want you wasting your time to roll a test image just for that | 16:57 |
| stinebd | like i did | 16:57 |
| arrrghhh | heh | 16:57 |
| *** NeoMatrixJR has joined #xdandroid | 16:57 | |
| emwe | stinebd: what is though, when it doesn't crash anymore on topa? | 16:57 |
| *** raffadna has left #xdandroid | 16:58 | |
| * stinebd shrugs | 16:58 | |
| stinebd | .35? | 16:58 |
| emwe | stinebd: .27 | 16:59 |
| emwe | stinebd: just discovered my topa from my thinkpad. | 16:59 |
| emwe | dunno what else bt'ish to test... | 16:59 |
| stinebd | could you reproduce the crash on topa before? | 16:59 |
| emwe | yap, half an hour ago | 16:59 |
| emwe | same kernel | 16:59 |
| *** NeoMatrixJR has quit IRC | 16:59 | |
| stinebd | well i don't know about topa, all i know is on my raph it still crashes with that patch | 17:00 |
| *** helicopter88 has quit IRC | 17:00 | |
| *** GlemSom has quit IRC | 17:01 | |
| stinebd | i was going to look at this more on saturday but i gotta work | 17:01 |
| emwe | stinebd: just paired fine. before it just crashed system_server | 17:01 |
| detule | take it easy guys, i am out | 17:02 |
| stinebd | bye | 17:02 |
| emwe | laters detule. | 17:02 |
| emwe | (crashed system_server short after enabling) | 17:02 |
| stinebd | after enabling? | 17:02 |
| stinebd | as in the check mark comes on? | 17:02 |
| emwe | yap | 17:02 |
| arrrghhh | detule, peace | 17:02 |
| emwe | well, used power widget to enable. think that is near the "checkmark" ;) | 17:03 |
| stinebd | did the green line at the bottom come on? | 17:03 |
| stinebd | or was it only kinda green? | 17:03 |
| emwe | darkish green, then crash | 17:04 |
| stinebd | mm | 17:04 |
| emwe | just transfered a file to topa | 17:04 |
| *** mod has left #xdandroid | 17:04 | |
| stinebd | i believe you | 17:04 |
| stinebd | could it be that it needs a make clean? | 17:05 |
| emwe | it has rebuilt quite some stuff | 17:05 |
| stinebd | ok i'll try that and see, then | 17:05 |
| emwe | i got issues with wifi on topa, though. | 17:07 |
| stinebd | what kind of issues? | 17:07 |
| emwe | fails to get an up | 17:07 |
| emwe | ip | 17:07 |
| stinebd | probably missing a merge from froyo | 17:07 |
| emwe | hm... Set_key: Wrong Key << typo in passphrase? | 17:08 |
| emwe | E/wpa_supplicant( 2071): Set_key: Wrong Key | 17:08 |
| emwe | retyping... | 17:08 |
| stinebd | don't bother | 17:09 |
| stinebd | there's a missing merge then | 17:09 |
| stinebd | i had that in froyo when i forgot to merge something | 17:09 |
| emwe | <3>[ 1136.973876] init: no such service 'dhcpcd_wlan0:-h android_ad07f88d53a0d8ac wlan0' | 17:10 |
| emwe | stinebd: you still remember in which area? | 17:10 |
| stinebd | libh_l or system/core or some crap | 17:12 |
| emwe | can't spot stuff in libh_l | 17:19 |
| emwe | system/core has some bcrm patchram stuff | 17:19 |
| *** d3tul3 has joined #xdandroid | 17:21 | |
| stinebd | also check init.rc | 17:21 |
| stinebd | it was something painfully nonobvious | 17:23 |
| emwe | stinebd: that's the only diff. the rest i took over some time ago. | 17:31 |
| emwe | http://pastebin.com/fR2CwzNM | 17:31 |
| *** gs0 has quit IRC | 17:50 | |
| *** gs0 has joined #xdandroid | 17:52 | |
| d3tul3 | emwe, i think i was overthinking something when i was writing that kernel patch -> i'll have something more elegant tomorrow | 18:06 |
| *** f00bar80 has quit IRC | 18:06 | |
| emwe | d3tul3: no hurries. just gb'ed my RAPH. no froyo device left. | 18:06 |
| arrrghhh | lol | 18:07 |
| arrrghhh | NOES! | 18:07 |
| *** rpierce99 has quit IRC | 18:08 | |
| emwe | arrrghhh: you are in the dog house talking bad about gb. :P | 18:09 |
| arrrghhh | lol | 18:09 |
| arrrghhh | i love gb, just wish i could run it daily | 18:09 |
| arrrghhh | the data issues kill me... | 18:09 |
| emwe | let me google shortly tomorrow for a one liner. | 18:10 |
| *** f00bar80 has joined #xdandroid | 18:11 | |
| arrrghhh | lol | 18:11 |
| arrrghhh | emwe, you keep it up brotha. one line at a time... | 18:11 |
| arrrghhh | :P | 18:11 |
| emwe | yah, better then my never finished .35 | 18:12 |
| emwe | "my" is relative. | 18:12 |
| emwe | ok, raph doesn't crash with gb-tibt | 18:12 |
| emwe | but somehow very flaky to discover from thinkpad. | 18:12 |
| arrrghhh | wow | 18:12 |
| emwe | i'll let stine verify. going to hold on. | 18:13 |
| arrrghhh | if you want cook up an image | 18:14 |
| arrrghhh | i haz a RAPH i can test on.l | 18:14 |
| arrrghhh | er | 18:14 |
| arrrghhh | on | 18:14 |
| emwe | arrrghhh: you still got the .27-acoustic kernel around? | 18:18 |
| emwe | arrrghhh: and btw.. did i name the other images frx07.1plus instead gbx0aplus? | 18:18 |
| arrrghhh | yes you named them frx07.1plus | 18:18 |
| arrrghhh | and i don't have the RAPH here now... | 18:18 |
| arrrghhh | but i do have a .27 acoustic kernel for it | 18:18 |
| emwe | ok. just packed up the sytem image. | 18:19 |
| arrrghhh | cool | 18:19 |
| emwe | arrrghhh: mail out. have fun. | 18:23 |
| arrrghhh | thanks | 18:23 |
| arrrghhh | so that's for testing on RAPH | 18:24 |
| arrrghhh | on .27+acoustic | 18:24 |
| emwe | for any device. | 18:24 |
| arrrghhh | and see what BT does? | 18:24 |
| arrrghhh | oh? | 18:24 |
| emwe | yes, acoustic | 18:24 |
| arrrghhh | wat am i testing | 18:24 |
| emwe | yeah, includes the likely tibt | 18:24 |
| emwe | fix | 18:24 |
| arrrghhh | k | 18:24 |
| emwe | you can drive it on the rhod as well, though i meant. | 18:24 |
| emwe | also try wifi on raph. shouldn't work. can't get it to work on raph and topa | 18:25 |
| emwe | can't get ip adress dhcp'ed. | 18:25 |
| emwe | i am out. leaving the box on though for the upload. | 18:25 |
| emwe | gnight. | 18:25 |
| *** emwe has quit IRC | 18:25 | |
| arrrghhh | damn you emwe | 18:28 |
| stinebd | MCGUIRK | 18:30 |
| arrrghhh | he said the build includes prox... what a tease. we all know that doesn't work. | 18:31 |
| *** vinceweis_ has joined #xdandroid | 18:43 | |
| *** d3tul3 has quit IRC | 18:55 | |
| *** programmer8922 has joined #xdandroid | 18:55 | |
| *** vinceweis has joined #xdandroid | 19:06 | |
| *** vinceweis_ has quit IRC | 19:06 | |
| *** vinceweis has quit IRC | 19:08 | |
| *** vinceweis has joined #xdandroid | 19:10 | |
| *** vinceweis has quit IRC | 19:53 | |
| *** programmer8922 has quit IRC | 19:57 | |
| *** d3tul3 has joined #xdandroid | 20:18 | |
| *** hardwalker has joined #xdandroid | 20:25 | |
| *** d3tul3 has quit IRC | 20:53 | |
| *** programmer8922 has joined #xdandroid | 20:56 | |
| *** programmer8922 has quit IRC | 21:03 | |
| *** rpierce99 has joined #xdandroid | 21:12 | |
| *** rpierce99 has quit IRC | 21:48 | |
| *** rpierce99 has joined #xdandroid | 21:49 | |
| *** rpierce99 has quit IRC | 21:53 | |
| *** Ivo has quit IRC | 22:06 | |
| *** programmer8922 has joined #xdandroid | 22:14 | |
| *** rpierce99 has joined #xdandroid | 22:29 | |
| *** TheSeven has quit IRC | 22:57 | |
| *** [7] has joined #xdandroid | 22:57 | |
| *** ryannathansSLEEP is now known as ryannathans | 23:14 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!