DocScrutinizer05 changed the topic of #neo900 to: http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900 | 2013-11-04 - the day our fundraiser reached its goal | 2014-05-01 360 devices 75k€| 0712 183 ~30k | 0810 300 ~49k | 0914 346 ~56k
norly has quit [Quit: Leaving.]
norly has joined #neo900
<DocScrutinizer05> http://maemo.cloud-7.de/
<DocScrutinizer05> (CAL==mtd1)
<DocScrutinizer05> of course that's *my* MAC for BT, WLAN etc ;-)
<wpwrak> was. now it's everyone's. anonymity, at long last ! ;-)
<DocScrutinizer05> well, not that I care about a stupid MAC
<DocScrutinizer05> I don't even consider IMEI a particularly confidential info
<wpwrak> i'm sure that, according to some law enforcement official, the west just has perished :)
<DocScrutinizer05> well, sure. Now you can drive across europe in 50, meanders searching for my WLAN MAC to spot where I am :-P
<DocScrutinizer05> 50m*
<DocScrutinizer05> with my IMEI you at least could try to put that on the blacklist, but they will ask your ID number and name, address, to do so
<wpwrak> ah, we have yours, of course :)
<wpwrak> except for the ID. but hey, people forget such things :)
<DocScrutinizer05> well, good luck with finding the IMEI of *my* phone ;-)
<DocScrutinizer05> of course you can try random IMEIs created by a generator. All N900 IMEI are somewhat similar
<DocScrutinizer05> and while you're at it, go on with all Sony IMEIs, and BB
<DocScrutinizer05> and even when you succeed to get my IMEI blacklisted, I got it unlocked faster than you did lock it
<wpwrak> hmm yes, we would have to keep you from going outdoors. maybe bribe some local politician to introduce week where smoking in public places, including outdoors, is prohibited ? they should like that. show initiative. that would ground you for that week ;-)
<DocScrutinizer05> unlike you I don't need to show my ID card to my service provider to get device unlocked, since they already seen it. I only need to authenticate to them with my password, and maybe tell them my ID card number again
<Oksana> Unlock your cellular-phone IMEI by calling from landline phone? Or online, opening the relevant unlock-site through WiFi?
<DocScrutinizer05> so I don't even need to leave home
<DocScrutinizer05> Oksana: you forget I got a 60+ other cellphones here ;-P
<Oksana> Heh... :-)
<DocScrutinizer05> and of course I could also use landline and VoIP
<wpwrak> damn !
<DocScrutinizer05> and probably even FAX
<DocScrutinizer05> maybe email, duh!
<Oksana> Off-topic: How difficult is it to send a fax from a mobile phone? Photo-scan a document, then?..
<DocScrutinizer05> FAX isn't supported anymore by most of modems
<DocScrutinizer05> in former time iot been the third CSD service-ID besides voice and data
<DocScrutinizer05> it*
<wpwrak> i remember staring at it in my nokia 2110 manual, wondering "and what shall i do with you ... ?"
<DocScrutinizer05> you however might be able to convert the picture to dunnowhat format and send it via a VoIP (or other similar) provider
<DocScrutinizer05> my provider (sipgate.de) accepts pdf iirc
<DocScrutinizer05> sending fax is no problem. *receiving* fax is tricky
<Pali> have you seen parser for N810 BME CAL data?
<DocScrutinizer05> not yet. Only seen general CAL parser/"fs-driver"
<Pali> it is really loader from "bme" CAL to kernel driver which parse those data and do some magic
<DocScrutinizer05> well yeah, N810 BME been an abomination
<DocScrutinizer05> charging 100% software controlled
<Pali> that 10-bme-pmm-image script call "generic" CAL parser calvaria which extract data from "bme" CAL section
<Pali> and then those raw data send to that kernel driver in file 900-n810-battery-management.patch
<Pali> on N900 we have bme section in CAL too
<Pali> maybe structure is same?
<DocScrutinizer05> yes, prolly cruft
<Pali> and we can finally decode what is there stored?
<DocScrutinizer05> go ahead! :-D
<DocScrutinizer05> I guess it is a set of parameters to create an algorithmic curve for capacity versus voltage
<DocScrutinizer05> stskeeps told me his eyes started bleeding when he looked at the *sourcecode* of N900 bme
<DocScrutinizer05> it's probably a toxic ancient hairball of cargo cult coding mixed with "NFC, but it seems to work"
<DocScrutinizer05> it's pretty obvious that bme doesn't use bq27200 gas gauge for determining battery charge level
SylvieLorxu has quit [Quit: ZNC - http://znc.in]
<DocScrutinizer05> at least not exclusively
<DocScrutinizer05> rather bme, after "stop bme; start bme" shows massively too low charge level for a short time, then eventually adjusts its meter
<DocScrutinizer05> indistry uses funny algorithms to make battery meter show what users expect it to show
<Pali> ok, now I know what is stored in bme CAL section
<Pali> calibration values for ADC channels
<DocScrutinizer05> from iPhone I heard "damn, the battery meter shows 50% and yet I can operate the phone for several more hours" --> apple changed meter to show "full == 70% of battery capacity"
<DocScrutinizer05> Pali: alas N900 bme doesn't use many ADC at all. Maybe battery voltage from GAIA, and that's pretty much calibrated by factory and needs no further calibration
<Pali> Charger voltage, Battery voltage, Battery voltage, unknown, Charger voltage, Battery size indicator, Battery temperature, unknown
<Pali> and yes we really used some values from bme CAL for battery temperature
<DocScrutinizer05> yeah, well the NTC in battery, called "BSI"
<Pali> I remember that once I used some raw constants from bme CAL into some formula which I found in another driver, all measured values for battery temperature were correct
<DocScrutinizer05> I wonder how bme wants to calibrate that. It has no normal to calibrate it against
<Pali> it looks like some data are static
<Pali> and some can be changed
<Pali> there is Battery voltage 3 times in bme CAL
<Pali> but with different flags
<DocScrutinizer05> full, warning threshold, empty
<Pali> does not bme write to CAL?
<DocScrutinizer05> it's probably highly boring to learn what those values are meant for, if anything
<DocScrutinizer05> yes
<Pali> so some values in bme CAL are used for something...
<DocScrutinizer05> what makes you think that? ;-)
<Pali> rewriting data for battery percentage based from battery voltage?
<DocScrutinizer05> "isn't bme writing to register #46 of the 5 registers in bq24150? So there must be hidden registers in bq24150" - I don't think so
<DocScrutinizer05> bme is junk
<Pali> :D
<Pali> for Battery size indicator there is value C0 04
<Pali> 1216 mAh? :D
<Pali> (in my CAL)
<DocScrutinizer05> well, you tell me, after using your hex converter
<Pali> 0x04C0 = 1216
<DocScrutinizer05> battery is 1320
<DocScrutinizer05> iirc
<Pali> no those first batteries were smaller
<DocScrutinizer05> anyway, nobody knows what for we need BSI anyway
<Pali> and I remeber that BME show me something about 1220
<DocScrutinizer05> forget BME
<DocScrutinizer05> it's dead
<Pali> I know we do not need it
<Pali> and now I know that in bme CAL is nothing interested...
<DocScrutinizer05> :-)
<Pali> only data for battery temperature
<Pali> so only last 3 BME sections are unknown: cert-npc, cert-ccc, cert-hwc
norly has quit [Quit: Leaving.]
Pali has quit [Remote host closed the connection]
sixwheeledbeast has quit [Ping timeout: 258 seconds]
sixwheeledbeast has joined #neo900
xes has quit [Quit: Going offline...]
unclouded has quit [Ping timeout: 272 seconds]
nox- has quit [Quit: Leaving]
unclouded has joined #neo900
unclouded has quit [Ping timeout: 272 seconds]
unclouded has joined #neo900
jonwil has joined #neo900
<freemangordon> hmm, can't we parse ATAGS from the userspace?
<freemangordon> why we need that in the kernel?
che1 has joined #neo900
Kabouik_ has joined #neo900
Kabouik has quit [Ping timeout: 244 seconds]
jonwil has quit [Remote host closed the connection]
Kabouik_ has quit [Ping timeout: 264 seconds]
che1 has quit [Ping timeout: 255 seconds]
che1 has joined #neo900
sparetire_ has quit [Quit: sparetire_]
fingertips has joined #neo900
<fingertips> DocScrutinizer05: availiable resources?
<fingertips> available resources DocScrutinizer?
arcean has joined #neo900
SylvieLorxu has joined #neo900
fingertips has left #neo900 [#neo900]
che1 has quit [Ping timeout: 255 seconds]
Pali has joined #neo900
SylvieLorxu has quit [Quit: ZNC - http://znc.in]
che1 has joined #neo900
che1 has quit [Ping timeout: 256 seconds]
Nokiabot has joined #neo900
MonkeyofDoom has quit [Ping timeout: 258 seconds]
che1 has joined #neo900
Nokiabot has quit [Quit: jmIrc destroyed by the OS]
SylvieLorxu has joined #neo900
<DocScrutinizer05> ???
che1 has quit [Ping timeout: 240 seconds]
che1 has joined #neo900
sparetire_ has joined #neo900
obsed has quit [Ping timeout: 245 seconds]
jonwil has joined #neo900
freemangordon has quit [Remote host closed the connection]
freemangordon has joined #neo900
che1 has quit [Ping timeout: 272 seconds]
norly has joined #neo900
tics has joined #neo900
tics has quit [Quit: Page closed]
<DocScrutinizer05> dirt simple verification 3-component-circuit for IrDA/CIR/IR-UART
<Oksana> Good morning :-)
<DocScrutinizer05> moo
<Oksana> Mew
arcean has quit [Quit: Konversation terminated!]
Pali has quit [Remote host closed the connection]
<jake42> DocScrutinizer05: how do you like the mini oszilloscope?
<DocScrutinizer05> it's great for its price and size
<jake42> :-)
che1 has joined #neo900
RzR is now known as rZr
Kabouik has joined #neo900
MonkeyofDoom has joined #neo900
wazrus has joined #neo900