Database Info

[Q] [Help] Autorotate and wifi issues

Hi there.
I have an issue with auto-rotation and wifi.
I'm running an Asus tf 101, currently running CM. Technical details at the end of the post.
My issue is that autorotate is no longer working on CM, which led me to try upgrading to the latest CM, but when I tried a clean install (wiped cache, wiped data, wiped davlik) neither the autorotate nor the wifi worked.
Restoring my previous backup worked, and I returned to the situation which had wifi working, but no autorotate.
My poor searching skills found issues with the latest ROMs and autorotate, but I couldn't find any mention of autorotate which failed.
I suspect that with my messing about with ROMs & Kernels I might have messed things up, potentially corrupting the Kernel that I've been using.
[UPDATE] to eliminate sensor failure I installed a sensor app which indicates that the tf101 is successfully getting the orientation information.
[Q] Where is the best place to go to learn how Kernels & ROMs interact that I might learn how to fix whatever my mistake was?
[Q] Has anyone else encountered this? Does it sound like something fixable?
If I am in the wrong place, I would love a nudge in the direction of the appropriate forum.
Thank you.
Details:
Android Version: 4/1/2
Kernel version 2/6/39/4-kat-gae9f1bb
[email protected] #56
Sun Nov 11 19:08:06 CET 2012
CyanogenMod Version
10-201222-Nightly-tf101
I can sort you out with a build date and number as well if it would be useful.

It's pretty hard to troubleshoot. I had the same problem so I moved away from CM10 and went with Team EOS' 4.2.1 (see my sig).
But from what I could gather through months of playing around, this sort of stuff happens when you upgrade from another version and "something goes wrong". It doesn't mean that your new updated rom won't work, but you may get unexpected results. How did you do your rom install process, and from which rom/version?
You could install a logcat or manually tail -f the log files then trigger the autorotate with an app, then see what happens in the logs then report back. Otherwise all I can suggest is to get your post count to 10 and post in that rom's thread to get further help.

Lethe6 said:
It's pretty hard to troubleshoot. I had the same problem so I moved away from CM10 and went with Team EOS' 4.2.1 (see my sig).
But from what I could gather through months of playing around, this sort of stuff happens when you upgrade from another version and "something goes wrong". It doesn't mean that your new updated rom won't work, but you may get unexpected results. How did you do your rom install process, and from which rom/version?
Click to expand...
Click to collapse
Was the problem fixed when you went to Team EOS?
I have been messing with the ROM, and at one point while downgrading to 9.1 the screen was stuck on the loading image for more than two hours, so I turned off and restored from backup, that might well have done something.
I'll look around for a logcat to install....
Thank you very much.

You can also try this:
- Turn off the device completely
- adb logcat (see this for more details)
- Boot the device
You'll get all the logs printed in adb so you can check for errors. Yes the problem was solved with Team EOS' rom. I get perfect wifi signal and auto-rotate works nicely, my only "problem" is that if it goes to sleep it doesn't detect the dock SD card until I reboot, but I can live with that!
Edit: Dock SD card issue fixed with Preview B128.

In the end I also moved to Team EOS, there are a few little quirks, but nothing I can't live without at this stage. Also my video playback has become significanly better.
Thank you for your help!

maybe software auto rotation can fix your problem
search on playstore....
gutlak...

[Q] Help! Lost all sensors after ColorOS -> CM11

Hi all,
Got my OnePlus One last week. It's a Chinese version that comes with ColorOS. I immediately tried to flash CM11 nightly onto it after I checked the phone is working.
For some reason I thought I could flash CM11 directly, and so the first thing I did was installing TWRP 2.8.0.1. Then, I copied CM11 zip in to /sdcard , booted to TWRP recovery, wiped all partitions (including System) and then flashed CM11. In hindsight, I believe it was the wrong way to get CM11. I could have wiped something really important (sensors drivers?) when wiping System.
Initially, CM11 nightly seemed to work OK. Then I noticed the Auto-Rotate is not working at all. I installed CPU-Z and *gasp*, there's not a single sensor listed in the CPU-Z Sensors tab!
I spent hours today trying various methods (flash CM11S, flash ColorOS, flash /persist, /reserve4 partitions). However, the sensors are still dead! Besides auto-rotate, I think auto-brightness, proximity sensors are all dead.
Is there any way to get the sensors working again? Your help is much appreciated!

Try http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and see if your sensors work after restoring to factory images.

Someone else said only twrp 2.7 is supported for opo, another guy had similar device breaking problems with 2.8.

I'm using TWRP 2.8.0.1 and have no problems. TWRP 2.8 had problems, but 2.8.0.1 resolved them.

Thanks a lot for the quick reply, zephiK! I've run flash-all.sh and I'm in CM11S now.
CPU-Z no longer shows an empty Sensors list! however, only the following 4 sensors have readings:
AK8963 Magnetometer
AK8963 Magnetometer Uncalibrated
TMG-3993 IR_Gesture & Proximity
TMG-3993 Ambient
No readings for the rest...

Does auto rotate work? I'm not really sure how your sensors disappeared in the first place, its very odd.

/system is wiped on every ROM flash anyway so that's not the reason. Glad it's working better at least. Any more issues with the sensors other then some not showing?

Nope, the auto-rotate is still not working.
I've just rebooted CM11S, and... the Sensors tab in CPU-Z became empty again! This is very strange indeed...

I think t is a kernel problem,
Maybe you van flash the original boot.img

Rebooted again. The list of sensors are showing in CPU-Z again, and the same 4 lines have readings (AK8963 Magnetometer, TMG-3993). Still no auto-rotate.
My gut feeling is that there is a low level corruption in one of the "special" partitions. By special I mean the ones that are there but not included in any of the ROMs or factory images. Unfortunately, I don't have a NANDROID backup to restore from (Huge mistake on my part).
Is there a way to download an NANDROID image containing those special partitions?
@gurby1, I thought about kernel problem too, but I've tried flashing many ROMs and kernels:
CM11S 33R
CM11 Nightly 20140296
Franco Kernel r20
ColorOS 2.0 beta
ColorOS 1.2
and the results were the same - broken auto-rotate.

Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437

DecemberNexus said:
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
Click to expand...
Click to collapse
Hello,
Did you find a solution ? I have exactly the same issue as you. It even worst, I don't see any sensor on my device. I have installed many ROMs without any success. I hope it is not a HW problem
Thanks.

Guys.. I also have this issue..
Glad if there any solution on this...

Same problem
Guys any solution yet? I'm getting annoyed by this so much.. Please post here if u have found any solutions. Thx.

I also have the sensor problem which is all sensor is "not supported" in antutu and empty in CPU-Z sensor tab. I fixed it by flashing the persist.img from this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...

Dzhedaj said:
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Click to expand...
Click to collapse
Have you try flash the persist.img?

TheDynamiteGuy said:
Have you try flash the persist.img?
Click to expand...
Click to collapse
Tried flashing everything, modems, persist.img, etc. Nothing helps, so seems something is toast in the hardware...

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.

Proximity & Light sensors broken?

Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.

Bump..

gneville said:
Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.
Click to expand...
Click to collapse
When you say you've flashed CMOS12 & CMOS12.1, that means the nightlies right? Flashing OxygenOS or any of the CM nightlies should've flashed their respective firmwares. I'm afraid that it is a hardware problem if that's the case.

gneville said:
Hi guys, looking for some suggestions.
My Proximity & Light Sensors have stopped working - and not sure what else to try. I have tried the following:
Flashed CM11S
Flashed CMOS12 & CMOS12.1
Flashed Modems individually (for relavent rom) - and tried Oxygen
If I try this app - it tells me there's no sensor available on my phone.
Looking for any other suggestions really. How likely is it that the sensors have just failed?
I've also emailed Oneplus support - but don't hold out much hope for a prompt or useful reply (looking at other peoples experiences!)
Thanks in advance.
Click to expand...
Click to collapse
Hi, i've the same problem. Lightsensor + Proximitysensor are not working. I also think it's a hardware issue. Today i tried a lot of modem firmware versions since there is an issue with the proximity sensor and modem firmware. No luck.
Did you found a solution? My device is still in warranty but i would like to avoid this procedure.
Regards

@dr0bz if you want to be sure it isn't an hardware issue I suggest to flash completely back to stock and see if the proximity sensor works then, if not with all the default software then I am afraid it is defect and has to be replaced

@wulsic, than i fear this is a hardware case to 100%. I've tried yesterday a complete stock OPO cm 13.2 found here on xda. Ok, than a warranty repair is not avoidable.
thx

dr0bz said:
@wulsic, than i fear this is a hardware case to 100%. I've tried yesterday a complete stock OPO cm 13.2 found here on xda. Ok, than a warranty repair is not avoidable.
thx
Click to expand...
Click to collapse
Well goodluck with sending it to warranty then and don't forget to backup ur data:good:

I've just made a whatsapp call and the app is properly using the sensor. The display is properly switching off near the ear. Funny, ideas?

dr0bz said:
I've just made a whatsapp call and the app is properly using the sensor. The display is properly switching off near the ear. Funny, ideas?
Click to expand...
Click to collapse
Lol, the proximity sensor is working in phone app as well. Perhaps there was an ota update and i just didn't noticed the new state. The weird thing naturally is that i've already returned everything to stock before.

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