yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] shadowcore:
Dont know if they are. The last iPhone i owned was the 4S.

According to this http://appleinsider.com/articles/16...will-lead-to-more-faithful-color-reproduction

They arent "color accurate" at least since the iphone 7. I could assume that the 6 and 6s and previous phones to have sRGB range, but what percentage? I couldnt tell you.

Wide gamut or "wide colors" means that they go over 100% of sRGB range, meaning neon colors.
[Google Pixel 2 XL Guides, News, & Discussion] Nitemare3219:
You don't seem to know what you're talking about. iPhone 7 and above are some of the most color accurate phones in existence, with the X being the absolute best. They are calibrated with sRGB and DCI-P3 color profiles and can switch between the two based on how the content is coded. It's called color space management, and just because a display is capable of going above sRGB doesn't mean it's inaccurate... sRGB is a terribly limited space and doesn't nearly represent what human vision is capable of.
[Google Pixel 2 XL Guides, News, & Discussion] shadowcore:
Unless you can provide sources that back your claims, you are in the wrong place to spread iphone propaganda.

You cannot calibrate a screen based on two color standards.

And the subject is color accuracy, not "what the human eye is capable".

And its less than plausible, that apple, the kings of BS, are going to invest time and money to properly calibrate millions of devices.

That just doesnt work. If you are triggered by this, go to mac forums.
[Google Pixel 2 XL Guides, News, & Discussion] Nitemare3219:
You clearly need to do some research. You can have more than one color space on a device and switch between color spaces as necessary. DisplayMate would be a good place to start...
[Google Pixel 2 XL Guides, News, & Discussion] mlin:
My understanding is boosted provides a more significant change than vivid. Something like %20 vs %10.
[Google Pixel 2 XL Guides, News, & Discussion] SupaDupaFly24:
Ok thats awesome thanks!

Too bad this update is taking forever to come ?
[Google Pixel 2 XL Guides, News, & Discussion] LLStarks:
I compared my Pixel 2 XL against a Galaxy S3, Galaxy S6, and a OnePlus One. The phone does not hold up well.

Max brightness. Adaptive brightness disabled. Night light disabled. Let's see how well OLED has evolved. OPO is a control, I guess.

Brightness: The P2XL is bright. No complaints here. All 4 compete well.

Colors: This was depressing. The screen is blue. Very blue. Even face on and sitting still. I've dealt with Pentile before, but the blue shift is just jarring. Natural (sRGB) is washed out on the P2XL while Basic (sRGB) on the GS6 still has that pop look to it. Boosted looks identical to Natural. GS6 adaptive color mode is very balanced. The OPO has one color mode, stock. Looks far better than what you'd expect for how cheap the phone was. Never tried messing around with kcal kernels. GS3 is super saturated but holds up amazingly. P2XL saturated mode looks like a rushed afterthought. Not enough care has gone into this mode and it doesn't satisfy the criticisms of the default sRGB. It's extremely red and oversaturated. There's no way to get a decent white on this screen. We've been spoiled by saturated screens but this is absurd. The red of the Chrome icon and my background are not the same shade of red. Night light, lowest intensity, doesn't help any of the modes much.

Viewing angles: P2XL wins. GS6 struggles as it approaches 180 degrees.

Burn-in: Using a 50% gray background and hiding the navbar, I don't see any on the P2XL. I've only had it for a few days, but this is good so far. GS3 fails. The ICS/JB launch icon is etched into the screen despite somehow running Nougat.

Overall: The P2XL screen is very grainy. It's distracting. The colors are just wacky. I feel like I lost the lottery on a phone manufactured on 10/24. It's as if nothing has been addressed more than a month later.
[Google Pixel 2 XL Guides, News, & Discussion] SquireSCA:
I downgraded from 8.1 Dev channel and I can't seem to get the 8.0 update...

My screen looks fine, the mild blue at angles doesn't bother me... My issues are the BlueTooth issues of voice commands not working, crackling and stuttering, and when I run the burn in test, I see just the faintest hint of it. Granted, you don't really see it in normal use, but it is there and will probably get worse. Unfortunately I am outside of the 15 day return window, so I will likely have to go buy a Samsung or iPhone and then just try to sell this one and get some of my money back, although with the perception of this phone being so trouble prone, I will likely have a hard time selling it.

Shame, Google really could have had a winner here... I was with them through the "screen issues" as mine didn't seem to have any, but if they can't even get BlueTooth working properly, then I have no use for the phone. I need it for Android Auto and especially when I ride. My helmet has a BT system installed and I need that for music, phone calls, turn by turn navigation and it currently doesn't do any of those well, if at all...
[Google Pixel 2 XL Guides, News, & Discussion] Nephilim:
Well first, the Bluetooth issue is fixed in 8.1, I'm running the developer preview. Second the burn-in issue is not present on all devices and there are plenty of ways to keep it from happening fast (I use Navbar Apps from Play Store). Third, burn-in will happen over time no matter what on any OLED display you get regardless of the brand. Google not only gave an option for setting an over-saturated cartoony color mode for the people crying but they added fading nav buttons to decrease burn-in also. The big thing though, is 2 year warranty. You have a problem with your device, just have a new one sent to you. They'll do it overnight and it'll take you a whole 10 minutes to transfer everything to the new phone.

Seriously, you bought a phone when it launched and are complaining about issues, that's ridiculous. If you can't handle bugs you shouldn't by brand new devices right away. Give Google time to release necessary updates.
[Google Pixel 2 XL Guides, News, & Discussion] SquireSCA:
I had the BT issue on 8.1 which is why I downgraded to 8.0 in an effort to see if I could get the latest OTA and fix it...

Second, I don't need to be patient. This is a flagship, premium price phone, not some $399 beta phone program. It's not ridiculous to expect a company like Google to get their **** together. But they wanted to beat the iPhone X to the punch this Xmas season, so they pushed it out the door with several glaring bugs.

Not to worry, they just issued me a refund and I went and got an 8+ 256GB for the same price as the amount that Google is refunding me for the P2XL 128GB... so I didn't lose a dime on the swap.

Their customer service, top notch! I just don't want to pay a grand to be a beta tester and spend the next couple months helping them fix their quality control issues in order to get the phone working the way it was supposed to from the beginning.

That's not ridiculous. Making excuses is.

I was willing to live with the slight blue tint and the risk of burn in, but I use BT every day for calls, NAV, music, etc... And the phone has the worst BT quality of any of the 20+ phones I have ever owned...
[Google Pixel 2 XL Guides, News, & Discussion] Nephilim:
Welcome to the 1%. The Bluetooth issue is completely non existent for myself and many others with 8.1. it's been documented. I guess getting a lemon means all the devices are that way. Have fun with your bloatware and oversaturated colors along with a device that also contains blue shift and will inevitably get burn-in.
[Google Pixel 2 XL Guides, News, & Discussion] SquireSCA:
I just read no less than 7 articles on the bt issue yesterday, kid. I have the issue, and my screen was beginning to burn in after 17 days. I decided to cut my losses.

I didn’t say everyone has it so there is no need to take it persona;pay and get all butt hurt. Grow up.
[Google Pixel 2 XL Guides, News, & Discussion] arcanexvi:
BT is definitely an issue currently but I do expect it to be fixed with updates. Whoever is in charge of BT over @ Google blows. Every new phone they launch has issues with it til several patches in. My Pixel XL had similar issues at the start.
[Google Pixel 2 XL Guides, News, & Discussion] SquireSCA:
Bt is. Core feature, to have it not working is like calls. Or wife not working
[Google Pixel 2 XL Guides, News, & Discussion] Nephilim:
As I've already said. Bluetooth is an issue for SOME people not everyone and I haven't heard of a single person that's using it on 8.1 having issues outside this thread. It's incredibly annoying when people go off on a ragefest about something as if it's a universal issue just because they're experiencing it. Also, I'll say it again, if you can't handle issues don't buy new electronics on day one. **** happens and you cannot blame Google for not testing enough because a small team is not going to be able to cover every single variable that the millions of users encounter on a day to day basis as well as you cannot predict every single device is going to be 100% perfect, that's impossible for any type of tech.
[Google Pixel 2 XL Guides, News, & Discussion] skip24ftlb:
I've yet to receive my handset being a UK consumer. But if bt isn't working properly, then it's a bigger deal here than it might be for the USA pixel owners.

We cannot get away with driving with a phone clamped to our ear. Its a 6 point penalty, a big fine, and insurance costs go through the roof.

Ultimately Google is the home of android. And if you buy a Google handset, then it goes without saying, it should be [emoji817]% bug free.

Its that simple..

I don't mind beta testing add'ons like lens, but core stuff should work.
[Google Pixel 2 XL Guides, News, & Discussion] DaveP2611:
Exactly this, I'm shifting over to the P2XL from a OP5 due to the camera on that phone sucking pretty badly, but the moment you raise an issue the defence force come out and tell me i'm imagining things. It's an issue that I have and an issue that I can solve by purchasing a new phone.
[Google Pixel 2 XL Guides, News, & Discussion] Lawlrus:
You updated to the Nov 8.0 build? I was told there were a bunch of bt fixes pushed with that build. I'm tired of waiting for the ota so I think tomorrow night I'm going to sideload the ota because my phone won't connect to my 2017 vehicle worth a damn. Works on my TV's sound bar, and my bt ear buds I just got.

The Nov update is the newest for the device, so if any would have working bt it would be it.
[Google Pixel 2 XL Guides, News, & Discussion] SquireSCA:
Except that the only one going off on a ragefest, is you. I simply said that I was willing to live with the slight blue shift and stuff, but when I saw burn in happening at just over 2 weeks, and that the BT audio and crap is awful and a deal breaker, you seem more upset about it than I was. I simply called Google and arranged to get my money back and went and bought a new iPhone. Problem solved.

Stop being that over the top drama queen fanboy, where if someone points out the issues with "your team", you get your panties in a twist...
[Google Pixel 2 XL Guides, News, & Discussion] ewizzle78:
Finally got my OTA! took forever. unlocked phone on tmobile. Saturated mode def looks more overblown like a Samsung screen. Not sure I like it or not yet. I didn't mind the colors in the vivid mode before the update. This has more pop! Hopefully people will shut the hell up about the color issue now.
[Google Pixel 2 XL Guides, News, & Discussion] draiken78:
They need a setting between boosted and saturated. Saturated seems like they just cranked the red up to a rediculous level.
[Google Pixel 2 XL Guides, News, & Discussion] Nephilim:
I rolled back to 8.0 just to take a look at saturated mode, yeah, I hate it. I went back to 8.1 beta and I'll stick with vivid/boosted. I prefer accurate colors over bullsh*t display model television looking colors.

Also, it may be just me but the replacement 2 XL I got from Google due to burn-in on my day one model has a much better display. I'm not seeing any blue shift, the colors are still natural but they stand out more as if there's better contrast. I tried the graininess test at low brightness and that's gone too. Could it be Google had LG revise their display panels due to all the heat they got on launch? I don't know. I'm just stating what I see personally.

I'd post a screenshot but that would serve zero relevance since you'd be viewing it on your screen, not mine lol.
[Huawei P8 Questions & Answers] Overloke:
Hi all,

I recently flashed CM13 onto my GRA-UL00 Huawei P8. Everything went fine until I noticed that there was no sound. I've spent about seven hours looking for a fix, and I've come up with nothing. I've noticed that I have no mixer_paths.xml file, and when I attempt to put in a new one, there is still no sound. I've tried a clean CM13 install, wiping everything and starting over, the latest Lineage release for Huawei P8, as well as reverting the ROM and Recovery to stock and running a clean install then. Nothing has worked, and my phone simply has no sound.

There is one other similar thread at the moment, started by Rome7643, who had one reply, from him, which was "Never mind, fixed it", with no explanation as to how or what he did.

Does anyone have any ideas as to what could've caused this, and more importantly, how to rectify it?

Thanks.

EDIT: I also JUST noticed that when the sound is enabled (that is, the phone isn't in Vibrate or Silent mode), the phone lags - it takes several seconds for it to register presses on the keypad, the keyboard barely works, sometimes it doesn't register my touch on apps. But if I put the sound back down to Vibrate or Silent, it goes back to work like normal.
[Huawei P8 Questions & Answers] Overloke:
For what it's worth, I messaged Rome7643 privately and asked him what he did to fix the issue. I'll post the fix here for posterity, in case someone else has this issue, Googles it, and runs across this thread as well. I want to give all credit for this fix to Rome, as he was the one who figured it out, not me.

Basically, the fix is to download a stock image (so the update.app file), and use the Huawei Update Extractor tool to extract the Image, Recovery, Cust and Boot .img files. Using Fastboot, flash them as you normally would, restart, and start the phone as normal. At this point, the sound is still not back. You now need to put the full update.app file into a folder called dload in the root of an SD card. Then, turn the phone off, and boot into the automatic Huawei updater by holding BOTH the Volume Up and Down buttons as you power on the phone. The phone should automatically begin to do a full, clean, fresh update from the update.app.

Rome said that he had to do this several times before the sound came back, but for me, the sound returned on the first attempt. I then reflashed the Lineage 13 beta build, and I had sound, and I flashed the Cyanogenmod 13 build, and I also retained sound. There is still an issue with the signal indicator, but that's related to the ROMs themselves, and unrelated to the sound issue.
[P3300, MDA Compact III ROM Development] patterns:
hi guys does anyone know what is the maximum size sd card i can get for the artemis? i got t mobile mda compact 3.

if there is a restriction is there also a way to increase the size - i.e. with a cab file etc?

thanks
[P3300, MDA Compact III ROM Development] fubofo:
I think 8GB with SDHC fix installed
[Galaxy Note5 Q&A, Help & Troubleshooting] omegfa:
Hi

I did back to unroot

Shealth not work ... and many problems

I checked dev posts and no new rom

Without any note 8 port rom

I don't know what to do ....

Back to root and flash which rom? ( i need stable and without battery drain )

OR

Stay unroot with bugs + security denied like shealth , ...

Please help me ( suggest stable rom or with kernel )

920cd _ note 5 duos

Sorry for my bad English

Thanks
[Galaxy Note5 Q&A, Help & Troubleshooting] omegfa:
root again, flash MYSTYLEROM

security issues solved(shealth,...) but low-quality camera + without deep sleep
[Galaxy Note5 Q&A, Help & Troubleshooting] sinkoo1979:
flash this rom "N920X ☆☆Full Port Note FE by RadeonMaya v4.0☆☆"

It works like a charm on my note 5 N920S. All Working for me except language download and samsung music player.
[Galaxy Note5 Q&A, Help & Troubleshooting] omegfa:
thanks, I will flash it, I hope it be stable for daily use
[Galaxy Note5 Q&A, Help & Troubleshooting] omegfa:
N920X ☆☆Full Port Note FE by RadeonMaya is great rom

note 7 fe (great port)+AOD+deep sleep + all things work in 920cd +smooth
[Galaxy Note5 Q&A, Help & Troubleshooting] cabbage65:
N920X ☆☆Full Port Note FE by RadeonMaya v4.0☆☆, works with no problems on my 920T, stable, all updated features working and good battery life.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] libtoni:
I have downgraded my phone s6 edge from 7.0 to 6.0.1. I downloaded firmware from the samsung page for the country and the nexwort it was bought for.

I used odin, phone was recognised and the whole process was successful. Odin said PASS!!

After installing the software it restarted and i said " Stopping IU" and stopping "features enhance".

After that restarted and it has been stuck at the logo since.

What do i do nexT?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Rizzed:
Head over to recovery mode and perform a factory reset. Boot-up will take about 10-15 minutes.
[Huawei P9 Questions & Answers] dazehaze:
Hi,

I have RR-N-v5.8.4-20170813-eva-Unofficial installed on my P9.

Sometimes, I need to try other ROMs but I can't and I don't know why, even I erased all data and tried a clean installation. Do you know what's going on?

Here I attached TWRP sceen of my problem.

Is TWRP thinks that my phone is Huawei Honor 8? Because it says my phone is frd.

[IMG="https://xdaforums.com/attachment.php?attachmentid=4325602&stc=1&d=1510049369"]https://xdaforums.com/attachment.php?attachmentid=4325602&stc=1&d=1510049369[/IMG]
[Android Q&A, Help & Troubleshooting] nerbrume:
Hello all,

I have a Zenfone 2 (ze551ML aka Z00A), with TWRP 3.02, with a broken usb port, so I can't connect it to a computer.

I'm trying to upgrade my bootloader, from a Lollipop bootloader to a Marshmallow Bootloader. (in order to upgrade to Lineage 14.1)

To do this, I have some files, which are supposed to be flashed using fastboot. The script is as follow:

fastboot flash splashscreen splashscreen_551.img
fastboot flash token bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
flash recovery TWRP-3.0.3-M3-Z00A.img

Since I can use that, I'l trying to do it from within TWRP, using it's Terminal.

1) The TWRP terminal provides a "flash_image" binary.

I guess I can do :

flash_image splashscreen splashscreen_551.img
flash_image fastboot droidboot_4_21_40_134.img
flash_image recovery TWRP-3.0.3-M3-Z00A.img

Is that correct ?

2) Is there a way to flash the other bin files ?

My TWRP doesn't have any binary like flash_token, flash_ifwi, or flash_dnx.

But maybe I can do flash_image token bom-token_ze551ml_4_21_40_134.bin ? (and so on)

3) The updated TWRP version I'm flashing (3.0.3-M3-Z00A) is supposed to be only compatible with the M bootloader.

Is it safe to only issue the commands listed in 1), or am I at risk of having an "incomplete" bootloader, by not flashing the ".bin" files ?

While I'm pretty sure that the ifwi is only baseband related, I don't know what bom_token and dnx are for.

Thanks for reading !

PS: Apologies is not the right forum to post. I feel like it is more related to TWRP than Zenfone2, but I can move to the Zenfone2 sub-forum if needed.
[Upgrading, Modifying and Unlocking] Blisk1:
Can anyone explain why is good to use custom ROM on new android phones?

As far as I know once you have installed custom rom there is no way going back to original.
[Upgrading, Modifying and Unlocking] Ibuprophen:
Your best bet is to post this question within the following thread.

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

Good Luck!

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Android Apps and Games] amirsuleman:
A new addition to the 100-speed bumps challenge. This is an amazing game on play store.

mod edit - duplicate thread closed

https://xdaforums.com/android/apps-games/100-speed-bumps-challenge-speed-breaker-t3701520
[OnePlus 5 Questions & Answers] bigtreiber:
Hi there,

I'm running OOS 4.5.14 and since one of the latest updates (I can't tell when) I'm no longer able to access the Bluetooth Audio Codec Settings under:

Settings -> Advanced -> Bluetooth Audio Codec (aptX / aptX-HD)

Any ideas what I can do / what went wrong? Bluetooth Audio is working,

Thx, bigtreiber
[OnePlus 5 Questions & Answers] bigtreiber:
Does anybody have any suggestion?
[OnePlus 5 Questions & Answers] Eric214:
Have you tried dirty flashing .14? If yes then I'd wipe everything and flash .14 from completely clean.
[General Questions and Answers] 1edenec:
Hello, everyone.

I have unbricked oneplus 5 and encrypted TWRP backup. How can i properly restore it to my phone? I tried simple restoring, but i had recovery loop. And i was surprised that there is no information how to do it.

What was done:

1) Unlock bootloader

2)TWRP flashed

3) Backup Restored

What i have:

1) Recovery loop

What i need:

1) Your Help.

TY.
[General Questions and Answers] Ibuprophen:
I don't have this device but, the following area of the forum is specific to your device.

https://xdaforums.com/oneplus-5

Your best bet is to post this question within the following Official TWRP thread for your device.

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

There's always the fallback option in the following thread for your question.

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

Good Luck!

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[General Questions and Answers] 1edenec:
Ty for your answer, but I tried to found answer in other threads. Nothing. I know how to restore backup, but nobody told how to restore encrypted backup. Looks like this thread is prohibited by Lord Voldemort:(
[General Questions and Answers] Ibuprophen:
The last thread i had posted was to the help thread for your specific device.

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

I don't have this device and the help thread is where I would go to ask a question if I can't locate another thread for an answer.

I don't have this device but, I do have TWRP and, personally, if I can't restore a backup, then i just delete the backup file and start over again with a fresh installation on the device. It's a bummer but, nothing is perfect or guaranteed.

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[General Questions and Answers] 1edenec:
i did it) but it would be good to know what was wrong to prevent it for other people
[General Questions and Answers] Ibuprophen:
Making others aware of an issue is a great thing to do but, if there's a specific support thread, like the following, it's an even better place to make any issues known for other members who have that specific device and TWRP.

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

I wish you the best of luck!

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[General Questions and Answers] Slurme:
Hello guys,

i have a Geotel Amigo with Android Nougat.

I need your help.

No tools working for root (King(o), Towel, Eroot, Frama, Iroot, Genius.

No costum rom existent.

Have you are a idee?

Need help for root :)