Hello all!
Yesterday, while trying to load a couple files and install a program, my Hermes kept locking up. Found out my Card was almost full. (Lexar XD 2Gb)
Turns out somehow during that process, it correpted two folders on my Card, the Programs Files and the Live Search Folders. I have no access to those folders (can open them, but cannot delete files) and programs using them like AvantGo will not work.
I tried deleting both on the Device itself, then on the PC (2 pcs, work and home) through activesync, and finally putting the card into a Card Reader and trying to access and delete from my PC. Nothing worked.
I then tried to Fdisk to find errors, but Fdisk would report it couldn't do it after 10 secs. Tried the reboot and check also, no go.
So it looks like a few folders are corrupted. Anyone know of any (preferably free) software that can fix this issue. Otherwise I'll trun to Frys and get a new card, but it has a lot of stuff on it and I'd rather not have to do that at this time.
I should mention, most of the folders work fine, all my music, pictures, file back up etc work ok. Its just those two upper lvl folders and anything inside them. Wierd!
Thanks!
Do not know any software which can fix the issues you described.
But you mentioned that you are going to buy another disk.
I don't believe that's necessary.
You should be able to format the disk. Usually formatting the disk should clean all the badly recorded parts on the disk.
You might also want to invest in a good back up software in the future for when similar occasions happen again.
Well, a quick google shows all sorts of software out there, most of it more for saving stuff (mostly image related) but others that are supposed to fix corrupted sectors supposedly, looking for peeps in here that have run into same problem.
Been planning on a new card at some point, 4-8gb would be nice, just wasn't planning on going that way quite yet.
And I back things up, but you cant back up installed programs, you have to re-install them. Like I said, all the Data and stuff is fine.....
A piece of software called DelinvFile might help. 15 day trial available.
Ok... I have been a member for awhile, reading this and that...
I have been using WM based phones ever since i could remember (minus a small sidekick phase). So, when I found out that WM7 wasnt avail for my HD2... I was quite upset.
I decided to take the plunge and try Android for my SD card. W O W!!!!
Very fast, & functionable. I have stayed away for installing roms and such because of their instability. But this is absolutely beautiful.
Now i haven't updated to the new release that came out this morning, and was wondering if i should because i have been having some small issues.
1. When running WM6.5 since the install, i have had a problem with messages updating on main screen, don't know if it is related or not.
2. This was a fresh install of WM6.5 along with an SD card format. I am not allowed to store any info on card anymore. It's a 16g card, and I don't like to waste space. I no longer have a place for my tunes..... not cool. Not to mention can't store pics, and all the movies I burned via DVDFab.
3. Now I have read that there is a way to 'partition' my SD card, but there are so many ways to do this. I would like to do this with the best way/program so i dont fry my card. Link to the most stable way of doing this would be appreciated.
4. Now as impressed with AmeriCanAndriod as I am.. I have a question about the lockscreen... It is NOT about it's size/fullscreen as i have read on here... But when i walk away and it appearantly locks itself, it goes BLACK. the buttons on the device still light up, but screen will not activate and i have to end up pulling the battery. I have read that this is not advisable since shutting down is where the OS saves it's data to the SD card itself.
Yes, I am as green as it comes to this, but I am not a complete fool. I do try and look up issues pertaining to my problems. I can strip a PC down and rebuild it again in minutes, but phones are new to my tinkering. I love my HD2, and love all the things I have read I can do with it.
I understand that the forced close issue has been rectified in the build released this morning. Can this be confirmed????
Also will I be able to save the data.img and restore my apps and settings i have installed if I want to update to the new release?
Partitioning the SD... Will it cause me to reformat card and have to re-install Andoid on phone?
LASTLY..... Thank You to the AmeriCanAndroid Tean for making a beautiful OS that can easily be installed. Having a dual boot system is perfect for me. All the power and funtionabilty of WM & all the fun of Android. You couldn't ask for more. All the talent in this OS truly shows in this streamless, beautiful, user friendly system.
~Bdwlf2~
First off, this is not the place where to post. You should post in the builds own thread located here. Second i know that black screen happens to me as well but what i do is leave it for about 3 min on standby and its cleared up by then. Make sure to have the latest build from the thread mentioned above. And yes you will be able to keep the same data.img from the previous release unless specified. Partition yes you will format but simply drag and your Android folder to your desktop and once you're done drag it back in simple.
Thank You for the reply. I was going to post in the AmeriCanAndroid thread, but since this is my first post. I had a popup tell me I had to post HERE, instead of that thread until I reach 10 posts.
If a Moderator wishes to move this, I have no problems with that. I wanted to post where it was most relevant in the first place. I just want to be able to reply without the 'newbe' restrictions.
Relieved that I can save my things, by saving the data.img file.
Partitioning, would love a link to the best/safest method.
Blackscreen.. So I just hit a button and leave it for awhile? That's not very practical if I had a buisness call to make, or an emergency. Is there a workaround? Can I shut off the Auto Lock?
What folder do I add music, ringtones, movies and other goodies to? Can WM 7 Android share these same files? (as long as they're not OS specific obviously)
Ah, i see your reasoning, no problem. A good guide on partitioning that i used as well can be found here. And well there inst really a fix to the black screen problem and i haven't searched for one since it only happens on boot of Android. What seems to make it come back faster for me is locking and unlocking the phone quickly. And you can just place a folder and name it anything you want on the root of the SD card. Heck you can put all your mp3,photos,documents on the root of the SD card and Android will still pick them up, it doesn't matter. And when you say "Share" do you mean Bluetooth sending? Then yes, you can.
Nope... SD card will not let me install anything while i was hook to puter. I was running WM at the time, not android. That shouldn't have been a problem. I am about to hook SD card directly to copmuter itself and copy files that way.
I have had all music located on card before this install, nicely organized by artist or genre, along with my movies, pics, etc. But wont allow me to do this now. I am little confused about that, unless android locked SD/root to android application only. Since most programs that lock things usually prompt you for user allowances, which i did not see, i am ruling that out as an option. Phones and computers are very similar as i am finding out.
The blackscreen doesn't occur on Droid boot... It happens when it sleeps, hibernates, or whatever you call it. Can not wake it from this state.
The Data.img.... Do i put that in after i update and run android, or do i put it in the very begining when i copy droid folder to SD card?
Thanx
~Bdwlf2~
Yup, android put a 'write protect' on SD card. Trying some format tools now. Had to put a re-partiton on it to get rid of protection, which made it a Bad Disk. So trying a recovery on it now. I refuse to be beatin by an object smaller than my thumbnail. Arrrgh!
Android does not lock the SD card to application only, that's very odd that you cant copy files to the SD card. Maybe its a setting on your computer that wont allow you? And about the black screen problem, there seems to be no one reporting about that on the thread as far i can see. Are you running SetCPU or a Task Killer by any chance? Those make Android behave very odd. If not i would suggest downloading the latest build again and formatting your SD Card and putting Android on it again. You can also move your stuff your desktop and put it back again. About the Data.img, you don't really need to move it anywhere. When there is a new update to the build, i simply extract the contents of the new build to the Android folder on my SD card and over write. Simplest method I've seen yet.
bdwlf2 said:
Yup, android put a 'write protect' on SD card. Trying some format tools now. Had to put a re-partiton on it to get rid of protection, which made it a Bad Disk. So trying a recovery on it now. I refuse to be beatin by an object smaller than my thumbnail. Arrrgh!
Click to expand...
Click to collapse
That seems very odd. I've been using this build since February 24th and it has never locked up like that. But nonetheless you found a fix, good work.
No, not running any of those programs. I have extensively swapped data with this card numerous times.
I checked all setting in android prior to putting into puter. In therory, android should NOT write protect the disk, but something did. I have read this happening to others just in XDA forums alone.
Just got disk back to the "good" state using MiniTool Power Data Recovery... Let's take a peek as to see if it works correctly now.
Hmmmm... I think I should have used, repair damage partiton after recovery... still not working.
***scratches head***
I may need another cup of coffee for this.
How about a simple reformat?
Sent from my HTC HD2 using XDA Premium App
Nope. Tried that.
Windows formatter - no
SD formatter - no
Mini tool -nada
MyDefrag - not
Test disk - running now... pending
Try to reformat the SD from Windows Mobile?
Yup, first option....
Would go partially thru it, then stop. Worked fine yesterday. This starting to become un-nerving.
I will find a way. There is always a way. Unless something shorts/melts/breaks/ or fry's... there is always a way. Just a matter of correct knowedge and tool combination.
bdwlf2 said:
Yup, first option....
Would go partially thru it, then stop. Worked fine yesterday. This starting to become un-nerving.
I will find a way. There is always a way. Unless something shorts/melts/breaks/ or fry's... there is always a way. Just a matter of correct knowedge and tool combination.
Click to expand...
Click to collapse
Alright good luck.
Trying HDD Regenerator v2011
Seems to be doing something, using limited Demo mode. At least it is identifying the bad sectors.
This one is gonna take awhile. If it works, or i find something that does, I will post. I've read other's have had this problem, and I can save the person buying/tossing out cards.... Then the work is worth it.
57min into it and only scanned 11mb????? This may be a month to scan 16g. If my math is correct. That's 1gig (1000mb) / 11per hour = 90.90hrs to complete 1g of scanning, multiplied by 15 (usable gigs) = 1363.6363hrs or 51.81 days? 51 days to complete scan?!?!?!?! Gonna look for another program. Wow.
Good thing I have a small 2g card. Unfortunately it won't hold 1/2 of my music. Argh, and I just put a 2 HD movies on there.
If you want to partition or format your SD you HAVE to be in Windows Mobile.
Also, if you are repartitioning your SD, I recommend you recreate your data.img or else it will have issues.
I tried to format in WM... Fail. All the files reappeared.
I did notice .android_secure file. That wasn't there before.
I have unmounted, seems like it is remounting itself. I even unmounted and yanked battery immediately. No success.
Yes, Android still boots.... Something in there is locking card. If card was bad, Android would obviously not be booting.
I cant add or remove data from that card. I have tried several programs.
**** Edit****
Please Do Not ask if switch on adapted is locked, I have two adapters, both UNLOCKED... For some reason, my "Spidey Senses" are telling me that I am about to be asked that question. Being asked this will only cause me to "sigh" loudly before i bang my head on desk. Which will still leave me with locked card and now a fresh migrane.
As some of you may remember, my first Note 3, which I got a week ago yesterday, was returned for a full refund the next day due to a Nandroid restore failure through TWRP.
However, some of you may also remember that I had an extremely annoying error message pop up continually for the entire 24 hours I had the device.
The error: Unfortunately IndexService has stopped
This error revealed itself every 1-2 minutes. I could not figure out why as there was little information anywhere on the Internet.
However, after picking up a new Note 3 yesterday, and after many hours of trial-and-error file transfers, I think I found the reason ... a corrupt or otherwise damaged/flawed PDF file.
All other files, Word, Excel, Images, Videos, etc., were NOT the cause, and it had nothing to do with the SDCard. It doesn’t matter if you use a 64MB, 32MB, Class 6, Class 10, or UHS-1 type card. The card is not the problem. I know this because, this time, with my new Note 3, I never put in an SDCard. I transferred all files directly to internal storage and, unfortunately, the IndexService error still appeared … every 1-2 minutes.
This time, however, I noticed that the error message appeared only AFTER I transferred all my files to the device, so I knew it had to do with these files, and that’s where I focused my attention.
It took about 9 hours last night and early this morning. I began by deleting all personal files from the device. Result: No error messages. Then, directory-by-directory (I have 12,554 files and 371 directories), I transferred them back to the device, each time waiting about 3-4 minutes to see if the error message would appear. I read in other forums that the problem might be related to PDF files, so I first transferred all other file types. Result: No error messages. Then I begin transferring PDF files. I did so in groups of about 50 at a time. Yes, I have many PDF files; about 2,100 of them. It all came down to two PDF files. Wow, 2 out of 2,100! I can’t explain why, but when I transferred those two files to the device, the error message appeared, and when I deleted them, the error message disappeared.
Fortunately, the two files were not important, so I permanently deleted them; however, before doing so, I thought that they might have originally been written using a very old version of Adobe, and that they simply couldn’t be “read” by the Adobe reader on the Note 3. With this in mind, I opened them in the latest version of Adobe on my PC, and then re-saved them with a new file name; however, the result was the same. They still caused the indexing error. So, at this point I have no idea why they are causing the problem.
Finally, after all my files were transferred to internal storage, without the 2 problem files, I waited 1 hour. No error message. I then put in my Sandisk 32GB UHS-1 card, copied all the files over, and then waited another 30 minutes. No error message. This morning I deleted all the files from internal storage so that I only had them on the SDCard. No error message. It has now been over 24 hours, and still no error message.
SUMMARY:
1) The indexing error is NOT caused by the external SDCard.
2) The indexing error is PROBABLY caused by a problem PDF file(s)
3) The size of the PDF file is irrelevant. My problem files were each about 10MB; however, all smaller sizes, and even the remaining larger-sized PDF files do not cause a problem.
4) Others have suggested that I turn OFF a particular service, but it didn’t work for me.
5) Others have suggested that the error relates to files larger than 200MB. This does NOT appear to be the case in my situation. I have many files that are more than 200MB, and there isn’t a problem.
6) Another xda member said to create a file called .nomedia and place it in the root of the directory where the problem files are located. I tried this, but I still get the error message.
I hope this helps others.
Peter
PeterGuru said:
As some of you may remember, my first Note 3, which I got a week ago yesterday, was returned for a full refund the next day due to a Nandroid restore failure through TWRP.
However, some of you may also remember that I had an extremely annoying error message pop up continually for the entire 24 hours I had the device.
The error: Unfortunately IndexService has stopped
This error revealed itself every 1-2 minutes. I could not figure out why as there was little information anywhere on the Internet.
However, after picking up a new Note 3 yesterday, and after many hours of trial-and-error file transfers, I think I found the reason ... a corrupt or otherwise damaged/flawed PDF file.
All other files, Word, Excel, Images, Videos, etc., were NOT the cause, and it had nothing to do with the SDCard. It doesn’t matter if you use a 64MB, 32MB, Class 6, Class 10, or UHS-1 type card. The card is not the problem. I know this because, this time, with my new Note 3, I never put in an SDCard. I transferred all files directly to internal storage and, unfortunately, the IndexService error still appeared … every 1-2 minutes.
This time, however, I noticed that the error message appeared only AFTER I transferred all my files to the device, so I knew it had to do with these files, and that’s where I focused my attention.
It took about 9 hours last night and early this morning. I began by deleting all personal files from the device. Result: No error messages. Then, directory-by-directory (I have 12,554 files and 371 directories), I transferred them back to the device, each time waiting about 3-4 minutes to see if the error message would appear. I read in other forums that the problem might be related to PDF files, so I first transferred all other file types. Result: No error messages. Then I begin transferring PDF files. I did so in groups of about 50 at a time. Yes, I have many PDF files; about 2,100 of them. It all came down to two PDF files. Wow, 2 out of 2,100! I can’t explain why, but when I transferred those two files to the device, the error message appeared, and when I deleted them, the error message disappeared.
Fortunately, the two files were not important, so I permanently deleted them; however, before doing so, I thought that they might have originally been written using a very old version of Adobe, and that they simply couldn’t be “read” by the Adobe reader on the Note 3. With this in mind, I opened them in the latest version of Adobe on my PC, and then re-saved them with a new file name; however, the result was the same. They still caused the indexing error. So, at this point I have no idea why they are causing the problem.
Finally, after all my files were transferred to internal storage, without the 2 problem files, I waited 1 hour. No error message. I then put in my Sandisk 32GB UHS-1 card, copied all the files over, and then waited another 30 minutes. No error message. This morning I deleted all the files from internal storage so that I only had them on the SDCard. No error message. It has now been about 6 hours, and still no error message.
SUMMARY:
1) The indexing error is NOT caused by the external SDCard.
2) The indexing error is PROBABLY caused by a problem PDF file(s)
3) The size of the PDF file is irrelevant. My problem files were each about 10MB; however, all smaller sizes, and even the remaining larger-sized PDF files do not cause a problem.
4) Others have suggested that I turn OFF a particular service, but it didn’t work for me.
5) Others have suggested that the error relates to files larger than 200MB. This does NOT appear to be the case in my situation. I have many files that are more than 200MB, and there isn’t a problem.
6) Another xda member said to create a file called .nomedia, and place it in the root of the directory where the culprit files are located. I tried this, but I still get the error message.
I hope this helps others.
Peter
Click to expand...
Click to collapse
I have been trying to get this problem solved as well -- thanks for spelling out what *isn't* working; I've tried several of these things as well. Killing the app/service, asking the s-finder not to index files, putting the .nomedia files in place have all failed to make it go away. It is a little mind boggling that this is an issue as I've had the same loaded SDcard data (fresh card now, same data) on a note1 and note2 and never had this sort of trouble.
Even when I've killed the indexing service it seems to come back without power cycling, perhaps there is something triggering it to come back.
Hopefully there is an official answer on this soon, the phone becomes unresponsive for seconds all too regularly.
Lance
Looks like we've gone through the same thing ...
lance_lascari said:
I have been trying to get this problem solved as well -- thanks for spelling out what *isn't* working; I've tried several of these things as well. Killing the app/service, asking the s-finder not to index files, putting the .nomedia files in place have all failed to make it go away. It is a little mind boggling that this is an issue as I've had the same loaded SDcard data (fresh card now, same data) on a note1 and note2 and never had this sort of trouble.
Even when I've killed the indexing service it seems to come back without power cycling, perhaps there is something triggering it to come back.
Hopefully there is an official answer on this soon, the phone becomes unresponsive for seconds all too regularly.
Lance
Click to expand...
Click to collapse
It looks like we've gone through the same thing. Sadly, when the IndexService error exists, it REALLY sucks battery power.
I hope you get yours resolved.
Peter
P.S. So far today ... no errors.
Peter a big thank you for the effort on this one. Im not having the issue(yet) but i had been wondering about the cause after reading your posts.
Sent from my SM-N900W8 using xda premium
PeterGuru said:
It looks like we've gone through the same thing. Sadly, when the IndexService error exists, it REALLY sucks battery power.
I hope you get yours resolved.
Peter
P.S. So far today ... no errors.
Click to expand...
Click to collapse
Since I'm going to be travelling this week and need the phone to be reliable, I tried just deleting my document archives for now ( ~ four thousand PDF files mostly)... and what a difference in battery life and keeping that error message away. I hope they fix it so I can have my docs back.
Lance
I'm not sure if they will fix it ...
lance_lascari said:
Since I'm going to be travelling this week and need the phone to be reliable, I tried just deleting my document archives for now ( ~ four thousand PDF files mostly)... and what a difference in battery life and keeping that error message away. I hope they fix it so I can have my docs back.
Lance
Click to expand...
Click to collapse
To be honest, I'm not sure if "they" will ever fix it.
At least you know, for sure, that it has to do with your PDF files, just like my situation. Perhaps you can now do what I did, and start copying all the PDF files back to your device, but in large groups ... perhaps 100 at a time. Then wait about 5 minutes, and try another 100.
Logically speaking, though, it would be best to try half your PDF files, so about 2000 first. Then, if you get the error message, remove them all, and re-copy 1000 of them. Slowly but surely you'll narrow down the culprit files. Yes, it may take you a few to several hours, but it can be done, and you'll probably discover that it's simply a few files, or even just ONE file that's causing all the problems.
Peter
PeterGuru said:
To be honest, I'm not sure if "they" will ever fix it.
At least you know, for sure, that it has to do with your PDF files, just like my situation. Perhaps you can now do what I did, and start copying all the PDF files back to your device, but in large groups ... perhaps 100 at a time. Then wait about 5 minutes, and try another 100.
Logically speaking, though, it would be best to try half your PDF files, so about 2000 first. Then, if you get the error message, remove them all, and re-copy 1000 of them. Slowly but surely you'll narrow down the culprit files. Yes, it may take you a few to several hours, but it can be done, and you'll probably discover that it's simply a few files, or even just ONE file that's causing all the problems.
Peter
Click to expand...
Click to collapse
Peter,
I appreciate your comment -- but the issue is pretty widespread and I suspect the noise level will rise as people start really using their devices (only released on Verizon in the US this past week). They would be unwise not to fix it; the two previous generations of the stock note phones did not show this problem. A bit selling point is the ability to have so much storage (between internal and SD). It is possible that I will someday put the effort in to find any specific files that cause the problem, but the whole directory is synchronized with dropbox and I don't want to have to separate it and lose sync just to work around samsung's bug.
I guess I will give some of it a shot, at least I will copy the folder with mostly books (large files, a few hundred) before the archives of technical literature -- that is a start to see if I can narrow it down. I'll have my nexus7 with me, which happily deals with the same files...
Cheers,
Lance
So if I let this service to run long enough to do its job, will it ever finish? As I noticed it runs only when the screen in on. And the culprit pdf (600Mb) in my case is the only one I really need. Is there any way to block it without root access and permanently?
Thanks!
I think if you add a file named .nomedia to a folder it will prevent any indexing in that folder. A very similar problem can occur with a corrupt music or video file. In that case also, the battery life is killed quickly since it can't complete its scanning. Best to identify the bad files and get rid of them, but if that's not an option, add a .nomedia file to the directory.
Sent from my SAMSUNG-SGH-I317
This is what I was going to suggest; however, it doesn't always work ... but give it a try.
The ".nomedia" file should be created within your device.
Peter
Sent from my mobile device
Im surprised you couldn't find anything on the Internet about this issue as it was discussed here in several threads a couple of weeks ago & corrupted .PDF files were seen to be the cause.
I think you could have saved yourself A LOT of time by simply searching XDA for posts "Note 3 indexservice" ....
http://forum.xda-developers.com/showthread.php?t=2463788
Sent from my SM-N9005 using xda app-developers app
I'm astounded at your brazen reply. Yes, I searched everywhere, including xda, and there were, at the time, no concrete answers. There were many ideas, but nothing definitive.
Case in point, the ".nomedia" idea from another member on xda seemed believable, but it didn't work for me. Also, and I repeat, AT THE TIME, the majority of suggestions had to do with files over 200MB, but this was also not the case with me.
If you want to help, offer ideas and suggestions. Simply trying to make a person feel bad is counter-productive.
Peter
Sent from my mobile device
Please don't blame the messenger.
Search is your friend.
Sent from my SM-N9005 using xda app-developers app
What you don't seem to understand is that the unit I have now is the second Note 3. My problem began with my first unit, which I got on release day in Canada, which was October 4. I returned this particular unit the next morning for a full refund. Believe me, I looked at your link, and the date was October 5, AFTER I returned the original unit.
Peter
P.S. Had YOU done a search, you would have known about my issue, which I posted in a few threads on October 4.
Sent from my mobile device
Yes so anyway just in case it's still not clear, i just posted to explain that we found out about the .pdf file corruption causing it a week or so ago.
Sent from my SM-N9005 using xda app-developers app
So is there any way to change pdf files so our Note would not go ballistic about it? How to distinguish between ''good and bad'' pdfs?
Deleted lost interest...
Yeah... I use ezPDF from my S2 on, mainly because it does not have problems with handling any kind of pdf... Adobe and Polaris on the other hand are inferior in my opinion. Any way I am thanking everybody who contributed information on the issue! Hope permanent solution emerges and it should not be the one by eliminating pdf files from my collection.
Regards!
Hi,
This is my temporary solution to the problem…
1. Create folder named ''.nomedia'' (not file in folder) - (I didn't try, but I think that you can name it whatever you want as long as it starts with ''.'')
2. Reboot
3. Copy pdfs to your phone or SD card
4. Unplug USB and move pdfs to folder .nomedia
5. Reboot – because as soon as pdf file that is causing the problem is on the phone's memory, Index service starts and will not stop until you reboot your phone
6. You can access your pdfs through file manager and open them from there.
Unfortunately there is no option to sync your files with any cloud storage, but at least they can be in the memory of the phone to make good use of them.
IMPORTANT: if my solution is already mentioned somewhere on XDA I sincerely apologize!
(and there was a bit of a sarcasm in the final notice)
Pat. said:
Deleted lost interest...
Click to expand...
Click to collapse
..