Wanna buy my N900? I don't miss using it. Especially its abysmal GPS, abysmal video recording, resistive touchscreen, terrible manual calendar sync setup, no choice of map software, etc. etc.
Good riddance. That proper keyboard alone couldn't make up for everything else.
I live within an European city - not downtown, but relatively close. My commute by car over ~10km is 18-20 mins, same distance by public transport takes 40-50 mins, depending on train reliability and workers not striking.
I don't intent to change your mind because it's often that people are stuck to their opinions.
Just want to say that sitting in public transports I can do other things such as doing some work or reading a book. While sitting in a car feels terrible to me. 30 minutes of driving a car is a lot worse than sitting in public transport. Also, if I have to commute by walk/bike, I also feel much better.
> Just want to say that sitting in public transports I can do other things such as doing some work or reading a book.
In my experience that kind of activity was often not possible, especially in cases where one bus was late and I had go worry about getting to the connecting stop on time. Likewise I couldn't really read b/c I might get distracted and miss a connection.
This was all pre-Internet and of course pre-unlimited data plan. These days I might have a downright pleasurable experience on public transport listening to podcasts under those conditions. Except here in Seattle there are just too many maniacs on some lines.
What's there to change your mind? There are areas that are poorly connected and cars are much more convenient.
I live outside Rome, Italy, my SO works downtown. It takes her 35ish minutes to get to work by train, it would take her way more than one hour by car.
Hell, it takes her colleagues living in Rome center often an hour to get to work on a 6 km drive.
The funniest thing was when I worked with a guy that commuted by train from Naples! That's 150 miles away. And he would still get back home quicker by train than people living in Rome.
Neo900 is dead. Unfortunately. It was always on shaky ground (the nature of a hardware project) but what seems to have killed it was PayPal withholding its funds for long enough to take the wind out of key people's sails. PayPal just decided to abruptly lock out the project account one day after accruing a substantial number of down-payments, and refused to give the funds back for around a year. By the time some progress started being made again, the funds were no longer enough and the project was at that point based on seriously obsolete hardware (as opposed to the regular kind of obsolete most hardware projects have to work with).
* This was long ago enough that PayPal wasn't _quite_ as famous for its practices.
* In Europe people generally assume that companies big and small won't try to fuck you over because there are usually repercussions. Apparently American companies are exempt.
* When trying to get sizeable donations for a moonshot hardware project with high risk of failure it's ideal if donating didn't involve entering an IBAN. (Although I think kickstarter wasn't considered because the project was so niche that there was no chance of hitting a "milestone" in a reasonable time and the approach was to use funds as they came in order to allow the project to make steady progress. The idea being that people who were unconvinced earlier might become convinced later and you'd slowly attract enough support as you progress the project. I think the incident pre-dates crowd supply.)
The problem is the hardware, not the software. Also, what you want as a paranoid person is your baseband not part of the SoC running your computer - this project hear does that, Jolla and others are using standard Android SoCs.
Jolla added libhybris to make it easy to use Android hardware adaptations - which at that time was needed to get a phone out (ste, which the first Jolla phone was supposed to be based on, decided to get out of the phone chip business during the prototyping phase, and that was the last vendor offering proper Linux drivers). I never was much of a fan of that as you just pull in way too much uncontrollable crap - unfortunately it works good enough that a lot of other projects then also jumped on that, instead of reviving a focus of doing proper Linux drivers (something I was worried might happen when the libhybris development started).
I'd argue software is the main problem. If you want to make a new smartphone OS, just target a pixel or something. The driver + kernel stack as pretty close to as open as you'll find anywhere. The hardware is flagship-grade, updated every year, and shipping now.
I've had zero luck putting a non-Android daily driver OS on it though. I'll define daily driver as "all of this works tolerably well":
Phone, SMS/MMS, web browser, podcasts, navigation, music player and camera.
Heck, drop the camera requirement for version one, and then you're down to "video, audio, GPS and phone stuff works".
Jolla's Sailfish OS is used as a daily driver by a small niche in EU, probably tens of thousands of users taking into consideration download and update traffic.
It's definitely usable as a daily driver. There are some rough edges if you only want to use native applications and want to avoid Android applications, which go through an emulation layer. But it's still pretty nice! Things like offline mapping work really well.
You can, by using the libhybris hardware abstraction layer I've mentioned. It is relatively simple, though still requires understanding of how low level stuff works. The main problems there are graphics and modem, both of which typically are not open drivers - and with that you then pull in half of your typical android system into your regular linux distribution just to get the hardware working.
If you don't care about the modem and graphics acceleration (or, in same cases, graphics output at all) you should be able to get it booting with the available kernel relatively easily.
Camera also tends to be not tends to be not that much of an issue - typically there's enough in the available kernel that you can get a gstreamer pipeline running, and then just have to figure out how to make it not look completely shit.
And after all that you still end up having a device with the baseband sitting on your SoC.
