• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][UNOFFICIAL][4.4.4] DeCAF Cyanogenmod 11, Release 1

whoshotjr2006 said:
Hey can someone upload a boost mobile stock ROM apns_conf.XML from /etc? And if anyone has the sprint prepaid volt, that one too. I need to see the differences (or lack thereof) in those files between carriers.
Click to expand...
Here, I pulled this with root browser from my boost volt running the stock updated rom. i sent a test mms to make sure my mms was working and it did. so this should be the right one. sorry for the zip file.. AF wouldnt let me upload the xml..
 

Attachments

Corey Fields said:
Here, I pulled this with root browser from my boost volt running the stock updated rom. i sent a test mms to make sure my mms was working and it did. so this should be the right one. sorry for the zip file.. AF wouldnt let me upload the xml..
Click to expand...

Thank you for that. It looks like its the same as virgin's so I think we are good there.
 
Corey Fields said:
So, do you have any progress with the audio? I'd love to use this as my daily driver but I can't do without sound. But I do want to thank you for all your hard work so far.
Click to expand...

Not yet I'm working on getting quarx's caf kernel source up for us right now and fighting with random freezes on my build machine. I think that might help sound if we can get it compiling and it would sure help me if I could get my PC working right again lol.
 
whoshotjr2006 said:
Not yet I'm working on getting quarx's caf kernel source up for us right now and fighting with random freezes on my build machine. I think that might help sound if we can get it compiling and it would sure help me if I could get my PC working right again lol.
Click to expand...
Have you redone the paste on your CPU?
 
halrulez said:
Have you redone the paste on your CPU?
Click to expand...

i probably should, i've had this laptop for almost 2 years now, i guess may would be two years lol. probably just time for an upgrade to a decent i5 or i7 haswell desktop.

on a related note, https://github.com/touchpro/android_kernel_lge_msm8226

it was rough and took about a week straight of analyzing code to figure out what others did and it all boiled down to a Kconfig file, but thats an LG Volt CAF kernel. it compiled fine for me, it might complain about the modules not being built but that is 1) just a compiler warning and 2) supposedly the modules are built into the kernel. I have a build finishing up now with display-caf-new, media-caf-new and audio-caf sources compiling, and everything seems to be going smooth.

I cannot guarantee anything, but if the rom boots i'll upload it and we can see what works and what doesnt. If CAF works out for us, I'd like to abandon the stock kernel. Quarx2k has a rolling CAF w7 official nightly build for Cyanogenmod, so hopefully we can too eventually.
 
whoshotjr2006 said:
i probably should, i've had this laptop for almost 2 years now, i guess may would be two years lol. probably just time for an upgrade to a decent i5 or i7 haswell desktop.

on a related note, https://github.com/touchpro/android_kernel_lge_msm8226

it was rough and took about a week straight of analyzing code to figure out what others did and it all boiled down to a Kconfig file, but thats an LG Volt CAF kernel. it compiled fine for me, it might complain about the modules not being built but that is 1) just a compiler warning and 2) supposedly the modules are built into the kernel. I have a build finishing up now with display-caf-new, media-caf-new and audio-caf sources compiling, and everything seems to be going smooth.

I cannot guarantee anything, but if the rom boots i'll upload it and we can see what works and what doesnt. If CAF works out for us, I'd like to abandon the stock kernel. Quarx2k has a rolling CAF w7 official nightly build for Cyanogenmod, so hopefully we can too eventually.
Click to expand...
Can't wait till the next build :D
 
whoshotjr2006 said:
i probably should, i've had this laptop for almost 2 years now, i guess may would be two years lol. probably just time for an upgrade to a decent i5 or i7 haswell desktop.

on a related note, https://github.com/touchpro/android_kernel_lge_msm8226

it was rough and took about a week straight of analyzing code to figure out what others did and it all boiled down to a Kconfig file, but thats an LG Volt CAF kernel. it compiled fine for me, it might complain about the modules not being built but that is 1) just a compiler warning and 2) supposedly the modules are built into the kernel. I have a build finishing up now with display-caf-new, media-caf-new and audio-caf sources compiling, and everything seems to be going smooth.

I cannot guarantee anything, but if the rom boots i'll upload it and we can see what works and what doesnt. If CAF works out for us, I'd like to abandon the stock kernel. Quarx2k has a rolling CAF w7 official nightly build for Cyanogenmod, so hopefully we can too eventually.
Click to expand...
Great work and patience man! Can't wait to try the next build, i wish i knew more about CM to help you but I'll definitely try. When i can I'd like to make a donation too, this isn't exactly easy dev work. [emoji3]
 
My candy rom boots but is quite buggy, built with quarx kernel cm12, just need to clean it up a little then will release for testing. Cant test data here (havent paid my bill till after holidays) sound is glitchy as is video only tested with youtube. Only front camera is working, and gps seems wonky. But should have some things worked out by later tonight or mid tomorrow.
 
Bad_MOFO_33 said:
My candy rom boots but is quite buggy, built with quarx kernel cm12, just need to clean it up a little then will release for testing. Cant test data here (havent paid my bill till after holidays) sound is glitchy as is video only tested with youtube. Only front camera is working, and gps seems wonky. But should have some things worked out by later tonight or mid tomorrow.
Click to expand...
When you release this ROM, if you can can you Make a post of this thread so I could know because I'm checking this ROM page daily and i would be happy to be one of the first people to test this rom as soon as its released. Thank you
 
Bad_MOFO_33 said:
My candy rom boots but is quite buggy, built with quarx kernel cm12, just need to clean it up a little then will release for testing. Cant test data here (havent paid my bill till after holidays) sound is glitchy as is video only tested with youtube. Only front camera is working, and gps seems wonky. But should have some things worked out by later tonight or mid tomorrow.
Click to expand...

i got mine booting but i cant really test it because my touchscreen isnt working. thats with the kernel that built that supposedly didnt need /system/lib/modules. i'm also having trouble making modules, it keeps dying on me at lge_ts_core.c about a multiple definition of 'power_block' at line 1121. did you run into that, and if so do you remember how you fixed it? if i comment out "CONFIG_TOUCHSCREEN_MELFAS_MMS136=y" in defconfig it compiles correctly, but according to the stock kernel defconfig thats something we need.

drivers/input/touchscreen/lge_ts_core.o: In function `touch_lock_func':
/home/jesse/android/out/target/product/x5/obj/KERNEL_OBJ/../../../../../../kernel/lge/msm8226/drivers/input/touchscreen/lge_ts_core.c:1121: multiple definition of `power_block'
drivers/input/touchscreen/mms100a_ts.o:/home/jesse/android/out/target/product/x5/obj/KERNEL_OBJ/../../../../../../kernel/lge/msm8226/drivers/input/touchscreen/mms100a_ts.c:299: first defined here
CC drivers/mmc/card/queue.o
/home/jesse/android/kernel/lge/msm8226/scripts/Makefile.build:375: recipe for target 'drivers/input/touchscreen/built-in.o' failed
make[5]: *** [drivers/input/touchscreen/built-in.o] Error 1
/home/jesse/android/kernel/lge/msm8226/scripts/Makefile.build:443: recipe for target 'drivers/input/touchscreen' failed
make[4]: *** [drivers/input/touchscreen] Error 2
/home/jesse/android/kernel/lge/msm8226/scripts/Makefile.build:443: recipe for target 'drivers/input' failed
make[3]: *** [drivers/input] Error 2
make[3]: *** Waiting for unfinished jobs....
 
@whoshotjr2006 i used quarx cm12 build, without much error, definitely not driver errors. did you pull it source from repo? I would delete msm8226 and repo sync, also which defconfig are you using?


On a side note.. I just started my rebuild of Candy5. after make clean && repo sync was hit with a few errors but hopefully they are gone.
mka recoveryimage = built
mka bootimage = built
mka libandroid_runtime = built
mka services = built
mka framework = built
mka systemimage = building now
mka otapackage = ....

I opened a channel on freenode name ##LG_VOLT if anyone wants to chat about things
 
Last edited:
Bad_MOFO_33 said:
@whoshotjr2006 i used quarx cm12 build, without much error, definitely not driver errors. did you pull it source from repo? I would delete msm8226 and repo sync, also which defconfig are you using?


On a side note.. I just started my rebuild of Candy5. after make clean && repo sync was hit with a few errors but hopefully they are gone.
mka recoveryimage = built
mka bootimage = built
mka libandroid_runtime = built
mka services = built
mka framework = built
mka systemimage = building now
mka otapackage = ....

I think i am going to open a channel on freenode name ##LG_VOLT if anyone wants to chat about things
Click to expand...

I'm using a custom defconfig and ported over the msm8926 stuff in arch/arm/mach-msm and arch/arm/boot/DTS with stock x5 DTS files. Are you using the cm11_msm8226_defconfig and quarxs w7ds DTS files when you build?
 
there should be a line in the cm11_msm8226_defconfig about W7(just search W7) edited it to read CONFIG_MACH_MSM8926_X5_SPR=y

i can send you the source if you want
 
Bad_MOFO_33 said:
there should be a line in the cm11_msm8226_defconfig about W7(just search W7) edited it to read CONFIG_MACH_MSM8926_X5_SPR=y

i can send you the source if you want
Click to expand...

That would be awesome, that way I can see what we did different. I do have the config mach msm8926 x5 spr line in defconfig, I just thought there was more file work to it when you change the kernel target mach. But if its working the way you have it, I can't argue with that lol.
 
Bad_MOFO_33 said:
think in mach-msm the makefile and kconfig, and lge folder of mach-msm makefile
Click to expand...

Touchscreen works with your kernel? I'm still trying to figure out why mines not working, did you change anything else in defconfig beyond the x5 spr line? Also, is yours building modules and putting them in system/lib/modules?

I think I got the make files and kconfigs set right from comparing them to stock, but I probably missed something.

edit: sorry, mobile didnt show me you uploaded. thanks!
 
Last edited:
didnt change anything else in the defconfig, not too sure about other files though ( was stuck on it for about a day, before it decided to not error out) also was having a hell of a time using the gcc from cm11 thats why i went up to cm12
 
Bad_MOFO_33 said:
didnt change anything else in the defconfig, not too sure about other files though ( was stuck on it for about a day, before it decided to not error out) also was having a hell of a time using the gcc from cm11 thats why i went up to cm12
Click to expand...

did you set #TARGET_BOARD_USE_DTS := msm8226-x5_spr_us or leave it out in BoardConfig.mk for your rom compile?
 
Bad_MOFO_33 said:
so got done compiling, wipe data factory reset. flash new rom, reboot,...security error:saddroid:
was able to restore though, weird that my new recovery i just made isnt booting either, think something got screwy in the kernel???? will try again tomorrow
Click to expand...

That's awesome your getting so far though, I'm still floundering in the kernel lol. I tried your kernel source and ran into module compile problems on cm11, so I went back to what I had before and compiling everything from scratch. Got through kernel errors with stock defconfig and gonna see what the ROM does when it gets done.

Good luck man, I'm happy as hell to have you to swap ideas with, and everyone else here too. We have an awesome community here.
 
You must log in or register to reply here.
Back
Top Bottom