yashsingh1/xdaforums huggingface dataset:
[One (M7) General] puremind:
Great stuff I will go to the shops and check it out. Why can't you find the ID on the DNA?
[One (M7) General] Maedhros:
I made a thread about this earlier, but I only got troll responses.

Hope this thread receives actual input, this is kind of an important thing for me.
[One (M7) General] jonstatt:
Hate to throw a spanner in the works here, but it may also be that different firmwares are producing different default colour temperatures. With the One X there were indeed three manufacturers of screen. For the European models it was Acer and Sharp. Acer had been colour fidelity, but less uniform, and not as bright. The sharp was a light cannon, but very cool colour temperature, and better uniformity. However, HTC reduced the disparity through firmware updates!

Therefore, the only true way is if we can find a reliable way of finding the vendor code such as in the log file.

Also I can tell you that I had a Sony Xperia last year. Even though all the screens are made by Sony, there was a huge variance between two supposedly identical phones, as I found out when I compared to a friends.

---------- Post added at 01:35 PM ---------- Previous post was at 01:30 PM ----------

Absolutely spot on accuracy here. I confirmed the One X+ my wife bought had an identical characteristic to the One X Acer screen I had before. However they seem to have improved the uniformity issues from my original One X.

I also have a suspicion that at least my One uses a Sharp panel and has a number of characteristics similar to the Sharp screen used on the One X. It has a colour temperature that is a bit on the cool side for sure. Although I haven't measured yet, I have a keen eye, and I would have said it was a little over 7000K. I also compared it to my wife's One X+ and it is a bit cooler, but not rediculous (nothing like the S3 which was wildly off). We may find a future firmware update corrects this if the variance between One's with sharp panels is not too severe.
[One (M7) General] puremind:
Even if it were true, battery life will still fluctuate depending on the screen type you have, and it is something end users have no control over once the device has been purchased, so may as well test his before purchasing...
[One (M7) General] BarryH_GEG:
You're sort of on a witch hunt. HTC hasn't used two panel vendors on a single device since the Teg3 One X. When they did, none of the characteristics of the phone (EG: power draw, benchmarks) were any different. You're basing all your assumptions on tests conducted by eight different reviewers, using eight different methodologies, and using eight different sets of conditions.

Here's how the Teg3 One X fared in some of those same reviewer's tests. They were all testing a One X with the AUO panel because HTC didn't provide review samples that had the warmer Sharp panel (for good reason). And from being on the One X forum I assure you, as much as that phone was picked apart with a microscope, it there were any impacts to anything but color temperature because of the two different displays it would have been on the front page.

And if you performed the same analysis you did to reach your conclusion on any phone you'd see similar deviations. The deviations are there but it's differences in the reviewer's testing, not the devices themselves. By all means carry on but I think when people begin posting their panel ID’s it’ll most likely show a single display type.
[One (M7) General] puremind:
Please be honest about this. It is not even debatable that maximum brightness has an impact on battery life. Just to prove my point. Take this test:

http://www.computerbase.de/artikel/handys/2013/htc-one-im-test/5/

Battery time at maximal brightness (383cd/m²): 277 min (4:37)

Battery time at 200cd/m²: 322 min (5:22)

That's 16% more battery for a 58% decrease in brightness. Therefore, if you do the maths, this means an 11% difference in battery performance for web browsing/HD Video between the 650cd/m² model and the 385cd/m² model.

If you apply this to the current GSM Arena battery charts, which were created based on the top brightness model (650cd/m²), you can see that the HTC One climbs further up on the chart.

And this factor is even an underestimation for the GSM charts, because they measure standard definition video as opposed to HD, so the impact of screen brightness in their testing environment should be even more, probably around 20% between the two devices.
[One (M7) General] BarryH_GEG:
Do you know what brightness settings each of the reviewer’s used when they tested battery life? I'm willing to bet it's not maximum brightness and that all the phones each of them test are set to some equivalent level that the reviewer applies consistently.

And what you're saying is debatable. Each of the reviewer's data you're quoting is correct; based on

their

testing methodology. What I'm saying is that the same display is performing within 10+/-% (normal deviation) and that 382cd/m2 from 3Dnews

is the same

as 647cd/m2 from GSMArena. The display's not performing any differently, it's how their testing that's causing variations. The swings in the One X comparative I provided show that. Do you honestly believe if the delta on One X displays at max brightness was 386 vs. 550 that the owners of the less bright display(s) wouldn't notice? There are 100 pages discussing the difference between the warm Sharp panel vs. the cool AUO panel so it’s not as if owners aren’t conscious of their display’s performance.

So you’re taking something that’s meant to be viewed vertically (EG: comparing multiple devices performance against each other on GSMArena where the same methodology was used) and trying to make it horizontal by taking a single device's results from eight different reviewers and comparing them. It can't work because, again, they all use different methodologies for

each

of their tests. No analysis based on an undefined or inconsistent baseline can ever be compared. There are just too many variables that can (and do) skew the results. And here’s how to prove this. If you ran the same analysis across the same eight sites for the XZ you’d get a similar result to what you got for the One. Same for any other phone. If what you’re representing were true every device produced would have three display types and wild swings in battery life based on huge variations in brightness. We know that’s not the case because it would be all over each devices respective XDA forum.

Here's one of GSMArena's battery tests.

The web browsing test is performed using an automated script which reloads a webpage every ten seconds. There are no flash elements on the web pages, so the playing field is even. The brightness of the phones' displays is set to 50% and we use a Wireless N router placed a few meters away to get full connectivity bars.
[One (M7) General] puremind:
No disrespect, but you don't seem to be intimately familiar with screen calibration. The difference between the top level of observed brightness and the lowest one is huge. Not difference is testing conditions, protocol or testing devices can explain such a difference (650cd/m² to 385cd/m²).

If testing devices had such error margins, it would be a well known fact amongst professional calibrators, and no one would hire their services because essentially eye calibration would not be any less accurate than measured calibration...Please be serious.

As someone who had calibrated many displays, and repeated measurements with different measurement devices and under different conditions, please trust me when I say that brightness measurements are very stable and reliable, using even the cheapest colorimeters (chromaticity and black levels are more sensitive to the device used but brightness is easy).
[One (M7) General] LadFromWales85:
This thread makes me nervous. When the One X come out, I had access to several handsets at once, all of which displayed different tints when on boot screen or recovery screen. Some white some yellowed.

Is this the same with the One? Are there cool and warm screens?
[One (M7) General] BarryH_GEG:
No disrespect, but you don't seem very familiar with comparative analytics which are the crux of your conclusions.

This is from the site you posted with the lowest cd/m2 score for the One. The One's performance against the One X+ matches up to GSMArena's comparison of the same two devices even though GSMArena's relative cd/m2 score for both devices was almost double. If the One's they each had didn't have screens that were performing similarly the deviation against the One X+ would have been pretty obvious to both of them.

Maximum brightness has remained virtually unchanged from the HTC One X +: was 373 cd / m 2, was 10 candelas more. But seriously change the contrast: on the already considerable 862:1 she grew up in half and is now 1258:1.​
[One (M7) General] puremind:
Who spoke about wild swings in battery life? I gave you a figure (11% for a 58% difference in brightness) based on 1 testing environment, 1 testing device, 1 reviewer. The difference is there. In fact, I even have no doubt that the difference could be more when testing SD videos instead of HD videos like in the test I quoted or that this percentage could be higher when starting from a much higher brightness point.

I read the GSMArena testing setup. Based on this, the difference is probably even larger than in my estimate for their own setting. As you said, not all settings will produce the same differences. The GSM set up for video testing was less demanding in terms of video processing, therefore the impact of screen brightness should be even greater!

The fact that battery life is impacted by maximum screen brightness is just not debatable, especially if what you say is true and it is only one and the same display. This actually precludes any other factors such as different display energy efficiency between different display models from making the brighter display brightness somehow equally energy efficient than the lower brightness display.

If what you say is true, then the battery difference is just not questionable. if screens had been different, I could have agreed that the brighter screen could have been as energy efficient due to different technology, but as it stands, light must be produced with energy and more light with more energy..
[One (M7) General] puremind:
Comparative analytics reinforce my point - the computerbase setup is actually more forgiving for screen brightness than the GSMArena one (focus on HD Video means the proportion of battery loss explained by brightess vs. that explained by video processing is less vs the GSM Arena setting), so based on comparative analytics, the difference would be even greater than 11%. That will teach me for understating battery improvements in my table just to not appear to arbitrarily inflate my results!
[One (M7) General] BarryH_GEG:
Of course it is. Your assumption, based on a flawed comparative resulting in a flawed conclusion, is that each One built could have a display that varies from 382-647cd/m2 and therefore battery performance could vary accordingly. I'm saying there's most likely a single panel used on the One and the difference in brightness between any two panels is no more than 10+/-% due to manufacturing tolerances and that all One's will have similar battery life when used the same way. If you're right this thread will balloon in to 100+ pages and end up a sticky because the lucky winners of the "screen lottery" you're describing that draw 382cd/m2 displays will be up in arms. If I'm right this thread will die out fairly quickly as the deviation you're hypothesizing only exists on paper.
[MDA, XDA, 1010 Software Upgrading] k_kirk:
Hi,

I have 4.00.021 on my Asian XDA and decided T-Mobile is not good for me. I now have the well documented can't go back issue and guess what, my bootloader is 5.17 to make the insult even bigger... I tried the fix broken bootloader but get the following error : ... As you will notice I put the tool in c:\binaries as the long directory names were attributed to this problem earlier on. Any idea how I can overcome this riddle? Thanks a zillion in advance.

C:\binaries>pnewbootloader bootloader_v5_15.nb0

'C:\binaries\pput.exe' is not recognized as an internal or external command,

operable program or batch file.

ERROR: ITReadProcessMemory - Unspecified error

Unable to find flash info offset, cannot disable bootloader writeprotect
[MDA, XDA, 1010 Software Upgrading] cgigate:
search and read old threads!
[MDA, XDA, 1010 Software Upgrading] k_kirk:
Thanks for your friendly reply. I did exactly as you told reviewed many threads and am none the wiser. The new fix broken bootloader tool gives me the error mentioned below and I could not see a resolution to that. I will try the old XDAwrit + SD Card reader option next but comparatively thats a very risk option as I understand it and hence my reoluctance.

If you know how to make fix broken bootloader work please spare me with a part of your wisdom and just tell me how. Thanks a lot for your help.
[MDA, XDA, 1010 Software Upgrading] cgigate:
read this link http://www.xda-developers.com/forum/viewtopic.php?t=2928

if you still cannot make it work, send to me, I will fix it for you
[MDA, XDA, 1010 Software Upgrading] k_kirk:
Thanks for your offer for help. I must be the miggest idiot on this forum. I still can't make it work... I read & read & read the link you gave me but I'm still none the wiser. Few issues I am stuck with :

In the thread you mention I see the reference to 'pnewbootloader bl515.nb0'

I do not have bl515.nb0 but I have bootloader_v5_15.nb0 from Jeff's tools and when I use this file I get the following error. My ActiveStink is working.

H:\build>pnewbootloader bootloader_v5_15.nb0

Unable to find flash info offset, cannot disable bootloader writeprotect

Then I want to use the wallaby patch loader option so I refer to the following link but this link is not live any more.

updated version of wallaby patch loader at http://www.xs4all.nl/~itsme/download/wbt-1.5.tar.gz

What should be my next step? Should I try to fix whatevers wrong with the pnewbootloader or should I hunt down the wallaby patch loader option....

Totally confused. Thanks a lot for your help. Regards
[MDA, XDA, 1010 Software Upgrading] itsme:
my latest tools don't use 'pput' anymore, so you will encounter less problems

if you use the newest from http://www.xs4all.nl/~itsme/projects/xda/tools.html
[MDA, XDA, 1010 Software Upgrading] k_kirk:
Got it and tried it. Results are the same :

C:\binaries\build>pnewbootloader.exe bootloader_v5_15.nb0

Copying C:\binaries\build\itsutils.dll to WCE:\windows\itsutils.dll

Unable to find flash info offset, cannot disable bootloader writeprotect

Do you think this has anything to do with the protection T-Mobile builds into their ROMs? To re-iterate I have the 4.00.021 on.

Any other ideas? Thanks a lot for all your help. Regards.

Kerem
[MDA, XDA, 1010 Software Upgrading] k_kirk:
As per instructions in your text file I tried pmemdump and get the following. Not sure if this is of any help.

C:\binaries\build>pmemdump 0x80001880 0x40

80001880 20 00 00 00 20 72 30 00 ff ff 00 f1 e0 07 1f 00 ... r0.........

80001890 00 00 00 00 20 20 20 20 56 35 2e 31 37 20 20 20 .... V5.17

800018a0 20 00 00 00 20 20 42 6f 6f 74 6c 6f 61 64 65 72 ... Bootloader

800018b0 20 00 00 00 20 57 41 4c 4c 41 42 59 20 00 00 00 ... WALLABY ...
[MDA, XDA, 1010 Software Upgrading] Billgate:
I have the Same error with k_kirt when i try to down from 6.22 to 5.15 , Dont know what to do. Somebody help me.
[MDA, XDA, 1010 Software Upgrading] k_kirk:
billgate, please see

http://xda-developers.com/forum/viewtopic.php?t=3162

Thanks to the help from friends on this site my problem is resolved. If you have a SD card reader/writer you can use the older version of XDArit to write the Wallaby patch and then bring your bootloader version to 5.15.

good luck.
[MDA, XDA, 1010 Software Upgrading] Diki:
K_kirk,

Could you please explain in detail?

Where can I find the bootloader 5.15? I have downloaded the file "wallaby-patch-tool.nb2"

What should I do now?

please help me!
[MDA, XDA, 1010 Software Upgrading] Indecided:
donpkong,

nice to see a fellow m'sian here.

Anyways, i'm currently on 6.22, downgraded my WM2003 to PPC2002, because of poor battery life and a DEAD vibrator after upgrading.

I"m trying to downgrade my 6.22 to a 5.15 because I have an inkling it's the root of the problems - IE vibrator not working.

Pnewbootloader doesn't work for me - it just says "Unable to find flash info offset, cannot disable bootloader writeprotect" so i guess the only hope is via SD-flashing.

Would like to get a few things clear here.. in a nutshell, what I have to do is :

1) Create Wallaby-diagnostics card

2) Create ROM image + 5.15 bootloader onto another SD card using XDArit options

then

1) Load up with patched diagnostics card (Wallaby)

2) Backup ROM + Bootloader (optional)

3) Select Restore SD

4) Insert SD, restore OS + Bootloader

Is there anything I missed out? I'm desperately wanting my vibration back because it's annoying to miss calls during meetings and stuff like that.

Thanks!
[MDA, XDA, 1010 Software Upgrading] donpkong:
i did not have to downgrade from 6.22 to 5.15 and my vibrator works fine on WM2003. i do not know how to downgrade bootloader or have the need to do so.
[MDA, XDA, 1010 Software Upgrading] Kavin:
What do i got to do if my xda lose bootloader.

Press and hold Power Button then Press Reset. Nothing appear.
[MDA, XDA, 1010 Software Upgrading] buzz_lightyear:
@kavin

the same happened to my XDAII.

I would say, once you lose the bootloader and you, probably, don't want to play with JTAG, you can only send it to repair service...

buzz
[MDA, XDA, 1010 Software Upgrading] Kavin:
Thank buzz_lightyear for reply.

But I can't send it because I'm living VietNam.

I give it to someone but they said that Nothing can do.

Oh....my god! I'll lost my xda...>> :cry:
[MDA, XDA, 1010 Software Upgrading] negatong:
Thanks donpkong

This is the amazing thread. Solve my problem that I have looked for solution for a long time. Thanks!!!
[Sprint Samsung Galaxy S III] Max_Pain:
Hey guys. Just did some reading in the general, themes & apps and development sections and didnt find anything but i must ask since my wife insists....is it possible now or will it be ever possible to do the dual camera thing from the s4 ads or is it a hardware limitation and only the s4 will be able to do it?

Thanks.
[Sprint Samsung Galaxy S III] tazfanatic:
Not sure if Sammy has released source yet so till then I doubt anyone will be able to answer this till then.
[Sprint Samsung Galaxy S III] kingy9000:
All Software Updates to S4 will be given to S3

From what I have read about the Galaxy S4 and seen it doesn't seem to have any special camera improvements except for a 13 megapixel back camera and 2 megapixel front camera compared to the S3's back 8 megapixel and front 1 megapixel camera. Also Samsung themselves said that any new software update, which this seems to be, will be given to the Galaxy S3. So until Samsung release the new software's source code or whatnot I don't see someone else doing this soon, maybe. (There might be some modders out there who might build their own tweak for this but unlikely)

While you wait for this feature to be released I would suggest using the Multi-lens Camera, which can be found with a quick search in the play market, that can be used to take pictures like shown in the S4 ads and more! (Haven't tested the application myself yet) Hope I helped you out. :D
[Sprint Samsung Galaxy S III] topherk:
I'm no developer, but it's possible that there's a hardware limitation in terms of physically switching both cameras on at the same time. I doubt it, but it's definitely a possibility.

That being said, if there is no such hardware limitation, I believe our dev's will be able to figure it out even before the release of the software. There are already commands that control each camera separately (in order to switch them), so it's just a matter of making an app (or modifying the camera apk) to allow both at the same time. Of course, I'm making it sound easier than it actually is, but I believe that it should be possible.
[Sprint Samsung Galaxy S III] 11marko11:
Possible the porting of that camera on my s2??
[Sprint Samsung Galaxy S III] CNexus:
Same thing applies. Dont just start listing phones now saying "how about this one".
[Sprint Samsung Galaxy S III] -EViL-KoNCEPTz-:
Go ask in your phones forums.

☆SoA: Son's of Android™☆

I like to break stuff! :D
[Sprint Samsung Galaxy S III] brianmoyano:
Any news?
[Sprint Samsung Galaxy S III] zim_zimmer:
Not sure if this helps as I've just found this on my lunch break so haven't had a chance to try it, but the video looks like it could answer your question

https://www.youtube.com/watch?v=h0I1_cF0ML4
[HTC Droid DNA] brian85:
Will the Verizon droid DNA work on straight talk?
[HTC Droid DNA] romy134:
The Droid DNA is for Verizon Right? I dont belive this combination will work, as Verizon is CDMA and I belive Strait TALK IS gsm
[HTC Droid DNA] Bigandrewgold:
It will work. The DNA is a global phone.
[HTC Droid DNA] 123421342:
You wont get 4g though. You might get hspa+, maybe. However you will be getting screwed over because straight talks's gsm coverage is inferior to their cdma coverage.
[HTC Droid DNA] zounduser:
I was just gonna start a thread on this topic. I'm using straight talk on my DNA right now. I get hspa+ or "at&t" 4g speeds. I was just talking with a Wal-Mart rep who told me, that 3 straight talk users here In Montana were terminated from straight talk because the SIM runs on AT&T network. In the fine print supposedly it's only supposed to use sprint, and Verizon networks. I guess AT&T caught these users using their towers.

I'm a little scared of getting terminated myself. But I don't want to pay Verizon high ass prices! I guess that new law will affect us after all.
[HTC Droid DNA] Mr.Mischief:
Define "screwed".

AT&T's 3G is faster than Verizon's. You can't use Straight Talk Verizon with your own phone either.
[HTC Droid DNA] CharliesTheMan:
^^ That's what she said
[HTC Droid DNA] enigma2446:
iv been using straight talk sim on a verizon droid dna for awhile now and everthing seems to work fine even the h+ speeds. seeing that it is a global phone you just have to create a new apn via straight talk change the network mode and your done
[HTC Droid DNA] pio_masaki:
I think they meant on the CDMA side of straight talk vs the gsm side.

Tapatalked from my HTC DNA - MoKee
[HTC Droid DNA] justin lamantia:
Since I've bin back using my HTC DNA I've bin with ultra.me which is in new york, so far no problem. Honestly if you yourself has an account with them I wouldn't worry. But for myself I keep hearing about METRO PCS about unlocked phones & up too $100 REBATE , I think I might check that out. The subject of the story is that if you have a phone you like make sure it's unlocked & go to whoever you feel comfortable with bottom line!!!!!!!!!!!!!!!!!!!!!!!!!!
[HTC Droid DNA] cherryiice1:
Walk through please?

To any of the posters that have the dna running on straight talk, I'd love a walk through on what needs to be done to get this to work. I'm giving my boyfriend my old dna, and he has straight talk service currently. He's really excited to get a phone that's a lot better than the one he's been using for the last three years, and I really want to pull this off for him but Im not sure what exactly I need to do. All help is appreciated... Thanks!
[HTC Droid DNA] Uzephi:
I think you just set the phone to global mode for gsm networks of on stock. If using a custom Rom, just download the gsm version.
[HTC Droid DNA] xlxcrossing:
Service is good as it runs on at&t. HSPA speeds can vary from 2-8 MB so for $45 a month you can't go wrong. If he uses a sense based ROM he will probably have to manually edit his APN which the Straight Talk website covers in detail. If its a stock android ROM for me it automatically configured my APN. I just put my ST Sim in the phone.
[HTC Droid DNA] mrlokoo:
im using att

do any one knows how to connect it on cdma instead of gsm att or tmobile?