> That's also clarified in the blog post. Sorry, I haven't posted the link before: https://puri.sm/posts/supplying-the-demand/ https://puri.sm/posts/supplying-t

> That's also clarified in the blog post. Sorry, I haven't posted the link before: https://puri.sm/posts/supplying-the-demand/ https://puri.sm/posts/supplying-the-demand/ The blog post says one thing. Nobody in the community has posted anything about actually having an Aspen in hand and working on it yet. > They are and will be available to anyone owning the phone, just like I said in the previous post. Technically I own one because I plonked down the ~$500 or whatever it was to preorder one. I'm in the later batches, but I have paid for one. It would be nice to get at those schematics, if they exist publicly. Sadly, I haven't been able to find them, and you haven't been forthcoming except to point me to a schematic and board art for the dev board. > You said: even the dev units have no details on their construction > so I showed you the full open sourced design. Ah, sorry -- I should have been more clear in the first post. I was referring to the schematics for the EmCraft SOM, without which trying to manage thermals and manipulating device trees is going to be problematic. Frankly, it's a bit disingenuous to call that a full open sourced design -- half the dev unit's board is missing and buried inside that EmCraft symbol. > You said: the community can't get in there to help. And they can't without schematics for the EmCraft SOM. I was prepping to actually help out at one point, but stopped because I couldn't find the EmCraft SOM schematic. > you're moving the goal posts and making me look wrong. No, you're reading too much into the original post. I said the community hasn't been able to help. Purism isn't the community, and your link points to a commit from a Purism account. I fail to see how I moved the goal posts here. > See, that's the problem with your posts here. I'd much rather have you get corrected by asking questions at the community channels, which are frequently answered by engineers rather than post under-researched false things on unrelated forums. By posting wrong things, you're undermining the project, which you yourself claim to support. I have asked in the community and dev board channels, on Matrix, and I have spoken with engineers involved. Some questions were answered, some weren't. Others were answered with handwavy "eventually" statements. I mentioned this in the first post I made about this.