Slashdot Mirror


postmarketOS Pursues A Linux-Based, LTS OS For Android Phones (liliputing.com)

An anonymous reader quotes Liliputing: Buy an iPhone and you might get 4-5 years of official software updates. Android phones typically get 1-3 years of updates... if they get any updates at all. But there are ways to breathe new life into some older Android phones. If you can unlock the bootloader, you may be able to install a custom ROM like LineageOS and get unofficial software updates for a few more years. The folks behind postmarketOS want to go even further: they're developing a Linux-based alternative to Android with the goal of providing up to 10 years of support for old smartphones...

Right now postmarketOS is a touch-friendly operating system based on Alpine Linux that runs on a handful of devices including the Samsung Galaxy Nexus, Google Nexus 4, 5, and 7 (2012), and several other Samsung, HTC, LG, Motorola, and Sony smartphones. There are also ports for some non-Android phones such as the Nokia N900 and work-in-progress builds for the BlackBerry Bolt Touch 9900 and Jolla Phone. Note that when I say the operating system runs on those devices, I basically mean it boots. Some phones only have network access via a USB cable, for instance. None of the devices can actually be used to make phone calls. But here's the cool thing: the developers are hoping to create a single kernel that works with all supported devices, which means that postmarketOS would work a lot like a desktop operating system, allowing you to install the same OS on any smartphone with the proper hardware.

One postmarketOS developer complains that Android's architecture "is based on forking (one might as well say copy-pasting) the entire code-base for each and every device and Android version. And then working on that independent, basically instantly incompatible version. Especially adding device-specific drivers plays an important role... Here is the solution: Bend an existing Linux distribution to run on smartphones. Apply all necessary changes as small patches and upstream them, where it makes sense."

111 comments

  1. Uh, what? by Anonymous Coward · · Score: 0

    Patches get applied to the upstream Android distribution when submitted by manufacturers. What makes this approach any different? Do they suddenly think they can get manufacturers to play ball by saying it's Linux for smartphones (isn't that what Android is anyway?).

    1. Re:Uh, what? by Anonymous Coward · · Score: 0

      Nobody was talking about manufacturers before you came here.

      And Android, aside of using Linux as a kernel, is hardly similar to anything known from desktop.

    2. Re: Uh, what? by Anonymous Coward · · Score: 0

      Ffs, this should just be the policy for all consumer electronics (CE) licenses. Anything less than 10 years support is just disgustingly wasteful. The difference is nothing requires manufacturers to release compatible updates with their slightly different hardware.

    3. Re: Uh, what? by Anonymous Coward · · Score: 0

      Ffs, this should just be the policy for all consumer electronics (CE) licenses. Anything less than 10 years support is just disgustingly wasteful.

      I tried to tell the auto-makers something similar. Anything less than 50 years support is just disgusting and wasteful!

    4. Re: Uh, what? by Anonymous Coward · · Score: 0

      Auto makers are required to provide enough parts for 20 years with each car they release.

    5. Re:Uh, what? by Anonymous Coward · · Score: 0

      The difference is that the Android vendors are greedy, and try to lock in customers to their own GUI, store middleware, shovelware, spyware etc. Because all smartphones are proprietary hardware platforms, every device needs it's own custom drivers, etc.

      Compare that with the game console, exact same issue, once the hardware is obsolete, you can't even play old games without purchasing it again on another platform , if it ever happens at all.

      The PC platform is closing slowly, At one point in time you used to be able to replace socketed RAM chips, ROM chips, CPU's, and had a standard bus for all of the hardware to communicate with. Today you're lucky if RAM is socketed, let alone the CPU. Intel keeps producing CPU's and South/Northbridge chipsets that may as well be integrated into the CPU since you keep having to replace the motherboard with every CPU and RAM change anyway.

      In another decade the desktop PC will not exist, it will be looked down upon much in the same way we look down upon a CRT screen. Only rich gamers and data centers will have PC systems, everyone else will get away with a tablet computer or a smart phone.

      So ultimately, as much as I love the efficiency of the iPhone, and loathe the shitty Android fragmentation ecosystem, I think both of these will eventually go extinct and be replaced with a standardized secure (as in, all devices will receive updates forever) platform, but it won't be Linux. Linux is simply egregiously poorly designed to be used as a smart phone, because Linux philosophy says "everything goes into userland, in software", where as a smartphone needs to take advantage of all hardware acceleration features in everything from the LTE modem and WiFi, to the Video and audio codecs and UI acceleration.

      There needs to be a built from the ground up Mobile OS that can be *nix compatible, but it needs to take a dramatically different attitude and prioritize battery life and security over the current failed state of Android.

    6. Re:Uh, what? by viperidaenz · · Score: 1

      Someone must have forgotten that every single phone has a custom kernel. Most phones are still no 3.x kernels with no hope of mainline support.

      Added to the issue of old SoC's with no mainline support is every phone has a different set of devices attached to it, from touch controllers, to accelerometers, gyroscopes, audio codecs, cell radios, wifi/bt chips... even the buttons aren't going to be on any sort of standardised port, they're on random gpio's.

      At least if it was Android based, they could use the kernel, drivers and BSP developed by the manufacturer.

      Without manufacturer support, this is going to support only a handful of phones and will be forgotten like the dozes of other projects before it.

    7. Re:Uh, what? by viperidaenz · · Score: 1

      Intel keeps producing CPU's and South/Northbridge chipsets that may as well be integrated into the CPU since you keep having to replace the motherboard with every CPU and RAM change anyway.

      I know, right! They should have stuck to DDR2 and AGP. They should have never integrated the memory controller and kept the front side bus.
      They shouldn't keep upgrading the bandwidth from the CPU to the rest of the system.
      All because you want to buy less stuff from them.

    8. Re:Uh, what? by Zero__Kelvin · · Score: 1

      My phone, hardly an high end phone, has a 3.x kernel. I just checked an old retired phone from a different manufacturer I had laying around; also runs a 3.x kernel. I'm going to call bullshit on your claim.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    9. Re:Uh, what? by viperidaenz · · Score: 1

      That was a typo. It should have read "Most phones are still on 3.x kernels"
      The word "no" doesn't make sense.

      My Moto X 2014 still runs a 3.4.42 kernel. 3.4 went EOL in April. Motorola/Lenovo hasn't sent out a security patch since August 2016

    10. Re:Uh, what? by Zero__Kelvin · · Score: 1

      I thought it was supposed to be "not", as in there is not anything wrong with using 3.x kernels :^)

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    11. Re:Uh, what? by Anonymous Coward · · Score: 0

      Strictly speaking, they can maintain an EOL kernel and backport some fixes in a similar vein to what is done with RHEL.
      Although we'll agree that isn't happening there.

    12. Re:Uh, what? by Anonymous Coward · · Score: 0

      In another decade the desktop PC will not exist, it will be looked down upon much in the same way we look down upon a CRT screen. Only rich gamers and data centers will have PC systems, everyone else will get away with a tablet computer or a smart phone.

      But maybe that attitude of looking down on, ridiculing and loathing old grandpa stuff will go out of style as well, relatively. If TV and TV advertising lose their clout on entire societies and if society devolves further, will there be anyone left to tell us to deride and loathe crappy decade old stuff?

      In a decade, smartphones will be mundane stuff that "old people" have had before people were born, just like my grandma already had a dishwasher when I was a toddler.

      Also when patents on x86-64, SSE2, SSE3, NX bit etc. expire we might see PC compatible phones anyway. I'm not sure if that's likely but it's possible. Or they might become mostly compatible (UEFI, etc.) instead of the current situation which looks like CP/M : every hardware is incompatible but runs the same applications on top of a same OS customized for every incompatible hardware.

  2. Sounds like replicant.us by aglider · · Score: 1

    Another almost dead project!

    --
    Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
    1. Re:Sounds like replicant.us by Anonymous Coward · · Score: 0

      Mark Shuttleworth also had a half hearted go at it with Ubuntu.

    2. Re:Sounds like replicant.us by jofas · · Score: 1

      An artificially well-funded go at it, too. I tried ubuntu for phones and it ran well. It just has zero apps.

  3. Once more, in Engrish by Anonymous Coward · · Score: 0

    preeze

  4. Pixel by Anonymous Coward · · Score: 0

    Buy Pixel from google and you get updates also for at least 5 years. People have choice and if they select other manufacturers they have to live with what others provide. One of the reason i dont buy Samsung is their UI and no updates.

    1. Re: Pixel by Anonymous Coward · · Score: 0

      Really? Nexus isn't good for five years, where does Google guarantee five for Pixel? If it's in writing, I'll buy.

    2. Re:Pixel by Anonymous Coward · · Score: 0

      Hogwash. Pixels will only receive version updates through Oct 2018, and security updates through Oct 2019

      https://support.google.com/nexus/answer/4457705?hl=en"

    3. Re: Pixel by Thundercat007 · · Score: 2

      Agreed. My work phone is Samsung, still original 4.4.1 never received an update EVER. Still vulnerable to StageFright. Thanks for the update you promised Samsuck. Personal phone is Nexus 5x. Update monthly.

    4. Re: Pixel by Anonymous Coward · · Score: 0

      If you buy the right phones... You get updates.. My ancient Samsung galaxy note 4 still enjoy updates and have for a While been running an official Samsung android 6.0.1.. Latest patch was 1st of juli 2017

      My BlackBerry priv which is also old, runs BlackBerry android 6.0.1 and latest patch was 7th of juli 2017

  5. Are we ready for LTS phones? by jellomizer · · Score: 4, Interesting

    The phone market today seems akin to the PC Market back in the early 90's where they are just starting to settle down on what people want and what can be made, but are we there yet?

    early 1980 PC's were made with a bunch of processors and OS's they were some systems, that were compatible with each other, but they were considered ripoffs and often would fall into legal problems.

    Late 1990 Phones. Were made with a bunch of different systems and every new model was like a new phone.

    late 1980 PC's Battle lines are being drawn. Apple vs. IBM (What we now call a PC) Amiga holding on.

    Early 2000 Phones. Black Berry, Microsoft Mobile, Palm were fighting for the smart phone market, while Nokia, Samsung, LG, Motorola were fighting for the consumer market.

    Early 1990 The IBM PC won with its compatibles with Microsoft being the true victor as with all the Hardware in fighting, Microsoft was expanding the winning side, to be entrenched in the next battle.

    Late 2000 phones. the iPhone came out, and Android was under serious development. Apple and Google have been playing behind the scenes of the smart phone war realizing the smaller Consumer Models were not going to make it.

    Late 1990 The PC were no longer connected to IBM and all the IBM Compatibles were fighting for the better selling PC. Microsoft really holding onto the market share

    Early 2010 Phones, Apple is the dominate player and Google putting a good push on Android, However the phone makers are trying to make their phones better selling then each other.

    Early 2000 PC's Are more or less getting boring to the market Apple had a resurgence for this decade, due to the Halo effect of its iPod line and Microsoft not doing much with XP and delays on the new OS. But in terms of PC's we got use to using them more as a general tool, then something cool and a status symbol.

    Late 2010 Phones. Well this is where we are at now. Are we getting ready for a life of boring mobile devices where we don't really care about them any more, they are just a tool, where LTS makes a lot of sense because we won't be needed to update our phones any longer barring failure or damage.

    As I type this on my 6 year old Thinkpad, which still is fast and seems to do things just as good as the newer PC's barring high end video. Where before I was getting a new PC every 3 or 4 years to keep up with the times, now it just a tool, I could get a smaller lighter and faster PC.... But what for? It does what I want and I am not having any problems keeping the software up to date, or finding new software for it.

    Is the mobile market getting to this point or are their going to be some twist and turns that will make LTS OS a wast of time, because we will be using out of date and usless phones.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Are we ready for LTS phones? by Anonymous Coward · · Score: 0

      We're probably almost there now.

      Phones have reached the 'good enough' stage. They have enough storage space and are fast enough. At least the higher end phones.

      Over the next decade the lower end 'smart' phones will reach there as well. Where every phone will have 16GB, a fast processor, multitouch screen, and nimble UI.

      Then things will stagnate. Which is likely a good thing.

      I'm certainly not looking fondly back at the 90s when I had to buy a new computer every couple years just to keep up with the latest applications I was running.

    2. Re:Are we ready for LTS phones? by Anonymous Coward · · Score: 0

      The software isnt a problem. There are several phones out there that have hardware caple of running newer software and thanks to the communtiy do. Look how long the Galaxy Nexus has been supoorted? The Nexus 4 and 5 are still communtiy favorites and have receives updates well past what the manufacturer supplied.

      Hardware however is. Batteries dont hold up over time, and getting quality replacements is a problen number one. Problem number two is phones are becoming even more sealed and harder to replace components. Not to mention other issues like flash failures, and other board failures. Im "typing" this right now on a Nexus 5X that is known to have bootlooping issues due to a common hardware issue/failure.

      Dont get me wrong, I only buy devices I can unlock and that have official Lineage (in the past CM) support. However, expecting a portable device like a phone or tablet to last ten years probably is not realistic. Just playing devils advocate.

    3. Re:Are we ready for LTS phones? by DuckDodgers · · Score: 4, Interesting

      Is the mobile market getting to this point or are their going to be some twist and turns that will make LTS OS a wast of time, because we will be using out of date and useless phones.

      I would argue we reached the point of diminishing returns on hardware upgrades two or three years ago. A full HD screen, 2GB of RAM, and a three year old multi-core ARM processor runs Android 7.x just fine. Upgrades are nice, but most people that don't have a six figure income would prefer to have phones that keep working and keep getting security fixes for five years or longer.

      But the industry is trying to ride the planned obsolescence wagon as long as possible. In addition to the lack of software updates, we have a rarity of removable storage and greater rarity of removable batteries.

    4. Re:Are we ready for LTS phones? by JohnFen · · Score: 1

      I've been running an LTS for years!

      Well, sorta. My approach is to jailbreak the damned thing an put my own OS on it. Then I don't have to rely on a manufacturer to provide software updates (and don't have to tolerate the bastardized versions and crapware that the manufacturers provide). If I can't jailbreak or there's no decent OS for a phone, then I don't buy the phone.

      I've been doing this for years now, and it's been very, very good.

    5. Re:Are we ready for LTS phones? by JohnFen · · Score: 1

      However, expecting a portable device like a phone or tablet to last ten years probably is not realistic. Just playing devils advocate.

      I don't know about that. My current phone is 4 years old and shows no sign of impending doom. Of course, that's only 40% of ten years, so we'll see...

    6. Re:Are we ready for LTS phones? by Kjella · · Score: 1

      But the industry is trying to ride the planned obsolescence wagon as long as possible. In addition to the lack of software updates, we have a rarity of removable storage and greater rarity of removable batteries.

      And yet the worst offender there is best in class when it comes to OS support. I had the iPhone 4, it had 51 months of support (and they have in the past issued at least one security patch for EOL devices). It looks like 4 years is the main standard, you start with one iOS version and get four updates. Three if it's a late cycle product. From iOS 11 onwards it's all 64 bit / ARMv8 processors though, the iPhone 5s is already 4 years old next month and it's supported in iOS 11 that's still in beta so at least 5 years and possibly longer. These super short support times are pretty much an Android problem, not a smartphone problem.

      --
      Live today, because you never know what tomorrow brings
    7. Re:Are we ready for LTS phones? by DuckDodgers · · Score: 1

      I absolutely grant that iOS is better than Android in this respect. But even if it's a royal pain in the neck to get LineageOS or some other Android Open Source Project fork onto smart phones, at least it can be done. There's some interaction with open source. The iOS may provide longer product life, but you are locked solidly to Apple.

    8. Re: Are we ready for LTS phones? by Brockmire · · Score: 1

      Sounds like you're full of shit.

    9. Re:Are we ready for LTS phones? by Ol+Olsoc · · Score: 1

      I absolutely grant that iOS is better than Android in this respect. But even if it's a royal pain in the neck to get LineageOS or some other Android Open Source Project fork onto smart phones, at least it can be done. There's some interaction with open source. The iOS may provide longer product life, but you are locked solidly to Apple.

      I'm also "locked" to Apple since my iPhone integrates so well with my iMac and provides many features within that integration.

      But this "locked" word. I do not think it means what you think it means. My using an iPhone doesn't stop me from using and enjoying other Operating systems. I have Linux on a number of computers, a W10 laptop, and a couple Android tablets. Even a Chromebook. Full disclosure, I recently converted the Chromebook from ChromeOS to Gallium.

      I missed out on the Ford versus Chevy groupthink that smarter people are blessed with.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    10. Re:Are we ready for LTS phones? by DuckDodgers · · Score: 1

      Yes, locked. Can you take the movies you buy on iOS and legally transfer them to your Linux or W10 laptop? Can you buy any laptop you like and put MacOS on it? When your iPhone stops receiving security updates from Apple, do you have any choice other than "trash it" and "run without security fixes"? When Apple decides to change some core feature you don't like, can you fork the code - or pay someone else to fork the code, or take advantage of a fork someone else made - to go back to the old behavior? Can you port the applications you like to other hardware? Operating systems?

      Yes, locked. Now again, I'm not saying the situation with Android is better. While Android has the potential to be as open as a typical Linux distribution like Debian or Gentoo, in practice it's nearly as bad as Apple in most respects and worse in a few key respects - namely, security upgrades over the life of a product.

      Contrast all of that to running a free software environment like Debian, Gentoo, Arch, Fedora, Suse, etc... or even FreeBSD and its derivatives. Moving movies around is technically possible. Any hardware with drivers is supported and you have the freedom and legal right to create or help fund the create drivers for other hardware. Security fixes are indefinite, typically when hardware is dropped from Linux kernel support it's 15 years or more after it stopped being sold to consumers. That's freedom. No locks. It's what we should have everywhere.

    11. Re:Are we ready for LTS phones? by DuckDodgers · · Score: 1

      P.S. I try to avoid brand groupthink too. I guess we're both stupid.

      And I should have added, I am not condemning you for your choice. I respect it. I'm kicking around the idea of making the same choice with respect to mobile phones, since my Motorola Android device hasn't received some major security fixes since it was all of nine months old. I wonder if the FSF would send back my dues if they knew. :) I'm just saying that it's bad for all of us that the freedom-respecting choices are so rare and so poor.

    12. Re:Are we ready for LTS phones? by Ol+Olsoc · · Score: 1

      Yes, locked. Can you take the movies you buy on iOS and legally transfer them to your Linux or W10 laptop?

      I don't care.

      Can you buy any laptop you like and put MacOS on it?

      I most certainly do not under any circumstances have any desire to do such a thing. Dunno how old you are, but my Windows uber allies frinds used to com to me all ablush about how thy had such a myriad of choices for their computers, making it so superior to my Mac, with it's limited choice of boards and all. Now, they use the excues that they have so many choices, and that's one of the reasons they fail on updates. That the Mac's limited number of choices makes it easier to update.

      Short version - I want the computer to work, not to brag about shit.

      When your iPhone stops receiving security updates from Apple, do you have any choice other than "trash it" and "run without security fixes"?

      Such a thing has not ever happened, so I have no idea how to answer that question.

      When Apple decides to change some core feature you don't like, can you fork the code - or pay someone else to fork the code, or take advantage of a fork someone else made - to go back to the old behavior? Can you port the applications you like to other hardware? Operating systems?

      This is cute. I run Windows on my Mac flawlessly - in fact windows runs pretty good on it - better and more reliable than on my Windows only machines. I can run Linux on it as well - I've booted several live Distros. Don't really feel the need to install any of them because MacOS is already Unix.

      Everyone does that on their Windows machines, eh?

      And if you are talking soley about the phone - well, if you are using a phone as a computing device, I'll quit picking on you and hand out a little sympathy instead. I need my phone to work, and occasionally tether a real device to it. Otherwise meh.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    13. Re:Are we ready for LTS phones? by Anonymous Coward · · Score: 0

      When Apple decides to change some core feature you don't like, can you fork the code - or pay someone else to fork the code, or take advantage of a fork someone else made - to go back to the old behavior?

      Yes but this is the fantasy argument people always make, the reality is that it's cost-prohibitive to maintain a fork. Just look at systemd, the simple thing to do would have been to just fork and maintain the upstream distribution from the point just before systemd was introduced...but no there was (and still is) endless bitching about it and all the mainstream distributions put it in the "too hard" basket.

      Or take a look at Google Play Services, the proprietary blob that more and more Android features are being pushed into, the previously open source features aren't maintained and there is no open source implementation of Google Play Services, sure in theory you could develop one but in practise it just isn't going to happen so from a practical perspective you're in the same situation as iOS users...except they get far more updates.

      I still see no excuse for Google to offer such poor support for their Pixel phones.

    14. Re:Are we ready for LTS phones? by exomondo · · Score: 1

      How do you manage the driver kernel compatibility?

    15. Re:Are we ready for LTS phones? by JohnFen · · Score: 1

      I didn't write the OS, I'm using one of the many ROMs that are available. They manage this issue. Over the years, I've used a few different flavors on a couple of different phones and, except very early on, I have never had any issues with this.

  6. handhelds.org and the openembedded project by lkcl · · Score: 4, Interesting

    this is basically what a very small team behind handhelds.org did with the openembedded project. bitbake - the build system behind openembedded - became an extremely powerful tool as a result, empowering that small team and part-time contributors to quite literally manage the build for something mad like over a hundred different hand-held devices... including some smartphones.

    i don't exactly know the full history but i *think* that most of the team behind handhelds.org were employees of Compaq, and the employees weren't too happy that all of Compaq's PDAs ran Wince[ouch]. when Compaq lost interest in PDAs (even the ones with phone capability) thanks to the huge success of HTC's very first few phones like the Blueangel and Universal (a brilliant clamshell microlaptop in effect) it wasn't long before handhelds.org went down the tubes as well... which is a real serious pity. a *lot* of critical history - and source code - went down with it. i vaguely recall there being some sort of fight over the domain name... gaah this was all over 12 years ago now so it's all a bit fuzzy.

    anyway, various... idiots since.... have lambasted bitbake and the entire openembedded project as quotes being too complex quotes and have come up with quotes simpler quotes systems such as buildroot. not realising that the complexity behind openembedded and bitbake is *there for a good reason*. along similar lines you end up with even more idiotic things like forking an entire distribution on a per-manufacturer basis, just as the OA describes.

    the point is: it's a great idea for a small team to offer support for a wide range of devices, but they'll need appropriate infrastructure to do it. bitbake - and its ability to hybrid-combine python and shell-code with regular expression pattern-matching to manage toolchain downloading, toolchain compiling, patches, configuration, cross-compiling, cross-compiling using qemu to run the compilation and configuration "native" (yes, really! bitbake can run a native compiler via a qemu headless configuration in order to handle the proper cross-compiling of an entire OS!), parallel builds, cacheing and a bucket-load more, would be a good starting point for them. anything else - once you get into the details - quickly becomes a total nightmare, and that's what things like buildroot's developers totally fail to understand.

    1. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      anyway, various... idiots since.... have lambasted bitbake and the entire openembedded project as quotes being too complex quotes and have come up with quotes simpler quotes systems such as buildroot. not realising that the complexity behind openembedded and bitbake is *there for a good reason*. along similar lines you end up with even more idiotic things like forking an entire distribution on a per-manufacturer basis, just as the OA describes.

      There are many valid criticisms of the bitbake system if you step out of your bubble and stop dismissing anyone who criticises it as an idiot. It is clearly designed from the point of view of maintaining an OS distribution without too many custom changes from upstream. To do this efficiently, they encourage separating the distribution's own changes into a set of patch files that are applied on top of the upstream. But this does not scale well for device manufacturers, who generally have a lot of changes involved in supporting a particular hardware design, and quite frankly git is a much better tool for managing the patches than bitbake.

      Android doesn't need to be forked completely - aside from the kernel and HAL, they could easily use the standard AOSP. But they don't, because they want differentiation from the competition. The same will apply to any OS looking to replace it. The manufacturers are going to end up forking it, and all the supposed advantages will not survive beyond the first proof-of-concept device.

    2. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      The core cast of the handhelds.org project were actually people from the DEC Itsy project.

      And the iPaq linux thing wasn't actually a reverse-engineering project at all. The team actually convinced management to make some key linux-friendly decisions around the iPaq's early development, so they could use it to broaden out research around the Itsy.

      For example the sheath/shield design was influenced by linux people before the iPaq ever shipped.

    3. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      Bitbake. Please shoot me. That is all.

    4. Re:handhelds.org and the openembedded project by drinkypoo · · Score: 1

      I used to run Familiar Linux on an iPaq H2215 with a Sandisk 128MB CF+WiFi card and I loved it. It was really useful in the same way that an Android phone is now useful. I could ssh and so on, as you might expect. Having nonvolatile storage of some kind was mandatory because PocketPC of the day didn't come with any. My PDA had a 400 MHz PXA255, which was actually pretty darned peppy.

      However, OpenEmbedded has always been a nightmare. No matter how scrupulously I have followed instructions, I have never got anything of any complexity to actually build. It would take a long while to convince me that it was worth the time and effort that's been spent on it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:handhelds.org and the openembedded project by BlueLightning · · Score: 1

      To do this efficiently, they encourage separating the distribution's own changes into a set of patch files that are applied on top of the upstream. But this does not scale well for device manufacturers, who generally have a lot of changes involved in supporting a particular hardware design, and quite frankly git is a much better tool for managing the patches than bitbake.

      There's nothing that prevents you from pointing to a git repo in a bitbake recipe, in fact if it's more than a few patches, I would naturally encourage it - and it's pretty much assumed for kernel recipes.

    6. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      Wow, that's a well-considered in-depth review there.

    7. Re:handhelds.org and the openembedded project by BlueLightning · · Score: 1

      However, OpenEmbedded has always been a nightmare. No matter how scrupulously I have followed instructions, I have never got anything of any complexity to actually build. It would take a long while to convince me that it was worth the time and effort that's been spent on it.

      I'm sorry you've had that experience, but I can say that whilst we do indeed have a complex system, many, many other users by now have been able to use it successfully, from new users to small consultancies right up to large corporations. I'll also say that if the last time you tried it was more than a few years ago you were probably using something quite different from what we deliver today - it has certainly improved leaps and bounds since the handhelds.org days.

    8. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      Android is currently a rather monolithic system with custom build infrastructure and a bunch of Android-specific forks or re-implementations of things that are often present on an embedded linux system.

      I've often wondered whether it'd be possible to unpick the separate parts of Android and create a more "linux-distribution-like" architecture from them, so that rather than building the whole thing together it would be built from a number of smaller packages that compose together, as we see with Debian and RedHat.

      Certainly not trivial, but taking the "top part" of Android and making it run on a more generalized "bottom half" would have the benefit of having access to the existing Android app ecosystem, which has a lot more mobile-oriented apps available than the open source Linux world that tends to focus more on the desktop.

    9. Re: handhelds.org and the openembedded project by Brockmire · · Score: 1

      A colleague and I recently had to get into bitbake stuff to build Yocto, and we both hate it. So it doesn't surprise me that a guy who spells "quotes" instead of just using them really likes bitbake.

    10. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      Likewise I am sorry that you are a njgger. I'll also say that if the last time you realized you were a njgger was back during the tribal-Africa days you were probably experiencing a pre-slavery condition something quite different from what is delivered today - your lot has certainly improved by leaps and bounds because of the inventiveness of the white man's civilization during which the same white man has become a second-class citizen.

    11. Re: handhelds.org and the openembedded project by BlueLightning · · Score: 1

      What made you hate it specifically?

    12. Re:handhelds.org and the openembedded project by Anonymous Coward · · Score: 0

      So depressing you exist.

  7. Re:I have a better idea: by Anonymous Coward · · Score: 0

    Whoever downvoted the parent is clearly not on the side of George Soros, who wants to see the USA crumble into pieces and fall apart so he can make a profit. As a white nationalist, I support George Soros, who worked with Nazis, and stole gold from Jews to build his empire. I think it is wonderful when Jews become powerful enough to manipulate world markets and the media, as George Soros does.

  8. Re:I have a better idea: by Anonymous Coward · · Score: 0

    Is it weird when a post disappears from /., and then reappears when George Soros' name appears?

  9. I really like the idea! by Anonymous Coward · · Score: 0

    There is a lot of work ahead but I think the computing world needs this.

  10. Would the company last that long? by damaki · · Score: 1

    So, in a nutshell, I should trust blindly a small company/organization to provide me with free support for 10 years, no string attached? Man, few open source communities can do such crazy support without any kind of funding.
    And do not tell me about Debian, Slackware, Arch, LineageOS and so. Either they got clear ties to well defined corporate funding or they get upstream patches from open source software funded by companies.
    Get real. Unless there is a real paid subscription, a programmed hardware obsolescence, a shady telemetrics-heavy framework, an appstore cash cow, or clearly defined sponsors, I will not ever touch this thing.

    --
    Stupidity is the root of all evil.
    1. Re:Would the company last that long? by ChunderDownunder · · Score: 2

      What company? It's one guy with a donate page, which might pay for the cost of hosting.

      The rest is community-driven, where contributors are encouraged to port the base system to their device.

    2. Re:Would the company last that long? by JohnFen · · Score: 1

      So, in a nutshell, I should trust blindly a small company/organization to provide me with free support for 10 years, no string attached?

      Why would you blindly trust any organization to provide you with support (free or otherwise) for 10 years?

    3. Re:Would the company last that long? by Anonymous Coward · · Score: 0

      Why would you blindly trust any organization to provide you with support (free or otherwise) for 10 years?

      yeah linux has had free user support from the internet and user groups since 1994, what's your damage? maybe poor math skills?

    4. Re:Would the company last that long? by damaki · · Score: 1

      Isn't it the sale pitch of the said phone? I mean, if the support is not provided because the company or the company crashes, there is no point in buying this phone.

      --
      Stupidity is the root of all evil.
    5. Re:Would the company last that long? by damaki · · Score: 1

      Linux is quite the exception and definitely not the rule. And it has been corporate-funded for ages which is not the case here.

      --
      Stupidity is the root of all evil.
    6. Re:Would the company last that long? by JohnFen · · Score: 1

      I think you missed the word "blindly" in there. Trusting organizations that have a lengthy track history is not blind trust.

    7. Re:Would the company last that long? by Anonymous Coward · · Score: 0

      which is not the case here.

      linux survived for years with no corporate funding, wtf are you talking about?

    8. Re:Would the company last that long? by Anonymous Coward · · Score: 0

      I think you missed the word "blindly" in there. Trusting organizations that have a lengthy track history is not blind trust.

      Many people trusted a brand-new startup, RedHat, to support linux for them, even in mission-critical applications.

  11. Sauce? by Anonymous Coward · · Score: 0

    How does one make an LTS distro based on closed source drivers? Does the support only apply to security patches?

  12. Re-inventing the wheel, again and again and ... by Anonymous Coward · · Score: 0

    Most all mobile apps are just dumbed down re-inventions of the good 'ol regular computer programs.. dumbed down but also 10x more bloated..

    Personally I think they telecom industry made deals with all the big computer/phone manufacturers NOT to build phone size x86, Windows/Linux compatible computers.. And they were all for it, to create their own walled garden(enslaved) ecosystems. OQO. Flipstart, Sony UX and many others were 'right on the door' but they all seemed to give up when Android and Iphones came out!?!?!

    I think if there were a fully functional phone sized x86 PC (pinch zoom, WinXP-7 UI) people might not necessarily even use 'voice services', wifi and or VOip tech would be most common.

    Their are plenty of Intel Compute sticks /knockoffs, and the modern x86 chips are just as, if not better power management than arm... So I know they can be made to the Droid3 form factor.. but no-one is doing it? I'd pay 2x the price of an iphone for one if some #$%#$ would make one properly.
    x86, runs legacy x86 OS's/software, slideout kb. 2 micro-usb(one for power), MicroSD, hdmi,removable battery, yada yad.

    Seriously, both Iphone and Android are #$%$# ing terrible vs regular old Windows/Linux desktop apps.. Some say traditional desktop is not usable on a phone, I've tried it through VNC, works great.. The problem is the industry is keeping these off the market for some reason.(keep programmers busy? Rewriting the same old thing I presume).

    https://www.intel.com/content/...

    1. Re:Re-inventing the wheel, again and again and ... by MightyMartian · · Score: 1

      What are you talking about? Traditional Windows software work horribly on a touch interface.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    2. Re:Re-inventing the wheel, again and again and ... by DuckDodgers · · Score: 1, Insightful

      Android and iOS mobile apps have three changes over desktop.

      1. Designed for a touch interface.
      2. Designed to auto-save and switch to lower power or background off mode as directed by the OS and then transparently resume when returned to the foreground. I don't know how well iOS uses that feature for its apps. Earlier versions of Androids were pretty awful at it, and programs like "Advanced Task Killer" were needed to keep the phone from grinding to a crawl. Android 5.x and newer uses it effectively, you can have a 2GB device and switch between forty apps rapidly without manually closing any of them, and the phone keeps right on going at full speed because the OS pauses and closes things in the background. Similar APIs could be written for Linux and Windows, but nobody has (or they have but they're ignored by 98% of Windows and Linux application developers).
      3. Designed so that untrusted apps can be installed with restricted permissions. This kind of thing has always been possible on Windows and especially on Linux (or other Unix flavors) but sandboxes like AppImage, Snappy, and Flatpak didn't have the same focus when iOS and Android launched as they do today.

      So you're understating the value iOS and Android bring to mobile and overstating how easy it would be to do similar things on traditional Linux or Windows.

      I'm not defending the walled gardens, the locked bootloaders, or the proprietary drivers and firmware required for everything from the GPS to the cell modems to the wifi chips. Those are all anti-freedom, anti-privacy, anti-consumer. But the idea of a popular smartphone operating system running plain Linux or Windows 7 is even more of an impossible dream than Replicant.us, WebOS, Meego, etc...

    3. Re:Re-inventing the wheel, again and again and ... by Wrath0fb0b · · Score: 1

      or the proprietary drivers and firmware required for everything from the GPS to the cell modems to the wifi chips.

      First, how else do you propose to deliver functionality from those peripherals? A company dedicated to making low-power high-throughput WiFi chips is already going to have trouble paying its engineers and keeping up with the process node changes and technology/standards upgrades in a low-margin business. Releasing the firmware code would reveal quite a bit of the technology and method used, both software and hardware, most of which would be instantly commandeered by cheap Asian knockoffs. If you believe that embedded engineers should be paid and that R&D should go into new standards and improvements, then you need to articulate a structure that would allow that to happen.

      Second, do you think that Linux (or even BSD) let alone Windows is any different? We have barely-functional[1] open source drivers for GPUs, lets alone the firmware embedded on the chip. And likewise the firmware running on all the other peripherals (hard drives, keyboards, trackpads, WiFi adapters, battery chargers) is all bespoke and proprietary.

    4. Re:Re-inventing the wheel, again and again and ... by drinkypoo · · Score: 1

      What are you talking about? Traditional Windows software work horribly on a touch interface.

      It depends on how traditional it is. Some of the really old stuff was designed for small screen sizes and didn't make much use of the right button, if any.

      On the other hand, the start menu was garbage for PDAs. Microsoft actually had the UI working better in the earlier versions of WinCE.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Re-inventing the wheel, again and again and ... by DuckDodgers · · Score: 1

      Oh, on top of the reasons you stated there's one more: a lot of these wireless chips, GPS, etc... license components or software from other vendors, and the manufacturer may not have the right to release their code as open. This is one of the objections I think AMD raised when they were asked to make the code for their Platform Security Processor open source.

      Everything is locked because the current market makes that the profitable way to go. We've got to figure out how to put the incentive towards opening everything. I realize I'm being idealistic and I don't have a concrete path forward. But consider that, for example, if you get a device driver expected into the mainline Linux kernel then you don't have to backport security fixes to older kernels. You can just use the latest kernel to supply customers with the fix. So that would be a great motivator for companies to open things - but consumers just take for granted that newer security fixes flat out aren't coming.

    6. Re:Re-inventing the wheel, again and again and ... by JohnFen · · Score: 1

      On the other hand, the start menu was garbage for PDAs.

      I agree, but I find it interesting that the resurgence of touch interfaces has brought the Start Menu back in a modified form. Now we call it the "hamburger menu".

  13. Re:I have a better idea: by Anonymous Coward · · Score: 0

    make phone calls? text messages?

    what are you? some kind of caveman who thawed out recently?

  14. LineageOS by Anonymous Coward · · Score: 0

    This already exists with the former founder of Cyanogen OS in the form of LineageOS. [https://lineageos.org/about/]

    The list of supported devices is here and it is pretty long. [https://wiki.lineageos.org/devices/]

    I have an original OnePlusOne and thanks to LineageOS I am currently sitting on Android 7.1.2. with a patchset from 8/14/2017. Monday, I'll have a new update.

    If this extended(aka super-one year) support is important to you please:
    (1) Use this OS
    (2) Report bugs in a useful way.
    (3) Contribute in some small financial way to the project.

    1. Re:LineageOS by DuckDodgers · · Score: 3, Interesting

      As far as I understand it, LineageOS has individual images for each hardware skew. This PostmarketOS project has the idealistic but possibly impractical goal of having one core universal package and then one unique package per hardware skew.

      So in terms of architecture, PostmarketOS would be an improvement. But it's not clear to me that it could ever be done.

    2. Re:LineageOS by Anonymous Coward · · Score: 0

      Except for the fact that more and more things are starting to use SafetyNet making it hard to actually use your smartphone the way most people do.

  15. Re:I have a better idea: by umghhh · · Score: 1

    You managed number of things. To write a thoughtful few sentences on the subject, at least they can be qualified as interesting if one does not subscribe to the ideas presented. Then you asked for downvote in the way as sure as hell. It worked on both counts. You also made me laugh which on this afternoon was not an easy task. I thank you for that. On the second thought I should not have laughed either way. But I still did. I hate (watch out google!!!) having to cry. I much more prefer to laugh.

  16. None of the devices can amake phone calls. by Anonymous Coward · · Score: 0

    None of the devices can actually be used to make phone calls.

    Sounds like a real key selling point, since we are talking about, well, phones here.

    1. Re: None of the devices can amake phone calls. by JohnFen · · Score: 1

      While I wouldn't use a phone that couldn't, you know, make phone calls it's also true that I only average about a phone call per week despite using my phone heavily (for non-social media communications) throughout the day.

      I could see some people being OK with it not being a phone.

  17. Cool by Anonymous Coward · · Score: 0

    Sounds cool, let's see if this becomes a reality and i'm just a lurker in this project.

  18. Not everyone is on board with disposable phones by Noishkel · · Score: 4, Interesting

    One thing that a tech people don't realize is that not everyone wants the latest phone every year to begin with. A large portion of the market will never used ANY of the advanced features that Google tries to add with every generation of phone. I do repair and salvage of these various devices, and one of the greats complains I hear is that NO ONE want's these new features that Google keeps pushing with each version of their hardware. None of them give a damn to integrate ANYTHING with their google accounts and mostly just want something that'll play video. And none of them I speak to EVER buy anything on the Play store.

    Hell, right now I'm sitting on a 50 pound box of older phones from the past 5 years. I don't do repair of these things a primary job, but even then I've got such a back log of spares that I'm mostly just chucking a good half of what I get because I've got too many. Even the place in town that does this for a business has the same problem.

    1. Re:Not everyone is on board with disposable phones by JohnFen · · Score: 3, Insightful

      One thing that a tech people don't realize is that not everyone wants the latest phone every year to begin with.

      I'm a tech person and I don't want the latest phone every year. What I want is a phone that meets my needs. I have that now, and will keep using it for however many years that it continues to meet my needs. A lot, hopefully.

      Changing phones is disruptive. The less I have to do it, the better.

    2. Re:Not everyone is on board with disposable phones by ChatHuant · · Score: 1

      one of the greats complains I hear is that NO ONE want's these new features that Google keeps pushing with each version of their hardware

      It doesn't help that most of the new features seem to be there for the benefit of Google and other ad-slingers, not the customer; they require Google accounts, location reporting, trackers running all the time and so on. I may be more privacy aware than other people, but I have pretty much stopped adding more apps (pretty much all require too many permissions), and am only using the phone for basic tasks, like voice calls, contact list, calendaring and light web browsing (contacts and calendar items get synchronized via USB, not Google, and browsing is done via Firefox with ublock Origin and Ghostery). My next phone will either be a basic feature phone or maybe an iPhone.

    3. Re:Not everyone is on board with disposable phones by JohnFen · · Score: 1

      My next phone will either be a basic feature phone or maybe an iPhone.

      Just as a point of interest -- it's totally doable to have an Android phone that does not contain or use any Google apps whatsoever, let alone phone home to the Google mothership.

  19. Re:I have a better idea: by JohnFen · · Score: 1

    Design a linux based smartphone OS that does exactly TWO things: make phone calls, and send text messages.

    If it only does those two things, it doesn't have to be a smartphone. You can pick up a feature phone for $20 right now that will do that.

  20. confusing and boring by pD-brane · · Score: 1

    Android is Linux. They want to put GNU/Linux on the smart phone. This is not new either. I find it quite uninteresting.

  21. Well there you go! by Noishkel · · Score: 2

    Yeah that's one thing I didn't think to mention, but that is a valid point and a real problem for the mobile industry. Constantly having to relearn the ins and outs of an OS is frustrating as HELL and puts off a lot of the consumer market.

    To go along with that line of thought; as I said I don't do phone repair as a primary job. Just as a second job since i have a lot of skill in electronics repair. No, my primary job up until very recently was a local route Truck driver. And there is nothing more INFURIATING than relying on a phone for you job only to have it brick itself from a screwed up forced update. Which is why I 100% abandoned the use my ANY smart phone for any job specific task. It is NOT worth the hassle.

  22. Pernicious spymachines by jabberw0k · · Score: 0

    Great. A telephone that cannot be used to make telephone calls. With a five-inch screen that makes the Kaypro I look generous. No real keyboard, only a touchscreen emulation of a keyboard with microscopic key-targets so you can type perhaps as fast as five words a minute before realizing everything you entered was silently changed to be nothing like what you intended to write. Of what possible use is such a device?

    1. Re:Pernicious spymachines by JohnFen · · Score: 1

      No use to you, obviously. But personally, I find it very useful to have a powerful computer with me everywhere I go.

  23. Standard Linux distro by Anonymous Coward · · Score: 0

    I would love to be able to put normal distro like Fedora on my phone and tablet. As long I can make phone calls + message, everything else is already available. It has web browsers, mapping programs, music player, etc.

    So why can't I run Fedora on my devices? Why does it have to be Android?

  24. Firefox OS by brianerst · · Score: 3, Interesting

    Why not just fork and develop Firefox OS? It actually works, is based on Linux, CSS and HTML5 and has actually been deployed by a handful of phone manufacturers, primarily in India. I don't even think it's truly dead, as a couple of small Indian firms appear to still be developing it.

    Sure, it was a waste of time for Mozilla but no need to reinvent the wheel.

    1. Re:Firefox OS by r0kk3rz · · Score: 1

      Why not just fork and develop Firefox OS? It actually works, is based on Linux, CSS and HTML5 and has actually been deployed by a handful of phone manufacturers, primarily in India. I don't even think it's truly dead, as a couple of small Indian firms appear to still be developing it.

      Sure, it was a waste of time for Mozilla but no need to reinvent the wheel.

      Why not just do something completely different? Well FXOS is based upon Android and these guys don't seem want anything to do with Android. I wish them the best of luck but getting decent mainline hardware support out of modern phones is a serious undertaking, there's a reason why all recent efforts (firefox os, ubuntu touch, sailifsh os) use various hacks to re-use the android based drivers.

    2. Re:Firefox OS by Anonymous Coward · · Score: 0

      From what I read of TFA these guys use Android kernels it seems. Perhaps none of the user land. But I think they reuse some drivers else I can't see how they would get something on the screen with touchscreen working.

  25. Re: I have a better idea: by Anonymous Coward · · Score: 0

    I want to be able to do three things:

    Phone calls, text messages, GPS, and Facebook

    I'll come in again...

  26. I will try it by drolli · · Score: 1

    my galaxy note 2 hardware is still quite ok (microphone problems, but using it as a phone never was a priority), but CM is non existent and samsung stopped to deliver update a long time ago.... I would be a bigger fan if they would have based it on debian, but ok...

    1. Re:I will try it by Anonymous Coward · · Score: 1

      LineageOS is the new CyanogenMod.
      Version 14.1 (Android Nougat Equivalent) is available for Galaxy S2.

      https://download.lineageos.org/i9100

    2. Re:I will try it by Anonymous Coward · · Score: 0

      Error....
      Galaxy Note 2
      https://download.lineageos.org/t0lte

  27. Re: Re-inventing the wheel, again and again and .. by Anonymous Coward · · Score: 0

    My Amd Rx 480 runs faster and more stable with the open drivers tjan what it does with the closed ones on Windows.

  28. Device drivers? by Namarrgon · · Score: 1

    There's good reasons why it's easy to install Linux on 10yo PCs but Google can't update Android even on its own phones for more than a few years, and those are all down to device drivers. PCs have well-documented processors, standardised BIOS, common hardware interfaces, and nearly all the main hardware APIs are open and well-understood (notable exceptions include high-level 3D graphics acceleration chips). Anyone can write something that will boot and run on nearly any PC (or VM) in the last 25 years.

    That's not what the phone world looks like. Even without carrier complications, smartphones are built on a limited range of proprietary SoCs whose hardware interfaces are jealously guarded by their manufacturers, who supply specific binary driver blobs for each model under strict NDAs to companies that buy enough. Any OS HAL has to be tailored to those driver blobs, usually by the phone's manufacturer when they build the hardware. New SoC (new drivers), or new OS, and this has to be done again. If the SoC vendor exits the market (like TI did), you're out of luck. It's a huge job for organisations like Cyanogen/Lineage to blindly juggle existing closed drivers with continuing lower-level OS changes, papering over the growing gaps (especially if the HAL source isn't available) for each different device, and results are not always ideal.

    postmarketOS hasn't attempted to tackle most of these drivers yet, even for the few devices it boots on. FirefoxOS has the same issue, with support only for the few specific devices it was tailored to, and porting MeeGo, Maemo, Sailfish, Tizen, WebOS, Ubuntu Touch, or any Linux distro would have to be done in the dark for each and every different phone.

    Google's new Android O release (due today) hopes to alleviate this somewhat with Project Treble, a standardised driver interface layer that SoC vendors can interface to, regardless of model or vendor or (hopefully) AOSP updates. There's still carrier- and manufacturer-specific changes to worry about, but in theory new releases of vanilla Android could be installed on Treble-compliant platforms with minimal effort, and maybe even older devices could have Treble layers written for them, ensuring continued support for years to come.

    --
    Why would anyone engrave "Elbereth"?
    1. Re:Device drivers? by Anonymous Coward · · Score: 0

      Because of course adding yet another layer of code to things will solve all problems. /eyeroll

      Wake me up when someone finally does the obvious and necessary thing of getting the fucking manufacturers to open up and standardise the hardware interfaces.

  29. this is how i visualize my ideal smarthphone by Anonymous Coward · · Score: 0

    it comes without a system, i plug it into the fucking computer, load a fucking program with several distros to install, pick one and install the system and some basic apps from a fucking repository, ideally all apps would be no nonsense stuff made by some basement dweller mega nerd with really thick glasses, kinda like the ones in regular linux distros

    im not interested in the spy machines they sell today, they are garbage

  30. Openmoko by manu0601 · · Score: 1

    Perhaps it is time to re-read Why Openmoko failed

  31. Re:I have a better idea: by Anonymous Coward · · Score: 0

    Design a linux based smartphone OS that does exactly TWO things: make phone calls, and send text messages.

    That isn't a better idea at all, it is a much worse idea because nobody wants that.

  32. Re: Re-inventing the wheel, again and again and .. by Anonymous Coward · · Score: 0

    My guess would be that the surface phone will be just that... An x86/AMD64 based smartphone that runs full Blown Windows 10... But with default tablet mode when not in dock and default desktop mode when in dock... Hopefully still with the option of selecting tablet mode for dock and desktop for non dock if you should want to do that..

    That would make sense for ms and boost Their 'metro' apps

    I just Hope they wont make an arm based surface phone that would be stupid

    There have been x86/amd64 based phones with Windows before

    but the tech was powerhungry and they ran xp and win 7..

    Both were not optimal for a phone

  33. Without replaceable batteries by rickb928 · · Score: 1

    Smartphone OS support for 10 years is pointless.

    If battery life is measured in charge cycles, then a 1000-cycle battery can most optimistically last 3-4 years. In practice most have trouble getting past 30 months without being significantly degraded, and that downward spiral of battery life makes the last 3 months miserable. Snap-on external batteries or Qi chargers to give more and more convenient recharging opportunities don;t offer much of an enhanced experience. Battery life cycle duration is the real limiting factor, and the trend to non-removable batteries ensures the industry has a defined and predictable replacement cycle, hence a predictable replacement market.

    Profits. Enabling users to extend the life of their insanely expensive toys isn't as profitable as relying on Moore's Law to make the replacement to so so attractive.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:Without replaceable batteries by JohnFen · · Score: 1

      This is the primary reason why I refuse to buy any phone that doesn't have a replaceable battery.

  34. Nice by XSportSeeker · · Score: 1

    I hope all the best for them fully knowing it's an uphill battle...
    How many projects with similar promisses we've heard about in the past?

    I'd really love to use older smartphones as a Linux box of sorts, even if there are downsides to it... put it to good use instead of turning it into eWaste and all.

  35. Re: I have a better idea: by Anonymous Coward · · Score: 0

    This is why I was a believer in Firefox OS. They only needed to release a low end 5" phone with IPS display, now there are tons of these selling with Android 5 and 6 in 2017.
    There was a 5", 16:9 480p phone that got delayed and canceled which is a shame as everyone wanted a 5" phone already.

    I was like Chromebook but for phones and without Google applications.

  36. Re: Re-inventing the wheel, again and again and .. by Anonymous Coward · · Score: 0

    I don't know about Windows XP and 7 phones, are you sure these weren't "Mobile Internet Devices" instead? more like a tiny micro laptop with 3G.
    More like a descendant of Olivetti Quaderno or Toshiba Libretto than of a Nokia 9000.

    The real x86 phones ran Android.

    Yes they have kind of an ARM Surface Phone, it's the HP elite phone, whatever it's called. I suppose you that once updated to Snapdragon 835 you can use one to run Photoshop CS2 or a 20-year-old version of Autocad, etc.

    Intel exited the phone market and AMD is gonna use an architecture that scales from netbooks to servers, so.. unless an x86 vendor secretly works on a chip for phones, even VIA, there's simply no suitable hardware for an amd64 phone even though there's no technical reason it can't be done.