Related
Hello,
I've tried to find this issue in the forums, but can't.
I have a problem with my camera on the AT&T Tilt (8925), it really slows down in low light settings. Unless it's really bright or sunny it takes horrible pictures. The preview mode jumps and skips.(I'm using the ROM it came with)
The 8525 that I had before would take pictures and video no problem in semi low light situations, but the Tilt is not even close.
Please let me know if other people are having the same problem or if you think I have a defective unit or something is wrong with the ROM.
I don't think anyone has ever had a problem with their camera in low light. It must be just your phone. I would take it back to ATT and demand a refund and a free phone for your troubles.
i agree, i think not a single person in this forum has any issue with using the camera in low light conditions. In fact, I'm pretty sure that if you look in the kaiser wiki, you will see nothing about low fps in the camera at all.
Have you pressed Control Alt Delete?
Kaze0110 said:
Have you pressed Control Alt Delete?
Click to expand...
Click to collapse
Oh, is this a webcam he is talking about?
ok thanks, I get it
kspirit said:
ok thanks, I get it
Click to expand...
Click to collapse
Haha, that was sweet. No one was suggesting that you check out the wiki and you totally did not get the hint that they were not hinting.
grizzley said:
Oh, is this a webcam he is talking about?
Click to expand...
Click to collapse
Oh, which reminds me, I was going to bring this up after I tested it as working or not.
I had a webcam that had the same problem as this phone's does.
Point being, I was going to install the latest camera software because that one (the 5.xx version) had different registry settings than the 4.xx one did. And I THINK, that there was a registry setting that defined the different increments available for the lighting scenarios.
EG: you should be able to deactivate the camera's ability to auto adjust to light, or at least increase the time before it does to some unholy number.
kspirit said:
Hello,
I've tried to find this issue in the forums, but can't.
.
Click to expand...
Click to collapse
How can you say you couldn't find the answer? There are tons of threads and a classaction law suite (or something like that) with this problem stamped all over it.
Ok so I don't know how HTC can allow this type of thing to happen but the Kaiser is by far the worst phone I've used in terms of bugs.
The camera... oh the camera...
My secondary VGA camera takes a 5x clearer photo than the 3MP one.
The VGA camera has no lag or reduced fps in the viewer, yet the 3MP camera has horrible horrible lag when you press button and what seems like 3-5 fps.
This is all the same with the video...
Can somebody tell me what the ****?? Are you all having this problem also or is it just me?
Could it be my radio?
I'm using ROMeOS 4.21
Thanks... and HTC... eff you!
edit: forgot to mention I've tried editing the registry and changing the button to half press instead of full... nothing works.
I'm sorry, but this sort of thing has been discussed before.
Here:http://forum.xda-developers.com/showthread.php?t=360001&highlight=Camera
Here:http://forum.xda-developers.com/showthread.php?t=426101&highlight=Camera
And try searching for the Subject "Camera" in this Fourm. You'll find a few posts.
I am not going to spend another minute trolling on this issue.
Dave
Thanks Dave but I've really tried everything suggested in those thread already.
From changing the registry in HKLM\Software\HTC\Camera\Captparam
to installing HTC Album and Camera (with no improvements).
Also I don't see how the first link you posted is relevant at all.
This is why I come to think it is either a screw up in my registry or my radio?
I think the camera in general is bad, I though the first link was a different thread, sorry.
If you search for Threads with the title camera in Kaiser General you will see the scale of how many people have complained about this camera. I am not happy with mine, but I also own a EOS400D, so it's not too bad
Dave
lol I see fair enough... For me I was planning to use my phone camera as my primary camera.. I really just cannot believe the VGA camera can operate at a higher quality than the 3MP..
I honestly think there is a fault in my registry..
I'll say it again.. sometimes the camera works perfect and takes a picture instantly with no FPS lag in the viewer, but most of the time it will be extremely low FPS and after I press the shutter button it will lag for 3 seconds then capture a fuzzy ****ty image.
deXtrous said:
lol I see fair enough... For me I was planning to use my phone camera as my primary camera.. I really just cannot believe the VGA camera can operate at a higher quality than the 3MP..
I honestly think there is a fault in my registry..
I'll say it again.. sometimes the camera works perfect and takes a picture instantly with no FPS lag in the viewer, but most of the time it will be extremely low FPS and after I press the shutter button it will lag for 3 seconds then capture a fuzzy ****ty image.
Click to expand...
Click to collapse
Do a Hard Reset and / or try another ROM, if you really think there is something in the registry corrupt / wrong.
Ta
Dave
DaveShaw said:
Do a Hard Reset and / or try another ROM, if you really think there is something in the registry corrupt / wrong.
Ta
Dave
Click to expand...
Click to collapse
Might just do that, cheers.
deXtrous said:
lol I see fair enough... For me I was planning to use my phone camera as my primary camera..
[blah blah blah]
Click to expand...
Click to collapse
You have got to be kidding.... It's convenient to have a decent camera built into the phone. But your primary camera? Ugh.
deXtrous said:
lol I see fair enough... For me I was planning to use my phone camera as my primary camera.. I really just cannot believe the VGA camera can operate at a higher quality than the 3MP..
I honestly think there is a fault in my registry..
I'll say it again.. sometimes the camera works perfect and takes a picture instantly with no FPS lag in the viewer, but most of the time it will be extremely low FPS and after I press the shutter button it will lag for 3 seconds then capture a fuzzy ****ty image.
Click to expand...
Click to collapse
Have you noticed that the camera takes faster pics in lit areas and slower the darker it gets? This topic is fairly redundant. Click my Vegas link and you can see what the camera does.
Ok, so you're getting a fuzzy image, that will be due to movement when pressing the button.
To improve this slightly use the 3 second timer, that way you can line it up, press the button and hold the camera steady to get a more stable picture.
No, its not a fix for the poor hardware, but it helps a little.
Try removing the transparent cover from the rear casing - or just take pics without the rear casing. Pic quality improves no end....
deXtrous said:
Ok so I don't know how HTC can allow this type of thing to happen but the Kaiser is by far the worst phone I've used in terms of bugs.
The camera... oh the camera...
My secondary VGA camera takes a 5x clearer photo than the 3MP one.
The VGA camera has no lag or reduced fps in the viewer, yet the 3MP camera has horrible horrible lag when you press button and what seems like 3-5 fps.
This is all the same with the video...
Can somebody tell me what the ****?? Are you all having this problem also or is it just me?
Could it be my radio?
I'm using ROMeOS 4.21
Thanks... and HTC... eff you!
edit: forgot to mention I've tried editing the registry and changing the button to half press instead of full... nothing works.
Click to expand...
Click to collapse
This has been discussed many times before...The camera is only usable in daylight. Even artificial light makes it really slow (bulbs) Here's why whenever you use the camera in other conditions than the daylight it switches itself into "Night Mode" and because of the lack of optimized 2D drivers the nightmode is terribly slow. Now... there's a small workaround....turn on the camera...if it's slow...press the button on the side the one that switches the screen off..press it again after about 10 seconds and you should have satisfying amount of frames in the camera app. Basically this trick forces the camera to turn off the night mode at least for a while. The only drawback is the quality of the pictures...they are darker. So if you disable the night mode through the registry you will have the camera without any lags.
Good luck
You think the Kaiser is the worst phone ever because it takes bad pictures. Wow. I think it is the best phone ever with an ok camera. I didn't buy the phone because of the camera.
wmg76 said:
You think the Kaiser is the worst phone ever because it takes bad pictures. Wow. I think it is the best phone ever with an ok camera. I didn't buy the phone because of the camera.
Click to expand...
Click to collapse
Not only the camera mate, and it's my personal opinion.
The phone itself is very buggy, crashes, not very responsive..
I thank got I found this forum or else my phone would be in the trash by now..
PS. Was your post even needed?
oh, oh, oh.
Please, deXtrous, a little humility. You joined last month and go around shouting at people already?
Perhaps your phone bugging out and crashing is a result of multiple registry edits, application installs, radio/spl/rom incompatibility etc. Not necessarily of putrid quality of the phone itself. Look around this forum: there are many MANY people who are either happy with their Kaisers, or have only minor gripes. This should mean that the phone is not inherently bad, just that - maybe- it is less than perfect... but then, what IS perfect?
Ever since I switched to ROMeOS (easily half a year) I haven't had a single hang-up or bug-out. Granted, I tend to use a tried-and-tested set of applications, but hey, there are about 40-50 of them! And my Kaiser still works nice and fast..... sans the camera which still sucks... but hey, it's just an effing camera. Useful in a phone but FAR from key.
deXtrous said:
Not only the camera mate, and it's my personal opinion.
The phone itself is very buggy, crashes, not very responsive..
I thank got I found this forum or else my phone would be in the trash by now..
PS. Was your post even needed?
Click to expand...
Click to collapse
You're asking a guy who's defending a kaiser, in a kaiser forum, after you rubbish the kaiser, if he needed to post. I think you should chill for a bit..
OK, enough. No need to start laying into each other.
Can a Mod close this thread? Nothing constructive can come from this.
Ta
Dave
Ha... Sorry I find this kind of funny..
It's just a phone guys, no need to take offense to anything I say about a silly phone..
It's my personal experiences with the phone. Not everyone can be happy with the product they buy but why should the unhappy ones be shunned off by their counterparts for simply voicing their opinions?
Everyone has an opinion and view on things, no need to be offended of my opinion that the kaiser is a piece of crap with **** battery life, **** camera, flimsy buttons and crap hardware (IME).
anyway,
The camera was like this even prior to any ROM swapping or registry editing, which is why I thought a new ROM might help but apparently not.
Maybe you have a bad phone, I know I don't think mine is buggy and non reponsive. Also nothing I have on mine seems to be flimsy..
Bad phone maybe?
Hello all,
As developers start to use firmware 1.5 I have updated the GPS status app to work with the new firmware.
The good news is that I no longer have to use internal APIs. Some features have been removed or changed:
- Screen orientation settig has been removed as it can be configured globally in 1.5
- Magnetic declination setting is removed too, but the good news is that declination is now automatically calculated (without internet access) based on a geomagnetic model. The model also gives the absolute value of the magnetc field at your location which is also displayed.
- finally: the GPS is not automatically turned on, because average programs can no longer turn on the GPS (it is possible only by using the system settings program) (GPS switch appliction will no longer work)
Have fun, comments are welcome.
Rudolf
If you start the app without enabling GPS first, it crashes right away.
Karolis said:
If you start the app without enabling GPS first, it crashes right away.
Click to expand...
Click to collapse
Thanks, noted the issue.
Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...
i hope this works because GPStatus is my favorite app.
g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.
without moving, my heading goes frim 78-81deg.
joeydsmith said:
g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.
Click to expand...
Click to collapse
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Having acceleration at 1.0 g is correct (at least GPS Stus 1.5 works the same way) as we are standing on the surface of the earth Thats a different stiry whether it is correct to call it "acceleration" for ordinary people (I know Einstein would not mind it )
lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.
joeydsmith said:
lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.
Click to expand...
Click to collapse
Version 1.4 did that, but that was not correct.
The problem is that acceleration is a vector not a scalar. I.e. I have to add/substract vectors not scalars...
example:
- If you would accelerate horizontally with 1g and in addition the earth has also 1g gravity, you would feel (and your phone would measure) approximately 1.41g (sqrt(1g^2+1g^2))
- on the other hand if you would accelerate vertically (upwards) with 1g, your body would feel 2g
The real problem: it is not possible to measure the direction of your acceleration (and according to Einstein its not even distinguishable from the gravity at all).
Maybe I will assume that the acceleration is horizontal (which is true for most ordinary people, moving on the surface of Earth). The rest (astronauts during launch, parachute jumpers) will get slightly wrong results, but I'm hoping they will have better equipment than relying on their G1
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
meanwhile i thanks so much your work and hope gpsstaus.apk go to work in the future at least good that we have working in the past...
best regards and electronics greetings from spain
I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...
rhornig said:
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Click to expand...
Click to collapse
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...
unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
Click to expand...
Click to collapse
That sounds like the compass is being influnced by a magnetic field, try waving the phone in a figure 8 to get it to reset itself.
koxx said:
Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...
Click to expand...
Click to collapse
Thanks. Fixed (hopefully) and updated the first post.
delta_foxtrot2 said:
I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...
Click to expand...
Click to collapse
Yepp. Thats a bug. Thanks for finding I will fix it for the next release.
unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
Click to expand...
Click to collapse
After firmware upgrades or if you experience strong magnetic field the internal compass must be recalibrated. Check the heading reading in the upper left corner. If it contains ?, ?? or ??? after the number, then your compass is inaccurate and must be recalibrated.
As alsready mentioned, you should draw big 8s in the air with your phone for about a minute. If everything goes well, the ? marks should go away and your compass should be much more accurate.
rhornig said:
Thanks. Fixed (hopefully) and updated the first post.
Click to expand...
Click to collapse
It works now ! thank you !!!
delta_foxtrot2 said:
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...
Click to expand...
Click to collapse
Thanks. Good idea, however the android framework itself should do the filtering (i'm already using the slowest possible update frequency which means the highest filtering). I will wait until the final 1.5 firmware comes out, and then revisit the issue.
Yay. It works. The compass does look a little faster
On my third galaxy note now, read more about it here.
The gyroscope isn't working, I've tried calibrating it many times and I did a factory reset of the phone.
Is there a way to fix this or am I screwed?
i think i have the same problem! the accelerometer works perfectly, but the gyro doesn't move at all while calibration, is that what u r facing?
parthpatels007 said:
i think i have the same problem! the accelerometer works perfectly, but the gyro doesn't move at all while calibration, is that what u r facing?
Click to expand...
Click to collapse
Yeah, the gyro ball isn't moving at all during calibration. The accelerometer is moving correctly only after calibrating it, but after some time the ball can be on the left side when it's supposed to be on the right side or something like that.. I'd hate to be forced to send this one back as well... pretty tired of sending back replacements and on Samsung's bad quality control of their new released product...
though the gyro isn't getting calibrated, but i think it's working perfectly. correct me if i'm wrong, maybe some1 who has used other phones having gyro may know better
For me the ball in calibration menu is not moving at all. However, if I dial *#0*# and select sensors, readings from gyro are ok. Seems like a software problem.
tomksoft said:
For me the ball in calibration menu is not moving at all. However, if I dial *#0*# and select sensors, readings from gyro are ok. Seems like a software problem.
Click to expand...
Click to collapse
Indeed. If you download a sensor checker you will see it is working perfectly... the little ball in the calibrator doesn't just move.. = software.
Sent from my GT-N7000 using xda premium
The Gyroscope actually works
http://youtu.be/rZx_x9zB1dE
Thanks to tomksoft for the *#0*#0 code
Forget me if I'm wrong but the ball shouldn't move should it? Little test for you guys, go into calibration and move the phone around, do you feel a slight pull from the phone when moving it? as if you were holding a spinning gyroscope? Mine does this, its a weird sensation but if it does do this then your gyroscope is working fine. I think if the ball moved the gyroscope would be broken because its suppose to stay dead centre?
Alexanderbooth said:
Forget me if I'm wrong but the ball shouldn't move should it? Little test for you guys, go into calibration and move the phone around, do you feel a slight pull from the phone when moving it? as if you were holding a spinning gyroscope? Mine does this, its a weird sensation but if it does do this then your gyroscope is working fine. I think if the ball moved the gyroscope would be broken because its suppose to stay dead centre?
Click to expand...
Click to collapse
i doubt what u r saying is right :\ correct me if wrong
Alexanderbooth said:
Forget me if I'm wrong but the ball shouldn't move should it? Little test for you guys, go into calibration and move the phone around, do you feel a slight pull from the phone when moving it? as if you were holding a spinning gyroscope? Mine does this, its a weird sensation but if it does do this then your gyroscope is working fine. I think if the ball moved the gyroscope would be broken because its suppose to stay dead centre?
Click to expand...
Click to collapse
lol wut?
he says 'forget him'
parthpatels007 said:
i doubt what u r saying is right :\ correct me if wrong
Click to expand...
Click to collapse
I second that
;-(;-(;-(;-(;-(
Hello all!
I also thought my gyro wasn't working, because the calibration ball stood still. Before I knew about the sensor test code, I found a nice app to test it, called GyroRotate. It basically just shows a colored cube which rotates if you rotate the phone. Seems to be working great on my phone. The only thing is that when I do 360 degrees with phone, the cube seems to have rotated only 180 degrees. I don't know if this is the gyroscope reporting such values, or the app is coded in such a way.
I didn't come to the conclusion that there is something wrong with the gyroscope because the ball isn't moving during calibration. But because screen rotate will work randomly and I need to calibrate it again for it to work until it starts acting weird again. For an example, if I tilt my phone to the right it will act as if I tilted it to the left. Sometimes it will act as if I was holding the phone in landscape mode when I'm not etc.. Really annoying.
Edit: I also have problems with playing games like Labyrinth where the ball won't respond accuratelly to how I am moving the phone.. It will work if I calibrate the phone but after a while it will stop working again.. I also did the *#0*# test and it said PASS.
bnapalm said:
Hello all!
I also thought my gyro wasn't working, because the calibration ball stood still.
Click to expand...
Click to collapse
I don't actually have a Note yet, it's in the mail, but could it be that you have to hold on the screen for it to work? The reason why I bring this up is because, correct me if I'm wrong, in the browser if you press and hold onto the screen with two fingers and move the Note it zooms in/out, and this function uses the gyro, I believe.
k1ng617: no, at least for my Note, the ball stays in the center whether I put it on the table or pick it up and wave/rotate all over the place.
bnapalm said:
k1ng617: no, at least for my Note, the ball stays in the center whether I put it on the table or pick it up and wave/rotate all over the place.
Click to expand...
Click to collapse
How about in the browser does the two-finger hold and zoom work? Or the move an item across homescreens work by motion? Phonearena says this is handled by the gyro. If it does it might just mean the application is broken.
k1ng617 said:
How about in the browser does the two-finger hold and zoom work? Or the move an item across homescreens work by motion? Phonearena says this is handled by the gyro. If it does it might just mean the application is broken.
Click to expand...
Click to collapse
Yes, the two-finger zoom works flawlessly. The motion-icon-moving does work, although I can't seem to always get it to work.. But I'm guessing it's using accelerometer, since I have to move the device left/right (this also works if I don't rotate the phone at all and keep it straight while moving left/right)
My Note's gyro is broken too It's easy to test the gyro with e.g. google sky map
https://www.youtube.com/watch?v=JrK1wQjh980
They are testing palm print and fingerprints detection by touch screen. Seems that touch resolution is enought to reconize one print from another
And this is the cool stuff: They use a nexus 5 to test... Very interesting
Are you sure it isn't a modified nexus 5?
no
i think that is modified nexus 5. i didnt saw it before
Well judging by what they describe, they are using any touchscreen as a scanner. I don't thing you need to modify anything internally, I think it's more software based.
Basically you just need to root your nexus, and have access to the digitizer directly in order to track patterns when you touch the screen.
Based on the patterns you get to track thanks to the digitizer, you can authenticate or reject an user. For me, it looks totally software based.
Remember that app you use to track how many points you can do on a touchscreen? If you press one it shows you the coordinates and so on and so forth until you reach 10. I think it's based on something like that, except it's probably much more advanced tracking since you can get patterns for fists/ears/fingers etc.
Judging by the looks of it though, I don't think it can read your "fingerprint". I don't think the resolution is enough. So, instead if reads your fist print since the resolution should be enough to calculate who's who. (I don't know if i`m making any sense right now lol).
Anyway, in short, looks okay, as long as you use fists/ears , whatever. Since Google introduced fingerprint auth, I don;t think they are going to allow fists and ears prints in their APIs so I don;t think you;re going to be able to use your fists for buying stuff from Google play, still , for a nerd like me the video is very satisfying.
its a project by Yahoo,... saw it last month i think,... for more info here
personally i think it wont be that secure and in cold climates it would be pretty hard to do that,...
chiragkrishna said:
its a project by Yahoo,... saw it last month i think,... for more info here
personally i think it wont be that secure and in cold climates it would be pretty hard to do that,...
Click to expand...
Click to collapse
agreed, this is why i was thinking Google will never allow this in their APIs.
doesn't seem practical, making a fist gesture to unlock your phone or placing it to your ear to unlock or gripping the phone to unlock.
It'll be socially awkward and won't be accepted as much as fingerprint sensors, besides I don't think it'll be that secure anyway.
Fingerprint sensors are the way to go :good:
As more and more devices get these sensors, I think in the long run.. fingerprint sensors will be cheaper
Think about it, A replacement Touch ID sensor on eBay is like $5... it's just the software implementation on it.