Dear Guys, I was facing with uncalibrated, unaccurate accelerometer sensor or gyroscope. This problem cause a lot problem when playing games and can't calibrate the sensor manually.
With CM13 there aren't any setting where we can calibrate our OP2 sensors. With Oxygen OS 3.0.2 we have an option in the Hidden Menu.
If you are in a custom rom where you can't calibrate the sensors then install OxygenOS or SkydragonROM then follow this link: https://forums.oneplus.net/threads/re-calibrating-accelerometer-magnetometer-gyroscope-sensor.405894/
After you calibrated successfully you can check with bubble level app.
After that you now can flash a custom rom like CM13.
The calibration stayed with clean flash for me.
It is an experience which helped me.
I hope it can help for others.
Cheers
That explains the unresponsive compass results, however a really messy way to fix it. I'm hoping for an app to calibrate without having to land on OOS just for this functionality ?
I performed the above procedure, clean flashed OOS 3.0.2, I didn't established network connection nor a Google account. I performed the 3 calibration tests, my device (A2003) passed.
After that I acquired GPS signal, locked and compass working.
Then I rebooted into TWRP.
I made a backup of my EFS (which makes a backup of modemst1/modemst2)
I restored a full CM13 backup (Aug 11th nightly). Booted up and the compass worked.
Then I dirty flashed the Aug 12th nightly (Dalvik/Cache wiped). When CM13 booted, the compass didn't work.
I booted into TWRP, restored EFS, wiped Cache only, I rebooted into CM13 now compass is working.
Thanks for the post but I don't think the above procedure is working, I had compass working/not working after reboot before, I don't think the calibration had anything to do with it.
PS: the reason I backed up / restored EFS after OOS 3.0.2 is because I knew from my old device (Moto G 2014) that Snapdragon caches GPS data in modemst1/modemst2 partition. So I thought maybe I should get a GPS lock and compass working on OOS 3.0.2, back up the 2 partitions included in EFS and restore them when I 'll have trouble on CM13. Maybe this did the trick.
---------- Post added at 05:20 PM ---------- Previous post was at 04:42 PM ----------
I also dirty flashed Aug 13th nighlty, wiped Dalvik/Cache, compass didn't work.
I rebooted in TWRP, restored EFS from OOS 3.0.2, wiped Cache only, booted back in CM13 and compass worked.
Wow thanks to everyone for this tip. My compass seems to be fixed now.
I guess the key point for people using cm13 is to make sure you make the EFS partition backup after calibrating in OOS so that you can restore it every time you update.
Related
The gestures randomly stop working after the marshmallow update. So, I clean flashed 3.1.3 with stock recovery after deleting cache and data. Gestures randomly stop after sometime but works again if you reboot. Any way out?
Now, I am rooted with twrp recovery.
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
I think that explains it.
Exodusche said:
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
Click to expand...
Click to collapse
Thanks I will do my research!
pavikum said:
Thanks I will do my research!
Click to expand...
Click to collapse
No problem also meant to say gestures never worked better. . Almost to good every time I clean my screen flashlight or music starts playing lol.
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
vinz_uk80 said:
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
Click to expand...
Click to collapse
Haha, at least I have some company now!. Thanks, that trick works!
maybe we followed the similar steps to arrive at this issue.
I was on Sultan CM rom 13 , when the 3.1.1 update arrived, I unrooted my phone locked the OEM and clean installed 3.1.1 through stock rcovery after clearing data and cache. My phone gesture problem started from here, I updated to 3.1.2 through OTA and that did not solve it, so I clean installed 3.1.2 and later 3.1.3. Rooted it with modified superSU and blu spark twrp recovery. Did you follow the same steps.
I am not wiping the internal storage yet, as suggested by 'Exodusche', as I am doing my research to understand the potential risks. But, I did not really find any helpful article till now.
I just extracted the firmware files from the HYDROGEN 2.5 beta/(now Oxygen 3.5.6) release.
Just flash this and then LineAge OS/former CM14.1 official(Confirmed Working) and get VoLTE working..
VoLTE working perfectly (no RR and network drops)with modem ver 1.2
FLASH ON YOUR OWN RISK, AS we are Tweaking Modem Firmware
LineAge OS/former CM14.1 already has VoLTE patches in it.
Just Found out OxygenOS2 also had patches so v1.1b is working on it.(Confirmed for V 2.0.1)
If you have flashed on oxygen.3.1 to reset your phone
follow oneplus china's guide
EDIT : You will end up giving up your IMEI 2 if you rolled back to old Firmware
Fix for Missing IMEI in older ROMS:
The new modem changes the way IMEI is stored, so in older ROM's like OOS3.1.0 you can enable the IMEI by simply flashing the new H2OS modem on the ROM(OOS3.1.0) and it will enable the ROM to read the IMEI for Slot2 ​
And edit build.prop and add
Code:
#ifdef VENDOR_EDIT
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=0
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=0
#endif
In the end for getting volte working
Fix for Random Reboots(CM14.1) and Network Drops(H2OS) :
Download Network Signal Guru from play store.
Give root access and start testing from 3 dot menu.
Now click magic wand and select BAND LOCKING.
Select only the band with best strength( 5 in my case) and uncheck rest of them.
Stop the testing
AND You are good to Go
Mine Network stable since 3 days.
Even you can get VoLTE working in OOS 2.0(Lollipop):
Oneplus tried to implement VoLTE for Oneplus2 back in the development days of OxygenOS 2 and the have VoLTE patches in it too. So If you flash the modded zip of the VoLTE modem you can even get VoLTE calling working on OOS 2(Tested on 2.0.1).
Download :
v1.2 here
v1.1b here (For Lollipop/Older Bootloader)
Just hit a thanks if I saved your time from downloading whole OS zip.
thnx dude
Finally, the whole "is volte working" thing comes to an end... May God bless us all! :laugh:
That deserves an applause...:good::victory:
I have not tested it but hope it is working. Thanks for this
Hi guys,
Just a quick update from my side.
It's not working here in Canada. My carrier Bell does support VOLTE but it still goes to H+ (HSPA) when in call. Not sure what's wrong here. Or maybe OnePlus has a different radio static_nvbk file for the North American OnePlus 2 model.
What do you guys think?
Can i flash this on a cm13 based rom too??? Or does it require cm14??
Not working on cm 14.1 official build
Are there any issues with this , i am on cm14.1
Not working for me on off cm 14.1
Boeffla kernel (OOS version) works fine on H2OS 2.5 beta. I am using kernel auditor to adjust saturation, as boeffla config app doesn't work.
Sent from my ONE A2003 using XDA-Developers mobile app
Can someone provide a gdrive mirror as 4shared is giving an error
Thanks
no one try this unless you backup your efs.
i was using cm14.1. there people says flashing this zip can enable the VOLTE, and i did, but that didnt work. it was as usual (except some extra options in PREFERRED NETWORK tab). so i want to reset it by flashing the rom. it didnt work. so i flashed the OOS v3.1.0. But that gave me no IMEI and i have lost both imei and no wifi connection. Also, phone is rebooting randomly. Few months ago, i have backed up my imei (2 modem files), but when i try to restore it, the adb cmd doesnt show my phone in FASTBOOT MODE...
anyone here to help me???
dhaval2010 said:
Can someone provide a gdrive mirror as 4shared is giving an error
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B5FCssz7PFehaWxuZmVxaC0zVTQ
sanchitd5 said:
I just extracted the firmware files from the HYDROGEN 2.5 beta release.
Just flash this on CM14/CM based rom and get VoLTE working..
Download : v1.1 here
Just hit a thanks if I saved your time from downloading whole H2OS zip.
Click to expand...
Click to collapse
You might wanna add to the OP that backup efs is mandatory.. Even a little hint about the risks of tweaking modem files would be useful! You know how people are, they flash first before they think..
V1.1? What is the difference according to 1.0?
shahfaishal said:
i was using cm14.1. there people says flashing this zip can enable the VOLTE, and i did, but that didnt work. it was as usual (except some extra options in PREFERRED NETWORK tab). so i want to reset it by flashing the rom. it didnt work. so i flashed the OOS v3.1.0. But that gave me no IMEI and i have lost both imei and no wifi connection. Also, phone is rebooting randomly. Few months ago, i have backed up my imei (2 modem files), but when i try to restore it, the adb cmd doesnt show my phone in FASTBOOT MODE...
anyone here to help me???
Click to expand...
Click to collapse
You have a backup of efs via twrp? Does recovery still work? Did you try to clean install? Maybe if you flash the modem file of 3.1 you get it working again.. But now is a point where you should think thoroughly before the next step, one step killed you efs / imei and I guess not OOS3.1, even H2os is unlikely.. Looks like a big mess
shahfaishal said:
i was using cm14.1. there people says flashing this zip can enable the VOLTE, and i did, but that didnt work. it was as usual (except some extra options in PREFERRED NETWORK tab). so i want to reset it by flashing the rom. it didnt work. so i flashed the OOS v3.1.0. But that gave me no IMEI and i have lost both imei and no wifi connection. Also, phone is rebooting randomly. Few months ago, i have backed up my imei (2 modem files), but when i try to restore it, the adb cmd doesnt show my phone in FASTBOOT MODE...
anyone here to help me???
Click to expand...
Click to collapse
OOS 3.1 wont work after trying flash H2os 2.5.. it wont connect to wifi or even show simcards, and even if it will boot it will keep rebooting.. same thing happened to me yesterday.. I tried changing the recovery to hybrid, even tried flashing the modem from OOS 3.1, that didn't help either and then tried flashing cm14.1 or even Exodus 6.0.1 but nothing booted because of course the recovery was wrong. And when I tried flashing OOS 3.1 my mac address was weird and not the usual one.. so I did later was, I flashed h2os 2.5 with same recovery, hybrid one, booted the OS, when it went to wifi it showed me my usual mac address which confirmed that wifi was working then I rebooted and went into wipe, did factory reset, then wiped cache, dalvik, data and system, basically except internal storage everything.. then I installed the latest TWRP which is 302-2 from install image and then flashed cm14.1 and gapps etc. and everything started working again.. sim cards wifi everything else too.. I havent tried installing OOS 3.1 again.. but I think flashing gapps along with h2os 2.5 doesn't let you go ahead with the setup and flashing h2os 2.5 installs new modem which completely breaks connectivity in OOS 3.1
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
shahfaishal said:
i was using cm14.1. there people says flashing this zip can enable the VOLTE, and i did, but that didnt work. it was as usual (except some extra options in PREFERRED NETWORK tab). so i want to reset it by flashing the rom. it didnt work. so i flashed the OOS v3.1.0. But that gave me no IMEI and i have lost both imei and no wifi connection. Also, phone is rebooting randomly. Few months ago, i have backed up my imei (2 modem files), but when i try to restore it, the adb cmd doesnt show my phone in FASTBOOT MODE...
anyone here to help me???
Click to expand...
Click to collapse
check this,
https://forums.oneplus.net/threads/...d-for-oneplus-2-will-be-updated.461705/page-3
---------- Post added at 12:39 PM ---------- Previous post was at 12:38 PM ----------
Rohandd said:
OOS 3.1 wont work after trying flash H2os 2.5.. it wont connect to wifi or even show simcards, and even if it will boot it will keep rebooting.. same thing happened to me yesterday.. I tried changing the recovery to hybrid, even tried flashing the modem from OOS 3.1, that didn't help either and then tried flashing cm14.1 or even Exodus 6.0.1 but nothing booted because of course the recovery was wrong. And when I tried flashing OOS 3.1 my mac address was weird and not the usual one.. so I did later was, I flashed h2os 2.5 with same recovery, hybrid one, booted the OS, when it went to wifi it showed me my usual mac address which confirmed that wifi was working then I rebooted and went into wipe, did factory reset, then wiped cache, dalvik, data and system, basically except internal storage everything.. then I installed the latest TWRP which is 302-2 from install image and then flashed cm14.1 and gapps etc. and everything started working again.. sim cards wifi everything else too.. I havent tried installing OOS 3.1 again.. but I think flashing gapps along with h2os 2.5 doesn't let you go ahead with the setup and flashing h2os 2.5 installs new modem which completely breaks connectivity in OOS 3.1
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
check this,
https://forums.oneplus.net/threads/...d-for-oneplus-2-will-be-updated.461705/page-3
Click to expand...
Click to collapse
Although in the end it worked for me it was lot of trial and error and of course panicking..
Mirror link please!!!
Bro.. help me! It's saying "signature invalid. Please try again!". I'm not able to download.. please provide a mirror
I'll try to make this short.
I believe I rooted in Lollipop though exact information on what version, etc.. is unknown to me, as I didn't take notes. I followed whatever guide there was at the time (Sept 2015) to root and unlock/bump the bootloader. All went great and then spent time bouncing back and forth between CM and Resurrection Remix roms using TWRP.
Then came Marshmallow. For most of the year I used Xenon HD and Resurrection. Now that I'm exploring Nougat. Every one I test has signal issues. I seemed to get it fixed on the crDroid 1.4 build, but later after a restore to my Nandroid of that build it was broken again.
I have prefaced my question with this info for a little background. I'm curious as to whether I should/could update my modem to one of the last official LG Sprint updates modem.
Will this help with general signal? Moreover would this potentially fix my issues with N roms? I've considered that this might just be an issue with CM based roms currently. I've tried AICP and AOSCP N roms back a few weeks. Sadly I don't remember if this was an issue with them - I think I just had some general instability issues.
Any information is appreciated. Thanks!
Sent from my LG-ls990 using Tapatalk
that sucks no responses. I need to know too!
If the issue on crDroid 1.4 is the cycling modem that isn't holding connection, the apparent solution is to install an old cdRdoid (1.2/1.3), use TWRP to backup the EFS, THEN do the clean-flash stuff. After it's all loaded, reboot to recovery, and restore the EFS from the old backup. This solves the cycling issue. Here's the steps:
1. Install crDroid (1114) 1.3
2. Boot phone to home screen (with stable connection)
3. Reboot Recovery
4. "Backup" EFS data
5. "Wipe" System/Data/Cache (at least).
6. Install crDroid 1.4 (Dec2) and gApps (Dec5)
7. Reboot Recovery
8. "Restore" EFS data
9. Boot to crDroid.
->Stable antenna connection
long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?
Hello everyone,
I'm experiencing a weird issue with a new F1: the camera flashlight icon is disabled and can't be activated.
Once out of the box, with stock ROM, it was initially working. Restoring the backup of my old F1 (LineageOS 16.0), I think that accidentally I should have restored/wiped something wrong.
After that I restored the stock ROM (beryllium_global_images_V12.0.3.0.QEJMIXM_20201227.0000.00_10.0_global) to fix it, but the flashlight works only if used in CIT mode, it doesn't in any another app.
Which could be the root cause? Wrong firmware?
Thanks in advance
SilverHawk.83 said:
Hello everyone,
I'm experiencing a weird issue with a new F1: the camera flashlight icon is disabled and can't be activated.
Once out of the box, with stock ROM, it was initially working. Restoring the backup of my old F1 (LineageOS 16.0), I think that accidentally I should have restored/wiped something wrong.
After that I restored the stock ROM (beryllium_global_images_V12.0.3.0.QEJMIXM_20201227.0000.00_10.0_global) to fix it, but the flashlight works only if used in CIT mode, it doesn't in any another app.
Which could be the root cause? Wrong firmware?
Thanks in advance
Click to expand...
Click to collapse
I would flash stock firmware and factory reset the device. Hopefully this will fix your issue.
Then you should be careful with flashing the custom rom you prefer ... maybe restoring the backup of your old devices is not the best idea.
It_ler said:
I would flash stock firmware and factory reset the device. Hopefully this will fix your issue.
Then you should be careful with flashing the custom rom you prefer ... maybe restoring the backup of your old devices is not the best idea.
Click to expand...
Click to collapse
I usually install LineageOS on every phone before to do everything else. We have three Poco F1, and I had no issue with the other two, only for this I think I did a mistake somewhere.
I already did a factory reset, restoring full stock ROM too. I suspect to have accidentally damaged another partition (i.e. persist).
Any other hint?