yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Android Development] foxmeister:
I'd imagine it would be a case of diff'ing the Hero kernel source against the "stock" 2.6.27 for Android 1.5, analysing the differences, and then applying them (where appropriate) to the 2.6.29 source for Android 1.6.

Regards,

Dave
[Hero, G2 Touch Android Development] CTVIrus:
Yes, the biggest question is how many did they change? Does anybody got some time to make some statistics about this? lines changed, added, removed?
[Hero, G2 Touch Android Development] us1111:
Can't we skip donut and go for Eclair, or is that a stupid thing to say :eek:
[Hero, G2 Touch Android Development] foxmeister:
Given Google haven't released the source code to Eclair yet, no.

Regards,

Dave
[Hero, G2 Touch Android Development] E2K:
Could you explain that?

It's booting into vanilla android? with everything working?
[Hero, G2 Touch Android Development] marazi:
quick question for the devs here, is it now possible to do a port of the CyanogenMod to the HERO...??
[Hero, G2 Touch Android Development] stripealipe:
I think we should all be looking forward to our own custom Hero ROM with the new kernels now being released.

Why port Cyanogen's ROM when it's been heavily optimised for a diffferent handset with less RAM, worse camera, and generally less resources?

Personally i look forward to a Modaco build ROM built around 1.5 initially, with some nice tweaks such as BFS, compcache etc

Then hopefully once the kernel has been properly looked at and compiled we can get a working 1.6 version of Android until HTC release their version with Sense built in.

And then we can have some nice custom versions built around that!

And once again, thanks Paul and indeed all the others now flocking around the Hero ROM scene, cooking, building, giving us their time. Should be an interesting few weeks ahead of us! :)
[Hero, G2 Touch Android Development] marazi:
true true, and i agree :)

yes, thanks to all the devs here for the great job they are doing :)
[Hero, G2 Touch Android Development] matt6gsr:
When you see what rom-cookers have done to the galaxy rom, im very excited to see what our cookers can do now they have everything they need.

Good luck
[Hero, G2 Touch Android Development] mopodo:
I successfully compiled some kernels, but none of them will but. All stops on the "hero" image.

Is there a way to get the boot output to the screen or a console via adb?

Without any logs it's not really funny to playing around ;)
[Hero, G2 Touch Android Development] Lox_Dev:
Don't forget to build wlan.ko from android sources. Or wifi won't work
[Hero, G2 Touch Android Development] MercuryStar:
Oh my my my my this is excellent news!

And here is the obligatory slashdot thread

http://mobile.slashdot.org/story/09/10/22/2315250/HTC-Finally-Releases-Hero-Source-Code

I can't wait to discover all the new things I'll be able to do to my Hero in coming months... :D
[Hero, G2 Touch Android Development] vd3:
First time trying to compile a linux kernel for android. Does anyone know what the config option USB_FUNCTION_PROJECTOR is? I am not able to build the kernel with it enabled ("No make targets" error).
[Hero, G2 Touch Android Development] E2K:
After the kernel source got released, it didn't go exactly like planned if I'm honest..

Everybody is running around, asking questions, and randomly trying to compile something, not sure if they want (or can even get) 1.5 or 1.6, what they need to do, etcetera.

I am sure if you combine your efforts, and start from scratch together, you can have a working hero android by tonight.

Can anyone confirm this?
[Hero, G2 Touch Android Development] Poischack:
Just a little question : how do you install a kernel on the phone without making a update.zip (I don't know how to sign file and I not really sure to want to know).
[Hero, G2 Touch Android Development] Poischack:
Answer to myself :

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[Hero, G2 Touch Android Development] packetlss:
Remember to use the --base=0x19200000 parameter when building images for the Hero or you might run into problems.
[Hero, G2 Touch Android Development] felikz:
very nice, now that we have the code we can really customize roms

äöü
[Hero, G2 Touch Android Development] dying4004:
do we have chance now of gettting nice themes like other android phones? cheers
[Hero, G2 Touch Android Development] erikwt:
What do you mean? As argument of mkbootimg?
[Hero, G2 Touch Android Development] packetlss:
Yes.

(10 chars)
[Hero, G2 Touch Android Development] erikwt:
What 'version' of mkbootimg do you use? Mine, from cupcake sourcetree, doesn't allow such argument.
[Hero, G2 Touch Android Development] paulobrien:
You need the donut version.

P
[Hero, G2 Touch Android Development] erikwt:
Yes, I see. Thanks.
[Hero, G2 Touch Android Development] E2K:
Who do I need to give a blowjob here to program me a working 1.6 vanilla android on my hero? :p
[Hero, G2 Touch Android Development] dying4004:
what have we got after releasing of kernel? before the release may were like will do everything just if htc releases the kernel. now kernel is released and where r we? not a single theme from magic is ported. not a single rom from magic is ported. whats the benifit of the kernel then?

we all were calling htc names and were complaining for not releasing the kernel. and now they have released it and we are chewing fingers. :D:D
[Hero, G2 Touch Android Development] foxmeister:
Correction! *You* are chewing fingers! How do you know what other people are doing?

Regards,

Dave
[Hero, G2 Touch Android Development] oblika:
Haven't you see the Modaco Custrom Kernel? (http://xdaforums.com/showthread.php?t=575197)

:D
[Hero, G2 Touch Android Development] frandavid100:
So, how does that apply to getting a working ION / Magic ROM? Can that kernel be used with one of the existing ROMs so everything will work with them?
[Hero, G2 Touch Android Development] OttarA:
Getting a working ION ROM has been done already. The problem is getting a donut ION ROM working, and to do that the kernel has to be updated to 2.6.29. To do that the changes from 2.6.27 to 2.6.29 has to be identified.

And please stop nagging all the people doing this for us for free...
[Hero, G2 Touch Android Development] E2K:
that is not true at all; most of the things were not working (at all).

they never finished it.
[Hero, G2 Touch Android Development] frandavid100:
Hi,

Well, I meant a ROM where all the hardware (GPS, camera, accelerometer, trackball...) works. That does not exist yet.

That was not nagging or complaining, I'm sorry if it sounded like that. It was a real question out of genuine curiosity, since I don't know how that link gets us any closer to a working rom. I don't know how the whole thing works, and would like to.
[Hero, G2 Touch Android Development] OttarA:
Sorry about beeing so harsh, there has just been so many complains about developer working slow and that the kernel release has had no change. Again sorry about beeing harsh
[Hero, G2 Touch Android Development] frandavid100:
Never mind :-)
[Hero, G2 Touch Android Development] behnaam:
I freshly compiled a wlan.ko with the hero kernel source and I replaced the one in my MotoBlur ROM but wifi still doesn't work? Any dev or kernel guru that can help?
[Hero, G2 Touch Android Development] Lox_Dev:
I understand why devs are leaving XDA....
[Hero, G2 Touch Android Development] E2K:
I would not exactly call them "devs".

They are leaving because they cannot compile a working android kernel, plus of shame because they were talking like when they received the kernel source, they would become gods or something. I believe only noobs are leaving ;)
[Hero, G2 Touch Android Development] OttarA:
Are you saying they're leaving because of me? I was just trying to make all the complaining stop :confused:
[Hero, G2 Touch Android Development] foxmeister:
No, it is attitudes like this one that is the problem.

You clearly have no concept of what is actually required and how it need to be done. If there is any "shame" here, it is on you!

Regards,

Dave
[Hero, G2 Touch Android Development] J-Zeus:
Lets calm this down everyone. :confused:

There is, I understand it, no onus on developers to do any work, let alone at speed.

I for one value their work and am appreciative of the time / difficulties involved.

Let's just sit tight, and I'm sure they'll come up with good stuff:D

And if you really can't wait, you can always learn how to do it yourself, and share the results:)
[Hero, G2 Touch Android Development] dying4004:
u r going at good pace mate. :D. hope to see motoblur with wifi very soon. cheers
[Hero, G2 Touch Android Development] Fluesopp:
Is the HTC Keyboard a part of the kernel or is that a separate app?
[Hero, G2 Touch Android Development] mopodo:
No apps are part of the kernel, only drivers etc. are in the kernel

All apk things are seperated
[Hero, G2 Touch Android Development] maejrep:
Has anyone else noticed that the kernel source that they've released appears to be incomplete, at least as far as heroc goes? There are several options that appear in /proc/config.gz on the device, that are not available in the kernel's Kconfig. Most notably, of course, CONFIG_MACH_HEROC, which is the Sprint Hero (and DESIREC/Eris, NEONC, and HEROCT), and a CONFIG_PROXIMITYSENSOR which doesn't appear in the code anywhere, but exists in config.gz as a disabled option ("# CONFIG_PROXIMITYSENSOR is not set").

This is the diff that results when using config.gz as .config, and running "make oldconfig":

http://htc.privatepaste.com/2ce8220756

That explains why my stock-source-compiled-from-HTC's-config.gz kernel fails to boot :)

But that's kind of an important piece of information for us HEROC users to know... Shouldn't HTC be obligated to release the additional missing source code? Especially now that the Eris and Sprint Hero are on the market.

For those who are complaining about lack of advancement even with the kernel source, this would be one of potentially many major roadblocks that a HEROC developer will run into. And in that case, it's not their fault -- it's HTC's.

EDIT: Apparently I'm just blind, or dyslexic... I read "board-hero.c" as "board-heroc.c" :( The "HTC Hero Kernel Source Code" name clearly does not include heroc. I'll go to sleep now.
[Hero, G2 Touch Android Development] foxmeister:
Given how long it took HTC to release the kernel source code, I'm not at all surprised that it doesn't cover the CDMA versions. I guess you'll need to get onto them about it!

Regards,

Dave
[Hero, G2 Touch Android Development] packetlss:
I've never managed to get a heroc kernel booting from the released code either.

However I think I saw someone in the Hero CDMA forum that had compiled a CIFS module for CDMA Hero, might want to have a look on how he did it.

Someone with a CDMA Hero should open a ticket with support for them to release the source. Reminding them on twitter also suggested :)
[Hero, G2 Touch Android Development] maejrep:
It's not a problem to build modules and load them into the kernel, because the rest of the kernel is already built and has support for the phone. The problem is that there are no board-heroc*.c source files in the release archive, thus building a kernel for the heroc board won't work. Even if you just ungzip config.gz to .config and compile, or add the HEROC config option to Kconfig, it's going to fail once it starts building arch/arm/mach-msm/ because the Makefile says that if CONFIG_MACH_HEROC is enabled, it should build "board-heroc.o". In order to build that object, it must have a board-heroc.c file to compile. And without that file, you get "No rule to make target board-heroc.o"

I would imagine that much of the source is very similar to board-hero.c (for the GSM hero), but I haven't tried copying those files to board-heroc*, to see if that works. I'll try it and report back.

The nice thing is that the built kernel (shipped on the phone) gives us clues about naming files, functions, etc. :p

EDIT: No dice.. I figured as much. It's a different radio, I'm not surprised that it would need modified configurations. But surprisingly, it seems the CDMA Hero is much closer to the GSM Hero than other GSM/CDMA phones of HTC's past (e.g., RAPH/DIAM).
[Hero, G2 Touch Android Development] packetlss:
Ah ok, that explains it. Trying to reverse engineer the parameters for it should be doable, and most of the offsets and stuff should be obtainable on a rooted CDMA hero, most probably through /proc or sysctl interface, hell even dmesg might reveal some. I know someone did this for 32A sapphires before HTC released the source for that. The source released supports many different modem versions and also CDMA chipsets are selectable so it might just be that the board config is missing.
[Hero, G2 Touch Android Development] diesel556:
I just tweeted the following to htc:

@htc Is there an ETA for a kernel source release to add missing pieces required for the CDMA Hero? For specifics see http://bit.ly/6PBtS0
[Hero, G2 Touch Android Development] Samek:
Hello!

Has anyone tried porting htc's kernel_hero 2.6.27 to 2.6.29? If so, what problems did you face? What was your way of doing it?

I'm under opinion that it can be done, but it's not one day job.

I'm thinking the best way would be to first diff android-msm-2.6.27 and kernel_hero, and then apply necessary changes for Hero to android-msm-2.6.27. The second step is to diff patched android-msm-2.6.27 and android-msm-2.6.29 and apply necessary changes..

EDIT: So far I managed to do the first step, but I think I included some other unnecessary changes, so it's not complete yet.
[Hero, G2 Touch Android Development] foxmeister:
It's a lot of work. I tried it before but the kernel I built didn't work at all, and I had no time to look into why. At that point, we got a working 2.6.29 kernel (object only of course) via the leak of HTC's 2.1 build, so it seemed like a pointless exercise to me continuing further.

Once HTC ships 2.1 for Hero, they will be obliged to release their kernel source for 2.6.29.

Regards,

Dave
[Hero, G2 Touch Android Development] pulser_g2:
Yeah, I was actually thinking about this myself just earlier today. Once we do get a 2.1 build, we'll all need to start harassing HTC again to get sources.

Is there any chance they'll be organised this time and get the sources released at the same time (or before :)) the release of the ROM (binary)? I doubt it TBH
[Hero, G2 Touch Android Development] Samek:
Yeah, that's all true but we don't even know when HTC will be releasing their update and I'm starting to think it won't be anytime soon. So waiting here is really not the best option.

You didn't answer any of my questions. I already know the facts, it would be great if HTC would release kernel source for 2.6.29, but let's face it, it's not gonna happen anytime soon.

So, please give me some useful answers or don't reply at all.

Am I the only one interested in doing this? Am I the only one seeing great benefits in doing this?
[Hero, G2 Touch Android Development] foxmeister:
Errhhh - yes I did.

You asked:

To which I replied:

Nice attitude! 4 posts and you're already the "thread police"! ;)

Did you actually bother reading any of the threads where this has been discussed *at length*?

Regards,

Dave
[Hero, G2 Touch Android Development] kendong2:
no, you are the only one that hasn't gotten to the fact that it is a buttload of work, would probably take several weeks and it is not assured that it would yield a usable result. and by now we have probably the new rom from htc before you managed to compile a working kernel, especially if you keep complaining instead of working.
[Hero, G2 Touch Android Development] Samek:
Ok, I'll rephrase myself: Is anyone out there who hasn't gave up on porting HTC's 2.6.27 to 2.6.29?

Sorry if my last post sounded offensive, it wasn't meant that way. I was a little pissed at replys, I expected different replys :)
[Hero, G2 Touch Android Development] kendong2:
no problem. afaik there is no ongoing work on this, but from your question i take it that you haven't read this: http://xdaforums.com/showthread.php?t=566415, from this thread lox_dev started this project: http://lox.knc.nc/Android/KernelPatches/, but he also wrote this:

i think that was our best shot, feel free to give your best, but with the upcoming eclair update (and therefore the .29 kernel sources) i don't see it happen... it is that simple, with everybody expecting eclair in the next few days nobody wants to take the effort to port the sources.
[Hero, G2 Touch Android Development] Samek:
I forgot all about this lox's thread, so thank you for reminding me.
[Hero, G2 Touch Android Development] sanpei:
i think in your way, the two patches will have many conflicts (not meaning the conflicts auto patch tools reporting) even if you modified sources manually.

make your work based on msm-kernel-2.6.29, don't copy and paste much things into it (except the sensor drivers, since those drivers do not make many conflicts with existing codes, it can be added easily with some minor changes), just make some changes you think necessary (finally,you will find that's enough to run an AOSP ROM and most functions in a SenseUI ROM).

you MUST understanding every steps on booting. they are common knowledges which you can search and get them on the internet, and are just "simple and stupid" codes as linux guys will say themselves.

then, you can look into board-sapphire.c as it's a template. compare the three groups: board-sapphire*.c from msm-kernel 2.6.29, board-sapphire*.c from htc-hero 2.6.27, board-hero*.c from htc-hero 2.6.7.

(though your phone is not sapp, but you can get some understanding here. and if you really look into it but not just make some automatic diff things, you would found that there are not many changes are necessary for running ASOP ROMs, though the codes look like have some large different).

understanding what are the differents and what are affected by these differents. with these understanding, you can make a diff between htc-hero-2.6.27 and msm-2.6.29 now (you don't need care about the msm-2.6.27 too much). with the results, take a look at the memory address parts and radio parts carefully, you can ignore almost all others.

then you can find all things to make your phone boot and execute init, after init process executes adb daemon, everything will become exercisable though there are some other difficult there if you want your kernel working properly.

in ONE word: understanding than just patching. good luck!

update:

yes one can say everything are just about the time. but it is determined by what he have learned in the time past and not the time which he have or not have willing to kill if one can do a thing (or do a thing in a short time) or not. you can't say why cyanogen can do such things just because he have more time and will have more time than someone.

if you have enough confidence to understand how all things work, don't be scared by some blank incomprehensive speech; you won't take too much time to do this job. and if you are interested with these, you must go for it even you have not known too much now. :)
[Hero, G2 Touch Android Development] simplyblue:
Hi guys, I have a question to ask.

Is it possible to enable USB On The Go function on HTC Hero?

From the configuration file of the kernel, there are some options related to USB such as:

CONFIG_USB_SUPPORT=y

CONFIG_USB_ARCH_HAS_HCD=y

# CONFIG_USB_ARCH_HAS_OHCI is not set

# CONFIG_USB_ARCH_HAS_EHCI is not set

# CONFIG_USB is not set

# CONFIG_USB_OTG_WHITELIST is not set

# CONFIG_USB_OTG_BLACKLIST_HUB is not set

I tried setting CONFIG_USB_OTG_WHITELIST=y, but that alone didn't seem to work.

May I ask for some advice?
[Hero, G2 Touch Android Development] mopodo:
doesnt look like its support at the moment

http://code.google.com/p/android/issues/detail?id=738
[Hero, G2 Touch Android Development] maejrep:
Good summary of what would be required. I did manage to get android-msm-2.6.29 to compile with board-heroc (which I copied from board-hero, and fixed so that it boots in 2.6.27 on the CDMA hero), and other platform-specific changes from the released 2.6.27 GSM hero code. It doesn't boot on HEROC, but might boot on the GSM (I don't have one). Of course my copy is meant for the CDMA hero, so it wouldn't boot as-is, but can point out the changes that were necessary to get the HTC-specific files to compile cleanly in a 2.6.29 code base.

I've also managed to backport some of the stuff from the 2.6.29-nexusone branch, back into my 2.6.27 code -- specifically msm_camera, msm_v4l2, and the s5k3e2fx video driver (replaces the i2c s5k3e2fx chip driver and the board-hero*-camsensor driver). It works up until displaying the video stream to the canvas, which I believe is caused by the fact that we have to use a proprietary libcamera/liboemcamera. Though it may work for GSM, using the libraries from the leaked rom.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] bonevbs:
Is there a stock 6.5.1 ROM without all the htc customizations like the phone app or manila ?

I would really like to see a ROM with the new contacts app Titanium interface and so on.. I think thats what is missing here at Rhodium forum: a clean, fast stock(microsoft-stock !) ROM...

Too bad I can't cook. :(
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] ai6908:
Start cooking...or pay someone cook to make your own!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] rvashi:
I'd like to see a stock type of ROM too for 6.5.1!!

However, even though some of us can cook ROMs, not everyone has the indepth know how or the time to invest. That's why people make donations to the ones that do cook the ROMs.

I'd suggest that if you can contribute anything nice, don't worry about replying to the thread.
[Touch HD General] stadros83:
Hello, I've got some questions for blackstone's owners :

- Are you "happy" with this phone ?

- Is it missing something for you ?

- What the best for you ? A Blackstone or a HERO (android) ?

- Do you know if HTC will release an official Windows Mobile 6.5 for it ??

I'm thinking of changing my Nike, and the HD looks great.
[Touch HD General] JanSchotsmans:
Wait for the HD2

If there is one thing lacking in the original HD, its that the CPU just isn't fully suited to drive a large display like the HD has.

In the HD 2, the Snapdragon is used, which isn't only much faster frequency wise, its also a new generation of ARM which has more pipes and instructions.

Clock per clock the new ARM CPU's can be seen as anywhere between 2 and 4 times faster.

At a clockrate considerably higher then the HD's 500+ (snapdragon is 1Ghz), the performance difference will be immense.

Calculate into that that Windows Phone (6.5) is considerably faster on the HD then 6.1 and you'll have the HD2 being an absolute monster.

I'm very happy with my HD, I have full freedom to do with it what I want, I can use all the apps that I need and want and I still prefer a Windows Mobile phone over anything else, because it has so much history and apps that have been around for a long time.

I love the Hero, simply drool over the design, but its said to be slow, even with Android.

So if you want Android, wait for the Touch HD2's mirror set that runs android.

The HD is a year old device, so buying it now, might give you a nice price, but there is a new generation of hardware coming out now which is leaps and bounds ahead of everything even half a year ago.

The HD's hardware's basis is still the same as a TYTN2, the CPU is a bit faster but the display is much higher resolution.
[Touch HD General] stadros83:
Yeah I know about the HD2 ... but I don't want to buy a new one ;).

I'm looking for an used one, so cheaper ...

The HD2 will be to expessive for me !!
[Touch HD General] Fallen Spartan:
All these questions have been asked many times before. I see no need to ask again. We have threads on android, hd vs hd2, will hd get wm6.5, are you happy with hd etc etc etc

Please use the search function