Has anyone been able to get Google's call screening to work? I've seen some guides for older OnePlus devices, I was wondering how it would work for the 9.
I would love this as well. On my Oneplus 7T I was able to get it down by installing a lower version of the google dialer and doing some other stuff but the OP9 comes with the google dialer pre installed and it can't be downgraded (that I can find).
Root
Magisk
Google Dialer Framework
Done
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks!
Your screenshot doesn't show the call screening option though. I have those same exact things on my non rooted phone.
NotTheGiant said:
Thanks!
Your screenshot doesn't show the call screening option though. I have those same exact things on my non rooted phone.
Click to expand...
Click to collapse
It's not possible on non Pixel devices with recent phone app updates. It used to work with an older version, but not anymore. Even if you use an older version, it doesn't work anymore.
ram4ufriends said:
It's not possible on non Pixel devices with recent phone app updates. It used to work with an older version, but not anymore. Even if you use an older version, it doesn't work anymore.
Click to expand...
Click to collapse
Actually, you can get Google call screening to work on non pixel phones, I already got it to work on my OnePlus 9 Pro, but you need to have root. It's actually pretty easy on the OnePlus 9 series as the default dialer is Google. All you have to do after is:
Root phone, install BusyBox Magisk module and Magisk props module, change device fingerprint to Google pixel 5, restart then enable device emulation (do this using the props module just like changing device fingerprint), enable all settings except display.id and reboot. You'll have the call screening option now because it thinks it's a pixel 5. Problem with this method is you won't get system updates. But, once you know there is an update you can go into props module, revert all changes, revert Magisk, install update, re root and reapply the changes to get call screening working again.
jeffsga88 said:
Actually, you can get Google call screening to work on non pixel phones, I already got it to work on my OnePlus 9 Pro, but you need to have root. It's actually pretty easy on the OnePlus 9 series as the default dialer is Google. All you have to do after is:
Root phone, install BusyBox Magisk module and Magisk props module, change device fingerprint to Google pixel 5, restart then enable device emulation (do this using the props module just like changing device fingerprint), enable all settings except display.id and reboot. You'll have the call screening option now because it thinks it's a pixel 5. Problem with this method is you won't get system updates. But, once you know there is an update you can go into props module, revert all changes, revert Magisk, install update, re root and reapply the changes to get call screening working again.
Click to expand...
Click to collapse
Thanks for explaining all that. If the phone thinks it's a pixel 5, does that give you any problems anywhere else? Is there anything from oneplus that doesn't work anymore?
jeffsga88 said:
Actually, you can get Google call screening to work on non pixel phones, I already got it to work on my OnePlus 9 Pro, but you need to have root. It's actually pretty easy on the OnePlus 9 series as the default dialer is Google. All you have to do after is:
Root phone, install BusyBox Magisk module and Magisk props module, change device fingerprint to Google pixel 5, restart then enable device emulation (do this using the props module just like changing device fingerprint), enable all settings except display.id and reboot. You'll have the call screening option now because it thinks it's a pixel 5. Problem with this method is you won't get system updates. But, once you know there is an update you can go into props module, revert all changes, revert Magisk, install update, re root and reapply the changes to get call screening working again.
Click to expand...
Click to collapse
I had to uninstall the latest beta of the Google dialer and reinstall it to make it work in the end but big thanks for the guide! This was the main reason I rooted my phone lol.
Quick question, to revert the changes can we just do "reset all options/settings" in the props module? Or would we have to manually undo the steps?
Awesome, I got it working. Thanks!
I can't help but wonder if this would give us free photo storage after June 1 as well, since it thinks it's a Pixel.
NotTheGiant said:
Thanks for explaining all that. If the phone thinks it's a pixel 5, does that give you any problems anywhere else? Is there anything from oneplus that doesn't work anymore?
Click to expand...
Click to collapse
As far as I could tell, it only affected system updates. It also changes the VoLTE signature to pixel 5 that's sent to the network, although I don't think that negatively affects anything. It also makes the about phone screen show mostly blank information, but that's just cosmetic. Even when they're was a system update, it wouldn't show in updates until I referred changes.
toyanucci said:
I had to uninstall the latest beta of the Google dialer and reinstall it to make it work in the end but big thanks for the guide! This was the main reason I rooted my phone lol.
Quick question, to revert the changes can we just do "reset all options/settings" in the props module? Or would we have to manually undo the steps?
Click to expand...
Click to collapse
Yes, just use reset all options in props module to get it back to normal.
NotTheGiant said:
Awesome, I got it working. Thanks!
I can't help but wonder if this would give us free photo storage after June 1 as well, since it thinks it's a Pixel.
Click to expand...
Click to collapse
From what I read before, they're discontinuing free photo storage even on the pixel lineup. If they changed their minds since then and decided to keep it on pixels, then yes, this would give you the free storage as it thinks it's a pixel.
jeffsga88 said:
From what I read before, they're discontinuing free photo storage even on the pixel lineup.
Click to expand...
Click to collapse
It's for devices after the Pixel 5. The Pixel 5 will still have free "high quality" storage.
The about phone looks fine to me, but the settings search feature no longer works. Maybe that's not related who knows.
NotTheGiant said:
It's for devices after the Pixel 5. The Pixel 5 will still have free "high quality" storage.
The about phone looks fine to me, but the settings search feature no longer works. Maybe that's not related who knows.
Click to expand...
Click to collapse
My about phone has info missing. Settings search works fine through
toyanucci said:
My about phone has info missing. Settings search works fine through
Click to expand...
Click to collapse
Ok my bad, I have the same about phone page. I didn't realize it was saying "none" for processor and camera.
And here's what I see when I search the settings for "fingerprint" for example. It might be something else that I did if it looks fine for you.
NotTheGiant said:
Ok my bad, I have the same about phone page. I didn't realize it was saying "none" for processor and camera.
And here's what I see when I search the settings for "fingerprint" for example. It might be something else that I did if it looks fine for you.
Click to expand...
Click to collapse
Great guide, thanks
NotTheGiant said:
Awesome, I got it working. Thanks!
I can't help but wonder if this would give us free photo storage after June 1 as well, since it thinks it's a Pixel.
Click to expand...
Click to collapse
I switched to Amazon Photos since it provides unlimited photo storage including original size. Yay for Amazon, creepy company but the perks are awesome.
Found a big problem. My Google assistant no longer opens
Fixed it by going into the props module, then simulation then disabled all as shown in the screenshot. Upon reboot call screen still works and so does Google assistant and the info in about phone is once again correct.
Call screen disappeared after a while with this solution. I'll research some more how to fix the google assistant issue.
UPDATE
I found the fix here which is to flash a file in magisk to fix the assistant. Now everything works. I just need to remember to undo all of this whenever I'm gonna flash an Oxygen OS system update
toyanucci said:
Fixed it by going into the props module, then simulation then disabled all as shown in the screenshot. Upon reboot call screen still works and so does Google assistant and the info in about phone is once again correct.
Call screen disappeared after a while with this solution. I'll research some more how to fix the google assistant issue.
UPDATE
I found the fix here which is to flash a file in magisk to fix the assistant. Now everything works. I just need to remember to undo all of this whenever I'm gonna flash an Oxygen OS system update
Click to expand...
Click to collapse
Thanks! I haven't had any problems with the assistant so far, and my search issue fixed itself overnight somehow.
zymphad said:
I switched to Amazon Photos since it provides unlimited photo storage including original size. Yay for Amazon, creepy company but the perks are awesome.
Click to expand...
Click to collapse
Thanks, I'll look into that option!
Related
The app is now live on Google Play.
Thanks to all my beta testers for helping me iron out the wrinkles. I will still post beta versions here when I have new features that need testing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tired of entering your password all the time? SkipLock lets you skip past the lock screen when you're connected to a designated wifi or bluetooth device. When you're at home or in your car, your phone is safe and you don't need to be typing in that damn password all the time. When you're connected to your wifi network, or any bluetooth device, you can go straight to the home screen when you press the power button. You can even have it keep the phone unlocked while you're connected to a bluetooth keychain or headset. As soon as the phone gets out of range, it locks.
This is a public beta. SkipLock is a complete rewrite of Unlock With WiFi. Why rewrite it? This blog post explains the reasoning behind it.
Here are the new features in SkipLock:
Pattern and face unlock supported on rooted devices
Completely redesigned Android 4+ user interface
No background service = less memory usage and more reliable
No status bar icon required (but it’s still an option). Tray-only notifications also an option.
If you have notifications enabled, you can now tap the notification to instantly lock the device
Even more cool stuff coming later
Many of the existing features from Unlock With WiFi will also be in the new app. Some of them are:
Automatically turn off wifi when leaving home
Automatically turn on/off bluetooth
Automatically turn on/off sync
WidgetLocker integration
Lock delay has been removed because Android 4+ supports it natively now
If you have a bug to report, press Bug Report in the app's menu. This will send me some diagnostic information that will help me figure out what's wrong. This is the quickest way to get a response. You may post more general questions in this thread, and I will try to answer them, but bug reports sent directly to me take precedence.
SkipLock requires Android 4.0 or above. Root is required for patterns and face unlock. Only PINs and passwords are supported without root.
SkipLock FAQ
The FAQ is now being maintained on my website.
Crashes on startup on CM 10.2 M1 on HTC One
MajorGaz said:
Crashes on startup on CM 10.2 M1 on HTC One
Click to expand...
Click to collapse
sorry about that! it is the first release of the beta, so please bear with me. can you email me the log file? it's at /sdcard/SkipLock.log. send it to support at benhirashima dot you know what.
Crashes
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]
Bionic22 said:
This seems like a really great and useful app. However I can't seem to access it. Every time I click on the app it just crashes.
Running Droid Bionic with Jelly Bean [4.1.2]
Click to expand...
Click to collapse
sorry, corrupted apk file! i just uploaded a new one that works.
Ben74 said:
sorry, corrupted apk file! i just uploaded a new one that works.
Click to expand...
Click to collapse
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.
D3_ said:
Seems to work fine on my Nexus 5.
Only tested the WiFi setting though, not bluetooth.
Are there any plans to unlock with NFC too? I should be getting an NFC ring soon and I'd love for it to work with that, so when I grab my phone there's no PIN/password but when others get hold of it it requires a PIN/password.
Click to expand...
Click to collapse
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.
Ben74 said:
i would love to do that too, but unfortunately, the NFC reader is not active unless the phone is already awake and unlocked. that goes for most phones anyway. obviously, there are some exceptions, like the moto x.
Click to expand...
Click to collapse
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
hmm, that's interesting. maybe i'll look into it when i get a chance.
Installs now.
Will give it a whack when i get home
It works!
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.
Bionic22 said:
My phone was locked and by adding my WiFi network as an exception, the phone was automatically unlocked.
I'll test it out tomorrow when I leave my house and when I get back to see if it re-locks when i leave my wifi network/unlocks itself upon reaching my wifi network.
Click to expand...
Click to collapse
great! thanks for the feedback. try to test it with bluetooth too, if you can.
Also work on my SGS3 Omega v51 4.3
sent from my amazing SGS3 via Tapatalk
Is this time limited?
I don't know how you did it, but this works on stock rooted HTC One with pattern lock! Your previous app and some other apps do not, but this one works perfectly! When does this beta expire?
Take my money!
Side note: does not work on nexus7 with CM 10.2 (4.3) pattern always shows even when skiplock notification says its unlocked. Going to submit report from app
Thanks for this! I have missed this function since using HTC One. And will use this on my Nexus 5 when it arrives too
D3_ said:
True, but there are plenty of custom ROMs and even xposed modules which allow you to enable NFC with the screen off or with the screen on and the phone locked.
Still, if it's not something you're willing to add, there's nothing I can do to change that. The app works great as it is.
Click to expand...
Click to collapse
Yes, the S3 supports nfc from the lockscreen on some ROMs
My Feedback
Thank you for this great little software. You can also achieve this with software like lama or tasker. But I dont need such big toolkits. So your app fits perfectly on my device.
Here are my thoughts:
* starting an app when a network is in reach - great for car-users to start their favorite mp3-player etc.
* simple geofencing to re enable wifi/bluetooth
* turning on/off different system profiles (so you dont have to take care of all settings...it´s all build into the os)
Keep on coding!
working great on note 2 4.3 keep it up bro!
thanks for the feedback, guys. good to hear it's working! for those who asked, yes it's time limited. the current version will expire at the end of november, but if i feel that more testing is necessary, i will update the app and extend the time limit.
Since its now officially rolling out, I was wondering what other bugs people have spotted in B361 (and if known, any ways to fix/get around them).
For me so far I've notice
Android Pay -- Android Pay no longer works as its supposed to. It no longer works from any screen, and only works when the app is open. It also takes a very long time to respond even when it is open (I'm actually not certain that it's not working from the lock screen, but if it is, it takes far too long to respond)
Device security -- If you use a Google Apps account that requires device encryption, and that a password be required on restart, the system seems to report that these criteria are not met, even when they are. Device Policy will bombard you with notifications that they are not met, and prevent the account from syncing.
The first one is just extremely irritating, but really not that big a deal. Although I don't have huge issues not being able to sync the Google Apps account in question, I feel the second issue should be classed as critical, and should've been fixed before final release, because for some users this will be a dealbreaker.
Android Pay working fine for me.
oxfordmark said:
Android Pay working fine for me.
Click to expand...
Click to collapse
Well that's weird (but possibly good news). What cust version are you on? Did you get it on final release or from early update program? I even did a full wipe and the problem persists.
Android Pay is working fine for me aswell, C432 here, Updated from L09C432B182 to L09C432B361
esist said:
Well that's weird (but possibly good news). What cust version are you on? Did you get it on final release or from early update program? I even did a full wipe and the problem persists.
Click to expand...
Click to collapse
Hey
I'm C432 and went from B182 to the latest version on Saturday. I want part of the beta
Working great here too
166>>182>>>361
Used Huawei updater
Sent from my EVA-L09 using Tapatalk
Not sure if this is a bug or not but can any of you guys change the notification icon colours? For instance textra and whatsapp allow you to select the colour but it stays as white. Previous android versions worked fine.
i contacted huawei live support and they told me that if problems appear you should do a factory reset because of data migration issues, this helped me for example with lockscreen notifications
on 361 since last week and haven't found issues with Android Paid. I only unlock with fingerprint and place the phone over the nfc terminal.
theogkillzone said:
Android Pay is working fine for me aswell, C432 here, Updated from L09C432B182 to L09C432B361
Click to expand...
Click to collapse
That's really strange (that I'm having issues). It does seem to be entirely related to B361 cause it disappeared when I did a rollback to B182.... Have to tinker with it some more and find the cause.
OldDroid said:
i contacted huawei live support and they told me that if problems appear you should do a factory reset because of data migration issues, this helped me for example with lockscreen notifications
Click to expand...
Click to collapse
I did that. After I first experience issues, I rolled back, upgraded again, then did a factory reset.
dbesoli said:
on 361 since last week and haven't found issues with Android Paid. I only unlock with fingerprint and place the phone over the nfc terminal.
Click to expand...
Click to collapse
Is this what others have been doing?
This worked for me today. I remember it not working before but I'm really not certain.
But before I could pay for small transactions without unlocking at all, which definitely doesn't work since the update.
Maybe it's related to magazine unlock. I had it disabled before update but this doesn't seem to be possible anymore.
I find my whatsapp notifications are slow to come through , if they come through at all, anybody else have the same issue?
jpbroad1970 said:
I find my whatsapp notifications are slow to come through , if they come through at all, anybody else have the same issue?
Click to expand...
Click to collapse
Is it closing WhatsApp when the screen turns off? I did notice once that WhatsApp was open with WiFi on and messages weren't even going out until I went into Contacts and hit refresh (what I always do to force WhatsApp to retry to connect to the internet). But it was just a once off.
it seems to close , I will keep my eye on it. it only appears to be on the 1st one or two messages.......perhaps its just me lol
jpbroad1970 said:
it seems to close , I will keep my eye on it. it only appears to be on the 1st one or two messages.......perhaps its just me lol
Click to expand...
Click to collapse
Try disabling it closing it when the screen turns off.
Out of curiosity, do we know if there is any difference between the B361 that was released as early adopter, and the B361 that was released as final? There were two "full" packages, with different dates on them, both marked B361. As early adopter update, I got one with a kernel build date of 30 December.
Does anyone who got it as the "final" update know if theirs is actually the same? I know a different build date doesn't necessarily mean it had any changes beyond that, but just to know.
esist said:
Try disabling it closing it when the screen turns off.
Out of curiosity, do we know if there is any difference between the B361 that was released as early adopter, and the B361 that was released as final? There were two "full" packages, with different dates on them, both marked B361. As early adopter update, I got one with a kernel build date of 30 December.
Does anyone who got it as the "final" update know if theirs is actually the same? I know a different build date doesn't necessarily mean it had any changes beyond that, but just to know.
Click to expand...
Click to collapse
my build is 30th December, I was thinking about going back and then reloading the later firmware in case its any different
There are no NFC settings
Are you sure? You flashed rom for l19
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Debug USB keeps switching off whenever I go outside developer options..
esist said:
Is this what others have been doing?
This worked for me today. I remember it not working before but I'm really not certain.
But before I could pay for small transactions without unlocking at all, which definitely doesn't work since the update.
Maybe it's related to magazine unlock. I had it disabled before update but this doesn't seem to be possible anymore.
Click to expand...
Click to collapse
Yeah, before this update I just had to turn the phone on for Android Pay to work, now I have to unlock it (with my fingerprint). I guess it's enhanced security to stop people pocket swiping your money
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.
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
I have that same problem.
I tried 5 different custom roms, I tried the kernel, it didn't work.
everything is working, only the sound on the phone call is neither going nor coming. same as normal earphone with bluetooth earphone.
audio recording in video recording, music working, microphone recording sound, but no sound in calls. There is an imei signal, but there is no solution.
Even emergency calls have the same problem.
why could it be?
Thank You for replying, OnlineBeyin!
And here I thought, I was completely alone in this. At least there's someone out there sharing the pain!
Well, here's to a strage new Problem.
In a funny way, I love this about digital technology; it never gets boring - as soon as you'd think you've got your stuff figured out, along comes a curious problem you've never heard of or even expected to be possible.
I havent found a solution yet but having someone with the same problem gives me hope, maybe together we can work it out.
I don't think it's about the custom ROMs since You tried five of them to no avail. What do You mean by "trying a kernel"?
I've come to terms with it since I kind of enjoy the silence that not being able to answer calls has provided, but there is some other strange behaviour that might hint at a possible solution I have not yet explored:
I've taken a look at the NikGApps package I was using (core) and I've realised that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I might need the basic version, since the core version does not provide an obvious dialer (What does "AOSP" stand for?) nor "Google Carrier Services", both of which seem quite important for phone calls.
Now me being a rather lazy fellow by nature, I thought I could just install the basic version over the the core version. In doing that, the clock app stopped working. I don't know why but opening it leads to the app crashing.
I've just seen Your post so I wanted to reply first rather then try a bunch of stuff and keep you waiting for an answer, but that's where I'm at.
So this strange behaviour (not being able to open the clock app) leads me to belive that...
<TL;DR>
Could there be an issue with different versions of programs running in the background?
(My point being Android is basically a customized version UNIX which has some similarities with Linux with which I have some modest experience with.
There I've experienced such issues around the OS telling me (paraphrasing) "the thing You want won't work like that because it is dependent on something that cannot be resolved automatically. You gotta have this version of that other thing to talk to that version of yet another thing and you have to solve that first. Then it'll work.")
So, long story short,
just to rule out this source of error, the next thing I'm going to try is to make a clean install with the full and original Version of GApps just to see if it'll work and go from there. If that won't help, I'll find out if there is something like the bash terminal from Linux just so I can see what the phone is doing exactly.
I hope this helps, if at least to spark an idea from somebody, anybody else!
I really want to get this phone working at some point, if only for sustainability's sake!
hi mate, still having the same problem...
Here's what I've tried and what I'm sure of
I tried turning off features such as google assistant voice listening and it didn't work.
I tested multiple microphones in the device with hardware test programs and the speaker that acts as a handset and it works fine.
The device is calling the other party, sending sms, just because there is a voice exchange problem, I have no doubts about imei etc.
It's purely a software issue. it's so clear
The first thing I would try would be to go back to the original rom. I haven't tested this before.
I also think that the device may have different criteria according to different countries, so there may be a conflict. But I don't think I made a lot of mistakes, to be honest.
It's very important to me that you share your every attempt.
I really want to operate this device. It's my favorite device.
In the meantime, I opened the device and tried to change the transmission films. I tried changing the bottom charging port. These are not solutions.
Hi
Cyberfreak1992 said:
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
Click to expand...
Click to collapse
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Happy new year, everyone!
System23 said:
Hi
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Click to expand...
Click to collapse
With great pleasure I'm here to announce:
Can confirm this works! Just tried it today, the patch straightforwadly fixes this issue.
I had to skip the integrity check in TWRP to be able install it, but that should be obvious.
I already lost hope.
All the thanks and all the glory definately go to System23!
Here are some things I've learned and/or used to solve things and make this phone how I want it in the first month of so of ownership:
- install all the Androplus magisk modules
- if you search for "more dark mode options" in settings you can choose to force whatever app you want into dark mode. this one took me awhile to figure out
- if you are rooted and have any problem getting notifications use the app DozeOff from the Fdroid store
- if you want to see screen on time install digital wellbeing from the play store, no app will appear installed but you can use the app activity launcher to open it, then in settings you can choose to have the app appear.
- for some reason forcing desktop mode in chrome android does not work for me after turning the chrome flag on, but using the app Chrome UA forces chrome to display websites in desktop mode as default each time instead of mobile
- use vivid navigation gestures so you have gestures with a 3rd party launcher
- if you want to use a 3rd party app and hide the nav bar, use the magisk module Fullscreen/Immersive Gestures q-t, us the androplus modele Hide Status bar to get a truly fullscreen phone when unfolded.
- are you not getting the latest MIUI update and also want to stay rooted with magisk? install MIUI downloader from the play store, grab the latest software there you want the full version. go to miui updates in settings and tap on the icon 10 times, you will now have the option to flash update files. install the magisk module MIUI flash freely. you can now flash a full rom update from the file you downloaded. flash the update but don't reboot. go to magisk and install magisk to inactive slot OTA. you'll now have the latest version of MIUI and won't have to wait.
knives of ice said:
Here are some things I've learned and/or used to solve things and make this phone how I want it in the first month of so of ownership:
- install all the Androplus magisk modules
- if you search for "more dark mode options" in settings you can choose to force whatever app you want into dark mode. this one took me awhile to figure out
- if you are rooted and have any problem getting notifications use the app DozeOff from the Fdroid store
- if you want to see screen on time install digital wellbeing from the play store, no app will appear installed but you can use the app activity launcher to open it, then in settings you can choose to have the app appear.
- for some reason forcing desktop mode in chrome android does not work for me after turning the chrome flag on, but using the app Chrome UA forces chrome to display websites in desktop mode as default each time instead of mobile
- use vivid navigation gestures so you have gestures with a 3rd party launcher
- if you want to use a 3rd party app and hide the nav bar, use the magisk module Fullscreen/Immersive Gestures q-t, us the androplus modele Hide Status bar to get a truly fullscreen phone when unfolded.
- are you not getting the latest MIUI update and also want to stay rooted with magisk? install MIUI downloader from the play store, grab the latest software there you want the full version. go to miui updates in settings and tap on the icon 10 times, you will now have the option to flash update files. install the magisk module MIUI flash freely. you can now flash a full rom update from the file you downloaded. flash the update but don't reboot. go to magisk and install magisk to inactive slot OTA. you'll now have the latest version of MIUI and won't have to wait.
Click to expand...
Click to collapse
Hi, I 'm not understanding your way of updating. When you say go to miui udates in setings, what settings? In the app or the phone settingts? tap what icon 10 times?
dooley19 said:
Hi, I 'm not understanding your way of updating. When you say go to miui udates in setings, what settings? In the app or the phone settingts? tap what icon 10 times?
Click to expand...
Click to collapse
How to install MIUI updates manually / early - xiaomiui
Xiaomi continues to release updates for their devices but sometimes these updates may take longer to arrive than normal. With this guide we are going to teach
xiaomiui.net
just follow that, then you have to install the magisk module to be able to install the local file
knives of ice said:
How to install MIUI updates manually / early - xiaomiui
Xiaomi continues to release updates for their devices but sometimes these updates may take longer to arrive than normal. With this guide we are going to teach
xiaomiui.net
just follow that, then you have to install the magisk module to be able to install the local file
Click to expand...
Click to collapse
Okay thanks
Phone updated on its own. I had to reboot to turn on the setting to press 10 times. When I rebooted. It was on the new firmware but I'm not rooted anymore
dooley19 said:
Phone updated on its own. I had to reboot to turn on the setting to press 10 times. When I rebooted. It was on the new firmware but I'm not rooted anymore
Click to expand...
Click to collapse
You have to turn off auto update in Developer Settings.
frcraig said:
You have to turn off auto update in Developer Settings.
Click to expand...
Click to collapse
So now I have to root it again like I did the first time rooting?
Yes. Auto update must be disabled both in Settings and in Developer Options. You can manually update, but to preserve root you must carefully follow the instructions knives of ice and I have posted on the forum.
frcraig said:
Yes. Auto update must be disabled both in Settings and in Developer Options. You can manually update, but to preserve root you must carefully follow the instructions knives of ice and I have posted on the forum.
Click to expand...
Click to collapse
Okay thanks I'm now rooted again and I turned off auto update. Any good modules to download? I have the android auto one and the MIUI China to Global.
dooley19 said:
Okay thanks I'm now rooted again and I turned off auto update. Any good modules to download? I have the android auto one and the MIUI China to Global.
Click to expand...
Click to collapse
Is your Android Auto working?
Anyone else had issues with voice calls sounding absolutely awful for the other person?
Apparently it sounds like I'm under water and doesn't sound great at all. I then recorded a phonecall with someone and can confirm that my end sounds absolutely awful.
I'm in the UK and using Giffgaff if that counts at all.
EDIT: Had a SIM from Three arrive that I ordered 'cause I'm off to the US next week, just made a phonecall with that and the quality was a typical normal quality, not an underwater sounding mess. So whatever it is, it's something to do with Giffgaff and the phone (it works perfectly fine on my previous phone).
Waltee said:
Anyone else had issues with voice calls sounding absolutely awful for the other person?
Apparently it sounds like I'm under water and doesn't sound great at all. I then recorded a phonecall with someone and can confirm that my end sounds absolutely awful.
I'm in the UK and using Giffgaff if that counts at all.
EDIT: Had a SIM from Three arrive that I ordered 'cause I'm off to the US next week, just made a phonecall with that and the quality was a typical normal quality, not an underwater sounding mess. So whatever it is, it's something to do with Giffgaff and the phone (it works perfectly fine on my previous phone).
Click to expand...
Click to collapse
Do you have VoLTE enabled? The VoLTE toggle appears in Settings/Mobile Network/SIM if coded on your SIM Card. Some SIMs, like those from T-Mobile, allow this automatically. With some carriers you have to get around the fact that this is not an "approved device" on their Network. Use the dial code * # * # 86583 # * # * to disable carrier check and the VoLTE option will appear. If it is working you will get an HD symbol before or above your cell signal bars in the system notifications tray. Without VoLTE enabled, even though you are connected to a 4G or 5G network, voice calls fall back and connect on the old 3G networks. To see if you have correctly enabled VoLTE look at your system notifications tray and note what you are connected to - ie 4G. Now place a voice call and see if it stays on 4G or whether it changes to H, H+, HSPA, or 3G. If it drops, then you don't have VoLTE enabled. If the code to disable the carrier check doesn't work, you can unlock the bootloader, root with Magisk, and install a VoLTE Enabler module. Voice quality on 3G is poor compared to VoLTE (which carries voice calls over 4G or 5G). The Americans have shut down their 3G towers so you won't be able to place voice calls in the States unless you get this settled. Alternatively, when you land in the US you can connect to the airport's WiFi and download the Google Voice app, get a free American phone number, and you can then place free phone calls in the US and Canada to American and Canadian numbers, and for just a few pence call home. Google Voice uses mobile data, so it will work anywhere in the US over 4G or 5G data. Unfortunately GiffGaff doesn't have any roaming arrangements with US carriers (it only has EU roaming partners), but if you have picked up a Three SIM, their Three Go Roam should work. If "automatically connect to preferred network" is enabled in the Settings/Mobile Data/SIM of your phone, then it might try to connect to AT&T which could be problematic. I have a Canadian SIM and the dial code to disable carrier check and enable VoLTE works with Canadian carriers, but on a trip to Colorado last week I couldn't make voice calls as the trick didn't work on the AT&T network which uses a "whitelist" of approved devices for VoLTE. T-Mobile doesn't, so I changed the phone setting to "manually select network", waited for it to search, and then chose T-Mobile. I then had VoLTE back and could place voice calls. Let us know how you made out with voice calls in the US. EDIT: I just checked with someone in the UK and GiffGaff doesn't support VoLTE at all as they push all their voice calls over 3G and VoLTE is Voice Over LTE (4G). Three, Vodafone, and EE push their voice calls over 4G in the UK.
dooley19 said:
Okay thanks I'm now rooted again and I turned off auto update. Any good modules to download? I have the android auto one and the MIUI China to Global.
Click to expand...
Click to collapse
Can you share how you rooted this phone? Coming from a person who doesn't know how to at all
Hi,
After months of sitting on the fence, I finally purchased the phone and taking delivery of it the next couple of days. Coming from a 1st time user of Xiaomi and foldable phone, I would like to ask a few questions if I may:
1) Unlock the bootloader - waiting period of 168 hours.
So during the waiting period, can i start using the phone normally and transferring my data over?
2) After waiting period is up, I will start installing Magisk via patching method to root the phone. What are the list of Magisk modules and what are the must-haves to install for this phone? I don't drive so Android Auto is not required.
3) When can i start running the ADB commands to uninstall the chinese apps?
4) Is it a must to disable MIUI optimizations in order to enable horizontal split? I read somewhere that there is a horizontal spilt mod?
Thank you for taking the time to read and clear my enquiries. Really appreciate it.
Illidann said:
Hi,
After months of sitting on the fence, I finally purchased the phone and taking delivery of it the next couple of days. Coming from a 1st time user of Xiaomi and foldable phone, I would like to ask a few questions if I may:
1) Unlock the bootloader - waiting period of 168 hours.
So during the waiting period, can i start using the phone normally and transferring my data over?
2) After waiting period is up, I will start installing Magisk via patching method to root the phone. What are the list of Magisk modules and what are the must-haves to install for this phone? I don't drive so Android Auto is not required.
3) When can i start running the ADB commands to uninstall the chinese apps?
4) Is it a must to disable MIUI optimizations in order to enable horizontal split? I read somewhere that there is a horizontal spilt mod?
Thank you for taking the time to read and clear my enquiries. Really appreciate it.
Click to expand...
Click to collapse
1) Unlock the bootloader - waiting period of 168 hours.
You can use it normally. Just make sure you log into your xiaomi account and dont log out during that time or else it will reset the timer
2) After waiting period is up, I will start installing Magisk via patching method to root the phone. What are the list of Magisk modules and what are the must-haves to install for this phone?
I would recommend androplus module for the global conversion and universal safteynet fix
3) When can i start running the ADB commands to uninstall the chinese apps?
as soon as you get the phone. Just make sure you dont remove the wrong one or else you get boot looped and need to factory reset
4) Is it a must to disable MIUI optimizations in order to enable horizontal split? I read somewhere that there is a horizontal spilt mod?
I dont know of any mods to enable horizontal split so im pretty sure it is. MIUI optimisations has given me more problems than features though so im fine with having it off (other than my keyboard getting reset every time I reboot)
Illidann said:
Hi,
After months of sitting on the fence, I finally purchased the phone and taking delivery of it the next couple of days. Coming from a 1st time user of Xiaomi and foldable phone, I would like to ask a few questions if I may:
1) Unlock the bootloader - waiting period of 168 hours.
So during the waiting period, can i start using the phone normally and transferring my data over?
2) After waiting period is up, I will start installing Magisk via patching method to root the phone. What are the list of Magisk modules and what are the must-haves to install for this phone? I don't drive so Android Auto is not required.
3) When can i start running the ADB commands to uninstall the chinese apps?
4) Is it a must to disable MIUI optimizations in order to enable horizontal split? I read somewhere that there is a horizontal spilt mod?
Thank you for taking the time to read and clear my enquiries. Really appreciate it.
Click to expand...
Click to collapse
As ThatsJustLogic said, be very very careful with what you erase. My first go I deleted xiaomi cloud and I kept getting an error pop up every 5 seconds.
In terms of modules, it’s really up to you and how you want the device to look and feel.
Thank you
ThatsJustLogic andGlesi2323 for the kind advice.
Hi, surprised no one has mentioned this but.. There is no way to customize the app grid?? It only has the default 4x5 option and no way to change it, am I missing something? Is there a way to fix this without rooting, etc?
Thanks!
Hi you can use de launcher alpha module magisk numerous options like google discover at left, blur, grid.....
babaorum1973 said:
Hi you can use de launcher alpha module magisk numerous options like google discover at left, blur, grid.....
Click to expand...
Click to collapse
Can you please elaborate? A link to the module if possible as I can't locate anything specific with that name...