<emOne>
+"I think i may have worked around the issue by removing the offending paths from the database. (mysql in my case)"
buzzmarshall has joined #libreelec
<emOne>
maybe buzzmarshall knows
<emOne>
^^
<emOne>
he doesn't speak anymore
<emOne>
he lost his voice :(
andy-burns has joined #libreelec
lolek has joined #libreelec
<lolek>
hi
gouchi has quit [Remote host closed the connection]
<lolek>
oblikoamorale: are you here?
<buzzmarshall>
@emOne man i keep missing ya
<emOne>
yes you do buzz
<emOne>
I am about to go too
<emOne>
how are you?
<buzzmarshall>
just got home and was doing my workout and i thought that was you i could see the screem from across the room
<buzzmarshall>
good and yourself
<lolek>
well, do anyone recall any problems with wifi just after starting up libreelec on rpi?
<emOne>
not too bad
<emOne>
same as always
<emOne>
heh,, here we go again .. wifi related issues lolek
<buzzmarshall>
i kept missing you over the weekend as i was here off and on while working on github
<emOne>
no worries
<lolek>
emOne: well
<lolek>
what I can say
<buzzmarshall>
i don't yet havd a rpi4 but will probably get one shortly then i can play as well
<lolek>
well I need some hints so I can start digging
<lolek>
right now it's enough to go to setting and reactivate the connection
<lolek>
so ... what does the reactivation do?
<lolek>
it's just calling systemctl restart networking?
<lolek>
or something else?
<buzzmarshall>
but i have seen a few people having issues
* emOne
has no idea
<emOne>
buzzmarshall: do you know?
<buzzmarshall>
hm... not sure how they go about doing it on the rpi but i would think its gottta restart negotiating the connection
Fenster has quit [Ping timeout: 272 seconds]
<buzzmarshall>
that would invovle a few different things
<lolek>
well ok.. which config of kodi is responsible of handling that ui button then
<emOne>
buzzmarshall: I will talk to you soon. I got to go
<emOne>
see you all later
<buzzmarshall>
but from what i seen others saying it seems like it goes to sleep
emOne has left #libreelec [#libreelec]
<lolek>
well I wanted to just try adding something into autostart.sh
<lolek>
something like stop; sleep(2); start;
<lolek>
just need to know what I need to start/stop
<buzzmarshall>
i would think that lE's control panel probably handles the interface part between kodi and the underlying linux base which is kinda like busybox
<lolek>
is it networking or something else?
<buzzmarshall>
it could be a number of things from dtb settings not quite right
<buzzmarshall>
or maybe its negotiating a speed link that for some reason the box can't hold up to
<buzzmarshall>
so rather then renogiate and drop down in speed maybe the box is just loosing it
<buzzmarshall>
then when you restart it maybe throwing out some garbage from the earlier connection and then working ok
<buzzmarshall>
logs i quess are the 1st place to start
<buzzmarshall>
if you got a usb wifi stick maybe try it and see if the problem carry's over to it as well
<buzzmarshall>
if not then you at least no its confined to the chipset in the device
<lolek>
well I don't have any usb wifi stick.. we're in 2020 man:)
<buzzmarshall>
but if the issue carry's over to a external wifi on usb then its something in the core code someplace
<buzzmarshall>
ya... i get ya
<buzzmarshall>
ive never really looked at LE's control panel to see how its python code works with the underlying system
<lolek>
hmm I can try to find it.. just don't know where to start
<lolek>
so it you have any starting point just drop it on me
<lolek>
cause right now I can also try to check every single file in the /
<buzzmarshall>
what version of LE are you running?
<lolek>
9.2.0
<lolek>
official
<buzzmarshall>
ive just recently got a lot more in depth with LE's current build system and am working on the masters and newest stuff and not really looked much at the current stuff
<buzzmarshall>
is it just LE your having the issue with or is the Android os doing it as well
<lolek>
eee Android?
<lolek>
o.O
<buzzmarshall>
lol... i agree and you won't find it on any of my devices
<buzzmarshall>
but i thought i would ask...lol
<lolek>
erm
<buzzmarshall>
what about any other of the LE forks? have you tried any of them to see if they have the same issue
<lolek>
tbh nope
<lolek>
I've just almost finished setting up the libreelec
<lolek>
and it kind of works
<lolek>
just the problem with wifi
<buzzmarshall>
theres so many differnt things it could be so trying to elimanate stuff
<lolek>
well tbh
<buzzmarshall>
does putting the device closer to the source make any difference?
<lolek>
I'd like to just get it working
<lolek>
erm it's already close.. the signal strength is 70%
<buzzmarshall>
ya you'd think that would ok
<lolek>
well it works :)
<lolek>
let me see something
<buzzmarshall>
so does it work ok and then get slower over time?
<lolek>
right now signal is on -53dBm and noise is -91dBm... speed is 150Mbps rx and tx
<lolek>
so it's very very good
<lolek>
nope it's not getting slower
<lolek>
have there pulseaudio server
<lolek>
was streaming for the whole day.. no problems after I've pushed pulseaudio into realtime mode
<lolek>
so tbh I'd like to just fix this.. using a hack/workaround personaly, doesn't matter
<lolek>
so, do you know where I can look for the ui files?
<buzzmarshall>
in the source code they will be in the LibreELEC Settings package but hangon and let me ssh into a box and see where exactaly ther are siting in the running ssystem
<lolek>
ok great
<lolek>
thanks!
<buzzmarshall>
the service.libreelect.settings on this T95 are sitting in the /usr/share/kodi/addon/service.libreelec.settings directory
<lolek>
yea but there are only pyo files
<lolek>
I need sources
<lolek>
hmm
<lolek>
where's the repo?
<buzzmarshall>
inside that directory you can see all the scripts and stuff as well if you go into the resources/lib dircectory theres a module directory with the modules
<buzzmarshall>
don't for tho when looking at the package.mk file that there maybe other dependencies being brought in as well
<buzzmarshall>
but essentially that whole package is what sets up whatever is in the LibreELEC control panel as i think all of that then runs under the service.xxxx process
<lolek>
hmm
<lolek>
wondering if it would be enough to call systemctl restart conman
<buzzmarshall>
so how its starting things you will glean from it
<buzzmarshall>
maybe
<lolek>
ha
<lolek>
connmanctl
<lolek>
:)
<buzzmarshall>
cool
<lolek>
now I just need to find out what's showing up when it's not working
<lolek>
enable <technology>|offline Enables given technology or offline mode
<lolek>
I think that should last
<lolek>
just don't know what's the "technology" here
<buzzmarshall>
you got me as other then some basic idea of whats where i never actually use wifi so ive not spent much time looking at that package
<lolek>
ok so
<lolek>
connmanctl disable wifi
<lolek>
connmanctl enable wifi
<lolek>
here... this should be enough to take care of this
<lolek>
also doing: connmanctl state
<lolek>
and grep for the wifi state
<lolek>
if it's there proper
<lolek>
should all together do the trick :)
<buzzmarshall>
thats good hopefully you'll find what you need...
<lolek>
ok at least it's some starting point
<buzzmarshall>
wish i could be more help but its just not something ive spent much time looking at
<lolek>
thanks man for your help :)
<lolek>
nah, that's enough
<lolek>
the problem is always to find some starting point
<buzzmarshall>
cool... hey you did the work... im just babbling
<buzzmarshall>
lol
<lolek>
so if you have something to catch up... it's much easier then