Related
Chrome still freezes and locks the N10. Have to reboot so the software update didnt change this for me. I will just stick to Dolphin as I get no freezes using that browser.
Sent from my Nexus 10 using xda premium
Can you reproduce the crash? I've used Chrome, on 4.2.2, and have had no crashes (I don't even think I had any crashes in the past either).
espionage724 said:
Can you reproduce the crash? I've used Chrome, on 4.2.2, and have had no crashes (I don't even think I had any crashes in the past either).
Click to expand...
Click to collapse
Same.. Never a crash on 4.2.1 or 4.2.2 and I've always used Chrome..
I think it might just be my device as I got freezes with chrome from the day I bought it. I stop using Chrome and lockups stopped. Just got the update two days ago and I used Chrome for the first time and the first website I went too and was reading an article, it froze up and I had to do a hard reset. I'm all stock and not rooted.
Sent from my Nexus 10 using xda premium
returned?
I haven't had any crashes or any issues that everyone else has had. Maybe its because I waited to buy my nexus 4 and nexus 10 until February but if I did experience any of those issues I would have returned the device. Why bother with it? That's just my two cents but thank god I haven't had any issues, Yet!! And hopefully I never do
No need to return as I perfer Dolphin anyways, which solved my problem. I bought it from Staples in Jan. and would have been easy to return if I chose too.
Sent from my SAMSUNG-SGH-I317 using xda premium
Mine crash like nobody business using chrome at 4.2 or 4.2.1
The problem was fix for me after running 4.2.2, by the way I am using latest chrome beta as it perform much better.
Odd, got mine in November and have never had a chrome crash/freeze or hard restart. Admittedly, my average use is less than 3 hours daily, but still...
Sent from my SGH-T889
Did you try the newest Chrome beta?
Chrome still crashes for me.
I have Chrome neatly frozen with Titanium Backup since I got the N10 (I had terrible experience with it on my phone). Never had any problems related to it.
This thread begs my question. I am using Chrome Beta but what do you do with the native Chrome? I have both installed because it seems like Chrome is pretty well integrated into the system and there isn't a uninstall option.
I could freeze it but don't want it to cause any issues.
Any thoughts or experiences?
Sent from my EVO using Tapatalk 2
I use Chrome beta, and have had 1 hard-freeze in Chrome in approx 20 hours use since the upgrade to 4.2.2. Being the beta version of Chrome it can occasionally crash also, but its not too often this happens now either. I don't mind Chrome crashing every few hours as its only a 3 second job to press the button on my homescreen with my tabs still loaded when it re-opens, but freezes are not cool.
Before that, I was on cyanogenmod and Chrome would get a freeze every 5 hours or so.
Only had occasional freezes in Chrome beta since early December. In over 100 hours uptime since installing 4.2.2 I've only used Chrome (not beta!) and had zero lagging, zero freezes and no reboots.
... beamed from my Nexus 10 to your planet
I was having major problems with chrome after 4.2.2 it was just being sluggish and locking up for seconds or more at a time, rebooting seems to fix it and the problem is intermittent.
I have always had lock up and restart problems in chrome on my Nexus 10. I cannot see a particular repeatable browser action and/or site that causes the lock up, but the process is always the same:
Browsing, chrome hangs, screen buttons freeze, and after multiple screen touches the device will shut down and restart.
Happens perhaps 3-4 times a week
I have also had it lock up like that one time while using the cameras, but only once. I have owned the device since launch.
Sent from my Nexus 7 using Tapatalk HD
I had crashes several times per day with Chrome (beta and stock)and 4.2.1. I've had zero crashes under 4.2.2 with Chrome beta. I haven't tried the stick version under 4.2.2.
I used to continually have issues with chrome locking or rebooting. Not sure if it was the change to 4.2.2 or the fact I finally bit the bullet and rooted then installed Seeder and LagFix Free but I haven't had a lock up since and things seem to be running faster than ever!!!! Still stock rom and kernel
I still get crashes with 4.2.2, but it's much reduced compared to 4.2.1. I used to be getting several a day and now it's every couple days.
For those with issues, have you performed a factory reset?
As we all have figured by now, JSS is broken. The dead locks are in AOSP r2.1.
Do we want to search for solutions together and share what we might find here?
Options would be to bring this to Googles attention, monitoring and cherry-picking master commits (i just saw some today referring to dead locks) and tracking the differences between JWR (r1) and JSS (r2.1).
To me the issue seems to be not kernel related, looks like surfaceflinger to me, thread concurrency.
as for the symptoms,
It's too random [..]. Looks like everything else continue work in background. I get ~X seconds of hang each time, and after some input actions got executed in row.
And hangs come in bursts and then do no appear for hours...
Click to expand...
Click to collapse
It is true that it goes to deadlock for input but it occurs on other parts of the OS so it is not just input, input is just a strong way to get to the issue which is why it is reported on that part and it is more common on input.
Has stated above, Surfaceflinger is not just having issues with text input, it is also having issues with screen input has well.
Maybe some code in Surfaceflinger is having issues with the kernel since the code is not completely correct.
By the way I did get a deadlock while typing this.
Sent from my Nexus 4 using Tapatalk 4
This doesnt look like a memory (RAM) problem. I just used again my N4 and I got one of those freezes.
I say that because I got it right after rebooting, with no apps opened
Bluewall said:
This doesnt look like a memory (RAM) problem. I just used again my N4 and I got one of those freezes.
I say that because I got it right after rebooting, with no apps opened
Click to expand...
Click to collapse
I have over 1GB of ram free and still get this issue.
Sent from my Nexus 4 using Tapatalk 4
I dont think that this is only related to surfaceflinger. It happens often enough when I left the phone with screen on some time and want to use it again. Everything locks up. Even the signal bar does just sit there. Aswell as when waking it up to enter my pin code.
Sent from my Nexus 4 using xda premium
Bluewall said:
This doesnt look like a memory (RAM) problem. I just used again my N4 and I got one of those freezes.
I say that because I got it right after rebooting, with no apps opened
Click to expand...
Click to collapse
there are new commits up for frameworks/native master
046b72f Merge "fix a possible deadlock when removing a layer and destroying a client" by Jean-Baptiste Queru - 3 days ago master
e5886d9 fix a possible deadlock when removing a layer and destroying a client by Mathias Agopian - 9 weeks ago
9f476fd Merge "Add a symbol to represent MNC=0" by Wink Saville - 10 days ago
8df483c Add a symbol to represent MNC=0 by Johan Redestig - 2 months ago
082fc1c am ae961022: Merge "EGL: Fix error for eglCreateWindowSurface" by Jesse Hall - 3 weeks ago
ae96102 Merge "EGL: Fix error for eglCreateWindowSurface" by Jesse Hall - 3 weeks ago jb-mr1.1-dev-plus-aosp
77a9b4a EGL: Fix error for eglCreateWindowSurface by Jonathan Hamilton - 3 weeks ago
384f55f Merge "Tweaks for forward compatibility" into stage-aosp-master by Jean-Baptiste Queru - 3 weeks ago
b6a0ca7 Tweaks for forward compatibility by Jean-Baptiste Queru - 3 weeks ago
65752b2 Reconcile with jb-mr2-zeroday-release - do not merge by The Android Open Source Project - 4 weeks ago
70421f3 merge in jb-mr2-zeroday-release history after reset to jb-mr2-dev by The Android Automerger - 4 weeks ago jb-mr2.0-release android-4.3_r2.1
00aea5c am ac9a96da: fix a dead-lock in sensorservice by Mathias Agopian - 4 weeks ago
ac9a96d fix a dead-lock in sensorservice by Mathias Agopian - 4 weeks ago jb-mr2-dev
9201798 Reconcile with jb-mr2-zeroday-release - do not merge by The Android Open Source Project - 4 weeks ago
176c0fd merge in jb-mr2-zeroday-release history after reset to jb-mr2-dev by The Android Automerger - 4 weeks ago
47f31b1 Reconcile with jb-mr2-release - do not merge by The Android Open Source Project - 4 weeks ago
439b197 Find non-extension GLES wrappers in eglGetProcAddress by Jesse Hall - 5 weeks ago jb-mr2-release android-4.3_r1
Click to expand...
Click to collapse
R2.1 (JSS)
R1 (JWR)
it's interesting that R2.1 saw dead lock related "fixes" while master comes back to it.
the google developer had this to say
simplifed the code a bit, and made it behave a little
closer to mr1.1 -- I couldn't convince myself that
some changes in how locks were used were correct.
Click to expand...
Click to collapse
i'm trying this now - problem is the random nature. i haven't had a freeze for 3 days now. if more developers can implement changes maybe we can evaluate this better.
perhaps tracking more repos would make sense, fw/native is just a stab into the blue.
I just wanted to say that its seems to be very app pendant.
I am experiencing those freezes only within whatsapp. while typing very fast on the keyboard, the freezes do often occur. it's not an app freeze, it's the deadlock freeze.
I did not notice something similar while using other apps, even apps which use a lot more of resources (like 3d games and stuff like that)
P
I have got the logcat and it contains a damn long list of ANRs, kernel issues and MUCH more. o.o
Screenshot of a log which says what is going on:
View attachment 2176393
Logcat here on my site: http://caftp.3owl.com/Downloads/Logcats/Log_2013-08-09_12-00-25.txt
Sent from my Nexus 4 using Tapatalk 4
I use Swype and never seen this issue. Weird
I only got that problem while typing something and it seems some **** is doing too much work on the Main Thread.
franciscofranco said:
I only got that problem while typing something and it seems some **** is doing too much work on the Main Thread.
Click to expand...
Click to collapse
Moles I'm on your latest beta in the dev, the 8.9 build and I just experienced a lock playing candy crush. Wanted to give the feedback that the changes may not have helped.
Is't it weird that some users have this and others do not ?
I had never seen this, 1 day with AOSPA kernel, then updated to faux 19b4 and then 19b4m (no oc).
I thought it might be related to the new touch driver, because i though only input was freezing (since i never saw this issue), but now i seem to understand that it is freezing the whole phone ?
I've tested plenty JSS roms and kernels combo and freezes are there and happening randomly.I really hope you guys can solve this issue.Good luck !:thumbup:
"using the search button won't get you killed" <--taptalk sig
derPianist said:
I just wanted to say that its seems to be very app pendant.
I am experiencing those freezes only within whatsapp. while typing very fast on the keyboard, the freezes do often occur. it's not an app freeze, it's the deadlock freeze.
I did not notice something similar while using other apps, even apps which use a lot more of resources (like 3d games and stuff like that)
P
Click to expand...
Click to collapse
franciscofranco said:
I only got that problem while typing something and it seems some **** is doing too much work on the Main Thread.
Click to expand...
Click to collapse
yes. I can confirm this. just answered a message in Skype and got the freeze. so it does not seem to be app pendant.
P
derPianist said:
yes. I can confirm this. just answered a message in Skype and got the freeze. so it does not seem to be app pendant.
P
Click to expand...
Click to collapse
I just got it using XDA app while typing. It looked like something was blocking the Main Thread/UI Thread.
Sent from my AOSP using xda premium
I got lockups constantly while texting. Froze the aosp keyboard and installed the Google keyboard from play store. So far not a single lockup
Sent from my Nexus 7 using xda app-developers app
It's not a specific keyboard problem. Before I flashed back to stock ROM, I was getting freezes with google keyboard, swiftkey, and kii. Additionally, I was getting freezes when not even doing input. Most of the worst freezes occurred when downloading.
scottharris4 said:
It's not a specific keyboard problem. Before I flashed back to stock ROM, I was getting freezes with google keyboard, swiftkey, and kii. Additionally, I was getting freezes when not even doing input. Most of the worst freezes occurred when downloading.
Click to expand...
Click to collapse
+1
Sent from my Nexus 4 using Tapatalk 4
Google should be paying you guys instead of their pot head so called Engineers. :laugh:
scottharris4 said:
It's not a specific keyboard problem. Before I flashed back to stock ROM, I was getting freezes with google keyboard, swiftkey, and kii. Additionally, I was getting freezes when not even doing input. Most of the worst freezes occurred when downloading.
Click to expand...
Click to collapse
Just reporting in case anyone else was having the same issue I had. Typing was slow and choppy on aosp and had a roughly 80% chance of lockup. Since switching to Google keyboard that hasn't happened a single time.
Sent from my Nexus 4 using xda app-developers app
Hi guys, can anyone tell me how can I fix this situation, because when I'm using my Nexus 9 most of the times when I minimize an app and open other, most of the time the app that I minimize will restart.
Did a factory defaults and options in developper seem to be ok, no restritctions regarding apps on backgroung.
Usually I play Star wars Galaxy of heroes, and if I change to discord (chat app) when I return it restarts my game
I also noticed that Ram availability is low, and I did a factory default 2 days ago, only installed the game and discord, nothing else.
Any suggestion?? Should I Root and Install a new ROM, if so what would you recommend?
I would prefer to Keep the actual OS if there's a fix for it
Thanks
I can't help but wonder if this is similar to what mine does. The apps in the recent display disappear -not all of them but definitely 50%. This does not happen on my N5X. I can't say when it started but at least 4 months ago.
Sent from my Nexus 5X using Tapatalk
ritchea said:
I can't help but wonder if this is similar to what mine does. The apps in the recent display disappear -not all of them but definitely 50%. This does not happen on my N5X. I can't say when it started but at least 4 months ago.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hi, the apps don't disappear, the tabs are there, they simply restart when I select them instead of just changing back to the previously running app.
It's kind of annoying when I'm on the middle of a game and want to check out something else, if I switch to chrome or other app there is a big risk that the game will restart and I will lost any progression made...same happens with other apps.
Hi there!
I have tried like 15 oreo roms and I always end up with my camera app crashing or freezing entire phone.
I don't use camera ports, just stock apps. It works fine at the beginning but after a day or so it starts to crash and freeze.
Did anybody have similar problems? What can be causing this kind of behavior? Do I need to upgrade anything (firmware maybe?) to run oreo without problems?
Same thing for me, i even had a problem that my photos were not saved, but I tried using Camera MX today, works ok without crashing and freezing for now.
Same problem here. Really frustrating.
Sent from my Redmi Note 3 using Tapatalk
After 4 days of using the phone....
Upgraded latest color OS
Instagram isn't opening and by chance if it does it is crashing in a minute or two.
Any help ?