Related
Auto APN Activation
hi for all friend and thanks for Dungphp's For provide this file
many friend have problem with data connection on installed build, hope this method problem data connecton solve.with corect parameter.
im after many search in web and xda-dev... find and create installer and file for Add auto apn for all Build can use.
If no active Auto APN use of this method:
1-with root explorer delete file (/system/etc/customer/apns-conf.xml or /system/etc/apns-conf.xml) (If exist)
2-connect device with usb charge only (adb previously installed please)
3-down this and extract rar file and run install.bat
4-on settings > ireless & networks >mobile network >access Point Name > press menu key and press reset to default
5-enjoy
*** if mms not worked , please delete your apn and set manually its woked 100% ***
Very well, thank you for sharing
I just PM'd Dungphp about that cause i was having problems with certain sense builds allowing me to select the correct apn but no E/H in the notification area/status bar. Thanks.
essi_baba said:
Auto APN Activation
hi for all guys and thanks for Dungphp's For provide this file
many gays have problem...
Click to expand...
Click to collapse
bwuahahahahhhhaaaaa!
essi_baba said:
Auto APN Activation
hi for all guys and thanks for Dungphp's For provide this file
many gays have problem with data connection on installed build, hope this
Click to expand...
Click to collapse
dohclude said:
bwuahahahahhhhaaaaa!
Click to expand...
Click to collapse
Come on We all know he meant "guys" lol...
anyways awesome work OP keep up the work. XD
essi_baba said:
many gays have problem
Click to expand...
Click to collapse
hmmmm
edit comment
im sorry for type wrong word .
first post edited.
essi_baba said:
Auto APN Activation
hi for all friend and thanks for Dungphp's For provide this file
many friend have problem with data connection on installed build, hope this method problem data connecton solve.with corect parameter.
im after many search in web and xda-dev... find and create installer and file for Add auto apn for all Build can use.
If no active Auto APN use of this method:
1-with root explorer delete file (/system/etc/customer/apns-conf.xml or /system/etc/apns-conf.xml)
2-connect device with usb charge only (adb previously installed please)
3-down this and extract rar file and run install.bat
4-enjoy
Click to expand...
Click to collapse
u change it to friend now yea...hehehe
NWY, tried this but its not working for me,
can't find folder (sytem/etc/customer)..
so just skip it n proced with install.bat,check setting still no apn,
found out,apns-conf.xml was push to (system/etc/apns-conf.xml),then i delete system/etc/apns-conf.xml n reinstall it again,but still nothing on apn..
something wrong with i did??
install
oroo708 said:
u change it to friend now yea...hehehe
NWY, tried this but its not working for me,
can't find folder (sytem/etc/customer)..
so just skip it n proced with install.bat,check setting still no apn,
found out,apns-conf.xml was push to (system/etc/apns-conf.xml),then i delete system/etc/apns-conf.xml n reinstall it again,but still nothing on apn..
something wrong with i did??
Click to expand...
Click to collapse
If you only do :
1-with root explorer delete file (/system/etc/customer/apns-conf.xml or /system/etc/apns-conf.xml) (If exist)
2-connect device with usb charge only (adb previously installed please)
3-down this and extract rar file and run install.bat
4-on settings > wireless & networks >mobile network >access Point Name > press menu key and press reset to default
5-enjoy
essi_baba said:
If you only do :
4-on settings > ireless & networks >mobile network >access Point Name > press menu key and press reset to default
5-enjoy
Click to expand...
Click to collapse
done it but still nothing..
is it my rom or what??i'm using NDT ginger..
Works for me. Thankx.
One more thing. If you actually have root explorer, there is no need to use adb commands. Just replace the apns-conf.xml file in /system/etc/ and reset permissions as rw-r-r and reboot device.
Once rebooted, go to APN and press menu, then press Reset APN to default. Worked for me.
Hi !
Worked for me on Samsung Galaxy S GT-I9000 ICS ( TiramiSlim ROM ).
But Failed on Samsung Galaxy SII GT-I9100 MIUI ICS CM9 ( cMIUI ROM ).
Nowadays, thanks for this hudge list !!! )
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Great find. Thanks!
Thanks man, I have a DIY dock for mine and the fact I had to enter my PIN sideways everytime I unlock my device driving me insane.
Can this code be used on the fly? I'm using a app at the moment (called Rotate) which can enable, disable lockscreen rotation. however this is heavy on memory and I want to simply do this with a script in Tasker.
---------- Post added at 04:58 PM ---------- Previous post was at 04:37 PM ----------
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
privatesam said:
Just ran this from terminal emulator as root and it worked! Awesome - but it is lost on reboot so I need to be able to run this as a script in tasker - scripting looks tricky in Tasker though. Open to ideas!
Click to expand...
Click to collapse
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
manumanfred said:
I have enabled rotation by modifying bools.xml file and now I get to know that JB 4.2 has different rotation texts to enable rotation!
How about Launcher?
Click to expand...
Click to collapse
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Awesome. This worked for me on 4.1.2 as well. Thanks!
Really useful in the car since I don't have the official car dock. No more unlocking sideways!
Cilraaz said:
If you run it from a terminal emulator, it's temporary. If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
manumanfred said:
I know that, that's why I have modified bools.xml file to enable rotation on launcher + lockscreen.
I think JB 4.2.x have also the changed code for launcher rotation...
Click to expand...
Click to collapse
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
dosent work for me
xaueious said:
Force enable lockscreen rotation
Code:
setprop lockscreen.rot_override true
Force disable lockscreen rotation
Code:
setprop lockscreen.rot_override false
On devices that already can rotate, this does nothing.
Code should work on all AOSP ROMs with lockscreens that don't rotate, unless the code there has been modified.
Resets on reboot though I think
Click to expand...
Click to collapse
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
siddharthisback said:
I tried this command in the terminal and no error message came.i.e it got executed properly Then when i see the lock-screen it is always in portrait mode.
Cant manage to get it to landscape mode. My auto rotation is on.
I am on 4.2.2 and using NOVA launcher. Xperia S OPENSEMC ROM.
Any idea y i am not able to rotate my lockscreen ??
Click to expand...
Click to collapse
Run Terminal as root, type "su" (no quotes), then enter, then the command.
Cilraaz said:
... If you want it to be permanent, add lockscreen.rot_override=true to /system/build.prop
Click to expand...
Click to collapse
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for this. I wasn't sure if there was a specific spot in build.prop where I had to insert the line. The temporary fix in Terminal Emulator worked for me, but now it sticks after boot! I was sick of having to unlock my device sideways when it was in my car mount. The only weird thing is that it smooshes my wallpaper instead of switching to the landscape orientation, but I can live with that.
laur3n.newm4n said:
... I was sick of having to unlock my device sideways when it was in my car mount.
Click to expand...
Click to collapse
Yes, the car mount in heads up position with the cables (USB-power and 3,5 audio jack) to the bottom were exactly my reason to add this option permanently, too. The position of this environment variable in the configuration file build.prop does not matter, it is just common sense to add additional lines at the end, so you can find them easily.
dark0shark said:
Thank you, this works perfectly with 4.2.2 (CM 10.1).
Here are the steps to do this, if someone is not too familiar with editing a file in the /system file system:
1. Install app "ES File Explorer", new version 3.0.0
2. In ES File Explorer, go into Tools > Root Explorer, Option Mount R/W
3. Choose /system to be mounted RW
4. Allow (permanent) Superuser permissions for this app
5. Go to /system and open file build.prop with ES Notice-Editor (this Editor will ask for superuser permission, others won't)
6. Choose "Edit" from the upper right Options in Editor
7. Scroll to the end of the file and add the line lockscreen.rot_override=true, beware of syntax corruption due to automatic grammar correction
7. Exit ES Notice-Editor, answer question "Do you want to save build.prop" with "Yes"
8. Leave ES File Explorer and restart the phone
That's it, - check after reboot that the logon lockscreen turns while you turn the phone (maybe with some delay while turning)
Click to expand...
Click to collapse
Thank you for outlining this -- it helped me remember what to do!
and kaferei
Jeffreycat said:
Thank you for outlining this -- it helped me remember what to do!
Click to expand...
Click to collapse
Indeed -- very helpful and worked for me as well!
basic build.prop editing to enable pie on sgh-i747m
Shibang said:
Indeed -- very helpful and worked for me as well!
Click to expand...
Click to collapse
Thanks for providing the info on this basic build prop prop editing !
Ive been reading CyanogenMod 10.1 – A Complete Hands-On Review & Guide
by Haroon Q Raja and really wanted to enable Pie,etc on my rooted Samsung SGH I747m. With your help I was able to edit my build prop as was suggested by a comment I picked up on to:
ro.product.manufacturer=LGE
ro.product.model=Nexus 4
This didnt make any difference. Is there something else that needs to be changed?
Samsung G3 SGH-I747M Rogers
Cilraaz said:
...
On 4.1.2, you could add launcher.force_enable_rotation=true to make the default launcher rotate, but some say that doesn't work in 4.2 (I use Apex Launcher, so I haven't tried the stock launcher) and you have to modify bools.xml, as you stated. I don't know if it requires both the bools.xml edit and build.prop entry or not, though.
The build.prop change for the lockscreen works without the bools.xml edit, though.
Click to expand...
Click to collapse
Redscorpian said:
Does anyone have an answer to whether they have changed the code in 4.2? I can't find a bools.xml file anywhere - and no one seems to point at it. Also, no one says exactly where the suggested code should sit in the build.prop file - at the end, in the 'build' section, at the front? And it doesn't work on android 4.2.2 as far as I can tell although the terminal emulator temporary method works. And while you're firguring that out - can you tell me a way (without an app) to get the screen to stay awake after rebooting? Why won't that option remain set in Developer Options?
Click to expand...
Click to collapse
No one can tell?
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
madd0g said:
Some users who flashed the leaked JWR66N on their N4's report there is no full app rotation anymore in the Camera app, just the icons. So another change to feel optimistic about 4.3.
Click to expand...
Click to collapse
Speaking of the camera, I played around with a iPad yesterday at the local store, i felt that Apple's shutter button have a better placement as compared to Google's. The shutter button is placed by the right side of the app, falls just nice of my thumb.
Beamed from my Grouper
I dont know how many other people out there use androids built in vpn, but i hate the fact that you are required to use a security screen (pattern, pin, password) to do so. I have found a way to bypass this if you are rooted. This has only been tested on the stock kk rooted ota. However i would think it is the same on almost any stock based rom.
This assumes you already have your vpn and a security screen setup and working.
Go to the market and download a root capable data base (db) editor. I use SQLite Editor which is a paid app, but im sure there are free ones too.
Open the db editor. SQLite Editor sorts it by the app (in this case Android System) the data base is associated with, others may not work this way and may require you to navigate to the db file directly (/data/system/locksettings.db).
Open locksettings.db and select the locksettings directory. Look for the line that says "lockscreen.password_type". Under the value colum it will show some random number. Select the line and edit the value to be 0 (zero). Save if required by your db app, and restart your phone.
When it reboots you should no longer have a security lock screen only the swipe up screen. When you go to settings - more - vpn, it will still say you need to setup a security lock. Hit CANCEL, and it will show you your list of setup vpn's. Select one and connect. Boom working vpn with no pattern, pin, password screen required.
To undo this just go to settings - security - screenlock, and setup a new lock pattern, pin, or password.
You can also disable the swipe up lock screen by editing the "lockscreen.disabled" value in the locksettings.db to be a 1 instead of a 0.
good write up, thank you sir.
Where did you get stock kk rooted?
Sent from my HTC One
I was already unlocked and s-off, so i ruu'd took the kk ota and then rooted it. But i believe santod has his thread in development where you can download the stock rooted kk rom.
an alternative method
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Alternative method
found it on another forum
The process does not require rooting its more like a bug
worked on my i9300 with 4.3 firmware
1. Add a VPN
2. Lock the device with a pin
3. Enter the pin wrong 5 times
4. Press OK to the message that pops up
5 Press Forgot Pin
6. Sign into your Google Account
7. Select pin lock
8. Press cancel.
and now u got unlocked screen with working vpns
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Hirishiolo said:
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Click to expand...
Click to collapse
Yeah i have the same issue (nexus 10 rooted 4.4.3 stock)
Hit cancel, and it should bypass it.
cmlusco said:
Hit cancel, and it should bypass it.
Click to expand...
Click to collapse
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
schickel said:
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
Click to expand...
Click to collapse
same for me, it does not work
ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
Thank you :good:
ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
Click to expand...
Click to collapse
My locksettings.db is empty as well. Does anybody know why?
Geilerzucker said:
My locksettings.db is empty as well. Does anybody know why?
Click to expand...
Click to collapse
on mine one its not empty
Hirishiolo said:
same for me, it does not work
Click to expand...
Click to collapse
i also followed the tutorial now and same as you guys, doesnt work
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
is there any other solution?
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Clauu said:
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Click to expand...
Click to collapse
Try a different file manager.
It failed like that for me with ES File Explorer,
but worked when I used SM File Browser.
---------- Post added at 10:53 AM ---------- Previous post was at 10:42 AM ----------
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
Click to expand...
Click to collapse
Tap on the "QUERY *" button to see the file contents.
---------- Post added at 11:11 AM ---------- Previous post was at 10:53 AM ----------
pajenn said:
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
Click to expand...
Click to collapse
What I do here: just type something.. anything, doesn't matter. At least one character.
Then on the next screen, where it asks to set up a lockscreen, just Cancel.
This seems to be necessary once per boot -- any password, different time or the same, works.
After that it lands me on the VPN manager screen, all functional.
Well I kind of messed up. I tried to open with SQLite but it would give me an error 14. So i decided to try to open just like that using ES Explorer and edit it like regular note(SQL is totally different I had no idea). Anyways i didnt edit anything but now i cant set a pin or any type of security on my phone. When i try to set up a pin it still shows a swipe and when i try again my Note 3 freezes and get an error message saying settings stopped responding.
Any idea on how to fix this? Im rooted and im running the latest firmware 4.4.2 if that helps.
Is there a way of removing the default APN on a Galaxy Note3 (running Android 4.3)? I have the phone rooted.
Thanks!
m4f1050 said:
Is there a way of removing the default APN on a Galaxy Note3 (running Android 4.3)? I have the phone rooted.
Thanks!
Click to expand...
Click to collapse
create a new one, if u cant delete it...
and add this to APN type...
APN type= default,supl,mms (this will make it default APN)
mdiaz33685 said:
create a new one, if u cant delete it...
and add this to APN type...
APN type= default,supl,mms (this will make it default APN)
Click to expand...
Click to collapse
Thanks but I already did that. I am looking to delete the default T-Mobile US LTE one
You can't and there is no real reason to bother to remove it anyway. Just use the new entry.
You can remove it, but it requires a SQL editor.
Go to data/data/com.android.providers.telephony/databases and edit nwk_info.db
Select the "carriers" table and locate the T-Mobile US LTE / 310260 entry (should be line 26)
Scroll all the way to the far right and change the editable value from 0 to 1.
Restart your phone and you should be able to edit the entry.
The other option is to edit /system/etc/apns-conf.xml directly.
Remember the first rule in tweaking your system... make a backup copy first.
rjohnstone said:
You can remove it, but it requires a SQL editor.
Go to data/data/com.android.providers.telephony/databases and edit nwk_info.db
Select the "carriers" table and locate the T-Mobile US LTE / 310260 entry (should be line 26)
Scroll all the way to the far right and change the editable value from 0 to 1.
Restart your phone and you should be able to edit the entry.
The other option is to edit /system/etc/apns-conf.xml directly.
Remember the first rule in tweaking your system... make a backup copy first.
Click to expand...
Click to collapse
See, this is the type of answer I like to get... not "create a new one" or "you don't need to remove it".. If I want to remove it, LET ME REMOVE IT, it's my phone!
Thanks rjohnstone (for telling me how to edit the entry) and mdiaz (for the APN types)! BTW used SqlLite, great app, only $2.99 on Play store and works VERY well!
Attached is a (simple) Magisk module which allows you to disable:
- app measurement
- app analytics
- app firebase tracking
- app crashlytics
In short, each APK (system app or user app) may have background services to do all sorts of tracking and ad handling. Module allows you to disable (or enable) those services.
You must obviously be rooted and have a working Magisk.
How to install:
Code:
a) download attached zip file
b) push the zip file to your /sdcard folder (use: adb push dss.zip /sdcard)
c) open Magisk
d) in the panel at the bottom, tap the "modules" icon
e) at the top, select "install downloaded module"
f) navigate to your /sdcard folder
g) select dss.zip
h) tap the reboot button
After installation:
The script must be run manually using the command line. First, open a shell using adb:
Code:
> adb shell
$ su
#
The script has the following syntax:
Code:
dss {disable|enable} {user|system} <package-name>
You must provide 2 or 3 arguments to the script:
a) first argument is "disable" or "enable" (by default Analytics/Firebase/etc services are enabled)
b) second argument is "user" or "system" (use "user" for any app wich you installed using an APK or installed from play store; use "system" for apps which come as part of the official Google image, e.g. contacts/dialer/messaging)
c) the third argument is optional and - if present - contains the name of a specific package (e.g. com.banking.mybankapp)
Examples:
1) disable analytics/firebase/etc for ALL user apps
Code:
# dss disable user
2) enable analytics/firebase/etc for ALL system apps (this is the default)
Code:
# dss enable system
3) disable analytics/firebase/etc for Feedly
Code:
# dss disable user com.devhd.feedly
The script will show you output of the services which get disabled, for example for the Feedly case:
Code:
Component {com.devhd.feedly/com.facebook.internal.FacebookInitProvider} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsJobService} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsReceiver} new state: disabled
Component {com.devhd.feedly/com.google.android.gms.analytics.AnalyticsService} new state: disabled
Occasionally it can happen that after disabling Analytics/Firebase/etc, the app no longer works. Then just "enable" again. Apps should - in principle - be resilient but some are not coded properly. Alternatively, you can try to figure out exactly which of the services causes the crash and (manuall) re-enable that service (but you will need to look into the source code a bit). When you run this on Feedly for example, you will find that it crashes afterwards (reason is that the script disabled com.devhd.feedly/com.facebook.internal.FacebookInitProvider). You can re-enable that service individually using:
Code:
pm enable com.devhd.feedly/com.facebook.internal.FacebookInitProvider
or just do:
Code:
# dss enable user com.devhd.feedly
(that will re-enable all the services previously disabled)
You can also disable stuff for system apps, e.g. com.android.contacts (Contacts), com.android.vending (Play store app), etc ...
However, one BIG WARNING. If you disable this for system apps, make sure to re-run the script with the 'enable system' argument BEFORE running a Play-systemupdate otherwise that may bootloop. So, to be on the safe side, if you have used the script to disable services in system APKs, then run:
Code:
# dss enable system
before doing the Play-systemupdate.
I you want to check the source code (simple sh script), just unzip the dss.zip in a new directory and check out the file system/bin/dss. It's not complicated ...
This will save you (a tiny litte bit) of battery, but more importantly, a lot of nasty "tracking" (which you don't need).
Changes are persistent across reboots.
github: https://github.com/foobar66/dss
Notes:
When I run this for the user apps on my phone, I have ~189 background services that get disabled.
If you want to know more about firebase, look here: https://firebase.google.com/
And here is some detail about app analytics: https://developers.google.com/analytics/devguides/collection/android/v4
If you want to know the name of your APKs/packages, do:
Code:
# pm list packages -f
Looks like a brillant tool, I'll test it, thanks a lot for this very user-friendly and efficient tool!
Yes brilliant tool thanks for this!
I'll third, I run this on my device at the moment on user apps. Great tool and does what it says it will do. Thank you for this!
Great tool.
Thanks for the effort and sharing.
Great share
wow, thanks OP
I did disable analytics/firebase/etc for ALL user apps and scrolling facebook on Chrome no longer jittery.
Flashed and disabled analytics on ProtonAOSP. Thank you for the tool.
This would be great on the Pixel 5
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Really useful tool, mate! Will be trying on my device once I get Magisk to work.
Utini said:
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Click to expand...
Click to collapse
Also:
You should implement that the module saves the output of the disabled packages.
That way you can easily (and safer) restore those packages e.g. when uninstalling the module?
Same goes for all your other modules:
They tinker with the system but how can I safely restore the original form and uninstall the module?
Utini said:
Also:
You should implement that the module saves the output of the disabled packages.
That way you can easily (and safer) restore those packages e.g. when uninstalling the module?
Same goes for all your other modules:
They tinker with the system but how can I safely restore the original form and uninstall the module?
Click to expand...
Click to collapse
Well, as this is commandline based its basically all there in OP
BTW saving the output is easy, just expand the commandline by "> filename.log" (without the "")
And the safe way back before uninstalling is just dss enable user / dss enable system
s3axel said:
Well, as this is commandline based its basically all there in OP
BTW saving the output is easy, just expand the commandline by "> filename.log" (without the "")
And the safe way back before uninstalling is just dss enable user / dss enable system
Click to expand...
Click to collapse
What I was trying to say is that the module should use the output for when restoring / enabling.
If you have looked at the source code of the module, then you will see that it basically works by creating an array of queried packages to disable/enable. I could imagine that due to what ever fault / later update / package changes / ... the "enable query" might look different than the "disable query" that was run months before. Meaning that there is a chance that not everything that got disabled will get enabled again.
Looks amazing so far, not just for Pixel 6 but good for other phones too
Utini said:
207 user packages got disabled.
Do I have to also run "dss enable system" after the initial "dss disable user"?
Will I have to re-run this after an app updates?
Will I have to re-run this after a monthly android update?
Click to expand...
Click to collapse
1. No, your own choice if you want to disable the services for system packages
2. No
3. No
Utini said:
What I was trying to say is that the module should use the output for when restoring / enabling.
If you have looked at the source code of the module, then you will see that it basically works by creating an array of queried packages to disable/enable. I could imagine that due to what ever fault / later update / package changes / ... the "enable query" might look different than the "disable query" that was run months before. Meaning that there is a chance that not everything that got disabled will get enabled again.
Click to expand...
Click to collapse
Indeed ... that would be a very good improvement ... I´ll have a look at implementing that.
Thanks for the suggestion.
MrRob0t said:
This would be great on the Pixel 5
Click to expand...
Click to collapse
Will work on any phone.
foobar66 said:
Indeed ... that would be a very good improvement ... I´ll have a look at implementing that.
Thanks for the suggestion.
Click to expand...
Click to collapse
It would also be useful for re-running the module after installing some new apps.
E.g. re-running dss disable user will try to disable all user apps even if 90% of them was disabled previously already.
If there was a "file" or "log" to compare what was disabled already, then it could only care about what is now newly installed