13 ms·

Google open-sources the Pebble OS

1263 points by hexxeh 2y ago

https://github.com/google/pebble https://github.com/google/pebble

atYevP 2y ago
Lets go!
zitterbewegung 2y ago
This is pretty awesome. I had a Pebble but the battery went out and was sad to see that you had to buy used / refurbished. Being epaper and lasting for so long the best part of it was that it just managed notifications with my phone. I moved on to the Apple Watch from my brother (series 0) and it took awhile for the Apple Watch to have its killer application which was a fitness tracker.
- jsheard 2y ago
  You can still get watches which use the same MIP display technology as the Pebble and run similar "smart-ish" software with very long battery life. They tend to be marketed more as fitness/sports watches rather than smartwatches though.
  - LeifCarrotson 2y ago
    MIP and e-paper are not exactly the same. I love my transflective MIP Garmin Fenix watch, but it's not nearly as high-contrast as my wife's Kindle, which uses a reflective MIP e-paper display. I would be an ideal candidate for a rePebble if I were not as happy as I am with my Garmin - though with their recent changes to inReach plans, crazy prices and lackluster features on the Fenix 8, and trend towards AMOLED displays (away from their roots, chasing the Apple watch market) they're not looking as amazing as they once did.
    - jsheard 2y ago
      I think you're mixing up e-paper (generic term for non-emissive reflective displays) and e-ink (the trademark for a specific type of e-paper display). The Pebble used a MIP LCD, just like Coros and Garmins MIP models, it never had anything in common with the e-ink displays used on Kindles.
- ClassyJacket 2y ago
  Every Pebble model used an LCD display. It being epaper has to be one of the most pervasive myths in tech history. It was a low powered, reflective LCD, so it did improve on other LCDs in those areas somewhat, but it wasn't eink technology.
maxehmookau 2y ago
This is cool! I remember receiving my first Pebble watch on kickstarter. I felt like I was in the future!
- PokemonNoGo 2y ago
  you still will be! In a few!
guzik 2y ago
Pebble is still the best and the only watch I've ever owned. Nothing has matched its simplicity and functionality for me.
spencerflem 2y ago
Don't say it often, but this is very nice of Google and they really didn't have to. Credit where it's due
- GuB-42 2y ago
  Yep, that's the kind of thing I would have expected "don't be evil" Google from 20 years ago to do. All is not lost.
- skort 2y ago
  [flagged]
  - RobotToaster 2y ago
    It feels like they deliberately sat on it until it's almost completely dead.
    - freedomben 2y ago
      Fortunately you don't need to go on your feelings, because people involved have told us exactly what happened. RePebble guy (Eric) reached out, asked them to open source, they spent a ton of effort to get it releasable, and did just that. Unless you think everybody involved is lying.
  - elaus 2y ago
    I prefer to shit on companies that don't even do "the bare minimum" and never publish source code of their dead products. Today, this is not Google.
    - deleted 2y ago
      [deleted]
    - scarface_74 2y ago
      I’m the first to criticize Google and say they have the attention span of a crack addled flea. But I have to commend them for this.
jsheard 2y ago
They've open sourced what they can, but these third party bits had to be stripped out: - All of the system fonts - The Bluetooth stack, except for a stub that will function in an emulator - The STM peripheral library - The voice codec - ARM CMSIS - For the Pebble 2 HR, the heart rate monitor driver
- v9v 2y ago
  I remember reading that the Bluetooth stack was one of the main differentiators for Pebble at the time due to its reliability, shame it's not included here.
  - aryonoco 2y ago
    In 2014, that certainly was true. Every open source Bluetooth stack (i.e., Android, Linux and FreeBSD) was buggy and unreliable. Since then they rewrote the Bluetooth stack in Android twice, and finally what's in AOSP is quite comprehensive and reliable. It's now been merged into ChromeOS as well. I feel like it's the same about many of the items mentioned above, the free/libre offering in that space are a lot more polished than was the case 9-10 years ago. Back then the audio codec was still a patent encumbered minefield, now you can just use opus. The quality and diversity of free fonts is ordered of magnitudes above what it was 10 years ago. In short, it should be much easier for Eric to fill those gaps with free/open offerings than it was 10 years ago.
- CuriousCosmic 2y ago
  > - ARM CMSIS It's worth noting that CMSIS itself is open source but some of the drivers for this hardware probably were not.
  - bri3d 2y ago
    Old versions of CMSIS had a weird "only for use with ARM hardware" license header, which also carried through into most BSPs. I don't think this was resolved until around CMSIS 4, so it might just be a matter of front porting since it looks like normal STM32 stuff which is mostly permissively licensed now.
rvz 2y ago
Give credit where credit is due, at least Google gives back to the community. Well done.
- Alive-in-2025 2y ago
  Well, better would have been investing in it and making it better. At least they didn't produce some awful spy on you thing that had nothing to do with p and called it pebble
  - TulliusCicero 2y ago
    Pebble was dead long before Google got to own this IP.
    - Alive-in-2025 2y ago
      Do you think they have a future? I love the idea of a watch I can write simple little apps on. I looked at garmin, it was more challenging. the apple watch just has such a short battery life, I can't stand to charge it so much
ryukafalz 2y ago
As a Pebble user to this day (I'm wearing one right now in fact) this is amazing! I'm hopeful that this leads to development and fixes on these old devices that haven't been possible until now. And who knows, maybe we could even see new smartwatches running a derivative of the Pebble OS at some point? The old hardware's great but since they're not being made anymore it's only a matter of time before they break down. Props to Google on this.
fsflover 2y ago
Dupe: https://news.ycombinator.com/item?id=42845017 https://news.ycombinator.com/item?id=42845017
erohead 2y ago
Thank you, Google. You didn't have to, but you did. We are all are extraordinarily grateful. I wrote a blog post about our plans to bring Pebble back, sustainably. https://ericmigi.com/blog/why-were-bringing-pebble-back https://ericmigi.com/blog/why-were-bringing-pebble-back We got our original start on HN (https://news.ycombinator.com/item?id=3827868 https://news.ycombinator.com/item?id=3827868), it's a pleasure to be back. If you're interested in getting a new Pebble, check out https://rePebble.com https://rePebble.com
- xvector 2y ago
  I love what you're doing but the design of the pebble turns me off. Thoughts on making a sleek design that actually looks like a pebble?
- Latty 2y ago
  I did wear my Pebble until it died, and then never found another smart watch worth it for me. Will keep an eye on this for sure.
  - ashirviskas 2y ago
    May I ask why it was so special for you? As I did not participate in all the hype and now I'm a happy owner of a Garmin watch and it does seem like it is closer in specs to Pebble than most other smartwatches. Other than the openness.
    - whs 2y ago
      I wear a Garmin and I still miss my Pebble Time that died to swelling battery. - Always on. Garmin has option to do that as well but it reduce the battery life to like 3 days. In outdoor my Pebble Time is very bright with zero backlight. - 5 days battery. I went on a trip to Japan without its proprietary charger, by the time I board my flight back it was on power save mode and it died the moment the plane landed. Garmin could do this if you set it to power saving mode, but the Pebble is in standard mode. One could argue that the Garmin do have more stuff like health monitoring that Pebble didn't. - Cheap and no frills. I want a second screen for my phone, not a health tracker. Originally my Pebble Time shipped with zero fitness features, and it later added a step counter once it's clear that the market direction go that way. - Garmin is quite thick, Pebble Time is thinner - The UI is simple - press up for past event, down for future event (calendar). Press the middle button for menu. Hold are configurable. Garmin has 4 main menus which are very confusing (fitness menu, shortcut menu, apps menu, system menu). - Lots of free apps and watch faces which I actually used (like a music app that show album art). I don't see any apps I would want to use on the Garmin, and they're mostly paid. The "hide in a hole while ceiling crush the map" game on Pebble was really well done. Now my Garmin use the simple time in Verdana watch face because I cba to find a decent one. - Even with low framerates, Pebble managed to deliver cute little animations. Replying to message show a flying paper plane, screen transitions have suitable animations (not generic ones like Android), and the best one is muting an apps show a Ostrich putting its head under the ground. The animation also hides how slow the hardware actually is, with later OS versions stalling over a second or two after a second long animation. - I think the phone app UI is not as good as say, Apple Watch, but it focus on apps and the store without the fitness features. Garmin's app is entirely about fitness and they hide smartwatch stuff in a menu plus another separate Connect IQ app. Overall the PebbleOS feel like a really solid and polished product than any smartwatch today. It do fewer things than most smartwatches, but that's all I care about and everything it does is very polished.
skort 2y ago
Hopefully this will accelerate the production of new hardware at some point. I misplaced my old Pebble Time and was excited for the Pebble Time 2 but those hopes were dashed when they closed up and fitbit had no interest in continuing to produce the watches that made Pebble what it was.
- scarface_74 2y ago
  Hardware is hard to almost impossible as a sustainable business as a small company unless there is a thriving ODM market and you can just use your own software.
whalesalad 2y ago
Are there any applications that are also open sourced? They mention snowy but it is giving a 404: https://github.com/pebble-dev/snowy https://github.com/pebble-dev/snowy
- zorgmonkey 2y ago
  I see a bunch of demo\test apps here https://github.com/google/pebble/tree/main/src/apps https://github.com/google/pebble/tree/main/src/apps
- will0 2y ago
  Try that URL again :)
  - follower 2y ago
    TL;DR: Tintin in the Land of the Public Domain. I had forgotten Pebble used Tintin-themed code names (which I assume was the inspiration for the Snowy assistant app's name?)... Tangentially & coincidentally related: the Tintin & Snowy[0] characters entered the/a Public Domain[1] at the beginning of this year! Which means your lawyer might advise that you might now actually be able to use an actual original Snowy illustration[2] for the app logo... I mention this primarily because I am currently (in theory) developing a Tintin-themed game for an annual Public Domain game jam[3]. In reality, I've spent more time trying to locate scans of Tintin-related documents/illustrations[4] that actually fall under the constraints necessary for even US Public Domain[5]. ---- [0] Milou. [1] Well, actually[1a], maybe only in the US for 2025? And 2034 in Berne-associated countries? And 2054 in Belgium? Or any year if you're an AI, seemingly? Okay, perhaps it's better to not use an original illustration. Such are the joys of actually trying to interact with the Public Domain in good faith[1b]. [1a] https://en.wikipedia.org/wiki/Tintin_in_the_Land_of_the_Soviets#Public_domain_status https://en.wikipedia.org/wiki/Tintin_in_the_Land_of_the_Sovi... [1b] It just now occurs to me to wonder whether or not Milou can actually be referred to as "Snowy" given Tintin wasn't translated into English until the 1950s (late 1950s for the use of the name "Snowy" rather "Milou") (and as late as 1989 for the first title "Tintin in the Land of the Soviets"), given translations are AIUI new works? [2] First appearance: https://en.wikipedia.org/wiki/File:Tintin_and_Snowy_from_Tintin_in_the_Land_of_the_Soviets_(1929).jpg https://en.wikipedia.org/wiki/File:Tintin_and_Snowy_from_Tin... [3] https://itch.io/jam/gaming-like-its-1929 https://itch.io/jam/gaming-like-its-1929 [4] Pretty interesting finding different variants on archive.org, e.g. [4a][4b][4c]. (After all, "entering the Public Domain" is not of much value if the related material isn't accessible or the status is unclear. (Which is why recent trends in FLOSS project copyright year ranges statements bug me...)) [4a] Original French language album: https://archive.org/details/tintinnb/Francais/Tome%2001%20-%20Tintin%20au%20pays%20des%20Soviets/page/n3/mode/2up https://archive.org/details/tintinnb/Francais/Tome%2001%20-%... [4b] Second French language newspaper serialization: https://archive.org/details/cv-1930-50-pb/page/n3/mode/2up https://archive.org/details/cv-1930-50-pb/page/n3/mode/2up [4c] Original physical illustration: https://archive.org/details/tome-01-herge-chronologie-dune-oeuvre-1907-1931_202211/page/224/mode/1up https://archive.org/details/tome-01-herge-chronologie-dune-o... [5] Okay, yeah, this kinda turned into a Public Domain rant, sorry? :) (To bring it back to the topic at hand: "Hey, can't wait until this Pebble OS code enters the Public Domain in the year `2024 + YYY`." :) )
tucnak 2y ago
To somebody who's completely out of the loop, hears about Pebble for the first time—why is this big news? Are we going to see novel software written for defunct hardware, or is the hardware going to evolve now that the software is open?
- Philpax 2y ago
  People really like their Pebble watches, and this will help keep them alive into the future. In some future, we may see new hardware produced that could use some derivative of the resulting operating system.
  - tucnak 2y ago
    I'm more of a mechanical-movement person myself, but I'm also fond of these little e-ink things; and indeed, they have come a long way. Maybe somebody makes a true e-ink pebble and designs it well, too.
- jabroni_salad 2y ago
  It's one of the original smart watches. What really sets it apart from modern ones is the e-ink display and dead simple interface (just a few buttons, no touchscreen). This simplicity means that it continues to do what it does well and doesn't really feel like it has aged badly. Certainly I would rather wear a pebble than a gen 1 Samsung watch or moto360. It's a delightful bit of kit that was sadly abandoned by owner and it's nice that they are open-sourcing a dead product instead of just leaving it to rot like so many other electronics are.
  - Gigachad 2y ago
    The pebble did not have an e ink display, It was just a low power LCD.
    - Zamiel_Snawley 2y ago
      There were many models of Pebble. The original definitely had epaper[0]. [0] https://www.kickstarter.com/projects/getpebble/pebble-e-paper-watch-for-iphone-and-android https://www.kickstarter.com/projects/getpebble/pebble-e-pape...
insane_dreamer 2y ago
Still have my Pebble watch from 10 years ago in a drawer somewhere. Great watch, good times. I'm back to a "classic" analog watch as I realized I don't really want notifications. But I might buy a smart watch (probably Apple watch at this point since I have a bunch of iOS hardware) for the health features (HR, EKG, etc.)
bix6 2y ago
Can anyone comment on Google’s Business reasons for doing this? Is this actually an act of goodwill or is this a commodity, antitrust, etc. play?
- deleted 2y ago
  [deleted]
- coldpie 2y ago
  Given the original Pebble folks are using this to spin up a re-launch ( https://news.ycombinator.com/item?id=42845185 https://news.ycombinator.com/item?id=42845185 ), my guess is the Pebble folks just know someone on the inside at Google who managed to get the lawyers to sign off on it.
  - bombcar 2y ago
    From my experience in large (and small) companies, trying to get something that is internally dead open sourced is usually not a huge fight against people saying no, just a laundry-list of things that need to be done before everyone will sign off on it. One motivated person at a decently high enough level can get it pushed through, as long as whoever the person making the decision asks about it says, 'eh, ok.'
    - 1337shadow 2y ago
      > Instead, we took a more direct route - I asked friends at Google (which bought Fitbit, which had bought Pebble’s IP) if they could open source PebbleOS. They said yes! Over the last year, a team inside Google (including some amazing ex-Pebblers turned Googlers) has been working on this. And today is the day - the source code for PebbleOS is now available at github.com/google/pebble (see their blog post). https://ericmigi.com/blog/why-were-bringing-pebble-back https://ericmigi.com/blog/why-were-bringing-pebble-back
      - coldpie 2y ago
        Ha! Called it.
j45 2y ago
Big news. It was so good. Now a new group of people will get to consider it.
MostlyStable 2y ago
Managed to post my comment after dang moved the comments to this thread, so reposting here: Some commenters mentioned that the e-ink screen (and the accompanying battery life) was one reason why the Pebble is so beloved, which reminded me of the Basis Peak, which was primarily a health tracker watch with some (very limited) smart functionality (mostly just some notifications, if I recall), that also had an e-ink screen and a nearly 1 week battery life and had a sort of similar trajectory: Bought by Intel, then killed two years later after a battery related recall issue. It was, in my opinion, by far the best fitness tracker watch ever, and remains so to this day. Not so much because of it's actual features (which were relatively standard), but the software paradigm of simple yet effective exercise gamification that helped encourage exercise habit formation. 8 years later and I still miss it.
markus_zhang 2y ago
Just curious, I'm not good with C. Here in the code, https://github.com/google/pebble/blob/main/src/libc/alloca.c#L19 https://github.com/google/pebble/blob/main/src/libc/alloca.c... From what I googled, this is just for stack allocation in gcc. Does that mean Pebble only has stack allocation?
- Cieric 2y ago
  Alloca is allocations on the stack, seems the kernel might be stack based, but the os itself has it's own implementation of malloc. Which is heap based. https://github.com/google/pebble/blob/main/src/libos/include/os/malloc.h https://github.com/google/pebble/blob/main/src/libos/include... I'm also seeing references to rtos as the true underlying os though.
  - markus_zhang 2y ago
    Thanks found it, https://github.com/google/pebble/blob/main/src/fw/kernel/pbl_malloc.c#L228 https://github.com/google/pebble/blob/main/src/fw/kernel/pbl... Which calls heap malloc: https://github.com/google/pebble/blob/main/src/libutil/heap.c#L236 https://github.com/google/pebble/blob/main/src/libutil/heap....
  - tesseract 2y ago
    It was based on FreeRTOS, but FreeRTOS at the time was extremely bare bones and only provided a preemptive scheduler, task management, and synchronization primitives. Everything else (memory management, I/O, ...) had to come either from whatever libc implementation was in use, or be built from scratch.
    - markus_zhang 2y ago
      Thanks, does that mean early FreeRTOS is a good beginner project for OS study?
      - tesseract 2y ago
        In my opinion it's not always the most readable codebase, due to some idiosyncratic style choices, but it definitely has the advantages of being small and focused.
glietu 2y ago
This really made my day!
andybak 2y ago
This, Google Wave, Tilt Brush (and more recently Blocks). And probably others I've forgotten. This really does help mitigate the damage done by "Killed by Google" and people are genuinely grateful (personally in my case). But even better would be to fix the dysfunctional internal dynamics that cause this syndrome in what appears to be disproportionally more frequently compared to other corporations.
- talldayo 2y ago
  Eh, I take a much more "gloves off" approach to this mentality. If you bought an Airport thinking that it would be your forever router, you're a moron. Same goes for buying an eero, or Google Home, or even an iPad at this point. You don't own this hardware, you control nothing about it. The idea that products live forever is a bedtime story we tell ourselves, an utter fairytale of the software industry. Everyone kills software products. The problem is our attitude of entitlement towards things we sign an EULA to use. You "own" TikTok on the App Store? Pssh, please. You don't even own the software runtime you use TikTok with.
  - andybak 2y ago
    I think you're rather missing the specific point in the process of making a much broader one.
- gaudystead 2y ago
  In case anyone would like a more complete list of products Google has killed, here's a handy website to mourn your favorite dead product: https://killedbygoogle.com/ https://killedbygoogle.com/ RIP Google Wave... I had such high hopes when it was first released... :'(
  - andybak 2y ago
    In case I was unclear - I was aiming for the list of "unkilled by Google". Shorter but more interesting.
- sbrother 2y ago
abhishekjha 2y ago
Aren't floating point comparisons frowned upon? https://github.com/google/pebble/blob/main/src/libc/math/floor.c#L55 https://github.com/google/pebble/blob/main/src/libc/math/flo... I guess you can freeze some compiler options to give you consistent results.
- Gigachad 2y ago
  I've only done a little bit of arduino programming, but for that you had to import a whole library for floating point math which took a huge amount of space, and many chips didn't even have hardware support for it.
- deleted 2y ago
  [deleted]
- kccqzy 2y ago
  This case looks okay. It's converting a double to an int64_t and then back to double for comparison. It doesn't really suffer from the typical reason why floating point comparison is frowned upon, such as catastrophic cancellation. I've once optimized a function to be faster, and in a unit test asserted that the old slower version gives exactly the same floating point answer as the new optimized version. It's doable in some cases.
elevatedastalt 2y ago
People passing cynical comments at Google need to understand that at a big co like Google, something like this doesn't 'just happen'. It probably happened because some passionate L6/L7 engineer wanted to do it and pushed through the bureaucracy to get approvals for it, probably largely on their own time (by which I mean that this was at best a side-project for them and at worst a distraction that was losing them favor with their bosses). At every point in the process, they probably had to justify what they were doing to their leads, to lawyers, to privacy reviewers, who had no real stake in it and so had nothing to lose by saying No. They almost certainly won't receive any career progress out of this and would risk a setback if something slips through the cracks (such as some unredacted proprietary information). They did it because they felt it was the right thing to do. Good things happen through the actions of individuals like this. We should acknowledge and celebrate it when they do, anti-big-tech cynicism can wait.
- jayde2767 2y ago
  Maybe...the cynic in me says that someone feels this needs to be preserved because it will become another Google relic in favor of something newer, or more shiny. Or likely something written in Go...just a guess on my part...
  - frosting1337 2y ago
    What do you mean? Pebble was dead before Google ever bought Fitbit.
    - deleted 2y ago
      [deleted]
- nialv7 2y ago
  I do wonder how they successfully justified this to the higher ups. If anything, I would like to learn from them so I can better justify the things I want to do..
  - 2y ago
pyuser583 2y ago
How much work is being done in the RTOS space? I would think a lot, but then I hear programmers complain it’s not worth it. Are RTOSs still the future?
- Zamiel_Snawley 2y ago
  I’ve never heard that RTOSs are the future in general. With that said, there are a lot of great RTOS options out there today. 1) PREEMPT_RT recently brought realtime capability to mainline Linux[0]. 2) Amazon open sourced the safety-certified ThreadX[1]. [0] https://en.m.wikipedia.org/wiki/PREEMPT_RT https://en.m.wikipedia.org/wiki/PREEMPT_RT [1] https://en.m.wikipedia.org/wiki/ThreadX https://en.m.wikipedia.org/wiki/ThreadX
  - tim-- 2y ago
    ThreadX was open sourced by Microsoft.
    - Zamiel_Snawley 2y ago
      You’re right! I got my wires crossed with Azure and AWS.
- follower 2y ago
  TL;DR: No. Maybe? Depends. It's probably reasonable to make a distinction between "Real Time" desktop/server OS (on CPUs) vs "Real Time" embedded hardware OS (on MCUs). (Even aside from any hard-/soft- real time distinction.) On the embedded side, in addition to FreeRTOS (upon which Pebble OS is built), I'm aware of others with reasonably high profile such as: * Zephyr (Linux Foundation, C): https://en.wikipedia.org/wiki/Zephyr_(operating_system) https://en.wikipedia.org/wiki/Zephyr_(operating_system) * NuttX (Apache Software Foundation, C & C++): https://en.wikipedia.org/wiki/NuttX https://en.wikipedia.org/wiki/NuttX In addition, there's also some "up & coming" Rust language projects which fall somewhere along the "framework" to "OS" spectrum (in part, via https://arewertosyet.com https://arewertosyet.com): * Tock: https://github.com/tock/tock https://github.com/tock/tock * Embassy: https://github.com/embassy-rs/embassy https://github.com/embassy-rs/embassy * Hubris: https://hubris.oxide.computer https://hubris.oxide.computer On the desktop side, I seem to recall in the past, OS such as BeOS & QNX have been presented as a possible future for real time desktop OS that hasn't arrived. As someone else already mentioned, PREEMPT_RT being merged for Linux is a recent development somewhat in this space which could have impact on both desktop & "embedded" situations but suitability varies dependent on, say, whether you're wanting to use it for audio production versus controlling some 10 tonne robot operating next to humans. Hope this at least goes some way to answering your question. :)
nialv7 2y ago
Good for them, but also, what a colossal waste. Fitbit brought Pebble, Google brought Fitbit. They had everything to make a better version of a product that people _loved_, that _I_ loved. And what had them done? Nothing but a blatant display of anticompetitive power. (Yes I am still mad, 8 years later)
- pickledoyster 2y ago
  then, after the damage is done, they throw some scraps to the plebs and the comment section is full of thank yous to the monopolist
franczesko 2y ago
Google, if you hear, please open source Stadia
- ctippett 2y ago
  At least the controller firmware!
gigatexal 2y ago
Yeah huge influx of goodwill to Google for doing this. I signed up. I wanna see the pebble folks succeed here.
8thcross 2y ago
"This means the code being released contains all the build system files (using the waf build system), but it will not compile or link as released." But what can you do with this?
- astrange 2y ago
  Read it and educate yourself. Feed it to an LLM for training data. Put it back together with the binary bits from an existing build.
8thcross 2y ago
"This means the code being released contains all the build system files (using the waf build system), but it will not compile or link as released." What do we do with this POS?
maz1b 2y ago
Now if only Fossil did the same for Misfit and Misfit rays.. that would be very appreciated.
1337shadow 2y ago
very cool but garmin quatix is hard to beat
ryukoposting 2y ago
Whatever massive nerd spent their 10% time doing this: thank you. This is a bit of light in the cynical pit of lost proprietary code.
ThinkBeat 2y ago
The heading is misleading. Proprietary parts of the system have been removed on the current repo will not compile due to missing code. "" Proprietary source code has been removed from this repository and it will not compile as-is. This is for information only. ""
ThinkBeat 2y ago
The title is misleading. Proprietary code has been removed from the repo and the published repo will not compile because of it. Google states: "" This is for information only."" ""This is the latest version of the internal repository from Pebble Technology providing the software to run on Pebble watches. Proprietary source code has been removed from this repository and it will not compile as-is""
Acnapyx1 2y ago
[flagged]
christkv 2y ago
Now we need a new watch that can run this.
miohtama 2y ago
When do we get to the point an AI can auto complete the removed driver and other code?
richardw 2y ago
Give Google their due. It’s infinitely easier and risk free to just bury and ignore. Thank you, Google!
deleted 2y ago
[deleted]

1263 points by hexxeh 2y ago

https://github.com/google/pebble https://github.com/google/pebble

atYevP 2y ago

Lets go!

zitterbewegung 2y ago

This is pretty awesome. I had a Pebble but the battery went out and was sad to see that you had to buy used / refurbished. Being epaper and lasting for so long the best part of it was that it just managed notifications with my phone. I moved on to the Apple Watch from my brother (series 0) and it took awhile for the Apple Watch to have its killer application which was a fitness tracker.

jsheard 2y ago
You can still get watches which use the same MIP display technology as the Pebble and run similar "smart-ish" software with very long battery life. They tend to be marketed more as fitness/sports watches rather than smartwatches though.
- LeifCarrotson 2y ago
  MIP and e-paper are not exactly the same. I love my transflective MIP Garmin Fenix watch, but it's not nearly as high-contrast as my wife's Kindle, which uses a reflective MIP e-paper display. I would be an ideal candidate for a rePebble if I were not as happy as I am with my Garmin - though with their recent changes to inReach plans, crazy prices and lackluster features on the Fenix 8, and trend towards AMOLED displays (away from their roots, chasing the Apple watch market) they're not looking as amazing as they once did.
  - jsheard 2y ago
    I think you're mixing up e-paper (generic term for non-emissive reflective displays) and e-ink (the trademark for a specific type of e-paper display). The Pebble used a MIP LCD, just like Coros and Garmins MIP models, it never had anything in common with the e-ink displays used on Kindles.
ClassyJacket 2y ago
Every Pebble model used an LCD display. It being epaper has to be one of the most pervasive myths in tech history. It was a low powered, reflective LCD, so it did improve on other LCDs in those areas somewhat, but it wasn't eink technology.

maxehmookau 2y ago

This is cool! I remember receiving my first Pebble watch on kickstarter. I felt like I was in the future!

PokemonNoGo 2y ago
you still will be! In a few!

guzik 2y ago

Pebble is still the best and the only watch I've ever owned. Nothing has matched its simplicity and functionality for me.

spencerflem 2y ago

Don't say it often, but this is very nice of Google and they really didn't have to. Credit where it's due

GuB-42 2y ago
Yep, that's the kind of thing I would have expected "don't be evil" Google from 20 years ago to do. All is not lost.
skort 2y ago
[flagged]
- RobotToaster 2y ago
  It feels like they deliberately sat on it until it's almost completely dead.
  - freedomben 2y ago
    Fortunately you don't need to go on your feelings, because people involved have told us exactly what happened. RePebble guy (Eric) reached out, asked them to open source, they spent a ton of effort to get it releasable, and did just that. Unless you think everybody involved is lying.
- elaus 2y ago
  I prefer to shit on companies that don't even do "the bare minimum" and never publish source code of their dead products. Today, this is not Google.
  - deleted 2y ago
    [deleted]
  - scarface_74 2y ago
    I’m the first to criticize Google and say they have the attention span of a crack addled flea. But I have to commend them for this.

jsheard 2y ago

They've open sourced what they can, but these third party bits had to be stripped out: - All of the system fonts - The Bluetooth stack, except for a stub that will function in an emulator - The STM peripheral library - The voice codec - ARM CMSIS - For the Pebble 2 HR, the heart rate monitor driver

v9v 2y ago
I remember reading that the Bluetooth stack was one of the main differentiators for Pebble at the time due to its reliability, shame it's not included here.
- aryonoco 2y ago
  In 2014, that certainly was true. Every open source Bluetooth stack (i.e., Android, Linux and FreeBSD) was buggy and unreliable. Since then they rewrote the Bluetooth stack in Android twice, and finally what's in AOSP is quite comprehensive and reliable. It's now been merged into ChromeOS as well. I feel like it's the same about many of the items mentioned above, the free/libre offering in that space are a lot more polished than was the case 9-10 years ago. Back then the audio codec was still a patent encumbered minefield, now you can just use opus. The quality and diversity of free fonts is ordered of magnitudes above what it was 10 years ago. In short, it should be much easier for Eric to fill those gaps with free/open offerings than it was 10 years ago.
CuriousCosmic 2y ago
> - ARM CMSIS It's worth noting that CMSIS itself is open source but some of the drivers for this hardware probably were not.
- bri3d 2y ago
  Old versions of CMSIS had a weird "only for use with ARM hardware" license header, which also carried through into most BSPs. I don't think this was resolved until around CMSIS 4, so it might just be a matter of front porting since it looks like normal STM32 stuff which is mostly permissively licensed now.

rvz 2y ago

Give credit where credit is due, at least Google gives back to the community. Well done.

Alive-in-2025 2y ago
Well, better would have been investing in it and making it better. At least they didn't produce some awful spy on you thing that had nothing to do with p and called it pebble
- TulliusCicero 2y ago
  Pebble was dead long before Google got to own this IP.
  - Alive-in-2025 2y ago
    Do you think they have a future? I love the idea of a watch I can write simple little apps on. I looked at garmin, it was more challenging. the apple watch just has such a short battery life, I can't stand to charge it so much

ryukafalz 2y ago

As a Pebble user to this day (I'm wearing one right now in fact) this is amazing! I'm hopeful that this leads to development and fixes on these old devices that haven't been possible until now. And who knows, maybe we could even see new smartwatches running a derivative of the Pebble OS at some point? The old hardware's great but since they're not being made anymore it's only a matter of time before they break down. Props to Google on this.

fsflover 2y ago

Dupe: https://news.ycombinator.com/item?id=42845017 https://news.ycombinator.com/item?id=42845017

erohead 2y ago

Thank you, Google. You didn't have to, but you did. We are all are extraordinarily grateful. I wrote a blog post about our plans to bring Pebble back, sustainably. https://ericmigi.com/blog/why-were-bringing-pebble-back https://ericmigi.com/blog/why-were-bringing-pebble-back We got our original start on HN (https://news.ycombinator.com/item?id=3827868 https://news.ycombinator.com/item?id=3827868), it's a pleasure to be back. If you're interested in getting a new Pebble, check out https://rePebble.com https://rePebble.com

xvector 2y ago
I love what you're doing but the design of the pebble turns me off. Thoughts on making a sleek design that actually looks like a pebble?
Latty 2y ago
I did wear my Pebble until it died, and then never found another smart watch worth it for me. Will keep an eye on this for sure.
- ashirviskas 2y ago
  May I ask why it was so special for you? As I did not participate in all the hype and now I'm a happy owner of a Garmin watch and it does seem like it is closer in specs to Pebble than most other smartwatches. Other than the openness.
  - whs 2y ago
    I wear a Garmin and I still miss my Pebble Time that died to swelling battery. - Always on. Garmin has option to do that as well but it reduce the battery life to like 3 days. In outdoor my Pebble Time is very bright with zero backlight. - 5 days battery. I went on a trip to Japan without its proprietary charger, by the time I board my flight back it was on power save mode and it died the moment the plane landed. Garmin could do this if you set it to power saving mode, but the Pebble is in standard mode. One could argue that the Garmin do have more stuff like health monitoring that Pebble didn't. - Cheap and no frills. I want a second screen for my phone, not a health tracker. Originally my Pebble Time shipped with zero fitness features, and it later added a step counter once it's clear that the market direction go that way. - Garmin is quite thick, Pebble Time is thinner - The UI is simple - press up for past event, down for future event (calendar). Press the middle button for menu. Hold are configurable. Garmin has 4 main menus which are very confusing (fitness menu, shortcut menu, apps menu, system menu). - Lots of free apps and watch faces which I actually used (like a music app that show album art). I don't see any apps I would want to use on the Garmin, and they're mostly paid. The "hide in a hole while ceiling crush the map" game on Pebble was really well done. Now my Garmin use the simple time in Verdana watch face because I cba to find a decent one. - Even with low framerates, Pebble managed to deliver cute little animations. Replying to message show a flying paper plane, screen transitions have suitable animations (not generic ones like Android), and the best one is muting an apps show a Ostrich putting its head under the ground. The animation also hides how slow the hardware actually is, with later OS versions stalling over a second or two after a second long animation. - I think the phone app UI is not as good as say, Apple Watch, but it focus on apps and the store without the fitness features. Garmin's app is entirely about fitness and they hide smartwatch stuff in a menu plus another separate Connect IQ app. Overall the PebbleOS feel like a really solid and polished product than any smartwatch today. It do fewer things than most smartwatches, but that's all I care about and everything it does is very polished.

skort 2y ago

Hopefully this will accelerate the production of new hardware at some point. I misplaced my old Pebble Time and was excited for the Pebble Time 2 but those hopes were dashed when they closed up and fitbit had no interest in continuing to produce the watches that made Pebble what it was.

scarface_74 2y ago
Hardware is hard to almost impossible as a sustainable business as a small company unless there is a thriving ODM market and you can just use your own software.

whalesalad 2y ago

Are there any applications that are also open sourced? They mention snowy but it is giving a 404: https://github.com/pebble-dev/snowy https://github.com/pebble-dev/snowy

zorgmonkey 2y ago
I see a bunch of demo\test apps here https://github.com/google/pebble/tree/main/src/apps https://github.com/google/pebble/tree/main/src/apps
will0 2y ago
Try that URL again :)
- follower 2y ago
  TL;DR: Tintin in the Land of the Public Domain. I had forgotten Pebble used Tintin-themed code names (which I assume was the inspiration for the Snowy assistant app's name?)... Tangentially & coincidentally related: the Tintin & Snowy[0] characters entered the/a Public Domain[1] at the beginning of this year! Which means your lawyer might advise that you might now actually be able to use an actual original Snowy illustration[2] for the app logo... I mention this primarily because I am currently (in theory) developing a Tintin-themed game for an annual Public Domain game jam[3]. In reality, I've spent more time trying to locate scans of Tintin-related documents/illustrations[4] that actually fall under the constraints necessary for even US Public Domain[5]. ---- [0] Milou. [1] Well, actually[1a], maybe only in the US for 2025? And 2034 in Berne-associated countries? And 2054 in Belgium? Or any year if you're an AI, seemingly? Okay, perhaps it's better to not use an original illustration. Such are the joys of actually trying to interact with the Public Domain in good faith[1b]. [1a] https://en.wikipedia.org/wiki/Tintin_in_the_Land_of_the_Soviets#Public_domain_status https://en.wikipedia.org/wiki/Tintin_in_the_Land_of_the_Sovi... [1b] It just now occurs to me to wonder whether or not Milou can actually be referred to as "Snowy" given Tintin wasn't translated into English until the 1950s (late 1950s for the use of the name "Snowy" rather "Milou") (and as late as 1989 for the first title "Tintin in the Land of the Soviets"), given translations are AIUI new works? [2] First appearance: https://en.wikipedia.org/wiki/File:Tintin_and_Snowy_from_Tintin_in_the_Land_of_the_Soviets_(1929).jpg https://en.wikipedia.org/wiki/File:Tintin_and_Snowy_from_Tin... [3] https://itch.io/jam/gaming-like-its-1929 https://itch.io/jam/gaming-like-its-1929 [4] Pretty interesting finding different variants on archive.org, e.g. [4a][4b][4c]. (After all, "entering the Public Domain" is not of much value if the related material isn't accessible or the status is unclear. (Which is why recent trends in FLOSS project copyright year ranges statements bug me...)) [4a] Original French language album: https://archive.org/details/tintinnb/Francais/Tome%2001%20-%20Tintin%20au%20pays%20des%20Soviets/page/n3/mode/2up https://archive.org/details/tintinnb/Francais/Tome%2001%20-%... [4b] Second French language newspaper serialization: https://archive.org/details/cv-1930-50-pb/page/n3/mode/2up https://archive.org/details/cv-1930-50-pb/page/n3/mode/2up [4c] Original physical illustration: https://archive.org/details/tome-01-herge-chronologie-dune-oeuvre-1907-1931_202211/page/224/mode/1up https://archive.org/details/tome-01-herge-chronologie-dune-o... [5] Okay, yeah, this kinda turned into a Public Domain rant, sorry? :) (To bring it back to the topic at hand: "Hey, can't wait until this Pebble OS code enters the Public Domain in the year `2024 + YYY`." :) )

tucnak 2y ago

To somebody who's completely out of the loop, hears about Pebble for the first time—why is this big news? Are we going to see novel software written for defunct hardware, or is the hardware going to evolve now that the software is open?

Philpax 2y ago
People really like their Pebble watches, and this will help keep them alive into the future. In some future, we may see new hardware produced that could use some derivative of the resulting operating system.
- tucnak 2y ago
  I'm more of a mechanical-movement person myself, but I'm also fond of these little e-ink things; and indeed, they have come a long way. Maybe somebody makes a true e-ink pebble and designs it well, too.
jabroni_salad 2y ago
It's one of the original smart watches. What really sets it apart from modern ones is the e-ink display and dead simple interface (just a few buttons, no touchscreen). This simplicity means that it continues to do what it does well and doesn't really feel like it has aged badly. Certainly I would rather wear a pebble than a gen 1 Samsung watch or moto360. It's a delightful bit of kit that was sadly abandoned by owner and it's nice that they are open-sourcing a dead product instead of just leaving it to rot like so many other electronics are.
- Gigachad 2y ago
  The pebble did not have an e ink display, It was just a low power LCD.
  - Zamiel_Snawley 2y ago
    There were many models of Pebble. The original definitely had epaper[0]. [0] https://www.kickstarter.com/projects/getpebble/pebble-e-paper-watch-for-iphone-and-android https://www.kickstarter.com/projects/getpebble/pebble-e-pape...

insane_dreamer 2y ago

Still have my Pebble watch from 10 years ago in a drawer somewhere. Great watch, good times. I'm back to a "classic" analog watch as I realized I don't really want notifications. But I might buy a smart watch (probably Apple watch at this point since I have a bunch of iOS hardware) for the health features (HR, EKG, etc.)

bix6 2y ago

Can anyone comment on Google’s Business reasons for doing this? Is this actually an act of goodwill or is this a commodity, antitrust, etc. play?

deleted 2y ago
[deleted]
coldpie 2y ago
Given the original Pebble folks are using this to spin up a re-launch ( https://news.ycombinator.com/item?id=42845185 https://news.ycombinator.com/item?id=42845185 ), my guess is the Pebble folks just know someone on the inside at Google who managed to get the lawyers to sign off on it.
- bombcar 2y ago
  From my experience in large (and small) companies, trying to get something that is internally dead open sourced is usually not a huge fight against people saying no, just a laundry-list of things that need to be done before everyone will sign off on it. One motivated person at a decently high enough level can get it pushed through, as long as whoever the person making the decision asks about it says, 'eh, ok.'
  - 1337shadow 2y ago
    > Instead, we took a more direct route - I asked friends at Google (which bought Fitbit, which had bought Pebble’s IP) if they could open source PebbleOS. They said yes! Over the last year, a team inside Google (including some amazing ex-Pebblers turned Googlers) has been working on this. And today is the day - the source code for PebbleOS is now available at github.com/google/pebble (see their blog post). https://ericmigi.com/blog/why-were-bringing-pebble-back https://ericmigi.com/blog/why-were-bringing-pebble-back
    - coldpie 2y ago
      Ha! Called it.

j45 2y ago

Big news. It was so good. Now a new group of people will get to consider it.

MostlyStable 2y ago

Managed to post my comment after dang moved the comments to this thread, so reposting here: Some commenters mentioned that the e-ink screen (and the accompanying battery life) was one reason why the Pebble is so beloved, which reminded me of the Basis Peak, which was primarily a health tracker watch with some (very limited) smart functionality (mostly just some notifications, if I recall), that also had an e-ink screen and a nearly 1 week battery life and had a sort of similar trajectory: Bought by Intel, then killed two years later after a battery related recall issue. It was, in my opinion, by far the best fitness tracker watch ever, and remains so to this day. Not so much because of it's actual features (which were relatively standard), but the software paradigm of simple yet effective exercise gamification that helped encourage exercise habit formation. 8 years later and I still miss it.

markus_zhang 2y ago

Just curious, I'm not good with C. Here in the code, https://github.com/google/pebble/blob/main/src/libc/alloca.c#L19 https://github.com/google/pebble/blob/main/src/libc/alloca.c... From what I googled, this is just for stack allocation in gcc. Does that mean Pebble only has stack allocation?

Cieric 2y ago
Alloca is allocations on the stack, seems the kernel might be stack based, but the os itself has it's own implementation of malloc. Which is heap based. https://github.com/google/pebble/blob/main/src/libos/include/os/malloc.h https://github.com/google/pebble/blob/main/src/libos/include... I'm also seeing references to rtos as the true underlying os though.
- markus_zhang 2y ago
  Thanks found it, https://github.com/google/pebble/blob/main/src/fw/kernel/pbl_malloc.c#L228 https://github.com/google/pebble/blob/main/src/fw/kernel/pbl... Which calls heap malloc: https://github.com/google/pebble/blob/main/src/libutil/heap.c#L236 https://github.com/google/pebble/blob/main/src/libutil/heap....
- tesseract 2y ago
  It was based on FreeRTOS, but FreeRTOS at the time was extremely bare bones and only provided a preemptive scheduler, task management, and synchronization primitives. Everything else (memory management, I/O, ...) had to come either from whatever libc implementation was in use, or be built from scratch.
  - markus_zhang 2y ago
    Thanks, does that mean early FreeRTOS is a good beginner project for OS study?
    - tesseract 2y ago
      In my opinion it's not always the most readable codebase, due to some idiosyncratic style choices, but it definitely has the advantages of being small and focused.

glietu 2y ago

This really made my day!

andybak 2y ago

This, Google Wave, Tilt Brush (and more recently Blocks). And probably others I've forgotten. This really does help mitigate the damage done by "Killed by Google" and people are genuinely grateful (personally in my case). But even better would be to fix the dysfunctional internal dynamics that cause this syndrome in what appears to be disproportionally more frequently compared to other corporations.

talldayo 2y ago
Eh, I take a much more "gloves off" approach to this mentality. If you bought an Airport thinking that it would be your forever router, you're a moron. Same goes for buying an eero, or Google Home, or even an iPad at this point. You don't own this hardware, you control nothing about it. The idea that products live forever is a bedtime story we tell ourselves, an utter fairytale of the software industry. Everyone kills software products. The problem is our attitude of entitlement towards things we sign an EULA to use. You "own" TikTok on the App Store? Pssh, please. You don't even own the software runtime you use TikTok with.
- andybak 2y ago
  I think you're rather missing the specific point in the process of making a much broader one.
gaudystead 2y ago
In case anyone would like a more complete list of products Google has killed, here's a handy website to mourn your favorite dead product: https://killedbygoogle.com/ https://killedbygoogle.com/ RIP Google Wave... I had such high hopes when it was first released... :'(
- andybak 2y ago
  In case I was unclear - I was aiming for the list of "unkilled by Google". Shorter but more interesting.
sbrother 2y ago

abhishekjha 2y ago

Aren't floating point comparisons frowned upon? https://github.com/google/pebble/blob/main/src/libc/math/floor.c#L55 https://github.com/google/pebble/blob/main/src/libc/math/flo... I guess you can freeze some compiler options to give you consistent results.

Gigachad 2y ago
I've only done a little bit of arduino programming, but for that you had to import a whole library for floating point math which took a huge amount of space, and many chips didn't even have hardware support for it.
deleted 2y ago
[deleted]
kccqzy 2y ago
This case looks okay. It's converting a double to an int64_t and then back to double for comparison. It doesn't really suffer from the typical reason why floating point comparison is frowned upon, such as catastrophic cancellation. I've once optimized a function to be faster, and in a unit test asserted that the old slower version gives exactly the same floating point answer as the new optimized version. It's doable in some cases.

elevatedastalt 2y ago

People passing cynical comments at Google need to understand that at a big co like Google, something like this doesn't 'just happen'. It probably happened because some passionate L6/L7 engineer wanted to do it and pushed through the bureaucracy to get approvals for it, probably largely on their own time (by which I mean that this was at best a side-project for them and at worst a distraction that was losing them favor with their bosses). At every point in the process, they probably had to justify what they were doing to their leads, to lawyers, to privacy reviewers, who had no real stake in it and so had nothing to lose by saying No. They almost certainly won't receive any career progress out of this and would risk a setback if something slips through the cracks (such as some unredacted proprietary information). They did it because they felt it was the right thing to do. Good things happen through the actions of individuals like this. We should acknowledge and celebrate it when they do, anti-big-tech cynicism can wait.

jayde2767 2y ago
Maybe...the cynic in me says that someone feels this needs to be preserved because it will become another Google relic in favor of something newer, or more shiny. Or likely something written in Go...just a guess on my part...
- frosting1337 2y ago
  What do you mean? Pebble was dead before Google ever bought Fitbit.
  - deleted 2y ago
    [deleted]
nialv7 2y ago
I do wonder how they successfully justified this to the higher ups. If anything, I would like to learn from them so I can better justify the things I want to do..
- 2y ago

pyuser583 2y ago

How much work is being done in the RTOS space? I would think a lot, but then I hear programmers complain it’s not worth it. Are RTOSs still the future?

Zamiel_Snawley 2y ago
I’ve never heard that RTOSs are the future in general. With that said, there are a lot of great RTOS options out there today. 1) PREEMPT_RT recently brought realtime capability to mainline Linux[0]. 2) Amazon open sourced the safety-certified ThreadX[1]. [0] https://en.m.wikipedia.org/wiki/PREEMPT_RT https://en.m.wikipedia.org/wiki/PREEMPT_RT [1] https://en.m.wikipedia.org/wiki/ThreadX https://en.m.wikipedia.org/wiki/ThreadX
- tim-- 2y ago
  ThreadX was open sourced by Microsoft.
  - Zamiel_Snawley 2y ago
    You’re right! I got my wires crossed with Azure and AWS.
follower 2y ago
TL;DR: No. Maybe? Depends. It's probably reasonable to make a distinction between "Real Time" desktop/server OS (on CPUs) vs "Real Time" embedded hardware OS (on MCUs). (Even aside from any hard-/soft- real time distinction.) On the embedded side, in addition to FreeRTOS (upon which Pebble OS is built), I'm aware of others with reasonably high profile such as: * Zephyr (Linux Foundation, C): https://en.wikipedia.org/wiki/Zephyr_(operating_system) https://en.wikipedia.org/wiki/Zephyr_(operating_system) * NuttX (Apache Software Foundation, C & C++): https://en.wikipedia.org/wiki/NuttX https://en.wikipedia.org/wiki/NuttX In addition, there's also some "up & coming" Rust language projects which fall somewhere along the "framework" to "OS" spectrum (in part, via https://arewertosyet.com https://arewertosyet.com): * Tock: https://github.com/tock/tock https://github.com/tock/tock * Embassy: https://github.com/embassy-rs/embassy https://github.com/embassy-rs/embassy * Hubris: https://hubris.oxide.computer https://hubris.oxide.computer On the desktop side, I seem to recall in the past, OS such as BeOS & QNX have been presented as a possible future for real time desktop OS that hasn't arrived. As someone else already mentioned, PREEMPT_RT being merged for Linux is a recent development somewhat in this space which could have impact on both desktop & "embedded" situations but suitability varies dependent on, say, whether you're wanting to use it for audio production versus controlling some 10 tonne robot operating next to humans. Hope this at least goes some way to answering your question. :)

nialv7 2y ago

Good for them, but also, what a colossal waste. Fitbit brought Pebble, Google brought Fitbit. They had everything to make a better version of a product that people _loved_, that _I_ loved. And what had them done? Nothing but a blatant display of anticompetitive power. (Yes I am still mad, 8 years later)

pickledoyster 2y ago
then, after the damage is done, they throw some scraps to the plebs and the comment section is full of thank yous to the monopolist

franczesko 2y ago

Google, if you hear, please open source Stadia

ctippett 2y ago
At least the controller firmware!

gigatexal 2y ago

Yeah huge influx of goodwill to Google for doing this. I signed up. I wanna see the pebble folks succeed here.

8thcross 2y ago

"This means the code being released contains all the build system files (using the waf build system), but it will not compile or link as released." But what can you do with this?

astrange 2y ago
Read it and educate yourself. Feed it to an LLM for training data. Put it back together with the binary bits from an existing build.

8thcross 2y ago

"This means the code being released contains all the build system files (using the waf build system), but it will not compile or link as released." What do we do with this POS?

maz1b 2y ago

Now if only Fossil did the same for Misfit and Misfit rays.. that would be very appreciated.

1337shadow 2y ago

very cool but garmin quatix is hard to beat

ryukoposting 2y ago

Whatever massive nerd spent their 10% time doing this: thank you. This is a bit of light in the cynical pit of lost proprietary code.

ThinkBeat 2y ago

The heading is misleading. Proprietary parts of the system have been removed on the current repo will not compile due to missing code. "" Proprietary source code has been removed from this repository and it will not compile as-is. This is for information only. ""

ThinkBeat 2y ago

The title is misleading. Proprietary code has been removed from the repo and the published repo will not compile because of it. Google states: "" This is for information only."" ""This is the latest version of the internal repository from Pebble Technology providing the software to run on Pebble watches. Proprietary source code has been removed from this repository and it will not compile as-is""

Acnapyx1 2y ago

[flagged]

christkv 2y ago

Now we need a new watch that can run this.

miohtama 2y ago

When do we get to the point an AI can auto complete the removed driver and other code?

richardw 2y ago

Give Google their due. It’s infinitely easier and risk free to just bury and ignore. Thank you, Google!

deleted 2y ago

[deleted]