I've been running into a issue lately with my phone and my research has turned up nothing so I thought I'd post here. For some reason, every night my phone automatically turns on silence mode around the same time. Originally I thought it happened because of me accidentally hitting the volume buttons, but I have made it a point to make sure the the phone isn't in silence mode before putting it down and it still happens during the evening. It started happening after I upgraded Lollipop and after doing some research thought it happened due to the new interruption settings, but it still happens even after "Downtime Days" is set to "None".
I am running the stock ROM rooted. I have looked into the apps I use and none of them should be able to set the phone to silent automatically. I'm trying to fix this without doing a factory reset if only because I'm worried it won't fix the problem. If anyone can help me out I'd appreciate it.
Related
I have a perplexing problem with two phones that I have. The issues is, when the phones go to sleep (either by timing out while on battery or when I hit the power button on the phone to turn off the screen), the CDMA radio will shut off after a while and won't turn back on until I perform one of the following:
1. Reboot
2. Make a phone call
3. Send a text message
4. Switch in and out of airplane mode.
I know when it's off because I will suddenly get a flood of text messages when I perform any of the above tasks.
I thought originally this was something wrong with my phone (maybe too much flashing), so I got another Galaxy Nexus (Sprint). Unfortunately, it does the same thing. If I keep it on a charger and do not turn the screen off, everything works fine.
The phones are a Galaxy Nexus that works with Sprint. Since I don't know when it happens, I captured a logcat of the phone overnight after I turned the screen off. The next morning, I had to dial out to "wake" the phone.
I have factory reset the phone, flashed another rom (it seems to happen to anything that was based on CM), All these have happened multiple times trying to fix the issue. I have wiped dalvik and cache with no avail. Is there something I'm not trying?
I tried looking around to see if anyone else had this problem, but came up empty.
Perhaps someone had had this problem as well and can direct me to a fix.
Logcat: http://www.darktremor.info/logs/logcat.txt
Thanks.
Hi everyone,
I'm having serious problems with my Wi-Fi on my Samsung Galaxy Note 3 Neo (SM-N7505). Whenever I click the button to activate the Wi-Fi, the icon goes from grey to a dull green (darker than the bright green which signals that a function is turned on), as it does when it's trying to turn itself on. Problem is, instead of turning on, it just stays in that state for a few minutes before reverting to grey. This has gone on for a while, and I've already tried several possible solutions which I found after online searches. I don't think it's a hardware issue (see point 1 for the reason), and I really hope it isn't, because my warranty has been voided due to rooting, so I can't have my phone replaced or repaired unless I pay for it (which I can't at the moment). So, I'm basically ignoring the possibility of hardware failure and trying every possible software solution, hoping one of them will work, otherwise I'm just stuck with no Wi-Fi. These are the fixes I've tried:
1) Take out the battery while the phone is on, wait a few seconds, then put it back in and boot the phone up. This used to work when the problem first presented itself a few months ago (which is why I don't think it's a hardware issue), and I've been since using this method to fix it whenever it happened again. But a few days ago, this method stopped working for whatever reason, so I was back to square one.
2) I tried renaming the data/misc/wifi/wpa_supplicant.conf file, which seems to have worked for some people, but not for me.
3) I tried updating the version from Kitkat to the recent Lollipop, hoping that would fix it, but nope.
4) I tried deleting practically every single app one by one, hoping that one of them was interfering with the Wi-Fi somehow, but nope.
5) As a last resort, I tried a factory reset, but not even that worked.
This is basically the long and short of what I've tried to fix this... I might've skipped a few of the simpler fixes I tried (for example, I just remember I tried disabling "Smart Network Switch", which seemed to do it for some people), but the big stuff is all there.
I'd really like to get my Wi-Fi back, so if anyone could help me fix this thing I'd be really grateful!
Thanks in advance to anyone who will bother to reply.
same problem dude
Same problem...wifi and bluetooth not working...pls help us
Same Problem for me, Initally it works fine even after updating Official Lollipop update (OTA), but after few months now wifi & bluetooth are not working for me. And finally faced battery drain issue for past few days. Battery goes down upto 20% per hour even in idle condition. Then i rooted & installed Note Rom & even after i face the same problem. Is there any way to fix?
My phone is a non-developer version that I bought from the verizon store about a year and a half ago. I installed the OTA update from verizon a couple of weeks ago for Marshmallow and ever since I updated my phone no longer vibrates for anything. The haptic feedback vibrations have stopped, notifications and the phone ringing don't vibrate either. I've gone through all of the sound settings on the device and no matter what settings I use the phone just doesn't vibrate. Oddly enough the other day when I powered off my device and removed the battery then put it back in and turned it on the vibrations came back for only a few seconds before stopping completely again. Seems to me like there's some sort of hardware problem but I don't understand how that could've been caused by the update. Vibrations worked perfectly fine for me before updating and even though I like Marshmallow i'm starting to wish I never upgraded in the first place. I almost constantly keep my phone in Vibrate mode when i'm out and about but this update has forced me to keep my ringer on at all times now. Please let me know if there's any suggestions out there on how to fix this annoying issue!
You can do a factory reset, save what ever is important to you before do the factory reset..
The thing is becoming increasingly unresponsive when something tries to wake it from deep sleep. A few weeks back someone tried to call me, and the screen turned on and flashed the dialer app, but the touchscreen was unresponsive. I'd click "Answer" and it wouldn't register. Clicking it repeatedly, clicking anywhere on the screen, trying to turn the screen off and on, nothing would work. The phone basically froze, only not exactly, because the sound was still playing. Like a minute later, I held the power button down and got the shutdown pop-up which seemed to rouse it out of whatever infinite loop it was stuck in.
This morning, it happened again when my alarm went off. I could not get the damn thing to stop. It happened again an hour later. When I tried to hold down the power button, the phone reset.
When it came back on, a bunch of my settings had been reset. It reverted to the default keyboard and started showing me tutorials like it thought this was my first time powering on the phone. Additionally, the System Updates menu shows I'm on the latest version, but all history of past updates has been wiped out.
I'm getting really concerned that this thing is gonna die on me any day now.
Aganar said:
The thing is becoming increasingly unresponsive when something tries to wake it from deep sleep. A few weeks back someone tried to call me, and the screen turned on and flashed the dialer app, but the touchscreen was unresponsive. I'd click "Answer" and it wouldn't register. Clicking it repeatedly, clicking anywhere on the screen, trying to turn the screen off and on, nothing would work. The phone basically froze, only not exactly, because the sound was still playing. Like a minute later, I held the power button down and got the shutdown pop-up which seemed to rouse it out of whatever infinite loop it was stuck in.
This morning, it happened again when my alarm went off. I could not get the damn thing to stop. It happened again an hour later. When I tried to hold down the power button, the phone reset.
When it came back on, a bunch of my settings had been reset. It reverted to the default keyboard and started showing me tutorials like it thought this was my first time powering on the phone. Additionally, the System Updates menu shows I'm on the latest version, but all history of past updates has been wiped out.
I'm getting really concerned that this thing is gonna die on me any day now.
Click to expand...
Click to collapse
How about factory resetting the phone, starting from scratch re the software installed? Yes, you'll need to reinstall your apps and reconfigure it, but it's like starting fresh. If it still malfunctions, then you can look deeper.
weinberk said:
How about factory resetting the phone, starting from scratch re the software installed? Yes, you'll need to reinstall your apps and reconfigure it, but it's like starting fresh. If it still malfunctions, then you can look deeper.
Click to expand...
Click to collapse
Thanks for the advice, but I ended up grabbing a Galaxy S8+ off a friend for very cheap. So, not really an issue anymore.
I had the weirdest thing happen to me this morning...
I have a fitbit that has my alarm set so it went off and woke me up a little...
I laid there waiting for my phone alarm to go off, but it didn't.
I looked at it and it was in stock Android Recovery and had 2 options...
(It said something like "Android may be corrupted and if you cannot access Android, you may need to factory reset)
Option 1 was to reboot
Option 2 was to Factory reset
I selected option 1 and it started to boot, got to the Google emblem and all of sudden it starting making this loud ringing sound (a sound I haven't heard) and would not stop... After hitting every button on the phone, it powered off like I turned the phone off and went right back to the same Android Recovery screen...
At that point I just factory reset and here we are...
Anyone ever experience this?
Anyone know what the heck happened? Lol
Thanks