Related
Recently it has been turning itself off for no reason. I also notice if I open and close the phone a few times it turns off as well seemingly at random.
Anyone else have this issue? I hate looking in my pocket to find my X1 off. it has a full battery so what gives?
yer i had this problem a few times.. update to the new R2A Rom.. should fix it
thanks i'm a bit scared to upgrade though. I'm not sure which version to use for US X1a.
OK I have to ask this again. What's the deal with my X1 turning off if I slide the top open and close too quickly? Anyone else have this issue? The phone just straight up resets if I open and close the slider twice in a row while it is in standbye!
hmm, glad....
to see that i am not alone..
I have the exact same problem on my x1.... i am running the Xion 1.1 swedish rom on it so i will try to update to a newer version to see if there is a difference.
maybe it's just a screen energy saving? click power button will call the screen back
hmm
Nah that is not the problem, the damn device reboots itself completely when closing the lid... however mine works if i do it "with care"...
Updated the software in the phone last night and no difference...
Bah!
Solved... i changed the battery and after that everything works swell... bought a new cheap one.. So something was fishy with the original one... China Copys FTW!
So before the gingerbread update i was experiencing the nexus one touch screen issue. This issue would happen mostly when the phone would be charging or warm, and the y coordinate of the touch screen would be off by about an inch. (I would post a link to youtube but i can't yet... new member =/ ) So if you try to answer your phone while the defect was active, you couldnt, because touching the slider would be recognized as trying to touch the 'menu' key on the phone.
Anyway, after gingerbread got pushed to my device, i have yet to experience this issue!! i havent been able to find anyone reporting this resolution. i'm extremely please about this because it was becoming a deal breaker after i missed an important call because i couldnt answer my phone due to the issue!!
anyone else experiencing this resolution!?
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Hollow.Droid said:
In my experiences it does still occur, although seemingly less frequently. It is a hardware problem though so probably won't disappear regardless of the OS
Click to expand...
Click to collapse
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
this is where I was at before the push, i was seriously considering the incredible s, but for now it seems to have completely disappeared from my device...
I've also heard its a hardware issue (I do believe it to be true, not questioning that), so i found it extremely odd that its not happening now on my device.
Guess I'll just keep my mouth shut and enjoy
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
NexusDro said:
Observed no difference. The bug still appears every now and then. Doesn't bother me much because it usually occurs when the phone's charging. Not when I'm on the street using it. I heard that removing any kind of screen protectors can actually solve this problem.
Click to expand...
Click to collapse
*gasp* not my invisible shield!?
Memnoch30 said:
Yup. For some reason I have worse now than before. Maybe I'm just using it more now. Lately it's driving me nuts, to the point of actually looking at a replacement.
Click to expand...
Click to collapse
I had it terribly after the GB OTA, I wiped cache & dalvik and it all but went away. One occurrence in a week and a half, and I've been using the crap out of the phone.
Slightly off topic question: On stock Android, is wiping cache the same as wiping the dalvik cache? The stock recovery doesn't have the "wipe dalvik" option, only "wipe cache".
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Rusty! said:
No it's not, but if you have root you can wipe it manually by removing the contents /data/dalvik-cache/
Click to expand...
Click to collapse
Thanks. But every time you flash an official update, the cache gets wiped and rebuilt though, right? That's why after each update it takes a long time to boot.
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
I still have the prob but it's different with 2.3
Before 2.3, the touchscreen problem was unpredictable and could happen at almost anytime, whether charging or not. I replaced the handset but the problem persisted.
Since upgrading to GB, I've noticed a very clear pattern. If I'm charging my device and unplug it before it is fully charged, the touchscreen becomes extremely erratic to the point I must reboot the phone. If it's allowed to charge completely it's okay.
It never happens when it's is not charging.
Still annoying as hell but I've moved to Africa and having the device replaced is a real challenge. So I guess I'm stuck with until I replace it.
Still has issue
Stock, no modification at all. Today when I was rearranging icons in ADW Launcher, it seems that the screen registered click below where my finger actually was, same as the problem I saw previous to updating to 2.3.3. The phone was not hooked to a charger at the time.
Stock GRI40 here on my Nexus One...same issues that i've already had with Froyo. As it was posted before, it's a hardware issue; and the Nexus S is the new kid on Google's block, so i'm not expecting anything to improve our screens.
filippogiad said:
I still have the touchscreen issue. i think it will never be solved because it's an hardware issue, not a software one.
So the problem still appears, maybe a little less frequently.
Click to expand...
Click to collapse
Theoretically, there is a chance they could fix a software workaround for the hardware problem. If the error happens in only specific circumstances, and ALWAYS happens in those circumstances, then just teach the phone to know when those circumstances are happening, and tell it what to do in those cases. However, I doubt anyone at Google is working too hard on this problem. I agree, it seems to be much less frequent than it ever was. Seems likely that they may have added a little something to help us out.
brettbellaire said:
Seems likely that they may have added a little something to help us out.
Click to expand...
Click to collapse
Or more likely, it could be unintentional.
So even with official OTA it's still here?
Remember me of the ''crazy'' screen problem we had before while charging,perhaps it's a hardware problem after all
This is a main reason why tomorrow i'm getting a new galaxy s.
I tried a lot of custom and stock roms, I sent my phone to HTC and they replaced hardware, but this issue still persist. And it cause me a lot of problems, especially while driving...
I also still get that glitch but not as frequently. I noticed that i didn't need to reboot the phone to fix it. All i need to do is tap the power button to shutoff the screen and then re-tap to turn it back on and it'll show the lock screen. Slide to unlock and the screen is precise once again.
The bug is still there for me also. However, I didn't seem to have it as bad as some did originally, and now I've noticed that it's happening even less frequently.
So, I'm on my second a500, first one seemed "off", bad battery life, random shutdowns, etc.
now, I understand some issues are fixed with the 1.141.07 update. I desparately run the system update check like a teenage girl waiting for a boy to call. But no dice.
Is there any way to legitimately get the update?
Seems like people were being updated last week and then nothing...... (crickets chirping).
I'm still not very impressed with my second unit. screen on/off thing drives me crazy. I dont think the battery should be draining when in standby. etc.
I know that nobody here works for Acer, so dont flame me. But if I can;t get a reliable android tab, I think I may run back and get an Ipad2 instead. I have had an ipad 1 since release, and I guess i'm spoiled to only needing to charge the thing once a week, and I use it heavily.
I really want a android tab though - I'm a big google person and love having all my stuff in sync and connected. But I dont like having to live next to the power outlet, or wonder when my unit is going to randomly restart. I'm sure there are others in the same boat.
My first one runs great, just bought a second one at Costco with the fabulous deal they have. I have no battery run down issues. Auto brightness, Wifi, and gps all on....except when in for sleep mode. I turn on Airplane mode on and off through a downloaded toggle widget.
I've been using it periodically for 3 days and haven't turned it off. Even started a new book with Kindle. Still have 55% battery.
I'd say you are running a bad app which is the culprit. I bet if you go back to stock reset you won't have the issues, other than sleep without airplane mode.
...and no, we are all waiting for the update or 3.1, whichever comes first. I need it for Exchange, everything else is pretty minor.
I guess I should have mentioned. my first unit, I did a factory reset and ran stock for a couple of days, and still had the same issues.
This new unit is pretty much stock, and only thing I have installed is Flash, Kindle, and File manager HD.I have it running in airplane mode, wifi set to turn off when the screen is off, and screen brightness at about 10%.
I charged it all night, I have used it maybe 3 times today (since 6am), just to browse a couple of sites, and @2:30 today the battery was already @ 40%. it has been in standby most of the day.
I find it hard to believe that 2 different units could perform so poorly.
I really want to love this product, but haivng a hard time doing so, lol
The thing you described should be fixed with the 3.1 update...be patient.
Sent from my HTC Desire using XDA App
BadGrim said:
So, I'm on my second a500, first one seemed "off", bad battery life, random shutdowns, etc.
now, I understand some issues are fixed with the 1.141.07 update. I desparately run the system update check like a teenage girl waiting for a boy to call. But no dice.
Is there any way to legitimately get the update?
Seems like people were being updated last week and then nothing...... (crickets chirping).
I'm still not very impressed with my second unit. screen on/off thing drives me crazy. I dont think the battery should be draining when in standby. etc.
I know that nobody here works for Acer, so dont flame me. But if I can;t get a reliable android tab, I think I may run back and get an Ipad2 instead. I have had an ipad 1 since release, and I guess i'm spoiled to only needing to charge the thing once a week, and I use it heavily.
I really want a android tab though - I'm a big google person and love having all my stuff in sync and connected. But I dont like having to live next to the power outlet, or wonder when my unit is going to randomly restart. I'm sure there are others in the same boat.
Click to expand...
Click to collapse
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
bonzer2u said:
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
Click to expand...
Click to collapse
I too am waiting for the .141.07 update. Seems I read that Acer had pulled the updates. Still check every day. I like my tablet and have not seen battery issues with very little standby drain.
The only issue I have is that the WiFi keeps disconnecting. I have checked the advanced settings and it is set at always connected and I have tried changing the channel on my router (suggested elsewhere) but once or twice an hour I have to bump the WiFi to get it to work.
bonzer2u said:
Make sure you register the device via the Acer registration widget in apps. This will get your s/n in the OTA database.....
Click to expand...
Click to collapse
yup, did that on both units.
so, I made it 12 hours today on a single charge. I only used it 3 times to browse the web for about 5 min (no flash), and I wrote an email and sent it.
Sorry, but that is ridiculous.
http://youtu.be/hE0NfL1C0-s
BadGrim said:
yup, did that on both units.
so, I made it 12 hours today on a single charge. I only used it 3 times to browse the web for about 5 min (no flash), and I wrote an email and sent it.
Sorry, but that is ridiculous.
no need to apologize, that plain suks......
call the support line, perhaps they can push it to your s/n....???
Click to expand...
Click to collapse
Mine has been fine, except for the GPS.
I have a build 1.112.01_EMEA_CUS7. A new tablet and it's registered from today so they probably update them by batches because there are no new updates.
EDIT: But it works brilliantly apart from the crashes when I've installed any app. I've fixed that but it would be nice to be bug free.
bpivk said:
I have a build 1.112.01_EMEA_CUS7. A new tablet and it's registered from today so they probably update them by batches because there are no new updates.
EDIT: But it works brilliantly apart from the crashes when I've installed any app. I've fixed that but it would be nice to be bug free.
Click to expand...
Click to collapse
You are lucky. There is a update from Acer here for your build. It will take you directly to 1.141.01.
You need to unzip it using this post and then move the extracted update.zip from the decoded.zip file to your external sdcard and then do the update key sequence (volume down and power pressed) and you're done
Thanks. I'm updating as I type this.
I just hope that it will update properly and that I won't have any problems with rooting and or bricking my device or any problems that I've already solved.
I come from Desire so I'm used to wiping my phone first so just updating is a new for me. I would also feel better if our bootloader would be unlocked.
EDIT: Updated OK. Root pending.
EDIT2: Rooted and disabled phone.apk
The phone now works perfectly and is updated.
bpivk said:
Thanks. I'm updating as I type this.
I just hope that it will update properly and that I won't have any problems with rooting and or bricking my device or any problems that I've already solved.
I come from Desire so I'm used to wiping my phone first so just updating is a new for me. I would also feel better if our bootloader would be unlocked.
Click to expand...
Click to collapse
This is an official update so it will either update or not if the checksums are wrong or it cannot binary patch a file. So no chance of a brick.
It works OK. The only thing I've noticed is the longer boot time.
The android screen takes a minute longer probably because it's building files.
I'll check logcat when I have the time and patience to mess with it some more.
I didn't know that the update would just fail. I was expecting a brick because I was reading some posts about people bricking their tablets. I guess I was wrong.
Feedback from Acer Support re Updates, Etc.
According to Acer tech support, there is no way to force the new firmware update or Honeycomb update to the Tab. You just have to be patient and wait for the Tab to update itself.
As we know, lots of people are complaining about the screen turning on/off/on/off by itself, resulting in battery drain. These complaints are well-publicized and easily found using search engines.
I first purchased a 16gb Iconia Tab. I called tech support about the flashing screen and reported it as an issue. After speaking with customer support, they emailed me a survey asking about my user experience with the Tab. I completed that survey and again noted the problem with the flashing screen and battery drain.
The new firmware update that was pushed to the device solved the flashing screen issue and improved battery life.
Then I bought a 32 gb Tab and experienced the same flashing screen/battery drain issue. I called tech support (to see if I could obtain the firmware update for the new Tab). Amazingly, tech support told me that they had never heard of this issue. I told them to search their knowledge base but they insisted this was the first time they heard about a problem with the screen.
I know that cannot be true because I called them twice about this very issue, and gave them feedback in their on-line survey.
Anyway, I expect that the screen problem will be resolved when the firmware update gets pushed to the device. Unfortunately, on my first 16gb TAB I got the firmware update the day after I opened the box. I'm still waiting for that update on the 32gb Tab after 10 days.
mandel4026 said:
As we know, lots of people are complaining about the screen turning on/off/on/off by itself, resulting in battery drain. These complaints are well-publicized and easily found using search engines.
Click to expand...
Click to collapse
I had this issue. It's because of the wifi. My screen would turn on and off randomly and it was because my wifi was on my place where it had bad reception. I turned it off and the screen didn't light up anymore.
I didn't test if it also occurs on the new firmware.
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'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.