My sister has a Nexus S 4g that she purchased used from Cowboom. Within the past 2 days the phone has started to freeze up when she attempts to turn it on with a dimmed screen. She ends up having to pull the battery to get it to reboot. She also woke up to a dead battery today after having the battery at 90% last night (I am assuming this is caused by the same issue).
Any ideas as to what might be going on, or any recommendations to try to fix it? She is on the last day of the cowboom 30 day return policy, so she is trying to figure out what to do.
maybe she has some problem with cpu clock or voltage at wakelock.
SuuK80 said:
maybe she has some problem with cpu clock or voltage at wakelock.
Click to expand...
Click to collapse
What's the best way to diagnose that?
happened to me with cyanogen 7.1 and default clock and voltage.
try to install antutu cpu master and cpu voltage and make some try.
or change kernel for example air kernel or matr1x
SuuK80 said:
happened to me with cyanogen 7.1 and default clock and voltage.
try to install antutu cpu master and cpu voltage and make some try.
or change kernel for example air kernel or matr1x
Click to expand...
Click to collapse
I would really rather not flash it with a different kernel, or change the cpu settings. The device is stock, and as I am not the one with the device, I would rather leave it that way. Is this a bug with stock ICS or something? Or does it sound like it is caused by the phone?
is difficult that can be a ICS bug.
if you are not sure and you don't wont do some attempt to fix it, send it back...
xur17 said:
My sister has a Nexus S 4g that she purchased used from Cowboom. Within the past 2 days the phone has started to freeze up when she attempts to turn it on with a dimmed screen. She ends up having to pull the battery to get it to reboot. She also woke up to a dead battery today after having the battery at 90% last night (I am assuming this is caused by the same issue).
Any ideas as to what might be going on, or any recommendations to try to fix it? She is on the last day of the cowboom 30 day return policy, so she is trying to figure out what to do.
Click to expand...
Click to collapse
It does happens to me too, its the kernel related problem... Solution is you flash a custom kernel....
Sent from my Nexus S using Tapatalk 2
SuuK80 said:
is difficult that can be a ICS bug.
if you are not sure and you don't wont do some attempt to fix it, send it back...
Click to expand...
Click to collapse
My sister just did an online chat with them, and they are sending her a different device. Unfortunately she has to send her device back first though, so she will be without a phone for a few days.
Since she only has a week to return it, it would be hard to verify that whatever I do actually fixed the phone in that time.
Related
Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?
Oh btw, I have the Samsung Vibrant
Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).
No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max
Are you guys using SetCPU for OC'ing, or for scheduling?
I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).
ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.
I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App
hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?
Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App
xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype
I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile
I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
If I remember correctly, there were a lot of people having this issue with SFR and you shoudl check that thread for more info. However, long story short, this can definitely be related to underclocking and/or undervolting.
Are you using SetCPU to underclock? If so, set your minimum speed to 200 MhZ as I think that resolved it for most people.
ok, set to 200mhz (was at 100mhz) will see if that fixes it. thanks.
I'm having the same issue since flashing Emotionless Beast. Used Voltage Control to set to 200. Is there a way to keep the settings through a reboot?
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
thetoady said:
I'm running the twilight zone v1.1.1 kernel and recently my phone has gone to a "death sleep" repeatedly when not plugged in. (when plugged in via usb on computer or wall wart its fine). I end up having to remove the battery and putting it back in to get it to work again (till the next time it falls asleep).
Is this possibly a kernel issue? a kernel controlling voltage issue? (under volting on battery?). A hardware issue? I've been running this kernel for a while now and its only started happening in the past few days.
I figure I'll try out stock soon to see if its a problem (and if it is, as I pay for TEP, I'll just take it into a store), but wanted to check here first
thanks.
Click to expand...
Click to collapse
Same thing happen to me a few time on twilight but since I'm been on genocide 2.0 kernel no problem for me genocide is the best for my phone
Try it out with jornaling on
Sent from my SPH-D700 using xda premium
I know this might sound stupid, but I had a problem similar to this the other day. It was only the screen was blank, but would still accept inputs on it. I could unlock the phone (using the TW lockscreen) and then, I was able to hold the power key and select reboot (on-screen location pressed from memory).
Is it just the screen, or the entire phone?
thetoady said:
ok, setting to 200mhz didn't seem to fix my issue, will probably try another kernel.
Click to expand...
Click to collapse
Hmm... Is it also undervolted? Might try changing that. FYI, I have also been using Genocide with no problems for a while now...
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
thetoady said:
Pretty sure its the entire phone. tried dialing it from my desk phone and it didnt ring.
also, the epic's version of ctrl-alt-del doesn't seem to work either (just happened again). will be trying genocide when I get home.
Click to expand...
Click to collapse
Try genocide 2.0 kernel & when you use titanium backup don't re install the app &data just install the apps hit the thank you button if I helped you in anyway!
Sent from my SPH-D700 using xda premium
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Until you figure out what works for your phone avoid all voltage changes and set minimum frequency to 200 Mhz and to set on boot. There are not enough advantages to over and undervolting to not have a working phone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's good advice. Didn't UV and OV cause some bricks once? My phone does that death sleep thing when I was at 100 Mhz on Genocide. Set it to 200 and no more problems.
uSo things were a bit more involved.
My phone died totally (major FC avalanch on startup), so I reimaged it, installed genocide and restored from backup (over an hour! w/ data) and its behaving well now.
though I do hate the spam genocide puts in the boot image.
Yesterday I got the ICS update via Kies.
Saw that my CPU was not going into deep sleep.
BetterBatteryStats showed the problem
fuel_alerted is forcing a kernel wakelock.
I tried searching the forums, and there are some fixes in some custom kernels.
However, I could not find out what exactly is fuel_alerted, why does this happen, and does it happen on all phones?
I believe taking out battery and putting it back in should fix the problem. Right?
Will it come again?
Whats the root cause of this problem?
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
i dont have this issue. i flash DDLP8 india yesterday.
tsk1979 said:
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
Click to expand...
Click to collapse
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
weng_cas said:
i dont have this issue. i flash DDLP8 india yesterday.
Click to expand...
Click to collapse
All ICS roms have this issue. You just have not hit it. Its a bug in the kernel. Somebody has fixed it in an open source code. I googled quite a bit, and also found the offending function
https://github.com/CyanogenMod/samsung-kernel-c1/commit/5f6d8422629002c530dcf30891c241fe3ee2e0ab
katyarevishal said:
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
Click to expand...
Click to collapse
Will do
Here is what the bug report says
"However, when the SOC starts rising, the wakelock was only destroyed"
Now what is SOC referring to? System on Chip? Does not make any sense. Can somebody look at the github page?
Try disabling the power saving mode and restarting.
Don't use power saving mode. I've only seen this Wakelock after I've checked the powersaving option.
Ironic. But true.
Sent from my GT-N7000 using XDA Premium HD app
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months.
I fixed this in I777 Gingerbread kernels back in October, I9100 kernel developers pulled in the fix fairly quickly. Despite the bug being documented and fixed by the community for months, it is still present in all of Samsung's ICS kernels.
It has been fixed in the CM9 kernel since the day I9100 Update4 sources were released.
It's also fixed in DAFUQ. (However a lot of other stuff is currently broken in DAFUQ.)
No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
I just noticed this param, I am not sure it was there before (I am on LPY)
Rebooting and it's still there!
Doing Power off now..
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
No - FM is a userspace issue, as is MHL.
For CM9, the only things the source release affects are:
1) Speakerphone (already fixed)
2) Possibly a more reliable wifi driver (although CM9 may just kangbang pawitp's great work on the Aries kernels)
3) Backporting some performance features such as improved busfreq control
Entropy512 said:
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months...
...No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Click to expand...
Click to collapse
Found this thread after seeing this causing wakelocks in my i9100 S2. Thanks for the explanation.
However, rebooting - as well as powering off and switching on again still did not eradicate the fuel_alert problem and CPU Spy was showing my phone couldn't enter deep sleep.
Only after pulling out battery (and waiting for 1 minute for good measure) and powering up again did the bug go. CPU spy then reported my phone had entered deep sleep and the fuel_alerted entry was no longer showing in BetterBatteryStats.
Remove the battery and wait for 1 minute and reboot the phone , it will fix the problem.
To avoid it from happening again , remember to wake and unlock the phone every time before removing the phone from charging(Data cable & charger both).
I never unlock the phone before plugging and unplugging, and inspite of that problem is not reappearing.
So it may be completely random. I looked at the github code, but somehow could not figure out any relation to lock/unlock while charging.
It happened to me once and i removed the battery for 15 mins and it disappeared. But today it happened again. I do have power saving mode enabled but i dont want to again and again remove the battery to fix it. I charge my phone by turning it off and once its charged i remove the charger, let the display go off and then only turn on the phone. Do i need to turn on the phone before i remove the charger?
I think the power save mode has something to do with it. I didn't check the battery history before turning it on though but after a few days the Note didn't last 12 hours with only 1 hour of usage. The processor was awake even when the screen was off.
As suggested here I removed the battery for a few mins. I reinstalled the battery and charged it while the phone was still off. After a few hours of charging I turned the phone on and date/time defaulted to base time as expected. I observed battery behavior for a few days and the processor is now sleeping when the display is off and only wakes up every once in a while maybe to sync. BTW I only have Gmail sync on everything else is set to manual. And I haven't touched the power save option since
I've been having a recurring problem where my phone will lock up in a deep sleep, leaving the phone completely off. In order to restart the phone, I have to hold Power and Vol Down which takes me to a charging logo, and then hit power again. This generally happens overnight when the phone is charging, but I've also had it happen once while making a VoIP call. I thought I resolved the issue by wiping the phone and flashing the stock 4.2 ROM. However, the issue just occurred last night after 4 days of bug-free usage.
My question is whether this is some sort of weird software bug or a hardware issue. I haven't seen others report identical behavior but I've seen lots of complaints about freezing and random reboots that seem to be due to software. Should I request an RMA?
+ 1 . I am having the same issue. I would say hang tight. Call the support team and let them know you are having issues. If atfer a few weeks the problem persists perhaps go through an rma. I suspect it is software related. Lets say you did RMA still had the issue then had a dead pixel or other problem? It would suck and you would have to go through the whole process again. rinse and repeat. Only if you want to return the device for a full refund, then I would say hurry up and make that call. My .02 Good luck.
NexUsandThem said:
+ 1 . I am having the same issue.
Click to expand...
Click to collapse
+1
Having the same issue. Although no clear pattern is visible. Sometimes I find the phone dead-locked after putting it aside for 10 minutes and sometimes it seems to run for a day or even two without issue. Running _motley kernel right now without any change on this front.
I rather think it's a software issue than hardware. So I am not going to RMA it.
Strangely when I power off the phone on such a lock-up and then reboot it I will see a substantial drop in battery after the reboot. So the phone seems to be in some state where it still drawns more battery than in normal operation. E.g. with _motley kernel and limited clocks I typically see 3-5% battery drop over night only. When it locks up during the night and I reset it in the morning then battery usually drops much more (e.g. 30-50% is gone). Maybe it's caused by some hanging/deadlocked driver.
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
shotta35 said:
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
Click to expand...
Click to collapse
In fact I got the device in dec 2012. Started to set it up and then decided to root it (including full factory reset). I only have a very minor amount of system-level applications installed. Actually the main reason to root was to use Voltage Control as I intended to limit clock rates and (if possible) voltages the same way I was used to do it on my Galaxy Tab 7 (P1000) where I was very pleased with 6-days battery lifetime.
Initially I found the minimum clock rate was set to 1GHz and I have reduced it to 304MHz (minimum with stock kernel). When I discovered first freezes/lock-ups then I reverted to default settings and found it still locking up occasionally. Meanwhile I am using _motley kernel which seems to include some voltage mod as well. Although Voltage Control does not show options to modify voltages. Then I found Trickster MOD which shows some voltage control but it seems to have no effect (at least I was used my galaxy tab to crash when undervolting too much and it's pretty "strange" to be able to set all clock voltages to 0.6V while still running stable; so I guess the settings won't have any effect right now).
I have also tried to remove all modifications and applications and/or profiles which could cause the issue without any difference. Even when run stock settings it occasionally completely locks-up the device.
Edit: I was wrong regarding voltages. In fact I found my device happily works at 1134MHz using 600mV. Since I am used to limit max clock rates to 810MHz I could simply put all voltages to 600mV without seeing a crash/reboot.
CAUTION: This does not necessarily have to apply to all devices. My one is "faster" binned Rev. 11 device. Some voltages of different users are collected here: https://docs.google.com/spreadsheet/ccc?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc#gid=0
So I've had this issue for a while now, probably since spring where my phone will consistently die at around 15% Everytime instead of 1%, it will just skip from 15% to 1% then power off immediately. This happened today when I had battery saver auto enable at 25% and used it a bit more till it got around 15% and while in standby it just powered off and when I tried hitting it back on it actually did and showed 1%. During this time I made a phone call and opened hangouts for about 2 minutes and locked my phone again and about another minute later it randomly powered off again and would no longer get past the boot animation without shutting off. I don't believe this is a ROM issue since I've changed my ROM multiple times from stock to many custom ones (Marshmallow/Nougat) and the issue is present on all of them. I am currently on the latest PureNexus ROM with Franco kernel.
Only thing that would make sense is that my battery is degraded pretty badly and I just need a new battery installed. I bought my phone from Huawei and have no insurance plan so I don't know how much battery replacement would come out to be.
I've had the same issue since 7 hit. beyond frustrating.
i had that issue before too. i did a clean factory reset and the issue went away
Well I've done full wipes (system,cache,internal,everything) and have gone through multiple roms stock, purenexus, weta, etc and it's been present in each. It does feel like it started happening once i switched to Nougat but I couldn't remember exactly. Might try a marshmallow rom and see if it's any different since I haven't ran marshmallow since Android N came out for beta.
Installed 7.1.1 still happens.
https://imgur.com/a/I6vbZ
I've also had this happen multiple times. Not since I wiped to get the Google Assistant.
Hi, did you find out any solution?
I have this issue also but it happens randomly. It started when I installed Nougat.
I have that too, even after I've flashed a full system image of 7.1.1 DP (used the flash all script, so including everything). Very annoying...
same here. did marshmallow help at all? i'm about to go that route, lock boot loader, etc.
frodriguez96 said:
Well I've done full wipes (system,cache,internal,everything) and have gone through multiple roms stock, purenexus, weta, etc and it's been present in each. It does feel like it started happening once i switched to Nougat but I couldn't remember exactly. Might try a marshmallow rom and see if it's any different since I haven't ran marshmallow since Android N came out for beta.
Click to expand...
Click to collapse
Root if you didn't, then do a battery calibration
Hopefully this solves the issue
I have this issue too. Battery unpredictable drops to 0% at 10%-20% and phone switches off.
I've had this issue before. I did a couple of things so not so sure what fixed it. I installed ex kernel. And tried the different Cpu settings on the Interactive Governor. Ghostpepper is the one I'm currently on. No idea what fixed it. But my phone did that same thing twice before I swapped to a different kernel.
---------- Post added at 05:01 AM ---------- Previous post was at 04:52 AM ----------
I think its more or less your cpu not liking any of the settings. Maybe making it scale down to low to fast or not letting it scale up. I'm not so sure but I think thats what it is. I also doubt any battery calibration apps do much. If I remember right all they do is erase your battery history. If anything it might be bad to use those apps. To each his own tho. I guess you guys can try those apps.
This apparently happens if you have auto battery saver enabled. Disable it and you should've have the issue.
Fun fact: if you select whatever percentage in the auto-mode, it will die at that percentage.
I got the same issue but randomly after upgrade to 7.
Koragg618 said:
This apparently happens if you have auto battery saver enabled. Disable it and you should've have the issue.
Fun fact: if you select whatever percentage in the auto-mode, it will die at that percentage.
Click to expand...
Click to collapse
That makes sense. My was battery saver was set to 10% which is when my phone would shut down. What fixed it for me was dirty flashing the rom. But I bet it only fixed it because it turned off battery saver.
On the other hand, I guess it does a great job saving battery this way. Best battery saver ever.
Mine and my wife's are hardware related. RMA'd both of them. Her's is a 5X though and would turn back on after about 20-30 seconds by itself after it turned off. Factory reset and all that, still on MM. Spoke to Project Fi and guy had me update it to N, it did it again right after we got done doing setup and it was still in the 90s%
Jammol said:
Mine and my wife's are hardware related. RMA'd both of them. Her's is a 5X though and would turn back on after about 20-30 seconds by itself after it turned off. Factory reset and all that, still on MM. Spoke to Project Fi and guy had me update it to N, it did it again right after we got done doing setup and it was still in the 90s%
Click to expand...
Click to collapse
Sounds haunted! Happy Halloween
galaxys said:
Sounds haunted! Happy Halloween
Click to expand...
Click to collapse
Yeah I know right. What made me even more mad was when she told me, "oh that....that's been happening for the past 3 months!" :crying:
Update: Got the new replacement. They sent me a brand new one!!!