Kahvibreak Nokia S40 Game Dumping - Revision history

Prostagma at 03:37, 22 January 2021

2021-01-22T03:37:19Z

← Older revision		Revision as of 05:37, 22 January 2021
Line 206:		Line 206:

	[[Category:Kahvibreak]]		[[Category:Kahvibreak]]
	[[Category:~~Curation~~ Guides]]		[[Category:Other Guides]]

Prostagma: categories

2021-01-19T17:16:26Z

Nokia64: Improved "Configuring gammu" section

2020-04-23T20:57:56Z

Improved "Configuring gammu" section

← Older revision		Revision as of 22:57, 23 April 2020
Line 38:		Line 38:

	====Windows====		====Windows====
	:ToDo: Document procedure with Toshiba's bluetooth stack.		:ToDo: Document procedure with Toshiba's bluetooth stack. Document MAC obtaining.
	:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)		:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)
	:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface. <br/>Press Windows + R and type in <code>control printers</code>, then press Enter. Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.		:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface. <br/>Press Windows + R and type in <code>control printers</code>, then press Enter. Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.
Line 54:		Line 54:
	: Nokia phones with Pop-Port connector may have different technologies regarding data cable connection, despite the Pop-Port connector being the same:		: Nokia phones with Pop-Port connector may have different technologies regarding data cable connection, despite the Pop-Port connector being the same:
	:* '''Serial''': on older phones. You will need either a Nokia CA-42, Nokia DKU-5 or aftermarket compatible cable. Such cables have a chip to do serial emulation over USB (Help Needed: CA-42 Might be internally performing differently, but should work)		:* '''Serial''': on older phones. You will need either a Nokia CA-42, Nokia DKU-5 or aftermarket compatible cable. Such cables have a chip to do serial emulation over USB (Help Needed: CA-42 Might be internally performing differently, but should work)
	:* '''USB''': on newer phones. You will need either a Nokia CA-53, Nokia CA-70, Nokia DKU-2 or aftermarket compatible cable. Such cables do direct connection between the computer and the phone, which does USB directly. ~~<br>~~You may check here [~~NokiaCableArchivedPages~~] whether your phone needs a serial or direct USB type cable. Also, you can tell some USB capable phones by checking whether they have a "USB data Cable" option on Settings > Connectivity.		:* '''USB''': on newer phones. You will need either a Nokia CA-53, Nokia CA-70, Nokia DKU-2 or aftermarket compatible cable. Such cables do direct connection between the computer and the phone, which does USB directly.
			:You may check [https://web.archive.org/web/20060718004201/http://europe.nokia.com/A4144914 here] and [https://web.archive.org/web/20071011052734/http://europe.nokia.com/A4144914 here (newer list)] whether your phone needs a serial or direct USB type cable. Also, you can tell some USB capable phones by checking whether they have a "USB data Cable" option on Settings > Connectivity.
	* '''Other connectors''':		* '''Other connectors''':
	: Some other phones have very specific connectors. Most of them are direct USB, so the procedure should not vary.		: Some other phones have very specific connectors. Most of them are direct USB, so the procedure should not vary.
Line 98:		Line 99:
	name = </pre>		name = </pre>
	* '''connection''':		* '''connection''':
	: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. ~~Please refer~~ to this documentation snippet from Gammu ~~[gammusnippet~~] ~~for more information~~.		: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''phonetblue'' or ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. Trying different settings is the best way to find out one that works. There's some technical documentation about connection types in [https://github.com/gammu/gammu/blob/master/docs/config/gammurc this documentation snippet from Gammu].
	:~~[ToDo~~: ~~Explain and document more cases, link~~ to ~~gammu doc]~~		: Some of our test results, for orientative purposes:
			<pre>
			Test results:
			Device \| Linux \| Windows \|
			---------------------------------------------------------------------
			Nokia 3100 (Via Serial to USB data cable) \| fbus \|
			Nokia 7230 (Via Bluetooth) \| bluephonet \| phonetblue \|
			Nokia 6151 (Via direct USB) \| fbususb \| ??? \|
			---------------------------------------------------------------------
			</pre>
	* '''device''':		* '''device''':
	: If connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, ~~under Linux~~ set it to the phone's interface device node~~, under~~ Windows set it to the phone's COM port, as <code>comX:</code>		:*Linux: if connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, set it to the phone's interface device node
			:*Windows: set it to the phone's COM port, as <code>comX:</code>
	* '''name''':		* '''name''':
	: An identifier for the phone, can be anything user-set		: An identifier for the phone, can be anything user-set
	'''Additional information for Windows users:'''		'''Additional information for Windows users:'''
	* Strange issues were experienced while reordering the elements in the config file. This should not be happening, but placing the ''connection'' field after the ''device'' one seems to cause the connection to fail. Due to this, we recommend keeping the fields ordered in the same way as our examples.		* Strange issues were experienced while reordering the elements in the config file. This should not be happening, but placing the ''connection'' field after the ''device'' one seems to cause the connection to fail. Due to this, we recommend keeping the fields ordered in the same way as our examples.
	* Adding `GammuCoding = CP1250` will make ~~_gammu_~~ output special characters in filenames in the character encoding understood by Windows command line. It's recommended to add it to the config file when running under Windows.		* Adding `GammuCoding = CP1250` will make ''gammu'' output special characters in filenames in the character encoding understood by Windows command line. It's recommended to add it to the config file when running under Windows.
	Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")		Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")
	===Examples===		===Examples===
Line 130:		Line 141:
	name = Nokia 7230		name = Nokia 7230
	</pre>		</pre>
			[ToDo: Win/BT]

	==4. Using Gammu==		==4. Using Gammu==

Nokia64: Complete using Gammu section,

2020-04-23T18:48:17Z

Complete using Gammu section,

@@ Line 68: / Line 68: @@
 [10674.228200] usb 3-1.2: Manufacturer: Nokia
 [10674.389704] cdc_acm 3-1.2:1.1: ttyACM0: USB ACM device</pre>
-* (Aftermarket USB-Serial data cable, with _Prolific_ PL2303 chip)
+* (Aftermarket USB-Serial data cable, with ''Prolific'' PL2303 chip)
 <pre>[ 2953.638050] usbserial: USB Serial support registered for pl2303
 [ 2953.638097] pl2303 3-1.2:1.0: pl2303 converter detected
@@ Line 143: / Line 143: @@
 : On both cases, if done right, typing <code>gammu</code> and pressing Enter should greet you with the program's built-in help message.
 '''2. Specifying the config file.'''
-: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This tells Gammu that the following argument will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.
+: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This argument tells Gammu that argument following it will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.
 : For example, if the config file path is <code>C:\Example\gammu_config.txt</code> the command will look like this:<br/> <code>gammu -c "C:\Example\gammu_config.txt"</code>
-'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down keys.
+'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down arrow keys.
 '''3. Testing the connection.'''
@@ Line 158: / Line 158: @@
 [...]</pre>
 :Note: If you get a "No response from device in specified time" error, make sure the connection type (Step 3) is properly set. Sometimes it's a matter of trial and error.

Nokia64: Add Nokia cable pics

2020-04-23T17:36:31Z

Add Nokia cable pics

← Older revision		Revision as of 19:36, 23 April 2020
Line 40:		Line 40:
	:ToDo: Document procedure with Toshiba's bluetooth stack.		:ToDo: Document procedure with Toshiba's bluetooth stack.
	:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)		:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)
	:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface.		:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface. <br/>Press Windows + R and type in <code>control printers</code>, then press Enter. Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.
	::Press Windows + R and type in <code>control printers</code>, then press Enter. Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.



	===Data cable===		===Data cable===
	Nokia phones may have many different connector types:		[[File:Kahvi-NokiaDataCables-toMobile.png]] [[File:Kahvi-NokiaDataCables-toPC.png]] <br/>
			Photo credits: User ''CHC - NO "i"'' from Howard Forums <br/>

			'''Nokia phones may have many different connector types:'''
	* '''USB''':		* '''USB''':
	: Use a standard USB cable to perform the connection.		: Use a standard USB cable to perform the connection.
Line 78:		Line 80:
	:* '''Original Nokia Direct USB cables'''		:* '''Original Nokia Direct USB cables'''
	:* '''PL2303-based Serial to USB cables:''' No drivers at Windows Update. Without driver it appears on Windows Device Manager as "USB-Serial Controller" under "Other Devices" <br/> Drivers available at: http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 for Windows XP up to 10, Don't forget to reboot. <br/> HXA/XA chip variants not supported on Win8 and above, there's an unnoficial patch to the drivers to make them interface those chip variants again on Win10 computers [ToDo] <br/> Despite Gammu having a special connection type ''fbuspl2303'' for pl2303 chips, the standard ''fbus'' was proven more reliable in our tests.		:* '''PL2303-based Serial to USB cables:''' No drivers at Windows Update. Without driver it appears on Windows Device Manager as "USB-Serial Controller" under "Other Devices" <br/> Drivers available at: http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 for Windows XP up to 10, Don't forget to reboot. <br/> HXA/XA chip variants not supported on Win8 and above, there's an unnoficial patch to the drivers to make them interface those chip variants again on Win10 computers [ToDo] <br/> Despite Gammu having a special connection type ''fbuspl2303'' for pl2303 chips, the standard ''fbus'' was proven more reliable in our tests.

			To open Device Manager, Press Windows + R and execute <code>devmgmt.msc</code>

	===IrDA===		===IrDA===

Nokia64 at 17:21, 23 April 2020

2020-04-23T17:21:46Z

← Older revision		Revision as of 19:21, 23 April 2020
Line 95:		Line 95:
	* '''connection''':		* '''connection''':
	: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. Please refer to this documentation snippet from Gammu [gammusnippet] for more information.		: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. Please refer to this documentation snippet from Gammu [gammusnippet] for more information.
			:[ToDo: Explain and document more cases, link to gammu doc]
	* '''device''':		* '''device''':
	: If connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, under Linux set it to the phone's interface device node, under Windows set it to the phone's COM port, as <code>comX:</code>		: If connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, under Linux set it to the phone's interface device node, under Windows set it to the phone's COM port, as <code>comX:</code>
	* '''name''':		* '''name''':
	: An identifier for the phone, can be anything user-set		: An identifier for the phone, can be anything user-set
			'''Additional information for Windows users:'''
			* Strange issues were experienced while reordering the elements in the config file. This should not be happening, but placing the ''connection'' field after the ''device'' one seems to cause the connection to fail. Due to this, we recommend keeping the fields ordered in the same way as our examples.
			* Adding `GammuCoding = CP1250` will make _gammu_ output special characters in filenames in the character encoding understood by Windows command line. It's recommended to add it to the config file when running under Windows.
	Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")		Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")
			===Examples===
	~~'''~~Examples~~:'''~~
	* (Nokia 3100 at COM8, Windows)		* (Nokia 3100 at COM8, Windows)
	<pre>[gammu]		<pre>[gammu]
			GammuCoding = CP1250
	connection = fbus		connection = fbus
	device = com8:		device = com8:
Line 137:		Line 141:
	: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This tells Gammu that the following argument will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.		: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This tells Gammu that the following argument will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.

	: For example, if the config file path is <code>C:\Example\~~gammu config~~.txt</code> the command will look like this:<br/> <code>gammu -c "C:\Example\~~gammu config~~.txt"</code>		: For example, if the config file path is <code>C:\Example\gammu_config.txt</code> the command will look like this:<br/> <code>gammu -c "C:\Example\gammu_config.txt"</code>
	'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down keys.		'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down keys.

	'''3. Testing the connection.'''		'''3. Testing the connection.'''
	:Now, let's check whether the connection is working and properly configured. Gammu's ''identify'' command will print basic information about your phone, and it's a quick way of testing whether the connection works. Append <code>identify</code> to the command line arguments: <br/><code>gammu -c "C:\Example\~~gammu config~~.txt" identify</code>		:Now, let's check whether the connection is working and properly configured. Gammu's ''identify'' command will print basic information about your phone, and it's a quick way of testing whether the connection works. Append <code>identify</code> to the command line arguments: <br/><code>gammu -c "C:\Example\gammu_config.txt" identify</code>
	:Once run, something like this should appear:		:Once run, something like this should appear:
	<pre>		<pre>

Nokia64: O.O Neat Windoze trickery

2020-04-23T17:05:14Z

O.O Neat Windoze trickery

← Older revision		Revision as of 19:05, 23 April 2020
Line 41:		Line 41:
	:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)		:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)
	:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface.		:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface.
	::* [ToDo: WinXP]		::Press Windows + R and type in <code>control printers</code>, then press Enter. Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.
	::* Windows ~~7: Go to "Devices~~ and ~~Printers" (at Start Menu)~~,
	~~::* [ToDo: Win10]~~
	::Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.

Nokia64: Those screwages you only see after pressing "save"

2020-04-23T16:59:27Z

Those screwages you only see after pressing "save"

← Older revision		Revision as of 18:59, 23 April 2020
Line 136:		Line 136:
	::* If you used the installer and added Gammu to the system path, press Windows Key + R, then type in ''cmd'' and press Enter.		::* If you used the installer and added Gammu to the system path, press Windows Key + R, then type in ''cmd'' and press Enter.
	::* If you extracted the files using 7Zip or did not add Gammu to the system path, browse to the directory where Gammu files are and do Shift + Right Click on the ''bin'' folder, then choose "open command window here"		::* If you extracted the files using 7Zip or did not add Gammu to the system path, browse to the directory where Gammu files are and do Shift + Right Click on the ''bin'' folder, then choose "open command window here"
	: On ~~all~~ cases, if done right, typing <code>gammu</code> and pressing Enter should greet you with the program's built-in help message.		: On both cases, if done right, typing <code>gammu</code> and pressing Enter should greet you with the program's built-in help message.
	'''2. Specifying the config file.'''		'''2. Specifying the config file.'''
	: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This tells Gammu that the following argument will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.		: We should tell Gammu where our configuration file is. To do so, we will specify it as a command-line argument.<br/> First of all, append a <code>-c</code> argument after the <code>gammu</code> command on the command line. This tells Gammu that the following argument will be the path to the configuration file. So now, paste the path after it, enclosed in '''"''' . On Windows, keep in mind that Ctrl+V won't work, do Right Click > Paste. Use your favourite way on Linux, many graphical terminal emulators let you paste by doing Ctrl+Shift+V.

	: For example, if the config file path is <code>C:\Example\gammu config.txt</code> the command will look like this:</br> <code>gammu -c "C:\Example\gammu config.txt"</code>		: For example, if the config file path is <code>C:\Example\gammu config.txt</code> the command will look like this:<br/> <code>gammu -c "C:\Example\gammu config.txt"</code>
	'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down keys.		'''Tip''': On Windows command line and most shells you can quickly recall past commands with the Up and Down keys.

Nokia64: Typos, reorganization and Bluetooth under Windoze

2020-04-23T16:56:47Z

Typos, reorganization and Bluetooth under Windoze

← Older revision		Revision as of 18:56, 23 April 2020
Line 21:		Line 21:
	===Bluetooth (Recommended, if available on your phone/computer)===		===Bluetooth (Recommended, if available on your phone/computer)===
	Make sure your phone haves Bluetooth enabled and phone visibility is set to discoverable mode.		Make sure your phone haves Bluetooth enabled and phone visibility is set to discoverable mode.
	On most phones Bluetooth settings are at Menu > Settings > Connectivity > Bluetooth		On most phones Bluetooth settings are at Menu > Settings > Connectivity > Bluetooth<br/>
			'''You will need the Bluetooth MAC address of your phone.''' It usually looks like a ''XX:XX:XX:XX:XX:XX'' string composed of hexadecimal numbers (0-9 and A-F characters). Sometimes it's shown without the ''':''' between them.<br/>On some phones you can check it out by dialing the code <code>*#2820#</code> (It's the 12 characters shown at the first line)
	====Linux====		====Linux====
	:Pair your phone to the bluetooth adaptor of your computer. Use your favourite method for doing so.<br/>For convenience, here's an how-to using ''bluetoothctl'': <br/>		:Pair your phone to the bluetooth adaptor of your computer. Use your favourite method for doing so.<br/>For convenience, here's an how-to using ''bluetoothctl'': <br/>
Line 30:		Line 31:
	:# Make sure the controller is powered and pairable, to do so run <code>power on</code>, <code>pairable on</code> and <code>agent on</code> (The agent is the pairing passkey negotiator).		:# Make sure the controller is powered and pairable, to do so run <code>power on</code>, <code>pairable on</code> and <code>agent on</code> (The agent is the pairing passkey negotiator).
	:# Start scanning for devices, run <code>scan on</code>. Eventually, new found devices will be echoed to the command line.<br/> You can display all found (and paired) devices with the <code>devices</code> command. You should see your phone appear on the list.		:# Start scanning for devices, run <code>scan on</code>. Eventually, new found devices will be echoed to the command line.<br/> You can display all found (and paired) devices with the <code>devices</code> command. You should see your phone appear on the list.
	:# Pair with your phone. Given your phone is <code>Device XX:XX:XX:XX:XX:XX (Friendly ~~Bluetooth~~ name ~~of your device)~~</code>, run <code>pair XX:XX:XX:XX:XX:XX</code>. This ''XX:XX:XX:XX:XX:XX'' string is the Bluetooth MAC address of your phone, you will need it later. <br/>Depending on your device, you will either have to:		:# Pair with your phone. Given your phone is <code>Device XX:XX:XX:XX:XX:XX [Friendly device name]</code>, run <code>pair XX:XX:XX:XX:XX:XX</code>. This ''XX:XX:XX:XX:XX:XX'' string is the Bluetooth MAC address of your phone, you will need it later. <br/>Depending on your device, you will either have to:
	:## Confirm a passkey. Type <code>yes</code> when prompted <code>Confirm passkey XXXXXX (yes/no)</code>		:## Confirm a passkey. Type <code>yes</code> when prompted <code>Confirm passkey XXXXXX (yes/no)</code>
	:## Type a passkey. You will be prompted for a passkey on both devices. Enter any same passkey in both devices.		:## Type a passkey. You will be prompted for a passkey on both devices. Enter any same passkey in both devices.
Line 37:		Line 38:

	====Windows====		====Windows====
	:ToDo: Document procedure, both ~~with~~ Windows ~~bluetooth stack~~ and ~~Toshiba~~'s ~~bluetooth stack~~.		:ToDo: Document procedure with Toshiba's bluetooth stack.
			:# Pair your phone with the computer: open the device paring wizard by pressing Windows + R and typing in <code>DevicePairingWizard</code> . Wait for your phone to appear, select it and follow the steps prompted by Windows. If it does not appears, make sure the phone is set on discoverable mode and it's not already paired to your computer. Even if it was already paired, it's recommended to re-pair it to avoid possible issues. (Remember you have to remove the pairing from both devices!)
			:# Find the COM port assigned to your phone's "Nokia PC Suite" serial interface.
			::* [ToDo: WinXP]
			::* Windows 7: Go to "Devices and Printers" (at Start Menu),
			::* [ToDo: Win10]
			::Right click at your phone, select "Properties" and go to the "Services" tab. A list of ''services'' will appear, look for the "Nokia PC Suite" one, make sure it's enabled and remember the COM port number at it's right.



	'''You will need the Bluetooth MAC adress of your phone.''' It usually looks like a ''XX:XX:XX:XX:XX:XX'' string composed of hexadecimal numbers (0-9 and A-F characters). Sometimes it's shown without the ''':''' between them.<br/>On some phones you can check it out by dialing the code <code>*#2820#</code> (It's the 12 hex characters shown at the first line)

	===Data cable===		===Data cable===
Line 71:		Line 76:
	In the above cases, ''/dev/ttyACM0'' and ''/dev/ttyUSB0'' are the device nodes assigned to the phone's data interface.<br/> You will likely want to make it readable/writable by your user. Do <code>chmod 777 [device node]</code> (as superuser) to make the device node readable/writable by everyone (non-permanently).		In the above cases, ''/dev/ttyACM0'' and ''/dev/ttyUSB0'' are the device nodes assigned to the phone's data interface.<br/> You will likely want to make it readable/writable by your user. Do <code>chmod 777 [device node]</code> (as superuser) to make the device node readable/writable by everyone (non-permanently).
	====Windows====		====Windows====
	ToDo~~: document procedure~~		'''This section is a stub. It is not finished''' <br/>
			On Windows, you <s>will</s> may encounter issues depending on your cable and connection type.
			:* '''Original Nokia Serial to USB cables'''
			:* '''Original Nokia Direct USB cables'''
			:* '''PL2303-based Serial to USB cables:''' No drivers at Windows Update. Without driver it appears on Windows Device Manager as "USB-Serial Controller" under "Other Devices" <br/> Drivers available at: http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 for Windows XP up to 10, Don't forget to reboot. <br/> HXA/XA chip variants not supported on Win8 and above, there's an unnoficial patch to the drivers to make them interface those chip variants again on Win10 computers [ToDo] <br/> Despite Gammu having a special connection type ''fbuspl2303'' for pl2303 chips, the standard ''fbus'' was proven more reliable in our tests.

	===IrDA===		===IrDA===
	It is also possible to connect to IrDA (Infrared) capable phones via an IrDA interface. Not recommended since some phones have a mysterious firmware bug causing them to brick over time when using Gammu to interface them over IrDA.		It is also possible to connect to IrDA (Infrared) capable phones via an IrDA interface. Not recommended since some phones have a mysterious firmware bug causing them to brick over time when using Gammu to interface them over IrDA.
Line 77:		Line 87:
	Gammu uses text files to store it's configuration parameters. <br/> At their simplest form, they have the following syntax:		Gammu uses text files to store it's configuration parameters. <br/> At their simplest form, they have the following syntax:
	<pre>[gammu]		<pre>[gammu]
			connection = [Connection mode]
	device = [Device Node/Bluetooth Address/COM Port]		device = [Device Node/Bluetooth Address/COM Port]
	name = [Phone's friendly name, can be anything user-set]		name = [Phone's friendly name, can be anything user-set]</pre>
	~~connection = [Connection mode~~]</pre>

	Create a empty text file and type/paste the following template:		Create a empty text file and type/paste the following template:
	<pre>[gammu]		<pre>[gammu]
			connection =
	device =		device =
	name =		name = </pre>
	~~connection~~ = </pre>		* '''connection''':
			: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. Please refer to this documentation snippet from Gammu [gammusnippet] for more information.
	* '''device''':		* '''device''':
	: If connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, under Linux set it to the phone's interface device node, under Windows set it to the phone's COM port, as <code>comX:</code>		: If connecting over Bluetooth, set it to the ''XX:XX:XX:XX:XX:XX'' Bluetooth address of the phone. If connecting via data cable, under Linux set it to the phone's interface device node, under Windows set it to the phone's COM port, as <code>comX:</code>
	* '''name''':		* '''name''':
	: An identifier for the phone, can be anything user-set		: An identifier for the phone, can be anything user-set
	* '''connection''':
	: This is the protocol variant Gammu will use to communicate with the phone. The most common values are ''fbus'' for Serial-over-USB phones, ''bluephonet'' for connections over Bluetooth and ''fbusdku5'' or ''dku2'' for direct USB connections. Please refer to this documentation snippet from Gammu [gammusnippet] for more information.
	Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")		Save the text file to a known location, and copy it's path. Filename does not matters. (On Windows, hold Shift and right click on the file then select "Copy as Path")

Line 97:		Line 107:
	* (Nokia 3100 at COM8, Windows)		* (Nokia 3100 at COM8, Windows)
	<pre>[gammu]		<pre>[gammu]
			connection = fbus
	device = com8:		device = com8:
	name = Nokia 3100		name = Nokia 3100
	~~connection = fbus~~
	</pre>		</pre>
	* (Nokia 7210 at /dev/ttyUSB0, Linux)		* (Nokia 7210 at /dev/ttyUSB0, Linux)
	<pre>		<pre>
	[gammu]		[gammu]
			connection = fbus
	device = /dev/ttyUSB0		device = /dev/ttyUSB0
	name = Nokia 7210		name = Nokia 7210
	~~connection = fbus~~
	</pre>		</pre>
	* (Nokia 7230 over Bluetooth)		* (Nokia 7230 over Bluetooth, Linux)
	<pre>		<pre>
	[gammu]		[gammu]
			connection = bluephonet
	device = 9C:4A:00:00:00:00		device = 9C:4A:00:00:00:00
	name = Nokia 7230		name = Nokia 7230
	~~connection = bluephonet~~
	</pre>		</pre>

Nokia64: I had "a" issue

2020-04-05T09:52:07Z

I had "a" issue

← Older revision		Revision as of 11:52, 5 April 2020
Line 69:		Line 69:
	[ 2953.639975] usb 3-1.2: pl2303 converter now attached to ttyUSB0</pre>		[ 2953.639975] usb 3-1.2: pl2303 converter now attached to ttyUSB0</pre>

	In the above cases, ''/dev/ttyACM0'' and ''/dev/ttyUSB0'' are the device nodes assigned to the phone's data interface.<br/> You will likely want to make it readable/writable by your user. Do <code>chmod 777 ~~/dev/{phone}~~</code> (as superuser) to make the device node readable/writable by everyone (non-permanently).		In the above cases, ''/dev/ttyACM0'' and ''/dev/ttyUSB0'' are the device nodes assigned to the phone's data interface.<br/> You will likely want to make it readable/writable by your user. Do <code>chmod 777 [device node]</code> (as superuser) to make the device node readable/writable by everyone (non-permanently).
	====Windows====		====Windows====
	ToDo: document procedure		ToDo: document procedure
	===IrDA===		===IrDA===
	It is also possible to connect to IrDA (Infrared) capable phones via a IrDA interface. Not recommended since some phones have a mysterious firmware bug causing them to brick over time when using Gammu to interface them over IrDA.		It is also possible to connect to IrDA (Infrared) capable phones via an IrDA interface. Not recommended since some phones have a mysterious firmware bug causing them to brick over time when using Gammu to interface them over IrDA.
	==3. Configuring Gammu==		==3. Configuring Gammu==
	Gammu uses text files to store it's configuration parameters. <br/> At their simplest form, they have the following syntax:		Gammu uses text files to store it's configuration parameters. <br/> At their simplest form, they have the following syntax:

← Older revision		Revision as of 19:16, 19 January 2021
Line 204:		Line 204:
	:* If you are on Linux, running <code>pwd</code> will return the current working directory. Navigate there with your favourite file browser.		:* If you are on Linux, running <code>pwd</code> will return the current working directory. Navigate there with your favourite file browser.
	:* If you are on Windows, execute <code>explorer .</code> to open the current working directory in Windows Explorer.		:* If you are on Windows, execute <code>explorer .</code> to open the current working directory in Windows Explorer.

			[[Category:Kahvibreak]]
			[[Category:Curation Guides]]