Database Users

Video added: camera flash sync problem! frustrated

i recently received a new nexus one because of dust under the screen. today i noticed my camera flash is not working properly.
everytime i take a picture with the flash enabled the flash fires once (for exposure metering i assume) but the second flash never comes. so the images are flashless and super dark.
i tried "factory resetting" and the roblem continues. anyone else have this problem. seems like a software issue? any ideas on how to fix this?
im on stock ere27 2.1 update-1. ALSO this problem effects aftermarket apps as well because its part of the firmware.
Update: recorded a short video to demonstrate my problem.
http://www.youtube.com/watch?v=RVKlSe0UiDY

Called HTC, they had no idea what they where talking about. Transfered me to Google support. They had no idea what was causing this problem and suggested a "swap"
... this phone is a SWAP... its 2 days old.
I'm getting sick of this.

Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?

Recorded a short video to further explain whats happening.
http://www.youtube.com/watch?v=RVKlSe0UiDY
please let me know what you think.

dills84 said:
Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?
Click to expand...
Click to collapse
It's definately a odd problem, I haven't seen this myself, but if you have already reset your phone to stock and have done the updates and are still experiencing problems. Sadly, your best bet is to have Google warrenty your phone. Don't root to see if its going to fix the problem, you'll be in a much deeper hole if it doesn't fix your problem.
TL;DR
Let Google replace your phone.

Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?

dills84 said:
Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?
Click to expand...
Click to collapse
You might want to take a look here.
It has a complete list of all the stock roms and images. (With download links.)

You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.

prettyboy85712 said:
You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.
Click to expand...
Click to collapse
Just trying to come up with an easy alternative since this is kind of a minor issue?
Also this phone is my second nexus one, First one had tons of dust under the screen. This one is real clean so I was hoping I could hang onto it!

why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk

palosjr said:
why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk
Click to expand...
Click to collapse
As stated, this is the problem. The first flash is for "exposure" the second flash is for the actual picture. So the camera is exposing thinking there is a flash coming from the camera. But there is no flash happening during the picture, only before hand.
And yes this is a firmware problem. so any app that uses the camera has the same problem with the flash. I've tried a bunch.

Does anyone know the actual hardware innards of the nexus? If this is just some kind software glitch I may just unlock my bootloarder and fire up CM. Maybe that'll fix it?
I'd hate to return another one... this ones screen is perrrfect.

[Q] N4 on Paranoid Android : Camera not working, no signal, doesn't detect sim

So I just Installed PA 3.99.1-RC1-20130914 and PA_GApps-20131018
It's strange to see that there was no Google Chrome by default along with the following issues :
- Camera is not working - on opening the app it simply says Can't connect to camera.
- There is no signal and on searching for networks, it asks for sim.
- Also the PA_OTA app says unable to check for updates, though I'm able to download apps.

Did you come from 4.2? Did you flash the new radio?

Chromium_ said:
Did you come from 4.2? Did you flash the new radio?
Click to expand...
Click to collapse
Coming from 4.3 . I hadn't flashed it earlier, did just now, Doing factory reset and reinstalling PA and GApps. Hope it helps.

Got stock image and flashed it to make sure everything is latest, flashed PA again but same issues.
Can it be because I'm using 3.99.1 ?
Back to stock for now. Need the SIM to work atleast.

anshul93 said:
Got stock image and flashed it to make sure everything is latest, flashed PA again but same issues.
Can it be because I'm using 3.99.1 ?
Back to stock for now. Need the SIM to work atleast.
Click to expand...
Click to collapse
May this Thread could help you:
http://forum.xda-developers.com/showthread.php?t=2491848
Could be a similar problem.

Random reboot with lollipop 5.1

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.

Greetings.
Have you tried using any other kernel, eg. franco kernel?

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)

Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app

killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.

This does not happen at all to me(using stock 5.1 with Franco Kernel).

This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.

_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).

Your battery is dying, I've been getting the same problem until I replaced the battery today.

richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?

I've been getting the same issues on my N7 since updating.

regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....

ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.

gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.

_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks

I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.

Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng

gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.

I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk

Problem with silent/vibrate/normal mode. Phone switches alone !

Hi everybody
Since few month i've got a strange bug (but i saw i'm not alone with this bug ^^).
4.4.2 Stock D80220F-EUR-XX
root
kernel, Dorimanx 10.2
BUG :
My phone switches from silentmode to vibrate or normal mode more than 10 times a day without any action. It's borring... :angel:
Quiet mode/quiet time not activated. All gesture function disabled except Knock-on.
I try to wipe cache/dalvik : no effect.
Thx

no idea ? :crying:

zdravo said:
Hi everybody
Since few month i've got a strange bug (but i saw i'm not alone with this bug ^^).
4.4.2 Stock D80220F-EUR-XX
root
kernel, Dorimanx 10.2
BUG :
My phone switches from silentmode to vibrate or normal mode more than 10 times a day without any action. It's borring... :angel:
Quiet mode/quiet time not activated. All gesture function disabled except Knock-on.
I try to wipe cache/dalvik : no effect.
Thx
Click to expand...
Click to collapse
Were you experiencing this problem on stock kernel?
It might be worth Returning to Stock and seeing if the problem persists. That way you can narrow the problem down to whether it was caused by user intervention or if it's in fact a hardware problem.
Have you tried any other ROMs, Kernels? Or have you only ever been having this issue with Stock 20F with Dori?

d00lz said:
Were you experiencing this problem on stock kernel?
It might be worth Returning to Stock and seeing if the problem persists. That way you can narrow the problem down to whether it was caused by user intervention or if it's in fact a hardware problem.
Have you tried any other ROMs, Kernels? Or have you only ever been having this issue with Stock 20F with Dori?
It's also quite possible that your phone is growing a conciousness and it's slowly becoming self aware. Now it's just enjoying playing tricks on you when it's in your pocket :silly:.
Click to expand...
Click to collapse
First of all, thx for your reply :highfive:
Hmm... i don't remember if i was on stock kernel or not the first time the problem came.
I will follow your advise and back to stock kernel and i see what happens
I've never tried another ROMs, only base on stock (stock OPEN). But yes maybe my phone is trying to communicate...
I will test kernel stock and i'll be back :fingers-crossed:
thx

Ok... with KK Stock Kernel, i still have this bug... :/
But i read that it could be a problem of version (20F)... some users have this bug too. Update to 20G or not ? or be patient and update to LP ?

any suggestions ? :/

More than 6 month later, i still have this curious bug :/

Just rooted S8.. Selective Focus in Camera not working anymore

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?