Hello everybody,
I have xiaomi mi max 32gb -Multirom 8.4.26
I make all my apps battery optimized except these apps (Greenify+amplify+powernap+Launcher+Appops+Magisk+Xposed).
{
"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"
}
But after rebooting my mobile,apps returns non-optimized.So I need to make all my apps optimized after every reboot. This task is tiring and wastes my time.
My Question:Can you help me batch optimize all apps after every reboot,please?By using tasker or adb command or mod or anything
Please help me
I found a task in the internet and edited it:
https://www.mediafire.com/file/ytoj29yxl2c0079/Optimization.tsk.xml
That task should do the following:
1-open "Battery optimization" screen.I can find it in greenify only as it is hidden in my rom.
2-unoptimize predefined list of apps "my root apps"
3- optimize all other system and user apps
But I found that the task doesnot make all other apps optimized as I want
Please help me
I can not guarantee this method works on all devices. It works well in Tasker on my nexus running 8.1 and previously on 7.1
You need the package name of the app you want to affect.
<Adds Play Store Tasker to battery optimization>
A1: Run Shell [
Command: dumpsys deviceidle whitelist +net.dinglisch.android.taskerm
Timeout (Seconds): 0
Use Root: On
Store Output In:
Store Errors In:
Store Result In:
]
<Removes Play Store Tasker from battery optimization>
A2: [X] Run Shell [
Command: dumpsys deviceidle whitelist -net.dinglisch.android.taskerm
Timeout (Seconds): 0
Use Root: On
Store Output In:
Store Errors In:
Store Result In:
]
<add "dumpsys deviceidle" info to a variable>
A3: Run Shell [
Command: dumpsys deviceidle
Timeout (Seconds): 0
Use Root: On
Store Output In: %DUMP
Store Errors In:
Store Result In:
]
<display contents of dumpsys variable>
A4: Popup [
Title: Dump Sys
Text: %DUMP
Background Image:
Layout: Popup
Timeout (Seconds): 134
Show Over Keyguard: On
]
In the dumpsys information, look for whitelist system/user apps. Anything listed there should be battery optimized.
Use A1 to battery optimize or A2 to remove from optimization.
BTW, I would have responded shortly after you posted originally but I _hate_ these Q/A formatted posts. I'm forced to use a browser to respond and on a phone that is a PITA.
Thank you sir very much for your reply
I used this command before in terminal with su:
(dumpsys deviceidle whitelist -package name)
But it works only with user apps ,It doesn`t make any change for system apps
please help me to find another working command that works with system apps
You are using root, right?
It works fine for me on system and user apps so it maybe a device limitation or Xposed, Greenify, or some other mod interfering.
Yes, I have magisk+xposed systemless+Greenify
please help me find any other command or mod or tasker task or anything that can do this job
please help me...............please
Related
{
"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"
}
Hello everybody, first time actually posting here but i figured i'd share on here
what i found out through trial and error... Since there is not much posting going
on here, hopefully it helps those who can't figure this out.
NOTE: there are some graphical glitches if you have widgets on your screen,
the picture may get stuck in the notification bar after rebooting, basically just open any app
and the notification bar will reset.
First, install ADWLauncher or any custom launcher you prefer.
then install AppWidgetPicker from this thread
http://forum.xda-developers.com/showthread.php?t=780828
Rename it to AppWidgetPicker.apk
then open up adb/terminal and:
adb remount
adb push AppWidgetPicker.apk /system/app/
then you need to correct the permissions (VERY IMPORTANT)
adb shell chmod 644 /system/app/AppWidgetPicker.apk
for safe measures, reboot.
now you should have a working custom launcher with widgets...
Now it leaves us with one problem, the Notification bar overlays a blue taskbar
and back button over the clock and rest of the notification bar.
Now there are 2 ways i've found to fix this. i've heard about freezing the
EmotionUI Launcher but i have no idea what that means, so i've come up
with this.
MAKE SURE YOU HAVE A LAUNCHER INSTALLED BEFORE PROCEEDING!
Head back into adb:
adb remount <--important
adb shell
when in shell ($)
su <--important
cd /system/app/
ls
now your looking for Launcher.apk & Launcher.odex
either (backup both Launcher.apk & Launcher.odex!)
mv /system/app/Launcher.apk /sdcard/Launcher.apk
mv /system/app/Launcher.odex /sdcard/Launcher.odex
or just completely remove it!
rm /system/app/Launcher.*
after this, Hit your home button and BAM!
if your wondering, yes the Emotion widgets DO WORK you may have a proble
where the row or column size don't show when placing it, but u can just fill it in,
then resize to your liking.
this can also be done in root explorer.
Since this is a Android Studio specific problem..... I'm posting here....
Just did a first install of Android Studio and cant even open the SDK Manager right off the bat. What gives?
{
"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"
}
In case the above image doesnt show it reads....
Cannot launch SDK manager.
Output:
'"f:\android\sdk\tools\lib\\find_java64.exe" -s' is not recognized as an internal or external command,
operable program or batch file.
ERROR: No suitable Java found. In order to properly use the Android Developer
Tools, you need a suitable version of Java JDK installed on your system.
We recommend that you install the JDK version of JavaSE, available here:
If you already have Java installed, you can define the JAVA_HOME environment
variable in Control Panel / System / Avanced System Settings to point to the
JDK folder.
You can find the complete Android SDK requirements here:
Click to expand...
Click to collapse
Notice the double slashes "\\find_java64.exe". This is an error (invalid path) that it is obviously generated incorrectly.
JAVA_HOME = "C:\Program Files\Java\jdk1.8.0_45"
PATH = "C:\ProgramData\Oracle\Java\javapath;%JAVA_HOME%; ...... etc ..... "
:crying:
fixed temporarily.....
had to make the following changes to android.bat in order to get SDK Manager to start.....
Change:
Code:
rem Check we have a valid Java.exe in the path.
set java_exe=
call lib\find_java.bat
if not defined java_exe goto :EOF
set jar_path=lib\sdkmanager.jar;lib\swtmenubar.jar
rem Set SWT.Jar path based on current architecture (x86 or x86_64)
for /f "delims=" %%a in ('"%java_exe%" -jar lib\archquery.jar') do set swt_path=lib\%%a
To:
Code:
rem Check we have a valid Java.exe in the path.
set java_exe=java.exe
set jar_path=lib\sdkmanager.jar;lib\swtmenubar.jar
rem Set SWT.Jar path based on current architecture (x86 or x86_64)
rem this fails..... for /f "delims=" %%a in ('"%java_exe%" -jar lib\archquery.jar') do set swt_path=lib\%%a
set swt_path=lib\x86_64
..... pathetic ...... its 2015.... no one should have to do this... come on google.
Sounds like the Environment Variable isn't set up yet.
Try Step 2 under 'Set up Android Studios on Windows'
Installing Android Studios
UPDATE: there is an alternative app that let you change the color mode, but you need root.
If you're interested, this is the xda thread, and the dev is @emandt. This is the only way I've found of having a not saturated color mode if you don't have a touchwiz rom, like Cyanogenmod.
works for me on G920f rom Touchwiz
< Tutorial >
1 - Join this community
Manual download - Version 1.1.6
Download link: http://www.emandt.net/Android/ColorModeChanger/Testing/ColorModeChanger_1106.apk
Version 1.1.6:
- Fixed Interface issues on Tablets
- Fixed FC on UI opening on Tablets
Limitations ONLY during BETA period:
1) Each time you launch the App it checks for License. If internet connection is not available, the App will not run.
2) For cause n.1 the option "Start at boot" will not work because internet connection is not ready during boot (but it will work when released outside the Beta period)
3) Only MANUAL update available
4) If you have more than one Google Account registered on your device, please contact me because I have to manually add the others to the Licensed list.
- Install on External SDCard is not supported
- Only English Language available
Instructions and development choises:
To avoid creating a permanent running Background Service/Process AND a separated Interface (for changing Settings) I preferred to use an "all-in-one" App which requires this steps:
- first launch the App doesn't show anything (it just set the default/last_saved configuration)
- if launched AGAIN within 30 seconds it will open Settings Interface
- next launches follow the same behaviour as before
This behaviour is intended to work with "Start at boot" options to avoid Interface launching after a Boot is completed.
PS: Open the Interface (the second launch within 30 secs from the first one) may take few seconds while reading informations of your screen.
Instructions for download and activate it:
1) Visit this link and accept to be a Beta Tester: https://play.google.com/apps/testing/com.emandt.colormodechanger (this link will allows your Google Account to get a valid License)
2) PLEASE DON'T DOWNLOAD the App from Play Store because a payment is required even if in Beta (Google is crazy charging Testers for this), but manually download it with the link above
Please report bugs providing Device Name and Android Version or I cannot help you so much.
{
"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"
}
Hi everyone,
I wanna build old version of Xposed, for Android SDK 16-19, then have tried to compile Xposed fw for hundreds time but still failed.
Environment: Ubuntu 15.10 x64 | tools: JDK 1.6, libc6 ....
AOSP: JZO54L / android-4.1.2_r2 /Jelly Bean ("make app_process" have been run successfully).
My steps:
- Download AOSP into /opt/android/aosp
- XposedBridge.jar: Download Xposed Installer here repo[dot]xposed[dot]info/module/de.robv.android.xposed.installer and detach jar from apk. Put it to /opt/out/java
- Download XposedTools source from github into /opt/xposed/ then make build.conf file:
Quote:
[General]
outdir = /opt/out
[Build]
# Please keep the base version number and add your custom suffix
version = 58
# makeflags = -j4
[GPG]
sign = release
user = 852109AA!
# Root directories of the AOSP source tree per SDK version
[AospDir]
16 = /opt/android/aosp
# SDKs to be used for compiling BusyBox
# Needs github[dot]com/rovo89/android_external_busybox
[BusyBox]
- To integrate Xposed to AOSP, I tried following 2 ways in the instruction (local manifest and manual cloning)
+ local manifest: link [XposedTools]/local_manifests/xposed_sdk16.xml to [aosp]/.repo/local_manifests/ then run repo sync.
+ manual cloning: remove [aosp]/build; clone github[dot]com/rovo89/platform_build/ to replace; clone github[dot]com/rovo89/Xposed into [aosp]/framework/base/cmds/xposed
- Go back to [XposedTools] and run ./build -t x86:16
>>output: cd /opt/android/aosp && . build/envsetup.sh >/dev/null && lunch full_x86-user >/dev/null && make -j4 TARGET_CPU_SMP=true xposed
The result I received is a big "app_process_xposed" file (~ 270-350 KBs), it size is as many times as the origin app_process file (~20 KBs). I think there are somethings wrong. I open them by 7z and see some differences:
{
"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"
}
I may did some mistakes in these steps. Could you please give me any advice?
Thank so much!
{
"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"
}
Attention: During this debloat proceess you can lose some of data. Do not continue if not sure. Recomended to do after you unpacked and updated software on your NEW device without copying your personal information.
1) download ADBApp Control (please buy if you like it)
2) activate ADB on your tab
3) activate ADB in developer settings
4) Connect usb cable to pc and run ADBAPPControl software
5) Allow ADB connection on your Samsung device
6) Choose all preinstalled app you no need (see my screen above), i had 122 useless apps selected.
6a) -------or Choose LOAD PRESET if want to load my 122 disabled apps list
7) Choose Delete data\cache if you want totally clean apps data (or deselect it)
8) Choose Disable (all selected apps will be DISABLED and not uninstalled and can be enabled back in any time if needed manually or via ADBAPPControl app)
9) Wait untill ADBAPPControl finish clean up, disconnect USB cable and restart your tablet
attention: do not disable Samsung Keybord if planning to use DEX - you can get bootloop
(comment from @sosimple)
Thanks!
Really a good list. If you don't use Samsung ecosystem, all the non useful.
From the 122 apps, you can open the text file with notepad and delete which you dont want to freeze. (I'm posting it for those who don't know how it works). I did it in not a new tab but worked fine.
There is also Ladb ( https://play.google.com/store/apps/details?id=com.draco.ladb ) which works fine in galaxy tab s8 ultra. You can create adb without pc, just be connected to a wifi, and freeze / Defreeze apps with adb commands (google it).
sosimple said:
From the 122 apps, you can open the text file with notepad and delete which you dont want to freeze. (I'm posting it for those who don't know how it works). I did it in not a new tab but worked fine.
Click to expand...
Click to collapse
just load my list in ADBAPP Control and UNCHECK an apps you want to keep ))) simply easy
I think the stock gallery app and calculator are pretty good. I'd keep those.
To have Dex working again, i should open those?
com.sec.android.desktopmode.uiservice
com.sec.android.app.desktoplauncher
com.samsung.desktopsystemui
Are there any others i must open?
Thanks,
Hi @malikin. Thanks for this. You may want to Edit your OP and change the thread type from the default of "Question" to "General" instead. Cheers.
sosimple said:
To have Dex working again, i should open those?
com.sec.android.desktopmode.uiservice
com.sec.android.app.desktoplauncher
com.samsung.desktopsystemui
Are there any others i must open?
Thanks,
Click to expand...
Click to collapse
I reply to myself. Anyone who wants Dex , defrose those. I just tested it. Also if you want dex ,don't ever freeze Samsung keybord (regardless if you dont use it because you have for example google keyboard) because when you start Dex ,tablet bootloop and you'll neet to factory reset. At least that is happening to Galaxy tab s6, I don't see why wont happen here.. If i had root I'll tested but i don't. In tab s6 where i have root , i can fix it without factory reset.