yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Applesexual:
Charlie's article rests entirely on Anandtech's analysis and the G Flex 2 not overheating.

Anandtech's analysis of the 810 is inaccurate of consumer devices, since they were using a TABLET, whose size helped with thermal constraints. We also don't know what cooling device Qualcomm stuffed inside that tablet.

The G Flex 2 throttles way too much and has terrible performance and battery life. In fact, the G Flex 2 is more of an argument supporting MY SIDE, NOT YOURS.
[One (M9) General] Applesexual:
Also, this lovely review just came out concerning the G Flex 2:

http://www.droid-life.com/2015/03/17/lg-g-flex-2-review/

Totally discredits Charlie's article about everything being fine on the G Flex 2.
[One (M9) General] Adam182:
All im seeing is a tragically unprofessional review, he has a few digs at HTC aswell and not a bad word to be said about Samsung... funny that. - Adam
[One (M9) General] Applesexual:
Where does he take a dig at HTC in that review?
[One (M9) General] LenAsh:
Yeah, yeah - this is about the M9, not the LG Flex thing.

Keep it relevant and civil please...
[One (M9) General] Applesexual:
It is relevant.

We understand that the 810 might have some heating issues, and several people posted an article from semi-accurate, which used the G Flex 2 as proof that the 810 doesn't overheat.

Discussing the G Flex 2's performance issues from throttling the 810 is a relevant part of this discussion, because htc devices that use the 810 may also run into the same issues as the G Flex 2.
[One (M9) General] LenAsh:
Until anyone gets one of the M9s in hand, everything is conjecture. Nothing is proof of anything until then.
[One (M9) General] th3:
This man has a good point [emoji106]

So far its just a "could be"

Sent using Tapatalk
[One (M9) General] Applesexual:
Then you may consider the article food for thought.

Realistically, I don't think the final build will differ much from tweakers' review numbers, as the review embargo was set to lift yesterday.

Why would htc give out a review unit that was so far different from the retail unit and then have the review embargo lifted yesterday? Does htc want bad publicity? None of the arguments saying "WAIT UNTIL FINAL BUILD" make sense.

The Galaxy S6 improving from current pre-release build makes sense, because the final build is set to release this week and the review embargo is set to release at the end of this month or early next month. Samsung is sure that the final build will differ from the pre-release build, since they're giving reviewers an extra week or so to review the final build devices, while htc isn't.

HTC, on the other hand, is letting reviewers post their reviews with the pre-release build, meaning htc thinks that not much will change from the final build.
[One (M9) General] breaky9973:
The very popular GSMArena already has their review of the Galaxy S6 up for a few days now. So what is this embargo you are talking about?

I will wait for more reviews. Remember that HTC probably uses different suppliers, for example, for the screen. And it's not the first time a product has been rushed to the market. Doesn't say the final product will not be good.
[One (M9) General] Applesexual:
Some sites have done a review with a pre-release model, but since all the reviews are glowing (Like this one that claimed the S6 was the closest thing to a masterpiece: https://recombu.com/mobile/article/samsung-galaxy-s6-review-in-depth), Samsung sees no reason to tell them to take down their reviews like what HTC is trying to do to the sites that were releasing their M9 reviews.

Under GSM's battery life test, this is what they wrote:

The real embargo date for the S6/S6 Edge is sometime late March/early April, at least 10 days after the final software build becomes available to reviewers, though I don't think Samsung would mind if reviewers broke that embargo, since they're confident the reviews for their phone will be stellar.

It says a lot when a company is confident of its own products and doesn't mind letting reviewers break the embargo date before the device is even released publicly.

HTC, on the other hand, is trying to stop any reviewer from talking about its device before the device even hits shelves. If HTC isn't confident about its own phone, why should I be? :confused:
[One (M9) General] Applesexual:
That's because the G Flex 2 is throttling to prevent the CPU from overheating. This means bad performance.

http://www.droid-life.com/2015/03/17/lg-g-flex-2-review/

If I had to guess, htc didn't put an aggressive throttling program into the M9 like LG did. Why? Who knows... Probably to preserve UI fluidity, but that means that the CPU has more leeway to generate heat and kill battery life.
[One (M9) General] p50kombi:
Look, at the end of all of this bickering, here's the facts:

It's a pre release phone with pre release software running a benchmark.

This means at the moment we know not how the final product will behave, you can't argue with that.

Also, really who cares about benchmarks.

I want my phone to be good at what I do on a daily basis and rest assured, that does not include running benchmarks just to tell people that 'mine is better than yours' .. It's pathetic

It's just plain stupidity in my view.

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M9) General] tmac31:
Problem isnt about scores its about heat you know?
[One (M9) General] p50kombi:
Are you being pedantic?

It will never get hot as it does with a benchmark during normal use YOU KNOW.

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M9) General] Applesexual:
The heating issue isn't the only problem.

The 810 also looks to be VERY power-hungry. The terrible G Flex 2 and M9 battery lives are a testament to that.

Honestly, I'm not sure what htc can do now other than throttle. The "optimization" they're talking about is probably just figuring out when they should throttle the CPU. I doubt it's some magical fix that many people here are hoping for.

HTC kept the throttling low, which ended up overheating the device. My guess is that htc didn't want a G Flex 2-like situation where the phone is lagging, stuttering and crashing every other second because the CPU is throttling too much.

In the end product, they'll probably have to throttle the CPU like what LG did, because 130+ degrees F will put them in lawsuit territory.
[One (M9) General] desiregeek:
I saw the new HTC One M9 here in Taipei as it is already available at the HTC stores for display purposes only. It is quite quick with not much lag at all. Only problem I found was the camera which in my opinion was pretty much average. Indoor rear main camera in my opinion was not great but just average. What I also did not like was how they installed Facebook in there and into Sense 7 with no Uninstall option!

Those that care about privacy and security will have to live with Faecebook on their HTC ONE M9 with no uninstall option under settings in applications.
[One (M9) General] rkial:
Privacy? You can always disable it. You'll never have to see it again
[One (M9) General] Adam182:
I must admit, I find it really annoying when apps cannot be uninstalled, just disabling them just doesn't do it for me. But thats bloatware and part of the parcel.

For Facebook to be one of these uninstallable apps its very dissapointing and i can understand why someone with privacy concerns wouldn't trust a disabled facebook app to really be disabled.

To me its not about a privacy issue, its just more crap that I don't want on my phone - Adam
[One (M9) General] tmac31:
yes it will throttle 7/24 instead.
[One (M9) General] hgoldner:
Well, that's your guess. My M8 has gotten up to 145F from time to time while involved in intensive activities, and it's S-OFF, rooted, and running a custom ROM and custom kernel that is undervolted. Lawsuit? You gotta be kidding me (and I'm a lawyer). There are no public reports I've heard of any HTC products exploding or catching fire (although there *are* of both Samsung and Apple products doing so).

Meanwhile, as to the individual who said he *did* have the product in his hands "on display" in Taipei, that doesn't count. I wouldn't make a purchase decision based upon someone who happened to see a product on display.

I've had the product "in my hands" since January as a tester. The only time the phone has overheated was while doing the dalvik cache rebuild after a ROM update (which we get every 72 hours or so), and even with that, I've never seen it over 130F. It is clear, at least in part, that this is because I tend to install A LOT of apps on my phone.

Look, 8 cores can get hot. It doesn't need to be "throttled," the triggering mechanism which activates the cores needs to be refined. The software is still in R&D. Let's see what HTC says today at noon, and what the final ROM looks like when people actually have the devices and are using them.
[One (M9) General] EddyOS:
No Dalvik any more, bud, only ART ;)
[One (M9) General] p50kombi:
But custom recoveries still call it dalvik wipe....

After dalvik wipe, Android has to rebuild the apps....it just takes longer...
[One (M9) General] fernando sor:
Dalvik is still present actually. It still builds.
[One (M9) General] EddyOS:
Then the recoveries need updating. There is no Dalvik cache, only ART, so it should really say 'Wipe ART cache' instead ;)
[One (M9) General] EddyOS:
It builds the cache, but it's not Dalvik. Android 5.x only uses Android Run Time (ART). Dalvik is no longer in use post-KitKat
[One (M9) General] p50kombi:
Potato-potaatooo... Artyfarty-dalvik.... still takes a long time whatever it's called :)

Cue rant from all the devs around here about the difference between dalvik and art
[One (M9) General] EddyOS:
Hahaha :D

Bit OT, I know, just had to make the correction

Just for my 2p on this thread, my M8 gets hot after doing a lot of taxing work but then again it is a metal body so I'd expect it to. I imagine the other devices don't get 'hot' as they're glass/plastic so dissipate the heat better but as everyone has said no one can comment until the retail devices hit the shops - and even then I'd still wait until the first OTA before making any proper judgements
[One (M9) General] hgoldner:
And if you're an app junkie like I am, whatever it's called, it takes a long time...... In the early HTC Incredible days, you couldn't tell what it was doing after flashing a new ROM, it just sat there frozen at the last frame of the boot animation. At least now the device tells us how many apps (of 279 or so on my devices) it's "rebuilt".
[One (M9) General] fernando sor:
I realize android uses ART now, On the Nexus 7 lollipop is it is still labeled Dalvik with full Dalvik files.

---------- Post added at 11:51 AM ---------- Previous post was at 11:50 AM ----------

Things have improved dramatically already.

---------- Post added at 11:55 AM ---------- Previous post was at 11:51 AM ----------

I think this where the confusion lies because as im sure you know if you decompile a lollipop app you still will have dalvik byte code present as decompiled source also known as smali.

here is from wiki..

To maintain backward compatibility, ART uses the same input bytecode as Dalvik, supplied through standard .dex files as part of APK files, while the .odex files are replaced with Executable and Linkable Format (ELF) executables. Once an application is compiled by using ART's on-device dex2oat utility, it is run solely from the compiled ELF executable; this approach eliminates various overheads involved with JIT compilation, but it requires additional time for compilation when an application is installed, and applications take up slightly larger amounts of space to store the compiled code.[1][3]
[One (M9) General] EddyOS:
But that's to do with apps, source code for the OS is still (meant to be) ART-only. Obviously, there'll be some crossover but, eventually, everything should be pure ART

Lollipop-based recoveries should really remove the 'Dalvik' name as it's not in technically not in use :)
[One (M9) General] fernando sor:
Yes you are right about the run time but as someone who has built apps from source I don't see that changing any time soon . We are talking about two different things here.

But I said that's what is causing the confusion. Dalvik is still used just not the virtual machine.
[One (M9) General] desiregeek:
Here are two pictures I took while at HTC Shop in Taipei. Not sure why but I am unable to post picture using my iPad.
[One (M9) General] Andy:
Guys, lets not get bogged down with what "some guy" on the internet said.

Just ignore it, report it and move on.

Add the user to your Ignore List and enjoy a clutter free XDA.

[IMG="Ignore List"]http://i.imgur.com/IqOZRiu.png[/IMG]

Cheers,
[One (M9) General] fernando sor:
Actually it is. I think you are confusing runtime with actual apps. Dalvik is still being built and can certainly be cleared in recovery. See data /dalvik cache
[One (M9) General] fernando sor:
He was reported. And he is still posting his garbage thread's and negative attacks on htc.
[One (M9) General] Stephen:
Moderator Information,

I have read through and decided to close this thread. Threads like these are not much use, until the phone has actually been released.
[HTC Excalibur] lukecheng:
Does O2 SMS Plus have a smartphone edition?

Miss my Treo. :[
[HTC Excalibur] oplitic:
Do you mean something that puts it in a AIM type format? If so then you can try TextMan and QThreader
[HTC Excalibur] padrino:
Its been talked about a lot. I've personally tried TextMan and SMS threader and they both fall short of the Treo. For now, im back to the regular cluttered inbox.
[Galaxy Note 4 Q&A, Help & Troubleshooting] greatgrandking:
both stock and aosp .... i just got note 4 today

thanks
[Galaxy Note 4 Q&A, Help & Troubleshooting] bondro:
AICP
[XDA Assist] mustafa2211988:
I have s4 i337 i flashed it with pda rom file but it didnt succeed plz i need ur recommendation
[XDA Assist] Heisenberg:
Hi :)

Thanks for writing to us at XDA Assist. A quick search allowed me to find your device forum here:

AT&T, Canadian Bell, Rogers, Telus, Virgin Samsung Galaxy S 4

Within that device forum you can find a q&a sub-forum here:

AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshooting

And within that q&a sub-forum I found a great q&a thread where you can ask any question here:

Stupid Questions Thread - No question too stupid!

I'd suggest you go and ask your question there and the good people of your device section will be able to help you out. Please note, I don't think your question is stupid, that paticular q&a thread is just named a little bit strangely.

Good luck!
[Android Q&A, Help & Troubleshooting] ImSoBored:
That's it... How much temperature can a LCD withstand before getting broken? I am planning to unstick the touchscreen from its LCD, and I would like to know this.

Thank you in advance.
[G3 Q&A, Help & Troubleshooting] ahmad.afef:
Hello,

I use a magnetic card "NFC" to access my work place and sometimes the card like to get lost. I've seen a guy using his samsung as a replacement for the card, but refused to tell me how!

Is there anyway to get this thing working using the LG G3 as I'll be getting one soon?

The card type is Mifare 14443-A3 as scanned using some phone

Can anyone help in this thing?
[G3 Q&A, Help & Troubleshooting] suljo94:
https://play.google.com/store/apps/details?id=de.syss.MifareClassicTool&hl=nl

set it up and use it
[G3 Q&A, Help & Troubleshooting] ahmad.afef:
Thank you very much. I'll try it as soon as I get the phone :D
[One (M8) Q&A, Help & Troubleshooting] hanzibar:
Hi,

I have an HTC that is Sprint lock

I wanted to understand if the fact that the device is Sprint lock is the same as SIM lock?

Thanks
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
"Sprint lock" is not a typical term. You might mean "locked to Sprint" or "carrier locked", which yes that would be the same as SIM locked.

You can easily find out if its SIM locked, by putting in another carrier's (besides Sprint) SIM. If it asks for an unlock code, its SIM locked. If it just works (gets at least voice service and SMS) than its not SIM locked.

If its Sprint branded, and not factory unlocked or otherwise modified, I believe it should be SIM locked.

Also, questions belong in the Q&A section. So I'll ask the mods to move this thread.
[One (M8) Q&A, Help & Troubleshooting] hanzibar:
so, basically, all the videos about how to sim unlock htc one m8 will work for me?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I have no idea what "all the videos" means.

If you mean the free mod (with s-off) the XDA thread specifically says it doesn't work for Sprint: http://xdaforums.com/showthread.php?t=2708572

But you may be able to use a paid service to SIM unlock.
[One (M8) Q&A, Help & Troubleshooting] hanzibar:
I saw that thread, it seem to be :

1. not work for Sprint

2. HTC closed that "hole" and now this won't work.

I guess I will have to find another way
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
1) I already stated that the method won't work for Sprint.

2) It depends on the hboot number, it may still work for older hboots on non-Sprint devices that have not been updated (and a good number of users are still on older hboots).

3) You can try a paid online unlock service. Many services will only charge if the unlock is successful. So its worth looking into, and often costs less than $10 US.
[Xperia Z1 Android Development] optimumpro:
February 4: Rom updated to include February security patches.

Download: http://xdaforums.com/devdb/project/dl/?id=16643

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

January 14. Rom updated to include Google's January 2016 security patches. Also, selinux not only disabled, but completely removed: the rom compiled without selinux sources/binaries.

Kernel does NOT include recovery, so use TWRP for Fota/Recovery partition.

Download: http://xdaforums.com/devdb/project/dl/?id=16217

_________________________________________________________________________________

For those who prefer to stick to bugless kitkat: Rom updated to include all "shields up" features including cleaning creepy Ips and dns defaults. Compiled just a few days ago.

Download Link: http://xdaforums.com/devdb/project/dl/?id=13001

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Here is Slimkat 10 unofficial built from sources on March 2. Built using JDK-7, which turned out to be beneficial for the rom. Slim, fast, smooth and stable. For those of you who have been using Lollipop for a while, you will see how much faster, smoother and more stable kitkat is. Everything works: no reboots, no freezing, no overheating, no screen light flickering, no video recording/play problems, great battery life and abundance of features. This taken together with improved security makes a pretty darn good rom. I tried it and got rid of Lollipop.

Changes:

1. New Iptables binaries which allow to stop kernel communicating (if used with Afwall) with Google home.

2. Changes in Vold to enable 256 bit AES encryption, as opposed to default 128 bit

3. Key length increased for multiple keys

3. Kernel with disabled Selinux and enabled Tomoyo together with all ciphers/hushes/digests/random number generation tools

4. Latest changes from Google code (I was surprised finding changes pushed for kitkat while synching Google source)

5. TWRP 2.8.x integrated in boot image

Install:

1. Be on Kitkat, rooted with recovery

2. Enter recovery and wipe Cache/System/Data

3. Flash the rom and reboot

4. Enjoy and say thank you or perhaps donate

Rom is in Download section above

Credit: Slimroms

Warning: I am not responsible for your device exploding and killing everybody around. You are on your own. :laugh:

Source: https://github.com/SlimRoms/platform_manifest/tree/kk4.4-caf

Source with changes: https://github.com/HonamiZ1

XDA:DevDB Information

Slimkat 10 Final Edition, ROM for the Sony Xperia Z1

Contributors

optimumpro

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Unlocked Bootloader

Based On: Slimroms

Version Information

Status: Stable

Current Stable Version: 10

Stable Release Date: 2015-03-02

Created 2015-03-03

Last Updated 2016-02-04
[Xperia Z1 Android Development] OmarEinea:
Believe me I have no interest in being in any of "your threads" {That's why I'm editing this post instead of posting a new one xD},

I'll leave this thread from any further discussion.... for now at least :p

Regards,

Omar.
[Xperia Z1 Android Development] optimumpro:
Thanks. Reading the OP might help...:D
[Xperia Z1 Android Development] optimumpro:
" you didn't get my point, did you!!"

Oh, I did get your point alright. :fingers-crossed:

Could you please do me a favor? Kindly stay away from my threads. If you feel that you need to continue to report me, that's your right, but again, stay away from my threads. :)

Best regards
[Xperia Z1 Android Development] shingers5:
Gonna give this a try as sounds like Kk on steroids well stable steroids.....LP still too buggy for me.
[Xperia Z1 Android Development] kkuuo:
I tried it. But play store doesn't work. What is the problem...?
[Xperia Z1 Android Development] optimumpro:
Rom Updated

See OP for description and download link...
[Xperia Z1 Android Development] avirale:
thanks

the best option is in that forum for the Z1 now

First download

:D
[Xperia Z1 Android Development] HotA3:
Thanks for all your awesome roms :)
[Xperia Z1 Android Development] Xecu:
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.

The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.

Edit:

I tried flashing TWRP 2.8.6.0 via Flashboot.

Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.

The Led also switches lights from purple to orange.
[Xperia Z1 Android Development] optimumpro:
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
[Xperia Z1 Android Development] Xecu:
Thank you! That did it.

But I still dont quite understand what happened here.

So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.

That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
[Xperia Z1 Android Development] optimumpro:
Xperias don't have recovery partition. Fota is used by stock firmware only, so it is available in custom roms, hence recovery image could be installed there. However, the normal way for custom roms is to incorporate recovery into boot image, which is faster. This was until lollipop, when the not so smart folks at Cyanogen, gave up on CWM (which was always in boot image) and came up with their own recovery. CM recovery does not work, so TWRP guys figured out a way to install their recovery in Fota, instead of having users/developers decompiling boot image, replacing CM recovery with TWRP and recompiling the image again. That's what I do in CM based kernels, but Slimrom folks use TWRP in boot by default.

So, when you did fastboot erase recovery, you got rid of recovery in fota partition. Now, you have TWRP in boot image.