Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: benpocalypse
10 hours ago
» Replies: 12
» Views: 5,654
|
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: anoduck
Yesterday, 03:14 PM
» Replies: 5
» Views: 8,685
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: biketool
09-21-2025, 02:03 PM
» Replies: 71
» Views: 32,666
|
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: j_s
09-19-2025, 04:04 PM
» Replies: 3
» Views: 10,313
|
Wifi 5Ghz Issue
Forum: PineNote Software
Last Post: nicolaos
09-17-2025, 06:36 PM
» Replies: 0
» Views: 3,811
|
the self built bl602_boot...
Forum: Getting Started
Last Post: pinecheng
09-16-2025, 02:15 PM
» Replies: 2
» Views: 4,887
|
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Gary2003
09-16-2025, 01:13 PM
» Replies: 13
» Views: 13,998
|
Cannot flash the modem fi...
Forum: Mobian on PinePhone
Last Post: anonymous
09-16-2025, 12:18 PM
» Replies: 7
» Views: 6,156
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
09-16-2025, 11:18 AM
» Replies: 8
» Views: 8,944
|
Mobian MMS/SMS text probl...
Forum: Mobian on PinePhone
Last Post: georgegohl888
09-15-2025, 02:42 AM
» Replies: 16
» Views: 24,973
|
|
|
Bluetooth sync software |
Posted by: adamfowleruk - 03-21-2022, 11:51 AM - Forum: PinePhone Pro Software
- Replies (1)
|
 |
Hi all,
I run the Herald Bluetooth Proximity project (part of Linux Foundation Public Health). This was originally for COVID-19 digital contact tracing app proximity, but can be used for general Bluetooth interoperability too. I've been thinking for a while a mobile app to share information, and eventually to sync data/settings might be useful between laptops/phones of different OS and models.
Would there be any particular angle to make this useful to PinePhone Pro users? I have a PinePhone and have just bought (yet to receive) a PinePhone Pro. It occurs to me that comms between different Pine-Things may be useful.
If there are particular scenarios people can think of do let me know. E.g. FindMyPinePhone, clipboard sharing, initial copying over of settings to a new phone, link to an opensource eHealth wearable and so on. (Note: We have C++, Java-Android, and Swift-iOS libraries that all interoperate).
All feedback welcome. Here's a link to the project itself if interested:-
https://heraldprox.io/herald
Thanks,
Adam.
|
|
|
Blueman GUI Bluetooth Network Access Point - fixing Bridging |
Posted by: biketool - 03-20-2022, 02:00 PM - Forum: Mobian on PinePhone
- Replies (12)
|
 |
This post is as much notes for me to look back on as a request for better minds to review my attempts.
(edit) Skip to the bottom post where I have the PAN protocol pairing via Blueman GUI but there is still a problem with getting the network bridge working.
I added the bluetoothpan.sh as per link below and after reviewing I assume the iptables commands in the script will work without editing them.
The problem is the pinephone is not reporting in its bluetooth UUID list that it is available as a network access point.
here is the UUID from my old N900 used for years as a bluetooth network access point
Code: <snip>
00000002-0000-1000-8000-0002ee000002 Proprietary
00001103-0000-1000-8000-00805f9b34fb Dialup Networking (DUN)
00001104-0000-1000-8000-00805f9b34fb IrMC Sync
00001105-0000-1000-8000-00805f9b34fb OBEX Object Push
00001106-0000-1000-8000-00805f9b34fb OBEX File Transfer
0000110a-0000-1000-8000-00805f9b34fb Audio Source
0000110c-0000-1000-8000-00805f9b34fb Remote Control Target
0000110e-0000-1000-8000-00805f9b34fb Remote Control
00001115-0000-1000-8000-00805f9b34fb PANU
00001116-0000-1000-8000-00805f9b34fb Network Access Point
00001117-0000-1000-8000-00805f9b34fb Group Network
0000112f-0000-1000-8000-00805f9b34fb Phonebook Access (PBAP) - PSE
00001132-0000-1000-8000-00805f9b34fb Message Access Server
00005005-0000-1000-8000-0002ee000001 Proprietary
00005601-0000-1000-8000-0002ee000001 Proprietary
/org/bluez/hci0
VS pinephone as is after script, unpair, reboot, and re-pair
Code: <snip>
00001104-0000-1000-8000-00805f9b34fb IrMC Sync
00001105-0000-1000-8000-00805f9b34fb OBEX Object Push
00001106-0000-1000-8000-00805f9b34fb OBEX File Transfer
00001108-0000-1000-8000-00805f9b34fb Headset
0000110a-0000-1000-8000-00805f9b34fb Audio Source
0000110b-0000-1000-8000-00805f9b34fb Audio Sink
0000110c-0000-1000-8000-00805f9b34fb Remote Control Target
0000110d-0000-1000-8000-00805f9b34fb Advanced Audio
0000110e-0000-1000-8000-00805f9b34fb Remote Control
0000111f-0000-1000-8000-00805f9b34fb Handsfree Audio Gateway
0000112f-0000-1000-8000-00805f9b34fb Phonebook Access (PBAP) - PSE
00001132-0000-1000-8000-00805f9b34fb Message Access Server
00001133-0000-1000-8000-00805f9b34fb Message Notification Server
00001200-0000-1000-8000-00805f9b34fb PnP Information
00001800-0000-1000-8000-00805f9b34fb Generic Access
00001801-0000-1000-8000-00805f9b34fb Generic Attribute
0000180a-0000-1000-8000-00805f9b34fb Device Information
00005005-0000-1000-8000-0002ee000001 Proprietary
usb:v1D6Bp0246d053E
/org/bluez/hci0
I followed the old N900 PAN script exactly after reviewing it
https://wiki.maemo.org/Bluetooth_PAN
I realize that the package genwall is probably what is doing the work bridging mobile data and bnep0 http://maemo.org/packages/view/genwall/
but not sure where/how the PAN and BT network access point profiles are generated on the N900 but not the Pinephone
Code: When connecting the PinePhone through the USB cable it creates a network the PC will join. The PinePhone has the IP address 10.66.0.1 fixed but the IP address of your PC will vary. Set up ip-forwarding on your PC and set up NAT on your outgoing internet interface:
sudo sysctl net.ipv4.ip_forward=1
sudo iptables -P FORWARD ACCEPT
DEV=$(ip route get 1 | grep -o 'dev .*' | cut -d ' ' -f 2)
sudo iptables -t nat -D POSTROUTING -o "$DEV" -j MASQUERADE 2> /dev/null || true
sudo iptables -t nat -A POSTROUTING -o "$DEV" -j MASQUERADE
Afterwards, on the PinePhone, e.g., through SSH to 10.66.0.1, you need to set the default route to be your PC's USB network interface, and you need to define a DNS server (here 1.1.1.1 from Cloudflare):
sudo ip route add default via "$(arp -n | grep 10.66.0. | grep ether | cut -d ' ' -f 1)"
sudo resolvectl dns usb0 1.1.1.1
sudo resolvectl default-route usb0 true
When you disconnect the cable without rebooting any device, on reconnecting you only need to repeat the commands on the PinePhone to set up the default route again.
the above from https://wiki.mobian-project.org/doku.php...pc-via-usb still requires SSHing into your phone VS using it as an automated BT net access point.
UFW https://wiki.mobian-project.org/doku.php...g#firewall might work to bridge mobile data to bnep0 but we still have the UUID problem.
and do I need to kludge about with scripting a bnep0?
https://www.linuxquestions.org/questions...157-print/
I dont think so because the
Code: /etc/udev/rules.d/98-bnep0.rules:
ACTION=="add", SUBSYSTEM=="net", KERNEL=="bnep0", RUN+="/etc/udev/bluenet.sh"
ACTION=="remove", SUBSYSTEM=="net", KERNEL=="bnep0", RUN+="/etc/udev/bluenet.sh"
generates the bnep0 device
additionaly the /etc/udev/bluenet.sh script might be a bit wonky
just to note it here a friend suggested to me
>this is why often, folks write stuff like if [ x$ACTION = x"add" ]; then
>you need to export ACTION = "add"
> if you want to run this script manually
> or
> Action=add /etc/udev/bluenet.sh
> for debugging you may insert a line#2 of logger "this is /etc/udev/bluenet.sh action: $ACTION" and see what you get in syslog
> logger "this is /etc/udev/bluenet.sh action: $ACTION"« is also a good way to check if the udev on your target platform maybe defines other actions than "add" for $ACTION
> which might well be the real root of your problem
>arbitrary example (I plugged in a USB memstick) https://termbin.com/m7h7
> mobian@mobian:/usr/sbin$ sudo /etc/udev/bluenet.sh
> will fail, like you seen
> you need
> mobian@mobian:/usr/sbin$ sudo ACTION=add /etc/udev/bluenet.sh
this document probably has everything needed as it creates a PAN for an OpenWRT router
https://elinux.org/images/1/15/ELC_NA_20...0814r1.pdf
including the below
Code: root@OpenWrt:~# dbus-send --system
--dest=org.bluez /org/bluez/hci0
--type=method_call
org.bluez.NetworkServer1.Register
string:“00001116-0000-1000-8000-00805f9b34fb”
string:"br-lan"
which full circle seems to address the UUID issue, maybe better minds will see the answer in the steps I have taken and info gathered in this post.
|
|
|
Manjaro I3 |
Posted by: james64 - 03-20-2022, 06:07 AM - Forum: General Discussion on Pinebook Pro
- Replies (1)
|
 |
I have official Manjaro i3 ARM install on my pinebook pro.
Today I used the laptop for the first in almost a year. I tried pacman -Syyu and it says nothing to do.
I visited Manjaro website and ARM i3 for PBP is not listed. Was it discontinued? Where can I read about that?
thanks
|
|
|
|