yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Kot_Ik:
Everything is ok for a long time. This issue has been fixed. You should use last nightly.
[Galaxy S 4 Mini Original Android Development] devilhopper:
I did some testing on this and got lucky. Turns out that the issue is in conjunction with a certain weather app I'm using, so if I turn it off, GPS will work just fine. The weather app caused no issues in previous Android versions, however, so I am still not convinced that the problem is with the app (could be the app, or a glitch in Lineage, or a combination of both). Also, if this was a general problem with the app, it would be all over the reviews in Google Play - however this is a very popular app with a 4.5 star rating, and I could not find anybody else having the same problem.
[Galaxy S 4 Mini Original Android Development] Michael24884:
If I were to change the kernel, would it be possible to flash this ROM to the Spring variant?
[Galaxy S 4 Mini Original Android Development] christiangre28:
Do we have any idea of when will the s4 mini will get Android 8.0 or even get it? I'm really excited to see it happening plus it promises more battery life and faster respond times. Thank you in advance for answering ☺️
[Galaxy S 4 Mini Original Android Development] devilhopper:
You're welcome.
[Galaxy S 4 Mini Original Android Development] Abelus:
Is it necessary to use custom recovery or can I flash it with stock recovery?
[Galaxy S 4 Mini Original Android Development] IronRoo:
No, you need custom recovery
[Galaxy S 4 Mini Original Android Development] Abelus:
Is there an instruction on how to install one, specifically for s4 mini duos?
[Galaxy S 4 Mini Original Android Development] IronRoo:
you must use a recovery specially made for your device, use TWRP from neozone thread below, I'd actually suggest using the tryout version 3.1.1

https://xdaforums.com/showthread.php?t=2678420

you need the tar.md5 file for your device and flash it with Odin (if Odin doesn't recognise your phone download Samsung USB drivers to your PC & reboot), the first time you flash TWRP follow option 1 instructions, [after that you can update just flash the zip file like you would when updating the rom with a zip file, Odin not required] (option 2)

(note: Slightly more detailed instructions may be found on the net for various Samsung devices, which you can use/watch to fully understand, if in any doubt, but follow the procedure in the TWRP thread above)

Backup before flashing TWRP: make sure you back up all your photos, documents, music etc to your PC, just in case of problems. TWRP/CWM etc do not back these up as in the data folder. Don't forget photos from apps like Whatsapp etc that may be hidden away in their own media folders, & recent call logs etc if important to you. Also any data on Samsung apps you may need to be recorded somehow or exported to another format that other apps can import as Samsung apps will not work on other roms eg Lineage OS. (you should probably also run a backup from your current Samsung recovery right now and move backup to your PC, not that I did.)

Backup after flashing TWRP: before installing custom rom run a full backup from TWRP saved to external SD card, so you can easily go back to your current setup, make a copy on your PC also.

You don't need to back anything up but it will make your life easier if anything goes wrong ;)
[Galaxy S 4 Mini Original Android Development] Olfason:
how i can see sdcard in windows GT-I9195 mtp device (i can only view and use internal storage)?

how i can use storage access to use sdcard in some apps?

...

I can access and write sdcard with a root file explorer via mnt/media_rw/xxx...

i can mount internal folder to sdcard. you can do this easily with FolderMount [ROOT]

i can access sdcard via TWRP
[Galaxy S 4 Mini Original Android Development] Rajesh Rajak:
is there any problem in new build 21/09/2017 for gt-i9192

because my phone not going further from sim setup and setup is closed unfortunately

please help
[Galaxy S 4 Mini Original Android Development] MJay99:
Just in case anyone runs into the same issue:

Dirty flashing to 2017-09-22 the included changes to FlipFlap seemed to have made it stop working after boot.

Deleting Dalvik and disabling / re-enabling FlipFlap made it work again for me.

(accidently posted to a wrong thread before)
[Galaxy S 4 Mini Original Android Development] JohnSoong:
For me, the only way I can see SDcard on windows is to either be in TWRP; or if in System, select "USB for file transfer" in the USB selection menu.

Selecting PTP only mounts the internal storage. There is no MTP selection in LOS that I can find.

EDIT: There is MTP selection in developer options, that appears to be the same as selecting "USB for file transfer".
[Galaxy S 4 Mini Original Android Development] powwow12:
Guys, I have a very annoying problem: alarm clock doesn't work when screen is off. When it comes the time to be triggered the phone restarts itself

If the screen is on and the time comes, alarm sound normally and there are no restarts

Ideas?
[Galaxy S 4 Mini Original Android Development] bdy64:
No confirmation here on lineage-14.1-20170922-nightly-serranoltexx. Works as intended.
[Galaxy S 4 Mini Original Android Development] em404:
Same, works on 20170922.

I had 2017-09-15 and 2017-09-22 installed on a GT-I9195 and USB data connection doesn't work on Windows nor on Linux, there is no notification when it's plugged in, there is no USB setting in Storage, "Select USB Configuration" in Developer options doesn't do anything(stuck on MTP), doesn't matter if USB debugging is on or off, wiped cache, /data, what else should I try? It worked on stock ROM, tried 3 different cables, Download Mode still works.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
USB worked fine for me (also I19195) for all the nightlies.

Did you try USB connection while in TWRP? And did adb detect your device? If neither works, maybe something to do with the windows drivers getting messed up, or something wrong with the USB port.
[Galaxy S 4 Mini Original Android Development] em404:
MTP in TWRP doesn't work, ADB only works over wifi, ADB sideload gets stuck loading in TWRP.

Can't be the USB imo, other samsung devices work just fine and it worked with stock ROM.., it doesn't connect on other PCs either.
[Galaxy S 4 Mini Original Android Development] utfluc:
Maybe it's your phone's USB port? Have you checked with another ROM? I haven't read your previous posts, so I don't know if you've tried that already.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
If USB don't work in TWRP or ADB, then it is unlikely to be the ROM. (But if you revert back to stock ROM it works?)

If you can connect to PC with other samsung devices, then it can't be the on the pc side.

I agree with the other poster, maybe the usb port in the phone. Try cleaning it first?
[Galaxy S 4 Mini Original Android Development] em404:
Here I mentioned that Download mode works so its not a hardware/connection issue, wireshark can see a few USB packets going back and forth when it gets connected.

Any ideas how to debug this? Baseband is I9195XXSCQAN, logcat doesn't report any erros when connecting, I get this in dmesg when changing from Charging to MTP in developer options:

[ 501.532000] msm8930_mclk_event: event = 1
[ 501.532427] usb: functions_store buff=mtp,adb
[ 501.532427] usb: android_enable_function name=mtp
[ 501.532427] usb: android_enable_function name=adb
[ 501.532794] usb: enable_store enabled=1, !dev->enabled=1
[ 501.532794] usb: enable_store f:mtp
[ 501.532794] usb: enable_store f:adb
[ 501.532824] usb: enable_store vendor=4e8,product=6860,bcdDevice=228
[ 501.532824] ,Class=0,SubClass=0,Protocol=0
[ 501.532824] usb: enable_store next cmd : usb_add_config
[ 501.532916] init: Starting service 'adbd'...
[ 501.549549] adb_open: 1 callbacks suppressed
[ 501.549549] adb_open
[ 501.549549] usb: android_bind_enabled_functions f:mtp
[ 501.549580] mtp_bind_config
[ 501.549610] usb: android_bind_enabled_functions f:adb
[ 501.549610] usb:: ci13xxx_pullup is_active: 1
[ 501.549641] usb:: ci13xxx_pullup udc->udc_driver->flags:3f
[ 501.549641] usb:: ci13xxx_pullup !udc->vbus_active:1, !udc->driver:0
[ 504.726689] msm8930_mclk_event: event = 8
[Galaxy S 4 Mini Original Android Development] kolak1234:
Can You explain how to back flip flap step by step.

Tnx
[Galaxy S 4 Mini Original Android Development] MJay99:
Not saying there might be not be other or more efficient ways, but this worked for me:

Reboot into TWRP, select wipe, be VERY careful to only select DALVIK/ART Cache.

Boot back into system, disable and re-enable Flip Flap in the Settings. Open and close cover... fixed two out of two mobiles for me.
[Galaxy S 4 Mini Original Android Development] devilhopper:
Can anyone confirm this please?
[Galaxy S 4 Mini Original Android Development] JohnSoong:
So basically fastboot works for you (download mode) but adb doesn't over USB. I am stumped. Maybe someone else has an idea??

A wild stab - maybe it is TWRP. What version are you using? People had problem with 2.x & this ROM. (Although I have not heard of USB issues.) I've been running 3.1 since migrating from CM 13.
[Galaxy S 4 Mini Original Android Development] the_MacAce:
Factory Mode

Any ideas why my phone is after switching off starting again by itself and booting into "Factory Mode" (see attachment)?

I came from Stock Android, flashed via Odin TWRP v3.0.3-0 and installed then LineageOS 14.1 (lineage-14.1-20170922-nightly-serranoltexx) and GApps Nano.

Everything worked fine but after second day when switching the phone off it boots again by itself into Factory Mode and I cannot enter TWRP anymore...

I can switch the phone off again and then it boots again by itself into Factory Mode. I have to switch it off, boot into Download Mode and from there Reboot to enter Android again.

There everything works fine until switching the phone off :D

I already made Factory Reset, flashed TWRP again and installed LineageOS again but Factory Mode appears again.

Removing battery also doesn't help, phone is booting again by itself into factory Mode when I insert the battery...

What can this be? :confused:

Thank you very much in advance!
[Galaxy S 4 Mini Original Android Development] ptr1968:
Install twrp again with Odin, Home-volumedown-power button.

Then before flashing new firmware, do system wipe and dalvik/cache wipe

After flashing firmware and gaps reboot

Do not instal the TWRP app when it is asking in the end, I got some issues with that

I have the exact same setup as you since yesterday and its working fine

Peter
[Galaxy S 4 Mini Original Android Development] Mohammed Bhere:
I did not find a choice flip flap in sitting ?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Do you have a case with a magnet in it? It then must be open & closed to show flip cover settings in settings. Search this thread for more

---------- Post added at 04:09 PM ---------- Previous post was at 03:45 PM ----------

looks like it's related to corrupt efs. Search for "exit factory mode" or look at the following. (I'd make a back up of your efs first though ..... Even if it's corrupted now you can still get it working ..... Maybe)

https://mobiletrans.wondershare.com/android/factory-mode-android.html
[Galaxy S 4 Mini Original Android Development] dong2007:
Hey Ppl,

I´M on CM 13 (S4 mini LTE) (see the attached pictures for more)

I want to migrate to Lineage 14.1 without loosing any user data (Of course i already have taken a backup)

I´ve read i should download an Experimental version to migrate but where can i found that file?

BTW: my recovery file is CWM clockwork-6.0.5.1
[Galaxy S 4 Mini Original Android Development] IronRoo:
The tool was originally for migrating from unofficial to official builds of LineageOS , I think. It was not really meant to migrate from CM13 to LOS14, but it seems to work OK, but some apps might misbehave or even cause your phone to reboot, I had some FC which nobody else has reported so the migration from CM13 might have been to blame. I used TWRP

The old unofficial builds are located in the 2nd post.
[Galaxy S 4 Mini Original Android Development] MJay99:
With TWRP, I remember migrating from CM13 to LOS13 (my own builds at first), then also the unofficial builds of LOS 13 by arco. Via the migration zip mentioned in a link in post #1 I went over to the official version of LOS 13 and then on to LOS 14 unofficial again (dirty flashing / upgrading) and again back to official as soon as it came out. From there, onwards to today's versions every few weeks. No significant issues (other then intermediate bugs in a couple of releases) encountered on that journey :)

This definitely isn't a recommended way, just a personal experience / success story ;)

If I was to try now, I'd test going from CM13 over to LOS13 official via the migration zip, then directly to LOS 14 official without any modification.

Maybe someone else can chime in if this worked for him / her.
[Galaxy S 4 Mini Original Android Development] dong2007:
[MENTION=5975519]IronRoo[/MENTION] & [MENTION=8222739]MJay99[/MENTION] Thx for the input :)....

I´ve cleared everything (wiped system data & cache and dalwik cache) and installed lineage OS 14.1 on new fresh...

But i have an other issue - i can't get root to working, i ´ve installed s4mini_RootKit_v2 via recovery mode with successful.

I´e updated the SuperSU app to the newest version

I´ve set the permission for root access to apps under development settings, but the says still i have no root access?

Look at the attached pictures for more.

Any ideas? :)

//

Dong
[Galaxy S 4 Mini Original Android Development] IronRoo:
You just need to flash the root add-on from the LineageOS extras page
[Galaxy S 4 Mini Original Android Development] dong2007:
Thx mate - I had just overlooked that :) - but it seems the lineage servers is down now.....
[Galaxy S 4 Mini Original Android Development] Abelus:
Is it possible to return to official android from the lineage os? I want to make sure before installing the lineage.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
By official android you mean the stock ROM that the S4 mini came with?

Make a nandroid with TWRP before you flash anything, then you should be able to use that to return your phone to the state it was before you flash LOS. If you start out with stock, you should get back to the stock ROM.

Of course, flashing TWRP would wipe your stock recovery and trip KNOX. If that is important to you, you would have to look for a stock image (specific to your model) that you can flash back to. <I found one thread at xda for the i19195i, but not the others.> However, even this may not untrip KNOX. <There are some workarounds, but I have no experience in going back to truly stock - with KNOX enabled, etc.>
[Galaxy S 4 Mini Original Android Development] Smeagal192:
See if sammobile has original S4 mini for your country, you could then restore using odin full factory image.

Why you would want too, I wonder :silly:
[Galaxy S 4 Mini Original Android Development] cdurex:
I've used Kies in the past( think is not working now ), and also Heimdall with images from sammobile

Odin works too.
[Galaxy S 4 Mini Original Android Development] Thoadi:
Me too, no reason to go back! Before I would go back to CM13... The only thing I miss is the Substratum Theme engine...
[Galaxy S 4 Mini Original Android Development] tostep:
Lineage 15.0

There are some news from LineageOS team:

May be, wrong topic, but I'm interested about official LineageOS 15.0 on our devices. :)
[Galaxy S 4 Mini Original Android Development] MJay99:
LOS changelog mentions they are working on it: https://www.lineageos.org/Changelog-14/

Doesn't say much for our device, but it's also not even ready yet generally.
[Galaxy S 4 Mini Original Android Development] Abelus:
Hi, I have installed lineage 14, all seems ok except that there a no contacts on sim cards Oo.
[Galaxy S 4 Mini Original Android Development] Claudio4780:
https://www.xda-developers.com/list-android-oreo-unofficial-ports/
[Galaxy S 4 Mini Original Android Development] carpler:
Not found any info about that, so I ask here. Why no nightly this week? Look also for another device (I not remember wich) and seems the same...

Inviato dal mio GT-I9195 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] JohnSoong:
Just downloaded 1001. I guess they are a couple days late.
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
[MENTION=3044346]arco68[/MENTION]

File browser has a problem. When it is on the external storage, it uses the native filesystem instead of the linux fuse. Newly created files have its ownership instead of media_rw:media_rw. Rom is of 170922.
[Galaxy S 4 Mini Original Android Development] Herdkilling:
Does this ROM support in car Android Auto?

I don't have a car to try it. :)
[Galaxy S 4 Mini Original Android Development] MJay99:
On Gerrit I'm seeing commits to a LOS 15 branch by Arco since a few weeks ago... so, guess he's working on it and at least will be attempting the porting :)
[Galaxy S 4 Mini Original Android Development] IronRoo:
Looked at Jenkins on Sunday and there seemed to be problems with all (?) builds… still look like there are problems

https://jenkins.lineageos.org/job/android/

I wonder if this effects other apps & other phones seen quite a few posts about people losing access to external, in recent weeks

Yes, but you need a headunit with Android Auto support and Android Auto installed on your phone (no car? No worries, the phone app will work similar just on your phone as on the headunit, but not great on a small screen) When you get a car I'd also recommend installing AnyAutoAudio if you use a 3rd party music app (side load now required… thanks Google)

https://xdaforums.com/android-auto/android-auto-general/app-anyautoaudio-audio-app-auto-t3607916

& NightToggler to set headunit to day mode even if you turn headlights on as required in many countries so it stops the headunit dimming.

https://play.google.com/store/apps/details?id=gb.aahelper.hr

You can even turn an old tablet into a headunit with this app to connect your phone to..... https://xdaforums.com/general/paid-software/android-4-1-headunit-reloaded-android-t3432348
[Galaxy S 4 Mini Original Android Development] Herdkilling:
Thank you! :)

I didn't know that XDA had an Android Auto forum. :victory:
[Galaxy S 4 Mini Original Android Development] Archiatrus:
Hi,

yesterday my S4 mini (serranoltexx) turned off and I am unable to turn it on again. Pressing the power button does nothing. Connecting it via USB to a charger or the computer does not start the charging animation. adb devices shows an empty list (installed the drivers, Windows 10 (admin)). The only small glimpse of hope is that under devices it shows "Qualcomm HS-USB QDLoader 9008 (COM3)" when I connect the phone via USB. So something must be alive in there. Probably also relevant: no root, usb-debugging most likely off, lineage-14.1-20170922-nightly-serranoltexx-signed installed via the internal updater and TWRP v3.1.1 a week ago.

Maybe somebody has an idea...
[Galaxy S 4 Mini Original Android Development] IronRoo:
I was just about to abort the 1001 ROM download as it was so slow tonight and wait for next weeks when I saw that this release has the Profiles tile in Quick Settings, the one thing I've really missed since CM13. And it also has burn in protection

It's made my day! Thanks a ton [MENTION=3044346]arco68[/MENTION]
[Galaxy S 4 Mini Original Android Development] Brentana:
Hello,

Already posted in another thread, but no one answered, so i try again here, since my problem is the same in both release... my be you are able to help me

i'm trying to increase the call volume, because it seems to me that under some situations it is a bit too low.

Found a trick speaking of changing value in Mixer_Paths.xml, in effect, that works well.

The problem is, i modified some values from 84 to 90, but a lot of things has changed.

What i really need is to increase the volume of the phone when someone call me, not the ringtome, but the remote person voice, and the phone is near my ear, not in speaker phone mode.

Is there someone that can tell the right section to change in Mixer_paths?

Thanks, regads,

Luciano
[Galaxy S 4 Mini Original Android Development] MJay99:
I'd suspect the sudden death that's also been hitting my first S4 mini (only the change of the logic board brought it back to life, which in this model, with a little care and spare part, is rather easy to do). Googling a bit for this back then, I found lots of reports of similar defects in a rather short time-frame, said to be related to the memory.
[Galaxy S 4 Mini Original Android Development] mielletseed:
In my opinion your internal storage has gone completely. Had the same with other phones. What you see is a kind of debug interface when the processor can't start anything else...
[Galaxy S 4 Mini Original Android Development] held600:
Can anybody confirm the following?:

- Define a systemprofile

- setup a WLAN trigger for this profile (on connect)

-> if trigger runs and profile is switched, the home button does not work anymore. Toggeling flight mode solves the issue.

Gesendet von meinem GT-I9195 mit Tapatalk
[Galaxy S 4 Mini Original Android Development] IronRoo:
At last someone else with that problem! I have not reported bug as I wasn't sure if it was due to me using the migration tool, from CM13 to LOS14. I wouldn't want to trouble [MENTION=3044346]arco68[/MENTION] with a "bug" of my own making, I've been meaning to do a clean reinstall for months to check this. Did you use the migration tool at all?

Actually the home button still works, if you double press it, eg it always goes to split screen for me, (which is a bit of a workaround) . But single press does nothing. For me going to flight mode didn't always fix, but going to default profile always does fix, will be a lot easier now with quick settings tile back. Also setting menu key to last app on long press is useful workaround also.
[Galaxy S 4 Mini Original Android Development] iskefiyeli:
1- When update complated root will remove

2-it don not have wifi direct file share

3- wifi connection has disconnecting
[Galaxy S 4 Mini Original Android Development] Kreacher01:
Did this test, home button does still work. Weekly build 2017-09-22.

Did a clean install of official LOS 14.1 some months ago and dirty updates since then.
[Galaxy S 4 Mini Original Android Development] held600:
I installed the OS in the early days with clean Installation. The bug was there, too. Then i dirty flashed updates, currently the Rom running from some days ago.

No use of migration tool.

Gesendet von meinem GT-I9195 mit Tapatalk
[Galaxy S 4 Mini Original Android Development] IronRoo:
OK, good that you did a clean flash, that suggests it is a genuine bug. I will see if I can pull a log sometime.

---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------

What root method are you using?

---------- Post added at 10:20 PM ---------- Previous post was at 10:16 PM ----------

Thanks for testing, much appreciated, however mine is intermittent, some times it works fine, so if you can continue using that trigger & let us know the results after a few days that would be great :svetius:
[Galaxy S 4 Mini Original Android Development] JohnSoong:
Something happened to stop Assistant in latest updates?

When LOS first came out, I had to edit build.prop to get Google Assistant working with each (dirty) flash of a new nightly. Since the official release, I had not have to do that. Google Assistant stayed with each update ..... except for the last few (or maybe more) nightlies. <I am on 1001 right now.>

Now, with each update, I have to re-edit build.prop, flush Google's cache and restart. Otherwise I get the old Now search instead of the Assistant.

Did something changed in the last few builds? Or maybe Google is playing around with things at their end?