Database Info

[Q]Changing / Removing Carrier name not spoofing

Hello,
my problem is that my Rockchip rk3066 SDK is shown as china mobile [produkt name] in Google Play and probably not only there.
This board has no cellular network capabilities so it is nonsense and furthermore it restricts some apps on Google Play. Furthermore Play seems to think that I am using this device from china (a lot Chinese soft porn apps - )
I already added
Code:
ro.carrier=wifi-only
to build.prop but this hasn't helped.
Do you have any ideas where I could change that?

motioncoding said:
Hello,
my problem is that my Rockchip rk3066 SDK is shown as china mobile [produkt name] in Google Play and probably not only there.
This board has no cellular network capabilities so it is nonsense and furthermore it restricts some apps on Google Play. Furthermore Play seems to think that I am using this device from china (a lot Chinese soft porn apps - )
I already added
Code:
ro.carrier=wifi-only
to build.prop but this hasn't helped.
Do you have any ideas where I could change that?
Click to expand...
Click to collapse
check carrier alpha and numeric, are they China based?

Robobob1221 said:
check carrier alpha and numeric, are they China based?
Click to expand...
Click to collapse
How can I do that?

motioncoding said:
How can I do that?
Click to expand...
Click to collapse
Its in the build.prop. look for the following if you have them. You might not have all of them:
Code:
ro.com.google.clientidbase=
ro.com.google.clientidbase.yt=
ro.com.google.clientidbase.am=
ro.com.google.clientidbase.vs=
ro.com.google.clientidbase.gmm=
ro.com.google.clientidbase.ms=
android.os.product.brand=
ro.cdma.home.operator.numeric=
ro.cdma.home.operator.alpha=
ro.product.brand=
ro.product.locale.language=
ro.build.description=
ro.build.fingerprint=
These are blank here but you should have a value after the =. Change out these values with values from your carrier, region.
This should fix your market not registering in your locale.

Robobob1221 said:
Its in the build.prop. look for the following if you have them. You might not have all of them:
Code:
ro.com.google.clientidbase=
ro.com.google.clientidbase.yt=
ro.com.google.clientidbase.am=
ro.com.google.clientidbase.vs=
ro.com.google.clientidbase.gmm=
ro.com.google.clientidbase.ms=
android.os.product.brand=
ro.cdma.home.operator.numeric=
ro.cdma.home.operator.alpha=
ro.product.brand=
ro.product.locale.language=
ro.build.description=
ro.build.fingerprint=
These are blank here but you should have a value after the =. Change out these values with values from your carrier, region.
This should fix your market not registering in your locale.
Click to expand...
Click to collapse
Ok but this device has no mobile connection so should I leave this values empty? e.g. The MK802 Android Stick doesn't show any carrier.

motioncoding said:
Ok but this device has no mobile connection so should I leave this values empty? e.g. The MK802 Android Stick doesn't show any carrier.
Click to expand...
Click to collapse
you got copies of of the build.props you can paste in a pm or something?

Fix video recording bug in any Rom [video frame drop fix] [100% Working]

Just add this two lines in your build.prop
Open Root --> System --> build.prop
Now add this two lines
Media.camera.ts.monotonic=0
Persist.camera.HAL3.enabled=true
Otherwise download build prop editor from play store and add this line.
Hit like if you like my work.
#It will be great if developers merge this lines into their build.prop while building the Rom. #no_more_video_recording_or_playing_bug_

hi,
my phone cant record video in apps like facebook will it work in this case too.

[email protected] said:
hi,
my phone cant record video in apps like facebook will it work in this case too.
Click to expand...
Click to collapse
Not sure with it ! Just give a try a watch it !

It worked on my Redmi 4A with HavocOS 3.0( Android 10 ). Thank you so much sir.

it didn't really work
i know this is an old thread but, is there a specific string/place/line in build.prop we should put that code in? or any empty line?

Google Recorder

Pixel 4 has just been announced and the recorder app is out.
Here are the main features of the app.
-Audio transcriptions
-Audio search
-Location tagging
-Save to Google Drive
Not Working
-Audio transcriptions aren't being saved but you can still do search, but only the audio recording shows up.
-Call recorded audio won't show up on the app.
Here's the link
https://www.apkmirror.com/apk/googl...rder-1-0-271580629-android-apk-download/#file
Sent from my GM1913 using Tapatalk

Yeah I'm loving it

I installed it and I have a ton of call recordings from using op built-in call recording and none show up there
Sent from my OnePlus7Pro using XDA Labs

Still on Pie.
Installs fine, records my voice, shows live transcript, saves fine and plays it back, but the transcript isn't saving

Works great. Just the transcripts are not saved for some reason. Also if you search a keyword, it gets to it in the recorded sound but no transcripts.

Working for me but the transcription doesn't save after I've saved the recording. So I'll record, click on transcription, save but then when I click on the audio then click on transcription, it says no transcription.

Live transcription is working smoothly for me, but after saving i can't recover the transcript i can only access the saved audio only

Thanks for the feedback. So anyways, call recorded audio is not being recognized by the app and transcriptions are not being saved. It might be a Google Pixel 4 exclusive since they added a chip just for offline transcriptions and stuff (not sure on that).
Anyway, I'll put your feedback of bugs or I might say incompatibilities on the first post. Thanks.
Sent from my GM1913 using Tapatalk

spart0n said:
I installed it and I have a ton of call recordings from using op built-in call recording and none show up there
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
Is there an option to use Google Recorder app for recording current call conversation?
Sent from my GM1913 using Tapatalk

saiz136 said:
Is there an option to use Google Recorder app for recording current call conversation?
Click to expand...
Click to collapse
There isn't BUT if I knew where the recording app held it's recordings I could set up tasker to auto copy/paste the files from my oos call recording to the folder where Google holds those files and boom maybe it will work that way
Sent from my OnePlus7Pro using XDA Labs

please recompile for oreo
hey do you think you guys could recompile this for an lg g7 or v30. Mine runs on Oreo (v30) and i had issues trying to update it. So could you guys please get this to work for android oreo phones like you have with Google Camera?

Google Recorder 1.0.273
Pixel 4 Recorder works on OP6t without saving transcript, only audio is saved and can search for words in the audio file. But this version works flawless on Huawei Mediapad M5 Pro with transcript file! Is it a hardware thing?

mailconstantijn said:
Pixel 4 Recorder works on OP6t without saving transcript, only audio is saved and can search for words in the audio file. But this version works flawless on Huawei Mediapad M5 Pro with transcript file! Is it a hardware thing?
Click to expand...
Click to collapse
works on a kirin 960 but not a snapdragon 855...or 845. That does seem a bit odd. That would make it seem less like a hardware issue the no?

Latest version fc. Only this version works.

Only english supported?

Can someone please make an android oreo version of this:crying:

The newer version (1.0.273860567) checks for a feature and exits if it is not present. Specifically, it checks for
Java:
getPackageManager().hasSystemFeature("com.google.android.feature.PIXEL_2019_EXPERIENCE")
. If it returns false, it'll
Java:
throw new IllegalStateException("Cannot start Recorder on unsupported device");
, which should be the reason that it crashes on other devices.

Mushinako said:
The newer version (1.0.273860567) checks for a feature and exits if it is not present. Specifically, it checks for
Java:
getPackageManager().hasSystemFeature("com.google.android.feature.PIXEL_2019_EXPERIENCE")
. If it returns false, it'll
Java:
throw new IllegalStateException("Cannot start Recorder on unsupported device");
, which should be the reason that it crashes on other devices.
Click to expand...
Click to collapse
any chance anyone can mod this out?

Clintroymkt said:
any chance anyone can mod this out?
Click to expand...
Click to collapse
Just deleting these lines that check this and recompile the apk may work. I haven't had a chance to do that yet. If anyone's interested, the lines of codes of interest are in src/main/java/com/android/apps/recorder/p003ui/application/RecorderApplication.java, lines 52, 95, 96. I exported the apk to Gradle using jadx, so your lines may not be the same as mine.
Edit: recompiled the apk using apktool. After getting rid off relevant code the new version works. Nothing much different from the previous version other than the device check. Still no transcript after saving.
Sent from my OnePlus 5T using XDA Labs

Mushinako said:
Just deleting these lines that check this and recompile the apk may work. I haven't had a chance to do that yet. If anyone's interested, the lines of codes of interest are in src/main/java/com/android/apps/recorder/p003ui/application/RecorderApplication.java, lines 52, 95, 96. I exported the apk to Gradle using jadx, so your lines may not be the same as mine.
Edit: recompiled the apk using apktool. After getting rid off relevant code the new version works. Nothing much different from the previous version other than the device check. Still no transcript after saving.
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
Can you share the apk?
Thanks

Call Recording Feature APK ?

My Settings does not have the option for call recording but i notice others in different regions do.
Its legal in my state to record without consent any conversation i am a part of. Devices and Surveillance Act 1999 Victoria. Same applies for Northern Territory and Queensland.
I wonder if its possible that someone with the S10plus or a Samsung model who has this feature to extract and make a apk to enable it.
When i had the Huawei Mate 20 Pro the feature was not available but a few months after release someone managed to extract and make a apk from another Huawei phone or firmware. This worked perfectly and there was no background sound distortion like there is with 3rd party apps.

https://forum.xda-developers.com/ma...recording-huawei-dialer-magisk-t3918036/page3

Darkat70 said:
https://forum.xda-developers.com/ma...recording-huawei-dialer-magisk-t3918036/page3
Click to expand...
Click to collapse
I believe on Android 10 only root can help you now. Google removed any possibilities already.
Try skvalex call recorder. But even this one will make a lausy recording if any without root.
If you root, but I guess you are with snapdragon, it will be easy. You can simply edit your cscfeature.xml and activate this functionality as a stock feature. Or when rooted, use the call recorder mentioned above.

tiho5 said:
I believe on Android 10 only root can help you now. Google removed any possibilities already.
Try skvalex call recorder. But even this one will make a lausy recording if any without root.
If you root, but I guess you are with snapdragon, it will be easy. You can simply edit your cscfeature.xml and activate this functionality as a stock feature. Or when rooted, use the call recorder mentioned above.
Click to expand...
Click to collapse
Cube ACR is working on both sides, although its super sensitive to background noise.

ACR is working perfect in Android 10 on my S10 PLUS..

Darkat70 said:
Cube ACR is working on both sides, although its super sensitive to background noise.
Click to expand...
Click to collapse
ACR is not working for me on both sides. What is the phone recording audio source you choose for both side recording. Right now I only hear my voice. Thank you for any feedback.

WhoIsJohnGalt1979 said:
ACR is not working for me on both sides. What is the phone recording audio source you choose for both side recording. Right now I only hear my voice. Thank you for any feedback.
Click to expand...
Click to collapse
This is what my settings are

tiho5 said:
I believe on Android 10 only root can help you now. Google removed any possibilities already.
Click to expand...
Click to collapse
Which possibility did Google remove, recording calls? This is incorrect. As the OP said - and I know for a fact from personal experience - stock ROMs in other countries (for example - Israel), on all recent Samsung models, have built-in Call Recording.

sbi1 said:
Which possibility did Google remove, recording calls? This is incorrect. As the OP said - and I know for a fact from personal experience - stock ROMs in other countries (for example - Israel), on all recent Samsung models, have built-in Call Recording.
Click to expand...
Click to collapse
I think that by following the line of "conversation" here it is more or less clear that what I said is meant for the countries that are not supported by Google for call recording.

tiho5 said:
I think that by following the line of "conversation" here it is more or less clear that what I said is meant for the countries that are not supported by Google for call recording.
Click to expand...
Click to collapse
Yes correct, Australia does not have stock call recording, because some states have different laws.
Queensland, Northern Territory and Victoria are exempt from these laws, under the surveillance devices act 1999 its legal to secretly record without consent any conversation that you are a part of.

.::Liquid::. said:
ACR is working perfect in Android 10 on my S10 PLUS..
Click to expand...
Click to collapse
Is it still Working even after the 10 Update??? Coz mine is only recording on my side only.. :crying::crying::crying::crying:

Chira1234 said:
Is it still Working even after the 10 Update??? Coz mine is only recording on my side only.. :crying::crying::crying::crying:
Click to expand...
Click to collapse
Have you enabled the accessibility option, this option needs to be enabled for android 10 without root.

Chira1234 said:
Is it still Working even after the 10 Update??? Coz mine is only recording on my side only.. :crying::crying::crying::crying:
Click to expand...
Click to collapse
I upgraded to the S20Ultra and Cube ACR still working so far. Seems clearer than the S10+ managed to get.

ACR (another call recorder by NLL Apps) is working ok on my s10+. You should give it a try. Of course is recording background and caller voice is lower but does it's job.

hinxnz said:
Have you enabled the accessibility option, this option needs to be enabled for android 10 without root.
Click to expand...
Click to collapse
Could you please explain to me how to do that???

Chira1234 said:
Could you please explain to me how to do that???
Click to expand...
Click to collapse
Settings / Accessibility / installed services.

Darkat70 said:
Settings / Accessibility / installed services.
Click to expand...
Click to collapse
Did that already. but still no luck. :crying::crying::crying::crying:

Hi ,
You need to root your phone
or maybe download call recorder from play store

True Phone dialer app works recording both sides except if your calling with wifi calling then it won't record the other side of the call only your side.

ACR you need to install from the galaxy store not from google apps https://galaxystore.samsung.com/det..._id=W_15fd7e58a4696d0121c0cc4ad18f1349&sign=1 works fine on S10+

Question Noisy sound when call by CarLink?

Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?

vitdaika said:
Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?
Click to expand...
Click to collapse
Not familiar with your unit, Mine, carlink Uses Wi-Fi for everything but phone, it uses Bluetooth You might be able to use a config,txt file to correct volume levels and bluetooth version.
you'll need fat32 formatted sd card with the "Isec6315update" out of the full update zip and a config.txt with this on it.
#test
ro.fyt.launcher=com.android.launcher4
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
sys.fyt.ec_version=6

03hdfatboy said:
Not familiar with your unit, Mine, carlink Uses Wi-Fi for everything but phone, it uses Bluetooth You might be able to use a config,txt file to correct volume levels and bluetooth version.
you'll need fat32 formatted sd card with the "Isec6315update" out of the full update zip and a config.txt with this on it.
#test
ro.fyt.launcher=com.android.launcher4
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
sys.fyt.ec_version=6
Click to expand...
Click to collapse
Thanks bro,
Where can I find the “lsec6315update”?

vitdaika said:
Thanks bro,
Where can I find the “lsec6315update”?
Click to expand...
Click to collapse
check inbox

vitdaika said:
Hello,
I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.
If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.
I tried searching every solution with CarLink but no luck.
Has anyone had the similar problem?
Click to expand...
Click to collapse
Is it an FYT unit, post Android system information including MCU version

marchnz said:
Is it an FYT unit, post Android system information including MCU version
Click to expand...
Click to collapse
Yes. It's a OledPro 12.3 Android head unit.
Android version: 10
Build Number: QP1A. 190711.020 release-keys
System Info: APP 1920×720 2023-03-04 15:37:04
CPU: UIS7862 Octa-Core [email protected] GB(Memory) + 32 GB(Storage)
MCU Version: 2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0

vitdaika said:
Yes. It's a OledPro 12.3 Android head unit.
Android version: 10
Build Number: QP1A. 190711.020 release-keys
System Info: APP 1920×720 2023-03-04 15:37:04
CPU: UIS7862 Octa-Core [email protected] GB(Memory) + 32 GB(Storage)
MCU Version: 2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
Click to expand...
Click to collapse
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
We can only derive from your MCU that it is a YIN type FYT with manufacturer code 53.
And CarLink is a reverse engineered piece of software to mimic the Android Auto layer in OEM units as good as possible.
Anyway, just like @03hdfatboy already mentioned: As far as I know also under Android Auto the BT connection is used for phone calls.
What might be an option to check is if your phone is set to "use WiFi for phone calls" and try to switch that on/off.

surfer63 said:
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
We can only derive from your MCU that it is a YIN type FYT with manufacturer code 53.
And CarLink is a reverse engineered piece of software to mimic the Android Auto layer in OEM units as good as possible.
Anyway, just like @03hdfatboy already mentioned: As far as I know also under Android Auto the BT connection is used for phone calls.
What might be an option to check is if your phone is set to "use WiFi for phone calls" and try to switch that on/off.
Click to expand...
Click to collapse
I think OledPro is a new 12,3 inch Android unit in Vietnamese market, since 2022.
As your suggestion, I tried to switch mode of "Call over WiFi" to On then Off on my iPhone 14 Pro, but it doesn't solve the problem.
I backed up the system using your guide post, and forgot the line "don't backup 360 camera". After backed-up, I modified the config.txt with the lsec6315update, and have successfully applied the config.txt, now the sound becomes a little bit better.
But, the system swiped my Camera 360 app. Is there a Camera 360 apk file to re-install it?

surfer63 said:
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.
Click to expand...
Click to collapse
please see it installed on my Toyota Corolla Cross 2022

vitdaika said:
But, the system swiped my Camera 360 app. Is there a Camera 360 apk file to re-install it?
Click to expand...
Click to collapse
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
In the mean time I wrote a script that should (re)install the 360 camera software.
For others: It will install the software, but it will of course only work if your unit really has the (hardware) 360-camera chip installed.
Please try the script: 360_installer.zip and let me know if it works.
As usual: unzip to a clean USB-stick and flash it.

surfer63 said:
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
Click to expand...
Click to collapse
Just did that and added them to post #4 of the "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" forum thread.

surfer63 said:
So far my backup script did not backup the 360 camera part as the script crashed on units without it.
I will now simply create two scripts: one for 360 camera and one for units without 360 camera.
In the mean time I wrote a script that should (re)install the 360 camera software.
For others: It will install the software, but it will of course only work if your unit really has the (hardware) 360-camera chip installed.
Please try the script: 360_installer.zip and let me know if it works.
As usual: unzip to a clean USB-stick and flash it.
Click to expand...
Click to collapse
It does not work

vitdaika said:
It does not work
Click to expand...
Click to collapse
Strange. The apk should simply be on your system and this script only restores the 360res folder and contents.
My system does not have the 360 configuration so I can't check.
Someone else here with a 360 system and more knowledge about it?

Hello, I have a CPU unit: UMS512S MCU 2022.07.08 the problem concerns I can't find anywhere to increase the sensitivity of the microphone conversation via carlik 2.0 version 2.22.0714.0919 and via BT the voice is hard to hear can anyone help me?

Same problem….

To prevent fragmented info I will answer your cross-posted question here:
What helps a tiny bit is to add the following lines to a config.txt:
Code:
persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7
Simply put that config.txt and an lsec7862update for a uis7862, or an lsec6316update for a sui8581a, on a blank usb-stick and flash it.
As said: this only helps a little bit. It is just that the internal microsophone sucks. (like I already mentioned in another topic by you where you asked exactly the same).
Also @louforgiveno mentioned above solution a few days ago in a post.

surfer63 said:
To prevent fragmented info I will answer your cross-posted question here:
What helps a tiny bit is to add the following lines to a config.txt:
Code:
persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7
Simply put that config.txt and an lsec7862update for a uis7862, or an lsec6316update for a sui8581a, on a blank usb-stick and flash it.
As said: this only helps a little bit. It is just that the internal microsophone sucks. (like I already mentioned in another topic by you where you asked exactly the same).
Also @louforgiveno mentioned above solution a few days ago in a post.
Click to expand...
Click to collapse
#callquality
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
persist.btmic.gain=10
persist.btspk.gain=7[
persist.audio.mic.senstivity=1
sys.fyt.ec_version=6
Would it be enough for me to add these codes?

thericksizzler said:
#callquality
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
persist.btmic.gain=10
persist.btspk.gain=7[
persist.audio.mic.senstivity=1
sys.fyt.ec_version=6
Would it be enough for me to add these codes?
Click to expand...
Click to collapse
Yes, but the bottom line (ec_version) is not needed.

surfer63 said:
Yes, but the bottom line (ec_version) is not needed.
Click to expand...
Click to collapse
I did as you said and changed the config file. but there is no change. I haven't tried it on bluetooth, I just tried it on carplay. the caller's voice is very scratchy. as if the speakers were blown. In my previous tests, the sound in bluetooth was better than carplay, but still not very good.
as a result the config settings did not make any changes.

thericksizzler said:
as a result the config settings did not make any changes.
Click to expand...
Click to collapse
They did make a change if you check your properties.
But I already mentioned that it would be a very minor improvement. It is going from terrible to slightly less terrible.