<SuperMarioSF>
they have IRC channel on libera.chat #aosc-retro
<Wizzup>
cool, I'll idle there
<SuperMarioSF>
btw the IRC channel is bridged with Discord and Telegram. So you can see the whole picture on the community.
<dreamer>
"bridged"
<Wizzup>
I've seen that before, usually, depending on the integration it becomes a bit messy
<dreamer>
not a bridge
<Wizzup>
dreamer: aren't there some more neat/native integrations?
<Wizzup>
I naively assumed there were
<dreamer>
indeed there are not
<dreamer>
only matrix does actual bridging of protocols
<Wizzup>
well, I suppose for the things you can't self host it's harder
<dreamer>
thigs like discord and telegram rely on bots shouting messages back and forth
<Wizzup>
what about mattermost, or spectrum?
<dreamer>
I call those "tin can telephones"
<dreamer>
mattermost has an ircd bridge
<dreamer>
that essentially works as a kind of bouncer service
<dreamer>
works rather well imo
<Wizzup>
in any case, it would be good to make it easier for folks to join at some point
<dreamer>
(means you connect to that service as if it's an ircd. using your irc client)
<Wizzup>
yeah I understand
<Wizzup>
SuperMarioSF: noted, I only saw a few folks on irc and /names doesn't show the rest I guess :)
<dreamer>
imo is generally less annoying as matrix with it's massive quits/joins :P
<dreamer>
and doesn't really have to "bridge" any thing, since it connects directly with mattermost
<SuperMarioSF>
on telegram side there are 120 members.
<Wizzup>
yeah, one of the downsides of your own ircd is that people usually prefer being on one of the larger irc servers I thought
<Wizzup>
I know that debian bridged xmpp and irc somehow, any idea how that worked?
SuperMarioSF has quit [Read error: Connection reset by peer]
SuperMarioSF has joined #maemo-leste
Livio has joined #maemo-leste
Livio_ has quit [Ping timeout: 268 seconds]
SuperMarioSF has quit [Read error: Connection reset by peer]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
well maybe that is not actually 'bridging', more like forwarding.
<SuperMarioSF>
(also apply on AOSC's)
SuperMarioSF has quit [Read error: Connection reset by peer]
SuperMarioSF has joined #maemo-leste
SuperMarioSF has quit [Read error: Connection reset by peer]
SuperMarioSF has joined #maemo-leste
akossh has quit [Read error: Connection reset by peer]
akossh has joined #maemo-leste
mardy has quit [Ping timeout: 240 seconds]
mardy has joined #maemo-leste
<SuperMarioSF>
some bad news.
<SuperMarioSF>
I can't get the old stock XT883. because seller refused to sell me.
<SuperMarioSF>
apparently someone tricked this person, make him paranoid about buyer request pay shipping fee when arrived.
<bencoh>
uh
<SuperMarioSF>
there are two less good condition XT883 available. also new stock.
<SuperMarioSF>
I had to admit these days the trust between two random strangers is basically a non-existence thing in China, no matter online or offline...
<Wizzup>
I can imagine
xes has quit [Ping timeout: 272 seconds]
xmn has quit [Ping timeout: 240 seconds]
<SuperMarioSF>
One of XT883's stock have been secured.
<SuperMarioSF>
1 to go.
<Wizzup>
sweet :)
xes has joined #maemo-leste
SuperMarioSF has quit [Read error: Connection reset by peer]
SuperMarioSF has joined #maemo-leste
SuperMarioSF has quit [Ping timeout: 240 seconds]
SuperMarioSF has joined #maemo-leste
sunshavi has quit [Ping timeout: 268 seconds]
SuperMarioSF has quit [Ping timeout: 255 seconds]
SuperMarioSF has joined #maemo-leste
<Wizzup>
not sure if anyone has seen it before, but my d4 has a slightly smaller screen render now, like there's a black border everywhere, and the screen redraw works weirdly
<Wizzup>
I have occasionally seen this on my n900 with fremantle, but it happened very rarely
<Wizzup>
screen rotation also fails
<Wizzup>
a few xrandr rotates makes it work again
<Wizzup>
weird
<SuperMarioSF>
maybe some X or compositor issue?
<sicelo>
i think it never happens in stock hildon, but from modified hildon as found in cssu onwards. I recall it happens when device boots up in portrait instead of landscape (hence not a problem in stock hildon, as portrait isn't really supported there)
<Wizzup>
sicelo: this just happened 'over night'
<Wizzup>
like, I woke up, unlocked the device, and it was like this, but uptime was 1+ day
<buZz>
Wizzup: i have sometimes seen such , but always assumed it was just my mind
<buZz>
does 'xrandr' also see it?
<Wizzup>
buZz: yes, it had a weird effect on me some times a few years ago when I was like "is this me?"
<buZz>
maybe you can see it on scrot?
<Wizzup>
I 'fixed' it already
<Wizzup>
but I'm sure it's there
<buZz>
next time
<Wizzup>
trust me, it is :)
<buZz>
is eh 'google talk' in 'voip&IM accounts' the general XMPP one?
<buZz>
oh 'telepathy-gabble' perhaps?
<Wizzup>
did you update?
<Wizzup>
there should be normal jabber/xmpp
<buZz>
i did, still have google talk and irc in there, no xmpp/jabber
<buZz>
do i need to install telepathy-gabble ?
<Wizzup>
sure, but isn't that pulled automatically
<uvos__>
Wizzup: does 'xrandr' also see it?
<uvos__>
this one is imporant
<buZz>
maybe some meta package isnt grabbing new items for it?
<Wizzup>
uvos__: it was giving the usual res
<Wizzup>
buZz: sorry, I can't check for you now, I can check in a few hours, I'm about to go out
<uvos__>
ok
<Wizzup>
uvos__: I didn't check overscan and such
<uvos__>
i gues also kill h-d next time
<uvos__>
to exonerate xorg
<uvos__>
but sounds like a bug in hildon
<buZz>
np, i'll just try installing it, someone at nurdspace setup a xmpp server
<buZz>
i might be online with buzz@space.nurdspace.nl now
<buZz>
but not finding a lot of frontends that could co-exist on maemo, i think
<norayr>
please give me a link to a proper usb condom.
<norayr>
mine turns droid4 up.
<norayr>
uvos said it shoudn't.
<norayr>
but when i search a usb condom on ebay, i only see something which looks like mine. and which i already got.
noidea_ has quit [Quit: Leaving]
noidea_ has joined #maemo-leste
<buZz>
noidea_: eh, i just made one myself, with a USB-A female and a USB-A male
<buZz>
and just connected GND and +5V inside it
<buZz>
i plan to make another one that does D+/D-/GND but no +5V
<uvos__>
you could build a condom that still pulls the id pin up
<uvos__>
a condom by itself dosent guarentee that the device says off
<buZz>
uvos__: or add a switch for that!
<uvos__>
you need to just connect vbus and gnd
<uvos__>
buZz: sure
<buZz>
but USB-A has no ID pin
<uvos__>
yeah but microusb dose
<uvos__>
the id pin is for iding the cable
<uvos__>
not for anything with the host
<buZz>
just noticed: osso-abook can show 'recent' contacts, which includes unadded contacts
<buZz>
tapping one crashes the tool
<buZz>
uvos__: so, a usb-micro condom could use a ID switch
<uvos__>
buZz: you could, im not sure why you would want to tho
<uvos__>
(for d4 usage)
uvos__ has quit [Quit: Konversation terminated!]
<buZz>
yeah not sure, a data-only condom could benefit more i guess
uvos__ has joined #maemo-leste
<buZz>
'export' in osso-abook also crashes :(
<norayr>
another question (not sure it was answered, but maybe i missed the answer) is why maemo kbd opens a window to type in? why initially they didn't do it the way it is in meego/sailfish/android. is wayland/xorg the issue?
<norayr>
(i cannot do hw hacks myself i think)
mardy has quit [Quit: WeeChat 2.8]
<Wizzup>
buZz: it shouldn't crash for sure, but yes, it's normal that it adds online folks from protocols even if they are not in the book
dev has joined #maemo-leste
<buZz>
norayr: afaik thats just the plain maemo method
<buZz>
meego/sailfish/android are indeed different, ios is similar though
uvos has joined #maemo-leste
<Wizzup>
buZz: I think if you want to edit the fields, you need to first add the contact as a contact, and then edit it
Pali has joined #maemo-leste
<buZz>
right, i dont really need to/want to, just trying to figure out how it works :P
<buZz>
fun to see my hackerspace buddies presence icons in contacts now though :)
<Wizzup>
:)
<sicelo>
norayr: maemo predates those OSes you talk about. Also, they may have done it that way because by then, they had no other way to do spell-checks for example
<sicelo>
FYI that 'window' was largely unchanged from even older iterations of Maemo (think N770, N8x0)
<uvos>
its a limitation of the way the vkb was desined not anything else
<Wizzup>
they designed it that way, yes
<sicelo>
norayr: also they supported text input via scribbling (but this didn't make it to Fremantle, probably ran out of time)
<sicelo>
So yeah, today it's considered a problem for obvious reasons
<sicelo>
Maybe Leste should have built itself on Harmattan as opposed to Fremantle :-p
<uvos>
it should be noted that the window is also an option on android, that android uses below a certain screen size
<uvos>
(not really relevant anymore)
<sicelo>
Android definitely does on landscape afaict
<uvos>
depends on screen size
<sicelo>
Tbh, the window thingy is somewhat expected in landscape (which maemo before harmattan was designed for)
<sicelo>
uvos: very few phones have 'deep' enough screen in landscape
<uvos>
on asop the screen has to be very small
<uvos>
i know samsung fidlled with it
<uvos>
but on asop it has to be less than 5 inches or something
<uvos>
(at 16:9 ofc)
<sicelo>
Continuing on my earlier thought - landscape keyboard is also a problem for phosh ... they're currently trying to keep the application visible, but the keyboard gets weird after that
<sicelo>
5 inches 🤣
<sicelo>
N900 diagonal is 3.5", ftr
<buZz>
maybe a osso-xterm fork could be made thats only portrait mode , plus , keeps a keyboard on bottom half of the screen
<Wizzup>
maybe different h-i-m could be made so it works for more apps
<sicelo>
And then I'm back to battery woes on d4 :'(
<buZz>
sicelo: you are?
<buZz>
what kinda woes
<sicelo>
Failure to charge
<buZz>
completely?
<sicelo>
Yes
<buZz>
it doesnt boot when connecting a usb cable?
<sicelo>
It boots, to death :-D
<buZz>
sicelo: what do you mean? you get kexecboot?
<sicelo>
Yeah
<buZz>
does it start the kernel then?
<buZz>
ever reaches that chargemode-sdl application?
<sicelo>
Currently doesn't get there
<sicelo>
Because cpcap thinks there's no charger or some such
<buZz>
sicelo: eh, during boot on lowpower, often for me, the d4 doesnt notice the USB cable offering power
<sicelo>
Yes, i remember you sais
<buZz>
sicelo: so during the time -after- kexecboot and the vibrating notification , but -before- i get txt on display, i tend to disconnect/reconnect USB cable a couple times, until LED goes green
<sicelo>
And it matches what i always see. I've accepted it as a "feature"
<buZz>
maybe this can help you?
<sicelo>
I know and do that
<buZz>
as a failsafe, i just have a external li+ charger in my bag with 2 wires :P
<buZz>
just connect it to the battery straight up, and charge from ~whatever (often a powerbank)
<buZz>
just some while is plenty to have it able to boot fully and charge itself again
<sicelo>
Yeah. It's a hassle
<buZz>
¯\_(ツ)_/¯
<buZz>
sicelo: another thing i do, is just carry my second d4 along with full battery and powered off
<Wizzup>
I've never been able to not power it
<buZz>
sicelo: then when first is ded/empty, just swap sim+SD over
<buZz>
:P
<sicelo>
I have 1 d4 ;-)
<buZz>
not really recommended imho (wifi calibration and battery calibration goes off)
<sicelo>
Why wifi calibration goes off when you swap sim?
<buZz>
Wizzup: ooo yesterday i almost got a nurdspacer into joining the maemo leste dev-ers , but he's still a bit held back :P any convincing arguments for him?
<buZz>
sicelo: because the wifi radio is calibrated
<sicelo>
Ah, sd
<buZz>
yeah sim&SD
<Wizzup>
depends on what he'd find a convincing argument :P
<buZz>
Wizzup: hehe not sure
<buZz>
he was going on that he really -needs- root on a device and how so many dont really do that
<buZz>
or how they arent coming with source, etc
<sicelo>
Wizzup: uvos says he also hasn't experienced it. But at least myself and buZz do, and somewhat frequently
<buZz>
yeah quite regular
<Wizzup>
sicelo: yeah, when I leave it on a wall charger for a bit it usually just boots after ~10 mins
<buZz>
but i can leave it 'on usb' while 'not charging' (no led goes on, doesnt boot)
<buZz>
just leave it for a while, it -will- charge some, slowly
<Wizzup>
right
<buZz>
iirc that even works when it boots directly from USB connecting, and then crashes during bootup
<sicelo>
It's never happened to me, or I didn't wait long enough. I'm not used to this :-P
<uvos>
did you update to devel
<uvos>
like this week?
<uvos>
i made the cpcap module built in
<uvos>
and ajdusted the irq timeing
<uvos>
and yeah i never have a problem with it
<sicelo>
I am updated
<buZz>
uvos: built-in so the cpmem stuff can work now/soonish ?
<Wizzup>
looks like if we implement handle channels well, we might be able to start a conversation from the address book easily
<buZz>
was it cpmem? not sure
DPA has joined #maemo-leste
<uvos>
buZz: cpmem?
<buZz>
eh, the library in kernel to read the data from battery? to know if its HV lipo or not
<buZz>
some 1wire protocol
<uvos>
buZz: no thats unrealted
<uvos>
also that works right now
<uvos>
i tested it recently on xt875
<buZz>
i dont see it working
<uvos>
you just have to unblacklist the module
<buZz>
oh
<uvos>
then detection works and design voltage is set to 4350 mV
<uvos>
you still have to change the charge voltage to 4.3 too
<uvos>
but you can do that over sysfs
<buZz>
i see just bluetooth and idle blacklisted?
<buZz>
at least, in /etc/modprobe.d/*
<uvos>
no
<uvos>
in leste we also blacklist hdq
<uvos>
i cant check rn
<buZz>
ah, yeah , thats in _idle
<uvos>
but im sure its there
<buZz>
i didnt know that was the one you ment :P
<buZz>
i didnt know charge voltage was settable over sysfs, nice :)
* buZz
reboots with hdq unblacklisted
<uvos>
should be reflected in voltage_max or what the sysfs file is called
<uvos>
and theres also charge_voltage or so
<buZz>
sadly, still sees 4200000 as max_design :(
<uvos>
thats stays 4.2 (design decision)
<buZz>
'can not find battery nvmem device' sadly in dmesg :(
<uvos>
check if the module probed
<uvos>
also i do have one battery where the nvmem failed
<uvos>
so theres that
<buZz>
omap_hdq couple lines above, also a 'w1_master_driver attaching...' right after first 'can not find battery nvmem device' , then another two 'can not find battery nvmem device'
<buZz>
i can try with another eb41 i guess
<uvos>
hmm thats wierd maybe dump the nvmem
<uvos>
its in systfs
<uvos>
somewhere
<uvos>
bus/twi or something
<buZz>
its saying it cannot find the nvmem device, how could i read it then?
<uvos>
it cant find the battery nvmem device
<uvos>
the way it works is i dumped a bunch of batteries and looked at the contence
<uvos>
idk what the bytes mean
* buZz
rubs the flexpcb against contacts a bit
<uvos>
if its some other version than i know of it might not work
<buZz>
uvos: ahh, ok, i'll check then
<dreamer>
buZz: or else it gets the hose again?
<buZz>
:D
<uvos>
ah also it wont work rn
<uvos>
since i built the cpcap modules in
<uvos>
but the 1w module is a module
<uvos>
the cpcap dependancy is soft
<uvos>
so in this case it cant work
<uvos>
it wont wait for the 1w module
<uvos>
since building it in dosent seam to help sicleo ill make it a module again next release
<buZz>
ah, hmm
<buZz>
'break irqstatus not cleared (04)' and 'TX irqstatus not cleared' are flooding my dmesg now, it seems
<buZz>
ah, after 'cat nvmem' a bunch of times, it eventually does give a reply
<uvos>
that sounds like you also have a hw issue
<buZz>
perhaps, or the irq isnt properly handled? should that happen through dtb?
<norayr>
I saw a unisoc t606 device today first time in my life. never heard before about unisoc company
<norayr>
it's nokia g21
<buZz>
cool :)
<norayr>
i also cannot charge my droid again
<norayr>
need to unscrew the battery to use separate charger
<norayr>
hate doing that.
<buZz>
tried just leaving it for 30mins on 'unable to boot, not showing sign of charging' ?
<buZz>
with USB connected
<buZz>
that so often works for me
<uvos>
thats _supposed_ to work
<buZz>
a 'usb doctor' then shows ~50mA of draw
<uvos>
cpcap has device off trikle charging
<buZz>
which isnt a lot :P
<uvos>
thats what its set to by mbm
<buZz>
but, enough to get some boot working well enough to charge more later
<norayr>
my pine64 charger shows how much the device draws
<buZz>
uvos: we cant change that right?
<buZz>
norayr: ah, built-in doctor :)
<uvos>
buZz: no also its like 75mA max
<buZz>
i'd love if some people could do the unblacklisting + check their 89-50003xxxxxxxxx number in /sys/bus/w1/devices/
<buZz>
:P
<buZz>
maybe thats visible on android even?
<uvos>
not sure what to do about that btw
<norayr>
so i noticed in android mode (with empty battery sign) it draws about 0.1-0.2 amper, so i left it like that overnight, but that dxdn't help.
<uvos>
not really sure how to id the chip then if its not allways the same
<buZz>
uvos: i know, but we first need to know how/what is happening , right? so more data could help
<norayr>
sometimes in same mode it ioesn't draw at all.
<buZz>
maybe we used the unique ID of the chip as the -name- of chip , while its actually just the ID string of the same chip?
<buZz>
norayr: maybe your ribbon is breaking a bit on the battery?
<uvos>
buZz: i mean its something to check but it for sure works on various batteries i have
<buZz>
right, but it would maybe be nicer if this works for >1 person? :D
<uvos>
yeah android not wanting to charge after booting (the ! battery sign means the android kernel bootet fully)
<uvos>
suggests some kind of hw failure
<uvos>
or you discharging the battery below 2.5V or something
<uvos>
android refuses to charge below some thresh around there
<uvos>
(also this is _terribe_ for the battery)
<buZz>
uvos: it may be as simple as 'just check for leading 89-500003'
<buZz>
eh, one 0 less
<buZz>
maybe its '89-5000' as chip identifier, and the remaining 4 bytes hex are just the unique battery serial# ?
vgratian has joined #maemo-leste
vgratian has left #maemo-leste [#maemo-leste]
sunshavi has quit [Ping timeout: 268 seconds]
vagag has left #maemo-leste [#maemo-leste]
Livio has quit [Quit: I'm gone away.]
<Wizzup>
uvos: so I am trying to understand your comments regarding my sphone patch and rtcom
<Wizzup>
I only see two rtcom_el_event_new, and I thought I patched both
joerg has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
<joerg>
buZz: >>leaving it for 30mins on 'unable to boot, not showing sign of charging' << didn't work e.g. on my N950 recently
adc_ has joined #maemo-leste
freemangordon1 has joined #maemo-leste
StephanvanSchaik has joined #maemo-leste
xmn_ has joined #maemo-leste
doc|home has joined #maemo-leste
meridion_ has joined #maemo-leste
Treebeard has joined #maemo-leste
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
tmlind has joined #maemo-leste
RedM_ has joined #maemo-leste
macros_2ndPC has joined #maemo-leste
ikmaak2 has joined #maemo-leste
meridion_ is now known as ghost
Langoor_ has joined #maemo-leste
ghost is now known as regain
DPA- has joined #maemo-leste
meridion has quit [Killed (lead.libera.chat (Nickname regained by services))]
regain is now known as meridion
<buZz>
joerg: yeah i was talking about the droid4 specifically
<joerg>
buZz: probably a common problem with a lot of embedded devices that use somewhat software controled charging
avoidr_ has joined #maemo-leste
<sicelo>
indeed
<joerg>
seems the hysteresis between where the system tries booting when batvoltage goes up and where it stops working when batvoltage drops is too small for old batteries with high ESR
DPA has quit [*.net *.split]
uvos has quit [*.net *.split]
dev has quit [*.net *.split]
uvos__ has quit [*.net *.split]
xmn has quit [*.net *.split]
akossh has quit [*.net *.split]
pere has quit [*.net *.split]
RedW has quit [*.net *.split]
freemangordon has quit [*.net *.split]
BenLand100 has quit [*.net *.split]
adc has quit [*.net *.split]
doc has quit [*.net *.split]
Treebeard is now known as BenLand100
Stephanv1nSchaik has quit [Ping timeout: 240 seconds]
Langoor has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
<buZz>
yeah totally
<buZz>
many devices just let the battery charger chip itself manage the poweron/off , so it can always trickle prior to booting
<buZz>
or at least, many i was analyzing
norayr has quit [Ping timeout: 240 seconds]
macros_ has quit [Ping timeout: 240 seconds]
ikmaak has quit [Ping timeout: 240 seconds]
tmlind_ has quit [Ping timeout: 240 seconds]
avoidr has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
<joerg>
they do tricky charge with a tiny current like the aforementioned 50mA (USB Vbus) and then when a certain battery voltage threshold gets tripped, the system tries booting and often succeeds to get to the point where it messes with charging chip, enables USB PHY and statemachine and the latter two alone need 60mA for themselves on N900 OMAP3. This in turn means the battery suddenly doesn't get charged by a 50+mA but gets DIScharged at a rate of (trickecharge
<joerg>
- sytembootcurrent) = possibly up to 100mA. Depending on the internal impedance of the battery this will cause a Vbat drop that might suffice to make the whole system emergency-shutdown from brownout-detection
<joerg>
trickle* not tricky :-)
uvos has joined #maemo-leste
<uvos>
Wizzup: yeah but sphone also reads events
<uvos>
and now its reading the backend in the wrong place
<Wizzup>
uvos: right, but the writing was ok
<Wizzup>
uvos: I get confused with the usage of local-name in sphone
<Wizzup>
what is this supposed to be?
<Wizzup>
it's always '<SelfHandle>' in fremantle
<Wizzup>
(since there is no name for the local contact/phone)
<Wizzup>
Is that supposed to be the name of the contact, human friendly?
<uvos>
no idea what its supposed to be in rtcom-el
<sicelo>
joerg: yeah. i always knew N900 to have that problem. but compared with what i've experienced on the Droid 4, N900 problem becomes completely insignificant. Maybe it's kexecboot dance that affects it (since device takes a while to get into kexecboot menu, and all this time it's only draining, not charging battery)
<uvos>
the point is that you changed the way that sphone stores events
<uvos>
but not it reads them
<uvos>
so this disconnect obv breaks sphone
<Wizzup>
yeah, I fixed this locally I think
<Wizzup>
I am just trying to figure out what sphone does with the "name"
<uvos>
what name?
<Wizzup>
it seems to use local-name for the contact->name
<Wizzup>
which is also wrong
<uvos>
thats human readable contact name
<uvos>
as the struct would suggest
<Wizzup>
I think that should be remote-uid
<uvos>
maybe, i cant help you with how rtcomm fields are supposed to be filled
<Wizzup>
:)
<uvos>
i have nothing to go by other than the field name
<Wizzup>
what about a n900 with fremantle? :P
<uvos>
nope
<sicelo>
:-P
<joerg>
sicelo: basically the problem needs hardware and bootloader cooperation to get solved. I N900 they had average hardware support for it and they compensated a lot by fixing the bootloader
adc_ has quit [Ping timeout: 240 seconds]
adc has joined #maemo-leste
avoidr_ is now known as avoidr
<joerg>
obviously the OMAP3-ROMBL enables USB to allow coldflashing, but in NOLO (next "1st" stage bootloader after OMAP's ROMBL) I think they deliberately shut down everything not needed - maybe incl USB PHY and interface - as soon as possible to reduce system power demand, and then let the battery charge while monitoring battery voltage for a certein higher threshold that allows safe regular system boot. Unless the battery is very old and high impedance
<uvos>
the d4 on the other hand is fully hw implemented, the bootloader just sets some regs and shutsdown
<joerg>
wow
<uvos>
problem is the comperator threshold is low
<uvos>
and we have to boot android and then linux before we can charge
<uvos>
this takes to long
<joerg>
the N900 charger controller has a watchdog that mandates tickling every ~10s or it will reset all registers to safe default state which is trickle charge
<joerg>
uvos: yeah, I can see how that takes waaaay too long
_whitelogger_ has joined #maemo-leste
<uvos>
this fixes:
<uvos>
* volume keys on xt875
<uvos>
* volume keys on pp
<uvos>
* lock-generic's lock on slide
<uvos>
* lock-tklock's relock feature
<uvos>
* power key on mz617
<uvos>
unfotinatly is also very likely to cause some hithero unkown subtle bugs
<uvos>
so please report
crab_ has joined #maemo-leste
sunshavi has joined #maemo-leste
<Wizzup>
which kind of bugs should we look for?
<Wizzup>
is this -devel?
<uvos>
Wizzup: yeah
<Wizzup>
ok
<uvos>
anything with input
<uvos>
obv
jrayhawk_ has joined #maemo-leste
jr-logbot has quit [Ping timeout: 240 seconds]
nohit has quit [Ping timeout: 240 seconds]
nohit_ is now known as nohit
sixwheeledbeast has quit [Ping timeout: 240 seconds]
LjL has quit [Ping timeout: 240 seconds]
_whitelogger has quit [Ping timeout: 240 seconds]
branon has quit [Ping timeout: 240 seconds]
crab has quit [Ping timeout: 240 seconds]
jrayhawk has quit [Ping timeout: 240 seconds]
LjL^ is now known as LjL
joerg has quit [Quit: this shouldn't have happened... ever]
joerg has joined #maemo-leste
crab_ has quit [Quit: WeeChat 3.5]
crab has joined #maemo-leste
sunshavi_ has joined #maemo-leste
sunshavi has quit [Ping timeout: 268 seconds]
tsaebdeleehwxis is now known as sixwheeledbeast
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
sunshavi_ has quit [Ping timeout: 268 seconds]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
sunshavi_ has joined #maemo-leste
sunshavi_ has quit [Ping timeout: 252 seconds]
uvos has quit [Ping timeout: 255 seconds]
Pali has quit [Ping timeout: 268 seconds]
sunshavi has joined #maemo-leste
<Wizzup>
uvos: ok, I think I fixed the sphone patch and did some typo fixes
<Wizzup>
will cleanly test soon, maybe not tomorrow, might be travelling