So I got frustrated with constant disconnects on my Android Auto with Oreo 8.0 on my x4. I rooted and switched to Lineage in hopes of the problem getting fixed. Not only was it not fixed, the problem was worse... because AA did not launch at ALL on my infotainment system. So... I decided to flash back to latest factory image and then took the 28.2 update... then re-rooted and my Android Auto is working flawlessly now.
So after trying multiple ROM's of different kinds, from Nougat to Oreo and even a few marshmallow, I noticed one pattern. The camera is not A1 on Nougat+ ROM's. And the reason being is Open GAPPS. I would flash an Oreo ROM without GAPPS and would immediately open the camera app and would notice that it would start every single time and have no problems. But as soon as I flashed any GAPPS package, the camera would start to act up again and the vicious cycle would start back up again. I found an old RR for marshmallow and flashed 6.0 GAPPS and that worked flawlessly... For some reason... It could've been a driver issue, not sure. But my point is that GAPPS may be the problem with the camera on all of the Nougat and Oreo ROMS. I'm not exactly sure how this could be fixed as it doesn't seem very promising that it can be fixed.
Roms that I tried this out on
-BootleggersROM
-Havoc-OS
-Candy 8.1 BETA
Hi, I'm facing this issue with my oneplus 3T on custom roms. Doesnt matter if its a 9.0 custom rom or an oreo rom, it still happens and has become very difficult for me to use. I've tried Havoc 9.0, Nitrogen OS 9.0, OmniROM 8.1, Pixel Experience 8.1 but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. How can i fix this? My method of flashing a ROM is:
Wipe Cache/System/Internal Storage/Dalvik etc.
Install oneplus 3t firmware (5.0.6 oreo)
Install Custom ROM.
Install Gapps
Reboot.
P.S. It works absolutely fine on Oxygen OS (5.0.6)
Looking for help. Thanks!
shraey96 said:
Hi, I'm facing this issue with my oneplus 3T on custom roms. Doesnt matter if its a 9.0 custom rom or an oreo rom, it still happens and has become very difficult for me to use. I've tried Havoc 9.0, Nitrogen OS 9.0, OmniROM 8.1, Pixel Experience 8.1 but it still happens. Whenever the phone goes to sleep or i lock it, and then when i try to wake it up from the lock using either fingerprint or power button, the screen lights up in black and the two capacitive buttons light up, i can hear a lock screen sound also, but the display stays black. How can i fix this? My method of flashing a ROM is:
Wipe Cache/System/Internal Storage/Dalvik etc.
Install oneplus 3t firmware (5.0.6 oreo)
Install Custom ROM.
Install Gapps
Reboot.
P.S. It works absolutely fine on Oxygen OS (5.0.6)
Looking for help. Thanks!
Click to expand...
Click to collapse
Just a couple of ideas.
Try an older Firmware when you flash a custom ROM. 5.0.4 perhaps.
Double check that you're using the correct Gapps. Opengapps 8.1 or 9.0 depending on ROM, ARM64 Pico. Or try without Gapps.
Ensure TWRP is latest Official.
Do you Format Data when you 'Wipe'?
5.0.4 Firmware
Dirk said:
Just a couple of ideas.
Try an older Firmware when you flash a custom ROM. 5.0.4 perhaps.
Double check that you're using the correct Gapps. Opengapps 8.1 or 9.0 depending on ROM, ARM64 Pico. Or try without Gapps.
Ensure TWRP is latest Official.
Do you Format Data when you 'Wipe'?
5.0.4 Firmware
Click to expand...
Click to collapse
I'm using TWRP 2.3.2
Also, GAPPS are according to ROM, 8.1 or 9.0 ARM64 PICO.
Yes i Format Data when I 'Wipe'!
Still haven't got any fixes for this issues yet
got the exact same problem, on twrp 3.2.3-1, on 5.0.8 firmware and lineageos 16 rom.
it also happens in twrp (after screen timeout after 1 minute, it will stay black).
works fine on oxygenOS, also otherwise works perfectly, until screen lock is ever enabled...
I just bought it used, are you sure you have the original screen? something seems fishy about mine.
I had a regular Oneplus 3 (non-T) before, the fingerprint sensor definitely seems different (deeper down, as if there was a glass protector or the screen was thicker). Maybe that's normal. But the fingerprint sensor also isn't reacting very well - the one on my old Oneplus 3 was MUCH better.
edit:
https://imgur.com/a/Ndvptqg
oneplus 3 on the left, my 3t with the problem on the right. gsmarena lists both models as 7.4mm thickness, so I guess the 3T definitely has a non-standard screen still sad that it works fine on oxygenOS, is there a way to provide helpful logs?
I started experiencing this issue when i replaced my screen for one on Ebay. The notification light and the screen is somewhat dimmer. You can tell its not original.
I have stock android 10 with march security patch. With magisk and Buildprop I enabled cam2api. Gcam works but the stock camera keeps crashing. This wasn't an issue on android 9. I believe Xiaomi did this intentionally to prevent people from using gcam. Now even if i revert my Buildprop back to the backup still situation stays the same ( I don't know how gcam still works ).
So, I ask Is there any way I can stay on stock android 10 to use the stock cam and gcam at the same time as I use the stock camera's Manual mode.
Or, Is there any workaround or the only solution is to revert back to Android 9?
Thank you.
I resorted to the services of Ministry of Solutions this weekend after downgrading to EMUI 9.1 and now have an unlocked bootloader.
I would now need a stable ROM. I have now succeeded to boot Lineage 18.1, 17.1 and 16 in various format along with CAOS and some GSI ROM (phhusson). Unfortunately, the phone is unusable because on all ROMs one of the following issue arises:
the dialer is crashing: immediately hanging up despite the voice coming on and off on the speaker. Same issue with google dialer.
OR
the camera and file manager are not working: SD card not found / internal storage error
Anyone out there running a stable ROM willing to share? Any tips?
Go Back to to EMUI with eRecovery and then
Downgrade to EMUI 9.0.0.195 and try Custom Rom again!