Hi,
Since a few weeks, I am experiencing horrible lags and freezes with my Galaxy Note 4 (SM-N910F) running Android 5.0.1 (N910FXXU1BOC5). It happens everytime I have a connectivity change and turns my phone into an unusable brick for long minutes each time (and draining my battery like mad!). I tried to wipe cache from recovery but it only helped for a few days top.
Issue :
I realized that when connectivity changes (4G to WiFi, 3G to 2G, No connectivity to 3G or WiFi), my device hangs completely, lags and freezes. It can last for a couple a minutes ! The touchscreen doesn't respond to any input or when it does, it lags like hell. Example : when I touch a button, the ripple effects begins almost 5 or 6 seconds afterward and is displayed frame by frame (like at 1fps). When changing activity, the screen goes black for 10 to 15 seconds.
When I listen to music when this happens, the sound is distorted or even stops.
I also noticed that the bluetooth sometimes goes off by itself.
The battery stats doesn't show anything ; CPU&RAM monitoring apps neither. I turned on "Show all ANRs" and I received a lot a "apps not responding" when it happens. Almost all my apps (at least the ones having background services) stopped responding.
I didn't see anything on the logs that could explain what happens, except that it show a lot a entries related to lack of memory :
This one appears a couple of times :
Code:
08-13 10:42:04.562: W/Binder(8832): Caught a RuntimeException from the binder stub implementation.
08-13 10:42:04.562: W/Binder(8832): r: Expected object header. Got 0x1 Parcel: pos=136 size=240
08-13 10:42:04.562: W/Binder(8832): at b.a(PG:10000)
08-13 10:42:04.562: W/Binder(8832): at bza.createFromParcel(Unknown Source)
08-13 10:42:04.562: W/Binder(8832): at byb.onTransact(Unknown Source)
08-13 10:42:04.562: W/Binder(8832): at android.os.Binder.execTransact(Binder.java:446)
Hundreds of entries like these ones :
Code:
08-13 10:42:06.932: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.942: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.962: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.982: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
Also, lot of entries like
Code:
08-13 10:42:07.132: I/Choreographer(15879): Skipped 148 frames! The application may be doing too much work on its main thread.
Anyone experienced this before ? Is there a known fix or a tip ?
Check the mobile data limit is turned off
It is off.
I do not know how to further investigate. Any idea what I could do to isolate the root cause of it ?
I had absolutely the same issue, plus sometimes it showed me no signal until I rebooted...
SurfaceFlinger and Choreographer is because the UI hangs...
now for the interesting part: I always flashed the latest rom available, because I thought this would have no impact on stability! latest was the Nordic pf2.
then I got a Gear VR and it took me a day to get it working. the thing was that the Gear VR software checks your rom and more important, the CSC. after I reflashed the latest official rom for my original CSC DBT (open germany), the Gear VR was working!
check in your dialer with *#1234# if a CSC code is shown, for me this was not the case until I reflashed, now I'm on BOC3 for modem, PDA and CSC and everything works as it should!
TML1504 said:
I had absolutely the same issue, plus sometimes it showed me no signal until I rebooted...
SurfaceFlinger and Choreographer is because the UI hangs...
now for the interesting part: I always flashed the latest rom available, because I thought this would have no impact on stability! latest was the Nordic pf2.
then I got a Gear VR and it took me a day to get it working. the thing was that the Gear VR software checks your rom and more important, the CSC. after I reflashed the latest official rom for my original CSC DBT (open germany), the Gear VR was working!
check in your dialer with *#1234# if a CSC code is shown, for me this was not the case until I reflashed, now I'm on BOC3 for modem, PDA and CSC and everything works as it should!
Click to expand...
Click to collapse
I have the same problem with my Note 4, but I have the original CSC (XEF) for my rom so CSC isn't the problem. I also have BOC5 so maybe the problem is linked to this specific rom version.
ant1fr said:
Hi,
Since a few weeks, I am experiencing horrible lags and freezes with my Galaxy Note 4 (SM-N910F) running Android 5.0.1 (N910FXXU1BOC5). It happens everytime I have a connectivity change and turns my phone into an unusable brick for long minutes each time (and draining my battery like mad!). I tried to wipe cache from recovery but it only helped for a few days top.
Issue :
I realized that when connectivity changes (4G to WiFi, 3G to 2G, No connectivity to 3G or WiFi), my device hangs completely, lags and freezes. It can last for a couple a minutes ! The touchscreen doesn't respond to any input or when it does, it lags like hell. Example : when I touch a button, the ripple effects begins almost 5 or 6 seconds afterward and is displayed frame by frame (like at 1fps). When changing activity, the screen goes black for 10 to 15 seconds.
When I listen to music when this happens, the sound is distorted or even stops.
I also noticed that the bluetooth sometimes goes off by itself.
The battery stats doesn't show anything ; CPU&RAM monitoring apps neither. I turned on "Show all ANRs" and I received a lot a "apps not responding" when it happens. Almost all my apps (at least the ones having background services) stopped responding.
I didn't see anything on the logs that could explain what happens, except that it show a lot a entries related to lack of memory :
This one appears a couple of times :
Code:
08-13 10:42:04.562: W/Binder(8832): Caught a RuntimeException from the binder stub implementation.
08-13 10:42:04.562: W/Binder(8832): r: Expected object header. Got 0x1 Parcel: pos=136 size=240
08-13 10:42:04.562: W/Binder(8832): at b.a(PG:10000)
08-13 10:42:04.562: W/Binder(8832): at bza.createFromParcel(Unknown Source)
08-13 10:42:04.562: W/Binder(8832): at byb.onTransact(Unknown Source)
08-13 10:42:04.562: W/Binder(8832): at android.os.Binder.execTransact(Binder.java:446)
Hundreds of entries like these ones :
Code:
08-13 10:42:06.932: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.942: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.962: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
08-13 10:42:06.982: W/SurfaceFlinger(300): EventThread: dropping event (7673796e) for connection 0xb3fa3c68
Also, lot of entries like
Code:
08-13 10:42:07.132: I/Choreographer(15879): Skipped 148 frames! The application may be doing too much work on its main thread.
Anyone experienced this before ? Is there a known fix or a tip ?
Click to expand...
Click to collapse
I think I fixed the problem. As I had the same problem and the same software version, I put the previous version I had, i.e. the BOC3 (CSC : TPD). And it seems that the freeze disappeared ! Give this a try
Having the exact same issue.
I am on PDA: N910FXXU1BOC5 with CSC: N910FBTU1BOB2
Going to wipe my phone, flash PDA: N910FXXU1BOC3 over the weekend and see if it fixes the issue.
Been on BOC3 since the weekend and no more issues.
Sent from my SM-N910F using Tapatalk
Same here : no more issue since revert back to BOC3
I'm on BOC3 (update to BOC5 never came through) and I'm having this same problem
I just cleared the cache partition via the bootloader and, while I'm still having lag, it's much better.
Never mind, after a couple of days I'm having the problem again. Any other ideas short of changing ROMs?
Same problem here.
Non-rooted (and not able to root as it is a work-provided phone); 5.0.1 generic (Australia) ROM; Baseband vers. N910GDTU1BOC5; Build no. LRX22C.N910GDTU1BOC5.
Any ideas on how to fix this?
antman68 said:
Same problem here.
Non-rooted (and not able to root as it is a work-provided phone); 5.0.1 generic (Australia) ROM; Baseband vers. N910GDTU1BOC5; Build no. LRX22C.N910GDTU1BOC5.
Any ideas on how to fix this?
Click to expand...
Click to collapse
One word : update. The issue seems linked to BOC5, so you may downgrade but also upgrade with new 5.1.1 firmwares (some unbranded phones got the OTA update today like unbranded italian).
I have had the exact same problem for quite a while with my stock 5.0.1. I never could figure out what was causing it but it makes sense that it could be when switching data sources. My S-Pen works when this is happening but the normal touch does not respond at all.
N910W8LU1BOE2
LRX22C.N910W8VLU1BOE2
Updating to 5.1.1 has helped, it's nowhere near as laggy as on 5.0.1. However, it can still be unresponsive at times when switching between mobile data and wifi. Wiping the cache partition seems to improve things for a day r 2. It's a big step up on 5.0.1 but still not perfect.
However, I am now more frequently receiving a message from my Samsung Gear Live watch that Android Wear is not responding but, when I tap on "Wait" in usually responds quickly,
Related
Hi. I'm having an extremely strange error on my ADP1 (not sure the exact model number, seems to just be a normal adp1 though i flashed DREAMIG when I re-rooted, as I was on the T-Mobile UK and also US (where I got donut, really weird) OTAs ). Anyway, I'm on CM 5.0.7 G1 with the official 1.6 radio from HTC and I have two main problems:
*Sometimes the phone just shuts off with a resonant image left on the screen. Had this error since CM 4.</li>
*The screen goes blank with the green notification light on and the phone will not work without a battery pull</li>
The first error reports nothing: it just stops.
The second error I ran a logcat on. Every time I press a button, a line appears with
D/KeyguardViewMediator( 112): wakeWhenReadLocked ( [button number] )
This line also appears a few times before the crash
W/ActivityManager( 112): finishreciever called but none active
Anyone know what the "green light of death" problem may be? Is it fixable?
Thanks.
EDIT: HTML fixed oops
Hello All,
I just got a new XPERIA E4 (Model E2104) from CLARO RD, its running on 4.4.4 KitKat , 24.0.A.2.12 Firmware and 3.4.67 Kernel. The thing is i have encountered a lot of problems and would like to know if its possible to update to a newer Firmware version (24.0.A.4.14 at least) in hopes of fixing them. I downloaded FlashTool and XperiFirm, and got the latest firmware from the XperiFirm database for this model (24.0.A.5.14) but im unsure of the flashing process, since ive never done it before. I went through some tutorials and saw that there was a bundling process involved but apparently the E4 is not supported since it doesn't show on the devices list for bundling that the program has, also saw another method that was done directly without the bundling but im unsure of what to check and what not to on the wipe options.
Problems include:
-Phone shutdowns and restarts automatically if left untouched for random intervals, sometimes it does it in short intervals ending in a "no screen lock position" (power button doesn't lock the screen and screen doesn't "sleep"), having to restart the phone by long pressing the power button and selecting Restart option to fix it.
-WIFI stops receiving data and stops working after extended streaming on YouTube (somewhere from 15 to 30 minutes), shutting down and turning back ON the WIFI doesn't work, Restarting the phone fixes this also.
-Doesn't allow 420p quality on streams either nor HD (but i think it doesn't support 720p on the E4 anyways).
-Battery doesn't last as much as its supposed to, screen sometimes uses 70% power on low brightness and nothing open.
I replaced the first phone i got for a new one and still having the same problems, so i figure it must be software related or a faulty line of phones.
Any help would be appreciated!
Thanks
I bought a Xiaomi Redmi Note 3G last September and it has been performing fine until very recently.
The phone works fine approximately 75% of the time, but intermittentlythe following problems occur simultaneously:
- Signal drops completely and 'NO SIM' is displayed
- The battery level drops around 1% every 20-30 seconds
- The volume and power buttons are unresponsive
- Wi-Fi disconnects
Sometimes the phone recovers from this and starts operating as normal,and sometimes the phone restarts and goes into a boot loop, eventually turningback on. Whilst the above problems occur,most other phone functionalities still work i.e. can still open upapplications, and swipe around the home screen.
Can anyone help?
Thank-you
EDIT: I should add that since this problem started I have tried a different rom and the problem has remained.
Hi,
have u wiped ur system (cache dalvik) before installing another ROM?
Try to pick a ROM that is confirmed to be stable to avoid bugs.
I have an S7 edge (SM-G935F) that currently runs the Superman rom. It has a strange issue where suddenly, out of nowhere, wifi stops responding. It has done this before, but then it was on stock rom. It was actually one of the reasons I reflashed it. After flashing, everything was fine for 2-3 months and then it started acting up again.
It's so bad that I now mostly run it on 4G (luckily I have a 35GB plan) because it can take upto a full minute to get it to respond on wifi after it's been sleeping.
As far as I can tell, the problem manifests itself like this:
* Phone has been unused for a while, wifi is on, wifi is connected to a network (problem is not network specific)
* I try to open any app that uses data, no response. If I just keep hammering retry/refresh/update etc it starts responding after anywhere between 20-60 seconds.
* During the non-responsive period the wifi-icon sometimes gets the little exclamation mark, but not always.
* After a period with wifi off it sometimes uses 20+ seconds to refresh and connect to a known hotspot.
I can probably fix it again by reflashing another rom, but I'm afraid the problems will be back in another few months.
Any suggestions on what I can try (besides returning it, I'll do it if I have to, but I'd rather not). Are there any wifi logs I can check after the problem appears next time. (I know how to use a terminal)
Anything
--
Rom: Superman Rom 2.4.1
Baseband: G935FXXU1DQGC
Kernel: 3.18.48-SuperStock_SM-G935F_V2.4.1
--
Install the stock rom. It was your faulty custom ROM if all get back to normal.
Sure, I can do that. But you did see that the problem existed before I installed the custom rom right?
The original manifestation of the problem was the reason I flashed another rom in the first place.
After ~14 months of ownership my phone started to get a bit wonky. My assumption is the bluetooth modem is hanging on a periodic scan/probe, causing processing of the central event loop (sadly I'm not an android dev, so I don't know what it's actually called - but the event loop that *everything* on the phone ties into for time and event based notifications) to seriously lag.
Examples: clock alarms do not go off at the correct time - they can be 5 to 20 minutes delayed. LightFlow's control of the LED is delayed by 1-10 minutes (e.g., stock light color comes on immediately, switches to lightflow's some time much later). Lightflow is set to clear the indicator once the phone is unlocked, but that doesn't happen until several minutes *after* I've unlocked the phone.
Turning off bluetooth via settings or the quick pulldown resolves this and the phone goes back to normal.
I've tried removing all bluetooth pairings, wiping data and cache of Bluetooth Share, wiping all cache, installed jrkruse's Hybrid BRA1 ROM, all with no change. This phone has never been rooted.
I use bluetooth a lot, so keeping it disabled all the time isn't super great.
I had similar issues with my S4, but switching ROMs tended to fix it, and certain modem FWs seemed better than others.
Any ideas?