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

Root [UNOFFICIAL][CAF][4.4.4] Cyanogenmod 11 Stable Build 2 (tom1957's camcorder/hq youtube/green tint)

zoombody said:
That said, I just tested this and my rear camera is working with this build. On all recent builds, including the "fixed" ones, I have the green tint. So where did things go wrong?

Here's the link, btw: https://www.androidfilehost.com/?fid=95897840722641185
Click to expand...
Good question. I didn't have the green tint on the decaf version of this rom but I did on the remix version. Haven't tested this one out though, currently on Pac Rom with green tint still.
 
JoshD said:
Good question. I didn't have the green tint on the decaf version of this rom but I did on the remix version. Haven't tested this one out though, currently on Pac Rom with green tint still.
Click to expand...
I haven't had the green camera issue on any of the ROMs. *fingers-crossed*
 
Darren Rutherford said:
Okay, so I found the 1/12 build in the CM12.1 thread, and I flashed it and no green tint! FYI I have had green tint on every other build. Why isn't this build listed on this thread?

Edit: Just to be clear, its the 1/12 CM11 build, I just happened to find the link while browsing the CM12.1 thread :p
Click to expand...
Lol
 
Darren Rutherford said:
This thread seems like it's dead :p
What's new with everyone? Lol
Click to expand...

My excuse is I welcomed my daughter into the world about 3 weeks ago. Between hanging out with her and my wife, school and work, I don't have much time for ROM dev. I was gonna plunge into marshmallow for volt, still might if I get this new computer I've been looking at with a core i7 and 16gb RAM.
 
whoshotjr2006 said:
My excuse is I welcomed my daughter into the world about 3 weeks ago. Between hanging out with her and my wife, school and work, I don't have much time for ROM dev. I was gonna plunge into marshmallow for volt, still might if I get this new computer I've been looking at with a core i7 and 16gb RAM.
Click to expand...
Congrats on becoming a father! And a PC with those specs should do fairly well :P
 
whoshotjr2006 said:
My excuse is I welcomed my daughter into the world about 3 weeks ago. Between hanging out with her and my wife, school and work, I don't have much time for ROM dev. I was gonna plunge into marshmallow for volt, still might if I get this new computer I've been looking at with a core i7 and 16gb RAM.
Click to expand...
Congrats bro! Enjoy spending your time with the little one :) and if you get around to Marshmallow, I'll join you. @Bad_MOFO_33 had a test build of CM13, and I build it myself using his sources (can't get past a persistent NFC force-close message though). But anyways, congratulations!
 
whoshotjr2006 said:
Relevant dev info:

the relevant repos you need from me (based on Quarx2k's Cm11 source) are:
device: https://github.com/touchpro/cm11_device_lge_x5
vendor: https://github.com/touchpro/vendor_lge_x5

and kernel based on bad_mofo_33's caf:
https://github.com/touchpro/android_kernel_lge_msm8226
Click to expand...

Which tree did you base this build on? CAF 4.4.4 or Cyanogenmod 11? Do you mind sharing your manifest? That would be a big big big help, thanks! (Working on a sister device of the X5, strugglin'.)
 
culot said:
Which tree did you base this build on? CAF 4.4.4 or Cyanogenmod 11? Do you mind sharing your manifest? That would be a big big big help, thanks! (Working on a sister device of the X5, strugglin'.)
Click to expand...

i just downloaded cm11 source, added in hardware_qcom_display_caf-new and media_caf-new, hardware_qcom_fm, qcom_common and the above named repos from me. there was a lot of tinkering to get it to where it needed to be in terms of booting and things working.

follow this: http://forum.xda-developers.com/showthread.php?t=2450045 to get all the partition sizes, remember to multiply partition size by 1024 to get the true size. what device are you working on, because i might be able to help you integrate the kernel crud to get it booting.
 
Thanks! I wasn't aware of those caf-new repos.

The device LG Fx0, which is based on the X5, but crossbred with the LG AKA -- is shares its 16GB storage, 1.5GB ram, 720p JDI Incell. I've got it mostly brought up, but there is specifically two problems that I have not been able to overcome:

The kernel requires a pronto_wlan module. In the stock firmware it is built from '/vendor/qcom/opensource/wlan/prima'. I've been through a number of branches for the same version it uses, even one that is supposedly the exact branch that they used, but no go, if I use a custom kernel no boots. I've also tried building the wlan module into the kernel by bringing the prima in-tree, 'drivers/staging/prima'. No go. So I'm stuck using the stock kernel with custom ramdisk.

Okay, that's not a huge big deal, I can live with that.

The bigger problem is that there is an audio_policy issue that prevents boot:

ServiceManager: Waiting for service media.audio_policy...
AudioSystem: AudioPolicyService not published, waiting...

I have spent months trying to overcome this and cannot make much headway. I think the problem may lie in the av frameworks, but I've tried every branch, every variation possible. The original audio seems to be Legacy, but CM legacy doesn't produce the libs that are too close to it. Definitely proprietary mofo running afoul.

If I dump a ton of binaries and libaries I can get boots, but its hacky and buggy.

My repos are at github.com/culots:

device_lge_madai @ cm-11.0 branch
kernel_lge_madai @ cm-11.0 branch
vendor_lge_madai @ cm-11.0 branch

Madai is the codename for this device. Also note the the kernel code is very close to the X5 (and to the G2M and AKA). The original Japanese firmware even includes a bootanimation for the X5, showing that that is where they started from.

BTW: LG Fx0 are still going for $60 on Amazon US if anyone wants a cool fully-unlocked, bootloader-unlocked device to tinker with. :) Hell, if you want to invest some serious dev work into this beast, I'd be willing to help finance your own copy of the device. I appear to be the only person working on it, and I feel terrible that I've let the users down on this.

That audio_policy issues prevents not only CM builds, but also FxOS builds. And the stock firmware is old and moldy, with no chance of an update from LG or KDDI or Mozilla.
 
whoshotjr2006 said:
i just downloaded cm11 source, added in hardware_qcom_display_caf-new and media_caf-new, hardware_qcom_fm, qcom_common and the above named repos from me. there was a lot of tinkering to get it to where it needed to be in terms of booting and things working.

follow this: http://forum.xda-developers.com/showthread.php?t=2450045 to get all the partition sizes, remember to multiply partition size by 1024 to get the true size. what device are you working on, because i might be able to help you integrate the kernel crud to get it booting.
Click to expand...

Ughh, nevermind. I found the problem: it was the camera HAL crap. I switched to specific_camera and now all my builds come together well. Except for the kernel wlan issue, but whatever.
 
culot said:
Ughh, nevermind. I found the problem: it was the camera HAL crap. I switched to specific_camera and now all my builds come together well. Except for the kernel wlan issue, but whatever.
Click to expand...

sorry i couldnt help more, been going though some personal crap that has my brain in other places. good you found what you did though, and make sure to port your work forward to cm13 for your device from what we are doing here too.
 
whoshotjr2006 said:
sorry i couldnt help more, been going though some personal crap that has my brain in other places. good you found what you did though, and make sure to port your work forward to cm13 for your device from what we are doing here too.
Click to expand...

It just irks me that this problem has been blocking me for months, and since the error read 'audio-policy' I've been looking for audio issues, only to have it turn out to be the camera. Nice to have it working. Now to update the kernel to work with cm13! Because of the specific quirks in the panel code that's going to be fun. Oy!
 
vic121 said:
I flashed this but keep getting a "AOSP keyboard has stopped working". I use TWRP 2.8.7.0, would that be why?
Click to expand...
Its a bug certain users are experiencing, I had that problem before switching to CM13. You can flash @Curtis1973 Xperia keyboard zip, worked for me on every ROM that gave me the AOSP keyboard error. You'll have to search for the zip here on AF (not enough time on my break).
 
have a boost mobile ls740, used at Ringplus. The phone is rooted. I can switch the system between ZV6 debloated ROM and cm-11-20150112 with TWRP backup/restore.

When flashed with ZV6 debloated ROM, The LTE works.
When loaded with cm-11-20150112, It can get 3G eHRPD networks only, no LTE, why? Is it relatded to PRL or profile?

cm-11-20150112 is the only no-stock ROM, that doesn’t thrown a green tint on the back camera.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom