Related
Hello all,
I've had my Tilt since November of 2007 and have been happy with it overall. However, back around May of 2008 I noticed that my sounds and notifications would randomly turn themselves off/change the settings for themselves. This was getting really annoying because I would routinely miss SMS/MMS and voicemails until I turned on my phone and saw the message on the screen. I would try to put the settings back to what I wanted but after about a day or so they would be reset without my knowledge.
I waited around for awhile telling myself that the ATT WM6.1 ROM would come out soon and hopefully fix it. However, it was several months until that happened and I'm still having problems. So, I've decided to turn to the community to see if anyone had some insight on the issue.
In trying to figure out what was going on, I did some testing on my phone/applications that I have installed. I have the stock ATT WM6.1 ROM with no hacks or cooked ROMs ever on it. One of the programs that I really like to use on my phone is TomTom Navigator v7 and I think this may be the problem. The last time I flashed my phone, I held off installing it for a couple of weeks and the notifications seemed to be working fine. After I re-installed it, everything went crazy again.
I also tried to pay attention to the sound settings I use on my phone and noticed that when I put the phone on vibrate only and then put it back to normal it seems to be the point at which the notifications don't come back. I'm using HTC Home that came with the WM6.1 ROM to manage the sound settings. Also, when the phone is in vibrate only the notifications also seem to go away so again, I can't tell if I have received a message or there is a reminder etc.
So, overall I think it may be some application that could be interfering with the sound settings but I'm not totally sure. Besides the normal installed applications, this is what I have installed on my phone:
AIM Mobile
BeyondPod (RSS Reader)
Google Maps
Live Search
Opera 9.5 Beta
Simple Timers (countdown timer)
TomTom Navigator (version 7.450)
If anyone knows if any of these applications could be interfering with my sound settings I would appreciate some feedback/help. Or, if anyone has had similar problems I would like to hear about them so we could troubleshoot. Thanks in advance for any support the community could provide.
# Opera 9.5 Beta <- He did it
There's a bug in the older beta's install the latest beta an it'll be OK.
Ta
Dave
Dave is correct. Take a look at the opera mobile forums. there is instructions on how to completely remove the older beta and install the new beta.
woooosh ... bugs begone
Thanks for the input guys! I was pretty sure I was running the latest beta (released in the second half of July or so?) but I will try again. I will check out the Opera forums for more information on this issue.
Do you think if I just remove Opera the problems will stop? I don't really use it all that much - mainly if PIE is just completely terrible on a page (instead of mostly terrible )
Anyway, thanks for the help, you guys rock!
Is anyone else having issues using the app HeyTell? The only ROM i can get it to work properly on is the stock AT&T 2.1, it doesn't even work on the stock 2.2 update. Basically on stock 2.1 I can send and receive messages perfectly without missing a message or having to close the app. If I update to 2.2 or flash a custom ROM, I can send about 2 messages and then it stops sending or receiving, I have to close the app and then try to send the message again. Once I open the app again, whatever the person sent to me is lost and they have to send it again.
Just putting this out there, I have emailed the developer and they are stating that they have no issues. I don't know what else to try, I have cleared the app's cache, uninstalled and reinstalled, I am out of ideas.
I've never even heard of this app before... I'll install it now and tell you how it goes.
EDIT: Okay, I obviously have no friends on this at the moment... But I've been clicking around the app and it seems fine? I'm using Paragon RC6 right now. The GPS/Map component seems to be working fine anyway... I can't really send a voice clip or message through it (no-one to send it to).
EDIT2: Okay, I somehow sent a voiceclip/message to myself and I've recorded it, sent it, and then received it fine. I'll keep playing around with this a little bit further in the morning.
I really appreciate it, it will work at first, and then just stop sending and receving, the little sending icon just spins and spins...then you have to force close it and then start it again, then it works for a few messages and then stops again.
I'm having the same problem with the HeyTell app. It's pretty much hit or miss for me, sometimes it works good for a while, sometimes it sends blank messages. I have a ton of friends using this app on iPhones or other Android devices and they aren't having problems at all.
I have emailed the developer and he states that it works perfectly for him on his phone, whether or not that is true, I am not sure.
Not trying to thread jack but for some reason my hey tell doesn't get messages on time. I'll be next to a buddy and I'll get a message that he sent hours ago. Does anyone else have this issue? I just have the 2.2 froyo update, no custom roms.
I thought for sure HeyTell would work on Official 2.2 as well but I have the same issue your stating. Like I said though, the developer states he has no issues...I am not sure what is going to happen.
HeyTell Support
Are you sure you contacted HeyTell support? I don't have any record of sending a "works for me" answer on a report like this...drop me another email to refresh my memory at [email protected] if you can - thanks in advance!
So! We're aware of an issue on the Galaxy S series phones (Fascinate, Epic, Captivate, Vibrant) introduced by 2.2 firmware (Samsung only, 2.2 makes HeyTell better on other phones). Symptoms appear to be spotty network reporting, media player issues (inconsistent record behavior), and the OS killing HeyTell during screen dims.
We're currently working hard to find a workaround for affected users (and trying to get more info from Samsung), but in the meantime, if you could do us a favor and email us your firmware revision number and any logs you have related to the behavior, we'd greatly appreciate it!
Since I had the issue with Stock 2.2 and not with Stock 2.1 I am running Stock 2.1 until there is a fix. If your asking me for logs I cannot help you there unless I put 2.2 on my phone. i am currently running HeyTell version 181, I am willing to load 2.2 and work with you and get you information, just let me know. I love this app, but my phone is kinda laggy and slow running 2.1 and I want to be running 2.2.
I"m also using HeyTell on 2.2 and having quite a bit of troubles. I'd be happy to send you logs if you could explain to me how to do so. Thanks!
Just a little update, I finally got tired of stock 2.1 last night and decided to try out MIUI. I was pleased to find that after sending more than 10 messages back and forth, HeyTell has not failed yet.... I will be testing all day at work today, I am not sure if they updated the app or if something in MIUI allows it to work. I just thought I would update those few of you that have had the same problem as me.
Everything is still working fine with HeyTell, I am running MIUI Beta 6 and HeyTell is working perfectly. I did notice an update to from the market, I am hoping that could be a fix for other cutom Roms and Stock 2.2.
As MIUI has no samsung crap in it, it should work fine, since it seems to be a samsung issue. Runs fine on CM7 as well.
We put a workaround into builds 1.1.3 -- that fixed it for stock, but didn't catch all of the custom ROMs, so we spun 1.1.4 - give that a whirl and it should work. If anyone runs into this issue again, shoot us an email with your model number (Menu > Profile > Email Support sends this to us, so that may be the fastest method, but also don't forget to include a description of the issue you hit).
Oh sweet so HeyTell should be working fine now with stock 2.2? I will test it now, thanks alot!
Ever since I downloaded the update the app works great! Thanks!
Hey Tell Message Queue Issues
I've been having a problem for a while now where message don't come in automatically, as if they're caught up in the queue somehow. I have to exit HeyTell multiple times, manually click on the message, hit the stop and play buttons, or multiple combinations of all of these just to get a single message to play sometimes. I'm using a Samsung SGS3 with Synergy. Any way to fix this issue? Thanks much!
I've got an annoying problem with my phone where the Wifi turns off when my phone is idle or asleep. This means my WhatsApp for Web disconnects and also my Moto Connect plays up too.
I've got the same problem at home, work and parents house so can't be an issue with all 3 networks. The keep wifi on during sleep option is set to Always before anyone mentions this to me.
Phone is running Lollipop 5.0 in the UK and is NOT rooted.
I noticed it doesn't happen when the phone is charging though.
Any ideas?
Right I've now tried changing the Sleep setting to Never but get the same problem.
Also tried connecting to the router via WPS but no luck.
Router is a Superhub 2. I've ruled out that it's the Superhub as I have a Samsung Galaxy S4 Mini that is running fine without a single drop out.
Definitely something Moto X related.
I've also tried on both the 2.4GHz and 5GHz bands with same results!
Try looking within the WiFi settings on the phone. Mine has this
. Added photo
Sent from my HTC One using XDA Free mobile app
Mine is identical to yours other than the fact that I don't have the wifi optimization option.
Right I've just cleared the cache as instructed by Motorola support.
Still have the same problem even after clearing cache.
Ok I can confirm that the issue goes away when in safe mode.
This is starting to piss me off as I don't have any way of checking if it's an app affecting my wifi disconnections!!!
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Wutang200 said:
I've finally found and fixed the problem myself!!
I decided to turn my bluetooth on (even though it wasn't connected to any bluetooth devices). This seems to stop the phone from causing the wifi to go to sleep!
It seems like it's a bug in the Moto X Lollipop firmware. How do I report bugs to Motorola??
It's funny how most say it's apps that cause strange behaviour but for me it's been the actual Android firmware each time I've ever had an issue!
I hope it gets fixed soon.
Click to expand...
Click to collapse
It's a known bug of 5.0, and already fixed for 5.1. Source, at the "Bug fixes section".
Great that you found a workarround.
Cheers!
Manuel.
Hey glad to know it's a well known bug. The work around still doesn't work. It still keeps disconnecting all the time! Driving me mad!! If the 5.1 update doesn't fix it for me, I'll need to try and get a refund and go for something else. Shame as I really like the Moto X but I can't live with an issue as stupid as this!
I'm not sure Motorola are aware of this issue at all. See their comment below from one of their support staff I'm speaking to now:
Santhosh: We have not received any reports regarding Wi-FI issue after the Android Lollipop update but please give me a moment I will provide the solution for this issue.
His solution for the issue was to get me to do a factory reset lol. I already did this when I first got updated to Lollipop!!
Going to try doing another one now to see if it actually makes any difference. Then will install a few apps at a time or something.
I am connected to WiFi just about all of time, and I have never experienced this.
Right I've done a factory reset and started completely afresh with none of my data or apps restored. WiFi has been solid; I've not had a single drop out!
I'm going to install just a couple of apps at a time and keep an eye out if the issue comes back until I find the culprit.
Hi
My phone was perfect (until now) with the WIFI since november 2014 even after I upgraded it to 5.0
But today, it suddenly starts with this problem by itself. so I restored it to factory defaults with no luck, I installed a new firmware, and still has the bug.
So, why it shows up until now by itself without any mod, app or update?
Sorry for my English.
Today I upgraded it to 5.1 and the issue persists
I had to back to stock 4.4.4. and now my wifi has been fixed so far, working good without interruption until now.
I hope this has fix the problem from sourse, and I'll wait a few days to upgrade it again.
EDIT: Has been a month since my downgrade to 4.4.4. and my WIFI still rocks.
Just want to say that I'm having the same issue since the update to 5.1. Wifi is set to be always on during sleep, but I regularly wake up my phone only to find it connected to 4G, and switching to wifi a few seconds after waking up.
I'm on a locked bootloader (unrooted of course). I did a full reset after the update...
I'm sorry to say that I've seen more little glitches since 5.1 than anything I noticed on 5.0.
EDIT: another issue I'm having is the stock mail client not syncing saying that there is no network connection. My exchange account (push) works fine however...
Just to say the issue has started for me too since the update to 5.1.
I've done 2 factory resets but no luck trying to fix this very annoying problem.
Motorola have asked me to send my phone in for repair so I'll try that and see what happens.
Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.
Hello All,
So since switching to the EU rom, I noticed that I am having issues with the RING app.
Not sure how many of you guys have RING cameras and use the RING app, but hoping that someone does.
Just curious to know, if you are using it, does your doorbell cam (or any other cams) work on the phone?
It works on my S10+ without an issue, while a few minutes later it does NOT work on the Mi 11 Ultra.
The timer is ticking and I can END the live call/view, but the camera picture is not working.
When I click on Live > Tap to Go Live > I get the following error where the video feed is supposed to be: Failed to connect. We're having trouble connecting to your Front Doorbell
Though if I go to the other phone I have, it works just fine.
So clearly its a phone issue and not the application or camera issue.
I am currently on Miui 12.5.17 EU rom, rooted, with LSposed installed. I've tried hiding magisk from Ring, but that did not solve the issue.
Any ideas?
I'm experiencing the same issue on the same ROM, no root, same version your on.
elite-fusion said:
Hello All,
So since switching to the EU rom, I noticed that I am having issues with the RING app.
Not sure how many of you guys have RING cameras and use the RING app, but hoping that someone does.
Just curious to know, if you are using it, does your doorbell cam (or any other cams) work on the phone?
It works on my S10+ without an issue, while a few minutes later it does NOT work on the Mi 11 Ultra.
The timer is ticking and I can END the live call/view, but the camera picture is not working.
When I click on Live > Tap to Go Live > I get the following error where the video feed is supposed to be: Failed to connect. We're having trouble connecting to your Front Doorbell
Though if I go to the other phone I have, it works just fine.
So clearly its a phone issue and not the application or camera issue.
I am currently on Miui 12.5.17 EU rom, rooted, with LSposed installed. I've tried hiding magisk from Ring, but that did not solve the issue.
Any ideas?
Click to expand...
Click to collapse
Do you have your work email, or any work related setup on your phone? Do you have a VPN app on your phone? These can cause this issue.
Hey, so I dont know what I did but the ring app started to work without issues later that day. or maybe the following day. This week has been a big blur at this point.
To further answer your question, yes, I do have a work profile set up through MS and all the MS apps, including InTune which I was able to install fine regardless of having the phone rooted, by using MagiskHide
I also have 2 sim cards in my phone, one personal TMO and one work from ATT
I dont know what combination of steps or actions I took to get it to work, but i was surprised myself that it started to work....
One thing I do remember doing is downloading an OLDER version of the app, which also did NOT work, but I figured I would just leave it installed for now since i didnt have time to go through any app updates. Then when I received a notification that someone was at the door, so I decided to just see if the video will work LIVE as someone was there, as opposed to a recorded motion (which did work on the phone without issue), and viola, it worked live... then eventually I did get around to updating to the latest version just to check and see if it will still work, and it did....
With regards to what the version of the Ring app was that I installed, I do not remember and I just checked the APKs I have on my phone and i do not see one. I think i might have used Aptoide app to download and install the older version. But I want to say it was from March of this year, so quite old, but I may be mistaken.
Nevermind, just found what the version was... Ring - Always Home v3.35.1
Ring - Always Home 3.35.1 (arm64-v8a + arm-v7a) (nodpi) (Android 5.0+) APK Download by Ring.com - APKMirror
Ring - Always Home 3.35.1 (arm64-v8a + arm-v7a) (nodpi) (Android 5.0+) APK Download by Ring.com - APKMirror Free and safe Android APK downloads
www.apkmirror.com
It's Intune and the work profile that installs phone security. The network masking that occurs causes the problems. Try removing it and testing it again.
I know that's the only changes I made on my phone before it stopped working.
I am 99.9 % sure that I tried the RING app BEFORE installing the work profile and thats when the issue was occurring...
not 100% thought, but 99.9%
But regardless..... as mentioned before.... It is currently working fine for me on the latest version of the Ring app... Not sure what I did to get it there, as I was not doing anything specific to fix the Ring app, but clearly something was done and everything now works as expected.
elite-fusion said:
I am 99.9 % sure that I tried the RING app BEFORE installing the work profile and thats when the issue was occurring...
not 100% thought, but 99.9%
But regardless..... as mentioned before.... It is currently working fine for me on the latest version of the Ring app... Not sure what I did to get it there, as I was not doing anything specific to fix the Ring app, but clearly something was done and everything now works as expected.
Click to expand...
Click to collapse
Congratulations, I meanwhile still have the same issue. Let me know if you ever find out how you fixed it.
Thank you.
See above...try to download the older version and run it for a day, hopefully that will get it to working? thats what i did, whether that was exactly what fixed the issue, i dont know, but worth a shot.
elite-fusion said:
See above...try to download the older version and run it for a day, hopefully that will get it to working? thats what i did, whether that was exactly what fixed the issue, i dont know, but worth a shot.
Click to expand...
Click to collapse
Old version of the app works. Maybe I'll wait until a new update is pushed. Last updated in September.
Actually, I lied before.... it DID NOT work on latest version. I just checked and it was NOT working....
I uninstalled and installed the older version and its back to working.
So i'll be using the older version.... As they say, if it ain't broke, dont fix it. so the old version will perfectly suffice
Any luck? Still struggling with this.
I've noticed that 12.5.17 has a lot of bugs. Waiting for another update desperately.