Been using my Cappy as a game device for close to a year since I got an SII. Tonight I tried to download an app via wireless and could not access Google Play. Tried using the SIM from the SII, but phone still gets network errors even with wifi on. Provisioned the phone, but still no go. I'm thinking a factory reset and starting from scratch might work, but I am running Andromeda 3 and am unsure what will happen if I do a reset. Will it restore to the factory version of Froyo? Will I lose root? I want to use the Cappy to fly my AR Drone 2, but I don't want to mess it up to do so. It flies great with the SII, but it would be nice to have the Cappy for it if possible. Incoming calls cause the copter to land and can be a pain. The Cappy doesn't even show up among my phones on Google Play. Don't remember deleting it, but until I can get some kind of network access I'm sunk. Did the APNs change for the Cappy in the past year? Shouldn't it be able to connect via wifi regardless? Thanks!
That's a strange problem... however you didn't specify what exactly isn't working. I know Google play doesn't work, but does anything else work over wifi? Either way, it is hard to give support when you are using a very outdated version of Android. I recommend you at least update to Gingerbread, or if you want, Jellybean.
You can also try clearing data for the play store. That's strange that it doesn't show up under your account. My old phone that I sold months ago is still there (twice), and there is no way to delete phones from the list. Are you sure you weren't using a different account?
I can't access either network, which is what is baffling me. I would think I should at least be able to access the internet via wifi, but even that won't work. It connects to my router fine, but beyond that nothing. As for my Play account, I remember several Cappys showing up there because I had 2 replacements within a month back when I first got it in 2010. Whether they dropped off from non-use or I deleted them somehow I don't remember. I just had my SII replaced under warranty last month and both are still there. My SII came with a new 4G SIM, which might not be compatible with the Cappy, but that doesn't explain not being able to connect via wifi. I'm stumped.
A factory data reset won't change your Rom, and you won't lose root. It might fix the problem.
Sent from my SGH-I897 using Tapatalk 2
Well, I managed to get online, but another issue cropped up. I logged into Google Play and can see all my installed apps. There are many needing updating, but when I try to do so I get a message that the app is not compatible with my device. Why would an already installed app see that an update is available and then not let me install it? I can also receive e-mail to my 2 configured e-mail accounts, but I can't send any e-mails through them. The same is true of both these accounts on my SII, so this issue may have nothing to do with the Cappy. I may just put a GB ROM on this thing, but it's been so long since I flashed anything that I have no idea which ROM to use or how to do it. I wonder if I copy over the APK for the app I want to run if it will work?
Miami_Son said:
Well, I managed to get online, but another issue cropped up. I logged into Google Play and can see all my installed apps. There are many needing updating, but when I try to do so I get a message that the app is not compatible with my device. Why would an already installed app see that an update is available and then not let me install it? I can also receive e-mail to my 2 configured e-mail accounts, but I can't send any e-mails through them. The same is true of both these accounts on my SII, so this issue may have nothing to do with the Cappy. I may just put a GB ROM on this thing, but it's been so long since I flashed anything that I have no idea which ROM to use or how to do it. I wonder if I copy over the APK for the app I want to run if it will work?
Click to expand...
Click to collapse
You'll need to flash KK4 with bootloaders (check the stickied in dev section). That will get you on stock GB, from there you can flash w/e ROM you want, I would suggest JB based. (AOKP and AOCP are my personal fav but you can look them up and choose one you see fit)
A lot of things changed since you were all over this forum But if you have TiBu, JB will optimize your apps so they should run fine (just remember to save your IMEI with TiBu otherwise they'll FC).
A fresh download of those apps tho will most likely be better. Just like after formatting a PC, it is better to fresh install your apps. And who knows, you might fall in love with your Cappy all over again
My phone was domestic unlocked. I was having a weird bug so I thought a software reinstall with Samsung Switch (PC) was a good idea...Worst decision I've made in 2016 so far! After the phone restarted, all Sprint apps were gone, and some others disabled like Facebook, Lookout and Instagram and the Hotspot and Tethering settings no longer appear. I went to a friend asking for some help: Various reinstalls with Odin yielded no results. GT idone needs root. A rooted phone is a no no for me as Banking apps and even Pokémon can't run. Factory resets and another "repair" with Samsung Switch are useless.
Where did the carrier apps went? Also, all the Sprint APNs no longer appear. Is there a NON ROOTED way of getting it back? We tried RTN, then reflashing with Odin with no results. I'm on the latest Marshmallow update (Came out yesterday)
Who is your carrier TELCEL?
Not sure what that is, actually I just look at your profile. What is your fw version?
Sent from my Portable
i have the same problem. some one please help. i miss my hotspot...# unlock sprint note 5 no root. 6.0.1 T_mobile is my Carrier
When I got the phone there wasn't all the apps on it. Now if I boot and clear the cache, re mount and reboot. It still has all the apps like bixby etc. even though during the setup I skip all that. WHat can I do. This is a US ATT locked phone which I could never send a mms or sms over 1mb.
I don't care if it is a ATT image. I don't need all the junk apps, but the advance messaging needs to work.
Quick Debloat ATT (SM-711U1)
No for non-rooted/stock/bootlocked phones This is my debloat list, simply copy paste into ADB. I still run some Google and Samsung services but this takes out all the carrier, Microsoft, Facebook and Samsung garbage that they lock into the...
forum.xda-developers.com
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.