Change logs are definitely one of the most important parts of any release. Be it an app, ROM, kernel, mod, tweak, script, you name it; releasing a change log with each new release allows users to see what you’ve changed, fixed, added, and subtracted from prior versions. Often, it’s the very first developer-to-user interaction, and a well thought out change log can ease the minds of the cautious and give users compelling reason to upgrade. Fans of CyanogenMod nightlies probably know the value of the change logs even more so than most other ORDers, as they receive substantial updates rather frequently.
Enter BBQlog. Released by XDA Senior Member peterperfect along with the team behind the previously covered OpenDESIGN project, BBQlog is a third-party website that gives you the change log for CyanogenMod Nightlies. While many users are asking what is the big deal, as that information is typically already made readily available, the catch is where they pull the updates from. Instead of using CyanogenMod Gerrit, which is the more popular way to show the change log, BBQlog pulls its change log stats straight from the GIT. This means it shows every single little change, unedited. It’s much like buying the “Not Rated” version of a movie. You get the movie, plus all the stuff they didn’t show you in theaters. Additionally, the BBQlog team is currently working on an Android app that’ll push all this information directly to your Android phone.
While it isn’t an official CyanogenMod project, it’s still quite useful nonetheless for users and developers alike. For the link to the website, the full list of credits, and more, visit the original thread.
February 20, 2012 By: Joseph Hindy
Dual booting on Android devices isn’t the newest technology out there, but whenever it gets ported to a phone, it’s a pretty exciting experience. So what does that say about triple booting? That is even more exciting, for one thing.
XDA Senior Member racks11479 has posted a method that will, once installed, allow users to boot into CyanogenMod7, CyanogenMod9 and stock on the Barnes & Noble Nook Color. Simply boot into CM7, then reboot to get into CM9 or power off and power on while pressing N to get to the boot menu for stock.
The process is relatively simple for those who own the Nook Color. You simply follow the same directions you normally would if you were to burn a NookieFroyo SD card from NookDevs.com, which racks11479 has been gracious enough to link to in the process. After that, there’s a short installation process, including an optional install of a Supercharge script, and you’re reading to start triple booting. Additionally, it appears that racks11479 consistently updates the thread and method so you can be sure that what you’re using is current and will likely be updated again.
For those who want triple booting goodness on their Nook Color, you can find download links, the full instructions, change log and all the additional options in the original thread. As per the norm, don’t forget to make a back up just in case!
One of the drawbacks to buying any device that doesn’t have Google Apps by default is the Android Market can be a little frustrating. Sometimes, not all the apps your device can run will show up. Other times, maybe apps you cannot run will show up. In any case, it can be a hassle.
For users of the Amazon Kindle Fire, your Market woes are one step closer to being over. XDA Member enkode has released a method that adds fixes to the Market so that Kindle Fire owners can have a more open experience with it.
The method itself is relatively simple, and easy to do as long as you follow the instructions. First, users are to edit their build.prop file and then install a modified version of the Android Market. The end result is Kindle Fire owners will have more Market goodness available to them than they had previously.
There are a few prerequisites though, to quote the developer:
YOU MUST BE RUNNING CM7
YOU MUST HAVE ROOT
I WILL NOT SUPPORT STOCK!
So you’re going to have to be rooted and running CyanogenMod before this mod will work for you. For those running the appropriate software, if you’d like to try it out, you can find the full instructions, download links and additional information in the original thread. As per the norm, be sure you make a backup before attempting, just in case something goes wrong.
January 18, 2012 By: Joseph Hindy
It’s pretty much apropos for all new and high end devices to get a CyanogenMod ROM of some sort. Most will get CyanogenMod7 and we’ve been following the releases of CyanogenMod9.
Well, XDA members of the Lenovo Ideapad A1 aren’t going to be left behind. XDA Member gmarkall has begun work compiling CyanogenMod7 for the spunky tablet and its users.
It’s still a work in progress and there isn’t a flashable zip for the ROM yet, but based on updates over the last few days, gmarkall is making progress. As the to-do list states:
This is just a beginning of a list, but I think the things that need to be worked on at the moment are:
Modify the Cyanogenmod build to be able to create a suitable update.zip for the A1.
Try flashing the update.zip, see what works, what doesn’t, build a list of non-working things, and then fix them one-by-one.
Since CWM for the A1 doesn’t yet support backups of the ramdisk, it would be handy to create an update.zip to restore the original Lenovo ramdisk.
So for those who are toting the Lenovo Ideapad A1 and can’t wait for CyanogenMod goodness, you’ll want to keep an eye on the original thread for updates and details. Also, for any developers who want to help finish the project, there’s a link for an IRC channel to join for collaboration purposes.
The LG P350, also known as the LG Optimus ME Titanium, is a mid range device that is pretty affordable. If that isn’t enough, it also has received CyanogenMod 7.
XDA Member pax0r has been kind enough to compile the mega popular ROM to this humble device and while the ROM is still a beta, it’s got enough features working to use as a daily driver for some people.
The list of features not working is very short and only includes a small break in the camera where users can’t see previews. However, the camera does still take pictures. This doesn’t mean there aren’t more, as pax0r states:
It’s testing and still WIP release so there still could be bugs.
Before installing, make sure you pick up the LG Optimus ME compatible custom recovery from the link and always take the proper precautions such as creating a full backup. Once you’ve got the proper prerequisites, though, it’s all a matter of installing the ROM.
For additional information, the installation instructions, download links and if you just want to keep updated on the progress, you can find all that and more in pax0r’s original thread.
January 16, 2012 By: Joseph Hindy
CyanogenMod is, at least statistically speaking, one of the most-used aftermarket ROMs of all time and has recently breached an impressive milestone of 1 million active users.
There are inherent things that come with having that many unique users. As XDA-Developers Recognized Developer, and CyanogenMod Team Recovery Guru, Koush has posted on his Google+:
As the project grows, so do our server requirements, hardware requirements, etc.
So, while kicking some ideas around camp, a really cool idea came up: a proprietary CyanogenMod App Store. It’s an easy concept; developers upload their apps to the proprietary store and the CM Team takes a small cut to help pay for server and hardware maintenance. Of course, this is not to be any regular app store and would be targeted for specific niches. As Koush explains:
Apps removed from the Market includes, one click root apps, emulators, tether apps, Visual Voicemail apps, and more. These are all completely legal (Nintendo emulators are fine, ROMs are NOT, there is a distinction).
So, developers would have another app store to upload their apps to and those with pulled apps could possibly give them a second chance at life. Based on threads like this one, a place like that for pulled apps is something some people would definitely love to see.
How do you feel about this? Is this a way to unify apps that are stricken from the Android Market by Google, or just a bad plan in general? Sound off in the comments!
December 30, 2011 By: liwen
There are many CyanogenMod-based ROMs available, but not all are officially supported, that is, listed on their website. In particular, you’ll notice that the Samsung Epic 4G, Sprint’s version of the bestselling Galaxy S isn’t there yet. But that’s only a matter of time now, since Decad3nce, the developer of the CM7 port, announced a few days ago that the “Samsung Epic gets officially forked into Cyanogenmod”.
December 29, 2011 By: Joseph Hindy
Soon, compiling CyanogenMod for your phone will be as easy as opening a user interface and adding a little information. Or at least that’s the plan from CyanogenMod team member, and XDA Recognized Developer, lithid-cm, who has released an alpha version of this powerful new software which will, as the name implies, compile CyanogenMod for you.
As stated, it is an alpha release, so if you’re expecting to download it and start porting CM to every phone on XDA, then you should probably pull the brakes a little bit. The features as it is right now include:
Check for repo installation on startup / or create a repo
Add and remove devices quickly and easily.
Remove all non english languages.
Remove live wallpapers
Remove cm wallpapers
Check if adb is running or not.
Update the repo
Built in color themes. > http://goo.gl/cED8t
Plugin support. (More information on this to come)
Odex plugin built into the package. This will take your connected cyanogemod installed phone and odex the rom on the phone.
And, as expected, there’s still a few problems as well:
There is nothing under the menu option 99. This is a placeholder for information about me and the compiler. If you select it it will just exit you out of the script.
There is no checking for installed software. You will need to install the needed packages on your own to compile. Check post 2 for needed software.
I have only tested this with ubuntu 11.04.
Removing the CM wallpapers from the build only works with gingerbread for now. Everything else is working as expected for me.
I don’t check for open ports on your network, so there might be issues connecting to the repos and syncing. I have not built error checking for that.
With a plethora of features still to be included and some bugs to work out, this beautiful, wonderful and purely awesome piece of software is definitely something the aspiring developer should be checking out. You can find more details, the features to come list, download links and installation instructions in the original thread .
December 28, 2011 By: Joseph Hindy
CyanogenMod is a really great ROM. It’s AOSP, it’s on a boatload of devices and people just seem to generally enjoy it. There aren’t many developers out there who try to make it better outside of a few new tweaks and some custom themes.
The functionality is very similar to the usual version of CM7, so users don’t have to re-learn how the ROM works per say, but the additions are really where it’s at. On top of the CM7 we all know and love, Freedomalfa has also included the following:
Lots of hard work.
Lots of tweaks
Many music enhancements
Many custom apps
Looks somewhat like a mix of ICS nd Sony Ericsson
Includes widgets from ICS and Sony Ericsson
Includes some performance tweaks
Includes some battery saving tweaks
New ringtones,notification sounds,ui sounds
Bravia engine enhancement(Stripped from a sony ericsson rom)
App to sd pre-enabled (Thanx to parasmi for his great tutorial)
3d sound enhancement( U can feel it if u hear through earphones)
A new customized lock screen that looks like the ICS one.
ICS transition animations (Thanks to yagya )
That’s quite a bit of extra stuff and some of it looks downright juicy. So if you’re a audiophile (read: music nut) and want to check out this highly customized ROM, you can check out further details, installation instructions and additional mods at the original thread found right here . But let’s face it, when going CyanogenMod, can you really go wrong?
October 13, 2011 By: azrienoch
Today is turning out to be a rollercoaster of news for the HP Touchpad. Shortly after last night’s article on how HP installed Android on every Touchpad in order to load the component manufacturers’ drivers for testing hardware, the Cyanogenmod Touchpad team announced the first public release of their CM7 alpha. It was over a month ago that the CM Touchpad team posted footage of Android’s first boot on the Touchpad. The result came at a price of hundreds of hours of volunteered time and tireless effort on the part of the CM developers, and we have nothing but gratitude for everything they did.
As the very first public build, the laundry list of bugs and non-working features is so long, it actually does include your socks. If you choose to try it out, be extremely careful to read and fully understand every last word of their disclaimer, Q&A, and instructions in the mirrored thread from RootzWiki.
Next in the lineup of today’s Touchpad news, a fourth Touchpad bearing Android 2.2 turned up today. There were previously only three known devices. One was bought at a Best Buy in Texas, one was bought at a Best Buy in Oklahoma, and the third was bought at a Wal-Mart in New Hampshire. Not much is known about this fourth device. What we know is that it was purchased in Germany, and not just a Touchpad running the CM7 alpha, dressed to look like the others. First, we see the Qualcomm boot animation in the video, just like on the three other Touchpads. It’s speculated that Qualcomm designed this version of Android, as the manufacturer of the processor on the Touchpad. The second reason we know this isn’t a fake is it’s running Froyo, whereas CM7–yes, even in it’s early alpha state–is Gingerbread.
Author’s note: And ain’t that just my luck? In the middle of writing about it, the video was privated. Check back here for updates, I’ll post a mirror if I can find it.
I bought the touchpad on 22nd of august at a store called Saturn in Munich. It is a major reseller in germany, like best buy. There is a so called “HP PN” number on the receipt and it matches with the one on the touchpad. Then on the package there is a sticker with the “HP PN” and the serial number. Both match with the ones on the touchpad. The receipt has got a signature of the clerk on it.
Last thing to round up all the Touchpad news so far today, trsohmers followed up last night’s article by posting the leaked Cypress Semiconductors drivers for the first time to the public, here on XDA-Developers. A note from trsohmers:
These drivers CAN NOT BE INSTALLED! These drivers were also NOT used by the Cyanogen Team for porting purposes as by using these drivers, you would not be able to use webOS. I am only posting these drivers as evidence, and for research/educational purposes, and it is in the DEVELOPMENT category as such.
If you have any news tips, please contact me or any Portal News Writer.
Rumors are flying about HP and their potential GPL violation by not releasing the source code of the Android kernel sold on three Touchpads so far. Many of them are speculation, much of it over-hyped, but the fact that we speculate points to how many questions go unanswered and how much interest there is in the matter.
A short history for people just tuning in on the issue: In HP’s Touchpad firesale, three known devices shipped with Android 2.2. Because the Android kernels and drivers are protected by the GPL version 2, all distributed modifications to the source code must be published if they mass distribute, intended to distribute, or publicly release the device. HP did not publish their Android kernel modifications, and therefore may be violating the GPL.
There are a few reasons we can’t say they are definitely violating the GPL. First, leaks don’t count as mass distribution, or as intent to distribute. This is why, when a few users approached HP about the GPL violation, HP responded, “HP Palm doesn’t support Android and has not authorized anyone to provide consumers with the Android OS for Touchpad.” Saying there is no intent to distribute is not enough to stave obligations to the general public. Yet, it’s only 3 devices. Not only does that not qualify as mass distribution, but it’s such an insignificant number of Android Touchpads that HP has plausible deniability on their side, and obviously imply it’s a leak in their response. It all depends on why Android was installed those three devices, who installed it–in other words, whether HP is responsible–and whether the truth of the matter qualifies according to GPL definitions.
As far as most people understand it, HP developers were either bored or testing. They rushed those Touchpads out the door with all the others in the firesale and did not install WebOS. If the developers were bored, it’s a leak. Their actions were in no way sanctioned by HP. If the developers were testing for HP, it’s still a leak because the release was unintentional, but they may be liable. HP did not deny that they sanctioned the actions of their developers, only that they did not sanction the distribution of that work. People have to pay for their mistakes too, not just what they intend to do.
Trsohmers, formerly of the TouchDroid team, came to me with a different version of the story. He says that HP used Android’s Linux foundation in the factory to test for faulty devices. This isn’t simply speculation. According to Green, who works with kernels for the CyanogenMod Touchpad team and posts their Touchpad videos on his YouTube channel, the team received an anonymous email that included a state-of-the-art Cypress Semiconductors touchscreen driver and a censored email. The drivers are hyper-accurate and used to test device limits, so the CM team couldn’t use them. However, their quality make Cypress Semiconductors undeniably the manufacturer, and the fact that they aren’t something just anyone could have lends credibility to the email. That is, the driver came from an inside source, and so, therefore, must the email. The email said this (grammatical errors are original):
In fact before HP refreshing their webOS image, all HP touchpad TSP controller board were used Android to run the MFG procedure. Attached file is the latest TMA395 Android driver. The significant difference is that the HP touchpad TSP controller firmware has no bootloader support so when you want to bring up the device with this driver a little effort need be cost take care of this difference. This job has been done by HP software team before.
The email says it’s not just a sample of devices from each batch, but every Touchpad is loaded with Android in the manufacturing process. If true, the fact that HP used Android to install WebOS is not a violation of the GPL. Using GPL-protected code for private use is perfectly legal. The significance is in the degree to which HP sanctioned the development of Android on the Touchpad. Still the same rules, three devices is more of a leak than anything, but now HP cannot deny that the sale of the Android Touchpads was their mistake.
Moreover, because you don’t need a license to use Android the way HP did, it’s highly unlikely that they got Android relicensed by Google. This is further supported by the fact that they didn’t include it in their defense against the public demand for their Android kernel modifications. So the good news for the general public is that if HP’s mistake can qualify as a GPL violation, it’s extremely unlikely that they have a license to disqualify the violation.
This leaves only a couple steps until HP may be taken to court. Someone needs to make it legally clear that HP distributed or made public their Android build for the Touchpad, according to the GPL. We know they distributed them–two were bought at Best Buys in Oklahoma and Texas, and the third was bought from Wal-Mart in New Hampshire. Whether or not this counts as distribution according to the GPL is what needs legal arguing.
If you have any information to clarify or fill in the blanks of the story, please contact me, or any other news writer. We respect wishes to remain anonymous.