Oksana | Is there a standard for file format of logs of instant messages? So that they can be tracked by tracker, instead of being dumped in one sqlite file. | 01:21 |
---|---|---|
DocScrutinizer05 | no | 01:48 |
DocScrutinizer05 | not afaik | 01:48 |
sicelo | what would be benefit for having the linked to tracker? i don't even see what the benefit of tracker is with everything that it already tracks, except music & images. | 07:18 |
Maxdamantus | Standard log format = text | 08:18 |
Maxdamantus | Works with a wide range of software. | 08:18 |
Maxdamantus | Resistant to corruption. | 08:18 |
sixwheeledbeast | Scout will search through messages, not sure if that is SMS or IM | 09:15 |
Vajb | my n900 just acted up interestingly. I listened to music via bluetooth headset. Paused the playback and put it on charge. Led started blinking and I thought to check if anyone tried to reach by. I slid slide open, but screen remained black. I tried the switch thing, nothing happened. I tried powerkey, nothing. Led kept blinking but otherwise device seemed dead. Then I disconnected my headset and thought to | 14:27 |
Vajb | give some time for it. One and half hour later the state was same. I switched on the headset, it connected, but I were not able to start the playback. | 14:27 |
buZz | Vajb: why not just remove battery and reboot the device? | 14:28 |
Vajb | I had no idea, but to try and remove battery. White led showed like in normal switch off. After plugging in the battery device started up normally | 14:28 |
Vajb | buZz: I've been told that hard power off is not exactly a good thing so I wanted to avoid that. | 14:29 |
Vajb | but in the end I had no choice | 14:29 |
Vajb | is this common among other devices? | 14:30 |
buZz | yeah its not a good thing , but 2 hrs no display is not a good thing either :P | 14:30 |
Vajb | I was at the gym ;) | 14:30 |
buZz | Vajb: we'd be unable to compare devices, my os isnt yours :) | 14:30 |
buZz | thats not a good thing either :P | 14:30 |
Vajb | matter of taste :) | 14:31 |
bencoh | Vajb: in such a case I'd usually try connecting to it via usb | 14:31 |
buZz | matter of just moving enough in real life ;) | 14:31 |
Vajb | does it make a difference if I reveal it is a climbing gym :p | 14:32 |
bencoh | nice | 14:33 |
buZz | Vajb: not really :P | 14:33 |
Vajb | bencoh: lets hope next time it happens Im at home, but now i were expecting phone call. | 14:33 |
buZz | compensating for passive behaviour IRL should be through active behaviour IRL , not in forced settings | 14:34 |
buZz | but well, i guess i'm hollistic or something | 14:34 |
buZz | each to its own ;) | 14:34 |
Vajb | actually I go here because I like it | 14:34 |
Vajb | hmm my sentence feels a bit retarded | 14:35 |
buZz | 'there' would be better in place, i think | 14:36 |
Vajb | yes, sounds better. | 14:57 |
buZz | :) | 15:07 |
freemangordon | Pali: https://github.com/maemo-leste/libcal/issues/1 | 18:09 |
Pali | just one structure? remove comments and write that C strucute from scratch | 18:11 |
freemangordon | mhm | 18:13 |
freemangordon | but I want to hear from the guy as well | 18:13 |
freemangordon | I don;t see a problem adding him to authors unless he insist on relicensing under gpl3, which would not happen | 18:14 |
freemangordon | actually there are 2 structures, but that makes no difference | 18:15 |
ontime | On n900 after boot dmesg shows 5 LEB bad. So I did nandtest on all mtd mindlessly. Who knows what that mean? :) Almost completly dead device, even doesn't react to pwr key to switch on. Found it first needs NOLO - success. Second, full flash - success (but phone board shows revision 0000 instead of 2101 or 2104). Now when try install kernel-power, just after launch softupd it shows: "ERROR: sysinfo: Phone info (block phone-info) read fa | 19:34 |
KotCzarny | find yourself new one? | 19:36 |
ontime | why? it seems all work, but not kernel-power | 19:38 |
KotCzarny | does modem work? (phone part) | 19:38 |
ontime | need to check | 19:38 |
ontime | phonet0 is available | 19:39 |
freemangordon | ontime: your CAL partition is erased | 19:39 |
ontime | yes, modem works | 19:41 |
freemangordon | unfortunately it contains device specific data which can;t be restored | 19:41 |
freemangordon | like wifi calibration values | 19:41 |
freemangordon | also, wlan/BT MAC addresses | 19:41 |
freemangordon | KotCzarny: iirc IMEI etc is not in CAL | 19:42 |
KotCzarny | hmm, might be messing up shorthands then (was it cmt?) | 19:42 |
freemangordon | iirc BB5 has its own persistent storage | 19:43 |
freemangordon | not 100% sure though | 19:43 |
freemangordon | yes, cmt | 19:43 |
KotCzarny | so apart from wifi/bt breaking, what are consequences of nuked cal data? | 19:43 |
freemangordon | should be that, can't recall anything else critical | 19:44 |
freemangordon | ah, HW revision too | 19:44 |
freemangordon | ontime: if you manage to get cal partition from another device, you may restore your n900 to almost 100% functional state | 19:45 |
freemangordon | but wifi calib and MAC addresses will be incorrect | 19:46 |
ontime | wifi connects to AP, but no route | 19:47 |
ontime | yes, I can get cal partition from another N900 | 19:47 |
ontime | but how? | 19:47 |
DocScrutinizer05 | >>So I did nandtest on all mtd<< OUCH!!!! | 19:48 |
ontime | now I know thats bad idea | 19:48 |
ontime | nandtest has misleading name | 19:48 |
DocScrutinizer05 | >>iirc BB5 has its own persistent storage<< of course. A ton err many MB | 19:50 |
freemangordon | ontime: it was long time ago I played with cal partition, but I have some vague memories that cat /dev/mtdXXX > cal_backup on a working device and then cat cal_backup > /dev/mtdXXX on the broken one will do the job | 19:51 |
freemangordon | you'll miss onenand erase counts, atc, but that should be there | 19:51 |
freemangordon | *etc | 19:52 |
freemangordon | hmm | 19:52 |
freemangordon | *DATA* should be there :) | 19:52 |
DocScrutinizer05 | find a cal dump on cloud7 | 19:53 |
freemangordon | DocScrutinizer05: is it dumped with cat? | 19:53 |
DocScrutinizer05 | 3 methods, diff shows they are identical. flashing though doesn't work with cat IIRC | 19:53 |
ontime | some around reflashing, I did nanddump all mtd from another working dev, and nandwrite to this poor one from rescueos, so that part is done | 19:55 |
freemangordon | you should be ok then | 19:55 |
ontime | ok, I reflash once again, and should be fine | 19:55 |
DocScrutinizer05 | http://maemo.cloud-7.de | 19:55 |
ontime | thanks | 19:55 |
freemangordon | ontime: you wrote the whole onenand or only cal partition? | 19:57 |
DocScrutinizer05 | freemangordon: this is what? 3rd time somevody really bricked his device? | 19:57 |
ontime | each mtd separatly | 19:57 |
freemangordon | DocScrutinizer05: it is not really bricked | 19:57 |
ontime | *separately | 19:58 |
DocScrutinizer05 | as bricked as it gets | 19:58 |
freemangordon | ontime: you should've written CAL partition only | 19:58 |
DocScrutinizer05 | N900 is unbrickable | 19:58 |
freemangordon | :nod: | 19:58 |
ontime | good chunk of hw | 19:59 |
DocScrutinizer05 | I *think* I've seen 2 nandtest bricks and one real damage by unknown reason | 20:03 |
DocScrutinizer05 | not counting the real hw failures | 20:03 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!