<Wizzup>
so this is likely not your problem, but the ' &' at the end could make it so that dbus isn't started before other maemo programs that need dbus start
<Wizzup>
it looks like you're indeed already touching the softlevel file
<diejuse>
"env | grep DBUS" => Nothing
<Wizzup>
can you check if dbus is running at all, with ps?
<Wizzup>
'ps xua | grep dbus'
<Wizzup>
same for 'ps xua | grep maemo'
<Wizzup>
see if maemo-launcher is running
<diejuse>
Without & no working. The same.
<Wizzup>
yes, that won't make all the difference, it will not continue with starting the other tools
<Wizzup>
you'll eventually need something more complicated than this, like run-parts on the xsession files or so
<diejuse>
'ps xua | grep dbus' => Error /proc must be mounted. And this is the real problem that I mentioned before. In modern versions of Android /proc /sys is not mounted with proot. However, with older Android versions (like 7) yes.
<diejuse>
proc not mounted is the key
<Wizzup>
that is a big problem
<diejuse>
I will focus on investigating some workaround to mount /proc with proot.
<diejuse>
And in the meantime I would like you to find some way to start Maemo apps without calling dbus. As we said before.
<diejuse>
The good thing about proot vs chroot is that all Android phones, new and old, could use Maemo Leste (non-native). It would be good. People don't usually root their smartphones and everyone could easily try it.
<diejuse>
Yes. It would be the best. But it is easy that nothing can be done to avoid the new restrictions on Android smartphones of new versions. That's why I'm also interested in some workaround to start those Maemo apps.
<Wizzup>
well, you won't be able to run/use maemo without dbus
<Wizzup>
almost everything depends on it
<Wizzup>
like, if you wanted to have the useful instant messaging features, it won't work
<Wizzup>
or the virtual keyboard, won't work
<Wizzup>
it's all dbus
<diejuse>
I understand. And why does the dbus that starts xfce4 in Devuan work?
<gnarface>
most likely they've patched it
<gnarface>
well, actually they've absolutely certainly patched it, but my guess is that most likely the patch is why it works
<gnarface>
(didn't read the whole scrollback, but dbus is definitely one of the few debian packages that devuan has forked)
<gnarface>
(they all have "devuan" in the version string on the package)
<diejuse>
Can't the dbus that Maemo uses have the same benefits as the dbus that is used to start other distros like xfce4 or lxde?
<Wizzup>
but really like I said, you'd just need something that executes everything maemo session needs, plus some of the init scripts
<diejuse>
I just tried "dbus-launch --exit-with-session launchMaemo.sh" but the result is the same.
<diejuse>
Yes. It would be the best. But it would also be nice if the Maemo graphical environment could be started with "dbus-launch" in the same way as the most popular desktops (xfce4, lxde, mate...)
<Wizzup>
not everything in maemo is part of a session, like icd2
<Wizzup>
also note that your launch maemo starts dbus twice more:
joerg has quit [Quit: this shouldn't have happened... ever]
joerg has joined #maemo-leste
antranigv has joined #maemo-leste
<Wizzup>
uvos: I pushed to the sphone mr, split out the spelling fixes as you asked, and added a commit to change the formatting, if you like the formatting (it is what you asked), then I will merge it into the main commit
diejuse has quit [Quit: Client closed]
joerg has quit [Quit: this shouldn't have happened... ever]
joerg has joined #maemo-leste
diejuse has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
mn3monic1 has joined #maemo-leste
f__ has joined #maemo-leste
Elektra has joined #maemo-leste
Elektra is now known as Guest744
eloy_ has joined #maemo-leste
Langoor_ has joined #maemo-leste
asriel has joined #maemo-leste
Guest744 is now known as Elektra
Elektra has quit [Changing host]
Elektra has joined #maemo-leste
parazyd1 has joined #maemo-leste
ashley has quit [Killed (NickServ (GHOST command used by Elektra))]
Elektra is now known as ashley
ungeskriptet6 has joined #maemo-leste
f__ is now known as funderscore
f_ has quit [Ping timeout: 264 seconds]
asrieldreemurr has quit [Ping timeout: 264 seconds]
parazyd has quit [Ping timeout: 264 seconds]
mn3monic has quit [Ping timeout: 264 seconds]
sunshavi_ has quit [Ping timeout: 264 seconds]
slep has quit [Ping timeout: 264 seconds]
eloy has quit [Ping timeout: 264 seconds]
Langoor has quit [Ping timeout: 264 seconds]
mn3monic1 is now known as mn3monic
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet has joined #maemo-leste
funderscore is now known as f_
ungeskriptet6 has quit [Ping timeout: 268 seconds]
synapse has quit [Ping timeout: 256 seconds]
inky has joined #maemo-leste
synapse has joined #maemo-leste
slep has joined #maemo-leste
pere has joined #maemo-leste
parazyd1 is now known as parazyd
parazyd has quit [Quit: parazyd]
parazyd has joined #maemo-leste
diejuse has quit [Quit: Client closed]
pere has quit [Ping timeout: 264 seconds]
ceene has quit [Ping timeout: 260 seconds]
anon777 has quit [Quit: Client closed]
anon777 has joined #maemo-leste
anon777 has quit [Quit: Client closed]
anon777 has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
Wizzup: thank you
<uvos>
Wizzup: so whats the status on this on generall, functionality wise
<uvos>
otherwise it looks ok now code wise, the extern "C" thing is just unessecary, please tell me if it failed to compile without it, that just means i forgot to do this in one of the headers
<uvos>
if you dont have any further concerns i would merge it now, besides the config changes that i would like for you to remove from the pr so that we can first merge it in a default disabled state so that it may be tested by simply loading it
<Wizzup>
uvos: I will fix the extern stuff, I'll fix the config comments yeah, and regarding the current state, I need to test it once more, but regular calls should work fine
<Wizzup>
sip/xmpp calls I've never had working with audio but i mostly tested on my vm
<uvos>
ok
<uvos>
well in default disabled state it cant hurt anyone
<uvos>
this way we can test it a bit and enable it in leste-config later
<Wizzup>
agreed
<Wizzup>
I'll make the changes today, I was fighting this usb modem for two hours and gave up, so I will test on my d4 instead
<Wizzup>
(fighting to test the new code)
<uvos>
ok, no rush
<uvos>
i have some other code for sphone i want to put in the same release
<uvos>
(instmod and rmmod for running sphone)
<Wizzup>
uvos: ok, I made the changes, now testing on my d4
<Wizzup>
uvos: the debian/control entry will need to be modified to get some -dev pkg and perhaps a recommends on the voicecallmgr package
<uvos>
one sneaky extern C still lurking in voicecallmanager.h
<Wizzup>
ah ok
<Wizzup>
I did grep extern *.cpp
<Wizzup>
so yeah
<Wizzup>
:D
<uvos>
yeah i think we need to change how this works generally
<uvos>
so rn sphone depends on things it dosent really need at run time only at build time.
<bencoh>
hmm ... silly question, but are you removing extern C from headers? if so, why?
<uvos>
these things should be required at build time and optional at runtime
<uvos>
bencoh: this is a c++ header
<bencoh>
ah
juiceme_ has joined #maemo-leste
juiceme has quit [Ping timeout: 268 seconds]
<Wizzup>
uvos: yeah some things to fix still:
<Wizzup>
sphone: faled to load module comm-voicecallmanager: missing symbol sphone_module_init
<uvos>
oh right shit im an idiot
<uvos>
that extern c was needed since sphone_module_init and exit is looked up by symbol name
<Wizzup>
you want the extern "C" stuff back in the header?
<uvos>
the others are passed by function pointer
<uvos>
no just around the ones that are looked up by symbol name
<uvos>
i presume you are mocing by target later and this can go away?
nela has quit [Ping timeout: 268 seconds]
diejuse has joined #maemo-leste
<Wizzup>
uvos: that can go I think
<Wizzup>
I will remove it too.
<Wizzup>
just remnants of me trying to make cmake work with qt
<Wizzup>
freemangordon: what do you think, should we use fremantle group_uid for our tp logging or use our own
<Wizzup>
huh, actually it looks like it *is* the same...
<Wizzup>
I meant for sms specifically
<Wizzup>
oh no, it is not the same.
<Wizzup>
so on fremantle the group_uid for sms is the last 7 digits of a phone number
<Wizzup>
on leste it's ring/tel/account0-[full phone number here]
<Wizzup>
I don't know why fremantle make it only the last 7 digits, maybe they know something we don't and it's never going to conflict (doubt it), or they tried to save space? I don't know
<Wizzup>
I guess you have the full number anyway in the remote_uid
<Wizzup>
in any case, from my POV the *only* reason to make it like fremantle that I can think of is so that when you import the rtcom el db from fremantle and you continue a sms conversation, it will end up in the same group/window
<Wizzup>
so, fremantle:
<Wizzup>
sqlite> select group_uid from events order by id desc limit 2; 6081360
<Wizzup>
6081360
<Wizzup>
leste (turned some digits into x to anonimise)
<Wizzup>
sqlite> select group_uid from events order by id desc limit 2;
<Wizzup>
ring/tel/account0-+31623xxxxxx
<Wizzup>
ring/tel/account0-+31623xxxxxx
<Wizzup>
maybe this was nokia's way of normalising numbers with and without prefix?
<freemangordon>
I don't think it makes sense to keep ring/tel/account0 in the db
<freemangordon>
this just gets duplicated, no?
<freemangordon>
last 7 digits from the phone number? I guess we shall read a bit
<freemangordon>
to me id does not seem unique
<freemangordon>
*it
<freemangordon>
perhaps it is combined with something else
<Wizzup>
this is how *all* other group ids are apart from sms fwiw
<Wizzup>
and if you have more than one modem, you probably want to know which one was used?
<freemangordon>
no, why do you care?
<freemangordon>
it is conversation with the same person, no?
<bencoh>
isn't group_uid just used as some kind of index to speed up searches?
<Wizzup>
bencoh: it's not just used to speed up, I think
<bencoh>
(not that it really makes any sense in a practical way, but ....)
<freemangordon>
have to run now, sorry
<Wizzup>
freemangordon: I mean I care in the same way that I can have different xmpp accounts messaging the same person
<Wizzup>
they're still different conversations I think
<Wizzup>
bencoh: I think it is used as a GROUP BY as well, I thought that is why it was called group_uid
<Wizzup>
all the code for this is open btw, so we could check, but I think if something has the same group_uid but different say remote_uid, then it will still be grouped together
<bencoh>
in convs you mean?
<Wizzup>
in anything that uses rtcom-eventlogger-ui, but yes, also in conversations since it uses rtcom-eventlogger
<Wizzup>
this is an example ui for rtcom-eventlogger-ui by nokia
<Wizzup>
I was planning to eventually change that function perhaps, but good to know
<uvos>
yeah makes sense
<uvos>
for now it could be the same as ofonos no?
<uvos>
maybe not if sip works
<Wizzup>
freemangordon: bencoh: maybe I should just follow fremantle group_uid for now, since we've been doing that on fremantle for years anyway, can always change it later?
<Wizzup>
sip works, just not with audio yet, but that is not sphone's fault
<uvos>
ok
<uvos>
sip should really be its own backend
<uvos>
ie the module should register 2+
<Wizzup>
it does
<uvos>
oh ok
<uvos>
but not with different shema
<Wizzup>
that might need some work, but sip can also be used to call regular numbers
<uvos>
ok
<Wizzup>
btw, just stating the obvious, but the ofono and voicecallmanager module should not really be active at the same time (they can be, but telepathy-ring will mess with the plain ofono module)
<Wizzup>
in any case I think the pr maybe is ready now?
<uvos>
seams so
<Wizzup>
freemangordon: also the group-uid not just being the phone number is also because a sip number can also call a regular number, for example
<uvos>
Additionally, the module relies on qtvoicecall, which is a (currently
<uvos>
maemo specific) addition to qtvoicecall
<uvos>
i dont grok this
<uvos>
not that this is super important
<Wizzup>
I probably missed a word there
<Wizzup>
I think I exported some functionality of qtvoicecall because they only exported a qml class to talk to qtvoicecall
<uvos>
you get pkg-config as an optional dependancy but then expect it to be there 2 lines later
<uvos>
should be required ofc
<uvos>
or guarded by if
<Wizzup>
check
<Wizzup>
yes please fix if you can
diejuse has joined #maemo-leste
<Wizzup>
uvos: for the rtcom call logging, shall I try to bring that up to my current understanding of how it should look like?
<Wizzup>
(for sphone)
Wizzup has quit [Ping timeout: 252 seconds]
Wizzup has joined #maemo-leste
<diejuse>
Wizzup Dbus working :D
<diejuse>
Fixed
<Wizzup>
great
<Wizzup>
what was the change?
<diejuse>
First I pseudo-mounted some key /proc files with proot. For example from /proc/uptime. That fixed the "/etc/init.d/dbus:50:[:-lt:unexpected operator" error
akossh has quit [Quit: Leaving.]
<Wizzup>
from some googlnig it looks like proot-distro would also create the uptime file
<diejuse>
Second, I checked the /etc/init.d/dbus file (I have knowledge of shell scripting) and made a modification that did the trick. In "start-top-daemon –start –quiet –pidfile $PIDFILE –chuid messagebus:messagebus –exec $DAEMON – –system $PARAMS" you must add "--chuid messagebus" or "--chuid $DAEMONUSER".
<diejuse>
It is the only solution (now) for non-rooted Android phones
<diejuse>
Now there are several things to solve and I ask you for help.
<diejuse>
First of all, portrait rotation (again). I have achieved it. It works fine in Maemo apps but it doesn't work when I open Debian apps (black screen).
<Wizzup>
hm, do maemo apps work in both rotations for you?
<Wizzup>
and how did you achieve it?
<diejuse>
At the end of launchMaemo.sh I have added "sleep 5; dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'portrait' "
<diejuse>
And works
<Wizzup>
okay, so the rotation isn't typically 'permanent' any apps that do not advertise support for portrait mode will get forced back to landscape mode, which might be what is giving you a black screen
<diejuse>
Everything works fine except when I open any Debian app.
<Wizzup>
I think there is a way to force it to stay in portrait, let me try to find it
<Wizzup>
iirc we had orientation lock applet
<diejuse>
Ok. I have installed orientation applet but I don't see changes.
<Wizzup>
you want to go into portrait mode and then activate the lock