arrrghhh | got a little worried there. | 00:00 |
---|---|---|
arrrghhh | wow it's going WAY faster now. | 00:00 |
arrrghhh | weird. | 00:01 |
arrrghhh | like 110kb/s vs 2mb/s lol | 00:01 |
arrrghhh | this should go much faster now lol | 00:02 |
arrrghhh | damnit. back to 100k. | 00:28 |
arrrghhh | i remember when i thought 10k was screamin LOL | 00:29 |
*** krog has quit IRC | 01:19 | |
*** hardwalker has joined #xdandroid | 01:24 | |
*** arrrghhh has quit IRC | 01:53 | |
*** krog has joined #xdandroid | 02:14 | |
*** camro has joined #xdandroid | 02:40 | |
*** zycho has joined #xdandroid | 02:57 | |
*** F22 has joined #xdandroid | 03:31 | |
*** dj6out has joined #xdandroid | 03:36 | |
*** dj6out is now known as dj6a | 03:37 | |
*** DidiVampire has joined #xdandroid | 03:53 | |
DidiVampire | Hi guys! | 03:53 |
*** kalemas has joined #xdandroid | 04:05 | |
*** dj6a has quit IRC | 04:08 | |
*** DidiVampire has left #xdandroid | 04:27 | |
*** kalemas has left #xdandroid | 05:01 | |
*** kalemas has joined #xdandroid | 05:07 | |
*** Ashar has joined #xdandroid | 05:09 | |
*** MegaMatze has joined #xdandroid | 05:18 | |
MegaMatze | hey guys, i just updated roofts, initrd and the new froyo 2.2.1 yesterday. now i have the problem that xdandroid doesnt start anymore... i only see the loading screen with the androids flying around all the time | 05:19 |
MegaMatze | whats the problem with it? | 05:19 |
*** leobaillard has joined #xdandroid | 05:23 | |
RogueAgent[tp2] | did you try deleting data.img? | 05:23 |
MegaMatze | thats the next thing i will try i think | 05:24 |
MegaMatze | had that as last exit | 05:25 |
MegaMatze | since i didnt want to loose all my data | 05:25 |
MegaMatze | but i guess there is no other choise | 05:25 |
RogueAgent[tp2] | pffft its android | 05:25 |
RogueAgent[tp2] | no such thing | 05:25 |
MegaMatze | ? | 05:25 |
RogueAgent[tp2] | loss of data | 05:26 |
MegaMatze | no? | 05:26 |
RogueAgent[tp2] | oh you'll lost it | 05:26 |
RogueAgent[tp2] | but its not htat hard to recover | 05:26 |
MegaMatze | oh okay | 05:26 |
RogueAgent[tp2] | contacts from gmail, applications from the market download list, email resyncs over once reset | 05:26 |
RogueAgent[tp2] | I make customers hard reset android phones all day | 05:27 |
RogueAgent[tp2] | takes like 10 minutes to resetup | 05:27 |
MegaMatze | oh okay | 05:27 |
MegaMatze | so just delete data.img | 05:27 |
MegaMatze | or anything else to delete? | 05:27 |
RogueAgent[tp2] | data.img afaik | 05:27 |
MegaMatze | okay | 05:28 |
MegaMatze | then ill try that now | 05:28 |
MegaMatze | thanks rogue | 05:28 |
MegaMatze | ;) | 05:28 |
RogueAgent[tp2] | i take no responsibilities for statements made | 05:28 |
*** MegaMatze has quit IRC | 05:28 | |
*** Ashar has quit IRC | 05:29 | |
*** TheDeadBOT has quit IRC | 05:33 | |
*** TheDeadBOT has joined #xdandroid | 05:34 | |
*** Ashar has joined #xdandroid | 05:35 | |
*** leobaillard has quit IRC | 05:37 | |
*** deadly` has joined #xdandroid | 05:39 | |
*** Ashar has quit IRC | 05:39 | |
*** deadly` has quit IRC | 05:39 | |
*** deadly` has joined #xdandroid | 05:39 | |
*** deadly` is now known as Ashar | 05:39 | |
*** leobaillard has joined #xdandroid | 05:40 | |
*** zycho has quit IRC | 05:59 | |
*** Ashar has quit IRC | 06:00 | |
*** Ashar has joined #xdandroid | 06:00 | |
*** Ashar has quit IRC | 06:17 | |
*** Ashar has joined #xdandroid | 06:22 | |
*** Ashar has quit IRC | 06:30 | |
*** Ashar has joined #xdandroid | 06:35 | |
*** Ashar has quit IRC | 07:13 | |
*** Ashar has joined #xdandroid | 07:13 | |
*** scarface has joined #xdandroid | 07:14 | |
scarface | hello | 07:14 |
*** Ashar has quit IRC | 07:14 | |
*** Ashar has joined #xdandroid | 07:14 | |
scarface | i have two questions , can i put all those apps from here : http://www.android.com/market/#app=com.ebay.mobile if i put xdanroid? secondly i want to ask if i put newer version of xandroid, how can i back up those apps, thank you | 07:14 |
*** scarface has quit IRC | 07:19 | |
*** Ashar has quit IRC | 07:25 | |
*** Ashar has joined #xdandroid | 07:25 | |
*** hardwalker has quit IRC | 07:30 | |
*** Ashar has quit IRC | 07:32 | |
*** Ashar has joined #xdandroid | 07:33 | |
*** Ashar has quit IRC | 07:54 | |
*** Ashar has joined #xdandroid | 07:56 | |
*** L_miller has joined #xdandroid | 07:59 | |
*** arrrghhh has joined #xdandroid | 08:00 | |
*** TheDeadCPU has joined #xdandroid | 08:01 | |
*** Ashar has quit IRC | 08:03 | |
*** Ashar has joined #xdandroid | 08:17 | |
*** Ashar has quit IRC | 08:20 | |
*** Ashar has joined #xdandroid | 08:20 | |
*** Ashar has quit IRC | 08:24 | |
*** Ashar has joined #xdandroid | 08:24 | |
*** arrrghhh has quit IRC | 08:39 | |
*** TheDeadBOT has quit IRC | 08:42 | |
*** Ashar has quit IRC | 08:42 | |
*** Ashar has joined #xdandroid | 08:44 | |
*** Ashar has quit IRC | 08:59 | |
*** Ashar has joined #xdandroid | 08:59 | |
*** Ashar has quit IRC | 09:03 | |
*** Ashar has joined #xdandroid | 09:03 | |
*** programmer8922 has quit IRC | 09:04 | |
*** arrrghhh has joined #xdandroid | 09:30 | |
*** balans has joined #xdandroid | 09:36 | |
*** XirXes has joined #xdandroid | 10:01 | |
*** TheDeadCPU has quit IRC | 10:12 | |
*** L_miller has quit IRC | 10:12 | |
*** leobaillard has quit IRC | 10:12 | |
*** F22 has quit IRC | 10:12 | |
*** paccer has quit IRC | 10:12 | |
*** camro has quit IRC | 10:12 | |
*** Ashar has quit IRC | 10:12 | |
*** jensen_ has quit IRC | 10:12 | |
*** Khaytsus has quit IRC | 10:12 | |
*** arrrghhh has quit IRC | 10:12 | |
*** Agin has quit IRC | 10:12 | |
*** balans has quit IRC | 10:12 | |
*** kalemas has quit IRC | 10:12 | |
*** krog has quit IRC | 10:12 | |
*** NeoMatrixJR has quit IRC | 10:12 | |
*** tblt has quit IRC | 10:12 | |
*** EricAhn has quit IRC | 10:12 | |
*** XirXes has quit IRC | 10:12 | |
*** Krazie has quit IRC | 10:12 | |
*** dcordes has quit IRC | 10:12 | |
*** paalsteek has quit IRC | 10:12 | |
*** cazh_ has quit IRC | 10:12 | |
*** purefusion has quit IRC | 10:12 | |
*** phh has quit IRC | 10:32 | |
*** phh has joined #xdandroid | 10:33 | |
*** arrrghhh has joined #xdandroid | 10:33 | |
*** XirXes has joined #xdandroid | 10:33 | |
*** balans has joined #xdandroid | 10:33 | |
*** Ashar has joined #xdandroid | 10:33 | |
*** TheDeadCPU has joined #xdandroid | 10:33 | |
*** L_miller has joined #xdandroid | 10:33 | |
*** leobaillard has joined #xdandroid | 10:33 | |
*** kalemas has joined #xdandroid | 10:33 | |
*** F22 has joined #xdandroid | 10:33 | |
*** camro has joined #xdandroid | 10:33 | |
*** krog has joined #xdandroid | 10:33 | |
*** Agin has joined #xdandroid | 10:33 | |
*** NeoMatrixJR has joined #xdandroid | 10:33 | |
*** cazh_ has joined #xdandroid | 10:33 | |
*** paccer has joined #xdandroid | 10:33 | |
*** jensen_ has joined #xdandroid | 10:33 | |
*** tblt has joined #xdandroid | 10:33 | |
*** Krazie has joined #xdandroid | 10:33 | |
*** EricAhn has joined #xdandroid | 10:33 | |
*** Khaytsus has joined #xdandroid | 10:33 | |
*** dcordes has joined #xdandroid | 10:33 | |
*** purefusion has joined #xdandroid | 10:33 | |
*** paalsteek has joined #xdandroid | 10:33 | |
*** LeTama has joined #xdandroid | 10:42 | |
*** balans has quit IRC | 11:13 | |
*** zycho has joined #xdandroid | 11:27 | |
*** emwe has joined #xdandroid | 11:37 | |
*** hamagc has joined #xdandroid | 11:54 | |
arrrghhh | anyone using neopeek's ext2 builds? | 12:02 |
hamagc | i tried it when he first came out | 12:02 |
*** kalemas has left #xdandroid | 12:03 | |
arrrghhh | hamagc: is there a way to set a rel_path? | 12:04 |
arrrghhh | or do i have to have it at the root of mah sd? | 12:04 |
hamagc | can't you put it in the startup? | 12:04 |
arrrghhh | eh i tried that dude :P | 12:04 |
arrrghhh | doesn't boot | 12:04 |
hamagc | lol obvious things first right | 12:05 |
arrrghhh | the error flew by so quick & it rebooted to winmo, i didn't even get to see what the actual error was. | 12:05 |
arrrghhh | i guess i can try to put it at the root, but i'd like to avoid that if possible. | 12:05 |
hamagc | and you have all the partitions setup right? you can try it at root and see if it gets it by. | 12:05 |
arrrghhh | yea i guess for TS purposes i should. damnit. | 12:06 |
arrrghhh | hrm something about passing an init= option to the kernel. | 12:17 |
arrrghhh | i have a feeling the install failed :P | 12:17 |
arrrghhh | ah i think i gots it. | 12:29 |
hamagc | ?? | 12:38 |
*** Ashar has quit IRC | 12:38 | |
arrrghhh | workie now | 12:42 |
arrrghhh | the npkinstall failed, need to do that from the root of sd evidently... can't mess with it. but the build itself i was able to run from a folder with the rel_path statement. | 12:43 |
stinebd | fellow phone geeks | 13:19 |
emwe | meep | 13:19 |
stinebd | emwe: get the raph yet? | 13:19 |
emwe | nope. | 13:19 |
stinebd | bah | 13:19 |
*** TheDeadCPU_ has joined #xdandroid | 13:20 | |
emwe | at least till 1pm no postal-info was in the mailbox about missed delivery... | 13:20 |
*** TheDeadCPU has quit IRC | 13:23 | |
*** TheDeadCPU has joined #xdandroid | 13:23 | |
*** TheDeadCPU_ has quit IRC | 13:24 | |
*** TheDeadCPU has quit IRC | 13:28 | |
*** mokmok_ has joined #xdandroid | 13:30 | |
mokmok_ | helloo | 13:30 |
mokmok_ | having problems with my fuze running android | 13:31 |
mokmok_ | do I need to have it on a stock ROM? | 13:31 |
hamagc | no | 13:33 |
arrrghhh | ROM shouldn't matter whatsoever | 13:33 |
arrrghhh | define:problems | 13:33 |
mokmok_ | well, I got it to boot once | 13:34 |
mokmok_ | but something kept crashing | 13:34 |
arrrghhh | k | 13:34 |
arrrghhh | acore? | 13:34 |
mokmok_ | cna't remember the name of the process | 13:34 |
mokmok_ | android.something | 13:34 |
mokmok_ | or something.android | 13:34 |
arrrghhh | yea | 13:34 |
mokmok_ | now I get "pdflush[19] exited with preempt count 1 | 13:35 |
mokmok_ | and a buunch of trace data before it | 13:35 |
arrrghhh | never see the bootanim? | 13:35 |
arrrghhh | flying droids | 13:35 |
mokmok_ | I did see that the one time, but got the crashing process after it | 13:35 |
arrrghhh | hmmmm | 13:36 |
arrrghhh | you said fuze... | 13:36 |
mokmok_ | yep | 13:36 |
arrrghhh | i'm going to go with delete the data.img and try again. | 13:36 |
arrrghhh | what build are you using? | 13:36 |
mokmok_ | I'm using the ProjectAndroid2.2BLAZN.092810 startup generator | 13:36 |
mokmok_ | and the latest build | 13:36 |
mokmok_ | I updated with the startup app | 13:36 |
*** TheDeadCPU has joined #xdandroid | 13:37 | |
*** balans has joined #xdandroid | 13:37 | |
mokmok_ | ok | 13:37 |
mokmok_ | I'll give it a shot | 13:37 |
arrrghhh | hrm | 13:37 |
arrrghhh | startup app works on fuze? | 13:37 |
mokmok_ | yep | 13:38 |
mokmok_ | at least, it starts booting the system | 13:38 |
arrrghhh | it was originally designed for RHOD... not sure if other devices were included or not. | 13:38 |
arrrghhh | i wouldn't use it | 13:38 |
arrrghhh | as we don't support it. | 13:38 |
mokmok_ | it's got a selection for fuze | 13:38 |
arrrghhh | you CAN use it, but don't expect us to help you with it :D | 13:38 |
mokmok_ | that's OK | 13:38 |
mokmok_ | is there an alternative that's better? | 13:38 |
TheDeadCPU | There are other devices in the utility | 13:38 |
arrrghhh | LIES | 13:39 |
arrrghhh | mokmok_: it's not really necessary... | 13:39 |
arrrghhh | you can boot w/o it. just click haret.exe | 13:39 |
mokmok_ | from what I understand it's just a startup.txt selector | 13:39 |
arrrghhh | eh selector... not so much. | 13:39 |
mokmok_ | with the option to update the system.ext2 | 13:39 |
arrrghhh | blastor out of and recreator of... perhaps. | 13:40 |
arrrghhh | and i think that's the one thing it can't update | 13:40 |
arrrghhh | is the system image | 13:40 |
arrrghhh | unless sov added that in 1.3.1? not sure. | 13:40 |
* arrrghhh doesn't use it. | 13:40 | |
* mokmok_ tries again. | 13:41 | |
* arrrghhh wishes he had some bacon | 13:41 | |
F22 | mokmok_: blazn overclocks by default from what i recall and that can cause crashing if your chip can't handle it. you might want to run it at stock speed and see how it goes. | 13:48 |
arrrghhh | there isn't a blazn build for RAPH... | 13:48 |
arrrghhh | did you just replace the system image mokmok_ ? | 13:48 |
F22 | i'd be curious to see his startup file | 13:55 |
*** balans has quit IRC | 13:58 | |
mokmok_ | sorry, was swapping LCDs on laptops | 14:06 |
mokmok_ | I'll post it to you | 14:07 |
mokmok_ | I did the "update" in the starter | 14:08 |
mokmok_ | the date's funny though | 14:08 |
mokmok_ | the app saya 10-31-10, but the date on the file itself is 8-27-10 | 14:08 |
*** JesusFreak316 has joined #xdandroid | 14:13 | |
mokmok_ | hmm, nope | 14:20 |
mokmok_ | took out the overclock and now I'm getting kernel panics | 14:20 |
mokmok_ | not syncing, fatal exception | 14:20 |
mokmok_ | d'oh, I opened the startup app again, it overwrote startup.txt | 14:26 |
* mokmok_ edits and restarts. | 14:26 | |
emwe | stinebd: if i push liglights to /lib/froyo/hw it will write through to rootfs.img and is persistent across boots, right? | 14:30 |
stinebd | emwe: right | 14:30 |
stinebd | don't forget to remount,rw first | 14:30 |
emwe | stinebd: remount /lib ? | 14:31 |
stinebd | / | 14:31 |
emwe | ok, thx | 14:31 |
stinebd | also sync before yanking the battery | 14:31 |
stinebd | or if you're one of those weird people that shut down normally, that's fine | 14:32 |
emwe | looks like android is sending out backlight messages a lot of times when sensor mode is set. so it would trigger the kernel hooks several times with no change... | 14:32 |
emwe | nono, sync and reboot -f ;) | 14:32 |
stinebd | well i pushed a change to liblights yesterday to solve that | 14:32 |
stinebd | is that what you're testing? | 14:32 |
*** Ashar has joined #xdandroid | 14:33 | |
emwe | i wen't further actually. when switching to sensor mode, it's nevertheless pushing out brightness changes which we then ignore as auto-bl is on. | 14:33 |
emwe | but i'd like to skip that, too. | 14:33 |
emwe | i suppose that is in relation to dimming the backlight after some time even when on auto-bl mode | 14:33 |
emwe | not sure, though. | 14:33 |
stinebd | ? | 14:34 |
stinebd | this is what i pushed: http://gitorious.org/xdandroid-eclair/xdandroid-hardware_msm7k/commit/10dc608cbd6876eb7903fc9b8232ea4b9bed02e6 | 14:34 |
stinebd | oh wait | 14:35 |
emwe | i know what you pushed :) but android still sends out brigthness changes with SENSOR_MODE=on after switching to it | 14:35 |
stinebd | that's wrong anyway hah | 14:35 |
emwe | which then trigger the backlight hook. | 14:35 |
stinebd | i need to use an else-if there | 14:35 |
stinebd | not an else | 14:36 |
stinebd | and then you should see the desired behavior | 14:36 |
*** |Jeroen| has joined #xdandroid | 14:37 | |
emwe | else-if (what?) stinebd ? | 14:37 |
stinebd | (pseudocode) g_brightnessMode == MANUAL | 14:37 |
stinebd | i have to look up what the constant for manual is | 14:37 |
emwe | g_brightnessMode == BRIGHTNESS_MODE_USER | 14:37 |
emwe | that in the else if? | 14:37 |
stinebd | yeah | 14:37 |
mokmok_ | sweet | 14:38 |
emwe | probably right, yes... but back to my assumption: isn't it regular behaviour to dimm backlight after some time even though one is in sensor-mode? | 14:38 |
mokmok_ | now it's booting | 14:38 |
stinebd | emwe: we can't do that in sensor mode even if we wanted to. we lose control of backlight completely | 14:38 |
F22 | :) | 14:38 |
emwe | stinebd: isn't that how it is done in winmo, too? | 14:38 |
mokmok_ | and also the director of sales gave me a binary watch | 14:39 |
stinebd | (except for backlight level 0 which is off) | 14:39 |
emwe | stinebd: hm. so yes, i wouldn't mind that it is not dimming on sensor mode, but i think i see that in wince... no? getting old and too lazy to look it up ;) | 14:40 |
stinebd | wince likely uses software backlight control | 14:40 |
emwe | hmhm! | 14:40 |
stinebd | similarly to how android is supposed to | 14:40 |
emwe | ok, then i will try the else if case locally. | 14:40 |
mokmok_ | sweet, I've tripled my phone's boot time! :p | 14:40 |
emwe | i even started a f**cking branch for that to not confuse repo again... | 14:41 |
stinebd | either that, or wince disables sensor after inactivity, then lowers backlight | 14:41 |
stinebd | (and then reactivates sensor on activity) | 14:41 |
emwe | might be but that sounds really like overhead for now. | 14:41 |
stinebd | well we all know microsoft's feelings on overhead | 14:42 |
emwe | if i am done with that, i will hopefully get back to debugging ril-loss after some hours... | 14:42 |
stinebd | let me know how it goes (ie if i should push it like that) | 14:42 |
emwe | yap. just about to test. and then the small config.xml change and it can be pushed to rootfs i guess. | 14:43 |
emwe | btw, i just used the passion values for the overlay. it works. should we take just theirs or should we stick to our limited 1 and 1+1 arrays? | 14:43 |
mokmok_ | so, is the display supposed to turn off every 5 seconds? | 14:44 |
stinebd | emwe: do those smaller arrays work too? | 14:44 |
mokmok_ | well this is frustrating | 14:45 |
stinebd | i don't think it really matters anyway, i'll have to test the changes no matter what | 14:45 |
mokmok_ | I'm at the "lock" screen, butit doesn't want to let me unlock | 14:45 |
stinebd | might as well just use the passion entries | 14:45 |
emwe | stinebd: i kept only the "1" for autobllevels and 128+250 for the other. | 14:45 |
mokmok_ | oh! that's because the touch screen isn't calibrated | 14:45 |
stinebd | emwe: ok, please send me whatever you're using for your final testing and if that works for me, that's what we'll use | 14:46 |
emwe | stinebd: ok. will do. | 14:46 |
mokmok_ | how do I get my touch screen calibrated? | 14:47 |
mokmok_ | that's funny, I figured out how much it's off | 14:47 |
JesusFreak316 | delete ts-cslibrate from your sdcard. | 14:48 |
F22 | yup | 14:49 |
JesusFreak316 | Next boot it will prompt to recalibrate. | 14:49 |
mokmok_ | ok | 14:49 |
mokmok_ | otherwise it seems to work OK | 14:49 |
mokmok_ | how do I do a safe reboot? | 14:50 |
mokmok_ | can I just pull the plug without damage? | 14:50 |
emwe | mokmok_: safest ist to shutdown ;) | 14:50 |
emwe | i use quick boot from market once in a while... dunno what it does internally | 14:51 |
mokmok_ | holding down the power button does nothing | 14:51 |
mokmok_ | I've never used android before, I don't know where the shutdown button is | 14:51 |
XirXes | its the end key | 14:52 |
mokmok_ | ok | 14:53 |
mokmok_ | does the OS run in RAM, or entirely from the SD card? | 14:53 |
mokmok_ | I'm assuming RAM, otherwise this'd be really slow | 14:54 |
XirXes | it mounts certain files on your sd card as partitions. | 14:55 |
XirXes | if you take out your sd card it will crash immediatly | 14:55 |
mokmok_ | that's probably not so great for battery usage, eh? | 14:57 |
JesusFreak316 | No, it's not. :) | 14:58 |
JesusFreak316 | But afaik it's not the main issue for battery, radio is mostly. | 14:59 |
* mokmok_ deletes the calibration file and restarts. | 14:59 | |
mokmok_ | I'm just glad to have it running :) | 14:59 |
mokmok_ | getting tired of winmo | 14:59 |
mokmok_ | sucks about the a2dp though | 15:00 |
F22 | mokmok_: power button shutoff is in a newer kernel. the kernel in blazn is a bit dated at this point. | 15:02 |
JesusFreak316 | Yeah, I've been wanting to try out one of Reefer's Blazin builds for a while but it's so outdated. Anyone heard if he's making a new one soon? | 15:04 |
*** zycho_ has joined #xdandroid | 15:04 | |
F22 | no idea | 15:08 |
*** zycho has quit IRC | 15:09 | |
mokmok_ | aww man | 15:11 |
mokmok_ | camera doesn't work with the barcode app | 15:11 |
F22 | camera doesn't work yet | 15:12 |
*** wladston has joined #xdandroid | 15:24 | |
*** balans has joined #xdandroid | 15:28 | |
*** mokmok_ has quit IRC | 15:28 | |
*** balans has quit IRC | 15:33 | |
F22 | hmm...that's odd...i'm running latest everything, i was streaming pandora, but not otherwise doing anything with it, and suddenly the music cut off and my phone went to the flying saucer xdanroid screen that appears during boot. | 15:43 |
F22 | anybody have any ideas on what might have happened? | 15:45 |
JesusFreak316 | Random crashes happen. | 15:47 |
JesusFreak316 | Pretty much get used to it. If you want to try to get it fixed run a logcat in adb so the devs can see what caused the crash. | 15:47 |
F22 | ok, so it's a known problem. i would assume the devs already have their own logcats? or do the crashes happen only on certain models? | 15:48 |
JesusFreak316 | They just happen. They're just random for the most part. I get them while installing apps, refreshing facebook, playing a nes emulator; there's no rhyme or reason in my experience. | 15:49 |
JesusFreak316 | I have a RAPH 100 HTC Fuze btw. | 15:49 |
JesusFreak316 | *RAPH110 | 15:50 |
F22 | I have a Rhod 210. | 15:50 |
JesusFreak316 | I haven't updated to the newest system yet though. | 15:50 |
JesusFreak316 | Still on the one from the 17th I think. | 15:50 |
JesusFreak316 | The sheer randomness of the crashes makes getting a logcat a pain; you just never know how long you have to wait before it does it. | 15:52 |
F22 | i see what you mean. my phone had been running for hours just fine, and then suddenly poof, restart. does it always reboot back into android like that? or does it sometimes shutdown totally. This morning when I woke up I found mine down despite having a full charge (i left it plugged into the usb charger over night) | 15:58 |
*** arrrghhh has quit IRC | 16:03 | |
*** JesusFreak316 has quit IRC | 16:24 | |
emwe | stinebd: overlay-patch: http://pastebin.com/f6JZnbBf (using passion values, what i used the last boots) liblights-patch: http://pastebin.com/qvHeR58R (needs to be an if not else if, because we need to immedeately set the brightness level which comes by with the switch to user-mode, otherwise, display wont dimm to lowest value after disabling auto-bl when using power widget.) | 16:33 |
*** Whosdaman has joined #xdandroid | 16:37 | |
stinebd | think we need the debugging in there? | 16:38 |
*** Whosdaman has left #xdandroid | 16:39 | |
*** L_miller has quit IRC | 16:41 | |
stinebd | <3 | 17:01 |
stinebd | i love rebuilding everything for one little xml change | 17:01 |
*** L_miller has joined #xdandroid | 17:01 | |
F22 | that's dedication! | 17:01 |
*** balans has joined #xdandroid | 17:01 | |
*** vw has joined #xdandroid | 17:05 | |
stinebd | well technically i have to rebuilt it all twice because i also make a target-files package so that i can generate an ota update | 17:06 |
xdandroid | New kernel available (20101103_215747) at http://zimages.googlecode.com/files/htc-msm-linux-20101103_215747-package.tar.bz2 | 17:07 |
stinebd | ooh | 17:07 |
*** balans has quit IRC | 17:07 | |
stinebd | aww rhod crap | 17:07 |
emwe | lol | 17:08 |
*** mokmok_ has joined #xdandroid | 17:15 | |
*** |Jeroen| has quit IRC | 17:17 | |
*** JesusFreak316 has joined #xdandroid | 17:21 | |
*** L_miller has quit IRC | 17:28 | |
stinebd | emwe: beautiful | 17:28 |
emwe | stinebd: nice to hear ;) | 17:29 |
stinebd | and you say this *works* on a topaz? | 17:29 |
emwe | yes. auto-bl and manual works in all situations now. *but* i am yet about to re-enable the gpio, vregs and mddi client deinit/init. but that will hopefully work. just about to test.... | 17:31 |
stinebd | in that case, i can't push it as it is | 17:32 |
stinebd | we need at least one broken device, to leech for donations | 17:32 |
stinebd | (kidding, i already pushed it) | 17:33 |
emwe | lol | 17:33 |
*** sle118 has joined #xdandroid | 17:33 | |
sle118 | hello everyone | 17:34 |
sle118 | I have a quick question... | 17:34 |
sle118 | Was there any keymap change in the latest releases? | 17:34 |
sle118 | for example, hitting the home button does not bring me the settings menu in the main windoe | 17:35 |
sle118 | window | 17:35 |
sle118 | power seems to be... well... power | 17:36 |
sle118 | Home=home | 17:36 |
sle118 | Back=back | 17:36 |
sle118 | center button=settings | 17:36 |
sle118 | ok | 17:36 |
sle118 | I think I get it now... | 17:36 |
hamagc | lol | 17:36 |
sle118 | yeah | 17:36 |
stinebd | yes i did make an announcement to that effect before pushing it. | 17:36 |
*** zycho_ has quit IRC | 17:36 | |
sle118 | sorry | 17:36 |
sle118 | I was out of the loop for a long time | 17:37 |
sle118 | my latest version was from september | 17:37 |
F22 | my latest version before yesterday was from march, so i can empathize. ;) | 17:37 |
sle118 | lol | 17:38 |
sle118 | good thing I have Titanium | 17:38 |
sle118 | but what a pain to reinstall everything | 17:38 |
*** vw has quit IRC | 17:38 | |
*** zycho has joined #xdandroid | 17:41 | |
xdandroid | New rootfs available (20101103-806f8b4) at: http://is.gd/gGs4J -- Changes at: http://is.gd/gGs4H | 17:43 |
F22 | i've compiled and run 3 kernels in the last few days, plus there are the userland improvements. heck i just replaced my kernel 5 minutes ago, and now there's a new rootfs. the updates keep coming. :P | 17:44 |
F22 | not that i'm complaining. :D | 17:44 |
F22 | i recall this time last year when cr2 was working on just getting the rhod panel to work, and most of the dev work seemed to be for diam/raph, not counting dzo's ongoing work for the vogue. | 17:47 |
*** arrrghhh has joined #xdandroid | 18:27 | |
*** hamagc has quit IRC | 18:28 | |
*** mokmok_ has quit IRC | 18:30 | |
*** LeTama has quit IRC | 18:30 | |
*** Curious_ has joined #xdandroid | 18:47 | |
Curious_ | how can i get autobrightness setting to be written to sysfs? | 18:48 |
Curious_ | I can get the info from here : http://developer.android.com/reference/android/provider/Settings.System.html#SCREEN_BRIGHTNESS_MODE | 18:48 |
arrrghhh | probably not the right room to ask in :P | 18:49 |
phh | I'd say it is | 18:49 |
phh | well i'm not sure to understand the question:pm | 18:49 |
arrrghhh | eh i figured he'd get a better response in #htc-linux. | 18:50 |
arrrghhh | i guess wrong is a strong word ;) | 18:50 |
TheDeadCPU | You didn't say wrong. | 18:51 |
arrrghhh | who's counting. | 18:51 |
Curious_ | i mean i want to use sysfs to check whether autobrightness is on or off | 18:52 |
Curious_ | in android | 18:52 |
Curious_ | i found out that you check whether auto-br is on or off from http://developer.android.com/reference/android/provider/Settings.System.html#SCREEN_BRIGHTNESS_MODE | 18:52 |
Curious_ | so | 18:52 |
Curious_ | how can i write into sysfs? | 18:53 |
*** JesusFreak316 has quit IRC | 18:54 | |
*** JesusFreak316 has joined #xdandroid | 19:02 | |
emwe | Curious_: there needs to be kernel side support for that sysfs entry. you got leo? | 19:08 |
Curious_ | yes | 19:08 |
Curious_ | ok kernel side support isn't hard but | 19:08 |
Curious_ | how about otherwise | 19:08 |
Curious_ | how can i make android update that sysfs | 19:08 |
emwe | it's not hard? didn't markinus say there is no kernel side support?! | 19:08 |
Curious_ | we can implement it | 19:09 |
Curious_ | but i don't know how to get info from android? | 19:09 |
emwe | Curious_: look at the recent xdandroid changes. we've done more or less the same there. | 19:09 |
Curious_ | do you have a link for xdandroid | 19:09 |
Curious_ | git;? | 19:09 |
emwe | Curious_: http://gitorious.org/xdandroid-eclair | 19:09 |
arrrghhh | we trade autobl for nand :P | 19:09 |
Curious_ | k | 19:09 |
emwe | Curious_: there's been changes to the overlay config.xml and liblights.c (hd2 liblights among others are here: http://www.gitorious.com/htc-hd2-android-libraries) | 19:10 |
Curious_ | k | 19:10 |
*** zycho has quit IRC | 19:16 | |
Curious_ | emwe, does xdandroid liblights have an indicator for autobrightness mode? | 19:26 |
*** camro has quit IRC | 19:26 | |
Curious_ | gitorious is like dead, that's why i'm asking | 19:26 |
emwe | Curious_: liblights is triggered via android which in turn calls the "sysfs" entry (it's a dbgfs entry on our devices) which in fact is microp-klt code in our kernel. | 19:27 |
emwe | Curious_: it's only writing to, not reading from the hook. | 19:28 |
arrrghhh | Curious_, you can try browsing the google cached page of it. | 19:28 |
arrrghhh | http://tinyurl.com/24o9xc2 | 19:28 |
arrrghhh | it does seem slow, but it loaded for me in ~30secs or so. | 19:28 |
emwe | dunno if there is an api liblights would have to extend to allow android for reading if auto-bl is enabled. | 19:28 |
Curious_ | hmm got it | 19:29 |
Curious_ | so if android doesn't give auto bl info to liblights | 19:29 |
Curious_ | i can't do what i want.. | 19:29 |
emwe | it passes a struct which tells liblights to enable/disable and set brightness via sysfs | 19:31 |
Curious_ | http://source.android.com/porting/lights.html#androidLightsBuildingDriver | 19:31 |
emwe | so that kernel actually sets what is requested. | 19:31 |
Curious_ | yeah but no auto-bl info i guess | 19:31 |
Curious_ | but what is #define BRIGHTNESS_MODE_SENSOR 1 needed for | 19:31 |
Curious_ | then? | 19:32 |
emwe | that is auto-bl | 19:32 |
emwe | when gito is back, lock at the recent lights.c changes in liblights | 19:33 |
Curious_ | yes, gonna check it | 19:33 |
Curious_ | BRIGHTNESS_MODE_SENSOR seemed to be usd in default liblights.h | 19:34 |
Curious_ | so it must support it right? | 19:34 |
Curious_ | used* | 19:34 |
Curious_ | emwe | 19:41 |
Curious_ | do you have latest lights.c | 19:41 |
Curious_ | i am impatient! | 19:42 |
*** JesusFreak316 has quit IRC | 19:42 | |
arrrghhh | lol | 19:42 |
arrrghhh | hey you almost waited 10 mins :P | 19:42 |
Curious_ | yeah that's me :D | 19:42 |
arrrghhh | did that google cached page version work any better? | 19:42 |
Curious_ | cache didn't gave source | 19:43 |
emwe | Curious_: if the android has the right overlay configuration then android will issue different "commands" via liblights.. inlcuding requesting sensor more or user mode. so yes, if the configuration overlay is correct, it is used and works. | 19:43 |
arrrghhh | bah. | 19:43 |
Curious_ | 10 mins for doing nothing but thinking possibilities based on lacky info is killing me.. | 19:43 |
emwe | Curious_: so first, you need to make sure your android distribution will ever request auto-bl. (aka it allows setting auto-bl in userland via display settings) | 19:44 |
Curious_ | yes | 19:44 |
*** kn_ has joined #xdandroid | 19:44 | |
Curious_ | but dunno whether requests from liblights | 19:44 |
Curious_ | where can i check it? | 19:45 |
emwe | if you enable auto-bl in android it *will* request it in liblights. | 19:45 |
emwe | and if you disable it again (manual mode/user mode) it *will* request BRIGHTNESS_MODE_USER again... | 19:45 |
Curious_ | so then I have what I need | 19:46 |
Curious_ | hmm ok | 19:46 |
Curious_ | do you know what android calls to change mode? | 19:46 |
Curious_ | in liblights.c? | 19:46 |
Curious_ | lights.. | 19:46 |
emwe | static int | 19:46 |
emwe | set_light_backlight(struct light_device_t* dev, | 19:46 |
emwe | struct light_state_t const* state) | 19:46 |
Curious_ | so it passes BRIGHTNESS_MODE_SENSOR to set_light_backlight when auto bl is enabled | 19:47 |
emwe | yap. | 19:48 |
emwe | but you should really see lights.c how the hooks are resolved. | 19:48 |
Curious_ | why they didn't put set_light_backlight in lights.h? | 19:48 |
Curious_ | yeah i am dying but still gito is dead | 19:48 |
Curious_ | don't you have lights.c of xdandroid? | 19:49 |
emwe | dependant on requested device, a different function pointer (implementing the same api) is called | 19:49 |
emwe | http://pastebin.com/i9ksSkfN | 19:49 |
Curious_ | where is the pointer of it defined | 19:51 |
Curious_ | is it defined in light_device_t? | 19:51 |
Curious_ | hw_device_t common;? | 19:51 |
emwe | it's set in the open_device hook which is called by android if i get that right | 19:52 |
emwe | err... open_lights() i mean | 19:53 |
Curious_ | ok | 19:54 |
Curious_ | got it | 19:54 |
Curious_ | thnx for the patience | 19:54 |
emwe | np | 19:55 |
emwe | so one last try getting the panel to wake....and then off to bed. | 19:55 |
Curious_ | one more thing | 19:55 |
Curious_ | android calls set_light_backlight once right? | 19:56 |
Curious_ | when auto bl is enabled. | 19:56 |
emwe | it actually calls it several times with differnet brightness values set in the struct. (but our recent change to lights.c makes sure it's only triggering the kernel hook once) | 19:57 |
Curious_ | why would it need to call it again and again if it is set to auto-bl | 19:57 |
emwe | so not permanently, but several calls in a row and then it's fine | 19:57 |
emwe | the structs contain different backlight levels | 19:58 |
emwe | probably for hw-dimming even on auto-bl ... no idea really. | 19:59 |
Curious_ | it is very stupid to call it again and again | 19:59 |
Curious_ | when auto-bl is on | 19:59 |
Curious_ | ah | 20:00 |
emwe | be inspired by our lights.c and it will make sure it's not trashing the kernel with the calls ;) | 20:00 |
emwe | (when on auto-bl) | 20:00 |
Curious_ | or does it get value from lsensor and pass it to lights.c to get it set? | 20:00 |
Curious_ | when auto-bl is on | 20:00 |
emwe | when lsensor is in effect it auto-adjusts display brightness without going over android | 20:03 |
XirXes | are there any android devices with ctrl keys? | 20:03 |
Curious_ | so why would android call it more than once | 20:03 |
Curious_ | i don't get it | 20:03 |
Curious_ | stupid android | 20:03 |
emwe | Curious_: i can't tell you. look in PowerManagerService | 20:04 |
Curious_ | thnx | 20:04 |
Curious_ | gonna check lights.c deeply | 20:04 |
stinebd | because normally android handles auto brightness in software | 20:04 |
stinebd | we trick it to use hardware auto brightness | 20:04 |
Curious_ | stinebd, how does it handle in software? | 20:05 |
Curious_ | polling? | 20:05 |
emwe | stinebd: in software by querying lsensor brightness report and faking a darker "image"? | 20:05 |
emwe | stinebd: and i wouldn't call it "we trick it". it's a config option for the better devices :P | 20:06 |
stinebd | emwe: or by setting the backlight levels after reading that brightness, yes | 20:06 |
stinebd | no, we absolutely do trick it | 20:06 |
emwe | then i have misunderstood something very much :) | 20:06 |
stinebd | in xdandroid, it's trying (and failing) to read lux values from the sensor (whose device node doesn't exist), and then trying to set brightness in liblights | 20:06 |
stinebd | we intercept the brightness calls while using the sensor and essentially NOOP it | 20:07 |
stinebd | (that conditional in the backlight function) | 20:07 |
stinebd | we're just very lucky that the structure has the brightness mode | 20:07 |
Curious_ | so android polls lsensor and sets the bl value to it | 20:07 |
Curious_ | ? | 20:07 |
stinebd | yes | 20:08 |
Curious_ | yeap | 20:08 |
Curious_ | great | 20:08 |
Curious_ | so it is time to have the same for leo | 20:08 |
stinebd | we didn't do it that way for 2 reasons: 1. wistilt2 was able to set up the microp to do it in hardware, 2. we don't have the sensor readings calibrated to mean anything useful (and that would be painful to do) | 20:09 |
stinebd | doing it in hardware greatly simplifies supporting all of our devices | 20:09 |
Curious_ | yeah | 20:10 |
Curious_ | stinebd | 20:10 |
Curious_ | why did you use dbgfs | 20:10 |
Curious_ | not sysfs? | 20:10 |
stinebd | wistilt2 did it, because it was easier to implement that way (basically one line of code) | 20:10 |
Curious_ | how do you check it in the driver? | 20:11 |
emwe | stinebd: so but it's our fault to not provide correct values ;) | 20:11 |
stinebd | emwe: right, but they would likely be different across devices, and would require someone spending time getting values for "real-world" ambient light levels | 20:11 |
Curious_ | yeah | 20:12 |
stinebd | meanwhile microp has values programmed into it and we don't have to bother | 20:12 |
Curious_ | it is really painful | 20:12 |
Curious_ | better not to mess with calibration | 20:12 |
emwe | stinebd: yap, agreed. but i still think our thingy is not tricking, allthough it officialy might look like it. i really like it how it is now. ;) | 20:12 |
stinebd | yeah, it's a really nice solution | 20:12 |
emwe | only need my freaking panel to wake... | 20:12 |
Curious_ | i didn't understand how do you read from dbgfs? | 20:12 |
Curious_ | and where? | 20:12 |
stinebd | we don't | 20:12 |
stinebd | we only write to dbgfs in userland | 20:13 |
Curious_ | so what does? | 20:13 |
Curious_ | yes | 20:13 |
Curious_ | then? | 20:13 |
emwe | Curious_: liblights does the write | 20:13 |
Curious_ | how microp gets reported? | 20:13 |
stinebd | that sets a variable in the kernel driver which tells microp to start autobl | 20:13 |
Curious_ | yes | 20:13 |
Curious_ | how can i read dbgfs from kernel? | 20:13 |
stinebd | have you seen the commit? | 20:14 |
Curious_ | lmc again | 20:14 |
emwe | it's a hook you define in your kernel module and whenever there is a write or a read to it the hook is called for you from the kernel itself | 20:14 |
emwe | so you have nothing to do then provide the implementation | 20:14 |
stinebd | gitorious is down | 20:14 |
emwe | (and define the sysfs/dbgfs hooks) | 20:14 |
Curious_ | it wasn'T completelty down | 20:15 |
Curious_ | at least i was able to see commits | 20:15 |
Curious_ | and still i am : ) | 20:15 |
Curious_ | but no blob.. | 20:15 |
stinebd | 503. it's down | 20:15 |
Curious_ | http://gitorious.org/xdandroid-eclair/eclair-rootfs/commit/806f8b4ffff111936b9ea661083d88cc76e71359 | 20:15 |
stinebd | http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commit/e59fdaf70f2a02728a7fdc7aaa7c5757d4508d6e | 20:17 |
stinebd | if you can get it to load | 20:17 |
Curious_ | what does klt means in micropklt :P | 20:18 |
Curious_ | 503 | 20:18 |
stinebd | what does it matter what it means? | 20:19 |
emwe | KeyLighT | 20:19 |
Curious_ | my name is curious ^ | 20:19 |
Curious_ | ^ ^ | 20:19 |
stinebd | key led touchscreen :P | 20:20 |
emwe | damnit. ;) | 20:20 |
Curious_ | i generally don't read documentation | 20:20 |
stinebd | i totally guessed | 20:20 |
emwe | stinebd: lol | 20:20 |
emwe | but makes even more sense | 20:21 |
Curious_ | good written code can be self explanatory so i wonder every detail | 20:21 |
Curious_ | reading docs need more time and | 20:21 |
Curious_ | you generally read what you don't need | 20:21 |
stinebd | that concept doesn't apply at the hardware level | 20:21 |
stinebd | 0s and 1s don't explain themselves | 20:21 |
Curious_ | yeah :D | 20:21 |
Curious_ | luckily i know about hw stuff a bit | 20:22 |
Curious_ | i am an EE guy | 20:22 |
emwe | EE? | 20:23 |
stinebd | electrical engineering | 20:23 |
Curious_ | electrical engineer | 20:23 |
stinebd | the guys not smart enough to write programs ;) | 20:24 |
Curious_ | lol | 20:24 |
Curious_ | nope the guys who are curious for the deepest | 20:24 |
Curious_ | at least me :)= | 20:24 |
Curious_ | i can write hi level | 20:25 |
Curious_ | low level | 20:25 |
Curious_ | but no mid :D | 20:25 |
Curious_ | it needs comprehensive knowledge | 20:25 |
Curious_ | especially when you are working with OS | 20:25 |
Curious_ | not a simple embedded device | 20:26 |
emwe | so gnight peeps | 20:27 |
emwe | panel madness has to continue tomorrow. what a pita. | 20:27 |
*** emwe has quit IRC | 20:27 | |
stinebd | byebye | 20:27 |
arrrghhh | so stinebd can you explain the newest rootfs commit in laymans terms? what changed? | 20:29 |
stinebd | emwe made it smarter. it doesn't try to blindly set brightness anymore | 20:29 |
stinebd | shouldn't be much of a difference for us, but apparently the old logic broke topaz | 20:29 |
arrrghhh | oh | 20:30 |
Curious_ | thnx for everything | 20:33 |
Curious_ | time to bed | 20:33 |
Curious_ | nn | 20:33 |
*** Curious_ has quit IRC | 20:33 | |
stinebd | byebye | 20:38 |
arrrghhh | that's some lag you got goin there stine :P | 20:39 |
stinebd | people leave too fast | 20:39 |
arrrghhh | dicks. | 20:40 |
arrrghhh | so hey something blew up on my building of the image. | 20:40 |
arrrghhh | well, 5 things blew up but i was able to fix 'em all | 20:40 |
arrrghhh | not sure what the latest one was, gonna try & deicpher... | 20:40 |
arrrghhh | wow, and that screen session is apparently full of jibberish... | 20:42 |
*** leobaillard has quit IRC | 20:43 | |
arrrghhh | ever seen anything like this? | 20:44 |
arrrghhh | http://yfrog.com/ev73612706p | 20:44 |
stinebd | reset | 20:44 |
arrrghhh | never saw those before trying to build this image :P | 20:44 |
arrrghhh | hrm | 20:46 |
arrrghhh | just did another make -j5, seems to be workin | 20:46 |
arrrghhh | we'll see what happens this time... | 20:46 |
arrrghhh | what causes that screen corruption tho? | 20:46 |
stinebd | never seen it on a make before, but generally catting a binary file would do that | 20:47 |
arrrghhh | hrm | 20:48 |
*** jensen_ has quit IRC | 20:50 | |
*** jensen has joined #xdandroid | 20:50 | |
arrrghhh | well now i'm perplexed | 20:53 |
arrrghhh | so i didn't see any build errors... | 20:53 |
arrrghhh | but in out/target/product/msm/root there's folders... but they're all empty. | 20:53 |
arrrghhh | i'm assuming i'll get a system.img file in the root/system folder?' | 20:53 |
stinebd | no | 20:54 |
stinebd | you'll get a system.img in out/target/product/msm | 20:54 |
arrrghhh | nope. | 20:54 |
stinebd | seen the docs? | 20:54 |
*** Reefermattness has joined #xdandroid | 20:54 | |
arrrghhh | http://xdandroid.com/wiki/Building_and_Packaging | 20:54 |
arrrghhh | that's where i am | 20:54 |
stinebd | yeah | 20:54 |
arrrghhh | # of cpus available plus one... so i did make -j5 | 20:55 |
stinebd | and what's the last word out of make? | 20:55 |
stinebd | or perhaps words | 20:55 |
arrrghhh | fawk | 20:56 |
arrrghhh | i closed the screen session evidently. | 20:56 |
arrrghhh | let's try that again... | 20:56 |
arrrghhh | oh do i need to be root to make? | 20:57 |
stinebd | no | 20:57 |
stinebd | but pay heed to the big red box | 20:57 |
stinebd | or pink i guess | 20:57 |
arrrghhh | ... | 20:57 |
arrrghhh | ah there's the error | 20:58 |
arrrghhh | no rule to make target `vendor/xdandroid/msm/proprietary/libgps.so' | 20:58 |
stinebd | ah so you messed up | 20:58 |
stinebd | that comes from the dream proprietary image | 20:59 |
arrrghhh | something i forgot to drop in? | 20:59 |
stinebd | so either you didn't download it and place it in aosp root or you didn't unzip-files | 20:59 |
arrrghhh | i downloaded those zips | 21:00 |
arrrghhh | and ran the ./unzip-files.sh script... | 21:00 |
arrrghhh | maybe something went wrong wif 'em. | 21:00 |
stinebd | yeah you did something wrong for sure | 21:00 |
arrrghhh | lol | 21:00 |
Reefermattness | arrrghhh, did you do that script with -g at the end or are we past that now stinebd ? :) | 21:01 |
arrrghhh | definitely had a -g | 21:01 |
arrrghhh | not past that yet :P | 21:01 |
stinebd | XDAndroid runs on hardware similar to the HTC G1 and Android Dev Phone. As a result, XDAndroid takes advantage of the similarities by using certain proprietary libraries as provided by the reference system for the Dev Phone. Before building the system, download the Dev Phone system image, signed-dream_devphone_userdebug-ota-14721.zip, from HTC Developer Center. Place the zip file in the root of your XDAndroid source tree and do not extract it. | 21:01 |
arrrghhh | did that | 21:02 |
arrrghhh | i'll do it again tho | 21:02 |
arrrghhh | don't need to copy&paste :P | 21:02 |
stinebd | can't help it if you don't read/understand the docs :P | 21:02 |
arrrghhh | well | 21:02 |
arrrghhh | read i did | 21:02 |
arrrghhh | understand... not quite over my head yet. | 21:02 |
arrrghhh | but getting there :P | 21:02 |
stinebd | btw in case you're wondering, i'd add a switch to download that automatically too but htc doesn't let you | 21:03 |
arrrghhh | hrm | 21:03 |
Reefermattness | arrrghhh, whats the error message? | 21:04 |
arrrghhh | that no rule to make target one | 21:04 |
stinebd | he didn't put the dream proprietary image in the right spot | 21:05 |
arrrghhh | make: *** No rule to make target `vendor/xdandroid/msm/proprietary/libgps.so', needed by `out/target/product/msm/obj/lib/libgps.so'. Stop. | 21:05 |
arrrghhh | doin it again | 21:05 |
arrrghhh | NOT extracted right? | 21:05 |
stinebd | not extracted | 21:05 |
Reefermattness | no :) | 21:05 |
stinebd | aosp root | 21:05 |
arrrghhh | cuz i swear i did that too :P | 21:05 |
arrrghhh | ok, doin the zip thing again... i wonder if i did just mv it to the wrong place. | 21:05 |
arrrghhh | in ~/xdandroid basically...? | 21:06 |
stinebd | the same directory you repo sync'd in | 21:06 |
arrrghhh | hrm | 21:06 |
stinebd | and buildspec.mk is in, etc etc | 21:06 |
arrrghhh | i guess i'll copy it to ~ | 21:06 |
stinebd | uh | 21:07 |
arrrghhh | buildspec.mk is in ~/xdandroid... | 21:07 |
arrrghhh | /home/<user>/ | 21:07 |
wladston | arrrghhh: trying to build ? hehe, to build is easy, prepare your ass if you want to edit :) | 21:07 |
stinebd | i know what ~ is | 21:07 |
stinebd | i've been unixing since you were in diapers | 21:07 |
arrrghhh | i doubt you're that old. | 21:07 |
stinebd | i was a computer scientist in a previous life | 21:07 |
arrrghhh | lol | 21:07 |
wladston | lol | 21:08 |
arrrghhh | well i'm sorry i evidently was not ;) | 21:08 |
wladston | I had no time to touch android source today :( will just apply the new paches and put it on the phone | 21:08 |
wladston | then race to bed :) | 21:09 |
arrrghhh | stinebd, i did my best to follow your directions to the T. re-reading them again, i don't see where i messed up TBH... | 21:10 |
arrrghhh | i put it in the 'recommended' location to hopefully make it easier to figure out what i did screw up :P | 21:10 |
stinebd | no worries, it's confusing to everyone at first | 21:10 |
stinebd | imagine me doing all that without any documentation | 21:11 |
arrrghhh | yea, no thanks. | 21:11 |
arrrghhh | this is why i let you do it first. | 21:11 |
stinebd | i purposely wrote those procedures in paragraph form instead of list form to hopefully help explain what's going on for people who did screw up | 21:11 |
arrrghhh | lmao ok i'll got thru it again. | 21:12 |
stinebd | basically all you have to do is make sure the dream image is in aosp root and then go into device/xdandroid/msm and run unzip-files.sh again | 21:14 |
stinebd | then go back to aosp root and make | 21:14 |
arrrghhh | alrighty. | 21:14 |
arrrghhh | i promise i did do that... i'm wondering if i'm not thinking aosp root is what i think it is... | 21:15 |
arrrghhh | you said where i did the repo sync from. | 21:15 |
stinebd | same place you keep buildspec.mk at | 21:15 |
arrrghhh | lemme see if i can verify i did that where i thinks i did that. | 21:15 |
arrrghhh | yea, that's definitely at ~/xdandroid | 21:15 |
*** hardwalker has joined #xdandroid | 21:20 | |
wladston | new images were added to roofs wonder what that is for | 21:20 |
arrrghhh | topaz | 21:20 |
arrrghhh | wladston, have you read the logs? :P | 21:21 |
wladston | oh, kay | 21:21 |
wladston | nope | 21:21 |
wladston | I've had no time to do anything droid today | 21:21 |
wladston | :( | 21:21 |
wladston | arrrghhh: I know that you are having a hard time to make a build | 21:21 |
wladston | :) | 21:21 |
wladston | wish I could help you, but I'm already a bit late for bed | 21:21 |
wladston | heading for bed ... night guys! | 21:23 |
*** wladston has quit IRC | 21:24 | |
arrrghhh | ok stinebd, i have the hw3d.zip, the gapps-hdpi.zip and the dream_devphone.zip all in ~/xdandroid. | 21:29 |
arrrghhh | i cd to device/xdandroid/msm and run the scrip | 21:30 |
arrrghhh | t | 21:30 |
F22 | hmm...there doesn't appear to be a > in the keymap for the rhodium 210, but there is one for the 400. | 21:30 |
arrrghhh | and it does its thing | 21:30 |
arrrghhh | do i need to +x the buildspec file or something? | 21:30 |
arrrghhh | F22, yea i think someone just shoehorned it in there for the 400 | 21:30 |
arrrghhh | same with | | 21:30 |
arrrghhh | is there a | on the 210 keymap? | 21:31 |
F22 | someone did shoehorn the | in. | 21:31 |
F22 | it's alt-y | 21:31 |
arrrghhh | haha | 21:31 |
arrrghhh | stinebd, i get a bunch of junk in the terminal when that command finishes. i do see some english at the bottom, removing zipfile comments... | 21:32 |
XirXes | F22: while your playin around in the 210 keymap you should put tab in there | 21:34 |
arrrghhh | tab's not in there...? | 21:34 |
*** ox0spy has joined #xdandroid | 21:34 | |
XirXes | if you can. idk the code for it but i bet its something along the line of 0xXX | 21:35 |
XirXes | is tab in other keymaps? | 21:35 |
stinebd | arrrghhh: yeah that's normal. it's removing zipfile comments from the google apps (which are made by signapk) | 21:35 |
XirXes | my votes on ALT-Q | 21:35 |
stinebd | and no need to chmod +x buildspec.mk, it's not a script | 21:35 |
F22 | i could swear i stumbled on tab while looking for the >. i'll take another look. | 21:36 |
arrrghhh | tab works for me | 21:38 |
arrrghhh | XirXes, if you mean to move between input boxes, use arrow keys. | 21:38 |
XirXes | i want it for auto complete in terminal | 21:38 |
arrrghhh | oh... that works? | 21:38 |
arrrghhh | i thought it was the search button | 21:38 |
arrrghhh | that we don't have | 21:39 |
XirXes | idk. i have a search button now. if thatl do it id be happy with that | 21:39 |
XirXes | arrrghhh: what key does tab for you? | 21:40 |
F22 | alt-, is tab | 21:40 |
arrrghhh | really? | 21:41 |
arrrghhh | i must be drunk. | 21:41 |
arrrghhh | i'm thinking of my raph... | 21:41 |
*** programmer8922 has joined #xdandroid | 21:41 | |
* arrrghhh puts on the dunce cap. | 21:41 | |
XirXes | so its 0x9 then? | 21:42 |
F22 | :D | 21:42 |
F22 | yup, that's what google android maps tab to. | 21:42 |
F22 | http://source.android.com/porting/keymaps_keyboard_input.html | 21:42 |
F22 | on a native android phone it looks like it's fn-space | 21:44 |
F22 | yup, asci hex for tab is 9 | 21:50 |
F22 | confirmed | 21:50 |
F22 | ascii | 21:50 |
*** TheDeadCPU has quit IRC | 21:51 | |
F22 | ok i'm seriously tempted to move tab from alt-, to alt-space, and then use alt-, for < and alt-. for > as on a pc keyboard. | 21:53 |
*** TheDeadBOT has joined #xdandroid | 21:55 | |
*** JesusFreak316 has joined #xdandroid | 21:56 | |
arrrghhh | alright | 21:57 |
arrrghhh | here goes another build attempt. | 21:57 |
arrrghhh | and same failure. | 21:57 |
F22 | is this the bt stuff you're working on? | 21:58 |
arrrghhh | no. | 21:58 |
* arrrghhh is not a dev. | 21:58 | |
F22 | oh doh, confused you with NeoMatrix | 21:59 |
F22 | sorry | 21:59 |
arrrghhh | lol np | 21:59 |
arrrghhh | not sure how you managed to do that :P | 21:59 |
*** sle118 has quit IRC | 21:59 | |
*** TheDeadPHONE has joined #xdandroid | 21:59 | |
F22 | probably because acl wanted to promote you from chief tester to a dev. ;) | 21:59 |
*** TheDeadPHONE has quit IRC | 22:00 | |
arrrghhh | stinebd, soooooooo i definitely do not have a libgps.so in vendor/xdandroid/msm/proprietary ... | 22:00 |
arrrghhh | yea well, i'm just tryin to get my feet wet here haha | 22:01 |
stinebd | unzip -l ~/xdandroid/signed-dream_devphone_userdebug-ota-14721.zip system/lib/libgps.so :P | 22:01 |
arrrghhh | lol ok | 22:02 |
arrrghhh | i don't copy it to vendor/xdandroid/msm/proprietary? | 22:03 |
stinebd | is the zip file there, and is libgps.so in it? | 22:04 |
*** TheDeadCPU has joined #xdandroid | 22:05 | |
stinebd | (unzip -l will tell you) | 22:05 |
*** TheDeadBOT has quit IRC | 22:06 | |
arrrghhh | zip is there | 22:06 |
arrrghhh | but no libgps.so.... | 22:06 |
stinebd | ... | 22:06 |
arrrghhh | boot.img, recovery.img, system.img... | 22:06 |
arrrghhh | oh crap | 22:06 |
stinebd | wut | 22:06 |
arrrghhh | i dled the img | 22:06 |
arrrghhh | not the ota | 22:06 |
*** TheDeadBOT has joined #xdandroid | 22:09 | |
*** TheDeadBOT has quit IRC | 22:11 | |
arrrghhh | acp: unable to remove 'out/target/product/msm/system/bin/akmd': No such file or directory eh? | 22:19 |
arrrghhh | stinebd, this one may not be user-error. but the rest of 'em have, so it is probably something i did wrong... blargh. | 22:22 |
stinebd | ? | 22:28 |
*** leobaillard has joined #xdandroid | 22:29 | |
*** arrrghhh has quit IRC | 22:32 | |
*** arrrghhh has joined #xdandroid | 22:38 | |
stinebd | ? | 22:40 |
arrrghhh | so i'm not sure what that error is. | 22:42 |
arrrghhh | i'm guessing you don't either? | 22:42 |
stinebd | no idea | 22:45 |
arrrghhh | damnit. | 22:46 |
arrrghhh | i had that & some warnings... | 22:46 |
arrrghhh | i figured that was the error it stopped on tho. | 22:46 |
arrrghhh | the next line is error 1 with the same directory | 22:47 |
* stinebd shrugs | 22:49 | |
stinebd | make clean ; make? | 22:49 |
arrrghhh | goin for another shot. | 22:53 |
arrrghhh | seems to be going. | 22:59 |
arrrghhh | i'm assuming this is going to take some time :P | 22:59 |
stinebd | about 3 months | 23:01 |
stinebd | it should be done before gingerbread is out | 23:01 |
arrrghhh | nice. | 23:02 |
arrrghhh | i didn't do the -j either | 23:02 |
arrrghhh | just make clean make | 23:02 |
stinebd | cancel it and start over | 23:02 |
arrrghhh | well sudo make clean make | 23:02 |
arrrghhh | really?: | 23:02 |
stinebd | yeah | 23:02 |
arrrghhh | Oo | 23:02 |
stinebd | wait sudo? | 23:02 |
arrrghhh | well | 23:02 |
arrrghhh | sudo make clean | 23:02 |
stinebd | you didn't do make as root at some point did you? | 23:02 |
arrrghhh | make | 23:02 |
arrrghhh | uhm... maybe. don't remember specifically, i tried a lot of things. probably. | 23:03 |
stinebd | well anyway, definitely re-run it with the jobserver | 23:03 |
stinebd | it'll take hours without it | 23:03 |
arrrghhh | -j5? | 23:03 |
arrrghhh | cores+1 right? | 23:03 |
stinebd | sure | 23:03 |
arrrghhh | lol | 23:03 |
arrrghhh | your confidence is reassuring. | 23:04 |
stinebd | well it can be whatever you want it to be | 23:04 |
stinebd | cores+1 is just a good number | 23:04 |
arrrghhh | oh | 23:04 |
arrrghhh | jobserver, never heard of it. | 23:04 |
arrrghhh | i've never built anything this gargantuan tho | 23:04 |
arrrghhh | oh no | 23:05 |
arrrghhh | man | 23:05 |
arrrghhh | i keep reattaching this screen session. i can't seem to detach it. | 23:05 |
arrrghhh | i've never had a screen session that i couldn't detach... | 23:07 |
arrrghhh | even exiting the ssh session doesn't seem to do it... wtf. | 23:07 |
arrrghhh | ah well, it's building on another session. | 23:07 |
stinebd | screen -d? | 23:07 |
arrrghhh | i ususally do ctrl-a, then d | 23:08 |
arrrghhh | but that did work... hrm. | 23:08 |
stinebd | you can log into a new terminal and screen -d | 23:08 |
*** leobaillard has quit IRC | 23:15 | |
arrrghhh | it appears to have... finished! | 23:38 |
arrrghhh | yup. produced a 118mb system.img file | 23:39 |
arrrghhh | thanks for the help stinebd | 23:55 |
arrrghhh | can't believe i downloaded the wrong file... d'oh. | 23:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!