I'm getting a weird error using the Aviary SDK for some users who are using ART. I'm confused on why this happening (only on 4.4.x obviously) as the app works perfectly when calling this SDK on Dalvik. Any one have any have any ideas to solve this? Aviary claims it's PhoneGap/Cordova issue (our base), but I don't think that's the issue here as it only fires when the activity is launched.
HTML:
06-06 09:45:36.037: D/Aviary(27701): Pictures folder: /storage/emulated/0/Pictures
06-06 09:45:36.037: D/Aviary(27701): show
06-06 09:45:36.037: D/Aviary(27701): VERSION => 3.0.4
06-06 09:45:36.037: D/Aviary(27701): VERSION => 157
06-06 09:45:36.041: I/ActivityManager(741): START u0 {dat=file:///storage/emulated/0/DCIM/Camera/1402062335694.jpg cmp=com.XXXX.app/com.aviary.android.feather.FeatherActivity (has extras)} from pid 27701
06-06 09:45:36.054: W/CursorWrapperInner(27701): Cursor finalized without prior close()
06-06 09:45:36.058: I/CordovaLog(27701): Changing log level to ERROR(6)
06-06 09:45:36.087: I/ActivityManager(741): Start proc com.XXXX.app:standalone for activity com.XXXX.app/com.aviary.android.feather.FeatherActivity: pid=28285 uid=10060 gids={50060, 3003, 1028, 1015}
06-06 16:20:12.473 W/art (188): Could not get current activity
......
06-06 09:45:36.320: E/art(28285): Verification failed on class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler in /data/app/com.XXXXXXX.apk because: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider)
06-06 09:45:36.320: E/AndroidRuntime(28285): FATAL EXCEPTION: SessionHandler
06-06 09:45:36.320: E/AndroidRuntime(28285): Process: com.XXXXX.app:standalone, PID: 28285
06-06 09:45:36.320: E/AndroidRuntime(28285): java.lang.VerifyError: Verifier rejected class com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler due to bad method void com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler.deleteBlobsAndSessions(com.aviary.android.feather.library.external.tracking.LocalyticsProvider) (declaration of 'com.aviary.android.feather.library.external.tracking.LocalyticsSession$UploadHandler' appears in /data/app/com.XXXXXXX.apk)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.init(LocalyticsSession.java:1427)
06-06 09:45:36.320: E/AndroidRuntime(28285): at com.aviary.android.feather.library.external.tracking.LocalyticsSession$SessionHandler.handleMessage(LocalyticsSession.java:1124)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Handler.dispatchMessage(Handler.java:102)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.Looper.loop(Looper.java:136)
06-06 09:45:36.320: E/AndroidRuntime(28285): at android.os.HandlerThread.run(HandlerThread.java:61)
06-06 09:45:36.320: W/ActivityManager(741): Force finishing activity com.XXXXXX.app/com.aviary.android.feather.FeatherActivity
First, some information about the device:
1. Samsung Galaxy S5 from TMobile
2. Has Lollipop installed (from OTA update)
3. Factory ROM, not rooted, bootloader still locked, no modifications whatsoever.
For some reason I am getting the "Unfortunately, Phone has stopped" popup continuously. This occurs from the moment I boot up (at lockscreen) and as soon as I press "OK", it comes up about 0.2 seconds later. Makes it very difficult to navigate the device menus.
I have looked at logcats and this exception is what occurs:
Code:
I/Telecom (10435): Call: CallerInfo received for ****: [email protected] { name null, phoneNumber non-null }
I/Telecom (10435): MissedCallNotifier: showMissedCallNotification
D/ScoverManager(10435): serviceVersion : 16908288
D/EcidContact(10435): ECID AOSP VERSION: 2.3.6
D/AndroidRuntime(10435): Shutting down VM
E/AndroidRuntime(10435): FATAL EXCEPTION: main
E/AndroidRuntime(10435): Process: com.android.server.telecom, PID: 10435
E/AndroidRuntime(10435): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime(10435): at com.android.server.telecom.secutils.TelecomUtils.getPresentationString(TelecomUtils.java:2917)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier.showMissedCallNotification(MissedCallNotifier.java:191)
E/AndroidRuntime(10435): at com.android.server.telecom.MissedCallNotifier$3$1.onCallerInfoChanged(MissedCallNotifier.java:617)
E/AndroidRuntime(10435): at com.android.server.telecom.Call.access$000(Call.java:74)
E/AndroidRuntime(10435): at com.android.server.telecom.Call$1.onQueryComplete(Call.java:165)
E/AndroidRuntime(10435): at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler.onQueryComplete(CallerInfoAsyncQuery.java:343)
E/AndroidRuntime(10435): at android.content.AsyncQueryHandler.handleMessage(AsyncQueryHandler.java:344)
E/AndroidRuntime(10435): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(10435): at android.os.Looper.loop(Looper.java:145)
E/AndroidRuntime(10435): at android.app.ActivityThread.main(ActivityThread.java:5837)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(10435): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1388)
E/AndroidRuntime(10435): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1183)
V/ApplicationPolicy( 783): isApplicationStateBlocked userId 0 pkgname com.android.server.telecom
W/ActivityManager( 783): Process com.android.server.telecom has crashed too many times: killing!
I/dumpstate(10454): begin
D/StatusBarManagerService( 783): manageDisableList userId=0 what=0x0 pkg=WindowManager.LayoutParams
D/CrashAnrDetector( 783): processName: com.android.server.telecom
D/CrashAnrDetector( 783): broadcastEvent : com.android.server.telecom system_app_crash
W/ContextImpl( 783): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1701 com.android.server.analytics.data.collection.application.CrashAnrDetector.broadcastEvent:296 com.android.server.analytics.data.collection.application.CrashAnrDetector.processDropBoxEntry:254 com.android.server.analytics.data.collection.application.CrashAnrDetector.access$100:60 com.android.server.analytics.data.collection.application.CrashAnrDetector$1.onReceive:102
I/SurfaceFlinger( 245): id=21 createSurf (49x49),1 flag=4, Application Error: com.android.server.telecom
I/OpenGLRenderer( 783): Initialized EGL, version 1.4
I/OpenGLRenderer( 783): HWUI protection enabled for context , &this =0x9de366f0 ,&mEglDisplay = 1 , &mEglConfig = 8
E/android.os.Debug( 783): [email protected] > sdumpstate -k -t -z -d -o /data/log/dumpstate_app_error
I/ServiceManager( 345): Waiting for service AtCmdFwd...
D/PowerManagerService( 783): [input device light] handleInputDeviceLightOff
It seems to have something to do with telecom. I have removed the SIM card, SD card, etc. No difference. I have tried clearing app data for contacts, contacts storage, phone app, even "com.android.server.telecom" from ADB SHELL PM CLEAR command, but no change.
Does anyone know what the issue could be? What can I try to do (besides factory reset of course) to fix the issue? Thanks in advance. I can post more logcats if needed.
There are numerous bugs with system apps crashing with lolipop on the S5. My contacts app is constantly crashing, vzw, OTA.
Ended up doing a factory reset, which fixed the issue
I really didn't want to factory reset ?
You need to factory reset after upgrading from KK to LP
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Android.Addiction said:
Ended up doing a factory reset, which fixed the issue
Click to expand...
Click to collapse
Android.Addiction said:
That's more of a personal preference. I've seen tons of upgrades on this phone that went fine.
Click to expand...
Click to collapse
___________________
Hi!
I use a google-free Omnirom on my Xperia X. There are 2 apps, both from f-droid, that crash the device to reboot. They work with Lineage on an other device. The apps are osmand, which generates an exceptionlog, and usbmountr.
Does any OR dev like to examine this? If yes, what files will I have to post? Maybe debugging it live in irc or jabber? I don't know, if this is a general OR problem, or a problem with the 64bit system.
Here is what osmand logs:
Code:
07.08.2017 8:32:35
Exception occured in thread Thread[main,5,main] :
java.lang.RuntimeException: Unable to resume activity {net.osmand.plus/net.osmand.plus.activities.MapActivity}: java.lang.RuntimeException: android.os.DeadSystemException
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3445)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3485)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2748)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1489)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6171)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
Caused by: java.lang.RuntimeException: android.os.DeadSystemException
at android.net.ConnectivityManager.getActiveNetworkInfo(ConnectivityManager.java:761)
at net.osmand.plus.OsmandSettings.isInternetConnected(OsmandSettings.java:265)
at net.osmand.plus.OsmandSettings.isInternetConnectionAvailable(OsmandSettings.java:252)
at net.osmand.plus.OsmandSettings.isInternetConnectionAvailable(OsmandSettings.java:246)
at net.osmand.plus.helpers.DiscountHelper.checkAndDisplay(DiscountHelper.java:54)
at net.osmand.plus.activities.MapActivity.onResume(MapActivity.java:637)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1270)
at android.app.Activity.performResume(Activity.java:6786)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3422)
... 10 more
Caused by: android.os.DeadSystemException
... 19 more
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
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build. Also seperate unlock bootloader not required... It will b done by flash process automatically.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
Unzip the downloaded file. Put it in a folder in desktop.
There is a file named "system+vendor.zip" or something like that, unzip that, refer readme guide for details.
Put those above unzipped .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Detailed process available in readme file inside.
Best of luck
This ROM is included
TWRP+Magisk
opengapps pico
Gcam
Ampere app
Viper sound mod
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file...
https://www.androidfilehost.com/?w=files&flid=293310
NB Drop a line in comment section mentioning your feedback / bugs / experience
Updated version V2
Changelog
Magisk19.3 (magisk20 creating problem)
Updated gapps
Fastboot flashscript errors removed
added viper sound mod
updated twrp3.3.1-0
(NB:: Need to unzip system.zip, vendor.zip,recovery.zip,boot.zip to get corrsponding img files before flash)
what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?
KLozhev said:
what are the differences from havoc 2.9 gsi? (besides TWRP + Magisk20.1 opengapps pico Gcam Ampere app Google Phone Dialer Safetynet Fixed)
Gcam version? all work fine?
Click to expand...
Click to collapse
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.
[email protected] said:
It is a fastboot rom.... Can b flashed thru fastboot mode without twrp/custom recovery. No need to unlock bootloader seperately.
Everything will b done thru flashing script... U can say
Its a one click install rom.
Click to expand...
Click to collapse
thx
[email protected] said:
TWRP+Magisk20.1
Gcam
Click to expand...
Click to collapse
Gcam not work
without root
in TWRP 3.2.3(!) not work, mtp, adb, microsb
in archive missing generate_image.exe
Code:
934 I ActivityManager: START u0 {act=android.content.pm.action.REQUEST_PERMISSIONS pkg=com.google.android.packageinstaller cmp=com.google.android.packageinstaller/com.android.packageinstaller.permission.ui.GrantPermissionsActivity (has extras)} from uid 10230
10-28 16:42:04.510 1532 3811 D StorageManagerService: UID 10230 is actively using camera; letting them defy reserved cached data
--------- beginning of crash
10-28 16:42:04.570 8619 8665 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
10-28 16:42:04.570 8619 8665 E AndroidRuntime: Process: com.google.android.GoogleCamera, PID: 8619
10-28 16:42:04.570 8619 8665 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at lar.run(Unknown Source:54)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
10-28 16:42:04.570 8619 8665 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
10-28 16:42:04.620 1532 8279 W ActivityManager: Force finishing activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
10-28 16:42:04.639 1532 8279 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1005 com.android.server.am.AppErrors.crashApplicationInner:469 com.android.server.am.AppErrors.crashApplication:392 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:15805 com.android.server.am.ActivityManagerService.handleApplicationCrash:15771
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.644 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
--------- beginning of main
10-28 16:42:04.693 949 8767 I chatty : uid=1047(cameraserver) /system/bin/cameraserver expire 3 lines
10-28 16:42:04.708 1532 5145 I WindowManager: WIN DEATH: Window{a97e4c3 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher}
10-28 16:42:04.708 1532 8108 I ActivityManager: Process com.google.android.GoogleCamera (pid 8619) has died: vis +99TOP
10-28 16:42:04.710 1532 1588 I chatty : uid=1000(system) ActivityManager expire 8 lines
10-28 16:42:04.710 795 8752 I chatty : uid=1047(cameraserver) [email protected] expire 4 lines
10-28 16:42:04.713 1532 3227 I WindowManager: WIN DEATH: Window{263b47e u0 Toast}
10-28 16:42:04.713 1532 3227 I chatty : uid=1000(system) Binder:1532_3 expire 1 line
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to set client state on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.732 831 1286 W SurfaceFlinger: Attempting to destroy on removed layer: com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0
10-28 16:42:04.736 795 8785 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.739 831 906 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.743 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_load not supported
10-28 16:42:04.743 815 840 E ANDR-PERF-OPTSHANDLER: Perflock resource /sys/devices/system/cpu/cpu0/cpufreq/schedutil/hispeed_freq not supported
10-28 16:42:04.749 1532 1587 W ActivityManager: Slow operation: 142ms so far, now at startProcess: returned from zygote!
10-28 16:42:04.752 746 746 I Zygote : Process 8619 exited due to signal (9)
10-28 16:42:04.763 8821 8821 I chatty : uid=10230(u0_a230) expire 4 lines
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating battery stats
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: building log message
10-28 16:42:04.763 1532 1587 I ActivityManager: Start proc 8821:com.google.android.GoogleCamera:crash_report/u0a230 for service com.google.android.GoogleCamera/com.google.android.apps.camera.app.silentfeedback.SilentFeedbackService
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: starting to update pids map
10-28 16:42:04.763 1532 1587 W ActivityManager: Slow operation: 156ms so far, now at startProcess: done updating pids map
10-28 16:42:04.768 831 1286 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.769 949 1913 I chatty : uid=1047(cameraserver) HwBinder:949_3 expire 12 lines
10-28 16:42:04.771 4271 4271 D Launcher.Utilities: onLauncherStart: 0
10-28 16:42:04.773 1532 3811 W ActivityManager: Unable to start service Intent { act=com.android.launcher3.WINDOW_OVERLAY dat=app://ch.deletescape.lawnchair.ci:10038?v=7&cv=9 pkg=com.google.android.googlequicksearchbox } U=0: not found
10-28 16:42:04.803 831 3852 E BufferQueueProducer: [SurfaceView - com.google.android.GoogleCamera/com.android.camera.CameraLauncher#0] queueBuffer: BufferQueue has been abandoned
10-28 16:42:04.815 795 1794 I chatty : uid=1047(cameraserver) HwBinder:795_1 expire 122 lines
10-28 16:42:04.818 815 840 E ANDR-PERF-MPCTL: Invalid profile no. 0, total profiles 0 only
10-28 16:42:04.853 795 8804 I chatty : uid=1047(cameraserver) [email protected] expire 1 line
10-28 16:42:04.893 795 8841 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.894 795 8842 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.895 795 8843 I chatty : uid=1047(cameraserver) [email protected] expire 3 lines
10-28 16:42:04.896 795 8844 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.903 8821 8821 E AndroidRuntime: FATAL EXCEPTION: main
10-28 16:42:04.903 8821 8821 E AndroidRuntime: Process: com.google.android.GoogleCamera:crash_report, PID: 8821
10-28 16:42:04.903 8821 8821 E AndroidRuntime: java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.GoogleCamera, sha1=61ed377e85d386a8dfee6b864bd85b0bfaa5af81, atk=false, ver=14848037.true
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:1950)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1918)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1868)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at ksy.a(Unknown Source:35)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at krq.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kzw.a(Unknown Source:98)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at laa.run(Unknown Source:21)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at kwm.run(Unknown Source:7)
10-28 16:42:04.903 8821 8821 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
10-28 16:42:04.908 1532 8820 W ActivityManager: Process com.google.android.GoogleCamera has crashed too many times: killing!
10-28 16:42:04.910 1532 8820 I ActivityManager: Killing 8821:com.google.android.GoogleCamera:crash_report/u0a230 (adj 500): crash
10-28 16:42:04.914 795 8846 I chatty : uid=1047(cameraserver) [email protected] expire 5 lines
10-28 16:42:04.918 795 8848 I chatty : uid=1047(cameraserver) [email protected] expire 2 lines
10-28 16:42:04.932 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-28 16:42:04.933 1532 1585 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-28 16:42:04.937 802 843 I SDM : ResourceImpl::SetMaxBandwidthMode: new bandwidth mode=0
10-28 16:42:04.947 439 439 E SELinux : avc: denied { find } for interface=vendor.lineage.camera.motor::ICameraMotor sid=u:r:cameraserver:s0 pid=949 scontext=u:r:cameraserver:s0 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=0
THANK YOU!!!!!!
[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Bootloader unlocking required or not ???
Techgaming432 said:
Bootloader unlocking required or not ???
Click to expand...
Click to collapse
Not required... Unlock will b done automatically by flash script
[email protected] said:
This file is exclusively prepared by BN_P
for
Asus Zenfone Max M2 (X01AD). It is havoc Pie 2.9 on pie vendor, Firmware-JP-16.2018.1910.52.
How to ::
1. Confirm your device model as above.
2. No need to be worried on which build your device is presently. This Rom can be flashed on any build.
3. Only for windows users, flashing can be done in windows only.
Before start flashing,
There is a file named "system+vendor.zip", unzip that, it will generate two file i.e. system.img and vendor.img
Put the above two .img files in the main folder i.e same location of flash_all.cmd.
4. Put your device in fastboot mode, connect to PC and run the flash_all.cmd, just double click on it.
5. Follow the pop up screen.
6. Data erase will be required after flashing before boot.
Best of luck
This ROM is included
TWRP+Magisk20.1
opengapps pico
Gcam
Ampere app
Google Phone Dialer
Safetynet Fixed
Bugs::
You tell me.
Thanks to::
@vincent for HavocOS GSI image.
[MENTION=268073]topjhonwu for magisk
Link for file
https://www.androidfilehost.com/?fid=4349826312261607460
Click to expand...
Click to collapse
Any other ROM like MIUI or Oxygen OS have for X01AD ??
Techgaming432 said:
Any other ROM like MIUI or Oxygen OS have for X01AD ??
Click to expand...
Click to collapse
Search.... I hv not made yet
[email protected] said:
Search.... I hv not made yet
Click to expand...
Click to collapse
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM
Techgaming432 said:
Please made a MIUI 10 stable ROM i will give what you want but please made a MIUI 10 stable ROM
Click to expand...
Click to collapse
May b in future
please tell me full process step by step
nixsting said:
please tell me full process step by step
Click to expand...
Click to collapse
Follow readme file inside
An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem
Techgaming432 said:
An error occurred when flashing the system image it says invalid sparse system in command prompt window and skips the system image from flashing
Please tell me the solve of the problem
Click to expand...
Click to collapse
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Before flashing ensure all img files are present
Sydtem.img
Vendor
Boot
Recovery
Other firmwire images
[email protected] said:
Did u unzipped system.zip and kept the system.img file at flashing folder....?
Plz follow readme file inside.
Click to expand...
Click to collapse
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres
Techgaming432 said:
Yes i extracted the system+vendor zip file and moved the system.img and vendor.img file into the same location on flashall.cmd and exactly follow the guide but the error occurres
Click to expand...
Click to collapse
Post a screenshot
[email protected] said:
Post a screenshot
Click to expand...
Click to collapse
Ok I will try another time to flash if the erro occure then i will take a screenshot of the command prompt window and send it to you by today evening