OK I know there have been similar threads on this but nothing conclusive has emerged, so I'm going to ask here.
I have the backlight flicker issue which other users have reported. It is most pronounced at around 40% brightness and is reasonably consistent to reproduce. The effect is a rapid change in the light level, almost light flickering candlelight. There is no corruption of the actual display.
I have seen this both on the stock ROM that came with the phone (Orange UK, 1.28) and all the latest CM10.1 builds).
My flatmate also has a One, but on Vodafone UK stock, with a higher 1.29 version. He has no flickering problem
So, I'm trying to figure out whether I have a hardware problem, or whether the newer software on my flatmate's phone is the difference. I'm still able to get a warranty replacement, although obviously that entails trying to get the thing back to stock so I'd rather avoid it if its something that'll get fixed shortly.
Is there any consensus on whether this is hardware or software? Anyone with similar problems care to post their software versions so we can see if there's any kind of pattern?
Cheers
Sent from my One using xda premium
If anyone's interesting, updating to the 1.29.401.12 firmware fixed my backlight issues. Running the latest CM now with no problems
Sent from my One using xda premium
thanks for the information, glad you sorted your problem out.
John.
Related
Please don't hate me for starting another GPS thread, but I'm dying to understand something. Every GPS problem thread has someone speak up and report that the GPS problems are fixed in most of the xda ROMs. So my questions to the ROM developers are...
At a high level, what did you do to solve the GPS issues? Did you rewrite or replace a buggy driver? Did you add code to make the driver smarter in dealing with flawed hardware? Do you feel the hardware is at fault? Did you just tweak some internal settings? Is it just because Froyo fixes it? Is it because fixing the lag solved the GPS issues?
Some people still insist that it's a hardware issue and no ROMs really fix the GPS. Some ROMs just make it tolerable. Do you agree with them? I don't think Samsung will ever admit it's a hardware problem because it would result in a multi dollar recall.
Thanks in advance.
richb500 said:
Please don't hate me for starting another GPS thread, but I'm dying to understand something. Every GPS problem thread has someone speak up and report that the GPS problems are fixed in most of the xda ROMs. So my questions to the ROM developers are...
At a high level, what did you do to solve the GPS issues? Did you rewrite or replace a buggy driver? Did you add code to make the driver smarter in dealing with flawed hardware? Do you feel the hardware is at fault? Did you just tweak some internal settings? Is it just because Froyo fixes it? Is it because fixing the lag solved the GPS issues?
Some people still insist that it's a hardware issue and no ROMs really fix the GPS. Some ROMs just make it tolerable. Do you agree with them? I don't think Samsung will ever admit it's a hardware problem because it would result in a multi dollar recall.
Thanks in advance.
Click to expand...
Click to collapse
There's a few software fixes that make it tolerable, but its not gonna as perfect as some other android phones or other phones in general. Its flat out a hardware problem. If it was software it would have been fixed by now
All of the fixes more or less use similiar methods to try and make it better, and sometimes it will probably seem almost perfect, sometimes it will flat out suck
good question.still wondering coz im still using the stock rom for 4months, >.<
Sent from my SAMSUNG-SGH-I897 using XDA App
For a long while now an on many different roms I have noticed my phone rebooting at what appears to be random atleast twice a week.
It's never been when in a call and I often only notice it because I see the boot animation on my phone out of the corner of my eye while it was doing nothing but being sat on my desk! Also I know when it has done it because it has switched back to my default network which I am not normally on.
For me I have had it on everything from CM7 to Juwes to docs rom to stock. If this is not normal behaviour I fear that my phone may have a hardware fault
Post your random reboot experiences here!
My experience: rarely with Darky 10.1, I got one today with Juwe 5.1 but I installed this rom two days ago and still making some experiment.
Bye.
always close to stock cfroot only + own changes = never had issues ...
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
TBH I haven't actually been on a pure stock rom for quite some time. From what I remember I would get the occasional random reboot but probably not quite as often as I have done since turning to custom roms.
Could some fundamental change that many custom roms make cause this?
Or could perhaps a certain rogue app which I have had installed on many different roms be causing this?
kezgez said:
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
Click to expand...
Click to collapse
Yes this is partly why I decided to create this thread and try to get to the bottom of it. My warranty runs out in 2/3 months and the paranoid side of me fears a hardware issue. I also started on 2.2 and don't think I got quite as many, if any, random reboots then which seems to coincide with your experiences.
Deck6rd said:
Yes this is partly why I decided to create this thread and try to get to the bottom of it. My warranty runs out in 2/3 months and the paranoid side of me fears a hardware issue. I also started on 2.2 and don't think I got quite as many, if any, random reboots then which seems to coincide with your experiences.
Click to expand...
Click to collapse
Yeah our guarantee runs out in about 6 or 7 weeks which is why I thought of phoning them, my phone has been back once because the motherboard or whatever its called had to be replaced. do you think it could be hardware?
kezgez said:
Yeah our guarantee runs out in about 6 or 7 weeks which is why I thought of phoning them, my phone has been back once because the motherboard or whatever its called had to be replaced. do you think it could be hardware?
Click to expand...
Click to collapse
I have no idea. I'm starting to think probably not. so far 75% of people to this poll have reboots either daily or weekly. I think it could be a software bug in all gingerbread based roms but i really don't no. Would be interesting to flash back to stock froyo and see if it persists then.
Keep an eye on this thread and hopefully we can get to the bottom of this
kezgez said:
Both my husband and I get them at least twice a week also, we are on stock JVH that we got from O2 through Kies, not rooted or anything. we are thinking of phoning samsung tomorrow, we never had any of these on 2.2, so I think it must be software with us both getting them since 2.3. both our phones are still in guarantee, although if it is software I dont know what they can do
Click to expand...
Click to collapse
Ideal time to flash a custom rom with root. Follow the white rabbit.........
blockbuster 2.4
Are those who never get any random reboots mostly on stock roms? if so which roms?
mhm...............
Deck6rd said:
so far 75% of people to this poll have reboots either daily or weekly. I think it could be a software bug in all gingerbread based roms but i really don't no
Click to expand...
Click to collapse
question/thread title is "Does your phone suffer from random reboots?" so majorityof people that does not have any reboots/problems will not join to read so they will not vote
also by the thread title in some way youre determining the anserw yet still youve got 15 people voted (thats not authoritative + 350 thread openings...) & 33% of them said NEVER
I used to get random reboots on stock firmware, because samsung can't write software! Since running cm7 based software (insanity cm) I haven't had one single reboot, the stability is mindblowing and it is super stable, however it is not really for flashing novices, just my humble opinion
Sent from my GT-I9000 using XDA Premium App
I'm with 2.3.4 JVP, and usually after an uptime of around 333 hours the phone reboots itself, happened twice...
$omator said:
question/thread title is "Does your phone suffer from random reboots?" so majorityof people that does not have any reboots/problems will not join to read so they will not vote
also by the thread title in some way youre determining the anserw yet still youve got 15 people voted (thats not authoritative + 350 thread openings...) & 33% of them said NEVER
Click to expand...
Click to collapse
Yes I do admit I haven't received the amount of feedback I was hoping for in this thread. And yes I am fully aware that polling on here is far from an accurate way of gathering data exactly for the reason you suggested but still I hoped to learn something about the extent of this phenomenon.
Also when I wrote that quote that you critisied for being inaccurate it was correct at the time. If not a little premature
However please feel free to share your experiences (or lack of) the topic in question.
I voted 'very rarely' - usually when running a buggy app that uses all RAM and CPU.
No reboots by itself so far.
to much, using dark core 2.6 , pilotx rom
Wow I thought I am the only who suffer with this..LOL...My phone is running JVO 2.3.3 and I updated it via Kies...no root no lagfix, quite a virgin Galaxy S..hahaah...
Very rarely, and it was only after this one time I had to swap batteries and didn't allow the phone to fully shutdown which must've caused some corruption. Even though I restored a backup certain things just seemed off and turned out I did had problems with reboots and so after that, most likely being the cause.
Besides that, after putting in a fresh ROM and whatnot, never had issues, not before the incident save once maybe.
I have changed to juwe 5.1 today from his 5.0. Was playing angry birds and left phone down for minute, then soon as screen locked it rebooted itself. Have not tried with other apps yet. Will post back when tried them out
I have them in GB/ICS and JB on official and custom roms. Seems that 312mhz min freq fixes for CM7 at least.
Why does this happen? Why hasn't LG fixed it? WHAT IS THE CAUSE?
Used to happen with any ROM on my Asus tf101...
Afaik until now no one know what exactly is causing this even other androids have this or all androids
Edit: oh i find it on my brain as i remember tonyp said that our cpu or the android cpu is failing to wakeup and this is a outdated binaries? Can someone correct me
Sent from my Optimus 2X using xda premium
grimmyrippy said:
Afaik until now no one know what exactly is causing this even other androids have this or all androids
Edit: oh i find it on my brain as i remember tonyp said that our cpu or the android cpu is failing to wakeup and this is a outdated binaries? Can someone correct me
Sent from my Optimus 2X using xda premium
Click to expand...
Click to collapse
As far as i know what you are saying is true...
Since people are saying the problem is more or less evident on all ROMs (custom or official) and on different phones, I am wondering whether this may (at least partially) be hardware-related, meaning a problem with the particular phone (not a model, but that very unit)? Just wondering because I am hot having this problem at all. I did see a lot of FCs or freezes while trying some experimental/unstable/beta ROMs, but with the stock-based ROM I am currently using I have not seen a single SOD. Same is true for DM ROM (also stock-based). What am I doing wrong? I admit, I am not using the phone as actively as many people do. I don't play any games. I don't install a lot of different apps. Just a regular daily use -- calls, email, browsing, WiFi/BT/GPS. But no SODs whatsoever...
I have no idea whats causing the BSOD, but my experience with my phone is it depends on which kernel I use.
Some kernels give BSOD no matter what ROM I use, but others "never" gives any BSOD.
I honestly have no idea but I have a feeling it's more hardware related than software. Also other android devices suffer from it?
-sandro- said:
I honestly have no idea but I have a feeling it's more hardware related than software. Also other android devices suffer from it?
Click to expand...
Click to collapse
Yes also other but other android is looking for deep sleep feature it mean that they actually want to have deep sleep on their phone to save battery and their something on our phone that triggers deep sleep and i think this something is the one we need to fix
Sent from my Optimus 2X using xda premium
Hey all,
So after trying to figure out why my camera won't focus where I tell it to, it seems that there was an international One update about a month ago that made improvements to the camera, as well as updating it's firmware. While reading the article, it was unclear whether or not that update was applied to the Ones that were to be sold in the US before release day.
Does anyone have some info on this? Can we expect this update sometime soon, or has it already been applied?
Edit: Well it seems there are multiple updates involving the camera (and a few other goodies) http://tech2.in.com/news/smartphone...ttery-life-improved-camera-performance/872234
How long does it take for sprint to rollout updates?
roflhorse said:
Hey all,
So after trying to figure out why my camera won't focus where I tell it to, it seems that there was an international One update about a month ago that made improvements to the camera, as well as updating it's firmware. While reading the article, it was unclear whether or not that update was applied to the Ones that were to be sold in the US before release day.
Does anyone have some info on this? Can we expect this update sometime soon, or has it already been applied?
Edit: Well it seems there are multiple updates involving the camera (and a few other goodies) http://tech2.in.com/news/smartphone...ttery-life-improved-camera-performance/872234
How long does it take for sprint to rollout updates?
Click to expand...
Click to collapse
We have the updates already..What we are waiting for now is the capacitive button fix..I honestly can't believe a update for the buttons has taken this long..(Im not a Samsung fan) but they got a pretty quick update after release to fix small issues.
I'm not sure if any of the updates were included with the US version. My camera seems fine, my "back" button, however, is a mess. It barely works, takes 2-3 presses sometimes. I put a freezer bag on my phone at work to keep metal shavings off of it (due to the 100% lack of a good pouch available) and the back button is non responsive through the bag. I have read it's the same way with a screen protector.
So, hopefully we will be getting an update soon to fix this, and whatever other issues people are having.
That's odd. I never have an issue with any of my buttons
Shifted from the ONE
heres what you can do guys, extract the rom.zip out of the RUU for the international update, decrypt the rom.zip which will give you output.zip. remove and replace any frameworks, modules, binaries, etc... as per instruction on the Porting any ROM to Sprint thread. be sure to remove any radio, hboot, modem, etc... images before flashing. hope this fixes your issues, but i haven't even heard of any of those issues prior to this thread. :\ good luck! may the droid be with you
Tilde88 said:
heres what you can do guys, extract the rom.zip out of the RUU for the international update, decrypt the rom.zip which will give you output.zip. remove and replace any frameworks, modules, binaries, etc... as per instruction on the Porting any ROM to Sprint thread. be sure to remove any radio, hboot, modem, etc... images before flashing. hope this fixes your issues, but i haven't even heard of any of those issues prior to this thread. :\ good luck! may the droid be with you
Click to expand...
Click to collapse
Really?... Cause the capacitive buttons being a crapshoot has been on numerous threads. It's a hugely known problem.
The camera though is new to me.
Sent from my HTC One
+1 on the buttons being wonky. Proven issue and supposedly fixed with the international update. Some people may not notice it simply becuase they naturally hit the sweet spot so to speak since the touch footprint of the button is sort of small.
The back button works best for me when I swipe it instead of pressing..
I see several of the issues the int'l update was supposed to fix. I don't think we have it. I emailed HTC about some issues I've had and their canned response seems like they're already it but no eta.
Sent from my HTCONE using xda app-developers app
Can any Cyanogen Mod rooted user tell me if u still get the purple tint camera issue..i like the camera of this beast and would root if the issue is solved after rooting..(i had gone thru some posts related to this and can say that this is a software issue since i hav 2 htc one and the one which iv not updated to version 4.2.2 does not hav this issue)..i dont want to hav the other phones camera ruined so would not update it..
So is rooting a solution..can anyone tell me..??
I haven't seen any tinting issue on GPE Rom
Sent from my HTC One using XDA Premium 4 mobile app
.SiD. said:
Can any Cyanogen Mod rooted user tell me if u still get the purple tint camera issue..i like the camera of this beast and would root if the issue is solved after rooting..(i had gone thru some posts related to this and can say that this is a software issue since i hav 2 htc one and the one which iv not updated to version 4.2.2 does not hav this issue)..i dont want to hav the other phones camera ruined so would not update it..
So is rooting a solution..can anyone tell me..??
Click to expand...
Click to collapse
I have a factory GPE and it has the tint issue, I think at this point the general consensus is that the tint is a hardware issue. Some camera apps deal with it better than others. Sense allows you to set the ISO and that helps a bit, stock android camera does not. But in the end it's a hardware issue. I think you can safely update the software, it's not going to affect your camera.
So if this is some kind of hardware issue then can I go for a replacement (I hav some scratches at the back of my HTC one)..so m I still unser it's warranty..??
And just out of curiosity..of this is a hardware issue than how is it affecting the other HTC one's which Did not hav that issue before the 4.3 update..??
.SiD. said:
So if this is some kind of hardware issue then can I go for a replacement (I hav some scratches at the back of my HTC one)..so m I still unser it's warranty..??
And just out of curiosity..of this is a hardware issue than how is it affecting the other HTC one's which Did not hav that issue before the 4.3 update..??
Click to expand...
Click to collapse
Regarding the warranty replacement, there is a whole thread about that. Many people have seen their problem get fixed under warranty, but your luck getting your phone fixed or replaced depends on your carrier or local HTC center, etc. It should also be completely stock.
How is it affecting phones that did not have the issue before 4.3? Is it? I'm no expert, but I haven't heard of that. However, one explanation could be that sometimes this issue presents over time and not immediately. Some people have gotten phone replacements that solve the camera issue and after a few weeks, the problem appeared on their new phones.