yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] Andrewbons:
I can't flash this kernel with odin, it failed. I've tried installing an older version of Rox but still blackscreen issue (but i didn't have it before installing chronokernel).

When i can't enter on recovery after lots of attempts, the only thing to do is flashing stock firmware or leaving it with a blackscreen lol

It's the same story all the time:

1)I flash stock firmware

2) I try to enter on stock recovery (few attemps, few minutes)

3) I install temporary CWM and i have to be lucky to enter on CWM or i have to go back to 2)

4) I install whatever i want XD

It all started with the first ChronoKernel version, we should start from that i think.
[Galaxy Ace II Android Development] S.AMU:
[MENTION=5840412]ace2nutzer[/MENTION]

In op you wrote that your kernel has full bln support. Does it mean that bln makes it own wakelock and that bln is working correctly even with the normal BL turned off?

Also waiting for kernel with f2fs support on data and cache
[Galaxy Ace II Android Development] BastiZ:
No its not. :)

I tryed to make a modul for Chronokernel.

But first, Chono isn't that battery friendly as StockTC and 2nd I have no idea how to do it :D
[Galaxy Ace II Android Development] ace2nutzer:
U are probably a noob XD U can't flash a .zip or a boot.img with odin.. u need to convert it first with linux.. rename md5 ... etc..

I've those "rescue" Kernel always here.. even on dev-host... for users like u .. with black screen issue.. related to s6d Driver... check in my dev-host for ODIN_kernel.tar .....

AGAIN: I NEVER had Blackscreen with all CWM Versions.. even on latest Build from Rox.

Therefore it's Your Problem.. and not mine.. and please keep in mind that i do it all for free... it's my freetime :) :o

U can noboby force here to make something for u.. the Sources are all on GitHub ..Everybody can download it for free and what u need to do is just compiling ! :highfive:

EDIT:

[MENTION=5382590]S.AMU[/MENTION]

Yes it need one app that activate wakelock.. and disable Wakelok when screen is ON.. clearly that works only with TASKER...

Thanks, I'll edit the Text. and perhaps add one of my TASKER Config Files.. or just refer to your How-To with TASKER. :)

But it have the another Driver with Blink... but don't worry.. u can use simple command from Tasker for normal Backlight on and off.. so without blinks... it works with both ! it's very nice... at this way.. it's not needed to write complicated scripts to generate blinks :) ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
[MENTION=5840412]ace2nutzer[/MENTION], I'm still waiting for F2FS version :D if you've any doubts about that, you can simply PM me :highfive: about F2FS support on /system - it still has side bug - if random reboot happen, it will boot into recovery(that caused by temporary workaround - compiling param.ko built-in to avoid some problems with loading it at boot).

I agree :D I'll move some my changes from ZenX to Interactive - since now it's practically same :)
[Galaxy Ace II Android Development] kjub6:
van you look on CrystalPA 7.05 - Android 4.4.4 - CRX Team ... have installed this theme and they have pimped the resolution is bigger and the device has a SUPERB touch dont know where or how to pimp it in your Rom ... can you help me ? icons notification bars everything is smaller and you have more room on screen is awesome have not came across it before

I dont use it cause it has no exFAT support :/ and moving apps to FAT32 SD is slowing it down
[Galaxy Ace II Android Development] S.AMU:
Oh, that's sad. Why is there no ROM and kernel which has correct BLN?
[Galaxy Ace II Android Development] ace2nutzer:
I really don't know S.AMU .. probably due to time... one day we will develop it right :D But not really needed.. with Tasker it works like a charm! Because u, or better i need anyway tasker for many other things :D
[Galaxy Ace II Android Development] lars85destroyer:
Why no zRam and KSM ?

And do I need to remove nt app ?
[Galaxy Ace II Android Development] ace2nutzer:
If u don't have Problems with stability, u can let it.

For Mobile Devices it' s better a real clean ram without compression., That will save Battery.

But for PC / Laptops with poor Ram, zRam and KSM will help to avoid to use the slowly HDD for Swap.
[Galaxy Ace II Android Development] lars85destroyer:
No problem for the moment, I won't touch it ^^

Oh I didn't know that ! All was enabled on my last configuration :')

But after 2 hours of use, I can see that WiFi + screen on drains so much battery ...
[Galaxy Ace II Android Development] MarquesYOLO:
3-4 hours after flashing kernel and no problems occurred. First custom kernel without reboots. Thanks [MENTION=5840412]ace2nutzer[/MENTION]

Enviado desde mi GT-I8160 usando Tapatalk 2
[Galaxy Ace II Android Development] INFERNO777:
[MENTION=5840412]ace2nutzer[/MENTION] you plan to do a kernel for 4.1.2 ?
[Galaxy Ace II Android Development] supachris:
Codinap rom and kernel works very well, I do not see any issue until now, and the phone is absolutely smooth with nova launcher. Great thanks to [MENTION=5840412]ace2nutzer[/MENTION].

Can you build an odin version for codinap too? For emergency
[Galaxy Ace II Android Development] BlueZ-:
Is it possible to set screen off freqs?
[Galaxy Ace II Android Development] darorsa:
up @ ace2nutzer

Do you issue kernel versions 4.1.2 STOCK ROM?
[Galaxy Ace II Android Development] biggstreet:
firstly : thank you for this kernel

will you make a bluid for stock rom 4.1.2 ?
[Galaxy Ace II Android Development] str3tch72:
[MENTION=5840412]ace2nutzer[/MENTION]

Can I flash Your ROM and kernel without full wipe?
[Galaxy Ace II Android Development] pijen:
If I want to use F2FS, what is minimum size for /cache? I swapped /sdcard0 and /sdcard1 too

currently my /cache is ~30MB with 2,7GB on /data and 190MB on /sdcard0

/system is in default size (600MB)

Thanks
[Galaxy Ace II Android Development] fluffi444:
130mb for Cache.

Gesendet von meinem GT-I8160P mit Tapatalk 2
[Galaxy Ace II Android Development] mej69:
I also want to use F2FS (actually ext4) and follow the instructions in Post #3.

But when I restore my backup, I get an error "Error in restoring /system".

Is it necessary to repartition NAND-flash before change FS? Or is there something else, what I have to do before changing FS?
[Galaxy Ace II Android Development] kjub6:
download

kernel f2fs and rom f2fs install kernel re-install format /system /data /cache and install rom ;) its easier and all data you will need to install anyway :)

[MENTION=5840412]ace2nutzer[/MENTION] are you sure that pimping up voltage to 900 is not shortening the life of battery ? my default was 600mA and ... and the USB is by default only one value I am able to change

the pimps in Carbon are way better than in TC11 that is true ... :/ the new locksscreen, carbon fibers are perfect.

shame is not working on f2fs ...
[Galaxy Ace II Android Development] doctormord:
Well, that's what I did. Switching to ART automatically deletes Cache as well.

Df is attached.

Regards.
[Galaxy Ace II Android Development] ace2nutzer:
u should to repart... u have too less space free on system and data.. actually u've 1 Gb used on data.. after F2FS + ART u've used: 1,4 - 1,55 GB !
[Galaxy Ace II Android Development] mej69:
I'm back on ext4 because I'm not sure to restore a cwm backup (on ext4) on f2fs-FS?!
[Galaxy Ace II Android Development] shaqman89:
[MENTION=5840412]ace2nutzer[/MENTION]

I like your kernel so far, but I've run into some issues that I think is quite bad. Whenever I am multitasking really heavily, let's say moving back and forth between 7-8 application, the phone just hangs and then reboots itself. This itself is okay for me, but what is not okay is after the reboot, my WiFi can't be used k grayed out).

Here is the last kmsg if you want to see into it: https://docs.google.com/file/d/0Bzo3MSxg_YFCSFo3ZnZWeWFuRkU/edit?usp=docslist_api

I am using your last f2fs update.

Great job, Btw :)
[Galaxy Ace II Android Development] nikolas1274:
How many free space do we need in system, data & cache for switching to art
[Galaxy Ace II Android Development] Vexylle:
Should I reinstal the gapps if I switch to ART? because I get force close all the time:/
[Galaxy Ace II Android Development] acrocosm:
For ext4 no you dont need to. You just switch to ART and it should rebuild the cache on reboot and you are set. It should be the same with f2fs as long as you have enough space for your apps and cache (both ART and f2FS)
[Galaxy Ace II Android Development] surfboardcm:
2 day running the ext4 11/18 and everything working fine. i can now see youtube videos... and filming...

thanks for your hard work.
[Galaxy Ace II Android Development] Vexylle:
thx, I'll see, but somehow it's a bit slower for me than dalvik, dunno maybe I'll do a clean instal
[Galaxy Ace II Android Development] ace2nutzer:
When u get error on restoring from ext @ f2fs.. then u don't have enough free space on system.. you must format it first in f2fs..

If u get anyway error.. then u need to repart.. follow post #3.

Thnx for the Log..

It's not normal.. i'll check the log.. but i think due to CPU voltages.... :-S Do u've overclocked ?? more than 1Ghz ?

This is normal !!! ART is fully optimized after 2 - 3 Days ! I can suggest to open 1 x all your apps.. and then reboot the Phone... also it's good when u reboot the Phone 2 x per day in the first 2 - 3 Days.. then ART is fully optimized.

For me it was the same.. ALL Apps was slower with ART.. but now it's incredible Fast !!
[Galaxy Ace II Android Development] shaqman89:
Yeah, I did. If I remember it correctly at that time I was using this configuration:

Interactive 200/1000

I/O: SIOPlus

GPU: 700 (could this be the cause? Due to the fact that I think it's more of a memory management issue, I haven't changed this configuration )

ART/F2FS

Additionally, I tried frequency more then 1200 and too bad I could use only 1300 with some reboots :p

Currently I am using 1050 and so far it's good.
[Galaxy Ace II Android Development] ChronoMonochrome:
Are you using just static 700 MHz clock? It may work unstable than 400/700 MHz.
[Galaxy Ace II Android Development] shaqman89:
Yes, I was using it static 700MHz.

I will try it with 400/700 and see if it still happens.
[Galaxy Ace II Android Development] ace2nutzer:
Yes then it's caused on OC.. GPU 700Mhz is very High.. but 1Ghz on cpu should work stable for all... if not u need to report me.

Default GPU is 400Mhz.. and GPU 500Mhz should work 100% stable.

btw: @ all :

what about the stability on this last kernel ??

U can compare the stability with the same freq. on other Builds from me.. but also on Chrono Kernel and Stock TC Kernel... if u feel on latest build here is less stability the any other Builds / kernel.. then report.. then i can improve the Stability by increasing the Voltages.. but that also will drain a little more battery.. that's normal. :)

Also all about Blackscreen after waking up the Phone over home / power button !

Therefore Guys.. i need some Reports .. then i can update Voltages.. and make new Build !!
[Galaxy Ace II Android Development] ChronoMonochrome:
Finally found time to test your kernel. So far it works good and smooth. :) Will report later. :)
[Galaxy Ace II Android Development] shaqman89:
I agree, it is very high XD

Normally, I do use it 400/480 but I was wondering whether it would be stable or not. *grin*

Now I've changed it to be 400/640.

I've only been using your 19/11 f2fs kernel so I couldn't compare it with before, but comparing with chrono's 2.6 version, yours is stable and fast. I had reboots when I was using frequency bigger than 1000 at that time with chrono's, but with yours I could use 1100 fine :)

One thing that I like more in chrono's kernel is the boot time. With chrono's kernel, my boot time is 8080 but with yours it's 8277. Not big of a difference, but it means there's still room to improve :D

Also, with chrono's kernel, I have 628 of RAM, while yours is 627. No big deal though.

Other than that and the reboot issue when I am heavily multitasking, it's working great and smooth :)

Update : With the exception of when I am heavily multitasking (only found it twice in the week I am using it), no black screen issues here so far. :D
[Galaxy Ace II Android Development] IAmLucky:
well, when i formated modemfs, i couldnt get data connections. Calls, messages were working.
[Galaxy Ace II Android Development] Dr360r:
Another build is up. What to expect this time?
[Galaxy Ace II Android Development] ace2nutzer:
Just testing .... u don't need to test actually ... i'm changing optimizations completely .. because old ones did broke too many things :)
[Galaxy Ace II Android Development] Dr360r:
Is it working better now?
[Galaxy Ace II Android Development] ace2nutzer:
it should ... at least theoretically ... because of more cleaner Code :)

it was a test with GCC 4.9 but with new optimizations (only fail-safe) ... and so far everything worked fine except of Camera FC when switching from Foto to Video.

And because i didn't applied an specific patch for GCC 4.9 , there was Google Play Services FC like hell ^^ .. but this is not the main problem.

Now deleted that GCC Version one time fore ever ;)

Actually it's compiling with GCC 4.8 ... i hope everything will work fine, if so i can add some more optimizations (only fail-safe).

U can test this build if u want with the usual set of critical Apps for FC ;)

I'll test as well of course :)

Remember:

Builds for daily usage only those that are mentioned in "latest" File in the root of FTP Server :)

All other Builds, are only for testing purposes and they will be deleted after some time :)
[Galaxy Ace II Android Development] Dr360r:
Last build: Browser fatally crashes. Google Play Services FCed once. Google Maps and Camera working fine, no java crashes.
[Galaxy Ace II Android Development] ace2nutzer:
New Kernel is out !!!

Changelog:

20160325:

Adjusted some more Brightness Values

Decreased Brightness on CM boot-logo

Disabled DT2W for LPM (caused random reboots)

Re-enabled Logcat + last_kmsg features ;)

Full reworked binary code optimizations

More Clean + Stable Code

Compiled with latest AOSP GCC 4.8 (orig. Google Toolchain)

Userspace RAM: 629 @ 630MB :D
[Galaxy Ace II Android Development] Yønn:
Latest kernel is 1MB lighter than previous ones (almost 10%)!

Is this related to new GCC 4.8 compilation or binary code optimizations?
[Galaxy Ace II Android Development] ace2nutzer:
Both together :)

But the Most impact comes from binary code optimizations ... Kernel is compiled now with -O2 instead -O3.

Also i've removed almost all non-standard optimizations which are not included on any optimizations level.

And i think it's not only 1MB difference .. it's probably even more ... because i've re-enabled at the same time android_logger + android_ram_console ... which increases kernel size of approx +1MB ..... but i don't remember exactly how much it's ... but maybe [MENTION=5695278]ChronoMonochrome[/MENTION] u remember ??

btw: this is the Commit of changed binary code optimizations:

https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/70077a91e767c7ebe40f7b3e3c5b339a8e623d9f
[Galaxy Ace II Android Development] ChronoMonochrome:
Depending on how big logger buffers do you use.

Btw, any reason to use GCC 4.8? I know that kitkat is supposed to be compiled by GCC 4.8 by google, but kernel isn't "android version aware". What is moreover, google has already switched to GCC 4.9 in M.
[Galaxy Ace II Android Development] ace2nutzer:
i switched to the latest armeabi AOSP GCC 4.8:

Reason? :D Because i want to use original Toolchain from Google.

After some Research i found out, that their Toolchain is best for cleanest code + to have max. stability ... rock solid ....

The only drawback is that, it's not tuned to the max, like Linaro, SaberMod, UEBER Toolchains ...

But i prefer to have properly working Toolchain rather than having a bit more performance but introducing some more bugs in the Code ;)

https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/

I don't see there 4.9 armeabi ... I'm missing smthg ? :)

And nope, KitKat wants androideabi GCC 4.7 :)

using 4.8 or 4.9 androideabi results in an completely screwed up build ... randomly occasionally FC for every APP.
[Galaxy Ace II Android Development] Craxor:
i cannot flash the latest rom from jb, showing status 7

my device is i8160 but its saying rom is for cordinap :confused:
[Galaxy Ace II Android Development] ChronoMonochrome:
https://github.com/ChronoMonochrome/android/blob/aosp-6.0/default.xml#L452

GCC 4.9 is a default in google manifest since android 6.0.0.

Btw, I can't say about GCC 4.8 and GCC 4.9, but I don't remember if using GCC 5.2 was causing to me much problems in Vanir kitkat. The only thing is that ART was completely broken and this is only unresolved problem so far. Are these FCs related to your optimizations?
[Galaxy Ace II Android Development] ace2nutzer:
use first temp.cwm fro my dev-host ....

if it'll still show u same error .. then flash first my kernel .... then power off the phone ... and boot to recovery again ... and try again .. it should work then ;)

Yes i know :) i just say using something higher than 4.7 in kitkat gives problems (androideabi) :)

Yes, broken ART, FC for Camera, and not working MAPS ;)

.

Nope, Google Defaults :)
[Galaxy Ace II Android Development] ChronoMonochrome:
So maybe this is something specific to google toolchains? I remember I was having camera FC on my very first unreleased April 2015 CM11 builds when was using GCC 4.9 from google NDK. Can't say about GCC 4.8 since I never was using this google toolchain but rather switched straightforwardly from GCC 4.7(from google) to GCC 5.2 from linaro.
[Galaxy Ace II Android Development] ace2nutzer:
Yes it's toolchain bug itself .. or just incompatibility for CM11 :)

Yeah but did it solved Camera FC with Linaro Gcc 5.2 ?? i think no ;)

U just used probably Camera libs from another working build ..... u know ?

btw i still don't see arm-eabi-4.9 ... :confused::confused::confused:

i cloned this repo to my laptop:

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9

there is only android-eabi-4.9 .... :cyclops:
[Galaxy Ace II Android Development] ChronoMonochrome:
Well, as far as I remember, default (and only) camera was randomly FCing, but e.g. OpenCamera was working properly. I'm still unsure where this bug came from, it also might be not properly applied fix, as lately I found that some part of a fix was missaplied. And nope, I wasn't using a prebuilt camera blobs (except camera.montblanc.so from stock).

Yeah, you're right, I've seem to mixed things up. Google only updated android-eabi toolchain, but not arm-eabi. Though I anyway don't see any reasons to use lower GCC version on kernel - as I previously said kernel isn't that much "aware" of android version, at least on our device, it's not very sensitive to GCC toolchain version(looking on how many devices still have to use GCC 4.8 or lower, we are really lucky that we can use as higher GCC as latest 5.3).
[Galaxy Ace II Android Development] ace2nutzer:
Right now tested again with clean build .. Target_thumb := -Os -mthumb

And it's still force closing when switching from foto to video (sometime). So u're right.. Fix is still not properly applied.. Or maybe i should revert this ?

https://github.com/ace2nutzer/android_frameworks_av/commit/f5f228139752586230dea933359b4057b022a55a

And yes... I've also faced some bugs in the code.. There was even an cm bug... Also i even didn't removed camera extra headers...

Also removed very carefully all mediatek changes by hand... Then applied the multimedia fix from rox.

As for gcc for kernel, u're right ... Every gcc version works fine.... Even self-compiled with linux headers instead android headers xD.

For now i'll stick to the latest eabi aosp gcc 4.8 ... Unless i'm 100% sure that using any 3rd-party toolchain is really better than the original from Google.

For sure following toolchains are very interesting:

Linaro

SaberMod

UEBER

Need to read more informations about such optimized toolchains if they are NOT more buggy than AOSP ones.

Btw build 26/03 is up !!

Updated sources...

Stable version

Normal optimized

So more speed will come soon .. ;)

Also tried to apply Fix for ChromeCast .. but it seems that it's not just one line of code... There are just too much differences between fixef cm-13.0 and our branch cm-11.0.

So we've to wait until cm team will fix cm-11.0 branch too.

Edit:

After some deeper research i came To the conclusion that using aosp google toolchains is best :)
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't remember whether or not it was causing any problems in kitkat, but in lollipop and higher android it works without causing camera to FC.

It seems to be properly applied. On vanir, I missed camera parameters definitions such as https://github.com/ace2nutzer/andro...cd7#diff-e21ab572623e6703810808957ab74d31R346 , thus default camera was being confused about that :D . But the rest camera apps seemed to be fine without these definitions . Try to capture logcat or test different camera apps.

Lol, I have to admit that I have gotten a different experience. Google toolchains often were causing for me an internal compiler errors (so-called "ICEs"), due to optimizations used. Though I agree about not using an "Hyper", "Extra", "Hybrid" or whatsoever "Super" toolchains from 3rd party before making sure that it makes any sense. For me linaro was an obvious choice, though probably SaberMod and Uber is good choice, but I haven't read about those ones.
[Galaxy Ace II Android Development] Sylvinette:
[MENTION=5840412]ace2nutzer[/MENTION] I've problem with storage for installing some apps, only got 1.1 gb on stock reparted. Is there any good flashable zip for more storage?
[Galaxy Ace II Android Development] Dr360r:
For c u later alligator: swipe is still not working in latest build.

[MENTION=5840412]ace2nutzer[/MENTION] : what have you done to the gps in latest build? I saw you added the ro.ril.def.agps.mode=1 and ro.ril.def.agps.feature=1 tags to the build.prop but it no longer saves agps data in/root/data/gps. I removed them and rebooted, nothing changed. I added them in the last section and in inverted order and rebooted again but phone still doesn't download agps data (and gps lock is much slower...). So i went back to 160313 for now. I found that even if i remove the tags and delete the AGPS data GPS is still downloading AGPS data everytime you connect to the internet.

Could you possibly revert it to how things were with 160313, and let us edit the build.prop instead?
[Galaxy Ace II Android Development] Tree4ever:
[MENTION=5840412]ace2nutzer[/MENTION],

should Rom 03.26 +03.25 kernel be as stable as Rom 03.13 +03.25 kernel?Do you recommend NT 1.7.1 or 1.7.2?
[Galaxy Ace II Android Development] IAmLucky:
newier is always better haha. But talking about ROM currently 16/03/13 is the most stable one (but you cant use xposed installer with this rom, framework cant be installed)