| *** Entropy512 is now known as gtg465xxx | 00:04 | |
| *** gtg465xxx is now known as Entropy512 | 00:05 | |
| *** arrrghhh has quit IRC | 00:17 | |
| *** NeoMatrixJR has quit IRC | 00:39 | |
| *** NeoMatrixJR has joined #xdandroid | 00:39 | |
| *** NeoMatrixJR2 has joined #xdandroid | 00:46 | |
| *** NeoMatrixJR has quit IRC | 00:46 | |
| *** ORi| has quit IRC | 00:52 | |
| *** NeoMatrixJR has joined #xdandroid | 00:55 | |
| *** NeoMatrixJR2 has quit IRC | 00:57 | |
| *** CazH has joined #xdandroid | 02:09 | |
| *** programmer8922 has joined #xdandroid | 02:09 | |
| *** GPFerror has quit IRC | 02:17 | |
| *** GPFerror has joined #xdandroid | 02:17 | |
| *** CazH has quit IRC | 02:32 | |
| *** CazH has joined #xdandroid | 02:42 | |
| *** GlemSom has joined #xdandroid | 03:24 | |
| lotjuh | hyc: I formatted my disk with the hp tool again and then re-install 07 on it with the latest kernel and rootfs | 05:42 |
|---|---|---|
| lotjuh | then at the first boot it rebooted when I had to enter my pincode to unlock my sim | 05:42 |
| lotjuh | but after the reboot I started android again and it worked without problems | 05:42 |
| lotjuh | but now, after a couple of hours, the green led became a red led when the screen was in sleep mode | 05:43 |
| lotjuh | and the battery died again over night | 05:43 |
| *** arrrghhh has joined #xdandroid | 05:58 | |
| arrrghhh | lotjuh, first you shouldn't be using a SIM PIN | 05:59 |
| arrrghhh | that's probably one issue | 05:59 |
| arrrghhh | second, the green LED can change color when it's sleeping - if the phone is syncing, etc it will have to wake | 05:59 |
| arrrghhh | it should go back to green tho | 06:00 |
| lotjuh | uhm, there's always a pincode to unlock your simcard | 06:00 |
| lotjuh | it comes from T-mobile with a pincode | 06:00 |
| lotjuh | the only thing you cn do is change th code on it | 06:00 |
| lotjuh | as far as I know | 06:00 |
| arrrghhh | no clue | 06:00 |
| arrrghhh | i heard having a SIM PIN is a bad idea tho | 06:00 |
| lotjuh | why? | 06:00 |
| arrrghhh | and from what i gleaned, it's configured in winmo | 06:01 |
| arrrghhh | i'm pretty sure you demonstrated why... | 06:01 |
| lotjuh | haha, ok | 06:01 |
| arrrghhh | my carrier doesn't use SIM's, so I am not sure | 06:01 |
| arrrghhh | all I know is what I've been told on this subject | 06:01 |
| lotjuh | so there's more ppl who have their android reboot when entering their pin? | 06:01 |
| arrrghhh | which I'm regurgitating to you. | 06:01 |
| arrrghhh | i haven't spoke with anyone in a while who has used a SIM PIN | 06:01 |
| arrrghhh | but everyone's conclusion was "don't use it" | 06:02 |
| lotjuh | I'm confues, I'm not even sure we're talking about the same pin code here | 06:02 |
| lotjuh | cause litterly -everybody- I know uses a pin code to unlock their simcard | 06:02 |
| arrrghhh | you shouldn't use any PIN codes in Android | 06:02 |
| arrrghhh | i've never used any PIN code | 06:02 |
| lotjuh | there's also a custom pincode you can set, I haven't done that | 06:02 |
| arrrghhh | how many of those people run Android on a WinMo phone? | 06:03 |
| lotjuh | it's just the code you have to enter to unlock your simcard, that code is even stored on your simcard | 06:03 |
| arrrghhh | ... | 06:03 |
| arrrghhh | i know what the SIM PIN is. | 06:03 |
| arrrghhh | i've just heard from many people to simply not use it | 06:03 |
| lotjuh | well, since you say you don't know anyone who's still using it, it made me really wonder if we're talking about the same thing here | 06:03 |
| arrrghhh | on XDAndroid | 06:04 |
| lotjuh | well can you tell me how to remove this pin code then? | 06:04 |
| arrrghhh | my carrier doesn't use SIM cards | 06:04 |
| arrrghhh | i'd assume it's a standard process for all GSM carriers | 06:07 |
| arrrghhh | also, on battery life - there's so many factors that determine good or bad batt life | 06:08 |
| arrrghhh | assuming you're in a good service area | 06:08 |
| *** panda84kde has joined #xdandroid | 06:08 | |
| arrrghhh | and you don't have a boatload of apps syncing constantly | 06:08 |
| arrrghhh | you *should* get 12+hrs | 06:08 |
| lotjuh | I haven't installed any extra apps | 06:09 |
| lotjuh | and I'm not using data | 06:09 |
| lotjuh | cause it's not in my subscriptions | 06:09 |
| lotjuh | so it can't be syncing stuff | 06:09 |
| lotjuh | I'm not calling with it either | 06:10 |
| lotjuh | does a bad service area make it have a red led when in sleep mode? | 06:10 |
| arrrghhh | not necessarily | 06:11 |
| arrrghhh | but a bad service area will drain any phone | 06:11 |
| arrrghhh | constantly searching for service | 06:11 |
| lotjuh | yeah, I know that | 06:11 |
| arrrghhh | barely getting service etc | 06:11 |
| arrrghhh | so.... why would you ask :P | 06:11 |
| lotjuh | the service it not too great here, but it's not constantly searching | 06:11 |
| arrrghhh | well i would say that's killing your battery then | 06:11 |
| lotjuh | well, cause the thing I noticed is that my pone keeps the red led on after a while | 06:12 |
| arrrghhh | if you have poor service, the radio will try to boost power | 06:12 |
| lotjuh | and it doesn't go back to green | 06:12 |
| arrrghhh | draining more battery | 06:12 |
| lotjuh | so I'm wondering what it's doing then | 06:12 |
| arrrghhh | hrm | 06:12 |
| arrrghhh | there's a few things that kill sleep | 06:12 |
| arrrghhh | BT on in WinMo when you boot haret | 06:12 |
| arrrghhh | a stupid app | 06:12 |
| arrrghhh | or GPS | 06:12 |
| arrrghhh | those are the only things I've found that kill sleep in FRX07 | 06:12 |
| lotjuh | hm | 06:13 |
| arrrghhh | does this happen in airplane mode? | 06:13 |
| arrrghhh | that would probably be the best test. | 06:13 |
| lotjuh | I will test that once my battery got charged a bit again yeah (-: | 06:14 |
| arrrghhh | k | 06:15 |
| arrrghhh | 4am here, bedtime | 06:15 |
| *** arrrghhh has quit IRC | 06:15 | |
| *** panda84kde has quit IRC | 06:39 | |
| *** emwe has joined #xdandroid | 09:20 | |
| *** virsys has joined #xdandroid | 09:49 | |
| D3tul3 | hi emwe | 10:33 |
| emwe | hi D3tul3. read your comments :) | 10:56 |
| D3tul3 | oh yeah...well learned a few things about i2c drivers these past couple of days | 11:13 |
| D3tul3 | at least one good thing came out of this exercise :) | 11:13 |
| D3tul3 | couldn't you incorporate microp-ksc for rhod much in the same way as you've done with led -> i.e. with a board file driven by microp-ng | 11:14 |
| emwe | the thing is, if you wan't led management code in one place, you need two i2c clients. e.g. topa button backlight is controlled by the klt client, rhod by the ksc client. | 11:18 |
| emwe | the rest is all klt. i need to figure a way of getting both in there. | 11:19 |
| emwe | i am just looking into h2w headset which is broken since the 35mm establishment. | 11:21 |
| D3tul3 | yeah i've been looking at your tree so much i am becoming intimately familiar with your commits | 11:22 |
| emwe | the led file base is courtesy of alex, though ;) | 11:23 |
| emwe | did some extension and renaming. | 11:23 |
| emwe | if you cna get amber and green led into microp-klt, it should be fine. | 11:23 |
| emwe | you "just" need the hooks. | 11:23 |
| emwe | liblights uses these two sysfs led devices if present. | 11:23 |
| emwe | so you could extend the led array with green and amber, provide the brightness_set hooks and be done. | 11:24 |
| D3tul3 | i am trying to add some code in klt so that it checks for platform_data in the client and acts accordingly | 11:24 |
| emwe | not required if i am not mistaken. | 11:24 |
| D3tul3 | much like microp_ng, that way i can just pass topaz-led | 11:25 |
| emwe | nah, do't use that topaz-led thingy... | 11:25 |
| emwe | that's just an intermediary step. i'd like to establish an led framework somehow with more board specific pdata involvment. but i just dunno what's reguired in total, that's why it is that bitch what it is now. | 11:25 |
| emwe | in the opposite one could just instantiate a shitload of board-specific led-setteing hooks which i'd like to avoid. | 11:26 |
| D3tul3 | but i think that's better than dumping device specific code in klt | 11:26 |
| D3tul3 | i'd rather dump the device specific code in a board file like rhodium-led or topaz-led | 11:27 |
| D3tul3 | and keep the i2c driver generic like microp-ng | 11:27 |
| emwe | yes, but what i dislike is copying 99% of the management code. | 11:27 |
| emwe | i though of somehow have in pdata defined what i2c lcient to use and what kind of data to pass | 11:28 |
| D3tul3 | that sounds pretty good | 11:29 |
| D3tul3 | do it:) | 11:29 |
| emwe | so we only have a callback which then instructs a common led driver which client to use, what data to send (buf array) and initially tells the callback what the last and now to be set brightness is. | 11:30 |
| emwe | yeah, that's the plan. | 11:30 |
| emwe | but for .27/3.0/.39 you can extends micropklt->leds array with red and green, increase the LED_CNT by 2 and register these, and then extend micropklt_led_brightness_set() or provide a custom one. | 11:31 |
| emwe | on the other hand, i dunno what happens to the other devices if liblights detects these two led devices. | 11:31 |
| emwe | have a look at liblights in xdandroid. | 11:32 |
| D3tul3 | yeah i haven't graduated to the userland side of things | 11:33 |
| emwe | it get's you easily distracted :) | 11:35 |
| emwe | what rhod variant are you on D3tul3? | 11:36 |
| D3tul3 | ok emwe so pretend like i am a 5 yr old, i see these suspend and resume functions in klt (or topaz-led) that set the led to green/amber or whatever....where do these functions get called? | 11:37 |
| D3tul3 | 400/Sprint | 11:37 |
| emwe | Detule: suspend and resume are kernel triggered. these are just for telling drivers that system is going suspend/resume. | 11:38 |
| emwe | Detule: the actual hooks for setting brightness on an led device are the brightness_set assignemnts to the actual led device itself. | 11:39 |
| emwe | let's assume you wan't it for the old microp-klt... one sec... | 11:39 |
| *** CazH has quit IRC | 11:39 | |
| emwe | line 738ff: data->leds[0].brightness_set | 11:40 |
| emwe | this sets the callback which is called whenever somebody writes (liblights or you echoing) to /sys/class/leds/<led-name>/brightness | 11:40 |
| D3tul3 | ok that's in probe | 11:40 |
| emwe | you can pass a customer hook | 11:41 |
| D3tul3 | which gets called in init right? | 11:41 |
| emwe | s/customer/custom | 11:41 |
| emwe | yap | 11:41 |
| *** CazH has joined #xdandroid | 11:41 | |
| emwe | so extends micropklt->leds array by two and register two more leds (increase MICROP_KLT_LED_CNT, too) | 11:42 |
| D3tul3 | ok so this should create the led devices so that userland can interact with them right? | 11:42 |
| emwe | exactly | 11:42 |
| emwe | if liblights finds them, it uses them. | 11:42 |
| D3tul3 | got it | 11:42 |
| emwe | liblights isn't as polished, but should do it just fine if it finds them. | 11:43 |
| emwe | as you don't need any fancy stuff which is done in the micropklt_led_brightness_set() you get much less trouble by providing a new set method. | 11:43 |
| D3tul3 | ok that makes sense | 11:44 |
| D3tul3 | now sorry to backtrack to my original question | 11:44 |
| emwe | that method could look like htctopaz_update_color_led() just with another argument list | 11:44 |
| D3tul3 | these suspend/resume functions in klt, on a kernel triggered suspend/resume get executed...do you know where in the kernel code i can see an example of that (pm.c?) | 11:45 |
| emwe | it's not in device/board specific code. kernel/power/* i think | 11:46 |
| emwe | btw, on resume on .27 topa get's that red led set... that's stupid. | 11:47 |
| D3tul3 | ok, and it doesn't matter that in your topaz-led code you've renamed these functions topaz*suspend something | 11:47 |
| emwe | these suspend/resume hooks are assigned to the pm strucutre in micropklt to tell the kernel which functions to use. | 11:47 |
| D3tul3 | oh | 11:47 |
| D3tul3 | got it | 11:47 |
| D3tul3 | .suspend = blahblah | 11:48 |
| D3tul3 | .resume = blahblah ok that makes sense | 11:48 |
| emwe | exactly | 11:48 |
| *** ringer has joined #xdandroid | 11:48 | |
| emwe | there's also the early/late variants which are called before/after suspend/resume | 11:48 |
| D3tul3 | k thanks for another lesson, family time | 11:49 |
| emwe | have fun! | 11:49 |
| emwe | going to get outta here likely as well | 11:49 |
| emwe | need some fresh air. | 11:49 |
| *** rpierce99 has joined #xdandroid | 12:42 | |
| *** rpierce99 has quit IRC | 12:43 | |
| *** CazH has quit IRC | 12:53 | |
| *** CazH has joined #xdandroid | 12:54 | |
| Tandyman100 | Wow. The Tilt2 has a FUBAR keyboard | 13:02 |
| Tandyman100 | what the flipping hell | 13:02 |
| *** CazH has quit IRC | 13:03 | |
| *** CazH has joined #xdandroid | 13:03 | |
| *** CazH has quit IRC | 13:05 | |
| *** CazH has joined #xdandroid | 13:06 | |
| *** ringer has quit IRC | 13:08 | |
| *** ORi|ON has joined #xdandroid | 13:35 | |
| *** ORi|ON has quit IRC | 13:36 | |
| *** vw_ has joined #xdandroid | 13:50 | |
| *** ringer has joined #xdandroid | 13:54 | |
| *** ringer has quit IRC | 14:26 | |
| *** ringer has joined #xdandroid | 14:49 | |
| *** programmer8922 has quit IRC | 15:12 | |
| *** vw_ has quit IRC | 15:18 | |
| *** ringer has quit IRC | 15:33 | |
| *** GlemSom has quit IRC | 16:14 | |
| *** emwe has quit IRC | 16:39 | |
| *** Tandyman100 has quit IRC | 17:12 | |
| *** krisse has joined #xdandroid | 17:16 | |
| krisse | hi all | 17:17 |
| krisse | I'm working on blackstone nand to get wifi | 17:17 |
| krisse | I have a question about calibration wifi file | 17:17 |
| *** Tandyman100 has joined #xdandroid | 17:17 | |
| krisse | the full 512mb nand on my blackstone does not contain that info when I'm booting into nand | 17:18 |
| krisse | however when putting windows mobile back and booting into android via haret | 17:18 |
| krisse | I have that information available | 17:18 |
| krisse | does this calibration info is writen by kernel to specific location? | 17:18 |
| phh | no | 17:20 |
| phh | but it's part of the windows rom | 17:20 |
| phh | so of course if you flash your nand | 17:20 |
| phh | you won't get the calibration | 17:20 |
| krisse | phh: aha | 17:28 |
| krisse | phh: how is it done in other devices then(windows mobile -> android) ? | 17:28 |
| krisse | phh: I have a kaizer also | 17:29 |
| phh | same calibration for everyone | 17:29 |
| krisse | phh: and there this part exists in nand | 17:29 |
| krisse | phh: meaning same mac adress to for everyone right? | 17:29 |
| phh | you can randomize it | 17:29 |
| krisse | phh: yep ok | 17:29 |
| krisse | phh: thx a lot | 17:29 |
| phh | but i'm just guessing | 17:29 |
| krisse | phh: the calibration file I have is binary | 17:30 |
| krisse | phh: took it from android running via haret | 17:31 |
| phh | well should be fine then | 17:31 |
| krisse | phh: so will not be easy to just replace mac address I think | 17:31 |
| krisse | phh: I try with this one already then | 17:31 |
| phh | ifconfig tiwlan0 mac xxxxxxxxx at startup ? | 17:31 |
| krisse | phh: thx | 17:31 |
| *** ringer has joined #xdandroid | 17:46 | |
| *** NeoMatrixJR_Mobi has joined #xdandroid | 18:35 | |
| *** arrrghhh has joined #xdandroid | 19:07 | |
| krisse | hi all | 19:16 |
| krisse | I managed to get wlan.ko partly loaded until the line initialized for nand blackstone | 19:17 |
| krisse | I used insmod wlan.ko to try that | 19:17 |
| krisse | but now it seems to be hanging | 19:17 |
| krisse | the module loading seems not to be exiting | 19:17 |
| krisse | this is the last line in dmesg | 19:18 |
| krisse | <6>[ 454.497741] TIWLAN: Driver initialized (rc 0) | 19:18 |
| krisse | when checking via other shell I see this | 19:18 |
| krisse | wlan 545572 1 - Loading 0xbf000000 | 19:18 |
| krisse | I see in c code that it seems top wait for sdio_wait return | 19:19 |
| stinebd | arrrghhh: i need you to grab a ramconsole dump for this atrix kernel and system combo... | 19:21 |
| arrrghhh | lolwut | 19:22 |
| krisse | phh: do you have an id for my question I posted here? | 19:46 |
| krisse | somebody else? | 19:58 |
| krisse | or at least give me a hint on where to look in kernel | 19:59 |
| *** Tandyman100 has quit IRC | 20:07 | |
| *** krisse has quit IRC | 20:27 | |
| *** JSkyhawk has joined #xdandroid | 20:32 | |
| *** JSkyhawk has left #xdandroid | 20:32 | |
| arrrghhh | tiad8's trolls are coming around here more and more... | 20:51 |
| *** arrrghhh has quit IRC | 21:37 | |
| *** NeoMatrixJR has quit IRC | 21:45 | |
| *** NeoMatrixJR_Mobi has quit IRC | 21:47 | |
| hyc | bummer | 22:10 |
| *** Miga has joined #xdandroid | 22:17 | |
| *** [7] has quit IRC | 22:38 | |
| *** TheSeven has joined #xdandroid | 22:38 | |
| *** D3tul3 has quit IRC | 22:54 | |
| *** rpierce99 has joined #xdandroid | 23:12 | |
| *** ringer has quit IRC | 23:35 | |
| *** rpierce99 has quit IRC | 23:41 | |
| *** Miga has quit IRC | 23:41 | |
| *** rpierce99 has joined #xdandroid | 23:42 | |
| *** programmer8922 has joined #xdandroid | 23:56 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!