yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] cdurex:
The update went awesome! :highfive:

First boot was ok for me! Stayed in the CM logo while booting, and yeah it took a while! But after that everything is awesome!!

Best ROM ever, as always!! :D

Thanks to CM team for making this possible!!

:good:
[Galaxy S 4 Mini Original Android Development] Th3Sh3r1ff:
Problem is still here.

No SD card detected in 20160516 nightly. [emoji15]
[Galaxy S 4 Mini Original Android Development] vmbr007:
:crying: Can I make a downgrade for a last week version?
[Galaxy S 4 Mini Original Android Development] Tigerman82:
Yeah, I'm getting this too. Updated from 0511 (everything was fine) to 0516. Cannot see the external SD via any file explorer and apps like Snap Camera which I have set to save files to the external SD crash when I try to use them. In TWRP I can of course see the external SD and, just to be sure, I pulled the memory card out, connected it to my Mac and checked that everything was still there.

Hopefully this will be fixed soon.
[Galaxy S 4 Mini Original Android Development] :
[MENTION=3044346]arco68[/MENTION], the media server and audioflinger is dying here.

Built cm13 from source today and I cannot make any calls.

Made a fresh install, no old cm was left.

I can see a lot of errors like:

05-17 11:18:46.686 650 1957 W AudioSystem: AudioFlinger server died!
05-17 11:18:46.686 650 1973 W AudioSystem: AudioPolicyService server died!
05-17 11:18:46.687 650 1265 E AudioService: Media server died.

Also the screen shows some strange things when trying to call somebody.

Any idea what is wrong here?

Find the logcat output attached.

Regards

Thomson

P.S: Here's the screen shot when trying to call:
[Galaxy S 4 Mini Original Android Development] Th3Sh3r1ff:
Still no SD card in 20160518.

Thinking of switching back to snapshot...
[Galaxy S 4 Mini Original Android Development] McClane13:
I'm on 20160516 nightly for 20+ hours,

and I've got none of the problems you're facing, until now at least.

I've been installing every single nightly from 20160501 on and the bugs have been negligible.

SD card in particular has been working just fine since the beginning

(formatted in exfat as portable, if that's a crucial factor).

Still, makes me think twice before updating to today's nightly.

By the way,

that's supposed to be 20160517, right?

Oh, and if anyone is interested

New BaseBand XXUCPD1
[Galaxy S 4 Mini Original Android Development] gonzalomorenorovetto:
I have another i9195 with 0509 nightly, and the same sdcard is working fine as portable on that phone. If i put the card back in the phone with 0517 nothing happens at first, but after a while a message shows the card is corrupted. Still fails to format it as portable or as internal.

edit: Updated the other phone to 20160517 and now I can't see the SDcard in that phone too.

I will try reverting one of the phones to 20160509
[Galaxy S 4 Mini Original Android Development] arco68:
Have no audio issues here, so I don't know why it's crashing for you.

The weird string thing I have seen reported on other devices, usually on unofficial builds. Try completely cleaning the OUT folder before building.
[Galaxy S 4 Mini Original Android Development] axiel7:
Some google apps (play services, play music, chrome, google search, gmail) give me fc when i open it, anyone else had/have this problem?

Enviado desde mi GT-I9195 mediante Tapatalk
[Galaxy S 4 Mini Original Android Development] Th3Sh3r1ff:
Yes, 20160517, I do NOT live in the future!

Decided to switch back from nightlies to snapshot.

CM is great and nightlies have almost no blocking bugs, but once in a while, it happens and it takes some time for the developers to fix it (even though they are travelling at the speed of light compared to most developpers I know).

So I guess the snapshot path is more for me...
[Galaxy S 4 Mini Original Android Development] androlev:
20160517 broke my sd card too (formatted as internal). Can't find it. All apps crash, since it's internal...

20160512 was fine. Reverting from 20160517 to 20160512 leads to boot loop. Trying to recover the encryption keys and hope that the sdcard didn't get formatted...
[Galaxy S 4 Mini Original Android Development] :
Guys, I've got a nasty problem which keeps coming back since Android 4.4. Currently I'm on the latest CM 13 Snapshot.

The problem is the screen wakes up periodically when the phone is locked. It wakes up, times out, wakes up, times out and so on.... and by this it's ruining my battery life. I really can't figure out what causes it. I tried disabling WiFi, set it to Airplane mode, or do both but nothing stops it. Luckily it goes away by itself after like 10 mins but it occurs for sure two times a day which is not acceptable. Even with this app called Wakelock Detector I couldn't figure it out and since it occurs even with Phone and Wireless connections disabled, it can't be Facebook or some messaging app, right?

I read on the Internet and as it seems this bug affects a lot of devices and there is no general solution which makes the troubleshooting difficult. Most times the suggestion was to update Android to 5.0. But I have had this issue now on EVERY Android version from 4.4 factory through CM 12 to CM 13.

I really don't know what I should do now. Is there anybody experiencing the same?
[Galaxy S 4 Mini Original Android Development] androlev:
SDcard issue is a kernel issue. The device is absent in /dev/block.

Kernel messages contain repeating blocks of this:

and later this
[Galaxy S 4 Mini Original Android Development] huawei92:
audio is good uninstalling v4a.. problem the SD does not ask for the integration of internal memory night 17/05
[Galaxy S 4 Mini Original Android Development] Foo Bar:
SDCard not mounted

Also have SDCard problem (build 16/05 & 18/05).

My SanDisk Ultra 16 GB is not seen whereas my hold Samsung 16 GB Class 6 is fully recognized.

I've tried to format my SanDisk with either my PC or TWRP (vFAT, F2FS, Ext4): never mounted.

Why some are detected and other not ? :(

Anyway, than for that great ROM :good:
[Galaxy S 4 Mini Original Android Development] :
Viper4Android works fine with the new audioHAL on my phone. Only problem I have is that the music playback starts to stutter and occasionally stops when the screen is off. With the screen on, playback is okay. It looks as if the kernel/system tries to put something to sleep which it shouldn't and never has done before. I've tried several things with Kernel Adiutor, but to no avail (standard kernel). Does anyone experience the same issue?
[Galaxy S 4 Mini Original Android Development] McClane13:
SD Card problems solved apparently !

Regarding the SD Card problems observed in the latest nightlies:

According to csendre, dev of the AOKP ROM (which is CM based)

the problem is now solved.

But I can't seem to spot the kernel code modification in the changelog.

ooppss, apparently here they are (thanks @androlev)

In short, based on the latest reports, it wouldn't be recommended to update to the latest nightlies,

but has anyone actually updated to 20160519 nightly to confirm the sd card bug is solved?

Well, according to @Tigerman82 and @androlev

the issue is resolved in the 20160519 nightly

Thanks in advance.

PS: btw, here's a potential workaround: flash the pre-20160513 stock kernel (post)

well, apparently there's no need after all.
[Galaxy S 4 Mini Original Android Development] Tigerman82:
I can confirm that the bug is (or at least seems to be) solved. I flashed a Nightly this week and got the extSD bug. Now that I flashed the 0519 Nightly, I'm once again able to see the extSD. :good::good::good::good::good:
[Galaxy S 4 Mini Original Android Development] androlev:
Todays (19) build fixed it for me, thanks Arne!

the commits aren't visible on gerrit, but if you go directly to github you'll see the "mmc fixups" commit in the kernel repo.
[Galaxy S 4 Mini Original Android Development] McClane13:
And one more question if I may.

So far, I've installed the mini package of OpenGapps,

and I'm thinking to install the micro package from now on.

Having the mini package currently installed, can I just flash the micro with the next cm nightly from within twrp

(followed by dalvik/art cache & cache wipes afterwards),

or is a full wipe (restore to defaults) necessary because I'm downgrading from a richer package to a lighter one,

and so there's a chance dirty data from uninstalled apps to be left behind?

Should I uninstall the extra apps in the mini package beforehand?

Any advice would be really helpful.

Thanks again.
[Galaxy S 4 Mini Original Android Development] chrisled:
My suggestion would be, to do a backup of the data you wish to keep to "microSDcard", prior to a Full Wipe. Now that the CM can "See" the internal/external SD card as it was, prior to 20160514 update, ( i.e. Normally ), backups to SD card will be okay.

Then, once you have done a full wipe, install CM and openGapps.

Otherwise issues may arise and certain apps may give errors.

Hope this helps.
[Galaxy S 4 Mini Original Android Development] Childe89:
Hello, I noticed in latest changelog "liblights: Add BLN support" - any idea how to activate on our device? BLN control app still gives "not supported" message
[Galaxy S 4 Mini Original Android Development] supachris:
Works also on snapshot and is kernel related. You can enable it with ns tools.
[Galaxy S 4 Mini Original Android Development] Childe89:
Great thanks for info :) and what do you mean by "ns tools" ? Didn´t heard before :) Can you provide little guide, or link to some? :)
[Galaxy S 4 Mini Original Android Development] milouk:
NS tools is an app from play store...download it an first think you will see is bln ;)
[Galaxy S 4 Mini Original Android Development] Foo Bar:
My SanDisk Card is recognized on build 19/05

Thanks [MENTION=7478875]McClane13[/MENTION] for point out new build was now correctly handling SDCard.
[Galaxy S 4 Mini Original Android Development] vampires.remembered:
I confirm SDCard working on cm-13.0-20160519-NIGHTLY-serranoltexx.zip. Yei!
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
Just tried this ROM with f2fs. It works so well, the phone is so much smoother. I recommend everyone to try it
[Galaxy S 4 Mini Original Android Development] denyo81:
What is f2fs dude?
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
It's a file system ;) the default is ext4, but f2fs has some advantages. Google it for more info ;) cm13 is compatible with it from source so you just have to format system/cache/data into f2fs (TWRP) and flash the ROM (you will loose any data. I don't recommend using full backups, it might not boot after, just save your data)
[Galaxy S 4 Mini Original Android Development] crisdotti:
How to use Usb otg in cyanogenmod 13?
[Galaxy S 4 Mini Original Android Development] JimmyRay:
Do we need to use a custom kernel for f2fs?

How are you formatting the partitions, by the way?

Cheers!
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
No, CM13 is compatible out of the box with F2FS. For formatting, in TWRP go to Wipe, Advanced Wipe, select just one partition (system/cache/data) and hit Repair or Change File System. Then select Change File System and choose F2FS. Do this for the three partitions (system/cache/data). Please note that if you have adopted storage, you will loose access to the files inside the SDcard (I'm not sure if it formats the sdcard tho, but I know I could not access any files in it. I ended up formatting it in my computer) so keep all your files including Titanium Backups in your computer!

After formating I just used the cable to transfer CM13 and Gapps to the device (you can also put them in your sdcard if you formated it in your desktop like me) and installed normally. Oh, and I also wiped Dalvik and Cache after just to be sure. After that just reboot and set up your device ;)

I used this recovery: http://xdaforums.com/showthread.php?t=2678420

I really don't recommend trying using TWRP backups after formatting (even changing the wiping method in the settings), specially if you have adopted storage. I think you'll just loose more time than actually setting the phone up and restoring backups if in the end it doesn't work.
[Galaxy S 4 Mini Original Android Development] supachris:
Installing CM13 Snapshot results in turning back to ext4 for system and changing wipe methode to only use rm results in no booting...
[Galaxy S 4 Mini Original Android Development] Keon91:
I only formated my cache and data partition to f2fs since it makes no sense to me to format the system partition to f2fs because it is read-only and ext4 is faster for reading data than f2fs.

But it works great!

I used the same recovery, the nightly from today and the micro build opengapps from here : http://opengapps.org/?api=6.0&variant=micro
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
The only way TWRP is turning back to ext4 is because you are trying to restore a backup of ext4 without that thingy checked in the settings about using rm. Installing the snapshot will NOT change anything!

---------- Post added at 12:48 PM ---------- Previous post was at 12:48 PM ----------

Probably you are right, maybe I'll switch system back to ext4 ;)
[Galaxy S 4 Mini Original Android Development] Guner24:
How do I know what s4 mini variant I have?
[Galaxy S 4 Mini Original Android Development] :
Guys really nobody?
[Galaxy S 4 Mini Original Android Development] toppits:
[MENTION=4347926]mcpossity[/MENTION]

I guess just nobody had this issue, so they couldn't help you on this one. If it's not the ROM (since not everybody has it, I guess it's not) and it's not your Hardware (which I hope it's not) it's probably an App or a Setting (just trying to narrow down the cause..). So did you try if your problem occurs after a clean Flash, all wiped fresh ROM/gapps install, without Setting up your apps and settings?

Since my gfs I9195 is currently a bit messed up, I'm thinking about getting her CM13 and when I'm already at it, I'll also try the F2FS tips, hope it's not the Hardware but only the Software that's messed up (on) her phone :/ Well we'll see next week. I read some good tips here and I think I'll go with the latest Snapshot + opengapps +F2FS. Will give Feedback. Thx for all the helpful Posts here, thx for sharing :)
[Galaxy S 4 Mini Original Android Development] iordache_srn:
wiped cache,data,sistem-format all 3 to f2fs -flashed 20160521 nightly+opengapps nano(smallest around 80-90 mb).flashed ok the nightly but the opengapps with error (error 70)-something regarding no space available

question :any ideea why?

when i format sistem in ext4 it frees up all the space around 1500 mb ,when format in f2fs just around 1100 mb

i saw your last posts and i ve formated cache and data to f2fs and sistem to ext4...all ok-flashed all ok
[Galaxy S 4 Mini Original Android Development] :
Go to settings --> system info --> model.
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
I got that exact same error message when installing gapps. I simply rebooted recovery and then it installed fine.
[Galaxy S 4 Mini Original Android Development] denyo81:
Guys, try this gapps. It's optimized for our devices. Working fantastic with f2fs!

http://xdaforums.com/showthread.php?t=3276606
[Galaxy S 4 Mini Original Android Development] JimmyRay:
So what's the consensus?

Leave system as ext4, but data and cache as f2fs?

Can we change just cache to f2fs (thus preventing the need to reinstall the rom) and still see some benefits?
[Galaxy S 4 Mini Original Android Development] filip555:
System, data and cache are formated as f2fs on my i9195, installed cm13 with open gapps pico, no problems at all.
[Galaxy S 4 Mini Original Android Development] gamer1182:
No new Gello browser for us? :/
[Galaxy S 4 Mini Original Android Development] iordache_srn:
i did a restart because the sound in facebook messenger chat werent,they returned after restart but now the wallpaper from lockscreen is missing...

anyone else has this problem?

edit:after a second restart the lockscreen wallpaper returned ...
[Galaxy S 4 Mini Original Android Development] paulyglocke:
Phone reboots while calling

Hi guys,

I am using a I9195 with cm-13.0-20160521-NIGHTLY-serranoltexx.zip, whenever I try to make a call the phone reboots, everything else works fine, I have also tried prior releases and this also happens, the google phone app also refuses to make a call, but it doesnt seem to reboot the phone, has anyone else had issues with this happening?

Paul.
[Galaxy S 4 Mini Original Android Development] powwow12:
What are the supposed benefits? Quicker?
[Galaxy S 4 Mini Original Android Development] :
Yeah, I had actually made a full wipe every time I switched a major Android version, e.g. from 4.4 to 5 to 6, which had no effect. I never restore from backup, but that didn't change anything either. New battery had also no effect. I think it's something with the software that's making problems...
[Galaxy S 4 Mini Original Android Development] huawei92:
Night top 22/05 for me and best of all and stable in all and the battery life and greatly increased speed and improved video and audio much better than snapshout
[Galaxy S 4 Mini Original Android Development] vmoreno94:
Want to test

Hello, could anyone tell me which bugs this rom has?
[Galaxy S 4 Mini Original Android Development] supachris:
I have an issue with Bluetooth sound volume. Every time I connect to my car stereo, the volume is decreased to a level of 70% or so...can this be changed somewhere?
[Galaxy S 4 Mini Original Android Development] chrischa:
if you are refering to this change you may have also red this change has the topic GT-I9100
[Galaxy S 4 Mini Original Android Development] :
Earlier in this thread Arco68 mentioned he implemented BLN-support in the CM-kernel for the S4 Mini. I use Performance Control to activate BLN. BLN works okay on my I9195.

---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------

Problem solved at least with nightly 22-5.
[Galaxy S 4 Mini Original Android Development] dwfak:
Same problem here.
[Galaxy S 4 Mini Original Android Development] chrischa:
Sounds you are using BLN. I use Ambient Notifications, but i would prefer bln, if it works correctly. Last time i used BLN (arround march) there was the following issue: Softkeys sometimes not responding after BLN event.

Is this issue still present or can you confirm its working now? :)
[Galaxy S 4 Mini Original Android Development] :
I had the softkey-issue as well, which is why I stopped using BLN a while ago. Since about a week now I'm using BLN again, no issues so far.
[Galaxy S 4 Mini Original Android Development] chrischa:
you mentioned an application called performance control, can you provide me a link please :)
[Galaxy S 4 Mini Original Android Development] :
You can find Performance Control here: http://xdaforums.com/showthread.php?t=2401988. You'll need Busybox though. I use BusyBox Pro by Stericson, you can look it up in the Play Store. Be sure to use 'smart install' when installing BusyBox Pro, so it won't interfere with CM's Toybox.
[Galaxy S 4 Mini Original Android Development] Childe89:
Earlier in this topis users recommended NSTools, which can enable BLN too, and works with toybox - no need to install busybox. :) Link to google play - https://play.google.com/store/apps/details?id=mobi.cyann.nstools

I´m using it since, and no problems so far :)
[Galaxy S 4 Mini Original Android Development] chrischa:
i already tried this method (in march). but this gave me the error of not-responding softkeys
[Galaxy S 4 Mini Original Android Development] malaga82:
I installed last nightly from "scratch" with mini gapps.

Everything fine, but i can't enable BLN, i tried BLN but it says "This kernel does not support BLN".

Which kernel did you use?

Thanks
[Galaxy S 4 Mini Original Android Development] supachris:
I get this Message too, but it works. Use NSTools, BLN Control is not working.
[Galaxy S 4 Mini Original Android Development] malaga82:
Thanks.

i was also using ambient display that suppress BLN.

Can you confirm me that it's constant led on and not flashing?
[Galaxy S 4 Mini Original Android Development] supachris:
Blinking is not supported by the kernel. NSTools only allow to activate static BLN. I did not try ambient light.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Using nstools, BLN works but get the soft key not responding problem randomly.
[Galaxy S 4 Mini Original Android Development] :
With Performance Control I haven't had the soft key-issue so far. Maybe it's down to Toybox in conjunction with the new CM-kernel? BLN is working just fine on my phone with Performance Control/BusyBox Pro smart install.
[Galaxy S 4 Mini Original Android Development] supachris:
Since CM13 I never have had the not responding button issue. In CM12.1 it was very often. I use snapshot with CM kernel.
[Galaxy S 4 Mini Original Android Development] dwfak:
Hello will be the problem with calling ( when you want call someone and phone restarts) repaired ? Because it is really needed. And when ? . Thanks.
[Galaxy S 4 Mini Original Android Development] McClane13:
@ paulyglocke & @dwfak

May I ask: what baseband and ROM are you using?

If using Stock ROM you could update to the latest ROM available here http://www.sammobile.com/firmwares/database/GT-I9195/

The latest ROM and baseband version is I9195XXUCPD1 updated just a few days ago (http://www.sammobile.com/firmwares/download/71810/I9195XXUCPD1_I9195PHECPD1_PHE/)

(XX is for Europe, but I believe users have reported it working for other areas such as Australia as well, depends on the channels your carrier is using)

If I recall correctly, although I'm not 100% certain, I have tried in the past updating from an older Stock ROM to a newer Stock ROM via Odin (without deleting data/factory reset) with success,

but do take a full backup first and proceed with extreme caution just in case, and of course YMMV!

If using third party ROM such as CM, consider updating just the baseband via Odin

You could check here http://xdaforums.com/showpost.php?p=66892288&postcount=971

You can get all modems from @redjamesg's collection here https://drive.google.com/folderview?id=0BzXmaKb7wuKUXzdwZDRaTVZuenM&usp=sharing

However, I haven't seen many reports of rebooting during calls, so if it's not the Rom or the Baseband,

maybe it's hardware related...

Anyway, hope it helps.

---------- Post added at 03:18 ---------- Previous post was at 02:44 ----------

Is BLN without any party tools feasible?

Are there any plans to expose that capability through a toggle in the settings perhaps?

If it is already implemented in the kernel, that shouldn't be much work, right?

Any info on that?

Thanks in advance.

---------- Post added at 03:22 ---------- Previous post was at 03:18 ----------

And one final question:

Is there any way to force the default download/ save location (for browsers. camera, music, videos etc) to be the SD Card (ext4 formatted as portable)

and not the internal storage?

Or is that a MM limitation?

Thanks in advance.
[Galaxy S 4 Mini Original Android Development] IronRoo:
I GUESS you could edit the Bluetooth or media player part of the file mentioned in the following post ..... but increase the value instead of lowering it (maybe set it back to 1:1) .......

http://xdaforums.com/showpost.php?p=66023445&postcount=968

(Note: I haven't a clue if Arco fixed the high volume in calls by tweaking these settings or some other method or if bluetooth/media player settings was also altered, so you'd have to take a chance ....... & do it for every new flash unless it's incorporated into a nightly)

---------- Post added at 05:05 PM ---------- Previous post was at 04:45 PM ----------

Not without using a 3rd party app. It's only possible via the settings in the individual apps that support external storage like the camera app, AFAIK.
[Galaxy S 4 Mini Original Android Development] Childe89:
This method don´t work anymore, since new audio HAL has been implemented, new path explained in this post: http://xdaforums.com/showpost.php?p=66868331&postcount=1399

True, that would be nice :)
[Galaxy S 4 Mini Original Android Development] KyeWalker:
No snapshot this month??