I find Jos Ryke's Beacon Cheat Sheet that he posted on Twitter very helpful to understand what is going on:
As you will see there is only a maximum of 18 bytes for the URL. Even with the bit of encoding they do in the Eddystone format, it is still not a very long url. A common way to get around this is to ...
It seems that that one of hundred tutorials you used is somewhat outdated. You should use the tutorial given on the official Raspberry Pi site: Setting up a Raspberry Pi as a routed wireless access point, as already suggested by @Andyroo in his answer.
If you have problems with hostapd or need a some more sophisticated setup, you may have a look at Setting ...
This question is pretty old, But even now I had come across similar issue:
I will detail you how I was able to fix this for current version of raspbian 10.
(i) Install Pulse audio tool
sudo apt-get install pulseaudio pulseaudio-module-bluetooth
(ii) Start Pulse audio
(iii) Now turn on your bluetooth speaker , and make it discoverable, ...
Is it because the OS itself is compiled for ARMv6?
The same reason the OS is compiled for ARMv6: Because it is intended for use on all models, including the ARMv6 Zeros, etc.
There is probably not much point in using an ARMv7 compiler on an ARMv6 system regardless of the underlying hardware. The system libraries and kernel are ARMv6.
Don't use NOOBS to install Raspberry Pi OS It's one more thing to worry about when you're troubleshooting an installation. Just use the Raspberry Pi Imager or something like Etcher. For Encrypting the OS the Offical Raspberry Pi forum has a post with instructions on how to do this. The OP used LUKS and created a script you could use.
Starting a service with rc.local has a number of problems:
If something you run in rc.local gets stuck, then your system will hang during boot
By default, things run from rc.local can’t output anywhere; so you can’t see any errors or other output
There’s no “lifetime management”. rc.local runs once and once only.
If you want to run it again, you have to ...
I expect this answer to be downvoted but here goes.
Stop following old articles that are based on old operating systems. Stretch was replaced by Buster well over a year ago.
Follow the new instructions [here] (As of Sept 2020).
Core steps I take BEFORE setting this up:
Download a new LITE version of the OS
Check SHA matches
Burn with Etcher and verify ...
Any Raspberry Pi operating system will boot on all Raspberry Pis released at or before the OS. So it should not be a problem to boot the Raspberry Pi OS (32-bit) on a RPi3B and a RPi4. The image contains different kernel and firmware to make this possible:
rpi ~$ ls -1 /boot/kernel*