When switching to bookmarks in browser it can be normal but many times I have a good lag. I wonder if others have ran into this also. I have used both task managers and wipe/reflash and these have just proved to be a temporary fix. everything else on the nexus flys.
Yeah mine does it sometimes.
It happens, usually why my cache is full and I accidentally got like 6 tabs or more open. ..lol
oh yeah, I get that lag as well. it doesn't happen all the time. but when it does happen it can take more than 5 seconds or much longer to open up bookmarks. must be a bug.
got the same lag here, running CM 5.06
I've had it since day 1, across every vanilla rom I've used. Hopefully it gets fixed in the next update. It only happens in thumbnail mode, not list mode.
Just got my Galaxy S yesterday, but had big problems with the Samsung apps right out of the box.
The main launcher would repeatedly lock up, it was totally unusable. After being frozen for a few minutes I would be able to kill twlauncher process, then it would start up again and run for a few seconds before freezing. I managed to download LauncherPro from the market place to replace it, which is much better.
However, the calendar is causing me grief now. It takes a long time to load, and is not particularly responsive, but the big issue is the battery usage.
1 hour 40 since unplugging and I'm down to 50% battery left (from a full overnight charge) - calendar is responsible for 17% of this(!) with 47 minutes of CPU usage. What is going on?!
Any advice on how to either fix this, or blitz the Samsung calendar app and use the standard google one?
Hi Meza1,
First thing to be aware of is that it takes about 5-7 days before the battery starts to settle down, the first 2 days are a little scary.
Your launcher locking up doesnt sound normal, so I'd keep an eye on that.
As for calendar, I've not noticed it being an issue. The usual battery hogs are when apps are set to high frequency updates. So recently I installed twitter on a 15min update and it took my battery from 2-3days standby down to 6hours!
You could reset your phone to factory and start again and if its still locking up you might want to get it exchanged. We all suffer lag of a few seconds here and there which we hope will be fixed, but not to the level you've just reported.
Root your phone and install "AutoKiller". Great app, it automatically cleans out your ram and uneeded background applications. Phone runs smoothly with no lag. I use "LauncherPro" instead of "TouchWiz".
My GPS also fixes almost instantly, less than 30 secs in most cases. This is in both Google Maps and Co-Pilot.
I really think that it would be unwise to root the phone at this stage, because it would appear to have problems that are not seen on most SGS's and therefore the chances are that the phone needs to be returned.
This would not be possible if "rooted".
Thanks for the responses. I think I'll try one of the lag-fix ROMs that are being mentioned and see how it goes. Is there a way to back up my apps and settings before doing this?
I would agree with Geryatrix and hold off rooting or upgrading your phone just yet, in case you need to return it.
The surfaceflinger seems to have indeed been fixed, but there is still a memory leak in the system, which I now encountered it for the 2nd time. I wanted to make screenshots, but just after I made the 2nd one, the tablet soft rebooted. It didn't freeze, it didn't show any google logo, it went directly to the boot animation and then the tablet booted. This seems to have been fixed it, unlike the previous surface flinger issue where you needed a normal reboot.
Anyway, in the 1st screenshot you can see 44h of uptime, in the 2nd one I took a pic in quick system info which displayed 198mb of free ram, just after I cleared all the processes, but then the tablet immediately soft rebooted and apparently didn't save the screenshot.
Running "ps su" in terminal emulator showed 56 rss, if I typed "su" 1st and then "ps su" there were 2 rows, one with 56 rss and the second with 116 rss, so the surface flinger has apparently been fixed.
Running factory image 4.3, rooted, deodexed, stock kernel. Has anyone experienced this issue on 4.3 so far?
LE: Oh I forgot to attach the first screenshot, sorry. Anyway it's a pic from cpu spy, which displayed 44h of uptime, so it's not that important.
I had just nearly the same phenomen. But my n10 softrebooted when I was starting to examine the process table. I just had found surfaceflinger, so I'm sure it was not that process, but sadly I hadn't found the mem-eater, when the colored X appeared.
I had done a dirty flash from aokp-pub, so I am not sure to blame android-4.3. But mem-leaks stick like sh** on a shoesole, so I'm sure, if it does not result from dirty flashing, we will hear soon from a new memory leak... (hopefully in some opensource part - cm and aokp team are faster in n10 support then google...)
I haven't had a single reboot since I flashed 4.3. My uptime is up into the 90+ hours range, and it would be higher if i hadn't had to reboot to install root, Adaway and the AOSP browser. I mainly use the tablet to browse the internet (using the AOSP browser) and reddit (via reddit news app), plus some youtube videos (using the youtube app) occasionally. I rarely play games, though I have played a little Real Racing 3 since the last bootup.
My advice is to download the stock rom from the google developers website, and completely wipe the tablet clean via the "flash-all" script. Re-install only the bare minimum apps, and see if the issues persist.
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Amiga4ever123 said:
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Click to expand...
Click to collapse
Same here on Nova
Sent from my Nexus 10 using Tapatalk HD
Ladies and gentlemen, I present you the "suspect": Google's Chrome, the all time crap browser.
I also mostly use the AOSP browser and occasionally Opera for some downloads that I can't do with the stock browser. I installed Chrome a few days ago to see how it works in 4.3 and it does indeed work better, but the 1st memory leak I encountered happened the day I used chrome, I'm sure of it. I wasn't much impressed with it so I went back to AOSP browser and everything worked fine, then I decided to give it another try: bam, memory leak again, yesterday, the day I used chrome again.
Also, I read some comments on the forums about people having reboots on 4.3, WHILE using chrome.
In fact, in 4.2.2 while we had the surface flinger problems, I remember that chrome was the main cause.
I am back to using AOSP and Opera and everything is working superbly.
Amiga4ever123 said:
I have 4.3 from Friday. No restarts at all, but I noticed two times strange behaviour. Tablet was soo slow, every action was soo laggy. I had to restart it. Maybe its apex fault. Im not sure
Click to expand...
Click to collapse
malikalhaji said:
Same here on Nova
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Are you rooted? If so, there is a bug in SuperSU V1.41 which causes CPU usage to sit at 100%...
Ref:
http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
Yep rooted. My Chrome is disabled. I hope update supersu will solve the problem with cpu usage. Thx for info about it
stiggy2012 said:
Are you rooted? If so, there is a bug in SuperSU V1.41 which causes CPU usage to sit at 100%...
Ref:
http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
Click to expand...
Click to collapse
Same here, might be SU fault, but I was using 1.43 when the tablet starts to lag heavily without rebooting. Couldn't find what the culprit was, CPU usage was normal, there was plenty of ram, even tried killing all background apps and services with no luck. Not even a hot boot could fix the lag.
Since then I've updated to SU1.5 so we'll see how that goes.
Sent from my Nexus 10 using Tapatalk 4 Beta
I got a reboot last night. Opened Google Now and it went to the bootanimation. Stock 4.3 with the Flaming Monkey Kernel, SU 1.45. It was my first reboot since January, when I went to custom ROMs. Went back to stock kernel, we'll see if that helps. Also, what AOSP Browser are you guys using? The one from the Installer from the play store closes every 5-10 minutes, and the apk ripped from CM 10.1.1.0 crashes on start-up...And I stopped using Chrome in January, and never had a reboot until Chrome was installed on 4.3. Coincidence? Probably not...
Sent from my MB855 using xda app-developers app
Never had any issues even on 4.2.2 with any sort of memory leak. Was able to go at least 5 days without any reboots and that's with using the chrome browser. I haven't used 4.3 long enough to post my findings with it but so far after 3 days it seems to be about the same. The only thing I can think of is that I bought my Nexus 10 in May so I don't know if a newer hardware version would make any difference.
Also, those of you with random reboots have you tried updating your boot loader yet? Not sure if or how it would make any difference but it's worth a shot.
Sent from my Nexus 10 using Tapatalk HD
Hi,
So my G2 (completely stock) has been great for the past year or so until recently.
Now, when I hit home, it often will stutter for a second or two to redraw all the icons. It seems in general the performance has dropped alot. I'm wondering if the problem is the RAM is being eaten by something, but when i check the app manager there is usually around 500 MB free.
It got so bad that swiftkey was lagging on keystrokes (i would type then wait a few seconds as a bunch of letters finally appeared) and I had to go to the stock keyboard.
When I am in a game however, the performance seems normal.
Anyone have any ideas on what is causing this?
Thank you!
This sounds normal considering you've been running it stock for a year. Sometimes it's good to do a factory reset and start fresh when things get laggy. Reboot if you haven't and see what it's like.
Was hoping NOT to hear that response Mostly because of app data.
Any suggestions for saving app data without root (so i dont think i can titanium backup).
Ok. I've searched all over and have found a thread with a similar problem with no responses. I hope this gets some help. I have a Verizon G2, and ever since the Lollipop update, my battery life has been pretty awful (sometimes less than 2 hours of SOT in 8 hours of battery time), and the performance is horrendous at times. some apps (facebook Messenger especially) will stop when I am using them. No crash report. They just close out of nowhere. Nova Launcher redraws almost every time I hit my home button, sometimes my phone gets ridiculously hot. There are times when Android system restarts, and I lose the navbar and status bar, leaving my phone quite useless for a couple minutes. I do not have a task killer This all happened on 100%stock unrooted
I read something similar happened with the 5.0 release on nexus devices and was related to a memory leak. I have read in ROM threads that the G2 does not have this memory leak.
Things I have tried.
Frequent reboots - Hit or miss temporarily. Sometimes it would reboot into lag and restarting apps
Frequently clearing running apps - sometimes helped for a few hours or so
Factory reset-helped for a couple days
Rooting and installing xposed with the "lollipop Memory leak fix module"-maybe helped for a day? no significant change
Installed a XDABBEB's stock based ROM with TiBu and without =same result - butter for the first few days, but the apps restarting is always there. Then it gradually loses its smoothness and all the problems begin again.
Is this not a common issue? Anyone have any suggestions? I'm thinking of going CM, but I really like LG's floating apps and such. I'd rather stay with stock. They just seem to work better as well.
When it works, it is awesome. I don't think there is any reason to get a new phone as this one still has great hardware. I'm just frustrated. My phone always worked amazingly on kitkat, but Lollipop seems to have ruined it.