+- 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 6.0 Tablet and TV (release candidate, maintained) (/showthread.php?tid=2861)
RE: Android 6.0 Tablet and TV (release candidate, maintained) - jonsmirl - 11-30-2016
(11-30-2016, 07:57 AM)ayufan Wrote: So, basically these tools require specially created images, in special format, with special headers. I don't think that this is possible the `dd` images then. I basically had very bad experience with these tools.
I believe that even today, you can prepare SD image that will basically install (dd) system to nand. It seems easier and more user friendly.
Allwinner wrote those tools and they work on all of their chips. They know the various bugs in the boot ROMs with FEL mode. I am also not in agreement with their approach, but these tools have been around since the A10 and they work everywhere.
Pine has not been exposed to this world since it lacks a eMMC chip on board. I consider not having a eMMC chip a major flaw in Pine since eMMC is far faster and way more reliable than SD Card. Pine also has a big flaw in not having working OTG for FEL mode.
I am shifting development onto the BananaPi M64 board which does not have Pine's flaws.
http://www.banana-pi.org/m64.html
The Bpi boards are similar but not exact clones. It is a minor amount of work to port BananaPi M64 Android back to Pine. So far the only difference I have discovered other than the addition of more hardware is that wifi is on DLDO3 instead of DLDo4 (Pine).
BTW - NAND is a complete mess on Allwinner, avoid it if possible. That was another major reason for the Allwinner tools, they can use the various NAND controllers to write the NAND.
RE: Android 6.0 Tablet and TV (release candidate, maintained) - ayufan - 11-30-2016
Quote:Allwinner wrote those tools and they work on all of their chips. They know the various bugs in the boot ROMs with FEL mode. I am also not in agreement with their approach, but these tools have been around since the A10 and they work everywhere.
It seems to be problem of u-boot, and something that can be fixed for specific board with a kernel. I'm not saying that you should not use it, I had very bad experience that's all. Doing custom images I had a hell a lot of less problems and make them more reproducible then using their broken tooling.
RE: Android 6.0 Tablet and TV (release candidate, maintained) - tommypine - 11-30-2016
I can't access Videos located on a USB-Stick with Kodi. The Stick dosen't show up. With ES File Explorer i can access them.
If i click on them in ES then i can play them in Kodi, but i can't add it as video source. Any help?
RE: Android 6.0 Tablet and TV (release candidate, maintained) - chavaone - 12-01-2016
Hi! Thanks for this awesome image!
)Where do you download the Netflix APK for this image? I have downloaded version 3.3.1 from APKMirror but when launch the app it throws an error telling me the device is not supported :/
RE: Android 6.0 Tablet and TV (release candidate, maintained) - ayufan - 12-01-2016
Try regular Netflix app, not the TV version.
RE: Android 6.0 Tablet and TV (release candidate, maintained) - Gastenpa34an - 12-01-2016
Hi! Nice work!
It works well, however I have one problem. When using an app such as Spotify or Dplay to watch some swedish TV channels I'm not able to control the volume. I can only get 100% or 0% ... any ideas how to solve this problem? I'm using the airmouse sold by Pine64 and with 5.1 it works fine.
/Niklas
RE: Android 6.0 Tablet and TV (release candidate, maintained) - ayufan - 12-01-2016
Does IR remote work?
RE: Android 6.0 Tablet and TV (release candidate, maintained) - Gastenpa34an - 12-01-2016
I don't have any IR. But even when I try to control the volume from settings I only get all or nothing...
RE: Android 6.0 Tablet and TV (release candidate, maintained) - yantoz - 12-01-2016
Hi Ayufan, this build works really nice!
Everything seems to be working really well but the android TV remote service. It crashed when a client tries to connect to it for missiing library.
12-02 06:00:27.894 D/WifiService(2747): acquireWifiLockLocked: WifiLock{RemoteServiceLock type=1 binder=android.os.BinderProxy@22c56c7}
12-02 06:00:27.894 I/ATVRemote.Server(5659): Communication starting with XXX.XXX.XXX.XXX
12-02 06:00:27.922 D/AndroidRuntime(5659): Shutting down VM
--------- beginning of crash
12-02 06:00:27.923 E/AndroidRuntime(5659): FATAL EXCEPTION: main
12-02 06:00:27.923 E/AndroidRuntime(5659): Process: com.google.android.remote.tv.services, PID: 5659
12-02 06:00:27.923 E/AndroidRuntime(5659): java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/priv-app/AtvRemoteService/AtvRemoteService.apk"],nativeLibraryDirectories=[/system/priv-app/AtvRemoteService/lib/arm64, /system/priv-app/AtvRemoteService/AtvRemoteService.apk!/lib/armeabi-v7a, /vendor/lib, /system/lib]]] couldn't find "libatv_uinputbridge.so"
12-02 06:00:27.923 E/AndroidRuntime(5659): at java.lang.Runtime.loadLibrary(Runtime.java:367)
12-02 06:00:27.923 E/AndroidRuntime(5659): at java.lang.System.loadLibrary(System.java:1076)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.UinputBridge.<clinit>(UinputBridge.java:41)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService.openInputBridge(RemoteService.java:669)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService.handleConfigure(RemoteService.java:843)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService.access$3100(RemoteService.java:55)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService$12.configure(RemoteService.java:1084)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService$12.configure(RemoteService.java:1080)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.ServerPacketParser.parseConfigure(ServerPacketParser.java:167)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.ServerPacketParser.parse(ServerPacketParser.java:106)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.RemoteService$11.onMessage(RemoteService.java:1058)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.google.android.tv.remote.TcpServer$Connection$5.run(TcpServer.java:287)
12-02 06:00:27.923 E/AndroidRuntime(5659): at android.os.Handler.handleCallback(Handler.java:739)
12-02 06:00:27.923 E/AndroidRuntime(5659): at android.os.Handler.dispatchMessage(Handler.java:95)
12-02 06:00:27.923 E/AndroidRuntime(5659): at android.os.Looper.loop(Looper.java:148)
12-02 06:00:27.923 E/AndroidRuntime(5659): at android.app.ActivityThread.main(ActivityThread.java:5417)
12-02 06:00:27.923 E/AndroidRuntime(5659): at java.lang.reflect.Method.invoke(Native Method)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
12-02 06:00:27.923 E/AndroidRuntime(5659): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-02 06:00:27.956 E/bt_h5 (11678): h5_timeout_handler
12-02 06:00:27.956 E/bt_h5 (11678): Wait H5 Sync Resp timeout, 12 times
RE: Android 6.0 Tablet and TV (release candidate, maintained) - chavaone - 12-01-2016
(12-01-2016, 10:27 AM)ayufan Wrote: Try regular Netflix app, not the TV version.
yep!
That works! In addition if I have both apps installed android tv version sometimes seem to work or at least it doesnt throw the error.I have some issue with Android TV Remote. The Android TV service stops every time I want to run it
When I have some time I'm gonna report the bug with the dmesg output and so.