Hello guys,
I have a problem with my camera.
When i enter camera app or any other camera related app i get:
Warning "Camera auto recovering".
I have no live view, but if i'm quick enough like i have 4 -5 seconds to press record i get image and video is recording.
also i can make pictures in that 4-5 seconds interval.
Sometimes Random I get live preview and everything works normal!
When i go to *#0*# in megacam
i get: Warning "camera failed"
This is what i get in ADB(logcat :*W):
Code:
E/SecCameraHardware( 1912): FimcV4l2 poll: error 0
W/SecCameraHardware( 1912): nativeGetPreview: warning, ESD Shock(0). Reset the camera device (10)
E/ISecCameraHardware( 1912): previewThread: error, nativeGetPreview
E/SecCameraCoreManager( 1912): notifyErrorCallback(1, 1010, 0)
E/SecCamera-JNI-Java(15002): Error 1010
W/SecCameraHardware( 1912): nativeStopPreview ++++++++
W/SecCameraHardware( 1912): nativeStopPreview ---------
W/ISecCameraHardware( 1912): stopPreview: warning, preview has been stopped
E/ISecCameraHardware( 1912): CAMERA power off noti. HAL is completely released
E/ISecCameraHardware( 1912): preview window is NULL!
W/AudioFlinger( 1912): session id 369 not found for pid 1912
W/AudioFlinger( 1912): session id 370 not found for pid 1912
W/AudioFlinger( 1912): session id 371 not found for pid 1912
I appreciate any help.
hello you could solve the problem
Warning "Camera auto recovering".
regards
EK GN120 Overheating/Heating/Battery Drain
I also have problem with my ek gn120... first i fully charged it before putting it inside the cabinet for storage then the next morning i get it to transfer files to computer then i notice its warm but the room is cold because of the airconditioning.. then when i try to switch it on it wont open because the battery is drained.. so meaning it is using the battery when battery is connected because the camera is warm when i took it and battery is now drained... then i tried to charge it now and it is super slow to charge. i charge it overnight from 2% and now it is 12% but before i only need to charge it like 4-6hrs then its ok.. i already did the factory reset but still doing the same thing. when its turned on the battery is not charging not like before. so is it the battery need replacement or there's more to my problem other than the battery? thankyou and have a nice day. :crying:
I know this is a very OLD problem, with the battery drain... but have you solved or at least figured out why it drains so badly? I purchased one recently that does the same.
Related
Hi,
When I press the Camera button on my XDAIIs it tries to launch Media Player instead of the camera.
If I open the Camera application from within the programs folder I get the following error...
Failed to initialize camera.
Please reset the hardware.
36001:100:2
Click to expand...
Click to collapse
Does anyone have a fix for this?
Many thanks
same here
Ive been getting this too. It has also coincided with the battery monitor showing battery life being drained at a very fast rate.
It first happend when I had about 18% on main battery, my girlfriend fell and snapped her clavical requiring me to call an ambulance. Pulled the XDA2i from my pocket powering it up I pressed the camera button. The screen went all funny and it killed itself (full reboot from scratch required). Got another person to call the ambulance.
Since then it crashed with the error you report, and the battery meter went screwy. SO then I re booted in corporate mode. Fine for a while but then the camera screwed up again. SO another full re boot.
Getting fed up I did think about returning it as faulty. Not had time so this time I copied the shortcut from the windows folder in to the start menu allowing me to re asign the button on the side.
I am currently watching it to see if the battery meter is playing up too. Bit of a problem as I have just started using TT5 incar so it goes on and off charge a lot along with a bluetooth headset bought on a few days ago.
Ill watch this and hope for more input
confirmation
OK lastnight the XDA2i went flat and wouldn't powerup. I left it around 11pm with 65% on the main battery 100% on the back up. I had to put it on charge for 5mins at 7am this morning before it would power up!!! It then read 12% on the main battery, backup at 100%
The unit is standard, out of the box standard. Running it in corporate mode, only program loaded is TT5. Proccessor set to turbo.
Normaly I would get a couple of days before charge (minimal usage)
Fitted with an www.integralmemory.com 1gb sd high speed card.
In the time it took me to write this the main battery dropped by 2%
HELP HELP HELP
When I boot my phone it gets stuck on the boot screen and the logcat spits out a bunch of hexadecimals with [heap] next to them and this warning over and over again
W/SurfaceComposerClient( 150): lock_layer timed out (is the CPU pegged?) layer=
0, lcblk=0x4010c020, state=00000043 (was 00000043)
then the cycle repeats. Here is a bigger chunk of the log http://dl.dropbox.com/u/673057/log.txt
I think it might have something to do with the batter because my battery seems to have been dieing a lot faster, it drained completely twice on me today and in between that my phone couldn't make or recieve calls for a while today.
Anyone have any idea what could be wrong with it?
schwiz said:
When I boot my phone it gets stuck on the boot screen and the logcat spits out a bunch of hexadecimals with [heap] next to them and this warning over and over again
W/SurfaceComposerClient( 150): lock_layer timed out (is the CPU pegged?) layer=
0, lcblk=0x4010c020, state=00000043 (was 00000043)
then the cycle repeats. Here is a bigger chunk of the log http://dl.dropbox.com/u/673057/log.txt
I think it might have something to do with the batter because my battery seems to have been dieing a lot faster, it drained completely twice on me today and in between that my phone couldn't make or recieve calls for a while today.
Anyone have any idea what could be wrong with it?
Click to expand...
Click to collapse
try wiping and reflashing the rom. it may have become corrupt. as for the battery, HTC will replace it NQA if you have it under warranty. tell them you think your bat is defective because it dies every few hours and they will send you a new one. then you send your old one back. if you dont send it back they charge you $40. they give you a shipping label too so its completely free
I tried reflashing, although I didn't suspect it would help because the rom had been working fine for weeks before this started happening. I already ordered a new battery off http://www.all4cellular.com/ for just 8 bucks brand new! Now I just need to wait a week while it ships in limbo hoping that is what is wrong.
wiping the battery info seems to have fixed it
I got a problem: my battery is draining REALLY fast, like 20% every 2 hours.
When I check battery history (*#64... code) it says that: int other usage : time without standby/sleeping (dunno how it's in English > got a Dutch version (Wordt Uitgevoerd)) is at 100%.
Partial wakelock: Maps is also at near 100%
Gallery is not present.
I've tried rebooting, but this keeps happening...
What is causing this?
Firmware: 2.2 JPA
Loook in Setting of the phone...There have many options for On/Off forderground and backgraund process and aplications...
Regards
What kind of option am I looking for?
I tried a factory restore, and it still drains with hardly any apps installed (just Gem miner, Fruit slicer, Battery indicator). Battery history doesn't show ANY app being run. Just shows that 'Other Usage > Being run (wordt uitgevoerd)' keeps increasing when I turn it off.
Please help, this device is becoming useless to me...
Hi all.
I'm running Maclaw's CM10.2 and it's mostly great. I'm getting random reboots, which nobody else seems to be talking about. I've narrowed it down as far as possible. For a reboot to happen:
Phone must be on battery
I must be actively using the phone
The reboot goes right back to the Samsung boot screen. Most of the time, it enters a boot loop unless I attach power. I usually hear two "low battery" sounds during boot at this point, regardless of how well charged the battery was before. If I attach power during boot, it is fine, though it shows the battery as nearly empty.
The reboots don't happen when the phone is plugged in to power, which also means I can't reproduce them when connected to ADB.
Has anyone else seen this behaviour? Can anyone suggest how I can capture logs or debug these reboots?
Dan.
djs52 said:
Hi all.
I'm running Maclaw's CM10.2 and it's mostly great. I'm getting random reboots, which nobody else seems to be talking about. I've narrowed it down as far as possible. For a reboot to happen:
Phone must be on battery
I must be actively using the phone
The reboot goes right back to the Samsung boot screen. Most of the time, it enters a boot loop unless I attach power. I usually hear two "low battery" sounds during boot at this point, regardless of how well charged the battery was before. If I attach power during boot, it is fine, though it shows the battery as nearly empty.
The reboots don't happen when the phone is plugged in to power, which also means I can't reproduce them when connected to ADB.
Has anyone else seen this behaviour? Can anyone suggest how I can capture logs or debug these reboots?
Dan.
Click to expand...
Click to collapse
Read my FAQ here, to see how to take logcats.
mauam said:
Read my FAQ here, to see how to take logcats.
Click to expand...
Click to collapse
Awesome, thanks. I knew about logcat, but didn't know about last-kmsg. Now, of course, I can't reproduce the problem
Interesting. The last thing that happens is the AB8500 driver decides to shut down:
Code:
[37032.798461] ab8500-fg ab8500-fg.0: Low bat Interrupt occured, now waiting for power off condition
[37032.798522] ab8500-fg ab8500-fg.0: Capacity : 14 Voltage : 3070mV
[37032.798553] ab8500-fg ab8500-fg.0: KDG_DATA] 215mAh/1500mAh 14% (Prev 216mAh 14%) 3070mV -246mA -295mA -1639 0 0 5 1 1 130 10 0 0 0
But no proper shutdown happens -- it just reboots.
I can see in the log the battery capacity dropping smoothly from 38% at time 34403 (43 minutes earlier), but the battery monitor shows the reading dropping off a cliff (see attached). It looks like the last value the battery monitor could see was about 40%. Any ideas?
Also in the logs, "Shut down pending..." at 36955.787566 (a minute and a half earlier), but I didn't get any notification on the screen. And 15% capacity seems a bit high to be forcing a shutdown?
I have the phone for a week now and more and more it's shut down when I want to switch it on. I then have to press the power button a bit longer and it will then restart normally.
And there is something else that I think is strange (I just found out while testing because of the other issue). When I press the power button multiple times then sometimes it doesn't switch on again. After a wait of a few seconds and another press it switches on again.
Anyone else has these issues? Can I track why it switches off? Is there a log to see what happend before?
Only when it's cold
I noticed that the random shutdowns are not so random. It only happens when the phone is cold. I can put it 3-4 minutes outside (a bit below 0 degrees celsius) and it switches off every time.
When it's warm - it never happens.
Anyone else have this problem? what's the temperature range which it should work in? I never had that with another phone and it's really not that cold.
Not me, but it's not that cold here.
But it is coldest time since i have z3c and i noticed that in camera when switching from superior auto to manual, or anything it lags a bit when it's cold.
I couldn't find operating range for our battery but it looks like that most Li-Po batteries suffer when temps go below the 0C
I'm going to assume that's your case.
Standby phone = no heat being generated = available current dropping = phone shutting down
Info
chaelli said:
I noticed that the random shutdowns are not so random. It only happens when the phone is cold. I can put it 3-4 minutes outside (a bit below 0 degrees celsius) and it switches off every time.
When it's warm - it never happens.
Anyone else have this problem? what's the temperature range which it should work in? I never had that with another phone and it's really not that cold.
Click to expand...
Click to collapse
weird
thr s always process in background so the phone temp will be always above 0 C
unless the environment temp be too below 0C (like -20C)
contact service center and tell the story and please inform us here what s their response
:good:
Thanks for the inputs. I know that there is a limit on lower temperature for the batteries. But as I easily was able to restart the phone and it showed no strange value for the battery-power, I don't think it can be only this. Also - we had 5 other phones with us and they all worked in the same environment. I'll keep you posted what the service center answers...
I have been in low-temperature environments(-18,+4,0 C) I did not stay too long, but phone survived without any hassle
I am having a very similar issue. Since day 1, my phone randomly reboots especially during the night every 20 minutes or so, and i usually find it switched off in the morning when i wake up. I even had to go work late the first morning because I use the alarm of the phone to wake up and since the phone was switched off, the alarm didn't work.
Last week i went to ski. Up in the mountain, the phone was almost completely useless ( Tempererature was just below 0 C ). It was constantly rebooting in my pocket and shutting down every 5 minutes. Whenever i wanted to use it, the screen opened and as i unlocked the phone it rebooted, however if i continue to use it afterwards ( opened mobile data and gps, talking, etc. ), it did not reboot. So i thought that it might be due to battery getting too cold. Also, i realized the rebooting happens more frequently when i put the phone in a very low power usage state like Ultra Stamina or flight mode. ( I also put the phone in flight mode during the night when i go to sleep )
I have contacted Xperia Care. They assumed this might be a software malfunction and suggested resetting my phone using PC Companion. I played along and reset my phone but it didn't fix anything. I will call them again tomorrow. I am suspecting the battery itself is faulty or the background task that is supposed to heat up the battery is not working properly.
Update: : Appaerently the phone was in fact faulty. They changed it with a new one which is working pretty fine