When I start Microsoft TAG on the HD2, the picture turns into a Green solid block and stays like that, I can never get to the point where the camera snaps on to the TAG and resolves it. Does anyone see the same behaviour? Otherwise the camera works fine.
I tried reinstalling Microsoft TAG but still face the problem, I also applied the HTC camera fix and it did not help.
Thanks.
That happens to me as well. I found that opening and closing the menu usually gets the camera to work.
However, once the camera's on, it's really difficult to align it with the barcode because it seems to move in a different direction to me. For instance, if I move the phone left the image on the screen will move up, if I move the phone down the image will move left and so on. It's very counter-intuitive and rotating the phone doesn't make any difference.
Same problems. I have complained to microsoft who do not have the HDt HD2 in their recognised phone list, though it is heavily highlighted by htem.
It is windows phone aka windows mobile 6.5, but since updating to the new ROM from HTC my screen says "Press Enter to capture..." which is a bit stupid as I don't have an enter key.
I have tried both the windows mobile and the windows phone variants of the software.
It worked subject to the above limitations before teh rom upgrade.
That happens to me now too... with ROM 1.43, no problem (not tested with 1.48) and with 1.61, it's the green problem you have..
Which ROM version do you have?
I am on 1.43, not sure if 1.61 is a safe ROM to update to....
Related
Hey guys, I have sat here looking at all the white fading, well I have a new one... that I know is software related.
Steps for me to cause it...
Flashed CRC full the other day, newest version.
Added some files from his update..
Added Palm Messaging on my own... forgetting I hate that program.
Got to work today, decided to remove Palm Messaging... errored out while trying..
Decided... must be running, need to kill processes.. No process found and application wasn't running...
Tried to remove again... failed.. got mad and tried to remove many times over... fail fail fail.
Decided to do a soft reset...
Shows the CRC loading screens... goes to show the animation and fades to white...
After 10 seconds or so... the holding the comm button causes the phone to go into vibrate.. so I know something is running.
Any Ideas?
my own reply
Active Sync tries to connect, windows recognizes something connected.. so does linux. Nothing succeeds so far, assuming active sync is not running on the device... meaning win mobile probably isn't able to boot.
Ok.. I have the vibrate on phone key press... and that works... even though it's a white screen... I'm assuming something to do with .net is screwed up.
Windows is definitely running, just shut off windows mobile via holding the power and hitting yes... even though i can't see anything...
But I am still convinced this is a software issue, because other than holding my phone and playing with it... I can't imagine that it was caused from hardware.
Gone into bootloader mode (power + ok + reset)... and it allows me to flash from there. Flashing OS 5.2.20748 (Build 20748.1.4.0 PV DVH) Black(Full) NoBS V22... see what happens.. 50%!
Flashing new Rom worked just fine, white screen is fixed...
Obviously a software issue.. I would only have to assume that .net was corrupted by palm messenger. Hope anyone else out there finds this information useful.
You could've just HRed the Hermes too... That would've reset back to "factory"... Just like re-installing a rom...
Cheers...
I installed the WWE rom from:
http://forum.xda-developers.com/showthread.php?t=431738
Now when I enter camera mode, all I see is black. Once I take a picture, in the preview, it'll actually show what it took a picture of. So it works, but I can't see what I'm taking a picture of.
Any ideas?
Also, once its saved and I go to it to view it, it gives me that 'no application associated' error, but when I go programs and run the view manually, it works fine.
How do I re-associate it?
another problem
another problem that im having is that it will ask me for the pin when I turn on the phone but it will disappear and not come back
Well, fixed the camera one; didn't need to install the camera patch. Check qualities and looks like already patched.
Still stuck on the other two.
Can can't figure out how to get the music tab up now. Used to work, now it isn't working. Hm...
That's not typical behavior. Try downloading another copy of the ROM update and reflashing. Make sure there are no SD cards in your phone while flashing. For safe measure do a hard reset right after you flash. Let us know if you still have the problem after that.
bitsnpieces said:
I installed the WWE rom from:
http://forum.xda-developers.com/showthread.php?t=431738
Now when I enter camera mode, all I see is black. Once I take a picture, in the preview, it'll actually show what it took a picture of. So it works, but I can't see what I'm taking a picture of.
Any ideas?
Click to expand...
Click to collapse
Same problem for me with the swedish installation, black on screen but taking pictures without any problem. Kamera Version 5.04 (Build 31875) Swe.
How to solve this?
Hi
for camera issues upgrade to Radio rom 1.59.42.23 or Radio rom 1.59.42.15
I can recommend 1.59.42.15 , with ver...23 gps doesnt work good - slow start, TT7 doesnt work
Can't update with this radio rom. pda phone rom update utility shows error 262. Update stopped in 0%.
Tested with 2 difret PC's.
about the pin code box, i have the same problem that the enter pin screen dissapears very soon, but i just press the call button once and then its popping up the screen again so... for me no big problem....
hi
if ya have upgrade to wm6.1..please remember not to install Hot fix for Touch Cruise photo quality issue cos i had encounter similar problem after installing the fix but once i removed the culprit my camera was back to usual
andyhca said:
if ya have upgrade to wm6.1..please remember not to install Hot fix for Touch Cruise photo quality issue cos i had encounter similar problem after installing the fix but once i removed the culprit my camera was back to usual
Click to expand...
Click to collapse
Still black screen after uninstall of the Hot fix for Touch Cruise photo quality issue.
do a soft reset if still cannot work do a hard reset and delete the hot fix
andyhca said:
do a soft reset if still cannot work do a hard reset and delete the hot fix
Click to expand...
Click to collapse
Nope. Still black screen after soft reset.
Taking pictures is no problem and even the preview of the taken picture shows i 3 sec, and then black screen again.
I re-installed the ROM and everything worked fine again.
Installed the photo fix HTC released the camera was bugged again, so uninstalled that and it worked. So that solved that.
the picture viewer would stuff up when I installed the 3D drivers. I want to keep these, so how do I associate the picture viewer to the images I take?
Also, I can't get the music tab up. Was it excluded in this ROM?
Hello all,
I've been reading this forum for a while but only now decided to ask for help.
I am one of those unfortunate htc users who got the "camera problem".
I've bought my Oribit2 of ebay and first it was working fine with all the functions etc. Then i started upgrading it, flashed hardspl, new ROMs, radios... at some point camera stopped working. Not sure exactly when, cause i have tried several different ROMs and radios before even noticing that something was wrong. At that point i had c_shekhar's ROM installed.
I started reading more on the problem and tried to flash original ROM/radio or other ROMS and radios but nothing helped. Camera was still not working with error "Unable to capture photo. Unable to get frame data from camera device." or something like that and VERY slow response in camera.exe.
I've seen same problem in many different threads on different forums, mostly it's been an issue with incompatible Radios and was fixed by reflashing but also, in many cases ppl had the same as i do - camera not working and flashing doesn't help.
So, some solutions appeared:
- taking out battery for 15 mins, fixed camera for some ppl.
- installing Nadavi camera fix and/or uninstalling afterwards
- deleting all camera.* files from windows and installing Nadavi camera etc...
Well, i've tried them all. Nothing worked. The trick with taking out battery partially worked once: i've flashed original O2 WM 6.0 and took out battery for about 30-40 mins. After putting it back - voila camera working as it should be, no lag, no error. I'm happy! NOT.
Of course i immediately decided to flash some better ROM cause original is crap. After flashing - camera dead again and this time even taking out batter for more then an hour didn't do anything.
Trying trick with nadavi camera fix proved to be partially working or at least a good step in right direction:
lag went away, i could operate the camera program, switch from back to front camera(which was working fine btw) and even capture videos...
well... kind of. In preview the image is all fuzzy, just coloured line and noise, impossible to see the image, only some parts of it.
But it was clear that somehow, when using back camera, the image was a mix of a rear and front cameras! I mean i can't see clear picture,
but if i move my hand near one of the cameras i see changes in image(it's still mostly coloured noise).
All this is weird isn't it?
After evaluating everything, it makes me think that it's not a hardware problem, but really a configuration problem.
Looks like there is small flash memory in camera device, or some another way to keep camera initialization and it does not depends on radio or ROM.
Now, seeing that some ppl were able to fix the problem while installing original rom, or installing Nadavi camera fix or both, makes me think that under some
specific conditions these internal camera settings can be reinitialized.
While browsing net, looking for answer, i have found this :
Some of us had problems with Htc devices recognizing the on board camera after installing new ROM's.
It has been my technical opinion and observance that this problem can accrue when you manually put the devices into bootloader mode and don't press the camera and power buttons together along with the reset button correctly.
Once this damage is done you will have to reinstall the ROM radio files via uploading a manufacturer ROM to your device that has the radio ROM packaged along with it e.g. "HTC sprint beta ROM".
To avoid this I suggest always letting your PC force your device into bootloader mode. Because even the best of us might not mash the keys just right causing your ppc to forget all of it's configured camera associations.
Click to expand...
Click to collapse
HERE
http://www.howardforums.com/showthread.php?threadid=1396410
Well, this guy seems to agree with me that it's camera settings problem and there must be the way to fix this.
Well, again, i have tried installing original ROM and radio again, with no luck(even tried different combinations of nadavi fix , taking out battery etc...)
So, now, i believe, what we need is someone who knows a great deal about programming mobile devices and drivers for camera in particular to try and
produce some kind of a software that can reinitialize these camera settings(this is if this theory is correct).
Since my phone was bought off ebay, i have no guarantee and cannot send it back for repairs.
Does anyone know the right person who can do this? Or maybe some other solution to fix the camera?
I'm in the same situation. I was using udk 4 or possibly 5. One day I noticed the camera didn't work. I still had an icon for in under programs and the default button turned it on. Since then I have tried newer roms and several radio roms. I have no icon for camera under programs and the camera button on the phone just loads the camera album.
Can anybody help us?
Many Thanks
Dan
The same thing happen to me as for you guys.
The only thing helped as I tried new radio roms and still was not working.
So I tried radio Murata - 1.58.21.23. And now camera works perfectly again!!
You can search here and you will find this radio on this forum.
cheers
Andrew
I have tried that radio.
the same story. radio is murata
will try to go this hell route - nadavi camera and stuff
Ive been on this all day now. Nothing I have tried has made it work. I'm on the original rom from o2 now and it's going back to the shop tomorrow.
Can they tell if i've put 3rd party roms on the phone? If so is there anything I can do to "re lock" it?
Cheers
Dan
Maniakaz said:
The same thing happen to me as for you guys.
The only thing helped as I tried new radio roms and still was not working.
So I tried radio Murata - 1.58.21.23. And now camera works perfectly again!!
You can search here and you will find this radio on this forum.
cheers
Andrew
Click to expand...
Click to collapse
not in all cases
i have a camera problem too...what is the answer?
Same problem for me, Camera not working any more
I was using M-Amine 2 ROM and camera started malfunctioning, (the first days was alleatory, and I arrived to fix it restarting camera or taking pictures two or three times, until finally the problem becomes definitif...)
I tested other roms (c_shekar, 3VLIT, Nadavi fix, and other radios...even original ROM....come back to c_shekar....with some small changes, but finally retour the same problem "unable to capture frame...".
Today I have reinstaled again Original latest French ROM, at the begining camera doesn´t worked, but suddenly It has come back again. Up to now still working after many resets and tests. I will keep you informed, I plan to come back to c_shekar, after some days of testing with original ROM.
it can be fixed with original rom
find my other post how to get ROM's with needed language.
b.r.
Alexandar
I have an O2 Orbit 2 as well.
I recently noticed that my camera isn't working anymore.
About 1 month ago I installed Core Player 1.2.4 and since then I had a lot of issues with the card. Folders starting disappearing, corrupted SD etc. Sometimes only some recent folders disappear.
However, most recently I discovered that the camera does not work anymore. Pressing the snapshot button doesn't start the camera. While the buttons do light up when the camera button is pressed (suggesting a software issue) the camera does not start. If I go into the Programs folder and start Camera, it starts. But when I press the camera button to take a picture, it goes upto the point that it makes the focus sound, the two framing aids (that look like a split square) turn green but that's it. No photo is taken. Camera however seem to work, everything looks ok through the camera but it just doesn't take photos/movies anymore.
I haven't installed/upgraded anything, I have the original rom.
I have tried to take out the battery for 30+ mins but the same issue happens.
It definitely looks like a software issue, either by a software that corrupted files (I suspect Core Player) and/or flash corruption issue (however I haven't got any software to tinker with the flash and haven't tried boot mode or whatever, just normal on/off).
Small update: I just noticed that altering the camera settings to "Half press" instead the "Full press" makes the camera take pictures.
However, returning again to "Full press" the camera doesn't take pictures again.
So a temporary fix is to set to "Half press" but even so, the camera application does not start when I press the camera button.
Can anyone please help?
hi, I have an old Polaris and 3 days ago upgrading from WM 6 to WM 6.1, causing the both cameras (front and back) to not respond although the screen still shows the numbers and stuff on touch screen that shows cameras are working fine, BUT pointing both cameras anywhere doesn't change the black view that's been displayed since the camera is turned on. weird. but when pressing the camera button, the picture taken is properly shown. I tried both camera (front and back), both produces normal photograph, but why the black screen?!
on top of that after the upgrade, touch screen has turn rigid that it's very hard to type. I have to play with the angle of touching the pen to the screen or else, the screen will just get stuck with whatever it was doing before.
any solution? please advise thanks.
Camera working but no Picture Monitor Screen
This may help you Bulukaki
I have a HTC P3650 allready with the WM6.1 upgrade
I downloaded today the factory update for picture quality, "Hot fix for Touch Cruise photo quality issue" from the HTC download site
After this upgrade , I was no longer able to monitor the picture of the camera on the screen. Just a black screen but with all the camera functions.
The camera was still able to take a picture, the picture showed up only after exposure on the screen. Similar to BULUKAKI`s problem
So my picture quality was not that bad prior to the photo quality upgrade and I removed the update from settings/system/remove programs and did a soft reset and the camera was again functioning as it should. Having said that, you may check wether or not the "Hot fix for Touch Cruise photo quality issue" was allready installed prior to your WM6.1 upgrade.
Maybe simply uninstall "Hot fix for Touch Cruise photo quality issue" will do the trick
Hope this helps
Hello,
I recently configured ActiveSync E-Mail on my HTC HD mini. Everything works fine until I power off and power on the device. The startup sequence is paused with the following text:
"Company policy has enabled device encryption. Startup is suspended. Select unlock to continue. Emergency calls: Press talk."
When I select Unlock then nothing happens (the button is pressed).
The device cannot be turned off by power off button (it only goes to sleep).
The problem is not solved by removing the battery, putting it back and powering on.
The only way to get the device working is to hard reset the device by the special sequence of keys.
Device: HTC HD mini
ROM: RUU_Photon_HTC_WWE_EastEurope_1.36.479.1_Radio_Signed_32.2803.05.06_0.63.05.36_Ship.exe
I reproduced this problem 3 times.
I downgraded from RUU_Photon_HTC_WWE_EastEurope_1.36.479.1_Radio_Signed_32.2803.05.06_0.63.05.36_Ship.exe to RUU_Photon_HTC_WWE_EastEurope_1.32.479.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe which seemed to remove the problem. However, it appeared after several power cycles also on 1.32.
Any idea how to correct this?
I had exactly the same problem when I purchased the HD minn a few months ago. It happened 3 times in a row that I had to hard-reset and re-install for exactly the same reason (no unlock keys after start-up.) I called my corporate's IT department. They said they changed something on my MS exchange policy profile that may help. Frankly, I can't believe that this was the real root cause of the issue but ever since then it works fine. Never had this problem again for 4 months.
Sorry that I don't have a real solution for you.
CM
Thank you for you reply. May I have additional questions?
1. What ROM release do you have on your HD mini? As you had the problem a few months ago it might be 1.32, right? I have the problem on ROM 1.36 when I first time power cycled the HD mini. It survived many power cycles on ROM 1.32 until the last one which caused the problem again.
2. Is there any chance asking your corp. IT dept. about the change they did?
==
edit:
It seems that the responsible one is HTC Sense. I upgraded from ROM 1.32 to 1.36. I decided to test this with HTC Sense turned off. The problem is no longer present on 1.36 when HTC Sense is off. However, it is a workaround only. I informed HTC support and I hope they will fix it.
Same problem as the others, only I found the cause!
Everything works fine on mine (1.36) until I change the lock screen wallpaper. As soon as I change that the device hangs on the unlock screen at start-up.
If you look at the way it all works, on start-up when you are prompted to unlock, you get the standard unlock screen with the slide down option, and a background picture. I'm guessing the default picture is held in un-encrypted memory, and so it works. If you change the picture, the new picture is held in encrypted space and can't be accessed until you add your key. Only you can't because the device has crashed.
One work around may be to assign it a background picture from the SD card. But having only just got the thing to work I don't feel like trying it in case it puts me back to square one.
Update: Yes copy the image you want to SD card and then change the lock screen wallpaper to point at that. Device boots normally with the new wallpaper.
Hopefully this will help someone.
radar: Thank you for your input. The explanation sounds reasonable. I'll test it once I need to reinstall the device. I'll stick with the working status I have for now.
I am in the middle of waiting for my hard reset to complete as I type. I just had the same exact issues as you all described. I wanted to add though that the background I was using when this happened was from my storage card so I dont know if that will fix anything.
Ill try to add anything else I find out. I am going to try this one more time and then forget about my work email if the same thing happens. Or I might try to find a new rom - but I like what I have
Edit: I actually just saw that you (radar) said the image on the card worked... weird. I'm goign to try again. If I could get around this everything will be working perfectly and I'm not ready to give up.
Try disabling HTC sense. It helped me.; I am running months (done several power cycles) without the problem.
Do you guys also have problems about when typing in a keyboard that 40% of the time it misses the touch point or pushing the wrong letter even thou you didnt pressed that letter?.. it always happening to me, i just tested this on CM7 and CM6.2..
When i tap "M" sometimes it taps the letter "B", sometimes when i tap the "Backspace" it sometimes presses the button around it like "M" or "L"..
Is this a hardware failure? or a kernel/driver/software for android that is failing?..
One more thing, if i hold an icon on the homescreen to allowing moving it, it sometimes dances around my finger..
I've had similar behaviour when one or more fingers almost touched the screen while holding it. Lay your phone on a table and check if it happens then too.
I think it's still the same, because will i'm testing it, im continously pressing the the letter "M" til it miss, then suddenly it misses everytime i press "M" i suddenly put the fone on the table while continueing to tap "M", still it misses.. my gosh, i hope its not a hardware failure..
anybody?
up anyone?...
Mine did that right before the touchscreen started to die. Check on it.
how sad, i think my warranty is over.. how much will i cost if i will get this to repair?..
I have the exact same issue.
http://forum.xda-developers.com/showthread.php?p=10836189
Another fellow has something similar, but not quite.
http://forum.xda-developers.com/showthread.php?t=922503
If I put Windows Mobile 6 back on the phone, the screen is back to its very accurate state. Android on SDcard works fine too. It's only when I try to use NAND / MAGLDR. Could you try flashing back Windows and testing it? And test an SD build as well?
FreakyFerret said:
I have the exact same issue.
http://forum.xda-developers.com/showthread.php?p=10836189
Another fellow has something similar, but not quite.
http://forum.xda-developers.com/showthread.php?t=922503
If I put Windows Mobile 6 back on the phone, the screen is back to its very accurate state. Android on SDcard works fine too. It's only when I try to use NAND / MAGLDR. Could you try flashing back Windows and testing it? And test an SD build as well?
Click to expand...
Click to collapse
I just bought this device second hand, dont know the record of this thing if it has really an issue when i bought..
i remember when i got this device to the 1st owner, its in windows mobile 6.5, i tried it from morning to night, i even txted a lot when it is still in 6.5, and i dont remember getting frustrated because of inacuracy.. it just started when i flashed the NAND ROM the night i bought it..
will try to revert back to WM6.5 and Android SD after work..
@FreakyFerret
according to one of the member in the thread you gave, his problem about accuracy has gone because of the kernel he used..
Did you used it? did it solve to you?, or do you have any other motheds that worked for you..
I didn't see anyone fixing the issue by trying a new kernel. But I've used a few different builds with different kernels, and it persists. I'll check the thread again later.