Even with setiron's newest 1.4.6 kernel im still having sdcard issues, it mounts fine now but even when copying to the sdcard it says that the files are too big when they're not and it won't copy to the sdcard. With xcaliburinhand 2.2.1 kernel im having randon read/write issues too.
Just wondering if anyone else is running into these issues too, love the smoothness of jpu but these sdcard issues are keeping me away from it.
peachpuff said:
Even with setiron's newest 1.4.6 kernel im still having sdcard issues, it mounts fine now but even when copying to the sdcard it says that the files are too big when they're not and it won't copy to the sdcard. With xcaliburinhand 2.2.1 kernel im having randon read/write issues too.
Just wondering if anyone else is running into these issues too, love the smoothness of jpu but these sdcard issues are keeping me away from it.
Click to expand...
Click to collapse
you either have a bad card or a bad card reader... two different kernals should have the same issue like that...
From what I've read and experienced, It's an issue with JPU. They changed the way the cards are read or something like that. Setiron and xcalibur put a fix in their kernels, however, their fixes haven't worked for me and other people. Like the OP said, My internal SD mounts but I can't copy or write to it.
Related
so now that we have a working sd card is there any way to change the save location of the browser and camera to the new working sd card?
Sent from my Xoom using Tapatalk
is there anything special to get the SD slot working? Mine still doesn't seem to be doing anything.
Well, in my opinion, which may be wrong...and probably is.
The new sd mod mounts the actual sd as /sdcard2/.
The problem i see with this is all the apps are looking for /sdcard/.
Now I think the best way to handle it would be to symlink /sdcard/ and /sdcard2/ as one volume.
The problem with that is that the volume manager would probably freak the **** out when you take your sdcard out of the device.
I don't know though, maybe bigrush or whoever got it working has this thought out better than I would have - but I am a software developer, not a kernel developer. That **** hurts my head.
Right now, i don't have an extra SD card worth my time of putting in (biggest extra I have is 8 gigs).
The only point I really see in it at the moment is extra space available from a file manager.
I am not sure if media scanner has to be modified to include the new directory to pic up on pictures, movies, and audio.
06types said:
is there anything special to get the SD slot working? Mine still doesn't seem to be doing anything.
Click to expand...
Click to collapse
Lol root your xoom and flash the new tiamat 1.3.0 kernel
oh, maybe ill just break down and root it... I didn't really see any point until now with the lack of roms out for this so far.
I have already flashed my xoom, with the original one button flash. The new version does not have a way like the original to just one button the kernel. Will I have to re-root everything and go from there or will it sense that I am already rooted and take me to changing the kernel to be able to use the sdcard?
floridatank said:
I have already flashed my xoom, with the original one button flash. The new version does not have a way like the original to just one button the kernel. Will I have to re-root everything and go from there or will it sense that I am already rooted and take me to changing the kernel to be able to use the sdcard?
Click to expand...
Click to collapse
if you use the newest one click method with tiamat 1.3.1 you will be wiping your xoom's data back to stock as well. which means you'll have to setup your xoom again and reinstall all your apps again.
if you want to just flash the newest kernel w/out wiping the data just follow the instructions on this page:
http://forum.xda-developers.com/showthread.php?t=978013
So, what rom should i use ? I use Khal V4 but it not so stable, it some time crack and some time can't not boot and it even sometime can't reconigize my SD card .
I just need a rom that stable and fast and can play game good. Any advise for me?
Thank you.
Don't know what to tell you. Khal's steel epic blue V4 is completely stable for me. Everything is fast and I don't get crashes... Even the camera app which used to jam up constantly and sometimes force me to do a battery pull after 3 pictures doesn't happen anymore (just fired off 10 shots in a row with no issues at all -though kind of slow rendering time sometimes).
You can try Dexter's 1.3 with Mioa7ae's patch, but I don't see why you should have any issues with Khal's rom.
I am using the Epic Blue also and after the first few days of tweaking, it runs stable and haven't had any real problems. The first few days were really hard and frustating to get everything running well and together.
I am using Full Fat32 with a 513swap and native froyo app2sd (with move2sd enabler) and this SD Speed Increase which ups that cache settings of your SD card through /System. Have to wipe Dalvik evey once in awhile but all-in-all faster than 2.1 and way more stable that Personared was. Could flash Galaxyxt4 though. Kept getting Md5 checksum error.
Good luck
justbenice said:
sometime can't reconigize my SD card
Click to expand...
Click to collapse
It seems to be very common for the SD card to cause trouble.
I think I would look into fixing your SD card. First try copying all the files off and reformatting it and copying them back. I recommend doing this after removing the card from the phone and inserting it directly into a computer. (If you're using the ext2/3 or swap partition you could get rid of them and reformat the entire card as fat). If you're still having problems, maybe your card has gone physically bad.
Since i got a new ROM flashed i got this issue that it never go away.
I got this scannig thing always and i dont let me do nothing from getting in to SDcard, not even the camera, Theres any fix for this issue..
I guess no body has an answer...!!
chipis said:
I guess no body has an answer...!!
Click to expand...
Click to collapse
Well, given the quality of your initial question, call me unsurprised. I don't have a clue about what you are asking.
are you talking about the media scanning process? which rom are you on and what does it say internal or external memory... either way reboot should fix the issue, pop out and reinsert your external sdcard if you have one.
Thanks for the quick respond, i have both, (internal) and (external Scaning media) It does not go away it just stays stick, i tried the reboot but still the same problem. I was using first theTHE WEAPOND 3.0-R1. I tried other ROMS but still the same...
mt3g said:
are you talking about the media scanning process? which rom are you on and what does it say internal or external memory... either way reboot should fix the issue, pop out and reinsert your external sdcard if you have one.
Click to expand...
Click to collapse
thats weird I've yet to see that issue on any rom. Maybe backup the files on to your PC and then format both wipe and boot if no errors then place all your files back and see if the issue comes back. If so then maybe a corrupt file or something best advice I have maybe someone will chime in with a different solution though.
I've had it hang at 80 something percent and then just reboot makes it go away, so I don't know what else to say.
Yea i know, But only with these Roms that i Mension. I tried The CM7 STABLE ROM and i had no problems with it. Can it Flashing different ROMS can leave many bugs behind or errors?
mt3g said:
thats weird I've yet to see that issue on any rom. Maybe backup the files on to your PC and then format both wipe and boot if no errors then place all your files back and see if the issue comes back. If so then maybe a corrupt file or something best advice I have maybe someone will chime in with a different solution though.
I've had it hang at 80 something percent and then just reboot makes it go away, so I don't know what else to say.
Click to expand...
Click to collapse
depends on how you flash it. and cm7 mounts there storage differently.
Hey guys. Does anyone know how to make this app work on ICS http://forum.xda-developers.com/showthread.php?t=1173195
or something similar to managed to read-write in microsd in ICS
tks
noope_br said:
Hey guys. Does anyone know how to make this app work on ICS http://forum.xda-developers.com/showthread.php?t=1173195
or something similar to managed to read-write in microsd in ICS
tks
Click to expand...
Click to collapse
Assuming you're on one of the EOS nightlies or the CM9 kang, you don't need anything special to read/write on your external sd. I typically use Root Explorer, but ES File Explorer and Astro should work, too. What problem are you having?
hchxoom said:
Assuming you're on one of the EOS nightlies or the CM9 kang, you don't need anything special to read/write on your external sd. I typically use Root Explorer, but ES File Explorer and Astro should work, too. What problem are you having?
Click to expand...
Click to collapse
No I am not in EOS or CM9. I'm in [UPDATE] [ICS] Stock IML77 Android 4.0.3, Root via CWM Recovery (U.S. Wi-Fi MZ604
And the problem I face is this below
Hardware sdcard continues to be read-only permissions via documented application
Why? cause titaniumbackup makes backups in a folder located on the microSD card,
That's not a big problem, transfer the folder to the internal memory of Xoom. But if it were possible would prefer the old folder.
That s why I ask! Is this official rom, is there any way to change is allowed? Just like the EOS and CM9.
tks
Apparently the application is running.
http://forum.xda-developers.com/show....php?t=1173195
I just needed to wait a few minutes after ICS was booted and yes i use the app to give me the direct write any app on sdcard.
tks
Yes. Had the same issue, but found it resolved itself after sometime (might have been after about the 3rd reboot). I think it takes some time for the ROM to configure itself on the tablet hardware so that al lthe associated apps can work properly. I notice this happens especially after doing a wipre/reset of data, and/or when moving to a new ROM like EOS or CM9 as mentioned above.
I just wanted to post this here in case it might help someone.
If you have ever had the SD card corrupted issue after installing a ROM or an update the first thing you should check is the kernel. I have found that every time I've had this issue I could still see the SD card in TWRP you couldn't figure out what was going on. I have since learned that the issue usually stems from the kernel. So take and reflash your current kernel or try a new kernel. Hope this helps someone good day
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
AngryManMLS said:
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
Click to expand...
Click to collapse
Why format the SD card if just flashing another kernel will fix the issue lol
shadavis08 said:
Why format the SD card if just flashing another kernel will fix the issue lol
Click to expand...
Click to collapse
I could think of a reason, that being (and this is an Android-wide rule) the kernel dictates support for file formats.
If you're using a kernel that has better features than a stock one on a ROM (let's say Gamma vs the stock LineageOS kernel in this case) the better kernel might not support the file-system format the stock one does. It comes down to support for what file-systems a kernel dev chooses to implement.
At least personally, I'd rather move 64GB off my microSD card, format it and move it all back on if it means I get to keep using a better kernel.
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
shadavis08 said:
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Click to expand...
Click to collapse
shadavis08 said:
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
Click to expand...
Click to collapse
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows 10-formatted SSD into my Windows 7-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
At least personally
Click to expand...
Click to collapse
which, again, doesn't make my process flawed.
Redline said:
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows-formatted SSD into my Linux-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
which, again, doesn't make my process flawed.
Click to expand...
Click to collapse
Wow really dude? I was giving some advice for people that could potentially keep them from losing all their data on the SD card. By simply flashing a different kernel before just wiping a card when the android system throws up an error saying sd card corrupted. You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
shadavis08 said:
You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
Click to expand...
Click to collapse
That's precisely the opposite of the reason why I'm here.
I was here to point out the benefits and potential downsides to doing it either way, but okay.
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
You could simulate this just by pulling the card without un-mounting it and then reinserting and android thinks the card is corrupt
I don't know. I don't have a computer to test with lol
One Twelve said:
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
Click to expand...
Click to collapse
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Redline said:
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Click to expand...
Click to collapse
My mistake not Android folder but lost.dir folder needs to be deleted
Back on nougat this happened to me twice on the same card. Formatted once and it happened again and this was back before I tried any custom ROMs or Kernels. Was purely stock rooted with SuperSU so it was definitely something screwy with LGs kernels
Kinda fuzzy but I think it happened first on 10J for TMobile and then again on 10K for my H918
I've not had any problems with my sandisk extreme 128GB for over a year now. On N.
I don't take the card out and swap it about, its been in all this time.