| Maxdamantus | I imagine you should be able to do SMS just using ofono and the Python scripts included with it. | 00:02 |
|---|---|---|
| Maxdamantus | (it won't be very nice interfacially though) | 00:03 |
| *** jkepler1 has joined #maemo | 00:33 | |
| *** jkepler has quit IRC | 00:35 | |
| *** jkepler1 is now known as jkepler | 00:35 | |
| *** merlin_1991 has quit IRC | 00:36 | |
| *** merlin1991 has joined #maemo | 00:36 | |
| *** Pali has quit IRC | 01:07 | |
| *** jkepler has quit IRC | 01:37 | |
| *** Kabouik_ has quit IRC | 02:16 | |
| *** xy2_ has quit IRC | 02:19 | |
| sunshavi | maxdamantus: very nice. What about phone calls?. are you talking just about cli, right? | 03:30 |
| *** FalconSpy has quit IRC | 03:32 | |
| *** Guest17768 has quit IRC | 03:54 | |
| *** stryngs has joined #maemo | 03:58 | |
| Maxdamantus | sunshavi: yes, just CLI. | 04:20 |
| brolin_empey | Vajb: You can look into bitlbee. I have not researched it for years, do not even know if it is still maintained. | 04:21 |
| Maxdamantus | sunshavi: last time I tried was before there was open cmt-speech code, but iirc I was able to make calls but not hear/say anything. | 04:21 |
| *** FalconSpy has joined #maemo | 04:23 | |
| brolin_empey | I primarily use Facebook Messenger in Pidgin on my home computer but there are some times when I have to use Facebook Messenger for the Android OS or the Facebook or Facebook Messenger Web site because what I need to do is not possible with the Pidgin (actually, libpurple) plug-in. There used to be Finch, which uses the same backend/stack as Pidgin but uses text/character mode. Presumably Finch is still maintained? | 04:26 |
| *** florian has quit IRC | 04:29 | |
| brolin_empey | I wonder if there is some model of smartphone running the Android OS with an integrated hardware keyboard of which I am unaware because it is marketed to business instead of consumers. I noticed that, at least in my area, the courier companies, at least FedEx and the UPS, still use a handheld computer with both a touch screen and an integrated hardware keyboard for text input instead of playing the frustrating game of trying to use a touch screen to edit | 04:39 |
| brolin_empey | text. The integrated hardware keyboard is one of the best hardware features of the Nokia N900 in my opinion even though I prefer the integrated hardware keyboard of the Nokia C6-00. | 04:39 |
| *** err0r3o3 has quit IRC | 06:22 | |
| *** err0r3o3 has joined #maemo | 06:22 | |
| *** err0r3o3 has quit IRC | 06:27 | |
| *** err0r3o3 has joined #maemo | 06:28 | |
| sunshavi | maxdamantus: mmmm. nice. that's very near to what i have know, making phone calls from cli and also sending sms messages from cli. But I need to hear what the person in the other side of the phone is saying :) | 06:34 |
| sunshavi | brolin_empey: I used bitlbee until 4 year ago and It was working nicely. Then I moved to jabber (just for not having another process running) | 06:35 |
| brolin_empey | sunshavi: ACK, am busy. | 06:39 |
| *** err0r3o3_ has joined #maemo | 08:07 | |
| *** err0r3o3 has quit IRC | 08:10 | |
| Vajb | brolin_empey: i saw that there was bitlbee version as well, but i doubt it wont work on n900. | 08:11 |
| *** drcode has quit IRC | 08:39 | |
| *** drcode has joined #maemo | 08:41 | |
| brolin_empey | Vajb: s/wont/will/ ? | 09:02 |
| Vajb | no idea to be honest | 09:15 |
| Vajb | just first thought... | 09:15 |
| brolin_empey | Vajb: Doubting that it will not work means that you expect it to work. Read your message more carefully. | 09:24 |
| Vajb | i stand corrected and to be honest, i had first written will, but corrected it to wont. | 09:27 |
| *** esaym153 has quit IRC | 09:28 | |
| *** esaym153 has joined #maemo | 09:28 | |
| *** esaym153 has quit IRC | 09:29 | |
| *** esaym153 has joined #maemo | 09:32 | |
| *** Pali has joined #maemo | 09:37 | |
| sicelo | Vajb: brolin_empey is right :-) | 10:07 |
| *** err0r3o3_ has quit IRC | 10:42 | |
| *** err0r3o3_ has joined #maemo | 10:42 | |
| *** err0r3o3_ has quit IRC | 10:47 | |
| *** err0r3o3_ has joined #maemo | 10:48 | |
| *** jkepler has joined #maemo | 10:57 | |
| *** xy2_ has joined #maemo | 11:23 | |
| Vajb | sicelo: im not native writer. My excuse ;) | 11:36 |
| *** xorly has joined #maemo | 11:56 | |
| *** florian has joined #maemo | 12:06 | |
| *** jonwil has joined #maemo | 12:20 | |
| *** florian has quit IRC | 12:22 | |
| jonwil | hi | 12:28 |
| *** jkepler has quit IRC | 12:29 | |
| Wizzup | freemangordon: can you summarise what things I can do for the .deb packages while the build infra is being worked on. I wanted the build infra in place because I figured that would provide a more organised grounds than just fetching and locally building+packaging the maemo pkgs | 12:30 |
| Wizzup | but I'm also happy to work on that latter part, it's just hard(er) for me to keep track of what to do, and what has been done, by who, etc | 12:30 |
| *** jkepler has joined #maemo | 12:33 | |
| *** xy2_ has quit IRC | 12:40 | |
| *** florian has joined #maemo | 12:40 | |
| jonwil | fremangordon, is it true you have been working on RE-ing hildon-plugins-notify-sv? If so, great :) | 12:41 |
| jonwil | I also see what looks like bits of a libplayback clone out there, also great :) | 12:41 |
| *** xorly has quit IRC | 12:41 | |
| *** xorly has joined #maemo | 12:55 | |
| *** florian has quit IRC | 13:04 | |
| *** florian has joined #maemo | 13:07 | |
| *** xorly has quit IRC | 13:12 | |
| NotKit | Wizzup, any luck with Droid 4, btw? | 13:12 |
| Wizzup | if you're asking about mainline, didn't have time for it yet. managed to flash the bootloader and everything on it though | 13:12 |
| NotKit | I couldn't get the display, it seems to require patches which don't clearly apply to 4.12 | 13:15 |
| Wizzup | yes, I know hdmi works, but not sure about internal display | 13:17 |
| *** TheKit has joined #maemo | 13:17 | |
| *** xy2_ has joined #maemo | 13:18 | |
| *** NotKit has quit IRC | 13:21 | |
| *** florian has quit IRC | 13:25 | |
| *** xorly has joined #maemo | 13:38 | |
| *** Kabouik_ has joined #maemo | 14:12 | |
| *** Kabouik has joined #maemo | 14:22 | |
| *** Kabouik_ has quit IRC | 14:23 | |
| *** e3x3 has joined #maemo | 14:38 | |
| *** xorly has quit IRC | 14:40 | |
| *** e3x3 has quit IRC | 15:10 | |
| *** jkepler has quit IRC | 15:42 | |
| *** jkepler has joined #maemo | 15:43 | |
| *** jkepler has quit IRC | 15:47 | |
| *** jkepler has joined #maemo | 16:06 | |
| *** drcode has quit IRC | 17:09 | |
| *** drcode has joined #maemo | 17:19 | |
| *** geaaru has joined #maemo | 17:47 | |
| *** drcode has quit IRC | 18:00 | |
| *** jonwil has quit IRC | 18:28 | |
| *** xy2_ has quit IRC | 18:34 | |
| *** xy2_ has joined #maemo | 18:39 | |
| *** xy2_ has quit IRC | 18:44 | |
| *** xy2_ has joined #maemo | 18:44 | |
| *** florian has joined #maemo | 18:45 | |
| *** MetalGearSolid has joined #maemo | 18:52 | |
| *** florian has quit IRC | 18:53 | |
| rysiek|pl | hi all | 19:05 |
| rysiek|pl | so I was trying to set up my n900 (running CSSU) as a bluetooth speaker | 19:05 |
| rysiek|pl | and might have borked my pulseaudio settings | 19:05 |
| rysiek|pl | of course I'm an idiot and did not back them up before meddling with them | 19:06 |
| rysiek|pl | trying to reinstall pulseaudio to get the default settings, but... | 19:06 |
| rysiek|pl | Reinstallation of pulseaudio is not possible, it cannot be downloaded. | 19:06 |
| rysiek|pl | I am sure this package is available *somewhere* | 19:07 |
| rysiek|pl | anybod any hints where? | 19:07 |
| enyc | rysiek|pl: hrrm not sure ;p outdated repository maybe? | 19:29 |
| rysiek|pl | perhaps | 19:29 |
| rysiek|pl | well, solved it in a different way now | 19:30 |
| enyc | rysiek|pl: you might do well just ot get another user to read/copy their settings file | 19:30 |
| rysiek|pl | yeah | 19:30 |
| rysiek|pl | found an old settings.pa.dpgk-old file somewhere | 19:30 |
| rysiek|pl | seems to work | 19:30 |
| enyc | now istall robbiethe1st backup and do backup ofd everything to sd-card... | 19:30 |
| rysiek|pl | haha good idea | 19:30 |
| *** xorly has joined #maemo | 19:53 | |
| *** geaaru has quit IRC | 20:01 | |
| *** xorly has quit IRC | 20:26 | |
| *** MetalGearSolid has quit IRC | 20:34 | |
| *** rhn_mk1 has joined #maemo | 20:47 | |
| rhn_mk1 | hey! a question to N900 gurus: I'm afraid I bricked my phone, is it possible to dump the flash contents? | 20:48 |
| *** TheKit has quit IRC | 21:19 | |
| *** ecloud has quit IRC | 21:19 | |
| *** ecloud has joined #maemo | 21:27 | |
| *** xy2_ has quit IRC | 21:32 | |
| sixwheeledbeast | define bricked? | 21:33 |
| *** NeKit has joined #maemo | 21:33 | |
| NIN101 | rhn_mk1: yeah with rescueOS | 21:34 |
| rhn_mk1 | bricked - doesn't react to power button or plugged cable | 21:34 |
| rhn_mk1 | if it doesn't get fixed by some drying, did anyone try to connect directly to the flash chip? | 21:36 |
| sicelo | drying? you mean it was bricked by moisture? | 21:37 |
| rhn_mk1 | sicelo: I tried washing it - when I powered it on after drying, the screen went weird after booting | 21:38 |
| rhn_mk1 | it did work for a few minutes at least | 21:39 |
| *** xy2_ has joined #maemo | 21:40 | |
| *** xorly has joined #maemo | 21:55 | |
| enyc | rhn_mk1: hrrm may be difficult ;p | 22:07 |
| enyc | rhn_mk1: also, using an external battery charger can be helpful | 22:07 |
| enyc | rhn_mk1: even on working n900 it CAN do silly things with flat battery states hard to get out of | 22:07 |
| rhn_mk1 | enyc: as opposed to PC USB or battery? | 22:07 |
| rhn_mk1 | the battery is good :/ I have a replacement n900 ready | 22:07 |
| * rhn_mk1 prays it works tomorrow so that I can copy the data out | 22:07 | |
| enyc | rhn_mk1: dont panic =) | 22:08 |
| rhn_mk1 | enyc: butbut... how can I survive without my calendar :P | 22:09 |
| *** jkepler has quit IRC | 22:13 | |
| *** jkepler has joined #maemo | 22:19 | |
| *** pagurus` has joined #maemo | 22:55 | |
| *** pagurus has quit IRC | 22:56 | |
| DocScrutinizer05 | rhn_mk1: drying device needs dissemblance and TWO weeks on 60°C warm heating or other heat source. Or alternatively no dissemblance and 3 months of drying, ideally in an environment with <10% relative humidity (air). BEWARE! operating any device (inserting battery is already "operating it") _before_ it been _completely_ dried will most likely ruin the device physically within 5 to 30 minutes from electrolytic corrosion | 23:05 |
| rhn_mk1 | DocScrutinizer05: thanks for the info, it will come in handy next time... | 23:06 |
| DocScrutinizer05 | and totally absolutely completely forget about RICE | 23:06 |
| DocScrutinizer05 | it does NUTTIN to dry your device | 23:06 |
| NeKit | any better if distilled water is used? | 23:07 |
| DocScrutinizer05 | ideally you disassemble and rinse with 98% ethanol or isopropanol. These alcohols are hygroscopic and non-conducting, thus neutralizing any water hiding under chips and wherenot | 23:08 |
| rhn_mk1 | DocScrutinizer05: where is it possible to get those in Germany? | 23:09 |
| DocScrutinizer05 | but the REALLY IMPORTANT thing is: TAKE OUT BATTERY and don't insert it again before device is absoltely dry | 23:09 |
| DocScrutinizer05 | hm? | 23:09 |
| rhn_mk1 | 98% isopropanol or ethanol | 23:09 |
| DocScrutinizer05 | alcohol? use Spiritus | 23:09 |
| rhn_mk1 | I washed with 70% solution | 23:09 |
| DocScrutinizer05 | or better: your Apotheke | 23:09 |
| rhn_mk1 | yeah, they gave me 70% | 23:10 |
| DocScrutinizer05 | 70% already ahs 30% water: bad! | 23:10 |
| rhn_mk1 | Spiritus get some additions to make it poisonous, isn't that also bad? | 23:10 |
| DocScrutinizer05 | well, should be a very minor problem | 23:11 |
| rhn_mk1 | DocScrutinizer05: do you think it's worth to try spiritus to displace any remaining water? | 23:11 |
| DocScrutinizer05 | those Denaturierung substances are very toxic or bitter and only <1% of Spiritus | 23:11 |
| DocScrutinizer05 | yes, absolutely | 23:12 |
| rhn_mk1 | I saw concerns of spiritus leaving residue | 23:12 |
| DocScrutinizer05 | for sure it's preferable to use clean 99% Ethanol from pharmacy | 23:12 |
| DocScrutinizer05 | or 98% or whatever they offer | 23:13 |
| rhn_mk1 | DocScrutinizer05: thanks, that gives me something to start round 3 | 23:13 |
| DocScrutinizer05 | :-) YW | 23:13 |
| DocScrutinizer05 | I love helping to rescue hardware :-) | 23:13 |
| DocScrutinizer05 | another more industrial method: use aqua_dest to rinse thoroughly, then vacuum dry for an hour or so | 23:15 |
| DocScrutinizer05 | real vaccum, not a vacuum cleaner | 23:16 |
| DocScrutinizer05 | slightly elevanted temperature will help a lot | 23:16 |
| DocScrutinizer05 | as for your original question: probably almost impossible to unsolder the eMMC chip without risking to lose the bits inside | 23:17 |
| rhn_mk1 | DocScrutinizer05: I'm afraid I don't have that kind of equipment :) | 23:18 |
| rhn_mk1 | *some* bits or *all* bits? | 23:18 |
| DocScrutinizer05 | sure, didn't assume you had :-D | 23:18 |
| DocScrutinizer05 | some | 23:18 |
| rhn_mk1 | good enough, I don't need perfect copy of my calendar | 23:18 |
| DocScrutinizer05 | it's risky anyway and outcome unclear | 23:18 |
| rhn_mk1 | true, I hoped it would be easier | 23:19 |
| rhn_mk1 | anyway, how long to dry after rinsing in alcohol? | 23:19 |
| DocScrutinizer05 | if you really want to do this, use preheating to 180°C then a hot air gn with 260°C to do the actual unsoldering | 23:19 |
| DocScrutinizer05 | one day should suffice, when placed at warm location | 23:20 |
| DocScrutinizer05 | alcohol is also way less critical even when remnants stay around under chips etc | 23:20 |
| DocScrutinizer05 | it won't instantly turn your copper traces into copper-oxide when voltage applied | 23:21 |
| *** florian has joined #maemo | 23:21 | |
| *** florian has joined #maemo | 23:21 | |
| rhn_mk1 | thanks | 23:21 |
| DocScrutinizer05 | when heating device, you may want to remove all plastic parts beforehand | 23:21 |
| DocScrutinizer05 | heating >120° that is | 23:22 |
| rhn_mk1 | I'll probably be back on IRC if I decide to go this route | 23:22 |
| DocScrutinizer05 | >80° is already critical for the plastic | 23:22 |
| DocScrutinizer05 | please watch out for main camera, it's not made to cope with any liquids | 23:23 |
| rhn_mk1 | taken out out of abundance of caution | 23:23 |
| rhn_mk1 | I can't believe I got on this boat without backing up | 23:23 |
| DocScrutinizer05 | hah, that's probably the sentence you only bet on *when* it gets spoken, not if | 23:24 |
| * DocScrutinizer05 needs to check his automatic backup stuff again - didn't for maybe half a year now | 23:25 | |
| rhn_mk1 | it's funnier if you know that I considered backups just before taking out the first screw | 23:25 |
| DocScrutinizer05 | the correct forensic way to recover content from eMMC while accepting device destruction would be to unsolder the SoC and contact the memory bus on the SoC pads (as long as the traces from SoC to eMMC are still OK) | 23:32 |
| rhn_mk1 | DocScrutinizer05: in order to get multiple tries at the pads? | 23:33 |
| DocScrutinizer05 | or you cut the PCB to get the eMMC chip incl PCB, the carefully file away the PCB until you reach the eMMC balls | 23:34 |
| DocScrutinizer05 | or - with precision tooling - you could even drill holes through the PCB until you just touch the eMMC solder balls | 23:35 |
| DocScrutinizer05 | rhn_mk1: in order to not apply any heat to the eMMC and instead unsolder the SoC and contact the PCB pads on SoC side | 23:35 |
| rhn_mk1 | that's a lot of work | 23:37 |
| DocScrutinizer05 | sure, I'm just sttaing what's the "correct" methods | 23:38 |
| rhn_mk1 | always interested in forensic methods, even if they may be overkill for me :) | 23:38 |
| DocScrutinizer05 | you also could check if the eMMC has JTAG pins, which you could use to read out content via JTAG boundary scan | 23:38 |
| DocScrutinizer05 | but to start with, you need supply voltage on eMMC | 23:39 |
| DocScrutinizer05 | on a defect device, that's not a given | 23:40 |
| rhn_mk1 | what's the problem with providing it externally? | 23:40 |
| DocScrutinizer05 | the power supply chain is highly sophisticated (TPS65950 GAIA companion chip) and needs to get controlled/configurated by a working CPU | 23:41 |
| *** florian_kc has quit IRC | 23:41 | |
| DocScrutinizer05 | you could probbaly supply external voltage, given you have access to the signal path for VCC and you accept any adverse effects to the regulator in TPS65950 | 23:42 |
| rhn_mk1 | I see, you mean it's necessary to start GAIA properly if VCC is not accessible | 23:42 |
| DocScrutinizer05 | well, wait. I *guess* the regulator for eMMC supply must come up without CPU intervention, so CPU could potentially boot from eMMC | 23:43 |
| DocScrutinizer05 | yes | 23:43 |
| DocScrutinizer05 | though, see above | 23:43 |
| DocScrutinizer05 | odds are GAIA will provide eMMC VCC as soon as you power up the device | 23:44 |
| rhn_mk1 | is VCC for MMC separate from CPU? | 23:45 |
| DocScrutinizer05 | sure | 23:46 |
| rhn_mk1 | oh, that's surprising | 23:46 |
| DocScrutinizer05 | not really, considering that CPU needs at least 3 voltages | 23:49 |
| DocScrutinizer05 | it will share V18_IO with eMMC I guess, but eMMC will probably need more than only V18_IO | 23:51 |
| rhn_mk1 | surprising for a HW newbie that is | 23:51 |
| DocScrutinizer05 | :-) | 23:51 |
| rhn_mk1 | DocScrutinizer05: thanks for all the help and explanations | 23:52 |
| rhn_mk1 | I'll report tomorrow at noon - not enough time to wait the full day :( | 23:52 |
| rhn_mk1 | wish me luck! good night | 23:53 |
| DocScrutinizer05 | o/ | 23:53 |
| *** rhn_mk1 has quit IRC | 23:58 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!