Skip to content
This repository has been archived by the owner on Jun 4, 2019. It is now read-only.

Crash Error receiving broadcast Intent #62

Open
lordgreg opened this issue Sep 15, 2014 · 3 comments
Open

Crash Error receiving broadcast Intent #62

lordgreg opened this issue Sep 15, 2014 · 3 comments
Assignees
Labels
Milestone

Comments

@lordgreg
Copy link
Owner

09-09 08:38:34.298 E/AndroidRuntime(19970): Process: gpapez.sfen, PID: 19970
09-09 08:38:34.298 E/AndroidRuntime(19970): java.lang.RuntimeException: Error receiving broadcast Intent { act=gpapez.sfen.ROOT_GRANTED flg=0x10 } in gpapez.sfen.Receiver@44cdc4c8
09-09 08:38:34.298 E/AndroidRuntime(19970): at gpapez.sfen.Event.areEventConditionsMet(Event.java:732)
09-09 08:38:34.298 E/AndroidRuntime(19970): at gpapez.sfen.Event.areEventConditionsMet(Event.java:876)
09-09 08:38:34.298 E/AndroidRuntime(19970): at gpapez.sfen.BackgroundService.EventFinder(BackgroundService.java:387)
09-09 08:38:34.298 E/AndroidRuntime(19970): at gpapez.sfen.Receiver.onReceive(Receiver.java:386)
@lordgreg lordgreg added the bug label Sep 15, 2014
@lordgreg
Copy link
Owner Author

@gerhardol did you get this error anytime running sfen? Usually, it happens when switching cells or somewhere where there's no signal. There's no extra info to that. Now, that my phone isn't rooted anymore, I can't even see the logs which is even crappier.

@gerhardol
Copy link
Contributor

Not seen it, but I do not record error cells either in Sfen (hardly in
Llama wither).
On 17 Sep 2014 06:21, "Gregor" notifications@github.com wrote:

@gerhardol https://github.com/gerhardol did you get this error anytime
running sfen? Usually, it happens when switching cells or somewhere where
there's no signal. There's no extra info to that. Now, that my phone isn't
rooted anymore, I can't even see the logs which is even crappier.


Reply to this email directly or view it on GitHub
#62 (comment).

@lordgreg
Copy link
Owner Author

java.lang.RuntimeException: Error receiving broadcast Intent { act=gpapez.sfen.ALARM_TRIGGER flg=0x14 (has extras) } in gpapez.sfen.Receiver@42b59f50
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:782)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5579)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.IllegalStateException: Fragment FragmentEvent{429ee2d0} not attached to Activity
at android.app.Fragment.getResources(Fragment.java:767)
at android.app.Fragment.getString(Fragment.java:789)
at gpapez.sfen.FragmentEvent.refreshEventsView(FragmentEvent.java:151)
at gpapez.sfen.Receiver.onReceive(Receiver.java:336)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:772)
... 9 more

Fix fragmentevent error.

@lordgreg lordgreg self-assigned this Sep 23, 2014
@lordgreg lordgreg added this to the 1.1 milestone Sep 23, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants