Anyone else getting random reboots/freezes on their A52s?
For me, this is what usually happens: The phone freezes for 2-3 seconds (usually without me doing anything demanding like gaming or using the camera), and then it usually does a full reboot (which goes to the bootloader screen that tells me that my bootloader is unlocked), or a soft reboot (that is just the Android boot screen). After it finishes booting, it's very likely that the same thing will happen again within 1-2 minutes. Afterwards, the phone is fine for 1-2 days until it does the reboot thing again.
Very rarely the phone just freezes without rebooting, and I have to turn it off by holding down all the buttons for a few seconds. I've also seen my phone reboot by itself while it was idle on my desk.
It's a very annoying issue that has caused me to lose a picture I had just taken. It could also cause me to lose an important phone call (since I have to enter my PIN after each reboot).
Anyone else having the same issue? I've found a few posts on Reddit mentioning this, but no one has found a solution, and I haven't seen anyone talk about it here.
I've never had this issue ever even with the various rom and firmware installations. Did this happen out of the box, after installing something, or just start up out of the blue one day?
Never, but my bootloader isn't unlocked.
I have had this phone since it came out and it has never rebooted on its own or frozen up on me, not even once.
Yes I have it too and I didn't find out why, even with logcats. It's happened to my friend too but sometimes it stops for a while and then a month later it starts again.
Same problem with my A52s.
I think it happens more often when it is warm.
It's almost like a power brown out.
On one of the reboots, there was a "microsd read error" (or something along those lines) so I removed the microsd. So far it has been working great. The microsd is a Samsung 512GB Evo plus (2021) I baught with the phone from samsung store.
I am so far testing the microsd and it seems it is faulty (extremely slow rear/write speeds after it is filled toa certain capacity)
Only time will tell if this is the problem.
Unfortunately the problem persists even after a factory reset.
However, I have found a way to consistently reproduce this issue by using Google's stressapptest which is basically a CPU + Memory stress test which tests for system stability.
I'm curious to see if this is the case for other people as well (whether or not you're experiencing this issue). If you'd like to try it (at your own risk, I'm not responsible if anything happens to your phone!), I have attached a build of stressapptest I compiled for arm64 devices.
Download, unzip it, and then execute the following:
Code:
adb push stressapptest /data/local/tmp
adb shell chmod +x /data/local/tmp/stressapptest
adb shell /data/local/tmp/stressapptest -M 4000 -W -s 3600
Note: If you have the 6GB RAM variant, then you may want to replace 4000 with 3000 in order to prevent Android's Low Memory Killer Daemon from killing stressapptest.
If you get an error similar to this, then your device (probably) has this issue:
Code:
2022/11/30-16:19:30(EET) Report Error: miscompare : DIMM Unknown : 1 : 27s
2022/11/30-16:19:30(EET) Hardware Error: miscompare on CPU 4(0xFF) at 0x740bd4d840(0x841:DIMM Unknown): read:0x0000000000008000, reread:0x0000000000008000 expected:0x0000000000000000
If your device restarts while stressapptest is running, then it almost certainly has this issue.
wwwsam said:
Same problem with my A52s.
I think it happens more often when it is warm.
It's almost like a power brown out.
On one of the reboots, there was a "microsd read error" (or something along those lines) so I removed the microsd. So far it has been working great. The microsd is a Samsung 512GB Evo plus (2021) I baught with the phone from samsung store.
I am so far testing the microsd and it seems it is faulty (extremely slow rear/write speeds after it is filled toa certain capacity)
Only time will tell if this is the problem.
Click to expand...
Click to collapse
Do a low level format of the card then format in the phone. (if that fails it's likely defective) If new simply first format in phone before using.
After which leave it in that device; never "share" it with other devices without formatting it first. It may work or you may end up with a corrupted card. Interface through phone to the PC rather than pulling the card and using a reader. The less you handle it, the better.
A card that has given you problems (if used as described here) is likely to screw up again in the future... be warned. Always use at least a V30 rated name brand card and buy from a trusted source only. Sandisk Extreme's interface and run well. I have both the .5 and 1tb variants. Zero issues with them on my N10+'s.
Related
So since all the other threads revolving around this issue seem to be nothing more than suggestions of things to try rather than trying to determine what the problem is, I wanted to start fresh.
Here's my issue regarding reboots on my Evo (Hw 003). Simply put the phone will reboot (typically under moderate/heavy use, I've not once seen it reboot on it's own, although I can't say it hasn't when I've been asleep).
This issue has persisted regardless of HBoot Version (I've been on 0.76 ENG, 0.97, and 2.10), PRI, Radios or ROM. Trust me, I've tried nearly every combination. It even persists when fully unrooted and returned to stock.
I've obviously tried every type of wipe (both through CW and Amon's Recovery and using Calkulin's WipeAll method in both recoveries) prior to flashing roms and after restart/crashes. I've tried eliminating SD Card issues, and these issues persist regardless of whether the SD card is in or out, or whether it's corrupted or not.
Here's the only things I can definitely say regarding the reboot issue (which I do have to believe is a HW issue, although it may have something to do with the early boot sequence...see my reasoning below).
When the crash occurs, the phone ALWAYS attempts to reboot itself. Very rarely it will do this successfully (but it seems to only be successful in doing so when on customs ROMs, specifically CM7 nightlies, which makes me think that those crash/reboots are unrelated and are actually just software issues with the rom/apps in question and should therefore be disregarded).
If my phone is currently set to S-OFF, the reboots always ends with under 5 seconds on the white HTC Evo screen, then display goes black and I get five vibrates and a flashing green power LED. When this happens and the phone is connected to my laptop via USB, right after the 5 buzzes, I get a Hardware Growl notification that a Qualcomm USB device has been connected.
If the phone is currently set to S-ON, the reboots result in a bootloop that again, shows the white HTC Evo screen for less than 5 seconds, then the screen goes black, phone restarts and starts the loop again. In these cases I don't get the Qualcomm/HW Growl message.
With S-OFF the only surefire way to get a working phone back is to remove the battery for a few minutes (seems like it needs at least 3-4 minutes, which makes me think some form of volatile chip/ram needs to drain to a certain point before working again). I can always get HBOOT/FASTBOOT though, even if I just remove the battery for a second. It feels like I can get into Recovery with the battery removed for less time than it takes to actually boot into the OS, although this may be an inaccurate observation on my behalf.
With S-ON, while removing the battery seems to yield the same results as when the phone is S-OFF, occasionally if I let the bootloop play out, it will eventually hang on the white HTC Evo screen for some time, then restart and boot like normal.
---------Conclusions----------
From what I can tell this whole reboot/crash issue people seems to be having (when it isn't caused by bad flashing or improper use of the phone) can be narrowed down to two areas.
1 - There is an issue with the phone's RAM. This would make sense since there is a difference in the results of removing the battery for a short time or long time when trying to recover from a crash.
2 - It's an issue with the phone's early boot sequence. Perhaps the phone's internal memory (specifically the boot partition or wherever HBOOT/FASTBOOT is stored, not 100% sure where that actually is) has bad sectors or is otherwise corrupt.
I'm leaning towards the RAM being the culprit though, since it seems to be the only thing linking all of the different crash/reboot scenarios. And although I've heard rumblings that it may be a CPU issue, I really doubt this since I can always get into HBOOT/FASTBOOT and because when it crashes and give the 5 buzzes (which some have speculated is a Qualcomm error code for CPU's) it then seems to be communicating on some level through the CPU and USB with my laptop.
While I obviously can't replace the phone's RAM to check this, I just wanted to see what the opinion of those who are a bit more familiar with the phones inner workings than I am have to say about this.
stefpap I have been experiencing the same systems that you describe here. I am currently on the Synergy rom, but I have also experienced this while on myn 2.2 . I have tried multiple reboots/resets and clearing of the sd card except for the rom itself. I want to say that the reboots happen while the GPS is running in maps and navigation. They also seem to happen while watching 15-20 min into a movie.
Have you made any headway on the issue? I also tend to believe that the memory is running away. I have found that the battery becomes a little warm when i remove it for the reset ( I dont know if it has anything to do with this issue)
One last thing, I cant remember this happening when I first received the phone. it also wasnt rooted and had different versions of apps, but who knows.... please let me know if you have found anything about this issue.
Well as an update I uprooted my phone and took it into a repair center, they saw what it was doing (see above) and ordered me a referb. Turns out the main board was causing reboot after getting to hot.
Sent from my PC36100 using XDA Premium App
Hi all
I'm running DeFroST 6.1a, stock DF kernel, and radio 5.11.05.14. Please bear with me because this might be a little long, as I try to explain everything I have done which landed me into a somewhat sticky situation.
A few weeks ago, I flashed the JAMT theme by ClassicalGas, and what I noted was the sudden loss of LED notification (and I don't seem to be the only one, actually). So I poke around, search the forum, and one user said he had gotten the LED notifications to work again by extracting the theme files from the JAMT framework-res.apk into the DF's framework-res and flashing the whole DF again.
I decided to try my hand at it, did a NAND, wiped, then flashed the "modified" DF - which caused my phone to be stuck in a bootloop. No biggie, just have to restore my NAND. I wipe, then when I'm about to restore my NAND, I get hit with
Code:
Error : run 'nandroid-mobile.sh' via adb!
Which, after some googling, could mean a couple of things, like the checksum is wrong, or battery is low, etc. But before I do anything, I hit the wrong button in recovery, then my ROM boots up (wiped). The first thing I realize during the starting phone set up application is that about half of my screen is not responding, but once I get out of the initial set-up, all functionality returns
I power down, charge my phone a good bit, _wiped_, then I did a NAND restore , without any problems this time, restoring my original problem free-state, and everything seemed fine
A couple of days later, on vacation, I was playing a Tower Defence game on my phone, and the whole thing froze on me. I popped out the battery. This is real strange because that game had always worked fine before.
I then try a bit of Zenonia. At certain points, my phone freezes up. Characters on screen, monsters, etc are all still moving around mind you. All EXCEPT me. There seems to be no response from touch whatsoever. I get a little frustrated and press the "home" button as well as the "power" button.
After some waiting, my phone screen goes off. I find out that it has went back to the lock screen, and when I unlock, its back to the home screen, with Zenonia still running in the background.
I inferred that my phone's response has been super delayed for some reason. It happens for over a week, sometimes, seemingly to resolve itself after a good wait, and sometimes never (which requires me to pop out the battery). Sometimes, it "hangs" so badly that my phone itself began force restart. Also, out of all the times it restarted, there was _once_ it was stuck in the bootanimation.
And I also have noticed, if my phone has been on the whole day, at night, my SMS app (stock) seems to move very slowly - in terms of when I type out my reply, the phone seems to lag behind and cannot keep up with my usual typing speed. Even pressing the "reply area" requires me to wait for some time until the keyboard pops out (not stock, but never had problems with it before).
Sometimes, unlocking the phone when I last left it as the SMS screen would also cause some lag when I unlock. Reboots from the power menu seems to clear it up (until the next time it happens again).
Last night I tried some Kongregate Arcade, which needed flash. At some point of playing, whenever I was about to receive an SMS, the phone seem to _not_ response to my touch once again, while baddies on the flash game still continued to move around and hit me.
At first I thought it might have been a problem with SetCPU's governor (does interactive cause problems? Regardless, SetCPU was not a problem before the NAND). No matter, I changed the governor of my screen off AND my "normal" profile, but still no dice.
Also, could it be a memory issue? I doubt it, I hadn't installed anything else before and after the NAND, and I manually clear any unwanted running processes (and I have been, since I've gotten the phone).
So, dear XDA, what exactly is wrong with my phone? I hope its not hardware, and I'm hoping that flashing a new ROM might help, but I haven't done so until I have heard some opinions :/
P/S: Probably at wit's end here...
Edit: I'm not sure if its related, but once when I pressed the home button when all forms of input didn't work (buttons, touch screen) when I was playing Zenonia, Launcher Pro was "about" to FC, giving me the option to kill it or to wait.
le bump with a summarized, easy on the eyes version.
1 )Bad attempt at theming DF 6.1a leads to bootloop.
2 )Wiped in preparation to restore nandroid, but accidentally boot up the device instead (boots to a "wiped" Defrost without all the bells and whistles). Top half of screen during the google account setup, wifi setup, time zone set up not responding. Problem goes away after exiting set up.
3 ) Wipe again in recovery, tried to restore NAND once more, but "Error : run 'nandroid-mobile.sh' via adb!"
4 ) Power down, charge phone, successfully restored NAND.
5 ) Phone is fine until I play games (which worked fine before). Some games totally freeze up the phone, while others are still running (monsters moving on screen and attack my unmoving character), but all forms of input is not recognized (button pressing, touch screen pressing, etc).
6) These "half-freezes" (inputs do not work, but the game still is running) also occur when playing flash games, right around the time I'm about to receive an SMS.
6 ) Whatever commands I pressed while the phone was "frozen" registers when the phone "unfreezes".
7 ) Sometimes freezes cause the phone to reboot, sometimes have to pull out the battery.
8 ) If phone has been on the whole day (regardless of heavy or light usage), stock SMS app seems to slow down and become unresponsive around late evening. A reboot fixes this.
9 ) Once, launcher pro was not responding, and I was given the choice to wait or kill it, when the phone recovered from a "half-freeze" (unrelated?)
Not a setcpu problem, because I have been using the same profiles since I got the phone, but I did play around with the governors to see if that changed anything.
Not a memory issue, because I dont install much, and I regularly manually kill unwanted processes.
Not sure why your phone acts like this and don't know a simple solution. But before tracking down the error, it's mostly and surely faster to install another ROM or just reflash this ROM and only install the apps you want to try - saves you some headaches... Also try to repartition/reformat your sdcard. I too had some issues with lagging system but i was only able to resolve it by flashing another ROM. I don't think it's an hardware related issue though...
Thanks for the response
Just flashed a new ROM. Gonna poke around and see what happens. Will report back.
Whats the best way to repartition an SD? Instead of Gparted of course. I'm not on Linux (my ubuntu installation went bad).
There are definitely thread about this, but before I flashed DF 6.1a (coming from DF 6.0e), I switched my recovery to AmonRa, selected ext2 partition of 0mb (because I had a 256 partition before, and then I wanted a 512mb) and then partitioned it again with a 512mb.
Honestly, it doesn't sound like the best way to do it, but that was what some threads said.
EDIT: Phone seems fine now on GV 1.1 How could a nandroid affect the phone so badly? hrm.
Partitioning with AmonRa's recovery works perfectly fine for me. You just have to set the ext2 partition to the desired size (i use 1024 as recommended on other threads - at least for sense roms). Afterwards upgrade ext2 to etx3 and maybe ext3 to ext4 (i have done this).
I too had to throw away some nandroid backups and start clean. Don't know why. I thought it has something to do with my "experience"...
Hello,
I'm running CM7 with S2E and every once in a while when I look at the phone it presents me with the PIN code screen, sometimes it spontaniously reboots, sometimes it just hangs and needs a battery pull to come back to life.
I've been having this problem for weeks now, have been trying to narrow down the list of suspects and I can't seem to shake the feeling it has something to do with the SD card. I have 2 cards, a 8GB one and a 2GB one and the problem appears to occur much more frequently on the 8GB card. (I've ordered a third on eBay just now to be able to test this further)
Also, this one time I succeeded in logging on with adb when the phone was acting up again and the shell seemed fine except it hung as soon as I did
Code:
cd /mnt/sdcard
ls
It doesn't appear to matter which CM version (or nightly) I run, or which radio is installed, problem always remains.
Getting ready to start to physically hurt the phone out of frustration
Has anyone ever had a similar problem?
Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )
Hi all,
I bought the phone in the subject almost 3/4 months ago and I always had issues with the sd card I bought (sandisk Ultra 128GB) as, at the beginning when the phone was using Oreo 8.1 the card was constantly resulting as not connected (External card stopped working) however thi swas working despite the error.
I have previously noticed that the phone was rebooting itself every now and then but I never paid to much attention to it.
Since I updated to Android Pie, however, this issue started becoming more persistent. In a day the phone can reboot itself multiple times (sometimes even 5/6 times in a short period) and, although the card is not failing anymore prompting the error message preaviously mentioned, this still keeps giving problems as, right after reboot the card is not recognised and a different message is prompted saying that the card has not been inserted in the device.
The error disappears only after I unlock the phone as this is recognised and the apps are loaded.
Reading through the internet I noticed that many people face the same problem or similar and no fix as been provided as of yet.
I tried everything I could: Factory reset, flashing the stock rom from scratch (following the forum's thread), using the phone in Safe Mode (in this case the card wasn't loaded by the system so no reboot happened or at least not fort the time has been in safe mode) and updating to the latest version of Pie but nothing.
I also ran an hardware test to see if the issue was due to a bad hardware component and I still have a monitoring app in case the issue happens again (as it is really random. sometimes it can pass an entire day before the issue arises again).
Has anyone had a similar issue and found a fix/workaround?
I really love the product and I think this is something that can happen as, by my point of view, this is something caused by the software or the stock rom itself, however I would like this to be resolved as, at the moment, this is really frustrating, plus being a long time issue I think it might cause serious problems to the phone's hardware.
Please let me know.
Best regards to all of you,
Davide
Is your sandisk fake?
You can checked wit app call "sd insight" , but the app only works on old OS (latest i try jelly bean 4.1)
But even your sandisk fake, the only common thing happened is the sd card ejected or android remounting over and over thats all , not until reboot randomly (based on my experience using fake ext sd card)
Maybe you can try with another sd card you have or your friends have, if the symptom happened again , I dont want to judge but maybe its hardware problem? But dont know for sure just my 2 cents bro...
manna.davide87 said:
Hi all,
I bought the phone in the subject almost 3/4 months ago and I always had issues with the sd card I bought (sandisk Ultra 128GB) as, at the beginning when the phone was using Oreo 8.1 the card was constantly resulting as not connected (External card stopped working) however thi swas working despite the error.
I have previously noticed that the phone was rebooting itself every now and then but I never paid to much attention to it.
Since I updated to Android Pie, however, this issue started becoming more persistent. In a day the phone can reboot itself multiple times (sometimes even 5/6 times in a short period) and, although the card is not failing anymore prompting the error message preaviously mentioned, this still keeps giving problems as, right after reboot the card is not recognised and a different message is prompted saying that the card has not been inserted in the device.
The error disappears only after I unlock the phone as this is recognised and the apps are loaded.
Reading through the internet I noticed that many people face the same problem or similar and no fix as been provided as of yet.
I tried everything I could: Factory reset, flashing the stock rom from scratch (following the forum's thread), using the phone in Safe Mode (in this case the card wasn't loaded by the system so no reboot happened or at least not fort the time has been in safe mode) and updating to the latest version of Pie but nothing.
I also ran an hardware test to see if the issue was due to a bad hardware component and I still have a monitoring app in case the issue happens again (as it is really random. sometimes it can pass an entire day before the issue arises again).
Has anyone had a similar issue and found a fix/workaround?
I really love the product and I think this is something that can happen as, by my point of view, this is something caused by the software or the stock rom itself, however I would like this to be resolved as, at the moment, this is really frustrating, plus being a long time issue I think it might cause serious problems to the phone's hardware.
Please let me know.
Best regards to all of you,
Davide
Click to expand...
Click to collapse
How did you format your card? Did you use internal or external option? Saw few posts with same issues and strange enough all with Sandisk cards.