I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
ClubWDW said:
I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
Click to expand...
Click to collapse
You updated to September security patch?
I believe so. I update the moment LOS releases their update.
ClubWDW said:
I believe so. I update the moment LOS releases their update.
Click to expand...
Click to collapse
I think it's a bug in all ROMs which have october security patch. From the package installer open recents apps and then select the installer again, that fix the problem.
It is a bug in LOS. If you'll minimize installation window, and execute it again from file manager - install button becomes active
Related
I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
roboots21 said:
I had the same issue. When you install wanam, it makes a backup of the features.xml file and removes most of the original text from thr file in /system/csc. Go there, see if there is a backup (will be called features.xml.bak and should be about 15 KB or so) and rename it to features.xml after deleting the current features.xml. Reboot. Voila. Profit.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Thanks,
Unfortunately, it still does not work. I deleted the new and renamed the .bak and now I'm still stuck on no service, and process stopped.
took about 6 minutes for cell service to come on.
I am having same problem since installing framework and related modules. Not having same length of delay but it's long enough to get attention. Sometimes it asks for SIM card to be installed. Still reading and searching for solution. Wiki check back later.
Thanks.
Sent from my SCH-I545 using xda app-developers app
I am finding this with the latest update 1.4.5. I TiBU back to 1.4.3 and don't see the problem. Then I used TiBU to not allow Wanam to auto update and all is well.
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
justinisloco said:
I rooted my MD7 GS4, and Recently (re)discovered Xposed Modules. I figured, hey why not. I wanted as much of a stock experience as possible, but stupid little things like the Text Messages on the lockscreen bothered me.
After downloading and installing Xposed and Wanam, and rebooting, my phone seems to not get any service for a few minutes before finally getting cell service. while searching, at times it will even ask me to switch to global mode? and if I press cancel, sometimes "Sorry, com.android.phone has stopped" and it will freeze. sometimes it wont force stop and then my cell data FINALLY comes on.
I have since deleted and uninstalled Wanam, Xposed, removed the framework, and still having the issue. I just cant figure out what it may be.
Click to expand...
Click to collapse
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
kenkamm said:
I have the same device, with the same issues after installing Xposed and Wanam. None of the suggestions here worked for me. However, for me, normal operation resumed after deleting Wanam and the Xposed framework. I'd love to find a solution to this, so I could use the Xposed & Wanam.
Click to expand...
Click to collapse
Even deleting it didn't fix it for me. I ended up unrooting and going back to stock. Since then move stayed stock unrooted. If I can't get a ROM then I might as well stay safe
Sent from my SCH-I545 using Tapatalk 4
NilsP said:
I found the same problem with Wanam or xTheme whenever I make changes with it and I just reboot and service comes right back. Or just don't use a soft reboot
Click to expand...
Click to collapse
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
NilsP said:
I know I am repeating myself but if you follow these steps you will be fine.
1) Apply whatever you want.
2) Exit out of whatever you are applying to home screen
3) Use the power button reboot option - Do Not use the reboot options in the xPosed modules
4) If you don't have signal bars in a few seconds when the lock screen come up just reboot with power again
Side note: Do not install or activate any more than 1 thing at a time. For example, install xPosed, reboot, install, Wanam, reboot, make selections in Wanam, then reboot. All reboots from the power button.
Click to expand...
Click to collapse
I followed all your rules as I tried this again today, and still not having any luck. I have narrowed my problem down to the installation of Wanam. I did a reboot between each step of installing the Xposed framework, and had no issues there. Yet, after installing Wanam (and before activating the Wanam module) upon reboot, the phone cannot find cell service for at least a few minutes after booting up. Rebooting again (and again and again) makes no difference.
I was trying to install some custom apk's for some games and stuff ( skins, fonts, wallpapers) and after tapping install and waiting about a minute, I always get "app not installed". It worked before with no problems and all of a sudden it won't install anything unless from Google Play. I do not have any overlays enabled and previous version/stock apk is uninstalled. I tried installing with Lucky Patcher and it said there was a conflict with permissions and to uninstall app first. The original apk is gone, so not sure what's up there.
Below is what I have. Thanks!
Samsung Galaxy Note 4
Lollipop 5.0.1
Kernel 3.10.40-4243283
Rooted
SuperSu
Titanium Backup Pro
Busy Box
Unreal that no one here knows anything about this...
Beantownfan73 said:
I was trying to install some custom apk's for some games and stuff ( skins, fonts, wallpapers) and after tapping install and waiting about a minute, I always get "app not installed". It worked before with no problems and all of a sudden it won't install anything unless from Google Play. I do not have any overlays enabled and previous version/stock apk is uninstalled. I tried installing with Lucky Patcher and it said there was a conflict with permissions and to uninstall app first. The original apk is gone, so not sure what's up there.
Below is what I have. Thanks!
Samsung Galaxy Note 4
Lollipop 5.0.1
Kernel 3.10.40-4243283
Rooted
SuperSu
Titanium Backup Pro
Busy Box
Click to expand...
Click to collapse
Is there any kind of error message or reason for the failure given? Anything you've changed for this to happen? Have you checked the logcat to see if there's any more information there?
Beantownfan73 said:
Unreal that no one here knows anything about this...
Click to expand...
Click to collapse
Is this the post from 2015 that you are talking about, since this is your last post until lately)? When you didn't get help for some gaming and other stuff that you were trying to use Lucky Patcher for, so you decided we were all jerks? Like any problem ever should be able to be solved just by posting to XDA,?
okay
Maybe you should read this thread/post
Operators are not here 24/7 to tend to your needs. Please realize that. This is a developers site first and foremost.
I’m not talking about not getting help for lucky patcher years ago. I’m talking about the one I posted yesterday or day before yesterday about custom roms for my sm-t810. I googled it and checked here, obviously in the wrong places, to find roms compatible with my device/firmware. The other post I made about broken links and malware, etc, was because that thread had to do with theming, a guide, how to do it, etc. I was disappointed that several links were either broke or lead to some ad page.
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
Hello, I have a Redmi Note 3 Pro running sMiUI (based on the Xiaomi.eu ROM) but this seems to be irrelevant.
while this strange behaviour doesn't seem to be limited to this device, being noted here and here, it does seem that the symptoms are the same.
In the SuperSU logs i found that firstly Whatsapp tried to gain root and was denied, followed by zygote requesting 3 times over the following few hours. The log for each is blank.
I have just rebooted my device and after unlocking whatsapp immediately requested root. Yet to see zygote request root again but I'll update you should it appear.
UPDATE: Whatsapp has again requested root.
UPDATE2: WhatsApp continues to request, however zygote has not. It appears to be happening every half-hour (ish)
U3: uninstalled WhatsApp, will see what happens at the half-hour mark.
Anyone know what's going on?
Also some probably irrelevant weirdness but I'll write it anyway given this only started appearing after this happened:
My phone did something weird earlier, I restarted, and normally on my ROM it just has a spinning little loading thingy in the middle of an otherwise blank screen, then goes off and reboots, showing the Mi logo, this time however it randomly showed a kinda-pulsating android logo shortly after the usually " spinning loading icon" and then continued to the usual Mi logo. Given I'm running sMiUI I've never seen it display a large android logo before like this. I just rebooted again and this behaviour was not repeated.
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
immns said:
Try xiaomi.eu rom, or stock rom. Or might be you're just installed modified WhatsApp and zygote apk from untrusted source. I don't use sMIUI
Click to expand...
Click to collapse
The struggle I went through to get off of the vendor ROM, I'm not going back to stock. sMiUI was based on the Xiaomi.eu ROM, so the zygote is probably straight out of that.
I have installed WhatsApp from Google Play so I assume it doesn't get more secure than that. I've made no attempt to replace zygote, I don't really know what it does, something about starting apps.
The ROM I'm using doesn't seem to be remotely relevant to this, given it's happened on 3 different devices from different brands as I can see from the links I provided.
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
immns said:
It doesn't make any sense. WhatsApp is used to not request any root permission unless it's infected by mallware. You can try to use xiaomi.eu rom alongside with 3rd party mods instead of use pre-moded rom from sMIUI.
Click to expand...
Click to collapse
Indeed, last WhatsApp update was 13th December, so I would have seen this happening before today if it was in normal WhatsApp. This is nothing to do with sMiUI, I've had this ROM installed for many months now with no issues.
And as previously stated it is based on Xiaomi.eu ROM.
But yes my suspicion is malware, however it's not specific to MIUI or any varients as this was also occurring on a Galaxy S5 and another device.
Everyone: Please read the entire thread before replying so I don't have to keep restating facts
Hey, i have same problem too, im using redmi note 2, today i get notif, whatsapp need access root, after several minute, zygote need access root too, now i deny that access at super su
first time root/customrom/kernel etc.
Ive had the same thing happen..First time I thought it was strange though and denied permision was with the zygote thing asking permission...ive granted whatsapp and whatsapp extensions permisson for example cause i thought that was just the way it worked. ive granted LMT permission and a couple more apps
thought it was more of a windows type "" do you trust this program to do things" type thing.
things is my, installation is pretty fresh. and I dont get where I should've gotten malware from
htcm8/Viperrom/elementalx kernel
bunch of file explorers (sdmaid /totalcommander) and terminals all from the playstore. Xposed installer and a couple modules that all seemed reputable with ongoing xda threads and downloaded from the original source. amplify/bootmanager(something with that maybe?)/chromepie/secure settings for a tasker profile/minminguard.
you see something we have in common on the phone?
phone is running fine..nothing strange. The zygote i got for the first time today and I denied and hopped on google...whatsapp is in my rootlog constantly. i see the greybox popping up every once in a while that root was granted. never thought anything of it.
today I installed termux ternimal from the playstore...maybe thats where the zygote su request comes from?
---------- Post added at 10:05 PM ---------- Previous post was at 09:39 PM ----------
from what I see elsewhere the whatsapp extension module in xposed, which is a root app might have something to do with the whatsapp requests. I dont exactly know how these things work but the altering might explain app doing thing they normally dont do.
dont know about zygote...got it one time and it has not been back
Same here.
I'm on a fresh install and this zygote su request wasn't appearing until I reinstalled all my apps.
Another forum states that zygote is run at such a raw level that it simply would never request root.
I am for now denying su requests with little to no adverse effects.
Can anyone confirm for certain that zygote should never need to request root? Is there anyway to dig out the rogue source/apk when av apps are showing nill?
As I have nothing Whatsapp on my phone, thinking it may be an xposed mod. Might be a good idea for us to list are xposed mods so we can cross reference. Not sure?
samsung i9505 | resurrection remix | android 6
I'd been dirty flashing LineageOS on my Xiaomi Mi 5, with no real issues, for almost exactly a year so, on Saturday, I decided that it was time for a clean flash.
I used Titanium Backup (latest free version from Play Store) for all apps and data, and all system settings (the guide I followed suggested these 2 scripts were all I needed). I noticed that after the backup, my wallpaper was back to the default and a few other settings had been reset.
Then I clean flashed exactly following the instructions in the official 15.1 LOS thread for my device.
So I have the all the latest: TWRP, OpenGAPPS (nano), LOS SU, firmware, and last week's LOS 15.1 of course. I have nothing else like Magisk installed - it's basically vanilla.
I then completed the initial setup and then restored using the Titanium Backups. Aside from a few settings needing to be done again, all seemed well. But then the home and recents buttons stopped working, along with notifications and the drop-down settings menu.
A bit of Googling revealed that this is symptomatic of the install wizard not having completed properly so I re-triggered it using the Nova Launcher activities workaround and that seemed to fix it. When I restarted the phone however, it kicked me back into TWRP.
Reinstalling the weekly got it going again but I had to redo the Nova workaround. I can't get the fix to stick and I'm concerned that it's symptomatic of a deeper problem.
I'd really appreciate some help diagnosing the problem / advice on how to proceed.. No-one else has mentioned anything like this that I've been able to find on the Official LOS 15.1 threads so I guess it's unlikely to be a ROM problem.. Might it have been Titanium Backup messing up settings somehow?
HairyPriest said:
I'd been dirty flashing LineageOS on my Xiaomi Mi 5, with no real issues, for almost exactly a year so, on Saturday, I decided that it was time for a clean flash.
I used Titanium Backup (latest free version from Play Store) for all apps and data, and all system settings (the guide I followed suggested these 2 scripts were all I needed). I noticed that after the backup, my wallpaper was back to the default and a few other settings had been reset.
Then I clean flashed exactly following the instructions in the official 15.1 LOS thread for my device.
So I have the all the latest: TWRP, OpenGAPPS (nano), LOS SU, firmware, and last week's LOS 15.1 of course. I have nothing else like Magisk installed - it's basically vanilla.
I then completed the initial setup and then restored using the Titanium Backups. Aside from a few settings needing to be done again, all seemed well. But then the home and recents buttons stopped working, along with notifications and the drop-down settings menu.
A bit of Googling revealed that this is symptomatic of the install wizard not having completed properly so I re-triggered it using the Nova Launcher activities workaround and that seemed to fix it. When I restarted the phone however, it kicked me back into TWRP.
Reinstalling the weekly got it going again but I had to redo the Nova workaround. I can't get the fix to stick and I'm concerned that it's symptomatic of a deeper problem.
I'd really appreciate some help diagnosing the problem / advice on how to proceed.. No-one else has mentioned anything like this that I've been able to find on the Official LOS 15.1 threads so I guess it's unlikely to be a ROM problem.. Might it have been Titanium Backup messing up settings somehow?
Click to expand...
Click to collapse
hi, dont know.. but the thing is... I am really questioning why "Setup Wizard 2.0" is always being Frozen on Titaniumbackup app in my phone. I Unfroze it but after restarting it is frozen again. Is it the same for you? ... I got no issues with it but, i just dont know why it is always frozen.
yllonjohnb said:
hi, dont know.. but the thing is... I am really questioning why "Setup Wizard 2.0" is always being Frozen on Titaniumbackup app in my phone. I Unfroze it but after restarting it is frozen again. Is it the same for you? ... I got no issues with it but, i just dont know why it is always frozen.
Click to expand...
Click to collapse
I'm new to Titanium - how do you see which apps are frozen?
HairyPriest said:
I'm new to Titanium - how do you see which apps are frozen?
Click to expand...
Click to collapse
just scroll among the app list.. See if you have a purple highlight on "Setup Wizard app. Or just use "filter" on the setting, and select "show frozen apps only".
yllonjohnb said:
just scroll among the app list.. See if you have a purple highlight on "Setup Wizard app. Or just use "filter" on the setting, and select "show frozen apps only".
Click to expand...
Click to collapse
Thanks, I looked and neither Pixel Setup nor Setup Wizard are frozen on mine (although they might be just after startup - I'll check next time)