Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[TIP] IndexService Error Solution ...

OP PeterGuru

12th October 2013, 04:55 PM   |  #1  
PeterGuru's Avatar
OP Senior Member
Flag Ontario, Canada
Thanks Meter: 1,156
 
1,422 posts
Join Date:Joined: Mar 2008
Donate to Me
More
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
Last edited by PeterGuru; 13th October 2013 at 03:28 PM.
The Following 8 Users Say Thank You to PeterGuru For This Useful Post: [ View ]
12th October 2013, 07:15 PM   |  #2  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by PeterGuru

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


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
13th October 2013, 12:20 AM   |  #3  
PeterGuru's Avatar
OP Senior Member
Flag Ontario, Canada
Thanks Meter: 1,156
 
1,422 posts
Join Date:Joined: Mar 2008
Donate to Me
More
Looks like we've gone through the same thing ...
Quote:
Originally Posted by lance_lascari

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

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.
13th October 2013, 12:41 AM   |  #4  
force70's Avatar
Senior Member
Flag toronto
Thanks Meter: 2,309
 
3,792 posts
Join Date:Joined: Jan 2012
More
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
The Following User Says Thank You to force70 For This Useful Post: [ View ]
14th October 2013, 03:01 PM   |  #5  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by PeterGuru

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.


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
14th October 2013, 03:29 PM   |  #6  
PeterGuru's Avatar
OP Senior Member
Flag Ontario, Canada
Thanks Meter: 1,156
 
1,422 posts
Join Date:Joined: Mar 2008
Donate to Me
More
I'm not sure if they will fix it ...
Quote:
Originally Posted by lance_lascari

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

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
14th October 2013, 04:10 PM   |  #7  
Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: May 2011
Quote:
Originally Posted by PeterGuru

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

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
15th October 2013, 12:08 PM   |  #8  
Member
Thanks Meter: 4
 
38 posts
Join Date:Joined: Jun 2012
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!
15th October 2013, 01:16 PM   |  #9  
Senior Member
Flag San Francisco
Thanks Meter: 40
 
174 posts
Join Date:Joined: Nov 2012
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
15th October 2013, 01:21 PM   |  #10  
PeterGuru's Avatar
OP Senior Member
Flag Ontario, Canada
Thanks Meter: 1,156
 
1,422 posts
Join Date:Joined: Mar 2008
Donate to Me
More
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

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes