yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] huawei92:
and always a dual-core 1.7 GHz having the kraft education can work the type E5300 duo core handles 64-bit systems and a dual-core
[Galaxy S 4 Mini Original Android Development] mike2nl:
I think you won't understand that a car needs petrol to drive and not milk ...

So for me stops the discussion here ...
[Galaxy S 4 Mini Original Android Development] huawei92:
iPhone 6s cortex a9 dual-core 64-bit iPhone 5s cortex to7 worst of our 64-bit

---------- Post added at 08:16 PM ---------- Previous post was at 08:01 PM ----------

having a 64-bit system on our phone would be much faster than the 32bit system and our processor with set64 should be faster solution adopted by the iPhone 5's dual core cortex a7 1GB RAM 1.6ghz
[Galaxy S 4 Mini Original Android Development] vonFumatore:
Hey

So i have installed this on my i9195. Using 0418 snapshot. Also root is enabled both with adb and apps. But i cant use hiromacro or other macro app. Ive allowed those, but when recording script it doesnt record taps and doest even get my screen res. Also hotkey (vol down) doesnt work. Like its unrooted. Worked like a charm on original rom (rooted). Maybe im missing some settings ? What could be the problem ?

Edit: Little bit of searching and problem may be with supersu, cause some programs may need this. Tried different ways to install chainfire su. First from play store (didnt work...went into bootloop). Reflashed cm/gapps again...tried flashing latest 2.72 beta version from recovery...Still bootloop.

Have anyone successfully installed su on i9195 (or any s4 mini) ?

Edit: I installed su successfully. It needed to be systemless. Still it doesnt fix my problem with macro app. Su granted permissions but nothing :(
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Doze doesn't seem to work. GSam reports 0% doze time despite my phone being stationary overnight. Does it work for anyone else? I'm using the last snapshot.
[Galaxy S 4 Mini Original Android Development] JimmyRay:
I do not believe our devices support the current implementation of Doze.

You can check for yourself here.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
The app says the phone doesn't support it. If I turn on aggressive doze within greenify it works though I suspect that is triggered by the screen turning off. Trouble is aggressive doze is a bit too flaky. Thanks for the reply and link :good:
[Galaxy S 4 Mini Original Android Development] sezerkoc28:
Hi [MENTION=3044346]arco68[/MENTION] please Can you do for GT-i9195i ? No anywhere custom rom for S4 mini plus(i9195i) please.thank you
[Galaxy S 4 Mini Original Android Development] powwow12:
I have the impression that that last nightly and a couple before it made the device a tad bit faster

Maybe placebo, but a welcome one nevertheless
[Galaxy S 4 Mini Original Android Development] huawei92:
I also yesterday I passed by snapshout 18/04 to 10/05 night and I noticed that most 'fast single bug and found that when I call in dialer comes in red lettering for the rest delighted only flaw that the dialer does not allow video calling like that samsung
[Galaxy S 4 Mini Original Android Development] huawei92:
problem night 12/05 for 9195 by dialing a number and then hangs the dialer of the call
[Galaxy S 4 Mini Original Android Development] mike2nl:
Ah, to new bro. When you take one then from yesterday that must be working ;).

But first read the change log, that can help to avoid things ...

CM13 changelog for i9515
[Galaxy S 4 Mini Original Android Development] huawei92:
I am affissato with modding I like to be up to date I'm going to look for problems, I hope that they will do two things first and perhaps impossible changing set of instructions to the CPU, making 64-bit with 64-bit cm and then the dialer that allows you to do video like Samsung and more improved graphics and audio power to hear calls for the rest of the audio is fine using viper + atmos FX audio disistallando with more permissive if linux busybox
[Galaxy S 4 Mini Original Android Development] cdurex:
Question

Hi everyone,

Am about to test CM13 what would be the best "stable" zip to flash like for a daily driver i9195.

I'm going to install the latest snapshot cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx.zip

Should I go with this one?

Are there any bugs in it, that were fixed on latest nightlies?

Thanks for the feedback on this.

...Oh and I'm coming from stock ROM, anything I should know about this update process?
[Galaxy S 4 Mini Original Android Development] chrisled:
CM11 on GT-i9195I

The Russian Brothers in arms have a "WORKING version of CM11 Kitkat" for the S4 mini Duos Value Edition (GT-I9192I) (Dual Sim Version). They have Kindly made a "BackUp Copy through CWM 6.0.5.1 recovery.

Follow the links in the last few posts of this thread. ---- "https://forum.cyanogenmod.org/topic/110203-gt-i9195i-supported/"

and you will be able to use CM11 on the GT-I9195.

make sure you understand that :-

1 it is a "Work in progress"

2 It still has a few issues

3 Read the last 3 posts carefully in this thread. this gives problem and solution to a Wifi/Data issue.

4 Set up Sim 1 to use phone effectively.
[Galaxy S 4 Mini Original Android Development] iman16:
Please help - Samsung GT-I9190 is bricked

My Samsung GT-I9190 is bricked and I need some help. I installed CyanogenMod 13 on it and it ran fine for the last few months without any issue. I put it to charge overnight and when I woke in the morning it was dead. It does not come on and will not respond to any button combinations for recovery or download mode. Not connecting on PC as well. Can someone please upload GT-I9190 debrick image so that I can try to revive this phone. Thanking you in advance.
[Galaxy S 4 Mini Original Android Development] Childe89:
I don´t want to bring bad news, but it looks like hardware failure to me
[Galaxy S 4 Mini Original Android Development] tchavei:
Same happened to me (I9195 though). Luckily it was two days before the two year warranty would expire so samsung fixed it for free... They had to swap the board. Hardware failure. They first tried to swap only the power/charging circuit first but no go. They then replaced the whole board and components except screen.

Enviado do meu GT-I9195 através de Tapatalk
[Galaxy S 4 Mini Original Android Development] sezerkoc28:
Chrisled, my gt-i9195i already have KitKat 4.4.4. Have Lolipop or Marsmallow cm ROM ?
[Galaxy S 4 Mini Original Android Development] chrisled:
As far as I know, despite what we all wish for, I am only aware of CM11 for GT-I9192I and this works on the GT-I9195I because both phones are snapdragon 410 quad core. So no CM12.1 or CM13 yet.
[Galaxy S 4 Mini Original Android Development] huawei92:
For viper4android atmos you must download the latest version 2.4.0.1 pack viperatmos 5.5 beats edition running from here : https://forums.oneplus.net/threads/...android-fx-le-vere-potenzialita-audio.179784/

the audio call listening and low for the rest feels so much better the speaker with Dolby atmos with earphones or aux and spectacular

for graphics I installed sony bravia engine 4 :http://xdaforums.com/android/software-hacking/recompeliren-bravia-engine-x-reality-t3141461

the modem and reported normal s4 not for mini x mini 4.4.2

I wondering if it was possible to bring the dialer on samsung CM13 to make a video call
[Galaxy S 4 Mini Original Android Development] arco68:
Next nightly will have a new audio HAL. If you find any issues, or the volume is too high or low in some situations, report it here.
[Galaxy S 4 Mini Original Android Development] huawei92:
the last night 13/05 audio from me and perhaps should not be a problem that viper use reinstalled night 12/05 (installando notte 13/05 l'audio non va può essere che uso viper anche disattivandolo non emette nessun suono? Per il momento sono ripassato alla 12/05)
[Galaxy S 4 Mini Original Android Development] arco68:
Sorry, I didn't understand anything of that.
[Galaxy S 4 Mini Original Android Development] huawei92:
installing night 13/05 audio does not go CAN Be That viper use Even turning it off does not emit no sound ? For The Moment are passed back to 12/05
[Galaxy S 4 Mini Original Android Development] mike2nl:
I think ... arco and me have the same issue. Possible a translation issue ...

...

You mean, so far i understand that, that the 13/05 CM13 build has audio issues together with your used V4A version, but it is well working in 12/05 build and

you are back to that for the moment, right?

If i have misunderstood it, correct me please!

@arco:

The nearly correct translation is (Italian2English):

-Installed Nightly 13/05 audio does not work together with

viper, even by deactivating it does not emit any sound?

- For the moment he is back to 12/05
[Galaxy S 4 Mini Original Android Development] huawei92:
Google translator disaster :'( ... thanks bro
[Galaxy S 4 Mini Original Android Development] mike2nl:
No iusse, bro. It's my FH Syndrom ;) (see signature).
[Galaxy S 4 Mini Original Android Development] Childe89:
Didn´t noticed any sound changes in latest nightly, but in my opinion earpiece in call volume can be lowered even more (I know it was already lowered some time ago), because I have it always on lowest level, but sometimes when caller is "louder" I would appreciate to lower it even more, but I can´t, so I have to move my phone away from ear few centimeters :)

But I can´t speak for all users, If anybody else thinks in call volume can be lowered a bit, please let know in the topic :)
[Galaxy S 4 Mini Original Android Development] sej7278:
you don't need to install any su app, they were deprecated in cm12 as we now use privacy guard not su to provide root to apps. su is only used from the terminal.

if you've got the # in the statusbar, then you've not exited an app that is still using root - have you got file manager running still (you have to click back a few times until it exits, you can't just press home)?
[Galaxy S 4 Mini Original Android Development] Freddynic159:
[IMG="supersu_update_binaries"]http://iforce.co.nz/i/23rn2vyb.woh.jpg[/IMG]

You selected

TWRP/CWM

on this screen? ... If this doesn't work then probably is a problem of CM13.

---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------

I have installed SuperSU on CM12.1 and it works perfectly for giving root permissions to applications, as well as to also update the binaries.
[Galaxy S 4 Mini Original Android Development] Timir1972:
For me, another problem occurred. Data after restarting the facility will be operational after turning on / off the plane. Then, when they are turned on, for example, messenger, facebook, etc. work. Browsers (defaul, Chrome, Opera) do not. Error message: ERR_TIMED_OUT. Where is the problem?
[Galaxy S 4 Mini Original Android Development] hollandais:
No problems with this ROM. I did a full clean flash for the first one, and a dirty for all the updates, flashed pico gapps for CM13 and installed a lot of gapps. No FC or other problems. I think that a lot of problems are due to a dirty flash or the use of not CM13 gapps....

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] nohab013:
Same problem here, but what is more strange, some apps (e.g. Total Commander) can write the sdcard with same permissions.

Could you please post if you have found a solution for it? Until that i go back to 12.1

---------- Post added at 11:42 AM ---------- Previous post was at 11:35 AM ----------

Sometimes i feel the reason of some changes is purely to have additional rows in the "what we have changed" document. E.g. reverting to the vertical app drawer of Froyo-Gingerbread makes me feel like that.
[Galaxy S 4 Mini Original Android Development] Timir1972:
I made a clean and dirty installation and the problem is still the same. Data going only in some applications. But first, I have to turn it on and then turn off airplane mode.
[Galaxy S 4 Mini Original Android Development] josepmaria:
Fail OTA update with cm recovery. I'm in 20151225 nightly.

Looking at nightlies changelog image that i've uploaded, is that correct?

Thank you.
[Galaxy S 4 Mini Original Android Development] Aidan-O-Matic:
Hello all. I made a mistake with this rom. I didn't notice the incrementation to cm13 rather than cm12 and dirty flashed 13 (20121226) over 12. I now find that I cant charge the phone using any charger. The phone was not physically damaged in any way between charging attempts so my guess is that the issue is kernel based. I really don't want to wipe as have not backed up for a while, but will if I need to . Any suggestions?
[Galaxy S 4 Mini Original Android Development] sasank360:
Wipe dalvik and cache. Not data. Then flash cm12 or cm12.1, whatever you used previously. That will sort of restore earlier rom.
[Galaxy S 4 Mini Original Android Development] Aidan-O-Matic:
Thanks for your help sasank, unfortunately the battery has now died so I'm a bit stuck until I find some way of charging it outside the device (this should do the trick). If I can I'll have another go later.
[Galaxy S 4 Mini Original Android Development] milouk:
2 More bugs

[MENTION=3044346]arco68[/MENTION] i noticed two more bugs ..

1) if i turn off the developer settings then they disappear from the setting and i have to tap again 7 times build number to re enable them..

2) if from mobile data settings i choose 3G instead of LTE ...i still have the LTE indicator on the status bar..
[Galaxy S 4 Mini Original Android Development] davidmlondon:
+1 with the exception that I flashed nano gapps. Is working great so far. Thanks arco :thumbup:
[Galaxy S 4 Mini Original Android Development] hollandais:
I made a mistake, I flashed also nano gapps.

Envoyé de mon GT-P5110 en utilisant Tapatalk
[Galaxy S 4 Mini Original Android Development] davidmlondon:
Thanks, thought I'd flashed the wrong one :)
[Galaxy S 4 Mini Original Android Development] jake3317:
For some reason the phone won't start when it is charging. Put you charger in and let it charge for a couple hours, at least long enough so it has enough juice to work itself past the Samsung logo. Unplug the charge and turn the phone on. As soon as the ROM logo is visible you can put your charger back in. Don't know why, but that is how I do it nowadays. First I thought as well that my phone was damaged [emoji4]

---------- Post added 28-12-2015 at 12:00 AM ---------- Previous post was 27-12-2015 at 11:59 PM ----------

Found a bug: multiple times when I do a soft reboot, the WiFi and data connection are disabled and can't be turned on. Only a complete reboot fixes this.
[Galaxy S 4 Mini Original Android Development] KyeWalker:
I did several times re-downloading the zip. I never got any error message it just simply reboot recovery. However, I was able to install the ROM using cyanogenmods recovery. I double checked TWRP and still wasn't able to install, same problem just reboots. The following days (23rd Dec) release did install through TWRP with no problem and I am able to automatically update nightlies using TWRP.

I also noticed whilst I was using cyanogenmods recovery I was not able to install the gapps base package but had no problem through TWRP.

Thanks for your feedback though dude ;)

---------- Post added at 11:22 PM ---------- Previous post was at 11:13 PM ----------

I was able to install gapps through TWRP, I'm assuming your using cyanogenmods recovery, me personally I would use open gapps base package, they can be found on XDA.

Hope I've helped ;)

[MENTION=4593999]Timir1972[/MENTION] this may help
[Galaxy S 4 Mini Original Android Development] zayustman:
im use SD card as internal, everything works fine, but when i want to update, folder in sd card or internal memory not detected in recovery, using both Cm recovery or CMW? how to update while my SD card is used as Internal Memory?

just show

0

obb

but everythings is empty

any sugestion or explanation? thanks
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
Copy the update file to \data\Media\0\twrp, and you should be able to install it
[Galaxy S 4 Mini Original Android Development] zayustman:
can't go to that folder, root access is still the problem, wait for recovery update that can detect sd card as internal memory maybe recovery can't read formated sd card as internal??

im running first build 20151222

EDITED : works with migrate data first to internal memory, and update via recovery (internal memory detected)

after update, migrate data to sd card again
[Galaxy S 4 Mini Original Android Development] Timir1972:
I do not know what I'm doing wrong? : - / I reinstalled into the device through ODIN original ROM from Samsung.4.2.2. Everything worked. Again I done so. Clean installation of the ROM (complete wipe) and everything worked. Today I downloaded the update and installed via CWM (without wipe) Re-error occurred, do not go mobile data. Data light LTE and can not connect! WHY???
[Galaxy S 4 Mini Original Android Development] huawei92:
Sei

Thanks brother, the CyanogenMod and fantastic world you are great I'm already thinking about CM14 Android 7 * _ * I hope you will come out on our smartphones are great because they are so happy

---------- Post added at 12:19 AM ---------- Previous post was at 12:03 AM ----------

audio-yourself operating normally for all applications in the 13/05 night? Which I do not feel anything tomorrow I try with the 14/05 version
[Galaxy S 4 Mini Original Android Development] mike2nl:
It's in Italian language. I can read about 30% then it stops, but no issue at all.

I use V4A but without any package.

But i have found some interesting links, possible there is one for you too?

- G+ group: https://plus.google.com/communities/113587825367501565460

- This guy had issues too, but i am not sure it is tour case.

-- Link yo it: http://xda-android-fix-help.blogspot.nl/2016/03/viper4android-universal-fix-cm13.html

Your issue can be a SELinux issue to. Here on XDA you can find an app that can change the permission.

But you have to reboot after changes.

And i think you know this thread, and this one? ;)
[Galaxy S 4 Mini Original Android Development] huawei92:
I use app selinuxmodechanger permissive night 12/05...in the night 13/05 also having the permits should not be the program v4a Also disable I do not hear the audio sound fx if they confirm that all is well Tomorrow I do a clean install of the night 14/05 without using v4a
[Galaxy S 4 Mini Original Android Development] mike2nl:
Ok, i hope that helps. SO we have to wait until tomorrow.
[Galaxy S 4 Mini Original Android Development] vonFumatore:
No one dont know what will fix this ?
[Galaxy S 4 Mini Original Android Development] iman16:
Unfortunately I don't have such luck, my warranty expired a long time ago :(, Anyway I found a debrick image on this forum and imaged it onto a sdcard. When I put in my phone it somehow came to live and vibrated and booted. However now it is stuck in a boot loop with the following and cannot get into download or recovery mode with the usual key combinations:

BOOT RECOVERY MODE.

CHECK BOOT PARTITIONS.

COPY FROM T-FLASH.

BOOT RECOVERY..

WRITE 139008 sectors..

REBOOT

Seems like I am clutching to straws here but worth a try:fingers-crossed:. Does anyone have any ideas on what to do next?
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
I have a big issue with 13/05 nightly to which I updated Last night. When I put the phone away with wifi on, the phone turns off after a few minutes. Does anyone else have this problem too because I didn't have it before this update?
[Galaxy S 4 Mini Original Android Development] huawei92:
There I managed to have supersu through viperaudiolegacy package yesterday mike2nl night I asked this page and get supersu+ viper4android cm13 http://xda-android-fix-help.blogspot.it/2016/03/viper4android-universal-fix-cm13.html?m=1
[Galaxy S 4 Mini Original Android Development] jarod99:
Sd Card Not Reading

Hello everyone, I have a problem with cyanogenmod 13 on my S4 Mini LTE: the sd card is named 0403-0201 and I can see it only with a file manager but I can't move app on sd because it doesn't appear in app settings and also sd doesn't appear in mermory option. How can I fix this problem? Thanks.
[Galaxy S 4 Mini Original Android Development] davidmlondon:
I've been using 0418 snapshot since release as a daily driver. Haven't had any problems at all.
[Galaxy S 4 Mini Original Android Development] cdurex:
Awesome thanks for the info. Today is the day. I will be transitioning to CM in a couple of hours...:fingers-crossed::victory:

Wish me luck.... :D
[Galaxy S 4 Mini Original Android Development] davidmlondon:
The first boot takes a while, mine sat at black screen for a few minutes before it started to boot so be patient. I almost powered off thinking it must have hung. Luckily I didn't. Good luck, it's a great rom :cool:
[Galaxy S 4 Mini Original Android Development] joelalmeidaptg:
Today's nightly seems to be having a issue with the charging icon on the status bar. The phone is charging but sometimes the icon remains like it isn't. I know it's charging because if I take the cable off while the screen is off, it turns on. It's just the icon that is borked
[Galaxy S 4 Mini Original Android Development] powwow12:
Dragging the status/notification bar all the way down cuts a part of the notification box

E.g. Poweramp is the only notification active. If I drag it down, playback buttons are partially hidden
[Galaxy S 4 Mini Original Android Development] der.michal:
How to increase headphones volume in latest nightlies? I used to modify snd_soc_msm_2x file, but that option isn't available now.
[Galaxy S 4 Mini Original Android Development] Linkdk:
After switching from F4k's CM12.1 to this official CM13 i have been having some problems with getting LTE working properly. It seems it takes minutes for it to lock onto the LTE signal, even though i try to force LTE through an app.

I have tried different modems (OL2, PB2) and also tried settings up the APN settings manually but it doesnt seem to change anything. Anyone having similiar problems?
[Galaxy S 4 Mini Original Android Development] Sigur Rós:
I have a GT-I9192 with JB 4.2.2, can I flash CM?
[Galaxy S 4 Mini Original Android Development] Th3Sh3r1ff:
I am on the latest nightly and my SD card is no longer recognised by the device.

Anyone else having this issue?
[Galaxy S 4 Mini Original Android Development] arco68:
/system/etc/mixer_paths.xml

https://github.com/CyanogenMod/andr...ommon/blob/cm-13.0/audio/mixer_paths.xml#L279
[Galaxy S 4 Mini Original Android Development] gonzalomorenorovetto:
im having the same problem, everything was working on 0509 but i updated today and i lost access to the card, phone won't see it

i reverted to a backup and i still cant see the sdcard

it was formated as adopted internal storage
[Galaxy S 4 Mini Original Android Development] budgoz:
Same here. Let's see if in today's nigthly it has been fixed.
[Galaxy S 4 Mini Original Android Development] vampires.remembered:
Same here 64GB formatted as portable... It always show as corrupted even after formatting.

After reboot the phone is stuck in boot loop whenever the sdcard is in the slot...

I can't access it if i set it as internal.

started from cm-13.0-20160513-NIGHTLY-serranoltexx.zip, if i remember correctly.
[Galaxy S 4 Mini Original Android Development] artu72:
That is strange, I have no problems

Inviato dal mio GT-I9195 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] der.michal:
Thank you, big boss
[Galaxy S 4 Mini Original Android Development] mike2nl:
You had read the 1st posting Sigur?

-> WARNING! This ROM is for the GT-I9190 and GT-I9195 variant only!

Big red letters, so i don't understand your question in this thread here.

Possible a mistake ...

Had you used google so as we all use search functions (and not eat it only),

you had found 100% what you are searching for.

<wisper>

Please Sigur, next time use the google or XDA search function first ...

</wisper>