yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] psndna88:
18-05-2016 Update v5.10.3 (Stock-sources based)

build wih GCC 6.0 UBERTC which promises to give good user experience

18-05-2016 Update v4.5.5 (ANYROM+AROMA) (smdk4x12_Kitkat-Lolypop_Marshmallow official/old_builds)

build wih GCC 6.0 UBERTC which promises to give good user experience
[Galaxy S III Original Android Development] SamuelMaki:
What happened to the ondemand governors? The battery saving one always worked the best for me.
[Galaxy S III Original Android Development] somoy1996:
will this kernel work for cm13 based roms?

and how to modify this kernel?

and what is the difference between 4.5.5 and 5.10.3??

i want to use it for ressurection remix cm13 and beanstalk rom :/ help please

Edit:

Using 4.5.5 cm11_cm12+ on RR, works great, thank you :)
[Galaxy S III Original Android Development] orsonbear:
[MENTION=4365701]psndna88[/MENTION]

Please, can you add in Agni control an option to choose how much zram devices must be used? (typical 1 to 4). Thanks for your great work and your consideration!
[Galaxy S III Original Android Development] MrBeckham666:
try cm13 by temasek :) this is great rom :)

version 4.5.5 smdk4x12 for CM rom :)
[Galaxy S III Original Android Development] gpjm15:
It's my first time to see this rom. Is this available for Resurrection Remix MM i9300? And what is the config app for this?
[Galaxy S III Original Android Development] goldbeard:
yes, its available for RR rom..use the below version and it auto installs the agni control app on flashing this kernel....

PSN_pureCM_11_12+_smdk4x12_ANYROM-AROMA-v4.5.5_I9300_OC
[Galaxy S III Original Android Development] The Funky Pear:
Well i have to say that uber GCC works wonders.indeed better user experience.

Great job as always.!
[Galaxy S III Original Android Development] exe98123q:
on shv e210k stock 4.4.4 latest, kernel PSN_pureCM_11_12+_smdk4x12_ANYROM-AROMA-v4.5.5_I9300_OC not working

can that be fixed ?
[Galaxy S III Original Android Development] shalushahil:
should i flash this kernal again when my rom is updates??
[Galaxy S III Original Android Development] tornado06:
Yes you have to. There is no survival option like boeffla kernel, at the Agni-control panel.
[Galaxy S III Original Android Development] dimuthu7:
Did anyone try this rom with beanstalk cm 13 rom
[Galaxy S III Original Android Development] orsonbear:
[MENTION=4365701]psndna88[/MENTION]

Thanks for you works and your brilliant ideas! I'm using your Agni kernels, have noticed that your init.d statement involved in creating a zram disk

echo 1 > /sys/block/zram0/initstate

related also to zram 1-3, generates an error of permission denied in any kernel, yours and stock ones, and doesn't have any effect coz excluding it the zram disk created is working well anyway...

Thanks!
[Galaxy S III Original Android Development] rusherrrx:
Up i want to try this rom any bugs?
[Galaxy S III Original Android Development] Scorpionea:
This is kernel not a rom [emoji14] [emoji14]
[Galaxy S III Original Android Development] rusherrrx:
ohh yeaa hahhahahah so this is the one you are talking about the other post?
[Galaxy S III Original Android Development] Scorpionea:
Yes that is correct, 5.10.3
[Galaxy S III Original Android Development] rusherrrx:
not familiar with this kernel is this preconfigured? like there is no more tweaking needed
[Galaxy S III Original Android Development] Scorpionea:
Download this one for PA

http://xdaforums.com/devdb/project/dl/?id=18497

Flash it in recovery ,follow aroma installer and then u will have new app in appdrawer for controlling and tweaking the kernel
[Galaxy S III Original Android Development] rusherrrx:
why is boeffla not working
[Galaxy S III Original Android Development] Elveneleven:
Hi,

Does this Kernel have an cifs module and if so how can it be activated? I can't find it in the features list or in the agni control app.

Thanks
[Galaxy S III Original Android Development] ThePzyDuck:
Wich is the lastest (anf fastest) buil for MM CM13? I9300 of course. Thanks!!
[Galaxy S III Original Android Development] Anewkine:
Hi,

With RR 5.7.3, I use 4.5.5 version.

Envoyé de mon GT-I9195 en utilisant Tapatalk
[Galaxy S III Original Android Development] exe98123q:
working for anyone who have shv e210k ?any links ?
[Galaxy S III Original Android Development] Mekanik97:
How i can flash this damn modified CWM and f2fs files?! im searching it for hours but can't find anything... You should guide noobs like me. Lastly is it working on CM13?
[Galaxy S III Original Android Development] Chuyine:
I can change the state of SELinux to enforcing?
[Galaxy S III Original Android Development] ali.akbar01:
How to Update?

How can i update AGNi kernel? It's current version is 4.9x which came by flashing MIUI 7.
[Galaxy S III Original Android Development] AbayefD:
For what rom this kernel?
[Galaxy S III Original Android Development] bandit.67:
For roms AOSP based
[Galaxy S III Original Android Development] AbayefD:
CM 11 and SlimKat supported?
[Galaxy S III Original Android Development] bandit.67:
I've tryed with CM but not work properly,Slim ok
[Galaxy S III Original Android Development] SuDGLaD:
Hello guys,

excuse me, I have tried but have not been answered.

This kernel works with the resurrection remix 5.7.4 (MM)?

Thanks in advance to those who will answer me.
[Galaxy S III Original Android Development] rochr4:
preload SWAP mechanics ?

Could You share some info how this SWAP is created ?

Is '/dev/block/mmcblk0p10' being formatted as linuxSWAP partition after action in 'AGNi control' app ?

Is a file on '/preload/*.swp' created and mounted on as loopback by losetup ?

I made it f2fs in TWRP 3.0.2.2:

~ # mkfs.f2fs /dev/block/mmcblk0p10

F2FS-tools: mkfs.f2fs Ver: 1.6.1 (2016-03-22) [modified by Motorola to reserve space]

Info: Debug level = 0

Info: Label =

Info: Segments per section = 1

Info: Sections per zone = 1

Info: Trim is enabled

Info: sector size = 512

Info: total sectors = 1146880 (560 MB)

Info: zone aligned segment0 blkaddr: 512

Info: format version with

"Linux version 3.0.101-CM-g3c3a954 (jenkins@build) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Sat Dec 3 11:57:39 EST 2016"

Info: Discarding device: 0 sectors

Info: Overprovision ratio = 8.700%

Info: Overprovision segments = 51 (GC reserved = 30)

Info: format successful

~ # blkid

/dev/block/mmcblk1p1: UUID="10e122da-68bd-4389-a11a-664bf8f88e01" TYPE="f2fs"

/dev/block/mmcblk0p12: UUID="1a6f340e-a728-4b54-94f7-c82e457c69df" TYPE="f2fs"

/dev/block/mmcblk0p10: UUID="0a6092f6-ed7c-4759-8587-233594d8c055" TYPE="f2fs"

/dev/block/mmcblk0p9: UUID="0e2f8b83-dddd-421f-9604-15986753e54c" TYPE="f2fs"

/dev/block/mmcblk0p8: UUID="340d61d2-33a8-4ded-b365-8acf1a6a3c41" TYPE="f2fs"

/dev/block/mmcblk0p3: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

blkid after reboot on running OS '[ROM][6.0.X][AOSP]Haxynox for i9300(20160808)' shows:

adb shell blkid

/dev/block/loop0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

/dev/block/zram0: UUID="bb37e46f-54ab-443f-98fb-33a667d2a4db" TYPE="swap"

/dev/block/mmcblk0p3: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

/dev/block/mmcblk0p8: UUID="340d61d2-33a8-4ded-b365-8acf1a6a3c41" TYPE="f2fs"

/dev/block/mmcblk0p9: UUID="0e2f8b83-dddd-421f-9604-15986753e54c" TYPE="f2fs"

/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

/dev/block/mmcblk0p12: UUID="1a6f340e-a728-4b54-94f7-c82e457c69df" TYPE="f2fs"

/dev/block/mmcblk1p1: UUID="10e122da-68bd-4389-a11a-664bf8f88e01" TYPE="f2fs"

afterwards in recovery it is recognized as ext4 also.

I migrated my whole device to f2fs thanks to Your awesome kernel, OP link 'F2FS_PRELOAD_FORMAT_I9300-signed.zip' is dead on dev-host site so I can't flash it or pick inside, could You pls repost those file or tell us how it is done, maybe recent recovery twrp-3.1.1-0-i9300.img got better f2fs tools? I will try it later and share.

Thank You Sir psndna88

p.s. wall of text, excuse.
[Galaxy S III Original Android Development] Yank555:
Agreed, but there is a second lesson, far more important imho, that still hasn't been learned I'm afraid, and that is one that really should. And there are many many more who would need to learn that one than a dev testing their stuff.

But you're right, 'nough said, I close the topic with this post.

Hope psndna88 will review the info I posted and hopefully be able to make a kernel that eventually "repairs" those touchscreens.

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6b-beta1 (Linux 3.0.80) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] Tuga2010:
I´m one of the unfortunate , and was angry when this happened .

Now I have reflected some hours , and discussing with who as the blame leaves no where .

So I suggest that people ( devs , non-devs ... ) try to help with ideas to solve this problem .

I´ve made a research on google, and leaded me to this forum and others with the same problem before. The solution was allways , send it to warranty to replace the front part of the device.

If some kind of file would solve this problem , will be the first one.

I want to leave a word to the likes of codeworkx and Yank555, to even went here in this topic, get your atencion in your freetime , to this problem and tried to fix with your help , would be much apreciated . So seriously ... thank you :good:

regards
[Galaxy S III Original Android Development] SnowPluralism:
Boa Sorte Companheiro!

Good Luck With It Mate
[Galaxy S III Original Android Development] nazfalas:
So...another victim here. We here all know the risks of flashing kernels/ROMs...so no one to blame here...but still angry right now as I need my phone and can't use it now.

Again:

I knew the risks...hope the devs figure something out...
[Galaxy S III Original Android Development] AndreiLux:
Before there's any more white knight replies and theories evolve here on how to try to fix the issue:

You're out of luck. I've tried to fix this extensively a few months ago for a user who (stupidly) flashed a Note 2 firmware on his 9305.

I force flashed the device's correct firmware by rewriting the flash logic successfully, but the touch controller would give an electrical error signal back which signified hardware failure. I spent quite some time researching the issue.

Only fix was a warranty resend of the device.

As for devs: use automation scripts, it gets rid of the human error factor on such issues.

PS: You can use a mouse via OTG meanwhile if you want to do anything with the device.
[Galaxy S III Original Android Development] psndna88:
i have immediately removed the affected v2.2 links seconds after1st brick report. v2.1 links are error free

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] psndna88:
there are automated scripts already... new v2.2 defconfig for named as s3 turned out to be actually for note2...

.

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] spoonymoon:
Oh crap

So what were talking about here is a physically burned touch controller (hardware failure) that cant in any way be fixed?

and theres no use in waiting for a software fix, because its actually broke? :crying:

damm:: but hey like you all point out, theres a risk in flashing every time, and i sure dont ´want´ something to happen to psndna88 at all !!

he made a big mistake (not testing before release) and theres nothing we can do about it seems - well s... happens

gonna prepare my s3 for a ride with postal service then :(

thanx to all devs who looked into this - appreciate it :)
[Galaxy S III Original Android Development] psndna88:
i regret to say that that would certainly be next step because even if i comple a repair-attempting kernel as mentioned in above posts... its not gonna work ... technically (MELFAS touchscreen controller) is most possibly ruined by (MELFAS_NOTE driver).

i didnt have time to test it at that moment before release as i tried to batch publish CM v2.2 kernels(I9300,N7100,N7105) in short time i had... certainly ended up badly.

so on reading 1st report of such touch failure i immediately removed all batch published v2.2 kernels for all above mentioned devices as safety precaution. now i have recompiled, verified (+ included a prop assert check too) them and are ready to be published.
[Galaxy S III Original Android Development] amppen:
I think it could still be worth a shot. It's inductive reasoning to assume, based on one or few examples, that HW is toasted. Different people have probably played with the faulty devices for different amounts of time, and different individual hardware can have different tolerances for such an error. Just saying.
[Galaxy S III Original Android Development] psndna88:
im gonna make a repair attemptimg test kernel as a last ditch effort to revive those devices

edit: some info: that bad boot.img had s3 ramdisk i think damage might hav been more if it had n2 ramdisk.
[Galaxy S III Original Android Development] spoonymoon:
Yes pls try that, its worth a shot (if we dont brick it completly?) but let´s try :eek:

(Out of thanks for today)
[Galaxy S III Original Android Development] psndna88:
try this http://d-h.st/iVy

repair attempt CM kernel

INFO for devs about this attempted repair kernel:

--- /Working_Directory/I9300/kernel_source/CM-10.1/AGNi-pureCM/drivers/input/touchscreen/mms_ts.c~	2013-04-27 12:34:22.400767280 +0530

+++ /Working_Directory/I9300/kernel_source/CM-10.1/AGNi-pureCM/drivers/input/touchscreen/mms_ts.c	2013-06-10 13:42:55.032689053 +0530

@@ -1890,7 +1890,7 @@

}

/* 4.8" OCTA LCD FW */

-	if (ver >= FW_VERSION_4_8 && ver != 0xFF\

+	if (ver != 0xFF\

&& ver != 0x00 && ver != 0x45) {

dev_info(&client->dev,

"4.8 fw version update does not need\n");
[Galaxy S III Original Android Development] spoonymoon:
-------------------------------------------------

Thx installs, sound and all - but no touch still :(
[Galaxy S III Original Android Development] psndna88:
im gonna make last attempt now !
[Galaxy S III Original Android Development] psndna88:
test this http://d-h.st/i5K

repair attempt 2

info for devs about this:

--- /Working_Directory/I9300/kernel_source/CM-10.1/AGNi-pureCM/drivers/input/touchscreen/mms_ts.c~	2013-04-27 12:34:22.400767280 +0530

+++ /Working_Directory/I9300/kernel_source/CM-10.1/AGNi-pureCM/drivers/input/touchscreen/mms_ts.c	2013-06-10 14:45:27.756792846 +0530

@@ -1890,12 +1890,12 @@

}

/* 4.8" OCTA LCD FW */

-	if (ver >= FW_VERSION_4_8 && ver != 0xFF\

+	/*if (ver >= FW_VERSION_4_8 && ver != 0xFF\

&& ver != 0x00 && ver != 0x45) {

dev_info(&client->dev,

"4.8 fw version update does not need\n");

goto done;

-	}

+	}*/

while (retries--) {

ret = mms100_ISC_download_mbinary(info);
[Galaxy S III Original Android Development] spoonymoon:
------------------------------------------------------------------

Nope, no change :(

thanx for trying :good:
[Galaxy S III Original Android Development] psndna88:
recompiled, verified and tested v2.2 and uploaded it.
[Galaxy S III Original Android Development] temasek:
U have my morale support.

Be strong.
[Galaxy S III Original Android Development] Theshawty:
There is a wise saying in Latin.

"Errare humanum est"
[Galaxy S III Original Android Development] codeworkx:
another variant would be to update the firmware via fw file on sdcard.

Flash kernel with attached patch applied.

Boot it.

Copy melfas_fw.bin onto your internal sdcard.

/sdcard/melfas_fw.bin

And then run:

echo fw_update > /sys/class/sec/tsp/cmd

Don't ask me where to get the needed file.
[Galaxy S III Original Android Development] codeworkx:
any success?
[Galaxy S III Original Android Development] amppen:
!

I'm holding my breath here too, someone say something! Sorry for getting involved here but I really feel bad for all the bricks and for the dev too.
[Galaxy S III Original Android Development] spoonymoon:
---------------------------------------

thanks a lot Codeworks much appreciated 4 sure :highfive:

But i only get to the point where i flash kernel-i9300-FORCE_TS_FW_FLASH-DANGER-signed.zip reboots - i see the samsung logo and then black screen !! Cwm still there and download mode - but no more, flashed it on rooted stock rom and no booting up?

installing stock again now

:D
[Galaxy S III Original Android Development] codeworkx:
it's a CM kernel, no stock one.
[Galaxy S III Original Android Development] spoonymoon:
ohh sorry my bad ;)

installing cm10.1 shortly and then trying again

momento..:rolleyes:

Edit - it booted ok on cm 10.1 but same 0 no touch :(
[Galaxy S III Original Android Development] Tuga2010:
How can i transfer this file .zip to philz recovery ?

thanks
[Galaxy S III Original Android Development] codeworkx:
ok, seems we need a melfas_fw.bin for i9300.

but dunno where to get it from. maybe it's possible to dump it from a working device.

another option is via the samsung service mode menu. it normally allows your to reflash the firmware.

but without touch this could be damn tricky. :D
[Galaxy S III Original Android Development] DualJoe:
Can we dd it out from there as well?

But who knows what impact that bad FW had on the system. Maybe it needs even more (data) restoration than just the original FW.
[Galaxy S III Original Android Development] psndna88:
do u know location so that i could possibly try to dump?

edit: i think by usb otg cable conected mouse service menu could be tried upon

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] psndna88:
in philz recovery,when usb connected,

mounts and storage>Mount mass storage..

mounts ur extsdcard as mass storage device.

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] codeworkx:
it's no blockdevice.

have a look at fw_write_image() and flash_writel().

maybe you can use flash_readl() to read it from the controller.

otg + mouse sounds like a option.
[Galaxy S III Original Android Development] spoonymoon:
Well flashed stock rom rooted, otg cable, installed triangleaway, booted to download, reset counter to 0, flashed stock again (counter still 0)

send it to claim warranty, so ill see what verdict is in a couple off days then :fingers-crossed:

but as expected i assume the digitizer got toasted - well s... happens and theres no ´hard´feelings from my site for sure ;)

Thanx a mill to you gentlemen for trying to help out :highfive:

:laugh:
[Galaxy S III Original Android Development] AndreiLux:
The binary is no different than the .ihex firmware inside the kernel but just in a different format.

Maybe you missed this but I'll say it again: I already had to do this for a user once and the controller gave an electrical malfunction signal.

Here's the kernel I had made for the 9305: dl It shouldn't break anything else on the 9300 except the modem, but use at your own risk.
[Galaxy S III Original Android Development] codeworkx:
just that the binary must be a combination of all 4 regions.

boot, core, priv, publ.
[Galaxy S III Original Android Development] FakeMobile:
there is init.d support?
[Galaxy S III Original Android Development] psndna88:
ofcourse
[Galaxy S III Original Android Development] psndna88:
v2.2.1: 12-06-2013: reimplemented triangle away support which was overwritten by previous CM bulk update commit
[Galaxy S III Q&A, Help & Troubleshooting] dreamers1016:
Just wanna ask, is there a need to wipe data / factory reset before flashing XXEMC2 from XXELKC (both are WanamLite versions)?

It's a pretty old modem so wondering if there is a need to do so. Thanks !
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
No

No idea what old modem means ??

jje
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
as there is quote a difference in the firmware base I would suggest a format system and data and don't restore any system data, just apps and data
[Galaxy S III Q&A, Help & Troubleshooting] dreamers1016:
Hmmm... not modem. wrong term.

Should be baseband as the correct term.

So it means that I have to wipe the data completely in my phone?
[Galaxy S III Q&A, Help & Troubleshooting] slaphead20:
Best thing to do is try a dirty flash(no wipe) and if you have problems then you will have to do a clean flash with data wipe....add always, backup...backup...backup
[Galaxy S III Q&A, Help & Troubleshooting] Striatum_bdr:
I don't know those roms but no need to change your modem if your phone is working right. I think a Rom should come without modem.
[Android Apps and Games] charles1111:
Nfs mw on galaxy s duos

To download the game search in Google nfs mw

Well don't wory whether the download is not for our phone.just download it....

-------------------------------

Now may be ur question is the installation is nearly 1.8 GB and our s duos has only 1.6 or 1.7 installation memory

So don't wory install the app external2internal on ur galaxy s duos may help you out(search in forum you will know how to use the app external2internal)

Now mostly ur done...

Now download the nfsmw apk with data from any where...

The version I downloaded was v1.28

Here we go with some screen shots...

View attachment 1877330

View attachment 1877332

View attachment 1877335

View attachment 1877336

View attachment 1877337

View attachment 1877340

View attachment 1877341

View attachment 1877343

View attachment 1877344

View attachment 1877345

For YouTube playback of nfsmw on s duos go here

https://www.youtube.com/watch?v=PKyFJm6yXNc&feature=youtube_gdata_player

Have fun...

Sent from my gt-s7562 using stock Rom pimped by app pimp my rom
[Android Apps and Games] nimeshlmcp:
Which other big games are working on s duos..

Sent from my GT-S7562
[Android Apps and Games] charles1111:
Well gta 3 is working and mw and more bt haven't tested

sent from galaxy s duos with pimped Rom
[Android Apps and Games] parkhajoon:
I have installed Root External to Internal Sd . It work so good and even my phone was little faster than b4. How to change it back to earlier . And what will happen if remove the external sd card after swap.
[Android Apps and Games] charles1111:
If u haven't enable the intd support u just restart ur phone it will come to its original state....

sent from galaxy s duos with pimped Rom
[Android Apps and Games] parkhajoon:
Yeah, I got it. Thanks man.
[Android Apps and Games] parkhajoon:
I have a questions to u Charles1111, whenever I want to restore my nandroid backup, we have enter recovery mode, but (mine) I always have to first go to download mode > Odin> recovery mode> then only restore backup. Is there any other where I can directly go to recovery mode and restore backup without using computer or Odin?
[Android Apps and Games] charles1111:
I think u haven't got the permanent cwm....

sent from galaxy s duos with pimped Rom
[Android Apps and Games] parkhajoon:
How-to get it.
[Android Apps and Games] charles1111:
Go to droideiser forum he had shown a good way to get u cwm permanent

http://www.droidiser.com/2012/10/how-to-root-samsung-galaxy-s-duos-install-cwm.html?m=1

sent from galaxy s duos with pimped Rom
[Android Apps and Games] parkhajoon:
Thanks man, did it. It seems that u have pipped ur Rom too. Is it safe, don't know what to install . Thanks again.
[Android Apps and Games] charles1111:
Go for its safe....

sent from galaxy s duos with pimped Rom
[Android Apps and Games] pavankiran56:
Hi charles1111,

i tried to run NFS mostwanted and shift on s duos but i get blck screen error can u provide me the links with whihc u have sucessfully installed and playing this game thanks in advance

i mean not sure if external2internal app would on a sdcard that is not partitioned or so what is the procedure you follwed it would be great help if share it with us . i tried many versions of nfs apk some only start if connected to internet intially dnt knw why.

im able to run replusez and other games
[Android Apps and Games] charles1111:
Hey the data which I had for nfs was of tab 2 and which run like a charm on my duos...

Take Ur time and Google how to use the external to internal app on s duos....