Hi all,
Newbie Archos 70 250Gb owner here - back with Archos after a long period in the iPod wilderness
I'm generally pleased with the A70 but there's one thing which is a bit of a showstopper for me at the moment. I specifically bought the A70 with the big disk because I'm a music junkie - I have 150Gb or so of mp3s, and I add 3-4 albums per month.
I've copied all my music to the A70's hard disk (something like 22,000 songs), but the media scanner has only found a small fraction of them. I can sit and watch it run, and it gets to about 3200 files before quitting. This is repeatable - if I rerun "update multimedia library" it never gets beyond this point.
Anyone got any clues as to how I can track down the problem? I'm wondering if I have one dodgy mp3 which is causing it to fail perhaps? Without knowing which one it is, it's going to be tough to fix this - I can't manually remove each one of 22,000 files and keep retrying! Are there some system logs somewhere I can check?
I beginning to wonder if I'm going to have to roll my own media scanner - I'm an experienced Java programmer but very light on Android skills so it might take me a while.. so I'd rather not if I don't have to - I'm not even sure if I get that level of access to the system.
Keith.
According to several folks over at the ArchosFans forums, the media scanner has a problem with tracks that have a "#" symbol in the name. Since I cannot post links yet, go to forum dot archosfans dot com, and search for "media scan hash pound #" and that should take you to the right thread.
That said, a custom media scanner might not be such a bad thing; it seems to be a source of unhappiness for a number of folks.
Hi,
Same problem here, i found that doing a 'rebuild media database from scratch' option in repair&fornatting menu did eventually (after about 1day of scanning) found all my files.
Be sure to keep your archos awake during the scan, use for example the pictureframe app so the device stays awake.
Hope this helps
Sent from my A70H using Tapatalk
Thanks guys - that's two things to try, I'll let you know how I get on.
Status update: clearing out the media library and re-running the scan didn't work - it still fails, and this time leaves me with an empty library.
So, i rolled a very simple scanning app, which I can point at a single directory (i.e. a single artist). It imports some things fine, but guess what - when importing files with a "#" in them the media scanner apparently falls over - silently, unfortunately, nothing gets reported to my little app when it happens. The thread referenced above also mentions issues where the "artist" tag doesn't match the "album artist" tag - I'll keep an eye open for those too.
This is the built-in Android media scanning service that is failing, as far as I can tell - it's not clear to me if Archos modified it or not, but it's pretty shoddy not being able to handle a valid filename.
So, I'm going to keep going with my little app (maybe this thread needs to move to the dev forum?) but right now the best I can make it do is to not scan files with a hash in them, or perhaps rename the files on disk (but that would really screw up my synch mechanism, as I don't want to have to rename a whole bunch of stuff in iTunes which I also use..)
This is all disappointing - I was an early adopter of Archos stuff with a JB6000 and JBR20 (still got it somewhere!) back in the day and they've always been pretty decent at the music side of things - this is not what I would expect from them and makes it difficult for me to know what to do next as this is my primary use of the device...
EDIT: for info: the # problem only occurs with the filename, not the tags - so renaming the file appears to solve the problem while leaving the tags intact - I'll go down that route for a bit, see if I can fix things that way.
Keith.
20,000 song limit(!)
So it turns out that the scanning problem is all about hash symbols in filenames - once I removed all the hash symbols from file names the scan got all the way to the end, but hung on "Finishing scan" indefinitely. I realised I still had playlist files referencing the original filenames with hashes. Once I got rid of those, the scan completed just fine, but presented me with this:
Maximum multimedia library size reached: Only the first 20000 audio files have been indexed​
Well that's a bit of a showstopper isn't it. I'm struggling to understand why someone would ship what is basically an enhanced media player with 250Gb of space, and then restrict the media library so you can't make use of it all. Even my iPod Classic 160Gb can take more songs than that!
I'll take this over into the developers forum to see if there's any way around this limit - I'm assuming it won't be anything simple. Argh!
Keith.
Yes, yes I know *#*#INFO#*#* (Debug menu) has been discovered and thoroughly analyzed countless times but I want to draw attention to a few others:
*#*#225#*#* (presumably 225 = CAL) brings up Calendar Info which seemingly only lists the number of events for each sync'd Google calendar. Interesting, but not really userful.
*#*#CHECKIN#*#*
Rumored to trigger OTA updates but in my experience this is false. I have yet to find any explanation for what this does, but it consistently triggers network activity and then a "Checkin succeeded" notification appears.
Does anyone have any info on what a checkin is??
*#*#682#*#*
Consistently triggers network activity but I don't know the purpose. I got excited when I tried this because I'm waiting for the 2.3 update for my Tmo G2 and, well, 682 could stand for "ota".... But it didn't trigger any update, unsurprisingly.
Does anyone have any info on this one??
I'm trying to find a way to easily capture network traffic from my phone to learn anything about the network activity triggered by the last two commands. However, if anybody else already knows how to do this and would like to investigate, feel free!
Also, if anyone has discovered similar codes (of the *#*# _ #*#* variety - I'm not talking about manufacturer or carrier specific codes - no shortcodes for checking minute balances please!) feel free to share. I'm sure there have to be more of them!
Hi,
This is the first time I've started a thread so home I'm in the right place etc.
Just working on my first ever app. I created it as a service as that's what I thought I needed to monitor the battery status, screen status etc. I created some intent filters within the program itself to do that and assumed the process had to be running to get them.
Then I read I could have put the intents in the manifest file and my app will be started up if it isn't already running. That sounds quite neat as I can get rid of the notification icon I have to have in the notification area (I had to use setForeground to stop Android killing off the service and then immediately re-starting it). But -
Am I going to use up more battery with this second method? (using intents to wake the process) I'm not sure how often Android is going to terminate my process but if it's quite often then the overhead of my app starting up and reading some variables I'd have to persist could be a drain.
Any rule of thumb help here? I know the answer might have a bit of "depends" in it but really looking for some general advice.
Thanks.
Peter.
Hi all, I usually dont post on here as I am usually able to figure most things out myself including rooting, harware replacements, app installs using apks and data, generally overall quite proficient but I find myself lost on this one. Thats where the wonderful brains of XDA come in. Basically I have an issue where a certain application uses a login at launch. The application actually redirects to a website to verify the username and password combo. During the first login attempt, it will produce a username and password error. If you close the application and attempt to log in again, same issue. The username/password error is produced in a pop up window with an ok option on it to acknowledge error. Heres where things get a little interesting. If you do not exit the application and hit ok on the error window, you then have the option to try to log in again without relaunching app. This will work every single time. So basically what I am trying to figure out is a way to trace the app on both instances to verify where the application may be failing along the network and using the second instance where it works to cross reference to see failure point. I have tried packet sniffer to no avail. Any other suggestions would be greatly appreciated!
I have tinkered with Tasker on previous phones and generally managed to get it to do some useful stuff, though I am no expert. I have recently started playing around in Tasker again on a rooted Note 4 (SM-N910F), and I have noticed that things don't always work as expected... I know, I know... check for typos, user error, etc.
In an effort to debug a task that deals with appending characters to multiple variables, I deleted all non essential profiles, tasks and scenes, leaving 4x tasks (with less than 4 actions each) and 1x scene. I can append single digit numbers to one variable no problem, but in another variable I wanted to append a single "." at a time. This was not appending anything to the variable, so I changed the appended character to "o" instead. Lo and behold the variable in question is now appending "."s when that task is run. A lot of the errors (there have been some weird ones!) I have been seeing recently could be explained by some tasks and variables acting like previous/incomplete versions of themselves.
Is this something anyone else has experienced? I have a backup of my Tasker for anyone who wants to nose around in there to make sure I'm not calling "%Sanity eq 1/%Sanity" or other such nonsense. Just not sure the best way to get it to you. I am trying to build a custom PIN lock screen FYI. For those who do look around in there, the large grey button is an exit button so you don't lock yourself out of your phone, and the red button checks the entered PIN vs the stored one.