Related
ive been experiencing some problems with my camera software.
here's what happened.
on christmas i got a 6gb microSDHC card, i was using Duttys TouchFlo 7 rom, and it was working great. said i had like 3000 something pictures to take. then i upgraded to duttys DuelTouch rom, as well as the new camera software update, and i only have 150 pictures to take (and the number keeps going down as i fill up my storage card bit by bit.). but when i go to my memory options it says i still havr 4.1gb remaining, so whats wrong here? i put the old version of the camera software back on but it didnt fix it, and i put the newest version on, and still didnt fix it.
i really dont know what to do now, has anyone else experienced this?
ok i fixed it, i just exceeded the limit and now i have abouy 7000 pictures to take.
how did you fixed this problem?, I'm having the same one!!!
First of all thanks to all on the forum for all the useful tips and tweaks.
I finally took the bold step of my first flash two days ago to Dutty's latest Rom.
As he advised I have slowly added programmes and tweaks to make sure there were no bugs. Last night I was playing around with different wallpapers after a day of the phone being stable. Waking up this morning I found a lot of my tweaks for the today screen had reset themselves. Using file explorer i tried to open my storage card (I kept all the cabs i have been using on it) and it wasn't found. I took i out and have tried to open it through my laptop and it keeps asking to 'insert card' i.e it can't see it either. I tried a hard reset on my HD to see if it was anything I had installed and still nothing!
I have most things backed up on my PC and yesterday set up microsoft myphone so hopefully I haven't lost anything...BUT. Has flashing caused this or is it just coincidental that my storage card has gone tits up!
many thanks in advance.
P.S Off topic. has anybody else found that the Virgin advert causes a stuttering effect when scrolling down a page?
Hi Mate,
take a look at this link
http://forum.xda-developers.com/showthread.php?t=506560
Should explain all, it looks like when you upgrade to one of the newer roms not based on the 1.14 it kills the SD card, you could try formatting it again..
Happens quite randomly , so ...
Bloke
Cheers Bloke
Although the cause doesn't seem to be very clear. I flashed my HD without the SD card in. I have a sandisk card. It came with the phone but it was a replacement phone so not exactly bundled per se. (after getting the phone on an upgrade last Dec with Orange actually paying me a fiver for it, I lost it/had it stolen after owning it a month and had to then fork out £160 for it )
Sods law that i haven't been backing up my SD card as the majority of it was music that i have on my laptop anyway.
Thanks once again
I've never lost any info on my SD Card from flashing any roms, and I've flashed a lot. Even when going from 1.14 roms to 1.59 roms. No probs
However I have heard others have had similar problems and unfortunately only remedy was to format card. Once formatted problem shouldn't arise again
So to update:
tried out spare sd. Not a problem although only looked at it rather than file swap etc
Hard reset: still didn't find card
flashed stock 1.14 rom. Had colours go strange on screen whilst first installing but then touch flo started and colours as norm. Put SD card in and it wasn't found. Soft reset with card in and once booted funny colours came back (all kind of negative and opposite original colours, kind of cool but obviously not good). Still not finding card. Took card out and soft reset, all good and colours back to normal.
So, it seems, I will have to format. Bye Bye data!
I tried to look at the card from command prompt on my PC (xp pro) and it still couldn't see it. Muchos corruption me thinks. Not sure how I am going to format it now?
I hope HTC will look into this and release some sort of fix. Unless they know it's a hardware fault on the card reader and realise it will cost a small fortune to fix everybodies HD not to mention the bad publicity.
Okay, maybe not the most common method to do this, but when I had this happen to me, I also couldn't format the card anymore in my PC (Vista). What I did wat put the card in an old Samsung phone I had lying around, and the phone initialised the card for itself. After that it was also readable again on my PC and in my HD.
Since this happened to me I always take out the SD Card if I flash my phone. Just to be on the safe side.
Ok, so everything was working fine yesterday. I woke up this morning and decided to play a little 'world of photo'. It FC's, so I mess with it for a little bit before just trying to open my normal camera. When I try to open my camera, it puts the screen in sleep mode, so I have to hit the power button and unlock the screen like normal, then it gives me the error "Cannot connect to camera".
My phone is rooted and flashed with the latest Cyanogen business, but like I said, nothing was altered, updated, downloaded, etc. My camera just stopped working. Anyone have any thoughts or ideas? Really hoping to get this resolved without having to contact HTC, as I'm sure the unlocked bootloader screen will cost me a small fortune.
If I open an alternative camera app, it opens, but doesn't work. I can back out and then go to my default camera and it works until I close it. Then it won't open again without having to go through the steps of opening the other app, etc.
I'd try a nandroid restore.
Tried it already. Tried restoring back to original, wiping, everything else. Nothing worked. Camera wasn't working all morning, now all of a sudden it's working again. Guess I'll just count my lucky chickens and chalk this up as a win...
Well, my happiness was short lived. Still having the same problem. I'm really not sure what exactly it could be. But the fact it worked the one time today gives me hope.
also having this problem. tried a nand backup and also wiping and re-flashing the gapps and the cm-5.0.4.1 update.. still nothing
it seems my camera went bad somehow, tried even flashing the stock rom, nothing... i'm calling htc, crap my phone is unlocked.. wish me luck.
update: yeap, im getting a replacement. they put $529 on hold on a credit card, send you the device and once they get the "damaged" device they release the funds... meh..
Hey velazcod, you think we can get an update on his this worked out? I'm having the same camera problem and I too am bootloader unlocked. I'd like to hear how HTC handled your unlocked device.
sorry for not posting a status before... so here is what happened:
- Called HTC and they didnt have any issues replacing the phone since the issue seemed to he a hardware issue. They have been nice about this, depends on the hardware issue, I guess if you burn the motherboard they will probably get *****y.
- You can send it to get repaired or replaced, both are in warranty, unless they find some other issue (water damage, etc). However, if you decide to get it replaced they would take your credit card, and put $528 on hold for a few days until they get the original phone back. They dont actually charge it to the credit card, just an authorization, it all depends in your bank, for example my bank (chase) put the money back in my account after 5 days.
- Anyway, I got my "new" N1, and I double checked everything before unlocking the bootloader and doing our stuff. The phone was crap, it was slow and the sticker on the battery cover seemed like it was removed, maybe a refurbished unit. I called and *****ed about it, and they said I needed to send my original phone back, and then later on request another replacement. I kept *****ing because I could live with a bad camera for a few weeks, but not with a slow phone
- Anyways, in the end they allowed me to send back that refurbished unit. After a few weeks i had no response from them and I had to call them, a day after i got my new phone, this time it was good, so i unlocked it, did my thing, factory reset the original phone and sent it on its way.
- It all seemed good for a few weeks, until i got a call from HTC saying that I needed to pay for a repair fee ($60 something) because they had found the problem had been user damage. the girl had no idea how to back that up, and i kept saying that i had never drop the phone or broken the camera in purpose (which is true). She said she was going to escalate the issue and I would get a call back. Still waiting.
In the end I got my new phone and we are all happy, but be careful, I love HTC but don't let them screw you.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
$60 isn't that bad. I would be interested in exactly what they found.
yes that isnt that bad. and i would pay it no problems if it really was my fault. but really, i take care badly of my phones and i had never drop or have done anything to my phone that would cause this camera issue.
besides, the girl that called me had no idea what really happened or what they found, when they call me i will post the info here.
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
moto211 said:
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
Click to expand...
Click to collapse
Well, keep in mind that it could be a placebo effect, and you think you are fixing it by fiddling the SD card but its not real.
The reason I tell you that is because, when the issue started happening for me, I would get that error randomly, and then it started happening more frequently until it totally stopped working.
Also, the Camera app not detecting the SD card gets an error when you try to take a picture and it actually says the specific SD card error. Try taking the SD card out and try it out, you will get a visual of the camera on the display, but when you try to take the picture it gives out the "SD card not detected" error... on the other hand, you might be experiencing something totally different.
This error "cannot connect to camera" also comes with the camera app not loading completely and visual of the camera not loading on the screen. Also try loading up the Barcode Scanner, you should get a similar error and no visual of the camera.
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
moto211 said:
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
Click to expand...
Click to collapse
I see what you mean. Makes sense, keep us posted.
Update:
So, although the fix I previously mentioned did work, I started having other issues that indicated that the actual camera hardware was failing. When I would start up the camera app the camera image displayed on the screen started showing color distortion. Sometimes it would do that and sometimes it wouldn't. I noticed that if it wasn't distorted, I could lightly squeeze the sides of the phone and the image would become distorted and would not go back to normal after I stopped squeezing. I figured that indicated hardware issues but decided to try a low level format on my memory card just in case it was an issue of bad blocks on the card. The format didn't fix anything. A few hours later, the camera died and never came back. I started a ticket with HTC for an advanced replacement. I received my new phone on Friday and am sending back the old one today. I restored it to unrooted factory ROM and recovery image. I will keep you guys posted as to what, if any charges they try to stick me with.
moto211 said:
Update:
So, although the fix I previously mentioned did work,......
Click to expand...
Click to collapse
crap, that's what i thought. that sucks. keep us posted :-/
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
moto211 said:
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
Click to expand...
Click to collapse
Good to hear that.
On my case, I was never contacted again by the "escalated rep"... but I just checked my ticket/case and it seemed to have been closed, so I guess good news.
Hello Guys,
I am having the same problem as you both had. Í am seeing the same symptoms such as not able to run the camera app. My phone screen goes blank when i try to open the camera app and the bar scanner program says it cannot connect to the camera and that I might need to restart my device. I have tried to use previous roms and removed the sd card but nothing seems to work. I am wanting to send it in for repair but I wanted to know what else I should do to my phone besides reflashing the stock rom. Did either of you have the amonRa recovery program and how did you remove it if you did. Is there anything else I should do?
Thanks.
I got the original shipping rom package from modaco and renamed it PASSIMG.zip and flashed it from the bootloader. It restored everything to stock...recovery, radio, and os.
Hi,
I am using an un-rooted Nexus One phone with Froyo (2.2.1).
The camera has stopped working unexpectedly.
Whenever I start the camera app, it gives me the error:
"Activity Camers (in application Camera) is not working"
It gives me the option to wait, force close or report.
If I select wait, it just hangs in there and pops the above msg again.
If I force close the app, and try to start it again, I get the error:
"Cannot connect to camera"
The phone did not fall down and is always handled properly.
This happened all of a sudden.
The last thing I did with the phone was to copy songs to the SD card.
I have factory reset the phone twice and formatted SD card, even swapped SD cards, but no luck yet.
I am based in India, the phone was bought in the US, I have no warranty.
Any help will be appreciated.
Thanks.
Sorry but I think your camera just died it is possible for the camera to die without any physical abuse but it is uncommon. The only other thing I can recommend would be to root and install a custom ROM (or at least a kernel) and see what happens but I don't think it will fix it.
Resolved....
Thanks Dude Random21..!!
Actually, I just resolved the issue about 30 mins ago.. Was downloading the apps and restoring its state as it was before I had factory reset it.
Well, after doing everything related to software to fix the issue, I concluded that it might be a hardware issue.
So, I started to search for threads involving camera hardware issues.
I took hints from the following post:
Google "Camera on my Nexus One not working - no flash either...all apps that use camera also not working - Help!?!?! " and you will be lucky..
(I cannot post links as I am a newbie)
Saw all videos on youtube about nexus teardown and just finished doing it.
I checked all the connections/internal wiring on the phone and once done, rebooted the phone and it worked..
Unfortunately my phone received a couple of scratches along the way, so others should be more careful about it.
Thanks for your help.
--- sent from my nexus one
No problem, I do what I can to help out. And good for you for having the guts to fix your nexus one's hardware cause I'm pretty sure that if I had an issue like that I would't have the guts to tear it down myself even with ifixit.
Remove (renaming is better) the DCIM directory from SDCARD. It is probably a corrupted (or incompatible with 2.3) file. After that, the camera cames back to life, then you can copy your “Camera” directory to the new DCIM directory created by your phone.
HTH
Hi all
Ever since upgrading to 2.3.3 I've been having random freezes that usually end up in needing a battery pull or pressing down on the power button until the phone reboots itself. This is with Darky's 10.1, although I don't think it's related to the "Darky parts" of the ROM itself, but something more to do with the OS.
Also, I've felt that the phone sometimes slows down. It doesn't feel like the original lag on 2.1, but rather feels like something's eating up CPU power. This will happen on ANY application, and even when moving through homescreens on TW Launcher or ADW Launcher.
Another thing of note is that it seems to be the UI or input process that hangs or dies or something. Because whatever's running keeps running I just can't make the phone respond to touch or any of the hard buttons. For example, today I was playing Age of Wind (sweet game, check it out) and after like 10 seconds of the game stuttering, the phone stopped responding, but my ship just kept going forward and the other ships were trying to keep up with me. Sounds and music kept going. And after 30 seconds of "inactivity", the screen went to sleep. As you can see everything's normal except there's no input.
So what I'd like is for ideas on how to fix or figure out what's wrong. I'm somewhat tech-savvy so I wouldn't be scared of using adb or some other debugging tool. So far I've not been able to figure out what's wrong because all the logs start over whenever I reboot the phone.
So, any ideas? Any additional information that would be useful?
Edit and update: I've changed the title because this has already happened on different custom ROM's, including Darky and Criskelo.
I have now tested for 5 days on Criskelo's ROM (based on 2.3.4) and it will happen also. So far what I've noticed both on Darky's and on Criskelo's ROMs:
- The phone will work perfectly for about 4-5 days
- On the 4th day it will start stuttering and lagging. That's when I know it's very close to locking up.
- On the 4th day it will maybe lock up once in a day
- After the 4th day it will start locking up up to three times a day
- The lock-up is at the UI level. Applications will keep running, it will ring if you call it, notification sounds are still alive, the screen will turn off normally after 30 seconds or whatever timeout you set up. But input is totally dead.
- When it locks up, both soft-buttons will light up and stay lit.
Possible causes:
- Something related to USB storage or SD card storage. Someone mentioned that it might be caused by the "fast media scanner". It's possible, because on one of my many tests, instead of reinstalling an OS, I formatted the minisd, the internal sd and phone storage and the phone was fine for 4-5 days and then it started doing screwy stuff again. This reinforces the theory that it's something to do with storage. My guess is the OS itself starts degrading the filesystem or handles or something. And my suspicion is that it's something in the /system/dbdata or /cache partitions, not the sdcard or external sd cards. Impossible to know because I have no idea how to debug using adb and nobody has given any ideas on this.
- I'm starting to suspect the BLN support in the kernel. I have BLN turned off, but I'm not so sure.
Hi,
Sorry don't have any answers, but am having the exact same problems on Darky's 10.1. Except I have a TouchWiz4 Port + Galaxy S II Icons.
Hopefully someone will know of this issue! Its starting to annoy me!!
Cheers,
Sunny
Tell me something, when you installed Darky, did you restore your apps via Titanium Backup? Did you select "Restore apps + data" or just apps?
I'm in the process of reinstalling Darky's from scratch, see if that works. If not I might go back to 9.5 or try Criskelo's ROM.
Thanks
Hi,
Nope I didn't backup or restore any apps. My data is all on my SD card and I just reinstall apps.. I came from DebusROM G1.
Thanks,
Sunny
Maybe a factory reset (do it in recovery) would help?
I actually did a factory reset before installing.
@sundazetoo: Do you have Voodoo lagfix enabled?
Last night, while in the process of reinstalling Darky's ROM, I disabled the lagfix (converting to RSF) and after almost an hour i decided to pull the battery. Then when I rebooted again, it went through the conversion process, finished in 2 minutes (wut!) and an error displayed (it couldn't mount some partition, one that I know is not critical).
So I'm suspecting a filesystem problem.
I already installed and DO NOT have Voodoo's lagfix enabled. I also did a complete wipe and restored my apps without data. So far it seems fine but it's only been a few hours.
@Lunchbox115: I did the factory reset when I installed too.
@ferparedes: Yep voodoo is enabled. I am now running on the stock launcher that came with Darky's 10.1 and it seems to be running a lot smoother. I was running a TW4 port so that may have been my problem!
I will monitor it and let you know how it goes.
Have you tried clearing the data / cache for the launchers you are using? That seems to fix alot of FC issues for apps for me.. I guess no harm in trying anyways?
2 days in after reinstalling.
Voodoo EXT4 lagfix NOT enabled. Phone is pretty snappy and I've haven't had any more freezes. I think it was either a bad EXT4 conversion or the lagfix itself was causing it. Anyways, since the phone is pretty fast I'm leaving it with RFS lagfix only.
One thing of note, though. I'm running stock GB launcher atm, because ADW was giving some problems.
Yesterday ADW Launcher *died* and although the phone was working and responsive, the launcher never came back. The result was that when I pressed the home button nothing happened but a blank screen. The power button worked, though, so I was able to do a clean reboot and switch to Launcher.
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Same again
I get these issues too. I seem to get them RFS and ext4 (I think - mostly its been ext4 though). Often get a delay on the keyboard. Its driving me a bit nuts but I am reluctant to go back to Froyo just for this (I hate having to restore all my user names and passwords).
Silly thing is I cannot recall if I got in when I tried Gingerreal (on Darky 10.1 now).
Would love to see thoughts and theories too..
G
UPDATE
After almost 2 days of totally flawless operation, I reinserted my 16 GB Micro SD card with all of my stuff in there. Among many things:
- Audible audiobooks, along with bookmark and "furthest listened" data
- Music, playlists. All created by TuneSync (which I use to wireless sync music and playlists from my PC's iTunes)
- Dropbox download folder
- Photos and videos taken with the phone
- Some other files not associated with any app
2 hours after doing this, blam, the phone locked up again requiring a reboot. So I removed the Micro SD and when I got home I backed up my photos and videos on the PC, reinserted it in the phone and formated the card. This was last night.
So far the phone's working fine.
My current theory:
The Micro SD card I originally bought for the phone was an 8gig. When I got the 16 gig one, I just copied everything from the 8gig onto a folder on the PC, then copied everything over to the 16 one. This might've broken something.
After going to Gingerbread, it's possible that the way some applications look for their data (for example, Audible) changed but when encountering the same data (that was copied over from a windows folder on the PC) it might've generated errors which in turn put the interface into a deadlock.
My strongest suspect is Audible. After installing Darky 10.1, the app just chugged away remembering all my farthest listened to data, all my audiobooks were visible, etc. After reinstalling (and removing the Micro SD) I had to redownload some, but it still remembered where I was and didn't have to reactivate the device. Now, after formatting the Micro SD, I've had to redownload everything, it didn't remember where I was on each audiobook and I also had to reactivate the device.
If the phone doesn't lock up during the next 4-5 days then I'll conclude that errors on accessing the Micro SD by some app was the cause.
sundazetoo said:
Interesting, I dont seem to have the same issues with the voodoo lag fix.
Also I am now using ADW Launcher EX and have not had any issues. I think my problem was the TW4 port.
Click to expand...
Click to collapse
Yeah I actually don't think ADW launcher is causing this particular problem. But in a different problem altogether, it did die and in this case required me to do a reboot, albeit a clean one. But if it gave me this one single problem than I'm inclined to stop using it. I don't want the phone disabled for the 3-5 minutes it takes to boot up if I need it in an emergency (it's a phone first and foremost, after all)
tw4 is an EVIL for SGSi9000 imho... because almost everyone have problems with it !!! so just use another Launchers... LauncherPro, Launcher EX (my favourite) but not TW4 )))
I tried to fix with a reinstall of stock jvp and then went to F1 v8 jvp rkm but I also formated ext_sd card as suggested here (and deleted audible application which I was not using.
So far so good but it's only been an hour...
Sent from my GT-I9000 using XDA Premium App
Definitely something related to sd card. Everything is screwy now but less so with the sd card out.
Anyone find any solutions?
I was getting double boot screens and freezes on the dialer. Realized it was the sd when my backup would not load.
Sent from my GT-I9000 using XDA Premium App
Had this happen to me today,
I had the phone boot up and it would get to the lockscreen, then media scan, then it would lock up, only a battery pull would turn it off.
Tried booting without the External SD and it didnt occur, hmmm
Put the microSD card in the card reader on the PC, and performed a scan for errors/fix bad sectors, it didnt find anything but i put it back in and it goes fine now, im sure its the external card.
related info
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
It did it again with the micro sd card out. So today I reformated the internal SD storage (usb storage) and will see how it goes. If this last attempt fails I will either go back to froyo or try another ROM.
But I do think it has something to do with one of the SD card storage.
gfacer said:
Found this thread that seems related;
http://forum.xda-developers.com/showthread.php?t=367912&page=3
Trying the chkdisk utility now...
Click to expand...
Click to collapse
Should be fine
More things to try
Looked at my rom page (F1 JVP) and noticed that V8, which I have now, had the faster media scanner as does Darky's 10.1-which is not getting updates often now it seems. Well the faster media scanner only lasted 2 days until V9 of the F1 rom when the delevoper removed it. My guess it that it was causing issues.
Leads me to wonder if that might be causing the corruption in the first place or at least a contributing factor.
Also read some threads at google about similar issues across a whole wave of devices and one person there mentioned H2testw utility to test the sectors of your SD card. It sounds like cheap ebay sd card and larger SD cards my have more issues (mine is a 32gb). It is best to format and then test with h2testw but I decided to run just on the empty parts of the card and decide from there.
G