As I posted back a few days ago in the update thread, supposedly there is another update in the works. Otherwise I really have no other information available other than my source didn't hesitate to answer yes, when I asked them about the rumor of another update.
I know for a fact they are tracking sd card issues as well as reports of issues with GPS.
As we know from the pre-eb13 stock firmwares there was a problem for six months with the gps xtra (almanac and ephemeris assistance) cache. I worked out a workaround, essentially forcing cold start, for that which was sticky'ed on a few sites.
While unofficial eb13 had some gps problems, which you addressed with proper fixes, they were not cache issues.
When people talk about turning wifi on and off, or intermittent or even not experiencing the bug, we should recall that of course people saw that with the pre eb13 firmware as well. There are a dozen possible reasons* for bad data in the cache and we never found out which one or more were the cause. User habits matter: how long the GPS is off, how far one moves, whether it is old ephemeris or partially old almanac etc, plus any number of habits that could unstick or make sticky the cache and/or a myriad of possibilities that could affect data calls to network by the cache repopulating routine. We only know the final eb13 didn't have the problme and it seems to be reappearing in ec05. We know that of the people reporting the problem, a soft reset or invoking cold start worked for virtually everyone
*
- failure to recognize age of data in cache
- failure to calculate age properly
- data stuck even if recognized as old
- no attempt if data is recognized as old
- no reattempt by device if data call fails
- some other stock routine occasionally blocking repopulation
- improper re-population even if old data is recognized as expired/partially expired and fresh data properly obtained from assistance server
- etc etc etc.