sunshavi has quit [Remote host closed the connection]
sunshavi has joined #maemo-leste
belcher has quit [Ping timeout: 252 seconds]
belcher has joined #maemo-leste
<freemangordon>
parazyd: which license?
<freemangordon>
not sure about the email, lets see who is going to maintain the translations on weblate
xmn has quit [Quit: ZZZzzz…]
xmn has joined #maemo-leste
<freemangordon>
though I guess you can put yours there
<parazyd>
Yeah, fine already with having mine.
<parazyd>
freemangordon: Lucenses for translations. Weblate wants us to set one, and maybe it'd make sense for us to have it in the repo too
<tmlind>
Wizzup: try with modprobe n_gsm debug=0xff, and leave gpsd running with some client, if you see packet messages in dmesg, it means gps hardware is still feeding data
<tmlind>
Wizzup: also some versions of gpsd had a bug where only one client could be opened or the output would hang
<tmlind>
that finally got fixed maybe 1 or 1.5 years ago in gpsd, sorry don't know what fixed it
<parazyd>
We have 3.20 in Leste
<parazyd>
That bug is fixed
<parazyd>
freemangordon: I compiled all the translations packages, and updated my VM. Seems good :)
<Entitlement>
parazyd - [ GitHub - maemo-leste-upstream-forks/pkg-gpsd: Packaging of gpsd for Debian ]
<tmlind>
hmm sorry not sure gpsd 3.20 has the bug fixed, it's easy to verify though: start gpsd, start gpspipe -r and wait until you see data, then start another gpspipe -r and there's no data except for the initial header
<tmlind>
i guess the test with maemo is: open maep and wait until you get connected, then rung gpspipe -r in a terminal
<parazyd>
Wizzup: ^
<parazyd>
Good to know.
<parazyd>
With liblocation we actually do have a single client all the time.
<parazyd>
We shouldn't have an issue with updating to 3.21 btw
<tmlind>
there's nothing like a flakey gps when you need it :)
<tmlind>
heh the first time i tried using d4 with gpsd few years ago.. there were too many mosquitoes and and fresh bear tracks in the moss so i gave up on reloading the modules and restarting gpsd etc that was needed back then :)
<uvos_>
a more sane aproche would be for someone to bisect the pvr traces no?
<Wizzup>
uvos_: yes, this is independent of the pvr stuff, though
<Wizzup>
uvos_: for example even just being able to log all modem traffic (which can be spammy) is helpful
<uvos_>
true
<uvos_>
but maybe the traces _should_ be annoying so that someone looks at it :P
<Wizzup>
I cannot do this much as once, I'm trying to wrap up things rather than jump from thing to thing
<Wizzup>
(not finishing them in the process :p )
diejuse11 has joined #maemo-leste
<diejuse11>
does anyone know how can I get "sudo" running for an user inside chroot?
<parazyd>
diejuse11: What's the current problem?
<sicelo>
journalctl (for logs) :-p
<parazyd>
Never! :D
<diejuse11>
I am chrooting Maemo on Android. I can enter like root or like user, but when I enter like user I can't to do "sudo" because I get "sudo: effective uid is not 0, is sudo installed setuid root? "
<parazyd>
So chmod u+s path/to/sudo/binary
<parazyd>
And check it's owned by root
<diejuse11>
It is "s" already
<diejuse11>
It is owned by root too
<parazyd>
Then perhaps Android is blocking you
<uvos_>
selinux
<diejuse11>
I am looking for ways
<diejuse11>
No luck at the moment
<uvos_>
android runs selinux
<parazyd>
Why do you need sudo though?
<sicelo>
parazyd: lol, but it natively does what Wizzup wants to do ;-)
<diejuse11>
Because I want to be able to use Maemo like user too, and install apps with sudo
<Wizzup>
sicelo: syslog-ng can do the same thing
<Wizzup>
parazyd: I mean we rely on sudo to work in maemo
<parazyd>
diejuse11: Then as uvos_ says you should look into selinux on Android and find out if you can either make an exception or, not recommended, disable it.
<diejuse11>
I know that apps like "Linux Deploy" get "sudo" usable for no root users
<diejuse11>
So it should be possible and not hard
<diejuse11>
By the way, I've already gotten the sound to work.
<diejuse11>
Now I am trying to install apps with the GUI
<diejuse11>
Video running Maemo Leste on Android will be soon
<Wizzup>
sweet :)
<diejuse11>
I am going fastly step by step
<Wizzup>
great, please keep documentation around :)
<diejuse11>
And now I need to remove errors when I try to install apps with GUI
<Entitlement>
Wizzup - [ hildon-home doesn't show the "Add widget" button upon installation of the first ... ]
<diejuse1>
mmm I hadn't seen it and I think that restarting
<Wizzup>
calendar widget maybe?
<diejuse1>
uvos. I think that is a good idea
<uvos_>
Wizzup: the calendar widget has to manny dependancies imo
<uvos_>
Wizzup: the shell command widget thingy is maybe a good candidate
<Wizzup>
I mean we ship qalendar as well
<diejuse1>
Wizzup, Uvos: I restaret
<diejuse1>
and works!
<diejuse1>
one more thing
<uvos_>
oh we do
<uvos_>
ok calendar widget is fine then
<diejuse1>
btw I am using Galaxy Fold 2
<diejuse1>
I say it in case you have any curiosity
inky has joined #maemo-leste
<Wizzup>
neat
<diejuse1>
mmm it crash some time when I add events to calendar
<diejuse1>
and all shortcut icons dissappear
<Wizzup>
sounds like hildon-home crashing
<diejuse1>
yes
<diejuse1>
crash and widget is not there when restarting
diejuse1_ has joined #maemo-leste
diejuse1 has quit [Ping timeout: 240 seconds]
<Wizzup>
diejuse1_: surprising, haven't seen that yet
<Wizzup>
it might relate to your environment, does stuff run as 'user' ?
diejuse1_ has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
<diejuse1>
Wizzup: no, it crashed being root
jonsger has joined #maemo-leste
<Wizzup>
do you have qalendar as well?
<freemangordon>
hmm, I am not sure running hildon-home as root is a good idea
<uvos_>
i mean it should not crash
<diejuse1>
I have calendar too
<diejuse1>
mmm I crash using "user" too. But not the first time, it crash the second time I touch it
xmn has quit [Ping timeout: 240 seconds]
<freemangordon>
diejuse1: any chance to get gdb backtrace or a coredump?
<diejuse1>
what folder to keep the information about the home shortcut and widgets?
<diejuse1>
freemangordon: I will have to check it
xmn has joined #maemo-leste
diejuse1 has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
<Wizzup>
uvos_: right, but some env vars or other things being different may cause it to take less tested codepaths
diejuse1 has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
<Wizzup>
n_gsm=0xff debug doesn't really provide a clue as to why ofono only recognizes the sim after ~100s of uptime
<Wizzup>
maybe there is some leste component doing something
<Wizzup>
hm, no, that should show up too
<uvos_>
Wizzup: the modem takes time to boot
<uvos_>
at least the 4g one dose take a long time
<uvos_>
the 3g modem might too
<Wizzup>
The modem does seem to reply, though, it's just after some time it actually reports on the sim
<uvos_>
that just how it is i think
<uvos_>
on linage os
<uvos_>
the system will boot
<uvos_>
and the sim will only apear after some time
<uvos_>
after android has allready finished booting
diejuse1 has quit [Read error: Connection reset by peer]
<Wizzup>
what is also weird is that it doesn't look like ofono asks for the sim info, it just ... gets it
<Wizzup>
but this doesn't work if ofono is never rebooted
<Wizzup>
s/rebooted/restarted/ on boot
<Wizzup>
and this only happens for sim with a pin, I think
* Wizzup
reboots d4 again
diejuse1 has joined #maemo-leste
<uvos_>
Wizzup: on android too
<Wizzup>
uvos_: well, how does android ever see your sim card with a pin?
<uvos_>
hmm?
<Wizzup>
ah, this time around 162s uptime the sim messages came
<Wizzup>
but ofono doesn't respond to them
<Wizzup>
interesting
<Wizzup>
uvos_: what I am understanding now is that a few things are going on:
<Wizzup>
1. the sim information comes from the modem pretty late, as late as 2.5minutes after booting the phone
<Wizzup>
2. ofono does not pick up on this info in some instances, the ofono started as part of normal boot procedure never does, at least if the sim has a pin
<uvos_>
right that you can repo on android
<Wizzup>
that is, now I see:
<Wizzup>
May 7 20:21:29 localhost kernel: [ 162.369750] gsd_receive_buf: 00000000: f9 2b ef f7 55 30 30 30 32 7e 2b 4d 53 49 4d 3d .+..U0002~+MSIM=
<Wizzup>
this presents problems for the way we do pin entry though
<Wizzup>
we do pinentry as part of the boot process
<uvos_>
thats not great anyhow
<Wizzup>
so if the modem much later just kind of realises it has a sim, that means our startup-pin-query has already run and decided there was nothing to be done
<uvos_>
you can hotswap sims on some phones
<Wizzup>
well, fine, but that's a new thing (tm) :)
<uvos_>
sure
<uvos_>
im just saying it might be worth it to just change how this works
<Wizzup>
uvos_: do we have a page somewhere on d4 modem hacking, or is that to be found elsewhere?
panzeroceania has quit [Read error: Connection reset by peer]
<Wizzup>
like, iirc you dissected some part of the firmware, found some source online, that kind of stuff
panzeroceania has joined #maemo-leste
diejuse1 has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
diejuse1 has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
diejuse1 has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
diejuse1 has quit [Read error: Connection reset by peer]
inky has quit [Ping timeout: 240 seconds]
<uvos_>
no not atm
inky has joined #maemo-leste
inky has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
diejuse1_ has joined #maemo-leste
diejuse1 has quit [Ping timeout: 252 seconds]
diejuse1_ has quit [Read error: Connection reset by peer]
diejuse1 has joined #maemo-leste
inky has joined #maemo-leste
diejuse1_ has joined #maemo-leste
diejuse1_ has quit [Quit: -a- Connection Timed Out]
<inky>
when you add something to the distribution, let's say if you add a phone caller, or mail client modest, will people get the client with updates automatically, or they need to know and add the programs manually?
<uvos_>
depends, when the dialer lands surely yes
<uvos_>
other programs no
<uvos_>
btw i modifyed the ui of trojita a bit and made it use thumb scrolling
<uvos_>
it works mostly ok, but some more work is to be done on the ui