Epo file download fails
- Thread starter Anunnaki
- Start date
EPO files for January 15
Here are today's EPO files.
Has anyone tried contacting MediaTek over mediatek.com/_en/08_info/03_contactUS.php?
Here are today's EPO files.
Has anyone tried contacting MediaTek over mediatek.com/_en/08_info/03_contactUS.php?
Last edited:
Thanks for the file. Here is a mirror link from ge.tt service.
Contactt? No.
Funny! -- There is no "technology" option in the drop-down menu. on the 03_contactUS.php page, and I'm unsure of what to write in the message. I wonder if a mediatek official forum site exists...
Last edited:
I selected Other and simply wrote something along the lines of:
Hello MediaTek team,
your ftp-server at epo.mediatek.com is virtually always down due to heavy traffic. Please fix this, as many users rely on the EPO data for their MediaTek GPS-decives to function properly. Thanks in advance!
XXX
your ftp-server at epo.mediatek.com is virtually always down due to heavy traffic. Please fix this, as many users rely on the EPO data for their MediaTek GPS-decives to function properly. Thanks in advance!
XXX
Maybe they will take notice if we spam them :cyclops:
First post here so hi to everyone.
Having read through all the posts here, it seems that there are several different trains of thought as to the cause and remedy for this problem, mostly based on one individual’s findings on one specific device.
My company uses PDAs as part of a dispatching system for taxis and we use thousands of devices that possibly allows us to see a more representative picture.
The EPO file download does reliably fail on the vast majority of devices but if left connected, by the end of the day most will have received it. From this, we have to assume it’s simply the servers struggling to cope with the high levels of attempted downloads rather than incorrect settings, otherwise they would never ever download.
Secondly, we have observed that from within a factory fresh batch of 100 devices, up to 10% will not download however long they’re left trying. This leads us to believe that the internal settings on these devices must be wrong even though they are all part of the same batch. This would be consistent with an internal flag that has not been expressly set or cleared in the production process and hence its state is somewhat undefined.
In a recent batch of 100 alternative devices from a dubious supplier, only 10% eventually achieved the download with the rest being totally useless. Again this has all the hallmarks of an undefined setting.
In short, we believe that there are two distinct issues at play. The servers are massively congested so even with the permission flags correct it may still take a long time to download. If the permission flags are wrong, it will never ever download.
Sorry I’m no great teckie but hopefully this may give some food for thought.
Bill
Having read through all the posts here, it seems that there are several different trains of thought as to the cause and remedy for this problem, mostly based on one individual’s findings on one specific device.
My company uses PDAs as part of a dispatching system for taxis and we use thousands of devices that possibly allows us to see a more representative picture.
The EPO file download does reliably fail on the vast majority of devices but if left connected, by the end of the day most will have received it. From this, we have to assume it’s simply the servers struggling to cope with the high levels of attempted downloads rather than incorrect settings, otherwise they would never ever download.
Secondly, we have observed that from within a factory fresh batch of 100 devices, up to 10% will not download however long they’re left trying. This leads us to believe that the internal settings on these devices must be wrong even though they are all part of the same batch. This would be consistent with an internal flag that has not been expressly set or cleared in the production process and hence its state is somewhat undefined.
In a recent batch of 100 alternative devices from a dubious supplier, only 10% eventually achieved the download with the rest being totally useless. Again this has all the hallmarks of an undefined setting.
In short, we believe that there are two distinct issues at play. The servers are massively congested so even with the permission flags correct it may still take a long time to download. If the permission flags are wrong, it will never ever download.
Sorry I’m no great teckie but hopefully this may give some food for thought.
Bill
Hi,
I noticed the maximum TTL for epo.mediatek.com is 30 second.
Then I've put the next script running for a day:
Code:
while true;
do host epo.mediatek.com | tee -a -i epo.mediatek.com.log ;
sleep 15;
done
Code:
cat epo.mediatek.com.log | grep epo.mediatek.com | awk '{print $4}' | sort | uniq124.219.30.162
124.219.30.163
124.219.30.164
124.219.30.165
124.219.30.166
124.219.30.167
124.219.30.168
124.219.30.169
124.219.30.170
124.219.30.171
54.193.53.205
54.200.6.244
54.201.46.179
54.213.119.11
54.213.12.103
54.213.135.230
54.213.21.35
Looping through the list I was able to download EPO files and then put them on my device by hand.
new epo 17_01_2014 here
http://www.adrive.com/public/xGHFMD/data epo17_01_2014.rar
you will need winrar to unzip
http://www.adrive.com/public/xGHFMD/data epo17_01_2014.rar
you will need winrar to unzip
Last edited:
Best time for me to download from Germany is between 8.pm till 6.am MEZ.
MTK Engineering Mode Start from the play store is equal to mobileuncle to enter the Engineer Mode. The best tip I used is to edit gps.conf in system/etc to use the nearest ntp sever and some other tweaks that you can find here with the help of the search key.
You have to play around a bit, to figure out the best settings for your devices, but it is worth to do the work. About 2- 25sec to fix and 7-11 sats locked, that's fine with me.
OK, the accuracy could be better (approx.20m) and the hight above see level isn't correct, not mind blowing, but there isn't much desert or jungle around here. Good luck to you all.
MTK Engineering Mode Start from the play store is equal to mobileuncle to enter the Engineer Mode. The best tip I used is to edit gps.conf in system/etc to use the nearest ntp sever and some other tweaks that you can find here with the help of the search key.
You have to play around a bit, to figure out the best settings for your devices, but it is worth to do the work. About 2- 25sec to fix and 7-11 sats locked, that's fine with me.
OK, the accuracy could be better (approx.20m) and the hight above see level isn't correct, not mind blowing, but there isn't much desert or jungle around here. Good luck to you all.
Well,
does anyone know Is Epo necessary and how much if is?
Has anyone used Gps without Epo and with what results?
I wonder ... :angel:
does anyone know Is Epo necessary and how much if is?
Has anyone used Gps without Epo and with what results?
I wonder ... :angel:
Welcome to the Forum Bill - well I'm a noob myself, but this place allows for one hell of a steep learning curve
You're right, it seems to be two problems, both of which we seem to be able to fix ourselves, but which we can also contact MediaTek about. Like I said, I don't know whether it will make any difference at all, but I'm sure it wouldn't be too much of a burden for them to fix a lonely FTP server - especially now that they're seemingly listening to customers.Well,
does anyone know Is Epo necessary and how much if is?
Has anyone used Gps without Epo and with what results?
I wonder ... :angel:
Before EPO: Min. 90 seconds to first fix.
After EPO: Max. 30 seconds to first fix.
After FasterGPS: Max. 10 seconds to first fix.
So if you haven't already set your NTP servers, check out play.google.com/store/apps/details?id=org.fastergps - it improved my GPS signal by order of magnitude
Last edited:
Before EPO: Min. 90 seconds to first fix.
After EPO: Max. 30 seconds to first fix.
After FasterGPS: Max. 10 seconds to first fix.
So if you haven't already set your NTP servers, check out play.google.com/store/apps/details?id=org.fastergps - it improved my GPS signal by order of magnitude
For earlier versions of Android was gps.conf file in my phone and I was trying a different configuration gps.conf, and found the most suitable.
But my cell phone with Android 4.2 has no gps.conf file!
Gps.conf file must be in cell phone?
Sorry my english...
Mine didn't exist either; I created one myself, but either I made mistakes or there was a bug - the system never accepted my gps.conf.
So I took the easy way out:
I installed FasterGPS: In the app, I set my region and country, and it simply created all necessary files - that solved everything.
I also just posted a tutorial on how to generally improve your GPS signal on MediaTek devices. I took information from this thread as well, so if you're looking for a comprehensive how-to, here you go.
If anyone knows any other tips on how to get better GPS reception, please let me know, and I'll add them to the list.
Hope this helps!
Last edited:
Nice! Thanx, I couldn't have done it better! Well done, exactly the way I meant to figure out to improve gps. BTW, there is no problem to insert a missing gps.conf in /system/etc, the only thing that could happen is, that it is ignored.
FasterFix messes up the text of my self-edited configfile, but afterwards it worked well.
Last edited:
25.01.2014.
https://www.dropbox.com/s/uv3esgwpsa7j13s/EPO_Files_25-1-2014_21-40-58.zip
Finally, I managed to download
https://www.dropbox.com/s/uv3esgwpsa7j13s/EPO_Files_25-1-2014_21-40-58.zip
Finally, I managed to download
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8Final solution?
Thanks to a tip from @ultrasound191, we now have a different source: the current EPO files can be found at
epodownload.mediatek.com/EPO.DAT
epodownload.mediatek.com/EPO.MD5
Just tried it, and it works perfectly - no delays, and files are always up to date. Cheers!7FTP server: epo.mediatek.com
Port: 21
Login: epo_alps
Password: epo_alps
There are two files:
EPO.DAT
EPO.MD5
Both files are updated on the server once per day, usualy around 7:51(GMT+2).
They should be downloaded to the folder: /data/misc .
When you try to download them from phone "EPO settings", you see message "EPO FILE INFO DOWNLOADING", than you see (50%). That 50% status appears and disappears around 3 times, and some time after that you receive error message "Download files invalid".
The reason is, that they have always wrong MD5 checksum in file EPO.MD5. So your phone download and compare/calc checksum for few times, but every time the checksum is incorrect. And that is reason, why it is not working.
I have tried to connect to the epo.mediatek.com ftp server manually from PC. Every time i download EPO.DAT file, the MD5 checksum is the same, but in EPO.MD5 file is another one (also still the same).
I have calculated correct MD5 checksum, and changed it to correct value to the file EPO.MD5. Than I have uploaded both files to my private FTP server. And than, through "Engineering Menu" (you can enter there by calling number *#*#3646633#*#* and then select "EPO" item) in the phone I have changed FTP connection/login/password to my server, and tested that. And when I have there correct MD5 checksum in file EPO.MD5, everything works as it should be.
So someone should tell Mediatek, that they have some serious problem with MD5 calculation on their FTP server.65
Oopss, sorry, I didn't know this, I suposed everydays system download EPO files. Here is January files, copy EPO.DAT, EPO.MD5 and LEGAL.txt on /data/misc folder:
https://mega.co.nz/#!NYlBFApL!Hrh57yPOTsbt7FZXn2RT3FhEXoE4knbBr61nd5E2gTg
regards!
New posts
-
Junsun V1 Plus 8GB-256GB - Britghtness settings by night too strong
- Latest: Alex-Le-Zombiz
