circles forever on Android 4.4.4

[sdgathman]

This is a Tracfone, and can't be rooted (at least not without 'leet skillz). Dat-installer 1.0.1. kernel-3.4.42-g6bc71f3

Tracing IP4 packets from the phone (on my home network), I see google monitoring my whereabouts, DNS requests (for google domains), and ARP. Nothing that could be Dat. I did not see any IP6 traffic (the phone does have an IP6 ip).

The phone has a 16GB SD card.

[staltz]

Interesting.

The phone doesn't need to be rooted for this to work. So one hypothesis ruled out.

The "starting up" circles happen simply due to the node.js background process starting up. Until it starts up, it shouldn't be doing any network requests.

Could you show me a portion of your logcat related to this? Just plug the USB to a computer then run adb logcat and run the app.

[sdgathman]

Started adb service:

# systemctl status -l adb
● adb.service - Android Debug Bridge (adb) service
   Loaded: loaded (/usr/lib/systemd/system/adb.service; disabled; vendor preset:
   Active: active (running) since Tue 2017-10-31 09:58:22 EDT; 13s ago
  Process: 31907 ExecStart=/usr/bin/adb start-server (code=exited, status=0/SUCC
 Main PID: 31908 (adb)
    Tasks: 5 (limit: 4915)
   CGroup: /system.slice/adb.service
           └─31908 adb -L tcp:5037 fork-server server --reply-fd 4

Oct 31 09:58:16 elissa.gathman.org systemd[1]: Starting Android Debug Bridge (ad
Oct 31 09:58:22 elissa.gathman.org adb[31907]: * daemon not running. starting it
Oct 31 09:58:22 elissa.gathman.org adb[31907]: * daemon started successfully *
Oct 31 09:58:22 elissa.gathman.org systemd[1]: Started Android Debug Bridge (adb

Ran adb logcat and started app - nothing:

$ adb logcat
- waiting for device -

[staltz]

Do you have developer mode turned on in the device? Try searching the web for help to get the adb logcat working, before solving that it'll be hard to solve this issue.

[sdgathman]

Turned on developer mode and PMed you a link to logcat via SSB.

[staltz]

Thanks, I found the relevant part in the logcat:

I/RNNodeThread( 6128): Node.js process is running...
E/nodejs  ( 6128): CANNOT LINK EXECUTABLE: cannot locate symbol "sigfillset" referenced by "/data/data/com.staltz.datinstaller/node"...
I/RNNodeThread( 6128): Node.js process terminated.

[sdgathman]

I've used rhino (Java implementation of javascript) for some minor things (scriptlets in Java apps) on servers. Is that usable on Android?

[staltz]

Hmm, no idea about that

[dominictarr]

I'm seeing the same problem here, it's just spinning endlessly

[dominictarr]

I also saw:

E/nodejs  ( 7459): CANNOT LINK EXECUTABLE: cannot locate symbol "sigfillset" referenced by "/data/data/com.mmmmm/node"...

[staltz]

@dominictarr what's your Android version?

[dominictarr]

it's also 4.4.4

On 12/4/17, André Staltz notifications@github.com wrote:

@dominictarr what's your Android version?

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/staltz/dat-installer/issues/2#issuecomment-348899070

[staltz]

I did some investigation, and it seems that "sigfillset" errors happens when an app is compiled for a SDK higher version than the device has.

This is probably solvable by re-compiling node for android, updating react-native-node, then updating this project. Probably isn't a huge effort to solve this.

But I see it as rather low-priority because Android 4.x is considered old, not supported, so it won't get security patches. Also because these apps are being built for the future, Android 4.x and lower versions will be less common (it's already just 28%, while >=5.0 versions are 72%).

So it's good to solve this, but not a show-stopper.

[dominictarr]

28% is a still a lot of people! it's just a bit less than 1/3 people!

[staltz]

Yes, a lot, but constantly decreasing :)

[dominictarr]

but how much work do you estimate it would be to build for 4 also?

[staltz]

Maybe 1 day of work?

[staltz]

Update: Android >=5.0 is now 82% of all versions, and probably porting this app to nodejs-mobile which (theoretically?) supports Android >=4.1 would help.