Ok I just noticed that every time I try to record 720p video after few seconds to a minute I get a camera failed message and it stops recording. It works fine if I choose any other resolution?? I'm running Bionic Ice 2 stable and Bali 3.1. I haven't had any issues at all except this. Could this be because I switched to Ext4? Has anybody ever had this problem and found a solution? Thanks.
Sent from my SGH-T959V using XDA App
Bryanb82 said:
Ok I just noticed that every time I try to record 720p video after few seconds to a minute I get a camera failed message and it stops recording. It works fine if I choose any other resolution?? I'm running Bionic Ice 2 stable and Bali 3.1. I haven't had any issues at all except this. Could this be because I switched to Ext4? Has anybody ever had this problem and found a solution? Thanks.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
No problems on my sgs4g running black ice 2 with voodoo enabled and Bali 3.1 kernel. i took a video at 1280x720 for over a minute with no fail.
Sent from my My Touch 4G using XDA Premium App
Try master reset?? If that doesn't work flash back to KD1. If that doesnt work then your phone is probably one of the few SGS's that are affected by the Camera Failed Bug. You will need to ODIN back to stock KD1, and unroot if the KD1 you're flashing comes with root.
Once you've tried alll of these call 611 on your phone. Let them know you've already done the master reset and it's still broken. They will get your warranty replacement shipped out. If you have insurance you'll only pay a 5 dollar processing fee. If you dont it will cost 20 bucks (shipping is free but there is a new processing fee as of about a week ago).
Bryanb82 said:
Ok I just noticed that every time I try to record 720p video after few seconds to a minute I get a camera failed message and it stops recording. It works fine if I choose any other resolution?? I'm running Bionic Ice 2 stable and Bali 3.1. I haven't had any issues at all except this. Could this be because I switched to Ext4? Has anybody ever had this problem and found a solution? Thanks.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
The SDHC card the phone ships with isn't fast enough for 720p. I had the same problem too until I replaced it with a faster one (the one that it ships with is a class 2, you can get a 32 gig class 4 for 55 bucks on amazon and you'll get double the space to boot)
I'm guessing you're trying to record at 1,280x720. I've been getting that too. The quick fix for that is to record something at 720x480 (or anything lower, I believe). Let it record for a few seconds, delete whatever you recorded, then switch back to 1,280x720. The HD recording should work again.
This problem seems to happen every time I reboot. Once I do this, it's pretty much set until my phone reboots again.
Let me know if it helped!
FBis251 said:
The SDHC card the phone ships with isn't fast enough for 720p. I had the same problem too until I replaced it with a faster one (the one that it ships with is a class 2, you can get a 32 gig class 4 for 55 bucks on amazon and you'll get double the space to boot)
Click to expand...
Click to collapse
Interesting.. ill look into that one. That might make sense considering the card that comes with the phone is a class 2 card. They have stopped shipping those horrid class 2 sandisk cards though.
Sent from my Samsung Galaxy Tab 10.1.
the reason why your camera is failing is because you need to go into CWM and fix permissions, once this is done your camera will work again
guaranteed trust me
dsexton702 said:
the reason why your camera is failing is because you need to go into CWM and fix permissions, once this is done your camera will work again
guaranteed trust me
Click to expand...
Click to collapse
No, that doesn't work. And before anyone says it's the speed of the HD card, it's not. I swapped to a Transcend Class 6 a long while back and HD recording had ALWAYS worked just fine before hand. It's something to do with Bali's 3.x's ext4 implementation or perhaps it doesn't play nice with WhiteHawk's stock KD1 that I Odined a while back.
http://forum.xda-developers.com/showpost.php?p=15288271&postcount=804
Then someone needs to explain why everything is working for me now after I removed the lagfix. It most definitely has something to do with the lagfix implementation. I was very methodical about what I did and changed only one variable at a time.
1) Whitehawk Odin stock KD1 deodexed with Bali 3.1UV, your init.d ext4 lagfix tweak, accurate battery mod, system/data/cache all ext4
2) Tried fixing permissions and clearing Dalvik, just in case. Still can't record properly.
3) Removed your init.d script and reboot. Still can't record properly
4) Updated to Bali 3.2UV. Still can't record properly.
5) CWM nandroid backup, RFS formatted, restored backup, completely disabled lagfix. Reboot. Checked Voodoo control panel and it says RFS compatibility mode. CAMERA WORKS.
Also, I'm using a Transcend class 6 SDHC card which has ALWAYS been fast enough before, and apparently is fast enough now that I fixed the problem by removing the lagfix.
Click to expand...
Click to collapse
edit: I am in the process of converting data and cache to ext4 but NOT system. Going to see what happens.
edit2: cache/data converted. camcorder app giving a "recording failed" error again after some recording.
edit3: disabled lagfix again without restoring the backup. just unchecked the box. linda converted for some time. back to rfs compatibility mode. but camera's not working again. in the process of repeating the steps i outlined above to verify that the camcorder WAS working originally. i know that the camcorder definitely USED to work, so at SOME point it broke. i just have to figure out where that point is.
edit4: full restore did NOT work this time. i even flashed back down to bali 2.0uv. this is very strange because i'm sure when i was on 2.0uv my hd camera was working... what the hell. i am currently looking at my sdhc card as being a culprit. yanked it out and doing a diagnostic check on it using my laptop.
I removed my Transcend class 6, and insert the stock Samsung 16GB card that I blanked out.
Currently recording, 3 minutes, without stopping.
Going to have to look into the SD issue more. It's a class 6 card so it should be fast enough, but maybe it has problems when it's filled up. Hmm... Very puzzled now. I ran a full format on the card, ran a full diagnostics, and copied my apps back on and it still crapped out...
edit: Wiped out the Transcend class 6, left it blank, popped it into the phone, recording with HD just fine now. Hmm...
update 2: HUH! This is very strange... stranger and stranger!
So I have 2 SD cards. A Transcend Class 6 8GB card. This is the card that I've been having problems with the entire time. "Recording failed" error in camcorder after random short amounts of time... usually between 10-60 seconds at best.
I popped in an empty Samsung Class 2 16GB card that came with the phone. NO PROBLEMS.
Okay, so I thought maybe it's a card problem. NOPE.
I formatted the Transcend card, put that back in WITHOUT restoring what I had on the SD card. And it records in the camcorder just fine!!
I then took the Samsung Class 2 card, and copied all the files back onto it that I had on my SD card (a restore) and IT DOES NOT WORK ANYMORE.
I then restore everything onto the Transcend card, IT DOES NOT WORK.
In other words, SOMETHING on my SD card is causing it the camcorder to fail! HMMMMMM. I'm trying to selectively restore my SD folders to see what happens....
edit: Narrowed it down to one of my media folders. Probably the DCIM folder.
I've been slowly restoring folders and I think it might have been due to a corrupted .thumbnails folder in DCM. Delete the entire .thumbnails folder and the system will regenerate them. See if that works.
edit: Disregard. That didn't work... I'm recording longer now, but I can't figure out why... Had it going for 2 full minutes before it failed out again. Wtf...
edit2: Conducted a new test to determine if it was a problem with the card being filled. Created a few dummy files to use up about 7GB of the 8GB on the card. Recording 4 minutes now, no problems. So it's not a problem with the card being filled up.
edit3: Siiiigh, many hours later and I still can't figure it out...
edit4: Giving up for now. The only thing I can conclude at the moment with certainty is that this isn't kernel related. It has to do with the SD card and the card not being able to keep up with the bitrate. The STRANGE part is that I have two cards, both of which ARE capable of keeping up with the bitrate when completely empty. I haven't been able to figure out what the variable is that causes the cards to stop keeping up. I completely restored my SD card's backup along with the entire DCIM folder and NOW it's working again, for no apparent reason! My theory is that there is an app running that accesses files on the card while the camera is recording which causes the total available bandwidth available for the camera to drop below what's needed for HD recording.
I would play with cache size on the sd card...for example...I've downloaded these apps from the market SD Booster and SD Speed Booster...both of them show the cache size of the SD Card on 4096kb this has to do with a tweak in Kernel or from ROM although I've suspected is kernel as I remember seeing a post from DrHonk talkin about he has a tweak for SD Card speed (I've checked my Init.d tweaks and I deleted the lines for SD Card tweaks just so I know what's creating this cache on my SD Card). Now if you download SD Tools from the market you can see your write and read speeds... my initial speed is really poor at 3.5 mbs on write at 4096kbs while I have a class 6 SD card and before tweaks the card stock speed on write was at least 6mbs...changing the cache to 2048kbs on either SD Booster or SD Speed booster gives me a better write speed than 4096kbs as oposed to the tweaks from Kernel or ROM...wouldn't hurt to try as when you reboot your device the cache on SD Card will come back to its original state from Kernel or ROM.
Without using any tweaks, my class 6 Transcend 8GB card gets this:
Antutu 3 runs, 11.3/3.3, 13.4/3.8, 13.1/4.8
Sd tools 3 runs, 24.2/7.5 24.4/8.5, 23.3/10.8
Related
Is anyone else having issues with their sd card corrupting? I have an 8gb class 6 transcend card and it has corrupted 3 times in the last month. I always unmount the card in windows before unplugging the phone. It seems to do it when I'm writing to the sd card from the phone.
The first time I noticed it was when I deleted a picture with built in photos app.
The next time was today when I made a nandroid backup before applying an update (theme). The nandroid backup finished and when I went to apply the update it came up with an error (I didn't reboot between the backup and applying the update). I reset the phone and the sd card was unavailable.
At one point I did have the card partitioned with the apps on one partition. When it corrupted I reflashed the phone back to 1.42 and left the apps on the phone. I went back to one partition and left it at that (fat32).
I don't know if I just have a bad card or something else is going on. I never had any problems with 1.41. However because it did it while doing a nandroid backup would that rule out the software version?
I would like to find a solution, as I don't trust the card anymore without backing it up frequently.
i've had it happen once (files names corrupted) but assumed it was down to the card as i had the same happen when it was in my N95, i've now bought a new card and i'll see how it goes.
When mine goes down, it seems like it kills the partition. When I open a disk manager I don't see a partition on the card anymore.
Hey axion,
Yea your card is pretty much dead... this also happened to me yesterday on my 4 gig card... yyour card will still work however reformatting or creating anymore partitions won't help bring it back.. for future update.zips or recovery boots upload your update files to your stock 1 gig card.. remember to always safely remove hardware with any card mounted to the to a computer..
YES - and not only have I had the same problems, it's with the same brand card! Transcend 4 GB Class 6.
My phone started having issues where I installed an application and it would act wonky, then if I tried to reboot it'd lock up into an infinite loop.
The last couple of times, I solved the loop by doing a fsck on the partition in GParted (booted into a GParted Live instance from a laptop using a USB stick). The problem reoccurs though, making me think there's something problematic with the card.
There's an app in the thread on the cheap 8 GB cards (of which I'm holding my recently received shipment . There's an app in that thread used to test write performance, but it does some crude error checking, and I had an issue when I did that test.
I'm going to do a partition clone and report back.
my dodgy card was 4GB Kingston, one interesting problem i had with it was video refused to play, i could read and write the file fine but android would refuse to play it and meridian video player would report the wrong pixel size, time and codec which had me confused all last weekend.
I'm also frequently having problems with my 8gb card (http://www.newegg.com/Product/Product.aspx?Item=N82E16820211341). Every few days I find myself firing up Ubuntu to fsck it and I always find errors. I often discover them when looking for a file on the phone (I usually do a find / | grep whatever and notice that I get "stale file handle" errors).
Should I get a newer/better card? I'm happy to pay more for a better one. I didn't know this brand, but it was the only class 6 I could find. If Sandisk made a faster card I'd get that, but I can only find a class 2. I have a 16gb Sandisk but it is only class 2 and therefore not good for apps, which is what I'm using the sdcard for.
If anyone can recommend a better one, I'll give it a try.
Does a 16gb class 8 exist yet? What about a 16gb class 6?
I just moved to the same card you have, mlevin - so I'll post back my experiences if I'm seeing anything.
I'm wondering if maybe moving the caches to SD isn't the greatest idea, since these devices aren't meant for continuous writes. If I have more issues, I might just move the caches back to the onboard memory.
giantcrazy said:
I just moved to the same card you have, mlevin - so I'll post back my experiences if I'm seeing anything.
I'm wondering if maybe moving the caches to SD isn't the greatest idea, since these devices aren't meant for continuous writes. If I have more issues, I might just move the caches back to the onboard memory.
Click to expand...
Click to collapse
Yeah, that worried me as well, so I moved my caches back to the main storage and only have app, app-private and data symlinked to the card.
If you are having problems after moving apps and data to your ext2 partition, you have to push the original init.rc and mountd.conf back onto the phone so you can wipe to card fully and restore it to the FAT32 file system.
I had a similar problem on my tmobile wing (variant of the Atlas which is a modified version of the Herald) running Windows Mobile 6 and Windows Mobile 6.1. I think it was also when I used the SD card as a place to store cache for PocketIE. Maybe that's the issue, using it as cache storage. (This is my theory, not something that has been confirmed.)
g1 sd card deletes itself
I am on my 4th sd card. I am not sure what is corrupting/deleting my data. I can copy over some music/video/pdfs/wtfevers and it'll stick around for awhile. Then BAM, music folder empty(had 1 gig of music in it). BAM, 1 of 3 video files corrupted. OH wait, now all 3 are gone. awesome. I keep a backup on my pc so I can copy it all back over once it goes south. I have the doodledroid drawing app on my phone and the folder will go corrupt - not allowing me to save an image until I delete the folder so it can reinitialize(create a non-f'ed up folder). Also, my picture thumbnails get f'ed so I have to delete that folder so the G1 can remake a new non-corrupted set. My PDFs disappeared about 3 days ago. Cards all formatted fat32. blah.
Frustrating.
I have root
kila-user 1.1 PLAT-RC33
Anyone else find a solution?
BTW, my sd cards were:
sandisk 2gb
sandisk 2gb
PNY 4gb (current)
Lexar 4gb
mlevin said:
I'm also frequently having problems with my 8gb card (http://www.newegg.com/Product/Product.aspx?Item=N82E16820211341). Every few days I find myself firing up Ubuntu to fsck it and I always find errors. I often discover them when looking for a file on the phone (I usually do a find / | grep whatever and notice that I get "stale file handle" errors).
Should I get a newer/better card? I'm happy to pay more for a better one. I didn't know this brand, but it was the only class 6 I could find. If Sandisk made a faster card I'd get that, but I can only find a class 2. I have a 16gb Sandisk but it is only class 2 and therefore not good for apps, which is what I'm using the sdcard for.
If anyone can recommend a better one, I'll give it a try.
Does a 16gb class 8 exist yet? What about a 16gb class 6?
Click to expand...
Click to collapse
mlevin: I have that card. It's been fine...until I believe the other day. I was running 5.01H w/ apps to sd and my battery had died so I charged it. Upon turning it on the android screen kept looping as though it wasn't mounting the card. Worse came to worse and I had to end up reformatting the card and starting from square 1. Now that I reformatted it, I'm getting "insufficent space" errors when trying to install paid apps even though I did everything right.
I'm wondering if it is the card.....
I've been using Dexter's froyo v1.3 for a week or two now, with basically no real issues. About 3 days ago or so, when I powered on my phone - you know how the sd card symbol appears in the status bar right when u turn on phone, it's loading sd card - so I see that symbol, but unlike how it usually is, it doesn't go away after a second (after it's loaded). So I pull down status bar and the icon says "checking for errors" and it doesn't go away at all. SD card just won't load. Oh I should mention -just remembered - I turned it on and I got "error with sd card, you may have to reformat" (or something like that) right before and then it just changed to "checking for errors" after I took out the sd card and reinserted.
Anyways, so my SD card isn't loading, right. I figured it might have something to do with the fact that I was using the SD card that came with it which is low class (2). I tried putting it in an SD card reader and put into my computer and it showed up and worked with no issues. But it just wasn't working on my XT720. So what I did was, I happened to have an extra micro SD card lying around (this one class 4) and I put it into the XT720. It worked just fine. That was a few days ago.
A few hours ago, I was using my camcorder on XT720. After using for quite a while I got "sd card not present, sd card must be present to use camcorder". I left the application and went to settings and my sd card was registered as present. I then went to gallery but I got the same "sd card not present" thing. My phone felt very hot at the time, which I assumed because I was using it for a while. I figured it might be an issue of overheating causing weird things. So I decided to power off my phone for a while and see what happens.
Upon turning on my phone, I was greeted with the SD card icon in the notification bar and upon pulling down; "Checking for errors". Now this new SD card won't load.
This is a really big issue for me, because I really need the SD card for stuff. Both SD cards seem to work fine in SD card reader on PC. Please let me know how I can fix this...
(sorry for making this so long, just wanted to have all info available).
....
Apparently this looks like a huge, long unresponded to issue for many people and not specific to Dexter's Froyo: http://code.google.com/p/android/issues/detail?id=2500
I'm going to try some of the solutions people posted, but problem seems unfixed for majority of users .
Gaaaaaah. My Android experience has been plagued with far too many issues....
What sucks is that if I want to flash back to stock to try to use warranty, I'm going to have issues if I need an SD card....
It seems you've already determined the issue, you have excluded the SD card(s) as the source of the problem. This leaves one thing - your phone is defective.
Flash it back to stock and send it in for service.
This issue has absolutely nothing to do with what software is on your phone.
R-D said:
This issue has absolutely nothing to do with what software is on your phone.
Click to expand...
Click to collapse
Yup, I've determined that as you can see in my edit... :-/
How can I flash back to stock without SD card?
syrenz said:
Yup, I've determined that as you can see in my edit... :-/
How can I flash back to stock without SD card?
Click to expand...
Click to collapse
You don't need the sdcard to flash a stock SBF with RSD lite.
I kept having same problem. If u are using move 2 SD or anything like that select auto and not Justin external I had to reformation my card about 3 times b4 I figured it out. Dexter posted somewhere not to use these apps.
similar issue with sd card
The only problem I've had with my sc card is that most of the time after my phone has been rebooted, the sd card will show up as not present once the phone has completely finished booting. Sometimes I can just reboot again and it will pick up on it but usually what I have to do is shut it down, remove the card, start it up and then once it indicates the sd card is not present I can reinsert and it loads just fine. I have an 8gb class 4 that came with the phone.
3rdstring said:
You don't need the sdcard to flash a stock SBF with RSD lite.
Click to expand...
Click to collapse
This is very good to know. Thanks.
easye420 said:
I kept having same problem. If u are using move 2 SD or anything like that select auto and not Justin external I had to reformation my card about 3 times b4 I figured it out. Dexter posted somewhere not to use these apps.
Click to expand...
Click to collapse
Nah, not using anything like that.
pillar2004 said:
The only problem I've had with my sc card is that most of the time after my phone has been rebooted, the sd card will show up as not present once the phone has completely finished booting. Sometimes I can just reboot again and it will pick up on it but usually what I have to do is shut it down, remove the card, start it up and then once it indicates the sd card is not present I can reinsert and it loads just fine. I have an 8gb class 4 that came with the phone.
Click to expand...
Click to collapse
I tried that once (it was something mentioned in that link I posted) but it didn't work. I'll probably try it out again before attempting to use warranty.
I would also try reformatting the sdcard, just because Windows can read it doesn't mean there aren't issues with the card.
K, so I put it in SD Card reader and into PC and began transferring all the files on the card to a new folder. During this process I got a pop-up a bunch of times telling me specific files were corrupted and unreadable and couldn't be transferred (mostly music filer for the most part). I then formated the card to delete the remaining corrupted stuff. Now put into phone and it registers as being there and now things like camera are working.
Gonna have to see how it fares when stuff are actually on the card, but for now things are looking good.
Thanks for the help guys, will update if I encounter further problems.
EDIT:
And after transferring some music on to it, it still seems to be working fine. Needless to say, I'm quite happy I don't have to go through the hassle of flashing stock and then trying to get a device exchange for warranty...
Though I am slightly worried that the device itself will corrupt things again (since my other SD card also worked fine for a few days). But I did also do a complete factory reset so perhaps there was some app causing issues that no longer will... Guess we'll see what happens.
I had problems with my stock (Cincinnati Bell) SD Card doing a similar thing -- showing up as no card inserted. Sometimes rebooting did the trick in fixing it. Then my phone fried and quit working. I thought it was related.
After I received a new (refurb) from Motorola as a warranty replacement, I used that same card and was getting the same error. So I upgraded to a new 32GB class 4 card and still got the error. I upgraded to Dexter's ROM and it still continued. I'd keep rebooting (three to four times sometimes) and eventually it would go away.
Then I decided to pull everything off the card, reformat & give it an ext3 partition using the method in the video tutorial in these forums. I haven't had the issue since -- it's been about a week now.
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.
So does anybody has had this error on their phone? Sometimes when I want to take a pic it shows a light blue/cyan screen error, and the picture doesn't get taken. The error says:
Failed to save photo to SD card (error code=2)
The following are fixes for this error:
- make sure your SD card is inserted
- remove the SD card and re-insert, then launch Camera ZOOM FX again
- reboot and try again
If this problem continues, please mail [email protected]
Somebody knows what is going on?
Thanks.
I'm using the same app, but haven't had any problems since switching to a Class 4 SD card (due to the known issue w/Class 10 cards on this device). Can't seem to use video with it though, every time I try to switch to video it force closes.
armyengineer51 said:
I'm using the same app, but haven't had any problems since switching to a Class 4 SD card (due to the known issue w/Class 10 cards on this device). Can't seem to use video with it though, every time I try to switch to video it force closes.
Click to expand...
Click to collapse
The weird thing is that if I do a factory reset, then it works fine, but as soon as I begin to install some apps and play around, then it happens again.
Somebody else has another input?
I was having the same issue I also did a Factory Reset then pulled the battery over night and have not had the issue since not sure if it was just a glitch or what.
I just downloaded Camera Zoom FX and got the same thin I took out my sd card and tried the app again, same response. I bought a 16mb class 6 sd card at the suggestion from here on what would work. The camera is a disappointment with the stock app, hope I can get FX working.
Sent from my MB865 using XDA App
So far no problems with Camera Zoom FX.
OS versions 2.3.5 or 2.3.6.
SDcard is a Sandisk 16G class 6
Any news nahuelarg86 on your situation
I had the same problem with this app. The standard camera app would appear to save the pictures but when you would go into MyGallery, no picture would be there although you wouldn't get an error message like CameraFX. I found this information somewhere else, but if I went and looked at the dcim directory on the sdcard there would be corrupt files in the Camera subdirectory. Deleting these files would then allow pictures to be saved. I was using a class 10 sd card, but switching to class 4 didn't fix the issue. I did the OTA update to 2.3.6 hoping this would correct the issue. This made things worse regarding the camera apps. Every picture file for news pics appeared to be corrupt. I then did a factory reset to 2.3.6 and I haven't had a problem with the camera apps since.
Well, I did a factory reset and I didn't have the problem again. But, I began to download some apps and play around and then I got it again... I deleted all the apps that I installed last time in hope that it would help, and it did. For me it's a pain in the a$$ to do factory resets because of the setting up, re installing of thing, etc.
I still don't know where the problem might be. Seems like it's related to space or the resources an app uses, but I know of the problems of SD cards and everything is stored in the phone's memory. So I have no idea...
I know this thread is old, but it was the first hit on google, so maybe someone else will need the solution: Most of the times the save feature on external sd card is corrupted because of rom change. Backup your data of your external sd on your PC. Then go in android under settings < "space" (Speicher auf deutsch) and format the external sd card. Afterwards you should be able again to save your pictures on your external sd card, because the card is now perfectly formatted to your rom....
Hi, I have the phone of my signature, a Samsung Galaxy Core 2 G355HN.
Everything works fine except the camera, but just sometimes. This is what happens. I'm chatting via WhatsApp and I try to share a picture of something. I tap on the camera icon, focus an object and press the middle button "take picture". When I press it, there's an error that says "Unkown error occurred", and I'm sent back to the chat screen. I try it again, press on the camera icon, focus an object, and the same error. Then I open the stock android camera app, and the same happens. It seems to be an error when trying to take the actual picture, like if suddenly the camera couldn't write data or had no permission to do so.
The only way to solve this is to reboot the phone, and then everything works fantastic. I've not found any method or something like that to activate this bug or error. It seems to happen randomly.
What can be causing this issue?
I've thought about some potential sources of the issue:
1. I have the phone rooted. May be the camera app suddenly and mysteriously loses permission to write data on the microSD card. May be SuperSU doesn't grant it access.
2. I have installed Xposed framework and the GravityBox [KK] module. May be that is causing this error.
3. A problem with the microSD (It's a Samsung EVO 64GB, and it works like a charm, but who knows...)
4. My stock carrier's ROM is faulty, though I don't think that's the case cause everything else works great.
5. I also have installed ES File Explorer, and one day happened one weird thing. Like a week ago I was trying to solve this problem by closing and restarting system apps (I mean WhatsApp, Camera app, and whatever I've found could be related in taking pictures), cleaning cache, dalvik cache, etc. Still, I opened the camera app, and when hit the button, the problem still appeared. I remember I opened ES File Explorer and went to the photo folder, then go to the camera app and the problem was solved. This is the only time I've solved the issue without restarting. Nevertheless, this bug has happened like 2 times since then, and I've tried to do that very same process, and the bug didn't got fixed.
Remember that this only happens sometimes randomly, and if I reboot the phone, the problem gets solved (until it occurs again).
Problem solved:
http://forum.xda-developers.com/gal...ing-photos-t3109320/post62979839#post62979839
Try to go to SuperSU setting and swipe down till u find the trust system user and check it. Tell me if this work
Sent from my GT-I8262 using XDA Free mobile app
All right. I have that one unchecked right know, and of course I can take photos without a problem. But when the error appears, instead of rebooting, I'm gonna check that option and activate it.
One question: should that question be activated by default?
I've been using this smartphone for 6 months and I've never activated it.
I've edited my main message:
5. I also have installed ES File Explorer, and one day happened one weird thing. Like a week ago I was trying to solve this problem by closing and restarting system apps (I mean WhatsApp, Camera app, and whatever I've found could be related in taking pictures), cleaning cache, dalvik cache, etc. Still, I opened the camera app, and when hit the button, the problem still appeared. I remember I opened ES File Explorer and went to the photo folder, then go to the camera app and the problem was solved. This is the only time I've solved the issue without restarting. Nevertheless, this bug has happened like 2 times since then, and I've tried to do that very same process, and the bug didn't got fixed.
Click to expand...
Click to collapse
Card error
Your GC2 doesn't support 64GB Card, like mine. That's the problem !
StratOS_HTC said:
Your GC2 doesn't support 64GB Card, like mine. That's the problem !
Click to expand...
Click to collapse
What?
The Core 2 does support 64GB, that's 100% guaranteed. I've had no problem with my card.
Anyway, if it did not support 64GB cards, it'd have no sense that this issue happens only suddenly like once or twice a week. But as I told you, this device supports 64GB of microSD, that's what Samsung claims in the official GC2 specs.
rambomhtri said:
What?
The Core 2 does support 64GB, that's 100% guaranteed. I've had no problem with my card.
Anyway, if it did not support 64GB cards, it'd have no sense that this issue happens only suddenly like once or twice a week. But as I told you, this device supports 64GB of microSD, that's what Samsung claims in the official GC2 specs.
Click to expand...
Click to collapse
This statement Samsung never stated. Couse it's wrong and it doesn't support fully !
Have written to Samsung support and they have stated that they intend to fix it in future development, they stated that this is kernel related.
I have tested mine G355HN on stock OS with class 10 SDHC 64 GB on exFAT partition. The resoults were identical couple of times. I were unable to copy/access some files on SDCard.When I put a card on comp's SDCard reader there werte errors on exFAT.I also got new identical card on ebay for free ( I bought it there ) and the things with new card happened again, so now I'm on 32 GB and those things never happened again for now.
Regards
http://www.gsmarena.com/samsung_galaxy_core_ii-6331.php
MEMORY Card slot microSD, up to 64 GB
http://www.samsung.com/in/consumer/mobile-devices/smartphones/others/SM-G355HZKDINU
External Memory Support
MicroSD (Up to 64GB)
http://gadgets.ndtv.com/samsung-galaxy-core-2-1738
Expandable storage type microSD
Expandable storage up to (GB) 64
http://www.mgsm.pl/pl/katalog/samsung/galaxycore2/
microSD, microSDHC, microSDXC (do 64 GB)
There's not a single webpage that claims this phone only supports 32GB. And Samsung's official page claims up to 64GB. So... yeah, this phone supports 64GB microSD cards, unless they are all lying about specs, even Samsung. Anyway, imagine that It wouldn't support 64GB cards:
Then why when I put the microSD card, the phone recognizes all those 64GB and there's no error message or unsupported message?
Why I can read and write data from the microSD card without any single problem, except this one, of course, that remember, only happens twice a week maximum. The rest of the time, it takes photos without any single problem.
h.d.z said:
Try to go to SuperSU setting and swipe down till u find the trust system user and check it. Tell me if this work
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
And that's the solution! :victory:
It has happened now, the "Unkown error occurred" bug. I went to SuperSU, checked the trust system setting, and go back to WhatsApp to take a photo, and it worked.
Thanks!
OK, I've tried to do this trick again, and it has not worked. What the hell?
I've had to reboot the phone, cause otherwise the error was not gonna get fixed.
Weird. What I did when the error occurred was go to SuperSU, untick trust system, went back to the camera, still the same error, went back to SuperSU, tick trust system, and the error still persisted.
OK, I think I've finally found out what's happening.
As I have a 64GB microSD card in this phone, I obviously set the download folder and camera folder in the Samsung EVO microSD card, that even was recommended by the default camera app.
This issue has been happening always, I thought I had fixed it when did the SuperSU option tweak, but I was wrong. It fixed it the first time, but it was pure causality. The issue is related with using the microSD as the camera picture folder. Since I've set it to the internal memory, the camera error has never happened again. So... something's wrong with the microSD support or the camera app. Besides this, the microSD works perfectly in every other aspect, this mobile recognizes without a single problem the 64GB and all the rest of the stuff is 100% working.
May be, as StratOS stated, there's something wrong with the kernel, or with the camera app. But he was wrong when he said that this mobile does not support 64GB, cause it does.