00:08.15 | *** join/#htc-linux nautis (~nautis@76-218-70-41.lightspeed.sntcca.sbcglobal.net) |
00:35.26 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
00:42.25 | *** join/#htc-linux gauner1986 (~Adium@p5B382DC6.dip.t-dialin.net) |
00:47.26 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
01:08.03 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
01:12.31 | jon_ | WisTilt2, get it working? |
01:19.00 | WisTilt2 | barbecue time right now and im the chef. i only got as far as finding fbearly suspend is shutting us down but haven't found any missing wakelock as of yet. |
01:19.40 | WisTilt2 | i'll be done cooking/eating in 30-45mins |
01:25.25 | jon_ | yeah that fbearlysuspend is some sketchy stuff too |
01:33.27 | *** join/#htc-linux rob_w_ (~bob@ppp-93-104-167-36.dynamic.mnet-online.de) |
01:39.12 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-240-56.26-151.libero.it) |
01:49.35 | *** join/#htc-linux jon_ (~jon@199.85.236.239) |
02:24.32 | jon_ | WisTilt2, i don't think we are supposed to have fbearlysuspend |
02:30.47 | WisTilt2 | boy do i know how to barbecue lamb! now i either need to take a nap or get my brain in gear. |
02:31.25 | WisTilt2 | jonpry whats happens when we remove it? i dont know why it would be needed anyway. |
02:33.14 | *** join/#htc-linux Raymonddull (~raymonddu@24-247-192-213.dhcp.monr.mi.charter.com) |
02:33.24 | WisTilt2 | btw, this fbearlysuspend apprears to be whats causing the panel shutdown to work the way it is, which isnt right. i added the panel register to turn off display in blank just to test it and it still stayed alive until mddi power off. |
02:41.23 | jon_ | i turned it off, but it doesn't help |
02:42.52 | WisTilt2 | where's the wakelock from userland after unlock happens? is that a key event or what? |
02:44.14 | jon_ | in theory it should be changing the timeout on powermanager |
02:44.44 | jon_ | like there is some short lock while unlock is visible. then after unlock it will be switched the user preference dealy |
02:45.16 | jon_ | maybe we probably have an attribute problem again so timeout is getting set to zero |
02:46.51 | jonpry | i pushed the stuff to get rid of fbearlysuspend whatever it does. atm i can't see how powermanager interacts with the kernel |
02:47.44 | WisTilt2 | yeah that logic sounds good. whatever timer value is or isnt being changed, it works out to 1200ms about every time. |
02:49.51 | *** join/#htc-linux Dunedan (~dunedan@phoenitydawn.de) |
02:53.02 | *** join/#htc-linux nautis_ (~nautis@76-218-70-41.lightspeed.sntcca.sbcglobal.net) |
02:55.23 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
02:59.00 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
03:01.58 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
03:03.42 | jonpry | i'm not terribly close to finding how wakelocks work by tracking down compiler warnings |
03:16.00 | *** join/#htc-linux MacDrunk (~marper@201.164.176.184) |
03:18.07 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
03:19.13 | *** join/#htc-linux Rob2223 (~Miranda@p4FFF0E4F.dip.t-dialin.net) |
03:23.05 | WisTilt2 | jonpry, where in pm core did you code the userwakelocks you mentioned earlier? |
03:26.07 | jonpry | i did regular wake locks. i just looks at userwakelock code and it is attribute kind of stuff, ie show and store implementation but they are never registered afaict. i searched all code and its like nothing in that file is ever referenced. same way on 27 so i guess userwakelocks are just dead code? |
03:32.54 | WisTilt2 | ok i see whats going on but dont know where to look to fix it yet. after unlock we're getting a suspend request from something, however, i traced the userland timer value which is 5 seconds for the unlock screen and that timeout is still working. in more simple terms, if you unlock immediately, you have the remaining time from the 5secs to hit power button otherwise it starts all over again. |
03:33.47 | WisTilt2 | the remaining time from the 5secs is still available even after it hits sleep after unlocking |
03:35.38 | WisTilt2 | this is strange also, you actually have to wait for it to hit full sleep before waking it up within the remaining 5secs timeout. |
03:36.06 | WisTilt2 | would it have anything to do with the sleep_update i see is still running? |
03:43.36 | jonpry | i'm not sure. what i don't understand is why the act of unlocking it triggers anything |
03:49.29 | WisTilt2 | before unlock the default 5 seconds timeout is running. after unlock, timeout gets changed to whatever the user has the screen timeout set to. I think that's where we aren't getting that new value or something else that is requesting suspend is the problem. |
03:49.44 | jonpry | as i recall there was some kind of thing in kernel/power that would check for wakelocks before performing a suspend but when i put in the stuff i didn't see it |
03:53.44 | jonpry | oic |
03:57.27 | WisTilt2 | i dont see anything in the current power code that even checks user wakelocks like it is done in .27 |
03:57.45 | jonpry | ah its in freezer |
04:02.03 | jonpry2 | my stupid internet |
04:02.11 | jonpry2 | anyways booting up and testing now |
04:02.38 | jonpry | i think it only gets checked in process.c |
04:04.03 | jonpry2 | no go |
04:04.52 | WisTilt2 | it looks like nothing in userwakelock.c is being called |
04:05.17 | jonpry2 | is that empirical or theoretical |
04:05.34 | WisTilt2 | this should all be happening in suspend_prepare shouldn't it? |
04:05.47 | jonpry2 | where is that? |
04:05.58 | WisTilt2 | in suspend.c |
04:06.56 | jonpry2 | nah, the freeze is supposed to cause an abort there |
04:06.58 | WisTilt2 | i dont think this is where we should be looking though. suspend isnt the problem, its either a wakelock or lack of being seen, or something else thats triggering that request suspend |
04:07.21 | jonpry2 | i'm pretty sure its the freezer |
04:07.38 | jonpry2 | it was missing code, and now i am having trouble integrating the logic properly |
04:07.44 | WisTilt2 | which file? |
04:07.49 | jonpry2 | process.c |
04:08.06 | WisTilt2 | in try to freeze? |
04:09.24 | jonpry2 | suspend_prepare is still doing something like: if (suspend_freeze_processes()) { |
04:09.24 | jonpry2 | error = -EAGAIN; |
04:09.37 | jonpry2 | yeah? |
04:09.45 | jonpry2 | yeah try to freeze |
04:11.09 | WisTilt2 | no, its error = suspend_freeze_processes(); |
04:11.09 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
04:11.09 | WisTilt2 | if (!error) |
04:11.09 | WisTilt2 | return 0; |
04:11.51 | jonpry2 | thats interestinf |
04:14.31 | jonpry2 | other than the possible negation of logic which is suspect. that can't return. processes need to be thawed |
04:16.25 | WisTilt2 | yeah and it should only thaw when -EAGAIN which we dont have |
04:16.52 | WisTilt2 | should be something like this-> |
04:16.53 | WisTilt2 | if (suspend_freeze_processes()) { |
04:16.54 | WisTilt2 | error = -EAGAIN; |
04:16.54 | WisTilt2 | goto Thaw; |
04:16.54 | WisTilt2 | } |
04:19.56 | jonpry2 | hrm. i guess that is fine then |
04:20.10 | jonpry2 | it thaw succeeds, then it falls through to thaw |
04:20.18 | jonpry2 | er freeze succeeds |
04:22.33 | jonpry2 | your sure that has_wake_lock(WAKE_LOCK_SUSPEND) would return true during this period where its going to sleep? |
04:24.50 | WisTilt2 | are you talking in wakelock.c? |
04:25.04 | jonpry2 | yeah |
04:25.58 | jonpry2 | the kernel pm stuff above that is looking pretty good to me. not what you have but with patches i just did |
04:28.50 | jonpry2 | http://pastebin.com/z1anjd2P |
04:28.51 | WisTilt2 | that should return false actually at the point we're talking about. if it was true we'd be seeing suspend abort but we're not, just seeing normal request suspend |
04:33.24 | jonpry2 | i guess i am confused. if theres no wakelock then why do we expect the phone to not sleep? |
04:35.00 | jonpry2 | i like this: Wake up in 4 seconds |
04:36.42 | WisTilt2 | if (has_wake_lock(WAKE_LOCK_SUSPEND)) - this is kind of illogical but it means to not go into suspend |
04:37.14 | WisTilt2 | we're not actually seeing that with unlock, i dont see it in your log either |
04:39.33 | WisTilt2 | your logs look like its not going right back into sleep when you unlock? or maybe cpu is slower than mine because im seeing several seconds in your logs where mine are 1.2s nearly every time. |
04:41.59 | jonpry2 | so what should be in the log regarding the wakelock? |
04:43.28 | jonpry2 | there is some 39'sh power code on android.git |
04:43.40 | WisTilt2 | there wont be anything for the unlock screen normally |
04:44.31 | jonpry2 | so right after it unlocks we should get powermanager |
04:47.23 | WisTilt2 | i really don't know to be honest. kernel pm has already done its thing by the time unlock screen is up so powermanager in android should be handling everything from that point shouldn't it? |
04:47.37 | jonpry2 | lets just get this: http://android.git.kernel.org/?p=kernel/tegra.git;a=tree;f=kernel/power;h=59c7c6fef8acd6e8eb7780536dad53ee88be6f87;hb=refs/heads/android-tegra-2.6.39 |
04:49.42 | WisTilt2 | this converts suspend/idle to syscore_ops, arent we already doing that? |
04:51.01 | jonpry2 | i don't understand |
04:51.33 | jonpry2 | that is just somebody else who knows what they are doing patching 39 pm with android crap. |
04:52.22 | jonpry2 | i just applied it. really they only had like 1 more line than i did. must be a good one |
04:52.34 | WisTilt2 | worth a try. i see several things changed in this code from what we have now. |
04:53.17 | WisTilt2 | only on process.c? |
04:53.33 | jonpry2 | some of its cosmetic |
04:54.17 | jonpry2 | booting... |
04:55.21 | jonpry2 | theres one change from process that looks potentialy important. and some changes to wakelocks regarding time. its possible the kernels new concept of time is blowing us out of the water |
04:57.22 | jonpry2 | same thing |
04:58.06 | WisTilt2 | was that with all those files or just process |
04:58.26 | jonpry2 | used the whole lot. but most had no changes |
04:59.31 | WisTilt2 | i just had a thought, let me check something... |
04:59.58 | jonpry2 | it kind of looks from the history that they didn't fix it either. |
05:00.32 | WisTilt2 | so they're seeing the same issue? |
05:01.11 | jonpry2 | not sure, but there are lots of edits to wakelock which basically has not changed in 2 years |
05:02.09 | WisTilt2 | you still have it booted on your phone? |
05:03.00 | jonpry2 | yeah |
05:03.34 | WisTilt2 | put it in sleep then hit the end key to start wake followed by the menu key and see if it still does it |
05:04.26 | jonpry2 | yes |
05:04.42 | WisTilt2 | menu key unlocking it though? |
05:04.56 | jonpry2 | end menu end gets it open |
05:05.12 | WisTilt2 | without it going back to sleep? |
05:05.27 | jonpry2 | goes to sleep after menu. second end is awake and unlocked |
05:05.39 | *** join/#htc-linux Raymonddull (~raymonddu@24-236-171-67.dhcp.monr.mi.charter.com) |
05:06.13 | WisTilt2 | you on a regular system.img now or still on our previous tls one? |
05:06.21 | jonpry2 | old one |
05:06.51 | WisTilt2 | ok brb, need to try something |
05:07.13 | jonpry2 | i pushed this new wakelock stuff. it works and is probably done better than mine |
05:12.37 | WisTilt2 | booting now with fingers crossed |
05:12.51 | jonpry2 | what is the theory? |
05:13.54 | WisTilt2 | i disabled the unlock screen to see if it goes right back to sleep when resuming already unlocked. |
05:15.21 | WisTilt2 | i initially was thinking it was something with msm_ts or tssc but since buttons did same thing that blew that theory |
05:16.01 | jonpry2 | and this new thing is to test..? |
05:17.30 | WisTilt2 | no unlock screen now so waking up this will tell us if its related to the unlock process or not |
05:18.50 | WisTilt2 | works like a champ. wakes fine every time now |
05:19.57 | WisTilt2 | waking every time and ive done it around 20 times now |
05:21.24 | jonpry2 | i still don't get it |
05:23.34 | WisTilt2 | jonpry, i did another test on my other phone. this is interesting... i used same kernel on both phones but the 2nd one i switched to the system.img with tls mod in it. unlock screen is still enabled and unlocking works perfect on it every time. figure that one out. sounds like tls is needed? |
05:24.14 | WisTilt2 | so tls and unlock screen or regular system with unlock screen disabled |
05:24.15 | jonpry2 | go to phone status and check the kernel :p |
05:24.43 | jonpry2 | maybe different version of android build? i suspect this could be caused by old libhardware or something |
05:25.42 | jonpry2 | this stuff still happens if i have usb plugged in |
05:27.42 | WisTilt2 | i already rebooted both phone and trying same setup with the kernel off your tree |
05:27.49 | WisTilt2 | you want the android build number? |
05:28.06 | jonpry2 | not really |
05:28.15 | jonpry2 | i want it to work :p |
05:28.47 | *** join/#htc-linux dobrin (~dobrin@85.91.150.26) |
05:28.55 | WisTilt2 | ok works perfect with this kernel also on both phones |
05:29.32 | jonpry2 | hmm |
05:29.58 | WisTilt2 | yep 10 times on both phone 100% working |
05:29.59 | jonpry2 | so my kernel works fine on both your android builds? |
05:30.03 | WisTilt2 | yes |
05:30.14 | jonpry2 | both phones have lock screen enabled? |
05:30.16 | WisTilt2 | im running the one off the tree as you compiled it |
05:30.54 | WisTilt2 | no, one phone has normal system.img with unlock screen disabled, the other is our tls system.img with unlock screen still enabled. |
05:31.15 | jonpry2 | 2.6.39-g40eec0f #60? |
05:31.27 | jonpry2 | well i have the tls image and it doesn't work |
05:31.35 | jonpry2 | but mine is frx05 |
05:31.42 | WisTilt2 | yep thats the same kernel |
05:32.19 | WisTilt2 | both my images are frx06. mine with tls i built off 06 also |
05:33.15 | jonpry2 | i really don't think it has anything to do with tls |
05:33.42 | WisTilt2 | but, my image without tls when i enable unlock screen it does the sleep deal again |
05:34.12 | jonpry2 | were these images built with the same manifest? |
05:34.23 | WisTilt2 | yes exactly |
05:34.32 | jonpry2 | different sd card then |
05:34.41 | WisTilt2 | only diff was the added bionic and hooks |
05:34.54 | jonpry2 | i just don't buy it |
05:35.45 | WisTilt2 | diff sd card? dont follow |
05:36.14 | jonpry2 | speed i think. if it can survive some critical time period the wakelock will get setup |
05:36.22 | WisTilt2 | also, i just put both phone to sleep for 3 minutes and they both worked fine still. |
05:36.42 | WisTilt2 | both sd cards are 8GB class 4 kingstons |
05:37.20 | WisTilt2 | why would disabling unlock screen fix it though? |
05:37.50 | jonpry2 | so why doesn't my phone work? i have absolutely no idea what conclusions can be drawn from having the unlock screen disabled |
05:38.26 | jonpry2 | and tls is like 3 lines of code when it comes down to it. they don't make the phone sleep or not sleep. they make it crash like a ton of bricks |
05:38.33 | WisTilt2 | i have an old 2GB no class card. let me put the setup with the unlock screen enabled and tls image and see, then ill try the other setup on same card |
05:40.48 | WisTilt2 | btw my system build is full_msm-eng 2.2.1 MASTER eng.root.20110520.113203 test-keys |
05:41.56 | jonpry2 | mine is full_msm-eng 2.2.2 FRX05 eng jon.20110514.194143 test-keys |
05:42.09 | jonpry2 | interesting fxr06 you have there |
05:42.14 | WisTilt2 | ok booting test #1. i also noticed that on both phones now the panel looks like it should when shutting down and coming back up. |
05:42.58 | WisTilt2 | hmm. i built mine off the current xdandroid tree |
05:43.23 | jonpry2 | must sleep. ttyl. i really think your chasing ghosts here. you didn't use a manifest. have to init -b sdlakjslkjda -m aslkdjalskjd |
05:45.06 | WisTilt2 | repo init -u git://gitorious.org/xdandroid/manifest.git -b froyo |
05:45.13 | WisTilt2 | thats what im using |
05:45.51 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-69-159.dynamic.mnet-online.de) |
05:58.59 | *** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@94.52.236.39) |
06:26.17 | *** join/#htc-linux MacDrunk (~marper@201.165.134.139) |
06:41.24 | *** join/#htc-linux dekar__ (~dekar@drms-590ed7be.pool.mediaWays.net) |
07:32.10 | *** join/#htc-linux helicopter88 (~helicopte@host117-115-dynamic.13-79-r.retail.telecomitalia.it) |
08:51.06 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
08:57.06 | *** join/#htc-linux helicopter88 (~helicopte@host117-115-dynamic.13-79-r.retail.telecomitalia.it) |
09:20.02 | *** join/#htc-linux khorben_ (~dont@2002:53ec:d9a1:1:221:28ff:fe14:b106) |
09:26.43 | *** join/#htc-linux rajkosto (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs) |
09:40.44 | *** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net) |
09:41.00 | *** join/#htc-linux ORi| (~ORi@91.181.186.58) |
10:08.06 | *** join/#htc-linux |Jeroen| (~jeroen@d5152B25B.access.telenet.be) |
10:18.48 | *** join/#htc-linux mastermerlin (~Adium@p4FEE54EB.dip.t-dialin.net) |
10:19.08 | *** join/#htc-linux mastermerlin1 (~Adium@p4FEE54EB.dip.t-dialin.net) |
10:27.17 | *** join/#htc-linux MacDrunk (~marper@201.165.123.122) |
10:42.03 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
11:06.28 | *** join/#htc-linux _twitch (~burning_a@64.112.96.58.static.exetel.com.au) |
11:06.42 | *** join/#htc-linux n0psl3d (~aefsefaef@host86-180-160-182.range86-180.btcentralplus.com) |
11:20.00 | dcordes | hi ! |
11:30.16 | *** join/#htc-linux XirXes (~xirxes@71-35-197-137.slkc.qwest.net) |
11:33.58 | *** join/#htc-linux gauner1986 (~Miranda@p508C791B.dip.t-dialin.net) |
11:48.29 | *** join/#htc-linux XirXes (~xirxes@71-35-197-137.slkc.qwest.net) |
11:49.39 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
11:55.45 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
12:01.29 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
12:11.30 | *** join/#htc-linux LordDeath__ (~LordDeath@cable-81-173-166-52.netcologne.de) |
12:12.19 | *** join/#htc-linux rzk_ (~rzk@89-178-102-49.broadband.corbina.ru) |
12:33.01 | *** join/#htc-linux n00fy (~n00fy@41.30.231.195) |
12:33.22 | n00fy | Hi, can I install linux on an htc snap running wm6.1? |
12:33.59 | dcordes | [[Snap]] |
12:33.59 | unilinky | http://htc-linux.org/wiki/index.php?title=Snap |
12:34.16 | dcordes | it's unknown to wiki :( |
12:34.29 | dcordes | n00fy: can you add some initial info ? |
12:36.35 | *** join/#htc-linux ppkko (6fffac50@gateway/web/freenode/ip.111.255.172.80) |
12:37.42 | n00fy | dcordes, meh |
13:03.46 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
13:04.33 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
13:19.05 | *** join/#htc-linux |Jeroen| (~jeroen@d5152B25B.access.telenet.be) |
13:19.29 | *** join/#htc-linux DJWillis (~djwillis@cpc3-bath5-2-0-cust220.aztw.cable.virginmedia.com) |
13:26.04 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
13:34.24 | *** join/#htc-linux helicopter88 (~helicopte@host117-115-dynamic.13-79-r.retail.telecomitalia.it) |
13:54.14 | *** join/#htc-linux icydragon6666 (~icydragon@HSI-KBW-095-208-165-211.hsi5.kabel-badenwuerttemberg.de) |
13:54.24 | *** part/#htc-linux icydragon6666 (~icydragon@HSI-KBW-095-208-165-211.hsi5.kabel-badenwuerttemberg.de) |
13:56.30 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
14:01.28 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
14:01.29 | *** join/#htc-linux jon_ (~jon@199.85.236.239) |
14:06.13 | *** join/#htc-linux n0psl3d (~n0psl3d@host86-180-160-182.range86-180.btcentralplus.com) |
14:27.51 | *** join/#htc-linux Segnale007 (~Segnale00@ppp-142-51.26-151.libero.it) |
14:49.57 | *** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@94.52.236.39) |
15:06.31 | *** join/#htc-linux mastermerlin (~Adium@p4FEE54EB.dip.t-dialin.net) |
15:15.20 | *** join/#htc-linux dobrin (~dobrin@85.91.150.26) |
15:32.03 | *** join/#htc-linux dobrin (~dobrin@85.91.150.26) |
15:32.26 | *** join/#htc-linux mastermerlin (~Adium@p4FEE54EB.dip.t-dialin.net) |
15:52.20 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
15:53.05 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
16:04.26 | *** join/#htc-linux icydragon6666 (~icydragon@HSI-KBW-095-208-165-211.hsi5.kabel-badenwuerttemberg.de) |
16:04.33 | *** part/#htc-linux icydragon6666 (~icydragon@HSI-KBW-095-208-165-211.hsi5.kabel-badenwuerttemberg.de) |
16:09.21 | *** join/#htc-linux KJ (575676e3@gateway/web/freenode/ip.87.86.118.227) |
16:21.33 | Guest56290 | is there peopl in here |
16:21.50 | arrrghhh | no |
16:23.11 | Guest56290 | does anyone have knownledge about why this new XDandroid doesnt full load without the lancherpro that can be download on the phone directly |
16:23.30 | arrrghhh | this channel is for kernel development |
16:23.50 | arrrghhh | you don't seem interested in that, sounds like you have the wrong room and an ancient build. |
16:23.57 | arrrghhh | no 'new' version of XDAndroid has LauncherPro. |
16:24.19 | Guest56290 | I downloaded it directly from this site |
16:24.39 | arrrghhh | htc-linux.org? |
16:24.47 | Guest56290 | no updateds located in archive or by XDA site |
16:24.57 | arrrghhh | .... |
16:26.41 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
16:27.36 | Guest56290 | the versions are not for touch pro 2 |
16:28.02 | arrrghhh | you should refresh the web page that you're one. |
16:28.04 | arrrghhh | on* |
16:28.28 | *** join/#htc-linux TreeEater (~TreeEater@94.159.197.219) |
16:30.46 | Guest56290 | the kernel on the site is for different mobile types |
16:31.10 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
16:31.27 | Guest56290 | 2.2 froyo does not work with out 2 updates |
16:32.46 | Guest56290 | .net and fireware both done but the laucherpro is not executing in the linux |
16:39.57 | *** join/#htc-linux jon_ (~jon@199.85.236.239) |
16:40.17 | arrrghhh | he'll never find the chat again. |
16:41.09 | TreeEater | poor guy |
16:46.04 | jon_ | is there some way to get rid of a pointer cast warning without casting it? |
16:46.33 | phh | :D |
16:46.41 | jon_ | this is important |
16:47.01 | jon_ | :p |
16:47.43 | jon_ | its impossible to know the type of the pointer i am assigning. so i can't cast to it |
16:49.14 | *** join/#htc-linux balans (~barry@82-170-217-205.ip.telfort.nl) |
16:51.32 | jon_ | so i want like (ireallymeanit) cast |
16:51.55 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
16:54.28 | *** join/#htc-linux DJWillis (~djwillis@cpc3-bath5-2-0-cust220.aztw.cable.virginmedia.com) |
17:18.11 | *** join/#htc-linux helicopter88 (~helicopte@host117-115-dynamic.13-79-r.retail.telecomitalia.it) |
17:19.57 | *** join/#htc-linux toastcfh (~toastcfh@29-37.200-68.tampabay.res.rr.com) |
17:21.54 | *** join/#htc-linux toastcfh (~toastcfh@unaffiliated/toastcfh) |
17:25.27 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
17:32.40 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39) |
17:34.30 | *** join/#htc-linux mastermerlin (~Adium@p4FEE54EB.dip.t-dialin.net) |
17:39.20 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
17:44.45 | *** join/#htc-linux mes (~mes@S010600259c411dd3.gv.shawcable.net) |
17:45.16 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-69-159.dynamic.mnet-online.de) |
17:55.41 | *** join/#htc-linux balans2 (~Gebruiker@82-170-217-205.ip.telfort.nl) |
17:56.30 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
17:58.46 | *** join/#htc-linux LargePrime (~LargePrim@173-108-127-24.pools.spcsdns.net) |
17:59.46 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
18:05.49 | *** join/#htc-linux XirXes_ (~xirxes@71-35-197-137.slkc.qwest.net) |
18:06.07 | *** join/#htc-linux rpierce99_ (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
18:06.12 | *** join/#htc-linux mastermerlin1 (~Adium@p4FEE54EB.dip.t-dialin.net) |
18:06.42 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
18:06.56 | *** join/#htc-linux Edgan (edgan@okcforum.org) |
18:08.39 | *** join/#htc-linux kysse (ville@2001:470:27:7ca::3) |
18:09.02 | *** join/#htc-linux c00lfon (lkula@irc6.pl) |
18:09.13 | *** join/#htc-linux bartman` (~bart@2607:f2c0:a000:175:2e0:81ff:fe47:3d01) |
18:09.32 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
18:15.25 | *** join/#htc-linux infernix (nix@unaffiliated/infernix) |
18:15.49 | *** join/#htc-linux j0ker (46b55762@gateway/web/freenode/ip.70.181.87.98) |
18:16.12 | j0ker | hello, i would like to ask a question... |
18:16.29 | j0ker | can i get linux on the htc freestyle? |
18:16.29 | helicopter88 | ask |
18:16.32 | arrrghhh | ohgod |
18:16.35 | arrrghhh | no dude |
18:16.45 | arrrghhh | it's BREW. you can't. |
18:16.48 | j0ker | can i do anything with it? |
18:16.58 | arrrghhh | might make a good frisbee |
18:17.04 | j0ker | lol |
18:17.05 | helicopter88 | lol |
18:17.22 | gauner1986 | i'd play a game |
18:17.45 | arrrghhh | hackey-sack? |
18:18.05 | gauner1986 | oh yeah :) |
18:18.22 | arrrghhh | lol |
18:20.18 | *** join/#htc-linux programmer8922 (~Evan@67.219.164.162) |
18:20.34 | j0ker | ok, can i get linux on an iphone 2g? |
18:21.03 | arrrghhh | maybe, but read the topic of this channel. |
18:21.11 | j0ker | yaa, i know |
18:21.25 | j0ker | ok, i'll go else where |
18:26.45 | *** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net) |
18:27.55 | TreeEater | can I get linux on my nokia 5110? |
18:29.18 | *** join/#htc-linux toastcfh (~toastcfh@29-37.200-68.tampabay.res.rr.com) |
18:31.36 | bioterror | TreeEater, sure |
18:32.15 | TreeEater | sorry, I should talk about nonesense like this in the chat room :) |
18:32.20 | *** join/#htc-linux DJWillis (~djwillis@cpc3-bath5-2-0-cust220.aztw.cable.virginmedia.com) |
18:34.03 | *** join/#htc-linux rob_w (~bob@ppp-93-104-167-36.dynamic.mnet-online.de) |
18:39.48 | jon_ | whats wrong with BREW? |
18:46.22 | *** join/#htc-linux kiozen (~kiozen@ppp-93-104-69-159.dynamic.mnet-online.de) |
18:48.35 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
18:51.12 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
18:56.59 | *** join/#htc-linux jon_ (~jon@199.85.236.239) |
18:59.32 | *** join/#htc-linux Rob2222 (~Miranda@p4FFF0E4F.dip.t-dialin.net) |
19:26.32 | *** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com) |
19:28.37 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
19:29.01 | *** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring) |
19:36.54 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
19:40.16 | *** join/#htc-linux toastcfh (~toastcfh@unaffiliated/toastcfh) |
19:48.00 | *** join/#htc-linux toastcfh (~toastcfh@29-37.200-68.tampabay.res.rr.com) |
19:52.47 | *** join/#htc-linux LargePrime (~LargePrim@173-108-50-145.pools.spcsdns.net) |
19:54.45 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
19:54.56 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
20:07.03 | *** join/#htc-linux MacDrunk (~marper@201.165.123.122) |
20:10.58 | *** join/#htc-linux ShapaTank (~ShapaTank@cpe-24-24-202-60.socal.res.rr.com) |
20:15.19 | *** join/#htc-linux surgex (surge@pool-98-118-157-221.bflony.fios.verizon.net) |
20:29.35 | *** join/#htc-linux MacDrunk (~marper@201.165.123.122) |
20:47.42 | *** join/#htc-linux RussellAlan (~R.Alan@ppp-70-249-144-71.dsl.rcsntx.swbell.net) |
20:47.53 | *** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net) |
20:48.11 | RussellAlan | Hello hello, I am working on a tilt 8925 (kaiser) i did the hardspl, then radio update |
20:48.20 | RussellAlan | then was looking to flash a rom without sdcard |
20:48.44 | RussellAlan | so i downloaded Incubus26J's rom and kaisimg-panel****tilt**.nbh |
20:48.46 | RussellAlan | and flashed it |
20:49.03 | RussellAlan | now the phone boots into the first linux screen although there are no files to be loaded |
20:49.10 | arrrghhh | this isn't a room for WinMo help dude |
20:49.28 | RussellAlan | correct |
20:49.32 | RussellAlan | this is linux |
20:49.58 | arrrghhh | oh kaiser can flash |
20:50.00 | arrrghhh | i forgot |
20:50.03 | arrrghhh | dunno who's going to help you tho |
20:50.24 | RussellAlan | pretty much, it is looking for files which arent found. |
20:51.12 | WisTilt2 | hey arrrghhh, do you know if the current frx06 source on the git repo is actually current? driving me nuts here, i started from scratch again doing repo init, sync, etc., and i still show 2.2.1 so i dont know wth im doing wrong now. |
20:52.47 | arrrghhh | hrm |
20:52.50 | arrrghhh | it should be up to 2.2.2 |
20:52.57 | arrrghhh | but it's not up to date with all the newest test stuffs |
20:53.00 | arrrghhh | are you pulling the master? |
20:53.05 | arrrghhh | or did you specify |
20:53.20 | WisTilt2 | im doing this--- |
20:53.33 | WisTilt2 | repo init -u git://gitorious.org/xdandroid/manifest.git -b froyo |
20:53.33 | WisTilt2 | $ repo sync |
20:53.41 | arrrghhh | seems right to be |
20:54.13 | arrrghhh | s/be/me/ |
20:54.15 | emwe | WisTilt2: heyho. saw your message in the logs regarding disabled that disabled pcom ISR just before i left. good to know. thx. |
20:54.17 | WisTilt2 | thats what ive done forever but testing with jonpry last night appears i have wrong system. |
20:54.19 | arrrghhh | and yea, that's correct. |
20:54.35 | *** join/#htc-linux LargePrime (~LargePrim@184-205-87-51.pools.spcsdns.net) |
20:54.52 | WisTilt2 | emwe: yeah i think that fixed it. i still have 1 phone running it since you committed it and still no problem. |
20:56.17 | *** join/#htc-linux GNUtoo (~GNUtoo@host148-3-dynamic.244-95-r.retail.telecomitalia.it) |
20:56.40 | WisTilt2 | emwe, one thing that patch did though i think is prevented usb quick detect from working due to no interrupt possibly. i move the usb status down in the sleep section outside the IF test and it detects immediately when in sleep, just doesnt detect immediately when already awake now. |
20:57.11 | emwe | yeah, exactly. instant plug notification is gone. |
20:57.38 | emwe | except for the sleep case. when the further would work though, no need for the exit sleep one :/ |
20:57.43 | jonpry | hi WisTilt2 |
20:58.12 | WisTilt2 | emwe: in any case, your patch fixed the problems completely at least on our 300's |
20:58.47 | emwe | WisTilt2: then likely on all others. there was a lot of reports in the autobuild page comments. we'll have to revisit that later then. |
20:59.09 | WisTilt2 | hey jonpry. any more luck? im about to give up on this system.img crap, still 2.2.1 even though im pulling it correctly from the tree. |
20:59.48 | jonpry | its init -m something |
20:59.48 | jonpry | arrrghhh probably knows |
20:59.57 | arrrghhh | he's using the correct command |
21:00.09 | arrrghhh | repo init -u git://gitorious.org/xdandroid/manifest.git -b froyo |
21:00.35 | jonpry | repo init -m xdandroid-2.2.2-manifest.xml |
21:00.44 | jonpry | repo init -u git://gitorious.org/xdandroid/manifest.git -b froyo -m xdandroid-2.2.2-manifest.xml |
21:00.50 | jonpry | for the whole deal |
21:00.50 | WisTilt2 | so question is, why with the build im using that has the tls and hooks.h changes does unlock not cause sleep? something changed somewhere. |
21:01.20 | WisTilt2 | ok ill try that. |
21:01.45 | emwe | i think several changes have gone into froyo branch since FRX06 |
21:01.57 | WisTilt2 | once i get 2.2.2 where i can do the same changes as last night, we can see if we're wasting time or not |
21:02.50 | jonpry | well it still doesn't work on my phone with or without tls. i am trying to boot a stock frx06 atm |
21:03.05 | arrrghhh | are you guys making userland changes? |
21:03.18 | WisTilt2 | did you make the hooks.h change also? |
21:03.53 | jonpry | no i didn't change anything |
21:05.05 | WisTilt2 | i mean to try to see if it fixes it like i was doing last night. tls file change and the change we made to hooks.h |
21:06.09 | jonpry | i have been using the tls mods the whole time. i never went back |
21:06.41 | jonpry | this frx06 is not working at all for me. take like 10 minutes to wake up. buttons won't respond. random hangs |
21:07.18 | WisTilt2 | well im now getting the 2.2.2 stuff so ill build it and test like last night and see if anything changes. |
21:07.37 | jonpry2 | acore force close |
21:07.41 | emwe | and i just updated from .27 rhod panel to .35 and i won't get it wake again... what is all this rhod panel madness.... |
21:07.59 | WisTilt2 | btw, i dl'd the frx06 system.ext2 and .39 kernel works nice on it except for that unlock sleep problem still happening. |
21:08.00 | emwe | <4>[ 328.569366] msmfb_pan_display timeout waiting for frame start, 146 1 |
21:08.41 | jonpry2 | was there ever a good 35 rhod panel? |
21:08.52 | emwe | well, the one from .27 should work |
21:08.58 | emwe | same i did for topa |
21:09.29 | emwe | acls nand version was there but with all stuff commented. |
21:09.49 | emwe | ok, gotta look tomorrow. gnight everyone! |
21:10.00 | jonpry2 | i got the 25 mar from here: http://files.xdandroid.com/ |
21:10.06 | *** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru) |
21:10.39 | jonpry2 | i had trouble with fb too. wistilt2 changed some timings in the framebuffer then it started working |
21:10.43 | WisTilt2 | jonpry thats the one i dl'd last night also. it takes a couple mins to settle down or you get the fc if you unlock too soon |
21:11.57 | jonpry2 | i fixed almost all compile errors |
21:12.11 | jonpry2 | there is a missing push though. current git will blow up your phone |
21:12.20 | Alex[sp3dev] | emwe: hi |
21:13.24 | jonpry2 | i'm pretty sure the problem is with time. 27 timer.c is probably not working right |
21:16.05 | WisTilt2 | jonpry, you are on to something. i noticed that something is not right timer wise because none of the apps that read cpu freq are seeing any value now, but they do in .27 kernel. |
21:16.42 | jonpry2 | something is also wrong with rtc. i'm pretty sure if you set an alarm it won't wake up the phone. not even a flicker |
21:16.45 | WisTilt2 | its that ludicrous speed fb you have going |
21:18.11 | jonpry2 | the cpu frequency stuff is something else. we are not building with CONFIG_CPU_FREQ. because the arch is missing the flag |
21:19.20 | jonpry2 | at least thats the first problem. api's are probably all changed too |
21:31.08 | jonpry | crash landing at vega? |
21:31.15 | *** join/#htc-linux ftoz (~root@214-151.gtt-net.cz) |
21:31.42 | WisTilt2 | jonpry im still in the long process of getting the whole 2.2.2 stuff. can you look at something for me real quick in your xdandroid source? |
21:31.52 | WisTilt2 | crash landing? |
21:33.24 | WisTilt2 | i think i see why my system.img build fixes the unlock problem, just want to verify your 2.2.2 source |
21:34.04 | jonpry | ok what is it? |
21:35.06 | WisTilt2 | in PowerManagerService.java |
21:35.20 | WisTilt2 | public void preventScreenOn(boolean prevent) { |
21:35.43 | WisTilt2 | mHandler.postDelayed(mForceReenableScreenTask <-- what value you have here? |
21:37.06 | WisTilt2 | frameworks/base/services/java/com/android/server/PowerManagerService.java |
21:37.13 | WisTilt2 | forgot full path sorry |
21:38.35 | jonpry | k onesec |
21:38.56 | jonpry | i did notice that i can see the phone actually unlock and the homescreen become visible before it goes to sleep |
21:39.25 | jonpry | 1000 |
21:41.46 | jonpry | gotta make dinner |
21:42.05 | WisTilt2 | change that to 100 if you feel like it and the unlock/sleep will probably work right. we still need to see why in kernel though. |
21:42.41 | WisTilt2 | ok enjoy dinner, im here all day and we're getting pizza later to go with nascar, which starts shortly. |
21:57.51 | *** join/#htc-linux LargePrime (~LargePrim@108.101.142.42) |
22:05.23 | *** join/#htc-linux ShapaTank (~ShapaTank@cpe-24-24-202-60.socal.res.rr.com) |
22:08.13 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
22:21.52 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
22:27.51 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
22:28.49 | *** join/#htc-linux toastcfh (~toastcfh@unaffiliated/toastcfh) |
22:35.42 | *** join/#htc-linux apt (~apt@rikers.org) |
22:35.43 | *** topic/#htc-linux is Welcome to the HTC Linux project | Community portal & WiKi http://htc-linux.org | For IRC logs, HaRET & kernel mailing lists etc. see http://htc-linux.org/wiki/index.php?title=Contact | The htc-linux.org project is not affiliated with the HTC Corporation | This channel is for development purposes - Join #htc-linux-chat for offtopic |
22:38.09 | WisTilt2 | wth, you can't build 2.2.2 with java version 1.6.0_18? |
22:38.23 | WisTilt2 | says it needs to be 1.5 |
22:40.21 | WisTilt2 | and the current tree appears to be 2.2.2 FRX05 not 06 |
22:45.14 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
22:45.18 | *** join/#htc-linux LordDeath__ (~LordDeath@cable-81-173-166-52.netcologne.de) |
22:45.32 | dcordes | gitorious sucks |
22:46.04 | dcordes | I don't like the web interface. it limits viewable file size and crashes my browsers frequently |
22:47.43 | dcordes | good night |
22:47.53 | jonpry | WisTilt2, 2.2.3 maybe? |
22:47.59 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
22:48.56 | WisTilt2 | no manifest available for 2.2.3 |
22:49.26 | WisTilt2 | did you try changing that value to 100 already? |
22:50.01 | jonpry | no |
22:50.04 | WisTilt2 | current tree has that set at 5000 so dont know why your's has 1000 |
22:50.17 | jonpry | you had me change it sometime ago |
22:51.08 | WisTilt2 | should have been changed to 100 not 1000. that is the only difference with this system.img that is making unlock work so its related to that function somehow |
22:51.29 | jonpry | my plan is to fix rtc |
22:52.22 | WisTilt2 | k. im going to test battery drain fix. this android side is getting me in a bad mood:) |
22:53.25 | jonpry | i'm pretty sure i ended up using the pm.c from 27 mainline that doesn't work on my 210 |
22:53.56 | WisTilt2 | did you add the flush_console i see in the current pm? |
22:54.47 | jonpry | yeah that is not being used atm |
22:56.06 | jonpry | i think its actually lost its mind. i set an alarm and not only did it not wakeup but when i woke it up, the alarm didn't go off |
22:59.46 | jonpry | nm alarm works if you set it for the right days |
23:02.49 | arrrghhh | lol |
23:07.36 | jonpry | WisTilt2, this does not look good for us :( |
23:08.08 | WisTilt2 | rtc no good? |
23:10.58 | jonpry | rtc is fine. no idea what is broke |
23:19.45 | jonpry | the only thing i can think of is to make a series of patches for both .27 and .35 to spew debugging information for comparison |
23:19.45 | jonpry | er39 |
23:20.08 | *** join/#htc-linux jonpry2 (~jon@199.85.236.239) |
23:25.46 | WisTilt2 | if we do that we should decide who's going to compare what so we're not both doing the same thing |
23:26.14 | WisTilt2 | im about to test a pm change for battery drain right now |
23:30.02 | WisTilt2 | jonpry, is this unlock problem, high drain, and the cpu scaling the only critical fixes right now? |
23:31.37 | jonpry | wifi works but not through android. probably just incorrect packaging of modules |
23:32.01 | jonpry | i found some sketchy stuff in timer |
23:47.00 | *** join/#htc-linux MacDrunk (~marper@201.165.123.122) |
23:52.30 | *** join/#htc-linux jonpry (~jon@199.85.236.239) |
23:57.34 | *** join/#htc-linux LargePrime (LargePrime@c-71-238-114-115.hsd1.mi.comcast.net) |