Originally Posted by Sneakyghost

Hey guys, what's the reason i am not getting a reply to my question regarding the colorspace issue with the newer htc kernels in recoveries?
I tried to explain it 6 days ago here and didn't get any answer since, not even a "we don't know" or anything...

I'd really like to be answered, as i currently haven't really gotten an idea where to go with this issue. The colorshift does annoy quite a few users by now and we have to work around it by using older recoveries over at the Ville forum, which is kind of, well, not as good as it could be.
I was really hoping to get an idea here how to proceed and if Amarullz could maybe include another ini_set("force_colorspace","????") that would be about perfect.

Thanks for your attention.

Think you're gonna have to wait till amarullz announces the new aroma core/system he's working on for a fix to this issue. It a limitation of the current implementation of the binary. It's explained somewhere in this thread better than I can.

Sent from my SC-02E using Tapatalk 4 Beta

Originally Posted by Sneakyghost

Hey guys, what's the reason i am not getting a reply to my question regarding the colorspace issue with the newer htc kernels in recoveries?
I tried to explain it 6 days ago here and didn't get any answer since, not even a "we don't know" or anything...

I'd really like to be answered, as i currently haven't really gotten an idea where to go with this issue. The colorshift does annoy quite a few users by now and we have to work around it by using older recoveries over at the Ville forum, which is kind of, well, not as good as it could be.
I was really hoping to get an idea here how to proceed and if Amarullz could maybe include another ini_set("force_colorspace","????") that would be about perfect.

Thanks for your attention.

I do not have time lately to help
Found these while searching

Rendering Colors Properly in Aroma
http://forum.xda-developers.com/show...73&postcount=4

https://github.com/MiCode/miui_recov...er/device.conf

#ini_set("force_colorspace", "gbra"); //bule
ini_set("force_colorspace", "grba");
#ini_set("force_colorspace", "grba"); //yellow select
#ini_set("force_colorspace", "argb");//yellow background
#ini_set("force_colorspace", "brga"); //blue select

http://mobile.error-exception.org/ar...3A+Open+Source

CONFIGURATION FUNCTIONS  setcolor   Descriptions:   Set AROMA Installer Color Scheme. It can also defined in themes with theme.prop file 
  Sintax:      void setcolor(colorname, hexcolor); 
  Parameters:colorname - Name of color to be set. colorname with "_g" for gradient color.winbg, winbg_g 
  : Main/Top Most Window Backgroud winfg : Main/Top Most Window Text Foreground winfg_gray 
  : Main/Top Most Window Gray Text Foreground dialogbg, dialogbg_g 
  : Popup Window Backgroud (Alert, Confirm, About) dialogfg 
  : Popup Window Text Foreground textbg, textbg_g 
  : Textbox, Checkbox, and any scrollable UI Background textfg 
  : Textbox, Checkbox, and any scrollable UI Text Foreground textfg_gray 
  : Gray Text ( on Optionbox/Checkbox Item Description ) controlbg, controlbg_g 
  : Control / Button / Checkbox border - Background Color controlfg 
  : Button Text Color selectbg, selectbg_g 
  : Selected Element Background ( Pushed/focused Button/items, etc ) selectfg 
  : Selected Element Text/Foreground Color titlebg, titlebg_g 
  : Window Title Background titlefg 
  : Window Title Text Foreground Color navbg, navbg_g 
  : Bottom Bar (Navigation Bar) Background. Next-Previous Area scrollbar 
  : Scrollbar indicator color border, border_g : Common Border Color progressglow 
  : Progress Animation Color  hexcolor - Hexadecimal Color in RGB. it support 3 and 6 characters hexadecimal started with #. example: "#a8e" or "#ff5599".  Return Value: none   Examples:   ini_set   Descriptions:   Sets the value of a AROMA Installer configuration option   Sintax:      void setcolor(configname, newvalue);      Parameters:configname - Configuration name to be set.roundsize 
  : Set Corner size of rounded rectangle for common controls (default:"3") button_roundsize: Set Corner size of rounded rectangle for button controls (default:"2") window_roundsize : Set Corner size of rounded rectangle for main window (default:"4") transition_frame 
  : Set number of frames for transition (default:"5") text_ok 
  : Set text for common OK text (default:"OK") text_next 
  : Set text for wizard next button (default:"Next >") text_back 
  : Set text for wizard back button (default:"< Back") text_yes 
  : Set text for default yes button (default:"Yes") text_no 
  : Set text for default no button (default:"No") text_about 
  : Set text for About menu (default:"About & Informations") text_calibrating 
  : Set text for Calibration Menu (default:"Calibrating Tools") text_quit 
  : Set text for Quit Menu (default:"Quit Installation") text_quit_msg 
  : Set text for Quit Confirmation Message (default:"Are you sure to quit the Installer?") rom_name : Set ROM Name Information rom_version : Set ROM Version Information rom_author 
  : Set ROM Author Information rom_device : Set ROM Device Information customkeycode_up 
  : Set Alternative keycode for up key (navigate up) customkeycode_down : Set Alternative keycode for down key (navigate down) customkeycode_select : Set Alternative keycode for select key (select an item) customkeycode_back : Set Alternative keycode for back key customkeycode_menu 
  : Set Alternative keycode for menu key  newvalue - New value to be set for configname  Return Value: none   Examples:   calibrate   Descriptions:   Set Touch Screen Calibration Data. Different device may had different touch screen calibration data. To get calibration data, press menu, select calibration tools then follow the intructions.   Sintax:      void calibrate(divx, addx, divy, addy [, alternative_method]);   Parameters:divx - Division value for horizontal touchscreen to display resolution. addx - Add value for horizontal alignment. divy - Division value for vertical touchscreen to display resolution. addy - Add value for vertical alignment. alternative_method [Optional] - Use alternative method for touch screen handling if normal method not works in your device (default:"no")  Return Value: none   Examples:   calibtool   Descriptions:   Start calibration tool.   Sintax:      void calibtool(dummy_arguments);   Parameters:dummy_arguments - Edify should pass at least 1 arguments. Just Pass "" for it  Return Value: none   Examples:   theme   Descriptions:   Set AROMA Installer Theme will be used in next display.   Sintax:      void theme(theme_name);   Parameters:theme_name - Theme Name will be used. It was theme directory name located in "META-INF/com/google/android/aroma/themes"  Return Value: none   Examples:   VARIABLE FUNCTIONS  getvar   Descriptions:   Get Variable   Sintax:      variable_value getvar(varname);   Parameters:varname - Variable Name  Return Value: Variable Value   Examples:   setvar   Descriptions:   Set Variable   Sintax:      void setvar(varname, value);   Parameters:varname - Variable Name to be set value - New Value for Variable  Return Value: none   Examples:   appendvar   Descriptions:   Append new value after previous value, it's like concating strings ( previous_value + newvalue )   Sintax:      void appendvar(varname, value);   Parameters:varname - Variable Name to be set value - New Value to be appended in variable  Return Value: none   Examples:   prependvar   Descriptions:   Prepend new value before previous value, it's like concating strings ( newvalue + previous_value )   Sintax:      void prependvar(varname, value);   Parameters:varname - Variable Name to be set value - New Value to be prepended in variable  Return Value: none   Examples:   PROP FILE HANDLER FUNCTIONS  file_getprop   Descriptions:   Read prop file value for given keyname   Sintax:      prop_value file_getprop(filename, keyname);   Parameters:filename - Absolute path of prop file in filesystem keyname - Prop Key Name  Return Value: Value of prop for given keyname   Examples:   prop   Descriptions:   Same with file_getprop, but will read relatively from AROMA Temporary Directory "/tmp/aroma-data/"   Sintax:      prop_value prop(filename, keyname);   Parameters:filename - Relative path of prop file in AROMA Temporary Directory "/tmp/aroma-data/" keyname - Prop Key Name  Return Value: Value of prop for given keyname   Examples:   zipprop   Descriptions:   Same with file_getprop, but will read the prop file from Zip   Sintax:      prop_value zipprop(zip_path, keyname);   Parameters:zip_path - Absolute path of prop file in Zip ( don't add "/" in first character ) keyname - Prop Key Name  Return Value: Value of prop for given keyname   Examples:   resprop   Descriptions:   Same with zipprop, but will read the prop file from Zip relatively from AROMA Resource Directory "META-INF/com/google/android/aroma/"   Sintax:      prop_value

Originally Posted by badwolf94

Hey guys,

Every time i try to run my AROMA installer is gives me,

SYNTAX!!! aroma-config on line 93 col 3

I've searched through the config and that line is

);

After reading through this thread and trying all the various suggestions i couldn't seem to fix it. (Though i did find some missing "," and removing those at the end of the appropriate lines)

Any help would be appreciated

Originally Posted by Harbir

???? strange
ur aroma is working no problem see your self

Same here (tested with my update-binary files)


AROMA INSTALLER version 2.58
(c) 2012 by amarullz xda-developers

ROM Name : Badwolf: The Chameleon Circuit
ROM Version : 1.1 XXDME1
ROM Author : badwolf94
Device : International Samsung Galaxy Note II - N7100
Start at : Sun May 19 08:48:18 2013


----------------------------------
+ Samsung Galaxy Note II +
+ Badwolf: The Chameleon Circuit +
----------------------------------
----------------------------------
+ Formatting Partitions +
----------------------------------
+ Installing system... +
----------------------------------
+ Installing selected options +
----------------------------------
----------------------------------
+ Completed! +
----------------------------------
unmount of /system failed; no such volume
unmount of /data failed; no such volume
unmount of /preload failed; no such volume
script result was []


Installer Sucessfull (Status 0)


End at : Sun May 19 08:48:18 2013

Hi Carl1961,
nice to find you here again after having had quite a few meetings on the HD2 Forum back in the days...

Thank you for your efforts.

I now checked all possible channel combinations inspired by those you posted, trying to get the TWRP 2.5.0.0 Colorspace of RGBX_8888 to render properly in Aroma. Results (including my previous 4 attempts):

rgba=crash/stop of execution
argb=crash/stop of execution

rbga=dark blue/green tint
arbg=triggers TWRP UI reload

bgra=turquoise tint
abgr=dark blue/green tint

brga=dark blue/green tint
abrg=dark blue/green tint

gbra=dark blue/green tint
agbr=dark blue/green tint

grba=dark blue/green tint
agrb=dark blue/green tint

Question: do you know how to understand the "//blue select" or "//yellow background" bit behind the function? I cannot make much sense of it other than that being comments?
I suppose it will all boil down to something having to be adjusted/added on the Aroma side of things? Or else: it all boils down to the update-binary from Amarullz needing to learn to render RGBX_8888 properly.

I am not sure where the best place is to ask this question, but is there a way to decompile the classes.dex file inside of framework.jar replace a few files, recompile it and continue flashing the new framework.jar file using a script from a update zip? I know how to decompile/recompile the classes.dex using smali/baksmali on a computer, but I want to make a update zip that replaces certain files.

(solved)help for kernel selection and installation in aroma

---

sir i am working on aroma script to include selection for kernels. but cant figure out proper way for error free installation.
can anybody please look in it . i m attaching my meta-inf folder here. i need to have boot.img installation along with it's modules.

update-solved ...

Originally Posted by prestige777

I am not sure where the best place is to ask this question, but is there a way to decompile the classes.dex file inside of framework.jar replace a few files, recompile it and continue flashing the new framework.jar file using a script from a update zip? I know how to decompile/recompile the classes.dex using smali/baksmali on a computer, but I want to make a update zip that replaces certain files.

You want the update.zip to decompile, edit, rebuild, and sign? That sounds like a bit much for an update.zip.

Is there a reason you cannot include the edited framework.jar in your update.zip?