Every time I install or update an app, my phone (running 5.0 aosp lollipop with xposed) tends to soft reboot, it doesn't always happen and it doesn't always happen just when installing an app (sometimes it just does it while watching a video for instance) but it's driving me crazy. I think this could be because of the memory leak (so that my phone reboots because of a lack of RAM), but maybe it's just an app causing the trouble. Could someone please take a look at it for me? I attached two logcats. Thanks in advance!
here they are
Humpie said:
here they are
Click to expand...
Click to collapse
With random reboots, first place to look is kernel, then Xposed, then ROM.
If you are running stock, remove Xposed.
Wiping cache and dalvic cache solved the problem!
Now I know what to do when it reoccurs
Related
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
jdubsss said:
This started occurring last night when I was using Winamp to sync music files to my phone. Every 10% or so the phone would reboot itself and I'd have to start the entire process over. Since then, I've been getting random reboots while doing anything from typing an e-mail to closing an app and haven't been able to narrow it down to anything specific.
So far I've tried
1) Removing my external sd card
2) Uninstalling numerous apps to try an pinpoint one causing an issue
3) Underclock from the 1.9 ghz the rom comes with
4) Removing the battery
5) Reflashing the latest nightly, clearing cashe and dalvik
Anyone have any idea on how I can try to resolve this? I love the phone and the ROM, but I can't deal with random reboots while just using my phone normally.
Thanks in advance.
Click to expand...
Click to collapse
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
adoublearonn said:
I had this problem too with the latest release, even after reflashing it, and it even popped up randomly like your issue after using the ROM for a while. All of the sudden random reboots all the time. I went back to R64. I think there is a different kernel in some of the newer releases or some change, I don't really know, but R64 has been running perfect all around and hasn't rebooted once on me. You may be able to dirty flash back to 64, I don't know if it will work because I didn't try it, but I do know a clean flash fixed it for me. If it's just kernel issues then dirty flash should work as usual.
Click to expand...
Click to collapse
Thanks for the reply. I flashed leankernel tonight and so far so good... time will tell though.
Since yesterday my n8010 started to act slower and to stutter. I'm assuming i installed something that is causing this problem but i don't have an idea how to figure out what is causing it.
How would one start to analyze?
S.Phrenic said:
Since yesterday my n8010 started to act slower and to stutter. I'm assuming i installed something that is causing this problem but i don't have an idea how to figure out what is causing it.
How would one start to analyze?
Click to expand...
Click to collapse
Try to install OS Monitor and check which app Is using the most CPU power. And de install the latest app u've installed.
I've installed OS Monitor... didn't show much interesting stuff... i did deinstall some live wallpapers (wallpapers that weren't active) and that helped a bit.. still, not as smooth as it was before.
Thx for the tips
If you have it rooted and CWM installed, try wiping cache and dalvik cache.... There may be some bad code still floating around in there causing issues. If you don't have CWM don't do this.
A reboot might help also....
A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck
Hi everyone,
my Mate 7 has a tendency to do unexpected, spontaneous forced reboots every now and then. I have no idea what causes it. Recently, it happened multiple times while trying to scan my phone for viruses using the Avira app. Today, I tried to launch 3C Toolbox when it happened.
Any ideas? For info, I run firmware B137SP3 and am rooted with SuperUser.
Have U already tried a device reset and a clean install of thr firmware? Monitorize it after clean install without any other app (no 3rd party apps, just stock apps). If stable, ok it' s not a matter of firmware. Then proceede by installing your apps one by one and monitorize which one of those let the phone reboot.
tuddu said:
Have U already tried a device reset and a clean install of thr firmware? Monitorize it after clean install without any other app (no 3rd party apps, just stock apps). If stable, ok it' s not a matter of firmware. Then proceede by installing your apps one by one and monitorize which one of those let the phone reboot.
Click to expand...
Click to collapse
No, haven't tried that yet. I was afraid this might be the only way to find out what's happening. Since the reboots occur only sporadically (less than once a day), I'll postpone this for when I upgrade to Lollipop - which will require a clean system install anyway.
Thanks for the suggestion though!
How about wiping the cache?
PoisonNinja said:
How about wiping the cache?
Click to expand...
Click to collapse
App cache or cache partition? I have 3C Toolbox installed which automatically wipes all app caches upon reboot.
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
I have the same problem with craching and rebooting on both Tab2`s in the house.
One completly stock and one with CM11.
Mabye an faulty app ?
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Well, it is happening with everyone, the apps have become memory hungry and our devices lack RAM, andoid L, and our device kernel is full of bloatwares, our devs are trying very hard to overcome this, and we hope they will succeed in this too.
many people are of the view that android M has better management of ram, and I have seen in other devices that have confirmed they are experiencing better stability than lollipop. well on our device it's still in alpha stage, so wait and watch. till then keep your tab less burdened.
Steveh8204 said:
I have an occasional problem where my tablet will be loading an app (different apps) and it just freezes and then reboots.
Its running different apps so hard to pin down. Ive flashed the latest rom build (12.1-20160119-2048-UNOFFICIAL-P5110 at the moment) several times and its been the same through them all. Its also occured on previous roms.
What is the easiest way to diagnose the problem as I believe logcat resets after the forced reboot so I havent a clue how to diagnose it.
Could it be the Recovery or the Kernel that need updating?
Click to expand...
Click to collapse
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Zte blade l said:
Try changing SElinux to enforcing.
It helped me in my P3110.
HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Steveh8204 said:
Hi, thanks for the reply but how the hell do you do that lol
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
No need for that, just follow the original thread, bugs have been squashed. There are no more random reboots on latest builds.