Locus disables external sdcard after start (using Lollipop)
Hello everybody,
i have a Samsung Galaxy S4 (I9505). Yesterday i flashed Cyanogenmod 12 (Beta) wit Android Lollipop 5.0.1. My smartphone is rooted.
My external 32GB sdcard uses the exFAT Filesystem. All my Offline-Maps (Vector+Raster) are located there. As you can see in the following screenshots, I can use the sdcard with ES-Explorer (and many other apps) without any problems:
After installing and starting Locus maps (from internal sdcard), i tried to add my maps manually. I navigated to my maps folder on my external sdcard and locus starts to initialize the maps:
After a while, locus shows up this error message:
When I exit locus, my external sdcard is no longer available! I have to reboot android to use it again!
After rebooting android i can use my external sdcard again. When starting locus the next time, i can see this screen:
I couldn't resolve this problem. Other Apps like the gallery can read and write the pictures from my external sd card, Poweramp can play and download music to my external sdcard, so i think it is a locus problem, isn't it?
I also tried other filesystems:
FAT32: I cannot use it, because my maps are in the sqlite-format (single file) and over 7GB big.
ext4: I had problems to write on my external sdcard.
I hope you can help me!
Best regards
Thomas Steffen
The same problem 
Ok, I figured out, that if I delete everything inside my maps directory on the external sdcard (image maps in sqlite format), then everything (vector maps, added online maps, ...) works fine and my external sdcard keeps working. If I create a own map inside locus (download current view), it is stored on the internal sdcard - no problem. When i exit locus and cut the two created map files out and paste them to the map folder of my external sdcard, locus shows up an error message again and my external sdcard isn't usable anymore (until reboot).
So I think the problem are maps in the sqlite-format placed on an external sdcard.
Ok, I figured out, that if I delete everything inside my maps directory on the external sdcard (image maps in sqlite format), then everything (vector maps, added online maps, ...) works fine and my external sdcard keeps working. If I create a own map inside locus (download current view), it is stored on the internal sdcard - no problem. When i exit locus and cut the two created map files out and paste them to the map folder of my external sdcard, locus shows up an error message again and my external sdcard isn't usable anymore (until reboot).
So I think the problem are maps in the sqlite-format placed on an external sdcard.
Good day Thomas,
sorry to hear about such issues. On second side, experimental Cyanogen mode - no surprise.
Only what I can do for you now, is if you create a log right after this error appear, I can check content of this log. Maybe there will be any clue, why this problem happen.
How to create a log is wrote here: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . You have probably rooted device, so you may use second bottom method with app called "CatLog".
Good day Thomas,
sorry to hear about such issues. On second side, experimental Cyanogen mode - no surprise.
Only what I can do for you now, is if you create a log right after this error appear, I can check content of this log. Maybe there will be any clue, why this problem happen.
How to create a log is wrote here: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . You have probably rooted device, so you may use second bottom method with app called "CatLog".
Ok, I've made a little test map in the GEMF-Format and it works perfectly on my external sdcard. The problem is, that i don't like the fomat, because of hundred thousands of files are created, it you choose a big area with all zoom levels.
I will now try diffrent versions of the SQLite-Format an hope that one version will work for me.
P.S.: For the creation of the maps I use the freeware "Mobile Atlas Creator" which support many format!
Ok, I've made a little test map in the GEMF-Format and it works perfectly on my external sdcard. The problem is, that i don't like the fomat, because of hundred thousands of files are created, it you choose a big area with all zoom levels.
I will now try diffrent versions of the SQLite-Format an hope that one version will work for me.
P.S.: For the creation of the maps I use the freeware "Mobile Atlas Creator" which support many format!
about mobac:
tried "Big Planet..."?
about mobac:
tried "Big Planet..."?
The same problem with "BigPlanet-Tracks SQLite":
The same problem with "BigPlanet-Tracks SQLite":
[DE]
Wie kopierst du die Datei vom PC auf die externe Karte?
Kannst du einmal versuchen die extSD in den Kartenleser deines PCs zu schieben und dann die sqlite vom PC rüber zu kopieren?
[DE]
Wie kopierst du die Datei vom PC auf die externe Karte?
Kannst du einmal versuchen die extSD in den Kartenleser deines PCs zu schieben und dann die sqlite vom PC rüber zu kopieren?
Danke für den Tip, aber habe schon verschiedene Möglichkeiten ausprobiert. Kopieren über Datenkabel, WLAN und über Kartenleser. Alles mit dem gleichen Resultat. Wenn ich nach dem Fehler "disk i/o error 778" google, kann man zu dem Schluss kommem, dass es sich um ein Problem der SQLite-Datenbank unter Android 5 handel.
Danke für den Tip, aber habe schon verschiedene Möglichkeiten ausprobiert. Kopieren über Datenkabel, WLAN und über Kartenleser. Alles mit dem gleichen Resultat. Wenn ich nach dem Fehler "disk i/o error 778" google, kann man zu dem Schluss kommem, dass es sich um ein Problem der SQLite-Datenbank unter Android 5 handel.
Hey Menion, there seems to be a Problem with SQLite in Android Lollipop! Have a look at http://stackoverflow.com/questions/26816561/android-lollipop-changed-behavior-of-sqlite:
Hey Menion, there seems to be a Problem with SQLite in Android Lollipop! Have a look at http://stackoverflow.com/questions/26816561/android-lollipop-changed-behavior-of-sqlite:
Ok, I downgraded back to Android 4.4 (Imperium v16 ROM). Now everything works perfectly again! The thread can be closed
Ok, I downgraded back to Android 4.4 (Imperium v16 ROM). Now everything works perfectly again! The thread can be closed
I've got the exact same problem :
galaxy s4 i9505
cyanogenmod 12
more than 200 apps (with no problem)
The phone has an external sd of 64g fat with 3gb of maps
The external SD is mounted as /storage/sdcard1/
As soon as I select this directory in Locus (settings/misc/Default directories) it unmount sdcard1. I can acces the external sd only after unmount and mount again in android settings/storage.
How could I help ?
Here is the log cat during the problem : https://dl.dropboxusercontent.com/u/328269/locusproblem-log.txt
Thanks in advance
I've got the exact same problem :
galaxy s4 i9505
cyanogenmod 12
more than 200 apps (with no problem)
The phone has an external sd of 64g fat with 3gb of maps
The external SD is mounted as /storage/sdcard1/
As soon as I select this directory in Locus (settings/misc/Default directories) it unmount sdcard1. I can acces the external sd only after unmount and mount again in android settings/storage.
How could I help ?
Here is the log cat during the problem : https://dl.dropboxusercontent.com/u/328269/locusproblem-log.txt
Thanks in advance
Hello Vincent,
I'm sorry to say it, but
Also as I see in your log, there is some issue in native code:
02-02 17:04:30.167: I/DEBUG(28155): pid: 9772, tid: 9772, name: mount.exfat >>> /system/bin/mount.exfat <<<
02-02 17:04:30.167: E/DEBUG(28155): AM write failure (32 / Broken pipe)
02-02 17:04:30.167: I/DEBUG(28155): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2c
02-02 17:04:30.177: I/DEBUG(28155): r0 b6f7c838 r1 00000000 r2 ffffffc8 r3 b6f3ae04
02-02 17:04:30.177: I/DEBUG(28155): r4 b6f7c838 r5 bedd8720 r6 00000000 r7 b6f7ae0c
02-02 17:04:30.177: I/DEBUG(28155): r8 b6c6a200 r9 bedd8714 sl 00000001 fp 00000000
02-02 17:04:30.177: I/DEBUG(28155): ip b6f7af2c sp bedd8658 lr b6f5eed3 pc b6f62540 cpsr 80000030
02-02 17:04:30.177: I/DEBUG(28155): backtrace:
02-02 17:04:30.177: I/DEBUG(28155): #00 pc 00006540 /system/bin/mount.exfat
02-02 17:04:30.177: I/DEBUG(28155): #01 pc 00002ecf /system/bin/mount.exfat
02-02 17:04:30.177: I/DEBUG(28155): #02 pc 0000a4ab /system/bin/mount.exfat
So I rather suggest to post it on CyanogenMode support site.
Hello Vincent,
I'm sorry to say it, but
Also as I see in your log, there is some issue in native code:
02-02 17:04:30.167: I/DEBUG(28155): pid: 9772, tid: 9772, name: mount.exfat >>> /system/bin/mount.exfat <<<
02-02 17:04:30.167: E/DEBUG(28155): AM write failure (32 / Broken pipe)
02-02 17:04:30.167: I/DEBUG(28155): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2c
02-02 17:04:30.177: I/DEBUG(28155): r0 b6f7c838 r1 00000000 r2 ffffffc8 r3 b6f3ae04
02-02 17:04:30.177: I/DEBUG(28155): r4 b6f7c838 r5 bedd8720 r6 00000000 r7 b6f7ae0c
02-02 17:04:30.177: I/DEBUG(28155): r8 b6c6a200 r9 bedd8714 sl 00000001 fp 00000000
02-02 17:04:30.177: I/DEBUG(28155): ip b6f7af2c sp bedd8658 lr b6f5eed3 pc b6f62540 cpsr 80000030
02-02 17:04:30.177: I/DEBUG(28155): backtrace:
02-02 17:04:30.177: I/DEBUG(28155): #00 pc 00006540 /system/bin/mount.exfat
02-02 17:04:30.177: I/DEBUG(28155): #01 pc 00002ecf /system/bin/mount.exfat
02-02 17:04:30.177: I/DEBUG(28155): #02 pc 0000a4ab /system/bin/mount.exfat
So I rather suggest to post it on CyanogenMode support site.
I think in the moment, it is the only solution and if you don't use big offline maps, it should not be a problem. I went back to Android 4.4, because of big Maps.
You will have to wait until the CM-Team will fix this issue.
I think in the moment, it is the only solution and if you don't use big offline maps, it should not be a problem. I went back to Android 4.4, because of big Maps.
You will have to wait until the CM-Team will fix this issue.
Hi ! Good news :)
The problem is solved, at least in last cm12 for galaxy S4. Don't know when it has been fixed, I just retest today and no more problem with external_sd.
Regards
Hi ! Good news :)
The problem is solved, at least in last cm12 for galaxy S4. Don't know when it has been fixed, I just retest today and no more problem with external_sd.
Regards
For comparison: I run Sony Xperia S, fully rooted and all, and using the NAOSP rom. That used to be based on Android 5.0.2 and recently that moved up to the latest Android 5.1. And Locus continues to run like a charm on all of these! No issues whatsoever. I actually have 2 such phones: one stock (no root, original Sony ROM) with the old 4.1 and the other with 5.1. Oh, BTW, I also fiddled with ext4 vs f2fs and that did not impact at all either: everything just runs fine. (Actually, that old phone with 5.1 is running really well: smooth and rock stable.)
So seeing the story above: I would look at CM for the root cause.
What I think is quite handy is: connect the phone to PC, ensure that all drivers are OK and adb runs fine. Then use totalcommander and this plugin: http://www.totalcmd.net/plugring/android_adb.html
It is very convenient and with this, it is easy to capture the logcat output.
For comparison: I run Sony Xperia S, fully rooted and all, and using the NAOSP rom. That used to be based on Android 5.0.2 and recently that moved up to the latest Android 5.1. And Locus continues to run like a charm on all of these! No issues whatsoever. I actually have 2 such phones: one stock (no root, original Sony ROM) with the old 4.1 and the other with 5.1. Oh, BTW, I also fiddled with ext4 vs f2fs and that did not impact at all either: everything just runs fine. (Actually, that old phone with 5.1 is running really well: smooth and rock stable.)
So seeing the story above: I would look at CM for the root cause.
What I think is quite handy is: connect the phone to PC, ensure that all drivers are OK and adb runs fine. Then use totalcommander and this plugin: http://www.totalcmd.net/plugring/android_adb.html
It is very convenient and with this, it is easy to capture the logcat output.
Not sure this helps but I had the same problem. (here: http://help.locusmap.eu/topic/external-sd-card-missing-after-starting-locus) Looks like my solution was to format the SD card in NTFS. This gives you the option for files bigger than 3GB but also doesn't have the problem which seems to come from exFat format.
Hope this helps you.
Regards,
Tobias
Not sure this helps but I had the same problem. (here: http://help.locusmap.eu/topic/external-sd-card-missing-after-starting-locus) Looks like my solution was to format the SD card in NTFS. This gives you the option for files bigger than 3GB but also doesn't have the problem which seems to come from exFat format.
Hope this helps you.
Regards,
Tobias
Oh no! I was just happy that my CM12 ran so beautiful and bugfree, then I had this same crash!
Bad luck this.
And no solution here.
Since when Android can read and write NTFS???
Oh no! I was just happy that my CM12 ran so beautiful and bugfree, then I had this same crash!
Bad luck this.
And no solution here.
Since when Android can read and write NTFS???
Hm. I will give it a try...
Hm. I will give it a try...
My Godness! This works indeedly, Android (CM12 at least) does be able to write on NTFS!
I made a test with my SGS4 (GT-I9505) running CM12 (the last 2015-04-20 nightly) with a spare 16 GB MicroSD where I put NTFS on it and the Locus directory with only one big vectormap (germany.map) and no problems, all worked. I could copy files on the sd and open them.
Great an many thanks to you Tobias!
My Godness! This works indeedly, Android (CM12 at least) does be able to write on NTFS!
I made a test with my SGS4 (GT-I9505) running CM12 (the last 2015-04-20 nightly) with a spare 16 GB MicroSD where I put NTFS on it and the Locus directory with only one big vectormap (germany.map) and no problems, all worked. I could copy files on the sd and open them.
Great an many thanks to you Tobias!
Hah, glad to hear I was helping someone. Yea, I was quiet surprised myself but hey... it works! :D
Hah, glad to hear I was helping someone. Yea, I was quiet surprised myself but hey... it works! :D
Drawback (Nachteil) of NTFS on Android at least on my device is only:
- CWM/TWRP cannot read it, so a nandroid backup on external sd is not directly usable.
- system cannot copy files bigger than 2GB, so no big (>2gb) map file (e.g. from locus store) can be unpacked from zip or downloaded to external sd. Need a pc for these file operations.
I think the main reason why only locus met these rare SQLite-CM12 bugs is that there are no apps with these huge SQLite databases.
I am on CM12.0 from 20.4.2015, the last CM12 version. Maybe they fix this bug in CM12.1 some day.
By the way, anybody actually reported the bug to CM team?
Drawback (Nachteil) of NTFS on Android at least on my device is only:
- CWM/TWRP cannot read it, so a nandroid backup on external sd is not directly usable.
- system cannot copy files bigger than 2GB, so no big (>2gb) map file (e.g. from locus store) can be unpacked from zip or downloaded to external sd. Need a pc for these file operations.
I think the main reason why only locus met these rare SQLite-CM12 bugs is that there are no apps with these huge SQLite databases.
I am on CM12.0 from 20.4.2015, the last CM12 version. Maybe they fix this bug in CM12.1 some day.
By the way, anybody actually reported the bug to CM team?
Hm, not sure about CM12 but I'm using CM11 (android 4.4) and have the same bug. So at least that's not a CM12 / Android 5 bug only.
Hm, not sure about CM12 but I'm using CM11 (android 4.4) and have the same bug. So at least that's not a CM12 / Android 5 bug only.
Did anybody report this bug in CyanogenMod issue tracker?
Seems to be an old bug if it is already happening under CM11, maybe the CM-team isn't even aware of it?
Did anybody report this bug in CyanogenMod issue tracker?
Seems to be an old bug if it is already happening under CM11, maybe the CM-team isn't even aware of it?
I can confirm that format the ext sdcard in NTFS solve the issue with Locus (although is just a workaround).
I've tested the same maps with orux and didn't have problems. So the problem is a Cyanogen/Locus problem.
Thanks
I can confirm that format the ext sdcard in NTFS solve the issue with Locus (although is just a workaround).
I've tested the same maps with orux and didn't have problems. So the problem is a Cyanogen/Locus problem.
Thanks
OK, I cannot report a bug in the CM-Jira. The threshold is too high (no Xposed module installed, no nightly etc.). So I reported only to the german CM-Forum:
http://www.cyanogenmod-forum.de/Thread-CM-Bug-in-CM-mit-gro%C3%9Fen-SQLite-DBs-auf-extFAT-formatierten-ext-SD-Karten
So I doubt that this bug will ever reach the knowledge of the CM-Team and we most likely will have to live with it, if Menion is not able to find a real workaround in Locus (which is hopefully possible).
@Menion could you please have a look again? If Orux works, Locus could work as well, or? Tell me how I could help to fix if possible. The NTFS workaround becomes more and more unuseful.
Frank
OK, I cannot report a bug in the CM-Jira. The threshold is too high (no Xposed module installed, no nightly etc.). So I reported only to the german CM-Forum:
http://www.cyanogenmod-forum.de/Thread-CM-Bug-in-CM-mit-gro%C3%9Fen-SQLite-DBs-auf-extFAT-formatierten-ext-SD-Karten
So I doubt that this bug will ever reach the knowledge of the CM-Team and we most likely will have to live with it, if Menion is not able to find a real workaround in Locus (which is hopefully possible).
@Menion could you please have a look again? If Orux works, Locus could work as well, or? Tell me how I could help to fix if possible. The NTFS workaround becomes more and more unuseful.
Frank
I have the same problem with lollipop Stock Rom Sony z1c. My smartphone is rooted.
I have the same problem with lollipop Stock Rom Sony z1c. My smartphone is rooted.
I reached one of the CM12 supporter "AntaresOne", he will try to do something. I will send him a complete logfile.
@menion: could you not please re-look into this and maybe find a real workaround?
I reached one of the CM12 supporter "AntaresOne", he will try to do something. I will send him a complete logfile.
@menion: could you not please re-look into this and maybe find a real workaround?
Because of this issue I remove cyanogenmod rom and reinstall a stock Samsung rom on my Galaxy Note II and with stock (4.4.2) I don't have any problem with Locus. So right now I can't help you with log.
Thanks
Because of this issue I remove cyanogenmod rom and reinstall a stock Samsung rom on my Galaxy Note II and with stock (4.4.2) I don't have any problem with Locus. So right now I can't help you with log.
Thanks
Sorry, my SD Card is formatted in NTFS now. But the moment I switch cards I will try...
Sorry, my SD Card is formatted in NTFS now. But the moment I switch cards I will try...
I will do it. I will test it on a spare microsd and surely I will switch back to exFAT if this CM/Locus Bug is fixed/workarounded :)
But at this very moment I wonder why I didn't try FAT32 instead of exFAT, before using NTFS. I have no file on my sd-card bigger than 4 GB and so could easily use FAT32, if this wont bug the same.
So first I try Locus with FAT32 and then I will do a CatLog with exFAT and Locus on CM12 (SGS4).
I will do it. I will test it on a spare microsd and surely I will switch back to exFAT if this CM/Locus Bug is fixed/workarounded :)
But at this very moment I wonder why I didn't try FAT32 instead of exFAT, before using NTFS. I have no file on my sd-card bigger than 4 GB and so could easily use FAT32, if this wont bug the same.
So first I try Locus with FAT32 and then I will do a CatLog with exFAT and Locus on CM12 (SGS4).
1. FAT32 works with Locus and CM12!!! I will go for it then. I have at the moment no file bigger 4 GB, so no need to use NTFS which caused me some other, even worse problems (with files bigger 2 GB).
2. @menion: I just sent you a logcat.zip with 3 logcat in it. A 16 GB sd-card with exFAT, only Locus dir on it, no big files, just one sqlite map with 70 mb. Throws the sd-card out after Locus start.
But one other thing: I have Xposed framework 3.0-alpha4 installed, maybe (I hope not) this is related! I didnt mention it yet, but in the logcat I see entries about it.
Just in case this is related, which I doubt though, I would be able to do again the same logcat without Xposed, when I have more time (because then maybe I have to reset a lot, if a nandroid backup wont restore my rom correctly).
Thanks
frank
1. FAT32 works with Locus and CM12!!! I will go for it then. I have at the moment no file bigger 4 GB, so no need to use NTFS which caused me some other, even worse problems (with files bigger 2 GB).
2. @menion: I just sent you a logcat.zip with 3 logcat in it. A 16 GB sd-card with exFAT, only Locus dir on it, no big files, just one sqlite map with 70 mb. Throws the sd-card out after Locus start.
But one other thing: I have Xposed framework 3.0-alpha4 installed, maybe (I hope not) this is related! I didnt mention it yet, but in the logcat I see entries about it.
Just in case this is related, which I doubt though, I would be able to do again the same logcat without Xposed, when I have more time (because then maybe I have to reset a lot, if a nandroid backup wont restore my rom correctly).
Thanks
frank
For the xposed part I didn't has xposed and had the issues so the problem is not xposed related.
Are there any disadvantages of format a 128Gb sdxc card in Fat32?
Thanks
For the xposed part I didn't has xposed and had the issues so the problem is not xposed related.
Are there any disadvantages of format a 128Gb sdxc card in Fat32?
Thanks
Hello. Since I updated my Samsung Galaxy S4 to Cyanogenmod 12 (Lollipop 5.1.1) I have the same problem!!! I have NO files larger than 4GB and xposed Framework is NOT installed. SD Card has exFAT and 64GB.
Hope this is solved very soon. Locus is my favourite tool for orientation...
Before android update 4.2 everything works well. Did not change Card Filesystem.
PLeaaase
Hello. Since I updated my Samsung Galaxy S4 to Cyanogenmod 12 (Lollipop 5.1.1) I have the same problem!!! I have NO files larger than 4GB and xposed Framework is NOT installed. SD Card has exFAT and 64GB.
Hope this is solved very soon. Locus is my favourite tool for orientation...
Before android update 4.2 everything works well. Did not change Card Filesystem.
PLeaaase
@franc: thank you for your logs.
Crashes in native C++ code are usually my nightmare as I'm not C++ developer. Unfortunately in this case, it is same ...
This is crash clearly visible in your last log, that probably cause detach of SD card. But what this mean ... some Cyanogen mode developer should look at it. It will be a minute for them I think ...
@franc: thank you for your logs.
Crashes in native C++ code are usually my nightmare as I'm not C++ developer. Unfortunately in this case, it is same ...
This is crash clearly visible in your last log, that probably cause detach of SD card. But what this mean ... some Cyanogen mode developer should look at it. It will be a minute for them I think ...
I just have updated my phone to CM12.1 and have same problem too :(
I just have updated my phone to CM12.1 and have same problem too :(
I had already lollipop when I installed Locus Free. It ran without error.
Then I moved it to SD card and had the same mistake. I installed it again -still the same error. If I want to move it back to the Galaxy S4, I get the message: "Can not move".
But suddenly I have no error message regarding the SD card but: "Locus Free, Version 3.9. 3, Start. -->"There are still requires more data." --> If I click on DOWNLOAD, then comes the error: "Unknown problem, problem with internet connection, error code: 44"
I had already lollipop when I installed Locus Free. It ran without error.
Then I moved it to SD card and had the same mistake. I installed it again -still the same error. If I want to move it back to the Galaxy S4, I get the message: "Can not move".
But suddenly I have no error message regarding the SD card but: "Locus Free, Version 3.9. 3, Start. -->"There are still requires more data." --> If I click on DOWNLOAD, then comes the error: "Unknown problem, problem with internet connection, error code: 44"
Thank you, Menion.
I have now uninstalled it again and then installed. It works again. Get it now test and then definitely buy the full version.
Thank you, Menion.
I have now uninstalled it again and then installed. It works again. Get it now test and then definitely buy the full version.
Still same (after clean reinstall from market and from backup also) :(
Still same (after clean reinstall from market and from backup also) :(
Now again I come here, because I have now indeed a file bigger than 4 GB, the german wiki slob-file (for Aard2).
Bad luck and troubles, I cannot use it with FAT32 but I need locus as well so I am in a "Zwiespalt" :(
Look here in Jira:
https://jira.cyanogenmod.org/browse/GETCM-55
an old bug report, was closed, maybe exactly this bug.
Now again I come here, because I have now indeed a file bigger than 4 GB, the german wiki slob-file (for Aard2).
Bad luck and troubles, I cannot use it with FAT32 but I need locus as well so I am in a "Zwiespalt" :(
Look here in Jira:
https://jira.cyanogenmod.org/browse/GETCM-55
an old bug report, was closed, maybe exactly this bug.
Now I posted a bugreport in Jira anyway:
https://jira.cyanogenmod.org/browse/CYAN-6830
Now I posted a bugreport in Jira anyway:
https://jira.cyanogenmod.org/browse/CYAN-6830
Immediately closed, wont be fixed then.
Immediately closed, wont be fixed then.
Replies have been locked on this page!