| 00:25.02 | *** join/#maemo norly (~norly@enpas.org) |
| 00:31.41 | *** join/#maemo norly (~norly@enpas.org) |
| 00:33.10 | *** join/#maemo trumee- (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 00:41.17 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 01:05.11 | *** join/#maemo sparetire_ (~sparetire@unaffiliated/sparetire) |
| 01:07.40 | *** join/#maemo trumee- (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 01:16.48 | *** join/#maemo Humpelstilzchen (erik@f054182160.adsl.alicedsl.de) |
| 01:24.25 | *** join/#maemo eMHa (~mh@p579DBC37.dip0.t-ipconnect.de) |
| 02:07.47 | *** join/#maemo LauRoman (~LauRoman@5-14-12-75.residential.rdsnet.ro) |
| 02:38.32 | *** join/#maemo shentey (~shentey@pa-76-5-239-31.sta.embarqhsd.net) |
| 02:45.06 | *** join/#maemo shentey (~shentey@pa-76-5-239-31.sta.embarqhsd.net) |
| 04:04.31 | *** join/#maemo FlameReaper-PC (~honoo-pc@115.132.91.239) |
| 04:05.50 | *** join/#maemo shamus (~shmaus@ip-206-192-194-12.marylandheights.ip.cablemo.net) |
| 04:14.58 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 04:20.48 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 04:26.29 | *** join/#maemo protem (~protem@unaffiliated/protem) |
| 04:28.45 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 04:35.34 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 04:44.28 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 04:51.46 | *** join/#maemo Roth (~quassel@2601:18c:c700:f254:823:ca68:e055:4d72) |
| 04:59.14 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 05:16.10 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 05:20.50 | *** part/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 05:35.07 | *** join/#maemo lobito (~lobito@186.136.162.72) |
| 05:35.32 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 05:35.34 | *** join/#maemo lobito (~lobito@186.136.162.72) |
| 05:42.22 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 06:55.53 | Sicelo | about to start fixing the USB ports on my 2 N900. second N900 has previously had a botched fix .. the 5 pads are intact, but the bigger 'support' pads are gone |
| 06:55.56 | Sicelo | :( |
| 06:57.39 | KotCzarny | maybe make some kind of bga in the bottom of usb part then just attach it firmly in the right place? |
| 06:57.41 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 06:59.52 | Sicelo | what? |
| 07:00.30 | KotCzarny | in similar way that lcd connectors ribbon make contact |
| 07:13.37 | *** join/#maemo vectis (~phil@79-65-226-101.host.pobb.as13285.net) |
| 07:37.08 | *** join/#maemo FReaper-PC (~honoo-pc@115.132.91.239) |
| 07:48.02 | *** join/#maemo KotCzarny (~ariel@afla209.neoplus.adsl.tpnet.pl) |
| 07:56.07 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:07.21 | *** join/#maemo japa-fi (~jani@mobile-access-6df0a4-86.dhcp.inet.fi) |
| 08:33.27 | *** join/#maemo Serima (~kvirc@B9255734.rev.sefiber.dk) |
| 08:34.17 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:55.37 | *** join/#maemo futpib (~futpib@176.104.204.3) |
| 09:01.09 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 09:15.44 | Sicelo | yay! |
| 09:15.50 | Sicelo | main N900 fixed. :) |
| 09:15.55 | KotCzarny | and secured? |
| 09:15.56 | Sicelo | USB working good |
| 09:16.04 | Sicelo | will do the 2nd one later |
| 09:17.07 | Sicelo | definitely secured. |
| 09:17.35 | KotCzarny | you can start your own repair shop now! |
| 09:18.41 | Sicelo | haha, no. i hated this job. wasn't as difficult as i thought it would be, but still |
| 09:18.54 | KotCzarny | but moneys! |
| 09:19.12 | KotCzarny | also, you will get experienced enough to make it easy |
| 09:20.23 | Sicelo | will consider that. g2g |
| 09:46.17 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 09:47.34 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 09:47.57 | *** join/#maemo Marshall_Banana (~marshall_@x2f294b0.dyn.telefonica.de) |
| 10:04.49 | *** join/#maemo norly (~norly@enpas.org) |
| 10:08.50 | *** join/#maemo ssvb (~ssvb@85-76-110-238-nat.elisa-mobile.fi) |
| 10:36.06 | *** join/#maemo xorly (~xorly@ip-86-49-15-121.net.upcbroadband.cz) |
| 10:45.46 | Pali | tada... maemo5 running with 4.2-rc2 kernel! |
| 10:45.56 | KotCzarny | *slowclap* |
| 10:46.00 | KotCzarny | but is it.. stable? |
| 10:46.04 | Pali | if you need some log or test let me know |
| 10:46.24 | KotCzarny | um, phone/camera/audio/wifi/gps workings? |
| 10:46.37 | Pali | KotCzarny: no, I tried to boot it 10 times |
| 10:46.40 | KotCzarny | (and usual, kb and touchscreen) |
| 10:46.44 | Pali | and only now I got it |
| 10:46.57 | Pali | phone not, camera not, audio not, wifi yes, gps not |
| 10:47.22 | Pali | http://elinux.org/N900 --> state of kernel drivers |
| 10:47.31 | KotCzarny | Sorry! This site is experiencing technical difficulties. |
| 10:47.33 | KotCzarny | :) |
| 10:47.39 | KotCzarny | (Cannot contact the database server) |
| 10:47.41 | Pali | wiki is down |
| 10:47.58 | KotCzarny | overwhelmed by success? |
| 10:52.26 | Pali | cellular: ssc[7090]: modem connection cannot be established, retry (1 of 10) |
| 10:52.44 | Pali | ... |
| 10:52.45 | Pali | cellular: ssc[7090]: modem connection cannot be established, retry (10 of 10) |
| 10:52.50 | Pali | cellular: ssc[7090]: modem connection cannot be established, giving up |
| 10:53.20 | Pali | so nokia-modem/hsi/ssi is not working :-( |
| 10:53.24 | Pali | with 4.2 kernel |
| 10:53.33 | KotCzarny | could be something trivial? |
| 10:53.40 | DocScrutinizer05 | I'd power it up first |
| 10:53.44 | Pali | ask freemangordon |
| 11:14.22 | *** join/#maemo rd_ (~rd@p57A0FEB1.dip0.t-ipconnect.de) |
| 11:59.00 | *** join/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 12:31.23 | *** join/#maemo vakkov_ (~vakkov@vlan-173-game-63.comnet.bg) |
| 12:34.06 | *** join/#maemo rd_ (~rd@p57A0FEB1.dip0.t-ipconnect.de) |
| 12:53.45 | *** join/#maemo sunny_s (~sunny_s@pd95c1f18.dip0.t-ipconnect.de) |
| 13:23.07 | *** join/#maemo LauRoman (~LauRoman@5-14-12-75.residential.rdsnet.ro) |
| 13:27.47 | *** join/#maemo sunny_s (~sunny_s@pd95c1f18.dip0.t-ipconnect.de) |
| 13:55.36 | *** join/#maemo trumee_ (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 14:02.28 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 14:10.02 | *** join/#maemo japa-fi (~jani@mobile-access-6df012-174.dhcp.inet.fi) |
| 14:23.00 | *** join/#maemo japa-fi (~jani@mobile-access-6df012-174.dhcp.inet.fi) |
| 14:25.48 | *** join/#maemo sunny_s (~sunny_s@pd95c1f18.dip0.t-ipconnect.de) |
| 14:55.52 | *** join/#maemo bef0rd (~beford@unaffiliated/beford) |
| 14:59.03 | *** join/#maemo trumee_ (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 15:03.06 | *** join/#maemo japa-fi (~jani@mobile-access-6df012-174.dhcp.inet.fi) |
| 15:15.49 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 15:26.53 | *** join/#maemo rd_ (~rd@p57A0FEB1.dip0.t-ipconnect.de) |
| 15:31.36 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 15:36.01 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 15:43.06 | *** part/#maemo xray256 (~xray256@90.213.15.199) |
| 15:54.02 | *** join/#maemo xray256 (~xray256@90.213.15.199) |
| 15:54.30 | *** join/#maemo trumee- (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 16:08.27 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 16:09.15 | *** part/#maemo Xes (~xes@unaffiliated/xes) |
| 16:12.50 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 16:25.21 | *** join/#maemo Saif (75d84aec@gateway/web/freenode/ip.117.216.74.236) |
| 16:34.39 | Saif | great day to all . |
| 16:34.55 | L29Ah | allah akbar |
| 16:52.25 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 17:11.58 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 17:25.30 | *** join/#maemo RzR (~RzR@unaffiliated/rzr) |
| 17:28.20 | *** join/#maemo RzR (~RzR@82.236.136.171) |
| 17:32.18 | *** join/#maemo recharged (~recharged@d192-24-55-33.try.wideopenwest.com) |
| 17:33.10 | recharged | Hi. |
| 17:34.01 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 17:34.50 | *** part/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 17:34.57 | *** join/#maemo vectis (~phil@79-65-225-168.host.pobb.as13285.net) |
| 17:35.59 | DocScrutinizer05 | hi |
| 17:37.31 | recharged | I just had a quick question about the N900, and I was wondering if anyone could help out |
| 17:37.42 | DocScrutinizer05 | ~ask |
| 17:37.42 | infobot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 17:37.58 | KotCzarny | most likely someone can, anyone usually mean noone |
| 17:38.05 | KotCzarny | *means |
| 17:38.30 | recharged | how do you use 0xFFFF to flash the N900 (if possible)? |
| 17:38.37 | KotCzarny | ~flashing |
| 17:38.37 | infobot | it has been said that maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh |
| 17:38.46 | KotCzarny | ~0xffff |
| 17:38.46 | infobot | [0xffff] https://github.com/pali/0xFFFF, or http://talk.maemo.org/showthread.php?t=87996 |
| 17:38.50 | KotCzarny | ~0xFFFF |
| 17:38.50 | infobot | extra, extra, read all about it, 0xffff is https://github.com/pali/0xFFFF, or http://talk.maemo.org/showthread.php?t=87996 |
| 17:39.03 | DocScrutinizer05 | I think you use it mostly similar way like flasher-3.5 |
| 17:40.03 | recharged | how do you unpack fiasco images? I have the bin files, but I'm not too sure what to do. I've never flashed my N900 before |
| 17:40.21 | DocScrutinizer05 | you don't unpack them |
| 17:40.38 | KotCzarny | recharged: see the wiki page |
| 17:40.40 | recharged | o |
| 17:40.42 | KotCzarny | read first |
| 17:40.46 | KotCzarny | rtfm |
| 17:40.50 | recharged | which wiki? |
| 17:40.54 | KotCzarny | ~flashing |
| 17:40.54 | infobot | hmm... maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh |
| 17:40.57 | DocScrutinizer05 | http://wiki.maemo.org/Updating_the_tablet_firmware |
| 17:41.13 | KotCzarny | ~maemo-flashing |
| 17:41.14 | infobot | well, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh |
| 17:41.33 | DocScrutinizer05 | KotCzarny: what's wrong? |
| 17:41.34 | KotCzarny | it catches both phases or just subpattern match? |
| 17:41.40 | DocScrutinizer05 | no |
| 17:41.50 | KotCzarny | *phrases |
| 17:41.53 | DocScrutinizer05 | ~literal flashing |
| 17:41.53 | infobot | "flashing" is "<reply>see maemo-flashing" |
| 17:41.58 | recharged | there's nothing on 0xFFFF, I've read through this before |
| 17:42.00 | KotCzarny | alias then |
| 17:42.24 | KotCzarny | recharged: may i ask why are you trying 0xffff instead of flasher-3.5 ? |
| 17:42.38 | DocScrutinizer05 | recharged: 0xFFFF is a "drop in replacement" for flasher-3.5 |
| 17:43.09 | DocScrutinizer05 | the options may have slightly different syntax |
| 17:43.20 | recharged | flasher-3.5 is non-free, and ia32-libs aren't in debian sid to use |
| 17:43.56 | Pali | 0xFFFF contains --help |
| 17:43.58 | Pali | also manpage |
| 17:44.01 | DocScrutinizer05 | yep |
| 17:44.02 | Pali | and examples in doc/ |
| 17:44.05 | DocScrutinizer05 | of course :-) |
| 17:44.28 | DocScrutinizer05 | it's built and packaged by a smart guy, after all ;-) |
| 17:44.50 | KotCzarny | and 2 faq files |
| 17:45.06 | recharged | I've read all of those, but what do I do with the bin files? |
| 17:45.09 | Pali | recharged: https://github.com/pali/0xFFFF/blob/master/doc/examples |
| 17:45.19 | DocScrutinizer05 | recharged: you flash them |
| 17:45.46 | Pali | recharged: search for "Flash FIASCO image and reboot:" in examples file |
| 17:46.03 | KotCzarny | pali, put that examples as a output of 0xFFFF -h or something |
| 17:46.23 | DocScrutinizer05 | Flash FIASCO image and reboot: |
| 17:46.25 | DocScrutinizer05 | $ 0xFFFF -M <file> -f -r |
| 17:46.51 | DocScrutinizer05 | Pali: you should move that to top, it's by far the most common use |
| 17:47.02 | *** join/#maemo lobito (~lobito@186.136.162.72) |
| 17:47.15 | recharged | I'll try it, thank you |
| 17:47.15 | KotCzarny | also, add more info what do you need to flash and when |
| 17:47.26 | DocScrutinizer05 | :nod: |
| 17:47.35 | DocScrutinizer05 | recharged: yw :-) |
| 17:47.56 | Pali | note that 0xFFFF does not support flashing MMC images (yet) |
| 17:48.40 | DocScrutinizer05 | aka VANILLA |
| 17:50.59 | recharged | I tried that and it gave me "Error: Nothing to do" |
| 17:51.11 | KotCzarny | paste exact cmd line |
| 17:51.49 | recharged | 0xFFFF -M RX-51_2009SE_20.2010.36-2.002_PR_COMBINED_002_ARM.bin |
| 17:51.49 | recharged | 0xFFFF v0.6.1 // Open Free Fiasco Firmware Flasher |
| 17:51.49 | recharged | Error: Nothing to do |
| 17:51.53 | DocScrutinizer05 | no, not exact cmdline, it needs a real filename of fiasco image file instead <file> |
| 17:52.10 | KotCzarny | doc: i meant his line that he is using |
| 17:52.33 | recharged | I'm sorry about this |
| 17:52.37 | DocScrutinizer05 | Pali: ^^^ o.O |
| 17:52.51 | DocScrutinizer05 | recharged: no need to feel sorry |
| 17:53.07 | Pali | recharged: -f is missing |
| 17:53.18 | DocScrutinizer05 | LOL |
| 17:53.22 | DocScrutinizer05 | that was easy |
| 17:53.34 | Pali | 0xFFFF -M file.bin -f |
| 17:53.45 | recharged | oh wow |
| 17:53.52 | Pali | 0xFFFF was right, "Nothing to do"! |
| 17:53.59 | DocScrutinizer05 | :-> |
| 17:54.08 | recharged | thank you so much |
| 17:55.42 | recharged | now I just restart it, right? |
| 17:56.02 | Pali | if everything is OK, yes, reboot |
| 17:56.15 | recharged | h-how do I know if everything is okay? |
| 17:56.26 | Pali | there is no error/warning |
| 17:56.26 | DocScrutinizer05 | you need to first power up N900 while holding U key so it stays in NOKIA screen with USB logo |
| 17:56.34 | recharged | I did that |
| 17:56.41 | recharged | so it should be fine |
| 17:56.49 | Pali | post output from 0xFFFF if you are unsure |
| 17:58.03 | DocScrutinizer05 | Pali: will 0xFFFF do the "no suitable devie found. Waiting..." thing? |
| 17:58.10 | Pali | yes |
| 17:58.42 | recharged | is it normal for the initial boot to take a lot longer? |
| 17:58.48 | Pali | yes |
| 17:58.54 | DocScrutinizer05 | absolutely |
| 17:58.55 | Pali | optification |
| 17:58.57 | recharged | alright, good |
| 17:59.11 | recharged | because my issue was a boot loop |
| 17:59.21 | recharged | from purging all non-free software |
| 17:59.23 | recharged | (did not work) |
| 18:00.09 | DocScrutinizer05 | http://wiki.maemo.org/Updating_the_tablet_firmware#the_complete_foolproof_procedure >>After flashing unplug your device from PC prior to first boot. First boot can take several minutes, and screen may turn dark during that. You may try lock-slider switch, but do not power down device during first boot, until it finally finished...<< |
| 18:00.27 | recharged | it seems to be fine so far, so I assume it's good |
| 18:00.32 | recharged | thank you so much |
| 18:01.00 | *** join/#maemo trumee_ (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 18:02.29 | DocScrutinizer05 | consider hooking it up to charger already |
| 18:03.22 | recharged | i'm about to do that |
| 18:03.35 | recharged | s-so who's hyped about neo900? |
| 18:04.12 | DocScrutinizer05 | hm? |
| 18:04.51 | DocScrutinizer05 | I'm a great fan of Neo900 *blink* *blink* |
| 18:05.23 | DocScrutinizer05 | ;-) |
| 18:05.33 | recharged | one day |
| 18:06.19 | DocScrutinizer05 | the preorder window for complete devices is closing soonish |
| 18:08.03 | DocScrutinizer05 | it's pretty hard to get the needed N900 to upgrade them, and it gets harder by each other day |
| 18:08.06 | recharged | it seems like a great idea, but a lot of things about it worry me |
| 18:08.53 | DocScrutinizer05 | maybe you want to /join #neo900 ? |
| 18:09.43 | recharged | I've never thought of that, maybe after work |
| 18:09.54 | recharged | I'm not normally in irc channels |
| 18:10.44 | DocScrutinizer05 | you're welcome to join #neo900 channel any time, ask whatever worries you |
| 18:12.16 | recharged | mostly it's just the fact that there's seemingly more non-free software needed to get modules to work. at first it was just hardware acceleration and telephone stack, but now it seems like there's more, and they aren't informing us |
| 18:12.24 | recharged | but i'm sure it'll get worked out |
| 18:12.50 | recharged | anyway, I had another question about the n900, if this can be answered |
| 18:13.34 | Gadgetoid | I miss the n900 :( |
| 18:14.37 | DocScrutinizer05 | recharged: no, we don't need any other non-free software |
| 18:15.26 | recharged | didn't nfc need it, though? or it was something without a free firmware available. |
| 18:16.13 | DocScrutinizer05 | not even telephone stack is non-free (distinguishing between what's called telephony stack in application land aka linux, and the firmware on modem module you never even will see a bit or byte of) |
| 18:17.00 | recharged | really? |
| 18:17.09 | DocScrutinizer05 | NFC is completely open, see werner's very fine groundbreaking whitepaper on NFC design: http://neo900.org/stuff/papers/nfc-draft.pdf |
| 18:17.11 | recharged | maybe I read wrong, though. |
| 18:18.13 | DocScrutinizer05 | actually we have a NFC subsystem that's more open than any dev-board or lab eval board you could find out there |
| 18:18.31 | recharged | that's really awesome |
| 18:18.42 | recharged | I'm guessing you're a part of the dev team? |
| 18:18.44 | DocScrutinizer05 | you even can implement your own new NFC protocols on it |
| 18:18.56 | DocScrutinizer05 | ~docscrutinizer |
| 18:18.56 | infobot | somebody said docscrutinizer was jOERG, a HW-developer and engineer of Openmoko |
| 18:19.02 | DocScrutinizer05 | ~joerg |
| 18:19.02 | infobot | from memory, joerg is a natural born EE, ex HW-developer and engineer of Openmoko. Usually known as DocScrutinizer. Initiator of http://neo900.org |
| 18:19.38 | Gadgetoid | Nobody knows who DocScrutinizer05 is, he comes with the wind, goes with the tide, and leaves a wake of majesty wherever he treads |
| 18:19.55 | DocScrutinizer05 | hrhrhrhr |
| 18:20.05 | recharged | makes much more sense now |
| 18:20.20 | DocScrutinizer05 | I'm commonly known as "the grumpy old fart" |
| 18:21.39 | recharged | why go as two different names? |
| 18:22.04 | Gadgetoid | ... |
| 18:22.24 | DocScrutinizer05 | hmm? |
| 18:22.26 | Gadgetoid | Your parents named you recharged? |
| 18:22.33 | DocScrutinizer05 | :-D |
| 18:22.43 | recharged | it's possible |
| 18:23.44 | DocScrutinizer05 | anyway please don't miss our best page on the website: http://neo900.org/resources |
| 18:24.28 | recharged | don't worry, I've read through the site a lot. it's just funds are low currently |
| 18:24.57 | recharged | also, may I ask a quick question? |
| 18:25.45 | DocScrutinizer05 | ~ask |
| 18:25.45 | infobot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 18:26.28 | recharged | is it possible to enhance the n900's gsm signal with a config file? or anyway possible? |
| 18:26.46 | DocScrutinizer05 | absolutely no |
| 18:27.02 | recharged | I was afraid of that |
| 18:27.24 | DocScrutinizer05 | what's wrong with N900 gsm signal? |
| 18:27.30 | KotCzarny | does n900 have external antenna port on the board? |
| 18:27.34 | DocScrutinizer05 | yes |
| 18:27.38 | KotCzarny | then yes |
| 18:27.40 | recharged | I don't get a signal at all in my house |
| 18:27.50 | recharged | I have to put it by a window to get one bar |
| 18:28.18 | KotCzarny | put a mirror there? |
| 18:28.24 | DocScrutinizer05 | hmm, there are solutions for that, consisting of an external antenna, some box in between, and an internal antenna |
| 18:28.41 | DocScrutinizer05 | yes, it's almost "a mirror" |
| 18:29.22 | recharged | what's the most feasible option? |
| 18:29.41 | KotCzarny | recharged: put n900 on the window and handsfree bt box on the desk? |
| 18:29.58 | KotCzarny | easiest and requires no hacking |
| 18:30.09 | DocScrutinizer05 | http://www.aliexpress.com/store/product/GSM-booster-GSM-repeater-900Mhz-booster-GSM-signal-booster-repeater-GSM970/705657_426284742.html |
| 18:30.28 | KotCzarny | right, also check what band is better for you, 2g or 3g |
| 18:30.32 | DocScrutinizer05 | or what KotCzarny suggested ;-) |
| 18:31.43 | recharged | how would I use the handsfree box, and where would I get it? |
| 18:31.54 | recharged | and I only get 2g with at&t on my n900 |
| 18:32.34 | DocScrutinizer05 | make sure the frequency range of repeater is compatible to your carrier |
| 18:33.04 | recharged | but, I also get poor signal at other places besides my home. |
| 18:33.37 | recharged | which is why I thought maybe I could just edit a config file for the expense of battery life |
| 18:34.08 | KotCzarny | isnt at&t famous for spotty coverage? |
| 18:34.22 | recharged | yes |
| 18:34.47 | KotCzarny | here (.pl) i get pretty nice 'all bars' almost everywere |
| 18:35.44 | DocScrutinizer05 | another one (sorry for long link) http://www.lightinthebox.com/de/repetidor-de-sinal-celular-repeater-850mhz-yagi-antena-celular-handy-signal-booster-850-gsm-umts-amplificador_p3772839.html?currency=EUR&litb_from=paid_adwords_shopping&litb_from=&adword_mt=&adword_ct=84188221514&adword_kw=&adword_pos=1o4&adword_pl=&adword_net=g&adword_tar=&adw_src_id=1810908567_301588754_21687238394_kwd-80810021175&gclid=CLHs6JDDiMcCFWXJtAodIiIAlw |
| 18:36.04 | recharged | I think at&t are slowly phasing out theri 2g towers and the n900 only supports t-mobile's 3g network here |
| 18:37.06 | DocScrutinizer05 | recharged: compare to arbitrary other cellpgone on same carrier and band, when the N900 is actually sub-par you might need to clean the antenna contact in device |
| 18:37.19 | DocScrutinizer05 | yes, that too |
| 18:37.35 | recharged | I'll do that then, thank you |
| 18:37.55 | DocScrutinizer05 | yw |
| 18:38.02 | DocScrutinizer05 | afk |
| 18:38.04 | recharged | but I need to get ready for work, I could be on later. thanks for all of the help. |
| 18:38.10 | recharged | bye |
| 18:48.13 | *** join/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 18:51.51 | *** join/#maemo rd_ (~rd@p57A0FEB1.dip0.t-ipconnect.de) |
| 19:02.30 | *** join/#maemo arossdotme (~zxy@79-69-202-77.dynamic.dsl.as9105.com) |
| 19:47.33 | *** join/#maemo futpib (~futpib@176.104.204.3) |
| 19:57.31 | Sicelo | with replacement bme, does one still need to stop bme in order to calibrate? |
| 19:58.06 | *** join/#maemo arossdotme (~zxy@79-69-207-85.dynamic.dsl.as9105.com) |
| 20:23.47 | *** join/#maemo honvol7 (~honvol@ANancy-651-1-133-53.w109-221.abo.wanadoo.fr) |
| 20:35.04 | DocScrutinizer05 | no matter how you charge the battery, you want to stop it to discharge it. For premature system shutdown Pali said the replacement BME won't do that, so you don't need to stop it for discharging to empty and completing learning cycle |
| 20:36.35 | *** part/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 20:37.08 | Pali | bme-replacement does not contain any bme daemon anymore |
| 20:37.14 | Pali | at least not userspace daemon |
| 20:37.24 | Pali | so you cannot "stop bme", because there is no running |
| 20:38.06 | KotCzarny | can i install bme-replacement without rest of cssu? |
| 20:38.24 | *** join/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 20:44.22 | Pali | KotCzarny: you need kp53 |
| 20:44.22 | Sicelo | ok Pali. just one thing .. so in simple words, i just let N900 discharge until empty, and calibration should take care of itself? |
| 20:44.22 | Pali | but should work also without cssu |
| 20:44.22 | kerio | DocScrutinizer05: however, you likely want something that will fire up the charging again |
| 20:44.22 | KotCzarny | i have kp53 |
| 20:44.22 | kerio | unless you're willing to wait for like 5 hours |
| 20:44.22 | kerio | whilst looking at the n900 |
| 20:44.34 | Pali | Sicelo: yes |
| 20:44.48 | Sicelo | thanks. :) |
| 20:46.43 | Sicelo | one more thing .. bq27x00_battery module .. better to have it loaded or unloaded for replacment-bme to work properly? |
| 20:47.24 | Pali | without it bme replacment not work |
| 20:47.33 | Pali | bme replacement will load it at boot time |
| 20:50.43 | Sicelo | thanks Pali for this info |
| 20:53.44 | *** join/#maemo trumee_ (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 20:55.50 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 21:03.40 | DocScrutinizer05 | kerio: that's the point about bme stopping basically. Yes. on bme-replacement I dunno if and how you could stop charging with USB attached |
| 21:03.57 | kerio | echo "none" > /sys/class/power/whatever/mode |
| 21:04.08 | kerio | bq24150_charger? |
| 21:04.24 | DocScrutinizer05 | if the bme replacement kernel driver is designed according to my draft, it's as simple as "echo something >/sys/somewhere" |
| 21:06.28 | *** join/#maemo rd_ (~rd@p57A0FEB1.dip0.t-ipconnect.de) |
| 21:16.17 | *** part/#maemo Serima (~kvirc@B9255734.rev.sefiber.dk) |
| 21:33.49 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 21:38.42 | *** join/#maemo eMHa_ (~mh@p579DBC37.dip0.t-ipconnect.de) |
| 21:41.31 | *** part/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 22:02.18 | *** join/#maemo prometoys_ (~prometoys@unaffiliated/prometoys) |
| 22:13.04 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 22:40.19 | *** join/#maemo trumee (~trumee@c-73-155-84-209.hsd1.tx.comcast.net) |
| 23:30.22 | *** join/#maemo L29Ah (~L29Ah@195.19.225.242) |
| 23:51.46 | *** part/#maemo L29Ah (~L29Ah@195.19.225.242) |