-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 13 - Crashes on start #56
Comments
Can confirm this stopped working for me after upgrading to Android 13. |
I can't even start it on my redmi note 10 with custom lineage os but it runs on my pixel 6 pro that runs on calyx os, both android phone versions are Android 13 |
FYI, a similar issue got fixed at warren-bank/Android-Mock-Location#14 for my Pixel 6a with GrapheneOS. |
Hi, all. To quickly summarize the "dumb" workaround (as it's now affectionately known) mentioned by @schklom ...
Also, I should probably mention.. |
@TimoGoetze I have made the change that @warren-bank is proposing. Can you test if this APK is working for you? |
@mcastillof I'd offer to test your build myself, but I'm in the same boat. I don't have a device new enough to reproduce or test this bug. Consequently, I'm also not sure what the effect of this workaround actually is. It's either:
I suppose that either option is better than a fatal error.. crash. |
@warren-bank I wonder if a Pixel 6 device with Android 13 (arm64-v8a or x86) emulated using Android Studio could be useful to test the behavior. |
I don't know. I was actually wondering whether android-x86 had a nighly release to test in VirtualBox, but the project hasn't been active in quite a long time. Bliss OS is also some variation of Android x86, but its releases are based on versions of AOSP that are nowhere near new enough. |
I went ahead and tried a Pixel 6 pro with Android 13 (arm64-v8a) in Android Emulator within Android Studio. My host machine has an x86_64 architecture.
I will try an x86_64 image now. Hope it works this time. |
Yeah, definitely let me know the outcome. The x86_64 image will run.. dunno whether the bug will occur. Curious to find out. I'm actually reading this.. and am tempted to try the same methodology to run the newest Pixel factory image.. which we know is problematic. Though, now that you mention it, the OP might have been unable to run his image because he was also using an arm64 image. |
Now I'm a bit confused. I only use LineageOS, and I'm not used to that Android/Pixel stuff. The images found in Pixel factory image aren't the same as the images that can be downloaded with in Android Emulator in Android Studio? Pixel phones come with a different Android version? What's the name of the ROM? |
since I don't use it.. I'm not an expert.. but my understanding of the emulator that comes with Android Studio is that is uses the qemu emulator and the AVD (android virtual device) images that it downloads directly from google are very much like a factory image.. in that it's a zip file containing individual images for each partition. as to which version.. or how old the images are.. I'm not sure.. does the AVD manager provide details about each image? ..it's not in front of me at the moment. |
It booted now (x86_64 image) AVD manager only seems to say that it is an API 33:
|
In the followin image, I downloaded Tiramisu (number 1 red), It showed me the url of the download, but I can't get access to it now, |
hmm.. I googled the build number.. but it didn't pull anything up. going by the date of the last security update.. it should be pretty recent. what happens when you run the last stable release of your app (that users are seeing this issue)? |
Your fix seems to work fine, as I don't see that it crashes. I will try now without your fix. |
the response for the URL of that system image includes the header:
..but that can't be right |
pins and needles.. 😃 Pay for the whole seat, but you'll only need.. the edge! |
I couldn't reproduce the problem with the old code. And new problem arises in FakeTraveler when using Android 13,
which is solved by changing this line to
I believe that your code already address this FLAG_IMMUTABLE or FLAG_MUTABLE exception. So, we are the begging again. We need a tester which had the problem. |
Yeah.. there was an issue about that (missing PendingIntent flag) error in one of my apps a few months ago.. and I pushed an update across all of them at the same time. Easy enough to fix.. just annoying how every new version of Android breaks user space and requires updates to keep existing functionality working.. big pet peeve. Anyway, as you said.. shame that the emulator wasn't any help. But, huge thanks for bothering to test it! Would've been really nice to run this error through the debugger and be able to determine whether this workaround is actually fixing initialization of the provider.. or simply catching the exception and allowing the app to ignore that it failed. update: I just learned something new.. about the push toward running generic system images. I don't think I have a phone that supports this.. and even if I did, it still looks too risky to try installing an update manually.. but it's great to see.. because it's so very much needed.. and clearly the future for Android updatability. Links: 1, 2, 3, 4, and 5. Related links: 1, 2, and 3. |
I think the same.
We had to give it a try to the emulator. Have a good day/night @warren-bank warren-bank :) |
If somebody is still having this issue with FakeTraveler v1.9.1, which was released a few days ago in F-Droid, then please try if this APK is working for you and report it here. |
Tried the one from F-Droid. First just did not work. Then Crashed again. I cannot try from coders.cl. `` java.lang.IllegalStateException |
pixel 6. latest updates. |
Hello @TimoGoetze
Did you experienced any problem with the download of the APK from c.coders.cl server? I test the download and it worked without any problem. if you prefer I can upload the test APK here in Github. |
@TimoGoetze I have pushed this beta release to F-Droid. It should be available soon in F-Droid's app. As this is a beta release, you will have to manually install it from the versions dropdown. If you don't want to wait, you can download an unsigned apk built automatically by GitLab CI at the bottom of the Merge Request. Please, test the app and come back with feedback. |
@mcastillof It seems the build failed at F-Droid. |
@UnlimitedCookies @mcastillof serviceIntent = new Intent(context, ApplyMockBroadcastReceiver.class);
int flags = PendingIntent.FLAG_CANCEL_CURRENT;
if (Build.VERSION.SDK_INT >= 23)
flags |= PendingIntent.FLAG_IMMUTABLE;
pendingIntent = PendingIntent.getBroadcast(context, SCHEDULE_REQUEST_CODE, serviceIntent, flags); |
As noted, unfortunately F-droid build of
Unfortunately, that I've ended up forking and having GitHub compile it for me. It wasn't easy as usual, though, as Luckily, the resulting
I've tested the latest master 1878d70 on Android 13 (Samsung Galaxy S23+) and it no longer crashes there and works just fine! (if others want to try too, the Can we have an release of |
Sorry I haven't had the time to take care of FakeTraveler. I will work on the project this days to be sure it works on f-droid.. |
Describe the bug
A clear and concise description of what the bug is.
Information:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
works and doesnt crash
Screenshots
If applicable, add screenshots to help explain your problem.
Logcat
If the app is crashing, a logcat of the error could be very helpful.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: