131–140 of 251 posts
This is what we (early people in the android wear team) wanted android wear to be, until word from the top came down that "it shall run android, or it shall not exist". The rest is history....
Ah, I don't see sleep tracking. Gimme sleep tracking and I'm in!
What's flashed into the device is the whole system image, and it's up to you (that's the whole point!) to decide what this image does.
Anything sample code they provide is to be seen as a sample only.
Earlier quoted context omitted.
Why do you expect them to restrict what you can put on it (i.e. enforce a single OS), when the point seems to be for people to do whatever they want with it?
Because without a standard OS stack it is going to be the "Year of FOSS Watch"™.
It doesn't work by installing "apps", but rather, the whole system image is built from _your_ code. Which makes sense on a device that has 64KB RAM.
Any code samples they provide are just that: Samples.
If what you're looking for is a general public oriented device, this is not it. There's plenty in the market to pick from.
Earlier quoted context omitted.
ESP32 in deep sleep modes is reasonably battery friendly (all depending on your frame of reference, of course.) 5uA in RTC-only and 10+ uA in RTC+ULP sleep.
That's true, but then you don't get notifications or anything, since it's essentially off.
Earlier quoted context omitted.
I think GPS is a significant cost in the power budget. Many users would prefer longer battery life. The option to enable GPS would be nice, but it cuts into cost and size budgets.
Amazfit Bip (S) has a GPS and still lasts for about 2 weeks in the same form factor.
Earlier quoted context omitted.
That's true, but then you don't get notifications or anything, since it's essentially off.
Presumably for a watch use case, you'd plan to deep sleep (ULP) or hibernate (RTC) 98+% of every minute and turn the radios on as infrequently as you could stand to get external notifications. I don't need split-second precision on my notifications if the alternative is a much longer battery life.
Earlier quoted context omitted.
Why do you expect them to restrict what you can put on it (i.e. enforce a single OS), when the point seems to be for people to do whatever they want with it?
Because without a standard OS stack it is going to be the "Year of FOSS Watch"™.
Earlier quoted context omitted.
Presumably for a watch use case, you'd plan to deep sleep (ULP) or hibernate (RTC) 98+% of every minute and turn the radios on as infrequently as you could stand to get external notifications. I don't need split-second precision on my notifications if the alternative is a much longer battery life.
True, I guess the watch must have some sort of external circuitry that can wake it up every so often.
Earlier quoted context omitted.
The pine tab is a table available from the same site. I'm looking at it, but it isn't ready for someone with my limited hacking time - yet (I expect this to change in a few months)
I've got my eye on that one if it returns to stock. Thanks! A slightly alarming statement on the page: "Small numbers (1-3) of stuck or dead pixels are a characteristic of LCD screens. These are normal and should not be considered a defect." I've bought dozens of screens in my life (phones tablets monitors TV's) and have never had a stuck pixel. Is it actually normal?