Related
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you on a custom rom or stock rom ?
If on custom what rom and kernel u using?
Flashing another kernel may help
Sent from my GT-N7000 using XDA
docsportello said:
Hi, sometimes my note turns off by itself. When I try to wake the screen it doesn't wake and I have to push power button for some seconds before the note restarts. Is any if you experiencing the same issue?
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Are you sure it's totally off? I had this issues when phone looked like it's turned off, but when I pushed buttons for a while it was waking up, so I didn't have to restart it. Some people recommend using jBroid Kernel Cleaning script before you flash new kernel.
And if it's happening after installing new ROM I would recommend to flash stock ROM, then doing a full wipe twice and then flashing ROM you currently use or want to use.
I don't have such problem anymore so it might help.
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
docsportello said:
I'm on the custom rom, I've never rooted my device. The phone is like dead, it's not even turned off. At first I had to put the battery out and then put it in again. Then I discovered that if I pressed the power button for something like 5-6 secs it started again, with the samsung logo and all. Not a big issue but if I don't check my note often I risk to miss important calls. Please help me! Thanks
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
What apps do you have installed? I had this problem with both WidgetLocker and NoLed.
WidgetLocker I have just given up with - wish id never bought the stupid thing, as it's never worked reliably on my Note or my tablet! (rant over).
NoLed I traced the problem to the flash-the-screen battery saving features. Changing it to leave the screen on all the time when notifying hadn't seemed to use any more battery life and my dead screen problems have gone away.
Just something to consider!
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
squicky said:
You can try connecting your Note to the PC when running Samsung Kies software. Maybe it will find an update to the ROM you are on right now and this might fix your issue. If not you should go to the developement section of this forum and search for the recent stock rom available and then follow dr. ketan's guide http://forum.xda-developers.com/showthread.php?t=1424997
If flashing new ROM wouldn't solve your problem, then I guess it's a hardware issue that requires professional service.
Click to expand...
Click to collapse
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
kelvin fong said:
I think he should try a different kernel first. Another possibility is that some apps in your phone cause this problem.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I think its a stock kernel and ROM he's on... Even though he says 'custom ROM' he also says its never been rooted, so how would he get the custom ROM working if not by rooting the phone?!
That being the case it must be something interfering with the sleep mode so its probably best to check what has been installed recently, remove those apps one by one over a period of time and check if the problem goes away!
Yes it's a stock rom I am using and the issue happens randomly... Is it maybe lockscreen app? I read the users' comments and no one mentioned such a problem...
Sent from my GT-N7000 using XDA
me too my ho jus shuts off by itself.. I m using KL1 kernel wif KL3 rom
Note randomly shuts down - Did you solve this issue?
Hi,
I was wondering if you managed to solve this issue as I am experiencing the same issue where the phone randomly switches off when the screen is locked.
I am using easy battery saver app which sets the sleep schedule to check network data every 15 min.
Cheers
Galaxy Note 2 shuts down
The issue exists on the Galaxy Note 2 as well and has nothing to do with software.
The problem is hardware related. The phone is flawed and shuts off on it's own under various conditions, all hardware related. Take a look at this video: http://www.youtube.com/watch?v=SjLn2yikYnI
Also, take a look at this site I built that goes in to more detail regarding the issue: www.GalaxyNote2ShutsOff.com
One look at that short video and I am sure there will be some light bulbs going off. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
thanks for the heads up with NoLed....I just hope my issue ( phone's screen just dies when not in use - but I think the device is on as the headphone jack responds with the disconnection sound when unplugged) gets resolved...
I was thinking too that philz cwm may be affecting it ( kernel issues )? ...any way I will update as time passess
This has happened on both Stunner and Imilka CM9. Basically when I go to unlock the phone, the screen will show the previous home screen/app that was on before I shut off the screen, for just a flicker of a second, then will show the lock screen. It's as if the lockscreen itself is not activated until I go to 'unlock' the device.
This flicker is more of an annoyance than anything, but is anyone else experiencing this? How do I fix it?
octavian90 said:
This has happened on both Stunner and Imilka CM9. Basically when I go to unlock the phone, the screen will show the previous home screen/app that was on before I shut off the screen, for just a flicker of a second, then will show the lock screen. It's as if the lockscreen itself is not activated until I go to 'unlock' the device.
This flicker is more of an annoyance than anything, but is anyone else experiencing this? How do I fix it?
Click to expand...
Click to collapse
I had exactly the same flicker on early AOSP releases. Several other users confirmed it in the thread, but no solution was offered.
No such thing on CM9 for me now, though.
But as you say, it's just a mild annoyance, nothing more.
I have the same issue on imilka's CM9 ROM. Sometimes I see last runned app before phone was locked for a sec.
Sent from my GT-N7000 using XDA
Annoying! Maybe it's a problem with early ics leak and will be fixed later..
Sent from my GT-N7000 using Tapatalk
This is an ICS problem, even my stock Nexus s and my friends stock Galaxy Nexus have the flicker, some custom kernels for my Nexus s reduced the problem alot, but it still happened from time to time. Not much you can do about it.
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
lonehunter65 said:
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
Click to expand...
Click to collapse
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Miniloaf said:
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Click to expand...
Click to collapse
Do you know if devs are aware of this problem or working on it at all?
That's the only reason why I switched to DeSensed. It got annoying after a while.
I have been using 1.2 since it came out, and I have not experienced any random reboots or issues. I am using his kernel and am S-ON.
Sent from my HTC PH39100 using xda premium
I'm s-on and I've flashed with wcx recovery. Ive tried different methods of flashing the boot.img. Flashing it before and flashing the sd card copy afterward. I have also tried flashing either before or after. I did not select any UV. I chose the nonsense version of the install and am running apex launcher pro. I selected vram during install and disabled s2w. My CPU range is 384-1512 on setCPU, I am not running any profiles. I do use juicedefender ultimate and avast full time. I also have adaway installed. I can post a list of my other installed apps too if that would be relevant. Does any of this raise a red flag? Would the sense version of the Rom be more stable? Can anyone recommend another kernel if you believe that may be an issue? Any help would be appreciated as I do not have enough posts to state this problem in the dev forum.