yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] jason972000:
To rule out issues with your GPS, check if "GPS Status & Toolbox" from Playstore shows your correct coordinates. Also check if Google Maps navigation is working.

Also make sure the app has location permissions set.
[Galaxy S 4 Mini Android Development] nachosz1:
I'm using nightly (03-20-2017), and this notification doesn't stop, even if I set to doesn't t notify me.
[Galaxy S 4 Mini Android Development] Maddoxnl:
Yesterday I installed stock ROM. Then clean installed aopk 20-3. At first there was no mobile data. Performed a reset of networks. Then mobile data was OK.

Now I have a problem with Bluetooth. I can connect with my parrot carkit, but not with my jbl charge 3 Bluetooth speaker.... Does anyone have a idea where to search for a solution? Wipe cache? Install a other Bluetooth app? I'm lost for now....
[Galaxy S 4 Mini Android Development] csendre:
try today's build when it comes out. arco68 merged some BT related commits into the device tree
[Galaxy S 4 Mini Android Development] Maddoxnl:
Clean flash required?
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
What's you guys thoughts on Android O ?
[Galaxy S 4 Mini Android Development] Keller0088:
I have a biiiiig enormous question, if you look at the past of android, it was like, 2.0/2.1/2.3/4.0/4.1/4.2/4.3, and now is like android is walking on wuge steps, like 5.0 to 6.0 to 7.0 and now to "8.0", my question is, is this Marketing? Is this just to copy iOS, like iOS 8 Andoid 8? And... All this huge steps (5.0/6.0/7.0) are a lot things that were implemented to say 8.0 and not 7.2 or sth like that?
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
tbh I feel same, as far I know these 7.0 8.0 are major versions but 7.1 etc are revision
[Galaxy S 4 Mini Android Development] pedro311:
At last:

And it's working! :D
[Galaxy S 4 Mini Android Development] gabom88:
Offtopic about Super Mario Run

I'm already using AOKP over my s4 mini but i can not run Super Mario Run. any idea?.

The Game crash when appear the red Nintendo Logo.

Thanks and sorry for the offtopic
[Galaxy S 4 Mini Android Development] Lucifer.S:
Is this works for dual Sims model i9192???
[Galaxy S 4 Mini Android Development] :
I would advise anyone who has a question like this, to at least read the first post of the thread.....
[Galaxy S 4 Mini Android Development] Lucifer.S:
Ok
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
Yes I have it and works
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
[MENTION=5416372]csendre[/MENTION] have you added some performance tweaks in latest aokp because its faster and smoother then previous build???

I recommend all to update to latest aokp

Thanks for your hardwork
[Galaxy S 4 Mini Android Development] RomarioUKR:
It's a good idea :good: updating to latest ROM versions, but it's a little bit annoying to backup messages (Viber, whatsapp), dirty flash, restore apps, messages, register again... A lot operations to do. :silly:
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
why don't you dirty flash it?
[Galaxy S 4 Mini Android Development] RomarioUKR:
I think for nightly builds it's OK dirty flashing or I'm mistaken? :confused:
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
It's ok

If you switch from unofficial to official or vica-versa then it needs clean flash
[Galaxy S 4 Mini Android Development] nachosz1:
Today's nightly power menu is working!!
[Galaxy S 4 Mini Android Development] csendre:
??? I never had an issue with it
[Galaxy S 4 Mini Android Development] nachosz1:
Aokp rom control > power menu > "Rom control stopped working". It was happening in all nightlies until today's nightly. I've done two clean flash, but the issue went on.

(sorry my English)
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Hi Everyone,

This week my trusted oneplus one broke down so i decided to get back to my i9195. It was still on stock 4.4.2 so i wanted to upgrade it to this AOKP. However, when i flash it with TWRP it bootloops at the samsung logo (with warranty bit kernel displayed).

I used Heimdall to flash back to stock and then i repeated the TWRP, wipe, AOKP flashing process with no succes. Using adb logcat does not produce any log at all since it stays on "-waiting for device-"

The only rom i can flash with success is CM13-20160418-ZNH0EAO2NJ otherwise i get into the same bootloop (also with newer cm13 snapshots or lineage nightlies).

If i flash AOKP nightly and then the f4ktion_lp_2.3.1-eurlte kernel (which is intended for cm12) it will boot but remain stuck at the unicorn boot logo. Is there

it seems like it cannot find the kernel

Can anyone help me with this issue?

If there is any further info required please let me know

Thanks is advance! :)
[Galaxy S 4 Mini Android Development] Rainy_2k:
Wrong kernel version. Try clean flash + gapps, without kernel.
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Thanks, I know, without the kernel it also didn't work, i tried that before.

With the kernel i at least got to the booting logo, thats why i thought there must be something with the kernel
[Galaxy S 4 Mini Android Development] syednawaz:
why not try remix kernel? FK kernel is outdated. its not for cm14.

its hard to believe that its kernel problem bec lots of ppl here using i9195 with aokp.

Some steps you may already know but.

try using odin to flash the stock(do the main settings like selecting language,wifi setting,google,Phone name)

after that install twrp through odin(3.03.0 from here https://xdaforums.com/showthread.php?t=2678420)

and finally just install AOKPcm14 without gapp or kernels(my rom is dated 24.03.2017 , working fine).

and wish you can have a good luck.

Still you can try normal cm14(https://xdaforums.com/galaxy-s4-mini/development/rom-cyanogenmod-14-0-s4-mini-duos-t3477343)

i do things like this as i also got error rarely,like loop or black screen after the unicorn.or crashes at main screen. but it got fixed by doing steps above.

last.... seeing your post i think you already know all this. but just trying to help.... Hope you can install this awesome rom.
[Galaxy S 4 Mini Android Development] shepvrd:
In last 2-3 builds substratum doesn't work, it just like doesn't see OMS support and offer me legacy mode
[Galaxy S 4 Mini Android Development] csendre:
Just tested on today's nightly, no issues here. Perhaps wipe app data, and reinstall
[Galaxy S 4 Mini Android Development] shepvrd:
Just flashed DS 26.03 build from xfer with cache/dalvik/system/data wipe, substratum still closing at settings, works in legacy mode
[Galaxy S 4 Mini Android Development] helium314:
For me it works, but I had to remove substratum and install again after dirty flash.
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Thanks,

Yes i tried this too. The remix Kernel does not boot. It keeps stuck then at the samsung bootlogo. With CM13 only the april 2016 snapshot boots, if i update to the later snapshots it will be stuck.

Therefore I think something changed between those snapshots which is incorporated in all further cm based roms but i dont know what.

I tried your suggestion with Heimdall (OSX doesnt support odin) and TWRP 3.0.3.0 then i get stuck in the same bootloop again if i try to boot to recoery. If i use TWRP 3.1.N0-0 I can get into the recovery but if i flash anything except from the earlier mentioned cm13 snapshot i get a bootloop again. So no AOKP so far :crying:
[Galaxy S 4 Mini Android Development] csendre:
That is not what I meant. Clean cash and data for Substratum (the app, not system) then remove it and install again You may have some issues because of the change from rooted to non-root package. If this doesn't work either, you'll have to do a clean flash.
[Galaxy S 4 Mini Android Development] csendre:
Back up what you have on internal storage then boot into TWRP, go to wipe and from this menu select the "Format Data" option on the bottom right. Once done, flash latest nightly with no other kernel (you can do this later) or gapps. If this works, then you can reboot to recovery and flash latest remix for cm14 and gapps
[Galaxy S 4 Mini Android Development] shepvrd:
Well I flashed 3.1.0.0 TWRP (Odin version), then clean flashed and everything works. Anyway thanks for the info :)
[Galaxy S 4 Mini Android Development] Keller0088:
Man, this ROM is for S4 Mini DUOS, your version is the one sim 4G
[Galaxy S 4 Mini Android Development] Rainy_2k:
It's ok. His mobile is seranoltexx
[Galaxy S 4 Mini Android Development] Rainy_2k:
Just started to clean flash the 2017-03-26 build. Made a backup, wiped cache/dalvik-cache/system/data and there is no external sd... Nothing... Nothing that I can understand... I think now I need to flash stock with ODIN and lose everything and also second 64GB micro sd. (((

UPD: Understood.

Adopted storage keys are gone from /data/misc/vold folder. I have a backup of them. Now I'm trying to push them to /sdcard, but here is an error:closed

C:\ADB>adb push c:\adb\push\ \sdcard

error: closed

How I can copy the keys somewhere with adb and then move them to /data/misc/vold?
[Galaxy S 4 Mini Android Development] csendre:
Not me, the team keeps constantly working on it. This is why I stick with aokp, love the team behind it
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
yeah this tweaks are amazing
[Galaxy S 4 Mini Android Development] csendre:
That is a bit excessive :) All you have to do wipe dalvik, wipe cache and flash the ROM (aka dirty flash). This way all your data is retained However, it is a good idea to make a full backup from time to time, things sometimes go wrong with dirty flash.
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Thanks,

I just tried this (with the aokp_serranoltexx_nougat_nightly_2017-03-26_ota.zip) and I am stuck in the same bootloop again.. :(

I think the issue is that it cannot read the kernel (included in the nightly)

Here is what i tried so far chronologically:

- TWRP 3.1.N + wipe + AOKP Nightly --> Bootloop at samsung logo

- flash stock rom I9195XXUCPA1_I9195PHNCPB1 --> phone boots (but stock rom)

- TWRP 3.1.N + wipe + AOKP Nighly -- > Bootloop at samsung logo

- flash repair stock I9195XXUCNJ6_YERCNJ3_v4.4.2_Repair_Firmware --> Phone boots (but with repair ROM)

- TWRP 3.1.N + wipe + AOKP Nighly -- > Bootloop at samsung logo

- TWRP 3.1.N + wipe + AOKP Nighly + f4ktion_lp_2.3.1-eur_lte kernel -- > Phone boots but stuck at AOKP logo: kernel mismatch

** I got an idea: maybe custom kernel works --> downloaded cm14 remix

- TWRP 3.1.N + wipe + AOKP Nighly + Remix-kernel-CM14-v.9-LTE-20170307 -- > bootloop stuck samsung logo

** wanted to cry :/

- TWRP 3.1.N + wipe + cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx -- > Phone boots works perfectly

** wanted to update to newer cm13 snapshot

- TWRP 3.1.N + wipe + cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y6-serranoltexx -- > Bootloop again at samsung logo:mad:

** lets try AOKP again:

- TWRP 3.1.N + wipe with "Format Data" + AOKP Nightly --> Bootloop at samsung logo

i am totally clueless of what the issue is. Should i try another stockrom? is there something left somewhere which prevents me from installing newer custom roms? I basically wiped and reinstalled everything :confused: :silly:
[Galaxy S 4 Mini Android Development] csendre:
[MENTION=1577769]Dmitrinyy[/MENTION] This has nothing to do with kernel. If the image is read and TWRP is able to flash it, it is impossible that the kernel is not read. You either have a hardware issue or something is left over on your phone (from stock most likely) that causes the bootloop.

You can try a few things:

- Wipe everything then flash another stock ROM with Odin (find a friend with a windows PC if you don't have one) then flash back to TWRP and try AOKP again.

- If above doesn't work, flash CWM recovery (with Odin). This is old, but has better formatting options and you can format all partitions with it. I would format (and I mean format NOT wipe) /system, /data, /data /media and both cache partitions, then try to flash AOKP

If none of the above works then you must have a HW problem.
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Thanks for the explanation

i will give it a try later this week, need my phone now for some calls.

I will let you know if it works
[Galaxy S 4 Mini Android Development] Dmitrinyy:
Ok,so i couldn't let it go and tried everything you said with Odin with no success:

CMW was installed and formatting everything did not make a difference.

After installing AOKP i got a bootloop. Flashing the BlissRomKernel-serranoltexx-20160326 kernel (which is meant for CM13) i randomly got the device to boot AOKP (all the way to launcher) and run with some things not working off course..

Anyway thanks for the help i think it is a hardware issue then..
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
Guys there is a good news.

We can install samsung internel browser via play store

I have attached some screenshots

https://play.google.com/store/apps/details?id=com.sec.android.app.sbrowser.beta
[Galaxy S 4 Mini Android Development] zogger:
BT again

Upated yesterday from 25.03 to 28.03 build and BT connection problem returned (similar to that mentioned in #727). The rest is working perfect. Could you be so kind and fix it again?

Thanks a lot.
[Galaxy S 4 Mini Android Development] csendre:
There were no changes to BT, it should be working. Try a clean flash.
[Galaxy S 4 Mini Android Development] csendre:
I see loads of changes to Gallery in today's build. Has anyone tried if FC issues are gone? I didn't get a chance to flash it yet

Update: new gallery app works well so far, looks somewhat different
[Galaxy S 4 Mini Android Development] zogger:
Dirty flashed 03/30 build and everythings fine again. Perhaps I forgot to clean cache in previous installation.

A backup and restore feature of the systemprofiles would be nice, and a profile tile.

:good:
[Galaxy S 4 Mini Android Development] hexthor:
Can i have two sim cards in the i9192 model working fine?

In the last build, of course...

---------- Post added at 01:51 PM ---------- Previous post was at 01:25 PM ----------

Second question: how i fix this message "Set warranty bit : kernel" after install the rom?

I don't want to return to stock rom.
[Galaxy S 4 Mini Android Development] syednawaz:
installed 31march. yup galary works fine. but now i refreshed the page 1st april update also got released :(
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
Nope as far I know 2nd question*
[Galaxy S 4 Mini Android Development] csendre:
Of course, why wouldn't it work?

This is a Knox thing, I don't think it causes issues. arco68 looked into this, but couldn't test it. Let me do some digging

Update: that was for something else. The set warranty bit: kernel message is harmless it is caused by Knox bootloader. No fix for it but as I said it doesn't do anything.
[Galaxy S 4 Mini Android Development] hexthor:
same :(
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
The thing it shows is the device rooted
[Galaxy S 4 Mini Android Development] syednawaz:
Not really. If you have stock rom with stock bootloader and recovery and it is rooted. You will not see set warranty bit as phone start.

When changes are done to either boot loader or recovery you will see this set warranty writing.
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Thanks but i've already returned to the MM version, because after rooting this one my phone doesn't starts. hahaha I'm just having problems with this version.
[Galaxy S 4 Mini Android Development] AMOLK:
Settings>wireless & networks>more>emergency broadcast. Remove tick for all cell broadcast setting...after that you will not get these messages.
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Thank you, what root method are u using? Because I use the chainfire and my cell phone does not turn on when I flash.
[Galaxy S 4 Mini Android Development] AMOLK:
Inbuilt root with this ROM....For more details go to developer options

---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------

Also try clean flash and latest open gapp(any module is fine) sametime....first time it will take sometime to boot but not more than 15 min.
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Man I already deleted everything before flashing this rom. And about this root method, Is it not necessary to flash any files?
[Galaxy S 4 Mini Android Development] rookie12:
You don't have to any files root built in
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Really? So I'm a old school, I thought it only works with that chainfire root file.
[Galaxy S 4 Mini Android Development] rookie12:
All AOSP based ROMs has root built in

You only need to flash chain fire root file when ROM dev tells you to do
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Another noob question:

Are u guys using super su? I can't complete the installation.
[Galaxy S 4 Mini Android Development] rookie12:
No no super su app and what part of the installation you can t complete?
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
After the apk installation, when asking permission to restart.
[Galaxy S 4 Mini Android Development] csendre:
No need for super su. Just wipe everything again and do a clean flash. In AOKP you don't even have to enable root yourself, it is enabled by default.
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
There's some apps that they are not working right. Apps that requires root access.
[Galaxy S 4 Mini Android Development] AMOLK:
Every apps work fine.........except data connectivity issue for me.
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
I use the app2sd and titanium backup. Both aren't working well.
[Galaxy S 4 Mini Android Development] AMOLK:
I also use Titanium back up to restore all apps and data and it's working well no issue...
[Galaxy S 4 Mini Android Development] Sarcastic Warrior:
Well, i've returned again to MM. Thank you anyway, i'm gonna stop flooding this thread.
[Galaxy S 4 Mini Android Development] rookie12:
A very noob question

What will happen if I flash a cm13 serranolte or a serrano3g on a serranosdd?

I want the nightly
[Galaxy S 4 Mini Android Development] glkanth77:
Twrp won't allow you to flash and somehow managed to flash RIL will not work that means sim card will not detect
[Galaxy S 4 Mini Android Development] csendre:
http://xdaforums.com/showpost.php?p=69881908&postcount=321
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
I noticed so something about the new gallery, before you open it its green icon right? But when you open it and touch recents the icon is red and orange
[Galaxy S 4 Mini Android Development] hexthor:
When I activate the control ROM-> power menu-> screenshot and try to take a screenshot the phone reboots :(
[Galaxy S 4 Mini Android Development] asterismo:
Is there anyway to at least download the ROM files with a secure connection?

---------- Post added at 01:45 PM ---------- Previous post was at 01:36 PM ----------

Well, i found this link: https://basketbuild.com/devs/aokp/serranodsdd But there are 0 downloads, is this right? or is it clickbait?

Cheers,
[Galaxy S 4 Mini Android Development] Ahmed Kirkuk:
Use xfer it's faster and safer

http://xfer.aokp.co/?developer=AOKP&folder=serranodsdd
[Galaxy S 4 Mini Android Development] csendre:
Yeah, known bug, it is on the to do list. For now use volume down + power button combo
[Galaxy S 4 Mini Android Development] asterismo:
I misses the part in how a http link is safer anyways...
[Galaxy S 4 Mini Android Development] csendre:
What safety do you need? There is no login required so what exactly are you trying to protect?
[Galaxy S 4 Mini Android Development] asterismo:
The page has no secure connection, green lock icon? I mean, the OS of a mobile phone is in some sense, a security product, so it should be downloadable with a decent https connection, with checksums provided and such. right?
[Galaxy S 4 Mini Android Development] csendre:
Not quite. Secure connection keeps communication between you and a server secured so that no information about that communication (e.g bank transactions, passwords, etc.) is divulged. When it comes to the simple download of a file it is utterly useless and unnecessary.

If you don't trust the content of the file it is a different story, this is your prerogative and in this case you should stay on stock. These are official builds stored on trusted servers and just as trustworthy as any other official builds out there. Your chances of getting yourself in trouble is a billion times (actually more) higher by connecting to someone’s wifi then by downloading these builds.

Checksums would helpful only for verifying that your download did not get corrupted in the process (it happens) and for a long time I used to upload md5sum files for this purpose. However, since nobody was using them, I gave up on this just as everyone else. If you have a corrupt download just download and flash again.
[Galaxy S 4 Mini Android Development] asterismo:
Yes, and any if that undermines my reasoning. I assume developers put tge ROMs in serves they trust. So if you trust the server, the only remaining basic security aspect is that that server provides a secure connection for the user to download. I found AOKP ROMs in insecure connections and some other ROMs (maybe the same ones) in an external server providing yes, secure connection as i mentioned in my second post about the subject, the only thing i notices is the 'zero' download score. The xfer.aokp.co download page does not provide secure connection and thst is a major security issue for the whole thing i think. You may think otherwise. I was asking about a secure way to download the roms, and then i sirt of changed my question to that second site i found outside xfer.aokp.co that was providing https connections.

Best regards,
[Galaxy S 4 Mini Android Development] ffatboy:
Update Nightly

Hi,

How does one update from one nightly to the next without doing it manually?
[Galaxy S 4 Mini Android Development] rookie12:
No you have to do it manually is the only way
[Galaxy S 4 Mini Android Development] csendre:
It seems BB is still in maintenance mode so please use xfer for new builds for the time being.
[Galaxy S 4 Mini Android Development] Rainy_2k:
An investigation of chrysaor malware
[Galaxy S 4 Mini Android Development] nachosz1:
[MENTION=5416372]csendre[/MENTION] the option to turn on the torch with power button when the device is blocked was removed. Is there a way to put it back?
[Galaxy S 4 Mini Android Development] csendre:
Yes, something went wrong with an update. Reported it, will be looked at. Strange thing is that it still works if you had it turned on before dirty flash, so it is a user interface issue.

Update: OK, so I forgot as well ... this is under lockscreen options and not HW keys ... it is still there
[Galaxy S 4 Mini Android Development] nathanpearce0:
Issue with Snapchat

Very good rom, very smooth and enjoy running. I have an issue with the rear flash on snapchat. It does not focus for the first picture and then for the second it turns flash on and focuses but does not take a picture and hangs on the flash. Not sure if I post the issue here or someone else as I am new, please help.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
No issue with the rear cam flash in Snapchat make sure you upgrade to latest aokp with clean flash
[Galaxy S 4 Mini Android Development] nathanpearce0:
I have clean flashed but still have the same problem, I cleared data before flashing ROM but still have the problem.
[Galaxy S 4 Mini Android Development] Harvey_Spectar:
which model?

for me on serranodsdd its working fine
[Galaxy S 4 Mini Android Development] kevinarol:
Hi [MENTION=5416372]csendre[/MENTION] I want to report you I am unable to add some quicktile, everytime when I try to drag and drop the tile this disappear

http://i1195.photobucket.com/albums/aa383/kevinarol/tile-error.jpg
[Galaxy S 4 Mini Android Development] csendre:
Sorry, I don't understand what the issue is. Which tile did you try to add and what disappeared? I tried this morning and added a few tiles with no issues.
[Galaxy S 4 Mini Android Development] nathanpearce0:
serranoltexx is what I am using.