Hacker News new | past | comments | ask | show | jobs | submit login

There is no need of nor no sense in going to Apple to be rid of corporate control, Android can be tamed to serve the device owner instead of its manufacturer and distributor. Make sure to get a device which is supported by one of the AOSP-derived distributions, install said distribution and use one of the alternative repositories (FDroid being a good choice). Don't install any Google-specific apps, don't install - or remove - Google Play Services, in short don't play along with Google's game plan. This way you can have a device which serves you and your needs instead of those of Google or Apple. You might need to forego on the latest app craze because those are not available on FDroid but that just gives you so much more time to do other things instead of search for virtual fame and fortune by herding virtual sheep or finding virtual friends.



Which part of the "regarding general public" did you not understand?

Of course as I geek I can do all of that, but I rather sponsor someone that cares about the joe and jane on the street can do with their devices.


The general public part of the problem can be solved by offering an alternative Android-based distribution which can be installed by 'the general public' in a way similar to that which they install updates to the stock OS. For some devices this process is already available, for others there is more work to be done.


I have a certain amount of hope in that direction because of Project Treble.


Leave all hope ye who enter.

Project Treble[0] only enforces a certain level of hardware requirements.

There are zero requirements for OEMs or carriers to actually push updates to their devices, and they are still allowed to customize their forks. [1]

Also it requires consumers to buy a new device running Android O, hoping that the OEM will actually push updates, because even those getting an update from Android N to O won't have any guarantees of further updates.

[0] - https://source.android.com/devices/architecture/treble

[1] - http://androidbackstage.blogspot.de/2017/08/episode-75-proje...


I don't count on OEMs in any way. However, if my understanding is correct, Treble should make it far easier to install an aftermarket ROM on a Treble-compatible device.

When I shop for my next phone, "Treble-compatible" will be the top requirement.


Assuming the boot loader is unlocked.


There are alternatives to unlocking the bootloader. My current device (a 2011 Motorola Defy) can not be unlocked yet still I'm running it with Android 4.4.4 on a custom kernel. The trick here was to subvert the update process, other ways exist to do the same.


Which is something non-technical users can't do.


Which is a business opportunity for technical users.


Make sure to get a device which is supported by one of the AOSP-derived distributions

Which devices and which distro's ?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: