PINE64

A noob's first effort!

Spent most of the trying different SD cards and readers trying to find out why the computer said my cards are 32G and empty and the recommended image writer kept say I had 0Kb free. Switched to Win32DiskImager and all went well with flying colors.

Found out that the HDMI to VGA adapter that came with the Pine does not work and system would not boot. Booted within minutes once it was connected to 1080P HDMI TV.  Used the ethernet connection for first boot, then switched to WiFi. Everything seemed to going well. Video playback from YouTube was good and synced. No jitters.

I am using the IR remote for now. In the middle of testing phone rings so I just hit the mute button on the remote. When I go back to testing I have lost volume control that I had previously. Before I could set it at any level now it is either all the way off or wide open using the volume control buttons. Don't know why I lost control.

I did some brief testing with Kodi using KodiMaster build. I will say this do not attempt this without 2G. CPU usage while less than 50% most times the memory was down to only about 970M. Kodi will play and plays well but at times is sluggish in responding to commands. Lot of icons and graphics in the menus take time to load. You could cut it back to just text and save some time. Video playback was good with no buffering so that was a good sign. I did hear a low growl like a fan or hard drive at time when the Pine was straining to load something in Kodi. Didn't track it down but it is probably in the audio. I don't hear it in other apps.

I haven't tried Netflix or Hulu yet, but did try my favorite Playstation VUE that I use for live TV. It did install but when I went to run it I got an error message that it would not play in rooted devices so I guess using it for VUE is out of the question.

Compared to my normal box an Amazon Fire TV, Pine would get a C grade. Passing but just barely. But hey for about 1/3 the cost what can you expect. 

It's late and I am tired so that is it for now. Tomorrow I will move it to a 4K TV and see what happens when really pushed. Still wonder what happened to my volume controls with the IR remote. Might try a fresh image and leave the mute button alone but someone will eventually push it.

Traveler: the 2GB may be required, because of these settings: https://github.com/ayufan-pine64/device-...vice.mk#L3.

This are the VM memory settings with which are the images build (they are for 2GB): https://android.googlesource.com/platfor...ik-heap.mk

If you would edit build.prop to make them like this: https://android.googlesource.com/platfor...ik-heap.mk (which are for 1GB devices), your Pine should also work fine.

It is also probable that it would work on 512M device if these parameters were to be used: https://android.googlesource.com/platfor...ik-heap.mk

sir ayufan, ca android release, can you develop any android release (7.0, 6.0, 5.1,etc) with a cyanogen image like they have over aat the android x86 project site? it would open the doors to more user development on these releases, or figure out a way we can make roms or install roms onto these using our computers or the device itself?

xspartacusx: I don't have plans of doing that. If you need you have all sources and you can port my builds to cyanogenmod.

(02-01-2017, 05:41 AM)ayufan Wrote: [ -> ]xspartacusx: I don't have plans of doing that. If you need you have all sources and you can port my builds to cyanogenmod.

Linage OS is the new name for Cynogenmod.

(11-26-2016, 03:15 AM)ayufan Wrote: [ -> ]Based on my work for Android 7.0 (http://forum.pine64.org/showthread.php?tid=2136) I did downgrade to 6.0.

Download: https://github.com/ayufan-pine64/android-6.0/releases

It takes about 10 minutes for first boot to finish.

..............

When I try to connect using OpenVPN it gives me an error window: 
"Problem creating TUN interface - Possibly the tun.ko kernel module is not loaded in your Android kernel" 

logcat: 
02-02 09:38:40.676 30329 30329 I OpenVPNService: LOG: TUN Error: cannot acquire tun interface socket
02-02 09:38:40.677 30329 30329 I OpenVPNService: EVENT: TUN_IFACE_CREATE info='cannot acquire tun interface socket'


Is the above correct and is this not part of the kernel of this Android 6 release, and if so could this perhaps be added?

Cheers!

rookieone: it seems that it is added: https://github.com/ayufan-pine64/linux-3...nfig#L1084

Can you look at permissions of `/dev/tun`?

(02-02-2017, 04:51 AM)ayufan Wrote: [ -> ]rookieone: it seems that it is added: https://github.com/ayufan-pine64/linux-3...nfig#L1084

Can you look at permissions of `/dev/tun`?

root@tulip-chiphd:/ # ls -al /dev/tun
crw-rw---- system   vpn       10, 200 2017-02-01 20:31 tun
root@tulip-chiphd:/ #

Tried (not sure if this is a good idea ?-):

root@tulip-chiphd:/dev # chmod o+rw tun
root@tulip-chiphd:/dev # ls -al tun
crw-rw-rw- system   vpn       10, 200 2017-02-01 20:31 tun

(then still get the same errors as before, both in Android window, and logcat)

BTW, both "OpenVPN connect" and "OpenVPN for Android" apps cannot access tun.

I will check that later.

Hello,

I try to run android-6.0-pine-a64-tv-v1.1.3-r26.img, at first boot I only see a screen filled with red color. Wait more than 20 min and noting is changing..
I Burned the img with Etcher and also with Win32diskimager, Both did not work. I got an Samsung EVO Pro SD card 16gig.

Android 5 was running fine on my Pine64 A+2gb..

Hope you guys can help me,
Thanks

edit: I tried android-6.0-pine-a64-tv-v1.0.1-r20.img and its booting now, guess the pre-releases are not working yet?