Develop Bugs

[Q]Phone won't auto-rotate/malfunctioning sensor

My t999 lost autorotation after flashing custom roms, but I don't remember if I had it originally on tw. I've tried flashing latest Liquid Smooth, CM nightlies, PACman, Paranoid with full wipes between and nothing has worked. I even read through the flashing guide (even though I'm not new to android or rooting/flashing) and tried the triple wipe/double boot and that didn't help.
So I have been googling and searching xda and could only find one thread on the issue (I'd link but I'm new) but I tried everything listed and it didn't help.
Is anyone having the same problem or know how to fix it?

Go back to full stock and check if it broken or not. Otherwise you can replace by tmobile or samsung since its manufactures fault.
Odin latest firmware. Check stickies on development section.

bikrame said:
Go back to full stock and check if it broken or not. Otherwise you can replace by tmobile or samsung since its manufactures fault.
Odin latest firmware. Check stickies on development section.
Click to expand...
Click to collapse
Can Odin run on a mac? I've used it on my pc but its out for repair. I'm currently downloading a tw based rom but if that doesn't work I'll return to true stock.

dperla said:
Can Odin run on a mac? I've used it on my pc but its out for repair. I'm currently downloading a tw based rom but if that doesn't work I'll return to true stock.
Click to expand...
Click to collapse
Idk about mac. There is thread for it in general section. I will prefer official firmware over any tw based roms to check phone function.

Havr you tried checking if your auto-screen option is checked?
Sent from my SGH-T999 using xda app-developers app

gyggyty said:
Havr you tried checking if your auto-screen option is checked?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Lol
I dont think he is so stupid.

Well thinking back to when I got this phone, it's a refurb replacement for one that i broke the screen, I remembered that i tried the flip to mute music and it never worked. I believe that its a defective device and will contact T-Mobile but I will continue working with it.
I tried FrostyJB and no rotation.
Haha obviously I have checked Auto-rotation and I tried unchecking then pulling the battery and then booting and rechecking. I've tried unchecking, rebooting into recovery (through power menu and manually), wiping cache then booting and checking it. And also the thread I read at androd forums said to boot into download mode then pull the battery but that did nothing, others there said that they dropped their phones and that fixed it but I have never dropped my current phone ( I recieved it on sunday) so thought that that was not going to work so attempted it anyway. I slammed it on my couch and dropped it from a few inches onto my coffee table with no results.
I will need to return it to full stock anyway if I want to bring it in so I will do that through Odin and triangle-away, and if I still have no rotation I will report back and look into getting a replacement.

Some phones have their sensors messed up, I had a Mytouch 4G that had issues when calling. Would get a call the proximity sensor would turn off screen when I'm talking but when the call was over screen would not turn on. I had to reboot most of the time unfortunately it's not really fixable something so fragile,so eventually i just change the hex values so the screen wouldn't turn off during a call problem solved.
Sent from my SGH-T999 using xda app-developers app

there is a sensor test on most of the stock roms
in the stock dialer:
Quick Test Menu
*#7353#
select the Accelerometer test and tilt the phone whatever way you want.
If the arrows don't change, then the sensor isn't working. If the Arrows do change, then all good, problem in rom setup.......
Good Luck
Aloha

Defective phone, T-Mobile is replacing for free.

[Q] Anyone having camera issues?

I haven't seen anything about this, but my rear camera occasionally goes entirely black. At first I thought it was a problem with the 4.3 roms, but it's started happening even with TW Roms. At first I attributed it to having the Nottach framework on there, but that has been removed and I still have my camera black. Front camera works just fine. I may have to go back to stock and see if it is broken to see if it's a physical issue with the phone, but I thought I'd ask and see if this was well-known first.
Edit: If I put the camera in "Panorama" mode, the camera activates, but it is all out-of-focus. I'm thinking this means it's a software issue. Using Wicked v4 ROM.

neverbugme said:
I haven't seen anything about this, but my rear camera occasionally goes entirely black. At first I thought it was a problem with the 4.3 roms, but it's started happening even with TW Roms. At first I attributed it to having the Nottach framework on there, but that has been removed and I still have my camera black. Front camera works just fine. I may have to go back to stock and see if it is broken to see if it's a physical issue with the phone, but I thought I'd ask and see if this was well-known first.
Edit: If I put the camera in "Panorama" mode, the camera activates, but it is all out-of-focus. I'm thinking this means it's a software issue. Using Wicked v4 ROM.
Click to expand...
Click to collapse
I'm stock never rooted and my vamera blacks out sometimes where closing tye camera app doesnt do anything so I have to restart my phone to get it right again. I would like to know if this is a common thing or if there is something wrong with mine as well
Sent from my SGH-M919 using xda app-developers app

In case anyone else is having this problem, I eventually solved it. I flashed Infamous then Wicked v5.1 - camera was still black on both of these. Opened Google Edition Camera photosphere and started taking the pictures and that fixed it somehow. Not sure what the hell was the problem, but it hasn't been an issue since then.

[Q] Auto rotate problems and a fix?

My nexus 7 2013 has the problem that it does not auto rotate.
I know I'm not the only one.
If I load a app that reads the sensors for rotation etc, they all report 0000000 ie no reading what so ever.
The problem occured after the update of android.
This happens with all the 4.4.2 roms I have tried (yes I did a reset/totally clean instal) I've tried 3 including stock
This happens with all kernels I have tried 2 including stock
I thought it was a hardware fault however following a tip on a few forums, if you set the tablet to NOT auto rotate, reboot to recovery, clear the cache, reboot to system, turn auto rotate on, it works for a few minutes and then stops. I know a new device would fix the issue, as wood rolling back to the old android version.
I want to run 4.4.2 or higher.
I dont want to send it back under warranty as I have a glass screen protector on it that cost $40 by the time I had imported it.
Does anyone know if there is a kernel/rom that can fix this? (or has anyone had this issue and what did you do to fix it?)
Thanks, Marty

artymarty said:
My nexus 7 2013 has the problem that it does not auto rotate.
I know I'm not the only one.
If I load a app that reads the sensors for rotation etc, they all report 0000000 ie no reading what so ever.
The problem occured after the update of android.
This happens with all the 4.4.2 roms I have tried (yes I did a reset/totally clean instal) I've tried 3 including stock
This happens with all kernels I have tried 2 including stock
I thought it was a hardware fault however following a tip on a few forums, if you set the tablet to NOT auto rotate, reboot to recovery, clear the cache, reboot to system, turn auto rotate on, it works for a few minutes and then stops. I know a new device would fix the issue, as wood rolling back to the old android version.
I want to run 4.4.2 or higher.
I dont want to send it back under warranty as I have a glass screen protector on it that cost $40 by the time I had imported it.
Does anyone know if there is a kernel/rom that can fix this? (or has anyone had this issue and what did you do to fix it?)
Thanks, Marty
Click to expand...
Click to collapse
I use SinLess ROM and the official CM 11 ROM and never had a rotate issue. It could be a coincidence when the trouble stated too.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

[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.

Rotation is gone, even on stock rom.

So I've using custom roms for a while. But recently I realized rotation out of the blue. Reinstallations and fixes didn't work. So I decided to install TW Stock rom. And to my surprise rotation STILL doesn't work. Did the hardware just die? Any ideas?

ultra99 said:
So I've using custom roms for a while. But recently I realized rotation out of the blue. Reinstallations and fixes didn't work. So I decided to install TW Stock rom. And to my surprise rotation STILL doesn't work. Did the hardware just die? Any ideas?
Click to expand...
Click to collapse
for me too, but I think that a few drops killed it or sth like that. I've ordered new sensor, so will let you know if that fixed proximity sensor problems.
Try apps from play store to test if sensor is working. For me it detected, that sth is near and stay in that state until restart