Database Users

Camera Blur Gone - Simple Fix

By simply changing the brightness level to -2.0 you will no longer have a blur - it's like changing the ISO on a camera and the FPS will jump by over 50%. check it out in full here: http://www.fuzemobility.com/decrease-the-blur-of-your-camera-really/

bugsykoosh said:
By simply changing the brightness level to -2.0 you will no longer have a blur - it's like changing the ISO on a camera and the FPS will jump by over 50%. check it out in full here: http://www.fuzemobility.com/decrease-the-blur-of-your-camera-really/
Click to expand...
Click to collapse
Sounds excellent, will try this out!!
EDIT
I have tried this and can find no improvement whatsoever. As kkchan stated below, all I notice is the picture has become darker due to the decrease in brightness level. I have even tried this at -1.0, but still no improvement

Hi,
I tried, no improvement, sometime seem even worst because the photo become darker.

kkchan said:
Hi,
I tried, no improvement, sometime seem even worst because the photo become darker.
Click to expand...
Click to collapse
I did it myself on a Touch HD and went from +2 and changed it to -2 and it was a world of difference. At +2 any movement was a blur and at -2 I could move the camera and still get a clean shot

Fallen Spartan said:
Sounds excellent, will try this out!!
EDIT
I have tried this and can find no improvement whatsoever. As kkchan stated below, all I notice is the picture has become darker due to the decrease in brightness level. I have even tried this at -1.0, but still no improvement
Click to expand...
Click to collapse
In extreme light situtations (a bright day) there's almost no difference in speed but the HD never had a problem in very high light. The real impact is in moderate to low light. So far there are 2 comments at FuzeMobility both stating that it works effectively and I tested it last night on the HD and took an unusable camera and had something that could take a photo. Did you guys enable the FPS info to see if there was a change?

bugsykoosh said:
In extreme light situtations (a bright day) there's almost no difference in speed but the HD never had a problem in very high light. The real impact is in moderate to low light. So far there are 2 comments at FuzeMobility both stating that it works effectively and I tested it last night on the HD and took an unusable camera and had something that could take a photo. Did you guys enable the FPS info to see if there was a change?
Click to expand...
Click to collapse
I had already tried tweaking a number of settings for both the camera & video to get a better pic. This may have had some effect on these new settings. I will play around with it and see what I come up with

Fallen Spartan said:
I had already tried tweaking a number of settings for both the camera & video to get a better pic. This may have had some effect on these new settings. I will play around with it and see what I come up with
Click to expand...
Click to collapse
What settings if you don't mind? I'm always up for more tweaking I know about decreasing the delay times:
HKLM/Software/HTC/Camera/Captparam/ and set CaptureTimer = 0 and EnableCapKeyDelay = 0 and CapKeyDelayTime = 0
and changing the panaramic photo size...I hope you have a few more though

bugsykoosh said:
What settings if you don't mind? I'm always up for more tweaking I know about decreasing the delay times:
HKLM/Software/HTC/Camera/Captparam/ and set CaptureTimer = 0 and EnableCapKeyDelay = 0 and CapKeyDelayTime = 0
and changing the panaramic photo size...I hope you have a few more though
Click to expand...
Click to collapse
Basically I read through a lot of threads regarding enhancing camera and have changed numerous things including those mentioned by yourself, some I can't remember to be honest and those mentioned in the wiki listed below. Also using HD Tweak etc
Increase Quality of Photos
To increase the quality of photos, open the Camera, go to Settings, Advanced, then Image Properties. Increase Contrast to 5, Saturation to 5, and Sharpness to 4. Now you will have better definition and much more realistic colours. Also don't forget to choose Super Fine under Quality in Advanced Settings menu.
Reduce Blurriness in Photos
To focus better, have shutter set just to Touch. After you have touched you have the whole three seconds to steady your hand and take a non-blurry photo.
Activate Hidden Photo Modes
You can activate hidden photo modes using the 'HD Tweak' app. Make sure to leave the resolutions for these modes at 1 megapixel though or they may not work properly. For for the more advanced users, use the following reg entries:
To enable Burst mode
Mobile Device\HKLM\Software\HTC\Camera\P6
set "Enable" on "1"
To enable Sports mode:
Mobile Device\HKLM\Software\HTC\Camera\P8
set "Enable" on "1"
To enable Video Share mode:
Mobile Device\HKLM\Software\HTC\Camera\P9
set "Enable" on "1"
To enable GPS Photo mode:
Mobile Device\HKLM\Software\HTC\Camera\P10
set "Enable" on "1"
Get True 5 Mega pixel Resolution When Using Camera
To get 5MP instead of 4MP resolution when using your camera, you must switch off Widescreen mode in the 'Advanced' Menu.
Normal screen = 2592 x 1944 pixels = 5,038,848 pixels = 5MP
Widescreen = 2592 x 1552 pixels = 4,022,784 pixels = 4MP
Get Better Video Quality When Using Camera
Use MPEG format instead of H.263 for better quality video output. This option can be found by going to the Advanced Setting from the Video Settings menu. Once there, go to Capture Format and change format if necessary.
If I can think of any more I'll let you know.
These threads may help:
Best Camera Setting for Taking Pictures
Blackstone Camera 2009 (HTC) Discussion

Fallen Spartan said:
Basically I read through a lot of threads regarding enhancing camera and have changed numerous things including those mentioned by yourself, some I can't remember to be honest and those mentioned in the wiki listed below. Also using HD Tweak etc
Increase Quality of Photos
To increase the quality of photos, open the Camera, go to Settings, Advanced, then Image Properties. Increase Contrast to 5, Saturation to 5, and Sharpness to 4. Now you will have better definition and much more realistic colours. Also don't forget to choose Super Fine under Quality in Advanced Settings menu.
Reduce Blurriness in Photos
To focus better, have shutter set just to Touch. After you have touched you have the whole three seconds to steady your hand and take a non-blurry photo.
Activate Hidden Photo Modes
You can activate hidden photo modes using the 'HD Tweak' app. Make sure to leave the resolutions for these modes at 1 megapixel though or they may not work properly. For for the more advanced users, use the following reg entries:
To enable Burst mode
Mobile Device\HKLM\Software\HTC\Camera\P6
set "Enable" on "1"
To enable Sports mode:
Mobile Device\HKLM\Software\HTC\Camera\P8
set "Enable" on "1"
To enable Video Share mode:
Mobile Device\HKLM\Software\HTC\Camera\P9
set "Enable" on "1"
To enable GPS Photo mode:
Mobile Device\HKLM\Software\HTC\Camera\P10
set "Enable" on "1"
Get True 5 Mega pixel Resolution When Using Camera
To get 5MP instead of 4MP resolution when using your camera, you must switch off Widescreen mode in the 'Advanced' Menu.
Normal screen = 2592 x 1944 pixels = 5,038,848 pixels = 5MP
Widescreen = 2592 x 1552 pixels = 4,022,784 pixels = 4MP
Get Better Video Quality When Using Camera
Use MPEG format instead of H.263 for better quality video output. This option can be found by going to the Advanced Setting from the Video Settings menu. Once there, go to Capture Format and change format if necessary.
If I can think of any more I'll let you know.
These threads may help:
Best Camera Setting for Taking Pictures
Blackstone Camera 2009 (HTC) Discussion
Click to expand...
Click to collapse
Unfortunately I know about those Thank you though - I'm sure a lot of people will benefit from that list. The ability to do infinite zoom is still elusive as far as I know...

bugsykoosh said:
Unfortunately I know about those Thank you though - I'm sure a lot of people will benefit from that list. The ability to do infinite zoom is still elusive as far as I know...
Click to expand...
Click to collapse
More settings/tweaks included in those 2 threads I believe though

[CM7]KANG discussion

This is the place where you can post and talk about your own personal cm7 builds, aka KANGS, experimental ideas and such.
PURPOSE: keeping the main CM7 thread clean.
THIS

Subscribed although I can't build myself. This matter is too interesting not to follow. I think bk201 his posts are the ones that I pay most attention to and I hope he will not be discouraged by this 'ban' but will keep us informed here.
Taptalked u see
Taptalked u see

Zatta said:
Subscribed although I can't build myself. This matter is too interesting not to follow. I think bk201 his posts are the ones that I pay most attention to and I hope he will not be discouraged by this 'ban' but will keep us informed here.
Taptalked u see
Taptalked u see
Click to expand...
Click to collapse
yep, love those posts too

Zatta said:
Subscribed although I can't build myself. This matter is too interesting not to follow. I think bk201 his posts are the ones that I pay most attention to and I hope he will not be discouraged by this 'ban' but will keep us informed here.
Taptalked u see
Taptalked u see
Click to expand...
Click to collapse
Setting up a build environment isn't that hard. If you need help, please let me know.

siky_dude said:
This is the place where to talk about your own personal cm7 builds, aka KANGS.
PURPOSE: keeping the main CM7 thread clean.
THIS
Click to expand...
Click to collapse
sorry for all the trouble.
currently testing:
I426982b3, I16a40854, Idb544452
feedback: have to test this some more, but didn't work when i tried the first time. there could be a popup informing user that bootanim was imported sucessfully or not, also fps rate dropped quite a bit after 1 or 2 seconds previewing chosen bootanim. that worked, but when i rebooted bootanim was still the default. don't know if i did something wrong though.
If0476af0, If5485caf
feedback: no errors on output, but icon on statusbar doesn't show. profiles feature keeps working fine, with this on or off.
Idf1cb09f, I89bdbc11
feedback: working flawlessly. 3 or 4 seconds less on boot process.
I52fcd648
feedback: downloaded Third Blade from market (~49mb), no issues downloading or installing. internal/external sdcard unaffected. no more need for this maybe?
I4427e3f2
feedback: working without issues; from what i understand this a function that gets string lenght (for example from a user input, not so sure here); any way to get a more technical comparison? a math test to cpu perhaps?
I92569aa2
feedback: also working, and solved original issue.
Ic0b39c23
feedback: no compile errors, no issues until now, seamless.
Id3e68a75, I2e365a33
feedback: working; does what's described. will test further for conflict with HSPA setting introduced by pawitp.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I461e90ac, I70d846ab, I76632c87
feedback: working; need more time to check for improvements on battery runtime.

Very good work. Have you been commenting on gerrit also? That would useful for the peer reviewers.

jose.celestino said:
Very good work. Have you been commenting on gerrit also? That would useful for the peer reviewers.
Click to expand...
Click to collapse
I haven't, the devs said i shouldn't if i didn't have anything to contribute.
more in testing
I5cb28b08
feedback: no issues to report, seamless
Ic395fae3
feedback: fixes skewed preview on camera when launching it from lockscreen custom app starter, with auto-rotation/90º active.
I985c4573
feedback: looks good, seamless on the end user i guess
I923fa5aa
feedback: still working fine, that nice terminal
just saw this, will test later:
I7ccd5e2c

Jens1969 said:
Setting up a build environment isn't that hard. If you need help, please let me know.
Click to expand...
Click to collapse
Do you think we should get a little bit more constructive/extensive (based on the wiki, sure) on build tips? setting up the buildenv isn't hard at all (just bandwith/time consuming), but 'repo' cannot be trusted for anything else than 'repo sync', and git can be a bit overwhelming. I've been practicing, so i'm getting better at git, branching, merging and fixing conflicts when they occur.
and another one up for testing
I412f9bba - benchmark fans, let's go

For me the limit is my hardware. A notebook /w ubuntu (yeah!), but also 2 years old, 512 mb ram, 160 gb hd. Don't think that will do.
Taptalked u see

Zatta said:
For me the limit is my hardware. A notebook /w ubuntu (yeah!), but also 2 years old, 512 mb ram, 160 gb hd. Don't think that will do.
Taptalked u see
Click to expand...
Click to collapse
hmm, i used to build on a p4 with 2gb ram. linux holds its ground, it will not give up on you, even if you're browsing (don't watch flvs though ) or listen to music... i hope.
still, if you find something you want to see tested, write it down, someone will test it (if it doesn't get approved before that ) and share feedback.
---------- Post added at 10:06 PM ---------- Previous post was at 09:13 PM ----------
Received call, screen didn't wake up. pressed home once, no reaction, pressed power button twice, screen woke up and i was able to awnser the call.
http://pastebin.com/4PuAd31R
I/power ( 208): *** set_screen_state 0
D/SurfaceFlinger( 208): About to give-up screen, flinger = 0xeb108
D/KeyguardViewMediator( 208): wakeWhenReadyLocked(26)
I/power ( 208): *** set_screen_state 1
I/power ( 208): *** set_screen_state 1
Click to expand...
Click to collapse
i'm curious, what's KeyguardViewMediator?
quote from cm forums, user danielck78
Try this. Press on the sensor or somewhere near it. Try to press harder for about 2 seconds. Try if the screen turn back on.
Click to expand...
Click to collapse
edit: i'm with ring lockscreen. never happened before, but i've merged a couple of commits which are related to lockscreen stuff, note that i'm not saying that they are the cause. i'll try with vanilla kernel too (merged a couple of commits from zach 2.6.35.x towards battery runtime, although i don't think they're to blame since i had them for like 3 builds, that makes at least a week and a half using it)

bk201doesntexist said:
Do you think we should get a little bit more constructive/extensive (based on the wiki, sure) on build tips? setting up the buildenv isn't hard at all (just bandwith/time consuming), but 'repo' cannot be trusted for anything else than 'repo sync', and git can be a bit overwhelming.
Click to expand...
Click to collapse
Trying to get into CM7/SGS development, there seems no way around git. But git doesn't like me.
ATM I manage to 'sync repo' and cherry-pick commits. But get lost often. As you said: git is not easy.
So, I'd like this to be a place to talk about (maybe) upcoming changes and also to get some help with development related tasks.
On the long run, this could be a starting point to attract (or grow!) more SGS programmers.
I461e90ac: looks very promising. Switched to UMTS only and lost only 5% in two hour. Will see what I lose overnight.

bk201doesntexist said:
i'm curious, what's KeyguardViewMediator?
Click to expand...
Click to collapse
* Mediates requests related to the keyguard. This includes queries about the
* state of the keyguard, power management events that effect whether the keyguard
* should be shown or reset, callbacks to the phone window manager to notify
* it of when the keyguard is showing, and events from the keyguard view itself
* stating that the keyguard was succesfully unlocked.
At wakeWhenReadyLocked(26), the keyguard was notified that it may need to do something about a keypress, 26 is the keycode of the pressed key, KEYCODE_POWER = Power Key (http://developer.android.com/reference/android/view/KeyEvent.html).

jose.celestino said:
* Mediates requests related to the keyguard. This includes queries about the
* state of the keyguard, power management events that effect whether the keyguard
* should be shown or reset, callbacks to the phone window manager to notify
* it of when the keyguard is showing, and events from the keyguard view itself
* stating that the keyguard was succesfully unlocked.
At wakeWhenReadyLocked(26), the keyguard was notified that it may need to do something about a keypress, 26 is the keycode of the pressed key, KEYCODE_POWER = Power Key (http://developer.android.com/reference/android/view/KeyEvent.html).
Click to expand...
Click to collapse
thanks for the link (xda limit ) this whole section of the website looks like a nice place to learn.
anyways, another question while we follow the trail: at line 27 of the pastebin, set_screen_state 1 comes in, and this should have waken the screen, right?
as it didn't, then i pressed HOME, and WindowManager says there's a ringing incoming call already (because call Notification already has a fullScreenIntent right, that's why we can't leave the incoming call screen), so it can't pass that button press request further. i still don't get why power
set_screen_state 0 at line 43, without me pressing it, that's the thing.
edit: just now, phone was sleeping, and screen came up fine for a phone call. no issue. lol

Jens1969 said:
Trying to get into CM7/SGS development, there seems no way around git. But git doesn't like me.
ATM I manage to 'sync repo' and cherry-pick commits. But get lost often. As you said: git is not easy.
So, I'd like this to be a place to talk about (maybe) upcoming changes and also to get some help with development related tasks.
On the long run, this could be a starting point to attract (or grow!) more SGS programmers.
I461e90ac: looks very promising. Switched to UMTS only and lost only 5% in two hour. Will see what I lose overnight.
Click to expand...
Click to collapse
i'll try to get something going on the git side, although surely i need to improve as well. i now think cherry-picking/branches is easier than fixing conflicts. i'm managing myself through, you'll see, it's actually not that hard. it definately is easier for someone who knows how to code, but that's a given, i guess.
definately, i agree with you about the objective of this thread. i would add as well help improve users so that they can help themselves, maybe we'll turn into the devs of tomorrow (pretty utopic schedule that is, but still), maybe not, but we all learn something more out of it - knowledge has no place - while helping out the community, and making some more mistakes along the way.
I461e90ac looks promising indeed. i'll give one more cycle to it.
edit: i was bored so... in Ie259e6da, if we edit:
device/samsung/aries-common/AriesParts/res/values/arrays.xml to:
Code:
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<string-array name="backlight_timeout_entries">
<item>Off</item>
<item>Default (1.6 seconds)</item>
<item>2 seconds</item>
<item>5 seconds</item>
<item>10 seconds</item>
<item>15 seconds</item>
<item>30 seconds</item>
<item>Never</item>
</string-array>
<string-array name="backlight_timeout_entries_values" translatable="false">
<item>0</item>
<item>1600</item>
<item>2000</item>
<item>5000</item>
<item>10000</item>
<item>15000</item>
<item>30000</item>
<item>-1</item>
</string-array>
</resources>
would it be enough to turn off the leds entirely from AriesParts, while still having led notif, of course? or do we need to go kernel level, (i noticed drivers/input/keyboard/cypress-touchkey.c, like pawitp did here)?
i think only editing the xml doesn't do the trick like it should, does it? maybe if we changed this:
Code:
static void bl_set_timeout() {
if (bl_timeout > 0) {
mod_timer(&bl_timer, jiffies + msecs_to_jiffies(bl_timeout));
}
}
to
Code:
static void bl_set_timeout() {
if (bl_timeout ≥ 0) {
mod_timer(&bl_timer, jiffies + msecs_to_jiffies(bl_timeout));
}
}
no good? or would it still need something else? or is it completely way off and would make my phone melt
this doesn't look promising.. Void, seems to me that's the same as 'we don't need this'?
Code:
static void bl_off(struct work_struct *bl_off_work);
i think i will start doing some serious e-learning on coding.. once i get more "comfortable" at work and can relax a bit.

guys,i have been on cm7.1 from the day cm7.1 stable released and now Im on nightly 165,and i keep facing a problem (so do my 4friends)-the google framework service forcing problem
First i know a data wipe or wiping all the gapps and those apps that regard to account syncing ,but it sometimes work for a period(1day or less)and sometimes dun even works
can someone give me some helps ?
I'm on nightly 165 with stock kernel
Changed dpi with nitrality to 182dpi

leejack218 said:
guys,i have been on cm7.1 from the day cm7.1 stable released and now Im on nightly 165,and i keep facing a problem (so do my 4friends)-the google framework service forcing problem
First i know a data wipe or wiping all the gapps and those apps that regard to account syncing ,but it sometimes work for a period(1day or less)and sometimes dun even works
can someone give me some helps ?
I'm on nightly 165 with stock kernel
Changed dpi with nitrality to 182dpi
Click to expand...
Click to collapse
this is definitely the wrong thread for this. Answer in the q&a thread.
Edit: link to that is in my sig.
Taptalked u see

bk201doesntexist said:
edit: i was bored so... in Ie259e6da, if we edit:
device/samsung/aries-common/AriesParts/res/values/arrays.xml to:
Code:
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<string-array name="backlight_timeout_entries">
<item>Off</item>
<item>Default (1.6 seconds)</item>
<item>2 seconds</item>
<item>5 seconds</item>
<item>10 seconds</item>
<item>15 seconds</item>
<item>30 seconds</item>
<item>Never</item>
</string-array>
<string-array name="backlight_timeout_entries_values" translatable="false">
<item>0</item>
<item>1600</item>
<item>2000</item>
<item>5000</item>
<item>10000</item>
<item>15000</item>
<item>30000</item>
<item>-1</item>
</string-array>
</resources>
would it be enough to turn off the leds entirely from AriesParts, while still having led notif, of course?
Click to expand...
Click to collapse
No, that's the screen timeout.
or do we need to go kernel level, (i noticed drivers/input/keyboard/cypress-touchkey.c, like pawitp did here)?
Click to expand...
Click to collapse
You need this patch to get BACKLIGHT_TIMEOUT from userspace as it is hardcoded to 1600 (ms). Then you need another patch to set the value in CMParts or, in this case, AriesParts.
Don't know if 0 would turn it off though.
this doesn't look promising.. Void, seems to me that's the same as 'we don't need this'?
Code:
static void bl_off(struct work_struct *bl_off_work);
Click to expand...
Click to collapse
void means you don't care for the function return
EDIT: "Then you need another patch to set the value in CMParts", failed to see that that was the one you posted and included the arrays.xml. Disregard everything I said before that.

Yes if you edit that array, you will control the led backlight timer. Lowest you can go is 1. (0 is always on)
To test values do : echo 1 > /sys/class/misc/notification/bl_timeout
To turn it off however, some kernel "hacking" will be required

Oh, so that array is actually for the touchkeys backlight timeout. My bad.
And that's were it is read from userspace then, nice.

Daneshm90 said:
Yes if you edit that array, you will control the led backlight timer. Lowest you can go is 1. (0 is always on)
To test values do : echo 1 > /sys/class/misc/notification/bl_timeout
To turn it off however, some kernel "hacking" will be required
Click to expand...
Click to collapse
I'm confused. If 0 is always on, what's -1?
edit: Or did you mean -1 is always on?
edit2: (follow up on the next page) actually anything below 1 (since bl_timeout needs to be greater but not equal to 0) will make touchkey bl stay on forever.

Possible Fix For Touchscreen Issues/Misses (Updated 08/29)

SEE UPDATE BELOW
After doing some more digging on surfaceflinger, atd, and their related libs, I found some interesting entries in a "strings" analysis of libinputflinger.so. Loads of stuff on touch calibration. I noticed some repeated strings that looked like they're assigned to different properties. You can see this clearly by entering:
Code:
strings /system/lib/libinputflinger.so | grep -iE '(^touch\.|[ ][ ]touch\.)'| sed -e 's/^[ \t]*//' | sort -n | uniq
The terminal returns
Code:
touch.coverage.calibration
touch.coverage.calibration: box
touch.coverage.calibration: none
touch.deviceType
touch.distance.calibration
touch.distance.calibration: none
touch.distance.calibration: scaled
touch.distance.scale
touch.distance.scale: %0.3f
touch.gestureMode
touch.orientation.calibration
touch.orientation.calibration: interpolated
touch.orientation.calibration: none
touch.orientation.calibration: vector
touch.orientationAware
touch.pressure.calibration
touch.pressure.calibration: amplitude
touch.pressure.calibration: none
touch.pressure.calibration: physical
touch.pressure.scale
touch.pressure.scale: %0.3f
touch.size.bias
touch.size.bias: %0.3f
touch.size.calibration
touch.size.calibration: area
touch.size.calibration: box
touch.size.calibration: diameter
touch.size.calibration: geometric
touch.size.calibration: none
touch.size.isSummed
touch.size.isSummed: %s
touch.size.scale
touch.size.scale: %0.3f
touch.wake
I looked up some of strings on the net, and lo and behold, they're build.prop entries! You can see the props above that have different strings to assign to them. The ones with a "%0.3f" refer to a number value, and the one with "%s" is a boolean 0/1.
I've only done a little testing, but I found a baseline of improvement values to make our touch screens more responsive. Some of the properties I couldn't find info on, so I'm testing some values like touch.distance.scale. I feel like I have definitely noticed improvements though. I'm no longer so pissed off using my phone, and the frequency of misses overall seems significantly lower. It's acceptable now. Here's what I'm using now at the end of my build.prop:
Code:
##### touch ######
touch.deviceType=touchScreen
# (geometric, diameter, box, area)
touch.size.calibration=geometric
touch.size.scale=100
# (amplitude, physical, none)
touch.pressure.calibration=amplitude
touch.pressure.scale=0.1
touch.gestureMode=pointer
# (interpolated, vector, none)
touch.orientation.calibration=interpolated
# (box, none)
touch.coverage.calibration=box
For detailed information on these touch properties, read here(search for the property you're interested in; the page is pretty long). Some are self-explanatory and others we'll just need to test more. Check them out and see if any calibration values make a significant change. Just copy the above code and paste to the bottom of /system/build.prop with a nice file manager like Solid Explorer. Warning: Adding these entries in the build.prop will change the default touch properties. You can always change them back to stock by removing or commenting the entries from build.prop. I assume most values are aafe, but I can't be sure.
Also worth noting. I found some additional build.prop values to make Android snappier. The fling/swipe velocity make a big difference. Not sure what the others correlate to.
Code:
##### touch related #####
view.touch_slop=2
view.scroll_friction=1.5
view.minimum_fling_velocity=25
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.min_pointer_dur=8
windowsmgr.max_events_per_sec=200
EDIT: For detailed information on these touch properties, read here.
I'm gonna add some "profiles" of touch settings to use down here.
This one is for a Nexus 4 I believe. I'm trying it out now, and it seems pretty good. My goal is to emulate the touch experience I had with that phone.
Code:
##### touch ######
touch.deviceType=touchScreen
touch.orientationAware=1
# (geometric, diameter, box, area)
touch.size.calibration=diameter
touch.size.scale=10
touch.size.bias=0
touch.size.isSummed=0
# (amplitude, physical, none)
touch.pressure.calibration=amplitude
touch.pressure.scale=0.005
touch.gestureMode=pointer
# (interpolated, vector, none)
touch.orientation.calibration=none
UPDATE
Hey guys, so here's an update to what I've found out about the touch screen and its issues. I apologize for my low activity on xda. I've been real busy working on some linux projects.
First, in order for the touch.* settings to work, they need to be put in an .idc (input device configuration) file with the name of the device. For the G4, that is: /system/usr/idc/touch_dev.idc.
If you have another phone or want to check, you can get the name of your touch screen device with the terminal command:
Code:
for i in /dev/input/event*; do j="$(getevent -i $i | grep -i touch)"; j=${j#*name: }; [[ -z $j ]] || echo ${j//\"/}; done
Before you go try out the .idc file, I want to warn you that certain settings will disable the touch screen. If this happens, you'll need to use adb to delete or move /system/usr/idc/touch_dev.idc somewhere else so that it doesn't get loaded when the phone boots. These are some settings you must NOT change in the .idc file:
Code:
touch.deviceType = touchScreen
touch.coverage.calibration = box
These are the settings I'm currently using:
Code:
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.size.calibration = diameter
touch.size.scale = 1
touch.size.bias = 0
touch.size.isSummed = 0
touch.pressure.calibration = physical
touch.pressure.scale = 0.001
touch.orientation.calibration = none
touch.distance.calibration = none
touch.distance.scale = 0
touch.coverage.calibration = box
touch.gestureMode = spots
MultitouchSettleInterval = 1ms
MultitouchMinDistance = 1px
TapInterval = 1ms
TapSlop = 1px
I'm not sure if the Multitouch* and Tap* settings work or if adding more values from libinputflinger will work. There's little documentation on using settings that don't begin with "touch." You might have to do some experimentation and try other entries in the "strings /system/lib/libinputflinger.so" readout. I would also try using the first settings I posted if these don't seem to help.
Another thing I found out is that this phone performs better with low entropy. You can monitor your current entropy level in the terminal:
Code:
watch "cat /proc/sys/kernel/random/entropy_avail"
It's usually around 2000+ and peaks at 4096 with high activity which is where I think lag comes in. I found that lowering it to under 1000 average cut out the lag spikes I was getting:
Code:
echo 16 > /proc/sys/kernel/random/read_wakeup_threshold
echo 16 > /proc/sys/kernel/random/write_wakeup_threshold
I went ahead and added that to an init.d script. This doesn't have any side effects I've noticed besides possible increased battery life, since the "hwrng" process that generates entropy has no work to do. In case you don't have init.d, make sure busybox is installed, run this command in the terminal, and you'll have init.d startup:
Code:
mount -o remount,rw /system; echo "sleep 300 && run-parts /system/etc/init.d" >> /system/etc/init.qcom.post_boot.sh; mount -o remount,ro /system
One last thing to mention. The touch device has a little section in sysfs under: /sys/devices/virtual/input/lge_touch. There's some interesting information you can find there, values you can change, and tests you can run. Any file with a name ending in "test" can be run by opening the file, yes sysfs files are weird like this. All tests pass for me except "abs_test":
Code:
cat /sys/devices/virtual/input/lge_touch/abs_test
> ========RESULT=======
> Absolute Sensing Short Test : RESULT: Fail
> Absolute Sensing Open Test : RESULT: Fail
I haven't seen other people with or without touch screen issues run this test, so it may or may not be an indicator that something's wrong with the touch screen or its kernel-side drivers. By the way, this doesn't require superuser. You can check this on any device and even use a good text editor like QuickEdit to open the file and generate test results.
At this point, I'm fairly content with the new improvements I've made, but my best bet on a complete fix would be upgraded touch drivers. The "Advanced In-Cell Touch" device this phone uses is pretty new. There's a good chance this technology has drivers that don't have all the bugs worked out. This is something we'll have to wait on. On the other hand, if LGE handed over a bootloader unlock method and some source files, I'd be just fine with that too.

What "issues" is this attempting to fix

kyle1867 said:
What "issues" is this attempting to fix
Click to expand...
Click to collapse
Probably the horrible touch response many users experience.

Is this something that we can copy and paste into the end of the build prop, or is it replacing stuff that is already there?
Sent from my LG-H811 using XDA Free mobile app

Wow nice job man.
Is it possible to address the swipe registering as taps through this or do you think this will also address it?

Harmtan2 said:
Is this something that we can copy and paste into the end of the build prop, or is it replacing stuff that is already there?
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
You'll have to add almost all of them.

Yes bro am too facing the touch problem in my intex aqua star power. The problem is when we keep the finger the screen shakes and also in 100% of my usage 20% touch mismatches . On first i irritated and now i habituated with this touch. [emoji28]
Sent from my Aqua Star Power using Tapatalk

The build.prop edits seem to be making the difference. ?
Sent From My LG G4

Rydah805 said:
The build.prop edits seem to be making the difference. ?
Sent From My LG G4
Click to expand...
Click to collapse
would you say that double tap to wake is improved as well?

esmenikmatixx said:
would you say that double tap to wake is improved as well?
Click to expand...
Click to collapse
Hmm, you know what, it is.
Sent From My LG G4

esmenikmatixx said:
would you say that double tap to wake is improved as well?
Click to expand...
Click to collapse
I would say so I have all these except the new ones he posted an an script from another post an I do see some improvements defiantly double tap to wake

GUGUITOMTG4 said:
You'll have to add almost all of them.
Click to expand...
Click to collapse
Soooo... can you run through this with me? I'm not a novice but I'm trying to figure out how to add them? I can't simply text edit the build.prop on my phone or pull/push from my computer?

This post is the reason why I'm glad we now have root.

Akomack said:
Soooo... can you run through this with me? I'm not a novice but I'm trying to figure out how to add them? I can't simply text edit the build.prop on my phone or pull/push from my computer?
Click to expand...
Click to collapse
Yes, you can manually edit it and or push pull it, but sometimes it causes bootloop when edited as a plain text. I would suggest using a build prop editor app from Play Store (I use Build Prop Editor by JRummy. It's Also built in in Rom Toolbox). You will have to copy-paste line by line. I'm gonna try those settings, but in my case, my screen sometimes misses when the phone gets hot. I attribute my touchscreen issues to the Lag LG injected on thermal files.

GUGUITOMTG4 said:
Yes, you can manually edit it and or push pull it, but sometimes it causes bootloop when edited as a plain text. I would suggest using a build prop editor app from Play Store (I use Build Prop Editor by JRummy. It's Also built in in Rom Toolbox). You will have to copy-paste line by line. I'm gonna try those settings, but in my case, my screen sometimes misses when the phone gets hot. I attribute my touchscreen issues to the Lag LG injected on thermal files.
Click to expand...
Click to collapse
Do you have to be rooted to do that?

Hendrycks said:
Do you have to be rooted to do that?
Click to expand...
Click to collapse
Yes you do
Sent from my LG-H811 using Tapatalk

Hi,
yesterday I bought a G4 H815.
I have the following problem: If my phone is on the bed next to me, or lying on a table, the touchscreen response is terrible. If I'm holding it in my hand, there's no problem. If it's charging and so lying on the bed, there's no problem either.
I took a few photos with my Optimus Black, since I could't take any screenshots of the issue:
this is with my phone lying on the bed:
and here holding it in my hands, producing no problems at all.
what is this? It's bloody annonying and totally unacceptable from a phone of this level, And yes... I would use it without holding it, just placing it on my bed next to me, but you can see how it is performing like so...
is my display faulty, or what?

Thanks man.
It's indeed more responsive. Especially double tap to wake is working good now.

*justintime* said:
Thanks man.
It's indeed more responsive. Especially double tap to wake is working good now.
Click to expand...
Click to collapse
I didnt feel a difference can you post a screenshot of your buildprop? Thanks in advance
Maybe im doing it wrong
Sent from my LG-H811 using Tapatalk

Just edit with es file Explorer.
And get the build.prop in the system folder. Not the other one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

G4 Camera Mods FPS [MM]

FPS Mod - Get More FPs in video
To install
Copy file to
/system/vendor/lib/
Click to expand...
Click to collapse
Code:
permissions rw-r-r
V2 Changes
39 fps UHD Video
tested by @pikachukaki

every video i capture in my computer its said 29fps

This is not flashable zip you need to repleace file menualy

Does this work on Lollipop?

datvu said:
This is not flashable zip you need to repleace file menualy
Click to expand...
Click to collapse
yeah i replace the so lib file manually

pikachukaki said:
every video i capture in my computer its said 29fps
Click to expand...
Click to collapse
run
Code:
adb shell dumpsys media.camera
with your device connected and developer mode enabled.
Click to expand...
Click to collapse
theres some config file that has the fps defined maybe try change that i think it was the file changed in the 60fps mod for g4

defcomg said:
theres some config file that has the fps defined maybe try change that i think it was the file changed in the 60fps mod for g4
Click to expand...
Click to collapse
take it

pikachukaki said:
take it
Click to expand...
Click to collapse
in system/etc/camera_config.xml
look for
Code:
<item name="video_size_rear_supported">
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
</item>
change it to
Code:
<item name="video_size_rear_supported">
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
</item>
in /system/etc/media_profiles.xml
look for
Code:
minFrameRate="15" maxFrameRate="120"
change that to 240
in camera id 0 look for 1080 change frame to 90 | look 4kuhd change that to 60 or raise value by like 5 like say 35 fps 40 fps till it maxes out somewhere
if you open the lib with hex editor like hex workshop search for int16 value 6144 it will show all the resolutions
6144 is the Number of horizontal lines the number next to it is vertical the 4 bytes before it are active pixels w x h
Capture res example
HEX
Code:
C014 AC0B 0018 E00B 402E7021 0018BF1E 01000000 00000040 713DF041 01
aW aH W H Pixel Clock Output Clock Binning Min Fps Max Fps Sensor Mode
DEC
Code:
5312 2988 6144 3040 561000000 515840000 1 2 30.03 1
Pixel Clock = W * H * Max Fps
Output Clock When Not in HFR Mode = Pixel Clock it limits actual fps. When in HFR mode = Pixel Clock / 2
Sensor Mode 1 = Normal 2 = HFR 3 = HDR
G4 Video Res runs at Full sensor res @ 30 fps reducing aW aH W H to say 3840 2160 6144 2190 would let the G4 Gain more FPS in UHD Mode thats how i got 32fps UHD on OG SD800 i reduced the H value from 2219 to 2170.
so if you want to achieve 240fps without pushing device a aW/8 aH/8 W H/8 Max FPS * 8
this would give a guaranteed 240fps
Code:
664 373 6144 380 561000000 515840000 1 2 240.24 1
All that is needed is a camera 2 app that lets you set custom res and fps for video then you can play with these values
Output Clock is what limits the fps i dunno what the SD808 maxes out it could be higher than the default 515K
Hopefully the camera_config.xml mod method works for the stock camera

defcomg said:
in system/etc/camera_config.xml
look for
Code:
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
change it to
Code:
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
in /system/etc/media_profiles.xml
look for
Code:
minFrameRate="15" maxFrameRate="120"
change that to 240
in camera id 0 look for 1080 change frame to 90 | look 4kuhd change that to 60 or raise value by like 5 like say 35 fps 40 fps till it maxes out somewhere
if you open the lib with hex editor like hex workshop search for int16 value 6144 it will show all the resolutions
6144 is the Number of horizontal lines the number next to it is vertical the 4 bytes before it are active pixels w x h
Capture res example
HEX
Code:
C014 AC0B 0018 E00B 402E7021 0018BF1E 01000000 00000040 713DF041 01
aW aH W H Pixel Clock Output Clock Binning Min Fps Max Fps Sensor Mode
DEC
Code:
5312 2988 6144 3040 561000000 515840000 1 2 30.03 1
Pixel Clock = W * H * Max Fps
Output Clock When Not in HFR Mode = Pixel Clock it limits actual fps. When in HFR mode = Pixel Clock / 2
Sensor Mode 1 = Normal 2 = HFR 3 = HDR
G4 Video Res runs at Full sensor res @ 30 fps reducing aW aH W H to say 3840 2160 6144 2190 would let the G4 Gain more FPS in UHD Mode thats how i got 32fps UHD on OG SD800 i reduced the H value from 2219 to 2170.
so if you want to achieve 240fps without pushing device a aW/8 aH/8 W H/8 Max FPS * 8
this would give a guaranteed 240fps
Code:
664 373 6144 380 561000000 515840000 1 2 240.24 1
All that is needed is a camera 2 app that lets you set custom res and fps for video then you can play with these values
Output Clock is what limits the fps i dunno what the SD808 maxes out it could be higher than the default 515K
Hopefully the camera_config.xml mod method works for the stock camera
Click to expand...
Click to collapse
@defcomg I edit the two xml files now i will see what it can capture...but i dont have the knowlage to edit the so file...you seem to have it so edit it if you want and have the time and release a flashable zip to test it if you dont have the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Awsome Job! ant chance to get it for CM?

solokiller11 said:
Awsome Job! ant chance to get it for CM?
Click to expand...
Click to collapse
these are just test we need some G4 dev as i don't have a g4 to test

pikachukaki said:
@defcomg I edit the two xml files now i will see what it can capture...but i dont have the knowlage to edit the so file...you seem to have it so edit it if you want and have the time and release a flashable zip to test it if you dont have the device
Click to expand...
Click to collapse
might require apk mod or a camera app which lets you set fps i think L camera let you do that

defcomg said:
might require apk mod or a camera app which lets you set fps i think L camera let you do that
Click to expand...
Click to collapse
other fps mods edit the media_profiles.xml but i think if you want more fps than 60 and you edit the lib file you need to edit every file...tell me which files you need....

updated op

Im interested in testing this with my G4 but i am on LP 5.1 to get root without unlocking bootloader. I am still able to copy your file? or this file is different on LP and i need MM to test it?

Tomek33 said:
Im interested in testing this with my G4 but i am on LP 5.1 to get root without unlocking bootloader. I am still able to copy your file? or this file is different on LP and i need MM to test it?
Click to expand...
Click to collapse
i need libmmcamera_imx234.so from your rom then i can change the same values as on MM
also in theory if i kill UHD res i could make FHD run at 75 fps

defcomg said:
i need libmmcamera_imx234.so from your rom then i can change the same values as on MM
also in theory if i kill UHD res i could make FHD run at 75 fps
Click to expand...
Click to collapse
240 fps on HD resolution would be fantastic!!!

asce1992 said:
240 fps on HD resolution would be fantastic!!!
Click to expand...
Click to collapse
the 808 is unable to pull 240fps and yes the 5X is capable because it has to pull less Horizontal lines
Cap is 6.95 Gbps / 579,010,560 clock +/-
so
for 240 fps
12.92Gbps / 1,076,428,800 clock
so far ive seen g4 max out 124fps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 124.035 fps
Minimum frame rate : 107.143 fps
Maximum frame rate : 127.841 fps
Click to expand...
Click to collapse
from another imx234 device it has 240 fps 640x360

Can you try recording in 4096x2160 24fps?
Today I tried FilmicPro and it managed to record video in 4096x2160 although it was buggy.
I tried modding media_codecs.xml media_profiles.xml and camera_config.xml so that the stock camera app does it however once I start video recording it crashes.

pepo930 said:
Can you try recording in 4096x2160 24fps?
Today I tried FilmicPro and it managed to record video in 4096x2160 although it was buggy.
I tried modding media_codecs.xml media_profiles.xml and camera_config.xml so that the stock camera app does it however once I start video recording it crashes.
Click to expand...
Click to collapse
buggy?

Adb command to use the tele lens from 4x in the official Samsung camera app

Hi, we know the camera app won't use the 4x tele zoom until we zoom at 10x, even when lighting conditions are good enough and the zoom camera would give much better results (we know that from comparison with GCam).
While looking at the output of adb shell dumpsys media.camera, I noticed a suspicious samsung.android.scaler.zoomMapRatio variable with a value of 10.
With the command adb shell am start -a android.media.action.IMAGE_CAPTURE --ei samsung.android.scaler.zoomMapRatio 0 I can start the camera app and force this variable to zero... And suddenly the app switches between the main and the zoom cameras between 4x and 5x (depending on your lighting conditions) !
Now I need to find a way to start the camera on the phone with this command line - the setting is lost when closing the app.
Video demonstation - I run the adb command at 5s:

Please be aware that the Themes/Apps section is ONLY for releasing themes and apps.
Discussions like this go in the General section.
Thread moved.

V0latyle said:
Please be aware that the Themes/Apps section is ONLY for releasing themes and apps.
Discussions like this go in the General section.
Thread moved.
Click to expand...
Click to collapse
My bad, thx for the cleanup

I'm not sure what's the best way to launch the camera while forcing this setting...
I can write a launcher app, but the following code does work except we only get to take a photo - we cannot change mode (photo/video/portrait/etc.)
Code:
val takePictureIntent = Intent1(MediaStore.ACTION_IMAGE_CAPTURE)
takePictureIntent.putExtra("samsung.android.scaler.zoomMapRatio", 0) // <== Magic !
try {
startActivityForResult(takePictureIntent, pic_id);
} catch (e: Exception) {
// display error state to the user
}
The result in video: