Develop Bugs

Serious camera issues...

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

[POLL] - 1.29.401.11 ota - Does it fix your flicker issues?

I thought I would start a poll thread to see if we can gauge the effectiveness of the latest 1.29.401.11 ota update in fixing our screen flicker problems.
It will be best to submit your personal result after a few days usage as the fix apparently takes a few days to learn and adjust your voltage before it can be come noticeable.
Let's hope the results are favourable.
Update (17th May):
Well, so far so good for the latest update, the signs are very positive for a lot of users, still not happening for some although as a few of you have said it is early days to be feeding back on the effectiveness of the update, as HTC have said it can take 1-2 weeks for the flicker to go away. Although there is a fast fix method you can try which is working for many:
Fast fix (after a full charge):
Unplug device from charge
Turn the screen up to full brightness and disable auto adjust
Use the device/leave it on for 1 hour
Turn the screen off and leave it off for 5-10 minutes
Turn the screen back on and use at full brightness again for another hour
Repeat the process for 4-5 cycles
I would then advise returning the screen to your normal brightness settings and using it as normal for a few further days to see if the issue totally goes away
Report back if you can.

I cant vote till I am on the xda app right now but my flicker is gone since today. I updated yesterday and let it on full brightness some time
Sent from my HTC One X using XDA

I have only experienced the flicker issue once when 3G was disabled and I was connected via EDGE but I was not able to reproduce this behavior.

I will report after few days of testing. So far I can tell its still there, maybe got abit better, but need to test more.

N3m3515 said:
I cant vote till I am on the xda app right now but my flicker is gone since today. I updated yesterday and let it on full brightness some time
Click to expand...
Click to collapse
Very good news
DJ Set said:
I will report after few days of testing. So far I can tell its still there, maybe got abit better, but need to test more.
Click to expand...
Click to collapse
Let's hope it is getting better for you, and after a few more days usage it will be done altogether.
These are positive signs.

It's been told that it can take up to 14 days to correct itself and you're saying people should vote after a few days usage. I'm sorry but what is the point of opening this thread right now?
I'm saying this because people don't read. They'll check whether the issue is gone right after updating to 1.29 OTA and vote accordingly. And that will cause a misleading poll for people like me waiting to buy this phone because of this issue. At least the poll should be closed right now.

N3m3515 said:
I cant vote till I am on the xda app right now but my flicker is gone since today. I updated yesterday and let it on full brightness some time
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Did u connect the charger when running on full brightness? I updated two hour ago and im running on full bightness without charger.

umd said:
It's been told that it can take up to 14 days to correct itself and you're saying people should vote after a few days usage. I'm sorry but what is the point of opening this thread right now?
I'm saying this because people don't read. They'll check whether the issue is gone right after updating to 1.29 OTA and vote accordingly. And that will cause a misleading poll for people like me waiting to buy this phone because of this issue. At least the poll should be closed right now.
Click to expand...
Click to collapse
I totally agree with this. The poll should be put on hold, or at least someone should vote after say 5/10 days of usage (and/or) few days with max brightness.

umd said:
I'm saying this because people don't read. They'll check whether the issue is gone right after updating to 1.29 OTA and vote accordingly. And that will cause a misleading poll for people like me waiting to buy this phone because of this issue. At least the poll should be closed right now.
Click to expand...
Click to collapse
lovidore said:
I totally agree with this. The poll should be put on hold, or at least someone should vote after say 5/10 days of usage (and/or) few days with max brightness.
Click to expand...
Click to collapse
As it states in the OP, it is best to post after a few days usage with the latest update.
However many people are already reporting the flicker as fixed or getting better, and many people are trying the fast fix by leaving the screen on full brightness and this poll gives those 1X owners the opportunity to vote on preliminary findings.
I, and others already see the poll as useful, I am in the same boat as UMD, waiting to see if the issues are going to be resolved through a software update before I pull the trigger and buy the handset.

I can confirm that the flickering seems to disappear!! My device struggled with the flickering problem when it runs @ max. brightness level and from time to time while on auto brightness. After installing der latest OTA yesterday @ 7 pm i set it to max. brightness and used it very much, till device ran out of juice!
While it has been on charge i did NOT use the device! After full charge im running it again at max. brightness and playin' around (Whatsapp, some games, browsing). I check nearly every 15-30 minutes my battery graph because i experienced the heaviest flickering while seeing that battery screen like in the attachments @ the end of my post!
Furthermore i am checking the full grey image in the HTC pictures app again and again.
What can i say? It is getting MUCH MUCH better every hour! Before the update i had sometimes very bad flickering but now it is nearly gone! Another thing i would like to say is that it is NOT related to heat because i just played Shadowgun and Glowball and the HOX had a temperature of 47°C! After the gaming session i opened the full grey picture and the flickering has NOT regained!
You can check the flickering with the two pics i added in the attachments!
I will report when the flickering has completly gone! But i want to say that open a full grey picture and let it stay with display timeout set to zero did NOT change anything for me! I had to play around so that the display contents changed.

Didnt have it before... So cant vote ....

What about the 'I never had it in the first place' option?

EddyOS said:
What about the 'I never had it in the first place' option?
Click to expand...
Click to collapse
GTFO
10chars

lovidore said:
GTFO
10chars
Click to expand...
Click to collapse
Oh grow up - it's a serious question. It'd help people to see the issue isn't as bad as everyone thinks it is
Once you have many posts as me then you can tell to do one

all perfect now

EddyOS said:
Oh grow up - it's a serious question. It'd help people to see the issue isn't as bad as everyone thinks it is
Once you have many posts as me then you can tell to do one
Click to expand...
Click to collapse
You're coming here to give moral support to the people who have flickering screens?
Thanks bro. I'm absolutely positive that all 9k posts are just as informative as the one I just quoted. Anyways, moving on.

How do you "produce" flickering? I don't think I ever had that on my phone.
Sent from my HTC One X using xda premium

simpelsense said:
Did u connect the charger when running on full brightness? I updated two hour ago and im running on full bightness without charger.
Click to expand...
Click to collapse
Some time with some without.
Sent from my HTC One X using XDA

How about people also test for screen glitches like status bar garbled up while we scroll notification bar up and down, I will be relieved if that issue is resolved!!!

dryspuri said:
How about people also test for screen glitches like status bar garbled up while we scroll notification bar up and down, I will be relieved if that issue is resolved!!!
Click to expand...
Click to collapse
That issue is resolved for me since 1.28!

[Q] Going nuts if locked with an App open?

Hi all,
Last week I was at home pondering around as I do, when I heard a text come in.
I went to my phone and literally (no exaggeration) could not pick it up.
It was so hot, I had to touch it through my jumper. I unlocked it asap to see if anything was going on.
Low and behold, Facebook was looping into an error. Errors - Closes - Opens - Errors - Closes etc.
Is this something to worry about? Can apps actually cause that much heat?
Phone still functions fine afaik.
I turned it off, and put it in the fridge!! YES THE FRIDGE
I can't explain how hot it was to touch.
Is this specific to facebook?
Is it the error, loop or app that caused it? AND WHY DIDNT MY PHONE STOP WHEN IT WAS OVERHEATING?!?!
Thanks !!

Can you tell the details? The Rom, kernel you are using?
Sent from my HTC One X using xda premium

Totally Stock - Never unlocked never rooted never rommed nothing.
Facebook has received an update since this happened.
But I'm still at odd's as to why my HOX's over-heating safety never kicked in and shut the phone off.
It's like it was trying to melt itself !!

You have something nasty with heat problems these days Mr W ! But yeah the phones security system was supposed to do its job ! Hardware problem that's out in the open now because of a software problem !

I do Hoffman - Nah I'm sorry, Mr.Hofs is better.
But do you think Facebook is to blame? Or the phone for not dealing with it?
And
Should I now be worried about locking my device with an app open? (NEVER LEAVING FACEBOOK OPEN ANYWAY!)
PS - What do you mean "Hardware problem that's out in the open now because of a software problem !" Mr.Hofs?

Well maybe the phone suffered already of this "fault" but it comes now out to the open because your facebook app caused all that trouble !
I can't tell if its a 100% hardware fault or a 100% software fault. I think its a bit of both because the should have shut itself down !
Btw i read a while back that a newer software update caused the phone to overheat a bit while it was on usb charging. That was fixed by updating the windows drivers. If im not mistaken it was hamdir who came with that.
Otherwise a factory reset might do the trick, if it occurs another time.

Cpu will go right up to 99c before it shutdowns.....
Throttles at 85c
Sent from my HTC One X using xda app-developers app

treebill said:
Cpu will go right up to 99c before it shutdowns.....
Throttles at 85c
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I don't think it was that hot.. but surely if a phone reached that temp the plastic would melt?
Plastic melts at around 110 Degrees C ? Isn't 99 cutting it fine?
Mr Hofs said:
Well maybe the phone suffered already of this "fault" but it comes now out to the open because your facebook app caused all that trouble !
I can't tell if its a 100% hardware fault or a 100% software fault. I think its a bit of both because the should have shut itself down !
Btw i read a while back that a newer software update caused the phone to overheat a bit while it was on usb charging. That was fixed by updating the windows drivers. If im not mistaken it was hamdir who came with that.
Otherwise a factory reset might do the trick, if it occurs another time.
Click to expand...
Click to collapse
I hope its not hardware, as I'm sure warranty ran out last month... GUTTER.
I'ma find out when Warranty finishes, when thats the case I'ma custom ROM it, see what performance I can get out of it !!
But I'm still at odd's with this.
It never even gets hot for me, but that error-loop was just bonkers haha ! (May factory reset if it occurs again though !!)

Wilks3y said:
I don't think it was that hot.. but surely if a phone reached that temp the plastic would melt?
Plastic melts at around 110 Degrees C ? Isn't 99 cutting it fine?
Click to expand...
Click to collapse
well the CPU max temp is 99c meaning you could (in theory) run the chip at 98 c, though it would be throttled but it would be fine however the heat you are feeling is actually the battery heating up, the battery really shouldn't go above 55c, 60c is about it's limit. At 48c the battery reports as overheating and wont charge till it's 47c or below.
I believe gsam battery monitor has alarms you can set to warn you what the battery hits X c (you can set it), its a pretty good app for showing stats about your phone should defo try it out

treebill said:
well the CPU max temp is 99c meaning you could (in theory) run the chip at 98 c, though it would be throttled but it would be fine however the heat you are feeling is actually the battery heating up, the battery really shouldn't go above 55c, 60c is about it's limit. At 48c the battery reports as overheating and wont charge till it's 47c or below.
I believe gsam battery monitor has alarms you can set to warn you what the battery hits X c (you can set it), its a pretty good app for showing stats about your phone should defo try it out
Click to expand...
Click to collapse
Hey, I tried GSAM once and the layout of the app just threw me, didn't like it at all and the terms it uses to explain the data you're looking at isn't good IMO.
I have BBS ad WLD and think that will do for me - Thanks for the advice though.
I'ma keep an eye out and see what happens, I've felt it getting hot in my pocket once or twice, but unlocking the phone, and locking it again seems to make the heat die down. I need to find what may be causing this heat, may not have been the Facebook app alone, but that error was like tipping petrol onto the already burning fire.

Wilks3y said:
Hey, I tried GSAM once and the layout of the app just threw me, didn't like it at all and the terms it uses to explain the data you're looking at isn't good IMO.
I have BBS ad WLD and think that will do for me - Thanks for the advice though.
I'ma keep an eye out and see what happens, I've felt it getting hot in my pocket once or twice, but unlocking the phone, and locking it again seems to make the heat die down. I need to find what may be causing this heat, may not have been the Facebook app alone, but that error was like tipping petrol onto the already burning fire.
Click to expand...
Click to collapse
*burns* lol
any app that will show you apps/wake_locks will do. Something is keeping the phone awake making it use the CPU.
if you're rooted you could try underclocking the CPU to 1.3 GHz, undervolting or just simply disabling 2 cores.

treebill said:
*burns* lol
any app that will show you apps/wake_locks will do. Something is keeping the phone awake making it use the CPU.
if you're rooted you could try underclocking the CPU to 1.3 GHz, undervolting or just simply disabling 2 cores.
Click to expand...
Click to collapse
All good advice my friend, but 1 I'm not rooted yet, waiting for warranty to finish. (Silly I know, but never had luck with HTC)
2 - I don't want to under-volt/under-clock.
I've been monitoring and MAPS is my biggest Wakelock.
Disabled the Location settings this morning.
That not the cause of the heat though, I just have a feeling its not.
Thats the only time its really felt dangerously hot to me though !!
PS - Thanks for your replies everyone, much appreciated.

Yeah well i was just thinking out loud, heat problems are not my expertise !
I hope you get it sorted !

Mr Hofs said:
Yeah well i was just thinking out loud, heat problems are not my expertise !
I hope you get it sorted !
Click to expand...
Click to collapse
Cheers bud !
Will update if any progress.

Wilks3y said:
All good advice my friend, but 1 I'm not rooted yet, waiting for warranty to finish. (Silly I know, but never had luck with HTC)
2 - I don't want to under-volt/under-clock.
I've been monitoring and MAPS is my biggest Wakelock.
Disabled the Location settings this morning.
That not the cause of the heat though, I just have a feeling its not.
Thats the only time its really felt dangerously hot to me though !!
PS - Thanks for your replies everyone, much appreciated.
Click to expand...
Click to collapse
Yeah maps have always made my phone hot, using navigation with gps if you have it on charge will pop up "using more power than being supplied".
If you don't use maps I suggest disabling it.
Sent from my HTC One X using xda app-developers app

treebill said:
Yeah maps have always made my phone hot, using navigation with gps if you have it on charge will pop up "using more power than being supplied".
If you don't use maps I suggest disabling it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Problem is I rely on GMAPS and Naivgation, will disabling location services make any difference to me using Sat Nav etc?
If it does, I need it on as SatNav is my saviour.

Wilks3y said:
Problem is I rely on GMAPS and Naivgation, will disabling location services make any difference to me using Sat Nav etc?
If it does, I need it on as SatNav is my saviour.
Click to expand...
Click to collapse
its the "GPS satellites" coupled with data transfer and high CPU usage that makes it over heat everyone has this issues im afraid they only real way I've found to stop it from overheating is to disable 2 cores.

treebill said:
its the "GPS satellites" coupled with data transfer and high CPU usage that makes it over heat everyone has this issues im afraid they only real way I've found to stop it from overheating is to disable 2 cores.
Click to expand...
Click to collapse
Ahh so I'll still be fine using Navigation then?
Weeeee

Wilks3y said:
Ahh so I'll still be fine using Navigation then?
Weeeee
Click to expand...
Click to collapse
Should be, you should try using an offline map (google navigation can save areas of maps) that way you can use just satellites without mobile network.
Sent from my HTC One X using xda app-developers app

Barometer Broken?

My Barometer doesn't seem to work. It always reads as 1010.9 hPa, which is basically sea level. Since I am at ~3500ft it should not read this. I checked it with CPUz and Pressurenet, both read the same.
Just wondering if anyone else has this problem, or I need a new phone.

Bump, can anyone please test theirs?

Roadhog2k5 said:
Bump, can anyone please test theirs?
Click to expand...
Click to collapse
I'm at 5030 feet. Mine says 1010.7.
That's 29.90 inHG. I just looked at the local observation and it shows 29.95.

usmaak said:
I'm at 5030 feet. Mine says 1010.7.
That's 29.90 inHG. I just looked at the local observation and it shows 29.95.
Click to expand...
Click to collapse
That would be 1012.5 hpa according to wolfram alpha. Mine has read 1010.9 since day 1.
My local weather station is reading 1026 hpa. Phone still at 1010.9 lol. So I think it's broke.

Roadhog2k5 said:
That would be 1012.5 hpa according to wolfram alpha. Mine has read 1010.9 since day 1.
My local weather station is reading 1026 hpa. Phone still at 1010.9 lol. So I think it's broke.
Click to expand...
Click to collapse
Or the app is not working correctly. I will keep an eye on mine, and see if it stays stuck. It could just be a coincidence that the pressure in my area happens to be really close to the reading that I'm getting.

Mine appears to be stuck as well. Though the pressure has gone up here, the app is reading the same value that it did yesterday.

usmaak said:
Mine appears to be stuck as well. Though the pressure has gone up here, the app is reading the same value that it did yesterday.
Click to expand...
Click to collapse
That pretty much confirms it then. Hopefully just no software supports it yet is all.

tested about all the current ambient temp apps with barometer and they all appear to be broken and need updates.

Newest update to Pressurenet supports the Barometer!
EDIT: And now it is back to not working again. Odd :|

what about ambient room temp?

Try Accurate Barometer. Make sure you have GPS enabled so it can adjust for altitude.

Redapple63 said:
Try Accurate Barometer. Make sure you have GPS enabled so it can adjust for altitude.
Click to expand...
Click to collapse
I gave that app a try. It got my location and altitude 100% correct. It gave me a pressure reading of 1312.6 millibars. I'm now dead.

Forgive my ignorance, but what good it the barometer reading?
I know if it's going up or down it s used in predicting rain, but my weather widget just gives me the current rating without trend changes.

Mine seems to be working.

jmartens8 said:
Mine seems to be working.
Click to expand...
Click to collapse
I tried a lot of apps. They all give me the same reading, when adjusted for altitude. Unfortunately, my pressure is now reading 1309mb. Weird thing is, my wife's phone has the exact same altitude and temp, and it is reading 1215mb. It doesn't seem like a whole ton of thought went in to this barometer. Oh well, the barometer on my S3 was just as crappy.

I have a weather station at home and my phone barometer is always in line with that. You may have a defective barometer. Sorry...

Redapple63 said:
I have a weather station at home and my phone barometer is always in line with that. You may have a defective barometer. Sorry...
Click to expand...
Click to collapse
No doubt. Just not sure if I should care. It seems like I'm not the only one with a stuck barometer.
I'm past my return period. So I guess that there's really nothing that I can do about it.

usmaak said:
No doubt. Just not sure if I should care. It seems like I'm not the only one with a stuck barometer.
I'm past my return period. So I guess that there's really nothing that I can do about it.
Click to expand...
Click to collapse
Verizon has a warranty. They will replace your phone. The only downside is you get a refurbished phone, not a new one.
-Wizzle

Roadhog2k5 said:
My Barometer doesn't seem to work. It always reads as 1010.9 hPa, which is basically sea level. Since I am at ~3500ft it should not read this. I checked it with CPUz and Pressurenet, both read the same.
Just wondering if anyone else has this problem, or I need a new phone.
Click to expand...
Click to collapse
I'm confused so please humor me. Is there a temperature sensor and barometer in our phones? If so, is there a native app that utilizes it? If not, why would they include the sensor but no real way to access it appropriately? Thanks in advance

For a defect I think he would get a new one, especially in the first 2 months.

Help, extreme draining

Hi, i bought one moto z play, almost 2 months ago, and the battery was excellent, you can see on airplane mode, idle, not using it, the phone lates more than 17 days, and had 23% of juice left, after that, i boight another one, both are used, but this one, only last 2 days on the same conditions, airplane mode, even safe mode, not using at all, just 2 days, drains like 2% per hour without even touching it at all, what can i do?

What does it matter what happens when you never use it? And why buy a second phone if you already have one that lasts great?
Just sell the second and start using it like normal people. Nobody can tell you why that difference is and it doesn't matter. They have to last under normal conditions, but what you are doing is pretty much waste of battery. Letting it lie around in airplane mode for days is simply stupid. Then you could just turn it off

Artim_96 said:
What does it matter what happens when you never use it? And why buy a second phone if you already have one that lasts great?
Just sell the second and start using it like normal people. Nobody can tell you why that difference is and it doesn't matter. They have to last under normal conditions, but what you are doing is pretty much waste of battery. Letting it lie around in airplane mode for days is simply stupid. Then you could just turn it off
Click to expand...
Click to collapse
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.

dandrumheller said:
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.
Click to expand...
Click to collapse
Exactly, it was just a test, obviusly under normal conditions the drain Is Worst, only 3 SoT and 9 hours of battery, if you compare the two phones, one drains 2% and the other 0.1% por hour, that it's not normal.

If is not hw issue, something is draining battery in background. Have you tried factory reset? Compare settings on both phones, wifi/bt scan, SIM is inside on both, sd card?
Anyway, try to make both phones exactly the same from hw and sw perspective. If you haven't already.
Sent from my XT1635-02 using Tapatalk

Maybe put a CPU monitor app on both phones, let them both run in the same condition for the same time period, and see if the histories match? Not really sure how else to look, since you said safe mode didn't fix it.

Zeljko1234 said:
If is not hw issue, something is draining battery in background. Have you tried factory reset? Compare settings on both phones, wifi/bt scan, SIM is inside on both, sd card?
Anyway, try to make both phones exactly the same from hw and sw perspective. If you haven't already.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
the one with the problem has the december patch update, the good one, the november patch, thats the only difference on both. already tried factory reset, wipe cache, safe mode, even on safe mode, the 2% per hour draining persist.

dandrumheller said:
Maybe put a CPU monitor app on both phones, let them both run in the same condition for the same time period, and see if the histories match? Not really sure how else to look, since you said safe mode didn't fix it.
Click to expand...
Click to collapse
gonna FDR both, charge them to 100% and let them dry for a couple of hours with the cpu monitor.

kmry said:
the one with the problem has the december patch update, the good one, the november patch, thats the only difference on both. already tried factory reset, wipe cache, safe mode, even on safe mode, the 2% per hour draining persist.
Click to expand...
Click to collapse
You can try to upgrade good one to December patch to get the same batter life result
If there's no other difference, then looks like that is hw problem. But I'm still suspecting that you are missing something.

Zeljko1234 said:
You can try to upgrade good one to December patch to get the same batter life result
If there's no other difference, then looks like that is hw problem. But I'm still suspecting that you are missing something.
Click to expand...
Click to collapse
good joke, but im not gonna take that risk; cant think what i would be missing; i think ive tried everything except for a downgrade, but i read somewhere it cannot be done, the phone is on 7.1.1.

kmry said:
good joke, but im not gonna take that risk; cant think what i would be missing; i think ive tried everything except for a downgrade, but i read somewhere it cannot be done, the phone is on 7.1.1.
Click to expand...
Click to collapse
Do not downgrade. It is doable but next upgrade (OTA) and you will end up with brick.
I've already asked you, both phones are with/without SIM/sd card?

Zeljko1234 said:
Do not downgrade. It is doable but next upgrade (OTA) and you will end up with brick.
I've already asked you, both phones are with/without SIM/sd card?
Click to expand...
Click to collapse
both phones on airplane mode, without simcard, without sd card.

kmry said:
both phones on airplane mode, without simcard, without sd card.
Click to expand...
Click to collapse
Well, if both phones are the same from hw and sw perspective (except update on "bad one") then most probably cause is hw or update.
Do not try to downgrade, 8.0 is under SOAK (quite long already, but still has issues) and you may try it when is ready (don't flash leaked SOAK, please).
As said above, most likely is hw issue. Sorry for that.

camera app left running?

dandrumheller said:
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.
Click to expand...
Click to collapse
KrisM22 said:
camera app left running?
Click to expand...
Click to collapse
All apps were closed.

kmry said:
All apps were closed.
Click to expand...
Click to collapse
Your second pic says it's running. Sorry if I misinterpret.