Hello!
I recently updated to 4.3 and rooted the device using Odin, however the default camera app is no longer responding - it gives me the following error message: "Unfortunately, Camera has stopped working".
Things I've done to try and fix it:
1- cleaned cache and data but that didn't solve the problem.
2- also reset the device to factory through settings but it didn't work either
3- re-install camera.apk (wouldn't install using Titanium)
4- install new stock camera from 4.3 rom (installed but got the same message)
5- manually replaced the files for the camera (system/app/SamsungCamera.apk and SamsungCamera.odex) AND Gallery (SecGallery2013.apk and SecGallery2013.apk) with new ones
Issue still persists...
Any ideas? Pls help.
Thanks!
if you're using xpose mod and wanam update to the latest wanam.
ragomes14 said:
Hello!
I recently updated to 4.3 and rooted the device using Odin, however the default camera app is no longer responding - it gives me the following error message: "Unfortunately, Camera has stopped working".
Things I've done to try and fix it:
1- cleaned cache and data but that didn't solve the problem.
2- also reset the device to factory through settings but it didn't work either
3- re-install camera.apk (wouldn't install using Titanium)
4- install new stock camera from 4.3 rom (installed but got the same message)
5- manually replaced the files for the camera (system/app/SamsungCamera.apk and SamsungCamera.odex) AND Gallery (SecGallery2013.apk and SecGallery2013.apk) with new ones
Issue still persists...
Any ideas? Pls help.
Thanks!
Click to expand...
Click to collapse
ascrackoo1 said:
if you're using xpose mod and wanam update to the latest wanam.
Click to expand...
Click to collapse
Thanks but it didn't work.
I got it solved today thou in an unexpected way by actually using the Back up feature within ROM Manager - the phone went into back up mode (like recovery mode where you see the little android robot and command lines), waited until the back up process was finished then rebooted without choosing the option to "fix possible root loss" warning. After that camera was finally back again.
Then I recalled that the last time I've done this back up through Rom Manager there was some sort of problem during the process which interrupted it so I realize now that somehow it affected the camera (have no idea how they relate thou) - but the fact is that as soon as it successfully finished the back up the issue was automatically fixed. Weird, stupid and very rare, I know... At least is fixed!
ragomes14 said:
Thanks but it didn't work.
I got it solved today thou in an unexpected way by actually using the Back up feature within ROM Manager - the phone went into back up mode (like recovery mode where you see the little android robot and command lines), waited until the back up process was finished then rebooted without choosing the option to "fix possible root loss" warning. After that camera was finally back again.
Then I recalled that the last time I've done this back up through Rom Manager there was some sort of problem during the process which interrupted it so I realize now that somehow it affected the camera (have no idea how they relate thou) - but the fact is that as soon as it successfully finished the back up the issue was automatically fixed. Weird, stupid and very rare, I know... At least is fixed!
Click to expand...
Click to collapse
Not to thread jack, but do you have the apk for the stock camera app from 4.3? Thanks in advance
I've had exactly this same problem. Do I have to run a backup to fix it?
Since KitKat I can't create paired windows and save them to the side bar. I get a dialog box that says "Unable to add". How do I fix this?
working fine for me with stock rooted so seems to be an individual issue.
are you rooted ?
did you flash any custom rom ?
did you try the same after full wipe ?
I installed lineage-14.1 and at first installed the GApps Aroma package and it said it installed fine but nothing was installed when my phone booted up. No app store, gmail, nothing. So I started over and installed the pico package which gave me the playstore. Its a start and I downloaded what I needed. However as im playing around with my phone I am noticing some annoyances
- Not detecting my contacts from sim card or from google ( sim card is detected an calls/mms work)
- certain apps not even working such as the camera app. Not so much a problem as I can download a functional one from the playstore but I would like the issue resolved
- Cant root the phone, I tried towel root, kingroot, and Odin (which is how I originally rooted it)
- missing settings such as turning off the touch button lights
Any ideas? Suggestions for a different custom rom? Big thanks in advance
What is the phone model?
The phone is running the latest bootloader and modem?
What version of TWRP did you use?
Tried different versions of Open Gapps (http://opengapps.org/)?
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?
I have some issues with certain apps on an unrooted Galaxy S8+ Exynos running LineageOS 17.1 (Android 10.0) with TWRP recovery installed.
I own a Galaxy Watch Active, and I attempted to install the Galaxy Wear app from the Play Store and opened it, and got a 'Operating System on your phone has been modified in an unauthorised way' error. I also own Galaxy Buds+ which I need to pair as well (using standard bluetooth with them for now). How do I fix this issue? (bear in mind I'm not rooted)
The HSBC UK app is also messing around a bit, every time I open it and click the checkbox next to 'I accept the terms and conditions', it reboots my phone and crashes the app. Is this a general Android 10 issue with support for the HSBC app, or an anti-custom ROM move from HSBC? And if this is the case, how would I fix this too?
A more general issue is that Google Pay isn't working. It says my phone isn't supported to make payments in-store via NFC because it has been rooted (it hasn't been rooted, just installed a custom ROM). I didn't pass the SafetyNet test. It was installed with gapps by the way.
The least important issue is the Transport for London app, which says that my phone has been tampered with and is no longer supported by TfL and the app closes. Any way to trick the app into thinking I am not running a custom ROM?
Thank you so much for reading and I'd really appreciate your help! Thanks!
Did you manage to find a fix for the HSBC UK app reboot/crashing problem? I am having the same issue, but on Havoc OS running Android 11 rooted with Magisk.