yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] NilsP:
@Amarullz

I can confirm working well on HTC Rezound

http://xdaforums.com/showthread.php?t=1508118

Plus a couple of other devs using it also

Thanks
[Android Software/Hacking General [Developers Only]] macia10:
Hi,

Dont know if someone mentioned this before but touch screen does not work in any method on Galaxy Spica i5700
[Android Software/Hacking General [Developers Only]] amarullz:
Send me your aroma-config. use: http://pastebin.com/

It's absolutely don't need to sign anything now :cool:
[Android Software/Hacking General [Developers Only]] Paradoxxx:
So sad that it displays weird on My S2...

Else it seems that the touch works, but everything is displayed really really weirdly.

Looking forward for updates.
[Android Software/Hacking General [Developers Only]] amarullz:
Yes... know already.. On the way to fix it...
[Android Software/Hacking General [Developers Only]] bar3200:
Actually, I started everything all over again and mabye I did something wrong at first because now it's working... but I did something wrong with menubox so I fixed it and try again.... So before I try, any chance it will work with non english? It will show me the text?
[Android Software/Hacking General [Developers Only]] amarullz:
If your language only used !”#$%&’()*+,-./0123456789:;<=>?@ABCDEFGHI JKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~© it works.

I still don't have any planing to support unicode.. but true type font may be implemented for future...
[Android Software/Hacking General [Developers Only]] bar3200:
If I'll replace my language's letters with english letters, will it work?
[Android Software/Hacking General [Developers Only]] :
Hi,

Will you adds support for ldpi devices and resistive touchscreens, or if there is a way to do it myself?

I have tried it (not in my rom) and it works but it doesnt look good because my screen is ldpi(240x320), and touch isnt working. Soft keys and hardware keys are working ok

Thanks
[Android Software/Hacking General [Developers Only]] FBis251:
I can confirm the messed up graphics on the latest nightly (10f) on the SGS4G. Doesn't happen in builds 1 through 3 though.

SGS4G has a WVGA (800×480) screen.

Thank you for your time :).

EDIT

Is your displaycapture.zip supposed to NOT have an updater-script in it?
[Android Software/Hacking General [Developers Only]] amarullz:
you can create custom fonts yourself, but to access it you still need to use the ordered characters (from ascii code for space to ~)...

If you only need some chars that don't included in font list, My tips is swap some character that least used, like:

~`$^=+;><\|{}[]

and don't use this chars:

/%

because it used by path name when install ui (in percentage and path seperator)

You can change the default text like this:

ini_set("text_back","< Back");

ini_set("text_next", "Next >");

look at manual in first page

But I know there still some

Just try it first, if display&touch works, so it works (I know it will crowded/UI is too big), just need to create smaller custom fonts and smaller iconset...
[Android Software/Hacking General [Developers Only]] amarullz:
Doesn't happen in builds 1 through 3 though = will find why...

displaycapture.zip supposed to NOT have an updater-script = Yes.. no script, just binary.... can you dump the recovery log after you run it, and post here the result...
[Android Software/Hacking General [Developers Only]] :
I tried it already and it works, everything except touchscreen(hard and soft buttons works correctly)

Recovery is 5.0.2.6

As for the ui, i will try resizing font and elements
[Android Software/Hacking General [Developers Only]] bar3200:
Thank you so much for helping me btw!!

I tried to make my own font but I had a problem...

I did it in photoshop with 32 bit color like you said, and when I wanted to save, it didn't show "png" format.

When I tried it with 8 bit color, it did show.

What's the problem?
[Android Software/Hacking General [Developers Only]] amarullz:
I am not familiar with photoshop. But in Adobe Fireworks there is option when you export it. The different was:

8bit = 256color in pallete mode (support alpha transparancy)

24bit = True color rgb(255,255,255) - Not support transparancy

32bit = True color rgba - support alpha transparancy.

Is there any export menu in photoshop??
[Android Software/Hacking General [Developers Only]] bar3200:
Didn't find any export menu in photoshop... there is such a menu but not that kind of export...

I'll try fireworks :) thanks!
[Android Software/Hacking General [Developers Only]] FBis251:
Actually make that builds 1 through 5
[Android Software/Hacking General [Developers Only]] amarullz:
Try this: http://www.amarullz.com/_downloads/aroma-nighly/aroma-nightly-120204-011.zip
[Android Software/Hacking General [Developers Only]] :
i have managed to make ui look normal by resizing png's but touch still isnt working

Thanks for your work and help anyway
[Android Software/Hacking General [Developers Only]] FBis251:
Worked perfectly! Thank you.
[Android Software/Hacking General [Developers Only]] Chaqmol:
amarullz how did you take screenshot from aroma installation wizard?:D
[Android Software/Hacking General [Developers Only]] FBis251:
I'm pretty sure he used DDMS

http://developer.android.com/guide/developing/debugging/ddms.html
[Android Software/Hacking General [Developers Only]] Messi10:
Help

i get SYNTAX ERROR on aroma-config line 668 col 5 when i try to flash my rom with aroma installer.

Galaxy mini

aroma-config is attached
[Android Software/Hacking General [Developers Only]] Messi10:
thanks but still same problem:confused::confused::confused:
[Android Software/Hacking General [Developers Only]] Messi10:
thank u for trying to help me

Now i'm getting SYNTAX ERROR!!! line 41 col1:confused::confused::confused::confused:

sorry i'm a big nooob:cyclops::cyclops::cyclops:
[Android Software/Hacking General [Developers Only]] CosmicDan:
Nope, came back. I don't know what's causing this, the PNG compression, bit-depth and DPI of all my new graphics are identical to the originals. I guess this is unique to the X10 and without some debug-logging capability enabled in Aroma I'm stuck with this annoyance.
[Android Software/Hacking General [Developers Only]] mattmanwrx:
From what I can see - no endif; for line 191 if statement! (First theme statement!) (line 191 is in notepadd++)

##
# SET THEME
#
#-- Change Info:
# file_getprop : should use absolute path "/tmp/aroma/theme.prop"
# prop : just use relative path "theme.prop" will automatically read the "/tmp/aroma/theme.prop"
#
[COLOR="Red"]if prop("theme.prop","selected.0")=="1" then
theme("Generic");[/COLOR]

if prop("theme.prop","selected.0")=="2" then
theme("miui");
endif;

if prop("theme.prop","selected.0")=="3" then
theme("ics");
endif;

if prop("theme.prop","selected.0")=="4" then
theme("miui4");
endif;

if prop("theme.prop","selected.0")=="5" then
theme("sense");
endif;
[Android Software/Hacking General [Developers Only]] Dblfstr:
Post deleted.
[Android Software/Hacking General [Developers Only]] espaciosalter20:
I'm getting the following error:

What it's possible wrong?
[Android Software/Hacking General [Developers Only]] Dblfstr:
Too many endif after

If

Prop(gingerspeedmenu=4

Also there is an endif after supercharger tweaks, but no if.

Edit: never mind on that second part.

Edit 2: I see the first if now. Lol too many nested if statements.
[Android Software/Hacking General [Developers Only]] espaciosalter20:
Can you be a little more specific? what i have to change? Thanks!
[Android Software/Hacking General [Developers Only]] Turge:
Exactly what the error message says. iif requires 3 arguments and is used similar to an if else:

Example:

iif(prop("type.prop","selected")=="3",

"item.1.1=0\n" +

"item.1.2=0",

"");
[Android Software/Hacking General [Developers Only]] Dblfstr:
Sorry, I was reading on my phone and I hate typing on that thing.

I never saw the iif, only the if

But, Turge is right, if it expects three arguments, you need three. Did you mean to use an iif or just an if?

here is the part of the code:

if (prop("type.prop","selected")!="4") then
writetmpfile(
"customize.prop",

[B]iif(prop("type.prop","selected")=="3",[/B]
"item.1.1=0\n"+
"item.1.2=0\n"+
"item.1.3=0\n"+
"item.1.4=0\n"+
"item.1.5=0\n"+
"item.1.6=0\n"+
"item.1.7=0\n"+
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
hey guys hoping for a little help here. I am trying to create a script that will run when certin options are selected in aroma.config. It is for kernel options.

{

if

file_getprop("/tmp/aroma-data/tams2w.prop","selected.0") == "1"

then

run_program("/sbin/busybox", "sed", "-i", "s#^SWEEP2WAKE=.*#SWEEP2WAKE=1#", "/system/etc/init.d/00tamcore-kernel");

fi

}

{

if

file_getprop("/tmp/aroma-data/tams2w.prop","selected.0") == "2"

then

run_program("/sbin/busybox", "sed", "-i", "s#^SWEEP2WAKE=.*#SWEEP2WAKE=2#", "/system/etc/init.d/00tamcore-kernel");

fi

}

I just pretty much took a shot in the dark with that, but is a no go. Not sure how to set up the script in order to run my options. Any help would be greatly appreciated.

Trying to get the two attached scripts to run.
[Android Software/Hacking General [Developers Only]] Dblfstr:
Is this to enable the kernal module for the ability to swipe the screen to wake it (no pushing buttons) - isn't there an apk for that?
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
There are actually four different options in aroma for this kernel that I need to be able to run with a shell script. I have two kernel options now and the only way I am going to be able to get it all to work is getting a .sh script working for these.

Anyone willing to hop on #aroma and give a hand would be greatly appreciated.
[Android Software/Hacking General [Developers Only]] Dblfstr:
Sorry, I'm no good with shell scripts.

Can they not be enabled from the update script?
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
Yes I had them in the update script before, but with the new kernel my options in aroma.config change depending on the kernel you choose. So the bricked kernel would take you down one set of options and the tamcore down a different. But when running the update script and it comes to the options for tam core kernel it errors out say /tmp/aroma.config/tam.prop does not exist because those options were not selected during the install process. But if I can get my script running, just when it installs the tamcore kernel instead of have the update script to check aroma options, it just runs a shell script that will check the options and run them. This way aroma will not error out because I will not need seperate props for all the different options.

https://dl.dropbox.com/u/46609326/WORKING_EyeCandy_v2.6.zip

Here is my setup with out the system apps and other stuff, seeing the scripts and everything may help describe better what I am trying to accomplish.
[Android Software/Hacking General [Developers Only]] Dblfstr:
I see. I cannot go to dropbox while at work, so I will have to look at it when i get off work in ~1 hour.

You already have programmed the updater-script to run the shell script?

If so, is it just the shell script that needs to be written?
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
Is it possible to run an if command inside another before it is ended.

if

file_getprop("/tmp/aroma-data/kernels.prop","selected.0") == "3"

then

ui_print("-->Flashing Newest TamCore Kernel<--");

package_extract_dir("kernel/Tam", "/system");

package_extract_file("tam.img", "/dev/block/mmcblk0p20");

run_program("/sbin/busybox", "sed", "-i", "s#start mpdecision#\#start mpdecision#", "/system/etc/init.qcom.post_boot.sh");

run_program("/sbin/busybox", "sed", "-i", "s#start thermald#\#start thermald#", "/system/etc/init.qcom.post_boot.sh");

set_perm(0, 2000, 0755, "/system/etc/init.d/00tamcore-kernel");

if

file_getprop("/tmp/aroma-data/tams2w.prop","selected.0") == "1"

then

ui_print("-->Enabling Sweep2Wake<--");

run_program("/sbin/busybox", "sed", "-i", "s#^SWEEP2WAKE=.*#SWEEP2WAKE=1#", "/system/etc/init.d/00tamcore-kernel");

endif;

if

file_getprop("/tmp/aroma-data/tams2w.prop","selected.0") == "1"

then

ui_print("-->Enabling Sweep2Wake with no lights<--");

run_program("/sbin/busybox", "sed", "-i", "s#^SWEEP2WAKE=.*#SWEEP2WAKE=2#", "/system/etc/init.d/00tamcore-kernel");

endif;

if

file_getprop("/tmp/aroma-data/tammods.prop","item.0.1") == "1"

then

ui_print("-->Enabling ZRAM<--");

run_program("/sbin/busybox", "sed", "-i", "s#^ZRAM=.*#ZRAM=1#", "/system/etc/init.d/00tamcore-kernel");

endif;

if

file_getprop("/tmp/aroma-data/tammods.prop","item.0.2") == "1"

then

ui_print("-->Enabling Tun Module<--");

run_program("/sbin/busybox", "sed", "-i", "s#^TUN=.*#TUN=1#", "/system/etc/init.d/00tamcore-kernel");

endif;

endif;
[Android Software/Hacking General [Developers Only]] mattmanwrx:
Yes, it is possible... With help from.people in this thread I came up with this:

(a small snippet from.my script)...

if
( file_getprop("/tmp/aroma/animationtype.prop","selected.1") == "1" ) && ( file_getprop("/tmp/aroma/animationposition.prop","selected.1") == "2" );
then
if
file_getprop("/tmp/aroma/animationconfig.prop","selected.1") == "1";
then
package_extract_dir("centered/black/green-x", "/system/customize/resource");
ui_print("Green Centered X with a Black background copied");
endif;
if
file_getprop("/tmp/aroma/animationconfig.prop","selected.1") == "2";
then
package_extract_dir("centered/white/green-x", "/system/customize/resource");
ui_print("Green Centered X with a White background copied");
endif;
endif;
[Android Software/Hacking General [Developers Only]] pimpmaneaton:
Awesome, was able to get my issue sorted out by running multiple if commands inside an if command. This cured my issue where an if command in updater script did not cause an error because prop was not in /tmp due to an if command in the aroma.config.

So now just need to get my Kindle Rom running Aroma, but that will have to wait till the new Aroma is released with the newer calibration process.

Thanks everyone for you help.
[Android Software/Hacking General [Developers Only]] Robobob1221:
OK I've been trying to correct this but I'm getting the same Status 1 error everytime.

It tells me there is a Syntax Error on line 219 col 4 Here is a sample of the code

if (prop("type.prop","selected")=="1") then
#-- IF "Default" Installation, don't show configuration, then write default mods.prop
#-- NOTE: mods.prop should exists, or updater-script will error
writetmpfile(
#-- Prop file will write to /tmp/aroma/mods.prop
"mods.prop",

#-- Default Values
"selected.1=1\n"+	#-- SS Launcher
[COLOR="Red"]);[/COLOR]

The last line ');' is causing the error. why is this wrong? any help would be great
[Android Software/Hacking General [Developers Only]] ChaosFirZen:
"selected.1=1\n"+ #-- SS Launcher

Remove the "+" sign Plus is added when there is more Item..
[Android Software/Hacking General [Developers Only]] Robobob1221:
Thanks that worked but now I'm getting the same error but a different line, 247

#-- IF Not "Default" Show Main Features Selection
selectbox(
#-- Title
"Launcher Installer",

#-- Sub Title
"Please select the launcher you want with your installation:",

#-- Icon: <AROMA Resource Dir>/icons/default.png or <ThemeDir>/icon.default.png
"@default",

#-- Will be saved in mods.prop
"mods.prop",

#-----------------------------------[ Selectbox With Groups ]----------------------------------#
# TITLE | SUBTITLE | Initial Value #
#------------------+-----------------------------------------------------------+---------------#

"Launcher", "", 2, #-- Group 1. key = "selected.1"
"SS Launcher",	"Install SS Launcher",	1, #-- selected.1 = 1
"GO Launcher EX", "Install GO Launcher EX",	0, #-- selected.1 = 2
"ADW.Launcher", "Install ADW.Launcher",	0, #-- selected.1 = 3
"Rosie Launcher", "Install Rosie Launcher",	0, #-- selected.1 = 4
"AOSP Launcher", "Install default AOSP Launcher", 0, #-- selected.1 = 5

#--------[ Initial Value = 0: Unselected, 1: Selected, 2: Group Item, 3: Not Visible ]---------#
);
endif;

I've compared to the original, and the only thing I can see is that I only have one group. Is that the problem or am I blind?

The lines don't seem aligned here but they are in my script. Could that be the problem?
[Android Software/Hacking General [Developers Only]] mattmanwrx:
Remove the "," comma on - "AOSP Launcher", "Install default AOSP Launcher",

Should work then...
[Android Software/Hacking General [Developers Only]] Turge:
Let me give you a hint... Make sure the last character before the last closing bracket ")" of a function (ie. "selectbox") is not a "+" or a "," ;)
[Android Software/Hacking General [Developers Only]] Robobob1221:
It was the "," on the last 0.

Thanks for the tips/hints. Today was my first time to attempt using this. It's those small things that I miss! I must be blind:eek:

Got the aroma installer to work now! Thanks again:good::good:
[Android Software/Hacking General [Developers Only]] TheGreatSega:
Help. Syntax error

##
# MAIN FEATURES
#
if (prop("type.prop","selected")=="1") then
writetmpfile(
"mods.prop",

#-- Default Values
"selected.1=1\n"+ #-- build.prop
"selected.2=1\n"+ #-- RootAccess
"selected.3=1\n"+ #-- BootAnimation
"selected.4=1\n" #-- WiFiModules
);
else
#-- IF Not "Default" Show Main Features Selection
selectbox(
#-- Title
"Main Features",

#-- Sub Title
"Please choose an option for each of the items:",

#-- Icon: <AROMA Resource Dir>/icons/default.png or <ThemeDir>/icon.default.png
"@default",

#-- Will be saved in /tmp/aroma/mods.prop
"mods.prop",

#-----------------------------------[ Selectbox With Groups ]----------------------------------#
# TITLE | SUBTITLE | Initial Value #
#------------------+-----------------------------------------------------------+---------------#

"Device Model", "",	2, #-- Group 1. key = "selected.1"
"Xperia Arc", "",	1, #-- selected.1 = 1
"Xperia Arc S", "",	0, #-- selected.1 = 2
"Root Access", "",	2, #-- Group 2. key = "selected.2"
"Superuser", "Very stable and fast",	1, #-- selected.2 = 1
"SuperSU", "More powerful but less stable",	0, #-- selected.2 = 2
"Boot Animation", "",	2, #-- Group 3. key = "selected.3"
"ThSEGA", "ThSEGA Bootanimation",	1, #-- selected.3 = 1
"Dark knight", "ArcKnight Inspired",	0 #-- selected.3 = 2
"Make Believe", "Sony Make Belive", 0 #-- selected.3 = 3
"WiFi Modules", "", 2, #-- Group 4. key = "selected.4"
"Stock ", "Stock Modules", 1, #-- selected.4 = 1
"DoomKernel ", "DoomKernel Modules", 0, #-- selected.4 = 2
"Arc-Knight ", "Arc-Night WiFi Modules", 0, #-- selected.4 = 3
"KTG", "KTG WiFi Modules", 0, #-- selected.4 = 4

SYNTAX ERROR!!! aroma-config on line 209 col 23 (status 1)

Line 209 col 23 is "Make Believe",
[Android Software/Hacking General [Developers Only]] mattmanwrx:
No comma after the 0... Could be it?
[Android Software/Hacking General [Developers Only]] TheGreatSega:
Thanks but now i get this

##
# MAIN FEATURES
#
if (prop("type.prop","selected")=="1") then
writetmpfile(
"mods.prop",

#-- Default Values
"selected.1=1\n"+ #-- build.prop
"selected.2=1\n"+ #-- RootAccess
"selected.3=1\n"+ #-- BootAnimation
"selected.4=1\n" #-- WiFiModules
);
else
#-- IF Not "Default" Show Main Features Selection
selectbox(
#-- Title
"Main Features",

#-- Sub Title
"Please choose an option for each of the items:",

#-- Icon: <AROMA Resource Dir>/icons/default.png or <ThemeDir>/icon.default.png
"@default",

#-- Will be saved in /tmp/aroma/mods.prop
"mods.prop",

#-----------------------------------[ Selectbox With Groups ]----------------------------------#
# TITLE | SUBTITLE | Initial Value #
#------------------+-----------------------------------------------------------+---------------#

"Device Model", "",	2, #-- Group 1. key = "selected.1"
"Xperia Arc", "",	1, #-- selected.1 = 1
"Xperia Arc S", "",	0, #-- selected.1 = 2
"Root Access", "",	2, #-- Group 2. key = "selected.2"
"Superuser", "Very stable and fast",	1, #-- selected.2 = 1
"SuperSU", "More powerful but less stable",	0, #-- selected.2 = 2
"Boot Animation", "",	2, #-- Group 3. key = "selected.3"
"ThSEGA", "ThSEGA Bootanimation",	1, #-- selected.3 = 1
"Dark knight", "ArcKnight Inspired",	0 #-- selected.3 = 2
"Make Believe", "Sony Make Belive", 0 #-- selected.3 = 3
"WiFi Modules", "", 2, #-- Group 4. key = "selected.4"
"Stock ", "Stock Modules", 1, #-- selected.4 = 1
"DoomKernel ", "DoomKernel Modules", 0, #-- selected.4 = 2
"Arc-Knight ", "Arc-Night WiFi Modules", 0, #-- selected.4 = 3
"KTG", "KTG WiFi Modules", 0, #-- selected.4 = 4

#--------[ Initial Value = 0: Unselected, 1: Selected, 2: Group Item, 3: Not Visible ]---------#

);
endif;

SYNTAX ERROR!!! aroma-config on line 218 col 4 (status 1)

Line 218 col 4 is ");",
[Android Software/Hacking General [Developers Only]] mattmanwrx:
take out the comma after "0" on above line... So right before the );
[Android Software/Hacking General [Developers Only]] TheGreatSega:
i have no idea why i making ROOKIE mistakes!!.. its 2:30 here and i really need to finish this ROM.. thanks soo much for your help!!
[Android Software/Hacking General [Developers Only]] glennd:
Have been searching for an answer but cant find how to install a custom theme using the aroma installer? I am about to update my SG3 to the latest Omega rom and it would be nice if i could throw the Theme zip in the same zip as the Rom, so I can flash it once instead of flashing rom and then flashing theme. Were do I put the Theme?
[Android Software/Hacking General [Developers Only]] mattmanwrx:
Unless you're the rom developer it would be pointless, in my opinion.. It would be writing out a lot of work, for a single flash!

You would need to add the selectbox to the aroma-config, and then the correct if statement to the updater-script

What could just be easier is to add the theme to the .zip and in the updater -script get it to write the files without the "AROMA options"... It would still get installed, just you wont be asked an option in AROMA!
[Android Software/Hacking General [Developers Only]] CosmicDan:
I know I don't need to say it, but I'm unsubscribing from this thread because it just gets flooded with people asking for help who have no idea what they're doing and are too lazy to look at their code, it's not that hard to fix syntax errors.

Would be nice if there was another thread for aroma script help and then this thread can be reserved to UPDATES and BUG REPORTS (stuff that's actually important and good).

Meanwhile, the pixel-shift bug for the X10 in Aroma installer I reported a while back (but was ignored) has been fixed on the kernel level, so that's all fine now.
[Android Software/Hacking General [Developers Only]] da-pharoah:
well why dont you start one up then... no sence complaining if you dont offer a resoultion.... just my opinion... but fyi, im ok with asking for help here... sometimes it takes a second person to help me see whats right in front of my face. sometimes I have to step back and look at the code infront of me and sometimes I may miss something that creates a syntex error... so its nice to have help. but hey thats just my opinion on my own experiences....
[Android Software/Hacking General [Developers Only]] Dblfstr:
Where does this come into play

if
file_getprop("/tmp/aroma-data/sense4.prop","selected.0") == "4"
then

I see in your aroma-config where you can select the version.prop (or the theme) but I do not see where you select anything else.

You update is dependent on multple things being selected with you many many many if then statements. But I only see where you choose the version.prop.

If you choose the version.prop and it tells the updater to choose that theme, but the install is relying on more options that are never selected, you will get installation success messages, but nothing will be installed.

Maybe I am reading it wrong though.
[Android Software/Hacking General [Developers Only]] ssojyeti2:
You see, my updater script uses a patch similar to villain theme system, where it uses if, then, statements like those to get the job done. That's why it doesn't look like I'm telling it to flash something when I actually am.

So...

if

file_getprop("/tmp/aroma-data/sense4.prop","selected.0") == "4"

then

The patch that pushes the icons into the apps runs...