Hello,
Over a week ago I created a new thread in Galaxy S6 sub-forum and described my issue with it. Unfortunately there were no responses, because the sub-forum is only visited by limited number of users. I don't think my issue is device specific, so I decided to give it a go where there are more users and bigger chance for some assistance. I don't want to duplicate threads, so I would highly appreciate if you could visit the below link and see if you can help:
https://forum.xda-developers.com/galaxy-s6/help/issue-crypto-google-apps-force-close-t3793237
Short description:
All Google Apps force close, happens with custom ROMs+Opengapps and with stock Galaxy S6 ROMs. Apps that rely on encryption, e.g. Signal or Telegram won't work either, Signal displays "bad encrypted message". Looking at the logcat, this seems to be the problem:
Code:
E/AndroidRuntime(20624): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.apps.photos, sha1=24bb24c05e47e0aefa68a58a766179d9b613a600, atk=false, ver=12685023.true
E/AndroidRuntime(20624): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.android.vending, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
E/AndroidRuntime(21286): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.googlequicksearchbox, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
E/AndroidRuntime(11308): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.gm, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
W/System.err(12435): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.apps.maps, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
But it might not be the root cause and I don't know how to resolve it. I have attached more logs in the other thread and I listed what I did so far trying to fix it. Nothing helped. Please visit the linked thread for more details, I would appreciate any help.
Hello, Mistiq! Do you solve your problem?
These strings from your logcat:
New versions of the Android SDK no longer support the Crypto provider.
05-21 09:20:33.113 E/System (12113): * If your app was relying on setSeed() to derive keys from strings, you
05-21 09:20:33.113 E/System (12113): * should switch to using SecretKeySpec to load raw key bytes directly OR
05-21 09:20:33.113 E/System (12113): * use a real key derivation function (KDF). See advice here : there is must be a link, I had to delete it.
05-21 09:20:33.114 E/System (12113): Returning an instance of SecureRandom from the Crypto provider
05-21 09:20:33.114 E/System (12113): as a temporary measure so that the apps targeting earlier SDKs
05-21 09:20:33.114 E/System (12113): keep working. Please do not rely on the presence of the Crypto
05-21 09:20:33.114 E/System (12113): provider in the codebase, as our plan is to delete it
05-21 09:20:33.114 E/System (12113): completely in the future.
It seems to me that is the root of all evil
Related
When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.
Hi everyone,
I am new here on the forum, and the Streak is my very first Android phone. Just wanted to quickly say I really enjoy the community here and I like how everyone tries to help each other.
I noticed that a lot of people have been having problems with Camera forced close issues, which is what I've been experiencing as well. Please mind that this is my first Android phone, and my understanding of Linux is very limited.
I thought I'd post my findings so far in the forced close issues I've been experiencing. Here are some of what I think are the culprits behind the forced close:
Main Log:
1. First it tries to set unsupported parameters for the audio input, followed by more failed attempts to set other parameters
Code:
11-21 02:00:11.475 E/audio_input( 91): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value
11-21 02:00:11.475 E/audio_input( 91): VerifyAndSetParameter failed
2. Big Fail! It tries to load what looks to be a video encoder, and can't find it:
Code:
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.qcom.video.encoder.mpeg4 handle, try another component if available
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.PV.mpeg4enc handle, try another component if available
11-21 02:00:11.525 E/AuthorDriver( 91): Command 13 completed with error -17
11-21 02:00:11.535 E/MediaRecorder( 754): prepare failed: -17
11-21 02:00:11.535 E/videocamera( 754): prepare failed for /mnt/sdcard/DCIM/Camera/VID_20101121_020011.3gp
3. Dalvik Virtual Machine pops up an error, and throws it at Android for error handling:
Code:
11-21 02:00:11.545 F/dalvikvm( 754): Exception!!! threadid=1: thread exiting with uncaught exception (group=0x4001d7d8)
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:1297)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.access$300(VideoCamera.java:99)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:300)
Events Log:
1. Pretty straightforward -- video camera -- problem returns to android for handling during use of Media Recorder?
Code:
11-21 02:00:11.575 I/am_crash( 148): [754,com.android.camera,48709,java.io.IOException,prepare failed.,MediaRecorder.java,-2]
11-21 02:00:11.585 I/am_finish_activity( 148): [1193151496,8,com.android.camera/.VideoCamera,crashed]
11-21 02:00:11.585 I/am_pause_activity( 148): [1193151496,com.android.camera/.VideoCamera]
11-21 02:00:12.095 I/am_resume_activity( 148): [1190436808,2,com.dell.launcher/.Launcher]
System Log:
1. Same below -- start video camera, crash, Android handles the "oh no"s...
Code:
cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.android.camera/.Camera }
11-21 02:00:10.445 I/ActivityManager( 148): Starting activity: Intent { flg=0x4000000 cmp=com.android.camera/.VideoCamera (has extras) }
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
I've also attached the processes log, processesthread log, and system.prop files for reference (I removed all wifi and carrier information at the bottom of the system.prop, but I don't think it's relevant)
I think the main cause of the crash is the media recorder trying to set unsupported parameters and missing video encoder. Not sure though. Any assistance would be greatly appreciated -- I am still looking into the problems, and will get back to everyone on my findings.
Good job...Guess the codec might also be dealing with audio and the bad parm is caused by the unregistered/missing codec? [noob]
Yes - I think definitely there were some serious problems with updating it from a non-00 baseband version.
I think dependencies are missing/broken from either updating from a non 00 baseband version or the flashboot method itself. Those with 00 baseband have it easier, as they already have all the dependencies and can upgrade using the
"copy package to /sdcard/update.pkg" method.
I gave up trying to find the dependencies that were broken, instead went the "downgrading, converting to baseband 00 version and upgrading back to Froyo" method.
I've finally got everything working (including 720p recording) with a combination of Homeiss' "How To Install Official Dell 2.2 Upgrade.pkg" and Geek78's "How to go back from 21 to 00 builds" guide with a little alteration suggested by llecaroz (from modaco forum).
I think this downgrade first to Baseband 00 first than upgrade should fix all problems. The trick is to downgrade to downgrade to 1.6 that matches your baseband (21,31) first! In my case, I had a baseband 21 version.
Suggestions:
- I suggest to downgrade using Geek78's guide first (because, based on my experience, downgrading from 21 2.1 -> 00 1.6 ends up with DELL forever logo).
- If you end up with a "FOTA version error" thingy, you need to flash with a different recovery file (it changes the recovery version from 21 to 00)
- If getting "flash_image: not found" error, it means you are missing the binary. Get it from cyanogen.
Good luck with Homeiss' and Geek78's guide.
I can re-compile a more comprehensive guide, but I think I am unable to place links in here.
If you have upgraded the fastboot way (with the 3 files Stephen provided) You will have FCs on 720p recording! I have downgraded mine to 6267 and then upgraded with the pkg file! Now 720p works perfect!
Request is in the title - the LG Optimus One from Orange UK contains the Orange Signal Boost (UMA) software that would be useful to get working on other android phones with networks which support UMA. The topic is here but I've cross-posted here in case the topic gets lost in the general forum.
Here you go, This should be the original Orange V10C_00 firmware for your phone:
Code:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AORUBK/V10c_00/V10C_00.kdz
I was thinking maybe someone with the Optimus One could just backup the apk for Orange Signal Boost and post that. I have tried expanding the rom posted in the link and have got as far as the mbn files and boot.img etc but I don't know how to get at the apk's...
Bump
Could any owner of optimus one share that app with us ?
please
Again, please anyone! We just need a backup of the apk to get started!
Sent from my HTC Desire using XDA App
Ok, I managed to unpack the KDZ file but still couldn't find a way extract the Orange Signal Booster apk from boot.img file; so if anyone has backup of the apk it would be greatly appreciated.
I tried the same thing but had no luck. If you had the handset you could use a number of different apps (astro, titanium backup) to make a backup of the .apk file with very little technical knowledge.
It would be god send if we could get this app running on other handsets...
Here is the APK!
OK here is the APK which I have extracted from the ROM image. I tried installing it on my desire and it FCs as soon as I attempt to run it. If anyone else wants to get onboard with this please do!
Hi ballandbiscuit, many thanks for the APK. Tried it on my HTC DHD and had the same FC result as you. As far as I can tell, this is not a hardware restriction but possibly the result of other system services required by the app not installed on the handset.
I really wish someone from Orange with a bit of technical knowhow would get involved and assist us with this much needed feature.
what about some kind of logging? maybe it say something...
Sent from my LG-P500 using XDA App
Here is some data from logcat
Code:
I/ActivityManager( 167): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.kineto/.kineto }
I/ActivityManager( 167): Start proc com.android.kineto for activity com.android.kineto/.kineto: pid=1695 uid=10103 gids={3003, 3002, 3001, 1015}
W/dalvikvm( 1695): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/kineto/kineto;.<clinit>
W/dalvikvm( 1695): Class init failed in newInstance call (Lcom/android/kineto/kineto;)
D/AndroidRuntime( 1695): Shutting down VM
W/dalvikvm( 1695): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1695): FATAL EXCEPTION: main
E/AndroidRuntime( 1695): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1695): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 1695): at java.lang.Class.newInstance(Class.java:1429)
E/AndroidRuntime( 1695): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 1695): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
E/AndroidRuntime( 1695): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
E/AndroidRuntime( 1695): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
E/AndroidRuntime( 1695): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
E/AndroidRuntime( 1695): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1695): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1695): at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1695): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1695): Caused by: java.lang.UnsatisfiedLinkError: Library kineto not found
E/AndroidRuntime( 1695): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 1695): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 1695): at com.android.kineto.kineto.<clinit>(kineto.java:1552)
E/AndroidRuntime( 1695): ... 15 more
W/ActivityManager( 167): Force finishing activity com.android.kineto/.kineto
W/ActivityManager( 167): Activity pause timeout for HistoryRecord{46506b50 com.android.kineto/.kineto}
I/ActivityManager( 167): No longer want com.google.android.apps.uploader (pid 653): hidden #16
I/Process ( 1695): Sending signal. PID: 1695 SIG: 9
W/InputManagerService( 167): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 167): Process com.android.kineto (pid 1695) has died.
Not sure if this is relevant but earlier in the logcat...
Code:
W/PackageManager( 167): Not granting permission android.permission.DEVICE_POWER to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Not granting permission android.permission.UPDATE_DEVICE_STATS to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Unknown permission android.permission.INJECT_EVENT in package com.android.kineto
Having looked at some other posts regarding the T-Mobile US UMA app, which is also Kineto based I think it will take a lot of work to get this functioning. It appears to need some libraries such as...
libkento
linganril
librilswitch
and also some changes to the kernel as per this thread
http://forum.xda-developers.com/showthread.php?t=807116
I don't know if this was ever ported to devices other than the N1. It is shame that it requires more than just an app. Orange should be pushing this to all Android handsets. I don't use my phone at home for calls or texts because the signal is too weak, this is a loss for both myself and Orange because they don't get to charge me for calls I don't make. My wife has a Vodafone Sure Signal box which is brilliant but Orange don't offer such a device...
Okay, I just had a little luck with the UMA application.
Not quite there yet though.
BASICALLY, I have come to understand that the application extracted from various Roms FC cuz they are missing other files they depend on from the ROM.
I was using Orange Signal Boost apk from the Orange Desire S rom (am attaching it) on my HTC Legend.
Then I came across stories of someone in US who had extracted an apk from so Tmobile Rom for wifi calling and made it to work on a Nexus 1. I downloaded that files (also attached). This file was a modded version of original apk and had all the dependant files. (and consequently was 3mb vs 600kb of Orange signal boost)
So what I tried was
1. Install tmobile wifi app
2. Install Orange signal boost on TOP of it. It will ask you that this progam will replace another older program on your phone. Clcik okay.
3. What this does is leave old installed files needed from tmobile app and this time LO AND BEHOLD, signal boost app launches without FC
Here comes the problem though, it doesnt work, cuz somewhere hardcoded in the files that the tmobile app installs is the network info and naturally, our sims being orange are recognized as invalid sim.
Me and a LOT of other people would REALLY appreciate it if someone with any knowhow can look at this and figure it out for us
Can someone put this on the thread for the CM11 nightly build for Galaxy S4 i9505, unofficial I believe. I don't have the post count required. ROM is very good and works fine apart from the following issue, at least so far.
HDR won't save pictures from stock 4.4 camera app. It shows as a blank square on the gallery. Turning off HDR works fine. Logcat (first time so let me know if it's wrong and I'll do another):
--------- beginning of /dev/log/main
I/dalvikvm(16916): Enabling JNI app bug workarounds for target SDK version 11...
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
D/dalvikvm(16916): Trying to load lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
D/dalvikvm(16916): Added shared lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
I/libjackpal-androidterm(16916): JNI_OnLoad
I/Term (16916): waiting for: 16941
I/Term (16916): Subprocess exited: 129
W/IInputConnectionWrapper(16916): showStatusIcon on inactive InputConnection
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
I/Term (16916): waiting for: 17246
I/Term (16916): waiting for: 17402
If you ask me what I am saying, well I do not know, the matter is that this smartphone, Chinese, of medium to low quality and economic is known as LEAGOO Z5 LTE 37m, but here comes the strange issue, it is its processor , that on the internet, it is like mt6735, but the same device seen in flashtool is mt6737, and here the confusion begins, which is why not, for such echo with so many doubts take out the status of the aforementioned device in the context of recovery, and this is what I get,
petName=Z5
Lte
versionName=6.0-1488765164
resolution=854 * 480
versionCode=23
SDK_VERSION=23
RELEASE=6.0
Globe.REQUEST_HEADER_IMSI=748070103222388
Globe.REQUEST_HEADER_IMEI=352478081946651
BOARD=Android
BOOTLOADER=unknown
BRAND=LEAGOO
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=Z5
DISPLAY=LEAGOO Z5 Lte(37m)_OS2.0_A_20170306
FINGERPRINT=alps/full_bd6737m_35g_a_m0/bd6737m_35g_a_m0:6.0/MRA58K/1488765164:user/dev-keys
HARDWARE=mt6735
HOST=jyunspl2-PowerEdge-R720
ID=MRA58
K
IS_DEBUGGABLE=false
MANUFACTURER=LEAGOO
MODEL=Z5 Lte
PRODUCT=Z5
RADIO=unknown
SERIAL=0123456789
ABCDEF
SUPPORTED_32_BIT_ABIS=[Ljava.lang.String;@758aea8
SUPPORTED_64_BIT_ABIS=[Ljava.lang.String;@3e9bdc
1
SUPPORTED_ABIS=[Ljava.lang.String;@69cc966
TAG=Build
TAGS=dev-keys
TIME=1488765741000
TYPE=user
UNKNOWN=unknown
USER=huchao
crashTime=2018-02-07_14-33-44
STACK_TRACE=java.lang.RuntimeException:
Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings$NotificationAccessSettingsActivity}: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2576)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
... 10 more
Caused by: java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
android.app.Fragment$Instantiation
Exception: Unable to instantiate fragment com.android.settings.notification.ManagedServiceSettings$ScaryWarning
DialogFragment: make sure class name exists, is public, and has an empty constructor that is public
at android.app.Fragment.instantiate(Fragment.java:635)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
Caused by: java.lang.
InstantiationException: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
... 18 more
java.lang.Instantiation
Exception: java.lang.Class<com.android.settings.notification.ManagedServiceSettings$ScaryWarningDialogFragment>
has no zero argument constructor
at java.lang.Class.newInstance(Native Method)
at android.app.Fragment.instantiate(Fragment.java:624)
at android.app.FragmentState.instantiate(Fragment.java:111)
at android.app.FragmentManagerImpl.restoreAllState(FragmentManager.java:1885)
at android.app.FragmentController.restoreAllState(FragmentController.java:122)
at android.app.Activity.onCreate(Activity.java:927)
at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:648)
at android.app.Activity.performCreate(Activity.java:6390)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2523)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2658)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4321)
at android.app.ActivityThread.-wrap15(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5737)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:679)
the issue is, according to this info, if we go to the information collected on the internet, there is only one leagoo z5 lte 37, and this is mtk6735, therefore this device in my possession is a clone? or is it original ?, although deadly and even so the PC sometimes detects it, I do not know how to recover it with so many doubts,
with flashtool the skatter is 6737, because the skater of the 6735 gives me incorrect, although I also have an error in the 6737 when I want to flash it,
the mistake is:
ERROR: S-DL-GET-DRAM-SETTING-FAIL (0x13be)
[EMI]: Obtain DRAM Failed!
[HINT]lease check your load matches to your target which is to be downloade
I hope I have been as specific as possible to the respect
good to the geniuses of this forum I appreciate I can advise the respect, to at least recover it and know that diantres is really an abraso to all