Does anyone know of a way we can take the coding scripts from the SBC mod and use it in another kernel that does not have it?
Thread moved to Q&A.
Use the git repos to get source files for the kernel you want and the sbc mod and compile it yourself.
If you don't currently use or know how to use adb or fastboot I suggest not doing this yourself because there are alot of terminal commands you will have to issue just to set up your working environment. Not to mention setting up the environment itself, creating the source directory, adding the sbc mod to the proper place, etc, etc.
The point I am making is that it isn't easy for people to just pick up compilng a kernel especially if they don't push themselves to learn simple adb/fastboot operations. Add to the fact that if they don't know how to read/edit code there is a severely high learning curve that will have to be completed.
If all you want is a kernel with the sbc mod added ask that dev to make it and hope they will do it. It's not worth the trouble of setting up the environment just to compile one change that is not guaranteed to compile the first time versus the dev already having the environment up and running and it would only take them minutes to compile a new kernel with the changes.
The dev himself already stated he will not include the SBC script in his kernels....but I just posted him a request and ask him if he could cook it up for me.
The Kernel I was trying to use it with is ziggy's latest kernel
BAttitude7689 said:
The dev himself already stated he will not include the SBC script in his kernels....but I just posted him a request and ask him if he could cook it up for me.
The Kernel I was trying to use it with is ziggy's latest kernel
Click to expand...
Click to collapse
I personally compiled the kernel and kernels I am using for this very reason. Plus I wanted more control over things like undervolt levels, governors available/default/settings etc. At this point it seems the kernel you want is just out of your reach for the time being. Sucks, I know.
Related
Introduction
After a year of developing, with many stalls due to studying, we finally reached a stable state with the 2.6.35 kernel port. It is a quite honour to introduce you all to the Las Venturas kernel for the GSM Hero. It is a kernel based on the Cyanogenmod sources with updates coming from the AuroraCode forums. (those lads from Aurora are just geniuses) The main idea behind the Las Venturas was well, a fun project. Let's be honest I love deving new things and this is a really a nice project. We always strife to get the best out of our phones and the kernel has a big influence on it.
The 2.6.35 kernel adds speed improvements but in general it provides more functionality than the 2.6.29 kernel (based on the official HTC sources). It also has newer drivers for the Framebuffer (speed), adds ext4, better USB stack for our ARM devices.
Instructions
Go to your favourite recovery. Always wipe dalvik-cache!. Flash the kernel like any other update.zip, reboot and take a coffee while it is booting. Well done! High five yourself, as you just installed 2.6.35 for your Hero!
Downloads
Las Venturas version 1.2
http://www.mediafire.com/download.php?7r5rcr70mh3ynb3
md5sum: c37c43566cf882f21d0f1dde9afeb37d
Las Venturas version 1.1
Links:
http://www.mediafire.com/download.php?p3csh7sajbolp13
md5sum: 25d0fad0ac42ebf20be47f97c0511406
Las Venturas version 0.5.0
links:
http://94.23.152.245/xda/rmr/Las_Venturas-0.5.0.zip (thanks to wupper!)
http://www.multiupload.com/U6KYEOCWEE
md5: fa1d0b5767caa68152fe8166a7f74f4b
The big compare list
Current advantages:
full ext4 support
Newer overlay code, apps tend to be displayed faster than the original .29 kernel
Newer usb-code, more suitable for newer ROMs like Gingerbread and ICS than the .29 kernels
More stable GPS (no more reboots!)
General faster IO than 2.6.29
Less latency for playing sound/music
For the rest, it contains newer drivers for a lot of stuff. As it is a 2.6.35 kernel of course
Current disadvantages:
USB is experimental. Usb-tethering might not work, for non-sense ROMs you can try Erasmus fix
SD-card IO is slightly slower than flykernel (around 0.5%)
Change-log
Changes of last Version 1.2:
Faster general IO output
Fixed some bugs concerning SD speeds
Fixes to the interactive governor
Newer vibration-code, less latency (small impact, but everything is welcome)
Ashmem flushing fix
Code cleanup
Full log:
https://github.com/riemervdzee/hero-kernel-2.6.35/wiki/Changelog
Source code
Config used is found under kernel/arch/arm/config/hero_defconfig
https://github.com/riemervdzee/hero-kernel-2.6.35 (0.5.0 and above)
https://github.com/riemervdzee/cm-kernel (Older repository. For pre 0.5.0 versions)
Thanks list:
--> Elemag -- Initial start of this project, great advisor and debugger
--> s0be -- working on the .35 fork of this project for the Hero CMDA. Good to see another dev'er at work, always inspirational
--> Erasmux -- For his flykernel and his work on getting the .35 to work
--> Ninpo -- Initial start of this project
--> Feeyo -- For general fixes. Great mentor to linux/kernel programming
--> And of course all CyanogenMod lads working on the CM-kernel
Note that I hijacked Elemag's thread (he first opened this topic). So things might sound a bit wrong if you read the first pages
Las Venturax
This post will contain the releases I do until Riemer has time to catch up with me: (Unless I see me and Riemer would like to go in different directions with this kernel I don't want to open another thread for "my" versions)
Las_Venturax-0.6.2.zip (mediafire) (multiupload)
Scheduler tweaks (restored latency to 6ms and enabled hrtick - this time for real!)
SmartassV2: a few bug fixes.
Some upstream updates (thanks arco)
This is a generic "smart updater package" which can also be used to do OC from boot, as explained in my FlyKernel post under
Boot OC and optional tweaks (first post).
USB tethering on this kernel is different from the .29 kernels most ROMs are compatible with. Fixes for CM6/7 are found on post #1029.
More information about SmartassV2 (for users) can be found on my FlyKernel post.
ROM Developers
Developers aiming to integrate this kernel into their ROMs, might find it more convenient to use the following regular update package as a reference:
Las_Venturax-0.6.2-Floyo.zip
In this package the kernel's ramdisk is the one compatible with Floyo 1.4.
If you prefer to recompile the kernel yourself, you are very welcome to do so, but please share your updated sources. Obviously you are changing something (maybe very very small) otherwise why are you recompiling it? Please share with us what changes do you find to work better for you. You are also required to this by the GPL license of the kernel.
Previous versions:
Las_Venturax-0.6.0.zip (multiupload)
Tweaked scheduler parameters (lowered latency to minimum - ROM developers please do NOT overwrite the scheduler params in your init.rc)
Added smartassV2 governor as the new default governor - more details below (since 0.5f, tweaked built in sleep in 0.6.0)
Added interactiveX governor (since 0.5c)
Some compiler optimization (stable since 0.5e)
Fix for jogball notification (since 0.5a)
Use frequency table from fly kernel (since 0.5a)
Based on Las Venturas 0.5.0
Las_Venturax-0.5f.zip (multiupload)
Added smartassV2 governor (set as default)
Las_Venturax-0.5e.zip
Added "Wireless RNDIS" - could this fix usb tethering?
Tweaked compiler optimizations and moved to new toolchain
Las_Venturax-0.5d.zip
This version is a "quick fix" version trying to solve the stability issues (spontaneous reboots) reported with the 0.5c version. Only thing is I have no idea what is causing these problems so this is really a bit of a shot in the dark. Please report any stability issues, and if possible also state which ROM, what you where doing at the time and for spontaneous reboots attach a last_kmsg (i.e. "adb pull /proc/last_kmsg"). Thanks in advance to all the testers.
Reverted part of the compiler optimizations from 0.5c.
Back to NOOP scheduler
Default governor back to smartass. interactiveX is still available and I am still very interested in feedback regarding it.
Additional kernel config tweaks.
Las_Venturax-0.5c.zip
Added interactiveX governor by Imoseyon - for now this is the default governor (most likely a temporary situation).
Use BFQ I/O scheduler
Voodoo compilation optimizations
Fix for cpufreq time_in_state (i.e. SetCPU frequency counters) - broken only in 0.5a version (commit).
Note regarding the "new" interactiveX governor:
From a very quick look at its code, this governor looks promising to me, and I hope that it might provide better battery life over the current alternatives.
I am very interested to hear about the battery and performance with this governor vs. smartass and/or ondemand.
Some philosophical discussion on the subject:
It seems there are quite a lot of smartass/interactive variants out there (in kernels for other devices). I also have some ideas of my own, that will hopefully manifest into a new governor someday soon (smartassV2?).
In the meantime, interactiveX seems relatively close to smartass (also discriminates between screen on/off states), and to the best of my current understanding, in theory, given the parameters I have selected for it, I hope it might improve battery life.
Las_Venturax-0.5a.zip
Fix for jogball notification (commit)
Use frequency table from fly kernel
Based on Las Venturas 0.5.0
All changes are on my github.
Cudos to riemervdzee for all his hard work on this excellent kernel, as well as to all others who have helped to develop and test this kernel.
Yeah any and all kernel devs, get on this. I was supposed to be working on this with Elemag but Froyd has been eating my time. Hopefully one more release should get it "stable" so I can get back onto this.
Elemag has done fantastic work.
Hmm seems like there is already a .34 kernel for the G1. Damn them
Elemag said:
Hello,
A lot of things are already working, including:
MTD
usb
adb
charger/battery
display
keypad+trackball
...and probably most thing not mentioned as not working
Click to expand...
Click to collapse
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
erasmux said:
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
Click to expand...
Click to collapse
quote. i'm very interested
erasmux said:
Do you have a config file with adb working, I am stuck with no ADB using the hero_defconfig.
Also which ROM do you use for testing with this kernel? EDIT: to be more precise, I am mostly interested in the ramdisk you are using to get ADB to work.
Any other ideas how I can get adb to work?
Click to expand...
Click to collapse
Played a bit with the config and I finally got it working. Would still appreciate the config file you are using.
I am using the ramdisk from CM6 default boot.img. The config is hero_defconfig. Testing it under my own CM6 build which should be more or less the same as the CM6-nightlies.
The touchscreen driver synaptics_i2c_rmi.c does it contain the AOSP fixes found in the 2.6.29 kernels ?
rbrucemtl said:
The touchscreen driver synaptics_i2c_rmi.c does it contain the AOSP fixes found in the 2.6.29 kernels ?
Click to expand...
Click to collapse
I think it doesn't - Can't find anything related to eventhub filters.
looks good. thanks for posting sources. I'll help out also
Way awesome. Great job. I'm not too well versed in all this but I'd love to lend a hand as well.
Decad3nce said:
Way awesome. Great job. I'm not too well versed in all this but I'd love to lend a hand as well.
Click to expand...
Click to collapse
Agreed, not my field of expertise but willing to help in any way I can and I'm willing to learn
Sent from my HTC Hero running froyo: take that, Sprint!
Please guys, post here your improvements, your tweaks ecc ecc
mr.bang said:
Please guys, post here your improvements, your tweaks ecc ecc
Click to expand...
Click to collapse
Yeh a "tweak" which would make the rest of the hardware actually work would be nice.... We are still far from getting this kernel to a usable state. Let first concentrate on this.
I personally, have done a massive porting of code from the .29 kernel which has obviously resulted in the kernel not booting now - yippee Now working on trying to get it to boot which could takes anything between days and never.... Is there any way to debug the kernel boot if adb is not working?!
Anyone else working seriously on this?
i'm trying to work on this but i have few building problems..
You can boot, then reboot into a working kernel and pull /proc/last_kmsg if you can't get to adb. It would be nice if you post the output to pastebin and link it here .
As for the massive porting from .29 -- I think that the microp driver needs to be ported first, cause it is probably the bottleneck right now.
I found that the touchscreen driver initializes as /devices/virtual/input/input0 but on the .29 kernel it is input1 and input0 is the headset. I don't know if this can cause it not to work though.
If you have building problems, write to me, preferably in github. I don't have time to work much on this, because I am trying to make my diploma, but will surely take a look if someone has an idea.
Anyway, getting the touchscreen to work will be a breaking point
I actually started working on the SD card not being recognized (seemed easier than fixing the touchscreen or so I thought). Somehow got pulled in to porting a whole lot of code from the .29 kernel's arch/arm/mach-msm directory....
I'll try the last_kmsg thing sounds very usefull
Guys I think porting more and more stuff forward from .29 is a bad idea. Instead the stuff we -need- should be adapted for 2.6.34. Otherwise we're going to end up with some messy 2.6.29/34 hybrid. Everything we need is there in the kernel apart from specific drivers, otherwise 2.6.34 wouldn't work with the G1, however it does.
Hacre said:
Guys I think porting more and more stuff forward from .29 is a bad idea. Instead the stuff we -need- should be adapted for 2.6.34. Otherwise we're going to end up with some messy 2.6.29/34 hybrid. Everything we need is there in the kernel apart from specific drivers, otherwise 2.6.34 wouldn't work with the G1, however it does.
Click to expand...
Click to collapse
I was obviously talking only about drivers....
I am in need of a kernel with loop enabled. I am in the newest OTA, if one doesn't exist I could use some help compiling one from the newest source, I have everything I need to do it on my Linux machine I am stuck trying to find which makefile to edit and where the .config file containing CONFIG_DEV_BLK_LOOP is located.
If it matters at all I would much rather compile my own kernel so I can learn something new.
Thanks for any help guys!
Sent from my White Evo 4G
Really!? I am not lazy or dumb, I have gone through a lot of kernel threads and it is not stated wether or not loop is enabled, all I am looking for is a kernel close to stock with loop enabled, come on guys I know someone here knows of one, if not is ANYONE willing to work with me while I learn to make one?
matthewjulian said:
Really!?
Click to expand...
Click to collapse
LOL. I'm on the more technical side, program for a living and have compiled a share of Linux kernels in my life, and I'm not quite sure what you are referring to. Sadly most of the sharper devs pretty much handle these forums in a one-way manner, they put out stuff, but they rarely read other people's posts. There are plenty of people that like to help out, but most of those folks aren't going to know anything about compilation.
The makefile you need to edit is in the root of the kernel source. The very first one that you see.
I am referring to loop devices support, this enables me to boot ubuntu on my Evo, it is one line of code that needs to be un-commented and changed to "CONFIG_DEV_BLK_LOOP=y
I am just lost,I was following this tut here http://htcevohacks.com/htc-evo-hacks/how-to-build-your-own-htc-evo-4g-android-kernel/
but the directions seriously slack off from step 11 onward, any ideas?
Do you by chance want to install Ubuntu on your phone? I think I saw something pertaining to that in some instructions I browsed over a while back.
lithid-cm said:
Grab the latest HTC source code:
edit the makefile:
Code:
CONFIG_DEV_BLK_LOOP=y
Then compile the kernel. There are plenty of how tos for kernel compiling. Let me know if you need more direction.
Click to expand...
Click to collapse
I have all the files I need, I was following the tut at htcevohacks.com but the instructions seriously slack off & there are numerous makefiles in multiple folders on top of that I can't seem to find what file contains the line config_dev_blk_loop, could you point me to a more complete walk-through please, oh and I am on the latest OTA with the newest kernel and radios.
Bump for desperation,chewed up almost 3 days of my time...
Sent from my White Evo 4G
Bump for this simp
Ok, well I guess I am gonna just have to PM each Dev individually about each individual kernel, damn all I need is a how-to or tut on kernel compiling (which the search function apparently can't find) or someone that knows of a 2.2 kernel with loop devices enabled. Oh well.
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
nukedukem said:
I'm pretty sure netarchy kernels are loop back enabled. Ask around there maybe.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
YAAY! LMFAO, I will ask there, sorry I'm excited but I have been trying to get this working for a while; I would much rather learn to build it myself but I will take what I can get for now.
IF ANYONE knows where there is an in-depth tutorial on how to compile a kernel from the newest source I would be extremely appreciative, THANKS
Did you ever find or get your Complie to work? I tried for a while to compile the stock Kernel, then gave up. I took a stab in the dark and flashed a stable netarchy kernel. unfortunatly that Kernel didn't have Loop devices enabled (Pulled Config file and Unzipped it) I like the Kernel I am running but need to find a way to get ubuntu running.
Netarchy does have loop enabled, I am running Netarchy ___(will find which version later can't remember) but yeah I am running Lakia Linux
now(network security testing, think Backtrack 3) as well as another new Linux image from a guy here, anyways I think you need Netarchy universal cfs havs less no sbc 4.2.2
Sent from my White RLS5 Evo
hi everyone
well, i read for the forum and some threads about how to make a kernel,
but i have some doubt,
really a want to create a kernel for app tun.ko because according the app its possible that tun support is COMPILED WITHIN YOUR KERNEL.
well, my phone its cdma and i don't know how to get a kernel for modify, i think extract a kernel for mi actual room CM7 but i don't know how to do.
htc-desire5 said:
hi everyone
well, i read for the forum and some threads about how to make a kernel,
but i have some doubt,
really a want to create a kernel for app tun.ko because according the app its possible that tun support is COMPILED WITHIN YOUR KERNEL.
well, my phone its cdma and i don't know how to get a kernel for modify, i think extract a kernel for mi actual room CM7 but i don't know how to do.
Click to expand...
Click to collapse
Yeah, this is great idea!
I doesn't know too, but when I know, I will made OTG support kernel
lol, have you ever tried something easyer??
I have no idea from ROM but i tryed some ROM modding and that wasn't that easy. A tip try first something basicly and more easyer. It's like you want to build an computer without knowing anything about electric
I waited to post this over here until it was debugged and all the hardware works.
Even though this forum's been kinda dead quiet for a while, xda gets searched and I want this source code out there.
Derived from androidarmv6 project and tweaked over to thunderc from the p500 developers' awesome work getting it running on the Optimus One.
source:
https://github.com/bigsupersquid/and...7x27-3.0.x.git
(branch squid, for lack of imagination.)
make thunderc-test_defconfig
you'll want to change or remove the toolchain path in the config. it is highly unlikely that your cross toolchain is in the same path as mine.
I set it in the config to avoid having to add "CROSS_COMPILE=/blah/blah/etc" to the make command every time I rebuild the kernel.
it is for jellybean and kitkat roms.
use on older android versions messes up various things. Especially USB.
it conflicts with /sbin/chargerlogo or /sbin/charger for offline charging and bootloops unless that file is removed.
Use the attached removecharger.zip in recovery with signature verification off for that if you don't want to edit the ramdisk yourself.
md5sum b1a9f21285e09e06dc94422a8578dc98
enjoy
@bigsupersquid Know if anyone's willing to have a stab at building Firefox OS, now with the 3.x kernel?
EDIT: Well apparently there's no full ArmV6 support in it so, I guess not...
I kind of feel as if this should be a very basic topic and that I should not be having to post a new thread on it... but, out of curiosity, does anyone know whether or not the Android kernel-- which as we all know is a flavour of the Linux kernel-- can be updated through "patching" as the regular Linux kernel can? The reason I am asking is that I greatly prefer to run my device with a custom kernel that has extra features over the stock kernel, however, it seems like every custom kernel that is released is released as a one-shot deal, and that the only way to have a kernel that continues to be updated with fresh source is to run the kernels that are provided with the nightly ROM builds.
Of course, I could go the route of learning how to build my own kernels and add features to them.. but I guess my basic question is, does there exist any form of "general patch" that is periodically released by Google, or the Linux Kernel foundation, etc., that will bring your current kernel up-to-date with the latest system-wide changes (secuturity & stability fixes, etc), while leaving the bulk of the kernel and the kernel configuration in place? Or is that a totally unrealistic and impractical concept? I do build my own kernels from source for my laptop, but I know very little about compiling a kernel for android.. anyway, if there are any kernel devs still on this device's forum, what do you guys think?
Any feedback from knowledgeable individuals much appreciated.. thank you!
No. You would have to build the kernel and flash it yourself. You can usually find HTC's kernel source on their website for each device. You take that kernel and manually patch the updates yourself.