Related
Not sure if it's just me, but every/any time I try to open up the USA Today app, my phone reboots.
I've tried clearing data, clearing cache, uninstalling/reinstalling and the same thing - click the icon, splash screen, droid animation...
Anybody else?
dew.man said:
Not sure if it's just me, but every/any time I try to open up the USA Today app, my phone reboots.
I've tried clearing data, clearing cache, uninstalling/reinstalling and the same thing - click the icon, splash screen, droid animation...
Anybody else?
Click to expand...
Click to collapse
LOL yep, USA Today reboots the phone. Whats going on Motorola?
TRF-Inferno said:
LOL yep, USA Today reboots the phone. Whats going on Motorola?
Click to expand...
Click to collapse
Ok, glad it's not just me!
Absolutely love this phone, but was beginning to think I might've gotten a lemon. Guess will just have to wait for the JB update :fingers-crossed:
dew.man said:
Ok, glad it's not just me!
Absolutely love this phone, but was beginning to think I might've gotten a lemon. Guess will just have to wait for the JB update :fingers-crossed:
Click to expand...
Click to collapse
Weird - it doesn't happen to me.
olm3ca said:
Weird - it doesn't happen to me.
Click to expand...
Click to collapse
And the plot thickens lol
I installed the app just to see, and it reboots my phone after the splash screen as well. (on wifi)
No problems here - that "do you want alerts?" notification pops up immediately after the splash screen... maybe a coincidence, but worth mentioning... I guess.
jntdroid said:
No problems here - that "do you want alerts?" notification pops up immediately after the splash screen... maybe a coincidence, but worth mentioning... I guess.
Click to expand...
Click to collapse
doesnt happen to me either. I said "no" to alerts -- if it's rebooting, did you say "yes" to alerts?
Never even got to that point.
dew.man said:
Never even got to that point.
Click to expand...
Click to collapse
Is this freshly downloaded or being restored from a previous account? I wonder if you have the right one for ICS. Mine is v. 1.9.
Xatt said:
Is this freshly downloaded or being restored from a previous account? I wonder if you have the right one for ICS. Mine is v. 1.9.
Click to expand...
Click to collapse
Fresh installed. Even tried uninstalling and reinstalling from the Play Store.
Wonder what the difference is!?
dew.man said:
Fresh installed. Even tried uninstalling and reinstalling from the Play Store.
Wonder what the difference is!?
Click to expand...
Click to collapse
I'm wondering if it's some conflict between two apps.
Update: took a quick look at the reviews and see one person reporting it -- are you dmitry?
Xatt said:
I'm wondering if it's some conflict between two apps.
Update: took a quick look at the reviews and see one person reporting it -- are you dmitry?
Click to expand...
Click to collapse
I've got the same problem here. Weirdly, it also occurs when I try and use the AP Mobile app. Happens if I'm on wifi or mobile data.
Maybe part of Moto's plan to deny us access to quality news apps?
I came to the boards to see if this random rebooting was just my problem but seems like it is not. My phone has been rebooting for the last 3 nights in a row around the same time, 10pm eastern time. No clue what is causing it.
Also tried the USA Today app and yes it does reboot the phone.
Very strange...
Another issue I have is....my phone screen kinda flickers and starts getting brighter from dimmed screen.
Anyone else gets this?
UPDATE: I just saw this in the general section - http://forum.xda-developers.com/showthread.php?t=1919581
and I also installed Nova Launcher recently and I feel like that might be the culprit...This is really really strange.
Anyone else having this come up? Previously I was getting the msm_hsic_host wakelock, but now its this? Github seems to suggest its Chrome related so I've removed that and its still the same after rebooting and leaving it for awhile. WiFi is on, no mobile data or any bizarre apps installed.
Any help? Thanks!
Sent from my Nexus 4 using xda app-developers app
Done a factory reset this morning to no avail, still coming up. There must be someone who knows a little more!
It still shows without any app installed?
Try Franco kernel
Yup.
Even with Franco kernel, still shows up the same error.
Is nobody else getting this? Seems absurd!
same issue
Had the same issue.
i deactivated chrome and wakelock was gone.
cyberfrog77 said:
Had the same issue.
i deactivated chrome and wakelock was gone.
Click to expand...
Click to collapse
How does one do that?
I know this must have been discussed already but I need a solution personally for my phone as xda forum has always been helpful to me.
Since today it started happening that my GPS is off but gps icon on statusbar randomly starts flashing .
Whats the solution?
thahim said:
I know this must have been discussed already but I need a solution personally for my phone as xda forum has always been helpful to me.
Since today it started happening that my GPS is off but gps icon on statusbar randomly starts flashing .
Whats the solution?
Click to expand...
Click to collapse
Same here.....Wanam caused it for me. Disabling Wanam stopped the issue but now I have no Wanam
Trying to troubleshoot this now
moSess said:
Same here.....Wanam caused it for me. Disabling Wanam stopped the issue but now I have no Wanam
Trying to troubleshoot this now
Click to expand...
Click to collapse
I did the same.
thahim said:
I did the same.
Click to expand...
Click to collapse
Even after disabling Wanam it came back Aargh!!!!
:crying:
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
I'm looking for suggestions for figuring out the cause.
I'm not rooted.
I tried clearing cache in recovery.
The wakelock exists even in airplane mode.
The wakelock goes away after a reboot, but reemerges at some point.
Any ideas on what to try or where to go from here?
Thanks.
stokholm said:
I'm looking for suggestions for figuring out the cause.
I'm not rooted.
I tried clearing cache in recovery.
The wakelock exists even in airplane mode.
The wakelock goes away after a reboot, but reemerges at some point.
Any ideas on what to try or where to go from here?
Thanks.
Click to expand...
Click to collapse
Install betterbatterystats with the steps without root and find the culprit : https://www.google.nl/amp/s/www.xda-developers.com/stop-wakelocks-android-without-root/amp/
I have this too, found anything yet?
asc366 said:
I have this too, found anything yet?
Click to expand...
Click to collapse
Just installed GSam Battery Monitor Pro and currently waiting for it to happen again.
stokholm said:
Just installed GSam Battery Monitor Pro and currently waiting for it to happen again.
Click to expand...
Click to collapse
Let me know, i was unable to drill down using bbs
asc366 said:
Let me know, i was unable to drill down using bbs
Click to expand...
Click to collapse
I had to use a Magisk module to make BBS a system app to get it to work in Oreo. Even with root priveledges it wasn't collecting any data.
jhs39 said:
I had to use a Magisk module to make BBS a system app to get it to work in Oreo. Even with root priveledges it wasn't collecting any data.
Click to expand...
Click to collapse
Found out what the wakelock was? Im not rooted.
asc366 said:
Found out what the wakelock was? Im not rooted.
Click to expand...
Click to collapse
I'm not either, but with an ADB command you can grant permission for battery stats anyway.
It's a kernel wakelock. I'm not sure where to go from here. What's the best place to reach out to OnePlus, to have this fixed?
I suddenly face the same issue..
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
swa100 said:
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
Click to expand...
Click to collapse
I have
swa100 said:
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
Click to expand...
Click to collapse
Me neither.
Some people in the Oreo Beta thread seem to think that its a Bluetooth wake lock and that if you turn off Bluetooth and then reboot your phone it goes away.
I had a wake lock problem before I figured out how to get BBS to work but it went away after a couple days. I'm not using the stock kernel though--I'm using Lightning Kernel which blocks some wakelocks automatically and allows you to block others using the ElementalEx kernel control app.
jhs39 said:
Some people in the Oreo Beta thread seem to think that its a Bluetooth wake lock and that if you turn off Bluetooth and then reboot your phone it goes away.
I had a wake lock problem before I figured out how to get BBS to work but it went away after a couple days. I'm not using the stock kernel though--I'm using Lightning Kernel which blocks some wakelocks automatically and allows you to block others using the ElementalEx kernel control app.
Click to expand...
Click to collapse
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
swa100 said:
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
Click to expand...
Click to collapse
OP here. I have Bluetooth on all the time. But as I said, even in airplane mode the wakelock won't stop.
stokholm said:
OP here. I have Bluetooth on all the time. But as I said, even in airplane mode the wakelock won't stop.
Click to expand...
Click to collapse
Theres ppl claiming you need to actually boot with bluetooth disabled. Not just switching to airplane.mode but actually starting your phone without bluetooth. Have you tried this?
swa100 said:
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
Click to expand...
Click to collapse
I use Bluetooth a lot and I'm not having that wakelock problem but the kernel I'm using might be blocking it. Several people have said if you turn of Bluetooth and then reboot your phone the wakelock goes away. It's definitely worth trying.
I ended up going back to nougat. This wakelock was killing my battery life. Going to report the bug now.
edit: reported. See: https://forums.oneplus.net/threads/wakelock-after-using-bluetooth-devices.704688/ follow/reply would be great!
More and more people seem to have these problems:
https://forums.oneplus.net/threads/wakelock-after-using-bluetooth-devices.704688/
And in general: https://forums.oneplus.net/feedback/?node_id=243
Can anyone confirm if this bug still occurs on the stable version or on open beta 3?