[ROM][9.0][UNOFFICIAL] [G800F/M/Y] LineageOS 16.0 [Beta] [16-12-2020]

[Marteng69]

I use Magisk Works good. I haven't tried v 19.0. I've been using 18.1. It should probably work as well though. Just can't say for sure.

I am using Magisk 18.1 and root is working fine.

---------- Post added at 19:39 ---------- Previous post was at 19:26 ----------

I also want to thank @spookcity138 for this great ROM!
We do have three S5minis in our family as daily driver.
This weekend I installed the first with the 20190310-version. The installation went almost fine.

I have only some (knows) problems with the ROM:
1. Recording videos: it is only working with footej camera, not with open camera, nor the stock camera. But even with footej using the camera sometimes crashes, especially while changing between camera and video modes.
2. Creating a second user with the multi user settings is not working. Every time I switched to the previously created new user the dialog to finish the creation of the new user crashed and I had to delete the second user.
3. I once tried to encrypt the complete phone. After the next reboot the phone remained in a bootloop and I had to wipe everything.

 

[Extremelyd1]

I can't seem to install the rom zip file.
Whenever I try via TWRP I get a cut-off message in the log saying "E3004: This package is for device: kminiltexx, kminiltedv, kminilteub, kminilte; this device is .. ".
The rest of the message is not visible.
My phone is a G800F, any ideas?

Edit: Apparently my TWRP was outdated and therefore it couldn't flash the zip. Works great now!

 

[MikeT.]

Hello, thanks @spookcity for all your work, I'm glad that you're be back

I tried last build at my main device and the ROM was good for me (I'm with your AEX 6.4 for now)

There is a general problem (at both devices) since AEX 5.8 (ie in your xenonhd (oreo) from January, RR from @rodman01, LOS16,.. too) and I'm not sure where it come from, but I think it has to do with jdwp (see logs): I can't upload pictures in communities based on xenforo. Via and Lightning browser means "no app for this action available"

 

[MikeT.]

Log 2

 

[spookcity138]

First off: @spookcity138 thank you so much for still supporting this crappy old phone!

After sticking with lineage 13 or so for way too long and not really caring about my phone, I finally started flashing roms again when this thread came up.
With the first few releases I experienced the same issue with writing to sdcard that many people also reported here. The most annoying was WhatsApp not being able to download photos. Gladly this was fixed in the latest release!

Another issue that I kept stumbling upon and took me some googling to figure out was the Samsung Smart Cover (or: flip cover). I'm not using the actual cover, but the setting is enabled by default, which made my phone randomly enter some kind of locked state with the display half blue and only the time displayed. I couldn't do anything but restarting the phone. The solution for this is to go to Settings -> Connection Settings -> Smart Cover and just disable it.

I was kinda happy with my phone, but sometimes had huge performance issues that are also reported in more recent posts of this thread. I could counter the lockups by setting the performance governor in Kernel Adiutor, but this was not a long-term solution. Also there was no recent kernel with different governors or overclocking available that I wanted to try.
Finally I was also able to solve this problem, and here is how. In Magisk Manager I downloaded and installed LKT ('Legendary Kernel Tweaks'). The phone's CPU is not listed in the compatibility list, but nevertheless it works fine for me. In LKT I set the 'Balanced' profile, which so far works very well for me. I haven't tested for too long now, but battery life seems still quite fine and the phone is running reasonably smooth. Maybe one could even go for 'Performance' mode.

With these minor problems solved, I would like to repeat how overall happy I am now with this rom, smoothly running the latest Android on an I-don't-even-know-how-old phone and want to thank @spookcity138 again for the effort! I will see if I can find someone with a Paypal account...

Thanks a lot for such detailed feedback. It is very useful to me...and I'm sure others will find this useful also. I have made a few changes relating to memory. I reverted pinning a few services into memory. I also added a couple of memory optimization flags and in my testing (3 days or so) it has made a noticeable difference. This will be part of the next build and will hopefully,if not completely eliminate the random freezes,at least make them much less likely.

I am using Magisk 18.1 and root is working fine.

---------- Post added at 19:39 ---------- Previous post was at 19:26 ----------

I also want to thank @spookcity138 for this great ROM!
We do have three S5minis in our family as daily driver.
This weekend I installed the first with the 20190310-version. The installation went almost fine.

I have only some (knows) problems with the ROM:
1. Recording videos: it is only working with footej camera, not with open camera, nor the stock camera. But even with footej using the camera sometimes crashes, especially while changing between camera and video modes.
2. Creating a second user with the multi user settings is not working. Every time I switched to the previously created new user the dialog to finish the creation of the new user crashed and I had to delete the second user.
3. I once tried to encrypt the complete phone. After the next reboot the phone remained in a bootloop and I had to wipe everything.

Same to you. Feedback like this is helpful as I don't use all of these feature,so I would never know some of these things were broken.
1. Yeah,I don't record many videos,but I Know it is still sketchy. Our camera is just a bit of a mess. I will try to revisit this in the future and see if I am able to do anything about this.
2. Interesting, I am not sure about this. I will try to look into it.
3. I saw that a few devs have added a flag for legacy encryption to their device configs. I was unsure at the time exactly what this had to do with,but I will look into it again. Perhaps its as easy as just adding this.

Hello, thanks @spookcity for all your work, I'm glad that you're be back

I tried last build at my main device and the ROM was good for me (I'm with your AEX 6.4 for now)

There is a general problem (at both devices) since AEX 5.8 (ie in your xenonhd (oreo) from January, RR from @rodman01, LOS16,.. too) and I'm not sure where it come from, but I think it has to do with jdwp (see logs): I can't upload pictures in communities based on xenforo. Via and Lightning browser means "no app for this action available"

This I have no idea about off hand. I just know that jdwp is a java debugging protocol. Was "no app for this action available" the only other relevant bit of your log?

 

[Brummschaedel]

@Eightball2: Thanks a lot for the idea with LKT! The first impression is a bit faster response of the phone and a better battery life. I had to reenable the pedometer, but that's not a problem.
@ spookcity138: Just installed the overclocking kernel. And apart from running stable it seems to solve an issue, I found some days ago and just wanted to report: The MTP-connection only worked for downloading files to PC, uploading to the phone failed. Now I tried to get a log and: Hey with this kernel it works! Thanks!

 

[MikeT.]

...

This I have no idea about off hand. I just know that jdwp is a java debugging protocol. Was "no app for this action available" the only other relevant bit of your log?

I remember a notification in aex Oreo about java, lightning browser means "no app for open url", I'll looking for it.
Logs are filtered, send you more later today

Edit. @spookcity138 you have pm

 

[Asgabat]

it won't connect to Hidden wifi, how to fix this?

 

[spookcity138]

it won't connect to Hidden wifi, how to fix this?

This has been brought up before and I've been meaning to post the solution as it is not broken and works fine. It has just changed a bit in Android 9. The key:
Within the add network dialog add your SSID,security type and password. Then scroll down a bit. Click advanced and at the bottom change hidden -no to yes. Hit save and give it 20-30 seconds and it will connect.

 

[Marteng69]

Same to you. Feedback like this is helpful as I don't use all of these feature,so I would never know some of these things were broken.

Thanks for your time and your work.
I have found a new problem:
While running the build-in music app the music visualisation appears on the lock screen, even if it is disabled in the settings of the app. Is there any other setting, which is responsible?

 

[freaklunte]

hello,

is there a chance to upgrade from the Februarbuild to the last build without loosing personal data?

Thanks

 

[Marteng69]

is there a chance to upgrade from the Februarbuild to the last build without loosing personal data?

Usually you can update from one build to the other within the same LOS-version without wiping all data. You need to wipe only dalvik cache and cache after you installed the new build. Just follow the steps in the first post without wiping everything. After installing ROM and GApps (and if you want Magisk) perform a wipe of dalvik cache and cache in TWRP.
If you are coming from other ROMs that are based on LOS (crDroid etc.) you have to wipe everything.

 

[freaklunte]

. You need to wipe only dalvik cache and cache after you installed the new build..

that sounds good

 

[spookcity138]

Thanks for your time and your work.
I have found a new problem:
While running the build-in music app the music visualisation appears on the lock screen, even if it is disabled in the settings of the app. Is there any other setting, which is responsible?

I think this possibly has to do with me enabling always on display in the build. I'm not 100%,but think this is the case. I also think this is the reason why ambient display options crash in settings when clicked. I will look into it...Maybe i will just disable AOD if I can't figure it out and see if that is indeed the culprit of these problems.

 

[freaklunte]

. You need to wipe only dalvik cache and cache after you installed the new build..

that sounds good

and it is succesfully done

Thanks

 

[s5minimalist]

Flip mode squat ;-D

Hi there,

thanks for the awesome rom. Was so crazy yesterday to try out the LOS 16 ROM instead of the ~stable 14.1 one to have a nice up-to-date S5mini. Will try to use the phone productively nevertheless, will see how it goes. I already like the Pie-Feel of the system so I don't think I can go back. Coming from an ACE 3 LTE (S7275) with 14.1 on it, nice one, too.

So to give you a little feedback: All is running very smooth on my G800F, even though Compositing should not be working yet? Sometimes right after restart noticifations on the lock screen seem a little laggy, but in normal use all transitions, animations etc perform nicely.

I noticed, however, a bug with the flip cover mode today (FlipFlap System App?) I like rather small phones, the S5mini being just small enough to be carried around in my jeans’ front pocket (well, 4" kinda is the magic limit for that, so the S5mini is a tad too long).
Every once in a while when pulled out of the pocket and turned on, the Phone is in Flip Cover mode, i.e. half a blue screen with the clock and date on it. Nothing can be done there except turning the screen off again - even reboot by just pressing PwrBtn did not work for me (didn't try the VolUp+Pwr under bright light trick though). I was a little upset, to be honest, but since I had seen the Original Flip Covers for the Phone with a punch-out window, I knew it should have something to do with that. Put the Phone back in the pocket because I was in a hurry, and it returned to normal after a while. However, it happened a few times today while carrying it around in the pants. So maybe the Hall-Sensor should be looked after. Confirmed with a magnet from a Galaxy Tab Flip Cover I had lying around - moving it across the lower left end of the screen triggers the "blue screen".

Looking for a way now to disable the flip cover mode, but haven't found an option in the settings yet. Maybe have to remove flipflap.apk?

Thanks for any thoughts on this, looking forward to seeing this rom evolve. Cheers!

Edit: To be clear: the problem is the phone entering flip cover mode when NOT in a flip cover (I don't have one). Just carrying it around in a dark pocket seems to trigger the mode. Found similar reports for this device and earlier editions of LOS.

 

[MikeT.]

..

Looking for a way now to disable the flip cover mode, but haven't found an option in the settings yet. Maybe have to remove flipflap.apk?
..

You can freeze flipflap in Titanium Backup ie.

 

[metterschling]

Hi there,
Looking for a way now to disable the flip cover mode, but haven't found an option in the settings yet. Maybe have to remove flipflap.apk?.

No need to remove or freeze APKs, there is a setting. I had the same issue and toggling the setting solved it for me. Search this thread, there is a description how to toggle the setting a couple of messages back.

 

[freaklunte]

hi,

since the update to the version of 10.03.19, the system depends partly on the display touches or also in the running apps

I have also seen that the GPS position does not really fit (Locus Maps Pro), but have no direct comparison to the preview version.

are there ideas?

 

[s5minimalist]

No need to remove or freeze APKs, there is a setting. I had the same issue and toggling the setting solved it for me. Search this thread, there is a description how to toggle the setting a couple of messages back.

Thanks, found that one (#160 on Page 16), but I don't have that option in settings. There seem to be NFC Flip Covers, maybe the thing has to be detected somehow to unlock the option, read something like that elswhere.

Making flipflap.apk a user space app with "/system/app mover" (F-Droid) seems to have done the trick, though. Easier than deleting the sensor note via init script, which is sometimes also suggestes. APK freezing might also work, don't know about that.

But maybe the devs might want to look into that problem, maybe there could be a less error-prone default for the flip cover detection, or a fix for the Hall sensor problem triggering without a magnet (maybe static charge when rubbed inside pocket?)