Quickbar enables access to the most recently used apps directly from the lockscreen and the task switcher.
Launch your favourite app in seconds!
AUTOSTART SCRIPTS ARE AVAILABLE!
See debota-utilities rpm package below.
NOTE : DOWNLOAD ON YOUR OWN RESPONSABILITY!
I AM NOT RESPONSIBLE FOR ANY DAMAGE MADE TO YOUR PHONE / SYSTEM!
In order to install, you are required to enable installations from third-party source.
Download link below, sources are here (github)
Feel free to post comments to https://together.jolla.com/question/47944/quickbar-discussion-support-thread/
If you like our work; if you like to be #unlike; help in keeping our Rocket well fueled! Donate!
NOTE : Donating from Quickbar directly is not straightforward (most likely due to a browser issue):
* to enable login button, press enter after entering the password (mandatory).
Bitcoin wallet address :
1Ayx665f3dHEKMHT389qcZTwsibfyW122a
Flattr : tortoisedoc
Quickbar gives access to the most recently launched apps from lock screen as well as the task switcher in SF 2.0
To run:
To uninstall:
If you want to Support us, use the links above - and thanks! :)
Note:
IF YOU INSTALLED QUICKBAR FROM HARBOUR : UNINSTALL BEFORE INSTALLING THIS VERSION!
If you do not uninstall the harbour vesion first, SailfishOS will automatically re-sync to it once the installation is done!
We are working to improve QuickBar's usability constantly. Suggestions are welcomed.
Attachment | Size | Date |
---|---|---|
harbour-debota-0.36-145.armv7hl.rpm | 122.67 KB | 27/09/2015 - 21:39 |
debota-utilities-0.4-12.armv7hl.rpm | 2.98 KB | 12/11/2016 - 22:19 |
harbour-debota-0.65-199.armv7hl.rpm | 125.93 KB | 02/04/2017 - 09:12 |
harbour-debota-0.70-209.armv7hl.rpm | 127.09 KB | 02/03/2018 - 01:17 |
harbour-debota-0.80-222.i486.rpm | 149.1 KB | 03/04/2018 - 21:02 |
harbour-debota-0.90-234.i486.rpm | 143.52 KB | 19/06/2018 - 00:19 |
harbour-debota-0.90-234.armv7hl.rpm | 135.13 KB | 19/06/2018 - 00:19 |
harbour-debota-0.91-235.armv7hl.rpm | 140.13 KB | 19/03/2019 - 01:00 |
harbour-debota-0.93-238.armv7hl.rpm | 139.4 KB | 29/03/2019 - 00:23 |
harbour-debota-0.93-238.i486.rpm | 148.24 KB | 29/03/2019 - 00:23 |
harbour-debota-0.95-242.armv7hl.rpm | 137.19 KB | 22/02/2020 - 00:48 |
*DEBUG BUILD : 0.95.242 (salamaisku)
- fix qml in search dialog
*DEBUG BUILD : 0.95.241 (salamaisku)
- compatibility with HW keyboards for search dialog
*DEBUG BUILD : 0.95.240 (salamaisku)
- compatibility with HW keyboards for search dialog
*Bugfix release 0.91.235 (keväkuume)
- Compatibility fix on Oulanka
*New in version 0.90.234 (kesäkuume)
- !NEW! Added search functionality for apps finding
- fixed bugs in android launcher (side-invoked apps were not properly recognized)
*New in verison 0.80.222 (kevätuuli)
- Build for i486 (tablets & co)
*New in version 0.70-209 (pakkaste)
*New in version 0.65-199 (keväthiiri)
*New in version 0.63-194 (räntä)
*New in version 0.61-187 (phoenix, patchrelease "ega")
- fixed compatibility with previous OS versions (previous than 2.0.1, included )
*New in version 0.6-185 (phoenix)
- fixed input issues (finally!)
- rewrote qml code, now things are cleaner (and more maintainable)
- added shortcuts bar on top of quickbar for easy switching (swiping still available)
- added necessary things to make autostart available
- minor tids & quirks here and there
*New in version 0.5-163 (odyssey, patchrelease Circe)
- background is transparent now :)
- fixed transition / mouse sensitive bugs
- few corrections to settings screen
*New in version 0.5-161 (odyssey)
- SFOS 2.0 adaptation; which means:
* Back to the roots : Horizontal quickbar accessible by click on status bar (currently in lockscreen / task switcher only)
* Quicklaunch mode : last (from quickbar) started application gets launched automatically unpon unlocking the phone (i.e. when you press shoulder button to put screen on) TEST, see notes above, WIP
*New in version 0.28.96 (hiiri)
WARNING : THIS IS A COMPATIBILITY RELEASE FOR UITUKKA ONLY! IT IS NOT TESTED ON PREVIOUS RELEASES!
*New in version 0.16-75 (rautatie)
- First attempt at more detailed integration
NOTE : Still buggy, in case your Quickbar disappears on the lockscreen, unlock (aka close lockscreen) and it should reappear the nex time you go to lockscreen
- Support for LPM mode :)
*New in version 0.15-69 (saari patch-fix)
- Fixed swipe option for real
- Now app stops upon uninstall
*New in version 0.14-68 (saari)
Saari was supposed to be a patch fix for merenranta, instead it ended up including a new feature
(device lock support), hence it got upgraded to stand-alone release.
*New in version 0.12-43 (merenranta)
*New in version 0.10-30 (heinaallergia)
*New in version 0.9-22
*First version (beta)
Known issues:
See https://together.jolla.com/question/47944/quickbar-discussion-support-th... on tjc (registration required)
Comments
x01
Wed, 2021/01/13 - 20:29
Permalink
Blanks my screen black after activation on 3.4.0.4
GiuliettaSW
Fri, 2021/01/22 - 13:40
Permalink
Hi,
sorry for the misservice. Unfortunately, at the moment quickbar is not supported on ver > 3.4,
we are trying to get it there tho.
Kabouik
Mon, 2020/05/04 - 12:38
Permalink
No problem. Actually I just checked this comment section today to see if there was any news, so I'm glad to see I didn't miss something and leave you waiting. :]
Kabouik
Sun, 2020/02/23 - 23:23
Permalink
Thanks for the update @GiuliettaSW. I can confirm the app now launches again, however still no keyboard input in the search field.
Regarding the tap on top side of the screen to trigger the bar, I understood that the issue is it is not dynamic: when holding phone in landscape mode, the touch area that triggers the bar remains the same and therefore is the left edge of the screen. Since the top edge is used by SFOS for the top menu and interferes, how about making Quickbar appear when touching the left side or the right side of the screen? This would also be much easier to use one-handed when using regular phones in portrait orientation.
GiuliettaSW
Mon, 2020/04/20 - 21:13
Permalink
Hello!
thank you for the feedback, and sorry for the long wait! Its been a busy month!
We are still looking into this, and will try to come back with more questions asap
Kabouik
Tue, 2020/02/18 - 16:50
Permalink
No problem, I've been busy with other stuff too lately, and even had to install Android temporarily (that was painful), but I'm back to SFOS and will have more time to check openrepos now.
Kabouik
Mon, 2020/02/03 - 03:21
Permalink
Count me in for testing yes, of course. And thanks for considering my comments! I just have to remember coming here regularly because openrepos has no notification system for users.
Regarding Quicklauncher, I used to keep it running at all times, so it just required tapping on the cover, typing two or three chars, and then hitting return from the keyboard. Alternatively, I had it in the top row of my app launcher, so I could just restore the window by typing on its icon from a swipe from bottom, then type chars, then Return; that's one swipe and icon tap like when launching a new app, except I could use the keyboard to select the app instead of looking for the right icon in the app launcher. SFOS 3 broke its code but the UI integration was very good, working the same way as other apps, portrait and landscape.
However, maybe I am not used enough to Quickbar and just missed features. I appreciate the bar feature as it really adds an extra functionality to the SFOS UI, but right now I don't know how to show it when the screen is unlocked, and some users might actually want to avoid the bar function when not needed because it differs significantly from the default SFOS spirit. But in any case, I will be happy to test any option you come up with!
GiuliettaSW
Wed, 2020/02/05 - 00:04
Permalink
Hei!
I added a debug build (0.95.240) here; I'd like to start small, and see if the basic qt key bindings work on sfos; as I have no hw keyboard and I cant seem to be able to get emulator to react to them, I added the minimal code to be able to detect key presses.
So to test, please :
- open quickbar (for example on the lock screen)
- switch to search component
- press some letters on your hardware kb -> they should appear on the filter field
We might be in luck, and it might *just* work. Then we'll see the next steps.
Kabouik
Wed, 2020/02/05 - 12:34
Permalink
Thanks for the quick update! I tried it but unfortunately it does not seem to recognize hardware keyboard input yet.
GiuliettaSW
Thu, 2020/02/06 - 23:31
Permalink
Hello!
One more attempt; please see if the latest updated package (0.95.241) works for you.
Kabouik
Tue, 2020/02/11 - 12:16
Permalink
Hey, sorry for my late answer, I had no time at all to tinker with my phone lately and had to leave many things aside. Unfortunately it seems I cannot run the version 0.95.241, I get this typical SFOS behaviour with a cover and the spinning icon, and then the cover just closes after some time.
[nemo@Sailfish ~]$ harbour-debota
[D] unknown:0 - Specified Desktop file does not exist "/usr/share/applications/harbour-lookingglass.desktop"
[D] unknown:0 - Using Wayland-EGL
[W] unknown:0 - QQmlComponent: Component is not ready
Segmentation fault (core dumped)
I am under the impression that this harbour-lookingglass.desktop issue might be caused by something else than the Quickbar update actually, but I have not experienced that with other applications so far and I do not know what the Looking glass application is, so not sure why some applications would require it.
GiuliettaSW
Mon, 2020/02/17 - 11:21
Permalink
Hello!
Sorry for the long silence, have been busy with other projects, but will deliver soon.
GiuliettaSW
Tue, 2020/02/11 - 21:34
Permalink
Hmm this seems worser than I thought, there's a full-blown crash here. I will double check with my jolla to make sure I didnt forget anything.
GiuliettaSW
Wed, 2020/02/05 - 13:01
Permalink
Okay thanks, so the native events are not propagated. A question, how does the hw keyboard interfacing work deep down? Do you happen to have info / links?
Kabouik
Tue, 2020/02/11 - 12:39
Permalink
Here's what someone (@netman, Discord F(x)tec server) who knows what he is talking about replied to your question:
"aw9523 chip for most keys, as an 8x8 matrix, talks to the soc via i2c; modifier keys directly to gpio. Oh @kabouik further info would be that port 0 on the aw9523 is used as input and has pullup resistors, and port 1 is used as the output for scanning the matrix."
The driver in use for SFOS is here: https://github.com/sailfish-on-fxtecpro1/kernel-fxtec-pro1/blob/hybris-m...
GiuliettaSW
Tue, 2020/02/11 - 21:36
Permalink
Thanks! That's very detailed info ^^ im impressed! I was actually thinking about the Qt side of things; evdevkeyboard i believe is the driver?
GiuliettaSW
Mon, 2020/02/03 - 03:21
Permalink
you tap on the top bar to make quickbar appear on the homescreen (at the bottom)
just noticed this is missing from the text :D
Kabouik
Wed, 2020/02/05 - 12:33
Permalink
Thanks, good to know! However, while it works sometimes, other times it just triggers the top menu (lock button + ambiences). I haven't found yet how to reliably show Quickbar using this. Also, quickbar shows only in portrait mode (hence on the right of the screen when holding it in landscape), which is actually convenient because it is easier to reach, but icons should rotate according to the phone orientation and the search field may need a few adjustments.
GiuliettaSW
Wed, 2020/02/05 - 13:00
Permalink
About the focus issue, does it happen also when quickbar is not running?
About the icon rotation, yes that's a known bug. Lets see what can be done once have the keys in place!
Kabouik
Tue, 2020/02/11 - 12:28
Permalink
By "focus issue", you mean the top menu peeking when tapping on the top bar? It happens even without Quickbar, yes, I think it became a default feature for SFOS.
Kabouik
Fri, 2020/01/24 - 00:08
Permalink
GiuliettaSW, do you think it would be possible to add additional settings toggles so that one can use only the app search function, not the others, and extend that to beyond just thelock screen? Something like Quick Launcher from Jolla Store for instance, except Quick Launcher stopped working with recent SFOS releases, and is unmaintained with closed source.
I am using a Pro¹, and an app launcher would really be a great thing on a phone featuring a hardware keyboard.
While I think the other features of Quickbar are nice to have on SFOS, I don't really need them and therefore would rather just have the search function readily available without the other tabs and mini app icons, but I am not sure how much work it would be.
Note also that currently the app search does not react to keyboard input.
Thanks for maintaining this very unique app!
GiuliettaSW
Wed, 2020/01/29 - 13:48
Permalink
Hello! Thank you for using quickbar!
So to recap, it seems we have two things here:
1) the possibility to focus on a specific functionality
2) a bug (keyboard input not working)
About 1):
It is not a big work for us to add the possibility to decide which functionality should be displayed as first one by default - i.e. currently is MRU, but this could be changed to be Search function for example. Would that woek?
About 2):
This is a use-case that was not considered! It will be very interesting to implement this, thank you for bringing this up, very good point! Just to understand correctly, you mean to search for the app you are looking for (from the search function) by typing on the keyboard (and the text would be filled in), correct?
EDIT : actually it would be even easier to automatically switch to the search feature, if:
- quickbar is visible
- keyboard is used
Kabouik
Sat, 2020/02/01 - 02:25
Permalink
Thanks for your answer.
1. The possibility to use only one (or some) functionality(ies), but also to use it/them from outside the lockscreen bar. For instance, Quickbar could have a cover mode (possibly selected on the screen when the user can close the options after launching Quickbar), and in this mode the SFOS cover would stay open. Tapping on this cover would restore a fullscreen app with the different modules shown, or just the module enabled (in my case, just application search). Ideally, there would even be two cover actions to (1) cycle through enabled modules and (2) perform associated actions without restoring the full screen app (reopen last app, type text search, etc.), but that would really be a bonus.
2. Absolutely, no input from hardware keyboards at the moment.
About 1: what you suggest would work, and it is great to hear it wouldn't be too much work. However, it would be nice to be also able to use the feature in a more regular SFOS way, from a cover/fullscreen app and not just a bar on the lockscreen. Actually, since Quick Launcher no longer works, Quickbar could offer the exact same features on top of the features it already has. Since there is already some text search to launch applications in Quickbar, this would be relevant. You can have a look at Quick Launcher, this really is the feature I would be looking for (and I assume other people would too, so perhaps that would bring additional users to Quickbar).
About 2: Yes, absolutely. Again, check Quicklauncher from the Jolla Store to have an illustration of the functionality.
GiuliettaSW
Sat, 2020/02/01 - 23:05
Permalink
Okay;
then we have a plan. I will see what can be done in the next days; shouldnt take long. Though, as I disagree about covers & Quick Launcher-type of use being more helpful thank quickbar (quicklauncher requires a swipe, a selection, the code, then the search / a click on the recent searchs I guess? vs quickbar one click + mru for example & it's only the code left - which is mandatory anyways) and being better integrated (the change from sfos 2 to 3 did not break quickbar), I will first start with the keyboard support for the search component, then move on on the full-page quicksearch. Would you be able to test ?
Termitebug
Tue, 2018/06/26 - 16:37
Permalink
Thanks for the update! The new search funtionality is good and I like it :) Also the app's setting page crash bug has been cured on Jolla Tablet (issue were when you tried to open 2nd time the settings, which then crashed every time). I don't anymore get "infinite" cover loop on Tablet.
GiuliettaSW
Tue, 2018/06/26 - 21:36
Permalink
Btw is the resolution of the settings page fixed now as well?
Termitebug
Wed, 2018/06/27 - 01:31
Permalink
Yes the resolution is fixed now on Tablet :). But imho the space between texts "Scroll for more options" and "In order to...." is too narrow. Could you make it a bit larger height? And in my opinion the scrolling doesn't serve a purpose for now when there is only 2 options. If you plan to add more functionality in future, the scrolling behavior should be free-mode instead of auto-centering.
GiuliettaSW
Tue, 2018/06/26 - 19:22
Permalink
Great to hear it works now! :)
About the timer; would something like a slidebar with a timer interval from the settings page cover your needs?
Termitebug
Wed, 2018/06/27 - 01:16
Permalink
Hmm... that timer idea would probably be a good thing :)
Termitebug
Thu, 2018/04/19 - 11:14
Permalink
Works on Jolla Tablet device now and as it is now. All though the settings page of the app needs resolution dpi tweaking. App is nice utility but not fully usefull (yet) to me. What I'm missing and wishing to be added are: 1) Quickbar UI hiding timer as it is too fast fading away from me, 2) a simple search (libsailfishapp/Quick Launcher) function by applications name, so I don't have to guess "now where I did put it?" :p.
I would like UI desing be. 1st. Active cover and app front page with app listing (by alphabetical) and includes search funtion. 2nd. Current settings page behind pulley/swipe menu. 3rd. Quickbar as it is.
Pages