Develop Bugs

Quiet ring on pickup stopped working :(

Hi folks,
I am experiencing some strange problem, since leedroid rom mod 1.4 this feature isn't working anymore. I've tried a few different roms after I recognized that the volume stays the same after almost "throwing" the device in all possible directions I've wiped everything before installing the different roms but no change, it won't work for some reason and I don't no what this may caused.
It's a nice feature and I really don't want to miss it. Could this be perhaps a hardware related problem ? It's driving me nuts because I have no idea at the moment
Every help is appreciated ! Thanks in advance.

Hi again,
I've run some more "tests" and actually found out that it's working when the phone is lying on the desk, then the volume is getting reduced after grabbing it but when I hold the phone in my hand and shake it during an incoming call nothing happens unless I put it with the face down on a table.
So my question is this how it's supposed to work ? I actually don't know which sensors are being used for this feature :s

m8tix said:
Hi again,
I've run some more "tests" and actually found out that it's working when the phone is lying on the desk, then the volume is getting reduced after grabbing it but when I hold the phone in my hand and shake it during an incoming call nothing happens unless I put it with the face down on a table.
So my question is this how it's supposed to work ? I actually don't know which sensors are being used for this feature :s
Click to expand...
Click to collapse
The feature only works if the phone is completely still when it starts ringing in my experience.
If you're holding it in your hand and you call it then it won't happen. If you leave it on the desk and then call it, it will happen. The sensor being used is the Accelerometer, I think. Which is incredibly sensitive.

Budadank said:
The feature only works if the phone is completely still when it starts ringing in my experience.
If you're holding it in your hand and you call it then it won't happen. If you leave it on the desk and then call it, it will happen. The sensor being used is the Accelerometer, I think. Which is incredibly sensitive.
Click to expand...
Click to collapse
I really appreciate your answer !
That's what I actually thought and thanks a lot for your confirmation The sensor seems to be very sensitive in this case but as long as it's working I'm ok with it because I leave it almost all the time on my desk at work, I just thought that it also had worked while taking it from the pocket but I was obviously wrong.

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!

rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?

Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..

Which ROM?

I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?

Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):

Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....

Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone

Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.

rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).

I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now

djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.

HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks

rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.

are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...

Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).

I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...

After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.

You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

screen wont come back on during call

my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.

chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****

aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?

From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.

networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.

i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.

thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.

well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.

There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.

We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?

no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.

actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.

Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.

Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.

Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?

we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.

It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent

Proximity sensor seems to not work anymore

I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?

Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.

My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .

I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.

I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.

amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).

iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app

Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !

[Q] Black screen on calls

I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard

Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.

You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.

When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?

audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.

riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.

audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!

riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?

If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?

riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.

audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard

riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.

audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.