8 ms·
I'm probably going to turn in to that old guy with tin foil who can't play any games because nobody supports his choice of platform, but I really miss when comp
by CalRobert 13y ago
I'm probably going to turn in to that old guy with tin foil who can't play any games because nobody supports his choice of platform, but I really miss when computers were devices you could buy and then put your choice of OS on. Phones are pretty much just little ARM computers, why the hell don't I just install Ubuntu, Firefox OS, Android, WinPhone, Symbian, whatever? I could format a microSD card to boot from and go from there.
And while I'm complaining, phones (devices for communication, remember?) need proper keyboards.
OK. I'll crawl back into my cave now.
- StavrosK 13y agoWhy not? I installed Ubuntu the other day, it was trivial. Plus, there's a multitude of custom ROMs.
- CalRobert 13y agoYeah, but what you would call trivial might be insurmountable for lots of people. Cyanogenmod already has a lot of the privacy features missing in Android, but dicking around with clockworkmod recovery, etc. is pretty daunting.
- StavrosK 13y agoFair point.
- nileshtrivedi 13y agoCyanogenmod now provides a really easy installer that takes care of everything (including unlocking of the bootloader). I used it with my Nexus S last week without any hassles.
- tomkarlo 13y agoSwapping the OS on a desktop computer has never been particularly accessible to most people, either. What percentage of desktops ever get a different OS from what they came with? I'd guess less than 3% if you don't include upgrades from one version of Windows to another.
- thecodeore 13y agoBecause while the ARM processor is probably supported, most of the other sensors, camera, cell radios, etc have proprietary binary drivers that are not. Just read the problems Replicant, the true FOSS android, has had getting all components to work correctly.
- Nursie 13y agoOne of the issues with that is that devices on ARM systems are not as discoverable as a lot of other systems. You tend to need a kernel built for a particular processor variant, and it needs a device map of some sort for your specific device or it won't know how to find any of the stuff on the board and may just crash. Without this map you just can't boot. Graphics are also very non-open at the moment, so it can be very hard to install other operating systems in a useful way for that reason. In theory though, I agree entirely, that would be nice :)
- nileshtrivedi 13y agoLinux supports Device Tree mechanism which solves this issue. You would download a kernel for the correct processor and a .dts file that describes the phone's hardware.
- Nursie 13y agoHas this made it to mainline/release yet? I've been doing some ARM kernel support stuff for one of my devices, and DeviceTree isn't there even in 3.11.x (AFAICT) Previously you had a bit of boilerplate code that did much the same. Either way it doesn't actually solve the issue, because you still need the dts file, there's no hardware discovery. (ok that's a bit of a stretch, some of the busses and things like I2C are discoverable, but you need a map of GPIOs, UARTs etc etc)
- nileshtrivedi 13y agoHere are the LWN articles on Device Tree from June/July. Not sure how things have changed: https://lwn.net/Articles/560523/ https://lwn.net/Articles/560523/ https://lwn.net/Articles/561462/ https://lwn.net/Articles/561462/
- Nursie 13y agoI'm not sure how things have changed yet either, and I certainly think Device Tree is an important step forward from each and every board having its own (mostly identical) code in the kernel tree. But you do still need the dts, so while it makes device support easier, it doesn't solve the problem of discoverable hardware and you still need board specs etc, either from the original manufacturer or reverse engineered.
- ouaibe 13y agoBecause phones inherit from an old business model where they were subsidized by mobile network operators and thus manufactured and sold according to their needs, not to the users need. This meant you'd have many restrictions and the user was constrained to a tightly-controlled environment that forbode anything the operator deemed unnecessary (and could even contain malware/spyware-like pre-loaded software). That model gradually evolved into J2ME platforms (and the like), where developers (and sometime users) could make small customizations, until someone decided there was a huge market selling phones designed not for the operators but for their customers (i.e. Apple/Google). They still built the product partly following the same mindset/model and provided VM-centric phones that still are not designed to give you ring-0 access from the get go and maximize the operator's & manufacturer control on your device, hoping to gain revenues from gated developer communities, reselling applications that are mostly yet another graphical layer on top of code that already exists natively on regular computers since a long time ago. That model is gradually evolving (hopefully in the right direction) and operators are slowling realizing that they're not device vendors but merely ISPs, which means that the phones are to be sold to customers, centered around their needs and giving them the maximum control (letting them chose the OS and giving them ring0 access). You still need to get rid of the protected baseband cpu, the SIM, the TEE, the protected bootloaders etc. and eventually might have the device that you speak about.
- contingencies 13y agophones inherit from an old business model where they were subsidized by mobile network operators Only in the US.
- FigBug 13y agoI think not tying the OS to their hardware was a mistake by IBM. And while it may have let the PC win, what is the point of your platform winning if you get forced out of the business by the clones? There is no money in hardware, you need to control the OS.
- Tyrannosaurs 13y agoRe. proper keyboards - the market says otherwise. There have been plenty of Android phones with hard keyboards but they've not sold in sufficient quantities to make it attractive. If there was a market for it, people would be making them, if you disagree with that they what are you doing on here, your fortune awaits... Also worth seeing kids who've never used a physical keyboard to any great extent. I've seen them doing what must be close to 60 words a minute on a touch screen (tablet rather than phone but still). If you're used to it a touch screen keyboard isn't a massive limiting factor. EDIT: This is interesting: http://psychology.wichita.edu/surl/usabilitynews/122/ipadtyping.asp http://psychology.wichita.edu/surl/usabilitynews/122/ipadtyp... A study showing netbooks to have a typical typing speed of around 60WPM vs 40WPM for iPad, but interestingly it mentions that none of the participants had used an iPad. I'm guessing that someone with significant experience on a particular OS / soft keyboard with correction could close that gap pretty sharpish. EDIT2: http://thinkertry.com/2012/10/30/typing-speed-test-iphone-vs-ipad-vs-keyboard/ http://thinkertry.com/2012/10/30/typing-speed-test-iphone-vs... Someone testing iPhone, iPad and keyboard two years running: 2011: iPhone: 57 wpm, iPad: 60 wpm, Keyboard: 71 wpm 2012: iPhone: 51 wpm, iPad: 75 wpm, Keyboard: 82 wpm It seems that practice does indeed close the gap. Given that the total install base for touchscreen devices will exceed that for PCs in the next 12 months (probably next 6), that greater level of familiarity will shortly become standard.
- uchi 13y agoThere's actually something fairly interesting at play that should be mentioned: Typing with a physical keyboard is much more accurate than a touchscreen, but a touchscreen makes up this deficiency by a much simpler to use word completion feature. Error correction is also a breeze. Most of the words written in this post took advantage of those factors, and it took me about a minute to type everything up.
- Tyrannosaurs 13y agoTwo things: 1) Depends on the keyboard - the research I've posted showed that against a netbook keyboard, an iPad in landscape mode had greater accuracy. 2) Agree on the autocorrect features and it's something I've noticed this with touchscreen typing. It's taken me a while to get used to the auto-correct features. It used to be that they were basically a prompt that something was wrong that I'd retype mannually, now my instincts work with them. They also act as autocomplete when you're used to them - either fully or with edits (it'll often prompt with the right root word but with a different ending - say regretfully instead of regretful - in some cases it's quicker to accept it's suggestion and then delete than to continue typing, once you're used to it).
- pjc50 13y agoThe touch keyboard lacks feedback but folds to zero size, which is its great advantage. And people are in practice getting along just fine with them, which is why the hardware keyboards have fallen by the wayside. The main obstacle to boot-your-own-phone in the US is of course the carriers.
- tomrod 13y ago> The main obstacle to boot-your-own-phone in the US is of course the carriers. Surely if it were profitably one of them would break ranks, right? I mean, we have intelligent businesspeople in telecoms at least occasionally?
- nitrogen 13y agoBy this assumption, surely everything that can be invented already has, right?
- tomrod 13y agoWithin telecom pricing strategy? Yes, given current technology. One can go back in the lit to Bell Labs research in the 60s for all the pricing strategies. Jean Tirole fleshed most of it out with help by Jean Rochet. Source: Economist, network industries are my object of research
- pjc50 13y agoIt's very anti-profitable for them, because it removes their ability to suppress functionality of your phone in order to sell it back to you. First rule of phone company: why market when you can monopoly?
- 10098 13y ago> I really miss when computers were devices you could buy and then put your choice of OS on. uh, those are still around you know. You can even carry them in a backpack.