|
|
Post by neminem on Jan 24, 2014 21:39:21 GMT -5
I'm back! My Archos 5 broke a number of months ago (right as the warranty was about to expire  ), and it was a pain getting them to actually replace it under warranty. Finally got it back, and this was the first thing I installed, of course. So I'm seeing one major problem now with the current version - hitting "Exit" doesn't appear to do anything, by which I mean, after opening GoneMad, I am unable to put the Archos 5 into "deep sleep". After hitting "exit", I'm still unable to put the Archos 5 into deep sleep. I know it's definitely GoneMad, because if I go into "Manage Applications", find GoneMad, hit "Force Stop" on it, wait a few seconds, and then put it into deep sleep, it works. (Then I open GoneMad again, and again can't again.) This is completely reproduceable. Is there any information I could help you with to get this fixed? Thanks! |
|
|
|
Post by GoneMAD on Jan 25, 2014 16:13:33 GMT -5
gonemad music player doesnt need to be exited to hit a deep sleep. If you are not listening to music then it does nothing to prevent a deep sleep. My archos 5IT has gone into deep sleep hundreds of times with gmmp in focus
That being said, on android there is no actual way to truly exit an app. Menu -> Exit will shut down the music service and exit out of the UI.. but its up to the OS to shut it down
The only thing that would prevent a deep sleep is either playing music.. or having "Always keep device awake" enabled
|
|
|
|
Post by neminem on Jan 26, 2014 21:55:26 GMT -5
The only thing that would prevent a deep sleep is either playing music.. or having "Always keep device awake" enabled You say that, but I am seeing an extremely direct correlation between GoneMAD Music Player showing up in the list of apps that are running (opening the Application list, filtering by "Running"), and my Archos being unable to go to sleep. Music is not playing (because I've told it to exit, and in fact, paused it and then told it to exit), and that checkbox is not checked (just to be sure, I checked it, quit, opened GMMP again, unchecked it, then quit again). Still, if GoneMad is in the list of running apps, I can't sleep, and if it isn't (because I just restarted, or because I force-quit GMMP from the application list), I can. I definitely didn't have that problem with my previous Archos 5, so it's not surprising that you don't with yours either (though mine isn't an IT, but it wasn't before, either). I'm just wondering whether there's anything I could run to tell you why the issue exists for me? |
|
|
|
Post by GoneMAD on Jan 26, 2014 22:18:38 GMT -5
the archos 5.. as far as i know doesnt run android.. only the IT does Is this a different device that is running something other than android 1.6? But yea.. i mean i dont doubt you when you say your device is not going to sleep.. but its nothing im able to do anything about. The players doesnt keep any wakelocks open unless music is playing or that one setting is enabled. Wakelocks are what prevent a device from sleeping Android 1.6 is about 4 years old now and is quite horrible. There is a post in the general discussion that does link to some of the older versions.. gonemadmusicplayer.proboards.com/index.cgi?board=general&action=display&thread=148 |
|
|
|
Post by neminem on Jan 26, 2014 23:15:51 GMT -5
Oh, huh. Apparently you are correct. I thought I'd read that the 5IT was a second-gen 5 that went up to 2.1, but apparently I was incorrect in thinking that, which means I do have a 5IT. So there's no way to check whether, somehow, it is still keeping wakelocks even though it shouldn't be? Meanwhile, good suggestion, I'll go install older versions and see if at some point the issue goes away. That could help determine what the issue is, at least. Thanks.
|
|
|
|
Post by GoneMAD on Jan 26, 2014 23:56:02 GMT -5
|
|
|
|
Post by neminem on Feb 15, 2014 15:28:57 GMT -5
So I just got around to checking that link, and unfortunately, it looks like that only has the apk for the final version of each major release? I have confirmed that it worked fine in gmmp-1.3.22, but I really really don't want to be stuck on 1.3 - all the features I had asked for that you gave me, that made GMMP do everything I needed, were added sometime mid-1.4, and I know for a fact that this worked fine when my previous Archos 5 died, mid-1.4. I don't suppose there's any secret place to download apks between 1.3.22 and the current release? >.>
(Would both be useful for me, cause I could just stay on that version, and also for you to know what the heck changed.)
Thanks. >.>
|
|
|
|
Post by GoneMAD on Feb 16, 2014 2:34:10 GMT -5
So I just got around to checking that link, and unfortunately, it looks like that only has the apk for the final version of each major release? I have confirmed that it worked fine in gmmp-1.3.22, but I really really don't want to be stuck on 1.3 - all the features I had asked for that you gave me, that made GMMP do everything I needed, were added sometime mid-1.4, and I know for a fact that this worked fine when my previous Archos 5 died, mid-1.4. I don't suppose there's any secret place to download apks between 1.3.22 and the current release? >.> (Would both be useful for me, cause I could just stay on that version, and also for you to know what the heck changed.) Thanks. >.> Here are all the 1.4.x versions in a zip.. let me know when you download it so i can take it down: www.mediafire.com/download/q1h103ipkxt6jb2/gmmp-1.4-archive.zip |
|
|
|
Post by neminem on Feb 16, 2014 18:41:25 GMT -5
Awesomeness, thanks a bunch. I have now downloaded it, and will let you know what I learn once I've gone through and tried installing them. Thanks!
|
|
|
|
Post by neminem on Feb 16, 2014 22:40:11 GMT -5
Well, that's weird - I have no idea why I could reproduce this on any 1.4.* but not 1.3.*, but in any case, I figured out the component that was causing the issue: by turning off automatically running the scanner when the music service starts, I can now put the device to sleep. So scanning is keeping a wakelock open, something is going on that's preventing the scanner from completing (or making it take an unusually long time), something specific to particular Archos rather than Archoses in general.
So, that works well enough; I don't mind manually running the scanner. I run gmmp and then want to sleep the device 2-3 times a day... I clone my media collection to my Archos in batch, once every month or two. Much less annoying. Still weird, though.
|
|
|
|
Post by GoneMAD on Feb 17, 2014 1:56:28 GMT -5
Well, that's weird - I have no idea why I could reproduce this on any 1.4.* but not 1.3.*, but in any case, I figured out the component that was causing the issue: by turning off automatically running the scanner when the music service starts, I can now put the device to sleep. So scanning is keeping a wakelock open, something is going on that's preventing the scanner from completing (or making it take an unusually long time), something specific to particular Archos rather than Archoses in general. So, that works well enough; I don't mind manually running the scanner. I run gmmp and then want to sleep the device 2-3 times a day... I clone my media collection to my Archos in batch, once every month or two. Much less annoying. Still weird, though. i'll probably have to look through about a years worth of changes i made to the scanner.. but yea i've had various reports of the scanner getting hung up and never finishing. 95% of the time it was due to corrupt storage.. the other times it was an infinite recursion (a folder contains a folder that is actually linked to a parent of the original folder so it keeps on looping through the same few folders) |
|
|
|
Post by neminem on Feb 17, 2014 13:01:58 GMT -5
Oh yeah, duh, that would make sense, since it's the scanner - not something that changed between my old Archos device and this new one, necessarily (since I know 1.4.something was definitely working when the old one broke), but rather, more likely something that changed in the state of my music collection between then and now. In any case, I don't think you'd have to look through all the changes you made for years? At least in my case, since I reproduced the issue consistently on the very first 1.4.x release you made, but couldn't reproduce it on the final 1.3.x version. So that probably wouldn't be too much code?  In any case, I'm good for now. Still probably better to fix whatever the issue was, if you'd gotten other similar weird reports though. And let me know if you want me to try checking anything in particular to help you out. |
|
|
|
Post by GoneMAD on Feb 17, 2014 13:58:43 GMT -5
Oh yeah, duh, that would make sense, since it's the scanner - not something that changed between my old Archos device and this new one, necessarily (since I know 1.4.something was definitely working when the old one broke), but rather, more likely something that changed in the state of my music collection between then and now. In any case, I don't think you'd have to look through all the changes you made for years? At least in my case, since I reproduced the issue consistently on the very first 1.4.x release you made, but couldn't reproduce it on the final 1.3.x version. So that probably wouldn't be too much code? In any case, I'm good for now. Still probably better to fix whatever the issue was, if you'd gotten other similar weird reports though. And let me know if you want me to try checking anything in particular to help you out. yea that does narrow it down a bit.. i can see what changed from 1.3.22 to 1.4.0 |
|
), and it was a pain getting them to actually replace it under warranty. Finally got it back, and this was the first thing I installed, of course. 
