Related
So total noob question. What exactly is the lag thats being fixed? Is there a specific lag or is it more of a general slowness of the phone?
Thanks!!
Some apps open slow. Some people notice lag in booting the phone. Mainly overall feel i guess. Like you said.
docflower said:
So total noob question. What exactly is the lag thats being fixed? Is there a specific lag or is it more of a general slowness of the phone?
Thanks!!
Click to expand...
Click to collapse
The lag that is being referred to is a lag caused by samsung's property rfs file system that samsung put on this phone. As far as I can tell there is a flaw in data write where the rfs file system can pause for as much as second - and when you get multiple process waiting in line to write data it causes a very noticeable lag in the phone as it will come to almost a standstill.
If you don't nice anything don;t worry about it....LOL
I see more issues caused by lag fixing than those who don't bother with them...especially when loading new ROMS A slight hesitation now and then doesn't bother me.....Perfection is not the goal.
I've found I don't need a lagfix for Cog's 2.2 beta 5.6.
I get a hiccup every once in a while but otherwise everything seems to run fine. And it's still a billion times faster than my old iPhone so I'm happy either way. (I had to wait to do EVERYTHING on that POS)
http://capfaq.com/w/Lagfix
dayv said:
The lag that is being referred to is a lag caused by samsung's property rfs file system that samsung put on this phone. As far as I can tell there is a flaw in data write where the rfs file system can pause for as much as second - and when you get multiple process waiting in line to write data it causes a very noticeable lag in the phone as it will come to almost a standstill.
Click to expand...
Click to collapse
Exactly how do this happen ? Can this be replicated on this phone so everyone can see it ? I have seen and experienced wake up lag on Androids that have non stock roms..and also the damnable phone dialer lag as well with my Hero..but have yet had this problem with my Captivate....So.. what does one have to do to see it on the Captivate? Your saying the file system that is causing this correct...I don't believe it is the same thing other Android phones are experiencing and what has been called LAG to honest with you..if it were then everyone that had this phone would be complaining about it. Sometimes I had to swipe 4 or 5 times to unlock my Hero..or having tried to dial a number only to have 5 or 6 extra numbers punched in because of the LAG..
I think what you seeing and what is being described here as LAG isn't really the LAG of most Android based phones are having..What I think is being described is just a slight hesitation of certain applications being opened and closed..This is normal for any computer depending on what and how large the program is.The file system used with these may indeed cause this but it is nothing as compared to a phone that really Lags. Boot lag is something entirely different..and as far as I can tell can be caused by what is loaded on the phone and not really the phone itself, unless the phone isn't really wiping any residual data before applying a new rom and thus causing conflicts on booting.
If this wasn't the case..then every Galaxy phone would do this..complete stock or one that has been customized. I may be totally wrong..but I don't think I am..
Mac
The problem isn't on other Android phones because other Android phones don't use RFS. RFS is a Samsung thing.
And just about every person does complain about the lag... how severe it is depends on how heavy of a user you are so a few uber-light users might not notice it so much.
Me? I notice things like occasionally 10-30 seconds after returning to my home screen for my icons to appear, hesitation in keyboard entry causing massive typos and repeated keypresses, unresponsiveness of home keys only to have it suddenly register all queued presses, etc.
I acknowledge the problem but unfortunately a lot of the "lag fix" hacks cause more harm than good.
Mac11700 said:
Exactly how do this happen ? Can this be replicated on this phone so everyone can see it ? I have seen and experienced wake up lag on Androids that have non stock roms..and also the damnable phone dialer lag as well with my Hero..but have yet had this problem with my Captivate....So.. what does one have to do to see it on the Captivate? Your saying the file system that is causing this correct...I don't believe it is the same thing other Android phones are experiencing and what has been called LAG to honest with you..if it were then everyone that had this phone would be complaining about it. Sometimes I had to swipe 4 or 5 times to unlock my Hero..or having tried to dial a number only to have 5 or 6 extra numbers punched in because of the LAG..
I think what you seeing and what is being described here as LAG isn't really the LAG of most Android based phones are having..What I think is being described is just a slight hesitation of certain applications being opened and closed..This is normal for any computer depending on what and how large the program is.The file system used with these may indeed cause this but it is nothing as compared to a phone that really Lags. Boot lag is something entirely different..and as far as I can tell can be caused by what is loaded on the phone and not really the phone itself, unless the phone isn't really wiping any residual data before applying a new rom and thus causing conflicts on booting.
If this wasn't the case..then every Galaxy phone would do this..complete stock or one that has been customized. I may be totally wrong..but I don't think I am..
Mac
Click to expand...
Click to collapse
I did not say that I ever saw this lag myself - I was just answering the question as to what was being fixed in the lag fixes - and the rfs file system hang that happens at the sync on close at the end of a write is what these guys are attempting to address with these lag fixes.
I am not even using a lagfix as the current custom rom I am running is running just fine without one.
Here this thread gives more in depth description and explanation of the rfs lag
http://forum.xda-developers.com/showthread.php?t=799931
i feel the lag is caused by touchwiz and exaggerated by the file system. i never noticed a complete lack of lag with a lagfix. things got slightly less choppy but i think there is a big placebo effect around here. in eclair my phone was still laggy with any and all lagfix's that i tried including voodoo.
the leaked froyo doesn't lag too much but doesn't update the wallpaper on wakeup if you are running live walpapers so you get a black background ocasionally. applying the z4mod lagfix to froyo makes a difference in bootup and wakeup but is not totally necessary. actually there is a big potential for problems and forgetting to remove a lagfix before flashing will turn into a headache really fast.
The video in the below thread gives a clear enough demonstration of the effect. A lag in opening emails, or marking email unread, that is at least around 2 seconds every time and 5 seconds at one point. After a lagfix is installed, it consistently takes well under one second to perform the same operations.
As I understand it, lagfixes either re-partition the file system entirely with a new file system, or create a large cache so that data can be accessed quickly without as much interaction with the filesystem.
http://forum.xda-developers.com/showthread.php?p=8638406#post8638406
TheYar said:
The video in the below thread gives a clear enough demonstration of the effect. A lag in opening emails, or marking email unread, that is at least around 2 seconds every time and 5 seconds at one point. After a lagfix is installed, it consistently takes well under one second to perform the same operations.
As I understand it, lagfixes either re-partition the file system entirely with a new file system, or create a large cache so that data can be accessed quickly without as much interaction with the filesystem.
http://forum.xda-developers.com/showthread.php?p=8638406#post8638406
Click to expand...
Click to collapse
While the video does indeed show lag in opening everything with that custom rom..where is the video showing the same issue with that phone prior to any modifications using the stock rom..? I'm not talking about one that has been rooted and re flashed..I am talking about one straight out of the box... If it took that long just to boot up with cog..then there really is something wrong. From a dead stop with the battery out to being fully up and running..takes less than 45 seconds with mine running staright from the box stock. Either I don't understand everything( big possibility) or something is either wrong with that phone with that rom installed on it.
I'm not trying to say this isn't Lag on the video..it clearly shows it..but I do question why a fair comparison isn't being shown..As much as I hate to say it..it looks like the biggest amount of issues I have seen here is from folks who have rooted and flashed new roms. BTW..my email opens as fast as the fixed one does as well. I am sure someone does have these issues (perhaps not to this degree) on a unaltered phone..but I also think it is exactly what I said earlier too..that some of it is normal..but some want everything instantaneously...and I don't believe that will happen for sometime.
I do understand what folks do here and why..I'm not totally dumb when it comes to rooting and flashing...but to me and the way I am seeing it..something somewhere isn't being taken into account here with how this rom is acting. I know a lot went into developing it..but..in all honesty to my eyes it looks like it isn't fully optimized yet,even with what has been done with it so-far.Of course I have absolutely no way of knowing what that phone did when it was totally stock either...but with out a true side bt side comparison video of the same phone..nor will anyone else. Also..I don't blame folks who want something different..Hell..if folks didn't try to make changes..nothing new would ever get developed,but sometimes trying to fix something that works fine,is cutting off your nose to spite your face too..
To me..instead of trying to replace the file system with something different..why not try to make a rom using it..? The phones are spec'd to use it..so use it..optimize it..and see if most all of these "issues" go away..Maybe easier said than done..I don't know..but that's how I look at it.
Mac
The stock email is not the one shown in the video, it is touchdown which many use to sync their corporate email accounts as the stock program is inadequate or not compatible.
If you have not noticed the lag then you don't need a lagfix. Data intensive operations do exploit the flaws in the rfs system however and many experience better performance after installing one.
As for startup time, lagfix really has nothing to do with this. Regardless of setup, the phone will boot only slightly faster with one.
Sent telepathically using vulcan mind meld app.
For what its worth. I remember showing my coworker my lagfixed 2.1 and we compared to his stock, and did a side by side on browser, email and a couple of other apps. It was a big enough impression that he immediately installed oclf.
Sent from my SAMSUNG-SGH-I897 using XDA App
govgeek said:
For what its worth. I remember showing my coworker my lagfixed 2.1 and we compared to his stock, and did a side by side on browser, email and a couple of other apps. It was a big enough impression that he immediately installed oclf.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well..that make me wonder if all of these issues are a QC issue from Samsung..I do know I had to go through 7 different phones(all new not refurbs) for the wife last week we we signed up wit AT&T...
I guess I'll wait till the official non beta release of 2.2 is out before I start changing mine.This will give me a better understanding on how everything is right now..as opposed to flashing a different rom,and see if the phone starts acting up.
Thanks
Mac
Mac11700 said:
As much as I hate to say it..it looks like the biggest amount of issues I have seen here is from folks who have rooted and flashed new roms.
Click to expand...
Click to collapse
While I am rooted now (reluctantly, due to some things that I need to run that require it), my lag predates that as I only rooted recently. Lag of 10 seconds at a time is not uncommon... whether it's a freeze while using the keyboard, trying to pull down the notification bar, trying to switch apps, trying to use the "Home" key, or waiting for the home screen icons to re-appear. I've counted delays as long as 30 seconds at times.
If lagfixes weren't so dirty and unsafe, I'd be their biggest proponent.
I bought my Captivate on 12/13. For the first 3 weeks I had it I had almost no problems with it (other than the usual GPS issues). About 3 weeks ago I rooted (1-click Root), installed the 1-click decripple, SGS Tools, Titanium Backup and OCLF and removed some of the bloatware, but stayed with the stock ROM. Got some noticeable improvement as far as Quadrant benchmarks, but about a week after I did all that the phone started freaking out. I had my first of 2 unexplained shutdowns. Simple things, like receiving calls, would lock the phone up. Then I started having force closes when I tried to use a speed dial. The past week the battery has been doing strange things like losing 60% charge over 4-5 hours without using the phone for anything. It will somehow go back to normal and work fine for 4-5 days. Today, the force closes and lockups started anew. Again, an incoming call locked the device. I didn't even know it for 3 hours when I turned it on and the clock was over 3 hours behind and the screen wouldn't take any input beyond unlocking. Reboot and later I tried to speed dial and back into force close loop. Reboot...still does it. Tried to bring up my contacts and get a black screen, eventually leading to getting kicked back to the Home screen. Obviously, the contacts issue is related to the speed dial issue, which is probably related to the incoming call issue since they all are tied together. But what could be the problem? I am so frustrated I'm ready to hurl this thing at a wall. I uninstalled OCLF and am considering an Odin flash to stock. Seems like the phone is really flaky when it has a full of >90% charge. Any clues?
I would start with olcf. The lag fix it used its not recommended and may be causing data corruption
I have said it plenty of times before, and I will continue to preach....I recommend flashing back to stock and master clear to troubleshoot. That will give you assurance that you will start on a fresh clean slate, as far as bugs/data corruption/bad configurations. Obviously you will want to back up all of your data first. After you flash back and master clear, don't do anything else to it other than installing regular apps from the market to see how it runs. If it continues to act up, then you know you have hardware issues. If it fixes it, then you know you had something going on with your config or data corruption.
Whats your build number? If it is one of the 1007 builds then you may be able to get a warranty exchange for the reboots.
Getting noticeable improvement as far as Quadrant benchmarks go doesn't always = better
Here's the really odd thing, pulling the battery and rebooting seems to clear the issue for a few days. A plain reboot won't. I alternate between 2 batteries, both OEM. I've never cleared the battery stats. Could it be an issue with one or both batteries? It always seems to happen shortly after taking the phone off the charger.
If you haven't already, you can try recalibrating your battery. But the route I would take is flashing back to stock using odin one click. It doesn't take very long and it will rule out alot of things
Sent from my SAMSUNG-SGH-I897 using XDA App
phone
before you throw it aganist the wall let me know i will pick it up and give you another phone to throw
cavsoldier19d said:
I have said it plenty of times before, and I will continue to preach....I recommend flashing back to stock and master clear to troubleshoot. That will give you assurance that you will start on a fresh clean slate, as far as bugs/data corruption/bad configurations. Obviously you will want to back up all of your data first. After you flash back and master clear, don't do anything else to it other than installing regular apps from the market to see how it runs. If it continues to act up, then you know you have hardware issues. If it fixes it, then you know you had something going on with your config or data corruption.
Click to expand...
Click to collapse
Yup...I agree...and I would start with a 100% clean slate..and not use any data from any previous time..Flash a good kernel..a good modem..apply the gps fix of your choice..and enjoy..Trying to use parts of a stock rom..is self defeating...wither or not you get uber high benchmarks or not...You may want to stay with some type of stock build..but you IMHO your better off going with a I9000 rom/kernel/modem...Anything that is even close to stock AT&T is junk as far as I know.
Mac
cavsoldier19d said:
If you haven't already, you can try recalibrating your battery. But the route I would take is flashing back to stock using odin one click. It doesn't take very long and it will rule out alot of things
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
As soon as I have a few hours to spend redoing all my data, apps and info, I think that's what I'll do. I already downloaded the 1-click Odin OEM ROM. After flashing Odin do I have to redo the JH7 OTA update?
Miami_Son said:
As soon as I have a few hours to spend redoing all my data, apps and info, I think that's what I'll do. I already downloaded the 1-click Odin OEM ROM. After flashing Odin do I have to redo the JH7 OTA update?
Click to expand...
Click to collapse
you dont need a few hours. just titanium backup....and about 20 minutes for the whole thing.
Pirateghost said:
you dont need a few hours. just titanium backup....and about 20 minutes for the whole thing.
Click to expand...
Click to collapse
What if there's something wrong with an app I installed that is causing the problem? Wouldn't reinstalling my apps with TB just bring that problem back?
Miami_Son said:
As soon as I have a few hours to spend redoing all my data, apps and info, I think that's what I'll do. I already downloaded the 1-click Odin OEM ROM. After flashing Odin do I have to redo the JH7 OTA update?
Click to expand...
Click to collapse
It really doesn't even take a few hours to back up and restore. I have an 8gb external sd card full of music, photos and videos and over 200 apps stored internally and it takes me 10-15 mins if that using titanium backup pro for apps . You don't have to restore jh7 but it might be a good idea to do so if that's what your phone had out of the box.
Sent from my SAMSUNG-SGH-I897 using XDA App
Miami_Son said:
What if there's something wrong with an app I installed that is causing the problem? Wouldn't reinstalling my apps with TB just bring that problem back?
Click to expand...
Click to collapse
Typically restoring normal apps you get from the market will not cause you grief. But what can cause you grief is backing up and restoring mods, system data, configuration data etc. The goal is to create a totally unhacked unmodded totally stock experience to isolate and possibly identify what could be causing problems
Sent from my SAMSUNG-SGH-I897 using XDA App
cavsoldier19d said:
Typically restoring normal apps you get from the market will not cause you grief. But what can cause you grief is backing up and restoring mods, system data, configuration data etc.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
and OCLF.... dont forget that OCLF causes PAIN!
I need my phone tomorrow for work, so I'll settle for just uninstalling OCLF for now. Maybe Friday or Saturday I can sit down and "go back." I don't remember if the phone had JH7 or if I updated it OTA when I first got it, but that's what it has been running almost since day 1. Is there an Odin for JH7?
No there isn't but heres a thread on how to install it...
http://forum.xda-developers.com/showthread.php?t=790080&page=20
You will need to download jh7_ota.zip.
Basically, after you flash back to stock, you have to install clockworkmod recovery, place the zip file on your internal memory, boot into clockworkmod recovery and choose to install the zip file. I actually did this the other day to see if it actually works, because my phone came with jh7 out of the box.
PS...if you kept the box your phone came with, it will show near the barcodes if your phone came with JH7 or JF6
Box says JF6, so I must have upgraded it. Don't remember doing it, though. What's wrong with just using the Odin for JF6 and letting the phone do the OTA for JH7?
One click lag fix sucks.
Sent from my Captivate.
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
nemo.mareed said:
My Motorola Triumph keeps randomly rebooting and the battery goes from 90% to 7% suddenly sometimes. I had the phone for a week so far and the frequence of restarts is increasing. I don't have any task killer app.
Is it some software that I am using or it's a hardware issue? Do you think I should have the phone replaced by Virgin Mobile?
Click to expand...
Click to collapse
Is it rooted?
Sent from my VS910 4G using xda premium
Yes it is rooted. Is that a problem?
nemo.mareed said:
Yes it is rooted. Is that a problem?
Click to expand...
Click to collapse
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Haro912 said:
Try charging it all the way and using cwm to wipe the battery stats. That should fix the battery drain. The reboots I would try wiping Dalvik, cache, and last first data if the first 2 wipes don't help at all.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
I just figured out the problem has to do with wifi. When I turn it off and use 3G instead the mobile becomes stable (so far). Is anyone facing the same problem or it's just me? Is there a fix?
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Haro912 said:
Does it have a custom ROM on it? I've seen around the forums that there has been issues with the MT and wifi on the ROMs
Click to expand...
Click to collapse
No. But the frequency of the reboots increased after I re-installed the original MT stock ROM.
When I first bough the device it restarted once or twice a day. Now it reboots non stop unless I take out the battery. I re-installed the stock ROM from another source but the problem persisted. The problem goes away when I turn off wifi abut comes back when I turn it on.
Sounds like something to do with the kernel, not the ROM... maybe. I had horrible luck with any and all custom kernels for a long while. Although that's just my luck, might not be yours...
Looks like you had a problem from the beginning... Try everything stock, and if it's still there, return it... Wow my first post in years...
I know someone who had the same problem..
switched to the iPhone 4s...
Same here...
Me too...
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Problem solved!
kdevine said:
I have this problem as well. I am going to try the CM7 mod to see if that goes away. I have also isolated it to WiFi.
Click to expand...
Click to collapse
Wohooooooooooooo The problem DOES go away with CM7 beta 8 !!!! It's like magic!
Phone no longer reboots randomly
Wifi is stable and does not disconnect or cause the phone to reboot or the battery to heat up
And battery life improved 300%!!! I now charge it every other day with moderate 3g/wifi usage!
I had CM7 for three weeks so far and my frustration turned into happiness! It's just amazing how changing the software makes a HUGE difference!! Before CM7 I always felt like smashing my MT because of the hard time it gave me!
I followed the instructions on: http://www.motorolatriumphhacks.com/
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
alcapone1130 said:
i am having the same problem.I am running cm9 with latest update,out of know where my phone started rebooting on its own or while i was doing something or playing a game and it is doing it more and more.What should i do.
Click to expand...
Click to collapse
as far as ive seen with both cm7 and cm9, random reboots houldnt be an issue anymore, but for other still having the issue it usually comes from about 4 things over the rest
1. faulty hardware, which normally isnt the case, if faulty hardware was the issue you'd probly be seeing more then random reboots, but its still possible
2. Rom didn't take correctly during flash, either by chance, or because the phone wasent properly cleared and now settings are "head butting"
3. Running a custom rom in which you can adjust the cpu and the settings are either to low or to high, both can cause reboots
4. Most common one ive seen by far outta them all, Apps, certain apps especially after some updates will "play tricks" on the device and for some reason cause reboots sometimes, usually the next update of said app will resolve the issue but not always, so if you find an app thats the culprit you can notify that apps developer
you can always try and go back to 100% stock and see if the issue is still there but if your like me you probly hate the stock froyo by now lol
It may seem painful or whatnot but unless you find exactly what may be causing the reboots the best bet overall would be
Do a complete Fresh install of whatever rom you use, dont flash anything besides the rom and gapps if needed, also dont restore any backups yet, just to be sure
Once the fresh new rom is booted i turn the phone off then back on for safe measures lol
Now if you can lol try running the phone with No aftermarket apps besides any/if any that came on the rom, if the problem is gone you know for sure here that it was one of your apps
then 1 by 1 install your apps and give it some time in between app installs to see if the problem comes back and hopefully this way if it does youll know which app is causing troubles
FAQ
To quote directly from my FAQ,
"Reboots on Android are a pain, and can be attributed to multiple sources. I’ve been able to successfully reduce the amount of reboots that I get, but never eliminate them… Anyhow, here’s some troubleshooting information:
1. Format SD card in Windows (back up your SD card data first!) Make sure you format to FAT32. Don’t try formatting it in Linux. I have done this before and the phone wouldn’t boot up!
2. Slightly overclocking prevents some freezes.
Under Settings > Cyanogenmod Settings > Performance overclock the max speed to around 1300-1400ish. This should speed the phone up, but not to the point of the thing overheating
3. Fix SD Card permissions. Do this by booting into Recovery (You can do that if you have this ROM installed) and go to advanced > Fix SD card permissions. Now reboot.
4. Do not use Firefox, except the Nightly builds. Firefox has went through drastic speed and performance improvements recently, but the older builds, despite being called stable, are so slow, they will make the phone freeze and reboot. Yes, this includes Aurora. UPDATE: All Firefox versions except stable (ironic, eh?) have been used by me personally and have not made my phone reboot. Make sure you’re on at least version 14. (This one doesn't apply as much anymore, I need to update my FAQ!)
5. Give the phone a break from time to time. After intensive gaming for hours on end, the phone will often reboot while exiting a game.
That’s all the tips I have. I managed to drastically reduce my reboots by doing these, but not eliminate them completely. I hope g60madman or mantera find some hidden timeout value in the kernel (if one exists, like the auto reboot on BSOD in Windows) and either lengthens the timeout value or disables automatic rebooting so if this is a kernel panic, we may see the debugging details and upload them to fix some crashes.
6. Make sure that you have the VM heap size set to be adequate enough. I recommend at least 24 MB, preferably anywhere from 32 MB and up if you want the phone to last a while without rebooting.
7. Sometimes a cache wipe and dalvik cache wipe are needed to stop bootloops. Unfortunately, every once in a while, you may start getting bootloops. This usually due to some sort of corruption in the cache or dalvik cache. You can safely clear them through Clockworkmod Recovery without loosing any data, and this usually fixes the problem. If not, do a factory reset through Clockworkmod Recovery and reinstall this ROM."
Since I updated my Nexus S (i9020a to be exact) to ICS 4.0.4, my phone has been randomly rebooting like everyday! I did manually update it but I got stock Android and also I am unrooted not have my bootloader unlocked. Why is this happening so frequently? Should I factory reset my phone?
kyokeun1234 said:
Since I updated my Nexus S (i9020a to be exact) to ICS 4.0.4, my phone has been randomly rebooting like everyday! I did manually update it but I got stock Android and also I am unrooted not have my bootloader unlocked. Why is this happening so frequently? Should I factory reset my phone?
Click to expand...
Click to collapse
Try that yes
Sent from my Nexus S using xda premium
I just did. No reboot yet... hoping that this worth my data...
Sent from my Nexus S using XDA
I also had a spontaneous reboot a couple of days after I updated to 4.0.4.
It's only been four days total, so I'll be keeping an eye on it.
Sent from my Nexus S using xda premium
nope... didn't get it there...
maybe you should wipe your cache and dalvik-cache... and don't forget to fix permissions...
savantist said:
nope... didn't get it there...
maybe you should wipe your cache and dalvik-cache... and don't forget to fix permissions...
Click to expand...
Click to collapse
The thing is I'm not rooted and it seems that factory resetting actually did a job cuz no reboot so far... I'll update forum if this method works...
Sent from my Nexus S using XDA
Personally I've had several occurences of random reboots and actually at the phone lock into a reboot loop till I pulled the battery.
I think the issue is RAM management. The Nexus S doesn't have as much RAM as most tablets and it's younger sister the Galaxy Nexus. Something in how the OS decides which of the background services should be terminated and cached under heavy RAM load seems to be part of the problem.
For example, I seem to have improved my phone stability by removing apps that update in the background and don't need to (UAL, I'm looking at you ) and disabling background updates in other applications (TripIt, PodKicker Pro, etc) to prevent them from leaving background services running. That seems to have helped in my case.
[email protected] said:
Personally I've had several occurences of random reboots and actually at the phone lock into a reboot loop till I pulled the battery.
I think the issue is RAM management. The Nexus S doesn't have as much RAM as most tablets and it's younger sister the Galaxy Nexus. Something in how the OS decides which of the background services should be terminated and cached under heavy RAM load seems to be part of the problem.
For example, I seem to have improved my phone stability by removing apps that update in the background and don't need to (UAL, I'm looking at you ) and disabling background updates in other applications (TripIt, PodKicker Pro, etc) to prevent them from leaving background services running. That seems to have helped in my case.
Click to expand...
Click to collapse
You actually might be right! Ics probably is optimized for phone with duel core and at least 1gb of ram...
Sent from my Nexus S using XDA
kyokeun1234 said:
Since I updated my Nexus S (i9020a to be exact) to ICS 4.0.4, my phone has been randomly rebooting like everyday! I did manually update it but I got stock Android and also I am unrooted not have my bootloader unlocked. Why is this happening so frequently? Should I factory reset my phone?
Click to expand...
Click to collapse
wipe data may solve this issue.
I have been running Pete's Bugless Beast which has both the ROM and Kernel updated to 4.0.4. Never had a random reboot.
I doubt it is a memory issue. When my phone doesn't have a foreground app open it usually has 130 MB ~ 150 MB free. I never see it go below 100 MB.
AeroEchelon said:
I have been running Pete's Bugless Beast which has both the ROM and Kernel updated to 4.0.4. Never had a random reboot.
I doubt it is a memory issue. When my phone doesn't have a foreground app open it usually has 130 MB ~ 150 MB free. I never see it go below 100 MB.
Click to expand...
Click to collapse
My phone is not rooted, so is there any way to fix it without flashing anything?
Sent from my Nexus S using XDA
Exactly when is it powercycling?
Is it when running a certain app? When plugged in? When on standby? When you set it down or bump it?
There a number of different reasons the phone could be powercycling.
If it's while running a certain app or completely at random while you're not using it, unprevoked, first try hard resetting it. That will resolve the majority of issues.
If it's when you set it down or it's bumped, it's an issue with the battery making contact. Remove your battery, clean the contacts gently with a pencil eraser, make sure the contacts are clean and free from pocket lint on the phone itself and reinsert the battery.
If it's still doing it after a reset, it could be your processor. The best way I've found to test your processor is to max it out. You can do this by running a benchmark app over and over while everything on your phone is running. I personally use "Neocore" (available in the Play Store). Turn on your bluetooth, wifi, max your screen brightness, gps, every battery sucking processor running setting available. Run Neocore as 'Interactive Mode'. If you run that for an hour without powercycling, your processor is good. If it powercycles, you have a bad processor and should have your phone replaced through Samsung warranty.
Best of luck to you!
Random reboot
My phone is rebooting at least 15 times a day !
It is very random : during a phone call/installing an app/unlock the phone/writing with keyboard/phone is idle...
Applications are also often not responding...
I did a factory reset/wipe data several times but it didnt change anything.
Phone :Nexus S i9023
Carrier : unlocked ( HK )
OS/build number : Android 4.04/IMM76D
A really big amount of people posted the same issue on google mobile forum. ( i can't post link yet as it is my first post ) title "Random reboot of nexus with Android 4" ( please google it ) , but nobody mentionned anything with CPU. Could it be really that many people having a default CPU ?
After my last post, no reboots for while but now reboots are back with increasing frequency.
Sent from my Nexus S using xda premium
I don't usually like resurrect a really old thread, but after a road trip where my Nexus S randomly rebooted 4-5 times while running Podkicker Pro and Maps Navigation I went and reset my device to factory defaults. The next day I had the phone reboot in the middle of a podcast. Today it rebooted halfway through the first ring when I received a call.
Seems to be, at least in my case, that the reboots are related to mp3 audio.
This lead me to find this bug logged against the galaxy nexus: http://code.google.com/p/android/issues/detail?id=22669
It doesn't provide an answer, but it does provide some insight. I think personally I might look at different ringtone formats and see if converting my custom ringtone to something other than MP3 will help, but I'm not optimistic.
Anyone else having problem where background apps are closing too quick?
My podcast app gets killed all too quickly and my launcher as well.
Any non-root way of getting around it?
Sam
Same here. Haven't found a solution yet but my Spotify keeps getting killed
Same here. I hope memory management will be improved with 5.1.1
i have no memory issues at all.
what's the problem?
it's been a while,
i decided to restart my phone and wipe cache
now the phone's a speed demon again
i think this is the manifestation of the infamous memory leak...
so yeah if you're seeing the same thing
just restart
that should be a lot better after that
shubu000 said:
it's been a while,
i decided to restart my phone and wipe cache
now the phone's a speed demon again
i think this is the manifestation of the infamous memory leak...
so yeah if you're seeing the same thing
just restart
that should be a lot better after that
Click to expand...
Click to collapse
What memory leak?
shubu000 said:
it's been a while,
i decided to restart my phone and wipe cache
now the phone's a speed demon again
i think this is the manifestation of the infamous memory leak...
so yeah if you're seeing the same thing
just restart
that should be a lot better after that
Click to expand...
Click to collapse
you're right... it is not Lollipop memory leak (the famous one) but another kind of leak which saturate RAM after 100 hours circa of uptime...
A reboot every 100 Hours is ok... but I hope they will solve it asap
carburano said:
you're right... it is not Lollipop memory leak (the famous one) but another kind of leak which saturate RAM after 100 hours circa of uptime...
A reboot every 100 Hours is ok... but I hope they will solve it asap
Click to expand...
Click to collapse
There is no "lollipop memory leak" on the Z3. I think you must be talking about an application with a memory leak as I've had my phone for 8+ months now and have never had to reboot it. You should perhaps perform the usual steps to determine which app has the problem and then take the problem up with the developer, or use another app.
Webern said:
There is no "lollipop memory leak" on the Z3. I think you must be talking about an application with a memory leak as I've had my phone for 8+ months now and have never had to reboot it. You should perhaps perform the usual steps to determine which app has the problem and then take the problem up with the developer, or use another app.
Click to expand...
Click to collapse
Dear friend... We already know that Lollipop Memory Leak is not present in Z3... but this doesn't mean that memory management is ok...
please check this... https://github.com/sonyxperiadev/kernel/commit/f971262f63f380d9386dbe4c55eed0809eba0b18
Is a recent commit to solve a memory leak in the kernel...
As you can see memory management can be improved.
Ah... another thing: if I check app I will notice that only system apps cause this kind of memory saturation.
PS: Maybe you need to reboot your phone.. at least to install OTA
carburano said:
Dear friend... We already know that Lollipop Memory Leak is not present in Z3... but this doesn't mean that memory management is ok...
please check this... https://github.com/sonyxperiadev/kernel/commit/f971262f63f380d9386dbe4c55eed0809eba0b18
Is a recent commit to solve a memory leak in the kernel...
As you can see memory management can be improved.
Ah... another thing: if I check app I will notice that only system apps cause this kind of memory saturation.
PS: Maybe you need to reboot your phone.. at least to install OTA
Click to expand...
Click to collapse
I'm sure a few bytes goes astray every now and then. Unless it's something which happens repeatedly, and takes up a sizeable amount of memory you'll never notice it. And memory taken within a process will be freed when that process is killed (ie even if not freed explicitly from within that process).
Yes, I may have rebooted my phone to diagnose an issue or install an upgrade, but every 4 days? No - the phone is faulty or you've been installing rubbish if that's the case.
Webern said:
I'm sure a few bytes goes astray every now and then. Unless it's something which happens repeatedly, and takes up a sizeable amount of memory you'll never notice it. And memory taken within a process will be freed when that process is killed (ie even if not freed explicitly from within that process).
Yes, I may have rebooted my phone to diagnose an issue or install an upgrade, but every 4 days? No - the phone is faulty or you've been installing rubbish if that's the case.
Click to expand...
Click to collapse
No friend... this is theory but bugs are there and I think they're solved... because Z3+ is ok. Check this video:
https://www.youtube.com/watch?t=161&v=x7bT_ALUB8E
That's it
shubu000 said:
Anyone else having problem where background apps are closing too quick?
My podcast app gets killed all too quickly and my launcher as well.
Any non-root way of getting around it?
Sam
Click to expand...
Click to collapse
Absolutely.
I downgraded to KK because it was very frustrating.
Also I swear LP on my D6633 only uses 2 out of the 3gb of RAM. I never see less than 1GB free ram when I was on it.