[Q] SECAM_ERR: sony_sensor_reg_write: 0x0304 is failed - Xperia Arc Q&A, Help & Troubleshooting

Hi,
When starting the camera on my ARC, the android log is showing the following error (as being the first in a long list):
SECAM_ERR: sony_sensor_reg_write: 0x0304 is failed.
SECAM_ERR: Failed to init a sensor driver
It does so with different firmware versions and also after a Sony repair with PC companion.
Does any have an idea if this issue concerns:
= some software and/or firmware concerning a sensor driver
or
= an hardware of some dysfunctional sensor ?
TIA.
Paul

jungoso said:
SECAM_ERR: Failed to init a sensor driver
Click to expand...
Click to collapse
Sounds like HW to me, and if it's the same on other and the Stock ROM then that should tell you something.

Related

[Q] Camera take blurry pictures

Hello
My problem is for the rear camera of SGG I9082 which makes blurry picture
I check into the forum and found that have similar threat for SGS3 where it is proposed to be updates the CAM FW
When I dail *#34971539# and check the Phone to CAM FW Write (rear), it is displaying me:
Invalid Version
Cam FW Ver: A08B0S1GC01
Phone FW Ver: O08B0SAGD01
For the front camera it is make better picture (at lease for 2Mpx camera) and when I check the Phone to CAM FW Write (front), it is displaying me:
This is is the latest version
.... and the Cam FW Ver and the Phone FW Ver are matching
Please advice me what might be the problem that the rear camera is making blurry pictures and if the problem is the above, then please give me the proper FW for my rear camera and advice me how to install it
PS: All other activities like cleaning the camera or set-up it are done and nothing solve the problem
Thank you
ivotm81 said:
Hello
My problem is for the rear camera of SGG I9082 which makes blurry picture
I check into the forum and found that have similar threat for SGS3 where it is proposed to be updates the CAM FW
When I dail *#34971539# and check the Phone to CAM FW Write (rear), it is displaying me:
[...]
Please advice me what might be the problem that the rear camera is making blurry pictures and if the problem is the above, then please give me the proper FW for my rear camera and advice me how to install it
PS: All other activities like cleaning the camera or set-up it are done and nothing solve the problem
Thank you
Click to expand...
Click to collapse
Did you flashed a custom firmware?
I flashed CosmicCM (the latest) and had the impression that the pictures were kind of blurred or foggy. I reversed back to original 4.2.2 and the pictures got normal.
llinco said:
Did you flashed a custom firmware?
I flashed CosmicCM (the latest) and had the impression that the pictures were kind of blurred or foggy. I reversed back to original 4.2.2 and the pictures got normal.
Click to expand...
Click to collapse
No, I didn't do any flashing, I use the original (4.2.2) FW. it seem that for me only the driver for the camera is not installed (or it is installed the wrong one), All the other have no issue
U tried anything
Did u try to do anything via root like deleting some files or modifying something, u can try factory reset or problem may be on hardware base too that some dust may have entered glass of camera and causing dificulty in focus(ur problem was not focusing or not opening rear camera???) u could try using google camera too sometimes some file of camera get missing and u may try third party softwares...Hope it helps
loveymangal said:
Did u try to do anything via root like deleting some files or modifying something, u can try factory reset or problem may be on hardware base too that some dust may have entered glass of camera and causing dificulty in focus(ur problem was not focusing or not opening rear camera???) u could try using google camera too sometimes some file of camera get missing and u may try third party softwares...Hope it helps
Click to expand...
Click to collapse
Hello loveymangal
I didn't do anything like deleteing any sys files. About the reset I already try it several times - it didn't help. About the other topic yes they might create the problem, but at the moment I see that the FW of the rear camera is incorrect. If I have the possibility to to fix this issue and see if the problem reamin then I can go to the other possible problems (like the ones you are proposing). If someone can send me the install FW file for the rear camera to try if this is the issue will be great. About 3-rd party SW if you have the possibility to propose me some good will be great
Thank you
ivotm81 said:
Hello loveymangal
I didn't do anything like deleteing any sys files. About the reset I already try it several times - it didn't help. About the other topic yes they might create the problem, but at the moment I see that the FW of the rear camera is incorrect. If I have the possibility to to fix this issue and see if the problem reamin then I can go to the other possible problems (like the ones you are proposing). If someone can send me the install FW file for the rear camera to try if this is the issue will be great. About 3-rd party SW if you have the possibility to propose me some good will be great
Thank you
Click to expand...
Click to collapse
well i don't know much about installing of firmware of camera so i recommend u to try a custom rom so to check if installing a new ROM updates or installs the correct version of Firmware. IF that doesn't work try reinstalling your mobile with official 4.2 upgrade so it can go back to factory settings unroot it and give service centre to reinstall the Firmware... Without device in hand actually I can't help much.....Hope somehow your problem gets solved...
Try a Camera app from the Play Store like CameraMX, did you try turning "anti-shake on in camera settings?

Stereo Verify?

Hi,
I'm the developer of Open Camera, and I've had a reports of people unable to install my application due to "error 504" - usually this kind of thing is some device or Google Play issue that could happen with anything, but these all seem specific to Lenovo devices, particularly the Lenovo Vibe S1.
Someone sent me a screenshot showing that these devices have a pre-installed application "Stereo Verify", which has the same package name net.sourceforge.opencamera .
It's unclear what this app Stereo Verify does - it doesn't show as an application that can be launched, it only shows under Settings/Apps. Someone managed to launch it with QuickShortcutMaker, and said it "runs rather strange and only front (selfie) camera app" - they said it didn't look anything like the stock Lenovo camera.
It also uses the same icon that the early versions of Open Camera used.
The immediate problem is that users of this device can't install Open Camera. The more general question is whether this application is based on early versions of Open Camera, and if so, does it comply with the GPL...
For anyone with Lenovo phones - do you have this mysterious "Stereo Verify" on your phone? Does it prevent you being able to install Open Camera? Anyone know what this app might do? Did anyone receive either the source code, or a written offer for the source code to Stereo Verify?
Anyone know of a way to solve the problem or "error 504" where a pre-installed application has the same package name?
Thanks in advance,
mark
It's okay
I'm using Lenovo Vibe P1(p1a42) S288(last update) I have root and xposed installed.Your app is working with every function(led etc.)
Sepkov said:
I'm using Lenovo Vibe P1(p1a42) S288(last update) I have root and xposed installed.Your app is working with every function(led etc.)
Click to expand...
Click to collapse
Can u please tell how to root my lenovo vibe p1

Mi 5S Fingerprint doesn't work

hello i'm mi 5s 4gb/128gb user
yesterday, i was using cyanogenmod 13 but i want to use miui again
so i restored nendroid backup from twrp recovery
that was start of diaster..
after this. fingerprint scanner mostly doesn't work
sometimes fingerprint scanner work correctly after reboot, it doesn't work.. and sometimes... it works...
i did many many method (global rom, china rom via edl mode, fastboot mode) but everything has same result,
so i looked at my logcat
it says
QFP : QfpThreadMatch::execute: match result -3: QFP_INSUFFICIENT_COVERAGE
with my finger or not logcat said same result
why my fingerprint scanner doesn't work?
is it hardware issue?
sorry for poor english
yesterday, i was using cyanogenmod 13.......is it hardware issue? .......
jlmcr87 said:
yesterday, i was using cyanogenmod 13.......is it hardware issue? .......
Click to expand...
Click to collapse
???
Maybe placebo effect but people are saying Global rom had improved fingertip detection rate.
If i were you, i would flash as stock as possible, recovery, bootloader, lock status, everything, just to determine software versus hardware failure.
Hope for the best, as this kind of life cycle premature failure freak me out, first stucked autofocus sensor now this!!!
jpg3927 said:
???
Click to expand...
Click to collapse
You change the software and then ask if it´s hardware?
jlmcr87 said:
You change the software and then ask if it´s hardware?
Click to expand...
Click to collapse
yes it's strange
jpg3927 said:
yes it's strange
Click to expand...
Click to collapse
I had a problem which seemed to be hardware related after flashing the Chinese developer ROM and then later restoring a Miui EU ROM from a backup. My problem was with audio - there was no sound coming from the speaker or headphone output. I did diagnostic tests which failed - indicating a hardware problem.
It was only after re flashing the EU Miui ROM that the problem was resolved.
EpicSauce said:
I had a problem which seemed to be hardware related after flashing the Chinese developer ROM and then later restoring a Miui EU ROM from a backup. My problem was with audio - there was no sound coming from the speaker or headphone output. I did diagnostic tests which failed - indicating a hardware problem.
It was only after re flashing the EU Miui ROM that the problem was resolved.
Click to expand...
Click to collapse
i solved it
i think this was problem of driver
so i needed rollback of driver
first. i flashed 6.10.13 eu rom over 6.12.29
it occurs bootloop
second. i flashed 6.12.29 over 6.10.13 again. and fingerprint works like charm again!
Exists the cyanogenmod for Mi5s?
Still very buggy. We have to wait for xiaomi to release the source code to get nice CM .
The fingerprint happened to me too, it just stopped working.
Flash the stable global using fastboot, it will erase everything, and will be great again.
Don't restore with Titanium backup, I had all kind of weird problems everytime I tried.
One of the worst fp sensors ever. I tried all the tricks mentioned in several places, detection rate stays very low.
Sent from my MI 5s using Tapatalk
LucaOwner said:
Exists the cyanogenmod for Mi5s?
Click to expand...
Click to collapse
Linage os

sensors is not working on U5ASL4 !

When i Update official firmware to (A705FNXXU5ASL4) with Odin my sensors is not working anymore
for Example :
changed adaptive brightness To outdoor mode
rotation not work
proximity sensor is not work in calls or telegram
in CPU-Z also they are not available.
i tried SEK and THR region but still have problem
and i cant Flash U4ASK6 firmware
plz help me
i seen another post of you i don't remember where , you can't downgrade since you are now on U5 binary, i don't think the cause is the update, bring your device to samsung center and they will repair it.

Development [SEPTEMBER PATCH][ROM][pixel UI based on OneUI 4.1][Samsung A52s 5G]

TESTIMONIALS
This ROM is September patch. Super light, ready for daily use, it comes with google ecosystem instead of Samsung Bloats
FEATURES
Heavily debloated (Scamsung Knox, Account, Services, Scamsung Cloud, many system apps,
background processes, backdoors, Samsung SMART features, Secure Folder) (around 230 deleted apps)
Pixelyfied (This means all stock apps as Dialer, Messages, Launcher and Recents
-got replaced by Lawnchair,-
and more got replaced by pixel apps)
Overall improvements: MCK KERNEL BY DEFAULT (Enabled HighEnd animations, improved battery by using my debloat and
some optimizations by using some custom props) (Enabled features like AOD clock, music,
performance mode QS tile, faster bootup, disabled crc for smoother and greater sound)
and many more waiting for you to find it.
HOW TO INSTALL IT
Flash the ROM using Salvo's TWRP. Just do the regular format. But if you are coming from RAY OS, please FLASH THE STOCK SUPER before, because the scheme uses by ray os rom doesnt work with my ROM. But if you are coming from stock rom, just flash it and forget. Flash the ROM also and Reboot.
AFTER BOOTING PROCESS
After you`ve booted up into the ROM, install this Magisk app. Open Magisk, and if it`s asking you to reboot, reboot.
Then, open it again and flash this magisk module to fix camera and Safety Net. And then reboot.
You may have to crash the camera app a few times after every reboot, that`s how Scamsung is doing on rooted devices.
In case you set gestures navigation bar, reboot it after.
IF THE DIALER IS CRASHING, JUST SET IT AS THE DEFAULT PHONE APP. From now you can enjoy my hard crafted ROM.
DOWNLOAD LINKS and sources
MEGA link for ROM : mega link
Our Telegram support group: TG Group
Kernel Source Code: MCK repo​
Really looking forward to my Samsung phone not having any bloat ware. Tyvm sir.
Scamsuck
reserved
* Updated to September patch - and aloy better than before.
* as of now simcard manager is broken, so dualsim users may have to suffer abit, but it s manageable* (i m working on fixing this) FIXED
Will the TWRP touch problem be fixed?
NickDeveloper said:
Will the TWRP touch problem be fixed?
Click to expand...
Click to collapse
Can't say for sure. It was fixed on m52 from what I understand so a52s should be as well in theory. The same fix didn't work on a52s though, but devs are still trying.
any update for this rom
MsuatafaKhatab said:
any update for this rom
Click to expand...
Click to collapse
Soon sir.
If possible, kindly include the Samsung automatic call recording feature and double-tap to switch-on / switch-off gestures too in your next rom release please.
GreenIce said:
If possible, kindly include the Samsung automatic call recording feature and double-tap to switch-on / switch-off gestures too in your next rom release please.
Click to expand...
Click to collapse
By default, it has these features. Call recording is present when u call. And by double tap you mean double tap to wake and put the phone into idle?
ronardnx said:
By default, it has these features. Call recording is present when u call. And by double tap you mean double tap to wake and put the phone into idle?
Click to expand...
Click to collapse
Thank you. Yes, I use double-tap wake.
It s working for me without issues )
ronardnx said:
It s working for me without issues )
Click to expand...
Click to collapse
Thank you, I am currently trying out another ROM, I'll check this ROM too in the next couple of weeks.
First of all thank you a lot for your amazing work ronardnx !
I followed your Tutorial but there are some points where i got stucked. The TWRP linked in your Tutorial wasnt able to boot. So i managed to get TWRP with this tutorial: https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-6-2-1-for-galaxy-a52s-5g.4488419/
After that i installed your rom with a usb otg and on the console i got the message "The ROM has been successfully installed. BE THE LIGHTNESS!". BUT after that i got the following error lines:
1. Failed to mount "/system_root" (Invalid Argument)
2. Failed to mount "/product" (Invalid Argument)
When i choose "Reboot System" i got the message "No OS installd! Are you sure you wish to reboot?". If i swiped right to reboot, it showed me the Samsung Logo with the red text information that this is not a original samsung firmware blabla...
And suddenly the phone turns off and trys to boot again (bootloop).
Are there any known solutions for that kind of problem?
luffy786 said:
First of all thank you a lot for your amazing work ronardnx !
I followed your Tutorial but there are some points where i got stucked. The TWRP linked in your Tutorial wasnt able to boot. So i managed to get TWRP with this tutorial: https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-6-2-1-for-galaxy-a52s-5g.4488419/
After that i installed your rom with a usb otg and on the console i got the message "The ROM has been successfully installed. BE THE LIGHTNESS!". BUT after that i got the following error lines:
1. Failed to mount "/system_root" (Invalid Argument)
2. Failed to mount "/product" (Invalid Argument)
When i choose "Reboot System" i got the message "No OS installd! Are you sure you wish to reboot?". If i swiped right to reboot, it showed me the Samsung Logo with the red text information that this is not a original samsung firmware blabla...
And suddenly the phone turns off and trys to boot again (bootloop).
Are there any known solutions for that kind of problem?
Click to expand...
Click to collapse
I will update it tomorrow. Now is all stable and better. Just use the twrp gave by salvo, aka @BlackMesa123 . I have reworked the rom from scratch
Sir can u plese help me , how i flash super , now i am on ray os 3, if possible please provide steps.
PranjalGoswami said:
Sir can u plese help me , how i flash super , now i am on ray os 3, if possible please provide steps.
Click to expand...
Click to collapse
Flash stock Rom if you coming from RayOS
PranjalGoswami said:
Sir can u plese help me , how i flash super , now i am on ray os 3, if possible please provide steps.
Click to expand...
Click to collapse
i will no longer do oneui craps
only making gsi atleast usable
Correct
Sir ,
Appreciate your work, os running very smoothly, bug i notice ,if wifi calling is on , incoming and outgoing call is automatically disconnected after picking call. Some magisk module also not working like magnater. Search option also not in settings.

Categories

Resources