Database Users

[Solved] Proximity Sensor Failure - Screen off in calls in CM7? come in!

Found the solution!
It was by matlacki, basically just reflash stock ruu 1.32, re-root and restore your nanadroid and it's all good.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
==================================================
Btw i am using build 30
For those who having this proximity sensor issue like myself , I done a test.
Go to setting > CyanogenMod setting >display > automatic backlight > > tick use custom > edit other levels.
For me I can see my sensor functioning will. 7 for total darkness and 59 for din light and 190+ for lamp.
Now try to make a call and watch the screen go off. You can't on it back but there's still ringing tone.
I used my nexus one flash to shine on the sensor and my screen turned back on.
Now go back to the edit other lvl notice that the light sensor doesn't response to the different brightness.
A reboot will fix the problem but if there's s phone call,this bug starts again. Try it!!!
And share your results. If there's ppl with the same as mine, it might be a cm7 bug and not s proximity sensor failure

Its not a CM7 bug. I have never had the proximity sensor problem on any ROM, be it stock or otherwise.
I'm also using build 30 and no proximity sensor problem to report.

i want to believe its not a CM7 bug.
For the past 2 weeks when I was using various CM7 builds, I do not have any proximity issues as described by other users till yesterday, it just popped up.
Nandroid to my old backup (which has no such the problem), and problem still persist.

flashed back to RUU 1.32 rom and the sensor is working in sense rom.
So now i cant even send back for a replacement.

matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!

This problem started yesterday evening for me. 5days of CM7 without issues and now this dealbreaker. Need to pull battery after end of a call.
Sent from my Desire HD using XDA App

try flashing 1.32 RUU and redo the whole rooting again > and back to CM7.
seems unreal but it really did solve my problem..

Okay...
I'm having the same problem, i just checked it with the program "Sensorlist" which gives me info about the proximity sensor....
With CM7 it doesn't work, but with stock rooted ROM it works fine...
So it must be a problem with the CM7 software....
Has anyone solved the problem, so it doesn't come back?

Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?

My findings (with input from Apache14):
- The proximity issue only affects those with a non-Sharp LCD.
- The kernel source code released by HTC does not contain the correct code to handle this device. I am still looking for solutions.
- On the 1.32 kernel, when proximity is required, some polling mechanism is activated. I assume this is needed as there is no Interrupt hooked up on a hardware level on this LCD/chip (same sensor uC however).
- There is no source code for this. Not in HTC released kernel source or CM or AOSP.
Currently I am looking at either:
- Getting the latest source code for the DHD kernel which HTC has failed to release. The source code corresponds to some RUU older than 1.32.
or
- Hacking the kernel to do the same polling as present in the 1.32 kernel binaries.

McKebapp said:
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
Click to expand...
Click to collapse
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App

Numsefis said:
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Didn't remove them from the ROM.
I simply unticked them while/before restoring my FullBackup with TitaniumBackup.

For those that cant get proximity sensor to work on custom kernel/ROMS, try the following (no root required):
Code:
echo '0x50530b0c 0x140b0b0c' > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will adjust the calibration values. The 0b part is the 'low tide' aka FAR start and 0c is the 'high tide' aka NEAR start.
IOW, values below FAR start is FAR, and values above NEAR start is NEAR.
Tested this on latest Buzz (Apache14) kernel.
Need to somehow make this persistent, and make sure it does not get reset during normal operation.
Stay tuned
Update: Still thinking of how to apply this at boot, maybe 'init.d' ? Also havent been reset during normal operation.

Thanks for the info

ok but how do you appli that ?
Text editor ? etc.

Flashing default (stock ruu) kernel
did it for me. Prox sensor working as intended.
Sent from my Revolutionized Desire HD using XDA App

I wrote an app to fix this.
See http://forum.xda-developers.com/showthread.php?p=11312762#post11312762.

Great work Leppie!

I had this problem, wile on CM6, started after I installed ADW EX. Used to use launcher pro, but realy liked the transisions in ex, so started using that, and got this problem. Updated to CM7, stil had the problem, no matter rom version. Went back to launcher pro, and now it works like normal. Thinking ther might be something with the launcher, and mabye a hardwere thing in some phones.
I am now on nihtly CM7 34, I think, and no problem.
So for those having this prob, try to switch to another launcher, and reboot a couple of times.
Hope this helps

how did you downgrade?
with Recovery?! or with Gold card?!
i have done both ways but didn't solve my problem :-(
please give me a link of Stock rom ruu!

[Help] W-lan

Hiho guys,
didnt know where to ask else just got this big problem and hope one of you can help me ! (please no need posts like "use search option" ... used it ... didnt help)
Since 1-2 weeks my wlan doesnt work. worked perfectly before but now it doesnt.
first thought its cause of rixtas theme but than I switched from lightning+theme to checkrom v4 full wipe ... still didnt work
now I flashed stock rom ki4 and after it kh3(definitely worked on this one about 2 weeks ago) ... still doesnt work.
The Problem described is:
I hit the connect to W-lan botton ... it tries to connect and then on settings (wlan) is an "error" written below the wlan turn on button
or
It just switches wlan on ... tries to find networks but after about 5 secounds it just turns off again as never anything happened (wlan of course are available ... no mac or anything (open and secured wlans tested))
current system:
lightning 6.1 (kh3) - rixtas black chrome - rage kernel - titanium backup pro (maybe there is something wrong?!? but still after full wipe and stock rom?!?)
really hope that someone can help me !!!
greetz

You have to be more precise in your description. There is no "W-lan botton" on my phone! Infact there is nothing labeled "W-lan" either.
Do you mean the "WPS button connection" in "Wi-Fi Settings"? I never use that button but instead prefer to manually enter the details myself have you tried that?
Are you sure this is not a problem with your router setup? Have you tried connecting to a different WiFi router? (Edit: reread your post - answer yes!)
{Build:KI4 Version:1.3.4 (stock, rooted)}

LouisJB said:
You have to be more precise in your description. There is no "W-lan botton" on my phone! Infact there is nothing labeled "W-lan" either.
Do you mean the "WPS button connection" in "Wi-Fi Settings"? I never use that button but instead prefer to manually enter the details myself have you tried that?
Are you sure this is not a problem with your router setup? Have you tried connecting to a different WiFi router? (Edit: reread your post - answer yes!)
{Build:KI4 Version:1.3.4 (stock, rooted)}
Click to expand...
Click to collapse
I meant: settings -> wifi -> wlan-settings (below offline-modus) and there on the top I can turn wlan on or of ... if I try to turn it on it sometimes just give me an error written below wlan or other times it turns on... scans for networks ... an just turnsoff again after a few secounds ... its definitely a problem on the phone not on the router
it there a possibilty to read the error msg ?!? ... or to test the hardware if it works or is broken?

hmm doesnt anybody know something about this problem ?!? or possibilities to solve it ?

Just the usual - revert everything back to stock with a complete wipe/ hard reset of everything and if still faulty return under warranty.
Your symptoms sound more like software than hardware, but if you are able to completely revert the phone back to it's factory state then if it still does not work it must be a hardware fault.
{Build:KI4, Version:1.3.4 (stock, rooted)}

Thinking about it, a similar thing happened on one of our work development phones. It refused to connect. I found the problem by run "adb logcat" from the PC command prompt with the phone in debug mode. (Or use the catlog app) there was an helpful error message. I ended up deleting (renaming to be safe) one of the network configuration files. A new config file was then automatically re-generated and the network started working again! I can't remember which file it was but it contained all the saved network connections names in a text file.
{Build:KI4, Version:1.3.4 (stock, rooted)}

LouisJB said:
Thinking about it, a similar thing happened on one of our work development phones. It refused to connect. I found the problem by run "adb logcat" from the PC command prompt with the phone in debug mode. (Or use the catlog app) there was an helpful error message. I ended up deleting (renaming to be safe) one of the network configuration files. A new config file was then automatically re-generated and the network started working again! I can't remember which file it was but it contained all the saved network connections names in a text file.
{Build:KI4, Version:1.3.4 (stock, rooted)}
Click to expand...
Click to collapse
gonna try this ... already tried to full wipe it and flashed it back to stock ... but it didnt work ... will see ... probably just try this log thing today and post it if something happens ... if its useless I gonna send it back with warranty ... just need my jig

tried logcat and log collector but I guess I need some advises on this ones ...
logcat: I hit record ... collect filename ... than it says that its recording and one second later it saved (so stoped already ) ... nothing is in the logs ...
log collector just gives me:
Log Collector version: 1.1.0
Device model: GT-I9100
Firmware version: 2.3.4
Kernel version: 2.6.35.7-RAGEmod-U1-v1.1a
[email protected]) )
#10 SMP PREEMPT Wed Sep 14 22:44:43 CST 2011
Build number: Lite'ning Rom v6.1 XXKH3~Universal-Theme
... already known this

I still need help please

Did you try flashing stock kernel? Did you try full wipe (/wipe system, /wipe data, /wipe cache, /wipe dalvik-cache)?

I am having the exact same problem as Weste90 on my i9100.
When I turn on WiFi, it stays on for a 9-10 secs and turns itself off automatically.
I am using the official firmware. I tried using 2.3.5 (installed using odin from samfirmware.com) and the same problem remained.
Now i am back to KF3 (Installed by Kies) . Details in screenshots...
I have tried Factory reset and clearing cache (by volume up+home+power button menu).
Still no luck. Any ideas?

Both posters with problems please confirm that you have done the _four_ wipes suggested by xzx0O0.
Please try again the catlog app, there should be loads of logs in it.
also try installing the "Wifi Analyzer" app and post a screen shot.
I still think this is a software issue rather than hardware.
{Build:KI4, Version:1.3.4 (stock, rooted)}

zxz0O0 said:
Did you try flashing stock kernel? Did you try full wipe (/wipe system, /wipe data, /wipe cache, /wipe dalvik-cache)?
Click to expand...
Click to collapse
yes ...was meant in first post
LouisJB said:
Both posters with problems please confirm that you have done the _four_ wipes suggested by xzx0O0.
Please try again the catlog app, there should be loads of logs in it.
http://tapatalk.com/mu/5284f8be-9fac-a405.jpg
also try installing the "Wifi Analyzer" app and post a screen shot.
I still think this is a software issue rather than hardware.
{Build:KI4, Version:1.3.4 (stock, rooted)}
Click to expand...
Click to collapse
done it like he said already ... didnt help ... and the prob with log is that I probably use it wrong ... it just asks me how to call the file ... but saves instantly after it and doesnt record ...
edit:
just tried wifi analyzer ... this app say me when I start it that it needs connected wifi ... tries to connect permanent ... say me again that it needs connected wifi and so it goes on

LouisJB said:
Both posters with problems please confirm that you have done the _four_ wipes suggested by xzx0O0.
Click to expand...
Click to collapse
Please elaborate on the "four wipes"
I have reset factory settings + Cleared cache ... What else do I need to do.

abhsjain said:
Please elaborate on the "four wipes"
I have reset factory settings + Cleared cache ... What else do I need to do.
Click to expand...
Click to collapse
in clockworkmod
wipe system
wipe data
wipe cache
wipe dalvik-cache

Wifi analyzer works fine for me without being connected to a wifi router see sceen shot.
So does catlog. If you really can't get catlog working download the Android sdk to your PC and run adb.
Maybe it is a hardware fault.
{Build:KI4, Version:1.3.4 (stock, rooted)}

so flashed back to complete stock ke4 ... wifi analyzer still strikes it service ... just tries permanent to connect to wifi ...
but I got catlog running ! ... screenshots coming soon

so just cutted all the screenshots together ... ^^ hope I didnt mess up something...
first one is my phone stats and what wifi analyzer does ... or doesnt ^^
http://imageshack.us/f/535/sc20111006105221.jpg/
secound one is catlog ... made some screenshots ... didnt know on what I have to concentrate ... so I uploaded everything ^^ ... if u can tell me what I have to look for I can make new one ... (on the fourth screenshot I turned wifi on)
http://imageshack.us/f/535/sc20111006111323.jpg/

new topic: http://forum.xda-developers.com/showthread.php?p=18236849#post18236849
this can be closed ... thanks to LouisJB ... would be unbelievable happy if u can help me (in the other topic ! ^^)

[Q] Both cameras not working

Bought an S4 last week. Everything looked good, I tested the sound, vibrate, gps etc and it all checked out. However, stupid me didn't check the camera (I know I know).
So the whole phone seems to run fine, but the camera (front and back) can't be accessed by stock or 3rd party applications. (Usually "warning Camera Failed" or something similar). I've factory reset, cleared cache and everything. I even installed the nandroid backup from a working phone, but the camera gives the same issue.
Because it's both cameras I thought it had to be software, but after all the resets and cache clears I'm starting to lean toward hardware.
Can someone give me an idea where to start? Would it be camera connectors or motherboard? Is there a sensor that may be causing this? I'd like to get an idea before I start gutting my phone.
Thanks.

Try this if it works for you?
https://www.dropbox.com/s/xha0lztrny7923s/Restart_Camera.apk?dl=0
If this does not help, clear RAM with a ram cleaner and try starting the app again?
If that does not help either..flash stock rom via oding
If that does not help..turn the phone off..charge till 100%..turn the phone on..clear the ram..and start camera..
Sent from my GT-I9500 using XDA Free mobile app

Had this same issue a while back. What solved it for me was to re-flash the stock firmware. I too tried a nandroid backup, it didn't work but the flash did.

Turns out it was software related.
I installed a few stock firmwares that didn't fix anything. I didn't want to wait the 2 hours to download for free from Sammobile.com, but eventually i bit the bullet and got the appropriate (latest) version of my phone. After the reboot it was solved.
Granted, I tried many different firmwares, and some had the same name as the official firmware that i downloaded from sammobile but it did the trick.
Thanks for the pointers

Camera Not Recording (log inside)

Greetings,
The camera on my Note 3 is not working for video recording (taking pics works fine). I have switched a lot of roms and kernels on it, but I noticed the camera app would not record and, instead, show me a "Warning: Recording Error" followed by a force close and, usually, a reboot.
I decided to switch back to stock Lollipop to see if this would revert it, but it didn't work.
The phone specs and other info:
SM-9005
Currently on official Lollipop from Brazil (N9005VJUGBOD5_N9005ZTOGBOD4_ZTO from sammobile)
Stock kernel
These are the things I did to try and fix this, not in order:
1- Changed kernels
2- Changed roms (always wiping everything but internals on recovery before doing so)
3- Cleaned cache
4- Cleaned camera cache
5- Tried google camera app instead of the official camera app (it did not FC, but while it said it was recording, it would never save a video file of it)
6- Did a factory reset on the stock rom
7- Updated modem and bootloader with the files on the Aryamod thread
8- Tried removing the SD card completely
9- Tried reseating the SD card
10- Tried changing to internal card in the camera app
11- Changing recording resolution options
Last custom rom I had was the Omega Rom. First Lollipop rom I installed was the official (non leaked) Poland rom, and I did not use a pit file back then (as, according to the thread this was featured it, that file was meant only for users coming from the leaked lollipop rom).
This is the log from the camera bugging out in the Omega Rom:
http://pastebin.com/TkCA2KbT
I took a second one for precaution:
http://pastebin.com/1exMLTk3
This is not a hardware problem as it worked on KK. The problem persists on the official rom I just installed. Also, the SD card has a lot of space available, as does the internal memory.
Also, not sure if this is relevant, but most kernels give me a bootloop, exception being the Omega kernel and the Darkqueen. I also *may* have flashed by accident a rom based on Cyanogen at some point, but my memory is very fuzzy on this. I think that this wouldn't matter as I wipe everything before putting a new rom in, anyway (and if I did that, the new and now correct rom I put after that wouldn't leave any traces of this accident).
I have no idea what else to do to fix this.

I have exactly the same problem. I have a ZTO Note 3 with the same problem as well, sometimes the whole android crashes after I try to record it.
The whole problem began after I installed the Omega Rom, I used CM12.1 for quite some time and the camera record correctly. I am not sure if you managed to wipe the whole thing by using the TWRP, but once I did, I found out that it was a MTO problem, which I searched about and it was nothing major.
Did you manage to fix the problem?

Maybe install latest bootloader?

Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?

Journyman16 said:
Try changing the camera app video resolution back to 1080P - there's been a number of people had problems with UHD mode.
It's quite possible that BL and Modem flash will not work unless you turn the phone off and then go into DL mode for an Odin flash - rebooting into DL mode doesn't let them flash. So maybe once you went to a ROM that had the UHD issue, you haven't fully come back to stock?
Click to expand...
Click to collapse
white7561 said:
Maybe install latest bootloader?
Click to expand...
Click to collapse
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?

Leminur said:
Sorry for the time taken, I flashed the Omega Rom once again using TWRP, and then I flashed the bootloader and modem recommended for such rom using Odin, but the problem still continues. And I have tried change resolutions, storage and everything possible, the problem still continues.
Funny thing is, I thought it was the back camera problem, it could take photos but it freezes during video recording. Once I tried the front camera, the same problem happens as well, it does take pictures, but it does not record.
I am getting a little desperate now, I have a feeling that the omega rom made such problem but as of yet it did not fix said problem! What should I do?
Click to expand...
Click to collapse
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.

Video not recording
Do you have a link to the kernel and has anyone else tried this? I'm also having the same problem with the video recording not working and I'm not sure what to do about it.
chickenlittlesound said:
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
---------- Post added at 04:45 AM ---------- Previous post was at 04:40 AM ----------
Hi, I have the same problem on my note 3 and the only way to fix its installing the kernel civato v2.2 .(only work with v2.2)
i hope work for you.
Click to expand...
Click to collapse

I'm having exact same problem
I'm also having this exact same problem with my N9005 Note 3. Its running Lollipop but i don't really much about roms as i bought it used from some shop. Everything works fine both cameras take pictures but video recording doesn't work at all. Also i downloaded a screen roader app and its videos are also not recorded. When i finish recording them and go to gallery it says File Corrupted. Please anyone got fix of this problem yet?

So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

Hi everybody,
@hayder78,
I tried to do the same to fix the issue: flash with the last firmware available for my region code (XEF - N9005XXUGBOK6) using Odin 3.11.1 and the same options (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update) but I still have the issue.
@Fenrir007
Did you manage to fix the issue using the same method?

I had the same issue with a 6.0.1 ROM (MagMa-NX UX8.5) on my Note 3 N9005. Any attempt to record video merely resulted in a "recording failed" message after about a second.
I thought I had installed a recent bootloader and modem using Odin 3.11.1, but although I did it twice I had used a "Reboot to Download" restart and for some reason that does not seem to have taken properly - although I have no idea why, all the display messages said it had worked.
So I have just done a full (remove battery and then three-finger power-up) boot into Download as advised in this thread, and then sent the same BL_N9005XXSGBQA1 and CP_N9005XXUGBOJ2 files to the phone via Odin, and now video recording works fine.
So when people say clean boot into Download, they do actually mean it. Thanks folks!
Oh, and I did NOT need to tick the "clear EFS" option, which seemed a rather risky thing to try so I was avoiding it as long as I could.
Andre

Note 3 camera doesn't work

My wife's Note 3 has got a camera error. When trying to take a picture I get this error message (translated from Swedish): A server error occured. Restart camera. If I set language to English the error message is only: Camera error.
I have changed the camera unit to a new one, with no result.
Anybody had this problem before?
Phone has Android 5.0 installed, and always used stock ROM.

Was the phone dropped or exposed to moisture? If not, it could be a defective camera.
You can buy a third party and replace it yourself.

dextrose said:
My wife's Note 3 has got a camera error. When trying to take a picture I get this error message (translated from Swedish): A server error occured. Restart camera. If I set language to English the error message is only: Camera error.
I have changed the camera unit to a new one, with no result.
Anybody had this problem before?
Phone has Android 5.0 installed, and always used stock ROM.
Click to expand...
Click to collapse
I know you mention that you always used stock ROM but, maybe you should try a clean and fresh stock ROM flash, erasing everything possible and wiping everything
That would be a last resort, of course. Maybe some app or setting is interfering with your camera.

audit13 said:
Was the phone dropped or exposed to moisture? If not, it could be a defective camera.
You can buy a third party and replace it yourself.
Click to expand...
Click to collapse
Phone has not been dropped or exposed to moisture and as I wrote in my post, camera unit is changed to a new one. Same problem anyway.

ShaDisNX255 said:
I know you mention that you always used stock ROM but, maybe you should try a clean and fresh stock ROM flash, erasing everything possible and wiping everything
That would be a last resort, of course. Maybe some app or setting is interfering with your camera.
Click to expand...
Click to collapse
Thanks for your suggestion, I think I will try as a last resort!!
How do I set Odin to erase/wipe everything possible?

Where did you get the camera replacement? Is it possible the replacement camera is bad?

dextrose said:
Thanks for your suggestion, I think I will try as a last resort!!
How do I set Odin to erase/wipe everything possible?
Click to expand...
Click to collapse
I usually flash TWRP and format the /DATA partition, then boot in download mode and flash stock ROM when I start from scratch.

try installing a different camera app like open camera.
enter service mode *#0*# and test mega cam and front cam.
try reboot your phone in safe mode (power off, power on, volume down on samsung logo).
wipe cache from recovery (also dalvik cache if you on custome recovery).
complete wipe from recovery.
flash rom with odin.
if none of these steps worked, i guess it's a hardware problem.