yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] heiitorxd:
Boot

I got message when I power on my I-9195

"set warranty by kerner"

How can I fix it?
[Galaxy S 4 Mini Original Android Development] M1chiel:
By reinstalling Samsung's own software.
[Galaxy S 4 Mini Original Android Development] Mascarponi:
This is because you tripped KNOX, by rooting your device or installing a custom ROM..

Try 'traingle away', might do the trick.
[Galaxy S 4 Mini Original Android Development] tchavei:
I have an issue for some time now and it subsists through several nightlies. The volume of the person on the other side of a call is very very low even on max volume. When I use Bluetooth or the internal speaker, I can hear the caller Chrystal clear and loud. It's just in normal mode that I barely can hear the caller.

I have another I9195 and it has the exact same issue on cm13 so I think I can exclude a hardware problem. Am I the only one experiencing this? Is there a fix?

Thanks.

Tony

Enviado do meu GT-I9195 através de Tapatalk
[Galaxy S 4 Mini Original Android Development] IronRoo:
My extSD has the same xxxx-xxxx name, which shows on some apps but has not had any problem with using it to store data. I used to use OpenCamera on 5.1.1 so just reinstalled it, and it has same issue as you. But then I remembered there is a work around, go to "Settings/More camera controls/"Use Storage Access Framework" Now it works on my phone.
[Galaxy S 4 Mini Original Android Development] Mascarponi:
Thanks man, that did the trick!

I was almost giving this a try; http://xdaforums.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263

Don't know if that would fix it, but seems that there are more workarounds to force writing on ext sd-cards..
[Galaxy S 4 Mini Original Android Development] misscandy:
There is a way to have cm13, root, xposed and pokemon go?

I read a lot of tutorials but i don't undestood if i have to give up on something (like root or xposed).

Can you guys suggest me something? I love this rom, it's the best thing happened to my phone (really) but I like pokemon go too
[Galaxy S 4 Mini Original Android Development] IronRoo:
Mine is good, in fact I would like to be able to turn it down a bit lower! (though my nightly is over a week old, will update Sun probably)
[Galaxy S 4 Mini Original Android Development] tchavei:
I just cleaned my speaker with a nylon brush and changed all rx4 values in the sound file to 84 and it's working great now :)

Unfortunately I can't say for sure what fixed it but I believe it was the brush [emoji14]

Thx for your info.

Tony

Enviado do meu GT-I9195 através de Tapatalk
[Galaxy S 4 Mini Original Android Development] Daredevil 720:
Hey guys, sorry for being slightly offtopic.

My battery has been acting weird the last couple of years but lately it's become really really bad. Like, shutting off 2 hours after being unplugged from the charger while reading 60-80%. I've been using this phone for 3 years so I think it's the battery and not something CM-related.

They only battery I can find online in my country is the EB-B500BE. Right before ordering it I read on the shop's description that it's for the i9190 and that it's not compatible with the i9195. Does this make any sense? Can someone tell me for certain the the two phones share identical batteries?
[Galaxy S 4 Mini Original Android Development] Mascarponi:
Just installed Marshmallow SD Fix v2.0 to grant apps permission to write on ext sd-card. For some apps it works, but for some other apps still doesn't. I used to use Websharing Lite to transfer files from my PC to my ext sd-card via WIFI. However in Android 6.0 my ext sd-card seems not to be found in this app. Is there an (wifi)transfer app that works like this and can read/write to external sd-card over wifi ?
[Galaxy S 4 Mini Original Android Development] arco68:
The 9195 batteries have the NFC chip in them. You can probably use the 9190 battery, but will loose NFC functionality.
[Galaxy S 4 Mini Original Android Development] Daredevil 720:
Never really used the NFC on my device nor will I ever use it from what I can tell. So aside from that it should work fine in the 9195. Thanks!
[Galaxy S 4 Mini Original Android Development] milouk:
They Do NOT share the same battery... The LTE's battery has 4 poles while the 3G's 3 poles
[Galaxy S 4 Mini Original Android Development] Daredevil 720:
Will it work on the LTE device though, even without NFC?

I mean there's a possibility if that pole is NFC related.
[Galaxy S 4 Mini Original Android Development] jimenes:
I bought a B500BE battery (based on the original one with came with the phone, 4 poles, 9195). But it didn't fit, so I had to cut the extremes. It has been working since then, for 2 months with 0 problems.
[Galaxy S 4 Mini Original Android Development] milouk:
Both batteries have NFC (i changed battery a week ago and they accidentaly gave me the 3g one thats why i know.. Also both had NFC capabilities)
[Galaxy S 4 Mini Original Android Development] IronRoo:
Anyone attempting this must be 100% certain the protective seal of the actual cell inside is not damaged/weakened/punctured in any way and you only cut the outer plastic case part, else this is a potential fume/fire risk.
[Galaxy S 4 Mini Original Android Development] jimenes:
Very important advice (except for the Note 7 case, whose battery would blow up altought you had taken all those cares). I made sure of that by removing the top plastic (which was so easy to remove btw) and then proceed to cut the extremes (no more than 2mm in both sides, I think). It's better, anyway, to make sure the one you're buying (for less than 4€ in my case) will fit perfectly w/out any modifications.
[Galaxy S 4 Mini Original Android Development] Childe89:
Two latest nightlies cause camera bug for me - can´t switch some options in default camera app, causing a crash and app close. I think it´s because options are kind of "misaligned" for example - choosing 8MP switches on 6MP, choosing 1MP switches on VGA, and switching last option - VGA - force closes app, probably because there is no mapped option... big problem for "ON and OFF" switches...
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
Stucked at 6 MP :D

Also toybox doesn't work on 161028 rom.
[Galaxy S 4 Mini Original Android Development] KnightofTheHell:
Thanks for porting
[Galaxy S 4 Mini Original Android Development] Mascarponi:
Is there a way to have these shortcuts (Wifi, bluetooth, sound, etc) in the statusbar as were possible in CM11 ?
[Galaxy S 4 Mini Original Android Development] 4inch4life:
CM13 snapshot

I'm sorry if I will ask bothering newbie questions, but there is no alternative q/a and this thread, while long, doesn't seem kind on nightly!

I love the s4 mini, it is the only decent android phone with a 4,3" screen. I use it for work and fun, and I would not change it for anything else. It's so absurd that there is not even ONE phone after 3 years in this segment, an iPhoneSE alternative if you like.

However I'm accustomed to Touchwiz for the everyday stuff, so I want something as reliable. I'm asking about the last nightly. Be nice, I've read hundreds of old comments about problems with stuff, so I want to know if they are for real or just bugs from the past:

-connections. Is everything (4g, Bletooth devices, wifi, gps, nfc) fully operational? Will screen mirroring work as good or better :) than TW? HD voice VolLTE?

-camera. Does samsung have proprietary stuff over the app for making pics better or faster than open source third party? is there an option to disable photo shutter sound? Really annoying

-is this the preferred version, since cm14 is not official harware compatible and cm12 is plain old?

-Is there something I will loose, apart from slugginess and random crashes :D ?

Thanks and again sorry if they are totally noob questions!
[Galaxy S 4 Mini Original Android Development] Dieexe:
Everything is working right now, if you want full stability use latest Snapshot and Pico GAPPS, you'll lose just a little bit of camera quality and some features of TouchWiz, nothing crazy, and you'll win on everything else.

Try it, you will not be disappointed
[Galaxy S 4 Mini Original Android Development] Snofru1:
Unfortunately not, it´s a pity.
[Galaxy S 4 Mini Original Android Development] Childe89:
Camera bug in default camera app still persisting in latest nightly, please fix asap :) I´m using open camera in meantime, but I prefer stock :)
[Galaxy S 4 Mini Original Android Development] luisbraz:
Yes. Go to system - media - ui, and delete the camera and video sound files. You're fine till next update, then do the same! :)
[Galaxy S 4 Mini Original Android Development] JimmyRay:
Sluggish cellular data performance with 20161028 nightly?

Argh!

False alarm chaps, I should have known better than to doubt [MENTION=3044346]arco68[/MENTION]'s skills.

The issue is due to exceeding my carrier's monthly 2GB data cap, which automatically reduces my bandwidth 128kbps. Everything should be back to normal again tomorrow (1st November).

Checking my usage dashboard on the myDocomo website, I used just 0.9 GB last month, so I'm not sure why my usage has suddenly doubled!?

Again, my apologies for the false alarm.

Hello chaps,

I updated my I9195 to the latest nightly yesterday, as I have been doing regularly each month (usually at the end of the month). The S4 Mini was previously running the 20160930 build (without any issues) and updated to the 20161028 build.

Using the phone yesterday and today, it seemed that cellular data performance felt very sluggish, waiting for sites that I visit regularly to load, and images appearing one-by-one. One site even timed-out at the login stage. I switched to wifi and the sites loaded quickly, as normal, then back to cellular and the sluggishness returned. I also tried restarting the phone, but performance did not appear to change.

I'm currently in the process of updating to the 20161030 build, and hope that this restores the same cellular data performance I was enjoying with the 20160930 build.

A month is obviously quite a long time in the CM development world, but I wonder if anyone else has experienced reduced network performance with recent builds?

Cheers!

Update: No improvement with the 20161030 build, unfortunately...
[Galaxy S 4 Mini Original Android Development] Hash-b:
No Stereo Sound

Hi ! I have lost stereo sound on headphones after installing CM13 (first custom ROM on my device). Please help how to fix!
[Galaxy S 4 Mini Original Android Development] powwow12:
Parsing Error still persists on 2/11 nightly. I wonder what could have triggered this ****ery. There were no interesting commits on these last builds
[Galaxy S 4 Mini Original Android Development] iskefiyeli:
how to send file with wifi direct?
[Galaxy S 4 Mini Original Android Development] arco68:
I get that error if the file is corrupted or incomplete.
[Galaxy S 4 Mini Original Android Development] Daredevil 720:
Help guys!

I've been using a nightly from late September, haven't updated since then, everything worked fine.

Suddenly I tried to open Messenger and it refused to open. I force-stopped it and tried to open it again. I then got endless FC's for Trebuchet and Messenger so I tried to do a Soft Reboot from the power menu. CM kept loading but it wouldn't boot so I held down the power button to turn off the phone and try a fresh boot.

Now the phone freezes on the Samsung logo with the yellow "kernel ..." label and it won't boot into TWRP (v3.0.2.1) either as it freezes on the TWRP logo too. I went into download mode and tried reflashing TWRP through Odin but the process just hangs here:

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

Is my phone dead beyond recovery? I need to know if I have to buy a new phone.
[Galaxy S 4 Mini Original Android Development] McClane13:
No offense @arco68

but as I have reported several times the parsing error happens on solid downloads too.

In fact I have double-triple-multiple-checked the hashes of the downloads, and still the error persists.

Tested with multiple file managers, with multiple .apks, cleaned dalvik/cache from TWRP several times, tried about 10 different nightlies,

cleaned data/cache of multiple apps from within android (eg CMFileManager etc) but still the same error.

I posted several times on this thread but nobody took me seriously/cared enough to investigate, as you can see:

http://xdaforums.com/show...postcount=2288

I checked the changelogs for about two weeks back and I couldn't find any commit suspicious enough,

and the only semi-acceptable solution (a workaround really) suggested was a full wipe - clean install.

So, since I couldn't stand the neglect, I desperately needed the functionality and I had to do a clean install anyway,

I went ahead and installed cm14 right away, and thankfully the .apks install just fine (so far at least).

Just my 2c.

Thanks for the great ROMs btw. Keep up the great work.
[Galaxy S 4 Mini Original Android Development] :
So the lesson is:

If you have strange issues that nobody else seems to have and you have

1. Dirty flashed an update/not wiped data before flashing

2. Use custom kernel/xposed/system mods

then a clean flash will more than likely fix your issues.

BTW doing a clean flash is recommended(always), not a "work-around"
[Galaxy S 4 Mini Original Android Development] McClane13:
What are you talking about?

No offense, but seems that you misunderstood me mate.

really? nobody else?

http://xdaforums.com/galaxy-s4-mini...-0-s4-mini-t3276141/post69293625#post69293625

We are talking about an update from a cm13 nightly to a next cm13 nightly, not a major upgrade or a bump in a version.

So yay a dirty flash, but on an update, not upgrade. A clean install is mandatory from another ROM or from stock, but not from one nightly to another.

I always clean dalvik/art cache after the updates, but you will find no one doing a data wipe after every update. Who would do any update ever if that was the only way?

When do you get to actually *use* your phone, when you are setting up your apps and settings every other day?

No restore from dirty titanium backup either.

none used whatsoever. none.

Again, yay a dirty flash, but on an update, not upgrade. A clean install is mandatory from another ROM or from stock, but not from one nightly to another.

I always clean dalvik/art cache after the updates, but you will find no one doing a data wipe after every update. Who would do any update at all, ever if that was the only way?

When do you get to actually *use* your phone, when you are setting up your apps and settings every other day?

And, if you read the posts I linked to, the problem started to appear on a nightly around 14/10,

before that I was using cm13 nightlies for about 4 months without many issues, and specifically without the parsing error while installing apks.

The last clean installation I did was on August, and since then I've been updating to the latest nightly once - twice a week, with no clean installation/data wipes

and I've been installing apks several times a day (a project I'm working on) with no problems, until around the 14/10 nightly.

After the 14/10 nightly, with no modification on the system, no xposed, no change on the phone config whatsoever,

suddenly the apks, any apks, not corrupted, not incomplete, any apks, refused to be parsed correctly.

So a crucial (for me) functionality just vanished from one day to the other, and I'm to blame for not doing a clean install? yay right.

And under those circumstances, clean install *is* a work-around, you don't deal with the problem, you wipe it clean (literally).

Thanks for the troubleshooting, mate.

I wrote about it in this thread, but no one cared.

It seems that it is not manifested after a clean installation, that's why arco didn't pay much attention, I guess. but still is a major issue in my book.

So, my suggestion, get your facts straight before insulting my intelligence.

And again, thanks for your valuable contribution, just dismissing the facts and playing smart.
[Galaxy S 4 Mini Original Android Development] luisbraz:
As I told before, my g pad suddenly start to have the parse error, so probably is something related to some Google app that was updated.

And also had that error in s4 mini. The clean flash solved the problem, but didn't try again to install another apk, so I can't tell if it's back again.
[Galaxy S 4 Mini Original Android Development] :
My apologies, I stand corrected. But because only a few users have had this issue means that the solution is to do a clean flash. Nobody is going to spend significant time on an issue that affects only the few(and on multiple devices which means it is not a specific device issue; therefore you would be better off submitting a bug report directly to CM Jira)

If you dirty flash, you may run into all sorts of issues eventually. I'm not saying you shouldn't dirty flash. I'm saying if you do, expect to have problems at some point. Then do a clean flash. This is one such instance

Please accept my apologies. It was not my intention to insult your intelligence or upset you. It just seemed an obvious solution to me to do a clean flash after dirty flashing as you say since August. It would be the first thing I would do, especially after reporting the problem and getting other users feedback that either they didn't experience the problem, or that a clean flash fixed it. And FWIW I don't use gapps and have never had that issue. Anyway I'm glad it's sorted and again my apologies for upsetting you
[Galaxy S 4 Mini Original Android Development] iskefiyeli:
phone shutdown directly
[Galaxy S 4 Mini Original Android Development] powwow12:
Quick question: i ve done a full wipe/reinstall and now TWRP asks me to "keep read only or allow modifications" (iirc).

I went with allow modifications. Does it make any difference?
[Galaxy S 4 Mini Original Android Development] M1chiel:
Well done, else you cannot do much with twrp.
[Galaxy S 4 Mini Original Android Development] k44mos:
After i update to the last nightly 11/04 the file manager crash, anyone else have this problem?
[Galaxy S 4 Mini Original Android Development] echo124:
Someone please post nightly from September? Most stable, no Gello/browser crashes. Thanks!
[Galaxy S 4 Mini Original Android Development] mrki14:
Same problem with file manager crash, last nightly.
[Galaxy S 4 Mini Original Android Development] echo124:
Solution :File Manager Crash- delete File Manager data in Apps
[Galaxy S 4 Mini Original Android Development] mrki14:
Thanx file manager is working now after the data was deleted.
[Galaxy S 4 Mini Original Android Development] Childe89:
Or update to latest nightly, file manager works for me after update :)
[Galaxy S 4 Mini Original Android Development] thewild:
Hi all.

Just installed CM13 on my wife's serranoltexx, great ROM, really smooth compared to stock !

One problem that I hd not anticipated though : she has an s-view cover, and it does not work with CM13. It works for locking/unlocking the phone (so basic cover functionality is present), but there is nothing in the cover's window.

After some searching, I found out that s-view was working on CM11, but that some commits had not been merges it later releases.

I haven't found those commits though. Is there some hope of having this functionality merged into CM13 or even CM14 ?

Otherwise I'll just downgrade the phone to CM11 I believe.

Thanks, and bravo for the great work on this ROM, the difference with stock is very impressive !

(sorry for posting in the wrong thread first)
[Galaxy S 4 Mini Original Android Development] Diresh:
I think temasek unofficial cm13 for serranoltexx may have what you are looking for (it was present in settings but I never tested as I don't use covers)
[Galaxy S 4 Mini Original Android Development] thewild:
Thanks for the tip, I'll give it a try tonight !

Edit : Just to be sure. Are you talking about the option "smart cover wake" ? Because this is already working in CM13. What's not working is the "view" part, i.e. display info through closed-cover when pressing the power button.
[Galaxy S 4 Mini Original Android Development] heiitorxd:
My screen turn on light blue, like blur, cloudy, idk, but this happened sometimes.

Someone has this issue?
[Galaxy S 4 Mini Original Android Development] Diresh:
Yeah I was talking about smart cover wake , not sure about the view part

Edit: maybe you could try this http://xdaforums.com/galaxy-s4-mini...-bring-s-view-xposed-dashclock-t3467186/page1
[Galaxy S 4 Mini Original Android Development] misscandy:
After last update Kingdom Heart Unchained X began to crash
[Galaxy S 4 Mini Original Android Development] echo124:
October/November nighylies unstable, aps crash, etc, keyboard aosp crashes in browser and in messaging

Release from August has some bugs like music app crash with bluetooth and volume button music slip/ fast forwaRd doesnt work.

Someone plz post link mirror to nightly from September?!

Please?
[Galaxy S 4 Mini Original Android Development] IronRoo:
I have come to the conclusion that all my browsers crash (as mentioned previously) due to scrolling, as it only seems to happen then. (possible only when scrolling down, ie sliding finger up)

Are your apps crashing when you scroll?

Though as only one other user reported his browsers also fc, I'm not sure that it's a ROM issue.

(My keyboard, Flow, also fc quite often but then it's not a common one, I can't go back to a normal one so I don't care, I also think this is an app issue ...... I should take a log sometime I suppose)
[Galaxy S 4 Mini Original Android Development] Mascarponi:
Nightly 20161021 here, never experienced a browser crash, scrolling works normal ..

Not many fc overall .. quiet stable
[Galaxy S 4 Mini Original Android Development] echo124:
Pls upload to mirror?
[Galaxy S 4 Mini Original Android Development] :
I don't think an older build will fix your problems, but I do have 20160910 and some October builds(1001, 1008, 1015, 1030) if you want me to upload one?
[Galaxy S 4 Mini Original Android Development] echo124:
Pls do, probably anything 10/15 and below is best, thanks! I try all nightlies, problem occured in october, even clean flash
[Galaxy S 4 Mini Original Android Development] :
cm-13.0-20161001-NIGHTLY-serranoltexx.zip

https://mega.nz/#!Clt32DLZ!SWSIvEPwPpQSD2dgiASDx8G92mgw7FtMCxyM3b2YsGQ
[Galaxy S 4 Mini Original Android Development] kevinarol93:
Hi [MENTION=3044346]arco68[/MENTION] I want to report that the last nightly 20161113 for Serrano3G (i9190) its buggy, I try dirty flash over the 20161106 nightly and the first boot ok, when the screen off the capacitive bottons keep awake and the phone doesn't respond, I reboot bootloop. Try a clean flash and the same problem, first boot ok, screen off the capacitive bottons keep awake and the phone doesn't respond.

Have to return to 20161106 nightly ;)
[Galaxy S 4 Mini Original Android Development] IronRoo:
Thanks [MENTION=3044346]arco68[/MENTION] for keeping the MM builds coming promptly despite working hard on the Nougat ROM. It really is much appreciated for those of us who can't switch just yet for one reason or another, but I hope to be able soon!

Thin latest nightly with build date 20161113 has a security date of 5th Nov, though it should bra noted that the much publicised DirtyCow exploit has not been patched fully by Google, for that we have to wait another month! So play safe even though it seems it's not the easiest to exploit judging from the security thread and github.

https://www.xda-developers.com/dirt...possible-after-novembers-security-update/amp/

(list of Nov patches https://source.android.com/security/bulletin/2016-11-01.html)
[Galaxy S 4 Mini Original Android Development] IronRoo:
Some of you Xposed users might want to hold off updating to nightlies with Nov security patch for the time being, as all devices seem to bootloop when an Xposed module is run (I don't use exposed but everyone on my wife's phone with Exposed has it, so thought I'd mention it)

http://xdaforums.com/showpost.php?p=69571649&postcount=4346