search

microg / GmsCore

Free implementation of Play Services
https://microg.org
Apache License 2.0
8.72k stars 1.74k forks source link

Add warning to prerequisites (SetupWizard) #312

Open verdulo opened 7 years ago

verdulo commented 7 years ago

My problem is not directly relate to microG project, but rather to Android itself: according to prerequisites I removed the 'SetupWizard' app, unfortunately after removing that app and restoring to factory settings I cannot use the home button, notifications' bar doesn't work, I cannot enter developer options - it's known 'bug' on Android 6. I think that users should be warned about that problem.

ale5000-git commented 7 years ago

I wonder if it would be better to keep SetupWizard. I don't think it conflict with microG but I haven't tried.

n76 commented 7 years ago

I don't believe there is an issue with the setup wizard that that is part of AOSP, but if Gapps has been installed it replaces the AOSP one with a different incompatible one.

tomasz1986 commented 7 years ago

This bug has been around forever. At least ICS or even GB. It has nothing to do with Android 6 in particular. I never remove the SetupWizard when deleting GApps for this very reason.

WinSuk commented 7 years ago

This is not a bug on Android, but actually a feature. The setup wizard is ran on first boot, and sets a flag on the system saying the device has been set up and is ready to use. With the Google setup wizard, that happens after it runs through adding your Google account, etc. The AOSP version is a mostly-empty shell of an app that just sets the flag automatically. It's not visible, except maybe a blank screen for a few seconds. With neither app installed, the flag never gets set, and the home button/status bar/etc remains disabled.

https://android.googlesource.com/platform/packages/apps/Provision/+/master/src/com/android/provision/DefaultActivity.java

n76 commented 7 years ago

Not directly related but I think the work around could be the same: I had a time when doing a "dirty flash" for a ROM update got me stuck with the same symptoms. My fix was:

> adb root
> adb shell
# settings --user 0 put secure user_setup_complete 1
ale5000-git commented 7 years ago

If microG is installed then microG is detected as Google, so I think the SetupWizard of Google should work. Does anyone tried?

verdulo commented 7 years ago

@ale5000-git I installed microG services as system user, after resetting to factory settings, the wizard gets stuck at select wi-fi screen.

ale5000-git commented 7 years ago

The wi-fi screen shouldn't have anything to do with microG, or I'm wrong?

n76 commented 7 years ago

Correct, the wifi setup should be totally independent of microG.

verdulo commented 7 years ago

It shouldn't, but if you replace google services with microG (with spoofed signatures) some apparently unrelated things stop to work.

motatuc commented 7 years ago

I run into this problem just today which happened with Lineageos. For me the homescreen was black and I could not do anything with the phone.

The people from Lineage rewrote the SetupWizard. Now this Wizard is looking for the google setup wizard because it sees gms.

s0rl0v commented 7 years ago

I've got a FC loop with brand new LineageSetupWizard. adb shell rm -R /system/priv-app/LineageSetupWizard solved the problem. But this probably won't work after a factory reset.

0pLuS0 commented 5 years ago

SetupWizard will not work with microG;

---> https://github.com/microg/android_packages_apps_GmsCore/issues/681

I'd love to figure this out so I can make the ROM flashable in TWRP without GSF and replaced with microG, but not working.

Then I remove the SetupWizard and then the Recent Nav Button doesn't work, the Settings > User section, I tap it nothing happens.

The build section I tap several times to get the Developer Option, nothing happens...

It's as though the OxygenOS Rom needs GSF to first get setup and running, then it can be replaced with microG, but I want to make it into a microG rom, and I can't figure how... :(