yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Lanchon:
no, because it requires changing the stock kernel and i dont think that will happen. i discussed something like this with LA long ago and he didnt want to do it.

but if i were you i would try alternatives.

instead of mounting a partition to put the cpio file in, you can try:

either a) just dump the recovery cpio raw file into the RECOVERY partition space and use the /dev/what/ever partition as if it were the cpio file (if cpio extraction handles the padding) so no extra partition needs be mounted;

or maybe b) format RECOVERY in ext4, dump the recovery cpio file contents in there and do away with the recovery ramdrive. (recoveries do not mount/unmount RECOVERY so should work. but very ugly cause you would need to update recovery from android :( )
[Galaxy S II Original Android Development] lukss12:
It seems spaming with hours and hours of uptime has started and will not end! We know zeitferne kernel fixes the main freeze problem, please STOP! Now we already know too that a strange freeze and soft reboot is present due to some memory managment problem (that's what I think). When I have a little time I'll install facebook and chrome and try to force it to happen to collect some info with different zram configs. Till then, if anyone using freezefix kernel experience a soft reboot, recovering last_kmsg and dmesg will be very appreciated. Posting the same without a log is not useful.

Btw [MENTION=4141005]Lanchon[/MENTION] I had the same thought as you about using Recovery partition, the.ganster is right, I've never seen a PIT with less than 8 MB preload.

First of all, sorry about the blank quote I couldn't tag your name :confused:. Second, what have you tried so far? I'll try PolishVodka approach and don't want to waste time trying the same things that you had tried :sly::sly::sly:

About 500 Mhz bug, I found some weird things on the code related to lock frequency change while using decoders/encoders. But I'm studying for final exams and do not have time. It's 3 a.m here and the first time in the day I managed to read xda threads :S
[Galaxy S II Original Android Development] yosmokinman:
I don't trust TRIM AT ALL. Especially with the brickbug emmc's like VYL00M x19.

Please don't put that in official nightlies [MENTION=6159291]Lysergic Acid[/MENTION]

It may work fine a hundred times then brick out of nowhere. Don't potentially kill peoples phones.

If you do include it please make sure it is clearly stated.
[Galaxy S II Original Android Development] Naudiz:
lol, it's waaaay more likely that your old S2 will die from <insert any reason here> than from TRIM. Even Stock-Sammy Rom has TRIM enabled with a working patch for brickbug. [MENTION=4141005]Lanchon[/MENTION] has merged these patches into AOSP kernel and they have been tested for an eternity now. TRIM on S2 is as safe as on any other device nowadays.
[Galaxy S II Original Android Development] :
I have VYL00M x19 chip as well and it's safe. It's been safe for a long, long time. As long as the kernel is built with the correct patches there is no risk

Exactly
[Galaxy S II Original Android Development] good8life:
Perfectly working official cyanogenmod 12.1

I forgot about freeze 4 days !

I believe its good rom!

Thank you master : Lysergic Acid
[Galaxy S II Original Android Development] xhoster:
Little tip for some people who had to reset their phones pushing the power button for 10 seconds:

Check your filesystems! An error in /data or /system, even /sdcard0 could "cripple" your phone and cause soft reboots and slowdowns (there are still some other sources of slowdowns, but lets get rid of the obvious ones :) ).

Easiest way to do:

(READ FIRST AND DON'T WIPE YOUR PARTITIONS!)

- flash twrp kernel (can be found in this thread)

- go to wipe/advanced wipe

- check data/system/emmc (only one at a time and repeat following steps with each partition)

- press "repair or change filesystem" (DON'T SWIPE THE WIPE BUTTON!)

- press "repair" and wait for "done" msg

- go back and repeat for other partitions

If you encounter an error message like "ERROR=1" just repeat the repair process and see if it happens again. Normally this error just means "errors found and repaired".

Can be read in "fsck man" what they mean.
[Galaxy S II Original Android Development] wdevil12:
You Are The Man! I always wondered why manual soft rebooting after freezes or taking the battery out without switching off the phone could cause the infinitive bootloop on cm logo/samsung logo. I thought system gets corrupted due to the freeze. My workaround was restoring only system partition from backups. You saved the rest of my life! Thanks Bro!
[Galaxy S II Original Android Development] n3m3sis:
I have one small request for the rom. I have been using LA's rom since late September as a daily driver and by and large it is really very good.

The only gripe I have is that since I have been using the rom, my receiver volume is very low and I can hardly hear a caller unless it is really quiet around me. Likewise the caller can hardly hear me and keeps complaining of a bad line even with the volume turned up full.

Since about December, I did some exploring and found the tinyalsa-audio.xml file in /etc and by trial and error I have managed to get a really good volume on both my receiver and mic's (no more complaints from callers/called). The only problem is that every time I upgrade with a new nightly, I have to reset the settings all over again as the file is overwritten ( before you ask, saving the altered tinyalsa-audio.xml file and then overwriting the new one does not work, neither does cut and pasting the values from the saved one). Could I ask that the following values are altered from default in the rom so that I don't have to keep editing the tinyalsa-audio.xml file every time I update : Master Playback Volume (new value = "84"), DAC Playback Volume (new value = "85"), AD Analogue Volume (new value = "30"), Receiver Playback Volume (new value = "31"), <device type="builtin-mic"> AD Analogue Volume (new value="30"), Mic 1 Gain Volume (new value="3") <device type="earpiece"> AD Digital Volume (new value = "84"). I find that have plenty of volume adjustment with those settings, even in a noisy environment. Please LA, could you consider to change the default settings to these.?

Many thanks for your great work which has me holding on to my S2 for dear life and not upgrading to newer phone.
[Galaxy S II Original Android Development] rogers11:
Try this to backup and restore your changed file.
[Galaxy S II Original Android Development] n3m3sis:
Thank you for your reply however given the myriad ways I have tried to put back the altered file, or the contents thereof, everything results in the phone going silent, both in and out.

The only way to restore the volume is to apply the nightly again, then make the changes as outlined above in the tinyalsa-audio.xml file or the phone is too quiet. The changes always work however, so since that file is always overwritten by one with much quieter values everytime I update the nightly, I was just wondering how hard would it be to change the values in the xml file that comes with every new nightly.

Thanks once again for taking the time to answer.
[Galaxy S II Original Android Development] Lanchon:
actually LA and me both concur on the thought that NOT TRIMMING is what is dangerous and kills your emmc. on my end, my thoughts are usually justified by freely available or reproducible data, not by deep personal revelations while on ayahuasca. of course you are free to have your own thoughts.

that said, you can relax. i don't think LA will merge trim into official. (but i think he should, with a proper #ifdef covering only his devices: i9100, i777, d720 and n7000 are all tested safe). but there is a fair chance that he will merge trim into his unofficial TWRP-based kernel.

---------- Post added at 01:59 PM ---------- Previous post was at 01:41 PM ----------

well it's a big responsibility and a bit of a nuisance. first he needs to switch back to CM12.1 when he is working on CM13 to even look at your request, which i think in LA's case means downloading the CM12.1 sources again, which are probably gone because he was tight on space maybe.

then all changes have to be properly tested of course but he is not using CM12.1 i think, so he can't test and needs to put out a test kernel for others.

but most of all it's a big responsibility: many people have killed ear pieces and speakers by overdriving them. your cell operator could be sending low volume audio for whatever reason. or your earpiece could be partially damaged or dirty and does not move correctly. or maybe all are a bit quiet. but those settings are there for a reason. maybe samsung determined that, yes, its a low volume, but cranking it up would blast some speakers on some devices, so they toned it down.

what you ask is a tall order for a responsible maintainer.

if i were you, i would either:

a) find a solution for yourself

or b) get onboard the effort and fix this problem for all

to go with b) :

-first obtain consensus that something needs be done and its not that you have a defective device or out of spec operator.

-then test stock JB by sammy and verify that sound works better with that rom.

-then go and find the relevant entries in stock JB and show LA that the numbers on CM are over-conservative, and that it is safe to crank it up a bit.

-then maybe if you feel really helpful, submit your change to gerrit. but i guess LA can do it himself (if he downloads the code).

so to answer your question: yes, it's not that simple, it's just a bit hard, like all the work LA does.
[Galaxy S II Original Android Development] makix13:
Hi n3m3sis,

In my case, I install viper4android and it solves all my problems with sounds and enjoy a lot the music in my S2.

If you give a try and you have some issues please PM, to not spam the thread[emoji6]

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] n3m3sis:
Thank you Lanchon for your reply.

I do not have the time to learn all the skills that you have suggested (though I wish I had, as this stuff is where I used to be at).

I have reset the values everytime I update the nightly though with no ill effects. I understand that LA is on a new track as well with 13.0 so I think I will wait until the freezefix is merged with the nightlyies and make one last update. Then I will change settings again for the final time.

Thank you and all the others who have answered. I really appreciate you taking the time.

:) :) :)
[Galaxy S II Original Android Development] Lanchon:
the good thing about the community is that you dont need all skills. you can just do the bit of the work you can and let someone else take over. for example establishing that there is a problem in the first place (i really dont know, i dont use these phones).
[Galaxy S II Original Android Development] Dark1Angel:
have any of you who use freezefix kernel witnessed unresponsive touchscreen? since i flashed it the zoom on browser pictures is almost impossible and multiple touches are sensed when i touch just once, unresponsive keyboard and so on.
[Galaxy S II Original Android Development] Klaerchen:
Are you sure?

As far as I can see, the patch "BrickbugAftermath-SGS2/non-squashed-patches/android_kernel_samsung_smdk4412-samsung_wear_leveling_bug_patch.diff " is currently not applied to our standard CM12.1 kernel. Is this patch not necessary?
[Galaxy S II Original Android Development] Lanchon:
yes im sure, thats my repo you are pointing to and that is my port of the wl bug patch (original doesnt apply) that later turned out no to be needed.
[Galaxy S II Original Android Development] Klaerchen:
I didn't mean to offend :)

Thanks for the confirmation!
[Galaxy S II Original Android Development] Lanchon:
no offense taken!
[Galaxy S II Original Android Development] lukss12:
No one could have said it better. That's the reason we always ask people to read all the posts and make useful ones. Because no one want to read a bunch of useless posts. The amazing work done in this device is possible because of the community work. It's amazing and may be a record that a phone have run so many android versions. LA is the one who took the sword and lead now but there was a lot of people working hard on this device before. And the possibility of running LP and M is the evolution of their efforts.
[Galaxy S II Original Android Development] kal4metal:
[MENTION=4141005]Lanchon[/MENTION] is there any possibility of releasing a trim enabled kernel with fpbug fix for the recent nightlies, including the freezefix patch?
[Galaxy S II Original Android Development] lukss12:
Not here, do you use tempered glass? Screen protector? Or non samsung charger?
[Galaxy S II Original Android Development] Lanchon:
im busy right now. alls kernel are fpbug fixed by now.

i would like to help LA release a TRIM enabled TWRP kernel rather than making mine, but it is definitely an possibility.
[Galaxy S II Original Android Development] Dark1Angel:
of course i use screen protector. doesn't everyone? I use non samsung charger as the original broke some time ago but i can't see the conection. I've never had this problem before though. It appeared just after i flashed freezefix. If it persists i'm better off with LA's kernel
[Galaxy S II Original Android Development] kudos1uk:
Lanchon bases his kernel on stock and so does LA base his twrp on stock.

This has to follow a natural progression, official gets updated and folows throught, it safer too.
[Galaxy S II Original Android Development] ajislav:
Can you post a link to this part of the code? Thanks
[Galaxy S II Original Android Development] lukss12:
Sometimes screen protectors get dirty and cause that kind of behaviour... Last week a friend thought his touch screen was broken and when he took the protector out and clean the screen it started to work properly again.

And yes, if you want to blame freezefix kernel of this better you do good tests (but I don't see any possible relation).

About non samsung chargers, it's known that using a non official charger on any phone could cause the touch screen to get crazy but I assume your problem is also when non charging the phone, isn't it?

---------- Post added at 07:09 AM ---------- Previous post was at 06:51 AM ----------

If someone want to try and build a kernel!!!!!!

(I can't right now my build PC died :confused:, and I think it's forever :banghead: )

Login freq_lock and freq_unlock to see if the quantity of locks is equal to the unlocks?
[Galaxy S II Original Android Development] Dark1Angel:
it doesn't have anything to do with charging and with the screen protector as it worked fine before. could it be because of snapshot? till now i was on nightly.
[Galaxy S II Original Android Development] kudos1uk:
Why dont you just test it?

Flash Lanchon trim kernel, it's stock, see how it behaves then.
[Galaxy S II Original Android Development] flashxml:
What patch you use ?

https://gist.github.com/Oberon00/d2...e-0001-logging-in-exynos4_set_frequency-patch

1 - 8
[Galaxy S II Original Android Development] zeitferne:
Oh wow, I just noticed that I seem to have mixed in some files that do not belong there. I will fix that shortly. The important patch is 0007-cpuidle-exynos4-Treat-onlining-CPUs-as-online.patch.

EDIT: While at handling patches, I also submitted the patch to CM12.1 for review: http://review.cyanogenmod.org/#/c/126784. I had to change it slightly to not cause unnecessary overhead on devices that don't need the patch, so technically its untested ( [MENTION=6159291]Lysergic Acid[/MENTION]).
[Galaxy S II Original Android Development] Lanchon:
in the mean time, freezefixed TRIM kernels are up...

http://xdaforums.com/galaxy-s2/deve...kbug-aftermath-speeding-t2843238/post64658730

files:

https://www.androidfilehost.com/?w=files&flid=22984

https://www.androidfilehost.com/?fid=24352994023706454
[Galaxy S II Original Android Development] davishammet:
Can I install the latest nightly starting from a Jelly bean 4.1.2 stock ROM?
[Galaxy S II Original Android Development] Klaerchen:
Illegal Mali frequency 200 MHz

I saw a strange behavior of the Mali frequency in the current kernel (which has been patched to use the 3 frequencies 100, 160, 267 MHz, commit 125182).

The relevant lines in dmesg are:

Line 2173: <4>[13248.531774] c0 Mali: Mali frequency 160

Line 2259: <4>[13249.312132] c0 Mali: Mali frequency 100

Line 2349: <4>[13251.807339] c0 Mali: Mali frequency 160

Line 2353: <4>[13251.907639] c0 Mali: Mali frequency 266

Line 2565: <4>[13253.482507] c0 Mali: Mali frequency 200

Line 2771: <4>[13254.567476] c0 Mali: Mali frequency 200

Line 2997: <4>[13262.442490] c0 Mali: Mali frequency 200

Line 3277: <4>[13264.621966] c0 Mali: Mali frequency 200

So besides being set to 100, 160, and 267 MHz, it is also often set to 200 MHz. This frequency is not contained in the list in exynos4_pmm.c ?!?

And there is also another pattern:

When the frequency is increased, then these two lines appear:

<4>[13248.531494] c0 Mali: = regulator_set_voltage: 950000, 950000

<4>[13248.531774] c0 Mali: Mali frequency 160

When the frequency is decreased, then it's the other way round:

<4>[13249.312132] c0 Mali: Mali frequency 100

<4>[13249.312171] c0 Mali: = regulator_set_voltage: 950000, 950000

However, if the frequency is set to 200 MHz, then the voltage regulator is not set.

* Why is the frequency occasionally set to 200 MHz?

* Why is the voltage regulator not set appropriately?

Could this be a problem?

The complete dmesg is attached.

Another question:

Why is the frequency set to 266, although the frequency list contains the value 267 ?
[Galaxy S II Original Android Development] makix13:
Thanks for your gift, downloading and test asap.

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] daniu:
Hi,

great ...

I don't want to be rude, but honestly to find the kernel from your link is a long way - i9100 is here: https://www.androidfilehost.com/?fid=24352994023706469 - if you don't mind

Regards.
[Galaxy S II Original Android Development] ajislav:
Thank you Lanchon, zeitferne an LysergicAcid
[Galaxy S II Original Android Development] Lanchon:
to give you a better answer than i did before, please read these two posts:

background...

http://xdaforums.com/android/softwa...ug-aftermath-recovering-t2823051/post54295192

is it safe?...

http://xdaforums.com/android/softwa...ug-aftermath-recovering-t2823051/post54295202

these are part of thread that started way back while trying to figure out if it was possible to restore trim on the Exynos 4210 family. these were written before any tests were done and the safety of trim had been established. but they will still give you an overview of why i expected things to work even before trying them. contrary to folklore of the time, safety was the expected outcome. maybe they will help you change your mind on the subject.

---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------

no! thats the CM11 kernel!!

https://www.androidfilehost.com/?w=files&flid=22984

https://www.androidfilehost.com/?fid=24352994023706454
[Galaxy S II Original Android Development] daniu:
Hi,

OK - I guess I caused confusion. Probably the new kernel comes with CM-recovery and will work as intended: https://www.androidfilehost.com/?fid=24352994023706454

honestly: it's probably me but finding the right kernel from you is always really difficult (using smartphone normally - going to the first post in your thread and having to find the right place for the initial link and then to the more current ones is not really easy). Therefore I would appreciate if someone would just post the direct link here (as there is only one kernel from the kernels you provide that people are actually interested in right here) as soon as they found it. This time I wanted to be the one ... see what happened ;)

regards
[Galaxy S II Original Android Development] Klaerchen:
Some further investigation directly after device start:

<4>[ 0.695461] c0 Mali: mali_dvfs[0].vol = 950000

<4>[ 0.695489] c0 Mali: mali_dvfs[1].vol = 950000

<4>[ 0.695515] c0 Mali: mali_runtime_resume.vol = 950000

<4>[ 0.695544] c0 Mali: mali_dvfs[2].vol = 1000000

<4>[ 0.695570] c0 Mali: init_gpu_vol = 1000000

<4>[ 0.695654] c0 Mali: Mali frequency 266

<4>[ 0.695679] c0 Mali: init_mali_clock mali_clock c0ef410c

<4>[ 0.696142] c0 Mali: = regulator_set_voltage: 1000000, 1000000

<4>[ 0.696609] c0 Mali: Mali frequency 200

<4>[ 0.719601] c0 Mali: Mali device driver loaded

This frequency 200 MHz is set for the first time very early after boot.

The first occurence of a frequency change is:

<4>[ 340.092947] c0 Mali: mem_usage before 2234 : 27787264

<4>[ 340.446166] c0 Mali: = regulator_set_voltage: 950000, 950000

<4>[ 340.446687] c0 Mali: Mali frequency 160

<4>[ 340.645481] c0 Mali: = regulator_set_voltage: 1000000, 1000000

<4>[ 340.646284] c0 Mali: Mali frequency 266

(At time 340.4 the Mali frequency is still 200). The first change to 160 MHz shows the pattern of increasing frequency, so the driver thinks the old frequency would be 100 MHz.

Anybody (@zeitferne, [MENTION=6159291]Lysergic Acid[/MENTION]) has an idea, what goes wrong here?
[Galaxy S II Original Android Development] makix13:
Just install kernel-Lanchon-TRIM-FreezeFix-BuggyPegasusQ-20160105-cm-12.1-i9100, ondemand governor, sio I/O without issues.

Thanks to all, LA, Lanchon, Zeitferne etc, etc for your work, you are the current 3 Magic Kings, cheers from Spain!

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] Lanchon:
lol i didnt do anything this time! it's all zeitferne work!
[Galaxy S II Original Android Development] Saber:
Was also wondering why other patches were there as well when the important one was patch 7 (as you have mentioned) :)

Although you have said before that other patches were for logging :) So reading carefully guided me to the correct patch.
[Galaxy S II Original Android Development] zilez2003:
Fixed kernel and stock rom ?

I am litle bit out of shape - can we use fixed kernel with stock rom or Neat Rom ? Its Andori 4+, i dont know exact verison now.
[Galaxy S II Original Android Development] lukss12:
No dude CM 12.1 only. Kernels are android version and usually ROM specific. But it could be that a kernel works on different ROMs, same android version. (With proper modifications)

You can ask your ROM developer to add fix in the kernel.
[Galaxy S II Original Android Development] LeBourrin:
Thanks a lot to release this double-fix kernel !

I've installed it and trimmed my internal memory (many months I have trimmed). I'm happy now and report if any problem.
[Galaxy S II Original Android Development] chrisXL:
+1 for trim kernel.

Has anyone had problems with the latest nightly (01/06) or bad download? Twice the flash is not successful. Went back to the previous version.
[Galaxy S II Original Android Development] bixi:
Hi guys, i have a problem, I don't know if is a problem of the rom and of the kernel or of my device...when i charge my s2 and while I'm soft using (Tapatalk whatsapp) the battery's indicator some time slowly go down sometimes don't move or go up very slowly...it is normal? I've an anker battery...thanks in advance...
[Galaxy S II Original Android Development] Dark1Angel:
the kernel in the second link has pagasusq(or so the name says) how do i change it to ondemand?

second question: i'm on twrp. I read only cm recovery can be used so do i have to reflash the rom, without flashing the twrp (rec+kernel) to enable cm recovery or is it a faster way? does cmw work too?
[Galaxy S II Original Android Development] kal4metal:
As I'm aware (someone please correct me if I'm wrong), there is no twrpified kernel with freezefix patch, no cwm either for sure. Only gsstudios' dori kernel, but it doesn't boot for me. If you want to use it, you have to do with cm recovery.

Regards