Related
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
haojan said:
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
Click to expand...
Click to collapse
Provide us with more information. Is your phone rooted, on a custom ROM maybe, what have you been doing to your phone, when did this start happening, etc.
History
I started with stock, rooted, non-market apps, unhelpful kernel v1.2, removed AT&T bloatware. LCD density @ 180. Tried One Click Lag Fix v1.0 and v2.2 and uninstalled. Juice Defender to manage 3G. Juice Plotter to track battery.
After messing around with it, I encountered a reset of the default launcher selection each time I long pressed the home button to bring up the recently used programs. I then did a hard reset and that fixed that problem. After the hard reset, my Captivate ran great! I found it responsive and fast enough without the need to try and apply any lagfix.
I then reinstalled my selected applications. My phone started to randomly reboot about once a day. I noticed Juice Plotter's data would be lost and it had to rebuild. It also happened to reboot on me once while I was using it. Other than that, it has not really affected my usability.
If it hasn't affected your usability, do you want to fix it?
If you do want to fix it, then the best way is to restore to Stock and add things slowly until you determine the problem. If you return to Stock and it still reboots, then you have a hardware issue.
It doesn't "quite" affect usability but it is not working "normally" either.
Was hoping to see if anyone else have experienced random reboots and how to troubleshoot it. If not, I will try out Odin one-click flash to stock...
Hi.
I'm on the stock gingerbread. Have root, v6 supercharger script etc. Working on stock ROM and lg Launcher.
I'm wondering what these lines :
" hs.systemserver=64m
hs.com.lge.launcher2=64m "
In /system/build.prop means, and what effect it can do. I reduced heapsize from 64mb to 36mb to avoid freezes during a heavy multitasking. I use multitasking option in supercharger script. I use some background apps, and there is annoying freezing, and phone is not responding like if a ram policy was bad. It happens under the heavy usage, while using heavy apps (more than one) Phone sometimes reboots during this long freezes, and sometimes after long time wakes up with a screen that some app is not responding (then I kill it and phone is fine)
Can I delete these lines in build.prop ? And do it help in anything?
What else I can do?
Do anybody have an idea why stock GB ROM lags from time to time, and these lags are quite long if happen.
The reason I don't want to change to a custom ROM is that I want to have some things that are stock (dialer, lock screen, notification bar etc.) I would change if they work on miui, or cm7 became stable..
My stock gb rom is fast and not laggy so it's probably an app in background hogging up cpu or ram. Try using a task manager to stop apps you don't need from auto starting and then reboot.
If you are rooted you can also stop lg bloatware from running too.
Dave
Sent from my LG-P920 using Tapatalk
Yep, i'm working on it, stopping a bloatware, using different Launcher, and uninstalling unnecessary and possible lagging apps.
But, i'm afraid that either there are some malfunctions in the stock software, or I have this occasional lags and memory issues because I didn't do a wipe after the update from 2.2 to 2.3...
No person with such issues that sometimes an app is not responding and Android hangs, lags, not responing, and reboots ?
I must check deeper my problem... Maybe too many apps installed and running in the background...? I will check.. Cause it annoys me quite a bit.
I didn't do a wipe but when I did a factory reset things improved a lot except battery issue which is sorted now so maybe try that option?
Dave
Sent from my LG-P920 using Tapatalk
As far as I know to Wipe means a factory reset, so I think its the same thing.
You tell that the battery issue is being sorted out by LG itself,.or you mean that there is a solution here on xda forum? Any help will be appreciated. My battery life is fine but reading the battery usage is really messed up on every GB ROM I think. That is what they should work on..
So I have the i9020T (from Wind in Canada). I enjoyed running CM9 nightlies on it, but then Jellybean came along and I went nutso over it (like so many others). I flashed back to stock ICS, and then ran the OTA update on it to JB.
My experience has been disappointing. It was unfathomably slow. It was running-Windows-7-on-a-Pentium-III slow. The new UI and features are glorious, but I need a lot of patience if I expected to use them. I'm talking about delays of around 5 seconds to start an app, switch apps, or even open the app drawer, 2-3 seconds lag when bringing up the keyboard, and 5-10 seconds to bring up Google Now.
I automatically decided to nuke everything and start from a clean slate. I grabbed the 4.1.1 stock image from Google, then formatted /system and threw it on. After the initial setup, and before I even got to rooting the thing (never mind restoring from Titanium), it was still muscle-atrophyingly slow.
I ended up just restoring all of my apps and data, and using it as-is, figuring this is what I should expect from an older device. Yet everyone online raves about how much faster JB is than ICS on the Nexus S. Either you're all trolling me really hard, or I'm doing something very wrong.
Here's some more gory details:
Like I said, I wiped /system before loading the new image. I did it on the phone using Clockworkmod recovery, then used fastboot from my computer to load the image. I did not wipe data or cache, because I figured the whole image-writing thing would be obliterating all my stuff anyway, but perhaps I was wrong?
I've been playing with the CPU usage overlay, available in the Developer Options. First off, I have no clue what the different colours mean or what scale those bars represent, but I can tell you my load is typically 2.0 (even just sitting there idle with the screen on), all the way up to 15 or so if I'm trying to do something like use Chrome while listening to Google Play Music. system_server is always the top process, and its bar is always 3-4 times bigger than the next, with the sole exception of loading up Google Play Music, in which case the mediaserver process holds the top spot with a fairly long bar. ksmd, com.android.systemui, surfaceflinger, and com.android.phone are always running, but only ksmd even has a bar long enough to be visible. Other processes pop in and out, and of course they start going willy-nilly when I actually start using apps and switching between them.
There have been a handful of times where an app will die while I'm in the middle of using it, and 2-3 times the phone has outright rebooted itself.
So there's my story. Can someone tell me if I'm just plain doing it wrong? Perhaps there's a guide on how to completely sterilize the phone before loading the stock image? Or perhaps my hardware is broken? :-/
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Cool... I'm looking into it, and can't find any directions whatsoever on what I should download or how to install it. I'll keep digging, though. Thanks!
While I am not sure what is causing your issue I can confirm that stock jb should not be performing like you are describing. Except for loading up Google now. That does take some time but even that once its loaded runs OK.
Did you clear your SD card? If not back that up to a computer and wipe it. That's all that I can think of and it may actually fix it.
At first I noticed painfully slow speeds as well. Changing my min setting to 200 helped so much! I've heard the the Interactive governor is amazing with JB in terms of speed. You could try that out.
Nexus S. (GSM i9020a)
Paranoid (1.97 - 4.1.1)
Matrix (CFS - 22.5)
Ondemmand (1000/200)
Deep Idle (On - Deadline)
I've just flashed Air Kernel (I just picked one of four options, I don't know what the heck "blue color" means), then set the governor to smartassv2, and so far it feels snappier. I'll have to keep using it to see if it's the solution I need. Thanks to all who've made suggestions so far!
Sent from my Nexus S using xda app-developers app
If your phone is going crazy slow it could be a number of things like apps could be slowing down the phone in the background or the phone might be trying to sync. You could backup all of your apps and then wipe your phone fully it should speed it up quite a bit and then you can restore each app 1 by 1 to determine if its a rogue app causing it. But if you can't be arsed to do that and wipe then just try and flash Thalamus kernel and see what its like if you set the governor to interactive on that it should go crazy fast.
Sent from my Crespo using xda premium
Please provide clear advice Nexus S so slow on Jelly Bean
ronnygunz said:
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Click to expand...
Click to collapse
I can see there are many 'fixes' for slow running devices on Jelly Bean. However, I have no idea:
1. how install Air Kernel or where to get it from
2. How to change the CPU governor from "on-Demand" to "SMARTASSV2" or where to download this from
Please can someone give me the complete idiots guide to getting my Nexus S running properly again??
THANK YOU
There are a million guides on this forum for all of this. If you don't know how to flash a kernel or adjust CPU speeds, you need to familiarize yourself with these things and understand the risks. First off, try cleaning your phone up. Take all your important stuff off your external storage, and do a factory reset. My Nexus S never ever ran slow, even on stock.
Have you tried a more simple but fast kernel like marmite 4.2 from bedalus? Give it a try.
So I've been having tons of fun with my Sensation ever since I got it, and I installed AOKP 4.2.2 + Sultan Kernel r24.5, with all recommended settings aside from cpu speed which is at Sensation XE speed and undervolting is at recommended levels.
However, I've been getting this issue of everytime I'm installing apps, the phone hangs and just gets stuck until I take out the battery and turn it on again. This ONLY happens when installling apps, and hasn't happened with ANYTHING else. Any ideas? Kinda in a rut.
So basically, only when I'm in the Chrome app (not the beta, just stock chrome), when I hit the home button and come to my home screen, it's blank for a second or two, and then my apps / folders pop up. This shouldn't happen and hasn't happened to me until recently. It's almost as if i'm using too much RAM, but i know for sure I'm not as I've tested it with chrome being the only app even running. I don't think chrome is leaking 2 gb of ram...
Some info- this is on my nexus 5, rooted but stock rom with xposed. No xposed modules related to chrome, chrome is not greenified or anything, so i'm not sure where the problem is. I've reset all the default on ://chrome/flags so i'm not allowing it to use too much RAM. Can anyone think of why this is happening? I can provide more info if needed, just ask.
braddaugherty8 said:
So basically, only when I'm in the Chrome app (not the beta, just stock chrome), when I hit the home button and come to my home screen, it's blank for a second or two, and then my apps / folders pop up. This shouldn't happen and hasn't happened to me until recently. It's almost as if i'm using too much RAM, but i know for sure I'm not as I've tested it with chrome being the only app even running. I don't think chrome is leaking 2 gb of ram...
Some info- this is on my nexus 5, rooted but stock rom with xposed. No xposed modules related to chrome, chrome is not greenified or anything, so i'm not sure where the problem is. I've reset all the default on ://chrome/flags so i'm not allowing it to use too much RAM. Can anyone think of why this is happening? I can provide more info if needed, just ask.
Click to expand...
Click to collapse
first things first. xposed comes with a countless amount of undocumented issues. before doing anything else to try and fix your issue, get rid of xposed, completely. if that doesnt fix your issue, we will try other things. if you dont try removing xposed. then theres no point to try anything else.
simms22 said:
first things first. xposed comes with a countless amount of undocumented issues. before doing anything else to try and fix your issue, get rid of xposed, completely. if that doesnt fix your issue, we will try other things. if you dont try removing xposed. then theres no point to try anything else.
Click to expand...
Click to collapse
Simms is right. What I would recommend personally is having MultiROM installed and having one ROM on ART without exposed and another ROM with every XPosed module known to man and several species of Monkey. ?
Over time your device may seem fine but XPosed starts slowly corrupting the integrity of the ROM have no idea how. You'll get random force closes, weird audio bugs, force reboots, screen of deaths, and random lag spikes from my experience. You'll run every cleaner in the book, you'll clear cache and dalvik cache and fix permissions but it won't help. You've been struck by a smooth criminal, ahem. XPosed.