Develop Bugs

Simplistic HTC Hero Kernel Question.

Hi All,
Running rooted Hero with Modaco 2.5.1 rom ( thanks Paul )
Was hoping someone could ( simplistically ) answer a few question for me.
As I understand it - one of the things holding back development of Hero ROMS is that HTC haven't released the kernel for the Hero.
1) What exactly IS the kernel in the greater scheme of things?
2) When are HTC likely to release it?
3) When it is released, what new things will it allow developers to do?
4) Anything else relevant to it worth knowing?
TIA

Look at these:
1. The kernel is the Operating System for the phone, it runs everything.
2. That is the magic question...
3. It'll allow more development in terms of mods. we'll be able to change alot more and get more out of the phones.
I'm sure others will have more detailed explanations.

Regarding question 2:
I've gotten response from HTC support the other day that the release is planned but no sure date could be given.
Date: 5th of October
My question:
Hello there, I realize that this might not be the normal kind of request you guys get, but here goes. This is probably not your average request and might require escalation. I was wondering when the source code for the Hero kernel was gonna be available at developer.htc.com?
Click to expand...
Click to collapse
Answer:
Hello
This is quite a normal question we get here at HTC. The source code is something that will becoming soon. We have had contact with those far higher than my self or are planning on adding the source code as soon as possible. I have not been given a time scale but bases on the code for the two other handsets i should expect it in the next couple of weeks.
Hope this helps.
Click to expand...
Click to collapse
So, educated guess would be around the release of the Hero in the US.

Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Am I right in thinking the kernel is linux based?
And a big magic question - when the kernel is released, will people be able to modify it and get the bluetooth working properly?
Sorry if it's a bit basic - but interesting to me....

The Kernel is not the OS (As most people understand an OS to be) (OS meaning Operating System)
It's at the core of the OS but is not the OS. You can keep the same build of an OS but update the kernel and vica versa. It is (put simply) what converts the hardware calls from the OS into something the hardware understands.
So (using current issues as explanation) The OS tries to load the GPS and the kernel isn't configured with the right settings the GPS won't load. Similarly if you try and use the trackball and it's not setup in the kernel then it won't do anything.
The OS will still work fine with other things but until the kernel has the right settings put into it it just won't see the parts of the phone it's not set up to.
Here is a technical description of a Kernel.
http://www.linfo.org/kernel.html
I'm sure I've just made it as clear as dishwater but if not I hope it's helped.

J-Zeus said:
Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Click to expand...
Click to collapse
Not exactly. To add to what akirainblack has said already...ROM stands for Read Only Memory. In this context it is a bit different as it is the complete package that makes up the Kernel, the OS and anything that is pre-installed to the phone. When you run the RUU (Rom Update Utilitiy) on your PC is completely refreshes the system software in your phone - Kernel, OS and any pre-installed apps - just as if you had bought it from the shop like that.
J-Zeus said:
Am I right in thinking the kernel is linux based?
Click to expand...
Click to collapse
Yes.

Hmmm...
simple question... when the kernel is available... would we be able to get a white taskbar on the Hero?
//Nik

When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave

foxmeister said:
When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave
Click to expand...
Click to collapse
Including getting Bluetooth working?

J-Zeus said:
Including getting Bluetooth working?
Click to expand...
Click to collapse
In theory, yes. In practice, the situation is a little more complicated, but at the very least I'd imagine it would be possible to get BlueX, or something like it, working on rooted Heros fairly quickly.
Regards,
Dave

Given that this is a Linux kernel, aren't HTC required by the GPL to make the source available to all Hero owners?

This is covering the same ground, but is another way to look at things regarding the kernel and the OS. The kernel abstracts the specifics of the hardware from the Android system. For example, when the Android system requests that the bluetooth hardware be enabled, the kernel can translate that request so that it works with the particular hardware of the phone - as the bluetooth hardware of the Magic may be different from the bluetooth hardware of the Hero. So the kernel, is an interface that translates and Android call to the specific hardware level controls necessary. The kernel sits between the hardware and the Android system.
It also means that releasing the kernel will not allow us to make changes to the Hero Android user interfaces. If we want to change colours, icons and so on in the Hero ROM, we would need the source code for their "tweaked" Android and maybe to some degree their TouchFlo software. I doubt they would give that away. It would allows us however, to tweak the kernel, or transplant the driver code for specific hardware pieces in the Hero, to a newer version kernel.

I understand that the release of the hero kernel, could help me with my cause (getting 1.5/1.6 'clean' android on my hero without any htc apps/front ends).
Somebody suggested contacting HTC and asking for it to be released.
I have a few questions regarding that:
1) Has this happened before? That HTC released an android kernel?
2) Did this happen after the request?
3) Who should we contact to get it? (which HTC division)
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?

E2K said:
1) Has this happened before? That HTC released an android kernel?
Click to expand...
Click to collapse
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
E2K said:
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?
Click to expand...
Click to collapse
The HTC Sense UI won't be included in the kernel source.
They dont have to release the source of them.
New question
Is it possible to create a new donut kernel (2.6.29) with the changes they made to the 1.5 kernel (2.6.27)?
Looks like they send you the hole kernel, not just some patches and new drivers...

mopodo said:
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
Click to expand...
Click to collapse
So this means that we could compile or 'cook' a working vanilla android 1.5 for the HTC hero, with everything working fully?

HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).

jubeh said:
HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).
Click to expand...
Click to collapse
Hi, thank you for this information. You make it sound like it's possible
I tried searching for the Hero Kernel, but I could only find this:
http://developer.htc.com/
The hero is not listed (maybe it shares a lot with the magic kernel?).
edit: this post dating from september 10 stated that HTC would "release the kernel source soon".
This was more than a month ago though..
edit2: calling HTC Netherlands right now..
edit3: after explainig the need for the kernel, I've been on hold for 10 minutes now..
edit4: more than 18 minutes now
edit5: after 26 minutes I hang up

Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site

SquiffSquiff said:
Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site
Click to expand...
Click to collapse
I could be wrong, but I believe there is a difference between the 'kernel', and the 'kernel source'. The second one is needed when you want to compile the kernel.

Speaking as one who has compiled kernels in the past there are three components required here:
The kernel source- this is typically available from http://kernel.org/ If HTC have made any changes to the source of the kernel itself then these should be apparent in their distribution of the kernel source
The relevant configuration file '.config' which should accompany their distribution of the kernel source and permit you to compile any other kernel as a drop in replacement.
Source code and makefiles for any custom kernel modules ('drivers' in windows terminology) In Linux these have to be compiled together with the kernel.
To use a cookery analogy:
The kernel source is the raw ingredients. It can be set up for anything from a supercomputer to a DVD player depending on how you use it. The kernel config is the method which will allow you to bake the type of cake you intend. The modules sources are any of HTC’s own custom ingredients required for everything to work. THe kernel is the finished cake which you eat.

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient

[Kernel] .29 Alpha for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Here's a quick and dirty kernel compile with bluetooth and SetCPU OC both working for this ROM (and any Cyanogenmod based Hero ROM really). Should not be overclocking on boot.
Uses koush anykernel format to make it compatible for any CM based ROM.
I don't plan to update this. I had no intentions of making a Hero kernel so I probably wont be updating this. It was kind of an accident. I don't even have a GSM Hero. Anyways flash and enjoy! Devs can take what I did on my .config and make it good. There's some weird stuff in it.
If this eats your phone please do not hunt me down.
jaymac407 said:
Boots, testing more now..
Update: Wifi works, bluetooth works, OC seems to work (I THINK)
Good work.
Click to expand...
Click to collapse
I copied the netfilter options too. If someone can try to see if Wifi-tether works that would be awesome.
So apparently my kernel boots this aHero and fixes bluetooth. It's a .29 kernel based on the new source code.
Mind you that I might be missing some things. I took around 20 minutes comparing the existing .config and making one that is more similar to the Cyanogenmod .config by eyeballing differences and copying pasting code (yes really). I got really lazy toward the end because the .config was so damn long.
I at least enabled squashfs so the .sqf files decompress for sure now. Set localversion to cyanogenmod. You can see what I did to it in the download link as well, where I have a pastebin of what I did before I disabled perflock.
I also disabled a crap load of debug options that were enabled for some reason.
credits:
cyanogen for CM5. Based .config off his ROM
toastcfh for the kernel source code and being the father of all MSM7K overclocks
koush anykernel
.config here:
http://forum.xda-developers.com/showpost.php?p=6548814&postcount=53

how do i use this on ahero ? just flash it over the rom ?

Is this applicable to VanillaEclair?

Just flash this zip over my aHero?

Re: [Kernel] .29 Beta for Cyanogenmod 5 Based ROMs 【aHero】 - For the Impatient
Dont work for me om cyanogen mod, runs so slow it freezes. Cant get in set cpu and look
Sent from my HTC Hero using Tapatalk

going to test this now. I will update.

it sseems to freeze at boot (aHero 1.0 with JIT)

mine freeze at hero screen

Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?

furrypotato said:
Does it need a wipe and reflash first, or should it be ok to try over current CM ROM ( Vanillain 3.0 test version) ?
Click to expand...
Click to collapse
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen

I downloaded toastcfh's kernel source, but I didn't have time to compile..
anyway thanks for compiling, and I'll test it and report back soon..

Demologic said:
There specific patches for the villain roms, theres one for Vanillain 3. There is a thread with them on xda
I tired it on Vanillian but cant seem to get past the lockscreen
Click to expand...
Click to collapse
And me. Best wait I guess for a fix later.

Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.

jaymac407 said:
Heh, awesome.
Be advised that this sometimes freezes randomly, that's the only bug I can see so far. Especially during going from and to sleep. That's the only issue that needs to be resolved. Apart from that, everything seems to work.
Click to expand...
Click to collapse
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27

can i download the zip and flash it on ahero 1.0????

xaueious said:
Try in setcpu to make the governor performance, if not msm7k
the ondemand governor code was broked in HTC source in .27
Click to expand...
Click to collapse
Only options are performance and ondemand. Neither option seems to help with the crashes.

i have downloaded the zip on first page and flash over ahero 1.0 without JIT my phone boots and come to lockscreen and then i cant anything

Extracting kernel config from I9000XXJP3

Dear all,
Did anyone succeed extracting kernel configuration from I9000XXJP3? Kernel version is 2.6.32.9, the vermagic is "2.6.32.9 mod_unload ARMv7"
extract-ikconfig doesn't work on it.
I succeeded extracting a zImage gzipped payload, but it seems not to contain any configuration in it (see attached).
/proc/config.gz doesn't exist, Samsung open source package (downloaded from Samsung open source site) contains only Android 2.1 Eclair or previous versions.
My target is to build tun.ko and, eventually, ext3/ext4 modules to make them working in Samsung Galaxy S I9000 with rooted I9000XXJP3.
Any idea?

Without froyo source code or a good Samsung Kernel (es. for himem capable) I think is impossible to play good with theses beta roms.
Ciao

Any news? I need tun.ko for jp3 too..

I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!

redsh said:
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
Click to expand...
Click to collapse
Did you use the stock linux kernel? Or the common from android.kernel.org?
I'm trying the same thing actually. Isn't there any default config for the processor that might work? I tried with the config from .29 but when loading the module it says wrong format.

try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again

Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.

bilboa1 said:
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Click to expand...
Click to collapse
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..

miki4242 said:
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
Click to expand...
Click to collapse
Yes that would be a lot of work. Maybe its better to just wait until they release the kernel from froyo. I read that they release their opensource stuff rather fast. But just for adding a module like ext4 I don't think you need those patches, because imho they didn't touch the fs of the kernel. We just need an adaquate kernel config and adding modules should be possible.

Phlogiston said:
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
Click to expand...
Click to collapse
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions

Yes i've set the subversion as well but without the patches from samsung its impossible it seems. We need to wait and hope that they release the froyo kernel sources soon....

bilboa1 said:
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Click to expand...
Click to collapse
Are you sure they set CONFIG_MODVERSIONS? It's off in the downloadable sources.
Just compare the output of `modinfo -F vermagic <yourmodule>` to `modinfo -F vermagic <modulewhichloads>` or to /proc/version .

did this get solved yet? I google'd for the tun.ko file for my i9000 using jp3 but nothing yet... if you have a proper one for the MoDaCo version here please attach it! ~

I think I saw someone's post with tun.ko for FroYo beta somewhere in these forums, I mean i9000 Android Dev. One of the guys here has found a way to compile kernel for jp* here. I am sure.

I actually found it attached somewhere in the forum and it was 1,5447 mb big I think it was... but it still didn't work for me so I presumed the kernel or something must have been wrong.

[kernel]Newer kernel 2.6.32 for Vogue/Kaiser/Polaris

Dear all,
I ask around in the past days if anyone was doing it, but no luck, I even try to look myself if it was easy to do starting from CM kernel, but then, looking better on sourceforge.net the androidhtc project... in the git repo I've seen the htc-vogue-2.6.32 branch!!! Obviously started by dzo.
To get it I've done:
mkdir androidhtc
cd androidhtc
git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel
cd kernel
git checkout -b htc-vogue-2.6.32 origin/htc-vogue-2.6.32
Click to expand...
Click to collapse
Than to configure and compile it (I have a crossdev environment)
cp arch/arm/configs/vogue_defconfig .config
make ARCH=arm menuconfig
# need to be adjusted the config...
make ARCH=arm -j3 CROSS_COMPILE=arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Or you can take the nbh in DZO site and edit with NBH editor.
Everything is working right now:
wifi http://forum.xda-developers.com/showpost.php?p=7869029&postcount=5586
GPS, 3g, touch screen, camera, 3d... bluetooth.
In two days I didn't have any trouble.
Can't wait for the new compcache
Original thread on HTC Vogue by DZO

This is GOOD NEWS!!! I bet theres a shed load of work to be done yet though but it'll be good to get things up to date!

WOW.. nice keep your good work Dude..
I'm just newbie, only can hope and waiting

this confused me when i saw it. according to the internet the google foryo release already is .32

blindguyinanorgy said:
this confused me when i saw it. according to the internet the google foryo release already is .32
Click to expand...
Click to collapse
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.

This thread is kind of confusing. dzo said in the Fresh Froyo thread that he was pretty busy at the moment and what he meant with that is very likely that he is spending his available time on getting 2.6.32 ready for our devices.
It's very obvious if you keep an eye on the repo: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
The very best thing to do right know is propably to not disturb dzo more than necessary. I'm sure he'll let us know when it's has evolved to a somewhat useable state.

loserskater said:
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
Click to expand...
Click to collapse
You are correct that we are using an older kernal. .25 is from before cupcake, wow.
I guess what I saw on the web was that new devices with froyo are also going to already come with .32
I wonder if there is much difference for any phone

There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.

new kernal
voyteckst said:
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
Click to expand...
Click to collapse
Used kernel 2.6.32 after using nbheditor, boots fine running fine so far. Shows kernel version 2.6.32.9 in android settings using Fresh Froyo. Taking it to work tomorrow to test it more.

So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App

handle223 said:
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
From my tests:
- had to reinstall whole system because of force close errors after changing nbh...
- 3g works, camera works, bt probably works (it enables, so probably it works ;-) )
- cannot even enable wifi
- probably location don't work (I wait about 15 minutes without results)
- didn't check gps

for me on pola200 camera doesnt work... bt activates, but wlan as with all devices - not working. feeling pretty smooth with this kernel...

Wifi fix - new 26/08/2010 kernel
dzo said:
I've fixed wifi on the 2.6.32 kernel. Attached is the new module, put it in /system/lib/modules. You'll also need the very latest kernel. I made some very big changes to the sd driver so this could break other things..
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...

tiagoclc said:
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
Click to expand...
Click to collapse
Thanks, now wifi can be enabled ;-)

hello all
maybe a stupid Question how can I put the wlan.ko in the lib module
kisses
Rose Red

Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.

vArrow said:
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
Click to expand...
Click to collapse
No, You don't have to reinstall. You can mount /system partition rw and replace old one wlan.ko in /system/lib/modules/

Use this android update

thx all for your help
kisses
Rose

haret
Did someone try haret already? I've problems with zimage 2.6.32 ...it hangs on startup...can someone drop here the haret.exe, initrd and default.txt ?
Hugs

[REQ] Source CM6.1.2 WiMax Alpha 3

I have looked and been unable to find any links to source for CM6.1.2 WiMax Alpha 3. A tar.gz would be ideal but git-hub works as well as I can pull the tar from there. The reason for the request is to create a CM6/WiMax/HDMI release with full HW acceleration for those that need the pointer support that 6.1.2 provides.
I have tried the one SZ kernel that's available but it has the USB bug and HW accel detect issues and would rather start from a clean slate. Any help on source would be great. Thanks.

Lokifish Marz said:
I have looked and been unable to find any links to source for CM6.1.2 WiMax Alpha 3. A tar.gz would be ideal but git-hub works as well as I can pull the tar from there. The reason for the request is to create a CM6/WiMax/HDMI release with full HW acceleration for those that need the pointer support that 6.1.2 provides.
I have tried the one SZ kernel that's available but it has the USB bug and HW accel detect issues and would rather start from a clean slate. Any help on source would be great. Thanks.
Click to expand...
Click to collapse
It's the same kernel that is being used for CM7. You can roll that back if you want.
Also, why would you want a CM6 ROM when CM7 RC3 just came out?

ViViDboarder said:
It's the same kernel that is being used for CM7. You can roll that back if you want.
Also, why would you want a CM6 ROM when CM7 RC3 just came out?
Click to expand...
Click to collapse
So Alpha3 Froyo is actually a GB kernel? Didn't know that.
I'll check the RC3 change log to see if BT KB/mouse issues have been fixed. If not then still stuck at 6.1.2.
(update) Can find no mention of pointer support on CM7 other than requests. Nothing listed in change log.

Lokifish Marz said:
So Alpha3 Froyo is actually a GB kernel? Didn't know that.
I'll check the RC3 change log to see if BT KB/mouse issues have been fixed. If not then still stuck at 6.1.2.
(update) Can find no mention of pointer support on CM7 other than requests. Nothing listed in change log.
Click to expand...
Click to collapse
The android-x86 project doesn't even have this working yet so it will be a while before cm7 gets it.

spiicytuna said:
The android-x86 project doesn't even have this working yet so it will be a while before cm7 gets it.
Click to expand...
Click to collapse
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.

Lokifish Marz said:
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.
Click to expand...
Click to collapse
Merge the patches from the CM7 kernel in to your CM6 kernel then if you don't like the CM7 kernel.
That's the source...

Lokifish Marz said:
That's what I figured, so hopefully I can find source for froyo alpha3. If I don't get anything from this Q&A post I'll contact shinzul directly.
Click to expand...
Click to collapse
Why would you want to do this? The kernel from cm7 will boot cm6. The cm7 kernel is not specific to gingerbread.

spiicytuna said:
Why would you want to do this? The kernel from cm7 will boot cm6. The cm7 kernel is not specific to gingerbread.
Click to expand...
Click to collapse
Was having mouse cursor issues when I tried that but not on the stock alpha3.

Also... Rather than wasting time porting HDMI back to an old rom, why not work on a patch for pointer support in CM7?

Lokifish Marz said:
Was having mouse cursor issues when I tried that but not on the stock alpha3.
Click to expand...
Click to collapse
ahh; then merge the patches from the CM7 hdmi opensource kernel into your CM6 kernel and you'll be golden...but then the question starts to be why not work on porting the hid/mouse support from cm6 to cm7 which seems like the more logical choice of time to benefit all as most people aren't going to want to fall back to cm6.

spiicytuna said:
ahh; then merge the patches from the CM7 hdmi opensource kernel into your CM6 kernel and you'll be golden...but then the question starts to be why not work on porting the hid/mouse support from cm6 to cm7 which seems like the more logical choice of time to benefit all as most people aren't going to want to fall back to cm6.
Click to expand...
Click to collapse
I agree that it does make more sense try to port hid/mouse to cm7 but I still haven't found/seen a real fix to the slow usb issue on the new kernel. My linux is also a bit rusty.

As a reminder, since that build is no longer distributed, the source no longer needs to be made available. The GPL only requires source availability on distribution. If you didn't retrieve the source when the distribution was made available, there's no requirement for kernel devs to go and find a valid point of reference after the fact.
When the alphas were released, the kernel source was made available. The links to the source were removed at the same time the primary distribution link was removed.

agrabren said:
As a reminder, since that build is no longer distributed, the source no longer needs to be made available. The GPL only requires source availability on distribution. If you didn't retrieve the source when the distribution was made available, there's no requirement for kernel devs to go and find a valid point of reference after the fact.
When the alphas were released, the kernel source was made available. The links to the source were removed at the same time the primary distribution link was removed.
Click to expand...
Click to collapse
Oh well. Back to square one.

My memory is a little fuzzy, but I'm pretty sure that we were recommending a 2.6.34 kernel with Alpha 3. It took me but a few minutes to come up with:
https://github.com/toastcfh/cm-kernel/tree/android-msm-2.6.34/
Of course, this kernel has it's own "sleep bug" in that it doesn't let the phone go to sleep at all. Not exactly good for battery life, but you're welcome to fork it and make your own changes.
Use the switch branches dropdown if you want to try one of toastcfh's various 2.6.35 branches instead, but I'm pretty sure those have the USB bug.

Dees_Troy said:
My memory is a little fuzzy, but I'm pretty sure that we were recommending a 2.6.34 kernel with Alpha 3. It took me but a few minutes to come up with:
https://github.com/toastcfh/cm-kernel/tree/android-msm-2.6.34/
Of course, this kernel has it's own "sleep bug" in that it doesn't let the phone go to sleep at all. Not exactly good for battery life, but you're welcome to fork it and make your own changes.
Use the switch branches dropdown if you want to try one of toastcfh's various 2.6.35 branches instead, but I'm pretty sure those have the USB bug.
Click to expand...
Click to collapse
Sounds like a game of pick your poison....what do you want more and what can you live with?

spiicytuna said:
Sounds like a game of pick your poison....what do you want more and what can you live with?
Click to expand...
Click to collapse
That's my kinda game!