belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 258 seconds]
diejuse has quit [Quit: Leaving.]
diejuse has joined #maemo-leste
joerg has quit [Ping timeout: 268 seconds]
diejuse has quit [Ping timeout: 265 seconds]
joerg has joined #maemo-leste
mardy has joined #maemo-leste
sunshavi has quit [Ping timeout: 268 seconds]
rafael2k has quit [Ping timeout: 265 seconds]
rafael2k has joined #maemo-leste
pere has quit [Ping timeout: 272 seconds]
Pali has joined #maemo-leste
<Pali> marex: Hi! Ok, lets wait for freemangordon
<parazyd> uvos: Yes, I have that theme thing in my todo.
<lel> parazyd transferred a repository: https://github.com/maemo-leste/hildon-theme-devel
pere has joined #maemo-leste
mardy_2nd has joined #maemo-leste
uvos has joined #maemo-leste
<uvos> parazyd: great
mardy_2nd has quit [Quit: WeeChat 2.8]
<uvos> tmlind: to get the d4's earpiece to work in a voice call you have to set the mixer like mapphone ucm2 dose in this case (see https://github.com/maemo-leste/leste-config/blob/master/leste-config-mapphone/usr/share/alsa/ucm2/Mapphone_Audio/VoiceCall.conf.leste) write 0x1 to cpcap register 0x081c
<Wizzup> uvos: nice find
Daaanct12 has joined #maemo-leste
Daaanct12 has quit [Changing host]
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 252 seconds]
<uvos> tmlind: headset usage requries a write of 0x0260 to 0x081c work
<Wizzup> uvos: are you checking android and comparing?
<uvos> yes
<Wizzup> check
<uvos> i have one device in android and another in leste and was syncing up register state untill it works
<Wizzup> *nod*
<uvos> tmlind: ok so android uses 0006 for speakerphone
<uvos> but that seams to make no difference vs 0x0
<uvos> 0x0 is used by android only i hifi mode
<uvos> *in
<Wizzup> is cpcap firmware also available somewhere, or is it only something we can poke at by writing to it
<Wizzup> (in binary form)
<uvos> afiak its mostly in rom
<uvos> the kernel uploads some short code snipets to it
<uvos> those are in dts
<Wizzup> did anyone try to extract it?
<uvos> from cpcap rom/on-chip-flash?
<uvos> no
<Wizzup> mhm
<uvos> btw cpcap is also chainging 081c behind the mainline kernels back
<uvos> looks like unplugging the headphone changes this value
<uvos> this is why the headphones stop working when you unplugg and then replug them
<uvos> without changing the mixer settings again
<uvos> cpcap's hw/fw has changed the value in apearantly a failed attempt to autoswitch the outputs
<uvos> tmlind: ^^^
<uvos> also no omap4 gpio seams to corrispond to the headphone jack being plugged
<uvos> also no cpcap gpio register seams to corrispond to the headphone jack being plugged
<uvos> also no other cpcap register seams to corrispond either
<uvos> not on an android nor on mainline
<uvos> i guess on android cpcap maybe dose the switching with no input from the omap4
<bencoh> uvos: ah, so I'm not the only one with this bug
<Wizzup> bencoh: no, we all have it :)
<bencoh> alright
<Wizzup> it would be good if we could also be notified of it happening in userspace, for audio routing policy to kick in
<bencoh> I'm trying to remember whether I had it as well before I moved to leste
<uvos> Wizzup: idk if mapphone hw can do this, atm it sorta looks like no
<uvos> i guess if we understood cpcap uc we could progamm it to do whatever we want
<bencoh> uvos: how does android do it then?
<bencoh> I guess they receive an event of some sort
<uvos> bencoh: there is a cpcap macro that switches the output automaticly
<uvos> bencoh: i dont know how andorid knows the plugg state
<bencoh> something prevents us from re-using it?
<bencoh> hmm
<uvos> we could resue the macro yes
<uvos> then it would switch to headphones automaticly
<bencoh> but alsa wouldn't know about it
<uvos> but we have no way of syncing the mixer settings with whatever cpcap dose behind our back
<bencoh> yeah
<uvos> right
<uvos> this is the problem allready
* bencoh nods.
<uvos> cpcap just disables the headphone output when you unplugg it
<marex> Pali: Wizzup: freemangordon: it might in fact be better to discuss that in #u-boot and drag sjg1 into it
<Wizzup> ok, I joined the channel
<Wizzup> uvos: yeah curious to know how android knows it then
<Pali> joined
<tmlind> uvos: interesting, nice debugging :) sounds like we need to add handling for macro interrupts maybe?
<uvos> tmlind: right there is some macro mailbox
<uvos> tmlind: that might be where android knows
<tmlind> uvos: yeah must be something like that
<uvos> tmlind: anyhow will you add the correct call 081c values or shal i try to fiugre out how the mainline audio driver works?
<tmlind> uvos: please go for it if you have a chance, i won't be able to look at much anything for several days
<uvos> ok
<tmlind> uvos: voice calls are internal to cpcap for alsa, we do it all in set_tdm_slot() right now, so that could be buggy. the alsa driver should properly handle the mixer values
diejuse has joined #maemo-leste
stan has quit [Quit: Lost terminal]
stan has joined #maemo-leste
rafael2k has quit [Ping timeout: 252 seconds]
Daaanct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
Danct12 has joined #maemo-leste
inky_ has quit [Ping timeout: 268 seconds]
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 268 seconds]
inky_ has quit [Ping timeout: 268 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
<stan> it seems recent kernel/pvr drivers on droid4 lost the temporal dithering in 16bpp mode. now obvious 16bpp color banding is apparent
<Wizzup> We will not be using or supporting 16 bit going forward as I understand, so probably not a huge loss
<Wizzup> most applications cannot deal wiht 16 bit well at all, so that won't work well for us anyway
<parazyd> uvos: I think the themes should be fine now in devel
<stan> i'm curious to know which applications you refer to
pere has quit [Ping timeout: 272 seconds]
<stan> gl4es seems borken in 16bpp. glmark2 isn't working in 16bpp
<stan> but most applications shouldn't care
<Wizzup> we've had the discusson many times, and we decided not to that, it's probably in the irc logs somewher
<uvos> lots of modern stuff just renders 24bit surfaces and then converts to 16bit, eg firefox anything gtk3 anything qt5 in wayland mode
<uvos> probubly etc
<Wizzup> uvos: I had salutem installed now, rebooted
<Wizzup> and it shows upon boot
<uvos> right
<Wizzup> you told me to reboot twice
<Wizzup> not sure why
<uvos> because now it should never agian untill you change the html file
<Wizzup> also, the "Remove it withj" part for zram lacks at least a semicolon, or a separate line per command
<Wizzup> ok
<uvos> the intention is that the html fille will have a changelog
<uvos> and we update it
<Wizzup> I think we might also want a big(er) header for the html page that matches the window title
<uvos> and then salutem automaticly shows again next boot
<Wizzup> right
<uvos> Wizzup: sure the html file needs love
<parazyd> Wizzup: Yeah supposedly it can also do a subset of CSS
<Wizzup> is there a way to show up manually, clicking some icon?
<parazyd> Wizzup: So a nice design should be in place :)
<Wizzup> uvos: check
<uvos> Wizzup: i just took the wiki geting started page
<uvos> Wizzup: no
<uvos> Wizzup: you could add a desktop file for it
<uvos> Wizzup: and start salutem without the once flag
Danct12 has quit [Quit: Quitting]
<uvos> so you should be able to start salutem with
<uvos> salutem -t /usr/share/salutem.html
<Wizzup> btw, wifi auto connected for me just now
<Wizzup> uvos: ok, think it makes sense to have an icon for it?
<uvos> Wizzup: sure why not
<uvos> the user might want to refer to it again
<Wizzup> parazyd: what do you mean, 'be in place'?
<parazyd> Somebody should write it
<parazyd> I can, but not now
<Wizzup> ok
<uvos> tmlind: so simply switching the earpice controll in alsa mixer nukes CPCAP_REG_RXOA/0x081c to 0x0
<uvos> so its not that
<uvos> it sets CPCAP_REG_RXCOA CPCAP_REG_RXSDOA CPCAP_REG_RXEPOA correctly as you would expect in this case
<uvos> tmlind: i also set CPCAP_REG_RXCOA CPCAP_REG_RXSDOA and CPCAP_REG_RXEPOA by hand
<uvos> this dident change CPCAP_REG_RXOA so its not cpcap mcu chaning it behind out back
<uvos> so the problem is snd_soc_dapm_route
<uvos> snd_soc_dapm_route together with SND_SOC_DAPM_* is supposed to power off Earpiece PGA for power saving
<uvos> and apearntly it thinks its not needed with Voice PGA
<uvos> but im having a hard time reading the way this stuff is configured
<uvos> but the bug is in there
<uvos> anyhow with any setting in the Earpice alsamixer controll except Hifi this pice gets turned off:
<uvos> so no output
<uvos> for some reason, any invalid CPCAP_REG_RXOA value will enable the Speakerphone output amp so thats why the speakerphone happens to work
diejuse has quit [Quit: Leaving.]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
rafael2k has joined #maemo-leste
rafael2k has quit [Client Quit]
<lel> parazyd created a repository: https://github.com/maemo-leste/libtvout-ctl
<lel> parazyd closed an issue: https://github.com/maemo-leste/bugtracker/issues/57 (Look into gps (gpsd) support)
<lel> parazyd closed an issue: https://github.com/maemo-leste/bugtracker/issues/79 (Provide a virtual keyboard for the console)
<lel> parazyd assigned an issue: https://github.com/maemo-leste/bugtracker/issues/138 (osso-connectivity-ui: reverse engineer .mo files and add eap pap translation)
<lel> parazyd assigned an issue: https://github.com/maemo-leste/bugtracker/issues/211 (Provide a way to flash leste (or u-boot) directly)
lel has quit [Remote host closed the connection]
lel has joined #maemo-leste
<lel> parazyd opened an issue: https://github.com/maemo-leste/bugtracker/issues/550 (Pinephone: Provide some way of installing to emmc)
<lel> parazyd labeled an issue: https://github.com/maemo-leste/bugtracker/issues/550 (Pinephone: Provide some way of installing to emmc)
<lel> parazyd assigned an issue: https://github.com/maemo-leste/bugtracker/issues/550 (Pinephone: Provide some way of installing to emmc)
<lel> parazyd labeled an issue: https://github.com/maemo-leste/bugtracker/issues/550 (Pinephone: Provide some way of installing to emmc)
<lel> parazyd closed an issue: https://github.com/maemo-leste/bugtracker/issues/350 (Pinephone: 20200323 image written to eMMC failing to boot, stuck on "random: crng init done")
<lel> parazyd closed an issue: https://github.com/maemo-leste/bugtracker/issues/56 (Import maemo-tvout-control)
lel has quit [Remote host closed the connection]
lel has joined #maemo-leste
<Danct12> parazyd, regarding 550, that's unnecessary these days
<parazyd> What do you mean?
<parazyd> At the very least we need to change fstab
<Danct12> yeah fstab is the only thing that needs to be changed
<uvos> maybe add the same bug for mapphones too
<uvos> its tivial to install leste to emmc there
<uvos> just fstab and root= in boot.cfg needs to be changed
<uvos> if we change from the 2 partition layout of / and /boot and change root= to a partition lable you could even just flash the leste .img with fastboot so no sdcard is required
<uvos> or flash the same image to sdcard
<lel> parazyd labeled an issue: https://github.com/maemo-leste/bugtracker/issues/551 (Mapphone: Provide some way of installing to emmc)
<lel> parazyd opened an issue: https://github.com/maemo-leste/bugtracker/issues/551 (Mapphone: Provide some way of installing to emmc)
<lel> parazyd labeled an issue: https://github.com/maemo-leste/bugtracker/issues/551 (Mapphone: Provide some way of installing to emmc)
<parazyd> I don't want to ditch the 2 partition layout
<parazyd> It'll make FDE harder
<Danct12> i should also mention that there's https://github.com/dreemurrs-embedded/Jumpdrive
<Danct12> you flash this image to the sd card, boot the phone and the emmc becomes a mass storage device over usb
<parazyd> Cool
<bencoh> oh, neat
sunshavi has joined #maemo-leste
inky has quit [Quit: Leaving.]
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 272 seconds]
inky has quit [Ping timeout: 272 seconds]
pere has joined #maemo-leste
pere has quit [Read error: Connection reset by peer]
pere has joined #maemo-leste
<stan> anyone still getting the occasional reboot on Droid4? i was stable there a couple of weeks.
<stan> i don't need the GPS or GSM radio if that's a source of it
<uvos> 5.11 is stable, other than that pvr sometimes crahses (maybe causing a dsme reboot due to xorg dieing)
<stan> has anyone tried hacking a back cover to supply +5 to the inductive charge interface pins?
<stan> one could make a homemade slide-on extended battery
<sicelo> at least some did it for N900 ... should be much easier on the droid4, naturally
<uvos> the cpcap driver dosent support charging via those pins atm
<uvos> but you could just wire some random huge battery to the screw terminals
<uvos> that would work fine
<uvos> (and is indeed what i do with a 2200mAh battery)
<stan> they are spring-laden pogo pins, so all that's needed is a rounded contact in the right spot
<uvos> and kernel support
<stan> interesting
<stan> the motorola battery terminal has what looks like 4 contacts, two in the middle and two at the torx terminals, yes?
<uvos> yes
<uvos> the 2 contacts in the center dont matter
<stan> do you have a picture of your battery construction?
<uvos> no
<uvos> is a picture of the old battery i had
<uvos> it dident work so well because it had to high ir
<uvos> i just changed the cell after that
<uvos> the setup is the same
<uvos> the new cell is a nexus 5 one
<stan> your connector is interesting. did you etch it yourself?
<uvos> its cnc machined
<stan> the torx bolts carry the current down through the board to the droid4?
<uvos> you can take that to any pcb shop
<stan> no conductive layer needs to be on the bottom?
<uvos> and have it made
<uvos> yes the torx carry the current
<stan> that's just great
<stan> just great. just get the right voltage to them and go
<stan> -- what dc powered devices should be :)
<buZz> who tried to overclock microSD cards in here?
<uvos> me
<buZz> uvos: did you write up anything about it?
<parazyd> I managed too
mtnman has joined #maemo-leste
<uvos> no
<parazyd> There was a short kernel patch
<mtnman> helo
<uvos> but its really simple
<parazyd> mtnman: Hi
<buZz> any link to that patch?
<parazyd> uhh not sure
<mtnman> anyone here running maemo-leste on pinephone?
<buZz> :)
<uvos> search irc.txt
<parazyd> But it was just some frequency change
<stan> i think it disables internal emmc from working
<uvos> yes
<uvos> the patch was just forced every mmc device to 100mhz
<parazyd> mtnman: I got a new one recently and I started fixing up bugs
<uvos> the internal mmc dosent like that
<mtnman> parazyd got a new PP?
<parazyd> mtnman: Yeah because my old one died
<parazyd> Wizzup: Just managed to boot with openrc-init instead of sysv
Twig has joined #maemo-leste
<mtnman> ok i have one i bought last summer its running pmos. i want to put a new os on it and am considering maemo-leste. i liked maemo pretty well on my n900
<mtnman> parazyd: how does maemo-leste run on PP at this time?
<parazyd> It's decent. In landscape there are some grapics bugs, portrait seems good.
<parazyd> One thing you'll feel missing is a hw keyboard :0
<parazyd> :)
<mtnman> i have a bt keyboard
<mtnman> i need a bt mouse though
<parazyd> Maemo is made for hw keyboards really, but it's still usable on touchscreen-only devices
<uvos> mtnman: regular stuff alls applies
<uvos> we dont have a phone dialer etc
<uvos> *also
<mtnman> phone dialer is a big hole to fill
<uvos> right
<mtnman> i would actually enjoy being able to make phone calls with it
<parazyd> They work through the command line
<parazyd> And recently there is sphone which could serve as a usable dialer
<uvos> note: dosent work atm
<mtnman> uvos what doesn't work atm?
<uvos> sphone
<mtnman> ah
<uvos> (our dialer)
<mtnman> so its command line only...? using modemmanager?
<uvos> ofono
<mtnman> ok
<mtnman> well i have enjoyed running devuan on beagleboneblack and i enjoyed using maemo on n900 so maybe i wil give leste a shot on the pinephone
<parazyd> :)
<mtnman> are there bootable images or do i need to do an install?
Twig has quit [Ping timeout: 265 seconds]
<parazyd> Yeah on maedevu.maemo.org/images
Twig has joined #maemo-leste
<mtnman> parazyd: thanks for the link
<mtnman> whats the "dont-be-evil" version? free software only?
<parazyd> No, that was one of the devkits
<uvos> dont-be-evil is a prototype pp
<mtnman> so don't use that one?
<parazyd> No
<uvos> not unless you have a prototype pp
<mtnman> i have 3 gb version
<parazyd> Should work
<mtnman> so pinephone directory i presume
<parazyd> Yes
<mtnman> ok great. are there some instructions around for loading it onto sd card? i presume similar process to BBB
<mtnman> and should i use the latest image dated yesterday?
xmn has joined #maemo-leste
<parazyd> Yeah you can try the latest one
<mtnman> any suggestion where to look for instructions on loading to sd?
<mtnman> parazyd: thanks again
<parazyd> yw
<Wizzup> parazyd: ah, nice @ openrc-init
<mtnman> parazyd: any recommendation on partition size? i have a big card but would like to have the option of loading another os.
<parazyd> mtnman: Whatever you prefer, just don't make it smaller than the image
<mtnman> ok. how does it work for voice? pmos has been pretty spotty for voice calls
<parazyd> You'll have to try it out :p
<parazyd> There's ofono scripts
<parazyd> You install them with apt
<Wizzup> I also brought a pinephone with me, but I usually use the droid4 more
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
<lel> clort81 closed an issue: https://github.com/maemo-leste/bugtracker/issues/510 (Droid4: Add updated hw keyboard map to leste image.)
<mtnman> anyone know where i can get a new usb charging socket installed on a disabled n900?
Danct12 has quit [Ping timeout: 252 seconds]
<mtnman> i guess thats ot here
<stan> talk.maemo.org has a thread about those repairs
<parazyd> There's stuff on the Maemo forums for DIY I'm sure
<Wizzup> uvos: do you think we should have device specific salutem pages?
<uvos> Wizzup: maybe
<Wizzup> mtnman: it's not really off topic, but it's not easy to do
<uvos> Wizzup: ofc just putting the html file into leste-config is no issue
<Wizzup> uvos: like a page with the d4 keyboard keymap or something
<Wizzup> right
<uvos> Wizzup: sure sounds reasonable
<uvos> Wizzup: i wont be doing the html pages
<uvos> Wizzup: as you know that would result in lots of spelling errors :P
<mtnman> wizzup: i'd been hoping there might be some spare boards floating around the neo900 project but it seems do be dead
<stan> there are many spare boards with defective USB for you to practice soldering on
<uvos> hehe
<Wizzup> mtnman: depending on your level of maemo leste involvement I could try to send you a device
<mtnman> i have a device i'd like to repair.
<mtnman> wizzup: thanks for the offer. i would be involved basically as a tester
<uvos> Wizzup: since salutem just takes a -t parameter for the html file
<uvos> Wizzup: i think we should keep the main html file commen
<Wizzup> I will have to check at home what the state of my n900's are, but I can send a droid4 or bionic for sure
<uvos> and then have a .dekstop link we ship with device specific help
<Wizzup> uvos: sure, parazyd and I were thinking of making some pdf/html doc version as well based on restructured text, we could use something like that
<uvos> sure
<mtnman> would really like to repair the socket or switch out the board
<uvos> just for mainitinaince ease
<uvos> the device specific file would likely never change
<Wizzup> uvos: oh yeah it's here, ofc unfinished https://github.com/maemo-leste/leste-manual
<uvos> while the page salutem shows on startup would
<uvos> Wizzup: right great :)
<uvos> Wizzup: i wont be contributing any documentation
<sicelo> mtnman: you can repair it yourself, as long as you're careful, and maybe watch a YT video or two on SMD soldering. I did it on mine back in 2015/16, with zero prior experience, and a regular 30W soldering iron
<sicelo> fixing the USB might be better than swapping the mobo - as replacement mobo could have other issues, esp. the dreaded dead modem issue
<Wizzup> uvos: yeah, it might make sense to just have salutem work with this content before we push it out
<uvos> Wizzup: sure
<uvos> Wizzup: unless salutem needs code changes, which i would like to do myself then, just go for it :)
<Wizzup> ok, I have no idea how navigation inside it would work :p
<Wizzup> maybe a larger manual as pdf/epub should be separate from the help/changelog
<uvos> it would not
<uvos> i was thinking just 2 pages
<uvos> reached by 2 .dekstop files
<uvos> one with changelog
<Wizzup> uvos: well our leste manual will likely be large
<uvos> and another device manual
<uvos> ok
<uvos> well then you need a real html engine
Daanct12 has quit [Quit: Quitting]
<Wizzup> or we can use our pdf viewer
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
<uvos> that doesent work btw
<Wizzup> the pdf viewer doesn't work for you?
<uvos> i sefaults on 100% of pdf files i tryed it with
<Wizzup> really?
<uvos> yes
<Wizzup> care to share some?
<uvos> uh
<Wizzup> I've used it on various PDFs and it worked fine for me
<Wizzup> We need to upgrade the Xpdf core, but it shouldn't be that old/crashy
<sicelo> btw, Fremantle comes with html docs in MyDocs, iirc. I might have deleted mine
inky has joined #maemo-leste
<uvos> Wizzup: it segfaulted on the first one i tryed
<uvos> Wizzup: sec ill upload it
<uvos> i tryed a few more
<uvos> it segfaulted on all but one
<uvos> it also segfaults if you open a file
<uvos> and then open another
<uvos> even if the other file is a copy of the first
<uvos> (that otherwise works)
<uvos> so yeah
<uvos> pdfreader might as well not exist as far as reliability goes
<uvos> we should maybe preload something else as an example app :P
<Wizzup> uvos: that's a 404 for me
<Wizzup> uvos: It never crashed on me so I'm surprised
<parazyd> uvos: It opens here
<parazyd> Opening again does crash
<stan> mupdf handles that one fine
<stan> convenient finger scrolling as well
<stan> not that i want to discourage our maemoized-developments
<Wizzup> try to exit fullscreen mupdf without keyboard
<stan> yep
<Wizzup> uvos: it opens just fine for me
<Wizzup> (vm)
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
<stan> are you talking about the "pdf reader" installed with the image?
<uvos> on another try it did open for me
<uvos> but then it crahsed when i tried scrolling around a bit
<stan> or Dorian?
<uvos> now it crashed on first open again
<uvos> Wizzup: smells memory corruption
<Wizzup> uvos: we could attach gdb and see
<uvos> try with valgrind on vm
<uvos> anyhow ttyl
Twig has quit [Remote host closed the connection]
ceene has quit [Ping timeout: 272 seconds]
<stan> it should be easy to configure some 'virtual keyboard' daemon to trigger selected keystrokes with the offscreen area of the touchscreen
akossh has joined #maemo-leste
<freemangordon> Hi!
<stan> hello
<Wizzup> freemangordon: hi
<mtnman> successfully running maemo-leste on PP
<mtnman> thanks to all
<Wizzup> mtnman: please let us know what works / doesn't work for you
<mtnman> ok first thing: i don't see a sim card indicator or setting anywhere
<Wizzup> ok, yeah, give me a few minutes, I'll answer
<mtnman> ok
inky_ has quit [Ping timeout: 265 seconds]
inky_ has joined #maemo-leste
<Wizzup> mtnman: hi
<mtnman> hi
<Wizzup> mtnman: so there are packages to add the cellular applets and such, but they are quite alpha
<mtnman> okay...
<Wizzup> I need to see if we already have a meta package for it (I think so?), and if you install those, you should see the network status and/or sim status
<Wizzup> parazyd: do you recall if we already have the cellular meta?
<mtnman> that would be great
<parazyd> Wizzup: Yes in devel only
<Wizzup> parazyd: hildon-connectivity-cellular then? or?
<parazyd> -mobile
<Wizzup> s/cellular/mobile/ ?
<Wizzup> mtnman: to clarify, our aim to be support as much as fremantle does, and more, but we have to re-write a lot, so it's not "finished"
<mtnman> i get that
<Wizzup> ok
<mtnman> does this mean editing /etc/apt/sources.list to get the devel stuff
<Wizzup> mtnman: so presumably if you add the 'devel' repo to sources.list, and apt update, and then install hildon-connectivity-mobile, you should get those packages
<mtnman> ok sounds fairly straightforward
<Wizzup> what works for me is the status applet and the signal strength and technology, and I think on boot it should ask you for pin with gui if you have one set
<Wizzup> it should also automatically provision a data network if all goes well
<Wizzup> actually connecting to it will require a few attempts, which is a known problem
<Wizzup> the 'phone' part of the control panel *might* open, but it's not useful at this point
<mtnman> thus necessitating dialing from command line
<Wizzup> mtnman: well, this was about the control panel phone applet, like to change pin/puk, or set up call forwarding and such
<Wizzup> There is no GUI dialer yet, indeed, but we found sphone the other day which seems like it might suit us quite well
mardy has quit [Quit: WeeChat 2.8]
belcher_ is now known as belcher
<mtnman> is there a way to boot a pinephone from internal storage rather than sdcard without removing the card?
mtnman has quit [Quit: Lost terminal]
<parazyd> Probably, if you edit boot.scr
<stan> do any other target-phones for maemo-leste have offscreen touchscreen 'buttons' that can be mapped to keys? is there a "right way" to set that up?
<stan> i was thinking maybe pageup, pagedown and escape might be useful
cockroach has joined #maemo-leste
<stan> woah, they are already?
ceene has joined #maemo-leste
akossh has quit [Quit: Leaving.]
uvos has quit [Ping timeout: 272 seconds]
<stan> thank you for "Emergency Shell" on lcd tmlind.
<stan> saves me from pulling the sdcard to fix some goofups
Pali has quit [Ping timeout: 258 seconds]