Hi all. I humbly request the knowledge of the ancients! I have rooted my HTC One X and I installed the regular CM11 on it. Due to the power drain bug I reverted to CM10.
However, since then my light, gravity and other sensors have not worked at all. Sensor box reports no activity. From Googling I think my problem is a known bug with low hboot versions, but when I run Cid checker I get no Cid back so I am unsure how to go about upgrading my hboot
I have tried various fixes found on the google, such as overheating and crashing the phone to no avail. If there is a way to fix it without a system wipe I would prefer it but if it is unavoidable I can live with that.
I thank you all in advance for any and all help given!
Bumping.
Related
EDIT: SOLVED!!!! it was a usb brick. see last post for details.
hi all,
I have a problem with my desire.
Bluetooth won't turn on. If I try to enable BT, it says grey'ed out for like 10 secs and the goes back to unchecked.
I got this device used so I don't have many background information. All I can tell is I tried different ROMs and wiped all I could, but still no luck. I actually highly suspect this might be an hardware issues, but I'd really like to try everything before shipping back to assistance.
Here are my current specs:
htc desire amoled
bravo pvt1 ship s-on
hboot 0.80.0000
radio 5.11.05.27
rom cyanogenmod 7.1.0
kernel 2.6.37.6-cyanogenmod-geb50077
Recovery: Clockworkmod
ANY hint highly appreciated.
Got exactly the same problem.
BT worked while running the former stable CM release. I first noticed this issue when flashing latest CM. You tried other ROMs which didnt work?
Did you try other Radios as well?
I am not an expert, but I think it could be a problem of the radio. I never totally understood what the radio does, so could anybody help with this guess? I never changed Radio as there was no need for (never touch a running system).
lexo, did you try rolling back to 7.0.3 to see if BT would work again?
I was also thinking about radio, exp b\c it seems to not be a ROM-specific issue, as I have tried several: LeeDroid, InsertCoin, MIUI, as well as a stock rom.
I believe the point with radio is not necessarily about having the latest, but finding the one that works well with one's rom. Also, there is RIL, but that I don't know what it does.
No, didnt try that yet.
I use BT in my car to listen to music only so I didnt notice the issue at first. Now i am thinking about buying Galaxy Nexus, so I am not too exited about that point. But as I am willing to pass my Desire to my lil sister I would love to have it fixed.
Whats "RIL"? Think I never heard about it.
Don't know if this is relevant but had a similar problem with Bluetooth, wifi and Mobile data yesterday. None of them had connectivity!
The remedy that worked for me was to wipe the cache and dalvik, reflash CM7.1 via recovery (but remember to also flash the Google apps package) and soft reset.
No data is lost this way.
Hope that helps!
Sent from my HTC Desire using XDA App
This may not be relevant but when I couldn't enable Bluetooth on my done when I have a USB brick.....
Try the USB brick fix it may work
Sent from my HTC Desire using XDA App
update:
so far I did:
- wiped everything including dalvik and reflashed cm7 - no luck
- removed files in etc/bluetooth [read somewhere] - nuthing
- applyied a .zip update that is supposed to fix a possible USB brick - no change.
@LEXO: I think you might try the first two things I did, in your case they might work.
So now I flashed a RUU Rom and reverted to stock s-on bootloader, hboot, radio (ril, too, I believe, though I dunno how to tell ril version) and recovery.
The only thing I'm not completely sure about is the USB brick fix, but otherwise it's ready to ship to assistance.
@Reaper, can you point me to the USB fix you referred to?
guys!!! Thanks everyone, expecially reaper.
My BT is working again!!! turn out it was a USB brick, which I was able to solve fairly easy.
I had tried a usb brick fix that involved flashing a .zip, which I did. However still no BT changed so I assumed phone was not bricked after all.
Also, I always assumed usb brick would involve major cd and usb connect malfunctions, and that was not my case at all.
However it must have been that fix that didn't work, because I then followed the guide on this forum http://forum.xda-developers.com/showthread.php?t=691639: got my CID via fastboot, modified the files accordingly, put them on sd card, got temp root with visionary, issued the necessary commands with "free root system tool" terminal, rebooted, and voilà! BT is finally green.
I can't believe I made it!
Hey all,
About a year ago I got a new DHD everything was working fine. I rooted it (using visionary), tried cyanogen mod, went back to the original sense/frayo backup and finally installed a new kernel (Buzz)...
After that my proximity sensor stopped working, I kind of just put up with it because I was busy at uni, I just got used to manually turning my screen off. I thought it was something to do with the kernel and/or backup I was running. Since then I have installed Android Revolution 6.3.1 with new kernel and radio and thought it might just start working again but it hasn't...
My question then is:
Could I have done something to affect it while flashing/rooting e.t.c?
Is there any way I can check?
Is it likely to be a hardware failure? (the phone was less than a month old when it stopped working)
oh and I have tried Proximity Re-calibrator and it dose nothing (Unless it doesn't work with ARHD 6.3.1).
Thank you for your time.
This is a common problem. It's in the faq of the ARHD rom and the answer is:
http://forum.xda-developers.com/showthread.php?t=951858
SuLuke said:
This is a common problem. It's in the faq of the ARHD rom and the answer is:
http://forum.xda-developers.com/showthread.php?t=951858
Click to expand...
Click to collapse
I have tried and tried Proximity Sensor Recalibrator.... no change.
What did you do in the app? Did you also read some of the posts below the first posts on how to use it? I mean, a lot of people have already posted there that they have all sorts of problems with the sensor. If there is really nothing that helps you I would try flashing at least one more time with wiping everything (btw, did you do a full wipe before coming to arhd?)
Yes used the super wipe as suggested.
I've been holding my finger over the sensor and increasing the thresholds, attempting to get a change, all combinations of the sliders and it just says 'far' continually.
Thanks for replying, sorry if its just that I'm just using the program incorrectly...
Full wipe and re-flash tried everything in Proximity Sensor Recalibrator nothing changes...
Thank you for clicking on the thread.
I've loved my Zenfone 2 for a while now. I have the 64gb 1080p model. It was a well priced powerful phone for what I wanted.
However, I recently received an asus software update that completely borked the Gyroscope and some other sensors. I have read about similar issues online and testing the sensors reveals that they're not working.
Does anyone know how I can fix this? I have been unsuccessful in trying to install CyanogenMod13 or even TWRP/CWM. I rooted my phone and the bootloader is unlocked (white backscreen upon loading).
It seems as though ASUS doesn't want to fix this, would upgrading to a custom ROM provide firmware that would properly recognize and use the gyroscope as input?
I've tried wiping the system cache in the stock recovery, resetting to factory new and everything to no avail.
I am willing to "tip" or "pay" for someone's time if they can help me as I cannot auto-rotate or use any applications requiring certain sensors.
Thanks for your time.
I've upgraded to CM13 successfully now and the gyroscope is still not even recognized in Sensor applications. Is it hardware?
solution?
Last weekend I flashed an old HTC One X I had lying around with This Cyanogen
After a while I noticed location services was barely working.
Using androsensor I saw that, apart from sound and battery, none of my sensors were registering anything (waiting for event, or zero), and GPS saw NO satellites at all. (Sony in at the same time saw 21)
Being my first flash, I was thinking user error, everything else was working but hey.
I tried this resurrection remix, exactly the same result
I went back to old storage layout and tried the latest cm-11 snapshot, no difference.
Since I didn't think of testing the gps & co before flashing, I wanted to try to return to stock rom. but that's not as easy as it sounds apparently.
Backups got wiped while I was trying to get my first flash, and online references and links to tools are mostly invalid now.
I tried an original recovery and locking the bootloader, but got an error running the presumably correct RRU.exem, probably due to the 1.7x HBOOT I have.
There might be a hardware issue, I opened the device to check a dicky USB connector, but don't see any damage.
Finally tried This cyanogen again no difference.
So is there anyone left here with some more experience/insight that can help me get the sensors working in custom rom, OR be able to get me back to stock, so I can test them there.
If you need any more details, just ask.
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- Set up phone, comes with Nougat 7.0. Camera works at first, though seems to have problems with the auto focus. Camera app then updates overnight and stops working. Clear data/cache, remove updates, hard reset - no good. Flashlight does not work either, simply says "loading..." and stays like this indefinitely until closed.
- Factory reset, no change. Switch to safe mode, no change. Decided to unlock bootloader and install custom ROM after hearing that would fix it (I know, I know...I should have just sent it back at this point). Install Viper 5.10 + root with magisk, camera and flashlight still not working. Safe mode, not working. Full wipe in TWRP, RUU back to stock firmware (CID: HTC_034, flashed 2.41.401.3 signed firmware). Set up phone again on stock firmware, still no change in camera or flashlight.
- Install LeeDroid 10 3.7.0 custom ROM, root with magisk. I get a breakthrough here; turning off "OK Google" in settings gets the camera and flashlight working again! Still have the "laser autofocus blocked" issue, but I figure I'll deal with that later. Backed up with TiBu.
- Next day, decide to use a ROM that includes the latest security patches (got a bit annoyed waiting for HTC to push out the European updates, still on 1st January patch) so went for Resurrection Remix. Wipe, clean install etc. Camera stops working again, no change in safe mode. Wipe, clean flash back to LeeDroid, camera is no longer working, in normal mode or safe mode.
- Went through a bunch of custom ROMs at this point; ICE, Dirty Unicorns, LineageOS, then decided to try RR, LeeDroid and Viper again - camera still not working in normal mode or safe mode. With the ROMs that required GApps, used every package in both Open GApps and Dynamic GApps to install. No change to camera, Google Camera was unable to start as well.
- Flashed upgraded RUU (2.41.401.4 signed firmware) and went through the process of wipe/clean install custom ROM/test camera with all the above custom ROMs in normal mode and safe mode. No change in camera, though the ROMs were all excellently made
At this point I'm pretty stumped If it was a hardware problem, why did it work when I first installed LeeDroid, but not after? It's not been mishandled, it's just been sitting on my desk since I got it. The fact that it doesn't work in safe mode would suggest to me that ,maybe, a camera driver has been deleted somewhere along the way? I also tried a load of other methods I found on various message boards; flash it with no SD card inserted, flash without SIM card installed, etc. but absolutely nothing works.
Third party camera apps also don't work; most simply crash on starting. Open Camera says "Unable to access camera. Maybe being used by another app?", so I tried removing the permissions of all apps that had access to the camera except the camera itself - no change. Deleted cache/data/preferences of all apps - no change.
Finally, I had a look at the HTC diagnostics test using *#*# 3424 #*#* on the dialler - the camera test doesn't even show up! :crying:
I've run out of things to try at this point, so I'm posting this here to see if anyone can possibly shed some light on this very strange situation. Is there something I can do to fix it? Or should I start begging Amazon to give me a refund? Unfortunately I'm a week outside their 30 day return window...lesson learned for next time; if in doubt, send it back!
Oops, meant to post this in the Q and A forum. Don't want to spam a duplicate, is it possible to move it over?
Hardware issue. Contact HTC for a replacement. sounds like it may just not be connected. I had one with no working vibration notification, the motor would turn on, you could hear it, but the phone wouldn't vibrate. Got it replaced ASAP! I recommend you do the same!
FinnMacKool said:
Hi all,
I've been having quite a few problems with my month-old HTC 10, specifically with the camera (and the WLAN coverage, but at least that's working somewhat!) I finally unpacked it last week and have spent the whole week since attempting to fix the "Camera has stopped/Unable to connect to camera" problem. The selfie camera, however, is perfect and can be used in other apps, but attempting to switch to the camera on the back results in a freeze/force close. Considering I decided on the HTC 10 because of the camera quality, I'm a bit disappointed so far. A google search reveal a number of people having the same problem, but no real solution. Here's what I've done so far:
- !
Click to expand...
Click to collapse
Same issue here. The only thing that works for me (so far) is flashing back to a Marshmallow rom. HTC has been completely silent on this issue in terms of actually fixing the problem. They know the problem is there for only a small number of us and so aren't going to do anything about it. Fine. This was my first and will be my LAST htc phone. Buh bye htc, you'll never get another dime from me.
Did you fix the issue, coz i have the same in my HTC 10
Hi
follow my post in anildsouza73 blog..I will show how to fix it if someone really spoiled it...have a good day..
from yesterday morning the problem appeared to me. Initially, the difficulty in focusing, then rebooting the impossibility of opening the camera app and the flashlight. I found on Youtube the videos that showed the same problem. Is there a solution today?
Hi all
I found if I cleared my flashlight cache and then the camera cache, soft reset phone I could get the camera working again. Only problem now is the autofocus is not working properly. Any ideas for that?
Same problem. Focus stopped working, then I cannot launch camera app. Anyone found a solution?