POSTS TAGGED: Samsung Galaxy Nexus
Posted November 6, 2014 at 11:00 pm by Tomek Kondrat
Just yesterday, we talked about some early bird builds of Lollipop for several devices. Those builds all have one thing in common: They were made for devices with working AOSP device trees that have been provided by their manufacturers. This time, we want to showcase one of the first AOSP Lollipop ROMs for quite an old device, the Samsung Galaxy S III Mini.
Ironically, the S3 Mini’s bigger brother (which uses a different SoC) hasn’t received an official version of KitKat due to RAM limitations. XDA Senior Members New Macław and marcin1147 proved that Lollipop can work on the aforementioned Samsung phone. At the current stage of development, the S3 Mini Lollipop build can’t be considere. . . READ ON »
Posted October 8, 2014 at 09:30 am by Will Verduzco
Nearly one year ago when Google disclosed that the Samsung Galaxy Nexus would not get to enjoy Android 4.4 KitKat in official capacity, many were understandably upset. This device, which is still packs a relatively decent punch in the hardware specifications department, was more than capable of handling the latest firmware. In fact, at the time of KitKat’s release, the company touted that the increased optimization and decreased hardware requirements in Android 4.4 would help limit platform fragmentation.
While many were upset at Google, others quickly saw that the most likely reason as to why the beloved GNex would miss out was because of the lack of chipset drivers following TI’s exit . . . READ ON »
Posted September 2, 2014 at 11:00 pm by Tomek Kondrat
webOS has had rather turbulent history. Initially developed by Palm, the Linux kernel-based operating system has never found had an easy time making its way to mobile devices. However, and what may come as a surprise to many reading this, development work on the platform is still well underway. There are even working ports for some of popular devices like the Google Nexus 4, Nexus 7 (2012), Samsung Galaxy Nexus, and the long since forgotten HP Touchpad.
The project for mobile devices was renamed LuneOS. And like its predecessor, LuneOS remained open-source. As of now, not many things are working like they should, but the team standing behind the OS put lots of efforts to eliminate the current fl. . . READ ON »
Posted February 3, 2014 at 06:00 pm by Tomek Kondrat
Imagine that you’re flashing the latest nightly of your favorite ROM. If you are performing a fresh install by wiping all of your data, this also means that you have to flash all of your modified system apps, user apps, modules, and so on. And if you’re doing this on a regular basis, all the wasted time really starts to add up. So what do you do? Do you manually install these apps again, or do you add them to your favorite ROM? One of the better solutions is to use Aroma Installer by XDA Recognized Developer amarullz. However, you normally need some experience to configure it properly.
Posted December 26, 2013 at 04:00 am by Will Verduzco
As you’re making your way down the list of things to try with your newly acquired tech toys, one thing you’ll undoubtedly get around to is flashing a custom ROM. Those looking for aftermarket firmware now have one more Android 4.4.2-based option, as the AOKP team has just finished incorporating Google’s latest and greatest into their nightly builds.
Currently, Android 4.4.2-based nightly builds are available for the Google Nexus 5, Nexus 4, Nexus 10, Nexus 7 (2013), Galaxy Nexus, Galaxy S III, Galaxy S 4, HTC One, Xperia Z, Xperia ZL, Xperia T, and Xperia V. More devices will be added to the nightly list as soon as they’re ready. The AOKP team recommends a full wipe when installing the l. . . READ ON »
Posted December 5, 2013 at 07:30 am by Tomek Kondrat
The Samsung Galaxy Nexus was the first device to run Android 4.0 Ice Cream Sandwich. It was also the pride of Google and Samsung for a long time, and it still has quite a few stalwart fans. Good technical specification for its era combined with a then-amazing Super AMOLED HD screen equate to a device that is still more than adequate for most tasks. Unfortunately, Google chose to not bestow an official KitKat update on the device, leading many to speculate that this was due to TI’s exit from the mobile SoC industry.
A few weeks ago, we wrote about early KitKat releases by the Slim Team and XDA Senior Member Grarak, but a few things still needed to be polished and worked on. After few weeks, the GNex can join . . . READ ON »
Posted November 24, 2013 at 10:00 am by Tomek Kondrat
Android is six years old now. One week ago, we presented the first part of the Android story. Now, it’s time to continue the journey.
A long time ago in a galaxy far, far away—located in Mountain View, the first version of the operating system dedicated for tablets was born. Google called it 3. 0 Honeycomb and presented it alongside the Motorola Xoom.. . . READ ON »
Posted November 8, 2013 at 07:30 pm by Will Verduzco
We first heard that the Samsung Galaxy Nexus would not be receiving the Android 4.4 KitKat goods when Google announced that the device fell outside of the traditional 18-month window for firmware updates. Many figured, however, that the underlying cause of this was not Google’s choice, but rather TI’s exit from the mobile SoC market—and of course, the subsequent lack of Android 4.4-compatible driver binaries for the OMAP4460 used in the device.
Despite the driver setbacks, we’ve seen highly functional, source-built Android 4.4 ROMs pop up for the GSM Galaxy Nexus (maguro), as well as for the Verizon CDMA/LTE variant (toro). The only thing left in the way of a ha. . . READ ON »
Posted November 8, 2013 at 04:00 am by Will Verduzco
When it was discovered that the Samsung Galaxy Nexus would not be getting an official build of Android 4.4 KitKat, many of the device’s loyal users were understandably upset. After all, the Galaxy Nexus is still a competent device today, almost two years after its November 17, 2011 release date.
Despite Google’s claims that the Galaxy Nexus fell outside of the typical 18-month support window, many were quick to attribute the missing update path to TI’s exit from the mobile SoC market, and the subsequent absence of drivers for the latest version of Android. This very issue has been the source of various graphical glitches seen with early, unofficial builds for the GSM and Verizon varia. . . READ ON »