NexusHD2 Android Forum

Hi! This ROM work fine!

PS: Will you update the kernel in version 3.4? The 2.6 is a little old...

aiwenor wrote:Hi Tytung, great rom as always, but I can't work with it...
I use DataonEXT and it always installs without problems...the problems appear after the installation.
1. it works but wi-fi ain't working
2. it works, but it restarts to cyanogenmod every time I lock the phone or it locks itself
so I cant use it this way.

On # 1 look for wifi Fixer which may help.

Don't know about # 2..

Thanks man, but now after installing 3.1 it works fine.

Thanks Tytung, great work.

Valou66000 wrote:Hi! This ROM work fine!

PS: Will you update the kernel in version 3.4? The 2.6 is a little old...

No. AFAIK, the kernel 3.x for HD2 is not as good and stable as kernel 2.6 so far.
HD2 is an old device. In my opinion, it's not necessary to use a new kernel.

tytung wrote:No. AFAIK, the kernel 3.x for HD2 is not as good and stable as kernel 2.6 so far.
HD2 is an old device. In my opinion, it's not necessary to use a new kernel.

@Tytung, let me first say that I have a tremendous respect for your outstanding work and dedication to keeping our aging phones alive. Too many people here, and especially at xda, think that upgrading to a version 3.x kernel is a panacea that's going to magically unlock some hitherto unseen performance increase and prolong the lifespan of our aging devices. The fact is, this is impossible. When Linus introduced the 3.x kernel it had little to do with major improvement. It was more that he wanted a starting point for future change to be introduced.

As someone who has been a longtime Linux user I generally agree with your statement I quoted above, however, it's been my experience that kernel updates are necessary for the following reasons:
1) Bug fixes
2) Security updates
3) New or better Hardware support
4) Feature enhancements.

To those reading who are unfamiliar with the kernel development tree, at any given time there are multiple kernels being actively maintained or in development. For example, there are currently 8 stable Linux kernels supported. There is the mainline kernel 3.11, the last two stable versions 3.10.11 and 3.9.11(end of life), and the 5 longterm versions 3.4.x, 3.2.x, 3.0.x, 2.6.34.x, and 2.6.32.x. Tytung's kernel is based on 2.6.32.x which is the oldest actively supported kernel.

There are no forthcoming driver updates for our devices and there hasn't been in some time. Newer kernels don't introduce features supported by the hardware that aren't already supported by the current kernel. So generally speaking, a kernel update isn't justified, at least to a higher major version. Besides doing so might break something somewhere else. It would be, however, appropriate to update within the same major version, as this maintains compatibility,while incorporating the latest back-ported mainline bug fixes and security patches.
.
This is where I pose my question to Tytung..... Do you keep your kernel tree in sync with the 2.6.32.x longterm tree, or is yours a snapshot from when it was forked (except for your patches)?

I ask this because if yours is in-sync, then those who keep posting asking for an updated kernel should look elsewhere or build their own. If it isn't, however, then it's been isolated for a while and could perhaps be re-synced to bring in the enhancements that have been incorporated since it was forked. My 2 cents...

Ciao

Odysseus wrote:
@Tytung, let me first say that I have a tremendous respect for your outstanding work and dedication to keeping our aging phones alive. Too many people here, and especially at xda, think that upgrading to a version 3.x kernel is a panacea that's going to magically unlock some hitherto unseen performance increase and prolong the lifespan of our aging devices. The fact is, this is impossible. When Linus introduced the 3.x kernel it had little to do with major improvement. It was more that he wanted a starting point for future change to be introduced.

As someone who has been a longtime Linux user I generally agree with your statement I quoted above, however, it's been my experience that kernel updates are necessary for the following reasons:
1) Bug fixes
2) Security updates
3) New or better Hardware support
4) Feature enhancements.

To those reading who are unfamiliar with the kernel development tree, at any given time there are multiple kernels being actively maintained or in development. For example, there are currently 8 stable Linux kernels supported. There is the mainline kernel 3.11, the last two stable versions 3.10.11 and 3.9.11(end of life), and the 5 longterm versions 3.4.x, 3.2.x, 3.0.x, 2.6.34.x, and 2.6.32.x. Tytung's kernel is based on 2.6.32.x which is the oldest actively supported kernel.

There are no forthcoming driver updates for our devices and there hasn't been in some time. Newer kernels don't introduce features supported by the hardware that aren't already supported by the current kernel. So generally speaking, a kernel update isn't justified, at least to a higher major version. Besides doing so might break something somewhere else. It would be, however, appropriate to update within the same major version, as this maintains compatibility,while incorporating the latest back-ported mainline bug fixes and security patches.
.
This is where I pose my question to Tytung..... Do you keep your kernel tree in sync with the 2.6.32.x longterm tree, or is yours a snapshot from when it was forked (except for your patches)?

I ask this because if yours is in-sync, then those who keep posting asking for an updated kernel should look elsewhere or build their own. If it isn't, however, then it's been isolated for a while and could perhaps be re-synced to bring in the enhancements that have been incorporated since it was forked. My 2 cents...

Ciao

Thanks.
I didn't keep my kernel tree in sync with the 2.6.32.x longterm tree.
Some kernel devs (including me) have already backported a lot of features into our 2.6.32 kernel, so it's not easy to sync with the longterm tree.

Anyway, the compiled 3.0.16 kernel was released by marc1706 (for cLK).
And a modified version for MAGLDR NativeSD users was released by securecrt.
Thus, anyone who interested in marc1706's kernel 3.0.16 can replace the kernel and all related libs themselves.

whats pan.baidu.com links password .. when i translate it says 4 yards .. whats this .. other 2 links are blocked here ..

godsp33d wrote:whats pan.baidu.com links password .. when i translate it says 4 yards .. whats this .. other 2 links are blocked here ..

The last four chars of the youruls.tytung.com url to the baidu.

E.g., http://yourls.tytung.com/nexushd2-jb31-baidu-rwu1 (password is rwu1)

The main benefit of updating the kernel is not for new features but for bug fixes and security updates. If I understand correctly, the more up-to-date the kernel means the less work for backporting.

Hi everybody,

is it usefull to use SWAP Partition on this ROM with DataOnExt..?