So this was happening before but I factory reset my phone and now after about a week and a half it's happening again;
everytime i either go back to the previous screen, or while i'm on a loading screen (noticed it a lot with Netflix) but i get these green pixely squares that flash on my screen... this a known issue with the version? or should i take my phone back?
I'm not really sure how to better describe it...
Have yet to experience that, had my unit for over 2 weeks.
Take it back.
-smc
I have the same problem with mine had it since it came out?
Sent from my DROID3 using XDA App
I've had the same issue. Started happening within 2 weeks, but more recently it hasn't happened much. A battery pull always fixed it for me. I'm experiencing random reboots when the phone hasn't been touched for ten minutes, this is more disconcerting to me
I haven't noticed it after a reboot for a couple days now...
But i do remember almost directly after it first happened (before i did the factory reset) my phone started doing the whole random reboots too. That's when i read the post about fixing the camera and not using the assistant backup/restore functionality when you activate the account...
I thought it had fixed all the issues but seems they're still there just, less sever...
Rebooting the phone (temporarily) fixes the issue for me
[sent from my droid]
I swear, after using the camera this happens. Until I reboot I get some kind of green checkerboard whenever the screen rotates or changes
Same here. Every time I use the camera and sleep the phone it will get hot and drain the battery. Waking the phone gives me green pixellated images and serious slowness. Battery pull after taking pictures is the only way to mitigate it...for now.
Sent from my DROID3 using XDA App
So this seems to be a common issue... has anyone been able to talk to motorola? is there an update coming out anytime soon to get it fixed? or is it just a hand full of bad phones?
smc, have you still not experienced any of these issues?
can you try seeing if it might happen after some of these scenarios listed in this thread? would be greatly appreciated!
I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;
I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?
I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
I'm on stock room and unrooted. Like I said first time it's happened.
i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted
I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.
Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.
My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.
Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.
Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?
Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?
metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.
mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?
Hey,
I have an HTC One black - stock os - UK unlocked version - after 4.2.2 update.
I've got a strange problem regarding the top of the touchscreen. when the phone is horizontal, the top bit (between the top bar to the first widget) is not working. the rest of the screen working fine. when I pick the device up, the screen is working fine 70% of the time. as a result, I cant open the notification bar and it thinks that I'm clicking or re-arranging my widgets.
It's weird because IT DOES work 60% of the time.
1. did any of you experienced any of this before?
2. What do you think it is? software or I have to replace the digitizer?
3. Is it just calibration problem? I tried to calibrate the device using the keyboard screen calibration and it didn't do anything.
Thanks!
Eran.
i have a similar problem and no solution so far
sandmann241 said:
i have a similar problem and no solution so far
Click to expand...
Click to collapse
so what did you do/planing to do?
eranbaruch said:
so what did you do/planing to do?
Click to expand...
Click to collapse
Bump for more responses
I
I just started experiencing this same problem today as well. I was on a Google Edition 4.3 Rom for about 2 days, Viper 3.2 I believe and everything was initially working as it should. Suddenly I began experiencing the non responsive status bar. I cleared data & cache, fixed permissions, and even tried a factory reset with no luck. I then reinstalled the Rom and the problem persisted. I then downloaded and installed black jelly Rom along with a complete wipe of the entire storage after transferring important data to my PC, but the status bar was still unresponsive and it appeared the top 1/4 inch of display had a digitizer issue. I tried to restore an older backup of Venom Rom running Sense and I still had no luck, until I went into the browser so that I could rotate into landscape to see if I could access it from this orientation (don't know why that didn't cross my mind sooner?) After I pulled the notification shade in landscape I left it down and rotated back into portrait mode and drew the shade back up slowly, following through with the gesture all the way to the top of the display. Then the functionality from portrait was restored! I believe this is a software bug of some sort, but I'm contemplating returning it to stock and relocking the bootloader to return it. I'm actually using the Tmobile variant and it's only about 30 days old. My insurance will cover a replacement for a faulty unit, but who knows if will happen with another? After a Google search I discovered this was an issue that surfaced with quite a few One X's as well, so I'm thinking it may be a bug that's consistent with some HTC hardware of a different variants? Any updates or insight would be appreciated.
Has anyone else noticed problems with CM crashing on their Atrix HD? I have been running CM on mine since September and have noticed the same problems in both CM 10.2 (epinter) and CM 11 (official). I never noticed any problems with the stock software. I have identified at least two different types of crashes.
Type 1 typically happens overnight when plugged into a charger (though less so with more recent builds) or when the phone is idle in my pocket. There is no notice the phone has crashed though sometimes if it happens in my pocket the phone seems to warm up somewhat. When I pull out the phone and press the power button I get nothing at all. This requires holding down the power and volume buttons for an extended period to force the phone off and then restarting it.
Type 2 typically happens when on an active phone call, though it can happen other times when using the phone as well. This involves the phone crashing and immediately going into a reboot (red M on the display as soon as I pull the phone away from my head).
I also have a less serious issue where when I press the power button to turn on the screen it will occasionally display the lock screen but refuse to take any touch input. I can usually get things to work by pressing the power button a few more times to turn the screen off and on again.
Just yesterday I switched to the new unified builds and have not seen all of these happen yet but I have definitely seen a type 2 already. Just wondering if these problems are widespread as I don't see them discussed a lot and if there's anything I can do about them.
Nothing? Am I really the only one having these problems? For the record I have now seen both types of crashes on the unified build.
May be you can try to flash stock rom:silly:
Try flashing the latest Validus ROM. I have been using version 4.3, which is based on KOT49H and it's been very stable with no crashes.
Is there a crash log that I can capture and review after a crash?
BenFranske said:
Is there a crash log that I can capture and review after a crash?
Click to expand...
Click to collapse
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
kabaldan said:
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Click to expand...
Click to collapse
Great, I'll check those out the next time I have a crash. I am thinking there will almost certainly be some useful information for the second type of crash where the phone actually reboots itself. I am less optimistic that there will be any information when it simply locks up and I'm forced to reboot it by holding power and volume down buttons.
kabaldan said:
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
Click to expand...
Click to collapse
Thanks for the helpful information there too. My sister has forbidden me from wearing belt cases for at least the last 10 years but it's at least nice to understand what the problem is!
Crash Logs
Sorry it took me a while to get back to this. I've attached a few crash logs that I captured last month. I have updated the OS several times since then but I'm still experiencing both of the types of crashes I originally mentioned. Any assistance in interpreting the logs is appreciated!
Any ideas about what might be causing these crashes and reboots?
Am I really the only person with these issues? How can that be?
Hello,
I own the watch for about 1 year, and recently I faced issues with it,
The upper notification menu stays on the screen and start flashing in glow lightning, sometimes it's half screen, or just 2 lines from the top.
I think it's a burn-in but not sure, it appears only after leaving the watch without use (usually at night, and i can see the problem appearing in the morning).
It disappearing alone after playing with the watch for couple of minutes (turning off,on...)
*I'm running on LeeDrOiD latest rom
**can't post pictures cause i'm a new user....
Does anyone faced this issue, or have a solution for this ?
Thanks Ahead
Yes, a lot of post for this common issue.
it stop after a while and maybe related on the face used and on the time where the screen stay off.
Thanks, the problem seem to have been fixed after flashing the original stock rom.