Tag Info

Hot answers tagged

8

Have a look at this discussion. Is your problem same as the one discussed here? If so, Google is working on a fix.


8

The android issue tracker is located at http://b.android.com. you can report the issue there.


6

Saw this on another site: Ryan answered 4 weeks ago I was having the same issue after I updated my Galaxy S3 to Android 4.3. I think I just fixed it. Here's what I did: From the home screen, click the Apps icon Open the "Downloads" app In my case the files that kept showing up in the notification pull down were in the Other Downloads tab Click the ...


5

The Android Bug Report system. Search to see if someone has already suggested the feature, then submit your idea using the feature request template.


5

How long have you had your phone? One common cause of intermittent headphone connections like this can just be that after carrying your phone around in your pocket for months, it has picked up "pocket fluff" in the headphone socket. At first this just squashes down out of the way when your headphones are plugged in, but after a while so much builds up that ...


5

The official issue database for bugs/features/etc. of the Android OS can be found here. Copied from Bryan Denny's answer to another question.


4

I had the same problem, tried cleaning cache and data with no result. So I went in settings > applications > manage apps > all, picked the download manager and "uninstalled the updates". It told me the app would reset to factory settings, and when I started the phone again, it was running marketplace 3.4.4 and I managed to update and install apps normally ...


3

DONE: I backed up all my contents of my old emulator, created a fresh emulator using android create avd -t <TargetID> -n <EmulatorName> -a --abi <CPU/ABI-Used> To aid finding out the correct value of <TargetID> and the admissible values <CPU/ABI-Used> corresponding the same as per your choice of the API level, I used android ...


3

This is a known bug in Android (even in certain Eclair systems). There's a widget called Headset Blocker that when added to any of your homescreens and activated prevents the music player from playing whenever you unplug your headest. Freeware and it works. See if it helps.


3

I would try and clear the cache of this application menu Settings Applications Manage Applications All Market Clear cache Just to see whether this should help. You might also want to click the 'Clear data' button but than you must login to your account again.


3

Adding additional home screens is not a stock Android feature so I can't comment specifically, but clearing data for the launcher application should work. Settings → Applications → Manage applications → Launcher (might be named differently) → Clear data You will lose your current home screen configuration, of course, but this should take care of the ...


3

There is a lengthy discussion about this on: http://androidforums.com/droid-support-troubleshooting/87515-my-droids-touch-screen-going-crazy.html The main point seems to relate to either oil and dirt covering the screen and/or heating up issues from dirt within internal components. There are some suggested solutions such as carefully cleaning the screen ...


3

The Android issue tracker can be found here.


3

I reproduced the exact same issue on my Nexus 10 after upgrading to KitKat. Cycling power on the device after the update resolved the problem for me.


3

I also recently upgraded my Note2 from 4.1 to 4.3 and was having the same problem. I installed the Wakelock Detector by UzumApps and found that the Noom Walk pedometer app was waking the screen. I uninstalled the Noom Walk app and the screen no longer wakes. The Noom developers have posted a test APK which can be found here: ...


2

I had this problem recently with my milestone 2. Unfortunately I had to send it to service. Now it works, but whole touch panel was replaced with a new one. Just to clarify my problems: right column of touch panel (above search button, btw it didn't work as well) didn't work for more than one month. In more extreme weather conditions (temperature below 0 ...


2

After doing some more research, I found a thread with a lot of users having the same exact problem: Their solution is to use either Headset Blocker or Disable Autoplay apps. This seems to have sort of worked. Just make sure that taskkiller isn't disable either of these. I am still experimenting on how to fix this issue... Edit1: I still see the same ...


2

"Getting slow" can be caused by a couple of different things -- separately or combined. It could be an app hogging your CPU, or the system running low on free RAM. It's even possible that some service runs havoc, blocking resources (though this one would be a bit harder to track). Easy tracking for beginners (and for free) There are several possibilities ...


2

That's dangerously ignorant. I just checked today with a trustworthy site, and indeed, my Milestone² was affected as well. The source is known to be the stock dialer, so HTC phones are affected as well (at least unless they're running Jelly Bean already). I'd tell them to please give this statement in written form on company paper (with the HTC header), so ...


2

You will know if the kernel has hung, the led light stays on and not go further. As for your question, you need to be more clearer and specific as we do not know and since you posted a similar question before. You have not stated, what device is it, what android version is it, what kernel is it, all those are left out and thusly playing a guessing game ...


2

I updated the software to 4.1.2 and the problem has gone :-) I don't know if the bug has been fixed, or the process of upgrading has corrected the faulty state the phone was in. I'll update this post if the problem comes back...


2

Note that my other answer is more of a workaround (but also something recommended by many even without problems) that is almost guranteed to fix the problem. This is a direct fix which will most likely work, but I can't say that with absolute certainty as I can't recreate the situation myself. After some googling, I've noticed that your icon (as you point ...


2

This depends upon the ROM that you're using. If its stock, you're stuck, for most OEMs don't allow sending big reports as such. If its a google device, or any other device running AOSP, then, the link you've posted is appropriate. Be sure to provide as much related and useful info as possible. If you're running custom ROMs, they'd often provide you with ...


2

No. Motorola really did a shitty job of patching the ICS rom for the Xoom2 ME. the IR blaster didn't work for a couple months, and this speaker bug is indeed software. There is an app by Wyrm on the Play Store that fix some of the speakers issues: https://play.google.com/store/apps/details?id=wms.xoom2mespeakersfix ...


1

In my case the problem appears to have been caused by the "manage locking" section of JuiceDefender. Turning that off solved the problem.


1

If you have any custom lock screens, un-install them. This will make the annoying behaviour stop. At least it did for me. There was some funky systems settings between the lock screen app and next launcher that you get prompted for. This made the default lock screen come up (not the one I was trying to use). To recap, this happened with the NeXt launcher ...


1

This sounds a lot like the bug introduced in Android 4.1 Jelly Bean that (probably due to DRM and encryption) will install any paid application to /mnt/asec, even if it contains an account service. This has a side-effect of having all accounts associated with such apps being removed on every reboot. This Google Code issue has more details. As of Android ...


1

The same thing happens on my Nexus 7 running 4.2 and as answered in the other question the only way I found to get the screen back on was to perform a "soft reset". Hold down the power button for around 30 seconds, the device should start a soft reset (i.e. you don't lose any data/settings etc.) and reboot. Not really fixing the root cause of the issue but ...


1

Try uninstalling winamp first, and see if the issue is still there. There seems to be, by the sound of it (no pun intended), conflicts with the stock player and winamp, and both are trying to get a stranglehold on the media playing, competing with each other.


1

It looks like you'll have to do a factory reset.



Only top voted, non community-wiki answers of a minimum length are eligible