pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
attaripatel said:
pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
Click to expand...
Click to collapse
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
very difficult to understand
It_ler said:
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
Click to expand...
Click to collapse
very difficult tounderstand pls give me sugestion what i can dosimply to avoid this
Related
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Not really a simple way to troubleshoot that. Did you do a full wipe prior to flashing whatever ROM you're running? Trying booting into recovery and wiping dalvik/cache, that can fix plenty of small issues.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
bluephi1914 said:
i have been experiencing some force closes and random restarted, is there a program that can tell me what caused it or what app caused the error.
Click to expand...
Click to collapse
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
joeykrim said:
Yes, there is a way but it requires a bit of technical knowledge. Assuming you have the motivation, acquiring the knowledge shouldn't be an issue.
If you're familiar with how to use ADB (Android Debug Bridge), this program allows you to access a log Android creates on the device where all applications output errors, debug, warning and verbose information.
From the command line, you'd run, adb logcat or adb shell logcat. If you prefer to have a bit of a GUI, run ddms which is also packaged inside the Android SDK.
There is an Android application called aLogCat for free in the Android Market which offers a GUI on the device for viewing this information. Feel free to also try this method and see which works best for you.
Essentially, this log will contain a lot of information. HTC coders seem to lean on the side of outputing a lot of information.
This log is real time, it will scroll as the applications output information. The best way to find the FC is to trigger the FC and immediately look in logcat for the details. They should be flagged by E, for error, followed by some type of name convention for the application. There will generally be anywhere from 5-15 lines of output in logcat when an application force closes.
Once you're able to locate the FC error output in logcat, feel free to post back up here and we can attempt to give some feedback.
Understand, sometimes the issue is the result of the application developer's poor coding or not being able to forsee a potential error. Other times, the solution is as simple as wiping dalvik-cache or wiping the application's settings causing it to start again from scratch.
Hope that helps! Good luck!
Click to expand...
Click to collapse
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
il Duce said:
yes, logcat will show you, but you have to kinda know what you're looking for. There are some logcat apps on the market or you can logcat through ADB.
Also, random app FCs aren't all that weird, BUT if you are getting them consistently you could very likely fix it by fixing permissions in recovery.
If you fix perms and the issues persist, feel free to pull a logcat of the app crash, and either PM me the .txt file or link it here via pastebin.com. I am no expert but I could try to help. But again, fix perms first, that'll probably work.
Click to expand...
Click to collapse
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
Try to use the Fix Permissions Opinion in the Rom Manager App! That May Help...
Here's a Screenshot...
PMGRANDS said:
Here's a Screenshot...
Click to expand...
Click to collapse
Ok.. downloaded ROM Manager and ran Fix Permissions. Hopefully that will fix any issues that I had.
bluephi1914 said:
YOU HAVE GOT TO BE KIDDING ME... LOL as soon as i typed "adb logcat" at the command prompt in windows, the screen immediately fills up... and like you said its real time so it doesn't stop.
When "ADB logcat" is typed how far does this log go back. I think i typed it about 5-10 minutes after the restart....or random hot reboot. was this to long ???
Most of the lines begin with D/ or I/ or or V/ didn't see any E .... but im currently scrolling back through all of the output in the CMD screen, i had to unplug the phone to get it to stop scrolling.
Click to expand...
Click to collapse
D is debug, I is Information, V is verbose and E is Error. All FC messages will start with E although, sometimes other logcat information will help make the FC easier to understand. I usually gather them all around a specific FC and narrow it down as I go.
I don't recall the buffer limit size to logcat, but it is generally best to grab the logcat as soon as the FC issue occurs, that way the issue will be closest to the end of the buffer. This makes it easier to locate and less likely to be pushed out of the buffer.
bluephi1914 said:
typing "ADB logcat" from the command prompt in windows doesn't give me a .txt file does it?
Click to expand...
Click to collapse
no, by default it updates the screen in real time, to have it dump to a text file, adb logcat > logcat.txt . you might need to hit cntrl+c to stop it as it will continue to write in real time to the log file until you exit. the exit command is cntrl + c to kill the process, same as exiting.
Hope that helps arm you with another skill!
edit: in the last month since i originally posted my first answer, i found an application on the market, which is essentially a GUI for logcat called aLogCat. the developer open sourced his code and the application started in 2009. seems to work very well.
source code: http://code.google.com/p/alogcat
So,
SGS users, here is my another thread, for guys, who want to help devs of our sgs community.
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided.
Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> Very Easy
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> Almost Easy
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> Medium
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
CREDITS
CRESITS ;
I) @Niku-Droid
II)www.google.com
III) XDA Threads, as this information is taken up from threads of XDA only
Oh! I missed someone, Send me a PM
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
T3snake said:
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Niku-Droid said:
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Click to expand...
Click to collapse
of course i used adb
i want to take logcat while star is booting
but device doesnt show in adb until the booting is complete
When the projection function is turned on, the phone will reboot.
Sorry, I am a Taiwanese, so my English is not very good. I hope you can understand.
My whyre will restart whenever the projection function is turned on. This problem is very annoying because I use it often.
I hope that ArrowOS can be more perfect in Chinese culture, otherwise it will be difficult for my newbie, and how do you solve the 4G signal problem?
I use a lot of OS, but their 4G can't work, which makes me very troubled. As a geek, I want to learn how to deal with this.
The system you made is really great, I like it very much, I hope you will surpass PE.
how can solve no internet problem?
how can solve no internet problem?
Network problem on moto g4 plus of version Arrow Os 9
Doesn't access network problem while installed
The connection to my smartwatch dosnt work.
the bug that I found for the moment was that it does not allow changing the file transfer mode when connecting the usb cable to the computer
Niku-Droid said:
Кодlogcat -v long > /sdcard/test.log
Click to expand...
Click to collapse
Although I've made fundamental protection in the Xposed module of Greenify (especially in 2.6 beta 10), some of you are still experiencing bootloop if experimental Xposed-based features are activated.
It's really hard to dig these issue without logcat since Android devices and ROMs are highly diverse (fragmented). But logcat in the bootloop case is understandable harder to capture than regular crash issues.
If you are one of the bootloop victims, and would like to help me on this issue. Please follow this instructions to capture a proper logcat for the bootloop issue:
1. Download and install ADB tool, either as standalone package or from the Android SDK.
2. Connect your device with a PC or laptop with USB cable.
3. Enable developer options on your device. (this must be done before the bootloop happens)
4. Test logcat capturing by typing this command in shell (or command prompt): "adb logcat -v time -d" (without quote marks), if you see plenty of log scrolling through the screen and finished, it's ready.
5. Trigger the bootloop, then after the device reboot, type this command in shell: "adb logcat -v time > logcat.txt", if you read "waiting for device" and the command continues running, that's OK.
6. Wait until the last command to finish and return to the shell, then you will get a "logcat.txt" file in the current path (usually the root path of your user home / folder). Send it to me via email (or pastebin.com).
If the command does not finish in a long time, just press "Ctrl + C" to end it, and send me the logcat.txt if it's not empty.
Thanks very much for your effort to help diagnosing this issue.
I had some severe boot loops on a CM12 device last night, I think it was just soft reboots not hard (no way to confirm it, sorry). It was running in root mode. I think a play store update cured that one. The SuperSU logs confirmed it was the item requesting access just before soft reboot.
I also had severe soft boot loops on my Moto X OTA 4.4.4, running in boost mode. Updating from play store (to 2.6.1), or disabling the xposed module auth for Greenify would not fix it. Only blocking SuperSU access fixed it. I just verified that granting SU back again to Greenify immediately causes soft boot loop.
Unfortunately, the effected device is a work unit with sensitive information, so I cannot post anything. I can try limited requests if you have any.
Waking a hibernated system app (Spotlight Player) caused a soft reboot, but it appears its working properly now going back into hib and back.
Good evening all.. Just looking for some help if possible. I absolutely love Remix OS and I am really enjoying it so far. I have a dell inspirion 3000 11 inch 2 in 1 laptop. Everything works like a champ and its super smooth. I've installed to my hard drive with a window 10 dual boot. My issue is this: It will randomly just freeze, no matter what I am doing. browsing the web, looking at settings, watching a video, etc. It just freezes and then i have to hold the power button down to reboot. (is there a shortcut key or something to try to kill a task or is the power button the only option?) does anyone else have this issue? I've tried the latest update and that seemed to make it worse, so i downgraded but it still happens from time to time.
Any help or advice would be wonderful.
If you're using a Nvidia GPU, it's most probably a nouveau driver issue that will be fixed in the next kernel update.. Most probably in the next 1-2 updates.
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Vioner said:
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Click to expand...
Click to collapse
I had the freezing issue (because of nouveau) before and the problem is that all the system freezes that ALT+F1 doesn't work anymore
@modaifallah please read my signature
Back to the thread: His GPU is intel.
Sent from mobile
Thanks for your help so far.. I actually reinstalled the newest, from the torrent instead of OTA. No issues as of yet, but will try your guide when and if I do, then will follow up.
Downgrade to Remix OS 3.0.102 and freezing problem is gone, and az screen recorder is working fine to. Gpu driver on latest mesa Remix OS is buggy
My smartphone was written a third-party image and installed Magisk and some modules. But attempts to launching the screen after a long idle time (the screen is black) will cause System UI into "Not responding" status. For example, I set an alarm clock at night, and in the morning, the smartphone will ring normally but the screen cannot work, not responding with any clicks. Then for about a minute I can just long press the power key and choose to restart or shut down (in this occasion the UI goes into another style, not the same as MIUI's). Sometimes clicking and pressing the buttons madly will cause a small window which reads "System UI is not responding". Restarting, shutting down and choosing to relaunch the System UI in that window will fix the problem temporarily.
I think the problem may be confused and complicated because of the third-party system and those Magisk modules. I am just waiting for a way to extract the useful logs or to debug it, thus helping me to open an issue to the system developers.
Send out the logcat by executing' ADB logcat' and upload the resultant file here.
LR7875 said:
Send out the logcat by executing' ADB logcat' and upload the resultant file here.
Click to expand...
Click to collapse
Should I execute the command immediately after a UI crash? Or any time?
Little_Ye233 said:
Should I execute the command immediately after a UI crash? Or any time?
Click to expand...
Click to collapse
Execute this command when you faced a ui crash and uses the 'system ui not responding' window to solve it(do not reboot), and unlocked the phone.
LR7875 said:
Send out the logcat by executing' ADB logcat' and upload the resultant file here.
Click to expand...
Click to collapse
Should I execute the command immediately after a UI crash? Or any time
LR7875 said:
Execute this command when you faced a ui crash and uses the 'system ui not responding' window to solve it(do not reboot), and unlocked the phone.
Click to expand...
Click to collapse
OK, I will do it on tomorrow morning.
LR7875 said:
Execute this command when you faced a ui crash and uses the 'system ui not responding' window to solve it(do not reboot), and unlocked the phone.
Click to expand...
Click to collapse
I'm sorry to make you wait for a long time! The attachment is the logcat file. It contains two crashes today and yesterday. Today's crash was on around 6:50 and yesterday's was on around 6:00.
It's a pity that I didn't set an alarm clock yesterday and today's crash didn't last long. The screen revived from the crash just after I clicked several times. Maybe it's the clock that just slows down the device.
[logcat_2.log](https://raw.githubusercontent.com/filearchives/filearchives.github.io/main/logcat_2.log)
[DELETED]