Jump to content

Search the Community

Showing results for tags 'bananapim1'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support

Categories

  • Armbian
  • Armbian releases

Categories

  • Volunteering opportunities

Calendars

  • Community Calendar

Categories

  • Members

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. # PROBLEM: Recent bananapi m1 images (and other A20 boards?) have no kernel headers, and armbian-config is not working so no hardware support. # SOLUTION: Armbian_23.02.2_Bananapi_jammy_current_5.15.93.img.xz Take this image and install the headers manually - or update to recent ones from here (not all work). NOTE: Armbian_23.02.2_Bananapi_jammy_current_5.15.93_minimal.img.xz While is the same build, cannot unfreeze kernel changes in armbian-config gui Flash SD and drop the 3 kernel packages in /root/ After first boot run $ apt upgrade && apt upgrade --fix-missing Unfreeze kernel with $ armbian-config -> system -> unfreeze (should accept) Install kernel packages: $ dpkg -i <package-dtb.deb> <package-image.deb> <package-header.deb> reboot & freeze kernel again compare build scripts current vs minimal - and merge upstream? I am noob Please show the way. Files pack: https://www.dropbox.com/scl/fo/0bdengzqkn5x798ddxvp7/h?rlkey=i6kilnhhr6xzxgkmipfqy19pr&dl=0 credits: Note to self: I should learn how to compile and build images.
  2. Hello, I tied to activate SPI an a BananaPI M1 an Armbian VERSION=23.11.1 but didnt succeeded! I activated "spidev" at armbian-config and tried diferent configurations in "armbianEnv.tx. with: overlays=spi0 spi-spidev param_spidev_spi_bus=0 i get roland@bananapi:~$ dmesg | grep spi roland@bananapi:~$ lsmod | grep spi spidev 20480 0 roland@bananapi:~$ ls /dev/spidev* /dev/spidev0.0 roland@bananapi:~$ I installed "Rf24" library for an nrf24l01 module and tried "scanner" "gettingstarted" and my own c++ file. Al long as I define a wrong "CE" pin, I get response from the nrf24I01 modul. Mostly I get some senseless info, but I also get the module name. "nrf24l012". So there must be a connection. But I cannot use the correct CE pin. Everytime I define the correct CE gpio PIN, (nRF(22,0)) I get this error. terminate called after throwing an instance of 'GPIOException' what(): can't access /sys/class/gpio/gpio%d/direction GPIO pin. check access rights Abgebrochen " I have tried the nRF linrary an a RaspberryPi 3. There I have no problems. It worked out of the box. But because of 1Gb and SATA I need to use my BananaPi. I also have tried different modules. All worked on RaspberryPi and failed on BananaPi. Do you have any Idea, how I can get SPI to work?
  3. Hello, I just started to use my old BananaPi M1 (Armbian 23.8 Bookworm) to check sensor values by onewire and i2c. At last there was no problem with onewire But I cannot get I2c to work. /boot/armbianEnv.txt overlay_prefix=sun7i-a20 overlays=i2c2 w1-gpio param_w1_pin=PI3 For onewire I had to define "param_w1_pin=PI3" even if my onewire sensor is connected to GPIO7. for I2C I checked "lsmod | grep i2c" but couldnt find anything. So ieven if it is not correctly activated, I could run "i2cdetect -y 2" and could find my sensor at 0x76 but couldnt communicate with it. I think I need to load "i2c-bcm2708 i2c-dev". How can I get these to run? Or do I have to define the i2c_pins like I did with param_w1_pin ?
  4. Hey, im trying to install pihole on my very old banana pi bpi-m1 on an Armbian_22.11.0 OS (maybe that is the issue after all). im getting this error "Error: Unable to update package cache. Please try "sudo apt update" after that the installation wont continue. when i run sudo apt update it shows the following: Hit:1 http://ports.ubuntu.com jammy InRelease Hit:2 http://ports.ubuntu.com jammy-security InRelease Hit:3 http://ports.ubuntu.com jammy-updates InRelease Hit:4 http://ports.ubuntu.com jammy-backports InRelease Hit:5 http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu jammy InRelease Hit:6 http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Hit:7 https://itai-nelken.github.io/weekly-box86-debs/debian InRelease Hit:8 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:9 http://deb.volian.org/volian scar InRelease Get:10 https://cli.github.com/packages stable InRelease [3,917 B] Err:10 https://cli.github.com/packages stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 Hit:11 http://armbian.hosthatch.com/apt jammy InRelease Hit:12 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Reading package lists... Done W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 E: The repository 'http://cli.github.com/packages stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. When i do sudo apt-get update it gives me this: Hit:2 http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu jammy InRelease Hit:3 http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Hit:4 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:5 http://armbian.hosthatch.com/apt jammy InRelease Hit:6 http://ports.ubuntu.com jammy InRelease Hit:7 http://ports.ubuntu.com jammy-security InRelease Hit:8 http://ports.ubuntu.com jammy-updates InRelease Hit:9 http://ports.ubuntu.com jammy-backports InRelease Hit:11 https://itai-nelken.github.io/weekly-box86-debs/debian InRelease Hit:12 http://deb.volian.org/volian scar InRelease Get:1 https://cli.github.com/packages stable InRelease [3,917 B] Hit:10 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Err:1 https://cli.github.com/packages stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 Reading package lists... Done W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 E: The repository 'http://cli.github.com/packages stable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. after doing both of these updates it still won't work. does anyone have an idea? many thanks in advance
  5. Hello everyone I would like to set the monitor sleep time from the terminal. on Banana pi M1 with Armbian. You can help me ??
  6. Hi! I ended up here: My Banana M1 was working well, connecting to a monitor I was able to see it working. But after I removed the sd card (after turning the M1 off) and inserted into a Windows machine (it couldn't read the linux fs, did not format it) it won't start anymore. Tried with all the recommanded SD card software to test with the slowest method possible to detect errors on it, but no error on the sd card. Tried many times to write with the recommanded balena etcher the currently supported images on the sd card, like: Armbian_22.11.1_Bananapi_bullseye_current_5.15.80.img.xz Armbian_22.11.1_Bananapi_bullseye_current_5.15.80_minimal.img.xz Did check their checksums. I get a short red blink and the M1 is turned off. If the sd card is not loaded with a correct bootable image then the red light remains on but on the monitor in any case I see just the no signal message (tried with two different monitors). I doubt that it could have power issue as I use the AC Adapter IRN-050200U with the output of 5V 2000mA. Tried pressing keys while turning it on and off, still nothing appears on the monitor. Should I try anything more or is it ready to be thrown away? Any ideas what the heck could have happened?
  7. I know, using an old Banana Pi M1 for desktop doesn't make sense at all. I would prefer having help or/and advice clearing the problems I've encountered, instead a discussion why I'm testing a desktop environment on a BPi M1. Tested with Armbian 21.08.01 Buster / 5.10.60 After the initial boot nano or / and armbian-config doesn't work. A reboot solves this issue. After the second boot I changed verbosity to 7 and console to serial. All other changes where made throu armbian-config. Changing Pi's name works, but changing console's layout doesn't. Never mind, that is a minor problem, which can easily solved by hand. So I did "firmware upgrade" and rebooted my pi. dmesg: apt list lightdm lightdm/oldstable 1.26.0-4 armhf I proceed installing armbian desktop throu armbian-config. To ensure, that the installation will have all their dependencies installed, I quit armbian-config and reboot my pi. The armbianmonitor -u from this boot: http:// http://ix.io/3yvT This dmesg: Console-Output: systemctl status lightdm.service ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: Active: failed (Result: exit-code) since Sat 2021-09-11 01:45:59 CEST; 10min Docs: man:lightdm(1) Process: 593 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager Sep 11 01:45:59 deskpi systemd[1]: lightdm.service: Service RestartSec=100ms exp Sep 11 01:45:59 deskpi systemd[1]: lightdm.service: Scheduled restart job, resta Sep 11 01:45:59 deskpi systemd[1]: Stopped Light Display Manager. Sep 11 01:45:59 deskpi systemd[1]: lightdm.service: Start request repeated too q Sep 11 01:45:59 deskpi systemd[1]: lightdm.service: Failed with result 'exit-cod Sep 11 01:45:59 deskpi systemd[1]: Failed to start Light Display Manager. Sep 11 01:45:59 deskpi systemd[1]: lightdm.service: Triggering OnFailure= depend journalctl -xe -- Support: https://www.debian.org/support -- -- A start job for unit user@0.service has finished successfully. -- -- The job identifier is 810. Sep 11 01:46:32 deskpi systemd[1]: Started Session 2 of user root. -- Subject: A start job for unit session-2.scope has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit session-2.scope has finished successfully. -- -- The job identifier is 871. Sep 11 01:46:32 deskpi login[835]: ROOT LOGIN on '/dev/ttyS0' Sep 11 01:46:37 deskpi systemd[1]: systemd-hostnamed.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit systemd-hostnamed.service has successfully entered the 'dead' state. Sep 11 01:55:01 deskpi CRON[1345]: pam_unix(cron:session): session opened for us Sep 11 01:55:01 deskpi CRON[1346]: (root) CMD (command -v debian-sa1 > /dev/null Sep 11 01:55:01 deskpi CRON[1345]: pam_unix(cron:session): session closed for us On this point, I was couple of times before. I tried un- / re- install lightdm, which leaded me to missing kernel links. Installing an other display manager after installing armbian desktop via armbian-config will althrough bring errors and missing links for system.d. But at least armbian desktop does start. As a workaround having a desktop environment without having broken symblinks (but with a broken atomic namespace, whatever that means) I installed LXDE with LXDM. But this won't fix the problem with built-in lightdm. Thank you for your time reading my problems, i'll be deeply grateful for every hint fixing the broken lightdm.
  8. I have an OrangePi PC and a BananaPi M1, and both of them are able to switch to USB host mode or device mode by editing dr_mode in corresponding .dtb file. But seems that both board are not able to support HNP protocol. From my understanding, OrangePi PC and BananaPi M1 only has perpherial-only OTG, please correct me if I am wrong. Is there any board that can support HNP? I need something that can switch USB mode(from host mode to device mode or the other way around) without reboot the board Any advice is appreciated
  9. Hi, I have a Bananapi M1 running long Time with Debian Jessie. Now I installed Armbian Buster and always when I activate GPIO Pins my Network is gone on the integrated Card. Also GPIO is not working because of the Network Card. I tried to deactivate the Network Card and use an external WirelessLAN Card but the internal Card is still blocking my GPIO's. On Jessie and Wheezy before that was working perfect. Any advise? BR Peter
  10. Hello everybody! I upgraded my armbian on my Bananapi M1 to... armbian 20.08.17 Buster with Linux 5.8.16-sunxi Unfortunately I don't have any internet access anymore now. I can still SSH into the board, but I can not ping any server with it. What more information do you need to help? Thank you very much for your attention!
  11. I have a problem with my wireguard implementation. When connected through it I get lag spikes every few seconds. What might be the cause and solution to this? It is not the internet connection/cable/etc because a raspberry pi running wireguard works fine on the same exact cable, port etc.
  12. Ran the following command on my Banana PI to move to the HDD (SATA) nand-sata-install Install was a success: However I think some stuff went wrong during the transfer. Whenever I open a file in nano I get the following error: Error in /etc/nanorc on line 260: Error expanding /usr/share/nano/*.nanorc: Inappropriate ioctl for device I cannot run apt-get update anymore: pi@bananapi:~$ sudo apt-get update && sudo apt-get upgrade Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Hit:5 http://deb.debian.org/debian buster-backports InRelease Hit:4 https://armbian.tnahosting.net/apt buster InRelease Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. When I browse the directory with Winscp, I do not see the folder's it's looking for:
  13. Hello, i am new here and need the line in from MCU audio codec(U1-3 Pin AB20 & AB21), located wired on CSI connector(CON1 Pin 1 & 2), active. Is it possible? Regards Mario
  14. Rein

    net speed

    I have recently updated to Armbian Focal (Ubuntu 20.04). My Banana Pi M1 is running an apache server + some digital amateur radio stuff. So upload speed is important. My average download and upload speed as measured with speediest-cli is 45Mb/sec and 18Mb/sec respectively (wired connection to modem) With Focal I get these speeds with Buster (Debian 10) the download speed is still 45Mb/sec but the upload speed drops to 3.4 Mb/sec. These results are not one off but consistent. The am64 version of Buster does exactly the same thing.. My question is : can I change this with programming or is it a fixture in the kernel ? Can someone enlighten me please ? Rein
  15. Hi, Did anybody play with Cedrus on the recent kernels? I'm going to play with it on Bananapi m1, kernel 5.4 and Ubuntu Bionic. Should I just got step-by-step using this instructions http://linux-sunxi.org/Sunxi-Cedrus ? The goal is to evaluate whether this is suitable solution for video surveillnace. I'd used kerberosio with an IP camera for couple years and this does not work good with motion detection.
  16. Well, I have this old M1 lying around. I found use for it. However HDMI output seems to be broken and I have composite video USB dongle at my hand and it boots... but I can not do anything with it. The question becomes: How on earth can I make it "ssh login"-able from the first boot (preferably with mdns)? What should I do with the image? Auto configuration tools - as handy and nice those are - are not for this. Thanks.
  17. Hi, I am trying to use the SPI interface on the board GPIOs of a BananaPi M1+. I have started the latest version of Armbian available for this board (Armbian_19.11.6_Bananapi_bionic_current_5.4.8) and after the initial configuration the "/boot/armbianEnv.txt" file has the following added lines: fdtfile=sun7i-a20-bananapi-m1-plus.dtb overlays=spi-add-cs1 spi-spidev param_spidev_spi_bus=0 I have rebooted but I am unable to use the spidevX.Y under the "/dev" folder. What am I missing? NOTE: I have tried several combinations of values on the armbianEnv.txt configuration file (ie: using only overlays flags without the other ones, using only the spi-spidev flag, etc...), none succeeded.
  18. So I've installed and I'm running watchdog for some months now on BananaPi M1. I think it reboots the board when the default gateway has some issues. And that's fine, no problem with that. The board works 24/7 and it made 14+ days uptime without problems. But things have changed and the board reboots at least few times a day (seems I have a problem with armbianmonitor -u - the board rebooted twice before it ended). And here's the problem. watchdog doesnt log anything or I'm unable to find any usefull info. And watchdog.conf: (it seems that the board went offline - maybe internet connection issues, but I have another one running that's also "logless" and they have almost the same config except for the gateway IP) ping = 192.168.1.1 #ping = 172.26.1.255 interface = eth0 #file = /var/log/messages #change = 1407 # Uncomment to enable test. Setting one of these values to '0' disables it. # These values will hopefully never reboot your machine during normal use # (if your machine is really hung, the loadavg will go much higher than 25) max-load-1 = 24 max-load-5 = 18 max-load-15 = 12 # Note that this is the number of pages! # To get the real size, check how large the pagesize is on your machine. #min-memory = 1 #allocatable-memory = 1 #repair-binary = /usr/sbin/repair #repair-timeout = 60 #test-binary = #test-timeout = 60 # The retry-timeout and repair limit are used to handle errors in a more robust # manner. Errors must persist for longer than retry-timeout to action a repair # or reboot, and if repair-maximum attempts are made without the test passing a # reboot is initiated anyway. #retry-timeout = 60 #repair-maximum = 1 watchdog-device = /dev/watchdog # Defaults compiled into the binary temperature-sensor = /sys/class/thermal/thermal_zone0/temp max-temperature = 80 # Defaults compiled into the binary #admin = root interval = 10 logtick = 60 log-dir = /var/log/watchdog # This greatly decreases the chance that watchdog won't be scheduled before # your machine is really loaded realtime = yes priority = 1 # Check if rsyslogd is still running by enabling the following line #pidfile = /var/run/rsyslogd.pid
  19. Hi All, Just wanted to share a good story using armbian. I have used in the past 1-wire probes for temperature, and the process included decompiling, editing and recompiling dtb for my Banana Pi M1, which was not easy at all. Every firmware update deleted by changes and had to redo de recompilation. With latest kernels and armbian version, the process is now extremely easy, just edit: /boot/armbianEnv.txt Adding this lines: overlays=w1-gpio param_w1_pin=PI3 # desired pin(7th pin (GCLK) or number 4 on first column where number 1 is +3V) param_w1_pin_int_pullup=1 # internal pullup-resistor: 1=on, 0=off I just struggled a little bit to find the GPIO code (decompiled dtb and checked possible candidates). Information about temperature is here: cat /sys/bus/w1/devices/XX-YYYYYYY[this is your probe serial, if you have more they will be in /sys/bus/w1/devices/] /w1_slave You have plenty of information here, but don't need to do all they explain, just my edition has been enough: http://linux-sunxi.org/1-Wire
  20. Hello everyone, I am encountering problem with pulseaudio on Bananapi M1. I don't want the board to suspend speakers on idle. As Pulseaudio is used I simply commented this line: ``` ### Automatically suspend sinks/sources that become idle for too long #load-module module-suspend-on-idle `` in `/etc/pulse/default.pa`. The problem is that if I play something e.g. raspotify I dont hear the sound anymore. As soon I keep raspotify playing and restart Pulseaudio (killall pulseaudio) the sound is back again. If I pause music I lose sound again and need to kill pulseaudio. Does anybody encounter same thing?
  21. I have a local OpenVPN server on Banan Pi M1, with latest armbian. I tried to replace with OrangePi3 but current results is disappointing iperf3 results on Banana Pi M1 OpenVPN server Connecting to host bouygues.iperf.fr, port 5201 [ 4] local 10.8.0.4 port 46250 connected to 89.84.1.222 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 1.69 MBytes 14.1 Mbits/sec [ 4] 1.00-2.00 sec 1.81 MBytes 15.1 Mbits/sec [ 4] 2.00-3.00 sec 2.43 MBytes 20.4 Mbits/sec [ 4] 3.00-4.00 sec 681 KBytes 5.58 Mbits/sec [ 4] 4.00-5.00 sec 1.99 MBytes 16.7 Mbits/sec [ 4] 5.00-6.00 sec 1.33 MBytes 11.2 Mbits/sec [ 4] 6.00-7.00 sec 1.55 MBytes 13.0 Mbits/sec [ 4] 7.00-8.00 sec 1.62 MBytes 13.6 Mbits/sec [ 4] 8.00-9.00 sec 1.33 MBytes 11.2 Mbits/sec [ 4] 9.00-10.00 sec 1.76 MBytes 14.8 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 16.2 MBytes 13.6 Mbits/sec sender [ 4] 0.00-10.00 sec 15.7 MBytes 13.2 Mbits/sec receiver iperf3 results on Orange Pi 3 OpenVPN server Connecting to host bouygues.iperf.fr, port 5201 [ 4] local 10.8.1.4 port 41583 connected to 89.84.1.222 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 621 KBytes 5.09 Mbits/sec [ 4] 1.00-2.00 sec 868 KBytes 7.11 Mbits/sec [ 4] 2.00-3.00 sec 1.18 MBytes 9.89 Mbits/sec [ 4] 3.00-4.00 sec 1.16 MBytes 9.75 Mbits/sec [ 4] 4.00-5.00 sec 1.02 MBytes 8.53 Mbits/sec [ 4] 5.00-6.00 sec 966 KBytes 7.92 Mbits/sec [ 4] 6.00-7.00 sec 726 KBytes 5.95 Mbits/sec [ 4] 7.00-8.00 sec 676 KBytes 5.54 Mbits/sec [ 4] 8.00-9.00 sec 2.58 MBytes 21.7 Mbits/sec [ 4] 9.00-10.00 sec 4.78 MBytes 40.1 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 14.5 MBytes 12.2 Mbits/sec sender [ 4] 0.00-10.00 sec 14.0 MBytes 11.7 Mbits/sec receiver As you can see, connection via OPi3 is slower, but more than that, it is unstabe and fluctuating from 5-8 MBit/s to 40 MBit/s What can I tune to improve openvpn connectivity?
  22. i wanted to use my Banana Pi M1 for displaying multimedia content from websites like twitch.tv but firefox-esr and chromium crash when I try to load them. firefox opens its crash report box without a possibility to look at the related error messages. But the output of chromium can be viewed here: http://dpaste.com/37M0QNC It was installed from Armbian_5.65_Bananapi_Debian_stretch_next_4.14.78.img plus dist-upgrades. Iinitius
  23. Guys, purchased shortly my first Bananapi M1. I installed without problems Armbian to a SD Card and now in second step i would like to connect a 1TB Western Digital 2,5" SATA HDD. But which connection cable do i have to use with the Banana Pi? Can someone please post a link url if allowed or let me know? Thanks in advance!
  24. please enable green led Banana-pi M1 Armbian 5.75
  25. Hi, I did a dist-upgrade on my BPi M1. Now it is running on ARMBIAN 5.73 stable Debian GNU/Linux 9 (stretch) 4.7.3-sunxi When I choose a newer kernel in armbian-config after the reboot it is still running with the old kernel. When I do an apt-get upgrade it shows this error in the output: update-initramfs: failed for /boot/initrd.img-4.20.7-sunxi with 1 The BPi is booting from SSD with LVM. Thank you very much for any help. Regards, Robert
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines