I want to build android-2.3.3_r1 branch from AOSP, to install and Multiboot it with Android 4.4 KK
I synced the repo, but I cannot "lunch".... What could I do to be able to "lunch"'?
EDIT: Tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel but I got a bootloop (logcat said this once and again):
E/Sensors (10921): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors (10921): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors (10921): sns_pwr.c(488):sns_pwr_boot: DSPS device open failed err 19
E/Sensors (10921): sns_init_la.c(301):Error 5 initializing sns_pwr_init
E/Sensors (10921): sns_main.c(1476):Exiting! sensor1_init failed with 5
I/ServiceManager( 154): service 'media.audio_flinger' died
I/ServiceManager( 154): service 'media.player' died
I/ServiceManager( 154): service 'media.camera' died
I/Netd (10925): Netd 1.0 starting
W/InterfaceController(10925): Warning (dlopen failed: library "/system/lib/libne
tcmdiface.so" not found) while opening the net interface command library
I/mediaserver(10924): ServiceManager: 0x2a00b220
I/AudioFlinger(10924): Using default 3000 mSec as standby time.
I/CameraService(10924): CameraService started (pid=10924)
I/CameraService(10924): Loaded "Qcamera" camera module
I/QCameraHAL(10924): Handle base =0x0xb6270064
I/QCameraHAL(10924): getCameraInfo: numOfCameras = 2
I/QCameraHAL(10924): Handle [0]=0x0xb6270064
I/QCameraHAL(10924): Camera sensor 0 info:
I/QCameraHAL(10924): camera_id: 0
I/QCameraHAL(10924): modes_supported: 1
I/QCameraHAL(10924): position: 0
I/QCameraHAL(10924): sensor_mount_angle: 90
I/QCameraHAL(10924): Handle [1]=0x0xb62700a8
I/QCameraHAL(10924): Camera sensor 1 info:
I/QCameraHAL(10924): camera_id: 1
I/QCameraHAL(10924): modes_supported: 1
I/QCameraHAL(10924): position: 1
I/QCameraHAL(10924): sensor_mount_angle: 270
I/AudioPolicyManagerBase(10924): loadAudioPolicyConfig() loaded /system/etc/audi
o_policy.conf
D/audio_hw_primary(10924): adev_open: enter
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_INITIALIZE
E/ (10924): [ACDB RTC]->rtc init done!->result [0]
D/Diag_Lib(10924): actp_diag_init: call diag init function with B6014209
E/Diag_Lib(10924): Diag_LSM_Init: Failed to open handle to diag driver, error =
13
E/Diag_Lib(10924): actp_diag_init: diag init failed
E/ (10924): [ACDB ACPH]->actp diag init done!
D/ACDB-LOADER(10924): No existing ION info in ACDB driver
D/ACDB-LOADER(10924): ACDB -> ION_IOC_ALLOC
D/ACDB-LOADER(10924): ACDB -> ION_IOC_SHARE
D/ACDB-LOADER(10924): ACDB -> MMAP ADDR
D/ACDB-LOADER(10924): ACDB -> register MEM to ACDB driver: 0xb5e1a000
D/ACDB-LOADER(10924): ACDB -> send_asm_topology
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
D/ACDB-LOADER(10924): send mbhc data
D/ACDB-LOADER(10924): send tabla anc data
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 148
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 74
D/ACDB-LOADER(10924): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER(10924): done with conversion, anc config size is 74
D/ACDB-LOADER(10924): ACDB -> init done!
D/ (10924): csd_client_init
E/ (10924): csd_client_service_init: Invalid rx device 0, setting to hand
set
E/ (10924): csd_client_service_init: Invalid tx device 0, setting to hand
set
E/QMI_FW (10924): xport_open: socket creation failed - 1
E/Diag_Lib(10924): Diag_LSM_Init: Failed to open handle to diag driver, error =
13
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
E/QMI_FW (10924): QMUXD: Service_id=20 not found over conn_id=0
D/audio_hw_primary(10924): adev_open: exit
I/AudioFlinger(10924): loadHwModule() Loaded primary audio interface from QCOM A
udio HAL (audio) handle 1
D/audio_hw_primary(10924): adev_open_output_stream: enter: sample_rate(44100) ch
annel_mask(0x3) devices(0x2) flags(0x2)
D/audio_hw_primary(10924): adev_open_output_stream: exit
I/AudioFlinger(10924): HAL output buffer size 240 frames, normal mix buffer size
960 frames
I/AudioMixer(10924): found effect "Multichannel Downmix To Stereo" from The Andr
oid Open Source Project
E/MonoPipe(10924): Failed to fetch local time frequency when constructing a Mono
Pipe (res = -32). getNextWriteTimestamp calls will be non-functional
D/MDnsDS (10925): MDnsSdListener::Hander starting up
D/MDnsDS (10925): MDnsSdListener starting to monitor
D/MDnsDS (10925): Going to poll with pollCount 1
Click to expand...
Click to collapse
bamsbamx said:
I want to build android-2.3.3_r1 branch from AOSP, to install and Multiboot it with Android 4.4 KK
I synced the repo, but I cannot "lunch".... What could I do to be able to "lunch"'?
Click to expand...
Click to collapse
It just won't work, don't try.
2.3.3? is that number correct?if so, then just build it will not work.
realfelix said:
It just won't work, don't try.
Click to expand...
Click to collapse
opssemnik said:
2.3.3? is that number correct?if so, then just build it will not work.
Click to expand...
Click to collapse
Ok, but why it wont work? i have tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel... Got a bootloop
Logcat said there was an error with Netd and kept saying "going to poll with pollcount 1" once and again
bamsbamx said:
Ok, but why it wont work? i have tried to port Android 2.3.6 (GRK39F) factory image for Nexus S using PSX as base and PSX kernel... Got a bootloop
Logcat said there was an error with Netd and kept saying "going to poll with pollcount 1" once and again
Click to expand...
Click to collapse
Nexus 4 device tree and proprietary files are for jellybean. It simply isnt compatible with gingerbread.
Why don't you try with cupcake? You might have better luck with it...
Sent from my Nexus 4 using Tapatalk
it will not work without hard work because of s4 pro drivers are for 4.0.3+. since nexus 4 is packed with 4.2.2, u can build 4.1.2 or 4.0.4 or 4.0.3 and use lg og drivers.
BigDig said:
Why don't you try with cupcake? You might have better luck with it...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I want to try GB because I need to test my apps
bamsbamx said:
I want to try GB because I need to test my apps
Click to expand...
Click to collapse
Then, try to use a virtual machine on your pc
luiseteyo said:
Then, try to use a virtual machine on your pc
Click to expand...
Click to collapse
I have been using Android emulator with AVD, but It seems to be a bit slow.
Also, as we have multiboot why not to try GB in our Nexus??
bamsbamx said:
I have been using Android emulator with AVD, but It seems to be a bit slow.
Also, as we have multiboot why not to try GB in our Nexus??
Click to expand...
Click to collapse
Yes, yes, I am part of the people that say that development is always helpful and appreciated, even if consists in building a previous android version.
Because there aren't drivers for it and Qualcomm isn't going to release them for GB.
sent via tapatalk
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
we can at maxximum have 4.0.3 without any hard work. 2.3 is possible, but u need to "hack" the libs to make them for 2.3.
for 4.0.3 we use lg optimus g drivers(same chipset)
Oxious119 said:
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Haha, no... It would be like having a Porsche engine and have much lighter car body
opssemnik said:
we can at maxximum have 4.0.3 without any hard work. 2.3 is possible, but u need to "hack" the libs to make them for 2.3.
for 4.0.3 we use lg optimus g drivers(same chipset)
Click to expand...
Click to collapse
Well for having 4.0.3, could we get it working by just flashing a 4.0.3 rom for lg optimus g?
Oxious119 said:
That would be like removing a Porsche engine to replace it with a Fiat cinquecento engine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is like having a Porsche and study how to make a Fiat Punto work with its engine. Just study, curiosity, its development, I think it's a great idea.
Anyway, @bamsbamx I would try to build 4.1 or 4.0, which will be much easier.
luiseteyo said:
It is like having a Porsche and study how to make a Fiat Punto work with its engine. Just study, curiosity, its development, I think it's a great idea.
Anyway, @bamsbamx I would try to build 4.1 or 4.0, which will be much easier.
Click to expand...
Click to collapse
Well, but which device should I select to build?
After building, from where can I get those drivers?
I dont know to much about building
I know, I wasn't trying to discredit your effort.
Sent from my Nexus 4 using xda app-developers app
bamsbamx said:
Haha, no... It would be like having a Porsche engine and have much lighter car body
Well for having 4.0.3, could we get it working by just flashing a 4.0.3 rom for lg optimus g?
Click to expand...
Click to collapse
no, we cant use their kernel, we need to use our kernel, but edit ramdisk for ics.and if u porting from their kernels u need to change partition layout.
P.S: we also need to remove libs from their roms. and modify some things. so it would be way easier just to use their s4 pro libs with our builded ics.i tried their stock 4.1.2 it booted,(imodified ramdisk and removed some libs, and little tweaks to vold.fstab and framework). but my hdd failed so i lost everything and my phone is on repair.
opssemnik said:
no, we cant use their kernel, we need to use our kernel, but edit ramdisk for ics.and if u porting from their kernels u need to change partition layout.
P.S: we also need to remove libs from their roms. and modify some things. so it would be way easier just to use their s4 pro libs with our builded ics.i tried their stock 4.1.2 it booted,(imodified ramdisk and removed some libs, and little tweaks to vold.fstab and framework). but my hdd failed so i lost everything and my phone is on repair.
Click to expand...
Click to collapse
ok then, where could I get their S4 pro libs?
Related
So, i tried to compile V20a kernel and i get this errors:
Code:
CC drivers/power/lge_pm_sysfs.o
drivers/power/lge_pm_sysfs.c:25:38: fatal error: ../../kernel/power/power.h: No such file or directory
compilation terminated.
make[2]: *** [drivers/power/lge_pm_sysfs.o] Error 1
make[1]: *** [drivers/power] Error 2
make[1]: *** Waiting for unfinished jobs....
Code:
LD drivers/net/built-in.o
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC net/netfilter/xt_length.o
Anyone tried to compile? How can i solve this error?
i managed to compile it but it doesn't boot . logcat not available.
Please, can you give me some ideea as i am not a developer. I will flash now my original boot img
hmmm is bad
Hint
Hello,
I also discovered that the way the kernel should be compiled according to the readme file is impossible. It does mention a defconfig file that is not available.
However, it is possible to get the config file of an existing kernel, because it is compiled in in the kernel:
Use the following steps, when your PC is connected to your phone with an working v20a kernel:
$adb pull /proc/config.gz
$gunzip config.gz
$mv config YOURKERNELROOT/arch/arm/configs/u2_my_defconfig
$cd YOURKERNELROOT
$make youroptions u2_my_defconfig
de-wolff said:
Hello,
I also discovered that the way the kernel should be compiled according to the readme file is impossible. It does mention a defconfig file that is not available.
However, it is possible to get the config file of an existing kernel, because it is compiled in in the kernel:
Use the following steps, when your PC is connected to your phone with an working v20a kernel:
$adb pull /proc/config.gz
$gunzip config.gz
$mv config YOURKERNELROOT/arch/arm/configs/u2_my_defconfig
$cd YOURKERNELROOT
$make youroptions u2_my_defconfig
Click to expand...
Click to collapse
I built it using my phones defconfig and removed this from makefile "drivers/power/lge_pm_sysfs.o". The build was successful but it doesn't boot. I will start working on it today.
Update: IT BOOTS!
I wasn't packing it correctly:
These are the lines to pack it:
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline androidboot.hardware=u0 --base 0x00200000 --pagesize 4096 -o boot.img
Click to expand...
Click to collapse
kernel version is:
Linux version 3.4.0-perf ([email protected]) (gcc version 4.6.2 20111004 (prerelease) (Linaro GCC 4.6-2011.10) ) #2 PREEMPT Wed Apr 17 23:22:22 EEST 2013
Click to expand...
Click to collapse
i will start patching tomorrow or later because i have to figure out how to OC and how to git
tudorsirb said:
So, i tried to compile V20a kernel and i get this errors:
Code:
CC drivers/power/lge_pm_sysfs.o
drivers/power/lge_pm_sysfs.c:25:38: fatal error: ../../kernel/power/power.h: No such file or directory
compilation terminated.
make[2]: *** [drivers/power/lge_pm_sysfs.o] Error 1
make[1]: *** [drivers/power] Error 2
make[1]: *** Waiting for unfinished jobs....
Code:
LD drivers/net/built-in.o
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC net/netfilter/xt_length.o
Anyone tried to compile? How can i solve this error?
Click to expand...
Click to collapse
open lge_pm_sysfs.c and set power.h file to the correct path.
moon61 said:
open lge_pm_sysfs.c and set power.h file to the correct path.
Click to expand...
Click to collapse
i fixed that error, the kernel build and boots from stock sources. Now i'm trying to figure out what to do with the modules as wireless doesn't work, how to apply patches and how to overclock because i can't find freqs in acpuclock. Any sugestions?
How to modify kernel
Once you are able to make a working kerrnel, it is quite easy to modify it.
After you did make a working kernel, you can do from the commandline in the kernel root:
Make [crosscompile options] menuconfig.
Now you can change all kernel options, using a menu.
You have to install ncurses-dev, before you can do a make menuconfig
Once you are ready using the menuconfig, a new config file is created, with the name ,config ([dot]config). Beware that this is a hidden file in linux!. You can rename it and move it to your config dir.
Of course, most of the options are hardware related, and you do not want to change them, but the options you want to change, you can find all in the menu, together with a brief explanation of their usage,
(Excuses for my bad english, it is not my primary language)
de-wolff said:
Once you are able to make a working kerrnel, it is quite easy to modify it.
After you did make a working kernel, you can do from the commandline in the kernel root:
Make [crosscompile options] menuconfig.
Now you can change all kernel options, using a menu.
You have to install ncurses-dev, before you can do a make menuconfig
Once you are ready using the menuconfig, a new config file is created, with the name ,config ([dot]config). Beware that this is a hidden file in linux!. You can rename it and move it to your config dir.
Of course, most of the options are hardware related, and you do not want to change them, but the options you want to change, you can find all in the menu, together with a brief explanation of their usage,
(Excuses for my bad english, it is not my primary language)
Click to expand...
Click to collapse
Thanks, this will be useful after i apply some upstream changes. I know about menuconfig but i haven't got the tine to check it out. Right now i'm trying to overclock this kernel and i keep getting compile errors (took some code from l5). Will come back with info. If you can help me these days PM me with a gtalk ID.
tudorsirb said:
i fixed that error, the kernel build and boots from stock sources. Now i'm trying to figure out what to do with the modules as wireless doesn't work, how to apply patches and how to overclock because i can't find freqs in acpuclock. Any sugestions?
Click to expand...
Click to collapse
Yes I have a problem with wifi too, even I used new compiled modules. Did you fix it?
Sent from my LG-P705 using Tapatalk 2
moon61 said:
Yes I have a problem with wifi too, even I used new compiled modules. Did you fix it?
Sent from my LG-P705 using Tapatalk 2
Click to expand...
Click to collapse
I didn't fix it. I will look into it later (i'm at work ATM).
Logcat is:
Code:
need to unregister
04-22 11:28:19.010 E/WifiStateMachine( 449): Couldn't get getWiFiOffloadingIfaceIface :
04-22 11:28:19.010 E/WifiStateMachine( 449): useWiFiOffloading() : false
04-22 11:28:19.010 E/WifiStateMachine( 449): CONFIG_LGE_WLAN_PATH : true
04-22 11:28:19.010 D/WifiStateMachine( 449): setWifiState: enabling
04-22 11:28:19.010 I/WifiServiceExt( 449): WIFI_STATE_CHANGED_ACTION [2]
04-22 11:28:19.020 D/QuickSettingsReceiverStation( 514): Received: android.net.wifi.WIFI_STATE_CHANGED
04-22 11:28:19.030 E/WifiHW ( 449): nv_cmd_remote status 0
04-22 11:28:19.030 E/WifiHW ( 449): nv_cmd_remote status 0
04-22 11:28:19.030 E/WifiHW ( 449): Modem MAC address: a8 16 b2 93 c8 f6
04-22 11:28:19.030 E/WifiHW ( 449): Set wifi mac address a8 16 b2 93 c8 f6
04-22 11:28:19.030 E/WifiUtil( 449): U0 : CONFIG_LGE_WLAN_U0_JB_PATCH
04-22 11:28:19.030 I/ONCRPC ( 449): Setup RPC Call for task 4049f920
04-22 11:28:19.030 I/ONCRPC ( 449): oncrpc_xdr_call_msg_start: Prog: 3000000e, Ver: 00090001, Proc: 00000009
04-22 11:28:19.030 I/ONCRPC ( 449): xdr_std_msg_send_call: Sent Xid: a68, Prog: 3000000e, Ver: 00090001, Proc: 00000009
04-22 11:28:19.030 I/ONCRPC ( 449): xdr_std_msg_send_call: Received Reply Xid: a68, Prog: 3000000e, Ver: 00090001, Proc: 00000009
04-22 11:28:19.090 E/WifiStateMachine( 449): Failed to load driver!
04-22 11:28:19.090 E/WifiStateMachine( 449): Couldn't get getWiFiOffloadingIfaceIface :
04-22 11:28:19.090 E/WifiStateMachine( 449): useWiFiOffloading() : false
04-22 11:28:19.090 E/WifiStateMachine( 449): CONFIG_LGE_WLAN_PATH : true
04-22 11:28:19.090 D/WifiStateMachine( 449): setWifiState: unknown state
04-22 11:28:19.090 I/WifiServiceExt( 449): WIFI_STATE_CHANGED_ACTION [4]
04-22 11:28:19.090 E/WifiServiceExt( 449): WifiManager.WIFI_STATE_UNKNOWN
04-22 11:28:19.090 D/QuickSettingsReceiverStation( 514): Received: android.net.wifi.WIFI_STATE_CHANGED
Any news about how to fix wifi problem?
Sent from my LG-P705 using Tapatalk 2
any news??
Ok, i think i had find where the problem is. I change the cfg80211 value in the config file to "m". And know wifi work fine.
This is the kernel link
http://db.tt/lfJeyFeY
The kernel also o/c able too
Thanx to @tudorsirb :thumbup: and sorry for my bad english.
Sent from my LG-P705 using Tapatalk 2
moon61 said:
Ok, i think i had find where the problem is. I change the cfg80211 value in the config file to "m". And know wifi work fine.
This is the kernel link
http://db.tt/lfJeyFeY
The kernel also o/c able too
Thanx to @tudorsirb :thumbup: and sorry for my bad english.
Sent from my LG-P705 using Tapatalk 2
Click to expand...
Click to collapse
Did you use pll2 or pll4 for oc? If you use pll4 there's no difference in performance when using the phone becuase our phone does not OC that way.
Your OC code hould look like this:
Code:
{ 1, 1200000, [B]ACPU_PLL_2, 2, 0, [/B]150000, 3, 7, 200000 },
I learned it the hard way . Check out github for more references.
Hi,
I intensively searched for my problem, but found always other non-related stuff.
Recently (last 1, 2 days) my WiFi didn't connect to any APs any more. I was using CN nightlies and franco kernel, so today I did update CN without franco. Afterwards I downgraded CN and did a radio update and now I tried the stock 4.2.2 image with the flash-all script, which also seemed to reflash my radio.
The default wifi dialog always displayed the saved wifis only. And after installing stock, the initial wifi dialog displayed "searching" only for a very long time. Sometimes I see some networks and I even managed to connect to mine, but it dropped immediately.
I know, this is very undetailed, but do you have any recommendations / logs to look out / smth which could point me in the right direction? Or is my hardware just broken?
logcat outputs this when turning wi-fi on (on stock 4.2.2, unrooted):
D/WifiService( 499): setWifiEnabled: true pid=1942, uid=1000
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
W/Netd ( 156): No subsystem found in netlink event
D/NetlinkEvent( 156): Unexpected netlink message. type=0x11
D/Tethering( 499): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 499): InitialState.processMessage what=4
D/Tethering( 499): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 156): Softap fwReload - Ok
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring down wlan0
E/NetdConnector( 499): NDC Command {219 softap fwreload wlan0 STA} took too long (739ms)
I/wpa_supplicant( 9715): Successfully initialized wpa_supplicant
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
I/wpa_supplicant( 9715): rfkill: Cannot open RFKILL control device
D/CommandListener( 156): Setting iface cfg
D/CommandListener( 156): Trying to bring up p2p0
D/BluetoothAdapter( 1942): 1110956336: getState() : mService = null. Returning STATE_OFF
Click to expand...
Click to collapse
when flashing stock (via the official google flash scripts), stock firmware files (qualcom, ..) are also flashed, right? or could I do something useful with the official google binaries?
Stupid post.... Ignore
Hi,
Currently I'm compiling OmniRom for Samsung Galaxy Mega GT-I9205.
When I try to boot it for the first time, the Omni is stuck at the boot animation...
May I know what is the general failure for this particular issue? and how to solve it?
logcat F/
Code:
12-29 19:01:06.722 F/MediaProfiles( 287): frameworks/av/media/libmedia/MediaProfiles.cpp:324 CHECK(quality != -1) failed.
12-29 19:01:06.722 F/libc ( 287): Fatal signal 6 (SIGABRT) at 0x0000011f (code=-6), thread 287 (zygote)
logcat /E
Code:
12-29 19:01:07.513 E/QualcommCamera( 754): Qint android::get_number_of_cameras(): E
...
12-29 19:01:07.513 I/AudioPolicyManagerBase( 754): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
12-29 19:01:07.523 D/ALSADevice( 754): ALSA module opened
12-29 19:01:07.533 D/AudioHardwareALSA( 754): AudioHardware: DLOPEN successful for ACDBLOADER
12-29 19:01:07.533 D/ACDB-LOADER( 754): ACDB -> ACDB_CMD_INITIALIZE
12-29 19:01:07.533 E/ ( 754): [ACDB RTC]->rtc init done!->result [0]
12-29 19:01:07.533 E/Diag_Lib( 754): actp_diag_init: call diag init function with B5F20ECD
12-29 19:01:07.533 E/Diag_Lib( 754): Diag_LSM_Init: Failed to open handle to diag driver, error = 13
12-29 19:01:07.533 E/Diag_Lib( 754): actp_diag_init: diag init failed
12-29 19:01:07.533 E/ ( 754): [ACDB ACPH]->actp diag init done!
---
I suspect the media_profiles.xml is corrupted... but nope...
anywhere this is the comparison of media_profiles.xml between
melius >> https://github.com/Grarak/android_d...mon/blob/android-4.4/media/media_profiles.xml
hammerhead >> https://github.com/omnirom/android_device_lge_hammerhead/blob/android-4.4/media_profiles.xml
Diff >> http://diffchecker.com/ghjvhy51
and the device mk file
Code:
https://github.com/Grarak/android_device_samsung_melius-common/blob/android-4.4/melius-common.mk
# Media Profile
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/media/media_profiles.xml:system/etc/media_profiles.xml
# Note: Didnt have media_codecs.xml
Code:
https://github.com/omnirom/android_device_lge_hammerhead/blob/android-4.4/device.mk
PRODUCT_COPY_FILES += \
device/lge/hammerhead/media_codecs.xml:system/etc/media_codecs.xml \
device/lge/hammerhead/media_profiles.xml:system/etc/media_profiles.xml
Try using hammerhead (or another closer similar Qcom device)'s media_codec.xml and media_profiles.xml (or remove those files)
Thank your for the suggestion... look like i have to test on hammerhead xml afterall :crying:
but b4 that,
Im hoping someone able to tell me the logcat diagnostic
coz this file is currently used in CM11 (I9205) and they didnt have issue for this particular matter
Great news...
I managed to get it working... now omnirom have another working device in his pocket
Solutions: use media codec + profile from hammerhead... media codec + profile by touchwiz wont work
---
but i still have some problem
i able to get the camera to work, but the video recording is recording black screen...
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.
After a dealing with selling my house and moving into a new one, I've finally got my build system back together and connected to the Internet. This Ubuntu machine has been successfully building OmniROM 4.x for a couple devices and 5.1 for Nexus 5 for some time, but now I have a puzzle.
The "nightly" version of OmniROM boots and runs fine on the hardware. However, when I try to boot the "homemade" version of 5.1, it fails to get very far in the process. I've already pulled down a fresh repo, installed the factory drivers from https://developers.google.com/android/nexus/drivers (originally 5.1 LMY48B, but now have also tried fresh copies of 5.1 LMY48M) and everything appears to build properly.
Looking at the two logcat outputs, the earliest hints of error seem to be the inability to load a key library
NIGHTLY:
Code:
03-31 16:27:29.726 D/QSEECOMD: ( 179): qseecom listener services process entry PPID = 1
03-31 16:27:29.726 E/QSEECOMD: ( 179): Listener: index = 0, hierarchy = 0
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init dlopen(librpmb.so, RTLD_NOW) succeeds
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
HOMEMADE:
Code:
03-31 15:07:02.586 E/QSEECOMD: ( 176): Listener: index = 0, hierarchy = 0
03-31 15:07:02.586 E/QSEECOMD: ( 176): Init dlopen(librpmb.so, RLTD_NOW) is failed....
03-31 15:07:02.586 E/QSEECOMD: ( 176): ERROR: RPMB_INIT failed, shall not start listener services
That stanza, or one very similar is spattered throughout the homemade logcat.
Looking at the homemade version, "find / -name librpmb.so" returns nothing.
For the nightly version, it is found at /system/lib/librpmb.so
I don't see it in the output directory, but it is in the vendor source directory
Code:
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find . -name librpmb.so
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find $ANDROID_BUILD_TOP/vendor -name librpmb.so
/home/jeff/devel/build/hammerhead-5.1/vendor/qcom/hammerhead/proprietary/librpmb.so
Digging further, vendor/qcom/hammerhead/device-partial.mk does not include librpbm.so (but does, for example, include qseecomd)
I don't see anything in vendor/qcom/hammerhead/ that would copy over librpmb.so
Looking at the installed nightly rom, /system/lib/librpmb.so is there (and has the same md5 as that from the qcom driver distributions)
Has anyone seen this before? Any suggestions on resolution? (other than the obvious, "Well, just edit the qcom device-partial.mk")
I'm sort of stuffed on doing any dev work until I can get a working baseline build again...
Thanks,
Jeff
jeffsf said:
After a dealing with selling my house and moving into a new one, I've finally got my build system back together and connected to the Internet. This Ubuntu machine has been successfully building OmniROM 4.x for a couple devices and 5.1 for Nexus 5 for some time, but now I have a puzzle.
The "nightly" version of OmniROM boots and runs fine on the hardware. However, when I try to boot the "homemade" version of 5.1, it fails to get very far in the process. I've already pulled down a fresh repo, installed the factory drivers from https://developers.google.com/android/nexus/drivers (originally 5.1 LMY48B, but now have also tried fresh copies of 5.1 LMY48M) and everything appears to build properly.
Looking at the two logcat outputs, the earliest hints of error seem to be the inability to load a key library
NIGHTLY:
Code:
03-31 16:27:29.726 D/QSEECOMD: ( 179): qseecom listener services process entry PPID = 1
03-31 16:27:29.726 E/QSEECOMD: ( 179): Listener: index = 0, hierarchy = 0
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init dlopen(librpmb.so, RTLD_NOW) succeeds
03-31 16:27:29.733 D/QSEECOMD: ( 179): Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
HOMEMADE:
Code:
03-31 15:07:02.586 E/QSEECOMD: ( 176): Listener: index = 0, hierarchy = 0
03-31 15:07:02.586 E/QSEECOMD: ( 176): Init dlopen(librpmb.so, RLTD_NOW) is failed....
03-31 15:07:02.586 E/QSEECOMD: ( 176): ERROR: RPMB_INIT failed, shall not start listener services
That stanza, or one very similar is spattered throughout the homemade logcat.
Looking at the homemade version, "find / -name librpmb.so" returns nothing.
For the nightly version, it is found at /system/lib/librpmb.so
I don't see it in the output directory, but it is in the vendor source directory
Code:
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find . -name librpmb.so
[email protected]:~/devel/build/hammerhead-5.1/out/target/product/hammerhead$ find $ANDROID_BUILD_TOP/vendor -name librpmb.so
/home/jeff/devel/build/hammerhead-5.1/vendor/qcom/hammerhead/proprietary/librpmb.so
Digging further, vendor/qcom/hammerhead/device-partial.mk does not include librpbm.so (but does, for example, include qseecomd)
I don't see anything in vendor/qcom/hammerhead/ that would copy over librpmb.so
Looking at the installed nightly rom, /system/lib/librpmb.so is there (and has the same md5 as that from the qcom driver distributions)
Has anyone seen this before? Any suggestions on resolution? (other than the obvious, "Well, just edit the qcom device-partial.mk")
I'm sort of stuffed on doing any dev work until I can get a working baseline build again...
Thanks,
Jeff
Click to expand...
Click to collapse
Weird. I still haven't gotten completely back from vacation (have a friend visiting now) so I haven't built Omni in a while...
I'll try to build it when they leave, not sure when that will be though.
@XpLoDWilD and @maxwen - Could this potentially be one of those weird messes where our source trees have an issue but the build server hasn't properly synced? This wouldn't be the first time we've had a "why the hell didn't this break months ago" issues like some issues @Jakew02 had last winter.
More digging reveals that between 5.0 (LRX21O) and 5.1.1 (LMY48M) the following files appear to be added (all in 5.1.0 LMY47D aka 1743759):
vendor/qcom/hammerhead/proprietary/librpmb.so
vendor/qcom/hammerhead/proprietary/libssd.so
vendor/qcom/hammerhead/proprietary/qmi_fw.conf
On the other hand, vendor/qcom/hammerhead/device-partial.mk has apparently not changed since at least LRX21O
fgrep suggests that libssd.so is referenced in qseecomd (as is librpmb.so)
jeffsf said:
More digging reveals that between 5.0 (LRX21O) and 5.1.1 (LMY48M) the following files appear to be added (all in 5.1.0 LMY47D aka 1743759):
vendor/qcom/hammerhead/proprietary/librpmb.so
vendor/qcom/hammerhead/proprietary/libssd.so
vendor/qcom/hammerhead/proprietary/qmi_fw.conf
On the other hand, vendor/qcom/hammerhead/device-partial.mk has apparently not changed since at least LRX21O
fgrep suggests that libssd.so is referenced in qseecomd (as is librpmb.so)
Click to expand...
Click to collapse
Better use the DonkeyCoyote repo, at least this is what Jenkins does afaik: https://github.com/DonkeyCoyote/proprietary_vendor_lge/tree/android-5.1/hammerhead
golden-guy said:
Better use the DonkeyCoyote repo, at least this is what Jenkins does afaik: https://github.com/DonkeyCoyote/proprietary_vendor_lge/tree/android-5.1/hammerhead
Click to expand...
Click to collapse
Didn't realize he wasn't... librpmb was added with https://github.com/DonkeyCoyote/pro...mmit/1a71e5c4d257c4883e1dea461fd893df13e0413c
AOSP's official binary blob distros often are missing stuff that is necessary for some capabilities and CAN be found in the factory images.
We don't mention DC in any official documentation for legal liability reasons... We probably need to update the extract-files scripts for ALL of our devices...