Ive had a weird problem the last day or so, when I reboot my device, apps mysteriously go missing. Each time I reboot, like 5 or 6 different apps disappear. This only happens to SD card apps though. This started happening a few days ago but yesterday it got alot worse AFTER I had reformatted my card. Could there be something wrong with my SD card? The apps still appear to be installed in "manage applications" but they look like "com.aac.cachemate.demo" as the name of the app, instead of "Cachemate" and etc...?
did you use link2sd ?
com....whatever in manage applications usually means, that the apk file is missing, while the application data is present
the mess as described, can be seen if your ext partition is mounted too late ...
nadlabak has some fix about it
https://github.com/nadlabak/android...mmit/e5b9b3195687e04af7a7929f8637e77e1efae9a1
but i can't remember where is part of setting the property, after checking and mounting the whole card ...
nikctsh said:
did you use link2sd ?
Click to expand...
Click to collapse
I did not, I used the standard apps2sd built into CM6. Every time I reboot, different apps are missing and then some come back that were missing the time before...They all still appear in manage applications though so they might be intact but I'm not sure if all are, they show up with the default generic android icon, and weird names. "mobi.mgeek.tunnybrowser." (Dolphin Browser) and "net.flixter.android" (Flixter) etc...The storage sizes of the missing apps appear to be different then they are supposed to be. (Maybe)
(This might have something to do with it) Yesterday for hours (before I reformatted) the phone was stuck at "Preparing SD card, checking for errors" so I went online and followed the suggestion an xda member who suggested in another thread to delete the "fsck_msdos" file from "system /bin" which disables the SD card check to see if the SD card has been properly mounted and checked. It seemed to fix my other SD card issue for the rest of the day. could this be related?
Just share my experience , when I was in 2.1 , I used link2sd , and if I boot without sdcard , all my linked apps will happen like that , I think maybe this is the same case as apps2sd . So , what I do is just uninstalled all those apps , and reinstalled some of it ( it's quite annoying to reinstall over 100 apps ) . As you said , all those apps remained as it's package name , so I'm kinda sure our case is almost the same . But when I was in 2.2 , once I booted with sdcard inserted , but after boot completed , all my user apps dissapear , yes , ALL . But anyway , after scan for sdcard problem in OR , all my apps recovered , with no force close , just like nothing happen during the last boot . So also , try to scan for sdcard problem in OR .
It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....
donovanx3 said:
It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....
Click to expand...
Click to collapse
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
Ok I will run a chkdsk when I get some time to sit down at the computer later. I think it probably is corruption.
Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
SD card fixed with error checking in windows!! Thanks!
Fast Boot option may be the culprit
The advice about checking SD card on Windows or Linux sounds good and I will keep it in mind, but I did not need to fix this sort of problem. I am not familiar with CyanogenMod (CM) in any version, but if it has a fast boot option, read on...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
Sorry for opening up old thread. My HDC Note3 clone phone having the same/similar issue. The phone have 8G ROM which partition into 2 different name, internal phone (1G) and SD card (5G). Whatever Apps that I install on the SD card will disappear from home menu every-time I re-boot using the power button. However, it it still there when the phone do their own reboot due to something
I try unchecked "Fast Boot" but disappearing act still happen. Any suggestion to resolve the issue?
This is a strange one for me. Stumped. Been working on it all night, no improvement. New one for me, long-ish description (with detail), but a TL;DR too.
Last night I applied the 1.3 OTA for the K1. Being my K1 was rooted, I followed the process I have always followed by restoring the system images to stock, applying the OTA via recovery, then re-rooting. Process:
Shutdown tablet
Swap married/paired SD card with temp SD containing flashables (OTA, SuperSU)
Boot to bootloader, fastboot (re)flash tablet's current system images (recovery was already stock but flashed again for good measure, boot, system, blob -> staging)
Boot to custom recovery using fastboot boot -recovery image-
Flash OTA from temp SD, wipe caches, apply SuperSU
Shutdown, replace married SD, boot, enjoy life
This time I didn't immediately apply SuperSU, as I thought I'd flash 1.3 and let it go fully stock a bit to ensure no other updates were pending (nVidia seems to like incremental updates, so flashing to 1.1 won't give you an OTA to 1.3 directly, but to 1.2 first, then 1.3). I've also followed this process with the K1 for every update since 1.1 without a hitch, and although there haven't been many OTAs, it has still worked perfectly every time. Because of this and because I've done this a billion times on a million different devices with zero issues ever, I didn't take a backup before the update. Woe is me.
When I rebooted this time after flashing the OTA (no root), it booted up seemingly fine to the "Android is upgrading" modal, so I left the tablet alone for a bit to let it do its thing. When I came back, the tablet was HOT, was at a completely black screen save for the status bar (no wallpaper/launcher besides the clock/wifi icon which showed a connection, that's it). I tried to interact with it and couldn't (totally locked up, also a first), then it rebooted on its own. Subsequent times, during troubleshooting, I noticed that it's totally locked -- NOTHING responds, unless you can get to it before it reboots and hold power to kill it.
First thought was a bad flash. NBD, so went back and reflashed, double-checking everything and carefully following the same process. No dice. I did use a newer TWRP recovery from April of this year initially, which was a recommended version for the K1 specifically, rather than a really buggy but working one from last year. To test I did I try using the older TWRP on one of the next flashes thinking maybe the new one borked the partitions, or at least wasn't writing the partitions/symlinks properly (and the older one was the TWRP I had used for previous updates, with no issues). But, no change..
It took me a long time and many reflashes and cache formatting and digging before I realized if I pulled the married SD out, it booted just fine. Weird, and gets weirder. After leaving the married SD out and booting, and having the tablet working just as expected (except for missing the SD), Android shows a notification saying to reinsert the married SD. Once the married SD is reinserted, things seem OK for a few seconds before the whole system goes unresponsive again, heats up, and begins bootlooping. Before it sh'ts the bed, the message on the status notification asking to reinsert the married SD card doesn't change, but in the Storage settings, it shows it's "checking" the card, followed by a sudden hot death spiral into non-function. If you select the SD from Storage settings to take a look around its contents, the tablet basically locks up instantly. Inserting other SDs works fine (for the most part, still some other weirdness), it's just the married SD that totally kills the device without fail.
Obviously I'd like to avoid wiping and reinstalling the whole thing if it can be avoided, not just because my dumb ass didn't take a backup so I'd lose a ton of app/game data, but also because it's a just huge pain. A lot of the sites that offered "fixes" for these types of problems say to just wipe data, which is not a solution and is the nuclear option (like telling someone to to replace a car due to a flat tire).
Ideas? Is this as simple as recreating some symlinks that somehow disappeared and refuse to come back after all the flashes, and if so, how? I've been looking for hours and haven't found anyone with this particular issue or steps to correct.
[size=+2]TL;DR[/size]: Applied K1 1.3 OTA, married/paired SD card is no longer recognized, causes tablet to hard-lock and enter bootloop when inserted (other SDs do not cause this issue).
Other potentially pertinent bits:
Initial flash was dirty, second and subsequent flashes included a wipe of system first
Installed 1.2 images first, then tried going back to 1.1.1 and taking nVidia's OTAs to get back up to 1.3
1.1.1 does not recognize the married SD but doesn't kill the tablet, while 1.2 and 1.3 kill the tablet when the SD is inserted
When married SD is not inserted, using shell or ES Explorer or otherwise, not seeing a /storage/emulated/0, or /sdcard, or /data/media, or any other familiar storage related directories
When married SD is inserted, it dies too fast to look around much or try to do anything to check/fix the SD itself
/storage is totally empty except for a folder called "self", and inserting a working SD creates a directory under /storage labeled with the SD's serial number (not an emulated/0 directory or anything similar)
Not sure if this is expected behavior since the SD was married -- do those directories/symlinks live on the SD now since it's married, and won't show up in the device filesystem until everything's properly mounted?
Tried following these steps, which although written in the N5 forum, still seemed relevant.. no change
Tried the referenced SD permissions update with the card inserted and not, in case of the directories it touches only being visible/available with the card inserted, no change
Noticed even within TWRP, going to the "mount" menu seemed flaky, labored, and didn't show what I expected, but this could be because there isn't a "proper" or official custom recovery for the K1 yet and things are just buggy
ES File Manager still seems to think an /sdcard directory exists and tries to open to it, and just spins in an open directory.. as expected
Going to /data in ES File Manager shows me an empty directory with a message stating the SD card is missing
Using a working, freshly formatted SD in the tablet and trying to point Titanium to a directory on the SD gives me messages about the directory being unwritable, no matter where I go on the SD
Titanium's app permissions (including r/w storage) are proper, SD is not write protected (freshly formatted on the tablet)
Tried using SDFix, which also gave me an error re: "platform permission file is invalid"
There's probably more I'm missing, but can't remember it all -- I have tried everything, I feel like, and have been at it for 13 hours now (apologies if this is written spotty, fighting to keep my eyes open).
So is it totally hosed, or is this recoverable? Is there a way to fix the tablet to recognize the SD, or fix the SD itself if that's the issue (but I'd wonder how it got corrupted in the first place, since it has only been removed once fully powered down)? Is there at least a way to check the married SD for corruption or issues?
Thoughts?
EDIT: Formatting
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
GtrCraft said:
You removed the sdcard that was set as internal storage? Well you probably broke it/the data on it because that's not what you should do at all
Click to expand...
Click to collapse
And why is that? When the OS is running, sure, you can't. It'd be equivalent to just deleting /data while the OS was running. It seems pretty unlikely that removing and reinserting it while it's powered off, though, would make it suddenly unable to read the SD or forget its pairing. Adopted storage is "married" to the device via a generated encryption key, which is stored on the device's internal storage. It's all handled in software, not like the SD fuses itself to the device Removing the SD (while off) would not (and does not) break this pairing method, unless the internal storage or SD decides to spontaneously erase itself while the device was off.
The process outlined is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
grivad said:
When the OS is running, sure. Maybe that is the case, but it seems pretty unlikely that removing and reinserting it while it's powered off would make it spontaneously unable to read the SD or forget its pairing.
This is the recommended process for upgrading rooted devices with adopted storage. I've followed this process on multiple tablets/phones with adopted storage with zero issues, including this one several times, like I mentioned.
If it WERE the case that simply removing it (again, while off) made it forget the SD, I could understand the tablet reading the card and saying "nope not going to accept it, you done f'd up" and spitting out a dialog telling me to format it or whatnot.. lesson learned, if that were the case. However it's completely hard-locking the device (again, NOTHING works, no physical buttons, screen is unresponsive, only holding power to kill it works) when it's just reading the SD, and apparently pinning the CPU when doing so (hence the absurd heat)..? It's not just a matter of the tablet forgetting the SD
Click to expand...
Click to collapse
Still, you better off formatting it
Sent from my XT1562 using XDA Labs
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
lafester said:
Been running adopted storage in my mxpe since mm was released and have never removed the card to flash.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Cool.
Regarding the YOU CAN'T REMOVE IT belief (which is categorically false), if this were a serious issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Also that I cannot write to a working SD with Titanium. These things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
grivad said:
Cool.
Regarding the DON'T REMOVE IT belief, if this were an issue like people speculate it is, Android would simply not ALLOW you to remove it. Meaning if it was ever detected as being removed or missing, first time, Android would tell you "too bad, now it's unpaired", and would also make it REEEEALLY clear not to remove it at all, ever, during the pairing process, which it does not. Nor would it let you eject adopted storage, which you can, safely. Like I mentioned above, when booting without the SD present, the system runs fine and has a persistent notification asking you to reinsert the paired SD, and begins to check the SD as soon as it's inserted so it can be remounted. If you select the notification before putting the SD back in, it takes you to a panel explaining how the SD has all your apps, so you really should put it back in, or you can choose to "forget" the SD and you're back to square one. If you REALLY weren't supposed to remove the SD EVER, none of this would exist.
Additionally, pretty much every piece of documentation around adoptable storage says it can be removed just fine (but is only readable/usable by the device it was paired to), but the system kinda needs it to, you know, run all the apps you put on the thing, and will persistently remind you to reinsert it, unless you choose to break the adoption. So there's that.
Storage adoption isn't this magical, complicated thing. It mounts certain directories to your SD instead of internal storage (e.g., /storage/emulated), generates a key, then encrypts the card to prevent it from being read outside of the device it was paired with. That's really pretty much all there is to it. None of those things necessitate a or even imply that removal of an adopted SD would lead to sudden disaster. That's like believing if you take your hard drive out of your computer, but then plug it right back in, that it's going to be unbootable and dead. Doesn't work that way.
I appreciate you guys trying to help, but the problem is not simply that I removed the SD so now it's broken.
The thing that should get your attention is that when the SD is inserted, it begins to scan the SD and subsequently HARD-LOCKS. And PEGS THE CPU. Both of those things are pretty abnormal for Android devices, to say the least. There is something else going on here besides "You took the SD out and you weren't supposed to."
Click to expand...
Click to collapse
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
GtrCraft said:
Well you tried with another sd and there is no problem. So the cause of the freezing problem is your sd.
But be my guest and find another solution. I just gave an answer to your question and a solution for the problem. If you don't believe that then you shouldn't ask it in the first place
Click to expand...
Click to collapse
It's not that I don't believe the solution, I don't believe the premise because it is provably false There is absolutely nothing unsafe about ejecting adopted storage, which is why the OS lets you do it, even while it's running and using the storage. Even less of a risk if the thing is off. The "solution" offered wasn't much of a solution, and in the OP it was stated that I wasn't looking for that answer (already know that's an option, which is why I mentioned in the OP).
I appreciate you trying to help, but simply saying "format it", again, is the nuclear option. Not what I'm looking for. Either information as to what's happening (if anyone else has dealt with this) with a justification as to why it's irrepairable, or things to try based on the information I gave. Spending a lot of time being thorough just to get a "format it" response, to be frank, isn't very helpful It's like telling someone to reinstall their entire OS because they can't figure out how to install a driver, or to raze their house because a painting fell off the wall.
The SD didn't spontaneously corrupt itself in the 5 mins it was out of the device. No gamma bursts or EM storms in my area that I know of, either Because the only thing that changed was installing the OTA, this really seems to be a software problem (albeit a bit bizarre, to me) so it should be fixable via software. The fact it's pegging the CPU when the SD is inserted makes me wonder if it's getting stuck in a loop, maybe due to partition changes (looking for a file or partition it can't find). If that's the case, again, that should be fixable via software, with instruction from someone knowledgeable on how the Android FS and mounts work.
Again thanks for trying to help. I know formatting is an option (the easiest one), but I'm looking for just that -- options.
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
lafester said:
You did update the firmware with the sd out, nothing to do with lightning or gamma bursts.
Did you try downgrading firmware back to where it was?
Click to expand...
Click to collapse
True, the SD was out, however this is how I've both read to do it in multiple places, and how I've applied every OTA so far without issue (with the same adopted SD every time). As part of my troubleshooting, I did try flashing the OTA with the adopted SD inserted, though. It didn't make a difference.
I did try downgrading.. When I started the tablet was on 1.2, OTAd to 1.3. Every time I'd reflash I would do so to 1.2. I did try flashing down to 1.1.1 (the "recovery OS image") and OTAing back up, and like I mentioned that allowed me to use the device with the SD inserted, but it wouldn't recognize it as the adopted storage.. just kinda did nothing, as if the card wasn't inserted at all. This happened in 1.2 as well (OTAd from 1.1.1), and once it got up to 1.3 from 1.2 it all started all over again.
I'm creating an image of the SD right now (using dd) to try restoring it to another SD. I've read that doing this preserves the pairing information, so if it's a bad SD, this would hopefully fix it. I also wanted to try flashing directly to 1.3, but the images aren't available yet Only 1.2 and 1.1.1..
Honestly I would divorce the card before update then redo it after this whole method is janky anyway no reason to remap the data links like they do and all it would be required is if app devs were forced to comply with a data space method... The feature of installing to SD card should be available to non married storage.
Old thread, haven't been on in a while, but thought I'd post an update.
The problem ended up being a hardware issue. I contacted nVidia after absolutely nothing I tried resolved the issue (different SDs, different OS versions, different process to set up, etc.). I simply explained the problems I was having and my troubleshooting attempts, asked if it was a known issue or if they had any suggestions, and they immediately responded with RMA info, no questions asked. The replacement turnaround time was very fast (within a week IIRC), and the new K1 has had zero issues.
Hi
Can't remember whether or not this has been asked and answered, but here goes...
Shield tablet
5.1.1
Non-root
For the past 2 months or so I've been plagued with random reboots ( up to 2-3 times a day)
I've tried to
wipe cache 2 times
delete a whole bunch of apps
Change power settings
I have NOT YET tried to do a full wipe, due to the fact that I've got waaaay to many apps that don't sync data with google so it would be a major hassle to fix settings, copy data out and so on.... But am looking at backup solutions that include DATA ( helium)
I haven't been able to ascertain pattern.
Any suggestions on what I can do , or for that mater any way to find out why the hell it restarts.
Thanks in advance!
D
That's strange. So just reboots, no shutdowns?
I can only assume, maybe a rogue app with reboot access.
Just reboots
And It seems totally random.... everywhere from 4 times a day to non... Load dosen't seem to matter . From netflix and web to plain and simple spotify. It's driving me up one wall and down the other... can't figure it out, and really don't want to factory reset
Any form for event viewer or something that I can take a look at?
Worst part is I use it to take work notes and on a few occasions it's died (rebooted) on me in the middle of notetaking... starting to really mess with things ... and yes I know, do a factory reset, and I will if I run out of options. But my fear is that after I reinstall all the apps I'm back to square one, and it all starts all over again.
Maybe hibernating all non stock apps with Greenify could solve the riddle; if it's indeed a software issue. Once the problem ceased, activate one app at a time till the reboot bug reoccurs..
Hi
Sry for the slow reply
Been testing the Greenify for about 2 days and the same is still happening. I've more or less put all non stuck apps into hibernating list.. and run it every so often, as well as activated the hibernate at screen off. And it still happens... wish there was an event log or something that could point me in the right direction.
That's too bad. What if it is malware? I'd say make a factory reset. Stay clear of non stock apps and watch and see. If it still reboots, it must be a hardware issue. You still have warranty, aye?
Nope warranty is out, I think. I mean 2 year but got it back in 2014 at some point.
A damn it, was hoping to id the damn offending app and fix it without having to factory reset....
No one knows of any event / log feature in android ( akin to event viewer in windows)...??
I just read on Amazon that someone had the same issue inconsistent reboots and the culprit was a micro SD card.
Do you have on inside your Shield?
I had this problem like 3 months ago. When tablet was charging the led indicator was blinking on green an orange. The problem was that the cable from battery was connected bad, I just had to connect it with solder. (My tablet is replaced )
Niii4 said:
I just read on Amazon that someone had the same issue inconsistent reboots and the culprit was a micro SD card.
Do you have on inside your Shield?
Click to expand...
Click to collapse
Yeah, I do have an NTFS formated sd card installed...
Do you know of any easy way to check...or even better fix it?
Replace the SD card with another one or don't use one for now. You can still backup via USB or WiFi.
It may be a incompatible issue or a damaged SD card.
Backup via usb? As in copy paste the content of the SD card?
I have a lot of apps on the SD card, and not enough space on local storage to move back to tablet ....
Was hoping for some software based diagnostic or test to check the sdcard
Yes, you can copy n paste. Or save new data on a new SD card etc.
I presume there are Android SD card checker apps. But I think that won't help if it's an incompatible issue. Anyway, unmounting the current SD card won't erase its data. It's the sour apple you've to try.
Just somehow experienced the same.
Android 7.0 - no root no anything.
It's weird. Now it rebooted with 1% and then died. Before it just rebooted around 40%. Anyone found a solution?
Thanks
I've had a constant problem for the past few days with the camera. In every app that uses the camera I get an error message saying something like
"Please close other apps, the camera cannot be accessed right now."
This is temporarily redeemed with clearing my cache but after using the phone for a while the problem returns. Restarting the device doesn't seem to help very much but occasionally the camera will work after a restart. I'm on the software version 6.0.1 V20a-SEA-XX and I have a H959. I have not tried a hard reset on my device yet and wish to avoid that if an easier fix is available.
When the Mrs's phone was updated by LG following repair, she had a similar issue. It turned out to be an issue with the camera trying to save to the SD card, but the SD card not playing nice with the new firmware.
To see if you have the same issue, go into the camera and change the save location to internal storage before you attempt to take any shots. If you can take a shot after this change, you know its an issue with the SD card.
Lets hope its something so simple. :angel:
Masteryates said:
When the Mrs's phone was updated by LG following repair, she had a similar issue. It turned out to be an issue with the camera trying to save to the SD card, but the SD card not playing nice with the new firmware.
To see if you have the same issue, go into the camera and change the save location to internal storage before you attempt to take any shots. If you can take a shot after this change, you know its an issue with the SD card.
Lets hope its something so simple. :angel:
Click to expand...
Click to collapse
Got the camera to work for once and changed it to save to the phone. Worked for a while but I believe it reverted to saving to the SD card. Taking out the SD card and putting it back in was a simple fix along with saying "No" to a prompt about asking it I want to save to the SD card. Many thanks! I was starting to believe I'd never take photos again with this phone.
lol_cool88 said:
Got the camera to work for once and changed it to save to the phone. Worked for a while but I believe it reverted to saving to the SD card. Taking out the SD card and putting it back in was a simple fix along with saying "No" to a prompt about asking it I want to save to the SD card. Many thanks! I was starting to believe I'd never take photos again with this phone.
Click to expand...
Click to collapse
No problems Lol_cool. :highfive:
I would suggest you copy everything off that SD card and then format it using the phone before moving everything back onto it. Other apps may also cause the same types off issues if your SD card is now not entirely compatible with the phone.
Masteryates said:
No problems Lol_cool. :highfive:
I would suggest you copy everything off that SD card and then format it using the phone before moving everything back onto it. Other apps may also cause the same types off issues if your SD card is now not entirely compatible with the phone.
Click to expand...
Click to collapse
I have the same problem. I don't even use sd card and it always happen again and again. Even the flash can't be turned on in the quick toggle menu. I have hard resetted my phone several times and constantly appears again.
Ficoradic said:
I have the same problem. I don't even use sd card and it always happen again and again. Even the flash can't be turned on in the quick toggle menu. I have hard resetted my phone several times and constantly appears again.
Click to expand...
Click to collapse
I think LG will tell you to do a factory reset Ficoradic.
If that doesn't work, you'll have to do a RMA or pay for the repair if your out of warranty. :crying:
I'm having the exact same issue. I already replaced the rear camera module as I thought it was broken. It seemed to work for a while, but now i'm having the cannot connect to camera issue almost constantly.
What seems to help is to 'clear all' applications from the recent apps window, and use camera restarter (https://play.google.com/store/apps/details?id=com.exlyo.camerarestarter) a few times and launch the camera app again. (need root)
I'm using a rooted 5.1.1 v15C-EUR-XX, have root, xposed, powernap, amplify, greenify and some other root tools installed and am thinking that that might be the issue.
The restarter thing didn't work anymore today, so I put some pressure on the part of the laser focus thing while opening the camera app, and it worked until I took my finger off, then it went black. I tried again, and again it was a success. The connector for the camera is right under that laser thing so it might just be due to bad connection of the camera connector, or the laser thing that has a bad connection inside.