yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Little Rooster:
Yes, thanks, i already read and downloaded the installer and the fix. But what i was asking for is the framework zip to flash, not the installer.

Don't i need to flash the Xposed Framework??

>>

Another isse ...

I can't change the Background in the launcher. When i choose a black.jpg (iwant background pure black) always the default blue background pic re-appears. Also it's not possible to choose just a color, no pic.

What can i do??

(changing the lockscreen background was no problem)

<<

Edit last isse: Ok, this issue seems to be a problem with the jpg. On other devices this jpg was never a problem. i'm just wondering why.
[Galaxy S II Android Development] TriboDoP:
Hi

I don't use xposed so i looked in the xposed thread by [MENTION=5979925]Rovo69[/MENTION] ( i think) and copied this:

Installation of the framework:

Download the Xposed Installer APK and install it

Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"

Reboot

Done!

I am sure there must be a lot of information by searching.
[Galaxy S II Android Development] slybunda:
black screening a lot requiring hard reset. and video playback issues with whatsapp to at times.

im testing something different on this rom now to see if it makes a difference.
[Galaxy S II Android Development] Little Rooster:
In older Android versions (until 4.4, i think) the Framework AND the extra modules are installed via Xposed installer. In newer android versions (i think since Android 5) the newer framework is flashed via recovery. (e.g. "xposed-v89-sdk25-arm.zip" for LOS 14.1).

Only the moduls are installed via the Xinstaller.

I have tried the old version intalling procedure (like it is explained in your quote, too, and incl. fix), but it ends up in a bootloop.

This rom is neither old nor new. So i don't know wich framework i must install.

Each android version since 5.0 has it's own framework version … :(

Somebody knows what to do now??
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=5955924]zjq985062714[/MENTION] has made 2 builds 4.4.4 in january 2017.

One for xposed: cm-11-20170116-final-xposed-unofficial-i9100.zip

and one "normal " build: lineage-11-20170115-unofficial-i9100.zip

Maybe this could work for you
[Galaxy S II Android Development] Little Rooster:
Thanx. I have already tried about 10 variations. At the end the normal installer (xposed.installer_v33_36570c.apk) was working. It just needed 2x reboot. Now the framework is initialized. Let's hope it works without further problems …

Another problem with this rom: The integrated "screen mirroring" doesn't work.

It doesn't even find my chromecast.

Any solutions on this issue?
[Galaxy S II Android Development] Nobby1960:
About xposed with this ROM look into the first post of this thread in chapter "Known issues".
[Galaxy S II Android Development] Little Rooster:
Yes, i did. But there's no working fix posted.

With the posted suggestion, either the bootloop don't disappear, or (when it disappears) the framework is not inizialized.

With the original Xinstaller (not the old modded one by solarwarez) it works then after 2x reboot, in my case.
[Galaxy S II Android Development] slybunda:
found out what the issue is and how to replicate it. happens with whatsapp. once the whatsapp media folder has lots of videos in it, 150+ opening any new videos or downloading more videos doesnt work and crashes whatsapp. it even crashes the gallery app when trying to open the whatsapp videos through it, get crash message or just a black screen.

once i deleted 50 odd videos and got the count below 100 its working again properly.

after reading around looks like this is a common issue with cyanogen based roms. oddly the old rom i used to use which was a cyanogen mod rom from 2015 never had the problem, yet it was also kitkat based 4.4.4

anyone else having this issue?
[Galaxy S II Android Development] grzwolf:
New build is up ASB 2018-01-01.

Download via OP
[Galaxy S II Android Development] TriboDoP:
Thanks again for being the one and only to update kk!
[Galaxy S II Android Development] ze7zez:
[MENTION=1622467]grzwolf[/MENTION]

Does the widget from the Terminal temulator work well in this ROM?

Does the directory open in the terminal window after entering the "cd /storage" arguments?

Or, instead of opening the directory, only 1;100R text is visible and the folder does not open?
[Galaxy S II Android Development] grzwolf:
App itself works fine, its widget obviously not.

Actually I never tried the widged before, so don't even know until what ROM version it was working.
[Galaxy S II Android Development] ze7zez:
Works well on every other KK and on every MM, N and O.

I tested on many different devices.

It does not work on CM 11 only. Sharing to the application ("Term Here") also does not work, as described in this post.
[MENTION=5227588]Deltadroid[/MENTION] is very busy with Delta Gapps With Modular Addons and can not help.

You are one of the few developers actively creating CM11.

Will you advise/suggest how to diagnose this problem?

Thank you in advance for any tips.
[Galaxy S II Android Development] TriboDoP:
Hi

grzwolf said clearly in the op that the goal is to update in terms of security patches and not development.

So we can take the kitkat rom as it allways was or leave it.

I can only confirm that the app terminal emulator works.

And thanks to grzwolf for updating securoty patches!
[Galaxy S II Android Development] grzwolf:
1. go back in history

Try out previous versions of cm11 (see OP), perhaps start with the last official cm11 (August 2016) and report, whether one of them is working and o/c which one. That would dramatically narrow down the number of possibilities, what patch did it cause (why this: each month brings up approx. 5 ... 10 changes).

2. logcat

Make 2x logcat files, one on a device & a KK ROM where it works, another one where it fails on the same device with the failing KK ROM (do not mix devices and major OS versions).

Compare the outputs and identify the root cause.

Perhaps we could discuss the essence of your investigations here, xda after all is a developer forum.

open terminal app (Playstore: Android Terminal Emulator Jack Palevich), not the widget o/c

$su (root is needed to capture messages from all processes)

$logcat -c (have clean/fresh logcat)

$logcat > /sdcard/logfile.txt (start log messages capture)

let terminal run in background (push home button)

provoke failing & succeeding scenario

switch back to terminal (long press home) and close terminal (X in title bar)
[Galaxy S II Android Development] grzwolf:
The difficulty is, that there is no obvious error message.

Therefore the only chance is to compare logcats line by line for the same device running working/failing ROMs of the same major revision, here KK.

Try out this on a S2: https://androidfilehost.com/?fid=24686681827311894, which is the closest ROM I found compared to the last official cm11 build.
[Galaxy S II Android Development] ze7zez:
cm-11-20131205-SNAPSHOT-M1-mako - KRT16S - android-4.4_r1.2 - pwd command: selected catalog
cm-11-20140104-SNAPSHOT-M2-mako - KOT49H - android-4.4.2_r1 - pwd command: selected catalog
cm-11-20140210-SNAPSHOT-M3-mako - KOT49H - android-4.4.2_r1 - pwd command: selected catalog
cm-11-20140308-SNAPSHOT-M4-mako - KOT49H - android-4.4.2_r1 - pwd command: selected catalog
cm-11-20140405-SNAPSHOT-M5-mako - KVT49L - android-4.4.2_r2 - pwd command: selected catalog
cm-11-20140504-SNAPSHOT-M6-mako - KVT49L - android-4.4.2_r2 - pwd command: selected catalog
cm-11-20140609-SNAPSHOT-M7-mako - KVT49L - android-4.4.2_r2 - pwd command: selected catalog
cm-11-20140708-SNAPSHOT-M8-mako - KTU84P - android-4.4.4_r1 - pwd command: selected catalog
cm-11-20140804-SNAPSHOT-M9-mako - KTU84Q - android-4.4.4_r2 - pwd command: selected catalog and [B][COLOR="Red"]1; 100R[/COLOR][/B] string
cm-11-20140916-SNAPSHOT-M10-mako - KTU84Q - android-4.4.4_r2 - pwd command: selected catalog and [B][COLOR="red"]1; 100R[/COLOR][/B] string
cm-11-20141008-SNAPSHOT-M11-mako - KTU84Q - android-4.4.4_r2 - pwd command: root directory and [B][COLOR="red"]1; 100R[/COLOR][/B] string
cm-11-20141115-SNAPSHOT-M12-mako - KTU84Q - android-4.4.4_r2 - pwd command: root directory and [B][COLOR="red"]1; 100R[/COLOR][/B] string

From the above list it can be seen that the problem started in the android-4.4.4_r2 version, and since the release from 2014-10-08, the "Term Here" function has completely stopped working.

How to continue to look for the cause of the error?
[Galaxy S II Android Development] grzwolf:
Fails since 2014 ...

I suggest to give up.
[Galaxy S II Android Development] grzwolf:
If you are really in to the widget, you may consider to fork the terminal app.

https://github.com/jackpal/Android-Terminal-Emulator
[Galaxy S II Android Development] ze7zez:
Thank you very much for continuing your interest.

The Emulator terminal has variations.

1. Material Terminal by [MENTION=6270589]yarolegovich[/MENTION] (Material terminal emulator v.2.0.2) - year 2015

2. Terminal Emulator Free by ksharkapps.com - year 2017

Both behave identically on CM 11.

So I suppose that the change in the application TE will not change the way CM 11 works.

In the screenshot you can see what parameters the Terminal presents when you put it in a shortcut to the CM 11 lock screen.

I put a question about "Term Here" on the Total Commander forum.

Maybe Christian Ghisler can suggest something.
[Galaxy S II Android Development] grzwolf:
You could add additional log entries all over the place to identify the call,

where terminal finally craps out.

Even if the issue can't get fixed in the terminal app, it might help to understand the root cause.

AddShortcut.java
~~~~~~~~~~~~~~~~
- onCreate
- makeShortcut
- new DialogInterface.OnClickListener()
- buildShortcut
- calls RunShortcut class

RunShortcut.java
~~~~~~~~~~~~~~~~
public final class RunShortcut extends RemoteInterface
- calls openNewWindow

RemoteInterface.java
~~~~~~~~~~~~~~~~~~~~
protected String openNewWindow(String iInitialCommand)
- start point for widget
- calls ShellTermSession

ShellTermSession.java
~~~~~~~~~~~~~~~~~~~~~
public ShellTermSession(TermSettings settings, String initialCommand) throws IOException
- opens a new terminal with an initial command as argument
- to check:
* is "private void sendInitialCommand(String initialCommand)" called?
* if no, call it
* if yes, with what argument?
[Galaxy S II Android Development] grzwolf:
New build is up ASB 2018-02-01.

Download via OP
[Galaxy S II Android Development] Paddy's:
Hi,thank you very much for this rom because it is noticeably faster than lineage 14.1 and i prefer it.

I have some minor issues after i clean flashed this rom.

1) I don't see count badges notifications on any apps(i would like the count badge for missed calls on the phone app) .I tried also nova launcher without success. How can i fix this?

2) I don't see the floating preview notification circle when i receive a message from facebook messenger lite and the settings in the app is on. It doesn't work with nova launcher either. Is this a kitkat rom problem?

3) This is not very important but if i check my phone credit with the android sim toolkit app, it sends the request but i never receive the sms with the credit info. If i send a normal sms request to the right number i receive the sms with the sim credit info. I noticed this also in the lineage 14.1 rom and i have an italian operator sim.

Thanks again for your work .
[Galaxy S II Android Development] grzwolf:
I'm rather sceptic. Did your broken features ever work in a KK-ROM?

You could check older builds, backwards to the last official cm build (approx. August 2016), whether one of them would fix your issues.

If you were successful, then there might be a chance to identify the root cause.
[Galaxy S II Android Development] Paddy's:
Sorry if i bothered you , i noticed now that those are custom rom (specifically lineage os) missing features .

I tested now another phone with lineage os 14.1 and there aren't count badges and messenger chatheads either.

I normally use an lg with stock rom so i thought those features were present in every rom, instead you need third party apps to have those features in a lineage rom .

Thanks again for your work , i'll keep this rom anyway because those notification features are not essential.
[Galaxy S II Android Development] grzwolf:
New build is up ASB 2018-03-01.

Download via OP
[Galaxy S II Android Development] MikiGry:
I cant remeber. Did CM add music bug fix to their 4.4 sources or not ?
[Galaxy S II Android Development] grzwolf:
Afaik long time ago done in 2014.

Tell us if not, xda is a community project. In such case, don't forget logcat.
[Galaxy S II Android Development] mirhl:
FPBug, yes.
[Galaxy S II Android Development] phaleg:
Which gapps would you suggest?

In Lineage webpage they don't have 4.4 and if I click on gapps website I see no option to choose 4.4 either...
[Galaxy S II Android Development] TriboDoP:
Hi

Open gapps arm 4.4 pico or nano
[Galaxy S II Android Development] Wachicamo:
Check again ;)

Regards.
[Galaxy S II Android Development] MikiGry:
There is definitely something wrong with video codecs. Videos in browser don't work (there is only glitchy loading animation and after thet black screen with sound). Also OG youtube and NewPipe werent able to open any video from link (as soon as the video loads up, they would freeze and crash). After enabalding older player methode in NewPipe i was able to watch videos from link (open in --> NewPipe) . Also OG youtube is kinda unstable. Sometimes it works, sometimes it crashes. Reproducing this bug should be pretty easy

Note :

Im using DPI 200 but i dont think thats the problem
[Galaxy S II Android Development] TriboDoP:
hi

video in browser is an old known probleme, which does not seem to be solved..

you could try other browser like dolphin or firefox and use other player like vcl or mx player.

i did not try yet the following solution which claims to have solved the probleme:

https://xdaforums.com/showpost.php?p=70266718&postcount=142

(and going back to original dpi just to ckeck it out would not be a bad idea)
[Galaxy S II Android Development] MikiGry:
[MENTION=7031250]TriboDoP[/MENTION]

I will test this zip soon.

About OG crash. I installed logcat extreme, launched it and recorded whole process from launching OGyt to crash in process of loading video. These are most common errors which i found

- ENOENT

- a big portion of OMX error

I doesnt seem to be DPI caused error to me...http://cloud.tapatalk.com/s/5ae0999f9aebf/Screenshot_2018-04-25-17-01-17.png?

http://cloud.tapatalk.com/s/5ae09a3a015df/Screenshot_2018-04-25-17-01-24.png?

http://cloud.tapatalk.com/s/5ae09a4fa4f30/Screenshot_2018-04-25-17-01-30.png?

http://cloud.tapatalk.com/s/5ae09a5cbeede/Screenshot_2018-04-25-17-01-36.png?

Sorry for posting it like that. If it's not readable this way I will open that log on my computer and paste the lines which screenshots i took

Edit 2

[MENTION=7031250]TriboDoP[/MENTION]

Zip file worked. Despite still glitchy loading animation videos in chrome (at least in YouTube) are working :)

Unfortunatelly in Via (extremally light browser) they are still kinda broken. Video works fine as long as I'm not fullscreen. In fullscreen mode there is only blackscreen with sound. The wird thing is, that when I take a screenshot in fullscreen video mode I can see the current "frame" of the video in the screenshot

[MENTION=1622467]grzwolf[/MENTION]

Can you please attach the link to the videos in browser fix to the first post ?
[Galaxy S II Android Development] hamsterdroid:
Great job works great on my old but gold Samsung S2
[Galaxy S II Android Development] TriboDoP:
[MENTION=5468078]MikiGry[/MENTION]

Thanks for testing and giving some more information about this issue!

Regards
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-04-01.

Download via OP
[Galaxy S II Android Development] phaleg:
Thanks for keeping this solid android phone still alive, with a KK rom that is what it can run best
[Galaxy S II Android Development] hamsterdroid:
Thank you for your support
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-05-01.

Download via OP
[Galaxy S II Android Development] davidvanwijk:
Thanks for all the work!

Can this ROM be combined with NanoDroid (with MicroG and F-Droid)?
[Galaxy S II Android Development] grzwolf:
Never tried that. I'm afraid, with that you're on your own, but it might be worth to give it a try.
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-06-01.

Download via OP
[Galaxy S II Android Development] blue whale:
Hello,

To install this ROM, is it necessary to have the partitions changed by a PIT file, like it is necessary for the ROM on android 7 ?
[Galaxy S II Android Development] TriboDoP:
No

(And rom can of course be installed on changed paritions aswell)
[Galaxy S II Android Development] mario182:
Does the xposed fix no longer work on the 2018-06-01 build? I'm only getting repeatedly the single line

I/Netd ( 2610): Netd 1.0 starting

in the logcat after flashing the fix (and it's bootlooping)
[Galaxy S II Android Development] daun20:
What about "Unlegacy AOSP" on this Device? :cowboy:
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-07-01.

Download via OP
[Galaxy S II Android Development] Gastozz:
Is there any way to enable navigation bar?
[Galaxy S II Android Development] vdhero:
Use root explorer to open build.prop and add "qemu.hw.mainkeys=0" to it then save and reboot.
[Galaxy S II Android Development] czaz111:
Thanks

Have just installed this on my S2 to replace lineage 14.1 and have noticed an immediate improvement. There was one installation problem where on rebooting after installation I got a "Type password to decrypt storage" screen. This was solved by going back into TWRP recovery and setting the data partition to EXT4 as it was probably set to F2FS on the Lineage 14.1 install. Improvements are in speed of response and touchscreen sensitivity. Have not had time to check further. Thanks for keeping this going.
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-08.

Download via OP
[Galaxy S II Android Development] TriboDoP:
Hi

Thanks once more for being the last and only one for udating kk!

Regards!
[Galaxy S II Android Development] MrPacane:
This ROM is exactly what I needed! I was running LineageOS 14.1 and, in the last year, my phone became so slow that it was barely usable. I was about to restore the stock ROM but then I found yours. The installation went smoothly. I only had to format the Internal Storage as exfat (using CWM) to make the camera and the gallery work.

Great work, keep it up!!
[Galaxy S II Android Development] ibooth2004:
I'm planning to make a lollipop rom for Nexus 7 2013 (Flo), would there be any way to merge the latest security patches in to cm 12?
[Galaxy S II Android Development] grzwolf:
Sure, adapt the following to your device & branch.

Coarse overview:

https://xdaforums.com/showpost.php?p=74059817&postcount=142

Step by step:

https://xdaforums.com/showpost.php?p=74525695&postcount=79
[Galaxy S II Android Development] :
Thank you very much for releasing and maintaining this ROM.

There is no source code linked in the OP, so is the kernel used here completely stock, or have you added any custom fixes? By stock I mean https://github.com/LineageOS/android_kernel_samsung_smdk4412/tree/cm-11.0. I am asking since I want to build the kernel myself and I am curious whether I can just build it using the official Lineage 11.0 source.
[Galaxy S II Android Development] grzwolf:
cm11.0 to 100%.

Exactly the link you mentioned.
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB 2018-09.

Download via OP
[Galaxy S II Android Development] APBNDRUM:
Thanx for the rom.How is twrp recovery install in LOS 11 need a kernel to get isorec before flashing twrp??
[Galaxy S II Android Development] TriboDoP:
LOS has an isorec kernel. If you are already on isorec twrp 3.xxx

Just flash this this rom.

If you are on any other (kitkat compatible) recovery just flash this rom together with isorec twrp 3.xxxx
[Galaxy S II Android Development] akkis:
I just flashed the latest version from OP but on "About" setting, I got Android security patch level the value "1 July 2018". Is this normal?
[Galaxy S II Android Development] APBNDRUM:
Thank u for the helpful reply sir, I'm on stock samsung a beginner.
[Galaxy S II Android Development] guest4711:
According to OP it should be September. But because this string is not updated automatically it is possible he did not change it when merging the updates and building...
[Galaxy S II Android Development] akkis:
Thank you for the info!
[Galaxy S II Android Development] grzwolf:
You are correct. Mea culpa.

I just double checked my console history to find out, that all September patches are in the ROM.

All but #228457 ( source ), which bumps up the patch level date string, is missing.
[Galaxy S II Android Development] grzwolf:
New build is up containing 4.4.4 relevant parts of ASB as Unofficial Security Backport "September 2018".

More details & Download via OP
[Galaxy S II Android Development] Paddy's:
Recent pico opengapps 4.4 not working

Hi, i wiped everything(also system partition) to do a clean installation of this rom , so i downloaded the latest pico opengapps for arm 4.4 .

The installation was ok , but then it was impossible to add a google account in the initial setup(I tried to install gapps many times also after the first boot and i got the same problem).

Also in the rom settings there wasn't the add google account option and the playstore crashed immedialtely everytime i opened it.

I had to download an old version of pico opengapps 4.4 from 2016 and this old version worked.

I noticed now there is a big difference because the old version is only 41 MB and recent versions are 125 MB.

Do we have to use only old gapps versions or this could be fixed?

Thanks for your work with this rom .
[Galaxy S II Android Development] grzwolf:
Great finding!

Perhaps recent gapps versions are build against a KK not compatible API level. No chance to fix it.

Tell us the version and I'm going to link it in the OP.
[Galaxy S II Android Development] Paddy's:
Ok, this time i used this version from 2016 : open_gapps-arm-4.4-pico-20161006 .

If you Google this version you'll find the link, but maybe a version from 2016 it's not necessary because i installed this rom at the beginning of 2018 and the opengapps pico 4.4 of that time were working.

There are links to the older releases on the opengapps website and maybe even a version from june or july 2018 could work.

It would be better to find the latest version working on the opengapps website.

Thank you again .
[Sony Xperia XZ Premium Questions & Answers] apkapkapk:
Hi all,

I have an ipega game controller (can't remember the model number) that used to work with my Nexus 6P. It's got issues connecting to my XZP though. It connects and works for a while but after that, there're no more inputs from the controller. The controller is still connected (via bluetooth) and shows up as an input device in the emulator (SNES9x Ex+) but it doesn't seem to be registering input. I've tried connecting my XBOX One controller to the XZP as well but it doesn't work. Is there something wrong with my set or is this Sony's doing?

EDIT: Turns out that after updating the phone with the July update, the controller works now. That's really weird but I assume something messed up with the previous one. This seems to be the only change I noticed with the phone that made it work. No matter how many times I restarted or paired/unpaired it wouldn't work.
[Sony Xperia XZ Premium Questions & Answers] FartyParty:
My Xbox One v2 controller works fine via bluetooth and I use an app called Tincore Keymapper so I can use it in games.

Had a hard time finding an actually working app but Tincore Keymapper does the job amazingly.

Unless I totally misunderstood your post.