Most of this article doesn't only apply to Telegram+ -- it just happens to be an example that got a lot of coverage elsewhere, with many authors or commentators putting the full blame on Google, Telegram, the Telegram+ developer or even WhatsApp Inc (eh?). In this article, we'll try to look at the different aspects to provide a clear view of what actually happened, and what can (and hopefully will) improve with regards to developers in general and the Play...
Safe Kernel for AOSP-Based ROMs on the Epic 4G Touch
For those who haven’t heard, there have been some issues with Samsung ICS leaks and brick bugs. The Samsung Epic 4G Touch was no exception to kernel- and recovery-related issues. When CM9 ROMs were were first coming out on the Epic Touch, they didn’t come with a custom recovery. To flash to a different ROM, users had to flash a Gingerbread kernel containing the proper ClockworkMod recovery, and then use that recovery to flash to a new ROM. This is because the kernel being used suffered from similar issues as the hard brick bug on other Samsung devices. Thus, it meant that trying to wipe and flash a different ROM could result in a hard brick. That problem is now solved.
XDA Recognized Developer chris41g along with XDA Senior Member FranceIsBacon are currently building AOSP-compatible kernels with patched ClockworkMod recoveries. To put it more simply, they have disabled the emmc_cap_erase, which has been identified as one of the big troublemakers in the whole brick bug debacle. The purpose of this is to allow users to flash an AOSP-based ROM, flash their kernel, and then use that recovery to flash to whatever else they want without fear of bricking their devices.
Currently, the kernels are considered to be in the testing phase. They do work and users have reported as much, but none of them are good enough for Chris41g to declare stable. On top of being for AOSP-based ROMs and having a patched recovery, the kernel also has a number of other features including:
So if you’re running AOSP-based ICS ROM on the Epic Touch, you may want to look further. Those interested should head over to the original thread.[Thanks goes to XDA Elite Recognized Developer Entropy512 and XDA Developer Admin / Elite Recognized Developer pulser_g2 for the consults regarding the brick bug.]
Want something on the XDA Portal? Send us a tip!
Ever since custom recoveries and roms became popular, nandroid backups have been the fall back method for all android enthusiasts, irrespective of their confidence levels. They allow easy backup and restore in case things go wrong, which happens invariably when a modification is being tested. With that being said, how relevant are Nandroid Backups to this day? Back in 2011, when the world of Android was being awed by the likes of the Samsung Galaxy S2, a little modification made its appearance...
While HTC's latest flagship brings many new features, the aesthetic design of the device remains largely untouched in comparison to its predecessor. Many Android enthusiasts throughout the community were expecting a large redesign of one of the most beautiful handsets ever released, but what we got is something more along the lines of an 'HTC One M8S". So this begs the question, is the M9 worth the upgrade if you already own the M8? Current HTC One M8 users chime in and let us know your thoughts.