Earlier today we reported on some members of TeamHacksung expressing an unwillingness to develop a ROM for Samsung’s forthcoming Galaxy S 4 smartphone. The news certainly set the ‘net abuzz, but it appears the comments may not be as “official” as originally thought. The CyanogenMod Team has posted on their Google+ page a statement indicating no official position had been established regarding the Galaxy S 4 and that one would not be established until the device was available for retail purchases.
In the posting, the CM team reminds folks that announcements regarding support for devices will be communicated via their official channels on Google+, Twitter, Facebook, or their blog. The CM team also points out the comments from this morning posted by XpLoDWilD were just the opinions of four members of TeamHacksung who do not speak on behalf of CyanogenMod.
Those looking forward to getting CM running on a Galaxy S 4 can breathe a little easier for now.
Itching to grab that new Galaxy S 4 smartphone, but looking for a more stock experience? Well you may be out of luck as it appears that we will not see the famed CM ROM on the device— for now at least. In some rather surprising news, the CyanogenMod team announced that it has no plans to support the device as of this time. Because of the ever-growing conflicts of interests between the various Sammy licenses/kernels and well… the folks who want to
hack tweak things to make the device a little better, the CM team just felt that attaining the Galaxy S 4 just wasn’t worth the trouble. Here’s of XpLoDWilD of Team Hacksung sharing CM’s general thoughts and feelings about the Galaxy S 4:
“Nobody at Team Hacksung (the team behind Galaxy S2, Note, S3, Note2, G Tabs… official CM ports) plans to buy it, neither develop for it. There are two variants which will be a pain to maintain, [and] the bugs we have on the S3 will probably be there on S4, too (camera), and we all know Samsung ability to release sources while staying in line with mainline. Yes Qualcomm releases sources, but Exynos sources we had were far from [working on] actual Galaxy products. I’m pretty sure the same will happen for this one.
That’s a uniform “no” from us.”
Well… alrighty then. Here’s hoping that the CM team will find some sort of compromise and resolution… or that another team out there can step up and provide some of that custom goodness to the masses out there. Otherwise, it may appear that the Galaxy S 4 could possible lose some major luster and appeal.
source: Android Central
Those of you with a U.S. zip code will be able to buy the HTC One Developer Edition around the same time the standard HTC One is released in the U.S. The Developer Edition features an unlocked SIM and bootloader right out of the box, but everything else is the same. As far as radio frequencies, you get HSPA/WCDMA: 850/1900/2100 MHz, GSM/GPRS/EDGE: 850/900/1800/1900 MHz, and LTE: 700/850/AWS/1900 MHz (US). Unfortunately you won’t be able to grab this one on contract as it will run you $649 and quantities will be limited.
Fantastic news for HTC One X owners tired of waiting for the Android 4.1 Jelly Bean OTA…your wait is over! Assuming you were patient and are still running the stock firmware, you can now download it to your handset and update it yourself.
To install the update on your stock device (AT&T version ONLY), simply:
Remember that leak of Android 4.2.2 (JDQ39) we saw over the weekend for the Verizon Galaxy Nexus? Well thanks to a little help from XDA member oldblue910, the download is now available for you to install. Now it’s unlikely that this is the final version of the build, but that doesn’t mean you can enjoy a little 4.2.2 goodness. You don’t need to be rooted, but if you are, you need to be running 100% stock Android 4.1.1 (JRO030) in order to apply the update.
Uh oh— it looks like Samsung’s Galaxy Note II may have security flaw. While operating a G-Note II with Android 4.1.2, Terence Eden, recently discovered that the homescreen can actually be accessed by pressing the “Emergency Call” icon, followed by the ICE button and finally pressing the physical home key for several seconds. Although the homescreen does appear for a short period, it is enough time for any hacker to actually click and open one of the homescreen apps— which is especially bad if one of the homescreen apps performs an action at launch (think of a direct dial widget that can make phone calls for example). All of this can certainly cause major issues for owners that may end up with their devices falling into the wrong hands.
Unfortunately Samsung has yet to comment, but we’ll be sure it will want to patch this
potentially major little snafu as soon as possible.
What would the internet be without hackers hacking things? Not a day goes by where some hacker somewhere is attempting to access secure or private information. Well it looks like the Evernote Operation’s and Security team discovered they they were at the receiving end of suspicious computer activities. Although personal content nor payment information looks to be affected the investigation does show that Evernote user information (usernames, email addresses associated with Evernote accounts and encrypted passwords) were obtained. While this is worrisome in itself, files containing said user information is encrypted. However rather than rely on just that the Evernote team is playing it safe and requiring that you head on over to evernote.com to reset your password. In the process they also would like to remind everyone the importance of keeping your password secure:
“There are also several important steps that you can take to ensure that your data on any site, including Evernote, is secure:
- Avoid using simple passwords based on dictionary words
- Never use the same password on multiple sites or services
- Never click on ‘reset password’ requests in emails — instead go directly to the service.”
So if you’re a Evernote user then head on over to their web site to change your password. Hit the source link below to read the full post. It’s great to see a company be proactive about their security. I don’t know about you, but I’m going to go reset my password right now.
One of the features from Android 4.2 Jelly Bean that consistently scores interest from consumers is the camera app and specifically, the PhotoSphere function. Although Google has made some pieces of Android 4.2 available as standalone apps that can be installed on 4.1 devices, the camera has not been one of them. This means users that really want the new camera, including PhotoSphere, have to root their device and go through some manual steps to get the camera running on their 4.1 Jelly Bean powered devices. Developer Matthias Bosc has developed an app to make installation of the Android 4.2 camera app much easier and it is now available in the Google Play Store.
By now we’re sure you’re all well aware that it’s now illegal to unlock a device for use on another network. Well, enter the FCC into the fray. They have stepped up to look out for our best interests, so it appears. The FCC will begin their investigation on whether this law is actually harmful to market competitiveness and thus hindering innovation.
Prior to the ban that went into effect on January 26, users were free to unlock their devices for whatever reason they wished. Now that same act will result in legal ramifications. FCC chairman, Julius Genachowski, mentioned that he’s not quite sure of his authority in this situation, but he did say that he will try to use his platform to reverse the decision. Let’s hope Mr. Genachowski chalks one up for the good guys.
You may not be able to get your hands on a Sony Xperia Z quite yet as it is just starting to trickle out to some international markets, but when you do, instructions are already available for those who want to root their new device before doing anything else. Gaining root access has been accomplished by XDA forum member DoomLoRD using a modified root file he had for a Google Nexus 4. After some modifications, and with the assistance of some other developers, the new file for the Xperia Z is ready. If you hit the source link for access to the necessary files and instructions, you might note that DoomLoRD achieved this remotely as he does not yet have the device himself.
If you do get an Xperia Z and want to go down the root path, keep in mind you are taking some risks in unlocking the bootloader and flashing a new kernel on your device.
source: XDA Developers Forum