yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I'm currently on 0425 and had no problems flashing it. In my CM12-run I've had one instance where it did not boot. I had just installed a custom theme (style, boot logo, font etc.) and did not remember that there had been talk in this thread about custom themes causing problems. Luckily I had a nandroid backup so I did a clean install and restored it. After that, every time I flash a new nightly, I first check every box on the default theme menu making sure that I'm not using a custom theme. From then on I've had zero problems.

I got the problem solved although I didn't follow your suggestion but simply deleted the backup ringtones on the external SD. After another nightly flash, my ringtone settings were intact. Thank you for pointing out the problem.
[Galaxy S 4 Mini Original Android Development] jnvdh06:
What bugs are still present in this rom?

Which gapps should be used? https://www.androidfilehost.com/?fid=95916177934550004 Is this version fine?
[Galaxy S 4 Mini Original Android Development] honeyx:
I´m missing in this ROM the toggle for national Data-Roaming like it was present in CM10.2. Have to use international Data-Roaming to get it working.

Edit: I´ve rechecked this and the issue remains even with Data-Roaming enabled. Just less frequent. Problem is, my provider now supports national data-roaming and since now auto connecting to mobile data often doesn´t work. Insteed I´m getting a popup asking to connect. Enabling data roaming makes this happen less frequent, but the issue remains. With Cm10.2 this is working flawless, even if national data-roaming is kept disabled.

Edit 2: Latest nightly seems to have fixed this. Thanks Arne :)
[Galaxy S 4 Mini Original Android Development] Sprudeldudel:
latest nightly OTA update bricked my phone

Hey guys, in on twrp 2.8.5.0 and these nightly releases. Today's nightly installed ok, but after optimizing the apps it directly shut down. On the next reboot it again went into the optimizing process, but it's was only optimizing one app 1/1. After that it directly shut down again.

That's it. When I now try to power up, it will vibrate, but not even show the Samsung logo. I can't boot into android, not into recovery and also not into download. The screen is just black.

Any ideas?
[Galaxy S 4 Mini Original Android Development] Miccia:
Battery at 0% ???
[Galaxy S 4 Mini Original Android Development] Sprudeldudel:
battery is charged fully. i had charged it overnight before applying the update. :(

update: it went into rcovery after leaving it laying for a while. *relieved* went to previous nightly and all is well :)
[Galaxy S 4 Mini Original Android Development] kyrillos13:
Seems like a battery problem. I installed nightly 01/05 nightly just fine!
[Galaxy S 4 Mini Original Android Development] honeyx:
You shouldn´t use OTA without having CWM installed. There are plenty of warnings to not to use it when using a different recovery type and also to disable updating CWM in the ROM in this case. However, when you ignore them and still use OTA, it´s your fault.

Most likely the kernel that comes with the recovery got corrupted or the recovery itself.

You can try the blind method to reflash the recovery first by using Odin. So you must blindly try to bring it into download mode and see if Odin recognizes it. Should this work, flash CWM first. Reflash the Rotkit and the ROM afterwards and then you can go back to TWRP.
[Galaxy S 4 Mini Original Android Development] honeyx:
There is a slight glinch in the ROM. Sometimes when unlocking the screen the last app in the recent app view (the one on the top) gets relaunched. To avoid this the recent apps list needs to be cleared manually.
[Galaxy S 4 Mini Original Android Development] h1gh1:
I had no problems running TWRP, and I do regular updates. It supports Open Recovery Scripts, and it takes care of CWM not replacing it. Why would there be a problem when all it does is just flashing the zip update?
[Galaxy S 4 Mini Original Android Development] Sprudeldudel:
don't worry. :) Twrp is fine.
[Galaxy S 4 Mini Original Android Development] bryant88:
Hey guys! Looks like we are finally getting our first 12.1 nightly. Is there someone who flashed it? Do I need to make a full wipe, or cache and dalvik wipe is fine?

Thanks :)
[Galaxy S 4 Mini Original Android Development] hollandais:
Not yet, this morning I've flashed the 20150503 5.02 nightly.

Where have you seen the 12.1 ?

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Royal Ranger:
http://www.cmxlog.com/12.1/serranoltexx/#cm-12.1-20150504-NIGHTLY-serranoltexx.zip

Its available finally :) but i havent tried it yet, need to backup first
[Galaxy S 4 Mini Original Android Development] Razvan:
Yes, today nightly is CM 12.1 first release.

http://www.cmxlog.com/12.1/serranoltexx/#cm-12.1-20150504-NIGHTLY-serranoltexx.zip
[Galaxy S 4 Mini Original Android Development] bryant88:
Anyway guys FYI I just flashed it. I installed the 5.1 gapps and wiped cache and dalvik. It works!
[Galaxy S 4 Mini Original Android Development] hollandais:
I just found it. Dirty flash over 5.02 gives some problems. I'll do it again with a clean flash.

Envoyé de mon GT-P5110 en utilisant Tapatalk

---------- Post added at 06:01 PM ---------- Previous post was at 05:36 PM ----------

Back after a factory reset and flash of 5.1 gapps. Seems much better.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I guess I can now take a breather (have been flashing CM12 nightlies every third nightly) and let the CM12.1 mature before I give it a go. When I do flash the CM12.1, would this be correct procedure:

Backup contacts, call logs and SMS

Backup Whatsapp (backup via the app and make a copy of the Whatsapp folder)

Backup apps (but not app data) with Titanium Backup Pro

Backup launcher (I use Nova)

In recovery (TWRP), wipe cache, dalvik, system and data

Flash CM12.1

Flash GAPPS for 12.1 (for CM12 I flashed the full GAPPS linked to the instructions in this thread not realizing that you could use other GAPPS as well, so I I will now flash the PA-GAPPS Pico)

Flash kernel (F4K's kernel did wonders for my battery life and made everything a little bit smoother)

After first boot, restore contacts/call logs/SMS, install Titanium Backup Pro, restore apps.

Am I missing something?
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Gapps advice? I was using Micro PA Gapps with 12.0, can anyone recommend a minimal gapps package for 12.1? I prefer not to have too much Google bloat. Thanks
[Galaxy S 4 Mini Original Android Development] mikle85:
Hy!

New thread is open for 12.1 and there you can find the gapps package you need. since 12.1 is LP 5.1.1 you will need an 5.1.1 compatible version of gapps. Also F4ktion has a 12.1 build and in his thread you can find the minimal gapps, i think it would work as well.
[Galaxy S 4 Mini Original Android Development] hollandais:
Thanks, can you give us the link?

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] mikle85:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Would took you the same time to find it, but im a nice guy.. :)
[Galaxy S 4 Mini Original Android Development] AndroidxWolF:
New updates official cm12.1 for gt-i9190/i9195 :D
[Galaxy S 4 Mini Original Android Development] hollandais:
Yes, I know that you're a nice guy. Many thanks.?

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] luisbraz:
DELETED
[Galaxy S 4 Mini Original Android Development] honeyx:
Just flashing the zip via TWRP recovery is no problem, but doing OTA can corrupt TWRP recovery. It doesn´t mean it will for sure but this can happen. So belive me. These warnings are not for no reason. My TWRP UI got corrupted once too because I was a bit lazy that time but got this fixed.

So to sum this up. No problem by flashing a downloaded zip. But for using OTA CWM is recommended.
[Galaxy S 4 Mini Original Android Development] henrikusz:
Going to stock ROM

Hello,

a short question: what I need to do to go to stock ROM without any trouble or bootloop?:good:?

Thanks.
[Galaxy S 4 Mini Original Android Development] honeyx:
1. A flashable stock ROM zip.

2. Either CWM or TWRP recovery.

3. Enter the Recovery and whipe Dalvik, Cache, Data and System first. (Don´t forget to do a Backup of your present ROM before doing these steps -just in case)

4. Install the zip with the stock ROM and you should be fine.

in case of some troubles repeat the steps or flash it via Odin.
[Galaxy S 4 Mini Original Android Development] h1gh1:
I did all the OTA updates with TWRP. I mean, it is just running a script which flashes downloaded zip in /sdcard/cmupdater. Recommendation or not, common sense says that there should be no problems if you are running TWRP, and F4K has compiled 2.8.6.0.
[Galaxy S 4 Mini Original Android Development] twingor:
Works will release the 5.6? Me Setup stops in the middle! 5.5 is O.K.
[Galaxy S 4 Mini Original Android Development] honeyx:
Nice it worked for you but common sense or in other words in theory and the practice are two different things.

Like said I´m using TWRP too but never again for OTA. For me it just corrupted the UI and for the other guy a few posts back it obviously bricked the device. So these are just two practical (not just common sense) examples who are telling the opposite of your experience with OTA by using TWRP.

I also like TWRP over CWM but there are also a few other aspects that should be taken into account. TWRP is a universal recovery being ported to each device whereas CWM is designed by CyanogenMod Team to fit the CM ROMs build for the specific devices.

By using Arcos CM Builds together with his specially for his builds configured CWM Recovery the chances to brick your device are almost zero. Whereas by using a different recovery the chances are bigger.

So lets stop discussing what in theory. The bad examples about using OTA together with a different recovery other than CWM are enough prove of evidence.
[Galaxy S 4 Mini Original Android Development] h1gh1:
How can you be sure that recovery was the problem there? CWM development stopped. Arco probably builds his recovery along with the device tree, and F4K uses TWRP source with CM tree. If it is configured properly, it will work. Was there no one that had a brick with CWM? You are quick to blame something, while you can not be sure where the problem is.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
Question, does this also include cm recovery as standard? I'm hoping it's a no :)

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] h1gh1:
Not sure on that. New default recovery is even more basic than CWM.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
Indeed and I had it on i9100 5.1.1 rom so had to install slim rom in cm recovery as it brought back twrp and then flashed cwm recovery. I'm still on stock 4.4.2 firmware but rooted and cwm recovery but not willing to change to cm12 if it has their own recovery

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] h1gh1:
You can use CWM or TWRP. When you flash the ROM, just disable recovery updating in developer options.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
Before flashing?

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] h1gh1:
Yes. Flash the recovery, and then the ROM.
[Galaxy S 4 Mini Original Android Development] honeyx:
Dude. The problem is in which mode the recovery is entered. So who of us is quick about blaming something or trying to blame someone.

No offense to you or to F4K but have been there where you are. Jus stopped my active time here due to my education and changes in my private live. I´m talking from experience and I´m also able to port a recovery or take Arcos sources, compile a ROM or tweak a kernel. So this is not just theoretical and hypothetical. My experiences are going back to the time of the Galaxy W and S+ where Arco was also the main dev and the community was even bigger that this one.

And guess why I bought the S4mini now? Because I appreciate Arcos work. Had a S3mini meanwhile and the dev there is somewhat ... So now being just a passive User I prefer a device where I trust in the skills of the dev who is working on CM for it. And just by the way. I still own the Galaxy W with Arcos ROM on it and my personal kernel

So stop talking to me like to a noob and you beeing the wise guy just because you recently started to compile your own ROMs and offering some Alphas.

There is a difference in blaming something or just warning. When someone is telling you not to fill diesel in your car because your car needs gasoline, there is nothing to blame about. Niether the car nor the type of full.

Last but not least the facts are telling their own truth and the truth is TWRP is just ported but Arcos CM builds and CWM Recovery are comming from one hand. So even not very wise guys will know a CM from one dev and a recovery from someone else may cause troubles whereass this will be not that risky when both are comming from one and the same person.

And the truth is there are some cases where for example using OTA together with TWRP caused troubles to some ppl. Ignoring this and trying to blame someone will not change these facts.
[Galaxy S 4 Mini Original Android Development] h1gh1:
Again there are zero facts in your post, that proves that TWRP causes bricking. I do not need to know about your education, or cars. Were there no bricks with CWM? I bet there were. And do not tell me that you have been where I have, please. Again you speak without having anything to back you up. How could you know that? I do not thrust your judgment, neither with this nor with that TWRP matter.
[Galaxy S 4 Mini Original Android Development] :
Why don't you make official ROM for i9192?
[Galaxy S 4 Mini Original Android Development] honeyx:
Again, I´m not going to bring you facts nor to prove you something. The facts are out there speaking for themeselfes. So I will not search for all this just to quote it here to prove you anything. Belive it or not. Your theoretical and hypothetical arguing doesn´t make this better. And we are not in the kindergarden to play your personal war.

This just as a reminder for all the others. Posted by the dev himself:

His warning is basing on facts without going now into detail.
[Galaxy S 4 Mini Original Android Development] h1gh1:
As I said, you have no arguments. It's no personal war, you just make statements that you can not back up.
[Galaxy S 4 Mini Original Android Development] Charlie:
Hello guys.I want to ask which cm version is stable for daily use.Latest nightly or a previous version? Thank you!
[Galaxy S 4 Mini Original Android Development] h1gh1:
Latest 12.1 nightly is stable enough.
[Galaxy S 4 Mini Original Android Development] Charlie:
I will not do everyday updates, i dont need new features im just fine with stable versions with everything working. So saying latest version you are talking about this wright? --> cm-12.1-20150509-NIGHTLY
[Galaxy S 4 Mini Original Android Development] h1gh1:
Yes, I updated today to that one. It's working fine, but some bugs can be expected - it's nightly build still. You can update OTA every week or so.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
Does cm recovery come with this rom?

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] honeyx:
Because I´m not willing to aruge with you. What are your arguments? NONE! All you do is bringing for some reason F4k into play. Implying I´m blaming him and arguing with some theroretical statements. There is nothing to blame him when the problem relies in the Recovery itself and he just ported it. But you even are not clever enough to recognize the difference about this.

This are no real arguments just flaming around. Trying to blame me by implying i do so and trying to blame Arco by summing up your statements he is giving false warnings.

Either you bring some facts insteed of just making theoretical statements and flaming here, or stop this. Else the only one whom you are blaming is you yourself.

You even had no clue what I was talking about by saying the problem relies on the mode in which the recovery gets entered and want me to bring details? Sorry. Do your maths first before accusing Arco and me to give false advice.
[Galaxy S 4 Mini Original Android Development] walttheboss:
Can I ask on behalf of all of us that the personal battles be done on private messages. It is wasting lots of space. Thanks for both of your contributions but enough is enough.

Thanks.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
+1

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] honeyx:
Agree on this. Well said :)
[Galaxy S 4 Mini Original Android Development] h1gh1:
And what mode would be that? You got no clue what you are talking about. There is no special mode, it just runs the script by default and restart after script finishes. It flashes the full ROM - downloaded OTA by running updater script, and this is just the same as it would be to run install from GUI and point it to a zip file. Fact is that it is working properly on my phone for a month, each day, and I did not see any corruption, nor do I see why would you blame TWRP for yout UI corruption, or complete brick that some other guy had. You got nothing to say, except that developer recommends CWM and that TWRP corrupts devices somehow. That just makes no sense. And this will be my last take on this, excuse me for being so hard on this, and tiring for other members, but since this ROM is EOL now, I guess this is not that much of a problem.
[Galaxy S 4 Mini Original Android Development] jimbomodder:
2

you

and you take this to pm and stop filling the thread with a pointless argument. Both recovery have a + & - so deal with it and move on:banghead::banghead:

Sent from my GT-I9195
[Galaxy S 4 Mini Original Android Development] jinan:
Last Nightly is broken?

Is it just me or did the last Nightly "cm-12.1-20150513-NIGHTLY-serranoltexx.zip" break the UI?
[Galaxy S 4 Mini Original Android Development] hollandais:
In the Q & A thread there are others.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] hollandais:
Dirty flash of the 20150514 over the 20150512 is OK.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] twingor:
BLN

Hello. What can I do to get my work BLN? Thanks.
[Galaxy S 4 Mini Original Android Development] hollandais:
Just dirty flashed the 20150516 nightly over the 20150515 one. Seems OK.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] tgoncuoglu:
GPS

Ever since an update from (I think) about 2-3 weeks ago, my GPS seems to be unreliable. Is it just me or are others experiencing that too ?

By unreliable I mean it seems like working on mobile+wifi info only, not the actual gps device. Even if you choose "high accuracy" or "device only", so its accuracy seems limited.

As of now I have the 20150518 NIGHTLY installed (on my GT-I9190), but as I said, its been like this for 2-3 weeks.

TIA
[Galaxy S 4 Mini Original Android Development] hollandais:
I'm using the 20150518 nightly, and my gps works fine.

In my garden it gives me an error of 8 mtr.
[Galaxy S 4 Mini Original Android Development] twingor:
Nightly ended?
[Galaxy S 4 Mini Original Android Development] hollandais:
I don't think so, take a look here. This should be in the next nightly.

http://www.cmxlog.com/12.1/serranoltexx/

Envoyé de mon GT-P5110 en utilisant Tapatalk

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] twingor:
Yes. Version 23rd! Everything OK.:)
[Galaxy S 4 Mini Original Android Development] thepunisherbs:
New Gapps 2015-05-24: 15.05 Update

Following the link in the first post, new Gapps arrived...

https://github.com/cgapps/vendor_google/releases/tag/2015-05-24
[Galaxy S 4 Mini Original Android Development] jukyO:
211 Mb? Pfff....
[Galaxy S 4 Mini Original Android Development] twingor:
v. 25

Version 25 you can not install it.: O (. Even through the built-in recovery, despite Philz touch or automatic update ...
[Galaxy S 4 Mini Original Android Development] hollandais:
I just downloaded and flashed nightly 20150525 over the 20150523. Dirty flash, no problems.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Oudanios:
Thanks Brother
[Galaxy S 4 Mini Original Android Development] twingor:
Root

I did a clean installation. 26 and lost Root.: O (How do I get it back? Thanks in advance for your advice.
[Galaxy S 4 Mini Original Android Development] hollandais:
Try this:

Go to settings/ Developer options/Root access.

There set one of the options: I've set Apps and ADB.

But don't disable.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] twingor:
Q: How the heck do I get root?

A: Goto Settings and About Phone. Tap Build number 7 times. Go back and enter

Developer options. Change Root access to desired method.
[Galaxy S 4 Mini Original Android Development] hollandais:
Yes, I forgot your clean install.

Go to settings/About phone.

Search build number, and touch 6 or 7 times. Your device will tell you that you're now a developer.

Go back to settings, and you'll find developer options.

Further as I told you before.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Razvan:
[MENTION=3044346]arco68[/MENTION]

Man, here I discuss about CM12.1 at last few pages. Can we close it?
[Galaxy S 4 Mini Original Android Development] hollandais:
Sorry man, I just would help someone.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] Razvan:
No need for excuses but I find it very difficult and unnecessary to follow the discussion about same ROM in two different threads, isn't?
[Galaxy S 4 Mini Original Android Development] hollandais:
Yes, you are right. But I think that it always happens. In another thread I did it also.?

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] twingor:
I also apologize, but I did not know where I get answers. So I for a single thread of this ROM.
[Galaxy S 4 Mini Original Android Development] twingor:
Verzion 4.6.

Verzion 4.6. Not found:(
[Galaxy S 4 Mini Original Android Development] Razvan:
http://download.cyanogenmod.com/get/jenkins/112788/cm-12.1-20150604-NIGHTLY-serranoltexx.zip
[Galaxy S 4 Mini Original Android Development] twingor:
Thanks.It works as an official ...
[Galaxy S 4 Mini Original Android Development] thepunisherbs:
Hi [MENTION=3044346]arco68[/MENTION] , i use my phone around Russia but my phone language is Italian and i noticed this problem with CM12, Phone can't automatically see the timezone. It automatically put the timezone of central europe(+1) but usually i'm in the Moscow timezone, now i'm in the Yekaterinburg (+5) and i must choose it manually. Sim card is Russian and with CM11 i had no problems.
[Galaxy S 4 Mini Original Android Development] DavidSnake:
Really? I've just watched my phone going from 20% to our of bat in less than 2 min.. it was almost funny, the numbers going down like a bomb in austin powers..

I have only sync and mobile data (or wifi if at home), location in low battery mode, and the rest if off.

I'll try the others apps you posted later on, see if it improves...
[Galaxy S 4 Mini Original Android Development] arco68:
See if it's related to selinux. Try disabling it and then test.

adb shell setenforce 0
[Galaxy S 4 Mini Original Android Development] Insomniac-Butler:
Mine was the same with any previous ROM I've had too but I always use this configuration and its like a different phone, running 3g/4g all the time seems to be the big one for me, that's why I use network toggle type 5, always use 2g unless I'm away from WiFi an need to use the net. It toggles from network type pretty quickly so works for me but try the whole combination of what I listed, you be surprised