Jump to content


Photo

Tweaking the 1st OS release

- - - - -

  • Please log in to reply
1 reply to this topic

#1
tsh

tsh

    Newbie

  • Members
  • Pip
  • 46 posts
  • Devices:HTC Desire, AC100, Folio 100
Theory
Some of the installed apps are force-closing even out of the box, indicating the base ROM image is badly configured. Archiving and re-installing these seems to improve responsiveness. Do not try and prevent apps from being auto-loaded using a startup manager. The problem is with the application installation, not that the apps are draining the system.

Fix
The procedure goes like this:

Install systempanel (you will need access to an android phone, an emulator, or search for the APK and install it). Other tools may work as well, but that is the one I am familiar with. SystemPanel will archive itself onto SD, from where you can copy it to the Folio, browse to where it is with the toshiba file manager and install it.
Load System panel, select 'menu, installer'. This will show you all of the installed applications. Make a list of them all, then work through the list doing the following:
  • Select the app in the list to get more details.
  • Select 'archive' and check it has backed up the app. Skip any which are copy protected and can't be backed up.
  • Un-install the app.
  • Re-install the app. Move onto the next.
This will require you to enter any setup information again for each app, and to re-configure things like the supplied keyboard app, but it will make sure that any directories and configuration required is installed properly.

Running apps full-screen
You can use the 'spare parts' app to change the 'compatibility mode' for old applications which do not run full-screen. You will find this option near the bottom of the list on the front page of spare parts. The tick-box needs to be not ticked. It is 10th item down on the menu, under 'general'. You do need to reboot after un-ticking the box. Oddly, spare parts will FC on a HTC desire, but can still be sideloaded on the folio from the desire.

  • 0

#2
Vernice42

Vernice42

    Newbie

  • Members
  • Pip
  • 3 posts
Hi

just an interesting comparison on release designations allthe recent phone platforms with two major platforms for comparison



It shows why calling something a major or minor release isgenerally an exercise in confusion and why people are often wrong.







iOS had had 5 major releases per a recent Apple keynote, anumber of minor .x releases and a bunch of maintenance releases. the iPad 3.2release is not deemed major by Apple but I'd say it's more than minor. Maybe inbetween somewhere.



Android has had 5 major releases (1.0, 1.5, 2.0, 3.0, 4.0)and 7 lower .x release They don't necessarily call a .1 bump a minor releasesuch as 3.2. Google has called them three different things in the past.

source: http://developer.android.com/sdk/

They don't say what they all are so I'm assuming unlessotherwise proven that a .x release is a minor release.



WebOS is on it's 3rd major release



Windows Phone 7 is on it's second major release, 7.5



Blackberry makes things confusing. They're going from 7.0 to10.0 and that version has never matched their platform version. BB OS 6.0 wasplatform 4.x.


  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users