<buZz>
already this 20220508 image behaves differently ; when booting the 20220410 with a charger connected, it wont start charging until you remove&replug it
<buZz>
20220508 seems to be fine with it
<buZz>
although, this might be because i moved to -devel ?
belcher has quit [Quit: Leaving]
<buZz>
alright, what was the bundle to install for making it a phone? :D
<Wizzup>
I'd appreciate if you could spend some of the time documenting this - it's hildon-connectivity-mobile
belcher has joined #maemo-leste
<buZz>
hmmm, 20220508 @ droid4 doesnt seem to have the decent keyboard :( (with the OK layer)
<Wizzup>
hmm
<Wizzup>
could be a first boot thing maybe?
<buZz>
i rebooted a bunch of times now, nogo
<Wizzup>
hm, ok, will have to check.
<buZz>
can i do the hildon-connectivity-mobile without -devel too? guess not super useful?
<uvos__>
buZz: its me
<uvos__>
everything is a typo
<uvos__>
:P
<uvos__>
Wizzup: just the register i mentioned and one other is relevant
<uvos__>
all others are different
<uvos__>
but on purpose
<uvos__>
othe one other is the mic amp
<uvos__>
but it should work by just seting the output reg correctly
<Wizzup>
uvos__: so the register you mentioned is always 0 it seems
<Wizzup>
yeah, that's with mpv playing and me hearing it
<Wizzup>
(apart from the one file where nothing is playing)
<uvos__>
Wizzup: ok im not at home right now
<uvos__>
ill check my notes when i am
<uvos__>
maybe its the wrong register
<Wizzup>
great, ty
Wizzup has quit [Quit: leaving]
Wizzup has joined #maemo-leste
<buZz>
fyi, hildon-connectivity-mobile isnt installable without -devel
<Wizzup>
yes
<Wizzup>
that is on purpose
<buZz>
ok :)
<Wizzup>
you've probably noticed it's not quite ... end user ready
<buZz>
well, its is -in- the not-devel
<buZz>
hehe
ceene has quit [Ping timeout: 256 seconds]
<buZz>
alright, -mobile is installed on this -devel, lets reboot and see
<Wizzup>
buZz: I will be afk for a bit jfyi
<buZz>
np, hf \o
ceene has joined #maemo-leste
<buZz>
is libicd-network-ofono not needed? its not installed now
* buZz
installs and reboots
<buZz>
right, that does help
ceene has quit [Remote host closed the connection]
xmn has joined #maemo-leste
<buZz>
seems to be similarly broken as 20220410 after all the setup , meh
<Wizzup>
It's weird, it just works for me really.
<Wizzup>
maybe there's some step you're missing
<Wizzup>
it's hard to debug without getting much info though:)
<buZz>
yeah i think it might just be my simcard?
<Wizzup>
I don't think so.
<buZz>
what do you have on > 03:37:18 < buZz> org.ofono.AllowedAccessPoints.GetAllowedAccessPoints , returns just ([],)
<buZz>
?
<Wizzup>
I have no idea what that interface is, but I didn't ask about that
<buZz>
i know
<buZz>
03:41:44 < buZz> org.ofono.ConnectionContext.GetProperties does show route and dns
<buZz>
03:41:57 < buZz> and ip even, as static??
<Wizzup>
if you get a wwan3 interface at any point in time, it just means it worked.
<Wizzup>
and if it shows an ip, then the problem you're seeing is in icd2 not configuring the interface with the settings from ofono
<Wizzup>
it = mdbus2/ofono
<Wizzup>
so that's very likely -not- the sim card
<Wizzup>
for example, for me the data connection does not disappear
<buZz>
after the 'connect'/failure (which removes entry from icd2 UI) there's no IP configured, wwan3 is up, and org.ofono.ConnectionContext.GetProperties shows IP, dns, route (as static?)
<Wizzup>
how does it 'remote' it from the ui
<Wizzup>
do you never ever see the entry again until you reboot?
<buZz>
until i restart icd2 , yes
<Wizzup>
I don't have that problem
<Wizzup>
I just tried it
<Wizzup>
it still shows 'KPN'
<buZz>
and your APN name, is there any stored in the IAP ui in settings?
<buZz>
does org.ofono.ConnectionContext.GetProperties show a APN?
<buZz>
for me , both are '' , emptystring
<Wizzup>
yes, it shows an apn for me
<Wizzup>
'internet'
<buZz>
i feel this might be the origin of the problem
<Wizzup>
it's certainly a side effect of libicd-network-ofono not provisioning it correctly
<buZz>
configuring -anything- as APN makes it a) not disappear b) work even less (wwan3 isnt up, but!!! still IP/dns/route in org.ofono.ConnectionContext.GetProperties)
<Wizzup>
do you have the package with all the apns installed?
<Wizzup>
I think it is in the meta, but still
<buZz>
i doubt it contains 'youfone' :p
<Wizzup>
why would it not
<buZz>
its a kinda newish telco?
<Wizzup>
dpkg -L mobile-broadband-provider-info
<Wizzup>
does that show anything
<buZz>
20170903-1
<Wizzup>
no file listing?
<buZz>
yeah, its there
<Wizzup>
ok
<Wizzup>
it doesn't seem to contain youfone
<Wizzup>
so maybe just set it via gconf?
<buZz>
or just add to that pkg?
<buZz>
oh hmm, maybe because its a MVNO
<Wizzup>
what?
<Wizzup>
no, just use gconf to configure the iap
<buZz>
does that do something else than the UI?
<Wizzup>
I don't know, have you confirmed that your gconf has the right apn?
<Wizzup>
mine has
<Wizzup>
gprs_accesspointname = internet
<buZz>
i havent, but how could it work without the correct APN?
<buZz>
mobile-broadband-provider-info isnt our own, is it?
<buZz>
i'll just wedge my operator settings into the .xml
<Wizzup>
I mean....
<Wizzup>
that xml file is only used once to set the gconf settings..
<buZz>
right, i just wanna check if it might change behaviour
<Wizzup>
so if you tried what I suggest, to set it in gconf, maybe you wouldn't have to mess with the xml? :)
<buZz>
its a bit hard to find -where- in gconf tree to set it without |
<buZz>
:D
<buZz>
really should start using usbnet more again :)
<buZz>
omg omg omg
<buZz>
so, with my network in the .xml , failed gprs connects do -not- remove it from ICD2 UI
Evil_Bob has quit [Quit: brb]
<buZz>
and, on second connect, it works \o
<buZz>
just still doesnt set DNS correctly, but the failsafe 9.9.9.9 gets set
<buZz>
alright, i'll work this all into a 'state of leste - using as a phone'
<buZz>
i kinda wonder how all this would be on n900/pp , hope i can borrow that pp soonish
<Wizzup>
buZz: without | ?
<buZz>
hmm, ok, on -disconnect- it does disappear from ICD2 UI
<buZz>
:(
<buZz>
Wizzup: yeah , the 'OK' keyboard layer isnt here
<buZz>
hmmf, ok nevermind, that succes seems just once
<buZz>
-_-
<buZz>
soooo cloooose :P hahaha
<buZz>
at least, there doesnt seem to be much the 20220508 is doing that 20220410 wasnt
<buZz>
i'll go back to that one
<buZz>
ok, added network to .xml , deleted gconf entry for GPRS IAP , reboot
<buZz>
lets see
<buZz>
so eh , gconftool -s /sy..... (the GPRS iap) -t string gprs_accesspointname="poop" , and then gconftool -R /sys.. (same entry) , should that show 'poop' ?
<buZz>
because it just sticks to emptystring
<buZz>
ah, wait
<buZz>
right, not 'gprs_..=""' , but just "" and add the gprs_... to the path
<buZz>
welp, setting it to the correct value just makes it completely unable to connect, similar to setting APN in the UI
Evil_Bob has joined #maemo-leste
<buZz>
pfff, what a puzzle :D haha
<Wizzup>
what did you execute exactly?
<Wizzup>
it sounded like you had it working 30mins ago no>
<Wizzup>
upstream might already have a newer version
<Wizzup>
we ship the buster one
<buZz>
but even without, from what i'm reading, because there's no unique MMC&MNC , it could pick a already specified APN from another entry with the same details
<sicelo>
however, i'm a little lost - who do i sent the changes to? should it be original maintainers/reviewers that i sent to initially, or someone/something else?
mardy has quit [Quit: WeeChat 2.8]
uvos has joined #maemo-leste
<Wizzup>
sicelo: is this patch already merged?
<uvos>
Wizzup: its CPCAP_REG_RXCOA
<uvos>
#define CPCAP_REG_RXCOA0x0824/* RX Codec to Output Amps */
<jirido>
Well I might get it all wrong then, what is making maemo maemo?
<jirido>
I have a bunch old nokia/microsoft phones(the square ones) can maemo run on them?
<Wizzup>
yes and no
<Wizzup>
the answer to the question depends a bit on your background
<jirido>
lol
<jirido>
it's baad
<sicelo>
jirido: you said you have an N900, right?
<Wizzup>
jirido: so what we aim to have is something that looks and feels like maemo on the n900, but on more devices than just the n900, with nothing but open source software based upon the debian/devuan distribution
<Wizzup>
compare that to nokia maemo which wasn't fully open source, for example
<jirido>
Sounds sweet
<jirido>
I look forwarrd to feel secure on my phone some day
<Wizzup>
yes, me too.
<Wizzup>
uvos: btw I see this in sphone:
<Wizzup>
(sphone:4270): hildon-1-CRITICAL **: 23:24:29.107: Tried to initialized Hildon more than once.
<jirido>
is there some development of secure open source telecom chips going on?
<jirido>
Can't get more secure that the chip i guess or is it enough to have a opensource driver?
<Wizzup>
uvos: ok I got something on speakerphone now with:
<Wizzup>
depends on how you define telecom chips, do you mean modem?
<Wizzup>
uvos: nothing on earpeice though with 0001
<sicelo>
maybe osmocom (not sure about spelling)? jirido: there's not much progress, i'd say
<Wizzup>
uvos: same for headphone, that didn't work for me with the register setting, but maybe I also need to switch to it in pavucontrol?
<sicelo>
pp has a modem whose firmware is replaceable somewhat, but it's not open overall. and seems quectel (its vendor) is about to close the loophole which allowed the firmware to be replaceable in the first place
<jirido>
sicelo: thats bad. It should not be rocket sience to make an opensource radio chip.
<Wizzup>
uvos: ok I can get all three working when switching pulse profile + reg write
<Wizzup>
uvos: at least I can hear my n900 on the droid4
<Wizzup>
I can't hear the droid4 on the n900 yet
<sicelo>
i haven't taken calls on droid 4 in a while. so they currently work over loudspeaker only?
<Wizzup>
sicelo: I think is one of the first times I kinda got it working
<Wizzup>
but I am still not sure is that I hear both sides
<sicelo>
i definitely did get it working as well in the past - with both sides working fine. i suppose that was loudspeaker
<Wizzup>
I can hear my n900 on my d4 with earpiece and headphone
<Wizzup>
I am just not sure I can hear my droid on my n900
<sicelo>
nice
<Wizzup>
I'll try again in a bit
<Wizzup>
if I can get that working today I'd be quite happy
<Wizzup>
I mean all I'm doing is follow uvos' advice really
<sicelo>
i saw you want to use dbus-scripts to handle the switching? sounds like a good idea
<Wizzup>
but for the record, if you're in a call, go to pavucontrol and set the output you want, and then also the register write
<Wizzup>
maybe a similar things needs to be done when looking at input
<Wizzup>
I guess the mic gain?
<Wizzup>
looks like 0x0818 (CPCAP_REG_TXMP) is always 0x400 so that's not it
<sicelo>
118175:1592141117 <sicelo> yay, so i've just received a voice call on my d4 with ofono. works good. i did have to speak quite loud (using pavel's alsa config from unicsy_demo). i guess it's a matter of playing around until i find good microphone volume
<sicelo>
so maybe your N900 can hear the d4 ... but volume is low
<Wizzup>
maybe voice loopback or something else is needed?
<Wizzup>
yeah voice is at 13 atm
<Wizzup>
maybe that's it?
<Wizzup>
wait
<sicelo>
unless things have changed much since back then
<sicelo>
i didn't have to do anything special for that call
<Wizzup>
looks like call noise cancellation was off
<Wizzup>
hm pavucontrol sees no input device in phone call mode
<Wizzup>
sicelo: ok mics are 0
<sicelo>
:-)
<Wizzup>
I can hear myself when pavucontrol is set to speakerphone
<Wizzup>
but not when it's set to earpiece
<Wizzup>
uvos: ok so it looks like mic1/mic2 are 0 on my phone by default, and only in speakerphone mode in pavucontrol do I hear the d4
<Wizzup>
uvos: does that sound familiar?
<Wizzup>
tmlind: ^^
<uvos>
hmm what
<sicelo>
1592517205 <sicelo> got sound on N900 with a phone call after all :) N900 can 'hear' the other person quite good. i can't really hear N900 on the ohter phone. will test further tomorrow
<sicelo>
almost two full years ago
<Wizzup>
uvos: what in particular should I elaborate on :)
<uvos>
uvos: ok so it looks like mic1/mic2 are 0 on my phone by default, and only in speakerphone mode in pavucontrol do I hear the d4
<uvos>
are 0 what?
<Wizzup>
0% out of 100%
<Wizzup>
so it's literally silent
<Wizzup>
which part of the puzzle of why I never heard the d4 on the remote side
<Wizzup>
on top of that I also only hear the d4 if the pavucontrol output device is speakerphone
<Wizzup>
if it's earpiece or headphone I can't hear it
<uvos>
the mic only woring in some modes is familiar
<Wizzup>
oh, and I had to switch the "left" item to mic1 or mic2
<Wizzup>
right
<Wizzup>
"left" in the alsamixer F4 capture devices
<uvos>
it has the same problem as the output amps
<uvos>
just in a different place
<Wizzup>
right
<Wizzup>
I thought maybe it was CPCAP_REG_TXMP
<Wizzup>
but it doesn't look like it
<Wizzup>
but it looks like in calls the "left" value in alsamixer also isn't set to what it'd expect
<uvos>
there was one more bit you had to set
<uvos>
apearntly i lost the register dumps i had from android
<uvos>
at least i cant find it right now
<Wizzup>
ok
<Wizzup>
I'm planning to make a local build of sphone that just runs some sh scripts that sets up the registers
<uvos>
[23:25] <Wizzup> (sphone:4270): hildon-1-CRITICAL **: 23:24:29.107: Tried to initialized Hildon more than once.
<uvos>
sphone calls the function more than once becasue that way it dosent have to keep track of what module loaded when and if one that requires libhildon allready loaded
<uvos>
Wizzup: sphone can run sh scripts out of the box btw
<Wizzup>
is it possible to have more than out route plugin?
<uvos>
yes
<Wizzup>
like what if I actually made a route-registerhack :)
<Wizzup>
can we use them both at once?
<uvos>
sure
<uvos>
yes
<Wizzup>
(well preferrably pa first)
<Wizzup>
it almost seems worth it to me
<Wizzup>
(for now)
<uvos>
eh
<Wizzup>
well there's many things that are in flight / work in progress, but if with some simple work we can make the d4 actually make calls reliably, I think that's pretty big
<Wizzup>
of course it's not a ready solution in that sense
<Wizzup>
but if it allows me to toy around with making calls, I think that's pretty neat
<Wizzup>
like, I would switch my main device over if the following worked: (1) stable ofono (2) audio in calls (3) telepathy conversations with sms working
<uvos>
you dont have to write a multi page motivation statment to me, just do it if you like
<uvos>
i just would not do so myself, since i dont condone sutch terrible hackery
<uvos>
and yeah sure would be neat
<Wizzup>
I think having something this in place is more likely to lead to more interest in making a proper fix