I would say that we will miss the AOSP browser but we would be lying to you.
When I first got into developing and compiling Android, the AOSP browser I think was at it’s prime. It was getting updates from Google and many hobbyists around the community were still contributing to it. Those days are long gone with no light at the end of the tunnel.
Those that keep up with AOSP know that Google has slowly started to abandon AOSP apps in favor of their closed source alteratives. These apps include Browser, Music, Gallery2 and Calendar. While we would love to continue in putting lipstick on a pig and “materialize” these apps for future versions of Android, it’s taken a lot of out of us. In the end, these apps look nice but they still lack functionality.
Many developers have simply removed these apps from their ROMs and that’s a choice that we considered and for a while, was a very likely option.
We’re happy to say that for the browser app within DU, that’s no longer an option.
Thanks to the efforts of Team EOS developer Anders Nielsen, we can rest easy in knowing that we’re not only replacing the AOSP browser but replacing it with an open source alterative. One that’s being actively developed and in turn, get better with time.
If you have not put the pieces together, we’re talking about Google’s Chromium!
Oh ok, so is just like Google Chrome right?
In a lot of ways, that is correct. Google pulls a lot of their own code from Chromium to create Chrome.
Below is a small list of differences for those wondering
– Colorful logo
– User metrics are reported
– Video and Audio codecs (AAC, H.264, MP3, Opus, Theora, Vorbis, VP8, VP9, and WAV)
– Sandboxed PPAPI (non-free) Flash plugin included in release
– Code is tested by Chrome developers
– Sandbox is always on
– Single deb/rpm package
– Profile is kept in ~/.config/google-chrome
– Cache is kept in ~/.cache/google-chrome
– New releases are tested before being sent to users
– Google API keys are added by Google
– Sucks all the ram out of anything……is a black hole
– Blue logo
– User metrics are never reported
– Video and Audio codecs (Opus, Theora, Vorbis, VP8, VP9, and WAV by default)
– Supports NPAPI (unsandboxed) Flash plugins, including the one from Adobe in Chrome 34 and below
– Sandbox depends on the distribution
– Packaging depends on the distribution
– Profile is kept in ~/.config/chromium
– Cache is kept in ~/.cache/chromium
– Doesn’t suck as much….
You said it was open sourced, so why is it a prebuilt apk?
Those that have ever attempted the task of compiling Chromium from source know that is not something that you could compile inline with a ROM.
Syncing close to 14GB worth of source is a bit intimidating when you consider, this is just a freaking browser. Those that want to compile it from source are more then welcome but we chose not to and take the welcomed help from Team EOS.
In the coming weeks, don’t be surprised if we replace more of these abandon apps.
Again, thank you for your continued support and patience!