yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Pier_89:
My question was: How can I choose another folder (different from the internal Root) to save nighlty.zip via OTA?

Sorry for the wrong explaining :)
[Galaxy S II Android Development] mrfrantastic:
Lo

Sry but I don't know exactly what you want to do. Why don't you just make a factory reset instead of only wiping data?!

Also: were you already on CM13? I think you should try to read up a bit on flashing roms. Btw: I wrote down a few steps if you are on CM14 unofficial a few pages back. In general you should always factory reset when upgrading. If you don't then many problems can arise...
[Galaxy S II Android Development] sanyigz:
from CM 13.1 install 14.1 experimental + the newest opengapps mini, wipe cache. Result= "Unfortunately system UI has stopped"
[Galaxy S II Android Development] Nobby1960:
[MENTION=2948251]kolAflash[/MENTION]

Would you like to flash a stable nightly without problems in file manager etc.? Take this build .

In TWRP make a clean flash (full wipe): Cache/dalvik cache/system/data. Now flash this build an then the GApps.
[Galaxy S II Android Development] NikosTweak:
5GHz Wi-Fi

I can not connect more with 5GHz Wi-Fi network. More people with this problem?
[Galaxy S II Android Development] Pier_89:
Same to me. I'm actually on 2,4 GHz Wi-Fi network.
[Galaxy S II Android Development] Boolian:
Just to clarify the SU-add-ons :

Although both the original "SU-add-on.zip" & "Su-Remover-add-on.zip" both throw a "...signal-4" & "Failed" error when flashing in recovery - both actually work in practice after rebooting.

So long as 'zip file verification' is Not checked.

(Thanks to [MENTION=5076953]rnd83[/MENTION] for the observation)

Another slight anomaly:

After flashing eg. the "Remover" the Developer Options root access menu will still show root access for eg: Apps & Adb

However, actually opening the menu option, shows in fact only 'Disabled or Adb available.

As it should.

Toggle either of those and the higher level menu box changes to show correctly.

And vice-versa when re-flashing the SU-add-on after removal.

Basically it shows the previous flashed setting in the box until the menu options are toggled.

Without actually fully opening the Developer Options root access menu to check, at a glance, one may get the impression neither zip had worked.

The alternative 'modified' SU-add-on zip removes the recovery error & failed messages, but is not specifically required otherwise.
[Galaxy S II Android Development] mrfrantastic:
I think you are talking to the wrong guy ;)
[Galaxy S II Android Development] Nobby1960:
Oops - sh*t happens :silly: I corrected it.
[Galaxy S II Android Development] kolAflash:
Sorry for the misunderstanding. By "wiping data" I meant doing a factory reset. (I wiped data, system, cache and dalvik-cache)

I had a clean and fresh CM-13 installation and tried to migrate (update) it to LOS-14.1-experimental, but I ran into the described problem.

And as said, this was intended as a test I'd liked to do, before migrating another i9100 on which I have a lot of apps and settings which I really don't want to loose or reinstall. So migrating from CM-13 to LOS-14.1-experimental is exactly what I want, knowing it's much harder than just doing a factory reset.
[Galaxy S II Android Development] mrfrantastic:
You could try and flash the latest unofficial build before the experimental build, although this seems like a bit of a hassle.

Of course you could always back up your apps with Titanium and save the folder on another drive. Then after a clean flash of the LOS nightly you could restore your apps that way. Good luck!
[Galaxy S II Android Development] kolAflash:
Nevertheless I also had that problem with the official roms from: https://download.lineageos.org/i9100

And with the lineage-14.1-20170129-UNOFFICIAL-i9100.zip rom linked by [MENTION=7513127]Nobby1960[/MENTION] the file manager problem is gone.

Thanks!
[Galaxy S II Android Development] sparky.lennie:
Cm14

Is this ROM now reliable to use as a daily driver? If not then what are the well known major bugs in it? Does it have an synapse supported kernel?
[Galaxy S II Android Development] p3dboard:
Widevine DRM is broken at the moment, if we can find the Android One Widevine L3 blobs for Android 7, that should fix it.

This prevens DRM content from Google play movies from working

Looks like the Asus tf300 dev managed to track down the drm blobs - http://xdaforums.com/transformer-tf300t/development/rom-t3453702/page19 - might be able to download and extract them from his latest build
[Galaxy S II Android Development] Zarosky:
Hi, I have a problem whit cm-14.0-20161021 --com.android.phone has stopped. Why?
[Galaxy S II Android Development] haris1976:
reboot to recovery wipe cache & dalvik then reboot to system, the problem must solved
[Galaxy S II Android Development] mk555:
Ask

how to fix sometimes the phone reboot..?
[Galaxy S II Android Development] p3dboard:
The dev got updated blobs from https://github.com/RonGokhale/proprietary_vendor_sony/tree/nougat/nicki
[Galaxy S II Android Development] darkRd:
Thanks to SerenityS,

it is nice to see that SII still gets latest android version.

I installed the ROM without problem and gapps with aroma.

But play store did not work.

Google play services keeps stopping.

Any idea?
[Galaxy S II Android Development] good8life:
nothing sdcard0

Internal memory - sdcard0 it's not open
[Galaxy S II Android Development] rINanDO:
I think the issue is in cm filemanager itself. Use other file manage Mike Total Commander or File Manager from Asus.
[Galaxy S II Android Development] good8life:
No, it's screenshot from original program android - "download"
[Galaxy S II Android Development] rINanDO:
My bad, can't believe I didn't see that.
[Galaxy S II Android Development] MARCOSOFT:
MMS

May include GalaxyS2-common: Enable sending and receiving mms When mobile data is disabled?

It was merged into the CM13 few months https://review.cyanogenmod.org/#/c/152352/

This work has been especially developed by Arnab Chaudhuri (Arny), which I am very grateful.

I also thank Alex Tsanis (GreekDragon) and Caio Schnepper.

Can you provide the patch to make it enabled on CM14 (7.0)?

Thank you.

Marcosoft
[Galaxy S II Android Development] balloni55:
My first field test with GPS work fine, but if i move slow my possition wasn´t updated well :confused:

so searching finaly a geocache wouldn´t succeed:rolleyes:

Searching in the forum i found discription why and solution:o

http://xdaforums.com/showpost.php?p=67519463&postcount=5199

With "enabled statistic navigation" GPS work like a charme!

Navigation point me now direct to the geocache:good:

BTW: geocaching, after 2 hours with display always on, full brightness, no adaptive brightness, GPS always on, battery was at 15%. This is identical to the original SGS2
[Galaxy S II Android Development] MARCOSOFT:
Bluetooth now works much better than the CM13!

Good!
[Galaxy S II Android Development] the.gangster:
Found one more setting that is still not working. That one could especially be good to know as it could cause extra fees on your bill.

Settings -> more -> Cellular networks -> Network operators

"Error while searching for networks"

As that also happens for both of the submenus ('sarch networks' and 'choose automatically') I was unable to prevent my phone from registering on the foreign networks when travelling along the border.

(build20161021)

Edit:

btw still unchanged behaviour upon flashing:
[Galaxy S II Android Development] p3dboard:
Hi Dev's [MENTION=2222292]rINanDO[/MENTION] [MENTION=5857622]SerenityS[/MENTION]

Applying the same fix as ACIP Android 7.0 rom (http://gerrit.aicp-rom.com/#/c/29802/) fixes the Widevine L3 DRM subsystem, Google Play movies works (you can do this fix manually with root access to the cm14 rom) by replacing the Blob's and setting the permissions to RW,R,R using ES File Explorer.
[Galaxy S II Android Development] bauner:
@rINanDO @SerenityS

This fixed it on the n7000

https://github.com/bauner/cm-androi...mmit/35a5a4c54797e007460b0776f734166b627fb1e2
[Galaxy S II Android Development] HerrOrhan:
elo guys, i'm using xda for a long time now but never registered :D so hi!

i ran into the issue that the battery runs flat really fast, like 2hours with sim card in and wifi active. on older android versions i used the dorimanx kernel to get a proper readout of the charging current but this kernel does not work on 7.0. is there a way (software) to read out the charging current? even with usb/wall charger plugged in it drains the battery fairly fast.

if u need any logs just tell me

edit/update:

somehow the ampere app can read out the charging current with the original samsung wall charger but it's on 20 - 70mA where it is supposed to be at 500mA. same phone, android 6.1, and same app on dorimanx kernel charges at 500mA wall and 500mA usb. with stweaks and charging current maxed out it charges at 600 wall and 650 usb. (maybe the wall charger does not put out more current at all) but it's still nothing like 20 - 70mA.

any tips/solutions/workarounds are appreciated.
[Galaxy S II Android Development] SerenityS:
Thanks! I apply that patches a moment ago.

I will rebuild and check it works soon.
[Galaxy S II Android Development] the.gangster:
[MENTION=5857622]SerenityS[/MENTION]

Did you have a look at the flashscript as well?
[Galaxy S II Android Development] MARCOSOFT:
Lineage-14.1-20170129-UNOFFICIAL-i9100 was the last ROM developed by rINanDO and the next updates should be done via OTA, or if on the contrary, should we avoid OTA updates and wait for the new rINanDO ROMs?
[Galaxy S II Android Development] davidvanwijk:
Is there a thread for official, lineageos roms for the I9100? I am searching for instructions.

I have once repitted with IsoRec of Lanchon and am currently on build from rINanDO

Verstuurd vanaf mijn GT-P7500 met Tapatalk
[Galaxy S II Android Development] Draky50110:
You're inside :)
[Galaxy S II Android Development] davidvanwijk:
?okay... Two questions:

1) I understand that a clean install is needed (when not using experimental). True?

2) Are questions about problems building my own ROM also in place here?

Thanks!

Verstuurd vanaf mijn GT-P7500 met Tapatalk
[Galaxy S II Android Development] kolAflash:
Actually I already tried migrating from cm-14.1-20161208-UNOFFICIAL-i9100.zip (by rINanDO) to lineage-14.1-20170206-nightly-i9100-signed.zip

But I still got the same problem.

Thanks for the Titanium tip. I know of that possibility, but actually I was more thinking about the point, that I tried to migrate from a clean CM installation to LOS. I didn't run the CM system for more than 10 minutes. So I guessed more people must be having this problem and there might be something broken in the experimental build!?
[Galaxy S II Android Development] max6698:
Hi David,

if your second questions relates to compiler error messages like these...

In file included from hardware/samsung/ril/libril/ril.cpp:361:

hardware/samsung/ril/libril/ril_commands.h:153:6: error: use of undeclared identifier 'RIL_REQUEST_SET_CARRIER_RESTRICTIONS'

{RIL_REQUEST_SET_CARRIER_RESTRICTIONS, dispatchCarrierRestrictions, responseInts},

^

hardware/samsung/ril/libril/ril_commands.h:154:6: error: use of undeclared identifier 'RIL_REQUEST_GET_CARRIER_RESTRICTIONS'

{RIL_REQUEST_GET_CARRIER_RESTRICTIONS, dispatchVoid, responseCarrierRestrictions},

^

In file included from hardware/samsung/ril/libril/ril.cpp:365:

hardware/samsung/ril/libril/ril_unsol_commands.h:63:6: error: use of undeclared identifier 'RIL_UNSOL_PCO_DATA'

{RIL_UNSOL_PCO_DATA, responsePcoData, WAKE_PARTIAL},

I think we're all getting them and that's probably why the nightly is overdue.
[Galaxy S II Android Development] mrfrantastic:
Unofficial, experimental, nightly worked for me (and others), see my post a few pages back. Strange that you run in problems, it should work fine...
[Galaxy S II Android Development] kolAflash:
Sorry, I was a little unprecise.

Unofficial, experimental and nightly work for me too if I do a clean install. But after migrating from CM to LOS-experimental I get the described "System UI has stopped" error. So if I do a CM->LOS migration (as far as I know doing this is the only reason why the current current experimental builds exist) isn't working. And that's what I ment when I said "there might be something broken in the experimental build".

In other words:

Looks like migrating from CM -> LOS doesn't works at all on the i9100.

Question:

Has anyone successfully migrated from CM -> LOS?

(if yes, which was the old CM rom and to which LOS rom did you migrate?)
[Galaxy S II Android Development] Jamie_oppo:
How's the battery life in the nightlies compared to early january builds? I am on lineage os14.1 20170108. Is it worth flashing latest builds for better battery life or is it the same?
[Galaxy S II Android Development] sanyigz:
So how can i install the 14.1 lineageos over cm 13.1 to make it work?
[Galaxy S II Android Development] Cesartrejo1507@gmail.com:
Right now i am in the last unofficial but can I do a direct clean installation with the last nightly? Or you must first use the xperimental and then nightl
[Galaxy S II Android Development] dii86700:
Yes you go directly nightly build with clean install

---------- Post added at 01:11 PM ---------- Previous post was at 01:02 PM ----------

1 Backup your apps with Titanium backup

2 Make your nandrid backup with TWRP recovery

3 Download last nightly

4 Make full wipe (wipe Cache,dalvik cache,system,data)

5 Finish satup and back your apps with data from Titanium backup

Lineage os not instal over cm 13
[Galaxy S II Android Development] sanyigz:
And what's with the experimental image? If full wipe is required, then i'll keep the cm13, i don't want to wipe and do everything from the start.
[Galaxy S II Android Development] dii86700:
Experimental image work if you on unoficial build LOS 14.1 or cm 14 not work with cm13 but experimental broken image and not work solution is make backup with Titanium Backup and restor apps with Titanium Backup wen finish installing LOS if you not doing this then stay on cm13 for now :)
[Galaxy S II Android Development] NikosTweak:
5GHz Wi-Fi

Are there people who have a solution for the 5GHz Wi-Fi network problem? I can still only use 2.4 GHz Wi-Fi networks.
[Galaxy S II Android Development] Nobby1960:
Titanium Backup is one of my most important tools to recover my apps with data after a clean flash. It works very reliably.
[Galaxy S II Android Development] steiner.seevetal:
I'm not able to select sdcard1 (external) in the settings of TB as storage for backup, it said it is only readable, did you you have the same problem?

Gesendet von meinem SM-G920F mit Tapatalk
[Galaxy S II Android Development] Nobby1960:
No, this works for me without issues. In this moment I have changed the settings in TB to save backups on the external card. All backups were automatically moved in this folder. I have the free version.
[Galaxy S II Android Development] the.gangster:
Solution for Titanium to access external storage already explained here
[Galaxy S II Android Development] Yakap:
ROM toolbox pro also good for backup data
[Galaxy S II Android Development] max6698:
Can anyone give me a good reason for ever clearing cache when upgrading? The only stuff in there is some junk left by TWRP.

i9100:/cache # ls -alh /cache

total 12K

drwxrwx--- 6 system cache 4.0K 2017-02-03 21:51 .

drwxr-xr-x 17 root root 0 2017-02-11 03:28 ..

drwx------ 3 system system 4.0K 2017-02-03 21:59 backup

drwx------ 2 system system 4.0K 2017-02-11 07:32 backup_stage

drwxrwx--- 2 root root 4.0K 2017-02-03 21:50 lost+found

drwxrwx--- 2 system cache 4.0K 2017-02-11 03:27 recovery
[Galaxy S II Android Development] jojobg:
It's the app cache also ;)
[Galaxy S II Android Development] MARCOSOFT:
I'm with Lineage-14.1-20170129-UNOFFICIAL-i9100, was the last ROM developed by rINanDO.

If I check in settings for updates, two updates appear available, nightly 06/02/2016 and 08/02/2017 (I think they are the official).

Can I upgrade this way (OTA) directly to 08/02/2017?

Will recovery change? At this point I'm with TWRP 3.0.2-1.

For those who already updated, did you feel any change?

Does Rafio FM work in the last official version?

Is the MTP problem already fixed?

Thank you.
[Galaxy S II Android Development] toy_story:
No! I know about an issue updating via OTA.

Quick update if the error via OTA
[Galaxy S II Android Development] MARCOSOFT:
Can you tell me your experience of the remaining questions?
[Galaxy S II Android Development] toy_story:
Will recovery change? At this point I'm with TWRP 3.0.2-1.

- At this point I'm with TWRP 3.0.2-0, TWRP 3.0.2-1 installed later.

For those who already updated, did you feel any change?

- I did not notice!

Does Rafio FM work in the last official version?

- I do not know! Not tested!

Is the MTP problem already fixed?

- No!
[Galaxy S II Android Development] laptopu:
Yes FM radio works, there is another twrp on its way from [MENTION=2222292]rINanDO[/MENTION] to use emulated storage.
[Galaxy S II Android Development] steiner.seevetal:
FM radio for me too

Gesendet von meinem SM-G920F mit Tapatalk
[Galaxy S II Android Development] sanyigz:
I've unstalled the nigtly, but at root settings there is only "no" and "only ADB". No root for applications. 13.1 had 4 root settings. Why?
[Galaxy S II Android Development] the.gangster:
This only happens to dislexics, who are unable to read the last posts but by miracle manage to post a question here...

:(
[Galaxy S II Android Development] toy_story:
Lineage OS will not provide users with the default root-rights!

Root issues with the latest build!
[Galaxy S II Android Development] sanyigz:
thx, i've found the solution with google search, however the install of lineageos supersu works only by disabling zip signature check (just like the rom itself), also getting an error about "unable to run ... executeable" during the installation, but after restart to system i had full root options.
[Galaxy S II Android Development] toy_story:
As I did!

Opened in TWRP :

Install/ addonsu-arm-signed.zip / Wipe cache/dalvik .

Reboot System.

Root enable the phone settings, all 4 will root settings.

:good:
[Galaxy S II Android Development] laptopu:
The android police article says root file only needs flashing once, but once is enough for what? Once ever? Once after every dirty flash? Once after every clean flash? I think not allowing root by default is a poor decision by los.
[Galaxy S II Android Development] the.gangster:
"Flashing once only" means that the Root-addon contains an addon.d script to survive flashing of newer versions by making use of automatic backup and recovery methods.

But if you wipe the /system partition, these addons are also wiped. Just the same as it is with e.g. GApps, BLN_Addon and many more that rely on addon.d scripts.
[Galaxy S II Android Development] laptopu:
Thanks for that info. I really can't see why los team think not allowing root by default is a good idea unless I've totally missed the point?
[Galaxy S II Android Development] Boolian:
I could be wrong, but it's probably to enable compatibility with Safetynet by default. (Not clear how it passes with an unlocked bootloader though)

Users will expect to use eg. Android Pay etc. Can't have people unable to play PokemonGo either! Too many apps now require compatibility.

I suppose it's a logical decision.

It's an easy option to activate if needed.
[Galaxy S II Android Development] laptopu:
I hadn't thought about android pay as someone who doesn't have NFC phone so that's a fair point you make.
[Galaxy S II Android Development] papei:
I went through the process. It shows that I have full root options but root does not seem to work. If I go to the file managing program and try to click on the sdcard it says that I need elevated rights to do so. I went to the setting on the file manager to ensure that I have full root access and it says that I do. I also have system setting set to root for apps and adb.
[Galaxy S II Android Development] dii86700:
File Menager in official build not work root work solution for file menager is bookmark internal sd card or install File Ext or total comander root work in other apps or install other apps File Menager official build work excellent
[Galaxy S II Android Development] toy_story:
File Manager in official build Lineage OS is not working properly

Here is the solution

It is better to install another app file manager!
[Galaxy S II Android Development] wihushae:
But where to adress this issue, that the Los devs can solve this issue?
[Galaxy S II Android Development] Nobby1960:
For all who want a working original file manager from LineageOS:

Install nightly build 01/29

Install APK extractor app and copy the file manager. Now Install it in a newer build as apk, it should work. Check this out. Only an idea.
[Galaxy S II Android Development] papei:
You're right, thanks. I installed ES File Explorer and I have full root access. :good:
[Galaxy S II Android Development] shkedov:
[/COLOR]

Hmmm, sounds interesting! Will check, but nothing assures it to work. Did you perform it yourself?
[Galaxy S II Android Development] Nobby1960:
I perform it for you, one S2 has no ROM this moment. Stay tuned :)
[Galaxy S II Android Development] toy_story:
For anyone who wants to work from the original file manager LineageOS!

Guide my work:

- I unpack the firmware lineage-14.1-20170129-UNOFFICIAL-i9100.zip.

- Copied CMFileManager.apk.

Path: system.new.dat / app / CMFileManager / CMFileManager.apk

- The phone, deleted CMFileManager (app Root Explorer) .

- Restart.

- Installed CMFileManager.apk

* (Copied from UNOFFICIAL from 29.01)

- Restart.

Result:

CMFileManager works without problems.

Opens sdcard0 without problems in safe mode, and does not require

additional permits.

Conclusion :

Official LOS sets not working CMFileManager, and it's not right.

The right to access the root - it does not matter.

I think they will fix it in the following LOS!

It was an experiment!

And he was successful.

Write, if I did something wrong.

This can be useful.

Added working CMFileManager.

Set in TWRP!

I'm writing a script to install CMFileManager (from assembly rINanDO from 29.01) to replace LineageOS file manager in the assembly 02/08.

Scripr first removes not running manager, and then sets a certified manager of assembly for 29.01.
[Galaxy S II Android Development] MARCOSOFT:
How can I add this call recording function to Lineage-14.1-20170129-UNOFFICIAL-i9100?
[Galaxy S II Android Development] rINanDO:
The option is underneath the 3 dots icon on the right.
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: And the option to show the download / upload speed like in the image where is?
[Galaxy S II Android Development] MARCOSOFT:
I can not find! For sure?

I do not have the option is underneath the 3 dots icon on the right!
[Galaxy S II Android Development] MigoMujahid:
I don't think it's available in LineageOS, these are advanced options, the download and upload speed option is available in AICP and RR, but you can use this app to have this feature, for recording calls you can use this app , it's a good one.
[Galaxy S II Android Development] papei:
I do have the option, but doesn't call recording depend a bit on your carrier and the laws in your country? When I start call recording it fails every time.
[Galaxy S II Android Development] Nobby1960:
[MENTION=6330684]shkedov[/MENTION]

The solution from [MENTION=8052153]toy_story[/MENTION] is the best way to replace the LineageOS file manager in build 02/08. I have checked this out. Unfortunately, a simply installation from the magager apk does not work because the same filename already exists in the system directory. This must first be deleted. However, it requires a separate, root-capable manager, e.g. Root Explorer.
[Galaxy S II Android Development] sanyigz:
The built in file manager writes permission denied for me too, but it isn't needs root at all, because it has access only to non root things, but nothing appears in it, not even the non-root files so it's broken in current nightly. But downloadable file manager like OI file manager, and root explorer works like it should.