Related
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.
Hi devs,
I was trying to compile the eclair AOSP with hero profile. Everything compiled correctly and it boots up on my hero but why does my touchscreen not work??
Anyone could give me a hand on why the touchscreen is not working on my hero? I am using godmode kernel.
Thanks in advance,
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
maxisma said:
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
Click to expand...
Click to collapse
Thanks Maxima!
But this is for Froyo or also working for eclair?
And another question is it a special kernel config that I need to enable for the touchscreen to work? As I did use a working .config from another 2.1 rom.
Giving those files a go anyhow
Argh! I recompiled the kernel with the config from the kernel you posted. But still touchscreen does not work..
Also the unlock (pincode) screen does not popup so I cant make any calls.
Can anyone please give me some hints on why this is happening?
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
dipje said:
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
Click to expand...
Click to collapse
Ah! Thanks. Recompiling
btw and what about the pincode popup issue? Why am I not getting that popup when starting the phone?
Works! Nice! Thanks. And my other Question? Pincode unlock is not poping up. I cant get a signal from my provider
Anyone has a clue?
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Shakor said:
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Click to expand...
Click to collapse
RIL-library..
maxisma said:
RIL-library..
Click to expand...
Click to collapse
Cool. Thanks checking this out.
Still no joy.. Argh
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
Hi all,
I have Fat Free Froyo installed with the latest 14th Jan 2011 kernel voguimg-240x320-2.6.32-froyo-14-01-11_14.nbh edited to froyo & panel type 2 from t029000.massey.ac.nz but Google Goggles needs ipv6 support.
Is this a kernel problem or a problem with the build itself? I am experienced in linux, so can modprobe or insmod the ipv6.ko but I don't know where to get it from
Any help would be appreciated!
(message for kernel's developers) take this man! he can dev ipv6!
Jumping the gun there a bit
I triage bugs and work on stuff for Ubuntu. Have also ported a few linux bits to ppc64 (PlayStation 3).
I'm pinching the ipv6.ko from slayhers latest kernel build, hopefully that will work insmod-ding or modprobing it into the kernel thru the terminal on the Kaiser itself.
So, fingers crossed, this may be solved in 5 minutes!!
Didn't work, it must be compiled for a different platform...
Anyone have or know where to get a kernel for the Kaiser with ipv6 support, or failing that the correctly built ipv6.ko for the Kaiser so that it can be insmodded?
Getting it compiled in the kernel is the easy bit, although it does use up a lot of space which is limited in the kaiser's kernel so a little tweaking is needed. Getting it to work with the Kaiser's modem and the builds we currently use is a different matter unfortunately. It will take a bit of modding for it to work but it's more then achievable with a bit of free time. Wish i could buy that stuff!!If i get a chance i will get you the ipv6 module for the kaiser's kernel or a kernel with support for it so you can have a play.
I definitely look forward to it! If I knew how and what to modify I'd do it myself, but I thought arch-specific kernels had to be compiled on the arch itself? If that's the case, I can see how free time would be needed, it'd take hours or days to compile the linux kernel at 400MHz
I have compiled kernels before so if/when I learn how to do it myself, I could start to use my own git repo for more recent daily builds or something.
I'm also thinking about starting working on some *buntu stuff (I know Ubuntu is there for the Kaiser, but soem tweaks would help if I get a chance.)
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
xteejx said:
Hmm, a little Googling goes a long way http://www.androidonhtc.com/wiki/Get_Involved << was hard to find that,so hopefully I can add ipv6 somewhere in the 'make menuconfig' options for the kernel.
Are the standard kernel options used by "make vogue_defconfig" ok to use, i.e. will it build a normal useable kernel so that everything works?
Click to expand...
Click to collapse
Yes, that is th correct make file to use. I have built the kernel with IPV6 support, haven't tested it but have attached the module to the post for you to try
Brilliant! I'll try it sometime within the next couple of days, although I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build, but I haven't economised too much.
I can see the the options for ipv6 in the ncurses menuconfig, so I guess it's just a case of enabling it and building the zImage right?
I seem to be having the old problem with the wifi though, and I know it's kernel related, but there are only patches for it, i.e. the wlan.ko, but can't see how to implement it myself so it's an all-in-one solution
When I get the hang of the Kaiser hardware properly, I might just push through a newer kernel from the armlinux site so watch this space
xteejx said:
I might myself be working on a blazing fast kernel specifically for the HTC Kaiser, and it is SERIOUSLY!!!! fast, even at 400MHz I can notice a massive increase in speed with the exact same build
Click to expand...
Click to collapse
How have you managed that??? What have you done?
I have no idea how it happened, perhaps the other devs add a load of useless options, but all I did was follow the instructions at that link above and compiled a zImage from the 2.6.32 arm branch, using the 2010 arm tools. Used NBHeditor to edit it for Kaiser, panel 2, froyo, flashed it and bang (not literally thank god).
I can't answer any better than that. I used the default options (for now at least) that the vogue build script uses for the kernel, but bluetooth, camera and gps work. No internet connection as yet either through the network or wifi, dumno what I've missed there, and no ipv6 (but can add that easily enough). Wifi doesn't work either, but I'm working on it, although that MAY be the reason why it's so fast...maybe it's missing a few options...still unsure at this point.
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
xteejx said:
I notice that although this is an open community, and people attach NBHs, there are no changelogs or anything showing what the people have done with the kernel to implement some options, so it's kinda holding me back at the minute.
Click to expand...
Click to collapse
That isn't true, all tested changes are pushed to git, you can see what has been changed and how from here: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
*facepalm!*
Didn't see that, will bookmark it and keep an eye on it, perhaps work with it. Thanks for the link
the androidhtc.com site is not related directly to the develop project because no developer is connected to it. Also the git repository it not hosted in linux to go but on sourceforge (so download the correct git). That site is very outdated.
wifi works if you use the correct branch (on sourceforge) and modules.
Am I right in thinking that http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD is the prebuilt kernels and nbhs from the source at http://androidhtc.git.sourceforge.n...og;h=62f075ddd13f378fd252be94c77e4f93d12584fb ??
I think I'm looking at the right tree now.
Flashing the latest NBH: VOGUIMG-320-FROYO-01-16-11.NBH still gives me the wifi error. Do I need to manually add the wlan.ko to it or ??
I could've sworn that an NBH I flashed before had all that in the NBH and it worked fine.
Ok, got it back to how I had it:
Flashed latest.NBH from http://androidhtc.git.sourceforge.n...7c0bf5edc4f5c6d64ce4df29254e8332ce26b;hb=HEAD and dropped androidupdate.tgz to the /andboot folder of the SD card, installed update thru the boot menu and done.
So in reality there's nothing stopping me grabbing the same kernel source, building it and adding ipv6 support in the ncurses kernel config menu and making an NBH from it and flashing that over, and then doing the androidupdate.tgz, although I think with HTCFlasherGUI you can flash a zImage directly right??
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
xteejx said:
Is there something wrong with the git at http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=summary I can't get access, it's showing old stuff. It looks closed since git clone rejects me
Click to expand...
Click to collapse
No, nothing wrong with it. Just do:
git clone git://androidhtc.git.sourceforge.net/androidhtc/kernel.git
You then need to set it to the correct branch using 'git checkout -b <branch you want> '
It's the 2.6.32 branch you are interested in, you can find out exactly what it's called using 'git branch -a' which will list the available branches.
Cool. Knew something went wrong somewhere, had to be me lol!
I added that ipv6.ko to the NAND via a androidupdate.tgz (only way I could do it), and it didn't work, something about incorrect module format (or something like that).
Are there any prebuilt kernels or NBHs for the Kaiser that include ipv6? Either as a module that I can insmod it in the terminal or built-in?
I hate being upstaged by people that can use Goggles without any problems.
I know slayher's kernels have ipv6, but I flashed the new stock one from http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/ and it didn't work. I mean the kernel did, but Goggles didn't - couldn't insmod it either - same invalid module format as the ipv6.ko scooter did for me
Also the git clone didn't work:
Initialized empty Git repository in /home/name/android-git/kernel/.git/
fatal: The remote end hung up unexpectedly
Hi guys, only few words:
I'm working on a 3.10 kernel just for fun, i dunno if i'm able to make it stable.
If someone want to help any help is appreciated!
it's based on LA.BF.2.1.2_rb1.5 CAF branch
source code is here branch LA.BF.2.1.2_rb1.5 and test_usb
test boot.img is here: http://www58.zippyshare.com/v/eqVBaQhc/file.html
Working list:
- it boots!
- touch screen
- backlight
- sms and call
- audio
- Bluetooth
- NFC
- 3D Graphics
- adb
everything else is not working. use it with a usb cable plugged in or it will not work.
Major issue atm: it doesn't work without usb plugged in.
thanks to @myfluxi for his caf kernel & ROM
thanks to @Sultanxda for some suggestions
That's a good news! Maybe @myfluxi can help?
Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
Very interesting project. I'll keep an eye on this. I'm also available as a tester if you want [emoji5]
Sent from my Nexus 5 using Tapatalk
Interesting.
How did you get past what this guy said?:
Sultanxda said:
Stopped working on it :/ I managed to get modem firmware to load (modem still doesn't work), but 3.10 as a whole has one big problem on the Nexus 5: proprietary TrustZone (TZ) firmware. 3.10 is much, much more reliant on TZ than our 3.4 kernel. 3.10 is so reliant on TZ that the CAF 3.10 branch does not boot with the latest PM (power-management) drivers (I had to use the 3.10 source from the LG G Watch as a base to get this completely booting). There are scm calls to TZ everywhere in 3.10, and in particular all versions of 3.10's PM code are broken to some extreme degree with our ancient firmware (kernel always crashes on CPU idle power collapse). I'm sure it's possible to make everything work with our firmware, but you'd likely need to know things that only Qualcomm engineers know, such as the actual internals of the TZ firmware to see where there are incompatibilities between TZ and the new kernel (TZ firmware source code is confidential/proprietary, so it is not available to the public).
Click to expand...
Click to collapse
nagalun said:
Interesting.
How did you get past what this guy said?:
Click to expand...
Click to collapse
probably because now CAF source has got more patches than 1 year ago! maybe they used patches that already were in lg smartwatch source, who knows... luckily now we have got a booting CAF kernel
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
nagalun said:
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
Click to expand...
Click to collapse
thanks for the tests, adding to OP
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
I hope you get the help, collaboration and input you need to succeed!
3.10.x on N5? OMG Yeeees
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Creative9170 said:
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Click to expand...
Click to collapse
read from here to here, replace the kernel version in the url from 3.4 to 3.10 to get all improvements over the time. yes, backport features from 3.x/4.x to 3.4 will lower the gap between 3.4 and 3.10 but there's a motivation if newer devices use 3.10 instead backport stuff (caf will drop support for 3.4 sooner or later)
blackbird5308 said:
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
Click to expand...
Click to collapse
i'll take a look
small update:
got adb working (using 3.4 driver), now it's easier to debug for everyone!
http://www58.zippyshare.com/v/eqVBaQhc/file.html
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
kwjhgjh said:
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
Click to expand...
Click to collapse
Hi!
I already knew that those things are broken, i'm working on it
rmbq said:
Hi!
I already knew that those things are broken, i'm working on it
Click to expand...
Click to collapse
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
kwjhgjh said:
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
Click to expand...
Click to collapse
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
rmbq said:
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
Click to expand...
Click to collapse
'hilarious' means...unfamiliar vocabulary to me, but enough to understand your purpose.
I think to consider my main rom as CM-Caf. Good luck to your project!
I'll waiting your work. d=_=b
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
rachanta said:
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
Click to expand...
Click to collapse
i don't know where is the problem atm, i don't think it's related to USB drivers, sultanxda said it's TZ related... it isn't easy to track, i saved a log with something more than "watchdog bytes". also i don't know if LA.BF.2.1.2 is a good base, some drivers (ex adreno) are older than LA.BF.1.1.3 (our caf 3.4)!! xperiadev are working on LA.BF64.1.2.2 also for msm8974 soc, that branch is very up to date but i can't get it boot on hammerhead, and i don't know if they can get it boot on xperia devices with msm8974 soc...