Android users who are running CyanogenMod 10 or CyanogenMod 10.1, and probably many other custom ROMs, looking to clean up their device’s display by getting rid of the notification bar now have an option to achieve that goal. Best of all, the solution ensures the user can still swipe down from the top edge of the screen to get access to their notifications. This feat was accomplished by XDA Developers forum member enryea123 through some tweaks to the SystemUI.apk and framework-res.apk files. According to enryea123, this solution will eliminate the ability to pull down the notification bar from the lockscreen. All of the changes can be undone just by restoring the stock apk files.
The guide that walks you through the process can be accessed on the XDA forums using the source link below.
source: XDA Developers Forum
I’ll admit it; I’m a flashaholic. The only problem is that I don’t like that each nightly update is at least 150MB for my particular device. Even though I have unlimited data, it’s still not cool to either wait a while for the latest update to download via my carrier (non-LTE) or having to wait until I get home to do so via WiFi. Granted, this is probably not an issue to most, but if you like your nightlies, then you’ll definitely like this little gem of an app called CyanDelta which makes managing those various CyanogenMod updates a much more easier process. Hit the break to see how you can grab your precious updates without using up too much data.
With stable builds of CyanogenMod 10 being released yesterday to a select devices, more devices should start seeing support as the days go on. Today the U.S. Samsung Galaxy S3, Galaxy Note (1 and 2), HTC One X and S, and Sony Xperia T are now supported, among many others. If you’re curious about your device and if the CM team supports it, you can check out their website for further details.
In other news, with Android 4.2’s source code dropping yesterday, you can expect developers like CyanogenMod to quickly get their hands on that code and start working on their custom version of it. The CM team has revealed that it will be dubbed as CM10.1, rather than a whole new number such as CM11. Since Android 4.2 is still technically Jelly Bean, the team didn’t feel the need to bump the number up to 11. That will probably be saved for the next iteration of Android (Key Lime Pie perhaps?).
Check out CM’s official statement on the matter after the break!
Those of you who have been looking to get some Jelly Bean lovin’ courtesy of the CyanogenMod team will be all smiles at this news. The CM team has officially announced the final CM10 stable builds are being released for a handful of devices at this time. The lucky devices to make the first cut at the Sprint and Verizon Galaxy S III, Samsung Galaxy S II LTE and LG Optimus Black smartphones. Unfortunately those devices are the only ones with a stable CM10 build as of now and there is no timeline for when other devices can finally taste the stable goodness just yet. Hopefully the CM team will work its magic and roll out additional builds to the other devices sooner than later.
source: CyanogenMod Downloads
via: Android Police
We told you about the CyanogenMod (CM) 10 Updater a couple of weeks ago and we wanted to revisit the nice feature that the CM team included. Not so much a review, but an update as it’s simply a feature of a full-fledged ROM. The CM team was very quick about releasing this feature after they initially announced it. It was actually a feature found on a few previous versions of CM ROMs, but it’s been a while since CM users have been graced with this convenient feature. Granted, some may not feel comfortable trying something new or jumping back to a way they used to update their ROMs, but the feature is very convenient and at least worth a look if you’re running CM10 on your device.
For those of you that roll with a custom CyanogenMod 10 (CM10) AOSP ROM, today’s Nightly release (Oct. 10) comes with a slew of merged updates, including bringing your device up to Android 4.1.2. Those fine folks over at CyanogenMod sure do work quickly. If you remember, it was just yesterday that 4.1.2 was released to AOSP and began rolling out to the Nexus 7 via OTA.
Unfortunately we were only hit with the requisite “improves performance and stability and fixes bugs” change log from Google, and pouring through all that developer jargon in the official commit logs can be daunting in figuring out what has been changed or updated. Additionally, it’s still a little early to gain any takeaways from real-world testing of 4.1.2. However, based on a few lines in the commit logs we can see that one particular bug in 4.1.1 with “failing to connect to WPA enterprise wireless” has been addressed in 4.1.2. There also seems to be a few mentions of the browser, audio, camera, the kernel itself, and a slew of other updates.
If you’re on a recent CM10 release (within the past week), you can grab today’s release containing 4.1.2 from right there within your ROM by navigating to the CM Updater (Settings > About Phone > CyanogenMod updates). Otherwise you can grab it from your favorite source. If you’re new to the CM10 custom ROM scene and like what you hear, you can navigate to their site to read up on their AOSP custom ROMs for a multitude of devices.
Well, that was quick. After the CyanogenMod team announced they would be bringing a new OTA update solution to CM users “soon”, we didn’t think “soon” would be a matter of days. That’s exactly what has happened as the CM Updater has officially gone live for CM10. In case you’ve forgotten, this new updater will periodically check for updates and if an update is available, install it as needed.
This new feature is available now for those with the latest CM10 nightlies, so if you’re on that build, head on over to Settings > About Phone to configure you’re own settings and preferences. Now that this achievement is done, let’s keep our fingers crossed that we see something like this soon for those of us with earlier builds of CM ROMs.
The CyanogenMod team has formally announced that official CM10 nightlies will be available starting tonight. For rooted users, this is Christmas time as CM ROM’s are the current king when it comes to the Android modding community. The devices receiving the CM10 nightly treatment will include, but are not limited to:
- The US SGS3 variants
- The Galaxy Nexus variants
- The Nexus S varaints
- The Nexus 7
- The Transformer and Transformer Prime
- The SGS1 variants (Vibrant, Captivate, International, and i9000b)
- The SGS2 i9100g
- P3 and P5 tablets
According to the CM team, “Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.”
Just keep in mind that you, and you only, are responsible for anything that were to happen to your device if you decide to delve into flashing custom ROM’s. With that said, enjoy and let us know your experience with the CM10 nightlies once they become available later tonight!
source: CM’s Google+ Page
Sure the original HTC G1 is the ancestor of all Android phones, but it doesn’t mean it can’t be brought in today’s world. XDA superstud Jcarrz1 was able to bring some Android 4.1 glory to the G1 by bringing a buggy, but functional port of CM10, just like how he brought Ice Cream Sandwich to the smartphone last year. In addition, the awesome Google Now is also working in a functional capacity— while WiFi is working at full capacity (though cellular data isn’t). Jcarrz1’s achievement just shows that contrary to what OEMs want you to believe, users can have the latest software on their Android devices.
Interested in checking out more details or giving the port a try on your old G1? Hit the source link to find complete information of the details.
source: XDA Forums