<mda3>
Wow ! a lot of people here; active persons or all zombies ?
<mda3>
I'm following the neo900.org since it started, I like the project and would like to help
<mda3>
I don't have any electronic capabilities, I'm a web developer (php/javascript), if you need I can help in this area, or unitTests, or translations ?
<mda3>
I'll write to contact email so we keep in touch later
<mda3>
@++
<paulk-aldrin>
money perhaps :)
<mda3>
:) already backed for a neo900 :)
<mda3>
(190 if I remember)
<mda3>
there's need for more for sourcing parts ?
ajhc has quit [Ping timeout: 272 seconds]
<jake42>
yes, Doc is in the process of setting up a webshop so everybody can "order" their components
ajhc has joined #neo900
<mda3>
jake42, you mean every person who has backed for a device could give resources (money) so we can source the parts ?
<mvaenskae>
can the n900 therefore flatline and the battery needs to be initiated with some juice for it to finish boot until the battery loading mechanism can be initiated?
Guest40222 is now known as PrettieKitti_
<DocScrutinizer05>
that's exactly what emergency charging does
<kerio>
except that it doesn't work if it can't boot
<DocScrutinizer05>
to be precise, steady amber means: charging circuitry initialized and charging, main CPU not booted yet
<DocScrutinizer05>
kerio: stop spreading BS
<kerio>
emergency charging won't bring the voltage up enough for NOLO to allow flashing
<kerio>
will it
<DocScrutinizer05>
that's another problem
<DocScrutinizer05>
when CPU boots then the main CPU eventually takes over control over charging. at that point in time steady yellow stops. When then the system doesn't establish stable charging process, that's the system's problem, not the hardware's
<kerio>
users don't particularly care about the hardware
<kerio>
they care about the system working
<kerio>
as a whole
<DocScrutinizer05>
whatever, off topic for this chan
<DocScrutinizer05>
Neo900 charging works best when left alone
<MonkeyofDoom>
good :D
<DocScrutinizer05>
anyway mvaenskae asked if battery needs some kickstart to make N900 start charging, aiui. No it doesn't
<DocScrutinizer05>
the flatbat-deadlock is another problem
<DocScrutinizer05>
related to usually bootloops
<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)
<DocScrutinizer05>
~bootloop
<DocScrutinizer05>
~#maemo bootloop
<infobot>
[#maemo bootloop] 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>
I *really* wish Nokia had integrated a charge mode into xLoader or at least NOLO already
<DocScrutinizer05>
for N9 they did ;-P
<DocScrutinizer05>
but then, for N9 it would be pretty inconvenient to charge battery externally X-P
<DocScrutinizer05>
I really wonder what a certain (ex-)Nokia employee tested with flasher-3.5(!) on N9 that made him mumble "thought as much, they were lazy"
<DocScrutinizer05>
mind you, flasher-3.5 is for N900 and before, for N9 you're supposed to use 3.12
<DocScrutinizer05>
probably certain cert/checksum tests were not yet implemented in flasher-3.5
ddark has joined #neo900
<DocScrutinizer05>
((wish Nokia had integrated)) at very least into 2nd/secondary needed for coldflashing. They easily could have added a batt charge mode into that, and patch flasher-3.5 so that it reboots device into "rescue&charge / coldflashing mode" when battery too low for regular NOLO based flashing
<DocScrutinizer05>
Like a german politician once said
* DocScrutinizer05
idly wonders if Neo900 flashing will support DFU, and/or Nokia "mark2"(?), or only boot from auxiliary system via uSD
<DocScrutinizer05>
while Pali kicked 0xFFFF into shape and thus we have FOSS flasher for the Nokia protocol, it seems we completely lack any implementation on bootloader side that supports it, right?
<Pali>
yes, server side of nokia flashing protocol is missing...
mda3 has quit [Quit: Page closed]
<DocScrutinizer05>
then otoh I'm not educated about how DFU is implemented. Is it part of UBoot?
<Pali>
no idea
<DocScrutinizer05>
I'm pretty sure an unpatched NOLO won't work on any other device but N900, not even on a Neo900
<DocScrutinizer05>
and we just seen that detection of our awesome 1GB RAM depends on uboot as well
<DocScrutinizer05>
so despite all efforts of your humble EE team, Neo900 compatibility to N900 most certainly ends at NOLO
<DocScrutinizer05>
IOW we won't be able to support the "use flasher-3.5 to flash a slightly tweaked FIASCO image to Neo900" scenario
<DocScrutinizer05>
wow, that's even more scary. IRC completely silent on 20 channels since reboot
<kerio>
penis
<kerio>
ARE YOU FEELING BETTER
<DocScrutinizer05>
YES :-D
<DocScrutinizer05>
above bug is incredible. Opensuse/cabal messed up an arbitrary number of machines incl servers running 13.1
<DocScrutinizer05>
gotta love systemd, no?
<DocScrutinizer05>
what however bothers me even more is: I wasn't able to find this ticket or other notes about the bug. Seems my google fu also sucks meanwhile
<DocScrutinizer05>
finally the fine people of Suse inc in #opensuse helped ;-)
<kerio>
i'm not installing the backported libvirt 1.something because it wants to install libsystemd-something
<kerio>
and consolekit
<DocScrutinizer05>
yes, soon you'll find zilch linux packages that could run on a systemd-free system
ddark has quit [Ping timeout: 250 seconds]
<kerio>
DocScrutinizer05: do you have ipv6
<DocScrutinizer05>
well, prolly no
<kerio>
goddammit
<kerio>
i don't want to fire up a DO droplet just to ping
<DocScrutinizer05>
my DSL provider offers IPv6 but my landlord and router/DSL-owner doesn't really like to use it
<DocScrutinizer05>
maybe -p option was useful for an extension of POSIXLY_CORRECT alias, but for sure a posixly correct alias shouldn't accept any -option. For bash's extended alias builtin the "reusable format" for output is default, so -p is useless there either
<DocScrutinizer05>
alias [-p] [name[=value] ...]
<DocScrutinizer05>
Alias with no arguments or with the -p option prints the list of aliases in the form alias name=value on standard output.
<DocScrutinizer05>
from BASH_BUILTINS(1)
* DocScrutinizer05
shakes fist
<FIQ>
lol
<FIQ>
so basically
<FIQ>
-p is there to make your life harder
<DocScrutinizer05>
yes
<DocScrutinizer05>
pun on me: I forgot about unalias and tried to undefine my ``alias alias='alias --'´´ by giving a ``alias alias=´´. Guess what resulted ;-)
<DocScrutinizer05>
((tried to undefine...)) for testing alias -p