PINE64
Android and Ethernet - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PINE A64(+) (https://forum.pine64.org/forumdisplay.php?fid=4)
+--- Forum: Android on Pine A64(+) (https://forum.pine64.org/forumdisplay.php?fid=5)
+--- Thread: Android and Ethernet (/showthread.php?tid=509)

Pages: 1 2 3 4 5 6

RE: Android and Ethernet - Andrew2 - 04-04-2016

(04-04-2016, 05:29 AM)mlamie Wrote: I see a similar complains in the various threats.  They say there is an issue with the 2 GB board, which is not recognized correctly...

Is there a way to update drivers in Android and do some re-testing? Can we ask user:longsleep to have a look? He did a fixed on the Arch Linux image.
http://forum.pine64.org/showthread.php?tid=376&pid=4719#pid4719

Can the Pine team help?

They have to help, especially by improving documentation and some sort of a FAQ since it's close to unbelievable how many users spend hours after hours with these issues.

Currently the RemixOS image has problems with the 2GB models (integer overflow in Ethernet driver leading to crashes or in RemixOS case endless boot loop with connected Ethernet). Fix needed by RemixOS team.

The older Android images and the XFCE Arch Linux image do not show this behaviour but only since they do DRAM initialisation wrong and you end up with a 2GB board where only 1GB RAM is used (and then the Ethernet crash isn't triggered).

Longsleep both identified the problem and provides a fix for the Linux images, see the Linux Development forum threads.

This does not help with Android and no Linux dev even remotely thinks about fixing Android problems unpaid in his spare time!

Users with 2GB model wanting to use RemixOS with Ethernet: No way, you have to wait for a fix. Users with 1GB model: Disconnect Ethernet on the 1st boot otherwise Pine64 will never start (as soon as you see the Remix OS logo you can connect the Ethernet cable). The amount of time the 1st boot needs depends mostly on your SD card's speed (random I/O and not sequential transfer speeds), so in case you tried the spare SD card lying around for years in the drawer be prepared that the first boot takes ages. Cheap/crap cards can be 20-100 times slower than a good quality card or NAND/eMMC normally used on Android devices. And it's not about the 'speed class' but just random I/O.

RE: Android and Ethernet - W1SPY - 04-04-2016

Thanks for the info bud!

Sent from my SM-N900P using Tapatalk

RE: Android and Ethernet - f-stop - 04-05-2016

I have a different problem with mine. I have the 2g+ model and I got android working just fine on it. My problem is when I put in the ethernet cable it runs for 10 seconds and then crashes. I'm thinking this may be a power supply issue because when I just have the ethernet cable plugged in with no mouse or keyboard, it stays on. Once I plug in the mouse it crashes.

Any suggestions?

RE: Android and Ethernet - yusijs - 04-08-2016

(04-03-2016, 12:58 AM)mlamie Wrote: I do have the same experience. The first boot with the network cable connected didn’t work, after the PINE 64A logo I had a white screen for more then 15 min. Without the network cable the first boot did work (After the PINE 64A logo, the desktop of android came), and all reboots after the first boot it starts correctly with the cable attached.

The big issue now: Android doesn't work correctly with the Ethernet connection. The IP assignment is done (see screenshot). A soon I will open the browser I can see the webpage logo or header filled with the webpage name, but no way the page will load completely. The Google Play store, which tries to connect with the Internet will report a timeout message.

Can someone point us in the right direction? Where to search to get more logging?

Device: PINE 64A 2GB version
Image: sun50iw1p1_android_db1000_uart0_0216.img
Network connection: 1000 MB

I installed OS Monitor to check the log of Android (via USB stick with a apk file), I filtered the log messages (see log file).
Code:
2016-04-02 11:20:54,DEBUG,OpenGLRenderer,OS Monitor,Use EGL_SWAP_BEHAVIOR_PRESERVED: false
2016-04-02 11:20:54,DEBUG,Atlas,OS Monitor,Validating map...
2016-04-02 11:20:54,WARNING,Atlas,OS Monitor,Pointer 0x0, not in getPreloadedDrawables?
2016-04-02 11:20:54,WARNING,Atlas,OS Monitor,Pointer 0x0, not in getPreloadedDrawables?
2016-04-02 11:20:55,INFORMATION,OpenGLRenderer,OS Monitor,Initialized EGL, version 1.4
2016-04-02 11:20:55,DEBUG,OpenGLRenderer,OS Monitor,Enabling debug mode 0
2016-04-02 11:20:55,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 11:20:55,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.externalstorage: Resource ID #0x0
2016-04-02 11:20:58,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 11:20:58,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.shell: Resource ID #0x0
2016-04-02 11:20:58,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.google.android.configupdater: Resource ID #0x0
2016-04-02 11:21:03,DEBUG,OpenGLRenderer,OS Monitor,endAllStagingAnimators on 0x7f89f1f400 (RippleDrawable) with handle 0x7f8d240d40
2016-04-02 11:21:06,DEBUG,OpenGLRenderer,OS Monitor,endAllStagingAnimators on 0x7f807b3000 (RippleDrawable) with handle 0x7f8d2701a0
2016-04-02 11:21:50,INFORMATION,Choreographer,OS Monitor,Skipped 35 frames!  The application may be doing too much work on its main thread.

2016-04-02 12:54:22,INFORMATION,art,Unknown,Background partial concurrent mark sweep GC freed 62315(4MB) AllocSpace objects, 257(4MB) LOS objects, 40% free, 12MB/20MB, paused 3.692ms total 177.105ms
2016-04-02 12:54:59,WARNING,art,Unknown,Before Android 4.1, method int android.support.v7.internal.widget.ListViewCompat.lookForSelectablePosition(int, boolean) would have incorrectly overridden the package-private method in android.widget.ListView
2016-04-02 12:55:02,WARNING,InputEventReceiver,Unknown,Attempted to finish an input event but the input event receiver has already been disposed.
2016-04-02 12:55:34,WARNING,osmcore,Unknown,type=1400 audit(0.0:3): avc: denied { syslog_read } for scontext=u:r:untrusted_app:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0
2016-04-02 12:55:37,WARNING,InputEventReceiver,Unknown,Attempted to finish an input event but the input event receiver has already been disposed.
2016-04-02 12:55:48,DEBUG,OpenGLRenderer,Unknown,endAllStagingAnimators on 0x7f83389c00 (RippleDrawable) with handle 0x7f922619c0
2016-04-02 12:55:51,WARNING,Resources,Unknown,Converting to string: TypedValue{t=0x10/d=0x2 a=-1}
2016-04-02 12:56:10,DEBUG,OpenGLRenderer,Unknown,endAllStagingAnimators on 0x7f833d3000 (RippleDrawable) with handle 0x7f92343500
2016-04-02 12:56:19,INFORMATION,art,Unknown,Background partial concurrent mark sweep GC freed 54156(3MB) AllocSpace objects, 214(4MB) LOS objects, 39% free, 13MB/21MB, paused 2.153ms total 121.109ms
2016-04-02 12:56:36,VERBOSE,OSMCore,Unknown,force Exit

2016-04-02 12:56:37,INFORMATION,Process,Unknown,Sending signal. PID: 26487 SIG: 9
2016-04-02 12:56:43,DEBUG,OpenGLRenderer,OS Monitor,Use EGL_SWAP_BEHAVIOR_PRESERVED: false
2016-04-02 12:56:43,DEBUG,Atlas,OS Monitor,Validating map...
2016-04-02 12:56:43,VERBOSE,OSMCore,OS Monitor,use file system Unix domain socket
2016-04-02 12:56:43,INFORMATION,OpenGLRenderer,OS Monitor,Initialized EGL, version 1.4
2016-04-02 12:56:43,DEBUG,OpenGLRenderer,OS Monitor,Enabling debug mode 0
2016-04-02 12:56:44,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:44,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.providers.userdictionary: Resource ID #0x0
2016-04-02 12:56:44,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:44,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.google.android.gsf: Resource ID #0x0
2016-04-02 12:56:46,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:46,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.externalstorage: Resource ID #0x0
2016-04-02 12:56:46,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:46,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.packageinstaller: Resource ID #0x0
2016-04-02 12:56:46,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:46,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.defcontainer: Resource ID #0x0
2016-04-02 12:56:46,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:46,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.google.android.partnersetup: Resource ID #0x0
2016-04-02 12:56:46,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:46,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.google.android.gsf: Resource ID #0x0
2016-04-02 12:56:59,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:56:59,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.android.shell: Resource ID #0x0
2016-04-02 12:58:44,WARNING,ResourceType,OS Monitor,No package identifier when getting value for resource number 0x00000000
2016-04-02 12:58:44,WARNING,PackageManager,OS Monitor,Failure retrieving resources for com.google.android.gsf: Resource ID #0x0
2016-04-02 01:00:01,INFORMATION,art,OS Monitor,Background sticky concurrent mark sweep GC freed 36814(2MB) AllocSpace objects, 241(4MB) LOS objects, 37% free, 12MB/19MB, paused 5.553ms total 85.808ms
2016-04-02 01:00:17,INFORMATION,art,OS Monitor,Background sticky concurrent mark sweep GC freed 45174(1545KB) AllocSpace objects, 78(1248KB) LOS objects, 24% free, 8MB/11MB, paused 9.155ms total 33.023ms

I also included screenshots: http://imgur.com/a/QYVST

[Image: TAKqkii.png]

[Image: e6V2qa6.png]

[Image: YkWscyX.png]

[Image: 6czh0b1.png]

[Image: QfHP8YX.png]

[Image: XysrUXD.png]

[Image: 1iOvBOo.png]

This is 100% the same thing happening to me with a 2GB board. I also found I was able to browse around on my NAS on my local network, but wasnt able to do playback or anything like that one it. 

I thought when they said they would support Android and Ubuntu that they would have working versions by launch. Probably would've waited with buying if I had known this beforehand. Ah well.

RE: Android and Ethernet - zenmetsu - 04-08-2016

This is a DMA conflict with the 2GB board's gigabit ethernet device. Hardware new to market + DMA issue = Fix coming "Soon™*"

*Soon™ = Current date + 5

Honestly, it would be faster to sell your 2GB board on ebay and find someone selling the non-gigabit version.

RE: Android and Ethernet - yusijs - 04-08-2016

Yeah, probably. Seems silly though. Guess I'll use it as a letterweight, seems to be all its good for atm :3

RE: Android and Ethernet - Roverius - 04-09-2016

I started the Android version and i DONT even see a network connection.

Is there a way to enable LAN on Android? or check connectivity?
According to WIKI, the problem with the 2Gb Ram should be solved.
I booted the Pine with LAN connected and it booted fine, except i dont have any network connection at all.
Network ip is provided by DHCP on router.

Note:
Known problems
  1. GbE still unable to connect and currently fixing it. 100Mbps Ethernet link should be no problem.
Could the problem be because i am connected on a Gigabit Switch/Router?
What if i place a 100Mb switch bewteen the pine and the Gb Switch?




This is from WIKI:
http://wiki.pine64.org/index.php/Pine_A64_Software_Release
---------------------------------------------------------------------
Android Image Release 20160216
Google Drive Direct Download
Mega.nz Drive Direct Download
Torrent Download
MD5: 0aca1b9cc94babdb9313ce8c33a154f2
File Size: 345MB
Improvements
Solved Gigabit Ethernet Hang issues
Please take note that this release is for Pine A64 1GB and 2GB Ram version only.
------------------------------------------------------------------------------------------------

RE: Android and Ethernet - Roverius - 04-09-2016

OK,

I tried to boot the pine with a 100mb switch in place.
The Pine boots in a loop.
If i pull out the Lan Cable, the Pine boots normal.
The i place the Lan cable back after it has booted and then the pine shuts down en restarts back in a loop.

There is much work to be done before some decent Android will work on the Pine :\

RE: Android and Ethernet - Icetrips - 04-09-2016

I have the same issue with the 2gb version.

I connected the ethernet only after booted.
My ethernet seem to work... but I have really poor performance.
Probably as your diagnostic... connect/disconnect.

For example, I just downloaded an 113mb application in google play, seem this will take 8 hours...

I expect developper will have to release a new image for support the 2gb ethernet correctly.

RE: Android and Ethernet - yusijs - 04-10-2016

(04-09-2016, 11:02 PM)Icetrips Wrote: I have the same issue with the 2gb version.

I connected the ethernet only after booted.
My ethernet seem to work... but I have really poor performance.
Probably as your diagnostic... connect/disconnect.

For example, I just downloaded an 113mb application in google play, seem this will take 8 hours...

I expect developper will have to release a new image for support the 2gb ethernet correctly.

Lucky you - my board fails to open google play. :3