RipText Android Upgrade

Upgrade to existing RIPText project: Bugs 1. This is a very serious problem affecting some of our users. The application always has to be forced closed a couple of seconds after opening it. It'll show a blank screen before crashing. Happening on several versions of Android, from 2.x.x to 4.x.x. Has only occurred on phones where contacts have been added, and text messages received, prior to installation. Doesn't happen to all phones in this state though. After a factory data reset and restoring the contacts it can be opened but the problem has sometimes reappeared later on. 2. From our experience on all versions of Android >= 2.2, Ringer volume is set to full when the application is opened, the screen is rotated, or user navigates back to the conversation list view. 3. The screen doesn't rotate when viewing a message. It only rotates in the conversation list view. Modifications 1. We would like to support 2 types of accounts in the application. Currently we authenticate by phone number, which we can call a '2020tel Account'. We would also like to authenticate by username/password, which we can call a 'Prepaid Account'. A user can only use one type of account at a time. To support this, the application will need a new 'Account Options' view, where the type of account can be chosen and setup. Additionally, if the user is sending a message with a 'Prepaid Account', the application will need to send 'username' and 'password' parameters in the request to '[login to view URL]'. The 'Account Options' view needs to display 'Create Account' or 'Manage Account' (depending on whether username/password has been previously saved) buttons that launch URLs if it is a 'Prepaid Account' as well. 2. On first run could the user be shown the proposed 'Account Options' view. They shouldn't be able to use the application until they setup their account. 3. Does the Android API allow access to the user's phone number? If so, could it be stored automatically in the configuration so users don't have to enter it themselves manually. If not, could the 'Your phone number' view validate phone numbers such that it will show an error message if the input number isn't in the format [countrycode][phone number], e.g. '34654321098', where '34' is the country code for Spain, and '654321098' is the phone number. 4. We would like users to receive delivery reports when a message can't be sent. We can setup a PHP script ourselves that the app could poll for delivery reports. The app can include the user's phone number as a request parameter, and we can respond with a result code. We can agree on the specifics of this at a later time. 5. Could the title of the application be changed to 'RIP Text'. So, could we replace all visual instances of 'RIPText' to 'RIP Text'. 6. In the application menu, could 'Compose Option', 'Notification Option', and 'Sending Option' be renamed to 'Compose Options', 'Notification Options', and 'Sending Options'. 7. Could we have a font size option. At the moment on higher resolution screens it can be difficult to read text. 8. Could the height of textbox for entering the reply be increased? Making the header (RIPText logo, contact details, phone button) scrollable would give us much more available space to do that. 9. Could the message padding in conversation view be decreased. This is the view where you can see your SMS conversation with a contact.