Installed unofficial lineage os 17.1 but camera does not work - Samsung Galaxy Note 10+ Questions & Answers

I installed Ivan's Lineage OS rom, it works great. However, I have one main issue... the camera does not work. No matter what camera app I use, it just crashes.
I have tried using the kill camera app on F-Droid and restarted my phone multiple times to no avail.
If there are no solutions to this I might switch back to the stock rom.
Does anyone know a solution to this?

Related

Got a weird issue I can't track down, need help

Phone is a Samsung s3, sgh-T999L on tmobile.
Problem I am having is if I install anything above like pico gapps, basically anything that has more than like google play services, my camera on KK 4.4.x roms force closes and locks up.
I have narrowed it down to somthing withing the gapps packages that is causing the issue with the camera, but I cannot for the life of me track down what app is doing it, if it IS an app, my assumption is that it's an app that conflicts with the camera.
What I have done thus far is a Ful wipe, data, cache, internal, dalvik, etc....everthing, and I do this kind of wipe on every flash/install of roms.
I have tried cm11 full gapps, pa full, micro, and pico gapps, and every one of them except for the pico gapps, causes issues with the camera.
I have tried this on 3 different 4.4.4 roms....carbon rom, cm11 rom, and Octos KK rom, and all three have the exact same issue.
I first tried without using gapps and camera worked, so I then proceeded to try different versions of gapps, and narrowed it down to pico gapps works, while other gaps do not.
So has anyone else run into this issue or problem? I've tried searching google but I'm not exactly sure what to search for so I tried different search strings with no resolve, so I decided to post here and see if anyone else has had this issue.
In TW roms camera works fine, no issues. In KK roms useing just the minimal gapps (pico gapps) camera also works fine, using anything above the gapps package be it PA or cm, the camera does not function. When I say not function I mean it locks up, fc's, gives an errors of "cannot connect to camera" (I've done a search on that as well and got nothing).
So if anyone has had this issue and/or maybe has a fix, please please help!!!!!!
Thread moved to proper forum
Sent from my SM-G900T using XDA Premium 4 mobile app

OP3 - no camera after 03/23 LOS nightly

Hi,
I updated my phone to the latest nightly after updating to firmware 4.10 and now i don't have a camera app. When i try installing another one it tells me it can't connect to camera.
I tried wiping system, installing just the system image, installing GAPPS, everything; nothing seems to work.
Is there any possible solution to my problem?
Thanks.
you can try this
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
i saw the module support LOS.

Android Auto Broken for me since Oreo! Problem persists across OOS and Custom Roms!

I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?

Fingerprint Settings Crash in multiple ROMs

Hi I've got a 5t I started on FreedomOS, which was fine, but was still running 7.1.
I wanted to use MicroG, so opted for OmniROM and it was working perfectly. Then I found that WIFI tethering wouldn't work, not matter what I did full reset, apn settings, nothing worked.
I then thought I'd try Resurrection Remix and had it all setup and working. Then went to enter a lock code and it worked, then when I went to enter a fingerprint settings crashed and each time I opened settings it crashed. I had setup from scratch multiple times and tried both the OnePlus 3 and 4 firmwares. I had MicroG working via the Xposed module, so Omni is definitely my preferred option.
I then tested LineageOS and settings crash also when going to setup fingerprint or go to security settings at all.
I have done about 5 full formats including storage. It's kind of like the settings haven't been removed.
All I want is a clean ROM with MicroG support and a few customizations such as battery, dark theme etc, but have had no success.
I love the amount of support and customizations available for the OnePlus and that's was the main reason I got it.
Does anyone have any idea or something else I could try?
davoidd said:
Does anyone have any idea or something else I could try?
Click to expand...
Click to collapse
Have you tried a different firmware yet? Sounds firmware related - need the right firmware for the right ROM. OmniRom has that in the OP. Also just did some quick research on MicroG and found https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 if magisk is more desirable to you.
Hi thanks for your reply. I'm not sure why it happened, but have partly resolved it. I just switched to lineageos with native microg support.
Seems like removing some of these files can help. As even a full wipe doesn't remove these settings.
By removing these seemed to fix it.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
/data/system/users/0/settings_fingerprint.xml
You may also delete the following file if it exists
/data/validity/template.db

Latest OTA Update to Pixel 3a killed the camera!

I accepted the latest OTA update for lineage. After the reboot my camera app shows a black screen for the main camera and crashes after a few seconds.
What I've tried:
Messing with the camera app, permissions etc.
Trying other camera apps, same problem.
Rebooting.
Since I wanted to see what grapheneOS was like I tried installing that.
Same problem....?
Okay so then I thought they might be sharing the same camera driver. So I installed...
The latest Google factory image.
Then I tried reverting to Android 11 (everything was 12 before)
Main camera is still dead. Selfie camera works.

Categories

Resources