Wizzup | uvos: the d3 image boots, but it's unstable in the sense that it resets, but this is an unfortunate known problem | 17:06 |
---|---|---|
Wizzup | heh: https://www.ebay.com/itm/265510509076 | 17:12 |
Wizzup | hm, I don't see any apps in the launcher on the d3 though | 17:18 |
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>) | 17:18 |
huckg | The control panel on my bionic says 'Battery calibration needed'. How is that done? | 17:21 |
Wizzup | typically by letting the battery drain almost entirely and then charge it | 17:24 |
huckg | thanks. | 17:27 |
Wizzup | how is it working on you, the bionic, in general? | 17:28 |
* Wizzup is wondering what the biggest pain points are | 17:29 | |
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. | 17:31 |
Wizzup | these might be maemo patches here: maemo.org/packages/view/gpodder/ | 17:34 |
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. | 17:34 |
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 | 17:34 |
huckg | Oh yeah, I forgot about the button. | 17:35 |
Wizzup | I suspect the gpodder on maemo.org is very old, but the ui patches probably made it quite usable | 17:37 |
Wizzup | http://maemo.org/downloads/search/application.html?org_openpsa_products_search%5B1%5D%5Bproperty%5D=title&org_openpsa_products_search%5B1%5D%5Bconstraint%5D=LIKE&org_openpsa_products_search%5B1%5D%5Bvalue%5D=gpodder&org_openpsa_products_search%5B2%5D%5Bproperty%5D=os&org_openpsa_products_search%5B2%5D%5Bconstraint%5D=LIKE&org_openpsa_products_search%5B2%5D%5Bvalue%5D=Maemo5&fetch=Search | 17:37 |
huckg | I will try that gpodder out sometime today, and report back.. | 17:48 |
huckg | What is the thinking behind not using the volume buttons to control volume? | 17:58 |
humpelstilzchen[ | they could not decide which button increases and decreases volume :D | 18:01 |
sicelo | huckg: what does the volume button do? | 18:21 |
Wizzup | huckg: I was hoping the gpodder there would be a set of patches on top of gpodder, but it doesn't seem to be | 18:46 |
Wizzup | huckg: so it might be harder to take the maemo patches | 18:46 |
Wizzup | huckg: try apt install maemo-statusmenu-volume | 18:46 |
Wizzup | huckg: and then pkill status | 18:46 |
Wizzup | (wrt volume) | 18:46 |
Wizzup | but a few more things are necessary, like the pa line uvos mentioned | 18:47 |
Wizzup | humpelstilzchen[: it's funny, but not quite true, other things lack | 18:47 |
Wizzup | humpelstilzchen[: ;) | 18:47 |
humpelstilzchen[ | scnr | 18:54 |
Wizzup | :P | 19:00 |
huckg | sicelo: The volume button will change the size of the font in the terminal. | 19:02 |
huckg | volume up -> bigger text, volume down->smaller text | 19:11 |
Wizzup | uvos: btw, debugfs is not mounted in the images it looks like | 19:13 |
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 | 19:23 |
Wizzup | huckg: yeah you might be missing the line in system.pa | 19:34 |
Wizzup | brb dinner first | 19:34 |
huckg | bon appetit! | 19:35 |
freemangordon | there is no arguing on what volume buttons should do: | 19:46 |
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) | 19:47 |
freemangordon | if the device is rotated so the buttons are on top, left button decreases, right increases | 19:48 |
freemangordon | 'rotated' means the orientation of top application or desktop | 19:48 |
Wizzup | sounds like we need to wake up, read from accelerometer upon button press and then decide what to do ;) | 20:03 |
Wizzup | huckg: so I think you need this: 00:31 < uvos> we should load-module module-switch-on-port-available for pulse | 20:03 |
freemangordon | Wizzup: we don;t really need accel, why is that? | 20:05 |
Wizzup | how will the device know it's orientation? pretty sure we suspend reading from accel on device lock | 20:05 |
freemangordon | tklock knows what orientation it was activated in | 20:05 |
Wizzup | why would volume press activate the lock screen | 20:06 |
freemangordon | it should not | 20:06 |
freemangordon | but, it shall increase the volume | 20:06 |
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 | 20:06 |
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 | 20:07 |
Wizzup | if that makes sense | 20:07 |
freemangordon | Wizzup: have you ever had issues with that on fremantle? | 20:08 |
Wizzup | yes, I think so | 20:08 |
freemangordon | I never had | 20:08 |
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 | 20:08 |
freemangordon | but then again, this should not be device specific | 20:08 |
Wizzup | again, I don't have a strong opinion either way | 20:08 |
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) | 20:09 |
Wizzup | which I consider to be a bug | 20:09 |
freemangordon | I would not, as top application gets the control. to me this makes sense | 20:09 |
freemangordon | but yeah, this is arguable | 20:10 |
Wizzup | I mean if the device is locked | 20:10 |
freemangordon | sure | 20:10 |
Wizzup | I don't think it matters what activated app is when the device is locked | 20:10 |
Wizzup | but yeah | 20:10 |
freemangordon | it grabs, why should tklock or anyone override the grab? | 20:10 |
Wizzup | iirc there is special hack for that grab in fremantle | 20:11 |
Wizzup | probably why they couldn't make it work otherwise, but I don't remember | 20:11 |
Wizzup | they're edge cases to me anyway | 20:11 |
freemangordon | yeah, those are edge cases we can think of best solution to | 20:11 |
freemangordon | but in general I insist on having the behaviour I described ^^^ (when not locked) | 20:12 |
freemangordon | we shall discuss what is the best when locked | 20:12 |
freemangordon | like, make a list of use-cases and decide | 20:12 |
Wizzup | sure, when not locked I agree it makes sense | 20:12 |
freemangordon | I can think of 2 only (phone and media player) | 20:12 |
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 | 20:13 |
Wizzup | (mostly comes back to the fact that I don't care so much :p) | 20:13 |
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 | 20:13 |
freemangordon | maybe having orientation independent control when locked makes sense | 20:15 |
freemangordon | but I still think we shall take various use-cases before making a decision | 20:15 |
freemangordon | like - what if we are locked with keyboard open? | 20:16 |
freemangordon | that means we are in landscape, no? | 20:16 |
Wizzup | yes | 20:17 |
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 | 20:19 |
freemangordon | just tested | 20:19 |
freemangordon | and that makes all the sense to me | 20:19 |
Wizzup | to me it sounds like an oversight | 20:20 |
Wizzup | because what often happened for me is I would play music in landscape, get on my bicycle, put n900 in my pocket | 20:20 |
Wizzup | then during biking I would take out the phone with one hand and try to change volume, which is easier with portrait grab | 20:20 |
freemangordon | yeah, I understand your point | 20:21 |
humpelstilzchen[ | When I'm on the bike I change the volume while the device is in my pocket | 20:21 |
humpelstilzchen[ | this requires me to know which button is up and which is down | 20:21 |
freemangordon | could be, the current behaviour is the natural and intuitive, but again, we may change that | 20:21 |
freemangordon | to me is natural I mean | 20:22 |
Wizzup | or just let people configure it with gconf setting :) | 20:23 |
freemangordon | but, we may assume portrait orientation when locked and no keyboard is opened | 20:23 |
Wizzup | humpelstilzchen[: btw, does the modem work on the pp for you? | 20:23 |
freemangordon | Wizzup: I think we shall start writing configuration application | 20:24 |
humpelstilzchen[ | Wizzup: no sim here | 20:24 |
freemangordon | "Maemo Tweaks" in cpl | 20:24 |
Wizzup | humpelstilzchen[: ok, but it is detected? | 20:24 |
Wizzup | freemangordon: right, there is a maemo tweaks app in cssu :P | 20:24 |
Wizzup | I loved using that on my n900 when cssu came out | 20:25 |
humpelstilzchen[ | Wizzup: how do I check? | 20:25 |
Wizzup | change the transitions and stuff | 20:25 |
Wizzup | humpelstilzchen[: hmm download https://packages.debian.org/stretch/arm64/mdbus2/download and then run mdbus2 -s org.ofono | 20:25 |
freemangordon | Wizzup: I had bad experience with it, iirc | 20:26 |
freemangordon | I think we shall write something from scratch | 20:26 |
humpelstilzchen[ | stretch? lol | 20:27 |
* freemangordon is afk | 20:27 | |
Wizzup | humpelstilzchen[: mdbus2 is not in the newer distros I think | 20:30 |
Wizzup | humpelstilzchen[: it's just a debug tool | 20:30 |
humpelstilzchen[ | yes, I remember it from n900 days | 20:30 |
humpelstilzchen[ | and removed: https://packages.qa.debian.org/m/mdbus.html | 20:31 |
humpelstilzchen[ | mdbus2 -s org.ofono has only bluetooth stuff | 20:32 |
Wizzup | ok, so I don't think it sees the modem then | 20:32 |
Wizzup | so I have the same problem | 20:32 |
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. | 20:45 |
Wizzup | huckg: ah, you might not have the latest fixes! | 20:53 |
Wizzup | what version do you have? | 20:53 |
Wizzup | ii maemo-statusmenu-volume:armhf 0.56+2m7.1 armhf Volume status menu plugin | 20:53 |
Wizzup | (dpkg -l maemo-statusmenu-volume) | 20:54 |
huckg | I do have that version. | 20:55 |
Wizzup | hmm | 20:56 |
Wizzup | ah, no, I definitely do not have that bug | 20:56 |
Wizzup | uvos: maybe some weird behaviour on bionic? | 20:57 |
huckg | I will comment out that line in system.pa for now.... | 21:36 |
Wizzup | check | 21:49 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!