account arrowhead-down arrowhead-up mobile-menu search sm-bold-x x-skinny-rounded x-skinny arrowhead-right social-facebook social-googleplus social-instagram social-linkedin social-pinterest social-qzone social-renren social-tencent social-twitter social-vkontakt social-weibo social-youku social-youtube

Please help us improve our website

Take our customer survey to evaluate your visit.

It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.

cancel
Showing results for 
Search instead for 
Did you mean: 
Welcome to the Open Devices community!

This is where we discuss open source and development related questions on our Open Devices initiative.

Qseecom issues, Android 6.0.1, aries

SOLVED
Talent
Message 1 of 8
6,103 Views
Message 1 of 8

Qseecom issues, Android 6.0.1, aries

I am having the following issues with qseecom

[    4.073342] QSEECOM: qseecom_probe: qseecom.qsee_version = 0x405000
[    4.079225] QSEECOM: qseecom_probe: disk-encrypt-pipe-pair=0x2
[    4.084822] QSEECOM: qseecom_probe: file-encrypt-pipe-pair=0x0QSEECOM: qseecom_probe: qsee-ce-hw-instance=0x0
[    4.094717] QSEECOM: qseecom_probe: qseecom.appsbl_qseecom_support = 0x0<6>
[    4.101422] QSEECOM: qseecom_probe: qseecom clocks handled by other subsystem
[    4.108541] QSEECOM: qseecom_probe: qsee reentrancy support phase is not defined, setting to default 0
[    4.118730] QSEECOM: qseecom_probe: secure app region addr=0x7b00000 size=0x500000
[   10.741720] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   10.747136] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   10.891228] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   10.891363] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   10.893112] init: Service 'keystore' (pid 355) exited with status 1
[   10.893128] init: Service 'keystore' (pid 355) killing any children in process group
[   10.938086] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   10.950267] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   15.171624] init: Starting service 'keystore'...
[   15.210568] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   15.215397] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   15.222195] init: Service 'keystore' (pid 1259) exited with status 1
[   15.227516] init: Service 'keystore' (pid 1259) killing any children in process group
[   20.850514] init: Starting service 'keystore'...
[   20.878225] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   20.883271] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   20.889964] init: Service 'keystore' (pid 1885) exited with status 1
[   20.895325] init: Service 'keystore' (pid 1885) killing any children in process group
[   25.211362] init: Starting service 'keystore'...
[   25.250147] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   25.259329] QSEECOM: qseecom_ioctl: Invalid IOCTL: 0xc048970f
[   25.270194] init: Service 'keystore' (pid 2069) exited with status 1
[   25.275517] init: Service 'keystore' (pid 2069) killing any children in process group
01-01 00:02:34.283   333   333 D QSEECOMD: : qseecom listener services process entry PPID = 1
01-01 00:02:34.283   333   333 D QSEECOMD: : Parent qseecom daemon process paused!! 
01-01 00:02:34.283   337   337 D QSEECOMD: : qseecom listener service threads starting!!! 
01-01 00:02:34.283   337   337 D QSEECOMD: : Total listener services to start = 2
01-01 00:02:34.283   337   337 E QSEECOMD: : Listener: index = 0, hierarchy = 1
01-01 00:02:34.293   337   337 D QSEECOMD: : Init dlopen(libdrmtime.so, RTLD_NOW) succeeds
01-01 00:02:34.293   337   337 D QSEECOMD: : Init::Init dlsym(g_FSHandle atime_start) succeeds
01-01 00:02:34.293   337   337 D QSEECOMAPI: : QSEECom_register_listener 11 sb_length = 0x5000
01-01 00:02:34.303   337   337 D QSEECOMD: : Init atime_start ret = 0
01-01 00:02:34.303   337   337 D QSEECOMD: : time services: Started (Listener ID = 11)
01-01 00:02:34.303   337   337 E QSEECOMD: : Listener: index = 1, hierarchy = 1
01-01 00:02:34.303   337   337 D QSEECOMD: : Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
01-01 00:02:34.303   337   337 D QSEECOMD: : Init::Init dlsym(g_FSHandle fs_start) succeeds
01-01 00:02:34.303   337   337 D QSEECOMAPI: : QSEECom_register_listener 10 sb_length = 0x5000
01-01 00:02:34.307   337   337 D QSEECOMD: : Init fs_start ret = 0
01-01 00:02:34.307   337   337 D QSEECOMD: : file system services: Started (Listener ID = 10)
01-01 00:02:34.316   337   337 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
01-01 00:02:34.321   337   337 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.322   337   337 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
01-01 00:02:34.465   355   355 I keystore: Found keymaster0 module Keymaster QCOM HAL, version 3
01-01 00:02:34.465   355   355 I SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 122: Creating device
01-01 00:02:34.465   355   355 D SoftKeymaster: system/keymaster/soft_keymaster_device.cpp, Line 123: Device address: 0xb6ae4000
01-01 00:02:34.466   355   355 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-01 00:02:34.466   355   355 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.466   355   355 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-01 00:02:34.466   355   355 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.466   355   355 E QCOMKeyMaster: Loading keymaster app failed
01-01 00:02:34.466   355   355 E keystore: Error opening keystore keymaster0 device.
01-01 00:02:34.466   355   355 E keystore: keystore keymaster could not be initialized; exiting
01-01 00:02:34.512   337   337 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.512   337   337 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
01-01 00:02:34.524   337   337 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.525   337   337 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
01-01 00:02:34.535   337   337 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:34.535   337   337 E QSEECOMD: : Loading keymaster app failied
01-01 00:02:34.535   337   337 D QSEECOMD: : QSEECOM DAEMON RUNNING 
01-01 00:02:38.785  1259  1259 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-01 00:02:38.790  1259  1259 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:38.790  1259  1259 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x2000
01-01 00:02:38.795  1259  1259 E QSEECOMAPI: : Error::ioctl call query if app is loaded failed with ret = -1, errno = 22
01-01 00:02:38.796  1259  1259 E QCOMKeyMaster: Loading keymaster app failed
01-01 00:02:38.796  1259  1259 E keystore: Error opening keystore keymaster0 device.
01-01 00:02:38.796  1259  1259 E keystore: keystore keymaster could not be initialized; exiting
1 ACCEPTED SOLUTION

Accepted Solutions
Regular
Message 2 of 8
10,462 Views
Message 2 of 8

Re: Qseecom issues, Android 6.0.1, aries

Hey these errors will be fixed with new blobs and a kernel patch 

Slightly smiling Face 

7 REPLIES 7
Regular
Message 2 of 8
10,463 Views
Message 2 of 8

Re: Qseecom issues, Android 6.0.1, aries

Hey these errors will be fixed with new blobs and a kernel patch 

Slightly smiling Face 

Developer World
Message 3 of 8
6,063 Views
Message 3 of 8

Re: Qseecom issues, Android 6.0.1, aries

Hi,

 

The kernel patch has been published and blobs will come today

 

Regards

Alin

 

One time poster
Message 4 of 8
5,911 Views
Message 4 of 8

Re: Qseecom issues, Android 6.0.1, aries

Would someone be so kind as to link to the git commits related to fixing this issue?

 

Thanks!

One time poster
Message 5 of 8
3,444 Views
Message 5 of 8

Re: Qseecom issues, Android 6.0.1, aries

Update 

 

Message 6 of 8
3,434 Views
Message 6 of 8

Re: Qseecom issues, Android 6.0.1, aries

can I updet my sony xperia z1 to kernel

 

Message 7 of 8
3,432 Views
Message 7 of 8

Re: Qseecom issues, Android 6.0.1, aries

but how can I got this

Developer World
Message 8 of 8
3,316 Views
Message 8 of 8

Re: Qseecom issues, Android 6.0.1, aries

Hi,

 

you can always find the latest binaries and updates on the following page:

https://developer.sonymobile.com/open-devices/

 

please update your kernel with latest patches from our kerne:

https://github.com/sonyxperiadev/kernel

 

Regards

Alin