aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Setting to disable DFU and FS access (#1891)Dāvis Mošenkovs2025-09-0314-2/+171
| | | | | | | | | | | | | | * Expose SystemTask dependency controllers Expose NotificationManager and Settings for use by the feature in next commit. This is a memory efficient way for accessing SystemTask dependencies from controllers that have SystemTask injected as a dependency. Looks like each direct dependency injection uses 4 bytes RAM. As InfiniTime is close to running out of RAM (using 16 more bytes causes build to fail with "ld: region RAM overflowed with stack") it might be helpful to use this approach more. * Add setting to disable DFU and FS access
* navigation: fix greying out the app icon if not enabledHeiko Stuebner2025-07-0317-3/+64
| | | | | | | | | | | | | | | | Commit 0aead42fdf51 ("navigation: Add is available (#1847)") added the ability to draw the app icon in grey and in a disabled state when some prerequisits were not met. Only the Navigation app was using this mechanism due to its icons being stored in the external memory and possibly missing. Commit 63e0c4f4efb0 ("Application selection at build time") broke this by always setting the state as true: for (const auto& userApp : userApps) { apps[i++] = Screens::Tile::Applications {userApp.icon, userApp.app, true}; } Fix this by creating an isAvailable() strcuture in the app classes, similar to how the Watchfaces handle the same problem of checking availability.
* Dark App Launcher Tiles (#2294)Titus2025-06-291-2/+1
|
* (small) Music App Redesign (#2292)Titus2025-06-292-10/+10
|
* Analog face constexpr fixmark90642025-06-281-1/+4
|
* Initialise DisplayApp components in DisplayApp contextmark90642025-06-282-13/+12
|
* Disable legacy FreeRTOS functionsmark90642025-06-271-1/+1
|
* Pride flag watchface (#2201)Eshe2025-06-199-1/+469
|
* Ignore npm files (#2313)Owen from Canada2025-06-181-0/+5
|
* Set LF-only (\n) line endings for .sh files to fix #1905 (#2181)zyphlar2025-06-161-0/+3
|
* BatteryInfo App Redesign: Fixup (#2310)Titus2025-06-121-6/+9
| | | | * remove leading zeros from battery percentage * add correct colors matching the battery icon color thresholds
* set static text as static text (#2312)lmamane2025-06-121-3/+1
| | | | | and save a few bytes of heap memory Co-authored-by: Lionel Elie Mamane <lionel@mamane.lu>
* DisplayApp: use std::ranges function where possibleReinhold Gschweicher2025-05-301-16/+16
| | | | | Instead of raw for loops use `std::ranges::transform` where possible. And also use `std::ranges::find_if` instead of `std::find_if`.
* fixed libpango1.0-dev installkon-foo2025-05-301-1/+1
|
* CI: use bash for get-base-ref-size job (#2305)NeroBurner2025-05-291-0/+1
| | | | | | | | Same change as done in https://github.com/InfiniTimeOrg/InfiniTime/commit/c3295d6d2a325f9a7418b15b943342635026926e But for get-base-ref-size job The variable substitution I introduced are bash features. So they don't work with sh. Update the size job to use `bash` instead of `sh` as shell
* CI: use bash for output-sizs-jobNeroBurner2025-05-271-0/+1
| | | | | | | | | | Firmware build works. But the build size job afterwards fails. The firmware build uses `shell: bash --noprofile --norc -e -o pipefail {0}` as shell. The size job uses `shell: sh -e {0}` The variable substitution I introduced are bash features. So they don't work with sh. Update the size job to use `bash` instead of `sh` as shell
* docker: fix NRF_SDK download and subsequent build.sh (#2299)NeroBurner2025-05-271-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The upstream NRF-SDK download url and zip archive filename changed, which was fixed with https://github.com/InfiniTimeOrg/InfiniTime/pull/2270 But the archive contents stayed the same, with the "old" folder name. After #2270 we have basically the same docker-container as before the PR, but the `GetNrfSdk` function of the `build.sh` script is called again during firmware build time as the expected foldername for the SDK isn't the same as the zip filename: ```sh [ ! -d "$TOOLS_DIR/$NRF_SDK_VER" ] && GetNrfSdk ``` Then during the build the `buils.sh` script tries to execute `GetNrfSdk` again, which fails as the files already exist resulting in the following error: ``` replace /opt/nRF5_SDK_15.3.0_59ac345/components/802_15_4/api/HAL/hal_atomic.h? [y]es, [n]o, [A]ll, [N]one, [r]ename: NULL ``` Fix this by reverting the `NRF_SDK_VER` to the folder name in the zip archive and by some character replacement generate the download URL from the above (the download is in lower-case without the `_` and `.` characters). Furthermore add safeguards to check after the `GetNrfSdk` call if the expected folder is really created. Then we have an error early during container image creation if the contents of the zip-archive are unexpected.
* Refactors watch faces. Replace lv_tick_get() with xTaskGetTickCount()Steve Amor2025-05-234-6/+6
|
* Fix nRF SDK download links (#2270)Darius Arnold2025-05-212-3/+3
| | | nRF has moved the download to a new location- Update the build script to fetch from the same URL the download website currently provides.
* Fix conflict in NotificationManagerJean-François Milants2025-05-211-1/+1
|\
| * notification: Initialise messageFinlay Davidson2023-03-161-1/+1
| | | | | | | | | | | | Prevents reading uninitialised memory if notification gets cut off due to being more than 100 chars. The last character is assumed to be \0, but it is actually uninitialised.
* | fix: fix short ref not getting set in github buildsJulian Vos2025-05-211-1/+3
| |
* | Fix about screen vertical centering.Matt Zrinsky2025-05-191-1/+1
| | | | | | | | | | | | There was a newline at the end of the last line on the third screen, which was causing the label to not be centered vertically. Removing it fixes the centering.
* | Center text on timer button (#2229)Titus2025-05-161-2/+2
| |
* | Remove the vibration while charging (#1768)Max Friedrich2025-05-163-5/+0
| | | | | | | | | | | | | | | | | | | | | | * DisplayApp.cpp: Remove the vibration from OnChargingEvent This fixes a bug where the vibration interupts the physical connection with the charger and therefore triggers a new charging event and vibration, ending in a cycle of vibrations while charging. * remove OnChargingEvent message from DisplayApp --------- Co-authored-by: minacode <minamoto9@web.de>
* | Add background color to progress bar when flashing firmware (#2237)Titus2025-05-151-1/+5
| |
* | Simple calculator (#1483)Max Friedrich2025-05-128-1/+465
| | | | | | | | | | | | Co-authored-by: minacode <minamoto9@web.de> Co-authored-by: Finlay Davidson <finlay.davidson@coderclass.nl> Co-authored-by: SuIông N. <Boteium@users.noreply.github.com> Co-authored-by: mark9064 <30447455+mark9064@users.noreply.github.com>
* | Revert "docs: add git config items to docs"Max Jakobitsch2025-03-212-11/+2
| | | | | | | | This reverts commit 4066cc03004c89a7ac4d5a7a327729184ecac7b6.
* | docs: add git config items to docsMax Jakobitsch2025-03-212-2/+11
| |
* | chore: remove defunct .gitconfigMax-Julian Jakobitsch2025-03-211-5/+0
| | | | | | | | not actually used by git, see https://git-scm.com/docs/git-config and https://stackoverflow.com/q/18329621
* | Update Apps.mdLukas H.2025-03-211-1/+1
| |
* | make cmake command coherent with previous documentationLionel Elie Mamane2025-03-211-1/+1
| |
* | work around g++ version 12, 13 and 14 spurious warning (#2158)lmamane2025-03-141-0/+5
| | | | | | | | | | which is an error since we compile with -Werror Co-authored-by: Lionel Elie Mamane <lionel@mamane.lu>
* | BatteryInfo App Redesign using arc (#2236)Titus2025-03-142-21/+24
| | | | | | | | | | | | | | | | | | | | Redesign BatteryInfo App using an Arch widget instead of a bar. The colors I used are as follows: - Discharging (default): green - Charging: lime - Battery full: blue - Battery low (<10%): red
* | Fix Infineat crash when charging with AOD (#2256)Steveis2025-02-262-2/+6
| | | | | | | | Optimise the battery animation to not use 100% CPU (which causes DisplayApp to spin forever with AOD) (DisplayApp also needs to be fixed in the future so it cannot spin infinitely)
* | Fix EOL related build issues on Windows (#2077)Max Jakobitsch2025-02-111-2/+3
| | | | | | | | | | Prevent line endings from getting normalised to CRLF Co-authored-by: NeroBurner <pyro4hell@gmail.com>
* | Improve no notification text (#2238)Titus2025-02-101-2/+2
| | | | | | Change the "No notification" text to "No notifications"
* | Add "Run on InfiniEmu" link to pull requests (#2150)Felipe Martínez2025-01-281-0/+6
| |
* | Fixes #2219: use artifact v4 instead of v3Jozef Mlich2025-01-232-7/+7
| |
* | Alarm: Simplify alarm alerting screen (#2211)ljahn2025-01-212-3/+10
| | | | | | | | | | | | | | | | | | | | | | | | Simplify alarm alerting screen and fix bug with alerting on time value change SetAlerting creates an lv_task to automatically call StopAlerting after one minute. This task will call an invalid function reference and lead to a crash under the following condition: All exit paths but the time value change (so not considering this fix) call StopAlerting themselves, which also terminates the lv_task. However, the value change callback only calls DisableAlarm, because its normal use case is for setting up an alarm, where you have to re-confirm enabling the alarm after every change you make. DisableAlarm still sets isAlerting in the alarmController to false, probably because someone thought a currently alerting but also disabled alarm makes no sense, this was introduced in a0cd439. That causes the destructor of Alarm to think there is nothing to do regarding the alerting when the alarm screen is dismissed. Therefore it does not call StopAlerting and the lv_task is left with an invalid function pointer, because Alarm does not exist anymore once the lv_task finally goes to call the callback function
* | Show alarm controller state in status iconJozef Mlich2025-01-0511-9/+44
| |
* | weather: Fix inverted imperial forecast temperaturesVictor Kareh2024-12-101-3/+3
| | | | | | | | | | | | | | When converting to imperial units, the min and max temperatures were incorrectly inverted, causing confusion in the display. Fixes https://github.com/InfiniTimeOrg/InfiniTime/issues/2183
* | Use all free RAM for FreeRTOS heapFelipe Martínez2024-12-097-20/+102
| | | | | | | | | | * Use all free RAM for FreeRTOS heap * Wrap newlib malloc and related functions * Implement calloc
* | Set version to 1.15.0Jean-François Milants2024-12-031-1/+1
| |
* | spellingLionel Elie Mamane2024-11-251-1/+1
| |
* | remove unused includeLionel Elie Mamane2024-11-251-1/+0
| |
* | cmake: fix python path with use multi-version pythonxz-dev2024-11-172-0/+2
| |
* | Ignore old GoToRunning messagesmark90642024-11-171-2/+11
| |
* | Fix git hash calculation with Docker buildfebrezo2024-11-171-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix error when compiling the Pinetime using the Docker image. If done with Docker, the container does not trust the /sources folder, leading to a blank response of the command that grabs the git commit `git rev-parse --short HEAD`. ``` fatal: detected dubious ownership in repository at '/sources' To add an exception for this directory, call: git config --global --add safe.directory /sources PROJECT_GIT_COMMIT_HASH_SUCCESS? 128 BUILD CONFIGURATION ------------------- * Mode : Release * Version : 1.3.0 * Toolchain : /opt/gcc-arm-none-eabi-10.3-2021.10 * GitRef(S) : * NRF52 SDK : /opt/nRF5_SDK_15.3.0_59ac345 * Target device : PINETIME * Build DFU (using adafruit-nrfutil) : Enabled * Build resources : Enabled ``` If the `git config --global --add safe.directory /sources` is added to the Dockerfile, the problem is solved and the hash is added correctly.
* | ci: Normalise slash-containing `github.head_ref` valuesDom Rodriguez2024-11-171-5/+10
| | | | | | | | | | | | This fixes CI on #2121. Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
generated by cgit v1.2.3-70-g09d2 (git 2.51.2) at 2026-01-27 01:03:54 +0000