Related
For those who may find this useful...
I added the PTT service on my phone not thinking that my device may not yet be compatible with the app from AT&T. I found out the hard way but figured out how to get it going on my device.
1. After adding the service online I got a text a half hour later that it was active on the account.
2. I then rooted my Note 2 on the latest stock 4.3 rom.
3. Downloaded the app: Device Spoofer from the Play Store.
4. Backed up the device's current information in Device Spoofer
5. Changed the device's ID to that of the Galaxy S4 (i.e. sgh-i337)
6. Restart the device.
7.Launch At&t EPTT app and activate.
8. Once activated you can run spoofer again and restore your device's I'D and restart and the app will still work.
Just guessing but I would think this should work on the Note 3 as well. Everyone uses this at work so I thought it was worth looking into.
***EDIT: I used the Helium app to backup the At&t EPTT app and data to my Google Drive account and restored it on my At&t Note 3 and can confirm it works. I did not root my note 3 due to the Knox issues discussed here on XDA, so if anyone has another device that is rooted this is an easy way to get the PTT app working on a non rooted one.***
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
THANKS!!
This is awesome. Was thinking about trying this with a Nexus 5. Currently stuck with a Rugby Pro and it is BRUTAL. Glad to know there's a way around AT&T's BS.
ercave1 said:
For those who may find this useful...
I added the PTT service on my phone not thinking that my device may not yet be compatible with the app from AT&T. I found out the hard way but figured out how to get it going on my device.
1. After adding the service online I got a text a half hour later that it was active on the account.
2. I then rooted my Note 2 on the latest stock 4.3 rom.
3. Downloaded the app: Device Spoofer from the Play Store.
4. Backed up the device's current information in Device Spoofer
5. Changed the device's ID to that of the Galaxy S4 (i.e. sgh-i337)
6. Restart the device.
7.Launch At&t EPTT app and activate.
8. Once activated you can run spoofer again and restore your device's I'D and restart and the app will still work.
Just guessing but I would think this should work on the Note 3 as well. Everyone uses this at work so I thought it was worth looking into.
***EDIT: I used the Helium app to backup the At&t EPTT app and data to my Google Drive account and restored it on my At&t Note 3 and can confirm it works. I did not root my note 3 due to the Knox issues discussed here on XDA, so if anyone has another device that is rooted this is an easy way to get the PTT app working on a non rooted one.***
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a rooted S3 and used helium to backup and transfer to my new S5 and it doesn't work. It tries to activate and then fails saying i dont have a supported device. I must be doing something wrong?
EDIT: Rooted my S5 and tried your first method and still no dice. Hmmmm this is interesting. If I cant get this figured out I guess I will have to return the phone. Are you using your old sim or the new one that comes with the phone?
ProStreetCamaro said:
I have a rooted S3 and used helium to backup and transfer to my new S5 and it doesn't work. It tries to activate and then fails saying i dont have a supported device. I must be doing something wrong?
EDIT: Rooted my S5 and tried your first method and still no dice. Hmmmm this is interesting. If I cant get this figured out I guess I will have to return the phone. Are you using your old sim or the new one that comes with the phone?
Click to expand...
Click to collapse
It seems that my original method no longer works since they updated the PTT app. I was able to Spoof My Note 1's (sold my Note 2) device ID to that of an S4 and the app activates that way. I was hoping I could back it up again with Helium and Restore to my Note 3 but it tries to reactivate on the Note 3 and detects the current device ID. So at this point I believe my only option is to root my Note 3, spoof the device ID, and activate. Not something I want to do.
I also found that if I enable airplane mode then enable WIFI and you launch the app, after a minute or two it asks if you want to try to activate over WIFI, and then asks to enter an code provided by an administrator. I wonder if ATT would be willing to provide a code to users that already have the feature on the account and want to try the app on a newer device...It's a shot in the dark but couldn't hurt to ask.
EDIT: By ID, I mean model number.
ercave1 said:
It seems that my original method no longer works since they updated the PTT app. I was able to Spoof My Note 1's (sold my Note 2) device ID to that of an S4 and the app activates that way. I was hoping I could back it up again with Helium and Restore to my Note 3 but it tries to reactivate on the Note 3 and detects the current device ID. So at this point I believe my only option is to root my Note 3, spoof the device ID, and activate. Not something I want to do.
I also found that if I enable airplane mode then enable WIFI and you launch the app, after a minute or two it asks if you want to try to activate over WIFI, and then asks to enter an code provided by an administrator. I wonder if ATT would be willing to provide a code to users that already have the feature on the account and want to try the app on a newer device...It's a shot in the dark but couldn't hurt to ask.
EDIT: By ID, I mean model number.
Click to expand...
Click to collapse
I got it working. The app now looks at the phones model number. I simply changed the model number to that of an S4. It activated right away once i did that. When I go to about device my S5 shows as SAMSUNG-SGH-I337 which is an S4. :good:
Changing the ID appears to screw up NFC until you change it back to the original, at least on my Note 3. Changing back to the original kills the activation. Att seems to have caught on because the app, even the older version now activates on reboot.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
ercave1 said:
Changing the ID appears to screw up NFC until you change it back to the original, at least on my Note 3. Changing back to the original kills the activation. Att seems to have caught on because the app, even the older version now activates on reboot.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm interesting on the NFC. I dont use it so im not sure how the S5 reacts to the change. The eptt app has been working flawless though and the manager at the store called corporate and they told him they would be updating the app in the near future to support the S5.
Hello, I have a galaxy s3 from sprint SPH-L710. The phone will not take the last 4.4 update, I believe it’s due to the files don’t match because of the root and the sprint hot spot mod. But I noticed that my google play is not showing the right phone. It’s showing a GT-I9500 and my google security devices and activity are showing the galaxy s3 SPH-L710 which is correct, but when I click on find my device it shows a GT-I9500 which I never had, and it can’t find the device. Also under google security devices it is showing a galaxy s4 which I never had last synced 12/26/14 model GT-I9500 and I do not have the option to remove it. Also showing a galaxy s2 GT-I9100 last synced 12/13/14. I have not used my galaxy s2 in years, plus its deactivated and it’s a SPH-D710, it’s also showing a Samsung galaxy note 2 last synced 12/13/14 model GT-N7100 which I never owned or used.
anybody else seeing phantom devices in their security google information?
https://security.google.com/
I’m not sure what could be causing this? I only have done two changes on the phone, the root and the sprint hotspot mod. Whats the best way to proceed? remove both changes then do the update and see if those phantom devices go away? then root back the phone and put the sprint hot spot mod back? I cant lose phone or data. I am not phone hacking and moding guru. I’ve done it before with the oden tool but that is probably once or twice every two years. So as much walk through help will be appreciated.
PHONE INFO: under about device, model SPH-L710, android ver 4.3, baseband ver L710VPUCMK3, kernel ver 3.0.31-G1AC4B4-DIRTY [email protected] #1 SUN NOV 24, 12.30.47 PST 2013, build JSS15J.L710VPUCMK3, se for android status PERMISSIVE, hardware ver L710.14
Anyone getting issues with setting up numbersync following the update? I keep getting a backend error.
Sent from my SAMSUNG-SM-N920A using Tapatalk
I work for ATT (and use a Note 5 ATT variant with number sync to an Gear s2). We have noticed some issues getting number sync functioning on our phone after the MM update. Some things to check to help ( I did get mine working after a few headaches):
- Does your phone line have the cloud message backup and sync feature on it? (It's required for number sync to work)
- Are you using a unique MyAtt account, the way number sync works, it requires a separate MyATT account using a separate primary phone number for each device trying to setup number sync.
- Are both the watch and the phone fully updated (both firmware and gear manager need to be on the latest version)
If all else fails, factory reset the watch and then attempt to connect number sync again. If that fails its gonna end up being a factory reset on the phone, but only use that as a last resort.
Unfortunately customer care is very undereducated on the numbersync feature. If your in an area that has a device support center you may catch an employee that knows their stuff - but even that's rare. Feel free to PM me if there's anything else I can to to help out.
neopolotin75 said:
Anyone getting issues with setting up numbersync following the update? I keep getting a backend error.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Try there : https://addressbook.att.net
You can sync from your pc.
Sent from my SAMSUNG-SM-G935A using XDA Premium HD app
DTR204 said:
I work for ATT (and use a Note 5 ATT variant with number sync to an Gear s2). We have noticed some issues getting number sync functioning on our phone after the MM update. Some things to check to help ( I did get mine working after a few headaches):
- Does your phone line have the cloud message backup and sync feature on it? (It's required for number sync to work)
- Are you using a unique MyAtt account, the way number sync works, it requires a separate MyATT account using a separate primary phone number for each device trying to setup number sync.
- Are both the watch and the phone fully updated (both firmware and gear manager need to be on the latest version)
If all else fails, factory reset the watch and then attempt to connect number sync again. If that fails its gonna end up being a factory reset on the phone, but only use that as a last resort.
Unfortunately customer care is very undereducated on the numbersync feature. If your in an area that has a device support center you may catch an employee that knows their stuff - but even that's rare. Feel free to PM me if there's anything else I can to to help out.
Click to expand...
Click to collapse
Sorry I missed this....it started working but I still have issues where if I get too far from my phone my watch numbersync sign disappears and it doesn't work.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Hi all, I had just bought a new xiaomi mi 9 phone and I installed galaxy wearble application, galaxy watch plugin and Samsung accessory service, and gave them all permissions, but I can't log in my Samsung account to restore my watch backup or install new faces from store, when trying it gives my a blanc white popup instead of signing in screen, what to do?
Same thing is happening to me on a Pixel 3. Did you manage to fix it at all?
SdkDel said:
Same thing is happening to me on a Pixel 3. Did you manage to fix it at all?
Click to expand...
Click to collapse
No, I tried my best, looked in all settings and gave all permissions, the strange thing is that samsung pay and Samsung health can sign in normally but galaxy wearable and galaxy store can't, I hope someone can help.
MHH76 said:
No, I tried my best, looked in all settings and gave all permissions, the strange thing is that samsung pay and Samsung health can sign in normally but galaxy wearable and galaxy store can't, I hope someone can help.
Click to expand...
Click to collapse
I can't even get Samsung Pay to show up, even having sideloaded the apk onto my Pixel 3...
There's more people with the white page issue here:
https://us.community.samsung.com/t5...ar-app-on-phone-White-screen/m-p/585638#M7720
Same problemm on my S3 & Watch 42 mm + Huawei M10P. I changed the apk and same result. Chinese phones are banned by samsung?
I don't think so, people have the same issue with LG and pixel phones
Same problem here, moto g 6plus + galaxy watch
Can't sing in on app and white window
It appears to be an Android issue since I tested using my work iPhone and there I can login!
Also annoyed as hell bought the watch yesterday when the issue appears to have started also noticed Samsung accessory service was updated 2 days ago..
IMHO in Samsung world... Samsung Android phones have System app for Account crap...
IMHO it is missing on non Samsung Phones...
No idea if possible to install this System app...
Only as idea...
Best Regards
I have the same issue with One Plus 6T. It looks like issue with Android Oreo support. No response from Samsung by when issue will bebresolved.
Any way we can sideload facer and get additional watch faces ?
I made a thread on thursday morning about this. It's been going on for that long
I installed Samsung Account apk . Now when I click on Error Reports I get login page but even after entering credentials it never logins.
Seems like Galaxy Wearable tries to find the linked Samsung account for login.
Here,
I use a Huawei phone and have the same issue. I just bought my Galaxy Watch and can't seem to login to my Samsung Account.
I was looking into solutions online and came across sideloading .wgt files. Would that work for the Galaxy watch?
Any other way we can sideload Facer or any watch companion to have more watch faces ?
I have the same problem....
I called Samsung customer care as well. They sound as if they don't even know there exists and app called Galaxy Wearable.
Guys good news. After 3 days of fighting with samsung over twitter, email, phone, chat , this issue is resolved.
Please try at your end. I am able to login in my One Plus 6T.
At last, better late than never.
Working at last
Worked this morning, problem solved thanks God.
Bought Unlocked Pixel 3 From Google, & T-Mobile Crammed an App Onto the Phone Anyway!
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
lavin40 said:
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
Click to expand...
Click to collapse
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
packetfire said:
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
Click to expand...
Click to collapse
The app is pink I believe I got a Verizon pixel 3 xl cause the OEM unlock option is greyed out so I can't even root the phone
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
jbarcus81 said:
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
Click to expand...
Click to collapse
Yep. This. If the app(s) are installed it's because you let the setup install them. They (Google/T-Mobile) didn't install them on the phone without your consent. You just missed where you have the option to not install them.
ktmom said:
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Click to expand...
Click to collapse
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
packetfire said:
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.tmobile.pr.mytmobile
Tmobile silently installed this app on my unlocked pixel 3xl from best buy just yesterday after I set up my playstore account!
As a User app though.
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
Just to show that it was indeed installed to the device...
dirtyreturn said:
Just to show that it was indeed installed to the device...
Click to expand...
Click to collapse
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
ktmom said:
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
Click to expand...
Click to collapse
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
dirtyreturn said:
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
Click to expand...
Click to collapse
I think I had to disable TMO apps during setup on my PH-1. I'm sure that Google has agreements with the carriers who offer the device. Even (esp?) when the device comes straight from Google.
And yes, stock ROM.