gazzington
Headphoneus Supremus
Is the new update working properly now or are people still having problems?
The best result can be achieved only if no a software wakes up the device from its deep sleep.
Is the new update working properly now or are people still having problems?
Check Alarms and Partial Wakelocks screens. If there no a reason found there, please PM me.I come back and BBS says it was in deep sleep for 3h36m (99.5% of the time) and yet the battery is drained to 95%
Hi Paul,Please try the Batch Tool on the first page with the .img FW and then update to a later firmware. A PC is required when using the Batch Tool. There are instructions with the download.
Yes that is correct. Of course you will need to download Tidal from the Play Store.I just wanted to verify, once you install Lurker's firmware you can do Tidal Offline correct?
I just wanted to verify, once you install Lurker's firmware you can do Tidal Offline correct?
I see people mentioning some potential issues with the new firmware, just curious if these people are using Lurkers version of the FW or using the latest stock FW from iBasso? Haven't updated my device in a bit and want to make sure I'm putting the best one on the device in terms of functionality and performance and battery performance. I am currently on 2.10.275-L0.
Thanks, I read some people were on "275L2" and I wasn't sure if this was an updated/improved version further than 275L0.Unfortunately, I ran into the same issue with Lurker0's FW2.11.293 as the stock FW in regards to the "null" music track category. (see my posts # 1509, 1554)
I'm back to stock v2.10.275 and not holding my breath that iBasso is fixing the bugs in this release. (It's been out for 20 days and I have been in touch with Paul attempting to find a work around-to no avail.) IMO, this FW is a step back in several areas (null issue, slower library scan speed , no % tracker during scan, having to scan both storage locations separately-to name a few)
2.10.275L0 worked fine, as did stock-so I'd recommend to stick with it. Again, this is based on my experience with stock 2.11.293.
I am on the most recent firmware and did experience the null folder issue, all I did was rescan my SD card and it was fixed.
Paul told me to do a rescan. It didn't clear the null category for me - and I tried multiple times on different occasions.
Are you sure you're on the altest firmware? That shuld help fix the situation