https://forum.pine64.org/ Thu, 14 May 2026 20:58:57 +0000 MyBB https://forum.pine64.org/showthread.php?tid=19314 Thu, 27 Jun 2024 16:11:42 +0000 Dr_Turb]]> https://forum.pine64.org/showthread.php?tid=19314
Initially I was able to set it so that it woke up the display on raising my wrist; however yesterday that stopped working.  In the settings there is also an option to wake up with a single or double tap.  Neither of these works.  The watch can be woken by pressing the button, so it seems to be working OK otherwise - but does the refusal to be woken by a movement or a tap indicate that the accelerometer has failed?

Is accelerometer failure a known/likely occurence?  I've seen it mentioned once on the board.

Or could there be another issue; maybe re-starting the watch would help?  If so, can anyone suggest how to do that?

For background, this is a sealed device working with the KiActiv app on Android; so I only have access to the watch functions; KiActive should be receiving movement data for analysis offline.

TIL]]>
Initially I was able to set it so that it woke up the display on raising my wrist; however yesterday that stopped working.  In the settings there is also an option to wake up with a single or double tap.  Neither of these works.  The watch can be woken by pressing the button, so it seems to be working OK otherwise - but does the refusal to be woken by a movement or a tap indicate that the accelerometer has failed?

Is accelerometer failure a known/likely occurence?  I've seen it mentioned once on the board.

Or could there be another issue; maybe re-starting the watch would help?  If so, can anyone suggest how to do that?

For background, this is a sealed device working with the KiActiv app on Android; so I only have access to the watch functions; KiActive should be receiving movement data for analysis offline.

TIL]]> https://forum.pine64.org/showthread.php?tid=19257 Wed, 29 May 2024 10:27:00 +0000 semipol]]> https://forum.pine64.org/showthread.php?tid=19257


I have been using and loving my PineTime for almost 2 years, and it has suddenly developed a hardware issue. The touchscreen will not respond to touch, and the battery drain has gone from 16 days on a single charge to 2 days. I have rebooted the PineTime twice, flashed it from 1.13 to 1.14, allowed it to drain completely to shut it off, and nothing has helped. I'm not sure what could have caused this, I didn't drop or hit or soak it, from the battery drain it looks like it started at 5am when I was sleeping. Is there a way to repair it? All the other functions such as the step counter, bluetooth pairing, the physical button, notifications display etc all work.



Video:

https://imgur.com/Y7MA8Xq



Gadgetbridge showing it started at about 5am:

https://i.imgur.com/evRUXXr.jpeg]]>


I have been using and loving my PineTime for almost 2 years, and it has suddenly developed a hardware issue. The touchscreen will not respond to touch, and the battery drain has gone from 16 days on a single charge to 2 days. I have rebooted the PineTime twice, flashed it from 1.13 to 1.14, allowed it to drain completely to shut it off, and nothing has helped. I'm not sure what could have caused this, I didn't drop or hit or soak it, from the battery drain it looks like it started at 5am when I was sleeping. Is there a way to repair it? All the other functions such as the step counter, bluetooth pairing, the physical button, notifications display etc all work.



Video:

https://imgur.com/Y7MA8Xq



Gadgetbridge showing it started at about 5am:

https://i.imgur.com/evRUXXr.jpeg]]> https://forum.pine64.org/showthread.php?tid=18823 Sun, 29 Oct 2023 03:07:36 +0000 dallytaur]]> https://forum.pine64.org/showthread.php?tid=18823
I used this to make my own wrist strap 

if anyone is looking make custom strap I found that this working so far the best i used epoxy to get the clip attached to the nylon



  photo_2023-10-29_13-31-04.jpg (Size: 143.48 KB / Downloads: 450)


  photo_2023-10-29_13-31-11.jpg (Size: 104.76 KB / Downloads: 434) ]]>
I used this to make my own wrist strap 

if anyone is looking make custom strap I found that this working so far the best i used epoxy to get the clip attached to the nylon



  photo_2023-10-29_13-31-04.jpg (Size: 143.48 KB / Downloads: 450)


  photo_2023-10-29_13-31-11.jpg (Size: 104.76 KB / Downloads: 434) ]]> https://forum.pine64.org/showthread.php?tid=18461 Thu, 06 Jul 2023 15:31:40 +0000 mr_rockford]]> https://forum.pine64.org/showthread.php?tid=18461
What could be wrong with my watch? What can I do about it? Is it possible to send the watch back and get a replacement?]]>
What could be wrong with my watch? What can I do about it? Is it possible to send the watch back and get a replacement?]]> https://forum.pine64.org/showthread.php?tid=18372 Wed, 14 Jun 2023 21:02:26 +0000 surt]]> https://forum.pine64.org/showthread.php?tid=18372 Backlight not turning off when the display blanks and flickering when display is on and later some scanlines not drawing correctly.
Cleaning the PCB and screen connector hasn't fixed the problem and the display has started showing dimmer blotches so I figure there must be moisture on the display side.
So is it possible to non-destructively remove the LCD from the front case and if so how?]]> Backlight not turning off when the display blanks and flickering when display is on and later some scanlines not drawing correctly.
Cleaning the PCB and screen connector hasn't fixed the problem and the display has started showing dimmer blotches so I figure there must be moisture on the display side.
So is it possible to non-destructively remove the LCD from the front case and if so how?]]> https://forum.pine64.org/showthread.php?tid=18149 Tue, 18 Apr 2023 10:16:24 +0000 dynobang]]> https://forum.pine64.org/showthread.php?tid=18149
I'm a coding ignoramous who was bowled over reading about Wasp OS and some of the effectively live-coding videos on youtube.  Reminded me of my brother teaching himself to code on a Psion. I felt like the device is simple enough not to intimidate me (and for me to really grok the device and the code), so I bought one.  If I ever get around to learning to code it'll probably be for my PineTime!  My hats off to all the engineers, both hardware and 'software', including the folks at home learning-on and noodling-away-at these.  The work you publish even on forums like this is an inspiration.

Used my pinetime in the pool today.  Swipe inputs v difficult.  I wished I had a jog dial to scroll through options.  I imagine to be cheap and waterproof it would just be a magnetometer of some kind at the edge of the circuit board.  The edge of the case would have a knob which was, internally, a disc studded with tiny magnets, so that turning it would be detected by the magnetometer along with the direction of the turning.  If the screen was on (IE I was interacting with the watch), then it would listen for the turning of the knob.

Were it to be on a depressible button, behind a silicone cap, then the jog dial could also be used as a push-button.

I dream of a future where my phone tells my watch when I'm in work (GPS &/or wifi network recognition) and the applets accessible from the main screen are ones for dealing with work emergencies, as opposed to driving (car bluetooth recognition, when I might want a watch-face play/pause button or some such), or in the pool (touchscreen off, button and jogdial input only, and ready access to the metronome app for pacing and an app that sums up the duration my arms flail about in the pool to help me log it on my phone)... I'm sure others would have other suggestions!

Well, nowt like a half-baked idea to make the mind turn over.  Maybe the PCB just needs the magnetometer adjacent the strap connection, and someone makes an aftermarket dial baked into the watchstrap.  Hopefully something I could submit for consideration in case a PineTime Mk II is ever considered.

Yours with thanks,
DB

*To mods: thank you for keeping this forum going for all of us. Please do move this post if you think it would be better elsewhere.*]]>
I'm a coding ignoramous who was bowled over reading about Wasp OS and some of the effectively live-coding videos on youtube.  Reminded me of my brother teaching himself to code on a Psion. I felt like the device is simple enough not to intimidate me (and for me to really grok the device and the code), so I bought one.  If I ever get around to learning to code it'll probably be for my PineTime!  My hats off to all the engineers, both hardware and 'software', including the folks at home learning-on and noodling-away-at these.  The work you publish even on forums like this is an inspiration.

Used my pinetime in the pool today.  Swipe inputs v difficult.  I wished I had a jog dial to scroll through options.  I imagine to be cheap and waterproof it would just be a magnetometer of some kind at the edge of the circuit board.  The edge of the case would have a knob which was, internally, a disc studded with tiny magnets, so that turning it would be detected by the magnetometer along with the direction of the turning.  If the screen was on (IE I was interacting with the watch), then it would listen for the turning of the knob.

Were it to be on a depressible button, behind a silicone cap, then the jog dial could also be used as a push-button.

I dream of a future where my phone tells my watch when I'm in work (GPS &/or wifi network recognition) and the applets accessible from the main screen are ones for dealing with work emergencies, as opposed to driving (car bluetooth recognition, when I might want a watch-face play/pause button or some such), or in the pool (touchscreen off, button and jogdial input only, and ready access to the metronome app for pacing and an app that sums up the duration my arms flail about in the pool to help me log it on my phone)... I'm sure others would have other suggestions!

Well, nowt like a half-baked idea to make the mind turn over.  Maybe the PCB just needs the magnetometer adjacent the strap connection, and someone makes an aftermarket dial baked into the watchstrap.  Hopefully something I could submit for consideration in case a PineTime Mk II is ever considered.

Yours with thanks,
DB

*To mods: thank you for keeping this forum going for all of us. Please do move this post if you think it would be better elsewhere.*]]> https://forum.pine64.org/showthread.php?tid=17696 Tue, 06 Dec 2022 15:46:49 +0000 CDSIADO]]> https://forum.pine64.org/showthread.php?tid=17696 https://forum.pine64.org/showthread.php?tid=16964 Tue, 05 Jul 2022 21:28:01 +0000 ky56]]> https://forum.pine64.org/showthread.php?tid=16964 https://forum.pine64.org/showthread.php?tid=16150 Wed, 23 Feb 2022 18:36:05 +0000 nubushero]]> https://forum.pine64.org/showthread.php?tid=16150
I have searched the internet as well as these forums and can not find plans for the watch and the charging base.

Any format would work: DWG, STL, Sketchup, ...

Can anyone assist?

Thanks]]>
I have searched the internet as well as these forums and can not find plans for the watch and the charging base.

Any format would work: DWG, STL, Sketchup, ...

Can anyone assist?

Thanks]]> https://forum.pine64.org/showthread.php?tid=15725 Sun, 09 Jan 2022 20:56:40 +0000 Antoine]]> https://forum.pine64.org/showthread.php?tid=15725
It seems the accelerometer is dead on my PineTime. I have left my watch with an empty battery on my desk for 2-3 months. When I recharged it, the accelerometer gave 0 all the time and the step counter is also stuck to 0. I have noticed it with InfiniTime (v1.7.1 and v1.8.0). I have also tested with Wasp-OS with the same result. Otherwise the watch works very well.

Is there anybody who is experiencing the same failure? I believe there is not much I can do to fix it. Any help welcomed.

Antoine]]>
It seems the accelerometer is dead on my PineTime. I have left my watch with an empty battery on my desk for 2-3 months. When I recharged it, the accelerometer gave 0 all the time and the step counter is also stuck to 0. I have noticed it with InfiniTime (v1.7.1 and v1.8.0). I have also tested with Wasp-OS with the same result. Otherwise the watch works very well.

Is there anybody who is experiencing the same failure? I believe there is not much I can do to fix it. Any help welcomed.

Antoine]]> https://forum.pine64.org/showthread.php?tid=15483 Tue, 07 Dec 2021 18:29:52 +0000 ventyl]]> https://forum.pine64.org/showthread.php?tid=15483
Edit: model is up now

https://www.thingiverse.com/thing:5157985

  2021-12-07_18-57-58_1.jpg (Size: 327 KB / Downloads: 520)

  2021-12-07_18-57-49_1.jpg (Size: 298.04 KB / Downloads: 484) ]]>
Edit: model is up now

https://www.thingiverse.com/thing:5157985

  2021-12-07_18-57-58_1.jpg (Size: 327 KB / Downloads: 520)

  2021-12-07_18-57-49_1.jpg (Size: 298.04 KB / Downloads: 484) ]]> https://forum.pine64.org/showthread.php?tid=15299 Wed, 10 Nov 2021 04:08:05 +0000 matrix224]]> https://forum.pine64.org/showthread.php?tid=15299
I had recently purchased the dev kit package for the PineTime watch (one unsealed, one sealed) and have been having a lot of fun playing around with it. It's a new area for me and I've definitely learned a good deal from it!

With that being said, I want to stress that I'm by no means an expert with things like Bluetooth. I understand how it works and how to interact with it via code, but I couldn't tell you all the truly intricate details of it.

For reference, any tests or scenarios I mention below are using InfiniTime 1.6 with a custom app I had put on it to act as a simple remote control. I based the structure of the app off of the Music app's play/pause button implementation since that was essentially what I needed, just for a different use case that connects to my PC. It has been working perfectly fine and doing exactly what I expected in terms of functionality.

However, the one issue I've had is in regards to the Bluetooth cutting out more than I would've expected it to. There are times where I'm in direct line-of-sight of the adapter for my PC, standing approximately 12 - 15 or so feet from it, and it would start to get more latency and then typically disconnect. It would then reconnect intermittently until I got closer to the adapter, at which point it would be fine again. This would also happen if I was right below the adapter in my kitchen (maybe 7 or so feet, with only a few 2x4s separating the top of the kitchen from the floor above).

So, I tried the following to diagnose it:

• Connected to my phone instead of the PC adapter. Had the same results
  
• Tried a different PC adapter. Same results
  
• Tried using both the sealed and unsealed watches in the same situations described above. Had the same results for both in all cases
  

At this point I wasn't too sure what to think. I know that the connectivity varies on every device and some devices just have shorter ranges, so maybe that was just a limitation. Then, for some reason (I don't really even remember why I thought this), I figured "I've been wearing the watch in all these tests. What if I just hold it by the strap?"

I walked over to one of the places that I had these issues at and held the watch by the strap, and noted that there was barely - if any - latency. I moved my hand around holding the watch (lifting it up, moving it down, further away, closer, etc); still no issues. I figured this may just be a lucky fluke, so I tried other places I had issues at and to my surprise, still had no problems.

To see if I had finally lost my mind, I took the other watch and tried the same tests. I had the same results when holding it from the strap: no notable issues.Then, I took the watch, and laid it over my arm (didn't strap it on, just laid it down), and suddenly the connection died off.

I repeated the above experiment several times, with both watches, and every time I had the same results. Whenever I put the watch on my wrist, the connectivity would be cut off to a pretty extreme amount. I know that Bluetooth can't travel through water, and given that we're just walking, talking water sacs, it does add up that my body blocking the watch would reduce signal.

As another experiment, I bent the end of the Bluetooth antenna in my dev watch upwards a bit so that it was more vertical inside the case. My main reasoning was (rather simply) that antennas typically seem to point vertically from their base, so I have nothing to lose by trying that here. To my surprise, this actually seemed to reduce the issues I had while wearing the watch by a significant amount; not a complete fix, but certainly much better. Conversely, the sealed watch still had issues where the dev watch no longer did.

So with all that out of the way, my main questions:

• Is wearing the watch supposed to affect connectivity? Like I said above, I understand that our bodies block signal, but it seems kind of bizarre that wearing the watch - one of the main functions of it - would decrease connectivity by such a noticeable amount, no?
  
• Does it really make sense that my slight bending of the antenna would've increased performance to such a noticeable degree?
  
• Is there just something else here that I'm overlooking, or other factors that are just making this a red herring?
  

I also apologize if this is the wrong sub-forum. I figured since after all my tests it seemed hardware related, I would ask here.]]>
I had recently purchased the dev kit package for the PineTime watch (one unsealed, one sealed) and have been having a lot of fun playing around with it. It's a new area for me and I've definitely learned a good deal from it!

With that being said, I want to stress that I'm by no means an expert with things like Bluetooth. I understand how it works and how to interact with it via code, but I couldn't tell you all the truly intricate details of it.

For reference, any tests or scenarios I mention below are using InfiniTime 1.6 with a custom app I had put on it to act as a simple remote control. I based the structure of the app off of the Music app's play/pause button implementation since that was essentially what I needed, just for a different use case that connects to my PC. It has been working perfectly fine and doing exactly what I expected in terms of functionality.

However, the one issue I've had is in regards to the Bluetooth cutting out more than I would've expected it to. There are times where I'm in direct line-of-sight of the adapter for my PC, standing approximately 12 - 15 or so feet from it, and it would start to get more latency and then typically disconnect. It would then reconnect intermittently until I got closer to the adapter, at which point it would be fine again. This would also happen if I was right below the adapter in my kitchen (maybe 7 or so feet, with only a few 2x4s separating the top of the kitchen from the floor above).

So, I tried the following to diagnose it:

• Connected to my phone instead of the PC adapter. Had the same results
  
• Tried a different PC adapter. Same results
  
• Tried using both the sealed and unsealed watches in the same situations described above. Had the same results for both in all cases
  

At this point I wasn't too sure what to think. I know that the connectivity varies on every device and some devices just have shorter ranges, so maybe that was just a limitation. Then, for some reason (I don't really even remember why I thought this), I figured "I've been wearing the watch in all these tests. What if I just hold it by the strap?"

I walked over to one of the places that I had these issues at and held the watch by the strap, and noted that there was barely - if any - latency. I moved my hand around holding the watch (lifting it up, moving it down, further away, closer, etc); still no issues. I figured this may just be a lucky fluke, so I tried other places I had issues at and to my surprise, still had no problems.

To see if I had finally lost my mind, I took the other watch and tried the same tests. I had the same results when holding it from the strap: no notable issues.Then, I took the watch, and laid it over my arm (didn't strap it on, just laid it down), and suddenly the connection died off.

I repeated the above experiment several times, with both watches, and every time I had the same results. Whenever I put the watch on my wrist, the connectivity would be cut off to a pretty extreme amount. I know that Bluetooth can't travel through water, and given that we're just walking, talking water sacs, it does add up that my body blocking the watch would reduce signal.

As another experiment, I bent the end of the Bluetooth antenna in my dev watch upwards a bit so that it was more vertical inside the case. My main reasoning was (rather simply) that antennas typically seem to point vertically from their base, so I have nothing to lose by trying that here. To my surprise, this actually seemed to reduce the issues I had while wearing the watch by a significant amount; not a complete fix, but certainly much better. Conversely, the sealed watch still had issues where the dev watch no longer did.

So with all that out of the way, my main questions:

• Is wearing the watch supposed to affect connectivity? Like I said above, I understand that our bodies block signal, but it seems kind of bizarre that wearing the watch - one of the main functions of it - would decrease connectivity by such a noticeable amount, no?
  
• Does it really make sense that my slight bending of the antenna would've increased performance to such a noticeable degree?
  
• Is there just something else here that I'm overlooking, or other factors that are just making this a red herring?
  

I also apologize if this is the wrong sub-forum. I figured since after all my tests it seemed hardware related, I would ask here.]]> https://forum.pine64.org/showthread.php?tid=15256 Thu, 04 Nov 2021 03:19:23 +0000 kj6epl]]> https://forum.pine64.org/showthread.php?tid=15256 https://forum.pine64.org/showthread.php?tid=15195 Wed, 27 Oct 2021 06:31:39 +0000 jandy]]> https://forum.pine64.org/showthread.php?tid=15195 discusse improvements of hardware such as:

1) gps
2) nfc
3) nrf52840? (more flash and ram)
4) mag
5) gyro
6) PMIC for power consume
7) RTC battry]]> discusse improvements of hardware such as:

1) gps
2) nfc
3) nrf52840? (more flash and ram)
4) mag
5) gyro
6) PMIC for power consume
7) RTC battry]]> https://forum.pine64.org/showthread.php?tid=15094 Thu, 14 Oct 2021 09:36:54 +0000 kwinz]]> https://forum.pine64.org/showthread.php?tid=15094 wiki I only see mentioned that it uses the ST7789 display controller.

And that it's an 240×240 pixels IPS capacitive touchscreen, RGB 65K colors.

And there is a CAD model https://files.pine64.org/doc/datasheet/p...0Panel.jpg

But which exact LCD model is it? I am not asking about the controller, I am asking about the LCD itself.

Thanks in advance!]]> wiki I only see mentioned that it uses the ST7789 display controller.

And that it's an 240×240 pixels IPS capacitive touchscreen, RGB 65K colors.

And there is a CAD model https://files.pine64.org/doc/datasheet/p...0Panel.jpg

But which exact LCD model is it? I am not asking about the controller, I am asking about the LCD itself.

Thanks in advance!]]>