https://wiki.pine64.org/api.php?action=feedcontributions&feedformat=atom&user=Quantumcross 2026-04-08T10:49:06Z User contributions MediaWiki 1.37.1 https://wiki.pine64.org/index.php?title=PineTime_Hardware_Wishlist&diff=11564 2021-10-03T14:25:23Z

<p>Quantumcross: Refactor, reorganize pinetimev2 wishlist. Add piezo buzzer suggestion</p> <hr /> <div>This page contains a list of things people wish PineTime did differently<br /> <br /> === Hardware ===<br /> <br /> * Long pressing the button should power-cycle the watch without any software being involved<br /> * Other display technology could be explored.<br /> **[//en.Wikipedia.org/wiki/Transflective_liquid-crystal_display A transflective LCD]<br /> *** Increased readability in bright daylight<br /> **[//en.wikipedia.org/wiki/OLED OLED]<br /> *** Self-emissive display (pixels emit their own light)<br /> *** Allows for lower power usage with mostly black screens<br /> *** Allows for low power visual notifications (imagine an always-on small red square in the corner to indicate a notification)<br /> * Touchscreen with configurable sensitivity<br /> ** Ideal for gloved fingers and water droplet resistance<br /> ** Preferably it should remain capacitive, as a resistive touchscreen would have too many trade-offs.<br /> * A slightly bigger 256×256 pixel display<br /> ** This resolution is preferable for its binary alignment for low-level simplicity<br /> ** It has the property that its X and Y coordinates are each addressable with a single byte, with no bounds checking<br /> ** Its total number of pixels is a power of 2 (65536), and each pixel is addressable with exactly 2 bytes.<br /> ** The [http://Pelulamu.net/ibniz IBNIZ (Ideally Bare Numeric Impression giZmo) virtual machine], designed for minimalist demoscene graphics, has chosen 256×256 for its virtual display specifically for code efficiency.<br /> ** If PineTime also chose 256×256 then it would be a target platform for unclipped IBNIZ demoscene programmes, which would be really fun to play around with on one's wrist!<br /> * Full screen refresh is very slow<br /> ** A full 16-bit redraw on the display takes at worst 120ms, which is 8Hz<br /> ** Modest optimization is possible by adopting 12-bit color<br /> ** A smooth scrolling/usage/animation experience would be 30Hz minimum, preferably 60hz<br /> ** Display redraw is currently bottlenecked by the nRF52832 maximum SPI clock (8MHz).<br /> ** The nRF528(33/40) has one high speed SPI master which supports 32MHz, still well below the ST7789 maximum<br /> ** Parallel data transfer could be an option, but using more GPIOs (which don't look available)<br /> * Some sort of scroll wheel would be nice for convenience.<br /> * Changed GPIO assignment so more functionality is available (i.e. NFC and VSYNC)<br /> * Wireless charging, or Qi Charging capability<br /> * An external RTC circuit<br /> ** Allows the main MCU go to deep-sleep while retaining time.<br /> ** Allows time retention through MCU reset.<br /> * nRF5840 update<br /> ** 32MHz HS SPI, QuadSPI, CryptoCell + Secure Key Storage, more RAM, a coprocessor and the possibility to expose USB through power pins<br /> * Preferably a pre-certified MCU module with a ceramic antenna<br /> * Version without sensors but maybe bigger battery<br /> * Pins on the programmer connector to allow UART while developing (currently there is a TX test point on PCB). (Note: There's ARM SemiHosting, ITM and Segger RTT)<br /> * Connect SDO of ST7889 LCD controller to MCU.<br /> ** Allows MCU to execute READ commands<br /> ** Possibility of leveraging ST7889 RAM to save MCU RAM?<br /> * LCD must be centered on case. Currently is not and watchfaces seems different when clock is put on the other wrist.<br /> * A NFC antenna around the case, connected to the NFC pins.<br /> * Used sensors should be NDA-free and preferably also blob-free for easier development<br /> * Possibly replace BMA421 accelerometer<br /> ** The BMA421 doesn't have a public datasheet<br /> ** Special attention should be paid to advanced features, such as step counting integration or flick detection.<br /> * PineTime SoC could support USB or have a FTDI chip with the relevant pins exposed.<br /> ** It could allow flashing a sealed device, just like Arduinos work.<br /> ** The same USB-C could also be used for charging. <br /> * A bigger pulldown resistor for the power button<br /> ** 100k still leaks a noticeable amount of power when the button is always on.<br /> * Ceramic Bluetooth antenna for better signal reception<br /> * Ultra low quiescent current PMIC<br /> ** Better deep sleep/shipping/storage/off lifetime<br /> * Battery charger IC with built-in &quot;fuel gauge&quot;<br /> ** Better estimation of battery capacity<br /> * Small Piezo Buzzer<br /> ** Use case would be for very short beeps (think old-school casio watch) as notification.<br /> ** Of course developers can PWM other frequency to make it sing, but piezos tend to be shrill.<br /> <br /> <br /> [[Category:PineTime]]</div>

Quantumcross