yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] essenov:
[MENTION=6159291]Lysergic Acid[/MENTION], any chance to replace Cyanogen Recovery with TWRP? Is there any requirement to stick with the poor recovery?

I was not even able to find a threat about CM Recovery.
[Galaxy S II Original Android Development] ringen00:
I'm far from being a developer :)

But I feel the ROM has improved a LOT!!!

Random Reboots...in the past, yes...

[MENTION=6159291]Lysergic Acid[/MENTION] Thanks for the GREAT WORK!!!

Will check if I agreed to send data to CM...
[Galaxy S II Original Android Development] zeitferne:
I vaguely remember that I once looked in the last_kmsg after such a reboot and found a message along the lines of "out of memory and no processes remaining to kill", so it may be a kernel memory leak (or is there a way to mark processes as non-killable even in kernel OOM situations? Then it could be one of these too). However, I think a memory leak, belonging to a common bug class, should be easier to find than the fpbug. Google brought up e.g. https://www.kernel.org/doc/Documentation/kmemleak.txt (but I don't know if our old kernel supports that).

One thing that would probably be helpful (if it hasn't been done already) is analyzing /proc/last_kmsg after a reboot or freeze+force reboot.
[Galaxy S II Original Android Development] Weib67:
Hi [MENTION=5948587]zeitferne[/MENTION],

Woudn't you be the right man at the right place ? :)

Since you had already done the impossible once with fpbug, I think that many of us hope for a comeback. Are you actually still in the "business" ? Thanks. :)
[Galaxy S II Original Android Development] n3m3sis:
Delete me
[Galaxy S II Original Android Development] Boolian:
Stable.

0.5gb/1gb/6gb (8gb-storage) 32gb ext-sd

Nightly dirty auto flash

Boot.

Trim preload via terminal session.

Freeze Android Keyboard & Trebuchet (Google KB & Nova launcher)

SD Maid cleanup all options.

Boot recovery

Wipe cache

Flash Lanchon CM12 Trim Kernel

Boot

Trim (incl. System)

Use as stable daily driver!

Only issue to date has been the usual very occasional Freeze/Crash using Dashcam video. This known issue (exynos gpu/Mali) has improved with the latest CM12 builds.

I did have issues with Android Keyboard/Trebuchet but don't use them anyway.

So far it's all golden for me. Kudos all round!
[Galaxy S II Original Android Development] Lysergic Acid:
Surely I'll do my best to fix that, I'm also not the most experienced kernel developer ever, I'll do some tests with the kmemleak that [MENTION=5948587]zeitferne[/MENTION] just mentioned, maybe something comes up. There's still hope, relax :)
[Galaxy S II Original Android Development] x3dnd3x:
Actually just wondering, would having items stored in your external micro sd affect the speed? I still get some hangs now and then while opening Whatsapp and other applications. Have to manually remove battery to reset. :(
[Galaxy S II Original Android Development] LeBourrin:
I'm using Google Keyboard since KitKat but I recently saw that it uses much more memory than Android Keyboard.

So in order to have more free RAM I come back to the simple Android Keyboard and i'm happy with it.

My question is : I saw some peoples ( like [MENTION=6724217]Boolian[/MENTION] ) complaining about problems with Android Keyboard. What type of issues? Because I haven't got any for now.
[Galaxy S II Original Android Development] deyan:
I don't know if I encounter the same problems but my keyboard freezes while writing, or keys not respond for about a second and then suddenly comes back by printing all characters I typed. Also changing language takes 2+ sec...
[Galaxy S II Original Android Development] n3m3sis:
I don't change languages so I don't know about that, however I did get that sticking then printing every thing type.... on stock Jelly Bean. I cant say that I see it so much now on LA's nightlys
[Galaxy S II Original Android Development] zeitferne:
Sorry, I don't really have much free time at the moment, and also haven't set up a build environment or anything. (Besides, Lanchon did most of the crucial work for finding the fpbug.)
[Galaxy S II Original Android Development] Weib67:
That's unfortunate. Thanks anyway for the kmemleak idea. :)

Lanchon seemed rather pessimistic here, as he mostly thinks that our problems might very well come from hardware failure.

As LA suggested, I'll now try to relax while he's doing his magic. :laugh:

Wish you the best of luck, guys. :)
[Galaxy S II Original Android Development] FrodgE:
Hmmmm a message like this one?

<0>[76073.165674] c1 Kernel panic - not syncing: Out of memory and no killable processes...

I had a reboot today and happened to grab the last_kmsg
[Galaxy S II Original Android Development] Fr4nz83:
That's very interesting! Guys, whenever you're experiencing reboots/freezes I suggest you to upload your logs here. Let's help LA!
[Galaxy S II Original Android Development] aleMarvel:
i have 1 reboot for day...

not in the past but now.. :\
[Galaxy S II Original Android Development] maro777:
And I update every day and I have no restarts.
[Galaxy S II Original Android Development] Fr4nz83:
Try to keep the same nightly for more than 2-3 days, then come back here again and tell us whether you had freezes/reboots or not :)
[Galaxy S II Original Android Development] ringen00:
You are right!

Facebook app was trying to update - boom -> reboot!

After that it updated :)
[Galaxy S II Original Android Development] Boolian:
I get Android Keyboard (AOSP) has stopped error. I currently have it "frozen" with TiB

>>java.lang.UnsatisfiedLinkError: No implementation found for boolean com.android.inputmethod.latin.BinaryDictionary.addUnigramEntryNative(long, int[], int, int[], int, boolean, boolean, boolean, int) (tried Java_com_android_inputmethod_latin_BinaryDictionary_addUnigramEntryNative and Java_com_android_inputmethod_latin_BinaryDictionary_addUnigramEntryNative__J_3II_3IIZZZI)

at com.android.inputmethod.latin.BinaryDictionary.addUnigramEntryNative(Native Method)

at com.android.inputmethod.latin.BinaryDictionary.addUnigramEntry(BinaryDictionary.java:434)

at com.android.inputmethod.latin.ExpandableBinaryDictionary.addUnigramLocked(ExpandableBinaryDictionary.java:328)

at com.android.inputmethod.latin.ContactsBinaryDictionary.loadDeviceAccountsEmailAddressesLocked(ContactsBinaryDictionary.java:139)

at com.android.inputmethod.latin.ContactsBinaryDictionary.loadInitialContentsLocked(ContactsBinaryDictionary.java:122)

at com.android.inputmethod.latin.ExpandableBinaryDictionary.createNewDictionaryLocked(ExpandableBinaryDictionary.java:562)

at com.android.inputmethod.latin.ExpandableBinaryDictionary.access$700(ExpandableBinaryDictionary.java:53)

at com.android.inputmethod.latin.ExpandableBinaryDictionary$12.run(ExpandableBinaryDictionary.java:605)

at com.android.inputmethod.latin.ExpandableBinaryDictionary$1.run(ExpandableBinaryDictionary.java:194)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)

at java.lang.Thread.run(Thread.java:818)

<<
[Galaxy S II Original Android Development] aleMarvel:
i removed fb app.. too heavy for this CM12.. always problem.. i removed fb and use navigation browser..

(with cm12 when you update facebook you don't must use the phone! nothing.. if you use when update fb = crash and problem.. this happen only with fb app! )

this CM12 is great, but there is 1 crash for day, always :(

for now.. LA is great.. :D
[Galaxy S II Original Android Development] Alex86CT:
I m trying to install Cm 12.1 on my old s2 :) I come from JB stock. I have done:

1. Install Apolo by recovery stock and is OK;

2. Install recovery Kitkat CMW;

3. wipe data, system, cache and dalwik;

4. Flashed last nightly;

5. Flashed TK gappspico.

And now I am locked at "Upgrading contacts database", If I hard reboot (power button for 10 sec) I get locked on "Starting apps"

I've done wipe cache but same result.

Why I got this problem? What I missed?
[Galaxy S II Original Android Development] n3m3sis:
Alex, did you flash the last nightly, boot up, reboot to recovery and then flash TK gappspico or did you flash them both first then do your first boot after flashing?
[Galaxy S II Original Android Development] Alex86CT:
I've flashed together. I solved with wipe data, reflash only nightly and wipe cache.
[Galaxy S II Original Android Development] n3m3sis:
Great! There should be no need to flash TK gappspico again unless LA advises us to. Just reboot to recovery, wipe cache (only) and update new nightly. Enjoy the fruits of [MENTION=6159291]Lysergic Acid[/MENTION]'s (and helpers) wonderful labour. :D
[Galaxy S II Original Android Development] hogze94:
Does xposed work? I keep getting stuck at the boot logo,which version should I download?
[Galaxy S II Original Android Development] anonimowywybryk:
Use this xposed:

http://xdaforums.com/attachment.php?attachmentid=3499278&d=1444255420

Its work :)
[Galaxy S II Original Android Development] Dark1Angel:
Hi! Can anyone tell me what should I select when backing up from twrp from: Boot, Cashe, System, Data, Android Secure, to restore all apps and settings but to not create problems for the software?
[Galaxy S II Original Android Development] Spiralzz:
Whatever selected by default is fine.
[Galaxy S II Original Android Development] Dark1Angel:
nothing is selected by default
[Galaxy S II Original Android Development] Fr4nz83:
Ok, then select everything :)
[Galaxy S II Original Android Development] maro777:
I have uploaded NIGHTLY 1016, the day the phone worked fantastically. At night the phone turns itself completely off.
[Galaxy S II Original Android Development] daniu:
Hi

Everything does only make sense if you got lots of memory. The only advantage from saving cache is that you save time after restoring the backup ONCE

So leave that out ...

Regards
[Galaxy S II Original Android Development] Dark1Angel:
I have enough memory. I'll do the backup just before a wipe, it won't occupy space till then. So I backup everything besides cashe? Why backup the system?(is "system" the settings or the ROM itself?)
[Galaxy S II Original Android Development] Spiralzz:
System means /system partition. Has the ROM + kernel + system apps.
[Galaxy S II Original Android Development] Dark1Angel:
Ok, so i won't backup system as the whole backup thing is in order to restore after a ROM + GAPPS update so i don't need previous rom and gapps.

So which from : Boot, Cashe, System, Data, Android Secure does save my settings(all settings from the settings menu, not just the wallpaper as the google account backup does)?
[Galaxy S II Original Android Development] Weib67:
Hi,

This is off topic. You should post these questions in a twrp thread, you would get more help (those are very general questions, and have little to do with CM 12.1 developpement).

Plus, you have to understand that nandroid backups are not supposed to be used to restore data or settings after a clean flash. You might as well dirty flash over you current rom, and restore the backup only if something went wrong in the process.

That being said, there are indeed tools to deal finely with nandroid backups. But it’s even more off topic.

Good luck.:cowboy:
[Galaxy S II Original Android Development] daniu:
Hi

Even this is really OT I'll add one comment:

if you want to do what you plan to do you can just save everything and later restore only data partition. That part contains all app settings - the whole phone will look and feel almost the same as before. However I also guess that is quite similar to just dirty flashing.

Regards
[Galaxy S II Original Android Development] Mussels84:
Just updated a friend to this, all is working well for the most part.

Not sure if its a coverage/signal issue or not, but he's losing 3G data and getting the ! symbol with only call, text and wifi working. He was on an aussie unbranded 4.1.2 rom before going to CM.

any suggestions for how to work on that?
[Galaxy S II Original Android Development] matee89:
Hello!

Impressive work [MENTION=6159291]Lysergic Acid[/MENTION], the ROM is working wonderfully - performance and uptime wise. The only issue I have is random freeze and reboot while using Viber app. This can occur anytime while using the app. Anyone who have similar issue with Viber? I assume that it works well on stock ROM, but I haven't tried it yet. Shall I provide any logs? I must add that It happens less frequently since I did the factory reset and clean nightly install. My current setup is custom PIT with 1GB system partition + newest nightly.
[Galaxy S II Original Android Development] tuxfusion:
Same here reboots look like this.

deep sleep - wake up - auto app updates start - crash /reboot
[Galaxy S II Original Android Development] anonimowywybryk:
After upgrading to Windows 10 system does not recognize the device . Anyone have any idea ? Reinstalling the drivers for Galaxy SII does not help
[Galaxy S II Original Android Development] maro777:
I have a windows 10 and I've never had problems with the Galaxy S2 CM12.1 on this system.
[Galaxy S II Original Android Development] p3dboard:
Has anyone noticed that once you have a reasonable amount of apps (I have 144 apps when the Art runtime rebuild happens) that if you open an application that supports swiping left or right with content (eg Gmail, Outlook) that after you swipe left or right a number of times, the application freezes and locks up and Android reports the application is not responding and wants to force close the app.

In the logcat output, it reports errors about resources, it says that Input dispatching timed out, wait queue length:10, wait queue head age over 10,000 ms. It also has a Window Manager entry about input event dispatching timed out sending to the app, and that the touched window has not finished processing certain input events that were delivered.

Edit: I just wanted to say that this is not unique to CM 12.1, I also have this on my other device, Samsung Galaxy Tab 7.7, with slimlp Android 5.1.1, once the number of installed applications reaches a certain point it seems to happen. It doesn't happen on Android 4.4.4 (which I find less resource hungry on my Galaxy tab 7.7). So it might be a general Android bug, rather then a CM 12.1 bug.
[Galaxy S II Original Android Development] Saber:
Maybe it is an issue with the usb port driver, rather than the s2 usb driver. Most likely the upgrade has caused some devices not to work on your computer due to some driver issues with the usb port (therefore affecting other motherboard related components as well). This is probably caused by the enhancing of the hardware driver system, improving the security (in the windows NT kernel) so that there is less issues with viruses and etc.

If you've done everything on the phone side, maybe it's time to start thinking about the PC side, possibly reinstall windows and etc.

regards, gsstudios
[Galaxy S II Original Android Development] aleMarvel:
tonight me too !!!
[Galaxy S II Original Android Development] Fr4nz83:
What do you mean that the phone turns off??

Mine does not present this issue...
[Galaxy S II Original Android Development] Dr AM:
does this support fast charging by default?

I've read thar CM supported it but does our device support it?

by fast charging I mean charging 650mA as stock sammy ROMs and not 450mA as most aosp lollipop ROMs for our device use

Sent from GT-I9100 - 5.1.1
[Galaxy S II Original Android Development] maro777:
The phone has shut down completely and had to physically turn on the power switch.
[Galaxy S II Original Android Development] eminem_b:
[MENTION=6159291]Lysergic Acid[/MENTION]

Is there any chance that you can fix the screenrecord app?

I think it doesn't work only for our device.

If you are not aware of it, just open up a terminal and:

$ screenrecord /sdcard/test.mp4

This will result in a UI freeze which cannot be cancelled. A force reboot is needed afterwards.

There's also an app which I think uses screenrecord as a backend:

https://play.google.com/store/apps/details?id=com.rivulus.screenrecording&hl=en

This can also be used for testing whether it works or not.
[Galaxy S II Original Android Development] maro777:
Yes I confirm. It does not work Lollipop Screen Recorder, the phone is frozen.
[Galaxy S II Original Android Development] Weib67:
Here is the solution for screen recording:

Download the attached file "linker.txt". Then, REMOVE the .txt extension. The forum wouldn’t let me upload a file without an extension.

(Or, go to /system/bin/ and take the file "linker" from a rom that supports screen recording. OMNI 5.1 does).

Then, delete the old "linker", in the exact same folder as above, and paste the new one. Of course, you’ll need a root explorer with proper permissions.

At least this solution works for the app Screencast 3.2a (best performance on S2., but you’ll have edit colors). Does not work with apps that require Lollipop API.

Be sure to make a backup before, as this modification involves system files !

All credits go to [MENTION=4775725]Troubadour666[/MENTION] for this workaround.:good:
[Galaxy S II Original Android Development] wolfanger:
It happened the same to me too.
[Galaxy S II Original Android Development] eminem_b:
Screencast works for me since ever. The only problem with Screencast are the colors which are sort of wrong.

I don't use that app anymore because I don't record much, but since I found out for the Lollipop screenrecord, I kind of want to use it.

About this linker file, thanks, but I don't want to risk using compiled files without knowing what's under the hood.

If you can provide a source code to what's different or the whole linker file's source, that would be great for fixing it here.
[Galaxy S II Original Android Development] Weib67:
[MENTION=4840971]eminem_b[/MENTION]

Well, it is very unlikely that Screencast 3.2a is working on a stock CM 12.1.

You are right about the color, as I mentioned. It's the case since several Android versions. I use a PC to correct them. Performance wise, Screecast 3.2a is way better than any other recording solution.

Anyway, I explained how to get the file yourself, feel free to do so. :)
[Galaxy S II Original Android Development] WaLshy11:
Pardon my ignorance, I've been searching and trying to understand the flashing process but I'm still getting confused :(

I'm getting confused on what kernel/recovery to use to be able to flash the rom.

I'm using Aussie 4.1.2 stock rom. Is there a baseband version or build number I'm suppose to pay attention to? People are saying use PhilZ-cwm6-XWMS3 kernel, then flash PhilZ (6.48?) then flash the rom.. is this correct? My stock build number is XWLSH and I've read if I use the wrong one I might not get the proper radio?
[Galaxy S II Original Android Development] cherryb8844:
Its OK I have xwlst firmwares and always use this mathod for flashing the ROM .

Go to your stock recovery

Flash philz cwm recovery what you downloaded from their forum I always use PhilZ-cwm6-XWLSZ-OJC-5.15.9-signed

Then flash philz_touch_6.48.4-i9100

Then clean device to flash new ROM

Mean wipe data factory reset

When you go wipe data wipe factory reset their is the second dialogue sowing clean wipe to flash new ROM clean

The new cm12.1 ROM was takeing 15 to 20 minutes for flash ROM so charge your battery full before do anything :)

After flashing successful reboot your device
[Galaxy S II Original Android Development] WaLshy11:
Thanks! Ill give it a shot on the weekend (so I have time if I screw up) and see how it goes. Fingers crossed!
[Galaxy S II Original Android Development] p3dboard:
I figured out the issue. I had installed the webview update on Google play store. After i unistall that update, everything works again, no more freezing.
[Galaxy S II Original Android Development] Saber:
Maybe this is the doze feature found in Android 6.0 :laugh: jks, but seriously, maybe it is an issue with wakelocks or sods. I would look at better battery stats for misbehaving apps.
[Galaxy S II Original Android Development] Fr4nz83:
Happened to me as well (during the day). I think this thing may be related to the freeze/reboot issues...
[Galaxy S II Original Android Development] Weib67:
Unfortunately, as CM 13 developpement has started, CM 12.1 will get less and less attention. It's a pity that we are left with those nasty freezes.

And chances are that we will meet these bugs again in the future...

Just prove me wrong, and I would be happy. But for now, it's a fact.
[Galaxy S II Original Android Development] rINanDO:
If it is a kernel issue than we will have it also in cm-13.0 and if LA or somebody else finds and solves this nasty bug, it could be merged to cm-12.1, theoretically speaking ;)
[Galaxy S II Original Android Development] Weib67:
Yes, I agree. Problem is that there isn’t much devs working on it. As far as I know, LA is the only one.

And now, he is busy fixing basic things such as booting. Then wifi, GPS... and everything all over again on CM 13.0.

I’m just giving real world feedback, in which overall stability should be of higher priority than proof-of-concept-latest version.

Sorry to sound rude, but someone has to say it. Thanks to LA in any case.
[Galaxy S II Original Android Development] Fr4nz83:
Well, as other people pointed out CM 13 will carry on using the same kernel used for CM 12, so sooner or later that bug will be hopefully fixed in the next kernel versions :)
[Galaxy S II Original Android Development] tuxfusion:
Guys,

I just picked up my phone and it was off.

I had to force crash it ( 5 second power) before it would boot again.

Now it freezes at the Galaxy boot logo for ever. Removing battery, etc. nothing works. Recovery does _NOT_ work anymore. Only download mode ( Power+ Vol-Down + Home)

It was "rather" stable for weeks, ignoring the "daily" reboot all seem to have.

A non booting device, without recovery is new to me and I did everything to it already, including repartition , etc.

Any idea what the issue might have been ? Do i need to use download modus to install different kernel to then flash nightly again ? Alternatives ?

UPDATE:

re-flash CWM recovery kernel (heimdall, odin): fail ( 100% upload, never finishes)

re-partition + CWM flash: fail , never finished after minutes ( takes 3-4 seconds normally)

Situation now:

Device won't turn at all

It looks like this nightly killed the partition table/write ability of the internal sd. One more dead i9100. We will soon not need any more nightly at all I suppose, when all devices died.

I just wish I had killed it actively, it just died resting on my desk. So long. It has been 4 interesting years ( almost to the month!) Sadly I just decided to keep it until 2016 since there is just bull**** devices out there today now ...
[Galaxy S II Original Android Development] chrisXL:
Have you tried to flash stock jb rom?
[Galaxy S II Original Android Development] tuxfusion:
I'm starting to doubt the level of intelligence in the thread : )

Two people already asking me to flash a device that is dead. Not zombie dead , you know, walking and stuff. Dead like:

Situation now:

Device won't turn on at all
[Galaxy S II Original Android Development] Ponsel:
Insulting people might not be helping you solving your problem

Asking questions about reviving a bricked device in a developer thread neither.

Just a hint:

http://bfy.tw/2PBi
[Galaxy S II Original Android Development] vyrussu:
If Odin is connecting to your phone, try flashing a pit file and after that flash o JB rom...
[Galaxy S II Original Android Development] maro777:
To "tuxfusion". Man, if you think you can not do anything about your broken phone, it does not insult the people who want to help you.
[Galaxy S II Original Android Development] chrisXL:
my device had the same symptoms for 2 times in the past but is still alive. but given that the level of intelligence on this forum is low you can throw your s2 in trash.
[Galaxy S II Original Android Development] Fr4nz83:
Maybe it's some kind of faulty hardware and that's why the phone isn't turning on? Did you try to check the battery, etc.?

Anyway, follow the advices given to you by the other users, maybe something useful will come up for you...