[HELP CENTER] [Guide] How to prevent, handle wakelocks , and save battery life - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

[HELP CENTER] How to prevent § handle wakelocks § save battery life[GUIDE] [β]​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thread Purpose:
Information, help and support for those, who experiencing battery drain.​
Some of the material was taken from respective BetterBatteryStats thread - Check it out, for the sake of information and correct explanation. I take no credit for this info and grateful for it's existance.​
References and credits: @ahalford for all his hard work
& : Chasmodo - you know, who you are!
For the info & software: BetterBatteryStats creator & team
What is wakelock and why it may cause battery drain:
Wakelocks or to be more precise partial wakelocks is a pattern (in fact a class) than helps devs to make sure that important pieces of their code do not get interrupted.
Basically the phone has (simplified, kernel devs don't shoot) three states:
1. awake with screen on
2. awake
3. sleeping (that's you phone favorite state)
The transitions are from (1) to (2) and finally from (2) to (3). Now as long as you use your phone it's in (1) and does not leave that state as long as you keep using it interactively. If you stop using it the phone is aiming to go to (3) as fast as possible.
And here's where wakelocks are important: as our phones as smartphones they tend to do background processing. Some of this processing is important like e.g. making a phone call, listening to music or synchronizing your contacts.
As the phone wants to go from (2) to (3) and on the other hand you don't want to hang up while you are in a call the app keeps hold of a wakelock to prevent that transition. When you hang up the partial wakelock gets release and here we go (the phone goes to sleep).
So partial wakelocks is a tool and it's not something that we should forbid for obvious reasons. Now there are cases when the design on an app is not real life proven (conditions of poor of no coverage) and the wakelocks have negative effects because they are held unnecessarily or for too long.
How can we identify it?
BetterBatteryStats app identifies these wakelocks and using your expertise or the once from our users here you can understand what happens and find a strategy to change that for the better.
How can we eliminate it, if we found such?
The purpose of this thread - is support per situation, if solution has not been
found after reading FAQ & Tips section. You should provide BetterBatteryStats dump file, data about rom/kernel, (possibly) list of installed apps and describe your situation.
How to provide dump file:
Code:
[B]- Install the app and grant it root access.
- Plug/unplug the charger
- "Menu" - "More" - "Set Custom Ref." - creates a reference point
- Leave the phone with screen off for some time, 4 to 6 hours - this must be done so we can have uncluttered data as a basis for valid analysis
- Ensure you have the same wakelocks, that you've been about to report.
- Save a dump file - "Menu" - "More" - "Dump to file"
- It will look like - sdcard/BetterBatteryStats-2012-09-10_191252250.txt, for example
- Check that the chapters "Kernel wakelocks", "wakelocks" & "alarms"are populated.[/B]
I'm not posting the app FAQ on purpose - those, who can't handle it, can just provide a dump file. Those, who can understand or learn fast - don't need it
But. Brief explanation, about where to look at the wakelocks:
1.Set your reference as "Since unplugged" in the second line.
2. Then, in the first line: "Other" - look at the "Awake" vs "Screen on". If it differs a lot, continue with a drill-down.
3. First line - check under "Partial Wakelocks" and "Kernel wakelocks".
4. "Menu" - "More" - "Raw kernel wakelocks"
5. For more help: "Menu" - "Help" - "Getting started" or "How to".
6. Same web links:
Help:
http://asksven.github.com/BetterBatteryStats-Knowledge-Base/help.html
How to:
http://asksven.github.com/BetterBatteryStats-Knowledge-Base/howto.html
App Screenshots:
[/FONT]
Want to install Cyanogen or AOKP rom and have questions? Get here.

TYPICAL REASONS FOR WAKELOCKS & APP SUCKERS, KNOWN ISSUES:
- Any kind of messengers, social clients – like Skype, Facebook, Twitter, etc. Any of those, who want to be online, receive a push messages, sync every while. If it’s must to have them, disable it in accounts sync settings, and disable notifications in each app’s setting.
- “Energy savers” – Green Power, Timeriffic, etc. They mess with the system power policy, if you choose to enable/disable wi-fi, gps, data, Bluetooth, etc. Especially, Samsung’s one is known as problematic.
- “Soft-buttons”, so called “power button savers” – like ScreenOff & Lock and such. Related to previous group. Let the hardware do the job.
- Task killers - If it kills some services in the middle of their action, it will cause’em start all over again or even stuck, and eat your precious battery resources. If you have to use it (like in case with JB 4.1 memory leak issue, do it manually).
- Your sound settings – screen vibro & sounds on tap, haptic feedback – disable it.
- Media Scan – process, that will run after each fresh install & reboot. Typically takes about 10-15 minutes, runs on high CPU frequency. If stuck more than this, causes no Deep Sleep (can be seen in CPU Spy app) – you have an issue with Media Scan. It can stuck on large files directory – nothing to do here, unless you can reduce files number. Another case – problematic memory cluster, and there is only solution to back your data, format your storages, and start over.
- Startup - Check it – do you really need this entire long startup list? Throw some; it will only make the system act better.
- Accounts sync – again: Minimize your list. Drill down every account setting, Google especially: Picasa, Google Disc, G+, etc.
- App settings – always drill down your app settings – it may be some nasty hidden setting, that enables your app to be in constant action. No concrete advise, treat each app individually.
TIPS:
- Always perform clean install! Backup your stuff – App2zip (free on market) app, Titanium, whatever – spend some time for formats and setting up your settings, you will only have profit on this.
- Don’t judge your battery consumption right after new rom/kernel install. Especially in the first hour, while Media Scan is busy with scanning your storage. System needs some time to settle.
- It is highly suggested, after you installed all apps and made your configurations, to reboot recovery and clean your cache & dalvick.
- If you’re installing custom kernel and any .zip flashable files, don’t do it in the same time with rom flashing. Flash the rom, reboot system, let it settle, then reboot recovery again, flash your kernel/mods, let it settle again.
- WI-FI sleep policy: leave it on “Always”. Note’s wi-fi chip consumes nearly zero energy, and it would be much healthier to leave it on.
- WI-FI home network: if you’re on dynamic IP, set to maximum your DHCP lease time in router setting, and bind your device to the MAC address. Also, fix your WI-FI channel and frequency both on device and router.
- *Don’t mess with Fast Dormancy app, if you don’t have dormancy related wakelocks, or if you don’t know your cell operator dormancy setting! And, on JB 4.1 it’s sometimes more preferable to leave it on, than to deal with some weird wakelocks, that may appear. Another case – if your operator setting for dormancy is “off”, app won’t discover it, and, actually, you may enable it instead of disabling it.
Wakelocks - XDA Wiki - take a look at it, may be very useful.

AlarmManager
Author(s): sven, credits to andy2na @xda-dev
Ranking: n/a
Speaking Name: Alarm Manager
Rationale: AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast. Once onReceive() returns, the Alarm Manager releases this wake lock. This means that the phone will in some cases sleep as soon as your onReceive() method completes.
Know actions: AlarmManager itself is not generating partial wakelocks but the applications (intents) that were set to be called when an alarm goes off do. Alarms can be listed through the menu "Actions - Alarms".
Here is a comprehensive guide to analyse Alarms: In order to find those Intents run the command dumpsys alarm.
This will dump all the alarm events so you can see what is invoking AlarmManager as a wakelock. From there you can find the culprits that have a lot of wakeups. In some instances, you cant do anything about it (Android System), but in others, you can uninstall or disable notifications. Hope this helps in solving your excessive AlarmManager problems.
Scroll to the " Alarm Stats" near the bottom, it should look like this:
com.levelup.beautifulwidgets
246776ms running, 10 wakeups
10 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER flg=0x4
1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4
com.motorola.blur.datamanager.app
22ms running, 0 wakeups
1 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4 cmp=com.motorola.blur.datamanager.app/.DataManagerCheckinService
ccc71.bmw
130743ms running, 1585 wakeups
1585 alarms: flg=0x4
com.motorola.kpilogger
2156ms running, 0 wakeups
13 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4
com.gau.go.launcherex
528ms running, 10 wakeups
6 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4
4 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4
As you can see, in my case, the services that have invoked AlarmManager seem to be BeautifulWidgets (to update the clock everytime the minute changes - 1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOC K flg=0x4)
Battery Monitor Widget (obviously to pull the mW of the battery) - 130743ms running, 1585 wakeups
You could also reduce the amount of AlarmManager events by simply turning off Wireless location, Signing out of Google Talk, and turning off notifications or updates in apps you dont really use.
TLDR: AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much.
Known conditions of occurence:
Related wakelocks:
References:
http://forum.xda-developers.com/showpost.php?p=17207454&postcount=861
http://developer.android.com/reference/android/app/AlarmManager.html
AudioOut_1
Author(s): xda
Ranking: n/a
Speaking Name: AudioOut_1
Rationale: AudioOut is used to play notification and system sounds.
Know actions: From the home screen... Menu -> Sounds -> uncheck "Touch Sounds", uncheck "Screen lock Sounds"
Known conditions of occurence: Each time the screen is touched or locked.
AudioOut_3
User's experience
ConnectivityService
Author(s): sven
Ranking: n/a
Speaking Name: ConnectivityService
Rationale: Service responsible for tracking data connection / apn, establish and maintain connections. This wakelock is held during transition between data connections.
Know actions: May be conditioned by using a different radio/modem or bad coverage, may be reduced by forcing 2G.
Known conditions of occurence:
Related wakelocks:
References:http://grepcode.com/file/repository.../ConnectivityService.java#ConnectivityService
deleted_wake_locks
Author(s): sven, credits to Tritonio_GR @xda-dev
Ranking: n/a
Speaking Name: deleted_wake_locks
Rationale: In the API available to android drivers it is advised to call wake_lock_destroy before freeing the memory of the wakelock struct that they created. This is done above all on shutdown, but also in a few situations where a driver is unloaded dynamically from the kernel. Whenever it happens, the destroyed wakelocks disappear from the list but their stats are added up to this pseudo-wakelock to the deleted_wake_locks. This allows knowing that a set of old wakelocks had a combined set of stats that this entry shows. The stats of this entry do not increase unless additional real wakelocks that have non-zero stats are destroyed.
Know actions: Since this is merely an entry that combines the activity of all the kernel wake locks that no longer exist, there's nothing that can be directly done to reduce this entry. The best course of action is to identify the wake locks that generate activity and that are later deleted, before that happens and they end up showing in a combined way on this entry.
Known conditions of occurence:
The Wifi driver is one known source for kernel wakelocks that are destroyed whenever the driver is unloaded (when Wifi is disabled manually or as part of the turn-off policy). Wakelocks such as wlan_rx_wake and wlan_wake, when the driver is unloaded, will no longer show up in the list and their stats be added to the deleted_wake_lock previous values.
Related wakelocks:
References: http://forum.xda-developers.com/showpost.php?p=27227201&postcount=5644 http://forum.xda-developers.com/showpost.php?p=28915936&postcount=6671 http://www.netmite.com/android/mydr...k.chttp://elinux.org/Android_Power_Management
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint
Author(s): credits to lmihaila @xda-dev
Ranking: n/a
Speaking Name: AndroidEndpoint
Rationale: This wakelock has been found to occur under certain non reproducible conditions, showing high wakelock counts and in certain cases high wake times. As the reasons are not exactly known there is no garanty that this wakelock does not occur for other yet unknown reasons.
Know actions: In one case (see ref) this wakelock was successfully removed by changing the proxy / re-creating an APN definition and leaving the proxy blank for that APN. The "faulty" proxy was predefined for the provider Orange but it is not excluded that proxies from other providers show the same effect.
Known conditions of occurence:
Conditions are unclear, to be confirmed
Related wakelocks: Other GTALK_ASYNC_CONN partial wakelocks
References: http://forum.xda-developers.com/showpost.php?p=22786143&postcount=3416
network-location
Author(s): sven
Ranking: n/a
Speaking Name: Network Location
Rationale: The network location service is responsible for providing coarse grained location information to requesting applications.
The frequency of updates (and of wakelocks) is related to the precision requested by the application (max. time between updates, precision in meters).
Examples of app requesting coarse grained location: weather widgets, latitude, most social tools, google+
Know actions: Actions to reduce wakelocks:
• Find the responsible app: look for all network-location wakelocks and check for the responsible apps on the second line of the list
• Check the settings of the app to see if the precision can be changed
• Use the benefits of Wifi based location (stable location minimizing the update frequencies)
• Look for alternative apps with a better design
Known conditions of occurence: Poorly designed apps with too high requirements on precision will drive the Network Location Service up.
Unstable network conditions (frequent handovers between towers) may trigger location updates.
In some cases updating the radio/modem has effect on the network location: the location is based on the tower information delivered by the RIL.
Related wakelocks: LocationManagerService, NetworkLocationLocator, WifiService, GpsLocationProvider, network-location-cell-update
References:
http://developer.android.com/guide/topics/location/obtaining-user-location.html
http://developer.android.com/reference/android/location/LocationManager.html
PowerManagerService
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: PowerManagerService
Rationale: This kernel wakelock is a placeholder for all partial wakelocks being held in userland.
Know actions: Use "Partial Wakelocks" to drill down the applications / services causing wakelocks.
Known conditions of occurence:
Some devices show userland wakelocks as a total named PowerManagerService
suspend_backoff
Author(s): sven, credits to Tungstwenty @xda-dev
Ranking: n/a
Speaking Name: suspend_backoff
Rationale: suspend_backoff is triggered whenever there's a rapid succession of sleep-wakeup-sleep transitions in a short period of time (10 occurrences within x ms IIRC). When that happens, SB makes sure the device is continuously awake for a bit instead of alternating a lot. The KWL count indicator could give a hint about the source of those continuous wakes, but not a definite answer because it doesn't show their time distribution.
Know actions:
Known conditions of occurence:
In relation with Chrome: http://forum.xda-developers.com/showpost.php?p=28676218&postcount=24 In relation with Wifi turning on/off when the screen goes on/off
Related wakelocks:
References:
http://forum.xda-developers.com/showpost.php?p=28836538&postcount=6603
svnet
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: svnet
Rationale: basic radio management (Galaxy S/S II specific)
Know actions: No direct actions known, may be conditioned by using a different radio/modem
svnet dormancy
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: svnet-dormancy / multipdp (those are synonyms, depending on android version)
Rationale: svnet-dormancy is a kernel wakelock related to cell data transfers - Fast dormancy or not, you get a 6 second wakelock any time the radio transfers data
Know actions: Change the duration of the wakelock (use at your own risk). Reduce the wakelock by reducing the amount / number of data traffic requests
Known conditions of occurence:
Caused by data traffic
Sync
Author(s): sven
Ranking: n/a
Speaking Name: Account Sync Service
Rationale: The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.
The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.
Potentially the wakelock time is prone to raise in case of bad data connectivity.
Examples of accounts are: twitter, google+, linkedin, google mail
Know actions: Actions to reduce wakelocks:
• Remove any unwanted accounts
• Check the settings and remove any unwated options (contact sync)
• Check the frequency of the sync and see if you really need it as defined
Known conditions of occurence: Under bad data connectivity conditions, with poorly designed Sync providers
Related wakelocks: none
References: A known bug related to gmail: http://code.google.com/p/android/issues/detail?id=9307
SyncLoopWakeLock
Author(s): sven
Ranking: n/a
Speaking Name: SyncLoopWakeLock (Account Sync)
Rationale: SyncLoopWakeLock is the wakelock used by the Android SyncManager (android.content.SyncManager) and was introduced starting in 4.01. The sync service is responsible for syncing all the accounts from "Settings" - "accounts and sync". A wakelock is held while the sync process is running.
The more items are getting synced and the more often the sync occurs the higher the wakelock time will be.
Potentially the wakelock time is prone to raise in case of bad data connectivity.
Examples of accounts are: twitter, google+, linkedin, google mail
Know actions: Actions to reduce wakelocks:
• Remove any unwanted accounts
• Check the settings and remove any unwated options (contact sync)
• Check the frequency of the sync and see if you really need it as defined
Known conditions of occurence: This wakelock is held by the SyncManager while handling sync actions (method handle()). Previously this wakelock was known as sync. Under bad data connectivity conditions, with poorly designed Sync providers this wakelock is held longer.
Related wakelocks: sync
References: https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/sync
Sources: New implementation:http://grepcode.com/file/repository...droid/content/SyncManager.java#SyncManagerOld implementation (sync):http://grepcode.com/file/repository.../SyncManager.java#SyncManager.0SYNC_WAKE_LOCK
vbus_present
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: vbus_present
Rationale: vbus_present is a kernel wakelock that is held when the charger is connected.
Know actions: No action required.
Known conditions of occurence:
When plugged in to charger / charging USB port
wlan_rx
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: wlan_rx
Rationale: Wifi chip received a packet from somewhere - On a Galaxy S II, lots of these combined with the fact that the device takes 650 msec to resume from suspend and 150 to go back to sleep means that occasional wifi packets coming in will skyrocket Android OS usage. As an extreme example, run the following from a Linux box when wifi sleep policy is "never" and watch your deep sleep percentages plummet, your battery drain, and Android OS skyrocket: ping -i 5 <wifi IP address of phone>
Know actions: Use a sniffer to determine the cause of the traffic.
Known conditions of occurence:
Related wakelocks: wlan_wake References:
wlan_wake
Author(s): sven, credits to Entropy512 @xda-dev
Ranking: n/a
Speaking Name: wlan_wake
Rationale: wifi chip woke the CPU (Usually this fires and leads to a wlan_rx wakelock).
Know actions: Use a sniffer to determine the cause of the traffic.
Known conditions of occurence:
Related wakelocks: wlan_rx References:
***NEW***L2_HSIC:
HISC is the interface that connected the main Soc processor ( Also called Applciation Processor AP) to the modem ( 3G or 4G if there are two modems separately )
HSIC is uses the standard USB core library. And it is standard given by usb.org. The HSIC by itself consumes very less power and is one of the very power efficient and space efficient ways of interconnecting chips. Currently common to Qualcomm and Sammy Exynos architectures.
The reason seeing too many HSIC wake lock and other wake ups is due to the fact that the HSIC interface is waken up by modem (resulting modem scenarios are also so many) .
Also one important reason is EFS sync.
A concept : that the new modem architectures doesn't support a flash storage.(Saves lot of cost to manufacturer) .So every time modem needs to store something , it wakes up hisc interface and ask the AP (Main processor) to store it for him in his flash.
So this CP storing via AP is a fairy frequent activity even during suspend/deep sleep mode. Remember modem is periodically awake to do "Cell Update message" all the time.
I see the concern over this L2_hsic wake lock. I can say at this point that it is quite natural activity. and a necessary evil for smooth working of your modem( network 2g,3g,4g ) subsystem.
Every company including Sammy have some kind of power optimization done in the HSIC. So they taking care of this we considering fairy high battery drainer issue. .
If it is too high, modem/network can be blamed , if too many frequent network ( too many cell re-selection activity due to low RF reception) changes force the modem to do more activity, thus waking AP to do the work of storing its data over HSIC.

Remember: there is no app, that behaves in same way on different system. While it can drain on CM, it can be rock solid on the TW, and vice-versa. So, don't take those examples too serious and don't run to uninstall your apps just for preventive maintenance. Act per need.
So, as listed above, our Top Chart leader is Media Scan:
- Media Scan – process, that will run after each fresh install & reboot. Typically takes about 10-15 minutes, runs on high CPU frequency. If stuck more than this, causes no Deep Sleep (can be seen in CPU Spy app) – you have an issue with Media Scan. It can stuck on large files directory – nothing to do here, unless you can reduce files number. Another case – problematic memory cluster, and there is only solution to back up your data, format your storages, and start over.
Stopping the process won't help much, as on next reboot it will resume. Suggestion - charge the battery to 100% before Media Scan starts to rebel, and let it finish.
Another case - stopping any download (browser, market) in the middle. Media scan can possibly stuck until next reboot.
- Media Scan stuck:
1. You probably have some corrupted files, on which it stuck. Backup, start to restore to the step it was OK, to find the culprit
2. Folder with many files - likely to stuck or to spend a lots of time to scan it. Do the math. If you have to have this folder (likely to be a cache folder) - disable your media scan.
3. I/O scheduler - CFQ sometimes being reported as taking longer time to media scan to complete. Try NOOP.
4.And, of course, sometimes it won't work without formatting emmc and starting over.
- Google apps/services:
(in edit)
- Google Plus - there were cases, when this app, with auto-sync left, was just hanging in the memory and caused drain.
- Google Currents - depends on system, but there were also cases, when the service left active on CPU resource after it was even completely killed in task manager.
- Google Location service - if you choose to update your location by GPS only, expect wakelock, when GPS can't lock on a stellite. Second case - if location being updated from internet, and your mobile data is in bad state (poor signal, etc.). And, of course, it depends on apps, who require location update, and there are a lot of such. Whenever you don't need it - disable your locations service in Settings.
- Google Maps - brightest example of wakelock, caused by requiring your location. If you want to run Google Maps, disable the Location services, and disable Maps in start-up.
- "The Holy Trinity" - Skype, Facebook, WhatsApp. Just be sure to kill the app and & services, when you don't need it.
- Same applies for a clients of a kind: Viber, Twitter, etc.
- “Energy savers” – Green Power, Timeriffic, etc. They mess with the system power policy, if you choose to enable/disable wi-fi, gps, data, Bluetooth, etc. Especially, Samsung’s one (power policy) is known as problematic.
- “Soft-buttons”, so called “power button savers” – like ScreenOff & Lock and such. Related to previous group. Let the hardware do the job.
- Task killers - If it kills some services in the middle of their action, it will cause’em start all over again or even stuck, and eat your precious battery resources. If you have to use it (like in case with JB 4.1 memory leak issue, do it manually).
-Sopcast - very likely to stuck in memory, and to cause multi_pdp wakelock. Worse, it may keep consuming your precious data. Suggestion: reboot right after you ended using Sopcast.
- *new* - Weak network signal. Pretty understable, but still - weak network signal can cause some weird wakelocks. Especially, when you're on autosync on with mobile data, and the signal is weak, you will get "*sync*com.google.android.apps...." wakleock, "genie.widget" is you're syncing "new&weather" thing, RILJ is very likely, etc.

...

Amazing!! will save lot of threads/questions about battery drain.
It will be great if you can look at frequent questions about battery drain in Q&A and can include in Q&A of your thread.

Thanks, hopefully we'll build our database on the current and upcoming requests.

This should be a sticky.
Sent from my gnote as always Rooted & Deodexed Stock 4.0.4 XXLRQ HydraCore v4 STD

Well and comprehensively written, ahalford. Now let's wait for the first customers.

Well, I actually expected you to sleep, sir
Thanks, and I'm continuing with edit. Like I said, many things to be added later, as it always happens.

So, we started to collect our suspicious apps in post #4.
Please, don't hesitate to share your knowledge regarding such mVsuckers.

Thanx for your efforts mate...great work! :good:
Mike

This guide should be stickied
Sent from my GT-N7000 using xda app-developers app

Very Nice Guide. Thanks.
Sent from my GT-N7000 using Tapatalk 2

No one with problems? First client?...
:silly:

i don't know if my problem related or not... but here it is
as far i remember.... since the first time i installed official note ICS i'm facing a massive battery drain when wifi is on
i tried a lot of ROMs (Asylum at least two versions, Rocket three versions, Alliance , Liquidsmooth & black, CM9 official & Anidroid, PA & more)
its like draining 4-5% per hour without using, for example today i left the phone after one hour of use on 71% battery at 3 PM... now it's 7:17 PM and it's on 53% of battery.. thats 18% in 4 hours with maximum 10 minutes screen on
i'm running RR v11... before i tried to set wifi sleep policy to never(with other ROM) & the drain was gone with it
any suggestions on the files i need to upload if you could help..??

smarda7a said:
any suggestions on the files i need to upload if you could help..??
Click to expand...
Click to collapse
Start with dump file - it is exactly described in the OP (1st post) - How to provide a dump file.
Before this - look at posts #2 & #4 and try to apply the possible.

smarda7a said:
i don't know if my problem related or not... but here it is
as far i remember.... since the first time i installed official note ICS i'm facing a massive battery drain when wifi is on
i tried a lot of ROMs (Asylum at least two versions, Rocket three versions, Alliance , Liquidsmooth & black, CM9 official & Anidroid, PA & more)
its like draining 4-5% per hour without using, for example today i left the phone after one hour of use on 71% battery at 3 PM... now it's 7:17 PM and it's on 53% of battery.. thats 18% in 4 hours with maximum 10 minutes screen on
i'm running RR v11... before i tried to set wifi sleep policy to never(with other ROM) & the drain was gone with it
any suggestions on the files i need to upload if you could help..??
Click to expand...
Click to collapse
1. Install BetterBatteryStats if you don't have it already
2. Charge your Note, set 'Custom Reference Point' in BBS
3. Don't change your normal setup, but don't touch your phone for at least 4-5 hours (overnight perhaps)
4. After that start BBS, hit menu and choose 'dump to file'
5. Locate the dump file in root folder of one of your SD cards
6. Come back here and attach the dump file to your post
7. You'll get help

No deep sleep at all on PA and CM10
Thank you in advance for your time and attention!
After official ICS ROM (no probleme at all) I flashed HydraCore kernel and paranoidandroid from Utacka and here is my problem: my SGN is not use Deep Sleep - it is unused CPU state according to CPU Spy (see screenshot). Was trying to change kernel to official CM, was trying to flash CM10 ROM - no chance to make my Note go to deep sleep.
Here is the dump of BBS stats.
Thabk you in advance for any help!

200mpx said:
Thank you in advance for your time and attention!
After official ICS ROM (no probleme at all) I flashed HydraCore kernel and paranoidandroid from Utacka and here is my problem: my SGN is not use Deep Sleep - it is unused CPU state according to CPU Spy (see screenshot). Was trying to change kernel to official CM, was trying to flash CM10 ROM - no chance to make my Note go to deep sleep.
Here is the dump of BBS stats.
Thabk you in advance for any help!
Click to expand...
Click to collapse
Thanks for your submission:
Try the following steps:
1.Disable network location service in Settings - both by gps and by network
2. Disable all of screen sound & haptic feedback
3.Uninstall Aqua mail
4.Enter flight mode
5.Reboot to recovery, wipe cache & dalvick
6. Boot back to normal, exit flight mode, leave the phone for an hour.
И подчистите автозагрузку слегка...
Report back for the further escalation.

Related

Stopping NlpWakeLock, NlpWakeLockCollector and RILJ

I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
seh6183 said:
I have been trying on and off for over a year to eliminate these horrible wakelocks without disabling location services all together, and have finally found a solution.
I have tried wakelock terminator, amplify, and various other tweaks without the results I was looking for. I could only stop them by disabling location completely. Even with GPS only enabled the phone will eventually want to find its location and then if you're in a building where there is no GPS single, it will kill your battery trying to find one. So I finally stumbled across SlimLP which is an AOSP rom that has app ops baked into it. I found that if I simply modify the permissions of google play services and not allow it to use location, and also disable its ability to hold a wakelock, the nlp wakelocks (both) are gone forever. However, as soon as nlp is gone, the phone falls back to its backup plan which is RILJ to locate itself. So I then went into the phone apps permissions and disabled location and wakelock for it too. FINALLY these wakelocks are gone forever. My phone now loses 3% over 8 hours without disabling location services. There are literally 10 or less wakelocks system wide over 8 hours while I sleep, which is a huge contrast to the waking once every 25 seconds to check my location (or whatever absurd rate it was doing it). The only thing I can spot thats out of place it that google play services is registering a ton of alarms for location related stuff in better battery stats. I'm happy with this so far but feel it could be even better once I learn more.
What I really want to do is to be able to apply this to any android phone, such as my girlfriends z3. Unfortunately I can only get this to work with AOSP roms that have app ops built into them. I tried adding app ops to google based roms and even aosp roms and it doesnt work the same. If anyone could tell me what is different about roms with app ops built in, that would be great. I think we should look into this more to learn as much as possible because this affects everyone with an android phone. Thanks for reading.
Click to expand...
Click to collapse
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
niral7 said:
Wrong section...you might want to try Xposed and Amplify.
EDIT: I just realized I posted wrong section. For some reason, I thought this was Android Dev. Sorry
Click to expand...
Click to collapse
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
seh6183 said:
I've tried amplify as stated in the op. I'm surprised more people aren't bothered by wakelocks. I can't stand them.
Click to expand...
Click to collapse
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
niral7 said:
They're necessary to some degree. Google Now and other location-based/sync programs need them to work. They just get annoying when they're fired up every minute.
Click to expand...
Click to collapse
Well I've disabled the wakelocks and every location service including google now still functions as normal. The only benefit is me gaining 50% of my battery back. I just need to figure out what is so special about AOSP ROMs that have app ops baked in so I can apply these techniques to other phones.
So the App Ops Xposed module doesn't work the same way?
hayzooos said:
So the App Ops Xposed module doesn't work the same way?
Click to expand...
Click to collapse
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Glad you found a way to stop them and more so you decided to post your way to stop them here.
seh6183 said:
It works exactly the same except for some odd reason the wakelocks won't stop when you start disabling google play services and phone. It will disable other things without any problems. I'm thinking that maybe SlimLp has a different google play services app with different permissions or something. I'm not exactly sure what it is yet but I'm still looking into it on a daily basis. All I know is that 9000 wakelocks at the end of the day from google play services is UNACCEPTABLE and pisses me off. So I set out to find a way to stop them.
Click to expand...
Click to collapse
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Zwambo said:
Cataclysm Rom also has a App Ops. So I assume i can get same improvements as you do?
Or am I wrong and thinking the opposite direction?
Click to expand...
Click to collapse
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
setspeed said:
Doesn't the Phone app NEED to be able to keep the phone awake, so that it doesn't go to sleep mid-call?
Click to expand...
Click to collapse
It has no effect on the function of the phone at all except to eliminate the RILJ wakelock. I'm pretty sure this wakelock is the phones radio trying to triangulate your position using cell towers but not sure.
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Gentaz said:
All solutions I've seen or heard about untill now are just workarounds, and I found an elegant solution that allows geoloc to be on all the time.
I detailed it in a battery thread because of the savings it can offer : it consist of an app that replaces nlp with a local db : http://forum.xda-developers.com/showthread.php?p=59184505
I didn't try out with all google goeloc services but maps didn't seem to bother...
Click to expand...
Click to collapse
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
seh6183 said:
It should work yes. Go into google play services from apps, its in settings, then click modify, then disable location and wake lock. Do the same for phone. There are two phone apps and a dialer making it confusing. You'll want to disable the location and wakelock setting on the phone app which has the location toggle. The other phone app doesn't have a location toggle and you'll know that's not the right one.
After doing this, if you monitor with wake lock detector, you'll see that both NLP wakelocks are stopped completely instead of the 1000 an hour like usual. Same goes for RILJ. Google play services is still generating thousands of alarms each day for location related stuff and I have found a way to fix that as well but it needs more testing.
To put it simply, when my phone goes to sleep, that exactly what I want it to do, not appear as if its asleep and constantly check my location so that it can better offer me ads and places of interest near by.
Click to expand...
Click to collapse
Thx a million!
Will look in to those settings from the phone apps and google play services. Love it when the app ops is included in the ROM!
seh6183 said:
My solution has zero impact on location services as well. You're saying that your method totally stops NLP wakelocks and if you were to open maps, it would lock your location precisely?
Click to expand...
Click to collapse
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them☺
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on ?
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Gentaz said:
The fact that the gapps have a mind of their own is not big news, but alternatives exists to avoid dealing with them
I didn't say it will stop any wakelock (and I don't want to) : on the contrary, it consist of replacing the stock nlp with a more evolved one that allows to switch to a local db which is far less battery consuming for several reasons.
I didn't say it was "gps precise" either : it will locate you at the nearest antenna if you try a gps app like maps (did you actually read my link ?). Most of the time it has between 500m and 1500m (about a mile) uncertainty reported by the apps.
It just provides precise enough geoloc services for 95% of the apps you're using, even with your screen off like weather, loc. based profile mangers, local news, traffic, job/dating app or whatever... Granted : it won't compete with gps for you navigation or atronomy app but that's the 5% left when you'll switch the gps on
There should be a reason why you have so much wakelocks that does not involve blocking calls from a middleware as an answer.
Click to expand...
Click to collapse
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
What I did to get zero battery drain with GPS set on high accuracy:
- Download Disable Service from Google Play: https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=nl
- Go to System, then Google Play Services and disable everything that has something to do with 'Wear' and 'Fitness' since I don't use any of these features (for me these gave me wakelocks, but I'm not sure if this is the case for everyone), so: BrokeredFitnessService, WearableControlService, WearableService and WearableSyncService.
- Download LBE Security Master (http://forum.xda-developers.com/showthread.php?t=1422479) for its permission manager.
- Disable any location permission of all your apps that you don't want to use GPS (and other permissions to save more battery, but that's another topic).
I have to say I have Google Now disabled, and of course my phone is rooted to be able to use these apps. I run stock rom with stock kernel, and my battery is great with GPS enabled constantly.
seh6183 said:
If its crippling the phones ability to locate itself accurately then I am not interested as occasionally navigation is important to me. Also of it doesn't stop wakelocks then I am certainly not interested. The way that you word things makes it very difficult to get your point across I might add. I had a hard time following your post.
Click to expand...
Click to collapse
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she installs, but I prefer not having to explain mine what a wakelock is ☺
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to your antenna or ip when it is set to use network based location.
Gentaz said:
I guess you missinterpreted what I said : just enable gps when you need navigation... Gsm based location accuracy is ok for the all the rest.
- wakelock issues either came from the way the phone is set up or an uncommon situation causing this (bug, bloat, bad network or gps reception...) : blocking them is not a solution, it's a workaround and, if I undestood you correctly, is only valid for some cases and is fastidious/maintenance intensive. There are already many nexus 5 and other threads dealing with those issues anyway and It would be easier to just disable geoloc when screen is off.
- I suggested a solution less battery draining for 95% of goeloc based needs and is valid for most android phones and roms as long as you have root, not yet another a nlp/wakelock blocking "trick".
It's ok if your girlfriend doesn't mind having her z3 flashed with an ASOP ops enabled rom and learn to block the wakelocks of the new apps she's installing, but I prefer not having to explain mine what a wakelock is
- It doesnt cripple your phone at all, it extends its possibilities by adding a gsm based backend to the location provider : your phone was already doing the same except it had to go to a google hosted database to match your location to yourantenna or ip when it is set to use network based location.
Click to expand...
Click to collapse
Your solution is very interesting for sure and something I will try, but my gut feeling is that google play services is still going to look for my location just as often, waking the phone, even though it's communicating with a different database.
Also I'm not sure if you're suggesting that my phone specifically is having NLP wakelocks because it is broken or setup incorrectly, but if so that is totally inaccurate. All android phones are suffering from this wakelock whether the user is aware of it or not. The only ones not having NLP wakelocks are the ones who have disabled location services or somehow turned off the wakelock like I have.

Online User-Interface - Real-time Anti-Theft/Phone Status

Greetings everyone,
https://youtu.be/T9aKmLTujik
What you see above is a "Control Panel" for my own Galaxy S7 Edge. I host this on my own website.
This means it can be seen and accessed from anywhere in the world, on any browser and/or device.
For privacy and security, I will implement a login system in the near future.
It has a couple of neat features, but since they are written in Dutch I will translate them to English:
Information:
Check battery level/percentage and check if your phone is being charged or not
Warns the user from the control panel if the battery is low.
Warns the user from the control panel to pull out the plug out of charging when it is fully charged
Check if your phone is in a light or dark place. I have optimized the light sensor as best as I could, The results are pretty accurate
Clipboard of your current copied content on your phone
Shows the phone model and the date and time of the last update sent from your phone
Check if Bluetooth is enabled or not
Check if Wifi is enabled or not
Show the current WiFi name, Wifi Speed, Wifi Channel & Wifi Signal Strength
Show the current Data Carrier / Mobile Signal strength (Weak, Normal, Strong)
Shows the current Call Volume percentage
Shows the current Media Volume percentage
Check if the screen of the phone is turned on or off
Check if GPS is enabled or not ( There is also a Live Google Maps on the right side, showing where the phone is right now )
Checks if the phone in call / calling / or getting called. ( in other words, it shows the user is busy with a phone conversation )
Checks if the user is browsing on the internet on the phone or not. ( It will check if a browser is open, needs more adjustments for more accurate readings )
I am surprised at the speed of the operations.
It takes a total of 3 to 4 seconds after clicking on "take a picture" button to take a picture from the front-camera and Upload it to my google drive.
It also removes the picture from my phone after it has been uploaded. WIth combination of SMS control this can be a great anti-theft option.
The "Record Audio" function works great too. after clicking on it on the control panel, it starts recording audio, waits 10 seconds ( records for 10 seconds ), stops recording audio and then uploads it to a special folder in my Google Drive.
The "Send SMS" function is very fast. after clicking on it, it will take about 1.5 seconds to send the SMS from your phone.
For now, the number to send the SMS to is hardcoded, but I will make it a variable so that it will be possible to type in the number on your web control panel and send the SMS to the number from your browser.
The "LOCK your phone" function immediately lock your phone remotely, even when your screen is turned off. You can unlock it with the code that has been set up in the Tasker Event.
Clicking on the Wifi, Bluetooth & GPS icon will toggle them( on / off )
Clicking on the Phone (screen) Icon, Will toggle the phone screen ( turns it on and off )
Clicking on the Clipboard icon will copy all the content to your own clipboard.
Not only the text but the icons also change dynamically.
Grey icons represent a false variable (turned off / dark / not in call & etc ) and the blue icons represent the true variables.
For example, in the screenshot above, Bluetooth is turned off and wifi is turned on.
When the battery gets at 15% or less, the icon will turn red and green when it's fully charged (100%) and the user will get an alert box warning with a notification sound straight from the browser about the low battery / full charge . ( Sound and notification can be turned off if you wish).
I have wrote a script with AJAX (Asynchronous JavasScript and XML) to do all of this in Real-time and without page-reloads. AJAX refreshes the page information every second (or whatever the user wants) without reloading the page.
The controls in this control panel are in many cases and in my experience a lot faster than Android Device Manager or other apps like Cerberus and Airdroid.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- On Tasker, I have used Taskers own variables but also created my own variables to be created/changed on certain triggers.
For example, when the lx level ( light sensor ) gets low, it will set a variable to "false" as boolean, meaning there is not enough light == it is dark.
- Next I use this variable in my HTTP POST Request URL to a very simple PHP script on my website I wrote..
The HTTP POST Request URL will post to my PHP Script.
My PHP script grabs the URL, strips certain parts of it, turns it into PHP variables and then sends it to my MySQL database ( all on my own hosting).
- I again use the wonderful Tasker to do all of this this every 2 seconds.
You can get (almost) real-time information about your phone if it's set to be updated every 1 second.
This will not be very heavy on the database so it's possible.
- I then made another webpage containing another simple PHP script that grabs all the variables ( those we saved in previous steps) from my Database and echo's (shows) it on the screen.
This is the very same page you see on the screenshot, This is the Control Panel.
In the last step, all we have to do is visit the webpage on my website.
It will show the control panel as seen in the screenshot. You will also be able to control your phone from here.
I am making a simple login function where users can login.
this means a single database can hold more than 1 user if you wish to.
This will also protect others to see/control your phone from the web as they will need login credentials.
My script will then grab the corresponding variables of your phone when you login, using your ID and checking it on my database.
I know this may sound complicated for a lot of you who think that this is too much work, but I am planning to finish this and make it a some kind of a Open-Source thing available to every android and (rooted) tasker user.
All you need is:
- My Tasker project files ( all you need to do is import it to your own Android )
- Your own webhosting with MySQL database and PHP.
There are TONS of FREE online webhosting that will offer exact this. I'd love to post all the links here, but i'm not sure if it will be seen as advertising, so let me know.
- My PHP script(s), all you need to is simply upload it to your own website.
- My MySQL database configuration file - After importing this single file, the whole database will be created automatically on your website. ( using MySQL on your hosting )
After that, and when my Login function is complete, you could create an account for your self and/or others where they can login from anywhere in the world, on any browser or device and check their phone status and control their phone in Real-Time.
Sicariux said:
Greetings everyone,
i63.tinypic.com/20jsimh.png
What you see above is a "Control Panel" for my own Galaxy S7 Edge. I host this on my own website.
This means it can be seen and accessed from anywhere in the world, on any browser and/or device.
For privacy and security, I will implement a login system in the near future.
It has a couple of neat features, but since they are written in Dutch I will translate them to English:
Information:
Check battery level/percentage and check if your phone is being charged or not
Warns the user from the control panel if the battery is low.
Warns the user from the control panel to pull out the plug out of charging when it is fully charged
Check if your phone is in a light or dark place. I have optimized the light sensor as best as I could, The results are pretty accurate
Clipboard of your current copied content on your phone
Shows the phone model and the date and time of the last update sent from your phone
Check if Bluetooth is enabled or not
Check if Wifi is enabled or not
Show the current WiFi name, Wifi Speed, Wifi Channel & Wifi Signal Strength
Show the current Data Carrier / Mobile Signal strength (Weak, Normal, Strong)
Shows the current Call Volume percentage
Shows the current Media Volume percentage
Check if the screen of the phone is turned on or off
Check if GPS is enabled or not ( There is also a Live Google Maps on the right side, showing where the phone is right now )
Checks if the phone in call / calling / or getting called. ( in other words, it shows the user is busy with a phone conversation )
if the user is browsing on the internet on the phone or not. ( It will check if a browser is open, needs more adjustments for more accurate readings )
I am surprised at the speed of the operations.
It takes a total of 3 to 4 seconds after clicking on "take a picture" button to take a picture from the front-camera and Upload it to my google drive.
It also removes the picture from my phone after it has been uploaded. WIth combination of SMS control this can be a great anti-theft option.
The "Record Audio" function works great too. after clicking on it on the control panel, it starts recording audio, waits 10 seconds ( records for 10 seconds ), stops recording audio and then uploads it to a special folder in my Google Drive.
The "Send SMS" function is very fast. after clicking on it, it will take about 1.5 seconds to send the SMS from your phone.
For now, the number to send the SMS to is hardcoded, but I will make it a variable so that it will be possible to type in the number on your web control panel and send the SMS to the number from your browser.
The "LOCK your phone" function immediately lock your phone remotely, even when your screen is turned off. You can unlock it with the code that has been set up in the Tasker Event.
Clicking on the Wifi, Bluetooth & GPS icon will toggle them( on / off )
Clicking on the Phone (screen) Icon, Will toggle the phone screen ( turns it on and off )
Clicking on the Clipboard icon will copy all the content to your own clipboard.
Not only the text but the icons also change dynamically.
Grey icons represent a false variable (turned off / dark / not in call & etc ) and the blue icons represent the true variables.
For example, in the screenshot above, Bluetooth is turned off and wifi is turned on.
When the battery gets at 15% or less, the icon will turn red and green when it's fully charged (100%) and the user will get an alert box warning with a notification sound straight from the browser about the low battery / full charge . ( Sound and notification can be turned off if you wish).
I have wrote a script with AJAX (Asynchronous JavasScript and XML) to do all of this in Real-time and without page-reloads. AJAX refreshes the page information every second (or whatever the user wants) without reloading the page.
The controls in this control panel are in many cases and in my experience a lot faster than Android Device Manager or other apps like Cerberus and Airdroid.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- On Tasker, I have used Taskers own variables but also created my own variables to be created/changed on certain triggers.
For example, when the lx level ( light sensor ) gets low, it will set a variable to "false" as boolean, meaning there is not enough light == it is dark.
- Next I use this variable in my HTTP POST Request URL to a very simple PHP script on my website I wrote..
The HTTP POST Request URL will post to my PHP Script.
My PHP script grabs the URL, strips certain parts of it, turns it into PHP variables and then sends it to my MySQL database ( all on my own hosting).
- I again use the wonderful Tasker to do all of this this every 2 seconds.
You can get (almost) real-time information about your phone if it's set to be updated every 1 second.
This will not be very heavy on the database so it's possible.
- I then made another webpage containing another simple PHP script that grabs all the variables ( those we saved in previous steps) from my Database and echo's (shows) it on the screen.
This is the very same page you see on the screenshot, This is the Control Panel.
In the last step, all we have to do is visit the webpage on my website.
It will show the control panel as seen in the screenshot. You will also be able to control your phone from here.
I am making a simple login function where users can login.
this means a single database can hold more than 1 user if you wish to.
This will also protect others to see/control your phone from the web as they will need login credentials.
My script will then grab the corresponding variables of your phone when you login, using your ID and checking it on my database.
I know this may sound complicated for a lot of you who think that this is too much work, but I am planning to finish this and make it a some kind of a Open-Source thing available to every android and (rooted) tasker user.
All you need is:
- My Tasker project files ( all you need to do is import it to your own Android )
- Your own webhosting with MySQL database and PHP.
There are TONS of FREE online webhosting that will offer exact this. I'd love to post all the links here, but i'm not sure if it will be seen as advertising, so let me know.
- My PHP script(s), all you need to is simply upload it to your own website.
- My MySQL database configuration file - After importing this single file, the whole database will be created automatically on your website. ( using MySQL on your hosting )
After that, and when my Login function is complete, you could create an account for your self and/or others where they can login from anywhere in the world, on any browser or device and check their phone status and control their phone in Real-Time.
Click to expand...
Click to collapse
It looks like a great project.
Checks if the user is browsing on the internet on the phone or not. ( It will check if a browser is open, needs more adjustments for more accurate readings )
Click to expand...
Click to collapse
What about checking the network traffic to know whether the user is browsing or not?
I know this may sound complicated for a lot of you who think that this is too much work, but I am planning to finish this and make it a some kind of a Open-Source thing available to every android and (rooted) tasker user.
Click to expand...
Click to collapse
Even Open Source? That rocks.
XDA's Tasker subforum isn't that popular. You might wanna post your project on reddit too, where the Tasker community is way bigger and more popular:
https://www.reddit.com/r/tasker/. Let us know if you'll post it there too.
I'm looking forward for this project. Personally, I don't think I would use this as I don't think I really need it (although it doesn't hurt to have an anti-theft), but I'd like to see how it is done, if you're gonna make it Open Source.
Good luck!
Hi and thanks for your reply!
What about checking the network traffic to know whether the user is browsing or not?
Click to expand...
Click to collapse
Do you mean any random network traffic? in that case, a simple incoming whatsapp message could trigger the browser variable and set it to "true".
I will try reddit ... I have tried posting it in the official Tasker forums, but the my post is still awaiting moderator approval after a long time.
Since i've posted this thread, I've created new functions already like video recording (microphone audio included) the phone screen for 10 seconds and upload it to google drive.
I haven't seen this option on any other anti-theft yet. In a case of emergency, you could literally watch the thief do things on your phone and also hear him talking.
Since it's going be to open-source, it's highly customizable. You could change the icons, add new functions, remove functions , change the styling to your own wishes and improve the "web app" overall.
For those interested, Since the first post, I've added more options and starts looking good
https://youtu.be/T9aKmLTujik
For rooted users, you could make an add-on app that the user puts in the /system partition and, in case of factory reset, installs Tasker and restores it's data.
That way, the user has a chance of finding their phone even if the thief performs a factory/hard reset.
EDIT: Are your files available? I can't seem to find them.
Vagelis1608 said:
For rooted users, you could make an add-on app that the user puts in the /system partition and, in case of factory reset, installs Tasker and restores it's data.
That way, the user has a chance of finding their phone even if the thief performs a factory/hard reset.
EDIT: Are your files available? I can't seem to find them.
Click to expand...
Click to collapse
With the new Android versions, this is not a reliable thing anymore. This is the same reason Cerberus App stopped offering a special APK that could be installed in the /system by flashing it.
Also, it would be very difficult to have an add-on app install Tasker, AutoRemote, FolderSync and other plugins it needs automatically and configure them too.
I haven't made my files available yet. I am still perfecting it and awaiting community tips and input to expand the app more before releasing the source-files.

[HOW TO] Common Geolocation Notification Profiles

Let Tasker make you more efficient with your routine activities using Common Geolocation Notification Profiles
Features Include:
Easy access to relevant tasks when you most need them
Minimally intrusive persistent Notification
Themed Notifications for similar-type geolocations
Specific Tasker tasks for similar-type geolocations
Easily scalable for similar-type geolocations
Project Link W/ Setup:
Common Geolocation Notification Profiles
Enjoy!
Do you feel that using autolocation and geofences is battery friendly? I tend to only use "cell near" contexts and tons of terribly designed if statements " if a weekday AND TIME between 01.00 AND 04.00" etc
Do you notice a drain at all?
loogielv said:
Do you feel that using autolocation and geofences is battery friendly? I tend to only use "cell near" contexts and tons of terribly designed if statements " if a weekday AND TIME between 01.00 AND 04.00" etc
Do you notice a drain at all?
Click to expand...
Click to collapse
a small side question if you don't mind, could you please tell me what you use those for? maybe there are other alternative to cell near - personally I don't like/trust the geo context.
I use "cell near" contexts to determine my geolocation, and then if i really need to pinpoint my location I'll add two or three more contexts to that profile, such as "wifi near" or "location" but i only willl use taskers built in location because Tasker is designed to check the lowest battery consuming context first, and never check the others (more battery consuming) until that first is active.
So Tasker will only check cell near until cell near becomes active then it will check "my location"
I use this to determine when I'm home, or when I'm at work.
I never allow contexts that consistently poll and toll my battery. For instance the app context pulls your system every two seconds to see if that app is open and I will not allow that. I also do not allow "wait actions" in my tasks as nothing will suck your battery faster than setting something to wait 3 minutes (or 30 seconds even) before continuing with the task. I am happy to say that I can have as many as two hundred profiles enabled and waiting without noticing any sort of impact on my battery
Edit: one more thing if I must have a very precise battery sucker profile such as GPS or perhaps a plug-in that was not written by the strongest of coders I will pragmatically enable a disabled that profile with other profiles to make sure of the most minimal impact possible
very intense! :good:
for home detection, I use a 4-times-per-hour poll for Wi-Fi, I think it does not have any noticeable effect.
as for wait, I totally agree, a long wait do immensely affect the battery, so I just use mostly some seconds wait.
loogielv said:
Do you feel that using autolocation and geofences is battery friendly?
Click to expand...
Click to collapse
Do you notice a drain at all?[/QUOTE]
AutoLocation has been very battery friendly to me. I've used its Geofence monitoring for years now and have not noticed any adverse impacts on my battery life. Hope that helps!
loogielv said:
I tend to only use "cell near" contexts and tons of terribly designed if statements " if a weekday AND TIME between 01.00 AND 04.00" etc
Click to expand...
Click to collapse
I bet those can get very complicated haha.
Did you try out the project by chance? if so, did you happen to add any Tasks to the Profiles, and what were they? ...just curious! Thanks!

[GUIDE] Device Settings Menu Guide, Tips & Discussions | Part I - Connections

Device Settings Menu Guide, Tips & Discussions
Part 1 - Connections​
If you're new to this series or want to see the index, please read Post #2 first.​
The post has been updated as per the settings menu in latest Pie update.[/CENTER]
Wifi
Click on any network:
View supported Network speed, allocated IP address, gateway IP.
Toggle 'Auto Reconnect' to allow/disallow device to connect automatically to the network if it's in range.
Hold on any network > Manage network settings > Advanced > Set Static IP and DNS; Set Proxy;
Wifi Direct: Turn on Wifi Direct on a nearby device as well to transfer files wirelessly and fastly (speed up to gateway supported speed).
Menu > Advanced:
Turn on Wi-Fi Automatically: Your device will automatically enable Wi-Fi where you use it frequently. For example, you can disable your WiFi when you go out and you won't need to enable it again when you get back home. Tasker handles this job for me (try IFTTT for simpler setup).
Wi-Fi power saving mode: (On Pie, hop to developer mode) Analyzes your usage pattern and accordingly toggles WiFi. For example, if you get WhatsApp messages every 30 minutes on an average, the device learns about this traffic pattern and can toggle WiFi accordingly to fetch notifications every 30 minutes or whatsoever period is calculated. I keep this disabled as my usage pattern, like most of you, is dynamic. Better use App Sleep or Hibernation Apps like Greenify to save battery. Learn more about this mode here.
Wi-Fi control history: View apps that have toggled Wi-Fi recently. You can figure out if there's any culprit app that is toggling your Wi-Fi frequently when you have explicitly turned it off/on.
Hotspot 2.0: Automatically connects to APs that support Hotspot 2.0 or 802.11u. Network providers are themselves upgrading existing WiFi in public areas like airports and encryption is a must for Hotspot 2.0 so you can trust and rely on it while you don't have to manually guess the right network. Learn more about Hotspot 2.0 here.
WPS push button; WPS PIN Entry: (Pie doesn't support WPS but Google says it's coming back, Read here) Connect the device to WiFi by pushing WPS button on the router or entering WPS PIN in case these are enabled on the router. Learn about WPS here.
Install network certificates: Normally not needed. Some organization would need you to install certificates to access their domains. Same as what you do on PC to install certificates.
View device's MAC address and allocated IPv6/IPv4. Learn about MAC and IPs here.
Bluetooth
When the Bluetooth is ON, you can STOP/SCAN for nearby devices manually. Keep BT on for playing with following settings.
Menu > Advanced:
Dual Audio: Enables your device to connect to 2 different audio devices and play the same audio on both of them. Samsung explains this here.
Media volume sync: In case the connected audio device supports this, you can change the player's volume by your device's volume rockers by enabling this i.e. you don't have to manually raise the volume to the fullest on both your device and the connected player to get the highest volume possible for your house party.
Ringtone sync: Suggest usage?
Bluetooth control history: Similar as 'WiFi control history' above.
Phone visibility: (Moved to Separate section after Bluetooth in Pie, please tell if it works for BT as well) Allow devices (with Samsung Connect) to find your device for connection. You can disable it unless you live in a Smart Home or transfer files from other devices more often. Learn more about this mode here.
NFC and payment
It's turned ON by default on a new phone so do turn it OFF first. Samsung Pay will turn that ON if needed. The best thing about Samsung's flagship - Samsung Pay uses both NFC and MST (no other brand can do this) for payments. In case you don't know about MST (patented by LoopPay), must read here. MST works everywhere so I've keep NFC disabled.
Android Beam: Allows you to share stuff when you tap your phone with some other-phone-with-already-enabled-NFC.
Tap and pay: Select the default app for Payments and Others. Your default app will open up when you, for instance, tap your phone on an NFC-enabled POS (of course you need NFC to remain ON beforehand). Change 'If open app supports Tap and Pay' to 'Use open app instead of Samsung Pay' in case you want the App's own NFC payment feature, for example, in ICICI's Pockets.
Default NFC Method: By default and normally needed, 'Auto select'. In case you are the curious breed, learn about the different options here.
Flight Mode
Disables your operator's network. Since enabling this will also disable WiFi and Bluetooth altogether, you can turn back these two on without toggling flight mode.
Mobile networks
Data roaming: Enable it if your carrier doesn't charge you for roaming or you're rich enough.
VoLTE calls Primary: You'll see this in case your carrier supports VoLTE calling. #JioWaale
Network mode: By default, 'auto connect'. You can play with the options in case you're facing network mode changing issues or want to save battery (put to 2G only).
Access Point Names: I recommend you to request or configure your operator's settings for the first time even if it had been automatically fetched.
Data usage
Data saver: Formerly known as 'Restrict background data'. Your background apps will stop using network data i.e. you'll receive WhatsApp notifications only when you open the app again. You can also whitelist apps in 'Allow app while Data saver on'. This feature can help a lot in saving battery or making you check the phone less when you're hanging out with your girl. Me no girl so no enable!
Mobile data usage; Billing cycle and data warning: Do check this in a while to review the apps that uses most of your mobile data (maybe you don't need those apps that much on mobile data); Change your operator billing cycle, set data warning and enable data limit in case your operator doesn't give you free GBs.
Wi-Fi data usage; Restrict networks: Like mobile data, you can also review your Wi-Fi usage. Do review it once in a while to identify data-hungry apps that can affect battery and CPU as well; 'Restrict networks' (not available in Pie) helps you define your WiFi networks as 'metered'. It can be useful in a situation where a WiFi network you use is in fact a hotspot running on a device that uses mobile data. You can now restrict apps to use background data as described before in 'Data Saver'.
SIM card manager
Select Icon, Name and Network mode (described above) for the corresponding 'SIM slot' (not the SIM). Select preferred slot for calls, messaging and data. Learn about Smart Dual SIM here.
Mobile Hotspot and Tethering
Mobile Hotspot:
Wi-Fi sharing: In addition to mobile data, you can also share your Wi-Fi. This can be helpful in case you don't want to reveal your network or its credentials or don't know about them.
Menu > Allowed Devices: Enter MAC addresses of clients you want only to connect to your hotspot. Same as MAC filtering in routers.
Menu > Configure Mobile Hotspot; Timeout: Enable 'Hide my device' to stop exposing your SSID. Use 'WPA2 PSK' (Learn about wireless encryption here). 'Power saving mode' is similar to PMS in WiFi Advanced. Keep PMF on by default and change in case client doesn't support; Keep timeout low so that hotspot turns itself OFF earlier in case there's no client or change to 'Never Timeout' if you are going to need it for some time.
Bluetooth tethering; USB tethering: Learn about BT/USB tethering here.
More connection settings
Nearby device scanning: Although it uses Bluetooth Low Energy, I don't live in a Smart Home so have it disabled. If you enable it, you get notifications for nearby devices like TVs that support connections through your device (will annoy you at airports).
Printing: Do download Google Cloud Print and any other printing plugin required by your or your organization's printer.
MirrorLink: Great feature but I don't own a car. Learn more here.
Download Booster: Uses both WiFi and LTE at the same time to download apps over 30MB from Play Store and Galaxy Apps. In case you want that app as soon as possible.
VPN: Configure your VPNs here in case you have. I use Psiphon. You can also manually configure profiles as you do on PC.
Ethernet: Yes, you can use wired connection on your device too. Discussions here.
Private DNS: Pie supports DNS over HTTP/TCP and I recommend reading about this here. I use 1dot1dot1dot1.cloudflare-dns.com.
Series - Full Menu Guide Explained
Series - Device Settings Menu Guide​
Hey XDA! I just got free from the initial setup of my Galaxy Note9. I don't know how many of you do this but I'm one of a kind that gives a considerable amount of time to explore every setting, feature and every single option whenever I get a new device or even when I factory reset the existing one. It's been years since I have started with this curiosity and I have never found an 'all-in-one' menu guide to explain each and every option in the device. Yes, you could also simply google the option you want to know about but how about compiling all of them in one guide? I don't know if this experiment would work or not but here's I am starting with this. I have spent the past three weeks taking out time whenever I could to compile this guide.
There are a couple of reasons I had decided upon to start with this series. Firstly, I want to help newbies (or even experienced) out there to explore and know about every feature or option your device could offer. I have seen many duplicate threads that are created every day to query fellow users even about an individual but unfamiliar option in the settings. I intend to do my bit to clear this clutter and help potential askers to get answers beforehand. Secondly, this guide could serve as a manual in case you want to find or get briefed about an option. You could then simply 'Find in a page' over the threads or simply use XDA's 'search in the thread' option to save your time. Thirdly, since I've broken the settings into different threads, this could help users engage and discuss over a particular device's super-menu and spread their knowledge, come up with new ideas and explore more of their devices. Fourthly, this series is not constrained to Note9 only. The settings on every Android device out there is similar and you would be able to find any common to your device settings here as well. Fifthly, since I have provided links and sources to some options, this can serve as directory map as well. Sixthly, this guide consists of tips for many options that you won't probably find normally.
This guide is intended and recommended to be read by anyone at least once. If you're reading a thread for the first, I recommend you to open up the corresponding settings in your phone and read the settings description in case there is. All the threads are arranged in the same order as the settings would come up. You could then simply read out my description of the same, my selected configuration and hyperlinks to some articles or videos in case you're the curious breed. This guide is strongly recommended after a fresh start. I want you all to give some time to explore each and every option your device can offer.
Hope this experiment lives up to the marks. Both criticism and appreciation are greatly needed and appreciated. Please comment.
I've tried to explain each option you could find by going deep into any setting. No matter whatever links I have provided, I will feel grateful if you want me to explain any feature more than I have done already. Please ask questions related to any settings. Do provide me suggestions and your take on my configuration. Please provide me with more guides and articles for a particular feature. I want to have the precious contribution of XDA members in this guide. Discussion over any feature, setting, your configuration, did-you-knows and anything else is greatly appreciated. This is a newbie-friendly place so don't hesitate to ask questions - besides the fellow XDA members, I'm always here for you.
Regards,
Paras Lehana
Index
Part 1 - Connections
Part 2 - Sounds and vibration, Notifications, Wallpaper and themes
Part 3 - Display, Lock screen, Biometrics and security
Part 4 - Advanced features, Device maintenance, Apps
Part 5 - Cloud and accounts, Google, Accessibility, General management, Software update, User manual, About phone, Developer options
​
-- Reserved for FAQs --
Why are you posting this?
There's a very good "USER MANUAL" on the "Samsung"-site available:
User Manual Samsung Galaxy Note9
henklbr said:
Why are you posting this?
There's a very good "USER MANUAL" on the "Samsung"-site available:
User Manual Samsung Galaxy Note9
Click to expand...
Click to collapse
You have commented the same query on each of my parts. I have already answered you here where the similar discussion is already going on. Let's discuss there and keep this thread clean. Also, the 'why am I posting this' is already described in the Introductory Post.
Is there a way to toggle the "WiFi networks available" notification off?. It seems Samsung's removed this option from the advanced WiFi menu as well as grayed it out from the advanced notifications panel. Thanks.
astrodemoniac said:
Is there a way to toggle the "WiFi networks available" notification off?. It seems Samsung's removed this option from the advanced WiFi menu as well as grayed it out from the advanced notifications panel. Thanks.
Click to expand...
Click to collapse
I tried searching for this on the internet and found that a lot of users are annoyed by this. Did you try disabling Wi-Fi scanning in Connections > Location > Improve accuracy ? Do you even get notifications when your Wi-Fi is turned off? Next time you get this notification, long tap on the notification to know which system package/app is firing this notification. Try disabling it from there. And, can you post screenshot of "advanced notifications panel" where you're seeing grayed out option?
Can the settings menu be sorted alphabetically? in either lineage or stock roms
Problem with 192.168.100.1 address
Everytime I type in the 192.168.100.1 address, I receive a message "Internet Explorer Cannot Display
Webpage". I have tried this several times and it doesn't connect me to the website.
HELP

Samsung services dialling home to China (360.cn and 360safe.com) after Pie upgrade

Having ran NetGuard in logging mode for a few days now I've noticed that many of Samsung's in-built services are contacting web services associated at multiple DNS subdomains under:
- *.360.cn
- *.cloud.360safe.com
A lot of them on unsecured HTTP port 80 (some go via HTTPS port 443).
Services I've observed this behaviour so far are:
- Samsung ApexService
- ANT+ HAL Service
- Application installer (com.sec.android.preloadinstaller)
- Assistant Menu
- AirCommandManager (com.samsung.android.aircommandmanager)
- Plus too many other default services to list (most of which cannot be disabled)
Phone's running on stock unbranded SM-N960F build number PPR1.180610.011.N960FXXU2CSA2.
I've scanned the phone using bundled Device Care's McAfee security scan with no findings.
Has anyone else observed this behaviour?
sengork said:
Having ran NetGuard in logging mode for a few days now I've noticed that many of Samsung's in-built services are contacting web services associated at multiple DNS subdomains under:
- *.360.cn
- *.cloud.360safe.com
A lot of them on unsecured HTTP port 80 (some go via HTTPS port 443).
Services I've observed this behaviour so far are:
- Samsung ApexService
- ANT+ HAL Service
- Application installer (com.sec.android.preloadinstaller)
- Assistant Menu
- AirCommandManager (com.samsung.android.aircommandmanager)
- Plus too many other default services to list (most of which cannot be disabled)
Phone's running on stock unbranded SM-N960F build number PPR1.180610.011.N960FXXU2CSA2.
I've scanned the phone using bundled Device Care's McAfee security scan with no findings.
Has anyone else observed this behaviour?
Click to expand...
Click to collapse
I haven't looked at this as closely as you have,but,I'm guessing it's all tied-in from the Device Maintenance section of the phone.
The name of the company Samsung is currently in bed with is QIHOO:
https://en.wikipedia.org/wiki/Qihoo_360
https://seekingalpha.com/article/4165136-cheetah-mobile-lost-samsung-relevant-risks
Remember/heard of Cheetah Mobile (of Clean Master infamy) ?
https://www.prnewswire.com/news-rel...mobile-security-and-innovation-300043298.html
Well,that's who used to be in partnership w/Samsung & the Device Maintenance aka built-in Clean Master to most,if not all Samsung mobile products.
Fast-Forward to present day & we still have the crapware on our phones,likely scraping info & selling it to anyone interested.
Now,it's just with another company,presumably one with friendlier terms for Samsung.
As you've probably noticed,you can't fully disengage/disable/deny all permissions here,less root (or ADB disabling/package disabler apps).
At least you have a phone that's rootable & can cruise the ROM scene for one that leaves this crap off the phone.
If root isn't an option:
Set up your phone & apps,fine-tune as you like for battery optimization on a per app basis/permissions/etc....
Then,either via ADB or a package disabler,disable the apps responsible for the crapware,especially the ones related to Device Maintenance.
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Follow the link in the OP to the S9/S9+ forum/thread,it gives a better idea of what each .apk actually is/ties into.
Here's the app I use to disable crapware/things I don't use:
https://play.google.com/store/apps/details?id=com.wakasoftware.appfreezer
As to which apps to disable,the S9/S9+ thread,while not an exact match,should give you info on what to disable to stop the phone from pinging the 360 mothership & hopefully,not having any ill effects on the apps you want to keep on-board.
If you want a better idea of how each app is interconnected throughout the phone,use these two apps to take a look:
https://play.google.com/store/apps/details?id=com.ubqsoft.sec01
SD Maid (Pro):
https://play.google.com/store/apps/details?id=eu.thedarken.sdm&hl=en_US
(See the App Control & file manager sections of SD Maid for detailed app info).
Anyhoo,back to curbing the nonsense:
Whichever method you use to disable,should you choose to do so,start with this one:
com.samsung.android.lool (Device Maintenance).
This will make the entire Device Maintenance section inaccessible as well.
That is why I suggest disabling vs outright uninstalling (which necessitates a factory reset to get it back).
You may need to access Device Maintenance for whatever reason from time to time,hence the recommendation for disabling vs uninstalling.
Continue monitoring for a day or so & see if the pinging to the Mothership subsides,or hopefully puts a full-stop to it.
Please keep us updated on what,if any actions you take w/the results. :good:
Excellent overview, it's quite an eye opener thanks for the info.
I've disabled and force-stopped "com.samsung.android.lool" (amongst other junkware) and so far NetGuard hasn't shown a single network log entry to any of the 360 domains. I've uninstalled all 4 Facebook packages. Continuing to monitor this closely. My thought is that I can re-enable "com.samsung.android.lool" from time to time whenever maintenance is needed and then disable it again. Even better Adhell3 might be useful for blocking "com.samsung.android.lool" network attempts whilst retaining it for device management purposes however I haven't tried this yet.
For reference, here is my current list of disabled packages:
Code:
package:com.monotype.android.font.rosemary
package:com.samsung.android.app.ledcoverdream
package:com.sec.android.widgetapp.samsungapps
package:com.samsung.android.app.galaxyfinder
package:com.samsung.svoice.sync
package:com.cnn.mobile.android.phone.edgepanel
package:com.samsung.android.easysetup
package:com.samsung.android.provider.stickerprovider
package:com.samsung.android.app.sbrowseredge
package:com.samsung.android.rubin.app
package:com.sec.android.cover.ledcover
package:com.samsung.faceservice
package:com.monotype.android.font.foundation
package:com.sec.android.widgetapp.easymodecontactswidget
package:com.samsung.android.app.settings.bixby
package:com.sec.android.app.billing
package:com.samsung.android.app.selfmotionpanoramaviewer
package:com.samsung.android.game.gamehome
package:com.samsung.daydream.customization
package:com.sec.enterprise.knox.attestation
package:com.samsung.systemui.bixby2
package:com.dsi.ant.service.socket
package:com.microsoft.skydrive
package:com.samsung.SMT
package:com.samsung.android.drivelink.stub
package:com.android.hotwordenrollment.xgoogle
package:com.samsung.android.sm.devicesecurity
package:com.dsi.ant.sample.acquirechannels
package:com.samsung.android.aircommandmanager
package:com.samsung.android.bixby.service
package:com.samsung.android.smartface
package:com.android.egg
package:com.samsung.android.emojiupdater
package:com.samsung.android.bixby.agent
package:com.android.printspooler
package:com.android.hotwordenrollment.okgoogle
package:com.samsung.android.hmt.vrsvc
package:com.samsung.storyservice
package:com.android.dreams.basic
package:com.android.bips
package:com.samsung.android.game.gametools
package:com.samsung.android.app.simplesharing
package:com.samsung.android.service.peoplestripe
package:com.samsung.android.da.daagent
package:com.dsi.ant.plugins.antplus
package:com.samsung.android.app.taskedge
package:com.google.android.webview
package:com.samsung.android.app.mirrorlink
package:com.dsi.ant.server
package:com.samsung.android.allshare.service.fileshare
package:com.samsung.android.universalswitch
package:com.sec.android.app.apex
package:flipboard.boxer.app
package:com.google.android.printservice.recommendation
package:com.monotype.android.font.chococooky
package:com.android.dreams.phototable
package:com.samsung.android.bixbyvision.framework
package:com.samsung.android.game.gos
package:com.android.wallpaper.livepicker
package:com.samsung.android.beaconmanager
package:com.sec.enterprise.mdm.services.simpin
package:com.samsung.android.stickercenter
package:com.samsung.android.bixby.wakeup
package:com.samsung.android.samsungpass
package:com.samsung.android.spayfw
package:com.linkedin.android
package:com.samsung.android.lool
package:com.samsung.android.knox.analytics.uploader
package:com.samsung.android.sm.policy
package:com.sec.android.emergencylauncher
package:com.samsung.android.visionintelligence
package:com.samsung.android.app.watchmanagerstub
package:com.samsung.android.svoiceime
package:com.samsung.android.mateagent
package:com.enhance.gameservice
package:com.google.vr.vrcore
package:com.hiya.star
package:com.sec.enterprise.knox.cloudmdm.smdms
package:com.samsung.android.app.appsedge
package:com.samsung.android.samsungpassautofill
package:com.monotype.android.font.cooljazz
package:com.samsung.android.allshare.service.mediashare
package:com.samsung.android.app.clipboardedge
package:com.samsung.android.app.motionpanoramaviewer
package:com.samsung.android.bio.face.service
package:com.samsung.android.bixby.agent.dummy
sengork said:
Excellent overview, it's quite an eye opener thanks for the info.
I've disabled and force-stopped "com.samsung.android.lool" (amongst other junkware) and so far NetGuard hasn't shown a single network log entry to any of the 360 domains. I've uninstalled all 4 Facebook packages. Continuing to monitor this closely. My thought is that I can re-enable "com.samsung.android.lool" from time to time whenever maintenance is needed and then disable it again. Even better Adhell3 might be useful for blocking "com.samsung.android.lool" network attempts whilst retaining it for device management purposes however I haven't tried this yet.
For reference, here is my current list of disabled packages:
Code:
package:com.monotype.android.font.rosemary
package:com.samsung.android.app.ledcoverdream
package:com.sec.android.widgetapp.samsungapps
package:com.samsung.android.app.galaxyfinder
package:com.samsung.svoice.sync
package:com.cnn.mobile.android.phone.edgepanel
package:com.samsung.android.easysetup
package:com.samsung.android.provider.stickerprovider
package:com.samsung.android.app.sbrowseredge
package:com.samsung.android.rubin.app
package:com.sec.android.cover.ledcover
package:com.samsung.faceservice
package:com.monotype.android.font.foundation
package:com.sec.android.widgetapp.easymodecontactswidget
package:com.samsung.android.app.settings.bixby
package:com.sec.android.app.billing
package:com.samsung.android.app.selfmotionpanoramaviewer
package:com.samsung.android.game.gamehome
package:com.samsung.daydream.customization
package:com.sec.enterprise.knox.attestation
package:com.samsung.systemui.bixby2
package:com.dsi.ant.service.socket
package:com.microsoft.skydrive
package:com.samsung.SMT
package:com.samsung.android.drivelink.stub
package:com.android.hotwordenrollment.xgoogle
package:com.samsung.android.sm.devicesecurity
package:com.dsi.ant.sample.acquirechannels
package:com.samsung.android.aircommandmanager
package:com.samsung.android.bixby.service
package:com.samsung.android.smartface
package:com.android.egg
package:com.samsung.android.emojiupdater
package:com.samsung.android.bixby.agent
package:com.android.printspooler
package:com.android.hotwordenrollment.okgoogle
package:com.samsung.android.hmt.vrsvc
package:com.samsung.storyservice
package:com.android.dreams.basic
package:com.android.bips
package:com.samsung.android.game.gametools
package:com.samsung.android.app.simplesharing
package:com.samsung.android.service.peoplestripe
package:com.samsung.android.da.daagent
package:com.dsi.ant.plugins.antplus
package:com.samsung.android.app.taskedge
package:com.google.android.webview
package:com.samsung.android.app.mirrorlink
package:com.dsi.ant.server
package:com.samsung.android.allshare.service.fileshare
package:com.samsung.android.universalswitch
package:com.sec.android.app.apex
package:flipboard.boxer.app
package:com.google.android.printservice.recommendation
package:com.monotype.android.font.chococooky
package:com.android.dreams.phototable
package:com.samsung.android.bixbyvision.framework
package:com.samsung.android.game.gos
package:com.android.wallpaper.livepicker
package:com.samsung.android.beaconmanager
package:com.sec.enterprise.mdm.services.simpin
package:com.samsung.android.stickercenter
package:com.samsung.android.bixby.wakeup
package:com.samsung.android.samsungpass
package:com.samsung.android.spayfw
package:com.linkedin.android
package:com.samsung.android.lool
package:com.samsung.android.knox.analytics.uploader
package:com.samsung.android.sm.policy
package:com.sec.android.emergencylauncher
package:com.samsung.android.visionintelligence
package:com.samsung.android.app.watchmanagerstub
package:com.samsung.android.svoiceime
package:com.samsung.android.mateagent
package:com.enhance.gameservice
package:com.google.vr.vrcore
package:com.hiya.star
package:com.sec.enterprise.knox.cloudmdm.smdms
package:com.samsung.android.app.appsedge
package:com.samsung.android.samsungpassautofill
package:com.monotype.android.font.cooljazz
package:com.samsung.android.allshare.service.mediashare
package:com.samsung.android.app.clipboardedge
package:com.samsung.android.app.motionpanoramaviewer
package:com.samsung.android.bio.face.service
package:com.samsung.android.bixby.agent.dummy
Click to expand...
Click to collapse
:good: THX for the update,much appreciated! :good:
I was gonna post this in a bit (just noticed it myself this afternoon,LOL) ,but,it looks like you have added the other two .apks to your disabled list:
https://forum.xda-developers.com/showpost.php?p=78103170&postcount=123
It'a a shame the mfgs aren't required to be more up-front & state ,in common use language where the print is larger than a gnat's ass, the exact nature of the .apks & even more control over the services installed on them.
KOLIOSIS said:
It'a a shame the mfgs aren't required to be more up-front & state ,in common use language where the print is larger than a gnat's ass, the exact nature of the .apks & even more control over the services installed on them.
Click to expand...
Click to collapse
The closest to a manufacturer application list I came across was:
- https://support.samsungknox.com/hc/en-us/articles/115015195728-Common-Criteria-Mode
- For example https://docs.samsungknox.com/CCMode/N960F_O.pdf
This seems to relate to computer security certification known as Common Criteria:
- https://en.wikipedia.org/wiki/Common_Criteria
So the dial home behaviour seems to have passed this security certification (or perhaps the network flows were not part of the certification process). We can only guess...
I've had to reenable the following items to get APK installs to function (either through Play Store or locally stored APKs):
Code:
com.samsung.android.sm.policy
com.samsung.android.sm.devicesecurity
https://forum.xda-developers.com/ga...val-thread-t3857508/post78744845#post78744845
Continuing to monitor with NetGuard. So far ~1hr I haven't seen the packets repeat.
sengork said:
I've had to reenable the following items to get APK installs to function (either through Play Store or locally stored APKs):
https://forum.xda-developers.com/ga...val-thread-t3857508/post78744845#post78744845
Continuing to monitor with NetGuard. So far ~1hr I haven't seen the packets repeat.
Click to expand...
Click to collapse
IIRC,something like this was mentioned in the S9/S9+ debloat thread.
I didn't mention it earlier as you hadn't reported any issues,but,glad you were able to figure it out/find the same info I'd stumbled upon.
Well after a day of usage I can say that battery life is poorer without "com.samsung.android.lool". I've enabled it again now and blocked its domains via Adhell 3:
Code:
360.cn
360safe.com
*.360.cn
*.360safe.com
Furthermore I have disabled its WiFi and Mobile network access in Adhell 3. However this block is bypassed whenever applications using Android's native VPN facility are switched on so its not absolutely fool proof. Similar blocking can be done using NetGuard itself as long as you keep it switched on and filtering continuously.
I'll keep an eye on which other domains it attempts to contact.
sengork said:
Well after a day of usage I can say that battery life is poorer without "com.samsung.android.lool". I've enabled it again now and blocked its domains via Adhell 3:
Code:
360.cn
360safe.com
*.360.cn
*.360safe.com
Furthermore I have disabled its WiFi and Mobile network access in Adhell 3. However this block is bypassed whenever applications using Android's native VPN facility are switched on so its not absolutely fool proof. Similar blocking can be done using NetGuard itself as long as you keep it switched on and filtering continuously.
I'll keep an eye on which other domains it attempts to contact.
Click to expand...
Click to collapse
How much of a difference in battery life are we talking about?
It felt to be about 20%. Is Pie without Device Maintenance expected to put applications to sleep? I am guessing sleep is the major factor here (opposed to cleaning up caches and other storage capacity functions of Device Maintenance app).
sengork said:
It felt to be about 20%. Is Pie without Device Maintenance expected to put applications to sleep? I am guessing sleep is the major factor here (opposed to cleaning up caches and other storage capacity functions of Device Maintenance app).
Click to expand...
Click to collapse
I would like to think so,hoping Device Maintenance isn't ingrained to the level where it breaks the native Doze feature in Android.
JMHO,Device Maintenance seems to be just like Clean Master,running on top of Android/counterproductive,putting a hat on a hat,so to speak,LOL.
I haven't had a Nexus device since the N6 & never had a Pixel,but,I'm pretty sure none of 'em have DM..................................
Whenever I decide to update to Pie,I'm going to continue as I am now:
Battery Optimize all apps that I don't rely on for auto-updating or push notifications & then disabling Device Maintenance.
If something starts acting up,only then do I re-enable DM,take a look at Battery Optimizing for whatever is affected & again,disabling DM.
Guessing you've just recently updated to Pie.......
If it were me,I'd continue to disable DM & give the new OS upgrade a week or so,see what your battery life looks like then.
Battery life loss could be due to some user-installed apps that aren't playing nice w/Pie & not due to DM being disabled.
You will find the logo or text "powered by 360" on storage screen in Samsung device management app.
KOLIOSIS said:
Battery Optimize all apps that I don't rely on for auto-updating or push notifications & then disabling Device Maintenance.
If something starts acting up,only then do I re-enable DM,take a look at Battery Optimizing for whatever is affected & again,disabling DM.
Click to expand...
Click to collapse
I have taken your advise a few weeks ago and have concluded that removing DM whilst manually optimising all individual apps has resulted in no battery loss (in fact it has probably improved but this is within a margin of error). Thanks for your guidance.
Unless you need to connect to a Chinese domain for whatever reason, just block *. cn for good and forever about it.
hello guys i have bought galaxy note 9 in China and there is not preinstalled google play store app...
can anyone tell me how to install safely ))?? thank you ...
hey thanks for your attention but i dont need to access i have vpn i know how to access i want to know how to install because it is not installed so do you have some ideas ?))) how to do it
sandro comaia said:
hey thanks for your attention but i dont need to access i have vpn i know how to access i want to know how to install because it is not installed so do you have some ideas ?))) how to do it
Click to expand...
Click to collapse
Just side-load this .apk & you should be good to go:
https://www.apkmirror.com/apk/googl...5-22-all-0-pr-254908059-android-apk-download/
Was original poster was the only one who had this issue?
Is this a samsung thing or all androids?
Can this be a security risk?
There was a link to the s9 bloatware thread but it doesn't work
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Says 404 not found for me
Nameduser6 said:
Was original poster was the only one who had this issue?
Is this a samsung thing or all androids?
Can this be a security risk?
There was a link to the s9 bloatware thread but it doesn't work
https://forum.xda-developers.com/ga...laxy-note-9-bloatware-removal-thread-t3857508
Says 404 not found for me
Click to expand...
Click to collapse
Should be only Samsung phones. Interestingly i haven't seen it dial home since my original post and up until i uninstalled the Device Care package. Samsung might have changed the domains the tool dials home to.
Sent from my SM-N960F using Tapatalk

Categories

Resources