_whitelogger_ has joined #maemo-leste
akossh has quit [Quit: Leaving.]
gnarface has joined #maemo-leste
leste has joined #maemo-leste
n900 has joined #maemo-leste
diejuse has joined #maemo-leste
LjL has quit [Ping timeout: 240 seconds]
LjL has joined #maemo-leste
Guest3123 has joined #maemo-leste
diejuse has quit [Quit: Client closed]
xmn has quit [Ping timeout: 276 seconds]
slep has quit [Quit: Gateway shutdown]
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_]
fab_ has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
diejuse has joined #maemo-leste
sch has joined #maemo-leste
fab_ has quit [Quit: fab_]
diejuse has quit [Quit: Client closed]
xmn has joined #maemo-leste
pere has quit [Ping timeout: 264 seconds]
elastic_dog has quit [Ping timeout: 264 seconds]
pere has joined #maemo-leste
<Wizzup> uvos: ok, I have rooted this d3 with sigmakey now, so I can -finally- proceed
<Wizzup> (also tested, it's network unlocked already)
elastic_dog has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
lolcat has joined #maemo-leste
lolcat has quit [Client Quit]
arno11 has joined #maemo-leste
<arno11> hi guys, i just compared my Fremantle (cssu kernel v53, no thumb2, light transitions, swappiness=30, 500-805MHz) with Leste (same freqs, same transitions, -devel and same swappiness)...and the feeling is pretty similar now :)
<Wizzup> sweet :)
<arno11> the feeling is even better with h-d navigation
<arno11> :)
<Wizzup> I guess we should work on cmt speech integration then
<arno11> yes indeed, i forgot that :P
<Wizzup> uvos: I am wholly impressed by the razr battery life btw
<arno11> for cmtspeech (cmt_pulse as user in fact), i think that 'the not too bad moment to start it' is when pin code entry appears (because we are sure that nokia-modem is already loaded)
<Wizzup> maybe it can somehow only be started when modem is online, and shut off when modem is not online
<arno11> sounds good
<Wizzup> (not sure how to do that ;))
<arno11> ok :)
<arno11> we need chrt prio for PA and sphone as well and we can't use limits.conf for that (only working with rt kernel iirc)
Guest9934 is now known as Elektra
Elektra is now known as Guest7201
<arno11> maybe someone has a magic trick for that
Guest7201 is now known as RogueAdmin
<freemangordon> IIRC you said with PA as user no prio change is needed
<arno11> yes indeed it works
<freemangordon> but?
<arno11> but not very well if you are running other apps at the same time
<freemangordon> I see
RogueAdmin is now known as NotAKitten
NotAKitten has quit [Changing host]
NotAKitten has joined #maemo-leste
NotAKitten is now known as ashley
<freemangordon> can't we add some sudoer.d and call it a day?
<freemangordon> also, maybe we can create a cgroup with higher prio
<arno11> sudoer could work
<arno11> no idea for cgroup
<freemangordon> yeah, but cgroup shall be better
<arno11> yes probably
<freemangordon> Wizzup: ^^^ any idea how to tell elogind to move pid into a cgroup?
<freemangordon> we have /sys/fs/cgroup/elogind already
<Wizzup> freemangordon: the point was not about how to elevate the privs but how to start it at the right time
<freemangordon> I wonder if elogind will be happy if we create session dir subdir and move some processes there
<Wizzup> sorry I don't know much about cgroups
<arno11> Wizzup: we also need to elevate the privs to use chrt (just chrt, no impact on PA or sphone)
<freemangordon> arno11: so, renice does not work?
<arno11> renice is not enough unfortunately
<freemangordon> hmm, how's that?
<freemangordon> so, you set SCHED_FIFO on PA?
<arno11> sched RR
<Wizzup> arno11: this is all easily done with sudo
<Wizzup> we just need to figure out how it gets started
<freemangordon> with sudoer
<Wizzup> freemangordon: if we start it as init script on boot, it won't work
<Wizzup> that's the point
<freemangordon> I understand that
<Wizzup> 15:19 < arno11> for cmtspeech (cmt_pulse as user in fact), i think that 'the not too bad moment to start it' is when pin code entry appears (because we are sure that nokia-modem is already loaded)
<Wizzup> so when I say 'how it gets started' I mean which process actually launches it when the modem is online
<freemangordon> what I am saying is that we can change the prio once the process is started by using sudoer
<arno11> freemangordon: yes
<arno11> best option imo
<freemangordon> arno11: RR ends up as FIFO on linux, afaik
<freemangordon> RR is notr really supported
<freemangordon> (afaik)
<arno11> it seems to work well :P anyway FIFO gives similar results
<freemangordon> did you try DEADLINE?
<Wizzup> uvos: my static cpcaprw with armhf just owrks :)
<freemangordon> Wizzup: why not? as soon as you dont; try to use any FP, you should be fine
<freemangordon> FP as in call annother lib
<freemangordon> arno11: OTOH, during call there is no more impotant task that audio, so yeah...
<freemangordon> *important
<Wizzup> freemangordon: because he said it might not work
<freemangordon> ah
<arno11> freemangordon: didn't try deadline
<Wizzup> uvos: you said this:
<Wizzup> 17:06 < uvos> Wizzup: you can use cpu freq to force the oop
<Wizzup> 17:06 < Wizzup> in android?
<Wizzup> 17:06 < uvos> clowboot dose it in the script even
<Wizzup> 17:06 < uvos> yes
<Wizzup> 17:06 < uvos> just before kexec
<Wizzup> but I don't see it changing the freq anywhere
pere has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__> Wizzup: hmm its, its missing...
<uvos__> not good
<uvos__> here it is in kexecboot (to late in droid3 an bionic
<uvos__> the stock kernel uses totaly normal cpufreq
<uvos__> i also notices another problem...
<uvos__> the droid3 dosent have 1.2ghz oop
<uvos__> since motorola only overclocked the slow omap4 variants with the 4.0 update, which d3 never got
<uvos__> booting at a low opp but then running at full speed might be causing the crashes
<uvos__> since the memory will be stuck in a random opp
sch has quit [Ping timeout: 260 seconds]
<uvos__> then again bionic dosent seem to mind
<uvos__> hmm
<Wizzup> hi
<Wizzup> I made a script to dump the values on android, I'm about to run it now without usb cable attached
<uvos__> please fix the opp to 1.005Mhz or what the top oop was again
<uvos__> and kexec to kexecboot
<Wizzup> there is 300,600,800,1000
<uvos__> before wasteing any time on anything else
<Wizzup> hmmm
<uvos__> oh and limit the max oop in the mainline kernel to the same
<uvos__> we dont want emif to be in a lower oop than the cpu ever
<uvos__> this causes stability issues on d4
<Wizzup> so you want the kexecboot script to set the frequency to 1000 ?
<uvos__> yeah or just kexec from android by hand
<Wizzup> that line alone won't be enough bt\
<Wizzup> w
<Wizzup> let me share my current script
<Wizzup> wait there is a mistake in the script
<Wizzup> lol
<uvos__> oh and not the kexecboot script
<uvos__> you must do it in clownboot before the first kexec
<uvos__> kexecboot is after the first kexec but before the second
<Wizzup> ok, let me figure out how I am going to be able to edit those scripts given that I can't boot to android
<uvos__> just boot to leste recovery shell and use serial?
<Wizzup> if it is stable enough, that might work
<Wizzup> uvos__: how about this: https://bpa.st/FTDQ
<uvos__> otherwise reflash system and reinstall clown-boot
<uvos__> use $BBX ofc
<Wizzup> oh
<Wizzup> the umount -l didn't use $BBX
<uvos__> oh rihgt
<uvos__> yeah after $BBX cp $BBX / bbx is in ramfs
<Wizzup> ok, so /busybox is fine then
<uvos__> since we are about to loose everything else
<uvos__> not sure why you want to do it there, might as well do it earlier
<uvos__> but whatever
<Wizzup> right, don't know, just picked a place where it made sense :)
<uvos__> not sure what the echo and cat is for
<uvos__> the stock kernel has fbconsole disabled
<Wizzup> I was hoping to see it, but just realised I won't
<uvos__> you cant ever possibly see any of this
<Wizzup> to confirm that it actually worked, I mean
<Wizzup> yeah I just realised
<uvos__> and any misake means you have to reflash system
<Wizzup> well it's booting leste atm
<uvos__> this script is very fun to develop
<uvos__> if you do it erlier
<uvos__> before we loose permanent sortage
<uvos__> you can save the output somewhere in system
<Wizzup> right
<uvos__> if you also remount that rw
<uvos__> its ro otherwise
<Wizzup> well, maybe I just toy around in leste for a few minutes, and if it works, then we're done here
<Wizzup> what do you mean with ro/rw, /sys should be rw regardless no?
<Wizzup> oh, right
<uvos__> system on android is ro
<Wizzup> to store the output
<Wizzup> :)
<Wizzup> well, it still reset it looks like
<Wizzup> -- OMAP 00004430 (version 00000b22) PPA release1.3.5 R2
<Wizzup> Reset reason = 000379a2
<Wizzup> PPA hash Block:0x9ff00000 Size:260096 Flag:3
<Wizzup> Model ID is 0x00000003
<uvos__> mbm not happy
<Wizzup> I suppose what I could do is to install just kexecboot without the clown part on the other droid3 that I have, and manually kexec from android
<Wizzup> so make sure it's really in that frequency
<Wizzup> to make sure*
<uvos__> yes
<uvos__> but this is a fun procedure
<uvos__> not
<Wizzup> yeah
<Wizzup> well so I can just run the cpcaprw tool on leste now
<uvos__> because the uart.ko module distroys the serial port
<Wizzup> hm, the d3 also has 1200000 as available freq
<Wizzup> should it?
<uvos__> and then it also breaks usb and wifi
<uvos__> Wizzup: no, yes, maybe
<uvos__> Wizzup: bionic also has the same omap variant (1.0ghz only)
<uvos__> but motora decded 1.2 is fine there
<uvos__> but we tried this allready im sure
<Wizzup> I do remember that we did that, but we did not do it with the freq locked to 1Ghz before kexec
<Wizzup> but if you want maybe I should just run the cpcaprw script now?
<uvos__> sure you can try
<uvos__> its hardly hard
<Wizzup> bbiab
arno11 has left #maemo-leste [#maemo-leste]
fab_ has joined #maemo-leste
uvos__ has quit [Ping timeout: 252 seconds]
uvos__ has joined #maemo-leste
<sicelo> arno11: Wizzup: regarding cmtspeech maybe we can create a wrapper that runs at boot ... so it's a normal openrc/dsme service. this wrapper listens for the appearance of ofono's AudioSettings interface. when that shows up (meaning we have voice-capability ready), the wrapper starts the real cmtspeech.
uvos__ has quit [Ping timeout: 252 seconds]
<sicelo> but i think long term, we may need to fix whatever it is that causes cmtspeech to be sensitive about when it's started (tbh, i am not really sure it is, but i haven't done more extensive tests yet, even though i'd like to)
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 252 seconds]
arno11 has joined #maemo-leste
<arno11> sicelo: hi
<Wizzup> uvos: it does look like locking to 300mhz indeed did not help
<arno11> cmtspeech itself is not a problem on boot
<Wizzup> maybe the best thing to do at this point is to just do the reg dump and compare
<sicelo> ah, i meant to say `cmt_pulse`
<arno11> sicelo: a ok
<arno11> *ah
<Wizzup> so what actually is the problem with starting cmt_speech on boot? it can't find /dev/cmt_speech, or the modem isn't on ofono yet, or?
<arno11> cmtspeech is not the problem it is already loaded on boot
<Wizzup> what I mean is that is cmt_pulse just iterates over the modems on start and then doesn't listen to modem changes, we just fix that
<Wizzup> is that if*
<freemangordon> :nod:
<arno11> iirc cmt_pulse returns errors if the modem, ofono and PA are not already loaded
<freemangordon> what is cmt_pulse?
<freemangordon> sorry for the stupid question, but still
<freemangordon> where is the repo?
<arno11> libcmtspeechdata
<arno11> cmt_pulse is the binary
<freemangordon> who builds that? libcmtspeechdata?
<freemangordon> I can't find it here https://github.com/maemo-leste/libcmtspeechdata
<arno11> ?
<arno11> let me check
<sicelo> freemangordon: yes it's there. utils/pulse.c
<arno11> yup
<freemangordon> oh
<freemangordon> what the? we have Makefile and Makefile.am?!?
<sicelo> lol
<sicelo> fmg, yes it's super ugly code ... i did mention that it should be refactored some day
<arno11> indeed...
<sicelo> anyway, the issue is likely in utils/cmtspeech_ofono_test.c
<freemangordon> so, is that PA module?
<freemangordon> how do you start that?
<freemangordon> I see no main
<freemangordon> main()
<arno11> /usr/bin/cmt_pulse lol
<arno11> that's not a PA module
<sicelo> fmg, i think it's started by utils/cmtspeech_ofono_test.c
<freemangordon> ok
<freemangordon> tha makes sense
<freemangordon> sicelo: please confirm that if possible while I look into the code
<sicelo> i don't have the N900 handy right now
<freemangordon> ok
<Wizzup> the Makefile should tell you I think
<Wizzup> I will check
<freemangordon> arno11: what is the error when it fails?
<Wizzup> utils/pulse.c
<freemangordon> Wizzup: there is no main() in there :)
<freemangordon> at least I can't see it
<Wizzup> right
<sicelo> anyway, the issue is most likely the dbus side of things, i.e. utils/cmtspeech_ofono_test.c:test_dbus_init or main, which calls this function
<Wizzup> sorry I went through the same steps you did
<Wizzup> haha
<freemangordon> :)
<Wizzup> fprintf(stderr, "NFS sucks, version 0.0.1\n");
<Wizzup> pretty sure this is the main
<sicelo> utils/cmtspeech_ofono_test.c lines 166-169 ...
<Wizzup> yes
<freemangordon> ok, but I still need the error message
<Wizzup> sorry, I was just confirming that this is the main
<freemangordon> sicelo: arno11: did you ever tried to start that from xsession script?
<freemangordon> ah, it waits for ofono to initi
<Wizzup> blocking?
<freemangordon> no
<Wizzup> sounds like it should just work then
<freemangordon> and most-probably there is no 'org.ofono.AudioSettings' interface by that time
<freemangordon> and it just fails
<freemangordon> hmm, that should not fail
<freemangordon> arno11: so, how do you start cmt_pulse on startup when it fails?
<sicelo> i also don't believe it should fail, but yeah, i haven't tested that.
<sicelo> and yes, AudioSettings only shows up once the modem is Powered
<freemangordon> dbus_bus_add_match() hardly fails
<freemangordon> so I need details on the failure
<Wizzup> maybe someone can run it from a xsession script and see if it just works
<Wizzup> I'm not sure if we are 100% sure that it actuall fails
<freemangordon> mhm
<arno11> freemangordon: back. sorry, what was your main question ?
<freemangordon> what is the error (message ?) when cmt_pulse fails to start properly
akossh has joined #maemo-leste
<Wizzup> uvos: so how do get the cpcap regs on mainline?
<Wizzup> how do I*
<arno11> freemangordon: ah ok, sorry no time for me now, i'll have a look a bit later
<Wizzup> this is stock android
pere has quit [Ping timeout: 246 seconds]
pere has joined #maemo-leste
Juest has quit [Ping timeout: 252 seconds]
Juest has joined #maemo-leste
ceene has quit [Ping timeout: 260 seconds]
arno11 has quit [Quit: Lost terminal]
arno11 has joined #maemo-leste
<arno11> freemangordon: having a look @irc logs, i didn't remember i successfuly ran cmt_pulse on boot lol...in july
<arno11> using a basic init script
<arno11> adding 'depend() after ofono'
<arno11> apparently the only issue was the 15 sec latency bug (both ways). should not be a problem now
<arno11> so if you want me to try a cleaner method to start cmt_pulse on boot, let me know
<sicelo> yes, we do :-)
<arno11> :)
<Wizzup> xsession sounds like a good way
<arno11> ok, using /etc/X11/Xsession.d ?
<arno11> and adding for example 99cmt_pulse sh script with /usr/bin/cmt_pulse inside ?
<Wizzup> yeah, maybe look at the other scripts on how it should work exactly
<arno11> yeah seems to be trivial. i'll try tomorrow
mqlnv has quit [Ping timeout: 268 seconds]
mqlnv has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
<freemangordon> arno11: have a look at dh_installxsession
DPA has quit [Ping timeout: 268 seconds]
DPA has joined #maemo-leste
uvos has joined #maemo-leste
<uvos> Wizzup: its a regmap
<uvos> so theres a file in debugfs for it
<uvos> not sure the exact path
<Wizzup> hi
<Wizzup> ok, let me see
<uvos> might be /sys/debug/regmap even
<Wizzup> meanwhile the android ones I uploaded
<Wizzup> there is /sys/kernel/debug/regmap/
<Wizzup> # ls
<Wizzup> 0-0038 4806a000.serial:modem:audio-codec@2 dummy-scm_conf@4a002000
<Wizzup> 1-0044 dummy-omap4_padconf_global@4a1005a0 spi0.0
<uvos> spi0.0 is cpcap
<uvos> not sure why the name is so wierd
<uvos> i gues thats the host side of the bus?
<Wizzup> root@devuan-droid3:/sys/kernel/debug/regmap/spi0.0# cat name
<Wizzup> cpcap-core
<Wizzup> right
<Wizzup> ok, I can get the regs on serial, so shall I just them from mainline with screen on (and serial connected, but not usb)?
<uvos> as nutch of the same state as android as possible ofc
<uvos> since we are trying to make the diff as small as possible
<Wizzup> right
<Wizzup> the files I linked on my website have some pretty clear diffs
<Wizzup> between the diff frequencies
<uvos> sure, but ideally we would expect no diff between android and mainline, besides the rtc
<uvos> and the audio section is tricky
<Wizzup> what I mean is that maybe the android regs can tell us which mainlines regs to look at
<Wizzup> but then again I have no idea what I am doing :)
<uvos> what im looking for is mostly the possiblity of configureing a regulator wrong
akossh has quit [Ping timeout: 268 seconds]
<Wizzup> do you also want the emif regs?