Pali has quit [Quit: Pali]
thunderysteak has quit [Ping timeout: 260 seconds]
joerg has quit [Ping timeout: 260 seconds]
joerg has joined #maemo-leste
Twig has joined #maemo-leste
mardy has joined #maemo-leste
xmn has quit [Ping timeout: 272 seconds]
xmn_ has joined #maemo-leste
alex1216 has joined #maemo-leste
crab has quit [Read error: Connection reset by peer]
crab has joined #maemo-leste
<Wizzup> uvos: android doesn't do a lot of suspend? I thought it did
xmn_ has quit [Ping timeout: 272 seconds]
Pali has joined #maemo-leste
thunderysteak has joined #maemo-leste
akossh has joined #maemo-leste
<sicelo> anyone about? i am probably having a pebkac moment, but i can't find where `up_exported_device_get_battery_level` is defined in upower source code
<sicelo> if you can help me find where it's defined, since i'd like to know how it finds battery level
norayr has left #maemo-leste [Error from remote client]
akossh has quit [Quit: Leaving.]
akossh has joined #maemo-leste
thunderysteak has quit [Ping timeout: 252 seconds]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #maemo-leste
norayr has joined #maemo-leste
doc|home has quit [Ping timeout: 268 seconds]
<norayr> my droid4 with this battery also cannot charge it if it is very low.
<norayr> usually when it started it was able to enter charge mode and light up a green led. with these two btteries it maanages to even start hildon but doesnt start to charge anymore.
<norayr> i dont know if both batteries are bd or something changed in maemo.
<norayr> then hildon shuts down because the battery is low
<norayr> i managed to somehow make it to charge, accidentally. i tried to halt the phone during boot process to not deplete the battery and somehow green led slappeared and the screen showed a battery with very low level. i thought thats yastboot or something not maemo and not linux but after half an hour i touched it again
<norayr> and it continued to boot
<norayr> it looks like that battery was drown on framebuffer by linux kernel or maemo, no idea.
<norayr> drawn
<Wizzup> 12 days uptime on my d4 :)
<Wizzup> (with 6.1)
<sicelo> lucky. mine just shutdown a few minutes after being connected on charger yesterday
<Wizzup> hm, I don't think I usually see that
<Wizzup> my reboots have been from the modem oopses fulling up disk and requiring a reboot
xmn has joined #maemo-leste
akossh has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 272 seconds]
akossh has joined #maemo-leste
<sicelo> Wizzup: what did you end up doing about 19:29 26 #maemo-leste Libera
<sicelo> -EPASTE, sorry
<sicelo> seems upower people never replied?
<Wizzup> mhm
<sicelo> :-)
pere has joined #maemo-leste
thunderysteak has joined #maemo-leste
<buZz> norayr: sometimes it helps to disconnect and reconnect usb during powerup
<buZz> the 'battery drawn on framebuffer' is uvos' 'chargemode' thingy
xmn has quit [Ping timeout: 255 seconds]
<buZz> its a whole linux booted, just pressing powerbutton makes it continue
<norayr> buZz, i tried to disconnect and reconnect but it was too slow and the phone would shut down. but i have a pine64 charger, and i managed to turn it shortly off and on via a switch and that helped. maybe i did that to put it to that state i described. i don't remember exactly now.
<norayr> i forgot that i did that, but you reminded me.
<norayr> aha, now i know what is chargemode!
<norayr> maybe it makes sense to enter charge mode even with a better battery. because for me it was able to boot to hildon.
<norayr> but the charging didn't start, and then hildon reported low battery and
<norayr> the phone turned off.
<norayr> so forcing this charge mode somehow would be good. either forcing it or changing its values, because it doesn't enter chrage mode for me. well it entered somehow once.
<sicelo> it goes to charge mode always, if device was turned on by connecting usb cable
<buZz> sicelo: not for me
<buZz> its very unreliable
<buZz> if i -turn on- the phone by USB cable, the phone never detects the USB and boots past chargemode , all the time
<buZz> only if i connect the usb -after- kexecboot, it seems to trigger greenled & USB detection works
<buZz> i suspect it has to do with charger vs actual USB vs just resistors vs usbcondom
<norayr> >it goes to charge mode always, if device was turned on by connecting usb cable
<norayr> hmmm not sure it indeed works always.
<norayr> >only if i connect the usb -after- kexecboot, it seems to trigger greenled & USB detection works
<norayr> ah!
<sicelo> buZz: well i did disable charge mode myself, long ago. but afaik it should just work
uvos has joined #maemo-leste
<uvos> the way mapphones detect charging is racy/broken
<uvos> so this is aknown issue
<buZz> norayr: do you see that repeated for you?
<buZz> uvos: yeah, its not new
<norayr> i will try to make sure i am connecting the cable after kexecboot.
<uvos> buZz: um actually suprised it ever works
<uvos> its just a irq cpcap raises
<uvos> if its raised before the mianline kernel boots i would expect the irq to have been cleared by the android kernel
<uvos> for some reason sometimes it works
<uvos> it really should never work
<buZz> uvos: i feel the data pins are involved
<buZz> somehow ..
<uvos> anyhow freemangordon is rewirteing th usb detect stuff
<uvos> so its not to relevant anymore for long
<norayr> should i try to build for chimaera in phoenix?
<norayr> build with parameters
<norayr> release: extras
<Wizzup> yes please
<norayr> distribution: chimaera?
<norayr> should i replace beowulf with chimaera?
<Wizzup> just replace beowulf with chimaera
<norayr> >ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
<norayr> i think i need to make changes in the repos too.
<norayr> let me remember where there beowulf is mentioned.
<norayr> ah the branch!
<norayr> the branch should be maemo/chimaera probably.
alex1216 has quit [Quit: WeeChat 2.3]
<Wizzup> yes
<norayr> i think this is something i cannot deal with: https://phoenix.maemo.org/job/msid-repos/9/console
<norayr> md5 expected: a0f5d1d951f55234f8b01123370ad767, got: 3af6a70638c98a3165f58bdf786dac00
<norayr> File "pool/main/m/msid/msid_0.4.8.orig.tar.gz" is already registered with different checksums!
<norayr> there is already that file.
<norayr> i can change the tag and/or version of course. but the actual version did not change.
<norayr> should i change changelog?
<norayr> if i have msid (0.4.8-3+leste1) unstable; urgency=low
<norayr> should i change it to msid (0.4.8-4+leste1) unstable; urgency=low ?
<Wizzup> the same happened on jun 30
<norayr> should it be leste2?
<norayr> or i can change the number after the dash?
<norayr> but that would mean also changing changelog?
<Wizzup> I think you might want to increase the version first, and retag
<norayr> hmmm. ok, let it be other version.
<Wizzup> norayr: btw, I think I already did maefat, but thanks for checking it anyway
<norayr> oh!
<norayr> maybe i spoiled it?
<Wizzup> nah it's fine I think?
<Wizzup> norayr: souce pkgs are based on tag
<Wizzup> any time you change source you must make a new tag and new version
<Wizzup> so in this case there is already a 0.4.8 source pkg registered before
<norayr> but i didn't change the source. i only created a new branch.
<Wizzup> and only the amd64 job normally uploads the source
<norayr> and pushed it. and pushed the tag.
<Wizzup> yes, but this was already a problem for beowulf too.
<Wizzup> see my link
<norayr> ok, i'll try to find in the repos, which of my projects you wasn't able to rebuild.
<norayr> to not mess with those you already did.
<norayr> and thanks for doing that btw.
<Wizzup> for example I see that you changed the source without retagging
<Wizzup> norayr: you can see here what I checked :) https://github.com/maemo-leste/bugtracker/issues/644#issuecomment-1344151471
<norayr> let me see, because i believe i did the tag...
<norayr> maybe i did something wrong
<Wizzup> norayr: so:
<Wizzup> (1) you can never re-use a tag, you must increase it and push a new tag, and also in the changelog
<Wizzup> well that's it really, just (1)
<norayr> oh.
<Wizzup> in this case tag 0.4.8 points to commits that aren't even in main
<Wizzup> so there's a chance that the pkgs in the repo actually don't contain all the changes you wanted
<Wizzup> so just tag your HEAD as 0.4.9
<Wizzup> and then add 0.4.9 to the changelog
<Wizzup> or make it 0.4.8.1 if you want
<norayr> oh good, so i'll do photolightmeter, lagrange, leafpad, msid, shermans-aquarium-maemo, live-wallpaper, mstardict.
<norayr> is there a way to upgrade droid4 to chimaera or i should better download a new image and try to sync the home?
<Wizzup> sec.
<Wizzup> norayr: dist-upgrade might work if you do it right
<Wizzup> I can help in an hour or so
<norayr> i'll try. not now, i'll deal with repos now.
<freemangordon> Wizzup: I am still struggling with HAM :)
<freemangordon> but, almost there
<freemangordon> I need to fix that 1px offset that sometimes happens for couple of resolutions
<freemangordon> hopefuly I will fix it in 1-2 days
<Wizzup> freemangordon: heh, it's not that important
<freemangordon> well, I am so close it does not worth to leave it unfinished
<sicelo> oh, btw packages need to be ported to chimaera? when is it planned to release?
* sicelo has a few extras packages to take care of ... hopefully moving them over will be easy
<Wizzup> sicelo: asap :p
pere has quit [Ping timeout: 272 seconds]
mardy has quit [Quit: WeeChat 3.5]
<Wizzup> freemangordon: btw I checked the bluetooth RE work we have to do and it doesn't seesm to be too muc
<Wizzup> h
<Wizzup> connui-bluetooth-status-menu-item.so = 11.1K
<Wizzup> libdialog_bluez.so = 11.9K
<Wizzup> hildon-control-panel/libbtsettings.so = 19.9K
<Wizzup> libdialog_btsearch.so = 8.0K
Twig has quit [Remote host closed the connection]
<Wizzup> that's connui-btsettings and connui-conndlgs-bluetooth and connui-statusbar-bluetooth
<Wizzup> this disregards the obex stuff
<norayr> with mstardict i get this error:
<norayr> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/libgtk-x11-2.0.so: undefined reference to symbol 'g_module_open'
<norayr> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/libgmodule-2.0.so: error adding symbols: DSO missing from command line
<norayr> but the configure.ac is right and contains gmodule-2.0
<norayr> so libtool calls
<norayr> /bin/bash ../libtool --tag=CXX --mode=link x86_64-linux-gnu-g++ -g -O2 -o mstardict conf.o dictmngr.o libwrapper.o mstardict.o prefsdlg.o transwin.o tts.o -Wl,--export-dynamic -lgmodule-2.0 -pthread ...
<Wizzup> uvos: btw I have organicmaps running on my laptop atm
<Wizzup> norayr: please share the full error
<norayr> it seems right, -lgmodule is after .o files...
<norayr> minute
<norayr> this is the important part.
<norayr> for some reason it searches 'g_module_open' in libgtk-x11-2.0.so
<Wizzup> so the problem is absolutely in the order of the -l flags
<norayr> while it should be in libgmodule-2.0.so, and that file exists.
<Wizzup> I think they should be before the object
<Wizzup> files
<norayr> yes in configure.ac, look:
<Wizzup> I've done this a million times and still haven't done it properly
<Wizzup> I mean
<Wizzup> i did it properly
<Wizzup> but I don't remember it properly
<norayr> and it is there in config one time more
<Wizzup> you also need to look at Makefile.a,
<Wizzup> am
<norayr> oh
<Wizzup> I also don't see: AC_SUBST(LIB_STARDICT_LIBS) - don't you need that too?
<norayr> where where?
<norayr> in configure.ac?
<Wizzup> yes
<norayr> there is AC_SUBST(MSTARDICT_LIBS)
<Wizzup> hm
<Wizzup> if you cannot figure it out I can try to fix it
<norayr> there are two PKG_CHECK_MODULES lines, one for MSTARDICT_LIBS and one for MSTARDICT
<norayr> i'll suffer a bit more and pass it to you, will push and then pass.
<Wizzup> it should be simple really, just figure out how come the flags are in the wrong order
<Wizzup> autotools never gets them wrong if you set it up right
<Wizzup> norayr: did you figure it out?
<norayr> noooo
<norayr> ok i pass it to you.
<norayr> mstardict
<norayr> nothing to push actually
<norayr> i don't understand what is happening, why it searches the symbol g_module_open not in libgmodule but in libgtk-x11, and i don't see the problem in the linker line. :/
<Wizzup> norayr: ok
pere has joined #maemo-leste
<Wizzup> norayr: checking
<norayr> i managed to do photolightmeter, lagrange, msid, leafpad
<norayr> thank you
<Wizzup> sweet, checked them off the list
<Wizzup> :)
<norayr> yay!
<Wizzup> norayr: so
<Wizzup> src/Makefile.am
<Wizzup> -mstardict_LDADD = @MSTARDICT_LIBS@ @LIBINTL@ lib/libstardict.a
<Wizzup> +mstardict_LDADD = lib/libstardict.a @MSTARDICT_LIBS@ @LIBINTL@
<Wizzup> this will make it build
<norayr> oh. thank you. i don't understand the logic though, why lib/libstardict.a was causing it there, but okay.
<norayr> i really afraid what i may encounter with shermans-aquarium-maemo, live-wallpaper, and i forgot about 9x9 sudoku.
<norayr> plus you can check off the list oricutron because i never packaged it in the first place, but i will.
<Wizzup> norayr: I won't check it off then :p
<Wizzup> norayr: just ask, happy to help
<norayr> thank you!
<norayr> i spent about 3 days last time with live wallpaper and shermans, there were functions in old gstreamer that did not exist anymore, and almost no documentation, so i hardly figured out which new functions to call instead of old ones.
<Wizzup> darn, sorry to hear it was this hard
<Wizzup> we've done some other gstreamer porting for other packages, so that's often a good resource
<norayr> that was a great experience!
<norayr> good to know, true, that might have helped if i asked.
<Wizzup> freemangordon: ah there is also libconbtui0 :(
uvos has quit [Remote host closed the connection]
<Wizzup> norayr: lmk when mstardict is ready in the repos
<Wizzup> norayr: to be clear I didn't push a fix, just gave the the fix :P
<norayr> ah!
<norayr> ok will do!
<norayr> mstardict built. (:
<Wizzup> great, ty
Pali has quit [Quit: Pali]
elastic_dog has quit [Ping timeout: 265 seconds]
<Wizzup> freemangordon: btw I think you still have to confirm me with the naming of repos you want for chimaera
elastic_dog has joined #maemo-leste
akossh has quit [Quit: Leaving.]
<Wizzup> aaaa
<Wizzup> oops, sry
<norayr> shermans-aquarium-maemo, live-wallpaper are built, 9x9-sudoku is being built, should be fine.
<norayr> were built