Received my 1gb PINE last week. Debian, Ubuntu, and RemixOS all detect ethernet and connect. No such luck with Android. Status shows IP address as "Unavailable." I have link and activity lights, so the hardware is fine. Thoughts?
After having my pine since they first came out I finally got around to setting it up on Android. Here is what i have done so far and it seems to work great.
Bought a brand new SanDisk Extreme 32GB microSDHC UHS-1 card (95/90 read/write speeds). Used diskpart to clear the partition table and create a new primary partition. I used PheonixCard v310 with the latest PheonixCard android image from the pine wiki (428) and i was able to burn the image on the first try.
The first boot on the pine took less than 2 minutes and then from there I tried connecting to the play store or browser. No Ethernet connectivity. Read about this issue on the forum and found the problem. Gig ethernet not currently working for the 2GB pine board. Using the suggestions and connecting the board to a base10T switch inline with my router I was able gain access to the internet via the pine board.
Speedtests comparison with my android phone (M8) to the pine board.
download / upload (MBPS)
Pine64 : 6.9 / 5.3
M8: 32.1 / 12.1
Installed Kodi on my pine and was able to stably steam show and movies. I would call that a success. I also read posts about power being an issue; I am using a 40W two-port Anker charging brick; 2.4 amp port. Works great with all my micro sd devices.
yes, phoenix card is 100% PoS!
I tried million times to burn image on my 2 cards. finally, success!!! now it working everything, but on 100Mb LAN. Gb still not working...
same issue here, all working perfect on 100Mb/s or linux, no luck on android at 1Gb/s.
If anyone knows a trick to access the ethernet driver and change settings I'll take that.
We are currently getting the latest PHY driver from Realtek (PHY chip vendor) and check whether this will resolve the Gbit issue or concern. In our own lab, the Gbit seems works fine and we are that users seems getting no good results. Hopefully, the new PHY driver integration will able to resolve this outstanding issue. This takes 2-3 week for release.