Seems like such a simple question with I assume a simple answer but I can't find either anywhere. When I use something like Chrome to Mobile Beta on my Desktop, it shows I have 6 registered devices when in fact I only have 2. This is because every time I flashed a new rom on my phone, it changed the device's name and I re-registered it with that new name while the old name still stayed as a registered device. Therefore I basically have 4 devices listed there that no longer exist.
HOW DO I GET RID OF THEM????
Related
Howdy (and apologies ahead of time if this is a dup, I _did_ search, didn't find anything),
Is it just me or did application specific passwords break with Lollipop? Googled a bit and couldn't find any details. I just see postings stating that 2fa works now, but I don't see how that negates the need for app specific passwords.
I know 2fa is now supported but I'm a bit concerned to use my normal password as I'm not sure if it's stored in any way. Anyone know of any links that explain what exactly is stored and how the auth is persisted across reboots? Maybe I'm misunderstanding, but I thought that if my device was lost, with app passwords I could revoke the device without changing my main password.
The other issue is, since I'm using 2fa with the google auth app on this phone I wouldn't even be able to setup if I wiped this phone (which I will need to). At least prevously I could login to my google account on my PC, create the app specific password and sign on that way.
- TIA for any info
I have just upgraded my Nexus 5 from 4.4.4 into 5.0.1 (I didn't install 5.0.0). What I did:
1. Factory reset on 4.4.4
2. Install system update into 5.0.1
2. Factory reset on 5.0.1
3. Application specific password NOT accepted on initial account setup on Nexus 5. I had to use my master password and code list because you can't read sms before account is added on the phone.
Is this really broken? I haven't found any info on this either.
Wow, someone else who was using this feature. That makes 2 of us at least. I guess that's why they removed it...? Yeah, unless I'm missing something it appears it's indeed broken.
The best part is this isn't really part of Android, but part of gapps; no way to report bugs for that (at least that I've found). Someone opened a bug against AOSP but they closed it as this stuff isn't part of AOSP:
{scheme}code.google.com/p/android/issues/detail?id=57863&can=1&q=app%20specific%20password&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
They suggested using the "google mobile help forum"; I guess this page links to it: {scheme}googlemobile.blogspot.com/2008/11/got-questions-try-new-google-mobile.html - following the link just gives an error "no group mobile found" or something similar.
All I could see to do was to post a response to their help page on signing in with app specific password to Play pointing out the inaccuracy of the article. I can't find that article anymore, it looks like it might've been removed? I received no response to that.
I can't imagine this being a very difficult feature to support, so I'm a little surprised it was removed. But hey, at least they added all sorts of eye candy and other crap I don't really care about.
I think this is a deal breaker for me. Unless I'm misunderstanding here, if someone were to acquire my phone and extract the password the key or whatever it's storing, they would then be able to access my account settings and take full ownership. If it only had the app specific password, I don't think that'd allow them to modify security settings. If it's tieing the key to the device, that's great but I still can't revoke it (doesn't show up in the app specific password page). Unacceptable (again, unless I'm misunderstanding something?).
Maybe it's time to start looking for alternatives. Wonder if any Maemo derivatives can run on the M8? It was miles ahead of Android in all departments except eye candy anyways...
I'll reply here if I see any more info - please do the same.
This is totally broken.
My company uses App Specific Passwords and I just updated my Droid Turbo to Lollipop.
After the update, everything worked fine. However, I started getting google play service errors and had to wipe.
Now I need to log in using my authenticator password instead of my app specific password.
Not good
dragonash said:
This is totally broken.
My company uses App Specific Passwords and I just updated my Droid Turbo to Lollipop.
After the update, everything worked fine. However, I started getting google play service errors and had to wipe.
Now I need to log in using my authenticator password instead of my app specific password.
Not good
Click to expand...
Click to collapse
Agreed. Quite unfortunate, but I can't find anyone outside of this thread and a few random posts that seem to actually care.
Thanks for confirmation that this is still a problem, btw. I'm still not sure if there's anyplace to even raise this to Google...
i just spent an hour trying to understand why this smart feature wasn't working on my new mobile with a stock andorid lollipop! at least i feel less lonely now...
i sent a feedback to google even if i don't think they'll reply.. i opened a ticket on AOSP website (Issue 189310) if you want to check their reply.. sorry but i can't post outside links
Hi there. First of all I'm sorry if this is not the right place to post this.
Anyway, someone I know bought an used iPhone 6 only to discover that it's somehow an Android device heavily modded (it looks like an iPhone 6 on the outside, which is an issue because it doesn't have the three buttons the android apps are meant use). I'm not even sure if it's possible to make this usable, the iOS stuff is glitchy and Android apps don't seem to work that well either.
I'm not really a developer but I play around with Tasker/xposed and stuff so when I realized there wasn't an actual shortcut for the android settings (I can only access the iOS version of the settings, which the factory reset doesn't seem to be working), I decided to download the trial version of Tasker and see what I could fiddle so I could find out how this was done. On my first try I couldn't find a thing and now Tasker keeps crashing, I can't keep it open long enough to enable logging.
The root seems to have been made using the kingroot app (evidenced by the KingUser, which was the only thing I could find). Removing root access doesn't seem to do a thing.
Sooo... I've ran out of options and decided to post it here as a far cry for help. I realize I have not given you much and more info is probably required, but I'm not sure how to acquire it. The "About phone" on the menu doesn't give me much, device name is Android, Carrier is unknown and Version is 8.1.2 (12A405). Model number is MG492CH/A.
Thanks for your help and I'm sorry I couldn't provide any more useful information.
Hi, thank you for using XDA Assist. A goggle search of your model number shows it as an iphone clone. It doesn't surprise me that it uses Android as iOS would be next to impossible obtain. But the bad news is there is no information on XDA about your device. The closest I could find was this, http://forum.xda-developers.com/showthread.php?t=2778862 To return to stock you'd need the android factory image for your phone and a method to flash it. Both would be specific to the phone. The only other thing I can suggest is to ask in this forum, http://forum.xda-developers.com/android/help
I'm using a Nexus 6 with Android 7.0
I have this issue with the app thats supper annoying. I'm guessing its not implemented. Anyone has any suggestion, maybe a different phone app?
Google Phone App does not recognize phones in Contacts if country/area code is not the same.
ie. +54911 xxxx.yyyy and 11 xxxx.yyyy are the same but this does not detect it (WTF).
Also if I have Jorge Bush (+54911. xxxx.yyyy) as a Contact and I look for Bush it appears but if I look for xxxx it does not appear, I have to look it like +54911 .... or 11 ... depending on how I have it stored in my contact.
(Samsung's phone did this correctly 4 years ago come on!!)
Thanks!
OK, so, recently bought ymself a new phone, samsung j4+, I had a sumsung s3 neo or something like that. anyway, old phone ran A4.4, new phone has A8+ (android). I use an app called Mobizio for logging in and out of work, I;m a care worked and it's what we use. However, I can't log into the mobizio app on my new phone because it has a different UUID, so I want to change the UUID to that of my old phone which will no longer be used as the battery/phone is didgy and can;t hold its charge longer than an hour. the question is how do I go about changing the UUID, as 4.4 used a UUID for the whole phone, I think, and the new versions of andriod use different UUIDs for different apps, if what I read is correct, so I want to change the UUID for mobizio on my new phone to that of the old one
Hey guys,
so I lately had a bunch of issues with my Samsung and had to restore several backups etc after failed firmware updates.
Sometimes I lost a few apps, had to reinstall it, etc - it was a HUGE mess. I'm fairly certain at some point bumble downgraded me because I had so many reinstalls/reactivations/etc.
Here's the issue - I'm trying to create a new account and its easy to get around geo-location, IP and new phone-number and verification but I'm fairly certain they also track my device-ID or device-IDs if that changed with the backup/restores/reactivations.
I downloaded device-ID-changer and all the apps show up, ASIDE bumble... I'm wondering if I screwed up something like the registry (if android has something like this) with all the re-installs... the app opens, works, all good, but I can't sign up on this device because of the ID.
I'm on Pie so every app has a separate ID but Device ID changer cant find app.bumble.com.
I can sign up just fine from my tablet (on Nougat) - set geo-location/proxy/verification, easy - works every time, but as soon as I log in on phone I'm getting kicked off.
Where could the issue be? Why can't Device ID changer not find the app? Is there a way to find out if something went wrong with the install? I HIGHLY doubt they hardcoded all my device IPs in the installer (tried offline installs as well, so 0 change they send data down)
Could someone check if Device ID Changer 2019 can find com.bumble.app in the list on their phone?
thanks