<sicelo>
the issue with mic not working in calls really baffles me, especially because it's intermittent.
<sicelo>
uvos: any ideas? suggestion for what i can/should look at?
cytokine_storm has quit [Ping timeout: 260 seconds]
<sicelo>
arno11: is it possible that the hangup is not really a bug in tp/ofono/etc. but just the known issue with some UI elements almost hanging the device when there's a phone call?
<sicelo>
uvos: any idea about the TS bug too? it's quite inconvenient ... i.e. it seems reenabling the TS fails, when there's incoming call. maybe something's racy?
<sicelo>
it happens for me more than 75% of the time. workaround is to toggle the lock state of the device using the power key, hoping the caller stays on the line long enough for that
<sicelo>
something else ... i have contacts saved, but sphone doesn't resolve them
<sicelo>
or is it because i stored the number as +26876xxxxxx, and the incoming call actually comes as 76xxxxxx (i.e. local number without prefix)?
<sicelo>
i *think* this worked fine in Fremantle
arno11 has joined #maemo-leste
fab_ has joined #maemo-leste
<arno11>
sicelo: (for hangup) seems different. i checked in monitor-ofono and the call is correctly closed (and PA synch stopped). but sphone continues to show an active call
<sicelo>
just verified ... the number<->contact resolution is still broken even when the number doesn't include the prefix (+268)
<sicelo>
arno11: at least that shows fault is not in ofono :-P
<arno11>
i just mean that the call is really closed
<sicelo>
arno11: so i was wondering if, at that time, it's not actually N900 being somewhat frozen? thus the sphone UI appears to hang?
<arno11>
nope
<arno11>
sphone works fine
<arno11>
no freeze at all
<Wizzup>
let me just take a look (hopefully today) at the parts where you're not able to answer
<Wizzup>
oh, wait, sicelo you're saying this is a touchscreen issue?
<sicelo>
Wizzup: there are different unrelated issues
<sicelo>
1. there's a mic issue
<sicelo>
2. there's a TS issue
<sicelo>
3. there's a contact name resolution issue
<sicelo>
for mic issue ... i've already accepted the call (or i initiated it) ... i can hear the person, but they can't hear me at all. doesn't happen all the time, but is very frequent
<sicelo>
for TS issue ... there's an incoming call, sphone shows up, but touch anywhere does nothing. toggling lock state using power button restores things
<sicelo>
it's the mic issue that is more critical to me, for obvious reasons
<sicelo>
Wizzup: all these three are being experienced on Droid 4. no idea about N900
<sicelo>
then 4. contact name resolution seems not working. i *think* i've seen it work in the past with sphone, so i'm not sure what's different now
<Wizzup>
sicelo: so when you said it kept ringing, this is a ts issue?
<Wizzup>
or kept vibrating rather
<sicelo>
i think that was something else. maybe the device was frozen or something. hasn't happened again since yesterday
<Wizzup>
ok
<Wizzup>
sorry, I'm in the middle of some bureacratic nightmare wrestling match with the dutch government so my mind is kind of elsewhere
<arno11>
(on n900 no troubles like that, excepting hangup bug and name reso)
<arno11>
so good luck man
<Wizzup>
if you can make github issues with steps it will be easier for me to try it out when I can set my mind to it in few hours hopefully
<sicelo>
so it's just the 4 issues above that are recurring, with differing regularity
<Wizzup>
or a single github issue is fine to
<Wizzup>
too*
<sicelo>
sure, will do. unfortunately no idea about reproducing :-P
<sicelo>
because it just happens unexpectedly
<sicelo>
arno11: nice to know N900 isn't affected. that might help to narrow it down
<Wizzup>
if you can just describe like: incoming call, this happens
<arno11>
bbl
arno11 has left #maemo-leste [#maemo-leste]
<sicelo>
in the meantime, because of the mic issue, i moved the SIM to N9 (MeeGo)
<Wizzup>
*nod*
PPK has joined #maemo-leste
<PPK>
Interesting bug: 4G internet connection did not show up until set system settings Internet connection: Ask
<Wizzup>
what device is this?
<PPK>
Pinephone
<PPK>
latest image
<Wizzup>
so you're saying the lte wasn't provisioned until you opened the internet control panel in the settings?
<PPK>
yes
<PPK>
one special thing I have: wifi is disabled with dip-switch
<Wizzup>
hm, I wonder if that is related indeed
<PPK>
btw..how to set timezone with clock app, by default it seems to be London, clock shows right London time.
<PPK>
that map shows different place that chosed...but I managed.
<PPK>
that manual should be in place where is question mark icon in apps that does not work at all.
<PPK>
manual chapter 8.2.1 should add in picture how attach Pinephone keyboard to Pinephone. It would be nice that hint from wiki about layout comes default layout in Pinephone.
<PPK>
also I noticed with droid4 that still have to set that layout from wiki..it also should be default.
<PPK>
what file I have to edit in Droid4 if I want ÄÖÜẞ on AOUS with that OK button?
f_ has joined #maemo-leste
<PPK>
like it is with Pinephone Keyboard altgr-layout.
f_ has quit [Remote host closed the connection]
<Wizzup>
could you file some issues on gh? I made a label documentation so that you can add that label for the request on how to add the pinephone keyboard
<Wizzup>
brb
f_ has joined #maemo-leste
<LeePen>
I have leste booted on my n900 and with light transitions and tracker disabled, the speed is usable so far.
<LeePen>
Xterm doesn't seem to receive the <enter> key. I am having to use ctrl-j
<LeePen>
Any ideas?
<LeePen>
What is the alternative to osso-filemanager?
<Wizzup>
xterm or osso-xterm?
<Wizzup>
hamsterfiler I think can be used
<PPK>
LeePee, I use Midnight Commander (mc) as filemanager it support touch in Maemo.
<LeePen>
Both xterm and osso-xterm: actually <enter> is fine initially, but once I ssh elsewhere it the key no longer works and I have to use ctrl-j
<LeePen>
reset is no help.
<LeePen>
Sounds like a terminfo thing.
<PPK>
LeePee, You can also try Thunar as filemanager. It is not real Maemo version, but it is usable, example going into folder with touch and then space.
<PPK>
I hope that someday Thunar is default filemanager for Maemo.
<PPK>
LeePee: Hamster Filer also available thru Application Manager it is real Maemo software.
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
<PPK>
Is there any skill full enough to compile Maemo software to Leste like this: https://wiki.maemo.org/FMMS
<Wizzup>
I think fmms won't work because the cellular stack is very different
<Wizzup>
we probably need to figure out a better way to do mms
<Wizzup>
(right now we have none)
<PPK>
good to know
xes has joined #maemo-leste
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
PPK has quit [Quit: Client closed]
f_ has quit [Ping timeout: 260 seconds]
pere has quit [Ping timeout: 252 seconds]
fab_ has quit [Quit: fab_]
<LeePen>
Wizzup: yes and yes
fab_ has joined #maemo-leste
pere has joined #maemo-leste
arno11 has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__>
im suprised people still use mms, around here it was never popular
<uvos__>
everyone in my contacts seams to have gohne from sms directly to ip messaging skipping mms
<arno11>
LeePen: if you feel the speed just 'usable', check if your sdcard is fast enough and check if you upgraded to devel. few more tweaks are needed btw to make the n900 really usable @600MHz max. i'll make a list
<Wizzup>
arno11: yes please, a list, I have some time today now :)
<arno11>
ah ok cool :)
<uvos__>
sicelo: Wizzup: contact name resolution still works fine for me (as do the other things) i still use the ofono backend
<uvos__>
this suggests the line_id in sphone is wrong so the lookup fails
<uvos__>
when used with vcm
<uvos__>
sicelo: i use the d4 alot for phone calls and have never had any of your issues, but i do use a quie different setup since
<uvos__>
mic issue: could be a race in the kernel driver/ofono the modem audio handling is quite hacky, vcm might be triggering this by being alot slower
<uvos__>
ts issue: some systemui race with tlkock maybe - i dont use tklock so i would not see this
<Wizzup>
the kernel also has some racy issues still
<Wizzup>
iirc
<uvos__>
resolution issue: as mentioned
<uvos__>
yeah i said that
<Wizzup>
ah, you mentioned userspace
<Wizzup>
I meant kernelspace
<arno11>
Wizzup: LeePen: sysctl vm.swappiness=30, echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq, chrt -r -p 98 $(pgrep pulseaudio), tracker daemon -t (make sure miner, extract and store are stopped)
<arno11>
and light transitions
Daanct12 has quit [Quit: WeeChat 4.2.2]
<arno11>
and if you want, disable apt-worker (for the moment)
<sicelo>
uvos__: MMS seems popular in US/Canada for some reason
Daanct12 has joined #maemo-leste
<sicelo>
mic issue ... i can reflash a non-devel image and see if the problem is there. it could be related to vcm indeed, since i never had this issue before
<sicelo>
ts issue was there even pre-tp days
<uvos__>
sicelo: no nead to flash
<uvos__>
just delete the /usr/share/sphone/sphone.ini.d/SOMETHING-maemo.ini
<uvos__>
and reboot
<uvos__>
sphone will revert to its default non-maemo config which is what i use
<uvos__>
to make it permanent you can cp sphone.ini to ~/.sphone
<uvos__>
since SOMETHING-maemo.ini will return when leste-config upgrades
<uvos__>
sicelo: yeah and i can tell you why, in us mms is used when an iphone uses imessage to communicate with a non iphone
<uvos__>
imessage is non-existant outside us since iphones are not the dominat platform anywhere else
Daanct12 has quit [Quit: WeeChat 4.2.2]
<uvos__>
sicelo: as for tp issue could you check via ssh if the ts is disabled in xinput in this state
<uvos__>
also monitor tklock state with dbus-monitor if possible
<uvos__>
*ts issue
arno11 has left #maemo-leste [#maemo-leste]
<sixwheeledbeast>
where is "light transitions" from?
arno11 has joined #maemo-leste
<arno11>
sixwheeledbeast: that's just a custom transitions.ini file based on Fremantle tweaks
<sixwheeledbeast>
is there a source available?
<arno11>
(leste-config/pull/40)
<sixwheeledbeast>
so is this is devel already?
<arno11>
no
<sixwheeledbeast>
leste device transitions do feel clunky compared to my fremantle but I tweaked them years ago, need to compare
<arno11>
i did the same years ago too
<arno11>
now the feeling is even better on leste compared to my Fremantle (but transitions/effects/animations are almost completely disabled on my leste)
<arno11>
the major diff is still the touchscreen latency
<arno11>
far better on fremantle, i wonder why
<arno11>
and i wonder if it is possible to tweak that
ceene has quit [Ping timeout: 260 seconds]
<sixwheeledbeast>
maybe hardware being resistive?
<sixwheeledbeast>
or is this the same device
parazyd has quit [Ping timeout: 240 seconds]
<uvos__>
on n900 the hardware is always resistive (har har)
parazyd has joined #maemo-leste
<arno11>
sixwheeledbeast: i meant on the same device
xmn has joined #maemo-leste
<sixwheeledbeast>
:nod:
<sixwheeledbeast>
Comparing most of the ones changed in that pull I have larger values on, so there must be something else effecting the feel.
<arno11>
well, in fact, difficult to compare
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
uvos__ has quit [Read error: Connection reset by peer]
arno11 has left #maemo-leste [#maemo-leste]
diejuse has joined #maemo-leste
diejuse has quit [Ping timeout: 250 seconds]
diejuse has joined #maemo-leste
<diejuse>
LeePen I use SpaceFM like a file manager. It is good. Try it
diejuse has quit [Client Quit]
Gary_ has quit [Ping timeout: 240 seconds]
pere has quit [Ping timeout: 260 seconds]
mdz has joined #maemo-leste
f_ has joined #maemo-leste
<LeePen>
diejuse: thanks, I'll give it a go.
Twig has joined #maemo-leste
pere has joined #maemo-leste
f_ has quit [Remote host closed the connection]
f_ has joined #maemo-leste
Livio has joined #maemo-leste
Juest has quit [Ping timeout: 246 seconds]
fab_ has quit [Quit: fab_]
Juest has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
f_ is now known as funderscore
pere has quit [Ping timeout: 260 seconds]
funderscore is now known as f_
SystemError has quit [Remote host closed the connection]