Only allow merging if formatting pass.

Use --dry-run --formatted in astyle

Prerequisites

Since the ZSWatch hardware and firmware doesn't have anything in common (expect of fact that all of this related to one final product) I purpose to split it to different repositories. By growing project size and difficulties to maintain hw and fw in one repository we'll definitely end up with splitting them. I suggest doing it in early state of project before it's got too painful. By splitting the repository following advantages:

1. Possibility to setup independent pipelines
2. Follow some branching model for firmware
3. Track and handle releases/changelog clearly for firmware and hardware
4. Configure ZSWatch firmware repo as a manifest file in proper way, which provide possibility to:
   -- clone project and all dependencies via single command line,
   -- checkout certain version of Zephyr and modules
   -- automatically apply patches to Zephyr
   -- extend west command
   -- ect.
5. Define issues independently -> avoid mess of TODO
6. Open root directory in VSCode which provide:
   -- possibility to operate with Git extension for VSCode
   -- nRF Connect extension automatically loads application
   -- set up workspace and firmware specific settings

Side effects

1. Some manual merging required for all forks
2. Content of current repo will be changes, people will not see that they expect by clicking old link

Proposal

1. Create two new repositories named "ZSWatchFw" and "ZSWatcHw" and copy related part to there.
2. Keep current repo as a ZSWatch overview, keep demos, documentation, images.
3. Configure ZSWatch manifest repo which will include all 3 repositories and have a following tree:
   ZSWatch # zephyr top dir
   ├─ ZSWatch
   ├─ ZSWatchHw
   ├─ ZSWatchFw
   │ └─ west.yml # Main manifest
   ├─ zephyr
   ├─ modules
   ├─ bootloader
   ...

I don't like the idea of having hw sources in zephyr manifest, but it might be useful for someone.

Remove the callback used here https://github.com/jakkra/ZSWatch/blob/main/app/src/ble_comm.c#L535C5-L535C19 and use ZBUS event instead also for notifications.

In order to know when all subscribers and listeners are done with the event, see this approach here: See example how to do it here: https://github.com/zephyrproject-rtos/zephyr/pull/59071/files

I found these errors in the display driver init sequence.
/app/drivers/display/gc9a01.c

• (line 119-121)

    GC9A01A1_VREG1A, 0x13,
    GC9A01A1_VREG1B, 0x13,
    GC9A01A1_VREG2A, 0x22,

should be

    GC9A01A1_VREG1A,1, 0x13,
    GC9A01A1_VREG1B,1, 0x13,
    GC9A01A1_VREG2A,1, 0x22,

It is missing the numArgs.

• line 112
  0xB6, 2, 0x00, 0x00, should be 0xB6, 2, 0x00, 0x20,
• line 143
  GC9A01A_TEON, 1, GC9A01A_INVOFF, should be GC9A01A_TEON, 0,.

In my implementation I have removed some redundant register inits and moved some register inits to a function call,(some registers can be initialized earlier on , like orientation and pixel format). It also has pwm based backlight control implemented.

I hope this solves the problem that you face.
Cheers,
Amrith

First of all, your work currently looks good, but it seems that the first version of the watch shell can no longer meet the second version, and I am very interested in its shell style

t:"nav",instr:"High St towards Null St",distance:966,action:"continue",eta:"08:39"
t:"nav" - Navigation stopped

Example:
GB({"t":"notify","id":1,"src":"Maps","title":"0 yd - High St","body":"Campton - 11:48 ETA","img":"Y2MBAA....AAAAAAAAAAAAAA="})

Easiest is to do an app for it.

For example UI popup or a small vibration.

Info already published on ZBUS_CHAN_DECLARE(chg_state_data_chan);

When opening a watchface, such as the digital one, it would look nice if we added some type of animation of some objects in the watchface.

Hello, I am very interested in this program, but I'm new for zephyr. Now I already install the dev env at of zephyr in ubuntu22.04 according to https://docs.zephyrproject.org/latest/develop/getting_started/index.html. But I can't find the way to build the project, could you add some short description for How to build the app in README?
Thanks again for you awesome project.

Hello, I am very interested in your project. I am planning to build something similar but with AMOLED display and with internal small coin battery for RTC time. I am just curious why would you use battery supervisor chip? From your photos I can see that the battery has already integrated supervisor, so why you adding additional?

Right now k_msleep is used to delay in vibrations, this is super bad.
Vibrations needs to be able to run "in background".
Use timers instead to do vibrations.
Add a way to choose what vibration pattern to play.

Code: https://github.com/jakkra/ZSWatch/blob/main/app/src/vibration_motor.c

With 16MB external flash soon coming to the next hardware version we can now store alot of resources in this memory.

This open many new doors.

We need a way to easily put resources such as icons, fonts etc. in this flash and also point LVGL to read those resources from there.

LVGL already have support for this, but needs to be configured and enabled.

How to easily upload resources to external flash?

Hi Jakob Krantz,
just to let you know i added a link this this project of yours to my own open hardware catalogue. Heres' the link:

https://github.com/aeonSolutions/PCB-Prototyping-Catalogue/tree/main/wearables

keep up the good and great work !
regards,
Miguel T.

From the picture, it can be seen that you have already made the watch case, haven't you? How beautiful! Can you share the CAD files and take a look? I am very curious about how the button part is resolved. Thank you.

In addition user could input heigh, weight, etc. to get calories estimator
https://www.geeksforgeeks.org/steps-to-calories-calculator/
https://fitness.stackexchange.com/questions/25472/how-to-calculate-calorie-from-pedometer
...

I am trying to build native posix project. I get the following error. Am I doing something wrong or the build script is corrupted?

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: /home/mohammad/zephyrproject/projects/ZSWatch/app
-- CMake version: 3.27.4
-- Cache files will be written to: /home/mohammad/.cache/zephyr
-- Zephyr version: 3.4.99 (/home/mohammad/zephyrproject/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: native_posix
-- Found host-tools: zephyr 0.16.1 (/home/mohammad/zephyr-sdk-0.16.1)
-- Found toolchain: host (gcc/ld)
-- Found BOARD.dts: /home/mohammad/zephyrproject/zephyr/boards/posix/native_posix/native_posix.dts
-- Found devicetree overlay: /home/mohammad/zephyrproject/projects/ZSWatch/app/boards/native_posix.overlay
-- Generated zephyr.dts: /home/mohammad/zephyrproject/projects/ZSWatch/app/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/mohammad/zephyrproject/projects/ZSWatch/app/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /home/mohammad/zephyrproject/projects/ZSWatch/app/build/zephyr/dts.cmake

warning: SENSOR (defined at drivers/sensor/Kconfig:6) was assigned the value 'n' but got the value
'y'. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_SENSOR and/or look up SENSOR in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: MAX30101_SLOT1 (defined at drivers/sensor/max30101/Kconfig:143) was assigned the value '1'
but got the value ''. Check these unsatisfied dependencies: MAX30101_MULTI_LED_MODE (=n), MAX30101
(=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MAX30101_SLOT1 and/or look up
MAX30101_SLOT1 in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: MAX30101_SLOT2 (defined at drivers/sensor/max30101/Kconfig:158) was assigned the value '2'
but got the value ''. Check these unsatisfied dependencies: MAX30101_MULTI_LED_MODE (=n), MAX30101
(=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MAX30101_SLOT2 and/or look up
MAX30101_SLOT2 in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: MAX30101_SLOT3 (defined at drivers/sensor/max30101/Kconfig:173) was assigned the value '3'
but got the value ''. Check these unsatisfied dependencies: MAX30101_MULTI_LED_MODE (=n), MAX30101
(=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MAX30101_SLOT3 and/or look up
MAX30101_SLOT3 in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: MAX30101_SLOT4 (defined at drivers/sensor/max30101/Kconfig:188) was assigned the value '0'
but got the value ''. Check these unsatisfied dependencies: MAX30101_MULTI_LED_MODE (=n), MAX30101
(=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MAX30101_SLOT4 and/or look up
MAX30101_SLOT4 in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: PM (defined at subsys/pm/Kconfig:13) was assigned the value 'y' but got the value 'n'.
Check these unsatisfied dependencies: HAS_PM (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_PM and/or look up PM in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: The choice symbol MAX30101_MULTI_LED_MODE (defined at drivers/sensor/max30101/Kconfig:62)
was selected (set =y), but no symbol ended up as the choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MAX30101_MULTI_LED_MODE and/or look up
MAX30101_MULTI_LED_MODE in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: The choice symbol NEWLIB_LIBC (defined at lib/libc/Kconfig:85) was selected (set =y), but
EXTERNAL_LIBC (defined at lib/libc/Kconfig:101) ended up as the choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NEWLIB_LIBC and/or look up NEWLIB_LIBC in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


/home/mohammad/zephyrproject/projects/ZSWatch/app/prj.conf:36: warning: attempt to assign the value 'n' to the undefined symbol KSCAN_CST816S

/home/mohammad/zephyrproject/projects/ZSWatch/app/prj.conf:183: warning: attempt to assign the value '5' to the undefined symbol ZBUS_RUNTIME_OBSERVERS_POOL_SIZE

error: Aborting due to Kconfig warnings
Parsing /home/mohammad/zephyrproject/projects/ZSWatch/app/Kconfig
Loaded configuration '/home/mohammad/zephyrproject/zephyr/boards/posix/native_posix/native_posix_defconfig'
Merged configuration '/home/mohammad/zephyrproject/projects/ZSWatch/app/prj.conf'
Merged configuration '/home/mohammad/zephyrproject/projects/ZSWatch/app/boards/native_posix.conf'

CMake Error at /home/mohammad/zephyrproject/zephyr/cmake/modules/kconfig.cmake:348 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/mohammad/zephyrproject/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
  /home/mohammad/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /home/mohammad/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:15 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /usr/bin/cmake -DWEST_PYTHON=/usr/bin/python3 -B/home/mohammad/zephyrproject/projects/ZSWatch/app/build -GNinja -S/home/mohammad/zephyrproject/projects/ZSWatch/app

References:
https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/application_development/sysbuild/with_mcuboot
https://docs.zephyrproject.org/latest/build/sysbuild/index.html

Right now we cannot store an settings or anything that persists power loss.
This is quite bad, and we really need persistent storage.

Start with bringing it up, then next step is to organize a good way for apps to store/load settings etc.

Needed for rev 3 ZSWatch
zsw_light_sensor.c contains just code for reading chip ID right now.
Write a proper driver for it.

This is a binary blob and shall be optional to use (opt-in)

This blob needs to be downloaded from here by each person compiling (I think): https://www.bosch-sensortec.com/software-tools/software/bsec/

But this blob allows for the advanced features of the BMP588, such as air quality etc.

• Integrate this library and add functions to get this data
• Document how to set this up (download, where to put the lib etc.)

Idea

• Use the input subsystem to handle all events (touch and buttons)
• Create a driver for LVGL that contains the input subsystem handling. So we are able to control the inputs that are passed to LVGL
• Apply different key IDs to all buttons

References

https://docs.zephyrproject.org/latest/services/input/index.html#c.INPUT_CALLBACK_DEFINE
https://docs.zephyrproject.org/latest/build/dts/api/bindings/input/zephyr,input-longpress.html

ToDo

• #149
• #118
• Support more applications
  • Discord
  • YouTube
  • LinkedIn
  • Home Assistant
  • Finanzguru
  • Google Calendar
  • Steam
• Additional font for special characters
• Notification app freezes at some number of notifications (more than 14). Figure out why and add a workaround like visualizing only 10 notifications, etc.

Related to application_picker

It is a Great Project :)
I'd like to try, but I have question about the battery supervior.

When the battery goes down to 3.6V -> NCV(supervisor) RESET_OUTPUT to low ->
Disable LDO(CE), Turn off MCU.

For charing battery,
VBUS connected -> charge battery -> if +BATT>3.6 turn LDO on by NCV

what if LCD BL and MCU drain more than charged capacity(might be low current VBUS),
is there no glitch, like turn on and off in a loop?

I have been researching the structure of your first version recently, but I cannot understand your structure in the button section. How do you specifically implement the button function? I also noticed that you have a plastic part in the physical part of the button. Is this what you bought? Can you send me a purchase link to take a look? Thank you very much!

Code here: https://github.com/jakkra/ZSWatch/blob/main/app/src/ui/watchfaces/zsw_watchface_analog_ui.c

Currently compass app does not work unless watch is put flat.
This can be solved by using an algorithm that compensates for the tilt of the watch.

Today it's done here: https://github.com/jakkra/ZSWatch/blob/main/app/src/ram_retention_storage.c

Should be using the Zephyr subsystem instead: https://docs.zephyrproject.org/latest/services/retention/index.html

Event:
t:"call", cmd:"accept/incoming/outgoing/reject/start/end", name: "name", number: "+491234"

Example:
// Call coming in
GB({"t":"call","cmd":"incoming","name":"name","number":"+441234123123"})

To start with this could be a simple modification of the notification popup

Requires ability to measure current consumotion, using for example Nordic PPK2.

Issue probably in this file: https://github.com/jakkra/ZSWatch/blob/main/app/src/zsw_cpu_freq.c

There are some patches, for example to upscale native_posix SDL display.
Would be handy to automatically apply those patches when complinging.

Clicking on the battery arc could open the battery app for example, etc...

The touch chip IC cst816s have features to go into low power mode and then allow wakeup by doing gestures or taps on the screen. This would be a nice additional way to wake up the watch.

Implement this. What registers and how to configure this needs some digging as much documentation for the cst816s is in chinese.