yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] DaveKing:
First time record...must be. Runtime (mean art) bench in antutu -> 124 scored... LOL I think this 512mb patching is struggling totally the function of LP. This is the example of it. When we start to install more and more apps I started to see freezes and slow motions that never had seen before. No force closes, no kernel panic, nothing. Just slowness. :D It's incredible stable. But in my opinion this way of dirty flash has his good and bad points. Well, will try other options cause I want to use the phone as I want, and not being struggled with this small space. Free space is the base of every good perfomance device, rather is UNIX/Linux, Windows, MAC OS, etc... I think everyone is follow me in this.

Cheers and have a good weekend ;)
[Galaxy S II Original Android Development] mersad0101:
help

when add the wifi region in settings on wifi?

i dont use wifi till.without firs boot.:(
[Galaxy S II Original Android Development] Saber:
It's better to go with kitkat 4.4 rom since it is more stable and since you don't want to keep changing roms. CM11 M12 snapshot is quite old now, so I don't recommend it to anyone. Instead, you should flash CM11 nightlies from Markox89 (a bit old now, but stable) here: https://www.androidfilehost.com/?w=files&flid=33236 or latest unofficial snapshot (recommended because it is newer) here: https://www.androidfilehost.com/?w=files&flid=36883

regards, gsstudios

---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------

The CPU governor is not the reason for overheating. You could try ondemand for a more stable experience, but there is not much you can do to limit the heat other than underclocking the CPU or making sure no intensive app is running in the background.

regards, gsstudios
[Galaxy S II Original Android Development] khal_nayak:
i have no intensive tasks or apps running, in social media just whatsapp and in pegasusq i have always reduced the cpu scale up frequency so it doesnt go to the highest very soon but on cm11 it was better and much cooler but on cm12 it heats up a lot faster, stability wise cm12.1 is fine, just the random hangs from time to time
[Galaxy S II Original Android Development] khal_nayak:
on further analysis it seems android os keeps things running coz under battery i see that second battery consumer after screen on time, have installed better battery stats to find out root cause but the fact is when the android os thing keeps processor running, that causes excess heat and soon after that it crashes so it could be something related to that which is causing reboots and hangs
[Galaxy S II Original Android Development] zeitferne:
So I finally got around to compiling a kmemleak kernel myself so I could test that scenario now, and indeed just clearing the recent apps and waiting five minutes caused kmemleak to show these leaks (only 28 kB total) from the mali GPU driver: https://gist.github.com/Oberon00/4b1ac1ef2b1430055c27 (annotated with source files & line numbers thanks to addr2line -e out/target/product/i9100/obj/KERNEL_OBJ/vmlinux). So I guess maybe not clearing the recent apps themselves but the animation when doing so could play a role.
[Galaxy S II Original Android Development] eminem_b:
Thank you for contributing on this. I just want to note that the github link isn't working for me and probably for others.
[Galaxy S II Original Android Development] zeitferne:
Argh! Sorry, I fixed it now (correct one is https://gist.github.com/Oberon00/4b1ac1ef2b1430055c27).
[Galaxy S II Original Android Development] Fr4nz83:
I noticed this thing too! Let's say that I have the impression it increases the probability of having a freeze...
[Galaxy S II Original Android Development] kudos1uk:
[MENTION=6159291]Lysergic Acid[/MENTION]

Hope you don't mind me tagging you so you see this, I too get this and think this could be useful.
[Galaxy S II Original Android Development] khal_nayak:
it seems the default pegasusq governor settings make the cpu scale up a lot more causing the over heating so what i did was used an app called kernel auditor and tweaked the governor settings so they dont scale up too much very often even for light tasks and the over heating has gone down considerably, i would say heat reduced to 25% of the original, just a little warm to the touch now but not as hot as the default settings and battery life went up a lot. Ill keep it at this and monitor for a few more days, btw if any1 is interested the values i used are below:

cpu_down_freq - 500000

cpu_down_rate - 10

cpu_up_freq - 200000

cpu_up_rate - 20

cpucore_table - 2 1

down_differential - 5

dvfs_debug - 0

freq_step - 20

hotplug_freq_1_1 - 1000000

hotplug_freq_2_0 - 800000

hotplug_freq_2_1 - 1000000

hotplug_freq_3_0 - 800000

hotplug_freq_3_1 - 1000000

hotplug_freq_4_0 - 800000

hotplug_lock - 0

hotplug_rq_1_1 - 200

hotplug_rq_2_0 - 200

hotplug_rq_2_1 - 300

hotplug_rq_3_0 - 300

hotplug_rq_3_1 - 400

hotplug_rq_4_0 - 400

ignore_nice_load - 0

io_is_busy - 0

max_cpu_lock - 0

min_cpu_lock - 0

sampling_down_factor - 1

sampling_rate - 60000

sampling_rate_min - 10000

up_nr_cpus - 1

up_threshold - 85
[Galaxy S II Original Android Development] Lanchon:
besides my cm11 snapshot recommended by gsstudios, you should flash on top my matching trim kernel.
[Galaxy S II Original Android Development] Struck89:
Thanks also to gsstudios

Ok, so I just downloaded "cm-11-20150905-Lanchon-NIGHTLY-i9100.zip"

And the kernel I should use is this one?

kernel-Lanchon-TRIM-FPBug-20150904-cm-11-i9100.zip

Thanks!! :highfive:

EDIT: And what about the gapps? I have these:

Gapps-KK-4.4.0-Signed.zip

from this thread, which is quite old:

http://xdaforums.com/galaxy-s2/themes-apps/gapps-light-edition-google-apps-android-t2548351

(Nov 29th 2013) 2013!!!!!

Cheers!
[Galaxy S II Original Android Development] zeitferne:
[Deleted. I should properly read android versions before answering.]
[Galaxy S II Original Android Development] Struck89:
Haha, I was about to ask... "but... is it compatible???"

I will install the old ones and let google update itself:good:
[Galaxy S II Original Android Development] Lanchon:
yes, that kernel.

and for gapps:

http://xdaforums.com/android/software/reborn-gapps-t3074533

EDIT:

actually, better use this:

http://opengapps.org/
[Galaxy S II Original Android Development] Struck89:
Hi thanks all!

It was already done before your last post Lanchon, but thanks, I will have to probably use it in the future, I used the really really old one, and it's working fine. He is very happy.

But now I have noticed that he has too little space left... I guess I will have to redo it and repartition with your things down there:

http://xdaforums.com/galaxy-s2/development-derivatives/rom-brickbug-aftermath-speeding-t2843238

OMG!!! Definitely not looking forward to it...

1 GB system, 3/4/6 GB data right?

Pfff.... I will have to read even more... Repartitioning seems kind of dangerous if you haven't spent like hours reading...
[Galaxy S II Original Android Development] zilez2003:
I think he will like KitKat.
[Galaxy S II Original Android Development] Lanchon:
its very easy. repartition with my script and my PIT. use 6GB for /data as per my PIT.
[Galaxy S II Original Android Development] ermacwins:
Sorry for off topic [MENTION=6159291]Lysergic Acid[/MENTION] if it's not too trouble, can you point me to where the commit is to enable navigation bar which disables the capacitive keys please?
[Galaxy S II Original Android Development] Lysergic Acid:
That's pretty much the same thing I got, 10 minutes of the system running gets you easily up to 100kb of mali memory leaks, but it's hard to figure out a solution anyway

I don't know if there's a commit to do that specifically, but you can use the build.prop trick :p
[Galaxy S II Original Android Development] cherryb8844:
Hey [MENTION=6159291]Lysergic Acid[/MENTION] do you creating the new stock+twrp for new build the last is 2508 can I use this with the new builds I'm still on 1102 and this build don't have any freez and random reboots this is really like a stable but one issues here when I use UMS for copy files from pc phone freeze still using otg cable and USB for copying file from PC
[Galaxy S II Original Android Development] ermacwins:
This is what I mean. https://youtu.be/1Cb_0N88ZT0
[Galaxy S II Original Android Development] khal_nayak:
one other issue i noticed is when u plug power cable or if there is any notification sound, sometimes the starting few miliseconds of the audio gets dropped or the sound plays late at times. Mostly what i see is audio doesnt come for the starting few milliseconds.
[Galaxy S II Original Android Development] Weib67:
Hi LA,

Well, it's probably a long shot, but have you heard of the Nexus 10 mali leak problem from 2013 ?

here and here.

Maybe you could ask these devs to give you a hand. :)

A fix, or even just a workaround, would be awesome for S2 future. Else, I'm afraid people will end up losing interest in this device. :(
[Galaxy S II Original Android Development] Lysergic Acid:
That depends on this: http://review.cyanogenmod.org/#/c/101188/ which never gets merged, and then an overlay to enable the menu in button settings.
[Galaxy S II Original Android Development] zeitferne:
So my phone froze but after waiting long enough I was able to start an adb shell via USB. This is a screenshot of the output of "free", "top -m 5" and the current CPU frequency: https://dl.dropboxusercontent.com/u/1802511/XDA/Screenshot 2015-11-13 17.33.18.png. Also, here is the kmsg: https://gist.github.com/Oberon00/8485f08b56f04c0dd23f (1.34 MB and probably not very helpful, full of "binder: transaction failed". The messages kept coming so I eventually stopped cat). Unfortunately "cat /sys/kernel/debug/kmemleak" just hangs with no output, so I'm not able to provide that. I think its interesting that only one CPU is running and only at 150 Mhz even though according to top, they are 99% busy (if adding 33% system + 66% user is correct).

[MENTION=6159291]Lysergic Acid[/MENTION]: Right now I'm still connected, so if you want me to try anything else, please ask.

EDIT: So after it tried to soft-reboot, showing a slide show of the CM boot animation, my phone eventually rebooted itself. This is the last_kmsg: https://gist.github.com/Oberon00/15716a5d4afbdadc81eb Seems like kmemleak got stuck scanning or it was just too slow (CPU frequency?) so the kernel decided it was enough ("<3>[85912.022115] c0 BUG: soft lockup - CPU#0 stuck for 22s! [kmemleak:1227]"). Note that I had "cat /sys/kernel/debug/kmemleak" still running while this happened.
[Galaxy S II Original Android Development] ermacwins:
Thank you, is the overlay code also there?
[Galaxy S II Original Android Development] GbMax78:
Switch from sim/mobile internet to Wi-Fi doesn't works, viceversa is ok

Thanks a lot for this great rom! :)

I found a issue or something else when I enable Wi-Fi, I must reboot device to use it but when I disabled Wi-Fi I can use 3g/4g without device's reboot, is there someone who found a solution?

I use Debian and maybe I could make a script to solve the problem above...

GabrieleMax
[Galaxy S II Original Android Development] lukss12:
By now you're the unique with this behaviour may be not a ROM problem.
[Galaxy S II Original Android Development] cdrivex4:
I've been having something similar.. Move far away enough to lose connection to a secured WiFi, when I come back in range it doesn't connect, it remembers the connection in the list, tap connect as many times as i want and it won't do it..disable then enable wifi, no dice, airplane mode on wait, try again..nope.I have to "forget connection" and start again re-enter the password then it connects.
[Galaxy S II Original Android Development] GbMax78:
Thanks for your fast reply! :) This I9100 is not mine (I got a I9195 and I9001), I'll send an sms to explain to user what you wrote!

Have a nice day! :)

---------- Post added at 05:45 PM ---------- Previous post was at 05:36 PM ----------

Thanks for your reply, like I wrote in another post this phone is not mine, I used it just for one day at home without other wifi link, I'll ask to user some days later how it works!

Gabriele
[Galaxy S II Original Android Development] ringen00:
I experienced the same!
[Galaxy S II Original Android Development] khal_nayak:
try this, the ap u connect to, goto the advanced wifi settings and switch from dhcp to static and feed in an ip manually then go out of range and come back in and see if it conencts.

the issue with wifi im having is cant seem to make apps like automate and tasker detect if wifi on then is it connected or no and if not then disable wifi, wifi doesnt seem to trigger a not connected state to these apps.
[Galaxy S II Original Android Development] wdevil12:
mine has that problem too. I thought it was my router's fault. Reconnecting always requires me to forget and type the password again. But I haven't updated to latest nightlies for a while. does that still exist?
[Galaxy S II Original Android Development] daniu:
Hi guys ...

Not sure I understand your problem but: have you tried going to advanced wifi settings and turn off "scanning always available" and "keep wifi on during sleep"

These settings cause problems for me. Google maps asks to turn on the first one IIRC - I allow it to do so cause it improves location but I keep switching it off after using maps cause it makes trouble connection to Wi-Fi.

Regards
[Galaxy S II Original Android Development] ringen00:
I always use static IP and tasker...

The profile for automatic home WiFi is making trouble...
[Galaxy S II Original Android Development] Lanchon:
you might have too many remembered wifis. go through your known wifi list and forget all insecure networks, and all duplicated networks if any. turn off wifi then back on, then repeat procedure. do this until no further progress. hopefully then you'll have less than the max allowed networks and the phone will connect automatically. android remembers but does not connect to networks beyond a certain count.
[Galaxy S II Original Android Development] mimox:
I was looking for this as well as I would LOVE to use on-screen buttons was the hardware button does not register any presses anymore :(

I thought this was a CM feature as it is clearly part of the official Galaxy Tab Pro 8.4 build but looks like it only gets merged for some devices?
[Galaxy S II Original Android Development] cdrivex4:
Nope, only got 3 entries in saved networks an none of those 3 are in proximity of each other...and the WiFi on when asleep set to "never" trick just mentioned by [MENTION=914029]Danlu[/MENTION] is also finally giving a GPS lock in a reasonable time 30s-3 mins...

Summit ain't right.

Update: going to wifi-->saved networks , toggle automatic priority on. I have always had this turned off as if there are multiple networks I want the phone to connect to the WiFi first then when out of range can pick up hot spot from second mobile.

It now seems better at auto connecting when back in range of WiFi.

Though saved access point order priority no longer works.
[Galaxy S II Original Android Development] ccox421:
Hi All,

I installed cm12.1 nighties on my Galaxy s2 two weeks ago. Apart from a few freezes when under heavy load, the phone is working nicely. So thanks a lot for this wonderful rom!

I however tried to use EAP-SIM, which I was thinking should work in Lollipop. Yet, it is not an option, not it is working when I modify WPA Supplicant configuration file by hand. Any idea?

Many thanks in advance!
[Galaxy S II Original Android Development] the.gangster:
[MENTION=6159291]Lysergic Acid[/MENTION]

Any chance, you create a new TWRPied kernel to pick up latest changes?
[Galaxy S II Original Android Development] daniu:
Hi

Sorry ... don't get "my" part. Does it help or not? Actually I think the point is the other setting - scanning ...

Regards
[Galaxy S II Original Android Development] LeBourrin:
No, EAP-SIM is not present in Lollipop. Maybe in Marshmallow but i'm not sure.
[Galaxy S II Original Android Development] khal_nayak:
actually auto wifi off with tasker never worked well for me so currently i switched to automate and that works well so i bought the premium version and moved completely to automate. Give it a try.

here is the link to the flow i use to turn wifi off when on and not connected to any network for 1 min or when connected and went out of range

http://llamalab.com/automate/community/flows/1897
[Galaxy S II Original Android Development] astronix:
Is it possible for someone to install this rom with google app and give it as a backup ?
[Galaxy S II Original Android Development] ringen00:
Wow! Great idea!

So you're now not a tasker user anymore? Unthinkable for me - two many profiles...

Do you use Automate for WiFi with the standalone feature or as a tasker plugin?

I cannot find the plugin in Tasker btw...
[Galaxy S II Original Android Development] khal_nayak:
i use automate for wifi with the standalone feature and btw tasker wasnt updated from quiet some time now and automate is more polished and the developer replies to mails as well for everything. I read on a few sites u can import tasker profiles to automate but not sure on that. i was using tasker till now but always had issues with wifi or something else but automate works flawless so far. im not talking about any tasker plugin, automate is a separate app similar to tasker but uses a flow diagram rather than profiles and tasks, it might get confusing at the start building flows and diagrams but simply think logically and its a breeze to create flows in it and moreover i can finally switch off wifi when not conencted.
[Galaxy S II Original Android Development] Loc2262:
Hello!

I'm using plain CM 12.1 (nightly from Nov 13th) on my Samsung Galaxy S2 (I9100). No custom kernels or similar. The tool "VTS for Android" (vulnerability scanner) from the Play Store reports the device as vulnerable to CVE-2015-3636 ("pingpong") and CVE-2013-6123 (put/get_user). (Those are the only vulnerabilities listed as "vulnerable".)

For same CM 12.1 version on my Nexus 7, the tool reports "not vulnerable" for those two CVEs.

Can anyone confirm that? Might it be a false positive? Or could there really be some leftover vulns in the kernel used for the I9100? If so, are they going to be fixed?

Thanks a lot in advance for information, and for this great ROM!
[Galaxy S II Original Android Development] zeitferne:
Well, our kernel is really old and I would be surprised if it did not have even more known vulnerabilities than these (I'm pretty sure it has "pingpong" as the CVE entry says that was fixed only in Linux 4.0.3, don't know about the second one which is described as a series of bugs in the MSM camera driver and seem not related to anything with put/get_user).
[Galaxy S II Original Android Development] Loc2262:
Thanks for the info zeitferne!

CM 12.1 on my Nexus 7 is, according to "About tablet", using Kernel 3.1.10, and it's allegedly not vulnerable to "pingpong". Has that fix been backported to that kernel?

The version on the SGS2 is 3.0.64... Not that far behind it seems. Or do these version numbers not reflect the actual Linux kernel version?
[Galaxy S II Original Android Development] zeitferne:
They do, but apart from obvious modifications (drivers, Android specific patches) there will probably be a few additional backported patches and maybe a few missing ones. And regarding not being that far behind: Linux 3.0 was released in July 2011, and the oldest version that still receives patches is 3.2, released in January 2012 (https://en.wikipedia.org/wiki/Linux_kernel#3.x.y_releases).
[Galaxy S II Original Android Development] Loc2262:
Yeah very true. I was imprecise... I rather meant that the two kernel versions used for the I9100 and Grouper are not that far apart. According to the Wikipedia page, the Grouper kernel 3.1 also has been EOL since January 2012, yet it apparently got the backport for the two patched CVEs that I listed.

Can we assume that that is the case, and the kernel for Grouper was patched while I9100 wasn't?
[Galaxy S II Original Android Development] Drx86:
I finally see a snapshot in CyanogenMod changelog! :D
[Galaxy S II Original Android Development] cherryb8844:
First snapshot congratulations thanks [MENTION=6159291]Lysergic Acid[/MENTION] for your hard work

What mean that world YOG7DAO1JN in snapshot?

request

Need Latest stock+TWRP kernel
[Galaxy S II Original Android Development] _Atom_:
Thank u [MENTION=1174534]lysergic[/MENTION]_acid for your hard work for bringing the snapshot release :D

Anyone flashed the new snapshot release ? How is the new snapshot release ?
[Galaxy S II Original Android Development] alienflorina:
We must do a clean install for snapshot? Because it doesn't update ota

Απεστάλη από GT-I9100 using XDA Forums
[Galaxy S II Original Android Development] eminem_b:
Just install the latest nightly, you don't need the snapshot. It's just for people who don't use nightly builds and need a little more assurance.

As far as I know, this was the goal, making the snapshot step. Now the focus is most likely to be applied on CM13 :)
[Galaxy S II Original Android Development] Weib67:
I agree, since I've always heard that a snapshot is mostly just a renamed nightly. LA will certainly correct us if it's not the case. It took him time and efforts to release it, so there's maybe a little more.

Anyway, I don't think that the major freeze bug will be fixed any time soon, as it may require Google and Mali ingineers help.

However, this snapshot is probably a good example of how far our device has gone, with its strenghs and limitations.

But thanks to LA, there are way more reasons to use this rom than not to.

Cheers. :)
[Galaxy S II Original Android Development] Loc2262:
Also from me a big THANKS to LA for keeping CM alive on our merry old SGS2! :)

Could maybe anyone of you who's using the CM default kernel download the app "VTS for Android" from the Play Store and see if they also get the two vulnerabilities "pingpong" and "put/get_user"? I'd like to know if it's a generic issue with the kernel, or just applies to my device.

Note that your virus scanner might flag the app as malware, because it scans (among other things) for Stagefright exploits.

Thanks a lot!
[Galaxy S II Original Android Development] the.gangster:
right, and usually based on an older one, so changing from latest nightly to a latest snapshot is usually (technically) a downgrade.
[Galaxy S II Original Android Development] Lysergic Acid:
To be honest I don't know where they take those naming stuff from lol I'll be doing a update to the twrp zip soon
[Galaxy S II Original Android Development] Lysergic Acid:
Yes I'll correct you, the snapshot is different from any nightly. There's a list of differences from nightlies branch to snapshot branch, a bit too big so I'll not post it here. But basically they branch it off nightlies sometime and then include only stable approved changes to it ;)
[Galaxy S II Original Android Development] BenjyTec:
I finally managed to enable onscreen buttons. I downloaded "Build.prop Editor" from Playstore, tapped on + and entered the name "qemu.hw.mainkeys" and set the value "0". Save, reboot and onscreen buttons were there. Hope this helps anyone.
[Galaxy S II Original Android Development] Dr.Fix:
Well, this could be useful, since my main hardware key is not working well...
[Galaxy S II Original Android Development] Weib67:
Thanks for the precision. :)

Here comes the 1 million $ question: would you suggest to keep on using nighlies, or to use this snapshot instead from now on ?

I don't have any major issue on nightlies (I update every few weeks) besides the freeze problem. Do you recommand this snapshot anyway ?

Thank you. ;)
[Galaxy S II Original Android Development] kudos1uk:
Do they work along side the hard keys or do they replace the hard keys, I used to the onscreen keys to take the strain off the hardware keys in Kit Kat but liked both.

You used to be able to scale them nice and small as well, I assume your method only has one size?
[Galaxy S II Original Android Development] Sercan Ali:
No snapshot update on OTA. Should we download and flash it manually???