Root [ROM][WIP][4.4.2] CyanogenMod 11.0

[EagerestWolf]

80% of Cyanogenmod base synced

 

[rbheromax]

Can diff find the difference in 2 ramdisks?

yea but it'd be alot diff becuase of huawei's proprietary stuffs. its worth a shot tho

 

[EagerestWolf]

Ok, so this is weird. I went through the sync process, downloaded all of my lovely device files, and I did build/envsetup.sh, but I am getting an error that there is no command to make target bacon.

 

[rbheromax]

hmmmm....idk well ig stick with your command you use, since its essentially the same thing
im re--syncing now and gonna do a full build also. to see where things are so far

 

[EagerestWolf]

Found the issue, on my local repo, the fstab location was wrong and if it fails to find any file the build system will not make bacon. Also, sorry for the sloppy commits, git on my machine is dumb (and I gotta remember to pull before I commit).

 

[rbheromax]

yea sorry, i fixed that in a commit about an hour ago. my bad

 

[EagerestWolf]

No, it's good. I am just terrible at Git. I am used to Github for Windows. I need to remember to always pull before committing, so I don't have to fix silly issues like that with sloppy commits.

 

[EagerestWolf]

Build started. ETA: about 3 hours

 

[rbheromax]

wen i get more time, i will look into the ramdisk issue. that'll prolly be tomorrow. im a high school student so during the day im pretty busy. i'll prolly take a look tomorrow afterschool if i dont get started tonight. i gotta work a lil on my kitkat port for the ZTE Warp also

 

[EagerestWolf]

wen i get more time, i will look into the ramdisk issue. that'll prolly be tomorrow. im a high school student so during the day im pretty busy. i'll prolly take a look tomorrow afterschool if i dont get started tonight. i gotta work a lil on my kitkat port for the ZTE Warp also

That's cool. I am gonna work on this for the time being. I will also try to get some diffs on the ramdisks done. I should also start on CM9 for the Galaxy Centrua I have lying around here somewhere, but that will be God only knows when, plus I have work tomorrow, so I need to get some sleep myself.

 

[rbheromax]

ok im about to commit the chages for fstab.
did u add the set_metadata workaround hack to your local repo yet?

 

[EagerestWolf]

ok im about to commit the chages for fstab.
did u add the set_metadata workaround hack to your local repo yet?

My local repo is up to date with the Github repo

 

[rbheromax]

Do this:

Use this flag in BoardConfig.mk

USE_SET_METADATA := false

and then apply this manually:
https://github.com/temasek/android_build/commit/e6dd009c919c5b33cf04c9a5ef09cf19ae541728

then compile again. it should flash completely after removing props (if that issue occurs also)

 

[EagerestWolf]

Do this:

It's already set.

 

[EagerestWolf]

Kinda major issue. For some reason, the frameworks are not building at all. My framework folder only contains a hardware jar and a bluetooth jar. Not sure what is wrong...

 

[EagerestWolf]

On a more positive note, I finally got the proper recovery for KitKat to compile correctly. WIN!

 

[EagerestWolf]

Psh, this is gonna be easy. It's only 1511 lines. (I'm lying, I'm sweating already)

https://gist.github.com/Eagerestwolf/8798733

 

[rbheromax]

Kinda major issue. For some reason, the frameworks are not building at all. My framework folder only contains a hardware jar and a bluetooth jar. Not sure what is wrong...

yea idk this pissed me off

i had to do

mmm frameworks/base/core/res
mmm frameworks/base
mka ext android.policy am apache-xml bouncycastle bu content core core-junit
mka ime input pm services svc telephony-common uiautomator

and then watever make command u have to get a zip

its a bit extra but it works

 

[EagerestWolf]

yea idk this pissed me off

i had to do

mmm frameworks/base/core/res
mmm frameworks/base
mka ext android.policy am apache-xml bouncycastle bu content core core-junit
mka ime input pm services svc telephony-common uiautomator

and then watever make command u have to get a zip

its a bit extra but it works

Well you have to do that no more (turns out when I added all of the msm7627a stuff I deleted my line in the device_y301a1.mk file to call full.mk ... oops)

Anyhow, I am now at a stuck point, because I keep getting this error (spoilers, my name is Seth):

/home/seth/android/cm-11.0/out/target/product/y301a1/obj/EXECUTABLES/hostapd_intermediates/src/drivers/driver_nl80211.o:driver_nl80211.c:function wpa_driver_nl80211_ops: error: undefined reference to 'wpa_driver_nl80211_driver_cmd'

And I have no idea how to fix it, because I checked the driver_nl80211.c, and the variable is instantiated and defined, so idk.

Just to be safe, I did a make clean, make clobber, and I am building again.

 

[EagerestWolf]

I really should use CCACHE, these builds would go so much faster...but on Virtual Box, meh.

 

[EagerestWolf]

Nevermind CCACHE isn't helping, turns out I am hitting the execution cap on my processor. Why you no make faster processors Intel? (Hitting that cap actually kinda does say something, I have an Intel i5 hyper-threaded so much that my computer thinks I have a quad core [it's a dual core tho], plus it's an Ivy Bridge, so this is actually a powerhouse CPU)

 

[rbheromax]

Well you have to do that no more (turns out when I added all of the msm7627a stuff I deleted my line in the device_y301a1.mk file to call full.mk ... oops)

Anyhow, I am now at a stuck point, because I keep getting this error (spoilers, my name is Seth):

/home/seth/android/cm-11.0/out/target/product/y301a1/obj/EXECUTABLES/hostapd_intermediates/src/drivers/driver_nl80211.o:driver_nl80211.c:function wpa_driver_nl80211_ops: error: undefined reference to 'wpa_driver_nl80211_driver_cmd'

And I have no idea how to fix it, because I checked the driver_nl80211.c, and the variable is instantiated and defined, so idk.

Just to be safe, I did a make clean, make clobber, and I am building again.

try removing wpa_supplicant_version from BoardConfig.mk (while leaving the other wifi stuff intact)
it'll compile then i think

 

[EagerestWolf]

Yeah, that worked, but now I am stuck at this stupid make_ext4fs error again. I swear that program is tempermental. Sometimes, it works; sometimes it doesn't.

 

[EagerestWolf]

Figired it out. The system image size was too small so make_ext4fs wasn't able to make the superblocks

 

[EagerestWolf]

Build succeeded, but zip will not install. Evidently, the USE_SET_METADATA is a 0 or 1 option not true or false, because even though the value was set to false, Cyanogenmod read a 1 during build. Changed that to 0 to see what happens.