Reputation
Top tag
Next privilege 125 Rep.
Vote down
Badges
2 3 11
Impact
~35k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Jan
6
awarded  Famous Question
Nov
26
awarded  Nice Question
Nov
23
awarded  Famous Question
Sep
24
awarded  Autobiographer
Nov
15
awarded  Notable Question
Feb
5
awarded  Notable Question
Feb
4
awarded  Popular Question
Jan
31
awarded  Notable Question
Nov
12
awarded  Popular Question
Nov
6
awarded  Popular Question
Aug
1
awarded  Scholar
Jul
26
awarded  Supporter
Jul
25
awarded  Commentator
Jul
25
comment Debugging bootloop: Get an information log without ADB? Can an emulator help?
I've edited my post to reflect more specific system details.
Jul
25
awarded  Editor
Jul
25
revised Debugging bootloop: Get an information log without ADB? Can an emulator help?
added 118 characters in body
Jul
25
asked Debugging bootloop: Get an information log without ADB? Can an emulator help?
Jul
25
comment Does the Android emulator generate some sort of log file I can access if it crashes?
This is great information (as well as the posts you reference). However, it seems there's one massive wall every developer is going to run into: what about a BOOT-LOOP? You're phone (or emulator) crashes as it boots up with your installed image, and keeps trying to reboot, but keeps crashing. How do you get kernel messages or any kind of log to figure out how far the phone gets?
Jul
25
comment Does the Android emulator generate some sort of log file I can access if it crashes?
Yeah but it just says <waiting for device>. And if the emulator is simulating the phone crashing, does the emulator itself produce any log messages?
Jul
25
asked Does the Android emulator generate some sort of log file I can access if it crashes?