Magnetic sensor and proximity sensor not working - ONE Q&A, Help & Troubleshooting

Hi all!
I'm encountering some really strange event on my phone.
** Note: all the test I've dopne are on the end of this post. **
Even In a fresh installed ROM (clean wipe) there is no trace of the sensor.
Tests done:
Stock images tested (with full fastboot rewrite of every partition):
- 11.0
- 12.0
- 12.1
- 13.1
Custom ROMS:
@Sultanxda 12.1 cyanogenmod and 13.1 cyanogenmod
Official cyanogen:
- 13.1
- 14.1
Tested with Recovery:
- Stock Recovery
- Cyanogen's recovery
- TWRP (Bacon ad hoc version)
Tested Modems:
all the stock versions.
Teared open the entire phone, checked soldering points and connectors.
All check.
I'll listen to ANY suggestion.

i had 3 opos on 1 i think on the 2.4 release the c07 firmware breaked those Sensors

Related

[ROM][5.0.2][STOCK][FLASHABLE ZIP] Identity Crisis ROM (Single-SIM)

Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
Important Notice: This ROM can be flashed with either TWRP 2.8.1.0 or Philz Touch Recovery v6.55.0, however restoring backups is not straight forward. The only reliable way to restore a KitKat backup is to use this method.
.: Identity Crisis ROM (Single-SIM) :.​(Android 5.0.2)​Lollipop Bootloader not required​This ROM has been built from the latest firmware for XT1063 - Stock Android 5.0.2 (v22.21.28).
Yes, you read correctly; this is a Moto G (2nd Generation) ROM running on XT1032.
XT1032 Lollipop Radio Firmware available here.​First boot can take a few minutes.​Screen flicker is due to Kernel. Turn screen off once to fix. Custom stock kernels in the future might solve this.​
Features:
Stock XT1032 5.0.2 Kernel
Debloated (Motorola apps still available in Play Store)
Zipaligned
Rooted
Busybox
'Cast Screen' Enabled
OTA Updates | Motorola Notifications Disabled
MultiROM compatible - TBC
init.d Script Support
Post-install zipaligning (Darky / Fly-On Mod™)​
How to flash:
1) Sideload or download ROM to internal storage.
2) Boot into Custom Recovery.
3) Factory Reset (System, Data, Cache, Dalvik)
4) Flash zip, reboot.
This ROM requires a F2FS 'userdata' partition.
If you are GPE, or have ever been; you may need to convert to Stock. More info in FAQ here.​​
Working:
Almost everything​
Not Working:
Compass
CDMA or Dual-SIM support​
Tips:
Stock Boot Animation (Flash in Recovery)
Problems restoring TWRP backup? Read this and this
Speed up animations in Developer options - Instructions
"OK Google" / Google Search not working? Available in Play Store
Want Face Unlock? Flash this
Battery Percent Enabler
Adblock Plus issue
Faster GPS locking: Try this app
Enable Automatic Battery Saving Mode: Settings > Battery > Menu Button > Battery saver > Turn on automatically @ 5% or 15%​
Download v006 (355MB)​
v005
Download v005 (334MB) [Mirror]​
Screenshots:
http://forum.xda-developers.com/devdb/project/?id=7715#screenshots​
Changelog:
30/01/15 - v005 - Now using XT1032 Kernel / Modules. Fixed Camera issue. Updated SuperSU. Re-added Stock Equalizer (Sound > Audio effects)
22/01/15 - v004 - New build to fix audio issues
20/01/15 - v003 - Fixed APK issue (Thanks mounkg, VitaTaf); added ROM name to 'About phone' screen
17/01/15 - v002 - Fixed Speaker audio and Auto-rotate
16/01/15 - Initial release
XDA:DevDB Information
Identity Crisis ROM, ROM for the Moto G
Contributors
lost101, mounkg, VitaTaf
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: XT1063 (Titan) Stock Android 5.0.2 | Build: LXB22.46-28
Version Information
Status: Stable
Current Beta Version: v006
Created 2015-01-16
Last Updated 2015-02-22
Woe dude,awesome work! I will try this as soon as i get home!
Interesting ROM
Regarding Recoveries... What about the newer TWRP builds? Do they work properly with lollipop?
k-kuchen said:
Interesting ROM
Regarding Recoveries... What about the newer TWRP builds? Do they work properly with lollipop?
Click to expand...
Click to collapse
Work on Lollipop support has yet to begin.
Where is it? ?
Link up now. Sorry for the delay.
Twrp failed to flash, even after wiping internal storage, latest philz flashed fine. Working great on my xt1032
jikobutsu said:
Twrp failed to flash, even after wiping internal storage, latest philz flashed fine. Working great on my xt1032
Click to expand...
Click to collapse
TWRP needs a reboot if you wipe internal storage.
The ROM has no sound, and I mean everywhere ?
I made a test call and that had sound.
lost101 said:
I made a test call and that had sound.
Click to expand...
Click to collapse
can you test music playback? Or games sounds?
on mto g 1032 converted to gpe stuck at boot ... booting over 20 minutes now ... may i do migration maybe to f2fs ??
DeHuMaNiZeD said:
can you test music playback? Or games sounds?
Click to expand...
Click to collapse
I can't check until morning. A sound driver fix may be needed, should be only a small zip.
wts1 said:
on mto g 1032 converted to gpe stuck at boot ... booting over 20 minutes now ... may i do migration maybe to f2fs ??
Click to expand...
Click to collapse
Yes, f2fs required.
not working : audio , auto rotate
Made it with Phils recovery. Boot it in 3-4 min.. Rom is fast and smooth. Audio and rotate don't work, but if u fix that it would be great. Thanks @lost101
wts1 said:
not working : audio , auto rotate
Click to expand...
Click to collapse
bobrda said:
Made it with Phils recovery. Boot it in 3-4 min.. Rom is fast and smooth. Audio and rotate don't work, but if u fix that it would be great. Thanks @lost101
Click to expand...
Click to collapse
was about to flash it when i read this... too bad
will wait a little bit, in the meantime updating cm12
Can't wait for the audio fix.
Great ROM waiting for audio fix
Sent from my XT1032 using XDA Free mobile app
I actually contacted Shawn5162 a few hours before posting this. I asked him if he would consider a release of his ROM for Moto G (1st Gen) because I could see it might be possible, and told him how.
I made the decision to release a very basic ROM based on a pure stock system dump, for others to use as a launchpad for their own work. This ROM doesn't have most the features of the 'Titan Prime' ROM, because it's not a port of that ROM.
I don't mind changing the name if Shawn wants, and I am happy to credit anyone.
FYI: The codename of XT1063 is Titan.
EDIT: Now called 'Identity Crisis ROM' - the original working title...should have stuck with that.
With XT1063, the main speaker is front-facing.
A temporary solution is to re-route all audio to the earpiece speaker using SoundAbout.

Can't update from CM 12.1 to CM 13 on shieldtablet

Hi!
My shieldtablet is running CM 12.1 (latest 20160807 build)... That works fine. It has latest TWRP 3.0.2-2 installed. And latest open GAPPS 5.1 (mini arm).
I am trying to get it to run CM 13 I've tried the first builds... didn't work... I tried today with the very latest nightly build 20160909... I do this by booting to recovery (TWRP 3.0.2-2) then going to install, and installing cm-13-20160909-NIGHTLY-shieldtablet.zip, and also open_gapps-arm-6.0-mini-20160912.zip (using the install multiple ZIPs feature of TWRP). Then I wipe DAVIK and cache and reboot.
Device stays forever at the nvidia logo.
I turn it off. Boot to recovery, reinstall CM 12.1 and opengapps 5.1 with same process... and that works fine. Machine reboots like a charm.
Any idea if I am missing a step? And what step that would be?
Thanks in advance,
Gilles.
Have you done the firmware update?
http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
Firmware Update:
If you have not installed the latest stock ota, then some firmware files need updated. The following flashable zips will update the bootloader and the dtb corresponding with the listed stock version. Only the latest one listed here will be supported by recent CM builds.
3.1.1 (L)
4.2.0 (M)
Ah... No. I'm confused, though. What's the difference between L and M files? Do I need to flash both? Or just one?
I'm running CM 12.1 (Android 5.1.1 Lollipop)... So I could imagine having to flash L? But since I'm updating to 6.0.1... Would that mean M?
I imagine I download the ZIP, boot into TWRP, flash the right version. Then flash CM 13. Then flash Open GAPPS?
Or in a different order?
Thanks,
Gilles
I'm on stock, so it's just a shot in the dark - but i think this sounds logical:
L - Lollipop - 5.x, flash this when you are on 13.0 and want back to 12.1
M - Marshmallow - 6.x, flash this when you are on 12.1 and want flash 13.0
and then cm + gapps of course
regards,
wakko
All in one shot? Boot to TRWP, flash M, CM, GAPPS then reboot?
Hopefully - you'll only find out, when you try
So... that's exactly what I did, and it worked.
So steps : log into the SHIELD (CM 12.1 / Android 5.5.1)
Reboot to recovery (configured advanced reboot in developer options)
From recovery, selected the M drivers, then added the CM 13 zip, then added the Open GAPPS (6.0 ARM MINI) ZIP.
Then clicked FLASH
Then rebooted (I was impatient, didn't think to clear DALVIK and cache).
Machine rebooted and all seems well (SD card was detected and I said use as portable storage, Avast asked for a few more permissions, only Viber got confused and requires relinking to mobile account).
All nice.
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
ggravier said:
One issue is that the lock screen doesn't follow device rotation. It stays configured for portrait mode. Once I log in, and get to the main launcher screen, then the screen orientation properly follows device rotation.
Click to expand...
Click to collapse
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Steel01 said:
That default changed in cm13. Dunno if it was an aosp change or cm. You can toggle it back on under settings->display->rotation.
Click to expand...
Click to collapse
Thanks! Solved! So far, I love it!
ggravier said:
Thanks! Solved! So far, I love it!
Click to expand...
Click to collapse
I am having the exact same issues as OP. Not tried this fix yet, but seems promising. Question is, does any of those L or M files wotk with Nougat? or is there one for that too?

[ROMS][7.1.2][d838] Resurrection Remix N, LineageOS 14.1, Mokee N[stable]

Disclaimer:
/* **Your warranty is now void.** * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. * */
Resurrection Remix N
This rom is for D838 variant, maybe works on others, but I have not tested.
Working:
-Wifi
-Ril
-Camera (rear, front, video)
-Sound
-SDCard
-DT2W (Double tap to wake)
-Bluetooth
-NFC
Bugs:
-Tell me
LineageOS 14.1
Working:
-same as RR N
Bugs:
-same as RR N
Installation:
-same as RR N
Downloads:
Latest builds:
Mokee June Update:
-June security patch level
-Kernel and device tree updates
link : https://drive.google.com/open?id=1etfqN8e1C5VxvBdtyJmuSuDkIxRTg2vh
Mokee May Update:
-May security patch level
-Kernel and device tree updates
-Enabled zRam
link : https://drive.google.com/open?id=1El4BRvm0ehAMm7TzA1EiiHfRPYGDNGKr
February updates: (MOKEE N, LINEAGEOS 14.1, RR N
Download
Changelog:
-Kernel and device tree updates
-New governors and IO schedulers
-February security patch and ROM updates
(I'm gonna update RR and LineageOS soon)
December update:
https://drive.google.com/open?id=1jHwwNxaMJ91-iTOuSqm0jYRjzSuJO3jK[/SIZE][/B]
Only LineageOS is rooted, for other roms flash magisk.
Changelog:
-Kernel, device tree, rom updates
-December security patch level
Resurrection Remix N
RR-N-v5.8.5 20171010
link: https://1drv.ms/u/s!Ai3bT6KNVyQEiD62G-CtstEulJu0
news: RR updates, kernel updates, October security patch, etc
This is final build of RR based on Nougat
Lineage
lineage-14.1-20171013
link: https://1drv.ms/u/s!Ai3bT6KNVyQEiEArgg1WboOrj7B_
news: LineageOS updates, kernel updates, October security patch
This is final build of LineageOS based on Nougat[/B]
Installation:
You need twrp recovery by @xenius9 : https://forum.xda-developers.com/lg-g-pro-2/development/twrp-recovery-lg-g-pro-2-t3318686
1. MAKE BACKUP!!!
2. Push baseband , ROM and gapps to sdcard (copy cm13 zip and LP Baseband to sd card)
3. Make WIPE dalvik, data,cache(from recovery)(advanced wipe in twrp)
4. Install lollipop baseband
5. Install ROM
6. Install gapps
Additional links:
KK Baseband and kernel - https://yadi.sk/d/nVx3rb7MpheN9
LP Baseband and kernel(bumped)+KK bootloader - https://yadi.sk/d/_hz4jdQhpheNn
How to Restore previous ROM:
1. if you have KK based Rom - flash KK Baseband and restore ROM from Recovery
2. if you have LP based Rom - flash LP Baseband and restore ROM from Recovery
How to install twrp on kitkat:
1. You need ROOT
2. Download and install this apk: https://drive.google.com/file/d/0B4kfGU1z_PCla2pxMW9ZZWgzX3M/view?usp=sharing
3. Download updated TWRP zip and put to internal storage or sdcard: https://drive.google.com/file/d/0B0LH2ajSZjDpalVsQmpoTDBfTUE/view
4. Open installed app, grant root access, flash recovery
5. Reboot into recovery (via apk or power off phone, press power and volume down button until lg logo come up, release buttons for one second than press volume up and volume down, select yes and again yes. This will not erase your memory if you have TWRP flashed)
6. Flash updated TWRP
7. Reboot into recovery again
How to install TWRP on lollipop:
1. Need ROOT
2. Download and install LG drivers from here : https://drive.google.com/file/d/0B4kfGU1z_PClSWVlY0FGWWJoVFE/view?usp=sharing
3. Download and extract this files: https://drive.google.com/file/d/0B4kfGU1z_PClQ3AyM2lKOGR1S3M/view?usp=sharing
4. Enable usb debugging under developer options
5. Connect phone to pc via MTP
6. Run d838recovery.bat (You will see chinese language, just press any button to flash recovery)
7. Allow usb debugging and grant root access
8. DO NOT REMOVE USB CABLE
9. After finishing process press any key to reboot into TWRP recovery
TWRP 3.2.1-0
link: https://drive.google.com/file/d/1ADfHyz8ii6w_QErKkzhrKexTQ4a6cAXp/view?usp=sharing
to update from older twrp just flash zip
Recommended GAPPS (google apps) : http://opengapps.org/
Older builds
RR
link: https://drive.google.com/file/d/0B4kfGU1z_PClbmJUTkdGUnpYYlU/view?usp=sharing
Lineage
link: https://drive.google.com/open?id=0B4kfGU1z_PClbURaNm5ST1FMeVE
lineage-14.1-20170624
link: https://drive.google.com/file/d/0B4kfGU1z_PClRk5XV0pSS0hfMk0/view?usp=sharing
lineage-14.1-20170613
link: https://drive.google.com/open?id=0B4kfGU1z_PClSlBJd0djcWFHcDQ
Resurrection Remix M
Resurrection Remix M
-Based on @xenius9 Cyanogenmod 13
-Everything works
-Tested on D838 (I don't have F350 to test)
link: https://drive.google.com/file/d/0B4kfGU1z_PClaU02WVZMNHB0OVk/view?usp=sharing
LineageOS 13.0 (rebranded and updated CyanogenMod 13 )
Bugs: Same as CM13 and RR
Installation: Same as CM13 and RR
Link: https://drive.google.com/file/d/0B4kfGU1z_PClWDlobDhlSmZCbzA/view?usp=sharing
kernel and device tree sources: https://github.com/coavasic
thanks to:
@xenius9
RESURRECTION REMIX team
CyanogedMod
G2/G3 developers
Good, I am waiting for nuogat.
If I am already using Lollipop, do I need to flash lillipop baseband?
Does it have superSU, is it root?
yplim2300 said:
If I am already using Lollipop, do I need to flash lillipop baseband?
Does it have superSU, is it root?
Click to expand...
Click to collapse
No need, it has root
So nice?
I will flash it later.
Finished test on d838.
Done, its work very well! Vietnamese 99%, but isn't problem.
Best rom for me. But it play not good with stock rom. I play Mobius Final Fantasy with medium graphic and frame, some time it freeze 0,01s ^.^. Stock rom no problem. Can you fix it?
Hi, I am running this Rom now. So far so good no issue yet.
I found G Pro2 little slow though perhaps the storage or ram management.
which gapp should i should for this rom?i always get "unfortunately, google play has stopped"
g2mantap said:
which gapp should i should for this rom?i always get "unfortunately, google play has stopped"
Click to expand...
Click to collapse
i'm using this without any problem
https://www.androidfilehost.com/?fid=24591000424961929
coavasic said:
i'm using this without any problem
https://www.androidfilehost.com/?fid=24591000424961929
Click to expand...
Click to collapse
You flash this with Recovery?
We should choose ARM or ARM64 to download?
Yes, arm
Sent from my LG-D838 using Tapatalk
UPDATE: Let it go for a couple of hours and it seems fine OMG.
UPDATE 2: The second boot up takes a really long time too. I'm still waiting for it to boot up.
UPDATE 3: IT BOOTED UP! But it took seriously long. Tested Soft Reboot seems quick, now testing full reboot.
UPDATE 4: Seems like I should never do a full reboot or shut down on this. Holy **** it's long.
Not having a great time flashing this... Using TWRP 3.0.2-0 to flash the ROM somehow it doesn't go past starting apps. Doesn't seem to boot on CM13 as well.
I've tried:
- Full wipe (system, cache, dalvik, data) and normal wipe (cache, dalvik, data)
- Installing the ROM with and without GAPPS
- Installing LP Baseband & Kernel (found in CM13 thread) with ROM with and without GAPPS
ROM would refer to either RR and CM13.
No SD card inserted, tried having SIM card in or out, the only thing I have not tried is to put the camera back in (stock ROM works without camera).
how to install.. just flash baseband and rom and gapps? thats it? ty
pato2015 said:
how to install.. just flash baseband and rom and gapps? thats it? ty
Click to expand...
Click to collapse
Installation is same as CM13, if you are on lollipop/cm rom you don't need to flash baseband, just rom and gapps, if you are on kitkat flash lollipop baseband in cm13 thread.
@coavasic how long does it take for your phone to do a full reboot? Seems like it takes 45 minutes for mine to boot.
DJCrapsody said:
@coavasic how long does it take for your phone to do a full reboot? Seems like it takes 45 minutes for mine to boot.
Click to expand...
Click to collapse
about 1 min. It's just on this rom or same with cm13?
coavasic said:
about 1 min. It's just on this rom or same with cm13?
Click to expand...
Click to collapse
It's the same with CM13. Doesn't happen on stock or modded stock ROM though.
It's a LG D838 32GB Variant.
Update: Seems like the camera does not work after hooking it back up (it works when I'm on Stock ROM), could it be because the system has already registered it as a non-camera device as I did flash it without the camera hooked up. But I did also flash the Stock ROM without the camera and hooking the camera back on still allowed it to work... Hmm....
Update 2: Device feels sluggish compared to when on the stock ROM, when lucky, app just lags for a second, when unlucky, it hangs for a few minutes then crashes.
@coavasic it's definitely a CM thing, I just reflashed a modified stock ROM (Sphinx Pro v5a) and it booted up in seconds.
coavasic said:
-Based on @xenius9 Cyanogenmod 13
-Everything works
-Tested on D838 (I don't have F350 to test)
link: https://drive.google.com/file/d/0B4kfGU1z_PClaU02WVZMNHB0OVk/view?usp=sharing
kernel and device tree sources: https://github.com/coavasic
I will create this rom based on CM14.1 (nougat) when we have all basic functions working on Cm14.1
thanks to:
@xenius9
RESURRECTION REMIX M team
CyanogedMod
G2/G3 developers
Click to expand...
Click to collapse
just as suggestion....stock camera for this rom is not really good perfomance becoz the image not so bright......i already try installing lenovo super camera version 3.6.7 and it give much better result...hope u can replace the stock camera app
Working Perfectly On LG G Pro 2 F350S, Thanks For Beautiful ROM

[Q] LineageOS Nightly Dirty Flashing

I hope someone can help me here. I recently moved from CyanogenMod 13.1 to LineageOS 14.1 (fully wiping my phone). I haven't had any issues with LineageOS until I try to dirty flash a nightly build. I never had issues dirty flashing with CM, so I'm not sure what's going on. I just tried flashing the 7/25 build from the 7/18 build and the latest gapps. Upon rebooting, my D850 just sits at the boot screen (13 minutes now). When I restore from my TWRP backup, my phone will boot back up after about 3 minutes (for the first boot). Am I missing a step when flashing nightlies?

OnePlus 6, Lineage OS 16: Missing fingerprint support

I installed Lineage OS in the following order
- install current stock rom: 9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_31f86cec5f8d4c7b.zip
- wipe system, factory reset
- install Lineage OS: lineage-16.0-20191122-nightly-enchilada-signed.zip
Unfortunately, Lineage OS has no fingerprint support (setting not available). When I go back to the official stock rom fingerprint is working as expected.
Thanks for your replies.

Categories

Resources