Database Info

[REQ] Adjusted autobrightness app/hack

Could someone write either
1) Autobrightness adjuster (to set which values autobrightness uses),
or
2) Make a modified autobrightness file with the following values,
Sensor = Brightness
10 = 50
160 = 60
225 = 70
320 = 80
640 = 115
1280 = 145
2600 = 185
10240 = 255
Thanks.
P.S. This is for the latest OTA or, preferably, for myn rls2 rom.

Anybody?
----------

[Q] glReadPixels() Problem in Android to reconstruct the frame

I am working on a project on Augmented Reality with Android. The code captures the camera video, finds the marker and displays a cube on top of it. After this a motion vector (in the form of pixels moved in the x and y direction) is found. What I need to do is read the pixels from the GL layer and draw them again after moving them by the distance specified by the motion vector.
The GL layer is specified using the GLSurfaceView class which is a transparent layer. The problem I am facing is that when I use glReadPixels() to read the pixels and convert it into a 480x800 array (nexus one screen resolution), I get 3 different portions of the cube instead of one.
I intend to move the pixels by the motion vector after this and use glDrawPixels() to put the pixels back into the frame buffer
Please help me with the interpretation of the same. Is there something I am missing while using glReadPixels and also if there is some other function that will help me achieve the same. I was thinking of using glBlitFrameBuffer() but this is not supported by the android GL10 class.
I have attached the part of the code where I am reading the pixels and changing them to a 2D matrix along with the image of the pixels I reconstructed using MatLab.
Any help will be greatly appreciated.
Code:
gl.glPixelStorei(GL10.GL_PACK_ALIGNMENT, 1);
IntBuffer pixels = IntBuffer.allocate(384000);
gl.glReadPixels(0, 0, 800, 480, GL10.GL_RGBA, GL10.GL_UNSIGNED_BYTE ,pixels);
File f = new File ("./mnt/sdcard/Sahiba_PixelData_" + flag + ".txt");
if(!f.exists())
f.createNewFile();
FileWriter fw = new FileWriter(f);
int pixelsArr [][] = new int [480][800];
//int temp[] = pixels.array();
int n=0;
for(int i=0; i<480; i++){
for(int j=0; j<800; j++){
pixelsArr[i][j] = pixels.get(n);
//temp[n + pixels.arrayOffset()];
fw.write(pixelsArr[i][j] + " ");
//fw.write(pixels.get(n) + " ");
n++;
}
//fw.write("\n");
}
Log.i("GLLayer", "Pixels reading and storing finished !!!");
}catch(Exception e){
Log.i("GLLayer","Exception = " +e);
}

Tablet Mode For Sensation?

I would really love to see this on our phones:
http://forum.xda-developers.com/showthread.php?t=1543892
is it possible with our AOKP and CM9 builds? can a Dev please make this possible? as i think the size of our screen can really work this one out!
what do you think...

wow no one seems to care about this one....?

Looks like its just changing the DPI to one that is recognized as a tablet. Seems it's 129 for the GNex... he posted something showing a formula for finding the "magic number" for other devices.
From his post:
Code:
int shortSizeDp = shortSize * DisplayMetrics.DENSITY_DEFAULT / DisplayMetrics.DENSITY_DEVICE;
mStatusBarCanHide = shortSizeDp < 600;
full description here: http://baroqueworksdev.blogspot.com/...ice-cream.html
nexus has a width of 720 and a density of 320. shortSizeDp = 720 * 160 / 320 = 360. lower than 600, phone mode.
now put the dpi to magic number 192. shortSizeDp = 720 * 160 / 192 = 600. tadaaa, tablet mode.
Click to expand...
Click to collapse
Edit: It's also using a modded nova launcher. Not sure, however, I don't see why the launcher wouldn't work for us.
In fact, I just spent a little more time looking through this and I think it will work close to 100% with CM9 or AOKP roms. Hmmmm, just gotta find out the right DPI. (I haven't bothered, busy at work.)

Looking at DisplayMetrics:http://developer.android.com/reference/android/util/DisplayMetrics.html
There are a few preset densities which may interest us:
DENSITY_DEFAULT = 160
DENSITY_HIGH = 240
DENSITY_LOW = 120
DENSITY_MEDIUM = 160
Assuming that the above values holds true to the Sensation, then the following would give a 600 output:
DENSITY_DEFAULT = 160 (540 * 160 / 144 = 600)
DENSITY_HIGH = 240 (540 * 240 / 216 = 600)
DENSITY_LOW = 120 (540 * 120 / 108 = 600)
DENSITY_MEDIUM = 160 (540 * 160 / 144 = 600)
Still checking it out!
EDIT: Additional info - DENSITY_DEFAULT is directly linked to DENSITY_MEDIUM (DENSITY_DEFAULT = DENSITY_MEDIUM) so that explains why changes to DENSITY_MEDIUM affect the OS system wide (Not sure if this is the case in all ROMs).
Still checking, but bed time for me!!!.........

Seems we also need a modified services.jar
There is some info here: http://forum.xda-developers.com/showthread.php?t=1467051
Thread here for AOKP B33: http://rootzwiki.com/topic/23418-mod-tabletui-for-240-dpi-legacy-devices-aokp-b32b33/
Instructions state: Set density to 128 MAX & Tablet mode will be automatically activated However, since our Sensations have a screen width of 540, not 480 as most legacy devices, we may still need to find that "Magic Number"
Haven't tried it as i'm not running an AOKP based ROM but we need to know what to change in services.jar and then this should be able to be implimented in all ROMs!
Hope this helps
EDIT: The services.jar above uses the following formula: (480 * 160 / 128 = 600)
We should be able to do it using (540 * 160 / 144 = 600) 144 MAX - However, it wont hurt to try 128 since our device has a default density of 240?!
Also, don't forget to set your Font size to huge (or large) in ROM Control.

I have created a flashable zip for AOKP B33/34 which includes a Patched Launcher, Phone, Market & services.jar.
This should work on all AOKP ROMs!
This should also parse the build.prop and adjust your LCD Density to 128.
Also, don't forget to set your Font size to huge (or large) in ROM Control prior to flashing this.
I haven't tested this - I have created it blind so if you are going to try it then please make a nandroid backup first!!!
Should you try it, then Please leave feedback but don't get upset if it doesn't work for you - If it doesn't work then just restore your nandroid backup!
I hope this is of some use to someone
BTW: Flash using recovery!

[TEST] Possible phantom touches fix

Right now i couldn't say for sure it's working or not, but for couple of days i didn't face any phantom touches. I wanna share the idea to test it.
There's things that's need to be done:
1. Open "/system/build.prop" with editor ( root )
2. Add those lines ( paste )
touch.size.calibration=geometric
touch.size.scale=100
touch.pressure.calibration=amplitude
touch.pressure.scale=0.1
3. Save & Reboot
If some one else is has that issue, test it.

It's not working for me...

Forget to mentioned that screen sensitive reduced in system to 10 maybe it's matter
Sent from my GT-I9103 using xda premium

hey i have a new display with a major problem of randoom phantom touches i will test ur solution until tomorow and report if it works
btw i cant say what display it is it was a friend of mine who has changed the display maybe "asi" can tell me wich one it is
but thx for ur research
EDIT:
as for now the "phatches" (phantom touches) are gone with ur first config will test the second from now on
EDIT 2:
ive tested the second config and must say it runs a bit smoother than the first one and for my display i can say when u look a bit from the side i can see small squares a few mm in size and dont forget to remind the people who want to test this mod that they should check the file permission if it is 644
EDIT 3:
now i can say the phatches are gone on my phone i got none since yesterday and the second conf is truely a bit smoother thx for that maybe that work on other phones too if they have probs with phatches on an new screen
Gesendet von meinem GT-I9103 mit Tapatalk 2

Please test that config too. And i know that it's hw related, it's wouldn't be fixed fully. Just make it's more comfortable.
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.size.calibration = area
touch.size.scale = 43
touch.size.bias = 0
touch.size.isSummed = 0
touch.pressure.calibration = amplitude
touch.pressure.scale = 0.0125
touch.orientation.calibration = none
Sent from my GT-I9103 using xda premium

If u provide a flashable zip, it ll be easier n helpful
Sent from my GT-I9103 using Tapatalk 2

It is possible to fix my softkeys back and menu keys working automatically wihtout any touch ...from this coding???
Sent from my GT-I9103 using xda app-developers app

sacfire said:
It is possible to fix my softkeys back and menu keys working automatically wihtout any touch ...from this coding???
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
You should try for yourself
Sent from my GT-I9103 using xda premium

These settings should be input device-specific and should go into one of the idc files in '/system/usr/idc/'. What files are in those folder? Could you send me the list? Is there any sec_touchscreen.idc? What is the output of 'getevent -p' in shell?

the list of system/usr/idc is:
qwerty.idc
qwerty2.idc
none more...
output of getevent -p
add device 1: /dev/input/event5
name: "compass_sensor"
events:
REL (0002): 0000 0001 0002 0003 0004 0005 0006 0007
0008 0009
input props:
<none>
add device 2: /dev/input/event3
name: "mpu-accel"
events:
REL (0002): 0000 0001 0002
input props:
<none>
add device 3: /dev/input/event2
name: "light_sensor"
events:
REL (0002): 0009
input props:
<none>
add device 4: /dev/input/event1
name: "proximity_sensor"
events:
ABS (0003): 0019 : value 1, min 0, max 1, fuzz 0, flat 0, resolution 0
input props:
<none>
add device 5: /dev/input/event4
name: "sec_key"
events:
KEY (0001): 0066 0072 0073 0074 00d4
input props:
<none>
add device 6: /dev/input/event0
name: "sec_touchscreen"
events:
KEY (0001): 008b 009e
ABS (0003): 002f : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
0030 : value 0, min 0, max 30, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
003a : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
LED (0011): 0008
input props:
INPUT_PROP_DIRECT
Gesendet von meinem GT-I9103 mit Tapatalk 2

What is it ?
Sent from my GT-I9103 using xda app-developers app
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
What is file permition ? How to do ?
Sent from my GT-I9103 using xda app-developers app

Any updates?
Sent from my GT-I9103 using Tapatalk 2

Digma Plane 7594 3G stretched image problem

On my Digma Plane 7594 3G tablet I have a problem with stretched (or compressed, depending on screen orientation) image.
"dumpsys display | grep DisplayInfo" (adb) output:
Code:
mDisplayInfos=
PhysicalDisplayInfo{600 x 1024, 60.0024 fps, density 1.33125, 426.386 x 149.411 dpi, secure true, appVsyncOffset 1000000, bufferDeadline 16666000}
mBaseDisplayInfo=DisplayInfo{"Встроенный экран", uniqueId "local:0", app 600 x 1024, real 600 x 1024, largest app 600 x 1024, smallest app 600 x 1024, mode 1, defaultMode 1, modes [{id=1, width=600, height=1024, fps=60.0024}], colorMode 0, supportedColorModes [], hdrCapabilities [email protected], rotation 0, density 213 (426.386 x 149.411) dpi, layerStack 0, appVsyncOff 1000000, presDeadline 16666000, type BUILT_IN, state OFF, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, removeMode 0}
mOverrideDisplayInfo=DisplayInfo{"Встроенный экран", uniqueId "local:0", app 600 x 960, real 600 x 1024, largest app 960 x 928, smallest app 600 x 568, mode 1, defaultMode 1, modes [{id=1, width=600, height=1024, fps=60.0024}], colorMode 0, supportedColorModes [], hdrCapabilities [email protected], rotation 0, density 213 (426.386 x 149.411) dpi, layerStack 0, appVsyncOff 1000000, presDeadline 16666000, type BUILT_IN, state ON, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, removeMode 0}
I guess there is a problem with "app 600 x 960, real 600 x 1024" (in mOverrideDisplayInfo).
Is it possible to change "app" values to math "real" values (if that's the problem)?