[Q] Repeated error messages on logcat - Galaxy S 4 Q&A, Help & Troubleshooting

Guys can any of you reproduce the below logcat error?? its there from day one and i thought some custom roms might resolve it, but the error pops out ever few seconds.
Code:
05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McDaemon(2455): *** ERROR: Cannot open /system/app/mcRegistry/ffffffffd00000000000000000000004.tlbin
05-20 18:35:31.179: E/McDaemon(2455): *** Detected in mcRegistryFileGetServiceBlob/817()
05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/McClient(29224): *** ERROR: Daemon could not open session, responseId 16.
05-20 18:35:31.179: E/McClient(29224): *** Detected in mcOpenSession/387()
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 915(29224): DrValidator opening session failed: 16
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 853(29224): Error load DrValidator
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 149(29224): Error opening session
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 197(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 203(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.189: E/McClient(29224): *****************************
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 209(29224): Error during caches memory unmapping: 8
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 214(29224): Error closing session
05-20 18:35:31.199: E/ss_daemon.c, ln. 148(29224): Error cannot connect to TA/driver!

bumping

bump

No error.
Stock I9500 MDL with perseus kernel and CWM.
Sent from my GT-I9500 using xda premium

Bump

bala_gamer said:
Guys can any of you reproduce the below logcat error?? its there from day one and i thought some custom roms might resolve it, but the error pops out ever few seconds.
Code:
05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McDaemon(2455): *** ERROR: Cannot open /system/app/mcRegistry/ffffffffd00000000000000000000004.tlbin
05-20 18:35:31.179: E/McDaemon(2455): *** Detected in mcRegistryFileGetServiceBlob/817()
05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/McClient(29224): *** ERROR: Daemon could not open session, responseId 16.
05-20 18:35:31.179: E/McClient(29224): *** Detected in mcOpenSession/387()
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 915(29224): DrValidator opening session failed: 16
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 853(29224): Error load DrValidator
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 149(29224): Error opening session
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 197(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 203(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.189: E/McClient(29224): *****************************
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 209(29224): Error during caches memory unmapping: 8
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 214(29224): Error closing session
05-20 18:35:31.199: E/ss_daemon.c, ln. 148(29224): Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Hi bala.
Yep im getting the error message on bmea build rom.
I was going to delete the mcRegistry to see if the error went away. But just not had the time yet.
Optimal
Sent from my GT-I9505

get the same errors with FoxHound 0.6 (MF4) on Adam Kernel 1.4
would be cool if we could clarify it

i have investigated a little bit about the error messages.
as far as i can tell it is caused by the MobiCore Module wich is a Secured Mobile VPN for android.
i think it is used for all type of secure mobile payment options like nfc payment.
afaik there is a problem with nfc payment and custom roms (especially deodexed ones).
i dont have enough knowledge about the circumstances why it causes problems but i think it is something security related and that it is also the reason why the MobiCore Module does not load properly.
If this is the fact then someone with properly working nfc payment should not have this error messages in his logcat.
(it would be cool if someone could confirm this).
Maybe someone with more technical background can bring some light into this discussion.
sources:
MobiCore® Secured Mobile VPN for Android PDF
git googlesource of the mobicore module on the exynos platform with the code displaying the error ("Could not initialize MobiCore!")
MobiCoreDriverDaemon.cpp

clonednull said:
i have investigated a little bit about the error messages.
as far as i can tell it is caused by the MobiCore Module wich is a Secured Mobile VPN for android.
i think it is used for all type of secure mobile payment options like nfc payment.
afaik there is a problem with nfc payment and custom roms (especially deodexed ones).
i dont have enough knowledge about the circumstances why it causes problems but i think it is something security related and that it is also the reason why the MobiCore Module does not load properly.
If this is the fact then someone with properly working nfc payment should not have this error messages in his logcat.
(it would be cool if someone could confirm this).
Maybe someone with more technical background can bring some light into this discussion.
sources:
MobiCore® Secured Mobile VPN for Android PDF
git googlesource of the mobicore module on the exynos platform with the code displaying the error ("Could not initialize MobiCore!")
MobiCoreDriverDaemon.cpp
Click to expand...
Click to collapse
Hi clonednull.
See my previous post on nfc payment which relates to this. As I have been doing some investigation.
http://forum.xda-developers.com/showthread.php?p=42825999
Nfc payment will not work on deodex rom because of signature checks and looking for particular odex files and odex framework files.
Optimal
Sent from my GT-I9505

OptimalKiller said:
Hi clonednull.
See my previous post on nfc payment which relates to this. As I have been doing some investigation.
http://forum.xda-developers.com/showthread.php?p=42825999
Nfc payment will not work on deodex rom because of signature checks and looking for particular odex files and odex framework files.
Optimal
Sent from my GT-I9505
Click to expand...
Click to collapse
Thanks Optimal for bringing this up. I could imagine the MobiCore module also fails to load because of such security circumstances. As a VPN for payment transactions it would make sense.

I too am getting a very similar error. However, mine is this
Code:
E/QcrilMsgTunnelSocket( 2677): IOExceptionjava.io.IOException: No such file or d
irectoryReason: No such file or directory
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: open failed with "Permission denied"(errno 13)
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Kernel/CKMod.cpp:7
9/open()
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: Could not initialize MobiCore!
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Daemon/MobiCoreDri
verDaemon.cpp:133/run()
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: Exiting MobiCoreDaemon
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Daemon/MobiCoreDri
verDaemon.cpp:951/main()
E/McDaemon( 6149): *****************************
Have we found a solution/fix yet?

the error is there on almost all roms custom/stock .

bala_gamer said:
the error is there on almost all roms custom/stock .
Click to expand...
Click to collapse
I was able to fix it. There is a service that is being ran from the kernel. Can be disabled from either the init.rc or deleting renaming,
Mobicore-presetup.sh
Mobicore-startup.sh
Under directory /system/bin
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
I was able to fix it. There is a service that is being ran from the kernel. Can be disabled from either the init.rc or deleting renaming,
Mobicore-presetup.sh
Mobicore-startup.sh
Under directory /system/bin
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
great to see a working solution finally, does it have any other impact?

bala_gamer said:
great to see a working solution finally, does it have any other impact?
Click to expand...
Click to collapse
Nothing that I can see. Everything is still fully functional!
Sent from my SGH-M919 using Tapatalk 2

Ok folks.
Can someone test this if they have not deleted the .sh scripts.
Currently I am not getting any errors on my phone.
Can someone who is currently getting the errors go into the following folder /system/app/mcRegistry/
And let me know if they have any files inside that folder.
Optimal
Sent from my GT-I9505

OptimalKiller said:
Ok folks.
Can someone test this if they have not deleted the .sh scripts.
Currently I am not getting any errors on my phone.
Can someone who is currently getting the errors go into the following folder /system/app/mcRegistry/
And let me know if they have any files inside that folder.
Optimal
Sent from my GT-I9505
Click to expand...
Click to collapse
i'm getting the error (running Foxhound 0.9) and this is the content of my "mcRegistry" folder:
Code:
[email protected]:/system/app/mcRegistry # ls -l
ls -l
-rw-r--r-- 1 system system 9929 Aug 1 2008 07010000000000000000000000000000.tlbin
-rw-r--r-- 1 root root 5001 Aug 1 2008 FFFFFFFF000000000000000000000001.drbin
-rw-r--r-- 1 system system 17821 Aug 1 2008 ffffffff000000000000000000000004.tlbin
-rw-r--r-- 1 system system 48317 Aug 1 2008 ffffffff000000000000000000000005.tlbin
-rw-r--r-- 1 system system 42973 Aug 1 2008 ffffffff000000000000000000000008.tlbin
-rw-r--r-- 1 system system 109773 Aug 1 2008 ffffffff000000000000000000000009.tlbin
-rw-r--r-- 1 system system 50893 Aug 1 2008 ffffffffd00000000000000000000004.tlbin
this are the links generated by the .sh scripts

clonednull said:
i'm getting the error (running Foxhound 0.9) and this is the content of my "mcRegistry" folder:
Code:
[email protected]:/system/app/mcRegistry # ls -l
ls -l
-rw-r--r-- 1 system system 9929 Aug 1 2008 07010000000000000000000000000000.tlbin
-rw-r--r-- 1 root root 5001 Aug 1 2008 FFFFFFFF000000000000000000000001.drbin
-rw-r--r-- 1 system system 17821 Aug 1 2008 ffffffff000000000000000000000004.tlbin
-rw-r--r-- 1 system system 48317 Aug 1 2008 ffffffff000000000000000000000005.tlbin
-rw-r--r-- 1 system system 42973 Aug 1 2008 ffffffff000000000000000000000008.tlbin
-rw-r--r-- 1 system system 109773 Aug 1 2008 ffffffff000000000000000000000009.tlbin
-rw-r--r-- 1 system system 50893 Aug 1 2008 ffffffffd00000000000000000000004.tlbin
this are the links generated by the .sh scripts
Click to expand...
Click to collapse
Counts that idea out last time I remember getting those errors. My files was missing from that folder.
I thought it might have been those files causing that particular error.
Been trying to get the error again. But im defo not getting them at the moment.
Optimal
Sent from my GT-I9505

Just noticed these errors as well on my I337 running FoxHound .9 and a quick Google search brought me back here.
My log cat is just continuously streaming data with that error mixed in.
Does everybody's log write so fast when phone is doing nothing else that you can't even keep up or read it without pausing? Makes me worried about how much is running in the background when I try to keep my phone as streamlined as possible as is.

elesbb said:
I was able to fix it. There is a service that is being ran from the kernel. Can be disabled from either the init.rc or deleting renaming,
Mobicore-presetup.sh
Mobicore-startup.sh
Under directory /system/bin
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
just searched for those files and shockinly those files are not there in system/bin in wanam mf8 based rom

Related

[Q] Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE

I was working on an app and after I uploaded a *.ttf to the assets folder I went to run my app in the android emulator. It uploaded okay but during installation I got
[2011-08-03 14:36:37 - katastroapp] Installing katastroapp.apk...
[2011-08-03 14:36:40 - katastroapp] Installation error: INSTALL_FAILED_INSUFFICIENT_STORAGE
[2011-08-03 14:36:40 - katastroapp] Please check logcat output for more details.
[2011-08-03 14:36:41 - katastroapp] Launch canceled!
Here is my logcat
08-03 21:34:12.316: DEBUG/SntpClient(59): request time failed: java.net.SocketException: Address family not supported by protocol
08-03 21:36:37.893: DEBUG/AndroidRuntime(395): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
08-03 21:36:37.893: DEBUG/AndroidRuntime(395): CheckJNI is ON
08-03 21:36:38.183: DEBUG/AndroidRuntime(395): --- registering native functions ---
08-03 21:36:39.613: DEBUG/dalvikvm(247): GC_EXPLICIT freed 158 objects / 7584 bytes in 80ms
08-03 21:36:39.793: DEBUG/dalvikvm(59): GC_EXPLICIT freed 1624 objects / 73120 bytes in 145ms
08-03 21:36:39.904: DEBUG/AndroidRuntime(395): Shutting down VM
08-03 21:36:39.904: DEBUG/dalvikvm(395): Debugger has detached; object registry had 1 entries
08-03 21:36:39.943: INFO/AndroidRuntime(395): NOTE: attach of thread 'Binder Thread #3' failed
08-03 21:39:12.383: DEBUG/SntpClient(59): request time failed: java.net.SocketException: Address family not supported by protocol
If anyone knows whats up with that I would be greatly helped.
I figured it out, I just didnt give my emulator enough memory. stupid easy fix.

[Help] Port jelly bean

hello all
i tried port jb to wildfire
but touch screen not work, i don't know, i try use my devices idc
can somebody help me?
This is logcat
KoolSavas95 said:
Did u replaced all hw folders in lib folder? Maybe need to edit framework.jar
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
i will try
I think there are some permissions missing also from etc/permissions
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.contacts
W/PackageManager( 316): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.calendar
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cl in package com.android.providers.calendar
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.mail in package com.android.calendar
W/PackageManager( 316): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.providers.contacts
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.cp in package com.android.providers.contacts
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.settings
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES in package com.android.development
W/PackageManager( 316): Unknown permission com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser in package com.android.development
W/PackageManager( 316): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
Click to expand...
Click to collapse
deba1994 said:
I think there are some permissions missing also from etc/permissions
Click to expand...
Click to collapse
oh no,it is not related to touch screen
it here:
Code:
D/EventHub( 316): No input device configuration file found for device 'compass'.
D/EventHub( 316): No input device configuration file found for device 'curcial-oj'.
I/SystemServer( 316): Bluetooth Service
I/EventHub( 316): New device: id=2, fd=105, path='/dev/input/event6', name='curcial-oj', classes=0x9, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'lightsensor-level'.
D/EventHub( 316): No input device configuration file found for device 'buzz-keypad'.
I/EventHub( 316): New device: id=5, fd=107, path='/dev/input/event3', name='buzz-keypad', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/buzz-keypad.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=true, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'proximity'.
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_START
E/filemap ( 316): mmap(0,4096) failed: No such device
E/OMXCodec( 109): mediacodec list instance returned NULL
E/AudioCache( 109): Error 1, -2147483648 occurred
E/SoundPool( 316): Unable to load sample: (null)
I/EventHub( 316): New device: id=7, fd=108, path='/dev/input/event1', name='atmel-touchscreen', classes=0x55, configuration='/system/usr/idc/atmel-touchscreen.idc', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/EventHub( 316): No input device configuration file found for device 'h2w headset'.
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/EventHub( 316): New device: id=8, fd=98, path='/dev/input/event0', name='h2w headset', classes=0x1, configuration='', keyLayout='/system/usr/keylayout/h2w_headset.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=false
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/BluetoothProfileState( 316): Message:Entering Stable State
I/InputReader( 316): Device added: id=-1, name='Virtual', sources=0x00000301
I/InputReader( 316): Device added: id=8, name='h2w headset', sources=0x00000101
I/InputReader( 316): Touch device 'atmel-touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.
I/InputReader( 316): Device added: id=7, name='atmel-touchscreen', sources=0x00001503
I/InputReader( 316): Device added: id=0, name='buzz-keypad', sources=0x00000101
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 113): HRET = AKSC_HOF_DSS_REQUEST
I/InputReader( 316): Device added: id=2, name='curcial-oj', sources=0x00002103
E/Trace ( 316): error opening trace file: No such file or directory (2)
Code:
I/SystemServer( 316): Accessibility Manager
I/InputReader( 316): Reconfiguring input devices. changes=0x00000004
I/InputReader( 316): Device reconfigured: id=7, name='atmel-touchscreen', surface size is now 240x320, mode is 1
I/ActivityManager( 316): Config changed: {1.0 0mcc0mnc en_US sw320dp w320dp h401dp smll port ?uimode ?night finger -keyb/h/h -nav/h s.2}
Ok i'm not that good at this but will try to help....how did you port JB??did you compile from source?
i try port jb of heroc here
i port it by replace my zImage and ramdisk
I think u could try porting from here
and i think as koolsavas95 said..u may need to replace your hw folder in lib with what i am not sure....maybe u can try to use ics build as base ?
EDIT : that last mediafire link that i attached was wrong..sry dont download that !!!
thank you, deba1994
i will try
Best of luck and maybe if you are good at compiling u can maybe contact that x10 mini dev for help
tathanhlam66 said:
hello all
i tried port jb to wildfire
but touch screen not work, i don't know, i try use my devices idc
can somebody help me?
This is logcat
Click to expand...
Click to collapse
Any luck with the port?
I can not port it
my kernel does not work touch screen
If you are able to fix compiling errors you can try to build jb from source, just use sympnotic github: repo init -u git://github.com/sympnotic/android.git -b jellybean
I've tried to build from here but i got errors while compiling and i'm not able to solve them
I am downloading and compiling now from sympnotic. Let u know if it works
edit:
I could get past the bionic error, but the egl and external packads error are too much. Will try another time again.
*delete*

[Q] [L7] [DEV] V20a Kernel Build problems

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.

[Q] Cherry-Picking help

I want to cherry-pick "custom notification led settings" from purity to my aosp build.
So I went ahead and picked up these two commits
https://github.com/KitKatPurity/pla...mmit/c85834ed460ec99e0752f1f13e58cad74abf844e
and
https://github.com/KitKatPurity/pla...mmit/b37fdf4238b11b0232b12f218294131ea77ec309
The framework part ran well and there was no conflict. The settings part returned a small conflict which I solved myself. Now as I go on compiling, everything compiled good but then at the time of Settings.apk compiling it returned this error.
Code:
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:119: cannot find symbol
symbol : class DisplayManager
location: class com.android.settings.DisplaySettings
mDisplayManager = (DisplayManager)getActivity().getSystemService(
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:121: cannot find symbol
symbol : variable mDisplayManager
location: class com.android.settings.DisplaySettings
mWifiDisplayStatus = mDisplayManager.getWifiDisplayStatus();
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:122: cannot find symbol
symbol : variable KEY_WIFI_DISPLAY
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = (Preference)findPreference(KEY_WIFI_DISPLAY);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:123: cannot find symbol
symbol : variable mWifiDisplayStatus
location: class com.android.settings.DisplaySettings
if (mWifiDisplayStatus.getFeatureState()
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:124: cannot find symbol
symbol : variable WifiDisplayStatus
location: class com.android.settings.DisplaySettings
== WifiDisplayStatus.FEATURE_STATE_UNAVAILABLE) {
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:125: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
getPreferenceScreen().removePreference(mWifiDisplayPreference);
^
packages/apps/Settings/src/com/android/settings/DisplaySettings.java:126: cannot find symbol
symbol : variable mWifiDisplayPreference
location: class com.android.settings.DisplaySettings
mWifiDisplayPreference = null;
^
packages/apps/Settings/src/com/android/settings/purity/notificationlight/ApplicationLightPreference.java:170: method does not override or implement a method from a supertype
@Override
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
11 errors
make: *** [out/target/common/obj/APPS/Settings_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
Here are the link of the 2 files where the error is shown:
ApplicationLightPreference.java
DisplaySettings.java
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.
Since this is a question why not post in the section clearly marked for questions??
Sent from my Nexus 4 using xda premium
brajesh.sharma87 said:
I tried the following combination to solve it:
in ApplicationLightPreference.java, I deleted the line which returned the error.
in DisplaySettings.java I deleted the line which returned the error.
The build compiles fine, boot fines but but when I select display settings, it force closes.
Any help in solving this error is appreciated.
Click to expand...
Click to collapse
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.
MBQ_ said:
Find the commit that added the missing variable(s) and method(s)
pull a log for the force close.
Click to expand...
Click to collapse
Not sure what to do about the first line but here's the log
Code:
I/ActivityManager( 647): Displayed com.android.settings/.Settings: +631ms
I/ActivityManager( 647): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 9823
D/audio_hw_primary( 170): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/ACDB-LOADER( 170): ACDB -> send_afe_cal
D/SubSettings( 9823): Launching fragment com.android.settings.DisplaySettings
D/AndroidRuntime( 9823): Shutting down VM
W/dalvikvm( 9823): threadid=1: thread exiting with uncaught exception (group=0x415adba8)
E/AndroidRuntime( 9823): FATAL EXCEPTION: main
E/AndroidRuntime( 9823): Process: com.android.settings, PID: 9823
E/AndroidRuntime( 9823): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2195)
E/AndroidRuntime( 9823): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
E/AndroidRuntime( 9823): at android.app.ActivityThread.access$800(ActivityThread.java:135)
E/AndroidRuntime( 9823): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
E/AndroidRuntime( 9823): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 9823): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 9823): at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 9823): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 9823): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 9823): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 9823): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 9823): at com.android.settings.DisplaySettings.onCreate(DisplaySettings.java:134)
E/AndroidRuntime( 9823): at android.app.Fragment.performCreate(Fragment.java:1678)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:859)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062)
E/AndroidRuntime( 9823): at android.app.BackStackRecord.run(BackStackRecord.java:684)
E/AndroidRuntime( 9823): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1447)
E/AndroidRuntime( 9823): at android.app.Activity.performStart(Activity.java:5240)
E/AndroidRuntime( 9823): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2168)
E/AndroidRuntime( 9823): ... 11 more
W/ActivityManager( 647): Force finishing activity com.android.settings/.SubSettings
W/ActivityManager( 647): Force finishing activity com.android.settings/.Settings
W/ActivityManager( 647): Activity pause timeout for ActivityRecord{41e72210 u0 com.android.settings/.SubSettings t14 f}
W/Sidekick_LocationOracleImpl( 2543): Best location was null
I/Process ( 9823): Sending signal. PID: 9823 SIG: 9
V/SearchControllerCache( 2543): creating SearchController
W/Sidekick_LocationOracleImpl( 2543): Best location was null
W/GCoreFlp( 8127): No location to return for getLastLocation()
I/ActivityManager( 647): Process com.android.settings (pid 9823) has died.
I/WindowState( 647): WIN DEATH: Window{419b9318 u0 com.android.settings/com.android.settings.Settings}
D/dalvikvm( 2543): GC_FOR_ALLOC freed 1110K, 57% free 5133K/11704K, paused 27ms, total 27ms
I/MicroHotwordRecognitionRunner( 2543): Starting hotword detection.
D/audio_hw_primary( 170): select_devices: out_snd_device(0: ) in_snd_device(34: voice-rec-mic)
E/ACDB-LOADER( 170): Error: ACDB AudProc vol returned = -8
D/dalvikvm( 2543): GC_CONCURRENT freed 6K, 51% free 5756K/11704K, paused 2ms+3ms, total 32ms
I/SearchController( 2543): #onHotwordDetectorStarted
brajesh.sharma87 said:
Not sure what to do about the first line but here's the log
Click to expand...
Click to collapse
Something is wrong in the onCreate method of DisplaySettings.java
Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo
GeyerA said:
Hi, I checked and you miss the declaration in the Android Manifest in the packages_apps_settings. Go and check my Github commits. You do not need the modifcation in the proguard.flags though.
https://github.com/GeyerA/platform_...mmit/347e74714f0c6efa2dbd3ba49b5612e1cc11bf4f
For completeness also check the commits in the frameworks_base
https://github.com/GeyerA/platform_frameworks_base/commit/a77810164cb1bcb1d449f603f31a97939d9f9b3b
Also, make sure you got these...
https://github.com/PSX-PureSpeed/an...mmit/3e29b10a377f0985ee221aaa4fe10838733ed3df
https://github.com/PSX-PureSpeed/an...mmit/2ae7fbb6134f6831fba8184d0dd1092f5bee1f7a
This should fix your issues, just let me know or PM me as I am not always checking on your thread.
Nice week to everbody. Calo
Click to expand...
Click to collapse
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.
brajesh.sharma87 said:
Thanks for the answer. I discarded all the commits which I took from purity.
Started fresh and picked up the commits from your github. There was 1 conflict in DisplaySettings.java, I solved it and compiled. It then gave me error during compile about volume wake. I deleted those lines in question and compiled again. It compiled fine but after installing the output rom I still got FC when clicking on "Display Settings".
I didn't give up. I discarded all the previous commits again and this time picked up the volume wake commits first and then the LED customization commits and then from PSX commits which you advised. Everything ran well, there was not a single conflict this time. Even there was no error at the time of compilation. BUT as always on installing the rom I got the same FC on clicking Display settings.
Now I have deleted the entire out directory and this time will build fresh lets see if that can help, but for that I can only do it after 8-10 days as I am going out of station.
Thanks for all the help.
Click to expand...
Click to collapse
Hello, good that you have some progress although you might feel disappointed that it does not work. Here is one reason why I personally do not cherry-pick complex commits as it will also add the lines which are not part of that commit but part of my code.
Anyhow, I believe you missed one small thing which is in android_device_hammerhead. Sorry I forgot that one.
https://github.com/KitKatPurity/pla...mmit/217378d3e6a7a5370e7c1583fcfb4ae1e7a9ac7c
Especially this one in overlay/frameworks/base/core/res/res/values/config.xml
Code:
+ <!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
+ <bool name="config_intrusiveBatteryLed">true</bool>
+
+ <!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
+ <bool name="config_multiColorBatteryLed">true</bool>
+
I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:
GeyerA said:
........I am sure it will work then. Please do not delete everything again when something does not work, post the question first :silly:
Click to expand...
Click to collapse
Thanks but as i said, i wont have access to my laptop for next 8-10 days, will continue once i come back.
Sent from my Nexus 4 using Tapatalk
@GeyerA you're a genius. I've been working on this for last 1 month and finally succeeded.
As I didnt have access to my laptop and the resolution that u you gave was also possible through apk tool, I sent the framework-res.apk to a friend and asked him to just change those two values to 'true' he did so and sent the same to me and boom it worked. Thank you so very much.
Sent from my Nexus 4 using Tapatalk
Hello. I am happy to hear; great satisfaction that I could help. But the credit is Dario's from Kitkatpurity and Martin_Ro's from PSX. They helped me a lot and I suffered much more than you. No biggie but please use the thanks button ....
Sent from my AOSP on HammerHead using xda app-developers app

Camera FC in Android 9 PIE Roms

I have been facing Camera Fc's in almost all PIE Roms randomly after a reboot.
It happens randomly after rebooting the phone. In some ROMs it happens after two or three reboots, I am attaching the link of the log file
time: 1551073148867
msg: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2953)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3088)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1818)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6739)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$AndroidCameraDeviceInfo.getCharacteristics(AndroidCameraAgentImpl.java:176)
at com.android.camera.app.CameraController.getCharacteristics(CameraController.java:112)
at com.android.camera.CaptureModule.getFacingFromCameraId(CaptureModule.java:1542)
at com.android.camera.CaptureModule.init(CaptureModule.java:415)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1627)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:114)
at android.app.Activity.performCreate(Activity.java:7145)
at android.app.Activity.performCreate(Activity.java:7136)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2933)
... 11 more
I am new and therefore could not post url here.
Kindly look into this issue
ZABCXYZ said:
I have been facing Camera Fc's in almost all PIE Roms randomly after a reboot.
It happens randomly after rebooting the phone. In some ROMs it happens after two or three reboots, I am attaching the link of the log file
time: 1551073148867
msg: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2953)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3088)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1818)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6739)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$AndroidCameraDeviceInfo.getCharacteristics(AndroidCameraAgentImpl.java:176)
at com.android.camera.app.CameraController.getCharacteristics(CameraController.java:112)
at com.android.camera.CaptureModule.getFacingFromCameraId(CaptureModule.java:1542)
at com.android.camera.CaptureModule.init(CaptureModule.java:415)
at com.android.camera.CameraActivity.onCreateTasks(CameraActivity.java:1627)
at com.android.camera.util.QuickActivity.onCreate(QuickActivity.java:114)
at android.app.Activity.performCreate(Activity.java:7145)
at android.app.Activity.performCreate(Activity.java:7136)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1272)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2933)
... 11 more
I am new and therefore could not post url here.
Kindly look into this issue
Click to expand...
Click to collapse
U partitions are encrypted . Do format data. Then camera will work.
Format data command decrypts and erases the data and internal sd partition.
Go to twrp
Format data
Type Yes to format.
Reboot

Categories

Resources