Database Users

Phone reboots after launching Camera in Android 2,1

Hi All,
I have a problem where my phone crashes and reboots when I launch an app that uses the camera in any way, for example layar, barcode scanner, camera etc. This only happens in Android 2.1, I've tried various ROMs and always the same issue. I've tested Android 1.5 and there are no problems with that at all.
I've noticed the crashes only occur when I'm on battery power, it never happens when the phone is plugged in so I cannot get logs to see what is going on, unless someone knows a way to get the logs from a crash.
I was wondering if anyone else has seen this problem and if so, if they've found a resolution to it.

Since updating with the OTA 2.1 update I have been experiencing this problem too. Phone reboots when it uses the camera, Layar, Yelp, AugSatNav all seem to cause the problem.

I get this problem too, with the camera, and also sometimes when I put the volume down it freezes and reboots
Sent from my HTC Hero using XDA App

I've got the same problem. Restarting when launching apps using the camera.. Im glad that's not a HW problem but "only" SW bug.. I hope

It could (and probably is) a radio issue....Happens on the N1 and Desire if you try to use the camera too and seeing as the GPS,Camera both are dependant on the radio id say that is it! Find the radio reccomended with the rom you use and flash it( Beware of orange users being locked down though,you need a specific radio)

Just to add that I'm getting the same problem too running FroydVillain 1.2.2 and baseband 6.35.15.14, should point out that been having the problem for quite a while on a multitude of ROMs :-(

I'm not - did you full wipe?

Multiple wipes...

try 1.3 i guess

I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App

Tried multiple ROMs and multiple Radios with no change :-(
Unless theres a second secret wipe button hidden in recovery I don't know what else I can do :-/

try to disable "automatic brightness"...

Gynjanynja said:
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Hi,
I have had this problem since i went to 2.1 also, i have also flashed several rom's since villainrom 12 and have even used rcmix 1.0b which is a great 2.1 imo.
Have flashed 2.2 roms, and i am still having the same problem.
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Some things to consider.
The phone will never reboot if it is plugged in to a usb / electric plug Charger and is actually charging.
The phone will remain on and will carry on taking pictures IF you don't close out of the camera the first time around.
No task killer was installed on my phone at the time of this test, although i have had task killers before with the same results.
Lighting effects and brightness can sometimes have an effect on the ratio and probablility of a reboot, with brightness on full in a dark room being the most probable.
I am using the newest froyd rom 1.4.3 although i have tried pretty much every rom out there, I NEVER have this error when i installed a 1.5 rom which does not have apps2sd (weird that) which tells me that it is NOT a hardware fault.
I am using villains no logo kernel 19mhz - 691mhz
63.18.55.06PH_6.35.15.14 Radio
HTC Hero on Orage UK.
IF anybody can shed any light on this rather annoying matter resulting in this problem being erradicated will earn my eternal respect and a big clock. : )

dladz said:
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Click to expand...
Click to collapse
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?

btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I originally posted this issue and the descriptions from everyone else with the problem match mine pretty much perfectly.
I've taken all info off the sd card and performed a complete wipe of data, ext and davlik before formatting the sd card. I've put the blank SD card (apart from the ROM I'm about to flash) back into the phone and flashed. After config and before any new apps are installed on the phone I launch the camera and within 4 attempts at start the camera the phone will crash. This has happened across every 2.1 ROM I've tried, but doesn't happen on 1.5 ROMs.

Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?

btdag said:
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
Click to expand...
Click to collapse
Yep, it crashes using the stock app.
I've tried a rooted version of the offical but not the actual OTA update. I've not tried vanilla as I don't really want to run vanilla on it.
I've managed to take some logcat logs of the problem happening but there's nothing really specifc happening over a few crashes that would point to anything. .
I'm going to try to unroot my hero and downgrade to stock to start again. Just have to find a way to downgrade my bootloader first so I can put on the original RRU. I tried to downgrade before but got an invalid bootloader error.
The camera crash doesn't really affect me day to day as I don't really use the camera, where it is annoying is it stops you using apps that use the camera like goggles and layar.

Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.

btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I have formatted and re partitioned my sd card to a T and it still occurs and thats with everytime i install a new rom, i don't use titanium i go the long way around every time and re set up all my programs, I know i can replicate this error like i said and like i also said this does not occur in 1.5 roms.
I have also have this problem with vanilla, modaco's new one, villain rom, rcmix, froyd, it appears that ever since the phone was updated to 2.1 there is a problem when using the camera app.
I have tried to install a rom and replicate the issue without installing any apps at all and it still persists, the only thing i can say is that it doesn't happen when i'm either on 1.5 OR the phone is charging?
It sounds like the the phone is requesting access for use of the camera and then not putting back what it requested in the first place, like a cache or something, and it simply make the phone reboot when it is called upon again.
I don't believe it is a hardware fault, i know this sounds like wishful thinking but the phone does not have this error in 1.5 roms. Thus, it cannot be hardware. Simple!
Also a logcat does not show anything, i was only able to replicate the error once whilst my phone was plugged in, it just won't do it again, and when i posted my findings on villainroms bug report section, a few of the lads still didn't know what it was so i don't know what else to say.
I'm due for an upgrade in October so for me at least it's not that much of a deal but i'm planning on giving this phone to my daughter so it would be good to get it working for her.
Would save me a lot of earache.
If u need to know anything else then please let me know, oh and i am using a class 2 sd card, which i have been unable to change, however just today my girlfriend has just had a class six delivered and her old one will be up for grabs so i will test with that too. Has anyone else tried with multiple cards??? Also how do i find out what boot loader i am using (recover) as maybe the problem resides there.

btdag said:
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
Click to expand...
Click to collapse
Thats right, its any app which accesses the camera.
What could be the correlation between connecting the charger and not connecting the charger, could that be a power issue and the battery is delivering too low a power output on it's own to run the camera? Hence it works with the charger plugged in ?? Either way i think that is the only real clue there is to be honest, unless your phones still restart when the phone is plugged in, in which case it's not much use.

HTC Aria touch screen being very unresponsive

So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?

CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.

I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.

I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.

So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.

perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.

Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).

[Q] long time watcher and rom user. first time poster.

Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel

Tell us what your problems are here.

1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium

Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple

Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.

shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel

[Q] Screen Shift ICS 4.0.4-Sense 3.5-Cm Scream Rom-Miui Rom Help Me

hi my phone is just working 7.2 CM nand rom. ICS 4.0.4 - Htc Sense 3.5 - Cm scream rom - Miui Rom shift of the screen is in them. Usually red, vivid color screen is moving.Screen shift off color doesn't cause. Please help me.
Sorry for my english google translate

please help?

you should return to windows mobile first...

looks like a screen replacement that is not supported by our kernels

schlund said:
looks like a screen replacement that is not supported by our kernels
Click to expand...
Click to collapse
I had broken my screen repair.But it works cm7.2. ICS-HTC Sense-CM scream doesn't work. Why? What should I do?

please help me

what about old ROMs
mustafa3m said:
please help me
Click to expand...
Click to collapse
did try to switch back to SD card version of android or WM6.5??

do you have this problem yet?

tm.bax said:
do you have this problem yet?
Click to expand...
Click to collapse
yes, the problem continues

Hello there,
I recently changed from Schlund's Photonic SD Boot to CM 7.2 NAND Version, where I started having this strange issue. SD Boot worked just fine once I managed to get over the critical first 10 minutes after booting without freezing. Now the screen shifts occasionally, especially when I'm opening white windows or menus like the shutdown menu or the one where you enter a wlan security key. It stops in every position, just like mustafas picture shows. If I turn it around, the line dividing the screen just stays where it is, both frames will turn. I tried changing every single option related to the screen, flashing different versions, without gapps, without update, even [ROM] Phonerty MIUI v4 (ICS). The bug is a bit slower in this one, but still there. In all cases everything is the way it ought to be after tapping the standy button and waking it up again. But in most cases it will wont stay that way. I can't even flash it back to WM (and I don't really want to since I know how useful this little thing can be with Android on it), every RUU i tried to use told me I was using the wrong one. Any ideas? Anything new about this one?

I cannot use stock KK roms (TMO)

I've tried several stock KK roms and every single one is giving me same issue.
The rom itself boots up just fine. However, once the screen turns off and I turn it back in, it slowly turns on and it's just white or colored lines. The touch screen is still responsive, I can hear the sounds but I can't see a Damn thing unless I hard reset.
There are others like me, in Cloudy's roms, even Smiley's but we just get ignored or I believe I was told that since its just me and a few others it's not worth addressing.
So has anyone had this problem and have you fixed it? Can we get some TMO users to flash one of these roms so people know what I'm talking about? I need help guys.
You're my only hope.