00:05.12 | *** join/#htc-linux rajkosto (~rajkosto@rajkosto.broker.freenet6.net) |
00:18.25 | jonpry2 | WisTilt2, i dunno if its this new timer thing i have. but now you can see when it unlocks. it goes to sleep. then 4 seconds later is wakes again. and then falls back sleep. which is the "waking up again in 4 seconds" deal |
00:19.31 | jonpry2 | wtf |
00:20.26 | WisTilt2 | i stuck my pm in along with a bunch of printk's in earlysuspend and pm. i still dont have it narrowed down but something is setting the enter_state to suspend mode when it shouldn't. |
00:21.37 | WisTilt2 | i didn't try this again but i also looked like the unlock/sleep didn't happen on the 1st time after boot but started afterwards. |
00:23.12 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-242-47.26-151.libero.it) |
00:24.59 | *** join/#htc-linux pablo_ (c8756d3e@gateway/web/freenode/ip.200.117.109.62) |
00:25.27 | pablo_ | hi, is there an htc phone working with linux? |
00:26.16 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
00:31.27 | WisTilt2 | jonpry, can you look at earlysuspend.c in void register_early_suspend and tell me how the heck line 59 can even work? state has no value (setup on line 45) so those tests aren't predictable at all until state contains something. |
00:33.41 | WisTilt2 | request_suspend_state needs state to be right, which i can't see how it ever is |
00:35.39 | jonpry | it starts at zero right |
00:36.04 | jonpry | line 82 it gets REQUESTED flag |
00:36.25 | jonpry | er SUSPENDED |
00:36.35 | WisTilt2 | doesnt register happen before all of that? |
00:37.02 | jonpry | line 122 it gets !SUSPENDED |
00:37.30 | jonpry | line 164 gets REQUESTED |
00:38.08 | jonpry | should be zero while most registration is happening |
00:38.36 | jonpry | there is small chance that early suspends are being registers while pm ops are happening |
00:39.31 | WisTilt2 | in my logs during all this i keep seeing the request_suspend_state with the new_state value saying suspend where it should not be. sometimes its trying to set to suspend requested and suspend at same time. very confusing |
00:40.21 | WisTilt2 | you could be right, seems like a couple things are happening at same time that shouldn't be |
00:44.14 | *** join/#htc-linux RussellAlan (~R.Alan@ppp-70-249-144-71.dsl.rcsntx.swbell.net) |
00:44.32 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
00:46.38 | jonpry | confusing indeed |
00:48.07 | jonpry | i changed a few things with timers, but no effect |
00:50.34 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
00:54.41 | jonpry | we don't seem to have const char * const AUTO_OFF_TIMEOUT_DEV = "/sys/android_power/auto_off_timeout"; |
00:55.21 | jonpry | does 27 actually have that? |
01:04.34 | *** join/#htc-linux ORi| (~ORi@91.181.155.40) |
01:05.12 | WisTilt2 | jonpry, no it is not in .27 either |
01:06.06 | jonpry | its almost as if all this stuff is working fine |
01:06.16 | WisTilt2 | interesting, if you swipe the sound on/off on unlock screen it doesnt sleep, only unlock itself |
01:14.39 | WisTilt2 | back shortly, pizza is here |
01:19.49 | jonpry | so if i do: echo foo > /sys/power/wake_lock |
01:19.50 | jonpry | then grep foo /proc/wakelocks |
01:19.51 | jonpry | shows me that is exists |
01:19.57 | jonpry | along with some numbers i don't get |
01:21.02 | jonpry | but if i then do echo mem > /sys/power/state |
01:21.02 | jonpry | i see it turning off display like its no big deal. nothing in dmesg about wakelock interference |
01:21.11 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
01:35.34 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
01:44.41 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
01:56.44 | *** join/#htc-linux NeoMatrixJR (~chatzilla@173-20-63-176.client.mchsi.com) |
01:56.49 | jonpry | WisTilt2, i think i found something. your going to hate me |
01:58.56 | *** join/#htc-linux nrirclog (~nrirclog@netripper.com) |
02:01.30 | WisTilt2 | jonpry, full of pizza and beer now so i have no hate left in me:) what'd you find. |
02:05.05 | WisTilt2 | i don't know how you haven't gone postal with that connection |
02:05.22 | WisTilt2 | arrrghhh you still at kbd? |
02:05.24 | AstainHellbring | seriously thats a terrible one |
02:07.53 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
02:14.00 | jonpry2 | hey |
02:14.00 | jonpry2 | compare /proc/wakelocks on 27 and 39 |
02:14.28 | AstainHellbring | damn jonpry2 your internets sucks |
02:15.12 | WisTilt2 | so which one are we missing? |
02:17.27 | jonpry | like all of them. brb |
02:24.49 | WisTilt2 | just confirmed, unlock works without sleep 1st time from booting then fails every time after so that wakelock is not being seen |
02:32.47 | arrrghhh | WisTilt2, i'm back now, what's up? |
02:34.00 | WisTilt2 | hey, i completely re-setup the xdandroid repo, got all the 2.2.2 tree but it's still frx05? |
02:34.13 | arrrghhh | i think that's the manifest file or whatever |
02:34.46 | arrrghhh | hrm |
02:34.55 | arrrghhh | at least i thought it was, perhaps not. |
02:35.03 | WisTilt2 | i did the init like this-> repo init -u git://gitorious.org/xdandroid/manifest.git -b froyo -m xdandroid-2.2.2-manifest.xml, then repo sync |
02:35.11 | arrrghhh | i thought it was that buildspec.mk file |
02:35.25 | arrrghhh | but looking at the file, i don't think that is it.... |
02:35.28 | WisTilt2 | so its just the label wrong? |
02:35.33 | arrrghhh | well there's one surefire way to confirm |
02:35.51 | arrrghhh | does the in-call screen have fancy buttons, or is it mostly blank? |
02:36.38 | WisTilt2 | didnt try that and can't test it right now but that's a good point. frx06 got the new fancy in-call screen didn't it |
02:36.59 | arrrghhh | yep |
02:37.07 | arrrghhh | that was one of the few changes between 05->06 |
02:37.12 | arrrghhh | not a lot changed TBH |
02:37.34 | WisTilt2 | actually, brain fart here... i forgot i cant even build it because it doesn't like java 1.6 |
02:37.48 | WisTilt2 | i just see in the start of build it says frx05 |
02:37.56 | arrrghhh | hrm |
02:38.35 | WisTilt2 | PLATFORM_VERSION_CODENAME=REL |
02:38.35 | WisTilt2 | PLATFORM_VERSION=2.2.2 |
02:38.35 | WisTilt2 | TARGET_PRODUCT=generic |
02:38.35 | WisTilt2 | TARGET_BUILD_VARIANT=eng |
02:38.35 | WisTilt2 | TARGET_SIMULATOR= |
02:38.35 | WisTilt2 | TARGET_BUILD_TYPE=release |
02:38.37 | WisTilt2 | TARGET_BUILD_APPS= |
02:38.39 | WisTilt2 | TARGET_ARCH=arm |
02:38.41 | arrrghhh | i think that's defined in the build.prop |
02:38.41 | WisTilt2 | HOST_ARCH=x86 |
02:38.43 | WisTilt2 | HOST_OS=linux |
02:38.47 | WisTilt2 | HOST_BUILD_TYPE=release |
02:38.49 | WisTilt2 | BUILD_ID=FRX05 |
02:38.51 | arrrghhh | but at buildtime, i'm not sure what specifies it. |
02:38.53 | WisTilt2 | thats straight off the repo |
02:39.32 | WisTilt2 | k, im not going to worry about it. i have the actual frx06 system.ext2 im running now. i guess i've been running 2.2.1 forever and didn't realize it |
02:40.58 | WisTilt2 | we've been working on this crazy unlock screen issue and i've been looking at whats causing the high battery drain. |
02:41.08 | arrrghhh | nice |
02:41.45 | WisTilt2 | .39 is so much faster so will be nice when we get some of the critical crap fixed. |
02:41.50 | arrrghhh | indeed |
02:41.54 | arrrghhh | with those two things |
02:42.02 | arrrghhh | & installs |
02:42.43 | arrrghhh | .39 should be in at least a pretty good state |
02:43.27 | WisTilt2 | sounds like jonpry may have found the wakelock problem, so maybe we can figure out the install problem afterwards. maybe we'll get lucky and they're related, which is possible. |
02:43.41 | arrrghhh | sweet |
02:43.56 | arrrghhh | .39 felt like .27 on nilfs |
02:44.07 | arrrghhh | i guess i should try .39 on nilfs |
02:44.15 | arrrghhh | my phone will rip a hole in the space-time continuum |
02:45.11 | WisTilt2 | something else you might know... would 3G mode draw less than HSPA modes? it seems since at&t enabled their HSPA around here that my normal scbs 4/15 kernel is drawing almost .5% per hour more now. |
02:45.29 | arrrghhh | wouldn't surprise me |
02:45.41 | arrrghhh | at idle i wouldn't think so, but certainly in-use it would. |
02:46.37 | WisTilt2 | im talking in sleep only. i haven't changed anything else and signal here is the same so its not like radio has to xmt at any higher power than before. |
02:47.34 | arrrghhh | yea |
02:47.36 | arrrghhh | hrm... that's odd. |
03:07.28 | jonpry | found is such a strong word |
03:10.18 | jonpry | WisTilt2, i added evdev wakelock which seemed important. but no go |
03:12.03 | WisTilt2 | damn. |
03:12.49 | jonpry | arrrghhh, can you do a .27 experiment? |
03:12.55 | arrrghhh | sure what's up? |
03:13.09 | WisTilt2 | im going to trace the logic on this 1st unlock screen after booting then see what changes after that point. weird it works 1st try, which makes me think a wakelock value is changing |
03:13.38 | jonpry | get usb terminal open, and your phone in an unlocked state. then: echo foo > /sys/power/wake_lock; echo mem > /sys/power/state |
03:14.54 | jonpry | and see if it does anything |
03:14.54 | jonpry | the missing code is basically stuff to buy a fraction of second |
03:14.57 | jonpry | what i'm seeing is strange correlation with the pm functions and the panel blank or unblank |
03:15.14 | jonpry | like how does it kill panel? |
03:16.08 | arrrghhh | jonpry, just goes to the next line... |
03:16.18 | jonpry | does the screen turn off? |
03:17.11 | arrrghhh | yes |
03:17.38 | jonpry | and echo on > /sys/power/state |
03:17.46 | jonpry | turns it back on? |
03:18.28 | arrrghhh | yes |
03:19.05 | jonpry | can you paste the contents of /proc/wakelocks? |
03:19.25 | *** join/#htc-linux Rob2223 (~Miranda@p4FFF1DCD.dip.t-dialin.net) |
03:20.00 | arrrghhh | http://pastebin.com/aWn7F4yr |
03:21.15 | *** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc) |
03:26.19 | jonpry | thanks arrrghhh |
03:26.24 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
03:30.46 | arrrghhh | np |
03:35.06 | jonpry | WisTilt2, i have seen it work a few times now. so random timing related process |
03:36.07 | jonpry | and like i said it happens when plugged into usb. so its not wakelocks. its actually the setting of /sys/power/state that turns off the display. and that is indeed set to mem after unlock |
03:39.16 | WisTilt2 | could it be a clock that's different? i dont understand how it works everytime on the 1st attempt at boot then immediately stops working. mine stays consistent at around 1.2secs from then on. |
03:39.55 | jonpry | after boot phone is probably slow |
03:42.21 | jonpry | does libhardware need to implement the other kinds of wakelocks? |
03:43.07 | WisTilt2 | dont know |
03:43.31 | WisTilt2 | i may have found something, going to test before i get too excited |
03:53.07 | *** join/#htc-linux nautis_ (~nautis@76-218-70-41.lightspeed.sntcca.sbcglobal.net) |
03:54.46 | jonpry | I really think that libhardware is relying on a timing bug that used to be more certain |
03:57.33 | jonpry | the libhardware kind of sucks really. doesn't support most wakelocks and doesn't use activity timeout |
04:06.23 | jonpry | arrrghhh, does .27 have /sys/android_power ? |
04:06.40 | arrrghhh | let me see |
04:07.20 | arrrghhh | jonpry, no |
04:09.48 | WisTilt2 | ok, we have absolutely no evdev wakelocks at all and that's where the unlock event comes from. evdev.c is far different than .27 i see |
04:10.19 | jonpry | i have that fixed now. want me to push? |
04:10.42 | WisTilt2 | jonpry, what i did was took my 2.2.1 xdandroid and changed that value back to 5000 like it was, now unlock screws up, with it set at 100 it works 100%. |
04:10.59 | WisTilt2 | yes please so i can look at that evdev code |
04:11.49 | jonpry | its being a little funky. like the only way i can get it to not crash on suspend is to let it settle with usb plugged first |
04:13.21 | jonpry | WisTilt2, so at 100 it will work on 2.2.2? |
04:13.32 | jonpry | pushed |
04:13.37 | WisTilt2 | i cant build 2.2.2 due to my java 1.6 |
04:13.55 | jonpry | umm, you can't get java 1.5? |
04:14.00 | WisTilt2 | if you can try it that would be great. 5000 is the default, doesnt work right, 100 works perfect |
04:14.20 | WisTilt2 | i dont want mess up my 1.6 |
04:14.48 | jonpry | in ubuntu there is some alternates system. i can switch 1.6/1.5 gcj etc with one command |
04:16.38 | WisTilt2 | did you only push evdev.c? |
04:17.08 | jonpry | no i pushed everything cause i have been hacking all around |
04:17.19 | arrrghhh | yea that's what i had to do WisTilt2 |
04:17.23 | arrrghhh | force java version |
04:17.38 | jonpry | or edit build/core/main.mk and comment out 104-134 |
04:17.43 | WisTilt2 | how do i do that |
04:17.51 | WisTilt2 | force java version sounds good |
04:17.59 | arrrghhh | WisTilt2, i only know how to do it on ubuntu, there's probably a way on fedora tho. |
04:19.43 | *** join/#htc-linux XirXes (~xirxes@71-35-197-137.slkc.qwest.net) |
04:20.11 | WisTilt2 | jonpry what did you change in pm.c? its not letting me see the commit changes on the site, says too large to display |
04:20.37 | jonpry | when did you last pull? |
04:20.55 | WisTilt2 | just now |
04:21.10 | jonpry | i mean change between when and when |
04:21.52 | WisTilt2 | in the commit you just pushed was something in pm.c changed or was that earlier? |
04:22.48 | jonpry | earlier i think |
04:23.15 | jonpry | its just warning fixed |
04:23.49 | jonpry | should patch cleanly against whatever you have |
04:24.25 | jonpry | and just pull. when it gives you crap about the binaries not patching just ignore it. it will make some stupid files in your directory |
04:24.54 | jonpry | if it won't build then you know something important didn't merge |
04:26.27 | jonpry | --------------------------- arch/arm/mach-msm/pm.c ---------------------------- |
04:26.29 | jonpry | index 95b9daa..4a86c87 100644 |
04:26.29 | jonpry | @@ -140,7 +140,7 @@ static void msm_pm_add_stat(enum msm_pm_time_stats_id id, int64_t t) |
04:26.30 | jonpry | <PROTECTED> |
04:26.30 | jonpry | <PROTECTED> |
04:26.30 | jonpry | <PROTECTED> |
04:26.32 | jonpry | -void msm_pm_flush_console() |
04:26.32 | jonpry | +void msm_pm_flush_console(void) |
04:26.34 | jonpry | <PROTECTED> |
04:26.36 | jonpry | <PROTECTED> |
04:26.38 | jonpry | <PROTECTED> |
04:26.40 | jonpry | @@ -375,7 +375,7 @@ void arch_idle(void) |
04:26.42 | jonpry | <PROTECTED> |
04:26.44 | jonpry | <PROTECTED> |
04:26.48 | jonpry | <PROTECTED> |
04:26.50 | jonpry | -unsigned long saved_rate; |
04:26.52 | jonpry | +//unsigned long saved_rate; |
04:26.54 | jonpry | <PROTECTED> |
04:26.56 | jonpry | <PROTECTED> |
04:26.58 | jonpry | <PROTECTED> |
04:27.00 | jonpry | @@ -469,7 +469,7 @@ static struct platform_suspend_ops msm_pm_ops = { |
04:27.02 | jonpry | <PROTECTED> |
04:27.04 | jonpry | <PROTECTED> |
04:27.06 | jonpry | <PROTECTED> |
04:27.08 | jonpry | -static void msm_pm_restart(char str) |
04:27.10 | jonpry | +static void msm_pm_restart(char str, const char *cmd) |
04:27.12 | jonpry | <PROTECTED> |
04:27.14 | jonpry | <PROTECTED> |
04:27.18 | jonpry | <PROTECTED> |
04:27.20 | jonpry | @@ -492,13 +492,14 @@ static void msm_pm_restart(char str) |
04:27.22 | jonpry | <PROTECTED> |
04:27.24 | jonpry | <PROTECTED> |
04:27.26 | jonpry | <PROTECTED> |
04:27.28 | jonpry | +unsigned num; |
04:27.30 | jonpry | + |
04:27.32 | jonpry | <PROTECTED> |
04:27.34 | jonpry | <PROTECTED> |
04:27.36 | jonpry | <PROTECTED> |
04:27.41 | jonpry | <PROTECTED> |
04:28.07 | jonpry | <PROTECTED> |
04:28.07 | jonpry | <PROTECTED> |
04:28.07 | jonpry | -unsigned num; |
04:28.07 | jonpry | <PROTECTED> |
04:28.08 | jonpry | <PROTECTED> |
04:28.08 | jonpry | <PROTECTED> |
04:28.09 | jonpry | @@ -655,8 +656,9 @@ __initcall(msm_pm_init); |
04:28.09 | jonpry | <PROTECTED> |
04:28.10 | jonpry | <PROTECTED> |
04:28.10 | jonpry | <PROTECTED> |
04:28.11 | jonpry | -printk("Sending arm9_low_speed 2\n"); |
04:28.11 | jonpry | <PROTECTED> |
04:28.12 | jonpry | + |
04:28.12 | jonpry | +printk("Sending arm9_low_speed 2\n"); |
04:28.13 | jonpry | <PROTECTED> |
04:28.13 | jonpry | <PROTECTED> |
04:28.26 | jonpry | -printk("Sending arm9_low_speed 7\n"); |
04:28.28 | jonpry | <PROTECTED> |
04:28.30 | jonpry | + |
04:28.33 | jonpry | +printk("Sending arm9_low_speed 7\n"); |
04:28.34 | jonpry | <PROTECTED> |
04:28.36 | jonpry | <PROTECTED> |
04:28.39 | jonpry | <PROTECTED> |
04:28.40 | jonpry | oops |
04:28.45 | WisTilt2 | lol, was that headed for pastebin and you hit wrong window? |
04:28.48 | jonpry | i was trying to paste the pastebin address :p |
04:28.48 | jonpry | http://pastebin.com/D7DMftXg |
04:28.54 | jonpry | oh and then there is fiq handler |
04:29.04 | jonpry | it was already in pastebin. but the copy of the address didn't happen |
04:29.16 | arrrghhh | lol |
04:29.38 | jonpry2 | well ya know |
04:30.26 | WisTilt2 | do you know where the client list comes from in evdev_event? |
04:30.51 | jonpry | dude. 3.0 rc1 :p |
04:31.06 | jonpry | we're only one patchset away |
04:31.29 | jonpry | i dunno what that is |
04:32.04 | WisTilt2 | finals around the corner? |
04:32.12 | jonpry | kernel.org |
04:32.30 | jonpry | we can have first phone with linux 3.0 |
04:32.54 | jonpry | i can rebase it in like an hour :p |
04:33.14 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39) |
04:33.55 | arrrghhh | i heard linus was looking to not do a .40 |
04:34.37 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
04:34.38 | arrrghhh | and skipping right to 3.0 |
04:34.48 | jonpry | i thought it would be 2.8 though. they always said majors were for ABI change |
04:35.02 | WisTilt2 | jonpry, found a rather important wakelock that's missing in the event passing |
04:35.29 | jonpry | i'm a little confused about what the closest ancestor to 3.0 will be. will it be 2.6.39.2 or 2.6.39 ? |
04:35.46 | WisTilt2 | we need to add wake_lock_timeout(&client->wake_lock, HZ/10); right after the spinlock at line 59 |
04:36.51 | jonpry | in evdev? |
04:37.13 | WisTilt2 | yes |
04:38.03 | jonpry | thats already in there |
04:38.35 | jonpry | along with everything else that makes it work |
04:38.59 | jonpry | and wakelocks are not really interesting at this point because you can make as many as you want and it will still happen |
04:39.33 | WisTilt2 | i dont see that in this source, where are you looking? |
04:40.10 | jonpry | wakelocks themselves may be broken. but adding more here or there is not the crux of it |
04:41.25 | jonpry | you pulled? |
04:41.43 | WisTilt2 | yes, have current tree since you just pushed |
04:42.45 | jonpry | 61:62: spin_lock(&client->buffer_lock); |
04:42.46 | jonpry | wake_lock_timeout(&client->wake_lock, HZ/10); |
04:42.54 | jonpry | drivers/input/evdev.c |
04:42.58 | WisTilt2 | omg, yeah i have the tree but im looking at my previous evdev for god sakes |
04:43.03 | WisTilt2 | i need to go to bed |
04:44.02 | WisTilt2 | i had it in the editor but didn't reload after i pulled:) |
04:44.03 | jonpry | i just finished my new system.img |
04:44.10 | jonpry | that will do it |
04:44.54 | WisTilt2 | did you build it with that value changed to 100 for kicks? |
04:45.07 | jonpry | yep |
04:45.59 | jonpry | i enabled all the logging from libhardware_legacy/power so we can see exactly what android is offering when |
04:46.36 | WisTilt2 | good idea |
04:53.20 | jonpry | ok so android only ever tries to: acquire_wake_lock lock=1 id='rpc-interface' |
04:53.52 | jonpry | which doesn't necessarily seem correct to me, but like i said partial_wake_locks are not the problem |
04:54.32 | jonpry | other than that it literally calls set_screen_state 0 right after the unlock button gets to the end |
04:54.46 | jonpry | and 100 did not help me |
04:56.46 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-72-247.dynamic.mnet-online.de) |
05:02.25 | WisTilt2 | so what changed from 2.2.1 to 2.2.2 in this area. if you want to download my system.img where this value of 100 works, ill stick it on our ftp server. maybe you can use it to see something? |
05:04.26 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
05:06.36 | WisTilt2 | arrrghhh you still awake? you want to try this system.img and see if unlock works right on your 400 with the .39 kernel? |
05:09.51 | arrrghhh | sure |
05:09.59 | arrrghhh | just upgrading some voicemail servers @ work :P |
05:10.40 | WisTilt2 | you're doing work for work on a 3 day weekend? |
05:10.48 | arrrghhh | best time to do it |
05:10.54 | WisTilt2 | yeah true |
05:10.55 | arrrghhh | if something blows up, i've got all day tomorrow to fix it |
05:12.51 | WisTilt2 | ok zipping it up then ill upload it. filename will be system.zip and ill put up the current zImage also so you can try it with all the other fixes. |
05:13.29 | arrrghhh | k |
05:14.30 | arrrghhh | great, got 2 bad DIMMs. hopefully this thing'll limp along until Cisco ships me a new box... oy. |
05:16.48 | jonpry | i'm trying to figure out how this whole unlock process works. seems the actual screen calls some kind of callback that i can't find who implements it |
05:19.42 | WisTilt2 | jonpry, figuring that out requires lots of engineering fluid. |
05:19.49 | arrrghhh | heh |
05:19.56 | arrrghhh | i'm all out of single-malt scotch tho! |
05:21.03 | jonpry | i have some high test |
05:22.02 | WisTilt2 | yeah i like GlenLivet 21 myself |
05:22.57 | WisTilt2 | had some of their 40yr stuff once and couldn't tell the difference to justify the extra outrageous cost |
05:24.49 | WisTilt2 | arrrghhh btw, system.zip is up along with zImage with your usual filename. |
05:25.06 | arrrghhh | cool |
05:25.33 | WisTilt2 | if this combo doesn't fix the unlock/sleep deal on your phone im going to commit myself somewhere |
05:25.44 | arrrghhh | lol |
05:26.07 | WisTilt2 | i just want to make sure im not totally crazy in what im seeing here |
05:26.51 | jonpry | i'm pretty sure this is happening, but don't know why: WindowManagerPolicy#OFF_BECAUSE_OF_TIMEOUT |
05:27.53 | WisTilt2 | that is when the error happens in early suspend waiting for user to stop drawing i believe |
05:31.10 | arrrghhh | alrighty |
05:31.12 | arrrghhh | bootin |
05:33.00 | WisTilt2 | check the build number and also see if the new in-call screen is there. i almost think when i was running it last night it was there but it didnt say frx06 in build. |
05:33.56 | arrrghhh | heh |
05:33.57 | arrrghhh | ok |
05:34.17 | jonpry | ah thats the default state |
05:35.00 | jonpry | so basically if anything turns the blasted thing off, it will cause rtc alarm etc |
05:37.21 | jonpry | can you attach android debugger to the frameworks? |
05:38.11 | WisTilt2 | that's a stinebd question:) i have no idea |
05:38.35 | arrrghhh | hrm |
05:38.37 | arrrghhh | seems hung |
05:38.59 | WisTilt2 | you let it make new data.img? |
05:39.08 | arrrghhh | yea |
05:39.11 | arrrghhh | and it appeared to |
05:39.31 | jonpry | sometimes it takes long time |
05:39.40 | jonpry | you can test for death with usb |
05:39.45 | arrrghhh | blinkin cursor didn't blink |
05:40.21 | arrrghhh | yea it did create a data.img. gonna try booting again. |
05:42.38 | arrrghhh | appears to be booting OK |
05:46.26 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39) |
05:47.21 | arrrghhh | WisTilt2, old in-call screen... :/ |
05:47.48 | WisTilt2 | ok so it is 2.2.1 |
05:48.56 | arrrghhh | waiting to test the sleep issue |
05:50.45 | arrrghhh | durn thing won't sleep |
05:50.48 | arrrghhh | i'm on the old RIL tho |
05:51.29 | WisTilt2 | hmm, thats the only thing i haven't tried with this. im still on hyc's via bind mount |
05:51.41 | arrrghhh | yea i should've left it in there. |
05:53.36 | WisTilt2 | arrrghhh, scrap the test and let me put up the exact files i have running on both my phones. i have so many test versions i may have given you the wrong combo |
05:54.02 | WisTilt2 | im going to copy them off my phone so i know they're the right ones since it working on both phones here. |
05:55.31 | arrrghhh | heh |
05:55.32 | arrrghhh | ok |
05:55.53 | arrrghhh | hey lookie thar. the server disabled the bad DIMMs this time around, and the CPU isn't spiking like mad. |
05:56.07 | arrrghhh | eh i'll still let them send me a whole new rig. |
05:57.00 | WisTilt2 | this is a cisco server with bad dimms? |
05:57.41 | arrrghhh | yea kinda |
05:57.48 | arrrghhh | it's an 'appliance' |
05:57.54 | arrrghhh | but it's IBM hardware in reality |
05:58.04 | arrrghhh | cisco-branded IBM hardware. |
05:58.14 | WisTilt2 | ios or linux? |
05:58.30 | arrrghhh | linux |
05:58.34 | arrrghhh | Unity Connection |
05:59.49 | arrrghhh | cisco gave us two choices for hardware vendors, IBM or HP. from what i've seen, i wish we would've gone with HP |
05:59.55 | jonpry2 | i think this debugging system_process with adb will eventually work |
05:59.57 | arrrghhh | although they lost their partnership, some internal BS |
06:08.42 | jonpry | will take a few days to build though damn |
06:10.07 | jonpry | later fellas. adb remote debugging of frameworks == badass. whoever can do this holds the keys. http://source.android.com/source/using-eclipse.html |
06:10.20 | arrrghhh | nice |
06:10.27 | arrrghhh | cya dude |
06:10.44 | WisTilt2 | nit jonpry |
06:10.59 | WisTilt2 | ok arrrghhh new system.zip and zImage |
06:11.04 | arrrghhh | k |
06:11.07 | WisTilt2 | this has to work on your phone! |
06:11.15 | arrrghhh | lol |
06:11.19 | arrrghhh | yes sir... |
06:11.21 | arrrghhh | :P |
06:11.56 | WisTilt2 | psychiatric ward is not too far from where I live if not:) |
06:12.30 | arrrghhh | hahaha |
06:19.14 | arrrghhh | k. new data.img, booting |
06:22.15 | arrrghhh | hrm. kernel panic & freeze. i think this is same as the last time, lemme reboot. |
06:23.57 | WisTilt2 | ive had than after new data.img with .39 a couple times. dont know what causes it but all future boots work fine so far. |
06:24.48 | arrrghhh | that's what happened last time |
06:24.53 | arrrghhh | i have a data.img, booting. |
06:25.50 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
06:28.10 | *** join/#htc-linux MacDrunk (~marper@201.165.142.166) |
06:28.58 | *** join/#htc-linux hardwalker (~hardwalke@122-117-115-146.HINET-IP.hinet.net) |
06:32.20 | *** join/#htc-linux MacMiller (~marper@201.165.142.166) |
06:36.00 | *** join/#htc-linux MacDrunk (~marper@201.165.126.230) |
06:38.50 | WisTilt2 | arrrghhh smoke pouring out of your phone? |
06:39.10 | arrrghhh | lol not yet |
06:39.13 | arrrghhh | but i had another failed boot |
06:39.20 | arrrghhh | so i'm putting the newest RIL In |
06:39.24 | arrrghhh | bootin now |
06:40.05 | WisTilt2 | ok. i still haven't tried that but i've rebooted several times and working perfect, calls and all sound. about to try app install again for kicks |
06:40.23 | arrrghhh | hrm |
06:40.27 | arrrghhh | still failed to boot... |
06:41.11 | arrrghhh | anything special i need in rootfs? |
06:41.16 | *** join/#htc-linux dekar_ (~dekar@drms-590ced65.pool.mediaWays.net) |
06:41.23 | arrrghhh | i just have F22's rootfs "for" hyc's RIL |
06:41.28 | arrrghhh | ril2 |
06:42.17 | WisTilt2 | i have F22's earlier rootfs from months ago and running hyc's 4/14 ril |
06:45.21 | WisTilt2 | F22's 02/12/11 rootfs actually |
06:46.55 | arrrghhh | hrmmmm |
06:46.58 | arrrghhh | still failing to boot |
06:47.07 | WisTilt2 | how far does it get? |
06:48.53 | arrrghhh | 9e1032b2fc8f9c15813cc865f8985433 for the kernel |
06:48.55 | arrrghhh | 1 sec |
06:50.33 | arrrghhh | i see the touch calib stuff |
06:50.39 | arrrghhh | then it starts spitting out stuff too fast |
06:50.42 | arrrghhh | lots of 'end trace' |
06:50.53 | arrrghhh | eventually it hangs after a kernel panic |
06:50.53 | WisTilt2 | kernel sum is good |
06:51.58 | *** join/#htc-linux stroughtonsmith (~steven@86-43-216-108-dynamic.b-ras2.bbh.dublin.eircom.net) |
06:51.59 | WisTilt2 | system sum a9bfe19ed2cebd53b42525c74f891d79 |
06:52.43 | WisTilt2 | i can upload the rootfs if you want to try it |
06:54.13 | arrrghhh | i doubt that's the issue... |
06:54.16 | arrrghhh | m |
06:54.48 | WisTilt2 | you have the initrd offset still? |
06:55.20 | arrrghhh | set initrd_offset 0x00a00000 |
06:55.25 | arrrghhh | and the different haret |
06:55.29 | WisTilt2 | yep |
06:55.29 | arrrghhh | wait system.ext2 doesn't match |
06:55.33 | arrrghhh | was that the zip's md5? |
06:56.53 | arrrghhh | system.zip from the usual place right? |
06:57.14 | arrrghhh | neither of the md5's match for the system. the .ext2 or the .zip |
06:57.22 | WisTilt2 | beab12ff8dd918224376dcbc5ce00500 |
06:57.34 | arrrghhh | that matches the .zip |
06:58.21 | arrrghhh | where'd that system sum come from tho? |
06:58.54 | WisTilt2 | that last one was the zip |
06:59.04 | WisTilt2 | previous ending in 1d79 was ext2 |
06:59.23 | arrrghhh | weird, the ext2 came out a different sum for me. |
06:59.40 | *** join/#htc-linux Stskeeps (~cvm@Maemo/community/distmaster/Stskeeps) |
06:59.58 | WisTilt2 | you have fast download, ill upload the system.ext2 |
07:00.13 | arrrghhh | 150e8faa3fbb7997c4a109e9a4ad0598 |
07:00.16 | arrrghhh | is what i have |
07:00.24 | arrrghhh | alright |
07:00.26 | WisTilt2 | for ext2? |
07:00.32 | arrrghhh | yea |
07:01.53 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-242-47.26-151.libero.it) |
07:02.42 | arrrghhh | gonna try once more |
07:03.05 | arrrghhh | cuz md5 didn't match the one on my phone |
07:04.02 | *** join/#htc-linux Rob2222 (~Miranda@p4FFF1DCD.dip.t-dialin.net) |
07:04.08 | WisTilt2 | i just copied off my phone and md5sum is deaf6674b56fbb04b25a69dd85c692b1. sum is diff than before so maybe messed up during copy. uploading it now... |
07:04.21 | arrrghhh | weird |
07:04.26 | WisTilt2 | yeah it is |
07:05.34 | WisTilt2 | ok system.ext2 ready |
07:05.47 | arrrghhh | k |
07:06.38 | WisTilt2 | just did sum across usb to phone and it also matched so you should be good with this one |
07:16.24 | arrrghhh | alright, 2nd boot here we go! |
07:16.35 | arrrghhh | md5 matches this time too :P |
07:17.06 | arrrghhh | hrm |
07:17.08 | arrrghhh | doesn't look good |
07:17.13 | arrrghhh | rebooting to recovery |
07:17.16 | arrrghhh | lots of untracked pids |
07:17.22 | arrrghhh | kernel panic, freeze.. wth |
07:17.26 | WisTilt2 | wth |
07:17.33 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-242-47.26-151.libero.it) |
07:18.07 | WisTilt2 | same kernel and system. ril and rootfs is only other diff |
07:19.06 | WisTilt2 | check md5sum on those files on the phone itself |
07:20.20 | *** join/#htc-linux Bry8Star|Unix (~Bry8Star|@gateway/tor-sasl/bry8star-) |
07:22.59 | arrrghhh | ok this is maddening |
07:23.10 | arrrghhh | md5 matched on my laptop, didn't match after copying it over. |
07:23.35 | WisTilt2 | sdcard flaking? |
07:23.45 | arrrghhh | i guess? |
07:23.51 | arrrghhh | haven't had any other issues. |
07:24.26 | WisTilt2 | murphy must be staying up late lol. |
07:24.47 | arrrghhh | heh |
07:25.06 | arrrghhh | ok now it matches on the phone... |
07:25.08 | arrrghhh | oy |
07:25.50 | WisTilt2 | maybe we'll get lucky this boot, hopefully data.img is ok still |
07:26.20 | arrrghhh | yea i'm hoping too... it'll save time |
07:27.11 | arrrghhh | crap. status quo... |
07:28.44 | WisTilt2 | maybe .39 is too fast for the card. dying in same place? |
07:30.32 | *** join/#htc-linux dobrin (~dobrin@85.91.150.26) |
07:32.31 | arrrghhh | yea every time it hits the calib section |
07:32.47 | arrrghhh | other .39 kernels worked tho |
07:33.40 | WisTilt2 | is calib file ok? |
07:35.12 | WisTilt2 | this kernel is actually jonpry's last build as pushed to his tree. i didnt even rebuild it but it runs on both my phones fine. |
07:35.31 | arrrghhh | hrm |
07:35.55 | WisTilt2 | is the calib for touchscreen or that wifi calib stuff its crashing on? |
07:36.47 | arrrghhh | ts |
07:39.16 | WisTilt2 | my calib file contains 812,861,191,861,495,516,814,174,190,179 if that means anything |
07:45.46 | *** join/#htc-linux ShapaTank (~ShapaTank@cpe-24-24-202-60.socal.res.rr.com) |
07:46.00 | arrrghhh | 839,892,187,892,513,535,842,183,184,175 |
07:46.18 | arrrghhh | hrm. md5 doesn't match again. i thought it was mounting /system RO? |
07:47.51 | arrrghhh | i think it's bedtime for me tho man... |
07:48.11 | WisTilt2 | yeah me too. you'll probably get it going with a fresh mind tomorrow |
07:48.27 | arrrghhh | yea |
07:48.38 | arrrghhh | probably missing something silly :P |
07:48.49 | WisTilt2 | ill catch you sometime tomorrow if you're on. thanks for the attempt |
07:48.52 | arrrghhh | i'll talk to you tomorrow... er later today ha. take it easy. |
07:48.55 | arrrghhh | np |
08:02.59 | *** join/#htc-linux Termana (~bradley@122.151.121.39) |
08:33.36 | *** join/#htc-linux surge (surge@pool-98-118-157-221.bflony.fios.verizon.net) |
08:35.53 | *** join/#htc-linux Rajko (~rajkosto@rajkosto.broker.freenet6.net) |
08:36.42 | *** join/#htc-linux kvaster (~kvaster@46.28.100.16) |
08:44.23 | *** join/#htc-linux gauner1986 (~Miranda@p5B3839D1.dip.t-dialin.net) |
08:48.30 | *** join/#htc-linux rajkosto (~rajkosto@rajkosto.broker.freenet6.net) |
09:17.20 | *** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star) |
09:25.40 | *** part/#htc-linux ftoz (~root@214-151.gtt-net.cz) |
09:32.56 | *** join/#htc-linux stroughtonsmith (~steven@86-44-100-172-dynamic.b-ras2.bbh.dublin.eircom.net) |
09:39.28 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39) |
09:44.28 | *** join/#htc-linux rajkosto (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs) |
10:54.06 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de) |
10:57.15 | *** join/#htc-linux kvaster (~kvaster@leased-line-93-125-0-84.telecom.by) |
11:23.01 | *** join/#htc-linux RussellAlan (~R.Alan@ppp-70-249-144-71.dsl.rcsntx.swbell.net) |
11:38.18 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-157-28.26-151.libero.it) |
11:42.15 | *** join/#htc-linux kvaster (~kvaster@leased-line-93-125-0-84.telecom.by) |
11:50.34 | *** join/#htc-linux skodde (~skodde@unaffiliated/skodde) |
12:13.48 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
12:26.33 | *** join/#htc-linux khorben_ (~dont@2002:53ec:d9a1:1:221:28ff:fe14:b106) |
13:01.40 | *** join/#htc-linux arif-ali (~arif-ali@88-111-134-148.dynamic.dsl.as9105.com) |
13:06.39 | *** join/#htc-linux leviathan (~quassel@2001:470:26:484:6ef0:49ff:fee6:8dca) |
13:10.13 | *** join/#htc-linux helicopter88 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
13:18.19 | *** join/#htc-linux helicopter88 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
13:26.42 | *** join/#htc-linux kholk (~kholk@unaffiliated/kholk) |
13:26.45 | kholk | hi guys |
13:27.28 | kholk | I'm here for asking some help on a little thing that the HTC Linux project has already done multiple times |
13:28.02 | kholk | anyone can explain me how to get the physical RAM address of a device? |
13:53.11 | *** join/#htc-linux gauner1986 (~Miranda@p5B3839D1.dip.t-dialin.net) |
13:57.34 | *** join/#htc-linux nikou1 (~bizhan@c-67-180-55-37.hsd1.ca.comcast.net) |
14:02.31 | *** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net) |
14:04.26 | *** join/#htc-linux NetRipper (~netripper@tikkie.net) |
14:07.34 | jonpry | kholk, what kind of device are you working on? |
14:07.57 | kholk | Motorola Atrix |
14:08.07 | kholk | Olympus board |
14:08.08 | kholk | Tegra2 |
14:08.42 | kholk | I'm close to boot a custom BL, I need the physical RAM start address though |
14:08.55 | jonpry2 | do you have source? |
14:08.56 | kholk | that would solve the locked bl problem and skip it |
14:08.59 | kholk | yep I have |
14:09.07 | kholk | and UART too. |
14:09.15 | kholk | I can see what the NvMicroBoot is saying at boot |
14:09.18 | jonpry2 | then in machine_start it will say where ramis |
14:09.26 | kholk | 'cause I've actually got an unlocked engineering device |
14:09.35 | kholk | uh, machine_start? |
14:09.38 | kholk | looking at it |
14:10.14 | kholk | but I remember I've already looked at something like that |
14:10.21 | kholk | and didn't find anything |
14:10.33 | kholk | maybe it was another thing, so, searching |
14:10.56 | jonpry2 | its in the board file |
14:10.57 | kholk | I can remember anyway that on my bootloader sourcecode I can find 0x00000000 as RAM start address |
14:11.01 | kholk | thing that is impossible |
14:11.08 | kholk | oh, so I've already looked at it |
14:12.06 | jonpry2 | like here is the relevant section of board-htcrhodium.c http://pastebin.com/QYPFQYDB |
14:12.31 | jonpry2 | in our case its the definition of PHYS_OFFSET |
14:12.32 | kholk | boot_params? |
14:12.41 | kholk | oh. |
14:13.01 | jonpry2 | iirc that is probably true for all machines on newer kernels |
14:13.55 | kholk | thing is, I've already looked for PHYS_OFFSET |
14:14.02 | kholk | and there seems there isn't any trace of that |
14:14.18 | jonpry2 | is your tree online? |
14:14.33 | kholk | not mine, but the Moto kernel source is on opensource.motorola.com |
14:14.45 | jonpry2 | i only do gitweb |
14:15.00 | kholk | there isn't any gitweb for it |
14:15.10 | kholk | but if you want I can upload it on my gitorius |
14:15.51 | kholk | the only reference on PHYS_OFFSET that I'm finding is |
14:15.56 | kholk | ./include/mach/memory.h:#define PHYS_OFFSET UL(0) |
14:15.57 | jonpry2 | i'm assuming the stuff in mach-tegra is the same as for your chip |
14:16.01 | kholk | (in mach-tegra) |
14:16.08 | jonpry2 | yeah thats what i got too |
14:16.12 | kholk | heh. |
14:16.15 | jonpry2 | so there you go :p |
14:16.44 | jonpry2 | and boot_params is 0x100 |
14:17.16 | kholk | so the ram start address is 0x0? |
14:17.23 | jonpry2 | yep |
14:17.27 | kholk | rofl |
14:17.32 | kholk | so I've had the solution under my nose |
14:17.41 | kholk | and I wasn't believing at it? |
14:17.42 | kholk | :P |
14:17.46 | kholk | oh, well. |
14:18.32 | kholk | so...thanks man :D |
14:18.39 | jonpry2 | no problem |
14:21.26 | *** join/#htc-linux rob_w (~bob@ppp-188-174-127-152.dynamic.mnet-online.de) |
14:30.34 | *** join/#htc-linux MACK1E (~MACK1E@50-88-143-107.res.bhn.net) |
15:02.32 | *** join/#htc-linux helicopter88 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
15:02.50 | *** join/#htc-linux _kiozen (~kiozen@ppp-93-104-72-247.dynamic.mnet-online.de) |
15:10.53 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
15:11.12 | *** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru) |
15:11.22 | Alex[sp3dev] | kholk: still there? |
15:12.50 | *** join/#htc-linux _twitch (~burning_a@64.112.96.58.static.exetel.com.au) |
15:17.35 | kholk | Alex[sp3dev], yep |
15:19.48 | Alex[sp3dev] | kholk: ok. i've tried kexecing my tegra. basically, had to build kexec module separately (removing some vminfo stores and external symbols). it hanged. when i applied some armv7 kexec patches on top, seems to reboot. have you managed to execute something yet? i have doubts whether current cache code for armv7 can work on smp for kexec.. looks like we may need to write a new loader like splboot for xperia |
15:20.36 | kholk | I already have a new loader. |
15:20.42 | Alex[sp3dev] | does it work? |
15:20.47 | kholk | it seems to :) |
15:21.08 | kholk | the only problem happens after the cpu_reset |
15:21.15 | Alex[sp3dev] | could you share the code? i'll test somewhere close to weekends.. dang. hate acer |
15:21.24 | kholk | I'll do |
15:21.55 | kholk | gotta buy cigs now |
15:21.55 | kholk | :P |
15:21.56 | kholk | 'later |
15:22.00 | Alex[sp3dev] | what happens after cpu_reset anyway? |
15:22.28 | kholk | oh well |
15:22.33 | kholk | "hang" and reboot |
15:22.43 | kholk | it's because I haven't compiled a proper boot image |
15:22.47 | kholk | with the needed boot parameters |
15:22.53 | kholk | but, well, it's coming soon |
15:23.00 | kholk | as I already know the boot parms |
15:23.07 | kholk | and I only have to do an mkbootimg... |
15:23.07 | kholk | :P |
15:23.26 | Alex[sp3dev] | oh well. i don't even have kernel sources.. so it's gotta be fun |
15:23.38 | kholk | opensource.motorola.com |
15:23.45 | Alex[sp3dev] | i have acer iconia a500 |
15:23.47 | kholk | ATT Atrix -> kernel.tgz |
15:23.59 | kholk | iconia? |
15:24.06 | Alex[sp3dev] | yep |
15:24.07 | kholk | oh, you're using my Atrix kexec for iconia? |
15:24.19 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-157-28.26-151.libero.it) |
15:24.22 | Alex[sp3dev] | no. i'm using my own. haven't found sources for yours |
15:24.27 | kholk | haha |
15:24.32 | kholk | okay anyway |
15:24.50 | kholk | it's better to hold on, I think |
15:24.58 | kholk | and well |
15:25.03 | kholk | crack your iconia bootloader |
15:25.07 | Alex[sp3dev] | haha |
15:25.08 | kholk | you'll need it.... :) |
15:25.11 | kholk | not kidding. |
15:25.17 | Alex[sp3dev] | i can't even get a dump of it. |
15:25.21 | kholk | oh, |
15:25.30 | kholk | so I have to build a custom bootloader for you, too.... :) |
15:26.03 | kholk | my new method needs an SPL |
15:26.06 | Alex[sp3dev] | what do you mean by that? can tegra bootloader be circumvented without kexec? |
15:26.18 | kholk | Tegra bootloader? |
15:26.21 | kholk | you mean... |
15:26.24 | kholk | Iconia bootloader. |
15:26.26 | kholk | :) |
15:26.46 | kholk | OEMs are using custom solutions, my friend.. |
15:26.53 | Alex[sp3dev] | i suppose tegra has some bootloader inside the cpu which provides nvflash and launches second stage loader from nand or mmc |
15:27.01 | kholk | oh, the BootROM |
15:27.06 | kholk | nVMicroBoot |
15:27.19 | kholk | the IPL |
15:27.26 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
15:27.52 | kholk | well, you really can't skip what the IPL is doing |
15:28.02 | kholk | I can give you some output from MicroBoot though |
15:28.10 | kholk | as I can...and you all can't |
15:28.23 | kholk | (not that I'm a genius, I only have an engineering device) |
15:28.24 | Alex[sp3dev] | well, i made dumps of mmc start and according to tegra partition table.. i have not found where EBT is stored and when muromec tried to decode the part table.. well, he found nothing as well |
15:28.36 | kholk | EBT? |
15:28.38 | kholk | hah |
15:28.44 | kholk | what do you want? |
15:28.45 | kholk | MicroBoot? |
15:28.56 | Alex[sp3dev] | nah. want to find out where acer loader is stored |
15:29.05 | kholk | I can inform you that MicroBoot is the same for all Tegra devices |
15:29.12 | kholk | my Atrix runs on an Advent Vega MicroBoot |
15:29.15 | Alex[sp3dev] | i think it may be stored encrypted. but that'd be epically stupid |
15:29.17 | kholk | and on a custom BL.. |
15:29.30 | kholk | if your bootloader can't be dumped |
15:29.32 | kholk | you're half fucked |
15:29.37 | kholk | look at Motorola Xoom |
15:29.38 | kholk | :) |
15:29.50 | Alex[sp3dev] | what? isn't xoom unlocked by default? |
15:30.27 | kholk | yeah. take a Xoom and try to dump the bootloader. |
15:30.30 | kholk | rofl |
15:31.15 | Alex[sp3dev] | i'm fully fucked. when i flash custom linux or recovery, it bails out with checksum error on boot |
15:31.31 | kholk | Xoom's BL can give a way to exploit the Atrix BL |
15:31.41 | kholk | heh. |
15:31.48 | kholk | at Moto they aren't stupid |
15:32.04 | kholk | and on Xoom you can't access NvFlash too, so you can't unlock the mask on the BL partition |
15:32.07 | kholk | and you can't dump it |
15:32.15 | kholk | and you're really fully, totally fucked |
15:32.28 | kholk | unless you find a method for unmasking your BL partition |
15:32.37 | kholk | thing that is half impossible because it isn't done on the Linux kernel |
15:32.54 | Alex[sp3dev] | so what? is it stored in mmc but is hidden (remapped) by the controller? |
15:33.02 | kholk | so, well, unless Acer gives a BL update |
15:33.05 | kholk | you won't ever have it |
15:33.07 | kholk | well |
15:33.16 | kholk | Tegra2 has got a well good protection system |
15:33.22 | Alex[sp3dev] | i've noticed that |
15:33.24 | kholk | as it is masking the SBK for example |
15:33.29 | kholk | with FF's |
15:33.38 | kholk | it is even masking your partitions |
15:33.53 | kholk | you can mask everything you want with Tegra BootROM |
15:34.14 | kholk | even the Android system partition. but then you won't be able to boot. |
15:34.15 | kholk | :P |
15:34.20 | Alex[sp3dev] | and as i can guess, you cannot reconfigure masking once bootrom handles contol over? |
15:34.22 | kholk | so basically, you're fucked |
15:34.28 | kholk | well, exact |
15:34.31 | kholk | if it was possible |
15:34.32 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
15:34.38 | kholk | I'd already have reconfigured the maskings |
15:34.42 | kholk | and retrieved the SBK |
15:34.44 | kholk | out of the Atrix |
15:34.45 | kholk | :) |
15:35.29 | kholk | you need to play with ODMData |
15:35.31 | kholk | and BCT |
15:35.43 | kholk | but, well, as you know, you can't |
15:36.13 | kholk | anyway, just out of curiosity |
15:36.19 | kholk | why Acer Iconia and not Moto Xoom? |
15:36.41 | kholk | (Iconia = Iconia TAB, right?) |
15:36.42 | Alex[sp3dev] | it was like $200 cheaper.. now i know why.. |
15:36.51 | kholk | oh, yep |
15:36.51 | kholk | :) |
15:37.02 | kholk | ACER is ever cheaper than others |
15:37.15 | kholk | I don't know why you're all buying tablets though |
15:37.29 | kholk | buying an x86 machine with a touchscreen would be a better choice I think |
15:37.36 | kholk | anyway, I'm happy with my Tegra2 phone :P |
15:37.52 | kholk | okay, now I'll go to buy cigs |
15:37.53 | kholk | brb, 5 mins |
15:37.54 | kholk | :P |
15:37.58 | Alex[sp3dev] | tbh i don't know why i bought it.. i now think it'd be better to buy asus transformer or toshiba ac100.. and yeah, i can't stand x86 except if it is a desktop. |
15:37.59 | Alex[sp3dev] | ok |
15:38.28 | AstainHellbring | loves his g tablet with access to nvflash and all :) |
15:38.46 | Alex[sp3dev] | f u troll, go away now |
15:38.52 | AstainHellbring | lol |
15:40.55 | AstainHellbring | ironically I havent even setup access to nvflash or learned to far how to do it |
15:40.57 | Alex[sp3dev] | the tablet ain't bad as is.. but android just sucks.. |
15:41.16 | arrrghhh | heh |
15:49.58 | kholk | so |
15:50.03 | *** part/#htc-linux Stskeeps (~cvm@Maemo/community/distmaster/Stskeeps) |
15:50.06 | kholk | why have you bought an android tablet |
15:50.10 | kholk | if you don't like android |
15:50.12 | kholk | ? |
15:50.38 | Alex[sp3dev] | i planned on using it as a development device for ubuntu/meego. |
15:51.07 | kholk | why are you buying a retail device from an OEM if you want to use it exclusively for development purposes? |
15:51.28 | *** join/#htc-linux dekar_ (~dekar@studpool-wlan-75-100.fs.fbi.h-da.de) |
15:51.47 | kholk | I've bought an Atrix because it's small and I can take it in my pocket |
15:52.01 | kholk | you could have bought a development board |
15:52.08 | kholk | with a Tegra2 CPU module |
15:52.10 | Alex[sp3dev] | good question. anyway another reason is that i wanted a very fast device for reading pdf when on train.. ebooks and e-ink suck, you know |
15:52.47 | kholk | well, same thing |
15:52.58 | kholk | you still need some bag for carrying your device with you |
15:53.06 | kholk | a small development board would have been a good choice |
15:53.21 | Alex[sp3dev] | yeah, ventana looks almost like a finished tablet |
15:53.29 | kholk | I'm not talking about Ventana |
15:53.34 | Alex[sp3dev] | i |
15:53.35 | Alex[sp3dev] | i |
15:53.39 | Alex[sp3dev] | damn fuck |
15:53.46 | kholk | I'm talking about development kits |
15:53.50 | kholk | open boards |
15:53.58 | Alex[sp3dev] | i'm not that geek to carry pandaboard, lcd and a car battery in my backpack |
15:54.07 | kholk | well you don't have to |
15:54.17 | kholk | the board is such small |
15:54.30 | kholk | as a battery you could use a battery for RC airplanes |
15:54.37 | kholk | pretty small batteries |
15:54.44 | kholk | with like 4000mAh of amperage |
15:54.51 | kholk | 3.7V though. |
15:54.55 | kholk | the exact voltage for your device |
15:55.12 | kholk | LCD, you would buy a 7" or 10" LCD for your device |
15:55.17 | kholk | or OLED display |
15:55.30 | kholk | so that wouldn't be so big |
15:55.34 | kholk | just a little bigger than a tablet |
15:55.35 | Alex[sp3dev] | i think you need to talk to jonpry about prypad ;) |
15:55.42 | kholk | prypad? lol |
15:56.18 | Alex[sp3dev] | rumours are the end of the world will happen when he finishes assembling it |
15:57.32 | kholk | lol |
16:03.17 | *** join/#htc-linux dobrin (~dobrin@85.91.150.26) |
16:14.14 | *** join/#htc-linux gauner1986 (~Miranda@46.115.16.88) |
16:15.04 | *** join/#htc-linux mastermerlin (~Adium@p4FEE5B60.dip.t-dialin.net) |
16:27.20 | *** join/#htc-linux helicopter88 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
16:30.50 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de) |
16:36.09 | Willd | L |
16:36.11 | *** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@94.52.236.39) |
16:39.05 | *** join/#htc-linux kysse (ville@2001:470:27:7ca::3) |
17:03.18 | *** join/#htc-linux tiger2wander (~tiger2wan@58.187.36.199) |
17:05.31 | *** join/#htc-linux Erikson (~Erik@i5E86D1F5.versanet.de) |
17:11.45 | *** join/#htc-linux helicopter88 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
17:24.50 | *** join/#htc-linux gummybear (~gummybear@188-220-145-112.zone11.bethere.co.uk) |
17:25.00 | *** join/#htc-linux gauner1986 (~Miranda@p5B3839D1.dip.t-dialin.net) |
17:32.11 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
17:33.55 | jonpry | Alex[sp3dev], the end of me already happened. prypad is no more. i've decided to work full time on htc-linux |
17:35.55 | Alex[sp3dev] | jonpry: when can we expect linux 3.0 on rhodium? rebased already? |
17:36.51 | arrrghhh | heh |
17:37.28 | rob_w | is there any htc curently running omap3 ? |
17:38.07 | Alex[sp3dev] | http://www.blogcdn.com/mobile.engadget.com/media/2009/08/omap-combo-breaker.jpg |
17:41.55 | kholk | go to OMAP4. |
17:42.13 | kholk | did you know that OMAP4 features volatile memory encryption? |
17:42.17 | kholk | (RAM encryption) |
17:42.19 | kholk | rofl |
17:42.45 | Alex[sp3dev] | the encryption is getting more anal |
17:43.55 | jonpry | Alex[sp3dev], i'm going to do it this week sometime. i need to to do heritage analysis |
17:44.11 | jonpry | i think it might be easier to go to 39.2 first |
17:44.20 | kholk | yeah. |
17:44.27 | kholk | when they'll give you a locked device |
17:44.30 | kholk | with RAM encryption |
17:44.32 | kholk | it'll get anal. |
17:44.33 | kholk | to you. |
17:44.34 | kholk | rofl |
17:45.01 | jonpry | didn't via c3 have something like that? |
17:48.32 | jonpry | and whats the diff anyways. none of us have ever tried to tap the memory bus. thats more of an xbox thing |
17:49.13 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
18:05.58 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-157-28.26-151.libero.it) |
18:13.33 | *** join/#htc-linux dekar_ (~dekar@drms-590ced65.pool.mediaWays.net) |
18:24.40 | *** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru) |
18:34.01 | *** join/#htc-linux mdj__ru (~mdj@46.182.128.248) |
18:34.46 | *** join/#htc-linux skodde (~skodde@unaffiliated/skodde) |
18:45.16 | *** join/#htc-linux kholk (~kholk@host129-159-dynamic.55-79-r.retail.telecomitalia.it) |
18:49.02 | *** join/#htc-linux n0psl3d (~n0psl3d@host86-180-160-182.range86-180.btcentralplus.com) |
18:52.52 | *** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru) |
19:00.25 | *** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.sta.abo.bbox.fr) |
19:03.25 | *** join/#htc-linux ray|evo (~raymonddu@66-87-26-1.pools.spcsdns.net) |
19:07.16 | *** join/#htc-linux kholk (~kholk@host129-159-dynamic.55-79-r.retail.telecomitalia.it) |
19:07.20 | *** join/#htc-linux kholk (~kholk@unaffiliated/kholk) |
19:43.18 | *** join/#htc-linux arif-ali (~arif-ali@88-111-134-148.dynamic.dsl.as9105.com) |
19:43.49 | *** join/#htc-linux kholk (~kholk@host129-159-dynamic.55-79-r.retail.telecomitalia.it) |
19:46.23 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
19:49.50 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
19:56.58 | *** join/#htc-linux DJWillis (~djwillis@cpc3-bath5-2-0-cust220.aztw.cable.virginmedia.com) |
20:04.52 | *** join/#htc-linux helicop1 (~helicopte@host64-112-dynamic.250-95-r.retail.telecomitalia.it) |
20:13.08 | *** join/#htc-linux AstainMBL (~AstainMBL@unaffiliated/astainhellbring) |
20:22.17 | *** join/#htc-linux NeoMatrixJR_ (~chatzilla@173-20-63-176.client.mchsi.com) |
20:24.48 | *** join/#htc-linux leviathan_ (~quassel@2001:470:26:484:6ef0:49ff:fee6:8dca) |
20:25.31 | *** join/#htc-linux lippa (~lippa@ppp118-209-6-120.lns20.mel4.internode.on.net) |
20:26.34 | *** join/#htc-linux Ondalf_ (~ondalf@dsl-roibrasgw1-fe5dde00-134.dhcp.inet.fi) |
20:27.17 | *** join/#htc-linux gauner1986 (~Miranda@91.56.57.209) |
20:29.15 | *** join/#htc-linux ray|evo (~raymonddu@66-87-26-1.pools.spcsdns.net) |
20:29.23 | *** join/#htc-linux rpierce99_ (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
20:29.33 | *** join/#htc-linux gummybear_ (~gummybear@188-220-145-112.zone11.bethere.co.uk) |
20:29.57 | *** join/#htc-linux bioterror (sad157@graniitti.net) |
20:29.57 | *** join/#htc-linux bukington__ (~bukington@fac34-2-82-228-151-145.fbx.proxad.net) |
20:31.35 | *** join/#htc-linux infernix (nix@unaffiliated/infernix) |
20:33.59 | *** join/#htc-linux ray|evo (~raymonddu@66-87-26-1.pools.spcsdns.net) |
20:45.20 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
20:47.23 | *** join/#htc-linux phh (~quassel@quassel.rezel.enst.fr) |
21:03.12 | *** join/#htc-linux RaiderX303 (5b6e49b2@gateway/web/freenode/ip.91.110.73.178) |
21:08.49 | *** join/#htc-linux mastermerlin (~Adium@p4FEE5B60.dip.t-dialin.net) |
21:08.54 | *** join/#htc-linux mastermerlin1 (~Adium@p4FEE5B60.dip.t-dialin.net) |
21:15.29 | *** join/#htc-linux ray|evo (~raymonddu@66-87-13-226.pools.spcsdns.net) |
21:15.42 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
21:25.33 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-71-25.26-151.libero.it) |
21:26.27 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
21:42.36 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
21:45.35 | *** join/#htc-linux gauner1986 (~Adium@p5B3839D1.dip.t-dialin.net) |
21:51.04 | *** join/#htc-linux ray|evo (~raymonddu@66-87-28-51.pools.spcsdns.net) |
22:01.04 | *** join/#htc-linux bioterror (sad157@unaffiliated/bioterror) |
22:06.53 | *** join/#htc-linux rpierce99_ (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
22:23.00 | *** join/#htc-linux nikou1 (~bizhan@c-67-180-55-37.hsd1.ca.comcast.net) |
22:23.33 | *** join/#htc-linux fakker (~noobhands@cpc13-hitc6-2-0-cust129.9-2.cable.virginmedia.com) |
22:24.34 | *** join/#htc-linux bitplane (5b6c2015@gateway/web/freenode/ip.91.108.32.21) |
22:25.15 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
22:25.26 | bitplane | Hey, just read about your fine project on Reddit. Is anyone planning on integrating SMS and SIM contacts with telepathy? |
22:26.31 | fakker | telekenesis |
22:26.45 | fakker | telekinesis sorry |
22:27.41 | *** join/#htc-linux gauner19861 (~Adium@p5B3839D1.dip.t-dialin.net) |
22:42.55 | *** join/#htc-linux MACK1E (~MACK1E@50-88-143-107.res.bhn.net) |
22:47.36 | *** join/#htc-linux khorben (~dont@2002:53ec:d9a1:1:221:28ff:fe14:b106) |
22:53.50 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
23:07.25 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
23:22.36 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
23:47.10 | *** join/#htc-linux IonCannon218 (~quassel@vps2.ionplasma.net) |
23:47.35 | *** part/#htc-linux IonCannon218 (~quassel@vps2.ionplasma.net) |