02-24-2012 01:20 PM
Thanks for the additional feedback. We made some progress on the A1 but still don't have everything ready to update the package in the download link. Hopefully early next week .
I'll pass along your feedback on the K1. Probably will be at least Tuesday before I know anything more on this.
02-29-2012 11:54 AM
What I'm hearing back from the team is the thought that you may be using tools for version 4 of android rather than the honeycomb tools and it was thought that might be the issue. Are some others you have checked with using the same sdk? Are there others you could try to see if the result differ? Do you have the honeycomb specific tools?
Any more details you can provide ?
I think someone also asked about the bootloader on K1 - unfortunately, it turns out (so I'm told) that this is proprietary to one of our suppliers and can't be released. Not open source.
gmarkall and others interested in A1,
Still working on the missing items and the boot loaders - x-loader and U-boot. Probably several more days to get a complete package and update the link for download.
Sorry for the delay. Please bear with us a bit longer.
02-29-2012 12:12 PM
I have used every arm-eabi- toolchain going back to the beginning of time (ok, slight exaggeration). I have tried every toolchain I can find, along with different versions of gcc. I get the same results no matter the toolchain or gcc version. The toolchains I am using are not android 4.0.X specific and have been used by MANY other developers to compile a 2.6.36 honeycomb kernel for other devices, from the kernel source their manufacturer provided.
I fail to accept that the issue is with my toolchain or build machine. I am requesting the exact version of the toolchain that the dev team is using along with the gcc version they are using. I will then duplicate the setup on my build machine and see if the kernel will boot.
Thanks for your help Mark, but the runaround we're getting from the development team is ridiculous. I don't understand why it's so hard for them to provide a definite response or proper working kernel source code.
03-01-2012 12:22 AM
Thanks for the status update - looking forward to receiving the updated kernel/bootloaders package when it becomes available.
What about posting a log of the exact steps you used to configure and build the kernel, and the output of the build process? That way Mark will have something to pass on to the development team, and they might be able to suggest any additional steps that need to be taken.
Geoponer and Tinybeetle,
Demanding that Lenovo provide the source code for everything used to build the software on the A1 is excessive. As well as them not being required to provide all this, it's very likely that there are other proprietary components in their repositories that they don't have source distribution rights for (TI libraries, bundled apps, etc). Unpicking the sources they could distribute from the sources they couldn't would likely be a time-consuming process, and the benefit to the community of having the entire distributable source tree wouldn't be worth the wait for it.
Let's just keep our focus on the GPL components instead - it will be better for everyone.
03-01-2012 05:40 AM
I totally understand what you are saying and I know that you have the technical background and knowledge to fully understand these concepts. On the other hand, I have to admit that I cannot fully explain what GPL, boot loaders etc., as I lack the knowledge. I am only speaking as a customer/user who is expecting the things that are supposed to be delivered, in order for the community to obtain the required tools in order to start the development of new, revised ROMs, removing unwanted pieces of software and adding new, useful features (for example USB-OTG support) that can be implemented. As I mentioned earlier, I believe that the current software of A1 does not make justice to the existing hardware; I expect to see much more things from A1 with the appropriate software developments from the community.
Thank you for clearing things up for me. I respect the time and effort you dedicated so far in the development of CM7 for A1, despite the fact that you had no access to this critical mass of code and be sure that I will follow your next steps in future developments.
Let us all wait and see when are the missing pieces of this puzzle going to be available to the community.
03-01-2012 06:18 AM - edited 03-01-2012 06:26 AM
Thanks for responding. I agree with you that we can definitely push the A1 hardware further than it currently is being used, and I share your excitement for being able to use the source to exploit the hardware more.
Just to clarify things, GPL is the GNU General Public Licence . In essence, any developer who takes software that is licensed under the GPL, makes modifications to it, and then distributes compiled versions of this modified code, is also obliged to make their modified sources available to those who receive the modified software. There are some other conditions to the GPL, but this is the relevant one for us in this discussion.
The pieces of software that are in the A1 that are licensed under the GPL version 2 are (amongst others, but these are the ones I'm specifically aware of and interested in)
Having access to the Linux kernel will (assuming there's no technical reason the hardware doesn't support it) allow us to provide USB-OTG support, touchscreen support for unofficial Ice Cream Sandwich builds, amongst other things.
Having the sources to X-loader and U-Boot will mainly allow us to make changes that make development easier - the benefit to the community will most likely be some changes we can make that make it easier to test different kernel builds on the device. It'll also allow us to change the first Lenovo splash screen if we want to (Obviously a top priority! :-P)
With the release of these three items, we really will have everything we need to be able to do anything (software-wise) that we want with the device, within the bounds of the hardware possibilities. The majority of the Android source code is open-source but licensed under the Apache Software Licence , which means that Lenovo do not have to provide us with their modified sources. Although there's no legal reason for Lenovo to give us the source for the ASL-licensed code, there's no technical need either - we can get the sources that we need from the Android Open Source Project , or, as I have been doing, the Cyanogenmod repositories .
Like you, I'm very much looking forward to the release of these GPL components, which hopefully won't be too long from now.
 I tried to find a concise summary of the GPL, but failed. In ascending order of readability, these are reliable (but lengthy) resources:
http://www.gnu.org/licenses/gpl-2.0.html - the GPL Licence version 2 text.
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html - The GPL version 2 FAQ.
http://en.wikipedia.org/wiki/GNU_General_Public_License - Wikipedia GPL entry (looks reasonable to me, obviously anyone can edit it!).
 http://omappedia.org/wiki/Bootloader_Project - A description of the boot process on OMAP devices, of the the A1 is one of. It describes X-loader and U-Boot, and how the boot process works in detail.
 http://source.android.com/source/licenses.html - A brief description of why AOSP uses the Apache Software Licence.
 http://source.android.com/ - The Android Open Source Project.
 https://github.com/CyanogenMod - The Cyanogenmod repositories.
03-02-2012 02:06 PM
Do everyone, especially your customers, a huge favor by releasing the source code to the kernel for the A1 and K1 tablets so that the development community at xda-developers can complete a masterful revision of the fundamental Android software. You'll sell far more tablets and we'll be much happier instead of complaining here endlessly about all the stuff that doesn't work, that should have worked and you still don't have working.
I am an early adopter. Some of the issues are truly ridiculous and could have been solved. These people will do it for you at no cost. Don't be stupid. Don't worry about your egos. Nobody cares. You're not going to make a dime extra in your own private marketplace, drummed up by executives in an ivory tower in every major corporation. We know it's not happening. Don't be tempted. Make that revenue in hardware since once word gets out, people will buy up the remaining inventory just to root it. You know it. We know. Just do it!
03-02-2012 06:58 PM