Since V2.9 no new ports from me because there are "official" versions from tytung:
http://sites.google.com/site/nexushd2android/nexushd2-gingerbread/releases
************************
previous version:
SD-port of the CLK-Build:
[28.June.2011][MAG/cLK] NexusHD2-Gingerbread V2.8 [GRJ22/Android2.3.4][K: tytung_r10]
>>> Download-Link <<<
The version is almost unmodified.
Changes:
- SD-relevant adjustments
- added OI-Filemanager
This Build creates a 256MB data.img on the first start. If you want a larger phone storage, you can copy a bigger data.img in the android directory before the first start or replace the created 256MB file with a bigger one later (all previous data will be lost) or with the "update" (see below) edit the startup.txt to create another size.
older version:
NexusHD2-Gingerbread V2.7
UPDATE
Bluetooth values in my last version were wrong, if you had BT-Problems replace the rootfs.img from the build with the one from the archive "rootfs_new.7z" - also the cpu scaling governor now will be interactive with the new rootfs (as tytung recomands) - thanks tytung for the solution of this problem.
http://sites.google.com/site/nexushd2android/nexushd2-gingerbread/releases
************************
previous version:
SD-port of the CLK-Build:
[28.June.2011][MAG/cLK] NexusHD2-Gingerbread V2.8 [GRJ22/Android2.3.4][K: tytung_r10]
>>> Download-Link <<<
The version is almost unmodified.
Changes:
- SD-relevant adjustments
- added OI-Filemanager
This Build creates a 256MB data.img on the first start. If you want a larger phone storage, you can copy a bigger data.img in the android directory before the first start or replace the created 256MB file with a bigger one later (all previous data will be lost) or with the "update" (see below) edit the startup.txt to create another size.
older version:
NexusHD2-Gingerbread V2.7
UPDATE
Bluetooth values in my last version were wrong, if you had BT-Problems replace the rootfs.img from the build with the one from the archive "rootfs_new.7z" - also the cpu scaling governor now will be interactive with the new rootfs (as tytung recomands) - thanks tytung for the solution of this problem.
Attachments
Last edited: