| 00:03.11 | jonpry | detule did we ever get one of those smd dump in kernel things for a WCDMA event? |
| 00:34.33 | detule | no |
| 00:34.50 | detule | i would be very curious to see what the smd dump has to say when that happens jonpry |
| 00:36.44 | detule | updating usb/core will be a pain |
| 00:37.23 | detule | i think we can't use the android stuff from the new google trees because 3.0 and above i think are geared towards ics and they've changed some of the userland interface |
| 00:37.44 | detule | so we are stuck with their .39 tree which expects a bit backwards usb/core |
| 00:38.25 | jonpry | ouch |
| 00:38.47 | jonpry | however i ran ics on 39 kernel |
| 00:39.05 | jonpry | and adb was fine. so maybe the userland part is compatible? |
| 00:40.18 | jonpry | i have a suspicion that the ril's text parser is messing something up because these messages use spaces and other strange character |
| 00:40.41 | jonpry | however when that is fixed i think the result will be the same |
| 00:41.12 | jonpry | i think its reauthing to the network and refuses to deal with +clcc |
| 00:41.22 | jonpry | and it could take serious time depending on how bad the signal is |
| 00:41.29 | jonpry | or never complete |
| 00:44.38 | detule | whenever it issues that +clcc command it expects a string coming back starting with "+clcc"...if it doesn't see that i can see it getting stuck waiting |
| 00:48.12 | jonpry | your hacked ril fixes that right? |
| 01:12.11 | ahigerd | Works around it |
| 01:12.13 | ahigerd | Doesn't fix it |
| 01:12.31 | ahigerd | And only for CLCC, not for the other issues (SMS) |
| 01:16.40 | jonpry | you verified the sms bug with the autobuild kernel? |
| 01:16.48 | ahigerd | No, I haven't |
| 01:17.10 | ahigerd | But I haven't tried. |
| 01:18.04 | jonpry | bugs must be continually verified :p |
| 01:19.33 | ahigerd | I know that ^^; But this one is inconsistent enough to make it difficult to know |
| 01:19.56 | ahigerd | No way to tell if it's fixed or if I just haven't tripped it yet |
| 01:21.58 | jonpry | yeah i understand |
| 01:21.59 | ahigerd | wonders if sending texts to himself would be a valid test |
| 01:22.32 | jonpry | do you have a radio log from the failed sms? i really know nothing about the issue |
| 01:22.55 | ahigerd | Had one a week or so ago but I lost the link to the pastebin |
| 01:23.07 | ahigerd | Well... hmm. |
| 01:23.11 | ahigerd | Let me see if I can find it. |
| 01:23.57 | jonpry | would it be in the irc logs? |
| 01:24.15 | ahigerd | That's exactly what I was just checking, and the answer appears to be no, so let me check the GBX0B thread |
| 01:29.55 | ahigerd | Ugh. Not in the thread either. |
| 01:32.04 | *** join/#htc-linux mitsutaka (~mitsutaka@123.116.125.0) |
| 01:33.19 | jonpry | i believe there were two problems. i had the same symptoms as you but never once got a WCDMA |
| 01:33.43 | jonpry | just lost modem responses |
| 01:35.59 | ahigerd | Hmm. I suppose that could possibly be it... |
| 01:45.37 | jonpry | maybe we should just run the window mobile ril |
| 01:48.19 | ahigerd | ...we can do that? |
| 01:48.19 | jonpry | also i have thing that lets you run other htc ril |
| 01:48.26 | jonpry | mostly |
| 01:48.39 | ahigerd | o.o |
| 01:48.43 | jonpry | i've used it to run other windows mobile drivers |
| 01:48.49 | ahigerd | What, something like ndiswrapper for Android? |
| 01:49.05 | jonpry | yeah its based on ndiswrapper. but on steroids |
| 01:49.09 | ahigerd | Heh, wow. |
| 01:49.39 | jonpry | doesn't implement the whole wince api so stuff would need to be written to run the ril |
| 01:49.44 | ahigerd | Ah. |
| 01:50.13 | jonpry | big problem is that the ril's exported api is strange. need some kind of adaptor for android |
| 01:50.18 | ahigerd | I don't suppose we can get lucky and this baseband has been used in a phone that DOES natively run Android? >.> |
| 01:50.38 | jonpry | no its a different amss |
| 01:50.45 | ahigerd | D: |
| 01:50.56 | ahigerd | Oh well. I figure you guys would have tried that a long time ago anyway. |
| 01:51.00 | jonpry | g1 is probably the closest thing |
| 01:51.42 | jonpry | it was done on cdma a long time ago |
| 01:51.57 | jonpry | gsm was more recent |
| 01:52.02 | ahigerd | Ah. |
| 02:05.41 | jonpry | have you considered using a different radio rom? |
| 02:15.06 | ahigerd | I've considered it but don't know where I'd find another one. I know hyc and I have different versions despite having the same phone |
| 02:15.36 | ahigerd | We both have the problem, too |
| 02:17.44 | ahigerd | (I also don't know how to apply it but I figure the instructions would be easy enough to come up with.) |
| 02:25.20 | jonpry | i think these are old for some reason |
| 02:25.22 | jonpry | http://htcpedia.com/forum/touch-pro2-rom-development/437-%5Bresources%5D-rhodium-radio-roms.html |
| 02:25.44 | jonpry | but they can be found |
| 02:26.09 | jonpry | i have some crazy chinese radio that is part of unlocking your phone |
| 02:26.34 | jonpry | *BEWARE* don't install radio's without hard-spl |
| 02:28.34 | ahigerd | Hmm? |
| 02:29.14 | ahigerd | What's hard-spl? |
| 02:30.11 | ahigerd | Uh... also is it a problem that I don't run Windows? >.> |
| 02:32.10 | *** join/#htc-linux mitsutaka (~mitsutaka@219.143.36.82) |
| 02:33.07 | ahigerd | checks phone |
| 02:33.13 | ahigerd | Okay, I'm on 3.45.25.14 right now |
| 02:33.22 | ahigerd | hyc's is slightly newer |
| 02:33.23 | jonpry | hard-spl lets certain not properly signed things |
| 02:33.26 | *** join/#htc-linux mitsutak_ (~mitsutaka@219.143.36.82) |
| 02:33.55 | jonpry | the installers are much easier to use with windows |
| 02:34.36 | ahigerd | Er. Wait. No, hyc's isn't "slightly" newer; it's WAY newer. He's on 4.49.25.57 |
| 02:40.02 | ahigerd | Which makes me dubious of any of these making a difference >.> |
| 02:40.03 | jonpry | can you extract you rilphone.dll? |
| 02:40.55 | jonpry | the one i'm looking doesn't seem to handle these WCDMA messages |
| 02:40.56 | ahigerd | Sure, tell me how and I'll toss it to you |
| 02:41.07 | jonpry | oh i don't remember |
| 02:41.10 | ahigerd | ^^; |
| 02:41.23 | jonpry | some kind of file explorer seemed to work iirc |
| 02:41.44 | jonpry | resco maybe |
| 02:43.27 | jonpry | the ril likes [WCDMA] though |
| 02:44.40 | ahigerd | This will be in WinMo? |
| 02:45.23 | jonpry | yes |
| 02:46.05 | ahigerd | Okay, I'll reboot and try to track it down |
| 02:53.49 | ahigerd | Got it. How should I get it to you? 557KB |
| 03:00.41 | ahigerd | So what's your plan here? Disassemble it and see what's different? |
| 03:02.05 | jonpry | i wanted to see if there was something we were supposed to do when confronted with these strange messages |
| 03:02.21 | ahigerd | Ah, yeah. |
| 03:02.33 | jonpry | your rilphone doesn't seem to handle WCDMA either |
| 03:02.41 | ahigerd | If it helps, this doesn't happen in FRX from what I've heard |
| 03:03.09 | jonpry | that is interesting and i hope its wrong |
| 03:03.39 | jonpry | is that using the same ril and kernel? |
| 03:03.59 | ahigerd | Uh... if FRX is using .27 then same kernel. No clue about the ril; you'd have to ask detule or hyc. |
| 03:04.38 | ahigerd | Wait. It can't be completely the same kernel because FRX doesn't have prox |
| 03:05.03 | jonpry | that could be libsensors |
| 03:05.20 | ahigerd | Suppose that's possible. I guess I can boot into FRX really quick and find out :P |
| 03:05.37 | jonpry | need to make sure its using the same ril |
| 03:06.40 | jonpry | and then try to reproduce. i think this is service related |
| 03:07.18 | jonpry | like you have disparate 2g/3g signal strength and it is effectively switching networks |
| 03:07.18 | ahigerd | No problem, I'll check the kernel version and... um, I suppose I can compare md5sums on the ril? Not quite sure how else to tell if they're the same |
| 03:07.40 | ahigerd | I've been pondering the same thing since I first saw it. |
| 03:07.46 | ahigerd | It happens more often when I'm traveling than when I'm at home. |
| 03:07.46 | jonpry | you should be able to boot frx using the 3.2 kernel |
| 03:08.31 | jonpry | then we know its the same. it might even run detules hack ril.so |
| 03:09.41 | ahigerd | Kernel is 2.6.27.24-01356-gd4c7ebd |
| 03:12.11 | jonpry | so you've personally done this search for WCDMA events under FRX? |
| 03:13.02 | ahigerd | No, I haven't, but I also didn't ever have this problem under FRX. hyc's done more concrete research on the matter; this is actually the first time I've been back in Froyo since I updated |
| 03:15.08 | jonpry | i will ask hyc what he has done about it |
| 03:15.48 | ahigerd | Anyway, I can't confirm or deny the rils; they have different datestamps but no telling if they're built from the same source or not |
| 03:15.59 | jonpry | but i'm wondering if maybe they happen but froyo interprets the ril stuff differently so the effects are different |
| 03:16.42 | jonpry | and if you never get phantom calls. who would bother to check radio log |
| 03:17.11 | ahigerd | Valid point. |
| 03:19.20 | ahigerd | So far I've not seen any [WCDMA] WAKEUP messages though |
| 03:20.19 | jonpry | from rilphone.dll those are harmless. just means the radio is having verbal diarrhea |
| 03:20.36 | ahigerd | Ah. |
| 03:21.26 | jonpry | you are a software developer? |
| 03:21.34 | ahigerd | ...actually that's not even valid, I don't have data turned on XD |
| 03:21.45 | ahigerd | Yeah, C++ mostly |
| 03:22.17 | jonpry | no kernels yet? |
| 03:23.05 | ahigerd | No Android kernels, but I've done embedded kernel work before -- wrote and debugged a driver with an oscilloscope once :P |
| 03:23.35 | ahigerd | FRX is giving me: 03-31 22:22:55.690 D/RILJ ( 1418): [0152]< REQUEST_GET_NEIGHBORING_CELL_IDS error: com.android.internal.telephony.CommandException: GENERIC_FAILURE |
| 03:23.40 | ahigerd | Don't recall seeing anything like that in GBX |
| 03:24.24 | jonpry | probably an old ril. is that frx07+? |
| 03:24.27 | ahigerd | Doing it every 60 +/- 10 seconds |
| 03:24.30 | ahigerd | 07.1, yeah |
| 03:26.03 | jonpry | i wonder what AT?WCDMA=0 would do |
| 03:28.13 | ahigerd | What's it supposed to do, in theory? |
| 03:28.23 | jonpry | unknown |
| 03:28.38 | ahigerd | Oh |
| 04:17.55 | *** join/#htc-linux AstainHellbring (AstainHell@c-67-172-255-225.hsd1.ut.comcast.net) |
| 04:17.58 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 05:06.03 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 05:29.05 | detule | jonpry, this is what I am talking about, pretty sure gingerbread can't handle this https://github.com/android/kernel_common/commit/aab96815ae9a40e05600b8e351561b514233afca#drivers/usb/gadget |
| 05:31.44 | *** join/#htc-linux zeusk (77eb360e@gateway/web/freenode/ip.119.235.54.14) |
| 05:38.03 | jonpry | detule, what is acm? |
| 05:39.02 | detule | no idea |
| 05:40.37 | jonpry | doesn't sound too important |
| 05:41.01 | jonpry | probably can turn on adb with some initrd/rootfs magic |
| 05:41.13 | detule | if java wasn't so nasty we could bring services/java/com/android/server/usb/ from ics |
| 05:41.32 | detule | not quite as easy as syncing folders in the kernel |
| 05:42.33 | jonpry | might be |
| 05:50.39 | *** join/#htc-linux d3tul3 (~detule@pool-96-234-128-143.bltmmd.east.verizon.net) |
| 05:58.30 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 06:02.57 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 06:57.50 | *** join/#htc-linux gabriel_ (bc1bb33e@gateway/web/freenode/ip.188.27.179.62) |
| 06:59.55 | *** part/#htc-linux gabriel_ (bc1bb33e@gateway/web/freenode/ip.188.27.179.62) |
| 07:00.49 | *** join/#htc-linux paulk-desktop (~paulk@lib33-1-82-233-88-171.fbx.proxad.net) |
| 07:16.58 | *** join/#htc-linux gabriel_ (bc1bb33e@gateway/web/freenode/ip.188.27.179.62) |
| 07:40.06 | *** join/#htc-linux |Jeroen| (~jeroen@d5153E8CC.access.telenet.be) |
| 08:03.32 | *** join/#htc-linux |Jeroen| (~jeroen@d5153E8CC.access.telenet.be) |
| 08:32.23 | *** join/#htc-linux rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 09:07.04 | *** join/#htc-linux G4y (~heaheahah@160.8.202.84.customer.cdi.no) |
| 09:40.48 | *** join/#htc-linux helicopter88 (~helicopte@host135-115-dynamic.18-79-r.retail.telecomitalia.it) |
| 10:25.08 | *** join/#htc-linux rrr_ (5923a7ca@gateway/web/freenode/ip.89.35.167.202) |
| 10:43.30 | *** join/#htc-linux mitsutaka (~mitsutaka@123.116.125.0) |
| 10:45.36 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-93-167.dynamic.mnet-online.de) |
| 11:02.35 | *** join/#htc-linux GNUtoo (~gnutoo@host149-73-dynamic.56-82-r.retail.telecomitalia.it) |
| 11:05.30 | *** join/#htc-linux Aqumen (~nnscript@ip5650d5a0.direct-adsl.nl) |
| 11:19.57 | *** join/#htc-linux MacDrunk (~marper@201.165.119.167) |
| 11:20.32 | *** part/#htc-linux MacDrunk (~marper@201.165.119.167) |
| 11:25.08 | *** join/#htc-linux Aqumen (~nnscript@ip5650d5a0.direct-adsl.nl) |
| 11:32.14 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-164-174.netcologne.de) |
| 13:36.22 | *** join/#htc-linux detule (~detule@unaffiliated/d3tul3) |
| 13:59.05 | *** join/#htc-linux bitrot (~rajkosto@2001:470:d76b:da7a:fd2f:5462:fff6:41c1) |
| 13:59.25 | *** join/#htc-linux jonpry (~jon@adsl-98-85-196-230.mco.bellsouth.net) |
| 14:05.34 | *** join/#htc-linux GNUtoo (~gnutoo@host149-73-dynamic.56-82-r.retail.telecomitalia.it) |
| 14:36.58 | *** join/#htc-linux helicopter88 (~helicopte@host135-115-dynamic.18-79-r.retail.telecomitalia.it) |
| 15:02.16 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 15:23.06 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-164-174.netcologne.de) |
| 15:29.48 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 15:52.24 | *** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl) |
| 15:57.17 | *** join/#htc-linux nALLITeT (4df71221@gateway/web/freenode/ip.77.247.18.33) |
| 15:59.57 | nALLITeT | hi all, i have problems with adbd in debian port for HTC Wildfire. I tried manual at http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo#ADB but PC can't find device. |
| 16:08.01 | nALLITeT | but adb can't find device* |
| 16:09.00 | Willd | nALLITeT: Is your kernel adb enabled? |
| 16:11.36 | nALLITeT | yes |
| 16:11.44 | *** join/#htc-linux GNUtoo (~gnutoo@host149-73-dynamic.56-82-r.retail.telecomitalia.it) |
| 16:12.03 | Willd | You sure? :) |
| 16:12.21 | nALLITeT | 100% |
| 16:13.23 | *** join/#htc-linux Alex[sp3dev] (~alexander@178.76.204.13) |
| 16:14.33 | nALLITeT | original htc kernel + CONFIG_USB_ANDROID_ADB=y |
| 16:15.04 | *** join/#htc-linux ahigerd (~ahigerd@173.218.156.102) |
| 16:15.04 | *** join/#htc-linux ahigerd (~ahigerd@libqxt/developer/ahigerd) |
| 16:15.10 | Willd | And the adb usb device is visible on the host system? |
| 16:15.46 | nALLITeT | host system mounts device as storage device |
| 16:16.22 | Willd | There should be more than one device available |
| 16:16.49 | nALLITeT | yeah, there was second device, but i forget its name |
| 16:17.39 | *** join/#htc-linux simpson (77eb360e@gateway/web/freenode/ip.119.235.54.14) |
| 16:22.45 | nALLITeT | debian started, system detected only one device - HTC Android Phone USB Device |
| 16:24.50 | Willd | Yup, which should, in a proper setup, branch out into a few more |
| 17:13.54 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
| 17:15.38 | *** join/#htc-linux yuuki (~yuuki@dsbg-d9bb0aa4.pool.mediaWays.net) |
| 17:16.40 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 17:27.45 | simpson | what is lk_template in tinboot ? |
| 17:29.36 | Alex[sp3dev] | ehm.. an empty disk image with mbr maybe? |
| 17:29.54 | simpson | hm, thanks |
| 17:51.07 | *** join/#htc-linux jonpry (~jon@adsl-98-85-196-230.mco.bellsouth.net) |
| 18:14.24 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
| 18:19.28 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 18:46.33 | *** join/#htc-linux T-Junk (atari@i22172.upc-i.chello.nl) |
| 18:48.00 | *** join/#htc-linux simpson (77eb360e@gateway/web/freenode/ip.119.235.54.14) |
| 19:03.03 | detule | i heart powertop |
| 19:03.35 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 19:10.02 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
| 19:13.20 | *** join/#htc-linux khorben_ (~dont@port-83-236-217-161.static.qsc.de) |
| 19:19.57 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-107-19.dhcp.stcd.mn.charter.com) |
| 19:20.22 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 19:21.26 | *** join/#htc-linux swc|666 (~goldbond@Aircrack-NG/Friend) |
| 19:21.40 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-107-19.dhcp.stcd.mn.charter.com) |
| 19:25.02 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-107-19.dhcp.stcd.mn.charter.com) |
| 19:59.29 | *** join/#htc-linux ftoz (~root@cst-prg-116-34.cust.vodafone.cz) |
| 20:01.40 | *** join/#htc-linux ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 20:13.35 | *** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl) |
| 20:19.08 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 20:51.19 | *** join/#htc-linux jonpry (~jon@adsl-98-85-196-230.mco.bellsouth.net) |
| 21:00.18 | *** join/#htc-linux ahigerd (~ahigerd@173.218.111.126) |
| 21:00.18 | *** join/#htc-linux ahigerd (~ahigerd@libqxt/developer/ahigerd) |
| 21:04.06 | ahigerd | jonpry: Been running FRX since last night, got the [WCDMA] WAKEUP messages now but no spurious WCDMA or GSM messages, and I've been making test calls and test texts |
| 21:04.58 | jonpry | you have a method for logging everything? |
| 21:05.30 | ahigerd | No, but I've been keeping a logcat running whenever I'm home |
| 21:05.41 | ahigerd | And run GetLogs to a text file periodically when I'm out |
| 21:06.37 | ahigerd | I'm partially tempted to have the radio log running through grep and logging directly to SD, but I'm worried a bit about battery usage |
| 21:06.41 | jonpry | probably run logcat -b radio > /data/log in a terminal window |
| 21:06.49 | ahigerd | ^ what I just said ;) |
| 21:07.14 | jonpry | i wouldn't expect much trouble |
| 21:07.26 | jonpry | if there is radio traffic it will wake the processor anyways |
| 21:07.26 | ahigerd | True, if I'm grepping it won't be logging a ton |
| 21:07.46 | ahigerd | But I'd definitely want to grep because of the REQUEST_GET_NEIGHBORING_CELL_IDS error spam |
| 21:09.00 | jonpry | ic |
| 21:09.23 | jonpry | probably grep for CLCC -A4 |
| 21:10.13 | ahigerd | Ah, I was going to do egrep -B2 -A2 "(WCDMA|GSM)" |
| 21:11.39 | ahigerd | Though that'll grab a lot of noise now that I think about it, I'll just leave 3G on |
| 21:11.50 | ahigerd | And just grep for WCDMA |
| 21:11.56 | jonpry | sounds fine |
| 21:14.49 | ahigerd | logcat -v time -b radio | grep -B2 -A2 "WCDMA" | tee /sdcard/wcdma.log |
| 21:14.54 | ahigerd | And I'll just leave that running. |
| 21:15.20 | jonpry | sounds excellent |
| 21:16.11 | simpson | won't logcat be running till you kill it ? so what if you have a reset ? |
| 21:16.37 | ahigerd | I saved that to a shell script. If I have to reboot my phone I'll relaunch it. |
| 21:16.38 | simpson | logcat does not just output log till that time like dmesg but keeps waiting for user to kill it |
| 21:16.46 | ahigerd | Yes, that's the point. |
| 21:16.51 | ahigerd | I want it preemptively logging this stuff when it happens. |
| 21:16.58 | simpson | oh |
| 21:18.07 | detule | not sure how frx vs gbx would make a difference |
| 21:18.18 | detule | esp since hyc has said gbx with .27 is smooth sailing |
| 21:22.26 | ahigerd | Really? |
| 21:22.37 | ahigerd | I'll... have to try it. I can kexec to 3.2 when I need to tether. |
| 21:22.47 | ahigerd | I'll give FRX a couple more days of logging and then switch |
| 21:22.50 | jonpry | yeah that was the other test |
| 21:23.05 | jonpry | so no WCMDA under .27? |
| 21:23.08 | ahigerd | But I could have sworn I was running .27 when I first saw the problem |
| 21:23.11 | ahigerd | But maybe I'm wrong |
| 21:28.00 | jonpry | i figure there are only 2 possibilities. 1 this wcdma thing isn't really in the smd channel and there is some kind of corruption. 2 old bug reports are not reliable anymore since either the patch or insufficient logging |
| 21:31.26 | ahigerd | So test, test, test |
| 21:32.17 | *** join/#htc-linux DuperMan (~Duper@109-186-34-60.bb.netvision.net.il) |
| 21:33.19 | jonpry | corruption of the channel might be a better point of attack since its really the only hope of resolving the problem |
| 21:33.52 | ahigerd | Yeah... |
| 21:34.13 | jonpry | not sure how to go about it though |
| 21:34.39 | jonpry | i can print stuff to dmesg but logging that is difficult |
| 21:49.28 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
| 21:51.22 | *** join/#htc-linux jonpry (~jon@adsl-98-85-196-230.mco.bellsouth.net) |
| 21:52.31 | jonpry | maybe have a script that waits for WCDMA in logcat and then dumps the good stuff from /dev/mem? |
| 21:52.34 | jonpry | er not sure if that is possible. maybe /dev/mem only works with mmap |
| 21:54.31 | ahigerd | Couldn't you watch /proc/kmsg? |
| 21:54.39 | ahigerd | Or heck, just open another /proc node |
| 22:00.04 | jonpry | the logging has to be triggered from the radio output because we don't know the message even exists on the smd channel |
| 22:00.46 | jonpry | then ideally we would save the entire shared memory segment |
| 22:05.50 | ahigerd | Well, still, a proc node would give you the ability to expose whatever information you want to expose if /dev/mem won't work |
| 22:07.50 | ahigerd | Well, quick research indicates /dev/mem doesn't need mmap, you can seek in it like a normal file if your privileges permit |
| 22:10.19 | ahigerd | Or you could use /dev/kmem if that's easier to find the offset you need |
| 22:20.14 | jonpry | phys=0x1F1C210 size=0x2014 |
| 22:21.13 | jonpry | scratch that. size = 0x4028 |
| 22:21.23 | ahigerd | Well, I don't know if you can do it from a shell script but it should be pretty straightforward to build a trivial little app |
| 22:22.38 | jonpry | could always try a dd if=/dev/mem bs=1 skip=32621072 count=16424 |
| 22:23.16 | ahigerd | That... would work. |
| 22:23.46 | jonpry | it might anyways. sometimes it throws permission denied |
| 22:24.44 | jonpry | or bus error. gotta love that one |
| 22:39.54 | *** join/#htc-linux ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 23:01.57 | detule | wth does make ARCH=arm msm_defconfig not update .config |
| 23:03.15 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
| 23:03.45 | ahigerd | o.o; |
| 23:04.30 | detule | i am curious if on .27 one sees the [WCDMA] wakeup messages |
| 23:04.36 | ahigerd | I'm seeing them in FRX |
| 23:05.40 | detule | hm i can't try .27 with my ext4 partitions |
| 23:06.11 | ahigerd | Yay for using a boring fat32 SD card ;) |
| 23:06.42 | ahigerd | Can you not build ext4 for .27? Or is it broken? |
| 23:08.40 | ahigerd | sighs and tries to get code written, but it's a hot Sunday afternoon after a long, tiring Saturday... so hard to focus on code |
| 23:09.19 | detule | i think ,27 has some backwards ext4 predecessor |
| 23:09.29 | detule | pretty sure it doesn't mount my partitions |
| 23:09.45 | detule | oh and it's not enabled in config |
| 23:09.49 | ahigerd | Oh right, I remember that now, I'm running .32 on one of my other machines |
| 23:09.58 | ahigerd | The disk format was still in development |
| 23:33.19 | detule | jonpry, you using this 3.3 goodness |