<Oksana>
I remember that the chip ( http://cache.freescale.com/files/32bit/doc/data_sheet/CRTOUCHDS.pdf ) allows to detect "typical" gestures, one-finger slide or two-finger zoom-in-zoom-out-rotate, at the resistive touchscreen. Does it work as expected, or is there some problem?
<bencoh>
hmm ... using a special chip to detect TS gestures ?
<DocScrutinizer05>
Oksana: we haven't tested it yet
<Oksana>
Okay. Thank you :-) I am just hoping to hear about real-life-testing results of finger-vs-stylus detection
<DocScrutinizer05>
bencoh: the chip is not to detect gestures, the chip implements dual-touch on ordinary 4eire resistive touchscreens
<bencoh>
oh, kay
<bencoh>
that chip
<bencoh>
:)
<DocScrutinizer05>
the gesture detection is just a special way of the chip to report about dual-touch events on a HID interface
<DocScrutinizer05>
I'm not even liking it a lot
<DocScrutinizer05>
but well, in the end it prolly doesn't make lot of a difference
<Oksana>
I am not liking it a lot, because I think that it should have been possible to re-program it. Like, add one-finger spiral-zoom gesture detection into it.
<Oksana>
But, it's better than no-dual-touch at all
<DocScrutinizer05>
spiral zoom is done by microB already
<DocScrutinizer05>
I wouldn't like zooming kicking in when I for example try to draw a spiral in a drawing program
<DocScrutinizer05>
I'd rather like *no* gestures are detected at all by the chip, just reporting accurate X1Y1(,X2Y2)
<DocScrutinizer05>
gesture detection is actually something that's up to the driver or to the app
<DocScrutinizer05>
*should be*
nox- has quit [Quit: Leaving]
Humpelst1lzchen has quit [Ping timeout: 252 seconds]
<DocScrutinizer05>
you can't shut off N900 as long as it is connected to charger
<memfrob>
it's unplugged
<memfrob>
it finally stopped on its own. am i the only one here with this problem? the n900s cant be this unstable
<DocScrutinizer05>
never seen this
vakkov has quit [Ping timeout: 255 seconds]
<DocScrutinizer05>
maybe your power button is stuck?
<DocScrutinizer05>
it's just that the device powers up whan connected to charger, and it takes ~30s to boot up and almost as long for shutting down
<DocScrutinizer05>
now I seem to recall there once been such issue with device powering up again after shutdown, long ago. Can't recall details thouf. Must have been a software issue around power kernel
<DocScrutinizer05>
shouldn't happen after complete flashing of device
<memfrob>
i think i let off the power button too soon and it got caught in a loop
<DocScrutinizer05>
nope
<DocScrutinizer05>
there's no such issue in maemo/N900
<memfrob>
i just shut it down again and its behaving
<memfrob>
nope its looping again, i think i have a bad phone.
<DocScrutinizer05>
I think you should try to reflash manually
<DocScrutinizer05>
my script is not for badly messed up rootfs
<DocScrutinizer05>
flash COMBINED, flash VANILLA, flash COMBINED again, then let booot for 10min
<DocScrutinizer05>
both flashing COMBINED and VANILLA take ~30..90s
<DocScrutinizer05>
if it's faster, it failed
<DocScrutinizer05>
oooh, and you need fully charged known-good battery for flashing
<DocScrutinizer05>
charging battery will fail when phone bootloops
<DocScrutinizer05>
~bootloop
<infobot>
somebody said bootloop was when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device.
<memfrob>
wow so it has to be 100% . 95% etc will not work
<DocScrutinizer05>
there's no way for user to tell "95%" since when device bootloops you won't ever see any battery charge idicator with meaningful data
<DocScrutinizer05>
press and hold 'U' key and plug in charger. When it stays at Nokia screen with USB symbol, battery charge level is sufficient for charging
<DocScrutinizer05>
on powered down device, that is
<memfrob>
so you cant flash it if the USB logo is present on nokia bootsplash logo (the one without music)?
<DocScrutinizer05>
yes
<DocScrutinizer05>
err you CAN flash it
<memfrob>
ok that makes sense, because i saw that.
<memfrob>
well you can but it wont be a clean flash, there will be screwed up stuff, etc.
<DocScrutinizer05>
aha, why?
<memfrob>
well i cant seem to get a good flash and thats most likely the reason.
<DocScrutinizer05>
I can't make sense of your statement
<DocScrutinizer05>
this wiki page got debugged and improved over years, and everything in there is comprehensive and correct
<DocScrutinizer05>
no hints missing, no incorrect advice
<memfrob>
how does this make sense "neither the wall charger nor the USB cable will charge the N900 battery if the N900 cannot boot the OS" if it's an external battery wall charger, seperate from the N900?
<DocScrutinizer05>
it makes sense
<DocScrutinizer05>
N900 charging process is software controlled
<Oksana>
"neither the wall charger nor the USB cable will charge the N900 battery if the N900 cannot boot the OS" has "wall charger" as in "outlet->microUSB->N900"
<DocScrutinizer05>
that's why bootloops won't charge but discharge battery
<Oksana>
"wall charger" for battery (not N900) will work
<CaptHindsight>
the wall battery charger does not use the phone or OS to charge the battery
<DocScrutinizer05>
when you remove the battery it's not a N900 battery but a BL-5J
rjeffries has joined #neo900
<DocScrutinizer05>
I never heard of "the wall battery charger"
<CaptHindsight>
oh then we need to define the terms
<Oksana>
Yes, "battery charger" (be it from wall-outlet, USB, solar panel, whatever) will work. Unlike a "phone charger" (be it from USB, wall-outlet or whatever)
<CaptHindsight>
memfrob has a battery charger for the n900 batteries that plugs in a wall outlet and the battery plus directly into the charger, no phone necessary
<CaptHindsight>
plus/plugs
<DocScrutinizer05>
"wall charger" pretty much *is* a defined term in maemo context
<DocScrutinizer05>
when no phone necessary then why he's referring to a HowTo about *ohone* flashing?
<DocScrutinizer05>
phone even
<CaptHindsight>
when DocScrutinizer05 says wall charger it's the power supply that plus into the wall outlet and the other end into the n900
<CaptHindsight>
mo big deal, just a misunderstanding over semantics
<DocScrutinizer05>
~bootloop
<infobot>
methinks bootloop is when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device.
<DocScrutinizer05>
>>>... Or external charger ...<
<CaptHindsight>
so memfrob needs to start with a 100% fully charged battery
<CaptHindsight>
no problem
<DocScrutinizer05>
and I told to power down device, press and hold 'U' key and plug in wall charger, and check if USB icon stays on Nokia screen. When it does, the battery is sufficiently charged for flashing. When battery is not sufficiently charged, the Nokia screen (incl USB logo) will vanish and device tries to boot into OS to charge battery
<DocScrutinizer05>
which will fail when rootfs is garbled
<CaptHindsight>
I need to build a time machine so i can go back in time and poke some engineers in the eyes, among other things :)
<DocScrutinizer05>
~emergency charging
<DocScrutinizer05>
~emergencycharging
<DocScrutinizer05>
~listkeys emergency
<infobot>
Factoid search of 'emergency' by key (1): security emergency plan.
<DocScrutinizer05>
aaah
<DocScrutinizer05>
~flatbatrecover
<infobot>
Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop)
<Oksana>
Fortunately, Neo900's chip will not need OS to charge the battery.
<DocScrutinizer05>
yep
<DocScrutinizer05>
Neo900 hw is smarter
<memfrob>
DocScrutinizer05: thanks I'll flash it again and look watch the USB logos and be more observant this time
<DocScrutinizer05>
CaptHindsight: check out bq24150
<DocScrutinizer05>
it needs I2C watchdog kicking to keep it charging
<DocScrutinizer05>
NFC why Nokia didn't integrate that watchdog kicking into bootloader (aka NOLO aka "the Nokia screen")
<DocScrutinizer05>
NOLO checks battery voltage, but when it's too low voltage, NOLO doesn't charge battery, it tries to boot linux to make battery charging happen
<DocScrutinizer05>
which obviously is a pretty silly idea
<DocScrutinizer05>
the emergency charging of bq24150 (~flatbatrecover steady amber) only charges battery until CPU boots up
<DocScrutinizer05>
i.e. some 3.xV
<memfrob>
flashing vanilla took 28.9 seconds does that sound about right?
<DocScrutinizer05>
yes
<DocScrutinizer05>
very good
<memfrob>
ok i have a dark screen now with frozen loading dots below, after i flash combined the first time i immidiately flash with vanilla right?
<DocScrutinizer05>
right
<DocScrutinizer05>
and after that you flash combined again
arcean has quit [Read error: Connection reset by peer]
che11 has quit [Ping timeout: 256 seconds]
xes has quit [Quit: leaving]
xes has joined #neo900
freemangordon has quit [Ping timeout: 245 seconds]
mvaenskae has quit [Ping timeout: 245 seconds]
mvaenskae has joined #neo900
nox- has quit [Quit: Leaving]
<Oksana>
~marco
<infobot>
POLO!!
norly has quit [Quit: Leaving.]
<DocScrutinizer51>
~ding
<infobot>
dong
<DocScrutinizer51>
~king
<infobot>
~kong, or Dessimat0r
<DocScrutinizer51>
short update: right this minute we're all busy to figure how to finally merge data from 5 different sources into a single decent customer database that includes all payements (incl transfers from GDC) and emails telling us about special requests, merges multiple payments into one account balance etc pp
<Oksana>
Good :-D The PayPal-Bank-Whatever should be fairly simple, it's the Goldelico ones which you have to look out for?
<wpwrak>
(that's just the interest guessulator. some 10% error margin, i guess, since not everything is properly recorded)
<DocScrutinizer05>
Oksana: exactly
<DocScrutinizer05>
and the 12.4529743% GDC subtracted which we consider as valid payment
<wpwrak>
i get something like 13.2% (looking at actual transfers)
<wpwrak>
but then, this difference disappears in the noise, too
<DocScrutinizer05>
I.E. you donated 100.- to GDC, GDC according to your instructions transferred 84.96 to Neo900 UG. Neo900 UG shall issue a 100.-(!) Euro voucher to you
<DocScrutinizer05>
it's all a nightmare for an Electronics Engineer