IRC log for #htc-linux on 20110530

00:05.12*** join/#htc-linux rajkosto (~rajkosto@rajkosto.broker.freenet6.net)
00:18.25jonpry2WisTilt2, 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.31jonpry2wtf
00:20.26WisTilt2i 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.37WisTilt2i 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.27pablo_hi, is there an htc phone working with linux?
00:26.16*** join/#htc-linux jonpry (~jon@199.85.236.239)
00:31.27WisTilt2jonpry, 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.41WisTilt2request_suspend_state needs state to be right, which i can't see how it ever is
00:35.39jonpryit starts at zero right
00:36.04jonpryline 82 it gets REQUESTED flag
00:36.25jonpryer SUSPENDED
00:36.35WisTilt2doesnt register happen before all of that?
00:37.02jonpryline 122 it gets !SUSPENDED
00:37.30jonpryline 164 gets REQUESTED
00:38.08jonpryshould be zero while most registration is happening
00:38.36jonprythere is small chance that early suspends are being registers while pm ops are happening
00:39.31WisTilt2in 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.21WisTilt2you 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.38jonpryconfusing indeed
00:48.07jonpryi changed a few things with timers, but no effect
00:50.34*** join/#htc-linux jonpry2 (~jon@199.85.236.239)
00:54.41jonprywe don't seem to have const char * const AUTO_OFF_TIMEOUT_DEV = "/sys/android_power/auto_off_timeout";
00:55.21jonprydoes 27 actually have that?
01:04.34*** join/#htc-linux ORi| (~ORi@91.181.155.40)
01:05.12WisTilt2jonpry, no it is not in .27 either
01:06.06jonpryits almost as if all this stuff is working fine
01:06.16WisTilt2interesting, if you swipe the sound on/off on unlock screen it doesnt sleep, only unlock itself
01:14.39WisTilt2back shortly, pizza is here
01:19.49jonpryso if i do: echo foo > /sys/power/wake_lock
01:19.50jonprythen grep foo /proc/wakelocks
01:19.51jonpryshows me that is exists
01:19.57jonpryalong with some numbers i don't get
01:21.02jonprybut if i then do echo mem > /sys/power/state
01:21.02jonpryi 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.49jonpryWisTilt2, i think i found something. your going to hate me
01:58.56*** join/#htc-linux nrirclog (~nrirclog@netripper.com)
02:01.30WisTilt2jonpry, full of pizza and beer now so i have no hate left in me:)  what'd you find.
02:05.05WisTilt2i don't know how you haven't gone postal with that connection
02:05.22WisTilt2arrrghhh you still at kbd?
02:05.24AstainHellbringseriously thats a terrible one
02:07.53*** join/#htc-linux jonpry (~jon@199.85.236.239)
02:14.00jonpry2hey
02:14.00jonpry2compare /proc/wakelocks on 27 and 39
02:14.28AstainHellbringdamn jonpry2 your internets sucks
02:15.12WisTilt2so which one are we missing?
02:17.27jonprylike all of them. brb
02:24.49WisTilt2just confirmed, unlock works without sleep 1st time from booting then fails every time after so that wakelock is not being seen
02:32.47arrrghhhWisTilt2, i'm back now, what's up?
02:34.00WisTilt2hey, i completely re-setup the xdandroid repo, got all the 2.2.2 tree but it's still frx05?
02:34.13arrrghhhi think that's the manifest file or whatever
02:34.46arrrghhhhrm
02:34.55arrrghhhat least i thought it was, perhaps not.
02:35.03WisTilt2i 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.11arrrghhhi thought it was that buildspec.mk file
02:35.25arrrghhhbut looking at the file, i don't think that is it....
02:35.28WisTilt2so its just the label wrong?
02:35.33arrrghhhwell there's one surefire way to confirm
02:35.51arrrghhhdoes the in-call screen have fancy buttons, or is it mostly blank?
02:36.38WisTilt2didnt 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.59arrrghhhyep
02:37.07arrrghhhthat was one of the few changes between 05->06
02:37.12arrrghhhnot a lot changed TBH
02:37.34WisTilt2actually, brain fart here... i forgot i cant even build it because it doesn't like java 1.6
02:37.48WisTilt2i just see in the start of build it says frx05
02:37.56arrrghhhhrm
02:38.35WisTilt2PLATFORM_VERSION_CODENAME=REL
02:38.35WisTilt2PLATFORM_VERSION=2.2.2
02:38.35WisTilt2TARGET_PRODUCT=generic
02:38.35WisTilt2TARGET_BUILD_VARIANT=eng
02:38.35WisTilt2TARGET_SIMULATOR=
02:38.35WisTilt2TARGET_BUILD_TYPE=release
02:38.37WisTilt2TARGET_BUILD_APPS=
02:38.39WisTilt2TARGET_ARCH=arm
02:38.41arrrghhhi think that's defined in the build.prop
02:38.41WisTilt2HOST_ARCH=x86
02:38.43WisTilt2HOST_OS=linux
02:38.47WisTilt2HOST_BUILD_TYPE=release
02:38.49WisTilt2BUILD_ID=FRX05
02:38.51arrrghhhbut at buildtime, i'm not sure what specifies it.
02:38.53WisTilt2thats straight off the repo
02:39.32WisTilt2k, 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.58WisTilt2we've been working on this crazy unlock screen issue and i've been looking at whats causing the high battery drain.
02:41.08arrrghhhnice
02:41.45WisTilt2.39 is so much faster so will be nice when we get some of the critical crap fixed.
02:41.50arrrghhhindeed
02:41.54arrrghhhwith those two things
02:42.02arrrghhh& installs
02:42.43arrrghhh.39 should be in at least a pretty good state
02:43.27WisTilt2sounds 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.41arrrghhhsweet
02:43.56arrrghhh.39 felt like .27 on nilfs
02:44.07arrrghhhi guess i should try .39 on nilfs
02:44.15arrrghhhmy phone will rip a hole in the space-time continuum
02:45.11WisTilt2something 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.29arrrghhhwouldn't surprise me
02:45.41arrrghhhat idle i wouldn't think so, but certainly in-use it would.
02:46.37WisTilt2im 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.34arrrghhhyea
02:47.36arrrghhhhrm... that's odd.
03:07.28jonpryfound is such a strong word
03:10.18jonpryWisTilt2, i added evdev wakelock which seemed important. but no go
03:12.03WisTilt2damn.
03:12.49jonpryarrrghhh, can you do a .27 experiment?
03:12.55arrrghhhsure what's up?
03:13.09WisTilt2im 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.38jonpryget usb terminal open, and your phone in an unlocked state. then: echo foo > /sys/power/wake_lock; echo mem > /sys/power/state
03:14.54jonpryand see if it does anything
03:14.54jonprythe missing code is basically stuff to buy a fraction of second
03:14.57jonprywhat i'm seeing is strange correlation with the pm functions and the panel blank or unblank
03:15.14jonprylike how does it kill panel?
03:16.08arrrghhhjonpry, just goes to the next line...
03:16.18jonprydoes the screen turn off?
03:17.11arrrghhhyes
03:17.38jonpryand echo on > /sys/power/state
03:17.46jonpryturns it back on?
03:18.28arrrghhhyes
03:19.05jonprycan you paste the contents of /proc/wakelocks?
03:19.25*** join/#htc-linux Rob2223 (~Miranda@p4FFF1DCD.dip.t-dialin.net)
03:20.00arrrghhhhttp://pastebin.com/aWn7F4yr
03:21.15*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
03:26.19jonprythanks arrrghhh
03:26.24*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
03:30.46arrrghhhnp
03:35.06jonpryWisTilt2, i have seen it work a few times now. so random timing related process
03:36.07jonpryand 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.16WisTilt2could 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.55jonpryafter boot phone is probably slow
03:42.21jonprydoes libhardware need to implement the other kinds of wakelocks?
03:43.07WisTilt2dont know
03:43.31WisTilt2i 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.46jonpryI really think that libhardware is relying on a timing bug that used to be more certain
03:57.33jonprythe libhardware kind of sucks really. doesn't support most wakelocks and doesn't use activity timeout
04:06.23jonpryarrrghhh, does .27 have /sys/android_power ?
04:06.40arrrghhhlet me see
04:07.20arrrghhhjonpry, no
04:09.48WisTilt2ok, 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.19jonpryi have that fixed now. want me to push?
04:10.42WisTilt2jonpry, 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.59WisTilt2yes please so i can look at that evdev code
04:11.49jonpryits 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.21jonpryWisTilt2, so at 100 it will work on 2.2.2?
04:13.32jonprypushed
04:13.37WisTilt2i cant build 2.2.2 due to my java 1.6
04:13.55jonpryumm, you can't get java 1.5?
04:14.00WisTilt2if you can try it that would be great.  5000 is the default, doesnt work right, 100 works perfect
04:14.20WisTilt2i dont want mess up my 1.6
04:14.48jonpryin ubuntu there is some alternates system. i can switch 1.6/1.5 gcj etc with one command
04:16.38WisTilt2did you only push evdev.c?
04:17.08jonpryno i pushed everything cause i have been hacking all around
04:17.19arrrghhhyea that's what i had to do WisTilt2
04:17.23arrrghhhforce java version
04:17.38jonpryor edit build/core/main.mk and comment out 104-134
04:17.43WisTilt2how do i do that
04:17.51WisTilt2force java version sounds good
04:17.59arrrghhhWisTilt2, 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.11WisTilt2jonpry 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.37jonprywhen did you last pull?
04:20.55WisTilt2just now
04:21.10jonpryi mean change between when and when
04:21.52WisTilt2in the commit you just pushed was something in pm.c changed or was that earlier?
04:22.48jonpryearlier i think
04:23.15jonpryits just warning fixed
04:23.49jonpryshould patch cleanly against whatever you have
04:24.25jonpryand 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.54jonpryif it won't build then you know something important didn't merge
04:26.27jonpry--------------------------- arch/arm/mach-msm/pm.c ----------------------------
04:26.29jonpryindex 95b9daa..4a86c87 100644
04:26.29jonpry@@ -140,7 +140,7 @@ static void msm_pm_add_stat(enum msm_pm_time_stats_id id, int64_t t)
04:26.30jonpry<PROTECTED>
04:26.30jonpry<PROTECTED>
04:26.30jonpry<PROTECTED>
04:26.32jonpry-void msm_pm_flush_console()
04:26.32jonpry+void msm_pm_flush_console(void)
04:26.34jonpry<PROTECTED>
04:26.36jonpry<PROTECTED>
04:26.38jonpry<PROTECTED>
04:26.40jonpry@@ -375,7 +375,7 @@ void arch_idle(void)
04:26.42jonpry<PROTECTED>
04:26.44jonpry<PROTECTED>
04:26.48jonpry<PROTECTED>
04:26.50jonpry-unsigned long saved_rate;
04:26.52jonpry+//unsigned long saved_rate;
04:26.54jonpry<PROTECTED>
04:26.56jonpry<PROTECTED>
04:26.58jonpry<PROTECTED>
04:27.00jonpry@@ -469,7 +469,7 @@ static struct platform_suspend_ops msm_pm_ops = {
04:27.02jonpry<PROTECTED>
04:27.04jonpry<PROTECTED>
04:27.06jonpry<PROTECTED>
04:27.08jonpry-static void msm_pm_restart(char str)
04:27.10jonpry+static void msm_pm_restart(char str, const char *cmd)
04:27.12jonpry<PROTECTED>
04:27.14jonpry<PROTECTED>
04:27.18jonpry<PROTECTED>
04:27.20jonpry@@ -492,13 +492,14 @@ static void msm_pm_restart(char str)
04:27.22jonpry<PROTECTED>
04:27.24jonpry<PROTECTED>
04:27.26jonpry<PROTECTED>
04:27.28jonpry+unsigned num;
04:27.30jonpry+
04:27.32jonpry<PROTECTED>
04:27.34jonpry<PROTECTED>
04:27.36jonpry<PROTECTED>
04:27.41jonpry<PROTECTED>
04:28.07jonpry<PROTECTED>
04:28.07jonpry<PROTECTED>
04:28.07jonpry-unsigned num;
04:28.07jonpry<PROTECTED>
04:28.08jonpry<PROTECTED>
04:28.08jonpry<PROTECTED>
04:28.09jonpry@@ -655,8 +656,9 @@ __initcall(msm_pm_init);
04:28.09jonpry<PROTECTED>
04:28.10jonpry<PROTECTED>
04:28.10jonpry<PROTECTED>
04:28.11jonpry-printk("Sending arm9_low_speed 2\n");
04:28.11jonpry<PROTECTED>
04:28.12jonpry+
04:28.12jonpry+printk("Sending arm9_low_speed 2\n");
04:28.13jonpry<PROTECTED>
04:28.13jonpry<PROTECTED>
04:28.26jonpry-printk("Sending arm9_low_speed 7\n");
04:28.28jonpry<PROTECTED>
04:28.30jonpry+
04:28.33jonpry+printk("Sending arm9_low_speed 7\n");
04:28.34jonpry<PROTECTED>
04:28.36jonpry<PROTECTED>
04:28.39jonpry<PROTECTED>
04:28.40jonpryoops
04:28.45WisTilt2lol, was that headed for pastebin and you hit wrong window?
04:28.48jonpryi was trying to paste the pastebin address :p
04:28.48jonpryhttp://pastebin.com/D7DMftXg
04:28.54jonpryoh and then there is fiq handler
04:29.04jonpryit was already in pastebin. but the copy of the address didn't happen
04:29.16arrrghhhlol
04:29.38jonpry2well ya know
04:30.26WisTilt2do you know where the client list comes from in evdev_event?
04:30.51jonprydude. 3.0 rc1 :p
04:31.06jonprywe're only one patchset away
04:31.29jonpryi dunno what that is
04:32.04WisTilt2finals around the corner?
04:32.12jonprykernel.org
04:32.30jonprywe can have first phone with linux 3.0
04:32.54jonpryi can rebase it in like an hour :p
04:33.14*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
04:33.55arrrghhhi heard linus was looking to not do a .40
04:34.37*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
04:34.38arrrghhhand skipping right to 3.0
04:34.48jonpryi thought it would be 2.8 though. they always said majors were for ABI change
04:35.02WisTilt2jonpry, found a rather important wakelock that's missing in the event passing
04:35.29jonpryi'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.46WisTilt2we need to add wake_lock_timeout(&client->wake_lock, HZ/10); right after the spinlock at line 59
04:36.51jonpryin evdev?
04:37.13WisTilt2yes
04:38.03jonprythats already in there
04:38.35jonpryalong with everything else that makes it work
04:38.59jonpryand wakelocks are not really interesting at this point because you can make as many as you want and it will still happen
04:39.33WisTilt2i dont see that in this source, where are you looking?
04:40.10jonprywakelocks themselves may be broken. but adding more here or there is not the crux of it
04:41.25jonpryyou pulled?
04:41.43WisTilt2yes, have current tree since you just pushed
04:42.45jonpry61:62: spin_lock(&client->buffer_lock);
04:42.46jonprywake_lock_timeout(&client->wake_lock, HZ/10);
04:42.54jonprydrivers/input/evdev.c
04:42.58WisTilt2omg, yeah i have the tree but im looking at my previous evdev for god sakes
04:43.03WisTilt2i need to go to bed
04:44.02WisTilt2i had it in the editor but didn't reload after i pulled:)
04:44.03jonpryi just finished my new system.img
04:44.10jonprythat will do it
04:44.54WisTilt2did you build it with that value changed to 100 for kicks?
04:45.07jonpryyep
04:45.59jonpryi enabled all the logging from libhardware_legacy/power so we can see exactly what android is offering when
04:46.36WisTilt2good idea
04:53.20jonpryok so android only ever tries to: acquire_wake_lock lock=1 id='rpc-interface'
04:53.52jonprywhich doesn't necessarily seem correct to me, but like i said partial_wake_locks are not the problem
04:54.32jonpryother than that it literally calls set_screen_state 0 right after the unlock button gets to the end
04:54.46jonpryand 100 did not help me
04:56.46*** join/#htc-linux kiozen (~kiozen@ppp-93-104-72-247.dynamic.mnet-online.de)
05:02.25WisTilt2so 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.36WisTilt2arrrghhh 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.51arrrghhhsure
05:09.59arrrghhhjust upgrading some voicemail servers @ work :P
05:10.40WisTilt2you're doing work for work on a 3 day weekend?
05:10.48arrrghhhbest time to do it
05:10.54WisTilt2yeah true
05:10.55arrrghhhif something blows up, i've got all day tomorrow to fix it
05:12.51WisTilt2ok 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.29arrrghhhk
05:14.30arrrghhhgreat, got 2 bad DIMMs.  hopefully this thing'll limp along until Cisco ships me a new box... oy.
05:16.48jonpryi'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.42WisTilt2jonpry, figuring that out requires lots of engineering fluid.
05:19.49arrrghhhheh
05:19.56arrrghhhi'm all out of single-malt scotch tho!
05:21.03jonpryi have some high test
05:22.02WisTilt2yeah i like GlenLivet 21 myself
05:22.57WisTilt2had some of their 40yr stuff once and couldn't tell the difference to justify the extra outrageous cost
05:24.49WisTilt2arrrghhh btw, system.zip is up along with zImage with your usual filename.
05:25.06arrrghhhcool
05:25.33WisTilt2if this combo doesn't fix the unlock/sleep deal on your phone im going to commit myself somewhere
05:25.44arrrghhhlol
05:26.07WisTilt2i just want to make sure im not totally crazy in what im seeing here
05:26.51jonpryi'm pretty sure this is happening, but don't know why: WindowManagerPolicy#OFF_BECAUSE_OF_TIMEOUT
05:27.53WisTilt2that is when the error happens in early suspend waiting for user to stop drawing i believe
05:31.10arrrghhhalrighty
05:31.12arrrghhhbootin
05:33.00WisTilt2check 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.56arrrghhhheh
05:33.57arrrghhhok
05:34.17jonpryah thats the default state
05:35.00jonpryso basically if anything turns the blasted thing off, it will cause rtc alarm etc
05:37.21jonprycan you attach android debugger to the frameworks?
05:38.11WisTilt2that's a stinebd question:) i have no idea
05:38.35arrrghhhhrm
05:38.37arrrghhhseems hung
05:38.59WisTilt2you let it make new data.img?
05:39.08arrrghhhyea
05:39.11arrrghhhand it appeared to
05:39.31jonprysometimes it takes long time
05:39.40jonpryyou can test for death with usb
05:39.45arrrghhhblinkin cursor didn't blink
05:40.21arrrghhhyea it did create a data.img.  gonna try booting again.
05:42.38arrrghhhappears to be booting OK
05:46.26*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
05:47.21arrrghhhWisTilt2, old in-call screen... :/
05:47.48WisTilt2ok so it is 2.2.1
05:48.56arrrghhhwaiting to test the sleep issue
05:50.45arrrghhhdurn thing won't sleep
05:50.48arrrghhhi'm on the old RIL tho
05:51.29WisTilt2hmm, thats the only thing i haven't tried with this.  im still on hyc's via bind mount
05:51.41arrrghhhyea i should've left it in there.
05:53.36WisTilt2arrrghhh, 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.02WisTilt2im going to copy them off my phone so i know they're the right ones since it working on both phones here.
05:55.31arrrghhhheh
05:55.32arrrghhhok
05:55.53arrrghhhhey lookie thar.  the server disabled the bad DIMMs this time around, and the CPU isn't spiking like mad.
05:56.07arrrghhheh i'll still let them send me a whole new rig.
05:57.00WisTilt2this is a cisco server with bad dimms?
05:57.41arrrghhhyea kinda
05:57.48arrrghhhit's an 'appliance'
05:57.54arrrghhhbut it's IBM hardware in reality
05:58.04arrrghhhcisco-branded IBM hardware.
05:58.14WisTilt2ios or linux?
05:58.30arrrghhhlinux
05:58.34arrrghhhUnity Connection
05:59.49arrrghhhcisco 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.55jonpry2i think this debugging system_process with adb will eventually work
05:59.57arrrghhhalthough they lost their partnership, some internal BS
06:08.42jonprywill take a few days to build though damn
06:10.07jonprylater fellas. adb remote debugging of frameworks == badass. whoever can do this holds the keys. http://source.android.com/source/using-eclipse.html
06:10.20arrrghhhnice
06:10.27arrrghhhcya dude
06:10.44WisTilt2nit jonpry
06:10.59WisTilt2ok arrrghhh new system.zip and zImage
06:11.04arrrghhhk
06:11.07WisTilt2this has to work on your phone!
06:11.15arrrghhhlol
06:11.19arrrghhhyes sir...
06:11.21arrrghhh:P
06:11.56WisTilt2psychiatric ward is not too far from where I live if not:)
06:12.30arrrghhhhahaha
06:19.14arrrghhhk.  new data.img, booting
06:22.15arrrghhhhrm.  kernel panic & freeze.  i think this is same as the last time, lemme reboot.
06:23.57WisTilt2ive 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.48arrrghhhthat's what happened last time
06:24.53arrrghhhi 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.50WisTilt2arrrghhh smoke pouring out of your phone?
06:39.10arrrghhhlol not yet
06:39.13arrrghhhbut i had another failed boot
06:39.20arrrghhhso i'm putting the newest RIL In
06:39.24arrrghhhbootin now
06:40.05WisTilt2ok.  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.23arrrghhhhrm
06:40.27arrrghhhstill failed to boot...
06:41.11arrrghhhanything special i need in rootfs?
06:41.16*** join/#htc-linux dekar_ (~dekar@drms-590ced65.pool.mediaWays.net)
06:41.23arrrghhhi just have F22's rootfs "for" hyc's RIL
06:41.28arrrghhhril2
06:42.17WisTilt2i have F22's earlier rootfs from months ago and running hyc's 4/14 ril
06:45.21WisTilt2F22's 02/12/11 rootfs actually
06:46.55arrrghhhhrmmmm
06:46.58arrrghhhstill failing to boot
06:47.07WisTilt2how far does it get?
06:48.53arrrghhh9e1032b2fc8f9c15813cc865f8985433 for the kernel
06:48.55arrrghhh1 sec
06:50.33arrrghhhi see the touch calib stuff
06:50.39arrrghhhthen it starts spitting out stuff too fast
06:50.42arrrghhhlots of 'end trace'
06:50.53arrrghhheventually it hangs after a kernel panic
06:50.53WisTilt2kernel sum is good
06:51.58*** join/#htc-linux stroughtonsmith (~steven@86-43-216-108-dynamic.b-ras2.bbh.dublin.eircom.net)
06:51.59WisTilt2system sum a9bfe19ed2cebd53b42525c74f891d79
06:52.43WisTilt2i can upload the rootfs if you want to try it
06:54.13arrrghhhi doubt that's the issue...
06:54.16arrrghhhm
06:54.48WisTilt2you have the initrd offset still?
06:55.20arrrghhhset initrd_offset 0x00a00000
06:55.25arrrghhhand the different haret
06:55.29WisTilt2yep
06:55.29arrrghhhwait system.ext2 doesn't match
06:55.33arrrghhhwas that the zip's md5?
06:56.53arrrghhhsystem.zip from the usual place right?
06:57.14arrrghhhneither of the md5's match for the system.  the .ext2 or the .zip
06:57.22WisTilt2beab12ff8dd918224376dcbc5ce00500
06:57.34arrrghhhthat matches the .zip
06:58.21arrrghhhwhere'd that system sum come from tho?
06:58.54WisTilt2that last one was the zip
06:59.04WisTilt2previous ending in 1d79 was ext2
06:59.23arrrghhhweird, the ext2 came out a different sum for me.
06:59.40*** join/#htc-linux Stskeeps (~cvm@Maemo/community/distmaster/Stskeeps)
06:59.58WisTilt2you have fast download, ill upload the system.ext2
07:00.13arrrghhh150e8faa3fbb7997c4a109e9a4ad0598
07:00.16arrrghhhis what i have
07:00.24arrrghhhalright
07:00.26WisTilt2for ext2?
07:00.32arrrghhhyea
07:01.53*** join/#htc-linux Segnale007 (~Segnale00@ppp-242-47.26-151.libero.it)
07:02.42arrrghhhgonna try once more
07:03.05arrrghhhcuz md5 didn't match the one on my phone
07:04.02*** join/#htc-linux Rob2222 (~Miranda@p4FFF1DCD.dip.t-dialin.net)
07:04.08WisTilt2i 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.21arrrghhhweird
07:04.26WisTilt2yeah it is
07:05.34WisTilt2ok system.ext2 ready
07:05.47arrrghhhk
07:06.38WisTilt2just did sum across usb to phone and it also matched so you should be good with this one
07:16.24arrrghhhalright, 2nd boot here we go!
07:16.35arrrghhhmd5 matches this time too :P
07:17.06arrrghhhhrm
07:17.08arrrghhhdoesn't look good
07:17.13arrrghhhrebooting to recovery
07:17.16arrrghhhlots of untracked pids
07:17.22arrrghhhkernel panic, freeze.. wth
07:17.26WisTilt2wth
07:17.33*** join/#htc-linux Segnale007 (~Segnale00@ppp-242-47.26-151.libero.it)
07:18.07WisTilt2same kernel and system. ril and rootfs is only other diff
07:19.06WisTilt2check md5sum on those files on the phone itself
07:20.20*** join/#htc-linux Bry8Star|Unix (~Bry8Star|@gateway/tor-sasl/bry8star-)
07:22.59arrrghhhok this is maddening
07:23.10arrrghhhmd5 matched on my laptop, didn't match after copying it over.
07:23.35WisTilt2sdcard flaking?
07:23.45arrrghhhi guess?
07:23.51arrrghhhhaven't had any other issues.
07:24.26WisTilt2murphy must be staying up late lol.
07:24.47arrrghhhheh
07:25.06arrrghhhok now it matches on the phone...
07:25.08arrrghhhoy
07:25.50WisTilt2maybe we'll get lucky this boot, hopefully data.img is ok still
07:26.20arrrghhhyea i'm hoping too... it'll save time
07:27.11arrrghhhcrap.  status quo...
07:28.44WisTilt2maybe .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.31arrrghhhyea every time it hits the calib section
07:32.47arrrghhhother .39 kernels worked tho
07:33.40WisTilt2is calib file ok?
07:35.12WisTilt2this 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.31arrrghhhhrm
07:35.55WisTilt2is the calib for touchscreen or that wifi calib stuff its crashing on?
07:36.47arrrghhhts
07:39.16WisTilt2my 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.00arrrghhh839,892,187,892,513,535,842,183,184,175
07:46.18arrrghhhhrm.  md5 doesn't match again.  i thought it was mounting /system RO?
07:47.51arrrghhhi think it's bedtime for me tho man...
07:48.11WisTilt2yeah me too.  you'll probably get it going with a fresh mind tomorrow
07:48.27arrrghhhyea
07:48.38arrrghhhprobably missing something silly :P
07:48.49WisTilt2ill catch you sometime tomorrow if you're on.  thanks for the attempt
07:48.52arrrghhhi'll talk to you tomorrow... er later today ha.  take it easy.
07:48.55arrrghhhnp
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.45kholkhi guys
13:27.28kholkI'm here for asking some help on a little thing that the HTC Linux project has already done multiple times
13:28.02kholkanyone 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.34jonprykholk, what kind of device are you working on?
14:07.57kholkMotorola Atrix
14:08.07kholkOlympus board
14:08.08kholkTegra2
14:08.42kholkI'm close to boot a custom BL, I need the physical RAM start address though
14:08.55jonpry2do you have source?
14:08.56kholkthat would solve the locked bl problem and skip it
14:08.59kholkyep I have
14:09.07kholkand UART too.
14:09.15kholkI can see what the NvMicroBoot is saying at boot
14:09.18jonpry2then in machine_start it will say where ramis
14:09.26kholk'cause I've actually got an unlocked engineering device
14:09.35kholkuh, machine_start?
14:09.38kholklooking at it
14:10.14kholkbut I remember I've already looked at something like that
14:10.21kholkand didn't find anything
14:10.33kholkmaybe it was another thing, so, searching
14:10.56jonpry2its in the board file
14:10.57kholkI can remember anyway that on my bootloader sourcecode I can find 0x00000000 as RAM start address
14:11.01kholkthing that is impossible
14:11.08kholkoh, so I've already looked at it
14:12.06jonpry2like here is the relevant section of board-htcrhodium.c http://pastebin.com/QYPFQYDB
14:12.31jonpry2in our case its the definition of PHYS_OFFSET
14:12.32kholkboot_params?
14:12.41kholkoh.
14:13.01jonpry2iirc that is probably true for all machines on newer kernels
14:13.55kholkthing is, I've already looked for PHYS_OFFSET
14:14.02kholkand there seems there isn't any trace of that
14:14.18jonpry2is your tree online?
14:14.33kholknot mine, but the Moto kernel source is on opensource.motorola.com
14:14.45jonpry2i only do gitweb
14:15.00kholkthere isn't any gitweb for it
14:15.10kholkbut if you want I can upload it on my gitorius
14:15.51kholkthe only reference on PHYS_OFFSET that I'm finding is
14:15.56kholk./include/mach/memory.h:#define PHYS_OFFSET             UL(0)
14:15.57jonpry2i'm assuming the stuff in mach-tegra is the same as for your chip
14:16.01kholk(in mach-tegra)
14:16.08jonpry2yeah thats what i got too
14:16.12kholkheh.
14:16.15jonpry2so there you go :p
14:16.44jonpry2and boot_params is 0x100
14:17.16kholkso the ram start address is 0x0?
14:17.23jonpry2yep
14:17.27kholkrofl
14:17.32kholkso I've had the solution under my nose
14:17.41kholkand I wasn't believing at it?
14:17.42kholk:P
14:17.46kholkoh, well.
14:18.32kholkso...thanks man :D
14:18.39jonpry2no 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.22Alex[sp3dev]kholk: still there?
15:12.50*** join/#htc-linux _twitch (~burning_a@64.112.96.58.static.exetel.com.au)
15:17.35kholkAlex[sp3dev], yep
15:19.48Alex[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.36kholkI already have a new loader.
15:20.42Alex[sp3dev]does it work?
15:20.47kholkit seems to :)
15:21.08kholkthe only problem happens after the cpu_reset
15:21.15Alex[sp3dev]could you share the code? i'll test somewhere close to weekends.. dang. hate acer
15:21.24kholkI'll do
15:21.55kholkgotta buy cigs now
15:21.55kholk:P
15:21.56kholk'later
15:22.00Alex[sp3dev]what happens after cpu_reset anyway?
15:22.28kholkoh well
15:22.33kholk"hang" and reboot
15:22.43kholkit's because I haven't compiled a proper boot image
15:22.47kholkwith the needed boot parameters
15:22.53kholkbut, well, it's coming soon
15:23.00kholkas I already know the boot parms
15:23.07kholkand I only have to do an mkbootimg...
15:23.07kholk:P
15:23.26Alex[sp3dev]oh well. i don't even have kernel sources.. so it's gotta be fun
15:23.38kholkopensource.motorola.com
15:23.45Alex[sp3dev]i have acer iconia a500
15:23.47kholkATT Atrix -> kernel.tgz
15:23.59kholkiconia?
15:24.06Alex[sp3dev]yep
15:24.07kholkoh, 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.22Alex[sp3dev]no. i'm using my own. haven't found sources for yours
15:24.27kholkhaha
15:24.32kholkokay anyway
15:24.50kholkit's better to hold on, I think
15:24.58kholkand well
15:25.03kholkcrack your iconia bootloader
15:25.07Alex[sp3dev]haha
15:25.08kholkyou'll need it.... :)
15:25.11kholknot kidding.
15:25.17Alex[sp3dev]i can't even get a dump of it.
15:25.21kholkoh,
15:25.30kholkso I have to build a custom bootloader for you, too.... :)
15:26.03kholkmy new method needs an SPL
15:26.06Alex[sp3dev]what do you mean by that? can tegra bootloader be circumvented without kexec?
15:26.18kholkTegra bootloader?
15:26.21kholkyou mean...
15:26.24kholkIconia bootloader.
15:26.26kholk:)
15:26.46kholkOEMs are using custom solutions, my friend..
15:26.53Alex[sp3dev]i suppose tegra has some bootloader inside the cpu which provides nvflash and launches second stage loader from nand or mmc
15:27.01kholkoh, the BootROM
15:27.06kholknVMicroBoot
15:27.19kholkthe IPL
15:27.26*** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it)
15:27.52kholkwell, you really can't skip what the IPL is doing
15:28.02kholkI can give you some output from MicroBoot though
15:28.10kholkas I can...and you all can't
15:28.23kholk(not that I'm a genius, I only have an engineering device)
15:28.24Alex[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.36kholkEBT?
15:28.38kholkhah
15:28.44kholkwhat do you want?
15:28.45kholkMicroBoot?
15:28.56Alex[sp3dev]nah. want to find out where acer loader is stored
15:29.05kholkI can inform you that MicroBoot is the same for all Tegra devices
15:29.12kholkmy Atrix runs on an Advent Vega MicroBoot
15:29.15Alex[sp3dev]i think it may be stored encrypted. but that'd be epically stupid
15:29.17kholkand on a custom BL..
15:29.30kholkif your bootloader can't be dumped
15:29.32kholkyou're half fucked
15:29.37kholklook at Motorola Xoom
15:29.38kholk:)
15:29.50Alex[sp3dev]what? isn't xoom unlocked by default?
15:30.27kholkyeah. take a Xoom and try to dump the bootloader.
15:30.30kholkrofl
15:31.15Alex[sp3dev]i'm fully fucked. when i flash custom linux or recovery, it bails out with checksum error on boot
15:31.31kholkXoom's BL can give a way to exploit the Atrix BL
15:31.41kholkheh.
15:31.48kholkat Moto they aren't stupid
15:32.04kholkand on Xoom you can't access NvFlash too, so you can't unlock the mask on the BL partition
15:32.07kholkand you can't dump it
15:32.15kholkand you're really fully, totally fucked
15:32.28kholkunless you find a method for unmasking your BL partition
15:32.37kholkthing that is half impossible because it isn't done on the Linux kernel
15:32.54Alex[sp3dev]so what? is it stored in mmc but is hidden (remapped) by the controller?
15:33.02kholkso, well, unless Acer gives a BL update
15:33.05kholkyou won't ever have it
15:33.07kholkwell
15:33.16kholkTegra2 has got a well good protection system
15:33.22Alex[sp3dev]i've noticed that
15:33.24kholkas it is masking the SBK for example
15:33.29kholkwith FF's
15:33.38kholkit is even masking your partitions
15:33.53kholkyou can mask everything you want with Tegra BootROM
15:34.14kholkeven the Android system partition. but then you won't be able to boot.
15:34.15kholk:P
15:34.20Alex[sp3dev]and as i can guess, you cannot reconfigure masking once bootrom handles contol over?
15:34.22kholkso basically, you're fucked
15:34.28kholkwell, exact
15:34.31kholkif it was possible
15:34.32*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
15:34.38kholkI'd already have reconfigured the maskings
15:34.42kholkand retrieved the SBK
15:34.44kholkout of the Atrix
15:34.45kholk:)
15:35.29kholkyou need to play with ODMData
15:35.31kholkand BCT
15:35.43kholkbut, well, as you know, you can't
15:36.13kholkanyway, just out of curiosity
15:36.19kholkwhy Acer Iconia and not Moto Xoom?
15:36.41kholk(Iconia = Iconia TAB, right?)
15:36.42Alex[sp3dev]it was like $200 cheaper.. now i know why..
15:36.51kholkoh, yep
15:36.51kholk:)
15:37.02kholkACER is ever cheaper than others
15:37.15kholkI don't know why you're all buying tablets though
15:37.29kholkbuying an x86 machine with a touchscreen would be a better choice I think
15:37.36kholkanyway, I'm happy with my Tegra2 phone :P
15:37.52kholkokay, now I'll go to buy cigs
15:37.53kholkbrb, 5 mins
15:37.54kholk:P
15:37.58Alex[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.59Alex[sp3dev]ok
15:38.28AstainHellbringloves his g tablet with access to nvflash and all :)
15:38.46Alex[sp3dev]f u troll, go away now
15:38.52AstainHellbringlol
15:40.55AstainHellbringironically I havent even setup access to nvflash or learned to far how to do it
15:40.57Alex[sp3dev]the tablet ain't bad as is.. but android just sucks..
15:41.16arrrghhhheh
15:49.58kholkso
15:50.03*** part/#htc-linux Stskeeps (~cvm@Maemo/community/distmaster/Stskeeps)
15:50.06kholkwhy have you bought an android tablet
15:50.10kholkif you don't like android
15:50.12kholk?
15:50.38Alex[sp3dev]i planned on using it as a development device for ubuntu/meego.
15:51.07kholkwhy 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.47kholkI've bought an Atrix because it's small and I can take it in my pocket
15:52.01kholkyou could have bought a development board
15:52.08kholkwith a Tegra2 CPU module
15:52.10Alex[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.47kholkwell, same thing
15:52.58kholkyou still need some bag for carrying your device with you
15:53.06kholka small development board would have been a good choice
15:53.21Alex[sp3dev]yeah, ventana looks almost like a finished tablet
15:53.29kholkI'm not talking about Ventana
15:53.34Alex[sp3dev]i
15:53.35Alex[sp3dev]i
15:53.39Alex[sp3dev]damn fuck
15:53.46kholkI'm talking about development kits
15:53.50kholkopen boards
15:53.58Alex[sp3dev]i'm not that geek to carry pandaboard, lcd and a car battery in my backpack
15:54.07kholkwell you don't have to
15:54.17kholkthe board is such small
15:54.30kholkas a battery you could use a battery for RC airplanes
15:54.37kholkpretty small batteries
15:54.44kholkwith like 4000mAh of amperage
15:54.51kholk3.7V though.
15:54.55kholkthe exact voltage for your device
15:55.12kholkLCD, you would buy a 7" or 10" LCD for your device
15:55.17kholkor OLED display
15:55.30kholkso that wouldn't be so big
15:55.34kholkjust a little bigger than a tablet
15:55.35Alex[sp3dev]i think you need to talk to jonpry about prypad ;)
15:55.42kholkprypad? lol
15:56.18Alex[sp3dev]rumours are the end of the world will happen when he finishes assembling it
15:57.32kholklol
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.09WilldL
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.55jonpryAlex[sp3dev], the end of me already happened. prypad is no more. i've decided to work full time on htc-linux
17:35.55Alex[sp3dev]jonpry: when can we expect linux 3.0 on rhodium? rebased already?
17:36.51arrrghhhheh
17:37.28rob_wis there any htc curently running omap3 ?
17:38.07Alex[sp3dev]http://www.blogcdn.com/mobile.engadget.com/media/2009/08/omap-combo-breaker.jpg
17:41.55kholkgo to OMAP4.
17:42.13kholkdid you know that OMAP4 features volatile memory encryption?
17:42.17kholk(RAM encryption)
17:42.19kholkrofl
17:42.45Alex[sp3dev]the encryption is getting more anal
17:43.55jonpryAlex[sp3dev], i'm going to do it this week sometime. i need to to do heritage analysis
17:44.11jonpryi think it might be easier to go to 39.2 first
17:44.20kholkyeah.
17:44.27kholkwhen they'll give you a locked device
17:44.30kholkwith RAM encryption
17:44.32kholkit'll get anal.
17:44.33kholkto you.
17:44.34kholkrofl
17:45.01jonprydidn't via c3 have something like that?
17:48.32jonpryand 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.26bitplaneHey, just read about your fine project on Reddit. Is anyone planning on integrating SMS and SIM contacts with telepathy?
22:26.31fakkertelekenesis
22:26.45fakkertelekinesis 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)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.