Related
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i
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!
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute following command on Wear (with ADB enabled - doesn't require root) or run attached app (root on watch required).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing using following command (thanks @matejdro) or also use the wear app for that
Code:
adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"
Finish setup, let it work for some time and restart both phone B and your watch to properly apply all changes. Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
moneytoo said:
Android Wear allows pairing to a new/second phone only after you perform factory reset of Android Wear: "You can switch which phone or tablet your watch is paired with, but you need to reset your watch to factory settings first. Then you can pair your watch to the new phone or tablet." Google Support
It's ok for most people but some just have more devices and want to switch them from time to time. Performing factory reset means compiling apps to aot, retransferring all apps the need to reconfigure all apps (Wear Mini Launcher, anyone?).
There used to be an app BeeLink but it stopped working and was removed.
There's actually way faster way how to set up connection with a new phone - in a minute. Just delete application data of "Google Play Services Wearable" app and reboot. All the 3rd party apps with their configurations, all watch faces with configurations, Google Fit data, and basically everything else will be kept.
Run the following command on your pc (with Wear connected and ADB enabled - this doesn't require root) or use my app for switching on-the-go (it requires root on Wear).
Code:
adb shell "pm clear com.google.android.gms && reboot"
Step by step
Wear is connected with phone A so turn off Bluetooth on this phone.
Execute above command or run attached app (root required).
Power on Bluetooth on phone B.
Depending whatever devices were paired previously, confirm pairing code or initiate new pairing.
Done.
Attached apk is for installation on mobile phone (it contains and installs the actual Wear app). It's not on Play Store yet. Let's try it and get some feedback first.
Click to expand...
Click to collapse
rekil goth said:
Hi,
Thanks for making this for those of us who know nothing about adb. Unfortunately, I could not get this to work, but I'm certain the error is at my end. I downloaded and installed your apk, but I can't get it to open or find it in the app drawer. Excuse my ignorance. Could you please inform me as to how I can run the apk after installation? I downloaded it on to phone B, which does not have android wear installed, as per your instructions. However, I never got passed step 2 of your guide for the above mentioned reason.
Thank you kindly
Click to expand...
Click to collapse
this App needs to be Sync'd to the watch so download it to Phone A, which is already paired.
wait until it syncs or manually sync Apps in Wear App on phone A.
when it's availalbe on your watch, then start this procedure.
hmm, just tried this (both ADB command and App installed on watch) with a new phone and I couldn't get it to pair. had to do the watch reset
Not working for me either. Will try the adb route when I can and report back
Finally a solution to my problem.
When i flash a new ROM i have to pair my moto 360 again... And to do this i allways do a reset on my watch...
Next time i will try it and give a feedback.
Not working on moto 360 5.0.2, rooted?
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Hi, my SW3 was connected to my Mi 4, setup done and working fine. I used Titanium Backup to backup Android Wear and all the watch faces apps.
After I flashed a new custom ROM, used Titanium Backup to restore Android Wear and watch face apps, and also Bluetooth connections on my Mi 4. When SW 3 is connected to my computer, in Adb, it says unauthorised.
Since it is unauthorized, I can't run the ADB command.
Any suggestions?
I don't think there is anything you can do at this point. You should have authorized your PC when you still had working watch connection.
any plans to update it
matejdro said:
I was trying to figure out this one, but could not found proper app to clear. I cleared GMS, Wear launcher, settings etc. and nothing helped. In the end I found this solution which is even better IMO:
Code:
adb shell am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE
After executing above code via ADB, dialog will pop up on wear asking if you want to make watch discoverable. Then you can find and pair it to any phone.
Click to expand...
Click to collapse
Using Minimal ADB, I had to run as admin to make this work, but then it worked perfectly. Thanks very much!
nothing. doesn't work with 5.1.1 g watch rooted, the app gives me black screen (dismissable with swipe)
Just using app from OP is apparently not enough anymore on 5.1.1.
I just made tutorial on reddit on how to reset 5.1.1 watch: https://www.reddit.com/r/AndroidWear/comments/3c4qf8/tip_how_to_switch_phones_without_hard_reset/
I updated the Wear app (v0.2) with support for requesting Bluetooth discoverable mode as well.
Did you guys see this: https://developer.android.com/training/wearables/apps/bt-debugging.html
Yes! I'm so glad something like this has been developed! Worst part about switching ROMs is resetting android wear now. Thanks so much!
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
bartito said:
Performed the clean in the watch.
It works, and is possible to link the watch with another phone without perform a data wipe.
Then only problem that I've encontered is that the installed watchfaces aren't visible in the Android wear app (in the phone), and I can't set from the phone or hide some.
Thanks
EDIT: Sometimes, due to the watchfaces issue, Android wear app UI generates a FC
Code:
E/AndroidRuntime( 6255): FATAL EXCEPTION: main
E/AndroidRuntime( 6255): Process: com.google.android.wearable.app, PID: 6255
E/AndroidRuntime( 6255): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.content.ComponentName.equals(java.lang.Object)' on a null object reference
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.loadWatchFaces(WatchFacePreviewFragment.java:261)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.WatchFacePreviewFragment.onWatchFacesLoaded(WatchFacePreviewFragment.java:209)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:198)
E/AndroidRuntime( 6255): at com.google.android.clockwork.companion.watchfaces.WatchFaceLoadTask.onPostExecute(WatchFaceLoadTask.java:33)
E/AndroidRuntime( 6255): at android.os.AsyncTask.finish(AsyncTask.java:636)
E/AndroidRuntime( 6255): at android.os.AsyncTask.access$500(AsyncTask.java:177)
E/AndroidRuntime( 6255): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:653)
E/AndroidRuntime( 6255): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 6255): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 6255): at android.app.ActivityThread.main(ActivityThread.java:5293)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 6255): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 6255): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
W/ActivityManager( 829): Force finishing activity 1 com.google.android.wearable.app/com.google.android.clockwork.companion.StatusActivity
Click to expand...
Click to collapse
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
moneytoo said:
Did you also try reseting app data of both Android Wear and Google Play on the phone (& restart)?
Click to expand...
Click to collapse
yes, performed a reboot in the wear and also a wipe in the phone
CHANGELOG
https://github.com/ac-pm/Inspeckage/blob/master/CHANGELOG
Introduction
Inspeckage is a tool developed to offer dynamic analysis of Android applications. With this tool we can better understand what an Android application is doing at runtime.
* https://twitter.com/inspeckage
* https://play.google.com/store/apps/details?id=mobi.acpm.inspeckage
How it works?
It is a simply application (apk) with an internal HTTP server providing a friendly web interface.
Features
Information gathering
Requested Permissions
App Permissions
Shared Libraries
Exported Activities and Non Exported Activities
Exported Content Provider and Non Exported Content Provider
Exported Services and Non Exported Services
Exported Broadcast Receiver and Non Exported Broadcast Receiver
If is Debuggable
Version, UID and GIDs
etc
Hooks (until now)
With the hooks, we can see what the application is doing in real time.
Shared Preferences (log and file)
Serialization
Crypto
Hash
SQLite
HTTP (a http proxy tool it is still the best alternative)
File System
Miscellaneous (Clipboard, URL.Parse())
WebView
IPC
Actions
With the Xposed is possible do some actions like start a not exported activity!
Start any activity (exported and non exported)
Calling any provider (exported and non exported)
Disable FLAG_SECURE
SSL uncheck
Start, close and restart the application
Extras
APK Download
View the app's directory tree
Download the app files
Download the output generated by hooks in text file format
Printscreen
Configuration
Even with some hooks at HTTP libraries, using an external proxy tool it is still the best alternative to analyze the traffic.
Add a proxy to the target app
Enable and disable proxy
Add entries in the arp table
Requirements
Xposed Framework
Download
http://repo.xposed.info/module/mobi.acpm.inspeckage
Source Code
https://github.com/ac-pm/Inspeckage
Screenshots
Tab Screenshot
Reporting bugs
For bug reports and feature requests, please post them in the GitHub Issues page.
Genymotion
I made a small tutorial on how to get it ready for Inspeckage.
https://vimeo.com/156745941
XDA:DevDB Information
Inspeckage, Xposed for all devices (see above for details)
Contributors
acarlosmartins
Source Code: https://github.com/ac-pm/Inspeckage
Xposed Package Name: mobi.acpm.inspeckage
Version Information
Status: Stable
Current Stable Version: 1.4.1
Stable Release Date: 2016-07-19
Created 2016-02-29
Last Updated 2017-05-26
Crash on Marshmallow 6.x Stock LG G4,
Does not work with Adguard.
http://forum.xda-developers.com/android/apps-games/adguard-ad-blocker-doesnt-require-root-t2958895
great working like charm on sgs4 aosp lollipop rom
Nice one. Was looking for something like this for a long time. Will test it 2morrow. Hope the times of catlog are over
Thanks for your work
HorstiG said:
Crash on Marshmallow 6.x Stock LG G4,
Does not work with Adguard.
http://forum.xda-developers.com/android/apps-games/adguard-ad-blocker-doesnt-require-root-t2958895
Click to expand...
Click to collapse
Sorry, but it worked for me.
http://i.imgur.com/hQ3gEGM.png
Look, if the app does not use some libs, the tabs will be blank.
I'm testing with Genimotion android 5.1.0 API 22.
Awesome tool! Thank you!
I see `App is running: false`, and when app started. `The app is running?` Module enable: true | Version: 1.1b
Nexus 6, CM-13.0-20160305-NIGHTLY-shamu
@acarlosmartins: Please remove the "#" in front of the name at xposed repo
defim said:
@acarlosmartins: Please remove the "#" in front of the name at xposed repo
Click to expand...
Click to collapse
Done! Thank you for reminding me.
http://repo.xposed.info/module/mobi.acpm.inspeckage
d34dr00t said:
I see `App is running: false`, and when app started. `The app is running?` Module enable: true | Version: 1.1b
Nexus 6, CM-13.0-20160305-NIGHTLY-shamu
Click to expand...
Click to collapse
I will investigate. Thanks for the feedback!
Seems like a very nice app. Working well on my Lollipop device. Thanks!
Can you explain a bit more about what some of the features do, for example I see the app I launch says debuggable: no, what determines that?
Also The app I launched does make http requests but none showed up in the http tab, also what does the crypto tab show? that is probably the most interesting thing for me as someone interested in reverse engineering, is it possible to see clear text information that it is encrypting?
Hi,
The app doesn't work on Sony Xperia 4.1.2.
Logcat error:
6051 AndroidRuntime E FATAL EXCEPTION: main
6051 AndroidRuntime E java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{mobi.acpm.inspeckage/mobi.acpm.inspeckage.ui.M
ainActivity}: java.lang.ClassNotFoundException: mobi.acpm.inspeckage.ui.MainActivity
6051 AndroidRuntime E at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1987)
6051 AndroidRuntime E at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2088)
6051 AndroidRuntime E at android.app.ActivityThread.access$600(ActivityThread.java:134)
6051 AndroidRuntime E at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1199)
6051 AndroidRuntime E at android.os.Handler.dispatchMessage(Handler.java:99)
6051 AndroidRuntime E at android.os.Looper.loop(Looper.java:137)
6051 AndroidRuntime E at android.app.ActivityThread.main(ActivityThread.java:4744)
6051 AndroidRuntime E at java.lang.reflect.Method.invokeNative(Native Method)
6051 AndroidRuntime E at java.lang.reflect.Method.invoke(Method.java:511)
6051 AndroidRuntime E at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
6051 AndroidRuntime E at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
6051 AndroidRuntime E at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
6051 AndroidRuntime E at dalvik.system.NativeStart.main(Native Method)
6051 AndroidRuntime E Caused by: java.lang.ClassNotFoundException: mobi.acpm.inspeckage.ui.MainActivity
6051 AndroidRuntime E at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
6051 AndroidRuntime E at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
6051 AndroidRuntime E at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
6051 AndroidRuntime E at android.app.Instrumentation.newActivity(Instrumentation.java:1053)
6051 AndroidRuntime E at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1978)
6051 AndroidRuntime E ... 12 more
cybermapt said:
Hi,
6051 AndroidRuntime E FATAL EXCEPTION: main
6051 AndroidRuntime E java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{mobi.acpm.inspeckage/mobi.acpm.inspeckage.ui.M
ainActivity}: java.lang.ClassNotFoundException: mobi.acpm.inspeckage.ui.MainActivity
Click to expand...
Click to collapse
I have this "ClassNotFoundException" also in an app by me, but not published yet. I'm not sure what's the cause, but it could be an Xposed failure. It happens for me also with the "main" activity
Same error/crash with Nexus 7, Android 4.4.4
I tried to install older version. These older versions get on but the module remains disabled and app doesn't work.
Thanks
Inspeckage - Android Package Inspector - new version v1.4
# Inspeckage - CHANGELOG
1.4
---------------
- tabs with badges (counter);
- for "+ Hooks", FLAG_SECURE and proxy options you dont need restart the app;
- enable/disable hooks (tabs);
- support to android 4.x (experimental);
- android:allowBackup in info area;
- app icon in ifo area;
- some bug fixes.
1.3
---------------
- New tab "+ Hooks". Now the user can specify new hook's dynamically.
- collapsible app info area
- some bug fixes
1.2
---------------
New logcat.html page. A experimental page with websocket to show some information from the logcat.
1.1b
---------------
Fix the backpressed crash
Fix intent launch not found
Improvements in the Start Activity option
1.0b
---------------
With Inspeckage, we can get a good amount of information about the application's behavior:
== Information gathering
* Requested Permissions;
* App Permissions;
* Shared Libraries;
* Exported and Non-exported Activities, Content Providers,Broadcast Receivers and Services;
* Check if the app is debuggable or not;
* Version, UID and GIDs;
* etc.
== Hooks (so far)
With the hooks, we can see what the application is doing in real time:
* Shared Preferences (log and file);
* Serialization;
* Crypto;
* Hashes;
* SQLite;
* HTTP (an HTTP proxy tool is still the best alternative);
* File System;
* Miscellaneous (Clipboard, URL.Parse());
* WebView;
* IPC.
== Actions
With Xposed it's possible to perform actions such as start a unexported activity and much else:
* Start any activity (exported and unexported);
* Call any provider (exported and unexported);
* Disable FLAG_SECURE;
* SSL uncheck;
* Start, stop and restart the application.
== Extras
* APK Download;
* View the app's directory tree;
* Download the app's files;
* Download the output generated by hooks in text file format;
* Take a screen capture;
== Configuration
Even though our tool has some hooks to the HTTP libraries, using an external proxy tool is still the best option to analyze the app's traffic. With Inspeckage, you can:
* Add a proxy to the target app;
* Enable and disable proxy;
* Add entries in the arp table.
Hello,
I'm trying to get Inspeckage running on my LG G4 (H815, marshmallow v20e-208-01) .
I've tried with xposed v86 for arm64, then v85 for arm64 without success. I have get Inspeckage running fine (module installed, server started, webgui running) but when I try to start an application (i've tried for exemple FM radio) it fails with the system message "application has stop running"
Where could I be wrong ? Should I install another version of xposed ?
Thank you in advance.
Inspeckage - Android Package Inspector - v1.4.1 released
https://twitter.com/inspeckage
# Inspeckage - CHANGELOG
1.4.1
---------------
- add the option "Bind to address" on "Config" app screen - now you can bind to all interfaces, any specific local IP address, or to just the loopback interface.
Note: if you choose a non-loopback interface, other computers maybe can access the Inspeckage.
- bug fix - the "App is running:" always false
1.4
---------------
- tabs with badges (counter);
- for "+ Hooks", FLAG_SECURE and proxy options you dont need restart the app;
- enable/disable hooks (tabs);
- support to android 4.x (experimental);
- android:allowBackup in info area;
- app icon in info area;
- some bug fixes.
1.3
---------------
- New tab "+ Hooks". Now the user can specify new hook's dynamically.
- collapsible app info area
- some bug fixes
1.2
---------------
New logcat.html page. A experimental page with websocket to show some information from the logcat.
1.1b
---------------
Fix the backpressed crash
Fix intent launch not found
Improvements in the Start Activity option
1.0b
---------------
With Inspeckage, we can get a good amount of information about the application's behavior:
== Information gathering
* Requested Permissions;
* App Permissions;
* Shared Libraries;
* Exported and Non-exported Activities, Content Providers,Broadcast Receivers and Services;
* Check if the app is debuggable or not;
* Version, UID and GIDs;
* etc.
== Hooks (so far)
With the hooks, we can see what the application is doing in real time:
* Shared Preferences (log and file);
* Serialization;
* Crypto;
* Hashes;
* SQLite;
* HTTP (an HTTP proxy tool is still the best alternative);
* File System;
* Miscellaneous (Clipboard, URL.Parse());
* WebView;
* IPC.
== Actions
With Xposed it's possible to perform actions such as start a unexported activity and much else:
* Start any activity (exported and unexported);
* Call any provider (exported and unexported);
* Disable FLAG_SECURE;
* SSL uncheck;
* Start, stop and restart the application.
== Extras
* APK Download;
* View the app's directory tree;
* Download the app's files;
* Download the output generated by hooks in text file format;
* Take a screen capture;
== Configuration
Even though our tool has some hooks to the HTTP libraries, using an external proxy tool is still the best option to analyze the app's traffic. With Inspeckage, you can:
* Add a proxy to the target app;
* Enable and disable proxy;
* Add entries in the arp table.
AlaskanMalamute said:
Hello,
I'm trying to get Inspeckage running on my LG G4 (H815, marshmallow v20e-208-01) .
I've tried with xposed v86 for arm64, then v85 for arm64 without success. I have get Inspeckage running fine (module installed, server started, webgui running) but when I try to start an application (i've tried for exemple FM radio) it fails with the system message "application has stop running"
Where could I be wrong ? Should I install another version of xposed ?
Thank you in advance.
Click to expand...
Click to collapse
Please, try the version 1.4.1.
Thanks
doesnt work on mate7 mashmellow. when trying to inspect apk. lauching it just crash. no webgui
acarlosmartins said:
CHANGELOG
https://github.com/ac-pm/Inspeckage/blob/master/CHANGELOG
Introduction
Inspeckage is a tool developed to offer dynamic analysis of Android applications. With this tool we can better understand what an Android application is doing at runtime.
* https://twitter.com/inspeckage
* https://play.google.com/store/apps/details?id=mobi.acpm.inspeckage
How it works?
It is a simply application (apk) with an internal HTTP server providing a friendly web interface.
Features
Information gathering
Requested Permissions
App Permissions
Shared Libraries
Exported Activities and Non Exported Activities
Exported Content Provider and Non Exported Content Provider
Exported Services and Non Exported Services
Exported Broadcast Receiver and Non Exported Broadcast Receiver
If is Debuggable
Version, UID and GIDs
etc
Hooks (until now)
With the hooks, we can see what the application is doing in real time.
Shared Preferences (log and file)
Serialization
Crypto
Hash
SQLite
HTTP (a http proxy tool it is still the best alternative)
File System
Miscellaneous (Clipboard, URL.Parse())
WebView
IPC
Actions
With the Xposed is possible do some actions like start a not exported activity!
Start any activity (exported and non exported)
Calling any provider (exported and non exported)
Disable FLAG_SECURE
SSL uncheck
Start, close and restart the application
Extras
APK Download
View the app's directory tree
Download the app files
Download the output generated by hooks in text file format
Printscreen
Configuration
Even with some hooks at HTTP libraries, using an external proxy tool it is still the best alternative to analyze the traffic.
Add a proxy to the target app
Enable and disable proxy
Add entries in the arp table
Requirements
Xposed Framework
Download
http://repo.xposed.info/module/mobi.acpm.inspeckage
Source Code
https://github.com/ac-pm/Inspeckage
Screenshots
Tab Screenshot
Reporting bugs
For bug reports and feature requests, please post them in the GitHub Issues page.
Genymotion
I made a small tutorial on how to get it ready for Inspeckage.
https://vimeo.com/156745941
XDA:DevDB Information
Inspeckage, Xposed for all devices (see above for details)
Contributors
acarlosmartins
Source Code: https://github.com/ac-pm/Inspeckage
Xposed Package Name: mobi.acpm.inspeckage
Version Information
Status: Stable
Current Stable Version: 1.4.1
Stable Release Date: 2016-07-19
Created 2016-02-29
Last Updated 2016-07-19
Click to expand...
Click to collapse
First I have heard of this, apparently around a bit.
So ... can this be used to place Google Now pane as widget on someone else's launcher? (Want a Nobel?)
Other Google hacks?
I created Dooo app using android source code but after build when i install it my phone its opening and closing crashing.
Android Studio Build Report
Code:
Executing tasks: [:app:assembleRelease] in project C:\Users\Manoj\Project\Dooo
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns http://schemas.android.com/repository/android/common/02 to old ns http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns http://schemas.android.com/repository/android/generic/02 to old ns http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/addon2/02 to old ns http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/repository2/02 to old ns http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns http://schemas.android.com/sdk/android/repo/sys-img2/01
> Task :app:preBuild UP-TO-DATE
> Task :app:preReleaseBuild UP-TO-DATE
> Task :app:compileReleaseAidl NO-SOURCE
> Task :app:compileReleaseRenderscript NO-SOURCE
> Task :app:generateReleaseBuildConfig UP-TO-DATE
> Task :app:javaPreCompileRelease UP-TO-DATE
> Task :app:writeReleaseApplicationId UP-TO-DATE
> Task :app:analyticsRecordingRelease
> Task :app:checkReleaseAarMetadata UP-TO-DATE
> Task :app:generateReleaseResValues UP-TO-DATE
> Task :app:generateReleaseResources UP-TO-DATE
> Task :app:processReleaseGoogleServices UP-TO-DATE
> Task :app:mergeReleaseResources UP-TO-DATE
> Task :app:createReleaseCompatibleScreenManifests UP-TO-DATE
> Task :app:extractDeepLinksRelease UP-TO-DATE
> Task :app:processReleaseMainManifest UP-TO-DATE
> Task :app:processReleaseManifest UP-TO-DATE
> Task :app:processReleaseManifestForPackage UP-TO-DATE
> Task :app:processReleaseResources UP-TO-DATE
> Task :app:compileReleaseJavaWithJavac UP-TO-DATE
> Task :app:compileReleaseSources UP-TO-DATE
> Task :app:lintVitalRelease
> Task :app:mergeReleaseJniLibFolders UP-TO-DATE
> Task :app:mergeReleaseNativeLibs UP-TO-DATE
> Task :app:stripReleaseDebugSymbols UP-TO-DATE
> Task :app:extractReleaseNativeSymbolTables UP-TO-DATE
> Task :app:mergeReleaseNativeDebugMetadata NO-SOURCE
> Task :app:mergeReleaseShaders UP-TO-DATE
> Task :app:compileReleaseShaders NO-SOURCE
> Task :app:generateReleaseAssets UP-TO-DATE
> Task :app:mergeReleaseAssets UP-TO-DATE
> Task :app:compressReleaseAssets UP-TO-DATE
> Task :app:checkReleaseDuplicateClasses UP-TO-DATE
> Task :app:dexBuilderRelease UP-TO-DATE
> Task :app:desugarReleaseFileDependencies UP-TO-DATE
> Task :app:mergeExtDexRelease UP-TO-DATE
> Task :app:mergeDexRelease UP-TO-DATE
> Task :app:processReleaseJavaRes NO-SOURCE
> Task :app:mergeReleaseJavaResource UP-TO-DATE
> Task :app:optimizeReleaseResources UP-TO-DATE
> Task :app:collectReleaseDependencies UP-TO-DATE
> Task :app:sdkReleaseDependencyData UP-TO-DATE
> Task :app:validateSigningRelease UP-TO-DATE
> Task :app:writeReleaseAppMetadata UP-TO-DATE
> Task :app:writeReleaseSigningConfigVersions UP-TO-DATE
> Task :app:packageRelease
PackagingOptions.jniLibs.useLegacyPackaging should be set to true because android:extractNativeLibs is set to "true" in AndroidManifest.xml.
> Task :app:assembleRelease
BUILD SUCCESSFUL in 7s
36 actionable tasks: 3 executed, 33 up-to-date
Build Analyzer results available
Is it script problm or Android Studio Bug?
On phone in question do a LOGCAT to get the very reason why app crashes.
Code:
2021-08-27 17:20:15.727 6936-6936/com.dooo.android W/om.dooo.androi: Accessing hidden method Landroid/view/View;->computeFitSystemWindows(Landroid/graphics/Rect;Landroid/graphics/Rect;)Z (greylist, reflection, allowed)
2021-08-27 17:20:15.728 6936-6936/com.dooo.android W/om.dooo.androi: Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (greylist, reflection, allowed)
2021-08-27 17:20:15.867 6936-6936/com.dooo.android I/om.dooo.androi: Waiting for a blocking GC ClassLinker
2021-08-27 17:20:15.873 6936-6936/com.dooo.android I/om.dooo.androi: WaitForGcToComplete blocked ClassLinker on ClassLinker for 6.066ms
2021-08-27 17:20:15.909 6936-6936/com.dooo.android D/test: Permission is granted
2021-08-27 17:20:15.920 6936-12400/com.dooo.android I/FA: Tag Manager is not found and thus will not be used
2021-08-27 17:20:16.022 6936-12388/com.dooo.android D/HostConnection: HostConnection::get() New Host Connection established 0xf2b635c0, tid 12388
2021-08-27 17:20:16.027 6936-12388/com.dooo.android D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_vulkan ANDROID_EMU_deferred_vulkan_commands ANDROID_EMU_vulkan_null_optional_strings ANDROID_EMU_vulkan_create_resources_with_requirements ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer ANDROID_EMU_vulkan_ignored_handles ANDROID_EMU_has_shared_slots_host_memory_allocator ANDROID_EMU_vulkan_free_memory_sync ANDROID_EMU_vulkan_shader_float16_int8 ANDROID_EMU_vulkan_async_queue_submit ANDROID_EMU_sync_buffer_data GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_async_frame_commands ANDROID_EMU_gles_max_version_2
2021-08-27 17:20:16.028 6936-12388/com.dooo.android W/OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
2021-08-27 17:20:16.034 6936-12388/com.dooo.android D/EGL_emulation: eglCreateContext: 0xf2b62520: maj 2 min 0 rcv 2
2021-08-27 17:20:16.059 6936-12388/com.dooo.android D/EGL_emulation: eglMakeCurrent: 0xf2b62520: ver 2 0 (tinfo 0xc0061d30) (first time)
2021-08-27 17:20:16.085 6936-12388/com.dooo.android I/Gralloc4: mapper 4.x is not supported
2021-08-27 17:20:16.089 6936-12388/com.dooo.android D/HostConnection: createUnique: call
2021-08-27 17:20:16.089 6936-12388/com.dooo.android D/HostConnection: HostConnection::get() New Host Connection established 0xbb323470, tid 12388
2021-08-27 17:20:16.089 6936-12388/com.dooo.android D/goldfish-address-space: allocate: Ask for block of size 0x100
2021-08-27 17:20:16.090 6936-12388/com.dooo.android D/goldfish-address-space: allocate: ioctl allocate returned offset 0x3e7ffe000 size 0x2000
2021-08-27 17:20:16.096 6936-12388/com.dooo.android D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_native_sync_v4 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_vulkan ANDROID_EMU_deferred_vulkan_commands ANDROID_EMU_vulkan_null_optional_strings ANDROID_EMU_vulkan_create_resources_with_requirements ANDROID_EMU_YUV_Cache ANDROID_EMU_async_unmap_buffer ANDROID_EMU_vulkan_ignored_handles ANDROID_EMU_has_shared_slots_host_memory_allocator ANDROID_EMU_vulkan_free_memory_sync ANDROID_EMU_vulkan_shader_float16_int8 ANDROID_EMU_vulkan_async_queue_submit ANDROID_EMU_sync_buffer_data GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_host_side_tracing ANDROID_EMU_async_frame_commands ANDROID_EMU_gles_max_version_2
2021-08-27 17:20:16.221 6936-12402/com.dooo.android E/OneSignal: Error Getting FCM Token
java.io.IOException: AUTHENTICATION_FAILED
at com.google.firebase.iid.GmsRpc.handleResponse(com.google.firebase:[email protected]@21.0.1:7)
at com.google.firebase.iid.GmsRpc.lambda$extractResponseWhenComplete$0$GmsRpc(Unknown Source:8)
at com.google.firebase.iid.GmsRpc$$Lambda$0.then(Unknown Source:2)
at com.google.android.gms.tasks.zzd.run(Unknown Source:5)
at com.google.firebase.iid.FirebaseIidExecutors$$Lambda$0.execute(Unknown Source:0)
at com.google.android.gms.tasks.zzc.onComplete(Unknown Source:6)
at com.google.android.gms.tasks.zzr.zza(Unknown Source:19)
at com.google.android.gms.tasks.zzu.setResult(Unknown Source:86)
at com.google.android.gms.tasks.zzd.run(Unknown Source:15)
at com.google.android.gms.cloudmessaging.zzz.execute(Unknown Source:0)
at com.google.android.gms.tasks.zzc.onComplete(Unknown Source:6)
at com.google.android.gms.tasks.zzr.zza(Unknown Source:19)
at com.google.android.gms.tasks.zzu.setResult(Unknown Source:86)
at com.google.android.gms.tasks.TaskCompletionSource.setResult(Unknown Source:8)
at com.google.android.gms.cloudmessaging.zzq.zza(com.google.android.gms:[email protected]@16.0.0:9)
at com.google.android.gms.cloudmessaging.zzs.zza(com.google.android.gms:[email protected]@16.0.0:7)
at com.google.android.gms.cloudmessaging.zzf.zza(com.google.android.gms:[email protected]@16.0.0:45)
at com.google.android.gms.cloudmessaging.zzi.handleMessage(Unknown Source:2)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2021-08-27 17:20:16.243 6936-12406/com.dooo.android I/WM-WorkerWrapper: Worker result SUCCESS for Work [ id=3a6aa934-2bb0-476f-b807-d5571c9d5716, tags={ com.onesignal.OSNotificationRestoreWorkManager$NotificationRestoreWorker } ]
2021-08-27 17:20:16.333 6936-12400/com.dooo.android D/FA: Connected to remote service
2021-08-27 17:20:17.567 6936-6936/com.dooo.android D/AndroidRuntime: Shutting down VM
--------- beginning of crash
2021-08-27 17:20:17.571 6936-6936/com.dooo.android E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.dooo.android, PID: 6936
com.google.gson.JsonSyntaxException: Expected a com.google.gson.JsonObject but was com.google.gson.JsonPrimitive
at com.google.gson.internal.bind.TypeAdapters$35$1.read(TypeAdapters.java:897)
at com.google.gson.Gson.fromJson(Gson.java:932)
at com.google.gson.Gson.fromJson(Gson.java:897)
at com.google.gson.Gson.fromJson(Gson.java:846)
at com.google.gson.Gson.fromJson(Gson.java:817)
at com.dooo.android.Splash.lambda$loadConfig$6$Splash(Splash.java:181)
at com.dooo.android.Splash$$ExternalSyntheticLambda8.onResponse(Unknown Source:4)
at com.android.volley.toolbox.StringRequest.deliverResponse(StringRequest.java:82)
at com.android.volley.toolbox.StringRequest.deliverResponse(StringRequest.java:29)
at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:102)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2021-08-27 17:20:19.259 6936-6950/com.dooo.android I/om.dooo.androi: Thread[3,tid=6950,WaitingInMainSignalCatcherLoop,Thread*=0xe4e45410,peer=0x13240268,"Signal Catcher"]: reacting to signal 3
2021-08-27 17:20:19.415 6936-6950/com.dooo.android I/om.dooo.androi: Wrote stack traces to tombstoned
Please check the issue