text:
Reinstalling purchased apps on a new phone?

Possible Duplicate:
Move paid apps between devices?

My contract is getting close to finishing so I'll be upgrading to a new Android phone and giving my old phone to a family member.
When I move my Google account across to my new phone will I have to repurchase or just re-download my paid for apps?
Also will I'll have to remove the paid for apps from my old phone before it is associated with a new Google account?

Bonus question: If your old phone came with some app free that usually costs money, do you still have access to it / can use it on your new phone?

@user4188 mot usually because when the device comes with an app, it is installed on the device from the manufacturer and not via the android market.

You will not have to repurchase them if you associate the same Google account with the new device. They will be available in your market to re-download.
I don't know if you can have more then one phone associated with the same account, but I did not do anything when I got a new phone, except associate my google account to the new phone.

This is correct.  You can have more than one phone with the same account.

You just have to re-download them, not re-purchase them.  The apps are tied to your account, not your device.
As far as I know you don't have to do a thing to your old device before your apps are available for download and installation on your new one.
Post #2 in this thread states the same, for what it's worth.

This is correct.

Amazon App Store also follows the same model. I had to switch to a different ROM after clearing cache and reinstall on my NotionInk Adam Tablet. Through the browser I reinstalled the AmazonAppStore App. I used the same amazon UserID and passwd. It immeidately recognized all the apps I had purchased and provided option to download and re-install them.


text:
Need a car-friendly way to listen to music?
Here is specifically what I'm looking for.
1)  I would like the ability to use gesture/swipe controls to skip tracks.  This is much easier than finding a button on a touchscreen to change tracks.
2)  Ability to either prevent a lockscreen or control the player from the lockscreen.  I don't mind if I have to push the power button to get the screen to wakeup, but once I do, I would like the ability to control the music player without going through the Android screen lock.  I see this accomplished through either a certain type of music app, or some application that allows me to control what applications prevent a screen from locking.
I have a rooted Samsung Captivate (Galaxy-S) running a custom ROM variant of 2.2.1.

Go download PowerAmp.  Best $5 I ever spent on an app.
It includes lockscreen controls and I'm pretty sure you can set up lockscreen gestures to do whatever you want.  I'll confirm this real quick on my installation.
Edit: Confirmed on the lockscreen gestures.  Swiping left and right over the album art will skip the track forward and backward by default, from anywhere in the app or on the lockscreen.

Does it allow me to send audio to my parrot bluetooth head unit? I'd LOVE that.

@Pitto - I dunno, I don't use a BT headset so I've obviously never tried it.  As Chance said in his comment they offer a 15-day free trial, so you've really got nothing to lose by giving it a shot.

I'll get my lazy *** off this chair and do it :D Thanks!

I'm using it right now.  Great app.  Have you found a way to pause it other than the pause button or removing the headphones?  I want to be able to pause it without looking for the button on the screen.

source: Stack Exchange

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/

sort: votes


text:
Can I get .apk file of an installed app?
I have deployed my apps .apk file on a Qualcomm device. Now due to my bad luck my laptop on which this app was developed got stolen.So i do not have my app code with me. However i have the device on which i had earlier installed my app.
So my question is, can i get my apps .apk file from this device? if yes, then please tell me how to get that.
Any help is appreciable.
Thanks,
Gaurav

It should be located at /data/app/.  You can access that directly if you have root.  If not, you will have to use adb pull.  For example:

adb pull /data/app/myapp.apk C:\backup\myapp.apk

More info on adb: http://developer.android.com/guide/developing/tools/adb.html

If you know the installed file name of the apk (which on some devices may be myapp-1.apk or myapp-2.apk rather than just myapp.apk) you can directly access that as an ordinary user including the one adb runs as on a secured device, so you should be able to adb pull it.  But if you don't know the installed apk name, you cannot browse the /data/app directory without being root or aid_system.
It might be worth just guessing at the installed name - try it plain, try it with the -1.apk, and the -2.apk, etc.
There may be another way: I believe the following will work on a secured device but don't have one in front of me at the moment to test it.
EDIT: New idea for determining exact APK file name
1) adb pull /data/system/packages.xml
2) Look through it for your application's codePath entry
3) adb pull that
EDIT:  With regard to the old idea below, Matthew discovered that while the per-process files under /proc have read permission on a secured device, they are empty when read by an unprivileged uid other than that of their owner.  So this won't work.

1) Get your app running.  You'll also need a machine with adb.
2) type
adb shell ps

and look for the line with your app's name:
app_1     11959 907   112984 27580 ffffffff afd0c5bc S com.clevername.myapp

3) take the number in the second column which is the process id, and view it's virtual memory map, in this case I would type
adb shell cat /proc/11959/maps

and look for a line where it has mapped its own apk file into memory
43e9c000-43ea3000 r--s 001f4000 b3:06 15393      /data/app/com.clevername.myapp-1.apk

4) That's the file name you would need to adb pull
adb pull /data/app/com.clevername.myapp-1.apk .

Examination of the directory permissions in /proc suggests this should work for an unprivileged user, my apologies if it does not.  If you are familiar with the usage of 'grep' you can use that to avoid manually scanning the output.
Addendum: I'm not really sure what the story on apps installed to the SD card is.

I just tried on my secure device; adb shell cat /proc/####/maps returns nothing, unfortunately.

@Matthew... odd, I'm simulating the secure case and seeing most of the files in proc have zero size, but are readable.  Before I'd only checked that they would have read permissions.  Maybe it's done by nulling them rather than permissions so that /proc reading tools don't get a constant stream of access errors.  Oh well...  guessing at installed apk name variant may be the best.

My apk filename was all crazy and unguessable, but using packages.xml worked to figure out the real name.  :)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/3.0/


text:
Dell Streak's screen cracked - what are my options?
I hope this question is being asked in the right place - it's not a question about the Android OS, but it is about Android hardware. Please move it if it's better off on SuperUser.
I have just dropped my Dell Streak 5", and the screen has cracked.

I have a couple questions:

I have heard amazing things about Gorilla Glass - the machine is under a year old, has anyone else managed to get the screen replaced under the warranty because Gorilla Glass is supposed to be so strong? Then again, it could be that the screen under the Gorilla Glass is cracked...
Is the screen actually replaceable or is this effectively a brick?

I edited out your third question since shopping recommendations are offtopic.  The chatroom might be a good place to ask, though!

Found this on the Dell Forums:

My Dell Streak Gorilla Glass broke today...i was coming back from eating dinner with the family and walking up the stairs the DELL STREAK fell out of my jacket pocket....and bam crash boom..it has  all types of cracks and glass pieces all over the place...
SOLUTION....
I immediately called dell customer care to see what my options where and the CSR...WAS JUST GREAT. She went out of her way to take care of all my issues and she did...before i knew it she had ask for my service tag on my Streak...and some personal info and the next thing you knew it was getting a email confirming that my NEW DELL STREAK was on the way....UPS TRACKING # i was amazed....how quick it was being resolved....THANK YOU DELL

You can also probably get replacement screens off ebay, and I am sure there are youtube video tutorials on how to replace the screen.

I would assume the Gorilla Glass is not broken, just the underlying LCD display, but I would definitely argue that it should have provided more protection if I were trying to get a warranty claim fulfilled.  I would also assume the screen is replaceable, most are; talk to your carrier though (not sure if they'll route you to Dell).

In our case it'll be Dell - we bought it directly from them unlocked.


text:
Help with resizable widgets on Samsung Galaxy S 2?
I'm using the default launcher (TouchWiz 4.0). Some of the widgets can be resized which is great, but unfortunately it seems many others cannot be resized at all.

What causes this discrepancy?
Is there any other way to resize those seemingly non-resizable widgets?
Is there a way to tell in advance whether a widget (for example, one I am seeing on the market) is resizable this way?

Stock Android widgets are not re-sizable (although this is supposedly a feature that will be coming soon). If you can re-size some of them one of two things is going on: either the developer of the widget made it that way, or Samsung implemented this ability to work for some widgets. In the case of the latter they probably had to set it up specifically for the widgets that do it, so it is unlikely that any you find on the market are going to be re-sizable via TouchWiz. However, you do have another option. Launcher pro is a homescreen replacement app on the market; the paid version (yes the free version is misleadingly called launcher pro) offers resizing widgets as one of the added features. To my knowledge that would work for any widget regardless of how the developer made it. So if you're willing to put a couple bucks into it, you can re-size any widget that you want.


text:
How do I play MP3s from my Dropbox?
I have the Dropbox app on my Droid, and it can "download" files to the local storage on the phone, but for some reason, the music player app can't see those files.
How do I make the music playing app see the mp3s in my Dropbox? Is there an alternative way I should think about the problem or sync the files?

In Dropbox, simply add MP3s to favorites and they become available in a stock Google Play Music application (Tested in Android ICS)

That used to work for me, but after downloading the latest Dropbox, it no longer does. Now, even if I favorite an mp3 song on Dropbox and play it within the Dropbox app, it does not appear in my HTC phone's default music player nor Google Play Music.

I see. In this case, after tapping on a song it will be downloaded. Once it is saved, the Play Music app should see it.

If you export the tunes to the SD card rather than the music app then they will show straight up in the music player. Just a little annoying that you've got to do them one at a time rather than as a group.
Dropbox > More > Export > Save to SD card > select Music folder

PowerAmp seems to be able to scan the file system automatically. At least when I opened it, all my offline available sound files (regardless of format, I have many WAV and M4A files) were playable, while the solution with RescanMedia (amongst others) didn't work.
The Android version is 5.0.1. Dropbox and PowerAmp are from 12/13/2015. It costs 4 Euros (there is a 15 day trial) but to me this is worth it.

Some of the more advanced music players have the ability to rescan media from the phone.
In PlayerPro you can do Menu->Settings->Music Library->Refresh mediastore
This should then show up any music added since the last scan.

Hate to be the critic here but PlayerPro reports to no longer be able to Refresh the mediastore programmatically since 4.4 and will remove support for it (it would do that when media would be added to the sd card but I don't have one (yet) in my device...)

You can use Dropsync on your Android device to sync your device with your music folder on Dropbox.
In Dropsync, you pair a folder on your device with a folder on Dropbox. You then choose from several options how those paired folders should sync.
I pair a Music folder on Dropbox with my device's default Music folder. In Dropsync, I use the 'Download mirror' setting, so that any changes I make on Dropbox (add songs, delete songs) sync to my device, but changes on my device won't affect my Dropbox folder.
The stock Google Music Player then watches my device's Music folder and updates the music library automatically.

In dropbox just click the arrow on the right of the mp3 you want and use the "export" option and then save it to device. Done.

Indeed.  I would merely add that long-pressing a folder before export allows exporting all files in that folder at once.

all_licenses: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Why does "Google Services" take up increasing RAM and spawn new services over time?
I have a rooted OG Droid which I install custom ROMs to frequently. I've noticed in all builds of Froyo and Gingerbread that I've tried, over time of being on, certain services will take up more RAM and spawn new processes.
Specifically I've noticed that Google Services does this consistently. Initially it'll take maybe 7MB of RAM and only have 1 process (com.google.process.gapps). But after a good 10+ hours it'll spawn Android Core Apps (android.process.acore) and Calendar Storage (com.android.providers.calendar). Currently it's sitting at 21MB of usage.
This memory is never reclaimed and the phone will bog down as the internal Android task killer has to kill tasks more frequently. I eventually have to reboot.
Why does this happen and can I fix it?

Good question.  I've noticed a slow creep in memory usage but it hasn't been a problem on my Vibrant.

Yeah it's very much a big problem on the OG Droid which only has 256MB RAM

The additional processes are created on demand (e.g. if you open the calendar). The increasing memory consumption comes from the fact the Java is not able to release (heap) memory back to the system. That's why google has implemented the ActivityManager, which from time to time kills the whole process only to restart it later with a lower memory footprint. That is exactly what the task killer app try to do, which is kind of redundant.
The ActivityManger does it's job pretty good on my Galaxy S with only 329 MB RAM available to the system. I never needed no task killer. But, this is only a workaround for resource constrained devices like smartphones. Current high-end android devices have up to 1GB of memory or more, so that the ActivityManger will become more and more out of work.

Yeah but the problem is that the Android task killer is not killing the ever-growing processes like com.google.process.gapps and com.android.providers.calendar

@SAGExSDX How do you know that the Android task killer is not killing these processes? Isn't it possible that they need the resources from the beginning? But there is of course the possibility that they are whitelisted by the system and then there is sure a good reason why this is done.


text:
Update ongoing notification stuck after reboot
I selected to upgrade all of my applications, but my phone shut down for some reason during the upgrade. After restarting, I noticed that the upgrade was stuck so I cancelled the updates. Unfortunately, I still saw a notification that the other app were being downloaded. Even after restarting more times, clearing market data and killing the download process, the issue remains. How can I fix this?

Strange that clearing the data did not fix it.  However, you should be able to click on each of the apps that are pretend-downloading and hit Cancel.

I had already actually tried that. I then restarted a few more times and turned my Internet connection on and off and it eventually disappeared. I have no clue what fixed it


text:
Why most of the devices supported by CyanogenMod are from HTC?
Why most of the devices supported by CyanogenMod are from HTC?

Because, for the most part, HTC doesn't try to lock down their phones. Compare this to Motorola: all their phones have locked bootloaders except for the original Droid. However, Motorola has been showing signs that they might be changing this behavior in the future. A lot of the HTC phones can use the Unrevoked method to root their phones (except for maybe the Thunderbolt?).

And compare to Samsung: Their phones are very accessible, but have a ton of custom drivers. They're pretty hard to integrate into a AOSP-ish ROM.

Add to this that HTC publish his source code relatively soon after launching a device and the fact that their phones are pretty popular...you'll have the perfect ecosystem for hackers to play with this phones.

In the past, HTC phones have been the easiest to unlock, which directly translates to their hackability and therefore support from community developers.
Allegedly, newer HTC devices are a lot more restricted, which will put a damper on custom ROM availability.  I believe Samsung will soon take the lead in the "most hackable" category, and we'll start seeing more of their handsets on the CM's "supported" list.


text:
HTC Desire HD vibrating constantly
My girlfriend plugged her phone in to charge and it started vibrating, and never stopped. The only way to stop it is to power off the phone, and take the battery out. Even if the phone is off, it still vibrates if the battery is in.
She recently installed the eBay application, and tried removing that but nothing.
Running standard HTC/Telus (Alberta, Canada) 2.2.1. Phone has not been rooted or anything else. Phone is only 3 weeks old.
I have same phone, with no problems.
How do we make it stop?
Part 2:
Sometimes, after removing and replacing the battery it stops. But you just have to push on the back in a spot or two and it cranks up again. Seems like a hardware problem that we can't fix. Will probably end up going back to the Telus store to see what they say, and will most likely have to warranty it.
Still open to ideas though.
Part 3:
We can adjust the volume up and down, and it will go all the way up to full volume, make the little 'bing' noise to let you know the volume is turned up, all while still vibrating. Going up/down, changing the ring mode in settings, changing vibration settings in keyboard and other areas have no effect.

have you tried pressing the volume up/down rocker? I find with my HTC Desire, every so often I accidentally trigger the 'vibrate' profile via the volume rocker and it keeps vibrating (I think my case might be causing the rocker to be 'stuck'?).
Though your problem does sound like a hardware issue, so this might not be the solution you're after, but if the volume rocker can stop it vibrating will be easier than turning the phone off/on.

@pyko: Good point.  Is it possible that the volume down rocker is stuck and is causing the phone to constantly try and enter the "Vibrate only" state?

Definitely sounds like a hardware issue, I'd backup anything important and take it into the shop.

I'm with @GAThrawn on this one.  Time to get some use out of that warranty.

Hardware fault = return. Would be interesting to know what the vendor/manufacturer make of it, if anything.

Nobody posted it as an answer, so I'm going to: It's definitely a hardware issue.  There's no way that both the simple firmware for battery charging while the phone is off has the exact same bug as the software running when the phone is on.  Mark Wain's (deleted) answer indicates that he had a similar issue that, again, is best explained by bad hardware.

A warranty fix resulted in a working phone.

@Daniel Great :)

I had the same same problem and tried to take out the battery several times and when i turned the phone on again with the battery in, and is's vibrating all the time as soon as you turn on the phone. The phone will not not event get to the starting HTC screen. it vibrates all the time until you remove the battery again.
I found that when

The phone is turned off
Set the phone in the external HTC USB charger
It started with the standard start HTC screeen and every thing seems to be good now. I left it in the charger for some time now

I hope this post can help any one
/Pelle

There's a small chance that this will help you in some way, when you have this all time vibrating issue: in my case, I left a screw inside the phones case after I opened it to change the glass.
The screw somehow managed to get stuck between one contact of the vibrating motor, and the metal plate of the first case cover to remove. After reopening the phone and removing the screw the constant vibrating stopped. Phone was a HTC Wildfire and seems to work perfectly now.

Go to settings, accessibility, and turn of notification reminder.


text:
Other manufacturer's USB data cable for charging?
Is there any harm in using a USB data cable of any other phone (say LG) for charging up a Nexus S? "Any harm" here means will it adversely effect my battery life or the Nexus S device in any way?

USB data cables are pretty much interchangeable. Even on devices that have modified sockets to allow connecting a headset cable to the USB port, you can usually still use a normal USB cable for charging and data with no harm to the device.

I use an old Nokia cable on occasion with no problems.

What you might want to watch out for though are dollar-store chargers (either AC or car)... not really sure how the regulation on those is.

My HTC Desire and Kindle share the same style USB connector which is handy while traveling, I wish everyone would standardize on the same connector :)

Apple-related, but relevant to @ChrisStratton's comment: http://www.righto.com/2014/05/a-look-inside-ipad-chargers-pricey.html (related to chargers, not cables).

As far as I know, Nexus S uses the so called micro-USB cable, the same my Galaxy 5 does.
This is very good, because you can buy a generic cable like that in retail stores or shops that sells electronic stuff. I did so a few days after I bought my cell phone, and it costed the equivalent of US$4.00 in my country (Chile).


text:
How to Sync Text Messages from Outlook 2010 to Android
I went from the HTC "Tilt" running Windows 6.1 to the Samsung INFUSE running Android. I use an exchange server plus Outlook 2010 at my office. I can no longer send/receive text messages from my desktop. Everything else sync's fine. Does Android support an exchange between the PDA and the desktop for text messages?

SMS Backup + will sync SMS messages to your GMail account, you can then sync those to your outlook using Google Apps Sync.

No, not directly.
However, if you use Google Voice, you can have all your text messages emailed to you, which would allow you to sync them.
Link to Google Voice

There is a messaging app called Touchdown which will sync SMS. It is not perfect but I'll never go back. You can see more on their website.

I don't see anything on that page about SMS, nor on their Android Market page.


text:
Can I use Gmail while offline?
Is it possible to download the new emails from the Gmail account while online, and then read them while offline? Is it possible to write emails while offline that will be sent when online?

Yes.  And not just for the inbox, but inbox and sent may be the only folders synchronized by default.
From within the android gmail client:
Press menu
select more
select settings
scroll down and select labels
change the number of days from which you want messages kept on the phone
change individual labels (effectively folders) to none, this number of days, or all

NOTE: this answer was written about a now obsolete version of the gmail app, which continues to change in its user interface over time.  The answer will not be updated to track that evolution, as there are multiple versions in use at any time which behave differently, and it is ultimately the idea rather than the specific steps which are important.

Good catch, dude.  I totally overlooked this.

You had the right idea, almost posted it as a comment to yours.  Oh, got to remember to take my phone back out of airplane mode ;-)

As far as I know, gmail will "cache" your most recent emails.  If you have to "search" or browse through any labels, you probably won't be able to get to those emails. But your inbox (or at least the most recent in the inbox) should be available to view since your last sync.  Additionally, you should also be able to draft emails while offline (and save the drafts), you just won't be able to send them until online again.

Yes, you can view locally cached emails, even those from years ago as long as your sync settings allow. But you can't do offline search!

Is it possible to download the new emails from the Gmail account while online, and then read them while offline?

Yes, but only for your inbox I think.  If you open your inbox on your phone while you have a connection and let all of the messages you have unread propagate to your phone, then close the Gmail app and put yourself in airplane mode you can reopen the Gmail app and read through your unread messages.

Is it possible to write emails while offline that will be sent when online?

Yes.  If you compose and send an E-mail normally the messages that say "Sending..." will go out as soon as you have a connection again.  I just tested this by using airplane mode.

The MailDroid app gives a lot of storage options to allow offline caching.


text:
Are there cases where Android would start an app/service other than due to Intents or explicit user start?
I'm trying to understand how/why some of the processes that are running on my phone (DroidX, stock 2.2 ROM).
It's obvious that 2 likely reasons for a process to start are:

A direct action by the user/another program to start it (e.g. click on the icon of an app, or another process launches the .apk explicitly)
An Intent is registered by the app, and the event associated with that intent happens.

The question is, are there other reasons/causes/mechanisms by which a process could be started in Android? (aside from Intents or direct launch).
P.S. As a plausible theory, something could be started off of init.rc (being how Android is based off of Linux) but I don't know enough about Android internals to judge if it launches any apps via init.rc

Possibly helpful: You can use the Autostarts app to see all the different system events and what apps register for them.

@Matthew - I'm going to post a separate question about Autostarts, as a matter of fact, but just as a response to your comment, doesn't Autostarts merely list all registered Intent receivers?

A raw native process can be created by any of the usual unix-like mechanisms.
An android activity or service is usually forked off by zygote (in response to an intent), but I think there's an obscure way to start a vm by hand using app_process.

"usual unix-like mechanisms" - could you please clarify? I'm interested specifically in what would trigger the start of the process (e.g. some crontab entry? process scheduler respawning recently dead processes? etc...)

Well there isn't a cron daemon on there right now, but anyone could make an unprivileged one with an ordinary app, or root and install a real one.  Ditto inetd (at least for unprivileged ports).  And yes, the framework does respawn things it doesn't think should have died.  There's really very little restriction on process creation; security is more in terms of it being quite hard to start a process as a userid that's able to do more than be obnoxious with shared resources.

could you please clarify in greater detail "the framework does re-spawn things it doesn't think should have died"? That sounds significantly closer to what I was looking for as a plausible reason why some processes keep popping up on my phone.

@DVK: in some cases background services are terminated prematurely since the foreground application needs more memory, Android may restart the service later to finish the operation.


text:
Is there a way to list all Intents and all processes associated with them?
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), 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

Perhaps not all, but you can get a pretty good idea using:
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:

Does this dump all registered activity, or only intents that are actually triggered while the command runs?

I believe all registered one, but really IDK because IDK how to check...

make sure to run adb shell first :)

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.

According to several other similar questions on Stack Overflow, such a list is not available via APIs.
I'm not sure how apps like Tasker produce such lists. I wouldn't rule out iterating through all possible intents via the queryIntentActivities() function, or even parsing each installed app's manifest file.

I think adb shell dumpsys package resolvers receiver is pretty much what you are looking for.


text:
Different notification tones for multiple Gmail accounts
Is it possible to use different notification tones for each Gmail account?  I.e.:
account1@gmail.com => tone X
account2@gmail.com => tone Y
Maybe with a helper app?

The GMail app already appears to do this on a per-account basis. Simply open an account, then navigate to (Menu button)->More->Settings->Select Ringtone. This works fine on my version (2.3.4.1) and allows me to set a different ringtone for each account.
You can also use this to cause some accounts to provide vibrate/audible notifications while others do not. For example, my work account is set to vibrate "for all notifications", but my other accounts have their vibration set to "Never".


text:
How can I rate an app in Honeycomb?
Seems like I can't find out how to do the basics on my Honeycomb tablet.  How do you rate an app in the Market?

Your folder question is covered on another question: http://android.stackexchange.com/questions/7734/how-do-you-create-a-folder-on-a-home-screen-in-honeycomb-3-0-1-xoom

As your comment suggested on the other answer (now deleted), you can't.
The Android Marketplace app on Honeycomb seems to be very close to the web version which (at the time of posting) didn't allow ratings/comments.
Sorry to be the bearer of bad news!

thanks, luckily the market can be updated sooner or later and add this feature. I am frankly shocked that it was taken out for now.

The newest version of the Market (3.1.6) allows you to rate apps now. I'm not sure exactly when it was released, but it was rolled out to the Motorola Xoom as part of the 4G LTE upgrade. There's an XDA thread for the new version which has discussion about installing it on other devices (I got the update when my Xoom was upgraded, so I'm not sure about stability and the like). I'm not positive if it requires a specific version of Android to work (i.e. 3.2) or if it will work on all versions of Honeycomb.
Rating works pretty much like the phone version. You go to the app's page on the Market and there is a "Rate & Review" link on the left side of the page.


text:
Mice and Keyboard support in 3.1
Apparently, Android 3.1 will support USB devices such as mice and keyboards.

How much of an issue is driver support? If you have a "normal" keyboard or mouse, will it just plug and play?
Does the OS provide support for these input devices through standard Android controls, or will each program have to be modified seperately to support these input devices?

Most (pretty much all) USB keyboards and mice support the USB HID protocol. You might not be able to use some special "media keys" or other advanced features, but standard features will work without additional drivers.
As for routing USB Input to standard Android UI events, I suspect they'll do it (they'd be stupid not to) but couldn't find any conclusive information as of yet.

I've just tried a normal Microsoft USB mouse on my ASUS EEE Pad Transformer running Android 3.1.
It works just fine both in pre-installed applications (I tried the browser) and in third-party applications that I'm pretty sure have no dedicated support (they are not even adapted to 3.0 yet).
And as @Patrick noted, pretty much all USB mice and keyboards support the USB HID protocol, so you won't need specific per-mouse drivers.


text:
lock ES File Explorer or similar options
I want to lock ES file explorer, so that it can be opened after I put a password or pattern lock.
Is it possible in ES file explorer?
Is there any other file explorer that provides similar functionality?

There are many apps on the market that allows you to password-/PIN-/pattern- protect other apps, see: https://market.android.com/search?q=app+lock


text:
What's the difference between "sd card" and "usb storage"?
Under Settings -> Storage, I see entries for both "SD card" and "USB storage". What's the difference? What should I be using each of those for?
In addition, how can I control what data goes where? since so far, everything I've copied into my mobile (via USB cable and via Kies Air) seems to go to the "USB storage", as the "SD card" is almost completely empty of data.
Finally, where can I find the base folder of each of these, using a file explorer?

On my Samsung Galaxy SIII the same screen has entries for "Device memory" and "SD card". So what your device calls "USB storage" is the same as what my device calls "Device memory", and it refers to the internal SD card. The external SD card, the physical microSD card which you manually insert into your phone, is what is being referred to on this screen by the name of "SD card".

Have just noticed this too on my (original) Galaxy S since it got the Gingerbread update, presume that this is something that Samsung have changed in their Gingerbread build, as the S2 comes with  Gingerbread from the factory.
On the Galaxy S (and I presume it will be the same on the S2) they have a built-in storage (either 8GB or 16GB in the original S) that looks like an SD card to the OS, but is actually built into the phone, there is also a Micro-SD card slot, that can take normal micro-SD cards. On my device it looks like "SD Card" is the built-in storage space (8GB on my phone), whereas "USB Storage" is the separate SD card that plugs into the slot by the battery and you can plug the card in yourself (I've got a 32GB card in mine).
Previously these showed in the phone as "Internal SD Card" and "External SD Card". Since Gingerbread (see the screenshots below to see the contents of Settings -> Applications -> Manage Applications on an Android 2.3 Gingerbread LG Optimus Net smartphone), internal storage (including the internal SD card and excluding any possible ROM space) is called "Internal storage", which in the screenshots below amounts to a meager 150MB on the device where the screenshot was taken, whereas the space occupied by the external SD card, appears as "SD card storage", which in the screenshots below amounts to 16GB. It also appears that on Gingerbread (at least this is the case on my LG Optimus Net), it is not possible to see the amount of read-only-memory (ROM) which is present inside the smartphone (on such LG Optimus Net device this space amounts to 512MB according to the specs; newer devices don't have ROM, they just have a single internal SD card for internal storage):

Here is the screenshot of the Settings -> Storage screen on the aforementioned Gingerbread LG Optimus Net device. This screen uses the term "SD card" to refer to the external SD card and the term "Internal storage" to refer to the internal SD card excluding the (internal) ROM storage:

On the Samsung Galaxy SIII there is no internal ROM (just an internal SD card space and an optional external SD card space). On such device, the naming convention is different:
the interface accessed from Settings -> More -> Application manager calls "Device memory" the amount of internal SD card storage which is not allocated to system files but to user files (on my system a total of 11.3GB available for user files out of a total of 16GB for the internal SD card), whereas "USB storage" is the storage available on the external SD card (which when inserted as on the screenshot below amounts to 16GB for a 16GB microSD card):

On the Samsung Galaxy SIII the Settings -> More -> Storage screen is slightly inconsistent as it calls "Device memory" the total amount of memory on the internal SD card, and "SD card" the stuff available on the external SD card, as the screenshots below demonstrate:

So, the naming conventions used across various devices or even across the same device can be inconsistent and confusing. As long as you know how to interpret these terms on your own device you'll be OK.
Also, most apps don't know that there's two separate storage spaces, as this is a Samsung thing, not an Android thing. Media files copied into either location will be picked up OK by the media scanner, so you can put your music, etc where you want without any worries. Some apps, like the Camera app, have been modified by Samsung to know about the multiple storage locations and will let you save to either (configurable in the settings); others don't, and will only save to the internal storage space.
Here is the option allowing you to save to either location on the Samsung Galaxy SIII Camera app:

I haven't had a chance to play with Kies Air since Gingerbread, so can't help you there (but I will try to over the weekend and update). But for File Manager apps you should be able to see the folder /mnt/sdcard which is the internal SD card and looking down that you should see a folder called either external_sd or extSdCard which, if you open it is your micro-SD card. For any apps that let you pick where to save files, saving to this location will ensure its on the actual external SD card.

Indeed, there is an external_sd folder under /mnt/sdcard. I think the simplest thing will be to just move big files like music and videos there, and leave the apps to the regular internal memory.

@Oak That's what I do, use the external SD for all my music, videos and file transfers between PCs and leave the internal storage for apps to save to, and the camera.

On my Samsung Galaxy SIII there is no /mnt/sdcard/external_sd folder for the external SD card but I think if inserted the card would mount under /mnt/extSdCard since on my phone this folder exists but is empty.

On Galaxy S3, /sdcard (AKA /mnt/sdcard) refers to internal storage (which to the OS looks like/is an internal SD card), /mnt/extSdCard to an SD card to be plugged into the micro SD slot. USB storage in the user interface refers to the external storage, and /mnt/UsbDrive[A-F] refers to any USB stick that would be connected to the USB port using a dedicated USB OTG cable or attached to a USB hub attached to the USB cord via a USB OTG cable.

Some phones (e.g. SGS2) divide their internal storage in two parts. One is used for core system files and applications, while the the other for user files (pictures etc.). On sgs2 the first is called "Internal memory" and the second "USB memory".
As a bonus, clicking the "Move to SD card" will move an application from the "Internal" to the "USB" memory, even if an actual SD card is present.

On my galaxy note 1 it says in my storage (off the top of my head) Internal storage 1.7gb available, USB storage 11.50gb available and the SD card storage says 2.50gb available. As i only have a 4gb SD card in it at the moment it can only mean one thing and that is that the USB storage is part of your internal phone storage.

On my Samsung Galaxy Ace II, you can see all your  'sd-cards' under /storage.
sdcard0 is the main internal storage, extSdCard is the sdCard I put in myself.
I have UsdDrive A to F in there but all are empty. I believe the data saved in Usb Drive (as you can see in the settings) is on the same sdCard.
I am not sure if you need root to access this file.


text:
How do you trace incoming/outgoing HTTP connections on a rooted Android?
I would like to get a trace of any incoming & outgoing requests over HTTP from my android phone over a period of time (like you can do with Fiddler on a PC) - is there tool apart from WhisperCore that can do something like this?
The reason i don't want WhisperCore is because it needs to encrypt your whole device before it lets you use the tracer

try tcpdump, netstat combination.

It probably depends on what specifically you're trying to achieve.  Are you trying to trace what calls an application is making, or just what the browser is doing?  Is the device rooted?

You could use your computer to host a wireless connection, and proxy through Fiddler

Shark/Sharkreader in market (tcpdump frontend)


text:
How do I sync and share Calendars from multiple Google accounts with my phone?
I have some questions regarding to Android's default calendar app in Galaxy 5 (five).

I am working with two Google accounts, but my calendar app shows calendar of only one account which is marked default. How to see events in calendar of other account?
How can I sync events of Android calendar and Google's online calendar?
How can I share events of my calendar to other Android device or my friend's Google calendar?

Assuming you upgraded your Galaxy 5 to Android 2.2, you can do the following:

To sync and see calendars from both accounts:
a. If you already added your other GMail account, skip to step c.
b. Add your second GMail account under Menu -> Settings -> Accounts & sync -> Add account -> Google and follow directions there.
c. Tap on the newly added account and make sure the "Sync Calendar" option is selected and exit out of Settings.
d. Open up the Calendar app and go to Menu -> More -> Calendars expand the newly added Google account, which should show you all of its available calendars.  Keep tapping the button  to the right of each calendar until both icons are enabled, and the text under the account name reads "synced, visible", and tap the OK button.
e. You should now be able to view the second calendar's entries in the Calendar app (or any app that accesses Google calendars.)
Any events you create on your phone via the Calendar app and assign to a GMail account will automatically sync to your online GMail account.
Instructions for sharing your Google Calendar with a friend can be found here.

Chank, here in India we don't have any official upgrades from samsung and I don't want to void my warranty. So my phone is still in 2.1... :-(

I can't remember if 2.1 allows multiple GMail accounts or not.  If it does, then the idea is the same, only the menus are slightly different.  In either case, my answers to your questions 2 and 3 still apply.


text:
Only automatically connect to certain Wi-Fi networks
I have an HTC Desire with Android 2.2.
My problem is that there may be open Wi-Fi networks nearby that require a password once connected, e.g. hotspots at coffee shops. My phone connects to these, thereby blocking the 3G connection.
What I want to do is always use 3G unless I'm in range and connected to a list of certain Wi-Fi networks.

It auto-connects to any open WiFi network, regardless of whether or not you've used it in the past? I don't think I've heard of an Android phone doing that before.

The issue Lars is referring to is seen most often at coffee shops and restaurants.  Both Starbucks and McDonalds offer free WiFi, but after connecting you must first pull up a web page and accept the terms and conditions before your device gets full data access.  The next time you are near enough to connect to that AP, your device automatically connects, and will have no data until you realize it and pull up the web page and accept.

Go into your Wi-Fi settings. Long press on the networks that you don't want to automatically connect to and tap 'Forget'.

Thanks for this idea. The problem I have with it is that it is a little cumbersome for people who travel a lot and will see a lot of WiFi networks like that.

@Lars: I'm still a little unclear on your problem here. You should only have this issue with wifi networks that you've actually used in the past, but your phrasing in your question (and this comment) almost implies that your phone is connecting to any open wifi network you encounter. Do you just use a lot of different wifi networks? Are you encountering a lot that are all using the same SSID or something?

I am the IT guy for a small business, and we all have HTC Desire phones. Many employees will attempt to connect to an open WiFi and find that it is a captive portal. Once they connect, they will forever have that problem. I guess I can just instruct them to do as you say here.

You could try Wi-Fi Ruler.
With Wi-Fi Ruler you can set up which access points you want to automatically connect to and which ones to ignore.
This might be good if you want to remember the settings (just in case you want to connect again) but still avoid connecting to the AP.

I suggest that when you disconnect to a wifi network, you also forget it.
It will not connect to a WiFi network that you have not explicitly connected to in the past, so as long as you forget the WiFi network, it won't connect.
I regularly find myself doing this, although I rarely turn my WiFi on.


text:
How to browse Internet in Samsung Galaxy Fit using Broadband in Windows 7?
I have a Samsung Galaxy Fit smartphone and want to browse the web on it using BroadBand connection (the one i use for my pc connection to Internet) in Windows 7.

possible duplicate: http://android.stackexchange.com/questions/2298/how-to-set-up-reverse-tethering-over-usb

i have checked that question and there seems no solution to that problem .There is an answer but its not working properly and question posted was one year back

From everything I have read about this topic, it is possible to do on a linux machine, but not with a windows machine. this could be because of something with ADB on windows, or the USB drivers for windows.
Here is the info (note that this reference was done with a Nexus One):

Requirements:

Android 2.2 (or an older version with a root tethering app)
ADB from Android SDK, or a rooted Android 2.2 with terminal in root mode

STEP 1:
Device: Connect USB cable and activate USB Tethering. You should see on linux new network interface.
STEP 2:
On Linux Computer, setup a bridge:

usb0 is the new network intreface
eth0 is the main interface connected to internet (or a gateway)
$ sudo ifconfig eth0 0.0.0.0
$ sudo ifconfig usb0 0.0.0.0
$ sudo brctl addbr br0
$ sudo brctl addif br0 eth0
$ sudo brctl addif br0 usb0
$ sudo ifconfig br0 up
$ sudo dhclient br0

See Network Connection Bridge Help to setup bridges
STEP 3:
Setup usb0 interface of your phone. You have to options:

From your computer, execute:
./adb shell netcfg usb0 dhcp
Or in a root terminal on your phone, type:
su
netcfg usb0 dhcp

You should now be able to connect to Internet on your phone using your computer's Internet connection.
Try to do a ping www.google.com to be sure
STEP 4:
To shut down the reverse-tethering, first unbridge interfaces on your computer:
$ sudo ifconfig eth0 down
$ sudo ifconfig usb0 down
$ sudo ifconfig br0 down
$ sudo brctl delbr br0
$ sudo ifconfig eth0 up
$ sudo dhclient eth0

Then on your phone, uncheck the USB Tethering option

on running ./adb shell netcfg usb0 dhcp ,i got error: device not found

i am using a DSL connection and upon running sudo ifconfig eth01 0.0.0.0, i got this
SIOCSIFADDR: No such device,so i renamed the connection to eth0 ,then it worked fine

i didn't switch off usb tethering

The best and simplest idea in the long run would be to get a wireless broadband router that also supports ethernet (wired networking). Your pc can still use cables and your android phone just connects to it using wi-fi.
Without a wi-fi router you still have a few more options that work with Windows, as long as your pc has wi-fi (which you can get using a simple USB network card that costs less than 20 USD). In this case you have a few options (in order of recommendation):

Use software to turn your pc into a wifi router that shares it's internet connection. Instructions are available here.
Setup an ad-hoc network with Windows and then root your android phone to enable it to see ad-hoc networks using the instructions found here.
Use Wi-fi Direct which is a new protocol that'll work with Android 4.0 and Windows 8 (not very helpful, I know).


text:
How to solve: "Failed to push selection: Out of memory"
I Create an article in Stack overflow. But as I found this site, I decide to ask the same question here, because I still need your help.
I have made the following steps:

Launch Eclipse
Go To: Window -> Open Perspective -> Other ...
Select DDMS from the opened dialog
Select "File explorer" tab.
Press "Push a file onto the device" and select library which I wish to push.

Failed to push selection: Read-only file system

Minimize all opened windows and open Command Line
Write: cd C:\android\android-sdk-windows\platform-tools enter
Write: abd remount enter

You will see remount successful

Maximize Eclipse and try step 5.

Failed to push selection: Out of memory

Error appears! What to do to solve this problem ... Please help.
ADDED
1) When I write ADB SHELL MOUNT:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock0 /system yaffs2 rw 0 0
/dev/block/mtdblock1 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:0 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0

2 ) Shel Prompt starts with: #

Development questions are considered off-topic here according to our FAQ.

I read the word "Eclipse" so I voted this to close, but now that I read the rest of the post and the linked post, I'm starting to think that this is a good example of questions you get while developing an application that are not really development question. I can't retract my close vote, but I can warn other people not to cast close vote so fast.

I agree with @Lie that this is a grey area. I say this should stay open for now.

@ViTo Brothers Apoyan: I have two questions 1) What output do you have when you do adb shell mount (this will give you all of the filesystems mounted in the device and their mount options)? 2) when you do adb shell, does the shell prompt starts with # (which indicates you're root) or $ (which indicates you're not root)?

also you tagged this question with android-x86, android-x86 != android emulator running on x86 host machine. Are you actually using android-x86 or just the regular emulator?

@ Lie Ryan I have added answer in my post !

Launch the emulator from the command line so that you can specify a /system partition size using the -partition-size <MB> option. For example, I use this to launch an emulator running Android 1.6 with a /system partition of 512 MB:
emulator -avd Donut -partition-size 512

...where "Donut" is whatever you named your AVD (you can check in Eclipse's AVD manager if you need to). The emulator binary should be in your tools/ directory within your SDK install, which for you appears to be C:\android\android-sdk-windows\tools, so be sure you cd into that directory first (or add it to your system's %Path%).
Eclipse may not pick up the emulator right away, or it may recognize it and then drop the connection. If either of those happens, click the view menu on the Devices tab (the little arrow next to the minimize button) and select "Reset adb" to get the connection back.
Once it shows up in your devices, do what you were trying to do earlier. Run adb remount to get the /system partition in read-write mode, then use Eclipse to push the file wherever you want. I tested with a couple of random files a minute ago and was able to push them to /system/xbin without any trouble.
For reference, here's the partition size and use of /system on my Donut emulator when I specify a 512 MB partition:
> adb shell df
...
/system: 508416K total, 61332K used, 447084K available (block size 4096)
...

But here's how it looks if I launch without specifying a size:
> adb shell df
...
/system: 65536K total, 61204K used, 4332K available (block size 4096)
...

Additionally, you can set command line options in your application's run configuration via Eclipse if you want to. Go into your Java perspective, then select Run->Run Configurations from the menu bar. Select your application in the left pane, and then pick the "Target" tab. At the bottom is a text box labeled "Additional Emulator Command Line Options", and you can add -partition-size <MBs> to that text box so that the emulator launched when you run your application will have a larger /system partition.
Note: You may have to add also -no-snapstorage or other options, to disable loading the existing snaphot, to the command line. It did not work without it for me.

Thank you very match !!! You solve my problem !!! thanks a lot !!!!!!!

The easy way: restart your phone in Recovery mode, than mount System. Now you can push your file without a problem.

I assume you've missed the line /dev/block/mtdblock0 /system yaffs2 rw 0 0 in the question? So what should change when you mount it from recovery? Full is full, you don't gain additional space on a full file system by mounting it "from elsewhere".

How to solve: “Failed to push selection: Out of memory”
While creating new android virtual device(AVD)..
   on SD CARD tab type some value(100) in MB.
Really,It works for me!!

This is not correct. Creating a virtual SD card will not help you push files to the /system partition as the question asks. They are completely unrelated storage areas.


text:
Locale app & export settings
Is there any solution to backup Locale settings? I've defined couple of rules and I don't want to lose them while I reinstall some custom ROM.

possible duplicate of How to backup an Android device?

The first answer to that question mentions Titanium Backup, which (if you're rooted) can be used to back up individual apps.  I'll add an answer for non-root.

I don't think this is a duplicate. While backing up the whole device would, in effect do what Hubidubi wants, exporting the settings from the app could be used for more than just backup.

Quoting from the Locale's feedback forum regarding the Backup/Restore functionality:

AUTOMATIC BACKUP/RESTORE
  Locale has
  automatic backup and restore using
  Android 2.2's cloud-based backup
  mechanism. There are no configuration
  options within Locale--it just works!
To use this feature, simply make sure
  that backup/restore is enabled by
  going to the Android Settings ->
  Privacy and verifying that the
  checkboxes for Backup and Restore are
  both checked. Whenever Locale is
  uninstalled and reinstalled, the
  device is factory reset, or you
  upgrade to a new device, the
  situations will be automatically
  restored as long as Android is set up
  with the same Google account.
Locale's backup and restore is
  designed to work correctly across
  different devices with different
  hardware and software capabilities.
  For example, let's say a backup was
  made on a device with Wi-Fi and
  restored to a device without Wi-Fi.
  Locale will properly handle that
  transition.
Automatic backup and restore requires
  Android 2.2 or later, as well as a
  handset supporting Google's backup
  manager. If there are no options for
  Backup and Restore under Android
  Settings -> Privacy, then the device
  does not support backup and restore.
Since backups are tried to a Google
  account, be sure to always use the
  same Google account when setting up
  your Android devices.
MANUAL BACKUP/RESTORE
  In addition,
  there is a beta manual backup/restore
  feature to create a manual backup to
  the SD card. This feature is disabled
  by default, and must be manually
  enabled. After backups are enabled, a
  new Backup menu item will appear under
  the menu of the Locale home screen.
  From that menu item, you can create a
  backup to the phone's SD card. When
  Locale is re-installed, it will
  automatically detect any existing
  backups and ask whether you'd like to
  restore them. Because manual backups
  are a beta feature, we are unable to
  offer any support. To enable manual
  backups, please follow these
  instructions:

Allow installing apps outside of the Android Market
  a. Go to the Android Settings
  b. Tap on Applications
  c. Tap on Unknown sources
Install Backup Enabler
  a. Open the web browser on your phone
  b. Go to this address: www.twofortyfouram.com/backup.apk
  c. Once the download completes, tap on the download
  d. Follow the instructions to install
Perform backup
  a. Open Locale
  b. Choose Menu -> Backup


text:
Sideloading Apps on Google-TV
Even though a new version (which includes the android market) is coming out for the Google TV this summer, I'm a little impatient and slightly curious.
There are a few apps that I'd like to try out on the google TV that I don't think would necessarily break anything (i.e. apps that come to mind don't use sensors, camera, etc) so I'm wondering if there is a way to sideload apps into the current generation of the Google TV?
There is no support for opening APK files natively, but I wonder if I hook my computer up to the STB via USB, if I could run some adb blackmagic and inject apps into it.
Any thoughts or opinions?
And yes, I am aware the current apps out there aren't optimized for a google TV, but I'm looking to add some basic functionality to hold me over until the next version comes out.

Unfortunately the ADBD (adb daemon) is not enabled on any current Google TV hardware, so adb connectivity is not possible via USB, Ethernet, or any other means.
However, a few crafty tinkerers from GTVhacker site managed to hack the Logitech Revue unit to enable this functionality.  Keep in mind that this is a hardware hack and includes physically opening up the Revue box and soldering connections on the motherboard.  You can read more on this mod here.  Needless to say, this hack is not for everyone, and carries even more risk of bricking the STB as a plain software hack.

Of course things can never be easy, eh? I got my Revue unit for free by being a web developer and entering their giveaway, so it wouldn't be a financial loss if I bricked it. But I have incredibly bad luck when it comes to hardware, so I think I might be just forced to wait until official support is added. Sigh.

@Foxtrot: I hear ya. I intentionally don't own a soldering iron, specifically to deter myself from ruining (expensive) hardware :)

Haha +1. Same here. Additionally to deter myself from burning down my apartment. Like I said, I have really bad luck.


text:
Which, if any, of the major console game developers also develop for Android?
The Android market has a lot of apps now, and for the most part almost anything that could only be done on the iPhone a couple of years ago is now possible on Android. The app stores have become quite competitive and comparable.
However, one thing that appears to be missing from the Android Market are major console game developers. iOS, for example, has many titles by publishers such as Electronic Arts, SEGA, and Square Enix. Some of these are ports of console games (like Sonic the Hedgehog), and some of them are made-for-mobile games (like Square Enix's Chaos Rings). I don't see anything from those publishers in the Android Market.
So, my question is are there, in fact, any major console-game developers/publishers currently selling games in the official Android Market? If not, is there any reason to believe this might change?
Note that my question is about Google's Android Marketplace and does not include any 3rd party markets. I'm aware that Electronic Arts is selling apps in Amazon's store.

Gameloft has been reluctant to publish on Android Market because of their own DRM policies, but lately they have been changing their stance and putting more of their games on Android Market.
EA has plenty of titles up for sale as well (in Europe, see EA Netherlands).
Some other big names like iD Software and Epic have mentioned a strong possibility of bringing ports to the likes of Rage and Unreal Engine to Android some time in the future as well.
And then of course, there's Zynga, if you're not getting enough spam from their apps on Facebook.

Square Enix and Sega have several now, too.

How did you search for the publishers? Electronic Arts, for example, most certainly has applications in the Market. I only see one Square Enix game, though.
Beyond that, the Xperia Play will be supported by a line of Playstation titles. They're already starting to hit the market, in fact. I wouldn't recommend purchasing them unless you own an Xperia Play since I have no idea what running them on a non-suported device would entail (or if it's even feasible - I'll leave that to XDA), but it's another angle to it.
Whether or not they'll continue to update them or develop new games...I could only speculate, really.


text:
How can I fix this time-zone problem with calendar events that started after installing Android 2.3?
I'm using a Nexus One on T-Mobile in the US. A couple months ago my OS was updated to Android 2.3. Since then I've had a weird problem with my calendar events.
I can view calendar events just fine, and the calendar syncs with my Google Account bi-directionally without issue.
When I create a calendar event, the "time zone" option defaults to my current time zone, "GMT -4, Eastern Standard Time", just like it did on Android 2.2. However, when I touch the time zone option to select a time zone, there are two time zone entries that match mine. One is "GMT -4, Eastern Standard Time", the other is "GMT -4, Eastern Time".
The problem happens when I edit an event. Frequently, when I edit a calendar entry, the event jumps 4 hours ahead unless I manually edit it back down. For example, if I create a calendar event and set the starting time to 1:00pm, when I edit the event I've created the edit screen will show a starting time of 5:00pm. It still shows the correct time zone, but it adds the 4 hour GMT difference into the event's starting time. If I save the event without adjusting it back down, the next time I edit it it will say 9:00pm. This happens regardless of whether the event was originally created on the phone, or if it was created on my desktop PC by visiting http://www.google.com/calendar. It doesn't seem to matter which of the two "US Eastern Time" options I select when creating an event on the phone. This problem did not exist before I installed Android 2.3. It doesn't happen with every single event, but I haven't been able to figure out what the common element is between the unaffected events. It does seem that events that are freshly-created are less prone to this problem (possibly the problem starts after the data's been synced a few times?)
If I create a calendar event on my phone, and then edit it on my desktop PC using http://www.google.com/calendar, the PC edit screen behaves normally, and the changes sync back to my phone without issue. Only when editing events on the phone do I experience this problem.
It's very annoying that I have to dial my events back 4 hours every time I make a change to them. I've experimented with different settings but I haven't been able to figure out how to make this go away. Does anybody know how I can fix this?

On Eastern Time vs Eastern Standard Time: the difference is whether daylight savings adjustments are taken into account.

I had a problem with a secondary calendar which sounds similar. On edit the time zone changed. I went into the calendar and made sure all of them were set to my time zone. Each calendar has changeable time zone on Google calendars.

Thanks! I found that one of my three calendars had the GMT +0 timezone instead of my correct Eastern Time. I've changed it, and I'll watch it for a while to see that fixed it.

Yep! That was it. Fixing the time zone for the one calendar fixed the issue. I don't know how it got changed since it was apparently working right before, but thanks a lot for giving me the solution to this long-time annoyance!

I would suggest clearing the Calendar data and re-syncing the events from your Gmail account(s).
Go into Menu -> Settings -> Applications -> Manage applications -> All then scroll down to Calendar, tap on it, and tap on the "Clear Data" button.  Do the same for the "Calendar Storage" app.  Now go back twice (exit to the main Settings menu) and go into the Accounts & sync section.  For each account you added, go in and toggle the "Sync Calendar" option off and then back on again.
After the calendar data finishes synchronizing, try editing an existing event again and see if the issue persists.
P.S. You might need to re-enable the visibility of one or more calendars in the Calendar app by going to Menu -> More -> Calendars and ensuring the ones you want are set as "synced, visible".

Thanks for the suggestion. Just tried that, but unfortunately it didn't solve the problem.

I just figured out the fix and I'm no techie. After reading several of these posts I noticed someone said to uncheck a setting under calendars. I unchecked the box that said "use home time zone" after setting time to my zone. It worked even though I can't tell you why. I have only had my android for a week and have not traveled out of this time zone. I probably just checked the box not realizing what havoc it would cause!

My Samsung S-iii/Android 4.4.2 causes a 4 hr shift on my outlook calendar, even if the event was originally generated by Google's Holiday posting...if it's a reoccurring event.  Daily, monthly, annually, anything initiated on my android that is reoccurring displays the shift. And finding and turning on or off the time zone lock on either my Samsung calendar or my Google calendar doesn't seem to help.  However, any one time event, such as a doctor appointment, seems to come out okay regardless of calendar of origin.
So my personal work-around:  if I need to post a one-time appointment, I do it on my smartphone without much concern (so far...).  However,  if I need to post a reoccurring event, such as a class, I only post the first event, with a occurrence reminder in the title, like "Handball, MWF."  In this way, the next time, after a sync, I see the first event on Outlook, it will remind me to reenter it on my PC as a reoccurring event.

On my LG Android (Lollipop) I went to Calendar>Settings>Calendar Settings and unclicked "Lock default time zone".  This stopped my west coast appointment times from constantly being translated to EST.

My work outlook sends the appointment with a timezone of
TZID:New Zealand Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+1300
TZOFFSETTO:+1200
(I am in New Zealand) so this look reasonable.
The start time for a 7:30pm appontment on 7 April 2017 is:
DTSTART;TZID=New Zealand Standard Time:20170407T193000
but Android doesn't process this correctly regardless of my calendar timezone settings.
With timezone (New Zealand) on, it adds it with a 0 offset so it appears as an appointment on the 8th . I can manually then set the timezone of the appointment to NZ time and the appointment now shows correctly.
I note that an appointment created on android, for the same timehas
DTSTART:20170407T070000Z
This is a simpler way of specifying the date/time in a timezone independant way.
My conclusion is that it is a bug (incompatibility) between outlook and google calendar, so the workarounds expressed here don't really work.

Uncheckinge the "use home time zone" option also fixed it for me, although I am at a loss to know why this is so, especially since I didn't travel outside of home. Now, if I could only figure out how to keep google calendar and contacts in synch with MS Outlook, I'd be a happy camper.

Remove the account and re-create it. It fixes problem.

set the clock in you phone to the correct time zone -- then make weeks start on Mondays -- the problem will be fixed quickly by the phone

I don't know how mine got 4 hours ahead of itself, but I fixed it by changing my time zone to the west coast and back, and then it was OK.


text:
Project my screen of my Nexus One
I have a Nexus One, I would like to know if there is any way for me to project my screen content to my large screen TV?
Nexus One does not come with a hdmi port.
Thank you.

By "project", do you mean "play video"? Because that might be a bit of a challenge, depending on your network and (phone) CPU.
To just get screens/presentations, you could connect a laptop to your TV and a VNC server on your phone.
If you do want to play media files, and you have a DLNA client (Xbox 360, PS3, one of the million media boxes like Roku) connected, you can install a DLNA server on your Android (search Market - there are plenty) and stream media.
Plenty of the latest TVs even have a DLNA client built in.