yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] psndna88:
08-04-2016 Update v4.5.2(ANYROM+AROMA) (smdk4x12_Kitkat-Lolypop_official/old_builds)

staging: iio: use monotonic time since boot for event timestamps | cpufreq: pegasusq: boost: add support for setting a boost freq/cpulock,tone down the logspam,don't NULL timer function,drop more debugging | sensor: lsm330dlc: allow exposing in /dev/input | crypto: testmgr - add empty test vectors for null ciphers | KEYS: Fix race between read and revoke. This fixes CVE-2015-7550 | include/linux/poison.h: fix LIST_POISON{1,2} offset | BACKPORT: pagemap: do not leak physical addresses to non-privileged userspace | bcmdhd: Add checks for stack buffer overflows | net: wireless: bcmdhd: Add checks for stack buffer overflows | net: wireless: bcmdhd: check packet length for event messages | tty: Fix unsafe ldisc reference via ioctl(TIOCGETD) | mm: reorder can_do_mlock to fix audit denial | __ptrace_may_access() should not deny sub-threads | ext4: make orphan functions be no-op in no-journal mode | net: fix iterating over hashtable in tcp_nuke_addr() | net: add validation for the socket syscall protocol argument | bluetooth: Validate socket address length in sco_sock_bind() | tracing/syscalls: Fix perf syscall tracing when syscall_nr == -1 | tracing/syscalls: Ignore numbers outside NR_syscalls' range | net/l2tp: don't fall back on UDP [get|set]sockopt | KEYS: close race between key lookup and freeing | net: ipv4: current group_info should be put after using. | mnt: Only change user settable mount flags in remount | mnt: Prevent pivot_root from creating a loop in the mount tree | vfs: read file_handle only once in handle_to_path | fs: take i_mutex during prepare_binprm for set[ug]id executables | android: drivers: workaround debugfs race in binder | net: add length argument to skb_copy_and_csum_datagram_iovec | md: use kzalloc() when bitmap is disabled | KEYS: Fix handling of stored error in a negatively instantiated user key | vfs: new internal helper: mnt_has_parent(mnt) | vfs: more mnt_parent cleanups | Staging: android: binder: Add some tracepoints | Revert "udp: remove redundant variable" | fuse: break infinite loop in fuse_fill_write_pages() | pipe: iovec: Fix memory corruption when retrying atomic copy as non-atomic | input: Don't use monotonic time for event time stamps. | Input: add infrastructure for selecting clockid for event time stamps | mfc5x: update from n7100 source drop | pipe: Fix buffer offset after partially failed read | agni control installed as system app
[Galaxy S III Original Android Development] yoahmad1995:
What builds works on nameless I'm confused lol.
[Galaxy S III Original Android Development] SamuelMaki:
Stock-based, the other is for KK and Lollipop.
[Galaxy S III Original Android Development] yoahmad1995:
Yes I know but I'm confused which one to pick from his download page. There is oc and non oc......
[Galaxy S III Original Android Development] SamuelMaki:
Newest stock-based for MM, the OC means just that it is possible, not that it's forced.
[Galaxy S III Original Android Development] whoadood:
What's the name of it? I'm completely and hopelessly lost.

http://xdaforums.com/devdb/project/?id=2502#downloads
[Galaxy S III Original Android Development] SamuelMaki:
The one with the biggest version-number as usual.
[Galaxy S III Original Android Development] molonad:
deleted
[Galaxy S III Original Android Development] SamuelMaki:
Just a bumb :) The issue remains in latest and in all the roms I tried, have to use another app to undervolt 200mhz and 300mhz (they are stuck at 900mV).
[Galaxy S III Original Android Development] psndna88:
i have not undervolted lower frequencies to avoid sod issue if any.
[Galaxy S III Original Android Development] yoahmad1995:
Is this kernel based on NG?
[Galaxy S III Original Android Development] psndna88:
v4.5.2_r2 smdk4x12:

Remove touchwake charger mode TO fix proximity sensor issue while call | Fix USB OTG and remove redundant AGNI_PURECM_MODE | cpufreq: remove power save framework support of stock roms | i930x: disable samsung_extdisp driver to fix CVE-2015-1801 | removed the experimental ondemand control stuffs
[Galaxy S III Original Android Development] psndna88:
Reuploaded v4.5.2_r2 smdk4x12:

-cleanup and fix derp in configs
[Galaxy S III Original Android Development] kingdj:
Which version compatible with pure cm13 nightly version ?? Regards
[Galaxy S III Original Android Development] MrBeckham666:
support cm13 rom by temasek ?

support cm13 rom by temasek ?
[Galaxy S III Original Android Development] schizyk12:
Lol, how to download ur kernel, omg i'm too stupid for this.. I use cm13 and I want download ur kernel first time and I dont know how

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] sunny1234590:
There's a download tab, right? Click on it. Then select the latest kernel build and download it. Then flash it.

Done!

P.S: 4.5.2_r2 would work
[Galaxy S III Original Android Development] MrBeckham666:
what is the most frugal profile cpu?

boeffla of these are good? if there are any better?
[Galaxy S III Original Android Development] sleeper994:
Anyone using this with latest RR?
[Galaxy S III Original Android Development] sunny1234590:
I use Zanezam governor or PegasusQ default governor. It depends on personal use.

---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------

You can try. It will work.
[Galaxy S III Original Android Development] psndna88:
Reuploaded v4.5.2_r2 smdk4x12:

- fixed sec dock freeze
[Galaxy S III Original Android Development] psndna88:
19-04-2016 Update v5.10.1 (Stock-sources based)

i930x: disable samsung_extdisp driver to fix CVE-2015-1801 | remove touchwake charger mode | re-enabled switched-off-carging for stock kernels with old pre-kitkat bootloaders | mfc5x: enable SUPPORT_SLICE_ENCODING only for AGNi pureSTOCK | remove the experimental ondemand control stuff
[Galaxy S III Original Android Development] sleeper994:
Can i flash this over boeffla kernel, or should I go back to stock CM kernel before flashing this?
[Galaxy S III Original Android Development] psndna88:
over stock cm kernel only.
[Galaxy S III Original Android Development] rp158:
[MENTION=4365701]psndna88[/MENTION], thanks for your kernel! Run it on i9300 /Slim5.1 now and got an extra hour SOT.

1. There's a folder sdcard0/AGNi_efs_backup created, but unused.

2. Minirequest: would you make kernel's busybox a bit richer? I kept my shell-scripts simple and they run fine on Slim stock kernel and most LP- and MM-ROMs without installing busybox, but on Agni they struggle over else.
[Galaxy S III Original Android Development] djfox84:
My GT i9300 have boeffla kernel, can install directly this kernel agni? Or whats steps should i follow?
[Galaxy S III Original Android Development] psndna88:
ill try make latest Busybox

with lot options

install cm rom then flash agni.

for non-stock roms, stock standard rom's kernel should b present prior to flashing agni.
[Galaxy S III Original Android Development] AliTajelsir:
[MENTION=4365701]psndna88[/MENTION], I couldn't flash the kernel 5.10.1 although the flashing process would be completed successfully and only the AGNi control app was installed.

Using Haxynox ROM MM build 19/4, stock kernel, Super SU 2.65 and Xposed v83

What am I doing wrong?

Thanks in advance. Keep up the great wrok.

Here is the log file.
[Galaxy S III Original Android Development] MrBeckham666:
for custom rom flash version PSN_pureCM_11_12+_smdk4x12_ANYROM-AROMA-v4.5.2_r2_I9300_OC.zip

good rom is http://xdaforums.com/galaxy-s3/development/rom-temaseks-unofficial-cyanogenmod-13-t3286265
[Galaxy S III Original Android Development] foober:
I don't know which version i must flash on teamsek ROM (Android 6.)? Thx

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Original Android Development] rchtk:
Neither do I on nameless ROM based on cm13. There are a lot of links.. My first try resulted in a bootloop.

The very detailed changelog is much appreciated.

But on a phone scrolling is not easy. I'd suggest moving links to the top or moving changelog to the second post.

Cheers
[Galaxy S III Original Android Development] Glebun:
I just think devs should test their work before sharing it with others.

This has happened before, the only way is to replace the screen.
[Galaxy S III Original Android Development] codeworkx:
might be just because of the wrong firmware which got flashed on the touchscreen controller.

brewing a kernel which forces a flash of the correct firmware on boot might fix the issue.

did something similar a year ago on my own i9100. ;)
[Galaxy S III Original Android Development] psndna88:
can u spend some time for this?

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] Glebun:
if I were you I would pay him to spend some time on this :D
[Galaxy S III Original Android Development] codeworkx:
maybe on the next few days.
[Galaxy S III Original Android Development] spoonymoon:
that SURE would be nice of you gentlemen if some workaround could be made :rolleyes:

---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------

Gladly :fingers-crossed: 50$ on paypal ready if...?
[Galaxy S III Original Android Development] Yank555:
Would it be enough to uncomment :

/* #define FORCE_FW_FLASH */
/* #define FORCE_FW_PASS */

in "drivers/input/touchscreen/mms_ts.c" (lines 22 and 23) ?

Haven't looked further, just wanted to share this asap...

JP.

EDIT: Scratch that, looked nice'n'easy, but it's used nowhere...
[Galaxy S III Original Android Development] Tuga2010:
We all be thankfull for that . :good:

PS : I´m limited to 8 "thanks" per day :p

regards
[Galaxy S III Original Android Development] Yank555:
Maybe worth having a look here (or in that #ifdef block) :

eISCRet_t mms100_ISC_download_mbinary(struct mms_ts_info *info)

(same file, line 1265 in my sources)

JP.
[Galaxy S III Original Android Development] davtse:
I have to agree with this. I think being a member of XDA and downloading developmental apps or software of any sort means you implicitly accept the risk of bricking your device.

Developers who willingly and freely share what they have with others are far and few. Continue to point fingers and abuse them and soon they'll become extinct.
[Galaxy S III Original Android Development] Glebun:
but I still don't understand, what's the appropriate reaction of people whose phones are dead because of him?

should they thank him because he shared his work with them? I don't get you guys.

:laugh:
[Galaxy S III Original Android Development] psndna88:
ill check that in morning.. its midnight Here i am refraining to do sensitive code-looking in sleepiness.

till then i request u to look more.. a Dev tends to understand a dev more better

Sent from I9300 PureLook HD v6.1 XXEMD2 4.1.2 + AGNi pureSTOCK v2.2.1 kernel
[Galaxy S III Original Android Development] Yank555:
The apropriate reaction would be to just do nothing unless you can help. If you are in the case of someone with an impacted device and don't know how to help, just keep reading and hope for the best, but don't blame the dev., noone, and I repeat, not a single person forced any of them to download and flash the kernel.

So let me put this as clearly as I can :

- the dev. bears the responsibility for his mistake, and psndna88 more than made clear that he does

- the user bears the responsability to have flashed

knowningly

something that could lead to where he is now

So either we now spend posts and time blaming each other, or we use that time to figure out if there is anything we can do to save those devices.

Finger pointing will by no means help anyone involved, which is why I said to refrain from posting.

Want an example of a good reaction : Codeworkx gave us a path to possibly fix this, that indeed is an appropriate reaction.

JP.

---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------

It's getting late here as well, hard week at work ahead. I'll keep looking as I can, anyway feel free to contact me for anything, if I can help, I gladly will. But I must be honest, I haven't looked at firmware flashing code up until now, so it's all a learning process on my end.

JP.
[Galaxy S III Original Android Development] davtse:
I've bricked phones before as well. Was I angry? Sure. But not at the developer. Its an unspoken agreement that you flash things at your own risk. If you dont want to risk it, dont flash it.

I'm not telling you how you should or should not react. At the end of the day you dictate how you want to react. The point yank555 and I am trying to drive across is this. There is already little to no incentive for developers to share their work. You don't have to thank them(although you should), but please don't abuse them. It only serves as a deterrent for other aspiring developers. In any case, I'm sure OP feels bad enough as it is.
[Galaxy S III Original Android Development] amppen:
Oh man, I have that file in my sdcard. I was going to flash it tomorrow to check it out, after my ongoing advanced body bias test runs. Good thing I'm in the middle of testing, I feel like I just dodged a bullet.

My sympathies for both the OP and all the people who took the hit :(
[Galaxy S III Original Android Development] Yank555:
OK, so the file that contains the firmware would be : drivers/input/touchscreen/MMS100_ISC_Initial.h

This should be the file that helps load the firmware : drivers/input/touchscreen/mms100_ISC_download.c

The firmware update is handled here : drivers/input/touchscreen/mms_ts.c

static int mms_ts_fw_load(struct mms_ts_info *info)
{

struct i2c_client *client = info->client;
struct i2c_adapter *adapter = to_i2c_adapter(client->dev.parent);
int ret = 0;
int ver, hw_rev;
int retries = 3;

ver = get_fw_version(info);
info->fw_ic_ver = ver;
dev_info(&client->dev,
"[TSP]fw version 0x%02x !!!!\n", ver);

hw_rev = get_hw_version(info);
dev_info(&client->dev,
"[TSP]hw rev = 0x%02x\n", hw_rev);

pr_err("[TSP] ISC Ver [0x%02x] [0x%02x] [0x%02x]",
i2c_smbus_read_byte_data(info->client, 0xF3),
i2c_smbus_read_byte_data(info->client, 0xF4),
i2c_smbus_read_byte_data(info->client, 0xF5));

if (!info->pdata || !info->pdata->mux_fw_flash) {
ret = 1;
dev_err(&client->dev,
"fw cannot be updated, missing platform data\n");
goto out;
}

[COLOR="Red"][B]	/* 4.8" OCTA LCD FW */
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;
}[/B][/COLOR]

while (retries--) {
ret = mms100_ISC_download_mbinary(info);

ver = get_fw_version(info);
info->fw_ic_ver = ver;

if (ret == 0) {
pr_err("[TSP] mms100_ISC_download_mbinary success");
goto done;
} else {
pr_err("[TSP] mms100_ISC_download_mbinary fail [%d]",
ret);
ret = 1;
}

dev_err(&client->dev, "retrying flashing\n");
}

out:
return ret;

done:

#if ISC_DL_MODE	/* ISC_DL_MODE start */
pr_err("[TSP] ISC Ver [0x%02x] [0x%02x] [0x%02x]",
i2c_smbus_read_byte_data(info->client, 0xF3),
i2c_smbus_read_byte_data(info->client, 0xF4),
i2c_smbus_read_byte_data(info->client, 0xF5));
#endif

ret = mms_ts_finish_config(info);
return ret;
}

From what I see, current firmware version would be : "#define FW_VERSION_4_8 0xBB"

So changing :

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

to :

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

should do the trick.

Or plain to :

if (ver != 0xFF\

Or just comment out the whole if ;)

I do hope this will help !!

JP.

PS: [MENTION=2633650]Glebun[/MENTION] : See I could just have not cared and watched a movie or gone out etc., instead I'm using my free time trying to help out... anyway I don't get your way of thinking, should we devs pay you and be thankful for you using our stuff ??

PPS: Thanks to faux123 guiding me where to look for this, since I never even came close to such driver firmware updating stuff.
[Galaxy S III Original Android Development] spoonymoon:
--------------------------------------

You´re the best Yank555 - and Very skilled :victory:

hope this could lead to a fix?

thank you soo much :highfive:

-------------------------------------
[Galaxy S III Original Android Development] Yank555:
I could give you a counterexample :

I just pushed an update of my kernel today, 5 kernels, 3 for i9300 and 2 for i9305. That took me the best part of my sunday. Kay, I'm home as I'm not feeling too well (cold), so I had time to do it, but nonetheless, I could have spent my sunday on my couch wachting TV or even sleeping. I only need one of these 5 kernels myself, but well, since some people find them useful I kind of feel compelled to maintain all 5 of them, even if for 3 only a very few users really downlad them, but I'd feel bad to leave them out still.

I did indeed test the 3 i9300 kernels, but I cannot test the i9305 kernels due to lack of having such a device.

Now I make these i9305 kernels because I got asked to, and I agreed but with the clear idea of "you'd have to be the testers guys".

Also I have a 2nd S3 that I only use to test stuff, so today I resoted 2 nandroids to test the kernels for the ROMs I don't use as daily drivers.

What I want to say with this is, it's neither really easy nor a black&white kind of thing !

Users begging, rushing to get updates to feed their flashing additction and us wanting to please everybody ... are all things that make (unnecessary) pressure on devs.

And rushing, in any kind of way, can make us do mistakes. We all do at some point, good thing is generally these are only tiny things like boot loops or reboots and such, but well, sometimes worse can happen.

So look at the reaction [MENTION=4042238]amppen[/MENTION] posted, that's the kind of reaction that I consider adequate, he just felt sorry for both the dev and the users (and happy for himself not to have been one of them).

Now let's just hope Codeworkx idea is proven right and those phones can be saved without replacing the screen.

JP.
[Galaxy S III Original Android Development] danarama:
Yes, always test you're own products on your own device before releasing to the public but I think the OP has learned that lesson the hard way. There's no doubt he feels bad about it. I'm not sure its constructive to continue going round in circles
[Galaxy S III Original Android Development] Jonny:
Enough, kindly move on... everybody. I will remove the link from the OP as it can pose a risk of a brick. OP I hope you've realised you made a mistake and I trust that you will do your best to put it right.
[Galaxy S III Original Android Development] goldbeard:
I have finally found that I have to flash v4.5.2_r2 smdk4x12 for RR cm13 rom but couldn't find the link for download.

Can someone pls share the direct link for download ?

Edit: found the link

http://xdaforums.com/devdb/project/?id=2502#downloads
[Galaxy S III Original Android Development] orsonbear:
Kernel PSN_pureCM_11_12+_smdk4x12_ANYROM-AROMA-v4.5.2_r2_I9300_OC breaks auto rotation on CM13 Temasek 7.4. Tnx!
[Galaxy S III Original Android Development] AliTajelsir:
Thanks.

I discovered that my problem was I flashed systemless Super SU then AGNi kernel and the opposite should be done or it wouldn't be installed.

I think AGNi kernel image patcher needs the stock custom ROM kernel not to be modified in any way.
[Galaxy S III Original Android Development] rp158:
As said in OP, Anykernels read some configs from boot.img, which is found at the flash. So, there must be one and a stock one. Also important for restoring backup.
[Galaxy S III Original Android Development] MrBeckham666:
13 cm of temasek is still in beta problem with auto rotation happening often than once without kernel agnii.

I believe if some version of rom temasek work to someone about it should do backup :) I'm on version 7.4 so far I complain in my opinion is one of the most interesting roms. Sory for my english :)
[Galaxy S III Original Android Development] orsonbear:
Have tried 3 times switching between Stock Agni and Boeffla, with Stock and Boeffla auto rotation works every time, with Agni sorry auto rotation doesn't works at any time. I prefer Agni however, hoping in a rotation fix! :)

I forgot to say the problem there isn't with CM12.1 :)
[Galaxy S III Original Android Development] Samsagax:
Could there be a version of the zip without AROMA? Is nice to have an unatended installation.
[Galaxy S III Original Android Development] rp158:
[MENTION=4365701]psndna88[/MENTION], allow me a general question about AnyKernel: if I restore a TWRP-backup, which contains your kernel, will kernel at next boot try to read some configs from previous ROM or does he use params, stored in backup?
[Galaxy S III Original Android Development] psndna88:
ill see that

no plans

no, only zip installer reads from previous installed kernel
[Galaxy S III Original Android Development] psndna88:
15-05-2016 Update v4.5.4(ANYROM+AROMA) (smdk4x12_Kitkat-Lolypop_official/old_builds)

ALSA: usb-audio: avoid freeing umidi object twice | ALSA: timer: Fix double unlink of active_list | ALSA: timer: Fix race among timer ioctls | ALSA: timer: Harden slave timer list handling | pipe: limit the per-user amount of pages allocated in pipes | ALSA: hrtimer: Fix stall by hrtimer_cancel() | usbnet: cleanup after bind() in probe() | USB: cdc-acm: more sanity checking | netfilter: x_tables: fix unconditional helper | ipv4: Don't do expensive useless work during inetdev destroy. | Switched to GCC 5.3.1 Linaro toolchain | mdm: revert to stock I9305 update

15-05-2016 Update v5.10.2 (Stock-sources based)

ALSA: usb-audio: avoid freeing umidi object twice | ALSA: timer: Fix double unlink of active_list | ALSA: timer: Fix race among timer ioctls | ALSA: timer: Harden slave timer list handling | pipe: limit the per-user amount of pages allocated in pipes | ALSA: hrtimer: Fix stall by hrtimer_cancel() | usbnet: cleanup after bind() in probe() | USB: cdc-acm: more sanity checking | netfilter: x_tables: fix unconditional helper | ipv4: Don't do expensive useless work during inetdev destroy. | Switched to GCC 5.3.1 Linaro toolchain | mdm: revert to stock I9305 update | enable CONFIG_SENSORS_LSM330DLC_USE_INPUT_DEV
[Galaxy S III Original Android Development] anwar_suppa:
In this update when ever I do changes to the Agni control all goes to default over and over again, Im using the older update now works fine.

You're Awesome doe and Thanks :good:
[Galaxy S III Original Android Development] orsonbear:
Agni v5.10.2, CM12.1 unofficial by rpdroky, all woks fine! Tnx!
[Galaxy S III Original Android Development] goldbeard:
+1 same issue..however, whatever I changed is reflected in kernel adiutor, so I think its a UI glitch...
[Galaxy S III Original Android Development] orsonbear:
Try wiping cache partition at any kernel update, this can solve some weird behaviour...
[Galaxy S III Original Android Development] andrescm:
First-time user of this kernel, currently using PSN_pureCM_12+_ANYROM-AROMA-v5.10.2_I9300_OC.zip. I too noticed that changes don't stick. I gave a try at Kernel Adiutor but it can't control some things like battery charging rate and Boeffla sound. So I'll try an older version.

At least in my case the issue persists after clearing both cache partitions.

EDIT: After switching to the immediately previous version, PSN_pureCM_12+_ANYROM-AROMA-v5.10.1_I9300_OC.zip, changes do stick now. If I'm right, it's really not that changes didn't stick, but that they weren't applied at all by the app.
[Galaxy S III Original Android Development] psndna88:
Reupoaded last version(s):-

with old working busybox
[Galaxy S III Original Android Development] goldbeard:
thanks..everything back to normal :):o
[Galaxy S III Original Android Development] rp158:
[MENTION=4365701]psndna88[/MENTION]: I flashed 5.10.2 from 15.05.16 and got no problems with reporting/viewing edits in the app.

But I neither saw any changes in my TerminalEmulator: the shell is by default linked to /system/bin/sh - and it still struggles over simpliest commands. Not a big item, but strange...
[Galaxy S III Original Android Development] psndna88:
i hve not placed its symlinkss to system...

its standalone binary

/sbin/busybox
[Galaxy S III Original Android Development] rp158:
deleted