I just got a new Asus MeMO Pad 7 (ME176CX), set it up, and now I'm trying to create a new restricted user profile (for my kids). I can create the profile from my main owner's settings panel, but when I switch over to it, I immediately get the error message "Unfortunately, Setup Wizard has stopped". And then I cannot do anything other than push the power button twice (to turn off the screen and then get me back to the unlock screen) to return to the owner's account.
I already tried several things: I deleted the profile and tried creating another one. I tried creating a normal, non-restricted profile. I did a factory reset of the tablet. None of these helped.
Why is the setup wizard crashing all the time? How am I supposed to get past this problem to set up a secondary, restricted profile? Is this a common problem, or unique to my unit (can't find much about it searching here)?
If I can't create a limited account for my kids, this tablet is no good to me and I'll need to return it. I don't have time to figure out rooting, so any suggestions that don't rely on that are appreciated. I have submitted a ticket with Asus tech support, but... we'll see...
If this is the out-of-the-box experience for a brand new Asus tablet, should I expect things to get better, assuming this problem can be addressed, or should I just give in a get a Galaxy Tab 4?
Related
So far, I have not managed to remote wipe my Froyo Nexus One from Exchange. It just didn't work.
I'm wondering if this hasn't been implemented yet in the version I downloaded (the one that was publicized up last weekend) or if there's something I'm missing.
Has anyone every done this successfully?
Maybe when the finalized Froyo build is out. I would try it myself but what if it works
I'm stil unable to do this using FRF83. Has anyone else tried and had it successfully work?
Exchange sends the remote wipe command but the phone just doesn't acknowledge it.
I'm hoping Google isn't trying to quietly not include full ActiveSync capability into Froyo... it seems awfully late not to have features baked into incremental test builds after the source has been released.
You don't have the final release yet, chillax and wait for, then you can complain to your hearts desire about what isn't included.
I'm on FRF85B. Still doesn't work.
The admnistration settings are correctly configured I assume?(both server side and phone side)
I have the device setup connecting to my Exchange server. I can get mail fine. It updates my calendar fine.
Within Exchange, the device is setup and seen.
But when a Remote Wipe is initiated, nothing happens. I can see the request being sent, but the phone never acknowledges it. I get the standard security error the next time I try to sync and I can't send or receive any new mail, but I still have access to all mail that has already been pushed to me.
Even though our policy says that a PIN is required, I've never been prompted for a PIN. (Although, I do have a security pattern setup, so I dunno how that affects anything.)
Inside the device's Location & Security settings, there is an option for Select Device Administrators, but it doesn't do anything.
I don't know of any other configuration or administration options.
You may have to do a factory reset and implement the administrator from first boot.
You probably can't gain admin access to a device after the device is set up. That'd be a huge sercurity flaw.
Here's what the option looks like, under Location & Security Settings:
Device Administration
Select device administrators
Add or remove device administrators
It doesn't sound like I'd have to wipe in order to add.
ive tried a remote wipe too, but it didnt work :/
Probaby time to get in touch with Google Support.
I posted a bug report and heard back from someone at Google, saying that my issue only exists if Exchange is allowing unprovisioned devices.
So I turned that off. Now I'm getting "This Exchange Activesync Server requires security features your phone does not support."
At least it's a different message.
Now the word I'm getting from Google is:
(via http://code.google.com/p/android/issues/detail?id=9426)
"That's probably the "correct" response, as we only support the basic (EAS 2.5) features in Froyo. So if your server requires, for example, password history or expiration, or complex characters, then it won't be provisionable in Froyo. Our goal is to provide more policy support in future versions, but for now we support - password (PIN/alpha), minimum characters, max. fails to wipe, inactivity timeout, and remote wipe."
So there you have... still no full ActiveSync support in Froyo.
Success!
The password recovery policy is what was causing the holdup.
I had to create a custom policy for Android devices that didn't include this and everything worked as designed.
The next time I attempted to sync I had to confirm the Email app as functioning with a Device Administrator (which explains the odd Location & Security/Select Device Administrators button that nobody really knew what it did.). After allowing that, a PIN was enforced and a remote wipe was successful.
The only concern was that I was able to go in and remove Email as functioning with a Device Administrator. This prevented me from sending or receiving any new mail, but any already-synchronized email remained visible and readable.
So, this sounds simple; but I guarantee you it is not.
I just got my Note5 about 2 weeks ago; and despite some missing key features, I really like it. Until today.
Carrier: Sprint (who apparently doesn't have 24/7 customer service)
My fingers were a little dirty (which they have been before) and my scanner wouldn't unlock the phone. Cleaned them and now it's already locked and seems to not really check the prints anymore?
First attempted fix: backup password, I know I set it up...but it doesn't work. None of the passwords I might use will work.
Second attempted fix: Google signin, I have a free google apps account and apparently using my whole email address as username doesn't work on this; also tried just using the plain username just in case. I know the password is correct. I'm the domain administrator.
Third attempted fix: Android device manager, tried setting a new password on the lock screen and was greeted by the infuriating message "Since google has verified that your screen is already locked, the password you set won't be needed"
Fourth attempted fix: chat with samsung support, which was utterly useless. Although I did find out that samsung has their own unlock utility...except that it has to be setup beforehand.
Fifth attempted fix: bang head on cement...hasn't shown any signs of working yet. Although I feel less frustrated.......and less conscious.
Theories: free version of Google Apps, sucks (the apps themselves are great)...I've had tons of trouble getting signed into certain google features over the years. Also I have no option for a support PIN to use to contact google support.
I think that my latest OTA update may have somehow changed or reset my backup password.
The last theory is whomever changed Android device manager to not reset lockscreen passwords whenever you want to...basically made that tool half as useful as it should be and completely useless to me.
Anyone have any other ideas, that don't involve a full wipe?
I was finally able to gain access to my phone. I had to disable two-step verification in order to sign into my google apps account from the lock screen.
I am having the same issues and tried ALL of the fixes you tried except I didn't get the notification to login with google. When does that happen?
I had the problem, too. I ended up having to factory reset. REALLY irritated by this.
I recently retired my son's Galaxy Tab 2 (7") for a new SM-710 (updated OTA to 5.1.1). The old Tab 2 (running CM12) was setup in multi-user mode with him as a restricted user. It worked great - I could limit his access on an app by app basis, his data didn't cross-over into my data, he could log into services with his own account etc etc.
So I had intended to setup his new SM-710 the same way - me as the primary user, him as a restricted user. One HUGE problem - the Samsung (TouchWiz) version of Lollipop seems to be missing a critical menu item that is present on stock Lollipop devices. I can't find the "add users from lockscreen" option in the USER settings. On stock devices there is a menu button (top right) where this option is located. It is usually defaulted to unchecked, however on the Samsung version, the device behaves as if the option is checked, and yet there is no menu item to uncheck. This results in both the "GUEST" and "ADD USER" items appearing in the multi-user lockscreen menu when the device is locked. This is a problem for a multitude of reasons. My son could simply create a new user from the lockscreen and use that account to bypass all the restrictions I have placed on his account. Moreover, anyone else could do the same thing, making it impossible to secure the device.
I have tried a few fixes that I found here and elsewhere. All of them required me to root the device, none of them worked (build.prop edits, sql db edits etc). Happy to describe in detail what I tried, but didn't want to make the post any longer that it had to be). Has no one else noticed this problem/error/bug? Am I missing something obvious?
Any help / insight would be appreciated.
Have a look at Samsungs' "Kids Mode", available in the Galaxy Apps store. It is supposed to be their solution for handing your tablet or phone to your children. It requires a pin code to leave the Kids Mode. However, I suspect it is targeted at rather youngish kids.
My T815, which is still at 5.0.2, doesn't even have the options you describe. I'm a bit annoyed that Samsung has spent time disabling features that just come for free from Google.
The build.prop edit should have worked according to other threads. I'm not rooted, so I can't tell.
Are there any other users experiencing (solved?) issues with the Volkswagen remote access app? This app had been working well up until march of this year. Then the app just started throwing an error stating "unable to log in at this time" when I attempt to log in, but before I even enter any data.
I have tried all the usual steps including factory reset of my S21-Ultra to no avail. VW tech support has not responded to my requests for assistance. I had given up hope. Then, during July I had to switch handsets for a short time. On a moto stylus 5G, the app worked correctly with my existing account data. When switching back to my S21 I have the same error message.
Thanks in advance for any suggestions.
For the record - issue solved by pure focus, commitment, and sheer f*cking will.
It seems the car net app REQUIRES chrome to perform the initial connection setup. It does not utilize the default internet application. I prefer the samsung internet beta and promptly disable chrome after resetting to avoid downloading any updates for it. While I was on the temporary phone (knowing it was temporary) i did not go through my usual customizing / disabling. Once set up I check the "keep me logged in" option and I can disable chrome again.
Wow, talk about browser monopoly. Really dumb implementation, thanks sharing the cure
Hello,
I’m looking for any suggestions from users that have migrated their Google Home email address to a new Gmail and Home.
What I’m looking to do is:
Move Google Home from my current Gmail address to my new Gmail address in newly created “Home” in Google Home app
Move Nest devices (Wired doorbell, Speakers, Yale Lock, Protect, Thermostat, sensors) to newly created Home in Google Home app without losing my Nest Aware (1st Gen) subscription. And without factory resetting the Nest Doorbell as it is wired and not easy to get to the QR code.
Move YouTube TV from current Gmail address to new Gmail address.
Reasons:
Current email is associated with other things. Not just the Smart Home and have been getting more junk mail over the last 4 months.
“Issues” in Google’s development procedures and updates to the app have caused some devices to show up multiple times. Even after using the old method of downgrading the version of Google Home app and removing the duplicates, they still exists somewhere in Googles infrastructure. When giving voice commands, Google Assistant does not execute properly because it either doesn’t see the device or sees the device under a previous name.
After creating a Test Home environment for the Preview program, I moved one Chromecast w/Google TV dongle and a Nest mini to that environment. I had removed the devices from my main Home, factory reset and added them to the Test environment. Now, when I ask Google to sync my devices in the main Home, Google now responds that “two devices are not available and you might want to try setting them up again”
I’m waiting to execute this project until the new updates for Matter are released. Just in case there are problems so I do not have to factory reset devices or create a new Home, etc; more than once.
Any advice on the best ways to do this with minimal issues will be greatly appreciated.
Thanks
I know these following problems will not get fixed by creating a new Home in the app, but I wanted to list them to see how many others have been affected as well.
Because of the three major screw ups this year by Google, (the three I’m aware of) I’ve moved the majority of my Google Home routines to Amazon Alexa.
Google using code from Sonos costs us the use of being able to control Speaker groups. Still no fix.
The update pushed out to the Google Home App around October 20th 2022 time-frame broke the use of color light bulbs from major 3rd party vendors (that I know of Feit, Geeni, Tuya). Google Assistant no longer recognized the bulbs as color and only responds with an error when used in a routine or vocal command.
The fix for the above issue pushed out the following week only corrected part of the problem and broke Location. Whenever the Google Home app was opened, there was an error of “no location”. The App however does recognize color light bulbs again, but the update to power on/off, change brightness and set color, broke any routine that had a Starter that was time based. Example: For setting night functions of Locking the door, setting ADT alarm and turning off lights no longer executed. UNLESS, I remove the light bulb functions.
So basically I now have all routines that turn lights on/of, change brightness or color handled by Alexa.
It’s also weird that I could tell Google Assistant to run the broken routines and they worked, but it does not execute them based on a Time Starter.
4. Does anyone know how to dismiss ALL the notifications at once in the Google Home app like in previous versions. Instead of having to click the 3 dots next to each message and then click Dismiss?
Thanks again.