yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] cmd512:
Yes, I read through dk_zero-cool's thread as per your first post. I see that it does support the old init.d script compatibility by checking /system/etc/init.d. But, it simply wouldn't load using the old S99xxxx script name (permissions were set correctly also). So, following its *.rc suggestion (FILES="`find /system/etc/init.d -type f -iname '*.rc'), I tried renaming it to xxxx.rc, still wouldn't load. At that point, I could execute the *.rc script manually, and verified that the settings were pushed to Uv_mv. Just can't get the darn thing to load at startup... strange indeed.

Sounds great and thanks on the LED fading, definitely a nice feature. Much "softer" than just the LED flashing over and over and didn't notice any impact to battery.

Lastly, I remember your excellent post on GPU scaling from the SGS2 forums. I noticed in the GPU control file that the stock %'s are stupidly low for the SGS3 at 1-2: 27%/24%, 2-3: 35%/33%, and 3-4: 35%/35% stock. Just curious what settings you're running on your SGS3?

Thanks.
[Galaxy S III Original Android Development] zodiaxe66:
Looking forward to v18 later or tomorrow.u always do awesome work.

Scoobydoo has been changed to soundgasm.catchy non the less

Ps.have nice relaxing vacation...and dam 1 month on my back I could go for that right now
[Galaxy S III Original Android Development] AndreiLux:
I didn't get to fully finish AOSP support for now as I was working on porting Siyah's 1-kernel-for-all implementation, as I can't be arsed to always compile two kernels at a time as the other devs do. I will try to finish it tomorrow, but if I run out of time, then I'll just do it the stupid way and temporarily do a separate kernel for AOSP.

If there's any bugs, you have about 24 hours to report it, if not, see you in a few weeks.
[Galaxy S III Original Android Development] currydude:
Thanks, working a treat at the moment :)
[Galaxy S III Original Android Development] Vaddy23:
Hey Andrei beautiful kernel with awesome battery life! I'm using Omega 8.0 with Alpha 17 and you can tell there is a positive difference in battery life as a result of you disabling the touch booster (800mhz lock) feature Samsung implemented. My only question is will you allow for GPU overclock using an app like Voltage Control in the future? NOVA 3 lags during multiplayer gameplay, I think a GPU OC would improve performance.
[Galaxy S III Original Android Development] bala_gamer:
installed build 18 and having reboots when the mobile finishes loading things, will try to post last_kmsg

edit:

seems like the previous settings of setcpu/nstools is causing the reboot
[Galaxy S III Original Android Development] samaxen:
Help with init.d Scripts

Guys,

Can anybody help me with the scripts of init.d to undervolt CPU and GPU please.

Thanks
[Galaxy S III Original Android Development] tanseerj:
Hi Andrew, thank you so much for all your efforts! Can you please confirm if the MTP driver for MAC is working on your kernel? Samsung changed something on the stock LFB kernel that broke compatibility with MTP on MACs. I can confirm that is the case as going back to LF2 kernel solved the problem.

UPDATE: OK I quickly flashed this to check and its the same issue, MAC MTP not working with new LFB base from Samsung.
[Galaxy S III Original Android Development] tvhak:
version 18: having a lot of reboots to. when restarts and is loading in a few seconds he reboots again. and gets hot.
[Galaxy S III Original Android Development] ausdim:
+1
[Galaxy S III Original Android Development] bala_gamer:
yes can confirm that, the last build reboots before getting settled with homescreen
[Galaxy S III Original Android Development] jody2k:
Just hope some of our devices didnt take too much damage already... not that i want to freak you guys out but in that case the fix wont help much.
[Galaxy S III Original Android Development] DrAnGeR:
When you are entering Download Mode(thats for official roms or Flash via Odin) or Recovery Mode (CWM) you are always vulnerable. When you are booting in OS even the time that you need to boot to OS u are safe but as irida said given the situation that you were running the phone for 250 days having that bug all the time ( Booting to OS, CWM and Download Mode) and survived i think you can enter the recovery and do what ever you might need but there is a chance to get SDS :). Dev suggesting to w8 a bit for the new recoveries but its totally up to you and ur luck :P
[Galaxy S III Original Android Development] T0xic4u:
This Kernel has a magic fix wich will be applyed at every boot of your phone. So no need to flash it every time you entered recovery.

Taper di Tap with my S3 @177 days
[Galaxy S III Original Android Development] tntgdh:
Andreilux, i had no Problem on YouTube Using the 31. Just tried on my two gs3.
[Galaxy S III Original Android Development] Tenacious:
Video is still glitches for me on 31.1 default settings logcat https://www.dropbox.com/s/02hpim8i2m5ydxv/2013-01-09-02-40-09.txt

Edit

But only in YouTube app, played video with stock player no glitches also streamed video over Wifi also fine so only YouTube app and flash in browser have glitches.
[Galaxy S III Original Android Development] wikusq:
thank you so much :)

so:

1. download kernel

2. flash by CWM

3. reboot

4. and I'm safe until the open recovery/download mode again. yep?
[Galaxy S III Original Android Development] DrAnGeR:
yeap totally correct
[Galaxy S III Original Android Development] VexMunja:
Just flashed 31.1 - also have YouTube video problems.

Sent from S3
[Galaxy S III Original Android Development] KS_Ho:
+1

Same here, problem still exists :eek:
[Galaxy S III Original Android Development] AndreiLux:
I tried a HD video with Dice Player and it played smooth again, but you're right, if I try YouTube it's accessing outside of the declared memory spaces... Weird. I'll research this a bit and then update again.

Btw, logcats are totally useless for me. I need dmesg/last_kmsg for kernels.
[Galaxy S III Original Android Development] estanenmi:
mee too

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] tntgdh:
I had no problem whatsoever on my both phones. I tested with YouTube app both HD and normal resolution.

I'm using omega rom 35.
[Galaxy S III Original Android Development] jimbo77:
I don't understand what issue are you guys experiencing. I have played a few videos through YouTube app and they played fine.. No glitches what so ever
[Galaxy S III Original Android Development] AndreiLux:
Before I go on a wild goose chase, what ROM are the people on on who it works without glitches?
[Galaxy S III Original Android Development] tntgdh:
I am using omega rom 35 my friend. On both phones and they both play perfect... I just retested using my 3g..
[Galaxy S III Original Android Development] beaver2233:
on wifi, on both stock video player and YouTube have the aforementioned issue - running neatrom lite (LLA).

edit: tried a few more videos on the stock video player - seems ones recorded on the phone skip, ones downloaded off tube mate skip and those downloaded from torrents (family guy etc) work fine...
[Galaxy S III Original Android Development] Tenacious:
Sorry about that

dmesg https://www.dropbox.com/s/yrzw8xwmmipejuk/dmesg.txt

last_kmsg https://www.dropbox.com/s/0z9j3lfnvy1xvcr/last_kmsg.txt

Im on stock LLA.
[Galaxy S III Original Android Development] Chris_84:
Glitches on omega 36. With old and new bootloaders. Was trying if it might be the issue but without success. Also wiped cache and dalvik. Nothing. Deleting app data also no success. Will try tomorrow some more. Running now on stock kernel. No issues here.
[Galaxy S III Original Android Development] nfsmw_gr:
I've never used powersaving mode...

Weird..31.1 same results...

What could have gone wrong?

I also tested at stock settings and i got the same results.

Btw i saw in os monitor that android system had a bit of cpu usage...

Should i reflash my rom?I use ultima rom without tweaks of any kind except internal2external mod.
[Galaxy S III Original Android Development] spirit.of.resistance:
don't work on foxhound..
[Galaxy S III Original Android Development] jimbo77:
Stock Odexed XXELLA + Jkay Deluxe Framework
[Galaxy S III Original Android Development] VexMunja:
I'm om stock LLA, too. Apereantly,stock ELLA rom + 31.1 = YT video issues? As I can see, custom roms working fine...

Sent from S3
[Galaxy S III Original Android Development] DrAnGeR:
Guys help Andrei by saying which rom are you using and if its working or not. Not just saying the name of the rom without knowing if its working or not
[Galaxy S III Original Android Development] jimbo77:
Have you guys with the error wiped cache and Dalvik Cache after the kernel flash and update?
[Galaxy S III Original Android Development] psyntific:
Deleted

Sent from my GT-I9300 on ARHD 18 with perseus 31.1
[Galaxy S III Original Android Development] tntgdh:
I just found the lag problem here on that Samsung video that is in the phone. The weird thing is that almost all vids recorded from my camera work flawless...but two.... go figure. Seems that something is missing from those videos and makes them lag.

YouTube still perfect.
[Galaxy S III Original Android Development] AndreiLux:
I'm going to check the LLA libraries and if it's that I'll do a zip for people who haven't updated their ROMs yet and not update the kernel.
[Galaxy S III Original Android Development] tntgdh:
Also any video recorded using the phone's camera is broken.
[Galaxy S III Original Android Development] mamba720027:
Rom : Omega v36

Kernel: Perseus 31.1

Recorded camera videos lags on stock player and using mxplayer.

YouTube works fine for me.

Edit: also with mxplayer .mp4 videos lags but .flv videos experience no lags.

Sent from my GT-I9300
[Galaxy S III Original Android Development] optmkleung:
Wanamlite 5.3 LLA rom, youtube fine with low resolution video. But extrme lag for high resolution. 30.1 kernal
[Galaxy S III Original Android Development] :
Rom: neatrom 1.4

Kernel: perseus 31.1

Recorded video lags and stutters badly. Same on YouTube.
[Galaxy S III Original Android Development] jimbo77:
I just tried to play an HD video using stock player and I can now see the issue... The image jumps all over the screen, YouTube works fine though
[Galaxy S III Original Android Development] cgvelmax:
the same issue here the image shakes in stock player.

ARHD 18 with Perseus 31.1

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] estanenmi:
im on wanamlite 5.2 ll5 rom and i have youtube issues... on kernel 30.1 is fine...

also bsplayer any video imagen shake

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] drakester09:
Adding my info:

Video Shakes on full stock XELLA odexed.

Happens with Stock Video player and Youtube.

Tested with Perseus 31.1
[Galaxy S III Original Android Development] AndreiLux:
I'm going to upload 31.2 with a temporary fix until I figure out what Samsung is up to in their code, their security fix code related to MFC is broken/unfinished.
[Galaxy S III Original Android Development] ruskin0611:
Just to confirm; 31.2 is a temporary fix for the jerky video but still keeps the eMMC patch, is that right?
[Galaxy S III Original Android Development] AndreiLux:
Yes 31.1 was just an attempt to fix the jerky video and 31.2 fixes it through unconventional manners until I can go through the code a bit more. I'm getting tired for today so I'll leave it as is for now. Uploaded 31.2 in the OP.
[Galaxy S III Original Android Development] bala_gamer:
i dont have words to describe your efforts here andrei..!! thanks for incorporating the emmc patch and once again thanks for your work :)
[Galaxy S III Original Android Development] ruskin0611:
Brilliant. Thanks heaps... :good:
[Galaxy S III Original Android Development] pramdit:
Thank you very much andrei...
[Galaxy S III Original Android Development] MatangaChanga:
+1
[Galaxy S III Original Android Development] bala_gamer:
read last page?
[Galaxy S III Original Android Development] rulala:
My S3 is 32G. I use Emmc check. My info is

EMMC CHIP

type:VWU00M

revision:0xF0

I found "Near All" 16G users is VTU00M....everyone is VT...

so... I just want ask if 16G must be VTU00M?

I mean even though phone was Sent to change a new One...16g is also VTU00M?

am I right ? If I am right .... 16G users were Only solved by Emmc patch?

thanks.
[Galaxy S III Original Android Development] :
I didn't understand the second point so much.

The patch from Samsung is just a workaround, and it's applied every boot by the kernel. But what did you mean by "this also will include updated recoveries"?
[Galaxy S III Original Android Development] AndreiLux:
Recoveries are embedded with a different kernel than the normal boot kernel, recovery maintainers will need to repackage their recoveries with an >LLA stock kernel or complie their own with the patch applied.

You're still at risk when you are inside of the recovery, because you're using its respective kernel during that time.
[Galaxy S III Original Android Development] Angeluz01:
am i safe?

Thz for reply^^;

ics 4.04 Omega 9.1 XXBLG1
[Galaxy S III Original Android Development] sak500:
Anyone losing their camera pics or videos even if stored on external SD? I just lost couple of pictures i took a few days back. They are showing in dropbox but not in my external SD. This happened few months before the S3 chewed up my sandisk 32gb class 10 card and i had to get a new one underwarranty. WTF with s3. ALready got replaced motherboard for the SDS and again it might destroy my ext SD card.

BTW my default sample video plays perfectly on MXplayer on 31.2 didn't try the previous kernel so can't comment.
[Galaxy S III Original Android Development] :
Got it now. That's why Siyah can handle recovery and the kernel at the same time, without doubling the size. I always tought that recovery used the main kernel, maybe because it was like that on the i9100 (as it had a kernel+recovery and an unused recovery partitions). It's quite unlikely to brick right into the recovery, right? You spend 99% of your time using the phone, "safely", and then you gotta be damn lucky to brick the phone on these seconds flashing or wiping something on the recovery.

---------- Post added at 02:01 AM ---------- Previous post was at 01:57 AM ----------

The chip mentioned in OP, that got fixed by the patch: VTU00M

Your chip: VTU00M

Are you safe? make your own conclusions ;)

btw, juicedefender is useless for most users. No wonder why it stopped being updated... I honestly don't know the kind of proper user to use it. At the same time it manages connections and stuff, it keeps running in background and with wakelocks, otherwise it wouldn't do anything... let the system alone ;)
[Galaxy S III Original Android Development] drakester09:
What concerns me a bit regarding the recoveries is the sheer amount of i/o you usually do on it.

Backups, restores, flashing/copying large amounts of data, themes. Some do a simple wipe or write but others do massive copying.

Since we aren't certain on the condition that triggered the EMMC failure I'd avoid doing large ops for the moment just to be 100% safe.

Updates should come very soon. ;)
[Galaxy S III Original Android Development] dantheman122:
My chip type is VTU00M and Firmware 0xf1, does that mean my device is not affected or is 0xf1 the same as 0xF1?
[Galaxy S III Original Android Development] thekoRngear:
How about the cwm recovery (v 6.0.2.7)? that we flashed separately? Are those needing to be patched too?
[Galaxy S III Original Android Development] hellsgod:
Yes. All Recoveries needs to be patched.

hells

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Anakha56:
Many, many thanks for your hard work AndreiLux and Entropy512 for coming in and providing information :). It's dev's like you guys that make owning a android handset a blast :).
[Galaxy S III Original Android Development] mjb:
F and f are the same thing in hex. So yes, you're affected.
[Galaxy S III Original Android Development] dbenyakar:
Hi

I downloaded the Perseus.alpha31.2-i9300-CWM.zip in order to install in on my device which runs WanamLite 5.3.

However installation fails every time. My recovery is TWRP. I succeeded installing older versions of this kernel but not this one.

Has anyone encountered this issue before?
[Galaxy S III Original Android Development] bala_gamer:
Might be a bad download, flashed it via twrp and it works

《posted from samsung rom》
[Galaxy S III Original Android Development] dbenyakar:
I downloaded it 4 time already, wiped cache and Dalvik cache and it failed flashing the file every time.:(
[Galaxy S III Original Android Development] iridaki:
Get the .tar version and flash via Mobile Odin.
[Galaxy S III Original Android Development] svs57:
root@android:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type serial cid

VTU00M

0x0

0x0

0x000015

0x0100

05/2012

MMC

0x587f5904

15010056545530304df1587f59045fa9

But eMMC Brickbug Check show me

"sane chip"
[Galaxy S III Original Android Development] thekoRngear:
that sane chip status doesnt matter what matter are the hw revision and internal fw:

if it is VTU00M and 0xf1 or 0xF1 then you are affected.
[Galaxy S III Original Android Development] slaphead20:
I just read 20 pages to get all the information needed........why can't other people do this?.......20 frickin' pages off the same questions over and over again :banghead:
[Galaxy S III Original Android Development] svs57:
I just wrote that "eMMC Brickbug Check" doesn't identify wrong chip.
[Galaxy S III Original Android Development] rlorange:
Deleted
[Galaxy S III Original Android Development] slaphead20:
I'm not demanding anything....I'm commenting that if people read more then we wouldn't have to wade through pages off repeated questions to get the information, the person I quoted obviously didn't......your problem with me is?

---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------

.......and how to identify it has been posted numerous times!
[Galaxy S III Original Android Development] habylab:
When I flashed 31.2, my phone asked me if I want to disable recovery flash..m this doesn't normally happen when flashing a kernel, so is it okay to disable it?
[Galaxy S III Original Android Development] rlorange:
Edit... OK I think I overreacted man. I misinterpreted your post

---------- Post added at 06:34 PM ---------- Previous post was at 06:29 PM ----------

Slap-my- head your post read to me like you were complaining that you had to wade through pages to get to the post you quoted. I think the v post below me read the same :confused:
[Galaxy S III Original Android Development] slaphead20:
Edited due to apology!

No problem dude......reading practise anyone? ;):p:D
[Galaxy S III Original Android Development] kamalmawa:
Thankd Andrei for all your hard work and findings :good:

I see so much love going on this thread haha... here is a big hug 'O' from me.. rlorange I think you misread what he meant :silly:
[Galaxy S III Original Android Development] rlorange:
He me no read good

---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------

Group hug everyone? :p man this eMMC bug got me all jumpy. Please don't die on my (patting my SGS3 affectionately)
[Galaxy S III Original Android Development] danarama:
Please, if I use generic terminology, its not for lack of understanding. It's for simplicity.
[Galaxy S III Original Android Development] svs57:
May be easy change first post? Just remove link on wrong program and add identify shell code.

---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------

Have a question. Which CWM recovery has safe kernel?
[Galaxy S III Original Android Development] EViollet:
Especially when a chip's firmware IS software. So your assertion was correct.

I'm going to take advantage of this post to thank you Andreilux for your dedication to this community.

I really hope you continue to support us for as long as possible and not give up before, say... at least summer 2014 when I change my phone.... ;)

Regards,
[Galaxy S III Original Android Development] Pip_X:
Non so far.
[Galaxy S III Original Android Development] timvdhoorn:
First of all thank you very much for this kernel with the SDS fix!

But my battery drain in sleep is very high.. its a know problem?
[Galaxy S III Original Android Development] slaphead20:
Install bbs and find out what is causing drain....No problem here
[Galaxy S III Original Android Development] timvdhoorn:
i didnt had any problems on stock kernel of omega 36
[Galaxy S III Original Android Development] danarama:
Exactly. Software embedded in hardware! When using the generic categories of "Software" and "hardware", I'm not going to throw a "Firmware" in there ;)

Yes, sorry AndreiLux if I haven't said Thank you recently... I'm loving this Kernel so much. It's super!
[Galaxy S III Original Android Development] Nees3:
If I would flash this, is it easy to return to stock kernel? Since Custom Kernel will not clear everything with triangle away. I'm thinking of flashing this kernel till samsung brings out a stock kernel-update. or does the EXLLA now contains the fix also and the sources have only just been released? It is all abit confusing. (my device is running about 120days now, so the quicker fixed, the better :) )
[Galaxy S III Original Android Development] :
Try BBS and see whats causing the problem. It will mostly be the rogue apps. Moreover try different kernels and see which suits your use. For my usage, I did not find Siyah/ Stock kernel saving any battery but Persues has been completing suiting me a lot and I am sticking with it till date.

There is nothing wrong with Siyah or Stock, it is just that our usage sometimes does not make a kernel effective and we may have to research on a different one.

But we have finest devs who have created different kernels and thats the good part of being in XDA :)
[Galaxy S III Original Android Development] MuertoKo:
LLA seems to fix, and this kernel works for triangle away as well, for more info all it's written on OP :) you can read some posts back as Entropy said some words about this here and on SDS thread

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] :
My understanding on reading the OP is that Samsung has fixed the SDS in the Stock Kernel and Andrei has taken those for the Perseus. So stock kernel seems to fix SDS and yes you can flash perseus and as well return to Stock later.
[Galaxy S III Original Android Development] fedort:
Thanks a lot Andrei! I finally feel ´safe´ again, as I really was afraid of my S3 to die.
[Galaxy S III Original Android Development] skivnit:
Thanks for confirming my thoughts. I have the lla stock kernel I guess I don't need to flash Perseus
[Galaxy S III Original Android Development] :
You are very welcome :)
[Galaxy S III Original Android Development] thekoRngear:
Not fully until the recoveries are upgraded to that patch.
[Galaxy S III Original Android Development] Nees3:
But AndreiLux says this: … repackage their recoveries with an >LLA stock kernel or complie their …

> means in the case NEWER THEN, this is not NEWER or EQUAL to LLA (>=). So this makes it for me very confusing. For me, this means that only a newer kernel, based on update7 from samsung, contains the fix, not the current kernel.
[Galaxy S III Original Android Development] doromax:
A question : what do you mean with recoveries ?

Maybe Bootloader = Recovery ?

I don't understand this.
[Galaxy S III Original Android Development] flight23:
In the other thread someone examined the ELLA kernel and found the fix there as well:

http://xdaforums.com/showpost.php?p=36465270&postcount=2741
[Galaxy S III Original Android Development] Nees3:
Those that develop custom recovery software.

---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

They never looked for it in older kernels, what if that string can be found also in there? then it proofs nothing...