yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Phenom2122:
So it seems that ever since you guys decided to take the choice away from people whether to use GApps or not, there have been all sorts of issues. Google Contacts sync crashes constantly and has for the last couple of months now, trying to back up contacts to your device as a vcf immediately crashes the contacts app and has for a couple of months now. I constantly get errors telling me my memory card is corrupt and needs to be reformatted even though I can usually access it sometimes I need to reboot. Tried formatting it on my phone and still the same story, this has been happening for the last couple of months now. The idea of formatting it as internal memory would be nice if you didn't end up with less space than before. I'm sure this stuff has all been mentioned before. I've been coming across other issues over time that don't come to mind at the moment too.

I used to think CyanogenMod was boring, then I absolutely loved the CM 13 release, now it seems that the cons are starting to outweigh the pros again and I'm thinking of going back to Carbon KitKat.

Besides the fact that the GApps thing is kinda a deal breaker for me, what is going on here? Are our devices just getting too old for the latest versions of Android?
[Galaxy S 4 Mini Original Android Development] maddoka:
Thanks for checking, I wiped data and cache for the music app, and wiped cache /dalvik partitions when I flashed the last nightly.
[Galaxy S 4 Mini Original Android Development] Migual12:
I have installed cm-13.0-20160708-NIGHTLY-serranoltexx with open_gapps-arm-6.0-nano-20160709 . Since two weeks charging of the S4 mini does not work any more. If I plug in the charger, the battery slowly gets empty. I already tried several chargers, cables, usb charging and different batteries. Additionally I replaced the USB plug with platin by a new one. It is still possible to use the device if I charge the battery externally. Also it is possible to connect it via USB to PC to chose the access mode and transfer date. Could this be an issue with CM 13 or could it be an hardware error? Did someone have a similar problem? Thanks
[Galaxy S 4 Mini Original Android Development] milouk:
Probably a hardware issue...i am on latest nighly and phone charges fine...make sure there is no dust in the usb port and also make sure there is a connection between the cable and the port..in some cases a minor adjustment is nedded in the port..there are some tutorials online
[Galaxy S 4 Mini Original Android Development] Phenom2122:
I'm not sure if it still applies to this latest version of Android but sometimes you may need to recalibrate your battery for your device after installing a new ROM. A simple app that has worked for me before (on another device) is called 'Battery Calibration'. Sometimes not all the steps can be followed, such as charging your device to 100% but it generally works after a try or two.

Also, you should be able to charge your battery to full in recovery mode first if you are having trouble getting the calibration app to work initially.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Sounds like it could well be hardware. But just to check, I assume you've checked & not seen an app using more battery than normal in battery stats. Also try an app like Trepn that shows you what is using your cpu,

I did have an issue a few weeks ago with browsers apps hogging cpu using constant 20-50% and draining battery. But it seems to have fixed itself, though flashing new nightly may have done the trick. You should clean flash new nightly, might fix it, if not hardware looks more likely

edit: as [MENTION=5767881]Phenom2122[/MENTION] mentions about the recovery, when I was on a nightly from a few weeks ago I booted into recovery and it showed much higher battery than OS did, first time I've ever seen this, I flashed new nightly and then the OS showed the same battery level as recovery.
[Galaxy S 4 Mini Original Android Development] :
What do you mean "ever since you guys decided to take the choice away from people whether to use GApps or not"? You can use gapps or not, it's your choice

The contacts sync problem is a gapps issue. Try TBO gapps or others

Contacts app crashing: have you changed dpi? This is a known problem if so. Another way to get the .vcf file is use the browser and go to your gmail account and create a .vcf file from there

Memory card issues don't happen for me. Maybe a faulty card?

Definately the device is not too old. My other phone is the S2 and it has MM roms working virtually perfectly. It's possible you are starting to see hardware issues though on your device.....
[Galaxy S 4 Mini Original Android Development] Phenom2122:
Play Store gets installed and the contacts sync crashes happen whether you install GApps or not. It might be something odd I'm doing on my phone but I've even done a clean install and this is the result so it seems to me that the basic GApps are included in this rom at the moment. As for the memory card thing, I'll see how it goes with an older rom that I've used extensively in the past. The only time I get an error with it is the last couple of months with this rom, it behaves perfectly when using the card in my pc with a card reader, however, no errors.
[Galaxy S 4 Mini Original Android Development] IronRoo:
No there are no Googly bits in CM, that's why you have to install separately. You have to install gapps else no play store

Are you restoring backups?
[Galaxy S 4 Mini Original Android Development] Phenom2122:
Hmm perhaps I was drunk or over tired the last time I tried. One thing that has made me reluctant to experiment is the fact I couldn't back up contacts (although there's probably an app for that I guess) so thanks for the tip to get a vcf backup working properly. When I'm around WiFi again I'll try downloading the latest release of this Rom and trying again with a fresh install. Thanks for the help.
[Galaxy S 4 Mini Original Android Development] :
Maybe you are not wiping /system when you flash a new rom. Normally the rom has a script to automatically format /system when you flash the rom. I have noticed this hasn't always happened in the past depending on the rom.

What I do when I clean flash is manually wipe system, data, cache and dalvik/art cache. Sometimes I wipe internal sd for an extra clean flash, (but this will wipe photos, media and data from /data/data) This is done from "advanced wipe" in TWRP
[Galaxy S 4 Mini Original Android Development] Migual12:
Thanks, what do you mean by minor adjustments. I already changed the small board including usb-female connector and checkt the plugs of the board are fixed well into the motherboad.
[Galaxy S 4 Mini Original Android Development] DarkJoker360:
who can send me some screenshot of cm 14 please? (tomorrow my s4 mini will be back :) )
[Galaxy S 4 Mini Original Android Development] bierma32:
THX [MENTION=3044346]arco68[/MENTION] for the CM14 Test Bulid , you have done a great work, at the moment all works perfect, good battery life.

Im send you a donation 75U449721J794502B
[Galaxy S 4 Mini Original Android Development] igor45:
Perhaps you are always using the "nightly" versions? Your post doesn’t specify the particulars.

IF you've got "automatically restore" app data (under backup & restore) set, then even though you do a wipe between flashes your data will carry over possibly taking a bug along with it. So that makes it effectively a dirty flash not a clean flash.

Again, because I don't now your specific situation that is one possibility to look at.

If it helps, in my case (i257m/i9195) the contacts sync issue is NOT a gapps problem, it is with the nightly 09-10. The issue exists with 3 different versions of gapps that I tried. >>>The same gapps with the stable release (08/20) works flawlessly for me<<<

The latest nightlies are buggy, that's why they are called nightly and are not in the "release channel" so not sure why you'd be upset over bugs. Bugs per device can vary, of course.

Again, I had a host of issues with the nightly 9-10, mainly the "contacts sync shut down" and terrible battery drain (100% within one hour) Now stable with 08-20 release

I suggest you go to the stable cm13 (08/20), making sure you are actually achieving a clean install and you'll be good.
[Galaxy S 4 Mini Original Android Development] Phenom2122:
If someone isn't supposed to complain about bugs in nightly versions then perhaps, just maybe, the nightly versions shouldn't be available OTA? I'm no spring chicken when it comes to this, in fact I have been around on this website for a while now using various Roms and recoveries in different forms. While I appreciate the helpfulness, I do not appreciate having nightlies explained to me in italics like I am a child. Also, you quoted my entire post but clearly missed the part where I said this stuff has been happening for months..

On that note, as convenient as OTA updates are, it's a double edged sword. With previous Roms without OTA updates, a user had to come to the forum where they could read about every issue without being taken by surprise and participate, now it becomes a case of 'why bother'. I think a good way to get people to not complain about bugs in nightlys would be simple - only provide stable frikken versions OTA and for those who want nightlys, they must come to the forum. It's not the UI for OTA updates is incredibly advanced or anything, it shows the last three versions and that's it, you cannot browse through other versions even if you wanted to and with nightlys being, well nightly, the stable version disappears very quickly, in fact I was unaware there even was a stable version before coming here now. Sort that sh*t out before having a problem with people coming here to report bugs.

Thanks for your help but I already came to a conclusion earlier and I will try again when I have WiFi access.
[Galaxy S 4 Mini Original Android Development] Migual12:
Now I tried to charge in recovery mode. It shows the same effect. Every 15-20 minutes the percentage of battery dropped about 1 %. Starting point was 43%, the same value displayed before in CM13.

With Ampere App I measured the following values:

During discharging: 34%; 3,71 V; about -130mA

During charging: 33%; 3,74 V; about +160mA

During USB charging: 33%; 3,74 V; about +170mA

It seems that the voltage does not raise enough to sufficiently charge the battery.

Even with the positive current the percentage drops slowly during charging.

Finally my conclusion is that there must be an hardware error within the mainboard. This is supported that I used the S4 mini with this nightly for weeks without any problem.

Thanks to all but probably need to replace the device and buy a new one as it is not for daily use to externally charge and exchange the battery every time.
[Galaxy S 4 Mini Original Android Development] igor45:
I did read that and I thought it might have insulted you and took the chance that it wouldn't offend..

I did see that it was happening for months and I understand it's frustrating. FWIW I also experienced problems after agreeing to the OTA updates then realizing later that they were unstable versions (not having used CM since Kitkat and not ever using the CM OTA updates out of principle)

Excellent point you raise - I would say that one should HAVE TO manually download a Nightly or at least view some sort of disclaimer/warning if its going to be offered OTA. The way things used to be before Android became so popular. Example: I've used Ubuntu since v6 and used to be one could find great help for issues - now it's a sea of confused users and half answered half-asked questions with an even greater sea of confused resources available. At least with custom Roms the danger isnt as great of that happening completely though it tends to that direction directly proportional to the OS's popularity.

Again apologies for the seeming insult, and didnt mean to hijack your question with a soap-box...

Italics were placed more in the interest of being clear to those who may not know better. There're many more ppl jumping into things these days now that Android is so popular.
[Galaxy S 4 Mini Original Android Development] grot84:
Hi All,

I have a problem with one application (available form Play Store) after upgrading to new SNAPSHOT (20 Aug):

The app is crashing on start. I have checked it on other phones (S4 with AOSP 6.0.1) and it is working fine there.

Here is the app:

https://play.google.com/store/apps/details?id=pl.luxmed.pp&hl=pl

Here are the logs:

https://www.dropbox.com/s/e4fu3njzskiryxh/2016-09-12_19.07_LuxMed.zip?dl=0

I have tried clean data/wipe cashe/reinstall etc. nothing helps.

Please advise.

Thank you in advance.
[Galaxy S 4 Mini Original Android Development] Phenom2122:
[MENTION=942668]igor45[/MENTION] it's all good dude and apologies for taking it as an insult. I'm sure that once upon a time there was an option to only display stable or unstable updates? Or was that a different rom? Agreed fully. Not only is Android more popular but CM is the most popular custom rom of all and it would just make sense.

[MENTION=2477606]grot84[/MENTION] based on what something someone suggested to me before, try changing you DPi before using the app.

[MENTION=7548253]Migual12[/MENTION] I feel for you dude. Sad when the time finally arrives that your old trusty device starts to die.
[Galaxy S 4 Mini Original Android Development] umuturunc:
Yes, u r right. There was an option that allow you to select stable or nightly updates in old cm version
[Galaxy S 4 Mini Original Android Development] Migual12:
[MENTION=7548253]Migual12[/MENTION] I feel for you dude. Sad when the time finally arrives that your old trusty device starts to die.[/QUOTE]

At least, CM13 helped to extent the life of my S4 mini for quite a while as I could extend the 8GB Memory and improve performance without the stock bloadware. Thanks the developers for that. [emoji7]
[Galaxy S 4 Mini Original Android Development] huawei92:
CM14 test with kernel 2.9.14 remix there are no problems except video recording that doesn't work , while in the SD does not read the file manager root access... you can have theme chooser cm14?
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
Did you try another usb cable? Those cables are prone to develop resistance at the output side. (they are connected like the ethernet jack, by inserting jigsaw teeth into cable - no soldering) That resistance may not be itself current limiting that much, but internal charging algorithm may decide to lower the current to avoid heating on cable not to make the resistant spot worse. This is just a guess based on my some observations on charging current with different cables. The most stable and highest current cable is the one I soldered the output side.
[Galaxy S 4 Mini Original Android Development] Migual12:
Thank you, I already tried different cables, but I will doublecheck it again. The cables I tried worked with other smartphones without problems.

EDIT: Tried again three differend cables and two power supplies. The charging level degreases slowly independent of the configuration. Ampere App shows sometimes a current of over +300mA but it degreases rapidly to +130 mA. I find it strange that a positive current of 130mA degreases the charging level. It seems there is an Energy consumption due to a fault current. Thought i should try to charge with higher voltage but this would probably kill it. Maby I will try to use the phone as NAVI in the car if I find a way to directly power the phone from the car battery. Thanks.
[Galaxy S 4 Mini Original Android Development] DarkJoker360:
I m happy to be back guys :)
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
You are welcome. Increasing the voltage a bit may not kill but doesn't help at all, because the charger circuit manages the current with a linear regulator and you will only increase the power dissipated as heat.

I don't think that it is a circuit fault. One probability is the battery's bad condition. I remember that some battery applications reports that if it is in bad or good condition. Very probably they get this directly from OS without interpretion. If it is in bad condition, the charging algorithm may refuse to charge fast.

Also make sure that the battery and phone terminals are clean. If not, wipe them with alcohol.
[Galaxy S 4 Mini Original Android Development] grot84:
Changing DPI did not help. Still crash. Any other ideas?

Log:

https://www.dropbox.com/s/jw1uuezekk148v9/2016-09-14_19.03.Luxmed.zip?dl=0

Moreover, I have found another issue with WiFi - It is active but I cannot connect to any network. reboot helps for some time.

Logs:

https://www.dropbox.com/s/n8g5v56xk7cooin/2016-09-14_19.00.WiFi.zip?dl=0
[Galaxy S 4 Mini Original Android Development] shadyasker:
Is there any cm 14 test build for the curious Serrano3g users [emoji2]
[Galaxy S 4 Mini Original Android Development] arco68:
For those with echo problem in apps like Duo, can you flash the attached zip file in recovery, and test. NB only for 9195!

You also need to add the following to your build.prop:

use.voice.path.for.pcm.voip=true
[Galaxy S 4 Mini Original Android Development] _Matsiev_:
Edit updater-script and install 9195 build
[Galaxy S 4 Mini Original Android Development] shadyasker:
Are you sure have you tried it before ?
[Galaxy S 4 Mini Original Android Development] Dieexe:
Installed on i9190 and works pretty well, if anyone have this model and you want to test it just install any serranoltexx twrp (with rashr or another flash app) and then you'll be able to install any serranoltexx ROM, like this cm14, idk if mobile data or these things will work

screenshots!
[Galaxy S 4 Mini Original Android Development] milouk:
[MENTION=3044346]arco68[/MENTION] does the s4 mini have a built in FM transmitter?
[Galaxy S 4 Mini Original Android Development] huawei92:
this version does not have a lot of things is not as complete because it still apps are under development also lacks the theme chouser.... I look forward coming out of the first full night official to update by the time they are with cm14 unofficial
[Galaxy S 4 Mini Original Android Development] _Matsiev_:
Yes, i have tested many roms from 9195 and 9192
[Galaxy S 4 Mini Original Android Development] Whitest:
Thank you very much for your commitment to our S4 Mini - I'm testing adventurous- & curiously since yesterday & I really like it!

Although as you said it's still a little rough it works great considering it's a test version!

Only thing I've tested & found not to be working is infrared controls ;)

EDIT: [MENTION=3044346]arco68[/MENTION] I managed to build from sources without errors, dirty flashed my cm-14.0-20160916-UNOFFICIAL-serranoltexx.zip & now I was greeted with no WiFi & no SIM detected - at this early stage only clean flash possible?
[Galaxy S 4 Mini Original Android Development] arco68:
I've tried to get it to work before, but no success. So I don't think so. Or Samsung has disabled it in hardware.
[Galaxy S 4 Mini Original Android Development] arco68:
Anyone tested yet? Need some feedback whether it's working or not, so I can get the fixes into CM.
[Galaxy S 4 Mini Original Android Development] arco68:
I'll probably put up a new test build for both phones tomorrow.
[Galaxy S 4 Mini Original Android Development] shadyasker:
Thank you, I can't wait to test [emoji23]
[Galaxy S 4 Mini Original Android Development] arco68:
Here's new CM14 test builds. These are a little bit more complete, but there's still features missing, and some glitches here and there. Video recording still broken.

GT-I9190 (serrano3gxx): cm-14.0-20160917-UNOFFICIAL-serrano3gxx.zip

GT-I9195 (serranoltexx): cm-14.0-20160917-UNOFFICIAL-serranoltexx.zip

Enjoy!
[Galaxy S 4 Mini Original Android Development] huawei92:
zip file corrupted error CM14 lte :'(
[Galaxy S 4 Mini Original Android Development] Dieexe:
Happened to me, try to download with ADM (search on play store)
[Galaxy S 4 Mini Original Android Development] Whitest:
I downloaded with Chrome on my S4 Mini on previous CM14 test version - dirty flashed & everything works fine :D
[Galaxy S 4 Mini Original Android Development] huawei92:
Grazie arco68 sei grande!

---------- Post added at 08:30 PM ---------- Previous post was at 08:00 PM ----------

there a way to change the theme with a trebuchet?
[Galaxy S 4 Mini Original Android Development] arco68:
No, not yet.
[Galaxy S 4 Mini Original Android Development] DarkJoker360:
Guys, my s4 mini is dead and now I have a new phone, so Thanks to [MENTION=3044346]arco68[/MENTION] for his hard work, thsnks for all. R.I.P?

Inviato dal mio ALE-L21 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] huawei92:
you're doing a wonderful job you are great I think the best we've got CM14-

stai facendo un bellissimo lavoro sei grande penso che la migliore cm14 ce l'abbiamo noi
[Galaxy S 4 Mini Original Android Development] _Matsiev_:
New build has trouble with sd card access
[Galaxy S 4 Mini Original Android Development] Sushi1022:
Same here, along with a few spontaneous reboots. Reverting back to the previous build.
[Galaxy S 4 Mini Original Android Development] luisbraz:
You are talking about CM13 or the CM 14?

If it's CM13, the working nightly is then the 16?

Thanks.

---------- Post added at 10:37 AM ---------- Previous post was at 10:31 AM ----------

I'm going to update to the latest working nightly and will test this. Will report later.
[Galaxy S 4 Mini Original Android Development] Sushi1022:
The build not working properly is CM13. aicp_serranoltexx_mm-11.0-NIGHTLY-20160915
[Galaxy S 4 Mini Original Android Development] _Matsiev_:
CM14
[Galaxy S 4 Mini Original Android Development] luisbraz:
[MENTION=3044346]arco68[/MENTION]

Tested your voiptest zip file and everything is working well. I don't have echo and the other side either.

EDIT: forget to mention that I'm on 16 nightly and the test was performed in Google Duo.
[Galaxy S 4 Mini Original Android Development] KyeWalker:
[MENTION=3044346]arco68[/MENTION] can I request that the tests for cm14 be moved to a different dedicated thread to avoid confusion between ROMs. I can see this happening very soon and a lot of repetitive questions.

Thanks dude ;)
[Galaxy S 4 Mini Original Android Development] arco68:
Sweet! :)
[Galaxy S 4 Mini Original Android Development] csendre:
Just noticed this :) Did you end up making changes to the kernel as well?
[Galaxy S 4 Mini Original Android Development] arco68:
Yup. Patches on gerrit, if you want to test it on serranodsdd.
[Galaxy S 4 Mini Original Android Development] csendre:
I would love to but will have to wait until I am back from vacation unless you are willing to make a flashable zip
[Galaxy S 4 Mini Original Android Development] szerwony:
I have a problem on all builds since June/July. Android keeps killing apps such as Facebook Messenger or Spotify even when I am using it. Sometimes also Google Now launcher. Do anyone know how to repair it? It's really annoying.
[Galaxy S 4 Mini Original Android Development] sboida1:
[MENTION=3044346]arco68[/MENTION] thank you for continuing to maintain the S4 mini bro, as per ur request I have been testing the latest cm14 ROM on this post, like others have mentioned, apps like Music (only seeing songs on internal memory), ES file explorer, Xplore can't access the SD card, only in-built is able to access.....also I have noted the status bar settings don't work, except for clock style, Battery Status setting going down to brightness control do nothing....,. Status icons setting causes a force close. Have also noticed that some sideloaded apps seem to crash