I had a 3000mAh "Akku King" battery with the size of the standard one(and NFC antenna). So no custom back cover necessary. But Akku King is just a german based online shop, probably not shipping worldwide.
[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat
- Thread starter haggertk
- Start date
I can only find a 4200/4800mAh or - ready 6800mAh batteries. None of which I trust and I can't remember how to tell if they're real or Memorex.
And such batteries should come with a back cover and the phone will fit in no case no more and if such a heavy load drops it will certainly break.
I regarded the additional 200mAh of my battery just as a small bonus.
And i never got a foul battery, whether most likely forged "genuine" ones for an LG phone or all the others for all kinds of stuff, mostly from third party suppliers.
I regarded the additional 200mAh of my battery just as a small bonus.
And i never got a foul battery, whether most likely forged "genuine" ones for an LG phone or all the others for all kinds of stuff, mostly from third party suppliers.
Last edited:
Security Patches
I know this post is 4 months old, but I would also like to know if this is something that the casual user could accomplish. This Unofficial 14.1 is far-and-away my favorite OS for the S5, and I see no reason to fix what isn't broken.
As FettyWap stated, I'd also like to thank @haggertk for his continued support, and welcome any update. Even quarterly patches would be very much appreciated.
I know this post is 4 months old, but I would also like to know if this is something that the casual user could accomplish. This Unofficial 14.1 is far-and-away my favorite OS for the S5, and I see no reason to fix what isn't broken.
As FettyWap stated, I'd also like to thank @haggertk for his continued support, and welcome any update. Even quarterly patches would be very much appreciated.
@purplevike I have since migrated to 16 and I am dealing with intermittent Bluetooth issues. What features are you looking to hold on to in 14.1. I agree it is superior as far as reliability is concerned. I did find some alternatives for call recording etc
Last edited:
I'd still be using my s5 if it weren't for the Bluetooth unreliability after 14.1. There is still an open ticket regarding Bluetooth stability. I filed a long time ago, never even acknowledged by haggertk...it seems to only affect a few of us though so maybe not worth his time given how much he's got going.
I think there are more of us than meets the eye with Blue Tooth issues after 14.1
I also just gave up on my S5 and upgraded to an S9. Problem solved. My S5 is still running Nougat as a backup unit.
If I had to guess, the issues are caused by the newer Blue Tooth Driver going into power management that the S5 hardware wasn't designed to deal with, causing the crashes. My idea is to integrate the older driver into the newer rom and see how that goes, if that could even be done?
I also just gave up on my S5 and upgraded to an S9. Problem solved. My S5 is still running Nougat as a backup unit.
If I had to guess, the issues are caused by the newer Blue Tooth Driver going into power management that the S5 hardware wasn't designed to deal with, causing the crashes. My idea is to integrate the older driver into the newer rom and see how that goes, if that could even be done?
It Just...Works
The loss of the ability to screen cast was a non-starter for me. Besides the buggy nature of bluetooth disconnects, and other inexplicable anomalies, (notifications and the like.) 16.1 just wasn't for me. 14.1 with updated patches is the perfect blend of functionality, reliability, usability, and security.
The loss of the ability to screen cast was a non-starter for me. Besides the buggy nature of bluetooth disconnects, and other inexplicable anomalies, (notifications and the like.) 16.1 just wasn't for me. 14.1 with updated patches is the perfect blend of functionality, reliability, usability, and security.
@haggertk Thanks for your continued support for the S5.
Would it be possible for a security update for LOS 14.1 builds? Definitely a crowd favourite.
Thanks again.
Would it be possible for a security update for LOS 14.1 builds? Definitely a crowd favourite.
Thanks again.
Most people certainly know that Google has recently implemented Covid-19 exposure notifications in its Play Services. They appear as the first menu item in the settings under Google. If you select this menu item, you will only see a white page. Normally, however, numerous setting options should appear there. This functionality is a prerequisite for using the national Covid-19 apps, which are now being rolled out by the national authorities. It seems that these apps will not be usable with Lineage 14.1 on the S5, right?
curiousrom
Recognized Contributor
Re: Google COVID-19 exposure notifications
On a Galaxy S5 G900M LineageOS 16.0 klte build 2020-04-27 + Open GApps Pico with Display > Style Dark the > Settings > Google > COVID-19 Exposure Notifications panel is white whithout any text.
Only when Display > Style Light is selected is the text visible.
That COVID-19 panel links to Android help https://support.google.com/android/answer/9888358
***
On a Galaxy S5 G900M LineageOS 16.0 klte build 2020-04-27 + Open GApps Pico with Display > Style Dark the > Settings > Google > COVID-19 Exposure Notifications panel is white whithout any text.
Only when Display > Style Light is selected is the text visible.
That COVID-19 panel links to Android help https://support.google.com/android/answer/9888358
***
@curiousrom: But it should not only link to the Android help but also offer two options to delete the Random IDs and to deactivate covid-19 tracing as you can see on the attached Screenshots from a German Smartphone where the tracing works. If these options are not present I suppose this is an indication that tracing will not work.
By the way: Lineage 14.1 doesn't offer a menu item Display -> Style Dark or Light.
By the way: Lineage 14.1 doesn't offer a menu item Display -> Style Dark or Light.
Attachments
Last edited:
After I have deleted the Google Play Services data via the settings, the menu item no longer appears in the Google settings. All very strange. It's a pity that there is no feedback on this...
Really great and much appreciated !!
Thank's a lot @haggertk
https://androidfilehost.com/?w=files&flid=140204&sort_by=date&sort_dir=DESC
Last edited:
It is as I suspected: With LineageOS 14.1 it is obviously not possible to use the Nearby.EXPOSURE_NOTIFICATION_API of Google Play Services. Although the Play Services are up to date (version 20.18.17, updated end of May) and Google writes in its documents that the functionality should be available from Android 6.0 on. I wonder what's causing it. There is only the error message as in the screenshot below.
Attachments
Last edited:
Just one more good reason to skip that sh**t and appreciate this rock solid ROM.
:good:
:good:
Last edited:
I leave the subjective evaluation of the app's usefulness to the scientists. I'm all about the technical aspect. I would be interested to know why the API does not work with LineageOS 14.1.
No LTE on G900T with QC2 Modem ?
First, thanks for making this LOS 14.1 ROM available. I don't need the latest LOS on my old SM-G900T (official nightly 16.0 builds from LOS), but it is nice to have a more recent Android OS on the device (compared to the last 6.0.1 TW ROM by Samsung).
Two observations:
(1) I was unable to install this ROM with TWRP v3.4.0.0; I needed to use TWRP v3.3.1.0 to install this ROM successfully.
(2) I installed this from stock ROM build MMB29M-G900TUVU1GQC2; I'm finding that data is limited mostly to HSPA or HPSA+ -- I rarely see LTE using an AT&T SIM.
This is a back-up device; my daily is an unlocked SM-G930U (S7), also with an AT&T SIM, and I always have LTE data. I found one old xda-developers thread that seemed
to address this issue: forum.xda-developers.com/tmobile-galaxy-s5/lte-connection-issues-lineageos-t3554259, which references a potential solution using force_g900f_ril_blobs.zip (also by OP of this thread). Can anyone here comment on whether this solution is appropriate for the G900T running this LOS 14.1 ROM to get reliable LTE data? If so, do I need to root the device to apply?
Update:
I tried to install the referenced ZIP from TWRP; it failed, so I wiped this unofficial 14.1 and am giving an official 15.1 nightly from Feb 2019 that I managed to find with a little Googling. So far, so good with regard to LTE connectivity...
First, thanks for making this LOS 14.1 ROM available. I don't need the latest LOS on my old SM-G900T (official nightly 16.0 builds from LOS), but it is nice to have a more recent Android OS on the device (compared to the last 6.0.1 TW ROM by Samsung).
Two observations:
(1) I was unable to install this ROM with TWRP v3.4.0.0; I needed to use TWRP v3.3.1.0 to install this ROM successfully.
(2) I installed this from stock ROM build MMB29M-G900TUVU1GQC2; I'm finding that data is limited mostly to HSPA or HPSA+ -- I rarely see LTE using an AT&T SIM.
This is a back-up device; my daily is an unlocked SM-G930U (S7), also with an AT&T SIM, and I always have LTE data. I found one old xda-developers thread that seemed
to address this issue: forum.xda-developers.com/tmobile-galaxy-s5/lte-connection-issues-lineageos-t3554259, which references a potential solution using force_g900f_ril_blobs.zip (also by OP of this thread). Can anyone here comment on whether this solution is appropriate for the G900T running this LOS 14.1 ROM to get reliable LTE data? If so, do I need to root the device to apply?
Update:
I tried to install the referenced ZIP from TWRP; it failed, so I wiped this unofficial 14.1 and am giving an official 15.1 nightly from Feb 2019 that I managed to find with a little Googling. So far, so good with regard to LTE connectivity...
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
293LineageOS official builds have been released.
Code:#include "std_disclaimer.h" /* * 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. */
Build/Variant Map:
FAQ/Frequent Statements
GApps:
Doesn't Work:
- CM ThemeEngine - Not ported to lineage-14.x
- VoLTE - Didn't work on cm-13.0. Didn't work on cm-14.1. Don't expect great things, even devices from the same generation as ours that had VoLTE on M (e.g., bacon) don't have it on N.
Downloads:
Official (lineage-14.1) - https://download.lineageos.org
Official SU Addon - https://download.lineageos.org/extras67Source:
https://github.com/LineageOS
https://review.lineageos.org
My Picks for unofficial (official doesn't pick anything):
https://github.com/haggertk/cm_build_stuff/tree/cm-14.154
It will be LineageOS as soon as we finish standing up a new Gerrit code review instance (should happen today) and merge rebranding patches. Currently it is a 100% bare fork -- CM source == LAOS source.
I'd expect official builds are at least a week away. There are a lot of offers for server time and storage space coming in, but no one really wanted to do much thinking along those lines yesterday during the holiday and step 1 really is getting Gerrit running.
Suffice to say, cyngn's actions over the weekend accelerated our timeline. We'd been planning to be cut over to new Gerrit by New Year's, but by deleting DNS entries and disabling SSH access to CM gerrit really has pulled the rug out from under us.
Please bear with us. If anyone is looking for general OFFICIAL LineageOS information/messaging, stick to these locations -- we control them:
http://lineageos.org/
https://www.reddit.com/r/LineageOS/
https://www.facebook.com/lineageandroid
https://twitter.com/lineageandroid
https://plus.google.com/11389707673812612076435Builds are being uploaded to the usual place, all with filenames containing the 20161027 date.
Changes of note:
- Kernel update to 3.4.12. Ozzy is grinding through, only about 100 releases left to go.
- seccomp-bpf. Well, this isn't exactly new to my builds, the last one or two had it, but I went ahead and merged it.
- Dirty COW fix. Yeah, all of you probably are running rooted, but we don't want some rogue app doing root-level stuff without you being prompted now, do we? This may have been in the last build, I cannot remember the time of day that I kicked it off...
- Anything merged into the greater cm-14.0 tree.
- Oh yeah, some camcorder thing. It appears to be working for me. It should work for you. Or it may completely blow up. It is still under active review. Beware, dragons.
Yes, I know that work is being done on cm-14.1 (Android 7.1). Not every project is forked yet, I don't want to deal with a frankentree, and I'd just as soon let that settle down a bit (first devices successfully booted only just last night). So no, no cm-14.1 yet. And no, I don't know when.33CM-14.1 builds are going up. I updated the first post, but if you don't feel like clicking back, they are here. klte is up already and kltevzw will be soon thereafter. The rest will come in due time. All will have the date of 20161029 in the filename.
If you want to dirty-flash upgrade from cm-14.0, you MUST flash new Android 7.1 gapps immediately after flashing cm-14.1 before booting the ROM or fail city will result.
For those asking what's different from the @javelinanddart build, pretty much just everything that's been committed in the last couple days to the greater CM tree. I did compile this using MALLOC_SVELTE which may help with our relatively low-memory device. If this looks good over the next couple days I'll merge it upstream.
Oh yeah, I also picked this unmerged commit that will let you actually change the status bar battery representation.
