I have noticed that the LOGCAT of my HTC One is getting flooded with messages from a "DropBoxManagerService" after I upgraded my device to Android KitKat 4.4.2.
I'm seeing this message repeated over and over again:
02-28 16:37:39.089 773-1376/? D/DropBoxManagerService﹕ Found time mapping 1393414988780 -> 1393414988780
It's outputting so fast that IntelliJ Idea's LOGCAT window is complaining: "Too much output to process". It can go on for hours before it settles down, and then starts again at some (apparently) arbitrary point in time.
I have tried to reset and disable the DropBox App, but it doesn't help. I'm suspecting this "infinite loop"-like behavior to be the culprit for a heavy battery drain issue, so I'm desperately trying to find a solution for the problem.
The service name is not getting listed by task-killer Apps.
Any good ideas are happily received!
I was told by a HTC Taiwan customer support manager that this is a bug of Google Play Service for Android 4.4.2 Kitkat, and all Android phone manufacturers like Samsung, Sony, etc. also suffers from this bug. (I wonder if it is true?) Please wait for update from Google.
I found this DropBoxManagerService message flooding bug will be triggered when there are new app updates available in Google Play Store. I can't see the update notification but my phone will become hot and battery drains fast. Reboot the phone will stop this flooding temporarily and Google Play Store will show update message immediately after reboot.
By the way, "Wipe cache partitions" does not work for me.
I tried reset htc one max to factory setting. It works.
The annoyed log will disappear.
You have to wipe the device's cache partition. After that the issue is solved as I noticed so far. No DropBoxManagerService flooding and no battery drain.
Hold power button and volume down key together until device powers off and you see black screen
Release power button only while you still keep holding down volume down key
Release volume down key when you see OS menu options
Use volume up/down keys to scroll and highlight "recovery" and press power button to select
When you see the icon that looks like a phone and orange "!" mark in a triangle, press power button and volume up key together once
It will display more options
Scroll to "wipe cache partitions" and press power button to select
Once wiping cache partitions is completed, select reboot
Related
Really weird issue but when I try to click once it doesn't register on the emulator but then I click again and the click registers. This is using AVD. Every other click seems to trigger in the proper place. This has nothing to do with my app just base image.
Take a look at this:
https://www.youtube.com/watch?v=axvxtGj4HPo&feature=youtu.be
and notice the first click doesn't register.
I notice the age on this thread, so not sure if you have already figured this out. I ran into something similar like this today in which no clicks were being registered at all. This issue still persisted even after closing and reopening the simulator. One thing I did notice is that the power button still worked.
I ended up fixing this by:
Clicking and holding the Power Hard Key
Restarting the device OS by clicking the Restart
After the OS Reboots, everything seems to work again.
Note: the Hard Key for power is the power button next to the volume controls on the right.
In my case it usually happens when the size on disk is very high (see in AVD Manager) and the solution in my case is to make a Wipe Data
Update #1 (Because the solution from above not always works)
Another thing I found is that when you want to swipe up from the Google bar does not open the apps menu. Then I open first the Messages app or Chrome and close again. From there the Swipe up works again.
I have found that Android recent app dialog can be disabled by disabling
package com.android.systemui. I want to run my (rooted) device in kiosk mode so it is essential that the recent apps dialog not be shown on long press.
Now, exactly what does com.android.systemui do? I don't need notifications and power indicators and stuff so it is OK if that kind of cosmetic stuff disappears. It is also OK if soft input home buttons disappear because I have replaced them with a software app (Button saviour).
Is it safe to disable com.android.systemui, or do I risk subtle system hangs in certain unclear situations? To put it shortly -is it just another app, or is it absolutely essential to the Android operating system? (I haven't experienced any problems this far!)
Is com.android.systemui available in all Android versions?
If you completely remove SystemUI.apk from the system, your device will hang on start-up and never fully boot again. Tried it before. ;) Framework-res and the system have some dependencies on SystemUI.
The correct, non-invasive way to get rid of SystemUI is to have an application that force-closes it upon BOOT_COMPLETED via am force-stop com.example.systemui or kill <PID>. Depending on device SystemUI restarts itself (not always), if it does you'll have to set a Timer that repeats the kill process. There's an app on Play store that does this, but I can't say for the reliability.
Hope this helps,
I have it disabled on my phone succesfully via removal; gone is the ugly top bar with the notifications and clock.
Drawbacks are that native screenshots won't work nor does the recent apps switcher, but both issues can be fixed via replacements.
Battery life increases slightly due to lower CPU usage.
(I9500 cyanogenmod 11)
Here's the idea. I have a HTC Desire HD phone, rooted, custom rom (JellyTime 4.2.2) installed. This is the second time this has happened:
After a phone restart, phone gets stuck when loading on splash screen. I see the animation, then it stops, but splash screen stays for infinity amount of time. Last time this has happened I had android debugging on, I used android-sdk for adb reboot recovery. And got it working again, but this time I wasn't cautious, and I don't have the debugging enabled. You might ask Why not go into recovery mode using power+volume combination? Well, I can't. My volume - button is broken. So here I am, with a stuck phone, with no apparent way to reach recovery mode. Any suggestions, guys? I'd be grateful.
EDIT: I was asked to define broken. The button IS missing, but even without being missing, the bottom button simply doesn't react when you click it mechanically.
By holding the volume up I was able to get to fastboot, and then I entered my recovery mode.
I am having an app in the store which runs fine on most devices but on one particular
Samsung Galaxy S2 running Android 4.1.2 (version JZO54K.I9100XWLSS).
It crashes on startup without a crash-report from google or from crashlytics which i integrated. Its not actually a crash it just flashes the main activity a while until the phone shuts down:
A video of that behavior:
https://dl.dropboxusercontent.com/u/523370/20131004_115027%5B1%5D.mpeg
Its a device from a user, so I cannot debug it locally. (Is there something to get a live logcat stream from the phone over the air?)
Has anyone experienced such a "crash" on start only affecting one particular device?
I have a SGS2 where it works without flaws. Could there be any hardware reasons resulting in such a crash e.g. Memory issue.
I know this problem is not likely to be resolved without any further source code / crashreports, but maybe someone can point me in the right direction.
best regards,
Mike
Actually shoe rat saved my day!
Because shoe rat just commented on the case I am answering it for completeness.
The user enabled the option
"Do not keep activities" which lead to this strange behavior, because an activity was killed during the splash screen.
As a future reminder to myself I will get rid of the splash screen because its not holo-style anyway.
Cost me a lot of time to figure this out and i probably wouldn't have found it without your help.
I was playing around with my tablet and testing my program, when there was a notification that said bug report captured and whether I would like to share it. I had not seen this message before so I clicked Yes, and then I clicked OK on the warning dialog box that asked me to share it only with people I trust. After that the gmail app opened up which had a screenshot of my tablet, as well as a file attached to it called bugreport<some numbers, date and time I think>.txt. I did not send the bug report as I was not sure what it was and where it would go. However my question is,
what exactly is this bug report?
Is it generated by the code that I was testing? Or is it generated by the android system itself?
Did I trigger something unknowingly when I pressed the hardware buttons (the tablet only has 3 hardware buttons, volume up/down and power)?
I have been trying but I cannot make that message appear again, and when I search for bug*.txt using my file viewer app, I cannot find the file. Where is that .txt fil that got attached to the bug report get saved on my tablet?
It's because you have turned on USB debugging in Developer Options. You can create a bug report by holding the power + both volume up and down.
Edit:
This is what the forums say:
By pressing Volume up + Volume down + power button, you will feel a
vibration after a second or so, that's when the bug reporting
initiated.
To disable:
/system/bin/bugmailer.sh must be deleted/renamed.
There should be a folder on your SD card called "bug reports".
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2252948
And this one: http://forum.xda-developers.com/showthread.php?t=1405639