Related
Anyone know of a tweak for this? On my sprint TP it is automatically turned off if I take picture while on a phone call, so there must be an option somewhere to turn it off for good.
i would really like to know this as well
ltt002 said:
i would really like to know this as well
Click to expand...
Click to collapse
Strange that it gets turned off during a phone call. Can anyone else confirm this?
yeah i tried it during a call and it does get turned off during a call.
i want to turn it off because the autofocus takes so long. especially when i need to snap those quick pictures...
Same here, no autofocus during a phone call... I'm using original ROM.
I'm very interested too in a solution for that strange behavior.
I would like to know how to turn it off as well because it takes too long to snap the shot! Would be great if there was an option to turn it on or off!
May no be EXACTLY what you're looking for, but go in to camera->settings->advanced and on page 3, there's a Shoot Option. Change this to Full Press, and no more AF.
dew.man said:
May no be EXACTLY what you're looking for, but go in to camera->settings->advanced and on page 3, there's a Shoot Option. Change this to Full Press, and no more AF.
Click to expand...
Click to collapse
I have it at Full Press, but that still is auto focus. As soon as you hit it, you will see the camera try to focus on what ever you're trying to shoot before it actually takes the photo.
I too am curious as to how to turn it off.
there's gotta be like a registry tweak????? someone? anyone? haha
Auto Focus - turn off tweak
ltt002 said:
there's gotta be like a registry tweak????? someone? anyone? haha
Click to expand...
Click to collapse
Even i m in dire need of this tweak........sometimes its impossible to get a good snap, bcos of the delay caused by auto focus.......
i was using UIQ 3 phone earlier, where a half press would lock the focus and full press will immediately click snap without a delay.....
can someone make sum tweal on similar lines
please someone. haha
BUMP.......
Turning off Auto Focus
Anyone help !!!!!!!!!
Bump
This is very odd. I guess that even HTC knew that the camera program was either not optimized or demanded to much resource so they cut off the autofocus mid call.
From my own experience, its really hard trying to figure out the system calls coming form the dialer, i dont think this is going to be an easy fix.
Bump!
Bump!
Bump!
it would be nice if someone could do this? i would donate happily )
also id really like a auto lfash - which i think is in development
but this is a good idea as i agree it takes so long to focus that you hardly ever get a good shot
I'm interested in this. Have missed many pics due to the focus being so slow!
why does nobody want to reply to thread with an answer? strange seeing as there is so much demand
I use AutoFocus and have no delay in taking a picture.
If you have a delay in taking a photo just change the settings using the Advanced Configuration Tool. Under the camera options, capture delay should be disabled, key delay disabled and capture key delay set to zero.
Also, try this:
HKLM/Software/HTC/Camera/Captparam/
and set
CaptureTimer = 0 (old=5000)
Two more things to do - go into the camera advanced settings (in the camera itself) and turn off the click sounds and set the review time to no limit. With those changes above I think I have a working camera here...
While we're at it, if your photos are yellow change the white balance settings: http://www.fuzemobility.com/?p=951
Hey all,
I just got (and totally love) the Fuze. I've already flashed it to NATF's 2.2 and it's just amazing. The only problem is that somewhere between yesterday and today, the camera has totally flaked out on me :-(.
I'll take a picture (and regardless of if its set to store on the memory card or internal mem) and once I opt to save it, the Fuze just hangs with the "Windows thinking" ball spinning. After a while it goes back to "Albums" and the recently shot picture isn't there.
I implemented the GPS fix and have been toying in Advance Config -- but I don't think any of those changes should have affected the camera. Even weirder, the picture counter is incrementing and I do have open storage on both the card and internal.
Any ideas?
- Matt
same thing happened to me.
Turns out autoconfig has a bug for the fuze.
For the camera options in autocofig
there's something called portrait, and was initially disabled.
changing it to enable breaks the camera.
took me days to figure that out...l o l
funnysam said:
same thing happened to me.
Turns out autoconfig has a bug for the fuze.
For the camera options in autocofig
there's something called portrait, and was initially disabled.
changing it to enable breaks the camera.
took me days to figure that out...l o l
Click to expand...
Click to collapse
Thanks! That was the problem and now the camera works fine! Is there a FAQ or something this should go into? Without your help I would never have found that.
- Matt
haa..np at all..just sharing something that i've found out after hours of hard resetting, flashing, installing, etc... l ol
maybe tomorrow'll be you helping me...
cheers!
-sam
Thanks!
I had this problem too, on both my Sprint Touch Pro and AT&T Fuze. Wouldn't save in photo mode (though video, contacts photo, panorama etc. modes were okay). There was no error message on the Fuze so I didn't realize there was a problem until I went looking for some pictures and couldn't find them. After I figured out what has going on I checked the Sprint version to see if it had the same problem. The Sprint Pro at least gives an error message about not being able to save the file.
I had installed Advanced Config on both devices, so I thought it might be one of the settings in there that had killed the camera. However, telling AC to restore all settings didn't fix it so I've been tearing my hair out looking for other causes. Fortunately I found this thread before rendering myself completely bald.
Is this a bug in AC, or was I wrong in my assumption that "restore all settings" would restore everything to default?
I wonder how many people with Fuzes have this problem but don't know about it due to the lack of an error message.
Cheers,
Elizabeth
Thanks, saved me hours. My pictures would save sometimes, but only half of the picture. Works perfectly again now.
glad someone helped you out!
funnysam said:
same thing happened to me.
Turns out autoconfig has a bug for the fuze.
For the camera options in autocofig
there's something called portrait, and was initially disabled.
changing it to enable breaks the camera.
took me days to figure that out...l o l
Click to expand...
Click to collapse
Thank you for sharing. Can't say how much time you saved me but you did!
Some searches I used to find this were:
raphael camera issue
raphael camera pause
raphael camera saving problem
touch camera issue
touch camera pause
touch camera saving problem
omg! this has bugged for the last month or so, and i've been too busy to do a good search on it! i thought i didn't try the right combination. i don't remember changing anything with AC, still thanks so much for the solution funnysam
Does new Autoconfig version fix the bug?
The latest version is 3.3.0.0.
Does anyone know if that bug was fixed?
I ask (instead of providing feedback from my own experience) because I had the older version installed first, and then installed the new version over it, so maybe the bug persisted.
AdvConfig 3.3 doesn't list the option for portrait now.
AdvConfig 3.3 doesn't list the option for portrait now.
Hmm, interesting.
I performed a "Reset all settings" did a soft reset, and the option for the Portrait is now visible, with "Enabled (default)" selected.
Once I disabled that option, camera is working great.
bwb8771 said:
...Option for the Portrait is now visible, with "Enabled (default)" selected.
Once I disabled that option, camera is working great.
Click to expand...
Click to collapse
Same problems, and this works for me
Thanks, Bros
I'm using AC3.3 and have some weird camera issues. The closest option I can see in AC3.3 is to "Encode photos in portrait mode" and have NO selected. Is this the option you guys are talking about?
Yes. That's the option.
For me, that fixed the issue of the camera taking *forever* to save the picture and then display the options buttons. Even if I left the camera to finish, the picture never saved.
And, it didn't matter whether the shot was landscape or portrait - with that option enabled, the problem persisted until that setting was disabled.
Too bad, because that would be a nice feature!
Thank you!!!
This problem has been plaguing me for the last 2 days. Seems that whenever I get my Fuze working just the way I like, something else happens to irritate the crap outta me. Thanks for posting this!
Hm.. I'm using Advanced Config 3.3 as well and it doesn't display the portrait option. Does anybody know the registry setting this is modifying?
I am glad I stumbled across this series of posts. My experience with the Autocofig Bug gave me several days worth of heartburn. Thank you for the help!! It was much appreciated!!!
My keyboard has been lagging and doing other strange things that has got me worried. I did a hard reset on it yesterday and before I even installed any software I was forced to use the on-screen board for a spell as the slide out was un-responsive. I chalked it up to some background process being a hog and moved on. Now I'm finding some consitencies.
On a fresh reboot if I open the notes app in landscape mode and start typing I can see the cursor moving but nothing else till I get about 75% across the screen and then there are some black artifacts that now look like a ton of characters all bunched up in the space of about 3 positions wide. If I keep typing till it does a return then the entire line of text shows up and the process repeats itself on the next line.
If I have a full page of text open in say Total commander's text editor in portrait mode and slide the keyboard out, it will make a pattern of those black artifacts diagonally down the screen toward the left side and it will not correct itself. If I go back to portrait mode all is well again. There is seriously something wrong here.
I can't find any information from searching on the problem but hoping one of the experts here could shed some light on it and let me know if it's time to think about a return. Will try to uncover more if I can.
Many Thanks,
Eidolen
I took some screens of the problem. Both pics on the bottom are the same document but left is with TC's editor and the right is Word. Upper right is word as well. Hopefullt the attachment makes it through, if not I can host and link to it.
If you are running a stock ROM without any customizations (you said you hard reset your device), then chances are you have a defective Fuze. You should exchange it through AT&T's 30 day return policy.
If you're not running a stock ROM, then maybe you have an unstable one. Flash Da_G's clean ROM and see if the issue still occurs. Since that ROM has very little installed by default, the chances of a software conflict are slim.
Please post back here with your status.
I was thinking the same thing but the one thing I can't reproduce is when the keyboard doesn't respond at all. Maybe the graphics and the responsiveness are 2 different things?? I'm wondering if clear-type might have something to do with the graphics but that shouldn't lag the keyboard.
Gonna disable Clear-type now and will report back.
Eidolen
Well if I would have done a search with cleartype I would have found my answer, sorry I didn't figure it out sooner. At least pople can see what cleartype looks like on the Fuze in landscape mode if they were wondering. Apparently there is no fix known other than to turn it off. Hopefully the laggy response clears up as well but not getting my hope up. Thanks for your response.
Eidolen
What an odd thing for ClearType to do in landscape mode... as for laggy response, flashing a clean ROM would give you a good gauge as to how preinstalled apps can affect such lag.
Same thing happens to me but in txt'in sometimes my keyboard dont work at all and i have to restart the device, but this has happen to me only 3 times and the keyboard still have life cuz when i hit the fn key or shift the light comes on indicating that i put them on. as for screen lag i bearly get screen lag, because i did some hack i saw in this thread and it seems to of help alittle
by the way am using the ROMeOS2, i was wondering if i was the only person with this problem but apperently not.
Yep I got the same problem. I installed the NullKb cab on my phone to keep the kb from popping up in Opera. It didn't work. I uninstalled NullKb, It still shows up as selectable under other input options. The lag got progressively worse and even resets will not get the keyboard to work.
I've got the same problem. It's really strange.
I used ROMeOS but now am back to Australian Three official rom.
It seems like, when ClearType is active, I can't see what I am writing with the keyboard in LandScape mode. Even stranger is that when you write an SMS, the keyboard writes fine as there is T9 active.
I really need a fix for this as this has started to frustrate me.
I found having "clear type" activated was my problem as well. I turn it off and my kb is back to usual normal. I have a euro stock unit. Very happy with the rest of it's performance. I can live without cleartype.
eidolen said:
My keyboard has been lagging and doing other strange things that has got me worried. I did a hard reset on it yesterday and before I even installed any software I was forced to use the on-screen board for a spell as the slide out was un-responsive. I chalked it up to some background process being a hog and moved on. Now I'm finding some consitencies.
On a fresh reboot if I open the notes app in landscape mode and start typing I can see the cursor moving but nothing else till I get about 75% across the screen and then there are some black artifacts that now look like a ton of characters all bunched up in the space of about 3 positions wide. If I keep typing till it does a return then the entire line of text shows up and the process repeats itself on the next line.
If I have a full page of text open in say Total commander's text editor in portrait mode and slide the keyboard out, it will make a pattern of those black artifacts diagonally down the screen toward the left side and it will not correct itself. If I go back to portrait mode all is well again. There is seriously something wrong here.
I can't find any information from searching on the problem but hoping one of the experts here could shed some light on it and let me know if it's time to think about a return. Will try to uncover more if I can.
Many Thanks,
Eidolen
Click to expand...
Click to collapse
Hi:
I had the same problems. I fixed it by disabling cleartype in landscape (using Diamond Tweaks), and then installing the Fuze Keyboard fix cab, which I am attaching here for you, in case you want to try it. I'm sorry I don't remember the original post I got it from. After doing these 2 things, everything seems to be working great for me.
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..
as of now, auto rotate for the JF updates and the droidsans app only allow us to rotate to the left.
is it at all possible to make it so the phone can be rotated to the right as well for us left handers? the blackberry storm has this feature and i thought it was pretty cool but im not sure if the g1 can support it.
I'd like to see something like that, too. Mostly because the phone won't stand on the left side on its own, but it will on the right.
yup, i like this idea
I'd quite like a way to lock (a toggle) the rotation too if at all possible, possibly from the menu, or maybe by pressing the camera button.
Use? When using at an angle such as laying in bed and you really want landscape mode without having the keyboard open. Also when you lay the g1 flat on a desk it can switch to portrait by accident.
darkflare said:
yup, i like this idea
I'd quite like a way to lock (a toggle) the rotation too if at all possible, possibly from the menu, or maybe by pressing the camera button.
Use? When using at an angle such as laying in bed and you really want landscape mode without having the keyboard open. Also when you lay the g1 flat on a desk it can switch to portrait by accident.
Click to expand...
Click to collapse
that is an excellent suggestion!
erasedgod said:
I'd like to see something like that, too. Mostly because the phone won't stand on the left side on its own, but it will on the right.
Click to expand...
Click to collapse
lol thanks for pointing this out. what a pos
yeah this would be a nice adition, but what i would like more is a keyboard over ride that forces the screen to landscape mode when he keyboard is open.
i would LOVE to see this happining on the G1 it would awesome !
i would like JF to see this and say what he thinks, and if its possible to do it, please do it =D
IIRC this isn't possible. When they originally unlocked the auto rotate feature it was stated that the os only had coordinates for 0 and 90 degrees. They would have to make extensive edits to the source to add 180 and 270 degrees for orientation. I know, that's a bummer dude.
Well I just found an app that rotates both ways... It's a game called "Wordzor Lite"
I'm pretty sure this shows that it CAN work but i have no idea how hard it would be to incorporate it into the home screen and such...
left-handed people are evil!
golferguy17 said:
Well I just found an app that rotates both ways... It's a game called "Wordzor Lite"
I'm pretty sure this shows that it CAN work but i have no idea how hard it would be to incorporate it into the home screen and such...
Click to expand...
Click to collapse
No one is saying that it's not technically possible, we're just saying that the current state of autorotate is easy because Android is already set up to rotate when you open the keyboard, whereas there is nothing already in place for rotating the other direction.
erasedgod said:
I'd like to see something like that, too. Mostly because the phone won't stand on the left side on its own, but it will on the right.
Click to expand...
Click to collapse
hey, you have made my day! i never realized that..
Hey guys. Not that I would ever want to take anything away from the amazing work of people like JesusFreke, and as someone who has never posted before...
Just to say that I am working on a slightly more stable auto-rotate patch for the kernel with exactly that feature of auto-rotate left. My intention is to make this selectable in three ways.
Off
Right only
Left only
Both
milestone.it said:
Hey guys. Not that I would ever want to take anything away from the amazing work of people like JesusFreke, and as someone who has never posted before...
Just to say that I am working on a slightly more stable auto-rotate patch for the kernel with exactly that feature of auto-rotate left. My intention is to make this selectable in three ways.
Off
Right only
Left only
Both
Click to expand...
Click to collapse
keep us updated
i know of several apps on the marketplace that already have this feature but would it be much different to get the whole OS to rotate?
...i'm guessing it would lol
Actually, its not so different. The bigest problem is stability. Trying to patch in a deliberate action for autorotate feature. Like people have said elsewhere it can be a little bit too sensitive. Should have first version available next week (unless I manage to brick it!)
Anything people want to chip in about autorotate whilst I'm patching it? I am not the worlds greatest programmer but I can usually get there.
I was just reading this thread and what came to mind was the Bubble app on the market. It does this but of course this is on a much smaller scale and not across the entire OS of the phone.
But the nice thing is that you can turn the phone end over end and the bubble rotates with it. Not sure if the Dev for that app is on here, or if you wanted to email him to see if he could provide a bit of insight to possibly assist.
right. i am still working hard on this. any suggestions as to what deliberate action you would like to force rotate? I have thought about an up/down flick then turn the direction you want.
the only problem with patching four-directional autorotate is that it creates interesting problems of when it is perfectly still, it still manages to rotate itself. ie, i left it still on the desk and it was happily rotating itself.
any suggestions from coders. also, is there a quicker way to compile than to recompile the whole stack? ie selective compiling?
cheers.
milestone.it said:
right. i am still working hard on this. any suggestions as to what deliberate action you would like to force rotate? I have thought about an up/down flick then turn the direction you want.
the only problem with patching four-directional autorotate is that it creates interesting problems of when it is perfectly still, it still manages to rotate itself. ie, i left it still on the desk and it was happily rotating itself.
any suggestions from coders. also, is there a quicker way to compile than to recompile the whole stack? ie selective compiling?
cheers.
Click to expand...
Click to collapse
instead of having a force rotate, can you implement a Lock Rotate instead?
That way you can rotate to the desired position, and lock it.
darkflare said:
instead of having a force rotate, can you implement a Lock Rotate instead?
That way you can rotate to the desired position, and lock it.
Click to expand...
Click to collapse
or i could just do that! that would actually be a lot easier to code
I thought it might ~_^
How is the patch applied? if you need a tester give me a pm as i'd be interested in testing and providing feedback
~DF