Database Info

Androip P update

i am unable to opt in the beta program with my pixel 2. whenever i click the opt in button it shows ''we could not enroll your device at this time please try again later" .

Try it from your PC. I did it that way and it worked

dracushor87 said:
Try it from your PC. I did it that way and it worked
Click to expand...
Click to collapse
no it's not working for me i tried from pc too.

Is p beta stable enough for everyday use?

Rotten Ross said:
Is p beta stable enough for everyday use?
Click to expand...
Click to collapse
I believe so. I've been running since it dropped. I haven't had any force closes and the only happens you I've had was with Nova Launcher not showing apps in the drawer and vertical mode. Other than that it's been running good.

jfdebo779 said:
I believe so. I've been running since it dropped. I haven't had any force closes and the only happens you I've had was with Nova Launcher not showing apps in the drawer and vertical mode. Other than that it's been running good.
Click to expand...
Click to collapse
Not sure if you found the fix but you can use Nova Launcher app drawer if you go into settings and change the toggle for card mode to on.

jfdebo779 said:
I believe so. I've been running since it dropped. I haven't had any force closes and the only happens you I've had was with Nova Launcher not showing apps in the drawer and vertical mode. Other than that it's been running good.
Click to expand...
Click to collapse
Wonderful I don't use any 3rd party launchers so that won't be an issue for me. As this is a beta how often is there updates? Just curious

No problems with Smart Launcher

i got enrolled today morning.. running smoothly so far..

Anyone else really annoyed by the clock being on the left? Beside that it runs and feel great, just a left sides clock is a no for me, hopefully we can move it back in later builds

A few Android P questions/observations that someone might be able to answer as I've had a few minutes to actually use it:
- What is the "Actions Services" and Suggestions app?
- Is there a way to enable locations services but not use GPS to save battery? I only see on/off and when on it says it will use GPS, mobile data, and wi-fi.

Has any one noticed that album are in play music is messed up on P? Mine is all over the place since i updated to P.

mikeynavy1 said:
A few Android P questions/observations that someone might be able to answer as I've had a few minutes to actually use it:
- What is the "Actions Services" and Suggestions app?
- Is there a way to enable locations services but not use GPS to save battery? I only see on/off and when on it says it will use GPS, mobile data, and wi-fi.
Click to expand...
Click to collapse
There is no need now for the battery saving option in location. There is considerable improvement in battery and GPS does not take away any significant chunk of battery. I am not sure about Actions Services and Suggestions. However, I guess it must be the app for predictive AI based actions.

I'm unable to enroll into the Android P Beta program despite being on a Google Pixel 2. I'm encountering this message - "There are no eligible devices associated with this Google account". Please help!

yogesh_MCFC said:
I'm unable to enroll into the Android P Beta program despite being on a Google Pixel 2. I'm encountering this message - "There are no eligible devices associated with this Google account". Please help!
Click to expand...
Click to collapse
Flash the whole factory image for DP2 instead.

I have flashed an image before and I'm not sure how to do it as well. I wanted to opt in using the rootless option. Could you please help me out as to why I don't see my Pixel 2 listed on my devices on Google Play? TIA.

xFirefly93 said:
Flash the whole factory image for DP2 instead.
Click to expand...
Click to collapse
I think I've found a fix. I removed my google account from the "Accounts" section. Then restarted the phone. It prompted me on restart to sign-in again and I did. Then I went & synced the account, and then downloaded one random app onto my device. Then checked again in Play > Settings and it was there! Magic! Now I can view my device on Google Play & I'm able to download the Android P Beta. It's pretty good.

Anyone know of a way to roll back to 8.1 without losing data? I'm rooted with magisk
I tried installing via system image but the phone will stay on the loading G on boot.
If I try fastboot boot TWRP.img, data is encrypted.

marc.ientilucci said:
Anyone know of a way to roll back to 8.1 without losing data? I'm rooted with magisk
I tried installing via system image but the phone will stay on the loading G on boot.
If I try fastboot boot TWRP.img, data is encrypted.
Click to expand...
Click to collapse
I would recommend a clean flash of latest 8.1 firmware (May security patch) by flashing the factory image.

xFirefly93 said:
I would recommend a clean flash of latest 8.1 firmware (May security patch) by flashing the factory image.
Click to expand...
Click to collapse
This is what I tried.

Messages App does not work after Huawei P30 EMUI 10 Upgrade

Received the recent update for P30 in Canada, Build Number 10.0.0.178 (C792E8R1P3) for my ELE-L04. Looks like the Google Message app (v4.4.076 and v5.2.062) cannot send out messages after upgrade. All out going messages will return "Not Sent. Tap to try again." error. Receiving message is fine.
-Cleared Message app cache and storage. No differences
-Confirmed that the SMS Center number is correct.
-Tried with different SMS apps, as long as they are using system sms messages, does not work.
-Tried with different SIM cards from different carriers, all not working.
-Tried the same SIM card on other phones, it works.
Folks, Any idea?

Weird bugs after a major OS upgrade usually require a factory reset to fix, always recommended anyway

Called with Huawei technical support. Confirmed, it is a bug. Support Rep suggested rolling back to EMUI 9.1 or waiting for next update.
Can't Believe It!!!

jingking said:
Called with Huawei technical support. Confirmed, it is a bug. Support Rep suggested rolling back to EMUI 9.1 or waiting for next update.
Can't Believe It!!!
Click to expand...
Click to collapse
You're the first I've seen with this 'bug', and I don't have it, so factory reset and see if it's gone before rolling back, which will also wipe your phone either way

*Detection* said:
You're the first I've seen with this 'bug', and I don't have it, so factory reset and see if it's gone before rolling back, which will also wipe your phone either way
Click to expand...
Click to collapse
Welcome to Canada, where you always get the delayed update, weird bugs, disabled huawei id and always offline themes app.
The tech support said I'm not the only one. In case someone can't perform this fundamental function, do not doubt yourself.

Looks like more people have the same issue.
https://www.reddit.com/r/Huawei/comments/er21u5/canada_emui_10_update_text_messaging_issue/

have you tried to uninstall the app and install it again?

DallasCZ said:
have you tried to uninstall the app and install it again?
Click to expand...
Click to collapse
I can only uninstall the message app update and back to the default 4.4 version. So the hiSuite method does not work for me.
However, just received Google messages app update v5.4.084. Looks like it is working now :good:

I've had this issue twice now, definitely caused by uninstalling apps. This time I discovered that uninstalling the Huawei Backup app is what broke texting. Simply reinstalled using the Play Store and texting is working, instantly.

Samsung watch stopped working properly after EMUI12 update?

Does anyone else own a Samsung watch?
Both myself and my wife have Samsung watches (she Galaxy watch active and me Galaxy watch 1) and both have P40 Pro with GMS, and GSF is frozen (no play store so we use aurora and everything works perfectly).
Since EMUI12 update everything is working fine but these watches keep losing bluetooth connection to the phone, therefore will not show notifications and the health data is sometimes not syncing.
We have tried resetting both watches, uninstalling all Samsung apps and reinstalling and then re-pairing watches and still the same problem occurs.
I tried to downgrade to older version of Samsung wearable apk but it was impossible, the app just wants to update itself right away (along with the watch plugin apks).
So the culprit is either EMUI12, android 11, or the wearable apk itself.
Would be good to know for sure as Samsung will not support these devices.
Ps. Both wearable app and the plugin app have app launch/battery optimization disabled.

I'm having the same issue. I'm either going to sell the phone or downgrading my os

I'm thinking it might be Bluetooth in general which is having issues. It seems to also be disconnecting from my car.
I've done a network settings reset to no avail.
Wonder if it's worth the time and effort wiping, downgrading all the way to emui 10 and then reinstalling GMS etc

My pebble and Huawei watch keep their Bluetooth connection without issues. Only the galaxy watch is disconnecting. My Bluetooth speaker and car also work fine

Same issue. Galaxy Watch keeps disconnecting/won't sync after my Huawei Mate 20 X updated to EMUI 12. Has anyone found a solution? I will have to ditch the phone (I love the big screen) or the watch. If I keep the phone I guess I'll pick up a Huawei watch.

frcraig said:
Same issue. Galaxy Watch keeps disconnecting/won't sync after my Huawei Mate 20 X updated to EMUI 12. Has anyone found a solution? I will have to ditch the phone (I love the big screen) or the watch. If I keep the phone I guess I'll pick up a Huawei watch.
Click to expand...
Click to collapse
Wow that's surprising that even Huawei devices with Google services built in are having the issue.
I ended up "upgrading" to an Oppo Find X5 Pro.
Still prefer the Huawei camera though

I found a solution. I installed the Huawei HiSuite software on my desktop computer, plugged my phone into a usb port, and used HiSuite to downgrade my phone's OS from EMUI 12 to EMUI 11. Now my watch works fine again.

frcraig said:
I found a solution. I installed the Huawei HiSuite software on my desktop computer, plugged my phone into a usb port, and used HiSuite to downgrade my phone's OS from EMUI 12 to EMUI 11. Now my watch works fine again.
Click to expand...
Click to collapse
I'm having the same issue with a P30 Pro updateted to EMUI12, my Gear S3 won't show WA notifications and often it's disconnected from the phone
Will the downgrade from EMUI12 to EMUI11 delete all the phone data?

ivan69_mi said:
I'm having the same issue with a P30 Pro updateted to EMUI12, my Gear S3 won't show WA notifications and often it's disconnected from the phone
Will the downgrade from EMUI12 to EMUI11 delete all the phone data?
Click to expand...
Click to collapse
yes

Despite the downgrade to emui 11 the galaxy wearable app doesn't work... I can't restore the watch backup, I can't update the apps,, I can't install new apps.
Sometimes the processes start, but they stop after a while like the BT connection stops... Also the link to Samsung account is unstable and asks for the password many times...

ivan69_mi said:
Despite the downgrade to emui 11 the galaxy wearable app doesn't work... I can't restore the watch backup, I can't update the apps,, I can't install new apps.
Sometimes the processes start, but they stop after a while like the BT connection stops... Also the link to Samsung account is unstable and asks for the password many times...
Click to expand...
Click to collapse
I have the same problem.

hetzelfde probleem hier na het installeren van de laatste update

sebulba1551 said:
I have the same problem.
Click to expand...
Click to collapse
Just to be sure, I've linked the watch to the company phone, a Samsung A50: everything worked without issues, so it's definitely a problem related to the phone...
After 3 days spent on it, I've decided to leave it linked to the Samsung and in case I'll purchase a different watch...

Yes, Huawei disappointed me,again

After updating tonight on my P30 pro, the watch works again.

So you are happy again !!!
Don't be discouraged too easily ...

Watch: Samsung Galaxy.
Smartphone: Huawei Nova 5T.
Rolled back to EMUI 11.
Couldn't restore watch back-up, samsung health didn't work.
Reinstalled galaxy wear, the plug-in and now seems to be ok, except whatsapp notifications.
For samsung health installed an older version, logged in and after that updated.

přešel jsem na telefon galaxy s9+ , Huawei stojí za hovno.

sebulba1551 said:
After updating tonight on my P30 pro, the watch works again.
Click to expand...
Click to collapse
Hi, out of curiosity, what update fixed it (huawei OS or Samsung app)?

I've had this same issue since Emui 12 on my P30. I'm not going to do anything yet, and hold out in hope that it'll get sorted with some update.
I've put this problem on a Huawei forum and a few people have said they've got tge same problem.

EMUI 12.0.0.228 update Google Play Services to safe version?

I am on EMUI12 (C432) and want to know whether or not it is safe to update google play services.
I installed it over a year ago using a method I cannot remember where I found, and currently have GSF frozen with icebox and the phone has been working perfectly (inc notifications) ever since. I just use Aurora to install/update apps (a bit of a pain having to do it manually but liveable).
Since going to EMUI/Android11 I am having some issues with Samsung Galaxy Wareable app being flakey with syncing with my Galaxy Watch, and also having recently got a car with Android Auto Wireless, I am having some issues with it too. On the latest version of Android Auto. Sometimes wireless works and sometimes it doesn't (the car has bluetooth connection which prompts phone to connect to the AA SSID but sometimes it just joins the bluetooth and then drops..
Anyway...
Currently on GPS version 20.47.13
Wondering if it is possible to update to a later version of play services without breaking notifications without first downgrading to EMUI10 -> EMUI11?
Thanks!

maximum 21.24.56.
It is possible to ruin all when you de-freeze GSF (play protect errors, auto-upgrade of Play Services, etc).

Thanks for your quick reply.
Can I go ahead and update the APK to 21.24.56 without defrosting GSF?

You can try. I dont remeber if it will counts if the GFS is frozen. In my method I have to have GFS not frozen. You are on other method.

Okay that didn't work
Downloaded it from apkmirror. It installed OK but now all google apps won't open.
Tried to reinstall old version, same thing.
Looks like I am going to have to downgrade (which I assume means wiping) and then follow your method.

mcall_r said:
Okay that didn't work
Downloaded it from apkmirror. It installed OK but now all google apps won't open.
Tried to reinstall old version, same thing.
Looks like I am going to have to downgrade (which I assume means wiping) and then follow your method.
Click to expand...
Click to collapse
Don't downgrade. We will talk after 2 hours

General Unable To Connect Watch 4 [Samsung Android 13/OneUI 5.0]

Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show

73sydney said:
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
Click to expand...
Click to collapse
check lot of iPhone problems..
btw, Oneplus had problem with connection GW4 after upgrade from 12 to 12.1. only one solution was reset GW. now on 1+ A13 doesnt work Google Wallet/Payments with cloned apps enabled.. Samsung is better competetion..

I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually

HyperChick said:
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
Click to expand...
Click to collapse
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too

Try updating google play services to the latest beta (apkmirror). Solved my issue

shaharofir said:
Try updating google play services to the latest beta (apkmirror). Solved my issue
Click to expand...
Click to collapse
tried latest beta (22.45.15 (190400-488417729) beta (190400))
absolutely no difference

73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some

DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Cheers, but just for reference, im quite involved in Magisk circles and hiding root (have modules to assist in this)...im usually helping others hide stuff or deal with root issues.....so i know what im doing
Also the same setup i use had no such issues in Android 12, its very much a Samsung making life harder for everyone, on purpose, because theyre basically acting like the new Apple and want to lock everything down. Ive decided to go back to Pixel, off to buy one soon, Samsung has gotten their last $ from me, they can go hang...

73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.

JazonX said:
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
Click to expand...
Click to collapse
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately

73sydney said:
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
Click to expand...
Click to collapse
Thank you for this.
I will use this If I ever lose the R/W ability in my device.
For now I have R/W - so I wrote to the file directly.

Heres what i found out......
TLDNR version:
Dont backup and restore Samsung Wearables Apps - even if you previously were able to do this for eons, like i had. I have used Migrate to backup and restore apps and app data for eons (important to note i always left the app data (middle column in Migrate GUI) disabled for Samsung Wearables apps. Always let the Watch be detected as part of device setup on stock ROM OR install the Galaxy Wearable live from the Play Store (after clearing Google Play Services/Store sata and achieving Integrity check if you are rooting your device)
Longer version:
The other night i finally got time to flash back to A12, ran my normal procedure, rooted, USNF...clear data on GP/GS and then connected Watch...only it still wouldnt connect, even though the app restore was taken from a clearly working A12 (just before i flashed A13)
So i had to alter my procedure in leaving out the backed up Samsung wearables apps during restore, and then let the installed ROM detect the presence of the Watch 4 AFTER i have rooted, USNF...clear data on GP/GS and then connect Watch...
Looks a little like this:
* Flash ROM via ODIN (including my special AIO.zip to install TWRP, format data, decrypt data etc)
* Watch 4 WAS powered on and waiting to be detected when setup wizard looks for it towards end of setup - ignored/cancelled setup this time - going to do the root, USNF module and integrity check thing firsties
* Finish setup
* Reboot to TWRP recovery
* Root with Magisk (renamed to .zip) via TWRP
* Reboot
* Install Magisk App to complete install (you can just use the stub installer which will download the full app, but im used to doing it this way)
* Reboot
* Install USNF (Mod) and put device in airplane mode clear data on Google Play Store/Services to pass Integrity Check
* Reboot
* Take device off airplane mode....
* Open Google Play and confirm its certified (just needs to show version (Device Is Certified of course comes later - as along as it doesnt say Device Is Not Certified, all is well)
* Watch 4 automatically detected (Wearable Manager Installer - this is i think obviously a stub installer to detect and call the latest Galaxy Wearable from the Play Store) and Watch setup commences
* Watch setup completes
* Restore remaining apps via Migrate (leaving wearables unselected - will leave them unchecked on next backup)
NOTE: you must do (and ALWAYS have had to do) the Watch connection AFTER clearing data on GP/GS to get Integrity to pass. If you do that data clear after you connect the Watch it will sever the connection, as it tied to GS
Noter 2: Ultimately i decided id had enough of Samsung tomfudgery, and i bought a Pixel 6 Pro and departed for sanity back to Pixel Lyfe.....

My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.

gettinwicked said:
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
Click to expand...
Click to collapse
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again

73sydney said:
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
Click to expand...
Click to collapse
Yeah, not rooted. I'll give the clearing play store and services data a whirl. I also have a conversation going with Samsung support on Twitter. Thanks for replying!

DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Root has nothing to do with, the Galaxy Wearable app doesnt stop working if your knox has been tripped.
Ive had the last 3 Galaxy watches and all my phones have been rooted with custom roms, any issues ive had connecting/pairing were user error.