All of a sudden my Captivate is opening and closing my app drawer multiple times, and the phone vibrates as of I am hitting the button to do this.
I am on Cognition 2.16.
I have read that multiple vibes means that FVs are happening, but with the app drawer opening and closing like that, I'm not sure that is the case here.
Any ideas? Of something is FCing, is thee some log I can check?
I'm afraid I may need to do a completely fresh re-load.
Not sure if this is related, but when i first got a captivate the home button was hitting itself and you could see the home button dimming as if it was pressed.
All apps would close themselves, since the home button was being pressed.
Related? I am unsure, but the vibrates are suspect.
ewingr said:
All of a sudden my Captivate is opening and closing my app drawer multiple times, and the phone vibrates as of I am hitting the button to do this.
I am on Cognition 2.16.
I have read that multiple vibes means that FVs are happening, but with the app drawer opening and closing like that, I'm not sure that is the case here.
Any ideas? Of something is FCing, is thee some log I can check?
I'm afraid I may need to do a completely fresh re-load.
Click to expand...
Click to collapse
Did you find a resolution?
Whatever is going on with this thing it is killing me.I'm out of town now, but when I get back, I guess I'll have to try a complete refresh, with a master clear. Doesn't seen anyone has any input, do this must not be a very prevelent problem.
If anyone is paying attention to this little saga ....
I think I need to exchange my phone. I have flasted back to stock build (stock even before the 'fix' that they sent out)...and I just experieneced it do some of the wierd stuff.
I think I'll finish applying 2.17 Cognition, just for kicks...but expect it to still be problematic, and will likely return it tomorrow for a new one.
By the way, I'll add: it was generally acting like it was entering various random keys. Most often, like it was hitting the BACK key. But then it would possibly back through several things, such as opening the APPS, then closing, then reopening.
I could be in XDA app, reading a post, and all of a sudden it would back out.
Really strange.
My second unit did the exact same thing (my first unit had borked wifi). Oddly enough, mine didn't do it either until I flashed my first ROM onto it, but then again that only took five minutes from when I first opened the box. A flash back to stock didn't help. I had to exchange my unit, and have had no problems since. If you're even close to your thirty day window, run, don't walk, back to the store.
Sent from my SAMSUNG-SGH-I897 using XDA App
Got the new one. Flashing mhy cognition 2.16 to it right now. Fingers crossed.
Related
Anyone ever see the message "Process system not responding". Here's the story.
Well, I've been installing apps like a loose cannon, figuring I may be dooming myself to a hard reset, and it may have come to pass.
Last thing that happened while the phone was running good, was I ran the demo of the 3D game XXXXXXXXX. I received a call, and had to hop away, and after that the phone became unresponsive. Looking at what was loaded with Advanced Task Killer, I did not see the game to kill, so I turned off the phone.
Now, it is taking a very long time to 'boot'. The Phone is Locked screen would pop up, and I'd try to slide it off, and it would slide about half off. Screen black except for the clock of the lock screen. And after sliding off half way, the screen would go black, as if it was off, but then the lock screen would come back.
Kept thinking that ultimately it would finish. After a bit I got the task bar at top, and it was saying preparing internal memory'Preparing Internal Mass Storage"; then finally " Media scanner running". Finally a few icons from the dock. But everything else still black.
Then finally it would come up with a big message "Sorry!. Process system is not responding. buttons for Force close, and Wait. I don't know if that is an Android message, or an app message. I tried force close, and it went back into the same iteration of events.
So the next time i tried a boot, I did not respond to the message for a while, and it seemed to be making progress behind the message. It went off, I turned it back on, it had lock screen, moved it off a bit easier.
Then finally it came up more screen things in place. Then again with a message "Process system is nto responding". Let it set 'til it went off again. This time it came up a bit futher, and this time it came up with window to select launcher. I selected TWiz launcher. Process message again, and I killed it this time.
Whewh...Still not resolved.
I guess if there are any suggestions short of hard reset, i'm interested in hearing. maybe one of you have had this happen. If it ever finishes loading, first thing I'm going to do is remove that game.
One thing that is a pain and I think contributes, is that so many apps load by default it seems. And the more you install the more that happens, from what I have seen. I know I don't have as many apps installed as I've seen others reference, but I do have 2-3 different memory type utilities that I've wondered if they woudl interfere with each othre, but they supposedly don't all load at boot.
Post long enough. I'll add more if I find anything interesting.
ewingr said:
Anyone ever see the message "Process system not responding". Here's the story.
Well, I've been installing apps like a loose cannon, figuring I may be dooming myself to a hard reset, and it may have come to pass.
Last thing that happened while the phone was running good, was I ran the demo of the 3D game XXXXXXXXX. I received a call, and had to hop away, and after that the phone became unresponsive. Looking at what was loaded with Advanced Task Killer, I did not see the game to kill, so I turned off the phone.
Now, it is taking a very long time to 'boot'. The Phone is Locked screen would pop up, and I'd try to slide it off, and it would slide about half off. Screen black except for the clock of the lock screen. And after sliding off half way, the screen would go black, as if it was off, but then the lock screen would come back.
Kept thinking that ultimately it would finish. After a bit I got the task bar at top, and it was saying preparing internal memory'Preparing Internal Mass Storage"; then finally " Media scanner running". Finally a few icons from the dock. But everything else still black.
Then finally it would come up with a big message "Sorry!. Process system is not responding. buttons for Force close, and Wait. I don't know if that is an Android message, or an app message. I tried force close, and it went back into the same iteration of events.
So the next time i tried a boot, I did not respond to the message for a while, and it seemed to be making progress behind the message. It went off, I turned it back on, it had lock screen, moved it off a bit easier.
Then finally it came up more screen things in place. Then again with a message "Process system is nto responding". Let it set 'til it went off again. This time it came up a bit futher, and this time it came up with window to select launcher. I selected TWiz launcher. Process message again, and I killed it this time.
Whewh...Still not resolved.
I guess if there are any suggestions short of hard reset, i'm interested in hearing. maybe one of you have had this happen. If it ever finishes loading, first thing I'm going to do is remove that game.
One thing that is a pain and I think contributes, is that so many apps load by default it seems. And the more you install the more that happens, from what I have seen. I know I don't have as many apps installed as I've seen others reference, but I do have 2-3 different memory type utilities that I've wondered if they woudl interfere with each othre, but they supposedly don't all load at boot.
Post long enough. I'll add more if I find anything interesting.
Click to expand...
Click to collapse
Well, the above post exactly describes what I have on my Captivate as well. Long boot times, "process system not responding", black screens, media scanner running/completed repeatedly, severe lagging...
Does anyone have any advice on how to deal with this issue? I've uninstalled my most recent apps, but it has not made any difference. Many thanks for any guidance!
Sounds like both of you need to restore to stock...Look in the Dev section for the Stock Odin3 1 click post..it is a sticky so it should be up towards the top..Follow the instructions and you will be back to stock...
The problems I mention above occur mostly during a reboot. The phone does eventually come up, with only occasional lagging still left (which may be more typical). I am torn between dealing with the lagging until Froyo is released (hopefully later this month) or perform the "restore to stock" you mention.
If I decide to "restore to stock", does that mean I lose everything? apps, messages, config, customizations, etc.
And if I lose everything, can I restore some apps with Titanium Backup? TB was loaded 2-3 weeks ago and I do have a full backup.
When Froyo comes, will it require the same or will it upgrade the existing OS and leave apps alone?
Many thanks for your response jhernand1102
I did that too, I sett a replacement lock screen wrong (because it asked me too) and there I was with out s phone for a few hours. The one click odin didn't work for me though. So I used the updated stock rom jh2 i believe. Look for the stock rom threads in developers forum as well as the one click odin.
If the one click odin doesn't work feel free to pm me with questions on the other rom.
Make sure you read it but they is a lot there that may confuse you.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
With titanium backup you should be fine. I haven't used it but that's the point of it. A reflash may be easier the finding the error and correcting the problem. And during any flash you may have some risk of losing something but I don't think, going to froyo will lose apps by design. Anyway you have titanium backup and samsung kies to help you keep everything.
Good luck!
Sent from my SAMSUNG-SGH-I897 using Tapatalk
tone_la said:
Well, the above post exactly describes what I have on my Captivate as well. Long boot times, "process system not responding", black screens, media scanner running/completed repeatedly, severe lagging...
Does anyone have any advice on how to deal with this issue? I've uninstalled my most recent apps, but it has not made any difference. Many thanks for any guidance!
Click to expand...
Click to collapse
I guess I forgot to post back what I had to do...having had no replies at all. I think I ended up in another thread.
Anyway...I did in fact have to reflash. Using the one-click which I believe is this thread is what I used.
ewingr said:
I guess I forgot to post back what I had to do...having had no replies at all. I think I ended up in another thread.
Anyway...I did in fact have to reflash. Using the one-click which I believe is this thread[/URL] is what I used.
Click to expand...
Click to collapse
Thanks to all for replying today! I will go ahead and re-flash to stock. I was hoping it would be longer (a few months) before I'd have to re-load, but I guess when you live on the edge (root and lots of installs), ya gotta be ready for things to go wrong.
I do love this phone though and Android after being on a BB for so many years! It is pretty much a 1.0, so we should expect bugs and work arounds until they work the kinks out. In a crazy sort of way, it is still fun to work through these gotchas. Thanks again!
Yeah. I really hated the idea of a reflash.
but, if you haven't yet, you need to look in the DEV thread, and look into Clockwork Mod and Rom Recovery. As well, you should get teh paid version of Titanium backup.
Between those two things, occasional reflash and reload is not too painful.
I've learned so much today! Got the paid version of Titanium Backup for an easy "restore all via batch" and also did the ROM Mgr / Clockwork Recovery (thanx ewingr). So, I now have the best of both worlds for getting out of a jam and looking forward to trying out any new ROM's that may come out; with ease thanks to these apps!
What the hell is going on. I tried resetting and everything, even exchanged the device and the new one is doing the same thing! Also vibrating and force closing it is getting on my nerves! The followig seems to happen after a while I am TIRED of having to turn of my phone and turn it back on! ~ I go to play a .mp3 it says " FIle type not supported"...My .mp3 ringtone does not work the phone just vibrates the selected ringtone doesnt work. I got too take a picture or record video it says "Camera Failed"....I get a visual voicemail....the "play" button is grayed out and I have to turn off phone turn it BACK On just to check my voicemail. Also occassioally my sms wont work either. I turn my phone off and on every morning and throughout day I notice this and its getting REAL annoying !
Well first off, this isn't a software flaw, this is specific to you, as we have many users here including myself who are using these phones daily without the issues you are describing.
You had said that the issue was with an mp3, can you upload that somewhere for us to test on our phones?
As far as the camera and visual voicemail, I've never heard of that issue before, perhaps you ended up with a bad phone again?
I am getting the frequent force close with messaging. I also have had problems with the camera and idk about the mp3 stuff I haven't put any ringtones on the phone yet. This is getting really annoying I agree.
I don't have any issues with mine? Have you guys done anything like rooting or flashing anything?
Nope, completely stock. The most I have done is take a screen shot lol.
hmm maybe some have a defect? It's not all SK4g's though, as some of us have no issues at all. I would suggest getting it replaced by T-Mobile, as this is a factory defect. not sure why that happened to you guys. has anyone else had these issues and found any fixes?
That's kinda tough the hearest t-mobile is like 4 hours from here /:
One of my friends who went with me on the trip to get the SK also got one and he says he's never gotten a force close so you may be right. But could it have anything to do with the amount of texts I send/receive? Because I have to admit it is pretty excessive. The failing to send messages when I am receiving one simultaneously is expected, but not the force closes in my opinion.
It shouldn't force close on you. I know mine fails to send every once in a while too, as I text a lot (kinda the reason I got the phone). failing to send isn't as big of a deal, as it notifies you and you just have to click resend. Not entirely sure why it's force closing though? I wonder if a logcat might help? if you have adb installed, you can try adb logcat and see what shows up when you force close? if we can find the issue there, it might be fixable from our end. all depends on where the flaw lies/if it's just a bad apk somehow or if there's an actual hardware issue or something.
I'll do a log next time there is a fc, I'm having another issue or it may be related, but this one is with WidgetLocker I believe. Sometimes when I go to unlock the phone it'll freeze up and then I dont know how to explain it, but it almost seems like it resets but it really doesnt. The phone will blackout for a little then the homescreen will pop up and service will gone for a while until the cards are read just like if I rebooted.
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
sduvick said:
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
Click to expand...
Click to collapse
Yeah I know it does that from time to time, but on my previous phone it wouldn't do that reboot thing where it would lose connection then resend my latest text messages once it reconnected.
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
sduvick said:
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
Click to expand...
Click to collapse
That's what I was thinking too, I'm gonna uninstall it for a bit and see if anything changes.
is anyone else having an issue with notification volume? everytime i reboot my SK, my notification volume gets pushed all the way down to nothing, so i don't get a sound notification for texts, emails, etc, until i move the notif. volume back up in my settings. i did root with the one-click for the Epic 4G.
This is a new UI so alot of the apps i.e. widgets you may put on will cause issues. If you like certain apps contact the dev so your device is supported correctly. Still to new to get mad at it till sum of the bugs get worked out. I did notice a couple of times when I left screen on in pocket on accident that when I go to use it again it doesn't respond to any touch but can move courser around till rebooted then its ok. If some don't already know the sk4g is almost the same as the epic. The sk4g is still a badass phone for 100bucks.
Same as the OP
I know this is a little old, but I've experienced the same problem as the OP so it seems they are not alone with this problem.
I actually tried two different newly formatted SD cards (because I thought it may have been the SD card), and still would have the problem. Then I actually did swap phones about a month ago and it seemed the problem would now take several days to resurface instead of several hours. And I could deal with that.
Since the OTA update about 2 weeks ago, the phone has been back on it's original BS as the OP posted and it's driving me nuts. I actually missed some emergency calls last night because the mp3 ringtone didn't work so I'm finding a solution to this issue today or trashing this phone.
My belief is that there is something interfering with the phone's ability to read the SD card for media. Because other apps I have that save to the SD card or read from it work fine. So I'm going to master reset it and not download any of my apps and see what happens when I set an mp3 ringtone. If it makes it through the day with no hiccups, I'll slowly add back one app at a time until hopefully I can find the culprit.
bipoler if you'd like, we can exchange via PM what apps we both have downloaded and see if we have some in common that may be problems.
I'll post back with any progress.
I've been having the problem with ringtones not working, just getting silence when I get a call. for me it seems to happen when I set a ringtone from the app Zedge, I don't think it happens when I use ringtones from the Android System, which would make sense if the issue is related to reading the sdcard. gonna go back to a system ringtone and see what happens today.
Yeah my phone had all those problems, but I installed the Lightning rom and all those problems went away, except for the ones about messages failing...I text A LOT
Lightning ROM
Thanks for that info on the Lightning Rom. I will check that out. Phone has been working flawlessly all day with the mp3 ringtone and no extra apps besides the master reset. I might give it until the morning before I start putting them back on.
On stock id install so many apps that ran on the background that id get delay from opening closing swiping and turning onthe phone.. so I wiped it installed a custom rom and just kept the essentials.. havnt had a problem since... well.. occasionly ill have to odi but that's on purpose
Sent from my SK4G
I may have caused this...this a.m., I picked up my gTab when it was almost finished booting. I accidentally hit the power button, which turned the screen off. I had to fiddle with it a minute to get the screen on...it kept going right back out after I pushed the power button. I finally got it on (no reboot from here).
From there, it was nuts. I was greeted with having to pick my launcher again. Then I got a slew of force closes. Almost nothing would start, and the few things I did get to run (Mail'd, Dolphin) ran like they were new installs. Rebooting did the same.
Finally, I ran fix permissions from CWM, and it would start without FCs. However, anything I had tried to start before was still like new installs (EULA, setup wizards, etc). I managed to restore some of those via Titanium.
Still, it's not back to normal. Some recent apps (like, Fieldrunners from yesterday) no longer appear to be installed. Really fubar.
Could this be caused by the power button thing? Or is it a sign of impending doom? Is there a better way to fix this other than what I've done?
Oh, and I forgot to mention...I started Amazon appstore to downloading today's app, and then was restoring old apps via Titanium. In the middle of that, it played a sound I've never heard...like a few seconds, ending with this weird sliding reverb. But...I wasn't sure if that was Amazon's download finishing in the background? Usually I wait on the download. But it was longer than a typical notification sound.
TarheelGrad1998 said:
I may have caused this...this a.m., I picked up my gTab when it was almost finished booting. I accidentally hit the power button, which turned the screen off. I had to fiddle with it a minute to get the screen on...it kept going right back out after I pushed the power button. I finally got it on (no reboot from here).
From there, it was nuts. I was greeted with having to pick my launcher again. Then I got a slew of force closes. Almost nothing would start, and the few things I did get to run (Mail'd, Dolphin) ran like they were new installs. Rebooting did the same.
Finally, I ran fix permissions from CWM, and it would start without FCs. However, anything I had tried to start before was still like new installs (EULA, setup wizards, etc). I managed to restore some of those via Titanium.
Still, it's not back to normal. Some recent apps (like, Fieldrunners from yesterday) no longer appear to be installed. Really fubar.
Could this be caused by the power button thing? Or is it a sign of impending doom? Is there a better way to fix this other than what I've done?
Click to expand...
Click to collapse
Wow, I am experiencing the same situation as you. I didn't hit any power button either. I am on VeganTab 5.1 and now contemplating a flashing to a new GB ROM.
Sorry, man, it really sucks. Obviously, I didn't get much feed back as to what or why. Fortunately, I had a not too old backup with Titanium, and was able to get most things back with just a few clicks. Other things I had to set back manually. Took me a couple of hours to get back to what I thought was "right".
I did figure out the odd noise was a ringtone, and it had set my email notification to that ringtone sound. It wasn't even on my tab before, as far as I know. So I have no idea where that came from.
I'm thinking of Flashing to Cyanogenmod myself. But without knowing the why...it still won't make me feel too much better.
TarheelGrad1998 said:
Sorry, man, it really sucks. Obviously, I didn't get much feed back as to what or why. Fortunately, I had a not too old backup with Titanium, and was able to get most things back with just a few clicks. Other things I had to set back manually. Took me a couple of hours to get back to what I thought was "right".
I did figure out the odd noise was a ringtone, and it had set my email notification to that ringtone sound. It wasn't even on my tab before, as far as I know. So I have no idea where that came from.
I'm thinking of Flashing to Cyanogenmod myself. But without knowing the why...it still won't make me feel too much better.
Click to expand...
Click to collapse
Thanks TarheelGrad. I did a permissions fix and that has worked for me too. Not sure why it went bonkers.
It's apparently a semi common problem.
My Wildfire running CM7 will always open up the clock app when I press the home button. Freezing the clock stops this happening.
Similarly, when I answer or make a call, the speakerphone is automatically activated. From what I can tell, the phone thinks it's docked, and indeed, if I set the phone to make a sound when it's docked, you do hear the notification.
If I plug in the power cable and wiggle it around, I can get it to activate/ deactivate this, but I dont have this problem at all if I go back to the Sense backup I have. (Should note, I've cleaned out the power socket with all manner of stuff, to no avail (thought it might be lint etc))
Basically, is there any way I can stop the phone from thinking it's docked/ just remove the dock facility entirely?
I found a thread somewhere that said something about changing the name of a dock related apk somewhere, but I can't for the life of me find it again.
Thanks!
I would start with a fresh install if you haven't tried that already.
Hit that thank button if I helped!
Yup, should've mentioned I've done that numerous times with different versions of stable CM7. Did a full wipe and cleared the dalvik cache each time too.
The problem doesnt happen until the phone has fully loaded i.e. the home button works normally for the first 10 seconds or so of the phone being on. Then I hear the notification to say the phone has been docked, and the problems begin.
Have you thought of uninstalling the docking software, and then rebooting?
Hit that thank button if I helped!
Well that's what I'm asking - how exactly do I do that?
I would download this,
http://www.apkapplications.com/2011/07/root-uninstaller-pro-apk-v121-download.html
Then look for the docking .apk
Hit that thank button if I helped!
Well I used that to freeze the clock before and that worked to stop the home button going to the clock, but the speakerphone issue remained.
There was no docking apk as far as I could tell.
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
flamph said:
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
Click to expand...
Click to collapse
Glad you got it fixed!
Sent from my DROID3 using XDA App
same problem here, tried everything, reflashing, data wipe, cache wipe.
and same as OP sense based roms do not show this symptoms.
I have this problem with CM7 and almost on every rom based on it.
I searched in many places, but there aren't any positive solutions.
please help.
P.S.- cleaning the USB port also didn't work for me..
I found a way to disable dock mode. there is an app called NoDock which disables the dock mode at OS level.
It requires root permission to disable the dock. so your phone must be rooted.
unlike apps like DockNothing this actually does the job.
no more auto speakerphone modes, no more home button taking to clock app.
m.appszoom.com/android_applications/tools/nodock-free-trialneed-root_ogod.html
Hello everyone!
Let me start off by saying that i'm actually using an unrooted, officially update nexus 5, updated to the latest 5.0.1
I have no problem whatsoever, battery really seem to have improved, but lately i've been getting a strange behavior
After a period of use (it goes from a couple of days to a whole week) the phone oddly slows down when i press the middle button, to return back to the homescreen.
For example, if I'm using the facebook app, and watch a couple of videos along with opening a few external links, when i press the home button, the whole home "loads" from start. I mean, i literally see nothing for a second, then it slowly loads widgets and icons. After it's been loaded, everything works flawlessly again, but if i open facebook again, use it for a while and press the home screen, it loads again.
Mind that i have no custom drawer (i tried Themer, it gives me the same error, it says "loading homescreen" when the problem appears) but the problem is still there with the stock homescreen. I tried force-closing the apps i used, thinking about a memory issue, but to no avail. I have to turn off and turn on the device, and everything works wonders again.
Is there any app that could help me with this issue? I'd like to understand why it's doing this and which app is slowing down my phone.
g0ldb3rg said:
Hello everyone!
Let me start off by saying that i'm actually using an unrooted, officially update nexus 5, updated to the latest 5.0.1
I have no problem whatsoever, battery really seem to have improved, but lately i've been getting a strange behavior
After a period of use (it goes from a couple of days to a whole week) the phone oddly slows down when i press the middle button, to return back to the homescreen.
For example, if I'm using the facebook app, and watch a couple of videos along with opening a few external links, when i press the home button, the whole home "loads" from start. I mean, i literally see nothing for a second, then it slowly loads widgets and icons. After it's been loaded, everything works flawlessly again, but if i open facebook again, use it for a while and press the home screen, it loads again.
Mind that i have no custom drawer (i tried Themer, it gives me the same error, it says "loading homescreen" when the problem appears) but the problem is still there with the stock homescreen. I tried force-closing the apps i used, thinking about a memory issue, but to no avail. I have to turn off and turn on the device, and everything works wonders again.
Is there any app that could help me with this issue? I'd like to understand why it's doing this and which app is slowing down my phone.
Click to expand...
Click to collapse
I am not Sure whether this is 100% sure, But have heard that there is a memory leak issue in lollipop. Which might be the reason of ur problem. And the oly way get enough memory is to restart. But again, I am not Sure whether the above information is correct though.
keertikumar_ws said:
I am not Sure whether this is 100% sure, But have heard that there is a memory leak issue in lollipop. Which might be the reason of ur problem. And the oly way get enough memory is to restart. But again, I am not Sure whether the above information is correct though.
Click to expand...
Click to collapse
I've heard that too, but it's strange that it has appeared only now. I haven't had this kind of issue ever since i updated it.
The FB app is just real buggy. My personal theory is whatever that app does exposes the Lollipop memory leak.
MrObvious said:
The FB app is just real buggy. My personal theory is whatever that app does exposes the Lollipop memory leak.
Click to expand...
Click to collapse
Yep i know about that, the FB app is just horrible script-wise. Nevertheless, i've never had THIS problem. And even if i forceclose it, it doesn't solve the problem anyway.