Related
So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretending that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.
whyzack_br said:
So here is the thing my screen is turning on randomly, but i've noticed 2 things
1 - When the phone is charging the screen does not turn on
2 - when i'm downloading anything the screen does not turn on too.
So my question is, is there a way to fool my system pretenfing that i'm downloading something that never ends or something like that? the battery comsumption is making me crazy.
Click to expand...
Click to collapse
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.
shut_down said:
You probably have some app that is making a mess. Do you use some lockscreen or notification app? Or something similar to those.
Click to expand...
Click to collapse
I don't think so, I Just applied the Cyanogen with Gapps, nothing more, and wiped everything but the problem always come back. /=
This might be a hardware issue. I faced a similar problem a few months back. I fixed it by cleaning my phone's micro USB port and the earphone jack.
In my case, it was caused because of build up of dirt.. my phone often "assumed" that I plugged in my USB cable and/or my earphone, that's why its display would turn on randomly.
[Q] Priority notification mode turning off on its own, even on "Indefinitely"?
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Yaqoub_H said:
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Click to expand...
Click to collapse
I never figured it out. Switched back to using Light Flow for notifications...
jeffreii said:
I never figured it out. Switched back to using Light Flow for notifications...
Click to expand...
Click to collapse
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Having same issue, no additional notification apps installed. Stock android on nexus 6 no root or anything yet. Thought I was loosing my mind thinking I never set it. Happens almost every night. Seems like a bug.
I'm having the opposite. On boot, priority mode is enabled even though it was off on shutdown. I turn it off then throughout the day I notice it come on again. I haven't been able to track anything down yet. I don't use lightflow.
Are there any logs that I can see that might tell me what is turning it on? There are no Downtime schedules.
Pure 3.95 / Franco r7
Yaqoub_H said:
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
Click to expand...
Click to collapse
So I finally got tired of Light Blow being buggy on the Nexus 6 and uninstalled it a few days ago...two nights in a row I set priority to "indefinitely" and when I woke up I found it had been turned off...so I don't think it's Light Flow causing the problem.
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Larzzzz82 said:
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
where exactly are you stuck at?
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Larzzzz82 said:
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Click to expand...
Click to collapse
so for the Wi-Fi part:
- there is the state 'Wi-Fi connected' to activate when you are connected
- you can use 'test net' to store ssid to a variable, then check it for a match with certain ssid, with which you want the profile to react to - only do when connected to certain Wi-Fi.
I don't have wireless charge so I cannot say anything here, but if I remember correctly, recent update of Tasker has included detection of this, so too should bff able to sound something useful in those states or events.
Then finally, in the clock app, you can either try to use intent or simulate taps to switch it to night clock.
After that, hopefully you will be happy with the result
Thank you sir. I will give those a shot
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Larzzzz82 said:
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Click to expand...
Click to collapse
what is your solution so far?
for connecting to Wi-Fi, sometimes it does not connect without screen on though, and I still have not figured that out.
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Larzzzz82 said:
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Click to expand...
Click to collapse
did you check to use root in the run shell commands?
Sadly I don't have a solution for the unlocking part.
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Click to expand...
Click to collapse
ah the pattern lock! now I see the pattern
do you have Xposed? maybe try to allow clock app over lock screen?
No exposed. Is it out for 7.1.1?
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
No exposed. Is it out for 7.1.1?
Click to expand...
Click to collapse
oh naah....
Seems to stop after the battery is charged... Gotta figure out how to latch the power till the end of the task.
So I just got a GS8. Fantastic phone. The only issue I am noticing is that when the phone enters "Do not Disturb" mode, it does not exit as scheduled. Typically it is set to turn on at 10 PM each night and turn off at 6 AM the next day. (save for the alarm that goes off at 5 AM). The alarm goes off fine. The phone, however, stays in "Do not Disturb" mode well past 6 AM and until I turn it off. Anyone else notice similar behavior? Could this result from the phone being connected to the A/C charger? I ask because when I set "Do not Disturb" to turn on and off at work it does so just fine. At work the phone is not connected to a charger.
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
rcobourn said:
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
Click to expand...
Click to collapse
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
anl2304 said:
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
Click to expand...
Click to collapse
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
You know, as long as I have had an android phone and I didn't think to do that. I should have. One issue I need to deal with is whether turning off the built-in Do Not Disturb disables that suspected hidden profile. If so, then I am good to go, if not, then I need to do the factory reset before using an app from the playstore (probably gives me more options than what Samsung allows).
Thanks.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
Resetting the device did the trick. rather than restoring apps from the Huawei Mate 9, I started fresh and downloaded apps from the app store. A pain, but it worked. Thanks again.