yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
Yes, it has been an issue for some lineage users here. (I mean physically here, not the forum :)) Disable the home button wake-up property and see if it happens again.
[Galaxy S 4 Mini Original Android Development] echo124:
[MENTION=3044346]arco68[/MENTION] [MENTION=5416372]csendre[/MENTION] is s4 mini capable pf better audio output via bluetooth? Audio on los 14 compared to s4 on los 14 is much more rich, more bass, etc. Is there a way to implement another audio hal?
[Galaxy S 4 Mini Original Android Development] DroidHero2002:
Just flash Dolby atmos.
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
Thanks for the tip it solved the issue pretty well.:good::)
[Galaxy S 4 Mini Original Android Development] echo124:
How is it different than audioFX?:
[Galaxy S 4 Mini Original Android Development] DroidHero2002:
Its a lot louder and clearer.
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
Did you just flash the zip and the issue was gone for good? This is still my main problem with the builds. I can't afford to miss overnight alarms anymore! Plz help
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
I have the same problem, did you fix it with the zip Arco provided?
[Galaxy S 4 Mini Original Android Development] equaeghe:
flip cover functionality not working

Hi, I'm on 14.1-20170615-NIGHTLY-serranodsdd and have a flip cover, but not of the S View type. I have activated the flip cover feature, namely to activate the lock screen when opening and shut off the screen when closing. However, this does not work, at all, i.e., the phone does not react in any way to the flip cover closing or opening. Is there some other setting that I need to change or is this functionality only available for the S View type?
[Galaxy S 4 Mini Original Android Development] devilhopper:
Er... says who? Link2SD has worked for many years without a native filesystem, and the app hasn't changed. So if it is indeed true that a native filesystem is requirend now (is it really?), that still bears the question why? Some fundamental change in Nougat or Marshmallow? Or, after all, a bug in Lineage, or it's implementation for the S4 Mini?
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
That was a guess, I should have said that. It is true that link2SD can work with FATFS, what I have said on previous post is wrong.
[Galaxy S 4 Mini Original Android Development] sej7278:
yes both kernel.zip and kernel2.zip fixed it for me, no need for deskclock.zip
[Galaxy S 4 Mini Original Android Development] Alex-71:
I had no more alarm issues since i flashed the zip and it's been a month now.

Compared to the frequency of issues i had before, i would say the fix has an effect.

I think you can give it a try (and keep a second alarm clock just for the case..)
[Galaxy S 4 Mini Original Android Development] eriksson25:
Just wanted to Thank you. I have not managed to unpack my boot.img and edit the init.rc, rapacked and flashed.

It almost works. It starts the boot, but the bootanimation continues forever. I have tried some diffrent commands but not found anything working yet. You have any more tips?
[Galaxy S 4 Mini Original Android Development] Doupas:
Hi mates

There is a solution to make the sdcard writable?. Unless of course I do it internal.

Best regards
[Galaxy S 4 Mini Original Android Development] carpler:
Can you tell me what's the right file to flash on Lineage 14.1?

Found several thread and files here on xda...

Many thanks!
[Galaxy S 4 Mini Original Android Development] DroidHero2002:
Just get the latest version. If it don't work use v4a.
[Galaxy S 4 Mini Original Android Development] Olfason:
you can access and write sdcard with a root file explorer via mnt/media_rw/xxx...

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

you can access sdcard via TWRP

:fingers-crossed::good:
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
Yes, it happens like you said... I tried to make it to mimic the power button press when charging, but even if it booted nicely and made the lock screen, the touch screen didn't function normally, so I abandoned this idea.

Another idea, I tried it and works but I take no responsibility:

1- In init.qcom.power.rc file delete the on charger section.

2- In init.rc file delete the on charger section. Instead, write:

on charger
write /proc/sysrq-trigger b

note: I tried the built-in powerctl command of init, it would be very useful if one would want to boot into recovery (in the case of broken keys) but it didn't worked. Later I will look for that again.

note2: People who want to learn about init and another android internals may go to the site: http://newandroidbook.com/ and download the book which is "right there".
[Galaxy S 4 Mini Original Android Development] IronRoo:
I think this was incorporated into the current rom a few weeks ago. Though not certain.

edit: [MENTION=6921398]equaeghe[/MENTION] I think I misunderstood you. You mean you were able to get the flip settings to show with the cover which is NOT the s-view type cover. Then that cover must have magnets in it to activate it. So it should be able to get the pin lockscreen to show, I can get it to work on my I9195 using a magnet. (though it doesn't go to pin enter screen if you press power button to turn screen off just before).

If it's not working then maybe there are no magnets in your cover?
[Galaxy S 4 Mini Original Android Development] eriksson25:
Had to try this before going to work this morning, AND IT WORKS!!!! Thank you so mutch!

Yesterday I tried alot of diffrent ways myself, like emulating the power button press but got no where. So thank you!
[Galaxy S 4 Mini Original Android Development] eltano06:
do i have to reflash gaaps and root after update
[Galaxy S 4 Mini Original Android Development] fahrer17:
No
[Galaxy S 4 Mini Original Android Development] sej7278:
well yes if you wiped /system
[Galaxy S 4 Mini Original Android Development] fahrer17:
Ok, but that's not what I call an "update"... :D
[Galaxy S 4 Mini Original Android Development] sej7278:
i do that with every upgrade, otherwise you could pollute /system and end up with a *really* dirty flash
[Galaxy S 4 Mini Original Android Development] D4ND310:
Not necessary, /system is wiped in the very process of flashing an update of your ROM, naturally.

Your optional root and Gapps(if you're "into that kind of thing"! ?) will be preserved over upgrades via your addon.d/.sh files.

What you need to watch out for for "polluting" your upgrade is rather /data, for instance, you may have an active kernel scaling app' set up to start at boot and your update may include a new kernel that is incompatible with its loaded /data parameters. Always default your scaling governer before upgrading in such cases or, you'll find a full wipe and fresh installation is necessary.
[Galaxy S 4 Mini Original Android Development] sej7278:
yeah i was wondering if it did that these days.
[Galaxy S 4 Mini Original Android Development] D4ND310:
Haha, I talk from bad experience. I've upgraded LOS forgetting I had previously set a scaler to run at boot for a custom kernel. It was underclocked to below the default LOS bottom frequency and continually looped on boot up. Wiping /data obviously fixed it and I keep a data backup but I could have saved myself an headache with a little forethought. ;)
[Galaxy S 4 Mini Original Android Development] sej7278:
yes looks like the stock kernel in the rom is the same as kernel2.zip now (different to kernel.zip)

changes seem to be that kernel.zip had:

CONFIG_RTC_INTF_ALARM=y

CONFIG_RTC_INTF_ALARM_DEV=y

# CONFIG_ANDROID_INTF_ALARM_DEV is not set

but kernel2.zip (and stock) instead has:

CONFIG_ANDROID_INTF_ALARM_DEV=y

oddly enough the kernel in 06/30 seems to be the same as 09/08 so i guess something in between broke alarms and its just been reverted, but there's been no commits to the kernel source since 06/29, but all kinds of alarm commits before that since january
[Galaxy S 4 Mini Original Android Development] akoine:
As promised, an update :

Installed lineage-14.1-20170908-nightly-serranoltexx-signed.zip this morning : flashed it, then wiped cache and Dalvik.

No problem, so far so good !:D

Thanks again for your help !
[Galaxy S 4 Mini Original Android Development] sej7278:
getting "cannot connect to camera" errors from 09/08, rolled back to a backup of 08/25 and its working again.
[Galaxy S 4 Mini Original Android Development] equaeghe:
The flip cover settings are available no matter what cover is or isn't attached to the phone. However, they do not have any effect. I tried with a magnet, but that didn't work either. I used the same (“strongest magnets in the world”) to see if there is a magnet in the cover and this does not seem to be the case. I'm currently assuming this is an S View cover-only feature.
[Galaxy S 4 Mini Original Android Development] jigs4wkiller:
Can someone please upload me the build.prop from this rom?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Once the flip cover settings have been turned on, yes, they are always available after that, even if you don't have a cover on. But the settings have to be activated with a magnet the first time, so you must have once put a cover with magnet on your phone with LOS14 ROM. As you can't detect a magnet in your case this is why it does not work, I think only flip covers likely have magnets. You should be able to use a strong fridge magnet 1/2 way up the left side of phone to simulate flip cover working, if you want to test, like I can.
[Galaxy S 4 Mini Original Android Development] Michael24884:
Im wondering if there's ever a chance that the S4 mini Sprint variant will ever get a Lineage Os rom...
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Where do I find these settings?
[Galaxy S 4 Mini Original Android Development] IronRoo:
The "flip cover" heading will be the next heading under the "buttons" heading in settings but that line will only appear after an S-cover case with a magnet in it has been fitted and opened and closed, thus activating the extra settings, as per Arco's earlier post. (but you can just use a magnet 1/2 way up the left side of phone like I did, leave it in place for a few seconds so it's detected, note weaker fridge magnets didn't seem to work, but a stronger one did, though maybe I just wasn't positioned directly over the Hall sensor)
[Galaxy S 4 Mini Original Android Development] ciccillover:
I am trying to install LineageOS 14.1 on a GT-I9195 (LTE version), but I'm stuck at the initial steps. The phone works perfectly (except for the digitizer) with the stock ROM/recovery, with TWRP 3.0.2 and CWM flashed through ODIN, but it just refuses to work with TWRP 3.0.3 (flashed through ODIN) and 3.1.1 (flashed through TWRP 3.0.2 using a Y cable and an USB mouse). After installing and rebooting, if the key combo for recovery mode is pressed, the device will display "Booting recovery" (or something) on a blue line as usual, but then, after a while:

- resets to a black screen

- vibrates once and pauses for a few seconds (as if it were trying to boot but failed)

- vibrates again and displays the Samsung S4 Mini boot logo with no blue line about booting recovery (as if it were about to start Android).

The same happens if I flash LOS through TWRP 3.0.2 and try a normal boot

The phone works fine with TWRP 3.0.2 and CWM flashed through ODIN (and of course with the stock recovery).

Am I missing anything?
[Galaxy S 4 Mini Original Android Development] Claudio4780:
Thanks, managed it with a fridge magnet. Unfortunately it does not work with my flip cover itself.
[Galaxy S 4 Mini Original Android Development] equaeghe:
The same here. I'm going to try and find out whether this is actually a flip cover feature or an S View feature (flip covers with a window). In case it is the former, we probably have a counterfeit (mine looks very legit, however). In case it is the latter, perhaps the option should be renamed to ‘S View’.
[Galaxy S 4 Mini Original Android Development] jigs4wkiller:
No? No one can Upload me 20kb file?
[Galaxy S 4 Mini Original Android Development] IronRoo:
I think Lineage can't use the name "s-view" as it is trademarked so they call it "flip cover" but it's intended to be the same, so we need an s-view cover for flip cover to work. But it is a bit misleading I suppose.
[Galaxy S 4 Mini Original Android Development] sej7278:
gist
[Galaxy S 4 Mini Original Android Development] powwow12:
Is it dangerous to leave SELINUX always on "permissive" ? I have absolutely no idea about the implications, and it's currently the only way to keep viper4arise working
[Galaxy S 4 Mini Original Android Development] ciccillover:
No one can help?
[Galaxy S 4 Mini Original Android Development] ZeroPointMax:
Sorry, not really xD

Maybe your device had a problem with the y cable. Maybe try flashing TWRP 3.1.1 through Odin?
[Galaxy S 4 Mini Original Android Development] bierma32:
[MENTION=2633069]ciccillover[/MENTION]

Are you sure that you installed the right Version for S4mini .

If got the 3.1. of TWRP installed, all works fine.
[Galaxy S 4 Mini Original Android Development] guglicap:
Hi, I'm considering installing this on my mother's phone, could you please tell me all the known bugs?

Also how smooth is it, considering this is a pretty old phone?

Thanks
[Galaxy S 4 Mini Original Android Development] ciccillover:
Pretty sure. Can you please point me to a recovery image that's proven to be working on a 9195?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] RedSkull23:
ne0zone75's tryout one works flawlessly, you can find it here https://www.androidfilehost.com/?fid=673368273298961086 it's a 3.1.1-0 version, i used to do everything with it when i had my i9195 and it never missed a shot
[Galaxy S 4 Mini Original Android Development] ciccillover:
Thank you so much, I will try it right away

EDIT: sorry, I didn't realize I had already tried that with no luck. I am flashing it from an existing (and the only working one at the moment) TWRP 3.0.2
[Galaxy S 4 Mini Original Android Development] rho-bot:
Have you flashed the recovery via ODIN?

I am also using ne0zone75's stable 3.0.2.1 without any issues. https://www.androidfilehost.com/?w=files&flid=33684

Also please recheck the phone ID by the sticker below the battery. GT-I9195i is not GT-I9195
[Galaxy S 4 Mini Original Android Development] RedSkull23:
No dude you have to flash that via ODIN
[Galaxy S 4 Mini Original Android Development] ciccillover:
How do you flash a zip (or the img file inside the zip) via ODIN? The version I'm using will only accept tar and tar.md5 files...

EDIT: I have flashed this one (this is ODIN flashable for sure, since it's in .tar.md5 format)

https://www.androidfilehost.com/?fid=529152257862709827

But no luck yet, still the same odd black screen + vibration + reboot to OS

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] rho-bot:
seems the Recovery doesn't fit your phone...

please provide the phone ID by the sticker below the battery
[Galaxy S 4 Mini Original Android Development] ciccillover:
GT-I9195

SSN: I9195GSMH

FCCID: A3LGTI9195

May the broken touch panel hinder the bootability of a recovery image?
[Galaxy S 4 Mini Original Android Development] rho-bot:
[MENTION=2633069]ciccillover[/MENTION]

Thanks for providing the label data, its the same as on my device, so we can exclude the phone type: It is the serranoltexx.

As said, I am using ne0zone75's stable 3.0.2.1 without any issues. https://www.androidfilehost.com/?w=files&flid=33684

On your device, I understood you are not able to successfully boot into Recovery (>3.0.2) and LOS14.

Did you try without SDcard placed? I know there were some mounting issues with encrypted SDcard. Maybe thats the blocking point...
[Galaxy S 4 Mini Original Android Development] ciccillover:
Thanks for your willingness to help. I am already doing everything without a MicroSD.

Are you able to flash and boot LOS 14.1 from TWRP 3.0.2.1?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] MaGu1000:
Hi

first of all: The LineageOS serranoltexx is verry great

1.) I updateted to lineage-14.1-20170915 on my I9195 and find a small issue:

The name of the externel SD-card changed to 'M-2M-[^E'. Is there a easy way to change the name?

2.) Is there a way to find out which safety patch date are implementet in the builds before donload?

Thanks in advance
[Galaxy S 4 Mini Original Android Development] RedSkull23:
Hi, dunno for the 1st question but it should be adjustable somehow. For the 2nd question, the builds always have the latest patch included, so except for builds that come out on a day of the month BEFORE the 5th, you'll always have latest security patch.
[Galaxy S 4 Mini Original Android Development] MaGu1000:
The security Patch Level is still 05.Aug.2017 listed in the last build 15.Sep. Is bis so OK?
[Galaxy S 4 Mini Original Android Development] RedSkull23:
Strange, the patch came out as always on September, 5th - https://source.android.com/security/bulletin/2017-09-01 - dunno why it isn't implemented yet... At this point, an answer by arco68 could clarify things.
[Galaxy S 4 Mini Original Android Development] Thoadi:
To 1) you looky, my SDCard (f2fs formated) is namey '05681132-a24c-4866-be4f-e916ed5c4c..' and didn't found out how to rename... But not a big deal, as in the file manager the name to access is 'sd_card1'
[Galaxy S 4 Mini Original Android Development] rho-bot:
LineageOS has a CVE tracker page, see https://cve.lineageos.org/android_kernel_samsung_msm8930-common

At least on Kernel level not every issue may have been fixed...

---------- Post added at 09:24 PM ---------- Previous post was at 09:17 PM ----------

Yes, have no issues for flashing via TWRP.

As the SDcard can also be excluded, I am running out of ideas.

Maybe the broken touch (or additional defects) are causing issues with your device?

Have you tried to go back to factory stock rom via ODIN?

Maybe then you can check with logcat if there are some additional HW errors reported...
[Galaxy S 4 Mini Original Android Development] Alex-71:
[MENTION=3044346]arco68[/MENTION]

Could you please confirm that flashing kernel2.zip is no longer necessary?
[Galaxy S 4 Mini Original Android Development] ciccillover:
Reverting back to the stock rom seems to work fine. Seems, because with a broken touch panel I can't do anything. All that I manage to see is the initial setup wizard.

I will try to logcat

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] flashviking:
Observations and feedback on 20170915 nightly

Hello,

Have been running LOS14.1 on this one since clean install 20170728 and had issues with wifi on that one and 20170908.

Now it works since the update this morning although I see there is a broadcom wifi-update coming with next build. I'm very happy wifi now works!

No feedback except this: Awesome work, contributors! Keep it up and I am looking forward to LOS15 Oreo!
[Galaxy S 4 Mini Original Android Development] iskefiyeli:
how to change Permission of extsdCARD? wifi transfer not work
[Galaxy S 4 Mini Original Android Development] ciccillover:
Gone back to a stock rom and the phone has started correctly, but since it was freshly installed after a full wipe, of course debug was not enabled, and since my touch panel is broken, I have no simple way to enable it and extract logs... Correct me if I'm wrong.

I could install a modified kernel with OTG, but to do so, I would have to downgrade to 4.2.2 first.

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] rho-bot:
You may try to use an ext. mouse as input device ;)

https://www.androidphonesoft.com/resources/enable-usb-debugging-android-broken-screen.html
[Galaxy S 4 Mini Original Android Development] BOTUS:
Hi, I put on the current build as of 1 sept and the camera is playing up and red blue lines/ coloured streeks run through skype video.

Saw was 15 sept build now out, downloaded, but download was interrupted / stalled a few times, at the end said checking download seemed OK ran the file and it booted in to twrp but no file just the last two earlier version I'd used... Rebooted and deleted 15 sept version and one from earlier to free up space.. re downloaded 15 sept cleanly ... as you run the file I can't remember how long it should take before it boots in to twerp? but progress bar on second time showed progress nicely up to 12 % then very quickly rebooted in to twrp and again in data/data org.linsages etc. the 15 sept file is again not there

any one explain why please ?
[Galaxy S 4 Mini Original Android Development] ciccillover:
Stock rom doesn't support OTG

Inviato dal mio LG-D855 utilizzando Tapatalk
[Galaxy S 4 Mini Original Android Development] IronRoo:
I can't explain why, apart from maybe corrupted data in updater app, you could try wipe the updater app data in system apps. (edit: see next post) Or I suggest you go to LOS website & download it manually & flash it with twrp from download folder.
[Galaxy S 4 Mini Original Android Development] MJay99:
I see the stalling and interruptions also - usally needs about three attempts to download it fully.

As for the file, it's not under /data/data/... anymore, but you'll find it under /data/lineageos_updater now.
[Galaxy S 4 Mini Original Android Development] playboicartii:
anyone getting error 7 in twrp ?
[Galaxy S 4 Mini Original Android Development] rho-bot:
Sorry, missed that :D

So only option is to try different kernel with adb enabled, or flash working TWRP (which should have adb support) and try to enable adb for ROM via Recovery (see post here)

---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------

Error 7 usually happens when you try to flash a ROM not fitting your phone.
[Galaxy S 4 Mini Original Android Development] dorpm:
Auto-update not working?

Under Settings -> About this phone -> LineageOS-Updates it is possible to download an update.

Then after downloading the update it is also possible to start the process. A message comes up saying that the phone now will restart in recovery mode. This works really good but after the phone has entered the recovery mode nothing happens.

I have TWRP 3.1.1-0-0 installed.

Any idea?
[Galaxy S 4 Mini Original Android Development] M1chiel:
Click Install and find the update in the /data/lineageos_updater folder. After installation reboot to system.
[Galaxy S 4 Mini Original Android Development] dorpm:
Works perfect, thanks for the tip!
[Galaxy S 4 Mini Original Android Development] BOTUS:
wow, thanks. file in there and worked. 2 weeks ago it was in data/data/org.linageos....

how were we supposed to know it moved?
[Galaxy S 4 Mini Original Android Development] MJay99:
It was mentioned in the changelog and commits of one of the last updates. But agree, not too easy to catch.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, it was mentioned before but I had forgotten until [MENTION=8222739]MJay99[/MENTION] posted. Neozone just posted on TWRP thread that he well go on holiday but will look at automatic update for our device when he comes back, maybe with the latest updates to the updater automatic updates can be fixed ;)
[Galaxy S 4 Mini Original Android Development] BOTUS:
15-09 build she reports camera in Skype / WhatsApp is better... with the streaks being narrower but still present red and blue
[Galaxy S 4 Mini Original Android Development] devilhopper:
Any update on this? As GPS is one of the most important functions for me, I find this terribly frustrating. Even worse than taking several minutes to find the position, it typically just doesn't update the previous position so if you do get some info, you still can't rely on it.

Btw. how do I report bugs for this particular build? I've tried several channels, but in this thread bugs typically get lost in the noise. On the lineageOS website, submitting new bugs currently isn't possible (no clue why) and on reddit, it's simply impossible to get any meaningful communication on a specific build (as the whole subreddit is for lineageOS in general).

Thanks!