Database Develop

[Q] random reboot/mms bug?

Hi there,
just wondering if anyone else are having issues of their phone randomly rebooting? does anyone know of a fix?
also, sending photos as an attachment does not work. in order to send a photo to anyone on your contact list.
found a work around by going through gallery and sending it directly from there.
if anyone know of a fix for either issues. the help would be greatly appreciated.
Thanks,
kevin

I've had several random reboots. Oddly enough, they usually occurred overnight when I wasn't using the phone. I would hear the vibration on my windowsill and saw it was rebooting. I did a factory reset yesterday and while in the midst of setting everything up on my phone, it rebooted again. I thought that maybe there was too much going on and it overloaded. But last night when I was out and not using my phone, it rebooted again. I'm gonna have to go to Verizon to swap the phone.

It keeps happening on mine, but almost always in the car while attached with BT. I'm wondering if BT has something to do with it, in my case.

Same thing
I am also experiencing the issue specifically at night. I have yet to actually have it interrupt me in anything but its still a concern. Just curious about whether for those of you who are experiencing it are using the Assist app or Android Assistant?

I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.

It happened again to me this morning as soon as I got in the car and it connected to Bluetooth. Once it reboots, it's solid.

MVPete1 said:
I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.
Click to expand...
Click to collapse
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.

I can't get Assist to work at all. I typically listen to podcasts in the car and when texts come in I get a notification sound but I've never had one read to me. I disabled Assist to see if this was the cause of my Bluetooth reboots, and it's not.
With Assist disabled entirely, each time my phone pairs with Bluetooth it connects but the moment I start to play something it reboots. It's very consistent.

Phibaroptik said:
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.
Click to expand...
Click to collapse
Just wanted to let everyone know that I haven't had any reboots with the new phone. I exchanged my old one for this one on Monday and so far everything's been good.

I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.

ricwhic414 said:
I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.
Click to expand...
Click to collapse
Same here and wondering if that's "Normal" too...

My Moto X turns off at night during charging.

[Q] Unknown App Flashing When Toggling Wifi

Last night I was at home and noticed my wifi wasn't on, so I used the quick settings in the shade to toggle it. After a few seconds, wifi connected, and some unknown app took focus and closed repeatedly. After a few moments, it stopped and all was well.
I thought it was strange, so I turned wifi back off and the same thing happened. I rebooted, tried again, and got the same result. I was trying to think of a way to see what was happening, so I tried using the Screen Record function in Gravity Box, which didn't help much, because it happens so fast, and no info is displayed, just a black window that goes away quickly.
I then turned on the CPU usage in Developer Options to see if anything consistently came to the top when toggling. I saw a few apps each time Plume (Twitter), and Maildroid (email) were two of them. Both of these apps behave differently on wifi and 3G/4G (push vs. pull), so thought -maybe- it could be something with that. I uninstalled both of those, rebooted and tried again, getting the same result.
I recorded the screen when this was happening with the CPU usage displayed, and was wondering if anyone has any ideas? I don't really want to uninstall and reinstall EVERY app on my phone, so I was hoping someone may have seen this before or see something I'm missing when watching it happen.
Video: https://copy.com/8L6VTsqcdbUjVTz
Thanks for any input anyone can offer!

Do you check virus from your phone ?

I am also having this, seems to be due to 4.4.2 OTA, which I continue to delay as I am rooted.
Mine doens't only happen with wifi change, but also just randomly when using hangouts, keyboard stays out but hangouts min -> maxes quickly. I have tried freezing the update apps but it apparently didn't do anything as I was still asked to update earlier.

Only hangouts? I have that app disabled.in the app settings.

I can't say for sure that being on 4.4.2 fixed it, but I am on 4.4.2 now and it is not happening anymore.
I unlocked my bootloader and did the 4.4.2 SBF, unlocked and rooted. I installed probably 99% of the same apps (only ditched 1-2 that I never used anymore) and I am not having the flashing issue anymore.
Hard to tell for certain if the pending OTA was the cause, but it may have been.

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.

[Q] Problems with whatsapp on z3c

Hi guys,
Has anyone had any problems with whatsapp on our phone? The app seems to get killed somehow when the phone goes to sleep, so I don't receive any messages until I open it up. I've not got any powersaver modes running and background data is allowed etc etc, it's getting very annoying and i'm sure the phone is killing a background process but can't work out how to fix it.
Anyone have any ideas?
Cheers

I had a similar issue with hangouts but I cleared cache and data and it worked again. maybe give this a shot for whatsapp
Sent from my D5803

No problem at all.
I use stamina mode all the time, excluding Gmail, Whatsapp, Timely and Cerberus, and I receive emails and messages.
My firmware version is 23.0.A.2.98

I have stamina mode activated all the time but whatsapp works great

Thanks for your replies, i don't what the problem is. The same thing happens if i am in stamina mode (with the app whitelisted) or not in stamina mode.
I have tried re-installing, clearing cache and data etc but the problem perists. I guess i will have to ask the app developers, presumably they will blame the phone

danhughes1961 said:
Thanks for your replies, i don't what the problem is. The same thing happens if i am in stamina mode (with the app whitelisted) or not in stamina mode.
I have tried re-installing, clearing cache and data etc but the problem perists. I guess i will have to ask the app developers, presumably they will blame the phone
Click to expand...
Click to collapse
When you notice it start happening, check the "running apps" in settings. Do most of them show "restarting" etc? I think I have the same issue. It looks like a memory leak on my side.

I've seen similar to this but I think it might also be related to when other people have a connection. My wife has issues with her work wifi and sometimes I only get her messages once she's back on our home network. I see the time stamp in whatsapp as the time she originally wrote the message...

Thanks - will check that next time i see it happening, it doesn't look like it has restarted recently but possibly was "pausing". I've restarted my phone now so all processes are on the same clock so i can spot any breaks easier next time
Moist said:
When you notice it start happening, check the "running apps" in settings. Do most of them show "restarting" etc? I think I have the same issue. It looks like a memory leak on my side.
Click to expand...
Click to collapse

piratemoon said:
I've seen similar to this but I think it might also be related to when other people have a connection. My wife has issues with her work wifi and sometimes I only get her messages once she's back on our home network. I see the time stamp in whatsapp as the time she originally wrote the message...
Click to expand...
Click to collapse
Cheers but seems not likely as messages from multiple contacts appear at the same time when i open the app, so the problem must be on my end

Quick update, i've had the problem happen again and checked the running apps, there was no pause happening. Even this morning on the train i was looking at the internet, so my phone was connected to data and obviously not asleep and i got no messages. Later on, i opened the app and a message appeared, sent at the time i was looking at the internet. I'm flummoxed. Will raise a support call and update if i have any luck

Phone randomly auto-mutes itself, can't increase volume [video inside]

Hey guys,
I have a weird issue with my Moto X 2014 (stock Lollipop, no root or anything), and I can't find anything helpful around the web.
I have a video of the issue - I can't post the link as I don't have enough messages, but go to vid.me and add this code to the URL: /tMXf
Basically every few days, I find the phone is on vibrate. The volume rocker is suddenly all the way down, even though it should be maxed out, and I can't physically turn it up as you can see in the video. Even in audio settings, the ringer options is greyed out.
Android's quiet hours setting is NOT active. I have Moto Assist set to kick in at night time, but this happens randomly during the day, plus I tried removing it but nothing changes. It's not something to do with calendar events silencing the phone either, as Moto Assist only has scenarios for driving and the aforementioned night time.
Anyone knows what could be happening here? Thanks, much appreciated.

That IS strange... Have you tried rebooting your phone?

cole_15 said:
That IS strange... Have you tried rebooting your phone?
Click to expand...
Click to collapse
Thanks for the reply, man... yes, of course I tried that, but it's definitely not a temporary glitch. It happens again and again, every few days. A reboot does fix the issue when it occurs (in fact, it's the only way to get sound back), but only until the next time.