Develop Bugs

[Q] Camera Flash Stopped Working

Anyone encountered camera flash stopped working suddenky in camera mode, flashlight app or other 3rd party app? I used to clear dalvik and cache n it was ok for awhile but now it totally stopped working. Will reflashing it and reformatting it bring back the flash? T705 user here btw.

slackerz_86 said:
Anyone encountered camera flash stopped working suddenky in camera mode, flashlight app or other 3rd party app? I used to clear dalvik and cache n it was ok for awhile but now it totally stopped working. Will reflashing it and reformatting it bring back the flash? T705 user here btw.
Click to expand...
Click to collapse
Well let's find out if it is a software issue or hardware issue. Backup your current ROM, then wipe data, flash a new rom and see if it works. If it doesn't it's hardware issue.

Kahun said:
Well let's find out if it is a software issue or hardware issue. Backup your current ROM, then wipe data, flash a new rom and see if it works. If it doesn't it's hardware issue.
Click to expand...
Click to collapse
i already reformat everything and reflash.... it was fine till one point it started again. what i did next, i tried to fix permission in TWRP and it works!!! i wonder which permission causes the flash to stop working.... i had to fix permissionb everytime it stopped working....
anyone knows any way of which i can actually see what or which thing that causes the break??

My Tab S (T700) wont flash too! Only rarely. I tried in complete darkness and no flash! Im prolly gonna end up registering for this site just to comment!

[Q] Camera Crash after Original Update to 4.4.2

Hello,
I have updated my GT-i9192 to various KK roms (Russia, Brazil...) and I still get hard camera crashes when I try to use the camera.
I have also try using Google's own Camera app, but this is still a problem.
I have also wiped the cache and reset to factory, still no go. I sometime get a 'Camera Fail' window, or the phone reboots directly. I am trying to avoid tripping Knox, so CM and others are out of the question (especially if it does end up being a hardware issue...!) even though I have no reason to think that the camera stopped working in-between updates - nor do I want to revert to 4.2.2.
Any hints welcome, this is annoying as hell.
TIA

tareumlaneuchie said:
Hello,
I have updated my GT-i9192 to various KK roms (Russia, Brazil...) and I still get hard camera crashes when I try to use the camera.
I have also try using Google's own Camera app, but this is still a problem.
I have also wiped the cache and reset to factory, still no go. I sometime get a 'Camera Fail' window, or the phone reboots directly. I am trying to avoid tripping Knox, so CM and others are out of the question (especially if it does end up being a hardware issue...!) even though I have no reason to think that the camera stopped working in-between updates - nor do I want to revert to 4.2.2.
Any hints welcome, this is annoying as hell.
TIA
Click to expand...
Click to collapse
try to clear the camera cache and data, but first force close it. after you do this, reboot.
also delete everything from \Phone\Android\data\com.sec.android.gallery3d\cache

Nope
Unfortunately, that did not work...
I am going to try to upgrade to CM 11 and hope that it will resolve my problems.

tareumlaneuchie said:
Unfortunately, that did not work...
I am going to try to upgrade to CM 11 and hope that it will resolve my problems.
Click to expand...
Click to collapse
Upgraded to CM 11 did not fix my problem, I ordered replacement cameras (both) from ebay and the problem is still there.
Seems like a motherboard issue.

[Q] Battery drainage because of mobile data

Hi Guys,
I am new to this forum and got a small question. My girlfriend has an Oppo Find 7a. You guys probably know that the stock ROM is ColorOS. In my opinion it's crappy as hell, lots of bugs and issues, so I decided to flash Dirty Unicorns 5.02 on it. I did that yesterday and all is working fine so far, except that the battery drained from 100% to 64% last night (in 8 hours). See the photos attached. According to the photos it seems clear that the issue is the mobile data usage. I've checked the settings and it seems mobile data loses connection, connects again and loses connection everytime. Probably this is the cause of the battery drainage. Somewhere on this forum I read something about flashing Alucard 1.1a kernel on it to fix this issue. I want to try this in the evening, but does anyone know the correct type of this kernel as I found different alucard 1.1a download links?

Can someone please help me out with this? Yesterday evening I just flashed the Alucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?

GRDD_ said:
Can someone please help me out with this? Yesterday evening I just flashed the Elucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?
Click to expand...
Click to collapse
before flashing DU did you flash proper modem and trustzone firmware?

treacherous_hawk said:
before flashing DU did you flash proper modem and trustzone firmware?
Click to expand...
Click to collapse
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?

GRDD_ said:
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?
Click to expand...
Click to collapse
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
https://plus.google.com/+BoskoTrkulja/posts/CENAM1a7Zob
you can get the modem and tz firmware here:
https://www.androidfilehost.com/?fid=95916177934529695

Sir, have my thanks! You are my hero of today. Thanks a bunch. I'm going to try this

treacherous_hawk said:
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
you can get the modem and tz firmware here:
Click to expand...
Click to collapse
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?

GRDD_ said:
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?
Click to expand...
Click to collapse
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
Alright, I will do it in that order then. Thanks again. Much appreciated.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?

GRDD_ said:
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?
Click to expand...
Click to collapse
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.

treacherous_hawk said:
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.
Click to expand...
Click to collapse
I will give the battery thing some time to settle down then. About the data connection issue; This was not an issue on coloros, but I will check apn and try another sim. Thanks again!

I've changed the APN settings, as they stood on some kind of roaming setting. It's now been set to live.vodafone and seems to be functioning better already . If I still run into some issues I'll let it know. Thanks for helping me out

Frequent freezes and hangs after rooting and installing twrp

So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!

aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)

aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.

ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?

aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.

ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.

aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?

ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!

And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas

Sensor issues after installing and wiping "o" beta.

So I installed the beta and decided to go back to 7.1.2.
I did a normal wipe in TWRP then reinstalled SAOSP.
The first problem I noticed was that the phone was slow to turn the screen on after pressing the power button or the fingerprint scanner.
The second problem was that the proximity sensor wasn't working in phone calls. I then checked a few others sensors and noticed that the rotation also want working.
I downloaded a sensor checking app and it showed that the proximity sensor had a value of 5 but it didn't change when covering the sensor.
First thought was a bad flash, so I re-wiped and installed a Nand backup that I knew was good. Same thing happened, so I tried PN. That didn't work.
Downloaded stock zip, backed up personal data, then did a complete wipe with the zip, internal data included. The problems stayed even on stock.
I have since read through whatever threads I could. This seems to be a random issue people have had in the past. Yet is particularly prevalent after the o beta.
Most people have suggested to just re-flash stock but that hasn't worked. The only suggestion I have read otherwise is to also lock and then unlock the bootloader in the process as well.
Who else has this problem and has anyone found a fix yet?

Ok, someone posted in another thread (PN) that the locking and unlocking the bootloader worked for them.
If you have the issue try it out.
Just remember to copy all your internal data to your PC or other storage to save it.

https://forum.xda-developers.com/showpost.php?p=72397601&postcount=10078
Link to solution

To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2

neth15 said:
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
Click to expand...
Click to collapse
I tried it this way but after flashing back to 7.1.2 stock, I now get a crash of com.android.phone immediately after booting, followed by a reboot.
Tried clearing cache but didn't help. Anyone know what to try to fix the crash?
UPDATE: Wiped data and now it's fine.