yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Kooswithak:
How did you get this to work? I've been trying to days to enable this option. I pushed "adb shell settings put global wfc_ims_enabled1" but to no avail has it worked.

I am on AT&T and have tried this with both a Google Pixel XL 2 from Google and Verizon. If you could give me any details of what your setup is like so I can try to enable this I'd dearly appreciate it!
[Google Pixel 2 XL Guides, News, & Discussion] antiochasylum:
+1 how? Very curious.
[Google Pixel 2 XL Guides, News, & Discussion] uicnren:
a screenshot showing the actual call going over wifi is needed.

unless ATT changed their mind in the last week, WiFi calling isnt available for the Pixel 2/XL, even if the option is enabled, the account has to be provisioned, and the phone needs the proper IMS profile, ATT to this date has refused to allow it.
[Google Pixel 2 XL Guides, News, & Discussion] gettingerr:
This is the first I've seen the option even appear. Will test some calls and report back.
[Google Pixel 2 XL Guides, News, & Discussion] gettingerr:
Looks like it isn't up and rolling yet, but the fact that the option appears has me hopeful. At&t still doesn't say that it supports VoLTE on P2XL, but we have that working, so perhaps Wi-Fi calling is coming soon.
[Google Pixel 2 XL Guides, News, & Discussion] Kooswithak:
Here's hoping. My apartment is on the bottom floor so reception is very spotty. What has been weird though is that if I start a call when I have reception and move to a spot in my apartment where there is no cell service, the call persists. So part of me thinks me enabling Wifi Calling from ADB may have done something?
[Google Pixel 2 XL Guides, News, & Discussion] balleron24z:
So you're saying that after the ADB command was set, and you're in an area that legitimately has 0 cell service (not just very low/nearly unusable)? Screenshot of this, please?
[Google Pixel 2 XL Guides, News, & Discussion] jimmiekain:
Sorry, I'm not sure I'm reading this correctly. Please clarify... Are you saying that VoLTE is working on the Pixel 2 on att? If yes, please please please tell me how.
[Google Pixel 2 XL Guides, News, & Discussion] MrMeeseeks:
It's working on the developer previews. Just talk to an AT&T tech and have them provision your SIM for it.
[Google Pixel 2 XL Guides, News, & Discussion] uicnren:
Yes, it works fine, if you meet all of AT&T criteria.
[Google Pixel 2 XL Guides, News, & Discussion] jimmiekain:
At&t criteria? What's the criteria? I've Google searched and only found information saying you can't have it unless you have an att branded phone.
[Google Pixel 2 XL Guides, News, & Discussion] uicnren:
https://www.att.com/esupport/article.html#!/wireless/KM1046244
[Google Pixel 2 XL Guides, News, & Discussion] balleron24z:
Because idiots around the US have no idea what they're talking about then they say "VoLTE on AT&T only works with AT&T-branded Android phones or iPhones". As long as a manufacturer certifies their device with AT&T, and configure their devices with the proper IMS profile for AT&T's network, VoLTE will work. Google (HTC/LG) certified the Pixel 2 / 2 XL with AT&T for VoLTE and RCS, both of which work if all criteria are met (proper SIM card, IMEI updated in billing system, options turned on), and right now, 8.1 DP1/DP2 are needed to use VoLTE on AT&T's network, as the modem/IMS configuration was updated on the phone to support it.
[Google Pixel 2 XL Guides, News, & Discussion] fosser2:
VoLTE is enabled in Android 8.1 for AT&T. I just flashed the final factory image and it does indeed work. You do have to verify that your sim card is properly provisioned for VoLTE. As for the WiFi calling portion of this conversation, I still cannot access the "Wi-Fi calling" setting within "Mobile network settings."
[Google Pixel 2 XL Guides, News, & Discussion] mbze430:
I am on 8.1 on AT&T but the unlock version of the phone... I don't ave the VoLTE
[Google Pixel 2 XL Guides, News, & Discussion] jimmiekain:
Check to make sure your sim card supports it. If it does you'll wanna call att and have a technician make sure your account is provisioned properly. Also you'll need to make sure they have the IMEI of your phone.
[Google Pixel 2 XL Guides, News, & Discussion] uicnren:
and again....

https://www.att.com/esupport/article.html#!/wireless/KM1046244
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
I just bought a Verizon Pixel 2 XL and Volte doesn't work. I'm on 8.1.0 February security patch. I thought that the Verizon Pixel was exactly the same as the Google Store version, other than the locked bootloader. Does anyone know how to get this working? I've already called At&t twice, and they say it should be working.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Is advanced calling enabled in settings/Network &internet/Mobil network/advanced. ??

If yes, then look at the link 2 posts above yours.
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
Yeah, it's enabled. I also checked the *#*#4636#*#*, and ran the ping test. Everything passed. Ims service status reads unavailable and not registered.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Have you looked here?

https://www.att.com/esupport/article.html#!/wireless/KM1046244
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
Yes

My sim has the 27
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Guess it's an at&t thing then my friend. I can't help you there. Good luck though.
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
Am I correct though, about the Verizon version being the same as the Google store version? Except for the locked bootloader?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep. And the Verizon bloat of course.
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
VoLTE is working! After the 4th call to At&t, I finally talked to a guy that knew exactly what the problem was. My software version was not updated on their end for some reason. He said that the software version was supposed to be 5 on At&t's system, but it was saying I was on version 1. He updated me to 5, and now it's working. This last call only took about 3 minutes. I wish it wasn't so hard to talk to someone who actually knows what they are doing. :good:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Don't ya just love Carrier War Games!!? Sheesh! Glad you got it working though ??
[Google Pixel 2 XL Guides, News, & Discussion] Halarican:
I have the "VZ" Pixel XL 2 and it didn't come with any bloat. I think the phone only downloads the bloat if you activate it with a VZ SIM, but I've been using it with an at&t SIM from day 1 and there was no bloat whatsoever.

To the issue at hand, I also had run around and make a lot of calls before I was able to get VOLTE to work. Some have mentioned that you also need Advanced voicemail provisioned in your account, and I did that and everything that was prescribed. Ultimately, I just went to an at&t store and got a new SIM (my original SIM met the guidelines), and after a reboot with the new SIM it started working.

Wifi calling is not an option that shows up for me under setting :/
[Google Pixel 2 XL Guides, News, & Discussion] uicnren:
Nor will it until/if AT&T enables it.
[Google Pixel 2 XL Guides, News, & Discussion] Surge1223:
Works on Verizon, but I'm on a custom rom, and I changed the crap out of carrier config and vendor overlays. I don't even use volte or wifi calling, I just hate Verizon so much I wanted to make sure I could help others screw them over as well.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
What happened man!!?? Did the Big Red undercover hit squad come to your house and steal your data?? Glad I'm not on your bad side Mr. Code master!! ????
[Google Pixel 2 XL Guides, News, & Discussion] cjxsutton:
Can you please be more specific? I talked to tech support and they had no idea what I was talking about.

I also have the 27 SIM and my account is set up for WiFi calling on AT&T's end, still not working.

I have the Pixel 2 and Pixel 2 XL straight from Google.

EDIT: Nevermind, VoLTE isn't an issue for me. I came here because of WiFi calling. I need WiFi calling, not sure why everyone is always talking about VoLTE in these threads that are clearly labeled "WIFI CALLING". They aren't synonymous.
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
You will have to keep calling until you get a representative that knows what’s going on. The last call that I made to AT&T, I told the guy that my Pixel 2 xl was for sure supposed to work with HD Voice/VoLTE. I told him that I received an update that was specifically for HD Voice on AT&T. That’s all I told him. He then checked the software on his end, and said that I was still on version 1 so he updated his end to 5 (whatever that means). I rebooted my phone and it worked. Remember, it took me 4 different calls to get this done. 3 of those calls were excruciating, the reps had no idea why my phone wasn’t working properly. BTW, I had the Verizon version of the Pixel 2 XL.

Edit...I just noticed your addition to the post. YOU CAN NOT GET WIFI CALLING. NO NO. Wifi calling only works on AT&T phones. Not sure why everyone keeps asking this.
[Google Pixel 2 XL Guides, News, & Discussion] ilal2ielli:
Because once upon a time, VoLTE also was an ATT branded phone feature too.
[Google Pixel 2 XL Guides, News, & Discussion] lyall29:
Yeah I know, I was just being a smart***. The guy I was trying to help out, seemed very upset that people on this thread are asking about VoLTE. :):good:
[Google Pixel 2 XL Guides, News, & Discussion] naiku:
Well, looks like this thread confirmed it. No WiFi calling on AT&T.... One more reason to look at moving to Fi then I guess.
[Xiaomi Mi A1 Questions & Answers] Ahmed Al-Sayed:
Hi guys .... every time I try to flash twrp.img via fastboot it says successful but when I boot into recovery I find it the stock one ... does anyone know what's wrong ??

ps : when I enter "fastboot boot twrp.img" it boots very well into twrp...but when I enter "fastboot flash twrp.img" it doesn't flash the new recovery .
[Xiaomi Mi A1 Questions & Answers] jimmy123322:
Download required files from downloads

Unlock your bootloader( u must be unrooted)

Reboot to bootloader

fastboot boot recovery.img

flash twp-installer.zip

reboot to recovery and check if twrp is there

, if not (100% chances)

Reboot to bootloader

fastboot set_active b (I am assuming you are on slot a, else use fastboot set_active a or you can change slot on twrp itself)

fastboot boot twp.img

flash twp-installer.zip

reboot to recovery

Success

Thanks to https://xdaforums.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
[Xiaomi Mi A1 Questions & Answers] bpodnar:
I have try that but when I flash twrp it says FAILED PARTITION TABLE DOESNT EXSIST and I am getting bootloop. If I try to fastboot boot recovery.img (twrp 3.1.1.0) then the device boots up instead going to TWRP recovery. I can boot only in newest TWRP 3.2 but cant flash anything from it. Tryed to choose SLOT A and B on REBOOT menu but no success. Please help!
[Xiaomi Mi A1 Questions & Answers] thezinq:
Same thing happened with me also and I BRICKED my phone
[Xiaomi Mi A1 Questions & Answers] coremania:
Try a clean flash of a stock rom, fastboot image of your choice, after that try the twrp boot and flash again. May there's something corrupt on your phones.
[Xiaomi Mi A1 Questions & Answers] AlwaysWin:
https://drive.google.com/drive/mobile/folders/1EAw5z0KFgSDFpniPiOHUDbcyQctmfZ1t

Download the files provided above and follow the same method as given by the OP.

By that recovery image , ur system internal memory will be accessable and u will be able to copy the twrp installer zip file in internal memory of phone .

Once done that , flash in both partitions and you are good to go.

THIS ONLY WORKS FOR OREO STABLE.

I'M NOT RESPONSIBLE FOR ANY KINDA OF DAMAGE DONE TO YOUR PHONE , so be aware and know about what u r going to do.

just use these files , but follow the same steps as u did before
[Xiaomi Mi A1 Questions & Answers] XAB235:
Thank you you saved my ass!
[Android Q&A, Help & Troubleshooting] abrakadabra_srb:
Hi everyone!

My friends and I are working on a custom AOSP based ROM for Nexus and Pixel devices which is targeting children as main users. The idea is to have a remote controllable, bloatware free, pure AOSP ROM that would allow parents to track their kids mobile usage. Some of the features would be:

Location tracking (constant or on request)

Block applications (block install, uninstall, running)

Internet access firewall per app (Mobile data and/or Wifi)

Restrict access to various settings and controls (camera, airplane mode...)

Panic mode: activated by the kid which locks the device and starts emitting location via SMS and to controlling app

Lock mode: activated by the parent so that the child can focus on other things (school, play time, night time...)

Mobile app for parents to control the phone

Peer to peer communication (via pubnub or ably) with data encryption (no data stored on servers, all on parents and child's device) between the ROM and the controlling app

No root access (of course)

Ad blocking and inappropriate web site restrictions via hosts file (later via proxy)

Since all features are system integrated, nothing can be overridden by the child

We are in a finishing phase of implementing this ROM and I would like to ask all of you parents who are thinking of giving their kids a phone to help us out in determining if this is something that they would use. Would be great if you could put in comments which device would you prefer or if you any other comment regarding the idea or ROM itself. We are targeting Nexus and Pixel phones since AOSP runs smoothly on them and there are no hardware related issues because we all know how kids get frustrated with a non-working phone :)

Thanks in advance!
[Android Q&A, Help & Troubleshooting] Pixlelelele:
Hi There,

I'm looking into phones for a child. I like what bark has to offer but don't necessarily want to use them. I looked a bit for custom roms and came across this...did it go anywhere?
[Samsung Galaxy Note 8 Questions and Answers] noahattic:
Hi guys,

Coming from an Exynos Note 5, I'm about to upgrade to Note 8. As always, I root and flash custom rom to my phone all the times, since I cannot stand the stock rom.

Now, I have this obvious question that a lot of note 8 noobies like me might have - which model will have the best dev supports?

Snapdragon or Exynos based devices??

millions of thanks in advance.
[Samsung Galaxy Note 8 Questions and Answers] Kalm_Traveler:
Several people have asked the same question here - you may want to search next time. The short version is that outside North America and Hong Kong, the Note 8 models are all Exynos, and those are easier to mod due to unlocked bootloader. The Snapdragon version does have a root method now, but per history the Snapdragon versions never have as much development as the Exynos versions.
[Samsung Galaxy Note 8 Questions and Answers] noahattic:
Thank you!

I will search more thoroughly next time. Exynos versions it is then.

I think they use snapdragon in chinese market too.
[Essential Phone Questions & Answers] cygnets:
Bit of a noob at this, but I was able to get the bootloader unlocked and install twrp recovery but after realizing that NMI81C is kinda old and being a sprint user and there OTA updatings being stupid slow I wanted to manually update to NMJ32F via adb sideload.

How do I do this? From what I read, you have to revert back to stock recovery via stock recovery.img but I cant seem to find any stock recovery.img online..

am I just stupid, a complete noob, or both?

Btw this is my first time trying this in years after switching from my note 4 to iphone, so this is basically all new to me lol
[Essential Phone Questions & Answers] elkay:
Yep, you need stock recovery to accept and sideload stock OTAs. They did release stock firmware images finally. I shouldn't assume the stock recovery is there, but I will say that it probably is.
[Essential Phone Questions & Answers] DAE1964:
You have the latest firmware for Sprint. The later is for all other carriers.

https://www.essential.com/developer/current-builds
[Essential Phone Questions & Answers] cygnets:
Indeed, I read that even though this is the current firmware for sprint users, its only because sprints OTA updates are ridiculiously slow. So as others can update OTA (those not with Sprint) we cant, UNLESS we manually download the update and use adb sideload to update. Which is what im trying to do, but because I have twrp recovery already installed on build NMI81C, I need to revert back to stock firmware but can't find any stock firmware for NMI81C thus leaving me stuck on NMI81C with twrp.

Not only that, is root check is saying its not rooted.
[Essential Phone Questions & Answers] Barshalen:
Download the NMI81C firmware from https://www.essential.com/developer/current-builds and then you should be able to just flash the boot from that package by adding .img to the "boot" file and then flashing it via "fastboot flash boot boot.img". After that you should be able to boot into the stock recovery and then select apply update via adb. Just use the command "adb sideload ota.zip" to begin the update.
[Essential Phone Questions & Answers] cygnets:
Just a closer, was able to revert back to stock firmware but on firmware NMJ20D and remove TWRP recovery. I just finished installing the NMJ32F firmware on my Sprint variant. No longer on NMI81C :D

now I can start looking into getting TWRP and such back on my phone, thank you guys
[Essential Phone Questions & Answers] cygnets:
damn I just got done doing all that without help, but thank you for that. I didnt have to download the NMI81C firmware tho, just went straight to NMJ20D and then updated to NMJ32F.
[Essential Phone Questions & Answers] timkennett:
After sideloading latest firmware, does the bootloader still say Variant - Sprint? Is there a way to make the Variant openus since the hardware is the same?
[Essential Phone Questions & Answers] kbonnel:
Oh, do keep us informed if you find a way to modify the Variant. My phone doesn't list anything after Variant (no Sprint or OpenUS) even though I bought mine from Sprint. I sent a tech request to essential, waiting to hear back.
[Oukitel (All phone models)] DerTeufel1980:
​

This is a Official Build of madOS ( based on AOSP Oreo ) for Oukitel K6000 Plus with MTK 6750 SoC

madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Installation Instructions:

Download ROM from M.A.D. Facebook

OR from xda DevDB

Download OpenGapps nano or pico from OpenGapps

(choose Arm64 and Android 8.0 )

Backup

Unlock Bootloader Bootloader unlock

Flash new mandatory new Oreo TWRP (available on downloads)

Boot to the new TWRP recovery

full Wipes (dont come crying if you didn't .. ;p )

Install rom (optionally following by GAPPS if you use them)

Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').

Reboot System

Working:

RIL (Calls /SMS, Data connection, etc)

Wifi

Bluetooth

FM Radio

All Sensors (including fingerprint)

Lights; HW Keys

Both storages & MTP

HW de/encoding

Camera (photos and video)

GPS & aGPS

Audio

madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)

Not working:

nothing known

XDA:DevDB Information

madOS_O_K6KP, ROM for all devices (see above for details)

Contributors

DerTeufel1980, superdragonpt, fire855

Source Code: https://github.com/MediatekAndroidDevelopers

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.x

ROM Firmware Required: bootloader unlocked, twrp

Based On: AOSP

Version Information

Status: Stable

Current Stable Version: 1

Stable Release Date: 2017-11-19

Created 2017-11-19

Last Updated 2017-12-31
[Oukitel (All phone models)] DerTeufel1980:
Reserved

How-To unlock Bootloader and install TWRP

ATTENTION: This is voiding your warrenty

Install minimal adb and fastboo to your PCt: Minimal ADB and Fastboot

On the smartphone: Go to Settings --> About Phone and hit 'build Number' seven times, to enable 'Developer Options'

Go to Settings --> Developer Options, and allow usb-debugging and allow OEM-unlocking (For bootloader unlock)

Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc

Start 'Minimal adb and Fastboot' at Pc. In the command window, type: "adb reboot bootloader" and press Enter (this is restarting the smartphone into the bootloader)

WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty! In the command window, type "fastboot oem unlock" and press Enter (to unlock the bootloader). You probably need to press some button of the phone to confirm (check the display for this)

Download the Twrp image: Oukitel K6000 Plus TWRP, and copy the recovery.img file to the installation folder of 'minimal adb and fastboot'

In the command window, type "fastboot flash recovery recovery.img" and press Enter. After successful flash, enter "fastboot reboot" in the command window, press 'Enter'. Then immediately press and hold 'volume up key' on the smartphone (Until a small menu appears)

3 options appear on the smartphone: Recovery, Fastboot, Normal. You can navigate with 'volume up key' and confirm your selection with 'volume down'. Navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)