Related
GMusicFS exposes cloud Google Music as a FUSE filesystem on rooted devices
EDIT 09/10/2015: v1.0.15 released, fixed Google Music issues
EDIT 02/20/2015: v1.0.14 released, Lollipop compatible, fixed Google Music issues
EDIT 03/03/2014: v1.0.12+ has no restrictions anymore (100% free). It is not available anymore on Google Play and you can download the APK below instead.
This app is provided "as is" and may not be working properly with some ROMs and/or kernels. It is unsupported and not actively developed.
This app doesn't work with all kernels which explains reboots on some devices.
This app does tricky and hacky things that may not work well on all devices or unreliably.
It's even a miracle that it sort of works on current Android.
You can use it if it works on your device and find it useful, but most people should use the official Google Music app instead.
There will be no bug fixes as I stopped entirely developping it.
Maybe there will be an update if the next Android version breaks it again and there's an easy fix, but that's all you can expect at this point.
Download APK v1.0.15
Documentation
Short youtube video
The goal is to bring Google Music streaming support to most third party music players like Poweramp, PlayerPro, n7player and many more.
From the point of view of these apps, Google Music tracks will look like regular files that can be played.
I you ever wanted to play Google Music with something else than the Google Music app, that should fit the bill.
Make sure to read the Help section within the app as it contains very important usage info (especially on Android 4.2+) and music player specific initial setup.
Requirements
a rooted device running Android 4.1+ on ARM, or x86 (untested) CPU. Root is necessary for mounting the filesystem
A kernel supporting FUSE filesystems (should be the case of all 4.0+ kernel)
SuperSU or Superuser
Some music uploaded to the Google Music service
A compatible third party music player. Tested working with Poweramp, Winamp, PlayerPro, n7player. Should work with most players using the Android MediaPlayer API or ffmpeg. Doesn't work with Deadbeef and XenoAmp.
Recording a log file
Here's how to setup logging, to troubleshoot issues.
Do not post log files on the forum or on the web as they contain your Google account name.
start GMusicFS
in the Settings tab, enable Logging (select "App" as the logging mode, unless being instructed otherwise), then click the "Exit" button to exit the app
restart the app and operate the app until the error appear
exit the app
send me (bubbleguuum at free.fr) the log file located on your SD Card as file Android/data/com.bubblesoft.android.gmusicfs/logs/log.txt
Re: [APP][4.0+][ROOT][BETA] GMusicFS: play cloud Google Music in most music players a
It looks very promising, but does not seem to work on my sensation running CM 10.1 (see screenshot)
Sent from my HTC Sensation using Tapatalk 2
Edit: fixed some ugly formating caused by Tapatalk
@hobbypunk:
Thanks for the report. I'll install CM 10.1 on one of my device to see how it goes. I'm not actually that surprised that mounting is not working on some ROMs. For now, I only tested on Nexus 4 and Nexus 7 running stock rooted ROM as well as my old SGS with CM10 (4.1.2).
Re: [APP][4.0+][ROOT][BETA] GMusicFS: play cloud Google Music in most music players a
Great app, I love finally having my Google music in player pro. It's a bit of a drain on battery and ram and needs a bit more buffering, but it's great for a beta!
R: [APP][4.0+][ROOT][BETA] GMusicFS: play cloud Google Music in most music players ap
hobbypunk said:
It looks very promising, but does not seem to work on my sensation running CM 10.1
(see screenshot)
Sent from my HTC Sensation using Tapatalk 2
Click to expand...
Click to collapse
Same here on Galaxy Note 10.1 N8000 running Cm10.1
Sent from my N8000 using Tapatalk HD
Failed to create folder
The app gets to about the 10th album and says it is unable to create the folder on the SD card. Have tried multiple times but it always stops. Have created the named folder myself but still get the same error. On CM10.1 on Xperia ARC.
Keep up the good work though this is exactly what I am after. Get it all working and name your price
@TheMorpheus, @hobbypunk:
I could somewhat reproduce this "permission denied" error. It seems to happen if the SuperSU popup asking for root is not clicked before the countdown reach 0. It is not related to a specific ROM.
There are 2 such popups displayed the very first time the app is started:
- the first one is displayed immediately on app start and ask permission for GMusicFS
- the second popup is displayed the first time the filesystem is mounted (which can happen way later, after initial sync) and ask permission for "ADB shell"
To force these 2 popups to reappear can you do this and report if it fixes the problem:
- exit GMusicFS if it is started (cross button on top)
- launch the SuperSU app and remove both GMusicFS and "ADB shell" from the apps list (long-click on app and "Forget").
- Restart GMusicFS. It will show the first popup (on app start) and the second permission popup (during mounting). Answer "Grant" to both before the countdown reach 0.
cdkane said:
The app gets to about the 10th album and says it is unable to create the folder on the SD card. Have tried multiple times but it always stops. Have created the named folder myself but still get the same error. On CM10.1 on Xperia ARC.
Keep up the good work though this is exactly what I am after. Get it all working and name your price
Click to expand...
Click to collapse
Thank you for the report. Can you record and send me a log file (bubbleguuum at free.fr):
- start GMusicFS
- in the Settings tab, enable Logging (select "App" as the loggin mode), then click the "Exit" button to exit the app
- restart the app and operate the app until the error appear
- exit the app
- send me the log file located on your SD Card as file Android/data/com.bubblesoft.android.gmusicfs/logs/log.txt
Thanks!
bubbleguuum said:
@TheMorpheus, @hobbypunk:
I could somewhat reproduce this "permission denied" error. It seems to happen if the SuperSU popup asking for root is not clicked before the countdown reach 0. It is not related to a specific ROM.
There are 2 such popups displayed the very first time the app is started:
- the first one is displayed immediately on app start and ask permission for GMusicFS
- the second popup is displayed the first time the filesystem is mounted (which can happen way later, after initial sync) and ask permission for "ADB shell"
To force these 2 popups to reappear can you do this and report if it fixes the problem:
- exit GMusicFS if it is started (cross button on top)
- launch the SuperSU app and remove both GMusicFS and "ADB shell" from the apps list (long-click on app and "Forget").
- Restart GMusicFS. It will show the first popup (on app start) and the second permission popup (during mounting). Answer "Grant" to both before the countdown reach 0.
Click to expand...
Click to collapse
I still can't see a second popup asking for access to ADB shell, synced well over 10 minutes ago. Exited app, got SuperSU to forget app, did it again, first popup appeared straight away, granted it, but still no second popup.
Nitroz said:
I still can't see a second popup asking for access to ADB shell, synced well over 10 minutes ago. Exited app, got SuperSU to forget app, did it again, first popup appeared straight away, granted it, but still no second popup.
Click to expand...
Click to collapse
In the SuperSU apps list, is there an entry titled "ADB shell" ?
Btw make sure to update to the latest version of SuperSU, just in case.
bubbleguuum said:
In the SuperSU apps list, is there an entry titled "ADB shell" ?
Btw make sure to update to the latest version of SuperSU, just in case.
Click to expand...
Click to collapse
nothing in the apps list for 'ADB Shell' just the app name. Also updated to latest SU, made no difference, still have mount errors.
Wish you all the best with this project. With an 8GB Nexus 4 Google Music is a must for me, but sadly the official app pales in comparison to 3rd party players.
edit: I set it to 50 songs to test, works great. Used Noozy audio player.
I should probably add I'm getting error code 1. I'll get a log.
Nitroz said:
nothing in the apps list for 'ADB Shell' just the app name. Also updated to latest SU, made no difference, still have mount errors.
Click to expand...
Click to collapse
Ok, I'll have to research why SuperSU is not prompting for adb shell in some cases. In any case, that is the reason for the mount error.
Nitroz said:
nothing in the apps list for 'ADB Shell' just the app name. Also updated to latest SU, made no difference, still have mount errors.
Click to expand...
Click to collapse
I think I've found the cause of SuperSU not asking for "adb shell" permission: on CyanogenMod only, there is a specific setting that must be enabled to allow root adb execution.
Go into the Settings of the phone. In the "System" section, if you do not have the "Developer options" menu entry, you must enable it.
To enable it, go into the "About phone" menu and click on "Build number" 7 times.
Then, in Settings > Developer options, change "Root access" to "Apps and ADB" (I think the default is just "Apps").
Restart GMusicFS (no need to sync again) and it should ask for permission (will do it only once) when mounting.
Wow thank you for this great app. Works great with Power Amp. I searched for a way to see only the music that is available on my google account and exclude the music that is on my device and haven`t found a way to do so until now. Thanks again for this great app
The only "problem" I have right now is that I have over 100 album folders and it would be great if I wouldn`t see those 100 folders but just the songs that are in those folders. Is this possible?
Edit:
Ok found out how to do it on Power Amp. just press on the little arrow which is right from the "Albums" folder and then hit "Enqueue" and it will transfer all the songs into your library under Queue.
Re: [APP][4.0+][ROOT][BETA] GMusicFS: play cloud Google Music in most music players a
bubbleguuum said:
I think I've found the cause of SuperSU not asking for "adb shell" permission: on CyanogenMod only, there is a specific setting that must be enabled to allow root adb execution.
Go into the Settings of the phone. In the "System" section, if you do not have the "Developer options" menu entry, you must enable it.
To enable it, go into the "About phone" menu and click on "Build number" 7 times.
Then, in Settings > Developer options, change "Root access" to "Apps and ADB" (I think the default is just "Apps").
Restart GMusicFS (no need to sync again) and it should ask for permission (will do it only once) when mounting.
Click to expand...
Click to collapse
Perfect. Working on cm10.1 using poweramp.
Sent from my HTC Sensation using Tapatalk 2
Works well, mostly, until you get a spot of bad reception, then it starts skipping a lot. I suppose you haven't implemented buffering yet?
Also, planning on finding a way around having to have the notification and remount button? perhaps a list of watched apps to automatically remount?
Logcat emailed as requested. Hopefully it helps and I can start using this awesome app soon!
This is awesome! I got it to work on my DNA running Viper 1.1.3.
It sync'd through the letter D, but then error'd saying "...mp3: open failed: ENAMETOOLONG (File name too long)".
Working great on artists A-D though.
Hello,
Is anyone on Honor 8 / EMUI 4.1 able to get chrome notifications?
I've been checking Chrome settings and found nothing wrong, expect for the fact I don't seem to be able to add chrome to the list of apps that can ignore battery optimization, since it is not listed. I'm not sure if this is the reason though.
Please share your ideas / suggestions.
RM
It's because Chrome is a system app already so it is by default protected. Except it doesn't even work correctly probably because of their ram management, which kind of make this phone useless for receiving notification for me.
I tried adding Google Clock and S-Health to protected apps and also lock it in the "recent apps" menu, they still get forced close and the alarm didn't ring or it stopped counting steps.
I haven't used EMUI5 yet to know if it's fixed.
Hello!
Solution found! The hint (system app) of the previous post made me try this:
1-Uninstall Chrome (using TiBu - root needed)
2-Reinstall Chrome from Play Store
3-Configure settings to allow notifications from wanted pages
4-Add Chrome to the list of apps that can ignore battery optimizations
So far it is working as expected...
About the other notification issues I've faced before (Google Keep, WhatsApp,...) I've solved it after enabling "keep mobile data on when sleeping", besides adding the app to the ignore battery optimization list, of course.
RM
I have found that same exempt setting as well, unfortunately Chrome isn't in the list so I guess that's why you have to root to remove it first and readd it as third party app for it to show up.
To much effort to just get notification working, a basic feature of all phones and risk losing warranty and Android Pay access.
To make it clear for others:
1. add the app to the Protected apps list (settings - advanced settings - battery manager - protected apps).
2. go to settings - apps - advanced - exempt from battery optimization - select the drop down list and and select "all apps" - find your app and set it to allow.
Huawei programmers must have pride themselves in putting settings inside convoluted maze that's impossible to find.
You might also want to add Settings - Advanced Settings - Battery Manger - Upper right gear - keep mobile data on during sleep.
I second you about this kind of maze that we must run to just have notifications, but, on the other hand I'm kind of OK with it, as soon I can find a way to solve matter!
RM
*****UPDATE APRIL 5, 2018 - This guide will activate the FULL Google Assistant!***** USE THIS GOOGLE APP AS OF DECEMBER 8 2018, https://www.apkmirror.com/apk/googl...oogle-app-8-33-6-21-arm-android-apk-download/
Many of you probably recall my last guide on getting 'ok Google' to work. Well Sort of: How to guide: Enable 'ok Google' to work from ANY screen. You may also recall it was a bit of work to get it working and the downside was the modifications didn't hold after a reboot, assuming the system didn't shut the service down first. So I put the project on hold until I could figure it out.
Well it's been 6 months and I am happy to report I have found a permanent solution which will activate the FULL Google Assistant on ANY non-rooted or rooted Amazon device. All we will do today is make a few small edits within the settings of FireOS. The modifications WILL survive reboots!
If you are using Alexa, you will Have to disable it and install the latest version of the Google App located at this link. Make sure to also have Google Play Services installed.
****WARNING: THE FOLLOWING APPLICATION IS VERY POWERFUL. MAKING THE WRONG EDITS CAN RESULT IN A POTENTIAL, UNRECOVERABLE BRICK. I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR DEVICES.****
1. You can download Settings Database Editor, install it and make the edits within that application (not recommended) or you can follow along with me and we'll use ADB. But if you do choose the application, you need to grant it the proper permission. Please plug your tablet into your PC and open an ADB window and type the following line below:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
2. Open Settings Database Editor. You will see three choices at the top: system, secure and global. Please, ONLY select 'secure'.
3. Scroll all the way to the bottom and you will see:
Code:
voice_interaction_service
voice_recognition_service
4. Tap on voice_interaction_service. A window will pop up that says 'edit setting'. Delete any text currently in the window if there is any and type the text below into it with NO SPACES:
Code:
com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
OR use ADB:
Code:
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
5. Tap on voice_recognition_service. A window will pop up that says 'edit setting'. Delete any text currently in the window if there is any and type the text below into it with NO SPACES:
Code:
com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
OR use ADB:
Code:
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
6. Scroll all the way back to the top of Settings Database Editor. At the very top of the list, tap 'Add new setting'. For the first entry type:
Code:
assistant
and tap 'save changes.' Now type in in the second entry:
Code:
com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
and save changes.
7. In the list, locate the setting
Code:
alexa_enabled
and tap on it. Change the number from a 1 to 0 and save changes.
That's it. You should be done! Now reboot your tablet using ADB:
Code:
adb reboot
8. Now it's time to configure your Assistant. Open the Google App. > Tap three lines on bottom right corner > Settings > Voice > 'Ok Google Detection' > Set the preferences to your liking. You will have to train your voice model so make sure you do that first. When done, tap back twice. Make sure your search language is set to English and your search region is The United States. See the next step as to why.
9. Go here and download the Google Assistant APK, install it and open it. You will get a message saying your device isn't compatible with Assistant, but that's ok. Installing the APK will ensure your tablet receives the proper upgrades when Assistant is made available for 5.0 devices.
I hope everyone enjoys this! I am so excited to get this working
Thanks, great job! I can confirm it works great on Fire HD 8 OS 5.6.0.1. I even think the microphone is more responsive with this method. Yes, Google Assistant is somewhat more limited on Lollipop, but it's still useful anyway.
I used the Settings Database Editor app. It's not "scary" if you follow the directions. It makes me wonder what more can be done to this little tablet to make it more "root-like" with Settings Database Editor and ADB.
Thanks!
wcarlson40 said:
Thanks, great job! I can confirm it works great on Fire HD 8 OS 5.6.0.1. I even think the microphone is more responsive with this method. Yes, Google Assistant is somewhat more limited on Lollipop, but it's still useful anyway.
I used the Settings Database Editor app. It's not "scary" if you follow the directions. It makes me wonder what more can be done to this little tablet to make it more "root-like" with Settings Database Editor and ADB.
Thanks!
Click to expand...
Click to collapse
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Awesome bro.
I'm using fire 8 in India, they have disabled Alexa based on location. If I change my Amazon account location to US, I get Alexa. But, changing back the location to India, disables Alexa again. Alexa option won't be visible in the settings menu.
Do you think, is there anything I can edit in settings app to get Alexa?
---------- Post added at 05:18 AM ---------- Previous post was at 05:18 AM ----------
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
Can't wait
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
That would be awesome, as I couldn't find much other info at all about this app and its uses.
There also seems to be a whole bunch of AOSP settings hidden in the software you obviously can't use, such as mobile networks, GPS, and the LED notification light.
Tweaks I have done so far:
Toggle either full or partial immersive mode in certain apps
Remove lockscreen ads (doesn't work in 5.6)
Nothing else I tried yet I couldn't already do in the regular settings app.
DragonFire1024 said:
I'll be making a thread sometime soon on the tweaks I've been able to come up with. For not having root, it's pretty impressive.
Click to expand...
Click to collapse
You never fail to impress
This worked for me but some functionality is missing. If I say "Okay Google, set a timer for [x] minutes." It will just do a Google search for those words. It doesn't automatically open up the Clock app and start the timer. This is with the default Clock app disabled and the Google Clocl app installed.
autobulb said:
This worked for me but some functionality is missing. If I say "Okay Google, set a timer for [x] minutes." It will just do a Google search for those words. It doesn't automatically open up the Clock app and start the timer. This is with the default Clock app disabled and the Google Clocl app installed.
Click to expand...
Click to collapse
In the past few weeks I learned that unless the app is actually uninstalled, the system still recognizes it as an app. THis will be as close to the assistant as we get, until it's rolled out to all of Lollipop devices. Also, without Gapps being part of /system/priv-app, a lot of the functionality won't be possible. However, I do see to recall the voice assistant working for the alarm, or basic system functions. It could be possible, that Google stopped that function to lollipop devices or it's just simply mucked by one, or Amazon patched it as well.
Assistant now fully working
Been checking daily whether launching the assistant shortcut would work. Yesterday night it went from assistant not available on this device to Google assistant is not your chosen assistant. After following this guide and rebooting now I have full Google assistant with home control etc!
xperia709 said:
Been checking daily whether launching the assistant shortcut would work. Yesterday night it went from assistant not available on this device to Google assistant is not your chosen assistant. After following this guide and rebooting now I have full Google assistant with home control etc!
Click to expand...
Click to collapse
Does this include the full assistant you get in 6.0+?
Sent from my Samsung Galaxy S4 using XDA Labs
I also just got the full Google Assistant yesterday afternoon. It appears to be the same as what's on 6.0+ tablets.
lakitu47 said:
I also just got the full Google Assistant yesterday afternoon. It appears to be the same as what's on 6.0+ tablets.
Click to expand...
Click to collapse
This is great. It looks like they likely finally rolled it out to Lollipop devices. Let's hope it isn't another mistake!
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Does this include the full assistant you get in 6.0+?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Yup, the full assistant experience. I have google's clock, play music, spotify installed, works with all of them just like on normal 6.0+
Bet they're enabling server side for all tablets now 5.1+ and above, even though the page still says 6.0+ on google's site. Wake word seems to work with screen on but not off. Still so much better than alexa. You also lose the long press home to activate, tried using a nav button app on xposed but that ended up breaking the framework and I almost couldn't use the tablet.
xperia709 said:
Yup, the full assistant experience. I have google's clock, play music, spotify installed, works with all of them just like on normal 6.0+
Bet they're enabling server side for all tablets now 5.1+ and above, even though the page still says 6.0+ on google's site. Wake word seems to work with screen on but not off. Still so much better than alexa. You also lose the long press home to activate, tried using a nav button app on xposed but that ended up breaking the framework and I almost couldn't use the tablet.
Click to expand...
Click to collapse
There are a few edits in the framework that fix that and allow for the home button to long press to the Installed assistant app. I forget where though. When I get home I'll look through my notes and find it once I set this up again. With root it's a fairly easy fix.
Sent from my Moto E4 using XDA Labs
Confirmed. Appears the FULL assistant is now available using my original methods. However it requires only the first 2 ADB commands to get everything working. This also works on Fire Launcher which makes this even more glorious.
I haven't had luck with this for the 8" HD as far as the full functionality goes. Now that Alexa works hands-free for it, I don't see it as a big deal but it works great for the 10", though
dondraper23 said:
I haven't had luck with this for the 8" HD as far as the full functionality goes. Now that Alexa works hands-free for it, I don't see it as a big deal but it works great for the 10", though
Click to expand...
Click to collapse
Tested it in HD 8 and worked perfectly. Haven't tried it on my HD 10 yet.
Side note: I've tried this on other 5.1 devices, not from Amazon, and it doesn't work. So this is likely a fluke from and update to the Google app. The other suggestion would be to try the beta APK. I started on a fresh FireOS 5.4.0.0 and downloaded play services and Google beta APK. Not sure if that makes a difference or not. None the less, get it while you can if you can
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Tested it in HD 8 and worked perfectly. Haven't tried it on my HD 10 yet.
Side note: I've tried this on other 5.1 devices, not from Amazon, and it doesn't work. So this is likely a fluke from and update to the Google app. The other suggestion would be to try the beta APK. I started on a fresh FireOS 5.4.0.0 and downloaded play services and Google beta APK. Not sure if that makes a difference or not. None the less, get it while you can if you can
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
I'm sure I just did something wrong then cuz all I was getting was a google search everytime I tried to get it to work with the 8HD. I'll give it another go on Sunday
keep getting this error at step 1... wish there was a bat or something I could download for this
C:\platform-tools>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Bad argument: java.lang.IllegalArgumentException: Unknown package: by4a.setedit22
lovemesomeandroidyo said:
keep getting this error at step 1... wish there was a bat or something I could download for this
C:\platform-tools>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Bad argument: java.lang.IllegalArgumentException: Unknown package: by4a.setedit22
Click to expand...
Click to collapse
To use ADB, you MUST have USB debugging enabled in developer options.
If you're using Windows, make sure you use Command Prompt (cmd.exe) instead of PowerShell.
Open a command prompt window in the location of the Platform Tools. Type in "ADB shell" first, then wait for it to connect. You may need to allow debugging from your computer on your tablet from a pop-up dialog. Then type in the rest of the command starting at "pm grant" after [email protected][device codename].
My phone is forcing upon me an update that I wish to stave off, if possible, or stop altogether if possible.
The upcoming update will happen in a day if I don't figure out how to stop it.
How can we definitively tell if the baseband will be incremented with any given forced update?
And how can we tell if this is a security-only update, or if the baseband will be updated too?
Use Package Disabler or an adb edit to disable these two services. Stops it dead in its tracks.
blackhawk said:
Use Package Disabler or an adb edit to disable these two services. Stops it dead in its tracks.
Click to expand...
Click to collapse
Ah. Too late! This time anyway.
But your information is good for next time.
I'll use this information in the future (and so can others, which is the point of my fleshing what you just had suggested as the answer) to disable the following two services on my T-Mobile Galaxy A32 5G (SM-326U) Android 12 setup...
<com.sec.android.soagent>
What is com.sec.android.soagent?
What is SOAgent in Samsung Galaxy?
What does com.sec.android.soagent do?
<com.ws.dm>
What is com.ws.dm?
What does com.ws.dm do in a Google Activity?
What does Com WS DS mean?
When I looked to disable those two services using my MuntashirAkon App Manager...
<https://github.com/MuntashirAkon/AppManager>
I found that perhaps that second service has a different name?
<com.sec.android.soagent>
<com.wssyncmldm>
What is com.wssyncmldm?
How to disable com.wssyncmldm
Step by step guide to disabling com.wssyncmldm
All you need to know about com.wssyncmldm
Why disable com.wssyncmldm
How to fix com ws sync mldm
Everything you need to know about com.wssyncmldm
As for "Package Disabler", I didn't even know you could disable system packages without being root (alas, my phone can't be rooted).
It's nice to know you can disable system apps without root.
So that others don't have to look for it, I think I found it here, at least with my first set of search terms.
Package Disabler
<https://www.packagedisabler.com>
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
You can disable apps with 1 click. Disabled application / package will not be uninstalled or updated using Google play or any other means.
This app also provides password / uninstall protection to avoid misuse.
When I searched on XDA-Developers forum threads for package disabler, I found a bunch of hits, but I don't know which are canonical updated threads.
Package Disabler Pro- De-Bloat & Remove Stock Apps For Better Ram-Battery Life
Package Disabler - Android 11?
which also suggests LADB(Kunal Adb) or PC adb
Package Disabler?
Package Disabler?
New package disabler,works!!!
Package Disabler
Package disabler pro
[GUIDE] [No Root] Disable System Apps & Bloatware: Package Disabler Pro - T-Mobile
Has anyone found an alternative apk to package disabler pro?
Need Help with my note 8 Bootloop caused by disabled Packages
What bloatware have you safely disabled/removed on the Galaxy Tab S3?
These non-forum articles showed up in a google search for more information about this useful "package disabler" tool which purports to disable system packages without needing to be root.
Debloat Galaxy Devices Without Root
Universal Android Debloater helps you get rid of unwanted apps and bloatware on your phone
How to disable any pre-installed system app bloatware on Android without root
Android Central Package Disabler
Regarding the adb commands, I use adb all day every day for a variety of things (see below) but I haven't used adb (or ladb) to disable a service which requires root as I didn't know you could do that.
How to duplicate what adb does to ad hoc open any given Activity on the Android phone?
[adb] [Wireless debugging] [Wi-Fi] Is there an updated XDA tutorial yet on setting up adb COMPLETELY wirelessly as of Android 11+ (no USB cable!)?
[adb] What is the adb syntax to connect wirelessly to Android by unique serial number (instead of by Wi-Fi LAN IP address & random port assignment)?
[adb] [Wireless debugging] [Wi-Fi] Is there an updated XDA tutorial yet on setting up adb COMPLETELY wirelessly as of Android 11+ (no USB cable!)?
(PSA) Using the new Android 12 TILE for 'Developer options' 'Wireless debugging' to establish adb connection over Wi-Fi without USB
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Android 12 Developer options adb "Wireless debugging" option keeps turning off
For any given trusted computer, can we make an adb usb debugging connection on day one & then SAVE adbkey.pub authentication keys for use years later?
As for how to use either local adb (ladb) to disable packages (without needing the PC and without needing to be rooted), my first task was to look up what the ladb commands might be...
Say hello to LADB, a local ADB shell without needing root or a computer!
How to debloat your phone (and more) without connecting to a PC
And then let's look up some of the adb commands to figure out what they are to disable the two services using a PC but without needing to be rooted.
XDA-Developers guide to ADB
ADB Tips & Tricks: ADB commands that every power user should know about!
Obviously I have some homework to do before I can successfully disable the two services listed above without needing to be rooted (as my phone can't be rooted) using just adb (which seems like the easiest way to approach this task)...
Since I'm always connected to my phone via adb anyway (as I mirror my screen and audio onto my PC) I may as well use the adb commands to disable the two update services, where might these be the related necessary adb commands to employ for that task?
C:\> adb shell pm list packages | findstr /i soagent
That should find "package:com.sec.android.soagent"
C:\> adb shell pm list packages -d | findstr /i soagent
That should find the disabled packages & then grep for "com.sec.android.soagent" which shouldn't (yet) be in that list
C:\> adb shell pm disable-user --user 0 com.sec.android.soagent
That should (I hope) disable the listed package (is that correct?)
C:\> adb shell pm enable --user 0 com.sec.android.soagent
That should (if desired), re-enable the listed package (is that right?)Likewise, these are likely the related steps for com.wssyncmldm:
C:\> adb shell pm list packages | findstr /i wssyncmldm
C:\> adb shell pm list packages -d | findstr /i wssyncmldm
C:\> adb shell pm disable-user --user 0 com.wssyncmldm
C:\> adb shell pm enable --user 0 com.wssyncmldm
But first, may I confirm that my two services are of a different name than that which was initially suggested?
And may I confirm the adb commands to disable those two services?
You can probably roll it back from 12 to 11 if you want provided the boot loader wasn't upgraded too.
This stock Samsung N10+ hasn't been updated in over 3 years; still running on Pie. Current load is over 2.5 yo, still fast, very stable with minimal maintenance. Security simply isn't an issue with its current configuration... screw the Google scare hype. This is what Android is capable of... if you leave it be.
blackhawk said:
You can probably roll it back from 12 to 11 if you want provided the boot loader wasn't upgraded too.
Click to expand...
Click to collapse
Thank you for that suggestion, where I really don't know that much about Android, which I openly admit. I can research if pointed in the right direction though.
I am told the bootloader for the T-Mobile A32-5G needs to be version 5 or below (maybe even 3 or below) in order to root the Samsung Galaxy A32-5G, and mine is currently version 8.
I don't know how to roll back a bootloader, but even so, I'm not sure I understand your suggestion of rolling back the Android version from 12 to 11.
How would changing the OS change the bootloader version?
blackhawk said:
This stock Samsung N10+ hasn't been updated in over 3 years; still running on Pie. Current load is over 2.5 yo, still fast, very stable with minimal maintenance. Security simply isn't an issue with its current configuration... screw the Google scare hype. This is what Android is capable of... if you leave it be.
Click to expand...
Click to collapse
I very much appreciate your kind and thoughtful advice that pointed me in the direction of the two packages that I needed to disable, which is what I needed to research in the right direction.
I also much appreciate that you mentioned adb will do the job of disabling those packages without me being rooted, as that too was a required datapoint that I didn't know until you told me.
Thank you very much for your kind advice, where I do agree with you this hype about having the latest security patches isn't something I'm all that worried about.
However....
There is this "nagging concern" that, as of Google's Project Mainline and Project Treble (both since renamed), the way that the 25 core modules update is no longer via carrier updates but over the air with Google Framework Services updates (not to be confused with Google Play Services updates).
AdServices multi-package multi-type Android 13
adbd com.android.adbd APEX Android 11
AppSearch com.android.appsearch APEX Android 13
ART com.android.art APEX Android 12
Bluetooth APEX Android 13
CellBroadcast com.android.cellbroadcast APEX Android 11
Conscrypt com.android.conscrypt APEX Android 10
Device Scheduling com.android.scheduling APEX Android 12
DNS Resolver com.android.resolv APEX Android 10
DocumentsUI com.android.documentsui APK Android 10
ExtServices com.android.ext.services APK (Android 10)
ExtServices com.android.ext.services APEX (Android 11)
IPsec/IKEv2 Library com.android.ipsec APEX Android 11
Media Media: com.android.media Android 10 (extractors)
Media Codecs: com.android.media.swcodec APEX Android 10 (extractors, MediaSession API) Android 11 (MediaParser API)
MediaProvider com.android.mediaprovider APEX Android 11
ModuleMetadata com.android.modulemetadata APK Android 10
Network Stack Network Stack Permission Configuration: com.android.networkstack.permissionconfig
Captive Portal Login: com.android.captiveportallogin
Network Components: com.android.networkstack APK Android 10
NNAPI Runtime com.android.neuralnetworks APK Android 11
OnDevicePersonalization Runtime Multiple Multiple Android 13
PermissionController com.android.permissioncontroller APK Android 10
SDK Extensions com.android.sdkext APEX Android 11
Statsd com.android.os.statsd APEX Android 11
Tethering com.android.tethering APK Android 11
Time Zone Data com.android.tzdata APEX Android 10
UWB com.android.uwb APEX Android 13
Wi-Fi com.android.wifi APEX Android 11
It's all very confusing HOW Android updates nowadays.
Some updates are over the air by the carrier
Other updates are done separately for the 25 core modules
Still others are done over a Google Play Store app Activity
(These last app updates are not really part of the Google Play Store app but the Activity for app updates appears in the settings for the Google Play Store app so a lot of people associate those app updates with the Google Play Store app).
In short, does this method of disabling two packages "really" work to stop all updates?
Or does it just work for the Project Mainline updates?
Or just the carrier supplied security updates?
I don't know.
You're welcome.
The bootloader version can be upgraded but not rolled back on a Snapdragon. If just the rom was upgraded from 11 to 12 it can be rolled back by flashing Android 11 if the bootloader wasn't upgraded too. I think this is the case for you but check it to be sure. Personally I don't muck with the firmware. A Samsung Experience center at a Best Buy can also flash it back to 11.
I really don't worry about updating any apps unless there's a improvement I need, so I don't.
It leads to a more stable platform since everything is already running well, more importantly it's fulfilling its mission. In the end that's all that counts. This is my solution; it may not be what others do but it works very well for me. I send almost zero time now troubleshooting... it just runs.
blackhawk said:
You're welcome.
Click to expand...
Click to collapse
Without you, I wouldn't have known the name of the two packages, nor that adb can disable them without me being rooted. Thanks.
What I don't know, yet anyway, is which of the following software versions those two packages above facilitated the updates for...
Android version [e.g., Android 12]
Baseband version [e.g., A326USQS8BVL3]
Security update [e.g., Dec. 1, 2022]
Google Play System [e.g., March 1, 2022]
Google Play Services [e.g., 22.42.12 (190400-481949630]
Google Play Store [e.g., 33.5.16-21 [0][PR] 4933219047]
Firmware (such as the Qualcomm modem firmware)
25 Core modules in Project Mainline
These are apparently updated either over Google Play Services on the net or OTA by partners.
Default/original apps (such as Chrome, YouTube, etc.)
User apps (of which there may be hundreds)
blackhawk said:
The bootloader version can be upgraded but not rolled back on a Snapdragon.
Click to expand...
Click to collapse
I didn't think it was going to be easy to unlock the bootloader, let alone roll it backward a notch or two.
BTW, it's not a Snapdragon I don't think.
DevCheck (see attached screenshot) shows it to be a "Mediatek Dimensity 720" powering this SM-A326U Galaxy A32 5G.
blackhawk said:
If just the rom was upgraded from 11 to 12 it can be rolled back by flashing Android 11 if the bootloader wasn't upgraded too. I think this is the case for you but check it to be sure. Personally I don't muck with the firmware. A Samsung Experience center at a Best Buy can also flash it back to 11.
Click to expand...
Click to collapse
I've seen that link, and I found it fantastic, where I think I'm stuck in not being able to root unless something new comes up - which is my main purpose here in at least freezing the bootloader version at 8.
The main lack of information I have at the moment is I don't know WHAT PROCESS updates the bootloader.
blackhawk said:
I really don't worry about updating any apps unless there's a improvement I need, so I don't.
Click to expand...
Click to collapse
I'm with you 100% in that I don't update ANY apps unless I KNOW it has something I want (which almost never happens).
That's good that neither of us worries about app updates because most people don't realize what a MESS app updates truly are!
I've found out most people THINK that the Google Play Store does a check for new apps for ALL your installed apps - but I've tested it and it doesn't even come close (see attached screenshot proof).
The Google Play Store app update section isn't even part of the Google Play Store (it's an Activity within it but it's independent of the Google Play Store app itself) - but what's worse is the fact it updates barely any apps.
Maybe a dozen. Maybe even two dozen.
But the Google Play Store app update Activity MISSES hundreds upon hundreds of apps, which the screenshots below prove to be the case.
Luckily, as a result of that opinion which we both share that we don't update apps unless we need to, this whole app update mess isn't an issue for either one of us, but bear in mind that a LOT of people "think" the Google Play Store app "updates" all their apps.
It's not even close.
blackhawk said:
It leads to a more stable platform since everything is already running well, more importantly it's fulfilling its mission. In the end that's all that counts. This is my solution; it may not be what others do but it works very well for me. I send almost zero time now troubleshooting... it just runs.
Click to expand...
Click to collapse
I'm like you in that I don't update the hundreds of apps unless any one of them needs to be updated, which almost never happens.
But what is driving me nuts is the CONFUSION about what process updates what part of the Android operating system.
For example, I'm currently at:
The Google Play System = March 1, 2022
Settings > About phone > Software information
The Google Play Services = Version 22.42.12 (190400-481949630)
Settings > Apps > Your apps > Google Play Services
The Google Play Store = 33.5.16-21 [0][PR] 4933219047
Settings > Apps > Your apps > Google Play Services
But what is the process that updates those three entities?
It behooves us to nail this down as I'm confused what is updated when & how.
While there are at least a half dozen important layers of Android which are updated on a variety of schedules, I think the fundamental updated layers may be:
The Android OS version, baseband & security patch levels
The Google Play {System,Services,Store} system update levels
The versions of the 25 core modules of Project Mainline
The versions of the firmware in Project Treble
The versions of all the apps supplied with the native OS
I'm embarrassed, for example, to state that I have no idea whatsoever what updates the BASEBAND, for example.
Worse, I have no idea what process updates the 25 core modules of the Project Mainline modules (which is the core of Android).
Project Mainline core modules in Android 10
Project Mainline core modules in Android 11
Project Mainline core modules in Android 12
Project Mainline core modules in Android 13
What process updates those two dozen critical core modules?
com.wssyncmldm is what does all OTA firmware updates for the phone including the bootloader as far as I know. To stop OTA upgrades only it needs to be disabled. It's the only one that can permanently screw you up.
I'm not familiar with the MediaTek chipsets. Galaxy store updates it's apps as well, I firewall block it unless I need to use it.
I keep installable backup copies of all my apps including system. That way on a reload or if they get an unwanted update, I'm ready.
Worksv on Android 9,10, not sure about higher. Newer versions are on Playstore.
blackhawk said:
com.wssyncmldm is what does all OTA firmware updates for the phone including the bootloader as far as I know. To stop OTA upgrades only it needs to be disabled. It's the only one that can permanently screw you up.
Click to expand...
Click to collapse
Thank you for confirming com.wssyncmldm does the over-the-air firmware updates, and, particularly the caveat that it's the only updater package that can permanently screw the ability to root up.
Android is broken into so many components that I am going nuts trying to figure out what updates what - so that helps (a little).
blackhawk said:
I'm not familiar with the MediaTek chipsets. Galaxy store updates it's apps as well, I firewall block it unless I need to use it.
Click to expand...
Click to collapse
Thank you for bringing up the Galaxy App update mechanism, which I had omitted in my description of what updates apps above.
The OTA update often updates default system apps
The Google Play Store Activity Updater updates "some" apps
The FOSS Google Play Store clients also update "many" apps
The Samsung Galaxy Store updater updates its own apps
There are app updaters I've tested which update ALL apps
(Of course, these assume an update is available.)
Just so that you know, I never create ANY login on my phone, so I can't log into the galaxy store even if I had wanted to do so.
Is there any app in the Samsung Galaxy Store worth the login requirements?
That means I don't have a Google Account set up on my phone either (even as I have a Google Account), so I've learned empirically that if you log into the GMail app even once, it CREATES a Google Account on your phone.
The phone works better WITHOUT the Google Account setup.
Likewise if you log into the Google Maps app, or Google Voice, etc., but luckily ALL the Google apps have equivalent apps which generally work better than the Google apps do anyway.
GMail === FairMail mail client
Chrome === Ungoogled Chromium web client
YouTube === NewPipe YouTube client
Google Play Store === Aurora Google Play Store client
Google Maps === works fine w/o a login
Google Calendar === Etar
Google Messages === Pulse SMS (before Klinker sold to Maple Media)
Google launcher === Nova Launcher (before they sold out)
etc.
Note a good reason for SAVING all the APKs you install is shown in the case of Nova and Pulse where both went over to the dark side.
blackhawk said:
I keep installable backup copies of all my apps including system. That way on a reload or if they get an unwanted update, I'm ready.
Worksv on Android 9,10, not sure about higher. Newer versions are on Playstore.
Click to expand...
Click to collapse
Like you, I maintain all my APKs independently OUTSIDE of the current daily drive phone, where it's all completely automatic.
The FOSS Google Play Store clients have an option to NOT DELETE the APK when you install any app off the Google Play Store repository.
That fact bears repeating.
When you install an app off the Google Play store, presumably this sequence occurs:
1. The client finds the app & then you download the APK
2. The client initiates the installation of the APK
3. Then the client always DELETES the downloaded APK
But when you install that same app off that same repository using the FOSS Google Play Store clients, and if you check the box to NOT DELETE the APK after installation, then THIS sequence happens.
1. The client finds the app & then you download the APK
2. The client initiates the installation of the APK
3. Then the client always DOES NOT DELETE the downloaded APK
In addition, my Android file system and my Windows file systems are exactly the same (so to speak) since I use free WebDAV servers to mount my entire Android filesystem onto Windows as a drive letter over Wi-Fi (no cables necessary).
Can you mount BOTH Android internal & external storage onto Windows as a drive letter over Wi-Fi using a SINGLE WebDAV server?
That way, when I need to re-populate a new phone, I first bring over the homescreen and all the icon locations (which Nova does nicely), and then, one by one, I populate the apps by SLIDING them over using my mouse to slide from Windows to the mirrored Android.
See the screenshots below proving all that I say above.
BTW, I have one WARNING about extracting APKs, where I've tested ALL the free extractors extent, and where I've had some bad experiences where the extracted APK doesn't work on a different model phone (generally it's different in every way, hardware & software).
I've had MUCH BETTER experience just NOT DELETING the APK when it's downloaded off the Google Play Store repository, or the F-Droid repository, or the GitHub/Sourceforge/Guardian/etc., repositories.
This problem, I think, will only get worse as of the August 2022 decree by Google regarding APEX files (instead of APK files) on the Google Play Store repository.
In summary, Android UPDATES are complex, and I do NOT profess to understand what updates what - so any help anyone can provide is welcome as I am confused as to what updates what.
Since my credibility matters, screenshots below prove all I say above.
I use whatever comes in handy and don't go more nuts than I need to in order to get the job done.
The reason to be able to access the Samsung Galaxy store are the free icon packs and themes.
Edge add ons and certain other apps like Sound Assistant. The Good Lock family of apps are of particular interest for a Samsung user.
Nova isn't as fast or efficient as One UI. One UI is a very stable launcher and very customizable.
My stock N10+ homescreen running on One UI, modified with various Good Lock apps and One handed Operation plus. Digi Clock and Energy Ring are 3rd party apps.
blackhawk said:
Nova isn't as fast or efficient as One UI.
Click to expand...
Click to collapse
Nova free went over to the dark side as of the Branch acquisition.
Nova Launcher and Sesame Search have been acquired by Branch, an analytics company
As a direct result of the Branch acquisition, my Nova free is the last known good version (namely the pre-branch 7.0.57 version):
<https://novalauncher.com/beta>
<https://novalauncher.com/apk/NovaLauncher_7.0.57.apk>
Name: NovaLauncher_7.0.57.apk
Size: 8687535 bytes (8483 KiB)
SHA256: 05AE72221D8D4F3D6A111A3220A0C87040806AF4E53053EF64F2DE426990893E
Mostly what I like(d) about Nova free is the ability to save the homescreen (and all the folders, shortcuts, and icons) EXACTLY and then re-load it on any number of phones, no matter what make/model of that phone.
Another feature I really liked about Nova free is its ability to put icons on any grid and in any location whatsoever.
Last summer I had opened a thread seeking a replacement app launcher...
Nova launcher used to be the best free Android launcher - until now - so what's better?
We discussed the merits at that time...
blackhawk said:
One UI is a very stable launcher and very customizable.
Click to expand...
Click to collapse
I'm happy with my last-known-good-version of Nova free, but because they went over to the dark side, I have to find another app launcher.
If OneUI does those things, I might consider it.
Save homescreen/folders/icons & re-use later
Put icons on any grid (or no grid) whatsoever
GalaxyA325G said:
Mostly what I like(d) about Nova free is the ability to save the homescreen (and all the folders, shortcuts, and icons) EXACTLY and then re-load it on any number of phones, no matter what make/model of that phone.
The only other thing I really liked about Nova free is its ability to put icons on any grid and in any location whatsoever.
I'm happy with my last-known-good-version of Nova free, but because they went over to the dark side, I have to find another app launcher.
If OneUI does those two things, I might consider it.
Save homescreen/folders/icons & re-use later
Put icons on any grid (or no grid) whatsoever
Does it?
Click to expand...
Click to collapse
SmartSwitch can save icons and homescreen, however on a clean load I wouldn't use SmartSwitch other than to save homescreen settings so you'll need to rebuild the icons and apps although Goodlock apps and homepage settings remain in effect. So it's not like you just landed on mars and everything looks unworldly with no button navigation
Other than folders you're locked into the grid pattern.
One UI is faster, more efficient and very stable. In fact in 3 years I've never had it crash and force a reboot. Let me put this way, one of the most surefire ways to boot loop a Samsung is a 3rd party launcher. Been there, done that twice, back to back full reloads That convinced me to live with the white page indicators. That's my only real criticism of One UI.
Pick your poison wisely...
I didn't read the whole thread, but for instance it's already enough to freeze the "Software-Update" package to stop "Software-Update" notifications.
In my S8 with Android 9 it's located in /system/priv-app/FotaAgent/FotaAgent.apk. Just rename to "FotaAgent.apk.bak" and that's it!
Hi.
I've tested various Date Status Bar apps and I finally found one that I really like (Calendar Notify) and works (doesn't stop working after a while), but the notification tends to get hidden when there's other notifications and it defeats the purpose of having it on there. :-/
I was wondering if there's an ADB Shell command I can use to force it to be set as a priority? On older Android versions it was available as an option though it was taken for some reason (I can't find it anywhere), guess not many used it or something.
Thanks.
App must have the "Draw Over Other Apps" permission to prevent this "gets hidden". Check app's permissions ...
jwoegerbauer said:
App must have the "Draw Over Other Apps" permission to prevent this "gets hidden". Check app's permissions ...
Click to expand...
Click to collapse
Thanks, but the app isn't listed on there. :-/