Develop Bugs

Phone waking up on 4.2 :(

When I lock the phone using the power key after certain time it wakes up again automatically... It keeps happening... Any way to resolve this, which application is causing such an issue
Sent from my Galaxy Nexus using xda app-developers app

cldwar said:
When I lock the phone using the power key after certain time it wakes up again automatically... It keeps happening... Any way to resolve this, which application is causing such an issue
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
man, that's already the 3rd if not 4th thread abut this issue, one being opened by myself...
glad that I'm not the only one...
at beginning I thought it'd be a faulty/bent usb connector, as experienced by others, but since I am redaing of others with the same problem after upgrading, then it cannot be...
have you install;ed the OTA or started from cratch? have you cleaned dalvik cache? (I did with no avail) do you see a pattern in your wakeups? is it every x minutes? is it at random?
as regards me, it happens also when wifi and 3g and sync is off (but 2g on, that is I can only receive calls), so it cannot be anything related to signals...
I have installed BetterBatteryStats and will be sending a couple of resports to the developer trying to see if he can understand what is going on and what wakes up the phone...

I did a completely clean install... Wipe data and cache... Installed the OTA rom available on developers section.
Do tell me if you are able to find a solution.
Sent from my Galaxy Nexus using xda app-developers app

Check this bugreport:
https://code.google.com/p/android/issues/detail?id=39829

Yeah, the same thing happens to me. VZW Toro. Stock AOSP Rom. I think it's related to daydream. It didn't start happening until I enabled that functionality.

angel.de.marc said:
Yeah, the same thing happens to me. VZW Toro. Stock AOSP Rom. I think it's related to daydream. It didn't start happening until I enabled that functionality.
Click to expand...
Click to collapse
nope... daydream is off on my phone

It seems to be an issue with the WeChat app:
http://code.google.com/p/android/issues/detail?id=39625#c12
That's the original bug report. Star it for news and increase its visibility.

VuDuCuRSe said:
It seems to be an issue with the WeChat app:
http://code.google.com/p/android/issues/detail?id=39625#c12
That's the original bug report. Star it for news and increase its visibility.
Click to expand...
Click to collapse
what's wechat? something stock? new in 4.2?

Dunno, but follow the issue on that link. Answers ougta be there soon...

I do use WeChat .. let me delete this application and check ...

Deleted WeChat and disabled Day dream ... 7 minutes and phone is not waking up .. seems like the problem is resolved. ..

cldwar said:
Deleted WeChat and disabled Day dream ... 7 minutes and phone is not waking up .. seems like the problem is resolved. ..
Click to expand...
Click to collapse
I don't have wechat and the problem is there so no it's not wechat

I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.

tanmack33 said:
I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.
Click to expand...
Click to collapse
cant b wifi, , mine wakes up also when wifi is off and 3g is off and sync is off
I have tried with bbs as well but found notjing wrong

i've read all the reports of bugs, and the people with issues seem to have flashed the stock AOSP rom.. i dont have any of the issues described and the way i installed 4.2 was first flashing the takju 4.1.2 with nexus toolkit and then i got the 4.2 OTA from "about phone"->update.. oh and i have daydream activated.

For those of you with high android system usage, are you downloading music from Google pay music for offline usage? I did and I got this sudden increase. this has never happened to my phone before. Maybe Google play music needs update?
Sent from my Galaxy Nexus using xda premium

tanmack33 said:
I am in the same boat, Thegios.
No Wechat... No Daydream.
I have noticed my screen waking about every 10-15 minutes. It only happens when connected to my Wifi. My N7 does not wake at all. I have wiped the Cache and noticed my "Android System" hogging my battery stats.
I am trying to search what Apps I have settings for something like "sync only on wifi"... from there I should be able to find what is turning the screen on. I have BetterBattery Stats installed, and am trying to dig a little deeper there as well.
Click to expand...
Click to collapse
My problem is resolved by removing WeChat and daydream disabled...waited for like an hour and confirmed about the problem solution that worked for me.
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app

cldwar said:
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
it didn't work

cldwar said:
My problem is resolved by removing WeChat and daydream disabled...waited for like an hour and confirmed about the problem solution that worked for me.
You can try disabling that sleep mode apps in Apps settings.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Your problem may have been resolved but wechat and daydream is not the solution to this as many of us aren't using either and still having this issue. I think I'm going back to bone stock 4.1.2 and going to let the OTA upgrade me to 4.2 and see what happens.
wechat is NOT the solution people, as the Google Code page suggest this is a sync issue that could be caused by a number of apps.

opensourcefan said:
Your problem may have been resolved but wechat and daydream is not the solution to this as many of us aren't using either and still having this issue. I think I'm going back to bone stock 4.1.2 and going to let the OTA upgrade me to 4.2 and see what happens.
wechat is NOT the solution people, as the Google Code page suggest this is a sync issue that could be caused by a number of apps.
Click to expand...
Click to collapse
Sorry to report this but my phone has been bone stock since I bought it, got the 4.2 OTA, not using wechat or daydream and I still have this issue.

New Samsung Link draining battery

Is anyone else having this issue? It was fine when it was Allcast. After it updated to Link it's a really bad drain.

Nope I never use all cast though. I'd just freeze it. Unless you use it.
Sent from my SPH-L710 using Tapatalk 2

I never use it either. I'm going to freeze it, later. It's like it's constantly trying to find something to sync to on its own.

metalfan78 said:
I never use it either. I'm going to freeze it, later. It's like it's constantly trying to find something to sync to on its own.
Click to expand...
Click to collapse
That's Samsung for you.
Sent from my SPH-L710 using Tapatalk 2

Did you make sure that allcast is turned off under settings?

Yea, it was turned off. I uninstalled the update and decided not have the battery drain now. There seems to be something wrong with the update.

metalfan78 said:
Yea, it was turned off. I uninstalled the update and decided not have the battery drain now. There seems to be something wrong with the update.
Click to expand...
Click to collapse
How can I uninstall the update?

It showed up in my app list in the play store.

I'm too having the same problem in my galaxy s3 after an update to samsung link.. How can i freeze samsung link??

Battery drain with Samsunglink
I am facing the same problem with my Samsung Galaxy S3. There are no ways to stop the application which is running in the background. even if you force it stop, it has no effect.

madanambat said:
I am facing the same problem with my Samsung Galaxy S3. There are no ways to stop the application which is running in the background. even if you force it stop, it has no effect.
Click to expand...
Click to collapse
Got no idea else than uninstalling the update. Uninstalling update successfully solved the problem of battery drainage..

I uninstalled my Samsung apps, which I never use anyway and disabled what I can and that seems to have fixed the issue.
Sent from my Samsung Galaxy S3 using TapaTalk

I just noticed this problem today. I also noticed that the quick settings notification for Allshare isn't displaying correctly. It's showing that Allshare is off but when you dive (deeply) into the settings you can see that it's still active. I made sure it was switched off and I'll see if this fixes the battery drain.

New Update to android wear app

Guys, just received new update to android wear app v 1.0.4.1611133
Sent from my SM-N910C using Tapatalk 2

I updated, but don't see anything different on my watch.

Yeah.. That's the funny thing.. Nothing new in the change log too... They were the same features from earlier version... May be the interim one needed for the coming big update of v2.0 and wear OS w5.0.1 rumoured to roll out coming Wednesday
Sent from my SM-N910C using Tapatalk 2

Same here, no difference. Probably needed for the new upcoming update.

I did get my watch rebooting when I installed the update.. I thought, new update, but no.. ohh well.

eatonjb said:
I did get my watch rebooting when I installed the update.. I thought, new update, but no.. ohh well.
Click to expand...
Click to collapse
It updates Play Services to 6.5.90 (from 6.1.xx) on the watch.

I updated to this and paired my 360 with my new Moto X. I've been getting the "OK Google" at the top every time I look at the watch. I'm not sure if its the reset/pairing or update.
Anyone have this?
Sent from my XT1095 using XDA Free mobile app

trrubicon06 said:
I updated to this and paired my 360 with my new Moto X. I've been getting the "OK Google" at the top every time I look at the watch. I'm not sure if its the reset/pairing or update.
Anyone have this?
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Say "Ok Google" and do a few voice commands and it will go away.

My standard stock watch faces no longer display the date.
Is anyone else having this problem?

After i updated the android wear app, my whatsapp notification no longer vibrates the watch. The card's are there though.
Even calls won't vibrate my watch.

Dusty Rhodes said:
My standard stock watch faces no longer display the date.
Is anyone else having this problem?
Click to expand...
Click to collapse
Have you installed Moto Connect app?

xdatastic said:
Have you installed Moto Connect app?
Click to expand...
Click to collapse
Of course. I had the date showing on my watch faces before the update but it disappeared on the watch itself. I restarted and customized the faces and selected to show the date but it still doesn't show.

Dusty Rhodes said:
Of course. I had the date showing on my watch faces before the update but it disappeared on the watch itself. I restarted and customized the faces and selected to show the date but it still doesn't show.
Click to expand...
Click to collapse
I'm not having any issues with dates not showing up. They show up just fine and correct.

the latest update fixed the "show me my steps / heartrate" command. Previously it was displaying a google search result instead of opening the steps/heart rate app.

The new update broke a ton of functionality for me. I can no longer turn off the watch face while charging through turning ambient mode on and off. Voice commands also stopped working.
Anyone else have these issues?

Squintz said:
The new update broke a ton of functionality for me. I can no longer turn off the watch face while charging through turning ambient mode on and off. Voice commands also stopped working.
Anyone else have these issues?
Click to expand...
Click to collapse
Both of those features are still working fine for me. You might need to reset the watch and resync your faces/apps.

I am now getting Hangouts notifications for Chat messages as well as SMS messages.
Previously I was only getting them for SMS messages.

The latest version is here
http://www.apkmirror.com/apk/google-inc/android-wear/android-wear-1-0-5-1630507-apk/
Sent from my SM-N910C using Tapatalk 2

Steve-x said:
Both of those features are still working fine for me. You might need to reset the watch and resync your faces/apps.
Click to expand...
Click to collapse
How do you turn the watchface off while charging? Anyone else that's updated cannot, short of rooting and editing the build.prop
Sent from my Glamor Red M8

Fixed call answer
The new update also fixed an issue which some people had, about not being able to answer phone calls (only the red circle emerged to reject calls). Now both answer and reject are working again

Watch won't stay connected via Bluetooth

I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?

Anyone?

You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk

frellingfrakker said:
You need to reset the watch and re-pair it to the phone.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Did that 3-4 times. Today though it seems more stable.

Looks like Android Wear keeps crashing. That's the cause of all this, even after several resets.

Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk

giancarlo_f said:
Maybe CM 12.1 causes the problems?
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
Others on 12.1 have not had these issues.

Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.

karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I haven't gotten Wear 5.1.1 yet unfortunately. Hopefully soon. 5.0.2 is BUGGY! Especially with battery drain during app sync.

i'm having the same issue here running android wear 5 . and cm12.
6 reset so far today . it keep disconnecting and then after on the phone it says connecting... which does not goes away until you reset the watch .
It seems to be a software issue . Android wear is still buggy

karcher01 said:
Same for me here. Didn't have any problem with LG G Watch. Receive my brand new Moto 360 thurdsay and problem appears from the first sync. I was on Android Wear 4.4. WIth luck I manage to update to Android Wear 5.0.2 but still the same problem.
I noticed that when charging the watch, the connection works few minutes after. But when unpolugging the watch, it discionnects few seconds later.
Very disappointed !! Maybe an update bug (Android Wear has been updated 18th of may.
Click to expand...
Click to collapse
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360

karcher01 said:
I give up. I tested this morning with a new phone (ASus Padfone Inifinity). Same problem. I send my watch back for a refund and wait for anoter one. Back to my G Watch.
Edit : My G watch is just receving the 5.1.1 update. Good news of the day after this 4 days in Hell with Moto 360
Click to expand...
Click to collapse
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.

Moto 360 5.0.2
agentfazexx said:
The Moto360 should get 5.1.1 soon... Returning it was a bit excessive IMHO.
Click to expand...
Click to collapse
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.

dvrose said:
I am receiving the same disconnect issues with my Moto 360 running 5.0.2. It happens every ~5 minutes.
Click to expand...
Click to collapse
It should eventually stop. It did it for me after posting this for hours after resetting.

agentfazexx said:
I factory reset my Moto360 after clean wiping my phone (CM12.1 Nexus 6)... Now it won't stay connected via Bluetooth to my watch. Any idea how to fix this?
Click to expand...
Click to collapse
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way that CM12 and CM12.1 handles low energy bluetooth devices. Try another rom.

TheSt33v said:
It's a CM issue. When I had my S4, I had the same problem that you're describing on both CM12 and CM12.1, both official and unofficial builds. Installing a google play edition or stock-based rom solved the problem. I just got a Droid Turbo, and it also has no problems with the watch. After doing some reading, it seems like there is a problem with the way the CM12 and CM12.1 handle low energy bluetooth devices. Try another rom.
Click to expand...
Click to collapse
I got flamed in the thread for blaming the ROM.

agentfazexx said:
I got flamed in the thread for blaming the ROM.
Click to expand...
Click to collapse
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.

TheSt33v said:
Well whoever flamed you is stupid. It's a well known problem, at least with the S4. Go to any CM12 or 12.1 thread on the Verizon GS4 forum and search for Bluetooth. I guarantee at least 10 posts asking whether or not it is fixed in the latest build.
Click to expand...
Click to collapse
Whenever I blame anything on CM that worked fine on stock, they all flame me.
Those that had this issue.. Were you on CM or not?

Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk

giancarlo_f said:
Yep...... It's a CM-bug on my S4 too. I installed echo-rom (tw based based rom) and it worked perfect .
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
This happens to me on my stock Nexus 5, so I doubt it's a ROM issue. Most likely it's an issue with the firmware on the 360, or maybe the hardware. Hopefully 5.1.1 comes before my 30 days is up so I can decide whether or not to keep the 360, kind of sick of resetting the watch.

Having a issue with Bluetooth

Hi there.
I have a Z5P single sim version.
After I updated to Marshmallow 6.0,
Bluetooth isn't stable when I connected to my car. My car is 2012 vw Jetta tdi stock radio system(not navigation).
Often music turned down then back to same volume as before turned down like when i get notification, text, email, etc.
Before I updated to Marshmallow, I had same issue a few times, but it wasn't big deal.
Now it's just so annoying. And I wanna fix it.
Does anyone have same issue as me?
If there is way to fix it, please let me know!

That was always the case... I am having lost or intermittent music if there are too many apps are opened... Some time closing open apps do not help, I have to close the music app and restart again...
Sent from my SO-03H using Tapatalk

francisamarsingh said:
That was always the case... I am having lost or intermittent music if there are too many apps are opened... Some time closing open apps do not help, I have to close the music app and restart again...
Sent from my SO-03H using Tapatalk
Click to expand...
Click to collapse
Sorry for late response. I did same thing, close all app, or I just restart the phone. I use Spotify and all music is download in sd card. I also use Google music, and same thing happened. So I did forgot Bluetooth connection and recent connect again, but it's still happen. I don't really want to factory reset and use computer to fix program. It's too much to do. I just don't know what else I can do :/

Right now my Z5 is under repair and I have to do a factory reset so I will let you know if factory reset works...
Sent from my GT-I9505 using Tapatalk

Do you have any of the sony sound enhancements on or Viper?

francisamarsingh said:
Right now my Z5 is under repair and I have to do a factory reset so I will let you know if factory reset works...
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that but Thank you any information will help!
dude9946 said:
Do you have any of the sony sound enhancements on or Viper?
Click to expand...
Click to collapse

dude9946 said:
Do you have any of the sony sound enhancements on or Viper?
Click to expand...
Click to collapse
I have ClearAudio+ is on in the settings. That's all. I noticed that I have same issue even on my Bluetooth headphone now. What is Viper?

I had some really bad issues with my SBH70 headset dropping out after the MM update.
I cleared all bluetooth settings from phone and headset, cleared data fro SmartConnect and SBH70 app, uninstalled all updates for both, then updated everything and reconnected to bluetooth. Seems to have helped so far.

Nugstar said:
I had some really bad issues with my SBH70 headset dropping out after the MM update.
I cleared all bluetooth settings from phone and headset, cleared data fro SmartConnect and SBH70 app, uninstalled all updates for both, then updated everything and reconnected to bluetooth. Seems to have helped so far.
Click to expand...
Click to collapse
I haven't tried it yet, so I will try it and see if how it goes. Thanks for the info!
Sent from my E6853 using XDA-Developers mobile app

Update:
So at first, I did reset Bluetooth WiFi and signal settings, also smart connect and app setting. It did better for a couple time, then back to terrible again.
A couple of days later, I couldn't take it anymore, so I factory reset and repair on computer. It seems much better. Maybe a few times I still have same issue.
Great news is battery life is improved a lot. Now I don't need to charge till I go sleep. Also less buggy and faster.
My conclusion about this issue is, it is not about Bluetooth. It is something about OS or some software issue. When the phone is buggy and slow, this happens even all other app is closed.
Now I will wait for update to see if it will fix this issue.
Sent from my E6853 using XDA-Developers mobile app