For some Reason. all 4.4.4 ROMs I flash, I have issues with the proximity. I have flashed a few times to isolate the issue its hard to determine exactly where starts. I have been able to restore all my apps via titanium backup and no issue. once I start messing with the AOSP/SOKP features is when it presents itself. after a fresh boot I can make a call and it functions correctly. The next call I make the screen stays on. i use Phone Tester app and it shows it works the I press back the go back to the sensors status the proximity isnt working again. I have replaced the sensor to see if that was the issue and that is a no. Like I said, it works perfect on 4.4.2. I have also reflashed over the ROM after I finished setup nothing. Please help.
Related
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
jr8801 said:
So i have started encountering a problem in which about 3 minutes into a phone call my phone freezes and then ultimately turns off and only way to turn it back on is removing the battery and then power button.
I have had this problem on every rom starting on CM. After it happened on this rom i flashed juggs, beast, and da bomb (or whatever) and everyone it still happened. I wiped data, cache and delvik before every flash but this did not help.
I eventually just odin back to stock with the stock tar that is posted somewhere in this forum. This still has the problem. I found that it generally happens if i move from my ear and the screen turns on and then it wont turn back off and no menus are available (ak i cant get into dialer if i call bank or 800 number to input a number) and then it just completely freezes and turns off.
Any help with this would be great. I mean making phone calls is probably the most important part of a "phone" working. So i really need this to be fixed asap. thanks
Click to expand...
Click to collapse
Looks like it might be a kernal problem. Have you flashed back to the stock kernal? If not, I'd look there first
yeah i flashed stock kernal as well...problem still persist
uninstall Google+
no google + never have had it.
Have you tried flashing CM7 Alpha #2? I had that same problem with Alpha #1 release then flashed #2 fixed permissions. Then at first start up i rebooted with GPS on and voila! No more phone FC.
I started with Alpha #1 where the problem started flashed over #2 fixed permissions and same problem. thats when i started flashing the other roms to try to solve the problems but this hasnt helped. So i odin back to stock. flashed stock kernal and stock recovery. and i still have the problem.
What sucks is im just graduating college and im starting to receive calls from future employers and i cannot talk for more then 2 minutes before my phone decides to shut off.
So any other advice???
bump it up. Any help please...::
what it is doing now update: I click on a contact or type a number and press call and the screen turns black except the status bar. soft keys dont work, hard keys dont work. phone is a fail. people can still hear me and i can still hear them but the phone is unusable and i have to pull battery to get out of the black screen.
This was doing it on every rom and i have now put beastmod v2 4.0 still no luck :[
I just received my White GS2, finished the OTA update.
And yes, the dialer FC on me every single time once I push the hangup button.
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...
OK last week a did a restore to [ROM ] Pure Stock Rooted and debloated ROM via cwm. After doing it I ran into a bunch of force closes and restored back to my stock ROM I had rooted. Since going back to my rooted stock ROM when I receive a call or place a call. My phone screen shuts off and I can't get the screen to turn back on during the call. If the person on the other end of hangs up. I can then get the screen to turn on and things seem normal. I've tried formatting, wiping cache, and delvic. I've tried other ROM's like CM 4.3 and they all behave the same way. Does anyone know what other things I can try because I'm starting to think I got a F'ed up sensor issue that may be more hardware than software issue.
So, i'm completely lost. I was playing around with ROMs and mods (the RAM build.prop, for example), and now all my phone's sensors seem to be stuck.
I have reflashed back to completely stock ROM, taken official sprint update. Tried modded ROM, done factory resets, cleared/wiped everything, and still the issue persists.
It would appear my Gyroscope, Accelerometer, Proximity Sensor, and Compass are all not responding at all.
Right now i'm on rooted stock AOJ6.
Does anyone have any ideas? Maybe a corrupted sensor properties file or something similar like that? I'm completely at a loss.
Any help is appreciated.
Guys, it fixed itself. I booted into safe mode, restarted and all the sensors are working again.
I doubt it had anything to do with safe mode, as the sensors weren't working in safe mode.
I have no idea what could have done it. I wish I had a real answer for you.
Hi, I've an annoying problem with the Bluetooth: when it's turned on, it turns off randomly and after few seconds it turns on.
It's impossibile to keep connection with other devices.
I've the last firmware version.
Please help me!
Try a factory reset to see if it is a problem with the software or an app.
If it still keeps dropping it might be a broken Bluetooth module which has to be repaired...
I have root and recovery. Can I reflash the firmware I have with root and dualrecovery included? If yes, what I lost?
Thanks
I have a similar problem with various CM12 and CM12.1 builds ... Bluetooth just can't be turned on, after turning it on, it turns itself off after a few seconds.
Originally I thought, it maybe a hardware defect, but when going back to a previous version of CM (restoring a nandroid backup), Bluetooth worked flawlessly. As I didn't want to stay with a build from November, I kept updating the ROM, but Bluetooth stayed offline.
Until today when I made the suggested factory reset. Now Bluetooth works without problems, even after reinstalling all the apps I had installed before. So thanks for your advice, Schlengge