Database Info

CM12s Proximity sensor issue

Hi , i've updated my Oneplus one to official Cm12s.
My screen wont wake up when call comes , i have to double tap / press power buttom in order to see call screen.
Its happening specially when sensor is coverd or phone is in my pocket.
I've tried many diffrent solutions like flashing old 11s modem , new alpha lollipop modem , cm12s proximity fix zip , cm12s extras zip but nothing works !
So i attempted to create this thread , please help if you know how to solve it !
Thanks

Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon

I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?

IAmTheRobin said:
I am having an issue with my proximity sensor not working at all. The phone goes blank during a phone call and I cannot wake it up until after the call is over.
I am using an unofficial nightly build for CM11 from a few days ago. This was a recent downgrade from the recently released official CM12.1 nightly because I was not pleased with it's stability.
I used an app to see the sensor values and the light sensor works while the proximity reports nothing. Which modem should I try to flash for CM11 to try to get my sensor back?
I read the proximity sensor and the light sensor are the same hardware unit. Is this true? Or is there a chance I have to warranty my phone?
Click to expand...
Click to collapse
You need to flash a KitKat modem, this is the latest:
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Transmitted via Bacon

Fixed! Thanks.

IAmTheRobin said:
Fixed! Thanks.
Click to expand...
Click to collapse
No worries.
Transmitted via Bacon

Help
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).

.::[email protected]::. said:
Is it possible to flash the modem with cm (stock) recovery? My device is not rooted (bootloader locked).
I'm on cyanogen os 12. (ota update).
Click to expand...
Click to collapse
No, you need a custom recovery. Just unlock your bootloader, simple. It really should be unlocked anyway, you'll be screwed if you get into trouble and need to flash the stock images, because it's at that time that the unlock command won't work, and then you can say bye bye to your phone.
Transmitted via Bacon

Not fixed !
Isuue remain same
Sent from my A0001 using XDA Free mobile app

Proximity sensor not working
I'm on COS12 and my proximity sensor isn't working as well.
Tried reflashing the rom (not clean install but just reflash), and wiping cache and dalvik, but no luck
Also tried the oxygen modem, it gave me no result either...
What should i do now

timmaaa said:
Try flashing the latest Lollipop modem:
http://boeffla.df-kunde.de/bacon/modems/Full-YNG1TAS0YL-modem-flashable.zip
Transmitted via Bacon
Click to expand...
Click to collapse
I downloaded the sensor app and it did show that the proximity sensor was not working.
1) Flashed full CM modem, proximity fixed, no text/notifications on wifi. I know because I sent text with a different phone through WIFI, nothing popped up. I turned off WIFI and I get the texts.
2) Flashed 12.1 CM, same behaviors as above.
3) Flashed back to Team Nocturnal's 5.1.1 build, still same result.
4) I flash CM11 05Q modem, I get notifications/text on WIFI, but the other end is I get the proximity sensor issue; phone doesn't turn off while on a call and it activates the screen.
Still no solution or fix. Just FYI I am an at&t customer on the west coast.

I've some issue related to yours with proximity, but before trying to flash with new firmware - want to ask some people who know more about this than me.
My proximity sensor works good, screen disables during calls, enables while I've put my phone away an ear, BUT it stops working in random situations. I'm using an option to prevent phone unlock with proximity sensor, but phones somehow wakes up in my pocket. After restart all backs to normal. So I think it's not HW related issue as proximity sensor works. Do you think that changing firmware might help?
I'm on latest COS12.1S ROM (updated to second OTA). On COS12S all works good with disabled ambient display option, with enabled same issue. On COS12.1S tried to disable ambient display but no success.

Interesting issue. Replaced my LCD and was stuck in bootloop but...

Hi everyone.
I recently replaced my shatter LCD and was subsequently trapped in a bootloop. I began to wonder if the LCD I ordered was defective, so I removed the new screen and attached the old one. The device booted up fine (as fine as a devastated LCD screen would permit anyway). I detached the broken screen and reattached the new one and the device seems to be working fine.
I am now worried that shutting down the device will cause it to enter a boot loop again. Would reflashing the stock rom solve this issue? Has Motorola installed a failsafe that would prevent devices from booting up if there is a replacement screen attached to the logic board??

I am having the same issue, did you find a solution?

mike29892 said:
I am having the same issue, did you find a solution?
Click to expand...
Click to collapse
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?

ElonNoir said:
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
Click to expand...
Click to collapse
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?

mike29892 said:
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
Click to expand...
Click to collapse
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.

ElonNoir said:
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
Click to expand...
Click to collapse
I couldn't even get the device to boot before restoring to 5.1. I was on 6.0 broke my screen and then replaced the screen. After turning the phone back on it entered a boot loop. I restored to 5.1 and it was able to boot, but the touch screen was all wonky, and getting phantom touches. I tried to flash 6.0 again and it just put me in the boot loop again.

Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.

fresh cut vegetables said:
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
Click to expand...
Click to collapse
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.

ElonNoir said:
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
Click to expand...
Click to collapse
It won't reboot until the OS starts loading, as long as you can access TWRP you should be safe to flash a custom ROM... it seems to be a known issue that a non-Moto replacement screen will bootloop the OS with Marshmallow but not Lollipop, unknown if CM13 and ROMs based it (which is all custom MM ROMs) will bootloop or not.
Best solution is replace it with an OEM Moto screen, it won't bootloop, only 3rd party ones do.

SM-N920p Keeps rebooting after root on marshmallow . Have i bricked my phone?

Hello all. I am from the UK and recently purchased a sprint model phone. I wanted to remove handsfree activation. In order to do that i need a root. I rooted 5.1.1 with kernel SpaceX-Kernel-v0.1_N920P(official).tar and all seemed ok. Then i noticed that you could root marshmallow. I followed a tutorial on youtube and flashed two files through twrp no-verify-opt-encrypt.zip and SuperSU zip. I rebooted the phone and now i have a persistent problem. After around 15-30 seconds my phone shuts off and reboots itself. I have tried reflashing stock roms and the problem still persists. I have no idea if i have broken the phone as its usable until it shuts off . I went into the about phone section and it tells me the baseband and software versions are unknown aswell. Is there anyway to recover this?

Known issue. Drain battery until it is dead and charge again.

tdunham said:
Known issue. Drain battery until it is dead and charge again.
Click to expand...
Click to collapse
Thank you very much for responding. That has solved the issue completely! Using MOAR rom on 6.0.1 with no issues. Thanks once again!

Need help restoring s6 edge hardware functionality!

Hey guys, I recently flashed the Stock ROM PI3. The flash was successful, but I soon found out I have lost a lot of functionality in my phone. My sensors stopped working. My phone doesn't count steps anymore, can't auto-rotate, IR Blaster doesn't work, Heart rate sensor doesn't work, waving your hand over the front screen doesn't wake the screen anymore. The only sensor that seems to work is the fingerprint sensor. I have tried wiping data/cache and reflashing the stock ROM, at the link mentioned earlier, but nothing has solved this issue. If anyone has any idea what is going on, that would be very helpful!

Try to download the firmware again and then try flash it. Also make sure you have the latest version of odin

Stock Nougat Firmware "BLUETOOTH WON'T TURN ON" (HELP)

suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!

Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.

Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?

I don't know the answer to that

exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it

dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom

lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working

dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???

Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u

Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem