Hi all,


I have query regarding permissions for external drive on android TV and android 7.1 


Android TV 7.1 Community Build Image [microSD Boot] by ayufan
and 
Android 7.1.2 Stock Image [microSD Boot] [Rooted] [20171204]

In both cases external drive (2T ntfs partition) is mounted as read only Is there any possible to change that situation. I know that second release is rooted but I've tried use root account and change permission and owner with chmod and chown but without result.

 Or maybe I should you some other release? 

Thanks in advance. 

I've been talking with Quectel's  engineers about the possibility of swapping the EC25-G module with the EC25-AF that has all the bands for US 4G+ LTE on AT&T and T-Mobile and their related MVNOs.

They tell me that electrically, it's possible - the modules are compatible, and the antennas would likely not need to be changed. However, getting the EC-25-G module off the board would be difficult. It requires unsoldering the pins and heating the module to soften the solder underneath. The module will not survive the disassembly. But cleaning the pads and putting the EC25-AF should be straight forward. The module has it's software and IMEI and serial# loaded to the module but would require registering it if it hasn't been done already (I have a registered module sitting on my desk).

Before I consider risking doing this,  I'd like to know the possibility of Pine doing a batch of PinePhones for the North American market next year. How hard would it be to portion a subset of the next batch with the EC25-AF  module?

What is the proper method to apply list formatting (numbered or bulleted) to a post? I have used both the formatting buttons and MyCode. In each case I see the list in the editing window, but when previewed or posted, the lists do not show.

Curious

Hi all,

We'll be including a 'welcome' letter - or perhaps more accurately a 'getting started' letter - with future Pinebook Pro shipments. Here are the contents, let me know if I missed something:

Quote:Dear Piner,

Congratulations on your new Pinebook Pro! The Pinebook Pro has been created in conjunction with our community of developers and end-users like yourself. 

Our community maintains a well documented Wiki found on wiki.pine64.org. The Pinebook Pro Wiki section includes information about troubleshooting, available OSs, hardware disassembly, NVMe installation and compatibility, activation of privacy switches, the PCB layout as well as many other aspects of your device. Make sure to consult it regularly and contribute to it in any way you see fit. 

Anyone with a PINE64 forum account (forums.pine64.org) can contribute to the Wiki.      

Here are a few things to get you started: 
To power on your Pinebook Pro long-press the power button. On initial boot you’ll see a custom Debian PINE64 splash screen, after which the Pinebook Pro will reboot itself. This only occurs upon initial startup. We suggest that you do not plug in any external USB peripherals (USB-C docks, SSD/HDDs, mice, etc.,) on the first boot. Once the Pinebook Pro power cycles, you’ll be greeted with a LightDM login screen. 

The default operating system is Debian with a stylized MATE desktop 
The default login credentials are: rock / rock 

You can find out more information about the default Debian build on our forums - the thread is found in the Pinebook Pro section -> General Discussion on the Pinebook Pro -> Default OS update log. 

This thread also provides information on how to update the installation to newest version, change your username and home directory name, and lists all known bugs and improvements made to the system over time. 

Here is where you get help:
You are welcome to share your experience and ask any questions you may have on our forums and in the PINE64 community chats. The default OS comes with HexChat (IRC client) preinstalled that connects directly to our IRC server. Other chat options are also available and accessible via Forums and Chats drop-down on our main page (pine64.org). 

Have fun!

Subject: looking for Linux decoder/encoder API in H6 as well as any transcoding example


Dear community,

Please allow me to ask a very basic question here. 

Can anyone help me where to find decoder/encoder Linux API's in H6 as well as any transcoding exemplary code by using those API's?


Justin

Curious if anyone has done anything of significance with Node Red on the Pine. I've seen one post detailing the install, but otherwise, not a lot of discussion.

I just got messing around with Node Red this weekend, using a Raspberry Pi, and it got me thinking about these Pine boards sitting here not really doing much. The tool can do some pretty cool stuff, I'm sure I could come up with something useful for the Pine to be doing via Node Red.

The Pi has some nodes created for it, so its easy to control gpio, but not sure I've seen any mention of the same thing being done for the Pine. And, not being a node.js guru, not sure just how complex it would be to create some for the Pine.

Anyone? Any expert insight is appreciated.

I'm curious (yes, I know I could make another SD , and I just might) if anyone using the Debian or Ubuntu builds has tried out Anbox-arm64 yet?

I tried messing with some pkgbuilds in Manjaro to get the correct android.img to download, but hit an error, closed it out, and promptly forgot what happened. :/
I have snapd installed, but the wifi just crapped out (connected, but with ? in the icon for each connect I try.) If I have time tonight, I'm going to try to install the snap. I figured I'd reach out here and see if anyone got this idea in their head and whether the succeeded or failed, and potentially why.

HDMI doesn't work with any Kernel except the Kernel 4.4 from Rockchip (it also doesn't work with xorg) i tried out all kernel configs from rockchip and ayufan always same error:
[    4.030085] printk: console [ttyS2] enabled
[    4.031672] rockchip-vop ff370000.vop: Adding to iommu group 1
[    4.038101] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffffc0108c27d8)
[    4.038924] rockchip-drm display-subsystem: failed to bind ff3c0000.hdmi (ops 0xffffffc0108c5f30): -517
[    4.040292] rockchip-drm display-subsystem: master bind failed: -517

With Kernel 4.4 from Rockchip (ayufan) HDMI works:
[    3.167892] [drm] Initialized drm 1.1.0 20060810
[    3.173651] [drm] Rockchip DRM driver version: v1.0.1
[    3.174380] rockchip-drm display-subsystem: devfreq is not set
[    3.175647] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffff8008d86950)
[    3.176798] i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports
[    3.177487] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.178358] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[    3.180400] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops 0xffffff8008d7afa8)
[    3.181186] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.181851] [drm] No driver support for vblank timestamp query.
[    3.182495] rockchip-drm display-subsystem: failed to parse display resources
[    3.402118] rockchip-vop ff370000.vop: [drm:vop_crtc_enable] Update mode to 1280x1024p60, type: 11
[    3.469911] Console: switching to colour frame buffer device 160x64
[    3.503468] rockchip-drm display-subsystem: fb0:  frame buffer device

Xorg-log:
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.14.89-0-vanilla aarch64 Alpine Linux
Current Operating System: Linux localhost 5.4.2 #1 SMP Thu Dec 12 03:04:42 CET 2019 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.2 modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-5.4.2 extra_latent_entropy1
Build Date: 31 May 2019  06:21:31AM
 
Current version of pixman: 0.38.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 21 10:28:08 2016
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
MESA-LOADER: failed to open rockchip (search paths /usr/lib/xorg/modules/dri)
failed to load driver: rockchip
MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/xorg/modules/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /usr/lib/xorg/modules/dri)
failed to load swrast driver
couldn't get display device
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
(EE) /usr/share/libinput: failed to find data files
(EE) Failed to load the device quirks from /usr/share/libinput and /etc/libinput/local-overrides.quirks. This will negatively affect device b.
/usr/bin/startxfce4: X server already running on display :0
<stdin>:0: warning: Unknown encoding: C.UTF-8
    xfce4-session: No GPG agent found
xfce4-session: No SSH authentication agent found

(xfce4-session:2231): xfce4-session-WARNING **: 10:28:10.365: xfsm_manager_load_session: Something wrong with /home/admin/.cache/sessions/xfc?

(xfwm4:2278): GLib-CRITICAL **: 10:28:19.096: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-CRITICAL **: 10:28:20.459: g_str_has_prefix: assertion 'prefix != NULL' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.721: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed

(xfsettingsd:2284): GLib-GObject-CRITICAL **: 10:28:20.800: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed
Error relocating /usr/bin/Thunar: pango_attr_insert_hyphens_new: symbol not found
xfsettingsd: No window manager registered on screen 0.
xfce4-panel: No window manager registered on screen 0. To start the panel without this check, run with --disable-wm-check.
No window manager registered on screen 0. To start the xfdesktop without this check, run with --disable-wm-check.
xfce4-panel-Message: 10:28:33.334: Plugin "statusnotifier-7" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.338: Plugin "pulseaudio-8" was not found and has been removed from the configuration
xfce4-panel-Message: 10:28:33.377: Plugin "notification-plugin-10" was not found and has been removed from the configuration

** (wrapper-2.0:2315): WARNING **: 10:28:36.247: No outputs have backlight property

(wrapper-2.0:2315): xfce4-power-manager-plugin-WARNING **: 10:28:36.920: Xfce4-power-manager: The panel plugin is present, so the tray icon g.

(wrapper-2.0:2315): Gtk-WARNING **: 10:28:37.092: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button,)

(xfdesktop:2311): GLib-GObject-CRITICAL **: 10:28:46.065: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
^Cxinit: connection to X server lost

waiting for X server to shut down ^VGdk-Message: 10:28:59.978: xfdesktop: Fatal IO error 38 (Function not implemented) on X server :0.

Gdk-Message: 10:28:59.978: xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


I boot with extlinux.conf: The kernel starts only without console bootparameter: When i insert console=tty0 as boot paramter the kernel dont start.

Does anyone know what the problem could be.
Thank you in advance for your help

Good points, I think (I'm not going to cancel my Brave Heart order, though)

Hi folks.  I'll tell yoos about my experience and goals for my Rock64 1GB.

First I installed Archlinux ARM per their wiki.   15 mins I was up and ssh'ed in.    SSH freezes. gah   off to googling.
Not a happy start.  Saw a thread here on it that has no solution.   Found out to install ethtool and turn off TX.   Fixed I hope.

I then setup a sdcard to flash my SPI with ayufan's tool.    Installed Arch to a 2.5" hdd and hey  it booted from usb3....but it freezes.
Moved usb cable to usb2 port...seems ok.   Need answers on this usb3 issue.   I've read it's a problem.   I use sdcard for now.

Here's where I'm working now:   Installed X on both Manjaro and Arch arm.  Only fbdev works which I hear is about all most want or try to get working.   I want gles2 for qt5-gles so I can install and run KDE Plasma DE on both X and wayland.

Problems:  I've tried to install and build from source mesa-git mesa-arm-git  and they won't even build.   I suppose I dont have the chops yet to get a aarch64 toolchain installed correctly on the r64.  I see pkgs in the arm repo's but no how-to's on the net yet.


So if anyone has the above DE working with hardware accelerated gpu for the Mali-450 I'd like to work with you or hear your steps.   It involves  getting these parts all working.    mainline 5.4.x kernel options right for this board/gpu  that being lima driver and lima drm.    X pkgs like libdrm  mesa-20-git etc and then qt5 built for gles.   gles=OpenGL-ES  I think.

So far I'm not very impressed but I'm willing to work the bugs out of this board and dev the gpu some because it's cheap and powerful but a challenge.     If I wanted plug and play kde I'd have bought a pricier board.   

Cheers, tomarm