Opera 28 on Lolipop Crashes
-
scottb last edited by
Opera 29 still crashing for me on two devices, Nexus 5, Android 5.1.0 and Sony Xperia Z3 Compact, Android 5.0.2.
-
Deleted User last edited by
Here too. Note 3 with 5.0
Can you confirm that in developer menu you have all animations settings set on x1? Beside installation process these animation settings are the second trigger in first v29.
-
stefa011 last edited by
Here too. Note 3 with 5.0
Can you confirm that in developer menu you have all animations settings set on x1? Beside installation process these animation settings are the second trigger in first v29.
Can you be more precise
-
stefa011 last edited by
Device settings → Developer options {}.
Thanks for help, but still I cannot find it in my Sam Note 3 sertings
-
stefa011 last edited by
Here too. Note 3 with 5.0 Can you confirm that in developer menu you have all animations settings set on x1? Beside installation process these animation settings are the second trigger in first v29.
Can you be more precise
Yes it is x1!!!
-
emoller last edited by
Here too. Note 3 with 5.0
Can you confirm that in developer menu you have all animations settings set on x1? Beside installation process these animation settings are the second trigger in first v29.
Where did you get that idea from sagrid?
-
Deleted User last edited by
Here too. Note 3 with 5.0 Can you confirm that in developer menu you have all animations settings set on x1? Beside installation process these animation settings are the second trigger in first v29.
Where did you get that idea from sagrid?
Opera 29 can adjust the animation values as for WebKit(JB)/Chrome(KK). I bet that Google Chrome guys by their own doesn't know how to do that. Animations are delegated to compression heuristics now and on Chrome all flags are cluttered also, it's a whole mess.
-
emoller last edited by
Animations are delegated to compression heuristics now
Aooow... my brain hurts.
Ok, back to the topic...the crash that was discussed in this thread did only occur when you had a specific setting unchecked, but it had nothing to do with animations. -
Deleted User last edited by
Funny thing to say because 'mindnoise' was the first mini4 brand checking animations beside 'linkid' since old days, suggestive brand names don't you think? Transition flag up to chrome40 and heuristic set to 'none' does the same thing, btw. Bottom up, just exposing Appboy ID at first run can crash JB 4.3, beside that 29 first flavor works as it should.
-
Deleted User last edited by
My bad, Chrome Dev channel can be blamed for all crippled things lately: deprecated flags + another set of adware.