201–210 of 251 posts
Earlier quoted context omitted.
You might have just convinced me to buy the devkit. What do you use it for in your masters thesis?
Sadly I'm not sure what I'm allowed to make public just yet because I write the thesis for my company :(
Earlier quoted context omitted.
Well, that's exactly my point when I speak of compromises. If you want to be nude and pure then you go for the A72/A53, well aware that you're selling hardware that is almost a decade old and can't be used as a daily driver today. Otherwise, as unpleasant as it can be, you have to make a deal with Broadcom/Qualcomm, or get some other vendors to license their ARM chipset to you. The latter doesn't seem like the end of…
> you're selling hardware that is almost a decade old and can't be used as a daily driver today. My iPhone 6S is more than 5 years old, and is perfectly usable as a daily driver (and my SO's iPhone 6 is too - it's 6 years old, only runs iOS 12, but still gets security updates and is perfectly usable). It's fine if on the freedom/performance/up-to-dateness tradeoff, you're not pine64's customer. Many people are.
Earlier quoted context omitted.
I'm not really familiar with this space, but what did you think it should run? I can't imagine a team building a smartwatch at Google at that time expecting anything other than Android.
I would assume something like one of the RTOSes like what's listed for the PineTime? Seems like it'd be easier to get power consumption low and keep the watch speedy that way, then just interface with a phone, etc., over bluetooth or something.
Earlier quoted context omitted.
From my understanding of GNSS (I did some research on it in school, about a month full-time), that only works if you have a clock synchronized to a few nanoseconds and of course up to date satellite information. This is very plausible if you do it once a second, because in 1 second your quartz doesn't drift that much or you can count cpu clock cycles perhaps, and the ephemerides don't change that often. But once you…
I would assume a common use for GPS in a watch is workout tracking, so it gets manually started and stopped when they go for a run. it'd need more time at the start to get a clean fix, but in good conditions could probably get by with short blips.
Sadly moved to an Apple Watch, since the Pebble ecosystem started to die.
Lack of NFC :( But probably even if it had it it wouldn't work with Google/Apple Pay, for me payments using my watch would be the best application of "smart" together with notifications.
>But probably even if it had it it wouldn't work with Google/Apple Pay Defy not with 4MB of storage.
On the other hand good luck with getting such a device accepted by anyone in the financial industry. (On the other hand you probably could build something that proxies to your real physical card)
I have a pinetime and the form factor is great (until I lost the back plate, next one will be sealed). All the opensource activity around the watch is also great. The biggest drawback to me is only 64k of ram. Thats a Commodore64's worth of ram. The 240x240 screen is 57kbytes, it must have its own display ram. Also NordicSemi never seemed to be particularly opensource friendly. I'm hoping for a future RISCV edition o…
Apache have a fully open source Bluetooth LE stack for most of the Nordic Semi chips, in part because they actually documented their radio hardware unlike most other manufacturers.
I'd be the perfect target for the products of a company like Pine. A long-time geek who uses open-source software on nearly all of his devices, a tinkerer who doesn't mind recompiling a kernel or picking a solderer to make things work, and someone who seeks for absolute flexibility from his devices with zero corporate compromises. Unfortunately, the mediocre hardware used in their devices keeps holding me back. First…
I'd be the perfect target for the products of a company like Pine. A long-time geek who uses open-source software on nearly all of his devices, a tinkerer who doesn't mind recompiling a kernel or picking a solderer to make things work, and someone who seeks for absolute flexibility from his devices with zero corporate compromises. Unfortunately, the mediocre hardware used in their devices keeps holding me back. First…
That said, I too would love to see higher specced devices from Pine. An update to the Pinebook with a fancy new ARM chip and 16GB ram would be tempting indeed.
I'd be the perfect target for the products of a company like Pine. A long-time geek who uses open-source software on nearly all of his devices, a tinkerer who doesn't mind recompiling a kernel or picking a solderer to make things work, and someone who seeks for absolute flexibility from his devices with zero corporate compromises. Unfortunately, the mediocre hardware used in their devices keeps holding me back. First…
It's always hard to stay true to ones beliefs; when it comes with so many shortcomings.