Updated to kitkat not rooted now issues with phone. - Verizon Samsung Galaxy S 4

Anyone having issues with their phone? After taking the kitkat update, my phone seems laggier, battery drains quicker and sometimes my screen goes black amd i cant answer a phone call. Noticing the phone freezing now also.

skillzo1 said:
Anyone having issues with their phone? After taking the kitkat update, my phone seems laggier, battery drains quicker and sometimes my screen goes black amd i cant answer a phone call. Noticing the phone freezing now also.
Click to expand...
Click to collapse
Couple of things.
One, with upgrades like this, it's usually a good idea to do a factory reset after backing up your data. 4.3 was like this.
Two, when installing an update/new Rom, sometimes it takes a couple of days for it to "calm down" and settle in.

Thanks lawless.

-Lawless said:
Couple of things.
One, with upgrades like this, it's usually a good idea to do a factory reset after backing up your data. 4.3 was like this.
Two, when installing an update/new Rom, sometimes it takes a couple of days for it to "calm down" and settle in.
Click to expand...
Click to collapse
Thanks lawless

No problem. Hope it works out for you.

My wife's phone is 4.4 via ota and messes up once a day
sent by safestrap enabled bajarom

Go to setting more and then location and then under mode change to power save mode for battery
Sent from my SCH-I545 using XDA Premium HD app

About the screen off during phone calls; there's a setting in the Call menu you can tick to prevent the screen cutting off during calls. That might be it.

Related

[Q] Vibrant Black out.

Hey, I recently got this phone, and I must say its impressive. It runs so well and a great phone all-around. However lately when I go into department stores or even large buildings, the phone has no signal.
However when this occurs and the phone goes on standby, I noticed that you can't turn it back on without popping the battery in and out.
Is anybody else having this issue? I've been googling it and I can't find anything. Is this an android OS issue? A Hardware issue? or its just my phone doing it.
TLDR: No Signal kills phone? Is this common?
No issues here. If I lose signal it comes back on after im in range. Have you tried a factory reset since you had the phone. I did a factory reset when I got my phone and a lot of the issues were fixed.
This sounds like a weird problem. If its not related to an app or something and factory reset doesn't work, I think you should exchange it.
Sent from my SGH-T959 using XDA App
Actually I would think its a software issue not a phone defect. I have been experiencing the same issue. I'm on my 2nd one and the only way I can prevent it from blacking out like you say is to set it in flight mode. Kinda sucks when you're a cellphone salesman and you pull out your phone to try to sell one then the screen is just black and frozen.
I'd bet money it's all related to the GPS problem. With GPS enabled, and you go somewhere where it cannot get a signal (a weak as it is doing that anyway), GPS enabled apps, especially google maps but others as well, have locked my phone up.
My fix until the fix comes out is to leave GPS turned off except when I specifically want to use it.
I don't its a GPS issue the phone freezes even when the GPS is shut off. I'm willing to bet that the OP is having the same issue and his GPS is off as well.
@ op are you using setcpu app?
Sent from my GT-I9000 using XDA App
Farrenkip said:
TLDR: No Signal kills phone? Is this common?
Click to expand...
Click to collapse
Yes it is common fault throughout the Samsung Galaxy line of phones. Apparently pressing and holding the power button for ten seconds will force the phone to reboot, though I can't confirm this myself as it has never worked for me...
Some people have reported that a new SIM helps, others recommend the NoBars app. Personally I've tried both and neither have helped, leading me to think that this is a yet another hardware/software bug that can only be properly fixed by Samsung. It's perhaps also worth noting that I've had this happen to me 12+ times on two GT-I9000s running stock firmware with zero modifications.
I've entered a building where I work and have lost signal many times and ate lunch for nearly an hour. I just get the no signal image, but never blacked out.
It is true that holding the power/lock button for aprox 10 seconds will force a reboot.
Valeo said:
Yes it is common fault throughout the Samsung Galaxy line of phones. Apparently pressing and holding the power button for ten seconds will force the phone to reboot, though I can't confirm this myself as it has never worked for me...
Some people have reported that a new SIM helps, others recommend the NoBars app. Personally I've tried both and neither have helped, leading me to think that this is a yet another hardware/software bug that can only be properly fixed by Samsung. It's perhaps also worth noting that I've had this happen to me 12+ times on two GT-I9000s running stock firmware with zero modifications.
Click to expand...
Click to collapse
ive had the phone freeze a few times due to the gps **** and holding the power button has always rebooted the phone. you might have to hold it longer than 10 seconds depending on how hard the phone has locked up, but it eventually reboots.
Okay reformatting worked and fixed the signal issue. Musta went app happy and installed something that messed it up. Now that I reformatted i was a little more cafeful with what i Installed. However lately now my back and home keys has glitched and every time i push it, it either holds the menu key and goes to search or disables them for like 10 seconds
You must have install something the first time that is making your phone act up. Recommendation master reset your phone is like it come out of the box. That's what is master reset in case u don't know. If that's doesn't work get a new one. I am pretty sure they will change it cuz they did it for me.
Where do I master reset? I did Factory Data reset in the privacy settings. Is that it?
Okay doing a master reset. For those who need to know the combo. I did
Volume up + menu + power
So far this is a fix. Lets see how long it lasts.
Update: Going to take it back tomorrow. This must be a hardware failure.
That's not a master. You do it from the priv section with phone on. You will also have to call samsung if older then 15 days.
Sent from my SGH-T959 using XDA App
Maybe its the building? blocking the signal
Sent from my SGH-T959 using XDA App
I've locked the phone on 3G many of times, and when I go home I lose all 3G so the phone is in emergency mode.. sounds like you need to flash the new firmware.

[Q] Help LG-P760 frequent crash

LG-P760 stock Android 4.1.2
Only basic apps, FB, gmail etc.
1. Factory/hard reset
2. Works around 3-4 days perfectly, then starts to crash.
By crash I mean black screen, nothing helps, only battery pull.
3. After first crash, starts crashing more frequently. Happens only in standby.
Worst was today: If I start phone, log in, then it wont crash before I put it in standby. First time in standby, within 30 second, it had crashed.
twice crashed when someone tried to call me. Vibrated once, then crashed.
I would like to avoid replacing my phone.
Any ideas how to find the source of this problem? Any recommendations?
lamui said:
LG-P760 stock Android 4.1.2
Only basic apps, FB, gmail etc.
1. Factory/hard reset
2. Works around 3-4 days perfectly, then starts to crash.
By crash I mean black screen, nothing helps, only battery pull.
3. After first crash, starts crashing more frequently. Happens only in standby.
Worst was today: If I start phone, log in, then it wont crash before I put it in standby. First time in standby, within 30 second, it had crashed.
twice crashed when someone tried to call me. Vibrated once, then crashed.
I would like to avoid replacing my phone.
Any ideas how to find the source of this problem? Any recommendations?
Click to expand...
Click to collapse
I had the same problem with Vietnam Rom and it was the baseband. I changed to the baseband from ICS from a Rom of my country so I have Vietnam Rom+Original ICS baseband and everything works well.
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
lamui said:
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
Click to expand...
Click to collapse
You can.
lamui said:
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
Click to expand...
Click to collapse
I haven't unlocked it. The problem was the same: SOD sleep of death, when the screen goes off you can't do anything but pull the battery.
But if you can use the warranty use it. You should find the warranty info in the box to know where send it in your city.
Sent from my LG-P768 using xda app-developers app
Thanks. I will search into it. Sleep of death is new expression for me.
I only have phone, it came from relatives who threw away receipt + box.
Luckily I managed to get new receipt from provider yesterday (I dont think they usually give out receipts twice), so now I can use local warranty.
Thanks everyone for replying. I will post update when I have final solution.
Since you are stock you might want to consider flashing the kdz to see if that helps. Good luck!
Sent from my LG-P769(20d) using the xda-developers app. If I helped you please hit the "thank you" button.
I'm having the exact same issue with mine. I've heard everything from "try a different SD card" to "factory reset," and nothing seems to permanently fix the issue. What I've found kind of sort of works is just reboot it a whole bunch until it finally comes up and doesn't do it any more. From there, I'm good to go until the battery runs out or I need to reboot it because all the bloatware is causing it to glitch. This usually means that I have to reboot my device 10+ times in a row every few days. Hopefully, you found a more viable fix than this.
neo1piv014 said:
I'm having the exact same issue with mine. I've heard everything from "try a different SD card" to "factory reset," and nothing seems to permanently fix the issue. What I've found kind of sort of works is just reboot it a whole bunch until it finally comes up and doesn't do it any more. From there, I'm good to go until the battery runs out or I need to reboot it because all the bloatware is causing it to glitch. This usually means that I have to reboot my device 10+ times in a row every few days. Hopefully, you found a more viable fix than this.
Click to expand...
Click to collapse
Hi
I managed to kind of solve this issue. Because I am not sure how, I haven't closed thread yet.
Anyway, I warranted device, they re-installed soft. Came back, same thing. After around weeks use, SOD. Factory reset. After that, things went interesting.
I tried not to leave it idle. Always had something running. I also had noticed by the time it never occurred when it was plugged in or music was playing.
One day it did it again, but I was in a hurry and just disregarded it. I did something(I was busy, maybe just plugged it in automatically?) and it came back up. It took like 10 sec for screen to start, but it did just wake up. And it haven't had crash ever since. I have no idea is this solution or is this just some coincidence and I am not keen to factory reset again, to see will it reoccur. It's my only phone
TLDR: Managed to get out of sleep of death, haven't reoccurred since.

Random reboot while on a call?

I've had this problem sometime after Kitkat. When on a phone call, the phone will reboot randomly. Not everytime I use the phone. I've been suggested that it might be my sd card but I've ruled it out. I'm currently running nc5 stock 4.4. I've had xposed framework uninstalled to try to narrow this irritating problem. I've tried to switch roms, install them clean, install everything fresh and clean with no change. I've also had my Note 3 replaced because I thought this particular problem was hardware failure. Obviously that is not the case. I searched for an answer without success. It's very possible that I've missed something in the forums. I'll own that. I'm reaching out for help. If anyone has any suggestions I would really appreciate it. Thank you for your time.
Sent from my SM-N900P using Tapatalk
Boogeyman45 said:
I've had this problem sometime after Kitkat. When on a phone call, the phone will reboot randomly. Not everytime I use the phone. I've been suggested that it might be my sd card but I've ruled it out. I'm currently running nc5 stock 4.4. I've had xposed framework uninstalled to try to narrow this irritating problem. I've tried to switch roms, install them clean, install everything fresh and clean with no change. I've also had my Note 3 replaced because I thought this particular problem was hardware failure. Obviously that is not the case. I searched for an answer without success. It's very possible that I've missed something in the forums. I'll own that. I'm reaching out for help. If anyone has any suggestions I would really appreciate it. Thank you for your time.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I see from your post your back to a clean stock NC5, so that rules the OS out. You replaced the device, that rules out the hardware. What about the battery, are you running the battery from the first phone? Or are you running and extended battery? A short in the battery maybe? How long where on the call? Did the phone get hot and kick the high temp on device? I noticed several posts of phones shutting down from heat, it is a hot summer. The only other thing I can think of is the cell tower dropped the call, and for some reason the phone rebooted. Can you think of anything else?
I didn't consider the battery(original battery) . I haven't had any power problems yet. But that is a possibility. My calls could go on for 20 mins before it would reboot, then sometimes 10 mins. It really varies. The phone's temp would be normal I believe but I'll keep an eye on it. I did think about the reception being very low at my home and that being the cause, but it also has happened at work where I have a full signal. A battery replacement is a good idea, thank you. I will look into it. Any other suggestions will be appreciated.
Sent from my SM-N900P using Tapatalk
It could also be loose or dirty battery connections too, so check those too.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046
This patch seems to be working. Make sure to thank member thomashofmann, if it works for you.
Sent from my SM-N900P using Tapatalk

[Q] Unresponsive

Every so often, my G3 will become unresponsive. Usually happens right after the screen comes on - the interface freezes. Pressing the power button does nothing, pressing and holding the power button does nothing. I have to remove the battery in order to reset the phone.
I did search the forums, but was not able to find any similar threads or posts, was curious if I was the only one having this problem. Any ideas what might be causing this? Anyone else have any luck identifying root cause and correcting the issue?
Appreciate any help you guys can provide.
wosiek said:
Every so often, my G3 will become unresponsive. Usually happens right after the screen comes on - the interface freezes. Pressing the power button does nothing, pressing and holding the power button does nothing. I have to remove the battery in order to reset the phone.
I did search the forums, but was not able to find any similar threads or posts, was curious if I was the only one having this problem. Any ideas what might be causing this? Anyone else have any luck identifying root cause and correcting the issue?
Appreciate any help you guys can provide.
Click to expand...
Click to collapse
Are you using ART or dalvik?
ART
Sent from my LGLS990 using XDA Free mobile app
wosiek said:
ART
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
I had the same thing happening while on ART. I switched back to dalvik and it hasn't happened since.
Sent from my Sprint LG G3 using Tapatalk
Is that a known issue with ART? I reverted back to Dalvik, will see if the result is the same as yours. Appreciate the tip.
Sent from my LGLS990 using XDA Free mobile app
wosiek said:
Is that a known issue with ART? I reverted back to Dalvik, will see if the result is the same as yours. Appreciate the tip.
Click to expand...
Click to collapse
If the problem goes away on Dalvik, I would suspect you have some app installed that gets activated on startup, and isn't 100% compatible with ART. While most apps work fine with ART, not all do. Google has made it clear that the version of ART on KitKat is experimental, and the version on 'L' will be much different.
I'm on dalvik and my phone has started this. Not sure what I've changed in the last days. Running alogcat but since starting I can't reproduce it.
I ran into this problem a while back. Since I never used the LG Keyboard I tried to freeze and/or Greenify the darn thing but that caused the phone to just pause for an extended period of time when waking up. Apparently it really wants LG Keyboard to be around. So I just made sure it wasn't the default keyboard. The phone never really became permanently unresponsive; after fifteen to twenty minutes it finally woke up. But who wants that?
Reverting back to Dalvik appeared to do the trick. It's been a few days, and my device hasn't locked-up/become unresponsive since making the change. Normally I would experience one lock-up/unresponsive event once a day, or every other day.
Henri Blanche said:
I ran into this problem a while back. Since I never used the LG Keyboard I tried to freeze and/or Greenify the darn thing but that caused the phone to just pause for an extended period of time when waking up. Apparently it really wants LG Keyboard to be around. So I just made sure it wasn't the default keyboard. The phone never really became permanently unresponsive; after fifteen to twenty minutes it finally woke up. But who wants that?
Click to expand...
Click to collapse
I have had Google Keyboard set to default input since I purchased my G3; LG Keyboard left a lot to be desired in terms of performance and functionality. I never witnessed my device "wake up" like you described, but to be fair I never let it go for that long, either. Usually after 5 minutes or so my patience would wane and the battery would be pulled. And to your point, no one, and I mean no one, wants to wait 15-20 minutes for their device to return to a usable state.
wosiek said:
Reverting back to Dalvik appeared to do the trick. It's been a few days, and my device hasn't locked-up/become unresponsive since making the change. Normally I would experience one lock-up/unresponsive event once a day, or every other day.
I have had Google Keyboard set to default input since I purchased my G3; LG Keyboard left a lot to be desired in terms of performance and functionality. I never witnessed my device "wake up" like you described, but to be fair I never let it go for that long, either. Usually after 5 minutes or so my patience would wane and the battery would be pulled. And to your point, no one, and I mean no one, wants to wait 15-20 minutes for their device to return to a usable state.
Click to expand...
Click to collapse
Why are you trying to use ART,moron? ART is explicitly experimental. Use dalvik (like you're supposed to) and see if you still have lockups (which hpu won't, if you use the runtime that is already long established for running android). Duh.
scottspa74 said:
Why are you trying to use ART,moron? ART is explicitly experimental. Use dalvik (like you're supposed to) and see if you still have lockups (which hpu won't, if you use the runtime that is already long established for running android). Duh.
Click to expand...
Click to collapse
Many users have switched to ART and have seen an improvement in performance. It seems to be device specific as to whether you will encounter issues or not. That being said, I don't think it warranted the "moron" name tag. Just trying to keep the forum friendly.
Sent from my Stump'd & Bump'd Sprint LG G3 using Tapatalk
Evolution_Freak said:
Many users have switched to ART and have seen an improvement in performance. It seems to be device specific as to whether you will encounter issues or not. That being said, I don't think it warranted the "moron" name tag. Just trying to keep the forum friendly.
Sent from my Stump'd & Bump'd Sprint LG G3 using Tapatalk
Click to expand...
Click to collapse
+1
wosiek said:
Every so often, my G3 will become unresponsive. Usually happens right after the screen comes on - the interface freezes. Pressing the power button does nothing, pressing and holding the power button does nothing. I have to remove the battery in order to reset the phone.
I did search the forums, but was not able to find any similar threads or posts, was curious if I was the only one having this problem. Any ideas what might be causing this? Anyone else have any luck identifying root cause and correcting the issue?
Appreciate any help you guys can provide.
Click to expand...
Click to collapse
To watch this thread.
http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-shutsdown-t2803292
It's a knowing issue on LG G3.
There is no any exact solution for now.No matter your device was rooted or not,art or dalvik, it could happened randomly.

Extreme Lag with Galaxy S6 edge - TMobile

Hi all. I am hoping you guys an help as I am about to go back to my Nexus 6 at this point. I got a 64gb Galaxy S6 edge shipped to me at the end of March. On the first day I activated it I got the pop up that there was a software update so I did that. Every single review I've read talk to how the lag is almost gone, no overheating issues, etc. I stayed away from Samsung for so long because TouchWiz completely destroyed the Android experience for me, causing intense lag and slow down. If there is anything I can't stand when using a smartphone it is lag. Anyway, it seemed to work ok at first but I quickly noticed that it would get extremely hot for absolutely no reason at all. It will also completely lag out for no reason. For example. I'll go to unlock the phone from the lock screen and the animation will show it was swiped but it will just sit there for up to 20 seconds before doing anything. Often it just goes back to a black screen and I have to press the home button to try and unlock it again. If I try to use Google Maps many times it just hangs there for what seems like forever before it will move forward to actually start the navigation process. Navigating between music apps is painstakingly slow. I have powered off the unit multiple times, closed all open apps multiple times, etc and it doesn't seem to do anything. It will work better for a short time and then does it again. When I try to launch the camera it is supposed to launch super fast. At times I just sit there and wait. It is extremely frustrating. The longest I've had it sit there and freeze or lag has been close to a minute.
It also always seems like it is reallllllly warm, even after just a short while of using it. Again, it isn't every time I use it but more like 70% of the time. It could be resting in my pocket and get really hot, for example. It makes no sense.
Is my unit boned, or is this a common issue? I asked my developer friend and he suggested I turn off animations, etc. but why would I need to do this? I bought the phone with some crazy octa-core processor and tons of memory so it should breeze through all of this like nothing. My Nexus 6 almost never had any lag whatsoever and I would really like to think this phone is capable of more than what it is doing right now.
Any suggestions you guys have are more than welcome. I really like the phone but am at the point where if I can't get this awful lag/hanging issues fixed it is going on eBay =(.
Thanks for your time .
svenb352 said:
Hi all. I am hoping you guys an help as I am about to go back to my Nexus 6 at this point. I got a 64gb Galaxy S6 edge shipped to me at the end of March. On the first day I activated it I got the pop up that there was a software update so I did that. Every single review I've read talk to how the lag is almost gone, no overheating issues, etc. I stayed away from Samsung for so long because TouchWiz completely destroyed the Android experience for me, causing intense lag and slow down. If there is anything I can't stand when using a smartphone it is lag. Anyway, it seemed to work ok at first but I quickly noticed that it would get extremely hot for absolutely no reason at all. It will also completely lag out for no reason. For example. I'll go to unlock the phone from the lock screen and the animation will show it was swiped but it will just sit there for up to 20 seconds before doing anything. Often it just goes back to a black screen and I have to press the home button to try and unlock it again. If I try to use Google Maps many times it just hangs there for what seems like forever before it will move forward to actually start the navigation process. Navigating between music apps is painstakingly slow. I have powered off the unit multiple times, closed all open apps multiple times, etc and it doesn't seem to do anything. It will work better for a short time and then does it again. When I try to launch the camera it is supposed to launch super fast. At times I just sit there and wait. It is extremely frustrating. The longest I've had it sit there and freeze or lag has been close to a minute.
It also always seems like it is reallllllly warm, even after just a short while of using it. Again, it isn't every time I use it but more like 70% of the time. It could be resting in my pocket and get really hot, for example. It makes no sense.
Is my unit boned, or is this a common issue? I asked my developer friend and he suggested I turn off animations, etc. but why would I need to do this? I bought the phone with some crazy octa-core processor and tons of memory so it should breeze through all of this like nothing. My Nexus 6 almost never had any lag whatsoever and I would really like to think this phone is capable of more than what it is doing right now.
Any suggestions you guys have are more than welcome. I really like the phone but am at the point where if I can't get this awful lag/hanging issues fixed it is going on eBay =(.
Thanks for your time .
Click to expand...
Click to collapse
Quick answer factory reset see if that helps if not take it back to the store
I have no lag at all
I do have Lookout Mobile Security enabled, but it is only using like 7MB of ram. That wouldn't be causing this would it? I checked online at forum sites and it doesn't appear as though it would.
My first (S6 not edge) was like that. Turned into a handwarmer, got so hot it was literally burning hot! Took it back to the TMO store. Manager could not believe how hot the phone was, the box was warm and the phone inside was like a hot potato! Still frozen on the white TMobile splash screen from where it locked and stayed for hours. The phone was never really right. Got it exchanged for an Edge and it has been problem free, hardware wise.
Sounds like you have a bad one.
The Nexus 6 is a good phone, was going to sell mine but I need it to work with Google-Fi.
As suggested above, I would try factory reset first. Mine is very responsive even in power savings mode. It's just fast. I leave animation on at the default 1x. Did you look to see which apps are running the CPU up?
before a factory reset, try to go into recovery mode and clear cache. I've found on the tmobile version that once i got into recovery mode it did something of a small update automatically (in reading the scripts) and that doing that and then clearing cache really helped my battery drain i was having- might fix your lag too.
Clearing cache and factory reset after the update stopped my lag.
The battery though, just sucks. I'm down to 35% in 6 hours with less than 30 minutes of use.
I'm missing my nexus 6 at the moment. I hope I didn't mess up buying this.
Sent from my SM-G925T using Tapatalk
Guys I'm fairly certain this is just the typical 5.0.1 problem... I'm experiencing it too and factory wipes only fix temporarily.
Had same thing on my Moto X 2014 and went away with 5.1 update.
dominante58 said:
before a factory reset, try to go into recovery mode and clear cache. I've found on the tmobile version that once i got into recovery mode it did something of a small update automatically (in reading the scripts) and that doing that and then clearing cache really helped my battery drain i was having- might fix your lag too.
Click to expand...
Click to collapse
Hi there. Thanks for this tip. I went ahead and did this and it did a software update as soon as I went into recovery. I cleared out the cache as well and it seems to be much zippier now. What I have found with Samsung phones, though, is that usually they work fine for a few days and then end up going to hell. Thanks for your help and I will keep an eye on this. If it keeps ending up working poorly I will go back to the Nexus 6.
diaa08 said:
Guys I'm fairly certain this is just the typical 5.0.1 problem... I'm experiencing it too and factory wipes only fix temporarily.
Had same thing on my Moto X 2014 and went away with 5.1 update.
Click to expand...
Click to collapse
I really hope that's not the case since Samsung takes 10 times longer than any other OEM to update Android
Encountered a bit of lag again earlier. Cleared out cache again via recovery and resolved it. Definitely think I have a bum unit or something with this version of Android
Sent from my Galaxy S6 edge on T-Mobile via Tapatalk
I thought the main lollipop memory issue was tracked down to boot up animation and Touchwiz devices are not meant to have this, therefore the fix Google has made to stock devices has no bearing on Touchwiz. Basically the issues we have are Touchwiz related not Lollipop specific, though Samsung must be delighted as we all throw blame at Google it diverts blame.
One such bug is the*boot animation memory leak*bug which consumes greater amounts of memory during boot forcing the kernel to kill few process (might be core services as well) causing severe lags.*arter97*of XDA has found a work around for this issue and according to him*“the current Lollipop boot animation implementation does not releases the resources held to*playprevious frames”*which might be the root cause of the issue.
According to the developer’s research, almost all the devices (except for the Touchwiz based Samsung device) fall prey to this bug causing highly unstable UI.
Click to expand...
Click to collapse
http://www.droidviews.com/fix-android-5-0-lollipop-boot-animation-memory-leak/
Factory reset did it for me.

Categories

Resources