yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] ghines:
Hi all,

Each time I flash the latest weekly I reboot and the phone is not rooted anymore. I need to reboot into the Bootloader and flash the SuperSU zip for my phone to be rooted again. Is there a way to make rooting stick between flashes?

TIA

Greg
[Galaxy S 4 Mini Original Android Development] mielletseed:
Hello,

I have a problem with background apps being killed aggressively but that are apps that are expected to run in background, e.g. Titanium Backup, PowerAmp, streaming apps ...

I already configured them as "not optimized" in the battery menu, I tried to "lock" them in the recent apps screen - no luck. They are killed a short time after going into the backround :(

I have an other device running LOS 14.1 and there are no such problems there.

Any suggestions how I can avoid that background apps killing?
[Galaxy S 4 Mini Original Android Development] dav1129:
Cyanogenmod to LienageOS

I have appreciated these forums greatly over a few years now especially since I arrived late to smart phones and got my first one a few years back. It's an S4 mini DUOS which I have really enjoyed with a Cyanogenmod ROM since the beginning. But I ultimately found the limited internal storage a problem until I starting using an App called Link2SD which was great to manage installing apps to the SD card.

I recently tried upgrading from Cyanogenmod 12.1 to 14.1 Cyanogenmod or then LineageOS 14.1. But I found that for some reason Link2SD would not work with these ROMS.

So I'm stuck still happily for now with my S4 Mini DUOS and Cyanogenmod 12.1.

But I am ready I think to ultimately, or perhaps soonish in fact, upgrade to a new Samsung Galaxy. I have never paid ridiculous money for a new phone of bought one outright and certainly not now if I am going to install a custom ROM and void the warranty. So I am thinking a Galaxy S8 is too new and perhaps not supported for LineageOS and so perhaps a Galaxy 7 is old enough to still buy in good condition albeit out of warranty and is perhaps supported by LineageOS. But do I need to pay attention to which model precisely? For example, I think it exists as three models S7, S7 Edge and DUOS. Does Lineage support each model?

This is perhaps no longer the correct thread sorry but it is the one I have become familiar with.
[Galaxy S 4 Mini Original Android Development] Michael24884:
Download the addonsu from the Lineage website, don't use the SUPERSU.zip

https://download.lineageos.org/extras

---------- Post added at 07:21 AM ---------- Previous post was at 07:17 AM ----------

Check your developer options, you might have the background process limit to a minimum
[Galaxy S 4 Mini Original Android Development] mielletseed:
Thank you for your reply. I knew about this but I didn't mention it in my first post: it's set to standard. imho that's the maximum one can set in developer settings ...
[Galaxy S 4 Mini Original Android Development] Dyt199412syam:
Anyone here knows what is "preload" partitition? And then, this rom doesn't support add-on script, right? Thanks for the advance.
[Galaxy S 4 Mini Original Android Development] droopyar:
Hope arco68 release a prebuilt of Android Oreo Lineage 15. Some other devices have this now.

I know it is buggy still, but hope soon arco give us this upgrade :)
[Galaxy S 4 Mini Original Android Development] D4ND310:
I believe the Preload partition is a roughly 200mb area of the device where various built-in System/OEM apps can live/be moved to, to free up some space on the main System partition. Search for "TWRP Preload" for a more concise description, that's what I looked for some months ago when I wondered the same thing. I think it's generally unused by default but it can certainly be utilised.
[Galaxy S 4 Mini Original Android Development] kentchristopher:
I'm currently running CM13 and have had regular GPS/compass problems. (Sometimes it works, sometimes it doesn't.) I'm hoping it's a software issue and upgrading to a newer ROM might solve it -- or maybe reverting to KitKat.

Has anyone else had problems with GPS/compass which this ROM fixed?
[Galaxy S 4 Mini Original Android Development] Daniel78F:
Upgrade from CM13 to LineageOS 14.1

Hello,

on my S4 Mini (serranoltexx) I want to upgrade from CM13 to the latest LineageOS without loosing my settings. As I read I need the experimental version which is not online anymore at the lineage downloads. Do You (still) have it?

Thanks

Daniel
[Galaxy S 4 Mini Original Android Development] madvinegar:
I was always dirty flashing the new updated rom.

I don't know why, but the last roms could not be dirty flashed. After installation, the phone would never boot and was stuck in boot logo.

I had to wipe everything and install rom + gapps + addonsu from the beginning to get it to work.

Anyone else had the same problem?

Is substratum creating any problem...?
[Galaxy S 4 Mini Original Android Development] BOTUS:
Yes my exact issue with 27 Oct file. (reported page earlier) Can't get it to do anything, downloaded file to memory card and ran from there, ran old files, cleared dalvik and cache nothing works

the file hash I find perplexing as well after 3 downloads all the same

sha 1 7AEA6F92E1F5715309A4AFC07B022B652992DCFF

md5 29DE2B7C8D64D271CFF796910B2A8361

crc32 C980D4F2

yet the link says sha256 sha1 (whatever that is ???)

519566187d6a011c52f60215ceeec5fd7f731d7420c0124fe1f81085068708f0 lineage-14.1-20171027-nightly-serranoltexx-signed.zip
[Galaxy S 4 Mini Original Android Development] IronRoo:
you mean using the migration tool? It should work with current ROM, at least it worked for me going from CM13 to one of the early LOS14 which was NOT an experimental build. But keep if mind this is not the recommended way to upgrade and may cause some unexpected behaviors from apps, through I don't think I have had any.

---------- Post added at 12:14 AM ---------- Previous post was at 12:00 AM ----------

I dirty flashed 1027 build all went fine, though I had been clean flashing previous builds for at least a month, since last dirty flash. So problem must gather from earlier build.

Sha256 & sha1 are what has replaced md5, I am using an app from play store to check sha1. It looks like you are trying to check sha256 against sha1, without me actually checking them ass I have deleted download already. This is the sha1 from download page

7aea6f92e1f5715309a4afc07b022b652992dcff

edit: Do you have a TWRP backup over a month old or so? If so flashing that and then the latest ROM might enable you to keep most of your settings.
[Galaxy S 4 Mini Original Android Development] Dr. Slump:
I regularly dirty flash every week, no problems so far.

Might it be about gapps? I don't use it. If anybody who uses gapps reports that it is OK, then this case can be easily discarded.
[Galaxy S 4 Mini Original Android Development] IronRoo:
Could be I guess, for the record I have OpenGapps micro, updated that just a few weeks ago (& TWRP 3.1.0),
[Galaxy S 4 Mini Original Android Development] MJay99:
Been cross-upgrading from cm13 up to los14.1 and dirty flashing ever since including gapps micro - no significant issues.
[Galaxy S 4 Mini Original Android Development] BOTUS:
Thanks for the reply.

I see now there are actually two different links to the file hash. On IE11 it looks like one link (there is no space between them) I just checked, yes the sha 1 shows the file I have and the one you flag. Thanks

I think that's three users saying they have issues now that never saw before. I might try and flash a new gapps micro, then see what happens. I think I'm running TWRP 3.1.0.0 need to check.

wiped by mistake ! flashed gapps micro 1 Nov 2017 and it rebooted as new running 27 Oct 2017 version

wonderful, stupid phone now doesn't have a keyboard and you can't add a keyboard, so completely unable to input ANY info, ridiculous, if one was dumb the phone is now bin material, - defaults to google voice typing with no other one available.... I don't want google to know my voice ever !!!

.
[Galaxy S 4 Mini Original Android Development] Thoadi:
Did updates worked with substratum before?
[Galaxy S 4 Mini Original Android Development] madvinegar:
Yes, but I think that substratum was not integrated into the system before, like it is now.
[Galaxy S 4 Mini Original Android Development] IronRoo:
That is not supposed to be possible see the faq on Opengapps, it says you cannot flash without keyboard app. Try reflash gapps.

(also maybe it's there but you have to activate it in settings, under manage keyboard, though of course normally it's greyed out but it might not be if it has not installed correctly)
[Galaxy S 4 Mini Original Android Development] BOTUS:
thanks for reply,

I'd spent 90 mins looking and trying to get it to work... there was no keyboard once it booted... after flashing 1 nov gapps micro

CRC32: 503FE62F

MD5: 2574A5A76723BADDACCCDDCEFFC0D2BE

SHA-1: 5E6AD5338EF95A34F5EF957FBAE4C9A8F456B5DA

not sure how or why this happened.

the phone and whatsapp was arguing over a gboard issue for months, I had reflashed from a june clean install, to aug and sept versions and got a new gboard from playstore.... but the bug didn't go away.

I went here and got gboard 12 oct 17

https://www.apkmirror.com/apk/googl...909-release-armeabi-v7a-android-apk-download/

not sure how legit that site is, but up and running now that there's a keyboard on the device

weirdly it just updated chrome to 19 Sept, wouldn't that have been in gapps?
[Galaxy S 4 Mini Original Android Development] IronRoo:
new builds for 3G & DS are up since yesterday, but nothing for LTE… looks like build servers are now down :crying:
[Galaxy S 4 Mini Original Android Development] BOTUS:
ooops,

gave her back her phone and she said how do I make a phone call !!!

never noticed this is also missing :) all very strange.

I guess IronRoo was right should have tried reflashing gapps - do you know if I flash gapps again will it wipe out google maps and whatsapp so need to start with them all over again? and should the and phone biit turn up with gapps or be part of the OS ? Added google phone this evening and can make calls - but some buttons are not there like how to start and end a call !
[Galaxy S 4 Mini Original Android Development] Herdkilling:
I've tried Android Auto and it worked like a charm, I'm running 20170428. :)
[Galaxy S 4 Mini Original Android Development] Thoadi:
Just updated to 20171103 but no theme engine.

:(

It's save and work to install substratum from playstore? Is an addon required for LOS?
[Galaxy S 4 Mini Original Android Development] BOTUS:
flashed gapps open_gapps-arm-7.1-micro-20171104.zip, rebooted looked OK

flashed lineage-14.1-20171103-nightly-serranoltexx-signed.zip, rebooted and worked this time.

I see it now has 10 more gapps than it did when I'd flashed it last round both times using Micro !!!
[Galaxy S 4 Mini Original Android Development] Fabiofis:
Unfortunately I came back to stock rom, until the screen freeze problem that has been occurring in the last updates for GT-I9192 (serranodsdd) is solved, as reported in previous post.

Thanks for building this rom!
[Galaxy S 4 Mini Original Android Development] ghines:
Should I uninstall SuperSU before installing the addonsu or should I install the addonsu over the top of SuperSU?

TIA

Greg
[Galaxy S 4 Mini Original Android Development] carole.schummer:
Low Overall Volume Ouput

Hi,

I have a S4 Mini running Lineage 14.1 serranoltexx nightly 20171013.

It is running very good, so first of all THANK YOU VERY MUCH.

One thing though; I was wondering if there was a way to invrease the volume outcome mainly for listening to music the sound overall is pretty low trough the speakers, headphones and even my JBL Flip 2 which works vvery good and loud with other Devices. This happens with plugged in Aux or via bluetooth or with only the devices speakers.

I hope someone can help me! Cheers:)
[Galaxy S 4 Mini Original Android Development] ghines:
If someone could let me know how to replace SuperSU with addonsu it would be appreciated.

TIA
[Galaxy S 4 Mini Original Android Development] D4ND310:
Hi. There's an option in SuperSU named(similar to) 'Clean-up to switch to a new SU app'.

If you use that first, you'll be asked to reboot afterwards and SuperSU's Root functionality should be uninstalled.

After confirming you've cleaned up SuperSU, reboot to Recovery and flash Lineage_addonsu_xx.x.zip.

On reboot to System, you'll find the new Root enable/disable options, with a shortcut to Privacy Guard's Root Access tab for any Root request apps beneath, in your Developer Options.
[Galaxy S 4 Mini Original Android Development] ghines:
Great!!! Thanks heaps.

Greg

---------- Post added at 08:48 AM ---------- Previous post was at 08:23 AM ----------

Have enabled root in Developer Options but "Manage Root Accesses" is greyed out. Is this normal?

TIA

Greg
[Galaxy S 4 Mini Original Android Development] D4ND310:
Have you opened an app that requests Root access yet?

There may be nothing to list, if a request has not yet been made.

You'll only see apps there that have previously requested access so, if none have, nothing would be there to show.
[Galaxy S 4 Mini Original Android Development] ghines:
Yes, have opened Titanium Backup (says root access granted), Tasker and several other apps that need root. All is working OK, just that you cannot see what apps have been granted root as it is greyed out.
[Galaxy S 4 Mini Original Android Development] D4ND310:
That's odd. I've never had any issues after flashing the addonsu file.

What happens if you visit Settings >> Privacy >> Privacy Guard >> Advanced. Do you see the right-most Root Access tab there?
[Galaxy S 4 Mini Original Android Development] ghines:
No, the Root Access tab is not there.
[Galaxy S 4 Mini Original Android Development] D4ND310:
Hmmm, the last option I can think of is to open Privacy Guard and scroll to a known Root access app, long-press on the entry to open the full Appops toggles for the app and check whether the final option is the Root Permission dialogue.

Failing that, I can only hope that someone else reading has had/solved the issue and can advise you further on how to correct it. Good luck. ?
[Galaxy S 4 Mini Original Android Development] ghines:
There is no Root Permission dialogue at the final option. Thanks for your help.
[Galaxy S 4 Mini Original Android Development] Michael24884:
try settings the Root Access to : Apps and ABD
[Galaxy S 4 Mini Original Android Development] ghines:
Changed to Apps and ABD | rebooted. No difference "manage root accessess" still greyed out.
[Galaxy S 4 Mini Original Android Development] Michael24884:
Can't help much as I uninstalled su and switched to Magisk.

But try flashing the su remover from the lineage website and reflashing the su. That's all I got left
[Galaxy S 4 Mini Original Android Development] ghines:
OK, finally got this working by installing the latest nightly | rebooting | installing the addonsu.

Got 2 issues now:-

1. The apps being granted su access are not being remembered between reboots.

2. How do I remove the hash from the notification bar?

TIA

Greg
[Galaxy S 4 Mini Original Android Development] madvinegar:
[/COLOR]

Check this link

https://xdaforums.com/android/general/how-to-remove-superuser-indicator-cm13-t3490425
[Galaxy S 4 Mini Original Android Development] Kreacher01:
Build schedule has been rebalanced this night, serranoltexx will be build on Thursday now like the other Serrano versions instead of Friday.

So no new build today, next build will be on Thursday, November 16th.
[Galaxy S 4 Mini Original Android Development] BOTUS:
I was wondering, does the radio/modem only get flashed by a separate process?

https://xdaforums.com/showthread.php?t=2545784 here was an old post on how to do it, but not sure if its part of this linage update?

I'm on baseband 19195XXUCOD3 which doesn't seem to be any listed in the link, I'm in the UK its running on EE
[Galaxy S 4 Mini Original Android Development] syslog:
Is the missing alarm already fixed in the official builds at https://download.lineageos.org/serranoltexx ???

The link at mediafire says: Invalid or Deleted File

PS: I have an old build apparently with the alarm problem, and I'm looking for any possible ways to fix it.
[Galaxy S 4 Mini Original Android Development] Thoadi:
Yes...

https://xdaforums.com/galaxy-s4-mini/general/modem-samsung-galaxy-s4-mini-gt-i9195-t3390780/page15

See page 1 for manual with odin... You may have to change provider settings, like APN...
[Galaxy S 4 Mini Original Android Development] atsiz77:
I have activate Root ADB and APP but I have not Root access?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, it was fixed ages ago, just flash a recent build

---------- Post added at 12:08 AM ---------- Previous post was at 12:02 AM ----------

Did you flash the right suaddon? It's the first one in this list for arm based devices for LOS14

https://download.lineageos.org/extras

If wrong or not installed properly use the su remove tool & try again, whatever should fix.
[Galaxy S 4 Mini Original Android Development] atsiz77:
Thanks that was missing, now it works. But sometimes another question asks how do I have to make an online update? If I've downloaded an old nightly, just about normal recovery?
[Galaxy S 4 Mini Original Android Development] BOTUS:
thanks very much,

so you download a whole rom, break it open and modem locks to specific provider?

or use the one on the first page which is very latest for Norway (but should work)?

so there are ones 2 years newer... 50 meg seems a lot, is that normal on this phone?

not sure what APN is?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Yes, flash it with TWRP

( OTA will notify you when a new update is available, normally you can install from there, but currently it's not working And you need to find the file (search this thread for location) & flash manually. Personally I just go to website & download it to download folder, boot to TWRP & flash from there (I also check sha with an app))

---------- Post added at 01:00 AM ---------- Previous post was at 12:48 AM ----------

You can download a whole stock ROM and extract the modem but easier just to use the ones redyamesg already extracated, just flash his tar.md5 files with Odin (2x so it sticks as per his instructions ) edit: yes Norway xx modem will work on xx phone, I'm using it in Australia

Edit: Use this app (&/or TWRP) to back up your current Modem imei efs before flashing , & Copy it somewhere safe, might just save you a lot of trouble one day !

https://play.google.com/store/apps/details?id=ma.wanam.efs
[Galaxy S 4 Mini Original Android Development] Thoadi:
I use the extracted one from norway in switzerland, it works so no need to update now. But newer version are available...

APN are the settings for mobile internet accsess: settings -> more -> mobile settings -> APN

Check if the mobile internet access don't work... because norway operator settings. This may be fixed in the new LOS builds...
[Galaxy S 4 Mini Original Android Development] BOTUS:
cheers Thoadi and IronRoo

your patience helping us noddies is very useful

:)

noddy -definition

Someone who lands him/herself into difficulty through acts of sheer stupidity, possibly without even realising they have done anything wrong.

All done, wifi is lightning fast now, phone worked, all looking good. battery was dying in 4 hrs so will see how that goes now.

Its running I9195XXUCQG1
[Galaxy S 4 Mini Original Android Development] gostela:
I'm facing the following problem with my Samsung S4 Mini.

If I flash Lineage OS 14.1 everything works perfectly.

If I flash Lineage OS 14.1 and than the GApps ARM, 7.1 I recieve the following message when I reboot my phone: "Setup Wizard Has Stopped Working" (+ "Google Play Service Has Stopped Working").

The solution described here: https://xdaforums.com/crossdevice-dev/android-one-general/fix-setup-wizard-stopped-t3274219, does not work. I can't enable any permissions for the setup wizard and my home button stops working when I open the settings.

Any idea what I have to do to get the GApps installed together with Lineage OS? Thanks!
[Galaxy S 4 Mini Original Android Development] mielletseed:
You have to flash LOS and gapps in one step without reboot between. When you install gapps after a boot of your device this always occurs (maybe because the other Setup Wizard already ran).
[Galaxy S 4 Mini Original Android Development] gostela:
Thanks - that's exactly what I did - maybe my wording was a little misleading.

If I flash LOS & GApps (without reboot between), I get the error explained above.

If I flash only LOS without GApps, I don't get the error and LOS works fine. But as I need GApps I have to resolve this issue in some way. Any idea?
[Galaxy S 4 Mini Original Android Development] IronRoo:
I think mielletseed is right, it's probably permissions related.

Maybe need to do a factory reset as old permission data is there don't forget to back up your data & media files ie photos, Whatsapp photos etc

See no 10,

https://github.com/opengapps/opengapps/wiki/FAQ
[Galaxy S 4 Mini Original Android Development] gostela:
Thanks for your help.

I did the following:

1. TWRP - Factory Reset

2. TRWP - Wipe of Davlik Cache, System, Data, Cache

3. Flash Lineage OS 14.1 20171103

4. Flash Open GApps nano 7.1 20171112 (arm)

5. Wipe Dalvik & cache

6. Select Reboot

7. Following message appeared:

Install SuperSU?

Your device does not appear to be rooted.

Install SuperSU now?

This will root your device.

I selected: "Do not install"

8. Reboot

But the problem remains the same:

Besides the "Setup Wizard keeps stopping" I recieve the following notifications:

"ConfigUpdater has stopped"

"Google One Time Init has stopped"

"Devices Helps Services" keeps stopping"

+ some more

If I conduct the same steps without flashing GApps, Lineage OS works perfectly. So I have at least an interim solution with Lineage OS without GApps, but would be great to find a way to get the GApps installed.
[Galaxy S 4 Mini Original Android Development] thorium231:
Did you try different gapps-packages, like this one: https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192 ?
[Galaxy S 4 Mini Original Android Development] gostela:
Just tried it. Unfortunately the same error :(
[Galaxy S 4 Mini Original Android Development] D4ND310:
If having no Play Games isn't an issue for you, you might try NanoMOD + MicroG.
[Galaxy S 4 Mini Original Android Development] gostela:
I really would like to have the google Play Store
[Galaxy S 4 Mini Original Android Development] D4ND310:
You can have the Play Store via MicroG. The only thing you won't have access to is Play Games.

Your Play purchases can also be accessed via the modded Play package, included in the full NanoMOD setup. Check it out! ?
[Galaxy S 4 Mini Original Android Development] IronRoo:
I've not used supersu for a while, I guess it needs to be removed before new flash, though I'm a bit surprised nobody else has had this issue (maybe corrupted?) or is everyone else using LineageOS root add-on now! I am. Also you will see other mods like xposed mentioned on previous FAQ link, so uninstall anything that has modified system you may have installed before
[Galaxy S 4 Mini Original Android Development] gostela:
So what else do I need to do before flashing LingeageOS?

I did the Factory Reset & Wipe of Davlik Cache, System, Data, Cache. How can I remove supersu?

---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------

Thanks! I tried it but it didn't solved the problem:

After installation of Lingeage & MicroG, the Lineage works fine and I recieve no error.

But Google Play Store and microG Services Core weren't installed properply. The apps have no icons, only the android icon and when I try to open Play store I recieve the "Google Play Store keeps stopping" error. Same with microG Services Core ("microG Services Core keeps stopping")
[Galaxy S 4 Mini Original Android Development] Mohammed Bhere:
Substratum theme work or not??
[Galaxy S 4 Mini Original Android Development] gostela:
sorry I don't understand what you mean