yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Techbound:
I had the same issue after clean install ,couldn't get into my device because play services crashes after attempting to log into google account and setup wizard will start all over again and again and again ,so I got the aroma gapps and chose to remove cyanogen setup wizard got everything fine but may cause unexpected issues , then I decided to try using f2fs filesystem for system partition ,did that and clean installed the 30/09 build with micro gapps(google now launcher works well no misaligned app drawer) it works perfectly for me so just try it ;) no FCS
[Galaxy S 4 Mini Original Android Development] mdhuma:
Try TWRP 3.0.2.0 with clean fresh install,may work without error,
[Galaxy S 4 Mini Original Android Development] droopyar:
perfect

Works almost perfect all features.

Install and do the factory reset and wipes. This is important por stability.

Also FLASH Gapps for Android7. Older ones could crash something.

Do clean install and works perfect!
[Galaxy S 4 Mini Original Android Development] Vas0sky:
I'm having problems with the file manager (crashes when trying to open or open the menu for files that require root access). The battery style doesn't change anything. I'm having problems using the external sd card as internal (trying to move apps doesn't work with error: not enough space), flawless if I use it as external storage though. The Quick pulldown for the status bar doesn't work, nor does the Brightness control (that sliding through the status bar to change the brightness thing). I cannot disable the backlight of the buttons (only using the on-screen nav bar disables the light), nor I can reduce the timeout. The cyanogenmod launcher has misaligned apps. The camera gives "can't connect to camera" error and crashes when pressing the button to take videos.

I tested this after wiping data, cache and dalvik cache from CM13 and flashing this CM14 and gapps 7 nano. (You need to flash both the CM14 and the gapps without rebooting, otherwise you will get errors with either google play services, the package installer or both, this is a thing since CM13 and maybe even before).

Not every issue is a problem for me, e. g. I don't use the cyanogenmod launcher or the brightness control, but it would be nice to have nice and clean CM14 so I'm reporting them anyways.

Since it's the 3rd (or the 4th) version of the software that's ever been out for this phone (serranoltexx), it's simply awesome to have a fully working nougat version just a month later than its release date while others with official firmware and new phone are still waiting... Thank you so much, I'll use this daily over the official CM13. If I find new flaws and bugs I will report them here.

Again, Thank you so much for this cyanogenmod version, I hope it will make it and become the official one.
[Galaxy S 4 Mini Original Android Development] jakepsec:
Only main issue i noticed is the auto time zone not accurate with WiFi or mobile data enabled (in Canada). When these are not enabled, the time zone is right. Thanks for the ROM.
[Galaxy S 4 Mini Original Android Development] Kralisec:
After flash with 30/09 LTE: default network was configured to use 3G (17/09 use LTE as I expect)
[Galaxy S 4 Mini Original Android Development] csendre:
Is anybody experiencing Bluetooth issues? I can't get it to work on an Oct 07 build I made for the duos
[Galaxy S 4 Mini Original Android Development] sej7278:
time to repo sync like a mofo, as even if they do continue under a new name its going to take a while before the infrastructure is in place
[Galaxy S 4 Mini Original Android Development] arco68:
Project will continue, just under a different name.
[Galaxy S 4 Mini Original Android Development] zerolaunch:
Finally, You build latest one too.

Unfortunately, I can't see this build from official download anymore, but... Thank you for your hard work.

I hope to see your next works soon.

Maybe Lineage OS? Or something others like OmniROM?

Anyway, once again, Thank you for your kindness for a long time.
[Galaxy S 4 Mini Original Android Development] MrGoodtunes:
That is because this build of CM-14.1 is currently in testing, as indicated by [TEST] in the thread header. Also, accordingly, the flashable ZIP filename contains the word UNOFFICIAL, meaning this build is not available via the official CM repository.
[Galaxy S 4 Mini Original Android Development] zerolaunch:
Sorry for bad English.

It's not meaning what I want that.

I know that is test build.

But if CM was not shut it down, CM 14.1 will be official soon. :crying:

That is what I want to say.
[Galaxy S 4 Mini Original Android Development] Whitest:
I don't understand why dirty flashing merry christmas build 20161222 doesn't work for me. When flashing it gets stuck completely at step "flashing system image unconditionally" and I have to force reboot into recovery, wipe system & reflash 1210 build + gapps to make everything work again. I use latest TWRP 3.0.3-0 and downloaded build 20161222 3 times and each time the same problem. Any ideas?
[Galaxy S 4 Mini Original Android Development] bmwdroid:
I've tried dirty flashing, but it made a clean install and I couldn't do anything against it.

Nevertheless, I'm glad that this phone is still supported.

I would like to change my recovery from clockworkmod to twrp for this would allow me to backup data without system.

Clockworkmod makes a complete backup with no option.

Reinstallation of all the apps is probably much easier, than building this ROM.

At least for me. :)

I've read, that the twrp does not work with nougat.

Has anybody tried it anyhow, or knows anything different?
[Galaxy S 4 Mini Original Android Development] ProGameAndy:
TWRP v3.0.3 is compatible with Nougat, so it should work without any problems.
[Galaxy S 4 Mini Original Android Development] DerMoeJoe:
twrp 3.0.3 works fine with the newest build....
[Galaxy S 4 Mini Original Android Development] DJHasis:
Could you share your changes?

Would be nice to try what you have done.
[Galaxy S 4 Mini Original Android Development] Jo VDG:
I switched to Philz Touch for the previous major upgrade: http://xdaforums.com/showthread.php?t=2463322
[Galaxy S 4 Mini Original Android Development] csendre:
Guys, "official" is just a word, it has no real significance. arco68 is the developer for Serrano, so everything built with his device sources and LineageOS ROM sources IS the official version. Otherwise it is just semantics.
[Galaxy S 4 Mini Original Android Development] sej7278:
you're new here aren't you? this is xda-developers, we don't share, we just brag.
[Galaxy S 4 Mini Original Android Development] sysKin:
Sure.

Add Linaro's GCC 6.1. I did this by modifying .repo/local_manifests/roomservice.xml with the following:

Then, make the build system use it by modifying build/core/combo/TARGET_linux-arm.mk

(linaro now has GCC 6.2 too; it was not available back then so I haven't tried it)

Second change: the kernel we have doesn't build with GCC 6 because it only has headers for 4 and 5. However, headers for 5 work for 6, so do this:

- find a file /kernel/samsung/msm8930-common/include/linux/compiler-gcc5.h

- and copy it into a file named /kernel/samsung/msm8930-common/include/linux/compiler-gcc6.h

From now on, I mostly did this: "try to build, and if something fails because warning is treated as error, change the corresponding makefile to remove -Werror from it". Occasionally I would fix the code to avoid the warning instead, especially if it's obvious that the code is faulty.

This led to a large set of changes and unfortunately at this point I don't even know which of them are necessary anymore. It's always a mess to keep track of those :(

So, here's a full repo diff I currently have. I haven't built for ~three weeks so it might be out of date. It will almost certainly contain changes that aren't strictly needed.

https://www.dropbox.com/s/d14h255masgkg2e/diff.diff?dl=0

Moreover, this diff contains some optimisation flags that are independent from GCC 6 - mostly in build/core/combo/TARGET_linux-arm.mk. You should see it's got -O3 on place of -Os, and -Wl,O1 passed to the linker. You can use them without any GCC changes.

One last thing: after using -O3, the recovery image is too large to fit on our devices. I "faked" a larger recovery space in our device/samsung/serrano-common/rootdir/fstab.qcom to avoid build errors, but the recovery image is unusable.

Hopefully this helps a bit. I always end up with a mess of changes, not remembering why I did this-and-and-that, sorry about that :/

[edit] I just remembered something: if you use CCACHE, you need to clear it (or point it to a new location) because CCACHE is not aware you're using a new GCC and would provide cache hits, returning binaries from previous GCC. Such a trap.
[Galaxy S 4 Mini Original Android Development] IronRoo:
+1

I will miss that!

I've not installed as yet (was going to over Xmas but will now wait until LinageOS is somewhat established) do you have to go into settings every time to change profiles? How many taps? Is there a better set of triggers that you can use to switch profiles automatically?
[Galaxy S 4 Mini Original Android Development] Jo VDG:
I guess (hope) the tile will be added back. Too many taps to switch system profile from the settings now. The automatic triggers probably work as before (I see all the options in the settings) but I never found a set of triggers that fits my needs. So I prefer to switch profiles manually.
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
Can I dirty flash this on CM13 without losing data? if I do will be able to do the same to an official build?
[Galaxy S 4 Mini Original Android Development] Whitest:
No you can't. Clean flash required as it's a completely different version of Android (CM 13 = Android 6 Marshmallow, CM14.1 = Android 7.1 Nougat) after clean flashing CM 14.1 you can dirty flash future builds though. But be sure to check for LineageOS because the project is going to change it's name.
[Galaxy S 4 Mini Original Android Development] koutsman7100:
happy new year to every one!!

Arco,when do you estimate for the new built to come out?

just asking and nothing more
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, would be nice to have it, though I don't think it will be added back as it seems to be the nougat design. :(

I used to use an automation app, llama, prior to CM13, then tried a few other apps on CM13 but decided they weren't really worth it with the restricted access they had in Marshmallow (I didn't want to have root on permanently) so have been switching profiles manually or using a few triggers like Bluetooth to start Automobile profile etc, which was better than nothing.
[Galaxy S 4 Mini Original Android Development] DJHasis:
Thanks for your help.

I used almost all of your changes and Sabermod's 5.2 for the ndk and UberTC's 5.3 for the rest. I used O3 and also enlarged the recovery partition size and the image is usable. I've been using your changes for few days and I haven't had any major problems.

I think the major problem why your recovery image is not usable is because your using the same toolchain for all. And I thinkthat arm-eabi includes different set of tools that are needed for the ndk and recovery image to function properly.
[Galaxy S 4 Mini Original Android Development] Thoadi:
I still have hidden data traffic, one App has access, but not listed (even not as System App) in data saver settings...:eek:

Well, didn't work in Android M neither. So I had "APN on off" App by curvefish. It worked in Android M as System App, but doesn't run in N. Well, it's maybe not Nougat like ATM.:confused:

However, found the switch in APN settings, but it's inactive. How can I activate the toggle for APNs?

See image :cool:

I only use WLAN, just in emergency I'd like to activate APN for mobile data. Otherwise I spend 10...30 cent a day for nothing. A friend even spend 1 Bug for a day due to his pay plan.

Thanks for help...
[Galaxy S 4 Mini Original Android Development] echo124:
[MENTION=3044346]arco68[/MENTION] are you staying with your current device or moving on soon to something else? Thoughts on Lineage promising? Thanks! ;)

http://www.gsmarena.com/samsung_galaxy_alpha-6573.php

https://xdaforums.com/galaxy-alpha
[Galaxy S 4 Mini Original Android Development] HaselnuesseTo:
Hey [MENTION=3044346]arco68[/MENTION].. I tried flashing build cm-14.1-20161222 but I all of my gapps are crashing. I tried opengapps and dynamic gapps 7.1 mini, but on every boot there are errors of all gapps. It worked perfectly with older builds around cm-14.0-20161028.. I already tried this webview fix: http://www.gammerson.com/2016/11/fix-google-play-services-error-cm14.html

EDIT: I used twrp 2.8. I updated and everything is fine now!
[Galaxy S 4 Mini Original Android Development] zegovernator:
Hey, I wanted to know if anybody is having modem issues with this ROM. I'm sufferung from extreme signal loss on German provider T-Mobile. I updated to the modem to I9195XXUCOI4, since this was the last official modem updated to by this provider (according to sammobile.com). Flashing the newest European modem I9195XXUCPI1 won't do any change. Running CM13 it seems to be all fine. I know this ROM is still in early development stage but this is quite strange. Do you guys have any suggestions how to fix this? Is this maybe a RIL related problem?
[Galaxy S 4 Mini Original Android Development] ericlnu:
That log error is just the update-script, it's not serious.
[Galaxy S 4 Mini Original Android Development] Thoadi:
Full signal here... I also use I9195XXUCPI1 from XDA Member redjamesg, TWRP 3.0.2 and did factory reset...
[Galaxy S 4 Mini Original Android Development] Thoadi:
The solution is to move the App APNonoff by curvefish to "/system/priv-app/" folder,

in the "system/app/" folder, the App don't have permission to write APN Settings.
[Galaxy S 4 Mini Original Android Development] neca:
Maybe it's a silly question. :confused:

In settings, there is no theme menu. :confused:

How do I appear? :eek:

I wanted to change the colors :D

[IMG="Thema"]http://img.wonderhowto.com/img/original/78/66/63557715912285/0/635577159122857866.jpg[/IMG]
[Galaxy S 4 Mini Original Android Development] ProGameAndy:
The theme engine isn't implemented yet.
[Galaxy S 4 Mini Original Android Development] neca:
And will it be available soon? :confused:

I like this ROM, and congratulations to your development.

And I would like to keep on my GT-I9195LTE :cowboy:
[Galaxy S 4 Mini Original Android Development] csendre:
Maybe arco can provide more info on this but I heard rumours saying the theme engine project is dead. Other CM/lineage based ROMs are now integrating OMS support to work with the substratum theme engine
[Galaxy S 4 Mini Original Android Development] piojan:
Wifi location problem

Has anyone else noticed a problem with wifi that occurs once in a while (one a few hours, days) in the following way:

- despite wifi being enable it show that it's not connected and in a scanning stat

- when it enters this scanning state battery drains quickly (like 30%/hour).

- disabling and enabling wifi most of the time couses it to return to a normal connected state and stops battery draining.

I have looked at the similar issued and for a few day I now have wifi scanning disable (under location settings) and this problem does not occur.

Anyone had this befoul and found a different workaround / fix?
[Galaxy S 4 Mini Original Android Development] arco68:
First test builds of LineageOS 14.1. I don't know if dirty upgrading from previous CM build will work properly, so a clean flash is recommended.

GT-I9190 (serrano3gxx): lineage-14.1-20170121-UNOFFICIAL-serrano3gxx.zip

GT-I9195 (serranoltexx): lineage-14.1-20170121-UNOFFICIAL-serranoltexx.zip
[Galaxy S 4 Mini Original Android Development] kevinarol:
Thank you [MENTION=3044346]arco68[/MENTION] I will test later :good:
[Galaxy S 4 Mini Original Android Development] vagika:
hi, seems dirty is not working.....

anyway, awesome job, really really THANKS Arco. keeping device alive..!
[Galaxy S 4 Mini Original Android Development] :
Oh arco you're "back"!!!! Ty dude!!
[Galaxy S 4 Mini Original Android Development] Whitest:
just did a clean flash with latest LOS build from arco + latest open gapps - sadly there's a problem at setup, after connecting to WiFi a "Tap & Go" page/feature appears, which does not show any "Skip" button, so seems unskippable for now. I don't have any 2nd phone with NFC around here, so I can't continue setup for now... Seems there a small bug in setup assistant. Read about it in Galaxy S5 forum as well so seems to be a general LOS problem.

EDIT: Workaround found on reddit
[Galaxy S 4 Mini Original Android Development] sej7278:
what's in your roomservice.xml for lineageos [MENTION=3044346]arco68[/MENTION]?

my old cm13.1 has this, i assume we can't just change the project name?

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_serranoltexx" path="device/samsung/serranoltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8930-common" path="device/samsung/msm8930-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_serrano-common" path="device/samsung/serrano-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_msm8930-common" path="kernel/samsung/msm8930-common" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" groups="pdk" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
</manifest>
[Galaxy S 4 Mini Original Android Development] arco68:
Change CyanogenMod to LineageOS. But you also need to re-init.

repo init -u git://github.com/LineageOS/android.git -g all,-notdefault,-darwin,-mips,-x86 -b cm-14.1

Might be best to start with a fresh init though to avoid any problems.
[Galaxy S 4 Mini Original Android Development] sej7278:
ok thanks i'll give it a go, yeah i just downloaded a fresh lineageos 14.1 and kept my old cyanogenmod 13 repo

edit: it built fine thanks.
[Galaxy S 4 Mini Original Android Development] artu72:
Unfortunately after yet another fall (thanks to my 3 year old daughter), my faithful S4 mini died: cracked display and does not turn on. The repair costs are too high and I am passed to a motorola moto E 2015 (no budget in this time). Arco, thanks for everything. I'm sad.
[Galaxy S 4 Mini Original Android Development] DonQuichotte:
[MENTION=700912]arco[/MENTION]

Hello Arne,

will you also provide this experimental build for migrating to LOS 14.1 mentioned here, cause dirty flashing on top of even a LOS 14.1 rom does not work? I would be glad to avoid setting up the whole phone again.

Anyway, thank you for still supporting the SGS4M.

...bye DonQ
[Galaxy S 4 Mini Original Android Development] tako2k:
Dirty flashing from cm-13.0-20161211-NIGHTLY-serranoltexx. All is fine! No error, all function are running well and fast! Video is running too!! Bravo and thanks!
[Galaxy S 4 Mini Original Android Development] jooosi:
Dirty flashing from cm-13.0-20161212-NIGHTLY-serranoltexx was also no problem. Just had to reflash gapps, because Play Services were not working. Thank you for the good work, Arne!
[Galaxy S 4 Mini Original Android Development] Layeen:
After dirty flash, several processes were crashing so I did clean and everything is fine. I just miss one thing. At the point where I have to transfer my account from another device using NFC or BT, on CM I could skip it. Now I cant and I had to do it.
[Galaxy S 4 Mini Original Android Development] Diresh:
I used latest banks dynamic gapps and I could skip it.
[Galaxy S 4 Mini Original Android Development] bppjenil:
Well done

Thanks a million Arco for lineage rom. I installed and each and every functions works smoothly. My phone always with full of apps and all are working smoothly.

I feel something missing is THEME SUPPORT. Hope we will see soon...
[Galaxy S 4 Mini Original Android Development] Smeagal192:
Clean install on my 95 working a treat, along with pixel experience ,:laugh:
[Galaxy S 4 Mini Original Android Development] areshinakya:
Dirty flashing was working without a (noticeable) problem on my gapps free serranoltexx.

Thanks a lot [MENTION=3044346]arco68[/MENTION]

Is everything needed in lineageos git by now or are there still pending patches I have to manually apply before building myself?
[Galaxy S 4 Mini Original Android Development] piojan:
I don't see the MS Exchange account type options available (for email and contacts). Is this my local problem (maybe gaaps) or something more general? Has anyone tried adding it through Gmail? (for the contact look up).
[Galaxy S 4 Mini Original Android Development] neca:
I see there is a new version.

Can anyone tell me if this version has already implemented the theme engine?

Thank you :p
[Galaxy S 4 Mini Original Android Development] _Matsiev_:
No
[Galaxy S 4 Mini Original Android Development] M1chiel:
Yes, I set up my Exchange account through Gmail several times, but not in this specific rom. Calendar and contacts are also synchronized.
[Galaxy S 4 Mini Original Android Development] wfonz:
Using the latest build, no problem at all.

Thanks a lot [MENTION=3044346]arco68[/MENTION].
[Galaxy S 4 Mini Original Android Development] arco68:
The experimental build is just for migrating from a build signed with test keys, to a private signed build. We only have unofficial builds so far, thus no private signed builds, so there's no point yet.

Everything apart the bionic one for camera is there.

That's odd. You sure it's not there?
[Galaxy S 4 Mini Original Android Development] kevinarol:
Hi, just want to know if someone else is having issues with google keep in this rom? In my case the app keep loading infinitely
[Galaxy S 4 Mini Original Android Development] sej7278:
delete
[Galaxy S 4 Mini Original Android Development] Thoadi:
CM Filemanager crash when scrolling in ext SD Card DCIM at about image 257 of 360...

Logcat:

Lot's of...

01-24 21:29:42.855 W/ExifInterface(28171): Skip the tag entry since tag number is not defined: 2

and...

01-24 21:29:57.399 E/AndroidRuntime(28171):	at java.io.ByteArrayInputStream.read(ByteArrayInputStream.java:194)

Uncountable oft...

01-24 21:29:57.409 E/AndroidRuntime(28171):	at android.media.ExifInterface.readImageFileDirectory(ExifInterface.java:2294)

...stack overflow.

First issue since 1.Jan. and old QuickPic Version stopped working... :crying:
[Galaxy S 4 Mini Original Android Development] csendre:
No need for this language, please show respect to other users.

---------- Post added at 10:40 PM ---------- Previous post was at 10:35 PM ----------

You can try one of the Lineage based custom ROMs with OMS support for Substratum themes
[Galaxy S 4 Mini Original Android Development] neca:
:eek::(

---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------

Well, that's what I had to do. I do not like the white color in the menus :cyclops:

'll wait a little longer :cool:
[Galaxy S 4 Mini Original Android Development] kevinarol:
I've been trying the available nougat roms since yesterday with the must recent opengapps package and all the roms gave me the aame issue ?
[Galaxy S 4 Mini Original Android Development] csendre:
You mean the Google Keep issue? That is not a ROM problem, something is not OK with your gapps package. Use a pico or micro gapps package and install Keep from the play store. I just tried it and works. I am on an opengapps mini package.
[Galaxy S 4 Mini Original Android Development] kevinarol:
I have tried two pico pacckages, one from 20170115 and 0123 and the same problem, from which date is yours?

*sorry for bad english*
[Galaxy S 4 Mini Original Android Development] csendre:
I am still using a 12/30 mini package, maybe you can still find it in the archive.

I would also suggest a clean flash, maybe that is the issue