If by screen mirroring you mean casting your phone screen to a TV wirelessly, this has worked for me for the last several builds. Using 900t with latest baseband. Btw, also using open gapps nano
Last edited:
[ROM] [OFFICIAL] LineageOS 16.x ALL VARIANTS
- Thread starter Brunowp8
- Start date
If by screen mirroring you mean casting your phone screen to a TV wirelessly, this has worked for me for the last several builds. Using 900t with latest baseband. Btw, also using open gapps nano
Yes this is what I mean and some other users are having the same problem.
I'm using KLTE and haggertk's 20181210
https://xdaforums.com/showpost.php?p=78526392&postcount=765
I think it is somehow, a model specific problem. I am experiencing this issues with my phone. I'm on kltedv 20190109 (G900P) builds by the way.
I'm travelling and the clock only shows roaming time, and not both time zones (initial and roaming). Is that normal behaviour? Can it be changed without a third party app? Thanks
Five days ago I did a clean install in my 900V (wipe system, data, cache and davilic) of 16.0 using the Jan 2019 version with TWPR, Magisk 18.0 and OpenGApps. Everything has been fine until today when I placed my phone in airplane mode and powered my device off. When I rebooted the device 20 minutes later, I found I cannot connect to cell signal. when I go to about phone --> sim status it says Sim Status mobile network state "disconnected", network "Unknown", EID Unknown. My phone number is listed and a MEID list filled in
To address, I have rebooted several times and have also wipes ART/davilik and cache with reboot only to encounter the same issue. Also, I am able to use wifi without a problem. does anyone have any ideas how to fix?
To address, I have rebooted several times and have also wipes ART/davilik and cache with reboot only to encounter the same issue. Also, I am able to use wifi without a problem. does anyone have any ideas how to fix?
The easiest way is to have a TWRP backup of just the EFS settings from a good connection ROM and restore it when you lose the LTE connection. If you don't have that backup you can install a stock ROM that will reset your connection settings. Look for a stock ROM that is a zip file that you flash from TWRP and that way you won't need a computer to fix this later.
Thanks so much for your quick reply. I have a previous TWRP complete backup that includes the EFS partition, would restoring JUST the EFS partion from that backup work?..... or does the backup have to ONLY contain the EFS partition?
I have not tried that but I think it would work. It will not hurt your phone to try it.
curiousrom
Recognized Contributor
No Network, No IMEI, No SIM & EFS Partition Restore Fix
Have you tried turning off the phone, removing & reinserting the SIM card then turning back on?
From this EFS Partitions: What They Are And How To Get It Back If Lost thread:
"EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone... It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things..."
Yes you can restore any part of a full TWRP backup depending on the situation including only the EFS partition in your case to fix a No Network and/or a No IMEI problem.
TWRP > Restore > Select Storage (where your backup is located) > Select Package to Restore > Select Partitions to Restore > EFS (do not select Enable Digest) > Swipe to Restore. Reboot to System without doing anything else in TWRP.
You could make a backup of your current EFS before restoring the other one, just in case.
For users who have a No Network, No IMEI and/or No SIM problem & do not have an EFS Partition backup; if turning off & back on the phone does not fix the problem:
The backup & restore procedure is the same on the S5.
***
Have you tried turning off the phone, removing & reinserting the SIM card then turning back on?
From this EFS Partitions: What They Are And How To Get It Back If Lost thread:
"EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone... It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things..."
Yes you can restore any part of a full TWRP backup depending on the situation including only the EFS partition in your case to fix a No Network and/or a No IMEI problem.
TWRP > Restore > Select Storage (where your backup is located) > Select Package to Restore > Select Partitions to Restore > EFS (do not select Enable Digest) > Swipe to Restore. Reboot to System without doing anything else in TWRP.
You could make a backup of your current EFS before restoring the other one, just in case.
- Besides making a separate EFS Partition which I copy to computer because it's so small (only 10MB on the S5 as seen in the screenshot) I always include EFS when making a full TWRP backup before flashing a firmware.
- TWRP > Backup > Select Storage to external Micro SD card (so it does not get erased when flashing a new ROM or using Format Data) > Name: EFS_Backup (for example) > select only EFS > Swipe to Backup.
For users who have a No Network, No IMEI and/or No SIM problem & do not have an EFS Partition backup; if turning off & back on the phone does not fix the problem:
- In TWRP make a full backup of your current installation EXCEPT the EFS partition because you are currently having problems with it.
Install the most recent stock Samsung firmware for your phone. Write down and/or screenshot your working APN settings. - WARNING: If you do that with the special case S5 SM-G900V it will re-lock the bootloader and you will have to unlock it again.
- Install TWRP & make an EFS partition backup before flashing LineageOS.
- Either do a S5 LineageOS Super Clean Install or restore the backup you made above EXCEPT the EFS partition.
- If after booting to System you still have a No Network and/or No IMEI problem, restore the EFS partition made while running the Samsung stock firmware in TWRP.
- If it's still does not work compare the APN settings while running the Samsung stock firmware to LineageOS > Settings > Network & internet > Mobile network > expand Advanced > scroll all the way down to > Access Point Names (APN) & long press the APN's name, edit & 3-dots Save if any corrections are needed.
The backup & restore procedure is the same on the S5.
***
Last edited:
Possible bug with sounds
I installed KLTE version of haggertk's (20190109), with nothing else added aside from pico gapps, and it works exceptionally well - thanks for the fantastic job!
The only weird thing I noticed so far is that I can't change (better said, I couldn't find a way to change, so far) any sound.
If I access 'Settings/Sounds/Advanced', among other options I see 'Phone ringtone', 'Default notification sound' and 'Default alarm sound'.
After selecting any of these, I get a page with several options ('My sounds', 'Pixel sounds', etc.), but if I select one of them, I just go back to the previous page....
Is that something happening to anyone else?
I installed KLTE version of haggertk's (20190109), with nothing else added aside from pico gapps, and it works exceptionally well - thanks for the fantastic job!
The only weird thing I noticed so far is that I can't change (better said, I couldn't find a way to change, so far) any sound.
If I access 'Settings/Sounds/Advanced', among other options I see 'Phone ringtone', 'Default notification sound' and 'Default alarm sound'.
After selecting any of these, I get a page with several options ('My sounds', 'Pixel sounds', etc.), but if I select one of them, I just go back to the previous page....
Is that something happening to anyone else?
curiousrom
Recognized Contributor
Sounds Crash When Changing Ringtone, Notification or Alarm
Thanks for reporting this Sounds app bug in 16.0 build 2019-01-09. :good:
A link to your report was added to New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs.
I was able to replicate it on S5 G900M running haggertk's klte LineageOS 16.0 build 2019-01-09 + Open GApps ARM 9.0 Pico + Magisk v18.0 & it took me a while to figure it out as seen in the attachment: Settings > Sound > Advanced > press on either Phone ringtone or Default notification sound or Default alarm > and select the Sounds app > then select one of the folders & Sounds crashes.
The Sounds keeps stopping popup warning was disappearing so fast that I could not read it & had to use Lineage's screen Record app & play it back, pause & take a screenshot.
"...KLTE version of haggertk's (20190109) ...pico gapps" - Gapps is the key here as Play Store updated the stock 16.0 System app Sounds version 1.0 (com.google.android.soundpicker) to 2.0.
To figure that out I went to > Settings > Apps & notifications > 3-dots > Show system > Sounds > Advanced & scroll to the bottom to see App installed from Google Play Store & version 2.0 (223598125).
As seen in the second screenshot I used App Freezer to find Sounds' path: /data/app/com.google.android.soundpicker. Note that Sounds 2.0 has 4 services while 1.0 has zero.
After disabling Sounds in Apps & notifications & saying OK to the Replace this app with the factory version? the version changed to 1.0. Back in App Freezer the path was now changed to: /system/app/SoundPickerPrebuilt/SoundPickerPrebuilt.apk
After re-enabling Sounds I successfully changed the Ringtone with a simpler Sounds 1.0 as seen in the third attachment.
I attached a logcat of the crash after updating Sounds again manually in Play Store in case @haggertk reads this post using the fast & easy SysLog after a fresh reboot.
For those interested you can unzip & open the logcat.log with Wordpad for example to keep the formatting & search for soundpicker to find errors like these:
Sorry for the clutter XDA app users as the Hide function does not work in the app.
The Workarounds
My guess is that you don't use Play Store so your default Sounds 1.0 did not get updated or you are using an other app. Correct?
***
I installed KLTE version of haggertk's (20190109), with nothing else added aside from pico gapps, and it works exceptionally well - thanks for the fantastic job!
The only weird thing I noticed so far is that I can't change (better said, I couldn't find a way to change, so far) any sound.
If I access 'Settings/Sounds/Advanced', among other options I see 'Phone ringtone', 'Default notification sound' and 'Default alarm sound'.
After selecting any of these, I get a page with several options ('My sounds', 'Pixel sounds', etc.), but if I select one of them, I just go back to the previous page....
Is that something happening to anyone else?
Thanks for reporting this Sounds app bug in 16.0 build 2019-01-09. :good:
A link to your report was added to New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs.
I was able to replicate it on S5 G900M running haggertk's klte LineageOS 16.0 build 2019-01-09 + Open GApps ARM 9.0 Pico + Magisk v18.0 & it took me a while to figure it out as seen in the attachment: Settings > Sound > Advanced > press on either Phone ringtone or Default notification sound or Default alarm > and select the Sounds app > then select one of the folders & Sounds crashes.
The Sounds keeps stopping popup warning was disappearing so fast that I could not read it & had to use Lineage's screen Record app & play it back, pause & take a screenshot.
"...KLTE version of haggertk's (20190109) ...pico gapps" - Gapps is the key here as Play Store updated the stock 16.0 System app Sounds version 1.0 (com.google.android.soundpicker) to 2.0.
To figure that out I went to > Settings > Apps & notifications > 3-dots > Show system > Sounds > Advanced & scroll to the bottom to see App installed from Google Play Store & version 2.0 (223598125).
As seen in the second screenshot I used App Freezer to find Sounds' path: /data/app/com.google.android.soundpicker. Note that Sounds 2.0 has 4 services while 1.0 has zero.
After disabling Sounds in Apps & notifications & saying OK to the Replace this app with the factory version? the version changed to 1.0. Back in App Freezer the path was now changed to: /system/app/SoundPickerPrebuilt/SoundPickerPrebuilt.apk
After re-enabling Sounds I successfully changed the Ringtone with a simpler Sounds 1.0 as seen in the third attachment.
I attached a logcat of the crash after updating Sounds again manually in Play Store in case @haggertk reads this post using the fast & easy SysLog after a fresh reboot.
For those interested you can unzip & open the logcat.log with Wordpad for example to keep the formatting & search for soundpicker to find errors like these:
Sorry for the clutter XDA app users as the Hide function does not work in the app.
The Workarounds
- Don't change the default sounds.
- Disable & Enable Sounds to return to stock then disable auto-update in Play Store & don't update Sounds.
- Use the stock Media Storage app instead as seen in the first screenshot.
- Use a file explorer & select your own Ringtone, Notification or Alarm sounds.
- If you don't have app choices when you tap on Ringtone it's because you chose Always when selecting Sounds instead of Just once.
To fix that go to Settings > Apps & notifications > Default apps & remove Sounds.
If you don't see it there go to > Apps & notifications > 3-dots > Show system > Sounds > Advanced > Open by default > Clear Defaults.
My guess is that you don't use Play Store so your default Sounds 1.0 did not get updated or you are using an other app. Correct?
***
Last edited:
Correct. I don't install stuff that messes with core OS functionality. I think its important for getting a baseline on the overall reliability during this phase of testing.
Anyway, it does raise the old question of where to report this type of issue, as the proper Gitlab route is only available for official builds. It is unrealistic to expect devs to trawl through these forums to pick up on issues. Even if they do, it is a huge effort to relog them on any 'internal' system.
I think expanding the Gitlab system to accommodate 'credible' unofficial builds maybe the way forward. Who knows?
Many thanks to you for checking what I reported, I really appreciate! :good:
I already tried also your workaround (#2), and it works just fine for what I wanted to do (i.e., configure also on the new ROM my usual sounds).
Btw, just in case anyone else is interested, in the meantime I also installed Powertools and Greenify, because I'm already used to these tools and I like them.
That's what made me realize that this ROM is not rooted by default (not because it wasn't already mentioned, but just because I didn't notice - my fault).
So, I used TWRP 3.2.3-0 to flash the "boot.img" file which is included in the ZIP file of the ROM, and also "Magisk-v18.0.zip" right afterward.
That successfully rooted the ROM in a minute, and made Powertools and Greenify work as they should.
For all intents and purposes, my S5 is now pretty much a brand new device. Couldn't be better!
:highfive:
Last edited:
im back guys I haven't given up on this phone or anything im sorry I haven't answered anyone questions u had before I stated on a new school for network admin so ive been busy going to download the new version of the 2019 build and check it out ive had many issues with the current build I have right now like (plugging phone in when its off causes constant reboots(im using stock battery) ,using ram intensive root apps will restart your phone use Zanti3 pen test app for example, brightness is bugged doesn't really have much change to the screen until the very end portion, GPS is bugged for me atleast it sometimes works sometimes doesn't ,using battery saver doesn't auto grey scale and sometimes it does, ive had to switch to normal busybox build because the custom one was making my phone's battery die extremely fast with overclock also most apps cant see that the custom busy box is even installed,custom kernel get extramly unresponsive when phone is not used for a long period of time or when is being too intensively used, cell service for the klte dosent work for certain cell towers im with virgin mobile and it always just connects to brother tower service bell and ****ty wind mobile towers also unless ive straight outside I only usally get 1 bar to usually having no service inside )) ill get back to you guys on what ive found out and tested when I get home and install the new 2019 build currently on the oct 12th 2018 build xD
curiousrom
Recognized Contributor
Re: Old Build Problems, Custom Kernel & Other Tweaks
"...currently on the oct 12th 2018 build xD" - Holy cr@p that was 9 builds ago as you can see here https://androidfilehost.com/?w=files&flid=281382&sort_by=date&sort_dir=DESC and more than 375 merged commits ago as I need to go back 16 pages @ the present to find some of haggertk's merged stuff in October 2018: https://review.lineageos.org/q/owner:haggertk%40lineageos.org+branch:lineage-16.0+status:merged,375
Pay attention to the words of the wise from the post above :angel: :
Check this post & keep it stock for your first tests at least without custom kernel & your other tweaks : New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs.
"...plugging phone in when its off causes constant reboots...- That could be a bad cable, power adapter or damaged or dirty (pocket lint) USB charging port on your S5 or problem with older builds that has now been solved.
***
"...currently on the oct 12th 2018 build xD" - Holy cr@p
that was 9 builds ago as you can see here https://androidfilehost.com/?w=files&flid=281382&sort_by=date&sort_dir=DESC and more than 375 merged commits ago as I need to go back 16 pages @ the present to find some of haggertk's merged stuff in October 2018: https://review.lineageos.org/q/owner:haggertk%40lineageos.org+branch:lineage-16.0+status:merged,375Pay attention to the words of the wise from the post above :angel: :
Check this post & keep it stock for your first tests at least without custom kernel & your other tweaks
: New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs."...plugging phone in when its off causes constant reboots...- That could be a bad cable, power adapter or damaged or dirty (pocket lint) USB charging port on your S5 or problem with older builds that has now been solved.
***
Last edited:
Yes I'll make sure to keep it stock rooted I do like doing stuff in spare time with coding so I need root functions also my charging issue has happens since the very first build I used on here don't know what caused it I asked a few times on here lol oh well I'll do the testing for bugs and other stuff let me know if u need help at all doing stuff cause I have developed for the s5 neo roms before I'd like to bring ideas from my builds before on that phone to on this phone like my custom phone startup screen instead of Samsung s5 showing up and other tweaks and mods like viper4android
so I went to stock then got the 2019 version and factory reset now im stuck on the checking for updates as if I go to skip account setups it disables wifi so I cant skip the update check and ive tried with mobile data it does the same thing just says checking for updates is taking to long (edit went back to stock rom then going to reflash)
Last edited:
Just wondering in /sdcard/dev/block/by-name/param.bin is this where the splashscreen/boot logo is because I wanna make a custom splash screen but I can't seem to decomile the .bin file with 7zip like I could with my s5neo param file anyone help with this.would be great
I have a G900V.
Today I attempted to update to haggertk's 20190109 build, but upon rebooting to system, the phone does the standard "Phone is starting" progress bar on the home screen and then the whole system abruptly dies. The screen goes black and the phone does not respond to any button inputs.
I figured, OK - dirty flashing is not going to work. So I wiped data and did a clean flash. Upon boot, phone does the "Just a sec..." screen, and then same thing, drops to a black screen and the phone is a paperweight.
Next I tried a full nandroid restore from a working configuration to reset all partitions, then wiped data and clean flashed 20190109. Same black screen issue.
Next I figured maybe this is an issue with this particular build, so I reverted to the previous working release I was running, 20181203. Same black screen issue.
So at this point, I see two possibilities. One is that something is broken in software that was not recovered by my nandroid restore. In that case, how can I odin/twrp to stock without re-locking my bootloader/resetting my CID? The other possibility is that my phone has finally completely died and this is a hardware problem.
Any thoughts?
Today I attempted to update to haggertk's 20190109 build, but upon rebooting to system, the phone does the standard "Phone is starting" progress bar on the home screen and then the whole system abruptly dies. The screen goes black and the phone does not respond to any button inputs.
I figured, OK - dirty flashing is not going to work. So I wiped data and did a clean flash. Upon boot, phone does the "Just a sec..." screen, and then same thing, drops to a black screen and the phone is a paperweight.
Next I tried a full nandroid restore from a working configuration to reset all partitions, then wiped data and clean flashed 20190109. Same black screen issue.
Next I figured maybe this is an issue with this particular build, so I reverted to the previous working release I was running, 20181203. Same black screen issue.
So at this point, I see two possibilities. One is that something is broken in software that was not recovered by my nandroid restore. In that case, how can I odin/twrp to stock without re-locking my bootloader/resetting my CID? The other possibility is that my phone has finally completely died and this is a hardware problem.
Any thoughts?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
105
Code:* Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you.
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Galaxy S5 Supported Models/Variants & Download Links
klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
klteactivexx - SM-G870F
kltechn - SM-G9006V, SM-G9008V
kltechnduo - SM-G9006W, SM-G9008W
klteduos - SM-G900FD, SM-G900MD
kltedv - SM-G900I, SM-G900P
kltekdi - SCL-23
kltekor - SM-G900K, SM-G900L, SM-G900S
Use version 3.2.1-0 or newer of TWRP
How to install?
• Download the latest TWRP version
• Download the latest build
• Reboot to recovery
• Flash the latest build
• Reboot
Download Links
ROM: https://download.lineageos.org/
GApps: https://wiki.lineageos.org/gapps.html
TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html
Credits
Many thanks to the LineageOS team and all the contributors out there in the community
@haggertk Official Maintainer
Source Code :
Github: https://github.com/LineageOS
Code Review: https://review.lineageos.org/
Android Version: 9.x Pie29
And the actual klte* maintainer cannot reproduce non-working mobile data. On both a G900F with GSM service and a G900V with actual VZW service. CDMA data is the same as SIM data. Bands don't let data "slip by".
Now, I got an email that indicated that it seemed that IPv6 mobile data is working and IPv4 isn't. That's a curious, and plausible, finding. Maybe those with non-working mobile data want to report status related to that. Note that if people want to relay things to me then I only care about results on builds that I create (read: I know what went into them).
Edit -- OK, pretty sure I got it. I'll upload a build in a bit.
Edit 2 -- Uploaded21
haggertk is a lazy moron and hasn't worked out sepolicy for P yet, so it's still permissive as forced by https://review.lineageos.org/#/c/224917
More seriously, I hope to finally iron out policy this week. Been busy and wanted to do it right.
Regarding how important is it - I do not run devices as daily drivers without being enforcing. Quite a few security vulnerabilities are mitigated by selinux and legacy devices with legacy blobs can use belts and suspenders.
Sent from my PH-1 using Tapatalk19
Yeah, I forgot to go back and re-test after setting selinux to enforcing. I'll re-spin builds today to fix that.
Sent from my SM-N900T using Tapatalk
