NexusHD2 Android Forum

Hi guys,

thank you for building and providing CM images for the HD2!
I'm happily using an Android 4.1 version myself, which mostly works fine. However, I'd like to upgrade to KitKat (4.4), and I'd like to do so with a build free of the google apps.
Do you have to take any special steps, apply any patches, to build such an image from source myself?

Thank you

n56L wrote:Hi guys,

thank you for building and providing CM images for the HD2!
I'm happily using an Android 4.1 version myself, which mostly works fine. However, I'd like to upgrade to KitKat (4.4), and I'd like to do so with a build free of the google apps.
Do you have to take any special steps, apply any patches, to build such an image from source myself?

Thank you

You could remove google apps and libs yourself. It's easier.
If you want to build a working Kitkat ROM for HD2 from the CM source code, you need to do everything you said because HD2 is not supported by the CM team.

build a working Kitkat ROM for HD2 from the CM source code

yep, that is exactly what I intend to do

you need to do everything you said

What is everything? So what sources / source versions do you use, which patches do you apply on them, etc…

you need to do everything you said

What is everything? So what sources / source versions do you use, which patches do you apply on them, etc…

The HD2 is an old device. You probably should start with locating and understanding old legacy code required to make CM work with the HD2 when you read thru the sources and have a good grasp of the legacy drivers and code you can start to experiment with different builds. I am pretty sure most of the info you need is available with a little research.

Sent from my Nexus 7

As far as I know, most individual developers tend to get the paches from the evervolv team to build working 4.x ROMs, but since 4.2 there has been tons of problems regarding kernel and driver binaries and stuff, such as camera glitches, tethering, HWA (camcorder and 720p decoding) and every other issue. Tytung himself has built the most stable kernel till now and has made enormous effort on getting all features to work, like LowSoundFixer, legacy WiFi code for native tethering fix, camera app replacement, HWA support and so on. My suggestion would be to ask tytung and ask what you can do to use his binaries or to contact the other developers like pixelfreak and chautruongthinh and see what they've done. Of course you could try and do as much as you want, if you're capable of doing it. As you might know the backported kernel is a chaos of workarounds and missing features, so kernel developers are welcomed. Initially everything was based on Cotulla's inverse engineering of WM 6.5 drivers and that had been a terribly lot of work, so it's reasonable to avoid reinventing the wheel again yourself.

Gesendet von meinem HTC One X mit Tapatalk

Tytung himself has built the most stable kernel till now and has made enormous effort on getting all features to work

And I thought perhaps this effort might be (slightly) documented and reproducible… As usual on Linux systems, you know?

You could remove google apps and libs yourself. It's easier.

Well, this might also be an option for me. Is there any more to it than removing the individual .apks? Do I need to delete lines in the updater-script ?

Hi,

n56L wrote:Well, this might also be an option for me. Is there any more to it than removing the individual .apks? Do I need to delete lines in the updater-script ?

I'm still trying to figure out which files (or file contents) in tytungs ROM belong to the gapps package. Especially the Play Store apk I could not find. The content of the official gapps package did not really help me.