Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
I have thé same trouble sincères thé Google voice match was updated
Same issue for me, in Italian language.
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Homestar1217 said:
Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
Click to expand...
Click to collapse
It's currently the same on all roms, it's working if you use a gsi
Flatric said:
It's currently the same on all roms, it's working if you use a gsi
Click to expand...
Click to collapse
Good to know I'm not alone!
You are not alone! This happened to me a few weeks back. All my searching leads to gapps verification, or shall I say use of gapps instead of built into system. This feature does work once again using gsi with Google apps pre-installed as well as pixel exp ROM, as they are verified there.
Sent from my Mi MIX 2S using Tapatalk
Hi,
Same problem here in french language.
Voice Match used to work last week. Activation by pressing home is not working too.
I have to launch the app by clicking it
I have solved with last update MIUI Global 10.0.9.0
duraaraa said:
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Click to expand...
Click to collapse
I am still having this problem.
Same here, it stopped working about a week ago. Tried everything: retraining model, changing language from “English (Ireland)” to “English (United Kingdom)”… nothing works. I have to press the button to activate the assistant. I'm using the Pixel Experience ROM by Psy_Man – amazing ROM BTW, super stable.
Which version of the Google app do you use? I installed the 8.65.6.21.arm64, and Voice Match works on it.
I am experiencing the same issue ever since I flashed AEX. Pixel Experience was working fine and no issue with assistant but after the problem appeared all ROMs stopped working. I am currently on MIUI global because it's so far the only ROM that has it working, but it still requires faceunlock/fingerprint to unlock the phone though it does wake up by saying OK Google.
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
jamesyuli said:
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
Click to expand...
Click to collapse
I tried out OctopusOS ROM GSI. Very stable, could be a daily. I used it for a few days. But I prefer to be able to use a true dark theme. Didn't have issues with Google hot words at all. A few tweaks and some magisk modules help it out.
https://forum.xda-developers.com/pr...led-device-development/9-0-octopusos-t3859233
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havok.
Voice Match is working again in latest AOSIP
Flatric said:
Voice Match is working again in latest AOSIP
Click to expand...
Click to collapse
There's also a changelog entry for PE that hotword enrollment was fixed! More stuff to try!
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
noobtoob said:
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
almost 24 hours so far on the 12/30 build of Pixel Experience with no issues. The rom just runs flawlessly, and I love the pixel live wallpapers. OK Google still working with none of the voice options greyed out. Android wear device working too (Explorist 4). Auto bright, and lock/unlock good too. Battery seems good so far. These points aren't relevant, but everything else seems to work good.
I know Pixel experience is not very dense on details for install so here's my process.
Use MiFlash to flash fastboot version of latest developer rom
Re-flash TWRP, enter wipe menu and wipe (Not format, NOT the one you have to type y-e-s) the first four options, Dalvik, Cache, System, and Data.
Flash your rom
Boot! (Regardless of whether or not it makes a difference, I like to let it sit on the first screen for a little, and then after 2-5 mins, I'll restart, before setting it up)
Oh! And I've had less issues since I installed MIUI, went into settings, and Signed out of my Mi Account. Not sure if it makes a difference, but I no longer have to "authenticate" and unlock after I install MIUI. This confused me because I read that unlocking BL automatically disables find my phone, but evidently not.
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Gopena said:
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havoc.
Click to expand...
Click to collapse
1/3 Didn't post this yesterday, I tried Havoc as well and it behaved like miui, no OK Google to wake & Unlock, but ok google from lockscreen brought up the pin pad, and unlocking with pin or FP would allow google assistant to activate. Havoc also had no bluetooth audio.
Related
Hi, Just wondering if anyone is able to get smart unlock working on Mi4c? Tried numerous things but can't get it working.
which rom you are using?
CM13 and MIUI roms are all fine
I'm using the xiaomi.eu rom, maybe thats the issue
colb16 said:
I'm using the xiaomi.eu rom, maybe thats the issue
Click to expand...
Click to collapse
actually I tested xiaomi.eu rom with my friend, smart lock works fine . But we are using miband, not other bluetooth devices.
I was trying to get it working for home location but it didn't work. So frustrating having to input passcode each time!!
Works fine with my miband, sMIUI ROM (xiaomi.eu base)
I've read places that it works with miband alright. Just setting locations etc that the issue arise's
colb16 said:
I was trying to get it working for home location but it didn't work. So frustrating having to input passcode each time!!
Click to expand...
Click to collapse
I believe this is a bug within android itself. I have an HTC One and tried to use the trusted places smart unlock as well a few months back but it never worked. Just try to google "smart unlock trusted places" and you'll see that lots of people have the same issue.
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
I want to know how do I flash any if the files found on Google's developer site. (https://developers.google.com/android/drivers#sailfish)
It gives *.tgz files.
The reason for this is that my pixel has been cursed with the dreaded mic issue. I hope that flashing a driver image could help restore some functionality. It has now even spread to my speakers, the phone can't produce audio and videos and audio don't play unless through a Bluetooth device. AUX is not functional.
First it was just the mic giving issues and I good just reboot the phone and it would work again for some time. But now rebooting does nothing and now I can't even hear sound to play a video or game. Please help.
Just to give more description I want a way either via fastboot or adb or through the Recovery to install these files, if possible. Would it solve the issue?
Other issues include not being able to swipe to answer calls and the phone freezes if I do. Apps crash sometimes if they require audio output.
Same issue here (Searching for a used dead phone - 2017 manufactured, maybe screen cracked, body damage etc. So that I can replace the mobo as most of them say this is the way to fix it).
I saw some comments in Google forums that ''Android P beta builds'' fixed the issue for some. Wanted to try that, but I am not able to find beta links (As beta is over)
Installing drivers is worth a try.....Even I would like to know
So anybody has any ideas yet? Anything software wise at all?
Try flashing some custom roms and kernels
**FIX** unlock BL, twrp3231, pixeldust 9.0 ROM, magisk 18.1
Hey friends I was having same issue after stock to 9.0 update (with all patches up to today 3-9-19) on my pixel, first it wouldn't read a Sim and I unlocked the bootloader and used adb to fix that by resetting the modems, then less than 24 hours later it dropped the mic and then sound all together (probably with one of the first updates).
So I updated the phone completely and still no mic no audio. Checked xda and only found this thread. Tried 4 times to download the Google fix and every time it failed so I can't say if the adb sideload fix works but I had already prepped the twrp room and magisk files so I proceeded with that after 24 hours and no solution I could find.
Much to my satisfaction as soon as the rom was loaded (pre magisk) i heard audio. Continued to root and came out with sound and mic and mobile data finally! Pixeldust is very nice so far, snappy and lots of options though maybe a more mellow graphic designer for the stock wallpaper is called for!
Donz7733 said:
Same issue here (Searching for a used dead phone - 2017 manufactured, maybe screen cracked, body damage etc. So that I can replace the mobo as most of them say this is the way to fix it).
I saw some comments in Google forums that ''Android P beta builds'' fixed the issue for some. Wanted to try that, but I am not able to find beta links (As beta is over)
Installing drivers is worth a try.....Even I would like to know
Click to expand...
Click to collapse
Looks like you could try Android q beta now if you want
Sent from my Pixel using Tapatalk
thewraith420 said:
Looks like you could try Android q beta now if you want
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yeah planning to try it out
melchpro said:
**FIX** unlock BL, twrp3231, pixeldust 9.0 ROM, magisk 18.1
Hey friends I was having same issue after stock to 9.0 update (with all patches up to today 3-9-19) on my pixel, first it wouldn't read a Sim and I unlocked the bootloader and used adb to fix that by resetting the modems, then less than 24 hours later it dropped the mic and then sound all together (probably with one of the first updates).
So I updated the phone completely and still no mic no audio. Checked xda and only found this thread. Tried 4 times to download the Google fix and every time it failed so I can't say if the adb sideload fix works but I had already prepped the twrp room and magisk files so I proceeded with that after 24 hours and no solution I could find.
Much to my satisfaction as soon as the rom was loaded (pre magisk) i heard audio. Continued to root and came out with sound and mic and mobile data finally! Pixeldust is very nice so far, snappy and lots of options though maybe a more mellow graphic designer for the stock wallpaper is called for!
Click to expand...
Click to collapse
how do you reset modems ? my pixel dont read a sim
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??
Hi,
Those who installed LineageOS on T5, could you please share your experience ?
I noted from few comments on this forum:
5GHz Wifi is not working but 2.4 GHz is working fine
disable HW overlays in the dev options to remove blur
disable AudioFX to correct sound
Is there any other prooblem ? What about bluetooth, camera, GPS, gapps ?
Any feedback will be appreciated
I'm the one who said it didn't work on 5GHz wifi, it is working.
I had to wait several minutes until my AP appeared, once I connected for the first time it did not give me any problem.
Also something like this happened when starting LineageOS for the first time, it did not connect neither in 2.4 nor in 5 but waiting it worked.
After disabling AudioFX I installed Eqfy Equalizer which works fine.
The camera app is not working, a white line appears in the middle of the screen and there are no photo options or anything.
Since I don't use it to take photos, I have not tried more but I suppose that with some other camera app it should work.
Not tested bluetooth or GPS for now.
On the other hand, the tablet works more fluidly and you have more free space.
In the absence of trying more things, for now I'm sticking with LineageOS.
Thanks for your feedback.
I have flashed LienageOS 16, and have patched RAMDISK.IMG to install Magisk.
It looks OK, I like it so far. There are only two issues:
* Camera is not working
* I have only 2,4Ghz WiFi (which btw is working fine), but I do not see 5,0 GHz network in my list
GPS, bluetooth, sound, image,...everything seems working OK, but I didn't check in details.
Despite those two issues I will stay with LineageOS. I prefer it one hundred times over EMUI. And for camera, which btw is not very important to me neither, I will probably find a fix one day.
From time to time your 5GHz AP may appear, you can connect but then it disappears again.
Yesterday I checked, I thought it was connected in 5GHz but no, the connection was in 2.4
I confirm that the Wifi in 5GHz does not work.
borja113 said:
Thanks for your feedback.
I have flashed LienageOS 16, and have patched RAMDISK.IMG to install Magisk.
It looks OK, I like it so far. There are only two issues:
* Camera is not working
* I have only 2,4Ghz WiFi (which btw is working fine), but I do not see 5,0 GHz network in my list
GPS, bluetooth, sound, image,...everything seems working OK, but I didn't check in details.
Despite those two issues I will stay with LineageOS. I prefer it one hundred times over EMUI. And for camera, which btw is not very important to me neither, I will probably find a fix one day.
Click to expand...
Click to collapse
I have sorted it out.
For WiFi, I changed the channel on my router, put it at 44, and now the 5,0 Ghz Wifi is visible and I can connect.
For camera, I have found a Gcam which works OK, it is "GC_4.1.006.126161292-41003513.apk", easy to find on XDA.
So now I have LineageOS fully working. For the time being everything is fast and stable.
Kgonla said:
From time to time your 5GHz AP may appear, you can connect but then it disappears again.
Yesterday I checked, I thought it was connected in 5GHz but no, the connection was in 2.4
I confirm that the Wifi in 5GHz does not work.
Click to expand...
Click to collapse
I thik it is related to router. On my router, in settings, the choice of channel was set to automatic, I put it to 44 and it is visible, and the connection is fast and stable. For some reason the tablet doesn't see higher frequencies.
borja113 said:
I thik it is related to router. On my router, in settings, the choice of channel was set to automatic, I put it to 44 and it is visible, and the connection is fast and stable. For some reason the tablet doesn't see higher frequencies.
Click to expand...
Click to collapse
I'm going to take a look to Gcam, I've tested a couple of cam apps but not working.
Now I'm using channel 56 but previously I tested other channels, maybe the day it worked I was using a lower one, will test too.
Thanks a lot.
borja113 said:
I have sorted it out.
For WiFi, I changed the channel on my router, put it at 44, and now the 5,0 Ghz Wifi is visible and I can connect.
For camera, I have found a Gcam which works OK, it is "GC_4.1.006.126161292-41003513.apk", easy to find on XDA.
So now I have LineageOS fully working. For the time being everything is fast and stable.
Click to expand...
Click to collapse
Hello again, I have changed the channel to 44 and for now it works fine.
The Gcam is not working for me, It tells me that it cannot find the camera and closes.
Kgonla said:
Hello again, I have changed the channel to 44 and for now it works fine.
The Gcam is not working for me, It tells me that it cannot find the camera and closes.
Click to expand...
Click to collapse
Hello. If this can be of any help: the Gcam which I installed, I found it on this thread:
https://forum.xda-developers.com/huawei-p20/themes/google-camera-huawei-p20-kirin-devices-t3882198
It is : Google Camera v4.1.006.126161292, in the first post, section OTHER AVAILABLE APKs.
Maybe we’re not using the same version.
After flashing LineageOS, I found that I had two cameras : HwCamera2.apk 8.0.0.200 which I think is Huawei camera, and Camera2.apk 2.0.002. First one was crashing immediately, the second one didn’t work with a white line in the middle. Now I have first one disabled, second one is still there but useless. And third one is the one above which is OK.
Has anyone had any luck with Netflix?
I tried LineageOS yesterday and was unable to install Netflix from the play store, likely because it said I was uncertified. I was however able to download and side load Netflix, which initially appeared to resolve the issue, however any attempt to play content resulted in a 5.10 error. From what I can tell, this appears to be something to do with DRM, however the few potential solutions I've found using Magisk didn't help resolve the situation, and I've ended up reverting to Emui
Aside from Netflix, I didn't come across any other issues while testing. Unfortunately for me, Netflix was the main reason for getting this tablet in the first place, my old 3rd Gen iPad would have been more than adequate for my needs other wise
In order to get Netflix work, I installed one older versions found on apkmirror. I picked up randomly 6.21.0. I installed also liboemcrypto_disabler (even though I do not know if it was necessary), and in addition of that it is hidden in Magisk. It is working, I do not know how to check the quality, but I guess it is 720p.
Why TWRP needed why not to flash directly from stock recovery...
If you want to install LineageOS, the TWRP is not needed. You flash LineageOS via fastbot. In fact, it is better not to mess with TWRP, officially it is not supported by OpenKirin ROM's.
I also thought so but it's ok I have LineageOS installed with OpenCamera everythink seems to be working fine even LTE is there 16.1 version available ?
and also where can I get stock recovery if I need it, is it available for download anywhere ? or after LineageOS instalation it also installs stock recovery ?
If you want go to stock recovery again, On OpenKirin site there are comprehensive guides, under section Support, about where to find stock EMUI firmware, and how to extract and flash stock recovery image.
I do not think that LineageOS will install stock recovery, if you had TWRP before LineageOS installation, most likely it is still there. You may check it yourself : Vol Down + Power on boot.
I've just tried LineageOS build 6 on my AGS2-W09 and the camera seems to work ok now.
Had to install OpenCamera and set the all permissions, clear storage for this app and on the next run it can finally save the aquired photo.
The 5Ghz WiFi works with no problems (my router selected channel n.60)
As for audio: there is a glitch when device is booting, might want to not wear headphones during a reboot ☺
Haven't tried disabling AudioFX or installing Viper4Android as I am rolling back to stock firmware.
Netflix:
I think I konw why Netflix is not working: I have no IMEI with this OS.
UPDATE: IMEI should not matter on this device as it has no network.
I had tried the Netflix 6.21.0 version mentioned here and it gives me the same "Device failure occurred 501.-1006" error.
Then I've installed Kodi with a Netflix addon and it gives me: "It was not possible to get data from Widevine CryptoSession. Your system is not Widevine certified".
It is pretty clear that the LineageOS 16 build 6 (lineage-16.0-20201019-emui8-gapps.img) has no Widewine libraries installed.
Other than this the OS is very responsive, unfortunately I have to rollback because of this.
I am using this tablet for Netflix and prime on stock emui.
I really want to upgrade to custom ROM but no polished ROM anywhere!
guys how you have managed to pull boot.img from the device?
can anyone guide me through?
I have successfully managed to flash LineageOS latest build on MediaPad T5
kamilmirza said:
guys how you have managed to pull boot.img from the device?
can anyone guide me through?
I have successfully managed to flash LineageOS latest build on MediaPad T5
Click to expand...
Click to collapse
Can you share the entire installation process.
Thanks
bluestar778 said:
Can you share the entire installation process.
Thanks
Click to expand...
Click to collapse
For LineageOS 16 --> https://forum.xda-developers.com/t/twrp-lineageos-16-installed-in-t5.4161857/
For Latest build (LOS18.1) --> https://forum.xda-developers.com/t/...ation-guide-for-mediapad-t5-ags2-xxx.4291431/