Related
Since I've had my Artemis occasionally after a soft reset the SD card appears as not installed. I would have to remove the battery and sim etc, replace the SD card into the holder and start-up the phone and it'd usually be ok. The only trouble is lately it seems to be doing this more frequently and it is becoming more difficult to get the phone to recognise the card upon start-up again. Anyone else experience this? Have an cure?
i've had the same problem on my magican. The solution i found was to remove the SD card and place it back. It seems to me that cardreader's contacts broken.
Its big but you must read first.
http://forum.xda-developers.com/showthread.php?t=285511&page=24
So the card is corrupt? Because when I stick it into my pc it reads it perfectly fine, no problems or slowness.
My phone has stopped recognising the card completely now, but when I started the phone in safe mode using iLauncher it recognised it surprisingly. I'm suspecting there may be a piece of software or a setting stopping the phone from recognising it. I'll have a read through that link some more tho just in case there is a solution.
If anyone else has another solution then it would be greatly appreciated.
Cheers
Update: I've tried another 2 known working SD cards and neither of which are recognised by my device to it looks as tho its an issue with the phone and not the card. Has anyone experienced this before?
I've the same problem. I use 2 SanDisk cards, 512Mb and 2Gb, both of them seem to disappear as I boot the device. It hapens 50% of times and begins when I installed the HTC ArtemisSDEnhancement program.
I've tried to uninstall and reinstall several times and to format the crad but the errors continues at the 50% times.
When the P3300 reads the card I notice an abnormal slow response to any input and at the end it hungs for a big while. If you leave it alone it comes back but I usually need the phone now and I must have to soft reset.
I'm about to hard reset and try again but I don't have time.
Well I hard reset my device before I was going to post it back to o2 for a replacement and surprise surprise its working fine again!
That was 23 days ago and since then its behaved perfectly. I've installed the SD enchancement just in case but not certain if that's made any difference. Finger crossed its the last time the card starts disappearing.
This happens on my MDA C3 too now and again.
When it does, a soft reset does not solve it.
I have to take the battery out and then reinsert it.
After powering up the problemis not there.
Anyone know why this is happening as its really inconvenient to keep taking the battery out.
Thanks in advance.
BTW, one thing I have noticed, it seems to happen more often after a registry value change if that help anyone???
My incredible will restart itself randomly. There's no pattern to it, it runs fine when it's on or I don't see anything wrong with it. The only thing that may be different is that it hasn't been activated by verizon yet. Just wondering if anybody else is having this problem
Yes I do too.I have done two hard resets and it has not fixed the issue.
I plan on calling in for most likely a replacement this week. It's not the signal issue as I live in Ohio.
+1 random resets
1 Million Postings
<sigh> I feel like I should keep a text file on hand which addresses THIS issue, and one which answers "will the 2150mah battery need a new back" ...
Anyway, on THIS tried and true point, a google search shows:
http://community.vzw.com/t5/Android...DIBLE-HTC-Incredible-Reboot-Issue/td-p/191740
http://www.product-reviews.net/2010/05/03/htc-droid-incredible-reboot-problems/
http://www.engadget.com/2010/05/01/htc-incredible-suffering-random-reboots-for-tar-heel-fans-and-du/
http://www.phonesreview.co.uk/2010/05/02/htc-incredible-incredibly-reboots-persistently/
etc. In addition there are plenty of posts on this topic on PPCGeeks, Android Forum, and IncredibleForum
Hopefully a fix will come.
I've had my incredible for about a week now with absolutely zero random resets.. maybe the newer shipped phones got a fix?
mine randomly resets when in low service areas
or
I believe mine resets randomly when the phone gets too hot (pocket, holder, etc).
Probably doesn't help much but two-three weeks ago my phone rebooted randomly 3-4 times over the course of about two days. It was always in an area with four bars of service and it wasn't overheating (to the touch).
Hasn't happened since then, though, so dunno.
I have had my phone for about a month and have not had a random reboot. I have had the HTC logo come up with a loading screen for a few seconds after shutting down progs with the Advanced Task Mgr.
I did not have any problems for the first few weeks but yesterday it rebooted on its own twice in two hours. Then it was fine the rest of the day. Nothing since then but I am watching it.
UgXvibe said:
I have had my phone for about a month and have not had a random reboot. I have had the HTC logo come up with a loading screen for a few seconds after shutting down progs with the Advanced Task Mgr.
Click to expand...
Click to collapse
Ok, I take this statement back.. phone has rebooted 2 times in the past 2 days. I'm not sure whats doing it yet. Where I had the phone as I watched it restart is in a very low cell reception area.. I'm in the sticks so some spots in my house work better than others.
+1 for Random Rebooting , 2-3X a day
Once mine warms up it goes into an endless reboot cycle until i pull the battery. Make a call it reboots. Use the nav it reboots. I have perfect signal but the indicator jumps from 0 to 4 bars on all my phones like vzw has issues. Using my wm phone instead with no issues. Even not activated with a fresh rom flash it does it. What a pos.
I've had the phone for ~1 month and had ZERO random resets until I moved home from college. I always had full 3G service at school, but have 0-1 bars on 1X at home. I had two random resets today.
i got random restart until i pull out the battery.. finally i found the phone restart because of the sd card, i formatted the sd card then ok, but when moving the application to sd, the problem persist again, maybe it because some application cannot move to sd..
khaidir84 said:
i got random restart until i pull out the battery.. finally i found the phone restart because of the sd card, i formatted the sd card then ok, but when moving the application to sd, the problem persist again, maybe it because some application cannot move to sd..
Click to expand...
Click to collapse
I've had this happen when putting apps on SD while using LPP. It apparently does not deal well when apps are on SD. Note: none of the apps I was using widgets and I read up on the LPP FC on reboot situation. But idk what the issue is for you but i've been able to reproduce a reboot when apps are on SD and I force a lot of CPU usage with LPP. Not an issue anymore though I just don't put apps on SD to be safe
after create partition on my sd using darktremor script for ext3.. my problem solve.. this is because the script in the ext3 informed to the system that the ext3 is phone storage..
Sent from my Incredible S using XDA Premium App
Random restarts, lag, etc
I've had my Incredible for about a year and a half, and it's been rooted all along. I kept getting the "low on space" warning, so I applied the "Convert2Ext4_no_data_limit_normal_dalvik.zip" fix from another thread (http://forum.xda-developers.com/showthread.php?t=1488351)
But after applying this so-called "fix," my Incredible lags like crazy, randomly restarts, freezes, etc. For example, while typing this comment, it's trying to send a text to my wife, and going on about 5 minutes of the "please wait" screen while sending.
It's the standard incredible (ADR6300) running the stock ROM... :crying:
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 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.
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.