So You installed your shinny new rom It booted (mabe it didnt) And your salivating over your phone like its a shinny new toy. And whoops something goes wrong. Applicaton closes rom wont boot so on so forth. You go to post that you have a issue with the rom.
First off A NOOB
Will make countless threads over and over again Sometimes in the correct fourm most the time will not about that they cant get this to work.
Example title This rom blows help meeeeeeee i cant stall my hacked leet files rom is buserd..
body of text example
UR romz brokz ma aps fix it..
For all intents and prupose this thread is pointless not only should it be closed but the Poster should honestly go stick to stock. As they are a NOOB and prob for the first point didnt follow directions.
NOW THATS OUT OF THE WAY HERES THE PROPER WAY TO SUBMIT A BUG REPORT SO WE CAN FIX YOUR ISSUES OR AT LEAST TRY TO.
First off Get ADb shell.. Not only is it great for dev's its also great for you guys to send us stuff we to help u get your new shinny toy runnning.
Second off
http://developer.android.com/guide/developing/tools/logcat.html
^^^^learn it love it it it gives you logs. Yes crash logs app logs pretty much anything your android phone logs we can have u pull it out.
^^^THIS IS WHAT IS HELPFULL IN A BUG REPORT.^^^
Steps to proper bug report
FIRST OFF POST IN THE PROPER FOURM AND GASP THE PROPER THREAD U KNOW THE THREAD U GOT YOUR SHINNY NEW ROM FROM.
Second When you post be decriptive what were you doing when the rom crashed.
Did you try a phone reset? Yes No
Did clearing the cache and davak cash and fix premissons help via cwm?
Please list any and all tried.
IF these steps were done Does the crash still happen?
IF so
CRASH REPORT TIME
Put your phone in debug mode then connect to pc
Then navagate in dos to where ever you have your adb installed to
$ adb logcat
-f <filename> Writes log message output to <filename>. The default is stdout.
-v <format> Sets the output format for log messages. The default is brief format.
those 2 options are very handy
once you have your log file
ATTACH IT TO YOUR POST!!!!
We will look at the log's if we find out we need more info we can have you run logcat and change the format from brief to a more detailed format so we can better get an idea of whats going on.
Thank you!!!
Ps last note If its a issue we already know about hince its in the bug report and chainlog Please dont post over n over that this is broken when we already know it is thank u
Love your devs!
Hi Need some advice here. Yesterday i have successful upgrade my SGS2 firmware to the latest by using latest Kies (Country : Malaysia). But after that my SGS2 keep restarting after a message pop up : Sorry, you encountered network error. Please verify your connection and try again.
Later that i spend a lot of time and figure out it was actually crash on some of my existed application after the firmware upgrade. My SGS2 has totally of 134 applications, i am headache to figure out which application is actually cause the restarting . As such i tried to divide the application into 4 section (134/4) to transfer into the .android_secure folder. The first section successfully transferred without any restart issue. But the second , third and forth section having restarting issues. As you know that the .asec are not allow to copy by using usb cable. So every time i do the remove and move in the files and sd card to phone i totally spend more than 20 times to do this. But haven't finish figure out the culprit application.
If you have better solution for this case, please highly advice me. I scare i keep remove and move in the sd card will cause my phone hardware failure one day . Appreciate a lot.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Really need some help now. I am not sure is it cause by my router setting? Or what?? Due to too many application will cause the restarting issue, then i have not copy back some of the old application back to phone. What i did is reinstall back from the android market . The phone have been stable for awhile until i tried to open an old application which will link to a youtube page, then the same error message (refer to red word on the first thread above) and same restarting again..... huhu... now the thing make me so confuse is , is this cause by my router setting more or the latest firmware is not stable enough??? .... Anyone please advice. I am Malaysian and using Malaysia firmware to upgrade. You may check if there is a bug in the latest firmware version ( i couldn't remember the version).
Thanks and appreciate.
Hello,
I am wondering if you could help me with random reboots of my phone. I tried to get the last ksmsg but i got this:
HTML:
/system/bin/sh: cat: /proc/last_kmsg: No such file or directory
What can I do to find the message?
Currently in the proces of taking a logcat, but I am not sure my phone will crash.
Apart from the crash I really love this ROM
Hello again.
It crashed again, I had logging on with catlog and I got the last_kmsg. You can find the links to the logs here:
https://www.dropbox.com/s/1kefqyw5lnwd8td/lastkmsg.txt
and
https://www.dropbox.com/s/2qd2d00zrvbr4s3/logs_lastminute.txt
Am I doing this right? Maybe pastebin would be better?
I can't post in the thread in Android Development because of my post count and that is why I post here.
I hope that frankinstine will see this. Catlog ran for 2 days, log ended up 19MB big
Thank you for your time.
Hello,
me again.
Had a 5 or more crashes. This is the log https://www.dropbox.com/s/33hysl724mvb3n4/lastmsg2.txt
I don't know if you can see anything from it
I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Att.Fan1982 said:
I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Click to expand...
Click to collapse
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Att.Fan1982 said:
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Click to expand...
Click to collapse
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Mr hOaX said:
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Click to expand...
Click to collapse
Thanks, I'm restoring my stock root backup now in twrp recovery & will post my results if this solved the issue or not
Edit: No luck on the stock root screenshot either, guess I'll just have to live with the fact I can't take a screenshot on my device, at least until a definitive solution is found
Okay, latest update..........I did a factory restore + unroot using bacon root toolkit then re-rooted my device using the same toolkit & restored my nandroid of my last rom and................................................................................................................................................great news screenshots are working now! :good:
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
Even I am facing the same problem after updating CM12 latest version yesterday. Please help
I had this tonight on COS 12.1. A reboot cleared it for now.
I am having the same problem but got fed up searching a fix , I felt a waste of time searching for it too afterall how many times do we use that feature. i downloaded a third party app for the same & its working like a charm. Problem solved
Screenshot Issue
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
For now, screenshots work after renaming pictures to pictures 2 but I am unable to delete my pictures 2 now. There is a file name screenshot inside(not image). Any suggestions how to delete this?
Thank you.
saqlainsyed007 said:
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
Click to expand...
Click to collapse
Hi Guys,
Seems the internal memory permission has been jumbled up and you need to fire the following command to restore the same. Connect with adb while booted in recovery and run the following commands to correct the permissions. After that your problem might get solved:
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
Thanks
hey there guys,
my z3 keeps restarting itself every now an then, sometimes it's 5 minutes after a reboot sometimes it takes a few hours. Tried everything so far to see if it's software related: flashed concept, mm beta, completely wiped internal storage with flashtool when installing new rom, leaving it completely stock for a few days without root but nothing, also tried another sim card but nothing has helped so far, also in /proc there's no last_kmsg created so everything i found on logs so far was in data/system/dropbox
http://pastebin.com/N5FN078X
this was the only last_kmsg log i found so far maybe someone can find something in this log, would really appreciate any help :highfive:
Hi,
A few times ago my CyanogenMod also does some 'random reboots'.
The cyanogenmod logo appears but not the sony logo: it was just 'soft' reboot.
You can check this in your dmesg after reboot:
Code:
dmesg | tail
The numbers of seconds could give you this information. Then you can dump the dmesg.
Another thing I ran:
Code:
logcat > /storage/sdcard1/log
If your phone does a real reboot maybe you can see something. But warning logcat is really verbose so it writes a lot to the sdcard and file can grow fast.
Hope it help and sorry if some words are not the right ones