Since the last build (12/22) settings no longer crashes and shows a pop-up, but selecting anything but "don't change" (or whatever it is called in English) shows "null" as value.
I also miss the tile to switch profiles from the pull down menu.
[ROM][GT-I9190/I9192/I9195][Official][7.1.2] LineageOS 14.1 for S4 Mini
- Thread starter arco68
- Start date
I also miss the tile to switch profiles from the pull down menu.
Works great for me on GT-I9195. No critical bugs noticed so far. Only sometimes a previously paired Bluetooth device is not immediately reconnected. Have to turn Bluetooth off and the on again to make the contact.....
RIP CM, was hoping this would get official status soon but seems Cyanogen has delayed it to never 
G
GuestD2436
Guest
Hey arco... will you continue to develop this build after these news? Death of CyanogenMod
Last edited:
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
Project will continue, just under a different name.
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.
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.
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.
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.
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?
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?
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?
TWRP v3.0.3 is compatible with Nougat, so it should work without any problems.
Could you share your changes?
Would be nice to try what you have done.
I switched to Philz Touch for the previous major upgrade: http://forum.xda-developers.com/showthread.php?t=2463322
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.
you're new here aren't you? this is xda-developers, we don't share, we just brag.
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.
Last edited:
+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?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone