Database Users

TWS Bug Information

EDIT X3 Here is a definite fix for the TWS bug
BIG THANKS to mkasick for his hard work!!!! This fix has been incorporated into the latest bonsai ROM and will be included in the next Syndicate Rom. Thanks Devs!
Link to TWS bug fix/patch
I know the TWS (time without signal) bug is a known issue with this phone. It was present in di18 and is still here is eb13. However, it seems that some people have the bug, and some people do not have the bug after updating to eb13. I have not seen a lot of talk over this issue, which to me, is a HUGE issue. If you are not aware you have it and do not take preliminary steps to correct it, your battery will be drained much faster than normal.
I have tried everything I can think of to solve this issue including re-flashing in Odin several times, factory resets, etc... I am aware of the airplane mode toggle and profile/PRL update work arounds, but I am wondering if there is a FIX for this yet. These work arounds do not stick for me after re-booting, and it is very frustrating.
I am curious to see who has the bug on eb13 and who does not. If you are not experiencing the TWS bug, please post your method of upgrading, current ROM, kernel, etc..
Thank you for your input!
Edit: Thanks rocket, I should have included this to begin with. To check if you have the TWS bug, first make sure you are in an area with good coverage then
1. Charge battery all the way up (not really necessary, but will create a standard for testing)
2. Unplug and then stay in the same location for several hours
3. Go to Menu> Settings> About Phone> Battery Use> Cell Standby
4 Tap on Cell Standby and look for the "Time without signal"
5. If this is a high value such as above 40% you have the bug. I typically see 50 - 51% if I do not airplane toggle. After the toggle, I have 0 - 2% in my house where I have full 3g/4g coverage
EDITX2: Possible fix for TWS bug, need others to try
If you are having the TWS bug, try opening task manager (long press home button) and go to task manager. Then click on RAM management and clear level 1+2 memory. This should reset your radio as well. Get back to the home screen by pressing home button, wait a few seconds and power off the device properly (press and hold power button, power off) DO NOT do a battery pull to turn it off. Once the phone has fully shut down (after you feel it vibrate) wait a few more seconds and power back on. This should correct the problem and I have not had the issue come back after re-boots (no need to airplane toggle anymore).
*Disclaimer* What works for me may not work for you. I have no idea if this is just a device specific fix, but if other people can try this then we can rule that out. Sometimes clearing the memory resets the radio, sometimes it doesn't. I have noticed if it does reset the radio, your TWS bug will be fixed. It should stay after re-boots.

djbacon06 said:
I know the TWS (time without signal) bug is a known issue with this phone. It was present in di18 and is still here is eb13. However, it seems that some people have the bug, and some people do not have the bug after updating to eb13. I have not seen a lot of talk over this issue, which to me, is a HUGE issue.
I have tried everything I can think of to solve this issue including re-flashing in Odin several times, factory resets, etc... I am aware of the airplane mode toggle and profile/PRL update work arounds, but I am wondering if there is a FIX for this yet. These work arounds do not stick for me after re-booting, and it is very frustrating.
I am curious to see who has the bug on eb13 and who does not. If you are not experiencing the TWS bug, please post your method of upgrading, current ROM, kernel, etc..
Thank you for your input!
Click to expand...
Click to collapse
bizzare. Ive never had this bug. On eclair or leak froyos or eb13.

Do not have the bug now, nor did I have it at any point
Current Setup: EB13, Bonsai ROM v3.0.0
Upgrade Method, Flashed back to stock DI18 from DK28 using Odin
Used SWupdate to install EB13
Installed CWM 3.0.0.6
Installed Bonsai ROM v3.0.0

I have the bug. I suspect people who say they don't have the bug don't reboot very often, out of sight out of mind type of thing. I could be wrong.
What I do know is after the PRL "fix" came out tons of people were saying "yay its fixed" then a few days/weeks later they reboot and find its still an issue.
I'm hopeful that because Sprint & Samsung pulled the update (Samsung just pulled it from their site today I think) they would be working on an incremental update which fixes a lot of these complaints. I don't have any inside information, but when other SGS phones have had their updates pulled it seems like new releases were dropping within 2-3 weeks to correct problems. Also, the Samsung rep who reads XDA has been sent a list of bugs compiled on this forum so hopefully they will be addressing them without adding more "fireworks" type bugs
Edit:
I wanted to contribute a bit more to this thread, so first off if you don't know how to tell if you have the TWS bug follow these steps:
Charge battery all the way up
Unplug and then stay in the same location for several hours
Go to Menu> Settings> About Phone> Battery Use> Cell Standby
Tap on Cell Standby and look for the "Time without signal"
If this is a high value such as >40% you either have very poor cell coverage, or you have the TWS bug. I work primarily in a basement so my TWS is about 10% normally, but goes up over 50% when the TWS bug is active.

The TWS bug seems to be endemic to multiple Samsung devices and as far as I can tell they have never admitted or officially recognized that the problem exists. It has effected my phone on DI18, DK28 and EB13. From what I have read it is caused by sloppy modem.bin coding.

I know FOR CERTAIN that I have this bug!!!!!
EVERY DAY I receive voicemail notifications from people when their ORIGINAL call NEVER CAME THROUGH....
I checked the stats one day and my phone had been unplugged for 16 hours.....during that time it logged that I was "without a signal" 50% of that time.
8 HOURS WITHOUT A SIGNAL......ARE YOU FREAKING SERIOUS!!!!
(Looking for another carrier)
[Sprint is the Devil]
BTW
I had this bug in DI18 and I am currently running leaked DK28 with the same problems

I try to remember the airplane toggle mode trick whenever I reboot after swapping batteries and if I remember right away my TWS is 0% but without fail if I forget it's always around 50%. After I remember and toggle airplane mode it slowly lowers the % value as time passes. Running midnight4.1 right now, originally odin'd to eb13.

The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.

muyoso said:
The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.
Click to expand...
Click to collapse
Does not fix it for me. Has the same effect as toggling Airplane mode though. Reboot and it's back...

muyoso said:
The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.
Click to expand...
Click to collapse
Thanks for the input, but as I stated, for me at least, updating the PRL does NOT stick after re-boots to fix the problem. If this does fix yours, wonderful, but for people like me this is not a solution, only a temporary work around.
The fact that there is such a wide variance among users is very concerning.

bjhill2112 said:
Does not fix it for me. Has the same effect as toggling Airplane mode though. Reboot and it's back...
Click to expand...
Click to collapse
+1 this guy knows what I'm talkin bout!

Add me to the list of "had it, have it, and PRL/Profile updates don't stick past reboot."
My favorite way to fix it is to use a free little app called network I got from the market. It's just a shortcut to a radio settings menu that I used to be able to get through a dialcode, but I like just clicking on the button.
What I see with the menu is that the phone appears to default to "WCDMA Preferred" which is a type of network that our phones cannot access. I switch it to "CDMA Preferred," and the TWS problem will then go away (until next reboot, of course). What would really be great is if changing this setting could get coded into the custom ROMs.

Not sure what's fixed it
OK so when I initially flashed to EB13 I had the bug (also had it in DI18, but not DK28). I got an airplane mode toggle widget and all that shiz to make it easier to deal with.
After a few changes to my phone it is now gone.
I noticed it went away after I put Twilight Zone kernel on my phone, performed a flash to ext4 version EB13 through Odin from here, then reflashed Twilight Zone kernel to be sure it was still intact. I also restored my data from a back up i performed why on rfs/CMW2.
Today I attempted to flash the full Frozen ROM and for the few minutes I had it on my phone I noticed that the bug was back. I reodined using the same method as before, restored data, and wallah its gone.
Furthermore, I saw on here moments ago that there was a firmware update for the camera. After I installed it I noticed it FCing on Sports Scene mode. To fix that I flashed Twilight Zone again and still do not seem to have the bug back.
Anyone else want to try and give it a shot to see if it fixes/changes things for you?
I cannot tell if it's related to the kernel, the switch to ext4, or some combination of those things. Allz I know is its been days and it's still gone.

I definitely have this bug, and what "bugs" me is that I have been scratching my head trying to figure out why a bunch of my calls go straight to voicemail... this is a huge problem imho which hopefully will have a real fix soon. I downloaded the Network app but can't get the CDMA only mode to stick... "process.com.adroid.phone" crashes every time I guess I have to remember to toggle airplane mode after every reboot. This sux

It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.

Gersonian said:
OK so when I initially flashed to EB13 I had the bug (also had it in DI18, but not DK28). I got an airplane mode toggle widget and all that shiz to make it easier to deal with.
After a few changes to my phone it is now gone.
I noticed it went away after I put Twilight Zone kernel on my phone, performed a flash to ext4 version EB13 through Odin from here, then reflashed Twilight Zone kernel to be sure it was still intact. I also restored my data from a back up i performed why on rfs/CMW2.
Today I attempted to flash the full Frozen ROM and for the few minutes I had it on my phone I noticed that the bug was back. I reodined using the same method as before, restored data, and wallah its gone.
Furthermore, I saw on here moments ago that there was a firmware update for the camera. After I installed it I noticed it FCing on Sports Scene mode. To fix that I flashed Twilight Zone again and still do not seem to have the bug back.
Anyone else want to try and give it a shot to see if it fixes/changes things for you?
I cannot tell if it's related to the kernel, the switch to ext4, or some combination of those things. Allz I know is its been days and it's still gone.
Click to expand...
Click to collapse
Does the bug stay away after a reboot or 2? I also noticed that I thought I had this problem solved until one day I noticed my phone died after 6-8 hours into my 12 hour shift, and the reason I belive it is such a battery drain is that the phone doesn't sleep when it thinks it doesn't have a signal in addition 2 constantly scaning for prefered network. For sum reason it is set 2 wcdma by default when that's a gsm network. If anyone knows where that value is saved plz give me a heads up...
Sprint is absolutly no help as their "specialest" told me a task manager would fix this problem -rotflmfao!! after 3 techs and numorious "mistransfers" where I was hung up on I gave up hope that sprint highers compatant ppl..
Sent from my SPH-D700 using XDA App

mkasick said:
It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.
Click to expand...
Click to collapse
I now think I might be a little slow.. because that went way over my head.. lol
and I read it a few times..
and I work as a I.T tech..
but im also drunk right now maybe thats the reason..

Isn't thidls bug just visual? I have it and it had no effect on my phone.
Sent from my SPH-D700 using Tapatalk

mkasick said:
It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.
Click to expand...
Click to collapse
musclehead84 said:
Isn't thidls bug just visual? I have it and it had no effect on my phone.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I agree. The "TWS bug" is just a reporting issue. It has no real effect on battery life. The percentage of battery used by the cell radio is the same regardless of what TWS reads.

BigBrotherMotown said:
I know FOR CERTAIN that I have this bug!!!!!
EVERY DAY I receive voicemail notifications from people when their ORIGINAL call NEVER CAME THROUGH....
I checked the stats one day and my phone had been unplugged for 16 hours.....during that time it logged that I was "without a signal" 50% of that time.
8 HOURS WITHOUT A SIGNAL......ARE YOU FREAKING SERIOUS!!!!
(Looking for another carrier)
[Sprint is the Devil]
BTW
I had this bug in DI18 and I am currently running leaked DK28 with the same problems
Click to expand...
Click to collapse
This is what made me think that I probably had this with DI18 and even some of the DK28 roms I ran even though I didn't know how to check for it back then, I would always get voicemails and no record of a missed call in my call log. Very frustrating. So the battery life issue that may or may not be associated with this bug is of little consequence to me compared to not even getting calls due to lack of signal.

Back button just became erratic!!! Help!

My capacitive back button is going crazy!!! I figured it was just the rom or a program running in the background. So I rebooted into recovery and it happened then too!!! Definitely a hardware issue. I didn't drop the phone and I wiped the screen clean. So I'm not sure what the problem is. Is there any way I can disable the back button completely and remap it to the Search button? I never use the Search button, so this would work for me. Please help!

I have had this happen to me, it would randomly act up. After two weeks or so, it just stopped happening.
I have seen reports on forums that some people have tightened the screws on the back of the phone and had luck with that fixing the problem.
Sorry I can't be more helpful.

Yeah happened to me too when I first rooted it, found out it wasn't the root that did it but an application that I put on there that was not compatible with the phone.

I had the same problem too -- I posted this a few days ago on another thread dealing with this problem. I'm not sure why it's happening but it many people think it's a software incompatibility issue. I did five hard resets and the problem went away. Most people who tried the hard resets only did it once, and the problem persists. It'll even persist in recovery. I think you need to do enough hard resets until the problem disappears. Mine now is glitch-free -- good luck.
http://forum.xda-developers.com/showthread.php?t=952535&highlight=back+button+issue&page=2
Nexus S
Rooted Stock 2.3.1
T-mobile unlocked

Try installing the stock 2.3.4 just for trial. The new update fixed all my issues with the back button
Sent from my Nexus S using XDA App

I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.

SphericalPuma said:
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
Click to expand...
Click to collapse
Your new nexus s are using latest version or not?

I have this issue sometimes too. Mine doesn't go crazy though, it just becomes unresponsive and dark. I have to wait a couple of seconds and then it comes back. Kinda of like the phone freezing while the damn button come back.
Running Nexus S4G 2.3.4

Battery, "learning usage patterns"

Updated my s4 recently witch added smart manager and redesigned battery option in settings. Now it only says "learning usage pattern" it does not show me how much hours it is left before i need to charge it.
Take a look at my screenshot i took earlier.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Regards

SteeL900 said:
Updated my s4 recently witch added smart manager and redesigned battery option in settings. Now it only says "learning usage pattern" it does not show me how much hours it is left before i need to charge it.
Regards
Click to expand...
Click to collapse
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.

@SteeL900: Don't follow the advice you've been given to wipe your phone. That won't resolve the problem and will just annoy you. The solution to the problem is to just be patient, as it takes some time for the app to properly report the estimated time remaining.

Uzair40 said:
Turn off your phone, and then turn it on pressing and holding Volume Up, Home, and Power button at the same time until you see a warning. Then press Volume Up to continue, and navigate using volume keys and select wipe cache/factory reset with the Home button, then reboot.
Please note that by doing this all your data will be lost.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
@SteeL900: Don't follow the advice you've been given to wipe your phone. That won't resolve the problem and will just annoy you. The solution to the problem is to just be patient, as it takes some time for the app to properly report the estimated time remaining.
Click to expand...
Click to collapse
Thank you for your answers. I did try to wipe and that did not solve the problem. I updated the phone like 1 week ago and it still says " learning usage patterns" i mean how long does it take?
Regards

This is the bug in OH2 firmware and cant be resolved,Flash the latest OJ2 DBT firmware which has latest Smart Manager provider and it shows estimated usage time left

Battery "learning usage pattern" Fix Galaxy s6
I have the same problem...when i bought Galaxy S6
but now i found a way of recovery...
Go to settings>>Backup & Reset>>Scroll down>>Factory reset
Please make sure that you make a Backup for the phone...
do that and your phone will refresh and solves the problem of "learning usage pattern"

I have the same problem with my i9500 and Smart Manager is stuck at learning mode. Thus no app is being optimized due to npt being learnt.
Using stock Rom. Rooted. Non original battery.

My phone is I9500XXUHOH6 btw.

I found out that problem happens with replacement battery and not with original Samsung battery.

Umar472 said:
I have the same problem...when i bought Galaxy S6
but now i found a way of recovery...
Go to settings>>Backup & Reset>>Scroll down>>Factory reset
Please make sure that you make a Backup for the phone...
do that and your phone will refresh and solves the problem of "learning usage pattern"
Click to expand...
Click to collapse
I tried this once when I encoutered the same problem. It was fixed by this method.

majcomtech said:
I tried this once when I encoutered the same problem. It was fixed by this method.
Click to expand...
Click to collapse
My problem started post i reset the phone, before resetting it it was showing remaining time and it was accurate!! then I had to reset it due to certain issues and now it is stuck at "Learning usage pattern"

RAMDOOT said:
My problem started post i reset the phone, before resetting it it was showing remaining time and it was accurate!! then I had to reset it due to certain issues and now it is stuck at "Learning usage pattern"
Click to expand...
Click to collapse
let your phone totally drain and recharge it full and finally wait and have patience, just a couple of hours or a day maybe, hopefully it will work again.
by the way the method of resetting is not the cure of this problem. i am sorry if i confirmed that the method of resetting is working. since i tried it again after flashing and resetting many times it never help. just drain your battery and recharge it 100% and wait.

majcomtech said:
let your phone totally drain and recharge it full and finally wait and have patience, just a couple of hours or a day maybe, hopefully it will work again.
by the way the method of resetting is not the cure of this problem. i am sorry if i confirmed that the method of resetting is working. since i tried it again after flashing and resetting many times it never help. just drain your battery and recharge it 100% and wait.
Click to expand...
Click to collapse
Yeah it actually happened on its own, the battery got fully drained and then i charged it after half n hour, the battery app was now showing estimates (Learning usage Pattern was gone!!). Then i realized following points :
1. It required the whole cycle to be completed i.e. full charged to full drain to understand the usage pattern
2. When I did the factory reset i had many apps on my phone which were all set with their cache and cookies which got wiped off and post reset i installed them all again and i guess they were setting up in background and making their libraries ready so it consumed more power on the first day.
However, today is the 4th day post reset and the battery competence is back again :good: so what i have learned is Patience is the key :angel:

Note 4 (T-Mobile) Lag, Freeze, Crashes, Restarts.

This is my first post on this forum. I searched around here for a solution, didn't really find one matching my problem. I am not a phone wizard or anything like that either. So I'll try my best explaining my problem.
First things first:
Phone: Note 4
Model #: SM-N910T
Android Version: 5.1.1
Rom: Stock Rom
Rooted: Rooted Once and used a custom Stock T Mobile Rom Once.
Here's the ROM I used at the time: http://forum.xda-developers.com/not...10tuvu1cog2-debloated-deodexed-stock-t3175406
Recently I So recently my phone out of the blue started lagging, freezing, and restarting itself. I didn't download any applications or anything like that for it to freeze up. I was currently then on the custom ROM I have mentioned above and it was the updated version. I have tried everything to my knowledge to try and fix the problem. I have tried going back to stock T mobile ROM (currently on stock rom now) through odin and stuff. After all that, it was still lagging, freezing, and restarting etc... Ran it through safe mode and the only problem in safe mode is that the lag is gone, but the restart is still there. Running in safe mode, if I would turn the screen off and back on to unlock my phone, there would be like 40% chance that it would restart after unlocking the phone and the phone would just restart normally. Rarely, whenever my phone would attempt to restart.. I would get a "Could not boot normally" message along with couples codes below and the image of android guy. Then I would have to take my battery out and attempt to restart the phone once again.. I've wiped the cache and everything in recovery mode, nothing helps at all. Also, the phone is in perfect condition. Hasn't been dropped, cracked, no water damage, or anything like that.
This place is my only hope to fix my phone before I will go out to buy another phone from the carrier.
Thank you all for taking your time to help me

u r not alone
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964

doctor geek said:
hi, huntitude. even i am experiencing similar issues. kindly follow this thread and update if u find any solution
http://forum.xda-developers.com/note-4/help/frustrating-problem-phone-lagging-t3336964
Click to expand...
Click to collapse
Well I already got rid of my note 4 unfortunately before anyone could help me here so I had to upgrade my phone to note 5 and return note 4. While I still had my note 4, I realized something weird. While the phone was lagging and crashing etc.. When I had it plugged in for charge it would work perfectly fine. No lag, it wouldn't freeze up or restart (had it running perfect for 7 hours). It was like my phone was brand new again. As soon as I unplugged it from the charger, few minutes in and it was back to restarting and all that. I never knew why it did that.
Anyone know why this mightve happened?

Might be the battery though

I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.

Huntitude said:
I thought that too. I tried my brothers note 4 battery for awhile and it worked for a little bit and then it started doing the same thing even on his battery. Shrugs.
Click to expand...
Click to collapse
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.

d4rkkn16ht said:
In the COH update iteration there is an annoying bug that affect fingerprint.
The bug causing the phone to restart, lagging & closing all apps randomly when the fingerprint is set.
May be this one is also the same.
Try to disable all fingerprint related settings.
Click to expand...
Click to collapse
I never used finger print scanning on my Note 4. Always disabled.

Phone unresponsive / Android system / huge battery drain from yesterday

Hi everyone,
since yesterday I am having a major issue with my Honor 8 (FRD-L09, unbranded, stock OTA /Android 7.0, security patch level 5.8.2017/). After some time (it can be several minutes or hour) the phone becomes unresponsive. I am able to unlock the display but that is all. It is not possible to swipe left/right/notification bar. Software buttons are working, what helps (for at least some time) is when I hit left square button and clear memory. Even it clears only 20 MB, phone is running ok for some time again. Battery drain is enourmous - yesterday when these problems started for me I had 93% and in 4 hours without using phone at all it dropped to 40% ! When I check battery stats, it is drained by "Android system".
Yesterday I missed some phone calls because of that (I know people called me, but no missed call and no missed call sms from operator). The first sympthoms I noticed yesterday were (apart from slow response) that when I swiped some nofitication away, or I closed some app (that had notification icon), the notification icon(s) did not disappear from the bar, but applications were closed...
What is the most important information is that this behavior started for me yesterday morning OR Wednesday evening /not 100% sure here/. And also what is important is that my colleague has the same phone (bought from different seller, but again unbranded etc.) and he started to have the exact same issues on Tuesday (8.5.2018).
Any help from you would be much appreciated, I am assuming it was caused by some background update of whatever (Google? Huawei?)
Thanks.
skubko

Easier (and faster?) than looking for the needle in the haystack is to backup with HiSuit and then factory reset in the stock recovery.
Then instead of restoring apps, download them from Google Play and setup manually the ones you can. Check progressively for any behaviour (lag and drain). Install something to check SOC utilization per process, like a task manager.

zinko_pt said:
Easier (and faster?) than looking for the needle in the haystack is to backup with HiSuit and then factory reset in the stock recovery.
Then instead of restoring apps, download them from Google Play and setup manually the ones you can. Check progressively for any behaviour (lag and drain). Install something to check SOC utilization per process, like a task manager.
Click to expand...
Click to collapse
Yeap, if this would be case just for myself, it would have been the first thing I would do. But if two different phone owners have the same issue, I do not think factory reset will do the trick. I will just loose everything, will need to setup everything manually, install manually and for nothing as I believe the same situation will appear afterwards... My first guess is Google Play Services. When I check it in Google Play store, from yesterday there are several one-star comments complaining about different misbehaviours, I am just surprised that here in Honor 8 forum I did not find any complaints yet...

I'm having the same issue for the last couple if days
Sent from my FRD-L09 using Tapatalk

My mother has this phone and is having the same exact issues for the last few days. Really bizzare stuff. She just called to let me know she has a full battery before going to bed last night and now it's drained to nothing and the time is somehow two hours behind so her alarm didn't go off. She almost missed getting up for work. A restart seems to return it to normal but not for long.

The same problem appeared by me, fw B404. From yesterday, the wifi goes down, sees no network. Today it appeared unresponsive only SW buttons worked but no apps. I tried the restart now it tooks 10 minutes.

Hello everyone,
I have the same problem for a few weeks on my FRD-L09.
After a few minutes or hours, my phone becomes very slow and the battery is empty very quickly. Wifi becomes hs too. I can just unlock the phone.
I made a factory reset and the problem is still present. Glad to see that I'm no longer the only one to have this problem!

Have anyone installed and pulled some logs from CPU Spy?

I am facing same issue on my L02 model from past 2 days, many apps slows down or not load properly like uber, facebook, walpy, google assistant and some other google apps. May be honor slows down the phone like apple, to increase their latest phone sales or its due to google tickling with their services..

hello all,
- do you have an SD card? if yes, have you tried removing it?
- emui comes with avast pre-installed, which updates and scans behind the scenes. maybe it's a bad virus definition update, try to disable it!

for me, I don't have sd card and avast is not installed.
I'm in stock rom and the problem seems to be present since the B403.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I was just toying around with my mother's phone and initallly it was fine but then froze in the same way people describe. Restarted and was fine but then apps started launching on their own until it eventually froze. It's like it's possessed. I've had Play Service issues specific to my Axon 7 in the past but nothing like this. How the hell does the system time change itself and lose two hours? That's bizzare. Someone in China having a little fun?
This just started out of the blue a few days ago. She noticed it Wednesday but it might have started Tuesday. She's 70 and often complains about her phone and it's just her. It's obviously the phone this time.

Hybris03 said:
for me, I don't have sd card and avast is not installed.
I'm in stock rom and the problem seems to be present since the B403.
Click to expand...
Click to collapse
Avast scanner is preinstalled and included in Phone Manager, so you have it for sure, but it is well hidden. Go to Phone Manager -> Virus Scan and you will see their logo. You can disable periodic scanning from there.
Two more questions that may help you:
- Is the problem persisting if you set the phone to Power saving? Or ultra power saving? (although in the latter case most of the functionality is disabled anyway)
- Have you tried to install BetterBatteryStats (with the extra permissions using adb commands) and check what is causing wakeups/alarms and partial wakelocks? Maybe that will help you identify the culprit.

I've got exactly the same problem, which also started a couple of days ago. The phone becomes unresponsive - I can unlock it but not much else, possibly remove notifications but the ones below don't move up when I do. A restart only helps briefly, and I have to do it by holding down the power button for 10 secs, otherwise, it gets stuck on the reboot animation.
edit: My phone is also an Honor 8.

supersakis said:
Avast scanner is preinstalled and included in Phone Manager, so you have it for sure, but it is well hidden. Go to Phone Manager -> Virus Scan and you will see their logo. You can disable periodic scanning from there.
Two more questions that may help you:
- Is the problem persisting if you set the phone to Power saving? Or ultra power saving? (although in the latter case most of the functionality is disabled anyway)
- Have you tried to install BetterBatteryStats (with the extra permissions using adb commands) and check what is causing wakeups/alarms and partial wakelocks? Maybe that will help you identify the culprit.
Click to expand...
Click to collapse
It's ok for avast.
Problem is always present with the different modes of the power manager.
I'm currently at work, I will test BetterBatteryStats tomorrow night.
Thank you for your help

Downgrade to March
Downgrade to March Upgrade B403 seems to solve the problem.

Got an update for L09 B395. my phone becomes unresponsive everytime my phone get sleep while wifi is open. the problem is due to wifi setting "Keep wifi ON during sleep" is set to NEVER. when i changed the wifi setting to "Always" my phone run smoothly again.

aedel said:
Got an update for L09 B395. my phone becomes unresponsive everytime my phone get sleep while wifi is open. the problem is due to wifi setting "Keep wifi ON during sleep" is set to NEVER. when i changed the wifi setting to "Always" my phone run smoothly again.
Click to expand...
Click to collapse
I will try changing the wifi settings and if the problem persists, I will try downgrade to B403.
I'll keep you informed.

Hybris03 said:
I will try changing the wifi settings and if the problem persists, I will try downgrade to B403.
I'll keep you informed.
Click to expand...
Click to collapse
Downgrade was not successful... after some hour the same sh*t.
Indeed, the problem has something to do with WiFi.

kharthax said:
Downgrade was not successful... after some hour the same sh*t.
Indeed, the problem has something to do with WiFi.
Click to expand...
Click to collapse
After mofidifying wifi setting on "never", battery drain seems to be normal.
I confirm that tomorow after a full day of use.