I once encountered similar behavior which was triggered by Ambient Display feature inside Settings. There is a guide on OnePlus Forums here (see Usage of Privacy Guard & Built in Settings (All Users)) which mentions this:
Ambient Display – this is again another option under the Display section of the Settings, when turned on (is ON by default) ...
At least for me, it was actually the device password - used to unlock the phone. So basically it asks for the device password when you try to add a new Google account for some reason. I formatted my phone thinking something else was the issue - but if you enter the device password, it then asks for the account name as normal.
Nothing to worry about, unless you have downloaded an app suggested by the pop-up.
In More detail:
It's an old issue. You visit a normal website, and suddenly you see pop-ups telling you that your phone has a virus.
It's called scareware. It's basically "ads" which scare you into downloading their "anti-virus" apps. Many times, the apps you ...
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 "...
What is a "blue screen"?
Certain Android devices sometimes become unresponsive and display a plain bright blue screen with no text on it. See photo.
What should be done?
(This answer is based on what someone on IRC once told me.)
If you only ever see a blue screen once or twice a month, ignore the problem and restart your phone when it happens.
If you ...
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 ...
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: http://noom.uservoice.com/forums/...
I had the same issue today. I had to replace my old (broken) Nexus 5X to a new Nexus 5X.
After unsucessfull tries (same error message as you) I started to all reconfigure manually when I noticed my old Nexus 5X was running Android 7.0 and the new stock Nexus 5X was still on Android 6.0.
So here is what I did: I accepted the update to Android 7.0, then did ...
From what I know the rollover is not the only problem, also an additional week counter 13 bits is introduced. A new data format (with larger data) can of course cause problems if unsupported by the GPS receiver firmware.
Also I have read that some GPS devices use the week counter for plausibility checking of the received data. If the week is smaller than ...
Just pulling all files via adb to a WIndows computer has multiple problems:
Android/Linux allows multiple files in one directory that just differ in their case.
The file-system on Linux allow characters in file- and directory names that are disallowed on Windows
Some file-names are completely disallowed on Windows which are just regular file-names on Linux/...
If you're using the stock Android keyboard, you can report it on the central Android bug tracker. Be warned that there are already more than 25000 reports there, and many never receive any response from Google.
If you find a bug in a third-party keyboard you're using, visit the keyboard's page in Google Play (either through the Play Store app or on the ...
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
I've had positive and reliable experiences running Android 5.0.1 on Nexus 10, Nexus 7, and Nexus 5.
However, my Nexus 4 experiences reboots with Android L and a friend's Nexus 4 outright powers down regularly.
That said, a bugfix Android 5.0.2 is rolling out to Nexus devices right now. So wait.
The answer to your question is no, the Google Play Store does not include a built in bug report feature.
In order to submit a bug report, you should first check the developer website to see if such a function is provided. If not, your best option is to email the developer or, if the issue concerns other users, post a public comment.
It does not appear to be possible to keep notifications from rotating positions on the lock screen in Android 7 Nougat. See explanation below, and the way to disable this action in Android Lollipop.
This appears to be desired behavior. See explanation below.
Priority notifications rise to the top. See http://www.greenbot.com/article/2854634/master-...
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...
I have discovered the solution (at least for my Nexus 7)! Here's what happens:
Tap Take Bug Report
Take bug report "take a while" popup displays - Tap report
After about 30 seconds, the words "bug report captured" appear for about 2 seconds on left side of the top manu bar (the one with Time and Wi-Fi and other icons).
An adroid icon then displays on the ...
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 ...
"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 ...
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 ...
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:
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 ...
I am sure if you have tried heading over to the Facebook app over the Google PlayStore and have read their description over their you would have got your answer anyway,you can report to the bugs over the Facebook Help Centre.
Note: You need to log yourself over the Facebook account in order to do so.
I recently had the same issue - I have an old Samsung Galaxy S with Android 2.3.6. I think somehow an app got updated when I was on WiFi, but I didn't know what it was. I noticed a "sync" icon appeared and would not go away.
I finally realized I could go to Settings → Applications → Battery Use, and find out that YouTube was the culprit.
Then I ...
Factory reset will resolve this issue! To get to that option though you have to be in recovery mode. To boot to recovery mode press the power button and volume up button simultaneously! And then you will get this screen:
Then just reset to factory version and it should work!