Android ( Galaxy Note 2 , Note 10.1 - Android 4.1.1 ) not Working TweenMax

[KTS 0 Likes (Newbie)]

Hi ,

I'm Not well English... sorry ,


I'm Using TweenMax.js 1.8.0

used to exmaple :

function clickAAA() {

TweenMax.to(aaa, 0.75, {y:0, onUpdate:test1, onComplete:test2});
}

Well Working Any Device , OS...

but Samsung Galaxy Note 2 (Android 4.1.1)

, Samsung Galaxy Note 10.1 ( Android 4.1.2 ) , and I'm not have Other Device )

No Working...

Where : Original Browser
When:

[ Browser - Tab 1] Loading page and tween max Method click -> Well Done!

Go More Tab [ Broswer - Tab2 - other page ] And Return [ Broswer - Tab1] and click -> Not Working!

 

i think not working ticker

i'm tested 'https://www.greensock.com/get-started-js/' , has same problem.

this problem to cause Device?

please help and advice,

Thanks you

[KTS 0 Likes (Newbie)]

I'm find solution!!!

 

TweenMax.js ( 1.8.0 version)

 

Line 4694 ~ 4701

 

 

 

//a bug in iOS 6 Safari occasionally prevents the requestAnimationFrame from working initially, so we use a 1-second timeout that automatically falls back to setTimeout() if it senses this condition.

            setTimeout(function() {

                if (_useRAF && !_id) {

                    _self.useRAF(false);

                }

 

            }, 1000);

 

 

to change 

 

 

      setTimeout(function() {

                    _self.useRAF(false);

 

            }, 1000);

 

 

 working TweenMax.to!...

 

but , i think change code mean 'not use requestAnimationFrame'; 

 

i'm afraid to performance down...

 

please help other solution~!

 

 

[GreenSock 12,333 Likes (Superhero)]

I don't have that specific device, but in testing on an Android tablet TweenMax seems to work fine. I wonder if there's a browser bug in the device you're talking about. You can disable the requestAnimationFrame functionality for GSAP by simply calling this after the files have loaded: 

 

 

TweenLite.ticker.useRAF(false);
 

 

 

Does that solve things for you?

[Dhashvir 0 Likes (Newbie)]

I can confirm that on android 4.1.1 and 4.1.2 that requestanimationframe gets cancelled opening a new tab and never gets started again when navigating back to the tab. Tested on Samsung Note 2, S3 on both 4.1.1 & 4.1.2.