Skip to content

Latest commit

 

History

History
88 lines (45 loc) · 10.5 KB

tasks-and-changes-todo.md

File metadata and controls

88 lines (45 loc) · 10.5 KB
Raw

Tasks and changes to do

This list of suggested changes is for those Sailors hackers or Jolla employees that wish to improve SFOS. It is divided into two parts. The list of tasks, which are activities that received some sort of investigation, and the list of requests for change, which are just described without any further investigation activity.

LIST OF TASKS TO DO

  • provide a not truncated LVM userdata filesystem image (here);

  • improve and fix the hybris-recovery.img shortcomings (here);

  • take care of the short-comings listed into this post (here).  

  • an easy way to deploy of the A-GPS config for X10 II and III (here) moreover about Settings:System -> Location:Location -> device only mode, it should disable the A-GPS functioning also at least for the part which communicates / requests data from remote sources. IMHO, the A-GPS inevitably does that, thus disabling it completely, it is the only safe way of fulfilling the device only user choice/will.

  • energy saver at 50%, 100% battery threshold and hysteresis at 87% is too much, 85% at least (here) also for 80% the 75% hysteresis threshold is suggested. Probably the 95%-90% and 80%-75% would address the needs of those that have a fully functional battery and those that do not.

  • implementing power saving templates (here) to better dealing with Bluetooth crazy CPU usage (>here) and (here).

  • adding more options for device lock considering that 1 minute seems to be the finest granularity. (>here).

  • provide a fingerprint restart icon/link in lockscreen (>here) but probably the best approach is to start sailfish-fpd service just in those few cases - just two - it is needed and bring down soon after it did its work.

  • add an option for disabling the Android Support autostart and keep it sleeping/ready to start. (here).

  • add an option in the native browser to let it keep alive a background tab that is doing some tasks like playing music. (>here).

  • this solution about URLs encoding (>here) + sanitisation should be applied also to shared links in particular with native browser that fails to open those URLs that did not just converted.

  • transition to the "user situational approach" in setting the smartphone behaviour models. (here).

  • in the Patch Manager patch list page a (de)activation "tap to undo" grace time needs to be added. (here).

  • add a permanent tethering setting because restarting the network WiFi tethering fails to raise up but WLAN, instead. (>here).

  • fixing the bash regression, a request to include it as standard again. (>here).

  • add a toggle button to inhibit SSHd for every interface but USB tethering. (>here).

  • add a timeout to disable WiFi tethering when unused for a certain time. (>here).

  • add a QRcode creation to access the WiFi network in Setting -> WiFi Sharing page. Unless the PIN / password or the finger print to show the password will unblur also the QRcode (>here).

  • a cron task scheduled @reboot  is needed to fix some files in users/root home that have too relaxed permissions set. (>here).

  • develop a regular expressions pre-parser/sanitiser to deal with iptables rules for connman (>here).

  • bring Patch Manager + Web Catalog to the next level and change the crime novel into a love story fo Sailors (here).

  • filesystem overlay tricks too old versions of filesystem utils like cp and tar but possibly also prevents that modem/GPS can be correctly configured (here).

  • try to optimise the native browser about:config, some suggestions (>here).

  • Considering the USER BACKUP section of this guide, the Settings:System → System:Backup can be put in condition to work also using SSH connection. Below the “Add cloud account” can be added a button for “Use the SSH connection” with brief instructions. Then, also the restore procedure can be added.

  • Evaluate a better and more general approach to backup and restore (here).

REQUEST OF CHANGES

  • the sleep 1 takes between 1s and 12s to expire on Xperia 10 II despite the power saving mode but power saving makes this HUGE time jittering more probable. This should be fixed because it can create more nasty problems and it is an indicator (common root cause, I suppose) of HUGE lag in interactive processes.

  • when ofono service starts the GPS/modem has just read the configuration files from the original vendor partition not from the root overlay under which is mounted and this is the main reason because it is always a cold start.

  • add a quick access to Android settings menu which at the moment is available with Settings:System -> Android Support -> Show Licences -> (back).

  • top menu can open the Settings:System menù but in that case it should fork the call otherwise pulling down the top-menu causes the child to die and the top menu to retract delivering a bad user experience.

  • in top-menu, SIMs items can be put on the same line with the locking screen icon in such a way to save vertical space.

  • a single tap on the background raises the first line of the app menu but that raise should be sticky (configurable timeout where 0 means sticky) because usually it lasts too less for being useful.

  • VPN icon in the top-menu is highlighted when a data connection is active and shows the name of the config used. Unfortunately, when no data connection is available it turns grey with the standard VPN label. This confuses the user about whether the service is enabled for raising the next connection or not. There are two ways to deal with this lack: 1. keep the icon highlight but rename its label in VPN or 2. turns grey but keeps the label about the name of the configuration. In both cases, the user should be forbidden to rename the VPN connection as VPN with a case insensitive check also for the file import feature. For a quick 1st implementation, I suggest replacing the label in VPN:ON when the VPN is not connected but ready to connect and VPN:NO otherwise. Another way of delivering this information is to add a green/grey dot to the VPN icon.

  • in topmenu the Connect to Internet icon/menu is appallingly useless because everybody uses WiFI / Mobile data icons as long as data is a limited/charged resource while Wifi is not. Moreover the SIM choice in dual-SIM devices is granted in the top menu. Thus Connect to Internet especially if a long press on a SIM leads to the SIM setting menu. Instead, an icon to access the Settings:System -> Connectivity:Mobile network is missing.

  • Pure Black Theme and Pure Black Backgrouds should be delivered with the installation image (installed by default) because they participate in the energy saving policy in OLED devices. An option for the auto-enabling power save mode can be added to switch temporarily to these pure-black settings belows a certain battery threshold. For example 20% energy saving, 10% pure black mode but the user can also choose 10% energy saving, 20% pure black mode.

  • device unlock max number of tires - it is not clear what the devices is going to do about it: a) offering new set of retries after a reboot; b) lock forever until a recognised fingerprint is given but it does not work during rebooting volume deciphering this is a quite dangerous statement, thus to exclude; c) delete permanently the user data erasing the LUKS key which can be a nice feature to have in combination with a resetting to standard installation as long as the user explicitly choose this option and s/he should not allowed to. In fact, what happens if the smartphone falls in the hands of someone that makes all the tries just for playing with it or with the precise intention of deleting your data or letting them inaccessible? The best is that after N tries, a timeout 2x-increasing is set and displayed on the screen: 15min, 30min, 60min, 2h, 4h, 8h, 16h, etc.

  • add an emergency immediate user data deletion / reset inserting a special PIN during the request of the device unlock PIN both during the boot or the screen unlocking procedure. A way to implement this, is a secure erase of the LUKS key and continue/force the reboot which will land to a default SFOS installation in such a way the smartphone will be brought back to the factory settings. About the SD/MMC card inside if it is present: a similar procedure can be performed but only if the user decided to encrypt it otherwise it is assumed that data is not sensitive by choice.

  • these adaptation0 aliendalvik sailfish-eas xt9 repositories are enabled by default, but it is wrong because they can be refreshed only when the device has a Jolla account. Otherwise, a relative long timeout for each of them keeps the refresh procedure stuck. Therefore, the Jolla account creation and deletion actions must take care of enabling and disabling them, which must be set as disabled by default.

  • do not let lxc@multi-user.service fails for no reason.