joerg has quit [Read error: Connection reset by peer]
joerg has joined #maemo-leste
Oksana has joined #maemo-leste
xmn has joined #maemo-leste
peetah has quit [Ping timeout: 264 seconds]
peetah has joined #maemo-leste
<Wizzup> bencoh: btw, I see this in wpa_supplicant: <3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<Wizzup> bencoh: per nl80211_reg_beacon_hint_event in hostap/src/drivers/driver_nl80211_event.c I assume that actually it does change the regulatory domain based on other beacons
<Wizzup> didn't check it really hard, but wanted to follow up on that
<Wizzup> looks like wpa_supplicant has various sources of regdom info
<Wizzup> see reg_init_str in hostap/wpa_supplicant/events.c
<Wizzup> freemangordon: ^^
<Wizzup> so those beacon hints cause EVENT_CHANNEL_LIST_CHANGED which does seem to change frequencies and such
<Wizzup> so it looks like the "magic" might just work
<Wizzup> of course, we can do more, based on modem status for example.
cockroach has quit [Quit: leaving]
diejuse has quit [Ping timeout: 272 seconds]
pagurus has quit [Ping timeout: 252 seconds]
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 265 seconds]
mardy has joined #maemo-leste
DocScrutinizer has joined #maemo-leste
joerg is now known as Guest1745
DocScrutinizer is now known as joerg
Guest1745 has quit [Ping timeout: 272 seconds]
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
diejuse has joined #maemo-leste
_whitelogger has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
diejuse has joined #maemo-leste
ravelo has joined #maemo-leste
<ravelo> 'lo
Daanct12 has quit [Ping timeout: 264 seconds]
mobian has joined #maemo-leste
mobian has quit [Client Quit]
mobian has joined #maemo-leste
mobian has quit [Client Quit]
<diejuse> Hi, I am trying with ARM instead ARM64. I am trying to chroot Maemo Leste on an old ARM Android Phone. I get many error messages like "failed to get XImage of pixmap". Any clue/help to solve it?
xmn has quit [Quit: ZZZzzz…]
panzeroceania has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
Pali has joined #maemo-leste
pagurus has joined #maemo-leste
<bencoh> Wizzup: oh, interesting
<bencoh> it's really "magic" :)
diejuse has joined #maemo-leste
uvos has joined #maemo-leste
Pali has quit [Ping timeout: 272 seconds]
buZz has quit [Ping timeout: 272 seconds]
Oksana has quit [Ping timeout: 272 seconds]
<uvos> diejuse: sounds more like a 3d driver problem than an x problem per say
Oksana has joined #maemo-leste
<uvos> or bitedness problem even
<Wizzup> uvos: it could be older android not supporting X as well
<diejuse> uvos: however if I open the apps through Xephyr it works and I don't get those messages
<Wizzup> Xephyr might not be accelerated
<diejuse> is there any way to remove Hildon's animations to make it faster?
diejuse has quit [Quit: Leaving.]
<Wizzup> diejuse:: not trivially, no, you won't have a good experience without 3d generally
<inky> diejuse, i don't really understand what you are doing, but would like to. so you have a leste chroot on an android phone. okay. that would work in commandline. then did you use some X surface for android?
diejuse has joined #maemo-leste
buZz has joined #maemo-leste
buZz is now known as Guest4453
diejuse has quit [Quit: Leaving.]
belcher_ has quit [Ping timeout: 272 seconds]
belcher has joined #maemo-leste
diejuse has joined #maemo-leste
belcher has quit [Quit: Leaving]
<diejuse> I use "XSDL XServer" app like X Window System / X11 server
<diejuse> inky
<diejuse> Now I'm testing it on an old mobile, on an Xperia Pro
<diejuse> I want to see if Maemo Leste is usable through the chroot technique on old mobiles.
<diejuse> The script I made for ARM64 does not work at all because it gives me graphical errors when I open the applications. But if I do a workaround using "xephyr" I can get it to work.
cockroach has joined #maemo-leste
<Wizzup> diejuse: so it's likely related to 3D (driver) stuff
<diejuse> Wizzup: It seems to be so. I love Xephyr. I also fixed the drop down menu problem with Xephyr.
<diejuse> The only problem is that the performance drops a bit.
<uvos> diejuse: you are unlikely to have that mutch luck with the pro really
<uvos> a android device that old, what dose it run linux 2.6.x?
<uvos> im kinda supprised glibc still has support for the kernel its running...
<uvos> looks like current glibc needs at least 3.2
<uvos> our glibc is older so maybe it works with 2.6
<uvos> if so your setup will die with the upgrade to debian/devuan 11
<Wizzup> there's always mainlining :)
<diejuse> uvos: When I first entered this channel, you told me that what I was trying was not going to work. Now I will surprise you again. :P
<uvos> heh
<uvos> yeah maybe im overly sceptic
<uvos> but still chroot over ever more ainchent android underpinnings its unsustanable
<diejuse> Firefox and Chromium don't work well on the Xperia Pro but Dillo works quite well.
<diejuse> I will make another video and put documentation.
<uvos> so what kernel is the pro running?
<diejuse> Yes but first I had to update to Android 7 (Lineage OS 14.1)
<uvos> right but lineageos rarely upgrades the kernel
<uvos> they mostly just work with the vendor kernel as long a possible
<uvos> and then drop the device when not
<diejuse> With Android 6 (CyanogenMod 13) it didn't work
<uvos> they dropped a huge amount of devices after 14 for this reason
<uvos> since later android needs a newer kernel
<diejuse> Similarly, I managed to get Maemo to work on a Blackberry Key 1 (Android 7) but it didn't work for me on a Blackberry Priv (Android 6)
<diejuse> uvos: I understand
<uvos> go to settings -> about phone -> android version
<uvos> and tell my "Kernel version" for the devices
<uvos> im curious
<diejuse> one moment
<diejuse> Uvos: Kernel 3.4.0-LX+
<uvos> ok your safe for now :)
<diejuse> >3,2
<diejuse> >3.2
<uvos> barely made it :P
<uvos> what device was what?
<diejuse> hehe
belcher has joined #maemo-leste
<diejuse> the device? Sony Xperia Pro MK16
<diejuse> beauty device with physical keyboard
<diejuse> I bought it second-hand for 30 euros and did several experiments on it.
<diejuse> I have got xperia mini pro sk17 too. Another beauty device.
<Wizzup> uvos: for the record I did chat some more with fmg about the whole wlancond and such, and it does do some sensible things like change wireless power saving state if a voip call is active, and other stuff like that, not yet sure where we could fit that, so we might ultimately need a daemon to manage some of that
<Wizzup> there's no immediate solution required and for now we'll add stuff to libicd-network-wpasupplicant (like power saving etc)
<Wizzup> we'll deal with it once we can make calls and voip calls ;)
<uvos> "whatever manages modem state" still seams like the sane awnser
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #maemo-leste
<uvos> regarding voip, if we do decide to mangage modem state in mce, it allready knows the call state so a module could do this with almost no extra code
<Wizzup> yes, but then mce would have to do all wireless power saving setting
<uvos> we could make a global decission that "power managment is mces job" or something like that if you like
<Wizzup> and then it needs IAP knowledge etc
<uvos> or a seperate modem manager deamon
<Wizzup> It does get a bit messy
<Wizzup> right
<Wizzup> in any case, it's not super relevant now, just wanted to follow up
<Wizzup> and yes, btw, a modem module for mce would be good, to online the modem and such
<uvos> no new modules until we unfork our mces :)
<Wizzup> yeah, yeah ;)
belcher has quit [Quit: Leaving]
belcher has joined #maemo-leste
<uvos> btw im not sure we have to do anything special for voip
<uvos> since kernel has dynamic power-saving and will do latency management based on packet behavior
<uvos> and the old network latancy interface is gohne
<uvos> so you cant tell the kernel anymore that you need real time
<uvos> (and its also not needed anymore)_
<Wizzup> I think 'iw set <dev> power_save on' on n900 will make packet latency go up a _lot_ even when active
<Wizzup> so probably it will be
<uvos> right but the interface that allowed userspace to detemine what latency is acceptable (what wlancond almost certenly used) is gone afaik
<uvos> so you can oly turn dps off
<bencoh> iirc there are 3 mods in maemo5, and two of them are definitely bearable latency-wise
<bencoh> the super-low-power one is a bit harsh (still iirc)
<bencoh> but that's the kind of thing you'll notice if you ssh (or other low-latency activity) anyway
Danct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
<Wizzup> uvos: possible @ power saving granularity
diejuse has quit [Quit: Leaving.]
Guest4453 is now known as buZz
Danct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
xmn has joined #maemo-leste
diejuse has joined #maemo-leste
DocScrutinizer has joined #maemo-leste
joerg has quit [Killed (copper.libera.chat (Nickname regained by services))]
DocScrutinizer is now known as joerg
diejuse has quit [Quit: Leaving.]
uvos has quit [Ping timeout: 245 seconds]
uvos has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
Pali has joined #maemo-leste
<tmlind> Wizzup: hmm i naturally backported the musb breaking pinephone fix to the droid4-pending-v5.10 and later trees too..
<tmlind> so that would explain the reports about usb notworking networking
<uvos> parazyd: ^^^
<tmlind> i'll go push the fix for the fix to all the droid4-pending-v5.10 and later branches
<uvos> we dont need 5.12
<uvos> leste is on 5.10 and 5.11 and non leste use is 5.13
<uvos> for me at least
<tmlind> ok
<tmlind> we really should get m-l kernel working with the ddk-1.17 :(
<uvos> yeah :|
<bencoh> any link to the musb thing?
<bencoh> thanks!
<uvos> tmlind: btw your ttys0 patch + disabling sysreq and disabling kernel consol on serial port makes the boot failures with usb pluged in dissapear
<uvos> so mabye add that patch to the droid4-pending-* branches
<tmlind> uvos: ok cool
<uvos> but the fact that i have to disable kernel console on serial suggests the port is still misbehaveing somehow
<tmlind> yeah..
<uvos> (ie hanging or soemthing)
<tmlind> did you set sysrq to 0 in .config?
<uvos> yeah
<tmlind> hmm
<uvos> but it dont know if its needed
<tmlind> let's wait on that one a bit then
<uvos> that alone was not nessecary
<uvos> or enough rather
<tmlind> yeah
<uvos> i had to also disable the output
<uvos> ok @ wait
<tmlind> parazyd: pushed out updated droid4-pending-v5.10 and droid4-pending-v5.11 to github with latest stable stuff merged in + usb networking fix applied
<tmlind> parazyd: only compile tested those branches, i've been using the usb fix for few days locally though. there was also a trivial charger merge conflict so might be worth testing
<uvos> same here usb fix has been fine on 5.11
<tmlind> ok
<tmlind> uvos: i'll wait on aplying the usb fix to the droid4-pending-v5.13 branch and will just merge in -rc5 that should have the fix
<uvos> tmlind: ok :)
<tmlind> no other users for that branch beyong you and i probably right now :)
<uvos> right :P
<tmlind> uvos: fyi somehow wl12xx produces always a sdio read error on first boot on mz617
<tmlind> uvos: and power key does not get detected by kexecboot
<tmlind> uvos: so i can't select the kexecboot kernel to boot right now..
<uvos> ok ill check it out once Wizzup's package arrives :)
<tmlind> uvos: ok, i don't really have a much of a kernel patch for it yet, just nothing in it really just the compatible
<uvos> thats fine
<tmlind> uvos: will send to you when you get the package, been trying to figure out the lcd panel
<tmlind> the lcd seems to be dsi to a dsi-to-lvds bridge
<uvos> mostly mapphone-common.dtsi (or what the name is) should have it coverd except lcd and some sensor specifics
<uvos> interesing
<uvos> wierd way to do it
<tmlind> something similar is in exynos5250-arndale.dts, hopefully that compatible will work here too
Twig has joined #maemo-leste
<tmlind> it's a toshiba tc358765 that hopefully is very similar to tc358764.c that the mainline kernel driver handles
<tmlind> no idea what the difference between tc358764 and tc358765 is if anybody cares to try to research :)
<uvos> i++ :P
<tmlind> heh
<tmlind> or a typo
<tmlind> or charge more money from a big custome
<tmlind> r
_inky has joined #maemo-leste
Twig has quit [Ping timeout: 272 seconds]
<tmlind> google search produced this answer:
<tmlind> The TC358764 supports panels up to 1366x768, with 24 bits per pixel. The TC358765 supports panels up to 1920x1200, with 18 bits per pixel. Applicable to a range of mobile product platforms such as MIDs, netbooks, smartbooks and eBooks.
inky_ has quit [Ping timeout: 272 seconds]
<tmlind> i guess i need to somehow fix the kexecboot power key for mz617 first
<uvos> the keycode is likey just different
<uvos> check in android
<tmlind> noisy dmesg for v3.0.8 kernel on it shows KEY_POWER debug statements for each press and release..
<uvos> hmm
<uvos> ok thats wierd then
<tmlind> it should be the same cpcap power key as on others
<tmlind> hmm maybe it does not work on xt894 either, let me check
<uvos> it certly works on xt875
<uvos> so kexecboot binary isent totaly broken
<tmlind> you boot to mainline kernel though?
<uvos> but different kernel ofcourse
<uvos> right
<uvos> but ist not a fundamental bug in kexecboot im saying
<tmlind> heh power key won't do anything for xt894 either with kexecboot :) funny nobody noticed
<tmlind> so the keycode must not be KEY_POWER, or it's not advertised as a proper keyboard
<tmlind> hmm there's define VERY_LONG_HOLD_REBOOT, maybe it just needs to be pressed for longer..
Twig has joined #maemo-leste
<tmlind> nope, maybe kexecboot only supports one keyboard or something
<uvos> that would not work on xt875
<uvos> xt875 has power and volume on different devices
<uvos> both work
<uvos> not sure why they used the keyboard matrix for 2 keys btw
<uvos> maybe its just inherited form/so that its the same as xt862 or something
<tmlind> uvos: but xt875 uses mainline kernel with kexecboot, not v3.0.8 kernel
<uvos> tmlind: sure but it still has 2 keyboard event devices
<uvos> and kexeboot picks up both
<uvos> so its not that
<tmlind> uvos: ok
<uvos> btw android there is getevent
<uvos> == evtest
<uvos> (just about)
<uvos> if you have root
<tmlind> ok still have usable android on mz617
<tmlind> so is getevent there built-in?
<uvos> its part of asop
<uvos> dosent enforce that they ship it
<tmlind> ok
<uvos> im booting los on d4
<tmlind> ok
<uvos> goes absolutly crazy with events on d4
<tmlind> does it generate KEY_POWER?
<uvos> i cant red anything
<uvos> the accel is a event device
<uvos> and it totaly swamps everything
<tmlind> heh
<uvos> power goes
<uvos> 001 006b
<uvos> looks like its KEY_END
<tmlind> huh?
<uvos> yeah its KEY_END
<uvos> getevent -lt /dev/input/event2
<uvos> and press power
<tmlind> weird
<uvos> yeah
<uvos> i absolutly hate useing the terminal in los
<uvos> there is no ctrl
<uvos> how grr
<tmlind> ok event3 on mz617 stock android, but KEY_END yeah
<tmlind> ok i'll patch kexecboot for that
<tmlind> userspace tweaks it in android or what?
<uvos> great
<uvos> cant parse
<uvos> what userspace tweaks
<tmlind> hmm no userspace gets run with utagboot though
<uvos> oh the key_end
<tmlind> i'm not seeing KEY_END in the v3.0.8 kernel sources
<uvos> yeah no must be the kernel somehow
<tmlind> for the cpcap driver
<uvos> no idea
<tmlind> weird
xmn has quit [Read error: Connection reset by peer]
<tmlind> uvos: ok pushed out updated droid4-xyboard-kexecboot-2017.11 to github, will email out the patch with your in cc
<tmlind> thanks for helping to debug that one :)
<uvos> you are ofc welcome :)
ravelo has quit [Quit: Connection closed for inactivity]
<tmlind> kexecboot patch sent, detaching from keyboard now, ttyl
inky_ has joined #maemo-leste
_inky has quit [Ping timeout: 264 seconds]
trench has quit [Remote host closed the connection]
inky_ has quit [Ping timeout: 245 seconds]
ravelo has joined #maemo-leste
inky_ has joined #maemo-leste
Twig has quit [Remote host closed the connection]
<parazyd> tmlind, uvos: Thanks for the notification for the patch
<parazyd> I'll get it ready soon
diejuse has joined #maemo-leste
dreamer has quit [Ping timeout: 264 seconds]
dreamer has joined #maemo-leste
diejuse1 has joined #maemo-leste
diejuse has quit [Read error: Connection reset by peer]
mardy has quit [Quit: WeeChat 2.8]
ajr has joined #maemo-leste
diejuse1 has quit [Quit: Leaving.]
uvos has quit [Ping timeout: 252 seconds]
diejuse has joined #maemo-leste
ravelo has quit [Quit: Connection closed for inactivity]
xmn has joined #maemo-leste
buZz has quit [Quit: Reconnecting]
buZz has joined #maemo-leste
mrtux has quit [Changing host]
mrtux has joined #maemo-leste