yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 7 Questions & Answers] DelphinusMinor:
Nova Launcher Prime is good and my goto launcher. Square Home 3 is a nice Windows 10 launcher. I also recommend Smart Launcher 5. It's handy they way it automatically sorts your apps into categories.
[Xiaomi Redmi Note 7 Questions & Answers] jamespmi:
I think that depends on the personal taste of each one... I prefer 100x Lawnchair 2 over Nova.

https://twitter.com/lawnchairapp/

Download on ApkMirror https://www.apkmirror.com/apk/deletescape/lawnchair/lawnchair-2-0-2168-ci-alpha-release/
[Xiaomi Redmi Note 7 Questions & Answers] tomax80:
Try Poco Launcher...runs very good and it integrates with miui
[Xiaomi Redmi Note 7 Questions & Answers] NeoDJW:
+1 , its great
[Xiaomi Redmi Note 7 Questions & Answers] Quaresma_7:
I'm also very happy with Poco launcher. I could only last a couple hours in MIUI without an app drawer so I installed the beautifully compatible Poco Launcher and looked no further. The updates have only made it better (night mode, MIUI 10 icon animations), can lock the phone with a double tap, great overall.

How does Nova compare to Poco on the Note 7?
[Samsung Galaxy S8 Questions and Answers] _McShane_:
Like the ability to hide magisk, is there such a thing for when you're mirroring the phone? When streaming with the Sky Q app while also mirroring, I get an error saying "you can't stream anything while connected to another device." I have an S8 and it's rooted. Thanks!
[Galaxy S 5 Q&A, Help & Troubleshooting] ineedromsz:
Sooo basically I have this GS5 and it had a custom rom- I think it was Lineage OS 15 or 14.1 (or a different rom)

My sister was using it (it was her phone) and she told me it blacked out. The phone had glitched a couple of times but i didn't do anything about it. January this year it fully blacked out, never to turn on, charge and go to download/bootloader mode again. I've looked around on Google but i haven't seen a solution. I've tried cleaning out the charging port, removing the battery, tried to boot it into bootloader, connect it to PC, and I've looked around on iFixit but there wasn't anything helpful. If anyone could help give any help, software or tips that would be appreciated.

Device-

Samsung Galaxy S5

SM-G900F

Locked to EE

On Custom Rom
[Galaxy S 5 Q&A, Help & Troubleshooting] ineedromsz:
If you need to see pictures then tell me below
[Windows 10, 8, 7, XP etc.] master dm:
If all of these problems are any indication, Microsoft has a lot of work to do. Plus, there are still a lot of Windows 10 problems that are still around, like printer connectivity issues. But, who knows, maybe Microsoft will actually fix some of these problems in the Windows 10 May 2019 Update, which should be out soon.

Still, if you’re having a hard time with the operating system, we’ve compiled a guide to 100 of the most common Windows 10 problems, and how to fix them – whether it’s a Windows 10 problem with a printer or connectivity issues. So, if you’re trying to troubleshoot your device, keep reading.

1. Having enough space to install Windows 10:

If you're planning to move to Windows 10, actually installing the OS is the first area you could potentially run into problems with. Installing a new operating system requires a certain amount of free space on your drive so that it can be downloaded and certain elements can be run successfully.

For Windows 10, the space requirement is 16GB, which should be kept free on the main system drive the computer uses. This is actually the same as previous versions of Windows, so if you've upgraded before you can most likely do it again.

If you want to check how much space is left on your PC, go to My Computer (or This PC, depending on which version of Windows you’re running) where any drives you have will be listed. You can see the remaining space indicated beneath each drive, or you can right click and select Properties for a better overview (your system drive is usually C:)

2. Checking you have a powerful enough PC:

Just as with space requirements, your PC will also have to be capable of running Windows 10. This means that it must reach certain minimum system requirements.

The requirements for running Windows 10 are relatively low: A processor of 1GHz or faster; 1GB (32-bit) or 2GB (64-bit) of RAM; 16GB of free drive space; Microsoft DirectX 9 graphic device; and a Microsoft account combined with internet access.

To find out your PC's spec, go to Control Panel and select System and Security, then System.

However, keep in mind that these are the minimum requirements, and you should shoot for higher specs to have a smooth and enjoyable experience.
[Windows 10, 8, 7, XP etc.] ShadowEO:
It's no worse for device compatibility than Windows 7, considering that many drivers are likely ports up from W7. That said, as you pointed out, Windows 10 is still a WIP OS and does get better with each feature update. However they've resolved your space issues with the Reserved Update partition, as long as you have enough space for the Reserved partition, the update should work.
[T-Mobile LG G4] xxxmem60:
hi guys so i got this lg g4 h811 and was wondering if the h815 housing body frame compatible to the h811. I kind of a broke the body frame of my h811 and i was having a hard time finding the most parts since i live here in the philippines because lg g4 is not a very popular model here and most parts i can find online are parts for the h815 version only. It might be kind of a noob question but i haven't seen the h815 version yet and i just want to make sure if they have the same hardware parts because i don't have the luxury of wasting money on the wrong hardware parts since i dont have that much money:(:( . I really need the advice :crying: thank you
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] benparker:
The K20 Pro is a no brainer at this price.

MOD EDIT, YT link removed
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] Turbine1991:
Did they slightly overclock the cpu or something!?
[Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D] strongst:
Thread closed as it violates the FORUM RULES

strongst

Forum Moderator
[Galaxy S III Q&A, Help & Troubleshooting] Alezzzito:
Hi guys, so I have a S3 wich is in an endless bootloop since yesterday, but the thing here is that I already removed the power button from the board, hoping that would cause the loop to stop, but it didn't, I can't get in download mode because it restarts, can't get on recovery either because it restarts too.

I thought that without the power button it would be impossible that the phone could get stuck in bootloop but here I am, so does anybody knows what could that be, or what could I do? I don't know what to think by now.
[Galaxy S III Q&A, Help & Troubleshooting] theandroid02:
Are you able to boot into download mode?
[Galaxy S III Q&A, Help & Troubleshooting] rodman01:
I suggest to take the battery out for some minutes and try it again. if this is also not working then the only thing remaining is to try it with a jig usb "stick". It costs only a few euro/dollar and will start the device in usb mode.
[Tilt, TyTN II, MDA Vario III General] Jed D`Lagged:
There seem to be issues with Windows Mobile 6.1 and Landscape.

If you switch the display to landscape, and reboot the phone, it will change back to portrait.

If you press the missed calls button in HTC Home while in landscape, it will switch back to portrait.

Anyone have any ideas on how to fix this?
[Tilt, TyTN II, MDA Vario III General] Jed D`Lagged:
Alright, I fixed the missed calls issue with a new dialer, but the phone still consistantly boots into Portrait.
[Tilt, TyTN II, MDA Vario III General] bapssystupr3m3:
i'm not too sure but i would assume u have a kaiser...and when u say it boots into portrait i assume its a soft reset or a power on...and i assume that when you're in landscape mode u have the hardware keyboard slid out...if it boots to portrait...cant u just slide in n out the keyboard to have it go back to landscape?
[Tilt, TyTN II, MDA Vario III General] Jed D`Lagged:
Sure, when I slide out the keyboard, it goes into landscape. However, when I close it again, it goes back into portrait.

If, after the phone has booted, I go into Screen options and change it back to Landscape, it will stay in landscape regardless of what I do.

When I soft-reset, it goes back into portrait. If they keyboard is open, it will start in portrait, then shift into landscape. Upon closing the keyboard, it's back to portrait.
[Tilt, TyTN II, MDA Vario III General] NotATreoFan:
This is the default behavior for HTC devices. My Wizard did this just like my Tilt. I would suspect the cause is because when you slide out the hardware keyboard, a sensor activates a service running in the WM subsystem that tells WM to rotate the screen.

However, if you actually go into the screen options and change the default screen orientation to landscape, the registry is updated to reflect landscape as the new default orientation.
[Tilt, TyTN II, MDA Vario III General] Jed D`Lagged:
So yeah, done that.

Windows Mobile 6.0 did not have this problem. If you set it to Landscape in screen options, and rebooted, it would stay in landscape. This issue with it always booting in portrait is new in 6.1.
[Tilt, TyTN II, MDA Vario III General] nunorsilva:
Same problem here.. anybody found any solution? Thanks.
[Google Pixel 3a Guides, News, & Discussion] duh1:
There seems to be a lot of confusion concerning how to flash, root, and update these new a/b devices, with a lot of adventurous users bootlooping or even bricking their devices. Thought it might help to provide some basic guidelines some of you might find useful. Not intended to be exhaustively inclusive...

1. Know what you are doing before you do it, not after. Ask before try.

2. Unless you are an expert, do not be first in line to try untested procedures. Have some patience and wait for the definitive guide.

3. Do not flash images from a different model device to yours.

4. Keep your current active slot on the same version of firmware as it is your fall back when things go wrong in the inactive slot. Simply put, flash new firmware to the inactive slot, otherwise you risk bootloops.

5. Only when you have successfully booted an updated firmware, then the inactive slot becomes your current active slot, and the now inactive slot becomes your backup of the previous version.

6. Do not reboot your device out of frustration unless you are sure the active slot has a uncorrupted current system boot image. Otherwise you risk the device not booting into system.

7. Do not relock your bootloader unless you have just flashed a complete stock firmware. Otherwise you risk bricking your device.

8. Do not mod beyond your skills until you have a custom recovery installed, such as TWRP, and an nandroid backup of a working system.

9. Do not update your system or Magisk without a nandroid backup to restore when things inevitably go wrong.

10. Do not flash or OTA update a ROM without first enabling USB Debugging for ADB and Fastboot access, plus creating a TWRP nandroid backup of your working system to restore when it goes wrong. Also, an ADB or Titanium backup of your apps and data, plus phone databases to restore if successful.

How to fix a bootloop or booting directly into recovery:

1. When you are stuck on the boot screen, you can turn off by holding the power button until it shuts down.

2. From phone off, press & hold Power + Volume Down button for a few seconds to boot your phone into bootloader mode.

3. Reflash a current system stock boot image to the active slot and reboot. You can test it first...

fastboot boot stockboot.img

4. If that doesn't work, see if you can go back to your previous system in the inactive slot. In bootloader mode...

fastboot set_active other

and reboot.

5. If all else fails and you do not have a nandroid backup to restore, flash-all stock firmware removing the “-w” from the script to preserve apps, settings, and data.

Helpful Guides:

Android Backup Types...

https://android.stackexchange.com/tags/backup/info/

A/B Seamless Updates & Commands...

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

Magisk Docs...

https://topjohnwu.github.io/Magisk/

Magisk-MagiskHide Install & Troubleshooting Guide...

https://www.didgeridoohan.com/magisk/

Pixel Firmware Images...

https://developers.google.com/android/images
[Google Pixel 3a Guides, News, & Discussion] pbanj:
while number 3 is a great rule of thumb, it isn't always true. like the stuff for the 3a and 3a xl are pretty interchangeable, same with the other pixels. there are a few other phones like that also. maybe add "unless it has been confirmed to work"
[Google Pixel 3a Guides, News, & Discussion] duh1:
I had that in there originally, but for most, it's just a better habit to download firmware for your specific model. Even if there's some partition images that are the same, not all will be.

The 3a and 3a XL boot and system images have different checksums -- could just be model identifiers, but I've seen that cascade into driver issues and hardware malfunctions. Why risk it...
[OnePlus 6T  Questions & Answers] notorious.dds:
So, I've been reading ad nauseum on this topic with regards to flashing new ROMs on my 6t and getting locked out due to decryption.

Among other threads and places across the interweb, I've read all of these:

https://xdaforums.com/search/forum/8259?query=Encryption

During my travels I've discovered that the s**t doesn't really hit the fan until "data" is wiped via TWRP. I see that the recommend process for flashing new ROMs goes like this:

Boot on twrp

Flash ROM

Flash twrp installer

Reboot to twrp

Factory reset

Reboot to system

Am I understanding this correctly that if I transpose steps 4 and 5, then I shall plan on losing all of my data, but if I reboot from TWRP (right back into TWRP) before step 5 (aka data wipe), I shouldn't loose my data?

Assuming that is correct, does it matter if I leave a lock screen password enabled before rebooting to TWRP from the soon-to-be replaced ROM? I ask this because removing the lock screen password did not seem to reduce my chances of encountering permananly encrypted data.

Thanks!
[OnePlus 6T  Questions & Answers] idkwhothatis123:
Yes. For the love of god. Someone please clear up how we can flash on the go. I don't always have access to a computer with Adb/fastboot.

Every time I try to switch roms, upon rebooting to TWRP, my folders encrypt. Then I have to format data and voila, no fricking ROM to flash and I'm stuck
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Yeah A/B partition are a nuisance when it comes to flashing. I'd recommend you to do a clean flash of the ROM. Follow these steps.

1. Download the Latest Stable OOS from OnePlus's Website. Download the ROM ZIP of your Choice as well as the latest TWRP Installer. Transfer these to your phone and also copy them to a Laptop as you might have to Format Data.

2. Now Reboot to Recovery and flash OOS ZIP and TWRP Installer. Let it finish. Once it's done Reboot to Recovery from Within TWRP.

3. Again flash OOS and TWRP Installer. If for some reason your folders are messed up (as you posted in the image earlier) just go to Wipe and Format Data. And transfer the OOS and TWRP Installer to Internal and Flash them. Let it finish.

4. Once that's done, now again Reboot to Recovery and now flash ROM and TWRP Installer. After that's done, again Reboot to Recovery.

5. Again, flash ROM and TWRP Installer. Once done, Reboot to Recovery.

6. Now flash Gapps of your Choice. Stock are Recommend while anything above Nano will work. AROMA won't work. Once Gapps are flashed now go to Wipe and do a Factory Reset (Swipe to Factory Reset). Once that's Done, hit Reboot System and wait for the ROM to Load.

7. After the Initial Setup, Reboot to Recovery and flash Magisk and Custom Kernel if you want.

Personally I Format Data after flashing Gapps to get a "clean install". But that's not necessary. Also if you want to flash ROMs often I'd suggest investing in Swift Backup. It's an excellent app for Backups and can Backup almost Anything. Hope this helps.

This is what I do. Occasionally I get the Encrypted Folders but if followed correctly all is smooth. I can flash any ROM without Encryption. Except maybe stock OOS.
[OnePlus 6T  Questions & Answers] notorious.dds:
Thanks Mannan.

However, what I'm really looking for is someone to explain the following:

1. Which action or actions is it that triggers the phone to be encypted without a way to decrypt when flashing a new rom? My suspicion is that if the phone was encrypted while having been boot from slot A, then wiping data while in slot A results in data loss. By extension, rebooting into slot B and then wiping data allows slot B to now hold the encryption key. I'm sure this theory has got some errors, but it's the best I can come up with having no intrinsic knowledge on the topic.

2. Are there any means of mitigating data loss should the phone become encrypted? I.e. If possible, can I back up data (minus /data/media) and then restore that when I can't get access to /data/media?

With regards to question #1, I developed my "suspicion" after lossing ambition to test it. When I get my ambition back to fight this issue, I'll try again. I'm just getting sick of transfering 25+ gigs of data via adb every time the data gets encrypted and I can't get it decrypted. :rolleyes:
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
You're not that far off, actually. And while I'm no developer I suspect that Encryption kicks in when

a). You flash stock OOS. No matter what ROM you are on, when you flash OOS it's possible you can get encrypted. I'm not sure about this but if a developer could confirm that'd be great. This one time, I flashed OOS Stable while on Beta and it Encrypted my Storage. So I had to retransfer with a computer to flash it the required two times. So basically avoid flashing OOS when on a Custom ROM. Even when switching ROMs.

b). Just as you said, when you Wipe Data within TWRP and then Reboot to TWRP it also Encrypts the Device. So I usually Wipe Data after flashing ROM & Gapps. Otherwise if you Wipe Data after flashing ROM it will Encrypt you.

And to answer that last Question the app I personally use is called Swift Backup. It's an amazing app and although it costs $5.49 it can Backup Apps and Data. It can also backup the Files in Android/obb. Give it a go.
[OnePlus 6T  Questions & Answers] notorious.dds:
I've been fiddling around with OOS and The Pixel Experience (aka TPE) ROM. I've yet to need to flash OOS in order to loose my ability to decrypt. Flashing TPE screws everything up quite nicely as well. That said, I have gotten into the situation where TWRP (booted from either slot) has got everything encrypted. However, in one case, I was able to get the data back by recreating the boot_a partition as it existed before I wiped data. I think there may be something to be learned here. However, subsequent attempts to use this method have not been successful. In other words, I'm not sure what I actually learned.

I'm still using Titanium Backup (paid version as well). It works quite well and I'm happy with it. That said, it's still a much bigger pain in the butt to restore vs performing a nandroid restore of the data. It's apples and oranges though. In order for the nandroid to provide any real value, you pretty much have to do right before need it... unless you never do anything on your phone. It also only works with the ROM from which it was created... obviously. Since my current nandroid backup of /data is > 22 gb, its fairly cumbersome.
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
I dunno if it will work but when you get Encrypted try booting the TWRP image. Maybe that'll work.
[OnePlus 6T  Questions & Answers] mlock420:
Doesn't this problem occur with backups and restore from twrp as well?.... This A/B stuff I'm not used to but I'll keep reading and hopefully something in my brain will kick in lol...
[OnePlus 6T  Questions & Answers] notorious.dds:
Yeah, that I defintitely tried. No dice. However, I just backed up everthing and I'm about to start blowing the thing up with ROM flashes. Consider it a stress test. I'll report back.
[OnePlus 6T  Questions & Answers] notorious.dds:
What I've got so far...

Coming from OOS 9.0.14 running on slot B with a lock screen pattern enabled, I boot into TWRP on slot B.

I then flashed The Pixel Experiance ROM via it's .zip file. (The flash is then applied to slot A because it goes to the inactive slot).

Flashed the TWRP install .zip

Changed active slot to A

Reboot to recovery (aka TWRP) ... now in slot A.

wiped data (minus storage)

Flashed magisk

Reboot system

This got me into the new ROM with data intact. However, when rebooting to recovery (still slot A), it would ask for a pattern but yet wouldn't accept the pattern to decrypt. Rebooting back into Pixel Experience the data was decrypted. So, even the data would decrypt when booted into system, I could no longer get to the data from within TWRP. I then changed the lock pattern from within Pixel Experience and reboot to TWRP, it still couldn't decrypt the data. Rebooting back to system succeeded in that it actually boot, but I could no longer unlock the phone (stuck on "phone is starting"). My presumption at this point was that Pixel Experience could no longer decrypt the data.

I then:

Reboot to TWRP (slot A still)

Flashed OOS

Flashed TWRP

Set active slot to B

Reboot to recovery (aka TWRP)

wiped data (minus storage)

reboot to system

At this point OOS failed to boot and I was returned to TWRP. Data was still not able to be decrypted. I then did a factory reset plus wiped storage (aka data, dalvik, and internal storage) and tried to boot to system... still failed and sent me back to TWRP. This time, although data was empty, it was decrypted. I tried to reboot system again. It failed again and sent me back to TWRP.

So, at this point , I've wiped data and internal storage but I cannot get stock OOS to boot. So, I reboot to bootloader and executed:

fastboot -w

My understanding is that this should do the same this as performing a factory reset from within TWRP. However, rebooting to system succeeded this time.

So, the new questions are:

1. How is it that I can decrypt data when booted into Pixel Experience on slot A, but I cannot decrypt the data via TWRP?

2. If I removed the lock screen pattern from OOS before flashing PixelExperience, would I have been able to decrypt the data in both the ROM and within TWRP?

3. Why is factory resetting via fastboot effective when doing so in TWRP is not?
[OnePlus 6T  Questions & Answers] Deleted member 8892904:
Well starting from the way you flashed the ROM, the rule of thumb is that you NEVER manually change slots. Now since you are on stock follow the instructions I posted earlier to flash PE or any other ROM for that matter. I think when you manually set the slot it somehow messed up Decryption. Next, after flashing OOS from TWRP when you are on a Custom ROM, you must always Format Data. The command you ran via Fastboot (fastboot -w) does just that.

So I just flashed Bootleggers from Stock OpenBeta 11. These are the steps I followed. I was successfully able to flash and was able to keep my Data intact. These are the steps I followed.

Starting from OpenBeta 11 I flashed ROM (Bootleggers) and then TWRP Installer. Then go to Reboot and Select Recovery. Once in Recovery, again flash ROM and TWRP Installer. Once done, reboot to Recovery. Flash Gapps and then go to Wipe and do a Swipe to Fa Tory Reset. This will Delete all your Data except Internal Storage. This is a necessary step when flashing a ROM. Once done, reboot to System. After this I was able to boot up Successfully with my Internal Storage as it was before flashing. After that I restored my backup. Everything is working and I can enter and Decrypt TWRP without error.
[OnePlus 6T  Questions & Answers] g_oral:
This thread should be pined as a guide because instalation notes in ROM threads are so basic.