I enrolled for the Android O Beta a few months ago and installed it on my Pixel. I decided to leave, so I went to https://www.google.com/android/beta only to find that "there are no eligible devices associated with this Google account." I'm signed into the same account on both the phone and the site. I tried basic things like signing out and in, running app updates, and I even reset and re-setup the phone. Nothing worked, so I sideloaded the latest stable 7.x release. It installed fine, but upon setting it up, I received the beta notification telling me to update. I checked the site again, and the phone still isn't listed.
Has anyone encountered anything like this?
I had this exact problem multiple times trying to join and unjoin the beta. Even contacted Google and they couldn't help at all.
I actually had to make a new email, remove the account on the phone and sign in with the new email. At that point the page acknowledges that I have a " eligible device ". I'll join or unenroll and when it's done I sign back into my device.
Another problem (more critical in my opinion) is when I get the message that my devices are not eligible, I also can't use the web Android device manager. For example, I wouldn't be able to locate my device, make it ring, or lock and erase it.
noidea24 said:
I had this exact problem multiple times trying to join and unjoin the beta. Even contacted Google and they couldn't help at all.
I actually had to make a new email, remove the account on the phone and sign in with the new email. At that point the page acknowledges that I have a " eligible device ". I'll join or unenroll and when it's done I sign back into my device.
Another problem (more critical in my opinion) is when I get the message that my devices are not eligible, I also can't use the web Android device manager. For example, I wouldn't be able to locate my device, make it ring, or lock and erase it.
Click to expand...
Click to collapse
Just download stock image from Google and use adb to flash all
Sometimes I don't want to backup and restore all my data.
noidea24 said:
Sometimes I don't want to backup and restore all my data.
Click to expand...
Click to collapse
I just got a used XL with the persistent beta notice that wouldn't go away, but installing the 8.1 OTA finally made it go away.
Related
Hi there XDA,
Proud to be a member of the One X team, I have searched for a resoloution to this issue however I cannot find a single thing. Basically i ctreated a Google account specifically for this phone, as I don't use my old Google account and I wanted to start fresh. After logging in to it and setting up all the other accounts on the phone, I decided to install apps. I went to the online Play store however as the phone hadn't completed its initial sync it wasn't appearing online, so I started to download from the PlayStore on the phone. That's when I noticed that on trying to install UPDATES for pre-installed applications it said 'Your order is processing. Your item will be available in a few minutes' Well after a few minutes my application will not update and this error will not stop.
I did a factory reset, and set the phone up with my old Google account however I didn't set anything else up, just my old Google account. Then I tried to update apps through the PlayStore and it worked! I put the issues down to the new Google account and so quickly created another. I did a factory reset and set the phone up with ONLY this new Google account. The updates WORKED.
So then I did another reset and set the phone up with all the accounts ect and this new google account. The phone will not install updates and is giving me the error again also the phone is appearing online, however it won't install any apps, it says the request has been sent when i click install online however the app never installs on my phone. If I go to the PlayStore on my phone and install a not-installed app it will work though.
Please help somebody thankyou!
When I got my Note 4, I have been unable to download my paid email app (Enhanced Email) from Google Play.
It tries, but gets a 505 error part way through. Research shows that this apparently happens with the update to Lollipop on some phones. My old phone is able to use the email program and update from the play store just fine after Lollipop - it is apparently just the initial download that gets stuck.
The developer says I need to remove the stock email app first, then try again. If that doesn't work the next plan is to somehow install it with ADB/ABD(?). Others have made this work, so I am willing to try it. I can see this is going to be a process, but I need help with the first step - removing the original email app. Without rooting the phone, how do I do that?
Hi,
I'm fairly new to the Android rooting community, that said I have been jailbroken on iOS since the days of 1.1.2 and have rooting experience with KitKat. I have a Nexus 5X and after rooting, the phone worked fine. I installed TWRP 3.0.2 and Xposed framework, but for some reason I was unable to get Xposed to work. After a week of no issues with the phone, the Play Store stopped working, and Hangouts failed to send messages. I could send SMS via Messenger app and would receive the replies in Hangouts. I did a factory reset, and now I am unable to do anything. I cannot login to my google account, use the play store. Whenever I do anything I get a message that says:
Couldn't sign in
There was a problem communicating with the google servers.
Try again later.
I've searched the web and the forums for issues like this and can't find anything. I would really appreciate the help. It may be a simple mistake that I made as I am not fully aware of how the Android filesystem works.
Also when I check for updates, it stays that the last time it checked was: 12/31/1969. My clock is set correctly and I am connected to Wifi.
Wow!!! What ROM and gapps are you running?
I haven't seen this since my LG G2 a couple years ago. Hop in date and time in your settings and turn off automatic date and time and manually add it... Unless you're saying its right there.
I would try going to TWRP and wiping.
Wipe/advanced and then check every box except for internal storage. Then hit home and go back to install, choose ROM then gapps then vendor.
Xposed has to be installed as a zip from recovery before you can install/use the apk (in 6.0.1 anyway-use arm64).
jbburf said:
Hi,
I'm fairly new to the Android rooting community, that said I have been jailbroken on iOS since the days of 1.1.2 and have rooting experience with KitKat. I have a Nexus 5X and after rooting, the phone worked fine. I installed TWRP 3.0.2 and Xposed framework, but for some reason I was unable to get Xposed to work. After a week of no issues with the phone, the Play Store stopped working, and Hangouts failed to send messages. I could send SMS via Messenger app and would receive the replies in Hangouts. I did a factory reset, and now I am unable to do anything. I cannot login to my google account, use the play store. Whenever I do anything I get a message that says:
Couldn't sign in
There was a problem communicating with the google servers.
Try again later.
I've searched the web and the forums for issues like this and can't find anything. I would really appreciate the help. It may be a simple mistake that I made as I am not fully aware of how the Android filesystem works.
Also when I check for updates, it stays that the last time it checked was: 12/31/1969. My clock is set correctly and I am connected to Wifi.
Click to expand...
Click to collapse
What happens if you try on mobile data?
Darke5tShad0w said:
What happens if you try on mobile data?
Click to expand...
Click to collapse
Unfortunately I can't use data either since I am unable to activate my project Fi service (since I am not able to make any data connection).
I've resolved this by wiping and installing PureNexus. No idea what was going on with the factory ROM though.
jbburf said:
Unfortunately I can't use data either since I am unable to activate my project Fi service (since I am not able to make any data connection).
I've resolved this by wiping and installing PureNexus. No idea what was going on with the factory ROM though.
Click to expand...
Click to collapse
Any chance you changed your Google account password around the time you reset the phone? I think there is some lockout mechanism if they detect password change then factory reset. I believe it is something like 72hour hold.
Hi all,
I've tried to update my chrome application (the pre-installed on my Global Poco F3 which is under MIUI Global 12.02 stable global) I have tried multiple times to update the Chrome app from the Google Play Store with no success to this day.
I've investigated using adb logcat and I've seen a specific error trigger itself :
4-10 00:34:14.008 17140 17170 E Finsky : [993] tvh.apply(44): IQ::GROUP_INSTALL: Error validating group. Rejecting requests: [com.google.android.trichromelibrary, com.android.chrome]
04-10 00:34:14.008 17140 17170 E Finsky : com.google.android.finsky.installqueue.impl.preprocessor.GroupInstallValidator$InvalidGroupException: GROUP_INSTALL: Group com.google.android.trichromelibrary and com.google.android.trichromelibrary have overlapping module [com.google.android.trichromelibrary, com.android.chrome]
Obfuscated long Java backtrace...
Click to expand...
Click to collapse
I have tried to update chrome on a Redmi Note 8 pro without success as well. However, under LOS (Lineage OS 18.1) another phone has successfully updated the Chrome app, meaning this issue is probably not due to a weird Google Play Store bug but most likely due to MIUI 12.
Anyone has encountered this issue ? And is there any way we could work around this ? (instead of waiting for a potential fix in MIUI 12.5)
Thanks for any help on this matter, I can provide the whole backtrace if anyone want to see it but I doubt it would help anyway since she looks pretty obfuscated to me (the only thing I could understand was some execute function being called but all the classes names have been randomized and most functions call names too).
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
UPD: Or you can download right now from apkmirror.com, if you want
Xoby said:
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
Click to expand...
Click to collapse
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
AkechiShiro said:
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
Click to expand...
Click to collapse
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
I cannot understand the mistake. I updated Chrome to the latest version 3 days ago.
Xoby said:
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
Click to expand...
Click to collapse
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
AkechiShiro said:
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
Click to expand...
Click to collapse
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Fabio Bertelli said:
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Click to expand...
Click to collapse
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
AkechiShiro said:
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
Click to expand...
Click to collapse
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Fabio Bertelli said:
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Click to expand...
Click to collapse
Good thing you figure it out, and also thanks for explaining how for others who will face this issue, maybe sometimes the notification disappears for some reason or the configuration doesn't finish successfully and this issue happens.
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