Help! I've been using Xposed for a while now to great reward, when suddenly installed mods and apks will not launch. The Xposed module says they are installed, but when attempting to launch I get a pop-up stating that I must activate the (activated) module and reboot, though this has been done. Greenify is suddenly failing and needs to be shortcut activated constantly & the screen lock hibernate won't activate after I check the settings box or the pop-up. Baidu downloads manager captured the package, but no data flows. Dolphin downloads and installs, but then after activating & rebooting they read as inactive only on launch. The logs all say "file does not exist". Going to have to reinstall & am ditching TouchWiz for sure. Any advice would be appreciated. Been out of the loop for a bit, but catching up, but for these WTF moments. Guess that makes me a re-noob.
Related
I have noticed a number of times now that I will download an app and its installer will run but when I get to the screen where I have to click either the "install" button or the "cancel" button, that the "install" button does not work. It has no effect and doesn't highlight - just seems completely dead. The "cancel" button always still works when this happens.
It has happened for apps being installed or updated from play and it has also happened on sideloaded or other apps - like my non-play version of tasker which just had an update to download and install. Downloaded just fine, "install" button non-functional. Rebooted the phone, went to the Download folder and launched the apk - now the install button works fine! WTF?!
This is very annoying. The same thing has happened trying to install some apps directly from google play. It will download and start the install, but when it comes time to click the install button - it doesn't work. Reboot the phone, go back to google play, and now it will install properly.
Is anyone else seeing this? How common is it? My phone is rooted, but everything else is stock.
Install button problem
I had this problem with "Turn off the screen" app. However, that's the only one so far
Just happened again - that's about 6 times today
I've been trying lots of apps on my new nexus 5, so lots of installs. From the tasker site, I downloaded two icon packs to the Download directory. I'm using es explorer to look at the details of the two apk files. When I click on them, I get the screen that shows me the applications access and asks me if I want to install it. The install button at the bottom does nothing, the cancel button works as expected.
Now I'm going to reboot - and experience tells me I will then be able to install them both...
Interesting - I was able to install the first icon apk, but not the second one. So installing the first one is causing some sort of state change, or something else started later in the phone's start up process to block it. Rebooting again and waiting this time for everything that starts on boot to start...
That was unexpected - I still can't install it. Going to try rebooting again and trying to install it earlier...
Alright, that seems to be the key. I was able to install it multiple times but eventually the install buttton stopped working.
I started killing applications and trying to install the apk after each app quit. I traced it to Juice Defender Ultimate, which is a surprise. I can disable Juice from its menu, keeping it loaded, and the install works. When I click the enable button in Juice, the install button for the apk immediately stops working.
I will continue searching and experimenting and report back my results. Have any other Juice Defender users noticed the problem?
Juice defender is a crap app. Don't use it, it'll only make matters worse for your battery.
I agree, it's not worth using it. Anyway when I used it some time ago I also had this problem, it's linked to the brightness control, so you need to disable it before every installation. They also have a fixed installer app that automatically disable auto brightness before install and then enable if after it finished. If your phone don't ask what app you want to use to install then clear the default app settings and choose the fixed installer next time.
Inviato dal mio Nexus 5 utilizzando Tapatalk
I have removed Juice Defender
Thanks for your reply. I had also noticed some unexpected changes in screen brightness with juice defender and will be interested to see if that also disappears now that it's gone.
I also own tasker so I'm looking at using that to save power by changing the phone settings in various ways.
Thanks for the input! It's a strange problem that the cancel button works but the install button doesn't.
yaconsult said:
Thanks for your reply. I had also noticed some unexpected changes in screen brightness with juice defender and will be interested to see if that also disappears now that it's gone.
I also own tasker so I'm looking at using that to save power by changing the phone settings in various ways.
Thanks for the input! It's a strange problem that the cancel button works but the install button doesn't.
Click to expand...
Click to collapse
Get betterbatterystats to see what wake locks are keeping your device awake. That's the best way to get good battery life. It can take a little figuring but once you know what's causing the problem you can start to address it
It isn't a problem. When an app like juice defender or screen filter or lux auto brightness controls your brightness, they use an overlay to make it look like your screen is getting darker than it can. The overlay, since it covers the entire screen without you noticing, also disables the install button. This is a security feature implemented BY GOOGLE to keep an overlay app with malicious intent from being able to hit the install button and installing things without you knowing.
THIS IS NOT A BUG
Sent from my Nexus 5 using Tapatalk
Additional links and info about Juice Defender and the app install button
http://feedback.latedroid.com/forums/70437-feedback/suggestions/2518486-i-can-t-install-apps-from-sd-card-when-jd-is-start
http://feedback.latedroid.com/forums/70437-feedback/suggestions/1681367-issue-can-t-install-apps
http://forum.xda-developers.com/showthread.php?t=1324537
Lenovo A7-40 multiuser/restricted profile - "app is not installed" for every app
Hi everybody,
for mentioned tablet with Android 4.4.2 I installed CWM (which gets always deleted after reboot) and rooted the tablet in order to activate multiuser/multiprofile. This worked out so I could set fw.max_users = 4.
Since the tablet is used by our little daughter I installed Kids Place in order to restrict as much as possible. Unfortunately booting into "safe mode" bypasses kids place completely and provides full access to everything (she found out by accident). So I tried to get rid of this problem by trying to create a restricted profile which did not work since the installation did not finish normally and for all assigned apps I get the information "app is not installed" (while it is shown and can be clicked on).
So I tried to setup a second complete user. But same problem here: Installation did not finish normally (also black screen and running circle forever) and afterwards none of the shown apps can be started from homescreen (while I could start playstore from within settings/apps menu): Message: "app is not installed".
Does anybody have any idea how to get this topic solved? Either by preventing the safe mode being able to be used without kids place or by creating a restricted profile which works as expected?
Many thanks in advance!
Bye
This is not meant to be a detailed tutorial, but rather an overview of the struggle I had to root and modify a Wiko Lenny 3 (with links for convenience), so others can benefit.
About a week ago I purchased a Wiko Lenny 3, a device with minimal RAM specs (1GB) for Marshmallow. This creates problems with app-notifications due to the Phone Assist (/system/vendor/operator/app/ApePhoneAssist) and Protected Apps (/system/app/CustomWhitelist) software that is pre-installed by Wiko to compensate for the low RAM.
First, I freshstarted the phone and put in the basic configuration. I immediately updated the system to OTA version V54.
Then I flashed TWRP 3.0.3-0 with SPFlashtool from this site:
http://www.needrom.com/download/recovery-twrp-wiko-lenny-3/ .
There is also TWRP 3.0.2 available but that DID NOT WORK on my phone:
http://drive.google.com/file/d/0B6isv8b6duCrbjdJbDVlRFpONlk/view
After that I rooted the thing via TWRP with SuperSU.zip, and installed Xposed via TWRP. I debloated the phone by removing most Google trash.
I use Syncthing to sync the contents of my external SD card to other devices. But Syncthing needs write permission on the SD card and Marshmallow mounts the SD card read only, and can only give write permission to the ./Android folder on the SD card. I fixed this with XInternalSD. The other option, Marshmallow SD Fix 2.0, DID NOT WORK.
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267
http://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263
So far, so good. However, after a while I noticed that FaceSlim (lightweight FB client) did not send push notifications. FaceSlim works perfectly on my old KitKat phone and also on a Lollipop tablet. So I checked running processes with OSMonitor and it turned out that FaceSlim was not being autostarted at boot. Some other services were not autostarted at boot as well:
AFWall+
Applock
DataStats
EZ Wifi Notification
FDroid
MaterialFBook
WiFi Automatic
Xprivacy
I have K-9 Mail installed as well but that app actually DID send notifications, for a while at least, later on it would not work anymore.
DataStats would not stay on screen if I forced closed it after starting it manually.
AFWall+ would only start if I added the widget on the home screen.
I tried every recommendation, like disabling doze mode for all apps and whitelisting the apps in Wiko's "Phone Assist" app, an overly aggressive resource manager that is shipped on Wiko phones, probably to make up for the low RAM. Nothing would autostart the apps.
So, I decided to flash the phone to its original state, using the official vanilla ROM from Wiko (V54), just to see if rooting screwed up the phone:
http://nl.wikomobile.com/maj.php?telephone=1246
After flashing the phone, I tried to get notifications from FaceSlim, but that still wouldn't work, so i guess the problem was not in my rooting the phone.
I also tried to flash TWRP again but this DID NOT WORK WITH THE DOWNLOADED ROM FROM WIKO (as opposed to the OTA update). TWRP got installed, but the phone would hang at startup at the Lenny logo, not booting to the UI.
Fortunately I had a TWRP backup of the old system and I flashed it, I could again boot into the UI now.
I found that other users experienced similar behaviour:
http://www.android-hilfe.de/thema/a...enachrichtigungen-funktionieren-nicht.781196/ (German)
http://android.stackexchange.com/qu...ground-sync-processes-wiko-lenny-3-what-to-do
As said earlier the Wiko has two pre-installed apps that manage autostart behaviour and power management.
1 - The "Phone Assist" software has a "Boot Optimize" screen. This feature does work for some apps, but not at boot level. When I deny autostart for AFwall+, it comes up after a reboot and is killed shortly thereafter. If I disable everything in Boot Optimize, the switch for Applock and Wetteronline returns to enabled after a reboot. Moreover, it cannot prevent Instagram from starting, one power hungry app.
2 - Phone Assist also has a "Power Management > Power saving" mode presumably to restrict network acces for apps in screen-off mode. This could be the same as the 3rd party Doze apps on Google Play that use a local VPN to restrict per-app network acces in standby mode. It is debatable if this saves much power, and there could be a security risk.
3 - Phone Assist also has in "Power Management > Advanced > Gear icon > Whitelist" (free translation, my language is Dutch) a screen to "whitelist background apps". If you whitelist an app here, it is simultaneously enabled in the previous menu ("Power Management > Power saving"), so I suspect this menu is redundant.
After playing around with the various settings in "Phone Assist", NOT A SINGLE APP WOULD START AT BOOT ANYMORE, even if I whitelisted all.
4 - The "Protected Apps" feature, found in the Android Settings, will allow you to whitelist apps for autostart. If you put this app in default mode, it will select some apps to start at boot by itself. If you whitelist apps, they indeed do start at boot. But "Protected Apps" has a limit of four apps that are allowed to autostart. This makes use of the phone for social networking/email very limited. Some Huawei phones have this feature too, and also with a limit of four apps. This is clearly an attempt to make up for the low RAM in this device, preventing users from running too many background apps. "Protected Apps" overrides all "Phone Assist > Boot Optimize" settings, making the latter effectively useless.
5 - On top of that there is the native Marshmallow Doze mode, which requires that you whitelist apps from Doze power management.
As you can see this is a complete mess. To enable/disable an app from autostart or power saving modes you have to visit two to five configuration screens. Tinno is the company that programmed this disaster (http://tinno.com/homepage?lang=en). Actually Wiko phones seem to be rebranded Tinno phones.
"Phone Assist" also has a junk cleaner (powered by Purify) that notified me once in a while asking me to delete SEVERAL GIGABYTES of junk. I had absolutely no desire to try that one ...
You can find so-called fixes on youtube for background apps that don't start, which involves installing QuickShortcutMaker, and enabling Low RAM via One Clean. That does not work on this phone.
There is a way to circumvent these autostart/powersave restrictions without removing the Wiko apps. With Link2SD or LuckyPatcher you can convert a user app to a system app. That way the app will start at boot and will send you notifications as well.
However, I wanted to get rid of this badly programmed mess altogether, and keep my apps running as user apps, so I have removed Phone Assist, its separate uninstaller, One Clean, and Protected Apps.
After deinstalling Phone Assist with SDmaid I manually removed "/system/vendor/operator/app/ApePhoneAssist" and "/data/dalvik-cache/arm/[email protected]@[email protected]@@[email protected]@classes.dex"
In /system/build.prop I edited the line "ro.tinno.whitelist.set=true" to "ro.tinno.whitelist.set=false". I don't know what that line does exactly, but it's just to be on the safe side. I think this setting is overwritten if you reinstall Phone Assist or Protected Apps.
I whitelisted some Social Media and Mail apps in Marshmallow native Doze mode.
After a few reboots some of my autostart apps started to reappear at boot, but not all. Only after I started the missing apps manually from the launcher they would appear after a reboot, and persist.
Later, I made a TWRP backup, and after that I wiped the cache and dalvik/art-cache with TWRP. Evertyhing went well.
Wiping the dalvik-cache can be a risky thing, it once left me with Android trying to optimize nine apps at every boot. I turned out that those were apps that I converted from user app to system app, and back. I removed those apps and reinstalled them and the optimization at boot went away.
So now every app starts at boot as it should, but it would be nice if this "Protected Apps" feature would not have a limit of four apps to boot, because then we would have a nice integrated boot manager. If anyone can find out if it is possible to modify this limit I would be much obliged
EDIT: So, three years later and I still have this phone. I have recently installed update v59 and encountered the same problems. After deleting PhoneAssist and ProtectedApps only a few of my apps worked right, and that was only after multiple reboots. Other apps would still not show notifications. However after I edited /system/build.prop and changed this line to "ro.tinno.low_memory=false" all apps suddenly worked correctly. Maybe this would even work with PhoneAssist and ProtectedApps still installed, but I don't care to find out at this point.
Didn't work for me, but...
Hi,
If someone has the same problem and stumbles on this post...
Setting ro.tinno.whitelist.set=false didn't work for me, probably because I aggressively modified the stock ROM to remove most of the vendor apps (including this PhoneAssist and Bootclean crap).
What actually worked for me was to set ro.tinno.low_memory=false. After that, all apps supposed to start at boot, actually did.
Once I'll finish my tests and use the phone for a couple of weeks, I intend to post a complete guide explaining how to uncrappify this phone (it's wonderful what you can do once you manage to successfully flash TWRP).
Wiko Lenny 3 2 gb RAM and 16 gb ROM
Hi guys, I have a clone of Wiko Lenny 3 commercialized in Tunisia under the name of EVERTEK EVERSTAR PRO 2. The device that I now has 2gb Ram and 16 gb of Internal storage, but the original version of the Wiko Lenny 3 has only 1 gb Ram. I confirm that is exactly the same device same processor same camera and screen. So I was wondering if I can flash my phone with the official Wiko Rom ? Does android indentifie Ram and Internal storage from the Phone ? Pleaaase Help me .. and sorry for my English
MoonSweep78 said:
Hi,
If someone has the same problem and stumbles on this post...
Setting ro.tinno.whitelist.set=false didn't work for me, probably because I aggressively modified the stock ROM to remove most of the vendor apps (including this PhoneAssist and Bootclean crap).
What actually worked for me was to set ro.tinno.low_memory=false. After that, all apps supposed to start at boot, actually did.
Once I'll finish my tests and use the phone for a couple of weeks, I intend to post a complete guide explaining how to uncrappify this phone (it's wonderful what you can do once you manage to successfully flash TWRP).
Click to expand...
Click to collapse
Yes, I installed update v59 and "ro.tinno.low_memory=false" works for me too, thanks!
Hey Guys,
A few weeks ago (not exactly sure of the time) I started getting a lot of prompts for Google Chrome and Play Services using a lot of power. It's the white box that pops up on screen, lists the apps, and gives the options to check again in a week or fix now. I keep hitting fix now, and after a couple days, sometimes later that day, I get the same alert. If I pull down the system bar, it's the Device Maintenance panel and I can tap on fix from there.
I've uninstalled play services patches, and reinstalled. I've uninstalled chrome and reinstalled, but that doesn't seem to have done anything. I had a prompt to install the new Tmo patch (12/10/2017 ish) which I installed hoping that might fix the problems, but it didn't.
Just wondering if anyone on Tmo with the S8+ has recently had any apps starting to go crazy and constantly being bombarded with "device fix" popups. Would booting to recovery and wiping cache help?
Galaxy S8+
T-Mobile
Stock - Updated with carrier push (12/10/2017)
No mods, no root, etc.
Thanks,
Sin.
So, I am changing this thread entirely. My original thread is hidden below.
I am running stock 10.0.1 rooted with Magisk. I was having the following issues:
1) Whenever selecting "Build and Install" for an overlay, it would then not show up in the Manager tab.
2) Whenever attempting to uninstall an overlay, it would not uninstall.
Turns out, any time I make a change in Substratum I have to restart before that change takes affect (with the exception of enabling/disabling an overlay). I'm not sure if this is the expected behavior, but if it is then it wasn't made very clear. So hopefully this helps anyone else who is experiencing the same issues.
Substratum has been really shaky for me on 10.0.1. My main issue is that I cannot get overlays to uninstall.
In substratum I go to Manager > Check the (already disabled) overlay that I want to uninstall > Tap the Action Button > Tap "Uninstall selected."
Nothing happens when I do this. Any ideas?
[Update] The workaround that I have found practical for my purposes was to run the SubstratumRescue.zip from TWRP. You will have to reconfigure your gesture and customization settings when you do this, but it is not as much of a pain in the ass as it could be I suppose.
I have always used build/install. Reboot. Activate them. Done.
Works every time I mess with my phone and need to get my theme back.
To uninstall, I uninstall what I want, reboot. Never had any issues getting them to go away.