yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Q&A, Help & Troubleshooting] vergilbt:
Correct me but you did replace the phone because the color of border from fingerprint sensor was changing? [emoji33] [emoji33] [emoji33]
[OnePlus 2 Q&A, Help & Troubleshooting] Aleycat:
The color was not changing, the chrome lining had worn off so it was really noticeable wear. After just 2 days of getting the phone it seemed unacceptable for it to wear so fast. My replacement is perfect and has no signs of wear.
[OnePlus 2 Q&A, Help & Troubleshooting] Labhya:
Can you see some signs of corrosion on your replaced device? I'm facing the same problem, I will go to service center soon for replacement. How much time they took for replacement?
[OnePlus 2 Q&A, Help & Troubleshooting] krishna442:
The chrome lining(if you call it so) has generated some spots on it. My OPT didn't even fall down. It looks disgusting.
[OnePlus 2 Q&A, Help & Troubleshooting] wtoj34:
Mine looks like crap too, but my home button is 100% broken so the lining is the least of my problems, really. Lol
[OnePlus 2 Q&A, Help & Troubleshooting] muqtaliff:
Same here. The lining has partially worn off after around two months. But the button and fingerprint sensor work fine so I will live with it.
[OnePlus 2 Q&A, Help & Troubleshooting] evertking:
Chrome? Hmmm mine is black. But that was my only gripe about the OnePlus one. My metal rim around the phone started falling. If that was metal?
[8125, K-JAM, P4300, MDA Vario ROM Development] Adrock1492:
I used a registry hack to delete the Outlook folder and I also deleted the Active Sync folder in the same registry. After rebooting the SMS text inbox notification no longer works. I've gone into the registry and reactivated the inbox received message notification & i have the the notification on in the Sounds section on the Settings menu in WM5. Do i need to flash back to the original settings and start from scratch or is there a tweak/setting that i'm missing?
[8125, K-JAM, P4300, MDA Vario ROM Development] Huckleberry88:
Can't help you with the settings but a hardreset would do I suppose - no need to reflash.
[Moto G 2015 General] hp420:
Marshmallow comes with a new native wifi calling feature, but it's hidden on Moto G3. Here's how to enable it:

Step 1

download and install this app:

https://play.google.com/store/apps/details?id=de.szalkowski.activitylauncher

Step 2

run the app and click the pull-down menu up top. choose "all apps"

scroll to settings and expand the list. scroll down to wifi calling:

Long press the wifi calling option and select "create a shortcut"

Step 3

navigate to your home screen and find the new wifi calling icon. click it and turn on wifi calling
[Moto G 2015 General] tember1214:
Awesome!!! When I go and turn it goes on but going back into shortcut it's off. Any ideas?
[Moto G 2015 General] hp420:
we may need root to be able to keep it enabled, or possibly just have it set as on by default with a custom rom.
[Moto G 2015 General] Selmak:
Out if curiosity I tried this, and got the same thing as well on CM13. As soon as I leave the activation screen it shuts off.
[Moto G 2015 General] nelsonw:
You can install 3rd party Voip servers?
[Moto G 2015 General] FW_16:
Any update to get Wi-Fi calling to stay on?
[Moto G 2015 General] melp57:
Maybe it won't stick unless you are on a network with WiFi calling?
[Moto G 2015 General] tgsboats:
Can the activitylauncher be used to turn on wi-fi calling feature with the new moto g4 play?
[Moto G 2015 General] acejavelin:
If the features is in your device but hidden, probably... If it's not capable, disabled, or removed, no. All activity launcher does is create a shortcut for an app or activity that's already installed on your device, it doesn't add new features other than its own (to create shortcuts to things).
[Moto G 2015 General] tgsboats:
I don't have the Moto G4 Play yet, thinking of purchasing it but first I need to know if the phone has wi-fi calling feature. How can I find out if this feature is available on the G4 Play?
[Moto G 2015 General] acejavelin:
Probably look or ask in the Moto G4 Play group... http://xdaforums.com/g4-play
[Moto G 2015 General] melp57:
I have the 3g and on TMobile. They have wifi calling.

Unlike the iPhone that actually has a setting for turning it on and off, the 3g has no such feature. It is a feature of MM. Don't understand if you can turn it on with activity launcher why it doesn't work. Doesn't even stay on. I know with TMobile and the iPhone, first time you turn it on you have to verify your address for 911 purposes. So I guess only certain phones actually support wifi calling, even though MM has it built in.
[Moto G 2015 General] tgsboats:
Thank you for the reply melp57 - not sure what MM stands for, please explain?
[Moto G 2015 General] Gravemind2015:
MarshMallow Android 6.0

Broadcasted from Zeta Retuculi
[Moto G 2015 General] the-german:
Yes. Activity launcher does give you the same options on moto g4 play. But wifi calling will not stay on, at least not on stock rom, on metro pcs, which supports wifi calling on branded phones and is included in my plan
[Moto G 2015 General] mrViZhy:
This solution not working. Welkome to thread created by me:

https://xdaforums.com/2015-moto-g/help/vowifi-wi-fi-calling-moto-g-2015-osprey-t3632789

There i'm asking about enabling Wi-Fi calling on our devices.;)
[Moto G 2015 General] douglascrp:
Same thing here.

Once the app is closed, it is disabled again.
[Moto G 2015 General] ppgirl:
Many retail mobiles have "Wifi Calling" function but not any menu entry to enable , The APP can check the hidden function and enable it if can use.

https://play.google.com/store/apps/details?id=com.widget7.wifi.calling
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] stephenju:
I have TWRP on my 8.4 right now. What's the difference between it and CR? And how can I replace TWRP with CR?

Thanks.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] AndyYan:
CR is very limited in function and IMO shouldn't be used at all. To try it out, download one of the recovery images available from CM's nightly site and flash it with appropriate tools.

Sent from Google Nexus 4 @ CM12.1

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Shield Tablet Original Android Development] Steel01:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

DOWNLOAD:

Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed

1) Download the latest version from our website on your device

2) Reboot to TWRP

3) Hit Install and tap the "Images..." button in the lower right

4) Browse to the location of the TWRP image on your device and select it

5) Select recovery from the partition list and swipe to flash

OR:

You can find more information and download links on our website.

Direct device link

BUGS:

If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:

Live support is available via #twrp on Freenode with your IRC client or just click this link.
[Shield Tablet Original Android Development] Steel01:
Releases including and past 3.0.2-2 will work on both the L and M bootloader. The screen update issues plaguing unofficial 3.0.0 do not happen on these newer builds either. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
[Shield Tablet Original Android Development] hardslog:
Don't you love the smell of success in the morning? :laugh:
[Shield Tablet Original Android Development] sabret00the:
Finally, official status!
[Shield Tablet Original Android Development] sbdags:
Nice! Nice! Nice!

Time for me to get some more roms out I guess ;)
[Shield Tablet Original Android Development] DaveTheRave:
ro.product.device missing?

Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.

Can anyone care to confirm if this is an issue with the official recovery image?
[Shield Tablet Original Android Development] lj50036:
Yes, It is an issue I am working on.. :good:

Thx for the feedback, I will be posting a working version soon.. :D

Thx Josh

EDIT:

Can I get some feedback on this, seems to be working as expected... :good:

Changelog:

Remove vendor init, cm is able to install now.

TWRP 2.8.7.1 DOWNLOAD LINK !!

Thx Josh
[Shield Tablet Original Android Development] el3ctrik:
Hi Josh,

I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:

E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled

I tried using the

adb shell twrp decrypt <pin>

command to decrypt using adb, but get the following response:

Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.

This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
[Shield Tablet Original Android Development] lj50036:
Yes, this is a HUGE issue..... :(

I need to look at making this happen....

Thx Josh

EDIT:

Ok lets give this a go :)

Changelog:

Added decryption support.

TWRP 2.8.7.2 DOWNLOAD LINK !!

Thx Josh
[Shield Tablet Original Android Development] philipp21897:
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
[Shield Tablet Original Android Development] lj50036:
I am going to need just a bit more :)

Please run: adb pull /tmp/recovery.log

Upload or pastebin the output

Thx Josh
[Shield Tablet Original Android Development] An Droid:
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:

http://xdaforums.com/showthread.php?t=2877117

Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
[Shield Tablet Original Android Development] Steel01:
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.

[MENTION=5123642]lj50036[/MENTION]: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
[Shield Tablet Original Android Development] lj50036:
I started with a similar device tree, but did some cleaning up :)

The device tree is linked in post #2

Thx Josh

Dont forget to check gerrit... :p

http://gerrit.twrp.me/#/c/1115/

Thx Josh
[Shield Tablet Original Android Development] Steel01:
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.

*peruses changesets*

*is skeptical that it will work right*

I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.

Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?

The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
[Shield Tablet Original Android Development] lj50036:
Ok, that is a lot to take in......

I am more then willing to work with anyone that is willing to work with me.....

I am still learning everyday... :)

If you would like to join us on irc feel free, that is going to be the best for me....

Thx Josh
[Shield Tablet Original Android Development] Steel01:
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
[Shield Tablet Original Android Development] lj50036:
TWRP IRC

Network: freenode

Channel: #twrp

Thx Josh

EDIT:

Huge thx to [MENTION=1416222]Steel01[/MENTION] for all his help with this project..... :good:

Changelog:

Reforked kernel source, vendor init is working as expected....

TWRP 2.8.7.3 DOWNLOAD LINK !!

Thx Josh
[Shield Tablet Original Android Development] el3ctrik:
Hi Josh - just had a chance to test 2.8.7.3 on my encrypted device and working perfectly.

Thanks!
[Shield Tablet Original Android Development] SdtBarbarossa:
did you already saw this?

http://xdaforums.com/showthread.php?p=64143425

ti fix just define the props correctly via override (i dont know if its shield or shieldtab or anything like that )
[Shield Tablet Original Android Development] D-m-x:
[MENTION=1416222]Steel01[/MENTION]: Thank you for the updated TWRP, it seems actually faster :)

Altough my Adopted Storage isn't recognized, I am only seeing Internal, Micro SD and USB OTG (bith 0MB which is of course right). Not seeing anything in the Logs like failed Mount etc. like how it was in previous Versions. Am I missing something here?
[Shield Tablet Original Android Development] Steel01:
No, you're probably not missing anything. I reapplied an old fix for adopted storage that had been lost, but apparently that wasn't enough. Guess that's back on my list of things to check.
[Shield Tablet Original Android Development] D-m-x:
Ok thanks, just tell me if I can help in any way!
[Shield Tablet Original Android Development] nathan-96:
[MENTION=1416222]Steel01[/MENTION] When flashing a rom with the latest TWRP, I get the error: "this zip is for 'shieldtablet' your device is ' ' "(Empty string). Flashing with older TWRP works fine.
[Shield Tablet Original Android Development] Steel01:
Sounds like init didn't detect the device model correctly. Which model do you have? Also, can you paste the contents of /proc/cmdline?
[Shield Tablet Original Android Development] nathan-96:
I have an K1, it happend when I tried to flash an optimized stock rom.

I dont have an cmdline folder inside my proc folder :/

https://photos.app.goo.gl/fUzHsuvqcNOPlhKh1
[Shield Tablet Original Android Development] Steel01:
It's a file, not a folder. Will look similar to:

androidboot.hardware=tn8 buildvariant=userdebug androidboot.security=unlocked tegraid=40.1.1.0.0 mem=2010M@2048M memtype=0 vpr_resize tsec=32M@4064M otf_key=*snip* ddr_die=2048M@2048M section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*snip* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset touch_id=0@9 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 lp0_vec=4096@0xfdaff000 tegra_fbmem=18743296@0xad012000 core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 nck=1048576@0xfdb00000 android.kerneltype=normal androidboot.bootreason=pmc:power_on_reset,pmic:PwrOnLPK vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Might want to scrub the serial and otf_key like I did. But the main part I'm looking for is the second field in the board_info parameter. 0x00ea is the wifi only models.
[Shield Tablet Original Android Development] nathan-96:
androidboot.hardware=tn8 buildvariant=eng androidboot.security=unlocked tegraid=40.1.1.0.0 mem=2010M@2048M memtype=0 vpr_resize tsec=32M@4064M otf_key=*scrubbed* ddr_die=2048M@2048M section=256M commchip_id=0 usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 androidboot.serialno=*scrubbed* androidboot.commchip_id=0 androidboot.modem=none androidboot.touch_vendor_id=0 androidboot.touch_panel_id=9 androidboot.touch_feature=0 androidboot.orientation=0 androidboot.batterytype=1 fiq_debugger.script=reset touch_id=0@9 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,3 sku_override=0 usbcore.old_scheme_first=1 lp0_vec=4096@0xfdaff000 tegra_fbmem=18743296@0xad012000 core_edp_mv=1150 core_edp_ma=4000 board_info=0x06e1:0x00ea:0x04:0x00:0x00 tegraboot=sdmmc gpt gpt_sector=41983 modem_id=0 nck=1048576@0xfdb00000 android.kerneltype=recovery androidboot.bootreason=pmc:software_reset,pmic:NoReason vmalloc=300m androidboot.bootloader=4.00.2016.04-8b2413b7

Thanks, here it is :)
[Shield Tablet Original Android Development] Steel01:
That looks fine. Weird... Was is the output of the following two commands:

getprop ro.hardware

getprop ro.product.name
[Shield Tablet Original Android Development] nathan-96:
tn8 & wx_na_wf

Is it possible that it happens because I formatted every partition in twrp?
[Shield Tablet Original Android Development] Steel01:
Eh? If those are set, then why is it failing?? How about

getprop ro.product.device

getprop ro.product.name

Also, what are you trying to flash? And no, wiping won't break things like this.
[Shield Tablet Original Android Development] nathan-96:
ro.product.name & shieldtablet

I tried flashing last official lineage ;)

---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------

shieldtablet & wx_na_wf
[Shield Tablet Original Android Development] s2berto:
Yet Another Bootloader Unknown Issue (aka, YABUI)

I am stuck here, folks. Samsung devices are more my comfort zone, so figure I have hit something unique on the Shield Tablet. I am trying to install LOS 14.1 on my wife's ST K1 via TWRP 3.1.1-0 and I get the 'supports bootloader 4.00.x ... bootloader unknown ... error 7' issue. I have flashed boot.img from the LOS zip and a stock boot.img from nvidia, but still come up with differen bootloader versions.

I have ADB, fastboot & TWRP at my disposal, but no bootable OS. Any suggestions on installing the real 4.00.x bootloader?

TIA, s2
[Shield Tablet Original Android Development] Steel01:
[MENTION=4915333]s2berto[/MENTION] Bootloader is not what's in boot.img. You want the file linked in the opening post to my Lineage thread, the one labelled firmware. Flash that in twrp and reboot once. You'll have to let it try to boot android normally for the update to actually apply. At that point, you can go back to twrp and flash lineage as expected. The check is there to prevent issue with firmware/bootloader incompatibilities.
[Shield Tablet Original Android Development] s2berto:
My fault

Thank you for your quick reply, Steel01. I think I had two problems: 1 ) I was thinking boot.img covered the bootloader, not the boot partition. 2 ) I did not fully read the MOP. My familiarity with Galaxy stuff, LINUX & UNIX probably made me go 'Yep, yep, got it'. Very bad procedure for an IT guy...

I will start afresh in the morning and heed your instructions.
[Shield Tablet Original Android Development] Steel01:
So, Nvidia does handle things differently. It's not hard to assume it'll work like all the Qcom stuff out there, but it's not true. QCom stuff (which covers the US Galaxy variants) has multiple firmware partitions you directly flash to update stuff. Nvidia instead using a staging partition. You flash a blob to the staging partition and during boot, the system checks to see if the blob is valid and if so, applies it to all relevant partitions and reboots. So, it is an extra step, but it does allow for better sanity checks and prevent simple bricks.
[Shield Tablet Original Android Development] skorpiodav:
I tried the latest version twrp-3.2.3-0-shieldtablet.img but the adopted storage is not detected, is this right? I'm looking for a versione higher than 3.1.0.0 to use with TWRP backup tool to backup directly to PC. I found a modified 3.1.0.2 version that works but I would like to use an official and updated version.
[Shield Tablet Original Android Development] Son-j:
I tried using TWRP 3.2.3.0 bit it seems that it can't write to SD card so I cant put my back up there. Any suggestion?
[Shield Tablet Original Android Development] Adai0:
I have this problem too. I formatted the sd card as internal storage which does encrypt it. TWRP sees the sd card. However it looks like it cannot encrypt the card.

[MENTION=1416222]Steel01[/MENTION]: Is there any chance you can have a look into this soon? :D
[Shield Tablet Original Android Development] Steel01:
Oh, the adopted storage issue again. :meh: Well, that *should* have worked on 3.2.3-0. There had been some issues with a few of the twrp releases using older versions of my device tree, so that's where I would have assumed the problem came from. But 3.2.3-0 should have had that fixed. I don't personally use adopted storage, so I have to go out of my way to test it. I'll try to find some time over the weekend to set that up on one of my test tablets and see what's going on.
[Shield Tablet Original Android Development] Adai0:
Any chance to help you? I'd be ready to do a test :) Also, is there a version known to be working so that it is possible to compare the sources? I've found a working version from BitO BSessiOn (TWRP_3.1.0-0_multirom_shieldtablet_20170324-02_BitO BSessiOn.img) though no sources. Although I've never been built TWRP yet, but I'd be willing to learn something new and give it a try ;)
[Shield Tablet Original Android Development] gullkhan0:
Do you mean you can't access various folders or some are missing in TWRP? If that's so, I'm having same trouble as you. Could you please post the link to the modified recovery you mentioned, thank you.
[Shield Tablet Original Android Development] skorpiodav:
The issue is TWRP can't see the external SD so is not possible to access its content.

Sadly I'm not able to find the source but it was a post from Xda, the version I'm using is named: TWRP_3.1.0-2_multirom_shieldtablet_20170415-01.img can't attach it because it is too big but probably you can find it online or maybe you can find the original post (I'll try to find it again when I have more time).
[Shield Tablet Original Android Development] gullkhan0:
Thanks. I tried it and it gets stuck at the splash screen whenever I try to run it. Gonna flash back the official version.
[Shield Tablet Original Android Development] kbeezie:
I can choose MicroSD as a storage option, but course it's only going to show 15MB free, but that is because I've used my SD card formatted as internal/adopted storage. So I wouldn't expect TWRP to treat it as anything other than internal data (like how can you make a backup of "data" to a volume that's treated as a part of it).

I just assumed that if I had it as portable storage, TWRP would be able to see it.

I just been using an OTG cable and backing to an external 64GB or 128GB thumbdrive formated as exFat without any issues.
[Shield Tablet Original Android Development] Disrupthor:
Hi there, is there any plan to add f2fs support? Thank you. @Steel01