I know that there are a bunch of topics about this issue in and out stackoverflow, and I have tried to edit the config.txt as much as I could, never getting different results. (BTW: I got it working with Raspian really easily editing the config.txt, but it does not work for android for some reason).
You can of course change the resolution using xrandr, but you first have to convince xrandr that it should let you. ;-)To do that, you need to generate the appropriate "mode" settings.The easiest way to do that is by using the "cvt" command.
Armed with all of that info, you can set the resolution as follows, by pasting the string from after "Modeline" in the cvt output.Here I took the liberty of simplifying the "1280x1024_60.00" to just "1280x1024_60" and then used that consistently:
So I finally got it working by trial and error. I used a different Android image that had the vc4-fkms-v3d overlay instead of the vc4-kms-v3d commonly used in the other Android images I tried before. That seemed to do the trick for me.
I read that the vc4-fkms-v3d overlay is still a bit experimental, so I do not know if there will be any limitations using it. And I would still appreciate if someone has any input on this, but for now the case is closed.
I am working on a project where I need to transfer data between android and raspberry pi via Bluetooth. However, I am new to this and I don't have deep understanding on what happens when two devices are paired. Based on assumption that the two devices of interest are already paired, where would the starting point be for programming for such task? I've been reading on BluetoothSocket, but I am still unsure of where to start. Can anyone help me please?
I have been looking into this same issue, here is the reading I found on my end. I was looking to specifically code in python so that's the angle of the first one, the second is C++, but has a really thorough intro.
The specific parts to look at involve the planning aspect. The intro of the beej programming guide shows specifically what sockets are and how they fit in a network sense. This means streaming sockets and datagram sockets. It also shows which of the sockets are used and which are availible. Chapters 1 through 3 gave me a solid enough reading basis to use the second document to determine a few things.
Chapter 2 of the MIT document goes into specific detail about each of the steps that must occur at a structural level including L2CAP + UDT, RCOMM, and whatever the stream one was. From reading these I was able to determine that the network I wanted to use was an L2CAP. I hope these help point you in the right direction though as far as what network you want to setup and what language you want to program in.
I've been working on the same task little while ago. The point is, that in order to start sending and receiving data you have to establish connection first. There is two side- device which connects (creates socket) and the other receiving connection (bluetooth server socket), giving out connection once connection is complete. After connection is established, you should stop receiving incoming connection or attempting establishing any connections.From implementation perspective, you should implement few threads for managing all those stages - connection thread, accept thread, communucation thread. There is a great example from Google: -BluetoothChat . It uses that technic. The only drawback is that it uses Handler (Android feature, allowing thereads to communicate) for informing user about Bluetooth events. I modified it a bit by introducing another thread, receiving status updates and calling methods from callback interface, feel free to use code from project:
Hi, I did this process, and it works perfectly! I just have 1 quick question, would you be so kind as to give me an explanation of how to set up a 3.5 in. touchscreen with this?
It would be greatly appreciated!
Hi, so I was installing lineage OS 14.1 (android 7.1) in my raspberry pi 3B. Android 7.1 runs much faster than android 10 on this model. I got lineage OS running fine on it but when I got into recovery mode to install Gapps, it would not leave recovery mode. The Gapps installation seemed to have gone smoothly, but now every time I hit reboot it just boots back into recovery! Do you have any fixes?
Hi Emmett, a small improvement suggestion. I noticed i have only limited space available on my 64GB SD-card. Something like 5GB is free. I guess some space on the SD-card is not accessible. Can you include some hints how to add the unused space. Many thanks, Jac
You may have to try downloading the Android build we are currently linked to. I briefly updated it to Android 11 but there is a few things I need to sort out still, so it has been changed back to Android 10.
HI, I am new to this and I currently trying to get my app inventor and raspberry pi to connect. In my project I am using App inventor to simulate a open and closing while on the raspberry pi 3 I have a relay and 2 led to show open and closing.
@Juan_Antonio That link looks awesome!
I've built a robot containing a Raspberry Pi Zero W. Currently, the only way to control it is from my Raspberry Pi 2 luggable, which communicates with the Zero via Wi-Fi (no router). It'd be nice if I could control the robot from my Android smartphone, which is a lot smaller! (Plus I always have my phone with me.)
Then you can use the web component in App inventor. Set the url to the ip address of your raspberry pi followed by :1880/mit. (e.g. :1880/mit) You can use the PostText method. I use this to switch a light on and off by sending a MQTT message to Domoticz using the MQTT node in Node-RED.
@Juan_Antonio I can't get that Circuit Digest example to work (even after I added () to the prints so the codes is Python 3). The Pi code has never got past server_socket.accept() despite much mucking about on my Android phone. (The Bluetooth terminal program mentioned by Circuit Digest doesn't seem to work on my phone; at least, I haven't found any way of telling it which Bluetooth device to connect to. I've tried a couple of other Bluetooth terminal programs, but they can't connect to my Pi.)
I've got an App Inventor app which happily displays a list of paired devices using
blocks115852 12.7 KB
If I tap on "B8:27:EB:14:9D:19 RPi0W" (which is the Pi running the Circuit Digest Python code), my code does
blocks908102 13.6 KB
which pops up an error message (which disappears frustratingly quickly) that says "Error 507: Unable to connect. Is the device turned on?" (It is, and waiting for a connection.)
@Juan_Antonio How strange! My phone's running Android 10 (and my Pi 0W is running Buster).
I might look (elsewhere) for code for 2 Raspberries to communicate by Bluetooth. (Or maybe I can get my phone to talk to my Pi via Wi-Fi.) What software were you running on your Pi? The Python code on the Code Digest page outputs thus:
Initially, I got "Failed to connect to SDP server on FF:FF:FF:00:00:00: No such file or directory".
Then I tried the instructions in raspbian - Failed to connect to SDP server on FF:FF:FF:00:00:00: No such file or directory - Raspberry Pi Stack Exchange
Then sdptool gave the 189(!) lines I've attached. My minimal App Inventor app still won't connect to the Python code. Nor will Bluetooth Terminal or Serial Bluetooth Terminal from Google Play. I guess this is unsurprising, since a comment on that StackExchange page says "This fix stopped working on 2021-01-11-raspios-buster-armhf.img"
sdptool.txt (4.3 KB)
Hello guys, Welcome to Being Engineers. Some times back I have posted a tutorial here in the Instructables on the topic of casting raspberry pi monitor, most specifically Raspbian OS screen to android mobile, as well as there we were able to control the pi from the mobile itself. It got quite some views and recently some people were facing problems completing the steps. The process is quite orthodox and takes a lot of time to connect each time. So I decided to put up a new tutorial which will be much easier to execute and more convenient on the go. In this method, you only need a power bank to connect to the Pi each time you want it to be. That means you can cast pi screen to your mobile anytime anywhere. No need of internet, no router, no monitor, just a power bank. But this method will only work with newer Raspberry Pi because they have the Wi-Fi chip build in and we will be using the WI-Fi only. But you can use older versions of Pi with the help of WiFi dongle.
Go to your network adapter settings. Then Open the properties of the network adapter. Open the second tab and you will find a check box that can enable the sharing feature from your laptop to the raspberry pi.
Now you have to use some IP Scanner software to know the IP address of your raspberry pi that is connected with the Laptop or PC. I am using the software named Advanced IP Scanner. It is very easy to use. Just put in the possible minimum and maximum range of IP address and it will find out the active devices with corresponding IP address.
First of all connect an ethernet cable to the RJ-45 jack in the raspberry pi. Connect the other side to the laptop or PC. Put in the SD card in which Raspbian is installed. Then power up the Pi with a 5V 2A micro usb power adapter.
From the list find the network with the name of your hotspot name. It has to be there. If the name is not in the list then reboot the Pi and try again. You will find that eventually. it's time to type in the SSID and PSK which are the hotspot name and the hotspot password respectively.
Type in the command " sudo nano/etc/wpa_supplicant/wpa_supplicant.conf ". It will open a file named wpa_supplicant.conf which is a configuration file for wlan. Copy the following two lines and paste it there.
Type in the command " sudo apt-get install tightvncserver " and press enter to start the installation. It will take some minute depending upon your internet speed. When the installation is done then shutdown the pi.
d3342ee215