Skip to main content

RE: Android Orphans: Visualizing a Sad History of Support

Source: theunderstatement.com/

A very good summary about Android environment. Very well summed-up and visualized the two rival ecosystem.

Root of problems - Hardware Manufacturers

Android suppose to be an open source project.By the default nature of an open-source, it is bound to lure all the hackers around the world to get their hands dirty on the project. Yet hardware manufacturers tries very hard to be in control of both the hardware and the software (firmware).
".. there’s no incentive for smartphone manufacturers to update the OS: because manufacturers don’t make any money after the hardware sale... The hacker community (e.g. CyanogenMod, et cetera) has frequently managed to get these phones to run the newer operating systems, so it isn’t a hardware issue."
Despite realizing that they can't make money after hardware sale, and they are resource tight to keep up with the pace of the OS development, they still want to be in control. They even demanded takedown of the roms [1], which the hackers used to baked their custom rom (firmware).

This IMO is the biggest mistake of all the vendors. They should be grateful there are these fan-boys out there that help improve the products and user experience. If not for these fan-boys, many would have left Android for other OS, such as iOS.

And to some extend, Google itself also demanded takedown of CyanogenMod [2], despite their tremendous effort in help keeping the Android devices up-to-date, and perform better, with the lag-fixes, memory management fixes, and performance tweak.


Openness of Open-source.

Nuff said, if I'm part of the mass non-it-savvy consumers, I would been stick to iPhone long time ago. But, because I enjoy hacking my own products. That's why I sticked to AOSP.



References:
  1. http://www.phonenews.com/htc-now-demanding-takedown-of-unmodified-rom-archives-11464/
  2. http://phandroid.com/2009/09/25/google-responds-to-cyanogen-uproar/

Comments

Popular posts from this blog

225019099301.apps.googleusercontent.com

Recent activity on my Gmail just revealed that there's this app "Authorized Application (225019099301.apps.googleusercontent.com)" from IP address 54.235.159.144 assessing my Gmail.

The IP address is from a Amazon server ec2-54-235-159-144.compute-1.amazonaws.com. (IP Lookup).

And blacklist check (http://whatismyipaddress.com/blacklist-check) shows that the IP is clean too.

Clicking on the "Manage Account Access" didn't give any information on the application "225019099301.apps.googleusercontent.com".


After Googling, it appears that the app is Mailbox (source: http://productforums.google.com/forum/#!topic/gmail/9LVW_etXyTE)

To make things easy, Google should show the applications with their ID.


Backup MySQL to Azure Storage in 30 Seconds

Step 1. Disable password prompt for "mysqldump command"mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password: NO) when trying to connect 1. Run "vi ~/.my.cnf"
2. Add the following lines

[mysqldump]user=mysqluser password=secret
3. For Bitnami, you'll need to append the following line in "/opt/bitnami/mysql/my.cnf"

!include ~/.my.cnf
4. Try running to see if the command works.
mysqldump --all-databases > /home/bitnami/backups/db-backup.sql



Step 2(a). Install Azure-CLI Prerequisites: Installing npm.sudo apt-get update sudo apt-get install nodejs sudo apt-get install npm Note: If you facing issue while installing nodejs/npm on Ubuntu 12.04, you can refer to his article for alternative way to install https://rtcamp.com/tutorials/nodejs/node-js-npm-install-ubuntu/, or this http://stackoverflow.com/questions/16302436/install-nodejs-on-ubuntu-12-10#comment32247107_16303380

Install Azure CLI.npm install azure-cl…

Generate GoDaddy SSL Certificate (.crt) for Azure Websites (.pfx)

Step 1: Getting GoDaddy SSL cert.
Let's say you have a domain name of my_domain.com. You'll first need to generate the the .csr file for GoDaddy with the following command:

openssl req -new -newkey rsa:2048 -nodes -keyout my_domain.com.key -out my_domain.com.csr


This gives you 2 files:
my_domain.com.key - This is the private key
my_domain.com.csr - This is the Certificate Signing Request


Copy the content of my_domain.com.csr file to the SSL signing authority (GoDaddy).



Once approved, GoDaddy give you back a .zip file with the following 2 files:

18f1c77f369c0b59.crt - This is your cert
gd_bundle-g2-g1.crt - This is the GoDaddy Certificate Chain


Step 2: Convert a CERT/PEM certificate to a PFX certificate
openssl pkcs12 -export -out my_domain.com.pfx -inkey my_domain.com.key -in 18f1c77f369c0b59.crt


Step 3: Certificate to Upload to Azure.


Step 4: Assign SSL Bindings.




Step 5: Done!


References:

http://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate…