<Wizzup>
hm, I don't see any apps in the launcher on the d3 though
<Wizzup>
probably some fs corruption: hd_launcher_tree_populate: Failed to load tree: Error on line 1 char 1: Document must begin with an element (e.g. <book>)
<huckg>
The control panel on my bionic says 'Battery calibration needed'. How is that done?
<Wizzup>
typically by letting the battery drain almost entirely and then charge it
<huckg>
thanks.
<Wizzup>
how is it working on you, the bionic, in general?
* Wizzup
is wondering what the biggest pain points are
<huckg>
I am using it for playing podcasts, I installed gpodder but the gui doesn't work: I can touch a menu and it opens, but I cannot activate any of the menu items. Then it will typically freeze up the device.
<Wizzup>
these might be maemo patches here: maemo.org/packages/view/gpodder/
<huckg>
A new issue I noticed today with the Calendar app: If I try to add a new event, the virtual keyboard does not come up when I click in the text box.
<Wizzup>
huckg: yeah, the virtual keyboard not auto showing in qt is a known problem, you can raise it with the button to raise the vkb, but we need to fix that
<huckg>
Oh yeah, I forgot about the button.
<Wizzup>
I suspect the gpodder on maemo.org is very old, but the ui patches probably made it quite usable
<Wizzup>
but a few more things are necessary, like the pa line uvos mentioned
<Wizzup>
humpelstilzchen[: it's funny, but not quite true, other things lack
<Wizzup>
humpelstilzchen[: ;)
<humpelstilzchen[>
scnr
<Wizzup>
:P
<huckg>
sicelo: The volume button will change the size of the font in the terminal.
<huckg>
volume up -> bigger text, volume down->smaller text
<Wizzup>
uvos: btw, debugfs is not mounted in the images it looks like
huckg61 has joined #maemo-leste
huckg has quit [Quit: Client closed]
huckg61 has quit [Client Quit]
huckg has joined #maemo-leste
<huckg>
Wizzup: I installed maemo-statusmenu-volume but moving the slider has no effect on the volume. alsamixer (no arguments) works, and I also made a tiny shell script that uses pactl set-sink-volume
<Wizzup>
huckg: yeah you might be missing the line in system.pa
<Wizzup>
brb dinner first
<huckg>
bon appetit!
<freemangordon>
there is no arguing on what volume buttons should do:
<freemangordon>
if the device is rotated such that buttons are on the side, uper volume button shall increase and lower shall decrease (volume, size, page, etc)
<freemangordon>
if the device is rotated so the buttons are on top, left button decreases, right increases
<freemangordon>
'rotated' means the orientation of top application or desktop
<Wizzup>
sounds like we need to wake up, read from accelerometer upon button press and then decide what to do ;)
<Wizzup>
huckg: so I think you need this: 00:31 < uvos> we should load-module module-switch-on-port-available for pulse
<freemangordon>
Wizzup: we don;t really need accel, why is that?
<Wizzup>
how will the device know it's orientation? pretty sure we suspend reading from accel on device lock
<freemangordon>
tklock knows what orientation it was activated in
<Wizzup>
why would volume press activate the lock screen
<freemangordon>
it should not
<freemangordon>
but, it shall increase the volume
<Wizzup>
if I lock the phone and put it in my pocket, and then take it out, I just want to increase or decrease the volume, not remember how it was last locked before I put it in my pocket
<Wizzup>
I don't care what tklock thinks its last orientation was, I want to know, purely based on phone orientation or just hardcoded, which increases and which decreases
<Wizzup>
if that makes sense
<freemangordon>
Wizzup: have you ever had issues with that on fremantle?
<Wizzup>
yes, I think so
<freemangordon>
I never had
<Wizzup>
but also I don't find the phone orientation always as reliable as possible (hw wise, not sw wise), which is a problem also on modern phones, where people want their stuff to rotate and it doesn't, so it's hard to make volume buttons work well in that scenario
<freemangordon>
but then again, this should not be device specific
<Wizzup>
again, I don't have a strong opinion either way
<Wizzup>
I just know that the fremantle behaviour wasn't always great for me (iirc if you lock with osso-xterm selected, it also doesn't do volume)
<Wizzup>
which I consider to be a bug
<freemangordon>
I would not, as top application gets the control. to me this makes sense
<freemangordon>
but yeah, this is arguable
<Wizzup>
I mean if the device is locked
<freemangordon>
sure
<Wizzup>
I don't think it matters what activated app is when the device is locked
<Wizzup>
but yeah
<freemangordon>
it grabs, why should tklock or anyone override the grab?
<Wizzup>
iirc there is special hack for that grab in fremantle
<Wizzup>
probably why they couldn't make it work otherwise, but I don't remember
<Wizzup>
they're edge cases to me anyway
<freemangordon>
yeah, those are edge cases we can think of best solution to
<freemangordon>
but in general I insist on having the behaviour I described ^^^ (when not locked)
<freemangordon>
we shall discuss what is the best when locked
<freemangordon>
like, make a list of use-cases and decide
<Wizzup>
sure, when not locked I agree it makes sense
<freemangordon>
I can think of 2 only (phone and media player)
<Wizzup>
to be entirely honest I'm not super psyched to make a use case list here and now, but I think we could make an issue on GH and put some proper arguments and use cases there
<Wizzup>
(mostly comes back to the fact that I don't care so much :p)
<freemangordon>
and I can assure you, it is very hard to forget which orientation you locked the device for those 2. It is a muscle memory basically, no need to think either
<freemangordon>
maybe having orientation independent control when locked makes sense
<freemangordon>
but I still think we shall take various use-cases before making a decision
<freemangordon>
like - what if we are locked with keyboard open?
<freemangordon>
that means we are in landscape, no?
<Wizzup>
yes
<freemangordon>
and I can assure you with media player running and playing a song, fremantle uses the orientation it was locked in to decide which button is what
<freemangordon>
just tested
<freemangordon>
and that makes all the sense to me
<Wizzup>
to me it sounds like an oversight
<Wizzup>
because what often happened for me is I would play music in landscape, get on my bicycle, put n900 in my pocket
<Wizzup>
then during biking I would take out the phone with one hand and try to change volume, which is easier with portrait grab
<freemangordon>
yeah, I understand your point
<humpelstilzchen[>
When I'm on the bike I change the volume while the device is in my pocket
<humpelstilzchen[>
this requires me to know which button is up and which is down
<freemangordon>
could be, the current behaviour is the natural and intuitive, but again, we may change that
<freemangordon>
to me is natural I mean
<Wizzup>
or just let people configure it with gconf setting :)
<freemangordon>
but, we may assume portrait orientation when locked and no keyboard is opened
<Wizzup>
humpelstilzchen[: btw, does the modem work on the pp for you?
<freemangordon>
Wizzup: I think we shall start writing configuration application
<humpelstilzchen[>
Wizzup: no sim here
<freemangordon>
"Maemo Tweaks" in cpl
<Wizzup>
humpelstilzchen[: ok, but it is detected?
<Wizzup>
freemangordon: right, there is a maemo tweaks app in cssu :P
<Wizzup>
I loved using that on my n900 when cssu came out
<humpelstilzchen[>
mdbus2 -s org.ofono has only bluetooth stuff
<Wizzup>
ok, so I don't think it sees the modem then
<Wizzup>
so I have the same problem
<huckg>
Wizzup: I added that line to /etc/pulse/system.pa and when I play an mp3 with the slider all the way down it starts playing at what sounds like full volume, then the device shuts itself down after a few seconds. Maybe that line needs to be at a certain place in the system.pa file? I just placed it at the end.
<Wizzup>
huckg: ah, you might not have the latest fixes!
<Wizzup>
what version do you have?
<Wizzup>
ii maemo-statusmenu-volume:armhf 0.56+2m7.1 armhf Volume status menu plugin
<Wizzup>
(dpkg -l maemo-statusmenu-volume)
<huckg>
I do have that version.
<Wizzup>
hmm
<Wizzup>
ah, no, I definitely do not have that bug
<Wizzup>
uvos: maybe some weird behaviour on bionic?
_inky has quit [Ping timeout: 256 seconds]
_inky has joined #maemo-leste
<huckg>
I will comment out that line in system.pa for now....