yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Questions & Answers] blunden:
Pixel phones have never had particularly exciting hardware, especially if you consider how late in the year it launches. Once again, it seems like it will have a slightly dated look with semi-large bezels for a flagship. Their only redeeming quality is the software and the camera (which we know is also mostly about awesome software).
[OnePlus 7 Pro Questions & Answers] Cowbell_Guy:
Since the leaked specs of that just came out... What do you guys think? Would anyone consider that phone over this? I'm looking to get a new phone in next few months just trying to figure out options for a Verizon unlocked bootloader
[OnePlus 7 Pro Questions & Answers] ram4ufriends:
Pixel might not beat OnePlus 7 Pro in terms of smoothness and speed.. but camera is a different story.. I have 7 Pro and planning to buy Pixel 4.. if the performance degradation is really noticeable, I will return Pixel 4 and keep OnePlus 7 Pro
[OnePlus 7 Pro Questions & Answers] SlyUK:
I think Pixel 4/4XL will be far superior to OnePlus 7 Pro in the camera department only at a guess.
[OnePlus 7 Pro Questions & Answers] Cowbell_Guy:
agreed, I think Camera is the one area that pixel is always king.

although that aside, I was disappointed to see that it is only rumored to have six gig of RAM. I can't really see any of the other specs being better than what we currently have. Honestly I'm debating between the 7 plus, before XL, or the next one plus. All I really care about is performance and speed. I'm not a huge photographer
[OnePlus 7 Pro Questions & Answers] SlyUK:
If thats the case then OnePlus 7 Pro is definitely the phone to get.
[OnePlus 7 Pro Questions & Answers] GUGUITOMTG4:
Don't forget that by when Pixel 4 releases, Oneplus will have a successor to this phone a month later
[OnePlus 7 Pro Questions & Answers] Zorachus:
Big Nexus / Pixel fan here, having owned almost all Nexus phones, and the Pixel 2 XL and now the 3 XL, and only owned the original OnePlus One, but I have to say, that beast had a long life, with ROM's it performed very well for several years, a good 3+ years the OPO was still fast and smooth. But the stock Android experience doesn't seems as cool as it used to, seems a little laggy sometimes, or not as warp speed smooth.

Whereas Oxygen OS is super fast, extreme smooth, and has extra tweaks and more customization baked in. OnePlus phones is sort of like a Pixel that's running a custom ROM and customer tweaked kernel.

So this is how I see it playing out;

- Pixel 4 XL wins in the camera department, and of course first for updates direct from Google. And the little things like wireless charging and official IP68 rating.

- OnePlus 7 Pro wins other areas; smoother faster OS experience. Maybe better display screen. Faster charging. More customization baked in.
[OnePlus 7 Pro Questions & Answers] Cowbell_Guy:
Good point. At the very least, night as well wait until the 4 comes out. Will force down prices of the 7, and the 8 will hopefully be released soon after

Which starts another argument- why would someone ever buy a phone with an old outdated processor when a new one was coming out a few months later
[OnePlus 7 Pro Questions & Answers] SlyUK:
You buy a phone when you need it, simple as that. Something new is always around the corner, but if you wait for that you will be waiting forever.
[OnePlus 7 Pro Questions & Answers] blunden:
Nope. Not even a little. The Pixel continues looking dated and boring and almost certainly won't feel as smooth.
[OnePlus 7 Pro Questions & Answers] Cowbell_Guy:
Truth. I guess I'll just have to decide if I want 7 or 7T
[Huawei P10 Questions & Answers] bigshowjh:
I see feature advisor in my status bar after a reboot. Just wondering what it was. I have force stopped it upon reboots. I see I can remove notifications for it. But I think I just want to delete it, but before removing it I wanted to make sure what the ramifications are in doing so.
[Huawei P10 Questions & Answers] bigshowjh:
Removed it no issues
[Samsung Galaxy Note 9 Questions & Answers] playerone_:
I just got a Note 9 on Amazon, I realize a small risk associated with that. The phone was sold as a factory unlocked device. I received it today and I checked it in the settings and the device is confirmed as a SM-N960U1 which is what it should be. However, when I go to register the phone on Samsung's website, I enter the IMEI and it registered as a SM-N960UZKASPR which is an unlocked sprint variant. I am using this phone on AT&T at the moment, but will be transferring to T-Mobile very soon. Am I going to have issues with this as far as bands and networks are concerned, or anything else? I know I am screwed when it comes to wifi calling and volte.
[Samsung Galaxy Note 9 Questions & Answers] qnc:
What I assume happened is that the phone was a sprint model but was unlocked. The previous owner installed the U1 firmware which is the unlocked and unbranded firmware.

All US models are built with the same hardware, radios etc. Compatible with all networks.

You will be able to use it on Tmobile no problem.

You are not screwed if you want tmobile features

If you want tmobile related features wifi calling and the like, you will need to flash the tmobile firmware.
[Vivo Nex Guides, News, & Discussion] erkund:
Anyone else noticing camera issues since update? The stock camera app seems to be desaturating shadows.
[Realme 3 Pro Guides, News, & Discussion] khannz7:
Caution: Data will be encrypted And This process can brick your device. Don't blame me

~ You need to have unlocked bootloader

~ Download any AOSP A/B build

~ Download vbmeta attached below

~ Goto Bootloader, enter

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

~ Flash THIS TWRP

fastboot flash recovery recovery.img

enter into recovery via bootloader, use the volume keys to choose & power button to select.

~ Wipe Dalvik, System, Data & Cache.

~ Extract the .img from downloaded AOSP file *.xz & *adb push *.img /external_sd or whatever directory

~ Locate the extracted file & install it through twrp. Reboot to System.​
[Realme 3 Pro Guides, News, & Discussion] hazam1992:
Hi.... Tried a couple of the GSIs... They work great but fingerprint is missing... Now I want to go back to stock... Do you have stock vbmeta.img?
[Realme 3 Pro Guides, News, & Discussion] khannz7:
Flash this stock os through twrp

https://mega.nz/#!2YU0AaTK!lYVNNHRYJw4jmPcJI8CDLOs-c00nwvt-1DZV7Rlazek

FP is issue

Did VoLTE work? And which Gsis did you flash
[Realme 3 Pro Guides, News, & Discussion] Samdroid18:
Hi, how did you unlocked BL and installed twrp. I heard it's bricking the device after unlock.
[Realme 3 Pro Guides, News, & Discussion] hazam1992:
Thanks bro, you're a life saver.... I flashed Havoc and Descendant OS... they were generally buttery smooth and incredibly snappy, but since both lacked fingerprint scanner, I tried switching back... phone is still in a bootloop... about to flash the rom you linked.... fingers crossed...
[Realme 3 Pro Guides, News, & Discussion] stryker09:
Did it work?
[Realme 3 Pro Guides, News, & Discussion] hazam1992:
Like a charm! Thanks again...
[Realme 3 Pro Guides, News, & Discussion] zanjanu:
Can I flash magisk/supersu for root with this ?

Try flash with twrp/boot patched but I got brick
[Realme 3 Pro Guides, News, & Discussion] matrix0807:
On havoc and descendant os, is the camera quality still good? Photo and video?

If FP still issue, how about unlock with face unlock? Is that work well?

Thankyou
[Realme 3 Pro Guides, News, & Discussion] ZainBilq:
On havoc, camera is not stable, it will not take photos if there is not external sd card. Otherwise, camera quality is just okay..

Face unlock, I did not try...
[Android Q&A, Help & Troubleshooting] VampireSquid:
UPDATE: Miraculously got through all steps of the Setup Wizard after all :) It's apparently not broken, but just VERY unstable... ;) For now, it's possible to use 'adb reboot recovery' again :)

I don't think I can delete my post here though.

- - - - - - - - -

Hi!

I've got a problem trying to install Lineage:

(1) After installation, it turns out that the Google Setup Assistant, which pops up first after booting, keeps crashing, so I don't get through the setup procedure.

(2) I cannot enter the recovery mode any more! Before, the phone used to load the TWRP menu when pressing Power + Volume Up + Home. But now, it's just the wakeup screen repeating again and again...

I feel stuck: I cannot reinstall any ROM without being able to enter the recovery mode. Further, it looks to me as if it's impossible to connect the phone to the computer as long as I cannot even pass through the Setup Assistant.

My tries: Reinstalling TWRP with Heimdall. There were no error messages, but it did not help.

Phone: Samsung Galaxy S3 Mini (GT-I8190)

OS: Lineage 14.1 Unofficial

Recovery: TWRP 3.2.2.

How can I get out?
[Android Q&A, Help & Troubleshooting] GarlicBreadFox:
Hello,

What would be the 2019 cleanest way to uninstall a system app?

My case: Flashed xiaomi EU (clean) ROM for a Redmi and it didn't come with youtube preinstalled. I ran to install it but now I noticed it cannot be uninstalled normally, only remove system updates (this one is funny because I assume removing system updates leaves a base version but not sure what a base version of youtube would be for a ROM that didn't have it in the first place, I guess youtube base version would be related to playstore version installed).

So I've seen uninstall procedures via ADB, titaniumbackup (don't own it yet) and other playstore apps. But not sure what would be the most recommended method nowadays, on a rooted phone (magisk) if that makes any difference.

Thanks for your time
[General Questions and Answers] STDupont:
Gentlemen/ Ladies,

Any Pro here? Can anyone tell me step-by-step...NO-BS...how to back-up my android OS + data, here , please !?

I ran into some difficulties...I am trying to fully backup my Nexus 5 at this stage.

I was told I need a few things, 15-seconds ADB installer, SDK , TWP-3.2.1-1

When I typed in DOS, in my computer i got a response:

"adb" is not recognized as in internal or external command operable program or batch file

I am having so much problems with that SDK Android thing, ...Someone here at this forum gave me this :

https://xdaforums.com/google-nexus-5/general/guide-nexus-5-how-to-unlock-bootloader-t2507905

From the link-ADB and Fastboot Installation

1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks [MENTION=962867]El Daddy[/MENTION])

Link removed since it expired

2. Extract the zip and place the android-sdk-windows folder on your desktop.

**If you chose to download the slimmed sdk skip to step 5**

3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):

- Tools > Android SDK Tools, Android SDK Platform-tools

- Extras > Android Support Library, Google USB Driver

4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.

5. To confirm that it is indeed working, open a command prompt window and enter the following commands:

Code:

cd Desktop/android-sdk-windows/platform-tools

adb version

If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are ....

What are those SDK Tools/ & Android SDK platform-tools,....? How to get it working for adb error in DOS?

True instructions step by step please.....the above instructions, are no where near from what I saw on screen !

Thank you,
[General Questions and Answers] Droidriven:
Using TWRP custom recovery is the best option.

I have a N5 also.

Install adb/fastboot on PC, download TWRP for your device in .img format, rename the TWRP file to "recovery.img", place the recovery.img in your fastboot folder on PC, boot your device into fastboot mode, connect your device to PC, open a cmd terminal on PC.

Then type:

fastboot devices

Then press enter, it should return a serial number, then type:

fastboot flash recovery recovery.img

Then press enter, it should flash the recovery, then type:

adb reboot recovery

Then press enter, it should reboot device into TWRP. Then select the "Backup" option in TWRP, on the next screen, select the partitions you want to backup, then swipe the slider, then you'll have a backup of everything you want to backup. To restore the backup, boot into TWRP and select "Restore" then find your backup and restore it.

Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage, to ensure that the backup does not get lost, corrupted or wiped accidentally, I recommend storing a copy of the backup on PC or some other external storage(flash drive, external hard drive, etc..).
[General Questions and Answers] STDupont:
Hello,

Thank you so much for yr reply, I truly appreciated, I MEAN IT !

Just a few things for confirmation:

-"place the recovery.img in your fastboot folder on PC"..........I take it after I download &installation TWRP on my PC, there will be a fastboot folder on my PC, right?

-"Side note: after creating the nandroid backup in TWRP, it will store the backup on internal storage"......

Thank you very much !
[General Questions and Answers] Droidriven:
You will not be installing TWRP on your PC, you will only be downloading the TWRP recovery.img and storing it in your fastboot folder. Renaming the file to "recovery.img" as well as storing it in your fastboot is not "required", but it does simplify things to make it easier. Otherwise, when you type the fastboot command to flash the recovery, you would have to use the specific file name that you downloaded and the exact path to where it is stored on your PC. Renaming the file and storing it in your fastboot folder simplifies the command to

fastboot flash recovery recovery.img

Instead of

fastboot flash recovery (specific name of the file you downloaded)(exact path to the file on your PC)

Whereas renaming to recovery.img and storing in your fastboot folder removes the need to be specific and flashes recovery.img from fastboot folder by default without having to be specific.

When you install adb/fastboot on PC, you will have a fastboot folder. You can get the installer from the link below.

https://androidmtk.com/download-15-seconds-adb-installer

As for the part about TWRP storing the backup on internal. What I mean is, the N5 doesn't have an sdcard slot for external sdcard, this means that TWRP will store the backup that it creates on your internal storage by default, you'll find the backup in your TWRP folder on your phone. Copy it from your TWRP folder on your device and move it to your PC or some other storage location other than on your phone.

Storing backups on internal can be risky, sometimes your device can get corrupted or can even accidentally get wiped for no apparent reason, if either of these issues happens, the data that you had stored on internal will not be accessible, if this happens, you may not be able to restore that backup. To ensure that you don't screw yourself out of being able to use the backup, you can store it on a flashdrive. If your copy on the phone gets corrupted or if your phone gets soft bricked or accidentally wiped, you won't be able use the copy that is on your internal storage in your device. If that happens, you will have to connect the flashdrive to your phone via OTG cable, then you can boot into TWRP and use the restore option, once you have the restore feature open, you can choose which storage you restore from, choose the OTG flashdrive and you can restore the copy that is on the flashdrive instead of the copy that is stored on your phone.

Did you understand that this time?

I also recommend backing up your personal data(such as contacts and photos and such using some other means other than TWRP), then, after flashing your custom ROM, you can restore that personal data back to your phone so that you have it available in your new ROM. You can back your contacts up to Google and your photos to Google Photos or just copy the photos to PC using Windows file manager. Other types of data must be backed up by other means depending on what type of data is in question, such as using adb to backup your apps and app data then using adb to restore your apps and app data.
[General Questions and Answers] STDupont:
Hello,

Yes, I understand and know a few things about Windows OS, but when it comes to Android OS, bootloader, fast boot, TWRP...I am a 101-stupid ! But yes, what you are telling me are very similar to Windows OS backup onto external device, which I need....I am going to do tonight,....if I run into any difficulties, sure will keep you informed,....

Once again, I truly appreciated your help, I MEAN IT !
[General Questions and Answers] STDupont:
Hello,

I am getting the same thing ! I copied that TWRP-3.2-1 Hammerhead, and renamed the copy as you said as recovery.img, and moved it to 15 second ADB installer folder.

Started my phone as you said, also in developer's mode, with USB scanning for device error. Then I tried in Recovery mode, same thing.

Any suggestion ? Was it something I did wrong ?? Million thanks ,
[General Questions and Answers] Droidriven:
Did you actually install adb as this thread says to do?

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

Once you actually have it installed, open Windows file manager and select your C drive, then you'll see the adb folder instead of a fastboot folder(this folder will have the adb and fastboot .exe files), place the recovery.img in that folder.

On your device, go to system settings>developer options and make sure you have the USB debugging option enabled. If you don't have the developer options setting, go to system settings>about phone, scroll down until you see "build number", tap the build number 10 times quickly until you see a message telling you that you have enabled developer options, then go to developer options and enable USB debugging.

Then open the Windows cmd terminal, boot your device into fastboot mode, connect device to PC, open a Windows cmd terminal, type the command:

fastboot devices

Press enter, if it returns the serial number, you're connected. Then continue with the command:

fastboot flash recovery recovery.img

Then press enter, it should flash the recovery, then type the command:

adb reboot recovery

Press enter and it should reboot the device into TWRP. Then continue on with using the Backup option in TWRP to create your n android backup.

There are plenty of threads here at XDA that completely explain how to flash TWRP via fastboot and plenty of threads here that describe how to create backups using TWRP. Try reading some of those threads and you'll understand it much better and it will probably answer any other questions that you have.

Just do a Google search for:

"How to flash TWRP via fastboot Nexus 5"

Use those instructions.

Then do a Google search for:

"How to create android backup via TWRP"

Those two searches should tell you what you need to know.

If you can't understand these simple instructions that I've given as simple as I can make them or if you can't understand the information that you find with these two searches that I've described, then, you should forget about flashing any kind of ROMs on your device because you'll probably brick your device due to your lack of understanding.

I don't know why you haven't already tried Google searching about this process to understand it. Don't be lazy, do your research.

---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------

One more thing that I forgot to add, you have to unlock your bootloader before you can flash TWRP on the device. To do this, verify that you have enabled the "OEM unlock" option in developer options, then open a Windows cmd terminal and type

fastboot oem unlock

Press enter, it will unlock bootloader but it will also wipe a personal data when you unlock the bootloader so make sure you have your important personal stuff backed up before you unlock the bootloader.

Then you can continue with flashing TWRP.
[General Questions and Answers] STDupont:
Hello,

I have it installed. Actaully I was encountering errors but don't want to waste yr time here either.

I will take a close look of the links you provided. I understood what you said, it makes perfect sense. And I know a lot about Windows OS and other stuff, just NOT Android OS and all these.

I also mentioned the developer's mode was ON and USB error detecting was ON, as well. And you are RIGHT ON, ....

Thanks again,

It just when it comes to execution,
[General Questions and Answers] Droidriven:
It takes some getting used to, but with proper research based on your device model number and the thing you want to do on that model, it is easily overcome.
[Sony Xperia 1 Guides, News, & Discussion] iArvee:
I did a wm size in adb to check what the default resolution is, and it seems to be in 1080p (21:9 ratio).

This would explain why the battery life is still great. Despite being in 1080p, the display is still very crisp. Crispier than my XZ3. :D

If I did this wrong, please do correct me!
[Sony Xperia 1 Guides, News, & Discussion] Mackay53:
They were never going to make the phone 4K all the time, wouldn't make sense
[Sony Xperia 1 Guides, News, & Discussion] Sensination:
Great news! Really happy about that :)
[Sony Xperia 1 Guides, News, & Discussion] riz157:
can you change resolution to 4k at all times?
[Sony Xperia 1 Guides, News, & Discussion] Mackay53:
Yes through ADB but why would you want to do that? Would be a bit pointless
[Sony Xperia 1 Guides, News, & Discussion] masteriori:
Do you have the command to enable 4K at all times? Also, do we need to root? It would be good to try I guess.

I wonder if it's possible to enable Super-vivid mode on Sony Xperia 1?

Thanks
[Sony Xperia 1 Guides, News, & Discussion] Mackay53:
Can't remember but it will be in the XZ premium thread somewhere.

You wont notice a difference and the software already knows when 4k is needed
[Sony Xperia 1 Guides, News, & Discussion] theskig:
That's fake. You can do it with any phone.

I read the gsmarena review and there's written the screen is always in 4K. I'm wondering where they get this info.
[Sony Xperia 1 Guides, News, & Discussion] Allesa:
When I screenshot in any app including launcher, it results in 1644x3840 tho.. Previous 4k sony phones produced fullhd images if you ss on launcher

So which info should we refer to? Wmsize on adb or screenshot pixel size?
[Sony Xperia 1 Guides, News, & Discussion] theskig:
No.

My XZ Premium screenshots are 2160x3840 png files, and the same for my older Z5 Premium.

That adb system is so suggested from users that many people believe in it, but the true reality was explained by a developer in this forum in "Z5p days". The proof is that you can do that with any phone.

It also explains that 4K screen is completely useless because nobody can spot the difference from fullHD (and I say this while it's since 3 years I'm only using 4K phones)
[Sony Xperia 1 Guides, News, & Discussion] jateruy:
Using wm size on Xperia 1 results in screen touch area only works in partial, equaling to the scaled screen size, but the text is simply crispier. Anyone knows how to fix the touch area problem?
[Sony Xperia 1 Guides, News, & Discussion] yumcimil:
Do Kindle/Moon Reader etc.. run in 4k or 1080p mode?
[Sony Xperia 1 Guides, News, & Discussion] masteriori:
Did you actually change the resolution to 1644x3840? If so, are you suggesting that we can't have it at 4K all the time?
[Sony Xperia 1 Guides, News, & Discussion] jateruy:
I did exactly ./wm size 1644x3840 and yes...unfortunately that is the case where currently we cannot have the phone at 4K all time at this moment.

I'm guessing that Sony did something to the UI touch overlay in order for the side sense detection to work precisely.