yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] Claudio4780:
After dirty flash and migration usage the battery icon was selectable. This morning after a clean flash incl. open_gapps-arm-7.1-nano-20170429.zip there is no option anymore to choose battery display icon.
[Galaxy S 4 Mini Original Android Development] Andi46:
Magisk (+passing SafetyNet) is possible, supersu also should function... REALLY REALLY NICE :good::D
[Galaxy S 4 Mini Original Android Development] csendre:
No such problems here. This is on a clean flash with opengapps pico. Wipe your partitions and try again
[Galaxy S 4 Mini Original Android Development] BOTUS:
You could use the official build instead. See first post.

good advice, thanks ! I just put on

lineage-14.1-20170428-nightly-serranoltexx-signed.zip

open_gapps-arm-7.1-stock-20170430.zip

clock is working and both builds are a bit newer :)
[Galaxy S 4 Mini Original Android Development] waldfee:
I'm trying to get an I9195 LTE with CM13 updated to the latest Lineage 14.1 using the migration script and TWRP 3.0.3 (3.1.0 doesn't seem to start on my device). When flashing it does the migration script, then on falshing the lineage ROM it seems to be stuck at about 30% of "patching system image unconditionally". Anyone seen the same and knows a way to work around?
[Galaxy S 4 Mini Original Android Development] RedSkull23:
I'm on CM13 last snapshot; i wiped dalvik, cache 'n system from the recovery and then i tried a clean flash of the first official nightly by arco downloaded by lineage site (lineage-14.1-20170428-nightly-serranoltexx-signed) on my GT-1915 by TWRP 3.0.2.0, immediately after i flashed the open_gapps-arm-7.1-pico-20170429 package, and last i flashed the addonsu-arm-signed package.

The result has been that i've got stuck on bootloop, so i've came back to a backup of CM13. The only bizzarre thing that i've came in, during the final phase of the flashing process, was a couple of errors listed as here;

[COLOR="Red"]E:unknown command [log]
E:unknown command [log][/COLOR]

I've read from a reddit thread found by writing on google "[e] error unknown lineageos" that it is simple an ignorable error, and that it shouldn't affect nothing. Probably a simple mistake in the code, nothing more.

I've just followed the usual rules 'bout flashing a rom via recovery, so the question is: am i doing somethin' wrong? Maybe flashing the addonsu-arm package AFTER the first boot and not meanwhile the flashing of the other 2 packages could change something? Or i could have to wipe somethin' else..? Thanks in advance :)

EDIT cause big doubt; the TWRP recovery 3.1.0.0 could be a solution? Maybe my 3.0.2.0 couldn't be able to flash LineageOS 14.1 rom correctly cause an out-of-date situation? Givin' a try as soon as I can.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
Migration from [TEST] to [Official]

Happy to report that my migration from 14.1 [TEST] to Official build went mostly without a hitch.

I flashed the migration zip, followed by the Official ROM, then the su addon.

I had the 2 "unknown command" errors just like the poster above, but the ROM installed and everything seemed to be working fine.

All my apps and settings were intact. (I had to re-edit build.prop for Assistant to work, but that is expected.)

Thanks to Arco68 and the dev team!!!
[Galaxy S 4 Mini Original Android Development] Bernd.Defy:
Got the same messages, i think it's the older TWRP-Version you use.
[Galaxy S 4 Mini Original Android Development] JohnSoong:
I am using TWRP 3.0.2-1 and the migration went perfectly.

However, I was migrating from LOS 14.1 to the official build. I believe that is what the migration tool is supposed to do.

When I went from CM 13.0 to LOS 14.1 I need to do a clean install (factory reset first, then reinstall Gapps, etc after the ROM.) I would think that is what you need to do. I don't think you can migrate from CM to LOS using the migration tool.

On some devices, there are official builds that can migrate from CM 13 to LOS 14.1 (they are labeled experimental in the LOS download site.) However, I cannot find that for the S4 mini ... so a clean install was the only option.
[Galaxy S 4 Mini Original Android Development] Bernd.Defy:
04-28 nightly: Bluetooth Tethering and flipflap not working

Like in the latest unofficals, following issues on my dirty-flashed i9195:

* Bluetooth Tethering not working (worked in 03-13-unoffical)

* Flip-Case-Support missing (also worked in 03-13-unoffical)

As i always did a dirty flash, i don't know, if a clean install prevents the bluetooth-problem. Flipcase-Support is reverted (no flipflap.akp in system), does anybody knows the reason why?

No other issues, quite good ROM, use it as a daily driver. Hope that bluetooth tethering will work again...
[Galaxy S 4 Mini Original Android Development] JohnSoong:
If you dirty flashed, you should not have to flash Gapps after the ROM, as all the apps and data are still intact. You can of course flash a different Gapps package on-top of a pre-existing one. I have not done this enough to tell if it would remove apps when you flash a smaller package on top of a larger package.

If you haven't tried this, maybe try uninstalling the app from the play store on a computer. (Log on to your account on the play store, should see your list of installed apps. You can push the uninstall from there. Also can push installation of apps from a computer as well. I find working on the computer much faster than from the phone.)

Also, try dirty flashing a bigger Gapps package (or even aroma with just the clock.) Maybe that will flash a clean version on top of the old.
[Galaxy S 4 Mini Original Android Development] Diresh:
Sounds like a bad download, redownload and try installing again.
[Galaxy S 4 Mini Original Android Development] waldfee:
Thanks everyone for feedback and recommendations. I found the issue wich obviously can be called a "user error" since the adoptabe storage didn't have enough free space for TWRP to unpack/operate the image. I went into file manager and freed-up some space, TWR 3.0.3 flashed all files afterwards and so far it looks like 14.1 is working fine for me even though I came from CM13.

Great image!
[Galaxy S 4 Mini Original Android Development] sej7278:
to the couple of people above who seem confused, the migration script is from lineageos 14.1 unofficial to official, not for cm13 to lineageos 14.1 which obviously won't work without a clean install wiping /data (not dirty)
[Galaxy S 4 Mini Original Android Development] IronRoo:
True ........ but it's worked for multiple people without a clean install!!! :cowboy:

(Edit: though of course it may cause strange issues in the future .....)
[Galaxy S 4 Mini Original Android Development] RedSkull23:
Tried again with TWRP 3.1.0.0, no errors and everything went fine... Testing it a lil' bit, still no bugs for now. Really a good work
[Galaxy S 4 Mini Original Android Development] orsmes:
#1085

i have a same error 7 when i upgrade lineage os 14.1 from unofficial to official with twrp 3.0.3. My device is gt-i9190.
[Galaxy S 4 Mini Original Android Development] sej7278:
i've got a new router so it could be that, but is anyone else seeing on the official build that they can't get 150mbps wifi 5ghz connections anymore? my phone is only getting up to 135mbps
[Galaxy S 4 Mini Original Android Development] benboggart:
Unable to disable 2nd SIM in i9192

First off: Thanks to arco68 and csendre for keeping our phones alive. Because of you guys, I just purchased a "new" one since none of the modern phones fits my requirements for size, dual-sim and modern OS!

My question: Is there no option in LOS to turn off either SIM? I assumed that would be a given for any phone with Dual-SIM, as it was included in any stock OS I've used so far. I found several people asking for the same regarding CM on other devices, but didn't come across a useful answer.

I find that to be a very essential function in my previous phones, be it for travelling or for separating private from professional availability.

Ben
[Galaxy S 4 Mini Original Android Development] RedSkull23:
That should be the install script of the rom, wich uses a log function not present in that version of TWRP. Logging here is not usually necessary, so you can easily ignore it.
[Galaxy S 4 Mini Original Android Development] orsmes:
do you mean that the second and third lines of the rom which are about aspects? if yes. i deleted them and tried to installed again but it didn't work.
[Galaxy S 4 Mini Original Android Development] arco68:
com.google.android.deskclock is the package name for the clock app included with LineageOS. It's not possible to uninstall or upgrade it since it's stored in the read-only /system location. Only option is to delete the apk manually as root, or replace it with an apk with the same name. After deleting the apk, you should be able to install any app with the same package name.

Why it doesn't show up in the app drawer for you, I don't know.
[Galaxy S 4 Mini Original Android Development] christiangre28:
After some days of use the official has a bit worse performance in comparison with the last unofficial build,plus I can't get root access.And last one the battery consuption is bad.Anyone help me fix this.i did a clean install of the nighty and I have this problems so far

Edit:I installed the rootkit for the phone nothing happend
[Galaxy S 4 Mini Original Android Development] arco68:
Bluetooth tethering works here. Tested it yesterday.

Flip case is not there, because for our device we need a patch which has not been merged in official sources.
[Galaxy S 4 Mini Original Android Development] arco68:
Might be a selinux denial preventing the apps to read the MAC address. Try in permissive mode.
[Galaxy S 4 Mini Original Android Development] RedSkull23:
The error can't be there, as i said that couple of errors can't prevent the installation of the ROM, because they are harmless errors. Can you make a fast resume of your setup? (Recovery used, method, device type... ROM version?)

Have you tried flashing the addonsu-arm-signed.zip package by TWRP 3.1.0?
[Galaxy S 4 Mini Original Android Development] christiangre28:
Thank you so much I have finally root access :laugh:
[Galaxy S 4 Mini Original Android Development] ghines:
Bump
[Galaxy S 4 Mini Original Android Development] sillet91:
The battery in this build is good for me, if you want to be a root user, install the súper su addon, from lineageOS page, in extra
[Galaxy S 4 Mini Original Android Development] Andi46:
Here everything works as it should, clean flashed...
[Galaxy S 4 Mini Original Android Development] sej7278:
yes i managed to get 150mbps on the same floor - seems my new router doesn't like ceilings, as i can only just get 135mbps upstairs.

---------- Post added at 11:33 AM ---------- Previous post was at 11:32 AM ----------

so now we've gone official, will the official build instructions work now, or are there patches still to apply from gerrit?
[Galaxy S 4 Mini Original Android Development] csendre:
Unfortunately this option is gone for us. It went away in the early days of CM13 because QC made some code proprietary. Some newer dual SIM phones got it back with a different method but our blobs are too old and don't support it.
[Galaxy S 4 Mini Original Android Development] MarcWilmots:
I did an upgrade to official LineageOS 14.1 coming from unofficial by flashing these 4 zips:

lineage-migration-signed.zip

lineage-14.1-20170428-nightly-serranoltexx-signed.zip

open_gapps-arm-7.1-micro-20170502.zip

addonsu-arm-signed.zip

and it's working great. Thanks a lot.

Only issue i still have is that i have to edit the build.prop by adb.
[Galaxy S 4 Mini Original Android Development] RedSkull23:
Experiencing some issues while downloading files with DeeBrowser; the download starts and the icon come out, then it immediately stop, and when i go to download folder i find only a blank file, with no details or name either. I tried even an mp3 file and the result was the same, the only difference is that the icon of the file found in dl folder has headphones icon, so Lineage at least recognize the type of file as music. I've tried this only in mobile mode, not desktop. Gonna give a try in desktop mode soon.

EDIT at 18.29 pm; i switch on mobile data (usually i keep them off) and suddenly the dl of the mp3 has started and finished, while of the 4 pictures wich i tried to download I've seen no traces
[Galaxy S 4 Mini Original Android Development] BOTUS:
lineage-14.1-20170428-nightly-serranoltexx-signed.zip

open_gapps-arm-7.1-stock-20170430.zip

with this set up I can't turn the device on when its on charge. Is this normal ? I could see its a good idea to stop it being turned on if its under xxx% charge (say 20%) but this was at 90% 95% 97% and fully Charged state. On numerous occasions.

With it on charge, I recollect it flashes a battery type status with no numbers or text which looks like its trying to say its totally flat. If you persist trying to turn it on (knowing full well its fully charged) then the on button takes a lot longer to respond than it should (getting on for 4 to 5 seconds before any reaction) flashes the samsung 19195 logo and goes to sleep, then a while later the battery status with bars and text displays, goes out and the phone remains completely off.

If you unplug the cable it turns on normally.

It has done this with two different batteries in different or both fully charged states
[Galaxy S 4 Mini Original Android Development] 12Christian:
Hi, are there any known bugs in this rom about bad sound quality when using the phones speaker?
[Galaxy S 4 Mini Original Android Development] arco68:
Any gapps package above micro is not recommended. Some of the files they install replaces our own files, and causes issues and breaks functionality.
[Galaxy S 4 Mini Original Android Development] cdurex:
Thanks for the hard work

Awesome thanks for the build arco68 now official, we went from 50 to top 22 now 21 :D

I will install it on the weekend... +1 that count :silly::cool:

Link to Stats page: https://stats.lineageos.org

View attachment 4135785
[Galaxy S 4 Mini Original Android Development] benboggart:
Oh, what a bummer!

I'm pretty sure whatever idea I'm coming up with isn't new, but is there a way that LOS would allow access to the phone without authorizing both SIM cards, e.g. by having a skip-option when entering the second PIN? Or is the access routine part of a blob as well?

Or couldn't we have a boot option to ignore either SIM?

Anything but physical extraction of the SIM card would be good.

Thanks for your reply btw, such info isn't easy to come by using google (search) only.
[Galaxy S 4 Mini Original Android Development] cdurex:
Arco, we should add this important info to the OP. :good:
[Galaxy S 4 Mini Original Android Development] echo124:
How to fix data on mms ?
[Galaxy S 4 Mini Original Android Development] IronRoo:
did you restore a backup? Deleting the telephony.db file and rebooting might fix (do you need to wipe cache & dalvik in recovery, not sure) Anyhow I suspect that may be the area you need to investigate as per ref in the OP by Arco

(Edit: maybe even just deleting app data insystem apps > phone & messaging storage would do it?)
[Galaxy S 4 Mini Original Android Development] arco68:
I tested it yesterday, both sending and receiving, and it worked fine for me.
[Galaxy S 4 Mini Original Android Development] Archiatrus:
"Any gapps package above micro is not recommended. Some of the files they install replaces our own files, and causes issues and breaks functionality."

Just a suggestion: Can this be put in the OP? Some users (like me) are stupid and think getting the full thing is a good idea because then they "do not miss anything". I did not notice anything broken with the mini package, but this probably only means it is not horribly broken.

Anyway, thanks a lot for keeping me old but trusty phone alive :)
[Galaxy S 4 Mini Original Android Development] MarcWilmots:
Using solid explorer it works for me too. Strange. Thanks
[Galaxy S 4 Mini Original Android Development] karl_k:
Update fails

Hi ! I just try to upgrade from lineage-14.1-20170409-UNOFFICIAL-serranoltexx.zip to lineage-14.1-20170428-nightly-serranoltexx-signed.zip but i get Error 7 in TWRP 3.0.3.0. The MD5 does verify OK. Its a GT-I9195.

Any Ideas what could be wrong ?

Error Message is:

Can't install this package on top of incompatible data. Please try another package or run a factory reset. Updater Process ended with Error: 7
[Galaxy S 4 Mini Original Android Development] Mek7:
As mentioned in the OP, flash migration zip first.
[Galaxy S 4 Mini Original Android Development] karl_k:
Thanks, that worked great !

Cheers,

Karl
[Galaxy S 4 Mini Original Android Development] orsmes:
I have lineage os 20170419 unofficial version but i wasn't able to update to official one. At last i found the solution. there is a migration problem which is about some initial signiture and solved with lineage-migration-signed.zip

Installation steps:

1-Make a backup in TWRP.

2-Flash lineage-migration-signed.zip.

3-Reboot

3-Flash an official Lineage build.

4-Reboot.

then you have the official Lineage OS. Works great.
[Galaxy S 4 Mini Original Android Development] bierma32:
All about update from unofficial to official with the migration .zip is written on the OP from arco68, why nobody read this ?
[Galaxy S 4 Mini Original Android Development] BavoV:
BTW the build Day on OP would be nice. I have been told it is friday.
[Galaxy S 4 Mini Original Android Development] echo124:
Basically mms download, but sometimes get stuck and just sit "downloading" if. Maybe it's network, but seems ok on los13. Earlier versions of cm14.1 also no problem, but seemed to start occuring after certain cm 14.1/los 14.1 build. Sorry or being not clear.:eek:
[Galaxy S 4 Mini Original Android Development] Tyranio:
BLN, CPU Overclock, 3800 mha Battery

Hi there,

it would be really great if the kernel would support:

- BLN control -> the devices has no LED

- CPU overclock -> to give this old devices a little more power

- the possibility to choose the mha size of the battery -> there are 3800 mha batteries on the market

If there is no chance for offical support, is there a way to modify the kernel for my own?
[Galaxy S 4 Mini Original Android Development] Hinterecke:
https://xdaforums.com/showpost.php?p=71049007&postcount=1637
[Galaxy S 4 Mini Original Android Development] Mek7:
Hey,

I think I found a problem in the official ROM, which was not present in the unofficial one. Automatic display brightness doesn't seem to work well. When the phone is waken up, it displays the lock screen with full brightness, only then slowly dims to what the actual brightness (automatic, according to surrounding environment) should be. Previously, and as it should work, brightness was automagically set right from the start.
[Galaxy S 4 Mini Original Android Development] orsmes:
is it normal that i can't see restarting section on power menu?
[Galaxy S 4 Mini Original Android Development] rellieberman:
Is it selected in power menu? Settings->buttons->power menu.
[Galaxy S 4 Mini Original Android Development] orsmes:
yes, it is selected.
[Galaxy S 4 Mini Original Android Development] MaChiMiB:
restart should be displayed.

Try this to enable the advanced restart option:

Enable the Developer Options by going to Settings. Click on About phone and then tap Seven times on the Build number.

Go back to settings, the 2nd last entry should be Developer Options. In there the 3rd entry is the Advanced restart section. Enable this and look if the entry pops up when you long press the power button.
[Galaxy S 4 Mini Original Android Development] IronRoo:
All new S4 Mini builds with this months security patches & new browser are about nearly finished according to Jenkins, I will flash as soon as the footy is finished!

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

Yes, I was bored waiting for someone!
[Galaxy S 4 Mini Original Android Development] Smeagal192:
Downloaded update, install just takes you to twrp 3.1.0.0 homescreen, no update script runs as did for marshmallow, any ideas :(
[Galaxy S 4 Mini Original Android Development] rogers11:
Flash manually from TWRP. What else?
[Galaxy S 4 Mini Original Android Development] RedSkull23:
Another official nightly has came out on lineage site, it looks to apply this update
[Galaxy S 4 Mini Original Android Development] Mek7:
As others have already noted, I too would like to emphasize that flashing opengapps above micro is not supported. I tried aroma to get google clock installed, but all kinds of things (not apparent at first sight), broke:

- clock was installed, however, alarm was always a few minutes late

- AOSP keyboard was replaced by Gboard settings of which crashed, and anyway, it was a step back in functionality as the Gboard was more dumb

- my dialer app (True Phone) which I had set as default to replace the dumb default google one, did not display anything, did not even activate phone display on incoming call, so I had phone ringing and vibrating, but no way to actually accept it, and even reinstalling True Phone did not fix it

Thankfully I had a backup which I restored so I use a different clock app for my alarm, and everything else is working.
[Galaxy S 4 Mini Original Android Development] raisedfist:
I just installed this ROM and it works pretty well, with a single issue: I get "no internet connection" when connected to wifi. I connect to my personal router and all other devices in the house have no issues. Also, setting another phone as hotspot and connecting to it, I don't have this problem.

Is there something I can do to fix this issue?
[Galaxy S 4 Mini Original Android Development] Bernd.Defy:
Thank you for testing. Went back to 03-13, as flipcase support is nice enough to be not-so-up-to-date. Will our device's flipflap-implementation will ever be merged or does it contain some copyrighted or closed source stuff? If not - how difficult is doing the patch for myself and compile then? How many files will will be affected?
[Galaxy S 4 Mini Original Android Development] iman16:
I did a clean install with aroma on i9190 and it worked flawlessly for me. Clock with alarms working perfectly, WiFi, 3g, telephone etc.
[Galaxy S 4 Mini Original Android Development] Haugrolizated:
I've got the same problem.
[Galaxy S 4 Mini Original Android Development] M1chiel:
The downloaded zip should be in /data/data/org.lineageos.updater/app_updates

Can you manually install it from there in TWRP?
[Galaxy S 4 Mini Original Android Development] fahrer17:
A friend of mine had the same problem and he solved it by installing the upate manually.
[Galaxy S 4 Mini Original Android Development] BavoV:
Yes, I can.
[Galaxy S 4 Mini Original Android Development] IronRoo:
No it's not proprietary software, Arco mentioned the flipflap app a few months ago, they were trying to implement it I think, so hopefully it'll be back one day
[Galaxy S 4 Mini Original Android Development] 1of16:
There are some apps special for dual sim devices. My redmi 2 pro also aint got these options to choose ringtones for each sim too.

Maybe some apps can help there...but i coulndt find anything useful yet.
[Galaxy S 4 Mini Original Android Development] echo124:
Sorry let me rephrase, auto_enable_data on mms - problems receiving mms when data is off.

Observed behavior: there is no indicator that data is turned on when mms is being received unlike in cm 13.
[Galaxy S 4 Mini Original Android Development] Haugrolizated:
Me too. Thanks a lot.

But, anyone knows why this happens? I updated to LOS 14.1 from official LOS 13.0 two weeks ago and from the first nightly of LOS 14.1 it does not work anymore. TWRP 3.0.3-0
[Galaxy S 4 Mini Original Android Development] fahrer17:
My guess is that's it is a temporarily problem. I think this happened to my N4 too with the very first LOS release. After updating to the next nightly everything was fine. So nothing to worry about (I hope ;)).