Quote:
Originally Posted by
sourav143
Anyone here can read my logcat? Pls solve my problem, when i open paytm app my phone getting rebooted, pls check this, if u found any solution pls tell me
There is two logcats of same thing, if u find any common error pls tell
Based on your logs from 12-02-2017, paytm is trying to get broadcast permissions that are being denied. This is then causing the application to hang, which cascades into the android system and eventually causes a reboot because processes are getting hung. One problem you have in trying to diagnose this is that you're using the catlog app. Don't get me wrong, the app is great for problems that don't send you into a bootloop or cause your phone to reboot, but this is like trying to diagnose a problem at boot on your PC with software installed on the OS. You just don't see everything you need to. Get a set of clean logs using adb, it'll be much easier for others to see the actual start/stop of the system.
FWIW - I took the "lengthy" logs and ran a simple search for paytm. Once I started seeing errors (denoted by the E/ in the log) surrounding the application, I simply read what was happening during that timeframe. Below are the most frequent entries surrounding the app.
Code:
I/InputDispatcher( 2824): Application is not responding: 13166 It has been 20004.9ms since event, 20004.6ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 48. Wait queue head age: 20462.2ms.
12-02 10:27:15.839 I/WindowManager( 2824): Input event dispatching timed out sending to net.one97.paytm/net.one97.paytm.landingpage.activity.AJRMainActivity. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 48. Wait queue head age: 20462.2ms.
E/d (13166): readAppPrivateFile() com.paytm.xEngage.props.json
D/ActivityManager(26894): resumeTopActivityInnerLocked() : #1 prevTask=TaskRecord{a46fcded0 #283 A=net.one97.paytm U=0 StackId=1 sz=1} next=ActivityRecord{af8d992d0 u0 net.one97.paytm/.AJRJarvisSplash t283} mFocusedStack=ActivityStack{6e0831dd0 stackId=1, 1 tasks}
12-01 23:18:30.453 D/ActivityTrigger(26894): ActivityTrigger activityPauseTrigger
12-01 23:18:30.462 V/Launcher(27938): Launcher.onPause()
12-01 23:18:30.462 W/BroadcastQueue(26894): Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 launchParam=MultiScreenLaunchParams { mDisplayId=0 mBaseDisplayId=0 mFlags=0 } (has extras) } from com.sec.android.app.launcher (pid=27938, uid=10069) requires com.google.android.launcher.permission.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.gms/.icing.proxy.ApplicationLauncherReceiver
Because it looks to be calling the Samsung launcher, your ROM simply may not be compatible with this app (I don't know, I don't know anything about the ROM you're running)
Hope that gets you on the right path
Pune, India
Jeddah
Wollongong
Maras Dantia
Linear Mode
