updated first post but no new kernel build yet.
if you build the codeaurora kernel you will need a patched haret to boot because the resulting Image is huge. here is a build from NetRipper with a fix that moves initrd location 5Mb further:
http://www.netripper.com/leo/haret-p...430_233234.exe

Linux Loader

---

What loader are you using for this distro?

Are drivers the issue?

Where do you need help?

Perhaps I can use my pathetic knowledge of linux to help come up with a Driod HD2 build.

Originally Posted by zarathustrax

Simranjits.... When have you ever seen quicker progress with putting android or linux on a non-android phone? They are not incompetent at all... they're making great progress for what they're doing. Seriously, tell me.... what other non-android device had android developed for it faster than this, including developing a new kernel for the chipset? Keep in mind that Android for the TP2 already had a kernel developed for it, which took as much time as it's taking them for the HD2s snapdragon. 2011 is not that far away... if they have it finished early 2011 then they are doing pretty good. If you can do better, THAN DO IT! Stop being negative!

Isn't the android kernel for the QSD8k already running on the Nexus One, the Desire, the Bravo, the Incredible, and soon the Supersonic?
I'm not trying to stir up the flame here, but, with variations of HSXPA banding, the chipsets for all those devices are all based on the HD2's, and the source for at least the Nexus' kernel is freely available.
It's common knowledge that the sense versions for the Desire were originally engineered using a tweaked HD2 and the devices are mostly the same except for minor details.
I fail to see, then, how it is that a whole new kernel has to be made when at least another one exists already.
This is all, ofcourse, if we're talking about the QSD8k. It might be that the problem is drivers for the additional components of the device which we won't have until the Supersonic (which looks like it might share more production parts with the HD2 than the N1-based devices do) is released.

Originally Posted by kristoff123

This is only somewhat related, but nonetheless should make people less hesitant about trying android if and when we have a working ROM.

I talked to TMobile (US), and, while you cannot use an Android device on a Smartphone plan (which is what the HD2 uses), you can switch back and forth, more or less at will, between Android and Smartphone data plans. Knowing this will certainly come in handy when actually trying to connect to the internet.

i believe its just different apn settings. i will check into this however.

RULE #2

---

2. Be polite and respect your fellow xda-dev user.

There is no need for cursing, flaming, racism or personal attacks. There are a lot of different nationalities on this forum all with different cultures, this means that no matter what you're like, you'll have to adjust to people that are most definitely not like you. For this reason we'd like to ask you to refrain from discussions about religion or politics, we do not wish to limit your right to free speech, but we have noticed these topics tend to get heated and might be best discussed in a different environment. It will gain you a lot of respect if you help to keep the peace. It's disrespectful and therefore not permitted to create Alias Member names in an attempt to deceive others.

Everyone, lets stay on topic and stop hijacking the OP's thread. To those select members who are constantly flaming and disrespecting other members you are on my watch list. Cool it or bans will be issued, you know who you are!

http://htc-linux.org/wiki/index.php?title=Contact

Originally Posted by dcordes

demain, c'est loin

Originally Posted by Zepiii

Après demain, c'est encore plus loin

English translation must be included per xda rules guys.


4. Use the English language.

We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.

Originally Posted by cedesmith

According to phone arena supersonic release date is about 13 June.
This info was retracted but is still on google's cache here .

This means that probably we will have at least a touchscreen driver.
It does not mean that we can use the supersonic kernel or that kernel will not freeze but here i am confident that devs will make it work.

yea let's hope we're lucky and it's the same ts.

btw if you are interested in experimenting with the leo kernel a bit I made small howto with htc vogue as example.

http://htc-linux.org/wiki/index.php?...rtGuide#Kernel

also it's worth reading hte mailing list where LeTama describes an approach of analyzing the user mode binary execution problem http://lists.linuxtogo.org/pipermail...ay/thread.html
(please do not post 'when is android done?' emails there)

I wonder if this matter, but the Leo uses a QSD8250 and the EVO uses a QSD8650. On close examination leads me to believe the difference is the GSM v CDMA dealio, as the Incredible also uses the 8650. The HTC devices that use a 8250 is the Passion (Nexus One) the Bravo (Desire), and of course the Leo (8250B for the US, with AWS support, I believe).

On the Android side, we had the Dream/Sapphire use the MSM7201A and the Magic/Hero use the MSM7200A, and that was enough to warrant an incompability with the kernels (though it was never explored exactly how different they were, but it was far more than the radio as the device wouldn't even boot with a mismatched kernel).

Also, a thought just crossed my mind, don't know if it leads somewhere.
When the Bravo's system was ported to the Passion, the boot had to use the Passion's kernel because the Bravo kernel wouldn't boot.
The Bravo is more akin to the Euro spec Leo based on bands, and the Passion is more akin to the US spec Leo (both use T-Mobile US' bands). How about trying the Bravo kernel for the Leo?

Also, I'm not sure whether the module for the Supersonic could be used, again, because it's based on a different kernel, so it might be incompatible that way unless there's some access to the source for it.

yea qsd8250 vs qsd8650 seems to have many differences. just like msm72xx(A) vs msm75xx(A) .

don't see a reason to not release the source code for touchscreen.