yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ChronoMonochrome:
:laugh: :good:

I think it worth only to ensure that the most "vital" ROM binaries are compiled in ARM mode. Doing it in the way you said, it would be really never-ending testing :D

Btw, thanks for the link to the benchmark results. Out of curiosity, I've downloaded CoreMark sources and compiled it for android, results are below:

root@:/ # coremark_thumb
coremark_thumb
2K performance run parameters for coremark.
CoreMark Size : 666
Total ticks : 14453
Total time (secs): 14.453000
Iterations/Sec : 4151.387255
Iterations : 60000
Compiler version : GCC5.3.1 20160401 (optimized)
Compiler flags : -O2 -mthumb -march=armv7-a -mtune=cortex-a9
Memory location : Please put data memory location here
(e.g. code in flash, data on heap etc)
seedcrc : 0xe9f5
[0]crclist : 0xe714
[0]crcmatrix : 0x1fd7
[0]crcstate : 0x8e3a
[0]crcfinal : 0xbd59
Correct operation validated. See readme.txt for run and reporting rules.
CoreMark 1.0 : 4151.387255 / GCC5.3.1 20160401 (optimized) -O2 -mthumb -march=armv7-a -mtune=cortex-a9 / Heap

root@:/ # coremark_arm
coremark_arm
2K performance run parameters for coremark.
CoreMark Size : 666
Total ticks : 13845
Total time (secs): 13.845000
Iterations/Sec : 4333.694475
Iterations : 60000
Compiler version : GCC5.3.1 20160401 (optimized)
Compiler flags : -O2 -marm -march=armv7-a -mtune=cortex-a9
Memory location : Please put data memory location here
(e.g. code in flash, data on heap etc)
seedcrc : 0xe9f5
[0]crclist : 0xe714
[0]crcmatrix : 0x1fd7
[0]crcstate : 0x8e3a
[0]crcfinal : 0xbd59
Correct operation validated. See readme.txt for run and reporting rules.
CoreMark 1.0 : 4333.694475 / GCC5.3.1 20160401 (optimized) -O2 -marm -march=armv7-a -mtune=cortex-a9 / Heap

Later I'll add here more optimizations I'm using to see if it can change thumb vs arm ratio.

P.s. The size of binaries reported by benchmark itself is incorrect. ARM binary is of 25264 bytes and Thumb one is of 21372 bytes.
[Galaxy Ace II Android Development] shaqman89:
@up

That's some interesting result :D

So according to that (with standard compiler flags), we got ARM is 4% faster with a 18% difference of size?

Say, cmiiw, but is it not that binary size doesn't represents RAM allocation? If that's true, I actually agree that bigger binary size is acceptable if it gives better performance.
[Galaxy Ace II Android Development] ace2nutzer:
Well that's pretty interesting now :D :good:

Well, and now how to check about RAM usage ??

btw Guys... i've finally updated Post 1 - 3 :D ... enjoy !!
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, it's possible. But lets remember that android is not a benchmark - there are libraries that can reside in the memory while actually not doing anything resource-intensive (or do so relatively rarely). This is exactly the case where the less size has binary then better, though it may not be that easy to determine which these binaries are, or at least not so obvious.

So far have no ideas better than checking it using ps or top utility.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah .... why not ?? - Can u pls provide some stats ?? Accordingly to the CoreMark u did for thumb-2 vs. arm ???
[Galaxy Ace II Android Development] ChronoMonochrome:
Seems that difference is exactly same as difference between sizes of binaries. ARM binary requires 984 kB to run and THUMB one 980 kB, so I assume, the "base" memory requirement is ~960Kb + the actual size of binary. Looks like it's only beneficial to use Thumb-2 in cases where difference in binary size is more significant than just a few kB.

[MENTION=5840412]ace2nutzer[/MENTION], a few more tests results, added almost all flags I was using before:

ARM -O2

THUMB -O2

ARM -O3

THUMB -O3

P.s. some flags aren't shown by benchmark, in all the tests additionally were applied flags below:

Some interesting points: using LTO has great impact on resulting size of binary: for -O2 both ARM and THUMB modes benchmark size is 17848 bytes, though seems that LTO has no impact on performance in this case. For -O3 ARM binary size is 34232 and for THUMB 30136 bytes. As can be seen -O3 -marm gives a better result here. -funroll-loops increases speed for about 100-130 points, the rest flags (-funsafe-loop-optimizations, -ffast-math etc) seems not to have any impact.

UPD. On other hand...

Two more tests with GCC 5.2 from Linaro:

Thumb -O3

ARM -O3

This is a totally different result than in case with GCC 5.3! Even though results are not as good as in case with GCC 5.3, this is exactly the case when Thumb-2 outperformed ARM mode (sizes of ARM and THUMB binaries are 33 and 27 kBs, respectively). Nope, somehow reason lies in -O3 itself. When I compiled with -O2, I got 4476 and 4164 points, for ARM and THUMB, respectively.

The fun thing is: than more different optimizations sets I'm testing the more unpredictable results it shows :)
[Galaxy Ace II Android Development] Dr360r:
Build 160510 uploaded/compiled bad. File size 133.6 MB.

No. It means the power button is either dirty or defective.
[Galaxy Ace II Android Development] Dr360r:
If only Samsung had you guys as coders...

[MENTION=5840412]ace2nutzer[/MENTION] [MENTION=7332124]beardedpanda[/MENTION] On build 160510, Poweramp installs, Sound Recorder works (not with WAV though) and Amazon pictures still don't show up.
[Galaxy Ace II Android Development] beastuct:
There are 4647+ comments, it is indicated below everyones name. Anyway does anyone know how to change max quality in youtube? (like from 360p to at least 480p) and why do the touch buttons keep blinking occassionally when device is locked? My thought is that it's for the notifications, right? Can I change the duration-the way it's blinking or to turn this off? Thanks:cowboy:
[Galaxy Ace II Android Development] beardedpanda:
They're blinking for notifications. You can disable it in NT app -> Advanced menu.

If I remeber right, you can't change the video quality in official YT app and there no exceptions.

Wysłane z mojego GT-I8160 przy użyciu Tapatalka
[Galaxy Ace II Android Development] Culateralligator:
@up

Just use OGYouTube 4.4.1.1. Though it's an old version, it allows reproducing with 480p.
[Galaxy Ace II Android Development] beardedpanda:
[MENTION=5840412]ace2nutzer[/MENTION]

I will test now that build. ;)

On 160509 I experience some apps issues (Taptalk and stock browser start to FC variously) rest of my installed appa work normally .

I asking, because I'm just curious. I had a problems with Power button long time ago (long before the stable 13/03 ROM). My phone resets randomly and when I just touch that button it will bring me Power menu (with shutdown, reboot etc. options). I fixed that by simply hitting gently a wooden windowsill with my phone. (that part with the Power button) and I dropped it from bed two times. Now, it's work flawlessly. :laugh::victory::p

BTW: I glued plastic cover from original charger (that one with upwards arrow on it), few days ago. The plug inside it, is holded by only two plastic "hooks".
[Galaxy Ace II Android Development] IAmLucky:
browser version of youtube is actually identical, except its not as native as youtube app, but all design is just the same, i have uninstalled youtube.
[Galaxy Ace II Android Development] beardedpanda:
[MENTION=5840412]ace2nutzer[/MENTION] [MENTION=6902149]Dr360r[/MENTION]

Instagram videos still not working.

About webp: In 20160510 build I see that images in Google Images shows normally in stock browser. I also observe less glitching in the area below input box (see attachment) when doing the search on Google web site.

On builds before 20160510 they're glitched like Amazon pictures.

Wysłane z mojego GT-I8160 przy użyciu Tapatalka
[Galaxy Ace II Android Development] dimon130:
Flash cm11-20160510-UNOFFICIAL-Codina

About phone - Android security patch level February 1, 2016 This is a bug or ...
[Galaxy Ace II Android Development] Dr360r:
Normal. A patch that simply makes it say "1 May 2016" was removed.
[Galaxy Ace II Android Development] ace2nutzer:
Thank u guys for all the reports for latest build !

Latest Build is compiled with default AOSP Flags ... so far this Variant shows up the smallest Amount of bugs ... even if i can't understand this .. because there are by default some very aggressive optimizations enabled, that usually can hurt code quality.

I'm for now completely out of new ideas on how to optimize to the max without to breaks the Code.

It seems like we already found out, that the ROM Code is very dirty coded by Google or CM team or what ever other external developers from "android_external" repos ... such as ffmpeg; webp and so on ...

On kernel-side i was able very quickly to find out the best possible set of flags without to running into that much problems like the ROM here.

The Biggest problem is not only the bad code quality, but it's the very long compilation time .... this makes it almost impossible to find out best possible + 100% working.

I'm rebuilding that CM11 since around 4 months .. almost day + night ... (yes i'm not employed too) and now i came to the conclusion that it's better to only make very low modifications in order to not risk again a broken build.

btw: even not worth it to mention about using a different GCC Version.

So i'll try now the last very small set of optimizations, and let us hope everything will work like that 10.05. build from today :)

If not, i'll rebuild again, and then only with fail-safe + ARM + LTO .. and nothing more .... maybe better ...

I'm simply tired to rebuild same ROM since months ... anyway it was not useless at all ! I've learned a lot of useful things ! :)
[Galaxy Ace II Android Development] Dr360r:
Oh, i understand it must be awful :( . I'm sorry.

That's how life works. You understand and learn more and more every day.

By the way i think the original goal was reached. A flagship-like experience on the Ace 2. More or less optimized, but since February the phone is definitely flagship like.
[Galaxy Ace II Android Development] ace2nutzer:
Yes.. but ... ;)

btw: i've actually time to write this post, because Build Server is actually Down !

But i think it's again due of that very bad internet connection from Indonesia. ;)

As for ROM optimizations: At least all other optimizations for build.prop + Java, works properly.

But wait, this is not all ;) I think i'm still able to make it even better :)

LCD Driver optimization is still missing. :)
[Galaxy Ace II Android Development] ace2nutzer:
btw latest changelog for ROM ... just to keep things in the proper order:

20160510 ROM:

Fixed poweramp installation

Compiled with stock AOSP Code Optimizations

Server is still down :(
[Galaxy Ace II Android Development] greeceeeee:
I made a fresh install of 20160510 ROM with open gapps pico 20160223(this version is lighter than hdpi mini gapps) and it is smoother and faster than ever!
[Galaxy Ace II Android Development] shaqman89:
Ouch, I'm sorry to hear about your condition [MENTION=5840412]ace2nutzer[/MENTION]. Hopefully things will go for the best.

As for the goal, I do agree with [MENTION=6902149]Dr360r[/MENTION]. Multitasking is now better indeed, and the phone is responsive as ever to the point that I don't rely my laptop that much anymore to do some routine tasks. So for that, cheers ;)

Ps: it's actually quite a surprise how much things could be optimized from such a low priced phone. :good:

Lol. Unfortunately, this time we could safely blame Microsoft and it's decision on deciding when best to restart the server after an update. I admit, haven't restarted the host for like a a month now, so updates happened.

On a side note, I was experimenting with Linux server the other day, and found it to be simpler when it's configured right. I do miss the configuration tools, but when it's all in place, it runs smoothly :D

Anyway, the server should be accessible now.
[Galaxy Ace II Android Development] ace2nutzer:
It has nothing to do with the price of the phone.

Theoretically u can optimize every phone the same way.

Linux kernel + ROM is almost same on every Android Phone.

btw: last days i had an opportunity to have an very old Android phone in my hands ...

There is running Stock ROM GB 2.3.6

with an very old kernel version .. too .. smthg 2.6.x or so ...

Funny thing: only 128MB RAM lol

It was running really slow... but after booting to recovery and doing so an wipe data .. later it worked nearly as fast like our Phone here !! Now imagine to flash optimized kernel + ROM ... then it's really fast. But of course not very convenient .. due of too low ram...

there i would enable zram with 64MB lol .. better as nothing. Such phones is still good for old people they only need to use the phone for calls, Photos, music and whatzapp. Unfortunately i didn't checked CPU type .. but probably only old ARM single-core ;)

btw: i really low ARM processors.. they are simply efficient... very fast and good powersaving .. as we can see, even on very old phones u can can buy used, probably for 5 - 10 € lol ;)

So compared such very old phone to our ace 2 here ... then the ace2 is still really good. In my eyes not a low-end phone ! :)
[Galaxy Ace II Android Development] camd1123:
Phone, Mobile connection and Airplane mode error?

Please help me!

-My Mobile connection icon shows no signal, but still the provider's name.

-com.android.phone just keep crashing. I searched Google, they said it was Samsung devices fault, and I did what they tell to fix it (wipe Phone data, Contacts data) but it didn't work. :crying::crying:

-Airplane mode just keep turning ON and OFF itself. T.T As it does, com.android.phone crashes.

I reinstalled ROM, tried new ones, reseted to Factory settings, reboot many times, tried new SIM card.. but nothing fixes these. :crying::crying:

These started in the first time I install a CM ROM, I went through 2 CM ROMS until now (last one is from this post) and these faults still here. :crying::crying::crying:
[Galaxy Ace II Android Development] Dr360r:
A little OT, but funny nevertheless: as i was cleaning my phone i noticed that the battery i bought back in July was bloated. If you put it flat on the floor and rotate it, it spins a lot. I exchanged it with the old one it replaced (i kept it charged even if i didn't use it for about a year) and it's working fine...
[Galaxy Ace II Android Development] beardedpanda:
So far the May builds (except 13/03) are the best. Everything work OK on them.

[MENTION=5713849]camd1123[/MENTION]

First try:

Remove the google account from Settings and In the CWM recovery do:

1. Wipe cache

2. Wipe dalvik cache

3. Fix permissons

4. Reboot to system

If that doesn't work, please follow manual from HERE and follow the steps from Bricking and unbricking section.

Be aware!

following this steps is euqal with losing your data.
[Galaxy Ace II Android Development] shaqman89:
I love this mindset :D

And besides, why throw it away if it's still fulfills our current need, right?
[Galaxy Ace II Android Development] camd1123:
Umm... How can I "Fix Permissions"? :crying::crying: I stupidly wiped the two caches then realize that. :crying: And I also don't understand the thing you said about the Bricking steps from the manual. My phone didn't have any behave like that, but should I just do the steps?

Update: I used TWRP for "Fix Permissions" option, i used it and now my phone my kinda dead, stuck on "Samsung GT-I8160"... TT.TT Im going on the "Bricking" steps now.
[Galaxy Ace II Android Development] beardedpanda:
Flash the older recovery (temporary one - temp_CWM...) from dev host (link to the dev host with older builds and temporary recovery are in the first post of this topic). When you have that temp recovery flashed, go to the Advanced and do Fix permissons and wait until it end . Before doing that do wipe cache and dalvik cache. Then reboot to system. Say No for prevent flashing the stock recovery (I suppose you have a CWM recovery from ace2nutzer kernel) and say Yes for fixing root. ;)

Even if your phone doesn't behave like in that chapter, you should do that steps. I do some research about your problem and people recommend to reflash the ROM.

If you flash with Bricking and unbricking guide (I think you have a Ace 2 not other phone) then you got everything clean and your phone will be like stock one.

You flash any reaprtion files?
[Galaxy Ace II Android Development] camd1123:
I did the Brick fix, and it is now on "Russian Stock ROM"

I accidentally Bricked it and now it is on Stock ROM after steps. Can you help me with the country CSC step? I downloaded the ENC2 filefrom Samfirm but I dont know how to install it. And, from this stock ROM, can I start installing COOK ROM like I did the first time? Do I need to root and install recovery again?

*Thank you for spending so much time for me. I own you a lot.
[Galaxy Ace II Android Development] beardedpanda:
What about that CSC step? You only have to Google which CSC for your Country represent an Unbranded (ROM without any Operator bloatware) one and put it in SAMFIRM, check the automatically encryption option and check option for checking the CRC 32 error (If that option still there) and in the end download the ROM. ;)

You now have a coded file. In SAMFIRM there is an option to Encode files. Please Encode that downloaded firmware and flash it with ODIN like one file ROM. After encoding you should have a .zip file if I remember right. Then unpack that .zip and inside it you should find a tar.md5 file. Flash that file with ODIN like I said above.

First of all, you must flash that downloaded ROM from SAMFIRM before moving to the custom ROMs. Yes, you need to root and install recovery again.

I recommend you to using ace2nutzer ROM and kernel if your phone is a Ace 2 ;) This ROM and kernel for now it is the best option. ;) When you decide to install ace2nutzer ROM and kernel you don't need to root the phone. This ROM is prerooted.

All installation steps you find in the Manual or in the first post of this thread. ;)
[Galaxy Ace II Android Development] ace2nutzer:
btw for now 10.05. is for daily usage.

And for now started again to build test builds .. i simply can't accept to build the whole rom only with -Os ... this is somehow to low optimized ;) That means 11.05 is actually compiling ... that coming build + other newer builds, are for now only for testing if poweramp + sound recorder app will work fine ... please don't use them for daily usage .. as they cause randomly FC.

I'm very busy for now ... so pls test those test-builds [MENTION=6902149]Dr360r[/MENTION] and [MENTION=7332124]beardedpanda[/MENTION]

Thank u very much my dear Friends ;)
[Galaxy Ace II Android Development] Dr360r:
Glad to be of help with turning the Ace 2 into a decent phone.
[Galaxy Ace II Android Development] lotrzyk0:
[MENTION=5840412]ace2nutzer[/MENTION] is it possible to build more and more performanced/lite ROM/kernel? I am wondering if you already achieved maximum from our device. And 2nd question. Can be something done to decrease delay between click on app and response (moment when it starts) ?
[Galaxy Ace II Android Development] seanmalto:
Hey, glad to find this post.

BTW where is the step (if i want to repart my internal storage) take place?

thanks

Oh, one more question

which one is better? 20160510 or 20160511 build?
[Galaxy Ace II Android Development] beardedpanda:
I don't post it. Use files from HERE or search, Google for more repartitions.

For installation method head to the first post or the manual. ;)
[Galaxy Ace II Android Development] Dr360r:
160511: Poweramp not installing. Sound Recorder working. Amazon pics not showing up.
[Galaxy Ace II Android Development] IAmLucky:
well, it is possible to max everything out, but as you can see some optimisationz gives a lot of problems/fcs and other stuff which will stop working. So ace2nutzer is looking to find the best combination for rom to be STABLE + FAST. And run everything with no problems. Also for that delay, have you tried to lower animation speed in developer options??
[Galaxy Ace II Android Development] ace2nutzer:
again and again .. only versions from file "latest" ... or just what u see in the thread name ;)

ok thx ! starting next test ....

btw only check poweramp + sound recorder .. other things are not affected for now. ;)
[Galaxy Ace II Android Development] Dr360r:
BTW can you make something in order for Sound Recorder to not crash when trying to record a WAV file?
[Galaxy Ace II Android Development] ace2nutzer:
Most likely it's not supported by our Hardware....

WAV support is disabled by default:

https://github.com/CyanogenMod/andr...android/soundrecorder/SoundRecorder.java#L388

i've enabled it now ... just testing ....

See also Commit Message:

https://github.com/CyanogenMod/andr...mmit/373a21923742c41007b7dc91064e43a59f3fa46d
[Galaxy Ace II Android Development] beardedpanda:
[MENTION=5840412]ace2nutzer[/MENTION] [MENTION=6902149]Dr360r[/MENTION]

I've got a question: If I use THIS guide to build a webp.so and I copy it to system/libs and gives to it 644 chmod, it should work (or not) normally? I want to test that lib finally and maybe I find something useful for you. Later I move to Linux for compiling and etc.

BTW: I prepared the unsued but connected HDD for installing Linux (Ubuntu 16.04 LTS) for better Android support and to start learning this system. Any advices or information (like for a newbie but in short form) for that "projects"?

BTW 2: I will back for testing (in a full-time) at the end of the next week. Now I have an exams marathon on my academy. Brace yourself! Exams are coming! [emoji14]
[Galaxy Ace II Android Development] ace2nutzer:
Do it ! If it's not painfully to build it for u.

But i doubt that it'll work at all :)

As i was told to u, u can only build it with other android sources too....

Check original cm repo.. And then try to see the difference
[Galaxy Ace II Android Development] beardedpanda:
[MENTION=6902149]Dr360r[/MENTION]

I will try to do my best. ;)

BTW: On 20160510 build: Sending videos in Instagram app works if video is send through the private messages.

It doesn't work if I uploaded it for public. (Tested on mobile data connection)

Later I do more tests.

Wysłane z mojego GT-I8160 przy użyciu Tapatalka
[Galaxy Ace II Android Development] happyrik:
Hi Ace2nutzer

after a period with light rom stock I went back to the CM11 - 10/05/2016 with your latest kernel.

I do not use gapps and operation is impressive.... I would say another phone.

Thank you.
[Galaxy Ace II Android Development] Dr360r:
Yes, all it took was some optimizations, a major debloat of the code, updated CM11 sources and a top notch kernel. Now it's a flagship phone, thanks to everyone that contributed to the project.

[MENTION=5840412]ace2nutzer[/MENTION] I had to install the Odina kernel. I notice that the Odin kernel in your Dev Host doesn't work. I put the phone in download mode, i connect it to the computer, i extract the md5 file from the zip and put it in PDA (Odin 3.07) then start. It locks up at SMDDownload.. then Complete(Write) operation failed. Chronomonochrome's Odin kernel flashes successfully though.
[Galaxy Ace II Android Development] ace2nutzer:
@up

Are u testing latest build ? (Same date)
[Galaxy Ace II Android Development] Dr360r:
Huh? What do you mean? I'm downloading it from dev host (i corrected the post above...). The ROM is 160504. Kernel is 160507...
[Galaxy Ace II Android Development] ace2nutzer:
Nope, flash my odin kernel without to unzip.

Also there is new 11.05 rom for testing poweramp sound recorder also wav ... ;)

Btw don't forget to flash cwm kernel again after odin kernel... Because of missing modules.
[Galaxy Ace II Android Development] Dr360r:
Tested. Poweramp doesn't install. Sound recorder works with AMR and 3GPP, but crashes with WAV.

And you're right. Don't unzip the Odin kernel. Just put the zip in the PDA field. It installs now.
[Galaxy Ace II Android Development] ace2nutzer:
Thanks, but just to make sure,... Yesterday late on 23:00h i've started new compilation.

That means u was testing the first 11.05 ... And now u tested the second 11.05 ? I'm right ?
[Galaxy Ace II Android Development] Dr360r:
Yes. I downloaded it some minutes ago. The one that says 01:58.

The WAV stuff is strange. I bought a recorder app and i can record in WAV 44KHz just fine.