**** BEGIN LOGGING AT Thu Sep 13 10:04:13 2018
Sep 13 12:27:07 <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 
Sep 13 12:27:13 <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.
Sep 13 12:28:24 <buZz> Vajb: why not just remove battery and reboot the device?
Sep 13 12:28:48 <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
Sep 13 12:29:33 <Vajb> buZz: I've been told that hard power off is not exactly a good thing so I wanted to avoid that.
Sep 13 12:29:50 <Vajb> but in the end I had no choice
Sep 13 12:30:11 <Vajb> is this common among other devices?
Sep 13 12:30:18 <buZz> yeah its not a good thing , but 2 hrs no display is not a good thing either :P
Sep 13 12:30:34 <Vajb> I was at the gym ;)
Sep 13 12:30:35 <buZz> Vajb: we'd be unable to compare devices, my os isnt yours :)
Sep 13 12:30:45 <buZz> thats not a good thing either :P
Sep 13 12:31:14 <Vajb> matter of taste :)
Sep 13 12:31:23 <bencoh> Vajb: in such a case I'd usually try connecting to it via usb
Sep 13 12:31:27 <buZz> matter of just moving enough in real life ;)
Sep 13 12:32:44 <Vajb> does it make a difference if I reveal it is a climbing gym :p
Sep 13 12:33:00 <bencoh> nice
Sep 13 12:33:40 <buZz> Vajb: not really :P
Sep 13 12:33:48 <Vajb> bencoh: lets hope next time it happens Im at home, but now i were expecting phone call.
Sep 13 12:34:05 <buZz> compensating for passive behaviour IRL should be through active behaviour IRL , not in forced settings
Sep 13 12:34:23 <buZz> but well, i guess i'm hollistic or something
Sep 13 12:34:39 <buZz> each to its own ;)
Sep 13 12:34:43 <Vajb> actually I go here because I like it
Sep 13 12:35:25 <Vajb> hmm my sentence feels a bit retarded
Sep 13 12:36:13 <buZz> 'there' would be better in place, i think
Sep 13 12:57:58 <Vajb> yes, sounds better.
Sep 13 13:07:18 <buZz> :)
Sep 13 16:09:07 <freemangordon> Pali: https://github.com/maemo-leste/libcal/issues/1
Sep 13 16:11:17 <Pali> just one structure? remove comments and write that C strucute from scratch
Sep 13 16:13:29 <freemangordon> mhm
Sep 13 16:13:39 <freemangordon> but I want to hear from the guy as well
Sep 13 16:14:09 <freemangordon> I don;t see a problem adding him to authors unless he insist on relicensing under gpl3, which would not happen
Sep 13 16:15:40 <freemangordon> actually there are 2 structures, but that makes no difference
Sep 13 17:34:41 <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
Sep 13 17:36:21 <KotCzarny> find yourself new one?
Sep 13 17:38:05 <ontime> why? it seems all work, but not kernel-power
Sep 13 17:38:17 <KotCzarny> does modem work? (phone part)
Sep 13 17:38:51 <ontime> need to check
Sep 13 17:39:26 <ontime> phonet0 is available
Sep 13 17:39:57 <freemangordon> ontime: your CAL partition is erased
Sep 13 17:41:01 <ontime> yes, modem works
Sep 13 17:41:15 <freemangordon> unfortunately it contains device specific data which can;t be restored
Sep 13 17:41:38 <freemangordon> like wifi calibration values
Sep 13 17:41:54 <freemangordon> also, wlan/BT MAC addresses
Sep 13 17:42:07 <freemangordon> KotCzarny: iirc IMEI etc is not in CAL
Sep 13 17:42:55 <KotCzarny> hmm, might be messing up shorthands then (was it cmt?)
Sep 13 17:43:27 <freemangordon> iirc BB5 has its own persistent storage
Sep 13 17:43:33 <freemangordon> not 100% sure though
Sep 13 17:43:47 <freemangordon> yes, cmt
Sep 13 17:43:49 <KotCzarny> so apart from wifi/bt breaking, what are consequences of nuked cal data?
Sep 13 17:44:22 <freemangordon> should be that, can't recall anything else critical
Sep 13 17:44:29 <freemangordon> ah, HW revision too
Sep 13 17:45:44 <freemangordon> ontime: if you manage to get cal partition from another device, you may restore your n900 to almost 100% functional state
Sep 13 17:46:08 <freemangordon> but wifi calib and MAC addresses will be incorrect
Sep 13 17:47:00 <ontime> wifi connects to AP, but no route
Sep 13 17:47:24 <ontime> yes, I can get cal partition from another N900
Sep 13 17:47:31 <ontime> but how?
Sep 13 17:48:10 <DocScrutinizer05> >>So I did nandtest on all mtd<< OUCH!!!!
Sep 13 17:48:36 <ontime> now I know thats bad idea
Sep 13 17:48:57 <ontime> nandtest has misleading name
Sep 13 17:50:22 <DocScrutinizer05> >>iirc BB5 has its own persistent storage<< of course. A ton err many MB
Sep 13 17:51:31 <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
Sep 13 17:51:56 <freemangordon> you'll miss onenand erase counts, atc, but that should be there
Sep 13 17:52:00 <freemangordon> *etc
Sep 13 17:52:39 <freemangordon> hmm
Sep 13 17:52:46 <freemangordon> *DATA* should be there :)
Sep 13 17:53:11 <DocScrutinizer05> find a cal dump on cloud7
Sep 13 17:53:33 <freemangordon> DocScrutinizer05: is it dumped with cat?
Sep 13 17:53:59 <DocScrutinizer05> 3 methods, diff shows they are identical. flashing though doesn't work with cat IIRC
Sep 13 17:55:10 <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
Sep 13 17:55:32 <freemangordon> you should be ok then
Sep 13 17:55:41 <ontime> ok, I reflash once again, and should be fine
Sep 13 17:55:44 <DocScrutinizer05> http://maemo.cloud-7.de
Sep 13 17:55:51 <ontime> thanks
Sep 13 17:57:01 <freemangordon> ontime: you wrote the whole onenand or only cal partition?
Sep 13 17:57:17 <DocScrutinizer05> freemangordon: this is what? 3rd time somevody really bricked his device?
Sep 13 17:57:32 <ontime> each mtd separatly
Sep 13 17:57:54 <freemangordon> DocScrutinizer05: it is not really bricked
Sep 13 17:58:00 <ontime> *separately
Sep 13 17:58:06 <DocScrutinizer05> as bricked as it gets
Sep 13 17:58:38 <freemangordon> ontime: you should've written CAL partition only
Sep 13 17:58:43 <DocScrutinizer05> N900 is unbrickable
Sep 13 17:58:51 <freemangordon> :nod:
Sep 13 17:59:17 <ontime> good chunk of hw
Sep 13 18:03:10 <DocScrutinizer05> I *think* I've seen 2 nandtest bricks and one real damage by unknown reason
Sep 13 18:03:37 <DocScrutinizer05> not counting the real hw failures
**** ENDING LOGGING AT Thu Sep 13 20:58:25 2018

**** BEGIN LOGGING AT Thu Sep 13 23:44:37 2018
**** ENDING LOGGING AT Fri Sep 14 03:00:10 2018