Extremely slow on android

[timsuchanek]

Hey, first of all: Awesome library!
The API and the usage is just pure awesome!

I am trying RNRF on Android on a Nexus 5, but only get very slow responses, see here:
https://drive.google.com/file/d/0B-zpEic041zoR1Fhd0VhTnA5VkU/view?usp=sharing

Any idea why that is the case?
Thanks!

[aksonov]

The problem I don't have android. Maybe community could help. Have you tried to debug? This component is just wrapper around exNavigator. Does ExNavigator work well on android?

[danielweinmann]

@timsuchanek, did you test it without live reloading and chrome debugging? For me it's only (extremely) slow when I have live reloading or chrome debugging on ;)

[timsuchanek]

Hey, yes I tried it without debugger enabled. But what I found:
If it has already been opened once, it's a lot faster.
Only the first 1-2 times it's slow.
I'll check ExNavigator standalone

[micksabox]

Hey @timsuchanek thanks for reporting this. Is it slow without animations (i.e. a <Scheme> with no animation config)? I am willing to compromise animations for performance if worse comes to worse. I don't have an Android either, or else I would try it myself.

[sbycrosz]

I can confirm the example app slowed down on Android 4.4 (It takes ~2s from clicking a button to any route changes). And the exNavigator examples don't have the same issue.

Edit: After enabling chrome debugging the delay magically disappear -__________-

[aksonov]

@sbycrosz Is it slow for tab bar or for all pages?

[zebulgar]

I've been testing this library on Android today and it appears to be working fine as long as I don't use the chrome debugging.

There does seem to be a delay in 'switch' animations between tabs. I'm looking into it.

[osdio]

I have test the 'switch' on tab, it's too slow, about 1.5s to change the tab. I have turn off the chrome debug and live reload, it's the same.

[aksonov]

Could you check latest version? Also please uncomment console logging within debug.js and check.

[doomsower]

I've tried to debug Example app from version 2.3.1 on Android tablet. Animations were extremely slow.
Here is console output with debug.js uncommented
I also made a release build of simple app (using version 2.3.1) and ran it on Samsung Galaxy S3. Again everything was very slow.
Maybe updating "@exponent/react-native-navigator": "^0.3.5" to latest will fix it?

[aksonov]

Please check core exnavigator code

Pavel.

24 февр. 2016 г., в 21:18, doomsower notifications@github.com написал(а):

I've tried to debug Example app from version 2.3.1 on Android tablet. Animations were extremely slow.
Here is console output with debug.js uncommented
I also made a release build of simple app (using version 2.3.1) and ran it on Samsung Galaxy S3. Again everything was very slow.
Maybe updating "@exponent/react-native-navigator": "^0.3.5" to latest will fix it?

—
Reply to this email directly or view it on GitHub.

[doddys]

Hi,

I am also experiencing slowness. However, when chrome debugging is enabled, it is faster .
Behaviour in simulator (android and iOS) and physical device is the same as when chrome debugging is disabled.

Is there anyway to disabled "@exponent/react-native-navigator" completely to isolate the problem?

Doddy

[TonyCois]

Hi,

I had this problem too, but I solved it by disabling the dev mode.

Here the issue on react-native github :
facebook/react-native#3049

I tried another router and it was exactly the same on android. The demo was
very slow. So, I'm not sure that it comes to react-native-router-flux :)

Tony

Le ven. 26 févr. 2016 à 03:10, doddys notifications@github.com a écrit :

Hi,

I am also experiencing slowness. However, when chrome debugging is
enabled, it is faster .
Behaviour in simulator (android and iOS) and physical device is the same
as when chrome debugging is disabled.

Is there anyway to disabled "@exponent/react-native-navigator" completely
to isolate the problem?

Doddy

—
Reply to this email directly or view it on GitHub
#199 (comment)
.

[doddys]

Hi,

I finally found why it was slow on my device/simulator. I was due to my own mistake.
I was doing a console.log(action) in the reducers. That turns out slow things a lot. Especially when executed on the device. It was ok when chrome debugging was turned on because it is executed using the chrome javascript engine which is much more powerful (laptop vs device).

After removing all the log(action), its much better now.

Doddy

[mofelee]

@doddys works for me 👍