Hi,
i just purchased a chinese OPPO Find 5 X909 phone with Android 4.4.4 and MT6592 CPU.
i switched it to english language.
My goal is to switch is to install Google Play Store.
I tried the following, but all of these issues failed, please help me:
1.) i downloaded a Google Play Store apk (4.2 and 4.6) and installed it, but a weird Android 4.4 virusscanner close everytime the app 1-2 seconds after the start. I stopped all apps that are related to a virusscanner, but didn´t had success, the behaviour was the same.
Inside the virusscanner, the language is complete in chinese, no chance to configurate something.
The name of the Virusscanner is Tencent QQ Pim Secure
Deinstallation isn´t possible,
2.) Although the CPU is another then the usual Find 5 one, i tried to install a new ROM from here: http://www.oppoforums.com/threads/find-5-coloros-v1-0-7i-beta.10372/
But when was on step "Press and hold the Power and Volume Down buttons to enter recovery mode", only chinese symbol was viewable and i didn´t knew what to select...
i didn´t tried something and stopped it, maybe this was a good idea for not bricking the phone
How can i stop or deinstall the chinese virus scanner software on Android 4.4.4?????
I don't know how to solve the playstore problem, but you can find a video explaining the Chinese recovery on the bottom of this post.
The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!
Hello XDA-Community,
I've got a Yoga Tab 3 Pro YT3-X90L from a customer.
He was telling me, that he wanted to unlock his device with the pattern, mismatched for several times and now its locked and requires the owners google account. Or something like that. He never had the owners google account. He told me that his seller has activated his device for him. And he has no clue who it was.
Now here is my part.
I've researched and obviously it's a FRP. The owners google account information are stored in the FRP-Partition. And this partition won't get deleted with a simple factory resett.
What i've tried so far:
1.) https://www.youtube.com/watch?v=nCzrnnh2K1w I was able to follow this tutorial to minute 9:08. But the option "Email and password" is not there anymore. I guess they patched it with 6.0.1.
2.) I tried to flash a stock rom or twrp with LenovoDownloader(QcomDLoader). The stock rom file is: Lenovo_Yoga_Tablet_3_YT3-X90L_ENG_S200028_1609230146. even its a german device this file was the only one i could find. But the LenovoDownloader won't recognize my device. The windows stays white, no entries. I guess i installed the correct driver for this device and Windows recognizes them as removable device if i plug it in via usb.
3.) I've tried to use adb and fastboot boot oem unlock. But this commands aren't working in locked state.
4.) With a trick i could open the Settings and was full of hope to active the developer options to set usb debbuging to active. But this developer options aren't available either with this "user".
5.) There is an apk for showing the "Email and password" interface. I could install it, but it force closes right after starting it.
6.) I've tried several tools to bypass this FRP: WinDroid Toolkit, D-G Unlocker, Realterm, but NOTHING.
What could i do further? I'm out of ideas right now.
I've read about a factory_update.img but i cant find anything, except the stock rom file, for this device.
Or downgrading the device, so i could use the "Email and password" but. But i can't even flash the stock rom.
Specs for the device:
Lenovo Yoga Tab 3 Pro YT3-X90L
Lenovo/YT3_l0_row_lte
6.0.1/MMB29M/LenovoYT3-X90L_S200307_170614
i appreciate any help i can get
greets
redplate
I've wrote it down. Hope this helps.
Situation:
"Confirm account: The device has been reset. To continue, sign in with a Google Account that was previously synced on this device. "
Explanation:
The device has been blocked by repeated input of the wrong password, pattern, etc. and can only be unlocked with the Google account of the owner.
A factory reset or hard reset does not help here, as the account information is saved in its own FRP partition and will not be deleted when the factory state is restored.
Solution:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
7. You can now not only browse the Internet through this search, but also search for and open installed programs.
8. We are looking for Chrome, open the internet browser, go to www.google.com and search for DPC test.
Link: https://www.apkmirror.com/apk/sampl...-release/test-dpc-4-0-6-android-apk-download/
9. After downloading this application, go back to the Google search application.
10. Here we enter "Download" to search for the download application.
11. In Downloads we can now find and install the downloaded app.
12. To allow the installation of this .apk, you must allow the installation of "unknown sources" in the settings.
13. Either you go here on the installation itself on "Settings", or you search for "Settings" on the Google search app.
14. After completing the installation of the DPC-Test program, start it with "Open".
15. The app itself is will register as a device owner and now allows us to set up a new Google Account as owner.
16. If this is set up, it will also be included in the FRP partition.
17. In the event of a new factory reset, the device is reset, the DPC-Test program is removed and the device can be freshly set up in the factory settings.
after the takeover of the owner, the reason for blocking the device was not present anymore and the old owner was overwritten. This will be overwritten in the FRP partition aswell with the new account and the old one no longer queried.
You, mister, are my savior! Thank you very much.
Solve works for Lenovo Yoga 3 tablet
Just a big giant thank you! My dad passed away leaving me a Lenovo Yoga 3 tablet, unable to gain access due to information stored in the FRP partition. :highfive:
Hi
I followed your instructions for first 5 points
redplate said:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
Click to expand...
Click to collapse
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance
marOOn1971 said:
Hi
I followed your instructions for first 5 points
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance
Click to expand...
Click to collapse
Hi. Actually I'm not into this anymore. Could be possible they removed it since it might was reported.
If I have any idea I'll let you know it
I've spent an embarrassingly long time on this last weekend and I believe there might be a small group of people that would appreciate the found solution for this issue.
tl;dr: When using opengapps copy https://gitlab.opengapps.org/opengapps/all/-/blob/master/product/overlay/PlayStoreOverlay.apk to /system/product/overlays reboot and the loop should be fixed. (Also make sure to have Family Link Manager and Family Link Helper installed as system apps).
The problem:
When using any custom ROM Google Family Link fails to be setup correctly no matter the opengapps version/size. The error is a loop at the "The Family Link Manager needs to be setup for this device" step and then it leads to a modal dialog "The profile manager is required for google accounts managed with family link.", when you click "Got it" you will be led back to the same page and a click to "Next" opens that same modal dialog again.
The solution:
The Family Link Manager (com.google.android.apps.kids.familylinkmanager) and Family Link Helper (com.google.android.apps.kids.flh) apps needs to be installed as system app (in /system/priv-app/). Besides that the PlayStore app needs specific resources set to make the callback intent to enable the Family Link Manager as Device Admin app work. Funnily enough there was https://gitlab.opengapps.org/opengapps/all/-/merge_requests/51 4 months ago but seemingly nothing copies that PlayStoreOverlay.apk to /system/product/overlays/, doing that manually using TWRP (or anything else that can write to /system/) does fix the loop and makes Family Link work properly.
Credits go to: https://gitlab.com/LineageOS/issues/android/-/issues/3383
I hope this helps somebody. Please move this post to the appropriate forum if it shouldn't live here.
Nexus2kSwiss, thanks for the post. It's the most helpful thing I've found so far. I'm still having a problem with the loop, but I seem to be getting farther along. There's probably some basic detail I'm missing.
Device: Moto G4 Play
ROM: LineageOS 17.1
I found that LineageOS has a built-in root feature that can be toggled. (That's awesome. Too bad it took me so long to find that out.)
My questions:
Does "Family Link Manager" and "Family Link Helper" need to be particular versions? Do they need to match versions? And what about just "Family Link"? That's a whole different version. I'm thinking that it either replaced the other two or it's just the piece you get from the Play Store, while the others may come baked in?
Does the "PlayStoreOverlay.apk" need to be a specific version.
In any case, should I copy all three of the Family Link files to /system/priv-app/?
Here are the steps I've written for myself:
1. enable developer options (tapping on the build number several times)
2. enable ADB developer options
3. enable root in developer options
4. On PC,
adb devices
adb root
adb remount
5.
adb push PlayStoreOverlay.apk /system/product/overlay/PlayStoreOverlay.apk
6.
adb push com.google.android.apps.kids.familylinkmanager.apk /system/priv-app/com.google.android.apps.kids.familylinkmanager.apk
7.
adb push com.google.android.apps.kids.familylinkhelper.apk /system/priv-app/com.google.android.apps.kids.familylinkhelper.apk
8. (not sure if this is needed)
adb push com.google.android.apps.kids.familylink.apk /system/priv-app/com.google.android.apps.kids.familylink.apk
I see the files are there now and I get farther along my journey. I'm able to select which apps should be allowed and it seems like I'm almost done, but I don't get to complete it. I get the message again about the profile manager that keeps popping up and won't let me past it. (I checked again and it actually just crashes at that point.)
Any thoughts?
Thanks.
You definitely need to reboot the device after putting the PlaystoreOverlay as I believe it doesn't get loaded automatically. Family Link Manager and Familylink helper should be the same version (just get the lastest from apkmirror or so).
The Family link app itself is not needed as it's just the UI for managing other devices.
Where do you get stuck now? Do you have gapps nano or bigger installed?
If I understand my original linked lineageos thread correctly there should be builds now available which do copy the PlaystoreOverlay correctly. So maybe using a newer build for your device fixes the issue.
Nexus2kSwiss said:
You definitely need to reboot the device after putting the PlaystoreOverlay as I believe it doesn't get loaded automatically. Family Link Manager and Familylink helper should be the same version (just get the lastest from apkmirror or so).
The Family link app itself is not needed as it's just the UI for managing other devices.
Where do you get stuck now? Do you have gapps nano or bigger installed?
If I understand my original linked lineageos thread correctly there should be builds now available which do copy the PlaystoreOverlay correctly. So maybe using a newer build for your device fixes the issue.
Click to expand...
Click to collapse
Thanks for the response. Good information!
I think I did the nano gapps install. It's about 400 MB. I'll look for a newer build that has the correct PlayStoreOverlay. Maybe that's the easiest.
I will report back if I get farther along.
Thanks again.
Okay, got it working!
I did a factory reset and wiped everything. Then, I reinstalled LineageOS 17.1 and the latest GApps.
lineage-17.1-20220204-nightly-harpia-signed.zip
open_gapps-arm-10.0-mini-20220204.zip
(I tried to install the "super" GApps, but found that "mini" was the largest bundle that would fit on this device without resizing the partition.)
On first boot-up:
I got an error for Speech Services. (Closed it.)
Connected to wifi.
"Checking for updates..." (automatic)
"Installing updates" (automatic)
"Copy apps & data" - Chose "Don't copy".
Signed in with my kid's account.
Agree to terms.
"Got get your parent" - Selected my (parent) account, logged in. Confirmed 2FA.
"Stick around for what's next" - "Next".
"Checking for updates..." (Again?)
"Please wait"
"Review apps" - This is where I select which apps to restrict for my kid. "Next"
"Google services" - "Accept"
"Protect your phone" - Screen lock settings.
"Access your Assistant with 'Hey Google'" - "Skip"
"Access your Assistant without unlocking your device" - "Skip"
"Anything else?" - "Done for now".
"LineageOS features" - leave "help..." selected. "Next".
"Restore apps and data" - "Skip"
Select "Start".
"Please wait"
"Your devices are connected" - "Next"
"Supervision ready!" - "OK"
It worked! I was beginning to doubt it.
So there you go. LineageOS 17.1 on Moto G4 Play with Open GApps ("mini") allows you to use Family Link / supervision.