Hey guys,
Not sure if anyone had thing kinda problem before. I have tried searching but to be honest, I don't even know what I'm searching for so here goes...
I got this problem with the screen when turning on the Galaxy tab as seen in the linked video.
If I turn it off and turn it back on, it works without issues but once I lock it and try to use it again, the screen goes wild again.
I think it started happening a week or so ago when i updated to the Official ICS ROM, and ever since then, I tried different ROMs but the issue stays with any ROM I flash from now.
Is this Modem or kernel related? I have not touched any of those yet.
Video Link: http://www.youtube.com/watch?v=pBRVChVyYls&feature=youtu.be
Any help is Appreciated and thanks in advance.
I had a similar problem 2 months after buying mine. to send and they had diagnosed it as a bad video controller. The parts were on back order and after 5 weeks they just sent me a new one.
When it started it would happen every couple of days somtimes randomly and sometimes after coming back from lock but by about 3 weeks after 1st seeing the problem it was happening every time I had it on for more than 1/2 hour. If you are still under warranty I would call support right away.
Good luck
loranz said:
Hey guys,
Not sure if anyone had thing kinda problem before. I have tried searching but to be honest, I don't even know what I'm searching for so here goes...
I got this problem with the screen when turning on the Galaxy tab as seen in the linked video.
If I turn it off and turn it back on, it works without issues but once I lock it and try to use it again, the screen goes wild again.
I think it started happening a week or so ago when i updated to the Official ICS ROM, and ever since then, I tried different ROMs but the issue stays with any ROM I flash from now.
Is this Modem or kernel related? I have not touched any of those yet.
Video Link: http://www.youtube.com/watch?v=pBRVChVyYls&feature=youtu.be
Any help is Appreciated and thanks in advance.
Click to expand...
Click to collapse
Related
i have had my wing for about a month and have resently learned about flashing roms.i have been using the open touch 7.4 lite for about 2 weeks and havent had problems until yesterday when i was listening to music and the screen kept turning grey and jus stayed there.and now its began to take longer to turn it on.ive tried new roms and reseting it bt nothing.can anybody help plz
edrift305 said:
i have had my wing for about a month and have resently learned about flashing roms.i have been using the open touch 7.4 lite for about 2 weeks and havent had problems until yesterday when i was listening to music and the screen kept turning grey and jus stayed there.and now its began to take longer to turn it on.ive tried new roms and reseting it bt nothing.can anybody help plz
Click to expand...
Click to collapse
i might be wrong, but i thought that there was a memory leak with the audio manager. the problem was that once audio manager was used it would run in the background continuously. i would look around this thread a bit, or just upgrade to a later release. good luck
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time
Hi
Has anyone experienced that the tablet switches off constantly with out any any specific reason?
I could easily surf or read an email without switching off.. but then i would watch a movie and it switch off instantly or the other way around and its not even shutting down.. it just goes from powered on, to completely switched off.. It does not get hot and it does charge perfectly and the battery level does not drop/discharge radically.. it has never been dropped or manhandled. and it started doing last week
I'm on stock 3.2 PDA:KMP CSC:KMP (XAB), not rooted..
Any ideas, suggestions?
Thanks in advance
I suggest you to discuss your matter from where have you bought the notebook as there might be some problem in hardware
SofiaBrown said:
I suggest you to discuss your matter from where have you bought the notebook as there might be some problem in hardware
Click to expand...
Click to collapse
What notebook?
You might have some apps installed that cause this...?
Jay Rock said:
What notebook?
You might have some apps installed that cause this...?
Click to expand...
Click to collapse
I hope he means tab?
Im gonna give that a shot. since that's the only thing i said i yes to, after the factory reset.
ill get back with the results
Thanks
-TB-
I used to own a Galaxy Tab plus 7.0, which experienced this known problem of random reboot and/or sleep of death. You could google that to find out more.
I've since returned it for a refund. Then I picked up this used P7500 a month ago. It has not experienced not even one reboot. Sure, apps do crash from time to time, but the OS never completely froze.
How long have you owned your unit? If relatively new, I would returned it. If for a while, and only recently you experienced the problem, then I would do a factory wipe, or at least re-trace your steps and uninstall the last few apps. Also, ask yourself whether the problem is already related to certain apps. If so, get rid of those apps.
hi
Did a complete wipe.. so now its close as possible to factory default..
Could it be a battery calibration error? it works plugged in to either pc or wall socket.. works 10min after but then switches of randomly
Thanks for all the help/suggestions so far really appreciate it!
I know some mentioned the option of returning it.. But its bought in the US and im located in Denmark!
-TB-
I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
KidCarter93 said:
I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
Click to expand...
Click to collapse
I had the same problem.I just opened the back cover and hit the mics with my finger several times. Since than I am not facing it anymore. I'm not telling its gonna work for you but you can give it a shot.
I had this problem as well but I fixed it. I found out the culprit causing it was the ROM that I was using. So I flashed back to stock and the crackling was gone! Whew.
Sent from my Nexus 4 using Tapatalk 2
I am facing crackling sound in headphone & also even in speakers , what problem will be ? Its terrible sound, cant even play any music .
KidCarter93 said:
I originally had this audio problem around 3 weeks ago while playing a game so I rebooted and it was working fine again.
A few minutes ago, exactly the same problem has happened again and a reboot hasn't resolved it, this time.
Here's a recording of the audio problem I'm having - http://db.tt/aqB3EM0W
EDIT - Again, it has sorted itself out but there's still clearly an underlying problem to have caused this.
If anyone's had this problem before, could you let me know how you fixed it and roughly how much it cost (if you took it to a repair shop)?
Thanks in advance
Click to expand...
Click to collapse
Which rom/kernel are you running with it?
kilometers4 said:
Which rom/kernel are you running with it?
Click to expand...
Click to collapse
Completely stock. Not even rooted. Since I edited the OP last to mention that it's fine again, it hasn't done it since but there's always a chance it could do it again.
KidCarter93 said:
Completely stock. Not even rooted. Since I edited the OP last to mention that it's fine again, it hasn't done it since but there's always a chance it could do it again.
Click to expand...
Click to collapse
Maybe try rooting? Might solve the problem. I'm rooted and have never had that issue.
kilometers4 said:
Maybe try rooting? Might solve the problem. I'm rooted and have never had that issue.
Click to expand...
Click to collapse
I think the problem must lie deeper than that somewhere because I stayed stock for a few months after getting it without a problem. I then decided to root + flash some ROMs, still with no problem. Then I had no problem for ages even after coming back to complete stock again.
I think I'll just have to wait and see if it does it again and then take it to a mate who'll be able to find out why it's done it and probably fix it
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.