I did a search here before posting this question. I did not find the answer.
When reporting an issue, like a boot loop, with a ROM, what files, if any should be captured before wiping/formatting?
For example, yesterday I installed the CM10.1 - WILD-FOR-THE-NIGHT-04082013-shooter.zip ROM. The phone was performing fantastic all day yesterday. I installed some apps and set things up. This morning, I decided to reboot the phone. Boot stuck at the CyanogenMod boot screen. I tried a battery pull, wiping cache & dalvik. Still the boot hang. I ended up formatting the 'data' partition then the phone successfully booted without having to reload the ROM.
I would have posted this in the CM10.1 thread in the development side but I'm not at my "10 posts" yet.
If you ever run into a bootloop or any issue like random reboots or a sudden FC of an app, the best thing for you to do IF you want to help that developer is this....
1. Provide as much information as possible about the issue.
Many users tend to think that by saying "my phone is getting random reboots" it helps BUT honestly, it does nothing at all!
In fact, think of it like if you took your car to the repair shop and said....my car makes a funny noise and ran out the repair shop! Do you think that would help the mechanics?
Unless they are wizards, I doubt it! Developers are not wizards either....clever individuals BUT not wizards
So when you're reporting an issue, state what you were doing to your phone if anything at all. What HBOOT, Kernel, CPU settings (min/max and governor) and just anything that you can think of! I personally would rather have MORE information then what I needed then not enough.
If is possible, provide a step by step of how to recreate the problem! Most developers love to able to recreate the issue on their phone so they can pull logcats of their own and test fixes
2. Along with providing vital information about your issue, there's also things that you may not know are happening in the background which might play a role in your issue.
This is where pulling a logcat is useful! Below is a link that goes into detail on what you need in order to pull a logcat and some useful information for you to read over as well...
http://forum.xda-developers.com/showthread.php?t=2141817
Related
Hey guys. as many of you know i am no stranger to the Android system, although i have been pretty much totally absent from the forums since i got a job with limited privelages on my comp.
Before I explain what happened to me, i should say that i have not made ANY changes to my system for at least 4 months, with the exception of build.prop updates, which i my phone has been running fine on for weeks. i found a setup i liked and ive been running it, along with the same root applications, for quite some time.
With that said, heres my timeline of events:
Normal day, doing what i always do on my phone everyday: phone was plugged in to a wall outlet at my desk. streaming music, browsing web, youtube, etc. nothing out of the ordinary
i first noticed something wierd was up when i went to install an old .apk i had saved on my sd card. i opened it through file manager which, naturally, brought up the stock package installer. i clicked ok to install, and it said "installing"..however it nevver finished. it was stuck on "installing" for several minutes. i tried a couple more times, same thing kept happening. i had no idea what was going on.
i went into settings>applications>manage applications. i scrolled down to package installer and clicked on it, with the intention of clearing cache/data, however the values never loaded, it just kept saying "computing". it was doing that for all other apps i checked as well.
then i opened titanium backup and wiped data for package installer through that. operation was performed successfully.
i went to reboot my phone, and thats the last thing it remembers. now whenever i try to turn my phone on, it gets past the kernel splash screen and its all black from there (i have the "no boot anamiation" command in my build.prop). the only response i get at that point is the led buttons will light up if i tap them. i have to pull the battery to turn the phone off/reboot.
i tried pushing packageinstaller.apk to /system/app using adb but that didnt solved anything. i also tried wiping cache/dalvik and fixing permissions through clockwork. nothing has worked.
i am running Froyo Trigger w/ Bali kernel.
sorry for the long post, but i figured id be as detailed as possible to minimize questions.
any suggestions would be great. i ask that no one please suggest factory reset/reflash/odin. i realize that those options are there, but i consider them last resorts. id rather brainstorm a solution than bail immediately.
thanks ahead.
also i forgot to mention, there was nothing wrong with the .apk i was originally trying to install. i have installed it/uninstalled it many times. i tested other .apk files i had, but package installer still behaved the same way
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Br1cK'd said:
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Click to expand...
Click to collapse
not sure if i should be embarrassed to admit this, but ive never used logcat...ill look into that
Your first step there is to get the android sdk setup on your pc, then once adb is part of your command line the simple command is "adb logcat" without it quotes. That will start the log displaying in the command line window.
There are other options with the logcat command, that output the log to a text document and its more in depth, but I dont remember it off the top of my head. Maybe someone can post it for you.
The only caveat is how far your phone is booting before it hangs, I think logcat will show something, but won't know for sure until you try it.
Sent from my ZenDroid, meditating on the XDA App
http://forum.xda-developers.com/showthread.php?t=1319802
Eugenes Froyo that doesn't brick, followed by an Odin to jfd.
Sent from my SGH-T959V using XDA App
I've been having crash events on my Galaxy Nexus, which creates bugreport text files and screen shots on a regular basis, not to mention popping up an Intent dialog asking me how I want to send crash info. It's an annoyance I'd like to correct, so I'm looking for ways to figure out and fix whatever is causing the problem.
Is there a good methodology I can run through to at least narrow down what software is throwing the errors and triggering bug reports? Failing that, is there a decent way to suppress them?
The crashes aren't predicable and seem to occur regardless of what app I'm currently using. Some (I think) occur when I'm not using the phone, and produce a screenshot of my lockscreen as debug info. I've done a fair amount of tinkering, including basic programming in Eclipse, so I'm wondering if I can use LogCat or some other debug tool to observe a crash. Or if I can look for a specific line of the 4 meg bugreport.txt to find what process is freaking. I just don't have enough experience with analyzing when things go wrong to know where to look.
Some simple facts about my case if you're interested in offering opinions:
-Been rooted on the Nexus for ages, but crashes only started fairly recently.
-Started roughly when (give or take a few days) I flashed to stock 4.0.4 and latest Verizon radios, because my collection of mods (maybe Clockwork Recovery) was preventing an OTA update from succeeding. Interestingly, it continued after doing a SuperWipe (of absolutely everything) and flashing in Jelly Bean with stock kernel.
-The radios were reflashed, but are the same between 4.0.4 and 4.1
-All the apps I use are all installed on both OS's. I don't particularly want to go through the time required to remove apps, wait for crashes, and reload them, particularly if there is a quicker solution.
I'm having the same issue. It has persisted through multiple re-images and wipes so It has to be something that I reload on the system, but I cannot figure out what it is...
I've tried digging through the crash reports and watching logcat but i haven't been able to reproduce the crashes on demand...
Update: Actually I have a theory that these crashes may actually be related to Google Wallet. My Secure Element is locked, but i don't have a need for wallet anyhow so I never got my device replaced. I don't remember having this issue before I switched my GNex to the Takju ROM (which included Wallet). This would also explain why the issue seems to persist between wipes (Each ROM I've loaded has always had Wallet pre-installed). I'm going to try using Titanium Backup to freeze Wallet and see if I get anymore crashes. I'll keep you posted.
Resolution:
The bug reports are being generated when USB Debugging is on and Volume Up, Volume Down, and Power are all hit. For me, this was happening frequently because my TPU case is fairly tight and it depresses the volume keys inadvertently.
Thread where I found the problem: http://forum.xda-developers.com/showthread.php?t=1451521
I create this thread to track the issue and want to get any idea and fix on the random reboot of CM10 series (it looks the Cm10.1 also has this issue).
One major problem is reading the CPU OM file (/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state, please find the details reporting in below link). This problem can be fixed in framework.jar by increasing the buffer. I have done for it and the frequency of reboot is down. But still have some random reboots....., disappointed.
https://code.google.com/p/android/issues/detail?id=9733
Remaining reboots will cause the screen in yellow and then reboot. Please find the details in below two links (one is reporting to CM bug tracking, but no one take care of it.).
https://jira.cyanogenmod.org/browse/CYAN-388
http://forum.cyanogenmod.com/topic/61997-cm10-freeze-yellow-screen-reboot-issue/
Also find someone had already reported this issue in XDA (http://forum.xda-developers.com/showthread.php?t=2301552) but cannot get the answer..., disappointed.
The problem is how to get the log for this issue? It will break logcat working since the reboot running.
Is there any idea or suggestion for this issue. Thank you so much!!!
If you want a log after a reboot, the file last_kmsg is used. http://forum.xda-developers.com/showthread.php?t=2093987
Good luck with your endeavor.
A bug report from 2011 is very unlikely relevant to recent ROMs, for one, unless you know for sure this buffer bug is still an issue and is not otherwise accounted for. And the 'yellow screen reboot' could be any number of things, but feel free to get something like a USB serial device going and really do some debugging on it.
You can be disappointed all you want, patches welcome...
I have a T Mobile GS5 which I Towel-rooted soon after purchase. It is currently running the stock NE6 build.
I wanted to upgrade w/ the Mobile Odin app and maintain root. However, after paying for and installing Mobile Odin (4.20), when I open the app, it immediately crashes and says it has stopped working. Given the option to report the failure or close, I chose to report. This returns a message that the google play store has stopped working.
Am I just being stupd? I have searched high and low for some similar posting or support and can find nothing.
Any suggestions?
Thanks for any help.....
..
fffft said:
Everyone says that they have searched, whether they have or not. It's too bad that you didn't tell us how you tried to search. Or what keywords you used, we could have helped you improve your searches. There are a ton of xxxx (app) has stopped working threads, so it's difficult to understand how you didn't find any.
You should have a second look as there is a wealth of information in existing threads. But to summarize briefly, you can try these steps -
You may not have installed the support files properly. Read the directions carefully and reinstall the app.
Try wiping your cache from recovery mode.
Clear the app's cache and data in the application manger in the settings menu.
As a last resort, close any background apps that may be causing a conflict.
.
Click to expand...
Click to collapse
in the three + weeks since I loaded the program have searched thru quite a few key words, including the exact error message, combinations of odin not working, tmobile mobile odin not working, ad nauseum. None of the threads I saw, and there were many, addressed odin not opening at all. Never since loading. Most folks have issues w/ flashing the wrong types of files, or not checking some box. I have never seen the odin screen. And in any search I have never seen that problem described.
When you say supporting files, what are you referring to? I know that the MO lite offered here requires supporting files, but I paid for mine, didnt know it wasnt complete. I tried loading up the lite version and got the same thing, instant shutdown. Makes me think that it is not an issue with MO but maybe something on my phone. Are you aware of any background apps which may cause conflict? I cleared the MO cache and data. Also forced a stop and rebooted. And removed/reinstalled.
So by posting here, I am not really looking to refine my searches so much as looking for someone who maybe had the same issue, overcame it, and is willing to share that insight to relieve my stupidity. I guess that wouldn't be you, although I appreciate your thoughts on the subject.
..
fffft said:
I appreciate your forthright candor. It's not possible to help everyone, so I choose to put my time towards helping those who tried to search the forum before posting. Just as you prefer to have someone who has been through the same experience provide you the answer. I'm not sure that is an efficient strategy except for the most common problems.
The likely solution is as I summarized earlier for any app that presents a ".. stopped working" message. Perhaps as you hope, someone who has had the same issue can further advise you. Good luck.
.
Click to expand...
Click to collapse
After going back and reading some more, something hit me, it was always kinda right there......
Looking at the screenshot of the MO display, i noticed the 'clear dalvik cache' command. Reminded me that I had been screwing around and had turned ART on to see how it ran. Wonder where the 'clear art cache' box is..............oh.
Turned dalvik back on, runs like a champ. just downloaded the addons, opened the tar I had on the external sd and I think I'm ready.
As I never did see a thread referring to this specific issue I figured I would document for the forum's info.
I appreciate you taking the time to respond.
had the same problem
Rev_zero said:
After going back and reading some more, something hit me, it was always kinda right there......
Looking at the screenshot of the MO display, i noticed the 'clear dalvik cache' command. Reminded me that I had been screwing around and had turned ART on to see how it ran. Wonder where the 'clear art cache' box is..............oh.
Turned dalvik back on, runs like a champ. just downloaded the addons, opened the tar I had on the external sd and I think I'm ready.
As I never did see a thread referring to this specific issue I figured I would document for the forum's info.
I appreciate you taking the time to respond.
Click to expand...
Click to collapse
I ran into the same problem. So, no need to feel stupid and im glad to see u realized the problem.
Its a learning process. Lol
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.