Databases
StackOverflow2013
Postsdbo
POAndroid Settings LocalePicker on Honeycomb
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid Settings LocalePicker on Honeycomb
    primarykey
    data
    text
    <p>I am implementing an app that uses the native language settings which can be accessed from: Menu > Settings > Language &amp; Keyboard > Select Language > Locale</p> <p>I can also open the Locale page directly using an intent which lists the languages by using the following code:</p> <pre><code>Intent languageIntent = new Intent(Intent.ACTION_MAIN); languageIntent.setClassName("com.android.settings", "com.android.settings.LocalePicker"); activity.startActivity(languageIntent); </code></pre> <p>^-- code credit: <a href="https://stackoverflow.com/questions/2596352/android-change-language-settings-locale-for-the-device/2596497#2596497">Change language settings (locale) for the device</a></p> <p>This works great on versions before Honeycomb. However the settings for Honeycomb has the little navigation area off to the left, like so: </p> <p><img src="https://i.stack.imgur.com/o8Kg7.png" alt="Image"></p> <p>and when i execute the above code I get this error:</p> <pre><code>Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.LocalePicker } from pid 24294 FATAL EXCEPTION: main android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings/com.android.settings.LocalePicker}; have you declared this activity in your AndroidManifest.xml? </code></pre> <p>Any idea why this is happening? If i change "com.android.settings.LocalePicker" to "com.android.settings.Settings" it will open up the settings page to whatever setting you had last selected but if i try to change the classname to something like: "com.android.settings.Settings.LocalePicker" it blows up again. Here is some modified code which I'm using until this issue is resolved:</p> <pre><code>Intent languageIntent = new Intent(Intent.ACTION_MAIN); int currentApiVersion = android.os.Build.VERSION.SDK_INT; final int HONEYCOMB = 11; if (currentApiVersion &lt; HONEYCOMB) // "HONEYCOMB" should be replaced with android.os.Build.VERSION_CODES.HONEYCOMB, but version code 'honeycomb' is not supported... { languageIntent.setClassName("com.android.settings", "com.android.settings.LocalePicker"); } else { languageIntent.setClassName("com.android.settings", "com.android.settings.Settings"); } activity.startActivityForResult(languageIntent, WtgActivity.LANGUAGE_CHANGE_REQUEST); </code></pre> <p>Running code that does something different based on version number is not ideal, so if anyone knows how to fix this i would appreciate it.</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USaveyD
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid Settings LocalePicker on Honeycomb
      1. USkmlzkma
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid Settings LocalePicker on Honeycomb
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAlso, a separate question (which i may post as a new question) does anyone know how to install a new language or if it is part of the firmware and can only be changed by hacking or using modded firmware?
      singulars
      1. POAndroid Settings LocalePicker on Honeycomb
      1. USaveyD
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload