Why I'm Ditching Android
kevq.uk
kevq.uk
Apple has serious problems, but on balance it seems to be the better choice. I also tend to agree with the OP that the iPhone SE is a reasonable size, unlike every Android phone on the market. I just really wish there were a decent chat client that supported XMPP-based services, that's really all that's stopped me from moving over (my carrier lets me receive SMS/MMS messages to an XMPP address and receive calls via SIP, so it's rather important to me).
As a developer, it constantly burns my biscuits that Apple software only runs on Apple hardware. The fact that I have no choice but to buy expensive Apple devices to develop for their platform is irritating.
I've never understood this line of thinking.
Maybe it's because I've been selling programs commercially since the 1980's. Back then, if you wanted to develop a program for a Commodore 64, you bought a Commodore 64. If you wanted to port it to a TRS-80, you bought a TRS-80. If you needed an Atari version, you bought Atari gear.
In the mid-80's it was just ordinary business that if you were developing a program, you released it on Commodore, Apple, Texas Instruments, IBM, and a few others. And to achieve that, you bought at least one machine from each of those companies.
The concept of "I want to build an iPhone app on a Windows box" is a strange new phenomenon to me.
To be fair, I can build an android app on a Windows or Mac.
Also you're talking about buying a computer to build on that computer. I think the argument was about needing a particular brand laptop to develop apps for a different device.
Fighting the customer doesn't usually go well in the long run.
So it really is on a different platform already, but one within the walls of the brand.
Sure most bought C64, Spectrum and so forth.
However if you actually wanted to be productive, you would be buying a bigger computer running CP/M, VMS or UNIX variant, cross compile Assembly code and use a transfer cable.
Apple is the lone hold out here.
But they also have no reason to change.
Follow the steps at https://sites.google.com/site/easylinuxtipsproject/oldgrub for a free Windows VM development license.
For Apple, it is an entire hardware platform.
For testing, yes. To protect their sanity, developers of big projects developed their code using rented CPU minutes on a mainframe.
Maybe apple should provide pay-by-the-minute xcode-as-a-service for the real 1980s feeling?
There certainly seem to be enough developers who complain about this. I wonder if there'd be a market for a virtual-iphone-dev-box-thing.
I don't think anyone would object of all it took to develop for iOS was the device bring targeted, or even an iOS device. The fact that you have to buy a different piece of Apple hardware is this the issue.
You can build Android apps on an Android device. Optionally, you can use Linux, MacOS, or Windows, instead.
> The concept of "I want to build an iPhone app on a Windows box" is a strange new phenomenon to me.
The iOS situation isn't like “you must buy a PC to build PC software”, but more like “you must buy an IBM mainframe to build PC software”.
edit: This is wrong, I can't find the source for that now but probably it was referring to 20% of services revenue. Its only like 5% of total revenue: http://fortune.com/2018/09/29/google-apple-safari-search-eng...
edit2: This was the source[1], they quoted 24% of services revenue:
[1] https://www.bloomberg.com/opinion/articles/2018-11-02/apple-...
[1] http://fortune.com/2018/09/29/google-apple-safari-search-eng...
[2] https://www.macrotrends.net/stocks/charts/AAPL/apple/revenue
This the single biggest reason I abandoned android for iPhone: A premium phone in a reasonable form factor.
By the way, Jolla should be installable on it, if I'm not wrong.
You can get Sailfish OS on it for 50€: https://forum.xda-developers.com/x-compact/how-to/sailfish-x...
I currently use an Omni ROM weekly build (Oreo, waiting for Pie). It's so much smoother and less terrible than the stock software.
Sure, this is not "It just works" (and I do like a lot about Apple's design), but I'm also glad it's not "fuck you, we decided this for you, take it".
Considering I disabled all Sony applications because I have no use for them, with the exception of the keyboard because can't be disabled, Omni ROMs are another option that I hadn't considered. I already dumped the TA partition with the DRM keys many moons ago (I only need to find where I stored it), but I suppose they only work with Android.
I'm tempted by Jolla, but I need a banking OTP generator that only exists on Android and iOS (so Android emulator or another phone)...
The open camera drivers bring a great performance increase in shutter response, but a pretty bad decrease in low-light performance.
The build I'm using has some annoying issues like a barely working fingerprint scanner and Bluetooth audio, but even with that it is less irritating than Sony's to me. I assume both are fixable fairly easy (I'm waiting for Pie builds).
The official Sailfish OS builds come with an Android app runtime (Alien Dalvik), I think, but it may be missing some security features.
I'm not sure if it uses the official Sony camera drivers, information about this seems to be conflicting. Maybe both are available, if Sailfish utilizes Android drivers.
About Sony official camera drivers, I checked briefly and it looks like they are available only on Android.
http://vbn.aau.dk/files/240065248/Mobile_Phone_Antenna_Perfo...
> This dramatic difference in head SAR levels is mainly because the transmitter is located at the bottom of Samsung phones rather than at the top, also they incorporate an innovative antenna that transmits the highest intensities of microwave radiation from the lower back of their smartphones.
http://weeksmd.com/2016/01/the-new-smart-phones-are-6x-more-...
I would just be a little cautious about this. Apple is currently sticking it to Google by making it easy to block ads and by offering appealing privacy features.
But we don't know what Apple will do if everyone switches away from Android. I would guess that the profit stream from selling everyone's data to advertisers when most users are locked into their ecosystem will be very appealing.
Similarly to how Google and Facebook both eschewed ads while drawing people away from other services that were swamped with ads.
Very little risk of that. Our owners also want phones, and for the moment do not mind sharing the brand/models with the 10 or 20% who can afford, and know enough to choose, it.
I keep wondering why Apple doesn't just build their own search engine and provide unfettered results based entirely on popularity/rank (and other "real" metrics) like how google "used" to be in the beginning. Yes, I know search is hard, but it's not as hard as all of the extra steps Google has been doing the last 15 or so years to manipulate their results higher so they get more $ out of it. Certainly it's not as complicated as building a new mapping system from scratch. That would go a great deal further to "increase Apple users privacy" than anything else I can think of. It would also cause a lot of financial harm to Alphabet if all of the sudden all Apple device owners world-wide suddenly didn't have their data going through Google. And, it would provide top-notch results, which Apple consumers would presumably love. What is the downside to this that I'm (obviously) missing?
Anyone is free to modify, build, and distribute their own versions of Android. How else would OEMs ship their own skins? This also means you can audit Android source for vulnerabilities, backdoors, etc.
Every major version ports more functionality from AOSP over to GSF - which is closed source.
I cannot audit GSF and I cannot check for backdoors,, GSF phones home as it legitimate functionality, it is next to possible to verify back-doors don't exist. Location APIs could just be for your location, or google/ three letter agencies could be tracking you .
All the major OEMs include AOSP + GSF and then their custom layers. The only popular OEM using without GSF I know is Amazon with the kindle platform. To get Google certified OEM / use droid trademarks / use GSF you need to jump through hoops and give Google all kinds of access, not remotely same as open source.
I used to work at a team messaging startup Flock and we used to get a lot of complaints from users about missing notifications. We were able to detect impacted users and reduce complaints substantially using duplicate acks from xmpp fcm and app. The details are outlined here in case anyone wants to check out: https://hackernoon.com/notifications-in-android-are-horribly...
IMO the blame belongs mostly to the thingies that kills apps so hard that Android blacklists them, and won't start them again until the user explicitly does it. That Android has that blacklist is understandable; that "battery savers" get innocent apps added is IMNSHO offensively shoddy.
The user retains that right. But the app cannot e.g. schedule anything to be run next time the phone is on WLAN, or next time the battery is being charged.
Edit: I realise I came across a bit too aggressive. Apologies for that.
I do not envy the job of an Android developer.
In a sense they are kind of right just in a wrong way, OEMs got even worse.
You have notifications, that are not important, so low priority.
But equally you have notifications that are important, those should be sent and logged message queue style, so they stay on the send queue until processed and processing acknowledged by the client.
It's just the custom battery saver stuff that some manufacturers implement on top of Android which causes issues. Google doesn't have much control over the privileged process that manufacturers install on devices.
One of those never works.
Though in my experience, any notifications is too many.
And yet useful apps have issues with notifications even without battery saving measures. It's not just a single app, it's been a consistent issue.
However, if a single app is mixing in, say, 5 frivolous notifications with 2 critical ones, I don't think there is any OS-level way to deal with that.
https://www.howtogeek.com/204187/how-to-disable-app-notifica...
Ditto for the New York Times, my local media, and even the BBC.
I just want an app that will send me notifications about breaking news. Breaking news that is actually important breaking news, and not "See our profile of some celebrity you don't give a crap about in tomorrow's New York Times!"
Sadly, the only news app I have left that's permitted to access notifications is Sky News. And even it spams on occasion. But it seems to be only around once or twice a month.
I saw your article about push notifications on certain android phone manufacturers and found it interesting -- something I hadn't seen before. Nice!
But, if I'm not mistaken, the OP is focusing especially on android notifications raised by the app itself rather than push notifications. I'm not sure, but it seems like the problem he highlights involves compatibility-mode changes to the way apps run code while the app itself is also in the background.
Or, it could be that the app developers are not using the officially recommended soup of background processing job scheduling classes the way Android says they should.
Or, maybe that soup of classes isn't always as reliable as advertised.
and I think what the OP was talking about was this kind of Notification. i think he was saying that various apps that count on reliably running code in the background (e.g. when the app itself is in the stopped state and not visible on screen) are no longer able to reliably run that code in the background because Android decided not to let them do that on demand in a reliable way (in order to save battery). but that backgrounded code is what had been placing notifications in the Notification Drawer (when, say, the app became aware that there was a new email in your inbox or when a Calendar appointment was now one hour away, etc).
as for push notifications, nowadays, Firebase Cloud Messaging is recommended. your app derives a service from FirebaseMessagingService and marks that service as "exported" in the manifest. and, you don't have to explicitly start that service. and, though i could be wrong, I think that service does not actually run in the background all the time. i think what happens is that some generic Firebase service invokes your app's service when a push notification has arrived for it. your app's service then processes that message as desired, and, if I understand correctly, it shuts back down. i believe Firebase is basically managing your service so that it does not have to run in the background all the time.
Surely every possible operating system suffers the same problem, no?
1. iOS is an Apple operating system. Every iOS device has a daemon running a service that connects with Apple's APNS (Apple Push Notification Service), and that service routes the notifications of every App to the user's device. APNS is non-negotiable, every iOS device has it running, and every App that wants to [reliably] deliver notifications must use it. It's part of the OS, so the OS won't kill it, in fact, if it crashes, the OS restarts it. It also means it's "well behaved", meaning it won't mine cryptocurrencies in the background (unless Apple breaks bad and decides that it's $1T value is not worth it anymore).
2. Android is not a strictly Google operating system. Google has it's APNS analogous, GCM (Google Cloud Messaging), but not every Android device has ties with Google, its open source, meaning millions (billions?) of Android devices out there are running without any Google ties. So in turn, many Apps device to have their own background tasks running all the time, with a persistent connection to the server to watch for notifications. Problem with this it's okay when you have 10 Apps with notifications, not when you have 100 Apps with notifications, each one having it's own background service. Some Android OEM's want their users to have great batt life and kill those background services, leaving notifications dead.
Also, sure, some user might run pure Android and not have a centralized push notification system, but that is not the problem people usually might be experiencing.
The power management and priority system is rather complicated on Android and incoming notifications might be deferred or not shown at all(to avoid wasting power on low priority notifications) depending on app, app usage and settings.
I never used Flock & would get spammed notifications (via SMS) from them.
My 2012 Twitter thread: https://twitter.com/wdr1/status/255454270160244736
It later which switched to email wherein the justification was "growth strategy."
Nope.
This account's Tweets are protected.
Why switch? After all this time (embarrassed to say), I've finally started to take my data privacy seriously. I really respect Google as an engineering company, and even as a product company. Products like Search/PageRank, Maps, StreetView, SkyMap, Translate, Books/Scholar, AdWords/AdSense/AdMob, Places, Trends, TensorFlow (and CoLab w/ free 12 hr sessions of TPU or GPU), BigTable, Gmail, Glass, and of course Android all are/were really great products. The only problem: those offerings are for the direct purpose of collecting your personal data (or the indirect purposes of making their other products - which collect your data - more efficient, or to bring more people online to collect data from).
I would love Google as a product company; I hate them as an ad company (85%+ of revenues resulting from advertising activities). I have migrated from, or I am currently migrating from, every Google product with the exception of YouTube (difficult to break from that, so I try to mitigate by having multiple accounts) and TensorFlow.
Notifications on Android were never an issue for me. Maybe I didn't have a similar suite of apps as OP. (iOS notifications have been more annoying thus far).
These days I can't even begin to work that out. There is easily a 100x more traffic and every single time I ran a capture I would find a whole bunch of new hosts being contacted that have no business talking to my phone. And I just use my phone for email and messaging. Not a big app user.
KaiOS may be a continuation of the same product, but it's not a continuation of the same project.
I told my parents to buy an Android initially but ultimately they moved to the iPhone because they thought it was simpler and better than Android. To me the fact that I can code my own apps with Java without having to buy a mac is a plus, but I understand people who aren't developers don't care about hackability if they can afford an iPhone.
IMHO iOS is good for developers who are okay with coloring inside the lines set out by Apple. The developer experience isn't perfect by any stretch, but writing personal apps/utilities in Swift using a package manager like Carthage is pretty painless.
Apple has some great features for de-centralization, such as the Multipeer Connectivity framework.
I think it depends a lot on where in the stack you want to work. If you want to customize your baseband or do system-level modifications then Android is the way to go. If you work higher up the stack, writing apps, then you might like iOS more than Android. I certainly did.
Just got one myself a couple weeks back, after being disappointed by the new Max Extra Turbo-sized models.
Dropping Android for iOS is a joke.
On the other hand it's not always as reasonable as it should be. I do find it frustrating that devices are so locked down, to the point where finding something to run lineage well and has the feature set you want can be tough. With my latest attempt I found a phone where several models, depending on what country and carrier, would not unlock the bootloader. And online sellers of phones are not always specific about what sub-model you get. I had to return a few because the seller sent me a Rodgers or an AT&T one that wouldn't unlock. I can definitely see how enough rounds of this can make some people throw their hands up and let Apple make all the choices.
The idea of mucking about with multiple phones just to find the one which irritates me the least is very unappealing. It's an appliance, I just need the thing to work.
/e/ might be a better fit for him.
If you are using linage and /e/ you can’t really add “works with all android apps” as a check in the pro column.
You’re getting even more fragmented than Android which is already much more than IOS. To each his own but let’s be honest about what these are.
Some core apps have replacements on the other side, like maps, might be why a full leap is better than half measures. /e/ should help with those. Ideally. Maybe it's not there yet.
My biggest problem right now is finding an Android phone smaller than 5", preferably under 4½", that I can both install lineageOS on and actually purchase :-\
Especially true with Contacts I feel like I'm doxing everybody I add to it. I have tried many alternative, but nothing even remotely measure to it.
Gmail's integration with Drive and Calendar are really nice. It's a very mature web email app besides all that. It's not hard to find other email solutions, but in my experience they lack the polish and integration that makes Gmail so valuable.
I have been looking for a good zero-knowledge cloud storage solution that fit my requirements for a while. All of the alternatives I've tried have severe limitations or unresolved issues.
Google drive doesn't work on Linux so it's a non-starter for me. Have you looked at PCloud and Dropbox?
At this point, both iOS and Android are in pretty stable states. It comes down to individual preferences. Author primarily seems to have an issue with Google, which again is justified.
WebView is the built in web view mechanism for all apps that don't want to roll their own web view, and Chrome for Android is a browser that makes use of that WebView mechanism. Strictly speaking, a browser is just an interface that lets you interact with web pages.
And you're not locked into WebView: if you actually wrote your own, you're entirely free to deploy it. It's just insanely hard to write a web render engine these days so for most people there's no point in the slightest: it just makes your application bigger.
One example where it _does_ make sense is Firefox for Android, which comes with its own engine, because as long as the Android core classes area available, it should be able to run. Not "stop working" just because someone tailored their Android build to not include WebView.
Android WebView is a system component powered by Chrome that allows Android apps to display web content
iOS has just as much bloatware, and much of it can't even be disabled, let alone uninstalled.
For privacy, consider that iOS does not let you disable AGPS data collection. On Android, it is opt in. iOS does not let you open addresses in an offline maps application by default, so Apple gets all your address lookups. iOS does not let you replace your default SMS app, so Apple gets all the phone numbers you want to send a message to in order to see if that phone number is associated with an iMessages account. On Android, you can set your default SMS app to Signal to get automatic private messaging by default. Worst of all, iOS does not let you develop for your own phone without registering an Apple ID.
Apple talks a good privacy game, but there is no substance there. You are jumping out of the frying pan and into the fryer.
I have a Xiaomi Mi A1 with Firefox and no Chrome anywhere. I flashed LineageOS with the Open GApps nano package (which does not include anything you can also get from the play store, like Chrome) and don't even know what the stock experience is like. So far I didn't experience any major problems running a non-stock ROM.
I’m sure the author would be glad to add that to the list of complaints. One OS might say, “Surprise! You got the wrong version/model/puppy for your use case!”. The other one won’t.
Or an Android One device.
Pure Android doesn't have to.
Basically I'd like the phone to cut off all mobile data, wifi, gps, and other radio and kill all applications when the screen is locked.
OnePlus has some background activity limits and you can turn on the aggressive Doze (or whatever it's called these days) but if my phone is locked I would really, really like to just receive calls and sms and have the system enforce that, and switch off all the unrelated hardware to extend standby time.
It will still poll for notifications - but nothing else.
It saved battery if I wasn't doing much with my phone. If I was constantly unlocking to check where I was on a map then it ate up more battery and it was incredibly frustrating as it takes a while to get a GPS lock when you don't have Wifi to assist in a city, until Wifi come back on which also takes a while. Friends that only communicate with messenger and Whatsapp had trouble getting through. Loads of apps that had been trying to communicate also woke up once there was a connection using up more CPU cycles, slowing everything down some more.
IMHO, its not worth it. Just use the background apps controller in Android 8.1. Whitelist the things that you do want notifications from and everything else can wait for you to open the app.
Google had such a good opportunity with android, and shit the bed with it, abusing users and letting manufacturers and carriers join in on the abuse.
There should be a "Right to Root".
https://www.techradar.com/news/canonicals-dream-for-an-ubunt...
https://puri.sm/posts/librem5-smartphone-makes-major-strides...
Turns out the number of people that actually want a phone with a terminal interface is in the dozens.
I use termux [1] which allows me to install whatever software I want with APT. I can use vim, ssh into servers, and mostly do whatever else I would do on a computer. It's not a strawman, it's just a developer-centric niche.
Although I still don't think it'll make for a very good phone, and I say this as a backer that's quite excited to get his hands on the Pyra. I'd look towards the Librem 5 for a more realistic phone experience.
So which is it, Apple is grossly over-priced or inline with what a decent Android phone costs? And then the author goes on to complain about the data firehouse back to Google and bloatware. Are we yet seeing that price is not always measured in dollars? I don’t mean to pick on the author, I guess it’s just interesting to watch the process of coming to this realization.
But the notifications, holee-shit. That seems like one of those “under a full moon...” reports, but others here confirm. I’m so speechless, I don’t even have a snarky Apple fanboi comment.
https://www.xda-developers.com/e-google-free-lineageos-fork-...
We're overdue for some viable third option.
"Android experience relies heavily on Google's Play Services. The microG project creates an alternative to installing Gapps, which install and execute closed-source blobs on our phones. MicroG however requires a patch called "signature spoofing"..."
I do use it. The notifications aren't flawless, since any application using firebase isn't going to work (the old GCM still works for now). Things may break any day. I suppose its akin to being on your own whilst running a Hackintosh except that the software is FOSS.
A reasonable alternative is a model where you pay for the software and get a license to run it. For that, you can opt for Sailfish which is almost completely FOSS. Heck, you can run community versions of Sailfish as well but without Alien Dalvik (Android compatibility layer). But I wouldn't depend on such too much.
Other alternatives are the Ubuntu Touch/Phone project by UBPorts, and the KDE people are also still alive and kicking. There's postmarketOS, based on Alpine, giving older smartphones a second life.
And you can also opt to use a dumbphone plus a mobile device. You don't need to have a smartphone.
I want a premium phone. I like good cameras, and big fat CPUs. So I've been using Samsung phones for a while. I currently have an S6, which I have been pretty happy with. But it has come to my attention that it has received its last update about 6 months ago. Samsung only sends updates for two years.
Having an internet-connected device that no longer gets patches? Seems like a terrible idea to me.
Apple supports their phones for 5 years. So that's the direction I'm currently looking.
The Pixel 3 is a big improvement over every other Android experience I've had, and I've been in the ecosystem since the Nexus One. It's the first Android phone I've used which actually feels like a premium phone, which is what I'd expect, considering its hefty price tag. Its camera has been called the top of the line by many reviewers. Heck, right now there's a post in the HN front page about the Pixel 3's camera [0].
Stock Android is still kinda buggy and rough around the edges in a few places, but it has definitely been improving. I've found the latest version to be much more stable and reliable, at least during the short time I've had it.
This is what happened to me when I bought a Nexus 5, and it was the final straw. I bought a cheap second hand iPhone 6S, and havn't looked back. I do miss the notification LED though, and the better clock/alarm functionality on Android.
While I did so for purely financial reasons (Microsoft was in the process of bailing out, so was putting their stock on fire sale and I couldn't resist, ecosystem disadvantages notwithstanding), I've come to appreciate the design and will be sad once I have to leave (I'm still using a Windows 10 Mobile Alcatel IDOL 4s as my daily driver).
To me, Windows Mobile had some of the best parts of Android (hardware variety) and Apple (regular OS/security updates for all).
Disclaimer: That's pure theory. I'm still figuring out how to do a custom build of LOS16+MicroG for my device, since it's only on LOS14.
> If you already have a LineageOS-supported device, you can grab a prebuilt LineageOS+MicroG image from the MicroG site.
I redacted a lengthy part of my comment since I felt it wouldn't add anything to the discussion; but it went like this: Sadly, my device (HTC 10 aka pme) is officially only on LineageOS 14.x, which is Android 7. Since I am coming from Android 8 stock ROM, I'd like to stay on Android 8 or even get Android 9. There are unofficial LineageOS builds for this (from a guy who just doesn't merge the back to LOS; which I can understand considering the additional effort - on top of all the work is already doing). But of course they lack the necessary patches for MicroG. And the MicroG only pre-builts are based on the official LineageOS build process and thus the official images. So I can only get Android 7 + MicroG with the comfortable "grab image and flash"-method.
I gave building a custom MicroG+LOS{15.1,16.0} a shot using the official MicroG docker image (just a single docker run command) and adding the unofficial builds local_manifest.xml, but those two builds failed for me and I didn't bother messing around with that docker c*. Accidentally, I did that the day before this was posted to HN, no changes since then. But I suppose I'll try a docker-less build on my machine once I feel like it.
Eventually I can just put MicroG on the unofficial build from xda-devs, since that doesn't contain GApps; but I am not sure how great the experience is when not having the MicroG/F-Droid patches. I will see.
EDIT: Regarding signature spoofing, the MicroG github wiki says:
> You can also patch your already-install ROM by flashing NanoDroid-patcher, without any computer interaction. It will auto-patch every updated ROM.
So maybe that works.
What may be easiest for you is actually to use Xposed. I think that can allow the signature spoofing needed for MicroG.
An alternative is to install microG [1], which reimplements assorted Google services. YMMV, but I've been able to run ~70% of all Android apps with no problems.
LineageOS for microG (which is a pre-built ROM) supports all phones that are supported by LineageOS. A full list of these phones can be found here:
Sorted by device age, with pictures and specifications: https://piotr-yuxuan.github.io/choose-a-new-phone/
Sorted by model, with LineageOS version and build day (view on desktop for all columns): https://www.lineageoslog.com/build/scheduler
Also see the rich custom rom scene for Android phones, with highly active communities building rooms for even phone models long abandoned by their manufacturers.
They did say in TFA (or perhaps another comment) that Apple uses privacy as a marketing jab against Google since they don't really want all your datas to sell ads.
Which does seem to hold true in practice, their newest crypto-chip thing they can't access even if they want to, going to the mat to against the FBI and various other instances over the years.
Somehow I dislike everything Apple represents, and reminds. The design, the simplicity which comes from restrictiveness. Even the lightest Linux window manager like i3wn, is better than all of os/x does.
I will just wait till a true open source option comes.
I think there's still an opportunity for such devices.
Pretty close to a dumb cell phone. For the most part nothing in my life got worse. It isn't that hard to ditch a real smart phone..well if your life is spent in front of a computer for your job anyway.
However, the Nokia 3310 is not a good dumb cell phone. The text messaging application is broken for messages for group messages and and multiple messages from the same person in a row. Basic stuff. Text messaging with the old style number pad entry is really as horrible as we remember. Surely there are better alternatives for key entry on a dumb phone in this age. Despite this, it does its job as a cell phone. It almost always has a charge, and it gets reception where my old cell phone would not, and despite its size you can always hear its ringer. So there are pluses. It does contain a web browser and 3G connectivity. I can use its web browser to read HN, and I do pretty frequently, but on most sites the formatting is always horribly wrong. Clicking a link frequently takes you to a different address than was clicked.
I tried both FOSS PND and classic TomTom's/Garmin's etc, none of them while having few strong points can really beat GMail (for now).
I hope Purism can create a FOSS phone but I'm not too optimistic since many tried it and fail, including many with far more resources than Pursim but for now change a jail for another only for background traffic it's not worth my money... I simply choose an economic device (MotoG 4G) and stick with it as long as it will work...
I don't see any reason to pay $1000 for a phone these days, and I probably could have gotten the same experience from the Moto G at $200.
I just want a phone that:
- can last the entire day - can run a browser reasonably well - has decent reception - will get security updates for at least 2 years (expected lifetime of batteries)
I don't need a fancy camera, next-gen graphics, or super high DPI screen, I just need a phone that's reasonably reliable, and even the bottom tier phones are more than capable.
2017, Pixel 1: https://www.jefftk.com/pictures/2017/20171228_091058.jpg
2017, Galaxy S6: https://www.jefftk.com/pictures/2017/20170312_123314_030.jpg
2014, Moto X: https://www.jefftk.com/pictures/2014/stevie-lily-ball.jpg
2011, Galaxy SII: https://www.jefftk.com/images/2011/all/IMG_20120115_202514.j...
Sure, which is why we're seeing a shift towards choosing a phone based on your personal/philosophical/marketing beliefs about how your personal data is treated instead, which is what at least part of this article talks about in justifying the switch.
Also it is easy to find a protectable huge case for these phones since they already exists for eons in the digital industry. I sometimes drop my phone in front of people to see what they are missing: the absence of broken screens.
And given the author's interest in FOSS...
Really interesting Lineage failed. He claims apps kept nagging about the lack of Google app support. How pervasive is that? Could he have just found a couple app alternatives rather than throwing them all out at once?
It's hard to disentangle whether the problems we have are with our phones, with the OS, or with the app ecosystem.
(Quick edit for clarity.)
And with security being key to me, I'm not interested on depending on a third party hack with all my sensitive data.
Yeah, helping third parties engage in signature spoofing does sound far from ideal.
My last phone was an iPhone 6 plus. It had Apple system apps that I couldn't uninstall.
I don't get it.
Honestly, (and personally) I feel better knowing that I am running an Android ROM with publicly available code on Github than any iOS any day
I believe you can use the Application Manager in Android to disable any of these Apps, even though you cannot remove them.
Just don't disable an App the phone actually needs.
Apple is constantly raising their prices ( asp ) and they won't share unit sales in their next stock report.
So I'm curious what this will do for the future.
Apple soured me with their bullshit around throttling the CPU to make the battery last the same. No wonder my phone was performing like shit.
But here's the bad news, this new phone I got is still not so hot. I still run out of battery despite working from home and only using the phone for google maps and calendar/slack when I'm out of office. I don't game on it or anything.
For my next phone I want to find a much more inexpensive phone, swappable battery, with a long-ass battery time. I would go with a Nokia but I don't know if their classic phone supports google maps.
RCS (the Android attempt at iMessage) is STILL not a real-world thing. Txt messaging and MMS on Android is still an absolute joke. My Samsung S8 has, what, a 12-megapixel camera (I never look at these specs anymore) that can take incredible pictures and videos but if I want to send them to someone I have to jump through a bunch of hoops. Upload them to dropbox, share it, send my friend the link, hope they click it vs it just playing in their messaging app.
If I send that video via text message it gets compressed to a 500kb blurry mess. I frequently have to explain to people that Androids don't take terrible pictures, my phone takes amazing pictures. The problem is when I send them to you I'm limited to the maximums of text messaging because phone providers haven't rolled out RCS. It also doesn't help that the Snapchat app back when I used to use it just took a screenshot of our camera app. That further shouted, "Android sucks at pictures, what a peasant phone!"
Tmobile has RCS now but it only works between Tmobile Android users who are using the stock messaging app. They might even need a recent phone with a specific version of Android, I'm not sure there. They rolled this out in June 2018. 2018! How long has imessage been around? And I still have never seen it actually kick in because 90% of the people I txt are on iphones. I also HAVE to use the built-in Messaging app to get this because the RCS API wasn't (not sure if it is now) public so other messaging apps couldn't send over RCS. If I use the Samsung messaging app then I lose the web messaging feature that the Google Messaging app gives me. The Google Messaging app is terrible, though, it doesn't even have the ability to click a person's name and see all of the media shared between us like the good messaging apps do. I have to literally scroll and scroll and scroll to see a picture that I've been sent.
There are all these tradeoffs just for messaging. Do I want an easy web experience so I don't have to pick my phone up every time I get a text? Then I lose the file library when you click a contacts name. Do I want RCS? I'm not even sure which Messaging app to use for it. It's either Samsung Messaging or I need to download Tmobile messaging.
I don't follow it but I don't believe ATT/Verizon are even going to roll out RCS, I believe they have their own implementation coming (somedayTM). Unless their "Advanced Messaging" is just RCS. Will that work with Tmobile users? Or will it just be between ATT customers?
I have plenty of other complaints about Android lately. Privacy, per-app notifications are a mess.
I LOVE the customization of Android and the lack of it is what I dislike about IOS but I'm to the point where I just want a smooth UX.
edit: Before I get the "Use Whatsapp/etc" that's just not an option. Google Hangouts was SOMEWHAT ubiquitous between my friends a few years ago and was great but if I'm taking pictures of my house for a contractor, or shooting pictures of my Jeep offroading to random Jeep friends and what not I'm not going to go "Are you on WhatsApp?" each time. I know these limits are because of carriers and not Google/Android specifically.
Yes, it's called iMessage.
He also hasn't really ditched Android yet, since his iPhone hasn't even been delivered yet.
I don't get the point of this blog post.
Be smart, pick up an old Blackberry 10 device and use its Android emulator.
And here's the crux of why I just don't bother, then again it's not really that big of a deal to me that I'm the "product".
I'll probably regret it some day, but I'm hoping that I won't.
The author clearly did not evaluate all of the alternatives, and simply jumped from one walled garden to another.
Bloatware, adware, and battery life are cited as his reasons. But he could have rooted his phone in 5 minutes then deleted all the bloatware and google apps in an instant. Add microG and adaway on top, and you have a nice ad-free system with much better battery life.
All he had to do was research.
And that's the problem. One platform offers, mostly, sane defaults with strong privacy guarantees and no bloatware, the other requires you to invest time and effort, first to research, then enact.
This can change any day. And if you think that's impossible, look at Windows or Google Chrome. Most users just will happily trade privacy for convenience.
> the other requires you to invest time and effort, first to research, then enact
This is classic learning curve = bad. Rust is also harder than JavaScript, and Vim is harder than Notepad. What matters is whether its worth it.
Some people don't see a problem with being at the whim of a megacorp and not having true ownership of their devices. That's normal. After all, Chrome and Windows have huge marketshare too.
Putting all the eggs in Apple's basket is near-sighted at best.
It can, but seeing as Apple have staked the farm on running things locally and respecting privacy as a USP it's doubtful. I'll take "privacy protecting today, but maybe in the future I'll have to switch" over "I'm the product" any day of the week.
And yes, a learning curve CAN be bad. There is so much conflicting information in this thread alone that shows shorting the wheat from the chaff is not easy, and at best people might buy into snake oil solutions, at worst be in a less secure state than they otherwise may have been before.
- calling
- texting
- taking pictures
- occasionally recording sound
- music
- directions
- occasionally, an alarm clock, a calendar and notes
- web surfing is a nice to have and I use it now that I have it.
- the ability to run a Debian Chroot and an X server is a nice to have.
Lineage 15 (soon 16) with latest updates, without Google apps does that brilliantly well, and I get a solid 6 to 10 days of battery life.
No emails (but k-9 mail works well if needed, and the webmail too), no chat. Chat would be possible (and I will probably want that in the future) with many applications like Signal, Riot, Conversations, maybe even WhatsApp (I haven't tested - not interested).
Directions with OsmAnd gives me great offline functionality, allowing for a 2€/month phone plan.
I get all notifications I want in a timely manner, which are texts and calls. No more.
edit: Oh, and installing apps without the phone needing any email address.
On iOS, I would not have such a freedom.
Next step: a blob-free phone, or no phone at all.