Related
I recently acquired two NS phones, one for wife, one for me. After playing them for a few days, I found the compass is not working for both of them,even after the calibration. They point to everywhere but the right direction.
I came from Samsung Vibrant, the reason I switched was because Vibrant has bad GPS and defective compass, which really bothered me. Now after the jumping, I found NS has the similar compass problem...
Can Samsung really make a working phone?
Maybe you got a bad one, I came from the vibrant a month ago and I'm hooked. Everything works and never going back to a non nexus phone ever. GPS works perfectly and locks in less than ten seconds. My first one was a dud so I got exchanged. If you're not happy than demand to be satisfied. Do it!!
Sent from my Nexus S using XDA App
I gave up on my compass, too. It rotates with the phone... Not completely anyway, but the display is nearly completely independent from magnetic north. I think the sensor value may be computed by something like
Code:
north = sha1(/dev/urandom + /dev/accelerometer);
On a more serious side note: We have some metal parts in our phones. If one close to the magnetometer sensor is only slightly magnetized, that would likely seriously impact compass performance. Unfortunately, there is neither a (simple) way to find out, whether it is so, nor a (simple) way to fix it.
since I acquired the two NS phones from two independent channels, now both of them showing bad compass, I'd suspect this is something systematic.
I'm surprised to see so little echo on this issue...
coolmib said:
since I acquired the two NS phones from two independent channels, now both of them showing bad compass, I'd suspect this is something systematic.
I'm surprised to see so little echo on this issue...
Click to expand...
Click to collapse
I just checked my compass on my NS and it seems to be real close to pointing north.
I had a G1 before and the compass would occasionally get stuck and give inaccurate readings. To fix that I would shake the phone vigorously like I was trying to take the fizz from a soda bottle and that would make the compass work properly. However I don't think that that is a problem with the NS.
The compass points wherever the point of gravity is. North is always facing down for me for some reason but gps status seems to work, but not entirely accurate.
Is there still no fix for this issue?
I often have to do the figure 8 when I want the compass to point north. Normally this works for me.
Seems like it was a rom issue. I had the newest cm rc1 and north was pointing wherever the ground was. I just returned it back to rooted 2.3.4 stock and seems to work fine, except it's shaky now.
EDIT: There is the "Compass" app that still points down, but google map and the other compass apps works somewhat fine (still shaky and about 10-15 degrees off or so)
I wonder is it pointing TRUE north or MAGNETIC north? Where I live there is almost no declination however some areas are +-15 degrees.
For my case in the original post, both phones are running the stock ROM of 2.3.4 (unrooted). I tried several compass Apps from the Market, none of them pointing to the right direction.....I wonder if it's a hardware problem.
coolmib said:
For my case in the original post, both phones are running the stock ROM of 2.3.4 (unrooted). I tried several compass Apps from the Market, none of them pointing to the right direction.....I wonder if it's a hardware problem.
Click to expand...
Click to collapse
Try using "Smart Compass" if you search for "Compass" in the market, it's usually the second one from the top.
koyanishi said:
I just checked my compass on my NS and it seems to be real close to pointing north.
I had a G1 before and the compass would occasionally get stuck and give inaccurate readings. To fix that I would shake the phone vigorously like I was trying to take the fizz from a soda bottle and that would make the compass work properly. However I don't think that that is a problem with the NS.
Click to expand...
Click to collapse
I have experimented a bit more with NS compass and have to agree that its accuracy is random - occasionally it will point north but more often it will be off by 10 to 20 degrees.
SovereigN7 said:
Try using "Smart Compass" if you search for "Compass" in the market, it's usually the second one from the top.
Click to expand...
Click to collapse
Just downloaded and installed "Smart Compass"。 Same problems persist...
try the compass built into the mapping app Locus. Best compass i've found yet.
coolmib said:
For my case in the original post, both phones are running the stock ROM of 2.3.4 (unrooted). I tried several compass Apps from the Market, none of them pointing to the right direction.....I wonder if it's a hardware problem.
Click to expand...
Click to collapse
Yes I think it is a hardware problem.
While researching a problem I have with NFC reading tags I cam upon this gem from this tread
http://forum.xda-developers.com/showthread.php?t=905512&highlight=nfc+-reading+tags
And chadrockey had this to say in post # 1 of that tread.
chadrockey said:
So I've been noticing that my compass would always misbehave (in terms of accuracy, not stability a la Sky Maps). I would get a pretty large static error (30 to 40 degrees obviously not declination); rotations would not be consistent (IE, a 180 degree turn would yield 100 degrees change.); and the magnitude of raw measurements was not like that of the magnetometer I got from Sparkfun.
Turns out the neodymium magnets I had near my desk actually latched onto my phone and magnetized the NFC antenna. I tested this by removing the cover and putting the magnet near the antenna and it sticks. Without the cover on, the compass worked much better.
I've mostly demagnetized my NFC antenna now by doing some magnet sweeps and leaving it near the heater, but I've learned to keep the magnets away.
If anyone is having problems with the compass overall accuracy, removing the back cover may help.
Click to expand...
Click to collapse
Now I never, as far as I know, have had strong magnets near the nfc antenna, but the nfc app does not read nfc tags so it could be that it is magnetized.
But if I take the back cover off my NS as chadrockey recommends, then the compass reading will be spot on.
oh, and btw, the best compass app that I know comes from swiss army knife which is one app containing a number of other neat apps
I have the same problem with my nexus s compass, north is not accurate ever and augmented reality application like streetview defect because the compass seems to vibrate, even if I have my hand stable the screen vibrates like I'm shacking the phone...
walker7373 said:
I have the same problem with my nexus s compass, north is not accurate ever and augmented reality application like streetview defect because the compass seems to vibrate, even if I have my hand stable the screen vibrates like I'm shacking the phone...
Click to expand...
Click to collapse
did you try using the compass without the case back cover?
tried removing the back case, compass still not working
I gave up my compass a couple of weeks after i got the phone. Shakes like a drug addict and the accuracy is worse than a blind guy trying out sharp shooting for the first time.
Ive removed the back cover, tried different apps and "calibrated" the compass multiple times but to no avail.
Join the club. The compass is a failure and google is not fixing, or not able to fix it.
Sent from my Nexus S using XDA App
I have a Verizon Samsung Galaxy Nexus LTE, rooted running Android 4.0.2. I recently noticed (while playing Doodle Jump) that my accelerometer was slightly off. If I held the phone straight vertical (or laid it flat) the doodle would move to the left. In order to play properly I would have to lean the phone to the right to compensate. I tested this again with two different gyroscope apps. It's off by about 4 degrees (not terrible but enough to be obnoxious). I also used the in-app calibration option which fixed the problem, but only for that app. I re-calibrated my compass to no effect and did a factory reset to no effect. I don't know is this problem existed before I rooted as rooting was the first thing I did.
I'm unsure whether this is worth sending the phone back over (I can re-lock my boot loader if needed). Or if I did, would they even take it back for such a small issue? I've had the phone for about a month now. I would much prefer some sort of software fix. I understand that certain phones had global calibration options in the past. I have root access and am open to some hacking.
Any help is appreciated.
With all these smart people around here, nobody has any suggestions?
The Galaxy Nexus forum is this way:
http://forum.xda-developers.com/forumdisplay.php?f=1336
Yours wouldn't be the first with accelerometer issues.
Greetings all. I'm not convinced my problem is specifically related to the One S, and I certainly haven't got anywhere near rooting yet, but you Guys are expert at nosing round in the bowels of this phone & the OS, and I'm getting totally flummoxed as to where I've gone wrong.
I've owned this phone since June and it was originally locked to O2, was unlocked and used on Giffgaff, an O2 offshoot - probably irrelevant. One of the apps I particularly wanted to use was Google Sky Map, duly installed and run successfully for a day or so. Other apps installed, as one does, but when I came back to Sky Map, the app was frozen, as were seemingly all compass function apps.
Various uninstalls & reinstalls later, a system reset and a factory reset and this function still was inactive. Returned to HTC for fixing. No better - all worked OK for a short while then stopped. Returned again and this time internals were swapped ,but now the microphone wouldn't work. Third return and an unlocked sim-free handset was returned.
As soon as I loaded my profile from Google, initially it worked, but later most of the sensors again seemed to fail. I've tried the full factory reboot then logged in with a totally new Gmail account, but no change. Phone Tester app shows only readings from proximity and light sensors - no gyroscope,compass, mag. field or accelerometer. Accelerometer did show one set of readings this morning, but nothing since. Lookout AV has always been installed. Incidentally, almost exactly the same profile worked perfectly well on my previous phone, a Wildfire S.
Should I shoot myself or the phone? I admit I'm not any sort of phone expert, but I don't think I'm that dense as to so consistently screw this thing up.
Any ideas people please, in (moderately) simple terminology?
Ok maybe you could shoot google, maybe its a fault by them.
If I helped in anyway please hit thanks
Thank you for the oh-so-helpful response.
Just in case one of the myriad readers of this thread should have just a quiver of interest ................. I believe I've found the answer.
It's always been difficult to pinpoint the problem, and certainly HTC haven't twigged what's happening, as before I sent the phone back to them I TOOK THE FLIP CASE OFF!
That's why it would work for a short while after return, until I replaced the case. I can only guess there's something like Carbon Black in the plastic back shell, and that's what's been interfering with the sensors.
It may also be relevant to the big Home Button problem, with the screen flipping between Home & Helicopter views. Has anyone investigated whether there could be sufficient signal degradation to trigger this problem caused by the use of a case?
Sweetness and light to all.
I spoke to an HTC rep, and he said they would not give an unbranded handset back. If that's the case, I want my phone unbranded. I'll take it to them and hopefully get an unbranded one.
Well good for your HTC rep. They can't go giving out unbranded sets like that. What is the World coming to?
Notwithstanding - the previous clutter of O2 apps was pleasantly noticeable by its absence as was the O2 splash screen.
What a lucky little customer I am and it's only taken 4 months to sort out.
I remember somewhere somebody reported issue with compass in our Relay.
Now I found that it is somehow related with other sensors and/or modules.
So if your compass not working properly turn off wifi, data transfer and GPS and try.
Regards
Mac
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
for me also no difference, however i try, google maps with gps is usually going sometimes ok. havent got the clue behind yet
Jax184 said:
Makes no difference for me. Everything on or everything off, the compass is still hopelessly miscalibrated after a reboot. Then a calibration cycle gets it approximately right until the next one.
Click to expand...
Click to collapse
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
gee one said:
I'm in the same boat- if I'm driving, it will correct when it uses the GPS, but standing still, it will be off. I think the issues started after updating one of the stock roms. I think the original stock rom was just fine.
I think Nardholio posted something about going back to stock, ripping the battery out with a solid GPS lock and then upgrading.
Click to expand...
Click to collapse
That's only needed if your GPS is totally inoperable.
So the Relay 4G has horrible GPS? Seems to be an ongoing theme with Samsung phones.
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Jax184 said:
Nah, the GPS works fine. It's the compass that's broken.
During the development of our CM rom, it was discovered that the GPS sometimes wouldn't work at all after flashing a custom ROM. This was because the stock ROM had put the GPS to sleep in a way which the custom ROM couldn't wake it from. That's why the battery pull technique was developed. It ensured the GPS was active when you installed the custom ROM.
I don't know if it's still needed or not. I don't think it is. If it is, it would only help you if your GPS doesn't work at all after flashing a custom ROM. If it's intermittent or has poor signal or something, you've got other problems.
Click to expand...
Click to collapse
I...don't know the difference between the GPS and the compass. I thought people were using the terms interchangeably, but apparently not.
Solkan said:
Regarding GPS, if I understand correctly, Relay 4G uses both GPS and GLONASS signal, so is the GPS fix considerably quicker than in devices without GLONASS and is the satellite coverage better as well?
I'm particularly interested if there is a noticeable difference in this regard between Samsung Captivate Glide's GPS and Relay 4G's GPS+GLONASS.
Click to expand...
Click to collapse
Okay...this is very interesting. Differences between GPS and compass aside, this still seems like good news. At least to me, cause GPS is very important to me, and its my understanding that the Captivate Glide's GPS is very hinky. Seems like if you stick with stock you'll be fine. Now, bluetooth, I have no idea how the bluetooth is on the Relay (stock or custom ROM), but at least the GPS is good and even better with this GLONASS.
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Jax184 said:
The compass is a standalone chip that detects the earths magnetic fields and tells the device which way it's oriented. But Samsung screwed something up, and every time the phone boots it's way out of calibration. You can fix it by taking it through a quick calibration cycle, and then all's right with it until the next reboot.
The compass and the GPS work together for things like maps. With the compass miscalibrated, the indicator on the map will often show that you're facing a compass direction other than what you really are. And it'll sometimes act as though you're walking backwards when moving at low speeds. But the actual GPS position and tracking are correct, it just has no idea what way you're facing. Again, a compass calibration will fix this.
Click to expand...
Click to collapse
Okay...I've actually been experiencing that lately with my Epic 4G on Cyanogenmod, but I blame that more on the most recent update of Google Maps which changed the entire interface than I do the ROM (I'm on the most recent stable release and before the Google Maps update GPS worked perfectly). But that's still something I'll save for that board. But what you described is exactly what I've been experiencing, the Navigation seems to work, but it takes a while for the indicator (the red arrow) to face the right direction. Since I use it to drive around my own town its not that big a deal, but if I ever go out of town, yeah it could be an issue.
Someone on one of the Relay 4G boards here opened up his Relay 4G and showed exactly where the metal components are, and how with some tweaking it may correct it without calibration...but with my luck I'd break the thing permanently.
I do wonder why the Relay 4G is like this...my only guess is that Samsung was trying to rush it out and didn't have the time to properly test it? I know it was supposed to be called something else (Blaze Q or something). But the funny thing is, even with this "error" (which from the sounds of it is easily remedied), it still seems like more of the spiritual successor to the Epic 4G than I originally thought the Captivate Glide was, or at least an Epic 4G if it was GSM. 5 rows of keys, same shape...I just don't know why this phone isn't more successful than it is. At least you can get it on eBay, new, for about $200-$300. I haven't been inside a T-mobile store in years so I don't know if they regularly keep them in stock or not. But its still available. That Captivate Glide is still available for less than $200, but with its issues with GPS and bluetooth...I don't know, seriously thinking about this phone now.
Anyway, thanks for the response. And by the way, how is the bluetooth on this phone?
EDIT: Herp derp, it was YOU who opened up their Relay 4G! My apologies, sometimes these boards blur together.
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Jax184 said:
Bluetooth seems okay, but I only have one bluetooth device, so I'm hardly an expert.
The guys working on our CM ROM are trying to improve performance when both wifi and bluetooth are in use at the same time. Since they're both 2.4 GHz, they tend to step on each others toes if both are on at once.
Click to expand...
Click to collapse
Ah okay. Though I can't remember the last time I tried to use both at once. Also, since the Relay 4G actually has a stock JB rom, what benefits would there be getting CM instead? I'm only on CM for the Epic 4G because Samsung/Sprint stopped updating it with Gingerbread.
You should try a compass calibration on the Epic to see if that helps with the pointer. First step away from large metal and electrical objects, so you're in a fairly clean magnetic environment. Then open up an app that uses the compass, like Metal Sniffer. Then, while keeping the screen on, slowly and smoothly rotate the phone 3 times around each axis. End over end 3 times, then side to side 3 times, then around and around 3 times.
At the end of it, the pointer should now point north.
Click to expand...
Click to collapse
Thanks. The folks on the other board said it was an issue with the updated Google Maps app as opposed to the GPS/compass itself, and suggested a downgrade. I may try both solutions, though to be honest with you there's a huge learning curve with the most recent update to Google Maps (for instance still can't figure out how to get it to record my current location, which came in handy with the previous versions if I ever came across a place or store I wanted to visit again).
On the Relay, the values of the magnetic field strength are all totally out of whack before you do this, and they suddenly drop to more rational levels after the calibration.
Click to expand...
Click to collapse
Speaking of that calibration trick, where is it described in detail around here?
EpicMikeNC said:
Speaking of that calibration trick, where is it described in detail around here?
Click to expand...
Click to collapse
That was it! :laugh:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Jax184 said:
That was it! :laugh:
Click to expand...
Click to collapse
Oh. lol Ok, thought what you described for the Epic 4G was different, not the same. Gotcha. :good:
The CM ROM is faster and trimmer than the stock ROM, and fixes a couple of bugs and annoyances. No touchwiz interface, no t-mobile tethering lockout, no samsung bloatware. And while it does have a few bugs of its own, it's under active development by several people, so it's rapidly improving.
Click to expand...
Click to collapse
Well I know from my experience with the Epic 4G, you can remove the bloatware with Titanium backup and tether via an ap (if you mean hotspot tether). But at least there's options, stock or CM.
Still don't get why this phone isn't more successful than it is.
Compass is wacky on mine
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Bobby Tables said:
On my Relay, the compass is off in bizarro land, and has been since I bought it. Stock ICS/unrooted, or stock JB/unrooted, same problem. It doesn't seem to hold calibration at all, and I can even notice that it very slowly spins as I drive. On those times I've tried Google Maps 7 (yuuuuck!), I've noticed that it cheerfully ignores your GPS heading and points the arrow to your alleged compass heading. Between the large amount of change-for-change's-sake UI stupidity, the compass problem, and its general crashiness, I've ditched the update and gone back to the original version.
I've just rooted it yesterday, but I seriously doubt that rooting would make any difference with the compass.
Click to expand...
Click to collapse
How did you root by the way? One-Click?
But yeah, based on what you just said, I'm convinced its the update, not the compass. I don't understand how Google went backwards in regards to this so-called update to Google maps. But the Metal Sniffer solution seems to work, 9 times out of 10 anyway.
Also, I keep looking and looking, but unless I'm still missing it, didn't the update take away to ability to save your current location?
The bootloader is unlocked, there is no reason to run a rooting script. Just flash CWM with Odin/Heimdall and then supersu
I'm having a very similar experience here on CM 10.2 nightlies. Calibrating the compass doesn't always work. When it does it doesn't always stick. And when it sticks, it will be very jumpy, skipping from one direction to the other at random. This prevents compass mode in Google Maps, so it's annoying but not such a huge deal.
so prior to being on venom 4.2, i was on venom 3.xx. i had no problems prior.
i flash 4.2, and had no problems related to the camera not working. i had other problems though, after reflashing 4.2 those problems went away, but now a new problem came up.
after a restart, i can use the camera maybe once, or take one photo. after that, the screen through the camera will be frozen on screen. i can still take pictures, but it will only be off what is on the screen. after closing the camera, or force closing it,upon trying to open the camera app again, it barely loads, then force closes automatically and i get an "unable to start camera" bubble on screen. i can see only the grid outline of the camera, off center and such very briefly ontop of my wallpaper.
i can do a reset on my phone, and resume taking pictures, sometimes i am fine to continue, other times its the same problem. this is a very common recurring problem for me.
looking at my apps, i see 2 cameras installed, one is the new 5.0, and the other is the old 4.xx camera. i have frozen the 4.xx camera before through titanium, and it doesnt fix it. should i uninstall the 4.xx camera altogether?
subsequent reflashing of this rom doesnt fix this issue. and i dont know what else to do rather than reflashing the rom from a blank slate. previous reflashings have been on top of the current rom.
i would rather not have to start new as this phone has crappy amoint of space, and i cannot back up all my apps and settings.
i dont know if it is kernel related. prior to 4.2 i was using elemental x, after 4.2 i switched to beastmode since i wasnt soff.
is there perhaps a way i can manually start the camera through root browser?
If you've got both versions of camera in your app drawer I'm guessing you dirty flashed the ROM, which has most likely caused your problems. Clean flash the ROM and see if it fixes your issue. This is why I'm totally against dirty flashing anything.
I don't understand how you don't have space to back up your apps, I have a backup of every app I've ever used and still have tons of space left over. The fact that you mention backing up settings troubles me, restoring system settings after flashing a new ROM will more than likely cause problems for you.
When you're flashing a ROM don't do it the lazy way, do it the right way, perform a full wipe (cache/dalvik cache/factory reset/system) and start clean. It only takes a few minutes to setup your ROM from scratch. Restore your apps but don't restore any system data.
Sent from my Evita
thanks for the reply.
as suggested, I did a complete reset. wiped the caches, factory reset, and system reset.
installed from scratch. But i am still having the camera issue?
now its just not loading at all. black screen, then close. no error message. and no unable to start message.
could it perhaps be a hardware issue at this point?
without restoring anything, under apps, I still see two instances of the camera app. one at 5.1, and one at 4.2.2. can anyone confirm this is normal?
the only thing out of the ordinary, within the past few months, my phone has been getting crazy hot at times. specifically right below the lens of the rear camera. I was getting this heat from charging, or even certain apps. Definitely attribute that to the age of the phone. as apps that ran smooth when the phone was new, no longer are so.
I dont know if the heat can cause hardware damage?
also, not sure how relevant this is in the context of my situation. but apps that use the camera do not work either when the camera is needed, such as snapchat and instagram.
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
timmaaa said:
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
Click to expand...
Click to collapse
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
chinaman_chong said:
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
There's nothing wrong with this phone. Given the right amount of knowledge and care the thing doesn't skip a beat. Even though there is no such thing as a soft brick (a phone is either bricked or it isn't), whatever it is that people experience in those so called "soft brick" instances is caused by user error 99% of the time. I've seen it time and time again.
Any phone available on the market can experience any amount of issues if it isn't handled correctly. You got unlucky and your camera is most likely shot, but any other problem you've encountered comes with the territory of flashing unofficial firmware and software, it isn't anything wrong with the device itself. These are possibilities you need to be comfortable with if you're going to modify your device.
Yea, I assumed there were gonna be risks when I rooted my phone. Dont know if any of the issues I had were related to rooting or not.
The soft brick scare I had was due to a flash that went wrong for no apparent reason.
another update on my phone. I noticed my front facing camera has no issues whatsoever. unluckily for me, I cannot even access my camera, to toggle to the front facing camera to even attempt to check it out. Instagram also does not allow me to switch either, it just gives me an error saying it cannot connect to a camera, then closes. snapchat's rear facing camera is just a black screen for me, but it doesnt force close, so I am able to toggle to the front camera, and it works just fine.
is there a setting or something I can modify, for now, so the front facing camera is the default?
my brother's one x recently went out this year too. I am gonna try to salvage his camera, and see if it will fix my problem.
I have not taken apart this phone yet, is the camera soldered or held in with connectors?
Have you tried an RUU yet like I previously suggested?
Sent from my Evita
chinaman_chong said:
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite.
Click to expand...
Click to collapse
If a couple hiccups and scares are too much for your, then it might be that modding phones is not for you. These types of things happen time to time to even those experienced with flashing ROMs. Occasional setbacks and troubleshooting is just part of the game. If that is too much for you, than don't play.
As timmaaa already mentioned, failure to boot is not the phone's fault; and its almost always a matter of user error and not following the procedures properly.
chinaman_chong said:
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
Random software errors like random rebooting, overheating, etc. are often easily remedied with the proper steps. They are likely not issue with the phone itself, but rather a result of improper steps while flashing the ROMs. I've flashed many ROMs on this device, and have never suffered any such issues that I couldn't solve easily.
As for your other complaints about the phone (lack of expandable memory, why you didn't choose another phone), I don't know why you even posted them, as they are not constructive. Those still on this forum are mostly here because we love the phone and remain loyal to it. Your comments aren't going to help your issue, and will only annoy fans of the device. Better to keep such comments to yourself.
If you hate the phone so much, go buy another one and be done with it. But crying about it isn't going to solve anything.
I would suggest you follow timmaaa's advice, and flash the appropriate RUU to "start over". S-off is highly recommended before RUU, as running certain RUUs with S-on and SuperCID will brick the phone.
I have the same device and the same problem.
It doesn't depends of firmware or kernel or camera app..
I thought it's hardware problem but it is not. Because i was changing the camera module and it doesn't helps((
Don't know what to do with this issue(