gg2112 has quit [Remote host closed the connection]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
Daanct12 has joined #maemo-leste
xmn has joined #maemo-leste
<Daanct12>
joerg: interestingly, maemo forum flagged my ip as a bad bot somehow lol
<Daanct12>
sorry for the wrong ping if this isn't the right person :)
xmn has quit [Ping timeout: 256 seconds]
joerg has quit [Ping timeout: 256 seconds]
joerg has joined #maemo-leste
<joerg>
Daanct12: the forum uses its own noforumspam stuff. I don't know details how to get unbanned, except by "changing your IP"
<buZz>
we have a forum?
<buZz>
oh maemo.org i guess
<joerg>
talk.maemo.org I guess
<Daanct12>
weird, it seems to have unbanned me
<Daanct12>
yup, talk.maemo.org
<buZz>
:)
<Daanct12>
i guess my tablet\ was cursed then
<buZz>
many leste users there?
<Daanct12>
i'm going to count myself as one :)
<buZz>
hehe
<buZz>
typing this on my d4 on -devel
<Daanct12>
i got another n900 for a good deal, unfortunately the open/close cover is kinda broken so it's always in the keyboard mode
<Daanct12>
:(
<Daanct12>
at least it still has the sd card magnet, so that's cool
<buZz>
get a d4, man :)
<Daanct12>
i will :)
<Daanct12>
but
<Daanct12>
i have a fxtec pro1 and 1x as well
<Daanct12>
i can hear Wizzup noise
* joerg
wonders where to find some ultra-tiny magnet for a replacement. It seems it's _always_ the magnet that got lost
<joerg>
wait, when it's always in kbd mode then I have a very good idea where the magnet must be
<joerg>
;-)
<Daanct12>
is it the motherboard?
<Daanct12>
i removed the back cover, it's still doing that
<Daanct12>
so i dont think it's the sd card magnet
<joerg>
yes, there's a hall-switch on the PCB, iirc above the O key
<Daanct12>
damn, that's really complicated construction lol
<joerg>
the magnet is supposed to stick in a "bay" on the bottom side of the display slide
<Daanct12>
no wonder why they the thing was too expensive back in the day and they had to cut some cost with the n9
macros_ has quit [Ping timeout: 256 seconds]
<Daanct12>
joerg: hmm, so you said that the magnet was most likely misaligned?
<joerg>
I think the magnet got loose from the display slide and sits near the hall-sensor now
<Daanct12>
i dont want to disassemble another n900 :) i already caused some noise issue to the touch screen
<Daanct12>
on my other n900
macros_ has joined #maemo-leste
<Daanct12>
joerg: hmm, then it's most likely what happened
<Daanct12>
that make sense
<joerg>
disclaimer: all this is 10 years old possibly foggy memories. I might be wrong regarding the magnet's fixation on display slide
<Daanct12>
well i'm just going to leave it in kb mode then
<Daanct12>
i still hate plugging back that display flex cable, i think i most likely have damaged that cable in process
<Daanct12>
which pretty much caused the noise issue
<joerg>
btdt
<joerg>
that connector is a bitch, and broken by design
<joerg>
I ruined my first N900 exactly same way you probably did: broken flex cable connector or more specifically I suspect the vias there are the culprit
<Daanct12>
i guess that issue could've been got rid of if they just use metal contacts or something
<Daanct12>
which, is not possible with that design
<Daanct12>
i still dont think you can find brand new flex cable on ali :(
<Daanct12>
anyway, Wizzup i got a pro1 and 1x :)
<Daanct12>
i think im going to boot leste on it
<Daanct12>
very soon
<Daanct12>
joerg: btw, my other n900 isn't exactly ruined, but it has noise on the screen that shows up when you move the cursor on the middle top of the display
<Daanct12>
so i dont use it for leste, and stick with fremantle for the touch apps
<joerg>
yes, I had display artifacts as well, green lines and garbled display
<joerg>
afk, cya
<Daanct12>
cya, gn
<tmlind>
mighty17[m]: yeah so if you add a new driver, you should also add yourself to the maintainers file, that's a separate patch
<tmlind>
mighty17[m]: i'd also stay away from the renames for the same reason as discussed on the list, and additionally they also add extra dependencies for getting your other real changes merged :)
mardy has joined #maemo-leste
adc has joined #maemo-leste
Twig has joined #maemo-leste
Pali has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
pere has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
Pali has quit [Ping timeout: 256 seconds]
pere has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
_uvos_ has joined #maemo-leste
<_uvos_>
Wizzup: more like fix hildons notifiy implementation
<_uvos_>
its there but somehow very broken
<_uvos_>
libnotify clients dont work, but randomly some others do
<_uvos_>
like gpodder
<Wizzup>
_uvos_: hm, it works well in modest it looks like
<Wizzup>
I don't know what specific problem(s) you're referring to
<_uvos_>
hildon implements a interface with xdgs notify names
<_uvos_>
but they dont behave right
<_uvos_>
breaking spec apps
<_uvos_>
also not everything is implemented at all
<_uvos_>
even for the earliest spec
<_uvos_>
modest probubly dose special things to get it to work
<_uvos_>
but as stated some desktop apps also work
<_uvos_>
like gpodder
<Wizzup>
it looked like hildon_banner_show_information would do it
<Wizzup>
yeah sure it does special things
<_uvos_>
well fixing the xdg interface would bring more joy
<_uvos_>
and would ot only make sphone work
<_uvos_>
*not
<Wizzup>
it's not the banner btw, let me find some other examples
<_uvos_>
i know
<_uvos_>
try gpodder
<_uvos_>
it dose a persitant xdg notification
<Wizzup>
so the gpodder window turns yellow?
<_uvos_>
that dose work
<Wizzup>
in the overview?
<_uvos_>
no but it gets a special window and blue hildon button and so on
<_uvos_>
and it uses the xdg interface
<_uvos_>
useing the same interface via libnotify is broken
<_uvos_>
and i tried driveing it via dbus-send and its quite broken
<Wizzup>
I think h-d implements an interface that works, but probably not the new one
<Wizzup>
I confirmed the maemo one works for sure
<_uvos_>
it also implements the generic one
<_uvos_>
sorta
<_uvos_>
imo i proving that makes more sense than pushing the nih one
<_uvos_>
*improving
<Wizzup>
the 'nih' one did work fine for over 10 years
<Wizzup>
if it's functionally the same, then sure, it makes sense
<Wizzup>
if it's not functionally the same then that's a problem
Daanct12 has quit [Remote host closed the connection]
mardy has quit [Ping timeout: 256 seconds]
mardy has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
mardy has joined #maemo-leste
Livio has quit [Ping timeout: 252 seconds]
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
<freemangordon>
_uvos_: I think hildon implements correctly the reported version
<freemangordon>
maybe we shall implement newer version, but that's another story
<freemangordon>
BTW, this is not that bad idea, I may work on that
<freemangordon>
it should be relatively easy for implementation
<freemangordon>
so, I think those that are broken, just assume the implemented specs version, without verifying
<freemangordon>
might be wrong though
<freemangordon>
_uvos_: could you point me to what exactly libnotify call is broke?
<freemangordon>
*broken
<freemangordon>
maybe I shall just use libnotify tests
<freemangordon>
and compare ubuntu<->leste
pere has joined #maemo-leste
pere has quit [Ping timeout: 248 seconds]
Twig has quit [Ping timeout: 256 seconds]
Livio has quit [Ping timeout: 268 seconds]
xmn has joined #maemo-leste
<Wizzup>
freemangordon: right but for example the yellow window indication something happened
<Wizzup>
freemangordon: sphone doesn't even keep a window open for it
<Wizzup>
so I don't think that relates to h-d implementing some notifications
<freemangordon>
Wizzup: you mean that sphone doesn't have visible window?
<freemangordon>
I don;t think it is necessary
<freemangordon>
like, it might assume that notification server implements "actions" or somesuch
<freemangordon>
see, I am not saying that hildon is at fault
<freemangordon>
do you know shpone code that calls libnotify?
<freemangordon>
do you know which code is that
<freemangordon>
umm...
<freemangordon>
I don;t think sphone uses libnotify at all
<Wizzup>
freemangordon: I think to see a missed call there needs to be a window showing you missed one
<Wizzup>
no?
<freemangordon>
sure
<freemangordon>
but that window is created by hildon itsel
<freemangordon>
itself
<freemangordon>
you just need to tell hildon to show it :)
norayr has left #maemo-leste [Error from remote client]
Livio has quit [Ping timeout: 268 seconds]
vagag has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
_uvos_ has quit [Ping timeout: 248 seconds]
<Wizzup>
uvos: I reported earlier that I can see the timeouts work
<Wizzup>
uvos: one or two days ago
<Wizzup>
uvos: btw there's the rtcom branch for sphone when you have some time
Livio has quit [Ping timeout: 256 seconds]
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 256 seconds]
<freemangordon>
uvos: I am almost sure v1.0 of the interface is implemented correctly. I f you find a bug, please LMK how to repro
<freemangordon>
and I'll fix it
<freemangordon>
and I think it is more productive to be more precise, like, instead of saying "Nokians are stupid, hildon is FUBAR and the end of the is near", just explain what exactly does not work or file an issue
<freemangordon>
*the end of the world
<Wizzup>
well there's many bugs, it is hard to always be precise :)
<freemangordon>
agree
<freemangordon>
anyway, re libnotify - I will start executing all of its tests on leste and fix/implement whatever needed
<freemangordon>
that spec is not really a rocket science
<freemangordon>
also, what are those "known problems in systemui"? They are not known to me, otherwise I would have already fixed them. Could you file issues?
<freemangordon>
and assign them to me
_uvos_ has joined #maemo-leste
<_uvos_>
Wizzup: with the date
<_uvos_>
sphone just takes the date that ofono provides
<_uvos_>
maybe something is wrong specifcily with missed calles
<_uvos_>
ofono likely logs/can be set to log calls itself
<_uvos_>
that would be helpfull to see where the issue is comeing from
<Wizzup>
_uvos_: are you seeing the same?
norayr has joined #maemo-leste
Livio has quit [Ping timeout: 248 seconds]
vagag has left #maemo-leste [Error from remote client]