02-15-2012 10:26 PM - edited 02-15-2012 10:34 PM
Feb 6th , to test a tiny OPENGL game, I upgrate IDE from Flash Builder to NDK 2.0 and PB OS from 1.0.8 to 220.127.116.1111 , the App runs Very well and smooth in real PB device.
but Yesterday , i notice i can't launch the camera app , both front and rear , Camera APP is BLACK sreen with some buttons( takeshots etc). Reboot , no luck.
the most issue is that ,i can't take the screen shot too, volumns key is ok with music app , but press both the keys (+, -) , DO Nothing, no click sound ,no picture stored . so i can't capture my new app image and post to appworld.
is software or hardware issue ?
tommorrow ,OS 2.0 will solved ?
02-16-2012 05:02 PM
The camera and screenshot functionality are both handled by the same system service.
It's likely there is a hardware problem with your device which is preventing the camera h/w from initializing.
If you do a security wipe and go back to 1.0.8, do you still have the problem?
How about if you do a security wipe & load the latest 2.0 beta?
02-26-2012 06:30 AM
after update to OS2.0 , screenshot still cant' work.
i have to do a security wipe, just now ,
PB rebootss well, still in the setup screen, i press the volumn keys (+,-) ,
the click sound comes back, so lucky
but the battery level is just 16%, it is too low to continue the update
plug and ,wating battery level to 20 %.
02-26-2012 07:39 AM
NO LUCKY ,
the issue isn't fixed after the install
screenshot not work again, camera is BLACK .
but i can capture the sreen while installing. here is the png file stored in the camera dir.
02-27-2012 10:13 AM
02-27-2012 10:56 AM
Without having physical access to your device, and your logs, I cannot really troubleshoot this.
Here are some rules of thumb I can throw out for you.. perhaps you can devise your own test
In any event, even if the problem is a software one, it is probably being caused by some out-of-spec hardware behaviour, and you should work towards replacing the device. With access to failed units, it may help to point development in the correct direction to catching any possible issues that may only crop up in very rare circumstances.
eg. imagine a hardware spec says that the camera should power up within 500ms. if you have a marginal unit which takes 510ms to power up (maybe due to ageing, maybe an out-of-spec device), the software may already be in an error-state. if we find that 1-in-a-thousand units exhibit this behaviour, then we can take it back to the camera sensor vendor and find out what would be the cause. If it turns out to be harmless or expected in rare cases, then simply extending an initialization timeout from 500ms to 600ms could resolve the problem in a future software update. If it points to a manufacturing issue, then it could be resolved and caught there, etc. etc.
02-27-2012 11:09 AM