yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] fitipardi:
Thanks mate, but i dont understand, maybe because i noob. Samsung changes mainboard (HW) to phones bricked and you fix by SW?

Regards

Enviado desde el bar con una birra en la otra mano
[Galaxy S III Original Android Development] Neokazaki:
+1, same question

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] fifamaniac:
Thx AndreiLux... having a 16 gb phone and been affreid that he dies... have wooned a new fan to your kernel... been on siyah so long, but that seems your kernel have the same sound improvments as siyah too!!!

A big thx by your hard work man!!!

:good::good::good::good::good::good::good::good::good::good:
[Galaxy S III Original Android Development] danarama:
EMMC failure caused by software. Fix preventative. Fix wouldnt repair already failed EMMC
[Galaxy S III Original Android Development] dimi22:
and what if it partially was failing but not bricked?
[Galaxy S III Original Android Development] Tyrigi:
sry for noob question what is EMMC failure?
[Galaxy S III Original Android Development] kaiur:
The EMMC frailure is sudden or agonic? I mean, could our EMMC been previously "touch" by death and fail even if we use the fix?
[Galaxy S III Original Android Development] danarama:
If the end result is actually hardware failure, partial hardware failure would still be hardware failure.

Not knowing what the actual fault or fix is, I can't say if software intervention at partial failure stage would prevent full failure or at what operational level the EMMC would remain

---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------

Honestly don't know. Not sure what the actual fault is....

---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------

Failure of the embedded Multi Media Card. Basically, the internal memory that the ROM, kernel, bootloader etc is installed on.
[Galaxy S III Original Android Development] jody2k:
Thx alot, guess you will saving alot s3's (hopefully)
[Galaxy S III Original Android Development] BoneMo:
but not me when i have CM10.1 :crying::crying:, so i have to live with the risk od emmc failure
[Galaxy S III Original Android Development] wikusq:
is fix for MMC failure in Perseus alpha30 (06/01) or fix will be inside the next verion? ^^
[Galaxy S III Original Android Development] vegeta1:
Just hold on for the update
[Galaxy S III Original Android Development] GrayJack:
Next which will appear in next hour :)
[Galaxy S III Original Android Development] drakester09:
Once the fix is pushed to Github, it can be pulled and integrated into CM kernel and other great third party kernels such as Siyah or Yank's.
[Galaxy S III Original Android Development] Lither:
@AndreiLux

The audio mod files used in this kernel is the same as Siyah? Because all my music is in 320kbps and I want the best of audio quality through my earphones
[Galaxy S III Original Android Development] Rob2222:
Andrei,

thx for confirming. When youre done with patching the kernel, could you maybe spent two more words about how it comes to MMC failure and how the newer kernels fix it? Is it a situation that can (but must not) occur? Or do we all have now "light" damaged (or at least hard used) MMC ICs after living 6 month with the old system?

BR and thanks in advance

Rob
[Galaxy S III Original Android Development] Entropy512:
It's not caused by software - it's caused by faulty firmware in the eMMC. It's possible, if such a firmware issue is known, to patch it on-the-fly to fix it. Kernels for the Galaxy Nexus have been doing this to fix a less severe issue since the spring, and now Samsung's source has a similar patch.

Unknown. There's a possibility that the patched firmware might be able to "clean up" data structures going forward. It's unknown.

You have to keep in mind that what is happening is not that underlying flash memory regions are getting destroyed, but the data structures the wear leveller is working with get corrupted. My guess is some sort of integer overflow problem after too many I/O cycles. In short - similar symptoms to Superbrick (attempts to access corrupted data structures hang the chip), but with a different cause.
[Galaxy S III Original Android Development] Rob2222:
So we don't need to be worried about having worn out EMMC ICs in our phones?

Does this mean, once youre running a kernel with the fix, the emmc firmware is patched and after that safe for all (also older) kernels?

BR

Rob
[Galaxy S III Original Android Development] faithhh:
yes bingo :cowboy:
[Galaxy S III Original Android Development] nicmicg:
sorry ... but what is SDS? and it became clear what is the cause of the EMMC faillure? :confused:

thanks
[Galaxy S III Original Android Development] _delice_doluca_:
It is a super exciting waiting :) That's a mind changer about selling the phone..
[Galaxy S III Original Android Development] ShannonAUT:
So the 30.1 version we can get from the first post has this patch already included?
[Galaxy S III Original Android Development] odd29:
No
[Galaxy S III Original Android Development] AndreiLux:
No, the fix is some MMC command magic and it is a soft-patch that's applied on every single boot or MMC resume. You will not be safe on kernels without it (People will have to use updated recoveries too!). The phones affected are as previously theorized only the ones with VTU00M memory chips.

Please give me another few moments as I'm testing for no other bugs.
[Galaxy S III Original Android Development] flight23:
No!

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] nfsmw_gr:
Man i've seen this frickin' question much too many times the last few days in this thread!

Andreilux isn't gonna answer you and none including me is gonna answer this too.

Try it yourself and see if it works nice enough for you!

Please guys don't ask again really,try it yourself.
[Galaxy S III Original Android Development] mjb:
No, not if the fix is a workaround in the mmc driver, or a run-time patch of the firmware (that needs to be applied at every powerup).
[Galaxy S III Original Android Development] nfsmw_gr:
How can one see what memory chip his/hers phone has?
[Galaxy S III Original Android Development] donteo:
Check playstore for "emmc check"
[Galaxy S III Original Android Development] GrayJack:
So you mean all recoveries should include your patch also because they perform operations with MMC also?
[Galaxy S III Original Android Development] mamba720027:
(SDS) sudden death syndrome. Cause of it is faulty firmware in the EMMC.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Rob2222:
Hello Andrei,

so is it safe to go back to a older bootloader?

Or is there a chance, that even the bootloader already does this MMC command magic?

BR

Rob
[Galaxy S III Original Android Development] mjb:
Recoveries have kernels too, so that kernel needs the patch.
[Galaxy S III Original Android Development] skivnit:
I guess everyone's waiting for your magic

Swyped from another galaxy
[Galaxy S III Original Android Development] nfsmw_gr:
Sh****t!!

My phone too has VTU00M memory chip...:(

Thank god it's still alive..:p

Thanks for fixing the issue Andreilux. :)
[Galaxy S III Original Android Development] ali4796:
According to "eMMC check" app:

My eMMC chip type is VTU00M.

So am i vulnerable of sudden death even after flashing new persus kernel (i mean the one that Andreilux is going to upload) ?

Thanks
[Galaxy S III Original Android Development] nfsmw_gr:
No,with the new version you'll be safe. :)
[Galaxy S III Original Android Development] Entropy512:
I'm not sure about what happens if the eMMC is close to failure - but hopefully the firmware patch will "repair as it goes along" in addition to not triggering failure.

And as Andrei said - it is patched in scratch RAM within the eMMC at boot time, and is done in a volatile manner.

Nonvolatile update of the eMMC is a highly dangerous operation - It fully wipes the entire chip including bootloaders, and if it fails it can leave a dead chip that is 100% unrecoverable. This is why we never received a fix for Superbrick or even a repair methodology.

And remember - the "sane/insane" chip determination is ONLY applicable to the GS2 "Superbrick" problem.

Since VTU00M is not vulnerable to last year's "Superbrick" bug it reports as sane with that app - but VTU00M is the chip you need to watch for.
[Galaxy S III Original Android Development] wikusq:
omg i love you ! :D
[Galaxy S III Original Android Development] Nees3:
But is this "update7-fix" and your own kernel also applied in the LLA release?
[Galaxy S III Original Android Development] AndreiLux:
This is a question nobody but Samsung can answer. The bootloader may do some MMC alteration as well, I do not know, but the soft-patch on the kernel side seems to be complete, even though it's just magic code and nobody can understand it so nobody can be sure of it.

Btw: "Magic" code/values in programming means fixed constant binary values of no intrinsic meaning to them. Nobody beyond the engineers knows their meaning.

The kernel is up in the OP, I'll write the changelog in a few moments. Sources are pushed to Github. The MMC fix itself is here, for the curious.
[Galaxy S III Original Android Development] sachilleas:
I will categorize our questions in order to be more clear for future users:

1)Where did you find guys these fixes and what is the "update 7"?

2)Is there a way to find wether my mmc is already worn out?

3)Ok, kernel will fix the SDS, but what about recovery? Andrei said that it should be patched too.
[Galaxy S III Original Android Development] behemot24:
I'm so out of luck - my phone died of sds today (for those who don't know, sds for galaxy s3 is what aids is for people), right before the patch is released :banghead:
[Galaxy S III Original Android Development] T0xic4u:
About Recovery, I guess as long as you don't boot to recovery you aren't in danger. The new kernel will fix the SDS when you boot the OS. Recoverys will get the magic fix later.

Taper di Tap with my S3 @176 days
[Galaxy S III Original Android Development] donteo:
Perseus-alpha31 this is the new "magic" kernel ?
[Galaxy S III Original Android Development] UltrasFrankfurt:
Am I in danger, when my emmc has the type VTU00M? Andrei said yes, but "emmc brick bug check" says no

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] 17RoiDavid:
there will be an official samsung update for that via ota or kies in the next few days?
[Galaxy S III Original Android Development] wikusq:
same here.

whats wrong? :s
[Galaxy S III Original Android Development] drakester09:
Brick bug has nothing to do with i9300. It affected SII/Note I etc.

We have a different issue on the emmc, it is patched on Perseus 31 and higher.

The app main usage is to check which type of emmc you have and the fw revision.
[Galaxy S III Original Android Development] SavanTorian:
but if you want to flash something via CWM or odin, you'll automatically get into recovery., what will happen then?

im affected to VTU00M :(
[Galaxy S III Original Android Development] T0xic4u:
Just flashed your new kernel. Fingers crossed. Thanks for your work.

Taper di Tap with my S3 @176 days
[Galaxy S III Original Android Development] GrayJack:
Strange - Perseus 31 mysteriously disappeared from the first post :)

Samsung guys hacked the forum? :D
[Galaxy S III Original Android Development] wikusq:
thx for answer!

will new magic kernel with fix works on old bootloader, yes?

and i will safe only when i will not open a recovery? or i get it wrong
[Galaxy S III Original Android Development] droidgirl74:
Dont see it anymore, either... hope, I did not flash too early??

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] DrAnGeR:
i think you are right considering what Andre claims, but i dont know i am a little confused with all that idea. In either way (old or new bootloader) triangle will reset the counter to 0 so you can claim the warranty and also samsung is not that stupid if he wante to track you he would put bootloader like HTC and sony. Dunno i am just saying
[Galaxy S III Original Android Development] donteo:
I flash it too :(
[Galaxy S III Original Android Development] T0xic4u:
Me too.

Taper di Tap with my S3 @176 days
[Galaxy S III Original Android Development] Crunozaur:
Installed 31a few moments ago. Seems to be working fine.

This is the first kernel which doesn't lag since Perseus 27a - I've tried stock, Siyah etc. All of them were stuck on 40 fps max after locking the device. Really strange bug, probably rom-related, but i was too lazy to reflash it.

AND it (probably) fixes SDS! :D

well done AndreiLux
[Galaxy S III Original Android Development] kire.htc:
Link please, cant find the kernel.
[Galaxy S III Original Android Development] DrAnGeR:
I can see the kernel but the counter for the views doesnt work.weird
[Galaxy S III Original Android Development] AndreiLux:
I did a minor mistake and re-uploaded 31, but those who already have it can stay with the one they downloaded.

Anyway, I'm done here, moving on to the other devices.
[Galaxy S III Original Android Development] real77055:
thanx a lot!!

i only didn't understand this one ''this also will include updated recoveries''

is the kernel update recoveries too?? twrp cwm???
[Galaxy S III Original Android Development] wiecho65:
Andrei i want to install you kernel but when i install your wersion 30 i lost Crt off. In siyah with stweaks its fix for this,can you also do it this fix?? Regards and thanks
[Galaxy S III Original Android Development] iridaki:
[delete]
[Galaxy S III Original Android Development] donteo:
Samsung's fix for the sudden death syndrome (SDS) included ? That is official fix that will get via ota ?
[Galaxy S III Original Android Development] wikusq:
does new kernel version work with old bootloader?

i will be safe only if i will not open a recovery after flasching? :X
[Galaxy S III Original Android Development] JSale:
Just tried watching a YouTube video withe the built in app after updating to v31, it is extremely jumpy and the images refresh slowly. Does this happen to anyone else, I cannot provide a log ATM but possibly in the morning.

I will use this kernel regardless as my phone is affected by emmc according to the app, but I m just curious as to if anyone else has similar behaviour.

Many regards

Jack
[Galaxy S III Original Android Development] jody2k:
Maybe a dumb question or I missed something, is there a way to disable hardcore sharpness tweaks in this kernel?
[Galaxy S III Original Android Development] Chris_84:
Yes you're right the sound is normal but the picture jump like you watching the video in fast forward.
[Galaxy S III Original Android Development] AndreiLux:
Ok, that's odd. I didn't test hardware decoding.

I guess there will be a version 31.1. Give me some time.
[Galaxy S III Original Android Development] donteo:
Y there is problem with youtube !
[Galaxy S III Original Android Development] Chris_84:
Take your time! Very thankful for everything you do! :thumbup:
[Galaxy S III Original Android Development] JSale:
Thanks a lot, I don't know where you get the time to produce such a great kernel.

Regards

Jack
[Galaxy S III Original Android Development] spirit.of.resistance:
Thank you Andreilux for all your work!!2 question,best way now for user,is keep the last kernel and the old bootloader to use perfectly triangle Away?and for people who doesn't root,flash,they will never have a solution?
[Galaxy S III Original Android Development] clin81:
this Soft patch works with xxella bootloader?
[Galaxy S III Original Android Development] nfsmw_gr:
Andreilux there's something wrong with the latest version.

At first,homescreen scrolling seemed a bit laggier than previous version so i run some benchmarks to see what's going on...(absolutely same setting nothing changed)

Antutu scores dropped from 17500+- to 9000+-

Geekbench scores dropped from 2000+- to 900+-

And quadrant scores dropped from 6800+- to 4500+-

Could you take a look please?

I'm reverting to 30.1 for now.

Cheers mate. :)

Also i forgot to mention that it self rebooted once for no obvious reason and boot time took a bit longer than excpected.

Anyway,i could do a logcat if you need any help. :)

Thank you for your work.
[Galaxy S III Original Android Development] Rob2222:
Your answer is some posts above youre post:

http://xdaforums.com/showthread.php?p=36464552#post36464552

BR

Rob
[Galaxy S III Original Android Development] T0xic4u:
My Antutu is

Taper di Tap with my S3 @177 days
[Galaxy S III Original Android Development] jimbo77:
I just flashed alfa 31 over Siyah 1.86 (I don't want to play with my luck when it comes to SDS) and wiped cache and dalvik cache and I don't have any of the issues mentioned.

Scroll is fine and YouTube videos played fine with no syncing issues at all...

This is my first time using Perseus, let's see how it goes...
[Galaxy S III Original Android Development] AndreiLux:
Turn off your powersavings mode...........

Okey, fixed it (Stuttering hardware decoding). Samsung forgot a change in their update7 sources. :rolleyes:

Uploading 31.1 in a few minutes. Edit: Up.
[Galaxy S III Original Android Development] krivinash:
Can someone , please, give us , total noobs some instruction how to flash that new kernel?

There are two files. What should I download? Im on stock xxella, so probably .tar file?

As i understud, I will always have to have this kernel in my device, to be safe of sds? After restarting my phone, the fix will be activated every time?

Thanks !!!
[Galaxy S III Original Android Development] DrAnGeR:
tar file is for ODIN and CWM is flash-able through recovery if that makes sense. ur choice.
[Galaxy S III Original Android Development] wikusq:
my questions again:

does new kernel version work with old bootloader?

i will be safe only if i will not open a recovery after flasching? :X

plz answer me
[Galaxy S III Original Android Development] psyntific:
Mate use mobile odin or odin to flash tar n recovery to flash zip

Sent from my GT-I9300 on ARHD 18 with perseus 31
[Galaxy S III Original Android Development] spirit.of.resistance:
you can flash the .tar file with odin or the zip by the recovery..
[Galaxy S III Original Android Development] illuminato 67:
I think yes at all

Inviato con il mio S3 ROM Omega 36
[Galaxy S III Original Android Development] DrAnGeR:
As far as i know it works. You will be safe as long as you are not entering the recovery mode. you are effected on the recovery mode :).

Now we are waiting the new recoveries :good:
[Galaxy S III Original Android Development] krivinash:
Thank for your answer!

Is the same procedure like when you flash the fw?

Two boxes cheked, putting .tar in pda , etc...?
[Galaxy S III Original Android Development] spirit.of.resistance:
i got new kernel with old bootloader,i think for the recovery we have to wait a fix too..
[Galaxy S III Original Android Development] DrAnGeR:
yes :)

two boxes F.Reset and the first one i dont remember the name :P
[Galaxy S III Original Android Development] iridaki:
However, considering it took about 200-250 days, during which the phones ran 24/7, for the bug to kill them, entering recovery once in a while for a few minutes should not be such a big deal, until updated recoveries start to emerge.
[Galaxy S III Original Android Development] wikusq:
thx a lot!

so CAN I flash kernel via recovery but after flashing i cant (shouldnt) going into cwm?

what will happen if i will start recovery mode? will i again vulnerable to sudden death? after each entry in recovery should i flash kernel? ;ooo
[Galaxy S III Original Android Development] hellsgod:
del
[Galaxy S III Original Android Development] cba1986:
This kernel has any side effect on LFB?
[Galaxy S III Original Android Development] qwerty12:
Hmm, I just wiped /data, reflashed XXALF2, then XXLFB, applied CF-Root and flashed your kernel:

C:\Users\Faheem>adb shell
shell@android:/ $

I'll probably end up setting up Linux in a VM and repacking the boot.img with a Chainfire-patched adbd. (I like the ideas behind this kernel too much to try others.)
[Galaxy S III Original Android Development] AndreiLux:
Well AOSP support is quite demanded, so I'll try to do that next, other than that, and ScoobyDoo sound which has political implications here and I need to make an app to configure it, I don't really see any cool (And by that, I mean useful) features in other kernels at the moment. One thing at a time...

If you watch a video on YouTube, rotate to fullscreen, and then rotate back, the video will be higher than its frame. Currently all kernels have this, and probably can't do anything about it until they release new sources, I'm not going to screw around to understand and search for fixes in the kernel for that.

Right. I'll switch to that method later on in the night and release a version. Sorry for the misunderstanding. Edit: just be clear, you want it to avoid to type "su" in ADB or what?
[Galaxy S III Original Android Development] qwerty12:
Thanks.

Yes, with adb running as root, I can use commands like "adb remount" (I'm lazy - I can't go back to running mount -o remount,rw manually now :)) and I can push files to /system directly without having to put them on /sdcard first, adb shell in, run su and move them from /sdcard. I have bought Chainfire's ADBD Insecure which does this - it kills off adbd, installs his own version and restarts it. (And has to do this on boot each time since /sbin is replaced by whatever is in boot.img) Since, however, I'm not using the stock kernel anymore and starting ADB over USB seems to be slow for my phone, it would be nice not to have to rely upon ADBD Insecure anymore.
[Galaxy S III Original Android Development] AndreiLux:
Here you go, didn't bother to compile something new, so same as a17. Sorry for the misunderstanding, I don't use ADB that much.

Switched back to ro.secure=1 and insecure adbd, don't know why it didn't work properly before though.

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb -s 4df1366638855f49 shell
root@android:/ # cat /proc/sys/kernel/osrelease
cat /proc/sys/kernel/osrelease
3.0.36-Perseus-alpha17
root@android:/ #
[Galaxy S III Original Android Development] knights.JayTana:
Andreilux

You hit the nail. That 2 is exactly what we're looking for... More power...
[Galaxy S III Original Android Development] Carphedon:
I would really like to use this kernel, reading the changelog, it looks to me that you are a very skillful developer. The only thing is that i need it to be compatible with CM9, i know it's on your todo list but just wanted to give a +1.
[Galaxy S III Original Android Development] cmd512:
Just flashed Perseus alpha17, the kernel is quite nice... 5 star vote added. (Told ya I'm not kernel biased!)

A few questions:

1) I've done just about everything I could to get a plainjane init.d script (CPU UV, GPU UV) to run at startup, but it just won't execute. I can rename it to 55xxxx.rc and execute it manually to apply the changes, but anyone care to walk me through dodo school as to why it's not loading at startup?

2) Question for Andre: Any plans of implementing LED Fade support by teamhacksung? I know this is not exactly a required feature by any means, but after using it on NEAK, it is quite nice if you do use the LED notification light.

Thanks in advance.
[Galaxy S III Original Android Development] AndreiLux:
Did you follow through the instructions here? I'm not using the normal run-of-the-mill init.d support. If that doesn't work / clear things up, I'll have to check again for bugs.

I will check LED fading. I want to release the update3 source update tonight and if possible also AOSP support, Thrusday I will be gone for a month.