Hi,
I am trying to get access to the IOMX interface for use in a video decoding app.
I realize the API's I am using are non public and subject to change but the public API are not good enough for me.
I need access to the compressed and decoded data and so this seems to the way to go.
I found some sample code on the net that shows how to get the IOMX pointer.
(tried to post the link but it won't let me since, apparently I am a noob :cyclops
So I tried running that and I get a crash.
This is the code:
Code:
sp<IServiceManager> sm = defaultServiceManager();
Vector<String16> vec = sm->listServices();
sp<IBinder> binder = sm->getService(String16("media.player"));
sp<IMediaPlayerService> service = interface_cast<IMediaPlayerService>(binder);
[COLOR="Red"]sp<IOMX> mOMX = service->getOMX();[/COLOR]
And the crash occurrs on the last line (red) - start of dump below.
All I want is to be able to enumerate the OMX components for now. When that works I expect I can continue.
Should I be initializing anything before running the above code? OMX? Stagefright?
Thank you in advance,
Tomer
06-25 10:02:40.300: I/DEBUG(13769): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-25 10:02:40.300: I/DEBUG(13769): Build fingerprint: 'samsung/GT-P7500/GT-P7500:3.2/HTJ85B/JJKK3:user/release-keys'
06-25 10:02:40.300: I/DEBUG(13769): pid: 15347, tid: 15359 >>> com.ai.playcast <<<
06-25 10:02:40.300: I/DEBUG(13769): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr ae684e99
06-25 10:02:40.300: I/DEBUG(13769): r0 ae684e99 r1 ae684e99 r2 00000001 r3 00000008
06-25 10:02:40.300: I/DEBUG(13769): r4 5c55e914 r5 ae684e99 r6 5c55e9d8 r7 00268910
06-25 10:02:40.300: I/DEBUG(13769): r8 a90388f5 r9 ae684e99 10 00268048 fp fffffe90
06-25 10:02:40.300: I/DEBUG(13769): ip a81233dc sp 5c55e8c0 lr a811aafd pc aff14aec cpsr 00000010
Questions go in the Q&A section
I have some updates on this that may make this less opaque.
I looked into the implementation of getOMX().
It seems straight forward enough so I copied it to my own code instead of calling getOMX(). This time it didn't crash - this is becoming a little voodoo.
However I got the handle to the IOMX object.
So then I tried enumerating the components but the list comes back empty.
Anyone has any idea why?
Here is my original crashing code (crashing on the red line):
Code:
android::ProcessState::self()->startThreadPool();
sp<IServiceManager> sm = defaultServiceManager();
sp<IBinder> binder = sm->getService(String16("media.player"));
sp<IMediaPlayerService> service = interface_cast<IMediaPlayerService>(binder);
[COLOR="Red"]sp<IOMX> mOMX = service->getOMX();[/COLOR]
This is my non-crashing code that returns an empty component list:
Code:
android::ProcessState::self()->startThreadPool();
sp<IServiceManager> sm = defaultServiceManager();
sp<IBinder> binder = sm->getService(String16("media.player"));
sp<IMediaPlayerService> service = interface_cast<IMediaPlayerService>(binder);
sp<IOMX> mOMX;
{
Parcel data, reply;
data.writeInterfaceToken(service->getInterfaceDescriptor());
binder->transact(6, data, &reply);
mOMX = interface_cast<IOMX>(reply.readStrongBinder());
}
List<IOMX::ComponentInfo> componenInfos;
status_t err = mOMX->listNodes(&componenInfos);
if (componenInfos.size() == 0)
[COLOR="red"]log_err("no components found %d", err);[/COLOR]
I've also tried calling OMX_Init() before all this but it didn't help.
Please, if anyone has any idea what's going on I would greatly appreciate it.
Thank you in advance
Use at your own risk - untested
I am not responsible for bricked devices.
Back up before doing anything
Compiled using the following device tree: https://github.com/CyanogenMod/android_device_sony_z3c
Working:
Nothing, as far as I am concerned which is why you should use at your own risk.Not Working:
Everything, as far as I am concerned which is why you should use at your own risk.
The commands I used to make zip package was:
Code:
. build/envsetup.sh
lunch
make bacon
(Brunch and Breakfast are for official devices only, I believe)
Local Manifest includes:
Code:
<project name="CyanogenMod/android_device_sony_z3c" path="device/sony/z3c" remote="github" />
<project name="CyanogenMod/android_device_sony_shinano-common" path="device/sony/shinano-common" remote="github" />
<project name="CyanogenMod/android_kernel_sony_msm8974" path="kernel/sony/msm8974" remote="github" />
<project name="CyanogenMod/android_device_sony_qcom-common" path="device/sony/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_device_sony_msm8974-common" path="device/sony/msm8974-common" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
File can be found in Downloads Tab
And,
Mirror: AndroidFileHost
XDA:DevDB Information
ROM compilation, ROM for the Sony Xperia Z3 Compact
Contributors
m0d
Thank you to Kali- and chirayudesai for setting up device tree at: android_device_sony_z3c
And, thank you to the people who spared the time in correcting my silly mistakes, and for responding to my even sillier questions.
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2014-12-15
Last Updated 2014-12-17
No clue how you managed to build, I've been trying for days!
Anyhow, booted it up and it restarts repeatedly at the 'starting system apps' stage. Here's a logcat:
Code:
https://bpaste.net/show/6aaa730e0985
---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------
Gairtial said:
No clue how you managed to build, I've been trying for days!
Anyhow, booted it up and it restarts repeatedly at the 'starting system apps' stage. Here's a logcat:
Code:
https://bpaste.net/show/6aaa730e0985
Click to expand...
Click to collapse
I should also mention that the installation initially failed. The device calls itself 'aries', not 'd5803'. Had to modify the script in the ZIP before flashing.
Gairtial said:
No clue how you managed to build, I've been trying for days!
Click to expand...
Click to collapse
Magic!
But, there is no magic.
Send me your build error,
And also the error for show commands and I will try to help.
As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks.
Gairtial said:
I should also mention that the installation initially failed. The device calls itself 'aries', not 'd5803'. Had to modify the script in the ZIP before flashing.
Click to expand...
Click to collapse
Yes, someone mentioned that before.
Not sure where to look.
I did find this in BoardConfig.mk,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c
And, in init.sony.usb.rc - this:
Code:
on boot
write /sys/class/android_usb/android0/iSerial ${ro.serialno}
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
The problem is sony calls the device aries, the code for the device is d5803, and the device tree by cm12 is z3c.
I like z3c but if anyone knows where, maybe one of the mk files, to make the changes?
Any help appreciated. I am learning as I go and as I said above:
Thank you to the people who take the time to correct my silly mistakes, and for responding to my even sillier questions
Click to expand...
Click to collapse
I only compiled device tree, no changes as of yet, other than small fixes for compilation.
m0d said:
Magic!
But, there is no magic.
Send me your build error,
And also the error for show commands and I will try to help.
As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks.
Click to expand...
Click to collapse
The build errors started with libtime_genoff.so being missing from the output directory so I manually copied it over and it continued on fine.
There were some issues with AAPT but I manually fixed those (and submitted patches for review to Gerrit).
Just waiting for the build to complete now. Are you on IRC/Hangouts or something? Mind if I PM you so we can talk a little more freely?
m0d said:
Magic!
But, there is no magic.
Send me your build error,
And also the error for show commands and I will try to help.
As that is the secret. In programming I come to find more and more that there is no better place to go than an actual person - not all errors are documented and some strange things happen for no apparent reason, or so one thinks.
Yes, someone mentioned that before.
Not sure where to look.
I did find this in BoardConfig.mk,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c
And, in init.sony.usb.rc - this:
Code:
on boot
write /sys/class/android_usb/android0/iSerial ${ro.serialno}
write /sys/class/android_usb/android0/iManufacturer ${ro.product.manufacturer}
write /sys/class/android_usb/android0/iProduct ${ro.product.model}
The problem is sony calls the device aries, the code for the device is d5803, and the device tree by cm12 is z3c.
I like z3c but if anyone knows where, maybe one of the mk files, to make the changes?
Any help appreciated. I am learning as I go and as I said above:
I only compiled device tree, no changes as of yet, other than small fixes for compilation.
Click to expand...
Click to collapse
Check your build.prop in your compiled build folder (/system) and look for the variables below:
"ro.product.device" "ro.build.product"
If you want to change the values, mount your system.img, make your changes and make new .img
(PM me if you need help with this..)
it's not hard to delect the first sentence in updater-script in zip,then we could get it flashed
Okay, did my own build using similar instructions and came up with the following issues:
libtime_genoff.so wasn't copied during the build process, manually copying required manually copying a second time after the build.
DPI was first set to 480 in build.prop. Reset it to 320 through ADB after booting and it works fine
On the first boot the modem appeared to work (connected to my network), on the second it did not. Nothing I can understand in ADB that's relevant.
Wifi appears to work properly
Camera crashes
GPS error message:
Code:
D/LocSvc_utils_cfg( 5088): D/loc_read_conf: using /etc/gps.conf
D/LocSvc_utils_cfg( 5088): D/loc_set_config_entry: PARAM DEBUG_LEVEL = 2
E/gpsone_dmn( 5088): gpsone_glue_pipeget:46] /data/misc/gsiff_ctrl_q, mode = 2
E/gpsone_dmn( 5088): gpsone_glue_pipeget:50] pipe_name: /data/misc/gsiff_ctrl_q failed: 13
E/gsiff_dmn( 5088): W/gsiff_dmn_init: Unable to initialize Message Queue!
E/gsiff_dmn( 5088): W/gsiff_loc_api_close: Improperly closing Loc API Client!
E/gsiff_dmn( 5088): W/gsiff_dmn_destroy: Could not destroy loc api!
E/gsiff_sp_glue( 5088): W/sp_destroy: Sensor provider not initialized. Sensor provider = 0
E/gsiff_dmn( 5088): W/gsiff_dmn_destroy: Could not destroy sensor provider rc = 0!
E/gpsone_dmn( 5088): gpsone_glue_piperemove:92] fd = -1, /data/misc/gsiff_ctrl_q
E/LocSvc_utils_ll( 5088): W/linked_list_destroy: Invalid list parameter!
F/libc ( 5088): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 5088 (gsiff_daemon)
I/DEBUG ( 263): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 263): Build fingerprint: 'Sony/D5803/D5803:4.4.4/23.0.A.2.105/lvf_Rw:user/release-keys'
I/DEBUG ( 263): Revision: '0'
I/DEBUG ( 263): ABI: 'arm'
I/DEBUG ( 263): pid: 5088, tid: 5088, name: gsiff_daemon >>> /system/bin/gsiff_daemon <<<
I/DEBUG ( 263): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
W/NativeCrashListener( 732): Couldn't find ProcessRecord for pid 5088
I/DEBUG ( 263): r0 00000008 r1 93475f55 r2 93475f55 r3 93475f55
E/DEBUG ( 263): AM write failure (32 / Broken pipe)
I/DEBUG ( 263): r4 00000008 r5 b4f539a4 r6 00000000 r7 b4f539a0
I/DEBUG ( 263): r8 00000003 r9 b6f9a098 sl 00000001 fp b6f94da0
I/DEBUG ( 263): ip b6c5dfbc sp be91f9b8 lr b6f116d1 pc b6f115b6 cpsr 600f0030
I/DEBUG ( 263):
I/DEBUG ( 263): backtrace:
I/DEBUG ( 263): #00 pc 000145b6 /system/lib/libc.so (pthread_mutex_trylock+3)
I/DEBUG ( 263): #01 pc 000146cd /system/lib/libc.so (pthread_mutex_destroy+4)
I/DEBUG ( 263): #02 pc 00002157 /system/lib/libgps.utils.so (msg_q_destroy+66)
I/DEBUG ( 263): #03 pc 00001a85 /system/bin/gsiff_daemon
I/DEBUG ( 263): #04 pc 00002af3 /system/bin/gsiff_daemon
I/DEBUG ( 263): #05 pc 0000fbb9 /system/lib/libc.so (__libc_init+44)
I/DEBUG ( 263): #06 pc 00001968 /system/bin/gsiff_daemon
I/DEBUG ( 263):
I/DEBUG ( 263): Tombstone written to: /data/tombstones/tombstone_
Camera messages:
Code:
E/cacao ( 7380): 1459692 cacao_chokoball.cpp (4914) 9002 E [CKB] ckb preCompile fail. keymgr create credmgr context.
W/cacao ( 7380): 1459761 cacao_chokoball.cpp (4923) 9002 W [CKB] Post process preLoad(0xffffff90)
E/mm-camera-sensor( 297): sony_sensor_power_up:1138,error
E/mm-camera-sensor( 297): sony_sensor_power_up:1145,error
I/Adreno-EGL( 7613): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: RGURRAM_AU_LINUX_ANDROID_LNX.LA.3.5.2.2_RB1.04.04.04.087.030+PATCH[ES]_msm8974_LNX.LA.3.5.2.2_RB1__release_ENGG ()
I/Adreno-EGL( 7613): OpenGL ES Shader Compiler Version: E031.24.00.15
I/Adreno-EGL( 7613): Build Date: 08/12/14 Tue
I/Adreno-EGL( 7613): Local Branch:
I/Adreno-EGL( 7613): Remote Branch: quic/LNX.LA.3.5.2.2_rb1
I/Adreno-EGL( 7613): Local Patches: 8b00bd16f3c1d9d35a2fa902df5e679888d2b2e3 Fixes an llvm crash with mini dEQP apk
I/Adreno-EGL( 7613): 38bad22e162dead4e008444520a0144c78a347bd Fixes a potential dEQP crash.
I/Adreno-EGL( 7613): ce345e1c45c2ae2d1fb2cb125c8d2574f1af5f95 Rev
I/OpenGLRenderer( 7613): Initialized EGL, version 1.4
D/OpenGLRenderer( 7613): Enabling debug mode 0
E/mm-camera( 297): cpp_module_set_clock_freq:1015] clk:133330000, dim:0, stream_type:0,
D/mm-camera( 297): mct_pipeline_process_set:command=800000e
E/cammw ( 7380): E: void* cammw_util_msg_cli_open(const char*, int32_t, cammw_util_msg_callbacks_t, uint32_t, cammw_any_t, uint32_t, cammw_any_t): connect err -1
E/cammw ( 7380): E: cammw_link_isp_cli_open: msg_cli_open fail
E/cammw ( 7380): E: cammw_camera_isp_create: isp create fail
E/cammw ( 7380): E: cammw_camera_open: isp socket create error
E/cammw ( 7380): E: cammw_camera_isp_destroy: invalid arg
E/cammw ( 7380): E: cammw_camera_sensor_destroy: invalid arg
E/cammw ( 7380): E: cammw_link_sensor_cli_close: invalid arg handle = 0x0
E/cammw ( 7380): E: cammw_err_t cammw_util_ashmem_free(cammw_buf_t*): Invalid Arg
E/cammw ( 7380): E: cammw_err_t cammw_util_ashmem_free(cammw_buf_t*): Invalid Arg
D/mm-camera( 297): mct_pipeline_process_set:command=800000b
D/mm-camera-sensor( 297): module_sensor_stop_session:700 session 1
E/cald ( 7380): 1463787 excal_system.cpp (221) 7891 E [EXC] Camera can't open.
E/cald ( 7380): 1463850 excal_system.cpp (447) 7891 E [EXC] system init is failed. General
E/cald ( 7380): 1463930 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: DebugMgr is not found
E/cald ( 7380): 1463984 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: BufMgr is not found
E/cald ( 7380): 1464037 excal_comp_mgr.cpp (156) 7891 E [EXC] Unregister component: DB is not found
I/cacao ( 7380): 1465315 pal.cpp (3383) 7891 I [INF] PAL_Delete
I/cald ( 7380): 1470629 cald_client.c (2051) 7891 I [INF] Cald_Client_Create
E/libcamera( 7380): failed to create Cald instance
E/libcamera( 7380): createInstance: failed startCamera
I/libcamera( 7380): HAL_openCameraHardware: X created hardware=0x0
E/CameraWrapper( 7380): vendor camera open fail
E/CameraClient( 7380): Could not open camera 0: -19
E/CameraClient( 7380): initialize: Camera 0: unable to initialize device: No such device (-19)
I/CameraClient( 7380): Destroying camera 0
D/NuPlayerDriver( 7380): reset(0xb460d040)
D/NuPlayerDriver( 7380): notifyResetComplete(0xb460d040)
D/NuPlayerDriver( 7380): reset(0xb460d1c0)
D/NuPlayerDriver( 7380): notifyResetComplete(0xb460d1c0)
W/CameraManager( 8386): Error querying camera device 0 for listing.
I/CameraService( 7380): getCameraCharacteristics: Switching to HAL1 shim implementation...
I/libcamera( 7380): HAL_getCameraInfo: E cameraId=1
I/libcamera( 7380): HAL_getCameraInfo: X
I/libcamera( 7380): HAL_getCameraInfo: E cameraId=1
I/libcamera( 7380): HAL_getCameraInfo: X
---------- Post added at 06:15 AM ---------- Previous post was at 06:06 AM ----------
Sorry, noticed a few things were out of date. in my tree. Previous post may not be correct. I'll be doing another build tonight after extracting vendor blobs and syncing properly and I'll post with more results.
Uploading new build I made with following:
I added to check for aries as well:
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c,aries
Which updates update script to:
Code:
assert(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" || getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" || getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" || getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || abort("This package is for device: D5803,D5833,z3c,aries; this device is " + getprop("ro.product.device") + "."););
nelvinchi said:
Check your build.prop in your compiled build folder (/system) and look for the variables below:
"ro.product.device" "ro.build.product"
If you want to change the values, mount your system.img, make your changes and make new .img
(PM me if you need help with this..)
Click to expand...
Click to collapse
Build prop is not the problem, consistency is.
Code:
ro.product.name=D5803
ro.build.product=z3c
ro.product.device=z3c
CM uses the above. Sony uses aries.
So I guess checking for all three, and the variation(D5833) should work in the end.
jsscx said:
it's not hard to delect the first sentence in updater-script in zip,then we could get it flashed
Click to expand...
Click to collapse
No, but that is not ideal. It should check the for the correct device.
But, the problem is that there is no consistency so I guess checking for all four should do it - D5803,D5833,z3c,aries.
Gairtial said:
Okay, did my own build using similar instructions and came up with the following issues:
libtime_genoff.so wasn't copied during the build process, manually copying required manually copying a second time after the build.
DPI was first set to 480 in build.prop. Reset it to 320 through ADB after booting and it works fine
On the first boot the modem appeared to work (connected to my network), on the second it did not. Nothing I can understand in ADB that's relevant.
Wifi appears to work properly
Camera crashes
---------- Post added at 06:15 AM ---------- Previous post was at 06:06 AM ----------
[/COLOR]Sorry, noticed a few things were out of date. in my tree. Previous post may not be correct. I'll be doing another build tonight after extracting vendor blobs and syncing properly and I'll post with more results.
Click to expand...
Click to collapse
I am not sure if I had any problems with "libtime_genoff.so", I checked the proprietary files list and it is in none of them.
The aapt was fixed in a commit, z3c.mk is now
Code:
PRODUCT_AAPT_CONFIG := normal hdpi xhdpi
PRODUCT_AAPT_PREF_CONFIG := xhdpi
And it compiled fine.
DPI also had a commit to change to 320.
So doing a repo sync should fix those previous issues.
I believe there was an issue with proprietary files as the proprietary-files.txt has been updated.
And now I have no errors when extracting files, so maybe camera files now are getting tranferred.
Review with updated changes just for z3c - http://review.cyanogenmod.org/#/q/status:merged+project:CyanogenMod/android_device_sony_z3c,n,z
Maybe a commit will be needed to fix update script as mentioned above,
Code:
# Assert
TARGET_OTA_ASSERT_DEVICE := D5803,D5833,z3c,aries
I believe there is a pull request with that specific change as well.
Thank you all for responses
Added to OP:
Mirror: AndroidFileHost
Also,
Please submit feedback.
All issues are welcome
so here's quick test:
boot with animation,when the app starting screen lasts a few seconds,then restart.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
jsscx said:
so here's quick test:
boot with animation,when the app starting screen lasts a few seconds,then restart.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
Click to expand...
Click to collapse
The name of the zip package you used will be helpful, i.e. 20141215 or 20141219
19
jsscx said:
so here's quick test:
boot with animation,when the app starting screen lasts a few seconds,then restart.
https://www.dropbox.com/s/nfexgudos3bni87/1.txt?dl=0
Click to expand...
Click to collapse
Maybe @jerpelea could help as more than one person has been encountering this issue.
jsscx said:
19
Click to expand...
Click to collapse
Uploaded new build only on AFH,
Mirror: AndroidFileHostThe repo sync includes these commits,
http://review.cyanogenmod.org/#/c/82475/
http://review.cyanogenmod.org/#/c/82465/
I can confirm the issue with the start loop.
Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off.
EDIT
- Also had to delete first line of updater script to get it to install
- The built in recovery still didn't let me install using 'apply' update, i had to use CWM 6.0.5.0 from AndroPlus Kernel to flash it
- Updater script recognized my device as 'Amami' when i don't have any reference to it in my build.prop, all value were D5803
Regards
spida_singh said:
I can confirm the issue with the start loop.
Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off.
Regards
Click to expand...
Click to collapse
I had the same problem and I could not test the rom
spida_singh said:
EDIT
- Also had to delete first line of updater script to get it to install
- The built in recovery still didn't let me install using 'apply' update, i had to use CWM 6.0.5.0 from AndroPlus Kernel to flash it
- Updater script recognized my device as 'Amami' when i don't have any reference to it in my build.prop, all value were D5803
Regards
Click to expand...
Click to collapse
Not sure why it is recognizing your device as Amami.
I added 'aries' to the assert so it should work.
I am creating zip packages using "make bacon", by default CM uses CWM so it is not surprising that you must use CWM to flash it.
As for built-in recovery, I am not sure, as it gets created automatically with the build.
Maybe changes are needed.
spida_singh said:
I can confirm the issue with the start loop.
Get a starting apps message, then reverts back to CM bootanimation, does this in a loop, hard to hard shut down phone (Volume up and Power) to get it to turn off.
Click to expand...
Click to collapse
Burakki said:
I had the same problem and I could not test the rom
Click to expand...
Click to collapse
I may have found why 'com.qualcomm.location.apk' was crashing,
It seems devs are trying to move it from 'app' to 'priv-app':
Code:
-app/com.qualcomm.location.apk:priv-app/com.qualcomm.location/com.qualcomm.location.apk
Changing 'proprietary-files.txt' from the above to
Code:
-app/com.qualcomm.location.apk
might fix that issue.
Compiling with change to see if it works.
m0d said:
It seems devs are trying to move it from 'app' to 'priv-app'
Click to expand...
Click to collapse
Any reason behind why this is trying to be done? Hasn't it always been inside app?
someone755 said:
Any reason behind why this is trying to be done? Hasn't it always been inside app?
Click to expand...
Click to collapse
No, not sure.
On Stock ROM it is located in app; however, somewhere along the line CM devs are moving it to priv-app.
The change I made does not seem to make a difference and I can not seem to find where are they moving it to priv-app
Android.mk in 'vendor/sony/shinano-common'
Code:
include $(CLEAR_VARS)
LOCAL_MODULE := com.qualcomm.location
LOCAL_MODULE_OWNER := sony
[COLOR="SeaGreen"]LOCAL_SRC_FILES := proprietary/priv-app/com.qualcomm.location/com.qualcomm.location.apk[/COLOR]
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)
LOCAL_MODULE_CLASS := APPS
LOCAL_CERTIFICATE := platform
LOCAL_PRIVILEGED_MODULE := true
include $(BUILD_PREBUILT)
And, it is being copied to: out/target/product/z3c/system/priv-app/com.qualcomm.location
I am not sure if this is of any concern, but from the logs com.qualcomm.location.apk looks like the root of the issue as everything dies after it encounters:
Code:
E/installd( 269): DexInv: --- END '/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk' --- status=0x0100, process failed
D/AndroidRuntime( 4634): Shutting down VM
E/AndroidRuntime( 4634): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
I tested it's working great..
Just a heads up! Cyanogenmod now has an official nightly for the Sony Xperia Z3 compact.
You can download their nighty builds from here:
http://download.cyanogenmod.org/?device=z3c
Hello all , this is my first tread on XDA forum , brief i have a Fujitsu Arrow F-01F (NTTDocomo) , with android 4.2.2 , no root . docomo has realeased an update to KK 4.4 , but no way to update it 'cause im outside Japan , i have downloaded tha update in a (Tar.gz) form , from spf.fmworld Dot net , i have placed the file on my External sd card , i have booted on recovery ==> update ==> i got a messsage says can't open the file . i will appreciate helping in this .
and thank you .
I'm looking for this too, I even don't know where to get the tar.gz.
Do you succeed?
If you have not found it yet: spf.fmworld.net/oss/oss/f-01f/
I'm experiencing the same problem with Fujitsu Arrows F-01F (Android 4.2.2, build V32R63C). Downloaded those two files from spf.fmworld.net (F01F_V19R43G.tar.gz and OSV-KK_F01F_V10R22A.tar.gz), put them on my external SD, booted into recovery mode and started the update. Everything I'm getting is the file open error:
----------------------
----------------------
SD Downloader
----------------------
----------------------
Device SW Downloading...
Don't Remove
the SD Card & the Battery
File Open Error.
----------------------
SD Downloading failed
----------------------
Rebooting!
It seems that the system needs another file or the filename is not correct. There's no any *.enc files in the archives and renaming doesn't work.
Have anyone figured out how to upgrade to Android 4.4?
Have tried to compile ROM from the sources of tar.gz files. Used BuilduntuVM and this manual. When calling make, it gives the error and stops:
[email protected]:~/android/kernel$ make -j4 ARCH=arm CROSS_COMPILE=arm-linux-androideabi-
CHK include/linux/version.h
CHK include/generated/utsrelease.h
/home/android/android/kernel/drivers/input/misc/Makefile:66: /home/android/android/kernel/../fjfeat/FjFeatMac.mk: No such file or directory
make[3]: *** No rule to make target '/home/android/android/kernel/../fjfeat/FjFeatMac.mk'. Stop.
scripts/Makefile.modbuiltin:54: recipe for target 'drivers/input/misc' failed
make[2]: *** [drivers/input/misc] Error 2
make[2]: *** Waiting for unfinished jobs....
scripts/Makefile.modbuiltin:54: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
make[1]: *** Waiting for unfinished jobs....
Makefile:1121: recipe for target 'drivers/modules.builtin' failed
make: *** [drivers/modules.builtin] Error 2
make: *** Waiting for unfinished jobs....
[email protected]:~/android/kernel$
Click to expand...
Click to collapse
It's obvious, that the compiler cannot find FjFeatMac.mk file. There is no fjfeat directory at all! And I have no idea where it can be obtained. Such folder or file is absent in any archive on spf.fmworld.net. So, those sources are of no use for end users as they are incomplete.
Solved the problem in the most obvious way - with sending the phone to Japan and back.
root fujitsu arrow f01f
help my plis root device fujitsu arrow f01f docomo thank
yogiesaputradewa said:
help my plis root device fujitsu arrow f01f docomo thank
Click to expand...
Click to collapse
Sadly, there's no "normal" root for F-01F. Please, take a look at this thread: https://forum.xda-developers.com/android/help/docomo-fujitsu-arrows-nx-f-01f-root-t3345350 Some very special exploit is able to give you a root but your privileges are very limited, e.g. you cannot mount system as r/w etc. You could try to talk to fi01 on github or twitter and maybe he would do something with it.
LOL i have this phone sitting for a while, finding how to upgrade the software, and then found this thread but no luck, i might throw this phone away instead sending to japan, hope there is another way someday.
mikey000 said:
LOL i have this phone sitting for a while, finding how to upgrade the software, and then found this thread but no luck, i might throw this phone away instead sending to japan, hope there is another way someday.
Click to expand...
Click to collapse
Well, until there will be real root with full rights, no way to do that. The latest official firmware for this phone is very outdated, so a custom build should be made and installed. This requires the bootloader to be unlocked.
Hi all,
I own an Japanese version of S3 (SC-06D) and I try to build my CM12.1 rom, but I had a problem at the very beginning, see the log below:
make: *** No rule to make target `/home/erio/android/aojp/out/target/product/d2dcm/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by `/home/erio/android/aojp/out/target/product/d2dcm/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Install: /home/erio/android/aojp/out/target/product/d2dcm/root/sbin/felica_init.sh
/home/erio/android/aojp/out/host/linux-x86/bin/checkpolicy: policy configuration loaded
/home/erio/android/aojp/out/host/linux-x86/bin/checkpolicy: writing binary representation (version 26) to /home/erio/android/aojp/out/target/product/d2dcm/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit
GEN /home/erio/android/aojp/out/target/product/d2dcm/obj/KERNEL_OBJ/Makefile
#
# configuration written to .config
#
make[1]: Leaving directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
make[1]: Entering directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
CHK include/linux/version.h
make[1]: Leaving directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
#### make failed to build some targets (04:37 (mm:ss)) ####
I couldn't found "/libminui_intermediates/export_includes" and "healthd_intermediates/import_includes" and it halt there. I done repo sync perfectly and no ideas on why there is such a problem. Please help.
erioho said:
Hi all,
I own an Japanese version of S3 (SC-06D) and I try to build my CM12.1 rom, but I had a problem at the very beginning, see the log below:
make: *** No rule to make target `/home/erio/android/aojp/out/target/product/d2dcm/obj/STATIC_LIBRARIES/libminui_intermediates/export_includes', needed by `/home/erio/android/aojp/out/target/product/d2dcm/obj/EXECUTABLES/healthd_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Install: /home/erio/android/aojp/out/target/product/d2dcm/root/sbin/felica_init.sh
/home/erio/android/aojp/out/host/linux-x86/bin/checkpolicy: policy configuration loaded
/home/erio/android/aojp/out/host/linux-x86/bin/checkpolicy: writing binary representation (version 26) to /home/erio/android/aojp/out/target/product/d2dcm/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit
GEN /home/erio/android/aojp/out/target/product/d2dcm/obj/KERNEL_OBJ/Makefile
#
# configuration written to .config
#
make[1]: Leaving directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
make[1]: Entering directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
CHK include/linux/version.h
make[1]: Leaving directory `/home/erio/android/aojp/kernel/samsung/d2dcm'
#### make failed to build some targets (04:37 (mm:ss)) ####
I couldn't found "/libminui_intermediates/export_includes" and "healthd_intermediates/import_includes" and it halt there. I done repo sync perfectly and no ideas on why there is such a problem. Please help.
Click to expand...
Click to collapse
Your issue is that the device is not supported by cm. So you will have to do all the legwork of getting the device trees and all the proper files. You can't use the same files for other s3 on your device.
zelendel said:
Your issue is that the device is not supported by cm. So you will have to do all the legwork of getting the device trees and all the proper files. You can't use the same files for other s3 on your device.
Click to expand...
Click to collapse
Thanks.
Once I successfully build CM12.1 on 9 July, but afterward, never success and prompt that error.
I reviewed a page on how to build for SC06D: http://lawnfield.blog.fc2.com/blog-entry-61.html
I had done all the things listed there, but finally got that error.
So, what exactly that error means and what should I do to resolve?
It seems (maybe) I solved the problem, now building but not yet complete.
From the source it use CWM as default recovery but now the code is using TWRP, so it halted. And I change it to TWRP and now running. For sure I have not much ideas on why such change in code, may be the KBC-developer intended to do, but not fully.
Another question is, If I would like to build the rom, but not all apks in /system/app, what should I do? As I would like to slim down the rom as some of the files are unnecessary to me, e.g. bootnanimation.zip and the default browser.