Related
Hi iv seen loads of people trying to remove stock apps. Due to the eMMC protection the DesireHD/DesireZ/G2 has we are unable to do this at this point. But what we can do is to stop them from running and showing in the app list.
I will use Amazon MP3 as an example :-
1) Find the process name of the APP yor want to disable. You can do this by looking in /system/app for the file name. Or i find this method a lil quicker
From Terminal App or ADB shell type
pm list packages
Click to expand...
Click to collapse
and find the process in the list i.e com.amazon.mp3
2) In Terminal App or ADB shell type "pm disable ProcessName" i.e.
pm disable com.amazon.mp3
Click to expand...
Click to collapse
3) Reboot phone or just the launcher
4) The app wont/cant run (the icon may stay tho.)
All credit goes to others around the web
[UPDATED 27/10/2010] Icon may not be removed
It just reappears in the list when I do this.
RD1945 said:
It just reappears in the list when I do this.
Click to expand...
Click to collapse
Same here too.
Well, I've used 'pm disable *twitter*' - That should work shouldn't it?
Rebooting now
Could you stop Sense from running this way and just use Launcher Pro?
Stock apps
I would be sooo greatfull to get no sence DHD... Im opened to any sugestions and ideas....
you must remember first to type 'su' to get super user permissions, you will know that you have su permissions when the $ turns to a #.
Hope this helps you all.
Credit to others and not me, I'm just regurgitating info that I have sought out.
Yer the icon wont go when in scense but the app cant run anyway so it cant hog RAM/CPU ect.
More comprehensive guide/explanation here from the G2 thread:
http://forum.xda-developers.com/showthread.php?t=809231
Hi
Can i disable Sense and the whole sense applications?
I cant find sense in the list.
Is com.htc.launcher the sense launcher?
EDIT:
I have disabled com.htc.launcher but sense is still there.
For those who hate bloatware HTC like me, I created this list:
Code:
su
pm disable com.amazon.mp3/com.amazon.mp3.client.activity.LauncherActivity
pm disable com.amazon.mp3
pm disable com.htc.android.Stock
pm disable com.htc.android.htcsetupwizard
pm disable com.htc.friendstream
pm disable com.htc.ereader
pm disable com.htc.laputa
pm disable com.htc.laputa.HtcLaputaInstaller
pm disable com.htc.connectedMedia
pm disable com.htc.Weather
pm disable com.htc.googlereader
pm disable com.htc.htctwitter
pm disable com.htc.android.mail
pm disable com.futuredial
pm disable com.htc.wdm
pm disable com.htc.recommend
Warning! The list is for those who REALLY hate the Sense and HTC applications: it disables apps like Weather, Ebook reader, RSS Feed reader, Locations, etc.
I have not tested the phone thoroughly after disabling these applications, I hope not to have disabled something vital .
If you know any other application that can be disabled safely, let me know and I will add to the list.
What we could really do with is a list of what each of these actually does.
Even better, can no-one make an app, like the SGS had, which you tap on the app name and it removes it (disables) rather than having to go into console?
Might be a dumb question but does this method require rooting?
Mojo Fones said:
Might be a dumb question but does this method require rooting?
Click to expand...
Click to collapse
Read the following thread, its easy to follow....and to answer your question....yes you need temp root.
http://forum.xda-developers.com/showthread.php?t=809231
Cheers.
This is also the only way to get rid of the stock version Soundhound and Quickoffice? I have purchased these 2 apps and if I install these two I will get 2 icons for Soundhound and 2 for Quickoffice. I have tried Launcherpro - because you can disable apps.. but if I disable the standard Soundhound then It will also disable the commercial version. This is also for Quickoffice!
Anyone got some tips for this 'problem'?
kaosnews said:
This is also the only way to get rid of the stock version Soundhound and Quickoffice? I have purchased these 2 apps and if I install these two I will get 2 icons for Soundhound and 2 for Quickoffice. I have tried Launcherpro - because you can disable apps.. but if I disable the standard Soundhound then It will also disable the commercial version. This is also for Quickoffice!
Anyone got some tips for this 'problem'?
Click to expand...
Click to collapse
Have the same question ! I'm trying to use VISIONary to get temp root but doesn't work ! I'm getting rooting device , please wait message for over 10 minutes now nothing else
Check if debugging mode is checked in setup/applications.
Yes it is checked otherwise you can't even run the app
the last version of titanium backup is able to totally remove system and/or preinstalled apps, like amazonmp3 etc. tried it and it worked for me, after two reboots the app is completely gone!
all of the above "hacks" didn't work for me (although i am temp rooted with visionary and used the "su" command), but titanium backup did the trick!
version: 3.5.7.3
click and hold on the app, choose "force remove app (by recovery exploit)"
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.
*****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].
Am seeing this tab in settings, what apk do I need to debloat to remove this? I've been through my apps list but dont see anything obvious, thanks
I don't have that option. Do you see it Samsung members app?
See grab, no its towards the bottom in Settings menu.
don't have that setting but going via help file it offers to install it via Smart Tutor for Samsung Galaxy app
Thanks, just want to get rid of that tab, any idea how?
do you have that app? uninstall it if yes
Have uninstalled smart tutor but the Remote Support tab remains in settings list. Guess there's no way to get rid of it?
restart the phone?
Still there after restart, was hoping there was an app I could disable etc to remove the heading from settings menu, guess not.
I would be glad to remove it as well, I suddenly got it appearing after the last update on my A52 5G.
Any new idea how to get away with this option in Settings?
A bit late to this post, but the solution is to install the Samsung Tips app which removes the "manual" and "remote support" options inside the Settings app and replaces it with a single "Tips" entry: https://galaxystore.samsung.com/pre...session_id=W_03bb1f02be95e1f7c89bf2450f16277d
You can remove both by having Tips installed and disabling it (not removing it) via "pm disable com.samsung.android.app.tips"
Macusercom said:
A bit late to this post, but the solution is to install the Samsung Tips app which removes the "manual" and "remote support" options inside the Settings app and replaces it with a single "Tips" entry: https://galaxystore.samsung.com/pre...session_id=W_03bb1f02be95e1f7c89bf2450f16277d
You can remove both by having Tips installed and disabling it (not removing it) via "pm disable com.samsung.android.app.tips"
Click to expand...
Click to collapse
This doesn't work on the S21 latest software, CVDC. It will disable Tips, but the Remote Support option will no longer be removed.
Macusercom said:
A bit late to this post, but the solution is to install the Samsung Tips app which removes the "manual" and "remote support" options inside the Settings app and replaces it with a single "Tips" entry: https://galaxystore.samsung.com/pre...session_id=W_03bb1f02be95e1f7c89bf2450f16277d
You can remove both by having Tips installed and disabling it (not removing it) via "pm disable com.samsung.android.app.tips"
Click to expand...
Click to collapse
On my S22+, I already have the latest version installed by default and tried to disable it via PDP app, but it tells me that some critical app can't be disabled.
It's a system app which isn't directly labeled remote support. You will have to use an application inspector to view all system apps then have to narrow down which app it is. I had to do this to remove the Samsung Account in settings, bixby vision, bixby page, software update installer & more.
Make sure you make an apk backup of the system app before you uninstall it incase you mess up your phone or make a setting inacessible that you needed. You can restore the apps by reinstalling them from the apk you backed up with a tap or use adb to install the app.
If you happen to find out which package name it is please reply with the name as I am trying to figure out which one it is on my phone as well. I imagine its one of the ones that begin with com.samsung.android good luck on the hunt & don't forget to let everyone know once you find out.
I recently updated to android 12 and accidentally updated the youtube app. Since then, opening youtube links from apps will open them in the default YouTube app which I don't want.
I looked in the settings to disable the app but the disable button is greyed out. I looked at the default links, which confusingly says it has no default links, then has links selected when you open the menu. I tried unchecking the box but that is disabled.
My phone is rooted so my next thought was to try uninstalling through titanium backup but this failed because the apk isn't available. The recovery exploit uninstall method failed for the same reason.
Any ideas on how to do this? I'm not bothered if the app is still installed, I just want control of how youtube links are handled.
Thanks in advance.
g-de said:
I recently updated to android 12 and accidentally updated the youtube app. Since then, opening youtube links from apps will open them in the default YouTube app which I don't want.
I looked in the settings to disable the app but the disable button is greyed out. I looked at the default links, which confusingly says it has no default links, then has links selected when you open the menu. I tried unchecking the box but that is disabled.
My phone is rooted so my next thought was to try uninstalling through titanium backup but this failed because the apk isn't available. The recovery exploit uninstall method failed for the same reason.
Any ideas on how to do this? I'm not bothered if the app is still installed, I just want control of how youtube links are handled.
Thanks in advance.
Click to expand...
Click to collapse
Use a root browser to remove the apk from your system/app or system/priv-app folder.
g-de said:
I recently updated to android 12 and accidentally updated the youtube app. Since then, opening youtube links from apps will open them in the default YouTube app which I don't want.
I looked in the settings to disable the app but the disable button is greyed out. I looked at the default links, which confusingly says it has no default links, then has links selected when you open the menu. I tried unchecking the box but that is disabled.
My phone is rooted so my next thought was to try uninstalling through titanium backup but this failed because the apk isn't available. The recovery exploit uninstall method failed for the same reason.
Any ideas on how to do this? I'm not bothered if the app is still installed, I just want control of how youtube links are handled.
Thanks in advance.
Click to expand...
Click to collapse
You might have luck by opening a root shell (use 'su' in termux), and then running 'pm disable-user --user 0 com.google.android.youtube', however this will disable the YouTube app entirely.
Clear default from original Youtube app.
Then assign the alternative player to be default one.
The solution from @teknixstuff worked perfectly (upvoted previously).
The other suggestions didn't work as the options are disabled. From my original post:
I looked in the settings to disable the app but the disable button is greyed out. I looked at the default links, which confusingly says it has no default links, then has links selected when you open the menu. I tried unchecking the box but that is disabled.
Click to expand...
Click to collapse
Maybe it wasn't clear I meant android app setting rather than in-app settings.
I'm not sure if it's Google or the manufacturer that is locking these options out.