Database Info

Unbelievable. Oneplus claims that a bug is now a feature.

Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!

I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie

MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.

nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!

nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all

kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.

So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders

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

call recording with Pixel 4A & Android 11

Call recording is important enough for me that I've stuck with a Samsung S5 for the last five years now solely to ensure all my calls are recorded. Sadly this phone is close to dying and I was interested in the Pixel 4A.
On the ACR reddit page it mentions that true two-way-call-recording from the audio source should be possible on Android 11 by rooting the phone and installing something called the Magisk repo with the “callrecorder-skvalex” module. I'm just looking for reassurance that this will work with the Pixel 4A before I buy it please.
Also, other than voiding the warranty is there any issues that arise with rooting your phone? Are you still able to download apps from the google play store with a rooted phone?
edit: I would be buying the UK version if that makes a difference.

Rooting your phone will make your phone less secure but as long as you use common sense when it comes to the apps and modules you install you should be fine. Google Pay will not work on a rooted phone (unless you spoof safetynet), but you will keep all google play functionality. Ive noticed that netflix disappears from Google Play when your phone is rooted, but you can just download it from a mirror site or the Aurora Store.
I havent personally used the module you mentioned, so i cant comment on whether or not itll work. And of course unlocking the bootloader will factory reset your device.

mickelsharples said:
Call recording is important enough for me that I've stuck with a Samsung S5 for the last five years now solely to ensure all my calls are recorded. Sadly this phone is close to dying and I was interested in the Pixel 4A.
On the ACR reddit page it mentions that true two-way-call-recording from the audio source should be possible on Android 11 by rooting the phone and installing something called the Magisk repo with the “callrecorder-skvalex” module. I'm just looking for reassurance that this will work with the Pixel 4A before I buy it please.
Also, other than voiding the warranty is there any issues that arise with rooting your phone? Are you still able to download apps from the google play store with a rooted phone?
edit: I would be buying the UK version if that makes a difference.
Click to expand...
Click to collapse
Check out this article see if any of these apps might work for you: https://www.androidauthority.com/best-call-recorder-apps-android-1001838/

7oey said:
I havent personally used the module you mentioned, so i cant comment on whether or not itll work. And of course unlocking the bootloader will factory reset your device.
Click to expand...
Click to collapse
Cheers for the info. Sounds like you Magisk... can I ask what method or guide you used to root your pixel and install Magisk?

mickelsharples said:
Cheers for the info. Sounds like you Magisk... can I ask what method or guide you used to root your pixel and install Magisk?
Click to expand...
Click to collapse
Use the standard patching of boot.img then boot it and direct install of magisk. Google hosts their own factory images where you can get the boot image.
Here's the guide: https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773

mickelsharples said:
Call recording is important enough for me that I've stuck with a Samsung S5 for the last five years now solely to ensure all my calls are recorded. Sadly this phone is close to dying and I was interested in the Pixel 4A.
On the ACR reddit page it mentions that true two-way-call-recording from the audio source should be possible on Android 11 by rooting the phone and installing something called the Magisk repo with the “callrecorder-skvalex” module. I'm just looking for reassurance that this will work with the Pixel 4A before I buy it please.
Also, other than voiding the warranty is there any issues that arise with rooting your phone? Are you still able to download apps from the google play store with a rooted phone?
edit: I would be buying the UK version if that makes a difference.
Click to expand...
Click to collapse
I'm in the same exact boat as the OP. Galaxy S5, trying to find a phone to maintain call recording. Am trying a G950F first, but so far not looking good. Tmobile SIM in it to undo RMM=Prenormal and cell signal is terrible. 1 to 0 bars, -115dBm LTE signal (-120dBm being the 'worst' as I've learned). So considering the Pixel 4a despite wanting more storage than 128gb. Would prefer OnePlus except the size is to...not something I want to try to fit in my pockets, despite having large hands that would like a larger phone.
Very interested in hearing peoples rooting experiences on Pixel 4a and call recording functionality.

I'm coming from an S7 myself. My 4a has Android 11 installed and with the Callrecorder app from Skvalex + the corresponding Magisk module, call recording worked perfectly. After thinking how many times I actually needed the recorded call on my old S7, I decided to get rid of the call recording app.

Latest version of Boldbeast Recorder with their Magisk module works perfect

I am sad to report that skyvalex call recorder does not record calls on my new pixel 4a 5G and I just emailed the developer about it. It used to work on my pixel 3a with android 10.
The program runs and creates audio files of the expected length, but when you play them back, there is no audio. And, yes, my phone is rooted with magisk and has the skyvalex magisk module installed. I suspect that something has changed in android 11 that is keeping it from capturing the audio.
I shall now try boldbeast since beeshyams says it works for him.

yaconsult said:
I am sad to report that skyvalex call recorder does not record calls on my new pixel 4a 5G and I just emailed the developer about it. It used to work on my pixel 3a with android 10.
The program runs and creates audio files of the expected length, but when you play them back, there is no audio. And, yes, my phone is rooted with magisk and has the skyvalex magisk module installed. I suspect that something has changed in android 11 that is keeping it from capturing the audio.
I shall now try boldbeast since beeshyams says it works for him.
Click to expand...
Click to collapse
Thank you for sharing your experience. I'm expecting delivery of a 4a 5g and want calling recording. So I'm hopeful that you making Skyvalex aware might accelerate the development of a fix.
Also, I don't know if this will be of help, but in my research last year I encountered this comment on an XDA article (thank goodness I bookmarked things!):
" Lexxior • 8 months ago • edited
It still works on Pie and Q if you have root. Just install app systemizer from Magisk and turn your desired call recorder into a system app. I have been using ACR for months this way and it works flawlessly."
https://www.xda-developers.com/android-11-call-recording/#comment
maybe if you can't find a app to work with root systemizing will still work well on Android 11 as well.
Edit: did some more searching around, came across an interesting post on BoldBeast. last post in thread by Admin:
https://www.boldbeast.com/forum/top...issions-for-android-11-for-pixel-2-xl-p2.html
apparently latest version of boldbeast should work fine on Android 11 according to developer.

yaconsult said:
I am sad to report that skyvalex call recorder does not record calls on my new pixel 4a 5G and I just emailed the developer about it. It used to work on my pixel 3a with android 10.
The program runs and creates audio files of the expected length, but when you play them back, there is no audio. And, yes, my phone is rooted with magisk and has the skyvalex magisk module installed. I suspect that something has changed in android 11 that is keeping it from capturing the audio.
I shall now try boldbeast since beeshyams says it works for him.
Click to expand...
Click to collapse
Aha! The skyvalex developer figured it out after I contacted him and sent logs! The problem was that I was connected to wifi and so the phone was using VoLTE, or VoIP, or Wi-Fi for calling. None of these can be recorded - only calls using the phone network.. So I turned off wifi and then the calls were properly recorded on the 4a 5G using skyvalex call recorder with the magisk module. I am happy that I can get high quality phone call recording again.
This limitation is caused by android, not the app and is documented in the faq here: https://callrecorder.skvalex.com/faq I checked and the boldbeast app has the same limitation: Only normal calls can be recorded, wifi calls can't be recorded no matter what recorder you are using, so if your phone supports the wifi call feature please disable it.
I am going to create a simple tasker scene that will turn off wifi whenever I place or answer a phone call - I think that may solve the problem for me. If you get empty recording files, try turning off wifi before starting your call and tell us what you find.
---------- Post added at 11:27 PM ---------- Previous post was at 11:02 PM ----------
Oh, I forgot to mention that I found out through some google searches that you can also record phone calls by using the built-in screen recorder BUT you do have to have speakerphone on or it won't hear the person on the other end.
Not an ideal method as it records not only the audio but also whatever is happening on the screen but it could be useful in a pinch. To make it easier to access, you can drag the Screen Record icon to the first page of the Android Quick Settings. I used this method a couple of times before the dev helped me get skyvalex working again by turning off wifi. The resulting files are bigger than you would like because they include a video of the screen but you could always extract the audio only if you wanted/needed to.

Android 12 Beta GSI Moto G 5G Ace Kiev development

update to more stable gsi 12

Hi, I have the moto one 5G ace, and I am very happy that we can get android 12 on it now. I have a few questions though.
A) how do I get android 11, when I try to update, it says android 10 is the latest version on moto updates.
B) where is the vbmeta, I am assuming google's GSI website.
C) does this GSI continue to receive android 12 updates?
Also, if you could friend me on discord at TheNextGamer21#9216, I have a team of developers that could help build a GSI for this device

Found the most stable Android 12 gsi for both the moto g 5 g kiev and moto g 5 g stylus.
I've tested both now for over a week as daily drivers and the gsi rom is 98% stable.
Has transformed my phone into a pixel...running Android 12..
Now there is bugs and some compromises one has to accept if you want this rom as a daily driver.
Working.
5g,lte,2g
Wifi
Bluetooth comes on and connects.
Magisk Alpha
R/W script
GPS
In call volume
Pixel goodies launcher etc...
Google camera video and pictures
Torch
Fingerprint pin and pattern
Viper4droid preinstalled under misc features
Headphone
More
Bluetooth in call audio and music audio playback
Google Pixel Always ON DISPLAY with clock animations
Gapps and Non-Gapps versions
Cons
Calls, mms, sms over 2g /3g only (working on it)
**use a free calls and text app example. "textnow" grab a free line and have calls ,mms,sms over 5G****
No moto gestures( I only use the chop for flashlight) workaround,,,app called "gravity
gestures" works perfectly..
Ill link the thread.
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...
forum.xda-developers.com

@jhjhjhjhjhjh Did you have to do anything special to get BT working on the Kiev with that Android 12 GSI? I can't seem to get it working at all. It tells me to try to turn my bluetooth device on and off.

GCPDetective said:
@jhjhjhjhjhjh Did you have to do anything special to get BT working on the Kiev with that Android 12 GSI? I can't seem to get it working at all. It tells me to try to turn my bluetooth device on and off.
Click to expand...
Click to collapse
(outdated, search in the telegram group of Nairo the unofficial rom)
Hello everyone! I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim. Warning: I don't take any responsibility if...
forum.xda-developers.com

Thanks for the link. I tried that yesterday but whenever I attempt to connect my BT device the whole phone locks up and freezes. Everything goes back to normal if I turn of the BT device.
EDIT: Saw in another thread you were having issues with the "e" build. Going to try and install the prior build and see if that resolves my issues.

GCPDetective said:
Thanks for the link. I tried that yesterday but whenever I attempt to connect my BT device the whole phone locks up and freezes. Everything goes back to normal if I turn of the BT device.
EDIT: Saw in another thread you were having issues with the "e" build. Going to try and install the prior build and see if that resolves my issues.
Click to expand...
Click to collapse
no worries..
let me know how its working for ya..
lastly, my Bluetooth had a slight delay when watching videos so to have Bluetooth working like stock. grab the "BTFM.bin " file from the stock firmware folder and flash it in fastboot mode.
code ..
fastboot flash bluetooth BTFM.bin
still working on VOLTE....

@jhjhjhjhjhjh Still no luck. I decided to check if maybe my BT device would work during phone calls and to my surprise it does. So it just seems to be something with media playback.

GCPDetective said:
@jhjhjhjhjhjh Still no luck. I decided to check if maybe my BT device would work during phone calls and to my surprise it does. So it just seems to be something with media playback.
Click to expand...
Click to collapse
Weird ...I followed the instructions to the tee. Bluetooth works here..

As soon as the bugs are out I'll hop on this.

Where is the development at with this I just seen it and a few questions
You state r/w script, meaning we can get r/w as in "/" mounted rw?
2nd and this is the deal maker, scoped storage, fused storage, adoptable storage.... All that trash that's stopping a lot of functionality of apps, is this a problem in this build?
Lastly and just for **it's a giggles, is there any where you can point me that I can grab one of these roms, not saying it's this easy but for my fingers sake we'll just jump on the sci-fi wagon for a sec, load it up on my PC change what I want to change flash to my phone and not disrespecting the makers, keep it to me.
Is that a dream or reality

jhjhjhjhjhjh said:
Found the most stable Android 12 gsi for both the moto g 5 g kiev and moto g 5 g stylus.
I've tested both now for over a week as daily drivers and the gsi rom is 98% stable.
Has transformed my phone into a pixel...running Android 12..
Now there is bugs and some compromises one has to accept if you want this rom as a daily driver.
Working.
5g,lte,2g
Wifi
Bluetooth comes on and connects.
Magisk Alpha
R/W script
GPS
In call volume
Pixel goodies launcher etc...
Google camera video and pictures
Torch
Fingerprint pin and pattern
Viper4droid preinstalled under misc features
Headphone
More
Bluetooth in call audio and music audio playback
Google Pixel Always ON DISPLAY with clock animations
Gapps and Non-Gapps versions
Cons
Calls, mms, sms over 2g /3g only (working on it)
**use a free calls and text app example. "textnow" grab a free line and have calls ,mms,sms over 5G****
No moto gestures( I only use the chop for flashlight) workaround,,,app called "gravity
gestures" works perfectly..
Ill link the thread.
[GSI][UNOFFICIAL][12] Pixel Experience
Pixel Experience for GSI What is this? Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation) Their mission is to offer the maximum possible stability and...
forum.xda-developers.com
Click to expand...
Click to collapse
What carrier are you on? I tried the latest pixel experience on at&t and had issues with calling and texting (when on 3g preferred network it shows no service but when on LTE only the data works- calls and messages don't go through)