While all evidence that the 4th iteration of the original Droid pointed at a December release it was pushed back to February of 2012 and a lot of folks became a bit grumpy. Well it’s finally February, the Droid 4 has been officially announced and is upon us. Released yesterday it didn’t take long for the development community to root the device. Security Researcher Dan Rosenberg was able to get root only hours after the device went on sale. However, before he released the exploit he decided to try an experiment.
He would only release the exploit if a $500 bounty was met. This bounty though, wasn’t an attempt at holding a file hostage to make a quick buck but rather, for a good cause. He wanted the first $200 so that he could continue modding and developing support of the device. The other $300 would be donated to the American Red Cross.
Personally I feel that this is a noble idea. Seriously, everyone paying a few bucks to get this man a phone to continue custom development on a new device while also giving money to a charity in the process; it’s an honorable concept. Well apparently I am in the minority in this thinking as Mr. Rosenberg received a number of complaints in how this idea was unfair. Worry not, rather than abandon his work and not release the exploit Rosenberg took the high road. He has decided to release the exploit free of charge and any money donated for his hard work will be donated straight to the American Red Cross.
The great thing about Android is that with enough patience and cunning you can get it on just about anything. It appears that this is a continued case as attempts at getting Android to run on Nokia’s N9 have been successful. Modders were successful in loading Ice Cream Sandwich on the MeeGo phone. Thanks in part to Alexey Roslyakov, the NITDroid project builds on previous work that ported Android to the Nokia N900.
Even though this MeeGo phone saw its share of love from fans Nokia quickly shifted focus on Windows Phone after their deal with Microsoft. This phone is able to dual boot both Meego and Android and can easily be done by pressing the volume-up button during boot to load Android rather than MeeGo. If you are interested in reading the progress on this active development you can hit the source below.
The biggest issue at the moment is getting N9′s hardware to cooperate with the functional Android Kernel. Getting OpenGL to work is an ongoing issue as well. However, progress as been made and here’s hoping we see some more progress made in the near future!
Google’s new bouncer-service that was announced last week is supposed to have dropped the number of malware apps in the Android Market by about 40% already. While that is a great number the Bouncer service isn’t perfect and it probably is the beginning to one of many back and forth battles between the Search Giant and malicious hackers in the making.
However, it appears that hackers may have already found a work around to this service. According to North Carolina State University professor Xuxian Jiang, he and his team have discovered a new malware variant that pulls off a pretty sneaky maneuver. The malware contains no malicious code when it’s first installed on a device. By doing this it evades scans or permission requests that could pick up on its intentions in the first place. Here’s the trick. After it’s downloaded the app is then able to download new code from a remote server and it can hide this in the data transfer from the phone’s communications.
For those of you who don’t know Google dropped official “developer device” support for the CDMA (Verizon) version of the Galaxy Nexus last week. While a statement was released explaining why, it apparently required further explanation as it wasn’t officially explained in full as to what this drop actually meant. So without futher hesitation here is what the official Google Group’s post has to say:
This is a big day for ROM developers everywhere as Xiaomi, a Chinese technology company, has open sourced its MIUI ROM for Android. For those that live under a rock, MIUI gives Android an iOS flair in both look and feel and is based on both Android 2.3.7 and CyanogenMod 7 sources. MIUI 4 (based on Ice Cream Sandwich) is even being toted as extremely stable on the Galaxy S II. You can check out our review on an earlier version here. It’s even safe to say that it’s one of the more popular ROMs out there.
If you are wanting to take a stab at the code you can swing on over to the Github where you will find several application and ROM source codes uploaded. While it may not be all of them you can certainly bet we’ll see more source codes pop up in the near future. Enjoy!
- File Explorer
- Sound Recorder
While most of us aren’t surprised by this move, I’m certainly not, Google has dropped official support for the CDMA (Verizon) Galaxy Nexus as a developer device. They did the same for the LTE Xoom and Nexus S 4G as well. At first folks thought was in regards to Google Wallet not being officially supported by Verizon however it was for a more in depth reason. It was first discovered by Droid-Life earlier this afternoon and while everyone was in a buzz and crying foul about the change, what we needed to do was wait. After many tech blogs reached out for comment, Dan Morril, an Android engineer had this to say:
Hello! This is a quick clarification about support for CDMA devices.
For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called “platform” key. However, when an individual creates a custom build from the AOSP source code, they don’t use the same signing key as these CDMA flies were signed with.
The result is that these files don’t work properly, and pure AOSP builds running on these devices can’t place calls, access mobile data, and so on. Because we aim to make sure that we are as clear as possible about the degree of support that devices have, we updated the docs over at source.android.com to reflect this reality.
We will still make available as many as possible of the closed-source binaries for these devices, and Nexus devices will continue to have unlockable bootloaders. And, of course, GSM/HSPA+ devices are still supported, as are any other devices we’re able to support. We’ve simply updated the documentation to be clearer about the current extent of CDMA support.
We are of course always working to improve support, and we’ll keep everyone updated as we make improvements. Thanks as always for your interest in AOSP!
Samsung just pushed out the kernel source code for AT&T’s version of the Samsung Galaxy Note. There are three different versions listed for download at Samsung’s Open Source Release Center. Why three, you ask? Your guess is as good as mine at this point, but according to one developer, they are almost all identical save for one line of code. Any guesses? Now, lets see what the talented dev community brings to the table once the device is actually released.
source: Android Police
via: Samsung Open Source Release Center
So if you haven’t realized from my posts by now, I like to experiment with Android from time to time and today was one of those more special days. While poking around FaceLock.apk, which I decompiled with apktool, I opened this. The screenshot above portrays a file “arrays.xml,” which contains what looks like phrases to be presented on the lock screen when a user’s face is not recognized. As those of you fortunate enough to run ICS know, currently an unrecognized face only returns “Sorry, don’t recognize you” or in some cases “Couldn’t find a face.” Aside from a different spelling of “recognize,” the list above also offers a substantially more varied output. So what is the meaning of this? I supposed it could be simply leftovers, never scrapped before release, or, letting my optimistic imagination run just a little bit, perhaps this is some preliminary work towards a future update; Majel maybe? It’s a stretch, but the varied and pretty casual responses seem more AI like to me. In any case, an interesting little something indeed.
There’s great news for those loyal fans who stuck with their Sprint CDMA Nexus S 4G
handsets instead of running over to Big Red and snatching a Galaxy Nexus
. The incredibly talented folks over at XDA managed to get the Ice Cream Sandwich
4.0.4 ROM up and running for the second iteration in the Google Nexus family. The ROM is reported to be in its final stages of testing and offers a few new features and updates. Among them are a new software modem, bootloader
and is now at biuld IMM26. Most if not all of the features are stable and working, including the WiMax radios. Further proof of a new build is revealed by its build date, January 30th 2012. So rest assured it’s not the same build we saw previously. It will be nice for Nexus S 4G owners to be slightly ahead of the curve, as you all know Google has already released the Android 4.0.3 ICS build
for the Nexus S 3G model as well as for a few other devices. If you’re feeling frisky, hit the downloads below and don’t forget to report back any issues you may find. Feel free to report them in our forum
so as to alert other Nexus S 4G owners as well. As always, be aware that you’re doing this at your own risk and the staff here at TA
are in no way responsible if you brick your device. So, in short, know what the heck you’re doing! Good luck and enjoy. For your convenience, we’ve provided all the downloads you need below courtesy of XDA (dev mrxkills). Big thanks goes to the rest of the developers who gave their blood, sweat and tears on tweaking this update for the Nexus S 4G.
Update: For some unknown reason, the dev has been asked to pull this down from the site.
Well it appears that Motorola has heard the development community’s cry for an unlocked bootloader as an article on the Motorola blog suggests that they will be releasing a “Developer Edition” of the powerhouse Droid RAZR sometime soon. The article was posted and quickly redacted suggesting that the news was released a little too soon. If you look at the image below, courtesy of Droid-Life, you can see that the article is dated for the 30th (tomorrow).
Right now the phone is only to be available in Europe but Motorola gives word that it will be seen in the United States. Even though Motorola said they were working on a bootloading solution over a year ago, and again in April of 2011, until now we had yet to see it happen. The only difference between this version of the RAZR and the one out for sale now, is the fact that it has an unlockable bootloader, as the original shipped with a locked bootloader. Otherwise it’s the same ridiculously thin, powerful device.
Right now the blog link in the source is down and you’ll get a “You 404′d it, Gnarly Dude” message. However the folks at Droid-life were able to snag a screenshot of the article before it went down. Hit the break below to check it out. I don’t know about you guys, but this is one heck of a win for the development community and who knows, this may be the start of a beautiful thing. Motorola hardware with unlockable bootloaders… You can’t beat that. Enjoy!