Related
Hi everyone,
New GN,
ITLF41
19250UGKL1
yakjuux
4.01
I've only unlocked it, haven't done anything else.
I was only replying to a text message and in the middle of text, GN froze and the screen went black with a white line across top of screen.
Seemed to occur while the auto-rotate function was trying to rotate screen.
I also noticed the auto rotate on my GN does not work well at all. Sometimes it does, sometimes it will not no matter how long I wait.
Nothing worked, had to pull battery.
Seems fine after replacing battery.
I wouldn't be concerned but for the fact that I was not using 3rd party apps or a different rom. The force 2d option is off.
Is maybe something funky with the GN auto-rotate feature in 4.01?
test4echo said:
Hi everyone,
New GN,
ITLF41
19250UGKL1
yakjuux
4.01
I've only unlocked it, haven't done anything else.
I was only replying to a text message and in the middle of text, GN froze and the screen went black with a white line across top of screen.
Seemed to occur while the auto-rotate function was trying to rotate screen.
I also noticed the auto rotate on my GN does not work well at all. Sometimes it does, sometimes it will not no matter how long I wait.
Nothing worked, had to pull battery.
Seems fine after replacing battery.
I wouldn't be concerned but for the fact that I was not using 3rd party apps or a different rom. The force 2d option is off.
Is maybe something funky with the GN auto-rotate feature in 4.01?
Click to expand...
Click to collapse
Yes, versions 4.0.2 and 4.0.3 fix a LOT of little issues with the GN. They really should've released the phone with one of those 2 versions rather than 4.0.1.
I don't think you should be too worried about battery pulls unless they happen more often than you like.
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
? when do you pull a battery out of a computer?
... haven't received a reboot since day one.
OJ in Compton said:
Yes, versions 4.0.2 and 4.0.3 fix a LOT of little issues with the GN. They really should've released the phone with one of those 2 versions rather than 4.0.1.
I don't think you should be too worried about battery pulls unless they happen more often than you like.
Click to expand...
Click to collapse
Ok great!
This is my first smart phone EVER....lol
Its a tough go catching up with all I've missed.
Thanks!
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
You really shouldn't be forcefully pulling the battery every week, that's terrible advice!
Goddamn it.....that's why I said "reboot" first! Lol!
sent from my Nexus Prime
Simer03 said:
Just like a computer...rebooting or pulling the battery at least once a week is recommended!
sent from my Nexus Prime
Click to expand...
Click to collapse
I'm a Network Admin for a large School Board. I know its strange I know nothing about smart Phones but I do know much about Wireless/Routers/switches and Computers.
If your rebooting computers once a week something is amiss....lol
I have servers and clients that have uptimes of 1 year+ before an update requires me to down a server or re-image a client.
In my case, if what had happened to my NEW GN happened on one of my OES2 Linux servers, Id be scrambling until the issue was found and fixed and i'd be none to happy.
But alas, a server is not a cell phone.
I hope it was a just a freak isolated incident.
You guys...I wasn't saying that u HAD to...if u HAVE to, then there's problems....but if u do it just because, it'll get rid of the little things, like the bug he has
sent from my Nexus Prime
Simer03 said:
You guys...I wasn't saying that u HAD to...if u HAVE to, then there's problems....but if u do it just because, it'll get rid of the little things, like the bug he has
sent from my Nexus Prime
Click to expand...
Click to collapse
LMAO...agreed!
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
Click to expand...
Click to collapse
One very simple reason: If you pull the battery in a bad moment, e.g. right when the hardware is writing something to the Flash memory, you might (soft-) brick your phone and lose all the data on it.
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Click to expand...
Click to collapse
Well because,
If I have to keep pulling the battery (which is NOT occurring thankfully so far) then I would say something is wrong and its not just a software bug. I would call it a blue screen of death in computer terms.
That could be anything from a hardware fault (Memory/CPU/IO sub system..etc) That would for me, mean taking it back.
A hard reset may temporarily fix the issue. But it doesn't solve the underlying problems.
I'm hoping the error was a one off. If it never occurs again, then we're good to go.
If it does, its goin back.
Same thing happened to me, the weird thing is it happened right after I completely reset the phone...
Sent from my Galaxy Nexus
big samm said:
Same thing happened to me, the weird thing is it happened right after I completely reset the phone...
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yea its strange...
In my case the Auto rotate feature seems to be the common theme for funkyness.
Sometimes its quick, less than a second, sometimes it doesn't move at all.....
Then, a hard lock.
I realize that 4.02 and .03 fix some bugs but I have the Canadian ver. and google is not gonna update OTA for my NG.
I'm not ready for the whole, flash to "google's" stock rom yet. I just learned to unlock it...lol. If it locks again i'll try that. If it don't i'll leave well enough alone.
Oh by the way, to the Admins, sorry for not posting in the Q&A section. I though i was in the Q&A, my mistake.
Please by all means move the thread.
zephiK said:
? when do you pull a battery out of a computer?
... haven't received a reboot since day one.
Click to expand...
Click to collapse
Actually, I have to replace cmos batteries all the time.
Usually they are good for 4 or 5 years but sometimes not.
Some people don't know what "Hit F1 to continue" means and I get calls all the time.
So yes, its quite common to have to pull a bad battery when dealing with 2,000+ PC's ...
Simer03 said:
I work for tmobile, at&t and Verizon! I've dealt with dumb little bugs that people have....pulling the battery is the first thing I tell them to do and 99% of the time, it fixes their bug! So why not just save yourself the time and be one step ahead of the phone!?
sent from my Nexus Prime
Click to expand...
Click to collapse
Because I use a otterbox with my Galaxy Nexus and it's not very pleasent to keep taking my phone out of it's hard shell case and putting it back in?
Pulling the battery is always a last resort. If the phone is frozen, that is fine to pull the battery or you can hold power on the phone and it'll turn off by itself (not sure if this is in the GN but it was in Galaxy S1).
@test4echo: That's not the experience of a daily person. Not everyone deals with 2,000+ people on computers.
zephiK said:
@test4echo: That's not the experience of a daily person. Not everyone deals with 2,000+ people on computers.
Click to expand...
Click to collapse
You are correct. Its not a common everyday thing for most.
I was just suggesting a legit reason for why anyone would need to pull a computer battery.
On another note, i agree with you that having an otterbox case makes it even more of a pain to have to pull the battery.
I just had another freeze up while trying to get back to the main page using the launcher.
Im getting worried now. I've had this phone for 2 weeks and it was great until today....
I think I'm gonna bring it back to virgin just to be safe before my 30 days is up.
If its just software then the new one will do it as well but at at least I'll know thats what it is and either wait for samsung updates or update manually.
Again....nowhere in my response did I say u HAVE to pull the battery every week....I simply said its best if u do, nobody is gonna force u to! But when u do get a bug...pull that battery, and if it keeps happening, send it for warranty...simple
sent from my Nexus Prime
Hi all,
I got my One X a few weeks ago, very soon after launch (O2). Initially I was very happy with my purchase but now I'm left extremely frustrated with this handset and regretting buying it - screen flicker, dropped calls, lots of little bugs, and now... The camera won't work!
I've been using it quite a bit since I bought it, but yesterday I was using it (no settings changed) and each time I took a picture there was either corruption in the image or a blank image with an exclamation mark icon instead of the picture. This now seems to happen almost every time I try to take a shot - I've done the following in an attempt to rectify:
1. Reboot handset
2. Ensured no other apps are running prior to using camera
3. Reset camera settings to default
4. Ensured phone was fully charged
5. Ensured I have enough free storage space (~22GB free)
I'm not going to perform a factory reset because I'm not convinced it's going to help anything AND I shouldn't really have to do that! I haven't got time to completely reconfigure my phone.
Still, I'm unable to take a photo and this is *really* annoying me! A premium handset with issues all over the place... Unacceptable!
Now I'm left thinking I'm going to go back to O2 and demand replacement with a SGS3, because by the looks of things HTC haven't actually fixed most of the bugs we're all experiencing.
Such a shame - had so much potential and a genuinely amazing device to pick up and use in many ways, but it's quite frankly not fit for purpose if I can't make reliable calls, take pictures or use the screen without serious flickering.
Has anyone else experienced these camera issues I described above?
Apologies for the tl;dr, just a very frustrated HOX owner.
So because you got a faulty phone all the others out there are not fit for purpose?
OK got ya that seems fair
There's something wrong with your particular phone, just get it replaced. The vast majority of people have no flaws whatsoever.
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
nikorette said:
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
adamsharif said:
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
Click to expand...
Click to collapse
Yes really. It'd be incredibly foolish to assume that XDA users are representative of the majority of phone users and even more foolish to assume that people who have flawless phones will be just as vociferous as those with flawed phones.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
Why don't you try and reflash your phone with a RUU or return it for replacement?
Well that's what I've done - just booked it in with O2 so will see what happens.
Still interested to know whether anyone has had this camera issue though?
adamsharif said:
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
nikorette said:
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Lol you still don't get it. Some people just do not know about forums. Unless you get a number from HTC that states how many returns per device made. Nobody, not you or me will know. Not reading anything other than what's on my screen. I'm defensive, by logic you're aggressive.
I guess you won't. Everyone else just ran a factory reset instead of crying about it.
Anyway like most of the threads on here its no longer about the op's post and more about the ego of the people posting. I'll admit I am at fault sorry if I derailed your thread..
Sent from my HTC One X using Tapatalk 2
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Adamsharif;
You do seem to have a phone that, under UK law does not appear to be fit for the purpose for which it is intended, regardless of the warranty obligations of HTC.
In reality, you should back everything up and factory reset the phone, if only to rule out any problems which could be solved, by doing this. If then, the phone does not work, you are well within your rights to demand a refund or a replacement.
If you're not willing to do a simple reset to fix potential issue, HTC and the users here are definitely not going to be willing to help you out. We can't reset the phone for you, but you still want to fix it by using and looking at the phone until it behaves itself.
adamsharif said:
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Click to expand...
Click to collapse
Here you go, proof that the majority of XDA members have no issues whatsoever with their device.
http://forum.xda-developers.com/showthread.php?t=1585082
Of course, people with no problems don't post much on forums, so the actual, real-world results of such a poll would be MUCH more one-sided.
As for your camera problem, many people have suggested fixes; Factory Reset, re-flashing RUU and, if all else fails, return the device and get a refund/replacement.
People seem to think their £500 device is going to be perfect. Don't get me wrong, It SHOULD be perfect, but no device is ever going to be. The HTC One X issues are also relatively minor compared to some devices that came before it.
kannanX10 said:
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Exactly. There's an old thread about this issue. Fixed with 1.28
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok, I guess I shouldn't have been so stubborn - currently backing up the device and will do a factory reset.
The backlight issue, however, is the one I'm returning for - the thing I find strange about both that and the camera issue is that they suddenly appear which really makes me feel that there are hardware issues in the first batch.
Lesson learned - don't buy a handset as soon as it comes out!
Personally I feel that mobile manufacturers need to undertake better testing and not rush their products to market - if you look at many of the recent handsets from Apple, Samsung, HTC there have been a lot of silly issues which have damaged reputations.
If I can have a HOX with working camera, backlight and calling it will be the perfect device!
You don't want to change your phone and yet you can't live with the problems. What do you want? Just ranting? Got it.
Sent from my HTC One X using XDA
ALL THE CORRUPTION ISSUES EXCEPT FLICKER are solved by firmware 1.29
My new hox was updated to 1.29 two days after I bought it, I never encountered the said issues, also flicker is related to overheat on 1.29 the phone temperature is a lot better
you regret buying the most praised and critically acclaimed android phone lol
I think we're being a little harsh on adamsharif, I love my HOX but its not without it's flaws and some of the 1.26 bugs were just messy...the phone shouldn't have been released with this firmware...it was rushed but I can understand why with the SG3 looming!
Unfortunately the average user turns to a forum when he / she has issues, the average user doesn't sign up to XDA to just say how happy they are, some do, just not your average joe, so it all looks like doom & gloom!
£500 is a lot of money, should we have to factory reset it after a few days / weeks? Should we not expect a near perfect product considering the money spent....I don't know....android isnt a perfect OS so I think the arsehole answer is get an iPhone!? I think in 3 months time we'll all be happier and mostly problem free!
Sent from my HTC One X using XDA
Guys please stop the pointless comments.
Back on topic. I suggest you try a third party camera app from market and see if that works. If it works, i too believe that hard reset will solve the problem. Also, don't underestimate hard reset. It usually solves most unknown issues
Hello,
I've been googling for days in order to avoid a repost out of respect for the community and to avoid redundancy, but my searches have yielded inconclusive results, with varying answers. Additionally, I couldn't find one in this particular subsection of the forum.
My problem stemmed from using Cyanogenmod while the screen is hot. I was texting on maximum brightness while also downloading several files so the entire AOSP messaging app got imprinted on the screen. The keyboard is faint but noticeable. I had a samsung epic 4g before this with similar problems that went away after I completely stopped usage and turned in on one day. The one on my old Galaxy SI was much more severe and visible from reasonable distance. This one is faint but enough to bother me.
Some searches said the handful screen burn in fix will help, other threads say I should just replace my device (I hope not to go through the hassle of that one) and others say that I should leave a white screen on and a few other searches say that such problems do not exist.
If this is a repost I apologize. All help appreciated.
First, have you shut the device off and let it cool down? If not, that could fix the issue. If that doesn't fix the issue, download LCD Test from the market, set it on the white screen, making sure that you keep the backlight on, and let that run for several hours. Sounds like a pain, but it can potentially fix the issue. There are other methods, but try these two first and if they don't work, let me know and we can try something else.
Sent from my SGH-T999 using xda premium
Never had that issue or seen a phone with that issue. never even had anyone come into the Tmo store I work at with that issue. Sounds to me that if you have had it on your past 3-4 phones maybe you should look at adjusting the way your using them.
As far as fixing it. Do the white screen thing or get it replaced
Sent from my SGH-T999 using Tapatalk 2
clninja said:
Never had that issue or seen a phone with that issue. never even had anyone come into the Tmo store I work at with that issue. Sounds to me that if you have had it on your past 3-4 phones maybe you should look at adjusting the way your using them.
As far as fixing it. Do the white screen thing or get it replaced
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
That's odd since this is a fairly common issue among those who use AOSP keyboard. To be frank I had my ex's name burn in on the screen as well because we messaged so much. Poetic justice perhaps.
I have successfully returned the phone and gotten a new titanium grey one. Thank you both.
So heading says it all, did you have the issue before you installed it and did the ROM fix the issue? I've done the low ISO, I missed around with the settings and it does not fix or make it at all better. I will not settle for a replacement device that is not brand new so I am looking for a software fix. I figure a ROM made from a developer phone would fix it since their software is not affected by this issue. So let me know if you have an answer for this. The key has to be that you had the issue before you installed the ROM. Don't trash the tread with junk or speculations of what might fix it I am only interested in facts at this point I've done all the Google might fix and none did....reply away!
Sent from my HTC6500LVW using xda app-developers app
So I read an article on engadget that said the 4.3 update made improvements to the camera in low light settings. I was previously avoiding 4.3/5.5 ROMs because you can't change the lock screen image independently of the home screen. Anyhow, I flashed it last night and have been snapping away with the camera. The pictures seem better.
It's a shame, other than the camera this phone is nearly perfect.
Sent from my HTC6500LVW using Tapatalk
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Sounds about exactly right for what can be done. The low-light picture taking is really a hard thing to accomplish, me thinks. I have a Canon DSLR, and fast lenses are expensive (apart from prime lenses), so I'm not surprised that this overprmised technology is not meeting expectation. That said, do people really use their camera phones that heavily? I don't. And it certainly wasn't a feature I considered when buying this phone. Not to knock any enthusiasts, but this defect has made me realize how many folks are satisfied with phone camera fidelity.
For any of you interested in photography. $50 spent on a 50mm prime will blow your brains out, expectation-wise.
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Over in the regular HTC one forum someone posted a video of a HTC one running kit Kat and the person had the phone laying down on a table. When he got to the camera the screen stayed black and their was no purple haze going in and out. So I hope it does fix it and look forward to a kit Kat Rom for our phones.
Sent from my HTC6500LVW using Tapatalk
Zynesterysdan said:
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good point. I've been playing with it more today. I have been able to capture most pictures without the hue, but like you said, it kind of fades in and out.
Sent from my HTC6500LVW using Tapatalk
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
one4thewings said:
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
Click to expand...
Click to collapse
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
jessbowring said:
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
Click to expand...
Click to collapse
Yes, I did return it to stock before sending it in. I don't know that I needed to, but I wasn't going to take a chance on them refusing to do the work because they didn't like my icons or zooper widgets. =)
I used this thread here: http://forum.xda-developers.com/showthread.php?t=2475216
Just to update this thread I did end up sending my phone to HTC to get repaired it was a one week turn around and came back same phone and fixed. Getting my phone repaired was a big deal since I don't want a CLN or Refrib device. So phone is fixed!
Sent from my HTC6500LVW using xda app-developers app
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
I'm a crack flasher so I flash just about every ROM released just to give it a go and I have to have a ROM (4.2.2, 4.3 or 4.4) that has remedied the issue. HTC swears up and down that there is a camera update coming with 4.3 but seeing as how AT&T and Sprint folks said it helped nothing at all in their forums I'm leaning towards a hardware issue. Sucks but we might be stuck with it.
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Before and after. No modifications just point and click didn't change anything on camera since I got it back.
Sent from my HTC6500LVW using xda app-developers app
Grnlantern79 said:
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Well unfortunately I can't be without my phone for more than a couple of days. I use it for work and personal. Too bad HTC doesn't have designated repair centers we can take our phones to for repairs of manufacturer defects. HTC should have acknowledged the issue and authorized cell provider stores where the device was purchased to do exchanges after the traditional 30 day exchange was up. I tried to exchange mine at the Verizon store I bought mine at and they wouldn't do it. Said I still had to go through warranty repair. It's understandable on VZW's end bc it isn't their fault HTC shipped jank phones but on the customer service side it makes both companies look bad. Glad yours got fixed though.
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It must be subjective bc my hue is still bad but my girlfriend's is semi-okay.
Has anyone noticed that, for all its pixel density, there is some really poor-looking emphasis on edges? Lots of places throughout the stock UI, fonts, icons, etc, will have their edges brighter than the rest of the object. What's more is this is not uniformly applied, so you wind up with some words or icons having this edge detection going on, and in other places, things look properly "flat".
Frankly it makes this "beautiful" screen look really ugly, since the UI it displays looks really ugly.
You may be talking about the over sharpening issue that's been discussed to death on these forums. Hopefully LG fixes it with an OTA update, or we get it fixed with ROMS.
Slash8915 said:
You may be talking about the over sharpening issue that's been discussed to death on these forums. Hopefully LG fixes it with an OTA update, or we get it fixed with ROMS.
Click to expand...
Click to collapse
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
courtlandj said:
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
Click to expand...
Click to collapse
Glad you like it.
americasteam said:
Glad you like it.
Click to expand...
Click to collapse
courtlandj said:
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
Click to expand...
Click to collapse
You knew the buttons were on the back before you bought it so the error is yours if you find there placement an issue.
I think the screen is fantastic and don't have the problem you speak of.
Sent from my LG-D855 using Tapatalk
Lol, buying a device with buttons on the back...just to come on xda and complain about buttons on the back? Okie
As far as the screen sharpness, they do need to address it somehow because black text are indeed awful (not to the point i will complain about them awful though)
Should have done your homework before buying a device that OBVIOUSLY came with buttons on the back though...considering it was flashed all over the internet so you cannot say "oh i bought it and realized buttons were on the back" lol
MaximoMark said:
You knew the buttons were on the back before you bought it so the error is yours if you find there placement an issue.
I think the screen is fantastic and don't have the problem you speak of.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
You have it, it just doesn't bother you. Good for you, my eyes are pretty sharp though and don't need LG's help in that regard. Button placement? Sure. Sure I knew that beforehand. That does not mean it's my error. It's still LG's error. See, I can't really use this thing before I purchase it. They have display models in stores, but the backs (and often the sides) are covered in whatever anti-theft anchoring the store uses. It's not until I get the device home, have it in my pocket, that these usability errors can really make themselves felt. It didn't bother me while the device was in my hand, I thought, well, maybe I will just learn, in time, where my fingers should go. Fine.
But then, and imagine this scenario as being one I cannot replicate in a store with a demo model, the phone was laying face side up on my desk, and I wanted to turn the volume down. Or I wanted to turn the screen off. I can do that without picking the phone up with just about all other phones in the world. Inconvenient. This is a small issue! This is not a big deal. But. But I paid $600 for this, I am not supposed to have to put up with some minor inconvenience, is how I see it. For their flagship phone, the top of LG's current heap, they shouldn't have got any "small issues" wrong. But they did. They got this wrong. And while people replying to this thread seem to want to forgive LG, and that is your prerogative, I refuse to do so.
Doesn't your phone have knock code to switch the screen off? Or have volume controls in the notification area?
Sent from my LG-D855 using Tapatalk
Anyway, the screen looks terrible and the big beautiful screen is the biggest selling point (or am I wrong on this? some argue camera...).
I wouldn't return the phone because the buttons were on the back and yes, "lol", I knew they were there before, during, and after purchasing it.
The big beautiful screen turning out to be not very beautiful, now that, that I could return a phone over. There's not even an option to disable the over-sharpening. Tell me that is not a design failure.
Why is this thread even in existence? This topic been covered elsewhere and not to mention the rest of the post are off topic.
Sent from my LG-D851 using Tapatalk
shook187 said:
Why is this thread even in existence? This topic been covered elsewhere and not to mention the rest of the post are off topic.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Not in terms of the screen looking not very great.
courtlandj said:
Not in terms of the screen looking not very great.
Click to expand...
Click to collapse
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
shook187 said:
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I have found that the stock theme/wallpapers/icons etc don't do the device any favors. Tweaking these things made the phone much more tolerable for me.
shook187 said:
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Including but not limited to. Sharpening is an issue, but since you cannot disable it, and since it is not by default enabled across all text rendering, not in all apps, etc, it's not uniform. The UI winds up non uniform. The entire graphical feel of it seems mixed and weird. So it made me feel like the display itself was not that great. I actually wondered if there was something physically wrong with my screen. Or, since it was not a uniform problem, was it only one part of the screen that was perhaps damaged or something.
courtlandj said:
You have it, it just doesn't bother you. Good for you, my eyes are pretty sharp though and don't need LG's help in that regard. Button placement? Sure. Sure I knew that beforehand. That does not mean it's my error. It's still LG's error. See, I can't really use this thing before I purchase it. They have display models in stores, but the backs (and often the sides) are covered in whatever anti-theft anchoring the store uses. It's not until I get the device home, have it in my pocket, that these usability errors can really make themselves felt. It didn't bother me while the device was in my hand, I thought, well, maybe I will just learn, in time, where my fingers should go. Fine.
But then, and imagine this scenario as being one I cannot replicate in a store with a demo model, the phone was laying face side up on my desk, and I wanted to turn the volume down. Or I wanted to turn the screen off. I can do that without picking the phone up with just about all other phones in the world. Inconvenient. This is a small issue! This is not a big deal. But. But I paid $600 for this, I am not supposed to have to put up with some minor inconvenience, is how I see it. For their flagship phone, the top of LG's current heap, they shouldn't have got any "small issues" wrong. But they did. They got this wrong. And while people replying to this thread seem to want to forgive LG, and that is your prerogative, I refuse to do so.
Click to expand...
Click to collapse
First, to your last post, the hardware buttons no software can address?
Tweaksbox can, they are hardware buttons like all others, it doesn't matter where they are on the device.
Turning the device off while flat on the table? Double tab the statusbar (yes, works with every launcher and in any app).
Sound: volume slider within notifications?!
If it's that much of an issue for you, swap it, simple as that, i do like having the buttons on the back, why? I can't press them by accident while gaming and i love the feel of having just the edges while in hand.
Last but not least, the oversharpening is your point, i don't really notice it and really like the screen, but that doesn't matter, that's just me, but anyways I'm pretty sure there will come an update for it, if not, that's xda, the bootloader unlock is almost released, there will be a fix for that, because, you know what, it's our device and we can mod the hell out of it if we like to. Every flagship has it's flaws, there isn't any perfect device on the market, if those of this device bug you too much, swap it for another, maybe those flaws you can stand.
Gesendet von meinem LG-D855
Buttons on the back is not an ERROR its lg DESIGN go to the lg 2 you will see, it wasn't thought over night...do not place your dislike on lg "error"
over sharpness been talked to death as it is. I never understand why people complain, don't like something return it. Its that much of an issue? return it. since I have gotten the phone I have only touched the volume keys for one, and only one thing....to take screen shot. Knock on puts the phone on for me, a simple double tap. If I want to be fancy, I can use the knock code or w.e the hell they call it. I only need my volume on two things, silent, vibration and sound...if its too loud notification is there to reduce it or voila...the buttons on the back a simple press will fix it.I do not need to move my hand in any weird kind of a way to do anything, I do not accidently have to press on the volume keys like i have done so many times.
The screen is beautiful without auto brightness. The oversharpness is batter of taste...you will either like it or you will hate it. You obviously hate it so very simple, return the phone instead of beating on the same dead horse. The screen is awful? we knoooooooooooooooooow from xda and all over the net and all over google + and every social media....the text are sharp? we knoooooooooooooooooooow...go return the phone.
mgbotoe said:
Buttons on the back is not an ERROR its lg DESIGN go to the lg 2 you will see, it wasn't thought over night...do not place your dislike on lg "error"
Click to expand...
Click to collapse
I feel that it is an error.
mgbotoe said:
over sharpness been talked to death as it is. I never understand why people complain, don't like something return it. Its that much of an issue? return it.
Click to expand...
Click to collapse
You are complaining about my complaints. I never understand why people complain about other people complaining. Don't like my complaint, ignore it. It's that much of an issue? Close your browser. :silly:
And with that, reported. We don't need another repetitive, argumentative thread that goes nowhere.
Than get rid of the error and return the phone like you said, no custom rom will fix that itch for you. Stop being a statistic of the list of people beating on the same dead horse.
Good luck on your future ventures I HOPE you do far more research on your next phone hunt huh? You rarely post in this forum as it is according to your junior status, member of 2011. Let hope the next post you choose to do about that phone wont result in something like this
Tootles
---------- Post added at 10:50 AM ---------- Previous post was at 10:48 AM ----------
meatlocker said:
And with that, reported. We don't need another repetitive, argumentative post that goes nowhere.
Click to expand...
Click to collapse
Thanks, i got lost in this lil banter. Lol see ya