brosame has quit [Quit: leaving]
parazyd has quit [Ping timeout: 264 seconds]
parazyd has joined #maemo-leste
akossh has quit [Quit: Leaving.]
joerg has quit [Ping timeout: 246 seconds]
joerg has joined #maemo-leste
<tmlind> Wizzup: best to test each operating point separately by disabling other c-states via sysfs
<tmlind> Wizzup: usually the issue is is voltage related or emif configuration related
<tmlind> uvos: interesting so what did you figure out on mainline sgx underperforming?
xmn has quit [Ping timeout: 260 seconds]
synapse has joined #maemo-leste
pere has quit [Ping timeout: 268 seconds]
<Wizzup> tmlind: ok, I will see if I can figure out where to change the c-states in sysfs if it's not just setting the cpu scaling frequency
arno11 has joined #maemo-leste
<Wizzup> arno11: I'll do the PR momentarily
<arno11> ok cool, thx
akossh has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
tsesani has joined #maemo-leste
tsesani has left #maemo-leste [#maemo-leste]
<Wizzup> tmlind: uvos: so it looks to me like qminet creates /dev/qcqmi{0,1,2,3} on android and the dir we linked earlier on gitlab really is the only thing necessary for it
<Wizzup> I wonder if qmicli can somehow just operate on these itnerfaces
<Wizzup> well that and the four qmi{0,1,2,3} network interfaces I guess
<Wizzup> this also mentions maybe what uvos was talking about
<Wizzup> Note: Some Android devices also support QMI-capable chipsets through GobiNet (everything hidden in the kernel and the RIL). In this case, though, you may see that shared memory can also be used to talk to the QMI device, instead of a /dev/qcqmi port.
<Wizzup> but I don't think this is the case here
<Wizzup> (famous last words)
<Wizzup> in general this seems like useful info btw
<Wizzup> for me at least
arno11 has joined #maemo-leste
xmn has joined #maemo-leste
<arno11> sicelo: Wizzup: if i pkill cm_pulse there is no negative impact, it restarts automatically and calls are working again...with a positive effect: (alerting) tone is working (again) now
<arno11> h-s-m, sometimes nokia-modem and now cmt_pulse. i wonder what's going on during boot
<arno11> ok issue solved for h-s-m
<arno11> renaming 15hildon-status-menu to 75hildon-status-menu (just after sphone in fact) makes h-s-m and availability BTN working correctly again
<arno11> freemangordon: ^^^
<arno11> i'll try to start cmt_pulse a bit later now
<arno11> issue solved for cmt_pulse as well
<arno11> Wizzup: i need to make a small change to cmt_pulse PR
<Wizzup> go for it
<arno11> could the very slow startup be related to 1 or several apps starting at the wrong time iyo ?
<Wizzup> I don't know if the startup is very slow
<Wizzup> does fremantle start much faster?
<arno11> yes a lot faster
<arno11> and an old leste img starts really faster too
<arno11> (PR updated btw)
<arno11> BTW for hildon-status-menu, is D4 affected or everything is ok with availibility BTN ?
<Wizzup> it works for me
<Wizzup> I don't know what problems you see specifically, but it works ok for me
<arno11> sorry for the lack of context: since december, availibility BTN in h-s-m was not working anymore on startup
<arno11> from a fresh install on n900
<arno11> and starting it a bit later solved the issue
<Wizzup> not sure what it would need then
<arno11> so (for n900) we need to modify h-s-m debian/rules or simply rename h-s-m xsession file in Xsession.post
<arno11> maybe we can modify debian/rules if there is no impact on other devices (dh_installxsession -u 'post 75' instead of dh_installxsession -u 'post 15')
<Wizzup> ok, but you say this makes a difference i wonder why
<Wizzup> like, what is making it bgreak
<Wizzup> break*
<arno11> the fact that it starts before hildon-home, hildon-desktop and conversations imo
<Wizzup> well conversations definitely has nothing to do with this
<Wizzup> brb
xmn has quit [Ping timeout: 252 seconds]
<Wizzup> correction, libqmi likely won't be able to talk to what I mentioned above, so it would indeed need to be integrated into qmi_wwan as non-usb backend
<Wizzup> but that might be quite doable
<freemangordon> arno11: I am against changing h-s-m start time unless we know why changing it make s a difference
<freemangordon> also, there is no issue on d4
<freemangordon> or in VM in that regard
<arno11> ok
<freemangordon> however...
<arno11> but remember i'm not a dev :P
<freemangordon> I want to finish as much as I can with what I am doing currently (connui-cellular)
<freemangordon> and then will see what's going on with n900/h-s-m
<arno11> ok
<freemangordon> might take a week or so until I am on it
<arno11> ok (anyway i found a workaround for me and i'm happy with that)
<arno11> :)
<freemangordon> right
<freemangordon> Wizzup: sicelo: EDGE == UMTS == 2.5, right?
<arno11> no: edge == 2.5g
<freemangordon> hmm
<freemangordon> and what is UMTS?
<arno11> umts == 3G
<freemangordon> ah
<freemangordon> ok
<arno11> hsdpa == 3.5G
<freemangordon> seems ofono does not report EDGE support
<arno11> but it works iirc
<Wizzup> you need to check specific extra bits. like my older code does
<freemangordon> Wizzup: care to point if you can, while I am searching?
<Wizzup> also ofono has "edge" as technology
<Wizzup> I am pretty sure
<Wizzup> freemangordon: ofono_rat_change
<freemangordon> but that's current RAT
<freemangordon> not capabilities
<Wizzup> what is gsm then, vs edge?
<freemangordon> no idea :)
<Wizzup> see my comment regarding NETWORK_MASK_EGPRS_SUPPORT
<freemangordon> ok
<Wizzup> at least thta might be relevant
<freemangordon> that's what I need
<Wizzup> note that btw we never show 3.5g in my current code
<Wizzup> it always shows 3g for some reason (iiuc)
<freemangordon> however, this needs modem to be connected to the net
<freemangordon> but we need if modem supports edge at all
* freemangordon ckecks
<freemangordon> *checks
<freemangordon> Features = sms net rat gprs ussd sim
<freemangordon> Wizzup: ^^^
<freemangordon> this is what modem reports
<freemangordon> oh, this is same as interfaces
<Wizzup> I think you just use the current radio tech?
<Wizzup> NetworkRegistration.Techology or whatever
<freemangordon> yeah
<freemangordon> seems I will have to
<freemangordon> Wizzup: oh, see org.ofono.NetworkOperator
<Wizzup> not all of these are present for all devices btw
<Wizzup> this might well be, jfyi
<freemangordon> this is where we have Technologies
<freemangordon> yeah, right
<freemangordon> ok, I think I have an idea how to continue
<Wizzup> :)
<Wizzup> important work
<freemangordon> I already (almost) implemented multi-modem support
<freemangordon> and get rid of libgofono
<Wizzup> great
pere has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
<sicelo> Wizzup: I've seen 3.5G on my N900 with Leste :-)
<Wizzup> sicelo: ok, maybe not 2.5G then
<Wizzup> (that would match the codes comments)
<arno11> yes i can confirm too, 3.5G icon works
<arno11> not 2.5G
<arno11> but 2.5g network works for sure (even if it shows 2G icon)
arno11 has left #maemo-leste [#maemo-leste]
<sicelo> 21:09 < freemangordon> but we need if modem supports edge at all <<== org.ofono.RadioSettings.AvailableTechnologies. unfortunately it's optional, and most of our modems don't have it. there's no other way to know if a modem supports a particular tech
eloy has quit [Quit: eloy]
eloy has joined #maemo-leste
<sicelo> actually scratch that ... we do have Available Techs
<sicelo> it's just there's nothing for EDGE :-)
<sicelo> N900 doesn't have it, mmm
gnarface has quit [Quit: Leaving]
<sicelo> i think something's up with ofono/drivers/isimodem/radio-settings.c ... i can look at it someday
<freemangordon> sicelo: yeah, I saw that ionterface
<freemangordon> *interface
<freemangordon> AvailableTechnologies = gsm umts lte
<freemangordon> this is on the USB modem I use to develop in the VM
<freemangordon> nothing about edge :)
<sicelo> yes, nor 3.5G
<freemangordon> mhm
<sicelo> because you can't select 2.5 or 3.5
<freemangordon> mhm
<sicelo> :-)
<freemangordon> but again, this seems to be the network cell property
<freemangordon> not modem one
<freemangordon> maybe all modems are assumed to support it
<freemangordon> and it depends on the tower etc
<freemangordon> will see when I have more advanced code
<sicelo> a cell/tower that supports 3.5 or 2.5 is also willing to use plain 2 or 3. so the negotiation for .5 is solely between modem & network. i never seen a phone where you can choose those modes
* sicelo looking forward to the upcoming code :-)
<sicelo> so isimodem driver doesn't have query_available_rats. damn
<freemangordon> hmm, it should have
<freemangordon> as on fremantle you can get network_supported_services
<sicelo> i guess work on the ofono driver stalled before that could be done. we do have missing bits for the modem
<freemangordon> get_radio_access_technology is the dbus call
<sicelo> we're just lucky that a lot was already added
<sicelo> fmg, yes but thay requires the driver to support it.
<freemangordon> oh, sorry
<freemangordon> it is Phone.Net.get_registration_status
<freemangordon> anyway, I think I will manage to do that properly
<sicelo> at least, even though AvailableTechnologies doesn't exist, you can still set "gsm" or "umts" on N900 as you need to. overall not a big deal
sch has joined #maemo-leste
arno11 has joined #maemo-leste
pere has joined #maemo-leste
tsesani has joined #maemo-leste
tsesani has left #maemo-leste [#maemo-leste]
diejuse has joined #maemo-leste
gnarface has joined #maemo-leste
gnarface has quit [Client Quit]
gnarface has joined #maemo-leste
gnarface has quit [Remote host closed the connection]
gnarface has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]