Shree KumarI put this project up on hackaday after some sane advise from various people, including
@Anool MahidhariaI have plans of starting a Kickstarter campaign for this kit - real soon. We have plans to upgrade KiteBoard to v2.0 - a supercharged upgrade, if I may say so. The new board will have powerful specs like a Octa-core 2GHz processor, 2GB RAM, 16 GB of storage, powerful GPU, WiFI a/c, two displays (both MIPI @1080p), 2 cameras, 4K video encode/decode, WiFi ac, USB 3.0, fast battery charging, plus a modem of course...
These are fairly top high end specs, but then we are thinking: let's take this to the next level. I am seriously considering to make the next version an Open Hardware design. If you look at all the files I have released till now, you find find files for side boards and flex cables. The main board, however, is not open at this time. This is set to change.
This could have some rather far reaching impact for various category of folks. I am not aware of any compact board that is so powerful, integrates a modem, is feature rich & allows the design of a compact, battery operated device. I am guessing that this will be heaven for students, startups, research folks, entrepreneurs, ... in short, anyone whose idea needs a mobile platform for their idea.
So -- hackaday, I ask you : how would you like the idea of an Open Hardware Android Phone ? ("mobile platform" would be more accurate, rather than "phone", really, if you see our design... )
Also, do weigh in on what you believe would be expectations from such a design - hopefully your dreams & maybe even rants.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.
[this comment has been deleted]
Hi Stuart,
I saw your comment first thing in the morning. It gladdens my heart to see that at-least *somebody* thinks that the *downgrade* is acceptable. Thanks a lot for your thoughts - seriously they are a lot more than I expected.
A whole lot of people fight & upgrade for 10-20% improvements every year. This looks meaningful to consumers, and I can understand that. But this is not any place. This is hackaday (I could make it phone-a-day if I had enough time on my hands :D ) . I am glad I made the initial decision to post my files here.
For makers, startups, researchers, and the discerning consumer, I find the small increments meaningless, BTW, as we can do so much more with the technology that is _in the past_. I mean, if you look at what I have posted on this page - the MSM8916 is from 2014. And those capabilities can get a serious boost by moving to a newer processor (as I have outlined earlier)- while preserving the extendability & hackability that makes the existing concept unique & useful.
Regarding the source code - it is useful to think of this as a LineageOS/Code Aurora Forum style implementation - with binary blobs for closed pieces like modem, camera, WiFi/BT, GPU, etc. We preserve the free parts (that are already free in AOSP, let me tell you) - in terms of the freedom to customize the Linux kernel & the whole Android Framework. That's a lot of stuff that OEMs are doing now - which the individual will get access to.
But let's not stop there - let's take it one step further - and create a new concept, a "maker OEM". Idea here is that a regular "consumer" OEM creates devices to suit consumers. A maker OEM helps the community build whatever they want to build, but in a viable way. This could be software features or hardware features.
Maker OEM uses their knowledge of the platform to expose all the features of the silicon possible - rather than hiding them for reasons like "consumers don't need it". Makers could find a use for it, and there is value exposing it. It's the Maker OEMs job to do that - if it is technically feasible.
An OEM maker can aggregate orders in thousands - which matches the volume needs of individual components at the component sourcing side - rather than millions - which is the scale at which a Smartphone vendor works.
We don't need to create a new concept here - group buys and order aggregation are already happening at various places.
To give a simplified example, community says "I need Sony IMX 999". Then maker OEM runs around checking feasibility... comes back & says - gimme 100$ a piece, 1000 piece orders. I will do it. At that point, it's clear to everyone what's needed. If there is demand, we do it. To give a more concrete example, "I need a bright 7 inch HD screen with 10 point touch for outdoor use.". Maker OEM runs around, figures that this is possible. And well -- guess what -- 100 $ a piece again. 1000 piece orders. If there are enough people needing this, then the idea goes through. Maker OEM has the capability, after all, and isn't fibbing. Afer delivering the thing, Maker OEM says - great you guys funded it - here's the design for it. Feel free to use it as you want.
If there is a future requirement for the same feature, the community has two choices - either try replicating it themselves (everything will be available), or come back to the "maker OEM". If they come to the maker OEM, then that's great - as the maker OEM is doing a lot of community service at a reasonable cost. Repeat orders can give the Maker OEM better leverage in terms of asking for a better price from the vendors - and that can *ideally* translate into a lower price in the final analysis for everyone. Everyone wins.
The dream of being able to build a phone entirely at home (with 3D printing, milling) is 100% realistic. The technology is already out there. I want to be the first one to run through a certification cycle, though, with the upgraded hardware.
I need 3000 people to make this happen. At almost 300$ a phone. Your thoughts ? How can you help me ?
Edit: rearrange slightly for readability.
Are you sure? yes | no