Related
There is this problem that i seem to be having that i cannot find any information on at all, i mean i have seached the forums several times and no one seems to be having the same problem as me
Basicly every now and again when i hit the power key to bring the phone screen back on it will sort of glitch and turn into a sort of negative look, you know the kind of effect you can set the camera to do, it looks like that and i cant remove it without a reboot and its getting a bit annoying, i just thought maby someone could help me
I am using the new shubcraft 1.4c and maxsenseui energy rom for WM. And i might as well ask if there has been any solution to the screen not coming on straight away when i press the key to wake it up, it doesnt ever sod but it does not come on straight away and sometimes i have to hit the power key several times to get it on but thats no show stopper whereas my main problem is pretty annoying. Thanks for any help in advanced and thanks to all of you guys that made android on HD2 possible
Cheers Dane.
xpstyle36 said:
There is this problem that i seem to be having that i cannot find any information on at all, i mean i have seached the forums several times and no one seems to be having the same problem as me
Basicly every now and again when i hit the power key to bring the phone screen back on it will sort of glitch and turn into a sort of negative look, you know the kind of effect you can set the camera to do, it looks like that and i cant remove it without a reboot and its getting a bit annoying, i just thought maby someone could help me
I am using the new shubcraft 1.4c and maxsenseui energy rom for WM. And i might as well ask if there has been any solution to the screen not coming on straight away when i press the key to wake it up, it doesnt ever sod but it does not come on straight away and sometimes i have to hit the power key several times to get it on but thats no show stopper whereas my main problem is pretty annoying. Thanks for any help in advanced and thanks to all of you guys that made android on HD2 possible
Cheers Dane.
Click to expand...
Click to collapse
I think the 'slow' wakeup is a known issue... I think
As for the negative efect, I got the same thing a few times, but it all seemed to stop after I started using mskip's bootloader....coincidence, maybe but its worth a try.
Lock estimate: 11:33 AM GMT
thesweeney said:
I think the 'slow' wakeup is a known issue... I think
As for the negative efect, I got the same thing a few times, but it all seemed to stop after I started using mskip's bootloader....coincidence, maybe but its worth a try.
Lock estimate: 11:33 AM GMT
Click to expand...
Click to collapse
Ah ok, i will try that now and thanks for the rapid response, didn't expect one that quick heh.
Dane.
xpstyle36 said:
Ah ok, i will try that now and thanks for the rapid response, didn't expect one that quick heh.
Dane.
Click to expand...
Click to collapse
No worries,... as i said, the bootloader may not have been what fixed it for me, it may have just been coincidence... but I know I have had far less problems and not a single WSOD since using the bootloader....
Good luck
thesweeney said:
No worries,... as i said, the bootloader may not have been what fixed it for me, it may have just been coincidence... but I know I have had far less problems and not a single WSOD since using the bootloader....
Good luck
Click to expand...
Click to collapse
Thanks alot Ah i love XDA such a nice bunch of people, would never get that level of tech support in a 3 shop lol !
I have this happening randomly at times, but very rare at think twice
now in a span of 2 weeks. It happened even after I stopped using
Android loaders (ie., mskip) (every time I make a fresh test, I HR winmo, format my sd card then start a fresh) as i said it is very rare
and occurrence is difficult to attribute to anything in particular
Before my actual WinMob ROM I had this effects a few times, now I haven't had it for about a week... Chuckys ROM has a "build-in" Android-loader, works fine for me...
This happened to me yesterday
I pressed the power button a few times in quick succession with a press of the home button thrown in somewhere for good measure.
I should learn to be more patient and let the screen come on
Im also using Mskips loader so can confirm this doesnt stop the issue
it happened to me once when i was using old kernals it also happened on windows mobile , but with new kernals it works fine
solved with frantic key presses
Mr_Erratic said:
This happened to me yesterday
I pressed the power button a few times in quick succession with a press of the home button thrown in somewhere for good measure.
I should learn to be more patient and let the screen come on
Im also using Mskips loader so can confirm this doesnt stop the issue
Click to expand...
Click to collapse
same thing happened to me and I got out of it using the ur frantic power button press solution []
thanks.
Hi,
Imilka reported on this saying it was only a glitch. Just reboot and don't worry about it.
Its happened to me a few times, mainly when I disconnect my charger.
Flashed from my fingers to your face
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.
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
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
Never had one so far. Running stock 4.2.2/Franco kernel nightly_110
-Edit- currently undervolted -75 mV.
just stop messing your phone up with stupid OCing and benchmarks... This issues are installed to protect the hardware from crashing... ( Red light of death... )
My phone just fine. never had this SOD.
Never had an issue on this device. On my old phone, dropping the min CPU speed too low would cause it a LOT.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
You don't have an option for unable to turn on phone without a reset: no blinking led. This is also a scenerio.
Please take a look here! http://forum.xda-developers.com/showthread.php?t=2195278
I've tried almost everything (wipe& re wipe , install stock ) and nothing seem to solve it.... most frustatin thing is when I hit "home" after playing heavly and ...bamm it goes black screen & hav to reboot pressin home&vol+
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Im using it now (customROM&UV) since it doesnt affect my issue.... I tried completly stock for 2 days and keep crashin... or at least on g.earth as I didnt install any app/game to be sure its not an app related issue.
Cant figure out what happens, it can play games w/o any issue, but sometimes when I change orientation it just goes black
PD: I dont hav enough time, but ill do a logcat to see what can possibily make it freeze
My case is not listed in the poll options:
- the phone went into standy, good battery, no calls, no high loads;
- LED was inactive totally.
- then I was unable to turn it on normally (only through reboot).
While in this state, trying to call the phone resulted in "long" tones, i.e., like the network saw the phone. The phone did not ring.
This happens with the latest stock firmware on the 2nd day of my use. Non-reproducible. Phone returned.
Would be delighted to learn if that's a hardware or software issue
Not necessarily SOD but experienced extreme battery drain under these situations
1- Charging via USB and left phone connected after PC shut down.
2- Charging via Wireless Charger left it on the pod.
In 1st ASA pc is shut down
and
In 2nd ASA Phone charged completely , as I suspect the charging process goes backwards ! It someone drain current from your battery to the power source.
AFAIK none of these issue are positive with normal good old AC charging. However you can still use a workaround by using the app called "Safe Charge"
This is my experience
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.