OTA-22 Call for Testing Companion Post

domubpkm

In the meantime, those who are going to switch to RC to test OTA-22, will lose all uAdBlock protection since it won't work after switching to RC (already reported that uAdBlock doesn't work currently) if they don't take some precautions.

My troubleshooting solution (will only work if the hosts file has not already been reset to zero for some reason) :

BEFORE any switch to the RC channel :

copy as a backup with File Manager your last still valid hosts file (size of several MB) (My Device/etc/hosts) and put it in Documents

AFTER switching to the RC channel (for example from stable to RC):

make the image editable with UTTT (System/make image editable/read and write temporarily until reboot)
with the terminal, reinstall the hosts file :
sudo cp $HOME/Documents/hosts /etc/hosts
Reboot the smartphone.

You will then be protected again.

This procedure allows you to reinstall the last valid hosts file you kept in case of need.

flohack

@mark1250 found that Nexus 7 (flo and deb) also need GPU blacklisting to prevent Morph from crashing. A new RC for both will be done.

mark1250

@flohack

Thanks for looking at the bug and finding a fix so quickly. You guys are awesome.

Mark

l12853

@flohack Hello , Sir ! The device I use is oneplus5, which consumes a lot of power on the experience , more than android , why ?

Beton

On BQ M10HD WebGL is not working, WebGL test site shows me:

Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

Camera inside Morph Browser is not working. In Jitsi I can see there are two camera devices, but for both it says "Preview unavailable", and in System Settings I can see Morph Browser never asked me for permissions to use Camera.

Even microphone is not working now in Jitsi Meet, which worked for me before. So I no longer can make Jitsi Meet calls using UT.

In Morph Browser logs I see many of these errors probably related to WebGL:

[13467:13514:0215/105611.956743:ERROR:gl_context_egl.cc(208)] eglCreateContext failed with error EGL_BAD_CONTEXT
[13467:13514:0215/105611.956862:ERROR:gpu_channel_manager.cc(401)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[13467:13514:0215/105611.956925:ERROR:shared_image_stub.cc(360)] SharedImageStub: unable to create context
[13467:13514:0215/105611.957021:ERROR:gpu_channel.cc(440)] GpuChannel: Failed to create SharedImageStub
[13467:13514:0215/105611.958656:ERROR:gl_context_egl.cc(208)] eglCreateContext failed with error EGL_BAD_CONTEXT
[13467:13514:0215/105611.958774:ERROR:gpu_channel_manager.cc(401)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[13467:13514:0215/105611.958835:ERROR:shared_image_stub.cc(360)] SharedImageStub: unable to create context
[13467:13514:0215/105611.958936:ERROR:gpu_channel.cc(440)] GpuChannel: Failed to create SharedImageStub

flohack

@l12853 well we will never be as efficient as Android. This is not a problem of that OTA. Did you install Waydroid by chance?

flohack

@beton Camera permission can only be asked if the kernel is patched, something we cannot do currently for the BQ and Meizu devices. In this case the camera should "just work".

sk

Just tested with bq m10 FHD (frieza) (rc for OTA22) with morph on:

webcamtests.com
front camera: works (after permission has been granted)
back camera: works (after permission has been granted)

mictests.com
microphone: works (after permission has been granted)

webgl.org
webGL remains not working.

sk

Tested also with bq4.5 and meizu mx4
webcamtests.com
front camera: doesn't work (after permission has been granted)
back camera: doesn't work (after permission has been granted)

mictests.com
microphone: doesn't work (after permission has been granted)

"Apparently your webcam is being used or blocked by another application. To start your webcam, you must temporarily close that application"

flohack

@sk Strange Mic worked for me on E4.5

sk

@flohack
Indeed, I retested at https://webrtc.comm.intouchhealth.com/webrtc/
also neither vid nor mic working on my e4.5

Ha. I rebooted - and now microphone is working in browser.

sk

@sk mx4:
mic works after 2 reboots.

Seems a little bit strange.

l12853

@flohack My device is stil the
stable version OTA21

Beton

@sk Can you check if Jitsi Meet is working for you?

I checked camera and mic on these sites and it seems to be more complicated.

I tried webcamtests on freshly started browser and it does not works, I was asked for camera permission inside browser, and after clicking "Yes", site still hangs on "Waiting for your permission.". Then I went to mictests, and it was the same. It doesn't even shows me available devices, just hangs on permission waiting.
After that I restarted Morph Browser and opened mictests, and it worked, it showed me 3 audio devices, after choosing first device, it succesfully recorded audio. Then I refreshed page, and it stopped working - just hangs on "Waiting for your permission" without asking me permission this time. Then I tried webcamtests again but it still doesnt worked.

So I still cannot manage to get camera working, and microphone worked for me just once in mictests after browser restart.

Jitsi Meet as before shows me 2 camera devices, but cannot get video from these devices, it also shows me 3 audio devices but these devices have white exclamation mark in red circle and no name, and Jitsi is unable to get audio from it.

flohack

@l12853 Then wait after OTA-22 maybe it improves... Release is tomorrow

l12853

@flohack Hello , Sir ! I ' m in China , and I can ＇ t make calls using China Telecom ' S 4G. Do I need to test the basic communication functions of each operating network

Bolly

@beton You can try switching off and on. It is not the same as rebooting.

arubislander

Front and rear camera is working in morph after granting permissions on Meizu Pro5.

Keneda

@flohack said in OTA-22 Call for Testing Companion Post:

@l12853 Then wait after OTA-22 maybe it improves... Release is tomorrow

Not for all device at once, it can take a week to reach owned device, i precise this because if not, maybe he'll come and create thread "no update for my device".

flohack

The phasing of device updates is 1%/hr so after 100 hours every device can download the update - Note also that with this OTA we try to bring back the push notification so that people get informed when its ready.