yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] dwarf_hero:
In cm 13 you have an extra option in privacy menu where you can customise all blocking actions - even block unknown numbers (that arent on your contact list) or private numbers that you cannot add to your contact list.

Same thing is with text messages.

Now i need to use 3rd part app to get same funcionality that gives cm 13 in this subject.

Apps are using ram and mobile data so having this integrated in system would be better (for me).
[Galaxy S II Android Development] sanyigz:
Whats with radios in lineageos and of course with cyanogenmod? The wifi connection is unstable, also the bluetooth connections. With my bt headset, the microphone has very low volume on S2, with smartwatch it isnt works at all, and if i move 2 metres away from the phone with the headset, then there are pauses in the sound, while with my old chineese smartphone every BT device works perfectly.

Also at talking on phone there are sound problems both on 2G and 3G
[Galaxy S II Android Development] toy_story:
Currently preparing to release LineageOOS 14.1 from 07.06

I'm waiting for a successful build and useful improvements, and there are a lot of them.
[Galaxy S II Android Development] nikits72:
Hi all,

there are many users

trying to update from CM to lineage os without wiping the phone according to this method but we all fail with error 7 when we try to do the step 2.

Is there someone who can tell us what we r doing wrong or what we should do to upgrade from CM13 to lineage os?

Thank you for your time reading this.

Regards.
[Galaxy S II Android Development] gm0:
Error 7 isn't the actual error message, the error message is what's written before. most likely you forgot step -2. of what you linked.

Also I can't say whether the experimental builds still work, they are certainly not officially supported anymore.
[Galaxy S II Android Development] toy_story:
First, update TWRP to TWRP 3.1.0-0 and try.
[Galaxy S II Android Development] gm0:
https://mirrorbits.lineageos.org/full/i9100/20170607/lineage-14.1-20170607-nightly-i9100-signed.zip

Flashes fine, brings it up to google's June security patch level (in reality probably doesn't comply again but I didn't verify this time).

[MENTION=2222292]rINanDO[/MENTION] not sure if BLN brightness setting is supposed to work already but it doesn't for me, at 0% it disables, any other value shows it with full brightness.

edit: also a bug: It's impossible to disable the backlight when using the buttons now, regardless of the slider setting they always light up. The timeout setting is also being ignored, they stay lit up until the screen turns off. That's very annoying. I don't need to see those buttons, I know they are there.
[Galaxy S II Android Development] rINanDO:
I just saw it broke because of a fix in hardware/Samsung a few days ago. A flag has been commented out which needs to be placed in our device repository.
[Galaxy S II Android Development] gm0:
Ah, had seen that commit but thought it was part of your changes. Next week then, thanks. :)
[Galaxy S II Android Development] nospamboz:
20170607 button backlight disable?

With the 20170607 backlight bug, if you have the backlight disabled and touch a button, the backlight turns on, despite being "disabled". A workaround to turn the backlight off again is to set the level to zero in Settings, and don't touch the button again.

I can get the backlight to work properly by falling back to 20170531, but then I lose the June 2017 security updates.

Until the fix is available in next week's build (hopefully), is there some shared object file I can rename, or some setting file I can manually edit, which can fully disable the backlight? Avoiding touching a button is difficult. Ask Arthur Dent.

http://www.goodreads.com/quotes/44928-arthur-dent-what-happens-if-i-press-this-button-ford

(The main annoyance for me is at night, when I use my i9100 as a bedside clock. The backlight keeps me awake.)
[Galaxy S II Android Development] gm0:
Just turning the screen off works, too.

And the file to replace is /system/lib/hw/lights.smdk4210.so - should work, there were no other changes to it this week.
[Galaxy S II Android Development] rINanDO:
I just noticed it was not because of this fix. I already added the flag properly in our device repository and it is working fine. The brightness-control bug is introduced when I added the touchkey_led_on_keypress option. It works fine when not enabled, but I enabled it by default for the stock behavior. To disable this, execute the following command in Terminal Emulator:

echo "0" > sys/devices/virtual/sec/sec_touchkey/touchkey_led_on_keypress

I didn't noticed the bug while I was testing fade-in/out feature with brightness-control.

You can enable fade-in/out manually using the following commands:

echo "1" > sys/devices/virtual/sec/sec_touchkey/touchkey_fadein

echo "1" > sys/devices/virtual/sec/sec_touchkey/touchkey_fadeout
[Galaxy S II Android Development] gm0:
Ah, even better, that's where it was hiding. Confirming this works (until you reboot only, ofc).

For those for whom it's not obvious: You can enable the terminal emulator in the developer options, but you can also just use adb shell (you need root for either).
[Galaxy S II Android Development] bersem:
sorry but the problem with download through updater is still present on todays update.

EDIT: Now work only download via browser app and copy update file to:

/data/data/org.lineageos.updater/app_updates
[Galaxy S II Android Development] the.gangster:
After spending the night on it I have pretty much finished all the many modifications in the configuration files of the BLN_MOD to reflect the changes due to the moved and renamed settings.

Also added controls for the new features (fadein/fadeout/touchkey_led_on_keypress) as discussed per PM.

(Nevertheless I wasn't aware that you already merged the commits to official. I had hoped we could have "talked" about one or two settings.)

But now I need some sleep first... :)
[Galaxy S II Android Development] franticfreddy:
Nightly Version 20170607 lagging like hell / kernel issue?

Hello,

i did clean install with full wipe.

I figured out that the min. cpu frequency is only 100 mhz

with kernel adiutor.

Then i set min. and max. cpu frequency at 1200 mhz and changed

governor to performance, and also changed the i/o schedular to row.

Its better but still it feels unstable and not so smooth like some

previous build.
[Galaxy S II Android Development] gm0:
[MENTION=7192829]franticfreddy[/MENTION] no such issues on my device (without any apps that modify the governor).
[Galaxy S II Android Development] Nobby1960:
[MENTION=7192829]franticfreddy[/MENTION]

Change in Kernel Adiutor the CPU governor from intelliactive to lulzactiveq. The performance governor often falls back to 800 MHz max/min.
[Galaxy S II Android Development] franticfreddy:
Hi,

yes i did notice now that its mostly at 800 mhz with performance governor.

But there arent any governor from what you suggest.

Theres only pegasusq beside the other standard ones.

Now i try pegasusq and its again a little bit better but still not so good.

But thanks anyways.
[Galaxy S II Android Development] nikits72:
The above is my question.

Thank you much for your answer.

I didn't forget the step 2

and also to be more specific the error says :

"Can't install this package on top of incompatible data"

Thank you for your answer.

I used TWRP ver. 3.1.0

In any case is ther a way or does anyone know a way to upgrade to Lineage Os from CM13 without losing data and apps?

Thank you for your time reading thiss.

Regards.
[Galaxy S II Android Development] the.gangster:
Nothing to do with /system-size.

Nothing to do with TWRP-version.

Error 7 "Can't install this package on top of incompatible data" is simply the safety check that checks if the ROM can be flashed dirty over the other.

That's why the migration* build was released:

to allow flashing the LOS-Roms that have a different signature over the ones with the CM-signature.

So use migration build for the hop and if that still fails go for a clean install. (you need to wipe /data then).

If you don't want to do that either, try on your own risk, what I described some 1484 posts ago already.

PS: *migration builds were called experimental builds (like already referred to by [MENTION=8075440]gm0[/MENTION] so I hope that was clear already. Nevertheless I wanted to correct the wording)
[Galaxy S II Android Development] gaikokujinkyofusho:
how to _disable_ sdcardfs in 14.1 on unrooted sgs2?

Hi, I have had issues with many of my apps not being able to access my sdcard after I upgraded my sgs2 to lineageos 14.1. I am able to access it with the included file manager but apps like osmand can not (problematic when one needs gigs of maps). It seems the root of the problem is that sdcardfs is now enabled which has caused some compatability issues. I don't have to have sdcardfs but I do need access to my sdcard. Everything I have found shows how to _enable_ sdcardfs but not _disable_ it. I did kind of figure how I might do it if my phone was rooted but I have chosen not to root it and would really prefer to not have to root it. So, is there a way I can just turn it off? via terminal or app or some hidden setting? or even if I need to flash a zip/mod then ok there too, I just can't quite figure what needs to be done.

Thx!
[Galaxy S II Android Development] gm0:
Thanks, but the guide he was following and that he linked used the "experimental" terminology, as do the archived such builds for the device, so I went with that on purpose, introducing new terminology just serves to confuse IMHO.

And [MENTION=4171579]nikits72[/MENTION] issue is (if I understood him correctly) is that he already flashed the experimental/migration build yet then cannot dirty flash the current build because the keys are not getting accepted. I'll refer to your otherwise quite correct post as to the solution but will add that before going for a clean install he should still back up his app data and settings first so he does not lose them (personally I like Titanium Backup for this but that's but one possibility).

---------- Post added at 09:26 ---------- Previous post was at 09:05 ----------

1. What made you think your issue has anything to do with sdcardfs?

2. I'm on the latest official build and there is no sdcardfs enabled, the driver is good old FUSE

3. Your issue is a permissions issue. Without knowing details of your setup (I'm not even sure if you're trying to access internal or external storage) the easiest is probably to uninstall and re-install that app.
[Galaxy S II Android Development] ale5000:
SDCardFS is the new way, not included yet, that will speed up the storage access.
[Galaxy S II Android Development] the.gangster:
You got me wrong. My edit was meant to clearify that *I* had lapidary called them migration build (as that was their purpose), but that I was referring to the same experimental build that you had already (correctly) referred to, as well as the guide. So it was meant not to confuse, but obviously it did.

And of cause, everyone trying to jump from one ROM to another should have a recent backup.

And don't forget to advice to check the battery level before... (just kidding) :).

My intention was to concentrate on his question and not to explain everything again from scratch once more. But now he should be well adviced meanwhile. Thx.
[Galaxy S II Android Development] gm0:
I hear you. On the other hand, you know as well as I do that it isn't usually the users that did do everything right who come here seeking help. ;)
[Galaxy S II Android Development] darkRd:
Hi,

I always flash latest nightly so I have lineage-14.1-20170607-nightly-i9100-signed.zip flashed now.

For I long time ago, my phone started to run very slowly. It usually takes a lot of time to start any application ( at least 40-50 seconds, very often more than one minute).

If someone calling me, it response very slowly, I hear the calling ring but takes too much time to see caller screen. most of the time the caller ends the call before I see a calling is coming.

Is there a way to find why it is so slow?
[Galaxy S II Android Development] jojobg:
Check battery stats for most usage by application. Install cpu monitor and check process/application using most CPU. Continue from there.
[Galaxy S II Android Development] darkRd:
I am continuously checking battery stats but there is no any application uses CPU too much, but OS itself uses too much. For example, last stats was, Android OS 44%, LineageOS system 25%, Screen 11%,
[Galaxy S II Android Development] gm0:
Check the diagnostic logs (logcat, maybe a dumpsys.), might give you some indication, in particular if it's filling up with timeouts or error messages. I'll also second [MENTION=6609462]jojobg[/MENTION]'s suggestion to get some task manager to see which tasks are using how much CPU. You could also be low on RAM depending on the apps you're running.

Something to consider is to make a backup of /data in TWRP and then wipe /data and flash the ROM again for a clean install. See if the issue persists. If it does it should be a hardware problem.
[Galaxy S II Android Development] Nobby1960:
Try to wipe cache and dalvik cache. After this the first boot will take long, but perhaps it solves your problem.
[Galaxy S II Android Development] nospamboz:
In my experience, the app battery stats aren't perfect, with the system getting blamed for what apps are really doing. For example, I recently had to get rid of Sygic, which (I think) wasn't failing gracefully when Bluetooth is off. I switched to OsmAnd+, and battery usage is back to normal. You may want to try to identify if an app is the real culprit.
[Galaxy S II Android Development] jojobg:
As I said, CPU monitor. Not task manager. You need to find which is the sys process that is taking CPU.As in your case it is the Android OS that smokes the battery. It may be totally different problem under the shell ;) at the end it is Linux based.
[Galaxy S II Android Development] Yongfa:
after latest update, cant connect to pc using usb???
[Galaxy S II Android Development] nospamboz:
Did you use the status pulldown to tap the "USB charging" status to set the USB connection to some kind of file transfer mode?
[Galaxy S II Android Development] darkRd:
I made a clean flash (wipe data, dalvik etc) latest nightly (20170607) because of slowness my phone. Now no any application can capture GPS signal for two days. I also intalled and try apps like gps essentials, they continously looking for GPS location but not find any satellites. Is there a problem in GPS with latest nightly? GPS was working when dirty flashed latest nigthl, but I had to clean install it again due to slowness.
[Galaxy S II Android Development] MigoMujahid:
You mean it worked when dirty flashed, but not when clean flashed!!!!

That's sounds weird!!! :eek:

Did you try clean flashing...again? Who knows, maybe that fix it..
[Galaxy S II Android Development] ale5000:
Have you flashed the latest GApps or microG?

Probably they are missing and GPS location fixing is slower.
[Galaxy S II Android Development] darkRd:
I prefer dirty flash because I don't want to reinstall or restore all the apps and my data. But my phone became very slow as I mentioned here a few posts before. The GPS was working, the apps could get the location. But I had to clean flash latest nightlly because of slowness. Now, no any apps can get location.

Yes, I have nano variant of GApps. I have also installed some GPS tools to delete and download a-gps xtra data.
[Galaxy S II Android Development] nospamboz:
I'm on 20170607, dirty flash, though. F-Droid SatStat app syncs 3/6 satellites in under two minutes, 5/6 after a couple of more minutes. Device-only, just GPS, no Google location, location scanning off. Indoors, top floor in two-floor building. I usually keep Location fully off unless I need it, turned it on specially for this test, now off again.
[Galaxy S II Android Development] dumdidum123:
Even though the GPS never seemed very strong, I got a 4/4 fix in less than 10 seconds. And after a minute I got 6/6.

Inside, 2,5m away from the window, highest floor.

So, no genereal GPS problem with the newest build, I would assume.
[Galaxy S II Android Development] gm0:
My GPS fix has always been 3-5 seconds outside/near windows, 15 seconds inside, not network or cell assisted, no gapps installed. All you need is a working antenna, all those tools are irrelevant. The gapps stuff is just so google can track your location.
[Galaxy S II Android Development] dpcdpc11:
Thank you for your help! Before I do anything, can you please confirm if this REPIT is of to flash: https://www.androidfilehost.com/?fid=745425885120700569 ?
[Galaxy S II Android Development] cikenkari:
Me rename the file to "lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-i9100.zip" then flash it from twrp, and flash the nighlty, let it boot. Next time reboot to recovery then applying modified "storage.xml" file to /data/system/
[Galaxy S II Android Development] Nobby1960:
All right, this is the latest version. You can start :)
[Galaxy S II Android Development] dpcdpc11:
Thanks Nobby! I've got it working... running latest LinageOS on my old S2, which btw runs smooth as silk!
[Galaxy S II Android Development] Spyr0s:
new nightly, synapse bln still f*ucked up'

why won't yo just drop the damned thing and restrore the normal function of backlight through lineage os settings?
[Galaxy S II Android Development] the.gangster:
Because IMHO [MENTION=2222292]rINanDO[/MENTION] is doing a fantastic job in bringing back both:

- normal function of button backlight submenu to control timeout and brightness

- BLN in the BLNWW way, making it possible to have BLN notifications while in deep sleep state (WW=without wakelock)

So I assume, this is worth waiting for yet another week.

And btw: Eat this. ;)
[Galaxy S II Android Development] rINanDO:
I just found out by accident why our phone drops to 800Mhz with performance governor. It isn't caused by the CPU governors at all.

The "EXYNOS4 - Thermal Management support" tmc.c detects the CPU temperture is getting high and drops the frequency (By locking max frequency to 800Mhz) regardless which governor you use (yes also when using ondemand and pegasusq).

Don't use PegasusQ. It is still not stable for our device. Besides working on BLN I'm trying to figure out why PegasusQ is unstable on our device. If anyone has a clue, please let me know.
[Galaxy S II Android Development] Nobby1960:
[MENTION=2222292]rINanDO[/MENTION]

Thank you very much to know that. Then I can finally give it up fighting with all possible governor settings :D I must install a big heat pipe with fan to keep cool the CPU ;)
[Galaxy S II Android Development] dzikk:
How pass safetynet ?
[Galaxy S II Android Development] ale5000:
If you do not flash root you pass safetynet or alternatively there are ways to hide it but I have never tried.
[Galaxy S II Android Development] dzikk:
I flashed only Lineage and Gapps and it doesn't pass safety net (unlocked bootloader ;( )
[Galaxy S II Android Development] gm0:
What phone are you using? Because the i9100 never had a locked boot loader to begin with.
[Galaxy S II Android Development] dzikk:
It is model :I9100

SSN I9100GSMH

[MENTION=309187]edit[/MENTION]

Fixed :

I had to use TrinagleAway and then flash Lineageos ;) now it pass ;)
[Galaxy S II Android Development] MARCOSOFT:
Do you have root?
[Galaxy S II Android Development] dzikk:
Now no
[Galaxy S II Android Development] ale5000:
Are the latest merged commits already BLNWW or they are still normal BLN?
[Galaxy S II Android Development] Boolian:
If you find out, let everyone know! ?

It's becoming a problem and will probably get worse.

Google changed the way SafetyNet operates and more apps will include SafetyNet checks by default.

It's a cat-and- mouse game trying to hide root etc.

If that is the model for the future, then it will need a working root "on-off" toggle and ultimately even that may not be good enough.

My banking app failed just after the latest Google & app update (prior to that it was only flagging "overlays")

Now it won't function.

Magisk & MicroG may be the future, who knows? Not me...
[Galaxy S II Android Development] dzikk:
To pass Safetynet you must have:

-rooted OS

-app TrinagleAway

First use TrinagleAway (you must have root to use it) then when you havent got a yellow trinagle warning (when boot) just unroot your device ;)

Sorry for language mistakes. I hope that you know what I mean :)
[Galaxy S II Android Development] ale5000:
In latest LineageOS on many devices (not yet in i9100) root is already hidden when disabled, so we can do the same thing without external apps but just standard LineageOS options.
[Galaxy S II Android Development] dzikk:
Safetynet checks bootloader status. If it is unlocked safety net will fail
[Galaxy S II Android Development] ale5000:
[MENTION=1221092]dzikk[/MENTION]: It is true for many other phones, but our device doesn't have this check at all.

I have the yellow triangle (never had time to run TrinagleAway), TWRP recovery and LineageOS and I still pass Safetynet without any problem.
[Galaxy S II Android Development] dzikk:
So maybe I have "different" phone ;) seriously without TrinagleAway I can't pass safetynet. On CM13 I conditionally pass safetynet (one option in safetynet helper was false) but Pokemon Go worked ;)

If I find free time I will do investigate ;)
[Galaxy S II Android Development] ale5000:
[MENTION=1221092]dzikk[/MENTION]: It may depend from the things that you have flashed before (things may survive ROM flash if you don't format system).

Have you tried to wipe system and data and flash only latest LineageOS and latest GApps without anything else?
[Galaxy S II Android Development] mfaseeh10:
Hey guys I have Cm12.1 12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100 the most stable one

So can anyone give me instructions of how to install it like do I have to install cm13 or can I directly flash the latest nightly?

That would be great help :)
[Galaxy S II Android Development] the.gangster:
yes
[Galaxy S II Android Development] Nobby1960:
[MENTION=8052153]toy_story[/MENTION]

Your scripts are working fine, man - thank you :)
[Galaxy S II Android Development] shkedov:
Hey friend! The dialer script doesn't exist there in your post. Thank you!
[Galaxy S II Android Development] Bishopandme:
Good news...

I'm in !

B
[Galaxy S II Android Development] Pier_89:
clocK Widget crashes everytime

Hi [MENTION=8052153]toy_story[/MENTION], could you fix it too?

I can't find a way to resolve it, even if I try to clear cache/data app of clocK and Yahoo Weather widgets.

Thank you in advance.

PS: Just see the screenshot.
[Galaxy S II Android Development] toy_story:
Script works incorrectly.

After applying the script, dialer works well, until you connect internet.

Because of this, deleted a script, modify and lay out, if it is still needed!
[Galaxy S II Android Development] Kpe0:
Fix it, please, i'm wating for it too) :cool:
[Galaxy S II Android Development] Pier_89:
[MENTION=2222292]rINanDO[/MENTION] Thank you for your hard work, but I've a big issue about clocK widget comparing to Yahoo Widget weather.

It's not fixed after a clean install. I'm on the last official (deleted) nightly.

I've already clear cache and data of clocK and Yahoo weather widget but the issue still remains.

Thank you in advance :)

Just see the screenshot.
[Galaxy S II Android Development] John D J:
Hi sorry, I'm on the official nightly 08 version. I just now connected to my computer and nothing has happened am I missing an option to enable USB read? Sorry if I've missed something.
[Galaxy S II Android Development] the.gangster:
about screenshots

As this is an international english-language forum and there are again so many localized screenshots in here, may I repeat the following suggestion?

It's no big deal for the individual any more to switch the language to english before recreating an error and pasting a screenshot.

Would make it so much easier for everyone else here.
[Galaxy S II Android Development] Pier_89:
In my case I think it's so easy to understand the error message :)