yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] hollandais:
For me it's good. I use it from the beginning as a daily driver. But I don't have special usage.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] toppits:
Just installed it on my gf's phone and it seems pretty stable to me.

Just the new Recovery from Cyanogen has very little options. Can't flash another Kernel for BLN with it (or am I doing sth. wrong?) and even Nandroid Backup isn't possible.

The pinning feature doesn't work that good, I wasn't able to unpin, but that seems to be a general problem with phones with hardware keys for now (if I didn't miss anything). Only restart let me use the phone again.

edit: I had the thing with the names displayed wrong. Not sure if that fixed it, but i switched to the "wrong" option to display it and changed it back and everything was fine again, on 15.03.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
I've been using as a daily since the start. There have been some bugs but nothing show stopping. Make sure to do a proper clean install, format /system, /cache and /data. But like all ROMs different people have different experiences depending on what they do with their phones.
[Galaxy S 4 Mini Original Android Development] Tirofog:
Still having an annoying problem here with the battery charge displayed, after a reboot it drops drastically e.g. from 46 to 9 per cent just now. The phone is a little over a year old so doubt if a new battery is the answer.

That works until the next time you go back into the dialler..
[Galaxy S 4 Mini Original Android Development] marcooleo:
But the Bluetooth problem still remains.. ?
[Galaxy S 4 Mini Original Android Development] canu7:
I don't have network data either with the 20150315 nightly. I can make, receive calls and SMS but there is always an exclamation mark in the network signal.

I can see no problems with the APN settings. I can create, delete and modify my configurations.

Is this the right place to notify this bugs? Does arco read this or should we fill a bug on JIRA?
[Galaxy S 4 Mini Original Android Development] bassie1988:
I do not have problems with data, it all works fine! I'm also on 20150315 with F4k's kernel.
[Galaxy S 4 Mini Original Android Development] toppits:
This might be a stupid question, but how did you flash the Kernel? I can't flash it with the Recovery that comes with the 15.3. nightly. So the only way I can think of is, that you had the Kernel before, flashed the new nightly and the Kernel again, right? But as i already have the crappy cyanogen recovery, how can i get there? :(

edit: no problem with data or anything here either, with the stock kernel.
[Galaxy S 4 Mini Original Android Development] semdoc:
Flash TWRP recovery :o

http://xdaforums.com/showthread.php?t=2678420

Then flash ROM + kernel in a row...
[Galaxy S 4 Mini Original Android Development] kblee0:
I tried turning off "ok Google" detection during two days. Sometimes I used voice search. I could no longer experience the "no-sound problem".
[Galaxy S 4 Mini Original Android Development] creatif:
I love this rom, and use it as a daily driver. The only bug I found:

- when connected to a power source, I receive Whatsapp messages.

- when not connected, I only receive them when I turn on the screen...

Any ideas?
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Apologies, I meant to report back. I have also done some voice searches by pressing the mic button, I've also used handsfree for voice calls and have not had the "no sound" problem in calls. Looks like ok Google detection may be the cause. Will let you know if anything changes.
[Galaxy S 4 Mini Original Android Development] ivbsd1:
Hi,

Do you plan to release snapshot or stable for CM12 in the nearest future ?
[Galaxy S 4 Mini Original Android Development] RyQril:
i guess soon enough, check this commit and its comments

http://review.cyanogenmod.org/#/c/91742/

"Branch: stable/cm-12.0-YNG1T"

http://review.cyanogenmod.org/#/c/91743/
[Galaxy S 4 Mini Original Android Development] 96DANGER96:
SoundAbout app fixed the problem for me!
[Galaxy S 4 Mini Original Android Development] Lizardway:
Visualizer bug

If lock screen visualizer is off and you turn on battery saver and then turn it off, lock screen visualizer turns on by itself.

P.S> WOW! It ll be fixed in 20th nightly! Thx!
[Galaxy S 4 Mini Original Android Development] saintxseiya:
[MENTION=3044346]arco68[/MENTION]

Hi,

i am trying to build the cm12 with your repos in the first post, but i am not succeeding, the mini just shows the Galaxy Splash screen and there it stops. :(

Any idea?

Cheers,

saint
[Galaxy S 4 Mini Original Android Development] Miccia:
Logcat?

How did u build?

For which devices?
[Galaxy S 4 Mini Original Android Development] saintxseiya:
Ciao Miccia,,

it is the serranoltexx, logcat is not possible, as it dows not boot, stuck at the very first splashscreen.

build was initiated with a local_manifest and the repos that i could find in the official first post.

gcc 4.8 standard toolchain

Francesco
[Galaxy S 4 Mini Original Android Development] pranjal18:
Hi! Can it be ported to i9192 variant?
[Galaxy S 4 Mini Original Android Development] Miccia:
Just repo sync, make clobber, then brunch serranoltexx and u are good, cause is a supported device
[Galaxy S 4 Mini Original Android Development] mooon3:
Hi there, does anyone could tell me which nightly was the last compiled from 5.0.1 before it get to 5.0.2 ? I don't know how to figure out... Thanks!
[Galaxy S 4 Mini Original Android Development] XxM4tzexX:
The official cm guide works for me.
[Galaxy S 4 Mini Original Android Development] saintxseiya:
Hmmm still it does not boot at all :( for sure that i do not have to add some vendor in manifest or something similar?
[Galaxy S 4 Mini Original Android Development] Miccia:
If u do brunch it will automatically download all. Have u done make clean before? And repo sync?
[Galaxy S 4 Mini Original Android Development] androidroot4u:
how do you root this rom i flashed the root zip for kitkat and its says no su binary.can someone give me the link to the su update and do i have to factory reset and flash the rom over again and then flash the su zip
[Galaxy S 4 Mini Original Android Development] arco68:
You sure you have the proprietary files in vendor/samsung?
[Galaxy S 4 Mini Original Android Development] saintxseiya:
That is why i asked if i have to ask vendor files ;) so should i add the vendor files vendor/samsung/serrano-common from the muppets by the local_manifest?

Thanks for helping out!
[Galaxy S 4 Mini Original Android Development] arco68:
Yup.
[Galaxy S 4 Mini Original Android Development] saintxseiya:
Hey, did that, but same problem persists :( Crazy thing.
[Galaxy S 4 Mini Original Android Development] Lizardway:
Media scanner works improperly. After rebooting it starts work without saving previous state. It causes no recent tracks in Eleven and wasting time before listening music or watch videos\pictures from gallery.

And sometimes "Battery charging" title is holding on lock screen and if you want to hide it you have to reconnect the phone to a charger.
[Galaxy S 4 Mini Original Android Development] dong2007:
After i updated from nightly-18 to nightly-21 - My S4 mini (i9195) bootloops to splash screen, when I go to enter the PIN :/ others with the experience??
[Galaxy S 4 Mini Original Android Development] hollandais:
No, but I went from 18 to 20 and then from 20 to 21.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] dong2007:
Which Modem version do you use? I use Modem I9195XXUCOB1 - Maybe that has the reason?

I´ve tried to wipe all user data , restore from my backup (nightly-17 working fine) and update to nightly-21 and same happens.
[Galaxy S 4 Mini Original Android Development] hollandais:
I use I9195XXUCNH5, Europe France.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] jopsinas:
I'm also using XXUCOB1 modem and 21st nightly works perfectly. Updated from 19th.

Try to clean flash without restoring anything.
[Galaxy S 4 Mini Original Android Development] chris42too:
XPrivacy - service context

Hi there,

would it be possible to include

xprivacy453 u:object_r:system_server_service:s0

into ramdisk/service_contexts to make XPrivacy usable with the ROM?

Original Info: https://github.com/M66B/XPrivacy#installation

Regards

Christian
[Galaxy S 4 Mini Original Android Development] sej7278:
i've got this as my .repo/local_manifests/roomservice.xml - the last line downloads the muppets proprietary files when you sync next:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_serranoltexx" path="device/samsung/serranoltexx" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" 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_qcom_fm" path="hardware/qcom/fm" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />
</manifest>

then like the official instructions:

repo sync
make clean
. build/envsetup.sh
brunch serranoltexx
[Galaxy S 4 Mini Original Android Development] skillz95:
I come from last CM11 nightly, this means i've to wipe all ?
[Galaxy S 4 Mini Original Android Development] XxM4tzexX:
It would be safer to do so.
[Galaxy S 4 Mini Original Android Development] RobinNet1:
When will be upgraded CM 12 to 5.1 version ?
[Galaxy S 4 Mini Original Android Development] skillz95:
I've flashed last fak kernel ( 2.0.5 ) and seems dat i cant put PIN code for my SIM card so i cant use it, how to fix it ? :(

Before it was workin fine..

EDIT : I've re-enabled stock lock screen ( i use CM locker ) bedore restarting phone and now it asks me for PIN, idk how this fixed the problem lol
[Galaxy S 4 Mini Original Android Development] John_Edward:
CM11 used to have both "Wake with home button" and "Unlock with home button", which combined with FaceLock enabled me to unlock with a double home click, without having to touch the screen (gloves etc).

In CM12, I've only found the Wake option.

Have I just missed the unlock option, or is it missing completely?

If it is, could it be possible to add it in ?

Definetely.

I accidentally updated from CM11 to CM12 without a full wipe, and it resulted in everything just force closing constantly.
[Galaxy S 4 Mini Original Android Development] skillz95:
Ok thank you all i've upgraded and now seems all is workin fine, last question, i don't have to flash gapps everytime i update to another nightly, right?
[Galaxy S 4 Mini Original Android Development] tds4u:
Try to wipe cache and dalvik cache after upgrade seperately inside Recovery. It's better to wipe system, too. But a SD card with ZIP file is expected...

- backup with e.g. Titanium

- install

- restore with e.g. Titanium

PS: GApps only if you wipe system on later update.
[Galaxy S 4 Mini Original Android Development] hollandais:
Right, you can do a dirty flash. But if you flash all (most) nightlys you better should do a full wipe sometimes.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] dong2007:
I've found out where the problem is. I used another Theme and this was the issue. So I changed back to the default Theme and now everything work again (nightly-22)

So for other there use other themes than default, be careful :)
[Galaxy S 4 Mini Original Android Development] chrmhoffmann:
cmupdater reboot shuts device off

Trying to update via cmupdater seems broken for me.

Note: I have a encrypted device...

The device takes ages to reboot and kmsg seems to show some (display related?) errors.

http://pastebin.com/raw.php?i=4kAasfGQ

Rebooting through the normal power menu works fine.

Chris
[Galaxy S 4 Mini Original Android Development] davidmlondon:
I notice in the last nightly that the quick menu tile to disable the lockscreen no longer works. Anyone else noticed this?
[Galaxy S 4 Mini Original Android Development] skillz95:
Is the CM Updater workin or it's broken and i've to download every nightly manually ?
[Galaxy S 4 Mini Original Android Development] tds4u:
Use recent TWRP version:

http://xdaforums.com/showthread.php?t=2678420
[Galaxy S 4 Mini Original Android Development] skillz95:
CWM won't work with CM updater?
[Galaxy S 4 Mini Original Android Development] hollandais:
I use the latest TWRP version, and CM updater works fine. Just flashed the 20150323 nightly, coming from the 20150322. The only thing I did manually was check for updates, accept download and accept flash. Boot into recovery, flash and reboot were done automatic.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] skillz95:
hmm ok but im on CWM and i wanna know if i can with this recovery or i've to install twrp :/
[Galaxy S 4 Mini Original Android Development] hollandais:
Maybe someone who uses CWM can reply?

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] skillz95:
nvm, i tried it, Cm updater is not workin with CWM, i downloaded the rom with cm updater and when phone reboots into recovery it automatically reboot another time in normal mode. I installed it manually.
[Galaxy S 4 Mini Original Android Development] XxM4tzexX:
It's rebooting because there is a error at the installation. This happens to me with twrp aswell. But twrp doesn't reboot automatically, instead it just stops and you have to flash the zip file manually.

Another thing is, I enabled the update of the recovery in the developer settings but everytime twrp is booting. Don't know why the new cwm isn't applied.
[Galaxy S 4 Mini Original Android Development] ChasingShadows:
AFAIK enabling the update of the recovery only works for CM recovery as the text says. It is not working for any other recovery like CWM or TWRP...
[Galaxy S 4 Mini Original Android Development] 96DANGER96:
CARRIER

two days ago I did a full wipe and installed the 22/03 nightly. But there is something strange, instead of "Vodafone IT" there is "Vodafone IT femto Network", why?
[Galaxy S 4 Mini Original Android Development] chrmhoffmann:
I am using the CM recovery, btw. [MENTION=3044346]arco68[/MENTION] any idea?

Chris
[Galaxy S 4 Mini Original Android Development] tchavei:
Mine showing Vodafone telecel (old name) while previously it was showing Vodafone PT

My guess is that somehow it's showing the old carrier names together with the new ones.

Regards

Tony

Sent from my keyboard through my phone or something like that.
[Galaxy S 4 Mini Original Android Development] ChasingShadows:
The carrier names are compiled into the rom. Obviously some name changes have not been seen by the developers.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I flashed the 24/03 nightly via TWRP to my S4 Mini LTE (int). It seemed bug-free except for a bug when, in contacts, trying to add a photo to a contact (some *.media app crashes everytime and I cannot get to choosing the photo). Unfortunately I came across a bigger problem. The messaging app crashed from time to time and can go into a devilish loop of crashes with a crash notice every two seconds. I did restore my contacts and messages via CM Backup so that might have done it. I tried to wipe cache/dalvik in TWRP which did not help and I also tried clearing the messaging app data which didn't help either. I'm currently flashing the 25/03 and hoping that would fix it. I'd hate to start again as it took me ages to get all my apps installed.

I did also have a problem with choosing which contacts the telephone/contacts app shows. After I had successfully restored my contacts, they disappeared and then appeared after another restoring attempt. I cannot find a menu where to choose which contacts are showed.
[Galaxy S 4 Mini Original Android Development] rolex2002:
[MENTION=3044346]arco68[/MENTION] When CM 12.1 beta will be for our device ?
[Galaxy S 4 Mini Original Android Development] gab_hamelin:
Be patient. Android 5.1 code is not even in cm yet.
[Galaxy S 4 Mini Original Android Development] rolex2002:
CM 12.1 for Nexus 5, OnePlus One etc...

http://xdaforums.com/oneplus-one/development/wip-cyanogenmod-12-1-t3063266

http://xdaforums.com/google-nexus-5/development/rom-cyanogenmod-12-1-nexus-5-t3063657
[Galaxy S 4 Mini Original Android Development] sej7278:
wow cyanogenmod recovery is rubbish isn't it - sure its nice to have touch, but no nandroid backup makes a recovery useless to me - who flashes without a backup?!

a quick "heimdall flash --RECOVERY recovery.img" as per these instructions put cwm 6051 back, but i'd rather not do that every time - especially as the flashable zip version doesn't work with cm-recovery.

i assume unticking "update recovery" in developer options will prevent cwm getting replaced by cm-recovery in future? or do i need to adjust my cm12 builds to stop bundling boot.img or something?
[Galaxy S 4 Mini Original Android Development] gab_hamelin:
Sorry. I did not found it

---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------

Just untick the option un developer
[Galaxy S 4 Mini Original Android Development] ahmedghazi:
Useless. It doesn't support Kies 3 !!!!!:(
[Galaxy S 4 Mini Original Android Development] ChasingShadows:
Exactly ...
[Galaxy S 4 Mini Original Android Development] kyrillos13:
Yes, and it won't support KIES at all. It's CyanogenMod, not Crapwiz.
[Galaxy S 4 Mini Original Android Development] sej7278:
yup, i can confirm that unticking the option stops the recovery being overwritten on subsequent flashes
[Galaxy S 4 Mini Original Android Development] twingor:
v. 26.3.

v. 26.3. 404 Not Found?!?
[Galaxy S 4 Mini Original Android Development] ahmedghazi:
Where I can find Crapwiz version !!!!!
[Galaxy S 4 Mini Original Android Development] 96DANGER96:
In call no sound problem... Again!! [MENTION=3044346]arco68[/MENTION] please can you explain us why nobody is trying to fix this problem?

Inviato dal mio iPad utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] hollandais:
I saw that there is a new nightly: 20150326.

When I try a download with CyanogenMod the device says: there's no new update.

When I try direct download through the browser, I see the file, and when I ask for download he ask me to install CM installer application. I did it and the device says "Sorry, your device is not supported". What's wrong?

Envoyé de mon GT-P5110 en utilisant Tapatalk

edit:

And when I try with my computer I've this error: 404 not found.

But I can download the 20130325 nightly with the computer as well with my I9195.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
I use cyandelta to update and that doesn't see the 0326 nightly either.
[Galaxy S 4 Mini Original Android Development] hollandais:
This morning my device found a new nightly (same date as yesterdays one) but the download and flash with CM updater is OK now.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Cyandelta found a new nightly today. Though it was the 0327 nightly. Seems to be fine.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
Recently I wrote about my troubles with the messaging app which kept crashing -- I was on the 25/3 nightly. I had restored my contacts and messages via CM (Cheetah Mobile) Backup which, as the first post of this thread warns, broke the messaging app. I decided to start from scratch and flash the 25/3 -- I'm using the latest TWRP found on these forums. This time I used SMS backup and restored my contacts via syncing them first with google on another phone. Everything went fine and this ROM indeed seems of daily driver caliber. My S4 Mini Int feels like a new phone without those annoying Kitkat-related restrictions I had with the stock ROM.

About updating... I'm not an expert on these matters, so I was not sure if I had to flash GAPPS every time I flashed a new nightly. Luckily I found the information I needed: no, you don't have to do that when updating between minor releases. I installed Cyandelta and let it import the 25/3 zip. However, it did not find any new nightlies even though 26/3 and 27/3 were already available. I then decided to try the CM Updater that comes with CM12. It downloaded the 27/3 super fast. I then manually booted to TWRP and flashed it. WIth 27/3 nightly running, my phone seems to have no bugs whatsoever. I'm not uninstalling Cyandelta just yet but it seems that using CM Updater and then manually flashing the new nightly via TWRP might be the best route to go. Oh, I do have to mention that with 25/3 Trebuchet started crashing (I had just used SD Maid Pro so that might be the reason) although I'm using Nova as my launcher. I cleared the app cache and, later on, updated to a new nightly and have had no notifications of a crashed Trebuchet since.

About CM12... It's fast, intuitive and simple. The battery drain seems to be on par with the stock ROM (I've not changed the governor/scheduler from Interactive/Row). I miss lock screen widgets (weather, battery percentage) but can live without them for now. The camera cannot save to ext sd which is why I'm currently using Open Camera as my primary camera app. USB OTG does not work for now. I would like to change themes but read from this thread that this might cause problems and I learned my lesson from restoring messages. All in all, I'm very pleased and it does seem like my phone is a 2015 model now.
[Galaxy S 4 Mini Original Android Development] hollandais:
Normally you can do an automatic update. The phone should tell you that a new nightly is up and you can tick this message for download. Otherwise you can do it semi-manually.

Settings/About this phone/Update CyanogenMod.

The new nightly can be shown there, otherwise you can refresh and find the new one. Tick for download, tick for flash, and with the latest twrp the phone goes into recovery, flash and reboot.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] S3miniFin:
There is another, maybe better soft for updating rom. Soft is CyanDelta. You can installing same time kernel update or gapps...
[Galaxy S 4 Mini Original Android Development] Dilshad969:
Can anyone report the issues faced on the latest buit
[Galaxy S 4 Mini Original Android Development] jnvdh06:
Im on 27/03 and everything seems to work perfectly
[Galaxy S 4 Mini Original Android Development] llapao:
Do you have otg working on latest build?

Thanks
[Galaxy S 4 Mini Original Android Development] jnvdh06:
Is it normal that the lock screen says charged even after I have disconnected it from charger? I have found this on all lollipop roms so far. Usually after reboot it goes away?
[Galaxy S 4 Mini Original Android Development] Tigerman82:
Earlier I wrote that the battery life of 27/03 was pretty much on par with stock ROM (Kitkat). I now have to say that it has a much better battery life. Although I am using apps like Greenify and try not to install any apps that I don't need, the battery would probably last well over two days with minimal usage. Especially when the screen is off, the battery percentage stays the same for an amazingly long time.

I now flashed 30/03 as the change log had a lot of changes/fixes but took a nandroid backup of 27/03 as it was just a great nightly for me.
[Galaxy S 4 Mini Original Android Development] jnvdh06:
In emails... The text gets mixed up with the reply buttons
[Galaxy S 4 Mini Original Android Development] robbo49:
Hi,

I' on the latest nightly build and my mic doesn't seem to work when calling people. However it works when using the google now application.

Any ideas?