Skip to content
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

Daemon terminated, please restart daemon #38

Open
SergiAlcala opened this issue Dec 14, 2020 · 23 comments
Open

Daemon terminated, please restart daemon #38

SergiAlcala opened this issue Dec 14, 2020 · 23 comments

Comments

@SergiAlcala
Copy link

Versions

  • OS: Android 11
  • Python version: python3
  • Device:: Google Pixel 4a 5G
    *Build Version: RD1A.200810.021.A1, Oct 2020

Description

I've installed the MI v6.0 in Google Pixel 4a 5G, rooted and everything seems to be correct, but when I try to run the NetLogger plugin, I receive a warning saying:

"Monitoring daemon is terminated. Restart the daemon".

I attach a link with the MI Log.

https://drive.google.com/file/d/1BFwi23sRZtDDXoKvCsGqtjhtZC5DN7a1/view?usp=sharing

Thank you

@yuanjieli
Copy link
Member

Thanks for your feedback. We observed similar issues on Google Pixel 5, and found it is because Google has recently disabled the diagnostic mode in their latest Pixel phone models. We are fixing it now.

To work it around, you many try to flash some 3rd-part custom ROM with root privilege and diagnostic mode to your Google phone, or try some other models.

@SergiAlcala
Copy link
Author

Thanks for your feedback. We observed similar issues on Google Pixel 5, and found it is because Google has recently disabled the diagnostic mode in their latest Pixel phone models. We are fixing it now.

To work it around, you many try to flash some 3rd-part custom ROM with root privilege and diagnostic mode to your Google phone, or try some other models.

Thank you for your response, do you recommend any custom ROM for this usage?

Kind Regards

@Awais174
Copy link

Awais174 commented Jan 6, 2021

@yuanjieli I have faced the same issue on the same mobile phone.

I might be able to contribute - are you planning to enable mobileinsight application to enable diagnostic mode itself?

@yuanjieli
Copy link
Member

Yes, we are working on it now.

@lgs96
Copy link

lgs96 commented Apr 12, 2021

Hi, I'm facing the same problem on Pixel 5. Is the problem solved in the latest version? (dev6.0-pixel)

@lnxgod
Copy link

lnxgod commented Apr 28, 2021

I'm running into the same issue. I have no issue switching firmwares if you can suggest a firmware thats friendly with your software.

@lnxgod
Copy link

lnxgod commented May 5, 2021

I've switched to Lineage 18.1 same issue.

@lnxgod
Copy link

lnxgod commented May 5, 2021

What other model?

@yuanjieli
Copy link
Member

Thanks for your feedback. Please check the following APK to see if it works on your phone:

https://github.com/mobile-insight/mobileinsight-mobile/releases/download/v6.0.0-beta/MobileInsight-6.0.0-beta.apk

@ltshandsome
Copy link

ltshandsome commented Jun 1, 2021

@yuanjieli I tried the new APK file using Google pixel 5. It doesn't show the string "Monitoring daemon is terminated. Restart the daemon" anymore, but it seems that the plugins don't collect anything and I don't know why:

Netlogger: when stop the plugin, it will show "Found undersized orphan log, file saved to ..." and the file size is 0 B.
RrcAnalysis and KPIAnalyzer: attached

Thank you

NetLogger_log[1].txt
RrcAnalysis_log[2].txt
KPIAnalyzer_log[1].txt

@why36
Copy link

why36 commented Nov 25, 2021

@yuanjieli I got the same problem with rooted MI 10, OS version: Android 10
"Monitoring daemon is terminated. Restart the daemon". always appear whatever plugin I chose.
Besides /dev/diag does not appear in my phone. However, MI 10 is the model you have tested on the website?

Do you have some idea for this?

@noahsmartin
Copy link

I'm seeing the same problem with a pixel 5 on Android 12 build # SP2A.220305.012 using 6.0.0 beta, are there any workarounds for this phone?

@limlynn
Copy link

limlynn commented Jun 1, 2022

I'm seeing the same problem with a pixel 5 on Android 11. Are there any improvements to this problem? BTW, Thank you for your dedicated work and support.

@hur
Copy link

hur commented Oct 7, 2022

pixel 5, android 11 AND 12, same issue (No logs appear). From dmesg, I can see:
[ 130.377138] diag: In diag_switch_logging, request to switch to invalid mode: 1061109567 the number is 0x3F3F3F3F in hex.

@SmartCar11
Copy link

Versions

  • OS: Android 11
  • Python version: python3
  • Device:: Google Pixel 4a 5G
    *Build Version: RD1A.200810.021.A1, Oct 2020

Description

I've installed the MI v6.0 in Google Pixel 4a 5G, rooted and everything seems to be correct, but when I try to run the NetLogger plugin, I receive a warning saying:

"Monitoring daemon is terminated. Restart the daemon".

I attach a link with the MI Log.

https://drive.google.com/file/d/1BFwi23sRZtDDXoKvCsGqtjhtZC5DN7a1/view?usp=sharing

Thank you

Hello, I had the same problem with google Pixel 5, did you fix the problem ? thanks

@lnxgod
Copy link

lnxgod commented Mar 29, 2023 via email

@SmartCar11
Copy link

The only way I could get it to work was to run an older version of the operating system. They remove some of the debug things in the newer operating system and it doesn't work.

On Wed, Mar 29, 2023, 11:03 AM Younes ST @.*> wrote: Versions - OS: Android 11 - Python version: python3 - Device:: Google Pixel 4a 5G Build Version: RD1A.200810.021.A1, Oct 2020 Description I've installed the MI v6.0 in Google Pixel 4a 5G, rooted and everything seems to be correct, but when I try to run the NetLogger plugin, I receive a warning saying: "Monitoring daemon is terminated. Restart the daemon". I attach a link with the MI Log. https://drive.google.com/file/d/1BFwi23sRZtDDXoKvCsGqtjhtZC5DN7a1/view?usp=sharing Thank you Hello, I had the same problem with google Pixel 5, did you fix the problem ? thanks — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASK3D7FJ536W4QR7UH5AM23W6R2NRANCNFSM4U2OOUBQ . You are receiving this because you commented.Message ID: @.>

Hi @Inxgod,

Thanks for your response, I have changed the version of the phone and resolve the problem of daemon but when I run the log I get an empty log 0Kb. Have you faced the same problem?
thanks in advance.

@cellular777
Copy link

The only way I could get it to work was to run an older version of the operating system. They remove some of the debug things in the newer operating system and it doesn't work.

On Wed, Mar 29, 2023, 11:03 AM Younes ST @.> wrote: Versions - OS: Android 11 - Python version: python3 - Device:: Google Pixel 4a 5G _Build Version: RD1A.200810.021.A1, Oct 2020 Description I've installed the MI v6.0 in Google Pixel 4a 5G, rooted and everything seems to be correct, but when I try to run the NetLogger plugin, I receive a warning saying: "Monitoring daemon is terminated. Restart the daemon". I attach a link with the MI Log. https://drive.google.com/file/d/1BFwi23sRZtDDXoKvCsGqtjhtZC5DN7a1/view?usp=sharing Thank you Hello, I had the same problem with google Pixel 5, did you fix the problem ? thanks — Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASK3D7FJ536W4QR7UH5AM23W6R2NRANCNFSM4U2OOUBQ . You are receiving this because you commented.Message ID: _@.*>

Hi @Inxgod,

Thanks for your response, I have changed the version of the phone and resolve the problem of daemon but when I run the log I get an empty log 0Kb. Have you faced the same problem? thanks in advance.

@SmartCar11 @lnxgod I have the same issue. Pixel 4a 5G. I tried Android 13 and got daemon errors. I tried Android 11 and get empty logs. Is there a certain version of Android's OS that does work? Any other options?

@yuanjieli is there an updated list of devices (besides the one on the website) that recommends any that are 5G capable? Assuming there is no way to get this to work with the Pixel 4a 5G.

@hur
Copy link

hur commented Aug 4, 2023

For the record, I was able to use Pixel 5 with Android 11 build RQ2A.210305.006. Any newer Android versions did not work because of empty logs since I don't know how to enable diag on the newer versions. I followed https://band.radio/diag to enable diag on this android version.

@cellular777
Copy link

@hur Thank you for the information. I have tried those same instructions for diag with RD1A.200810 (empty logs) and RQ3A.211001 (daemon errors). Ha, I didn't try RQ2A, maybe that is a sweet spot. I will report back.

@cellular777
Copy link

@hur very strange. I did not try RQ2A. I am still on RQ3A.211001 and it is now working. What is weird is that I already ran the commands from https://band.radio/diag though I was following https://forum.xda-developers.com/t/network-signal-guru.4005511/page-4#post-83499679 which has the exact same commands. Hmm. Idk, maybe I rebooted or ran something in the wrong order.

Either way thanks for responding. I can see message logs now.
I have a chicken and egg problem though. I can only get LTE connections (even with the network ##4636## set to both LTE/NR. However, if I upgrade to Android 13 I get NR connections fine (normally happens when I play a video. But, I can't go to Android 13 because of the daemon issues and diag issues...

I do wonder, are you able to see 5G NR logs on the Pixel 5? This would be NSA stuff.

@hur
Copy link

hur commented Aug 4, 2023

@hur very strange. I did not try RQ2A. I am still on RQ3A.211001 and it is now working. What is weird is that I already ran the commands from https://band.radio/diag though I was following https://forum.xda-developers.com/t/network-signal-guru.4005511/page-4#post-83499679 which has the exact same commands. Hmm. Idk, maybe I rebooted or ran something in the wrong order.

Either way thanks for responding. I can see message logs now.
I have a chicken and egg problem though. I can only get LTE connections (even with the network ##4636## set to both LTE/NR. However, if I upgrade to Android 13 I get NR connections fine (normally happens when I play a video. But, I can't go to Android 13 because of the daemon issues and diag issues...

I do wonder, are you able to see 5G NR logs on the Pixel 5? This would be NSA stuff.

I was working with LTE logs only so can't say for sure, sorry, although someone I was working used the same setup as me for some 5G logs if I recall correctly.

The daemon errors can be fixed by patching diag_revealer with the right logic and struct definitions for the particular kernel version, but enabling diag may be problematic on newer devices, I spent hours on it but couldn't get it working on Android 12

@langzhou11
Copy link

langzhou11 commented Oct 30, 2024

For the record, I was able to use Pixel 5 with Android 11 build RQ2A.210305.006. Any newer Android versions did not work because of empty logs since I don't know how to enable diag on the newer versions. I followed https://band.radio/diag to enable diag on this android version.

I couldn’t get the Pixel 5 with Android 11 build RQ2A.210305.006 to work successfully. After following the guide on https://band.radio/diag to enable diag, I connected to my computer with ADB. Then, using the command adb shell and ls -l /dev/diag, I could access /dev/diag on the phone, which seems to confirm diag is enabled. However, when I used the NetLogger plugin in the MobileInsight 6.0.0 APK, the mi2log files were 0 KB. The same thing happened when I tried the desktop version of MobileInsight—the mi2log files were also 0 KB. Has anyone experienced something similar or knows the reason for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests