Database Info

Htc kernel source

oh my god!
http://developer.htc.com/
ps: sorry if it is already posted!
pps: it's kernel source of htc brand phone or not?

So, what now?
So what's the real benefit of that. Sorry for the noob-ish question...

nk02 said:
oh my god!
http://developer.htc.com/
ps: sorry if it is already posted!
pps: it's kernel source of htc brand phone or not?
Click to expand...
Click to collapse
WTF! Man this is fantastic, thanks!

You could always cook it your self!

This is only the binaries for the device. As cc said, the kernel you make yourself. What we need is the source for the proprietary parts to make things like bluetooth work on hero among other things

Quick, someone alert cyanogen!
*edit* **** ^

jubeh said:
This is only the binaries for the device. As cc said, the kernel you make yourself. What we need is the source for the proprietary parts to make things like bluetooth work on hero among other things
Click to expand...
Click to collapse
Damn I spoke before I checked the link. Ya it's just the plain old HTC kernel source and useless proprietary binaries. I thought it was going to be their entire source for their Android build. Crap, move along people. Nothing to see here

You can extract all of the proprietary binaries from Hero using the extract script included in dream-open when you repo sync!

shafty023 said:
Damn I spoke before I checked the link. Ya it's just the plain old HTC kernel source and useless proprietary binaries. I thought it was going to be their entire source for their Android build. Crap, move along people. Nothing to see here
Click to expand...
Click to collapse
On the contrary, it has the source for their previously-proprietary kernel bits required for the canadian dream and magic devices, which means it should now be possible to build custom kernels for those devices for true and proper root/customization without the need for the death-spl. This is something that we've been fighting them for.

Just gave the source a quick look through. All of the default kernel settings/commits you would pull down from git are absent, that is, nothing is really set. I'm gonna cook it really quick without any fussing around with it to see what happens.

Man to bad they dont have the hero source as well but thats great.

The kernel is in the oven right now. I literally only changed two things for better performance, other than that this thing is stock.
Implemented CFQ and SLUB.

lbcoder said:
On the contrary, it has the source for their previously-proprietary kernel bits required for the canadian dream and magic devices, which means it should now be possible to build custom kernels for those devices for true and proper root/customization without the need for the death-spl. This is something that we've been fighting them for.
Click to expand...
Click to collapse
As CC stated previously, these can be extracted using the htc script from those devices. I didn't see anything that we couldn't already grab (IE libhtc_ril.so)

ccyrowski said:
The kernel is in the oven right now. I literally only changed two things for better performance, other than that this thing is stock.
Implemented CFQ and SLUB.
Click to expand...
Click to collapse
Hmmm should be interesting to see what results you find.

I cooked the kernel, wlan.ko, and modules. Those are all the files you should need. I'm at work right now, but when I'm home ill throw in a ramdisk to make the boot.img.
Does anyone here know how to mkbootimg boot.img so I don't have to make a million of them for every ROM out there? Or at least I'll make one for a cupcake ROM and one for a HERO ROM

Sorry for the total noobness but does this mean we can have .odex in builds now?

shafty023 said:
As CC stated previously, these can be extracted using the htc script from those devices. I didn't see anything that we couldn't already grab (IE libhtc_ril.so)
Click to expand...
Click to collapse
You might want to read some of the retardedly long root-rogers-dream threads. There is indeed a bunch of kernel code that we can't extract/reverse engineer without a huge effort. Those files pulled by the extract scripts are NOT RELATED. The difference is in the actual kernel.

I TAKE ABSOLUTELY NO RESPONSIBILITY FOR WHAT THIS DOES TO YOU PHONE.
I HAVE NOT TESTED IT.
I WHIPED IT UP ASAP SO YALL COULD FUX WITH IT.
I imagine you'll get partially through the boot process then it will loop. The again, maybe it will work. Who knows. Please provide me with a logcat if you try this.
You cannot flash the zip file. You cannot fastboot flash the boot.img-kernel. You must mkbootimg boot.img-kernel and ramdisk.cpio.gz to make boot.img.
wlan.ko is for wifi and goes in /system/lib/modules
modules.sqf go in /system/modules
Enjoy.
http://demarcatedmedia.com/rom/stockkernel.zip

no brave souls eh?

I'd test it if I knew what you were talking about Don't have ubuntu up and running, creating a VM right now using virtualbox. I have no idea how to compile mkbootimg though.

Building Android from source for Nexus S

EDIT: Oops, I meant to put this in General section. Sorry!!!
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
The first one is that there is of course no Google Apps. I understand why, but is there a good source for them? Or do the ones for CM7 work?
Second, I get the regular Android boot animation, not the cool Nexus S one. Is that normal?
Third, my Android version always says something like 3.1.x.x.x.x.x or something crazy. Is that normal? I was kind of expecting it to say GRJ22 2.3.4 or something like that.
I am trying to build full_crespo-user, FYI.

I use the normal gapps whenever I compile an aosp. Try the modded one specific for the nexus s. You would find it in the last pages of the nightlies thread.
Yes. The android marine blue animation is the default one for aosp.
The version number you are getting 3.1.xxzzxxxxxxxxxz is quite normal. This is the actual version of aosp. You can change it in your build.prop if you want to.
Good luck/
Sent from my Nexus S using Tapatalk

matt2053 said:
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
Click to expand...
Click to collapse
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
no need to pull them. anyway official binaries are available for the nexus s
http://code.google.com/android/nexus/drivers.html

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
Yes, pull from the gingerbread branch! Master is almost always full of bugs and not the best to build. You know you have master when the build number is pi (the 3.1.4... one mentioned earlier).
To use repo to pull down the gingerbread branch, use the repo init command as usual but add "-b gingerbread" at the end (no quotes).
Sent from my Nexus S

I would love to know more about this master vs gingerbread branch difference. I've been building from master it seems. What purposes do the different branches serve? Can someone shed some light on the Android development process?
Sent from my Nexus S using XDA App

So master basically contains everything, all versions. Master is basically all of android xD
Now, you can do a -b gingerbread to just clone the gingerbread branch, which will give u the 2.3 code for everything on android.
** Note -b can also be used for froyo, eclair, etc. **
I hope this helps!

Not development. Moved to Q&A.

I have another question so I am bumping this up:
I have successfully build Android 2.3.5 for my Nexus S. Is there anyone who might help me adding Google Nexus boot animation and Google Apps, and putting it all into a flashable zip?

I figured out the zip thanks to this awesome thread: http://forum.xda-developers.com/showthread.php?t=732957
Now my problem is the keyboard. The "suggested" words are only names from my contacts, I don't get any regular English language suggestions. Any ideas?

[DEV][SCRIPT][HOW-TO] Build MR GB 2.6.35 without thinking? WAHTS!?

Hey guys lithid here again with another helper script, and how-to. As some of you may know I have recently decided to start building kernels. While I still work on roms, I found kernels to be strange, and sometimes difficult. So instead of taking that knowledge and holding it to myself, I figured I would release it here and hopefully it could open the doors for more people working on kernels.
Basically I created a script, that would do the entire build process for a kernel, it would copy the config you want from arch/arm/configs, assigned the compiler, then compile the kernel. Now after the first time I compiled this I did a copy and paste to Koush's AnyKernel updater, while that was fine and only took a min or two, I found it really annoying to do it everytime, specially when I am testing changes to the compiled kernel. So I added in a any-kernel folder to my built environment. I also added the tool-chain compiler I would be using as well into my repo.
AnyKernel folder
Cross Compiler
Now this was great. I didn't have to build anything manually, all's I needed to do was sign the zip and then push it to my phone.
Then I thought (being so lazy) why not just have this script auto-sign the zips for me and place them in my home folder? So I did. I also added in my own keys so the signature is mine! =P
Auto-Sign
Now for the fun stuff, recently there have been some roms out there that use a slightly different flashing method. Well I solved that as well. Now the script not only builds one update.zip for the compiled kernel. It creates 3 one for each rom type.
Synergy Nightly
Synergy Godmode
Universal (All other sense roms)
Click to expand...
Click to collapse
So everything is basically done. Devs would be able to implement my script into their kernel environment to build kernels for all roms that are supported here on XDA.
How to:
NOTE: You will need to get a list of applications installed and be running linux for this to work. I used Ubuntu 11.04 for all my building needs. If you want a quick list of packages you will need to install first click here there you can install corresponding packages to compile this.
Code:
git clone https://[email protected]/lithid/Htc-Sense-Freedom-Kernel.git
cd Htc-Sense-Freedom-Kernel
./build-it.sh {version #}
That's it!
Here is an example:
Error:
Code:
[email protected]:~/Development/Htc-Sense-Freedom-Kernel$ ./build-it.sh
Written by Lithid
[Error]: Expected 1 parameter, got 0.
Usage: bash build-it.sh v# [BUILD VERSION]
Good:
Code:
[email protected]:~/Development/Htc-Sense-Freedom-Kernel$ ./build-it.sh v0.3
Here is a link to the script if you are interested in seeing what I wrote. Of course it will be updated over and over again. Just figured this would be something Devs and/or users who are inspired to be devs to build a kernel without no knowledge really.

This is nice, very nice. I think I would start with building the AOSP source first. But by the time I've done that, this'll probably be finished! So thanks for the information!

This looks pretty nice thanks for the right up and links I'll definitely be checking this out some more when I get to my PC.
Sent from my PC36100 using XDA App

Love it bro. Good stuff
Oh, is mdpi still an issue with this tutorial? =P

barnacles10 said:
Love it bro. Good stuff
Oh, is mdpi still an issue with this tutorial? =P
Click to expand...
Click to collapse
Yes, how did you know?
Sent from my PC36100 using XDA Premium App

You are the android king
Sent from my PC36100 using XDA App

Lol'ed so hard at this line in the script.
"function just_sign_the_fucking_zip()"

RileyGrant said:
Lol'ed so hard at this line in the script.
"function just_sign_the_fucking_zip()"
Click to expand...
Click to collapse
Gotta have some fun sometimes huh? It gets lonely writing scripts sometimes, I like to add a little bit of personality to my stuff. lol

lithid-cm said:
Gotta have some fun sometimes huh? It gets lonely writing scripts sometimes, I like to add a little bit of personality to my stuff. lol
Click to expand...
Click to collapse
thanks to that.
post 700 lol.

Holy crap!! Ran the script and right out of the box it compiled and everything is there! This is great! Now I can start poking around!

lithid-cm said:
Gotta have some fun sometimes huh? It gets lonely writing scripts sometimes, I like to add a little bit of personality to my stuff. lol
Click to expand...
Click to collapse
Exactly and gnomelook might be somthing 4 you if you like to change ubuntus look ^^
Sent from my PC36100 using XDA Premium App

I really been wanting to learn to make kernels but AOSP searched round some think you could steer me in the right direction?

Dozenboy0012 said:
I really been wanting to learn to make kernels but AOSP searched round some think you could steer me in the right direction?
Click to expand...
Click to collapse
I would look into the cyanogenmod kernel. It's on cyanogenmods github.
Sent from my PC36100 using XDA Premium App

Is smartass better to run or performance better? Alot of people been talking about smartass
Sent from my PC36100 using XDA Premium App

smartboy36 said:
Is smartass better to run or performance better? Alot of people been talking about smartass
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
It depends on what your looking for, try them each out and see which works better. Every phone is different.
Sent from my PC36100 using XDA Premium App

smartboy36 said:
Is smartass better to run or performance better? Alot of people been talking about smartass
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I tend to stick with smartass, oh wait we are talking about the kernel...

They both are working so perfectly but performance is my favorite
Sent from my PC36100 using XDA Premium App

Hey lithid, is there a way to do this without Linux? I don't have an extra pc? Thx man
Sent from my PC36100 using Tapatalk

gotshores said:
Hey lithid, is there a way to do this without Linux? I don't have an extra pc? Thx man
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Not unless your computer is a mac. Building on windows is currently not supported.

This is a noble effort but what happens when a user wants to add/subtract to/from a kernel and they are not familiar with c/c++? Copy/paste will go so far especially if they can't tell the difference between a newer version of source code on someones git and the original.
Actually understanding the source is a better way of learning to build kernels instead of having an auto script do everything.
I just finally got a stable gingersense evo kernel built because certain edits (which worked on froyo kernels) would cause the kernel to lag and wifi to throw errors. If the user doesn't know how to troubleshoot, this script becomes almost moot.
I only use two scripts when I compile kernels; one to set the cc, clean the build dir, and open the dir in nautilus and the other to boot my phone into recovery to push the modules then boot into fastboot and flash the zImage.
Again it's a noble effort but things like this (and dsixdas kitchen) make it too easy for novice users to make/build these items and we end up with dozens of threads of base build items that either don't present anything marginally better than the last or unstable items due to the lack of knowledge needed to provide extended support. Dsixdas kitchen is a great tool for saving time (I use it too but learned how to root a rom by hand) but it makes it too easy for novices to build roms.
Sorry for the longwinded post and I'm not bashing the effort...just trying to point out that some things should not be made so easy for specific reasons.

[HowTo][I9003][XXKPH][Kernel] Compile vanilla kernel from sources

To make it perfectly clear: This is a vanilla development kernel. It has absolutely no features the stock kernel does not have (no ext4, no OC, no nothing). But it may cause problems (SOD, eat battery, the apocalypse... you get the idea). This kernel only exists, because all earlier efforts to compile a stabel kernel have not been successfull.
EDIT: And this one isn't either. SOD-issue not solved - may occur less often, though. I'm not releasing the kernel, because it remains faulty.
EDIT2: Samsung released new sources on the 18th of November. Use these and the new toolchain instead!
First things first: The setup.
The Samsung GB source is used. Extract it to a new directory - do not copy it over the Froyo sources, simply because it says "Update1". You should now have something like
Code:
/home/<user>/<working_directory>/Kernel/...
and a folder for the platform - the latter will not be used.
The toolchain is from Codesourcery: Sourcery G++ Lite 2009q3-68 for ARM EABI. Extract it to wherever you like. Just remember the path (<your_path>).
The path to the toolchain, and the correct EXTRAVERSION are adjusted in the Makefile. Nothing else. The EXTRAVERSION is different for every firmware - see: settings => about phone.
Code:
cd /home/<user>/<working_directory>/Kernel/
gedit Makefile
Look out for:
Code:
...
EXTRAVERSION=.7-CL467143
...
CROSS_COMPILE=/<your_path>/toolchain/arm-2009q3/bin/arm-none-linux-gnueabi-
Thanks to Skin at this point, for his helpful tips!
A little spring cleaning is performed
Code:
cd /home/<user>/<working_directory>/Kernel/
make mrproper
This will delete all precompiled files and the config.
The config is extracted directly from the device with
Code:
cd /home/<user>/<working_directory>/
adb pull /proc/config.gz
gunzip config.gz
cp config /Kernel/.config
What happens after setting up everything:
The kernel is compiled.
Code:
make
The Samsung readme recommends another alternative:
Code:
make android_latona_r08_eng_defconfig
make
Do not run this, if you want to keep the .config from the device intact! This will overwrite it, and you will compile with different settings than the kernel on your i9003.
With the help of Skins unpack-repack-tools (look here), a flashable PDA is created. The CF-root normalboot.img from the 21.08.2011 is used as a basis (I like this one, no special reason ). Only the zImage is replaced with the self-compiled kernel.
The PDA is flashed with ODIN.
After the first reboot, the cache and Dalvik-cache are cleaned in CWM.
Have fun testing! And remember to make a nandroid backup. If you want to go back, flash Skins original CWM, and restore the nandroid backup afterwards.

What do you mean by stable here,XXKPH is quite stable for me

yamchirobe said:
What do you mean by stable here,XXKPH is quite stable for me
Click to expand...
Click to collapse
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.

vishal24387 said:
Dude he is talking about custom kernal & not about stock kernal. Problem with gb sources is that whenever we compile a kernal it has SOD problem. So this thread is suggesting info how to build a stable kernal.
Click to expand...
Click to collapse
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App

ronhoover88 said:
There is no problem with the sources...it depends on how they compile the kernel...that is causing the bugs!!
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Do u mean that source code.is correct then skin said that it is not compatable & codes are older. I have used skin & amit's oc version. Both have sod problem Are they doing any mistake in compiling kernal?? Please clear doubt.

No what i meant was the sources which were released (could be) for the dev releases XXKP7/KP9/KPE may be after next official update...we could have GB sources!!
Sent from my GT-I9003 using XDA App

You should post here the kernel so more people will test it.... if you have solved SOD and oher issues i can say that you are great... BTW good work, with your explanation many other people can try...

Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...

XDA_Bam said:
Seems I didn't - phone didn't wake from standby this afternoon.
But I noticed, that it did respond. I could change speaker volume, the soft keys were lid - only the screen remained black. I'm getting really curious...
Click to expand...
Click to collapse
I study on it.... the different between normal sleep and SOD is that, if you have a SOD, when you press the button to wakeup the phone the proc modemctl doesn't work and also the display driver cannot be activated.. i'm not sure if modemctl is responsable of turning up the LCD but this is what i found...

Another thing.... can i say now that must be something wrong in the sources?

Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.

XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
I wrote again to sammy;
Here my 1st email:
Hi again. I apologize but i have to ask something else.
I try again to build the kernel with the KPH source and i have the same issue (some time cannot wake - up from lock - sleep).
I follow perfectly the guide on kernel compilation so i really don't understand why that issue happen.
I have to insist on the fact that the source is not completely updated or maybe i'm doing something wrong.
I'm saying that the source are not updated cause the issue is part of precedent GB release but not of KPH.
Wish that you check again and report me if i have to do something else.
Thanks again
... they didn't answer so i wrote another:
Hi, i'm sorry but i have to write again. I tryed many times to compile a working kernel and what i build works correctly except that sometime the phone cannnot wakeup from sleep.... we ( me and other xda members) call this SOD. Also other members have compiled the kernel with your source and all have the same problem.
Please, check the source, they cannot be for the XXKPH FW. Or, at least, show us how to solve our issue.
THIS IS THE ANSWER:
Thank you for your continuous interest in our product.
This web site is intended to provide Open Source Software used in our product.
As mentioned previous mail, some of samsung proprietary codes are not included in the kernel. (codes that are not affected GPL - loadable modules) Please understand we do not guarantee opensource code is executable in target device.
We are sorry for not giving you an correct anwser upto your satisfaction.
Please accept our apology for not being able to handle your request up to your satisfaction.
Best Regards
You may find the source code

and if someone can explain me the meaning of "You may find the source code" woud be great....

XDA_Bam said:
Hmmm... I just checked: The last edit made in the GB kernel source files is from the 28. of June. There is no way, these are the XXKPH sources.
Click to expand...
Click to collapse
xcuseme bro... 28 June = KPH? Can you explain better?

Skin1980 said:
xcuseme bro... 28 June = KPH? Can you explain better?
Click to expand...
Click to collapse
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App

When i send source codes to doomlord related to usb otg he also mentioned that 'source codes are always present some what in broken form. They never provide complete source code. We have to manage with that'.
May be doomlord know better about this matter.

Mother effin sammy. Proprietary? it's not even proprietary information that we're asking for. We are just asking complete source codes that function properly. Is it something that they own that makes fix for the SOD? I freakingly don't believe so? Can someone pm me their email address?

go to samsung opensource, search for i9003, then send a message

ronhoover88 said:
These are old sources for XXKPE and below builds and not for XXKPH i guess coz XXKPH was built in august
We better wait for next official GB release and hope they release latest sorce codes...
You better continue with your OC kernel for froyo now...
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
Everyone of us might write to sammy... for the kernel i'm sorry but i really don't intend to go back to froyo.... haven't enouth time....

I have a suggestion. We have 3-4 gb releases present with us by samsung. Firs gb source was facing SOD problem a lot. But after that in later version till kph they removed problem successful. Can we compare those kernals & find the differce & come to know what exact changes they have made in kernal so that they reached to stable kernal of kph.

[Q] SGS4 custom rom on emulator

Hi,
Is the above possible? I found some guides for CYM but none for our phone...
any advice would be highly appreciated
10x
Alon

They aren't finished building cm for our phones yet... They are working on it though. Add for
an emulator, I asked that question a long time ago and I was told since there are so many Android devices and each one is different it would be useless for the manufacturer to build an emulator... The only way we could have one for our phone is to build it ourselves... Which would required a butt load of time and knowledge of many different things like Java, Linux, kernel building, scripting, etc...
Sent from my SGH-T959V using XDA App

thomas.raines said:
They aren't finished building cm for our phones yet... They are working on it though. Add for
an emulator, I asked that question a long time ago and I was told since there are so many Android devices and each one is different it would be useless for the manufacturer to build an emulator... The only way we could have one for our phone is to build it ourselves... Which would required a butt load of time and knowledge of many different things like Java, Linux, kernel building, scripting, etc...
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
so currently there is no way we can test our ROMs on emulator?

alon2 said:
so currently there is no way we can test our ROMs on emulator?
Click to expand...
Click to collapse
Well you can try to build the samsung sources against the aosp source code. The AOSP source code comes with the android emulator pre-compiled so you can test out your roms.

FBis251 said:
Well you can try to build the samsung sources against the aosp source code. The AOSP source code comes with the android emulator pre-compiled so you can test out your roms.
Click to expand...
Click to collapse
can you please elaborate on this one?I'm not sure I followed

alon2 said:
can you please elaborate on this one?I'm not sure I followed
Click to expand...
Click to collapse
http://source.android.com/source/building.html

FBis251 said:
http://source.android.com/source/building.html
Click to expand...
Click to collapse
OK...I'll see what I can understand from that
10x