As this catches on, it only helps improve linux hardware (ARM) support, telephony applications for linux, and the like. As well as being able to have (or make for others) a truly remarkable user interface and apps. This is a mobile computer, running linux, running a desktop environment (not webkit, or Java VM, or closed source code) that only limits what you can make by your skill and imagination.
Yes it looks pretty mediocre now, but that's because its waiting on you to get involved.
I loved always having access to a physical keyboard and an actual root linux shell out of the box without any hacking. I loved that my n900 behaved more like a computer and less like "mobile" device.
Too bad Nokia decided to end support for the n900. Most of its developers and lots of its users abandoned ship, and now I only use it as a camera because the n900 is stuck in 2009, and the web in 2016 is so bloated and heavy that nothing- not even the web browser or the unupdated apps- are usable now.
Things like this is what makes me feel that the mobile market came to a screeching halt somewhere around 2007, and has barely been picking up speed since.
Also, look into the neo900 project and Pyra. Neo900 is trying to upgrade the n900, and Pyra is the successor to Pandora, which is a pocket computer in a semi-similar vein to the old nokias. Neither is finished, but they're worth a look.
The neo900 makes me sad, because it's basically my ideal phone, but the price is just too much for me. I know it's not their fault, the low production quantities will do that, but still. It's an updated n900, with a fully FOSS stack and an isolated baseband to boot... awesome.
Plasma Mobile and Tizen are my only hopes for getting a non-Android Open Source OS on my phone.
The other project was called Moblin. It was an Intel project.
It's a shame the N950 never got a proper release. The N9 got praised highly on release, but the N950 would've been the true successor to the N900.
Reading this made me so sad. This is exactly how I feel. Nothing will ever be good enough again. :(
As mentioned, it'd be a usable device on its own to this day. If newspaper sites hadn't become unusable without an adblocker, if I didn't need browser updates every nanosecond and if the latest memory-hogging web trend language wasn't, well, what it was. I'd still use it.
Now I own two mobile devices. A BlackBerry Passport. Great UI, physical keyboard, indestructible. Dead software ecosystem, horribly closed source, last of its kind and while there's a lot to love It's not hard to see why. Then there's a rooted HTC phone. Great choice of software (termux alone makes up for so much). Hate hate hate ssh'ing with a touchscreen. Typing generally. Terrible battery life. Seems like it'll die from one harsh drop.
If my social life would not force mobile messengers on me, I'd have gone back to 20€ dumbphones and text/voice only. Though I bet even those come with a horrible browser and the accompanying remotely exploitable holes now.
All in all? Wonderful project. I'm very much hoping for a third player in the mobile game.
I used it as my main phone when travelling for years and it worked everywhere I needed it to when other phones wouldn't. I'd use it for getting unwacoughted access to WiFi when I was in a tough spot. I'd manage my servers with it. I'd use it to emit music through the radio on car trips and such (why is this no longer a thing?). I could even push my own programs on it without having to make a sacrifice to the phone gods. I'd also kill for a keyboard like that again.
But no, instead you have to get a hobbyist device or get one of the many shiny slabs running (poorly) one of three (and I mean, really, two) ecosystems.
So many of us miss that phone.
Android is 100% native code since that version.
Even the changes in Android 7, although they use an intepreter written in Assembly, the code is JITed with profile information, both are cached and it gets ultimately fully compiled to native code when the device is charging.
Also in case you didn't notice, Apple is pushing for LLVM bitcode for their newer OS versions.
There is even a BOF on this weeek's LLVM meeting about how to make LLVM IR fully hardware neutral.
Just about every Android device I've used has been painful in some way or other and invariably I've ended up rooting it and installing a custom firmware, generally the most light-weight one I can find.
Unfortunately, despite these antics Android remains annoyingly prone to sluggishness, freezing, reboots and various other random problems.
Ultimately it seems that with Android you're either forced to use a stock ROM which imposes a heavy memory footprint due to all the "wonderful" tweaks Samsung/Sony/HTC/Xiaomi have made or drop down to a user-built AOSP-based variant that is inevitably plague by its own issues.
I'm horrified to think this kind of thing is the height of the mobile user experience.
But on my Galaxy S4 and my current Galaxy S5 (which is updated to 6.0.1 I think), things work quite well.
It's not perfect of course: I'm using the regular Samsung/Sprint ROM which is absolutely loaded with crapware. I disabled all the crapware, but it's still there wasting a lot of valuable space out of my 16GB. It could be a little faster at times, like with the camera. But freezing and reboots just aren't a problem the way there were on old Android versions that I've used.
I do plan on trying out CyanogenMod sometime when I have some free time. But for now, the carrier-pushed version seems to work decently well. I don't have any giant complaints.
I have seen pretty sluggish, full of memory leaks and dangling pointers, C code written at enterprise level, by developers that couldn't care 1s about code quality.
Your points are still relevant, don't get me wrong, but the system isn't running Java bytecode specifically.
Google just used the Java language and APIs. But never it's byte code or VM.
Nowadays, the next best thing is the Pyra, but that still has't been released.
By the way, have you seen the neo900 project? It sounds like you would be interested, although it is also incomplete.
The n900 is everything that I thought the g1 was going to be, but wasn't. In a way, it was my fault for blindly creating my own hype over a first generation product I knew nothing about. The g1 turned out to be my bad and disappointing foray into smart phones.
Also, yes I have heard of the neo900 project, but am sad that the project is so far from its goals. There will never be enough n900 users to meet a crowdfund. :(
Another interesting project which might fill my desire for a true mobile computer (if only I could afford it) is the Pyra, the more powerful successor to the Pandora. But at $~500-$~600, it may not be worth it, and it still hasn't actually released yet (although the company did make the Pandora, so they have a history of Getting Stuff Done).
If you're going on the cheap, you can always hack together a Raspberry Pi and a tiny screen, keyboard, and battery into something semi-workable, and use a phone for the rest.
You can get a GSM board from Adafruit fairly cheaply, which would give you 3G data and voice/SMS on a Pi. You'd have to do your own wiring, but if you're building something like this that wouldn't be a problem. Throw a Ting SIM in there (or your other favorite carrier) and you're good to go.
Basically a mobile phone version of Bunnie's Novena laptop, though not quite as open source (at least not until Broadcom finishes opening up the RPi's processor).
On top of that, over the years, the kickstand broke, the screen got scratched badly, my belt clip broke in multiple places, the SIM slot became really finicky, and even the plastic around the keyboard was starting to come out.
And a lot of the problem was performance: a 600 MHz OMAP3 was great in 2009, but by 2014 it was just too slow to handle modern websites, and the browser based on Firefox 3.5 (maybe 3.6?) couldn't even handle some newer websites. And to be honest, the RAM was low even for its time... only 256 MB, operated as a unionfs with the rootfs, plus some of the (very, very slow) eMMC was formatted as swap. Over time, most apps stopped working: I remember using Facebrick to access Facebook for a while, and it was nice, but eventually the author stopped updating it, and Facebook changed their API, so no more Facebrick. It got to the point where I'd only use the browser, terminal, camera, and dialer, because that's all that was useful.
About a year after getting my Nexus 5, I booted up my N900 to get some photos off it, and I found I had difficulty emailing them to myself because Gmail had changed their API and flagged my N900's connection attempts because they used the old API that was deprecated for security reasons. None of the emails went through, and when I got back to my desktop, Google took me to a page telling me it thought my account had been compromised.
My batteries are swelling. I suspect it's no longer safe really.
Universal battery chargers are a life saver if you have multiple types of batteries to charge.
I'll give you the keyboard though. Nothing beats a full keyboard.
How much extra power do we have to cram into the device just to achieve the same performance?
Back in the late 90s/early 2000s, you could just run Linux on your x86. Sometimes half your hardware didn't work, but as long as you could get Ethernet and display you were in pretty good shape usually. The thing is, you could install it. You could try it.
With ARM, everything is so specialized. Looking at the forum posts for this thing, half of the threads are about porting to devices.
The manufactures have no incentive to standardize the platform. They customize to a device and it's better for them if you just throw it out in two years when they drop support.
A limited number of hobby devices now use the device tree configuration, but the ARM platform is far from being as standard as Intel or Power.
If the Ubuntu Edge had been funded, I think we'd be in a difference space with at least a handful of devices that had some standardization (if only to accommodate Canonical). As it stands, ARM fragmentation is a huge problem for hackers/devs.
Also SOC manufacturer usually has the drivers reference code but he might not publish it.
Generally not. Linux kernel modules generally can't be loaded by kernels with different versions, as the ABI constantly changes. It can be hard to use them even with the same version, if it was compiled differently. This is why they're always pushing for the drivers to be open-sourced and submitted to the kernel project for inclusion, because maintaining them separately is a giant PITA.
Phone makers don't bother because they don't care: they're not going to maintain the drivers very long anyway.
ps: I was actually looking into FDroid to free myself a little from Android locks, wishing for a simple linux + ssh + any signed code I wish.
The polish it has is unbelievable.
The question is: how? The website doesn't make it very clear to developers (after a fairly quick skim on my part, at least) as to how they can help with the initiative. I have a Nexus 6p, and it seems like my device isn't supported, but how can I maybe help with porting to a new device?
It had most of the downsides of android (closed drivers, no updates after 6 months, buy a new device or get exploited, beholden to vendors, OEMs and telcos which invariably suck, central control over software distribution), and zero of the upsides (abysmal performance [even the dialer was a laggy mess], lack of software)
Except for the fact you might trust Mozilla more than google, it wasn't anymore meaningfully open than android, and suffered crippling drawbacks in comparison. Nobody except a few developers cared that you can write apps in html/js.
The leadership was caught in a innovators dilemma (Symbian was aging but had a massive install base, Maemo has future potential but could massacre their Symbian earnings in a transition), and the board in the end brought in a Trojan horse that made a deal with Microsoft.
Also, what you are currently seeing happening in desktop Linux land, wayland, systemd, etc etc etc, is because of lessons (X11 and sysvinit is crap) various devs "learned" while working on Maemo in some capacity or other.
yes they may not be the perfect fit in a power constrained mobile device (My N800 seemed to last me just as well as the Android devices i have around me right now though), but why the hell are we turning the whole DE stack into a mobile phone in response?!
And the lie keeps being repeated, it was the board that sold Nokia by having a contract that would grant Elop a huge bonus if he managed to do sell the company to someone else!
"According to changes implemented in 2010, Elop was entitled to immediate share price performance bonus in case of a “change of control” situation… such as selling of Nokia’s handset division."
When this was known it was all over the place in European news.
However Nokia as a company did not go under; it is still very much there, particularly in telecom infra business.
Some customers, particularly very many in the USA, are not so happy to have Huawei or ZTE core switches etc, but in emerging markets they are less worried about Chinese intelligence infiltrating them, and also in Europe there seems to be less protectionism and concerns about national security. So the Chinese are catching the global market, without the Americans noticing much.
That explains a lot about you: although mostly your preference for strong typing. Working for a phone company will do that for you.
No, what explains that is that I used C for the first time in 1993, yet I was already coding since 1986.
So I was doing systems like level programming in Timex Basic, Turbo Basic, Turbo Pascal, Z80 and 80x86 on those in between years.
Also had friends using 68000, AMOS and GFA Basic on their Amigas.
Also I majored in systems level programming, with emphasis in compilers, which meant I have spent quite some time researching old programming environments, and still do. Better than reading newspapers sometimes.
So I learned that were better ways to do systems programming without having the compromises of C.
Plasma sits on top of the Android HAL like Firefox OS did. Nothing different there. Go buy you QC license and see for how long you'll get blob updates.
You're totally wrong about the performance penalty of FxOS compared to Android on the same hardware, but I'm done arguing that with trollaways.
In 2012, at the Akademy (KDE conference) in Tallinn, I spoke with Plasma developers who were, at the time, working on a tablet called "Vivaldi", which was supposed to ship with Plasma Active (the KDE 4 version of Plasma Mobile) based on Mer (the community fork of Meego). And they really struggled with the hardware part: They carefully assembled a BOM of parts for which open-source drivers were available, ordered test devices, built the whole software stack. And when they were ready to start mass production, the manufacturer was like: "What, that chip? That's soooo last month. We have this new chip here, which is completely undocumented, but we have an Android driver for you." Last I heard, they never got an actual device shipped because of that mess.
I don't know if it's gotten any better since then, but I can easily imagine how that situation led them to base the new Plasma Mobile on the Android HAL.
I don't see that detail mentioned on the site. Perhaps people familiar with KDE and Plasma know, but I don't. Or perhaps I'm overlooking something obvious ...
EDIT: Wikipedia says that Plasma is a desktop environment, not an OS, and that "Plasma Mobile is a Plasma variant for smartphones".
For mobile developers, the biggest difference is that they'd be using the Qt framework instead of the Android framework.
So the pitch at least for mobile developers, should be why it's a more pleasant and better (and more productive) experience to develop mobile apps with Qt vs the Android frameworks.
I'm not how much better Qt is going to be since I haven't used it. But I've been a long-time desktop Linux KDE user, and one of the biggest gripes I have with KDE is that its quite unstable and buggy compared to Mac and Windows.
KDE 4 became almost very-stable with 4.13+, but the early version of KDE 4 were horribly unstable. With Plasma 5, from what I hear, things got worse again.
This is the biggest problem, I think. To the people who have actually used KDE on deskotp Linux for a long time, how many of you have enough confidence in the stability and reliability of a mobile Qt/KDE environment to use it everyday?
I switched to Plasma 5 about a year ago, when the first stable version landed on Arch linux. It's been a daily driver since. Initial versions had lots of bugs in them - persistently high CPU usage. Sometimes the desktop hung for no fault of the user. Proper resumption after standby/resume was a lottery. On the plus side, the Breeze theme was a breath of fresh air compared to the older Oxygen theme.
Since version 5.6 was released things have improved and keep getting better with every new version. There are still occasional cockups with Intel graphics drivers leading to high CPU usage. The problem though seems to stem from the Qt libraries. Some GTK 3.x apps don't show proper widgets (blame Gnome devs for not having consistent themes for 3.x versions). I did give other DE's a go - Gnome 3.xx, Cinnamon, XFCE etc., but always ended up switching back. Plasma offered the best mix of customizability, performance and aesthetic appeal for me.
Both C++ and Java have been improving their syntax in recent years. I'd recommend reintroducing yourself to the latest version of either.
Second, there are experimental modules systems available that avoid many of the disadvantages of header-only code. If things go well, modules will be standard in C++20.
There are certainly things I would improve about the syntax of Java and C++, but both are improving quickly in that regard.
But for some reason they use marketing language to make it look like they have invented some new mobile OS.
By the way, it doesn't look very secure:
- first, you have to unlock the bootloader. It means you can install custom firmware but anyone having physical access to your phone can do it too.
- Google did a lot to make Android more secure. For example, every application is run under a separate user account to protect it from other (potentially malicious) applications. Applications' privileges are restricted. KDE doesn't have such features.
So if you like KDE or want to run or maybe write KDE applications this project will help you. But you'll have to forget about security and I guess the project is in early development stage now so there can be bugs and something might not work.
*> it does use android drivers*
I'm a LFS kind of guy. I'm also just as opposed to proprietary driver blobs as the next guy...
But, for the purpose of getting more use out of my existing phone... I guess I can just root the thing and copy some kernel modules off, eh? Nice.
Lot's of that is rather generic. Plasma Mobile is using the same libhybris to interface glibc system with blobs built for bionic (Android) libc.
In the second link you can see a reference to KDE Neon, which is development distro based on Kubuntu.
See also: https://neon.kde.org
> * https://plasma-mobile.org/technology/
This page doesn't mention the OS, afaict.
> * https://plasma-mobile.org/nexus-5/
This page seems to describe installing Plasma Mobile on top of Cyanogenmod, a fork of Android. Neon is mentioned only under "OLD INSTRUCTIONS AND ERRATA (no longer needed)".
See for example: https://kubuntu.org/news/kubuntu-team-launches-plasma-mobile...
It turns out it runs Neon, in a container, on top of Cyanogenmod.
You can read more about the approach here:
It turns out it runs Neon, in a container, on top of Cyanogenmod. They formerly used Ubuntu Touch, but no longer.
My favorite mobile OS so far has been Meego that ran on N9. That device was mind blowing and that OS. Amazing. It had such a simple, yet useful UI. Multi-tasking was better than what even Android has now. I hope Jolla doesn't die like that and we see a lot more devices come out running Sailfish.
You'd say that is flashy? Just curious :)
I mean checkout this: https://www.kde.org/announcements/4.3/images/kde430-desktop_...
Too much going on. Too much transparency, too much eye candy as if everything is made of glass. Plus the unnecessary widgets to hold desktop icons. I'm no expert in UI/UX design but as a user I find it unpleasant.
Just other day I was trying latest Ubuntu on a pen drive and I couldn't believe that renaming a directory now open a modal dialog that asks you for the new name of the directory. WTH? What was wrong with the inline directory naming? It was perfect and everyone else does it. It's such a basic thing to understand. You rename an item and edit it's name inline. You see all the time what you are remaning. As soon as you rename it, you see the change take effect immediately and see the new item take new place if sorting changes. Instead we now have a modal dialog that that asks for the new name. I also couldn't find any "create new file" in right click. What was wrong with that? IRRC, the search button also does open a dialog elsewhere.
Then come GnomeShell. That thing has 4 different types of controls on 4 edges of the screen. Every edge has a different control. Left has dock, top has a panel, right has workspace switcher and bottom has yet another panel which hosts different indicators than the top panel. I think bottom one handles 3rd party app indicators. Why do I as a user have to remember which different positions for different indicators? If I open something from top left corner (launcher) and want to switch workspace, I'll to drag my mouse all the way from top left corner to the right edge. I just don't get it.
I do actually really like Unity7. It's simple, clean and yet powerful. All indicators are in 1 place, switcher is simply inside dock and has amazing keyboard accessibility. I hope Unity8 doesn't ruin it with it's focus on mobile.
I don't hate Gnome. I love Gnome and has great respect and gratitude for it's developers. They are some of the best developers I know. It's just that the recent UX decisions have made it unusable for me and it kills me to think about how amazing and simple Gnome could have been.
They've also integrated features for setting panel layouts, and there is one ("Mutiny") that mimics Unity. They're even working on a HUD-like feature.
It may be underpowered now, but that physical keyboard still makes my envious: I could almost maybe write code on something like that.
> It may be underpowered now, but that physical
> keyboard still makes my envious: I could almost
> maybe write code on something like that.
It was slower than swype & variants for normal (mail, sms, etc) writing.
The physical keyboard had the benefit of providing relatively easy access to 'dev' keys - esc, ctrl, special characters. But it was so teeny that even as a proficient user (it was my primary phone for 3-4 years) the experience was arduous.
Years later I bought a tablet + BT keyboard (a Logitech one with the hard clam shell that became the stand) and that experience is much preferred. Would work well with a phone too, if you're happy with a small screen. Not pocket sized, certainly, but the keyboard is actually usable.
But I could and did use it to write and edit long-form prose.
It's way better than a touch-screen for shelling in and fixing server issues when you're stuck at a party away from keyboard.
Actual code writing tends to mean using lots of symbols though, and while the N900 keyboard was better than a touch screen, both make you want to rip open your skull and put the wires in directly in frustration.
I miss that keyboard.
When I had that keyboard, the best email-interface was still Mutt over a terminal. You could use Vim! Type without looking! It was ace.
That phone had the best microphone out of any I've ever owned by a clear mile too. Certainly the only one that could stand up to being used in the band practice-room without just distorting to hell coz of the volume.
I still use it for that, for video-recording band-practise, cos nothing else ever came close. The USB port broke and now can only transfer files with WI-FI and have to use an external battery charger, and all my batteries are swelling slightly and really ought to be retired.
But I don't have anything else that will actually work for it.
It's almost enough to make me miss my first phone, which was rubbish as a smartphone, but actually did have a real keyboard.
I installed it mostly so I could customize the backdrop, but I stayed because those few added gestures make prose input so much more efficient.
Still entirely awful and terrible for writing code though.
Delete the stupid Gif-Keyboard plugin, add in the "OMW" one for common-phrases-shortcuts (then build lots of templates), add the copy/paste bar, and the numbers row.
I like the fireworks-noises plugin too, audible feedback is helpful, but wish it sounded more like Ziggy off of Quantum Leap.
They appear to have ignored my suggestions on their forums to make it sound that way, and can't see a way to make my own plugin.
 - A feature of my S7 that nobody I've ever noticed talk about online is the ability to control the volume so easily just by putting your thumb over the speaker as you hold the phone. The fireworks noises are basically muted that way if you're trying to type in public ;)
I've definitely coded bash on it, many times.
Earlier versions of Maemo had been using GTK.
The intro of the Qt based Maemo 5 on the N900 effectively drove a wedge into the community, in particular as Nokia gave away N900s at the unveiling.
At the same time Nokia and Intel could not agree on the structure of Meego, with Intel first going deb (same as Maemo) but then switching to rpm with Moblin2.
In the end the whole mess was handed over to the Linux Foundation as both parties lost interest (Intel started Moblin in large part to light a fire under Microsoft to support mobile Atom).
Sailfish is based of Mer, A community reimplementation of Maemo without the proprietary Nokia bits (power management being a key part), that was started before the merger. But adopted various Meego elements afterwards.
BTW, it was the Sailfish IRC channel that spawn the supposed Poettering death threat. It was actually a bad joke about using kickstarter to fund an assassin after the Sailfish teams latest late night session of fixing breakages that a updated systemd caused. yes, Sailfish use systemd. And they were also a early adopter, if not instigator, of Wayland.
The one and only feature I want integrated into systemd is the ability to execute a command to punch Lennart in the face. If they did that, I might use it for a week.
Judging from the video, the state of Plasma Mobile is very impressive.
Main plasma mobile developer here, I wanted to reply some questions that surfaced in comments and give a bit of overview on current state and where we need help. We initially based it on Ubuntu Touch, and later on started using our own stack based on Cyanogenmod, more information on it at : http://blog.bshah.in/2016/05/02/plasma-mobile-new-base-syste...
So basically currently Plasma Mobile is made of,
- KDE Frameworks
- Plasma workspace
- Plasma phone shell
- Various Applications
- Minimal Cyanongenmod base
- LXC userspace tools for android
- Neon rootfs with Plasma Mobile
Q: Why we are using libhybris and not freedreno?
A: Short answer: In theory, we can use freedreno.
Long answer: kwin_wayland supports DRM backend, and freedreno provides the DRM on android devices, however we don't have access to device which supports freedreno easily. For instance I attempted to get mainline kernel working on Nexus 5 device and also submitted some device tree source files to Linux kernel tree, and will be available in kernel 4.9 release.. But sadly I was not able to finish this project
Q: Why not other devices?
A: Currently we don't have access to multiple devices, however we will be happy to help the community members to "port" or in other words, make Plasma mobile run on their devices.
Q: Where we need help?
A: You can help on pretty much everything.. Some things that come to mind, are
- Porting to other devices
- Various Plasma on Wayland todo items
- More applications for Plasma mobile
- Work on base system
Edit: edited for line breaks
Thanks! So were you able to get a usable result on Nexus 5? Sounds like it's the best candidate for this task. Do you plan to continue that effort, or there are some blockers that you couldn't resolve? I'm running Sailfish on Nexus 5 now, which uses libhybris and CM kernel with Qualcomm blobs, but I'm interested in more open alternative, and without driver blobs as well.
Not really there are not much important blocker to get DRM working, however main thing is I don't really have free time to continue that effort.
Also, when you say DRM, do you mean digital rights management? Why do we want that?
I have a Huawei Honor, but can't find any Android alternatives for it.
Is this hardcore hacking action stuff or can this be done by the average CS-major/Developer?
However, it seems they're trying to appeal to the more Libre folks - anti-all-current-smartphone-OS-vendors and their watchful eyes - who are generally developer types -- at least as far as I know. And those types of people are usually willing to give in the UX department.
I'd love to see this (and any alternative smartphone OS) project succeed, but it's got a fair amount of growing to do before that happens in my opinion.
I would love to someday have Linux running on my phone and just be able to do whatever the heck I want with it with simple APIs for interacting with sensors and cellular voice/sms/data just working. Like Arch Linux for your smartphone. That would be so fun to hack on I think.
I'd love to be able to have a working, stable and open mobile system. I don't want to be locked in into Google because i don't trust them (or anybody else) enough.
Android is great but i miss linux-like feeling of possibilities. But it can be due to my lack of technical skills. Maybe if i rooted the phone it'd be good enough now?
Anyway, i hope they succeed.
One way to take a step in this direction without root is with Termux and its addons (android 5+ only). It's made me much more content on android, although it'll only be truly comfortable if you plug in a keyboard or your phone has a physical keyboard.
Oh, but you should be impressed. For how long could OpenMoko not make phone calls?
Open-source phone OSs have a habit of neglecting actual phone functionality. So I think it's great that they highlight it.
Of course, Neo1973 was a different story, as it pretty much wasn't supposed to be fully working on day zero ;)
I then flashed a fully featured Debian on it which was able to do everything except making phone calls. I was so excited about that while all my non-techie friends were like "Well, lucky you but now you have a so called Smartphone which isn't even a phone."
Dropped it as a daily driver after two weeks or so to leave it on my desk for a long time until someone on the Freerunner mailing list asked if someone is willing to sell theirs. 20 people offered theirs for free so I couldn't get rid of mine. Gave it to an Open Device Lab then, they still own it but never listed it in their device list.
But somehow I don't regret buying it in the first place.
I believe Openmoko used GTK+. Maybe Qt was what the project needed all along.
And since 2008, when I got my Neo Freerunner, I didn't have many issues with phone functionality unless I broke it myself (which I kept doing, as I loved to tinker with that phone) - and I've been using Freerunner for years until I replaced it with N900. The worst issue I experienced that wasn't my fault was that in GTK-based Om2007.2 messaging app slowed down awfully once it got thousands of SMS in its history, with evolution-server hogging the CPU for many seconds on most actions. Didn't happen on next OS iterations.
There was also buzz issue on early devices, but that was easily fixable.
Running linux on my phone is cool, but getting away from binary blobs would be priceless.
More here: http://www.osnews.com/story/27416/The_second_operating_syste...
If the anchor text ("VIDEO INTRO") isn't hovered while its parent `div` is, the result is black text on black bg.
Freedreno kind of was progressing to enable that, but I'm not sure if there is any handset around which would be usable in native form given there some other drivers involved besides the GPU. Did anyone try that with Google Pixels?
Plasma Mobile supports the Nexus 5 and (maybe) the OnePlus One right now. CopperheadOS doesn't support either of those. I was unable to get a reliable source for supported devices for Ubuntu Phone (best I found was , not even sure if that's related) and so far I don't believe that the supported devices for THAT platform intersect with the other two.
Searching for sailfishOS device support only comes up with Jolla phones. It seems as if not only is the market lacking alternative systems, it's also near impossible to try out the ones that do exist. Buying a device for some experimental OS is something I have done (Flame for FxOs - still sad that it died, owned a Palm Pre), but cumbersome and expensive.
Copperhead is just a liberated Android for the most part, it just replaces Replicant.
Since Jolla develops sailfishOS, and the OS itself is mostly proprietary, it should be no surprise there isn't a hobbyist community supporting it on Android phones.
Plasma Mobile and Firefox OS were both in a class that could feasibly eventually sell phones with it stock. Its the same problem as the desktop Linux ecosystem - as long as you have to actually install the OS yourself, the market is nonexistent compared to the preinstalled market. You need units in stores in peoples faces before you can start making meaningful inroads into market adoption.
"Liberated" to the extent that it removes Google stuff such as Play Services, yes. However CopperheadOS is not completely libre. They do include non-free 3D drivers, for instance.
I agree that Copperhead largely appeals to the same group of people, and it's much more actively developed.
What I'm hoping for is some sort of 'reference device' (i.e. the Flame for FxOs) that is supported across platforms. It doesn't matter if it's ~older~ (Nexus 4?), just a way to compare platforms against each other: Run Ubuntu Phone, Plasma Mobile and CM on the same device (not at the same time ofc), check out if your use cases are supported/the platform can do what you need. Keep whatever is best, retry in 6 month. That'd be awesome.
hardware specs: http://www.gsmarena.com/lg_nexus_5-5705.php
I'm sure they will have at least a couple dozen of installs.
However Plasma 5 still has its fair share of UX issues here and there so I'm crossing fingers the KDE design community gets its hands on this.
But you don't want to clearly tell us who it is?
Their main-project is the KDE Plasma desktop environment, which is a GUI with accompanying applications for desktop Linux.
Probably the most famous thing outside of the Linux-world that they are responsible for is KHTML, which is what WebKit (and therefore also Blink) is based on.
I am totally against Google and its restrictions and tracking proprietary code in Android but this project looks more like an attempt to get user base to sell them some paid services later.
Do you really need KDE to make your phone "hackable"?
Google did a lot to polish Android code and released it under an open license. I doubt that project is able to invest a comparable amount of work.
Having the same interface on desktop and mobile devices is not going to work well.
UPD: their installer installs a firmware (like twrp) that makes your phone unprotected from reflashing and stealing your data or installing a backdoor if someone gets physical access to the phone. They do not warn about it.
KDE e.V. is a non-profit, so I don't think they could legally even do that...
I'm now very expecting the KDE tablet.
Ubuntu Touch is the big one though, I'd love to see more devices compatible with it. Some industrious fellow out there is probably willing to port most of the python crap in Kali to something more useful, agile, portable, and compatible with Ubuntu Touch, if something like that isn't already going on.
E.g. if you make a video, don't make it 6 minutes long, don't use such kind of annoying background music, don't advertise that you can call someone. It's like advertising a computer by showing that it can connect with a USB mouse. Show us the dev environment for apps, and how far your API can look into the system. Show us the operating system and its features, e.g. by showing that someone manipulates the list of processes in screenlock widgets or something. Show us the people who do cool stuff with it that they couldn't do in a walled garden environment.
The old free software dilemma: Do you wait until your product is polished, thus cutting yourself off all possible publicity? Or will you be vocal about your development efforts, and stand the complaints about rough edges, in order to attract helping hands?
E.g. both your messages target different people. Why inform users about your work in progress product instead of developers who may help you? And is this page really the best way to generate helping hands or is this more a user ad?
Verizon is also required to allow using any compatible LTE handset, and they aren't allowed to care what OS you use on it. The problem is that nobody is developing them.
It works way better than a few years ago, and for the reference, almost all mobile providers, including Verizon and AT&T (not sure about Sprint) are violating Net Neutrality by giving preferential treatment to their own services.
They've also been promoting sleazy marketing strategies like claiming to have "no contract", while stabbing people by cancelling people's device payment plans if they cancel service. I mean, they have only gotten worse since their primary marketing appeal was an attractive woman in a skin-tight leather suit.
They aren't any better, if not worse, because in contrast to T-Mobile, AT&T and Verizon are asking for money from other services if they want be exempt from caps. In my view they are all bad when Net Neutrality is concerned. It can be fixed only with better law which ban zero rating, and as well bans caps as a method of fleecing users.
It was proven time and again that data caps are driven by greed, not by necessity. That's clear in wireline networks where congestion isn't a problem at all, and can be as well demonstrated in mobile ones, where spectrum limit can be an issue. Caps don't prevent network congestion in mobile networks. I.e. don't pretend it's a network management tool, it's not. It's just money gouging tool. So it has nothing to do with fairness.
ISPs already have tiers for bandwidth. There is no need to use caps as well.
This is a simplified example of how tiered pricing works in a business sense I wrote up a few weeks ago to explain it: https://plus.google.com/+JakeWeisz/posts/8dSeCHrzZpo
Exactly my point. Therefore it's driven by greed, and is an indication of monopoly abuse. To repeat what I said. ISPs already have tired plans for _bandwidth_, and those who are heavier users can pay more for more bandwidth, which has technical necessity behind it. There is completely no need in caps.
> Your focus on that indicates you have no understanding of the market.
I understand it. The only reason this garbage like caps and violation of Net Neutrality happens is lack of competition, and crooks taking advantage of that fact in the context of insufficient regulations to prevent them.
The idea of paying for network speed is a poor one: It means the network is intentionally crippling their product when they can provide better, and they're under no obligation to even guarantee the speed you pay for. Paying for network speed is not good for the consumer.
Paying for usage is the ideal situation, because the provider and the customer have aligned interests. It's in the best interest of the provider to provide the fastest, highest quality service, so that users can consume the most data. And consumers get the best possible product, without being intentionally gimped or throttled.
Stop the demagoguery please. Calling greed "math" doesn't change it being greed.
> Paying for usage is the ideal situation
You sound like an ISP shill. Are you one? Paying for usage is horrendous, because ISPs who own media services disadvantage competing media services, by excluding their own from caps. This should be forbidden not just by Net Neutraility, but simply by antitrust law. But I suppose you think monopoly is ideal situation too, right? And you'd claim there is nothing wrong with "asking to pay more" because people have no choice but to use the abusive monopolist if they want service, and it's not greed but "basic math". Yeah, right.
Arguing with shills is pointless though, so I finished here. Everything was said above already anyway.
I have no business in the ISP space, accusing someone of being a shill because you disagree with them basically renders you useless in a discussion, and speaks to your inability to look at the argument objectively.
Sprint and T-Mobile are _terrible_, and no amount of savings is worth suffering through their networks. Oh, and there's the little matter of T-Mobile leading the charge against net neutrality.
Hopefully I don't send up swallowing these words, but I've gotta say that they appear to have made it extremely easy to install this. Running two fastboot commands, cloning a repo, and running a shell script is pretty easy, and making it easy goes a long way towards making it approachable.
EDIT: Install script is broken on macOS. I fixed it and got it flashed. It's dreadfully slow. :( I'd consider stability and performance my top two priorities. I already largely hate mobile devices, so the poor performance is really frustrating. I still need to play around with it to see what the other capabilities are like.
Or $425: http://store.shopblackberry.com/store/bbrryus/en_US/pd/produ...
Any particular reason those don't work for you?