[Galaxy S II Android Development] gianluca.cecchi:
I changed both ro.product.name and ro.product.model but I get the same message. Capturing a catlog just before running Gear App I see the problem seems in function isSamsungDeviceWithCustomBinary:

12-31 14:54:29.355 D/tUHM:TWatchManagerApplication(12240): AppVersion : 2.2.16101261
12-31 14:54:29.382 D/tUHM:SetupWizardWelcomeActivity(12240): UHM onCreate() Intent: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.samsung.android.app.watchmanager/.setupwizard.SetupWizardWelcomeActivity bnds=[353,137][466,280] (has extras) }
12-31 14:54:29.383 D/tUHM:SetupWizardWelcomeActivity(12240): UHM onCreate() Bundle: null
12-31 14:54:29.384 D/tUHM:SetupWizardWelcomeActivity(12240): density [1.5], densityDpi [240], heightPixels [800], widthPixels [480]
12-31 14:54:29.385 D/FeatureUtil(12240): semAvailable = false
12-31 14:54:29.498 D/tUHM:TWatchManagerApplication(12240): getAppContext()
12-31 14:54:29.499 D/tUHM:TWatchManagerApplication(12240): mAppContext = com.samsung.android.app.twatchmanager.TWatchManagerApplication@a6dacf3
12-31 14:54:29.504 D/tUHM:InstallationUtils(12240): hasInstallPermission() res:-1
12-31 14:54:29.506 D/tUHM:HostManagerUtils(12240): isSamsungDeviceWithCustomBinary, res [true]
12-31 14:54:29.507 D/tUHM:SetupWizardWelcomeActivity(12240): showCustomBinaryDialog
12-31 14:54:29.508 I/tUHM:CommonDialog(12240): createDialog()

Could it be related with yellow triangle, that I historically leave there, as I thought not so problematic?

Or any other mean to let the function think it is ok?

BTW: in build.prop I also added the line " ro.opa.eligible_device=true" and I was able to install Pixel Launcher by Google and after using it for some days I think is lighter than trebuchet and I like it. Of course only enabled apps (like gmail, maps, ecc) are able to get the typical Pixel sensitive context. But I didn't need to put SELinux to permissive as I saw in helps provided in your links.

I installed the velvet.apk app described in your posts and was able to set up google assistant too (after changing language to US English)

Next days I'm going to try with new rom provided; I'm still using 8th December one that works quite well in general.

One problem in that rom I have often found sound conflicts regarding microphone usage; have they been addressed in latest one?

For example, after using Maps and closing it, if I try to post a message via whatsapp microphone function or to detect a song with shazam I get microphone error messages inside the app and messages like this in catlog regarding the recording alsa device:

12-27 11:18:31.255 D/Yamaha-MC1N2-Audio(1994): yamaha_mc1n2_audio_set_route(80000004)
12-27 11:18:31.255 E/TinyALSA-Audio Input(1994): Unable to open pcm device: cannot open device '/dev/snd/pcmC0D0c': Device or resource busy
12-27 11:18:31.255 E/TinyALSA-Audio Input(1994): Unable to open pcm device
12-27 11:18:31.255 W/APM_AudioPolicyManager(1994): getInputForAttr() failed opening input: samplingRate 16000, format 1, channelMask 10
12-27 11:18:31.255 E/AudioRecord(11462): Could not get audio input for session 3281, record source 1999, sample rate 16000, format 0x1, channel mask 0x10, flags 0
12-27 11:18:31.255 E/AudioRecord-JNI(11462): Error creating AudioRecord instance: initialization check failed with status -22.

I could try "fuser" command to analyze who is locking the device, but it seems it is not provided by default.