This is my first post so be kind please. I was on nightlies until they stopped at 263. Gee One, I believe, has been posting Kang nightlies of the continuing development and they have been good. However one of the latest (somewhere between, say 320 and 327 or so), has caused problems with my sd card. On boot it doesn't read it and after I reboot (or actually I found rebooting doesn't do the trick. I have to turn it off then boot on) literally two dozen times or so, it will mount the card. But after anywheres from 5 minutes to 5 hours the card suddenly dismounts. So I rolled back to 263, the last "official" nightly, and all is fine again. I've replicated it by going back to the Kang and had to go back to 263 to cure it. I tried to post on the appropriate forum but I can't post there and I'm wondering whether others have this or it's just me and whether my conclusion based on observation is correct. Is it the Kang, me, or something obvious or nonobvious I've missed? Thanks.
Related
Hello All. I received a 32gb Class 4 SD Card for Christmas this year and have had nothing but issues. I am a faithful CyanogenMod 7 user and love the rom. However it constantly dismounts my new SD Card and other odd behavior. I have been testing it on stock 2.2 for a few days now and have had no issues. I have tried factory resets and so forth but nothing seems to make a difference. I have tried the latest MIUI as well. I assumed the SD Card was the issue for the longest time but since it works on stock I don't see how that could be the case. Perhaps a new kernel could help? If so any recommendations? I was running Teamhacksung ICS alpha build #14. It kept the card mounted fine but one issue made it unsuable for me.
Anyway any help appreciated. Thanks for reading!
This is a known issue, and it would help if you SEARCHED and then if you still didn't find the answer(which you would have). Then ask in the CM7 Q&A thread!!!
my apologies sir I am still very new.
I I flashed EOS nightly 51 with gapps 10.4 yesterday from nightly 34a, gapps 9.x. I did a full wipe as I was flashing a new gapps package. I have not loaded any new apps, simply restored my titanium backup.
While it seems rather random (not tied to any particular app/settings), I have had random screen freezes quite a few times in using this nightly. To fix, I have had to do the hard reset via power + volume down buttons. I filed a bug report but I just thought I'd ask if anyone else was having this particular issue with the latest nightlies (I have yet to flash 52 so this may have been fixed if it was indeed a bug).
Thanks.
I'm using a MZ601 with the TeamEOS nightlies for that flavour of the XOOM.
Others in the forums are reporting lockups similar to what you describe, but mine is working fine (Touch wood).
Some have suggested that changing the performance governor to lagfree instead of interactive helps.
I can only suggest you to flash a nightly numbered less than 50. With 51 I had problems my self for the first time since I flashed ICS on my xoom.
lucifergil said:
I can only suggest you to flash a nightly numbered less than 50. With 51 I had problems my self for the first time since I flashed ICS on my xoom.
Click to expand...
Click to collapse
Going to do this I guess. I feel like I remember someone saying they flashed back to 49.
Thanks guys. Just glad its not on my end.
I was having that problem yesterday but the latest nightly (53) seems to address the problem. Been using it most of the night with no reboots.
I got this for the 1st time yesterday since updating to ics. I only updated because my phone kept resetting since I installed a copy numbers to sim card app. Is this warning the ics version of resetting? What I mean is that I never had this warning on gingerbread and it got me thinking that ics removes the sd card to prevent the phone from restarting.
Anyway I sorted the problem by connecting the sd card to an adaptor on my pc then moving all its content onto pc and I then put the empty sd card back in my phone and formatted it and lastly put the files back onto it and its been fine so far.
scorpionatthepc said:
I got this for the 1st time yesterday since updating to ics. I only updated because my phone kept resetting since I installed a copy numbers to sim card app. Is this warning the ics version of resetting? What I mean is that I never had this warning on gingerbread and it got me thinking that ics removes the sd card to prevent the phone from restarting.
Anyway I sorted the problem by connecting the sd card to an adaptor on my pc then moving all its content onto pc and I then put the empty sd card back in my phone and formatted it and lastly put the files back onto it and its been fine so far.
Click to expand...
Click to collapse
I am also experiencing the same problem, the only way it seems for the SD card to be recognised again is by rebooting the phone.
I also experienced this when trying to restore contacts from the SD card.
Are you on ics or gingerbread? Like I said I never experienced it on gb but on gb the phone would reset if it didnt like something on the sd card.
scorpionatthepc said:
Are you on ics or gingerbread? Like I said I never experienced it on gb but on gb the phone would reset if it didnt like something on the sd card.
Click to expand...
Click to collapse
I have just updated to ICS and this has only started happening since that update.
What happened to the phone on GB if something went wrong with the SD?
Did it randomly go blank and have to be turned back on? If so I wonder if there is a fault with my SD card as what I have just described had been happening to me randomly while on GB.
On gb it would restart continueusly if there was a currupt file or if it didnt like something I installed. But this unexpectedly removed thing seems to be something ics does to stop it resetting.
Well I thought I solved the problem but its back again. It seems to happen when I go into gallery which makes me think theres a file in there what it doesnt like so Im going to move all pics to my pc and see if that solves the issue.
scorpionatthepc said:
Well I thought I solved the problem but its back again. It seems to happen when I go into gallery which makes me think theres a file in there what it doesnt like so Im going to move all pics to my pc and see if that solves the issue.
Click to expand...
Click to collapse
I have been having this issue too, but only since updating to the Andromadus Jelly Bean, I was running CM 9 for a while and this issue never occurred nor when I had the NEXX/NK111 Jelly Bean so I've put it down to something in the Kernel 3 code that the Andromadus build is using. It doesn't occur often, but you can guarantee that when it does it's when I really need it not to!
I've tried 2 SD cards, re-formatted, checked, etc and that makes no difference. I've gone several days without it happening and then it will just do it and it can take several reboots before it's stable again. I'm just looking at going back to the NEXX/NK111 builds now, I've not posted enough to be able to put this in the developer forum, but nobody else seems to be having this issue in the Andromadus thread.
RoboFig said:
I have been having this issue too, but only since updating to the Andromadus Jelly Bean, I was running CM 9 for a while and this issue never occurred nor when I had the NEXX/NK111 Jelly Bean so I've put it down to something in the Kernel 3 code that the Andromadus build is using. It doesn't occur often, but you can guarantee that when it does it's when I really need it not to!
I've tried 2 SD cards, re-formatted, checked, etc and that makes no difference. I've gone several days without it happening and then it will just do it and it can take several reboots before it's stable again. I'm just looking at going back to the NEXX/NK111 builds now, I've not posted enough to be able to put this in the developer forum, but nobody else seems to be having this issue in the Andromadus thread.
Click to expand...
Click to collapse
For further info, I've put the JB [ROM][04 SEP 2012][JB 4.1.1] Codename Android Saga 3 Nightly on my phone (not the latest build, that has Kernel 3 and some bugs) and it's been running now for about 36 hours without any issues, the battery life is better than other build's I've tried and I've had no SD card errors so far even when trying to cause one by doing a lot on the phone at the same time (which is the rumoured cause).
I think I might of solved this issue. My 8 gig class 4 card seems to work fine in my desire s yet my 16 gig class 6 card doesnt as it gives the removed message so logic tells me if I get a 16 gig class 4 card all should be fine.
Well I received my 16 gig class 4 card yesterday and transfaired all data to it and all seems fine so far so I guess class 4 cards are more suited for the desire s.
I'm using a 16gb class 10 in my desire S on Andromadus JB. I had the problem originally when I flashed from GB, however many reboots I tried it didn't fix.
I reformatted the card outside of the phone and it's been working fine since (3-4 weeks ago) except for one time. I've no clue what caused it, I went to sleep with it working fine, woke up in the morning with the issue again - a reboot fixed this though. Must be a kernel issue, since I never had the problem on any roms, GB or ICS, that I tried before.
I'm using a 4gb class 2 in my desire S on Official Sense 3.6 and Android 4.04. I had the problem originally when I flashed.
pedroxda-developers said:
I'm using a 4gb class 2 in my desire S on Official Sense 3.6 and Android 4.04. I had the problem originally when I flashed.
Click to expand...
Click to collapse
It is happening on any Sense ICS ROMS!
My wifes brother have HTC ONE V.
He have the same problem at least twice a week!
I think it's common bug for all HTC ICS ROMS!
I found this thread after searching for this issue. I have the T-Mobile Samsung Galaxy S2 and have also been having this issue constantly since updating to ICS.
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Which version of CM10? No reboots here on Provision.. Used CM10 latest nightly as a base.. If you have random reboots then I should too.. Also a logcat would be helpful.
Sent from my Provisioned Galaxy S Blaze
Im on the stable version, but ill try the nightly like the first post suggest or the link you provided
Edit: logcat on the way sorry about that
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2
anactoraaron said:
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Click to expand...
Click to collapse
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Daze7 said:
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Click to expand...
Click to collapse
Go to settings/storage. Press menu. Then USB computer connection. There you can choose. Select USB mass storage. When connected to the computer it will prompt you if you want to move files from computer to your phone.
Sent from my Provisioned Galaxy S Blaze
In the end I just went back to stock and did a clean new root, this time with ParanoidAndroid. I loved the cm10 stable i had but the phone shutting off was t0o much. Thanks for all the help though i really appreciate it. :angel:
I've got an i727R
It was rooted with TWRP and CyanogenMod 10.1.3 and it was fine.
This afternoon I noticed the battery dropping,rapidly. then it went off and could come back on.
I can't boot it with or without the battery, with or without the usb in (I suspect the battery is totally flat).
Prior to going crazy I:
- enabled encryption a couple of days ago
- noticed intagram had consumed 35% battery (i subsequently uninstalled instagram to try and stop the drain
When I plug the usb in it buzzes about once every two seconds
help
Wrong forum, belongs here. I've asked mods to move your thread, sit tight until they do.
MistahBungle said:
Wrong forum, belongs here. I've asked mods to move your thread, sit tight until they do.
Click to expand...
Click to collapse
Thanks. I noticed after I posted but couldn't delete (or find?) my post.
Good news, I was able to get it into download mode eventually. Once I was there I was good.
I re-flashed to stock with Odin; reformatted with default recovery to strip encryption; Odin'd it again; installed TWRP; finally CM 10.2.
It still seems to be having battery-drain issues, which I am investigating.
the_darkwing_duck said:
Thanks. I noticed after I posted but couldn't delete (or find?) my post.
Good news, I was able to get it into download mode eventually. Once I was there I was good.
I re-flashed to stock with Odin; reformatted with default recovery to strip encryption; Odin'd it again; installed TWRP; finally CM 10.2.
It still seems to be having battery-drain issues, which I am investigating.
Click to expand...
Click to collapse
Try a new or battery that has worked fine for you. also, clean flash your phone on a stock ROM and don't install any apps for a hour or so. See if the drain still exist. Best way to test it out!
Hit thanks if that helped!