Database Info

CM-11 testing for sm-t325 (mondrianlte), no radio support

I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!

Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?

THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.

crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)

Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.

crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?

works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?

THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).

crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !

Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.

crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)

THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta

crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?

megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..

I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.

megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.

crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance

THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?

crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework

THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.

So CM 14 is out for KLTE and is 90% stable, who wants to try on sprint?

Link to download it here (credit to AICP CM devs on their google plus page): https://plus.google.com/101577397694816898663/posts/GS4FcdKVomX
From the comments of the post, this is a write up of what is working:
I did dirty flash and all still works. I'd love to see a change log but I know that's asking a lot.
Boot time was fairly quick after flash approx 60 secs.
File explorer still can't see the sd card but as optix told me before, you can use rootbrowser app or just go to settings storage and you can see and manipulate sd.(I believe it's due to a superuser issue not related to ROM.)
BT worked fine for me last night on previous build except when not using it auto disconnected but as soon as media was played again it auto connected and plays normal. Will test BT further.
Also I know that cm theme manager is based on cm's C-apps and it's code base hasn't been updated to work in SDK 24 ie n-7.0 but I'm sure that will come soon.
There is a delay when connecting calls. The delay seems less when placing calls then when receiving. As long as the caller is patient it does connect. This might not be a Rom issue as I use Greenify and I've read some where that this issue had been encountered on other Roms.
As long as you can deal with the stock N theme, 20-30 ssecond call cconnect delay, and not having Xposed untill it's updated to work on SDK 24 then this is totaly daily driveable.
PS thank you to the Devs, please tell me how I can be of service helping or testing and I'm all yours.
Click to expand...
Click to collapse
Who wants to try?

not i, said the fly. still happy with MOAR 7.0

following nightlys
I have the sprint g900p and am following the nightlys build for cm 14, so far I've ran into a few issues, rotate doesn't always work, it is dependent on app. YouTube works but the stock cm chrome will not. Also I cannot send any SMS unless I force the radio to move from LTE to 3g.
And of course the SD card issue.
Just so you know, started with stock ROM, updated everything, clean Odin flash with twrp.
If you need any info let me know otherwise I'll post as I find bugs.

How to flash device driver binaries? Fix Pixel Mic/Audio issues?

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

Microphone not working...

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??

is there a working build of lineage 18 for moto g8 plus?

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.