So I recently updated to Oxygen 5.0.1 and ever since then I haven't been able to use advanced options when I long press an app. I used to have a variety of options including uninstall, but now those aren't working.
I'm not sure what I was on before this, but it was official from OnePlus, I just can't recall if it was a beta build or not. It was Android 8.0.0 and it still is.
I'm going to be romming it soon anyway, but I was curious as to why I lost those options.
You mean when on stock launcher and you long press an app? There's a small round with "i" in it, press that to go to that app option for clear cache or uninstall.
LightTheEntertainer said:
So I recently updated to Oxygen 5.0.1 and ever since then I haven't been able to use advanced options when I long press an app. I used to have a variety of options including uninstall, but now those aren't working.
I'm not sure what I was on before this, but it was official from OnePlus, I just can't recall if it was a beta build or not. It was Android 8.0.0 and it still is.
I'm going to be romming it soon anyway, but I was curious as to why I lost those options.
Click to expand...
Click to collapse
Were you on open beta before?
LightTheEntertainer said:
So I recently updated to Oxygen 5.0.1 and ever since then I haven't been able to use advanced options when I long press an app. I used to have a variety of options including uninstall, but now those aren't working.
I'm not sure what I was on before this, but it was official from OnePlus, I just can't recall if it was a beta build or not. It was Android 8.0.0 and it still is.
I'm going to be romming it soon anyway, but I was curious as to why I lost those options.
Click to expand...
Click to collapse
Try to download latest beta /prod build from oneplus official site and apply manual update. This possibly solve your problem
Related
So of course since i am rooted i could not just simply download the update. I was part of the developers preview though and was running OPP3.
So i downloaded the Android O Factory image from google and installed it manually expecting to have everything wiped. After install though using fastboot flash of all the images, all my apps were still present.
Is this normal? Did it full y install correctly? I was expecting to have to reinstall all my apps and re-setup device. Or because i was on developer preview and part of the beta testing within google they spared me the act of wiping my device?
Same experience with N
I had the same experience with N preview. I went from rooted N preview back to stock N. I installed the N factoruy image and didn't have to reinstall everything. AFIK the only reason that the device would be wiped is if you rolled back to the previous version (ie unenrolled from beta). I haven't bothered to root since then and am on 8.0 build OPR6.17623.010 which came as an OTA today 8/22. The only thing that I have had an issue with is the Pixel Launcher never upgraded to the latest version. The installed launcher ver is 7.1.1-3705938. I can't find anything related to the Pixel C launcher version anywhere and Google support was useless... a 30 minute live chat where I asked "what is the current version of Pixel Launcher in 8.0" was ultimately answered with "you will need to reset your device". Yes, that's always the best course of action. What launcher version do you have?
johnbravado said:
So of course since i am rooted i could not just simply download the update. I was part of the developers preview though and was running OPP3.
So i downloaded the Android O Factory image from google and installed it manually expecting to have everything wiped. After install though using fastboot flash of all the images, all my apps were still present.
Is this normal? Did it full y install correctly? I was expecting to have to reinstall all my apps and re-setup device. Or because i was on developer preview and part of the beta testing within google they spared me the act of wiping my device?
Click to expand...
Click to collapse
i got the image OPR6.170623.010 . flashed via fastboot. pixel launcher 7.1.1-3705938. so the OTA did give the same launcher the factory .zip has
Hi everyone Would you be so kind to provide me OTA dp4 for Pixel c if you still have it since all links for DP are down. Kind regards.
Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?
Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.
having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......
Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.
Well that sucks
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?
CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.
Fresh install from play store gets me this.
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.
Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0
Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!
lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...
why does a car/radio company care what a joke glad i dont have a car with unconnect
OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.
Since the update to 10.0.3.0 I've got a task named Android Setup in my tasklist. It seems to bundle some of the Google stuff, but I've never seen it before. My brother uses a Nokia 7 Plus with Pie and January patch aswell and he doesn't have this task. Could you please check inside developer settings / running services if you have it too?
Can't find this process on my phone
downloadonlyaccount said:
Can't find this process on my phone
Click to expand...
Click to collapse
Strange, on my side it even reappeared after flashing the full 10.0.3.0 firmware with data wipe.
I just figured that when I disable notification access for Android Setup the whole task disappears from the tasklist. I never gave it access.
Hi there. I'm new to Xiaomi/MIUI and would appreciate any help with the following issues.
Mi 10T – Global Stable 12.0.8 – stock launcher – MIUI optimization ON – de-bloated with ADB
I can't see how much storage space is being taken up by each installed app/package. They all show a "0" value.
I can't find Running Services under Developer Options.
I can't permanently disable usage access for System Launcher. It re-enables itself once I exit the settings menu.
App icons aren't updating. For example, Gmail, Maps, Photos and FB Messenger still display their old icons, despite me using the latest versions of those apps.
Google Play still displays the older menu style, despite me using the latest version of that app.
System Apps Updater doesn't detect OTA updates, despite several newer versions of MIUI 12 system apps existing on APK Mirror. This issue presented itself before I began de-bloating.
Updater doesn't detect OTA updates. I had to sideload 12.0.8 in order to update from the phone's original OS version (12.0.7). This issue presented itself before I began de-bloating.
Full disclosure: I'd rather not turn off MIUI optimization to see if that resolves any of these issues, as I'm not keen on resetting permissions (again).
Edit:
When I uninstall an app via the app drawer, a gap is left in its place. The icon of the uninstalled app is still there, it just turns invisible. I can uninstall it over and over, but it doesn't go away until I reboot the phone.
There doesn't appear to be a way to turn off the phone's equalizer. I can't use Blackplayer's equalizer until I do so. I don't know if the same applies to other music players.
Edit:
There doesn't appear to be a way to add emergency contacts or access them via the lockscreen emergency dialer. Emergency information (com.android.emergency) exists within the list of installed apps.
I'm on Global 12.0.7, unlocked, rooted and debloated. Stock recovery. What did you exactly do to update to 12.0.8? I do not want to wipe and I'm a little confused with the procedure...
sergio_sant said:
I'm on Global 12.0.7, unlocked, rooted and debloated. Stock recovery. What did you exactly do to update to 12.0.8? I do not want to wipe and I'm a little confused with the procedure...
Click to expand...
Click to collapse
I downloaded it from here, went to About Phone in Settings, clicked on the OS version number in the top left, clicked on the 3-dot menu in the top right and installed it via Mi File Manager.
AFAIK, you can only use Mi File Manager to install the update via this method. If you've disabled or uninstalled it, nothing will happen when you click that menu option – even if you've installed another file manager.
Dagabix said:
I downloaded it from here, went to About Phone in Settings, clicked on the OS version number in the top left, clicked on the 3-dot menu in the top right and installed it via Mi File Manager.
AFAIK, you can only use Mi File Manager to install the update via this method. If you've disabled or uninstalled it, nothing will happen when you click that menu option – even if you've installed another file manager.
Click to expand...
Click to collapse
I just tried this. It reboots and starts updating... but goes from 0.X% to 100% in two seconds, then it boots and it's still 12.0.7
sergio_sant said:
I just tried this. It reboots and starts updating... but goes from 0.X% to 100% in two seconds, then it boots and it's still 12.0.7
Click to expand...
Click to collapse
That sucks. It worked just fine for me. Don't know what else to suggest.
Dagabix said:
That sucks. It worked just fine for me. Don't know what else to suggest.
Click to expand...
Click to collapse
Finally I booted into TWRP and flashed 12.0.9 from there, no issues.
Hi
I was on Android 12 and signed in to the beta program 10 days ago.
I've noticed that APKs that were fine on Android 12 are not working anymore on Android 13 Beta.
APKs are crashing at opening.
I thought that may have been an issue related to the beta version of Android but couple of days ago Android 13 stable rolled out (I've signed out from the beta) but those apps are still not working.
I've found older APKs for a couple of apps and one works and one not.
How can I solve this without a factory reset?
Thank you in advance
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
skymera said:
What are the apps that are crashing? What does a logcat show when the app crashes?
Google introduced restrictions in A13 for side loaded apps. No longer can they use accessibility apis nor can they access notifications etc. Just speculation but if the apps you are using are old they may be crashing because of these changes.
Click to expand...
Click to collapse
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Lughnasadh said:
You can bypass those restrictions by going to the app info page of the app and clicking on the 3 dot menu in top right corner.
Click to expand...
Click to collapse
Wasn't aware of this, thanks!
I don't have any issues with manually installed apks...
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Waiting till the weekend to update, but what APKs are giving the error?
skymera said:
Wasn't aware of this, thanks!
Click to expand...
Click to collapse
Can't find this
Jeff_N said:
Hi, i have the same Problem with every sideloaded App.
There are no 3 dots in the right Corner.
I don't know exactly how to bypass Them
Click to expand...
Click to collapse
Do those apps need Accessibility and/or Notification Access permissions? If not, then I don't think the 3 dot menu needs to be there as it is only for those specific permissions (or whatever other permissions Google might add to the list in the future).
For example, I have Adaway installed but it doesn't have the 3 dot menu because it doesn't need either of those permissions. The same for App Manager.
I am really confused with this new "session-based install" security.
What are "session-based install" and "non-session-based install"
Play store app install --------- surly "session-based install" 100%.
3rd-party store install --------- is said also to be "session-based install".
Firefox download an apk --------- is said to be "non-session-based install",
But how the firefox different from a 3rd-party store????? a system white list something?
safetynet, selinux, forcing many settings, anti-rollback, non-store app restrictions.........
I enjoyed so much that google throws sht tons of troubles to billions of advanced users, to fight an enemy that may not even exist.
(how many people have their phone bootloader secretly unlocked remotely by a hacker and installed root malware, unknowingly?)
Gives a warning is good eg. bootloader locked warning is great IMO. But force the hands and keep finding ways to screw the advanced users as hard as they can, to get the "everything is under my control" status is the wrong path.
I read the news that malware devs have already found a way to bypass this restriction.
In the end, like many others, It achieved nothing, except giving trouble to advanced users and devs.
A global bypass must be also on the way, especially from China. Millions like 90% of APPs are not store-based in China since the google ban, and people are used to download apk from every companies' websites as we do on Windows PC.
somethingsomethingroot said:
Waiting till the weekend to update, but what APKs are giving the error?
Click to expand...
Click to collapse
3 APKs from the company I'm working for (not on PlayStore) 2 sideloaded apps, and a LADB signed sideloaded APK
For example you cut and CC cleaner keeps crashing all the time.
Same here. Almost every app not from Play Store keeps closing right on tap to start them.
Tried to sideload them per USB with full rights. Same.
My company apps that didn't come from the play store are opening without a problem
Thats Vers Strange, indeed.
Every sideloaded App, modded or Not does Not work
Thought it was me...this is bs!
What's the next step...start posting logs I assume?
It's not EVERY sideload for me but about 1 in 3 I'd say.
btw...I got an 'install failed' trying to install/flash the viper4android mod not realizing how old it was...now I'm seeing lotsa audio/sound related crap in logcat reader. If I AM 'currupt' somehow, will just a rom re-flash fix a magisk issue or do I need a full wipe?
Tia for any guidance offered!
Zaxx32 said:
Thought it was me...this is bs!
Click to expand...
Click to collapse
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
salamala893 said:
Me too but looks like is some security thing from Android 13. I really hope that somebody finds a workaround soon or I'll have to switch back to 12
Click to expand...
Click to collapse
12 won't work right on the 13 bootloader, and you can't downgrade the bootloader.
When I initially tested flashing only the 13 bootloader on my Pixel 6 Pro, while still running Android 12, it booted fine, I unlocked the phone, and all looked normal. But I didn't launch apps, especially Chrome, YouTube, and plenty of other things. If I had, I would have noticed problems that others have had since then. It was since found that certain/many kinds of apps will not work right running on Android 12 when you have the 13 bootloader installed.
I know this above is not what this thread is discussing, but since you mentioned it, I just wanted to point out that if you're on any Pixel 6/Pro/a with Android 13's bootloader flashed, you won't be able to use stock Android 12 on it. You'll be able to flash everything but the bootloader, boot it up, and unlock it, but before long you would discover problems that you wouldn't be able to work around and would effectively make your phone unuseable for many things that we take for granted.
By the way, hopefully you have the 13 bootloader flashed to both slots. Having the 13 bootloader on only one slot is a little dangerous.
Code:
adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img
Guys, but are you talking of sideloaded apps, or apps installed as apk?
gpvecchi said:
Guys, but are you talking of sideloaded apps, or apps installed as apk?
Click to expand...
Click to collapse
Apks