I think there are compatibility issues between Supercell games and my SD card. I'm getting SD card unexpectedly removed error when I tried to open Clash of clans. I faced the same problem before while I was playing Boom beach. I use a SanDisk Ultra MicroSDHC 16GB UHS-I Class 10 Memory Card.
skarthikpt said:
I think there are compatibility issues between Supercell games and my SD card. I'm getting SD card unexpectedly removed error when I tried to open Clash of clans. I faced the same problem before while I was playing Boom beach. I use a SanDisk Ultra MicroSDHC 16GB UHS-I Class 10 Memory Card.
Click to expand...
Click to collapse
i don't think so. i use the same SD card but a 32 GB variant and it works as flawlessly as it could. so honestly it doesn't seem like it's a compatibility issue.
Now i can advice you to troubleshoot it in this manner.
1. check when does it occur (the un-mounting message).
2. check whether it happens only on the current ROM or with the current kernels. (sometimes when your i/o options are not well tweaked as per your needs unexpected things can happen).
3. check for ROM bug fixes.
4. Try flashing another ROM like CM 12.1 latest nightly. it works flawlessly for me (as we have the same pair of hardware, might as well come handy).
5. Do a basic factory wipe i.e System, Data(Not Internal Storage), Cache, Dalvik Cache. This might aid you big time. so do not forget to wipe. but use it correctly otherwise can loose your storage in seconds.
you can try the above steps and see whether its a problem with your ROM or kernel.
if not come back for any other assistance with any unusual issue.
sanjumalik720 said:
i don't think so. i use the same SD card but a 32 GB variant and it works as flawlessly as it could. so honestly it doesn't seem like it's a compatibility issue.
Now i can advice you to troubleshoot it in this manner.
1. check when does it occur (the un-mounting message).
2. check whether it happens only on the current ROM or with the current kernels. (sometimes when your i/o options are not well tweaked as per your needs unexpected things can happen).
3. check for ROM bug fixes.
4. Try flashing another ROM like CM 12.1 latest nightly. it works flawlessly for me (as we have the same pair of hardware, might as well come handy).
5. Do a basic factory wipe i.e System, Data(Not Internal Storage), Cache, Dalvik Cache. This might aid you big time. so do not forget to wipe. but use it correctly otherwise can loose your storage in seconds.
you can try the above steps and see whether its a problem with your ROM or kernel.
if not come back for any other assistance with any unusual issue.
Click to expand...
Click to collapse
I'm on stock ROM. The message pops up exactly when I open Clash of Clans (Boom beach, few days back). I have a Moto G 2nd Gen. My device is not rooted. Is factory wipe same as Factory resetting the device? Moto G 2nd Gen is receiving Marshmallow now. I'll try again after upgrading to MM.
skarthikpt said:
I'm on stock ROM. The message pops up exactly when I open Clash of Clans (Boom beach, few days back). I have a Moto G 2nd Gen. My device is not rooted. Is factory wipe same as Factory resetting the device? Moto G 2nd Gen is receiving Marshmallow now. I'll try again after upgrading to MM.
Click to expand...
Click to collapse
did you try resetting your device? if not do it for once. it may trigger some possible issue fix. but tbh if its not into the rom it might be an issue with the hardware. so to be on a save side i recommend checking for the ROM issues manually by rooting and then installing a stable and working rom. like cm12.1 which may help you big time.
sanjumalik720 said:
did you try resetting your device? if not do it for once. it may trigger some possible issue fix. but tbh if its not into the rom it might be an issue with the hardware. so to be on a save side i recommend checking for the ROM issues manually by rooting and then installing a stable and working rom. like cm12.1 which may help you big time.
Click to expand...
Click to collapse
I am going to wait till MM update for Moto G. Also, I have requested a replacement from sandisk.
skarthikpt said:
I am going to wait till MM update for Moto G. Also, I have requested a replacement from sandisk.
Click to expand...
Click to collapse
Sandisk accepted my replacement request. They have asked me to send my SD card and they'll provide a new one it seems.
skarthikpt said:
Sandisk accepted my replacement request. They have asked me to send my SD card and they'll provide a new one it seems.
Click to expand...
Click to collapse
Very Well. Do let the community know whatever solves your issue. ciao.
Related
Finally ! Straight from Google DEVS
"nakasi" for Nexus 7 (Wi-Fi) 5.1.1 (LMY47V)
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
fortissimo said:
I found 5.1 official stock quite laggy on mine, coming from 4.4.4 official stock. So I wonder if there is a silver lining on this 5.1.1 or not. I won't hold my breath, but surprised that Google is willing to upgrade it despite it doesn't perform very well (similar to my iPad 1st gen taking 5.1.1, ironically, now same version number).
Click to expand...
Click to collapse
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
iBolski said:
I believe this was to fix the memory leak that was still present.
Installed via fastboot and rebooting now. Will update when I know more.
I do know that removing Facebook appears to help with performance, but there was still a performance issue on 5.1 that required a reboot at times.
I just think that this Nexus 7 (2012) is too old for LP.
Click to expand...
Click to collapse
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
gsmyth said:
I think the memory leak still hasn't been fixed yet, or it seems Google have found a fix but it STILL hasn't been released so it won't be in the 5.1.1 update.
https://code.google.com/p/android/issues/detail?id=170151&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
Click to expand...
Click to collapse
thats for the Nexus 5 though, I havent seen anything for the N7 yet.
2 of mine are bricked (one APX mode, the other corrupted emmc but seems to "work" - sort of - with all F2FS rom), I bought a board for $40 to replace one of them but the digitizer clamp and pins flaked off on contact when trying to reassemble it so Im reluctant to do anything with it without touch capability. its just going to sit there with my blutooth mouse for kitchen-netflix for now. Im thinking of selling them all "as is" but Im curious if this update pans out, I might keep the touchless one.
There's a lollipop rom for F2FS??
Varnak said:
There's a lollipop rom for F2FS??
Click to expand...
Click to collapse
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
JerryPi said:
Every lollipop rom can be run with f2fs on data and cache with an appropriate kernel. I use rastapop and franco kernel r82 in with f2fs and its golden
Click to expand...
Click to collapse
ok thanks. But i need to format system with normal partition?
Varnak said:
ok thanks. But i need to format system with normal partition?
Click to expand...
Click to collapse
You leave system partition on default ext4.
JerryPi said:
You leave system partition on default ext4.
Click to expand...
Click to collapse
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Varnak said:
How can i check wich partition are f2fs? i used a zip from this thread to convert http://forum.xda-developers.com/showthread.php?t=2678140
Click to expand...
Click to collapse
With the newer versions of twrp that zip is really not necessary to convert your partitions to a different file system.
To check and change format of your partitions go in your twrp recovery under wipe -advanced wipe - choose your partition - then repair or change your file system - there it says wich file system you are using and you can change it accordingly.
in twrp when you are changing the filesystem, it tells you which is the current.
Edit: just saw JerryPi's post
Two days in, 5.1.1 clearly better than 5.1 on my 32gb n7 2012 wifi.
Stock load/kernel/ext4 filesystems maintained, factory reset, full device restore/reinstall from cloud backup, rooted via TWRP, updated with SuperSU.
Nova Launcher, I just prefer it, no functional reason over stock Launcher.
Kindle app runs noticeably better, heck the Zinio reader app seems to work well too.
Google sheets/docs/presentation seems good.
TapaTalk Pro works well, as does Feedly. Notably less latency on network i/o and page transitions.
Facebook app doesn't seem to bring it down, even without any services disabled.
Haven't tried Chrome yet, and need to reload my music/video content to see how Rocket Player does.
disclaimer: I've taken to running "Trimmer (fstrim)" on an automatic schedule, daily, to keep nand free block lists healthy. That probably helps. I was doing that on 5.1 though.
If this keeps up I'd consider it a completely reasonable upgrade from KK.
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Marcovanbasten said:
Hi, what to do with the tgz file ? No zip to flash in custom recovery ?
Regards.
Click to expand...
Click to collapse
You need to flash via fastboot.
Hi guys.I have the Mix since Dec last year and it's definitely one of the best phones I've used recently.
I. Currently using theatest Epic ROM but my issues I have ...Apps fc'ing randomly and also random reboots...Have been happening constantly even with other ROMs.I usually do a full wipe when flashing.What can be causing this problems.
Thanks in advance
I found in the past when I used unofficial miui roms for other devices [for which unofficial is the only choice] that fc and random reboots usually came down to an argument between hand installed [flashed or app style install] google apps and the core of miui. This was especially common when I flashed gapps through twrp, even into a clean flash of the rom. I have used miui roms on many other devices, stopped at the note 3 when it would behave for a week or so but over time pick up fc's and reboots that would drive me crazy after a bit. No google apps and no fc's /reboots on the note 3 at the time. Have you tried the stable Chinese rom [unaltered]?
If all else fails it could be a ram /internal storage issue.
I havent tried any official roms but I see that there is a official global rom now available.
I will give it a go and hope the fc's and reboots stop.
Thanks:good:
If this is a ram issue or internal storage what can I do to fix it
Nicolfa said:
I found in the past when I used unofficial miui roms for other devices [for which unofficial is the only choice] that fc and random reboots usually came down to an argument between hand installed [flashed or app style install] google apps and the core of miui. This was especially common when I flashed gapps through twrp, even into a clean flash of the rom. I have used miui roms on many other devices, stopped at the note 3 when it would behave for a week or so but over time pick up fc's and reboots that would drive me crazy after a bit. No google apps and no fc's /reboots on the note 3 at the time. Have you tried the stable Chinese rom [unaltered]?
If all else fails it could be a ram /internal storage issue.
Click to expand...
Click to collapse
If this is a ram or internal storage issue what can I do to fix the problem
Not much really, you would have to go back on its warranty if any. Others may have more help though. Try and find ways to test the on board ram / storage and see if there are any issues, I am not knowledgeable enough in that area to guide you though.
Thanks though
Hey,
Just got a OnePlus 3T (Midnight Black) for my wife and wanted to get it rooted and updated to 7.1.1 as soon as I got it. I followed TK's suggestion on his video on using Opera VPN to change my region to Canada and got the update on the first try. After all was said and done I put my wife's sim card to start using the device and the 3T will not allow me to send phone calls, texts, or use data unless connected to Wi-Fi. I wasted a lot of time with AT&T thinking it was the sim card that was the issues but the device does receive text messages and calls so I am lost. The community on the OnePlus website has others who have issues after updating also to where their devices don't recognize the sim card(s) but they all seem pretty lost on any fixes to the issue. Anyone else have something similar or any solutions? Thanks in advance for anything positive.
No, I don't face this type of issue Sorry
After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.
I've always had an issue having the SIM card show up. I have to eject and reinsert the SIM slot after a reboot with the phone still on.
SIM issues after update seem to be a known problem on this phone, according to the following post. Either do a clean install of the full OTA, or do factory reset (somewhat obvious, backup any data you want to keep before doing either):
https://forum.xda-developers.com/showpost.php?p=71825477&postcount=1104
pitrus- said:
After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.
Click to expand...
Click to collapse
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.
rsnyc said:
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.
Click to expand...
Click to collapse
Unless you do like me, and run latest Lineage OS (Cyanogenmod), then you'll get 7.1.1 and working dual SIM. ?
I'm using EMMC CWM-based recovery v6.0.4.6 and my rom is Cyanogenmod 11-20141008-SNAPSHOT-M11-ovation.
I would love to upgrade to a faster and more stable rom if there is such a thing. I definitely don't need bleeding edge up to date stuff. I just want speed and stability. Advice appreciated, thanks!
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
herges said:
Hi, I've tried various Marshmallow and Nougat ROMS but from my experience they are not as fluid as the CM 11 ROMs - so I've gone back to these as they do everything I need them to do (apart from using the SDCARD as internal storage).
I would be happy to hear other people's experiences though.
Click to expand...
Click to collapse
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
nmyshkin said:
I finally convinced my husband to let me update his stock HD to CM 11 (the version archived at the very end of that thread). It was fine except for the need to hold in the power button to make sure it shut down, but he got used to that.
We began to run afoul of a few apps (like our local newspaper) that really wanted Lollipop or better, so I decided to take the plunge and installed the CM 12.1 in @amaces obsolete folder (and a pico GApps). For my husband, it's all good as long as the HDMI port still works
So far no complaints or odd behaviors with the CM 12.1 (same power button issue which apparently is like the poor--it will always be with us). I can't speak to relative speed (are any of these ROMs truly fast?) but it's certainly faster than AOSP 7.0 which I am running on my Nook Tablet, although I would not have known the difference if I had not been tweaking his tablet for him
So we're both happy.
Click to expand...
Click to collapse
nmyshkin said:
Edit: oh, and that thing about using the SD card as internal storage? I got sucked into that with my AOSP 7.0. The thing is, any backup I make with TWRP is trapped on the tablet. It can't be copied off--can't even be seen outside of TWRP. It eats up at least 2 gb of space that I begrudge. I would not recommend that option and would opt for portable storage if I were setting it up again.
Click to expand...
Click to collapse
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
ze7zez said:
I have Nook HD for a few days so you will not be surprised by my questions.
Do you use twrp-3.0.1-0-hummingbird.zip / twrp-3.1.1-0-hummingbird.img (experimental) from amaces or twrp-3.1.1-0-hummingbird.img from twrp.me?
Is there any USB OTG or Enable MTP in the Mount menu and none of it works?
Does any of these versions have Select Storage in the Backup menu and does not work?
Click to expand...
Click to collapse
No, if it concerns TWRP, I am not surprised. I flashed 2.8.7.5 to emmc when I did the CM 12.1 upgrade, but did not use it. Thankfully that install can be accomplished with CWM from the SD card. I have not even looked at the TWRP, but on my Nook Tablet I have had nothing but trouble with TWRP (now 3.0.2-0 I think). You have to touch things twice--sometimes. When you touch something you often get something entirely different. Sometimes it can't see the SD card until you boot several times into recovery. I hate it. Too bad CWM just didn't keep going. I don't care about the clunky interface. What good is a touch screen UI if the result is often random?
[Vent]
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.