See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Reserved
Reserved
Just wanted to say thanks for this!
I use this phone with hangouts dialer on wifi when I'm out working (leaving my good, fragile phone safe in the house). I was using the old cyangenmod 13 rom because it was the only one that would work without missing sim errors.
This rom works perfectly for my needs, again, thanks!
javelinanddart said:
See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Click to expand...
Click to collapse
Is this rom still being actively developed? I'm interested in testing if so.
FanboyStudios said:
Is this rom still being actively developed? I'm interested in testing if so.
Click to expand...
Click to collapse
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
javelinanddart said:
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
Click to expand...
Click to collapse
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Edit: Stock equalizer seems to work on all my audio files (.wav, .flac, .m4a), except .mp3 files.
FanboyStudios said:
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Click to expand...
Click to collapse
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
javelinanddart said:
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
Click to expand...
Click to collapse
I'm using the latest official build from the official LineageOS website. It's 14.1
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
javelinanddart said:
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
Click to expand...
Click to collapse
Oh, that's good news! In fact I did not check the NFC function before writing that message, I think I saw somewhere that NFC does not work in LineageOS on S5.
Or maybe I got confused with S4 (jfltexx) which I also own and where NFC does not work for sure.
I've sent you a donation thru Paypal, many thanks for your work!
Just a side note for fun and general info. My bank flagged my account after using their banking app as accessing with a "known fraud device" and locked my savings and checking. In the end, I had to get new accounts because they could not turn them on after the fact. I tried to explain in vain and they would not hear it. So fair warning if you try to use your banking app on the Lineage ROM. Nothing extra added, only the current version of this ROM and open gapps.
Is there any chance to see Wireguard VPN support in this build?
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
What are the bugs with the lineage-14.1-20180222-nightly-kltesprsports-signed.zip build? I'm interested in flashing. Also, was the issue with airplane mode disconnecting LTE on the s5 sport ever resolved? Disabling airplane mode does not initiate LTE connection only until I reboot my phone. I'm on build 14.1-20170418 currently so curious to see what has improved. Also, a big thanks to everyone in this community. I moved from cm13 to this build a year ago and I've been happy. Just looking to resolve the LTE issue .
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
vrobo said:
Is there any chance to see Wireguard VPN support in this build?
Click to expand...
Click to collapse
Wireguard is awesome.
I found out that calendar does not notify about forthcoming events. I use LineageOS without Google stuff (with Offline Calendar https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/ instead).
Is this a bug in Offline Calendar on in LineageOS build for kltesprsports?
vrobo said:
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
Wireguard is awesome.
Click to expand...
Click to collapse
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
onlyoneway said:
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
Click to expand...
Click to collapse
https://download.lineageos.org/kltesprsports/changes/
Hey Guys! I have a Samsung S5 sport that I recently dirty flashed to the 14.1-20180803-NIGHTLY-kltesprsports build. Now my battery does not go beyond 65% no matter how long I leave my phone plugged in. I have tested different cables and adapters, and still the same thing. Didn't have this issue with the 20180720 build. Any thoughts? Bug maybe? Thanks in advance.
Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat - Togari, ROM for the Sony Xperia Z Ultra
Contributors
OmarEinea, SlimRoms, prbassplayer
Source Code: https://github.com/SlimRoms
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Build 9
Stable Release Date: 2014-12-26
Current Beta Version: Build 8.20
Beta Release Date: 2014-12-09
Created 2014-06-30
Last Updated 2014-12-29
Camera fix apk
Found here
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Deleted
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
blueether said:
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
Click to expand...
Click to collapse
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
prbassplayer said:
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
Click to expand...
Click to collapse
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Edit:
I do know that carbon is using -caf as I had to change an include path to get past a not found .h
blueether said:
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Click to expand...
Click to collapse
Slim had problems with some video playback (browser video or Netflix) would be green unless I disabled hw overlays, when we moved caf that git fixed and camera was less problematic.
Sent from my Xperia Z1 using Tapatalk
Thanks a lot for another awesome firmware for the Z Ultra!!
Regarding the camera issue, I've been facing it on every custom firmware out there, and found a possible workaround (works for me, at least): as soon as the device boots, open the camera immediately, and it should open normally after a small delay / frame freeze. After that, it continues to work normally, without any freezes, until the next reboot. However, if you wait a while after boot before opening the camera, it will freeze with a static frame. Killing it will cause the "can't connect to camera" message to appear the next times you open the camera. And I've tested with different camera apps, it's the same thing.
Hope it helps to debug the issue.
Alright, currently running this as my main. No problems so far; Bluetooth, calling, LTE, Wi-Fi, and video all work completely. Haven't had a reason to use the camera yet, however.
all seems to be working, but it doesn't read my SD card. It's an class4 a-data 32GB card formatted as exFAT, I'm backing up its content and will format it in phone (it does recognize it, but when I tap mount sd card, more options just flash below and then it goes back to 'mount sd card')
edit: no luck, it doesn't even format the card. When I reformatted it via card reader to FAT32 or NTFS, it was recognized, but with NTFS formatting it does not see any data, so I guess it's just exFAT/NTFS support that's missing
oh and with this dpi settings, digits in PIN entry are too close together (but still possible to type them in) - see http://i.imgur.com/sNmEGOJ.jpg
awsome job buddy another device of Xperia Brigade
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
jouse i will do it if u want
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
blueether said:
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
Click to expand...
Click to collapse
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Not sure of the differences either, but as soon as I got Carbon togari to build the gpe built as well. There has only been a few little issues in the gpe build for carbon. although the last silm I built for the GPe didn't boot.
There only seems to be about 30 people downloading the GPe carbon so there may not be much of a call for it.
Been a while .. No new Updates for this ROM ???
VipiN'n'DroiD said:
Been a while .. No new Updates for this ROM ???
Click to expand...
Click to collapse
Bother reading much?
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
prbassplayer said:
Bother reading much?
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
Click to expand...
Click to collapse
Thanks Bro for your work [emoji106]
Support thread for RecEnabler.
HEY!
This module is becoming useless. A change in CarbonROM's gerrit is in the works that accomplishes the same thing.
Just letting you know!
RecEnabler (SHOULD) enable(s) Call Recording on supporting ROMs (e.g: CM, Carbon)
Submit bugs to the GitHub page, all else goes here.
GitHub
Xposed Repo
XDA:DevDB Information
RecEnabler, Xposed for all devices (see above for details)
Contributors
_alp1ne
Xposed Package Name: com.ender.recenabler
Version Information
Status: Alpha
Created 2014-08-24
Last Updated 2014-08-30
Does it work on both incoming and outgoing calls? I'm asking because I can't find any setting or switch to record calls.
I'm on latest cm nightly (maguro device)
From GNexus
All it can record is my own voice, FYI, the record button is on the phone dialer, bottom right.
It states it's recording but only works one way.
I'm using the latest CM11 on a Note 3 (CDN version).
Thanks
tpowell.ca said:
It states it's recording but only works one way.
Click to expand...
Click to collapse
+1
allanski said:
+1
Click to expand...
Click to collapse
Do not work for me. Screenshot of the screen with recordingbutton?
tpowell.ca said:
All it can record is my own voice, FYI, the record button is on the phone dialer, bottom right.
It states it's recording but only works one way.
I'm using the latest CM11 on a Note 3 (CDN version).
Thanks
Click to expand...
Click to collapse
+1
Using a one plus one. Cm 11s 33r. Doesn't seem to be working.
Will this work with carbon rom nightlies? Since it is cm based
Sadly no, i've tried it. At least not on Hammerhead (8/24).
This mod is being phased out. A change to enable it is in Carbon's gerrit.
Dont work on Nexus 5 with CM11s ROM
http://forum.xda-developers.com/xposed/modules/xposed-enablecmcallrecording-t2856248
I bought two Kenzos, one normal and one "Prime". On the first one I installed Mokee, that's the daily driver for my wife. On the second one I tried some ROMs, and I got two bugs that are annoying to me. If some of you would please try to reproduce them, so that we know for sure that they are bugs and report them. I have tested on "ResurrectionRemix-M-v5.7.3-20160807" and "aicp_kenzo_mm-11.0-NIGHTLY-20160812", both of them first with stock kernel and after that with "Radon-V2.1-Kenzo".
1. Kenzo has a magnetic switch, for the "smart covers" to put the phone to sleep when the flip-cover is closed and wake it up when it opens. It works on Mokee, but it doesn't work neither on RR nor AICP. If you don't have a Smart Cover you can use two small (and not powerful!) magnets. In the attached picture I have marked the zone where the two magnets in the cover are. If you put your two magnets floating over the screen (without touching it, use eventually some paper) in the corresponding area (~1 and 2 centimeters below the camera) the screen should go off, and if you remove them the screen should go on. I've looked at the live logs, and in RR and AICP no events are triggered, but they appear under Mokee ("PowerManagerService( 1261): Going to sleep due to lid switch (uid 1000)... ", etc). I have attached the logs in flip2016-08-13_23.05.zip.
2. I noticed that under RR and AICP I can not access the phone trough ADB. I can switch it to MTP mode, I see it, I can transfer files, but after switching to USB debugging "adb devices" gives me no device, and in the Device Manager I have only a unknown device. In fastboot mode it's woking. I don't think it's a driver issue, because under Mokee it's working as expected. I've attached logs captured under AICP with the Radon kernel.
3. Under Settings -> Security, check "Unknown sources", exit, and go again. The setting is not saved.
Off-topic: why isn't the Ambient Display working as expected? I remember that my former MotoE under CM12 got waked up when I took it out of my pocket, and so was the MotoG under CM13. Why can Kenzo do the same thing?
Flip Covers do not work with most Custom ROMs. It may be a driver issue or maybe just the code is missing. So, if you really want that to work, you can make a request to the maintainer of your favourite Custom ROM to add support for flip covers or simply you can use those ROMs that do have support for them.
For the ADB missing device, force your "unknown device" in Device Manager to update drivers and it should work fine from thereon. I have faced this many number of times on many different devices. ADB drivers, once installed, would work fine while the phone is on one ROM but would display as "unknown device" once the ROM is changed on the phone. Thankfully, updating drivers for that device almost always does the trick.
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
ayush3051 said:
Flip Covers do not work with most Custom ROMs.
Click to expand...
Click to collapse
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
ayush3051 said:
For the ADB missing device
Click to expand...
Click to collapse
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
Hi,
Most likely the code to have that feature is not yet included because of the custom roms are CM based including AICP and RR and the CM's official build for Kenzo just got out. A lot of devs will test and keep working on it. Meanwhile you can submit a request to CM via their site and they will include it or post it on the CM thread by the The Strix.
last but not the least use an app from the play store they surely do work in most of the cases.
Thank you for your reply, dwaipayanray95. I wanted first to have confirmation that these are really bugs, before submitting them. That's why I asked other users for help. I've tested them on CM13 only last night, I think that I will post them on TheStrix's thread.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
I could have tested it, but I am travelling for the next 30 or so days. So I cannot really test a new ROM like right now. I will be happy to do so once I reach home back, though I should tell you that I do not personally own a Flip Cover or have at my hands any small magnets.
But the thing is, even though the ROMs are CM based, they do not incorporate the whole CM base and hence are not capable of doing everything the base ROM does. Hope you understand this. On the other hand, the derived ROM may have some other feature which is not even present in the base ROM.
Let me give you an example in terms of AICP and RR, themselves.
Both AICP and RR do not implement CM's onscreen Navigation Bar, instead they have opted for DUI with pulse(which I personally love).
Similar may have been the case with the Flip cover code. If you want to you can make a device specific request at AICP and RR's Google+ pages. The developers are quite active there and can guide you much better than I can.
Regards and Thanks
If you still face the unkown device adb problem install the adb driver installer its around 9 mb.it can install drivers for all phones but you will have to disable driver signature enforcement in windows first.you will be good to go by this
and can i have proxisensor flip cover? cause i use a normal one not the official plastic one. i only want flip cover where the phone is in a tpu case. but its kinda anoying that the screen doesnt turn off. and i have tried some apps but they use more battery then they help...
First one isn't working in the most roms i tried which are commonly used some features of CM/Lineage, the second one you are also right. I had to remove RR so I can't check the third one, hope to solve my problems soon because I miss my RR
these issues are also not in aosp extended. but has in most of lineage based roms.
Let us get back once the CM14 nightlies start
Unofficial CM14 builds based on CyanogenMod + Grarak + Cherry-pick from CyanogenMod review stream
Facts:
Added 1 blob from OOS 3.1.0 to get the build working (Grarak is aware of it)
No extra features added, please do not request (still a n00b here)
Focus is more on debugging and hopefully help Grarak
Why is it not my daily driver though it is stable enough for a daily driver:
Unable to deactivate a SIM (just my itch)
Video recording does not work (Footej works but I want the stock camera to work: Will debug)
Busy to be able to spend more time debugging (especially with many other components changing rapidly)
Note:
Thank you all for being nice on this thread
hackworks said:
Unofficial builds of CM13 & AOSPA for OnePlus 2 with rotation vector fix. Please feel free to test it *only* for rotation vector bug (missing arrow in Google maps). Both builds are updated to latest source from their corresponding repositories.
AOSPA: https://www.androidfilehost.com/?w=files&flid=101343
CM13: https://www.androidfilehost.com/?w=files&flid=101350
CM13 changeset in review: http://review.cyanogenmod.org/#/c/157838/
AOSPA change (could not submit for review): http://pastebin.com/x9mMHzaq
Since this problem plagued us for a long time, I thought of sharing the builds for wider testing. Please be gentle, this is the first time I have shared a ROM that I have built
[All credits to the awesome hackers working on CM & AOSPA]
Click to expand...
Click to collapse
i would say, your hack is working just like your username..
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Mohit31 said:
Is it possible for you or anyone to make a flashable zip of the fix...!?
Would be much better and convenient
We can use it on any ROM and will not restricted to use above 2 ROMs only
Click to expand...
Click to collapse
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
hackworks said:
The change is in the framework. The part of the code calls into proprietary Qualcomm sensor service process to get a list of hardware sensors. In theory, this can be intercepted and filtered to ignore rotation vector sensor from hardware. This will let existing code in framework use the AOSP fusion sensor based implementation to get the values.
I have done something similar by intercepting IO requests to speed up IO over network
Click to expand...
Click to collapse
Lol... It all went above my head
I think the answer is, it's not possible, right?
Thank you very much. It's working for me.
(I guess next/about next will have the fix, too. The existing commit only has to be merged)
Great work! This bug has been present since ever.
Sent from my ONE A2003 using Tapatalk
Todays build doesn't have the fix already. Am I right?
PeterImmel said:
Todays build doesn't have the fix already. Am I right?
Click to expand...
Click to collapse
Getting a patch merged is a slow process especially with almost all of CM devs focussing on 'N'. I will make a new build available with patch to hide signal for deactivated SIM in the status bar (when I get back home from work). There are/were 2 issues bugging me for a long time.
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
That's awesome
Great work
Thanks a ton..!!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Click to expand...
Click to collapse
You 're the man! Back to CM13 because of your fixes. Many thanks!
hackworks said:
Updated build with fix to hide signal for deactivated SIM. Picked change from AOSPA and integrated into CM13. This completes the last 2 issues I faced on CM13 on OP2.
Build updated with latest changes as on 24th Aug 2016 (21.00): https://www.androidfilehost.com/?fid=24686680535466503
Click to expand...
Click to collapse
Any chance of fixing loudspeaker echo, WhatsApp voice note not loud and random vibrations due to dt2w?
With these fixed, CM will be bug free.
Sent from my ONE A2003 using Tapatalk
@hackworks Has the rom been built with latest aospa code?
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Yea. :/
This has still not been fixed.
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554 @hackworks Please have a look.
P.S. This issue isn't present on AOSPA. So maybe that'll help.
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
John-J.Hammy said:
Can i flash Xposede Framework?
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
It is just CM13 with the 2 fixes. All that applies to CM13 or AOSPA remains valid on these builds
Mohit31 said:
You have fixed some of the very irritating bugs..
I wonder if you can do your magic on this issue as well..
http://forum.xda-developers.com/showpost.php?p=67812802&postcount=1554
Click to expand...
Click to collapse
n00b here. No magic, just learning. I am working on using a cleaner approach to hide the SIM signal icon. Once done, will explore other areas
raburs said:
@hackworks Has the rom been built with latest aospa code?
Click to expand...
Click to collapse
Sorry for not responding earlier, I have uploaded a new build which is based on latest source as on today 26th Aug 2016 (night) for both CM13 & PA.
I tried my hands in Java code by implementing an event based mechanism to disable the SIM icon when it is disabled - Just ended up in flickering display and a SystemUI crash! Guess, I should just stick to C/C++ where I have spent most of my programming life (~18 yrs)! Summary: Will pick areas/bugs based programming language, no time to learn Java
DOWNLOAD
New builds will normally be available mid-month each month.
Actually important stuff:
Update TWRP, older versions may cause problems.
H918 users: Versions up to, but not including, 10p are ARB0. 10p+ is ARB1.
Verizon users (regardless of phone model): You need to make an outgoing call after booting to be registered correctly on their network. Calling your voicemail is an easy way to do this.
Make sure you have a backup of your EFS partition. If that gets wiped, then you may have issues connecting to LTE on some devices.
YewMinou: This is an app to make a detailed logcat file. If you run into issues, make a log and attach it to your post.
Please do a clean install and wipe cache and dalvik cache after flashing the ROM (TWRP should give you a button to do so once flashing is complete).
The first boot will take longer than the rest, be patient!
Changelogs can be found in Settings > Resurrection tools > About > Changelog.
Known Issues:
VoLTE and WIFI Calling do not work (and likely never will on any custom ROMs).
Standing on the shoulders of giants
This ROM would not be possible without people that have selflessly donated immense amounts of their free time and effort. I'd like to thank:
x86cpu, Rashed97, Omar-Avelar(oxavelar): For making current, aosp-based ROMs a reality for the v20.
runningnak3d: For making it possible to even flash those ROMs on many variants.
Phoenix591: For maintaining and updating TWRP for the v20.
I'd also like to thank everyone that works on LineageOS and Resurrection Remix!
Sources:
ResurrectionRemix
kernel_lge_msm8996
msm8996-common
v20-common
h910
h918
h990
ls997
us996
vs995
YewMinou
Wohaaaaaaa, Man I am in love with your work, Thanks for giving another lifetime to our LGv20s.
Changelogs any other information will be highly appreciated.
God bless you.
Thanks for bringing another life to the LG V20, will flash it on my V20 tonight and use it for the weekend to see the performance and possibly as a daily driver. Keeping my fingers crossed. Thanks again to you @Blaises
Awesome. Will test it for sure. May I flash it over stock oreo, or I'll have to revert to nougat?
droid_for_life said:
Changelogs any other information will be highly appreciated.
Click to expand...
Click to collapse
You can get to the changelogs on any RR build from Settings > Resurrection tools > About > Changelog. Unfortunately the first build doesn't have anything there yet, but each subsequent build will have the last month's changes listed there.
The only noteworthy change over RR pie is a set of patches I've been working on that enables per-contact colors in the messages app. I'll attempt to get that upstreamed once I clean up my code and squash the commits.
Qron said:
May I flash it over stock oreo, or I'll have to revert to nougat?
Click to expand...
Click to collapse
RR should have all the same quirks as x86cpu's LineageOS builds. So you'd likely need to revert to nougat if you want fingerprint to work. I only have one phone (us996) to test on, so let me know what you find out.
hi if the rom is based on LOS16 does it mean it have a notch support like in LOS?
thank you, looks like a good rom cant wait to try it
Hi
Thank you guy !
i have a question.
How is camera app? May we have the lg camera or google camera app in this rom ?
In Lionageos 16 we haven't and google camera is crashing.
mehradasadi said:
Hi
Thank you guy !
i have a question.
How is camera app? May we have the lg camera or google camera app in this rom ?
In Lionageos 16 we haven't and google camera is crashing.
Click to expand...
Click to collapse
We will never have any stock camera in Lineage because LG uses some proprietary software parts in their rom and it's hard to recreate these to get stuff to work, like the FM radio or VoLTE.
The camera in Lineage 16 works great, you should flash 15.1 first and then dirty flash if you're having issues and then try gamma kernel as well. 8 isn't work for me but 7 is. Also, Gcam 5.1 works flawlessly for me, but I haven't tried this rom yet
---------- Post added at 01:04 PM ---------- Previous post was at 12:55 PM ----------
Blaises;80277109
...
[/QUOTE said:
On the V20 Lineage telegram group someone showed a video of the brightness slider and its worse than Lineage's. It dark until the very end of it and I was wondering if you could fix this.
Nothing against x86cpu, I really appreciate his work and he's done so much amazing work but it's one of the few things that can't seem to get completely fixed so I am wondering if you could take a look at it.
Click to expand...
Click to collapse
Woah this is incredible to all V20 users thumb up
Grin59 said:
We will never have any stock camera in Lineage because LG uses some proprietary software parts in their rom and it's hard to recreate these to get stuff to work, like the FM radio or VoLTE.
The camera in Lineage 16 works great, you should flash 15.1 first and then dirty flash if you're having issues and then try gamma kernel as well. 8 isn't work for me but 7 is. Also, Gcam 5.1 works flawlessly for me, but I haven't tried this rom yet
---------- Post added at 01:04 PM ---------- Previous post was at 12:55 PM ----------
On the V20 Lineage telegram group someone showed a video of the brightness slider and its worse than Lineage's. It dark until the very end of it and I was wondering if you could fix this.
Nothing against x86cpu, I really appreciate his work and he's done so much amazing work but it's one of the few things that can't seem to get completely fixed so I am wondering if you could take a look at it.
Click to expand...
Click to collapse
Thank you for your reply.
Two important features in LG camera app is wide and normal lens changing and also 4K recording. These features are not accessible in other apps.
sharon1122 said:
hi if the rom is based on LOS16 does it mean it have a notch support like in LOS?
Click to expand...
Click to collapse
Yes, it's set up the same way to use the second screen area as a notch.
Grin59 said:
On the V20 Lineage telegram group someone showed a video of the brightness slider and its worse than Lineage's. It dark until the very end of it and I was wondering if you could fix this.
Click to expand...
Click to collapse
I didn't notice that since I had mine on auto. I'll poke around and see if there's anything I can do about it.
mehradasadi said:
Two important features in LG camera app is wide and normal lens changing and also 4K recording. These features are not accessible in other apps.
Click to expand...
Click to collapse
The wide angle camera should be available even if the default app can't see it. I have been using Open Camera and it is able to use all three cameras.
mehradasadi said:
Thank you for your reply.
Two important features in LG camera app is wide and normal lens changing and also 4K recording. These features are not accessible in other apps.
Click to expand...
Click to collapse
These features are in gcam, I'll link the thread I get gcam from.
https://forum.xda-developers.com/ap...google-camera-mod-wide-angle-t3747263/page245
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
Blaises said:
I didn't notice that since I had mine on auto. I'll poke around and see if there's anything I can do about it.
Click to expand...
Click to collapse
That would be greatly appreciated. I haven't tried the rom out myself yet as I'm going to be busy this weekend but I'll see if the slider is bad or not Sunday. Thank you.
i have a problem. the media volume did not work.
Solved. i flashed again and worked well.
sajadzare said:
i have a problem. the media volume did not work.
Click to expand...
Click to collapse
So you can't then the volume up or down?
in some cases when alarm was active screen does not show anything and screen was off, just alarm tone played.
and so received call screen.
i use gamma kernel for lineage 16 version 7.0 because version 8.0 was crashed some times when phone wants work hard, or hangs.
This is great stuff! Big fan of your 6.2.1 and this one will certainly be as good.
Thank you Blaises
sajadzare said:
in some cases when alarm was active screen does not show anything and screen was off, just alarm tone played.
and so received call screen.
i use gamma kernel for lineage 16 version 7.0 because version 8.0 was crashed some times when phone wants work hard, or hangs.
Click to expand...
Click to collapse
What model do you have?
Grin59 said:
What model do you have?
Click to expand...
Click to collapse
H990ds
Kernel is gamma version 7
For H990ds
working great. to enable camera i had to dirty flash from RR 6.2 (previous one)
after then all working good so far.
And what about the battery on this beautiful version.
My phone is 990 ds and the battery is implemented quickly. Is it a way to save power
Thanks to every assistant. Trenslated by Google.