Just rooted S8.. Selective Focus in Camera not working anymore - Samsung Galaxy S8 Questions and Answers

Hi guys,
Just rooted my S8 and installed TWRP, using STOCK Samsung ROM, AQH3. I noticed in the Camera that "Selective Focus" is not working anymore. I didn't change anything else, just rooted the device and installed Notorious Kernel, before doing this the Selective Focus was working OK. So does anyone know what happened? Any help would be highly appreciated, I really like this shooting mode. Thank you!
EDIT: To clarify: before this I got sometimes the error, but mostly of the time it worked well. Now after rooting the phone and installing TWRP it doesn't work at all in any conditions, even with different subjects.. I've heard someone reporting this issue in another thread, but I can't remember at all

Root these days is nothing but problems.

Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera

blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Flash stock firmware through Odin and then check again if this solve the issue.
Also which method of root? Magisk or SuperSu?

I used Magisk. Anyway if I'll flash stock firmware through Odin I'll lose TWRP and root and everything else right?

blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Seems like kernel related issue

Mmmh so you suggest to try changing kernel and/or flashing the stock one to see if the issue persists?

Related

[Q] Flash(LED) disabled in Camera app after flashing Kitkat 4.4

I followed Efrant's guide (http://forum.xda-developers.com/showthread.php?t=2010312) for flashing Android 4.4 stock image(I was previously on 4.3 rooted stock).
After the upgrade, when i tested the new stock camera app, I noticed that the Flash option is disabled(Flash symbol with strike-grayed out). I'm not able to change it to Flash or Auto-Flash mode. Then i downloaded another camera app(Focal cam), and there the Camera flash was working properly.So, I guess the problem is with Stock camera app(It seems to think that my N4 doesn't have an LED Flash).
Am I the only one facing this issue or are ppl out there with same issue ? I tried googling and searching here, but could not find this being mentioned before. Any work arounds (other than a 3rd party camera app) for this problem? If yes, then please let me know.
P.S: I'm already feeling bad about flashing 4.4 update(It is missing out most of the UI changes. I, so, envy N5 users ! Hell with you google )
Exactly the same problem and exactly the same feelings. Were you able to find a fix for this?
badhri said:
I followed Efrant's guide (http://forum.xda-developers.com/showthread.php?t=2010312) for flashing Android 4.4 stock image(I was previously on 4.3 rooted stock).
After the upgrade, when i tested the new stock camera app, I noticed that the Flash option is disabled(Flash symbol with strike-grayed out). I'm not able to change it to Flash or Auto-Flash mode. Then i downloaded another camera app(Focal cam), and there the Camera flash was working properly.So, I guess the problem is with Stock camera app(It seems to think that my N4 doesn't have an LED Flash).
Am I the only one facing this issue or are ppl out there with same issue ? I tried googling and searching here, but could not find this being mentioned before. Any work arounds (other than a 3rd party camera app) for this problem? If yes, then please let me know.
P.S: I'm already feeling bad about flashing 4.4 update(It is missing out most of the UI changes. I, so, envy N5 users ! Hell with you google )
Click to expand...
Click to collapse
Fixed! Just read about the KRT16S build that got pushed out. Re-imaged my Nexus 4 (no patience to wait for OTA) with this latest build and yes, this fixes the camera LED flash issue (it is now enabled). :good:
shikhanshu said:
Exactly the same problem and exactly the same feelings. Were you able to find a fix for this?
Click to expand...
Click to collapse

Can't connct to camera. I beg of your help.

Hello and thank you for taking the time.
I recently gotten this message popping up everytime I try to use the camera on my S4.
"Can't connect to camera". I'm not sure why this is happening, so I thought maybe perhaps it had to do with the camera itself
so I went ahead and got the camera part replaced and got a new camera and it still shows this :'( I spent a lot of money getting this new camera part and I still get this message.
Can some one please help me? I sincerely ask because I am losing hope.
I am currently running a PAC-MAN ROM
Thank you again!
Mkami said:
Hello and thank you for taking the time.
I recently gotten this message popping up everytime I try to use the camera on my S4.
"Can't connect to camera". I'm not sure why this is happening, so I thought maybe perhaps it had to do with the camera itself
so I went ahead and got the camera part replaced and got a new camera and it still shows this :'( I spent a lot of money getting this new camera part and I still get this message.
Can some one please help me? I sincerely ask because I am losing hope.
I am currently running a PAC-MAN ROM
Thank you again!
Click to expand...
Click to collapse
I'd recommend Odin back to stock. If the camera works then you know it was a software issue with your ROM. If not, then you most likely have a hardware issue.
Or if you you think that is too extreme, just try reinstalling your ROM first.
guut13 said:
I'd recommend Odin back to stock. If the camera works then you know it was a software issue with your ROM. If not, then you most likely have a hardware issue.
Or if you you think that is too extreme, just try reinstalling your ROM first.
Click to expand...
Click to collapse
Thank you so much for replying. I am sincerely grateful.
The front camera works just fine. Its the rear camera.
I have wiped and installed my ROM into the phone hoping that'll work but nothing. I also tried another ROM still nothing.
What you have suggest though about using ODIN to go back to stock ROM I shall try
Is there anything specific I need to do to go back to stock ROM for the s4? I have i337m and don't have the original ROM.
It's been 4months since I last did all this so I'm a bit in need of refreshing.
Thank you again friend
Mkami said:
Thank you so much for replying. I am sincerely grateful.
The front camera works just fine. Its the rear camera.
I have wiped and installed my ROM into the phone hoping that'll work but nothing. I also tried another ROM still nothing.
What you have suggest though about using ODIN to go back to stock ROM I shall try
Is there anything specific I need to do to go back to stock ROM for the s4? I have i337m and don't have the original ROM.
It's been 4months since I last did all this so I'm a bit in need of refreshing.
Thank you again friend
Click to expand...
Click to collapse
You'll need the odin tar file specific to your i337m phone. Unfortunately, I'm on i337 so I'm not sure which one you need.
I guess start with determining what base you are on. Should help you find it easier. This link will help with that..
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
guut13 said:
You'll need the odin tar file specific to your i337m phone. Unfortunately, I'm on i337 so I'm not sure which one you need.
I guess start with determining what base you are on. Should help you find it easier. This link will help with that..
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
Click to expand...
Click to collapse
So I have done everything and found out it is a hardware issue :/ Does this mean it is not fixable?
Mkami said:
So I have done everything and found out it is a hardware issue :/ Does this mean it is not fixable?
Click to expand...
Click to collapse
Sounds like a hardware issue then. (Had it been a driver issue, the stock samsung firmware that you installed on it would have solved that issue)
You mentioned you just got a new camera. Did the camera work after it was installed? If you took it to a store, maybe it's still under warranty and you can take it back. If you replaced it yourself, maybe the something came loose. Try taking it apart and making sure it's still connected. If it was an after market camera, maybe you need different drivers?
guut13 said:
Sounds like a hardware issue then. (Had it been a driver issue, the stock samsung firmware that you installed on it would have solved that issue)
You mentioned you just got a new camera. Did the camera work after it was installed? If you took it to a store, maybe it's still under warranty and you can take it back. If you replaced it yourself, maybe the something came loose. Try taking it apart and making sure it's still connected. If it was an after market camera, maybe you need different drivers?
Click to expand...
Click to collapse
Do you know where I can get the drivers for the camera on the s4 i337? I double checked everything after taking it apart and yet nothing. If it's an actual hardware issue I guess I can't do anything about it :'(. Actually my warranty is voided due to rooting. Thank you very very much for trying though
Mkami said:
Do you know where I can get the drivers for the camera on the s4 i337? I double checked everything after taking it apart and yet nothing. If it's an actual hardware issue I guess I can't do anything about it :'(. Actually my warranty is voided due to rooting. Thank you very very much for trying though
Click to expand...
Click to collapse
The Samsung camera drivers would be built in to the stock image. I just threw in the driver suggestion in case you replaced the camera with another brand.
I wouldn't worry too much about your warranty being void due to rooting. It's one thing if you bricked your phone because you were trying to flash something you shouldn't have and then try to get it replaced under warranty... That's wrong.
By Odin back to stock you put the phone back into the state it was when you first received it. If the camera is still not working, I would try to get it fixed under warranty. (unless of course it broke from a fall or a swim... then you'd be out of luck)

Huge problem need help

I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.
malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.
Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha
I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk
This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.
Good one... Hackberrybold

[H918] Random Reboots on Custom Roms

So, I had a day 1 v20 that began randomly rebooting back in december. Thought it was a hardware issue and finally got around to replacing it the other day. Now, after getting the replacement v20 set up on a custom rom (AICP) I'm seeing random reboots again. I've tried every single custom rom available for the h918 and they all experience reboots. When i've asked about the issue in the threads it seems as if I'm the only one. It appears to be a custom-rom only problem that apparently no one else is experiencing? The kernel panics are being caused by the modem, and it started happening when I upgraded to the 10j base. This replacement also came with 10j. Am I just super unlucky with two duds or is there really something going on here?
TLDR; Anyone else with a h918 with 10j bootloader/modem running custom roms and seeing random reboots?
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Biff627 said:
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Click to expand...
Click to collapse
Have always left kernel stock.
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Biff627 said:
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Click to expand...
Click to collapse
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
trobertson said:
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
Click to expand...
Click to collapse
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Biff627 said:
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Click to expand...
Click to collapse
The phone came with stock 10j.. flashing this wouldn't change anything.
trobertson said:
The phone came with stock 10j.. flashing this wouldn't change anything.
Click to expand...
Click to collapse
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Biff627 said:
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Click to expand...
Click to collapse
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
trobertson said:
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
Click to expand...
Click to collapse
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Biff627 said:
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Click to expand...
Click to collapse
Aicp, rr, cm-remix, stock Lineage.
trobertson said:
Aicp, rr, cm-remix, stock Lineage.
Click to expand...
Click to collapse
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Biff627 said:
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Click to expand...
Click to collapse
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j as most custom ROM users are still running 10d firmware
trobertson said:
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j
Click to expand...
Click to collapse
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Biff627 said:
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Click to expand...
Click to collapse
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
trobertson said:
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
Click to expand...
Click to collapse
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Biff627 said:
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Click to expand...
Click to collapse
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
trobertson said:
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
Click to expand...
Click to collapse
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
Not a Samsung fan. Especially with KNOX. I buy phones first based on the chances of development producing workable custom ROMs and second based on hardware features.
Back to the main topic: I just managed to flash the 10i modem alone so we'll see what happens. I'm working on extracting the 10d modem as well.
Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
UPDATE: Flashing the 10i modem made no difference, still having random reboots (although they seem less frequent), I will try the 10d modem once I find a way to extract it from the TOT files posted on this forum.

G935w8 cannot root without screwing up sensors

As it says in the title, I have seriously read all over this forum and cannot seem to find any clearcut answers to how to gain root without screwing up the sensors on this phone. I followed the instructions to format phone in TWRP then flash Su and the DM Verity zip but literally nothing has worked for me, I end up with root but without a working camera or anything else sensor related. I'm slightly frustrated as I've been using Android since 2008 and have rooted every single one, but have never come across a forum with as much varied info. Can anyone help me please :/
Wich version of SU are you flashing, have you tried with Magisk? This happening on stock (rooted) rom or/and on any other rom?
mrsmtt said:
Wich version of SU are you flashing, have you tried with Magisk? This happening on stock (rooted) rom or/and on any other rom?
Click to expand...
Click to collapse
I was flashing the 2.79 one shown in the tutorial on here. I also used the recommended dm verity zip. I checked the Canadian s7 edge post and couldn't seem to get any answers.
Thanks for the help by the way
As I see there's no difference in hardware between the canadian and international variant so what's happening to you it's odd; but there's another member "unit68" that had a similar problem (a bit more unlucky to be honest) wich solved that using "flash fire" that I have no idea what it is; his post is #431 here https://forum.xda-developers.com/s7...gat-canada-t3497448/post72246170#post72246170 maybe you can send him a pm and find a solution together! I hope you'll find out a way to gain root without problems! Good luck
mrsmtt said:
As I see there's no difference in hardware between the canadian and international variant so what's happening to you it's odd; but there's another member "unit68" that had a similar problem (a bit more unlucky to be honest) wich solved that using "flash fire" that I have no idea what it is; his post is #431 here https://forum.xda-developers.com/s7...gat-canada-t3497448/post72246170#post72246170 maybe you can send him a pm and find a solution together! I hope you'll find out a way to gain root without problems! Good luck
Click to expand...
Click to collapse
Thank you for your help. I have not yet tried flashing twrp then flashing a custom rom right away. I wanted to stay on stock, but it seems like that isn't possible.

Categories

Resources