Related
In latest Cyanogen OS 12.1 update YOG4PAS1NO and CM Snapshot 12.1 YOG4PAO236 the compass is still giving troubles indicating the correct direction when tilting the device... Fixing the compass is really easy and I don't know why CM mantainers didn't merge this fix for OPO. The fix is really simple, you can do it manually or flash the attached package in recovery.
Manual steps (root required):
Modify with an editor /system/etc/sensor_def_qcomdev.conf:
line 66: :version 0x00010004 (instead of 3)
line 89: 902 3 0x00010004 (instead of -3 and 3)]
Delete /data/misc/sensors/sns.reg
Reboot and test with https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
Source https://github.com/sultanxda/proprietary_vendor_oneplus/commit/2d48d254d3d330d3d2304e64fef68978611a4d1f
My compass never give me correct direction....Always calibrating....
I am on mokee mkl (similar to cm 12.1), will try tomorrow.
But no help here......
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Thank you, fixed my compass it seems
Sent from my TF700T using XDA Free mobile app
andrew2511 said:
In latest Cyanogen OS 12.1 update YOG4PAS1NO and CM Snapshot 12.1 YOG4PAO236 the compass is still giving troubles indicating the correct direction when tilting the device... Fixing the compass is really easy and I don't know why CM mantainers didn't merge this fix for OPO. The fix is really simple, you can do it manually or flash the attached package in recovery.
Manual steps (root required):
Modify with an editor /system/etc/sensor_def_qcomdev.conf:
line 66: :version 0x00010004 (instead of 3)
line 89: 902 3 0x00010004 (instead of -3 and 3)]
Delete /data/misc/sensors/sns.reg
Reboot and test with https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
Source https://github.com/sultanxda/proprietary_vendor_oneplus/commit/2d48d254d3d330d3d2304e64fef68978611a4d1f
Click to expand...
Click to collapse
Actually @Sultanxda mod is about line 66 (just a version modifier) and all the three lines 87-88-89 and not 89 only as you mentioned...
If you change all the version numbers to 0x00010004 like in the correct version of my change for the magnetometer, then you don't need to delete /data/misc/sensors/sns.reg. Or, what you can do is not change any of the version numbers (and instead only change line 89 from -3 to 3), but you would need to delete /data/misc/sensors/sns.reg. Either of these ways works.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/fix-compass-cos-12-1-and-cm-12-1-nightlies.350897/
My rotation does not work at all unless on oxygen os or cyagen os 4.4.4 but wen i try difrent roms rotation does not work and i download a sensor test and it says i dont have an orrientation sensor but i know i do becacuze wen i switch to stock it werks perfectly
KURDKiNG said:
My rotation does not work at all unless on oxygen os or cyagen os 4.4.4 but wen i try difrent roms rotation does not work and i download a sensor test and it says i dont have an orrientation sensor but i know i do becacuze wen i switch to stock it werks perfectly
Click to expand...
Click to collapse
Maybe a baseband problem? With Android 5.1 use the 241 baseband
Works on any cm based rom?
Do I need to downgrade twrp? Or can I use the latest one to flash the fix thanks ?
Sent from my A0001 using Tapatalk
Looks like there's no activity here but...
I had made this fix and the compass work ok with the phone facing up or front but when is facing down the north gets deviated by 180 degrees, I think that is why HERE Maps is always saying that my compass need calibration and doesn't work with the 8 figure.
Simple fix for inaccurate Compass
The values in the latest file as of 20th November 2015 have changed and therefore I could not apply this. However I managed to fix it with a simple old-school calibration as described here. It should work with any compass-aware app active on-screen, not just GPS Essentials. The compass had been inaccurate on my device since a long time, especially when the device wasn't parallel to the ground. I had tried numerous complicated methods in trying to fix it before and was pleasantly surprised that this worked. My compass now works properly and accurately in all orientations, and would suggest that others try this before going for more involved options. No luck with the HERE Maps "Compass needs adjusting" message though but at least now it points in the right direction!
on&off said:
The values in the latest file as of 20th November 2015 have changed and therefore I could not apply this. However I managed to fix it with a simple old-school calibration as described here. It should work with any compass-aware app active on-screen, not just GPS Essentials. The compass had been inaccurate on my device since a long time, especially when the device wasn't parallel to the ground. I had tried numerous complicated methods in trying to fix it before and was pleasantly surprised that this worked. My compass now works properly and accurately in all orientations, and would suggest that others try this before going for more involved options. No luck with the HERE Maps "Compass needs adjusting" message though but at least now it points in the right direction!
Click to expand...
Click to collapse
Combination of OP advice and above mentioned calibration has solved all my problems with compas and incline sensors. Now Sky View is finaly working fine, thank you so much!
I also have the HERE Maps "Compass needs adjusting" message, i've calibrated the compass with "GPS status" app so it's working but i have to recalibrate it when flashing a new ROM.
Wow thank you! It really worked - Bacon CyanogenMod latest CM12.1 Snapshot
My fingerprint scanner works just fine in official Miui. I unlocked the bootloader(unofficially), using cofface twrp. Currently on AOSCP 3.1 with agni kernel and have no option to turn on fps. Doesn't recognize it when i press it or anything. I've looked in all the folders and name files they said to look in and it all points to me having FPC fingerprint scanner as far as I can tell. I'm not a noob when it comes to flashing custom roms have been doing it since I got the first htc dream back in '09. I've tried other roms and kernals with no avail. It seems that since unlocking the bootloader and rooting I've lost access to my fps... I've never had it working on a custom rom at all. Please help with some possible solutions to this problem!
You may have a goodix, check the ROM threads for the goodix patch, and you may also need a kernel that supports it (agni works for most)
tried the goodix fix with agni kernel.. No luck.
to check for sure what sensor you have just install "AIDA64" - open "Devices" and check under "Fingerprint Scanner" your model.
I have the FPC102x and had the same problem under CM custom ROMs so went back to Miui...
AIDA64 says FPC102x. So are we burnt on the fps working at all on custom roms?
Device:
Redmi Note 3 Pro, Snapdragon, 2GB RAM, 16GB Internal.
Currently on ViperOS Coral with stock kernel. (latest version of magisk is installed)
Hey community (and hopefully devs)!
As the title suggests, (I think) I broke my vibration motor. Basically, I flashed two custom kernels on top of each other. I really don't have any more info about that, like which ROM or kernels I used. I know, there were warnings everywhere, I've seen them.
Anyway, all I'm asking is if there's any flashable zip or maybe edit of the build.prop to fix this issue.
I've tried RR, LineageOS, NOS, ViperOS, CosmicOS, AOSPA, AOSP Nougat and AOSP Oreo with Radon, Agni, ElementalX and Infected for kernels. All of them were at the latest version at that time. The firmwares used were (and still are) miuifirmware_kenzo_7.7.6 and miui_HMNote3ProGlobal_7.7.20_Firmware. Alongside those ROMs and kernels, I've used Kernel Aduitor. Having tried all of those, vibration had not worked fully. Sometimes, rarely, there was a gentle vibration when I pressed a button or letter, that's all. Though that gives me hope it can be fixed.
I really do need that vibration to work, it's how I used my alarms to wake up. Just sound doesn't cut it. School year's about to start and this being my final year, I want to go all in. But, I can do nothing if I'm asleep.
Please, for the love of me, provide sings useful feedback. I do need to fix it, and service centers aren't an option.
Thank you all.
PS0: I know it'll sound crazy, but if any dev reads this and wants to fix this issue, as I'm not the only one who faces it, please, at least send a message out leave a reply here. Any logs or other feedback, I'll be more than happy to try and provide!
PS1: I have not yet searched on MIUI forums. I do dislike all MIUI themed stuff.
:good::good::good::good:
Flash miui fastboot rom
Flash miui using miflash, it should get everything back to normal.
alright mates. i will try flashing the stock rom. i'll keep you posted for any difference.
0kanenas0 said:
alright mates. i will try flashing the stock rom. i'll keep you posted for any difference.
Click to expand...
Click to collapse
Any updates? Did it work?
---------- Post added at 01:33 AM ---------- Previous post was at 01:32 AM ----------
0kanenas0 said:
Device:
Redmi Note 3 Pro, Snapdragon, 2GB RAM, 16GB Internal.
Currently on ViperOS Coral with stock kernel. (latest version of magisk is installed)
Hey community (and hopefully devs)!
As the title suggests, (I think) I broke my vibration motor. Basically, I flashed two custom kernels on top of each other. I really don't have any more info about that, like which ROM or kernels I used. I know, there were warnings everywhere, I've seen them.
Anyway, all I'm asking is if there's any flashable zip or maybe edit of the build.prop to fix this issue.
I've tried RR, LineageOS, NOS, ViperOS, CosmicOS, AOSPA, AOSP Nougat and AOSP Oreo with Radon, Agni, ElementalX and Infected for kernels. All of them were at the latest version at that time. The firmwares used were (and still are) miuifirmware_kenzo_7.7.6 and miui_HMNote3ProGlobal_7.7.20_Firmware. Alongside those ROMs and kernels, I've used Kernel Aduitor. Having tried all of those, vibration had not worked fully. Sometimes, rarely, there was a gentle vibration when I pressed a button or letter, that's all. Though that gives me hope it can be fixed.
I really do need that vibration to work, it's how I used my alarms to wake up. Just sound doesn't cut it. School year's about to start and this being my final year, I want to go all in. But, I can do nothing if I'm asleep.
Please, for the love of me, provide sings useful feedback. I do need to fix it, and service centers aren't an option.
Thank you all.
PS0: I know it'll sound crazy, but if any dev reads this and wants to fix this issue, as I'm not the only one who faces it, please, at least send a message out leave a reply here. Any logs or other feedback, I'll be more than happy to try and provide!
PS1: I have not yet searched on MIUI forums. I do dislike all MIUI themed stuff.
:good::good::good::good:
Click to expand...
Click to collapse
I was on Viper 3.0 as well. Flashed ElementalX, then dirty flashed ROM, Flashed agni, dirty flashed ROM again and got this very problem.
Did you manage to fix it?
I did not flashlight the stock MIUI ROM, thus I do not know if that'd be a possible fix for this issue.
(I cannot stand anything premade, that I did not get to mess around. That's the reason why I didn't flash it.)
So I don't know how my vibration came back this morning but I lost it after a few hours.
This happened all of a sudden a few weeks after I lost the vibration under similar circumstances as stated in the OP.
This is quite surprising since it worked without any problems - it wasn't weak or inconsistent for the few hours I had it running today.
Could anyone please explain.
Hey there! I had the same problem. Problem arose when I was on CosmicOS on stock kernel. I don't have any service centres nearby so on the suggestion of my friend, I switched to NOS and the vibration motor started working after 2 days. Wierd, and I don't know whether CosmicOS was the problem but NOS has fixed it.
rkmadotra said:
Flash miui fastboot rom
Click to expand...
Click to collapse
ROM flash nahi ho rahi hai
Hi,
As the title stated, I have Redmi Note 3 SD with LineageOS installed. My phone suddenly dies at 40% when I put it on standby. Sometimes when I open camera app, it dies at 50%. I've tried many ROM including ViperOS, RR, but I haven't tried with MIUI yet mainly because I don't really like MIUI.
Have any of you guys get same experience as mine? What you guys do about it?
I'm planning to replace the battery because I thought it was the battery problem. But if you guys have any suggestions that would be great!
Thanks!
Update the IOS problem will be solved with new 11.2.1 version.
Just kidding
I would replace the Battery to fix issues like this if you the only one related to a specific Rom.
If you search trough the los thread you will see that some people had the same issue. I am not sure how they fixed it but i think some of the custom kernels had a patch to deal with this issue. I cant remember which one ( agni or radon) so you should search trough and/or ask those kernel developers.
This problem solved by changing kernel to francokernel. Thanks!
bradhawk said:
This problem solved by changing kernel to francokernel. Thanks!
Click to expand...
Click to collapse
try Nitrogen OS
I tried lots of naugat and Oreo ROMs in my kenzo.. but every rom has bug shutdown automatic if battery under 50%, i tried flash custom kernel radon or agni but its same. If you have same problem pls give me suggest rom & kernel .
My kenzo is 2gb variant
goriuscd said:
I tried lots of naugat and Oreo ROMs in my kenzo.. but every rom has bug shutdown automatic if battery under 50%, i tried flash custom kernel radon or agni but its same. If you have same problem pls give me suggest rom & kernel .
My kenzo is 2gb variant
Click to expand...
Click to collapse
My device is also 2gb. It doesnt shutdown even if battery is 5% or 8 %.. What bug u talking?
Does it happen on stock kernel too ?
Dont flash custom kernels. Stay on stock kernel and check if same problem happens.
Keep ur firmware updated to latest.
Do you clean flash rom ?
First Format data,
then wipe data reset,
flash rom, gapps
Reboot
I use Aosp Extended 5.7 Oreo..
naik2902 said:
My device is also 2gb. It doesnt shutdown even if battery is 5% or 8 %.. What bug u talking?
Does it happen on stock kernel too ?
Dont flash custom kernels. Stay on stock kernel and check if same problem happens.
Keep ur firmware updated to latest.
Do you clean flash rom ?
First Format data,
then wipe data reset,
flash rom, gapps
Reboot
I use Aosp Extended 5.7 Oreo..
Click to expand...
Click to collapse
This issue not all device, just some device facing this issue.
I try with stock kernel but same,
yes i always do as you say. But still there.
Any suggest nougat rom? I dont like oreo rom, coz battery drain fast in my device
What do you thing about aex 5.7?? It is good battery backup?? I always use 4g
goriuscd said:
This issue not all device, just some device facing this issue.
I try with stock kernel but same,
yes i always do as you say. But still there.
Any suggest nougat rom? I dont like oreo rom, coz battery drain fast in my device
What do you thing about aex 5.7?? It is good battery backup?? I always use 4g
Click to expand...
Click to collapse
Yes oreo has battery drain issue when mobile data is on.
Install aex nougat.
https://forum.xda-developers.com/redmi-note-3/development/rom-aospextended-rom-v1-2-t3506955
Update AospExtended 4.6
[21.10.17]
- Enable selfie mirror by default
- Tweak adaptive brightness
Escrima X12 Kamui-LightingBlade-PurpleElectricity
- Merge latest CAF tag
- Fix few deadlocks and memory leaks
- Merged KRACK Patch and security patch
- Fix Autoshutdown issue
- Add FingerprintID resume feature from OnePlus
- Fix fingerprint sometimes not detecting
- Light sensor fixes
- Fix Battery % issues
- Pushed Readahead value to 512
- Enable Arch power saving
The issue of Autoshutdowns was because of the Voltage Cut-Off values for Mi Max as implemented in the LOS kernel. This was causing issues on kenzo/Kate. So we reverted back to the Old Values of Voltage Cut Off from Kenzo-OSS. This took some time and lot of research. Although the sudden casue of this issue is unknown and that too happening with few users. I can't thank enough to these people
@neonkat - Tanay
@Umang96 - Umang
@psndna88 - Parvinder
@Adarsh001 - AdarshMR
@wight554
@BlackDragonz - Tester
I tried merging and picking a lot of stuff along with Psndna from his Agni to my Escrima. Thanks to Umang for the commit and pointing out where the issue was.
Again, thanks everyone for the collaborative work!
This is an explanation from amolamrit when many of user facing autoshutdown issue in those rom
goriuscd said:
Update AospExtended 4.6
[21.10.17]
- Enable selfie mirror by default
- Tweak adaptive brightness
Escrima X12 Kamui-LightingBlade-PurpleElectricity
- Merge latest CAF tag
- Fix few deadlocks and memory leaks
- Merged KRACK Patch and security patch
- Fix Autoshutdown issue
- Add FingerprintID resume feature from OnePlus
- Fix fingerprint sometimes not detecting
- Light sensor fixes
- Fix Battery % issues
- Pushed Readahead value to 512
- Enable Arch power saving
The issue of Autoshutdowns was because of the Voltage Cut-Off values for Mi Max as implemented in the LOS kernel. This was causing issues on kenzo/Kate. So we reverted back to the Old Values of Voltage Cut Off from Kenzo-OSS. This took some time and lot of research. Although the sudden casue of this issue is unknown and that too happening with few users. I can't thank enough to these people
@neonkat - Tanay
@Umang96 - Umang
@psndna88 - Parvinder
@Adarsh001 - AdarshMR
@wight554
@BlackDragonz - Tester
I tried merging and picking a lot of stuff along with Psndna from his Agni to my Escrima. Thanks to Umang for the commit and pointing out where the issue was.
Again, thanks everyone for the collaborative work!
This is an explanation from amolamrit when many of user facing autoshutdown issue in those rom
Click to expand...
Click to collapse
So u r not experiencing any shutdown on Aex 4.6 nougat ?
What about Aex Oreo 5.7 ? Did u face auto shutdown ?
naik2902 said:
So u r not experiencing any shutdown on Aex 4.6 nougat ?
What about Aex Oreo 5.7 ? Did u face auto shutdown ?
Click to expand...
Click to collapse
In latest aex 4.6 if battery under 20% its draining so fast,
In aex 5.7 dont know. I search nougat rom with good batery backup, no problem if its an old rom, any suggest?
@goriuscd did you find a solution to that problem ?