02:35 <buZz> are just these the sounds that nokia never released as opensource? https://paste.debian.net/plain/1243396

02:37 <buZz> thats just the contents of osso-sounds-rtc_5.6+0m5_all.deb

06:43 <Wizzup> buZz: yes

06:43 <Wizzup> buZz: there might be more

06:43 <Wizzup> we don't have the rtc ones installed by default I think

10:27 <Wizzup> tmlind: do you remember what you did to get a lower power data connection? iirc it was just using one of the other interfaces?

10:30 <uvos__> wwan2 iirc

10:31 <Wizzup> ok, ofono configs wwan3 for some reason for me

10:32 <Wizzup> I see this in the logs:

10:32 <Wizzup> 19:01 < tmlind> so wwan0, wwan1 for data, wwan2 works only once don't use, use wwan3 for mms

10:32 <Wizzup> 19:00 < uvos> tmlind: we can look at pm when it works

10:32 <Wizzup> 19:02 < tmlind> so again: so wwan0 for qmi and ofono voice, wwan1 for data, wwan2 works only once don't use, use wwan3 for mms

10:32 <Wizzup> so I guess maybe something changed since then

10:32 <Wizzup> bbiab

11:05 <buZz> Wizzup: the -rtc one doesnt seem to be in leste, no

11:17 <tmlind> Wizzup: i use wwan1 for data, don't think i'm really doing anything to make it lower power

11:33 <Wizzup> tmlind: hmm ok, iirc you said you got 2-3 days on a diff iface

11:50 <buZz> i use wwan3 on d4 all the time

11:50 <buZz> also seems to work for very long

13:11 <Wizzup> buZz: like two days?

13:13 <buZz> well , ~1

13:14 <buZz> my battery is just ~900-1000mAh it seems (after a bunch of trainingcycles)

13:15 <Wizzup> yeah, so I'm pretty sure that we can get a (lot) more

13:15 <buZz> more likely ~12-20 hrs

13:15 <buZz> sweet!

13:19 <uvos__> i mean ofc its possible

13:19 <uvos__> android dose like 30-50mW whilest connected

13:19 <buZz> nice

13:21 <uvos__> 1day sounds about right on leste atm

13:21 <uvos__> i get about 2

13:22 <uvos__> with 2Ah battery

13:56 <Wizzup> uvos__: fwiw I've been using the d4 with my hacks for a few days now to call people and it's been great

13:56 <Wizzup> both receiving and making calls

13:58 <uvos__> right goes to show there is very little missing to make the d4's setup work very well

13:58 <uvos__> cpcap/q6600 has really good audio quality too

13:58 <uvos__> could you push this?

14:01 <Wizzup> the hack? yes, I'll work on it today

14:01 <Wizzup> I wanted to add the switching to speaker and headphone first

14:05 <uvos__> Wizzup: how did the d4 alarm do today

14:06 <uvos__> unfortionatly mine worked

14:08 <Wizzup> Mine worked too, but it had no sound, but that's because of my call hacks ;)

14:08 <Wizzup> (the problem is that pa restores it before I restore the regs to before the call, and then pa needs a restart to work)

14:09 <uvos__> not sure why pa would need to restart

14:09 <uvos__> how would it even know the register state

14:09 <uvos__> as long as you restore it to whatever the driver expects

14:09 <Wizzup> well, playback just doesn't resume

14:10 <Wizzup> yeah, I think I know what's up

14:10 <Wizzup> I think what happens is:

14:10 <Wizzup> 1. pa sets mode to call

14:10 <Wizzup> 2. I store current regs, apply reg hacks

14:10 <Wizzup> <call>

14:10 <Wizzup> 3. pa sets mode to hifi

14:10 <Wizzup> 4. I restore to before applying reg hacks

14:10 <Wizzup> my idea was that I could have (4) run before (3)

14:11 <Wizzup> but I can't wiyj the current sphone datapipe stuff mode

14:11 <Wizzup> s/wiyj/with/

14:18 <uvos__> yes i know

14:18 <uvos__> i just dont see how having set the regs pa could end up "knowing" the difference

14:18 <uvos__> regardless of order

14:19 <uvos__> in sphone

14:19 <uvos__> instead of reseting when it asks you to

14:19 <uvos__> nvm

14:19 <uvos__> even better:

14:19 <uvos__> register a trigger and a filter

14:19 <uvos__> the triger you get after pa

14:19 <uvos__> the filter gets it before

14:22 <Wizzup> uvos__: well I guess the problem with above is that it sets it back to call mode :)

14:22 <Wizzup> hm, register a trigger where?

14:22 <uvos__> append_filter_to_datapipe

14:22 <uvos__> you ll allways get this before any triggers

14:23 <uvos__> so you can set it up so the trigger on the route pipe gets it after the pa moudle

14:23 <uvos__> but the filter gets it first

14:23 <Wizzup> hm

14:23 <Wizzup> ok, let me push some of the hacks, but keep in mind I need to clean it up more for sure

14:24 <uvos__> https://github.com/maemo-leste/sphone/blob/master/src/modapi/datapipe.her/src/modapi/datapipe.h

14:24 <Wizzup> that's a 404

14:24 <Wizzup> https://github.com/maemo-leste/sphone/blob/master/src/modapi/datapipe.h

14:25 <uvos__> yeah got mangled somehow

14:28 <Wizzup> going to focus on work for a bit, I think it would make sense to indeed fix this first and then focus on headphone and speakerphone

14:28 <Wizzup> also I have some ucm changes that I'll push at the same time

17:27 <MoepMan[m]> Hi, I have an N900 with a maemo leste install from probably around winter 2020 - apt update followed by apt upgrade will only give me a few devuan updates (and an error wrt to an expired leste key signature) but e.g. no new shiny kernel - what would be the best way to get this system up to date again?

17:28 <Wizzup> you can get the latest testing.key and add it

17:28 <Wizzup> dd'ing the latest image is definitely easier :)

17:29 <MoepMan[m]> so if I don't have any important user data on it I'd just dd the new image onto the SD card and be done with it? i.e. old u-boot entry booting from SD will just work the same with the new image?

17:30 <Wizzup> yes, I think so.