Related
Hey all. This is my first post here on XDA.
I've been thinking of compiling my own kernel image for my HTC Legend. I've spent hours googling and reading different forums and blog's. But without greater success, most of the guidelines are not spot on and some things are not cristal. So I have a few questions regarding this.
I have read that a specific radio image is just "comptabile" for compilation with a specific kernel version. So let's say I have HTC_LEGEND_RADIO_7_083521_sign.zip, how do I know what kernel version this is made for? In my ears this sounds pretty strange . I would not be able to build a kernel from that radio image and the 2.6.35.5 Linux kernel?
I've also tried to figure out what exactly the radio image is from various boguos posts on different forums, and what I belive it is from the tiny bits of information I've found is that It's modules for the phones hardware?
Oh, and what is the latest radio image version available for the HTC Legend?
Hope someone can help me clear some of my questions
I can only answer the very last question lol, it's 7.08.35.21
Latest RUU:
RUU_Legend_Vodafone_AU_2.10.178.1_Radio_47.39.35.09_7.08.35.21_release_138238_signed.exe
First seen in:
RUU_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7.08.35.21_release_130330_signed.exe
Hi tonper,
First... where did you get that radio has something to do with kernel??? Radio image is basically a firmware (operating system of its own that interacts with radio hw) and has nothing to do with Android kernel which is in fact patched Linux kernel. One can access all functions of radio through userspace Android apps that communicate with radio via native libraries. That's all that it is to say about radio in conjunction with kernel.
To be able to build a kernel one should first master basics of Unix/Linux system principles and first try to build own kernel for some Linux distro. One need to know also how to boot this kernel and use it with the rest of the operating system. Last thing to master is cross-compiling as you will be building kernel for ARM architecture most possibly on your x86 PC. In short the topics to search for would be:
* knowing Linux (principles)
* booting Linux (process)
* compiling Linux kernel
* cross-compiling
Android powah!
Thanks for your answer BlaY0!
Will check into it some more this weekend with this new information.
BlaY0 said:
* knowing Linux (principles)
* booting Linux (process)
* compiling Linux kernel
* cross-compiling
Click to expand...
Click to collapse
Been running Linux for 10 years and Debian for 7 years. So got the basic knowledge I just can't find any good documentation on this topic
Cyanogenmod wiki have some guides
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
snakehult said:
Cyanogenmod wiki have some guides
Click to expand...
Click to collapse
How could I have missed that page? Have been googling like a maniac. That was pretty much exactly what I was looking for. Thanks alot snake
tonper said:
Been running Linux for 10 years and Debian for 7 years. So got the basic knowledge I just can't find any good documentation on this topic
Click to expand...
Click to collapse
OK, then you're set m8 you just need to grab some ARM cross-compiling toolchain for x86. Your first bet would be Android NDK. You can also use CodeSourcery or even build your own toolchain with Buildroot... but for compiling kernel really doesn't matter which one U use.
Happy compiling
Hey guys i was just wondering what the big problem with the hardware acceleration on all of those ICS build are. for what i understand its a kernel problem. amazon build upon android 2.3 with an 2.6 kernel. the new ICS needs a kernel 3+ for driver and open gl to do the hardware acceleration. i'm i right?
in this state i do wonder, if it is possible to get hardware acceleration on ics. is it possible to build a 3+ kernel for the kindle? where is the problem, its only man hour that we need, or is for example the kernel signed to prevent flashing?
I know that they guys at the dev section are doing an amazing job so far, and to this point im very glad to have so many good dev working on the kindle. i do not ask for an date, like: in 3 days there will be an ics build with HWA.
im looking for some insight in the dev roadmap for example what is missing for the mentioned HWA.
thanks so far :>
It will come with time - man hours are indeed what's needed. No signed kernel problem. Needs a lot of hacking to get the new kernel to work.
yeah i would also like to know this
kernel 3.0 is not required for HW acceleration.
watch this video.
http://www.youtube.com/watch?feature=player_embedded&v=6Ug-HNK9XVE(4:50)
This tablet running fine on 2.6.39 kernel with hardware acceleration.
We have only 2.6.35 kernel... (older than 2.6.39)
Just developers can not yet solve the problem.
Android 3.0 kernel is definitely not needed for hardware acceleration. Teamhacksung had it working with a 2.6.35 kernel before they moved to a 3.0 kernel for their supported galaxy s devices.
For hw accelerated ui drawing you will need updated pvr drivers and modified fb drivers.
For hw accelerated video decoding, you will need updated dss bridge drivers, and updated codecs specifically for the IVA processor in the omap 4. I don't know if it is a requirement for our devices, but on the aries(hummingbird) platform they had to modify their framebuffer drivers to have more overlay buffers.
It just a toss up of whether it is easier to get a working 3.0 kernel, or back port all of the udpates.
I guess its time for me to get a VM setup and start hacking away. Or at the very least start comparing parts of our 2.6.35 kernel with the pandaboard, and gnex 3.0.8 kernel.
woolbeo said:
Android 3.0 kernel is definitely not needed for hardware acceleration. Teamhacksung had it working with a 2.6.35 kernel before they moved to a 3.0 kernel for their supported galaxy s devices.
For hw accelerated ui drawing you will need updated pvr drivers and modified fb drivers.
For hw accelerated video decoding, you will need updated dss bridge drivers, and updated codecs specifically for the IVA processor in the omap 4. I don't know if it is a requirement for our devices, but on the aries(hummingbird) platform they had to modify their framebuffer drivers to have more overlay buffers.
It just a toss up of whether it is easier to get a working 3.0 kernel, or back port all of the udpates.
I guess its time for me to get a VM setup and start hacking away. Or at the very least start comparing parts of our 2.6.35 kernel with the pandaboard, and gnex 3.0.8 kernel.
Click to expand...
Click to collapse
After buying the Kindle Fire just recently, I was looking up HWA and found your post. Thanks for the detailed response, much appreciated.
Hashcode is working hard on a 3.0 kernal and is keeping updates on his progress in this thread. He could be weeks away from debugging the kernal he is developing
My understanding is, for HWA to work running ICS, the 3.0 kernel is required. Yes, there are other ROMS that have HWA working but they are not ICS.
That is correct, the current kernel doesn't allow for the changes made in android 4.0. If you need HWA for daily use, stick with a gingerbread rom. Otherwise support and wait for Hashcodes work on the new kernel.
Sent from my Amazon Kindle Fire using xda premium
Hello
Can anyone point me to a guide or summary of alternative kernels please?
You can check our work on the nook color linux kernels in this thread here. http://forum.xda-developers.com/showthread.php?t=1370873&page=285
I also have a guide on using the Git and the Gerrit code review down in cyanogenMod central for the nook color linux tree at this thread link here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
If you want to help and have experience on building linux kernels feel free to post a follow up in the first link I have posted. We are using the git and the github to commit code for our linux kernel tree. If you need help on getting up and going on using git, look through the second link I gave, I have all of the links on the github for our project and other helpful tips for you to get started. Right now the top developers are committing code to the jellybean branches. <fat tire> is our top developer and github maintainer for the nook color linux kernel tree, you can find him in the first link I provided and can help you also.
Thanks. I'm able to put a kernel together, but i haven't much experience in original development. I'll keep an eye on that thread though!
Right now we are looking for a few debuggers for the Jelly Bean Kernels. You know how to use debuggers? We need to check for kernel opps that are not being caught by the machines. Last year here there was a developer that rooted 2 kernel opps out and submitted them to Gerrit as a patch. Henk Poley , the developer for the Git extentions used his app and rooted out a few kernel opps on the cyanogenMod stable 7.1 at the time. Check out the my link on debuggers if you are not sure how. Not glamous work but it needs done, and I am getting up and ready to go back to school. Might do that if you want to help.
<Eyeballer> here is looking for someone to strip out all the unnecessary phone .apks for the nook color cyanogenMod builds, like the phone.apk and the telephony.apk along with the voicedialer.apk. I was going to get started on doing that but got sidetracked on getting a proper workflow going on the github. That second thread has links on how to submit work and patches down at cyanogenMod.
~~~~~~~~~~~~~~~
If you are up to a more difficult challenge the wi-fi module needs more work on the Jelly bean builds, they are still getting wake lock problems with it. A few months ago the developers disassembled and reassembled the wi fi module and could not find any code conflicts within the driver or the module. They can fill you in on that up in IRC at #nook color if you want to follow up on that.
Wow. Uh, I don't actually use a debugger, I'm pretty new to building kernels. I used to program C++ in Visual Studio, but so far haven't investigated the debugging process. In my own kernels I use printk, and that's about as sophisticated as it gets.
I wish I could help, but I need the device to available at the moment for my young daughter. Good luck with JB. I'll consider helping if my situation changes.
can someone update .597 kernel here is source
https://github.com/kamarush/semc-kernel-msm7x30-3.0.8
https://github.com/nexx/htc-kernel-msm7x30
also cyanogen start porting 3.0 kernel for msm7x30
http://pocketnow.com/android/cyanogen-porting-linux-30-kernel-to-msm7x30-phones
thers some sorce i just googleing and found this
ps i alo find this : https://github.com/kamarush/semc-msm-3.4
According to a Google+ post (what are we going to call those? Geeps?) Cyanogen himself is working on porting the Linux 3.0 kernel to Android-powered devices running on the msm7x30 chipset.
According to the post “All the subsystem changes from 2.6.35 to 3.0 are super tedious, especially sound.”
What does the 3.0 kernel include?
First of all, it does NOT include any “special scary new features” and “there’s absolutely no reason to aim for the traditional ‘.0′ problems that so many projects have”.
Instead the release includes the “usual two thirds driver changes, and a lot of random fixes” and “some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!)”.
According to Linus himself, “in general this is supposed to be a fairly normal release cycle”.
So, with no much fanfare, the 3.0 kernel was released, and with the backing of one of the Android greats, it’s coming to smartphones soon.
Click to expand...
Click to collapse
Hi
I have successfully upgraded my Ideos X5 U8800 to 2.3.5 official Gingerbread, rooted it, and then repartitioned it using Blepart recovery. Subsequently I have checked out cm11 source, including Blefish repositories/code for the U8800 (thanks for good work, by the way!), compiled/built and installed a ROM. This was my first build.
OK. Good so far. Only I am looking to build cm10.1 because my goal is to eventually get this handset running Ubuntu Touch. Therefore, the next step is to get it running on cm10.1.
My problem is that I cannot find the source I need. I have tried to set up a fresh source tree and check out cm10.1 source combined with Blefish's source by specifying branch cm10.1 for the latter, using the files I used in .repo/local_manifests to get the cm11 device source etc. from Blefish. However, something seems to be missing as the lunch command fails and compilation aborts. Also, I can see that development has been discontinued on this branch for the U8800.
Any suggestions?
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Blefish said:
The cm-10.1 branch is deprecated, and I am not planning to update it as cm-11.0 is better in any way.
Is the Ubuntu Touch source code only based on cm-10.1 code though? Maybe you could have success using the cm-11.0 code as it is right now? I am not familiar to how Ubuntu uses the lunch commands, it might be different than Android's default.
Click to expand...
Click to collapse
Thanks for the quick response!
The Ubuntu Touch guide specifically states cm-10.1, but I will sign up with their forums and check whether I can use cm-11.
The following passage from the Ubuntu Touch Porting Guide gives the impression I might be able to base my work on cm-11? Would you agree?
"For quick reference, these are the current components used from Android:
Linux Kernel (stock Android kernel provided by the vendor, with a few changes to support some extra features needed by Ubuntu, such as Apparmor)
OpenGL ES2.0 HAL and drivers
Media (stagefright) HAL, to re-use the hardware video decoders
RILD for modem support
As Ubuntu is running as the main host on top of an Android kernel and the communication between the Android services and HAL happens via Binder, Sockets and libhybris. "
I am hoping this could work, as it would be a tremendous help, now that I have a running ROM built on 20 May with your source tree for the device specific code etc. which works like a charm! :good:
Best regards,
aribk