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
Related
Hello,
NOTE: Please see new thread with ROMs for Amplifier, HDMI and S/PDIF:
http://forum.xda-developers.com/showthread.php?t=2596910
Here is a build of Android 4.4 KitKat based on CM11 from repo sync on 12/14/2013 for TAS5713 (Amplifier) outputs. See the end of this post for details on issues and potential workarounds.
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited.
TAS5713 (Audio Amplifier):
Download: http://www.magicandroidapps.com/download/cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip (171MB)
MD5SUM: 422c9a863b9292dd0f2db60f105b4fd1 *cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF/HDMI: Sorry, no build available yet.
Recovery: http://www.magicandroidapps.com/download/cm-11.0-recovery.img
MD5SUM: 21ef5dffca97cc803ed2351e3b34068d *cm-11.0-recovery.img
To install:
Boot into recovery mode:
Code:
fastboot boot cm-11.0-recovery.img
When Q has reached recovery mode:
1. choose "install zip"
2. choose "install zip from sideload"
From PC:
Code:
adb sideload cm-11-20131214-UNOFFICIAL-steelhead_TAS5713.zip
It is a good idea to wipe data and cache. If coming from my previous cm-10.2 image, it may be possible to avoid wiping data/cache.
Sideload gapps if desired:
pa_gapps-full-4.4-20131119-signed.zip http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.4-20131119-signed.zip (257MB)
MD5SUM: fa40f00fbdee7332bde93f51ee68218b
From within recovery, "install zip from sideload" and:
Code:
adb sideload pa_gapps-full-4.4-20131119-signed.zip
If cm11 gets stuck in a boot loop, then you probably need to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in. Do not put your hand on top of the Q until the small LED on top lights up.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
If you keep your hand on the Q while plugging it in, or if you put your hand on it too quickly, it will not enter the bootloader.
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and CM 11 seems to be work, but there are some functional and stability issues.
FUNCTIONAL AND STABILITY ISSUES:
I have seen stuttering occasionally in audio playback in Google Music.
Chrome Browser in Google Play Store says it's not compatible with this device for some reason. Pulling the .apk off a phone and "adb install" to Nexus Q seems to work fine. Make sure you are using the latest Google Chrome update with KitKat support. The previous version will crash on KitKat.
If you find any other issues, please let me know.
Do you know if this point is fixed in the newest 4.4 builds?
"2. I have seen stuttering occasionally in audio playback in Google Music."
Thanks anyway, great work hharte !
Nice work. Any progress on WLAN? I have no wired ethernet near any of my Q's. Do you need any help moving forward with this?
Thank you sir, love to see development for this device!
Sent from my CM powered Nexus Q
I got WLAN working over the weekend, will post an updated ROM tomorrow.
Can we add packages from the factory images? I was thinking of the tungstenLEDService.apk. I guess its responsible for indicating the volume on the led ring and so on. I really miss that feature on CM. Maybe the visualizer package too, I don't know what that does but it would be great if we could get the led music visualization back, because it looks really cool
Here is the apk's location in the extracted system image
com.google.tungsten.ledservice
/app/TungstenLEDService.apk
/lib/libtungsten_led.so
I think the packages is installed here on stock Q's
package name=com.google.tungsten.ledservice
codePath=/system/app/TungstenLEDService.apk
nativeLibraryPath=/data/data/com.google.tungsten.ledservice/lib
package name=com.google.android.tungsten.visualizer
codePath=/system/app/Visualizer.apk
nativeLibraryPath=/data/data/com.google.android.tungsten.visualizer/lib
Do we have the source for these packages? I checked the android source but could not find any TungstenLEDService, but Im not completly sure were to look.
My biggest thing is getting the led ring and visualizer working on it again those are the 2 biggest things that I miss
Sent from my Nexus 7 using xda app-developers app
"SPDIF/HDMI: Sorry, no build available yet."
If you want SPDIF/HDMI audio output, you could flash the normal cm11 builds, don`t you?
I updated the build with working WLAN in the first post. Again, this is for the audio amplifier only.
Basari said:
"SPDIF/HDMI: Sorry, no build available yet."
If you want SPDIF/HDMI audio output, you could flash the normal cm11 builds, don`t you?
Click to expand...
Click to collapse
In theory yes, but not sure that standard cm11 has support for Q yet.
hharte said:
I updated the build with working WLAN in the first post. Again, this is for the audio amplifier only.
In theory yes, but not sure that standard cm11 has support for Q yet.
Click to expand...
Click to collapse
You're a god, please stay at this. After I install this where do I send Bitcoins?
Can SPDIF used as the audio input source?
Hello
Is uvcvideo.ko kernel part is included in the kernel ?
Thanks,
TT
Nice, I will try the new build as soon as possible. I'm waiting for my third Q bought on eBay. My girlfriend would kill me if I started tinkering with the existing ones, working perfect with CM 10.2 running spotify. The main reason I want KitKat on these are the improvements in performance. I use the Q's as my primary sound system with Spotify using the "Spotify Connect" feature. Amazing piece of hardware, I love the sound from the built in receiver but I'm not an audiophile.
Merry X-mas and a happy new year!
Extra Nexus Q
mannberg said:
Nice, I will try the new build as soon as possible. I'm waiting for my third Q bought on eBay. My girlfriend would kill me if I started tinkering with the existing ones, working perfect with CM 10.2 running spotify. The main reason I want KitKat on these are the improvements in performance. I use the Q's as my primary sound system with Spotify using the "Spotify Connect" feature. Amazing piece of hardware, I love the sound from the built in receiver but I'm not an audiophile.
Merry X-mas and a happy new year!
Click to expand...
Click to collapse
First of all, THANK YOU!, secondly, Merry Christmas & Happy New Year! Lastly, I happen to have a factory sealed Nexus Q just sitting here waiting to be put to good use. The opened but never used Q I have is getting this build as we speak. Just couldn't sit back without saying thank you!
Has anyone done this yet? How was the install? I've never rooted anything so I'm a little nervous it looks difficult. Could someone make a youtube how to?
Unsafe volyme warning
hharte can you dissable the "Unsafe volyme warning" in this rom?
How do I get video out put from my nexus
Ok so I have everything installed but you said the hdmi doesn't work so what am I supposed to use to see anything?
DavidLattimerii said:
Ok so I have everything installed but you said the hdmi doesn't work so what am I supposed to use to see anything?
Click to expand...
Click to collapse
Don't worry, video signal still goes through the HDMI cable, you'll see everything if you connect your Q to a display. However this is a build that supports the built-in audio amplifier. It means you won't hear anything through HDMI, you'll have connect your device to speakers (with banana plugs) in order to enjoy its sound.
Thank you for your efforts hharte!
Sent from my Nexus S using Tapatalk
yes you should be able to use the standard CM 4.4 builds, for HDMI sound. As far as i'm aware CM does support the Nexus Q..?
Sent from my Nexus Q using Tapatalk 2
OK sorry for my confusion however I was confused because currently when I plug my Q in to the tv (i've tried 2) it shows nothing not even a black screen the tv registers it as nothing so I am wondering if I installed something wrong or am I booting to it wrong?
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.
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??
I hope this goes to the right place, if not can someone direct me to where it goes.
I'm having an issue with what appears to be the phone app. i can call out but when the recipiant picks up all they here is a beep like a old school fax whine. I've searched this issue and I'm at a loss. Phone is Oneplus 7t with 18.1 hotdogb with no Google.
Thanks for any help,
Lowdownin
It is not just the phone app from my digging. I am also having the same issue with Signal, as well as another dialler I have installed to test. It also happens when using a SIP client both in the Phone app and separately (Mizudroid).
Regardless of how the call is made (inbound to me or outbound to another), all they hear is a high pitch tone. I can hear them fine. Hitting mute stops the noise for them, however unmuting restores it.
I have checked and the phone records sound via the microphone and when in speaker mode and the playback is perfect.
As per @Lowdownin928, I am at a loose end. I am in the process of downgrading and will report if that has an effect.
New ROM released today, tried that first - https://download.lineageos.org/hotdogb. No change.
Downgraded to the last before the one I was having trouble with - lineage-18.1-20210926-nightly-hotdogb-signed.zip - however this has the same issue.
At this stage I cannot work out why the ROM could cause this but then using other ROM's does not fix, even when doing a full wipe. Something else is going on.
Am looking at reverting to a t-mobile or international ROM to go way back and see what happens. If that does not fix it then I am stumped, as it seem to not be hardware. Very, very strange.
OK, so have installed an original t-mobile version of Android 10.0.3 for the 7T and low and behold, it works perfectly. No issue with outbound calls from SIM or SIP, did not bother testing further.
For reference, factory default t-mobile rom I used was at https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/, put phone in EDL mode and run the MDM. Came up fine.
Proceeded to System Update to v. 11.0.1.4.HD63CB. Reboot then tested for outbound noise on calls - no problems at all.
So at this stage the only way to fix this is to revert to the stock ROM, even with 11 it works fine. I have no idea what has happened with the LineageOS ROM but there is a fault somewhere. I am heading off to ask the question (and hope you will as well) but hope all this detail gives you an idea of where to go.
Just had a thought - there may be other ROM's that work fine, it could only be LineageOS that has this issue. If you don't need the feature set then look around in here.
Super surprised no-one else has had this issue, but there you go.
Success. Thanks to LuK1337, Lineage Team Member on the Reddit Support area this seems to have cleared the issue.
---
T-Mobile firmware isn't supported, you can flash retail one by following https://wiki.lineageos.org/devices/hotdogb/fw_update
---
So bootloader, flash lineage recovery, enter fastboot mode inside lineage recovery, flash all the .img's as laid out and then follow the rest of the install. Took a long time and careful reading but this was the key for the phone noise.
Thanks LuK1337.
Just wanted to let you guys know that I was also having the same issue and this solved it for me. Thanks so much dmc.kiint and LuK1337
hi, I have a moto g8 plus and I want to use Lineage but my devices isn't under the supported devices list. is there a working unoffical lineage build that is opensource for the moto g8 plus?
and if there is no build, how much work is it to port lineage to a new device and what knowledge is needed?
thx for your answers beforehand
I used @waltermobile's guide for 17.1 https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83094247
plus @AndyYan's 18.1 build: https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105
stormarrest said:
Seems fine so far - bluetooth audio wasn't working at first, but this workaround fixed it: https://forum.xda-developers.com/t/did-anyone-apply-gsi-on-moto-g8-plus.4066961/post-83397105
Click to expand...
Click to collapse
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue? I'm thinking of installing it; i'm tired of waiting for a custom ROM. thanks.
gfrank227 said:
Are you still using this? Any additional quirks or oddities besides the known bluetooth issue?
Click to expand...
Click to collapse
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.
stormarrest said:
Yes! After it took 5 days to set up, I was loath to throw any more time after it
The only other problem I've seen is that I can't join Zoom meetings – I'm able to log in, but either clicking a link or entering a code just dumps me back on the app's main screen. Other meeting / call apps work fine.
Click to expand...
Click to collapse
OK thanks for the info.
I attempted to install Lineage 19.2 on my moto g8 plus but it got stuck on the curved line and circle screen. i'm not even sure if I flashed it correctly; this is literally my first time trying to flash a whole GSI/Rom on any phone. Any advice or instructions would be appreciated (I used TWRP; after it was done flashing and I tried to restart it gave a warning that there was no OS; not sure how that's possible, and I still got that curved line screen). In short, I am not sure if it's the .img file I used or the flashing method, or perhaps even both.