• 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)

yea should be inside framework apk somewhere, however, that i found in zv6
edit its inside cm11 framework to
 
whoshotjr2006 said:
no clue bud. i tried different things, messing with fstab.x5, trying to make vold.fstab work with 4.4.4, and even recompiling framework-res.apk from scratch with a modified storage-list.xml, and cant get anything to stick. if you have any ideas that take compiling from scratch to accomplish, lemme know and ill roll you a custom build.
Click to expand...


PimpinEZ said:
yea should be inside framework apk somewhere, however, that i found in zv6
Click to expand...


I'm a doofus, I didn't fully read @whoshotjr2006's post, he already messed with those files. Whelp I'm out of ideas.
 
its all good man at least your learning the file structure if and when you switch devices.
 
Try searching around for storage/mount/mmcblk/mpt or userdata? try searching the logcat too it might have a clue? this is why i said to set it as swap since DDR is already on the mmc block. id think we may be able to even partition the ddr block somehow? to crazy
Code: 
ls -al /dev/block/platform/msm_sdcc.1/by-name
yafilthy@Yafilthy-Lenovo-G50-45:~$ adb shell
lock/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1970-01-04 10:35 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 10:35 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 10:35 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 10:35 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 10:35 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 10:35 carrier -> /dev/block/mmcblk0p
30
lrwxrwxrwx root root 1970-01-04 10:35 drm -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 10:35 eksst -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 10:35 encrypt -> /dev/block/mmcblk0p
22
lrwxrwxrwx root root 1970-01-04 10:35 factory -> /dev/block/mmcblk0p
26
lrwxrwxrwx root root 1970-01-04 10:35 fota -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 10:35 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 10:35 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 10:35 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 10:35 laf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 10:35 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 10:35 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 10:35 modemst1 -> /dev/block/mmcblk0
p11
lrwxrwxrwx root root 1970-01-04 10:35 modemst2 -> /dev/block/mmcblk0
p12
lrwxrwxrwx root root 1970-01-04 10:35 mpt -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 10:35 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 10:35 persist -> /dev/block/mmcblk0p
14
lrwxrwxrwx root root 1970-01-04 10:35 rct -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 10:35 recovery -> /dev/block/mmcblk0
p17
lrwxrwxrwx root root 1970-01-04 10:35 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 10:35 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 10:35 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 10:35 sbl1b -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 10:35 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 10:35 sns -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 10:35 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 10:35 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 10:35 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 10:35 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 10:35 userdata -> /dev/block/mmcblk0p34
root@x5:/ #
 
Last edited by a moderator:
PimpinEZ said:
Try searching around for storage/mount/mmcblk/mpt or userdata? try searching the logcat too it might have a clue? this is why i said to set it as swap since DDR is already on the mmc block. id think we may be able to even partition the ddr block somehow? to crazy
Click to expand...

whoa hang on... what is the ddr partition? ram?
 
ShapeShifter499 said:
whoa hang on... what is the ddr partition? ram?
Click to expand...
I researched all day for DDR partition. Everything was ambiguous or totally unrelated. From what it's able find about DDR partition :
  • mmcblk0p21 (our device)
  • 512 kb (our device, maybe others)
  • wrote over with ddr.bin during FOTA (.bin file containing all zeroes)
  • not every device has this partition
I know...not much, but that was Google searching. I'll try and look with some "Specialized Search Engines". I'm curious what is in there and why it gets zeroed.

Pic from DiskInfo apk
Screenshot_2016-01-19-20-45-25.png
 
Last edited:
Camera working great, no green tint.

Only issue I'm running into is no access to the back button. The only time the back button does work is to hide the keyboard. Home and menu buttons work as normal.

AOSP keyboard also force closes. I flashed Curtis1973 Xperia keyboard mod, fixed that.

Other that this is really smooth!!

Edit. I reflashed the rom, back button works.
 
Last edited:
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
 
Last edited:
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...
Note that this is a 1/12/2015 build compared to 1/11/2016.
 
You must log in or register to reply here.
Back
Top Bottom