**** BEGIN LOGGING AT Sun Jul 27 03:00:00 2014
Jul 27 03:58:49 <jon_y> I got some 2450 mAh batteries, I remember the N900 needs some hacks in order to properly use the capacity
Jul 27 03:58:58 <jon_y> anybody remember it?
Jul 27 08:59:09 <DocScrutinizer05> jon_y: never heard of hacks needed
Jul 27 08:59:51 <rZr> hi DocScrutinizer05 
Jul 27 09:00:48 <DocScrutinizer05> you will need several learning cycles for bq27200 to calibrate it to the new battery capacity. But then bq27200 is mostly irrelevant and orphaned
Jul 27 09:00:55 <DocScrutinizer05> hi RzR
Jul 27 09:10:47 <jonwil> hi
Jul 27 09:12:29 <DocScrutinizer05> hi jonwil
Jul 27 09:12:39 <APic> goldkatze: *plush*
Jul 27 10:23:12 <kerio> DocScrutinizer05: it's not orphaned if you use pali's stuff
Jul 27 10:50:46 <DocScrutinizer05> hm?
Jul 27 10:51:04 <DocScrutinizer05> sorry, my context stack got cleared since whatever you refer to
Jul 27 10:51:28 <DocScrutinizer05> aah
Jul 27 10:51:58 <DocScrutinizer05> yeah, pali's "bme" is using bq27200
Jul 27 10:53:42 <DocScrutinizer05> alas it seems it's sometmes relying on bq27200 a tad too much
Jul 27 11:43:07 <goldkatze> APic: :-)
Jul 27 12:19:34 <kerio> DocScrutinizer05: untrue :v
Jul 27 12:19:47 <kerio> hell, it relies on it too little
Jul 27 12:20:10 <kerio> it "prefers" the bogus data from rx51-battery if it's available
Jul 27 12:25:00 <DocScrutinizer05> maybe. I haven't had a too close look into all that
Jul 27 12:27:53 <DocScrutinizer05> let's agree on "it doesn't care too much about status of data being bogus, irrespective of the data source"?
Jul 27 12:31:36 <DocScrutinizer05> I seem to recall I suggested an embedded aka in-band flag for tagging probably bogus data, by e.g. setting least significant digit of capacity-now to an impair value (aka "set LSB to 1")
Jul 27 12:32:06 <DocScrutinizer05> and vice versa set LSB to 0 as long as data source is considered accurate
Jul 27 12:33:53 <DocScrutinizer05> iirc the reporting unit is µAh, so you could actually encode a 999 different error codes into least significant three decimals
Jul 27 12:35:11 <DocScrutinizer05> an "error" of 0.999mAh introduced by such sheme for sure is negligible
Jul 27 12:35:45 <DocScrutinizer05> scheme*
Jul 27 12:37:04 <bencoh> mAh ?
Jul 27 12:37:15 <DocScrutinizer05> ?
Jul 27 12:37:21 <bencoh> hm nevermind, misread something
Jul 27 12:41:54 <DocScrutinizer05> a "educated" battery applet or whatever could use such in-band flag to adapt the capacity display accordingly - e.g. change color from green to yellow or orange when data source got reported as unreliable/bogus/inaccurate aka least significant bit = 1
Jul 27 12:42:35 <DocScrutinizer05> while an "ignorant" stock battery applet will happily display the value no matter if LSB=1 or 0
Jul 27 12:43:59 <DocScrutinizer05> with a tad of luck it shows the complete numeric value to user who then can get educated and see that this value is uneven
Jul 27 12:46:07 <DocScrutinizer05> while such approach isn't exactly nice and clean, it has a big advantage of being 100% backward compatible
Jul 27 12:46:41 <DocScrutinizer05> and doesn't introduce any nasty API changes
Jul 27 14:29:53 <jon_y> DocScrutinizer05: can the stock n900 battery manager work with the 2450mAh batteries?
Jul 27 14:31:25 <kerio> "work with"
Jul 27 14:31:46 <kerio> it's not like the standard fuel gauge is better than an educated guess
Jul 27 14:37:04 <jon_y> kerio: I mean I can at least tell when it needs charging
Jul 27 14:37:11 <jon_y> or when it is full
Jul 27 14:37:15 <kerio> i guess so, yeah
Jul 27 14:37:23 <kerio> it should detect when it's full
Jul 27 14:37:42 <kerio> it will probably show it's a lot emptier than it actually is, however
Jul 27 14:38:23 <jon_y> hmm ok, will it kill the battery when charged way too often?
Jul 27 14:42:25 <kerio> it shouldn't
Jul 27 14:42:31 <kerio> but, you know
Jul 27 14:42:39 <kerio> you lose the benefits of the bigger battery
Jul 27 14:45:21 <DocScrutinizer05> basicaly no *real* problems with bigger battery
Jul 27 14:46:24 <DocScrutinizer05> your battery remaining capacity indicator might be terribly off, but that doesn't have any impact on neither charging nor discharging to empty
Jul 27 14:46:47 <DocScrutinizer05> worst case you get recurring "battery empty" warnings for hours
Jul 27 14:47:10 <DocScrutinizer05> which can annoy a lot but usually doesn't really break anything
Jul 27 14:47:12 <bencoh> sounds terrible :D
Jul 27 14:49:55 <DocScrutinizer05> both charging termination as well as system shutdown on battery empty are based on monitoring the voltage of the battery, and that will work regardless of the battery capacity that any chip estimates
Jul 27 14:51:41 <DocScrutinizer05> (charging termination actually gets detected from charging current the battery takes. When charging current drops under a certain threshold, the bq24150 charger chip detects that and changes state and operation mode to "battery full"))
Jul 27 14:51:59 <jon_y> well, I like to have some emergency backup :)
Jul 27 14:52:10 <DocScrutinizer05> hmm?
Jul 27 14:52:11 <jon_y> so empty battery doesn't actually mean empty
Jul 27 14:53:13 <jon_y> I guess charge time would also take longer
Jul 27 14:53:26 <DocScrutinizer05> yes, of course
Jul 27 14:53:34 <kerio> jon_y: just calibrate bq27k
Jul 27 14:53:43 <kerio> and install the bme replacement
Jul 27 14:54:03 <DocScrutinizer05> jon_y: or don't
Jul 27 14:54:32 <kerio> do eeet
Jul 27 14:54:55 <jon_y> does bq27k calibration affect software or hardware?
Jul 27 14:55:03 <kerio> yes
Jul 27 14:55:09 <jon_y> both?
Jul 27 14:55:39 <kerio> neither, really
Jul 27 14:55:49 <kerio> it can affect optional software
Jul 27 14:56:02 <jon_y> just wondering if the calibration is permanent
Jul 27 14:56:53 <kerio> nope
Jul 27 14:56:54 <DocScrutinizer05> bq27200 just monitors how much capacity the cell delivers, and it may store the amount of capacity delivered by battery when battery discharge voltage gets reached 
Jul 27 14:57:06 <kerio> hardware-mandated deprecation
Jul 27 14:57:17 <kerio> you're supposed to calibrate it ~regularly
Jul 27 14:57:25 <jon_y> oh ok
Jul 27 14:57:42 <jon_y> is that the script you run from a special boot up mode?
Jul 27 14:57:54 <DocScrutinizer05> there's no such thing like calibration, it just adapts its idea of how much capacity the battery might have
Jul 27 14:57:55 <jon_y> or am I confused with something else
Jul 27 14:58:05 <kerio> no no
Jul 27 14:58:40 <kerio> calibration is just charging until full, then discharging until empty
Jul 27 14:58:54 <DocScrutinizer05> no
Jul 27 14:59:21 <kerio> D:
Jul 27 14:59:31 <kerio> wat
Jul 27 14:59:50 <DocScrutinizer05> "calibration" just stores the measured capacity after a continuous discharge of a fully charged battery
Jul 27 15:00:14 <jon_y> so, can I do this while keeping the phone online?
Jul 27 15:00:20 <DocScrutinizer05> yes
Jul 27 15:00:37 <jon_y> oh ok, can't know when urgent calls come in
Jul 27 15:01:00 <jon_y> where's the calibration script?
Jul 27 15:01:09 <DocScrutinizer05> it basically happens automatically, though often bme shuts down the device before battery got discharged far enough for bq27200 chip to detect full discharge
Jul 27 15:01:48 <jon_y> how far off does the bq27200's idea of a full discharge go?
Jul 27 15:01:58 <jon_y> 2000mAh?
Jul 27 15:02:11 <DocScrutinizer05> my script disables bme and waits for bq27200 to "learn", then re-enables bme so your phone's battery gets charged again
Jul 27 15:02:13 <jon_y> iirc the stock batteris are ~1300mAh
Jul 27 15:02:17 <kerio> EDV1 is assumed to be 6% of the full charge
Jul 27 15:03:31 <DocScrutinizer05> but you don't really need such script to make bq27200 learn. Eventually it will learn while you pretty normally use up your battery until phone shuts down
Jul 27 15:03:58 <jon_y> oh, so I do have to wait for it to power off from low battery?
Jul 27 15:04:21 <kerio> not necessarily
Jul 27 15:04:29 <kerio> but it's the simplest way
Jul 27 15:04:48 <DocScrutinizer05> err, yes, when you don't use my script, that is the best and probably only way to make bq27200 learn the battery capacity eventually
Jul 27 15:05:58 <jon_y> ok, where is the link to your script?
Jul 27 15:06:02 * DocScrutinizer05 idly wonders if there's maybe a trick to teach bq27200 about assumed capacity, via commands from software side
Jul 27 15:06:28 <jon_y> ~bme
Jul 27 15:06:29 <infobot> somebody said bme was http://wiki.maemo.org/N900_Software_BME
Jul 27 15:06:54 <DocScrutinizer05> http://maemo.cloud-7.de/maemo5/patches_n_tools/calibrate-bq27k.sh
Jul 27 15:07:31 <DocScrutinizer05> will need a few other packages 
Jul 27 15:07:41 <DocScrutinizer05> particularly
Jul 27 15:07:48 <DocScrutinizer05> ~bq27k-detail
Jul 27 15:07:48 <infobot> somebody said bq27k-detail was http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2
Jul 27 15:08:03 <DocScrutinizer05> and thatz one needs i2ctools
Jul 27 15:08:23 <jon_y> ok, thanks
Jul 27 15:08:24 <DocScrutinizer05> and iirc they all need bash
Jul 27 15:09:03 <jon_y> are the 2 scripts similar?
Jul 27 15:09:19 <DocScrutinizer05> oh wait, prolly it needs http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27200.sh
Jul 27 15:09:42 <DocScrutinizer05> which shouldn't need bash
Jul 27 15:10:54 <jon_y> how do I use bq27200.sh?
Jul 27 15:11:01 <jon_y> let it run in the background?
Jul 27 15:11:45 <DocScrutinizer05> you don't need to "use it", the http://maemo.cloud-7.de/maemo5/patches_n_tools/calibrate-bq27k.sh does
Jul 27 15:12:17 <DocScrutinizer05> you can use it to read out the data from bq27200 chip in shell
Jul 27 15:12:27 <DocScrutinizer05> just invoke it
Jul 27 15:12:47 <jon_y> fastcharger as in wallwart?
Jul 27 15:12:58 <DocScrutinizer05> when you give a numeric parameter then it will run in a loop with those seconds of delay
Jul 27 15:13:09 <DocScrutinizer05> yes
Jul 27 15:13:21 <jon_y> ok
Jul 27 15:14:20 <jon_y> right now, my stock battery lasts ~6 days if I squeeze it
Jul 27 15:14:33 <DocScrutinizer05> that's pretty decent
Jul 27 15:14:56 <jon_y> probably 1.5 weeks with the new battery after calibration
Jul 27 15:15:14 <DocScrutinizer05> calibration doesn't change how long the battery lasts
Jul 27 15:15:33 <jon_y> well, at least it won't be mistakenly shutdown :)
Jul 27 15:16:13 <jon_y> I do put the phone into offline mode during the night
Jul 27 15:16:57 <dos1> jon_y: it's never "mistakenly shutdown"
Jul 27 15:17:22 <jon_y> < DocScrutinizer05> it basically happens automatically, though often bme shuts down the device before battery got discharged far enough for bq27200 chip to detect full discharge
Jul 27 15:17:29 <jon_y> isn't that what doc warned?
Jul 27 15:17:32 <dos1> it's "mistakenly displaying 0% and low battery signs hours before shutdown"
Jul 27 15:18:46 <dos1> jon_y: that warning only holds during the calibration itself
Jul 27 15:19:21 <jon_y> hmm ok, so basically, nothing to worry about once the chip is calibrated
Jul 27 15:19:26 <DocScrutinizer05> jon_y: nope. The bq27200 needs a - say - 60 seconds of battery voltage below 3450mV to learn the new capacity of battery. However the battery must not drop to 3400mV during that time, or BME will shut down hard the complete device
Jul 27 15:20:11 <jon_y> that's a tiny margin
Jul 27 15:20:16 <DocScrutinizer05> so when you discharge "too fast" then the device may shutdown before the bq27200 has completed the learning cycle
Jul 27 15:20:31 <jon_y> yes, that explains
Jul 27 15:20:40 <dos1> jon_y: calibration will only bring you more accurate percentage values - it won't change how long the battery lasts or when the device shutdowns
Jul 27 15:20:57 <DocScrutinizer05> the margin resp voltages are random ballpark numbers to explain what happens. They are defferent in reality
Jul 27 15:21:11 <jon_y> dos1: I know, I was under the impression that the chip misdetects the levels if not calibrated
Jul 27 15:21:25 <jon_y> and thusly shut it down before it has discharged fully
Jul 27 15:21:51 <DocScrutinizer05> nope, the shutdown done by BME is not even related to bq27200 afaik
Jul 27 15:21:52 <dos1> it does, but the shutdown is voltage based, so it's not related
Jul 27 15:23:12 <jon_y> ok, bme is responsible to safe shutdown if voltages are too low
Jul 27 15:23:30 <jon_y> but bq27200 is responsible for showing battery levels in the UI
Jul 27 15:23:35 <jon_y> did I get that right?
Jul 27 15:24:43 <DocScrutinizer05> yes
Jul 27 15:24:51 <DocScrutinizer05> basically correct
Jul 27 15:25:07 <jon_y> ok, thanks for the explanation
Jul 27 15:25:24 <DocScrutinizer05> for stock maemo. Pali's BME replacement may behave differently
Jul 27 15:26:15 <jon_y> uname says I'm on power52, not sure if that matters
Jul 27 15:26:27 <jon_y> haven't upgraded in awhile
Jul 27 15:26:28 <DocScrutinizer05> (it's not exactly bme itself which shuts down, but some chain starting at bme and ending in some osso or hildon stuff, I guess)
Jul 27 15:26:39 <DocScrutinizer05> doesn't matter
Jul 27 15:27:27 <jon_y> ok
Jul 27 15:27:58 <jon_y> hopefully my n900 can last until the end of the decade
Jul 27 15:30:13 <DocScrutinizer05> ~usbfix
Jul 27 15:30:14 <infobot> usbfix is, like, http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or http://www.youtube.com/watch?list=PL2862BF3631A5C1AA&feature=player_detailpage&v=fYz5nIHH0iY#t=1861, you will basically need two irons: a small good one and a 60+ Watt
Jul 27 15:30:22 <DocScrutinizer05> strongly recommended
Jul 27 15:31:05 <jon_y> yeah, I heard of that, but opening up my phone is kind of risky
Jul 27 15:31:27 <jon_y> the damned impossible to reconnect ribbon cables speak volumes
Jul 27 15:32:07 <DocScrutinizer05> yeah, connecting felx to that friggin 64pin B2B connector can be tricky
Jul 27 15:32:13 <DocScrutinizer05> flex*
Jul 27 15:32:16 <jon_y> also, I'm too far from the UK :(
Jul 27 15:34:35 <jon_y> I wonder if the USB receptacle walls actually do anything
Jul 27 15:35:15 <jon_y> if not, we could just make a smaller USB connector that just fit over the pins inside
Jul 27 15:35:20 <DocScrutinizer05> http://maemo.cloud-7.de/share-service/20140721_002.mp4 should help a lot for not damaginbg the USB
Jul 27 15:36:08 <kerio> jon_y: haters gonna hate
Jul 27 15:36:13 <kerio> install pali's bme, it's good
Jul 27 15:36:37 <jon_y> kerio: link? :)
Jul 27 15:36:48 <kerio> ~bmerep
Jul 27 15:36:55 <kerio> nope
Jul 27 15:37:52 <kerio> ~bme-replacement
Jul 27 15:37:53 <infobot> i guess bme-replacement is http://atrey.karlin.mff.cuni.cz/~pali/rx51-bme-replacement  http://atrey.karlin.mff.cuni.cz/~pali/projects/maemo/bme-replacement.html  See also: http://wiki.maemo.org/Bme_replacement . Please, use wiki page to report bugs/problems and/or solutions to them!
Jul 27 15:38:32 <DocScrutinizer05> I really dispise pali's habit to host such stuff on his own server
Jul 27 15:38:51 <kerio> doctors gonna scrutinize
Jul 27 15:40:13 <jon_y> kerio: more like if pali meets an accident someday or forgets to pay the bills, server is gone for good
Jul 27 15:40:27 <kerio> nah, it's a university webserver
Jul 27 15:40:34 <jon_y> all the dead links
Jul 27 15:40:35 <DocScrutinizer05> even worse
Jul 27 15:40:47 <kerio> :D
Jul 27 15:40:54 <jon_y> heh, that makes it even more iffy, uni can decide to pull the plug any time
Jul 27 15:41:05 <DocScrutinizer05> exactly
Jul 27 15:41:13 <kerio> meanwhile, acehack.de has 100% uptime
Jul 27 15:41:24 <kerio> whenever i'm not dicking around with stuff
Jul 27 15:42:43 <DocScrutinizer05> hey, we got garage for stuff like some "pali's bme replacement"
Jul 27 15:43:22 <kerio> well i think the source is on github at least
Jul 27 15:43:36 <DocScrutinizer05> and we got github or gitorious or whatever, for cssu related stuff
Jul 27 15:44:25 <DocScrutinizer05> and we got zilch backup strategy for some random university server
Jul 27 15:52:27 <kerio> DocScrutinizer05: wget -r
Jul 27 15:56:20 <DocScrutinizer05> eh?
Jul 27 15:56:31 <DocScrutinizer05> cat /dev/random
Jul 27 15:56:44 <DocScrutinizer05> fortune
Jul 27 15:57:09 <Sicelo> https://gitorious.org/rx51-bme-replacement
Jul 27 15:57:59 <Sicelo> :)
Jul 27 15:58:11 <DocScrutinizer05> well, then infobot is wrong
Jul 27 15:58:27 <Sicelo> maybe this can be added to infobot
Jul 27 15:58:45 <DocScrutinizer05> ffor users to pick which is the right one?
Jul 27 16:00:24 <Sicelo> i think those of us who don't know much about programming will benefit from Pali's uni page ... at least to get an idea what's going on
Jul 27 16:01:24 <DocScrutinizer05> why isn't it at http://rx51-bme-replacement.garage.maemo.org/  ?
Jul 27 16:04:07 <DocScrutinizer05> ooh wait, prolly because it would rather go to https://garage.maemo.org/projects/jrbme/ ?
Jul 27 16:08:24 <bencoh> "One step closer to a 100% free and open maemo" / 2010 ... that was optimistic :(
Jul 27 16:11:58 <DocScrutinizer05> >>So you run and you run to catch up with the sun but it's sinking // Racing around to come up behind you again. // The sun is the same in a relative way but you're older, // Shorter of breath and one day closer to death. <<
Jul 27 16:12:37 <DocScrutinizer05> s/day/step/
Jul 27 17:44:38 <T_X> anyone having an idea how packages can vanish from extras-devel?
Jul 27 17:44:56 <T_X> this package here: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/sflphone-common/0.9.7~ppa1~jaunty-maemo10/
Jul 27 17:45:10 <T_X> has a broken link to http://repository.maemo.org/extras-devel/pool/fremantle/free/s/sflphone-common/sflphone-common_0.9.7~ppa1~jaunty-maemo10_armel.deb
Jul 27 17:45:55 <T_X> (and now I can't install sflphone, wanted to have a look at it)
Jul 27 18:40:18 <DocScrutinizer05> this might be the result of devels using too leete special chars or versioning scheme in their packages (' names)
Jul 27 18:41:25 <DocScrutinizer05> eeerrrrrr nope, that's pretty simple: Old version cleaned by repository management	System	2010-07-24 12:11 UTC
Jul 27 18:42:57 <DocScrutinizer05> watch http://maemo.org/packages/view/sflphone-common/
Jul 27 18:45:01 <DocScrutinizer05> the pity is that the messing arond with package names made the autobuilder/ repository -management also clean the just built sflphone-common package
Jul 27 18:47:17 <DocScrutinizer05> anyway http://repository.maemo.org/extras-devel/pool/fremantle/free/s/sflphone-common/sflphone-common_0.9.7~ppa1~jaunty-maemo1_armel.deb seems to exist
Jul 27 18:51:40 <DocScrutinizer05> http://repository.maemo.org/extras-devel/pool/fremantle/free/s/sflphone-common/sflphone-common_0.9.7~ppa1~jaunty-maemo3_armel.deb  also exists
Jul 27 18:52:03 <DocScrutinizer05> but that's obviously the last one
Jul 27 18:54:42 <DocScrutinizer05> I mean...
Jul 27 18:54:46 <DocScrutinizer05> sflphone-common 0.9.7~ppa1~jaunty-maemo10	Fremantle Extras-devel free armel	Build succeeded	System	2010-07-24 11:42 UTC
Jul 27 18:58:37 <DocScrutinizer05> sflphone-common 0.9.7~ppa1~jaunty-maemo9	Fremantle Extras-devel free armel	Build succeeded	System	2010-07-24 11:22 UTC
Jul 27 18:58:49 <DocScrutinizer05> sflphone-common 0.9.7~ppa1~jaunty-maemo10	Fremantle Extras-devel free armel	Building	System	2010-07-24 11:36 UTC
Jul 27 18:59:02 <DocScrutinizer05> sflphone-common 0.9.7~ppa1~jaunty-maemo9	Fremantle Extras-devel free armel	Package imported	System	2010-07-24 11:39 UTC
Jul 27 18:59:52 <DocScrutinizer05> A) is maemo10 really > maemo9 ?
Jul 27 19:00:30 <DocScrutinizer05> B) devels really shouldn't upload two versions in 10 minutes, so the older one got not imported yet while the newer once succeeds to build
Jul 27 19:01:30 <DocScrutinizer05> slono, tztztz
Jul 27 19:02:37 <DocScrutinizer05> and then
Jul 27 19:02:39 <DocScrutinizer05> sflphone-common	Fremantle Extras-devel free armel	Package imported	System	2011-12-02 14:43 UTC
Jul 27 19:03:19 <DocScrutinizer05> which seems to lack any proper versioning
Jul 27 19:05:34 <DocScrutinizer05> I guess to clean up this mess you should start a new package sflphone-common2
Jul 27 19:09:02 <DocScrutinizer05> ask merlin1991 what to do to sanitize this confusion
Jul 27 19:09:36 <kerio> DocScrutinizer05: every year is getting shorter
Jul 27 19:09:42 <kerio> never seem to find the time
Jul 27 19:09:55 <kerio> plans that either come to naught, or half a page of scribbled lines
Jul 27 19:10:40 <DocScrutinizer05> thought I'd something more to say
Jul 27 23:14:26 <bencoh> is there a hildon/gtk widget to display web content ?
Jul 27 23:14:54 <bencoh> (to display web content in an app)
Jul 27 23:40:05 <dima5`> Is anybody still using an n900 with maemo as their main phone? I'm finding that the packages in the community APT repo now often have persistent issues, which makes sense since the user base isn't particularly high. Currently (and for the last few months) my n900 no longer has a working alarm clock. What does everybody do? Should I simply revert to some older set of packages and not touch them?
Jul 27 23:49:36 <RiD> Everything seems to work here, except the FM transmitter in one of them
Jul 27 23:49:54 <ecc3g> I just dont use many applications on my phone and yes it's my main phone...
Jul 27 23:53:31 <bencoh> same here
Jul 27 23:57:08 <dima5`> oh, that's interesting
Jul 27 23:57:43 <dima5`> Maybe I'm simply seeing some bug that's not very common. There was a series of bad bugs, and I just assumed that this was the new normal
Jul 27 23:58:23 <dima5`> I click on the clock on the desktop, the menu comes up. I click on "clock & alarms" and the alarm window simply doesn't come up. This works for yall?
Jul 28 00:01:26 <ecc3g> my n900 wakes me up every weekday...
Jul 28 00:01:54 <ecc3g> some of these units are getting old... if it doesn't fix itself with a fresh reflash then possibly it's done...
Jul 28 00:17:48 <bencoh> I highly doubt it would prevent only alram window from working ;)
Jul 28 00:25:23 <dima5`> My hardware is probably fine, and I'll do some software debugging. Thanks much
Jul 28 01:13:46 <dima5`> OK, another question. Anybody know of a good source of replacement n900 batteries? Ebay has plenty "genuine" ones, but it's impossible tell which are counterfeit. The 3rd party manufacturer I bought from before doesn't make these anymore
Jul 28 01:15:14 <RiD> dima5` http://talk.maemo.org/showpost.php?p=1053809&postcount=846
Jul 28 01:15:21 <RiD> ... wrong link
Jul 28 01:15:37 <RiD> this: http://talk.maemo.org/showthread.php?t=65568
Jul 28 01:35:16 <dima5`> thanks
**** ENDING LOGGING AT Mon Jul 28 03:00:00 2014