yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Questions & Answers] sb1893:
So many variables in play with getting the native hotspot working. Mine is working fine. I'm on a Google Pixel XL. (Verizon) Android 9. Unlocked. Rooted (with Magisk 16.7 (1671)), Magisk Manager 5.8.3, and using the module MagiskHide Props Config to set the prop net.tethering.noprovisioning to true.

On Android 8 and earlier, the module "Tethering Enabler" worked, but I found it no longer worked once I upgraded to Android 9. The module MagiskHideProps Config allows you to set various custom props systemlessly (much as we used to back in the day by just editing the build.prop). You can find information on how to use the module on XDA and it is linked in the module documentation itself. (The module is very well documented. and creates a terminal UI that you execute from a terminal on your device (or via ADB if prefer). I use Termux (from play store on my device). Once you get the custom prop setup via the "Props" program, you can verify it is working via terminal emulator on the device or from computer/ADB by running as root getprop net.tethering.noprovisioning and verifying it returns true. I suspect that your issue is with the Tethering Enabler module (assuming that is what you are using) as I don't believe it was updated to keep up with the changes in Magisk and perhaps Android 9.

Anyways - good luck. Let me know how it goes.
[Google Pixel XL Questions & Answers] airmaxx23:
If you're on Verizon you don't need to anything other than root the phone and the hotspot will work just fine.
[Google Pixel XL Questions & Answers] sb1893:
That is only if you are subscribed to the hotspot as part of your plan. Most Verizon plans include some level of hotspot subscription - albeit with throttling to barely usable speeds after hitting data thresholds. I didn't mention that I am on a grandfathered unlimited plan which does not include hotspot. The setting of that build.prop that I mentioned circumvents the subscription check and allows my hotspot to work. Even if rooted, without that prop set, I hit the subscription check and am told to contact Verizon to subscribe. As I said - lots of variables with getting hotspot to work.
[Google Pixel XL Questions & Answers] airmaxx23:
I'm not on a hotspot plan and all I've ever done is root my device (currently a Pixel XL) and setup the hotspot and it works. I'm also grandfathered in with unlimited data and I did it just recently when installing Pie.
[Google Pixel XL Questions & Answers] sb1893:
Hmmmm - well that is interesting and certainly a different experience than mine. I've always had to do some level of mod - build.prop edits, modified carrierentitlement.apk in the SuperSu days and then tethering enabler or the systemless prop edit I just described on Magisk....(I'm also on a Pixel XL / Stock)
[Google Pixel XL Questions & Answers] airmaxx23:
Yeah that is a bit strange.
[Google Pixel XL Questions & Answers] crackerjack1957:
BuildProp Editor

Add line:

net.tethering.noprovisioning=true

save

reboot
[Google Pixel XL Questions & Answers] GroovinChip:
This did it, thanks!
[Google Pixel XL Questions & Answers] tweaked:
Here is the newest module for magisk. Works for me.
[Google Pixel XL Questions & Answers] sb1893:
Cool - I didn't realize that module had been updated to work on PIE. Looks like a few viable options to get tethering working depending on preference. I'm going to stick with the MagiskHideProps method for now as it also allows for other systemless build.prop edits if any are needed in the future....Thanks, all!
[Google Pixel XL Questions & Answers] cwburns32:
Do you install this via recovery? Or do I have to drop zip into a specific folder?

---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------

Curious what you are using to edit build prop. I have MagiskHideProps installed via Magisk but not sure how to edit build prop
[Google Pixel XL Questions & Answers] roman.ramirez.12:
You can Flash with TWRP just make sure you know where you put it. I like to keep my stuff in downloads.
[Google Pixel XL Questions & Answers] Phalanx7621:
There are build.prop editors on the play store to make it easier
[Google Pixel XL Questions & Answers] sb1893:
MagiskHideProps allows you to enjoy the effect of editing build.prop without actually physically altering the file. You are basically injecting build.prop values into system memory at boot time (my understanding). This achieves the same effect as editing build.prop without making changes to the file itself in system. (systemless change) Once you have installed MagiskHideProps you can use a terminal emulator on your phone or ADB Shell session via your computer to execute the simple program "Props". The documentation of MagiskHideProps is very detailed and easy to follow. You need to add a new prop set to True for net.tethering.noprovisioning. Good luck.

S
[Google Pixel XL Questions & Answers] cwburns32:
Thank you all. I ended up using zip file but still have MagiskHideProps installed for future build.prop edits. Thanks again!
[Google Pixel XL Questions & Answers] tigerh4rebz:
guys my hotspot is unlocked i just want to hide my hotspot useage from verizion. is there a guide to do this???
[Google Pixel XL Questions & Answers] dmalikyar:
Excellent! I edited the build.prop using a text editor and added this setting but to no avail. I guess the trick is to use the BuildProp Editor app and follow your instructions. My Pixel 3 XL's native hotspot works like a champ now. Thanks again!!!!
[Google Pixel XL Questions & Answers] clambert11:
:good: You rock! Quick and easy fix. Did it in less than a minute and that included downloading the app.
[Android Q&A, Help & Troubleshooting] cletisvandamm:
It keeps asking for the original email it was setup with. I cant set it up to any email. I am able to get it to do a verification but it wont take the email or password. I have been working at this for weeks now. Well not 24/7. It is active with my ATT sim card in the phone. I even try the accessibility settings but the phone wants the original account that it was used with. Well I don't remember it. I have a verizon email account it does accept but then it reverts to adding a google account. I have what I think is my google account but it doesn't seem to like it for some reason. I would do accessibility and then hold the home button and it tells me to setup account. I haven't tried rooting. If I can login to the phone I can add a new google account but I'm also unable to add a friends it just wants whatever was in it. The phone is my wife's and i just want it for emergencies and don't want to go buy a new one from ATT. The phone is basically brand new.

Sorry but I'm unable to post this in the LG forum. If I root the phone will it help me or can I access my google account and somewhere it will allow me to bypass this to get to the user screen. like I do have a gmail address and I maybe able to access the phone but my wife claims she doesn't remember setting one up? Any help is appreciated. I also went to ATT and of course they just wanted to reset well restore or wipe it clean. They didnt think to disable find my phone or whatever is stopping me here.
[Android Q&A, Help & Troubleshooting] lzr2345:
FRP Unlock

Power on to 'Welcome' screen. Press +hold 'Emergency Call' while repeatedly tapping 'Arrow', this will get you to the home screen. You're in. 1)Deactivate 'Device Administrator' 2) clear data+cache+ DISABLE GPSERVICES and GPSTORE, 3)do a Factory Reset from within the phone. This works for Android v.7.

For Android v.6- Power on + go to 'WiFi screen', with WiFi ON tap ' + add network' this pulls up the keyboard. On 'Keyboard' press 'gear icon' and swipe up to the letter 'S' . Above the keyboard a 'gear icon' next to the word 'Settings' pops up. Tap this. You're in. 1) Deactivate 'Device Administrator' 2)clear data+cache+DISABLE GPSERVICES and GPSTORE, 3) do a Factory Reset from within the phone.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] EfroxGraphics:
Xposed 89 is installed but not activated.

Message: Version 89 of the Xposed Framework is installed, but it is not active. Please check the records for more details.

But, i check the records and nothing exist.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] EfroxGraphics:
I found the solution

Disable Xposed in Xposed Status

Reboot the device (After restarting, the folder and the file already exist in registers)

Activate Xposed in Xposed Status

Reboot the device (It should be up and running by now)

Ready
[LineageOS Questions & Answers] nezlek:
When placing or receiving a voice call (LOS 14.1, Samsung Galaxy S6, current build) the other party hears their own voice echo back in approximately 1.5 to 2 seconds. It depends on what is being used on the S6 to make the call. If the built-in microphone and speakers are used, the echo is very problematic. It is less noticable with a Bluetooth headset, and it is completely not there if one uses a wired headset (in this case a pair of Samsung wired earplugs). With the stock ROM, this does not occur. Perhaps there is a set of build.prop entries or other yet-to-be-documented settings to address the noise cancellation issue ? An otherwise rather excellent ROM, it would be a shame to not be able to use it if it required earplugs for voice calling. An extensive search through the other Galaxy S6 forum postings and the forum specific to the ROM reveals nothing of particular value, but maybe something was overlooked. Suggestions, anyone?
[LineageOS Questions & Answers] Ibuprophen:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device and variants.

https://xdaforums.com/showthread.php?t=3738447

I did come across the following thread that may be helpful for what you are looking for.

https://xdaforums.com/showthread.php?t=3795558

If all else fails, and you don't receive any support from the above threads, then your next best bet is to post this question within the following Q&A thread that's specific to your device and variants as well.

https://xdaforums.com/showthread.php?t=3110220

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[LineageOS Questions & Answers] nezlek:
Thanks

Thanks again for the interesting and useful suggestion(s). I thought I had exhausted the possible S6 support locations on XDA, so it a always a pleasant surprise to find even more. Unfortunately, no news was to be found there, either. I suspect that some "out of the box thinking" might be required to address this one, which is why I have floated this inquiry beyond what might be thought of as the usual places. Lots of other device owners (e.g. One Plus, etc..) seem to have reported echo problems on voice calls using LOS, with a variety of suggestions about how to address the problem. I can't believe that everyone uses headphones (which do make the problem go away) for all of their voice calling, so somewhere there is an answer. What I have found most peculiar is that MY device has no echo issues. It is the device on the other end of the connection that is exhibiting the echo, regardless of who makes the call. As the saying goes: "curiouser and curiouser..."
[LineageOS Questions & Answers] prismaanandito:
Same here. I still wondering what causing the problem on my Note 5 (RR&Lineage). Have you found any solution other than using a wired headset to receive and make call?

I'm still thinking about this answer from https://xdaforums.com/general/help/echo-problem-callers-phone-t3550550: "It seems to me that your mic is picking up the sound that your speaker is emitting and then feeding back to their phone. If you are on stock, try turning the in call volume down so that your speaker isn't so loud."

And I'll try to reduce the in-call volume and will report it later.
[LineageOS Questions & Answers] Brignoud:
Echo

Same here with Samsung A15 and Lineage 16 custom ROM

Caller hear a strange echo

I tried change in build prop the value setting of fluence.speaker = false with no succes
[LineageOS Questions & Answers] Outlaw Dragon:
Anyone found a solution yet?

I'm having the same problem.
[LineageOS Questions & Answers] maybeme2:
Same problem.
[LineageOS Questions & Answers] Brignoud:
So evidently this is a source problem propagated all over the all kind of ROM based on this project
[LineageOS Questions & Answers] Outlaw Dragon:
Where can I find more info about that?
[LineageOS Questions & Answers] DrSeahorse:
Same thing for me on my SM-G920F using 15.1.2019022-UNOFFICIAL-zerofltexx.

Call if fine for me, but other person can hear themselves with a couple of seconds delay. Doesnt matter who starts the call or what method for me. Did the same using bluetooth setup in car.
[LineageOS Questions & Answers] KeepingItCuttingEdge:
Exactly my thoughts, because in have 3 different devices on Lineage 15.1 and 16 that all exhibit this behavior.

Seems like it would be an easy and IMPORTANT fix to the base/source. Just correcting the issue somewhere in the base code should correct it for everyone...

:confused:
[LineageOS Questions & Answers] deejayjaytay:
Yeah, this is affecting me on three different devices all running 16.0. Sad, I had to go back to the stock firmware because I cannot talk to loved ones.
[LineageOS Questions & Answers] Tonio0:
Hello, i have the same problem with Samsung Galaxy S7 edge (SM-G935)

I found a video on youtube "How to fix mic and speaker in custom ROMs ?"

Use BUILDPROP EDITOR to edit and add "ro.qc.sdk.audio.fluencetype=none"

but don't work for me :(
[LineageOS Questions & Answers] kurtn:
YouTube? Really? I guess the download link for your ROM was from YouTube also. Without telling you, who actually built it? Thats the person you shouting ask for a fix.
[LineageOS Questions & Answers] Tonio0:
Hi kurtn, i just try to fix a problem, I sought "ro.qc.sdk.audio.fluencetype" and i found a video that explain how to edit the prop .. i don't understand your reply ?
[LineageOS Questions & Answers] kurtn:
Do you have a custom ROM insalled? What exactly?
[LineageOS Questions & Answers] Tonio0:
Yes, lineage OS 16.0 + magisk.

The echo is only with the speaker on, the caller hears himself speak
[LineageOS Questions & Answers] kurtn:
Maybe you should post there https://xdaforums.com/s7-edge/development/beta-lineageos-16-0-s7-edge-hero2lte-t3842464

Or downgrade to 15.1
[LineageOS Questions & Answers] DarthNAL:
Possible solution? Confirmation needed

Hello, I'm new as a poster here.

I had the problem with my Galaxy S4 VE (jfvelte). I had ResurrectionRemix (Marshmallow) for years and found LineageOS 16 for my device, so I installed it successfully and all seemed to be better, Camera is much more stable, better battery drain. After two days I noticed the problem with the echo for caller on two different devices (Modem I9515XXU1BPK4).

I didn't find any solution, only an open issue on GitHUB.

I downgraded to 15.1, same Problem.

I downgraded once more to 14.1. Problem fixed. All fine, but I didn't want to stay with this old sticky nougat stuff ;).

From the audio fix patch from sombree i knew that the problem is somewhere into the two files "audio_platform_info.xml" and "mixer_path.xml", but his fix is for 14.1, and not for 16.

So I tried to reinstall 16, and replaced the two files with the ones from 14.1 (the path have been modified from /system/etc to /system/vendor/etc).

NOW I HAVE 16 WITH NO ECHO PROBLEM. Other sound devices seem to work (Tested Speaker, Bluetooth and headphones/headset).

Being a Windows developer and no Android/Linux expert, I have no real idea from what I've done, so I wanted someone (maybe a real expert) to tell me:

Is my solution working (seems to be so)?

Why didn't someone had the Idea before?

Why have they (LineageOS devs) broken it?

Maybe I could help, and please fix it directly in ROM.

I've build a flashable patch with the "ZIPme" app. Should I upload it?
[LineageOS Questions & Answers] kurtn:
Could you please post there?

https://xdaforums.com/galaxy-s4/unified-development/official-lineageos-16-0-t3954912

I think that issues are device specific.
[LineageOS Questions & Answers] exaveal:
This problem still exists and makes all custom roms for samsung devices not useable for productive usage. :(
[LineageOS Questions & Answers] sirsalmanzadeh:
Exact same problem with my s7. Only on lineage based roms. I was using pixel experience rom. Because of that this problem I've installed nfe ported pie rom
[LineageOS Questions & Answers] hydrokracker:
Same problem on Moto x4 (Payton)
[LineageOS Questions & Answers] shiko0o:
Same for op3t with pixel experience Android 10
[LineageOS Questions & Answers] ThinkingTwice:
Thank you very much for the effort you put into solving this issue!

I just posted about the issue in the Q&A for my specific device (Asus Zenfone Max Pro M1) thinking it might have been a hardware issue, but it definitely looks like a common problem LineageOS users are facing.

It happens with multiple calling applications (I have experienced it on both WhatsApp and Signal), and it does look like it's related to the microphone picking up the sound from the speaker since it varies depending on how you hold the phone, the volume level, and whether or not you use headphones (the problem in this case seems to almost disappear).

I'm also new to the forums so I don't know if it's appropriate to post it here, but I would definitely like to have access to the flashable patch you have put together!
[LineageOS Questions & Answers] markd89:
Edit: Do you have a link to the original sombree patch?

Could you please upload the patch as well as the "source" -- two files you replaced?

Thank you!
[LineageOS Questions & Answers] Scepterus:
Can someone post a working config, so we could have it saved for future devices, I have an s6 with the echo problem.
[LineageOS Questions & Answers] cereal_sam:
Had the same problem with a Note 3. (N9005, hlte)

Found out that for me the problem was hardware based. On the bottom of the phone, about 10mm to the left of the USB-port, there is a pinhole (1mm) leading to an additional microphone.

This pinhole was completely clogged with dirt. Cleaning it, solved the issue completely.

previous symptoms:

-caller hears its own voice echoing when using the phone handheld.

-no echoing when the call is put on speakers or a wired headset is used

For the Note 3 said anti-noise microphone has an additional entrance on the back of the phone. By completely removing the back cover (battery is out in the open) the echo will also disappear.

The little pinhole on the phones bottom actually just leads to a plastic channel directing sound to that microphone. So by poking around in it with a needle, you can't accidentally damage the microphone. I do recommend though to disassemble the phone somewhat to properly clean this part. It's sufficient to take the battery and stylus out and remove the back frame which is hold by ~10 screws.

Could imagine that principle is true for several Samsung models.
[LineageOS Questions & Answers] Eklondh:
So it seems like the problem still persists. Im using this Rom on herolte https://xdaforums.com/t/lineageos-15-1-android-8-1-0-for-s7-herolte-build-53-18-20-2020.3710107/

Its from 2020 and the bug is still there, I think the lineage source is from 2017 tho. That's when they stopped developing for it I think?

Is it really this hard to fix it? The solution is device specific I guess? Damn. Everything works perfect besides this
[LineageOS Questions & Answers] Eklondh:
So I found sort of a workaround solution I guess. Boosting your normal in call speaker to a higher volume so that you can use that as the loud speaker

I made a post about how to do it for this particular Rom on the Galaxy S7 Exynos here

https://xdaforums.com/t/lineageos-1...lte-build-53-18-20-2020.3710107/post-87630593

I think the names of the values in the mixer_paths file are device specific tho so finding which value to change can be a bit time consuming, but with that said I'm guessing this work around would work on other devices, Roms and maybe even brands as well
[Android Q&A, Help & Troubleshooting] Agrevi:
[IMG="Device manager"]https://i.imgur.com/IaWbF0j.png[/IMG]

Where can I download the official drivers?
[Xiaomi Poco F1 Questions & Answers] munchy_cool:
Current Status as of 10th Nov 2018 - This effort is no longer being pursued.

Mi 8 qcn is available (thx to [MENTION=6828615]JR_44[/MENTION]) https://xdaforums.com/showpost.php?p=78020802&postcount=184

When I open it in a hex editor to swap out the IMEIs I dont see anything relevant. https://xdaforums.com/showpost.php?p=78120935&postcount=186

This effort is no longer being pursued. You have [MENTION=3378209]jaimani[/MENTION] on xda and also xda (@MishaalRahman) works with Poco in providing free devices to developers so maybe they can ask Poco if this is even possible.

Current Status as of 28th October 2018.

Need qcn backup from Mi8. you will need to be rooted.

How to create one?

https://xdaforums.com/redmi-note-3/how-to/guide-qpst-tool-backup-imei-nvram-t3455297

Current Status as of 26th October 2018.

Can't read NV items for LTE

https://xdaforums.com/showpost.php?p=77641511&postcount=59

If anyone has ideas let us know.

Current Status as of 18th October 2018.

We have backups of modem and fsg from Mi Mix 2S.

https://xdaforums.com/showpost.php?p=77902835&postcount=166

When I try to open fsg backup in a hexeditor I dont get anything useful. So need help with figuring that out.

If anyone has any other ideas on how to unlock the bands (other than QPST) please post here.

RT's are appreciated

https://twitter.com/munchy_cool/status/1046028765892087808

Current Status as of 24th September 2018.

We need modem and efs partitions backup from Mi 8 and Mi Mix 2S.

Current Status as of 17th September 2018.

3G and LTE bands are not stored/referenced at 6828 and 6829 in NV browser. Thanks to [MENTION=6068742]Heronicola[/MENTION] for checking. We need to find out where these bands are. so if anyone has an idea, feel free to comment in the thread.

https://xdaforums.com/showpost.php?p=77641511&postcount=59

Original Post

The Pocophone F1 LTE bands are listed as

1(2100), 3(1800), 5(850), 7(2600), 8(900), 20(800), 38(2600), 40(2300), 41(2500)

However, it is supposed to launched in Mexico and Colombia as well.

Mexico LTE Bands - 2 & 4.

Colombia LTE Bands - 4 & 7

Band 2 and 4 will be very helpful for us US peeps.

Not sure how Xiaomi locks the bands, do they use software? in which QPST should be able to unlock the bands.

or

They lock them via hardware, in which case Poco F1 will have a different model from Mexico and Colombia (and other countries which use Band 2 and Band 4?

QPST

https://xdaforums.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774

If anyone with a bootloader unlocked and rooted Poco F1 is willing to try QPST and see if the bands can be enabled please post here.

Thanks.
[Xiaomi Poco F1 Questions & Answers] mtonne:
Also following for the answer. Bands 2 and 4 would make it quite viable for T-Mobile service in the US.
[Xiaomi Poco F1 Questions & Answers] sagematt:
Phone has indeed been announced for Colombia (where LTE band 4 is used) and it's already going through Colombia's own certification authority. I would assume that we might be facing a similar situation as with Mi A1 in that the manual said it didn't support LTE band 4 (check the post I just linked to) but on first setup if you chose "Español (Mexico)" as the language, it would enable LTE band 4.
[Xiaomi Poco F1 Questions & Answers] eilegz:
its sad that this phone with the flagship qualcomm sd845 should handle universal lte bands, but somehow in xiaomi phones specially the LTE bands are pretty limited, for example here we use band 28 (700 mhz) and there are no support for that
[Xiaomi Poco F1 Questions & Answers] thesoupthief:
Hadn't heard about this, with the Mi A1. Very nice fudge, this. If the F1 can be wangled to use band 4 it will be a shot in the arm for north American interest and development
[Xiaomi Poco F1 Questions & Answers] munchy_cool:
which means that the band might be disabled via software and we should be able to enable it via QPST.