Related
Hi Guys,
Not sure if this is in the right section of the forum, but I'm looking to develop an application to test the responsiveness of the touch screen, either when clicking or making a gesture.
I have a pretty good understanding of the Android framework, but have not wrote an app from scratch by myself yet (although I have modified some apps).
I'm basically looking to find/calculate the number of samples returned from the touchscreen in Android when a person has his/her finger on the screen. Can any of ya'll help me get started in the right direction for this? Or perhaps know of any other benchmark tests that are open sourced so I can look over the code a little bit?
Thanks.
edit: So I see that the MotionEvent class would be the most useful and getHistorySize() is close to what I want but is more high level than exactly what I want, although it could be good enough. Any ideas on how I could use this or how to incorporate other functions to help make this work better?
The HTC One camera has cool features and can take good pictures.
However discussing it on XDA seems to lead to a lot of flaming, trolling and locked threads.
This placeholder thread may get resurrected at a later date, but for now it may be best to let camera information accumulate elsewhere.
Originally this thread was intended to contain information on the most interesting features and practical implications of those features were for taking successful pictures.
Also it contained specific details about which features were specific to which versions of camera software and how to determine which version of camera software you have.
PM me if you think the OP in this thread needs to be put back in its original state...
The second post in this thread contained a lot of common sense reminders about things such as
- why comparing this camera to other cameras is not helpful to people who just want to get the most out of *this* camera.
- how to compare (and how *not* to compare) two pictures to make a point
- how to have realistic expectations about this camera considering HTC's goals in balancing price, form factor, features etc.
These are just some of the obstacles that cause other camera threads to get derailed...
Reserved in case a FAQ or Glossary or some such becomes useful at some point...
I'm with the issue of prefocus with flash in low light condition.. is there any way to add the flash to focus like all phone do??
Inviato dal mio HTC One con Tapatalk 2
erto90 said:
I'm with the issue of prefocus with flash in low light condition.. is there any way to add the flash to focus like all phone do??
Click to expand...
Click to collapse
I haven't heard any best practices yet for total darkness situations. My results have been poor- the pre-flash is on for like a half-second, yet usually the autofocus doesn't lock on to anything. If there is *any* ambient light, you have a much better chance of acquiring focus if your subject is not moving and has *any* contrasty edges or patterns. (The camera "breathes" in and out of focus a lot while previewing in ambient light, but it is often close enough to allow a successful focus during the pre-flash and therefore a sharp image during the actual flash exposure) . If your barely-lit subject is amorphous, low-key, or moving, well, no. You're back to the same success rate as total darkness.
Also not forgetting Anandtech's 27,000 word review
http://www.anandtech.com/show/6747/htc-one-review
Lots of sample videos and photos of the camera's capabilities.
Thanks! added to OP.
I too would like to know why the HTC one struggles to auto focus when its dark. I have to take pictures 2 or 3 different times in order for it to come out good.
Sent from my HTC One using xda app-developers app
specter491 said:
I too would like to know why the HTC one struggles to auto focus when its dark. I have to take pictures 2 or 3 different times in order for it to come out good.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You answered your own question. Cos it's dark
Also, at the OP. Will you be writing up on the Topics for Discussion in your 2nd post, or are you just collecting info for those topics from various sources?
Both. When things have been quiet for too long I will pick one of them and do a deep dive.
My first area of exploration is to really try to see what changed with 2.17. There's so much good information buried in the ARHD thread (as well as bogus claims backed by poor or no evidence).
Can't wait to get a handle on that.
Sent from my HTC One using xda app-developers app
A number of users including myself have reported that their led on the back is always on, even when the device is powered down. The light is very dim and you will likely only be able to see it in a dark room. We are trying to figure out if this is a HW related issue (meaning we need to get our phones exchanged for new units) or if this is some kind of SW related issue that can be patched. It is important to find out just how widespread this issue is. Please take your S6 to a very dark place and check if your led is emitting any light and report back!
Thanks
It happens to mine. I created a post about it and the mods moved it to q&a. Which I thought was strange. Obviously it gets less views there. The true odd thing is that other threads in the general section are clearly question threads but are not moved.
Anyways yes my flash is always on. I have tried reboots, toggling the flashlight, taking photos with the flash, turning on and off different power modes. Ect.
madmanepic said:
It happens to mine. I created a post about it and the mods moved it to q&a. Which I thought was strange. Obviously it gets less views there. The true odd thing is that other threads in the general section are clearly question threads but are not moved.
Anyways yes my flash is always on. I have tried reboots, toggling the flashlight, taking photos with the flash, turning on and off different power modes. Ect.
Click to expand...
Click to collapse
Yeah I think it would be beneficial to let this thread get more views as we really need to know if we are all getting defective units. I hope Samsung is at least aware of this issue.
Others reported it in my thread. Maybe we can merge these together.
http://forum.xda-developers.com/showthread.php?t=3071356
Mine device has the issue. Doesn't seem to impact battery. LED's by nature require very little power to be lit. Whatever provides power to it must be faulty as a tiny bit of power is being sent to it thus it being very dimly lit. I'd wager on it being a hardware defect for sure.
Why don't you go and Exchange the device??
marcochapita said:
Why don't you go and Exchange the device??
Click to expand...
Click to collapse
I am gonna call T-Mobile about it tomorrow.
The device isn't out yet on major country's but I'm afraid it's a major problem on the first unit
madmanepic said:
Others reported it in my thread. Maybe we can merge these together.
http://forum.xda-developers.com/showthread.php?t=3071356
Click to expand...
Click to collapse
Here is another thread: http://forum.xda-developers.com/galaxy-s6/help/flash-lit-t3069039
This issue should be more widely reported and should also be brought to the attention of Samsung, T-Mobile, etc.
It might be relatively harmless, but we can't know for sure long term what this does for battery life and for the life of that LED.
I really doubt it is such a big problem, and I honestly don't believe it is anything hardware related (it can't be hardware related, really....). With the next OTA Samsung should fix that.
derWolf_ said:
I really doubt it is such a big problem, and I honestly don't believe it is anything hardware related (it can't be hardware related, really....). With the next OTA Samsung should fix that.
Click to expand...
Click to collapse
How do we know for sure that it isn't hardware related? Why would not all phones be impacted if it were just SW?
Do you have Google Fit installed? If so go into it's settings and disable its activity tracker - that "might" fix it.
http://www.androidcentral.com/psa-galaxy-s6-heart-rate-sensor-still-causes-issues-google-fit
Google Fit seems to have a bug with heartrate sensors.
MysteriousDiary said:
Do you have Google Fit installed? If so go into it's settings and disable its activity tracker - that "might" fix it.
Google fit seems to have a bug with heartrate sensors.
Click to expand...
Click to collapse
No google fit
poweroutlet said:
How do we know for sure that it isn't hardware related? Why would not all phones be impacted if it were just SW?
Click to expand...
Click to collapse
I can't guarantee you that it is not hardware related problem. Following basic logic though I can assume it is not, as I can't really see how it could be hardware problem. The flash doesn't just light up from itself you know, something triggers it to glow, even when the screen is off. I'm more than certain that there isn't a human-made light in the world that glows out of nowhere by itself- everything has a cause and effect.
And even though we are talking about the same software version (presumably) you know, that the hardware in the phone differs from unit to unit. That means that a certain part of the software may be triggering the flash to be light on, because your flash unit is not the same as on all other devices. Having said that I'm 99.9% sure it is software related and it will be fixed quite soon.
derWolf_ said:
I can't guarantee you that it is not hardware related problem. Following basic logic though I can assume it is not, as I can't really see how it could be hardware problem. The flash doesn't just light up from itself you know, something triggers it to glow, even when the screen is off. I'm more than certain that there isn't a human-made light in the world that glows out of nowhere by itself- everything has a cause and effect.
And even though we are talking about the same software version (presumably) you know, that the hardware in the phone differs from unit to unit. That means that a certain part of the software may be triggering the flash to be light on, because your flash unit is not the same as on all other devices. Having said that I'm 99.9% sure it is software related and it will be fixed quite soon.
Click to expand...
Click to collapse
I feel it is software related because it's more of a light leak, than a total fault. If it is hardware I would thing it wouldn't be the same for all of us with the problem, meaning dimly lit. Some would be saying theirs is medium on full on or the flash not working some of the time. Esp. If it was not working and just staying dimly lit, would signify more to me of hardware. We don't know what the update really fixed, so can't say it even targeted this. Hopefully bringing it to T-Mobile attention will get them to take a look at it.
I plan to get one from the store and have the clerk check it, in the back if there is no update before the 20 day online return period it's up.
Sent from my SM-G900T using AllianceR(●)m
Mod Edit
Thread Closed - Please see Flash always lit? thread already started on this topic.
ronnie498
Forum Moderator
Okay so this is kind of an idea/request I guess. I wish that someone would make some type of root that would make the Fingerprint sensor on the galaxy s5 function like the one on the Galaxy s6. Anyone else agree? If so reply or if there is already one please reply as well.
i dont agree. but thats mostly because i understand how hardware works.
its like asking for a file that makes a hdd into an ssd
its not the way it works
Croeta said:
Okay so this is kind of an idea/request I guess. I wish that someone would make some type of root that would make the Fingerprint sensor on the galaxy s5 function like the one on the Galaxy s6. Anyone else agree? If so reply or if there is already one please reply as well.
Click to expand...
Click to collapse
It's not the best way to start your xda career...
I think the s5 fingerprint sensor isn't capable of performing like that, I could be wrong.
Well I don't know, it could be done. New to this whole forum thing.
I think we can't do anything else than the swipe, but lockr or hi locker wich supports fingerprint is more easy.... Perhaps less secure, but it's easiest to unlock!!
I just thought that there could be a way to change it works. Eh, sorry I'm not good at this kind of stuff.
Croeta said:
I just thought that there could be a way to change it works. Eh, sorry I'm not good at this kind of stuff.
Click to expand...
Click to collapse
Hardware limitations basically limit how much software can do. Not much you can do if the fingerprint scanner itself works differently to the S6 one.
Correct me if I am wrong but with the right knowledge if you are able to alter the hardware application layer of the touch input for the finger print swipe you would be able to register the touches. I'm not 100% sure how to do it but there might be some sort of hardwares software help somewhere in wilderness
patch81 said:
Correct me if I am wrong but with the right knowledge if you are able to alter the hardware application layer of the touch input for the finger print swipe you would be able to register the touches. I'm not 100% sure how to do it but there might be some sort of hardwares software help somewhere in wilderness
Click to expand...
Click to collapse
there are 2 point regarding your topic ...
but first there is NO WAY the sensor can behave like s6 ... let me tell you how both works :
the galaxy s5 has a like motion-detection based sensor it gets input when you wipe not just press or touch thats number 1
number 2 all what you can do about it is limit the number of inputs the sensor records this may ease up the detection process
like in fingersecurity its a bit faster but you will have to swipe anyway the the system's but it has its drawbacks since the input signals are lower the effeciency of the sensor is becoming lower and by that i mean it might mix up and work with an anonymous person trying to unlock
i hope you got my point
Well I did say correct me cheers for the input haha.
patch81 said:
Well I did say correct me cheers for the input haha.
Click to expand...
Click to collapse
:cyclops::cyclops:
Hello, Recently I have this issue with the AOSP,GPE and TW ROMS. I test the game Oddworld Stranger Wrath ( have function with Gyro), and it go around (ghost) without I touch or hand my device, this problem occur on all roms, But I just can fix it on TW Roms with the code *#0... "device test" > Sensor and Gyro test, it calibrate and gyro works normal on Oddworld. Now on AOSP Roms and GPE, don' t have this function, and I try many apps from GP to try to fix it, but no results.... The only difference between Touchwiz rom and aosp is "device test" :/, any dev or person can help me please ? I would appreciate and give my thanks.
anyone here ?
Not as many as there were last year. The S4 is rapidly approaching three years old now, and many people have upgraded. In any event, you didn't search the forum, as this is a common question, though it actually has an uncommon answer.
Install Bubble Level from the Play Store and calibrate the gyroscope using it.
Strephon Alkhalikoi said:
Not as many as there were last year. The S4 is rapidly approaching three years old now, and many people have upgraded. In any event, you didn't search the forum, as this is a common question, though it actually has an uncommon answer.
Install Bubble Level from the Play Store and calibrate the gyroscope using it.
Click to expand...
Click to collapse
well, I used it, but don't solve the problem with gyroscope, you can try by your self and test the game oddworld on CM12.1 and see....
Yeah, well I'm not about to replace my copy of AOSP 7.1.1 with CyanogenMod to do this. I do however see more than one app titled "Bubble Level". Did you install this one?
Strephon Alkhalikoi said:
Yeah, well I'm not about to replace my copy of AOSP 7.1.1 with CyanogenMod to do this. I do however see more than one app titled "Bubble Level". Did you install this one?
Click to expand...
Click to collapse
Yes Sir, Bubble,GPS & Toolbox and others.... but don't give any results. I was think if have the possibility to adapt "device test" from touchwiz for AOSP ROMS, maybe it can fix this problem
To the best of my knowledge, that isn't possible due to the test suite requiring the Touchwiz framework. Honestly, if it's that much of a concern, I'd be installing a stock-based ROM and calling it a day.
Strephon Alkhalikoi said:
To the best of my knowledge, that isn't possible due to the test suite requiring the Touchwiz framework. Honestly, if it's that much of a concern, I'd be installing a stock-based ROM and calling it a day.
Click to expand...
Click to collapse
Understand, but have any way to fix it ? Provide any APP for aosp to fix ?You can test on your actual rom the gyroscope, I think it will drift way too on oddworld
hehk1234 said:
Understand, but have any way to fix it ?
Click to expand...
Click to collapse
Yes. Install a stock ROM.
Strephon Alkhalikoi said:
Yes. Install a stock ROM.
Click to expand...
Click to collapse
Well, So I never will fix the gyroscope drift way on AOSP and CM Roms ? :/
Sure. Install an app that allows you to calibrate the gyroscope. If that doesn't work and a stock ROM does, install the stock ROM.
In case you're having difficulty reading between the lines here, I don't have an issue with my gyroscope and have had AOSP on my S4 for a year and a half now. GPS Status & Toolbox was sufficient to get the job done, and the fact it didn't work for you is a sign of a different problem. A problem with your gyroscope.
Strephon Alkhalikoi said:
Sure. Install an app that allows you to calibrate the gyroscope. If that doesn't work and a stock ROM does, install the stock ROM.
In case you're having difficulty reading between the lines here, I don't have an issue with my gyroscope and have had AOSP on my S4 for a year and a half now. GPS Status & Toolbox was sufficient to get the job done, and the fact it didn't work for you is a sign of a different problem. A problem with your gyroscope.
Click to expand...
Click to collapse
When Lollipop become to old OS, I will update my device and try aosp Rom again. Another question Sir, on game vainglory with High settings graphics on (you can set it on config on the game) you can run it without any lags ?
I try to run this game on Aosp 6.0.1, but I get many slow downs.... I think is the driver update on adreno 320 cause this problem. When I back for aosp 5.1.1 or TW 5.0.1, runs without problem on high settings.
You're asking the wrong person. I only have four games on my device, and two of them are chess and yacht. The S4 hasn't been my daily driver since the beginning of 2016.
I will say this however: any AOSP ROM is better than LineageOS or Touchwiz, because AOSP consumes far fewer resources than both.
Strephon Alkhalikoi said:
You're asking the wrong person. I only have four games on my device, and two of them are chess and yacht. The S4 hasn't been my daily driver since the beginning of 2016.
I will say this however: any AOSP ROM is better than LineageOS or Touchwiz, because AOSP consumes far fewer resources than both.
Click to expand...
Click to collapse
Ok sir, thank you for share your experience here, I appreciate it . I will go to AOSP when the source code become more stable and bugs go way haha
I'm not aware of these bugs you speak of, but my usage pattern is not the same as yours.
Strephon Alkhalikoi said:
I'm not aware of these bugs you speak of, but my usage pattern is not the same as yours.
Click to expand...
Click to collapse
I flash again AOSP 5.1.1 from JDC Team, on Aida 64 the gyroscope appear (uncalibrated sensor), I try bubble level and Gps tool box, none results.... The drift way is very slow, but I noticed for calibrate it, some experience dev, need build init.d script to fix it or give me patch to apply on it. AOSP 5.1.1 is better than Touchwiz, the games in general fly here.... And battery life is very good.
I seriously doubt an experienced dev is going to create an init.d script just for you, especially when you demand they make a patch for a problem that you seem to be the only one having.
For the record, I just downloaded GPS Status & Toolbox from the Play Store specifically so I could calibrate the sensors. No problems with calibration, and the calibration persists, as my tricorder app now shows the correct orientation for the compass when it didn't before. I don't know what else to tell you. It's working here without a problem, so if it's not working for you there's another issue.