Imagine dropping one of those buggers in a busy pub. 30 fiddly little parts scattered across the floor.
Train platform droppage: also bad.
Google-owned Motorola Mobility hopes to shake up the smartphone world with its freshly announced Project Ara: an open platform for modular snap-together handsets. Project Ara - swappable hardware mobile Project Ara ... swappable mobile hardware parts Googorola plans to work with the Phonebloks project on the open-source …
"Imagine dropping one of those buggers in a busy pub. 30 fiddly little parts scattered across the floor.
Train platform droppage: also bad."
What's the difference compared with the old feature phones that after a drop? And what happens to a shiny last generation smartphone after the accidents you described?
I leave here the video http://www.youtube.com/watch?v=oDAw7vW7H0c#t=54 about the lock of the block, minute 0:54
Brilliant idea, clearly just at v0.5, but upgradeable, no sending the whole phone away for a dicky compass, just swap a part out.
Only problem will be to make it snaptogetherable will be size, the component enclosures will make it physically larger than a Samsung miniaturised device.
"Brilliant idea, clearly just at v0.5, but upgradeable"
Yeah genius. Just at the time the whole industry is moving away from this sort of thing. PCs are dying on their ass and laptops are getting so small there's no room for even a DIMM module. I agree that lots of geeks like this sort of thing, and the downvotes I'll get for this will prove that Reg readers think this is a winner. A good business model though? I really strongly doubt it.
I think it's a generational thing. The generations who grew up in the 80's or earlier didn't have insane amounts of toys and other expensive stuff so we took care of them carefully.
There appears to be a trend heading towards "just buy another one" that shows up more and more the younger people get.
C'mon Mr Campbell
There are people with restricted use of their hands through arthritis, just as there are people have less motor control of their hands for a variety of reasons, some with less strength in their fingers.
Even if your phone never slips from your fingers, you might trip and fall down... in which case you would want to be able to call for help even if you've fallen on your phone in your pocket. (I do hope you don't fall over!)
Other people have young children who might drop a phone onto the ground.
Personal experience does have a place in product design, but taking the experience of others into account can often result in the better product.
Yeah, sure, phones do occasionally hit the ground for unavoidable and explainable reasons. But in the huge, huge majority of cases, the reason is "User is a blithering idiot who has their attention elsewhere than what they are doing with a £500 electronic device". This I find hard to understand, and I find it even harder to understand that those who do regularly drop their phones always have an excuse ready. So they shell out lots of money for a new phone, and do it all over again, because they have lied to themselves about why it happened.
I think I have finally made this point stick with my eldest daughter, simply by ensuring that she pays for her own phones, and pointing out how much time she has taken to earn the money to do so. We'll see how long her new one lasts.
" I'd rather have half a dozen components that need re-assembly than one big broken component that needs binning."
Why do you assume that the energy dissipated by hitting the floor fast will be solely expended in neat dis-assembly? There's a strong chance that however the phone is made the glass screen and digitiser will be ****ed by the P1 percussive forces from being dropped. And there's no reason to believe that the other modular components will be sufficiently strongly engineered to resist impact damage. In my experience things like locating lugs are more likely to break than to unclip gracefully when dropped, and it isn't the soldered on or SoC integrated components that get mangled by a fall anyway.
This looks like Google taking a run up, with a view to planting a hefty kick in the (other) phone companies' collective
After all, it's probably to Google's benefit if its users can save money on phone replacements by having the option to upgrade only certain components (so as to leave more left over to buy apps, movies, music, and whatever Google advertises at them).
I (forlornly?) hope it works, I'd like to be able to build my phones the same way I build my desktops.
Not just phones. Leave the 3G/4G or other radio chipsets out, and you've got a (hopefully cut price) Android powered iPod.
Maybe there could be options for D pads and button modules? Screen in the middle, D pad on left, buttons on right, instant handheld games console. Swap the D pad and buttons around if you're southpaw (or just like it that way).
Bloody big camera lense on back, screen on front, sack everything else off asides an SD card module, and you have yourself a "smart" camera.
This could really be an awesome development.
My first thought was that this could extend well beyond phones. Or bring phones into new areas, whichever way you want to look at it.
As an example, the free flying community (Hang gliders etc.) use free software called XCSoar on Android for maps and airspace avoidance. Swap in proper altimeter and variometer modules and you're properly in business with a real flight instrument. It would be too big to be a regular phone then but who cares? That's not the point. There must be hundreds of specialist fields where a smartphone almost but not quite does the job you want.
This could be more versatile than a Raspberry Pi and without all the wires hanging out and Heath Robinson cases. Really hope they can get it to market.
The concept? Love it. A lot. However, I think they mean "open design" or possibly "open engineering", but this has nothing to do with "open source".
The only caveat, that I care about anyway, is that if the drivers aren't as open as the design then they can stuff it.
On the other hand, given that each component is interchangeable, that presents the opportunity for smaller, less monopolistic companies (or even hobbyists) to offer alternative modules unafflicted by the cancer of "IP".
When the wifi on my Lumia stopped working on the Underground
Nokia said it was a Virgin Wifi problem
Virgin said to contact my service provider, after all that's who I pay the bill to.
Vodafone (for it was them) said it was a Nokia problem.
With an "open source" phone I can see nothing but problems.
Of course it's not the first time Motorola has been here (and given up)
What on Earth does Microsoft have to do with open source? And what does that dongle linked to, from 2004, have to do with Phonebloks? Bit of a Chewbacca argument really.
And why are you trying to get wifi in a tunnel under the ground?
"What on Earth does Microsoft have to do with open source? "
Quite a lot actually. Microsoft made loads of contributions to Linux for instance.
Windows Server is also the most scalable NFS 4.1 server on the market with the best clustering features....
Quite a lot actually. Microsoft made loads of contributions to Linux for instance.
The most significant contribution I've heard of Microsoft dishing out to the Linux kernel has been something about Hyper V.
This wasn't through choice. This was through Microsoft breaking the terms of the GPL, being found out, and being told that they either cease to distribute their code forthwith, or release it as GPL, as per the terms of the code they half-inched. They then painted this as an exercise in generosity, rather than the truth of being caught with their pants down.
All while continuing to threaten anybody daring to use the toy Unix without paying them a tax over dodgy patents that they still won't disclose, and which still haven't been properly examined (because they haven't been disclosed). This is without getting into the ethics of even allowing software patents in the first place.
I'll ask again: What does Microsoft have to do with Open Source?
> Quite a lot actually. Microsoft made loads of contributions to Linux for instance.
No. You are wrong again. Microsoft made _one_ set of 'contributions' which were entirely related to supporting their virtual machines.
> Windows Server is also the most scalable NFS 4.1 server on the market with the best clustering features....
That is just marketing crap.
"As far as locking mechanisms go, this was solved a long while ago with the ZIF socket, no?"
No. ZIF sockets clamp the pins into the socket, but they don't lock them in. Using ZIF in this context could still result in the modules popping off if the device were dropped. You need a ball or flange of some sort at the end of the pins, which the phoneblok's design has. How secure that will be remains to be seen.
I really like this concept on so many levels, but I'm afraid that primarily because I'm a geeky, built your own kinda guy. I'm not sure there is enough market out there to support this, since most people just want a phone.
Take a look at a desktop vs a laptop. The desktop is designed to take standard modules, so there is lots of empty air in there to allow for them, copious air flow, standard connectors etc. The laptop on the other hand has few user replaceable parts (mostly memory and disk, and not always all of those), but is engineered for small size and long battery life.
In a world where smaller, lighter and faster are important selling points I really can't see this doing well.
Bad analogy. The only reason most desktops are as huge as they are is because of slavish attention to backwards compatibility. Plus, you can built very compact desktops from off-the-shelf parts (mostly borrowed from laptops, in fact) nowadays.
This will depend on making the modules small and standardizing on size and shape, though...
>The laptop on the other hand has few user replaceable parts (mostly memory and disk, and not always all of those)
In the 90s I had a TI laptop that had a plug in DVD that could be swapped with a floppy drive. The disk was in a slide out tray and could be swapped, additional trays could be bought. The RAM was swappable. The battery could be changed, and it also had PCMI card slots for network, USB, WiFi, modem, etc.
Nice idea for things which are already fairly self-contained, such as a battery or camera.
However, how would it work in terms of making things like memory (one obvious candidate) swappable? What's the side-effect of changing all of those pins you'd normally get on a memory chip, into something that would work on 4/5 pins (from what I can see in the image).
Genuinely interested in technology terms, but not sure I'd buy one. For the same reason I don't particularly want to fiddle around with my car or laptop.
quote: "However, how would it work in terms of making things like memory (one obvious candidate) swappable? What's the side-effect of changing all of those pins you'd normally get on a memory chip, into something that would work on 4/5 pins (from what I can see in the image)."
Serialisation of a parallel bus works fine, you just need a step up in clock speed equal to the decrease in lines to achieve a similar throughput (see SATA vs PATA etc.). If these are running a serial bus similar in speed to USB 3.0 or SATA 3 (5Gb / 6Gb) between components then there's a reasonable amount of bandwidth available, current SATA 3 SSDs don't manage to saturate the bus yet ;)
Some stuff will still benefit from parallel access (especially RAM <-> CPU transfers) but most other components (screen, non-volatile storage, radio) already tend to use serial buses anyway. I suspect they'll end up putting the CPU and RAM into the same package and serialise the rest, or just live with the bottleneck of a serial RAM interface.
I'd actually be really interested in this assuming it actually takes off; I'm one of those techies that loves to play with stuff and take it apart. Piecemeal upgrading of the phone instead of having to purchase a discrete new model definitely appeals :)
You can't add SATA, USB3, or some equivalent, to everything. It would be too expensive, and probably also electronically noisy in a confined space, which would make certification unlikely without some very careful EMC design - tricky if you're trying to work with something that has an aerial, like WiFi or Bluetooth.
There's also the problem that many components just aren't small enough to make this work. I think it's unlikely you'll get a WiFi aerial or GPS unit tiny enough to fit into one of the itty-bitty boxes. And if you try and fit it into a bigger box, you squeeze out space for useful stuff, like a battery.
Surely you'd make the Processor/RAM/GPU/screen connections special ones and force them to sit next to each other sensibly, rather than just anywhere on the bus? Everything else could sit on the bus somewhere and effectively not have a defined physical 'place'. You don't plug RAM into the SPI on desktop, for instance, so I don't see why they couldn't have a different connection.
Yep. I took my phone apart recently (three years old and the home button was getting iffy). The iFixit instructions were very insistant to never touch any of the shiny contacts, pins or socket, as the tolerances are so tight that a grease film will likely kill the conductance - and I did indeed have to open it up twice more to clean off the wifi and the touchscreen connectors.
The other thing with this is that most of the content of a phone is battery, plus some aerials and the interconnects. The CPU/flash/comms electronics are a tiny tiny sliver. So it's not a set of reasonably sized lego pieces as per the pic, there's one huge lump for the battery and a few bits'n'bobs.
Those bits are seriously tightly packed, with chippery and aerials shaped and overlaid for best space usage. If you split out the cellular radio and its aerial, then the bluetooth and its aerial, wifi, GPS, NFC... you'll end up with a device double its size of a normal integrated phone. If you're assembling a 'phablet' then that's not fatal, but anything under about 5" screen is probably not possible.
Take a look at any disassembly guide for a modern phone, and try and work out how to break that into functional lumps. There aren't enough to make a modular assembly worthwhile, I don't think.
As fun as the swappable modules look, I have to wonder if this will cause more problems than it solves. With this not only do I need to know if the next Android update supports my phone, but also how it supports my various add-on modules. That said, if anyone is in a position to accomplish this in at least a semi-practical manner, it's Google (expect to see module compatibility checking extend deep into the play store).
Swap out old CPU block, insert new CPU block, OS gets updated with the CPU? Hell, it might even promote a better chance of getting upgrades for the existing hardware, what with manufacturers not having the incentive to persuade you to buy a whole new device any more.
Really, after trying to use an older model iPad with a newer revision of iOS, I don't know whether having a bleeding-edge OS revision on older hardware, at least with locked down toys like smartphones and tablets, is a really good idea.
Tap.. tap.. fucking REACT YOU SLOW PIECE OF SHIT.. tap.. tap.. ah, there we are.
Seriously, don't ever listen to some iFan saying anything about Android glitches. An old phrase about stones and glass houses comes to mind.
A journalling filesystem on a flash device that implements a FTL, such as a SD card, EXT3 is fine.
True flash file systems are for MTD flash, of which my preference is for UBI. Most of these cannot be used on regular block devices without some MTD emulation trickery.
(Been there, done that.)
Should point out, not familiar with NILFS2 specifically… EXT3 has the nicety that other OSes can read/write it. Windows can access it using EXT2IFS. AFAIK there are FUSE drivers for MacOS X, and of course, the BSD derivatives all support it.
This post has been deleted by its author
...appears to take two modules each of three sizes and four formats -- small square, large square, thin rectangle long-edge-in, and thin rectangle short-edge-in. I foresee problems unless module-makers produce their parts in multiple formats: "I want THAT camera module, but they only come in 'thin-short-edge-in' and I only have a 'small-square' slot left!"
OTOH, it's probably a good thing that it's Googorola trying this, rather than Nokia/Microsoft... With tiles on both sides, you might not be able to tell which side of the phone you're looking at after a night out!
I do doubt this will be something where you can get a phone and just keep putting newer and newer parts on. However, I do like the idea of, if say my keyboard wore out (full keyboard please?) that I could just like unsnap it and snap in a new keyboard, versus the labor-intesive process required on a conventional phone. If I had a choice of a conventional smartphone, and one that is DYI like this, I'd get the DYI one.
- Steam/smoke generator for the steampunk crowd
- Taser module (just dont activate the app by mistake when you try to make a call, or put it in your pocket)
- Laser pointer
- Charging socket for bluetooth headset
- Hinges with stretchy cables for connections
The list goes on....
Now i can take trolling of co-workers even further:
Someone whines about low battery life on an iFruit or sealed android, i can pop the back off mine and swap a battery with ease. Someone bitching about lack of storage on their hard wired flash, pop the back cover point to the micro sd and go "can't you just swap that bit out for a bigger one"
Biting the hand that feeds IT © 1998–2021