-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reboot loop #157
Comments
If you tap on the icon in the lower right corner of ATAK (it looks kinda like a T-Beam) and go to the Logging tab do you see anything? You may want to change the logging level to Debug in the ATAK Forwarder settings. |
Dear Paul,
Thank you for helping with this. I have looked at the debug log. What
should I be looking for. I can tell you that when I turned on “Disable
writting to Comm Device”, the resetting loop stopped, but I wasn’t able to
communicate with the other ATAK devices.
…On Sun, Feb 19, 2023 at 12:51 PM paulmandal ***@***.***> wrote:
If you tap on the icon in the lower right corner of ATAK (it looks kinda
like a T-Beam) and go to the Logging tab do you see anything? You may want
to change the logging level to Debug in the ATAK Forwarder settings.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5GP3NDK4RP2P3W6JMS5P2LWYJTTPANCNFSM6AAAAAAUZYRPS4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am having a similar issue, everything worked before I rebooted my device. Galaxy S10E (US) ATAK 4.7.04 Using Meshtastic settings for channel info. ATAK, Mesh, and Forwarder were working fine, I restarted my phone and now ATAK constantly crashes when opening. `Native crash report {"TAK.sessionid":"f92a539f-a18e-42b3-bf5a-f4fc33d09a82", ********** Stack trace follows: #0 - 0x705a55fb20 ********** End of stack trace`
After removing the forwarder plugin ATAK loads no issues. |
The reboot loop is likely caused by the plugin writing the channel config every time, this will be patched in the next release. |
Thank you! I really appriciate you.
…On Sun, Feb 26, 2023 at 8:46 AM paulmandal ***@***.***> wrote:
Closed #157 <#157> as
completed via #159 <#159>
.
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5GP3NF67C45FNLTQCESHMDWZNUC7ANCNFSM6AAAAAAUZYRPS4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@Jamesmckain19 No problem, I hope this fixes the issue! |
Great work, thanks for the speedy review! |
The same problem still, unfortunately, I completely re-loaded everything, fresh installs. ATAK crashes a soon as the plugin is installed. Same error in the stack trace: "TAK.error":"java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference", |
Can you provide the rest of the fresh stack trace and the version of ATAK
you're using please?
…On Sun, Feb 26, 2023, 15:58 Kevin Levitz ***@***.***> wrote:
The same problem still, unfortunately, I completely re-loaded everything,
fresh installs. ATAK crashes a soon as the plugin is installed.
Same error in the stack trace:
"TAK.error":"java.lang.NullPointerException: Attempt to invoke virtual
method 'boolean java.lang.String.equals(java.lang.Object)' on a null object
reference",
—
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7YLS5UUFU7P7EWOW65B5TWZPNZXANCNFSM6AAAAAAUZYRPS4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Here is the full trace: https://drive.google.com/file/d/19UPeAO4wDAgSnh1ZKVj90nWfxy7-N35V/view?usp=sharing This was before after just updating and then after I deleted the forwarder plugin, delete meshtastic, delete ATAK, delete ATAK folder, reboot the phone, rest Meshtastic device(lora tbeam but the same issue is happening on my RAKs), and reinstall in order of Meshtastic>ATAK>Forwarder |
Paul,
First, thank you for this awesome tool! I appreciate the work you put in and shared with us.
I am having an issue when I connect my Meshtastic device (Lilygo Lora32) to the Meshtastic app, everything functions as expected. When I run it through the ATAK forwarder, however, the meshtatic device gets caught in a reboot loop.
Do you have any thoughts or suggestions.
Thank you in advance!
The text was updated successfully, but these errors were encountered: