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?
----------
Hello everybody, I have YeahPad A13 (All Winner A13, 1.0GHz, Cortex-A8; GPU: Mali) after hours of searching found suitable rom, becouse other for this model deosn't event boot up, on other touch screen isn't working and display positioning is correct. Found 2 Roms with working touch screen on both display is moved by about 1cm from left, touch screen is in right position.
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
[lcd0_para]
lcd_used = 1
lcd_x = 800
lcd_y = 480
lcd_dclk_freq = 33
lcd_pwm_not_used = 0
lcd_pwm_ch = 0
lcd_pwm_freq = 18000
lcd_pwm_pol = 1
lcd_if = 0
or some display drivers
[ctp_para1]
ctp_used = 1
ctp_name = "Gt811-TS",
ctp_twi_id = 1
ctp_twi_addr = 0x5d
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0
ctp_revert_y_flag = 1
ctp_exchange_x_y_flag = 1
ctp_int_port = portG11<6><default>
ctp_wakeup = portB03<1><default><default><1>
ctp_reset = portB03<1><default><default><1>
;ctp_io_port = portG11<6><default>
and so on
Click to expand...
Click to collapse
I would glad any help
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
[lcd0_para]
lcd_used = 1
lcd_x = 800
lcd_y = 480
lcd_dclk_freq = 33
lcd_pwm_not_used = 0
lcd_pwm_ch = 0
lcd_pwm_freq = 18000
lcd_pwm_pol = 1
lcd_if = 0
or some display drivers
[ctp_para1]
ctp_used = 1
ctp_name = "Gt811-TS",
ctp_twi_id = 1
ctp_twi_addr = 0x5d
ctp_screen_max_x = 800
ctp_screen_max_y = 480
ctp_revert_x_flag = 0
ctp_revert_y_flag = 1
ctp_exchange_x_y_flag = 1
ctp_int_port = portG11<6><default>
ctp_wakeup = portB03<1><default><default><1>
ctp_reset = portB03<1><default><default><1>
;ctp_io_port = portG11<6><default>
and so on
Click to expand...
Click to collapse
I would glad any help
Bump* Added video if it would help
Pihas said:
Hello everybody, I have YeahPad A13 (All Winner A13, 1.0GHz, Cortex-A8; GPU: Mali) after hours of searching found suitable rom, becouse other for this model deosn't event boot up, on other touch screen isn't working and display positioning is correct. Found 2 Roms with working touch screen on both display is moved by about 1cm from left, touch screen is in right position.
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
I would glad any help
Is it possible to move display by 1cm back?
Extracted IMG file and there are many settings for Display and it driver, maybe any body knows what to look for?
COMMON _SYS_CONFIG100000:
I would glad any help
Click to expand...
Click to collapse
the same thing with my windad 7 plus, i guess that the issue can be fixed if you change lcd_x = 800 for lcd_x = 752, actually i dont know how extract and repack img from manufacturers but if this works it will be helpfull if you can do this for me for my enjoy7+ tablet on this rom cm-10-20121023-UNOFFICIAL-rk2918.zip or on the original firm http://www.msi.com/service/download/firmware-18964.html
actually i dont know how it works
i hope this can be helpfull for you
thanks
Several weeks ago I installed Tubuntu on my TF101 (Thanks x3maniak, lilstevie and other guys for fantastic work)
But I was in want of F1-F12 function and Delete keys on dock-kbr.
I solved that with xmodmap
Step 1: dump current keymod map table to .Xmodmap file in user directory
Code:
$ xmodmap -pke > /home/user/.Xmodmap
Step 2: edit .Xmodmap
open in your favorite text editor
And change keycode 246 stroke to "keycode 246 = F1 F1 F1 F1 F1 F1 XF86Switch_VT_1 F1"
keycode 245 stroke to "keycode 245 = F2 F2 F2 F2 F2 F2 XF86Switch_VT_2 F2"
For other F-keys you will edit these strokes on given example:
F3 = keycode 68
F4 = keycode 224, keycode 232, keycode 237
F5 = keycode 225, keycode 233, keycode 238
F6 = keycode 69
F7 = keycode 220
F8 = keycode 158
F9 = keycode 70
F10 = keycode 173
F11 = keycode 172
F12 = keycode 171
For Delete I used 'Lock' btn and remapped "keycode 150 = Delete NoSymbol Delete"
Two words about F4, F5. The Brightness Up and Down keys didn't give results in 'xev' program and I changed all Brightness related keys in the file.
Step 3: reboot
It's strange, but xmodmap ~/.Xmodmap didn't affect on keymod table
Example file in attachment, but It was made for Russian (Cyrillic) -English kbd layouts
The following code, is a simple example of programmatically "WITHOUT XML" translate animation, that works perfect on all versión bellow Android 4.4.2, but does nothing on Android 4.4.2. It's really making me crazy!
Any ideas why?
Tested and working OK on: EMULATOR AVD with 4.1.2 (API 16), EMULATOR AVD with 4.2.2 (API 17), EMULATOR AVD with 4.3.1 (API 18), Galaxy Tab 3 (4.1.2), Surprice, surprice.....works on my Galaxy NOTE with Omnirom 4.4.4
Not Working on: EMULATOR AVD with 4.4.2 (API 19), Galaxy S4 (4.4.2), Galaxy Note 3 (4.4.2)
Code:
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
int myWidth = 1280;
int myHeight = 800;
requestWindowFeature(Window.FEATURE_NO_TITLE);
getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN, WindowManager.LayoutParams.FLAG_FULLSCREEN);
boolean isPortrait = getResources().getConfiguration().orientation == Configuration.ORIENTATION_PORTRAIT;
int frameBufferWidth = isPortrait ? myHeight : myWidth;
int frameBufferHeight = isPortrait ? myWidth : myHeight;
Bitmap frameBuffer = Bitmap.createBitmap(frameBufferWidth, frameBufferHeight, Config.RGB_565);
graphics = new AndroidGraphics(getAssets(), frameBuffer);
fl = new FrameLayout(this);
ImageView mons= new ImageView(this);
mons.setImageBitmap(graphics.newImage("mons/mons01.png", ImageFormat.ARGB8888).getBitmap());
mons.setX(400);
mons.setY(200);
TranslateAnimation aniTrans = new TranslateAnimation(0, 0, 0, -200);
aniTrans.setDuration(5000);
mons.setAnimation(aniTrans);
FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.WRAP_CONTENT, FrameLayout.LayoutParams.WRAP_CONTENT);
fl.addView(mons, params);
FrameLayout.LayoutParams flp = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.MATCH_PARENT, FrameLayout.LayoutParams.MATCH_PARENT);
this.setContentView(fl, flp);
mons.startAnimation(aniTrans);
aniTrans.startNow();
}
Issue Found!
HAVE FOUND THE PROBLEM, but NEED HELP TO SOLVED IT!
(NOTE: This only occurs in full java code. It doesn’t happened using XML file, what is not the case)
Now I should call this topic like:
ANDROID 4.4.2 CREATES A BLACK MASK OUTSIDE VIEW OBJECT BOUNDARY, ONLY DURING FULL JAVA CODE ANIMATIONS?
Why?:
Take a look to this new example code:
Code:
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
common = new Common(this, this);
FrameLayout.LayoutParams framelayoutparameter = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.MATCH_PARENT, FrameLayout.LayoutParams.MATCH_PARENT);
/* I think that this is the line code (imageviewparamenter) were Android 4.4.2 FAILS during animation.*/
LayoutParams imageviewparamenter = new LayoutParams(LayoutParams.WRAP_CONTENT, LayoutParams.WRAP_CONTENT);
/* No matter the size of the screen, Android 4.4.2 creates a black hole outside the image size,
* just during animation (see attached picture). Thats why animation dont show up, if the
* initial position (setX or setY) of the image, is outside the image boundary.*/
fl = new FrameLayout(this);
ImageView iv = new ImageView(this);
/* Image is located in the ASSET and is 100x100 pixels (non dpi dependable)
* "common" method use AssetManager to read the image file */
iv.setImageBitmap(common.newImage("iv_image.png", ImageFormat.RGB565).getBitmap());
iv.setX(50); // position show in the example
iv.setY(0);
fl.addView(iv, imageviewparamenter);
this.setContentView(fl, framelayoutparameter);
AlphaAnimation animation = new AlphaAnimation(0,1);
animation.setDuration(5000);
animation.setAnimationListener(this);
/* Also, "setAnimation(animation)" must be present, in order that
* Android 4.4.2 animates without skipping frames*/
iv.setAnimation(animation);
iv.startAnimation(animation);
}
Create a frame layout with a ImageView and alpha animation using pure java code. During animation, Android 4.4.2 (API19) is creating a black mask outside the ImageView size boundary, starting at x/y coordinates (0 + imageWidth / 0 + imageHeight), so if you initially place the image outside that coordinate, you don’t see any animation, just the original image at the end of the animation....
To recreate the issue, i have place the image in x = 50 . You would see that the half right side of the image is BLACK during Android 4.4.2 animation. You can recreate using emulator with any size of screen setup that you prefer. Using API 16,17,18, have no problem, but using API19, the black mask will make you crazy!
NOW, ANY IDEAS? or is a big bug on Android 4.4.2? or I just don’t see it?
Anyone?
SOLVED
! SOLVED !
For some reason, API19 programmatically pure java animations doesnt play very well with absolut settings, like setX() or setY(). Experts may take a look on this. API19 preffers to work with margins on the layout parameter side.
The following procedure, apply's to android 4.4.2. Of cource, it works on the others versions down and up, but you must change your way of thinking. You must place a imagen programmatically using layout parameters, so change:
Code:
iv.setX(50);
iv.setY(0);
to
Code:
lparam.setMargins(50, 0, 0, 0);
iv.setLayoutParams(lparam);
iv.requestLayout();
You must call "requestLayout()" to ensure that the new changes on the layout, will be commited when adding the view to the parent (fl).
Finnally, by mistake, I use "LayoutParams" instead of "FrameLayout.LayoutParams". This nothing have to do with the issue and was not affecting it, but is the correct way to define it, so change:
Code:
LayoutParams lparam = new LayoutParams(LayoutParams.WRAP_CONTENT, LayoutParams.WRAP_CONTENT);
to
Code:
FrameLayout.LayoutParams lparam = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.WRAP_CONTENT, FrameLayout.LayoutParams.WRAP_CONTENT);
The complete working code for any API is:
Code:
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Common common = new Common(this, this);
FrameLayout fl = new FrameLayout(this);
ImageView iv = new ImageView(this);
FrameLayout.LayoutParams flparam = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.MATCH_PARENT, FrameLayout.LayoutParams.MATCH_PARENT);
FrameLayout.LayoutParams lparam = new FrameLayout.LayoutParams(FrameLayout.LayoutParams.WRAP_CONTENT, FrameLayout.LayoutParams.WRAP_CONTENT);
iv.setImageBitmap(common.newImage("100x100.png", ImageFormat.RGB565).getBitmap());
lparam.setMargins(50, 0, 0, 0);
iv.setLayoutParams(lparam);
iv.requestLayout();
fl.addView(iv);
this.setContentView(fl, flparam);
AlphaAnimation animation = new AlphaAnimation(0, 1);
animation.setDuration(3000);
iv.setAnimation(animation);
iv.startAnimation(animation);
}
Anyone using KCAL with whatever kernel, what are your preferences on the RGB sliders, saturation, contrast, etc. I'm curious as to what people love.
My settings using EXKM:
- R,G, and B: All set to 256
- Saturation: 46
- Value: 128
- Contrast: 128
- Hue: 0
TacoTuco said:
Anyone using KCAL with whatever kernel, what are your preferences on the RGB sliders, saturation, contrast, etc. I'm curious as to what people love.
My settings using EXKM:
- R,G, and B: All set to 256
- Saturation: 46
- Value: 128
- Contrast: 128
- Hue: 0
Click to expand...
Click to collapse
Currently using:
R: 253
G: 247
B: 256
Saturation: 43
Value: 130
Contrast: 133
Bit more vibrant than stock while keeping the whites, white.