OK I thought i could start a thread with ways that we can minimize the replay of reboot or freeze problems. Just a solution till LG comes up with a magic patch!
I managed to minimize the reboots by installing Launcher Pro and by not start (after Reset) the Antivirus Crap.
Also I managed to minimize to 1 freezing per 10 charges by charging with different method. (ex. USB , Hub to PC, or other manufacturer) .
Newest CM7 is very stable, not a hiccup all day
I never got the black screen of death early on while owning my phone. It wasn't until a few days in it began happening. It got particularly bad yesterday so I reinstalled CM7 nightly and wiped my battery stats through clockwork recovery. I haven't had a blackscreen for 10 hours now.
Yesterday, did you install #15 by any chance? I found it to be really unstable, #16 is miles better.
Yea, 15 was quite unstable until I reinstalled it a 2nd time. 16 is quite stable so far. I think a general rule to follow would be to reinstall if you find it unstable. If it keeps messing up just hop back to the last stable build.
I haven't has a reboot or lock up since UNINSTALLING juice defender. If that helps
Mine started rebooting after 2 weeks. I had about 10 reboots a day.
But uninstalling juicedefender did the trick for me as well! Finally no reboots anymore!
I havent used Juice Defender, and i dont have any reboots, no lockups or anything..
I just rooted the device + used Root Explorer to remove all the bloatware
Mjuksel said:
I havent used Juice Defender, and i dont have any reboots, no lockups or anything..
I just rooted the device + used Root Explorer to remove all the bloatware
Click to expand...
Click to collapse
Did you rooted from day 1?
Why you didn't update to 10d?
i dont even know how to update lol
i just rooted it with 1click (link in signature) and removed all the crap
it was about a week after i got the phone i think..
without the rooting i also didnt have any reboots or whatsoever.. a little lag occasionally but thats all
after I removed all those memory management apps, task killer apps,
I have no problem again. just try it yourself.
I was advised by a friend whos been using android for a long time NOT to use TaskKiller and stuff..
By just letting all the Apps run, the system is more stable..
Just remove the unnecessary ****
I'm using the stock v10b ( v10d not available in belgium... ) and i had several freeze after using some intensive apps like games or navigation ( screen keep working but nothing respond ). The wierdest is that i can play on the app for long time and once i come back to the home, my phone freeze.
I would like to remove all the crap stuff running but i couldn't find how to uninstall permantly some apps ( like the twitter app ... ). Do i need to root it ?
About reboot. I put some video file on SD card and my phone starts rebooting. I deleted that file and everything is ok. The reboot is started by SD Media Scan. Since then(1-2 months), no reboots.
After I rooted the phone and frooze some bloatware. I didn't have any freezes or reboots at all. U use also juice defender and autokiller. So I can do two days without a charge.
Sent from my LG-P990 using Tapatalk
Related
I am on SGS #2 atm and im trying to stress test it using the HD video method. I have noticed random apps starting to FC. I guess my real question is, Are there certain apps that are more likely to FC compared to others? I noticed the phone gets REALLY slow at loading as it reaches the drive capacity, however, once i delete all the junk videos, the speed returns to normal. Ive also noticed the FC happens when i open too man apps.
Are there any other clear indicators?
Thanks!
Yes,
It's about to go.
Fair well~
Mine did that not too long ago. I was playing Game Dev Story and it got all laggy. So i reboot and i started getting loads of force closes. COuldnt even boot because LauncherPro kept fc. so i reset to factory and speed came back and no fc so far ( maybe one per day..) Strangely , this came right after flash from ODIN for the first time. Although i only flashed a new KERNEL which is speedmod. I NEVER had any problems before that and had my phone since OCT. Anyways, updated to K12O and still on a stock - rooted JL2. Lets pray for the better!
Yep.
Mine started to force close on my email app. Then when I got it working, I tried to attach a photo to an email when the email and picture gallery crashed. Restarted the phone and I kept getting all kinds of FC's on different apps every 1 minute or so. Reinserted the battery, turned it on and it was all over.
I just want the damn thing to die so i can send it in for a new one from samsung...
sleeplessfreek said:
I just want the damn thing to die so i can send it in for a new one from samsung...
Click to expand...
Click to collapse
Well the last thing that did it for me was I had backed up all my apps with myroot then formatted the internal card. Loaded all my apps back to my phone, then I did a mass update on all the apps at the same time. That's when my phone was unresponsive and FC's occurred consistently until the entire phone crashed.
I have a rooted, original Droid. I keep running into the same problem every time I install a new ROM. It always works great right off the bat, but after a few weeks or so, my phone has slowed down to the point that it's nearly unusable. Everything about it is slow: Apps load slowly, the browser is too slow for use, I'm constantly getting notified that different processes aren't responding, etc... So far, the only solution is install a fresh ROM every month.
I've tried loads of ROMs to see if it's a problem with my phone or with a certain ROM. Each new ROM does the same thing: Works great at first and then slows waaay down.
Anyone have any ideas? I've tried memory optimizers, removed all unnecessary apps, SetCPU profiles, and more. I've tried it with task killers, and without task killers. Regardless of what I do, I always have the same problem. Anyone else?
reboot the phone every 3 days
works on my milestone
I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA
Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.
It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA
Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA
So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.
I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.
It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"
Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!
ryunbaik said:
Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!
Click to expand...
Click to collapse
Hi
So you want to say SuperSu fixed your SOD?
What are the other settings of Devil kernel? Could you please share them
thx!
Yes more info would be nice. Right now I am fighting with my phone SOD about 5-8 times per day. Sucks.
as for me I keep "Captivate Keep Alive" till 70% of battery
then it turns off ..
My battery last about a working day - so it is somehow could be called "fine"...however I would prefer to NOT use wakelock progs....
I'm using Devil kernel too and Lanight ROM.
So please tell us more details: ROM version, kernel version, kernel settings ....etc...
Sorry for late response!
Sorry for the late response guys.
I thought it was the rooting to cm10 and SuperSu that did the trick, but apparently after rooting the phone, I started downloading all the Apps that I wanted to make my phone look cool. As silly as it sounds I installed World Weather app for clock and weather... oddly enough this thing keeps my phone from going to sleep. I realized this because after uninstalling it, going for a different look, I downloaded Rings Digital Weather and my phone started to turn off every 30 minutes again. Let me know if it works for you guys... cuz seriously this was the last thing I would've turned to to fix my phone
My UI freezes for 5 - 15 seconds, particularly when the phone regains network connectivity (reconnecting wifi or mobile network going from 0 to 1 bars). It's much improved after removing FB and Insta but. My launcher is even getting closed when the phone frequently, although the phone has ~500MB free RAM.
I dropped this poor phone one too many times, so before I replace it with another z3 compact, I'm wondering if everyone else on Marshmallow is seeing poor responsiveness as well.
I did have slow downs before but not like that,I have switched to Lineage and it works very well so I don't have any plans going back to stock Marshmallow.
yeah same here, i advice you to switch to lineage, you will feel like butter on the screen.
I don't have any lags at all, no launcher refreshes or whatever on stock MM. ( I don't use the horrible Facebook application)
Until 3 weeks ago, I used to have no lags at all on my stock Marshmallow 6.0.1 Z3C. I had uptime of 50 days and more and it didn't lag. Now, it happened twice in a row that my System RAM usage grew in last 5 days to 1,3 GB! It seems like a memory leak in kernel space. It's hard to pinpoint particular process. The phone is slow, multitasking doesn't work (reloads every app), my stock launcher redraws and the phone is unable to make/receive GSM calls - probably a symptom of low on memory state. I wonder, if it's caused by bluetooth driver, because I've transfered 100MB file on both occasions. I need more time to analyze this, this time I won't turn bluetooth on, so I can see if it is the cause.
Edit: I'm confident the cause is not bluetooth. Symptoms now appear after just 65 hours of uptime - . Now I tried to get rid of ES File Explorer, let's see what this bloatware did to system performace.
Edit 2: It seems the problem is gone after uninstalling ES File Explorer. Before uninstalling it had data storage set to external SD card. I replaced this piece of bloatware by open-source explorer called Amaze.
Thanks all. I was avoiding Lineage because I wanted the stock camera / DRM and their description makes it sound very unstable... "random reboots while charging", etc. I'll try it out anyway and add the stock camera back in if it runs well.
xnavra50 said:
Until 3 weeks ago...
Click to expand...
Click to collapse
Do share the source of the issue if you find it. I'm still seeing UI lockups when the phone loses internet connectivity.
jayarmstrong said:
Thanks all. I was avoiding Lineage because I wanted the stock camera / DRM and their description makes it sound very unstable... "random reboots while charging", etc. I'll try it out anyway and add the stock camera back in if it runs well.
Do share the source of the issue if you find it. I'm still seeing UI lockups when the phone loses internet connectivity.
Click to expand...
Click to collapse
camera works like stock in lineage, don't worry about that. you can face with other small bugs but still worth to use, it is better than stock in most cases.
having the same issue since a few weeks.
device gets VERY slow (i mean like 10 seconds to open the phone dialer or whats app)
Even did a factory reset, which only helped for ~2 days ...
same problem with my girlfriends Z3C.
Something is very wrong here ...
xnavra50 said:
Until 3 weeks ago, I used to have no lags at all on my stock Marshmallow 6.0.1 Z3C. I had uptime of 50 days and more and it didn't lag. Now, it happened twice in a row that my System RAM usage grew in last 5 days to 1,3 GB! It seems like a memory leak in kernel space. It's hard to pinpoint particular process. The phone is slow, multitasking doesn't work (reloads every app), my stock launcher redraws and the phone is unable to make/receive GSM calls - probably a symptom of low on memory state. I wonder, if it's caused by bluetooth driver, because I've transfered 100MB file on both occasions. I need more time to analyze this, this time I won't turn bluetooth on, so I can see if it is the cause.
Click to expand...
Click to collapse
Icefeldt said:
having the same issue since a few weeks.
device gets VERY slow (i mean like 10 seconds to open the phone dialer or whats app)
Even did a factory reset, which only helped for ~2 days ...
same problem with my girlfriends Z3C.
Something is very wrong here ...
Click to expand...
Click to collapse
there must be a reason that it is slow as hell in stock while it works with jet speed in lineage. something related to sony software, hardware is okay.
Wipe cache (Power and vol+ until 3 Vibrations) helped a little, but i don't put too much hope in it.
It's my gf's Phone so i kind of hesitate to install some unstable beta on it. Or is there any real stable release out there?
Sony haven't pushed out any updates for over a year, so not sure how you can blame it on MM build.
It'll be an app.
My money's on Facebook or Messanger.
No lags or slowdowns on my phone, had the same build on it for a year now.
Autoupdates turned OFF.
No Facebook/Messanger.
Didgesteve said:
Sony haven't pushed out any updates for over a year, so not sure how you can blame it on MM build.
It'll be an app.
My money's on Facebook or Messanger.
No lags or slowdowns on my phone, had the same build on it for a year now.
Autoupdates turned OFF.
No Facebook/Messanger.
Click to expand...
Click to collapse
Guess you're right, but i can't really accept a SD801 Phone being unable to run basic apps like FB
papa_Lutz said:
Guess you're right, but i can't really accept a SD801 Phone being unable to run basic apps like FB
Click to expand...
Click to collapse
Last year Facbook deliberatly broke their app, made it run slow and heat your phone up, as an experiment, to see what people would do. They honestly don't give a sh*t about what you think of thier app.
Uninstall it and use your browser, see if it makes a difference.
Try SD Maid from the playstore, that does some good basic houskeeping
Didgesteve said:
My money's on Facebook or Messanger.
Click to expand...
Click to collapse
Nope.
I do not have a Facebook account.
Therefore I do not have facebook or messenger installed.
But I do have these slowdowns :-/
I read in an italian forum that it's the Google app fault, you should unistall updates and disable automatic updates until it's fixed.
unpair said:
I read in an italian forum that it's the Google app fault, you should unistall updates and disable automatic updates until it's fixed.
Click to expand...
Click to collapse
Interesting.
You got a link to that thread/post?
Icefeldt said:
Interesting.
You got a link to that thread/post?
Click to expand...
Click to collapse
here and previous page
It seems the problem is gone after uninstalling ES File Explorer. Before uninstalling it had data storage set to external SD card. I replaced this piece of bloatware by open-source explorer called Amaze.
Now I have an uptime of 125 hours and counting, my System RAM usage is 0.90 GB and it isn't rising to 1.3 GB as it did before. So the phone is really smooth again. When I was checking my LogCat using DDMS, there seemed to be recurring message of ES File Explorer (estrong) leaking something, I don't remember if it was a window or an activity. What a piece of chinese malware it became. Interestingly, ES File Explorer's memory footprint was low (3 processes, 10MB total user space memory), even when leaking memory and this made debugging harder. Although I killed it, when the phone had problem (1.3 GB system memory), only a reboot worked. It totally seems like a memory leak to me.
GL debugging yours.
it works good with me ..
try to make clean install
I'm not going back to this crappy app. Once, it used to be outstanding, but they probably sold the app to another company in China and from there it went downhill. A lot of popups and ads for things I don't need. Their only purpose is to make your phone slower (bloatware) and optionally, to get money from you. I like simple, minimalistic apps, which do things they are designed for and do it right. Just this Linux approach and also "less is sometimes more".
It's confirmed that ES File Explorer makes network connections to China in background, no thanks!