Has someone else had a simelar problem with HTC One X? When I check the box on for NFC, it immediately uncheck itself. I had this problem since I updated to JB, already reverted to stock Jelly Bean still doesn't work. On ICS it worked fine, I have also reverted to stock ICS and ARHD ICS and there it also. So it's not broken, there's just somethingwrong with JB by me. But since JB it never had worked. I hope someone could help me. Because a friend of me bought a HTC One and now I would like to use NFC.
Related
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
I don't know but think people either don't know the meaning of stock or I have to learn the meaning
What you described is not stock Rom.and to your answer no I don't get sod.
True. I'm not on stock, I guess I meant to say that my ROM was created from stock. Good to know that someone else is not experiencing this though. Thanks.
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
Click to expand...
Click to collapse
+1
I was having screen freeze while using the google reader app. Had to pull battery.
Am running the same ROM, with battery percentage mod as well. Stock kernel. Not sure why.
possible sleep of death fix?
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB?.
Click to expand...
Click to collapse
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
chorner said:
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
Click to expand...
Click to collapse
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
063_XOBX said:
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
Click to expand...
Click to collapse
good point. i also was wrong about the sd card anyways. i flashed cm9 back on it. turned auto brightness off. it had the issue. rebooted. turned it back on. re-enabled autobrightness. no issue.
thanks for the compliment.
I'm on 4.2 and have the issue. A few times a day, I'll pull it out of my pocket and I see the "backlight" turn on but screen is on. (I'm not sure how there is a backlight if is amoled but i do see some kind of something very very faint )
In Developer Options put all animation scales to .5x.
el_charlie said:
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
Click to expand...
Click to collapse
I experienced a similar issue on 4.1, but it would happen almost once day (very annoying). I'm now on a 4.2 rom and I haven't seen the issue in weeks. :laugh:
On this particular Rom, has anyone had any issues with proximity sensor not recognizing the phone to your ear, therefore pressing buttons with your face instead of shutting off? I don't use phone for calls often, but seems every call I've taken I've run across that issue. Thanks!
I am on the latest MMuzzy Toro plus 4.2 and haven't noticed anything like this so far. I don't do a lot of calling but when I take a call it seems to work normally.
I'm running the 11/21 build and have no issue. I have made a few calls and no problems.
OP may try a fresh flash
Thanks I'll try fresh flash see what happens. Just wanted to see if anyone else had similar issues.
Sent from my Galaxy Nexus using xda app-developers app
I've problems with the Proximity sensor too.
Ok.. I am noob. But here is what I've.
I got the new 4.2 takju image from google and followed a very good thread here about how to install it and it worked perfectly. The only thing that is not working is Proximity sensor during Skype calls and Google Talk calls. I really can't understand this but this is the problem I've.
I flashed it twice with takju and it didn't work and installed yajku too and still not working. I am noticing minimal amount of reports about this but over the internet. But no solutions yet.
Hope someone would help us
I have been on his ROM from the day 4.2 dropped and it has been great. Few problems (googles not mmuzy's)but they have been fixed berry quickly
Sent from my Galaxy Nexus using Tapatalk 2
Yes, please check out my thread: http://forum.xda-developers.com/showthread.php?t=2006783
Fresh install, factory resets, the works. Still have the problem. Proximity sensor turns the screen off but the dial pad or even the end call button are active and are pressed by my cheek. It pretty much kills 4.2 for me and I am just about to go back to 4.1.2.
EDIT: Just to clarify, I am running completely stock 4.2 tajku
Just an FYI, appears to be a PGM issue in relation to 4.2. Even checked the PGM app thread and author released an update for the paid version, with the free version being updated soon.
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.
fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.
Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium
kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.
Hi Guys,
I have been having an issue with my S4 mini where if Bluetooth is turned on it will not see any Wifi networks, however if I turn off bluetooth it connects and works right away.
I have tried going back to stock and different kernels but I am getting nothing, and its sending me spare, since I sued bluetooth a lot.
Anyone else experienced it?
I am running stock 4.2.2 at the moment rooted, and have tried all sorts of roms and kernals.
Toje2 said:
Hi Guys,
I have been having an issue with my S4 mini where if Bluetooth is turned on it will not see any Wifi networks, however if I turn off bluetooth it connects and works right away.
I have tried going back to stock and different kernels but I am getting nothing, and its sending me spare, since I sued bluetooth a lot.
Anyone else experienced it?
I am running stock 4.2.2 at the moment rooted, and have tried all sorts of roms and kernals.
Click to expand...
Click to collapse
I'm running Proxyuser's Slimrom (JB) and F4ktion 1.3.0 Kernal has no such problem. Maybe try this combination? But I remember no such problem even before I did anything to the phone (ROOT/ROM/Kernel, etc), only the battery drain issue at standby.
TNCS said:
I'm running Proxyuser's Slimrom (JB) and F4ktion 1.3.0 Kernal has no such problem. Maybe try this combination? But I remember no such problem even before I did anything to the phone (ROOT/ROM/Kernel, etc), only the battery drain issue at standby.
Click to expand...
Click to collapse
Thanks! I'll Give it a go.
Ok, what strange is it seems to only be when I have root.
If I have root enabled, nothing, if I unroot my phone, all works perfect.
EDIT:
Well that's not true any more, running SlimKat now, slimjim gave that same result
Toje2 said:
Ok, what strange is it seems to only be when I have root.
If I have root enabled, nothing, if I unroot my phone, all works perfect.
EDIT:
Well that's not true any more, running SlimKat now, slimjim gave that same result
Click to expand...
Click to collapse
LOL, well whatever works for you. Since I'm running SlimJB and using root without any issue.
OK a follow up, the problem came back,
I got the ****s and sent it back to repair by Samsung, I got a new phone Back and the problem is gone.
The touchscreen stopped working on the phone a few months ago and a few weeks ago, after the phone had been dormant for a while, I decided to check if it worked and it was fine. But after a software update it stops working when you leave the phone for an hour or two, but if you turn the screen off and then back on it works (make sense?) Anyway, I'm assuming this is a software issue and there has been another update since then, current firmware is 4.2.2 and HTC Sense is 5.0, and I can't see this being a hardware issue. It doesn't really bother me that much but I want to sell the phone and I want it to be working perfectly when I do (I was thinking of putting a disclaimer but I fear the issue might worsen or the buyer will miss it). I've looked around for similar issues but there doesn't appear to be any, for most people it is a continuous thing (but it happened for others after updates as well.) Does anyone have any fixes for me?
sirman2 said:
The touchscreen stopped working on the phone a few months ago and a few weeks ago, after the phone had been dormant for a while, I decided to check if it worked and it was fine. But after a software update it stops working when you leave the phone for an hour or two, but if you turn the screen off and then back on it works (make sense?) Anyway, I'm assuming this is a software issue and there has been another update since then, current firmware is 4.2.2 and HTC Sense is 5.0, and I can't see this being a hardware issue. It doesn't really bother me that much but I want to sell the phone and I want it to be working perfectly when I do (I was thinking of putting a disclaimer but I fear the issue might worsen or the buyer will miss it). I've looked around for similar issues but there doesn't appear to be any, for most people it is a continuous thing (but it happened for others after updates as well.) Does anyone have any fixes for me?
Click to expand...
Click to collapse
Have you tried resetting the OS (if you're on stock)?
If not tried flashing a new rom or reflash it?
Bobbi lim said:
Have you tried resetting the OS (if you're on stock)?
If not tried flashing a new rom or reflash it?
Click to expand...
Click to collapse
I tried after I made this thread but the problem continues to persist.
Try to flash a coustom kernel like Alex-Kernel, XM-Kernel or lONELyX...