Related
I have a HTC Fuze (AT&T GSM). I followed the instruction on (http://forum.xda-developers.com/showthread.php?t=951981) for FRX06 but it keeps getting stuck at "task rpcrouter:15 blocked for more than 120 sec". It never gets to the calibration screen... I even tried downloading and using a pre-made ts-calib file but the results were the same.
I also tried numerous other posts ROMS (FRX03, FRX04, XDAndroid 2.2 (rel 1.6).cab, even tried XDAndroid 2.1 (rel 2.5a).cab) but I still get stuck at the "task rpcrouter:15 blocked for more than 120 sec" error.
I read in another post back in Feb 11 that it was an issue and someone acknowledging it is an issue but no solution stated in the 19 pages of forums. Another user states this is a "bootloop" but did not offer any solution.
In any case, I never got to any graphical screens - never got past the text screens (white text on black background).
Help!
Actually the fix was to delete the data.img but that would be the "quick fix". This WAS mentioned under the troubleshooting section of THIS post. If you really want to see the calibration screen, download an older kernel package as stated HERE.
BE SURE TO SAVE THE FILE CALLED ts-calibration THAT YOU JUST CREATED!Additionally, I want you to format your microSD and start over from scratch. Just to flush out any other issues that you and may not encounter; such as the "waiting on SD card" issue some complain about. When I say format, I mean use something other than windows to format your microSD. I use the free version of partition wizard and it seems to do the trick. IF you want something a little less program intensive, I would suggest using SD Formatter. Again, not required but it might help solve other issues you may encounter on down the line.
All of that being said, I have a RAPH110 aka at&t Fuze, so I know this process works. If it doesn't work for you, YOU are doing something wrong!
Also, if you insist that you would rather skip the calibration screen, you may use my ts-calibration file. Make sure you place it where the file called haret.exe is.
CLICK HERE for your viewing pleasure!
Same problem with FRX06 even after FORMAT with OVERWRITE of the microSD. I included the ts-calib file. Got past "Creating a new Data Store" then got stuck at "mdp irq is already 4 4 and above mdp_dma: busy" where it would retry after getting stuck for 120 sec.
I then reformatted again and this time tried "XDAndroid 2.2 (rel 1.6).cab". Got to "Creating a new Data Store" and it is stuck there for over an hour - so I gave up.
I then tried deleting the files for "XDAndroid 2.2 (rel 1.6).cab" and this time tried "XDAndroid 2.1 (rel 2.5a).cab". Same issue.
Next, I tried loading Android on the Device instead of Storage Card. Stuck at the same point... I waited 5 min then quit.
I read elsewhere possibility of problems using micro SDHC cards... do you have a microSD card in your Fuze? My card is a Patriot microSDHC 8GB.
As always, there may be a bad batch but have had no such luck with buying PNY nor SanDisk. You did download 1231 as mentioned earlier, correct? So, if you want to try that first, you'll need to delete the existing modules-xxx and zImage file and extract the contents of the downloaded file till you see the modules-xxx and zImage_xxx. Rename the one called zImage_xxx to just zImage and be sure to place them with the file called haret.exe and launch haret once more. Keep in mind, downloading the kernel packages may not be required but in order to test things out and to see what works best, it is. Good luck my friend!
So I tried again and let the install run overnight (>4 hr). In the morning, it was still looping so I stopped it. Today, when I looked at the microSD, I see 171 FSCH0xxx files... most are 32K. 170 was 192K and 171 was 1.81M total of these files were about 158MB. Does this indicate anything?
Anyway, I reformatted my microSD card twice using the SDFormatter (Overwrite, Size Adjustment on), loaded FRX06, replaced the set with the 2 files you sent and renamed the zImage file. Booting up, goes into text screen, still get the timeout error. This time I noticed that there was a line that says "INFO: task dd:91 blocked for more than 120 seconds." My guess is that it's creating those FSCK files again... meaning SD card errors?
Have you another microSD to confirm whether it is a bad card? I just started from scratch (for the 50th time today) and I am NOT seeing what you are seeing(I don't see any FSCHxxx files)... I don't suggest trying anything older than FRX06. If anything, I'd suggest you see if you can find another microSD and probably only use that card for temporary storage.
OK, I'll have to go get another card this weekend then. I do think it seems like the card has some kind of compatibility problem... what brand are you using?
For tonight, I've formatted the card twice and then am trying the "XDAndroid 2.2 (rel 1.6).cab" now... It is stuck in the "Creating a New Data store" line for >20 minutes now... (FXR06 passes that but gets hung up trying to fix the file system). I'll wait a while longer and see if it will miraculously finish creating the new data store.
Thanks for your suggestions.
I have a PNY and SanDisk both 4GB class 4. I think bestbuy has the PNY one for like 30 bucks (maybe cheaper?)
I don't know what the problem is but I'm willing to help out how ever I can
I downloaded MiniTool Partition Wizard and deleted the microSD card's partition then recreated it. Then, I recopied the files into the root of the microSD, installed into my FUZE, and clicked on herat... this time it got into the Android graphical portion (no calibration needed since I included the ts-calibration file), stayed at the ANDROID screen for a while then went blank. I waited about 6 minutes then turned it off. When I went to see what's inside the microSD, I found the data.img file 256MB and also messed up file system again - since I shut it off prematurely.
With a lot more confidence this time, I repartitioned the microSD again, placed my Android files under its own folder. Crossing my fingers...
Ah, so you've been using the file path method then? If that is the case all one would need to do is put rel_path=FRX06 in the startup.txt file, between the quotation marks. Additionally, if you prefer more ogranization and plan to run more than one build at a time, it is best to have that command in your startup.txt file for each build. Keeping in mind, once you do this, it pretty much sets the default path for that build to that particular folder. I wasn't aware that you were starting one folder deep, my apologies . It's best to use the root folder for troublshooting and what not. I prefer to only use one build at a time because I find it easier to keep problems isolated and it helps me troubleshoot at the same time.
Additionally, if you want a more easier way to troubleshoot Android issues and you don't mind waiting for the data store (aka data.img) to be recreated at boot time, then one would only need to delete the data.img file (keep in mind if you have any settings or contacts, these may be deleted as well). What I usually do is once I get a good data.img, I make a backup and zip them up (or use your method of archiving). I also make a backup before I make any changes, like if I am testing out a new rootfs or kernel package. Most of this has been discussed and mentioned in the Android forums.
That did not work so I reformatted again and went back to using the root of the microSD for Android... FRX06 was stuck on GUI but blank screen all night - I turned it off in the morning. Back to the drawing board. At least I got the microSD issue figured out... on to the next mystery.
Update:
OK, partitioned my 8GB to 7GB FAT32, 512MB ext3, 512MB linux swap. Loaded FXR06 into the root folder, booted and it works this time. However, once into Android, it would lock up.
Case 1: Boot up android, clicked on Gmail, screen is android but nothing in the screen except background. Took out battery to turn off.
Case 2: Boot up android, left it alone, screen turned off - will not wake up. Took out battery to turn off.
Case 3: Boot up android, went to settings to set up wifi, froze. Took out battery to turn off.
Case 4: Boot up android, went to settings to set up wifi, entered WEP key, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing). Took out battery to turn off.
Case 5: Replaced the modules and zImage files to the new ones you sent me (12/31/2010)... booted up android, went to settings to set up wifi, entered WEP key, shows connected, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing).
Seems my Fuze is locking up soon after Android boot. Tried numerous times... left alone, freeze. Tried calling, freeze. It seems to be time based. So close...
Strange, though, as the phone remains warm to the touch despite being frozen for some time.
Yeah, you lost me at partitioning your device as I don't even touch that stuff. I think you are using something different. Sorry but I can not help you, my friend!
Thanks anyway... the partitioning is just to make the partition "different". Probably no relevance unless it allowed me to exclude some bad sectors from use. As far as Froyo, I guess there is some kind of HW or SW problem with my phone. I may reflash my Fuze to another WM ROM - just to clean it up and isolate SW as the problem.
Let me clarify, I don't partition my microSD because XDAndroid builds simply do not require this. There are Neopeek variants that require partitioning of the microSD but I still think your method is slightly over exaggerated. I'm not sure why but I guess for some reason there may be an issue with your microSD and partitioning may be a way around this issue but I don't know enough about partitioning microSD/non-volatile flash. So, I couldn't say for sure...
Ok, so I installed Tael ROM (WM 6.5) then tried installing, it still freezes after 1-2 min of booting up (or during boot up). So it looks like it's a hardware (phone or microSD) issue for some reason. I guess hardware vs thinking kernel because the 2.1 installs also do not work.
On another note, it seems that the Android boot process corrupts my other files... I have folders for GPS and photo (DCIM) and it "corrects" those errors and kills my files.
Hmmm... I can't say for certain as I've never experienced that issue. All of my files remain intact before and after booting into Android and rebooting into winmo. Are you talking about the files on your phone or microSD. If you are talking about your microSD, you might be experiencing the hardware issue and the while you boot into Android, it is only attempting to "fix" these issues and in the process, kills the files contained with-in. Does this makes any sense?
Yes, the files are those I mentioned are in my microSD. So, yes, looks like some kind of interface issue causing Android to think the files are corrupt and then try to "fix" them. Strange though that WM does not try to fix the "errors".
I think it's kind of like the linux way to make sure there won't be any issues when you run the OS, since Android would run off the microSD and not from the phones storage. Currently, there is some development for this called NAND. Still really nothing solid as to whether it will work or not but always good to know, I guess?
Well, the thing is those files are pictures/videos/GPS maps... so I think WM is able to read them (so not an error) yet Android does during its pre-boot scan. Anyway, since upon successful scan and android actually loads, it would freeze in 1-2 min, so the problem may not be limited to the microSD. Yeah, perhaps the NAND will work better. I did get Warm Donut to run on my old Tilt, so I am still hopeful.
The issue that is stumping me is that I'm not experiencing the same issues you are with XDAndroid and I'm not sure how else to help aside from using another microSD to confirm an issue with your current microSD.. sorry
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.
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.
My Note20U5G has had this small glitch for a while:
When I am using it, especially it I am opening an app window or typing inside one, EVERYTHING on my screen disappears for like 1 second. The only thing left is the homescreen wallpaper (without icons on it) and after that 1 second everything comes back to normal, if I was typing the screen where I left of, I am taken back to continue typing, etc... Now, even though this happens only once or up to twice a day, I figured it could be a sign that something is wrong.
So what I did was, is that I deactivated all apps that (in my opinion) could've contributed to this; onehand operation plus, live wallpapers, some apps in the background such as wireless power sharing, that I really never use.
However, no help. The twice a day glitch continued.
Next, I wiped cache using the "safe mode" or whatever it is called. I did this 2 days ago. And yesterday the whole day phone operated without glitches. But as day passed today I got one again.
As I am clueless what to do next I figured to do a hard reset, that is set the phone to factory settings.
Since I've owned this phone since November, there's some preparation to do before reseting to factory settings, so I thought to ask you guys if someone else had this glitch, as I was unable to google for it.
Thanks
Looks like a system UI crash and spontaneous recovery.
Do you have any apps put to sleep /standby or enlisted in deep sleep esp system apps
Also do you have power saving turned on.
Any thing that you changed in developers options.
I would update my phone to latest firmware and factory reset it.
Update all apps
Report back with an update
fizzingbees said:
Looks like a system UI crash and spontaneous recovery.
Do you have any apps put to sleep /standby or enlisted in deep sleep esp system apps
Also do you have power saving turned on.
Any thing that you changed in developers options.
I would update my phone to latest firmware and factory reset it.
Update all apps
Report back with an update
Click to expand...
Click to collapse
Nope, I don't have power saving on.
Here are my deep sleep apps. Nothing worth mentioning there IMO, all of them are some apps I might use but I don't ever need them running in the background.
If I go for factory reset, what is the best way to do it and no lose any personal data by chance. Obviously, I would back up photos to my computer... But other than that, what should I be careful about?
Try clearing the system cache.
Factory reset time, may be malware or maybe the OS or a vital system apk got corrupted.
Almost always caused by a 3rd party app especially launchers.
You got an SD card slot, use it!
It's a data drive; you have a dual drive PC
OS, download folder and apps go on internal storage.
Critical data, user files, music, vids, DCIM (move images here once a week or so) and backup copies of apps, app settings backup, phone contact backups, etc go on the SD card.
Use ApkExport to copy all your apps... no Playstore needed for a reload.
Everything you need for a full restore should be on the SD card. Think it through completely to avoid unpleasant surprises.
The Lexar 512 gb V30 card works well $75.
Other cards may be faster; only use a name brand card with at least a V30 rating.
Note: backup the SD card to at least 2 hhds that are physically and electronically isolated from each other!
blackhawk said:
Try clearing the system cache.
Factory reset time, may be malware or maybe the OS or a vital system apk got corrupted.
Almost always caused by a 3rd party app especially launchers.
You got an SD card slot, use it!
It's a data drive; you have a dual drive PC
OS, download folder and apps go on internal storage.
Critical data, user files, music, vids, DCIM (move images here once a week or so) and backup copies of apps, app settings backup, phone contact backups, etc go on the SD card.
Use ApkExport to copy all your apps... no Playstore needed for a reload.
Everything you need for a full restore should be on the SD card. Think it through completely to avoid unpleasant surprises.
The Lexar 512 gb V30 card works well $75.
Other cards may be faster; only use a name brand card with at least a V30 rating.
Note: backup the SD card to at least 2 hhds that are physically and electronically isolated from each other!
Click to expand...
Click to collapse
LoL I didn't know there was a memory slot, didn't need to think about it since I switched from a 128gb phone to this 256gb. Yeah, gonna get an sd card. Thanks
vdamir78 said:
LoL I didn't know there was a memory slot, didn't need to think about it since I switched from a 128gb phone to this 256gb. Yeah, gonna get an sd card. Thanks
Click to expand...
Click to collapse
Yeah once you get use to it, you'll demand it.
All my PCs and laptops are dual drive. It saves a lot of time, pain and boosts performance.
I can do a full reload on my Note 10+ in about 2 hrs and have it back to about 99% fully operational with no internet connection.
Without the card it becomes a gruelling 8+ hour process including having to load over 240 gb of data.
Backup everything now as once an Android OS starts exhibiting instability it's one boot away from a boot loop☠
They are very rare but that's how they start many times
Alright, I have just done one more thing: I completely disabled Nova Launcher (stopped using it anyways after I bought this N20U). If that doesn't help, I am proceeding with the reset.
vdamir78 said:
Alright, I have just done one more thing: I completely disabled Nova Launcher (stopped using it anyways after I bought this N20U). If that doesn't help, I am proceeding with the reset.
Click to expand...
Click to collapse
The Samsung launcher is better anyway, rock solid stable, fast with little battery usage.
Clear the system cache.
A 3rd party launcher can definitely crash a Samsung. One boot looped my Note 10+ twice, back to back over a year ago. I was seeing red.
Still running on the OS from that 2nd reset... still fast and stable less the 3rd party launcher
No essential app in deep sleeping apps.
Boot to safe mode and see if the problem persist, otherwise it's one of your apps responsible for this anomaly.
Copy entire internal drive data to SD card it flash drive via otg adapter
Use smart switch to backup Samsung notes.
Use swift backup or alpha backup app for contacts logs, messages and apps ( external data not saved fully on non-root devices)
Backup whatsapp on Google drive.
Afterwards, either flash factory firmware via odin to completely remove all traces of bugs ( recommended, use csc instead of home csc to wipe internal storage and all data)
Or factory reset from settings.
Then boot to recovery and wipe internal storage +factory reset again.. Its a bit extra but would eliminate any software related issues.
Report with update
blackhawk said:
The Samsung launcher is better anyway, rock solid stable, fast with little battery usage.
Clear the system cache.
A 3rd party launcher can definitely crash a Samsung. One boot looped my Note 10+ twice, back to back over a year ago. I was seeing red.
Still running on the OS from that 2nd reset... still fast and stable less the 3rd party launcher
Click to expand...
Click to collapse
I have seen this issue with good lock app on my note 4.. Uninstalling it caused system ui to crash repeatedly making phone unusable
vdamir78 said:
Alright, I have just done one more thing: I completely disabled Nova Launcher (stopped using it anyways after I bought this N20U). If that doesn't help, I am proceeding with the reset.
Click to expand...
Click to collapse
That's strange.
I have been rocking nova launcher since completing setup wizard. No issues so far.
fizzingbees said:
I have seen this issue with good lock app on my note 4.. Uninstalling it caused system ui to crash repeatedly making phone unusable
Click to expand...
Click to collapse
Wonder if it was the Lockstar module?
I never use any apps like that... once bitten, twice shy Other than it's goofy lame main page Good Lock gives me zero issues.
It wasn't Nova that boot looped the 2 OSs
It was slower and used more battery though then One UI... Samsung has made big improvements to their native launcher. The most customizable stock Android platform in existence too. It runs very well, uses very little power and is rock solid stable at least on my Note 10+/Pie variant. It has never crashed.
blackhawk said:
Wonder if it was the Lockstar module?
I never use any apps like that... once bitten, twice shy Other than it's goofy lame main page Good Lock gives me zero issues.
It wasn't Nova that boot looped the 2 OSs
It was slower and used more battery though then One UI... Samsung has made big improvements to their native launcher. The most customizable stock Android platform in existence too. It runs very well, uses very little power and is rock solid stable at least on my Note 10+/Pie variant. It has never crashed.
Click to expand...
Click to collapse
Actually it was 2017 version of Samsung good lock app that changed the lockscreen and quick panel.
Not like the modules now.
Update:
I decided to go for a samsung microsd, but I had to order a 256gb on ebay. So while I am waiting for it, I disabled good lock (nicelock to be precise) and I completely uninstalled Nova launcher.
No glitches since then.
Update:
After going back & forth with sd card purchase for my phone, I finally got a 256gb sd card that is the same size as my note20ultra's internal memory. So I was thinking, is it possible to completely mirror the phone's storage to sd card, and after I factory reset the phone, to copy that mirror back to the phone.
I used to do this with some PCs at my work a long time ago, using some sort of "ghost software"... so anyways, my sd card is capable to take every single data from the phone, what is my best backup/restore option to go for after a factory reset?
(Btw, the problem that I described in the opening post still persists, however it has become less frequent, like 50% less of a "hiccup" than it used to be)
vdamir78 said:
(Btw, the problem that I described in the opening post still persists, however it has become less frequent, like 50% less of a "hiccup" than it used to be)
Click to expand...
Click to collapse
Which OS and Samsung UI are installed on your N20U?
Are any applications listed in your Care report "Application history" in the Samsung Battery and device care section?
I had major "issues" with the System UI crashing after updating to Android 11/One UI 3.0 until the bugs were fixed with an update.
Surely hope you find a fix and do not have to factory reset your phone.
vdamir78 said:
Update:
After going back & forth with sd card purchase for my phone, I finally got a 256gb sd card that is the same size as my note20ultra's internal memory. So I was thinking, is it possible to completely mirror the phone's storage to sd card, and after I factory reset the phone, to copy that mirror back to the phone.
I used to do this with some PCs at my work a long time ago, using some sort of "ghost software"... so anyways, my sd card is capable to take every single data from the phone, what is my best backup/restore option to go for after a factory reset?
(Btw, the problem that I described in the opening post still persists, however it has become less frequent, like 50% less of a "hiccup" than it used to be)
Click to expand...
Click to collapse
I don't know of any app that can mirror Android drives real time. That not to say there isn't.
You would definitely take a performance hit if you could do it.
Like I said before the best solution is to use the SD card as the data drive. Just make sure to backup it up redundantly.
The lag your describing is bothersome. Track it down. It may be malware.
Clear system cache and do a hard reboot.
Do a network reset and clear the sim card tool kit data. Toggle Developer options off to clear it's settings... you can reenable then.
Disable all animations.
Is it still there?
Does it happen in safe mode?
If a 3rd party app is the cause either correct it or uninstall the app.
If you can't resolve the issue consider it malware and do a factory reset.
See if it's there after the reset before loading apps. If still present reflash the firmware.
If still present it may be a hardware issue.
This phone should be rocket fast with no lag.
There's near zero lag on my 10+ which has a slower memory and CPU.
blackhawk said:
I don't know of any app that can mirror Android drives real time. That not to say there isn't.
You would definitely take a performance hit if you could do it.
Like I said before the best solution is to use the SD card as the data drive. Just make sure to backup it up redundantly.
The lag your describing is bothersome. Track it down. It may be malware.
Clear system cache and do a hard reboot.
Do a network reset and clear the sim card tool kit data. Toggle Developer options off to clear it's settings... you can reenable then.
Disable all animations.
Is it still there?
Does it happen in safe mode?
If a 3rd party app is the cause either correct it or uninstall the app.
If you can't resolve the issue consider it malware and do a factory reset.
See if it's there after the reset before loading apps. If still present reflash the firmware.
If still present it may be a hardware issue.
This phone should be rocket fast with no lag.
There's near zero lag on my 10+ which has a slower memory and CPU.
Click to expand...
Click to collapse
The problem is that it is so random. I could not pinpoint any app to relate to it. I unistalled some apps in the meantime, but it still persists (less frequent). If I restarted in safe mode I would probably have to keep the phone in safe mode for at least 3 days to be sure.
Is there a malware detecting antivirus for android that works efficiently?
vdamir78 said:
The problem is that it is so random. I could not pinpoint any app to relate to it. I unistalled some apps in the meantime, but it still persists (less frequent). If I restarted in safe mode I would probably have to keep the phone in safe mode for at least 3 days to be sure.
Is there a malware detecting antivirus for android that works efficiently?
Click to expand...
Click to collapse
Reload time if the steps I mentioned don't work or if you did a major firmware upgrade without a factory reset.
Malwarebytes is good but there are always new undetectable infections floating around.
With odd behavior that cause can't be determined a virus or rootkit is a real possibility. They are very rare if you're careful but can happen.
I caught a trojan preloader on my 10+ about a year ago in the download folder with Malwarebytes. Fortunately I found/deleted it before it could download it's payload package and install it. It self downloaded through the Samsung browser... a nasty little bugger.
Malwareb. detected one malware app today, some photoediting app...deleted it, so let's see...