Build Your Own Android Smartphone

Let’s get this out of the way first – this project isn’t meant to be a replacement for your regular smartphone. Although, at the very least, you can use it as one if you’d like to. But [Shree Kumar]’s Hackaday Prize 2018 entry, the Kite : Open Hardware Android Smartphone aims to be an Open platform for hackers and everyone else, enabling them to dig into the innards of a smartphone and use it as a base platform to build a variety of hardware.

When talking about modular smartphones, Google’s Project Ara and the Phonebloks project immediately spring to mind. Kite is similar in concept. It lets you interface hacker friendly modules and break out boards – for example, sensors or displays – to create your own customized solutions. And since the OS isn’t tied to any particular brand flavor, you can customize and tweak Android to suit specific requirements as well. There are no carrier locks or services to worry about and the bootloader is unlocked.

Hackaday Show-n-Tell in Bangalore

At the core of the project is the KiteBoard – populated with all the elements that are usually stuffed inside a smartphone package – Memory, LTE/3G/2G radios, micro SIM socket, GPS, WiFi, BT, FM, battery charging, accelerometer, compass, gyroscope and a micro SD slot. The first version of  KiteBoard was based around the Snapdragon 410. After some subtle prodding at a gathering of hackers in Bangalore, [Shree] moved over to the light side, and decided to make the KiteBoard V2 Open Source. The new board will feature a Snapdragon 450 processor among many other upgrades. The second PCB in the Kite Project is a display board which interfaces the 5″ touchscreen LCD to the main KiteBoard. Of Hacker interest is the addition of a 1080p HDMI output on this board that lets you hook it up to external monitors easily and also allows access to the MIPI DSI display interface.

Finally, there’s the Expansion Board which provides all the exciting hacking possibilities. It has a Raspberry Pi compatible HAT connector with GPIO’s referenced to 3.3 V (the KiteBoard works at 1.8 V). But the GPIO’s can also be referenced to 5 V instead of 3.3 V if you need to make connections to an Arduino, for example. All of the other phone interfaces are accessible via the expansion board such as the speaker, mic, earpiece, power, volume up / down for hacking convenience. The Expansion board also provides access to all the usual bus interfaces such as SPI, UART, I²C and I²S.

To showcase the capabilities of the Kite project, [Shree] and his team have built a few phone and gadget variants. Build instructions and design files for 3D printing enclosures and other parts have been documented in several of his project logs. A large part of the BoM consists of off-the-shelf components, other than the three Kite board modules. If you have feature requests, the Kite team is looking to hear from you.

When it comes to smartphone design, Quantity is the name of the game. Whether you’re talking to Qualcomm for the Snapdragon’s, or other vendors for memory, radios, displays and other critical items, you need to be toeing their line on MOQ’s. Add to this the need to certify the Kite board for various standards around the world, and one realizes that building such a phone isn’t a technical challenge as much as a financial one. The only way the Kite team could manage to achieve their goal is to drum up support and pledges via a Kickstarter campaign to ensure they have the required numbers to bring this project to fruition. Check them out and show them some love. The Judges of the Hackaday Prize have already shown theirs by picking this project among the 20 from the first round that move to the final round.

Continue reading “Build Your Own Android Smartphone”

Google Releases Project Ara MDK

Ara Modules

 

It’s been a little while since we’ve heard about modular smartphones, but Google has just released the Module Developers Kit (MDK) for Project Ara. The development kit gives an overview of the inner workings of the project, and provides templates for building your own modules.

Once you’ve agreed to the license agreement and downloaded the MDK, you’ll find a large specification document. It explains how a phone will comprise of many modules loaded into an endoskeleton, giving mechanical support and electrical connections. An interface block provides each module with power and data over LVDS. Modules are held in place by an electro-permanent magnet which can be toggled by software.

When you’re finished with the specification document, you can dive into the reference designs. These include templates and actual modules for WiFi, thermal imaging, a battery pack, and more. Mechanical CAD is provided as STEP files and drawings, and electrical design files are provided as Altium projects and PDF schematics.

We discussed both Project Ara and Phonebloks on Hackaday in the past, but now we’re starting to see real details. Google’s Project Ara Developer Conference takes place on April 15th and 16th, and you can register to take part remotely for free. Is this the start of an open, modular phone? Let us know what you think.

[Thanks to Adam for the tip]

Ask Hackaday: Does Project Ara Solve The Phonebloks’ Problems?

motorolaProjectAra

Our tips line is blowing up again, this time directing us to Motorola’s Project Ara: a phone with modular components that plug into a base “endoskeleton.” If you missed the news coverage strewn across the web and you are doing a double-take, that’s because Project Ara is frighteningly similar to the (presumed vaporware) Phonebloks concept from a few weeks ago. Phonebloks was the subject of our last “Ask Hackaday” article, generating hundreds of comments ranging from those defending the concept to those furiously opposed to it.

There’s a conspiracy theory circulating that suggests Motorola released the Phonebloks concept as a viral marketing scheme to generate hype before revealing the official product line. We suspect it’s a bit less conniving. As [jorde] explained on Hacker News, an Israeli startup, Modu, had developed a similar modular cell phone several years ago, and Google bought the patents in May of 2011. A few months later, Google bought something else: Motorola. It seems likely that Project Ara is merely a resurrected and revised Modu, and Motorola conveniently announced it in the wake of Phonebloks’ popularity. Regardless, Motorola has announced that they have partnered with Phonebloks’ creator Dave Hakkens .

So what’s different? Phonebloks was met with cries of “vaporware!” and fervent arguments raising concerns about unavoidable hardware limitations. Motorola claims their goal is:

to do for hardware what the Android platform has done for software: create a vibrant third-party developer ecosystem, lower the barriers to entry, increase the pace of innovation, and substantially compress development timelines.

Unlike Project Ara, Phonebloks didn’t consider open-source hardware (Wayback Machine link), and Motorola makes an interesting argument here: that advances in 3D printing indicate an evolving “open hardware ecosystem,” and the next era of phone development may rest in the hands of your average hacker or a small startup company. Some speculate that the Ara will be similar to the relationship between a PC and its peripherals: Motorola provides the essential guts while giving you some slots for attaching additional components. Let us know in the comments what you think about Project Ara: is it just more vaporware, or a watered-down but plausible alternative to Phonebloks?  And, perhaps most important: do you, as a hacker, want a phone that supports open hardware and lets you plug in “peripherals?” The Phonebloks website has since changed to reflect the partnership with Motorola, and includes a new video that you can watch below.

Continue reading “Ask Hackaday: Does Project Ara Solve The Phonebloks’ Problems?”

Ask Hackaday: Can We Do Better Than Phonebloks?

Our tips line is on fire with suggestions for us to cover the modular cell phone concept named Phonebloks. The phone’s designer states the problem as follows:

A phone only lasts a couple of years before it breaks or becomes obsolete. Although it’s often just one part which killed it we throw everything away since it’s almost impossible to repair or upgrade.

His solution is the above pictured phone, with modular components for each feature: wifi, camera, battery, etc. Rather than upgrade your entire phone, upgrade just the parts you need. A wave of followers have thrown their support behind this concept, and perhaps their hearts are in the right place hoping to reduce waste and cost. Behind the scenes here at Hackaday, however, the response has been a unanimous facepalm. The primary objection (other than design implausibilities) should be obvious: dividing the phone into exchangeable bits does not inherently reduce waste. Those bits have to go somewhere.

Now, don’t rush to the comments section to identify additional problems; there’s a juicy Reddit thread for that. Instead, we want to take the high road: Can we do better? Can we make a phone for the future that is less wasteful to produce, more easily recycled, and possibly upgradable? What would be included in its features, and how would we do it? Check out a video of the concept phone and tell us your alternatives after the break.

Continue reading “Ask Hackaday: Can We Do Better Than Phonebloks?”