PR1.2 compulsory My Nokia subscription - Revision history

andre: Protected "PR1.2 compulsory My Nokia subscription" [edit=autoconfirmed:move=autoconfirmed]

2012-06-13T15:33:27Z

Protected "PR1.2 compulsory My Nokia subscription" [edit=autoconfirmed:move=autoconfirmed]

← Older revision

Revision as of 15:33, 13 June 2012

pelago: Undo revision 48339 by 151.142.239.11 (Talk) Vandalism

2012-06-12T08:33:15Z

Undo revision 48339 by 151.142.239.11 (Talk) Vandalism

← Older revision		Revision as of 08:33, 12 June 2012
Line 11:		Line 11:
	Although users can unsubscribe after the installation is completed, Nokia have not said what data is sent in the registration SMS, they make no promises to remove their data, nor do they refund any costs and it is possible that the some courts may consider that the legal agreement they presented during the process was in some way binding on the user.		Although users can unsubscribe after the installation is completed, Nokia have not said what data is sent in the registration SMS, they make no promises to remove their data, nor do they refund any costs and it is possible that the some courts may consider that the legal agreement they presented during the process was in some way binding on the user.

-	That's ~~way more cvleer than I was expecting~~. ~~Thanks!~~	+	== How to avoid the compulsory registration while upgrading to PR1.2 ==
		+
		+	To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.
		+
		+	=== Automatic method ===
		+
		+	Install the ''notmynokia'' package from the [[extras-devel]] repository. As long as this package remains installed, it checks at every re-boot that the My Nokia registration program (cherry) will not run.
		+
		+	The package should be installed before the upgrade to PR1.2 takes place, and should remain installed afterwards. The package is believed to be effective for "over the air" (OTA) upgrades and should also work if the software is re-flashed (but the package should be re-installed as soon as possible afterwards).
		+
		+	However, if the eMMC is reflashed then protection is lost. See the notes on the manual method below for possible workrounds in this case.
		+
		+	Note: if you later decide you want to allow the registration, simply remove the ''notmynokia'' package.
		+
		+	=== Manual method ===
		+
		+	As you will see from the technical analysis below, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:
		+
		+	touch ~/.cherry_state
		+
		+	If, on your first boot into PR1.2, you see the Ny Nokia registration screen, see the "Recovery" section below.
		+
		+	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. See the section below for how to deal with that case.
		+
		+	=== Recovering ===
		+
		+	If the cherry process runs and displays the terms and conditions screen, it is not too late to avoid the registration as long as you have not clicked on the Done button to allow it to proceed. Simply turn the phone off by holding down the power button for a few seconds, remove the SIM card, and turn the phone back on again. Then, start X Terminal and type in the commands:
		+
		+	touch ~/.cherry_state
		+	sync
		+
		+	Note: if you have Wi-Fi network connectivity, you can install ''notmynokia'' instead of typing those commands if you wish.
		+
		+	Then turn the phone off again, reinsert the SIM card and turn it back on. The registration screen should not appear. You may want to still install ''notmynokia'' as soon as possible to help protect you in case the file somehow gets deleted.
		+
		+	If you have clicked to allow the registration process to continue, it is probably too late to stop it. Cherry will tell the CSD daemon, through CSD's libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM so the SMS is not visible in your Messaging history.
		+
		+	If the SMS cannot be sent (no balance on SIM card, no network coverage), the SMS may still be on the phone waiting to be sent. You can check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.
		+
		+	If the SMS has been sent, then all you can do is to use the Settings/My Nokia to unregister. Note that, in this case, Nokia makes no promises to discard your registration data (see the Terms and Conditions for whatever promises it makes, if any).

	== Technical analysis ==		== Technical analysis ==

151.142.239.11: /* How to avoid the compulsory registration while upgrading to PR1.2 */

2012-06-12T04:17:46Z

How to avoid the compulsory registration while upgrading to PR1.2

← Older revision		Revision as of 04:17, 12 June 2012
Line 11:		Line 11:
	Although users can unsubscribe after the installation is completed, Nokia have not said what data is sent in the registration SMS, they make no promises to remove their data, nor do they refund any costs and it is possible that the some courts may consider that the legal agreement they presented during the process was in some way binding on the user.		Although users can unsubscribe after the installation is completed, Nokia have not said what data is sent in the registration SMS, they make no promises to remove their data, nor do they refund any costs and it is possible that the some courts may consider that the legal agreement they presented during the process was in some way binding on the user.

-	~~== How to avoid the compulsory registration while upgrading to PR1.2 ==~~	+	That's way more cvleer than I was expecting. Thanks!
-		+
-	To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.	+
-		+
-	~~=== Automatic method ===~~	+
-		+
-	Install the ''notmynokia'' package from the [[extras-devel]] repository. As long as this package remains installed, it checks at every re-boot that the My Nokia registration program (cherry) will not run.	+
-		+
-	The package should be installed before the upgrade to PR1.2 takes place, and should remain installed afterwards. The package is believed to be effective for "over the air" (OTA) upgrades and should also work if the software is re-flashed (but the package should be re-installed as soon as possible afterwards).	+
-		+
-	~~However, if the eMMC is reflashed then protection is lost. See the notes on the manual method below for possible workrounds in this case.~~	+
-		+
-	~~Note: if you later decide you want to allow the registration, simply remove the ''notmynokia'' package.~~	+
-		+
-	~~=== Manual method ===~~	+
-		+
-	As you will see from the technical analysis below, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That ~~means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:~~	+
-		+
-	~~touch ~/.cherry_state~~	+
-		+
-	~~If, on your first boot into PR1.2, you see the Ny Nokia registration screen, see the "Recovery" section below.~~	+
-		+
-	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. See the section below for how to deal with that case.	+
-		+
-	~~=== Recovering ===~~	+
-		+
-	If the cherry process runs and displays the terms and conditions screen, it is not too late to avoid the registration as long as you have not clicked on the Done button to allow it to proceed. Simply turn the phone off by holding down the power button for a few seconds, remove the SIM card, and turn the phone back on again. Then, start X Terminal and type in the commands:	+
-		+
-	~~touch ~/.cherry_state~~	+
-	~~sync~~	+
-		+
-	~~Note: if you have Wi-Fi network connectivity, you can install ''notmynokia'' instead of typing those commands if you wish.~~	+
-		+
-	Then turn the phone off again, reinsert the SIM card and turn it back on. The registration screen should not appear. You may want to still install ''notmynokia'' as soon as possible to help protect you in case the file somehow gets deleted.	+
-		+
-	~~If you have clicked to allow the registration process to continue, it is probably too late to stop it. Cherry will tell the CSD daemon, through CSD~~'s ~~libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM so the SMS is not visible in your Messaging history.~~	+
-		+
-	If the SMS cannot be sent (no balance on SIM card, no network coverage), the SMS may still be on the phone waiting to be sent. You can check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.	+
-		+
-	If the SMS has been sent, then all you can do is to use the Settings/My Nokia to unregister. Note that, in this case, Nokia makes no promises to discard your registration data (see the Terms and Conditions for whatever promises it makes, if any).	+

	== Technical analysis ==		== Technical analysis ==

pelago: /* Automatic method */ Linked extras-devel

2011-01-08T17:35:18Z

Automatic method: Linked extras-devel

← Older revision		Revision as of 17:35, 8 January 2011
Line 17:		Line 17:
	=== Automatic method ===		=== Automatic method ===

-	Install the ''notmynokia'' package from the extras-devel repository. As long as this package remains installed, it checks at every re-boot that the My Nokia registration program (cherry) will not run.	+	Install the ''notmynokia'' package from the [[extras-devel]] repository. As long as this package remains installed, it checks at every re-boot that the My Nokia registration program (cherry) will not run.

	The package should be installed before the upgrade to PR1.2 takes place, and should remain installed afterwards. The package is believed to be effective for "over the air" (OTA) upgrades and should also work if the software is re-flashed (but the package should be re-installed as soon as possible afterwards).		The package should be installed before the upgrade to PR1.2 takes place, and should remain installed afterwards. The package is believed to be effective for "over the air" (OTA) upgrades and should also work if the software is re-flashed (but the package should be re-installed as soon as possible afterwards).

pelago: /* Recovering */ Clarified how to turn off, and a couple of other changes

2010-07-11T20:51:27Z

Recovering: Clarified how to turn off, and a couple of other changes

← Older revision		Revision as of 20:51, 11 July 2010
Line 37:		Line 37:
	=== Recovering ===		=== Recovering ===

-	If the cherry process runs and displays the terms and conditions screen, it is not too late to avoid the registration as long as you have not clicked on the button to allow it to proceed. Simply turn the phone off ~~(without clicking on~~ the ~~"Done"~~ button), remove the SIM card, and turn the phone back on again. Then, start ~~an Xterm~~ and type in the commands:	+	If the cherry process runs and displays the terms and conditions screen, it is not too late to avoid the registration as long as you have not clicked on the Done button to allow it to proceed. Simply turn the phone off by holding down the power button for a few seconds, remove the SIM card, and turn the phone back on again. Then, start X Terminal and type in the commands:

	touch ~/.cherry_state		touch ~/.cherry_state
	sync		sync

-	Note: if you have ~~WiFi~~ network connectivity, you can install ''notmynokia'' instead of typing those commands if you wish.	+	Note: if you have Wi-Fi network connectivity, you can install ''notmynokia'' instead of typing those commands if you wish.

	Then turn the phone off again, reinsert the SIM card and turn it back on. The registration screen should not appear. You may want to still install ''notmynokia'' as soon as possible to help protect you in case the file somehow gets deleted.		Then turn the phone off again, reinsert the SIM card and turn it back on. The registration screen should not appear. You may want to still install ''notmynokia'' as soon as possible to help protect you in case the file somehow gets deleted.

gcobb: Update Manual Method and add Recovering section

2010-07-11T15:04:46Z

Update Manual Method and add Recovering section

← Older revision		Revision as of 15:04, 11 July 2010
Line 31:		Line 31:
	touch ~/.cherry_state		touch ~/.cherry_state

-	~~Before you~~ first boot into PR1.2, ~~it is probably best to remove your SIM anyway~~, ~~just in case something went wrong and <code>/usr/bin/cherry</code> still ran~~.	+	If, on your first boot into PR1.2, you see the Ny Nokia registration screen, see the "Recovery" section below.

-	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. ~~But you can remove~~ the ~~SIM card, boot and create the file. Then you are free~~ to ~~reboot~~ with ~~the SIM card in and it should not subscribe you~~.	+	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. See the section below for how to deal with that case.

-	~~Cherry will tell the CSD daemon, through CSD's libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM.~~	+	=== Recovering ===

-	~~Before~~ you ~~put a~~ SIM back in, check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.	+	If the cherry process runs and displays the terms and conditions screen, it is not too late to avoid the registration as long as you have not clicked on the button to allow it to proceed. Simply turn the phone off (without clicking on the "Done" button), remove the SIM card, and turn the phone back on again. Then, start an Xterm and type in the commands:
		+
		+	touch ~/.cherry_state
		+	sync
		+
		+	Note: if you have WiFi network connectivity, you can install ''notmynokia'' instead of typing those commands if you wish.
		+
		+	Then turn the phone off again, reinsert the SIM card and turn it back on. The registration screen should not appear. You may want to still install ''notmynokia'' as soon as possible to help protect you in case the file somehow gets deleted.
		+
		+	If you have clicked to allow the registration process to continue, it is probably too late to stop it. Cherry will tell the CSD daemon, through CSD's libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM so the SMS is not visible in your Messaging history.
		+
		+	If the SMS cannot be sent (no balance on SIM card, no network coverage), the SMS may still be on the phone waiting to be sent. You can check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.
		+
		+	If the SMS has been sent, then all you can do is to use the Settings/My Nokia to unregister. Note that, in this case, Nokia makes no promises to discard your registration data (see the Terms and Conditions for whatever promises it makes, if any).

	== Technical analysis ==		== Technical analysis ==

jaffa: Nokia's response

2010-06-26T20:44:22Z

Nokia's response

← Older revision		Revision as of 20:44, 26 June 2010
Line 77:		Line 77:

	The package is not optified, contributing to the rootfs compressed terms files of about 1.3MB.		The package is not optified, contributing to the rootfs compressed terms files of about 1.3MB.
		+
		+	== Nokia's response ==
		+	Nokia [http://maemo.org/community/council/nokia_response_to_mynokia_subscription_in_pr1-2/ responded] to the [[Community Council]] on this:
		+
		+	<blockquote>
		+	:“Nokia Corporation respects applicable laws and regulations and has carefully reviewed the content in your mail. The latest Nokia devices are no longer traditional mobile phones. Instead they are mobile computers that include sophisticated services such as messaging, games, as well as capability to access online services, download applications, take pictures and video as well as to process text. Such devices should be seen more as portable computers with phone functionality rather than traditional mobile phones mainly capable making a phone call. N900 belongs to this category of mobile computers.
		+
		+	:The first use of the latest software for Nokia mobile computers include functionality preparing the device for the service use on behalf of the consumer. In this connection Nokia also provides the consumer with the possibility to receive support messages to assist the consumer get the most out of the purchased Nokia mobile computer. These messages include tips on the capabilities and features of the Nokia devices and available services and features. We believe that these support messages are for the benefit of the consumer and help those consumers who are not yet fully aware of the possibilities their devices offer to make the most out of their purchase.
		+
		+	:Nokia informs the user about this support feature and the cost of the SMS on the cover of the sales box and in the Nokia device user interface through the terms and conditions. Any personal information (including any information in the SMS) needed for the service is dealt with in accordance with Nokia's privacy policy available at http://www.nokia.com/privacy-policy.
		+
		+	:We have not found any grounds to assume that the My Nokia service would in any way breach the UK Computer Misuse Act, which is 'An Act to make provision for securing computer material against unauthorised access or modification; and for connected purposes'. Please provide further information if you feel a more detailed analysis is needed.
		+
		+	:In case you wish to know what personal data we hold about you or you wish to replenish, rectify, anonymize or delete any incomplete, incorrect or outdated personal data, or you wish us to cease processing your personal data for the purpose of sending promotional materials or direct marketing or for the performance of market research or on other compelling legal grounds, you may, as appropriate and in accordance with applicable law, exercise such rights by contacting us through the contact points referred to in Nokia’s privacy policy.”</blockquote>

	[[Category:N900]]		[[Category:N900]]
	[[Category:Users]]		[[Category:Users]]

gcobb: Add notmynokia package and some extra text

2010-06-24T10:19:07Z

Add notmynokia package and some extra text

← Older revision		Revision as of 10:19, 24 June 2010
Line 7:		Line 7:
	== The problem ==		== The problem ==

-	~~The main problem is that~~, ~~by default~~, all devices upgraded to PR1.2 are automatically subscribed to My Nokia. This involves a text (SMS) being sent from the device to Nokia, which might be at the owner's expense, and then receiving texts from Nokia. In normal circumstances, it is not possible to use the upgraded operating system without agreeing to subscribe to My Nokia.	+	In the PR1.2 update, Nokia included a feature to automatically register users with their MyNokia service. However, they did not allow an opt-out so all devices upgraded to PR1.2 are automatically subscribed to My Nokia. This involves a text (SMS) being sent from the device to Nokia, which might be at the owner's expense, and then receiving texts from Nokia. In normal circumstances, it is not possible to use the upgraded operating system without agreeing to subscribe to My Nokia.
		+
		+	Although users can unsubscribe after the installation is completed, Nokia have not said what data is sent in the registration SMS, they make no promises to remove their data, nor do they refund any costs and it is possible that the some courts may consider that the legal agreement they presented during the process was in some way binding on the user.

	== How to avoid the compulsory registration while upgrading to PR1.2 ==		== How to avoid the compulsory registration while upgrading to PR1.2 ==

	To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.		To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.
		+
		+	=== Automatic method ===
		+
		+	Install the ''notmynokia'' package from the extras-devel repository. As long as this package remains installed, it checks at every re-boot that the My Nokia registration program (cherry) will not run.
		+
		+	The package should be installed before the upgrade to PR1.2 takes place, and should remain installed afterwards. The package is believed to be effective for "over the air" (OTA) upgrades and should also work if the software is re-flashed (but the package should be re-installed as soon as possible afterwards).
		+
		+	However, if the eMMC is reflashed then protection is lost. See the notes on the manual method below for possible workrounds in this case.
		+
		+	Note: if you later decide you want to allow the registration, simply remove the ''notmynokia'' package.
		+
		+	=== Manual method ===

	As you will see from the technical analysis below, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:		As you will see from the technical analysis below, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:

pelago: Added bugs.maemo.org link

2010-06-23T21:37:49Z

Added bugs.maemo.org link

← Older revision		Revision as of 21:37, 23 June 2010
Line 3:		Line 3:
	The implementation of the feature is rather controversial, and some consider it a privacy breach. This document describes the problem and suggests some ways to work around it.		The implementation of the feature is rather controversial, and some consider it a privacy breach. This document describes the problem and suggests some ways to work around it.

-	See also the [http://talk.maemo.org/showthread.php?t=53565 ~~related~~ talk.maemo.org thread].	+	See also the related [http://talk.maemo.org/showthread.php?t=53565 talk.maemo.org thread] and [https://bugs.maemo.org/show_bug.cgi?id=10366 bugs.maemo.org bug].

	== The problem ==		== The problem ==

pelago: Move analysis lower down, as most people probably just want to find out how to avoid this

2010-06-23T21:28:20Z

Move analysis lower down, as most people probably just want to find out how to avoid this

← Older revision		Revision as of 21:28, 23 June 2010
Line 9:		Line 9:
	The main problem is that, by default, all devices upgraded to PR1.2 are automatically subscribed to My Nokia. This involves a text (SMS) being sent from the device to Nokia, which might be at the owner's expense, and then receiving texts from Nokia. In normal circumstances, it is not possible to use the upgraded operating system without agreeing to subscribe to My Nokia.		The main problem is that, by default, all devices upgraded to PR1.2 are automatically subscribed to My Nokia. This involves a text (SMS) being sent from the device to Nokia, which might be at the owner's expense, and then receiving texts from Nokia. In normal circumstances, it is not possible to use the upgraded operating system without agreeing to subscribe to My Nokia.

-	== ~~Technical analysis~~ ==	+	== How to avoid the compulsory registration while upgrading to PR1.2 ==
		+
		+	To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.
		+
		+	As you will see from the technical analysis below, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:
		+
		+	touch ~/.cherry_state
		+
		+	Before you first boot into PR1.2, it is probably best to remove your SIM anyway, just in case something went wrong and <code>/usr/bin/cherry</code> still ran.
		+
		+	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. But you can remove the SIM card, boot and create the file. Then you are free to reboot with the SIM card in and it should not subscribe you.
		+
		+	Cherry will tell the CSD daemon, through CSD's libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM.
		+
		+	Before you put a SIM back in, check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.

-	If you just wish to find out how to avoid this, please skip down to the [[#How to avoid the compulsory registration while upgrading to PR1.2\|How to avoid the compulsory registration while upgrading to PR1.2]] section.	+	== Technical analysis ==

	In PR1.2, the My Nokia feature is enabled by the "cherry" package. The package is closed source, but it can still be analysed to an extent. The package can be downloaded on any N900 (even those that have not been upgraded to PR1.2). Downloading the package as described here does not install it, so is safe. For some reason, trying to wget the package from a Linux desktop machine doesn't work.		In PR1.2, the My Nokia feature is enabled by the "cherry" package. The package is closed source, but it can still be analysed to an extent. The package can be downloaded on any N900 (even those that have not been upgraded to PR1.2). Downloading the package as described here does not install it, so is safe. For some reason, trying to wget the package from a Linux desktop machine doesn't work.
Line 48:		Line 62:
	The package also contains a ChangeLog, which makes interesting reading as to how the package developed over time.		The package also contains a ChangeLog, which makes interesting reading as to how the package developed over time.

-	The package is not optified, contributing to the rootfs compressed terms files of about 1.3MB	+	The package is not optified, contributing to the rootfs compressed terms files of about 1.3MB.
-		+
-	~~== How to avoid the compulsory registration while upgrading to PR1.2 ==~~	+
-		+
-	To avoid the compulsory registration, i.e. to avoid the device sending a text to Nokia and breaching privacy, it is most important to stop the <code>/usr/bin/cherry</code> app from running. It would also be nice to remove the My Nokia applet from Settings, but at least that should not subscribe you without asking.	+
-		+
-	As you will see from the technical analysis above, creating a file called <code>/home/user/.cherry_state</code> should stop <code>/usr/bin/cherry</code> from running. This file lives in the eMMC, so if your PR1.2 upgrade procedure doesn't involve flashing eMMC, then you can create that file before you upgrade and it should still be there after the upgrade. That means that you should avoid running <code>/usr/bin/cherry</code>. To create that file, type:	+
-		+
-	~~touch ~/.cherry_state~~	+
-		+
-	~~Before you first boot into PR1.2, it is probably best to remove your SIM anyway, just in case something went wrong and <code>/usr/bin/cherry</code> still ran.~~	+
-		+
-	If your upgrade method to PR1.2 involved flashing eMMC, this will mean that you cannot create the <code>/home/user/.cherry_state</code> file before booting into PR1.2. But you can remove the SIM card, boot and create the file. Then you are free to reboot with the SIM card in and it should not subscribe you.	+
-		+
-	~~Cherry will tell the CSD daemon, through CSD's libcsd-sms.so module, to send the SMS directly, bypassing Telepathy and RTCOMM.~~	+
-		+
-	Before you put a SIM back in, check to see if there are any files in <code>/var/spool/sms/outgoing</code> and check to see if <code>/var/spool/sms/regs_out.txt</code> contains an entry. If you haven't sent any other SMSes, it's a safe bet that this message scheduled to go out is the one produced by Cherry. Removing the file in <code>/var/spool/sms/outgoing</code> and the entry from regs_out.txt is safe, but make a backup just in case.	+

	[[Category:N900]]		[[Category:N900]]
	[[Category:Users]]		[[Category:Users]]