Hi all, wondered if anyone can help.
I have a rooted note 2 running jedi x16 rom and all is fine.
I have been testing out some 4.2 roms but when ever I reboot the phone it starts fine and then after a bit I get an error message saying com.android.phone has stopped working, then my signal goes then wait a couple of seconds and it comes back and then all is fine with the phone.
This only happens after i reboot the phone.
Any help would be great.
Hi, I have a camera problem with my Nexus 5x 32Gb.
First time the camera didn't started was on stock N with locked bootloader. I've tried reboots but didn't started.
I've unlocked bootloader, rooted.... flashed a N rom and the camera worked for some hours and when i've accessed camera phone freezed and rebooted and then again got the "camera error. Can't connect to camera" message.,
I've flashed the vendor.img and again, worked for some hours then freezed, rebooted and camera error message...
I've read that in many cases a reboot or flashing the vendor soled the problem but not in my case.
Seems like the vendor partition got corrupted after a while?!
I've done some catlogs. The first one wes done with the working camera, last one with camera error.
I've tried reading those log but with no luck, if can someone find my problem i'd be grateful.
I really like this awesome phone! View attachment 2016-11-20-06-18-58.txt
View attachment 2016-11-20-07-50-23.txt
Hi! I am running the newest nightly of the LineageOS (14.1-20170220-nightly-bullhead) on my Nexus 5X with the newest twrp 3.0.2-2 and I always get the error "can't connect to camera" when I try to start the camera. It started with the update from the first nightly to the second nightly. After today's installation and no fix I made a clean install, same issue. I tried deleting cash same result. What can that be?
Flashed with a the stock Nougat firmware and it went fine except my camera and NFC no longer work at all.
Camera gives a vague "Camera error" error in every app that utilizes the camera, and NFC fails to turn on . Id like to upgrade to the new Pixel Experience that was posted but not really sure how to get to the latest build as every other one i've tried breaks the fingerprint sensor.
XT1710-01 Unlocked running Android 7.1 "Stock" build
Not sure if this will help but I had that same problem and it turned out to be the font size. I reset it to default and the camera worked. Hope it helps
I recently tried to install a few different ROMs with no success. After flashing, I'm stuck in what appears to be a bootloop. About 5 - 10 minutes after being in this "bootloop", the softkeys will respond for about a minute, then a message will pop up saying "Process System isn't responding" with wait and close options. The phone freezes and then restarts. On Marshmallow-based ROMs, I can (sometimes) get to the welcome screen, but then it freezes and the "Process System" message appears again. Some of the ROMs I have tried are: CrDroid 3.8.9 Unofficial by alexenferman; Slim6, as well as other LOS 14/14.1 based and CM 13/13.1 based ROMs.
Any help would be appreciated.
Edit: I came across this thread: https://forum.xda-developers.com/galaxy-s3-att/development/lineage-14-1-d2att-rom-t3774764/page12
It turns out LOS will do this if the cameras are "missing." When I did a screen replacement a while ago, I damaged the flex cable for the front camera. I ordered a new one from eBay, which should (hopefully) fix my issue.
timmy4767 said:
I recently tried to install a few different ROMs with no success. After flashing, I'm stuck in what appears to be a bootloop. About 5 - 10 minutes after being in this "bootloop", the softkeys will respond for about a minute, then a message will pop up saying "Process System isn't responding" with wait and close options. The phone freezes and then restarts. On Marshmallow-based ROMs, I can (sometimes) get to the welcome screen, but then it freezes and the "Process System" message appears again. Some of the ROMs I have tried are: CrDroid 3.8.9 Unofficial by alexenferman; Slim6, as well as other LOS 14/14.1 based and CM 13/13.1 based ROMs.
Any help would be appreciated.
Edit: I came across this thread: https://forum.xda-developers.com/galaxy-s3-att/development/lineage-14-1-d2att-rom-t3774764/page12
It turns out LOS will do this if the cameras are "missing." When I did a screen replacement a while ago, I damaged the flex cable for the front camera. I ordered a new one from eBay, which should (hopefully) fix my issue.
Click to expand...
Click to collapse
If you cleared all of the data and cache partitions before installing a new rom, this means that the camera is the issue. Let me know how it works for you!
CrDroid O/S works good on my old Samsung Galaxy S3 i747
I am also interested if your Samsung Galaxy S3 i747 is up and running. You mentioned that CrDroid O/S wasn't working for you.
While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CrDroid. I find that CrDroid is the best, most stable, fully functioning O/S that I have used to date.
I followed someone's advice and clean installed. Reset to factory settings. Cleared all cache, system settings, everything! When booting up CrDroid , took a long, long time to fully install. But I knew the battery charge was full, so I waited about 20 minutes.
Totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
Damn fine phones.
DavidWCS said:
I am also interested if your Samsung Galaxy S3 i747 is up and running. You mentioned that CrDroid O/S wasn't working for you.
While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CrDroid. I find that CrDroid is the best, most stable, fully functioning O/S that I have used to date.
I followed someone's advice and clean installed. Reset to factory settings. Cleared all cache, system settings, everything! When booting up CrDroid , took a long, long time to fully install. But I knew the battery charge was full, so I waited about 20 minutes.
Totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
Damn fine phones.
Click to expand...
Click to collapse
Sorry for the late reply, but my S3 is up and running! It turns out that the camera was the issue. After a quick replacement, it booted up. It did take ~20-25 minutes on first boot, but it's working fine. I did do some slight overclocking, but CrDroid seems to run smoothly, especially for an 8-year-old device.
timmy4767 said:
Sorry for the late reply, but my S3 is up and running! It turns out that the camera was the issue. After a quick replacement, it booted up. It did take ~20-25 minutes on first boot, but it's working fine. I did do some slight overclocking, but CrDroid seems to run smoothly, especially for an 8-year-old device.
Click to expand...
Click to collapse
Quick?
" . . . the camera was the issue. After a quick replacement . . . "
How did you replace the camera?
Or am I misunderstanding you?
Hmm, I reread your original post. You replaced a 'flex cable' for the camera? Then everything worked?
DavidWCS said:
Quick?
" . . . the camera was the issue. After a quick replacement . . . "
How did you replace the camera?
Or am I misunderstanding you?
Hmm, I reread your original post. You replaced a 'flex cable' for the camera? Then everything worked?
Click to expand...
Click to collapse
I damaged the flex cable for the front camera / light sensor assembly (https://www.phonepartworld.com/image/cache/data/Products/SAMSUNG/Galaxy%20S3/1-Samsung-Galaxy-S3-Front-Camera-Replacement-700x600.jpg) a few years back, causing the front camera to not work. I just had to replace the entire assembly. It looks like Lineage may have some sort of POST that at some point, checks for the presence of the cameras, and when it sees that one is missing, fails to boot.