yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] RovG:
So it appears that there are 3 ways to invoke trim. Summarised from: http://askubuntu.com/questions/18903/how-to-enable-trim/19480#19480

•Automatic

By setting the discard flag when mounting. Drawback to this appears to be a performance overhead.

•Manual/On demand

User issues fstrim command from command line. Cumbersome

•Scheduled

By means of a cron job. Maybe every 24hours. I belive this is what we should strive for.

How does Android 4.3 do it?

From: http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices

"The Android framework will send out a “start idle maintenance window” event that the MountService listens for, and then invokes vold to fstrim filesystems when a few conditions have been met – the device hasn’t been touched for over an hour, no idle maintenance window event has been sent in 24 hours, and the device is either off-charger with 80% battery or on-charger with 30% battery. The goal is to have fstrim run roughly once every 24 hours if you’re in the habit of plugging the device in to charge every night."

And from:

https://community.freescale.com/mob...document?content=/api/core/v2/documents/95556

"How framework triggers fstrim in android4.3?****

Android4.3 introduces a new service IdleMaintenanceService to manage when and how trigger fstrim in right time. Once system satisfies the following conditions, it will send out one "ACTION_IDLE_MAINTENANCE_START" intent which the MountService listens for.

•Last time* "ACTION_IDLE_MAINTENANCE_START" intent has been sent before 24 hours.

•The device is either off-charger with 80% battery or on-charger with 30% battery

•The device can go idle state.

•User don't use it for 71 minutes."
[Galaxy S II Android Development] RovG:
fixing partitions, yes. Each partition/file system has its own LOST.DIR. This is the equivalent of lost+found directory in *nix systems. The

LOST.DIR on sdcard0 contains orphaned file/directory fragments of files or directories that previously existed on sdcard0. It was most likely placed there when e2fsck ran at boot time.

From: http://unix.stackexchange.com/quest...ose-of-the-lostfound-folder-in-linux-and-unix

"If you run*fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular,*fsck*might find data that looks like a complete file but doesn't have a name on the system — an*inodewith no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.If you tell*fsck*to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. Sofsck*deposits the file in a specific directory, called*lost+found*(after*lost and found*property).Files that appear in*lost+found*are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.Files can also appear in*lost+foundbecause the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.On many filesystems, the*lost+founddirectory is a bit special because it preallocates a bit of space for*fsck*to deposit files there. (The space isn't for the file data, which*fsck*leaves in place; it's for the directory entries which*fsckhas to make up.) If you accidentally delete*lost+found, don't re-create it with*mkdir, use*mklost+found*if available."
[Galaxy S II Android Development] jgcaap:
Thanks for listening. I hope we can still improve. =)
[Galaxy S II Android Development] RovG:
[MENTION=4663860]Computoncio[/MENTION], since you asked [emoji16], here is my input:

Automatically fixing partitions/file systems (fs) can be very dangerous. Users without uptodate backups can loose a lot.

I propose that if tune2fs -l or e2fsck without -f detect that the fs is not clean, then we inform the users that "fs is Dirty" and give them 3 options:

1. Boot to recovery so that a back up may be taken

2. Perform e2fsck

3. Ignore file system errors and continue to boot.

If no response is provided in 10 seconds option 3 is executed by default.

If tune2fs -l or e2fsck without -f detect that the fs is clean, then perform e2fsck -nv and if not clean, then we inform the users that "fs is in an inconsistent state" and give them 3 options:

1. Boot to recovery so that a back up may be taken

2. Perform e2fsck -p

3. Ignore file system errors and continue to boot.

If no response is provided in 10 seconds option 3 is executed by default.

Currently, when checking file systems, the boot logo is displayed on the screen. If the boot logo is displayed for a long time(, for me that would be more than 10 to 12 seconds) Users get impatient. It is also is difficult for users to tell if the system is in a start-up loop or just busy checking file systems. So firstly we need some way to keep the users informed of what's going on and its progress.

Regarding clearing of dalvik cache, I think only do this if a grep of the log file indicates that a dalvik cache file was affected.

HTH
[Galaxy S II Android Development] cybernetus:
I will not build more :) [MENTION=4663860]Computoncio[/MENTION] has a updated repository and he builds a public version :)

I will put your updates on my build , thanks :)
[Galaxy S II Android Development] cybernetus:
[MENTION=2376110]dorimanx[/MENTION] merge your updates

but i have a problem with the new recovery.

i build with your recovery and i receive an error o set_perms and the installation is stopped.

I am build now with the dorimanx recovery to see if the problem is the recovery.

---------- Post added at 03:29 AM ---------- Previous post was at 03:09 AM ----------

The same with dorimanx recovery :

set_perm: some changes failed

E:Error : kernel*.zip

(Status 7)

Installation aborted .

When i try with the v105-cybernetus no problems on flash.

---------- Post added at 03:41 AM ---------- Previous post was at 03:29 AM ----------

I believe this is the commit with problem : https://github.com/dorimanx/initramfs3/commit/1ff99d49569ad1f969de920eafbfd761f9a9ac37

I revert all today commits to see where are the problem.

---------- Post added at 03:53 AM ---------- Previous post was at 03:41 AM ----------

No success

I will wait for the other de devs :)
[Galaxy S II Android Development] RovG:
[MENTION=1670821]cybernetus[/MENTION], please can you try again but this time replace the updater binary in your zip with one from CM that works with KitKat.
[Galaxy S II Android Development] cybernetus:
For anyone needs to test, i will publish and v110 with the [MENTION=2376110]dorimanx[/MENTION] last commits in five minutes.

I need to see if the problem is my phone or the problem is with a commit )

---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------

You have a link of this updater ? I will try again with this .

Update: i will get the updater-binary from SpirtROM

---------- Post added at 04:36 AM ---------- Previous post was at 04:13 AM ----------

Changing the updater binary not work.
[Galaxy S II Android Development] RovG:
This is from Gustavo_s' KitKat kernel.
[Galaxy S II Android Development] cybernetus:
Again, the same error ...

---------- Post added at 05:01 AM ---------- Previous post was at 04:51 AM ----------

I publish the v110-cybnt for the branches 9.x and 10.x for a test.

If anyone needs download this on my storage http://dorimanx.ataliba.net

commits

last initramfs: https://github.com/dorimanx/initramfs3/commit/0348574d3cdc684d7b22eb5dfd59c37171a7c8d1

last kernel : https://github.com/dorimanx/Doriman...mmit/e344aef7fd7d3d3a6bb81c7684fd02092066d81e
[Galaxy S II Android Development] cybernetus:
Anyone with a report of the flash ?
[Galaxy S II Android Development] GieltjE:
Testing it since one hour ago, my phone keeps popping up the partition check errors as well with the previous builds.
[Galaxy S II Android Development] Spaulding89:
On my phone v110 flash was OK, boots fine and fast,system runs stable and no errors with partition. Great [MENTION=1670821]cybernetus[/MENTION]
[Galaxy S II Android Development] CHEF-KOCH:
Any process on this partition problem with the recovery? Or a workaround would be nice, it's impossible for me to get more then 2 GB ( I want 4GB) because every time I flash the new kernel it revert the space back. And flash a old kernel + pit + rom is also impossible (status 7 error which was fixed in newer recovery for cm11/kitkat).

Yup, can confirm, first start seems okay.

Edit:

No partition error fix popup on startup, fixed!? I didn't enabled the option to "fix" it on every boot but seems there is no error anymore after I flashed 110.
[Galaxy S II Android Development] Kousthubha Kumar:
I had quite data errors from v108, so decided to do a clean flash, v110 gave a Status 7 Error and didnt flash over stock as well as over v108 kernel. But it flashed successfully over v109 kernel. So I guess v110 can not be flashed directly..
[Galaxy S II Android Development] RovG:
I suspect that there are no partition errors being reported with v110 (it doesn't mean they are not there) because Computoncio' partition check & display in browser is not present in v110. If this is true, then the partition check & fix is forced at boot. This is how DorimanX had it set up previously. [MENTION=1670821]cybernetus[/MENTION] can confirm.
[Galaxy S II Android Development] dorimanx:
i have removed FORCED partition check.

if system report CLEAN on partition, there is no need to FORCE check and bump on journal mess that is OK as is.

we cant fix the multy allocation blocks.

they will be back on each boot.

so now ONLY if you really have errors, you will get report.

I am building new LINARO 2014:04 with new LIBS and new updated linaro compiler :)

Small part of build process LOG

[INFO ] =================================================================

[INFO ] Extracting and patching toolchain components

[EXTRA] Extracting 'linux-3.13'

[EXTRA] Extracting 'gmp-6.0.0a'

[EXTRA] Extracting 'mpfr-3.1.2'

[EXTRA] Extracting 'isl-0.12.2'

[EXTRA] Extracting 'cloog-0.18.1'

[EXTRA] Extracting 'mpc-1.0.2'

[EXTRA] Extracting 'binutils-2.24'

[EXTRA] Extracting 'gcc-linaro-4.8-2014.04'

[EXTRA] Extracting 'eglibc-2_19'

[EXTRA] Extracting 'gdb-7.7'

[EXTRA] Extracting 'ncurses-5.9'

[EXTRA] Extracting 'expat-2.1.0'

DONE!

pushed to all branches! :)

have fun people...

I will add something more next time when my wife ask if there is NEW update for her phone! :)
[Galaxy S II Android Development] cybernetus:
Thanks, i see that.

When i flash over the v105 i have the Status 7 error.

I believe all needs to install the v110 , needs to download the v109 from [MENTION=4663860]Computoncio[/MENTION] , reboot recovery and install the v110-cybnt

thanks for this tip :)
[Galaxy S II Android Development] RovG:
Fstrim.c

https://android.googlesource.com/pl...752b8081eab8318f87f47b97d97205fd14e3/fstrim.c
[Galaxy S II Android Development] dorimanx:
This is rom commit.

Leave the trim alone. In 3.12 tree this function became auto, ni user mess needed. You cant make it work by some binary that no longer have access to controls.

Sent from my LG-D802
[Galaxy S II Android Development] RovG:
How exactly does it work now in this auto mode? How can I check if it is working? I have looked in my logcat but don't see any entries for fstrim or fitrim.

---------- Post added at 08:43 PM ---------- Previous post was at 08:15 PM ----------

[MENTION=2376110]dorimanx[/MENTION], ok I found this:

From: https://lkml.org/lkml/2013/9/3/277

"Queued TRIM support, which enables sending TRIM to the device without draining in-flight RW commands, is added. Currently only enabled for ahci (and likely to stay that way for the foreseeable future)."

I am still not clear that it is enabled for our eMMC devices. How can I check? How can I check that it is working? What should I be looking for in my logcat?
[Galaxy S II Android Development] kkmiott:
Where can I download new Dorimanx build?

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Android Development] dorimanx:
Now our ssd emmc not need and dont support trim.

If you will try to mount data partition with trim, you will see in dmesg log about no support for trim.

As its been deprecated. And replaced with many functions in ext4 driver and in block code.

There was many commits and changes for this.

Its no longer needed, fs is trimmed on the fly if that what you seek to know.

Sent from my LG-D802
[Galaxy S II Android Development] m1trand1r:
hey guys.....just stopping by to say that v110 by [MENTION=1670821]cybernetus[/MENTION] is running fine on my side as of now.....been on v109 by [MENTION=4663860]Computoncio[/MENTION] since released w/o any major issues except my almost dead battery and data corruption on sudden power off of my device....lol....

Thanks devs....[emoji106][emoji106][emoji108][emoji108][emoji122][emoji122][emoji482][emoji482][emoji56]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] infatality:
Am back.. After so long.. No issues with v110! =P
[Galaxy S II Android Development] nuraniharun:
Hi dorimanx, computuncio and cybertenus

We cant wait. When can we flash 8x branche kernel v110 or v111?
[Galaxy S II Android Development] Twiq:
Dorimanx's v100 build is running very sweet since last night ?

Will definitely stick with this build for a while now..

Running 0416 Sabered SlimKat | DorimanX 10.43v108
[Galaxy S II Android Development] silentcontrole:
i don't really think dorimanx's v100 build is the last updated build it's 2014-04-01 build and we are 2014-05-02 :confused:
[Galaxy S II Android Development] Spaulding89:
V110 is the newest at the moment
[Galaxy S II Android Development] m1trand1r:
There's NO v110 or (I don't know where you saw[emoji33][emoji13] )v111.....for 8.x branch.....I guess 8.x branch is dev dead as it can't handle new updates.....I believe that builders have talked about this thing.....so....it's time to move on mate [emoji106][emoji106]

Beam-ed through your pineal gland via//Android 4.4.2.:p//

---------- Post added at 11:00 PM ---------- Previous post was at 10:57 PM ----------

It has music stop bug afaik.....otherwise it was rock stable.....for me....

hm.....why are u confused ?....mate was bored and flashed v100 which is nice apart from music bug:D

[MENTION=2376110]dorimanx[/MENTION]

I hope you're wife will become "update greedy" soon again.....so you'll have something to play with again[emoji106][emoji106][emoji106][emoji106][emoji56][emoji58][emoji56][emoji56][emoji122][emoji122][emoji122]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] cybernetus:
No updates on 8.x branch :)

because this we have no v110 for 8.x branch .

Do you see the message of [MENTION=5074262]StanTRC[/MENTION] ?

http://xdaforums.com/showpost.php?p=52302761&postcount=9081

---------- Post added at 04:06 AM ---------- Previous post was at 04:03 AM ----------

Building a new version with the updates of linaro of [MENTION=2376110]dorimanx[/MENTION]

New version v111 for all branches

---------- Post added at 04:31 AM ---------- Previous post was at 04:06 AM ----------

New v111 for all branches builded using the new linaro commit of [MENTION=2376110]dorimanx[/MENTION]

Kernel_Dorimanx-V10.43v111-cybnt-[23-06]-[02-05]-JB-SGII-PWR-CORE.zip

Kernel_Dorimanx-V9.43v111-cybnt-[23-14]-[02-05]-JB-SGII-PWR-CORE.zip

Kernel_Dorimanx-V8.43v111-cybnt-[23-21]-[02-05]-JB-SGII-PWR-CORE.zip

only one commit in kernel

Update LINARO 2014.04 Custom build for 3.13.y ARM source using latest libs and latest crosstool-ng builder.
[Galaxy S II Android Development] Klaus20:
I have got an error when I try to flash 8.43 v111

set_perm: some changes failed

(Status 7) Installation aborted. (I am coming from V8.43v76)

Somebody has an idea ?
[Galaxy S II Android Development] Paul_Kolanjian:
Same here, the only way I managed to flash successfully is by flashing Comp's 10.43 v109, reboot the recovery when v109 is flashed, install the 8.43 v111 by cybernetus, and all is good after installation.
[Galaxy S II Android Development] harm007:
Necessary to use v109 by comp before v111 by cybernetus ?

[MENTION=1670821]cybernetus[/MENTION] :

Is it necessary to flash the v109 from [MENTION=4663860]Computoncio[/MENTION], reboot recovery before installing the v111-cybnt ?

http://xdaforums.com/showpost.php?p=52338237&postcount=9102

[MENTION=535343]all[/MENTION] kernel dev : Thanks for all.

Best regards.
[Galaxy S II Android Development] jl10101:
Hey, I see you are saying that v100 has the music stop bug? Is this to say that the latest V111 has fixed this issue on KK ROMs? Thanks! :)
[Galaxy S II Android Development] m1trand1r:
AFAIK yes.... [MENTION=4663860]Computoncio[/MENTION] added some fixes found around by devs....regarding music stop bug in v99 and up.....and [MENTION=2376110]dorimanx[/MENTION] didn't sync with [MENTION=4663860]Computoncio[/MENTION]'s git when building v100 so music bug is present on v100....by dori....i'm yet to flash v111 shortly...,I just woke up and saw v111....

Thanks again devs.......let's play around again[emoji106][emoji106][emoji106][emoji12][emoji12]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] m1trand1r:
HO-HO-HO .....reporting pure smooooothnesssssss from v111....

Hats off to you devs.....:D:D

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] nuraniharun:
8.43v111 is very stable and smooth.

But it gives parsing errors at installing apk:crying:
[Galaxy S II Android Development] TheImpossibleEnemy:
same here:highfive::good::D
[Galaxy S II Android Development] m1trand1r:
Can you fetch logcat for devs to look at it....?....Which apks did you try to install.......?....maybe they don't support lower android version than 4.2.x or 4.3.x....sammy is 4.1.2.....

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Spaulding89:
Same Here my friend. Just Great.

Many Thanks to all devs. You are the best for my Beast.
[Galaxy S II Android Development] Troubadour666:
i never see my device with speed booting like that, even 2nd rom.

i flashed morning the last 8.43v111 , "Dualboot Master" (as they said !) have :

4.1.2 neatrom 6.2 / 4.4.2 Spririt (monsters the two :) )

i see some of you with bad flash result after v111 installed , so can i back to v109 , the most 'stable' branch 8 i know , to clone 2nd rom on 1rst rom and made some last C-ROM 6.3 from [MENTION=4336480]aways[/MENTION] flashes ?? (joke about asking) .

Why ? because my device has never been so 'stable' as "It" is today and since i use [MENTION=2376110]dorimanx[/MENTION] kernel and DualBoot with !

(i still have issue "execv error" with installtheme.sh "oficial" (moded for sec_data or not) external script called process , 1rst rom or 2nd rom flash, with new recovery, but i wait patiently, not a problem with v76 to use for.)

thanks team !
[Galaxy S II Android Development] zazzaixx:
I got status 7 when trying to flash 10.43v111 with C-rom 4.4.2 :eek:
[Galaxy S II Android Development] stylemessiah:
Have to say that i havent been up to much lately, but a few days ago installed [MENTION=4663860]Computoncio[/MENTION] s 109 build and apart from some mount errors (caused by me force resetting the phone by accident), ive had 0 issues and it seems to have shaved 0.1% off my already low 0.3% p/h battery drain on standby

Currently looking at nearly 11 hours at 0.2% p/h - thats nearly 11 hours for 2% battery (100-98)

So im happy. Looking forward to the next build.
[Galaxy S II Android Development] m1trand1r:
flash v109 prior flashing higher versions ;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] cybernetus:
Search :)

v109 after v111
[Galaxy S II Android Development] Troubadour666:
i have made a thread which concern the use of set_perm commands instead of set_metadata for permissions during flash, maybe could help without downgrade kernel, i'm nos sure. its an aroma pach to scratch over 4.4.2 rom.zip and flash with.

ok, i downgrade to v109 to use it with 6.3 C-ROM (discret lol!), but in 1rst rom this time, so i can see that my flash kernel process and integrated maliv2 for branch 8 over dualbooted 4.4.2 rom work fine too :)

the thread :

http://xdaforums.com/galaxy-s2/themes-apps/aroma-install-kitkat-rom-recovery-t2737658
[Galaxy S II Android Development] infatality:
V111 don't seems to deep sleep.. Anyone else.?
[Galaxy S II Android Development] TheImpossibleEnemy:
Sleeps well here
[Galaxy S II Android Development] nuraniharun:
8.43v111 is Sleeping very deep:D

But it gives parsing error at all of apk packages.

I reverted back to v109. All ok.

Logcat_kmsg is here...
[Galaxy S II Android Development] infatality:
Hmm.. Strange.. I will take a look further.. [emoji15]

On v10?
[Galaxy S II Android Development] m1trand1r:
Hey mate:).....Long time no see, eh?.....

I can confirm 10.43v111 deep-sleep = O.K. on my side as well.....

And.....welcome back buddy....[emoji106]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] infatality:
It's really strange.. I don't sleep deep sleep row either in CPU spy or BBS.. Trying to figure out what's going on.. Anyway I'm on official SlimKat..
[Galaxy S II Android Development] m1trand1r:
Weird.,....Slimkat issue?

and what's c6903?...I mean which device?

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] infatality:
Xperia Z1 =D

Probably SlimKat issue... Looking on..
[Galaxy S II Android Development] jgcaap:
After some testing i had no SOD, but i had the following, the phone is working fine then starts to slow down.... and then freezes. Still couldnt replicate this bug to see on a log. :\

This is with 10.43v108.

anyone have something similer?
[Galaxy S II Android Development] cybernetus:
Ok here too ...

---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------

8.x branch is a problem

Uses v109 . I believe new updates break the 8.x branch again ( new linaro I believe )

---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------

Try v111
[Galaxy S II Android Development] nuraniharun:
And also I believe that dorimanx, computuncio and you can inject new updates in 8x branch easily. Because they did this at past.
[Galaxy S II Android Development] m1trand1r:
if this would be so "easy".....wouldn't they do that already ?...Not everything is the same with updates.....something must be left out.....because of Samsung :(

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] alisam:
here too no deep sleep!! v111 branch 10
[Galaxy S II Android Development] cybernetus:
Reboot the phone

Kit kat has this problem

If this not solve , report
[Galaxy S II Android Development] alisam:
FULL WORKING NOW!! without flashing v109 before i was in dorimanx v 100