<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://maemo.octonezd.me/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=79.184.238.31</id>
	<title>Maemo Wiki Mirror - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://maemo.octonezd.me/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=79.184.238.31"/>
	<link rel="alternate" type="text/html" href="https://maemo.octonezd.me/index.php/Special:Contributions/79.184.238.31"/>
	<updated>2026-04-22T05:55:59Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://maemo.octonezd.me/index.php?title=Fremantle_Unsupported_Bluetooth_profiles&amp;diff=10974</id>
		<title>Fremantle Unsupported Bluetooth profiles</title>
		<link rel="alternate" type="text/html" href="https://maemo.octonezd.me/index.php?title=Fremantle_Unsupported_Bluetooth_profiles&amp;diff=10974"/>
		<updated>2017-12-16T18:45:33Z</updated>

		<summary type="html">&lt;p&gt;79.184.238.31: Perhaps you discovered a place or a social circle that is different, but if this was a brazilian facet, it is sadly fading as time goes.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are several [[Bluetooth]] profiles officially missing/unsupported in [[Open development/Maemo roadmap/Fremantle|Fremantle]] that are however supported by the upstream BlueZ project or can be made to work with some simple hacks. &lt;br /&gt;
&lt;br /&gt;
== DUN server ==&lt;br /&gt;
&lt;br /&gt;
There&#039;s a tool called pnatd (short for PhoNet AT Daemon) which can act as a proxy between the cellular modem PhoNet interface and a TTY device.&lt;br /&gt;
&lt;br /&gt;
=== Example script ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
sdptool add --channel 1 DUN&lt;br /&gt;
while true; do&lt;br /&gt;
        rfcomm -S --listen -1 1 /usr/bin/pnatd &#039;{}&#039;&lt;br /&gt;
        sleep 1&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is one known issue: Most likely due to a bug in the way that the Bluetooth and TTY subsystems in the kernel interact in this use case data can be lost if the DUN client starts immediately sending AT commands when the connection is created. This can e.g. be worked around by adding a 1 second delay to the chat script on the client side.&lt;br /&gt;
&lt;br /&gt;
Nonetheless, two dimensions of time kind a plane of time, which has no beginning and no end and is not restricted to any single course.  have a look [url=http://www.connoisseurseafood.pl/chocolate-slim--gdzie-kupic-cena-apteka.htm]Chocolate Slim[/url] my blog [url=http://www.rcn-conti.lv/man-pride-cena-lietoana-latvij.htm]Man Pride[/url]&lt;br /&gt;
&lt;br /&gt;
== PAN ==&lt;br /&gt;
&lt;br /&gt;
Fremantle comes with the bluetoothd network plugin installed but disabled through &amp;lt;code&amp;gt;/etc/bluetooth/main.conf&amp;lt;/code&amp;gt; - to use your N900 as a PAN server for other clients (such as N8x0) just enable this.&lt;br /&gt;
&lt;br /&gt;
If you want to connect to another device over PAN, see [[Bluetooth PAN]] for more detailed information.&lt;br /&gt;
&lt;br /&gt;
== Phone Book Access Profile (PBAP) and IrMC Sync ==&lt;br /&gt;
&lt;br /&gt;
{{main|Bluetooth PBAP}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Users]]&lt;br /&gt;
[[Category:Fremantle]]&lt;br /&gt;
[[Category:Bluetooth]]&lt;br /&gt;
[[Category:Power users]]&lt;/div&gt;</summary>
		<author><name>79.184.238.31</name></author>
	</entry>
</feed>