I had 3 random reboots while it was sleep mode.
yes
10chhar
Yep, I've seen mine do it 3 times since updating. Who knows how many times it's done it that I haven't seen.
The problem is the wifi will stay on after a random reboot and thus draining battery. You can see it on battery information in settings.
It just happened to me the past couple of days so I'm thinking it is one of the apps I installed. But I don't know how can I pinpoint it.
Yes
Sent from my Transformer TF101 using XDA Premium App
does for me anytime i have the keyboard dock connected and opened while the screen is sleep. did it 3-4 times. when the tablet isnt connected to the dock i doesn't do it at all.
SM0k3Y said:
does for me anytime i have the keyboard dock connected and opened while the screen is sleep. did it 3-4 times. when the tablet isnt connected to the dock i doesn't do it at all.
Click to expand...
Click to collapse
This is exactly what's happening to me. I have yet to see it reboot when not in the dock OR when in the dock with the screen on. Just as described above, if it is in the dock with the screen off, it will reboot occasionally.
This behavior completely stopped for me (knock on wood) when I removed my 16GB SD card from the slot on the dock. I've seen various threads about this working for others after I mentioned it previously, worth trying if you are using an SD card.
Random reboot twice last night...that I know of and once while using it. It's my Captivate all over.
Sent from my Captivate
I have had this issue as well.
As others have said, mine happens when it is docked and when the screen is off.
It can also happen when I am moving it to open position.
I have an SD card in the dock.
I have a feeling it has to do with the battery saver mode that disables the keyboards ability to unlock the tablet when it is asleep.
It will also redetect external storage each time it wakes. I think this is causing the issue.
I have disabled the MobileDock Battery saving mode in the screen settings and things seem better.
However, I haven't had it on long enough to say conclusively.
meatlocker said:
This behavior completely stopped for me (knock on wood) when I removed my 16GB SD card from the slot on the dock. I've seen various threads about this working for others after I mentioned it previously, worth trying if you are using an SD card.
Click to expand...
Click to collapse
It helped when I removed my 8 GB SD card from my keyboard dock... but after one or two days, it starts to reboot automatically again... I also noticed that my tablet itself reboots every few days...
Hrm I also just put a 16GB SD card in my dock and left it there recently, maybe I should take mine out and see if it helps. I'm also having an issue where when my tablet wakes and my SD card is in the slot, it either won't see it or it does but the folders all show as 0 byte files instead and I have to take it out and put back in to get it to work again.
I haveNever had a random Reboot on my tablet. Im on stock 3.1 no Dock.
I just realized that I too had the dock/tablet battery widget installed. Maybe that contributed to the reboot issue.
I no longer have it installed and have not experienced any weirdness.
I have mine 3 days and u haven't seen a reboot and when I check the system up time it's what it should be so I think mine is not doing it I am on stock 3.1 no root no sd card
Sent from my captivate BLAZING on firefly 3.0
curti.nogg said:
Random reboot twice last night...that I know of and once while using it. It's my Captivate all over.
Sent from my Captivate
Click to expand...
Click to collapse
Its my nexus s all over
Google will lose the battle
Sent from my Nexus S using XDA App
So this random reboot thing really started bugging me. Mine will reboot around 4 or 5 times a day while it's sitting on the desk open next to me and asleep.
I decided to try and figure out whats going on. After checking out all the threads on the matter it appears to have the following in common:
Any ROM, custom, rooted, stock, 3.01 or 3.1 seem affected
Only happens when tablet is docked with keyboard and asleep
Never happens when you are using the device
I'm on Prime 1.4, but had the problem on two MCR's I used (3.01 and 3.1), Prime 1.3 and Primordial.
I figured it must have something to do with the dock. Since th dock basically provides three things, battery, keyboard and storage slots I thought to start there. I did a full wipe on my TF and left it for a while. A reboot occured. I installed a real time loggerand set wifi to disconnect when the screen goes off. I figured maybe since the tablet by itself did not reboot it was something to do wiht the fact that the dock made the tab appear to be on charge, thus wifi never swithed off. It still rebooted. Not a wifi issue then...
I then noticed some folk having success by removng the SD card. So this was next. I removed my microSD that was in the provided SD carrier. Reboot! Then somebody told me the carrier has some electronics in it. I removed the whole unit. Bingo, three days and no reboot.
So, do the logs say anything? Well they say a heck of a lot, which is a bit of a problem. But looking for SDcard entries I found one consistant string of entries that always occurred close to a reboot. The SD card will randomly unmount. This is followed by a bunch entries after which the card will mount again.
So, not entirely sure what's going on , but problem seems to be related to the SD card slot.
I sure hope it can be fixed.
Log extract below where you can see the unmount etc. There is a lot more and it seems to happen quite often, but bottom line is that the card unmounts or the USBdevice disconnects. Why this should cause a reboot, I'm not sure. Maybe some brigher folks can figure it out.
06-15 13:08:13.509 D/DirectVolume( 90): Volume sdreader /data/Removable/SD partition 8:1 removed
06-15 13:08:13.529 D/ExternalStorage( 151): isExternalStoragePath : true
06-15 13:08:13.529 D/ExternalStorage( 151): onEvent:: raw= 605 Volume sdreader /data/Removable/SD state changed from 0 (No-Media) to 2 (Pending) cooked = 605 Volume sdreader /data/Removable/SD state changed from 0 (No-Media) to 2 (Pending)
06-15 13:08:13.529 D/ExternalStorage( 151): getVolumeState : /data/Removable/SD
06-15 13:08:13.529 D/ExternalStorage( 151): isExternalStoragePath : true
06-15 13:08:13.529 D/ExternalStorage( 151): onEvent:: raw= 605 Volume sdreader /data/Removable/SD state changed from 2 (Pending) to 1 (Idle-Unmounted) cooked = 605 Volume sdreader /data/Removable/SD state changed from 2 (Pending) to 1 (Idle-Unmounted)
06-15 13:08:13.529 D/ExternalStorage( 151): getVolumeState : /data/Removable/SD
06-15 13:08:13.529 D/ExternalStorage( 151): getUmsEnabling
06-15 13:08:13.529 D/ExternalStorage( 151): updatePublicVolumeState path : /data/Removable/SD state : unmounted
06-15 13:08:13.539 V/ExternalStorage( 151): updatePublicVolumeState mLegacyState_SDReader : removed
06-15 13:08:13.539 D/DirectVolume( 90): Volume sdreader /data/Removable/SD disk 8:0 removed
06-15 13:08:13.539 D/Vold ( 90): Volume sdreader state changing 1 (Idle-Unmounted) -> 0 (No-Media)
06-15 13:08:13.549 D/ExternalStorageNotification( 199): onExternalStorageStateChanged : path = /data/Removable/SD, newState = unmounted
06-15 13:08:13.559 D/ExternalStorage( 151): isExternalStoragePath : true
06-15 13:08:13.569 W/DMS ( 609): broadcast -> ACTION_EPAD_EXTERNAL_MEDIA_UNMOUNTED
06-15 13:08:13.569 D/UsbDeviceSettingsManager( 151): usbDeviceRemoved, sending Intent { act=android.hardware.usb.action.USB_DEVICE_DETACHED (has extras) }
06-15 13:08:13.589 D/ExternalStorage( 151): onEvent:: raw= 630 Volume sdreader /data/Removable/SD disk inserted (8:0) cooked = 630 Volume sdreader /data/Removable/SD disk inserted (8:0)
06-15 13:08:13.589 D/ExternalStorage( 151): doMountVolume : /data/Removable/SD
06-15 13:08:13.589 D/VoldCmdListener( 90): volume mount /data/Removable/SD
06-15 13:08:13.589 D/[ReceiveEvent]( 735): android.intent.action.EPAD_EXTERNAL_MEDIA_UNMOUNTED : /data/Removable/SD
Click to expand...
Click to collapse
andref said:
After checking out all the threads on the matter it appears to have the following in common:
Only happens when tablet is docked with keyboard and asleep
Click to expand...
Click to collapse
I'm not sure I agree with this statement - I have no dock and I experience the same issues. I do agree that it is something to do with the SD card though.
I was suffering the same reboot whilst I had a MicroSD card in my TF then I removed it. I have not noticed a reboot since.
I plan to plug a MicroSD back in soon and see what happens. I'll post back with my findings.
Also, can you tell me where you find the log you posted? Is there anything specific in the log that shows exactly when the reboot occurs?
Interesting, maybe this is a greater SD card issue then.
The log I got by using an app called LogViewer by ukzzang. It's nice as it has a record mode that writes to internal SD all the time.
There is nothing in the log at the time of the reboot sadly. I was kind of hoping for a app crash or kernel panic or something meaningful, but the logs simply stop at the reboot with nothing particular being logged.
Might be worth other folks runnng logs to see if there is some common issue here.
I want to be clear about my experience: the issue for me was with a FULL sized SD card in the DOCK slot, not the MicroSD in the tablet itself. I've had no issues at all with the MicroSD, and only seen the repeated sleep-dock reboot with a particular Patriot 16GB SD card in the dock.
Related
Hey there...
my Orbit2 (polaris) was working fine for some weeks now.
Well, something weird happened. Since yesterday the Storage Card doesn't show up anymore on my Orbit2.
I have no PC microSD-Reader to test it with that. But what the hell is that. I did nothing with the card. Really weird.
Any suggestions? Maybe a registry thing?
Thanks
Time to time my Cruise loses the card too...
This happens especially when doing weired things like lunching TomTom with the usb connected to the PC, and a sync starts blocking everything.
Usually it is just enough to hot remove and reinsert the card to get it back.
Beware, if you are obliged to reboot and the card is not seen yet, the system creates a "storage card" folder in the system memory and if your card gets recognized after, its name becomes "storage card 2".
To get back things, with the sd card outside the phone you have to erase the folder "storage card" just created.
Also, looking at forums it seems some people got the card corrupted, thus requiring the card to be reformatted (experience not yet tried).
Thanks for the answer.
Seems to be, that I'm in bigger trouble because removing and inserting doesn't help ;(
Even PocketMechanic doesn't recognize any card. But the device recognizes that i insert something because the backlight turns on when removing/inserting the card.
Also noticed the thing with the folder.
Hmm.. is there a key in the registry that could have something to do with that?
Well too bad. Will need to get a reader anywhere. Wanted to get a new, bigger card anyway but i need the data, hope it's not corrupted.
Bye
try this:
HKLM\System\StorageManager\Profiles\Auto Mount ... change to 1. if its alreay 1 change to 0 than again change to 1. becoz 1 to show SDcard. restert requer fot the effects.
hey,
got the same problem with the sd-card ...
why this happens :
- removed the sd-card
- started tomtom6 without maps stored on sd
- reinserted the sd-card
-> wm6 now did not recognize the inserted card !??
tried :
- softreset with and without the card
- changed the "automount" 0 / 1 and restarted the system several times (with and without the card)
- wm6 creates a folder called "StorageCard" ... deleted this folder ... restart ... different combinations of folder-delete / restart / registry change
but nothing works ... want to prevent the "hardreset" - any suggestions
thx
Neubi
Unrecognised micro SD card
Guys
Are yiou sure that the card is ok ?
I picked up an 8gig card from the web , it worked for a month then just died !
It is not recognised in any device / computer , its just dead !!!
Not sure why this should happen as I didnt touch/ remove the card , it was working , I went to bed , woke up and it wasnt working the next day !
£40.00 down the drain ,
Astro1
Couple months ago I got one of those fancy 16 GB microSD cards for my Vogue. This morning I woke up and saw that my regular backup (with Sprite) had completed. But I also quickly discovered that my card (where backups are stored to) had a corrupt file system.
Plugged it into Windows and did a couple of repair attempts, but nothing worked. Sighed and went to format option. After this it appeared to be successful except for the last line of the job - the dreaded "Track 0 is bad. Disk is unusable. You are totally screwed." message.
I can (and have done) some basic troubleshooting, but this one is beyond me. Is there a way to recover from this, or can I just throw the card into the trash?
AJ
Hi,
Running CM7, Faux123 2.0 kernel.
It's been 100% stable for me and my usage profile.
However, today switched off the phone to fully charge the battery. It was a clean shutdown, i.e. NOT a battery removal. I fully charged it and sometime later went to switch it on. When it started up it complained about the SD card. The Sensation couldn't see it at all.
I switched off, removed the card and inserted it in a uSD -> USB on a M$ Windoz system. The PC refused to mount it and also refused to format it, I made several attempts. I didn't have time to try it on my Linux system.
After flaffing around on the M$ Windoz system I tried on the phone again failed. I then rebooted into CWM and it reformatted fine, then booted fine.
I've only had one other uSD card issue before (on my Desire, the card just failed 100%, complete and utter failure on the card). This seems to have been a partial failure, almost a partitioning issue, must admit I didn't try to re-partition on the PC.
I was wondering if other folks have had similar uSD card issues.
I am having maddening issues with my Cap (running KJ3 rooted). When the SD card is inserted, it becomes very unstable and soft reboots - usually on startup (and repeats ad infinitium). If I start up without the SD card, I am stable, but I have many apps that KJ3 defaults to installing on the SD card. The problem occurs whether I insert the card before boot up, or insert after it has started up.
I have the same issue with 2 different cards. I tried a brand new class 10, 16GB. I restored apps from my TiBu backup which I had copied from the old card to new (on PC) - not sure if that is the issue...
Anyone have any ideas?
Well, if I am not mistaken, apps which are installed to SD are not on the removable SD card, but on the captivate's "Internal SD", which is the 16GB... well actually about 13GB after the phone's "internal Storage" partition is lopped off of it.
I would try a reflash and then test it before you install the apps.
rfound said:
Well, if I am not mistaken, apps which are installed to SD are not on the removable SD card, but on the captivate's "Internal SD", which is the 16GB... well actually about 13GB after the phone's "internal Storage" partition is lopped off of it.
I would try a reflash and then test it before you install the apps.
Click to expand...
Click to collapse
I've been down that road more times than you can imagine - flash, wipe in recovery, and reload. I had thought that it was the .androidsecure directory on the external SD that held the parts of the apps that move. what is clear is that this only happens with the external SD card inserted and mounted, and almost always happens within 10 minutes of startup or the previous cycle, i.e., before any program launches other than TouchWiz and often before any email sync (this is my work phone, syncs with Exchange 2007 server).
I did get a list of all apps that have the start on boot permission, not sure if any of these are regular problem children, they are, on my phone (not sure why some of them need that permission, but that's a different story):
Amazon MP3
Amazon Appstore
Contapps
Dolphin Browser
Finance
FIOS Remote
FilghtView Free
Folder Organizer
GetJar
Gmail
Goggles
Google Voice
Handcent SMS
iCookbook
Lookout
Maps
Market
MLB.com At Bat 11
Office Talk Free
OfficeSuite
Pocket Casts
Pocket Informant
ReadItLater
ScoreCenter
SeekDroid
Super Manager
Superuser
Titanium Backup
TuneIn Radio Pro
United Airlines
Wordsmith
Did you move the apps back to internal memory after restoring them? Iirc, when using the later leaks, they install all the apps to external sd(if there is one in the phone).
mrhaley30705 said:
Did you move the apps back to internal memory after restoring them? Iirc, when using the later leaks, they install all the apps to external sd(if there is one in the phone).
Click to expand...
Click to collapse
Going to start doing that, the next time I have a stable spell with the card in. The problem is that the failure is intermittent. It doesn't fail every time I have the SD card in, but every time it does fail, I have the card installed, and it usually takes awhile before it starts working again. Thinking about another factory reset and then reinstalling apps without TiBu help or the card in, at least until I get all of the ones that startup in main memory to eliminate that possibility.
Of course with the Epic finally getting the official upgrade, kind of want to hold off until the Captivate image finally comes out, that way if it is a hardware problem. I'll be on stock for the warranty exchange.
Arggh... maddening problems continued.
The phone stayed up (with SD card in for about 16 hours), during that time I moved every app with the permission to launch on boot to main memory. I then had the kernel panic, or whatever the soft boot actually is, occur while in Pocket Informant.
I then watched it cycle through display PIN-lock screen, start media scan, screen shut off, and then re-boot seven times, approximately every three minutes while never touching the phone. Some times I saw on the status bar "Media scan completed", sometimes it had the icons.
After powering down, and starting up from off - it is now up again, who knows for how long.
So unfortunately, I can now say this is not just a startup issue; I can also say that something that happens during startup (or at least the kernel launch) creates the conditions for this reboot cycle to occur.
Anyone out there have any ideas?
stoobie-doo said:
Arggh... maddening problems continued.
The phone stayed up (with SD card in for about 16 hours), during that time I moved every app with the permission to launch on boot to main memory. I then had the kernel panic, or whatever the soft boot actually is, occur while in Pocket Informant.
I then watched it cycle through display PIN-lock screen, start media scan, screen shut off, and then re-boot seven times, approximately every three minutes while never touching the phone. Some times I saw on the status bar "Media scan completed", sometimes it had the icons.
After powering down, and starting up from off - it is now up again, who knows for how long.
So unfortunately, I can now say this is not just a startup issue; I can also say that something that happens during startup (or at least the kernel launch) creates the conditions for this reboot cycle to occur.
Anyone out there have any ideas?
Click to expand...
Click to collapse
question what kind of sd card do you have in there as in what class? class 10s can cause issues . wait i see .. have you tried a class 4 or 6? I had mutiple 10s cause issues like this and exchanged for a 4 and all issues went away .. or you can format the card on your computer using fat32 and set to 32k sectors but that did not work for me ..
xhozt said:
question what kind of sd card do you have in there as in what class? class 10s can cause issues . wait i see .. have you tried a class 4 or 6? I had mutiple 10s cause issues like this and exchanged for a 4 and all issues went away .. or you can format the card on your computer using fat32 and set to 32k sectors but that did not work for me ..
Click to expand...
Click to collapse
I had a 16GB class 4 (Patriot) in. I just replaced it with a PNY 16GB Class 10. Both have had the same issues (currently using the Class 10). Both were formatted in the phone itself - so assuming they are FAT32.
OK, seems I understand the issue, and seems also that I cornered the issue.
First, the card is working normally while DEVICE ISN'T SLEEPING.
Second, it happens mostly while WE'RE SLEEPING AT NIGHT or WHILE THE PHONE LEFT DEEP SLEEP (Paranormal Activity? LOL)
So, based on this: something in kernel/ROM/anything that control the power to SDCARD doesn't provide correct/adequate voltage or electricity to the SDCARD while the phone in DEEPSLEEP.
Or: the card don't want to be suspended in deepsleep, it just removing itself when instructed to sleep (this one is the card's fault).
And: any card thats been badly removed thousands times (it can do around 20 bad removal at 7h period so, count it yourself), its become broken/unusable but not fried as stated in many site). The chip broken,yes,but due to bad removal thousands times....
So, any response and research is needed on this.
Also disassembling the device to re-plug the sd/sim module flex inside doesn't help at all, so don't bother with it.
I'm really into this really, because my SIII has already killed two 32 GB Class 10 Cards... suddenly the last one was a week ago I copied a filed restarted phone to recovery and boom SD gone... so I will check this post I think that the SD card killing case was only a few people but it seems like a major problem.
This is caused by bad quality SD cards. SanDisk already admitted it as a failure on their side.
I've already spent countless methods in trying to debug and fix it. I solved it by buying a new card.
Hmm, so the moderators can delete this thread as it seems that this doesnt need any research...
Coz many also said that using Samsung's card also got this trouble...
[solved] sd card umounting galaxy note 4 autosync dropbox
There are security files on the SD card that are markers that can't be over written. Simply copy all your data to a pc. Then format using the note sd format. Then copy only the important files like pictures movie ect. It's a security feature just start over.