| 12:48.04 | *** join/#maemo infobot (~infobot@rikers.org) |
| 12:48.04 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~combined ~emmc ~flasher sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 12:48.05 | *** mode/#maemo [+v infobot] by ChanServ |
| 12:48.10 | DocScrutinizer05 | ~wb |
| 12:48.11 | infobot | thx |
| 12:48.23 | Psi | logs on pc are the same, but with the 100K i can get to the non backlit nokia logo screen |
| 12:48.31 | Psi | before it would always start on the white one |
| 12:48.52 | Psi | i cant seem to get the phone to actally turn off |
| 12:49.12 | Psi | its either in usb mode or doing infinite reboots |
| 12:50.18 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 12:50.25 | Agge | Psi: shut of the PSU for at least one minute? |
| 12:50.44 | Psi | the phone always starts automatically when you insert a battery |
| 12:50.48 | DocScrutinizer05 | 2014-06-15T14:49:59.996024+02:00 localhost kernel: [2037151.880303] usb 2-1.5.3: new high-speed USB device number 11 using ehci-pci |
| 12:50.50 | DocScrutinizer05 | 2014-06-15T14:50:00.082030+02:00 localhost kernel: [2037151.966356] usb 2-1.5.3: unable to get BOS descriptor |
| 12:50.51 | DocScrutinizer05 | 2014-06-15T14:50:00.083027+02:00 localhost kernel: [2037151.967541] usb 2-1.5.3: New USB device found, idVendor=0421, idProduct=0106 |
| 12:50.53 | DocScrutinizer05 | 2014-06-15T14:50:00.083030+02:00 localhost kernel: [2037151.967545] usb 2-1.5.3: New USB device strings: Mfr=34, Product=38, SerialNumber=0 |
| 12:50.54 | DocScrutinizer05 | 2014-06-15T14:50:00.083030+02:00 localhost kernel: [2037151.967548] usb 2-1.5.3: Product: Nokia USB ROM |
| 12:50.56 | DocScrutinizer05 | 2014-06-15T14:50:00.083031+02:00 localhost kernel: [2037151.967551] usb 2-1.5.3: Manufacturer: Nokia |
| 12:51.00 | Psi | yeah, i know what it supposed to do |
| 12:51.44 | DocScrutinizer05 | that however it is supposed to do from ROM Bootloader, *unconditionally* (unless hw is defect) |
| 12:52.06 | *** join/#maemo useretail (useretail_@gateway/shell/elitebnc/x-overyhvtqzkegwac) |
| 12:52.14 | Agge | Psi: yeah but I have found that even if you remove the battery it wont start corectly unless you leve it unconected for a minute or so |
| 12:52.26 | Psi | i should trace the d- and d+ back to the usb driver chip |
| 12:52.27 | DocScrutinizer05 | while this is NOLO already: |
| 12:52.29 | DocScrutinizer05 | 2014-06-15T14:50:00.586041+02:00 localhost kernel: [2037152.469920] usb 2-1.5.3: USB disconnect, device number 11 |
| 12:52.31 | DocScrutinizer05 | 2014-06-15T14:50:01.276026+02:00 localhost kernel: [2037153.159029] usb 2-1.5.3: new high-speed USB device number 12 using ehci-pci |
| 12:52.32 | Psi | make sure they actually get there |
| 12:52.32 | DocScrutinizer05 | 2014-06-15T14:50:01.439030+02:00 localhost kernel: [2037153.321663] usb 2-1.5.3: New USB device found, idVendor=0421, idProduct=0105 |
| 12:52.34 | DocScrutinizer05 | 2014-06-15T14:50:01.439046+02:00 localhost kernel: [2037153.321676] usb 2-1.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5 |
| 12:52.35 | DocScrutinizer05 | 2014-06-15T14:50:01.439048+02:00 localhost kernel: [2037153.321677] usb 2-1.5.3: Product: Nokia N900 (Update mode) |
| 12:52.37 | DocScrutinizer05 | 2014-06-15T14:50:01.439049+02:00 localhost kernel: [2037153.321679] usb 2-1.5.3: Manufacturer: Nokia |
| 12:52.38 | DocScrutinizer05 | 2014-06-15T14:50:01.439049+02:00 localhost kernel: [2037153.321680] usb 2-1.5.3: SerialNumber: 4D554D323931313733 |
| 12:53.14 | Psi | Agge: ive started it many times after working on it unpluged for 10+ minutes and it always starts when the battery is connected |
| 12:53.27 | Agge | Psi: ok |
| 12:53.44 | *** join/#maemo Arkenoi (~ark@swsoft-msk-nat.sw.ru) |
| 12:54.43 | DocScrutinizer05 | Psi: you should check if ROM bootloader enumerates on USB |
| 12:54.54 | Psi | how do i check that |
| 12:55.08 | Psi | is it a different hold key or something |
| 12:55.24 | DocScrutinizer05 | connect powered-down device to linux machine, then provide power via USB |
| 12:56.03 | DocScrutinizer05 | ROM boot will not check for any keys pressed |
| 12:56.27 | DocScrutinizer05 | ROM BL only checks USB and enums, every single time the CPU boots |
| 12:56.53 | DocScrutinizer05 | this is how clodflash works |
| 12:57.01 | DocScrutinizer05 | ~coldflash |
| 12:57.02 | infobot | extra, extra, read all about it, coldflash is http://mg.pov.lt/maemo-irclog/%23maemo.2010-10-31.log.html#t2010-10-31T23:34:01 (jacekowski's instructions), or http://wiki.maemo.org/Updating_the_firmware/Cold_Flashing |
| 12:57.33 | Psi | same thing in logs, and phone just keeps rebooting |
| 12:57.57 | DocScrutinizer05 | it's NOT (I *repeat: NOT) recommended to do cold flashing ever, unless you have very strong ndications that NOLO is defective |
| 12:58.24 | DocScrutinizer05 | your logs are incomplete |
| 12:58.41 | DocScrutinizer05 | they only show end of a failing enum |
| 12:59.00 | DocScrutinizer05 | to see what's going on you need first few lines, not last |
| 12:59.45 | DocScrutinizer05 | it doesn't matter if device reboots or whatever |
| 13:00.34 | DocScrutinizer05 | as soon as CPU gets powered up, it executes ROM BL and (one of) first things ROM BL does is ENUM on USB, to check if a flasher asks for coldflash |
| 13:01.25 | DocScrutinizer05 | ROM BL is the initial bootloader, stored to ROM in CPU and immutable |
| 13:01.43 | Psi | this is all i get in kern.log http://pastebin.com/WSxx2zDX |
| 13:01.52 | Psi | maybe i need to enable better loging |
| 13:02.06 | DocScrutinizer05 | ROM BL does USB ENUM before it initializes any LCD or anything else |
| 13:03.25 | Psi | im familar with the message MSwindows is giving when i plug it into that, its the message you get when there is serious USB communication problems |
| 13:03.26 | DocScrutinizer05 | if that's the very first line that shows up after you attach your powered-down N900, then you got a hw problem (or driver problem on PC side, but that's pretty unlikely) |
| 13:03.49 | Psi | yeah |
| 13:04.09 | Psi | i think there must be a broken data line to the driver chip. Or the chip is fried |
| 13:04.43 | DocScrutinizer05 | particularly it shows that *some* of USB data still works, or otherwise the PC wouldn't even notice the USB device attached |
| 13:05.21 | DocScrutinizer05 | broken data line is possible but unlikely, particularly when you attached cable the way you did |
| 13:05.49 | DocScrutinizer05 | a short of one data line to something else is highly likely |
| 13:06.25 | DocScrutinizer05 | fried PHY is also possible but only likely when some terribly broken charger got attached |
| 13:06.45 | Psi | well it can be VCC or GND as i have checked ohms with DMM and its in the meg range between D- and D+ to GND or VCC |
| 13:06.55 | DocScrutinizer05 | 1707 PHY supposed to survive 5V on data line, and for sure supposed to survive data line grounded |
| 13:07.43 | DocScrutinizer05 | please check voltage on open-end D- D+ |
| 13:07.47 | DocScrutinizer05 | vs GND |
| 13:08.01 | Psi | open-end ? |
| 13:08.10 | DocScrutinizer05 | I don't recall the exact values from top of my head, but for sure not 0V |
| 13:08.18 | DocScrutinizer05 | not connected to PC |
| 13:08.26 | DocScrutinizer05 | only device powered up |
| 13:08.30 | honestly | USB uses differential signaling |
| 13:08.36 | DocScrutinizer05 | I know |
| 13:08.55 | DocScrutinizer05 | naming of D- D+ suggests that already |
| 13:09.01 | honestly | so idle connection should have both lines pulled up somewhat |
| 13:09.10 | DocScrutinizer05 | yup |
| 13:09.12 | honestly | at 2V or something like that |
| 13:09.16 | DocScrutinizer05 | :nod: |
| 13:09.20 | honestly | (: |
| 13:10.08 | Psi | both D- and D+ goto about 0.3V on DMM for about 0.5second right at power on when it vibrates |
| 13:10.12 | Psi | then goto zero volts |
| 13:10.55 | Psi | however DMM maybe lying, should really use scope |
| 13:11.51 | DocScrutinizer05 | actually I think *idle* USB device PHY has both pulled up weak (range of 100k), while active device (Vbus +5V) PHY is supposed to pull up one by 1.5k and pull down other by 15k or somesuch, depending on low speed or full speed it's either D+ or D- that's pulled up. I can't recall details from top of my head |
| 13:12.33 | DocScrutinizer05 | Psi: that sounds conclusive |
| 13:13.06 | DocScrutinizer05 | well, except for the 0.3V which probably are somewhat higher, but DMM is too slow |
| 13:13.47 | Psi | yeah, scope says its actually 0.6v |
| 13:13.48 | DocScrutinizer05 | Psi: I take it you have a lab PSU attached to battery? |
| 13:13.53 | Psi | yep |
| 13:14.01 | Psi | at 4.0V |
| 13:15.00 | DocScrutinizer05 | a battery voltage of <3.0V should cause CPU not booting and instead bq24150 charger chip asking 1707 PHY about D+/- short and depending on that it lits up the steady yellow indicator LED |
| 13:15.19 | DocScrutinizer05 | make Vbatt 2.3V please |
| 13:15.21 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 13:15.33 | DocScrutinizer05 | then apply 5V Vusb |
| 13:16.00 | DocScrutinizer05 | do this one time with open D+/- and one time with D+/- short |
| 13:17.47 | DocScrutinizer05 | sorry I have no discharged battery here, so can't reproduce the procedure. So you have to trust in my poor and clouded memory, or check the schematics and bq24150 datasheet yourself |
| 13:19.00 | DocScrutinizer05 | I *think* it's even sufficient to connect Vbatt+ and Vbatt-GND with a e.g. 100R, and not apply any voltage at all |
| 13:19.44 | Psi | yep, led comes on with D- and D+ as they are. If i short them and repeat i get no led |
| 13:19.58 | DocScrutinizer05 | ooh |
| 13:20.07 | DocScrutinizer05 | that's kinda weird |
| 13:20.08 | *** join/#maemo remarc_ (~sequantz@194.11.24.44) |
| 13:20.19 | DocScrutinizer05 | should be exactly other way round |
| 13:20.33 | DocScrutinizer05 | LED is amber? |
| 13:20.38 | Psi | yellow |
| 13:20.47 | DocScrutinizer05 | or is it red, or green, or flashing? |
| 13:20.56 | Psi | not red or green |
| 13:21.00 | DocScrutinizer05 | steady yellow, yep that's correct |
| 13:21.01 | Psi | not flashing, just solid |
| 13:21.15 | DocScrutinizer05 | weird |
| 13:21.21 | Psi | it wouldnt be able to draw the full 1A charge from usb PC 5v anyway |
| 13:21.39 | DocScrutinizer05 | np, that's not what it tries to do |
| 13:22.29 | DocScrutinizer05 | it however would try to charge up battery from charger with as much as it can pull from USB |
| 13:22.44 | DocScrutinizer05 | can you see on lab PSU how much it pulls |
| 13:22.46 | DocScrutinizer05 | ? |
| 13:23.18 | DocScrutinizer05 | or see voltage on battery pins going up, or sth? |
| 13:23.28 | Psi | yep, i can see that, it pulls the 2.3v up to 3.25V |
| 13:23.43 | Psi | can see it on lab psu meter |
| 13:24.20 | DocScrutinizer05 | It might be that it charges "battery" with 100mA when D+/- ope circuit, and tries with 500ma on D+/- short, thus causing Vbus supply cutting out and no yellow LED |
| 13:24.41 | DocScrutinizer05 | 3.25 is correct for charging, yes |
| 13:24.57 | DocScrutinizer05 | it's emergency charging end voltage |
| 13:25.11 | Psi | ah, makes sense |
| 13:25.46 | Psi | do you know if the usb driver IC is BGA or not |
| 13:25.52 | DocScrutinizer05 | when end voltage reached, bq24150 quits emergency charging and allows CPU to boot up |
| 13:26.04 | DocScrutinizer05 | it's BGA, yes |
| 13:27.09 | DocScrutinizer05 | http://wiki.maemo.org/N900_Hardware_USB#USB_Phy |
| 13:27.33 | Psi | is there a manual for the n900 which matches the part numbers in the schmatic diagram to physical locations on the pcb? |
| 13:28.59 | DocScrutinizer05 | the schematics itself has that, at end (page 15 orso) |
| 13:29.10 | Psi | really, i must have missed it |
| 13:29.11 | Psi | looks |
| 13:29.58 | DocScrutinizer05 | sorry, page 16 |
| 13:30.09 | Psi | yeah, im looking at it now |
| 13:30.18 | Psi | for some reason i thought that was missing |
| 13:30.30 | DocScrutinizer05 | http://wiki.maemo.org/N900_Hardware_Schematic#Page_16_Component_Finder_.28Top.29 |
| 13:31.55 | DocScrutinizer05 | anyway your tests suggest that 1707a PHY can detect a D+/- short correctly. That tells some story about what must be OK and working on your device |
| 13:31.58 | *** join/#maemo Wizzup (~Wizzup@2001:981:a731:1:f2ad:4eff:fe00:f3d) |
| 13:32.36 | Psi | yeah |
| 13:32.57 | DocScrutinizer05 | particularly it does suggest that none of D+ D- traces to phy is broken |
| 13:33.08 | Psi | now that i know how to find components on the board and trace the circuit i will have another play with the meter looking for faults |
| 13:33.37 | Psi | oh, there is a missing cap on the FM tx that i found loose in the phone |
| 13:33.42 | Psi | C6184 |
| 13:33.58 | Psi | its part of the sleep clock input to the FM tx chip |
| 13:34.06 | DocScrutinizer05 | ouch |
| 13:34.19 | Psi | the cap was still there, inside the metal can |
| 13:34.21 | Psi | just loose |
| 13:34.28 | DocScrutinizer05 | OUCH! |
| 13:35.22 | Psi | yeah, im beginning to wonder if one of the two broken components inside the phone may have touched something and shorted it out |
| 13:35.30 | DocScrutinizer05 | wonders how to find out which cap got loose, without opening can and while doing that, at least remove the loose cap |
| 13:36.23 | Psi | yeah, i have removed both the broken ESD chip and the borken cap |
| 13:36.25 | DocScrutinizer05 | yeah, a loose component is always a high risk to short other stuff randomly |
| 13:36.38 | Psi | cap looks ok, its still intact but esd chip i only found one half of it |
| 13:37.01 | DocScrutinizer05 | wtf? how can such a tiny chip break into parts |
| 13:37.24 | Psi | have a look where that chip is, its right at the point of the stylis |
| 13:37.41 | DocScrutinizer05 | hmm, not really |
| 13:37.52 | DocScrutinizer05 | some millimeter space between the two |
| 13:38.09 | Psi | i dunno, just seems an odd coincidence |
| 13:38.26 | Psi | i do push the stylis in with some force |
| 13:38.41 | DocScrutinizer05 | sure, when you bend the whole device a 10mm... ;-P |
| 13:38.48 | Psi | heh |
| 13:39.18 | Psi | ok, i need to sleep, its 1:40 here and i have to get up for work at 6 |
| 13:39.26 | DocScrutinizer05 | or insert something that's not exactly a correctly shaped stylus |
| 13:39.27 | Psi | thanks a lot for your help |
| 13:39.41 | DocScrutinizer05 | yw, good luck! |
| 13:39.47 | Psi | na, ive never put anything into the stylus hole thats not a stylus |
| 13:40.13 | Psi | maybe the chip came loose and got hit by the vibrator |
| 13:40.23 | DocScrutinizer05 | possible |
| 13:40.23 | Psi | that might crack it |
| 13:40.28 | DocScrutinizer05 | yup |
| 13:40.56 | Psi | ok, see ya. Thanks |
| 13:40.59 | DocScrutinizer05 | cya |
| 13:43.36 | *** join/#maemo useretail (useretail_@gateway/shell/elitebnc/x-wpixykcgxdujivbd) |
| 13:49.23 | *** join/#maemo RiD (kamisakea@2.83.56.229) |
| 13:58.10 | *** join/#maemo hxka (~hxka@128-69-211-162.broadband.corbina.ru) |
| 13:59.09 | *** join/#maemo RiD (RiD@2.83.56.229) |
| 14:34.37 | *** join/#maemo SmilyOrg (Smily@BSN-61-3-55.dial-up.dsl.siol.net) |
| 14:38.26 | *** join/#maemo erlehmann (~erlehmann@89.204.130.182) |
| 14:47.07 | *** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com) |
| 14:55.50 | *** join/#maemo shentey (~shentey@nrbg-4dbf5d70.pool.mediaWays.net) |
| 14:58.17 | *** join/#maemo MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 15:07.33 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 15:08.02 | *** join/#maemo MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 15:13.56 | *** join/#maemo javispedro (~javier@Maemo/community/contributor/javispedro) |
| 15:21.33 | *** join/#maemo MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 15:31.57 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 15:35.45 | *** join/#maemo psycho_oreos (~tuxsavvy@unaffiliated/tuxsavvy) |
| 15:51.55 | *** join/#maemo FReaper-PC (~FR@115.132.66.230) |
| 16:18.57 | *** join/#maemo kraft (kraft@gateway/shell/blinkenshell.org/x-prfbkafvvqvrgaod) |
| 16:26.26 | *** join/#maemo darkschneider (~gab@93-32-34-252.ip31.fastwebnet.it) |
| 16:33.17 | *** join/#maemo Nokiabot (~Nokiabot@182.66.39.65) |
| 16:45.44 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 16:50.23 | *** join/#maemo protem (~protem@unaffiliated/protem) |
| 17:13.06 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 17:13.31 | *** join/#maemo sq-one (~sq-one@p549A8FA8.dip0.t-ipconnect.de) |
| 17:53.17 | *** join/#maemo spoofy (~spoofy@unaffiliated/spoofy) |
| 18:32.26 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 18:41.43 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 18:54.57 | emma | hello |
| 18:55.06 | emma | May I ask what is the latest good news about Maemo? |
| 19:16.49 | *** join/#maemo ZogG_laptop (~ZogG_lapt@bzq-79-178-120-150.red.bezeqint.net) |
| 19:16.54 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 19:23.31 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:24.07 | *** join/#maemo mnzaki (~mnzaki@91-65-35-21-dynip.superkabel.de) |
| 19:37.05 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 19:48.53 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginm.net) |
| 19:56.41 | DocScrutinizer05 | maybe the upcomming coding competition? |
| 20:00.37 | DocScrutinizer05 | maybe the rumor that Neo900 UG ponders to donate (an option for) a device or alternatively a sustantial money price for a yet to get specified port of fremantle? |
| 20:01.15 | DocScrutinizer05 | suBstantial* |
| 20:01.16 | *** join/#maemo shentey (~shentey@nrbg-4dbf5d70.pool.mediaWays.net) |
| 20:01.30 | DocScrutinizer05 | and prize of course |
| 20:03.03 | honestly | I still can't parse that properly |
| 20:03.11 | honestly | who is donating what for what? |
| 20:03.20 | honestly | do you mean offering a bounty? |
| 20:06.51 | emma | why is there a bounty? |
| 20:09.27 | DocScrutinizer05 | errr, a competition is about prizes, winners and all that, no? |
| 20:10.19 | DocScrutinizer05 | honestly, is that so obscure? http://talk.maemo.org/showthread.php?t=93334 |
| 20:10.43 | honestly | oh, I see. |
| 20:45.09 | *** join/#maemo BonoNL_ (~sailfish@a83-163-206-88.adsl.xs4all.nl) |
| 20:53.14 | *** join/#maemo javispedro (~javier@Maemo/community/contributor/javispedro) |
| 21:09.44 | Gh0sty | hello I was wondering ... |
| 21:10.07 | Gh0sty | it's possible to run the n900 as mifi device (sharing 3G over wifi) |
| 21:11.05 | Gh0sty | but from what I read it's the same as most other linuxes ... it only supports WEP encryption? |
| 21:12.14 | honestly | as far as I know, yes. |
| 21:12.38 | honestly | you can also share 3G via usb. |
| 21:12.51 | Gh0sty | just for my interest but why do android phones support wpa2 accesspoint mode |
| 21:13.06 | Gh0sty | but thinks like an n900 or for example my laptop don't ? :/ |
| 21:13.20 | Gh0sty | something to do with the driver or is that even a feature that needs hardware support? |
| 21:15.30 | *** join/#maemo doc|home (~doc@69.172.145.146) |
| 21:15.30 | *** join/#maemo doc|home (~doc@gentoo/contributor/doc-007) |
| 21:16.34 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 21:20.15 | DocScrutinizer05 | who says N900 doesn't support WPA? |
| 21:20.52 | DocScrutinizer05 | not saysing that it does. Just wondering why you think it doesn't |
| 21:21.18 | honestly | there are no mobile hotspot apps offering it (: |
| 21:21.27 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 21:21.52 | DocScrutinizer05 | it supports WLA(2) for normal (infrastructure) mode device |
| 21:22.04 | DocScrutinizer05 | WPA |
| 21:23.23 | DocScrutinizer05 | it's quite possible that the chip doesn't support WPA AP mode, actaully I think the chip doesn't support genuine AP mode at all, it's an emulated AP mode. So you would have to emulate WPA as well, which aiui is what WPA-supplicant is made fore |
| 21:23.27 | DocScrutinizer05 | -e |
| 21:23.33 | *** join/#maemo _rd (~rd@p57B49FEB.dip0.t-ipconnect.de) |
| 21:25.37 | DocScrutinizer05 | iirc it emulates infrastructure AP by exploiting AdHoc mode which by design can't use WPA. At least that's my take on it |
| 21:27.35 | DocScrutinizer05 | so when the chip doesn't support WPA but WEP for AdHoc, it's what the emulated AP mode will support too, as long as you don't emulate WPA AP in software, which should be perfectly possible |
| 21:36.14 | ShadowJK | it's ad-hoc mode, not ap mode |
| 21:36.22 | ShadowJK | recent androids don't supprot ad-hoc btw |
| 21:43.40 | DocScrutinizer05 | that's what I said. AdHoc mode simmulating AP mode |
| 21:44.07 | Gh0sty | ah yes |
| 21:44.15 | Gh0sty | indeed that was one of the problems |
| 21:44.29 | Gh0sty | that it's doing ad-hoc so no android device can connect :/ |
| 21:44.30 | DocScrutinizer05 | and AdHoc only can do WEP, by principle of operation I guess |
| 21:44.37 | Gh0sty | think it's the same with my laptop |
| 21:44.50 | Gh0sty | for infrastructure mode the hardware needs to be better? :/ |
| 21:45.07 | DocScrutinizer05 | not better, just different |
| 21:45.14 | Gh0sty | well yes :p |
| 21:45.22 | DocScrutinizer05 | actually probably only the firmware needs to be different |
| 21:45.43 | DocScrutinizer05 | the firmware we got doesn't support AP |
| 21:45.59 | Gh0sty | ah the firmware is not open from that part of the phone? :/ |
| 21:46.01 | DocScrutinizer05 | but it supports injection :-) |
| 21:46.27 | DocScrutinizer05 | the firmware of the chip, not the linux system of the phone |
| 21:47.48 | DocScrutinizer05 | aiui injection is a sort of "raw" mode that allows you to send whatever you like. So it *can* do proper AP mode when you write (or find) a FOSS software that does the encoding and protocol stack |
| 21:48.09 | honestly | probably not too hard, just a lot of work. |
| 21:48.39 | DocScrutinizer05 | cave: this will keep the APE CPU busy and eat your battery like candy |
| 21:48.52 | Gh0sty | so in other words |
| 21:48.59 | honestly | om nom electrons. |
| 21:49.02 | Gh0sty | I will just buy one of those huawei toys :p |
| 21:49.33 | Gh0sty | if it was easy enough the n900 could still have a purpose but now ... :) |
| 21:49.45 | Gh0sty | not sure, still sits in the drawer :/ |
| 21:50.03 | honestly | send it to me for when mine croaks >_> |
| 21:50.26 | Gh0sty | well the led controller of mine is acting funky |
| 21:50.37 | Gh0sty | one of the reasons why i bought myself an nexus 5 |
| 21:50.46 | Gh0sty | not too happy with that one either but ... |
| 21:50.46 | DocScrutinizer05 | o.O |
| 21:50.50 | DocScrutinizer05 | funny? |
| 21:50.50 | javispedro | hm, softapd to the request? |
| 21:51.04 | javispedro | *to the rescue :) |
| 21:51.18 | DocScrutinizer05 | javispedro: \o/ |
| 21:51.24 | DocScrutinizer05 | hi!!! |
| 21:51.59 | javispedro | hi! |
| 21:52.52 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 21:59.30 | DocScrutinizer05 | javispedro: how about coding competition? |
| 21:59.56 | DocScrutinizer05 | or about joining the FPTF team? |
| 22:01.25 | DocScrutinizer05 | I heard rumors that some weirdo wants to promise a prize of 1000EUR for a fremantle based on open source only and capable to forward cmtspeech audio to an USB attached audiocard instead of modem |
| 22:01.31 | DocScrutinizer05 | ;-) |
| 22:02.13 | javispedro | ah well :) |
| 22:02.32 | javispedro | if I had the time a systemd-free distro is on the top of my list for now :) |
| 22:02.35 | DocScrutinizer05 | further conditions allegedly are: binary compatibility to maemo-extras packages, semi-decent power management |
| 22:03.58 | DocScrutinizer05 | aiui http://www.omappedia.com/wiki/Maemo_Getting_Started is already halfway tehre, maybe even further |
| 22:04.46 | DocScrutinizer05 | I think your understanding of how audio/mixer on N900 works would help a lot on achieving the cmtspeech goal |
| 22:07.21 | DocScrutinizer05 | (sidenote: it's allowed to import closed blobs from an existing fremantle installation, so the developer has such a system at hand. This wouldn't disqualify the solution) |
| 22:07.26 | *** join/#maemo remarc_ (~sequantz@194.11.24.44) |
| 22:07.54 | DocScrutinizer05 | above rule doesn't apply for kernel |
| 22:08.13 | javispedro | as of lately I have more time and I'm more on this channel, so feel free to ask |
| 22:08.28 | DocScrutinizer05 | well, obviously kernel isn't a closed blob on fremantle, so nevermind |
| 22:09.19 | DocScrutinizer05 | teams are allowed, the price will get shared on discretion of those who decide, and might even get upgraded |
| 22:09.32 | DocScrutinizer05 | prize :-S |
| 22:11.36 | DocScrutinizer05 | It occurred to me, a possible approach for audio (last resort) would be to treat the USB audio card as a SIP telephony account and just convert RTP to plain S16LE datastream to feed to the card |
| 22:12.14 | honestly | ugh, this is getting ridiculous |
| 22:12.18 | DocScrutinizer05 | but of course a genuine modem ("phone") account for the voicecalls would be preferred |
| 22:12.38 | DocScrutinizer05 | honestly: honestly? |
| 22:12.44 | honestly | honestly |
| 22:12.52 | honestly | my n900 just won't charge properly anymore |
| 22:12.52 | DocScrutinizer05 | elaborate! |
| 22:12.55 | nox- | doesnt that recorder app already record calls too? |
| 22:13.04 | DocScrutinizer05 | nox-: yep |
| 22:13.16 | DocScrutinizer05 | nox-: and javispedro understands how it does |
| 22:13.25 | nox- | ah |
| 22:13.25 | DocScrutinizer05 | I don't |
| 22:13.30 | honestly | there must be a loose contact somewhere |
| 22:13.51 | DocScrutinizer05 | honestly: check springs in battery |
| 22:14.09 | honestly | huh. |
| 22:14.13 | honestly | okay. |
| 22:14.16 | DocScrutinizer05 | you can gently bend them to "close" |
| 22:14.18 | honestly | that's a new one |
| 22:14.48 | DocScrutinizer05 | using a needle or somesuch tool |
| 22:15.03 | honestly | seems like the battery is sitting in there very solidly |
| 22:15.14 | DocScrutinizer05 | sure, it does |
| 22:15.26 | DocScrutinizer05 | not the springs in phone holding the battery |
| 22:15.39 | honestly | oh, I see |
| 22:15.44 | DocScrutinizer05 | the tiny golden critters in the battery's slots |
| 22:15.56 | honestly | right |
| 22:16.22 | DocScrutinizer05 | abusing them makes them gap open |
| 22:16.50 | DocScrutinizer05 | e.g by charging battery in external charger with thicker contact blades |
| 22:17.42 | DocScrutinizer05 | take care not to short anything when you stirr in there with a needle |
| 22:17.43 | honestly | I haven't done any abusing like that |
| 22:17.48 | honestly | yeah. |
| 22:18.14 | DocScrutinizer05 | visual control is OK. Lemme find a photo of a proper contact spring |
| 22:18.30 | honestly | oh, the phone had turned off due to low battery. |
| 22:18.39 | honestly | is it possible that it stayed in low-current emergency charging mode? |
| 22:18.42 | *** join/#maemo hubutm20 (~hubutm20@79.113.79.213) |
| 22:22.09 | *** join/#maemo shentey (~shentey@nrbg-4d071f0f.pool.mediaWays.net) |
| 22:24.04 | DocScrutinizer05 | http://maemo.cloud-7.de/share-service/20120504_002.jpg |
| 22:24.11 | DocScrutinizer05 | dang, the first one (almost) |
| 22:24.23 | DocScrutinizer05 | that took a while, bottom up |
| 22:25.06 | honestly | yeah, my battery contacts look like that. |
| 22:25.36 | honestly | let me see if I can't take a better picture :P |
| 22:27.09 | DocScrutinizer05 | o/ afk |
| 22:43.30 | *** join/#maemo shamus (~shmaus@ip-206-192-193-180.marylandheights.ip.cablemo.net) |
| 22:56.15 | *** join/#maemo janemba (~101@unaffiliated/janemba) |
| 23:41.26 | *** join/#maemo janemba (~101@unaffiliated/janemba) |
