yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] MrPadie:
Thanks for your input marc1076.

I am aware that it's not 3.0 yet, however, he has backported quite a few things for now, mainly concerning hardware acceleration (as written in the OP).

Would it not be a good step to then try this kernel on our current ICS builds in the hopes of any improvement? Or perhaps alternatively incorporate the backports (possibly more difficult) into our current ICS kernel(s) in an attempt to edge closer to true Hardware Acceleration?

A few thoughts, may be possible, or not - feel free to correct me. Thanks again for the advice.

MrP.
[HD2 Android NAND Development] warrenb213:
Once I see some true ics kernels with specific commits for ics you will see them appear in our kernels.
[HD2 Android NAND Development] MrPadie:
Thanks for your reply warrenb213.

However, I'm kinda lost as to what you are saying - are you saying that our current kernel (namely Tytung's kernel) for ICS is not a proper ICS kernel (which it isn't really, it's adapted from GB kernel from what I can tell), and until we have a kernel dedicated to ICS, there won't be any of the above mentioned additions?

If that's the case, what is your reasoning for saying that if I may ask? And also, where can these 'true' ICS kernels be sourced from? (As far as I know, the only 'true' ICS kernels around are based on 3.0, which in essence, defeats the object of us porting these additions back in the first place).

MrP.
[HD2 Android NAND Development] Rick_1995:
First of all, tytung's kernel which is based on hastarin's sd kernel is a base of .32 kernel from froyo source of the eVO 4g. It was not supposed to be used in gb but since it works, no worries.

Even though AOSP is opensource, the driver code for the devices is not, which makes porting difficult and moreso when the device actually never had any drivers for that specific os (read Android on HD2).

There is already an initiative (thread to be precise) in the qualcomm developer forums pleading them to opensource the qsd8250 drivers so that devs who are not so rich can backport ics to n1, desire (or HD2 for that matter) since it is clear that HTC certainly won't and google too has given up n1.

What tytung did to make his kernel work with ics is add upon the old base, it works but is dirty and should lead to unexpected issues.

The true ics kernels are based on the 3.0.1-tag of linus's repo.

You can sync into linus's 3.0.1 and compare it to the kernel source code of Galaxy Nexus, see the android changes, port them to the vanilla kernel, copy htcleo board files while rebasing them on 3.0.1 and adding the radio code from current kernels. It is far easy to say this than to actually do this when looking at the staggering size of the linux codebase.
[HD2 Android NAND Development] Dr_Grip:
The question is how many of the HD2-specific changes were broken by

a) changes in the upstream Linux codebase in between 2.6.32 and 2.6.40 (aka 3.0)?

b) android-specific changes between Froyo, GB and ICS

EDIT: There seems to be a working (except for USB mass storage) 2.6.35 kernel here. This at least reduces the number of upstream code changes to deal with.
[HD2 Android NAND Development] fhasovic:
USB mass storage works, confirmed it once again. USB Tethering doesn't work. Still working on it.
[HD2 Android NAND Development] uzi2:
And a fully working one here
[HD2 Android NAND Development] jan-willem3:
Because it was an htc kernel just like the prevous evo 4g kernel so porting it was more easy. If you look at the 2.6.35 cm kernel it is highly unstable and the MSM kernel is also an AOSP kernel like the cm kernel.
[HD2 Android NAND Development] Dr_Grip:
That does not make sense, I think. If the Desire devs get a working kernel for the Desire, the changes needed to make it working on the HD2 should be the same no matter if they are starting from a HTC or an AOSP codebase.

That it will be more complicated to get a working 3.0 Desire kernel without HTC's codebase is a challenge the Desire devs will have to face unrelated of the porting effort to the HD2.
[HD2 Android NAND Development] fhasovic:
Can you confirm that everything works?

My kernel is forked from ACA 2.6.35 non-sense and developed further...
[HD2 Android NAND Development] uzi2:
There are voice recorder issues in the current version, but these are fixed in the latest release 0103

Swyped from my aHD2oid
[HD2 Android NAND Development] mexicandroid:
SPEAKING FOR THE NOOBS

I LOVE MY PHONE TO ME IT'S SUPER FAST,

BUT WHAT YOU GUYS ARE SAYING IS THAT IF WE HAD A NATIVE ANDROID WITH THE SAME SPECS AS OUR HD2 IT WOULD BE EVEN FASTER AND BETTER?

THIS IS MY FIRST SMART PHONE SO I'M JUST CURIOUS ABOUT THAT.
[HD2 Android NAND Development] Dr_Grip:
turn your caps lock off.

Short answer: You can expect the same performance from the HD2 as from the Nexus One and Desire, given it runs the same software.

Slightly longer answer: This is a development thread. What we are talking about is getting the linux kernel (think: core of the system) version used by ICS running on our phone.

Getting this to work -as opposed to trying to get a Froyo/GB kernel working with ICS- would benefit both performance and stability.

There are some issues with that. Most of them are related to the fact that Google and HTC have dropped official support for the Nexus One and Desire. The only issue related to the HD2 not being an native Android phone is the need for a special radio driver.

EDIT: If you tried to be funny: You failed.
[HD2 Android NAND Development] warrenb213:
Uzi is correct. Ill be doing a fs thing soon, a Bluetooth thing soon, and more cam related stuff. But overall 99% is fully working.
[HD2 Android NAND Development] MrPadie:
Lets not dwindle off topic here guys.

Nevertheless, I stand with Dr. Grip on this one. Surely if a kernel is working over on the desire, regardless of its origin, the steps to port it over to HD2 do not deviate from the currently ported desire kernels? (Especially seeing as it is still based on 2.6.35).

I may be wrong, but it seems to make sense that way. Now, not to stir from anyone's preference, but in my own opinion, a pure 3.0 kernel for the HD2 is not a necessity right now. As it stands, I rate we try to get HWA working with what we have (2.6.35). 3.0 can be considered a long-term project, just as attempts were made to get sense working on our first kernels before 2.6.35 was worked on.

Yes, it might cause issues, but its an intermediary step, an experiment. I would do the port if I had the knowledge, but I'm not at the level yet.

So, are there any devs willing to try build the kernel from source (linked in OP) for our HD2's, and see where it goes?

Thanks,

MrP.
[HD2 Android NAND Development] DannyBiker:
Yeah but the problem is that this is thinking from a user perspective and not from a dev perspective. I'm sure there are limitations or variables that are therefore not considered here.

And that's why, the thread should be moved from the subforum as well...:)
[HD2 Android NAND Development] MrPadie:
I know its from a user perspective, which is why I have iterated the whole time that I may be wrong and my thoughts are from logic, not experience. I'm trying to bridge the gap at the moment between user/dev perspectives.

I disagree that this should be moved. Its not a Q&A, its not general, its a development initiative, but it lies with the mods at the end of the day.

What I am asking is: Can any of the devs port the kernel from source? If yes, go ahead! If not, why (in terms of THIS specific kernel)?
[HD2 Android NAND Development] Chaosz-X:
I can try to compile it for you guys with HD2's, if you can provide me a source code of another kernel working on the HD2. I don't have a HD2 myself though, so I can go on the donation-way, or you guys have to test every build ;p
[HD2 Android NAND Development] Dr_Grip:
The thread I linked on the last page includes this link to the source. I am willing to alpha test anything you get compiled.

Thanks for your effort!
[HD2 Android NAND Development] MrPadie:
I'm more than willing to give some builds a test. Please let us know in this thread when and if you make any progress.

Thanks for your efforts!

MrP.
[HD2 Android NAND Development] Dr_Grip:
If I am not mistaken we'll have to cook our own ICS ROM to test this kernel once it boots, as the ROMs available all include hacks to work with tytung's modified Froyo kernel.
[HD2 Android NAND Development] tytung:
You are wrong.

There's not any hack to make current ICS ROMs to work with my ICS kernel.

My ICS kernel is based on Froyo kernel (2.6.32), but I have backported some drivers from GB (2.6.35) and ICS (3.0) kernel.

Thus I called it an ICS kernel.

Please read what Jean-Baptiste M., a Software Engineer, Android Open-Source Project, Google., said below.

https://groups.google.com/group/android-building/msg/2fbd35946b9a36e2

It means if we backport proper drivers to kernel 2.6.29, we can use it to boot ICS ROM and support all the necessary features.

Just like kernel 2.6.29 is used by ICS version of Android Emulator in the SDK.

So no problem with 2.6.32.
[HD2 Android NAND Development] warrenb213:
Exactorama.
[HD2 Android NAND Development] Dr_Grip:
I stand corrected. Thanks for clearing that up.
[HD2 Android NAND Development] carl1961:
partly unpacked zImage

I might be looking for a needle in a hay stack, or spinning my wheels

this is best I could unpack Kernel 3 , seems not like the standard layout, maybe someone knows what to do , my goal was to compare with current HD2 kernels and see whats needed or missing

\kernel\sense4kernel\	-------	1	14	46,102,217	46,102,217

cpio-t

decompression_code

initramfs.cpio

initramfs.cpio.gz

initramfs.cpio+part3

kernel.img

padding_piggy

padding3

part3

piggy

piggy.gz

piggy.gz+piggy_trailer

piggy_trailer

sizes

E:\1RUU Endeavor 0.96.401.2\kernel\sense4kernel\1 ics sense4.0 kernelzImage\	-------	2	2	3,999,278	3,999,278

initramfs.cpio

zImageoriginaloffsetremoved.gz

sense4kernel 29MB
[HD2 Android NAND Development] Hammerfest:
this is true... but i cant help but want to see a 3.x kernel as base for going forward instead of the huge backlog of back-porting you and other dev's undertake...

It reminds me of the mods I used to do to my truck to stave off buying a new one... the last few I did where futile and finally made me realize what a hole I was digging myself into by "back-porting" all sorts of new performance parts and mods (yes, even for vehicles :D )
[HD2 Android NAND Development] carl1961:
switch from initrd to initramfs for newer kernels

For what I have learned they seem to switch from initrd to initramfs for newer kernels

this link may shine some light, and seeing I'm only a few day's old at learning kernels lol, this is probably old news to some advanced kernel developers and also I might be posting usless stuff, that I will delete when I find out...

http://wiki.debian.org/InitrdReplacementOptions

BootUtils BootUtils is designed for initramfs

README fo BootUtils

Introduction:

This set of utilities is designed for booting the new age of initramfs

enabled 2.6 kernel distributions... mouth full!

1. What is this initramfs all about?

initramfs is a gzipped cpio archive which is extracted into a dynamically

allocated ramdisk apon bootup. This archive contains programs and utilities

to bring up raid, evms, lvm ..etc devices, to find your root device, mount

it and startup your operating system.

2. Why the hell do I care?

You would care if you are a individual wanting to add encrypted root

support.

You would care if you're a distribution maintainer responsible for the boot

procedure of your particular distribution.

If you still don't know what is going on, you don't need these utilities.

3. What about run-init or even Redhat's nash?

run-init lacks various features, most notably pre-programed possibilities

for what init program to run ... and a number of other things.

nash seems to lack the ability to boot anything other than ext2 and xfs

root devices.

4. So what is soo great about these utilities?

Wide range of filesystem support, realistic distribution idependant

approach, ease of use.
[HD2 Android NAND Development] Germypan:
Hi boys, i have a question.... i saw that almost all ics devices use the kernel 3 with ics and jb, and i read that this kernel have a lot of fix for same issues for our leo. now, is there a solution to port kernel 3 to leo?

Germy
[HD2 Android NAND Development] ph03n!x:
This has been asked and answered in various places by kernel Devs - we are not able to get anything higher than 2.6.35 to boot, even 2.6.38 does not boot in our devices. Unless someone has the time, skill and patience to figure out how to get the newer kernels to boot, we are going to be using 2.6.32/ 35. On the other hand, almost all the required functionality has been backported to the current kernels - unless there comes a bump where a higher kernel is a must for further development, it may seem to be a futile attempt at getting the newer kernels to work.
[HD2 Android NAND Development] Rick_1995:
We are getting stuck when MMU is switched on, so that means something could be wrong with our iomap, page table setup and many other things, linux is not small and that makes the problem worse since the only way we (marc and me) can trace code execution is to use the switch on flash light or ram console (not even that sometimes if register pressure in a function is too high and stack is not setup till then). Cotulla did mention of helping us once he was done with his current projects, let's look forward to what mistake he finds :)
[HD2 Android NAND Development] jully3881:
your mean is that when cotula release the new mag , then he will devlopement our 3.0kenel?
[HD2 Android NAND Development] NRGZ28:
No..that's not what he said. Read the post again..lol
[HD2 Android NAND Development] Anon_1989:
Can someone provide a log of this error?

I think I know someone who can solve this issue

I'm referring to this mmu init error?
[HD2 Android NAND Development] marc1706:
That the problem. After MMU init and until the kernel init procedure there is no way we can debug the kernel via flashlight or kmsg (the log you were requesting).
[HD2 Android NAND Development] Anon_1989:
Soooo if you cannot see the error, how do you know for definite that its the mmu?
[HD2 Android NAND Development] marc1706:
We never said it's the MMU but rather that it's happening somewhere after the MMU init as we never reach the kernel init.
[HD2 Android NAND Development] Rick_1995:
I tried a flat mapped PTE for ramconsole, didn't work, only the necessary ranges are mapped till then like the kernel binary. I'll give it another go sometime later this week, got measles :(
[HD2 Android NAND Development] Anon_1989:
Nonamer is working on kernel 3 and shaky helping out, on HTC desire, isn't it better waiting for a 3.0?
[HD2 Android NAND Development] Rick_1995:
I don't trust shaky, but that's my personal opinion. Nonamer did pm me regarding the kernel on desire, will look into it when i get time, It shouldn't help this at all since the problems being faced on desire are completely different.
[HD2 Android NAND Development] xjjk:
Dude I don't know you but I appreciate your work keeping these old beasts up to date and I hope you get rid of your new "guests" soon. Measles don't sound like fun.
[HD2 Android NAND Development] Hammerfest:
they arent....

That being said, I dont plan on getting rid of my HD2 until SOMEONE gets a v3.x kernel with HWA and JB on this old monster...

Tall order I know :P
[HD2 Android NAND Development] Germypan:
But, if kernel 3 will works on bravo, this could be adapted to our device? or is this an idle information? My brother have a bravo and he told me that kernel 3 was almost ready

Sorry for my bad english
[HD2 Android NAND Development] Germypan:
Hi boys, do you know this 3D? http://xdaforums.com/showthread.php?t=1770095
[HD2 Android NAND Development] Germypan:
Hi my friends, i read this news http://www.xda-developers.com/android/the-new-development-cycle-starts/ and i have a question, if Rhodium has the 3.3/3.4 kernel, why our leo haven't this? :D :D :D I hope I have whetted the mind of genes

Germy
[HD2 Android NAND Development] nickholtus:
Hi,

Does one of the devs know kexec?

That will do the trick to boot the 3.0 kernel:)

Xperia 2011 bootloader only works with 2.6.32.x but with kexec kernel 3.0.8 and 3.4 boots:)
[HD2 Android NAND Development] -leo-:
In computing, kexec (kernel execution) is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware or BIOS) and directly loads the new kernel into memory, where it starts executing immediately. This avoids the long times associated with a full reboot, and can help systems to meet high-availability requirements by minimizing downtime.

Obviously, since this feature touches so many sensitive parts of the operating system, a great deal of care is needed to make it all work properly. The biggest challenge for kexec is that, in Linux, the new kernel that is to be rebooted to needs to sit in the same place in memory as the currently executing one. Replacing the existing kernel in memory with the new one, while still running in the context of the existing kernel, is a tough task. Another big issue is the state of the devices in the system. Firmware always initializes (or resets) the devices to a known "sane" state. The fact that kexec bypasses the firmware stage means that the state of the devices is unreliable.

Subsequent sections of this article will show you how to overcome these challenges, and how the direct booting to a new kernel is achieved. Note that kexec is currently available only on the x86 32-bit platform. Although work is underway to port kexec to other platforms, there is no working version of the code yet. Hence, all technical details in the subsequent sections are specific to the x86 platform.

from wikipedia and ibm :p
[HD2 Android NAND Development] nickholtus:
Kexec is already working on arm devices

So that problem is gone.

Some motorola devices use it, and now also the xperia devices without that "bugs"
[HD2 Android NAND Development] djsolidsnake86:
this will never gonna happening
[HD2 Android NAND Development] pirlano:
Yes yes, like, WP7, WP8, Froyo, Gingerbread, ICS, JB...

How do you know that?
[HD2 Android NAND Development] GODISMYCOPILOT:
just like the audio on sense 4 will never happen either ? lol
[HD2 Android NAND Development] nickholtus:
that's very good possible, they have got sense 4 almost fully working on the htc desire (sense 4.1)
[General Questions and Answers] Yomaster91:
Hey guys, so I just recently updated my Cappy from 2.3.4 to 2.3.5 KK4 using a couple of the forums found here on XDA. Question, though:

I attempted to apply the Fugu Root Mod before flashing to 2.3.5. When flashed, it showed the red Fugu fish, and then bootlooped on me until I pulled the battery. After that, I flashed the 2.3.5 update. Apparently, Fugu has failed on part of my own error, because I don't have SU, BusyBox, or any of the Fugu mods, and the kernel in the phones "About" section shows "2.6.35.7-I897UCKK4-CL614489."

The question: I don't really care to give rooting another go, and I've discovered the "fugumod" folder in my SD's directory. Of course, the file tells me not to delete it, but is it safe to do so being that the root was not applied?

Thanks in advance!
[myTouch 3G Slide Q&A, Help & Troubleshooting] cmons:
I searched the threads and found a similar issue but not exact..

Dropped a factory MTSlide into a doggie water dish and immediately retrieved it - it will now turn on but everytime it loads the same screen

ESPRESSO PVT SHIP S-ON

HBOOT-1.02.0000

MICROP-0620

TOUCH PANEL-SYNT0102

RADIO-7.15.35.16

NOV 26, 2010 etc....

HBOOT

and then it gives a menu but the volume rocker will not move down to anything other than FASTBOOT (maybe my volume rocker is jacked up from the water?)

When I select FASTBOOT it goes through a series of checks in which none of the images are found/valid..

Should I waste time trying to get this fixed at a repair shop? They want $50 just to look and it's $130 deductible, which IMO isn't even worth paying for the phone if it were working. I'm willing to root it or whatever needs to be done to get it up and running again.. I even read online to put it in the oven to dry it out? I'm open to any suggestions.

Thanks so much in advance.
[HTC EVO 3D] bmoreboy02:
I wanna get these headphones but there getting alot of mixed reviews from different phones. People with apple products say they pair well. People with droids say they don't

http://www.bestbuy.com/site/Motorol...uId=1326039&st=bluetooth headphones&cp=1&lp=7

Right now i have these and there awesome. Just wouldnt mind losing the wires

http://www.bestbuy.com/site/Yurbuds...ones/1997127.p?id=1218343141443&skuId=1997127
[HTC EVO 3D] gbopanonymous:
i had the S10's.. paired pretty good.. they are not very comfortable tho and you can find them cheaper online elsewhere, around $45.
[HTC EVO 3D] SerialKilla:
I had the original S-9's, and they paired well - sounded good too. Watch the knock-offs tho, they are NOT the same,and they won't pair well,or sound good either!
[HTC EVO 3D] KB112:
For sure, tons of knock offs on eBay. I got the S-9's but don't use them as much as I used too. They pair well and can be a decent distance from the phone and still pick up signal. If you have a large melon, they may be a bit tight and uncomfy though.
[HTC EVO 3D] bmoreboy02:
Lol unfortunately i have a large melon. Yea ive seen soke on ebay for $40 and they look exzactly the same as best buy ones.
[HTC EVO 3D] KB112:
The difference between the knockoffs and the legit ones is the buttons. My S9 has super sensitive buttons, you can just lightly press it and it will stop, skip tracks etc. The knockoffs you have to physically press the buttons firmly. It worked but felt very uncomfortable mashing a button while something is in your ear. My coworker swooped up the knock offs for like $25 on ebay. Also mine came with a Blue Tooth adapter for an ipod, works excellent.
[HTC EVO 3D] meme405:
Is there a specific reason you want in ear headphones?

Id say pick up a set of over the ear bluetooth headsets. I had a set of motorola s805's they were good. also had a set of jaybird sb2's which were sick.

Im now rocking a set of the new Beats by dre bluetooth headphones.

If you are stuck on in ear headsets check out jaybird they have an entire bluetooth product line with great support and service.

But i really think you should try over the ear (Your hearing will thank me later)
[HTC EVO 3D] bmoreboy02:
I wear them while jogging. Thats why i like the in ear design.
[HTC EVO 3D] KB112:
Exactly, for sports activities they work the best. Cans would just slide around and flop off.
[HTC EVO 3D] meme405:
Then i would definetly recommend Jaybird headphones as they are specifically engineered towards athletes and runners. They have a brand new set of freedom headphones which although I have yet to try look very well built and thought out.

Edit: Besides they have a sweat warranty thats pretty brilliant. Good service from these guys...
[HTC EVO 3D] KB112:
Sweat warranty...that's dope. lol
[HTC EVO 3D] tyler.durden:
I have a pair of the S9 and S10 Motorola headphones. I bought the S10s as an 'upgrade' but that turned out to not be the case, unfortunately. They weren't as loud and the sound just didn't seem as 'full'. Really the only positive thing about them is that they NEVER cut out on me, and had much better range. My S9s are more comfortable, louder, sound better, but they did cut out at certain angles(probably because I mainly used them with my phone in my pocket instead of on an arm band as recommended).

I just got a pair of the JayBird Freedom headphones for Christmas and they are definitely the best way to go and worth the extra money. The sound and fit is probably as good as you can possibly get with bluetooth in-ear headphones, and of course they have the sweat-proof warranty. I would recommend getting the JayBird's over EVERYTHING else, especially if you're using them for running and working out, as I do. You won't regret it!