Rockbox Ports are now being developed for various digital audio players!
Well I started the test at 4:25pm and it made it to 9:58pm before shutting off. 5 hours 33 minutes. This was looping the same album that resulted in 20 hours on the Apple firmware with a brand new (eBay) battery.When I go to "show disk" in the Debug menu, there's a bunch of power management and such items that say "not supported." I imagine that has something to do with it, but I'm still confused why there's such a huge discrepancy.
The same goes for the decrease in battery life; I don't doubt that it's real, but if there is no improvement with 3-12 (versus 3-11) then it's looking increasingly unlikely that it has anything to do with the "iflash fixes" being discussed here. If you're willing to be a guniea pig I can generate a one-off build that reverts to the known-corrupting pre-fix state (ie issue SLEEP commands), to confirm this theory.
The write error is unrelated to this is essentially a "write timeout". It's most likely completely unrelated to this powermgmt change, because we don't actually shut anything down until the disk subsystem has been idle for several seconds.The failure to mount after unplugging is almost always due to some filesystem error, typically caused by unsafe disconnects. Windows detected something wonky, so there was clearly something wrong.Can't comment on that first data abort panic, except perhaps that all three are due to the same underlying disk corruption. It's easy enough to back out the change re-enabling shutting off power to the "disk" but to be honest I don't think what you saw is due to this.(The best way to make sure here -- grab the 2021-03-11 and 2021-03-12 daily builds, and see if they behave any differently. Please unzip the builds via apple disk mode and do a disk check too just to be safe, afterwards have at it and see what happens. if 3-12 crashes as you describe but 3-11 does not, then we'll have pretty good confidence what's causing this...)The same goes for the decrease in battery life; I don't doubt that it's real, but if there is no improvement with 3-12 (versus 3-11) then it's looking increasingly unlikely that it has anything to do with the "iflash fixes" being discussed here. If you're willing to be a guniea pig I can generate a one-off build that reverts to the known-corrupting pre-fix state (ie issue SLEEP commands), to confirm this theory.
Ok confirmed crashed happen on 2021-03-12 but not on 2021-03-11
Quote from: roastpotatoes on March 12, 2021, 09:05:39 AMOk confirmed crashed happen on 2021-03-12 but not on 2021-03-11Thank you for confirming this. The only meaningful change between those two is that 03-12 allows turning off the power supply to the drive, which happens 2 seconds after the last I/O operation is reported as complete by the drive.Clearly the iFlash adapter is lying, and it's still writing stuff in the background even two seconds later. So, as another attempt to mitigate this, I've increased the poweroff delay to a full five seconds. Please test the most recent dev build (2743bde0 or newer include it) and see if it still crashes/corrupts things on you?
Roast, what brand SD card are you using? I had similar errors but only with an older DaneElec card. My Lexar Professional isn't giving me any errors on 2743bde0.But it also doesn't look like there's any improvement either. Still draining at the same rate.
Page created in 0.282 seconds with 18 queries.