Related
I just updated my vibrant from 2.1-update-1 to froyo 2.2 last night, its feel slow sometimes, but today while I was at college campus library I notice my vibrant turn on when I Hear the music. When I took it out of my front pocket I notice it rebooted. I didn't turn it off and it was in my front pocket with the touch screen laying on my wallet. Can it be a problem with froyo?
No it's not a problem with froyo. This mostly always happen. I can tell you this happen to most people here on xda with other phones as well. Maybe choose another rom.
Visit www.tomorrowisnews.com For Android news and more.
our experience...
one of our vibrant phones is still unrooted and stock 2.2. it has, on at least 2 occasions, done this since it was upgraded to 2.2 through kies. when it's done this, the phone just rebooted on it's own and started working normal again. if you are still stock and this keeps happening, you can always get a warranty exchange if you can't find a solution. this is what i am watching for before i root it, lol. you never know, it could be a hardware problem. this unrooted vibrant is our newest one out of the four we presently own. none of the others have done before...ever.
some of the software is hanging and causing a reboot. Try a custom rom and see if it goes away..... It most likely will
Oh, I see thanks for the info, and I can't really exchange it becaues I unlock it for ATT, but on the plus side froyo did fix my sim data refresh problem that kept popping up every 15 to 20 minutes. My suggestion to people is not to update to froyo cause of the auto restart apps feature. Even advance task killer can't stop it, Thanks to that feature it turn on every stock programs in the phone and use up most of my memory. I only get between 60 to 80 mb of free space left. And it drains the battery too. I charge it at night and it would finish charge before 12am and the next morningat 8 am I found the battery life less then 80%.
Hi;
I apologies in advance for the long thread, but I want other users to notice the symptoms I faced maybe someone else will benefit from it.important parts are marked in blue
MY galaxy s3 is only 4 months old....I got tempted by rooting and getting all -other- features such as fast recharging, sound hack, trying new roms before they are officially released...etc
anyhow, my phone's troubles showed strange symptoms quite shortly after the second rom being installed....
at first I was not fully aware of the required rooting steps, until I use the galaxy toolbox that rooted my phone easily for me...
then I started noticing the phone would start and everything but noticed (root user notices) take time to show up after boot, it would take approx. 1min then they will show very fast...after that everything is normal so i figured the processor is a little bit loaded...
few weeks later I started using CWM's backup &restore feature , noticed that when I go back to the official Rom, it lags, a lot! , I have to restart the phone at some points because it will stop responding...I started checking processor load and was surprised to see normal non harmful rates...so I forced apps to be closed once I exit them.
few roms and flashings later, the phone started restarting it self randomly,like an old car heating up, it would restart few times then get back to normal state....this would happen whenever i try to change anything in the rom (CM10+nightlies build)
few days ago, whenever the phone received or made a notification sound, I would pick it up and find it turned off! I turned on again and use it normally , no issues....after this happening for 2 times, the phone just died ...PIT partition is non-readable/writable anymore :crying:
I noticed the night this thing happened that, when I restored the rom, it took a longer time, and something was not found but the rom booted normally....
now my phone is in service and they are overloaded with service-warranty requests, so they haven't checked it yet (it has been there for 3-4 days)..I used traingle away on the current rom, no flash counter appears and the binary is official, but the rom appears as custom
notes:
*from the beginning, every step I made was a trial and error to me, I tried rooting once (manually) and I didn't figure it out,until i saw the toolbox that made it easy,,,the first root was amazing, but I rooted again after rom crashed and seems I used a different root that started all that trouble.
*All the mentioned above I believe were symptoms, that I didn't care about since the phone was acting normally after those occurring..I think I should've spotted them earlier.
*There have been 2 overheating incidents, one happened when I forgot the phone in my pants and by mistake i ticked "load new videos from subscriptions in youtube and the phone sucked up around 3gbs that day...it was really really hot when I got back to it.....the other one was when I went to sleep few days ago, I put it under my pillow, woke up with the phone overheated and restarting continuously "might've been doing this all overnight!"
*I insisted -although it was clearly troublesome to my phone- on installing Siyah kernal on every rom "always the latest one", sometimes the phone would keep restarting and I would have to restore a previous rom, sometimes it would go without issues, this happened more oftentimes during the last few weeks and CM10 nightlies offers dialy updates and I had to flash siyah back after every update...now I'm writing it and feeling stupid!
*Official JB roms caused the phone to hang a lot, so I kept using CM10+siyah kernel till the last moment.
now, what I would like to know is:
1- why does that chip get affected?? I never flashed a 3/4 part rom, just using CWM....
2- I decided (if) the phone gets fixed on warranty, to not to root again, I'm having a million guesses as the reason why this happened, including the fast recharging, the continuous flashings and testing (although all are stable roms, only official and CM10 roms), the overheating incidents....etc....I would like to know what you guys think.
If you had read the faqs and guides first you would not have the trouble .
Like
at first I was not fully aware of the required rooting steps
from the beginning, every step I made was a trial and error to me
I tried rooting once (manually) and I didn't figure it out,
>> basic CF Root is simple as it gets .
jje
UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
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.