Hi,
Anyone here noticed if the StickMount is stopped working after the update to JB 4.2? I have tried other mount apps but they all seems to be not working.
They mount the drive alright but the folder is empty. Anything to do with folder structure changed in JB 4.2?
Thanks
http://forum.xda-developers.com/showpost.php?p=34054744&postcount=182
Seems your not the only one.
PS - Did you update OTA or manually? THanks
Same here, Stickmount is not working, it will monut the mass storage but will only show an empty folder in any file explorer. Nexus Media Importer from the Play Store is working well.
dnsp said:
Same here, Stickmount is not working, it will monut the mass storage but will only show an empty folder in any file explorer. Nexus Media Importer from the Play Store is working well.
Click to expand...
Click to collapse
I can't test it right now, but can you verify you still have root after the upgrade? I just found out I lost mine and had to re-root. That could be the reason why it doesn't work.
Chainfire owns a Nexus 7 too. He will fix it soon, I would say.
Im leaning towards the fact its probably the root permissions you described.
As this happened to me when going to 4.1.2
So try to re-root and report back !
rtiangha said:
I can't test it right now, but can you verify you still have root after the upgrade? I just found out I lost mine and had to re-root. That could be the reason why it doesn't work.
Click to expand...
Click to collapse
Yes, rooted with superSU prompt kicking. I also had to re-root after the update.
i Have Root.But StickMount stopped Working.Lets wait..Chainfire will fix it soon hopefully.
Not working here too, did clean install and flashed everything again.
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
I don't think so. I believe it's related to the multiuser feature and the new mount points for /sdcard.
Sent from my Nexus 7 using xda app-developers app
That's my take as well. The new virtual directory structure is mucking things up.
drx69 said:
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
Click to expand...
Click to collapse
You are wrong
Other Chainfire app says everything has full support.
https://www.dropbox.com/s/zp55xc94gngzz8q/2012-11-13 20.45.58.png
drx69 said:
i may be wrong, but i believe that you have to have kernel support. You will probably have to wait until updated custom kernel comes out with otg support.
Click to expand...
Click to collapse
Unfortunately you would be incorrect. I've been using StickMount for USB-OTG on 100% stock rooted 4.1.2 for a while. Sucks it's broke in 4.2 currently but it just came out and I know chainfire will fix it up soon.
yaderly DKC
It's probably due to the new multiuser feature.
I manually mounted an usb flash drive to /mnt/shell/emulated/0/usbdrive.
Now "ls /mnt/shell/emulated/0/usbstick" shows it's content but not for the associated /storage/emulated/0/usbdrive.
So the new multiuser stuff makes the files "invisible" even if the usb flash drive is correctly mounted and can be accessed by root.
any udizes
Wilks3y said:
http://forum.xda-developers.com/showpost.php?p=34054744&postcount=182
Seems your not the only one.
PS - Did you update OTA or manually? THanks
Click to expand...
Click to collapse
Thanks. I updated manually.
StickMount
Updated manually, rooted and SuperSU installed, both Stickmount and USB OTG Helper display display empty folders.
Nexus Media Importer works fine, looks like I'll have to use this until Chainfire gets around to fixing up Stickmount.
i see chainfire has updated SuperSU i was wondering if anyone with 4.2 has any idea if this has helped Stickmount?
Herkfrog said:
i see chainfire has updated SuperSU i was wondering if anyone with 4.2 has any idea if this has helped Stickmount?
Click to expand...
Click to collapse
No the update just delt with apps that require root on the multi user profiles.
Sent from my Nexus 7 using xda app-developers app
pknall said:
Updated manually, rooted and SuperSU installed, both Stickmount and USB OTG Helper display display empty folders.
Nexus Media Importer works fine, looks like I'll have to use this until Chainfire gets around to fixing up Stickmount.
Click to expand...
Click to collapse
I am the "developer" of USB OTG Helper. Please could you be kind enough to try this version and confirm if this works -> http://www.mediafire.com/?wlt084peiksjb1l
The drive(s) are not mounted on sdcard but on /USB-OTG-Drives root folder.
Related
Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix
if you dont have superuser app in your applications then redownload it from the google play store app.
I do have super user but it denies all apps and when I run root checker it sais that its not rooted. I can see the log and everything. I turned root on and off from the settings but nothing.
kipster3001 said:
Hi everyone I just bought an HP touchpad from Craigslist and it was already dual boot for cm9 and webos. I thought that once you had cm9 you could have root access if you turn it on in the settings . I did that but still no root access not working . I've looked for an answer on how to re-root it but I didn't find it .. I would love your help.. so I can do the hulu fix
Click to expand...
Click to collapse
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.
chicle_11 said:
In webos, enable debugging, there's a code you type in, that gets you root.
Look around the webOS nation forum, there are good tutorials there that will help you out.
Click to expand...
Click to collapse
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..
kipster3001 said:
Will it then let me have root access when I boot cm9 . I know the code is webos20090606.
Let me try it..
Click to expand...
Click to collapse
It should. It did for me. And that is the code.
chicle_11 said:
It should. It did for me. And that is the code.
Click to expand...
Click to collapse
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Just flash the first zip in the post above to get root in Android
Enabling Developer Mode in webOS will have no effect on Android Root Access.
Make sure you go to CM Settings and make sure for Developer Options, Root Access is set to Apps and ADB
Also open the Super User app and look at the "Default Action" property and settings and make sure it isn't set to deny.
I'm about to go try this thank you
haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in andro
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse
When I try to flash the zips it said it can't open install aborted
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse
haxin said:
um...no. enabling developer mode in webos will have nothing to do with you having superuser access in android. theres a problem with your superuser binary in cm9, you either need to reinstall superuser, update the su binary, or fix permissions in android.
https://www.box.com/shared/96ae37619313c4cf997b Superuser-3.0.7-efghi-signed.zip
https://www.box.com/shared/7a0720991e80d9d89803 su-bin-3.0.3.2-efghi-signed.zip
Click to expand...
Click to collapse
kipster3001 said:
I'm about to go try this thank you
Click to expand...
Click to collapse
I just downloaded the zip files and there is something wrong with them. I can't open them. Either way, why don't you go into the Google Play Store on your Touchpad and then uninstall the SuperUser app. Then re-install it. After that double check to make sure that you have latest su binaries.
Another toy for us to play with . :silly:http://forum.xda-developers.com/showthread.php?t=2104326
App at Play Store https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix
It's not working on our device
DooMijasz said:
It's not working on our device
Click to expand...
Click to collapse
works on mine though I've actually not had time to read the thread yet .I've been a bit busy since I saw it .
But the one thing I recall reading is that you will see errors running it if it isn't compatable with your device.
Seeing zeros or numbers is fine.
I'm seeing no errors and saw numbers when I ran it .
What have I missed ?
Anyone else tried it ? I've seen it's had a few looks but no responses.
einstein.frat does your ROM mounts /data with -discard ?
Though I did see a few posts down one guy got rid of the mount /data with -discard script on his phone and switched to using this app as it worked better for him .
On my HTC Desire C i get error
fstrim -v /data(or cache it depends on what You will use this APP)
fstrim: FSTRIM: Operation not supported on transport endpoint
wich means our device is not suported and Lagfix does nothing for us. Check thread Page 9, same error for LG L5-610. OP explained that this error appear when device is not supported.
DooMijasz said:
On my HTC Desire C i get error
fstrim -v /data(or cache it depends on what You will use this APP)
fstrim: FSTRIM: Operation not supported on transport endpoint
wich means our device is not suported and Lagfix does nothing for us. Check thread Page 9, same error for LG L5-610. OP explained that this error appear when device is not supported.
Click to expand...
Click to collapse
Thats seems odd.I installed this app and works well(I dont get any error anways)
Try installing busybox from playstore and retry.Errors might be due to this busy box issues.
nikhil16242 said:
Thats seems odd.I installed this app and works well(I dont get any error anways)
Try installing busybox from playstore and retry.Errors might be due to this busy box issues.
Click to expand...
Click to collapse
Still the same error after installing new busybox from playstore.
I wonder if this problem is related to that, that 90% of your customizer scripts are not working on my device oO Just a lot of "No such file or directory" or "command not found" errors
Did you open the busybox and installed it from within (just verifying).
Sent from my HTC Desire C using xda app-developers app
Just check your busybox location . I've come across the odd recomendation to try system/xbin rather than system /bin . Also I always install it as a smart install (replace all(symlinks all)) and clean mode .(just in case this is the difference)
DooMijasz said:
Still the same error after installing new busybox from playstore.
I wonder if this problem is related to that, that 90% of your customizer scripts are not working on my device oO Just a lot of "No such file or directory" or "command not found" errors
Click to expand...
Click to collapse
Just noticed what you wrote . I'd guess you have an issue with your phone somewhere. Either Busybox or some other issue. What it is I have no clue . It's worth starting a new thread I think to see if one of the Gurus has an idea what is wrong .
nikhil16242 said:
Did you open the busybox and installed it from within (just verifying).
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Busybox installed from within with SMART INSTALL option. Idk whats wrong. I have exploss!on 2.1.1 rom installed.
DooMijasz said:
Busybox installed from within with SMART INSTALL option. Idk whats wrong. I have exploss!on 2.1.1 rom installed.
Click to expand...
Click to collapse
we are running Nameless . It could very well be your Rom . I've seen a few issues cropping up with Explosion lately unfortunately .
hey guys, what's your experience, does it worth to install?
neoyoli said:
hey guys, what's your experience, does it worth to install?
Click to expand...
Click to collapse
It's hard to say but that is entirely mine (our) own faults.
From my understanding (and I could be wrong) this is an implimentation of the Trim function they took so long to get on and working for ssds. This is ovbiously a good thing if I'm right.
Where it's hard to tell is because I/we are constantly flashing our phones. Most of the time I do a full wipe which does exactly the same action as ftrim . So atm I don't believe I've actually run the phone long enough to need to use it or should I say take proper advantage of it .
It's only meant to be run once a week so I'm keeping with it for the quiet times when I won't be flashing . I'll get to actually see how it works then .(maybe I'll try and do the next few updates as dirty flashes)
hope that helps
doea lagfree realy work ?
does it really work ?
To all KITKAT ROM USERS having problems in installing apps from play store:
If you have tried to install an app and got an error message: COULDN'T INSTALL IN USB STORAGE OR SD CARD,
1. DOWNLOAD and INSTALL SELINUX MODE CHANGER from play store. (Make sure that you have supersu installed and your phone rooted obviously). Grant permission access to SELinux mode changer when supersu prompts you.
2. OPEN SELINUX MODE CHANGER AND CHANGE SELINUX permission to PERMISSIVE.
3. INSTALL THE APP which you wanted for your phone.
Enjoy.
N.B. You can change the permission to ENFORCING after installing the app you wanted.
Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD
This is also how to get Cydia Substrate working on 4.4
Sent from my GT-I9100G using Tapatalk 4
ottomatteseo said:
Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Hi ottomatteseo. Did it work?
Omni rom don't have selinux
so how i install the app?
Fighting Dreamer said:
Omni rom don't have selinux
so how i install the app?
Click to expand...
Click to collapse
HI Fighting Dreamer. Omnirom has SELinux. But its mode in Android 4.4 is set to ENFORCING by default. I suspect that this is one of the reasons why we get the error message upon installing some apps which worked for previous android versions and rom.
Anyway, just download SELinux mode changer from playstore and follow the above instructions then install the app which gave you the error message. Update me if it worked for you. Good luck
rarjonillo said:
Hi ottomatteseo. Did it work?
Click to expand...
Click to collapse
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD
ottomatteseo said:
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Glad it worked for you.:good:
worked
thanks
alkasser011 said:
worked
thanks
Click to expand...
Click to collapse
Great.
This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.
Mll4eveR. said:
This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.
Click to expand...
Click to collapse
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.
rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I just flashed 4.4 and set SE Linux mode in "permissive" and updated to 4.4.1. The mode appeared to be "permissive" indeed in 4.4.1 but somehow the "couldn't install app in usb and sd card" error persisted.
I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18
Mll4eveR. said:
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.
Click to expand...
Click to collapse
colorprint said:
I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18
Click to expand...
Click to collapse
I think it's high time to report this to ryuinferno and jiangyi (developers of the CM11 and omni roms respectively).It may be caused by either the rom or still the specific app since there are some which are still not working with the 4.4 structure http://forums.androidcentral.com/google-nexus-5/331321-apps-do-not-work-currently-n5-4-4-a.html.
I'll report this. Thanks!
This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...
colorprint said:
This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...
Click to expand...
Click to collapse
Please see this. https://www.xda-developers.com/android/android-4-4-kitkats-art-and-app-compatibility/. Thanks.
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
pqueiro said:
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
Click to expand...
Click to collapse
Trying to update the game e get the message "your device isn't compatible with this version"
Rcpbarba said:
Trying to update the game e get the message "your device isn't compatible with this version"
Click to expand...
Click to collapse
I just updated from 1.0.2 to 1.1.0 and keep getting the same error message as before (the good old 803-3001).
This is supposed to be a connection error message, but it doesn't make sense -- if I hotspot off my magisk'd OP3T to a stock OPO or a stock iPad, the game works fine, so it stands to reason the connection is good.
Hence my suspicion that it's probably a SafetyNet issue (FE:H, like PoGo, uses SafetyNet -- might be a Nintendo thing). Any idea how to get around it?
Thanks!
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
pqueiro said:
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
Click to expand...
Click to collapse
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Didgeridoohan said:
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Click to expand...
Click to collapse
Well now, that's substantially more complicated and probably out of my league I'll have to stick to playing it on the iPad. It's not impossible, just annoying.
Thanks!
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
panchovix said:
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
Click to expand...
Click to collapse
The plot thickens. Let me check on my "playground" phone if I can replicate that.
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Klassikal said:
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Click to expand...
Click to collapse
FYI, tried this (took the opportunity when updating Oxygen OS) and it worked a treat! All is good. Backup > unroot > update > install > magisk all the things and it's working fine.
Thanks!
I have two G9+ phones, both rooted with Adaway installed. One has the stock ROM (Android 10) & the other has LineageOS 18.1.
On the phone with Lineage there are no ads when running a particular game. The same version of the game on Moto Android 10 has ads.
There is some app I don't understand called Moto GameTime that appeared when I started the game but I have disabled it. (I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Still, Google ads appear with the stock ROM despite having Adaway.
Everything looked ok in Adaway. It tells me its three sources are up to date. When I try to reload & reinstall hosts from those sources I get an error: "Unable to copy hosts file to /system partition. Please check Magisk systemless module is enabled the reboot." (Magisk Manager shows Magisk 23.0 is installed.)
Something is causing problems that seem to involve lack of access to the /system partition. I don't know if that is related to the appearance of ads on the stock ROM, but any thoughts? How can I fix this?
As I've stimulated no response here, I took the ugly step of wiping the phone, flashing the experimental LineageOS and restoring everything from backup (not a fully successful process because the data for certain apps was not backed up by Super Backup & Restore).
At least there are now no ads getting through onto the phone.
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w. There is a workaround for it (currently in development stages). It's a flash able zip script that dumps the super partition "fixes" it and flashes it back. Your phone must have the bootloader unlocked and be rooted for it to work. It currently works for A only devices without any issues, but is throwing an lpmake error 73 for mysterious/unknown reasons, but a fix is in the works. I will post a link when I get home.
I assume the phone is rooted with Magisk which is a systemless root method. Even with older devices /system remains unmodified. All changes are only overlays/modules managed by the Magisk App.
doktorspin said:
(I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Click to expand...
Click to collapse
This could also be done with a own module. See instructions here.
Keven11 said:
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w.
Click to expand...
Click to collapse
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I fixed the issue by ditching Android 10 for LOS 18.1. But thanks for the pointer.
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I'm glad you got it figured out. The data issue, along with many other bugs will be rectified any day now with the new release. The issue you are having with LOS 18.1 is because at the time of development the kernel for A11 hadn't been released by Moto yet. However, they did finally release it a little under 2 weeks ago. So the new version of it will be much much better. It will be linked to the same link I posted. It's just a matter of time now, and not much of it.
Telegram Odessa Devs and testers group: https://t.me/joinchat/SaZ2BX0M8bQmkioW