Database Users

[Q] Cherry-Picking help

I want to cherry-pick "custom notification led settings" from purity to my aosp build.
So I went ahead and picked up these two commits
https://github.com/KitKatPurity/pla...mmit/c85834ed460ec99e0752f1f13e58cad74abf844e
and
https://github.com/KitKatPurity/pla...mmit/b37fdf4238b11b0232b12f218294131ea77ec309
The framework part ran well and there was no conflict. The settings part returned a small conflict which I solved myself. Now as I go on compiling, everything compiled good but then at the time of Settings.apk compiling it returned this error.
Code:
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : class DisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable KEY_WIFI_DISPLAY
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:123: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
if (mWifiDisplayStatus.getFeatureState()
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:124: cannot find symbol
symbol : variable WifiDisplayStatus
location: class com.android.settings.DisplaySettings
== WifiDisplayStatus.FEATURE_STATE_UNAVAILABLE) {
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:125: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
getPreferenceScreen().removePreference(mWifiDisplayPreference);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:126: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = null;
^
packages/apps/Settings/src/com/android/settings/purity/notificationlight/ApplicationLightPreference.java:170: method does not override or implement a method from a supertype
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
11 errors
make: *** [out/target/common/obj/APPS/Settings_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Here are the link of the 2 files where the error is shown:
ApplicationLightPreference.java
DisplaySettings.java
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.

Since this is a question why not post in the section clearly marked for questions??
Sent from my Nexus 4 using xda premium

brajesh.sharma87 said:
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.
Click to expand...
Click to collapse
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.

MBQ_ said:
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.
Click to expand...
Click to collapse
Not sure what to do about the first line but here's the log
Code:
I/ActivityManager( 647): Displayed com.android.settings/.Settings: +631ms
I/ActivityManager( 647): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 9823
D/audio_hw_primary( 170): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/ACDB-LOADER( 170): ACDB -> send_afe_cal
D/SubSettings( 9823): Launching fragment com.android.settings.DisplaySettings
D/AndroidRuntime( 9823): Shutting down VM
W/dalvikvm( 9823): threadid=1: thread exiting with uncaught exception (group=0x415adba8)
E/AndroidRuntime( 9823): FATAL EXCEPTION: main
E/AndroidRuntime( 9823): Process: com.android.settings, PID: 9823
E/AndroidRuntime( 9823): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime( 9823): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime( 9823): at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime( 9823): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime( 9823): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 9823): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 9823): at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 9823): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9823): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 9823): at com.android.settings.DisplaySettings.onCreate(DisplaySettings.java:134)
E/AndroidRuntime( 9823): at android.app.Fragment.performCreate(Fragment.java:1678)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062)
E/AndroidRuntime( 9823): at android.app.BackStackRecord.run(BackStackRecord.java:684)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447)
E/AndroidRuntime( 9823): at android.app.Activity.performStart(Activity.java:5240)
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2168)
E/AndroidRuntime( 9823): ... 11 more
W/ActivityManager( 647): Force finishing activity com.android.settings/.SubSettings
W/ActivityManager( 647): Force finishing activity com.android.settings/.Settings
W/ActivityManager( 647): Activity pause timeout for ActivityRecord{41e72210 u0 com.android.settings/.SubSettings t14 f}
W/Sidekick_LocationOracleImpl( 2543): Best location was null
I/Process ( 9823): Sending signal. PID: 9823 SIG: 9
V/SearchControllerCache( 2543): creating SearchController
W/Sidekick_LocationOracleImpl( 2543): Best location was null
W/GCoreFlp( 8127): No location to return for getLastLocation()
I/ActivityManager( 647): Process com.android.settings (pid 9823) has died.
I/WindowState( 647): WIN DEATH: Window{419b9318 u0 com.android.settings/com.android.settings.Settings}
D/dalvikvm( 2543): GC_FOR_ALLOC freed 1110K, 57% free 5133K/11704K, paused 27ms, total 27ms
I/MicroHotwordRecognitionRunner( 2543): Starting hotword detection.
D/audio_hw_primary( 170): select_devices: out_snd_device(0: ) in_snd_device(34: voice-rec-mic)
E/ACDB-LOADER( 170): Error: ACDB AudProc vol returned = -8
D/dalvikvm( 2543): GC_CONCURRENT freed 6K, 51% free 5756K/11704K, paused 2ms+3ms, total 32ms
I/SearchController( 2543): #onHotwordDetectorStarted

brajesh.sharma87 said:
Not sure what to do about the first line but here's the log
Click to expand...
Click to collapse
Something is wrong in the onCreate method of DisplaySettings.java

Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo

GeyerA said:
Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo
Click to expand...
Click to collapse
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.

brajesh.sharma87 said:
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.
Click to expand...
Click to collapse
Hello, good that you have some progress although you might feel disappointed that it does not work. Here is one reason why I personally do not cherry-pick complex commits as it will also add the lines which are not part of that commit but part of my code.
Anyhow, I believe you missed one small thing which is in android_device_hammerhead. Sorry I forgot that one.
https://github.com/KitKatPurity/pla...mmit/217378d3e6a7a5370e7c1583fcfb4ae1e7a9ac7c
Especially this one in overlay/frameworks/base/core/res/res/values/config.xml
Code:
+ <!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
+ <bool name="config_intrusiveBatteryLed">true</bool>
+
+ <!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
+ <bool name="config_multiColorBatteryLed">true</bool>
+
I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:

GeyerA said:
........I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:
Click to expand...
Click to collapse
Thanks but as i said, i wont have access to my laptop for next 8-10 days, will continue once i come back.
Sent from my Nexus 4 using Tapatalk

@GeyerA you're a genius. I've been working on this for last 1 month and finally succeeded.
As I didnt have access to my laptop and the resolution that u you gave was also possible through apk tool, I sent the framework-res.apk to a friend and asked him to just change those two values to 'true' he did so and sent the same to me and boom it worked. Thank you so very much.
Sent from my Nexus 4 using Tapatalk

Hello. I am happy to hear; great satisfaction that I could help. But the credit is Dario's from Kitkatpurity and Martin_Ro's from PSX. They helped me a lot and I suffered much more than you. No biggie but please use the thanks button ....
Sent from my AOSP on HammerHead using xda app-developers app

[PORT][CM11] Xperia Z2 Sirius Smart Social Camera

Hello Friends I Ported Xperia Z2 Smart Social Camera Including Latest AR Effect,Background Defocus,Info Eye,Social live,Vine,Motionshot,Motiongraph For Xperia,Wikitude Places,Voice Balloon Photo,AR Effect For Line,V1 Sports For Sony Xperia Phones Running CM11 Kitkat Like Xperia M,SP,TX,V,L etc. I Hope Everyone Like & Enjoy It.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
AR Effect
Switch your camera to AR Effect mode and add fun animations to your photos and videos. Ranging from dinosaurs to ocean-life, these fully customisable themes can be easily edited.
Background Defocus
Create a blurred out background or foreground. Background Defocus simulates a shallow depth of field, capturing two image planes at different focus settings and allowing you to merge the different depths.
Info-eye™
Photograph an object and Info-eye™ will instantly give you all the relevant information you need, right through your camera viewfinder.
Social live
With Social live, you can broadcast every precious moment as it happens live via Facebook. Get your friends’ responses right on the screen and keep the conversation going all in real time.
Vine
Vine is the best way to see and share life in motion. Create short, beautiful, looping videos in a simple and fun way for your friends and family to see.
Motion Shot
This app allows you to capture a short movie by automatically rendering the movement into a single still image so that it appears to be a continuous picture. It is perfect for creating animated images with unique expressions in action scenes involving sports, animals, kids, friends, vehicles, airplanes and moving objects.
Motiongraph for Xperia™
Motiongraph for Xperia™ is a smartphone application that creates unusual images in which part of the image moves like a video.
Amaze your friends with these unique images that are limited only by your imagination.
Motiongraph for Xperia™ allows you to create your image in three simple and intuitive steps:
1. Shoot: Tap a button to record a video about 2 seconds in length.
2. Edit : Swipe across the screen to define the areas that you want it to move or not to move.
3. Save : Tap a button again to save your work, and you're done!
Instructions & Download Link Is On 2nd Post
Screenshots On 3rd Post
Credits
Thanks To macallen For XperiaZ2 FTF
Cheers U Can Post Screenshots Too & I'll Add To This Thread
If U Like My Work Dont Forgot To Press Thanks Button
XDA:DevDB Information
[PORT][CM11] Xperia Z2 Sirius Smart Social Camera, App for the Sony Xperia M
Contributors
xperiaz2
Version Information
Status: Stable
Current Stable Version: Final
Stable Release Date: 2014-04-28
Created 2014-04-28
Last Updated 2014-05-08

Installing Instruction For Any Cm11 Android
1.Download Z2SocialCamera4.zip flash via cwm
2.Download Z2 Camera Addons & Latest AR Effect 3.0.27 Install All apk Normally
3. Run Background Defocus Or Add Widget Camera Choose ur Fav. Camera Addons & Run
Here U Can Download Xperia Z2 Smart Social Camera
https://www.mediafire.com/?2ojpj2tjx853jkz
New Version Here Works On Many Android Phones
https://www.mediafire.com/?kkmapv7682kkkjs
Flash via CWM
Xperia Z2 Camera Addons
http://www.mediafire.com/download/a73e7otni7ap771/Z2CameraAddons.zip
Extract Zip Install All apk Normally
Latest AR Effect 3.0.27 With All Themes Like Spider-Man,Horror etc.
https://www.mediafire.com/?xd1453p1485sedv
AR Effect 2.0.8
https://www.mediafire.com/?8plt36ov6vptyz4
Install apk Normally.. :good:

Screenshots

Good Job Man....!!!!

Wow...youre suprising everyone bro
Thanks for this, I'll try this on my couzins xperia phone :good:
Btw bro, is it possible to port this to other devices running CM11?

totzkitotz said:
Wow...youre suprising everyone bro
Thanks for this, I'll try this on my couzins xperia phone :good:
Btw bro, is it possible to port this to other devices running CM11?
Click to expand...
Click to collapse
Yeah Pleasure Bro yup this works on other devices running cm11 too :good:

xperiaz2 said:
Yeah Pleasure Bro yup this works on other devices running cm11 too :good:
Click to expand...
Click to collapse
wow going to give it a try bro...ill feedback later, because I have an htc here running CM11 thats why Im also asking it..thanks again bro keep it up

cm11 where？

yeeson said:
cm11 where？
Click to expand...
Click to collapse
In the OP sir CM11 kitkat running devices :good:

totzkitotz said:
In the OP sir CM11 kitkat running devices :good:
Click to expand...
Click to collapse
Xperia Z2 cm11 where？

Great Job:good:

Levered said:
Great Job:good:
Click to expand...
Click to collapse
yeah thnx bro :good: Enjoy it

xperiaz2 said:
yeah thnx bro :good: Enjoy it
Click to expand...
Click to collapse
Btw CM11 many bugs....

Great work lokking forward to try this.
Is this works on aosp rom?
I m using carbon rom 4.4
Sent from my C5303 using Tapatalk

This is i want, thanks bro!

wow!! ive awaited this for so loooooooooong. i cannot believe its here!
im downloading now, thank you!! i will bug report soon as i can

Work for Xperia P AOSP 4.4.2? It is novathor and as Z1 camera did not work for novathor, there may be a chance that it may nit work...
Sent my AOSP Xperia P

Force Close!
The camera application force closes in AOSPA 4.2.2 Xperia L.
Hope in future it works!!!

@xperiaz2 Nice job. For xperia P with cm11 i have a force close.Could please add libmmjpeg_interface.so lib to test it ?
dlopen("/system/lib/libimageprocessorjni.so") failed: dlopen failed: could not load library "libcacao_common.so" needed by "libimageprocessorjni.so"; caused by could not load library "libcammw.so" needed by "libcacao_common.so"; caused by could not load library "libmmjpeg_interface.so" needed by "libcammw.so"; caused by library "libmmjpeg_interface.so" not found
Click to expand...
Click to collapse
And here's a part of a logcat:
Code:
E/dalvikvm( 4903):dlopen("/system/lib/libimageprocessorjni.so") failed: dlopen failed: could not load library "libcacao_common.so" needed by "libimageprocessorjni.so"; caused by could not load library "libcammw.so" needed by "libcacao_common.so"; caused by could not load library "libmmjpeg_interface.so" needed by "libcammw.so"; caused by library "libmmjpeg_interface.so" not found
W/dalvikvm( 4903): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Lcom/sonymobile/imageprocessor/superresolution/SuperResolutionProcessor;
I/dalvikvm( 4903): Could not find method android.os.storage.StorageManager$StorageType.name, referenced from method com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.getPathFromConfig
W/dalvikvm( 4903): VFY: unable to resolve virtual method 590: Landroid/os/storage/StorageManager$StorageType;.name ()Ljava/lang/String;
D/dalvikvm( 4903): VFY: replacing opcode 0x6e at 0x0024
I/dalvikvm( 4903): Could not find method android.os.storage.StorageManager.getVolumePath, referenced from method com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.getPathFromType
W/dalvikvm( 4903): VFY: unable to resolve virtual method 592: Landroid/os/storage/StorageManager;.getVolumePath (Landroid/os/storage/StorageManager$StorageType;)Ljava/lang/String;
D/dalvikvm( 4903): VFY: replacing opcode 0x6e at 0x0004
W/dalvikvm( 4903): VFY: unable to resolve static field 82 (UNKNOWN) in Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x62 at 0x0000
W/dalvikvm( 4903): VFY: unable to resolve static field 81 (INTERNAL) in Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x62 at 0x000b
W/dalvikvm( 4903): VFY: unable to resolve static field 80 (EXTERNAL_CARD) in Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x62 at 0x000e
W/dalvikvm( 4903): VFY: unable to resolve static field 80 (EXTERNAL_CARD) in Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x62 at 0x0006
W/dalvikvm( 4903): VFY: unable to resolve static field 81 (INTERNAL) in Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x62 at 0x000c
I/dalvikvm( 4903): Could not find method android.os.storage.StorageManager.getVolumeType, referenced from method com.sonyericsson.cameracommon.settings.SaveDestination.getOptions
W/dalvikvm( 4903): VFY: unable to resolve virtual method 594: Landroid/os/storage/StorageManager;.getVolumeType (Ljava/lang/String;)Landroid/os/storage/StorageManager$StorageType;
D/dalvikvm( 4903): VFY: replacing opcode 0x6e at 0x001e
I/dalvikvm( 4903): DexOpt: unable to optimize static field ref 0x0050 at 0x1b in Lcom/sonyericsson/cameracommon/settings/SaveDestination;.<clinit>
W/dalvikvm( 4903): Exception Ljava/lang/NoClassDefFoundError; thrown while initializing Lcom/sonyericsson/cameracommon/settings/SaveDestination;
W/dalvikvm( 4903): Exception Ljava/lang/NoClassDefFoundError; thrown while initializing Lcom/sonyericsson/cameracommon/mediasaving/CameraStorageManager$1;
D/AndroidRuntime( 4903): Shutting down VM
W/dalvikvm( 4903): threadid=1: thread exiting with uncaught exception (group=0x41916c80)
E/AndroidRuntime( 4903): FATAL EXCEPTION: main
E/AndroidRuntime( 4903): Process: com.sonyericsson.android.camera, PID: 4903
E/AndroidRuntime( 4903): java.lang.NoClassDefFoundError: android.os.storage.StorageManager$StorageType
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.settings.SaveDestination.<clinit>(SaveDestination.java:28)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.mediasaving.CameraStorageManager$1.<clinit>(CameraStorageManager.java:900)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.showOrClearStorageErrorPopup(CameraStorageManager.java:375)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.setLastStorageState(CameraStorageManager.java:344)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.updateStorageState(CameraStorageManager.java:322)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.mediasaving.CameraStorageManager.<init>(CameraStorageManager.java:202)
E/AndroidRuntime( 4903): at com.sonyericsson.cameracommon.activity.BaseActivity.onCreate(BaseActivity.java:250)
E/AndroidRuntime( 4903): at com.sonyericsson.android.camera.ExtendedActivity.onCreate(ExtendedActivity.java:273)
E/AndroidRuntime( 4903): at com.sonyericsson.android.camera.CameraActivity.onCreate(CameraActivity.java:226)
E/AndroidRuntime( 4903): at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime( 4903): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime( 4903): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
E/AndroidRuntime( 4903): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2265)
E/AndroidRuntime( 4903): at android.app.ActivityThread.access$800(ActivityThread.java:145)
E/AndroidRuntime( 4903): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1206)
E/AndroidRuntime( 4903): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4903): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4903): at android.app.ActivityThread.main(ActivityThread.java:5081)
E/AndroidRuntime( 4903): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4903): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 4903): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/AndroidRuntime( 4903): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/AndroidRuntime( 4903): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 2135): Force finishing activity com.sonyericsson.android.camera/.CameraActivity
I/libblt_hw( 1533): Library closed (handle = 8, fd = 54)
I/ActivityManager( 2135): Config changes=480 {1.0 202mcc1mnc en_US ldltr sw360dp w360dp h614dp 240dpi nrml long port finger -keyb/v/h -nav/h s.20 themeResource=null}
D/PhoneStatusBar( 2378): mSettingsPanelGravity = 55
I/InputReader( 2135): Reconfiguring input devices. changes=0x00000004
I/InputReader( 2135): Device reconfigured: id=1, name='sensor00.f11_sensor0', size 540x960, orientation 0, mode 1, display id 0
I/InputReader( 2135): Reconfiguring input devices. changes=0x00000004
I/libblt_hw( 1533): Library opened (handle = 5, fd = 54)
D/Tethering( 2135): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
D/Tethering( 2135): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/WindowManager( 2135): Screen frozen for +860ms due to Window{41f19120 u0 StatusBar}
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!
E/gralloc ( 1533): [User error] handle_2_hwmem_gralloc_handle: Invalid handle
I/libblt_hw( 1533): Library opened (handle = 8, fd = 43)
I/libblt_hw( 1533): Library opened (handle = 10, fd = 53)
I/libblt_hw( 1533): Library opened (handle = 11, fd = 57)
I/libblt_hw( 1533): Library opened (handle = 12, fd = 58)
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!
E/gralloc ( 1533): [User error] handle_2_hwmem_gralloc_handle: Invalid handle
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!
E/gralloc ( 1533): [User error] handle_2_hwmem_gralloc_handle: Invalid handle
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!
E/gralloc ( 1533): [User error] handle_2_hwmem_gralloc_handle: Invalid handle
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!
E/gralloc ( 1533): [User error] handle_2_hwmem_gralloc_handle: Invalid handle
E/STE-HWComposer( 1533): bufferIsHWMEM: Buffer handle is NULL!

I may have been dumb in trying this, but it's not working with my Xperia ZL running Omni 4.4.2. I don't know if I can help much by attaching the log but here goes. Searching for "sonymobile", "sonyericsson" or "camera" may help (?)

[DEV][Thinktank]Porting 4K & Timeshift video from Z2 to other Xperia devices

I've seen dozens of threads about 4K recording and Timeshift video. None of them work. Let's keep all relevant DEVELOPMENT info here. It will be way easier for real developers and other people that could share some useful info or their attempts to get 4K & 120 FPS recording on other device than the Z2.
If you can contribute, please do it here instead of your own threads. Working alone is much harder. Let's work together on this, so we could finally get it to work. That's what XDA is all about.
Please don't spam this thread. I've made it to ACTUALLY get this finally working.
Featured on:
Softpedia
gsmarena
xperiablog.net
androidbeat
nextpowerup
gadgethelpline - no link to this thread
androidheadlines
techshout
sonyxperiaz.co.uk
XDA
Let me know about any others @lagalaga @Riyal - we're getting famous xD
If you want to discuss about it or ask some questions about it then do it here in the link below and keep this thread clean:
http://forum.xda-developers.com/showthread.php?t=2768422

Download it from here
Discuss/talk about it here.
Thanks to me, @lagalaga and @Riyal .

FAQ:
Is this going to work on my xxx?
For now it's only compatible with Z1 and Z1c on 4.4. We're working on fixing all of the bugs and then we'll try to bring it to more devices. Z Ultra will propably be the next device that will get this mod ported as it also boasts S800 chip.
Does it work on CM11?
You tell us, it's really fresh!
How do I install it?
1. Root your phone
2. Make a nandroid backup in a recovery, just in case something goes wrong.
3. Install xposed framework
4. Install Serajr's modulemodule
5. Enable Serjar's module after installing it.
6. Reboot.
7. Flash the latest zip from this post
8. Enjoy!
Why do I need Serajr's "Xperia Xposed (KK)" Module?
Serajr's module contains the so-called "SuperUser mod". Please be aware that this is different from the SuperUser root management app. So, what does this mean?
The .apks contained in this mod have a different signature from the original .apk files. This prevents them from using the extended camera functions added by Sony. Serajr's "Xperia Xposed" mod disables this signature verification. If you do not want to install the Xposed framework or Serajr's module, you can also disable signature verification by patching the services.jar. Please see DavidMKD's instructions here.
I keep getting "Camera not available" errors in 4k or Timeshift Video
You probably do not have SuperUser mod installed properly. If you are using Serajr's Xposed module, you need to make sure that the Xposed framework is installed properly. Just launch the Xposed app, click on the first menu it and make sure app_process and XposedBridge.jar are installed and highlighted in green. If it still does not work, make sure that Serajr's module is in fact activated. Yes, you need to activate a module after downloading it. This also requires a reboot after activating the module.
My camera freezes when I record in 4k
You probably have SteadyShot enabled. This is currently not supported. It's also a good idea to make sure you've flashed the latest version of this mod. The Steadyshot menu item is disabled in the APK, but sometimes the setting is already activated in the app's database. You need to go to app settings and clear data for the following apps (thanks @jasonx20ac):
Cameracommon
Cameras
Camera extensions
Camera
Video
Video is too dark in Timeshift Video/120fps
olokos said:
Try blinking 120 times per second. I bet you won't see anything anything even if you blink 10 times per second.. That's pretty much it with the camera.
Click to expand...
Click to collapse
This is a hardware limitation, nothing we can do.
How do I uninstall your mod
You revert back to the backup you made just before you installed our mod. You did get a nandroid, right?[/QUOTE]
xxx doesn't work, help/other random questions and stuff
Don't post about it in this thread!!!
If you want to discuss about it or ask some questions about it then do it here in the link below and keep this thread clean! :
http://forum.xda-developers.com/showthread.php?t=2768422
What else needs to be done?
For this moment only steadyshot doesn't work on 4k recording.
Let me know if you have any other questions and I'll add them to the FAQ.
Will this work on Z Ultra/Z/T/V etc?
For now we will work on the Steadyshot and Z Ultra. Anything else that is not a sony device and is running older SoC than Snapdragon 800 won't be able to do 4k videos due to hardware limitations. 120fps MIGHT be possible on other devices than the S800 family, but first we'll have to deal with steadyshot or Z Ultra port. For now this is only working for Z1/Z1c.

I did my attempt before just not posting this on xda. I did to the point of even reverse engineering the so files of some of the camera libs to inspect it. One thing I could say is the libraries & the kernel already supports 4k & 120fps recording. The only limit now is the android profile for 4k and 120fps.
This thing requires a mod of the android Camera HAL on the core framework and add support for 4k and 120fps which I am finding it hard to do since I have no advance knowledge with android as a whole. I think anyone with full experience with the whole android source code could help this like for example some of the core developers on cyanogen.
If someone can backtrack this function I think we can port 4k.
http://developer.android.com/refere...mera.Parameters.html#getSupportedVideoSizes()

What's the output of this function on the Z1 and the Z2? We could try with an xposed module for a start.
Wysłane z mojego C6903 przy użyciu Tapatalka

My preliminary results and idea
Hey guys, let's do this!
I'm reposting my previous meagre results from the other thread.
Start with fresh KK 757 ROM
Deodex ROM, install Sejrar Xposed mod for SuperUser
Install @xperiaz2's newSuperVideoCamera.apk
Push the Z2 media_profiles.xml
At this point, timeshift recording _stops_ working with a new error message:
Code:
E/CameraSource( 318): Requested frame rate (120) is not supported: 15,30,45,60
This means, to me, that the FPS setting is rejected further down in the validation chain. Some kind of success.
Things I have tried as well:
Push Z2 camera.msm8974.so, camera.qcom.so - does not really change anything
Push the Z2 libstagefright.so - this results in a boot loop. (Perhaps because the other libs did not match)
Decompile newSuperVideoCamera.apk - there is some validation code in there which reads an XML ressource that comes with the APK. But I don't think the limit is in there. After all, that APK works on the Z2.
My ideas at this point:
libcamera_clientsemc.so
libcamera_client.so
Push the z2 camera firmware? (/system/vendor/camera/)
Deodex ALL the APKs, disassemble ALL the .so files and grep
I'm super short on time. My next step would be looking at where
Code:
E/CameraSource( 318): Requested frame rate (120) is not supported: 15,30,45,60
is coming from. I did find that string in some .so files. I basically wonder if the limitation is somewhere in the main framework or in a supporting camera file, like the EEPROM firmware.
Code:
[email protected]:/mnt/lib$ grep -E -ri "Requested frame rate .* is not supported" *
Binary file libstagefright.so matches
[email protected]:/mnt/lib$ cd ..
[email protected]:/mnt$ grep -E -ri "Requested frame rate .* is not supported" *
Hm, I just looked at the libstagefright source:
Code:
if (frameRate != -1) {
CHECK(frameRate > 0 && frameRate <= 120);
const char* supportedFrameRates =
params->get(CameraParameters::KEY_SUPPORTED_PREVIEW_FRAME_RATES);
CHECK(supportedFrameRates != NULL);
LOGV("Supported frame rates: %s", supportedFrameRates);
char buf[4];
snprintf(buf, 4, "%d", frameRate);
if (strstr(supportedFrameRates, buf) == NULL) {
LOGE("Requested frame rate (%d) is not supported: %s",
frameRate, supportedFrameRates);
return BAD_VALUE;
}
Where is CameraParameters::KEY_SUPPORTED_PREVIEW_FRAME_RATES coming from? Is that even related to the problem at hand? It says _PREVIEW_.
Edit: I'll just leave this here: http://source.android.com/devices/camera/camera.html
---------- Post added at 09:58 AM ---------- Previous post was at 09:08 AM ----------
I took a very quick look at the libs in lib/*cam*.so. I disassembled them using an objdump build for ARM binaries. It seems like all parameter-related calls go elsewhere. I think lib/libcal* might contain the HAL. Or lib/camera/libexcal_halctrl_plugin.so.
---------- Post added at 10:25 AM ---------- Previous post was at 09:58 AM ----------
Instead of blindly disassembling files, I've made a list of cam-related which differ from the Z2 dump.
Differing files are prefixed with +/-.
Code:
[email protected]:~/download/sirius/vendor/lib$ diff -u /tmp/sirius_cam_libs.txt /tmp/z1_cam_libs.txt
--- /tmp/sirius_cam_libs.txt 2014-05-30 10:22:51.376765058 +0200
+++ /tmp/z1_cam_libs.txt 2014-05-30 10:20:54.143544043 +0200
@@ -1,71 +1,73 @@
93a1f926d3a12e9ca4824c956d508a66 libcamera_client.so
b3d3ef1d566b3707f5775e02d4692d52 libcamera_clientsemc.so
-a3edba0d2feef9e2ab9c3f4b91a3dc37 libcamera_metadata.so
+f4e5f060ae74c371e531202ef54100c6 libcamera_metadata.so
72c9d7ba9dbe6b73018545cde8ab372a libcameraextensionclient.so
d586a965ccd6f650cc77780a32dadc8c libcameraextensionjni.so
7a5579b182d8d2e1cd15ac94a30f81bd libcameraextensionservice.so
-494537a6cb1e5fb0035907d5cfcb5c8e libcameralight.so
+9d93128f6bed366f5ac2202862832236 libcameralight.so
27a1b4f36a139a4f83e5d009f4e2e850 libcameraservice.so
-0b75f5df9b40958b0b4974056ac5eee7 libcammw.so
-e4eef4a200f8a9ff29bcd839a878ca3f libgcam.so
-4b7b821ca095e3d8adcab5c75752812f libgcam_swig_jni.so
+0f359b812950510539bf51d59b57ccb8 libcammw.so
+bc03ce47cc6436beaea03e0b32d887a6 libgcam.so
+34e22f61aec410da9fe12ad122497bbf libgcam_swig_jni.so
e93d12f69d96d7d7ad7014ef5fc992e3 libimscamera_jni.so
-63be241b1f1789a4834329b54231312b libmm-qcamera.so
-f13787f130fcb2b9deeaa9c32df18016 libmmcamera_interface.so
-82cdf1807bbc6a598f610c932e0b6c1d libexcal_halctrl_plugin.so
-2a94119126f0b4740f1987a819d06a22 libexcal_idtctrl_plugin.so
-4a8a1430c8eab53f3ef738ca0241fcd3 LGI02BN1.dat
-bd0ef41189e3a35a39ba583a573bd074 LGI02BN1_CACAO.dat
-d871adc83bde1828d0b02f55f991be15 LGI02BN1_IMX132.dat
-3e49122f24e2b7a6e3d613959e288823 SEM02BN1.dat
-bd0ef41189e3a35a39ba583a573bd074 SEM02BN1_CACAO.dat
-d871adc83bde1828d0b02f55f991be15 SEM02BN1_IMX132.dat
-decd21e51fda98dd083a8928dbd47813 SOI20BS0.dat
+3775b2b51b778f99e42dc34784cf4a72 libmm-qcamera.so
+d5b1cba2549b64054de57b3a17c15196 libmmcamera_interface.so
+b6237e563273dc166c5024b74de281ac libexcal_halctrl_plugin.so
+841c2be632d27950545e5c0945cb15f8 libexcal_idtctrl_plugin.so
+db5dd107ac9d44984d10f03a33711f8b LGI02BN1.dat
+05a9e3971bc288c831644f69356493c4 LGI02BN1_CACAO.dat
+9dbee89f32e5d34e6660208d9fc4680c LGI02BN1_IMX132.dat
+d87835b026f535098358fa0a3699eaff SEM02BN1.dat
+05a9e3971bc288c831644f69356493c4 SEM02BN1_CACAO.dat
+9dbee89f32e5d34e6660208d9fc4680c SEM02BN1_IMX132.dat
+a8d0735567ba3b04175b0ecd864c85c1 SOI13BS9.dat
+0adf6448947587eda7b92649ebbbac61 SOI13BS9_CACAO.dat
+efbb4d4ce6312999362f78b5d1ab282c SOI20BS0.dat
ec390331a2fefa7db5930358da5b96e9 SOI20BS0_BU64296GWX.dat
-1421ff0f451398c3e585405a9ea1a10b SOI20BS0_CACAO.dat
-4e61468ac674fcb1020e2715dc8dec6b SOI20BS0_IMX200.dat
+519c86ac9bbbf99d7ad418bf82d82af3 SOI20BS0_CACAO.dat
+e4d94011669e4c47bb88f65e4dcea02c SOI20BS0_IMX200.dat
929c9f0b96f577e51edbcab9f1922e3e flash.dat
-13a874cc2898fb3fd9b254834a0f0433 product.dat
+ee8a3c0ef00c8f6c8a9458a5d4fc06c6 product.dat
e9bd05f4403d30c2512abb517168ee63 product_CACAO.dat
-ef22da65ed1cd0e6fa89ec2c89ae6fc8 lib-imscamera.so
-39137471837272672a0ff48ffee5b4be libmmcamera2_c2d_module.so
-3c37dc9eec1790c03605abf6ac3983ee libmmcamera2_cpp_module.so
-1196676d59f606e1c458864808d8d1c3 libmmcamera2_iface_modules.so
-eef8fbe9f58afed5add9500ab533485c libmmcamera2_imglib_modules.so
-63c3981f5217c6e119e7574af08acbf2 libmmcamera2_isp_modules.so
-bbdf76cb4c21655060013c67569b8151 libmmcamera2_pproc_modules.so
-2570d502c5e6bf29125853f704bb8ad5 libmmcamera2_sensor_modules.so
-43d17188bad9a05b60adf30e4c193719 libmmcamera2_stats_algorithm.so
-f78b5538003b3bd79705ca8a935d1112 libmmcamera2_stats_modules.so
-fef566ec52a6308f170db11f23dd188e libmmcamera2_vpe_module.so
+9f29f495df282a671b6c163be6cdb30d lib-imscamera.so
+a1a4cb8ce8577d2b6333894e081d8c65 libmmcamera2_c2d_module.so
+75c8ffb6fd8bad34adf5f5eb40f1e02a libmmcamera2_cpp_module.so
+363f6d193977c4d10d4c7cfc401d7108 libmmcamera2_iface_modules.so
+d4fe52fce08bfea259f47677fd909681 libmmcamera2_imglib_modules.so
+8be561df7588929d21eb10fd6391dcd8 libmmcamera2_isp_modules.so
+23857108a8de8cc45c6b7c029f7336a4 libmmcamera2_pproc_modules.so
+3f0f59d3ab545bd64b273fa30cc6bd1d libmmcamera2_sensor_modules.so
+e026ad2af46ef786e431fae5852dbf4d libmmcamera2_stats_algorithm.so
+a7aba420d1e21208c90feff869811caa libmmcamera2_stats_modules.so
+c059bd13cb4692d24efa60286b52a29f libmmcamera2_vpe_module.so
f7767985d442ba1dc3da4c9172f44b6f libmmcamera2_wnr_module.so
98a7907d524c953f3b666feb3407083c libmmcamera_faceproc.so
-fc8d85b36cbd033956681bff04a06aab libmmcamera_hdr_gb_lib.so
-85354bcc6210e2d9b4fb17631a995a95 libmmcamera_hdr_lib.so
-5823693674a58cc40eb561bc4e437086 libmmcamera_imglib.so
-3bdb7b22a3a4171d4fac9a74afb512af libmmcamera_ofilm_oty5f03_eeprom.so
-0e8922a3d08b237860ac02457f6f0bbd libmmcamera_sunny_p12v01m_eeprom.so
-1a3e919c181d002588be5a4f6a31bdf6 libmmcamera_sunny_p5v23c_eeprom.so
-db462f6d784d37f37aa15331059081af libmmcamera_sunny_q8v18a_eeprom.so
-868fb153dac744402900638af861429b libmmcamera_tintless_algo.so
-f4faadbd97ecb6117a5e84113ad6b05c libmmcamera_tintless_bg_pca_algo.so
-12a182ff996d13144a24fcd7f30dbdea libmmcamera_truly_cm7700_eeprom.so
-b6f78a47d7c5725b8386ed3b034b7a40 libmmcamera_tuning.so
-ec2d3de7882441c12a740053a0bb4a0f libmmcamera_wavelet_lib.so
-939f75ffb07bc2b04baa067ffd4aca7c liboemcamera.so
+8b91580908c8bbba9ca7a32ac0f64b6d libmmcamera_hdr_gb_lib.so
+8a4b3584449021844c734dbdd4ffbcce libmmcamera_hdr_lib.so
+41ecfa8bd5f328f9bd37b77fb6c61966 libmmcamera_imglib.so
+2d1061d71161491820ee66dd66b3288b libmmcamera_ofilm_oty5f03_eeprom.so
+c6d923dcfb40e5dbf93122111754b96b libmmcamera_sunny_p12v01m_eeprom.so
+dedd91532de2977c00491acc984f1df4 libmmcamera_sunny_p5v23c_eeprom.so
+53f614eb8ad32fa4d92c18e0fd98c19e libmmcamera_sunny_q8v18a_eeprom.so
+a879624ba28c110018e2ae8205f0497f libmmcamera_tintless_algo.so
+d483a68b03749eb13132aab0154e8690 libmmcamera_tintless_bg_pca_algo.so
+0a178ce9b50ab4e6c053a8e5cdc97f7e libmmcamera_truly_cm7700_eeprom.so
+f8cbd2dd4f0e077e6e89e01a1a5cd3d0 libmmcamera_tuning.so
+3e982409dc91f11bb5b4b114bb582e6c libmmcamera_wavelet_lib.so
+27867ab76d31a46729646e31344777e0 liboemcamera.so
53bd825ac673f39f5cfbac5a82694104 libchromatix_SKUAA_ST_gc0339_common.so
91fe5ec1d3f13b7578aebaeb87afa401 libchromatix_SKUAA_ST_gc0339_default_video.so
b24bf7fa8d3a7e8e65c4edea6a355845 libchromatix_SKUAA_ST_gc0339_preview.so
ec30ed4fc7279b148a910e29b453794b libchromatix_SKUAB_ST_s5k4e1_common.so
-f8e399fa4afc64eb884e3fdb4ab7813c libchromatix_SKUAB_ST_s5k4e1_default_video.so
-7a6d551c28832a0a457e0514e199bcfd libchromatix_SKUAB_ST_s5k4e1_hfr_120fps.so
-706ac5e46c06e0d523d1febfbd10cb22 libchromatix_SKUAB_ST_s5k4e1_hfr_60fps.so
-2b51ad44d62c26b8ff095f303af7dd71 libchromatix_SKUAB_ST_s5k4e1_hfr_90fps.so
-ff7d89fc55788a71ce43077e8a9ff647 libchromatix_SKUAB_ST_s5k4e1_liveshot.so
-980ce2a3181e5b502aaa339504148ad8 libchromatix_SKUAB_ST_s5k4e1_preview.so
-86c6ddcc6b8342001d2cfd8c2ec36b9b libchromatix_SKUAB_ST_s5k4e1_snapshot.so
-b7304ae1e3719dde6f4268b44d55c8cc libchromatix_SKUAB_ST_s5k4e1_video_hd.so
-09d5bbc80c14aa638007a174debdf60e libchromatix_SKUAB_ST_s5k4e1_zsl.so
+ab5c972a78c23ae116e9e779b87cbfd4 libchromatix_SKUAB_ST_s5k4e1_default_video.so
+b50b1bb5dc89682197271b4b2a38789f libchromatix_SKUAB_ST_s5k4e1_hfr_120fps.so
+59e4adc79ce7256b2209338230adf674 libchromatix_SKUAB_ST_s5k4e1_hfr_60fps.so
+436a828d36be2b06802110f73ad11eb4 libchromatix_SKUAB_ST_s5k4e1_hfr_90fps.so
+eb4a412e1e082242fa58e3e081b4c2fa libchromatix_SKUAB_ST_s5k4e1_liveshot.so
+500e12147dbab0efee22b437d3c814d1 libchromatix_SKUAB_ST_s5k4e1_preview.so
+523e4950ac1001d24a3367019a5b7fbf libchromatix_SKUAB_ST_s5k4e1_snapshot.so
+1ded59af8a39029052cd43240a831bb6 libchromatix_SKUAB_ST_s5k4e1_video_hd.so
+86d5a8c26730acb26ce157c351164848 libchromatix_SKUAB_ST_s5k4e1_zsl.so
30e4c8c92ca754fe9b3319fe3bf45cbc libchromatix_imx134_common.so
f4199401d6aa464df711f34d244dac2d libchromatix_imx134_default_video.so
2217b32c548fa7fe8c260e4455c4eaca libchromatix_imx134_hfr_120.so
@@ -73,24 +75,24 @@
06c848b52fcf7ab79dee52d62f6b9902 libchromatix_imx134_preview.so
2dd3f4ef1cbd4bde61690c62b7d551d4 libchromatix_imx134_snapshot.so
e340858bd283c2e5ebe753b20af4e135 libchromatix_imx135_common.so
-78baf0e548af301dab5ddfb62b0a5d87 libchromatix_imx135_default_video.so
+557c15cf742559c36d9adfa7d81c866d libchromatix_imx135_default_video.so
37e794554421d3ec27937df96cbd0a7c libchromatix_imx135_hfr_120.so
7202126d9c6ecae036ece26bfdb3dd55 libchromatix_imx135_hfr_60.so
aadad7e9723cf58cebc766fc9a989238 libchromatix_imx135_hfr_90.so
-485983c388f87bf55e1e81e82862b9bc libchromatix_imx135_preview.so
-298fdecf75d9d893cea8639fe1657055 libchromatix_imx135_snapshot.so
-a43d4e752ffbb02a2404099f1f29d7b8 libchromatix_imx135_video_hd.so
+8e261788956847653294aaaffd3e33de libchromatix_imx135_preview.so
+e6a45db75fd4b82ebdb3bb79ec3f19f6 libchromatix_imx135_snapshot.so
+73e9af28f258c93e9dbafa8f7a8af90a libchromatix_imx135_video_hd.so
eb15537549887f222df684c4cc9546e6 libchromatix_ov2720_common.so
e109a1a032788624205442b51a40ccf6 libchromatix_ov2720_default_video.so
79ae6e084a11ef919147c7803c716451 libchromatix_ov2720_hfr.so
154ae2090b2251393843aeb0895f1151 libchromatix_ov2720_liveshot.so
88676a68918ccf651a49c3144c73fdd7 libchromatix_ov2720_preview.so
3a3488e0beb32c6cf3966ba52aece6d3 libchromatix_ov2720_zsl.so
-bfa6d04363964b68da5d88ed962bc56f libchromatix_ov5648_oty5f03_common.so
-9e7aec4feee9c249588ba229f2264f3e libchromatix_ov5648_oty5f03_default_video.so
-b65a1e3f9be559c1971fd57610dfffd1 libchromatix_ov5648_oty5f03_preview.so
-3562ce083f12b84a17e737991d15b09a libchromatix_ov5648_oty5f03_snapshot.so
-fbead760a33e399d7f6344b477b3e2cc libchromatix_ov5648_oty5f03_zsl.so
+4cd474f4272dde42c312e20e543ba57e libchromatix_ov5648_oty5f03_common.so
+a3b1785b37a3c73bb9e8aafe82eb1b55 libchromatix_ov5648_oty5f03_default_video.so
+e4bff3685e2d3baa589bfb3c2e04ccf8 libchromatix_ov5648_oty5f03_preview.so
+fcbe6ae1c33590d34f975b7be6af0f4c libchromatix_ov5648_oty5f03_snapshot.so
+ccde332fe3e14d1c1d180c8c98fbf9c7 libchromatix_ov5648_oty5f03_zsl.so
0a5edc031cfbb47bb6b1125545bb5617 libchromatix_ov8825_common.so
f6439e6909141a189ad34d38294420fd libchromatix_ov8825_default_video.so
53d7376f9f1b5c774de57991c8832942 libchromatix_ov8825_hfr_120fps.so
@@ -107,8 +109,8 @@
b513f118deb40d2d2dcc72ca304fa3e7 libchromatix_ov8865_q8v18a_common.so
498ee582bbca041ca6f1d1e0d12b024e libchromatix_ov8865_q8v18a_default_video.so
dd75ef2335ae5a7cfb933d3e4ca7972b libchromatix_ov8865_q8v18a_hfr_120fps.so
-fbe827e6411845a40b1103cf9beba4aa libchromatix_ov8865_q8v18a_hfr_60fps.so
-a74ebec872caaf1ea9e1dd5f5157a442 libchromatix_ov8865_q8v18a_hfr_90fps.so
+905d11aa09200de08da7e4bd8a72f097 libchromatix_ov8865_q8v18a_hfr_60fps.so
+16c2afb0ba3a14389454eab3e23090fd libchromatix_ov8865_q8v18a_hfr_90fps.so
eab4ee1f0fa18b292c15ccee1ea91a10 libchromatix_ov8865_q8v18a_liveshot.so
c37ba33169dc6519f10aff55be157721 libchromatix_ov8865_q8v18a_preview.so
17df16cea2081afa29dddb2efa657bb2 libchromatix_ov8865_q8v18a_snapshot.so
---------- Post added at 11:00 AM ---------- Previous post was at 10:25 AM ----------
I decided lib-imscamera.so looked promising. I dumped the assembly with
Code:
arm-none-eabi-objdump -g -t -T -x -D -S -s lib-imscamera.so
and diff'ed the files. Nothing spectacular. I guess I should try to diff the assembly for all relevant files.

My bet would be those files:
Code:
-4a8a1430c8eab53f3ef738ca0241fcd3 LGI02BN1.dat -bd0ef41189e3a35a39ba583a573bd074 LGI02BN1_CACAO.dat -d871adc83bde1828d0b02f55f991be15 LGI02BN1_IMX132.dat -3e49122f24e2b7a6e3d613959e288823 SEM02BN1.dat -bd0ef41189e3a35a39ba583a573bd074 SEM02BN1_CACAO.dat -d871adc83bde1828d0b02f55f991be15 SEM02BN1_IMX132.dat -decd21e51fda98dd083a8928dbd47813 SOI20BS0.dat
I think that's the firmware for the camera which is used on the Z2 and the Z1. The thing is - which one is for the Z2 and which one is for the Z1 and how do we actually use it?...
Somebody should really try flashing the Z2 rom. I actually think that I might try that myself. I'll propably end up in a bootloop, but whatever.

olokos said:
My bet would be those files:
Code:
-4a8a1430c8eab53f3ef738ca0241fcd3 LGI02BN1.dat -bd0ef41189e3a35a39ba583a573bd074 LGI02BN1_CACAO.dat -d871adc83bde1828d0b02f55f991be15 LGI02BN1_IMX132.dat -3e49122f24e2b7a6e3d613959e288823 SEM02BN1.dat -bd0ef41189e3a35a39ba583a573bd074 SEM02BN1_CACAO.dat -d871adc83bde1828d0b02f55f991be15 SEM02BN1_IMX132.dat -decd21e51fda98dd083a8928dbd47813 SOI20BS0.dat
I think that's the firmware for the camera which is used on the Z2 and the Z1. The thing is - which one is for the Z2 and which one is for the Z1 and how do we actually use it?...
Somebody should really try flashing the Z2 rom. I actually think that I might try that myself. I'll propably end up in a bootloop, but whatever.
Click to expand...
Click to collapse
I've PM'd you those files. I'm not sure if anything is gained by flashing the Z2 firmware. Either you will end up in a bootloop or you will end up with a working camera without knowing which files/changes in the Z2 rom were responsible

lagalaga said:
I've PM'd you those files. I'm not sure if anything is gained by flashing the Z2 firmware. Either you will end up in a bootloop or you will end up with a working camera without knowing which files/changes in the Z2 rom were responsible
Click to expand...
Click to collapse
I've flashed the .DAT files myself (the camera firmware). Now mediaserver crashes. The backtrace however gives us a nice insight how the stack is built:
Code:
I/DEBUG ( 326): #03 pc 0000dd07 /system/lib/libc.so (calloc+10)
I/DEBUG ( 326): #04 pc 0000815f /system/lib/libcald_pal.so (PAL_MemAllocEx+14)
I/DEBUG ( 326): #05 pc 00017759 /system/lib/libcald_hal.so
I/DEBUG ( 326): #06 pc 00019a47 /system/lib/libcald_hal.so
I/DEBUG ( 326): #07 pc 00009419 /system/lib/libcald_hal.so
I/DEBUG ( 326): #08 pc 00038fdf /system/lib/libcald_server.so
I/DEBUG ( 326): #09 pc 0003c731 /system/lib/libcald_server.so (Cald_CamCtrl_Create+88)
I/DEBUG ( 326): #10 pc 0003081d /system/lib/libcald_server.so
I/DEBUG ( 326): #11 pc 00002285 /system/lib/libcald_client.so (Cald_Client_Create+12)
I/DEBUG ( 326): #12 pc 000129e7 /system/lib/hw/camera.qcom.so (android::SemcCameraHardware::startCamera()+6)
I/DEBUG ( 326): #13 pc 00012d8f /system/lib/hw/camera.qcom.so (android::SemcCameraHardware::createInstance(int, bool)+214)
I/DEBUG ( 326): #14 pc 00012f27 /system/lib/hw/camera.qcom.so (HAL_openCameraHardware+74)
I/DEBUG ( 326): #15 pc 00008fff /system/lib/hw/camera.qcom.so
I/DEBUG ( 326): #16 pc 00044c91 /system/lib/libcameraservice.so (android::CameraClient::initialize(camera_module*)+180)
I/DEBUG ( 326): #17 pc 0003e58f /system/lib/libcameraservice.so (android::CameraService::connectFinishUnsafe(android::sp<android::CameraService::BasicClient> const&, android::sp<android::IBinder> const&)+16)
I/DEBUG ( 326): #18 pc 00040333 /system/lib/libcameraservice.so (android::CameraService::connect(android::sp<android::ICameraClient> const&, int, android::String16 const&, int, android::sp<android::ICamera>&)+494)
I/DEBUG ( 326): #19 pc 00021943 /system/lib/libcamera_client.so (android::BnCameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+314)
I/DEBUG ( 326): #20 pc 0003e0ad /system/lib/libcameraservice.so (android::CameraService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+104)
----
Edit:
I decided to copy the following (with the camera firmware in place):
libcald_hal.so
libcald_pal.so
libcald_server.so
libcald_util.so
libexcal_system.so
Didn't work, camera apps crash with a different backtrace than the one above:
Code:
W/dalvikvm( 4903): Exception Ljava/lang/NullPointerException; thrown while initializing Lcom/sonymobile/android/addoncamera/supervideo/paramet
ers/VideoSize;
W/dalvikvm( 4903): Exception Ljava/lang/ExceptionInInitializerError; thrown while initializing Lcom/sonymobile/android/addoncamera/supervideo/
parameters/CapturingMode;
D/dalvikvm( 4903): Method.invoke() on bad class Lcom/sonymobile/android/addoncamera/supervideo/parameters/CapturingMode; failed
D/AndroidRuntime( 4903): Shutting down VM
W/dalvikvm( 4903): threadid=1: thread exiting with uncaught exception (group=0x4161dd88)
E/AndroidRuntime( 4903): FATAL EXCEPTION: main
E/AndroidRuntime( 4903): Process: com.sonymobile.android.addoncamera.supervideo, PID: 4903
E/AndroidRuntime( 4903): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 4903): at com.sonymobile.android.addoncamera.supervideo.parameters.CapturingMode.<clinit>(CapturingMode.java:22)
E/AndroidRuntime( 4903): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4903): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 4903): at java.lang.Enum$1.create(Enum.java:43)
E/AndroidRuntime( 4903): at java.lang.Enum$1.create(Enum.java:35)
E/AndroidRuntime( 4903): at libcore.util.BasicLruCache.get(BasicLruCache.java:54)
E/AndroidRuntime( 4903): at java.lang.Enum.getSharedConstants(Enum.java:209)
E/AndroidRuntime( 4903): at java.util.EnumMap.initialization(EnumMap.java:758)
E/AndroidRuntime( 4903): at java.util.EnumMap.<init>(EnumMap.java:404)
E/AndroidRuntime( 4903): at com.sonymobile.android.addoncamera.supervideo.parameters.ParamManager.<init>(ParamManager.java:36)
E/AndroidRuntime( 4903): at com.sonymobile.android.addoncamera.supervideo.SuperVideoActivity.setupCoreInstance(SuperVideoActivity.java:199)
E/AndroidRuntime( 4903): at com.sonymobile.android.addoncamera.supervideo.SuperVideoActivity.setUpAll(SuperVideoActivity.java:150)
E/AndroidRuntime( 4903): at com.sonymobile.android.addoncamera.supervideo.SuperVideoActivity.onCreate(SuperVideoActivity.java:144)
------
edit deleted

There's also something else missing... :-\
Could you also post this mediaserver log? Maybe that will tell us more. Do you even get the feel of 120 fps before pressing the record button or are you stuck on launching?
Wysłane z mojego C6903 przy użyciu Tapatalka

olokos said:
There's also something else missing... :-\
Could you also post this mediaserver log? Maybe that will tell us more. Do you even get the feel of 120 fps before pressing the record button or are you stuck on launching?
Click to expand...
Click to collapse
The first backtrace I posted is from mediaserver, I believe. The camera stuff lives inside.mediaserver so they both hoedown.
I have been.looking at framework.jar
I believe Sony has added some Strings in the Camera classes related.to Her support
The strings are both in Z1 and Z2. So it is probably not the framework. I can see.that it all comes down to Camera.getParameters
I am going to look at the Camera documentation link above some more to find.out where these are coming.from. Perhaps we can indeed use Xposed.
Preview does not look like 120fps to me
This is with the Z2 media_profile, no other mods.

Is it possible to get 120 or 60 fps working on XZ? I know it doesnt have S800 like Z1, but I've heard there are also some S4 devuces thar can record in slo-mo
Sent from my C6603 using Tapatalk

speedy56 said:
Is it possible to get 120 or 60 fps working on XZ? I know it doesnt have S800 like Z1, but I've heard there are also some S4 devuces thar can record in slo-mo
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It's not yet working on the Z1 so I can't tell you anything. It might not work on Z1 at all. Please post your questions HERE

Random fun facts:
Z2 SemcPowerSaveModule can apparently limit camera FPS to save power/cope with thermal stress. No such thing in Z1
data/com.sonymobile.cameracommon/databases/camera_status.db stores the camera status, but I believe that is more of a cache and not the camera configuration. The corresponding class is CameraCommon/smali/com/sonymobile/cameracommon/provider/CameraStatusProvider.
Code:
...> ;
1|power_off|0|0x0|0x0|0x0|0|0|off|off|off|off|off|off|off|off|off
sqlite> .dump
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE android_metadata (locale TEXT);
INSERT INTO "android_metadata" VALUES('de_DE');
CREATE TABLE status (_id INTEGER PRIMARY KEY AUTOINCREMENT, device_status TEXT, camera_id INTEGER, preview_resolution TEXT, picture_resolution TEXT, video_resolution TEXT, preview_max_fps INTEGER, video_recording_fps INTEGER, burst_shooting TEXT, time_shift TEXT, art_filter TEXT, face_identification TEXT, face_detection TEXT, scene_recognition TEXT, object_tracking TEXT, video_stabilizer TEXT, photo_light TEXT);
INSERT INTO "status" VALUES(1,'power_off',0,'0x0','0x0','0x0',0,0,'off','off','off','off','off','off','off','off','off');
DELETE FROM sqlite_sequence;
INSERT INTO "sqlite_sequence" VALUES('status',1);
COMMIT;
sqlite> select video_recording_fps from status;
0
I decompiled the Z2 apks (all of them) and found nothing interesting. Might just be me.
I looked at some of the .so files again - it would be interesting to have some kind of dependency graph.
Some random strings and greps:
Code:
[email protected]:/mnt/vendor/lib$ grep -ri q-fps-range-values *
Binary file lib-imscamera.so matches
[email protected]:/mnt/vendor/lib$ grep -ri preview-fps-range
Binary file lib-imscamera.so matches
strings mm-qcamera-app | grep -i -E '(hfr|fps|frame|rate|high)'
libcammw
[email protected]:~/download/sirius$ arm-none-eabi-readelf -a -D ./lib/libcammw.so | grep NEED
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
0x00000001 (NEEDED) Shared library: [libcutils.so]
0x00000001 (NEEDED) Shared library: [libmmcamera_interface.so]
0x00000001 (NEEDED) Shared library: [libmmjpeg_interface.so]
./lib/libmmcamera_interface.so
doer
libcammw.so
cammw_sensor_get_caps
imx200_get_sensor_param
00009240 T cammw_camera_get_caps
0000b74c T cammw_camera_get_config
0000a8a8 T cammw_camera_get_port_info
cammw_get_info+0xd94
mm_camera_query_capability+0x54

I have a feeling that the magic is in libcammw.so. Replacing it leads to crashes related to liboemcamera.so and libmmcamera2_isp_modules.so.
In the log, I see this
Code:
06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: FILE data_size too large (41152)
06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: ERROR! param_version=0 != 263
06-01 08:52:51.084 10074 10135 E somc-camera-driver: SOCAM_ERR: sony_read_parameterfile: sony_read_parameterfile: cannnot a
Replacing the camera firmware again: no luck. Replacing the related libs: no luck.
In fact, even after removing the modifications, camera won't open anymore. I have to restore the system partition. Weird. So my last trial, replacing liboemcamera.so and libmmcamera2_isp_modules.so might have been irrelevant as the eeprom could have been messed up. Perhaps the camera needs to be powered down longer for that to unstick, but that's just a hypothesis.
Next step: attach a debugger to system/bin/mm-qcamera-daemon - that's where libcammw.so is used.
Next step after that: replace _all_ the *camera*so and *cal*so.

The GDB build in my NDK6 can't handle the shared object implementation on android. It does not see the libcammw.so.so stuff when attached to the camera daemon. I can't even continue the camera daemon after attaching. This is bull***.

Guys I was wandering if this helps you at all? As this says 120fps
Sent from my C6903 using XDA Premium 4 mobile app

adam20115 said:
Guys I was wandering if this helps you at all? As this says 120fps
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check the mediainfo of that file. I bet it's not 120fps if that's from using existing mods. If you can get that overlay or you know at least how to got that overlay just like in the previous mods, then let us know. @xperiaz2 @krabappel2548
If any of you wonder what would happen if you flash just the Z2 rom without kernel on the Z1,then it's a bootloop.
Wysłane z mojego C6903 przy użyciu Tapatalka

Guys try checking out camera.msm8794.so & camera.qcom.so. Also have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=2548974
It's from a LG G2 thread. They manage to port 4k & 120fps. The exact patch that implemented the feature was v2.0.6 link here. http://d-h.st/QhP

Riyal said:
http://forum.xda-developers.com/showthread.php?t=2548974
It's from a LG G2 thread. They manage to port 4k & 120fps. The exact patch that implemented the feature was v2.0.6 link here. http://d-h.st/QhP
Click to expand...
Click to collapse
Won't help, unfortunately. Something deeper in the system does not support 120fps.
Stuff I did today:
I looked at the available implementation of a QCOM camera HAL somewhere in the Android source code: https://android.googlesource.com/platform/hardware/qcom/camera
I traced the methods to obtain the available frame rates.
Code:
// Set HFR
String8 hfrValues = createHfrValuesString(
m_pCapability->hfr_tbl,
m_pCapability->hfr_tbl_cnt,
HFR_MODES_MAP,
sizeof(HFR_MODES_MAP) / sizeof(QCameraMap));
In that implementation, the frame rates are queried over the V4L interface directly from the kernel. The camera HAL defines a query_capability method pointer which calls mm_camera_intf_query_capability. This in turn calls mm_camera_query_capability.
Code:
int32_t mm_camera_query_capability(mm_camera_obj_t *my_obj)
{
int32_t rc = 0;
struct v4l2_capability cap;
/* get camera capabilities */
memset(&cap, 0, sizeof(cap));
rc = ioctl(my_obj->ctrl_fd, VIDIOC_QUERYCAP, &cap);
if (rc != 0) {
CDBG_ERROR("%s: cannot get camera capabilities, rc = %d\n", __func__, rc);
}
pthread_mutex_unlock(&my_obj->cam_lock);
return rc;
}
I don't know if the code works the same on the Z1, but libmmcamera_interface.so has the same method names. The HAL is in libmmcamera_interface.so, btw, and you can just call query_capability. See the code for mm-qcamera-app:
Code:
my_cam_app->hal_lib.ptr = dlopen("libmmcamera_interface.so", RTLD_NOW);
test_obj->cam = cam_app->hal_lib.mm_camera_open(cam_id);
rc = test_obj->cam->ops->query_capability(test_obj->cam->camera_handle);
if (rc != MM_CAMERA_OK) {
CDBG_ERROR("%s: failed query_capability", __func__);
rc = -MM_CAMERA_E_GENERAL;
goto error_after_getparm_buf_map;
}
So, of course, I decided to look at the kernel. I diff'ed doomlords Z1 and Z2 kernels and there is no relevant difference in drivers/media/platform/msm.
So, relevant code in the HAL is in QCamera2HardwareInterface::initCapabilities, which obtains a cam_capability_t struct. The struct contains:
Code:
uint8_t fps_ranges_tbl_cnt; /* fps ranges table size */
cam_fps_range_t fps_ranges_tbl[MAX_SIZES_CNT]; /* fps ranges table */
uint8_t hfr_tbl_cnt; /* table size for HFR */
cam_hfr_info_t hfr_tbl[CAM_HFR_MODE_MAX]; /* HFR table */
This is the kernel-side code that handles the IOCTL:
Code:
static int camera_v4l2_querycap(struct file *filep, void *fh,
struct v4l2_capability *cap)
{
int rc;
struct v4l2_event event;
/* can use cap->driver to make differentiation */
camera_pack_event(filep, MSM_CAMERA_GET_PARM,
MSM_CAMERA_PRIV_QUERY_CAP, -1, &event);
rc = msm_post_event(&event, MSM_POST_EVT_TIMEOUT);
if (rc < 0)
return rc;
rc = camera_check_event_status(&event);
return rc;
}
The code for msm_post_event looks like it talks to an 'imaging server' in userspace.

[Q] Warning and errors in logcat with HOB7/i9505

Hi!
My logcat is full of lines like the following:
Code:
04-03 11:38:09.692 W/SurfaceFlinger(280): Fail to Open /sys/devices/platform/gpusysfs/fps
04-03 11:38:09.702 E/SMD (19000): smd Interface open failed errno is 2 -1
04-03 11:38:10.442 E/Diag_Lib(20120): Diag_LSM_Init: Failed to open handle to diag driver, error = 2
04-03 11:38:10.452 E/auditd (2317): In denial and Property audit_ondenial is set to 1
04-03 11:38:10.452 W/ContextImpl(873): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1699 com.android.server.SEDenialService$AuditFileObserver.onEvent:76 android.os.FileObserver$ObserverThread.onEvent:122 android.os.FileObserver$ObserverThread.observe:-2 android.os.FileObserver$ObserverThread.run:85
These are being generated continuously, all the time.
Any idea what those might be?
Thank you!

Hi. I'm getting the same on XXUOBH7 5.0.2

No idea what they are, but if your S4 is working properly they aren't something you should be worrying about. Enjoy your phone.

I have these aswell, and the device seems to have poor battery life and poor performance!

OB7 what....?
Problems with custom built ROM belong in respective thread.
Seems like this one is a double post (which is not really appreciated by XDA )
http://forum.xda-developers.com/showthread.php?p=59864728
It's always a good start to be as specific as possible whether it's ROM, kernel or modem OB7 to narrow down the issue.

Help Getting cameras to work on LG L Fino CyanogenMod 12.1 (Qualcomm MSM8610)

Hello,
I am trying to port CM 12.1 to LG L Fino (d290n/d295). Currently, almost everything is working, but getting the cameras to work seems to be the biggest issue. The phone has the HI841 sensor for the rear camera and the HI707 sensor for the front camera. I have put the stock camera drivers on the kernel and , from the kernel messages, it is shown that both the cameras are picked up and initialized correctly during boot.
Code:
<6>[ 1.389166] i2c /dev entries driver
<7>[ 1.391789] msm_vidc: 1: Failed to read qcom,load-freq-tbl from device tree
<7>[ 1.391825] msm_vidc: 1: no elements in frequency table
<7>[ 1.391855] msm_vidc: 1: Failed to read qcom,reg-presets from device tree
<7>[ 1.391985] msm_vidc: 1: Failed to read qcom,buffer-type-tz-usage-table from device tree
<7>[ 1.392037] msm_vidc: 1: Q6 hfi device probe called
<6>[ 1.404394] msm_actuator_i2c_probe:1061 msm_actuator_i2c_probe: succeeded
<6>[ 1.404558] msm_actuator_i2c_probe:1061 msm_actuator_i2c_probe: succeeded
<3>[ 1.406453] rt8542_probe: id is NULL
<3>[ 1.406527] msm_led_get_dt_data:559 called
<3>[ 1.406665] msm_led_get_dt_data:589 subdev id 0
<3>[ 1.406797] msm_led_get_dt_data:594 msm_led_get_dt_data qcom,flash-name rt8542, rc 0
<3>[ 1.406944] msm_led_get_dt_data:658 msm_led_get_dt_data gpio count 1
<3>[ 1.407024] msm_led_get_dt_data:671 msm_led_get_dt_data gpio_array[0] = 18
<3>[ 1.407165] msm_flash_init_gpio_pin_tbl:521 msm_flash_init_gpio_pin_tbl qcom,gpio-flash-en 18
<3>[ 1.407299] msm_led_i2c_flash_create_v4lsubdev:98 Enter
<3>[ 1.407445] msm_led_i2c_flash_create_v4lsubdev:118 probe success
<3>[ 1.407533] msm_flash_i2c_probe:837 msm_flash_i2c_probe:837 probe success
<3>[ 1.408048] msm_eeprom_alloc_memory_map: pageen not needed
<3>[ 1.408187] msm_camera_request_gpio_table:551 invalid gpio_tbl (null) / size 0
<3>[ 1.624680] msm_camera_request_gpio_table:551 invalid gpio_tbl (null) / size 0
<6>[ 1.625549] imx219_init_module:333
<4>[ 1.625796] imx219_init_module: Sensor power is set as Rev.6(Line:362)
<3>[ 1.627536] imx219_init_module:378 rc -19
<3>[ 1.627901] msm_sensor_get_dt_data qcom,product-kor 0, rc -22
<3>[ 1.640157] qup_i2c f9928000.i2c: QUP: I2C status flags :0x1363c8, irq:132
<3>[ 1.640462] qup_i2c f9928000.i2c: I2C slave addr:0x1a not connected
<3>[ 1.640954] msm_sensor_match_id: imx219: read id failed
<3>[ 1.641376] qup_i2c f9928000.i2c: QUP: I2C status flags :0x1363c8, irq:132
<3>[ 1.641867] qup_i2c f9928000.i2c: I2C slave addr:0x1a not connected
<3>[ 1.642168] msm_sensor_match_id: imx219: read id failed
<3>[ 1.642783] qup_i2c f9928000.i2c: QUP: I2C status flags :0x1363c8, irq:132
<3>[ 1.643083] qup_i2c f9928000.i2c: I2C slave addr:0x1a not connected
<3>[ 1.643576] msm_sensor_match_id: imx219: read id failed
<3>[ 1.644120] msm_sensor_power_up:1140 match id failed rc -107
<3>[ 1.644365] msm_sensor_power_up:1156 failed
<3>[ 1.655464] msm_sensor_i2c_probe imx219 power up failed
<4>[ 1.655932] imx219: probe of 6-0034 failed with error -107
<6>[ 1.656301] hi841_init_module:255
<4>[ 1.656736] hi841_init_module: HW rev is 6. Sensor power is set as hi841_power_setting_on_8x10
<3>[ 1.658256] hi841_init_module:277 rc -19
<3>[ 1.658815] msm_sensor_get_dt_data qcom,product-kor 0, rc -22
<6>[ 1.682341] hi841_sensor_match_id: read id: 841 expected id 841:
<3>[ 1.682781] hi841_sensor_match_id:233 success!
<3>[ 1.704059] msm_sensor_power_down exit
<6>[ 1.704436] hi707_init_module:2904
<3>[ 1.706247] msm_sensor_get_dt_data qcom,product-kor 0, rc -22
<3>[ 1.804782] hi707_sensor_match_id: read id: b8 expected id b8:
<3>[ 1.805224] hi707_sensor_match_id: product_kor - -1
<3>[ 1.805465] hi707_sensor_match_id: maker gpio - 86
<3>[ 1.806120] vt_cam_id(gpio 86) is 0
<3>[ 1.908513] msm_sensor_power_down exit
Now, for the android part, I have tried different approaches:
Copying all the proprietary libs, including the camera HAL module, from the stock rom. Android complains about a missing call to "_ZN7androidCamera9isPreviewE" , which I find out that exists in libcamera_client.so. This library (the stock rom is kitkat) is using BufferQueue Constructor, which has been deprecated in Lollipop. I have reverted the BufferQueue Constructors in framework/native and did a rebuilt. I also copied the libcamera_client.so library from the stock rom/ The device won't boot (stays on the cm logo) and from the logcat, I see that the camera module keeps reinitializing. Removing the camera HAL module lets the device bootup and work correctly.
Code:
E/mm-camera( 9244): server_process_module_init:59, int mods
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/rmnet6/use_optimistic: No such file or directory
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/rmnet7/use_optimistic: No such file or directory
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/rmnet_usb0/use_optimistic: No such file or directory
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/teql0/use_optimistic: No such file or directory
E/Netd ( 9242): Failed to open /proc/sys/net/ipv6/conf/wlan0/use_optimistic: No such file or directory
E/mm-camera( 9244): isp_util_gen_hws_caps: integrating kernel vfe is pending
E/mm-camera( 9244): isp_tintless_create: using BG stats for tintless!, isp version = 20
E/mm-camera( 9244): is_module_init: Enter
E/mm-camera( 9244): cpp_hardware_find_subdev:903: no cpp device found.
E/mm-camera( 9244): cpp_hardware_create:40: error: cannot find cpp subdev
E/mm-camera( 9244): cpp_module_create_cpp_ctrl:164, failed, cannnot create cpp hardware instance
E/mm-camera( 9244): cpp_module_init:54 failed
E/mm-camera( 9244): vpe_module_init:26 name=vpe
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=video0 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev0 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev1 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev2 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev3 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev4 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev5 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev6 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev7 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev8 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev9 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev10 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev11 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=v4l-subdev12 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=video1 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9244): vpe_hardware_find_subdev:716: entity.name=video2 entity.revision=0
E/mm-camera( 9244): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9244): vpe_hardware_find_subdev:683: no more media devices
E/mm-camera( 9244): vpe_hardware_find_subdev:728: no vpe device found.
E/mm-camera( 9244): vpe_hardware_create:31: error: cannot find vpe subdev
E/mm-camera( 9244): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 9244): vpe_module_init:34 failed
E/mm-camera( 9244): c2d_module_init:28 name=c2d
E/mm-camera-img( 9244): img_core_get_comp:37] role 0 name qcom.wavelet
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9244): img_core_get_comp:47] find component role 0 name qcom.wavelet
W/linker ( 9244): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6ffffffe arg 0x10fc
W/linker ( 9244): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6fffffff arg 0x1
E/mm-camera-img( 9244): wd_comp_load:1571] WD library loaded successfully dsp 0
E/mm-camera-img( 9244): module_imglib_create_port:1254 portname imglib_d2_i0
E/mm-camera-img( 9244): img_core_get_comp:37] role 2 name qcom.faceproc
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[2] role 2 name qcom.faceproc
E/mm-camera-img( 9244): img_core_get_comp:47] find component role 2 name qcom.faceproc
W/linker ( 9244): libmmcamera_faceproc.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
E/mm-camera-img( 9244): img_core_get_comp:37] role 1 name qcom.hdr
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9244): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9244): img_core_get_comp:47] find component role 1 name qcom.hdr
E/mm-camera-img( 9244): hdr_comp_load:1137] HDR library loaded successfully
E/hdr ( 9244): Port hdr_dummy initialized
E/mm-camera-img( 9244): module_imglib_create_dummy_port:1362 portname imglib_dymmy_d1_i0
I/ThermalEngine( 309): Sensor:pa_therm0:37000 mC
W/linker ( 9282): libmmcamera_imglib.so: unused DT entry: type 0x6ffffffe arg 0x1c40
W/linker ( 9282): libmmcamera_imglib.so: unused DT entry: type 0x6fffffff arg 0x1
I/Netd ( 9280): Netd 1.0 starting
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/dummy0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/lo/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/p2p0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet1/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet2/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet3/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet4/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet5/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet6/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet7/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet8/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet1/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet2/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet3/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet4/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet5/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet6/use_optimistic: No such file or directory
E/mm-camera( 9282): server_process_module_init:59, int mods
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet7/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/rmnet_usb0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/teql0/use_optimistic: No such file or directory
E/Netd ( 9280): Failed to open /proc/sys/net/ipv6/conf/wlan0/use_optimistic: No such file or directory
E/mm-camera( 9282): isp_util_gen_hws_caps: integrating kernel vfe is pending
E/mm-camera( 9282): isp_tintless_create: using BG stats for tintless!, isp version = 20
E/mm-camera( 9282): is_module_init: Enter
E/mm-camera( 9282): cpp_hardware_find_subdev:903: no cpp device found.
E/mm-camera( 9282): cpp_hardware_create:40: error: cannot find cpp subdev
E/mm-camera( 9282): cpp_module_create_cpp_ctrl:164, failed, cannnot create cpp hardware instance
E/mm-camera( 9282): cpp_module_init:54 failed
E/mm-camera( 9282): vpe_module_init:26 name=vpe
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=video0 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev0 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev1 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev2 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev3 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev4 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev5 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev6 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev7 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev8 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev9 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev10 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev11 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=v4l-subdev12 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=video1 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9282): vpe_hardware_find_subdev:716: entity.name=video2 entity.revision=0
E/mm-camera( 9282): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9282): vpe_hardware_find_subdev:683: no more media devices
E/mm-camera( 9282): vpe_hardware_find_subdev:728: no vpe device found.
E/mm-camera( 9282): vpe_hardware_create:31: error: cannot find vpe subdev
E/mm-camera( 9282): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 9282): vpe_module_init:34 failed
E/mm-camera( 9282): c2d_module_init:28 name=c2d
E/mm-camera-img( 9282): img_core_get_comp:37] role 0 name qcom.wavelet
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9282): img_core_get_comp:47] find component role 0 name qcom.wavelet
W/linker ( 9282): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6ffffffe arg 0x10fc
W/linker ( 9282): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6fffffff arg 0x1
E/mm-camera-img( 9282): wd_comp_load:1571] WD library loaded successfully dsp 0
E/mm-camera-img( 9282): module_imglib_create_port:1254 portname imglib_d2_i0
E/mm-camera-img( 9282): img_core_get_comp:37] role 2 name qcom.faceproc
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[2] role 2 name qcom.faceproc
E/mm-camera-img( 9282): img_core_get_comp:47] find component role 2 name qcom.faceproc
W/linker ( 9282): libmmcamera_faceproc.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
E/mm-camera-img( 9282): img_core_get_comp:37] role 1 name qcom.hdr
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9282): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9282): img_core_get_comp:47] find component role 1 name qcom.hdr
E/mm-camera-img( 9282): hdr_comp_load:1137] HDR library loaded successfully
E/hdr ( 9282): Port hdr_dummy initialized
E/mm-camera-img( 9282): module_imglib_create_dummy_port:1362 portname imglib_dymmy_d1_i0
I/rmt_storage( 299): rmt_storage_connect_cb: clnt_h=0xa conn_h=0xb6403090
I/rmt_storage( 299): rmt_storage_rw_iovec_cb: /boot/modem_fs1: clnt_h=0x1: req_h=0xe msg_id=3: R/W request received
I/rmt_storage( 299): wakelock acquired: 1, error no: 42
I/rmt_storage( 299): rmt_storage_client_thread: /boot/modem_fs1: clnt_h=0x1 Unblock worker thread (th_id: -1236807552)
I/rmt_storage( 299): rmt_storage_client_thread: /boot/modem_fs1: clnt_h=0x1: req_h=0xe msg_id=3: Bytes written = 1572864
I/rmt_storage( 299): rmt_storage_client_thread: /boot/modem_fs1: clnt_h=0x1: req_h=0xe msg_id=3: Send response: res=0 err=0
I/rmt_storage( 299): rmt_storage_client_thread: /boot/modem_fs1: clnt_h=0x1 About to block rmt_storage client thread (th_id: -1236807552) wakelock released: 1, error no: 22
I/rmt_storage( 299):
I/rmt_storage( 299): rmt_storage_disconnect_cb: clnt_h=0x0xa conn_h=0x0xb6403090
I/ThermalEngine( 309): Sensor:pa_therm0:37000 mC
W/linker ( 9327): libmmcamera_imglib.so: unused DT entry: type 0x6ffffffe arg 0x1c40
W/linker ( 9327): libmmcamera_imglib.so: unused DT entry: type 0x6fffffff arg 0x1
E/mm-camera( 9327): server_process_module_init:59, int mods
E/mm-camera( 9327): isp_util_gen_hws_caps: integrating kernel vfe is pending
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet0/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet1/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet2/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet3/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet4/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet5/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet6/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet7/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet8/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet0/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet1/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet2/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet3/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet4/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet5/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet6/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet7/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/rmnet_usb0/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/sit0/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/teql0/use_optimistic: No such file or directory
E/Netd ( 9325): Failed to open /proc/sys/net/ipv6/conf/wlan0/use_optimistic: No such file or directory
E/mm-camera( 9327): isp_tintless_create: using BG stats for tintless!, isp version = 20
E/mm-camera( 9327): is_module_init: Enter
E/mm-camera( 9327): cpp_hardware_find_subdev:903: no cpp device found.
E/mm-camera( 9327): cpp_hardware_create:40: error: cannot find cpp subdev
E/mm-camera( 9327): cpp_module_create_cpp_ctrl:164, failed, cannnot create cpp hardware instance
E/mm-camera( 9327): cpp_module_init:54 failed
E/mm-camera( 9327): vpe_module_init:26 name=vpe
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=video0 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev0 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev1 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev2 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev3 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev4 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev5 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev6 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev7 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev8 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev9 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev10 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev11 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=v4l-subdev12 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=video1 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9327): vpe_hardware_find_subdev:716: entity.name=video2 entity.revision=0
E/mm-camera( 9327): vpe_hardware_find_subdev:711: done enumerating media entities
E/mm-camera( 9327): vpe_hardware_find_subdev:683: no more media devices
E/mm-camera( 9327): vpe_hardware_find_subdev:728: no vpe device found.
E/mm-camera( 9327): vpe_hardware_create:31: error: cannot find vpe subdev
E/mm-camera( 9327): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 9327): vpe_module_init:34 failed
E/mm-camera( 9327): c2d_module_init:28 name=c2d
E/mm-camera-img( 9327): img_core_get_comp:37] role 0 name qcom.wavelet
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9327): img_core_get_comp:47] find component role 0 name qcom.wavelet
W/linker ( 9327): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6ffffffe arg 0x10fc
W/linker ( 9327): libmmcamera_wavelet_lib.so: unused DT entry: type 0x6fffffff arg 0x1
E/mm-camera-img( 9327): wd_comp_load:1571] WD library loaded successfully dsp 0
E/mm-camera-img( 9327): module_imglib_create_port:1254 portname imglib_d2_i0
E/mm-camera-img( 9327): img_core_get_comp:37] role 2 name qcom.faceproc
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[2] role 2 name qcom.faceproc
E/mm-camera-img( 9327): img_core_get_comp:47] find component role 2 name qcom.faceproc
W/linker ( 9327): libmmcamera_faceproc.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
E/mm-camera-img( 9327): img_core_get_comp:37] role 1 name qcom.hdr
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[0] role 0 name qcom.wavelet
E/mm-camera-img( 9327): img_core_get_comp:42] comp_index[1] role 1 name qcom.hdr
E/mm-camera-img( 9327): img_core_get_comp:47] find component role 1 name qcom.hdr
E/mm-camera-img( 9327): hdr_comp_load:1137] HDR library loaded successfully
E/hdr ( 9327): Port hdr_dummy initialized
E/mm-camera-img( 9327): module_imglib_create_dummy_port:1362 portname imglib_dymmy_d1_i0
I/ThermalEngine( 309): Sensor:pa_therm0:37000 mC
W/linker ( 9364): libmmcamera_imglib.so: unused DT entry: type 0x6ffffffe arg 0x1c40
W/linker ( 9364): libmmcamera_imglib.so: unused DT entry: type 0x6fffffff arg 0x1
I/Netd ( 9362): Netd 1.0 starting
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/default/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/dummy0/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/lo/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/p2p0/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet0/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet1/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet2/accept_ra_rt_table: No such file or directory
E/Netd ( 9362): Failed to open /proc/sys/net/ipv6/conf/rev_rmnet3/accept_ra_rt_table: No such file or directory
I have also tried to build the open source qualcomm camera HAL, but the devices could not be opened, it was trying to open /dev/video1 and /dev/video2 with no success (I do not have a logcat right now, if it is needed I can provide one)
As far as I can understand, LG has used their custom av framework on this phone (???).
Does anyone have any idea on getting this to work properly?
Thank you very much for your help in advance, and sorry for the long post!

Some kind soul?