<issue_start>username_0: Does anyone know if Samsung Galaxy S GT-I9000's camera taken photos keep information about GPS location from when they were taken?

Thank you<issue_comment>username_1: It can if you turn the function on in the settings. In the settings menu there's an option for "GPS", that when checked turns on [geotagging](http://en.wikipedia.org/wiki/Geotagging):

![enter image description here](https://i.stack.imgur.com/BMnxi.png)

*via [GSM Arena](http://www.gsmarena.com/samsung_i9000_galaxy_s-review-478p6.php) & [CareAce](http://www.gsmarena.com/samsung_i9000_galaxy_s-review-478p6.php)*
Upvotes: 4 [selected_answer]<issue_comment>username_2: I just did a reset of all camera settings and the geotagging disappeared. Since this is what I wanted, I'm happy. When I bought it it was off (I think) and it got turned on sometime last month.
Upvotes: -1 <issue_comment>username_3: There is no setting in the camera phone for GPS on my Galaxy S GT19000.

I disabled everything in `Settings > location and security`. It was still geotagging my photos, and I couldn't work out how it was doing that. But if you go to `applications > local`, it was here for me. Just visit the `Settings` section.

Nasty.
Upvotes: 1


<issue_start>username_0: Is there a technical reason for why apps that only need their own data are not limited to one folder? I do realise that some apps use other apps' data, but I'd be much more likely to install an app that only asked for permission to store files in one, specific folder.<issue_comment>username_1: SD cards generally use the FAT file system, which does not allow for filesystem permissions. This means that the Android OS would have to manage a custom list of files, their permissions, a mapping of apps to files/folders, etc. in order to prevent apps from accessing the whole card. This would be a terrible mess. Not only complicated, but it would require a lot of storage space. And then one day you take out your SD card and remove some pictures, and the entire system breaks. You get the idea.
Upvotes: 3 <issue_comment>username_2: There are different mechanisms to store data in an Android application that don't need the SD card access permission. You can create databases, store application parameters, create files on the internal storage. All these will not require any specific permissions and these data are accessible only by the application that created them.

On the other side, if an application needs the SD card permission it may be because it as a very large amount of data to store or that it wants to modify/add/remove files such as in a file manager. But for important application specific data, the SD card if not recommended because it could be removed at anytime (or mounted as a USB drive) and not available to the applications.

I think a lot of applications that ask SD access permission could use another type of data storage that would not require that. Moreover, files created on the SD by an app will not be removed upon un-installation of the app but all other types of internal data storage will be. So to me it would be a better development practice not to use the SD if not required, and as you mentioned it would not scare people away like apps that access the whole SD.
Upvotes: 2 [selected_answer]<issue_comment>username_3: As username_1 has explained, with a normal SD card using the FAT file system, it's not possible to use the file permissions to control apps' access, the same way that Android controls their access to files on the internal filesystem. But now that Android phones use internal storage instead of SD cards, and they use MTP to offer access over USB instead of the mass storage device class, Android phones are free to use better filesystems for their large data storage.

KitKat added a new mechanism for apps to store large files. In the internal USB storage, each app gets a private data directory, just like in the smaller device memory. (On some devices, these might even be the very same filesystem.) Apps can access their private directory on this filesystem without needing any special permissions. It's also now possible for apps to only ask for the "read SD card" and "write SD card" permission on versions of Android prior to KitKat, if they only need the SD card in order to use a private directory like this.

The old shared directories like "Downloads", "Music", and "Notifications" are still present just like before, and still need those same permissions for access. Old apps that haven't been updated for KitKat will still use those directories, not the new, private directories.
Upvotes: 0


<issue_start>username_0: I was attracted by the hardware specifications of the Samsung Galaxy S.

However, I don't like the default TouchWiz skin developed by Samsung. I'd prefer to use the native Android UI, as in the Nexus S and similar devices.

Is it possible for me to perform "self installation" of the stock Android OS, after I bought the Samsung Galaxy S? If yes, how? Will I void the warranty of my phone by doing this?<issue_comment>username_1: I'm not familiar with the Samsung Galaxy, but in general if you want to install an aftermarket OS you need to root your phone and in general rooting your phone will void the warranty.

Do you have other reasons for wanting to change the OS or is it really just TouchWiz?

According to [this XDA post](http://forum.xda-developers.com/showpost.php?p=12269276&postcount=2), the only TouchWiz-free ROM is CyanogenMod. It's very unstable on the Galaxy S though.

However, you can install a different launcher such as LauncherPro. TouchWiz will still be on the phone, but just in the background, so you can have a more "stock Android" experience by using another launcher.

I hope I've answered your intial question. Don't hesitate to ask new questions about how to go about disabling TouchWiz if you do opt to go that route.
Upvotes: 4 [selected_answer]<issue_comment>username_2: In order to replace the OS there are a few steps that must be taken. I do not have a Samsung Galaxy S phone nor do I know how locked down it is. At this time, I do know that the SGS is not available on CyanogenMod yet (popular stock-ish Android OS rom).

In general, the steps for any phone would be:

1. Root the phone (varies by phone)
2. Download ROM Manager
3. Flash a recovery such as Clockwork Recovery
4. Make a backup of the phone's original ROM with Nandroid
5. Use ROM Manager to download a Rom, such a CyanogenMod
6. Flash the ROM with ROM Manager.

Some phones it is not possible to flash a rom because of a locked bootloader. Most Motorola Droid phones except for the original Droid and Xoom have this problem. However, as already mentioned, you can still replace the home launcher with another such as LauncherPro, ADW or numerous others.
Upvotes: 0 <issue_comment>username_3: Yes, flashing a custom ROM will void your warranty. However, it is very simple to revert to the stock ROM with a Galaxy S for warranty purposes. Rooting will also void your warranty, but the method below does not require root.

The easiest way to a get a new OS for a Galaxy S is to use Odin for Windows (download [here](http://forum.xda-developers.com/showpost.php?p=9088113&postcount=1). Search for "Heimdall" if you want to do this on Linux). You just need an Odin-flashable ROM. For the Galaxy S Vibrant, I highly recommend the ROM I currently use, [Bionix v1.3.1](http://forum.xda-developers.com/showthread.php?t=925548), which has a TouchWiz-free version. I assume you have a GT-I9000 however; you should look for one that suits your purposes in [XDA's i9000 Android Development forum](http://forum.xda-developers.com/forumdisplay.php?f=665).

**Edit:** According to [this post](http://forum.xda-developers.com/showpost.php?p=12269276&postcount=2), the only completely TouchWiz-free ROM is CyanogenMod, which is unstable/buggy. So if you don't want CM and just want to replace the launcher, you can do that without flashing another ROM as username_1 says in her answer. Otherwise you can continue with the instructions below for using Odin.

Once you have the ROM, do the following:

1. [Put your phone into Download mode](http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Download_Mode)
	1. Remove the battery
	2. If non-i9000, attach the phone to your PC via USB.
	3. Hold VolumeDown plus either the Home key (i9000) or VolumeUp (non-i9000) and the power button
		1. Reinsert the battery.
		2. Let go of the power button only about 1 second after the white device logo appears (if it does)
		3. After a few seconds a yellow triangle with an android in it should appear, you can let go of the keys since this is download mode.
2. Start up Odin.
3. If non-i9000, detatch your phone from USB.
4. Attach the phone to USB so that Odin recognizes it.
5. Load the .zip file you downloaded (the custom ROM) into the PDA field of Odin.
6. Load the 512 .pit file into the PIT field of Odin.
7. Check "Re-partition".
8. Hit Start. Odin will tell you when it's done; if it fails, reboot your phone and try again. (This happens occasionally).

Note that if you need to back anything up, you should do that beforehand and save the backup to your PC, since everything (except probably the external SD card) will be wiped on the phone. Also note that you do this at your own risk; Odin is very powerful and misusing it can damage your phone. I've used it dozens of times myself safely.
Upvotes: 3 <issue_comment>username_4: **Quick answer:** Yes it is possible to get a nearly stock Android on your Galaxy S.

I just flashed Gingerbread to my Galaxy S last week or so.

You can find any relevant information here:
<http://forum.cyanogenmod.com/topic/17020-all-models-cyanogenmod-7-for-samsung-galaxy-s-phones-experimental/>

Contrary to what is written in the first post I'd actually say that it is already pretty stable for a ROM which is described as 'experimental'.
Since I installed it I cannot remember of any system crash or similar. (Which doesn't mean that It won't destroy **your** phone.)

There are some missing features/bugs though.
Notably: radio, frontfacing camera.

Another funny bug is that your data connection only works after you lock & unlock your phone. (You have to do this once it boots so it's not a big deal.)

And oh, Gingerbread is awesome.

Edit: If you are on Linux you can use Heimdall instead of Odin.
Upvotes: 1


<issue_start>username_0: my HTC Wildfire with CM7 - RC4, doesn't like a combination of two things:

* Data enabled on a 2G Network
* SD Card inserted.

When these two conditions are met, either the phone will slow down to a halt or it will reboot. If it reboots, if I don't remove the SD card it will not detect it, unless I reboot without it in. Or, the SD card will just be undetected and sometimes a notifications pops up telling me "SD Card Removed Unexpectedly"

At my school, my phone network's signal isn't very good due to the building being rubbish and 2G signals are the only thing we get inside the building.

On my old SD card it was 4GB and I think it worked, however my SD card is now 16GB and it doesn't like this. It shouldn't be a problem as it's a ScanDisk (a very reputable make) and I've tried another 16GB card which I sent back due to the issue, so I don't think it's that.

Many thanks to people who can figure out what's up with my phone,

Joe<issue_comment>username_1: I would indeed verify first that this is not related to some 3rd party app or any other than stock ROM. For this do a complete reset and try again. Also try with a smaller SD card since 16GB might not be supported by your phone (need to check specs for that, I don't know).

You can make a backup to get it back to your personalized settings quick.

If you can confirm the stock ROM and default settings do have this bug too you can report this to HTC. Otherwise you'll have to solve it on your own, looking what app/setting is getting this result.
Upvotes: 2 <issue_comment>username_2: Scandisk? you sure? Did you mean SanDisk?

Can you absolutely vouch for the authenticity of the SD card? There are plenty of 'fakes' - usually low grade/slow branded as faster cards.

Theres a good guide to spotting fakes here [eBay guide](http://reviews.ebay.co.uk/FAKE-SanDisk-Ultra-Secure-Digital-Cards-Exposed_W0QQugidZ10000000001254881)
Upvotes: 0 <issue_comment>username_3: I had exactly the same issue here, on my Asus fonepad tablet.
It happened from the beginning, with few 3rd party apps installed and different SD cards.

My workaround was to set "WCDMA only" in the settings ;)
Upvotes: 0


<issue_start>username_0: Anyone have an Acer A500 (just got mine today) and have luck with bluetooth network tethering.
I've got an OG Droid, so WiFi is not a possibility at the moment.
Tried the directions here: <http://www.droid-life.com/2011/03/01/how-to-bluetooth-tether-to-motorola-xoom-using-original-droid/>

but had no luck. I realize that those are for the XOOM, but I was hoping it would be the same since they both run stock honeycomb. I got as far as pairing the devices, but when I click on the droid device on the A500 it shows nothing under profiles, where it should show Tethering.

would really like to be able to tether with this until I get a new phone<issue_comment>username_1: The user guide for A500 says bluetooth only supports mikeless head phones. I'm, miffed too.
Upvotes: 1 <issue_comment>username_2: Have an A500, droid1, and here is how I got WiFi tether to work.

Root the phone, root the a500. Install RootExplorer for the a500 and <http://code.google.com/p/android-wifi-tether/> for the phone.

Replace the WPA supplicant file as per these instructions: <http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/4016-how-enable-ad-hoc-wi-fi-connection.html> (I know it's for the xoom, but I have it running on my a500 and it works fine).

Turn on the wifi (not the bluetooth) tether on the phone, and you should see it available on the a500 (given you replaced the supplicant, as above).

I know it's not Bluetooth, but the stack doesn't expose ad-hoc bluetooth networking as of this release. This was you can get SOMETHING going. Enjoy!

J3
Upvotes: 0 <issue_comment>username_3: Try the [PDAnet Tablet app](https://market.android.com/details?id=com.pdanet.tablet), it's in beta but might work with the Acer A500.
Upvotes: 0


<issue_start>username_0: My current situation is this: I use Mac OS X at home and Ubuntu Linux at work. My phone is a Samsung Galaxy S. Whenever I want to update my firmware *the intended way (i.e. using Kies, I am aware of Odin)*, I have to boot into an old Windows XP installation that I have lying around.

I was wondering if there is a handset manufacturer that embraces Linux. The Samsung phone seems to be just the wrongest choice I could have made with the windows-centric Kies software.

**Edit**: I should probably point out, that I live in Germany and I want to use a prepaid phone service without contract. Also, I am looking for a great "out-of-the-box" experience without too much hackery (i.e. without voiding the warranty).

**Edit2**: I was hoping to learn about brands which support Linux (like NVidia does with their proprietary drivers) or maybe learn about tools and techniques:

* Heimdall is a nice tool, but I don't feel that it has Samsungs approval, and I feel that using it might void the warranty.
* Over-The-Air Updates is something, that seems to be useful, but it won't work for me, as I don't have a contract with a cell phone provider. (*Edit 3:* This line is just non-sense, I receive OTA updates over wi-fi.)

Therefore I am still looking for some enlightenment about which direction I should go with my next phone.

**Edit 3:** After my recent purchase of the Samsung Galaxy S3 (I know... fool me once...), I would like to reopen the issue. My setup (except for the phone) is still the same (Mac OS X at home and Ubuntu Linux at home and at work).

In order to access the file system I either connect to an Ubuntu machine via USB. This is not ideal, because the drive size of the external sd card is not reported correctly, which makes me a little less confident in this solution.

On the Mac, I can only get iPhoto recognize the device in PTP mode. [Android file transfer](http://www.android.com/filetransfer/) does not recognize the device after the latest OTA firmware update.

As an alternative to the USB connection, I found [DigiSSHD](https://play.google.com/store/apps/details?id=org.digimead.digi.ctrl.sshd&hl=en) as a workaround to transfer files wirelessly.

After spending hours of looking for a better solution and adjusting my workflow to workarounds, I would like to ask again: **Is there a there a handset manufacturer that embraces Linux and provides native tools to interact with the device?**

I don't mind if the tool is proprietary or free as long as it works.<issue_comment>username_1: I don't know of a Kies alternative, but there is [Heimdall](http://www.glassechidna.com.au/products/heimdall/), an Open Source, Cross Platform, Odin alternative.
Upvotes: 3 <issue_comment>username_2: If you don't want to be tied to Windows-based Kies, Simply don't pick Samsung phones. Almost every other Android manufacturer's phones can be upgraded Over The Air without the need of an attached computer; for some reason Samsung's can't or won't do it.

Android was designed so it does not need to be attached to a computer as much as possible; Android was designed to sync data (address book, etc), installs software (market, etc), and do system updates over the air. Some manufacturer/carriers do not yet embrace this unfortunately, and is forcing your phone to be attached to a computer.
Upvotes: 3 <issue_comment>username_3: OTA updates are a better solution. Not sure why Samsung sticks to some update utility while many other manufacturers use OTA update. HTC does OTA on my Hero and now on my Desire Z also. My Acer beTouch 130e required a utility. Not sure for other brands.
Upvotes: 1 <issue_comment>username_4: I think that the linux support not only depends on the manufacturer.

In the case of the *Palms*, PalmOne only released desktop applications for Windows and Mac, but despite of that fact the linux community developed solutions like J-Pilot for example.
Upvotes: 2


<issue_start>username_0: Is there a way to list all Intents and all processes associated with them?

Specifics: Droid X, 2.2 stock ROM, rooted.

I'm perfectly fine with any approach, as long as it gets a guaranteed **complete** list:

* A script or a series of commands in Terminal Emulator is fine. No limitation on supposed required technical proficiency (assume that the reader is a qualified long-term Unix power user). As noted, the phone is rooted.
* An app is OK (ideally, it should be able to export the list, but even Autostarts-like GUI display is OK)

Caveat: if you recommend an app (e.g. [Autostarts](https://market.android.com/details?id=com.elsdoerfer.android.autostarts)), I would request some assurance that it does, indeed, list **all** registered Intent receivers, not merely some sub-set - either as documentation/statement from the author or some other evidence (e.g. analysis of which APIs the code uses).
* Worst case scenario, I'll take an API specifics<issue_comment>username_1: According to several [other](https://stackoverflow.com/questions/4619479/list-intent-filters-for-installed-packages) [similar](https://stackoverflow.com/questions/3011454/listing-an-applications-activity-and-intent-filters) [questions](https://stackoverflow.com/questions/4094109/android-how-to-i-get-a-list-of-all-available-intent-filters) on stackoverflow, such a list is not available via APIs.

I'm not sure how apps like [Tasker](https://market.android.com/details?id=net.dinglisch.android.taskerm) produce such lists. I wouldn't rule out iterating through all possible intents via the [queryIntentActivities()](http://developer.android.com/reference/android/content/pm/PackageManager.html#queryIntentActivities%28android.content.Intent,%20int%29) function, or even parsing each installed app's manifest file.
Upvotes: 2 <issue_comment>username_2: Autostarts parses the application manifests. That's really the best way.

(There is a seemingly auto-generated broadcast\_actions.txt file shipped with the Android SDK, but it's not complete, in my experience).

Depending on what is wanted, you need to consider:

* That apps can broadcast custom events, and other apps may listen to those custom events.
* That apps can register themselves to receive events at runtime, as opposed to statically in the manifest. Autostarts will not list those, and I am not aware that such temporary registrations are exposed in any way.
* Autostarts only lists broadcast events. Events can also be sent directly to specific activities of specific applications. Autostarts will not list those, but the information can be found in the manifests.

You can also look at /data/system/packages.xml on your phone, which is where the PackageManager services caches information about installed packages (so it doesn't have to parse the Manifests). I don't remember if it contains information about intents - I vaguely remember that it might not include any application components that have been disabled, but I'm not sure.
Upvotes: 2 <issue_comment>username_3: Perhaps not all, but you can get a pretty good idea [using](https://stackoverflow.com/a/32707859/1147688):

```
dumpsys activity broadcasts |grep -iE ".+\.[0-9A-Z_\-]+:$" |sort

```

The *grep* expression makes sure to only catch lines ending in the intent like format of `...blahblah.SOME_INTENT:`. I then use *sort* to get it more readable. It may not catch all, but it's a good start.

```
    SIDESYNC.action.CTRL_PRESSED_STATE_EVENT:
    SIDESYNC.action.EXIST_TEXT_BEFORE_CURSOR_STATE_EVENT:
    SIDESYNC.action.INPUT_TEXT_EVENT:
    SIDESYNC.action.PREDICTIVE_TEXT_EVENT:
    SIDESYNC.action.SHIFT_PRESSED_STATE_EVENT:
    SamsungIME.UpdateAvailableLanguageAction:
    android.accounts.LOGIN_ACCOUNTS_CHANGED:
    android.app.action.DEVICE_POLICY_MANAGER_PASSWORD_CHANGED:
    android.app.action.DEVICE_POLICY_MANAGER_STATE_CHANGED:
    android.app.action.ENTER_CAR_MODE:
    android.app.action.ENTER_DESK_MODE:
    android.app.action.EXIT_CAR_MODE:
    android.app.action.EXIT_DESK_MODE:
    android.app.backup.intent.INIT:
    android.app.backup.intent.RUN:
    android.app.enterprise.action.ACTION_WIFI_POLICY_STATE_CHANGED:
    android.appwidget.action.APPWIDGET_INVALID_HOST_CALLBACKS:
    android.bluetooth.a2dp.profile.action.CONNECTION_STATE_CHANGED:
    android.bluetooth.adapter.action.CONNECTION_STATE_CHANGED:
    android.bluetooth.adapter.action.DISCOVERY_FINISHED:
    android.bluetooth.adapter.action.LOCAL_NAME_CHANGED:
    android.bluetooth.adapter.action.STATE_CHANGED:
    android.bluetooth.device.action.ACL_CONNECTED:
    android.bluetooth.device.action.ACL_DISCONNECTED:
    android.bluetooth.device.action.ACTION_IN_RANGE_ALERT:
    android.bluetooth.device.action.ACTION_OUT_OF_RANGE_ALERT:
    android.bluetooth.device.action.ALIAS_CHANGED:
    android.bluetooth.device.action.AUTO_LOCK_SERVICE:
    android.bluetooth.device.action.BOND_STATE_CHANGED:
    android.bluetooth.device.action.CLASS_CHANGED:
    android.bluetooth.device.action.RSSI:
    android.bluetooth.headset.profile.action.AUDIO_STATE_CHANGED:
    android.bluetooth.headset.profile.action.CONNECTION_STATE_CHANGED:
    android.bluetooth.input.profile.action.CONNECTION_STATE_CHANGED:
    android.content.syncmanager.SYNC_ALARM:
    android.dirEncryption.DirEncryptionManager.UNMOUNT_POLICY:
    android.hardware.display.action.WIFI_DISPLAY_STATUS_CHANGED:
    android.hardware.usb.action.USB_DEVICE_ATTACHED:
    android.hardware.usb.action.USB_DEVICE_DETACHED:
    android.hardware.usb.action.USB_STATE:
    android.intent.action.ACTIONMEMOFILEPATHFORLOG:
    android.intent.action.ACTION_CLOSE_DIALOG_DATA_ROAMING_GUARD:
    android.intent.action.ACTION_POWER_CONNECTED:
    android.intent.action.ACTION_POWER_DISCONNECTED:
    android.intent.action.ACTION_SHOW_DIALOG_DATA_ROAMING_GUARD:
    android.intent.action.ACTION_SHUTDOWN:
    android.intent.action.AIRPLANE_MODE:
    android.intent.action.ALARM_CHANGED:
    android.intent.action.ANY_DATA_STATE:
    android.intent.action.AT_CMSS_COMPLETE:
    android.intent.action.BADGE_COUNT_UPDATE:
    android.intent.action.BATTERY_CHANGED:
    android.intent.action.BATTERY_LOW:
    android.intent.action.BATTERY_OKAY:
    android.intent.action.BCS_REQUEST:
    android.intent.action.BOOT_COMPLETED:
    android.intent.action.CHAMELEON_PRECONFIG:
    android.intent.action.CHECK_COOLDOWN_LEVEL:
    android.intent.action.CHECK_SIOP_LEVEL:
    android.intent.action.CLOSE_SYSTEM_DIALOGS:
    android.intent.action.COEX_INFO:
    android.intent.action.CONFIGURATION_CHANGED:
    android.intent.action.CSC_CHAMELEON_UPDATE_CALL_SETTINGS:
    android.intent.action.CSC_UPDATE_NETWORK_DONE:
    android.intent.action.CSC_WIFI_DEFAULTAP_DONE:
    android.intent.action.CSC_WIFI_GENERALINFO_DONE:
    android.intent.action.CUSTOMER_TEST_RESPONSE:
    android.intent.action.DATA_CONNECTION_CONNECTED_TO_PROVISIONING_APN:
    android.intent.action.DATA_CONNECTION_FAILED:
    android.intent.action.DATE_CHANGED:
    android.intent.action.DB_CLEAN:
    android.intent.action.DEFAULT_CS_SIM_CHANGED:
    android.intent.action.DEVICE_STORAGE_FULL:
    android.intent.action.DEVICE_STORAGE_LOW:
    android.intent.action.DEVICE_STORAGE_NOT_FULL:
    android.intent.action.DEVICE_STORAGE_OK:
    android.intent.action.DOCK_EVENT:
    android.intent.action.DORMANT_MODE_OFF:
    android.intent.action.DORMANT_MODE_ON:
    android.intent.action.DORMANT_MODE_UPDATE:
    android.intent.action.DOWNLOAD_COMPLETE:
    android.intent.action.DREAMING_STARTED:
    android.intent.action.DREAMING_STOPPED:
    android.intent.action.DROPBOX_ENTRY_ADDED:
    android.intent.action.EMERGENCY_CALLBACK_MODE_CHANGED:
    android.intent.action.EMERGENCY_START_SERVICE_BY_ORDER:
    android.intent.action.EMERGENCY_STATE_CHANGED:
    android.intent.action.EXTERNAL_APPLICATIONS_AVAILABLE:
    android.intent.action.EXTERNAL_APPLICATIONS_UNAVAILABLE:
    android.intent.action.EXTERNAL_CAR_CONNECTED:
    android.intent.action.EXTERNAL_CAR_DISCONNECTED:
    android.intent.action.EXTERNAL_USB_HEADSET_PLUG:
    android.intent.action.FLATMOTION_CP:
    android.intent.action.GCF_DEVICE_STORAGE_LOW:
    android.intent.action.GCF_DEVICE_STORAGE_OK:
    android.intent.action.GRIPSENSOR_CP:
    android.intent.action.HDMI_PLUGGED:
    android.intent.action.HEADSET_PLUG:
    android.intent.action.LOCALE_CHANGED:
    android.intent.action.LTE_SMS_STATUS:
    android.intent.action.MASTER_CLEAR_NOTIFICATION:
    android.intent.action.MEDIA_BUTTON:
    android.intent.action.MEDIA_MOUNTED:
    android.intent.action.MEDIA_REMOVED:
    android.intent.action.NETWORK_SET_TIME:
    android.intent.action.NETWORK_SET_TIMEZONE:
    android.intent.action.NOT_ALLOWED_SCREEN_MIRRORING:
    android.intent.action.PACKAGE_ADDED:
    android.intent.action.PACKAGE_REMOVED:
    android.intent.action.PALM_DOWN:
    android.intent.action.PDP_RESET_TEST:
    android.intent.action.PHONE_STATE:
    android.intent.action.PROXIMITY_CP:
    android.intent.action.PROXY_CHANGE:
    android.intent.action.RADIO_TECHNOLOGY:
    android.intent.action.REBOOT:
    android.intent.action.REQUEST_HOME_COUNT:
    android.intent.action.REQUEST_WIDGET_COUNT:
    android.intent.action.SARDEVICE_CP:
    android.intent.action.SB_HIDE_DIALOG:
    android.intent.action.SB_SHOW_DIALOG:
    android.intent.action.SCREENRECORDER_INFORMATION:
    android.intent.action.SCREEN_OFF:
    android.intent.action.SCREEN_ON:
    android.intent.action.SECURE_PLAYBACK_START:
    android.intent.action.SECURE_PLAYBACK_STOP:
    android.intent.action.SERVICE_STATE:
    android.intent.action.SETTINGS_SOFT_RESET:
    android.intent.action.SET_WIFI:
    android.intent.action.SHOW_BRIGHTNESS_DIALOG:
    android.intent.action.SIM_STATE_CHANGED:
    android.intent.action.SIOP_LEVEL_CHANGED:
    android.intent.action.START_FACTORY_TEST:
    android.intent.action.START_NETWORK_BOOSTER:
    android.intent.action.STOP_FACTORY_TEST:
    android.intent.action.STOP_NETWORK_BOOSTER:
    android.intent.action.SWEEP_DOWN:
    android.intent.action.SWEEP_LEFT:
    android.intent.action.SWEEP_RIGHT:
    android.intent.action.SYNC_STATE_CHANGED:
    android.intent.action.TIMEZONE_CHANGED:
    android.intent.action.TIME_SET:
    android.intent.action.TIME_TICK:
    android.intent.action.TURNOVERMOTION_CP:
    android.intent.action.UID_REMOVED:
    android.intent.action.USBHID_KEYBOARD_EVENT:
    android.intent.action.USBHID_MOUSE_EVENT:
    android.intent.action.USB_AUDIO_ACCESSORY_PLUG:
    android.intent.action.USB_AUDIO_DEVICE_PLUG:
    android.intent.action.USB_CHARGING:
    android.intent.action.USER_ADDED:
    android.intent.action.USER_BACKGROUND:
    android.intent.action.USER_FOREGROUND:
    android.intent.action.USER_INFO_CHANGED:
    android.intent.action.USER_PRESENT:
    android.intent.action.USER_REMOVED:
    android.intent.action.USER_STARTED:
    android.intent.action.USER_STARTING:
    android.intent.action.USER_STOPPED:
    android.intent.action.USER_STOPPING:
    android.intent.action.USER_SWITCHED:
    android.intent.action.VIDEO_PLAYBACK_STOP:
    android.intent.action.WAITING_AUTO_LOGIN:
    android.intent.action.WB_AMR:
    android.intent.action.WIFIDISPLAY_NOTI_CONNECTION_MODE:
    android.intent.action.WIFI_DISPLAY:
    android.intent.action.WIFI_DISPLAY_SINK_STATE:
    android.intent.action.WIFI_DISPLAY_URL_FROM_NATIVE:
    android.intent.action.proximity_sensor:
    android.intent.action.sec.LSO_CONFIG_CHANGED:
    android.intent.action.sec.MDM_ACCOUNT_DELETE_RESULT:
    android.intent.action.sec.MDM_ACCOUNT_SETUP_RESULT:
    android.intent.action.stk.check_screen_idle:
    android.intent.action.stk.idle_screen:
    android.location.GPS_ENABLED_CHANGE:
    android.location.GPS_FIX_CHANGE:
    android.location.MODE_CHANGED:
    android.location.PROVIDERS_CHANGED:
    android.media.RINGER_MODE_CHANGED:
    android.media.VOLUME_CHANGED_ACTION:
    android.mtp.MtpClient.action.USB_PERMISSION:
    android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED:
    android.net.conn.BACKGROUND_DATA_SETTING_CHANGED:
    android.net.conn.CONNECTIVITY_CHANGE:
    android.net.conn.CONNECTIVITY_CHANGE_IMMEDIATE:
    android.net.conn.INET_CONDITION_ACTION:
    android.net.conn.MOBILE_DATA_ENABLE_POPUP:
    android.net.conn.TETHER_STATE_CHANGED:
    android.net.proxy.PAC_REFRESH:
    android.net.wifi.CONFIGURED_NETWORKS_CHANGE:
    android.net.wifi.ERROR:
    android.net.wifi.LINK_CONFIGURATION_CHANGED:
    android.net.wifi.MAXAP_NOTI:
    android.net.wifi.NETWORK_OXYGEN_STATE_CHANGE:
    android.net.wifi.RSSI_CHANGED:
    android.net.wifi.SCAN_RESULTS:
    android.net.wifi.SEC_NOTIFICATION_CANCEL:
    android.net.wifi.SET_HOME_AP:
    android.net.wifi.SHOW_INFO_MESSAGE:
    android.net.wifi.STATE_CHANGE:
    android.net.wifi.WIFI_AP_STATE_CHANGED:
    android.net.wifi.WIFI_AP_STA_STATUS_CHANGED:
    android.net.wifi.WIFI_AP_WPS_STATE_ACTION:
    android.net.wifi.WIFI_DIALOG_CANCEL_ACTION:
    android.net.wifi.WIFI_OXYGEN_STATE_CHANGE:
    android.net.wifi.WIFI_STATE_CHANGED:
    android.net.wifi.p2p.CONNECTION_STATE_CHANGE:
    android.net.wifi.p2p.PEERS_CHANGED:
    android.net.wifi.p2p.REQUEST_STATE_CHANGE:
    android.net.wifi.p2p.STATE_CHANGED:
    android.net.wifi.p2p.STOPFIND_TIMER_EXPIRED:
    android.net.wifi.p2p.THIS_DEVICE_CHANGED:
    android.net.wifi.supplicant.CONNECTION_CHANGE:
    android.net.wifi.supplicant.STATE_CHANGE:
    android.nfc.action.ADAPTER_STATE_CHANGED:
    android.provider.Telephony.SPN_STRINGS_UPDATED:
    android.provider.Telephony.WAP_PUSH_RECEIVED:
    android.security.STORAGE_CHANGED:
    android.server.display.wfd.DISCONNECT:
    android.settings.ALL_SOUND_MUTE:
    android.settings.MONO_AUDIO_CHANGED:
    android.settings.POWERSAVING_AUTO_ENABLE:
    android.settings.POWERSAVING_CHANGED:
    android.settings.POWERSAVING_SWITCH_CHANGED:
    android.settings.PRAYMODE_PREFERENCE_CHANGED:
    android.systemui.usb.STORAGE_NOTIFICATION_CANCEL:
    android.view.volumepanel.CLICK_BUTTON1:
    android.view.volumepanel.CLICK_BUTTON2:
    application/vnd.omaloc-supl-init:
    com.android.action.SIM_REFRESH_INIT:
    com.android.deskclock.ALARM_ALERT:
    com.android.deskclock.ALARM_DONE:
    com.android.internal.location.ALARM_TIMEOUT:
    com.android.internal.location.ALARM_WAKEUP:
    com.android.internal.policy.impl.Keyguard.PCW_LOCKED:
    com.android.internal.policy.impl.Keyguard.PCW_UNLOCKED:
    com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD:
    com.android.internal.policy.impl.sec.UserActivityByShortcut:
    com.android.internal.telephony.cdma.intent.action.TTY_ENABLED_CHANGE:
    com.android.internal.telephony.data-reconnect.bip:
    com.android.internal.telephony.data-reconnect.cbs:
    com.android.internal.telephony.data-reconnect.default:
    com.android.internal.telephony.data-reconnect.dun:
    com.android.internal.telephony.data-reconnect.ent1:
    com.android.internal.telephony.data-reconnect.ent2:
    com.android.internal.telephony.data-reconnect.fota:
    com.android.internal.telephony.data-reconnect.hipri:
    com.android.internal.telephony.data-reconnect.ia:
    com.android.internal.telephony.data-reconnect.ims:
    com.android.internal.telephony.data-reconnect.mms:
    com.android.internal.telephony.data-reconnect.supl:
    com.android.internal.telephony.data-restart-trysetup.bip:
    com.android.internal.telephony.data-restart-trysetup.cbs:
    com.android.internal.telephony.data-restart-trysetup.default:
    com.android.internal.telephony.data-restart-trysetup.dun:
    com.android.internal.telephony.data-restart-trysetup.ent1:
    com.android.internal.telephony.data-restart-trysetup.ent2:
    com.android.internal.telephony.data-restart-trysetup.fota:
    com.android.internal.telephony.data-restart-trysetup.hipri:
    com.android.internal.telephony.data-restart-trysetup.ia:
    com.android.internal.telephony.data-restart-trysetup.ims:
    com.android.internal.telephony.data-restart-trysetup.mms:
    com.android.internal.telephony.data-restart-trysetup.supl:
    com.android.internal.telephony.data-stall:
    com.android.internal.telephony.dataconnection.DataConnection.DC-1.action_retry:
    com.android.internal.telephony.dcn_result:
    com.android.internal.telephony.provisioning_apn_alarm:
    com.android.keyguard.action.flight_mode:
    com.android.launcher.action.ACTION_HOME_RESTORE:
    com.android.launcher.action.EASY_MODE_CHANGE:
    com.android.mms.LANGUAGE_ACTION:
    com.android.mms.NOTIFICATION_CANCEL_ACTION:
    com.android.mms.NOTIFICATION_DELETED_ACTION:
    com.android.nfc.action.INTERNAL_TARGET_DESELECTED:
    com.android.phone.NATURAL_SOUND:
    com.android.phone.NOISE_REDUCTION:
    com.android.phone.action.ACTION_DATA_NOTIFICATION:
    com.android.phone.action.DISABLE_UCE_TOGGLE:
    com.android.phone.sendToCPACPlugged:
    com.android.server.ACTION_EXPIRED_PASSWORD_NOTIFICATION:
    com.android.server.BatteryService.action.DORMANT_END:
    com.android.server.BatteryService.action.DORMANT_START:
    com.android.server.IdleMaintenanceService.action.FORCE_IDLE_MAINTENANCE:
    com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE:
    com.android.server.LightsService.action.UPDATE_SVC_LED:
    com.android.server.MY_INTENT:
    com.android.server.NetworkTimeUpdateService.action.POLL:
    com.android.server.NotificationManagerService.PickupMotionArrived:
    com.android.server.PowerManagerService.action.AUTO_POWER_OFF:
    com.android.server.PowerManagerService.action.FAILED_TO_DETECT_FACE_BEFORE_DIM:
    com.android.server.WifiManager.action.DELAYED_DRIVER_STOP:
    com.android.server.WifiManager.action.DEVICE_IDLE:
    com.android.server.WifiManager.action.REFRESH_BATCHED_SCAN:
    com.android.server.WifiManager.action.START_SCAN:
    com.android.server.action.NETWORK_STATS_POLL:
    com.android.server.action.NETWORK_STATS_UPDATED:
    com.android.server.action.UPDATE_TWILIGHT_STATE:
    com.android.server.am.BROADCAST_DHA_DEBUG_ON:
    com.android.server.am.BROADCAST_DO_TRIM:
    com.android.server.am.BROADCAST_SET_TRIM_TH:
    com.android.server.connectivityservice.CONNECTED_TO_PROVISIONING_NETWORK_ACTION:
    com.android.server.enterprise.ICCID_AVAILABLE:
    com.android.server.enterprise.WFD_DISABLE:
    com.android.server.enterprise.billing.action_enable_status_modified:
    com.android.server.enterprise.billing.mapping_modified:
    com.android.server.enterprise.billing.notification_dismissed:
    com.android.server.enterprise.billing.profile_turn_on_status_modified:
    com.android.server.enterprise.billing.roaming_modified:
    com.android.server.enterprise.billing.wifi_fallback_modified:
    com.android.server.enterprise.kioskmode.REFRESH_HWKEY_CACHE:
    com.android.server.enterprise.restriction.SEND_BLOCKED_MMS:
    com.android.server.enterprise.restriction.SEND_BLOCKED_SMS:
    com.android.server.net.action.ALLOW_BACKGROUND:
    com.android.server.net.action.SNOOZE_WARNING:
    com.android.settings.DEVICE_NAME_CHANGED:
    com.android.settings.LaunchGlanceView:
    com.android.sms.action.CLEAR_ALL:
    com.android.sms.action.SWEEP_NOTIFICATION:
    com.android.sync.SYNC_CONN_STATUS_CHANGED:
    com.android.systemui.BATTERY_LEVEL_TEST:
    com.android.systemui.demo:
    com.android.systemui.power.action.ACTION_BATTERY_LOW_COCKTAIL_BUTTON:
    com.android.systemui.power.action.ACTION_BATTERY_LOW_COCKTAIL_TOUCH:
    com.android.systemui.power.action.ACTION_CLEAR_SHUTDOWN:
    com.android.systemui.power.action.ACTION_REQUEST_SHUTDOWN:
    com.android.systemui.power.action.POWER_SHARING:
    com.android.systemui.statusbar.ANIMATING:
    com.android.systemui.statusbar.COLLAPSED:
    com.android.systemui.statusbar.EXPANDED:
    com.estrongs.action.chromecast.control.close:
    com.estrongs.action.chromecast.control.disconnect:
    com.estrongs.action.chromecast.control.next:
    com.estrongs.action.chromecast.control.play:
    com.estrongs.action.chromecast.control.preview:
    com.facebook.abtest.action.CLEAR_CACHE:
    com.facebook.abtest.action.UPDATE_CACHE:
    com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM:
    com.facebook.auth.broadcast.ACTION_CLEAR_CACHE_REQUEST:
    com.facebook.backgroundlocation.settings.BackgroundLocationSettingsHandler.updated_settings:
    com.facebook.common.appstate.peers:
    com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana:
    com.facebook.common.hardware.NetworkActivityBroadcastManager.NETWORKING_ACTIVE:
    com.facebook.common.hardware.NetworkActivityBroadcastManager.NETWORKING_INACTIVE:
    com.facebook.intent.action.prod.messages.ACTION_CLEAR_ALL_MESSAGES:
    com.facebook.intent.action.prod.messages.ACTION_CLEAR_MESSAGE:
    com.facebook.intent.action.prod.messages.ACTION_NEW_MESSAGE:
    com.facebook.katana.provider.FbSharedPrefsProvider.CHANGED_ACTION:
    com.facebook.messages.ipc.peers.PROD:
    com.facebook.zero.ACTION_FORCE_ZERO_HEADER_REFRESH:
    com.facebook.zero.ACTION_ZERO_REFRESH_TOKEN:
    com.facebook.zero.ZERO_RATING_CLEAR_SETTINGS:
    com.google.android.gms.flp.EXPIRATION_ALARM:
    com.google.android.gms.gcm.PACKAGE_FULLY_REMOVED:
    com.google.android.gms.gcm.PACKAGE_REPLACED:
    com.google.android.googlequicksearchbox.action.PAUSE_HOTWORD:
    com.google.android.googlequicksearchbox.action.PAUSE_HOTWORD_FIRST_PARTY:
    com.google.android.googlequicksearchbox.action.RESUME_HOTWORD:
    com.google.android.googlequicksearchbox.action.RESUME_HOTWORD_FIRST_PARTY:
    com.google.android.intent.action.GCM_RECONNECT:
    com.google.android.intent.action.MCS_HEARTBEAT:
    com.google.android.intent.action.SEND_IDLE:
    com.google.android.location.intent.action.END_LOCATION_BURST:
    com.google.android.location.internal.server.ACTION_RESTARTED:
    com.google.android.location.reporting.ACTION_INSISTENT_SYNC:
    com.qcom.location.XtraDownloadRequest:
    com.qualcomm.location.geofence.breach:
    com.qualcomm.location.geofence.checkgeofences:
    com.qualcomm.location.ulp.HYBRID_HIGH_POWER_REQUEST_CHANGE:
    com.samsung.accessory.intent.action.UPDATE_NOTIFICATION_ITEM:
    com.samsung.action.HS20_EXPIRY_TIME_FOUND:
    com.samsung.android.app.audio.epinforequest:
    com.samsung.android.app.camera.RVF:
    com.samsung.android.intent.action.FINGERPRINT_ADDED:
    com.samsung.android.intent.action.FINGERPRINT_LOCK_SET:
    com.samsung.android.intent.action.FINGERPRINT_PASSWORD_UPDATED:
    com.samsung.android.intent.action.FINGERPRINT_REMOVED:
    com.samsung.android.intent.action.FINGERPRINT_RESET:
    com.samsung.android.intent.action.PRIVATE_MODE_OFF:
    com.samsung.android.intent.action.PRIVATE_MODE_ON:
    com.samsung.android.intent.action.UPDATING_APPWIDGET_COMPLETED:
    com.samsung.android.multiwindow.MINIMIZE_ALL:
    com.samsung.android.sdk.samsunglink.SlinkLaunchUtils.BROADCAST_SAMSUNG_LINK_EXITED:
    com.samsung.android.service.hermes.action.collect:
    com.samsung.axt9info.close:
    com.samsung.check.update.schedule:
    com.samsung.cover.NFC.OPEN:
    com.samsung.cover.OPEN:
    com.samsung.cover.REQUEST_REMOTEVIEWS:
    com.samsung.felica.action.LOCKSTATUS_LOCK:
    com.samsung.felica.action.LOCKSTATUS_UNLOCK:
    com.samsung.intent.action.ICC_CARD_STATE_CHANGED:
    com.samsung.intent.action.SIMDB_UNKNOWN_READY:
    com.samsung.intent.action.setCardDataInit:
    com.samsung.knox.ACTION_CANCEL_NOTIFICATION:
    com.samsung.knox.ACTION_NEW_NOTIFICATION:
    com.samsung.knox.clipboard.clipremoved:
    com.samsung.knox.clipboard.clipscleared:
    com.samsung.knox.clipboard.sync:
    com.samsung.knox.fmc_incoming_call:
    com.samsung.location.SERVICE_READY:
    com.samsung.pen.INSERT.USER_SWITCH:
    com.samsung.pen.INSERT:
    com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT:
    com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT_FROM_ALARM:
    com.samsung.sec.android.clockpackage.alarm.ALARM_STARTED_IN_ALERT:
    com.samsung.sec.android.clockpackage.alarm.ALARM_STOP:
    com.samsung.sec.android.clockpackage.alarm.ALARM_STOPPED_IN_ALERT:
    com.samsung.spdsuccess:
    com.samsung.wfd.RESULT_WFD_UPDATE:
    com.samsung.wfd.WFD_SESSION_ESTABLISHED:
    com.samsung.wfd.WFD_SESSION_TERMINATED:
    com.sec.GMS_bundling:
    com.sec.android.FindingLostPhone.CANCEL:
    com.sec.android.FindingLostPhone.SUBSCRIBE:
    com.sec.android.FindingLostPhonePlus.CANCEL:
    com.sec.android.FindingLostPhonePlus.SUBSCRIBE:
    com.sec.android.Keyguard.SIDE_TOUCH_UNLOCK:
    com.sec.android.LTE_CA_PARAMETER:
    com.sec.android.LTE_WIDEBAND_INFO:
    com.sec.android.action.CLEAR_MISSED_EVENT:
    com.sec.android.action.NOTIFY_FOCUS_WINDOWS:
    com.sec.android.action.NOTIFY_MULTIWINDOW_STATUS:
    com.sec.android.action.NOTIFY_SPLIT_WINDOWS:
    com.sec.android.app.GCF_MODE_ACTION:
    com.sec.android.app.camera.ACTION_START_BACK_CAMERA:
    com.sec.android.app.camera.ACTION_START_COVER_CAMERA:
    com.sec.android.app.camera.ACTION_START_FRONT_CAMERA:
    com.sec.android.app.camera.ACTION_STOP_CAMERA:
    com.sec.android.app.camera.ACTION_STOP_COVER_CAMERA:
    com.sec.android.app.clockpackage.timer.TIMER_STARTED_IN_ALERT:
    com.sec.android.app.dictionary.SEARCH:
    com.sec.android.app.launcher.MOVE_TO_PRIVATE:
    com.sec.android.app.mms.CB_CLEAR:
    com.sec.android.app.mms.SMS_CB_DIRECT_DISPLAY_RECEIVED:
    com.sec.android.app.mms.SSMS_STATE_FILE_UPDATE:
    com.sec.android.app.nfctest.GET_ESE_TYPE:
    com.sec.android.app.nfctest.NFC_CHECK_ESE:
    com.sec.android.app.nfctest.NFC_CHECK_SIM:
    com.sec.android.app.nfctest.NFC_DISCOVERY_DISABLE:
    com.sec.android.app.nfctest.NFC_DISCOVERY_ENABLE:
    com.sec.android.app.nfctest.NFC_ON_NO_DISCOVERY:
    com.sec.android.app.nfctest.NFC_TEST_END:
    com.sec.android.app.nfctest.NFC_TEST_START:
    com.sec.android.app.nfctest.PRBS_TEST_OFF:
    com.sec.android.app.nfctest.PRBS_TEST_ON:
    com.sec.android.app.nfctest.SET_ESE_TYPE:
    com.sec.android.app.ocr.OCR_SIP_TEXT:
    com.sec.android.app.ocr3.OCR_SIP_TEXT:
    com.sec.android.app.ocrlite.OCR_SIP_TEXT:
    com.sec.android.app.secsetupwizard.SETUPWIZARD_COMPLETE:
    com.sec.android.app.tmserver.mirrorlink:
    com.sec.android.contextaware.HEADSET_PLUG:
    com.sec.android.emergencymode.UltraPowerSavingManager.ORDER_ULTRA_POWERSAVING_SERVICE:
    com.sec.android.enterprisenotificationcenter.ENTERPRISE_MODE_CHANGE:
    com.sec.android.inputmethod.ACTION_ALARM_LIVELANGUAGE:
    com.sec.android.inputmethod.RequestImeInfo:
    com.sec.android.inputmethod.language_downloaded:
    com.sec.android.intent.action.BUNDLING_POLICY_UPDATED:
    com.sec.android.intent.action.EMERGENCY_MODE_CHANGED:
    com.sec.android.intent.action.INTERNAL_SPEAKER:
    com.sec.android.intent.action.PAUSE_WATCH:
    com.sec.android.intent.action.POWER_SAVING_MODE_CHANGED:
    com.sec.android.intent.action.QUICK_SHOT:
    com.sec.android.intent.action.REQUEST_BACKUP_LOCKSCREEN:
    com.sec.android.intent.action.REQUEST_RESTORE_LOCKSCREEN:
    com.sec.android.intent.action.SSRM_MDNIE_CHANGED:
    com.sec.android.intent.action.SSRM_REQUEST:
    com.sec.android.intent.action.ULTRA_POWER_SAVING_MODE_CHANGED:
    com.sec.android.phone.CHANGED_CALL_NUMBER:
    com.sec.android.phone.action.DataEnable:
    com.sec.android.quicksetting.REFRESH:
    com.sec.android.sconnect.service.ENABLED:
    com.sec.android.sidesync.action.FINISH_SIDESYNC_APP:
    com.sec.android.sidesync.action.KMS_KEYBOARD:
    com.sec.android.sidesync.action.PSS_KEYBOARD:
    com.sec.android.sidesync.source.SERVICE_DESTROY:
    com.sec.android.sidesync.source.SET_BINDER:
    com.sec.android.sidesync.source.SIDESYNC_CONNECTED:
    com.sec.android.sidesync.source.SIDESYNC_HIDE_SIP:
    com.sec.android.sidesync.source.SIDESYNC_INPUT_KEY:
    com.sec.android.sidesync.source.SIDESYNC_LANGUAGE_ID:
    com.sec.android.widgetapp.ap.accuweatherdaemon.action.AUTO_REFRESH:
    com.sec.android.widgetapp.ap.accuweatherdaemon.action.CHANE_SETTING:
    com.sec.android.widgetapp.ap.accuweatherdaemon.action.CHANGE_WEATHER_DATA:
    com.sec.android.widgetapp.ap.accuweatherdaemon.action.WEATHER_DATE_SYNC:
    com.sec.factory.app.factorytest.FTA_OFF:
    com.sec.factory.app.factorytest.FTA_ON:
    ...
* Sticky action android.hardware.usb.action.USB_CABLE_STATE:
* Sticky action android.hardware.usb.action.USB_STATE:
* Sticky action android.intent.action.ANY_DATA_STATE:
* Sticky action android.intent.action.BATTERY_CHANGED:
* Sticky action android.intent.action.CHECK_HMT_LEVEL:
* Sticky action android.intent.action.HDMI_PLUGGED:
* Sticky action android.intent.action.MAX_BRIGHTNESS_CHANGED:
* Sticky action android.intent.action.NETWORK_SET_TIMEZONE:
* Sticky action android.intent.action.SERVICE_STATE:
* Sticky action android.intent.action.SIG_STR:
* Sticky action android.intent.action.SIM_STATE_CHANGED:
* Sticky action android.intent.action.SIOP_LEVEL_CHANGED:
* Sticky action android.media.ACTION_SCO_AUDIO_STATE_UPDATED:
* Sticky action android.media.MASTER_MUTE_CHANGED_ACTION:
* Sticky action android.media.RINGER_MODE_CHANGED:
* Sticky action android.media.SCO_AUDIO_STATE_CHANGED:
* Sticky action android.net.conn.CONNECTIVITY_CHANGE:
* Sticky action android.net.conn.CONNECTIVITY_CHANGE_IMMEDIATE:
* Sticky action android.net.conn.INET_CONDITION_ACTION:
* Sticky action android.net.conn.TETHER_STATE_CHANGED:
* Sticky action android.net.nsd.STATE_CHANGED:
* Sticky action android.net.wifi.STATE_CHANGE:
* Sticky action android.net.wifi.WIFI_STATE_CHANGED:
* Sticky action android.net.wifi.p2p.CONNECTION_STATE_CHANGE:
* Sticky action android.net.wifi.p2p.PERSISTENT_GROUPS_CHANGED:
* Sticky action android.net.wifi.p2p.STATE_CHANGED:
* Sticky action android.net.wifi.p2p.THIS_DEVICE_CHANGED:
* Sticky action android.net.wifi.supplicant.STATE_CHANGE:
* Sticky action android.os.UpdateLock.UPDATE_LOCK_CHANGED:
* Sticky action android.provider.Telephony.SPN_STRINGS_UPDATED:
* Sticky action com.samsung.android.providers.context.intent.APP_CREATED:
* Sticky action com.samsung.glove.ENABLE:
* Sticky action com.samsung.pen.INSERT:
* Sticky action com.sec.intent.action.SYSSCOPESTATUS:

```
Upvotes: 2


<issue_start>username_0: I have an HTC Desire, and the default YouTube app does not cache the video after it plays the first time. The second time you play, it downloads the same video a second time, but I would like to cache the video on the memory card.

Is there any way to do this with the default YouTube app? If not, is there a third-party app that can do something like this?<issue_comment>username_1: I would think, that videos are not cached because of memory constraints on mobile devices.

Software developers have to design and implement software that works for the great majority of users. Perhaps adding an intelligent (device agnostic) cache function is not on the top of functionality they want to implement right now.
Upvotes: 1 <issue_comment>username_2: Google's YouTube app has an option to preload videos that are either in a channel you are subscribed to or that are in your "watch later" list. I haven't tested this but I think it will keep a video that you have preloaded cached for a while after you watched it for the first time.
Upvotes: 2


<issue_start>username_0: 1. Every-time I try to add a new contact, my Nexus S force me to put the contact under "Google contact from [my <EMAIL>]<EMAIL>". Is there any way to change this? As I am concern on privacy. I do not want to let Google server to have every of my contacts.
2. After adding new contact, I have to go to "Display options". Under [my address]<EMAIL>, there is a no name group (The first group with name is System Group:My Contacts). Is there any way I can assign name to the no name group?<issue_comment>username_1: You should get the option to add them unsynced. Like this:
![enter image description here](https://i.stack.imgur.com/VrUP6.png)
Upvotes: 3 [selected_answer]<issue_comment>username_2: As far as I know, contacts are always filed under some account. Presumably the design intent is that contacts are usually stored somewhere else, in some reliable storage, in case you lose the data on your phone.

I'm not in a position to try this myself, but here's a possible way to get an “unsynced” account: Install the free “[The Missing Sync for Android](https://market.android.com/details?id=com.markspace.missingsync&feature=search_result)” app. This app is intended to sync contacts directly with your desktop, and the desktop half is a paid app, but the phone side can be installed for free, and if you never sync it the data will stay on your phone.

The Missing Sync app will generate an account on your phone called “MissingSync” (which will be labeled “unsynced” even though it actually is synced via the Missing Sync app), which you can add contacts under.
Upvotes: 0


<issue_start>username_0: I have Samsung galaxy ace with android 2.2 mobile.

Is there any way or any application so i can run many applications simultaneously and i can switch among them?

**Why do i need this.**

1. When i surf facebook(or any other
application), and i click on a link.
I am suppose to wait until the page
gets opened then i read it pess back
button to reach on previous button.
If i press previous button in
between i'll lost page which was
being loaded.
2. If i read some sms, and i have to
search the meaning of a word in dictionary, i
would have to exit from sms box.<issue_comment>username_1: Case #1: You can get back to recently used apps by holding down the home key until a menu appears, and then selecting the app you want to return to.

Case #2: Press the home button and open your dictionary app, and then use the method in #1 to return to messaging.

This works if you don't have too many apps open, since the memory is limited and if you open too many apps, android will close them from the background.

The important distinction is that the home key does not quit the app but exists to the launcher, and the back button exits the app.
Upvotes: 4 [selected_answer]<issue_comment>username_2: Onik is correct in suggesting the built in task switcher but if you search "task switcher" in the market you will find a number of apps that might help, I suggest picking something light weight and intuitive.

From personal experience I can easily suggest QuickDesk or Wave Launcher.

QuickDesk will bring up a virtual home screen whenever/wherever. You can assign your favourite apps, shortcuts etc and it can show a scrollbar of recently run apps.

I recently switched to Wave Launcher and love it. It's highly configurable, light and intuitive, mimicking the gesture activate ribbon in Palm's WebOS. With a flick of your thumb or finger, you can bring up your favourite app, a recently run app, shortcut, or app draw overlay, all without leaving your current app (as long as you back out of whatever you're in). It is regulary updated and has brought many new features and improvements. Take a little time to experiment and tweak it and I thin you'll be very happy.

Best of luck.
Upvotes: 2


<issue_start>username_0: The Locus Maps app allows downloading maps and using them offline. When selecting a map region, the zoom levels have to be selected. I've downloaded a map at a specific zoom level (23) expecting that I will be able to use lower zoom levels as well (1-22).

However - I can now only go through the map at zoom level 23, which is awkward.

Is there any way to add additional zoom levels to those maps already downloaded, without having to download the entire thing again from scratch (it's big)?

Thank you!<issue_comment>username_1: After searching and searching - I don't think there's a way to do this. The only option is deleting the old map and downloading the map once again with multiple zoom levels selected.
Upvotes: 1 <issue_comment>username_2: Did you read the Locus documentation for downloading maps? Check [this document](http://docs.locusmap.eu/doku.php/manual%3amap_download).

In the end, there is a section called "Download types". There is a type called "External map", and this is what you need for this task.
Upvotes: 0


<issue_start>username_0: I need to change the default browser in my Android device to Opera. Is there any way to do that?<issue_comment>username_1: Certainly! Go in your **Settings**, **Manage Applications**. Click the **All** tab, and then select **Browser**. You must then click the **Clear Defaults** button.

Now next time that an application requires a browser (say, you click a link in your Twitter app) the **Complete action using** dialog will pop up and you can select Opera and tick the **Use by default for this action** box.

**Followup**: Make sure that you have installed Opera (or any other browser of your choice). If you only have the default browser installed, you will not get the **Complete action using** dialog. Again, look in **Settings**, **Manage Applications** but this time go in **Downloaded** to make sure that your preferred browser is there.
Upvotes: 4 <issue_comment>username_2: If you're getting an option to choose which browser to use, select the checkbox to set the default and then tap Opera.

If you're not getting an option to choose a browser to use, then you need to go into your settings and clear the default from the current from the current browser: `Settings -> Applications -> Manage Applications -> All -> [Current Default Browser] -> Clear Defaults`. The next time you open a link from outside a browser, you'll be given the option to set the default.
Upvotes: 2 <issue_comment>username_3: After installing Opera, when you open a link from somewhere in the system, you should see a popup asking you to choose between the browsers available. That popup should have a checkbox for saving the browser you choose as the default browser.

If you have already set a default browser, you must go to **Settings** > **Applications** > **Manage applications**, find the browser you now have as default and click on "**Clear defaults**" in the details page, then go through the process described in the first paragraph.
Upvotes: 5 <issue_comment>username_4: I'm using Android 2.3 and I couldn't find the stock browser to clear defaults. Then I realized that it is now called "Web" instead of "Browser" under `Settings - Applications - Manage applications - "All" tab`.
Upvotes: 3 <issue_comment>username_5: Just as an update, an easier way (on Android 4.0+ ICS) would be to go:

Settings > Apps > App Associations, then tap on "Web URLs" and a box will come up showing all browsers installed, you tap on the one you want to be the default browser. Same way for e-mail address links, phone numbers, etc.
Upvotes: 2 <issue_comment>username_6: In my opinion [Dafault App Manager](https://market.android.com/details?id=com.appiator.defaultappmanager) is the easiest way to configure the default apps (incl. the browser).
Upvotes: 0 <issue_comment>username_7: The answer given by @username_1 was actually more helpful to me, since I have a Samsung device.

The default browser is called "Internet". I think this was the case on my HTC with Orange (yep, just confirmed that).

I needed to click on "All" as @username_1 recommended, and then only can you see all the stock apps.
Upvotes: 1 <issue_comment>username_8: Download Opera to your device.

When you try to open something which requires a browser, you will be given the chance to select a browser. Select Opera, and press the `Always` button.
Upvotes: 0 <issue_comment>username_9: Go to the default app that is opening on your android now in settings > apps and click on it, then click disable, the next time you try to open the default browser you will be prompted to choose a default browser, and that's how it's done!
Upvotes: 0 <issue_comment>username_10: For kitkat users

1. Open **Settings**
2. Go to **Apps**
3. On the **All tabs**, look for your default browser and tap on it
4. Under **Launch by Default**, press the "**Clear defaults**" button, to reset default browser
5. Then open a link, you are asked to select a browser, select Opera , select Always.
Upvotes: 0 <issue_comment>username_11: For **Android M**:

`Settings`->`Apps`->`Advanced`->`Default App Settings`

All the default settings can be overridden there.
Upvotes: 1 <issue_comment>username_12: Xiaomi MIUI - Settings -> App Settings > System Apps / Installed apps -> Defaults (bottom) -> Browser -> change your default browser.
Upvotes: 1


<issue_start>username_0: I turned on geo-tagging for photos, but the problem is that the GPS locking procedure seems to only start when I open the camera app - but it takes minutes for it to lock on a location and by that time the photo opportunity is gone.

Is there any way to enable GPS lock to be ready even before opening the camera app? For instance some phone settings to toggle it off and on, or some service I can get which continuously runs in the background and maintains a GPS lock?

And if there is, what will be the power implications of maintaining a GPS lock? Does it drain a lot from the battery, or is it relatively benign?

My device is Samsung Galaxy S 2, running Android 2.3.3.<issue_comment>username_1: I've found that if I'm using another app in the background that polls for location (e.g. latitude in Maps) I tend to get much more accurate geo-tags in photos. YMMV, but perhaps if you know you're going to be shooting photos you can open up Maps or similar first to start the process going.

WRT your battery life question, leaving maps open tends to destroy my battery in a few (5-7) hours (Dinc 1, known for horrible battery life anyway, even among android phones), especially if I'm shooting a number of photos. When I know I'm going to be using my phone in that manner I typically bring a second battery along, so that when I'm done I can still make calls.
Upvotes: 1 <issue_comment>username_2: I'm starting GpsFix before any app that use GPS
<https://market.android.com/details?id=com.androidlab.gpsfix>
Upvotes: 0


<issue_start>username_0: Can Skype be used for video calling on a Samsung Galaxy 10.1?

I have been googling, but the results are not clear, for example, the official [Skype Blog](http://blogs.skype.com/garage/2011/08/skype_21_for_android_more_devi.html) says that Skype 2.1 supports the Samsung Galaxy Tab, but it is not clear if this means that it works with both the 7" and 10.1" versions.

*Update: as of early 2012, Skype does work on most Android tablets.*<issue_comment>username_1: If it was turned off, it wouldn't be able to detect the network.

Go to `Settings -> Wireless and network -> Wi-Fi settings` and uncheck Wi-Fi to disable Wi-Fi.
Upvotes: 3 <issue_comment>username_2: Another thing that you may want to uncheck is the alerts for open wireless networks and forget all the networks your phone has already connected to, as most Android phones are, by default, set up to re-connect to wireless networks they've already connected to. You can find these options, as username_1 said above, under Settings > Wireless and Network.
Upvotes: 2 [selected_answer]


<issue_start>username_0: Is it possible to send / retrieve MMS messages via WiFi or is it mandatory to be connected to my provider via the mobile data connection?

If a user has an active WiFi connection, what happens when there's an incoming MMS?<issue_comment>username_1: I dont think it's possible, since the data is sent through the cell network and not through a traditional Wi-Fi style Internet connection.
Upvotes: 3 <issue_comment>username_2: Your network probably uses a separate MMS APN for multimedia messaging, and these are restricted to the operator's own network, so the messages can't be received via WiFi. Also, the messages are directed to your phone number so this could be compared to using SIP/VoIP through your regular phone number.

If there is an active WiFi connection, it is ignored and packet data is used instead (if enabled).
Upvotes: 2 <issue_comment>username_3: It could be done technically. AFAIK all communication between MMS enabled components is done via standard TCP/IP.
But in a regular provider setup the MMS store and forward server(s) (MMSC) are only reachable via the providers network. That's why you can not send and receive MMS via WiFi.

It's also the reason why you can not make a call and send/receive an MMS simultaneously when you have only 2G (GPRS/EDGE) connectivity.

Normally android will drop the GSM data connection if there is WiFi connectivity and all data will be routed through the WiFi interface, **but there is one exception**: The MMS traffic will still go through the mobile data connection.
Upvotes: 5 [selected_answer]<issue_comment>username_4: As others have mentioned, the only way to receive a MMS directed toward the number serviced by your carrier is for you to be connected to their service. However, you might consider a service such as Google Voice. Google Voice provides an alternative number that is then routed to your phone. Currently Google Voice only supports SMS, but there may be other services that offer MMS support. A SMS message sent to your Google Voice number would then be visible in the Google Voice app, even if you only have a WiFi connection.
Upvotes: 1 <issue_comment>username_5: This is dependent on the Carrier. UMA is the form of radio that allows the sending of traditional texts and mms over Wifi. T-Mobile in the US is the carrier who has it, as for where you are, I would check with your provider.
Upvotes: 2 <issue_comment>username_6: I think that most (smart) phones do not know how to create a separate IP socket to send/receive MMS over wifi. So they revert by default to the data socket provided by the carrier. Or they may not have the ability to switch between two different sockets automatically. If you do root your phone and change the default MMS IP socket, you may lose all MMS connectivity depending on the phone.
Upvotes: 1 <issue_comment>username_7: This is an old thread, I know, but I wanted to add that the Nokia N900 multimedia messaging app could receive notification of a MMS via the cellular network and retrieve the MMS, itself, via the Internet, at least on Wind (now Freedom Mobile) in Canada. This avoided roaming data charges and is the one feature that I miss most from my N900, now that I am using an Android phone.
Upvotes: 0


<issue_start>username_0: I currently use [Mute All](https://market.android.com/details?id=com.km.house.volume) but it requires several clicks. I like the ease of [Silent Toggle Widget](https://market.android.com/details?id=com.aiteam.silenttogglewidget&hl=en) but it doesn't turn of media sounds.

Ideally the widget would also turn of haptic feedback.<issue_comment>username_1: I created a Task in Tasker called Silent that does this and created a widget that allows the one click behavior you are looking for.

Basically Silent is just a set of tasks that set the notification/ringer/system volume/etc to level 0. Here is the XML for the Silent.tsk.xml if you want to import it.

```

Silent
14

 `304`

 1

 `305`

 1

 2130837581

 1

 `256`

 1

 3

 Vibrate On

 Vibrate On

 `550`

 `308`

 1

 1

 `258`

```
Upvotes: 2 <issue_comment>username_2: With [Audio Muter](https://play.google.com/store/apps/details?id=MyApps.AudioMuter) you should be able to set the media volume to silent, however it's a paid app.
Upvotes: 0 <issue_comment>username_3: [Audio Manager](https://play.google.com/store/apps/details?id=com.smartandroidapps.audiowidget&hl=en) (free) and [Audio Manager Pro](https://play.google.com/store/apps/details?id=com.smartandroidapps.audiowidgetpro) ($2.99) fully solve this issue very cleanly. It gives complete control over haptic feedback and the 6 distinct audio volume controls (including media volume), and lets you construct profiles that can be toggled with one-click widgets.
Upvotes: 0


<issue_start>username_0: I'm looking to buy a small tablet to use as a "table phone" for use with a headset, and for video telephony. GSM telephony is a must - I don't want to rely entirely on Skype, or Internet connectivity in general. (Plus I'm eligible for a landline number on my mobile contract so people can call me from normal phones for free, which is great.)

I am hovering between the [7" P1000 Samsung Galaxy Tab](http://www.gsmarena.com/samsung_p1000_galaxy_tab-3370.php) and the more expensive, newer [8.9" one.](http://www.gsmarena.com/samsung_galaxy_tab_8_9_3g-3891.php)

The 7" one officially supports GSM telephony. Various tests remarked that it's a bit too chunky for use as a normal mobile phone but for my use case on the desk, that doesn't matter. I really just want something I can carry around in a bag, and put on my desk to make calls with.

The 8.9" one supports GSM telephony, but doesn't come with it activated out of the box. You need third party Android products in order to use it.

This strikes me as odd, and makes me expect problems - why else would one build in the functionality, but not ship with it enabled? Telephony is the one thing I really, really need to just *work* - I can't afford to deal with dropping connections, bad voice quality, patches, and an overall "beta" experience.

Is telephony feasible on an 8.9" Samsung Galaxy Tab?<issue_comment>username_1: A list with tablets will rapidly became outdated so the best is to provide a reference to 2 sites that will probably get updated at least every once in a while:

* <http://en.wikipedia.org/wiki/Comparison_of_Android_devices>

(not all specs available you can search for the model name here <http://www.gsmarena.com/> to get the specs) and

* <http://www.google.com/phone>

(only US devices I think)
Upvotes: 0 <issue_comment>username_2: You write that the 8.9" tablet has support for GSM telephony but that it is not activated out of the box - and that suprises and concerns you.

Well, for many of us, the original 7" Galaxy Tab is the same: the hardware supports GSM telephony but the North American firmwares have no support for it. Presumably this was done at the behest of the N.A. carriers who want users to use the tablet as a second cellular device - not as a replacement for a phone.

As a result, I had to root the Galaxy Tab and load a European firmware on it in order to activate its GSM telephony. Once I did this it worked perfectly well as both a phone and a tablet. (Though it does seem rather slow by today's standards, and it won't be getting ICS.)

It sounds like that is the same situation that you would face with the 8.9" tab: the fact that the GSM telephony was not supported out of the box did not mean that it didn't work well - but you need to be prepared to get your hands dirty to 'activate' this functionality yourself.
Upvotes: 2


<issue_start>username_0: I'm a system administrator for a school division, and we are upgrading our Wi-Fi network. Is there a way that I can map the strength of the Wi-Fi signal at different places inside a building (where GPS does not work)?

I have used some stumblers -- Wi-Fi Analyzer and Meraki Wi-Fi Stumbler -- and those really do most of what I need, but I'd really like to see things on a map. I've tried some standard wardriving applications -- such as WiGLE Wi-Fi Wardriving and Wi-Fi Map Maker - Free -- and they just don't really work without a GPS coordinate.

I'd be more than happy to snap a photo of a building map and indicate where I am at different places and be able to see, say, a heat-map of the signal strength (and better still if I could see if by BSSID). I'd also be find with using the phone as a collection device and analyzing the data later on the computer.

Is there a way to map the Wi-Fi signal strength at different places in the buildings I'm providing Wi-Fi service to?<issue_comment>username_1: Did you try [WiFi Mapper](https://market.android.com/details?id=com.osiris_mobile.wifimapper)?
Upvotes: 2 <issue_comment>username_2: You could try "[WiFi Maps Light](https://play.google.com/store/apps/details?id=com.renjuplay.tools.wifimapslight)" for Android, available for free in Google Play.
Upvotes: 2


<issue_start>username_0: The **canonical** location for my music collection is the Android phone (synced from Mac at work), and I have a Windows PC at home connected to the speaker system. Is it possible to play the music on Android, but stream (via bluetooth, wifi or USB) the audio to these speakers (via the PC)?<issue_comment>username_1: Yes, you can do this in Windows XP and 7. It will stream all audio from the phone- apps, games, etc. You do not need any additional software, just Bluetooth connectivity on the PC.

AirDroid lets you access your device, including streaming music, over WiFi via a web browser.

You could also just plug your phone into a USB to your PC, and play the music on the PC with MusicBee or any other media player.
Upvotes: 0 <issue_comment>username_2: In case you haven't found a solution yet, I would recommend an app called [Soundwire](https://play.google.com/store/apps/details?id=com.georgie.SoundWireFree)
Upvotes: 0 <issue_comment>username_3: Yes, you can. No additional soft or hardware is required. On Android 4.4.2 and Windows XP:

1. Enable Bluetooth on both devices
2. Make sure under Windows' Bluetooth Configuration -> Local Services you have the 'Headset' service set to 'Automatic startup'
3. Connect the devices (using a pass-phrase if required)
4. Check on Android that 'Media audio' is enabled for the connected PC
5. Play some music, enjoy!
Upvotes: 1 <issue_comment>username_4: Get a Male to Male 3.5 mm audio cable. Connect one end to your phone's audio jack and the other one to your PC's microphone jack.

Now here comes the tricky part :

1. In the notification area, right click the speaker icon. Click "Playback Devices".
2. In the Dialogue Box, right click "Speakers -> Set as Default Device". If
 there is already a green tick on the speaker icon, move to step 3.
3. If you have laptop then (A) or desktop then (B) :

```
(A) Remove the cable you just connected. Now click on "Recording" Tab. See, there's a Mic which has a green tick. Don't interfere with this thing. Now the second one is a mic which is disconnected and has a red mark. Now connect the cable. It will show ready. Now double click it. In the popup, click "Listen" Tab. Check the "Listen to this Device". In the "Playback through this device dropdown, select Speakers. Now click apply. Your computer might now start producing awkward sounds, to adjust, click "Levels" Tab. Now adjust Microphone volume and Microphone boost to the desired amount to remove any sort of noise.

(B) If you have a desktop, All the steps are same as a laptop except the microphone selection. In the recording devices menu, only one microphone should be there. So it is easy to find that. Do all the next steps as a laptop.

```

**NOTE :** If you can't see your device, right click and tick "Show disabled devices" and "Show disconnected devices". If your device is disabled, enable it first.
 4. Now play any audio of your choice in the phone to get the desired output.

**P.S.** : Any device with a 3.5 mm audio output can be used as a source.
Upvotes: 1


<issue_start>username_0: Since I got this device in mid November to now, I have had great battery life usually lasting almost two full days and never having a problem for one day unless I'd been using it excessively. Suddenly yesterday I started losing power and the device is dead in just about 8 hours, with the graph of battery loss showing only Skype and Android OS. I haven't used Skype at all and don't know why it would even show up on this graph, but Android OS usually hadn't been showing up as more than about 5-15% of my total battery usage, much less overshadowing everything else. I uninstalled Skype thinking it may have updated and have noticed no difference at all.

I've started looking for solutions online, and found forums for "android OS bug fixes" but nothing that detailed anything similar to this situation. <http://forum.xda-developers.com/showthread.php?t=1135033>

I have had Gingerbread 2.3.3 since I got this phone (annoyingly.. where is ICS Samsung??) I'm pretty sure and have had no battery drain problems such as this at all until just recently. I had not made any changes to the system nor any applications or widgets and see no reason why suddenly the OS would start to consume my battery erroneously.

I don't have WiFi on typically unless I'm in a zone where I do have it and sketchy service such as at work sometimes (I am a student and only work about 15 hours a week on top of classes) and at home if I'm updating apps or using my phone a lot and want the quicker service. GPS and Bluetooth are always off, along with 4G unless I will be currently using it a lot in a 4G zone.

Basically, I see no reason why my battery life should suddenly become awful when I had been having such a wonderful experience with this phone for months. What could have caused this and how can I reverse it?? Thanks!<issue_comment>username_1: Are any apps showing suspiciously high cpu use? You can check with Seepu, or with 'top' command at the terminal or adb-shell.
Upvotes: 1 <issue_comment>username_2: I'm having precisely the same issue. I was comfortably getting 18ish hours, and now roughly 9. Android OS was at somewhere around 75% usage, where normally it rests cozily below display usage.

I have swapped in my spare battery and things appear marginally better, but I'm not so sure just yet. I'm pondering the possibility that a hard power off might have helped also (vs. a regular reboot)

Check out [this article](http://betanews.com/2011/12/29/my-android-nightmare/) also, it seems very familiar and his was a faulty antenna.
Upvotes: 0 <issue_comment>username_3: THE SOLUTION:

OK here is the deal...I researched this as it happened to me just that way a few days ago....but first, some background.

I bought the Samsung Galaxy 3 from radio Shack-My carrier is Sprint. The device has NOT been rooted. Had pretty good luck with the Samsung Epic (Galaxy S).

Installed: Juice Defender Pro-Almost DOUBLED my battery life until....

4 days ago, I awoke at about 6 am to see that the battery had been charged, so i disconnected the charger. Went back to sleep, and about 8am, was horrified to see that the battery had SOMEHOW drained to 23%...It had drained 3/4 of its capacity in just under 2 hours!

Well that aint happening. After some very tedious research, I was left with a few possibilities: 1) bad battery or device (no kidding) (2) Make some setting changes (i did that...I set my display to minimum and NOT to auto, and made a few other changes) But the thing that did the trick was uninstalling some apps that I just installed. Once that was done, the phone ran fine.

The problem is that some applications, especially third party ones, will not always work properly, and/or can drain the battery. The only way to know for sure is to uninstall them...wait to see if it helps, and if it does, then install them again, and see if the problem returns. i elected to NOT reinstall the applications. I figure that i can try others, and today, I only install one app at a time, and if the phone behaves properly, then it stays.

There are MANY things one can do to extend battery life. I LOVE Juice Defender Pro. It does what it says it will do, and was worth every dime I paid. There are other things you can do like Use airplane mode when listening to mp3's. I went on a motorcycle ride, listened to music for 3 hours, and only used about 8% of my battery life to do it.

Anyway, I hope this helps. Try getting rid of apps that were most recently installed before the issue occurred. It was the solution's for me.
Upvotes: 1


<issue_start>username_0: Is a google account mandatory to use the android market?<issue_comment>username_1: Yes. You need one to sign in, even for free apps. Paid apps are paid for via Google Checkout.
Upvotes: 2 <issue_comment>username_2: Yes, it is mandatory to use Google Account to use Google's Android Market; however it is not mandatory to use Google's Android Market to install Android applications. There are many [third party app markets](https://android.stackexchange.com/questions/216/what-are-the-alternative-android-app-markets) and you can sideload an .apk file you have downloaded to the device (except on some devices from brain-damaged carriers where this option is disabled). Some alternative markets do not require registration.
Upvotes: 3


<issue_start>username_0: The two ways I see to secure an Android phone is through a PIN lock screen or through an app lock program (Password is too inconvenient and pattern is insecure for [various reasons](https://android.stackexchange.com/questions/18763/just-how-secure-is-a-pattern-lock)). The lock screen has the advantage of keeping someone from the phone altogether, but an app lock program can allow me to use basic functionality while locking the apps that I choose such as Email or Package Installer.

Is one option easier to hack/bypass than another? Let's assume that the App Lock program has a helper app that prevents it from being killed (although how well such an app works is worthy of being discussed in an answer - point being it takes a little more work than simply going to task manager and killing it).

I am primarily concerned about data on the phone.

I know that ultimately I cannot rely on either method to secure the phone indefinitely, but to only secure it long enough for me take various actions such as remote wipe, change Google password, Exchange password, etc...

I'm running Gingerbread 2.3.6. For what it's worth it is rooted and has ClockWordMod recovery.<issue_comment>username_1: I would use lock screen... It is easy to use bruteforce on any apps which are using a pin code, it is harden with the lock screen, but not impossible.. So don't carry very important documents on your phone...
Upvotes: 1 <issue_comment>username_2: You could always Encrypt your device.

Depending on what phone you are using will determine the method or even availablity of this function.

It takes time though and you should do it with about 80-90% battery.

Also, I beleive the fact that your phone is rooted, makes it less secure - assuming the thief/person who picked up your phone (assuming that it was to be lost).

As long as they can access the internal/external storage, they can bypass this.
Upvotes: 2 <issue_comment>username_3: The app locker gives you more access, and is working against the system rather than with it. Almost by definition, it's much less secure.

An app locker might keep out the casual user, but not anyone who knows what they're doing. Unless it blocks new apps by default, sideloading would be a problem. Depending on the device that may be enough to root it (if you're not already) and then they can more or less bypass/remove anything on the device. adb access is a risk in both cases but the ability to interact with the device may provide some other options.

I agree with username_2 that encryption is the way to go. Using a lock screen plus an app locker is better than using only one of them, as well.
Upvotes: 3 [selected_answer]


<issue_start>username_0: I'd like to use my HTC Evo 3D as an external monitor for my Canon 7D camera. The Canon 7D has a HDMI output. It also has an USB port, naturally.

I was wondering whether this would be possible. I think the USB/MHL port on HTC Evo 3D is for output only and it cannot receive any signal inputs. Is that right?

That would leave the USB port for this. But I still don't know how to achieve it.

I want to achieve something like this:

![photo of camera with external microphone inputs and monitor](https://i.stack.imgur.com/Ahj2n.jpg)<issue_comment>username_1: As far as I know, there are several apps on google play that will support several external cameras via USB, and I believe they allow for control of camera via android as well. Just search for Canon Camera Controller.
Upvotes: 0 <issue_comment>username_2: If your HTC phone has OTG support. You can use one of these [USB OTG adapters](http://rads.stackoverflow.com/amzn/click/B00AYPEL56). Then you can plug your 70D using a mini USB cable and then plug it in to the OTG cable and plug it into your phone. Then you can download an app such as [DSLR Controller](https://play.google.com/store/apps/details?id=eu.chainfire.dslrcontroller&hl=en) and you should see live feed of your 70D on the phone.
Upvotes: 1


<issue_start>username_0: Even when I set the backlight onto its dimmest, it is still very bright when using it in the dark. However, when you have low battery it appears even dimmer, so I know it is possible to get it to that level.

Is there anyway to set it to this reduced level?

If it makes any difference, I am using a Galaxy Ace (2.3.3).<issue_comment>username_1: I'm currently using [Screen Filter](https://play.google.com/store/apps/details?id=com.haxor&hl=en). It reduces the brightness of your phone below the level of what Android OS provides. Works for me and is a good battery saver. Hope this helps.
Upvotes: 3 [selected_answer]<issue_comment>username_2: You can use [Dimmer](https://f-droid.org/repository/browse/?fdfilter=brightness&fdid=giraffine.dimmer) available on F-droid (an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform).

>
> ### Dimmer
>
>
> Lower brightness
>
>
> Lower the brightness beyond the limit through a filter.
>
>
> License: [Apache2](https://www.gnu.org/licenses/license-list.html#apache2)
>
>
>

Current version (3.3.1) [apk](https://f-droid.org/repo/giraffine.dimmer_37.apk).

[![enter image description here](https://i.stack.imgur.com/POkjmm.jpg)](https://i.stack.imgur.com/POkjmm.jpg)
Upvotes: 0


<issue_start>username_0: If I wish to install applications such as Skype, DropBox, etc however without registering for a Google account, is that possible? If so, how do I install them without a Google account?<issue_comment>username_1: You could use other App stores like [**Amazon App Store**](http://www.amazon.com/gp/mas/get-appstore/android) or **GetJar**, but you would also need accounts on those.

You can side-load apps via downloading APK files on PC and then installing them from your SD card. Just try opening the APK files with a file manager like **ES File Explorer** or **ASTRO File Manager** which would give a option to open it with Package manager or Install.

But I assume from your question that you don't want to enable **Installation of Non-market apps**, then you don't get much choice. Even Amazon App store requires that feature enabled.
Upvotes: 2 <issue_comment>username_2: Use ADB to install the applications.

Install the Android sdk ( <https://developer.android.com/sdk/index.html> ).

Enable USB debugging in Settings>Applications>Development.
This process can be done even without enabling side-loading of apps. Open a command prompt window and type:

```
adb install app_name.apk

```
Upvotes: 4 [selected_answer]<issue_comment>username_3: one can download APK files available on Google Play Store, without a Google account, by using [APK Pure](http://apkpure.com).
it also allows downloading previous versions which may be helpful for people trying older devices, which need older app version for compatibility reasons.

additionally, one may choose to use a region-specific build.
Upvotes: 0


<issue_start>username_0: I am using Android 4.0 and latest version of Google Maps. The interface is in English. When I search for direction to some place say Kyoto, the interface is in mixed English and Japanese. See the attached screenshot to understand what I mean.

![Screenshot](https://dl.dropbox.com/s/n95iz3jzs2fxiam/2012-06-12%2015.32.01.png)

How do see the destination names in English?<issue_comment>username_1: It's not possible to get it in English. You will always get the text as it is "locally". It's also a [known annoyance](http://productforums.google.com/forum/#!topic/maps/dxcN3YowkEo).
Upvotes: 2 [selected_answer]<issue_comment>username_2: Try installing [Morelocale 2](https://play.google.com/store/apps/details?id=jp.co.c_lis.ccl.morelocale&hl=en) and setting the locale to one of the English speaking countries or yet better define a new locale with language en and locale JP.
Upvotes: 0


<issue_start>username_0: I used wifi tether application to share internet connection in rooted xperia x8 android 2.1 version. It is work for my laptop.
I can connect this network correctly with my laptop. But I can not connect this network with another android phone or tablet.
Because this network does not appear in another android phone or tablet. What setting should I change?<issue_comment>username_1: Most likely, your X8 is broadcasting the wireless network in [ad-hoc](http://en.wikipedia.org/wiki/Wireless_ad_hoc_network) mode rather than [infrastructure (AP) mode](http://compnetworking.about.com/cs/wireless/f/infrawireless.htm). Android does not natively support ad-hoc wireless connections, which is why your tablet cannot see or connect to the hotspot.

Your options depend largely on the state of your devices. If your phone is rooted then you can try a custom ROM or kernel that is built with support for infrastructure mode. [XDA's X8 sub-forum](http://forum.xda-developers.com/forumdisplay.php?f=849&order=desc&page=2) would be a good place to start looking for a ROM/kernel that suits your needs. Custom ROMs may list infrastructure or wifi tethering support in their features, though you may have to skim the ROM's thread as a whole to find out.

If your tablet is rooted then you could try to find a wireless module that has been built to support ad-hoc mode. There are modifications for many mainstream tablets that will enable this functionality, usually consisting of a patched version of the `wpa_supplicant` binary that would need to be installed on your device.

If neither device is rooted then there is probably not much you can do. You may want to look into other alternatives, such as perhaps [Bluetooth tethering](https://android.stackexchange.com/questions/tagged/bluetooth-tethering).
Upvotes: 2 <issue_comment>username_2: The **wifi-tether** app supports running in infrastructure mode.

1. Make sure you have the app called [**wifi-tether**](http://code.google.com/p/android-wifi-tether/) (Not wireless-tether or anything)
2. Use of this app requires a rooted phone and netfilter compiled into your kernel (which may or may not come stock)
Upvotes: 1


<issue_start>username_0: Fido has a service where they allocate a public IP address for some fees. I have paid the fees and apparently they have allocated my phone a public IP address. In normal circumstances, I should be able to see the IP address in my device settings (status information), but it shows "IP address unavailable". Fido customer service is not able to help, saying that they only have instructions for the iPhone. For any other phone, I should contact the manufacturer.

Any idea how I could go about finding the public IP address that I am paying through my nose for?

Carrier: Fido in Canada.

Phone: Samsung Galaxy S2

OS: Android 4.0.3<issue_comment>username_1: You could always use the browser hit one of the many web pages that will tell you what your IP address is. [WhatsMyIp](http://www.whatsmyip.org/) being one such.
Upvotes: 2 <issue_comment>username_2: Get [Network Info II](https://play.google.com/store/apps/details?id=aws.apps.networkInfoIi). It also gives you the name of your gateway.
Upvotes: 0 <issue_comment>username_3: Typically your carrier will be using NAT so you will have either a private RFC1918 address or an already allocated public IP.

A free app like [Net Tools](https://play.google.com/store/apps/details?id=com.sanctuaire.netswisstool&hl=en "Net Tools") will tell you the IP assigned directly to your phone, so can you have IP communications with your carrier. (Net Tools will use netcfg as you have).

If you go to whatismyip.com you will likely find a different IP though because your connection is behind a NAT device. This is why you can't "ping" your phones IP.
Upvotes: 1 <issue_comment>username_4: So reproducing the solution here for posterity: Need to change the default apn to either publicip.apn or vpn.com. All the other settings remain the same as the original default apn (which is fido-core.appl1.apn). Restart the device and voila!, the phone has a public ip. It can be discovered using adb and netcfg. @MartinSchröder, thanks a lot for pointing out Network Info II tool, its quite useful. Only thing is, after tethering the device, it reports an IPV6 rndis ip as the "internal" ip of the device.
Upvotes: 2 [selected_answer]<issue_comment>username_5: This open-source app might fit your needs, called [External IP](http://f-droid.org/repository/browse/?fdid=org.kost.externalip&fdpage=3).

>
> This simple application will show your IP addresses(default local &
>  external).
>
>
>
Upvotes: 0


<issue_start>username_0: They appear to perform the same functionality... only difference I see is that Currents layout is more like a magazine. And I can import my Reader subscriptions to Currents.

What's the difference between the two? Is there any reason to use one over the other? Does Currents replace Reader?<issue_comment>username_1: **Google Reader**
=================

Google Reader is a Web-based tool for gathering, reading, and sharing all the interesting blogs and websites you read on the web.

It was released by Google on October 7, 2005 and graduated from beta status on September 17, 2007. Is available on any modern web browser with JavaScript enabled.

**For further information visit:**

* [Google Support - Getting started with Google Reader](http://support.google.com/reader/bin/answer.py?hl=en&answer=113517)
* [Wikipedia - Google Reader](http://en.wikipedia.org/wiki/Google_Reader)

---

**Google Currents**
===================

Google Currents is an APP that delivers beautiful magazine-like editions to your tablet and smartphone for high speed and offline reading.

It was released by Google in December 2011 is currently available for Android and username_2 devices.

**For further information visit:**

* [Google Currents Webpage](https://www.google.com/producer/currents)
* [Google play - Google Currents page](https://play.google.com/store/apps/details?id=com.google.android.apps.currents&hl=en)
* [Wikipedia - Google Currents](http://en.wikipedia.org/wiki/Google_Currents)

---

**To answer your questions**
============================

>
> What's the difference between the two?
>
>
>

**R:** The major difference is that Google Currents is an APP to be installed on your tablet or smartphone, while the Google Reader is a web-based application.

>
> Is there any reason to use one over the other?
>
>
>

**R:** The major reason is that Google Current is currently available for tablet and smartphones, while the Google Reader, being a web-based application can be used on every device with an JavaScript ready web browser.

>
> Does Currents replace Reader?
>
>
>

**R:** Haven't found any indication that Google Currents came to replace Google Reader. Actually the opposite seems to be happening, as the Google Currents can accept your feeds from your Google Reader account. Think of Google Currents as a more flexible way of reading feeds without the need of a web browser.

---

**Reader APP vs Currents APP**
==============================

You've mentioned on the comment for this answer that there's a Currents app and a Reader app. Yes, it does exists and I didn't know about it.

Just installed to compare the differences:

* **Reader APP:**

Continues to be a plain old fashioned RSS feed, just with a new "face".

From [Differences between the mobile and standard web interface (Google Support)](http://support.google.com/mobile/bin/answer.py?hl=en&answer=73777&topic=13564&ctx=topic)

>
> The mobile interface accesses the same subscriptions as the standard web interface, and items read on your mobile device will be marked as read in the standard interface as well. Similarly, items read on the web will be marked as read in the mobile interface. The only difference is that you can't set up subscriptions from your mobile device.
>
>
>
* **Currents app:**

Instead of adding direct RSS feeds, you can add featured sites from well over 150 publishers that Google has partnered with. They include Forbes, TechCrunch, AllThingsD, The Huffington Post, ABC News, Al Jazeera, and The Guardian.

You can choose sites from other featured topics including Business, Design, Science & Tech, Sports, and your RSS feeds from your Google Reader account.

Additionally, you can be a [Google Producer](https://www.google.com/producer/home) and add your own content to Google Currents.
Upvotes: 3 <issue_comment>username_2: Google Reader is a cloud-based feed reader *service*. On top of this service, there are many apps as a front-end to user. E.g.- Official Google Reader apps (Web, Android), Feedly (Firefox, Android) etc.

Google Currents is a front-end digital magazine/ newspaper delivery app (with cloud sync) available to Android and username_2 (no web interface yet). Google Currents can read feeds, but it wasn't designed for that. Google has a vision attached with it: Real digital magazine/ newspaper delivery which is beyond normal feed reading! See the differences:

* Feed publishers don't have control of content display in end app, but Currents publishers do have. They can divide their currents in sections, sub-sections. They can decide the layout of this digital magazine etc. Its not just nice looking magazine interface.. its more than that. Feedly, which sync with Google Reader, also provides magazine interface, but its not really a magazine. Think about your real-world magazine reading experience.
* Currents can be premium. Current publishers can charge you which is not possible with Google Reader. While there's a concept of premium feeds (which is rare), Google Reader can only subscribe it. But, Google Currents can be marketplace for that.

Google Currents can't replace Google Reader because its different thing. If you don't have special interest in those hand-created digital publications, go for Google Reader. You can use it on web, Windows, Mac, Ubuntu etc along with tablets and smartphones (all in sync for read/unread status, starred items). You can have thousands of interface choices thanks to Google Reader API. And yes, you can always mix feeds in Google Reader to create your own feed DJ (which is not possible with Google Currents).
Upvotes: 4 [selected_answer]<issue_comment>username_3: One other important thing to add about Google Currents is that depending on how many things you subscribe to, it can add on tons of megabytes to your phone's memory. I have a Samsung Galaxy S3 and I noticed that with my subscriptions and feeds, the Currents app is currently eating up 180 mb of memory on my phone.
If that is not a problem for you, then Currents is a nice format to read info that you receive from your Google reader or maybe check out some magazines even. I myself can go without the frills to save that space on my phone. I believe in the end, it all just boils down to personal preference .
Upvotes: 0