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
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,
Hi,
I am experiencing random reboots since upgrading to 7.0 - aporx. 1 reboot per day.
I left logcat recording overnight and succesfuly catch the right moment, however I am not seeing anything clear.
Can someone look for any unusual things please?
Sooo... Having an issue with bluetooth and 1 speaker... Can connect to my others but this 1 wont let me after i reflashed my phone. Tells me password error for device but doesnt prompt me to enter one. Last time this happened after about 100 times trying to pair it went through.. Any1 else have this issue or know a work around? Cleared cache rebooted phone and speaker. Other coworker unpaired and paired with speaker in like 2 seconds. Kinda frustrating lol thanks all
Hi all, since I bought this phone I've a really annoying problem with WA. When I've WA open in a chat and switch apps from multitasking (eg switching from WA to Instagram)and then return to WA from multitasking agaun, my phone freezes for like 5 seconds becoming unresponsive (sometimes even the power button wont work). I have no idea what's happening, I tried uninstalling and reinstalling WA several times but nlthing changed. I tried also take a logcat but the only thing I found it this line:
Code:
InputDispatcher: Waiting for application to become ready for input: 29556. Reason: Waiting because the touched window's input channel is full. Outbound queue length: 1. Wait queue length: 104
...
InputDispatcher: Waiting for application to become ready for input: 29556. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 27. Wait queue head age: 575.5ms.
Do you have any advices?
Ty