yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] jojobg:
Ok folks anyone of you in an Mixed or Internal mode for SD card. What is your experience, I'm unable to make it as default install location and cannot move apps to that partition. Anyone with a clue ? Good thing is I see app2sd functionality returned and able to move to portable internal memory and portable part of sd card in my case. But then this makes internal/mixed mode redundant at present time...
[Galaxy S II Android Development] rINanDO:
On i9100 I fixed it with this commit: https://github.com/LineageOS/androi...mmit/616750a3b71bccbbf27968f49dbf9a4e58c00f7a
[Galaxy S II Android Development] ale5000:
Almost none.

The only one really noticeable is in the Lineage OS file manager, but you can just install a different file manager from Play Store.
[Galaxy S II Android Development] Mirajoo7:
so what about the "MTP Host Stopped Working" issue?
[Galaxy S II Android Development] ale5000:
Sometime it crash, but its use is almost none (at least for me), so I just forgot it.
[Galaxy S II Android Development] MigoMujahid:
A common issue since the beginning of this project, don't worry, it's nothing serious.
[Galaxy S II Android Development] p3dboard:
Hi [MENTION=2222292]rINanDO[/MENTION],

Do you know if this commit for the RIL update has been reverted or fixed by later committs?

https://review.lineageos.org/#/c/161124/

It's just that on [MENTION=5651185]GreekDragon[/MENTION] AICP builds for the i9100 that use the Lineageos base code, it seems that the build after the 9th of February, the Mobile Data stopped working, and on the next build the on the 11th of Feb 2017 for AICP, that commit had been added from Lineageos.

Since there's a bug with Root Support on AICP at the moment, they have stopped the nightly builds from what I can see of AICP for the i9100. I was just wondering if your later RIL commits for fixing Crashes may have resolved the Mobile Data issue as well. Since we don't have newer nightly builds, of AICP, I can't tell if those commits will fix this bug. (https://review.lineageos.org/#/q/owner:drjisakh%40gmail.com+status:merged)
[Galaxy S II Android Development] rINanDO:
The cause of loosing mobile data was this commit:

https://review.lineageos.org/#/c/160656/

And has been fixed by this:

https://review.lineageos.org/#/c/161512/

https://github.com/LineageOS/androi...mmit/5b75c5763c96714af841f9ae4d0606228fb1615a
[Galaxy S II Android Development] Skyline:
Custom Kernel For LineageOS 14.1

Hello guys, since we have an official Lineage OS 14.1 thread by rINanDo, I hope it will be okay if I upload my personal kernel build here if anyone want to try it.

Basically I had just compiled the LOS 14.1 kernel sources with Gustavo's commits and some other commits by some others devs and RAMDISK from unofficial LineageOS 28/01 by rINanDo

And also tried to add most of the controls from synapse to Kernel Adiutor.

I have NOT tested the BLN fragment if controls works or not coz I am using I9100g's display panel my touchkeys don't work. If anyone is going to use BLN controls plz PM if it has any problem I'll try to fix it.

I had changed the app name and package name of original kernel adiutor by grarak to avoid conflicts ONLY. I respect the original developer and his efforts.

CAUTION : I had tested this kernel and currently using it on my S2 plz install this kernel with full responsibilities on your own

Kernel

[url]https://www.dropbox.com/s/6quq09xjsnzp2ik/Kernel-%5BLinaro-4.9%5D-%5B24-02%5D-%5B20-53%5D.zip?dl=0[/url]

Kernel Adiutor(GT-I9100)

[url]https://www.dropbox.com/s/a2s7hhejbhhw35f/Kernel%20Adiutor%20%28GT-I9100%29.apk?dl=0[/url]

Created new thread for kernel and updated kernel build is uploaded there
[Galaxy S II Android Development] Boolian:
Just to be clear: the attached file is a 'custom mod' of the open source 'Kernel Adiutor' application, with Synapse controls etc added - is this correct?

I ask because soon there will be a queue complaining their Play Store version is not working properly

:good:
[Galaxy S II Android Development] sanyigz:
After a missed call, when i picked up my phone, the display was automatically enabled, without touching anything. Before that, with CM 13, 12, or factory android, i had to press the power button to see my notifications. I thought that this is a nice feature, but then i looked at the battery charge % and it was very low, without reason. So i've opened the battery menu in the settings, and saw that the phone was awake roughly since the missed call, till i looked at the notification.

So i've called my phone from another one, waited, and looked the battery history again, and the same happened, that missed call notification keeps the phone awake.

Is this a bug or feature? If a feature, then how can i disable it?
[Galaxy S II Android Development] Nobby1960:
The display was not in full brightness, it was dimmed? If yes, I know this issue. It must be a bug in all LineageOS-based builds. It happens sometimes.

---------- Post added at 10:52 PM ---------- Previous post was at 10:32 PM ----------

[MENTION=5798657]Skyline[/MENTION]

I have tested your kernel and the modded Adiutor with the unofficial build 02/29. Unfortunately the performance profile with 1200 MHz doesn't work permanent. If I start an app, that needs full power from both CPU cores like Google Earth, the CPU clock falls back to ondemand 800 MHz. This must be an issue of the ROM in the energy saving control.
[Galaxy S II Android Development] sanyigz:
The display wasn't on all the time, but when i picked up the phone from the table, and this is something new as it isn't worked like this in previous systems. The cpu/system was awake all time, probably to listen for movement, and enable display when that happens.
[Galaxy S II Android Development] Nobby1960:
Okay - the phone doesn't fall back into deepsleep mode after a missed call, as I understand. I've never watched this, only sometimes the problem with the dimmed display. If this happens, the battery is very quickly empty and you wonder why.
[Galaxy S II Android Development] TreckeR:
Just disable ambient display
[Galaxy S II Android Development] Skyline:
What is the problem in play store version?
[Galaxy S II Android Development] jojobg:
Ambient Display. A very nice feature.
[Galaxy S II Android Development] sanyigz:
Yes, i've found that after posting. Nothing positive in android 7 over 6, just negatives... this weird default feature, nearly impossible slide to unlock, thinking about reverting to cm13.1
[Galaxy S II Android Development] Boolian:
No problems with it, I was just clarifying your link is a modified version optimised with your kernel.

The standard play store version will not have your modifications.
[Galaxy S II Android Development] Skyline:
Ohk, Yeah what you said is true
[Galaxy S II Android Development] Boolian:
CM13 took 5 months until I found a stable-ish build I could call a daily driver and there were several months of bug fixing & improvements after that and never had an official "Stable" release for our device.

LOS unofficial is just 5 month in development and Official LOS team are dealing with their entire infrastucture having been torn down. I think it's doing great. Already It's shaping up to be the slickest ROM yet.
[Galaxy S II Android Development] sanyigz:
It's not LOS, but google. Google is on the slope, their new thing are worse and worse, it seems this applies to android too.
[Galaxy S II Android Development] mrfrantastic:
So far Nougat seems to be far better than MM. I use it as a daily driver and the only thing I am missing is Xposed, but that's about it.
[Galaxy S II Android Development] Boolian:
You might see it eventually Link
[Galaxy S II Android Development] Skyline:
I tried switching governor from ondemand to Performance from Kernel Adiutor bcoz that's what actually happens when you switch to performance profile in battery section and cpu stays all time on 1200 mhz as it should without any problem but I am currently using AICP 7th Feb build
[Galaxy S II Android Development] rINanDO:
Possibly a selinux restriction. Try permissive.
[Galaxy S II Android Development] MigoMujahid:
So the Kernel actually works with AICP??, or you're just saying that you're currently using AICP?
[Galaxy S II Android Development] Skyline:
Yeah all features of kernel works fine but some rom features may not work properly coz we are using selinux policies from LOS and AICP have some extra policies
[Galaxy S II Android Development] MigoMujahid:
I tried it with AICP but got bootlooped, any suggestions??
[Galaxy S II Android Development] Skyline:
Which build you are using?
[Galaxy S II Android Development] MigoMujahid:
The same as yours, Feb 7th, i flashed it over with only cache and Dalvik wiped, does it take more than expected to boot?
[Galaxy S II Android Development] Skyline:
No wipes are necessary
[Galaxy S II Android Development] Nobby1960:
Kernel Adiutor in itself is a great app - but I have the problem that the battery settings with all LineageOS-based Nougat builds (really - all) and the Adiutor probably mutually influence itself. The adiutor switches up at 1200 MHz performance on booting, then the ROM says "No, my friend - this is not possible. Here is a maximum of 800 MHz ondemand announced, I'm the boss of the whole". But some apps need the full power from both CPU cores like Google Earth and it's annoying on the long run, to switch on 1200 MHz by hand every minute. The slider in battery settings still stay on performance profile, if I switch it up after reboot.

I have an overlay to see the current CPU clockspeed on display (like in crDroid) and CPU-Z installed.
[Galaxy S II Android Development] Skyline:
I don't have problem like that though and everything seems to work fine for me.

Btw I think I should create a new thread tomorrow. In next build we will be using ramdisks according to roms for better compatibility
[Galaxy S II Android Development] Nobby1960:
Okay - fine. But I must check your kernel in crDroid :)
[Galaxy S II Android Development] Skyline:
It may not work properly if there are some sepolicy differences between LOS and crDroid roms. Some features of AICP was not working before when I was using that kernel with LOS 14.1 ramdisk but now I added AICP ramdisk to kernel now everything seems to work.
[Galaxy S II Android Development] MigoMujahid:
You're right

I flashed it with no wipes, it's great, i will test for a while and report

Thank you :o

Report about the BLN

Backlight is on all the times, even when i disable it from synapse and settings

Oh, and memory management are amazing and the overclocking is great, thanks :o
[Galaxy S II Android Development] Skyline:
All the credits go to our devs like gustavo_s ,arnab, rINanDo and so on.

You disabled it in Synapse?? I will try to look into it if it has any problems
[Galaxy S II Android Development] toy_story:
Script fix Dialer_v2 for LineageOS !

- Has large photo of the caller

- Improved the display speed of the caller

- Enable call record (in test mode)

Earned a recording function - write to me about it!

Script fix Dialer_v2 for LineageOS !
[Galaxy S II Android Development] Wandeta:
Thanks
[Galaxy S II Android Development] sanyigz:
Updater isn't works. "Not possible to restart in recovery mode"... or unable (it's not set to english language)
[Galaxy S II Android Development] the.gangster:
[MENTION=7776932]sanyigz[/MENTION]

good joke. :)

because this was fixed *after* the last unofficial build was published.

But do you really get offered an update to an unofficial build in your updater????
[Galaxy S II Android Development] Draky50110:
No more unofficial build ?

So we can use official buidls directly now, without sig problem ?

I'm on last cM13 and I'd like to have CM14.

Are there a list of bugs still alive like MTP of file manager not working correctly ?
[Galaxy S II Android Development] BenjyTec:
Issues i encountered so far on latest official LineageOS build:

- MTP host randomly crashes

- Filemanager was disabled in the latest build. It is replaced by system downloads file manager.

- storage menu in settings shows wrong numbers

- little animation glitches

Beside those, the ROM is very fluid and stable. Note that an upgrade from unofficial to official is a little bit complicated. Check out the last pages and the OP of the official thread for further information and help.

Hope this helped.
[Galaxy S II Android Development] Nobby1960:
The MTP host issue is nothing serious, it's a "cosmetical" problem. Just disable the message until the next reboot. The filemanager is a buggy thing. Take a third party app.
[Galaxy S II Android Development] Draky50110:
And what about coming from CM13 ?

Do I just need to full wipe + flash CM14 + Gapps + suaddon .
[Galaxy S II Android Development] SerenityS:
Ignore that error.
[Galaxy S II Android Development] the.gangster:
Well I'll do and did so far.

Just reported it as I thought it would be easy to fix and I read that already several times (where noobs posted and assumed that a real error would have occured).

But it''s ok to fix "real" errors first...

Once more: great work!
[Galaxy S II Android Development] KoT_Vitaly:
Hello, help me how to solve this problemmu. Do not have access to the SD card, it constantly pops up (screenshot). I apologize for the translation of google translayte.
[Galaxy S II Android Development] Lister Of Smeg:
Hi All,

Yeah, I've never known how to over come this screen either... Found it on a couple of roms now...

All help gratefully received...

Cheers, Lister
[Galaxy S II Android Development] SunEvrard:
Just reboot dude. :)

If u have an SDcard issue with another apps, just reboot and It will be fixed.

File manager don't work so install "ES File Explorer". To install ES File Explorer copy it on your SDcard with PC and go to "settings" on your phone->Storage->Portable storage-> (ignore MTP......closed) and find ESfileexplorer.apk to install it.
[Galaxy S II Android Development] rINanDO:
Try this:

Close your App.

Go to Settings -> Apps -> Select your App -> Permissions -> set everything to active

Restart App.
[Galaxy S II Android Development] pippone121263:
you need to set it in root mode:

open the app, go in settings (up left corner), setting (down left corner) setting general, advance, root mode

hope it can help
[Galaxy S II Android Development] rINanDO:
Thanx for the hint! I implemented this to fix the issue, so we still use 'clean' CM-sources.

https://github.com/rINanDO/android_...mmit/87afce7fdeb70a7bcc4a6521a1cd0d330fa41b8f
[Galaxy S II Android Development] KoT_Vitaly:
Regarding applications Your advice helped. thanks for the help
[Galaxy S II Android Development] midium:
Hi everyone, sorry if maybe posting an already replied answer, but I don't have time to go back to read 15 pages of replies.

I would just like to know if the rom is stable and working enough to be used for daily purposes.

Cheers,

Matteo
[Galaxy S II Android Development] bauner:
I also tried this earlier and it did not fix the network search for me

btw

I merged your Camera: HAL improvements and fixes some time ago and it seems to break video recording in whatsapp.

I reverted it in a cm13 testbuild today and it is working again
[Galaxy S II Android Development] davy0104:
Just try ;) At least you should have time for that.

Cheers, Davy
[Galaxy S II Android Development] Lister Of Smeg:
Hi Midium,

Thats ok, we all have busy lives to live.... So in order to answer your own question, do you have time to read the title of the topic?? "CM14 UNSTABLE" ?

Whilst largely, most features are now working... It's still considered WIP (work in progress) and as yet, would not be recommended to be used as your daily driver/purpose... As not to mention, various 3rd party apps will not work yet....

Cheers, Lister
[Galaxy S II Android Development] Andrea900:
It drains your battery, also.
[Galaxy S II Android Development] sparky.lennie:
Hi guys

I got a problem with cm14 20161021 build, when my battery drain to 0% I connected the charger and it remained at 0% and now its about 1h30mins since I connected the charger but the battery is still at 0%,, my question is__ IS THE CHARGING ISSUE FIXED IN THIS BUILD 20161021?
[Galaxy S II Android Development] rINanDO:
Which camera app do you use?
[Galaxy S II Android Development] Andrea900:
Unplug the battery for a moment, then plug it in your device and charge it.
[Galaxy S II Android Development] darkRd:
Hi,

I installed this ROM 3 days ago and using for daily purposes without too much problem.

But I installed it from the beginning 4 or 5 times to get a working one.

In my experience, after installing and booting phone, google play services continuously stopped so I could not set up a google account.

Therefore I could not use playstore or restore contact info from my google account.

I tried reinstalling the ROM a few times and in my fourth or fifth trial google play services were also worked (I dont have any idea why it did not work previous attemps)

Now I am using it daily, sometimes it suddenly reboots but in general it works fine.

It is enough stable for my needs. ril, wifi, bluetooth, GPS are all working for me. But, battery seems to be discharging faster than before.
[Galaxy S II Android Development] darkRd:
Here are some screenshots from cm14.

I liked new left menu in camera very much.

and I noticed one row pulldown to quick toggle Wi-Fi, mobile data, battery, Do Not Disturb mode, and flashlight.
[Galaxy S II Android Development] bauner:
camera2
[Galaxy S II Android Development] DevisG79:
Coming from CM13 to LineageOS14 full wipe is required anyway. So full wipe+flash rom+flash suaddon+flash gapps(optional)
[Galaxy S II Android Development] Draky50110:
Thanks.

Do you recommend any file manager ? Amaze ?

Is OTA update working ?
[Galaxy S II Android Development] DevisG79:
F.e. root browser or ES file explorer or you flash the zip file from Toystory. It`s in the official thread. OTA didn`t test it yet.
[Galaxy S II Android Development] the.gangster:
[MENTION=3582785]Draky50110[/MENTION]

It might be recommended but it is not required!

But if you want to try an update first, you have to flash the experimental build first (together with the newer GApps), boot into that ROM and then finally install the latest Nightly...

If you have issues, you can still wipe everything and start from scratch.
[Galaxy S II Android Development] Draky50110:
Thanks for the tip but I prefer to do a full wipe ;) so going to official directly
[Galaxy S II Android Development] DevisG79:
You are right. It`s not required if you want bugs or lags. (no offense)
[Galaxy S II Android Development] toy_story:
[i9100] Useful fixes for LineageOS 14.1

Adding and fixing in a new format, for [i9100] Useful fixes for LineageOS 14.1 [7.1.1]
[Galaxy S II Android Development] toy_story:
Script remove the superuser indicator "#" !

Script remove the superuser indicator "#" !

Hello,

I noticed that many of you don't like the superuser indicator ('#') in the status bar

and that some of you even flash SuperSU or Xposed, just to get rid of it.

Well, that's not necessary, because there is a much easier way.

So here is the "right way" to remove the "#":

Set in TWRP: Hide_SU_Icon.zip

Disliked Returned back !

Set in TWRP: SU_Icon-REVERT.zip

P.S. After the first power-up, you may need to reboot!

Download here ...
[Galaxy S II Android Development] avtandil33:
Are you sure that you put correct link?
[Galaxy S II Android Development] toy_story:
Download here ...

Yes, click on the link, look not much down and you'll see everything!
[Galaxy S II Android Development] avtandil33:
Sorry

I see only manual for firmware update.

Maybe you can put direct link for the scripts without 'go there-turn left-go down...' ? :laugh:
[Galaxy S II Android Development] toy_story:
Script remove the superuser indicator "#" !

Personally for you added direct download links!
[Galaxy S II Android Development] avtandil33:
Many thanks personally from me ! :victory:
[Galaxy S II Android Development] lexus46:
Most roms there have in Settings an option to show-hide SU icon in the Statusbar when a session is active...
[Galaxy S II Android Development] toy_story:
In most, but not in all!
[Galaxy S II Android Development] ripee:
My unofficial i9100 builds

Link in my signature. Built with the following roomservice.xml file, they include built-in root:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>
<project name="LineageOS/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revison="cm-14.1" />
<project name="LineageOS/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revison="cm-14.1" />
<project name="LineageOS/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revison="cm-14.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revison="cm-14.1" />
<project name="LineageOS/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revison="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revison="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-14.1" />
</manifest>

Thanks to rINanDO for the hard work in perfecting the code :)
[Galaxy S II Android Development] Ciex:
Is it just me, or is this rom slow as hell? It's even more slower than the stock rom for god sake, lol!
[Galaxy S II Android Development] Nobby1960:
Hmm - something cannot be right. I recently had a stock ROM (4.1.2 - Jelly Bean) on the S2, alone the browser remained stuck and lags on simple pages. Also overall, the stock ROM was for me slow-moving in direct comparison to a Lineage-based Nougat ROM.
[Galaxy S II Android Development] Cassker:
I'm having trouble upgrading. I was on a previous build from a few weeks ago. I first tried upgrading OTA from the settings but when it restarted, it reached the startup logo but never stopped. After awhile the phone turned off and I decided to reflash TWRP and upgrade from there. Same results. Help?
[Galaxy S II Android Development] Nobby1960:
Did you make a clean flash? If not, do this - make a full wipe in TWRP: cache/dalvik/system/data.
[Galaxy S II Android Development] Cassker:
I had wiped cache/dalvik but not system and data. That did the trick, thanks. Guess I won't be updating as often if it requires a complete wipe every time.
[Galaxy S II Android Development] Nobby1960:
This can happen if the build data is too far apart. In the meantime, so much has changed that an update no longer works properly. You can also switch to the official build because there are weekly updates.
[Galaxy S II Android Development] rINanDO:
Hi all,

I got a new experimental unofficial build for you guys to test. In this build I added the frequencies from the Dorimanx kernel. No overclock support, but frequencies from 100-1200Mhz in 100Mhz steps. The i9300 uses pegasusQ and I updated the code so it will run also on a 2 core CPU with an updated PowerHAL for the i9100. Please test a post your findings.

Download here: lineage-14.1-20170410-UNOFFICIAL-i9100_PegasusQ_100-1200Mhz.zip
[Galaxy S II Android Development] rINanDO:
Hmmm I just found out the updated PowerHAL wasn't included in this build.... my bad. Forgot to checkout my repo.... I had continuously 1200Mhz on low battery instead of max 1 cpu and max 800Mhz.

One other thing. When you change the governor and switch it back to PegasusQ, PegasusQ with updated PowerHAL won't work properly because the permissions of PegasusQ-settings are only set at boottime. Please test and post your findings.

Download here: lineage-14.1-20170411-UNOFFICIAL-i9100_PegasusQ_100-1200Mhz.zip
[Galaxy S II Android Development] haris1976:
Hmmm I just found out the updated PowerHAL wasn't included in this build.... my bad. Forgot to checkout my repo.... I had continuously 1200Mhz on low battery instead of max 1 cpu and max 800Mhz.

One other thing. When you change the governor and switch it back to PegasusQ, PegasusQ with updated PowerHAL won't work properly because the permissions of PegasusQ-settings are only set at boottime. Please test and post your findings.

Download here: lineage-14.1-20170411-UNOFFICIAL-i9100_PegasusQ_100-1200Mhz.zip

Dirty flash or clean flash with 10th build ?