yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Charlie:
For me every time I update to a newer snapshot, cwm recovery asks me to fix root(before exiting recovery). Maybe it's something relative to this?
[Galaxy S 4 Mini Original Android Development] micheclb:
I never actually updated it! And after the first installation everything was working correctly!
[Galaxy S 4 Mini Original Android Development] _cosi_:
CM12.1 provides an option to move an app to SD Card but that has several drawbacks:

- For some apps it does not work at all

- As soon as an app is updated, it's placed in internal flash again

- Shortcuts to Apps on SD card are removed on next restart

Additionally, when updating from Android 4.x to 5.x you will get ART instead of Dalvik cache, using more space for every application.
[Galaxy S 4 Mini Original Android Development] hollandais:
Yes, I've seen this on my gtab2 under 5.1.1. Same problem.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] artu72:
Other sideback effect:

When installing a new CM version, at first restart phone performs app optimization in two stages: 1) apps on internal memory; then it performs a soft reboot and then optimize apps on SD card.
[Galaxy S 4 Mini Original Android Development] hollandais:
Yes that's right. The first time I believed that my apps had disappeared, then, after a reboot, they were back again. But some shortcuts should be created again. This happens on my gtab2, so I think it's ROM related.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Draylin:
If you are sure that you have activated root in the developers settings and root still doesn't work you can just flash the SuperSU zip to install SuperSU and its root binary.

To answer your second question: The updater installs the newest version automatically through the recovery. But it actually makes no difference if you use the updater or just download the *.zip and install it yourself in the recovery. Although your data should still be there after an update it's always a good idea to make a full backup before flashing.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Still getting no sound issue randomly with calls after performing voice search. Really annoying not being able to use voice search/dictation.
[Galaxy S 4 Mini Original Android Development] Draylin:
I don't think so. At the release of CM 12 somebody said that this issue is caused by a small incompatibility from CWM to Lollipop and that the user should choose not to fix root.
[Galaxy S 4 Mini Original Android Development] sej7278:
i haven't managed to complete a build for a couple of weeks (last success was 14th november) due to some libvpx error:

target StaticLib: libvpx_asm_offsets_vp8 (~/cm12/out/target/product/serranoltexx/obj/STATIC_LIBRARIES/libvpx_asm_offsets_vp8_intermediates/libvpx_asm_offsets_vp8.a)
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: ~/cm12/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: ~/cm12/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:31: error: unsupported reloc 43
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:787: error: unsupported reloc 43
clang: error: linker command failed with exit code 1 (use -v to see invocation)
build/core/host_executable_internal.mk:31: recipe for target '~/cm12/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/libvpx_obj_int_extract' failed
make: *** [~/cm12/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/libvpx_obj_int_extract] Error 1

anyone know the fix? i'm using debian sid 64-bit, been building cyanogenmod since 7.0 and not had a problem. it looks like its the linker stage, but there's something about clang which i don't have installed, i'm using gcc (installing clang doesn't help)
[Galaxy S 4 Mini Original Android Development] sevenrock:
http://review.cyanogenmod.org/#/c/120824/

The last comment explains how to disable the use of clang.
[Galaxy S 4 Mini Original Android Development] sej7278:
ah lovely thanks, itrying a build with "WITHOUT_HOST_CLANG=true" now, i'll report back if it works in 30mins or so. so it seems its a conflict with ccache.

edit: yes it seems to be working, although getting this sort of warning for almost every line of output now, so it would be nicer to get clang working properly rather than disabling it:

warning: unknown warning option '-Wno-unused-local-typedef' [-Wunknown-warning-option]

edit 2: failed again with:

cc1: error: unrecognized command line option '-integrated-as'

i then installed clang-3.8 and the build got a bit further, but then fell over with the old:

external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:31: error: unsupported reloc 43

disabling ccache didn't fix it.

clang 3.8 installed and "WITHOUT_HOST_CLANG=true" set didn't fix it.

setting "WITHOUT_CLANG=true" errors with:

arm-linux-androideabi-gcc: error: unrecognized command line option '-fno-slp-vectorize'

setting "CLANG_CONFIG_arm_EXTRA_CFLAGS=" instead of "-no-integrated-as" as well as "WITHOUT_CLANG=true" failed, back to the reloc 43 crap again, i give up.
[Galaxy S 4 Mini Original Android Development] Mitko:
Any plans for CM13?
[Galaxy S 4 Mini Original Android Development] sej7278:
looks like it: http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_serrano-common
[Galaxy S 4 Mini Original Android Development] Charlie:
---------- Post added at 10:15 AM ---------- Previous post was at 10:14 AM ----------

First nightly of cm13 is up.
[Galaxy S 4 Mini Original Android Development] hollandais:
Hi, thanks,

Can you give us the link to the topic please,

Thanks

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Mitko:
It's at the Galaxy S 4 Mini Original Android Development

Link to thread: http://xdaforums.com/galaxy-s4-mini...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
[Galaxy S 4 Mini Original Android Development] hollandais:
Sorry, I forgot to say "Thanks". It's a nice ROM.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] aurisltu:
Hello everyone I was gone for a long time. Where stable builds gone?
[Galaxy S 4 Mini Original Android Development] Mutoid:
Can`t find change log.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
They have started releasing CM 13 nightlies so no more 12.1
[Galaxy S 4 Mini Original Android Development] hollandais:
Changelog for cm13: http://www.cmxlog.com/13/serranoltexx

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] davidmlondon:
I am using the last 12.1 snapshot. Will stick with 12.1 for a while. My question is should I install the last 12.1 nightly or stick with the snapshot? There have been quite a lot of nightlies since the snapshot.
[Galaxy S 4 Mini Original Android Development] Loulou-13:
hi !

with this new cm13 ,cyanogenmod team don't release a "final" LP cm12.1 ?

this last nightly is FULL stable & verified ?
[Galaxy S 4 Mini Original Android Development] Charlie:
Just to understand how things work, I have the latest snapshot of 12.1, will an update hit my phone from CM updater(snapshot channel) when a marshmallow snapshot released? It works just like an update? Because is more than a simple update.

Thank you guys and merry Christmas to all :highfive:
[Galaxy S 4 Mini Original Android Development] hollandais:
Take a look here: http://xdaforums.com/showthread.php?t=3276141

and you'll find there all you need to know before flashing this ROM.

Envoyé de mon GT-P5110 en utilisant Tapatalk

---------- Post added at 06:23 PM ---------- Previous post was at 06:20 PM ----------

Take a look on the first post..

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Charlie:
Ok thanks I knew that, but I want some theoretical explanation of upgrading to a newer android version process , just to learn some things.
[Galaxy S 4 Mini Original Android Development] Mutoid:
Hello. Will be new CM 12.1 snapshot?
[Galaxy S 4 Mini Original Android Development] Charlie:
I don't think so, maybe a last stable build because cm12.1 builds stopped.
[Galaxy S 4 Mini Original Android Development] playitlouder:
I've just read that CM13 is not quite ready yet (unstable mobile data).

Does anybody have the latest CM12.1 nighly. It's not on CMs servers anymore.
[Galaxy S 4 Mini Original Android Development] Charlie:
https://download.cyanogenmod.org/?device=serranoltexx
[Galaxy S 4 Mini Original Android Development] playitlouder:
http://get.cm/404/jenkins/140374/cm-12.1-20151221-NIGHTLY-serranoltexx.zip

This is the latest CM 12 nightly. 404 ;)
[Galaxy S 4 Mini Original Android Development] redjamesg:
I have the 20151120 lying around if needed.

Sendt fra min GT-I9195 med Tapatalk
[Galaxy S 4 Mini Original Android Development] aurisltu:
Something is wrong. I lost 80% of battery over night. And now I loosing 1% of battery every 2 seconds.
[Galaxy S 4 Mini Original Android Development] Royal Ranger:
Try calibrating the battery. That helped for me
[Galaxy S 4 Mini Original Android Development] Mr. Death:
Sometimes I have similar problem. Usually restart helps to stop battery drain. I suspect something like Play Service update.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I'm on the last CM12.1 Nightly and experiencing a serious problem with my S4 Mini. Yesterday I set a pattern lock screen (not using any lock screen apps) and it worked great. However, I now only get a dark screen with no 'pattern dots' and when I try to make the pattern I set estimating the 'dots', I get "wrong pattern". I've tried this a million times with no results. I've rebooted the phone, wiped cache/dalvik via TWRP, taken the battery out, the works. Nothing helps.

Is there a way to bypass this malfunctioning CM12.1 lock screen or do I need wipe the whole device and start over.
[Galaxy S 4 Mini Original Android Development] tchavei:
Doesn't the phone vibrate when you pass a dot with your finger? That should be enough to guide you to draw the correct pattern?

I think there is no way to bypass the screen lock unless you have the phone rooted with adb enabled and even then I'm not sure.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
No, it does not vibrate. I do have the device rooted (switch it on via developer's options) and I'm pretty sure the same goes for ADB.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I didn't find a way to bypass the lockscreen but luckily found a workaround so that I didn't have to start over. Firstly I took a nandroid backup of this malfunctioning ROM. Then I restored a 3-week-old nandroid, updated the apps and used the paid Titanium app to extract the missing app data (most importantly, lost Whatsapp discussion) from the malfunctioning ROM (amazing you can do this). Now I'm back to where I left off and will not be using the pattern lock screen any time soon.
[Galaxy S 4 Mini Original Android Development] Tom Mix:
attention!

no, it is not amazing,

as you have not encrypted your device.:silly:
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
I believe there's a setting for taking the dots in the lockscreen settings. Maybe you activated it by mistake
[Galaxy S 4 Mini Original Android Development] Tigerman82:
Okey, I wasn't aware of this. However, if there is such a setting and it was the cause of this, I seriously have to question the reasoning behind it. I mean I basically had a simple Z-pattern and, having a sort of photographic memory, I tried to draw it on the supposedly invisible dots dozens of times in different spots. I even took another Samsung with the spots visible next to my phone and tried to pinpoint the exact location of the dots. However, I wasn't able to login. I mean that setting would then mean that you are locked out of your own phone as it apparently requires hundreds of tries and drawing the dots with a pen on to the display so that you hit them perfectly.

Anyway, I do think that this was just some sort of bug.
[Galaxy S 4 Mini Original Android Development] tchavei:
There was a way to recover through your Gmail account if your phone is setup for Gmail. I used it once to unlock my son's phone since he created a pattern and forgot about it.
[Galaxy S 4 Mini Original Android Development] arsm74:
[MENTION=3044346]arco68[/MENTION] would it be possible for a new snapshot created for CM12.1 for i9190/95 with all fixes in November/December 2015 from CM team? I see the last one is 20151117 ....thanks for all your work again...
[Galaxy S 4 Mini Original Android Development] Selenikss:
Help

no sound on 12.1-20150327-UNOFFICIAL-serranoltexx

No music, no notifications, it only vibrates.

I've cheked the buttons on the phone, but still nothing.
[Galaxy S 4 Mini Original Android Development] bierma32:
Flash the lastet stable Version from CM 12.1, Download link you can find here http://download.cyanogenmod.org/?device=serranoltexx&type=snapshot release date 2015-11-17
[Galaxy S 4 Mini Original Android Development] Loulou-13:
hi everybody !!! ;)

someone have the last cm12.1-20151221 ,please ???

cm download site give 404 error ....
[Galaxy S 4 Mini Original Android Development] Selenikss:
[MENTION=5390857]bierma32[/MENTION] Thanx it worked.
[Galaxy S 4 Mini Original Android Development] :
Hello

I am trying to build cm12.1 from sources. That used to work until recently. The build process gives errors and eventually stops.

Here's the output:

target thumb C++: components_user_prefs_gyp <= external/chromium_org/components/user_prefs/user_prefs.cc
host Executable: third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp (/cm/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/libvpx_obj_int_extract)
target StaticLib: third_party_libvpx_libvpx_intrinsics_neon_gyp (/cm/out/target/product/serranoltexx/obj/STATIC_LIBRARIES/third_party_libvpx_libvpx_intrinsics_neon_gyp_intermediates/third_party_libvpx_libvpx_intrinsics_neon_gyp.a)
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /cm/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /cm/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/third_party/libvpx/source/libvpx/build/make/obj_int_extract.o: unsupported reloc 43 against global symbol stderr
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:31: error: unsupported reloc 43
external/chromium_org/third_party/libvpx/source/libvpx/build/make/obj_int_extract.c:787: error: unsupported reloc 43
clang: error: linker command failed with exit code 1 (use -v to see invocation)
build/core/host_executable_internal.mk:31: recipe for target '/cm/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/libvpx_obj_int_extract' failed
make: *** [/cm/out/host/linux-x86/obj32/EXECUTABLES/third_party_libvpx_libvpx_obj_int_extract_arm_host_gyp_intermediates/libvpx_obj_int_extract] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory '/cm'

Someone pointed to this commit causing the problem: http://review.cyanogenmod.org/#/c/120824/

But even reverting the commit does not help. Also setting WITHOUT_HOST_CLANG=true did not help.

Any ideas how to solve this problem? Maybe [MENTION=3044346]arco68[/MENTION]?
[Galaxy S 4 Mini Original Android Development] :
Hello

Got CM12.1 compiled again.

Some things one has to do to finish the compiling process.

1.) Use an older linux distribution like debian jessie. Debian Sid and recent ubuntu versions have a problem with binutils - compiling CM12.1 is not possible at the moment.

2) One has to apply some commits. This is because clang makes problems and breaks the build. And because the commits only made their way into CM13, they have to be applied manually for CM12.1.

To be applied are these three:

.

If this is done, CM12.1 build just fine. Built it some minutes ago with debian jessie. ;)
[Galaxy S 4 Mini Original Android Development] Mr. Death:
Could you please provide some download link? I'd like to update my CM12.1. Thank you!
[Galaxy S 4 Mini Original Android Development] :
Sure. Where is a good place to upload it?

---------- Post added at 03:55 PM ---------- Previous post was at 03:38 PM ----------

Uploaded my build.

Filename: cm-12.1-20160113-UNOFFICIAL-serranoltexx.zip

Link:

https://www.sendspace.com/file/crwhj1

MD5-Sum:

693710f6273ed1eff40b9c2aad119999

P.S.: This build works. ;)
[Galaxy S 4 Mini Original Android Development] fankool:
thank you Thomson, but how can I manually apply the commit? Do I have to add them after installation of rom, I suppose.
[Galaxy S 4 Mini Original Android Development] :
These commits have to be applied before building the rom; you apply them to the source code.

They cannot be applied to the rom itself.

You can use my prebuilt rom from the comment above or you build the rom on your own.
[Galaxy S 4 Mini Original Android Development] LaShto34:
Are there real fixes compared to snapshot 20151117?

I mean real fixes...

I know there is a page with changes, but it'a a long list and not in "english" (you know what I mean).

Thank you in advance for an answer.

By the I uploaded here modded kernel for this version with selinux permisive and superuser mod (modded services.jar) if anyone is interested.
[Galaxy S 4 Mini Original Android Development] Mr. Death:
I think it's commited latest nighlies. CM 12.1 is still in development, some devices even don't have CM13. If you are on november snapshot it's the latest snapshot.
[Galaxy S 4 Mini Original Android Development] LaShto34:
I knew that. I just wanted to know the changes (major ones) between 17.11.2015-13.01.2016.

Nevermind...
[Galaxy S 4 Mini Original Android Development] fankool:
Sorry for my question. I'll install your rom in the next 2 days, if something's wrong I'll post here.

thank you
[Galaxy S 4 Mini Original Android Development] john-soda:
+1!!!!!!!!!!!!!
[Galaxy S 4 Mini Original Android Development] Loulou-13:
hi ;)

i have found !!!

===> http://xdaforums.com/galaxy-s4-mini/help/mirror-cm-12-1-20151221-nightly-t3294121
[Galaxy S 4 Mini Original Android Development] john-soda:
Thanks very very much!!!
[Galaxy S 4 Mini Original Android Development] LaShto34:
I'm just saying, but 20160113 CM12.1 work very well. I did not find a bug so far.

It's posted just a page back.
[Galaxy S 4 Mini Original Android Development] Tonyco1:
Hello,

I want to install this last stable ROM.

Here it is what I do till that moment. Before few years I root my the GT-I9195 using ClockworkMod from this tread: http://xdaforums.com/showthread.php?t=2364980 and also from this tread I flash stock kernel with this one in the tread, so it solve the problem with battery draining.

Now I want to install CyanogenMod 12.1 but it is written on first page: Warning: "Only use this recovery to flash CM-12.1. Otherwise, you risk bricking your phone!", my question is in case I am already root my phone with ClockworkMod and install custom kernel, can I flash CM-12.1 using TWRP Recovery using this method: http://www.androhippo.com/2015/10/how-to-install-any-custom-rom-using.html or I need to go again trough all procedures with odin ?

Also if I use TWRP Recovery, what should I do with Cyanogen Recovery .img file, because I see that only .zip file is used for TWRP Recovery method for flashing ROM.

Thanks for answers.
[Galaxy S 4 Mini Original Android Development] LaShto34:
From day 1 I flashed through odin twrp 2.8.7.0 from this thread http://xdaforums.com/showthread.php?t=2678420 (I have a GT-I9195). Never ever had a issue with CM 12.1 , no matter what build date and type.

CM recovery is used for making OTA updates only. It is like stock recovery. I never used it.
[Galaxy S 4 Mini Original Android Development] Tonyco1:
OK, but in my case with already rooted phone and custom kernel, I still don't have answer, can I use this method http://www.androhippo.com/2015/10/how-to-install-any-custom-rom-using.html to flash new CM12.1 ROM ?
[Galaxy S 4 Mini Original Android Development] LaShto34:
Yes.

Or you may simple follow op's first page instructions, but read twrp where it says cwm. :D
[Galaxy S 4 Mini Original Android Development] Tonyco1:
Thanks, I wait for my new GT-I9195i, and my old one I will give it to my wife, but first I want to put new ROM on it. I will let you know if it works fine with the method I described before.
[Galaxy S 4 Mini Original Android Development] Kong2000:
This is S4 Mini thread and it would be nice if you could stop spamming it with S4 stuff. There is no CM12.1 13.01.2016 ! :cyclops:
[Galaxy S 4 Mini Original Android Development] Tonyco1:
Please tell me what is the difference between NIGHTLY and SNAPSHOT versions of this ROM ?
[Galaxy S 4 Mini Original Android Development] Kong2000:
Too lazy to read? https://wiki.cyanogenmod.org/w/Serranoltexx_Info
[Galaxy S 4 Mini Original Android Development] LaShto34:
I think some of us really should learn to read forum posts before writing on this forum.

But life goes on...
[Galaxy S 4 Mini Original Android Development] Kong2000:
OK, this thread is official cm 12.1 and your file is unofficial. It would be nice if you could stop spamming the thread with unofficial stuff. :cyclops:

better?
[Galaxy S 4 Mini Original Android Development] LaShto34:
Listen to me, pumpkin, just admit you were wrong. That version was posted here so there was no reason to ask that question elsewhere.

OK? :cyclops:
[Galaxy S 4 Mini Original Android Development] Kong2000:
Postet by somebody like you moron spamming the thread?
[Galaxy S 4 Mini Original Android Development] LaShto34:
OMG. :cyclops:
[Galaxy S 4 Mini Original Android Development] Tom Mix:
ladies please!

unfortunately the moderation team here on xda seems to be to busy

to change the title of this topic from:

[GT-I9190/I9195][ROM][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE

to

[EOL][GT-I9190/I9195][ROM][Official][5.1.1] CyanogenMod 12.1 for S4 Mini 3G/LTE [EndOfLiFE a.k.a. EOL]

one can imagine what EOL means...:eek:

so if one takes a look into the CM12.1 Nightlies Changelogs the answer is given clearly:

err01: Device incorrect or not supported.
Device may have been transitioned to a newer version of CyanogenMod.

so my question is: WTF are you doing here?:confused:

arguing about official vs. unofficial :silly:

the serranoltexx chapter 'official cm12.1' was closed 2015-12-21!

welcome to 'official cm13.0' for serranoltexx!

...unsubscribed :rolleyes:
[Galaxy S 4 Mini Original Android Development] mick711:
Yes unfortunetly i never see Android Linux Windows Cyanogen OS finished need to change all time if you would like to are more secure. But need to change hardward frequently so i have Old phone with Old rom And Old computer with Old os, And vert happy. If its possible to answer à call with button no slide its greet i never find after Froyo.