| 00:30.29 | *** join/#htc-linux noobie1 (noobie@5ac6c1e8.bb.sky.com) |
| 00:31.26 | noobie1 | mjeejay - do u have a link to revolution v1.5? |
| 00:38.32 | *** join/#htc-linux cr2_ (~cr2@ip-80-226-0-1.vodafone-net.de) |
| 00:39.09 | cr2_ | Echo31: msleep 0x118 is the only sleep delay i have found for gps |
| 00:39.53 | *** join/#htc-linux noobie1a (noobie@5ac6c1e8.bb.sky.com) |
| 00:39.55 | *** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk) |
| 00:39.56 | noobie1a | mjeejay - do u have a link to revolution v1.5? |
| 00:41.10 | *** join/#htc-linux Markinus (~Miranda@212.255.46.170) |
| 00:45.27 | *** join/#htc-linux mastermerlin (~Adium@p4FEE5DC3.dip.t-dialin.net) |
| 00:50.58 | *** join/#htc-linux romey (9bb2040a@gateway/web/freenode/ip.155.178.4.10) |
| 00:57.12 | *** join/#htc-linux TheDeadCPU_ (~TheDeadCP@ti0064a380-0409.bb.online.no) |
| 00:59.51 | ocm | Anyone know whatsup with cotulla? I haven't seen him around lately |
| 01:00.33 | *** join/#htc-linux dcordes (~oedevel@unaffiliated/dcordes) |
| 01:01.35 | Hunterok | ocm: All ok with him) Just another nickname) |
| 01:01.55 | ocm | oh, and what might that be? If im allowed to know lol |
| 01:02.34 | Hunterok | ocm: I think it will be fair if you'll read the log to check it))) |
| 01:02.48 | ocm | okay, fair enough lol |
| 01:11.59 | *** join/#htc-linux [zozi] (~chatzilla@bl15-64-200.dsl.telepac.pt) |
| 01:15.02 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
| 01:20.05 | *** join/#htc-linux cr2_ (~cr2@ip-80-226-0-1.vodafone-net.de) |
| 01:22.01 | *** join/#htc-linux Unholy (~IceChat7@24.139.90.39) |
| 01:29.22 | *** join/#htc-linux cedesmith (~chatzilla@188.173.15.86) |
| 01:33.00 | cedesmith | read the logs for yesterday and Hunterkll and Rajko bluetooth on CM6 does not need change, i works with CM6 libs if you drop -lpm in init rc as cass said |
| 01:40.55 | *** join/#htc-linux kubi (~Adium@miranda/user/kubi) |
| 01:44.48 | *** join/#htc-linux Willow (~Willow@cpe-173-175-86-45.stx.res.rr.com) |
| 02:11.52 | *** join/#htc-linux tblt (~tblt@corp-nat.corp.tw1.yahoo.com) |
| 02:16.17 | *** join/#htc-linux iDavid (~iDavid@197.0.201.58) |
| 02:25.12 | *** join/#htc-linux ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 02:35.26 | *** join/#htc-linux crawling (crawling@a94-132-179-158.cpe.netcabo.pt) |
| 02:46.27 | *** join/#htc-linux kubi (~Adium@miranda/user/kubi) |
| 03:01.44 | *** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net) |
| 03:04.33 | *** part/#htc-linux ocm (~ocm@189.183.7.64) |
| 03:05.53 | *** join/#htc-linux Rajko (bitrot@wan.rajkonet.info) |
| 03:16.57 | *** join/#htc-linux malloc_ (~ocm@189.183.7.64) |
| 03:20.04 | F22 | hiya WisTilt2 |
| 03:24.32 | *** join/#htc-linux threeagle (~3agle@cpe-76-181-77-22.columbus.res.rr.com) |
| 03:40.31 | WisTilt2 | Hi there F22. i have one of my grandsons spending the night unexpectedly so not going to be around long. any additional info you found testing since last night? |
| 03:41.35 | F22 | meter seems to match the actual volume now just as you and arrrghhh experienced. |
| 03:42.33 | WisTilt2 | is it matching initially or only after you hit vol up/down once? |
| 03:42.37 | F22 | the last time i tested it was dead on for the beginning which is not something either of you experienced from what i understand. i'm going test that bit again now just to see if i can repeat it. |
| 03:43.08 | F22 | i'm just hoping to avoid another crash. |
| 03:43.14 | F22 | those crashes make testing painful |
| 03:44.07 | F22 | btw, my incall problem the other day was related to a bad data.img. deleting it and forcing android to recreate it fixed my incall problem. |
| 03:44.10 | WisTilt2 | yeah really hope arrrghhh can capture some good logs with the crash so we can see whats going on. i am still leaning toward either gsensors or at least an irq problem somewhere. |
| 03:44.29 | F22 | what sort of logs are you looking for? |
| 03:45.40 | WisTilt2 | dmesg output if possible during the crash back to the boot ani screen. then we can at least trace the crash to the function or area thats triggering it. |
| 03:45.59 | WisTilt2 | if its going to boot ani when crashing, dmesg will be intact. |
| 03:46.12 | F22 | ahh. |
| 03:46.27 | F22 | where would you like me to send that? |
| 03:46.51 | WisTilt2 | regarding data.img, yes that seems to fix lots of issues that creep up over time, which is another thing that needs to be fixed. |
| 03:46.58 | *** join/#htc-linux Pohket (~Adium@207-172-112-247.c3-0.rdl-ubr2.trpr-rdl.pa.cable.rcn.com) |
| 03:47.23 | WisTilt2 | you can pastebin link here |
| 03:47.30 | WisTilt2 | Hey Pohket, long time no see |
| 03:48.15 | F22 | agreed. so many things to address...only so much time...i was distracted the other night tracing a wifi issue that seems to be related to a bad init that's floating around. |
| 03:48.28 | Pohket | Hey - been a busy week |
| 03:49.02 | F22 | ok, will do. |
| 03:49.07 | Pohket | Anything new that I've missed? |
| 03:50.20 | WisTilt2 | Pohket you and i need to get back on adsp tables after i finish the lights. i have a new 6125 table that i haven't committed yet but now also have some changes to audiopara file so will do them together. |
| 03:50.38 | Pohket | Would love to do that |
| 03:50.48 | Pohket | Sound's been my biggest thing on this, as you can tell =) |
| 03:51.26 | F22 | I was just telling cr2 how you swooped in from out of the blue and fixed sound earlier Pohket. |
| 03:52.22 | F22 | a lot of people were banging their heads against that in frustration. |
| 03:52.56 | WisTilt2 | Pohnet: the vfe part of the tables needs some work also to get camera working. i think you will be good for that. next week we can hookup and work on them. |
| 03:52.58 | Pohket | Well, I just took what WisTilt2 had said |
| 03:53.30 | F22 | WisTilt2's arrival has been a godsend to this project. :) |
| 03:53.37 | Pohket | And I'll assume that we can go whittle it down to 3 tables instead of 6⦠|
| 03:55.32 | WisTilt2 | Pohket took my "hints" to the audio problem perfectly:) we were unable to really say directly what was wrong until we got our NDA with qcomm ironed out for this stuff. |
| 03:56.13 | Pohket | Yes - the values were all there, it was the order that was off ever so slightly |
| 03:58.47 | *** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring) |
| 03:59.03 | WisTilt2 | F22 is speakerphone starting at level 3 each time you enable it, even after you adjust up or down? |
| 03:59.35 | F22 | hmm...it's still exact, and it started at 4 it looks like. i went up one at the beginning and it went to 5. didn't crash this time though. i was careful to both hold it steady and wait for the volume meter to disappear before pressing it again. |
| 03:59.43 | *** join/#htc-linux bzo (~chatzilla@c-76-126-175-200.hsd1.ca.comcast.net) |
| 03:59.50 | F22 | i then went all the way down. |
| 04:00.00 | WisTilt2 | Pohket yes on the number of tables. actually looks like only 2 will be needed unless we do the tv section also. |
| 04:00.19 | WisTilt2 | image0 and combo are only ones really used. |
| 04:00.27 | F22 | ending call, and calling again. |
| 04:01.21 | bzo | hey there WisTilt2 |
| 04:01.25 | WisTilt2 | i told arrrghhh i thought if you waited until vol meter left the screen before you changed level again it wouldnt crash, at least im seeing that most of the time |
| 04:02.09 | WisTilt2 | hey bzo! you've been scarce or on vacation:) i have some new table changes for you to try with that init code you tried last time we did this. |
| 04:02.13 | F22 | and given that i grabbed this kernel after you called it a night last night i know it was your last one. although i can check to make sure the date-stamp matches my last download if there is any question. |
| 04:02.23 | WisTilt2 | bzo for camera that is of course |
| 04:02.45 | WisTilt2 | F22 that was the last one yes so you're current |
| 04:02.45 | bzo | WisTilt2: just very busy, worst of it should be over now |
| 04:02.54 | bzo | ah, you figured out something new with dsp? |
| 04:03.46 | *** join/#htc-linux JesusFreak316 (~JesusFrea@pool-173-65-109-252.tampfl.fios.verizon.net) |
| 04:04.23 | WisTilt2 | yeah went through the docs in detail for the camera section and made some changes to the 6125 table and task section |
| 04:05.18 | bzo | ok, when do you want to give it a try? |
| 04:05.44 | WisTilt2 | you up to it now? |
| 04:06.36 | bzo | ok, I'll be back in about 5 minutes - have to switch computers |
| 04:06.54 | F22 | hmm...new call...hit the down button, went down to 4 according to logcat, so i think it started at 5 this time. |
| 04:06.58 | WisTilt2 | ill put it together for you |
| 04:07.28 | WisTilt2 | are you going by the phone_handsfree_volx F22? |
| 04:08.01 | F22 | I/AudioHardwareMSM72XX( 1259): Setting in-call volume to 4 (available range is 0 to 5) |
| 04:08.49 | WisTilt2 | the set volume msg isnt in sync with my stuff yet so thats not accurate. only the dump saying phone_handsfree_volx will be what i have it set to |
| 04:09.13 | F22 | ok, i'll shell in and look at dmesg instead. |
| 04:09.30 | WisTilt2 | i think anyway... see if those both match but i think they are off by 1 or 2 |
| 04:10.43 | F22 | [ 8369.948760] msm_setup_audio - Param is: PHONE_HANDSFREE_VOL4 |
| 04:10.52 | F22 | that's the last one i have. i have a 5 before that. |
| 04:11.32 | WisTilt2 | thats it. that will change each time you change volume and that is the actual level being set |
| 04:11.43 | *** join/#htc-linux bzo (~chatzilla@c-76-126-175-200.hsd1.ca.comcast.net) |
| 04:11.51 | F22 | ok, i'll end the call and make another. |
| 04:13.03 | bzo | WisTilt2: ok, ready when you are |
| 04:13.30 | F22 | [ 8792.585266] msm_setup_audio - Param is: PHONE_HANDSFREE_VOL3 |
| 04:13.31 | F22 | [ 8792.585296] Turnin mic bias on 1 |
| 04:13.31 | F22 | [ 8792.585388] --- msm_setup_audio -- 0xe |
| 04:13.31 | F22 | [ 8792.585418] snd_set_volume 0 0 3 |
| 04:13.33 | F22 | we're good |
| 04:14.14 | WisTilt2 | there ya go |
| 04:15.02 | WisTilt2 | bzo ill dump in pm, really dont want it public until its 100% correct. |
| 04:15.05 | F22 | hit the down button, it went to 3 again. But the meter had said it was at 4. |
| 04:15.17 | F22 | so now the meter matches. |
| 04:15.22 | F22 | they're both at 3. |
| 04:16.03 | WisTilt2 | so its off by 1 initially? |
| 04:16.25 | F22 | well it was this time. i can try starting at 1 and see how it goes. |
| 04:16.43 | F22 | the meter seems to remember where i was last time. |
| 04:16.59 | F22 | judging by my previous calls. |
| 04:17.28 | *** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc) |
| 04:17.31 | F22 | i suspect the meter started at 4, while the actual sound was 3. |
| 04:17.44 | F22 | when i hit down, the sound stayed at 3, but the meter dropped to 3. |
| 04:18.47 | F22 | er. hmm...the meter may actually have 6 settings, not 5. |
| 04:19.00 | F22 | i think you mentioned that the other night now that i recall. |
| 04:19.10 | WisTilt2 | yes that is probably part of the problem |
| 04:19.31 | F22 | ok, let me end this call at the very bottom. |
| 04:19.36 | F22 | then i'll make another call. |
| 04:20.50 | WisTilt2 | hopefully meter will still start off high, otherwise the variable im setting for that isnt the correct one. |
| 04:22.14 | Scrizz | is punching kidneys: Gone away for now |
| 04:24.27 | F22 | hmm...volume states 0 to 5. haven't yet made a new call. just getting a feel for the different volume levels. making new call now. |
| 04:24.34 | F22 | ending at volume state 0. |
| 04:24.57 | *** join/#htc-linux Unholy (~IceChat7@24.139.90.39) |
| 04:26.24 | Willow | does anyone know where in haret src to look to make framebuffer fill entire screen every time? |
| 04:26.34 | F22 | starts at volume state 3 |
| 04:30.12 | F22 | something weird happened. phone did not crash, but phone call suddenly ended and now i can't dial. |
| 04:30.32 | WisTilt2 | speakerphone on or off? |
| 04:31.37 | F22 | speakerphone sounded like it was off. |
| 04:31.49 | F22 | funny, i was able to take an incoming call. |
| 04:32.34 | Unholy | what would i have to change to make my kernel overclock to 1.1ghz and beundervolted to 925, i think i know the file i have to modify (freq_table.c), what i dont know is what needs to be changed in the code. im using stock kernel linux_on_wince_htc |
| 04:32.44 | *** join/#htc-linux gpc (~gpc@114-44-5-60.dynamic.hinet.net) |
| 04:33.42 | bzo | WisTilt2: I did fix up some other stuff since we last chatted so hopefully we'll make some more progress today |
| 04:33.59 | WisTilt2 | bzo: im curious if with these changes you make it past that last point from last time. |
| 04:34.11 | WisTilt2 | its so close |
| 04:34.28 | bzo | I did move slightly forward from last time, had to patch on of the graphic libs |
| 04:35.11 | WisTilt2 | F22 were the dial keys still working or just not dialing? |
| 04:35.33 | F22 | bleh, just rebooted. i was hitting redial. |
| 04:35.41 | F22 | not sure if i could manually dial or not. |
| 04:36.03 | WisTilt2 | Pohket btw, on this kernel so you know... rear speaker light now works. green when in speakerphone, red blinking when in any kind of record mode like voice search etc. |
| 04:36.28 | F22 | it would go to the dialing screen, i'd hear the speaker crackle for a brief instant, and then it would say call ended. |
| 04:36.32 | F22 | without ever dialing |
| 04:37.27 | Pohket | I saw that in the code |
| 04:37.35 | Pohket | that I pulled earlier this evening |
| 04:37.56 | Pohket | that's a nice feature though - glad you found those and threw 'em in =) |
| 04:38.05 | bzo | WisTilt2: perhaps gets a little further... mostly more of the same |
| 04:38.08 | WisTilt2 | hopefully another new data.img wont be needed. id really like to know what gets trashed in data to cause all these weird issues. |
| 04:38.24 | WisTilt2 | is it making it to vfetask? |
| 04:38.44 | F22 | will look as soon as android is back up |
| 04:38.54 | F22 | er wait, i manually booted. |
| 04:38.55 | F22 | damn |
| 04:38.57 | Pohket | F22 - the way the code works now, if you're in speakerphone mode |
| 04:38.59 | F22 | should have grabbed it before. |
| 04:39.04 | Pohket | generate a DTMF |
| 04:39.09 | Pohket | the DTMF turns off speaker |
| 04:39.16 | bzo | WisTilt2: no, but it might be going 1 line further in the kernel log |
| 04:39.26 | Pohket | If you hit it off and back on, it will work again |
| 04:39.45 | Pohket | It's part of the way we handle the speaker â basically the playback turns it off when it shouldn't |
| 04:40.05 | bzo | WisTilt2: I think it used to stop at msm_camera: msm_get_stats |
| 04:40.17 | bzo | but it is now printing after that msm_camera: msm_control: rc 0 |
| 04:40.41 | WisTilt2 | bzo so its stopping right at vfetask trying to register or before? |
| 04:41.28 | bzo | the register of vfetask always worked, but it never got to the enable |
| 04:41.38 | bzo | still stopping before that |
| 04:42.09 | bzo | hmm, I am getting a bunch of MetadataDriver errors in logcat which I've never seen before. Wonder what the heck that is? |
| 04:42.58 | WisTilt2 | so vfetask is making it to being registered? |
| 04:43.01 | Willow | would the haret frame buffer be inconsistent in showing at all and in how much is visible if the correct start of physical RAM is not known and an incorrect RAMADDR is set? |
| 04:43.05 | *** join/#htc-linux programmer8922 (~Evan@67.219.166.182) |
| 04:43.34 | F22 | outbound calling working again after reboot |
| 04:44.06 | bzo | WisTilt2: yes, I don't think getting vfetask registered was ever a problem |
| 04:44.29 | Pohket | alright guys - out for the night â see ya 'round |
| 04:44.45 | F22 | thanks for the info Pohket |
| 04:44.48 | F22 | have a good night |
| 04:44.49 | *** part/#htc-linux Pohket (~Adium@207-172-112-247.c3-0.rdl-ubr2.trpr-rdl.pa.cable.rcn.com) |
| 04:44.57 | WisTilt2 | bzo: ok we need to verify something... can you change the vfeCommandQueue from 0x5f6 to anything that is not in the table and see if you crash earlier. |
| 04:45.51 | bzo | WisTilt2: I can try it, but I'm pretty sure vfetask was getting registered even before the tables were fixed |
| 04:45.56 | F22 | odd |
| 04:46.18 | *** join/#htc-linux kernelzilla (~patrick@63-225-208-38.phnx.qwest.net) |
| 04:46.31 | WisTilt2 | bzo ok if thats the case then nm. i was thinking it wasnt registering until table fix |
| 04:47.03 | bzo | seems the only thing needed to register vfetask was passing the string "VFETASK" |
| 04:47.04 | F22 | started at vol 3 went, hit vol up, bar moved to the middle, it went down to vol 2. |
| 04:47.31 | F22 | not sure what starting state of the meter was. |
| 04:47.38 | WisTilt2 | duplicate the new combo stuff to image0 also, along with task to module just in case its trying to use image0 for camera |
| 04:48.06 | bzo | ok |
| 04:49.15 | F22 | hmm...bar in middle is the third of 6 places on the meter, so that matches vol state 2. |
| 04:49.30 | WisTilt2 | F22 so it sounds like meter value isnt taking my write initially. can you hit vol only 1 time then look at dmesg to see if there is a volume write error |
| 04:50.09 | F22 | does it matter whether i go up or down at this point? |
| 04:50.16 | WisTilt2 | no |
| 04:50.29 | WisTilt2 | i just want to see if the 1st write is erroring out |
| 04:50.32 | F22 | ok |
| 04:50.38 | WisTilt2 | it will log that error |
| 04:50.41 | F22 | 1st write after speaker is turned on? |
| 04:50.53 | F22 | so turn off speaker and back on? |
| 04:51.12 | WisTilt2 | that will work yes, write happens with vol up/down though |
| 04:51.24 | bzo | WisTilt2: btw, nothing has changed in the queue_offset_table, right? |
| 04:51.40 | WisTilt2 | basically im writing the new value back to userland variable to match the meter hopefully |
| 04:52.12 | WisTilt2 | bzo: no not from my last commit |
| 04:52.26 | WisTilt2 | only task to module |
| 04:53.09 | WisTilt2 | only difference is all the notes to the right naming the dsp task that each queue belongs to |
| 04:55.33 | F22 | not seeing an error, but i can pastebin what i have. |
| 04:56.55 | WisTilt2 | is this after a crash? |
| 04:57.07 | F22 | no |
| 04:57.11 | F22 | you wanted after a crash? |
| 04:57.43 | WisTilt2 | yes after it reboots back to boot ani |
| 04:57.49 | F22 | ahh... |
| 04:58.46 | F22 | btw, this last time, meter started at 0 where i left it. dmesg said 3 as it should. hit up button once. meter went up to 1. dmesg dropped to 1. |
| 04:58.47 | *** join/#htc-linux Unholy (~IceChat7@24.139.90.39) |
| 04:59.32 | F22 | is that pretty much what you were seeing? |
| 04:59.50 | WisTilt2 | let me try that. |
| 05:00.51 | Willow | Unholy: did you find your answer re: overclocking? I'm sorry I don't have an answer for you...I'm at the beginning stages of porting Linux to HTC Snap Willow and don't even have haret booting the kernel yet |
| 05:01.28 | F22 | i had to draw a little pic of where the bar is at the different levels so i could read it properly. |
| 05:01.34 | bzo | WisTilt2: seems to be the same as last time |
| 05:01.44 | Unholy | not yet still searching. and np keep at it heh |
| 05:02.26 | F22 | 0 is under the speaker, 1 is under the n in In, 2 is between the 2 l's in Call, 3 is under the l in Volume, 4 is under the 3 in Volume, and 5 is a full bar. |
| 05:03.08 | F22 | s/the 3/the e/ |
| 05:03.12 | WisTilt2 | bzo: can you dump your log again so i can refresh my memory |
| 05:04.34 | bzo | http://pastebin.ca/1990847 |
| 05:04.38 | F22 | i'll force the crash now and get you that dmesg if there isn't anything else you want me to do right now while i'm still in the speaker with an adb shell into the phone. |
| 05:04.47 | WisTilt2 | F22: ok i set level all the way down, speakerphone off then on, hit vol up and bar was almost at minimum but sound level was definitely at 3. hit up again and level went up and meter then jumped up about 3/4 way and matched. |
| 05:05.06 | WisTilt2 | looks like 1st write isnt happening |
| 05:06.02 | *** join/#htc-linux UbuCake (~vsrrlua@108.116.55.209) |
| 05:06.26 | F22 | http://pastebin.com/xb9wn3bC <--- not for crash, but for what we were just talking about |
| 05:07.00 | F22 | meter 0->1 dmesg 3->1 |
| 05:07.09 | bzo | WisTilt2: gtg, will probably be on tomorrow night |
| 05:08.01 | *** join/#htc-linux UbeCake (~vsrrlua@108.116.55.209) |
| 05:08.57 | F22 | 0 defined as the bar being filled up to the speaker, and 1 defined as the bar filled up to the "n" in "In-Call" |
| 05:11.30 | WisTilt2 | ok that almost sounds like the in-call value is changing things. level 3 when enabled is obviously happening but jumping down to level 1 can only be coming from userland since it thinks it was at 0 |
| 05:11.43 | F22 | yup |
| 05:12.38 | WisTilt2 | ok i need to go through all the logic in volume again and get the actual variable its using during in-call so we can write to the correct one to match things |
| 05:12.54 | *** join/#htc-linux jhewitt (~chatzilla@76.8.209.180) |
| 05:13.01 | UbeCake | Willow: to get the haret framebuffer working, you need to make sure that you remove all sd cards from your phone BEFORE startint haret. If that doesn't work then you need to free up memory by deleting most of the files in the Windows folder on your phone |
| 05:13.35 | F22 | sounds good. want me to do another test to confirm it's consistent. or have you checked yourself already? |
| 05:14.01 | WisTilt2 | under that same test if you left last volume at highest and then hit down, it should change to level 4 which isnt right |
| 05:14.32 | F22 | makes sense. that's not what was happening before? |
| 05:14.43 | F22 | er now? |
| 05:14.47 | WisTilt2 | i didnt think so but now im confused |
| 05:14.54 | F22 | i can test. |
| 05:15.04 | F22 | ending call at volume 5. |
| 05:15.10 | WisTilt2 | i dont think i ever tried from leaving a call at lowest or highest |
| 05:15.44 | Willow | well I tried taking my sd card out and the framebuffer was still not full screen .. let me try it a couple more times |
| 05:16.00 | F22 | hmmm....somehow my phone turned off. damn bugs. no boot screen either. |
| 05:16.40 | F22 | i wasn't adjusting the volume at the time. |
| 05:17.10 | F22 | my phone had gone to sleep, i hit the power button and it turned off. |
| 05:17.22 | UbeCake | Another thing to try that most people wouldn't think of is make sure your battery door is securely snapped on as that can affect the framebuffer memory |
| 05:17.30 | WisTilt2 | we really need a fast winmo boot for testing, thats the most time consuming part |
| 05:17.35 | F22 | at least i think that's what happened. wasn't expecting that to happen, so wasn't paying a whole lot of attention. just wanted the thing to wake up. |
| 05:17.59 | F22 | agreed on the fast winmo boot. |
| 05:18.55 | WisTilt2 | or get something like grub in there right after hardware inits and bypass winmo altogether for testing |
| 05:19.38 | F22 | :) |
| 05:19.46 | F22 | i'd settle for lilo. :P |
| 05:20.30 | F22 | that time it came up pretty thankfully. |
| 05:20.32 | F22 | back in adroid |
| 05:22.21 | *** join/#htc-linux aoastill (6276a6a4@gateway/web/freenode/ip.98.118.166.164) |
| 05:22.31 | Willow | UbeCake: well, I tried it several more times with my sd card out and the framebuffer still is very inconsistent and never is drawn full screen. I haven't tried deleting the files in the Windows folder yet and I don't quite see the connection of that with running haret. Have you gotten the framebuffer to go full screen? |
| 05:24.13 | aoastill | is this where I come to get help for the android project? |
| 05:24.30 | F22 | interesting. this time: meter: ?->0 dmesg 3->0 wasn't sure where i started though. ending at 5 this time. |
| 05:24.56 | Unholy | aoastill #htc-linux-chat |
| 05:25.23 | aoastill | yeah..... |
| 05:26.28 | Willow | aoastill: if you have a device that has not yet gotten linux to boot on it and you are taking that task upon yourself then this is the place to be so you can bounce ideas off others who may be of some help |
| 05:26.50 | F22 | yup, it worked as expected: meter 5->4 dmesg 3->4 |
| 05:27.16 | F22 | that was in the same call, i exited speakerphone then went back in. i can check with a separate phone call too if you like. |
| 05:28.35 | WisTilt2 | did you hit up or down? |
| 05:28.39 | F22 | down |
| 05:28.44 | F22 | did you want me to hit up? |
| 05:28.57 | WisTilt2 | try up with it already at 5 |
| 05:29.03 | F22 | will do |
| 05:30.23 | UbeCake | Try deleting the nk.exe file from windows folder and if that doesn't get it working then just randomly delete a few more files until it works |
| 05:30.25 | F22 | didn't work |
| 05:30.26 | F22 | no change |
| 05:30.50 | F22 | [ 707.532043] gpiomatrix: unmapped key, 0-1 (35-39) changed to 1 |
| 05:31.31 | *** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey) |
| 05:32.10 | WisTilt2 | that should have move dmesg up to 4 which means in-call variable is the culprit since it was already at 5 so userland never called the volume up function. |
| 05:32.15 | F22 | by that i mean: meter 5->5 dmesg 3->3 |
| 05:32.31 | F22 | dmesg doesn't seem to register a change at all |
| 05:32.34 | WisTilt2 | i can work with that now that we know whats actually happening. |
| 05:32.34 | F22 | will pastebin |
| 05:32.42 | WisTilt2 | it wont |
| 05:32.42 | F22 | ok |
| 05:32.58 | F22 | no need to pastebin that then. |
| 05:33.34 | WisTilt2 | userland is at maximum so it skips calling the up function so my stuff never runs in that state. now i know its logic |
| 05:33.34 | F22 | ok, i should probably get you that crash dmesg now then. |
| 05:33.51 | Willow | UbeCake: I can't delete the nk.exe file and that doesn't make sense anyway because if I could delete it then wince would not boot at all since that it the windows kernel. I'm going to try to find something in the haret source to fix the problem. I'm pretty sure that is where I need to focus although exactly where is the question. |
| 05:34.08 | WisTilt2 | yes if you could. really want to find that crash cause. |
| 05:34.19 | F22 | glad we know what's going with the volume changes now. :) |
| 05:34.43 | WisTilt2 | yes for sure. i can code around that problem. just a logic issue |
| 05:34.50 | *** join/#htc-linux rogue (~rogue@udp220070uds.hawaiiantel.net) |
| 05:35.08 | F22 | i fully understand. |
| 05:35.21 | rogue | Willow: UbeCake is trying to get you to destroy your phone. nk.exe is the Windows kernel. |
| 05:35.37 | F22 | let's see, two things i've been careful not to do...adjust volume more than one before the bar disappears, and move the phone while adjusting. which do i want to change first? |
| 05:36.33 | WisTilt2 | id go with changing volume while in speakerphone and move phone on its side and back to trigger the gsensors and see if that is a problem |
| 05:37.05 | WisTilt2 | that may only be an issue when playing sound though from what ive seen |
| 05:37.21 | rogue | Willow: glad you caught that. Back to lurking (actually was on HTML logs when I saw that.) |
| 05:37.41 | F22 | ok, will put other phone next to my clock radio and turn the thing on. :P |
| 05:37.50 | Unholy | isint there a kitchen for you guy's device, with tha tits pretty easy to cook a bare minimum wm rom, remove some packages i really cant remeber what can be removed right now but its quite easy, also place a haret shortcut in the windows startup folder |
| 05:38.08 | F22 | simply moving the phone around by itself with no significant sound coming through didn't cause a crash in the 20 or so seconds i tried it. |
| 05:39.36 | Willow | rogue: yeah, I'll probably just ignore anything he says unless it makes good sense. I had thought of trying what Unholy suggests but haven't spent enough time with the kitchen to figure out how it all works. |
| 05:40.09 | F22 | crash coming... :D |
| 05:40.26 | F22 | xdandroid screen up |
| 05:41.25 | F22 | speaker crackling, speaker light on back lit. |
| 05:41.40 | Willow | Hey, at least I can say that android never crashes on my device ;D |
| 05:42.20 | F22 | noooo!!!!!!!!!!! it rebooted into winmo on its own. |
| 05:42.52 | WisTilt2 | F22: after the crash log try this image and see if meter and dmesg match now from beginning and when adjusting. |
| 05:43.08 | WisTilt2 | damn, of course. it knew we were trying to log it |
| 05:44.19 | F22 | ok, in win mo right now. will drop in the kernel and go back into android. |
| 05:44.20 | Willow | I did find that I can get a fullscreen framebuffer on haret (well except for a block in the center) if I comment out the call to mmu_trampoline...of course that is not helpful because it could never boot linux without running the trampoline |
| 05:45.36 | *** join/#htc-linux i-Katik (~guru_icq@217.17.163.12) |
| 05:47.33 | *** join/#htc-linux ocm (~ocm@189.183.7.64) |
| 05:49.45 | F22 | ok, new kernel placed, starting haret... |
| 05:51.55 | ocm | F22: what phone are you using? |
| 05:52.04 | WisTilt2 | you might try the speakerphone logs before you force the crash to save time |
| 05:53.23 | WisTilt2 | hopefully level 3 at start matches meter and this up/down issue is fixed so we can move on to this crash problem. |
| 05:53.38 | F22 | right, that's what i was planning. |
| 05:54.10 | WisTilt2 | you oc'd or running standard speed |
| 05:54.51 | F22 | let me turn my radio off first, don't want to increase the odds of it crashing while trying to get the speakerphone logs... :P |
| 05:57.48 | F22 | hmm...did it start at vol 1 or vol 3? is that intentional? i'm seeing both despite never having hit the volume button. |
| 05:57.59 | F22 | first vol 1, then vol 3 |
| 05:58.15 | F22 | exiting speaker, and going back in. |
| 05:58.30 | WisTilt2 | vol 3 is still where it should start |
| 06:00.08 | WisTilt2 | try the minimum or maximum test and see if it jumps to 3 like it should. i dont know where that 1 is coming from. |
| 06:00.15 | F22 | seeing lots of microp-klt |
| 06:00.33 | WisTilt2 | i2c errors? |
| 06:01.25 | F22 | i'll pastebin and you can judge for yourself what is going on. |
| 06:02.06 | F22 | http://pastebin.com/Z56mijw8 |
| 06:02.35 | F22 | note that i never hit the volume button |
| 06:02.41 | WisTilt2 | thats normal. its the autobl setting screen level |
| 06:03.03 | F22 | i'm getting 3 volume level 3's this time. |
| 06:03.15 | F22 | i don't recall seeing that before when starting out. |
| 06:03.16 | WisTilt2 | does that when panel comes up |
| 06:03.39 | F22 | oh, doh. |
| 06:03.47 | F22 | didn't know that |
| 06:04.12 | WisTilt2 | yeah 3 volume and level should be 3 good. up/down should match now hopefully no matter what the level was when you leave then return |
| 06:04.50 | WisTilt2 | it should be 3/3 each time at enable |
| 06:05.29 | F22 | hit down button, meter ?->0 dmesg 3->0 |
| 06:05.41 | F22 | will leave here and exit, then re-enter. |
| 06:05.49 | F22 | speaker that is. |
| 06:05.57 | WisTilt2 | should come up 3/3 hopefully |
| 06:06.29 | WisTilt2 | meter should be at 3 level also |
| 06:07.51 | F22 | ok dmesg is 3. if go up, meter should got to 4 right? not both dropping to 1. |
| 06:07.58 | WisTilt2 | yep |
| 06:08.04 | Willow | this code in asmstuff.S is making me sleepy... I'll catch you all tomorrow. I'll check the irc logs for any belated helpful replies to my previous unanswered questions. g'night |
| 06:08.13 | *** part/#htc-linux Willow (~Willow@cpe-173-175-86-45.stx.res.rr.com) |
| 06:08.49 | F22 | both changed to 1 |
| 06:10.07 | F22 | so no change there it looks like. want me to check if 5+1 still results in no change? |
| 06:10.30 | WisTilt2 | yes try that while i look this over again |
| 06:10.45 | F22 | will do |
| 06:11.18 | WisTilt2 | also check dmesg for any "set volume: error writing" if thats showing up anywhere |
| 06:12.53 | F22 | no change |
| 06:13.02 | F22 | ok, looking... |
| 06:13.04 | WisTilt2 | has to be a writing error on 1st up/down. no other way is that value being missed that i can see. its not taking my level 3 value into userland on 1st write. |
| 06:13.37 | WisTilt2 | but you should see that writing error if thats the case |
| 06:14.57 | F22 | ahh! |
| 06:15.08 | F22 | [ 1421.993713] msm_i2c msm_i2c.0: error, status c8 |
| 06:15.08 | F22 | [ 1421.993804] msm_i2c msm_i2c.0: Error during data xfer (-5) |
| 06:15.08 | F22 | [ 1422.012298] micropklt, i2c write retry |
| 06:15.41 | WisTilt2 | thats not it, thats actually normal occasionally |
| 06:16.15 | WisTilt2 | it will specifically say snd_ioctl set volume: error writing back -- ignoring |
| 06:16.42 | F22 | those are the only times the word error or Error or ERROR appear in the dmesg. |
| 06:17.41 | F22 | nothing with snd and some sort of error on the same line |
| 06:18.12 | WisTilt2 | but when you enable speakerphone both show 3 right, until you hit volume |
| 06:18.25 | F22 | i'm piping it through grep just in case i'm blind and missing something. |
| 06:18.42 | F22 | both what show 3? |
| 06:18.58 | WisTilt2 | handsfree and set volume |
| 06:19.36 | WisTilt2 | or are you using the visual meter to determine its level? |
| 06:19.56 | F22 | yup, both handsfree and set volume are initially at 3 when i hit the speaker button |
| 06:20.17 | WisTilt2 | then up or down those should be following each other |
| 06:20.43 | F22 | i've been making a distinction between the meter and dmesg, which until now i've been basing on the handsfree number. |
| 06:22.24 | WisTilt2 | oh. meter may not graphically be correct yet, although i was hoping it was. as long as set volume and handsfree match then its working like it should. if meter isnt in correct bar level we need to find the variable it uses so graphically things match also. |
| 06:22.41 | F22 | i'm looking through the dmesg to make sure they always matched. |
| 06:23.42 | WisTilt2 | so when you are saying it goes to 1 for example, you're talking about the meter not handsfree against set volume? |
| 06:23.52 | F22 | right |
| 06:24.17 | F22 | before i was saying things like meter 0->1 dmesg 3->1 |
| 06:24.26 | F22 | meter was meter, dmesg was hansfree |
| 06:25.33 | F22 | i based the first number in meter on the last state of the volume when i last exited the speakerphone, or the last time i hit the volume button if i already hit the volume button at least once in speaker. |
| 06:25.50 | WisTilt2 | ok then we're ok and its working correctly. bar is determined from some other variable. i was pulling out what hair i have left because i thought volume and handsfree were not matching lol and its been right all along. |
| 06:26.58 | F22 | that's what i figured. just need to find that variable. |
| 06:27.08 | WisTilt2 | i got ya. ok i just need to dig through libaudio in userland to find how the value for bar is determined and link it somehow |
| 06:27.32 | WisTilt2 | one more question... |
| 06:27.36 | F22 | go ahead |
| 06:28.20 | WisTilt2 | if you leave speakerphone after you turn the level all the way down, then go back to speakerphone does volume level sound like its going back to 3? |
| 06:28.41 | F22 | good question |
| 06:28.49 | WisTilt2 | then hitting up it should go up only 2 levels |
| 06:29.33 | F22 | easy to test, i can't really hear 0 unless my ear is against the phone. |
| 06:30.04 | F22 | setting speaker to 0, exiting, turning radio back on, then turning spaker on. |
| 06:30.10 | F22 | sound good? |
| 06:30.20 | WisTilt2 | yep |
| 06:30.51 | WisTilt2 | it better go to 3 or i quit |
| 06:33.45 | F22 | i can hear it |
| 06:33.56 | F22 | hitting the down button doesn't lower it, but that isn't surprising. |
| 06:34.11 | F22 | going up now. |
| 06:34.23 | F22 | heh, going up lowered the volume |
| 06:34.41 | F22 | makes sense. |
| 06:34.49 | WisTilt2 | it will since it thinks its at 0 so up went to 1 then 2 etc |
| 06:34.50 | F22 | the actual volume is being reset to what's on the meter. |
| 06:34.58 | F22 | yup |
| 06:35.01 | WisTilt2 | once i get that variable we'll be in sync |
| 06:35.12 | F22 | sounds like we have a plan. :) |
| 06:35.18 | F22 | now to get you that log... |
| 06:35.27 | WisTilt2 | so crash the phone time |
| 06:36.08 | F22 | phone crashing... |
| 06:36.42 | F22 | ooh, got a dmesg as it was crashing |
| 06:38.00 | F22 | my adb connection stayed up. |
| 06:38.45 | WisTilt2 | so we're going to get some juicy info during the crash it seems |
| 06:39.28 | *** join/#htc-linux aoastill (6276a6a4@gateway/web/freenode/ip.98.118.166.164) |
| 06:39.52 | *** join/#htc-linux Quickness (Quick@adsl-76-192-35-205.dsl.emhril.sbcglobal.net) |
| 06:40.06 | *** part/#htc-linux Quickness (Quick@adsl-76-192-35-205.dsl.emhril.sbcglobal.net) |
| 06:40.36 | aoastill | looking for help with an HTC touch pro 2 |
| 06:41.16 | F22 | complete dmessage coming right up... |
| 06:41.37 | WisTilt2 | nice |
| 06:43.53 | F22 | http://pastebin.com/pzPXtUZv |
| 06:47.55 | F22 | just a sidenote, speakerphone light is lit, and speakerphone is crackling. |
| 06:48.52 | F22 | but as before, the phone connection got cut during the crash. |
| 06:49.04 | F22 | so that's all consistent. |
| 06:49.27 | WisTilt2 | F22 ill have to go through this in detail tomorrow night but looks like its 3d related. problem started about 1.5 minutes before it actually crashed and hw3d seems to have triggered it then finally ended it. |
| 06:49.45 | F22 | ahhh...interesting... |
| 06:49.49 | F22 | 3d... |
| 06:49.53 | F22 | lol |
| 06:49.55 | WisTilt2 | do you have hw3d enabled in startup |
| 06:50.12 | F22 | checks |
| 06:51.23 | F22 | set cmdline "lcd.density=240 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=2 force_cdma=0 physkeyboard=rhod210 rel_path=andboot" |
| 06:51.53 | F22 | need to up my clock. :P |
| 06:52.09 | WisTilt2 | looks like not. i think its off by default. not 100% that 3d is the problem but looks like it contributed |
| 06:52.40 | WisTilt2 | some runaway code that should be fun tracking down |
| 06:52.59 | WisTilt2 | at least we have a crash log to work with finally |
| 06:53.06 | F22 | yup :) |
| 06:53.57 | F22 | which do you think you'll tackle first? the volume variable? or the crashing issue? |
| 06:54.15 | WisTilt2 | ok i need to hit the sack. thought id be offline long ago with my grandson here tonight but he fell asleep over 3hrs ago so glad we could get this much done. |
| 06:54.20 | WisTilt2 | volume |
| 06:54.27 | F22 | hmm...might also be useful to get a dmessage when pandora while streaming music crashes too, just to compare. |
| 06:54.29 | WisTilt2 | should be easy |
| 06:54.38 | F22 | dmesg |
| 06:54.47 | F22 | i keep saving the file to dmessage, now i'm calling it dmessage. :P |
| 06:54.58 | WisTilt2 | yeah that would be a good crash log also |
| 06:55.35 | F22 | that's a harder one to get. but if i let it sit for a few hours i'm sure it will crash at least once in that timeframe without me doing a thing. |
| 06:55.55 | F22 | and i'll know when the music cuts out.; |
| 06:56.01 | WisTilt2 | does it also just boot back to the ani screen or do a full reboot? |
| 06:56.09 | F22 | ani screen also. |
| 06:56.16 | WisTilt2 | good, more info |
| 06:57.24 | F22 | will try to get that then for you. not like i need an excuse to listen to music... :P |
| 06:57.46 | *** join/#htc-linux BbLugNut|2 (~kvirc@108.118.253.171) |
| 06:58.33 | WisTilt2 | i'll catch you tomorrow night. should have the volume meter thing fixed then we'll tackle the crash stuff. |
| 06:58.46 | F22 | sounds good. :) |
| 06:58.50 | F22 | have a good night! |
| 06:58.55 | WisTilt2 | thanks again, been productive. |
| 06:59.12 | F22 | agreed. i'm pleased. |
| 07:03.28 | F22 | aoastill: this is a development channel, unless your question directly relates to the development of the linux kernel on a non-native htc device there is probably a better channel elsewhere to ask your question. this is not a help channel. |
| 07:07.44 | *** join/#htc-linux NeoMatrixJR (~chatzilla@173-25-51-102.client.mchsi.com) |
| 07:14.10 | F22 | ocm: rhodium |
| 07:32.34 | *** join/#htc-linux dcordes (~oedevel@unaffiliated/dcordes) |
| 07:33.32 | *** join/#htc-linux nrirclog (~nrirclog@netripper.com) |
| 07:36.40 | *** join/#htc-linux hastarin (~hastarin@220-253-44-94.VIC.netspace.net.au) |
| 07:39.58 | *** join/#htc-linux LeTama (~letama@vau06-1-82-228-252-90.fbx.proxad.net) |
| 07:45.27 | *** join/#htc-linux iDavid (~iDavid@41.226.240.23) |
| 07:52.38 | *** join/#htc-linux phantomcircuit (~phantomci@adsl-99-157-75-203.dsl.pltn13.sbcglobal.net) |
| 07:56.13 | *** join/#htc-linux dekar (~dekar@drms-4d0146d6.pool.mediaWays.net) |
| 08:19.34 | *** join/#htc-linux jonolo (574b8b38@gateway/web/freenode/ip.87.75.139.56) |
| 08:35.05 | *** join/#htc-linux Rob2223 (~Miranda@p4FFF34AB.dip.t-dialin.net) |
| 08:36.20 | *** join/#htc-linux lanwin (~wagners@p5B064586.dip0.t-ipconnect.de) |
| 08:36.26 | lanwin | good morning |
| 08:36.44 | lanwin | is there any difference how iptables handles rmnet compared to ppp? |
| 08:49.23 | *** join/#htc-linux kiozen (~kiozen@rgnb-5d87dbc1.pool.mediaWays.net) |
| 09:01.11 | *** join/#htc-linux OptX (~do@mnhm-5f74c99e.pool.mediaWays.net) |
| 09:07.50 | *** join/#htc-linux GlemSom (~glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk) |
| 09:11.36 | *** join/#htc-linux wish34 (~wishmaste@5e069895.bb.sky.com) |
| 09:14.55 | *** join/#htc-linux kubi (~Adium@miranda/user/kubi) |
| 09:21.55 | *** join/#htc-linux Jhinta (~Jhinta@s5592f326.adsl.wanadoo.nl) |
| 09:22.52 | *** join/#htc-linux leobaillard (~leobailla@leobaillard.org) |
| 09:32.53 | *** join/#htc-linux dekar (~dekar@drms-4d0146d6.pool.mediaWays.net) |
| 09:45.15 | *** join/#htc-linux pH5 (~ph5@e178205015.adsl.alicedsl.de) |
| 09:48.55 | *** join/#htc-linux eR^zeRa` (~zzeratul@88.103.98.168) |
| 09:55.57 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
| 09:59.12 | *** join/#htc-linux Arash18k (~Arash18k@85.133.200.152) |
| 10:02.35 | *** join/#htc-linux mdeejay_ (~mdeejay@188.168.168.101) |
| 10:02.42 | *** join/#htc-linux kerch2 (2961d1e8@gateway/web/freenode/ip.41.97.209.232) |
| 10:03.42 | *** part/#htc-linux kerch2 (2961d1e8@gateway/web/freenode/ip.41.97.209.232) |
| 10:08.21 | *** join/#htc-linux iDavid (~iDavid@41.226.240.23) |
| 10:10.35 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
| 10:13.15 | *** join/#htc-linux MacDrunk (~marper@201.165.130.186) |
| 10:16.57 | *** join/#htc-linux GNUtoo|laptop (~gnutoo@95.232.144.102) |
| 10:19.58 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
| 10:23.04 | *** join/#htc-linux the_eye_ (~dimitris@78-211-216.adsl.cyta.gr) |
| 10:23.36 | *** join/#htc-linux Ashar (deadly@unaffiliated/ashar) |
| 10:28.20 | *** join/#htc-linux tblt (~tblt@corp-nat.corp.tw1.yahoo.com) |
| 10:36.56 | *** join/#htc-linux Echo31 (~olivier@mir31-4-82-240-194-54.fbx.proxad.net) |
| 10:46.42 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
| 10:49.37 | *** join/#htc-linux Neo31 (~Neo31@unaffiliated/neo31) |
| 10:49.59 | *** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp) |
| 10:58.49 | *** join/#htc-linux Jack-E (~Jack@host86-140-240-200.range86-140.btcentralplus.com) |
| 11:12.18 | *** join/#htc-linux Gergo (d5860c6f@gateway/web/freenode/ip.213.134.12.111) |
| 11:12.26 | Gergo | hy !! |
| 11:12.31 | Gergo | hello |
| 11:13.04 | Gergo | Project Android running on LG GM750 ? |
| 11:19.46 | *** join/#htc-linux naxx (~andrew@ppp91-78-156-68.pppoe.mtu-net.ru) |
| 11:20.16 | Gergo | Project Android running on LG GM750 ? |
| 11:27.16 | *** join/#htc-linux Phally (~Phally@d28072.upc-d.chello.nl) |
| 11:33.39 | *** join/#htc-linux Markinus (~Miranda@212.255.36.196) |
| 11:39.09 | *** join/#htc-linux Guachiflai_ (57d91f4a@gateway/web/freenode/ip.87.217.31.74) |
| 11:42.27 | *** join/#htc-linux BabelO (~fcr@AMontpellier-554-1-64-17.w86-202.abo.wanadoo.fr) |
| 11:42.27 | *** join/#htc-linux BabelO (~fcr@unaffiliated/babelo) |
| 11:48.38 | *** join/#htc-linux [zozi] (~chatzilla@2.80.137.55) |
| 11:50.46 | Markinus | hi |
| 11:51.35 | LeTama | Hello Markinus |
| 11:54.12 | Markinus | LeTama: my tg01 is sended to a wrong address . . . argh . .now I have wait again some days . . |
| 11:55.15 | LeTama | Markinus: yes, saw that. Too bad |
| 11:55.27 | Markinus | yes . .. :( |
| 11:57.46 | *** join/#htc-linux iDavid (~iDavid@41.226.240.23) |
| 11:57.50 | *** part/#htc-linux iDavid (~iDavid@41.226.240.23) |
| 11:57.52 | *** join/#htc-linux Neonkoala (~Neonkoala@cpc1-rdng18-0-0-cust21.15-3.cable.virginmedia.com) |
| 11:58.03 | *** join/#htc-linux shadoko (~noe@94-23-154-153.kimsufi.com) |
| 12:07.11 | *** join/#htc-linux luc_ (5e3edc93@gateway/web/freenode/ip.94.62.220.147) |
| 12:11.03 | *** join/#htc-linux nilsk123 (~yaaic@ip5653f257.direct-adsl.nl) |
| 12:14.00 | *** join/#htc-linux Ashar (deadly@unaffiliated/ashar) |
| 12:14.52 | *** join/#htc-linux nilsk1232 (~yaaic@host064-002.kpn-gprs.nl) |
| 12:20.49 | fakker | [- OS Uptime: 1wk 4h 39m 7s -] |
| 12:20.54 | fakker | laptop still not dead |
| 12:20.55 | fakker | :O |
| 12:22.31 | nilsk1232 | i havent been plugged in for 20 years and im still alive |
| 12:24.57 | *** join/#htc-linux Echo31 (~olivier@mir31-4-82-240-194-54.fbx.proxad.net) |
| 12:29.34 | *** join/#htc-linux kubi1 (~Adium@e176075125.adsl.alicedsl.de) |
| 12:29.45 | *** part/#htc-linux kubi1 (~Adium@e176075125.adsl.alicedsl.de) |
| 12:47.55 | *** join/#htc-linux LordDeath (~LordDeath@cable-81-173-165-2.netcologne.de) |
| 12:48.25 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
| 13:04.21 | *** join/#htc-linux hastarin (~hastarin@220-253-44-94.VIC.netspace.net.au) |
| 13:04.46 | *** join/#htc-linux MN-hd2 (~yaaic@customer49227.104.wv.cust.t-mobile.co.uk) |
| 13:05.27 | hastarin | Just found out something interesting about notification LEDs! |
| 13:05.42 | hastarin | If you boot with the charger plugged in then they work. |
| 13:05.43 | MN-hd2 | hi |
| 13:08.05 | *** join/#htc-linux Neonkoala (~Neonkoala@cpc1-rdng18-0-0-cust21.15-3.cable.virginmedia.com) |
| 13:08.13 | *** join/#htc-linux Ashar (deadly@unaffiliated/ashar) |
| 13:18.40 | *** join/#htc-linux froezen (~ircap@92.29.140.185) |
| 13:21.00 | *** join/#htc-linux CrAzY_CbR (d5e74651@gateway/web/freenode/ip.213.231.70.81) |
| 13:21.43 | *** join/#htc-linux jiogi (~jiogi@212.50.115.55) |
| 13:21.57 | jiogi | hastarin: have you tried to replicate it again? |
| 13:22.28 | jiogi | hastarin: i ve booted with charger plugged in and still same thing |
| 13:23.07 | hastarin | jiogi: I have never had leds working correctly. I booted with charger in, then got a friend to chat to me via Google Talk and got a notification. |
| 13:23.36 | hastarin | I tried again with an email and got a notification. I deleted the email via my PC and the notification cleared. |
| 13:24.40 | jiogi | hastarin: strange.. mine work but only once. sms: 1 blink of the green led, missed call: not a blink, switches on and stays on. Call: 1 blink.. but thats it |
| 13:25.48 | hastarin | It might also be build related I guess. Do you have the latest liblights and which kernel are you using? |
| 13:27.26 | jiogi | git kernel |
| 13:27.39 | jiogi | using evo revolution from mdeejay |
| 13:27.58 | jiogi | git 8ths of Nov |
| 13:28.05 | jiogi | without the latest camera related changes |
| 13:28.15 | jiogi | was lazy to apply new changes |
| 13:28.40 | jiogi | the liblights are included i think they were as of 5th of november |
| 13:30.01 | hastarin | Hmm, strange, so you booted with the cable in, then unplugged it once Android was up and running? |
| 13:30.52 | *** join/#htc-linux eR^Z` (~zzeratul@88.103.98.168) |
| 13:32.11 | jiogi | yup |
| 13:32.17 | jiogi | i ll try again |
| 13:32.36 | jiogi | m on haret though,, |
| 13:32.57 | jiogi | are you wall plugged in or usb ? |
| 13:33.42 | hastarin | I'm on haret too. I used AC charger |
| 13:34.42 | jiogi | did it now with USB though, i will re-test and check with ac charger in a while |
| 13:34.53 | jiogi | are you on an EVO based build? |
| 13:35.34 | hastarin | No Desire. I'm using mdeejay Clean Sense 2.3 with my kernel (8.2) |
| 13:35.42 | jiogi | hmm |
| 13:35.58 | jiogi | dont you have ts freezes with desire based? |
| 13:36.26 | mdeejay | with fixed r8.2 no more freezes |
| 13:36.48 | jiogi | the one from the guy claiming gsensor fix ? |
| 13:36.52 | jiogi | or urs? |
| 13:36.54 | hastarin | I never noticed freezes personally, except on resume, but then I don't walk and text, etc |
| 13:37.52 | jiogi | hastarin |
| 13:37.55 | jiogi | it works!!! |
| 13:38.02 | *** join/#htc-linux mdeejay (~mdeejay@188.168.168.101) |
| 13:38.09 | mdeejay | gpc yes |
| 13:38.15 | mdeejay | oops |
| 13:38.23 | hastarin | OK so it has to be AC charger then it seems? |
| 13:38.34 | jiogi | i plugged it on USB, set w6.5 to see USB as Companion, and then booted with button leds on |
| 13:38.43 | jiogi | no, it was on PC |
| 13:38.57 | jiogi | just set the connection to be as Companion device in Windows |
| 13:39.00 | hastarin | Oh so it just needs to have cable AC/USB in on boot. |
| 13:39.06 | jiogi | so that i could see the card |
| 13:39.21 | jiogi | the LED blinks slower than windows though |
| 13:39.36 | hastarin | Yeah, but it blinks! :D |
| 13:39.40 | jiogi | dont know whether that is normal in adroid |
| 13:39.42 | jiogi | yes :) |
| 13:39.54 | hastarin | Slower isn't so bad, saves some power. |
| 13:39.58 | mdeejay | strange bug :) |
| 13:39.59 | jiogi | yup |
| 13:40.16 | jiogi | mdeejay: are you gonna update evo revolution ? :P |
| 13:40.26 | mdeejay | after fix i2c |
| 13:40.30 | jiogi | ok |
| 13:40.47 | *** join/#htc-linux Markinus (~Miranda@212.255.36.196) |
| 13:40.48 | mdeejay | AND I REMOVE BFQ from kernel |
| 13:40.54 | jiogi | hastarin: have you noticed any long delay once it blinks ? |
| 13:40.55 | hastarin | So now we need to figure out what the kernel does differently when cable is in on boot. Must be something it should be doing even if it isn't in. |
| 13:41.16 | Markinus | Hi |
| 13:41.20 | jiogi | i ve been trying to access messages to read the unread and it still Loading |
| 13:41.24 | hastarin | What do you mean long delay? I've only done 2 quick tests so far. I just found this out. |
| 13:41.32 | hastarin | Welcome Markinus. |
| 13:41.38 | jiogi | hastarin: its still loading messages |
| 13:42.12 | hastarin | We've just found out that booting with cable plugged in (on haret anyway) makes the notification LEDs work. |
| 13:42.49 | jiogi | tested :) |
| 13:42.51 | hastarin | jiogi: I'm still not sure what you mean. Like the phone is lagged? |
| 13:42.58 | mdeejay | with bfq kernel @ 1228 slower @998 :D |
| 13:42.59 | jiogi | in both EVO Sense and Desire Sense |
| 13:43.10 | Markinus | hastarin: intresting |
| 13:43.18 | jiogi | hastarin: it was only first time, now its very quick as expected |
| 13:43.52 | hastarin | Markinus: Did you do the code for detecting cable on bootup or was that LeTama? |
| 13:43.57 | jiogi | at least its something :) |
| 13:44.06 | Markinus | hastarin: cotulla and me |
| 13:44.12 | hastarin | I'm guessing it's doing something different that it should be doing even if the cable isn't in? |
| 13:44.14 | *** join/#htc-linux Blizzzard (5e09b634@gateway/web/freenode/ip.94.9.182.52) |
| 13:44.53 | hastarin | Almost 1am here, but when I saw that post on the forum I had to jump on and spread the news. :) |
| 13:45.04 | Markinus | hastarin: hehe :) |
| 13:45.27 | Markinus | hastarin: there is a difference, but why it should change the notofocations led, it's strange |
| 13:45.39 | hastarin | All credit to rafpigna for discovering it. |
| 13:46.29 | Markinus | hastarin: I read about the gseonmsor leg fix too |
| 13:46.42 | Markinus | hastarin: is this happend on your device too? |
| 13:46.52 | Markinus | hastarin: hanings? i2c erors? |
| 13:47.00 | Markinus | hastarin: I didn't have this problem |
| 13:47.04 | hastarin | I haven't tried it. I never noticed i2c errors except on resume. |
| 13:47.14 | Markinus | like me |
| 13:47.18 | hastarin | I don't walk and type/play touch screen games. |
| 13:47.18 | jiogi | Markinus: i have this problem only on Desire builds, on EVO there is no such thing |
| 13:47.27 | hastarin | And I turn off auto rotate normally. |
| 13:47.37 | Markinus | jiogi: hmm, intresting |
| 13:47.38 | hastarin | It annoys me when I'm lying in bed and screen rotates, etc :p |
| 13:48.03 | jiogi | hastarin: i wouldnt notice it that much, until i tried EVO, its too smooth in comparison with desire, and i noticed that its Ts freezes |
| 13:48.20 | hastarin | I've asked the guys who wrote the patch to contact you/LeTama or just release the patch already. :) |
| 13:48.44 | mdeejay | 99% users have g-sensor bug :D |
| 13:48.59 | Markinus | hastarin: I looked to the code, the gsensor driver is original EVO, I didn't change it |
| 13:49.01 | hastarin | jiogi: EVO smoother than Desire? My device is super smooth. :) |
| 13:49.16 | jiogi | hastarin: i will try your combination today |
| 13:49.18 | jiogi | ;) |
| 13:49.20 | mdeejay | Desire based builds BETTER than EVO !!! |
| 13:49.41 | jiogi | mdeejay: are you sure ? :P |
| 13:49.50 | hastarin | I have played Fruit Ninja without problems, though not whilst walking/shaking the phone. :p |
| 13:49.55 | mdeejay | more compatible with HD2 without fuckin 4G |
| 13:50.06 | mdeejay | and others small bugs |
| 13:50.28 | hastarin | Markinus: Have you seen the i2c patch they are testing? |
| 13:51.11 | *** join/#htc-linux Willow (~Willow@cpe-173-175-86-45.stx.res.rr.com) |
| 13:51.52 | mdeejay | hastarin http://www.youtube.com/watch?v=-RlCuITimvM |
| 13:54.48 | hastarin | Ahh g-sensor, I was thinking, touch screen freeze. I have played Glyder 2 for hours, with maybe 1 or 2 glitches but they seemed to be due to other apps causing issues or low memory. |
| 13:54.59 | Markinus | hastarin: I saw only the Image, nop rouce patch |
| 13:55.02 | Markinus | *source |
| 13:56.14 | hastarin | Interesting though, I just reproduced it in Teeter very easily. I wonder if it's related to the vibration. |
| 13:56.41 | *** join/#htc-linux noellenchris (ad3d72f1@gateway/web/freenode/ip.173.61.114.241) |
| 13:57.21 | hastarin | Markinus: I have asked them via PM if they are happy for me to pass it on to you. Personally I think they should just release it to the public but am respecting their wishes for now. |
| 13:57.28 | mdeejay | with your patched r8.2 i don't have this issue with teeter |
| 13:58.04 | shadoko | using the showsensors app it doesnt freeze anymore either with patched 8.2 |
| 13:58.46 | hastarin | mdeejay: I didn't patch it, they did. It's easy to build my kernel with my FAQ and a little knowledge. |
| 13:58.49 | Markinus | hastarin: If I have it I will look to and and if all ok push it |
| 14:00.16 | hastarin | If they don't release it in the next few days I may just do it for them. Strictly speaking, they should have done so anyway from a legal standpoint. |
| 14:02.45 | mdeejay | hastarin pastebin patch :D |
| 14:03.02 | *** join/#htc-linux avinashhm (~avinash-h@192.163.20.231) |
| 14:05.10 | hastarin | mdeejay: Like I said, I'll give them some more time to do it first. |
| 14:05.50 | shadoko | say, hastarin. how about implementing the smartass governer in your kernel? |
| 14:06.26 | mdeejay | :( |
| 14:07.09 | hastarin | shadoko: I might add it at some stage. It would be easier if mdeejay released his source and/or diffs. :) |
| 14:07.20 | mdeejay | :) |
| 14:07.30 | shadoko | yeah, release the source mdeejay :3 |
| 14:07.46 | hastarin | But personally I don't agree with the basic theory of it. I will stick with Interactive. |
| 14:07.47 | mdeejay | i cant upload to gitorious |
| 14:07.58 | shadoko | what about github? |
| 14:08.04 | hastarin | mdeejay: Did you make your own clone? |
| 14:08.13 | mdeejay | yes |
| 14:08.20 | mdeejay | i have clone |
| 14:08.27 | hastarin | And then use git on your local copy of the clone? |
| 14:08.52 | hastarin | Oh so you were working on http://gitorious.org/~mdeejay/linux-on-wince-htc/mdeejays-linux_on_wince_htc |
| 14:12.22 | *** join/#htc-linux pH5_ (~ph5@e178233070.adsl.alicedsl.de) |
| 14:14.50 | *** join/#htc-linux Aevum (~Ticcor@46.42.217.87.dynamic.jazztel.es) |
| 14:17.09 | jiogi | mdeejay: in the patched 8,2 there is a file cifs.ko where shall it be placed? |
| 14:18.04 | *** join/#htc-linux luc__ (5e3edc93@gateway/web/freenode/ip.94.62.220.147) |
| 14:22.49 | Aevum | im still getting the same issue, |
| 14:22.59 | Aevum | the phone hangs on a black screen and eats up the battery |
| 14:24.11 | Markinus | no |
| 14:24.20 | Markinus | ww |
| 14:26.02 | Aevum | ? |
| 14:28.30 | shadoko | jiogi: /system/lib/modules/ |
| 14:29.17 | jiogi | thanks |
| 14:29.42 | jiogi | shadoko: so basically we copy these ko files in modules, then make the links and camera will be functional ? |
| 14:30.10 | shadoko | jiogi: i'm not entirely sure about that, i only tried camera on a cm6 build and it was fine for me |
| 14:30.17 | jiogi | ok |
| 14:31.43 | hastarin | jiogi: Jump to #htc-linux-chat |
| 14:32.27 | jiogi | sorry |
| 14:37.20 | *** join/#htc-linux spetrillo (~SteveP@71.167.185.184) |
| 14:38.35 | *** join/#htc-linux kiozen (~kiozen@rgnb-5d87dbc1.pool.mediaWays.net) |
| 14:44.22 | *** join/#htc-linux eR^zeRa` (~zzeratul@88.103.98.168) |
| 14:48.36 | *** join/#htc-linux wish34 (~wishmaste@5e069895.bb.sky.com) |
| 14:49.17 | *** join/#htc-linux toi (~toi@d54C2AA76.access.telenet.be) |
| 14:51.34 | Markinus | hastarin: I think about to revert to old battery driver driver |
| 14:51.50 | Markinus | hastarin: there are some problems and differences between weince and android |
| 14:52.01 | Markinus | till we fix the nex completly for our battery |
| 14:52.07 | Markinus | *new |
| 14:53.16 | hastarin | Markinus: You mean differences in temperature or charge level or ...? |
| 14:54.43 | Markinus | cgarge level |
| 14:54.49 | Markinus | temepratur is ok |
| 14:55.23 | hastarin | I haven't taken notice. Does it get it wrong? Seems to discharge to 0 and charge to 100 ok? |
| 14:55.53 | Markinus | hastarin: I get the message if you compare it with wince and to a reset between and drop the battery trhere is a difference |
| 14:56.06 | Markinus | 10% or so |
| 14:56.11 | Markinus | over wince vale |
| 14:56.13 | Markinus | value |
| 14:56.30 | hastarin | Oh wow! I noticed it adjusts based on voltages. Maybe we need to adjust voltage mappings it's using. |
| 14:57.01 | hastarin | Reverting sounds OK to me. Old driver, with the last changes so it charged to 100% seems reasonable to me. |
| 14:57.14 | Markinus | hastarin: yes, I think so too |
| 14:57.31 | Markinus | we have to find out the coefficients for the calculation for our batteries |
| 14:59.08 | hastarin | They would seem to be the hard part. :( |
| 14:59.30 | hastarin | Unless they happen to be one of the hard coded values in the old driver. |
| 15:00.10 | luc__ | Markinus: lets ask more people to test this |
| 15:00.11 | hastarin | Well if that gets reverted I can reapply my extended battery patch at least. That will make extended battery users very happy as they'll get the other changes. |
| 15:00.31 | Markinus | ok, I will do it today . . |
| 15:01.35 | luc__ | Markinus: doing the the same thing in windows shows 10 % more |
| 15:01.46 | hastarin | Oh, I notice one of the values I saw mentioned Pd_M is written out by tBattery log. |
| 15:02.21 | luc__ | hastarin u are on nand? |
| 15:02.33 | hastarin | luc: No, haret. |
| 15:02.38 | luc__ | ok |
| 15:02.41 | luc__ | lets test |
| 15:03.18 | luc__ | charge in android, then remove batt, see how much shows wm |
| 15:04.03 | hastarin | Why remove it? Why not just reboot? |
| 15:04.17 | hastarin | Well reboot, remove, then see in WM ok? |
| 15:04.20 | luc__ | second test remove batt, reset, charge in wm, remove batt, rebot in wm see proc? |
| 15:05.09 | hastarin | I'm not sure what you're wanting to test there? |
| 15:05.14 | luc__ | this way we gonna se if there is a diff between wm and andro in showing the real proc. |
| 15:06.06 | hastarin | Well Android was showing 92%, rebooted, removed battery, replaced battery, booted in to WM and it shows 100% |
| 15:06.18 | luc__ | like mine |
| 15:06.25 | hastarin | So yes, it is showing differently. |
| 15:06.33 | luc__ | now try with reset |
| 15:07.06 | luc__ | on me after reset wm shows 92% |
| 15:07.10 | luc__ | not 100% |
| 15:07.22 | hastarin | Of course it does. |
| 15:07.36 | hastarin | Because it just reads the ACR value that Android wrote. |
| 15:07.49 | luc__ | after reset? |
| 15:08.04 | hastarin | Yes, the ACR value survives reset. |
| 15:08.12 | luc__ | acr stays after reset? |
| 15:08.13 | luc__ | ahh |
| 15:08.14 | luc__ | ok |
| 15:08.19 | luc__ | thats why |
| 15:08.36 | luc__ | so is something wrong!? |
| 15:08.45 | luc__ | 10% diff |
| 15:09.15 | hastarin | Yes, that's why Markinus has said he is going to revert the new driver until it can be fixed. |
| 15:09.47 | luc__ | ive talk to him about this issue already |
| 15:10.10 | luc__ | i think thats why its reverting old driver |
| 15:11.30 | hastarin | Yes that's what he said. All good then. |
| 15:12.08 | hastarin | I must go. 2:11am here |
| 15:12.11 | luc__ | the only bad thing with the new desire hd driver is not to over charge. |
| 15:12.36 | luc__ | ok bb histarin..see ya |
| 15:14.28 | luc__ | Markinus: if you think the old home made driver is better just remove the patch |
| 15:14.41 | *** join/#htc-linux ts0cha0tik (~ts0cha0ti@254-44.125-70.tampabay.res.rr.com) |
| 15:19.51 | jiogi | the patched kernel for TS freeze (hastarin 8.2 patched) really works, hope that devs push it to GIT soon. |
| 15:20.22 | shadoko | can't wait for the source on that one |
| 15:20.40 | mdeejay | :( |
| 15:20.42 | mdeejay | i too |
| 15:20.54 | luc__ | jiogi: ask markinus...is going to revert a patch anyway |
| 15:21.27 | luc__ | maybe he will pus the ts fix too |
| 15:21.50 | luc__ | *h |
| 15:21.52 | shadoko | i don't think he's got the source yet, the author wanted to make sure there were no side-effects first |
| 15:22.10 | jiogi | Markinus: do you think that old battery driver with all the know-how from the new one that we are currently on, can be perfectionised? |
| 15:22.38 | jiogi | today we ve found 3 major fixes :), lights can work as long as you boot with cable on |
| 15:22.49 | jiogi | battery can be better at least 10% |
| 15:23.04 | jiogi | and TS freezes can be eliminated with new source |
| 15:23.34 | Markinus | jiogi: TS freezes??? I nmever had it :) what new sources? |
| 15:23.55 | Markinus | jiogi: the new batterie driver is a MONSTER |
| 15:23.59 | Markinus | very big |
| 15:24.04 | mdeejay | g-sensor fix |
| 15:24.06 | Markinus | our old works nice too |
| 15:24.10 | Markinus | there is no a problem |
| 15:24.11 | shadoko | the freezing: http://www.youtube.com/watch?v=-RlCuITimvM |
| 15:24.18 | mdeejay | its g-sensor |
| 15:24.21 | mdeejay | no ts |
| 15:24.24 | Markinus | ahh, gsensor, ok |
| 15:24.24 | jiogi | Markinus: the ones from the XDA guys,, applied the g-sensor fix, it eliminated some minor TS freezes |
| 15:24.38 | Markinus | same thing, ok |
| 15:24.43 | jiogi | mdeejay: i think it affected TS ? or not |
| 15:24.49 | Markinus | intresting that it happends only on some devices |
| 15:24.55 | jiogi | yeap |
| 15:25.07 | mdeejay | g-sensor error -> ts freeze ;D |
| 15:25.17 | jiogi | Markinus: about battery, can it be cleaned up or fixed? |
| 15:25.20 | jiogi | mdeejay: yeap |
| 15:27.01 | Markinus | jiogi: the did the driver with much informations abouit the baterries |
| 15:27.07 | Markinus | there a deffierent |
| 15:27.19 | Markinus | corrections coefficients for each batterie |
| 15:27.32 | Markinus | jiogi: we have to find it out if we will use it full |
| 15:27.52 | jiogi | Markinus: aham.. i see |
| 15:28.10 | Markinus | jiogi: there is a list of 4 baterries from desire HD |
| 15:28.17 | Markinus | but they 1230 is different to our |
| 15:28.34 | jiogi | Markinus: i ve noticed.. |
| 15:29.31 | jiogi | Markinus: our battery (the prev one) only had some minor issues with 100% charge.. it was going up to 86% and there was a last patch for 99% i think ? |
| 15:29.39 | *** join/#htc-linux spetrillo (~SteveP@71.167.185.184) |
| 15:29.49 | Markinus | jiogi: not after my last change |
| 15:29.57 | Markinus | jiogi: then it works good |
| 15:30.13 | Markinus | but only 2 days till the new one come out :) |
| 15:30.50 | jiogi | Markinus: yes i remember,, will you go through again and compare new vs old and see if there is anything we can grab from HD's ? or raw testing ? |
| 15:31.32 | Markinus | for first we let my old one. IT should now works good. Then we look if we can do something for the new one |
| 15:32.12 | *** join/#htc-linux iDavid (~iDavid@41.226.240.23) |
| 15:32.29 | iDavid | ~apt seen cotulla |
| 15:32.33 | apt | cotulla <~opera@nat004-252-205-109.tvoe.tv> was last seen on IRC in channel #htc-linux, 19d 1h 42m 19s ago, saying: 'bb'. |
| 15:32.44 | iDavid | What happened with cotulla? |
| 15:32.54 | mdeejay | nothing |
| 15:33.04 | luc__ | maybe delenn |
| 15:33.06 | jiogi | ~apt seen Delenn |
| 15:33.07 | apt | jiogi: i haven't seen 'delenn' |
| 15:33.18 | mdeejay | [Delenn] |
| 15:33.23 | iDavid | Thats what i thought too.. |
| 15:33.24 | luc__ | [delenn] |
| 15:33.32 | luc__ | lol |
| 15:34.03 | iDavid | so its now delenn.pp.ru ? |
| 15:34.17 | luc__ | ~apt seen [Delenn] |
| 15:34.18 | apt | [delenn] <~opera@nat004-252-205-109.tvoe.tv> was last seen on IRC in channel #htc-linux, 19h 24m 59s ago, saying: 'don't understand anything %)'. |
| 15:36.55 | Rajko | thats about right |
| 15:47.39 | *** join/#htc-linux dan1j3l (~danijel@93-138-251-250.adsl.net.t-com.hr) |
| 15:48.29 | dan1j3l | hi |
| 15:50.00 | luc__ | hi Dan |
| 15:50.27 | luc__ | news? |
| 15:51.08 | dan1j3l | no, nothing much... |
| 15:53.02 | LeTama | hi guys |
| 15:53.39 | dan1j3l | hi |
| 15:54.09 | LeTama | dan1j3l, I sent a merge request for lib wrapper if you want to integrate it. |
| 15:54.15 | eR^zeRa` | apt is a bot? |
| 15:54.26 | eR^zeRa` | ~apt help |
| 15:54.38 | dan1j3l | LeTama: ok |
| 15:55.01 | eR^zeRa` | ~apt reverse abc |
| 15:55.13 | eR^zeRa` | :L |
| 15:56.20 | dan1j3l | LeTama: new wrapper looks nice |
| 15:57.51 | LeTama | dan1j3l: it works quite well, yes |
| 15:57.55 | LeTama | hopefully this new version will behave a little better, or at least help troubleshooting |
| 15:59.48 | jiogi | dan1j3l: have you read about LED notifications on SENSE builds? |
| 16:00.07 | jiogi | dan1j3l: it works if you have the cable plugged while booting |
| 16:00.35 | dan1j3l | <PROTECTED> |
| 16:00.50 | dan1j3l | <PROTECTED> |
| 16:01.06 | dan1j3l | <PROTECTED> |
| 16:01.23 | jiogi | try todays logs after 14:00 |
| 16:01.35 | jiogi | hastarin found out from another xda user |
| 16:01.42 | jiogi | i tested as well and it works |
| 16:02.04 | dan1j3l | <PROTECTED> |
| 16:02.25 | jiogi | dan1j3l: you are welcome, it might be a bit easier now to track it down ;) |
| 16:02.59 | dan1j3l | <PROTECTED> |
| 16:03.11 | dan1j3l | ok, must go now, bbl |
| 16:03.16 | jiogi | dan1j3l: c u |
| 16:03.41 | *** join/#htc-linux m77 (~m77@cpc2-nfds9-0-0-cust764.8-2.cable.virginmedia.com) |
| 16:03.53 | *** part/#htc-linux m77 (~m77@cpc2-nfds9-0-0-cust764.8-2.cable.virginmedia.com) |
| 16:04.04 | mdeejay | hm new wrapper :) |
| 16:05.05 | jiogi | ppp ? |
| 16:06.26 | jiogi | nice |
| 16:07.48 | shadoko | testing the new wrapper now |
| 16:13.24 | *** join/#htc-linux Neo31 (~Neo31@unaffiliated/neo31) |
| 16:13.52 | *** join/#htc-linux Josh13x12 (~josh13x12@99-190-187-250.lightspeed.lsvlky.sbcglobal.net) |
| 16:16.23 | *** join/#htc-linux ocm (~ocm@189.183.7.64) |
| 16:17.41 | *** join/#htc-linux dan1j3l (~danijel@78-1-143-233.adsl.net.t-com.hr) |
| 16:22.13 | *** join/#htc-linux toi (~toi@d54C2AA76.access.telenet.be) |
| 16:23.52 | *** join/#htc-linux tb_killa (~tb_killa@dsbg-4db576cc.pool.mediaWays.net) |
| 16:37.50 | *** join/#htc-linux naxx (~andrew@ppp91-76-133-143.pppoe.mtu-net.ru) |
| 16:42.28 | *** join/#htc-linux Arash18k (~Arash18k@85.133.200.152) |
| 16:45.08 | dcordes | ~seen smoku |
| 16:45.09 | apt | smoku <~79f6be280@xkh1g1.infr.xiaoka.com> was last seen on IRC in channel #meego, 2d 2h 30m 54s ago, saying: ':/ i should have learned not to click every single link i see on irc already...'. |
| 16:45.29 | Willow | Well, I thought I knew what I was doing but it doesn't work. |
| 16:45.29 | Willow | Can someone tell me how to code the following c statement in arm assemby? |
| 16:45.29 | Willow | writel(0x1cc,(unsigned)(0xa9900000)); |
| 16:45.35 | Arash18k | dcordes, have time? |
| 16:46.24 | dcordes | Arash18k: hi |
| 16:46.48 | dcordes | Arash18k: a litle. did you see [[Ubuntu/Leo]] ? |
| 16:46.48 | unilinky | http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo |
| 16:47.01 | Arash18k | yes, nice guid |
| 16:47.11 | dcordes | did you try to create your own image ? |
| 16:47.26 | Arash18k | i did, i even booted lucid |
| 16:47.51 | dcordes | Arash18k: does your keypad work ? |
| 16:47.56 | dcordes | (in Xorg) |
| 16:47.59 | Arash18k | but there was a little problem on maverick and meego |
| 16:48.15 | Arash18k | it worked on terminal |
| 16:48.33 | Arash18k | did test it on xorg |
| 16:48.44 | Arash18k | *didnt |
| 16:48.51 | dcordes | could you try ? |
| 16:49.14 | Arash18k | yes, i'll try tomorow |
| 16:49.48 | Arash18k | but looks like mouse rotation is not working on meego and maverik |
| 16:49.49 | dcordes | good thanks. it would be nice to add comentary on it in above wiki page. it has something on broken keypad in xorg in maverick |
| 16:50.22 | Arash18k | *touch |
| 16:50.55 | dcordes | Arash18k: did you take notice of [[Ubuntu/Leo#Touchscreen]] ? it works for me |
| 16:50.55 | unilinky | http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo%23Touchscreen |
| 16:51.06 | Arash18k | yeah it worked fine in lucid |
| 16:51.09 | dcordes | I tested this in maverick |
| 16:51.58 | dcordes | can we switch to #ubuntu-arm ? |
| 16:52.08 | Arash18k | sure |
| 16:53.02 | *** join/#htc-linux nineX_ (~nunya@75-132-13-29.dhcp.stls.mo.charter.com) |
| 16:53.22 | Willow | The following is the arm assembler that I thought would do the same as the c command I mentioned above: |
| 16:53.22 | Willow | i2cWrite:.word 0xa9900000 |
| 16:53.22 | Willow | ldrr9, =i2cWrite |
| 16:53.22 | Willow | ldrr8, =0xCD |
| 16:53.23 | Willow | addr8, r8, #0xFF |
| 16:53.23 | Willow | strr8, [r9] |
| 16:53.24 | Willow | Unfortunately it does not appear to do what I intend...probably because I have not told it to do what I intend :( Any ideas where I have gone wrong? |
| 16:55.42 | *** join/#htc-linux Paul__ (~Anee@a85-138-178-60.cpe.netcabo.pt) |
| 16:56.35 | Paul__ | We would like to see HD2 on this site:http://wiki.meego.com/ARM/MSMQSD |
| 16:59.22 | *** join/#htc-linux manusfreedom (~manusfree@tra78-1-82-235-115-79.fbx.proxad.net) |
| 17:00.46 | *** join/#htc-linux jiogi (~jiogi@212.50.115.55) |
| 17:04.18 | GNUtoo|laptop | hi, |
| 17:04.26 | GNUtoo|laptop | is there any infos on how to replace akmd? |
| 17:04.41 | GNUtoo|laptop | does it need a daemon? |
| 17:04.50 | GNUtoo|laptop | are standalone ioctl enough? |
| 17:05.30 | GNUtoo|laptop | dcordes, hi |
| 17:05.45 | dcordes | hi GNUtoo|laptop |
| 17:06.46 | *** join/#htc-linux Jack-E (~Jack@host86-140-240-200.range86-140.btcentralplus.com) |
| 17:08.14 | *** join/#htc-linux FsTluxe (~FsTluxe@82.176.11.11) |
| 17:08.58 | *** join/#htc-linux Arash18k (~Arash18k@85.133.200.152) |
| 17:11.10 | luc_ | Markinus: are you going to revert the battery commit? |
| 17:12.02 | *** join/#htc-linux t3g (3e9e600d@gateway/web/freenode/ip.62.158.96.13) |
| 17:12.13 | Markinus | I'm now on it |
| 17:16.34 | Willow | nobody here know arm assembly? |
| 17:22.29 | *** join/#htc-linux froezen (~ircap@92.29.135.203) |
| 17:30.14 | *** join/#htc-linux eR^Z` (~zzeratul@88.103.98.168) |
| 17:30.54 | *** join/#htc-linux froezen (~ircap@92.29.135.203) |
| 17:33.05 | *** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr) |
| 17:35.37 | *** join/#htc-linux ocm (~ocm@189.183.7.64) |
| 17:35.40 | *** join/#htc-linux the_eye_ (~dimitris@78-211-216.adsl.cyta.gr) |
| 17:37.46 | *** join/#htc-linux Downy (~Downy@p5DF57027.dip.t-dialin.net) |
| 17:39.38 | Willow | The last thing I see on the haret framebuffer is "Turning off MMU..." and of course, the Linux kernel does not boot. Should there be any other message displayed on the haret framebuffer after "Turning off MMU..." ?? |
| 17:40.05 | *** join/#htc-linux Ultimaex (4d0c59b5@gateway/web/freenode/ip.77.12.89.181) |
| 17:40.17 | Markinus | old battery driver now pushed |
| 17:40.51 | mdeejay | good |
| 17:40.56 | Markinus | Willow: can you something see in the ramconsole dump? |
| 17:41.02 | mdeejay | extended support? |
| 17:41.20 | Markinus | hastarin has a patch for that |
| 17:42.00 | Willow | I'm pretty sure it is nearly impossible to view the ramconsole dump on the Willow platform since it does not have a reset button to do a warm reset |
| 17:42.09 | mdeejay | ok |
| 17:42.23 | Markinus | Willow: do you add the very early console patch? than you can dump it and see where the kernel is hanging |
| 17:42.44 | Markinus | Willow: battery . .drop |
| 17:42.46 | Markinus | works too |
| 17:43.25 | *** join/#htc-linux arrrghhh (~arrrghhh@c-71-237-40-111.hsd1.co.comcast.net) |
| 17:43.45 | Willow | ahh, then I'll try that. so to look at the ramconsole I just drop battery and then upon booting, start haretconsole and dump some memory address that I can probably look up |
| 17:43.55 | *** join/#htc-linux cr2_ (~cr2@ip-80-226-0-1.vodafone-net.de) |
| 17:44.02 | Markinus | yes |
| 17:44.06 | Markinus | here is our patch |
| 17:44.07 | Markinus | http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc/commit/45c4a05fb6c542bc49a999187eaa7fe95ebdfc64 |
| 17:44.16 | Markinus | but you have to look to the addresses of your device |
| 17:44.45 | cr2_ | Echo31: ping |
| 17:47.38 | Markinus | Willow: in this patch the change in the config file for the ramaddress is wrong |
| 17:47.50 | Ultimaex | www.ti.com/ez430 |
| 17:47.53 | Ultimaex | errr |
| 17:47.53 | Ultimaex | sry |
| 17:47.55 | Ultimaex | lol |
| 17:47.55 | Markinus | Willow: you have to add there the virstual address of you ramcosole location |
| 17:49.51 | *** join/#htc-linux gauner1986 (~Miranda@p508C6C81.dip.t-dialin.net) |
| 17:50.27 | *** join/#htc-linux Downy (~Downy@p5DF57027.dip.t-dialin.net) |
| 17:50.27 | Markinus | Willow: the other goot thing for debuuging ios a visual or vibration signal what you can add in the machine init stuff. |
| 17:50.42 | Markinus | Willow: if you know how you can activate vibration on your device |
| 17:50.54 | Markinus | or of you've a camera led |
| 17:50.54 | gauner1986 | hi |
| 17:51.05 | Markinus | hi |
| 17:51.12 | gauner1986 | news? |
| 17:51.13 | gauner1986 | :) |
| 17:51.21 | Markinus | I had to revert our battery driver |
| 17:51.25 | Markinus | to many problems |
| 17:51.29 | gauner1986 | hum?? |
| 17:51.34 | gauner1986 | working fine for me |
| 17:51.44 | Markinus | have to find more about the physics of our battery |
| 17:51.54 | Markinus | gauner1986: you think that! :) |
| 17:52.02 | gauner1986 | well it's working BETTER than the old one |
| 17:52.24 | Markinus | gauner1986: it shows 10% LESS as wince |
| 17:52.28 | Markinus | if we have 90% |
| 17:52.32 | Markinus | wince shows 100 |
| 17:52.34 | Markinus | not good |
| 17:52.53 | gauner1986 | so lets just add 10% |
| 17:52.54 | gauner1986 | :D |
| 17:52.55 | Markinus | gauner1986: the last modified from me worked good too |
| 17:53.27 | Markinus | gauner1986: and there was something about notifications |
| 17:53.34 | gauner1986 | hm? |
| 17:53.36 | Markinus | gauner1986: it seems i works if the cable is in on boot |
| 17:53.41 | gauner1986 | wtf |
| 17:54.15 | mdeejay | :) |
| 17:54.30 | gauner1986 | so sense is giving the correct information then? |
| 17:54.51 | LeTama | Markinus, couldn't wince driver be less reliable ? |
| 17:55.01 | Markinus | LeTama: battery? |
| 17:55.06 | LeTama | yes |
| 17:55.23 | LeTama | after all, ce driver is quite old now |
| 17:55.48 | Markinus | LeTama: I dodn'T know. But the new driver need coefficients for voltage correction. They are battery specific. We used the one from desire HD 1230 mAh batterie and seems it's different |
| 17:56.14 | Willow | I've been trying to use the green/orange indicator led which I can control from haretconsole. I modified kernel to turn off the led before uncompressing the kernel and it never turned off the led. Since that is as early in the kernel boot process as I could get, I am tried to put the turn off led code in haret trampoline code. I suspect my assembly instructions are incorrect to do what I am trying to do since this is my first time using |
| 17:56.15 | Markinus | LeTama: we have tio find more about our battery our bevor we using it |
| 17:56.20 | gauner1986 | markinus: maybe they can be taken from ce driver? |
| 17:56.31 | LeTama | Markinus: ok, I see |
| 17:56.34 | Markinus | maybe, if it's done same way |
| 17:56.52 | *** join/#htc-linux Ultimaex (4d0c59b5@gateway/web/freenode/ip.77.12.89.181) |
| 17:56.53 | gauner1986 | well i'm fine with it atm |
| 17:57.16 | Markinus | LeTama: the latest driver morks nice . .and shows good values. Thew risk is smaller for overvcharging |
| 17:57.36 | LeTama | ok |
| 17:57.36 | FsTluxe | somone agree with my method installing Modules @ Leo Ubuntu Build? Ive compiled kernel with some changes. So I'm installing the modulles first mounting the .ext2 in ubuntu then i do this: -----sudo make modules_install prefix="/home/fst/mnt"----- |Is this good method:)? |
| 17:57.38 | gauner1986 | i disliked the old battery drivers behavior to stop charging when current is 5 and if you plug in the cable again shortly after |
| 17:57.42 | gauner1986 | it starts charging again |
| 17:58.49 | *** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@89.32.146.153) |
| 17:59.09 | FsTluxe | I'm doubt its good or not..need confirm.. |
| 17:59.45 | *** join/#htc-linux AgentBlair (~AgentBlai@adsl-69-108-49-55.dsl.sndg02.pacbell.net) |
| 18:00.09 | gauner1986 | Markinus: at what current does the new battery driver stop to charge? |
| 18:00.15 | Arash18k | FsTluxe, use INSTALL_MOD_PATH=/path/you/want/your/module/go |
| 18:00.16 | Markinus | voltage |
| 18:01.43 | Arash18k | FsTluxe, in your case sudo make modules_install INSTALL_MOD_PATH="/home/fst/mnt |
| 18:07.03 | *** join/#htc-linux mastermerlin (~Adium@p4FEE4FBC.dip.t-dialin.net) |
| 18:08.01 | gauner1986 | Markinus: http://forum.xda-developers.com/showpost.php?p=9208297&postcount=192 <- did you take a look at his g-sensor freezes patch ? |
| 18:08.24 | *** join/#htc-linux threeagle (~3agle@cpe-76-181-77-22.columbus.res.rr.com) |
| 18:10.00 | *** join/#htc-linux JesusFreak316 (~JesusFrea@pool-173-65-109-252.tampfl.fios.verizon.net) |
| 18:10.29 | Echo31 | cr2_ Hi |
| 18:10.58 | cr2_ | Echo31: i've found some tffs code for mdoc g3/g4 |
| 18:11.23 | cr2_ | Echo31: but it's not exactly what is needed. still very useful |
| 18:11.50 | cr2_ | mainly for mdoc h3 |
| 18:12.18 | cr2_ | although the main code structure looks similar to the disassembled g3 and g3 drivers |
| 18:13.10 | Markinus | gauner1986: ahh now the sources, ok will take a look |
| 18:13.11 | Echo31 | cr2_: G4 is it more complex than G3? |
| 18:14.11 | cr2_ | some registers are at a different place |
| 18:15.21 | *** join/#htc-linux BbLugNut|2 (~kvirc@108.109.214.18) |
| 18:15.41 | cr2_ | http://hands.com/~lkcl/hp6915/g4.c |
| 18:16.47 | *** join/#htc-linux Praveen (75c788dc@gateway/web/freenode/ip.117.199.136.220) |
| 18:17.47 | Echo31 | cr2_: assembler code ! |
| 18:18.34 | cr2_ | yeah. but the g3.c is already converted into c |
| 18:18.48 | cr2_ | so you only need to watch for differences |
| 18:18.56 | cr2_ | http://hands.com/~lkcl/hp6915/g3.c |
| 18:19.59 | cr2_ | btw, it is also possible to add mdoc functions to haret |
| 18:23.31 | eR^Z` | in case you haven't seen yet .. http://www.youtube.com/watch?v=Eq3CuMDXaPs :K |
| 18:27.33 | *** join/#htc-linux memin1857 (~memin1857@178.244.240.81) |
| 18:28.29 | *** join/#htc-linux Pkirsche (~Downy@p5DF57027.dip.t-dialin.net) |
| 18:28.36 | *** join/#htc-linux |Jeroen| (~jeroen@d5152B6A8.access.telenet.be) |
| 18:29.38 | Echo31 | cr2_: what is the similar driver ? MTD_NAND_DISKONCHIP ? |
| 18:30.49 | *** join/#htc-linux avinashhm (~avinash-h@192.163.20.231) |
| 18:32.30 | *** join/#htc-linux jiogi (~jiogi@212.50.115.55) |
| 18:33.27 | *** join/#htc-linux netson (~netson@125.161.196.242) |
| 18:36.58 | *** join/#htc-linux Josh13x12 (~josh13x12@99-190-187-250.lightspeed.lsvlky.sbcglobal.net) |
| 18:52.12 | *** join/#htc-linux apt (~apt@rikers.org) |
| 18:52.12 | *** 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 |
| 18:52.19 | gauner1986 | ah |
| 18:52.20 | gauner1986 | apt |
| 18:52.20 | gauner1986 | <3 |
| 18:53.53 | eR^Z` | http://kecy.roumen.cz/God_troll.jpg |
| 18:54.45 | *** join/#htc-linux programmer8922 (~Evan@67.219.166.182) |
| 18:55.48 | *** join/#htc-linux Alex[sp3dev] (~alexander@91.209.218.137) |
| 18:56.31 | Alex[sp3dev] | hey Willow |
| 18:59.49 | Alex[sp3dev] | if you still care for that asm, that should be.. mov r0, #0xa0000000; orr r0, r0, #0x9000000; orr r0, r0, #0x900000; mov r1, #0x1cc; str r1, [r0]. just make sure that it is a phys addr, since mmu will be off |
| 19:05.11 | *** join/#htc-linux TheDeadCPU (~TheDeadCP@89-162-46-133.insignal.net) |
| 19:06.08 | *** join/#htc-linux t3g (3e9e2bd8@gateway/web/freenode/ip.62.158.43.216) |
| 19:18.53 | *** part/#htc-linux ts0cha0tik (~ts0cha0ti@254-44.125-70.tampabay.res.rr.com) |
| 19:20.00 | *** join/#htc-linux ts0cha0tik (~ts0cha0ti@254-44.125-70.tampabay.res.rr.com) |
| 19:26.32 | *** part/#htc-linux dan1j3l (~danijel@78-1-143-233.adsl.net.t-com.hr) |
| 19:29.35 | *** join/#htc-linux jonolo (574b8b38@gateway/web/freenode/ip.87.75.139.56) |
| 19:37.27 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
| 19:40.06 | *** join/#htc-linux RaiderX (~RaiderX@109.180.71.89) |
| 19:40.21 | *** join/#htc-linux the_eye_ (~dimitris@78-211-216.adsl.cyta.gr) |
| 19:43.30 | *** join/#htc-linux [acl] (~abel@cpe-69-203-141-229.si.res.rr.com) |
| 20:05.03 | *** join/#htc-linux TiTidom (~TiTidom@lon92-8-88-165-13-68.fbx.proxad.net) |
| 20:07.45 | [acl] | phh: you around ? |
| 20:09.07 | *** join/#htc-linux vart (~Alexander@79.135.222.215) |
| 20:10.02 | *** part/#htc-linux vart (~Alexander@79.135.222.215) |
| 20:16.00 | *** join/#htc-linux wish34 (~wishmaste@5e069895.bb.sky.com) |
| 20:27.33 | *** join/#htc-linux zoraz (~chatzilla@202.70.54.207) |
| 20:29.47 | *** join/#htc-linux RaiderX (~RaiderX@109.180.24.135) |
| 20:38.59 | *** join/#htc-linux b-maximenko (5bd2a5fa@gateway/web/freenode/ip.91.210.165.250) |
| 20:42.58 | *** part/#htc-linux t3g (3e9e2bd8@gateway/web/freenode/ip.62.158.43.216) |
| 20:46.32 | *** join/#htc-linux IFailStuff (~IFail@unaffiliated/ifailstuff) |
| 20:46.53 | *** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821) |
| 20:47.11 | *** join/#htc-linux phantomcircuit (~phantomci@adsl-99-157-75-203.dsl.pltn13.sbcglobal.net) |
| 21:06.26 | *** join/#htc-linux Rob2222 (~Miranda@p4FFF34AB.dip.t-dialin.net) |
| 21:10.31 | *** join/#htc-linux EdangeL (~EdangeL@adsl-136.109.242.192.tellas.gr) |
| 21:12.32 | *** join/#htc-linux Curious_ (51064e08@gateway/web/freenode/ip.81.6.78.8) |
| 21:13.04 | Curious_ | Markinus, about desire HD battery driver, it doesn't show different values in wince and android for me |
| 21:13.18 | Curious_ | i use a desire / sense build |
| 21:13.32 | gauner1986 | maybe they become different after a while |
| 21:13.39 | gauner1986 | just like the problem we had before |
| 21:13.46 | gauner1986 | but different |
| 21:13.47 | gauner1986 | :P |
| 21:13.55 | Curious_ | but there was one issue yesterday, after using android for 2-3 days, i kept it charging on usb in wince |
| 21:14.11 | Curious_ | when it was 100%, amber led started to blink |
| 21:14.20 | Curious_ | battery was hot |
| 21:14.24 | Rajko | gauner1986, WHY DID WE REVERT |
| 21:14.27 | Rajko | MARKINUS |
| 21:14.28 | Rajko | WHY REVERT |
| 21:14.32 | Rajko | WHOLE TEAM IS BABIES |
| 21:14.35 | Curious_ | when i unplugged it, blinking gone |
| 21:14.42 | *** join/#htc-linux Andreyxxl[HD2EU] (Andreyxxl@89.32.146.153) |
| 21:15.03 | Rajko | its obviously fine ifyou dont use wince. |
| 21:15.07 | Curious_ | i disabled charging and connected usb to be sure, and it proved that it was trying to overcharge in wince |
| 21:15.15 | Curious_ | but i dunno why, it was showing 100% |
| 21:15.15 | Rajko | havent had any problems with dhd batter |
| 21:15.40 | Curious_ | Rajko, but markinus says we are not filling up fully |
| 21:15.53 | gauner1986 | rajko: i didn't want to revert, it was markinus decision :P it was also fine for me in all terms.. but markinus just noticed some difference in percentage shown between ce and linux |
| 21:16.06 | Rajko | probably because you shouldnt be using both |
| 21:16.18 | Rajko | better than random 30% |
| 21:16.21 | Rajko | then back to 100% |
| 21:16.24 | Rajko | when its actually 50% |
| 21:16.30 | gauner1986 | yeah |
| 21:16.32 | gauner1986 | it's way better |
| 21:16.53 | Rajko | 4074mV |
| 21:16.57 | Rajko | 94% |
| 21:17.11 | Curious_ | 4.1 was 100% right,? |
| 21:17.15 | Rajko | 4.2 |
| 21:17.26 | jiogi | Rajko: he did it because there is a possibility that it is overcharging with the DHD new driver. once its investigated he will do the necessary changes. |
| 21:17.26 | gauner1986 | 4137 or so |
| 21:17.48 | Curious_ | 4137 at 100% ? |
| 21:17.56 | gauner1986 | shouldn't it be protected against overcharging by hardware? |
| 21:17.56 | Rajko | it gets hot the first time you plug it n |
| 21:18.00 | Rajko | after reflash |
| 21:18.08 | Rajko | but after that its gravy |
| 21:18.14 | Curious_ | it doesn't get hot in android at all |
| 21:18.36 | Curious_ | and "hot" is relative.. |
| 21:19.30 | Curious_ | has anybody tested this i2c hack? |
| 21:19.40 | gauner1986 | anyway |
| 21:19.45 | gauner1986 | i'll stick to the dhd driver |
| 21:20.00 | *** join/#htc-linux the_eye_ (~dimitris@78-211-216.adsl.cyta.gr) |
| 21:21.23 | jiogi | Curious_: ive tested it, it seems to be working.. not sure if its the proper way though |
| 21:21.23 | Rajko | ive remmoveed battery and rebooted |
| 21:21.37 | Rajko | now at 99% at 4047mV |
| 21:21.46 | Curious_ | jiogi: it is not the proper way but seems fine for now.. |
| 21:21.58 | jiogi | yeap, m using it |
| 21:22.06 | jiogi | temporary i hope |
| 21:22.11 | gauner1986 | rajko: so it's not perfect, but better than the other one :D |
| 21:22.13 | Curious_ | and are you sure that it is the highest value that your battery can take? |
| 21:22.31 | Curious_ | your battery life may have degraded? |
| 21:24.17 | jiogi | 4.182V just booted with custom battery driver. i charged it while was totally turned OFF and booted with cable on |
| 21:24.40 | jiogi | even though 100% it says: Charging and orange LED is on |
| 21:24.47 | Rajko | yeah ? |
| 21:24.51 | Rajko | it will trickle charge untill 4.2v |
| 21:24.56 | Rajko | and low low current |
| 21:25.18 | Curious_ | 4.023 = 79% in wince |
| 21:25.33 | Rajko | 98% at 4108mV now |
| 21:25.52 | Curious_ | is the percentage calculated linearly? |
| 21:26.04 | Curious_ | (max-min)/total interval * 100 ? |
| 21:26.24 | Curious_ | apt: s/max/present |
| 21:26.30 | Rajko | no. |
| 21:26.30 | gauner1986 | i guess it's calculated way more complex |
| 21:26.40 | Curious_ | it doesn't seem linear |
| 21:26.45 | Curious_ | at least for wince |
| 21:27.31 | Curious_ | (present-min)/(max-min)*100 gives 65% but wince says 79% |
| 21:27.43 | Rajko | Curious_, HERP |
| 21:27.43 | Curious_ | if max and min are exactly 4.2 and 3.7 respectively |
| 21:27.48 | Rajko | 3.6 |
| 21:27.56 | Curious_ | oh |
| 21:28.44 | Curious_ | still wrong |
| 21:28.49 | Curious_ | with 9% error |
| 21:28.58 | Curious_ | what is the proper way to calculate it? |
| 21:29.33 | Rajko | you cant |
| 21:30.28 | *** join/#htc-linux Curious__ (51064e08@gateway/web/freenode/ip.81.6.78.8) |
| 21:30.29 | *** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey) |
| 21:31.50 | Curious__ | rajko: i can't what? |
| 21:32.10 | Rajko | calculate |
| 21:32.18 | Curious__ | why not |
| 21:32.33 | Curious__ | don't we have the formula somewhere? |
| 21:32.41 | gauner1986 | in the ce battery driver |
| 21:32.42 | gauner1986 | ? |
| 21:32.43 | gauner1986 | ^^ |
| 21:33.01 | Curious__ | cotulla looked at it and his percentage calculation was wrong? :P |
| 21:33.06 | gauner1986 | not sure if they do the same calculation |
| 21:33.13 | gauner1986 | it was incomplete |
| 21:33.16 | gauner1986 | not wrong |
| 21:33.29 | Curious__ | hmm |
| 21:35.04 | Rajko | gauner1986, it never overcharged for me |
| 21:35.07 | Rajko | and i leave it at night |
| 21:35.11 | gauner1986 | yeah |
| 21:35.14 | Jack-E | likewise |
| 21:35.17 | gauner1986 | me either |
| 21:35.18 | Rajko | it says 0mA in currentwidget when its like that |
| 21:35.20 | Curious_ | go to wince and see for yourself |
| 21:35.25 | gauner1986 | led is green |
| 21:35.37 | gauner1986 | charger is in powering only state |
| 21:36.09 | jiogi | guys, i ve upgraded to latest kernel from git, and camera app wont load, i ve copied the 2 files in lib directory, i ve created the links from 0 to 1,,, what else? |
| 21:36.34 | Rajko | you need to create the links every boot. |
| 21:36.39 | Rajko | put it in an initscript |
| 21:36.43 | Curious_ | you should not open app before creating links |
| 21:36.48 | jiogi | oh ok |
| 21:36.49 | Curious_ | and what rajko said.. |
| 21:36.53 | jiogi | i didn |
| 21:37.12 | Rajko | also use all files with camera in their name from desire |
| 21:37.20 | Rajko | and all omx files except videnc |
| 21:37.33 | jiogi | ok.. |
| 21:37.56 | jiogi | thx |
| 21:38.48 | gauner1986 | seems we really need a wiki for this |
| 21:38.49 | gauner1986 | :P |
| 21:38.52 | gauner1986 | or |
| 21:38.54 | gauner1986 | wiki entries |
| 21:39.05 | Curious_ | yes |
| 21:39.07 | Curious_ | gn |
| 21:39.24 | Curious_ | get monitor mode on for bcm4329 |
| 21:39.27 | gauner1986 | if all of us htc-linux nerds would leave today, nobody would know anything |
| 21:39.29 | Curious_ | !!!!^!^!^!^! |
| 21:41.14 | Markinus | Rajko: BABIES? ehh, you're the granddad or what?!? |
| 21:41.51 | Rajko | http://www.youtube.com/watch?v=GXLDFNcDHao |
| 21:42.26 | arrrghhh | gauner1986, i don't know anything and you're still here. |
| 21:42.58 | Rajko | Markinus, whats problem with dhd battery |
| 21:43.12 | Markinus | Rajko: if you look to the driver than you can see we have to change much things bevor we can realy use it correctly |
| 21:43.26 | *** join/#htc-linux v1nsai (~v1nsai@ip68-228-16-26.pn.at.cox.net) |
| 21:43.30 | Markinus | Rajko: first, there is a autodetection for batteries |
| 21:43.47 | Markinus | Rajko: this is done over the read of the 2nd aux register (adc) |
| 21:43.53 | *** join/#htc-linux Neo31 (~Neo31@unaffiliated/neo31) |
| 21:44.01 | Markinus | Rajko: on desire HD it's the internal resistor of the battery |
| 21:44.10 | Markinus | something from 5k -> 50kOhm |
| 21:44.21 | Markinus | Rajko: we get there something ehh. . 150 . . . |
| 21:44.27 | Markinus | Rajko: so it's totaly different |
| 21:44.45 | Markinus | Rajko: second, for the calculations there are coeficients for voltage correction |
| 21:44.59 | Markinus | Rajko: they are totaly wrong it seems |
| 21:45.10 | gauner1986 | arrrghhh: you haven't asked enough :P |
| 21:45.12 | Markinus | Rajko: there 1230 mA battery is completly different to our |
| 21:45.17 | arrrghhh | lol |
| 21:45.57 | *** part/#htc-linux Arash18k (~Arash18k@85.133.200.152) |
| 21:46.08 | gauner1986 | Markinus: but i don't get what's better on the old driver? |
| 21:46.08 | Markinus | Rajko: I would say the old driver is for first better, we know what there happend, we have to clean and get this new driver realy good to work and add it new then |
| 21:46.08 | *** join/#htc-linux kiozen (~kiozen@rgnb-5d87dbc1.pool.mediaWays.net) |
| 21:46.11 | Rajko | battery is SPY ! |
| 21:46.39 | *** join/#htc-linux phantomcircuit (~phantomci@adsl-99-157-75-203.dsl.pltn13.sbcglobal.net) |
| 21:46.41 | gauner1986 | Markinus: i guess it also has some incomplete formulas / wrong values |
| 21:47.18 | Markinus | gauner1986: yo don't know what the new one did with our battery .. . |
| 21:47.40 | gauner1986 | you do? how do you know they are incorrect? |
| 21:47.41 | gauner1986 | :) |
| 21:47.52 | Rajko | it seems to work much better man |
| 21:47.57 | Markinus | gauner1986: If you all want to use the new one, ok, but I'm for it to get it real good to work first |
| 21:48.29 | gauner1986 | Markinus: i don't say it's perfect.. but i say it's working better than the old one... |
| 21:48.55 | *** join/#htc-linux TheDeadCPU (~TheDeadCP@89-162-46-133.insignal.net) |
| 21:49.38 | *** join/#htc-linux manusfreedom_ (~manusfree@tra78-1-82-235-115-79.fbx.proxad.net) |
| 21:51.29 | *** join/#htc-linux Chalkster (~Chalkster@cpc1-ando4-0-0-cust799.15-1.cable.virginmedia.com) |
| 21:52.43 | Markinus | ok, I you all want to use the new one, then I do tomorrow a new clean commit with all changed in one. But we have to disable the battery detection and do it staticly |
| 21:53.11 | Markinus | and the coefficient . .hmmm . .we could try which are the best . .but how? |
| 21:53.28 | gauner1986 | Markinus: not the problem.. battery detection isn't working anyway? |
| 21:53.38 | Markinus | no |
| 21:54.08 | Markinus | wince see the internal resistance of the batterie in a other wys, till now I could find out how they do it |
| 21:54.23 | gauner1986 | anyone knows what sense this could make? |
| 21:54.23 | gauner1986 | - (loops_per_jiffy/(5000/HZ)) % 100, loops_per_jiffy); |
| 21:54.23 | gauner1986 | + (loops_per_jiffy * 10 /(50000/HZ)) % 100, loops_per_jiffy); |
| 21:54.26 | Markinus | couldn't |
| 21:55.45 | gauner1986 | wanna try the brainfuckscheduler |
| 21:55.46 | gauner1986 | :) |
| 21:56.44 | *** join/#htc-linux TheDeadCPU (~TheDeadCP@89-162-46-133.insignal.net) |
| 22:04.22 | *** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey) |
| 22:06.13 | Rajko | gauner1986, loops per jiffy is classic |
| 22:06.56 | *** join/#htc-linux raymonddull (~raymonddu@24-247-53-174.dhcp.monr.mi.charter.com) |
| 22:07.04 | gauner1986 | Markinus: they got weird formulas for everything? :D |
| 22:07.31 | Markinus | hehe :) |
| 22:15.21 | *** join/#htc-linux Regulator (~duffman@c-67-162-193-231.hsd1.ar.comcast.net) |
| 22:19.33 | *** join/#htc-linux [acl] (~abel@cpe-69-203-141-229.si.res.rr.com) |
| 22:28.46 | *** join/#htc-linux Bally3_ (5000b457@gateway/web/freenode/ip.80.0.180.87) |
| 22:30.23 | phh | [acl]: i'm there |
| 22:35.11 | [acl] | phh: need ideas bro.. |
| 22:35.19 | phh | ok, about what ? |
| 22:35.45 | [acl] | phh: so i got the .35 fb to compile but im getting lockedup somewhere. without fb i cant really debug. trying to figure out how to dump ramconsole now |
| 22:36.00 | phh | ~ramconsole |
| 22:36.00 | apt | extra, extra, read all about it, ramconsole is pwf dm 0x8e0000 0x20000 |
| 22:36.01 | phh | like that ? |
| 22:36.17 | [acl] | huh? explain |
| 22:36.36 | phh | haha |
| 22:36.37 | phh | no. |
| 22:36.38 | phh | sorry |
| 22:36.40 | phh | stupid brain |
| 22:36.57 | phh | [acl]: ask cmonex/olipro |
| 22:37.09 | [acl] | ok |
| 22:37.24 | [acl] | i know its clock related so im didding in there |
| 22:37.34 | [acl] | *digging |
| 22:39.03 | phh | well I meant for the "dump ramconsole" part |
| 22:39.11 | phh | they know what to tell to spl |
| 22:43.20 | *** part/#htc-linux jiogi (~jiogi@212.50.115.55) |
| 23:09.26 | Markinus | night |
| 23:09.40 | gauner1986 | goodnight |
| 23:25.21 | *** join/#htc-linux Necrosan (~necrosan@unaffiliated/necrosan) |
| 23:37.59 | *** join/#htc-linux AgentBlair (~AgentBlai@adsl-69-108-49-55.dsl.sndg02.pacbell.net) |
