[Xposted my thread from Note-5 general since it is a common issue]
Hello guys! It has been a long time since I have been trying to sort out my drain issues on my S6 Edge+ , a couple of days ago I finally figured out to use Wakelock Detector without root then it comes out that it was actually the maps keeping the phone awake via "NLPWakelock" through Android OS. I will cover out the process step by step to found out which app is causing the drain and why! We will need ABD, so we must have a computer.
1)First we are gonna need the app; "Wakelock Detector [Lite]" root users may use normal version too.
Play store link: https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector.noroot&hl=tr,
2) We should open USB Debugging option in developer settings. And connect our phone to computer via USB.
{
"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"
}
3) To check if we have adb installed, you can simply run command promt ( windows/run/cmd ) and write
Code:
adb devices
If the output is similar to the image below, it means you have ADB installed and if you have device entry you have your ADB device drivers installed too.
If ADB is not installed, please kindly check Snoop05's thread to use his perfect tool - 15 Seconds ADB installer ( Yes, 15 seconds, actually less )
4) Once you make sure you have your device entry after writing " adb devices" , we gonna need to write this command to give Wakelock Detector battery history permissions:
Code:
adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS
At this point we may see a popup dialog on our phone like this:
You need to allow it and preferably you can check always allow option.
5) That's it guys. Now we have Wakelock detector working!
Most of the important drains caused by CPU wakelocks and Kernel Wakelocks. With or without root, the things we can do to kernel wakelocks are limited, afaik. So lets come to CPU Wakelocks. What you should do is use your phone regularly a couple hours after you gave permissions to the app and run it. Then you will see which apps , and which wakelocks they have called both individually. After that you can pinpoint the issue with a google search! Hope it helps you guys. I fixed my drain, I was getting 3hours of SOT before now I have more than 4-4.5 hours through my daily usage.
Notes:
Here is an awesome guide about wakelocks by T.J. Bender , you can check your wakelock there too.
Please feel free to ask any questions or unclear points. Hope your phones deeper sleeps!
Up to date
Related
So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"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"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize
Hello, i am a beginning developer. And created this tool "Easy ADB". I know that there are many tools that have the same features, but i was bored. Also you need to now that my english is realy bad so ignore that or PM me if you can late it.
The features are:
Manage you applications
Explorere your device with "Device explorer"
The device explorer include's a fast textviewer
The program works also in CMW
Work with multiple devices
For the moment i have released a stable V0.2.1. For download got to the project page.
https://easyadbandroid.codeplex.com/
A screenshot.
{
"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"
}
The program at itself works realy feast think i. Also i don not lose it time to ask the apk pictures.
Requirements
A rooted adroid device
Busybox installed (if you use CM or a costum kernel it is already installed in most casses)
Netframework 4
If you have a bug, please go to the issue tracker.
https://easyadbandroid.codeplex.com/workitem/list/basic
How you can help! Just post all you idea's to add on the program.
If you device bricks because you deleted a system app. Don't worry just press help and follow the instructions.
Please tell me if you like my application, cheers!
gud luck with the project
Has nobody problems with the program? There are 16 dowloads on the day i released it here on XDA. (The other day's i can not see).
Anyway i have a question. How can i detect with a adb command of the device is rooted or busybox is installed. Problem is i have only a "X10 pro mini" with CM7. And can not try to install busybox because it is already pre-installed. Otherwise in the programfolder you have a script folder (for adb shell). If somebody has a script that install busybox, I would be very happy that someone can share that with me .
thomas15v said:
Has nobody problems with the program? There are 16 dowloads on the day i released it here on XDA. (The other day's i can not see).
Anyway i have a question. How can i detect with a adb command of the device is rooted or busybox is installed. Problem is i have only a "X10 pro mini" with CM7. And can not try to install busybox because it is already pre-installed. Otherwise in the programfolder you have a script folder (for adb shell). If somebody has a script that install busybox, I would be very happy that someone can share that with me .
Click to expand...
Click to collapse
I'm on the move so I can't give you a full answer yet. But one option to see if Busybox is installed is to try to pull it. If you can't, then it's not there.
Version 0.2.1 released and is stable. Press thanks if you liked it .
(please :/....)
Ok just uploaded a new version. I updated my phone to ICS and was wondered that my application is incompatible with it. Now it must work fine. Only problem i don't now of it still works on GB. Can sombody test it out for me.
No update for this software?
Info
+ Clean install of Windows 10
+ Motorola USB drivers installed
+ Installed the latest Motoactv firmware (MA 1.7.10 N8) and rooted
+ Installed TCX exporter since Motoactv site is unreliable/dying.
Boast
+ This device is still amazing. Its battery life on marathon mode actually lasted as I finished a marathon. There is no competitor out there that has 8GB storage for music, decent battery life and doesn't cost over $200, even the upcoming TomTom Spark.
Problems
- Motoactv doesn't charge when plugged into a wall charger. Will only charge using a USB port.
- Cannot make the device show up as a USB storage device so I can sync with Doubletwist
- Cannot sync with iTunes due to problems with Motocast, Nero/Motorola Media Link software
-- Despite updating to the latest Java 32 and 64 bit, I'm still greeted with this message:
{
"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"
}
Question
How can I enable usb storage on the fly without having to run the MotoACTV Root Tool and "stop adb and enable USB"?
Why does the Motoactv not charge when using a wall charger?
Bump.
adb shell am start -a com.android.settings.APPLICATION_DEVELOPMENT_SETTINGS: Gives option on Actv screen to disable USB Debugging (turn off ADB permanently). Note, you can only access this option WITH ADB, so once you turn it off, you can only gain ADB back by reflashing the boot image (generally the 1.6.0 boot image).
Found this from: http://motoactv.wikispaces.com/useful_adb_fastboot_command
Worked great on my motoactv and my friends. If I remember correctly you want to make sure the screen not asleep on the motoactv when you run the command. Hope this helps! Still loving my motoactv.
Quintman said:
adb shell am start -a com.android.settings.APPLICATION_DEVELOPMENT_SETTINGS
Click to expand...
Click to collapse
That worked.
Still loving my motoactv.
Click to expand...
Click to collapse
Amen.
Hey guys,
I'm posting here as a last resort before a factory reset.
By the way, let me first say that I'm sorry to post this here, as I know it's SO stupid, what's happening.
I had the same lock pattern for 2 years now, never had a problem.
Last week, it just fell out my mind completely. I've been trying for 4 days straight to remember it.
It's quite a complicated one, with the pattern tracing deactivated so I can't remember the shape and my thumb tried with its motor memory but to no avail :x
The thing is, I extensively use the notepad stock app (Samsung Notes ? Android Notes ?) and I have a **** TON of info I REALLY don't want to lose. And it's not on the SD card, ofc.
I don't care much about the rest, to be honest.
Fun fact, I only synced contacts via the android sync function.
So how can I either remove the lock pattern or access my phone files with an explorer on my computer (I guess I can find a memory file for the notepad somewhere), knowing that :
- Not rooted
- USB debugging not activated
- Not registered with Samsung account
- Android version is the latest available in France for an SM-A510F as I do all updates
I can provide as much as I can to prove my ownership of the phone if needed.
Thank you for reading and maybe for helping.
You have absolutely every right to laugh to my (dumb) face.
EDIT :
Just tried something else. Booted in recovery to try an ADB command.
Since Windows didn't recognize the phone in recovery mode, I selected the option "Load package with ADB" or something like that.
Now the phone was listed in devices on ADB and I tried this : adb shell rm /data/system/gesture.key
Result : error.
Great.
So since the phone was unresponsive to any button, I waited and there was a timeout on the package load.
BUT NOW...
I have a blue screen that says "Error!" and it's completely unresponsive.
GREAT.
I'm off to work, read you soon.
XOXO
{
"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"
}
<Mod Edit>
Thread closed by OP request.
Warning: I will not be responsible for any wrong doings that might occur with following this guide, this is my first Guide here, expect some errors. Any damage to any device that might happen by following then steps is responsiblility of particular user not mine. I recommend that you don't do anything you don't understand.
Disclaimer: I do not personally own a RedMi Note 5A device, I helped a friend to clean up some space on their device, as a part of which, I uninstalled some of the OEM apps that were not used by them.
If you use any of the apps, you should not uninstall them.
Difficultly level: Easy to medium.
Experience required: You should be familiar with ADB, Windows BatchScript (optional), Android file system.
As superuser access is not used in this process, root is not required, you can try this on Non-Rooted devices
Tested on : Redmi Note 5A, Android-8.x, MiUi v10.x
Should work on all device prior to Android 9.
Requirements: ADB installed on PC, supposedly windows. A proper USB cable, an Android Phone.
I'll assume you have already setup ADB via Android-SDK or minimalistic ADB tools, and not go into that.
1. Enable developer mode, USB debugging on phone,
2. Connect device to PC (in a USB 2.0 port, preferably).
3. start adb, "adb start-server"
4. Make sure device is available.
Now there is batch file in attachment for uninstalling and a text file with the list of apps I uninstalled. You can either replace the package name with those you want to remove or you can copy the command, make it a single line command and replace the package name directly into the prompt as I did
{
"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"
}
Additional details are given in the attachment zip files, see below. You replace the package name with the app you want to uninstall and run the script/command in command line.
Same thing can in theory be achieved if "pm" command is readable by a third party terminal emulator apps like Termux, note that, on new devices, "/" is not readable, "/system/bin/pm" might be readable depending on ROM, thus ADB way should always work, but calling "pm" from on device apps is also possible.
Expected results: single word "success" on a new line.
If it says "device offline", restart adb with "adb kill-server" followed by "adb start-server" , if that doesn't work restart the smartphone, if that doesn't work check that USB port is v2.0( search on Google how to determine ), if that doesn't work, your cable would be faulty or some connection error.
Reserved.