yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] k2wl:
hey Amarullz !! thanks for aroma.

i have made my rom with aroma installer. link - http://xdaforums.com/showthread.php?t=2200677

kindly add it to ur list. thanks again.
[Android Software/Hacking General [Developers Only]] Mr Impossible:
Seem to be having problems with Aroma on a TMO M919 with touch screen not working. I have used it on a S3 and a N2 without problems. I can navigate with the power/volume keys just fine. Any ideas or suggestions?

Thx!
[Android Software/Hacking General [Developers Only]] masterex567:
Yup but, now i created two tmp files called apex.prop and nova.prop

If user selects apex launcher in the menu box, he gets different options of icon packs, and if user selects nova launcher he gets nova icon packs.

All went well, tried to test and now if i select apex launcher, recovery shows that it cannot find nova.prop.

If i select nova launcher it shows that it cannot find apex.prop

What can i do?
[Android Software/Hacking General [Developers Only]] Harbir:
i think u made it like

in menu apex is sleeted

if prop("apex.prop","selected")=="1" then

that is wrong

make it like this

if prop("launcher.prop","selected")=="1" then

and

if prop("launcher.prop","selected")=="2" then (for nova)
[Android Software/Hacking General [Developers Only]] masterex567:
That's what i'm doing..

but instead of the launcher.prop","selected") i'm using "launcher.prop",selected.1")

maybe that's the problem.
[Android Software/Hacking General [Developers Only]] Harbir:
right u are doing that wrong :D it is a menu box
[Android Software/Hacking General [Developers Only]] masterex567:
On second thought i want to use a selectbox...

I already have a menubox, and many options...

So i use selected.1 right?
[Android Software/Hacking General [Developers Only]] Harbir:
For selectbox use selected.0 kk;)
[Android Software/Hacking General [Developers Only]] masterex567:
If you don't mind, i'm going to pm you with all the details.

Please try to spare some time and help. :)
[Android Software/Hacking General [Developers Only]] Harbir:
U have a fix ....;) check pm
[Android Software/Hacking General [Developers Only]] utkaar099:
Getting a syntax error on line 191 col 7 with a Status 1 error, can't seem to find what's up.

EDIT: nevermind found it lol
[Android Software/Hacking General [Developers Only]] ketut.kumajaya:
[MENTION=402300]amarullz[/MENTION] Reuse your AROMA binary for dual booting boot menu http://xdaforums.com/showpost.php?p=41219095&postcount=108, big thanks!
[Android Software/Hacking General [Developers Only]] Snuzzo:
Can't quite seem to get this right:

I've been playing around with this for about an hour now trying to echo/cat back values of multiple prop files made to allow an end user see what values they chose, almost as a last chance confirmation before installing.

Currently as an example it's set to as follows:

alert(
"Current install set for",
prop("value.prop", "ui")+
prop("value.prop", "ui")+
prop("value.prop", "ui")
);

Before the "ready to install" viewbox
[Android Software/Hacking General [Developers Only]] Snuzzo:
Ok found that I needed to add a little something extra

alert(
"Current install set for",
prop("value.prop", "ui")+"\n"+
prop("value.prop", "ui")+"\n"+
prop("value.prop", "ui")
);

That works PERFECT!
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I was just wondering one thing. Why is it that the original updater-binary is even used along with Aroma? Just add erase_image and flash_image and you can do everything from within aroma without needing any additional install binary. The problem with updater-binary is that it is not cross device compatible. Even though most of them are compiled for any type of arm, different versions works for different devices. Just remove the updater-binary and you can even skip that extra work of setting up the extra updater-script and just built aromas script to do everything.

EDIT

Well, it seams that one important thing is missing. A folder extraction function. All we have in aroma, is file extraction to /tmp/aroma/.

TODO?

extract_dir("system", "/system")
[Android Software/Hacking General [Developers Only]] Sneakyghost:
[EDIT]

Disregard. My previous post about the package_extract not working is likely due to a faulty device rather then a faulty update-binary-installer or update-binary.

Mobile Post
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Hmm, I think that I need a second pair of eyes on this small Aroma script.

ini_set("text_next", "Start Injector");

selectbox(
"Select Action", "Please select an action for the Injector",

"@install",

"action.prop",

"Inject boot partition", "Extract, inject and reflash the current boot.img", 1, #-- selected.0 = 1
"Inject and store current boot.img", "Extract, inject and store the current boot.img to the primary storage", 0, #-- selected.0 = 2
"Inject stored boot.img", "Inject a boot.img stored in Injector/ on the primary storage", 0, #-- selected.0 = 3
"Inject and Flash stored boot.img", "Inject and flash a boot.img stored in Injector/ on the primary storage", 0 #-- selected.0 = 4
);

if prop("action.prop", "selected.0")=="1" then
setvar("inject.message", "Injecting the boot partition");
setvar("inject.action", "inject-flash-current");

else
if prop("action.prop", "selected.0")=="2" then
setvar("inject.message", "Injecting the extracted boot partition and storing it");
setvar("inject.action", "inject-store-current");

else
if prop("action.prop", "selected.0")=="3" then
setvar("inject.message", "Injecting stored boot.img");
setvar("inject.action", "inject-stored");

else
setvar("inject.message", "Injecting and flashing stored boot.img");
setvar("inject.action", "inject-flash-stored");
endif;
endif;
endif;

pleasewait("Unpacking installer package...");

if
ziptotmp("busybox", "busybox") && ziptotmp("src.zip", "src.zip")
then
pleasewait("Extracting source files...");

if
exec("/tmp/aroma-data/busybox", "mkdir", "/tmp/aroma-data/injector") && exec("/tmp/aroma-data/busybox", "unzip", "/tmp/aroma-data/src.zip", "-d", "/tmp/aroma-data/injector") && exec("/tmp/aroma-data/busybox", "chmod", "0775", "/tmp/aroma-data/injector/injector.sh")
then
pleasewait("Running Injector...");
exec("/tmp/aroma-data/injector/injector.sh", getvar("inject.action"));
endif;
endif;

ini_set("text_next", "Exit");

textbox(
# -- Headline -- #
"Injector Log",

"<b>Log output from the Injector</b>",

# -- Icon -- #
"@info",

# -- Text -- #
read("/tmp/injector.log")
);

reboot("disable");

I have been looking at this over and over again, and I can't see what I am missing. For some reason, the last textbox is never displayed. Everything above works fine, the content is extracted, the scripts and such are executed successfully, but when the time comes to display the textbox, aroma just skips to the end and exists.
[Android Software/Hacking General [Developers Only]] Harbir:
to read the text from u have t use this codes

readfile_aroma("injector.log")

where injector.log is present in META-INF/............/aroma folder kk
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Yes I know. But that file is not placed in the ZIP. It is generated by the script executed above, and is placed in /tmp/ on the device.
[Android Software/Hacking General [Developers Only]] Harbir:
Ok , so for that u can use

readtmpfile("injector.log")

It will read data from /tmp/aroma-data/injector.log
[Android Software/Hacking General [Developers Only]] CNexus:
You need to place the text box before you set the exit text
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The exit text is the text for the button in the textbox. This needs to be set before the box is created
[Android Software/Hacking General [Developers Only]] CNexus:
Have you tried it the way I suggested? I always set my exit text last
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I am not at a computer at the moment. But I will give anything a try at this time.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
That made no diff. Still quits before displaying the box
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
In the Injector.sh script, I started an independent sub-process at the end. Aroma does not like that it seams. If I remove that, everything works fine.
[Android Software/Hacking General [Developers Only]] Sneakyghost:
Hello,

is this being worked on? Any news?
[Android Software/Hacking General [Developers Only]] MikeC84:
Was wondering about this as well..

Also I am trying to make a aroma.zip for my kernel but am nearly unable to press any checkbox or next/back on screen buttons. I have to use back and home hardware buttons to navigate through it. I have edited the keys a little which helped a tad but still it seems pretty hard to check boxes and press back/next button.

Any way to eliminate this issue?

Thanks,

Mike
[Android Software/Hacking General [Developers Only]] Snuzzo:
Use the previous version maybe? The one that doesn't rely on "twrp touchscreen detection."

Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
[Android Software/Hacking General [Developers Only]] ahsan_s37:
Can you make Pakage(.apk) installer like this ? It would be awesome ! :)
[Android Software/Hacking General [Developers Only]] xdracco:
Is there any way to bypass Aroma Installer on roms that implement it?
[Android Software/Hacking General [Developers Only]] Harbir:
u have to rewrite the update script and have to do many things to install the rom that's the only thing u can do (no way to bypass it )
[Android Software/Hacking General [Developers Only]] xdracco:
Thanks for the reply Harbir. I figured as much but thought I'd ask anyways.
[Android Software/Hacking General [Developers Only]] CNexus:
THIS. +500

Would definitely speed things up as well since the whole calling on the updater script would be gone
[Android Software/Hacking General [Developers Only]] [NUT]:
[MENTION=402300]amarullz[/MENTION]

On my Xperia Z aroma acts funny in several ways:

1) it is quite slow loading and sometimes it doesn't even start at all. This is both in twrp 2.5.0.0 and in cwm 6.0.3.2

2) it does respond to the touch input but it does not always act on the press of a button. It does however show the button pressed and 'sticks' in that status.

3) reboot does not work, it causes the recovery to shutdown but not entirely, it basically hangs the phone up just before the reboot.

I hope you are able to fix these issues soon, as they effectively make aroma useless on the Z. Check superuser.zip, that's my 'get to know aroma' project before I attempt something bigger...

Even DooMLoRD reported having these problems with the Z and ZL...
[Android Software/Hacking General [Developers Only]] CoffinStuffer:
Have you tried downgrading recovery? On the one x aroma gets wacked out on any version past twrp 2.3.3.1. Can't say its your issue,bit it's worth a shot.
[Android Software/Hacking General [Developers Only]] [NUT]:
Not quite... any version of TWRP below 2.4.4.0 cause major issues with the Z/ZL... so thats a no-go. Same applies to CWM 6.0.2.8 by the way... CWM 6.0.3.0 and 6.0.3.2 seem to be stable.
[Android Software/Hacking General [Developers Only]] CoffinStuffer:
Cool man. Sorry that doesnt help on your device. At first I had a few recovery reboots when building my aroma. The problem was in the updater. The actual set for the roms install,at first. Then symlinks was the next fix.Best advice I could give is compare other aromas. Keep all the menu boxes and install lines the same,as much as possible. My aroma did not work 100% until I figured that out.
[Android Software/Hacking General [Developers Only]] GermanGuy:
[MENTION=402300]amarullz[/MENTION]: Here is a donation towards your purchase of a HTC ONE. We badly need a fix for Aroma on that device. Keeps crashing/freezing all the time.

Confirmation number: 5N871966868366222
[Android Software/Hacking General [Developers Only]] Scott:
Hope you get your HTC One. We would love to see the update!

Confirmation number: 7DD522409E010560L
[Android Software/Hacking General [Developers Only]] Thela7:
Since all the cool kids are doing it...

Here is my small donation towards the HTC One fund 8BV15872P6428973U
[Android Software/Hacking General [Developers Only]] BeansTown106:
Don't Forget To Donate To Me:

[MENTION=402300]amarullz[/MENTION]: Here's 50$ 5VT272219G362170G for your troubles hopefully u can get something going S4,Note8, and htc one all have this touchscreen issue :(
[Android Software/Hacking General [Developers Only]] bajasur:
Are we going to see this fix for the s4?
[Android Software/Hacking General [Developers Only]] amarullz:
Need tester for new AROMA Engine. SGS4 & One is very welcome... http://db.tt/O6R5xVSd
[Android Software/Hacking General [Developers Only]] bajasur:
Thank you kind sir!
[Android Software/Hacking General [Developers Only]] clark44:
Testing now thanks!

EDIT: U.S SGS4 tested and touch is working. Was very slow when moving my finger around but touch was accurate and worked. I'm in the IRC for further assistance
[Android Software/Hacking General [Developers Only]] JEANRIVERA:
[MENTION=3828647]torxx[/MENTION]

---------- Post added at 03:00 AM ---------- Previous post was at 02:59 AM ----------

[MENTION=1631739]mike1986.[/MENTION]
[Android Software/Hacking General [Developers Only]] savie:
Sir [MENTION=402300]amarullz[/MENTION]

I know aroma need cwm/twrp to make it run on recovery.. ive check diagram on 1st page..

My question is there any clue to make aromaInstaller as default of recovery so we pass cwm/twrp interface??

Thanks for advance..
[Android Software/Hacking General [Developers Only]] amarullz:
Dump the recovery.log is very welcome :)

I still doesn't filter the touch move event, so It may flooding the message queue by move event. But if it was accurate, that was great. How about animation before you playing with touch screen? is it smooth?... This engine already optimized with ARM Neon for display drawing.

It was possible to make AROMA Recovery with AROMA engine (core), but need intensive coding :laugh:. Will try it after I finished new AROMA Installer.

----

And thank you very much for anyone who donate me for HTC One, It still far away from goals, but I can wait it (the device launch still 1 moth[july] in my country). I still using my galaxy nexus for development now...

Sorry for waiting,.. I have a new born child (1 month old) now, It was busy months back then, but now I have many spare time again to developing it... :victory::victory::victory:
[Android Software/Hacking General [Developers Only]] amarullz:
Ok, Please test again View attachment aromacore_test.zip this file in attachment... I hope the slow movement was solved...
[Android Software/Hacking General [Developers Only]] Turge:
Hey Amarullz,

I just tested this on the HTC One and here are my observations:

-touch was very slow - it would take up to 1 second for the circle to reach my finger when I would stop

-never froze once

-colors are still messed up - greenish tint was still present and there were a lot of graphic glitches when starting and ending the app (not sure if you're truing to address these)

Thanks for looking into this though!
[Android Software/Hacking General [Developers Only]] clark44:
Download keeps failing please reupload.

EDIT: Ok flashed the file using TWRP and first thing i saw was red background with a blue rectangle that kept expanding and collapsing. The red was flickering a lot. The touch was a little more responsive in regards to dragging your finger across the screen. Moving across more then one causes the tracker to move slowly in loop like motions. Other then that the circle that was used to track touch was very large but I'm guessing it will be much smaller in the final version.
[Android Software/Hacking General [Developers Only]] [NUT]:
Would it be useful to test the new aroma versions on the Xperia Z too?
[Android Software/Hacking General [Developers Only]] JEANRIVERA:
This is exactly the same thing I have observed
[Android Software/Hacking General [Developers Only]] CNexus:
[MENTION=402300]amarullz[/MENTION]

Dude, as said above, the only thing preventing us devs just skipping the updater-script entirely is the lack of

extract(dirInZip, targetDir)

And

extract_file(fileInZip, targetFile)

If you could implement those two, we could literally just do everything from inside the aroma-config so that it's more streamlined, because everything else that the updater-script can do (and more) can be done inside in there :cool:

Thanks for all the hard work :thumbup:
[Android Software/Hacking General [Developers Only]] codekidX:
hello [MENTION=402300]amarullz[/MENTION]

i have tested this attachememt in my galaxy grand duos I9082 and here are the things i obseved:

-starting animations was very smooth

-the touch is accurate

-while swipping here and there the movement is slow(if i swipe screen from up to down the touch circle comes about .60 seconds late)

also how did you get that anim at the start? i saw the zip there was only update binary and fonts.

great work please dont stop this aroma project
[Android Software/Hacking General [Developers Only]] amarullz:
I will add preupdate and postupdate in installer process, so the step was:

preupdate -> updater-script -> postupdate

While the pre and post update was handled by aroma installer.

Functions like extract, chmod, chown, symlink and other filesystem task was easy to implement and will surely be available in next version. But I cant completely get rid the updater-script, because some important functions like format is device specific (or tell me if I am was wrong).

Thanks, I will take a look again.. Maybe it was too many touch screen event sended by touch device when you move the finger.

The animation was completely drawing task by new core. It was simple gradient rounded rectangle. But in new core, it supported alphablending optimized with ARM Neon.

If the animation woks so smooth, the problem from touch screen test wasnt because the drawing engine...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
A lot of devs (me included) have often used scripts to handle some custom things, format could be one such thing (or just a direct call to busybox). If you implement a way to extract whole directories, I promise that we will manage anything else in other ways if needed :)

But keeping the option of using updater-binary is also fine. We can just choose not to use it if we dont need it.
[Android Software/Hacking General [Developers Only]] CNexus:
Ah thats true. I'll see if maybe there's another way to format partitions, but it seems like everything else would be better handled by Aroma

Also, I took a look at the source code and saw 2 reboot options. Would it be easy enough to add a reboot("recovery" ) option too? It would be nice if it's not too much trouble, and from looking at the linux source it seems like its not.

Thank you again for the awesome work and best wishes for your newborn. :thumbup:
[Android Software/Hacking General [Developers Only]] amarullz:
Did you use TWRP?... Someone with cwm said it works well and lagfree without greenish tint problem... Can you please dump the recovery.log? so I can find the solution...
[Android Software/Hacking General [Developers Only]] [NUT]:
[MENTION=402300]amarullz[/MENTION]

Would it be a good idea to try your test versions on the Sony Xperia Z too?

I'd be happy to help you out debugging for the Z, as it are problems which can drive my users mental :p
[Android Software/Hacking General [Developers Only]] amarullz:
Yes, I need anyone to test it, and report to me,.. dump the recovery.log also great...
[Android Software/Hacking General [Developers Only]] [NUT]:
OK :)

To make AROMA look good on the Z, i need to ini_set("force_colorspace","rgba"); in my aroma-config otherwise it will look just like your test version: blue-ish.

The startup was looking weird, turned red and a whilte-blue-ish rounded corner square grew in size and then shrank again for a few times, it's an effect that worked ok, but probably because the correct colorspace can't be found looks awful.

The circle is moving slow and if i trace a circle i would be done in like one second, but the circle takes almost 8 to complete the same movement.

Clicking the rounded square when you stop moving on the screen did turn it to a circle very fast.

In recovery.zip there is the log from both CWM and TWRP.
[Android Software/Hacking General [Developers Only]] amarullz:
Ok, this may the problem in color space:

AROMA[I] red : 24, 8, 0
AROMA[I] green : 16, 8, 0
AROMA[I] blue : 8, 8, 0
AROMA[V] transp : 0, 8, 0

I will add test to force colorspace to default r:16,g:8,b:0,t:24. Just wait and please try again while I am finished compiled new test file...
[Android Software/Hacking General [Developers Only]] [NUT]:
Waiting :good:
[Android Software/Hacking General [Developers Only]] amarullz:
Here View attachment aroma_core_test3.zip
[Android Software/Hacking General [Developers Only]] [NUT]:
:victory:

It looks great now. The animation shows a little artifacting when the rounded corner square is almost at it's biggest. The circle now moves correctly along side my finger, the touches of the screen are picked up even faster when i press a random location on screen or when i touch the small square it changes to a circle immediately :)

If i move really quickly, the circle also shows a little redraw artifacting, but i consider that to be trivial.

:highfive:

You've got it!

Attached my logs from CWM and TWRP during this testing session.
[Android Software/Hacking General [Developers Only]] amarullz:
I want to see the artifact if possible in video :). But is the color fixed?

The performance penalty before was caused by freetype engine. I reduces memory footprint for freetype, so it dont need to cache the drawed glyph before, but I think it wasnt good idea, so I will rethink better solution for it...
[Android Software/Hacking General [Developers Only]] [NUT]:
The colors are perfect!

http://www.fun-industries.nl/xda/tmp/aroma-test3.mp4 (80Mb) made with my ARC.

It was still running an older LuPuS kernel, so the camera button was not working, you will notice i had trouble stopping the filming :silly:

- EDIT -

Oh, i remember the first part was only showing the artifacts in CWM. In TWRP as you can see it's looking just fine. Only the second part shows the artifacts, they are quick to recover but they are visible on the film.
[Android Software/Hacking General [Developers Only]] Madaditya:
Tested on My Xperia Pro,

1.Touch detected perfect

2.No delays for me though

i could provide these

View attachment AromaTestrecovery.txt
[Android Software/Hacking General [Developers Only]] :
Sorry If I'm posting in the wrong place, I'm not sure if there is a standalone thread for problems.

Anyway, after making all the needed changes, I decided to test.

I added the Aroma Installer to my ROM and, when installing via CWM I received the following error:

SYNTAX ERROR!!! aroma-config on line 345 col 1
E: Error in /sdcard/C6603_TuRdZzROM.zip
(Status 1)
Installation Aborted

I then went to check line 345...

Then there was the problem; There was no line 345, my last line was 344.

Surely it's impossible to get an error on a line that doesn't exist?!
[Android Software/Hacking General [Developers Only]] Patrics83:
Since amarullz is back in town you might wanna post in this thread. http://xdaforums.com/showthread.php?t=1770284

Upload your aroma-config together with a short description of your problem.

Sent from my HTC One X
[Android Software/Hacking General [Developers Only]] monkeytools:
new phone support

Hello

I am trying to get support for a phone not listed. I have did a test build. But cant find update-binary is the error that i get. My question will aroma work with gb or is it ics,jb only. I can post any info needed. Ok the phone is a Casio commando. Any help would be great thanks.