diejuse has quit [Quit: Client closed]
ashley has quit [Read error: Connection reset by peer]
ashley has joined #maemo-leste
ashley is now known as Guest9994
Guest9994 is now known as Elektra
Elektra is now known as Guest9240
Guest9240 is now known as NotAKitten
NotAKitten has quit [Changing host]
NotAKitten has joined #maemo-leste
NotAKitten is now known as ashley
xmn has quit [Ping timeout: 264 seconds]
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
fab_ has joined #maemo-leste
ceene has joined #maemo-leste
fab_ has quit [Quit: fab_]
<freemangordon> tmlind: uvos: why is d4 modem using AT interface and not qmi?
Pali has joined #maemo-leste
fab_ has joined #maemo-leste
<tmlind> freemangordon: i could never get the notifications to trigger on qmi, they seem to be forced to uart ts27.010 only
<tmlind> sure if you figure out a way to make things work with qmi that would simplify things :)
<tmlind> seems to be a modem firmware specific configuration
<freemangordon> I see
<tmlind> who knows, maybe the modem configuration could be updated with some commands
<freemangordon> well, either ways we don;t have qmi calls working (in upstream)
<freemangordon> so I will spend some time on it
<tmlind> ok cool. so for now we've been mostly using qmi commands, and just kick the modem on uart pdu notifications so the qmimodem sees the event
<tmlind> let me find the commit for you
<freemangordon> perhaps I should have cc-ed you
<freemangordon> next time
<freemangordon> I guess that should work on d4 as well
<tmlind> ok great
<tmlind> so for kicking the qmimodem on uart notifications, see mot_qmi_trigger_events()
<tmlind> ideally we'd find a way to re-route notifications back to the qmimodem by using some at or qmi commands..
<tmlind> and then plain qmimodem should just work
<freemangordon> and it lacks voice calls suppoer :D
<freemangordon> but, yeah, that's the plan
<freemangordon> will take a while though, I want to finish what I was doing initially before jumping to qmimodem (cpl phone applet)
<tmlind> and i think right now if a qmimodem data connection gets disconnected, qmimodem driver won't notice that and modem consumes extra 80 mW of power until the data connection is shut down
<freemangordon> and then will jump to d4 driver
<tmlind> so at least disconnect notification using mot_qmi_trigger_events() is currently missing and causing poor power consumption when moving around and getting disconnected by the cell network
<tmlind> ok
<freemangordon> oh
<freemangordon> ok, lets save that somewhere
<tmlind> yeah we get some 0 ending uart notfication, but should call mot_qmi_trigger_events()
Pali has quit [Ping timeout: 256 seconds]
<tmlind> so uart knows data got disconnected, qmimodem driver does not
<tmlind> probably easy to reproduce with some tin foil over the phone :)
<freemangordon> already did that when I was playing with signal strength iirc :)
<tmlind> hehe ok :)
<freemangordon> I think it is some 'enable event' command that's missing
<tmlind> ok
<tmlind> it was wizzup who accidentally discovered the mot_qmi_trigger_events() style kick will notfiy the qmimodem btw :)
<tmlind> hmm so i guess one option would be to call mot_qmi_trigger_events() every three seconds when there's an active voice or data connection
<tmlind> or every 10 seconds, then qmimodem should behave
<tmlind> it would not help with incoming sms or voice calls though
<freemangordon> my bigger concern is what to do with qmimodem voice patches that float around inet
<tmlind> possibly we could also have the kernel serdev driver notify kernel qmi on any events..
<tmlind> weird that the qmimodem voice patches are not merged
<freemangordon> mhm
<freemangordon> maybe they were never sent
<tmlind> yeah maybe, wasn't there some mailing list change over the past few years or something?
<freemangordon> I see them only on pmos gitlab repo
<freemangordon> there was
<tmlind> in any case ofono development stalled pretty much over 10 years ago already it seems :(
<freemangordon> but is very active lately
<tmlind> ok good to hear
<tmlind> nothing stopping you from sending the voice patches though
<tmlind> if the pmos folks don't use ofono, they probably lost interest
<freemangordon> right, that's what sicelo said as well
<freemangordon> what stops me is that I am not sure I'll be able to test them
<tmlind> make a voice call?
<freemangordon> from the VM ;)
<freemangordon> but yeah, will try to
<tmlind> d4 or n900?
<freemangordon> x86_64 VM
<freemangordon> that's what I mostly use for development
<tmlind> heh you could connect over usb to d4 modem from your x86_64 vm :)
<freemangordon> I have EC20 that came with Anakon
<freemangordon> *Anakin
<tmlind> ok
<freemangordon> tmlind: umm, how? like, is this some gadget?
<freemangordon> if that's possible, that'd be great
<tmlind> no.. the d4 firmware bootloader whatever cell testing mode remuxes the qmimodem to the micro-usb
<tmlind> you can do the same from linux too, the code is missing in the phy-cpcap-usb though
<freemangordon> ah, more development :)
<tmlind> let me find the define for it
<freemangordon> I'll pass and just use EC20, all this tiny gaps are vastly distracting me
<freemangordon> *these
<freemangordon> unless it is very easy
<tmlind> yeh np, fyi i think the gpio mux option in phy-cpcap-usb.c is CPCAP_MDM_RX_TX to route the modem to the micro-usb
<freemangordon> ok, thanks
<tmlind> that kind of hints that there must be some way to make the d4 modem behave as qmimodem only
<freemangordon> when it comes to d4 I'll do the development on the device, it is fast enough
<freemangordon> right
<tmlind> maybe the bootloader in that case sends some command to the modem so the notifications are routed to qmimodem
<freemangordon> andoid is using AT notifications as well, right?
<tmlind> hmm or actually, maybe it's some command over uart when android boots
<freemangordon> most-probably
<tmlind> so booting to the bp only mode to android, and adb logcat radio and look at the commands when pc uses a data connection might reveal something
<freemangordon> tmlind: pretend that I have no idea about android :) - what is bp mode?
<freemangordon> maybe uvos or Wizzup can help with this
<tmlind> if you boot to the firmware bootloader menu with vol up and down pressed, theres' an option for bp only mode (base band only i think)
<freemangordon> ah
<tmlind> so if you boot android to bp only mode, then connect d4 to a pc, it shows up as a qmimodem and ttyUSB serial ports
<freemangordon> that sounds great
<freemangordon> lemme try it
<tmlind> hmm but likely adb logcat radio won't work in that case as the micro-usb is routed to the modem..
<tmlind> mainline kernel should have the modem usb id's, assuming they don't change for the bp mode
<freemangordon> ofono recognized that as some AT modem
<tmlind> hehe cool :)
<tmlind> try a qmi voice call and see what happens?
<freemangordon> I can't, in VM this is upstream ofono I use to send patches
<freemangordon> will have to revert to stock first
<tmlind> ok well just add the qmimodem voice patches but not the maemo uart hacks
<freemangordon> but not now, have to run
<tmlind> ok me too, ttyl
<freemangordon> anyway, thanks, will keep you informed
<tmlind> ok thanks
pere has quit [Ping timeout: 264 seconds]
elastic_dog has quit [Ping timeout: 272 seconds]
elastic_dog has joined #maemo-leste
elastic_dog has quit [Excess Flood]
elastic_dog has joined #maemo-leste
pere has joined #maemo-leste
mdz has joined #maemo-leste
sch has joined #maemo-leste
<Wizzup> freemangordon: we use the pinephone, doesn't that use qmi modem for voice calls
<Wizzup> s/use/support/
<freemangordon> yes, PP uses qmimodem, for voice calls, but this is not upstreamed
<Wizzup> isn't that what you're looking for, or?
<Wizzup> maybe I got confused
<freemangordon> it is, but it is not in a shape to be upstreamed
<Wizzup> btw, the modem pass through would be kinda of useful on the d4 too, much like the n900 can pass through it's modem over usb
<Wizzup> freemangordon: right
<freemangordon> ok,
<freemangordon> but I am not going to implement that now :)
<Wizzup> sure
diejuse has joined #maemo-leste
<Wizzup> pavel worked it on a while ago over just usb iirc
<freemangordon> it still uses AT cpommands though
<freemangordon> *commands
<freemangordon> I will try switching to qmi
<Wizzup> hm?
<Wizzup> I think just using qmi over usb is a dead end for d4
<Wizzup> the power usage is completely unacceptable
<freemangordon> ok
<freemangordon> anyway, at least we have something upstreamed
<freemangordon> could you repeat again what is the requirement for moving away from g_at_chat?
<freemangordon> Wizzup: hmm:
<freemangordon> ofono_devinfo_create(modem, 0, "qmimodem", data->device);
<freemangordon> this is what I see in our ofono
<freemangordon> in motmdm_pre_sim() that is
<freemangordon> seems I lack the details on what "the power usage is completely unacceptable" is supposed to mean
<Wizzup> yes, our modem is a mix of qmi over usb and at commands
<Wizzup> I don't remember the details, but tmlind would hopefully
<Wizzup> 'our modem' -> 'our ofo\no modem'
uvos__ has joined #maemo-leste
<uvos__> Ä btw, the modem pass through would be kinda of useful on the d4 too, much like the n900 can pass through it's modem over usbÄ
<uvos__> d4 can do this in hardware
<uvos__> i dont quite remember the details but its one of the options you can choose in fastboot
<uvos__> "seems I lack the details on what "the power usage is completely unacceptable" is supposed to mean" if you use qmi only you need to keep the usb if awake at all time so the modem can send you updates when a call or notification comes in
<uvos__> this has unacceptable power consumption implications
<uvos__> however this dosent mean you need to use the at interface and the gpio irqs for calls as sutch
<uvos__> but you do need to use them to catch the modem telling you theres an event underway so you can wake the qmi interface
<tmlind> uvos__: the usb interface will autoidle though when no traffic so it may not be that bad
<tmlind> here's a broken mz616 32 on ebay btw if anybody wants to buy it for parts, seems to ship only to germany https://www.ebay.com/itm/204346488943
<tmlind> so presumably it has a micro-sd
<tmlind> seems the price is kind of expensive but maybe the seller would take an offer of something lower
<diejuse> Is there a way to open a window in Maemo with scrollbars? Many applications display content that overflows the screen and cannot be accessed. It also happens with apps that overflow content when switching from landscape to portrait mode making them unusable. For example miphoto is not usable in portrait mode.
<diejuse> *mihphoto
<uvos__> nope
xmn has joined #maemo-leste
<uvos__> you could make xorg run in some higher resolution and rescale to the display using randrs transformation matrix
<uvos__> but this would be a very extream solution
<uvos__> and switching would require a reboot
<uvos__> tmlind: 40euro for a broken decade old tablet, insane
diejuse has quit [Quit: Client closed]
<buZz> xrandr itself can also do scaling
<buZz> never really got it to work well, though
<buZz> ah, thats what you said :D randrs
<tmlind> uvos__: maybe make an offer for 10€? :)
<buZz> Wizzup: found a car-mount? :)
<uvos__> buZz: randr is even more correct as randr is the extension in xorg and xrandr is just a cli program the can to be used to speak the client side of the randr protocoll :P
<uvos__> \me pedantic
<buZz> yeah :D
* uvos__ pedantic
<buZz> thanks <3
* buZz likes pedantics
<buZz> uvos__: i want a carmount for droid4 , to mount a droid4 -inside- my 3D printer
<buZz> and run 'klipperscreen' on it, and show interface of printer with touch controls
<buZz> :)
<buZz> maybe even with USBethernet instead of wifi
<uvos__> neat
<uvos__> maybe a mz609 would be even better suited to this task
<buZz> i think it'll be ideal :)
<buZz> i dont know, but for droid4 Wizzup has some 'carmounts'
<buZz> whichever device, i just want to mount it solidly to the frame
<buZz> and i have 2x droid4 here, so why not that :)
peetah has quit [Read error: Connection reset by peer]
peetah has joined #maemo-leste
<Wizzup> you might also be able to 3d print something
<Wizzup> I will have to search for a while, doing some renovation and these aren't accessible
<buZz> Wizzup: there's no real rush
<buZz> just trying to find a project -_- , some IRL emotional crap happened over last months, and i'm still recovering
<buZz> need to find something that grabs my attention away well enough ;)
<buZz> not sure if this would be it though
<dsc_> buZz: what 3d printer do you have?
<buZz> for this project? https://nurdspace.nl/CoreAnet
<buZz> i also have a Malyan M100
<buZz> and at the hackerspace we have ...8? 3d printers, but just 2x Creality Ender3 are hooked up
<dsc_> nice
<tmlind> fyi rebasing the pending mapphone patches on v6.8-rc4 here
<buZz> yeah its pretty
<buZz> current printarea is ~20x30x20cm , but i could increase that in all directions still
<buZz> and superquiet and fast
<tmlind> for a 3d printer use of mz609 with the touchscreen the touchscreen driver remains problematic
<tmlind> uvos__: or did you figure out some recent touchscreen branch for mz609?
<buZz> -most- i want the screen for is just displaying temps etc, but controlling printer from it would be nice yeah
<buZz> i can do it all remotely too, over http
<tmlind> yeah ok
mdz has quit [Ping timeout: 264 seconds]
diejuse has joined #maemo-leste
hexnewbie has quit [Ping timeout: 264 seconds]
hexnewbie has joined #maemo-leste
fab_ has quit [Quit: fab_]
<uvos__> tmlind: oh no i forgot about that
<uvos__> miz61x then
<uvos__> or allwiner tablet
ceene has quit [Ping timeout: 260 seconds]
<tmlind> yeah
<tmlind> pushed out v6.8-rc4 based branches
<tmlind> looks like the console on the lcd issue is still there and needs to be bisected
<tmlind> very lightly tested as always :)
<Wizzup> tmlind: for mz60x, is it just the ts that does not work, or also the lcd?
mdz has joined #maemo-leste
<tmlind> Wizzup: mz617 (and mz615 and mz616) are pretty close to working with mainline, different ts controller
<tmlind> had an oops in the v6.8-rc4 based branch at gsd_receive_buf()
<tmlind> at least got the pstore trace, i disabled the pstore compression option so it's more usable now
<tmlind> gotta go now
slep_ has left #maemo-leste [#maemo-leste]
pere has quit [Ping timeout: 252 seconds]
uvos__ has quit [Ping timeout: 255 seconds]
diejuse has quit [Quit: Client closed]
Pali has joined #maemo-leste
uvos__ has joined #maemo-leste
slep has joined #maemo-leste
fab_ has joined #maemo-leste
Pali has quit [Ping timeout: 272 seconds]
pere has joined #maemo-leste
xmn has quit [Read error: Connection reset by peer]
xmn has joined #maemo-leste
akossh has joined #maemo-leste
vahag has joined #maemo-leste
diejuse has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
diejuse has quit [Quit: Client closed]
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
fab_ has quit [Remote host closed the connection]
diejuse has joined #maemo-leste
fab_ has joined #maemo-leste
diejuse has quit [Quit: Client closed]
diejuse has joined #maemo-leste
pere has joined #maemo-leste
fab_ has quit [Quit: fab_]
akossh has quit [Quit: Leaving.]
mdz has quit [Ping timeout: 252 seconds]
diejuse has quit [Quit: Client closed]
<Oksana> My Fxtec Pro1 is a brick since a problem with Sailfish OS update.
<Oksana> I have been using Nokia 1.3 for a while. Laggy, not-Linux, and no hardware keyboard.
<Oksana> Cosmo Communicator looks attractive, but is pricey even on sale. https://store.planetcom.co.uk/products/cosmo-communicator
<Oksana> Question: does anybody have experience with whether Cosmo Communicator can function as everyday phone while running Linux (such as, Maemo Leste?)?
<Oksana> Or is it more like "Decorative Debian" that cannot access much of the hardware?
<inky> hello, i am not from the team of devs, i contribute sometimes
<Wizzup> I think some of the problems with the cosmo communicator was it's mainline support
<inky> and it looks like it doesn't have mainline support.
<Oksana> Why?.. > Please note that altough it's possible to keep using Linux v3, updating from v3 to v4 using apt is not possible. <
<inky> Wizzup or anyone from the team will answer better. but my understanding they use android kernel. Postmarketos is possible to install to some devices via their pmbootstrap utility to which you provide kernel sources to build. it can be mainline or android sources. maemo only uses mainline.
<inky> and if you are able to run debian, as an extreme case you might be able to convert it to devuan, and then add some repos and install some packages from maemo repos and you'll have maemo? i don't know?
<Oksana> Anyway, Dragonbox Pyra is probably more Linux-friendly out of the box. Don't want to waddle through another "Linux on top of Android kernel" thing where partition might be encrypted.