Database Info

[FIX] Slow Camera Startup - "Camera Failed" Message

Greetings,,
Many of us are facing some random restarts by launching the camera or slow camera issue
Actually Doc already have a fix, which I found here but I don't know why I can't find a separate thread for it ...
Of course all credits go to Doc for this fix
Link for the fix: http://d-h.st/YYl
Just flash it...
For noobs,, here is a video guide
Regards,,

Great! Thanks

Excellent thanks
Sent from my GT-I9500 using Tapatalk 4 Beta

i'd tried this fix but it didn't work unfortunately and i got reboots on opening the camera again .
after flashing adams kernel 1.3.1 and on Wanam's Rom...so far no reboots ...still testing

i dont really know what this fix does as i have not downloaded. But what i have identified is, if you flash someother kernel from different FW then the problem persist. For example if you flash ME2 stock kernel on ME1 then the camera will be broken and if you flash the ME2 on ME2 then there wont be any problem with the camera

hoezay said:
i'd tried this fix but it didn't work unfortunately and i got reboots on opening the camera again .
after flashing adams kernel 1.3.1 and on Wanam's Rom...so far no reboots ...still testing
Click to expand...
Click to collapse
What has worked for me is limiting the background processes to 4 in the Developers Options. You have to know that every time you reboot the phone the limit for background processes goes back to default, so after every reboot (voluntary) you need to go and change it.
This is not my discovery, somebody suggested it in another thread.
Cheers

it need root right ??? bec i don't have like the recovery in the video

You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta

cmd512 said:
You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I agree with you +1
Sent from my GT-I9500 using Tapatalk 2

what he said
cmd512 said:
You guys are seriously mistaken. Doc's camera fix merely copies the latest camera firmware rev to the firmware folder, which fixes the "camera failed" message when using an older custom kernel with a newer ROM. It has absolutely NOTHING to do with the random crashing encountered when launching the camera, you WILL still get that until Samsung releases a proper fix for it.
Please either change the thread title or lock the thread, nothing worse than misinformation.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
+N

[Q]Walkman restarting my phone. HELP

HELP!!! I've updated my phone three days ago. And now I'm facing a BIG problem: everytime I close WALKMAN app (no matter how: by stopping with hands free phone button, by stopping in the widget in lockscreen and even when a clean my recent apps) everytime I do something like this with Walkman, my phone gets into some kind of restart. I have tried with stock version of the app e the updated version too. I NEED HELP, it's the most important thing in my smartphone for me, and I don't want to use another player forever. (4.2.2 Upadate)
P.S: I make a full system factory SUS update and a factory reset of the phone settings too.
And I don't want to downgrade cause in last firmware I had a problem with WiFi speed and with de led lights... I really don't want to downgrade.

Try flash another firmware..
Sent from my C2105 using xda app-developers app

talhah sabri said:
Try flash another firmware..
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
But where I will find firmware downloads?
I only found C2105 firmwares, but mine is C2104.
What can I do?

It's the same problem that m facing.bt my issue is thru google chrome not by walkman.
Sent from my C2104 using xda app-developers app

Not only Walkman
dropdan said:
HELP!!! I've updated my phone three days ago. And now I'm facing a BIG problem: everytime I close WALKMAN app (no matter how: by stopping with hands free phone button, by stopping in the widget in lockscreen and even when a clean my recent apps) everytime I do something like this with Walkman, my phone gets into some kind of restart. I have tried with stock version of the app e the updated version too. I NEED HELP, it's the most important thing in my smartphone for me, and I don't want to use another player forever. (4.2.2 Upadate)
P.S: I make a full system factory SUS update and a factory reset of the phone settings too.
And I don't want to downgrade cause in last firmware I had a problem with WiFi speed and with de led lights... I really don't want to downgrade.
Click to expand...
Click to collapse
I have the same problem but with my headphones, i plug the headphone and the phone restarts, i flashed my phone with a c2104's rom and i don't use chrome.

[Q] Phone freezing and bootlooping frequently

Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.

igohenrique said:
Hi guys =)
After I unlocked bootloader and flashed a custom Kernel, my phone started freezing and sometimes it gets stuck on a bootloop. I've flashed two custom Kernels and the stock one, but nothing seems to help My phone freezing happens frequently. And I can notice some glitches when listening to music or using Chrome. Sometimes I'm doing nothing and it freezes. After a couple of minutes frozen I can use it again.
Do you have any idea on how to fix it? It's quite annoying if I must say.
Latest firmware btw. Rooted.
Click to expand...
Click to collapse
If you're using Phantom Kernel, may I suggest you to try version 4.5 like @faizalotai said to me on this. When I was using latest version, my phone freezes every time, but the downgrade solved the problem. You can get the v4.5 from attachments

It's exactly the lastest version I have flashed on my phone. I'll give it a shot. Thanks =D

You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app

srcharged said:
You can try to use thunder zap kernel too.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?

NO!!
DsvCdsSoftware said:
I've never used TZ, 'cause I read in other posts that it mess up a bit the modules and kernel files, besides phone's heat up a lot and for some users they can only change kernel after a fresh FTF flash. Is this true?
Click to expand...
Click to collapse
Most certainly no! cos i have flashed phantom and back to TZ and then again to phantom and so on loads of times..
i never had any problems. And everything is working crisply for me. No heating issues, nothing..
Im on CM11. Using TZ 4.1 r-2

I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app

Sure!
DsvCdsSoftware said:
I'm using. 14 firmware yet, cause I need Bluetooth in my work, but this issues I told you are in 4.2.2, but I'm thinking in giving a chance to TZ
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just give it a try and let me know. Use the Voltage table given by him. And soon we will have bluetooth on our devices. Its all set already!

Thanks, @DsvCdsSoftware It worked! No more phone freezing! I also flashed PurePerformances™X, it's just perfect =)

[Q] "Google Play Services Stopped" all the time [H6+]

I believe Honor are aware of this issue and working on a fix.
Does anyone else have this problem?
Any known fix by changing settings/not using a particular app.... etc?
Uninstalling the latest "GPS" update only temporarily "fixes" the issue

clearing the cache helped here

Tried it, but nothing much works for long. Apparently there is a fix coming in the OTA update, coming soon. Flashing it manually has tendency to brick phone.
Sent from my GT-N5110 using Tapatalk

Hi,
I have the same issue on a Honor 6 (h60-l12) since updating to EMUI 3.0. I don't know where the problem comes from. How do you know there is a fix coming for that ?
Maybe, flashing gapps with CWM could resolve this issue due to a bad google services installed ?

I was told by Honor via Twitter, about the fix.
Sent from my PE-TL10 using Tapatalk

It's seems to be fixed since the 3.1 official update

Install Aptoide.. and check updates.. it fixed for me.. updates are for play store, tailback etc
Sent from my PE-TL10 using Tapatalk

Black screen on Google setup

When trying to setup new phone after rooting, I'm getting a black screen when trying to login to Google. It comes after resetting phone.I was using a black theme, would that affect it,
Sent from my [device_name] using XDA-Developers Legacy app

I've also gone into accounts and tried adding a Google account, same result
Any way to fix?
https://photos.app.goo.gl/8iX7KVcMLHtpb12KA
Sent from my [device_name] using XDA-Developers Legacy app

Seems Google couldn't fix it either. Sending a replacement
Sent from my [device_name] using XDA-Developers Legacy app

Damn, there are a lot of things I read on this forum that causing me to think of canceling my phone.

Just submitted an RMA for my device. The proximity sensor over the last 3 days hasn't been working properly and wont activate the screen when I try to hang up a call after pulling the phone away from my head.

What root method did you use gvsukids? I'm getting my phone today and will be rooting it. Just concerned now..

toy4x4 said:
What root method did you use gvsukids? I'm getting my phone today and will be rooting it. Just concerned now..
Click to expand...
Click to collapse
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Flash to both slots
Sent from my [device_name] using XDA-Developers Legacy app

gvsukids said:
When trying to setup new phone after rooting, I'm getting a black screen when trying to login to Google. It comes after resetting phone.I was using a black theme, would that affect it,
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seems that chrome wasn't installed and that was causing the issue. After installing boot.img from magisk, I was able to sign-in to play store and now don't need the RMA.
It's an issue with the modified boot.img from rooting phone which removed chrome
Sent from my [device_name] using XDA-Developers Legacy app

Thanks for the heads up!

gvsukids said:
Seems that chrome wasn't installed and that was causing the issue. After installing boot.img from magisk, I was able to sign-in to play store and now don't need the RMA.
It's an issue with the modified boot.img from rooting phone which removed chrome
Click to expand...
Click to collapse
You are hero!!!!! Thanks for this

Had this same problem when I flashed Android 8(Oreo) on my Samsung Galaxy S7 edge (SM-G935V) that came with android 6.0.1(Marshmallow). I solved this by simply clearing the cache of google play services and updating my google apps...and it was working fine.

I resolved the same issue on a different device by installing Android Web View. If issues persist, try (re-)installing it. Mine was a custom ROM which apparently had issues with Web View.