Nightly builds for the cm-10.2 branch for this device have stopped.
Please see here for nightly builds of cm-11.0 (kitkat)
Or continue for the stable cm-10.2 build...
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Q/A thread:
http://forum.xda-developers.com/showthread.php?t=2346808
Please use the above unless you have something development-related to contribute here. Thank you.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 10.2 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery (see here)
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Useful Links
BBQLog changelog
jfltevzw CyanogenMod wiki
Jira issue tracker
Other Issues?
Before posting on this thread, make sure of a few things:
Make sure you have the LATEST version of ClockworkMod recovery. Other recoveries may work but will not be supported by CyanogenMod
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsImNvbS50b3J0ZWwuc3lzbG9nIl0
Download Links
CyanogenMod:
Download: http://download.cyanogenmod.org/?device=jfltevzw&type=stable
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 10.2 for the Verizon Galaxy S4, a ROM for the Verizon Samsung Galaxy S 4
Contributors
invisiblek
Version Information
Status: Testing
Created 2013-09-13
Last Updated 2014-04-23
Mine!
invisiblek said:
Known issues:
None at this time
Click to expand...
Click to collapse
is in call bluetooth working? downloading now and will test when i get my headset back, but I know that has been the major problem with the other cdma jf builds. I was going to look at it all today but if you've got it fixed it would save me the trouble haha
Thanks for your time on this man!
fallingup said:
is in call bluetooth working? downloading now and will test when i get my headset back, but I know that has been the major problem with the other cdma jf builds. I was going to look at it all today but if you've got it fixed it would save me the trouble haha
Thanks for your time on this man!
Click to expand...
Click to collapse
Steve fixed it last night
https://github.com/CyanogenMod/andr...mmit/b38c14a9314d6ab1662765b1ac003f169ee01d17
invisiblek said:
Steve fixed it last night
https://github.com/CyanogenMod/andr...mmit/b38c14a9314d6ab1662765b1ac003f169ee01d17
Click to expand...
Click to collapse
Nice. Might try to build some carbon goodness since i went through all of the trouble of blowing off the dust of my build box
edit: it was early and i cant read
Hey. Glad there's a thread up now. I already reported this via PM, but I thought I'd throw it out there for the community, and I have a workaround.
I can't seem to get a GPS lock in Navigation. However, on stock it works fine. I saw another user post in the help section that he has the same issue on stock. He mentioned that turning off mobile and wifi location fixes the issue for him. I took a shot and it worked. Not sure what to make of it.
Anyone else see this behavior?
Awesome will flash shortly! Is GPS fixed?
Bluetooth is just turning itself off and a2dp isn't working.
Sent from my SCH-I545 using xda premium
SonicJoe said:
Hey. Glad there's a thread up now. I already reported this via PM, but I thought I'd throw it out there for the community, and I have a workaround.
I can't seem to get a GPS lock in Navigation. However, on stock it works fine. I saw another user post in the help section that he has the same issue on stock. He mentioned that turning off mobile and wifi location fixes the issue for him. I took a shot and it worked. Not sure what to make of it.
Anyone else see this behavior?
Click to expand...
Click to collapse
It's a known aosp issue. Last rom I tried workaround didn't work for me. Hopefully it works for me now
Sent from my SCH-I545 using Tapatalk 2
twiz0r said:
It's a known aosp issue. Last rom I tried workaround didn't work for me. Hopefully it works for me now
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm not 100% sure that is accurate, unless it affects phones or devices with mobile data only. I have a GTab 2 wifi running CM 10.1 and it works fine. I tested there before sending my logcat to invisiblek to make sure it was a device issue, not a CM issue.
SonicJoe said:
I'm not 100% sure that is accurate, unless it affects phones or devices with mobile data only. I have a GTab 2 wifi running CM 10.1 and it works fine. I tested there before sending my logcat to invisiblek to make sure it was a device issue, not a CM issue.
Click to expand...
Click to collapse
Im pretty sure he was claiming that it's an AOSP issue specific to are phone....
mbh87 said:
Im pretty sure he was claiming that it's an AOSP issue specific to are phone....
Click to expand...
Click to collapse
That is correct
Sent from my SCH-I545 using Tapatalk 2
twiz0r said:
That is correct
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Sorry. Misunderstood you.
SonicJoe said:
Sorry. Misunderstood you.
Click to expand...
Click to collapse
No worries my friend
Sent from my SCH-I545 using Tapatalk 2
jakeo423 said:
Bluetooth is just turning itself off and a2dp isn't working.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Same here. And the gps only works when mobile networks is unchecked.
I also had trouble getting the trebuchet launcher to work in landscape modes. (Nova works fine)
So happy to see this moving forward!
jakeo423 said:
Bluetooth is just turning itself off and a2dp isn't working.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I can confirm that bluetooth and a2dp are both working 100% for me. Maybe try reflashing?
I'm excited to try the photosphere gallery. Apk with this device. I'm hoping it doesn't have the touch to focus bug like d2vzw did. But even if it does, my fingers are crossed we will get a photosphere mod when the "nexus s4" is released.
I love all the cm camera options, but photosphere is awesome.
Is anyone, besides me, having trouble receiving calls? Whenever I answer a call, the phone locks up after a few seconds.
kingramon0 said:
Is anyone, besides me, having trouble receiving calls? Whenever I answer a call, the phone locks up after a few seconds.
Click to expand...
Click to collapse
when someone calls me I'll let you know...[forever_alone.jpg]
Running well here. No issues that I see so far.
I don't use Bluetooth often so I'm not sure about that.
GPS locks fine. Mobile data is good. :thumbup:
sent from my Galaxy S4 using xda premium
Related
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
I use the Ninphetamine kernel and a clockwork recovery initramfs. The initramfs has been altered and will not boot with other ones. This is because of a missing socket that the older init.rc doesn't make.
I'll be using the next post to describe what I'm working on and update it with any useful info I find.
Currently it's in an unusable state, here's where it stands:
Working
Making calls
SMS
Audio
Internet (Data Connection)
Note: When you open browser, it will crash because google's home page try's to use location services, you need to navigate away quickly in order for it not to crash.
Proximity Sensor
Internal Storage
microSD Storage
Vibration
Camera
USB Transfer with Internal Storage
Untested
Other Sensors
TV Out (doubtful)
Not Working (yet)
WiFi (don't even turn this on, it will reboot endlessly) <-- working on it
Camcorder
Bluetooth
GPS
USB Transfer with microSD (not a huge priority)
I know that cyanogenmod is pretty darn close to AOSP and that I'm duplicating work, but I'm doing it anyways.
If you want to try it out:
Binaries:
CWM Kernel Zip
CWM AOSP Zip
Note: Obviously you need to wipe.
Sources:
https://github.com/nemasu/
Working on WiFi
no notes yet
nemasu said:
I noticed there was no active development that was trying to get the standard AOSP build working, which I really would like to use as my day to day ROM....so I decided to give it a shot. Feel free to help
Click to expand...
Click to collapse
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Pume said:
AdamG has made devnull (http://forum.xda-developers.com/showthread.php?t=1183063&highlight=devnull) which is basicly the AOSP build. Some stuff not working though as the CM7 team has not managed to get audio over bluetooth working.
He has also started the Oxygen development. The oxygen thread is here: http://www.forums.acsyndicate.net/showthread.php/1591-ROM-AOSP-GRJ90-2.3.5-Oxygen-v2.2.1
Good to hear others working on this too, hope you manage to get bluetooth audio issue sorted and perhaps help other AOSP / CM7 devs with that issue.
Click to expand...
Click to collapse
Ah, yeah, I forgot about that one. I'll be leaving it completely stock AOSP though (when it works well anyways). Might speed things up for me a bit. I am doing this as a sort of hobby too, interesting to learn how it works.
EDIT: It WILL speed things up a great deal....DevNull did some great work.
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
All the same, great work mate, we need more AOSP ROM's, since AdamG has taken a break due to personal reasons it's nice for another dev to take the helm.
Good luck mate, all the best.
nesquix said:
search for the Oxygen ROM on google.
it's a rom for SGS2 where everything works, and it's only AOSP.
http://forum.oxygen.im/index.php
Click to expand...
Click to collapse
Does A2DP work on Oxygen?
Sent from my CM7 powered SGS2
This xda members...
AdamG did great work yes but it does not preclude to new AOSP roms.
Keep your respected work.
Edit: If AdamG had taken a break, maybe you should think to fork devnull. This speeds up work and you can focus another thinks etc A2DP and tvout. Its open source
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
bluheart said:
I have been using CM7 as well as Devnull/Oxygen and I felt Oxygen was very stable, while CM7 26 was the most stable for me while 31 made my me turn back to Oxygen.
My sincere request, kindly take over from where Adam left Will be a great boon for us!
Click to expand...
Click to collapse
Agree......
Sent from my GT-I9100 using Tapatalk
Keep up the good work!
Nice work buddy
I turn my back for 1 day and you're nearly done! Keep it up
does it have a aosp lockscreen only?
Always nice to see more AOSP love will be keeping an eye on this, good luck man no wifi would be a dealbreaker for me ATM..
wliu88 said:
does it have a aosp lockscreen only?
Click to expand...
Click to collapse
yup, I've added nothing to it, pure aosp.
Hi! I'm trying to reproduce this compilation but no success. It stucks with a lot of libs errors. Any idea? I'm using a little modified device configuration from android_device_samsung_galaxys2.
Sent from my GT-I9100 using XDA App
I spent some hours testing files responsible for BT audio streaming from TeamEOS CM10 builds (the feature works there) on the official CM10 nightly builds.
Finally after couple of the ROM re flashes I found what file can be transfered from the TeamEOS builds to get the BT audio streaming working.
The workaround to fix the issue:
1. Download and unzip the file: http://www32.zippyshare.com/v/8042271/file.html
2. Copy the file "audio_policy.conf" to device root/system/etc
3. Reboot the Prime
Let me know if this fix works also for you.
The files are taken from the Team EOS "EOS-tf201-20120814-38" build file. Thank you guys.
Super... will check it out ASAP and will try to merge into CM10
this works... though you only need to replace ""audio_policy.conf"".... the other are not needed!!
Does that mean, the BT hasn't worked yet for CM10 or is that a fix for the known BT-bugs?
I often get BT-interruptions when streaming music to my AV-Receiver. Specially under heavy use (surfing the web for example...). Anybody else mentioning this problems?
craigacgomez said:
this works... though you only need to replace ""audio_policy.conf"".... the other are not needed!!
Click to expand...
Click to collapse
Will try with policy. conf again, first time during my tests it didn't work, probably I did something wrong that day. Thanks for feedback.
EDIT:The first post corrected as per Craig's findings
Thank you! I can listen to Pandora again
Just out of curiosity, would this also work with a touchwiz/stock version of a Rom as well? Thanks!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Fixed bluetooth problem, now all phone calls are on speaker phone
Sent from my SAMSUNG-SGH-I717 using xda premium
dafoxs said:
Fixed bluetooth problem, now all phone calls are on speaker phone
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Tell me step by step what you did to fix the problem? I've tried this and it still isn't working for me. I'm using the latest CM10 nightly.
seems the fix has been merged in the latest build (cm-10-20120912-NIGHTLY-tf201.zip)
http://review.cyanogenmod.com/#/c/22104/
eSbek said:
I spent some hours testing files responsible for BT audio streaming from TeamEOS CM10 builds (the feature works there) on the official CM10 nightly builds.
Finally after couple of the ROM re flashes I found what file can be transfered from the TeamEOS builds to get the BT audio streaming working.
The workaround to fix the issue:
1. Download and unzip the file: http://www32.zippyshare.com/v/8042271/file.html
2. Copy the file "audio_policy.conf" to device root/system/etc
3. Reboot the Prime
Let me know if this fix works also for you.
The files are taken from the Team EOS "EOS-tf201-20120814-38" build file. Thank you guys.
Click to expand...
Click to collapse
y u no gerrit this?
Entropy512 said:
y u no gerrit this?
Click to expand...
Click to collapse
It's already merged into CM10... was submitted to gerrit by Alex on Aug 25 and merged int CM10 on Sept 11... read the thread before posting.... the previous post already said that!!
craigacgomez said:
It's already merged into CM10... was submitted to gerrit by Alex on Aug 25 and merged int CM10 on Sept 11... read the thread before posting.... the previous post already said that!!
Click to expand...
Click to collapse
For whatever reason that post wasn't displaying then... Either way, this thread should never have existed and never made it to the portal. If the maintainer had been properly contacted, it would've only been broken for a night or two.
Entropy512 said:
For whatever reason that post wasn't displaying then... Either way, this thread should never have existed and never made it to the portal. If the maintainer had been properly contacted, it would've only been broken for a night or two.
Click to expand...
Click to collapse
Well, it was a trial and error and this thread was merely created as a possible fix... when it was well tested and finalised it was pushed to gerrit just 2-3 days later... yes, it did take time for the maintainers to accept the change and merge it in CM10, but I assume they were busy...
craigacgomez said:
Well, it was a trial and error and this thread was merely created as a possible fix... when it was well tested and finalised it was pushed to gerrit just 2-3 days later... yes, it did take time for the maintainers to accept the change and merge it in CM10, but I assume they were busy...
Click to expand...
Click to collapse
This fix doesn't work anymore with latest builds of CM10.
Hi,
I have this issue.
Does anyone has solution ?
Thanks
SpySpy01 said:
Hi,
I have this issue.
Does anyone has solution ?
Thanks
Click to expand...
Click to collapse
Strange, the "fix" has been implemented in the official CM10 build, I have no problem with my bt earphones since. Are you running the official build or EOS/Craigacgomez?
The Bluetooth stream seems to be pretty good, I connected it to my cousin's Infiniti EX35 and it was seemed to lose a little bass but other than that it was a pleasant experience.
Bluetooth streaming works fine on my iPhone 5 on my 2011 maxima. On the i4S it worked good too...no issues here
...on iPhone5/iOS6 via Tapatalk...
Will this 'audio_policy. conf' fix work on any phone and CM10 flavor?
Also, I noticed that with my CM10 ROM, the native audio_policy.conf file is in a root/system/etc/bluetooth folder, not root/system/etc. Does that make a difference?
The bluetooth issues that I'm having have to do with pairing as well as tons of loud static during calls.
Thx.
Sent from my LG-LS670 using Tapatalk 2
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
#include
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.
Submitting bug reports on nightly builds is the leading cause of male impotence.
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Instructions:
Your device will need to be rooted and have custom recovery before proceeding. Please check your device forum for instructions.
First time flashing CyanogenMod 12 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Already on CM12, try a dirty flash.
Reboot into recovery
Make back up <optional>
Wipe cache, system, dalvik-cache
Install ROM, GApps and optional Superuser app
Reboot
Download: CM12 nightly builds
Basketbuild - HERE
AndroidFileHost - HERE
Goo.im - HERE
There have been issues with Goo.im lately, if your download is corrupt or install fails then try the Basketbuild mirror.
Google Apps: Optional add on package that allows Google Play services such as Google Play Store and other Google Apps outside of AOSP based ROMs.
Check THIS post
Changelog:
CyanogenMod Change Log HERE
G3 Specific Change Log HERE
AndroidUser00110001 Change Log HERE
invsisblek Change Log HERE
GitHub - Source Code:
GitHub - CyanogenMod
GitHub - AndroidUser00110001
GitHub - invsisblek
Credits:
Thanks to all sent Paypal!!!
CyanogenMod
Thanks to @invisiblek for the work he has done on device trees.
Thanks to @timmytim for all of his work in getting CM11/12 to where it is now.
Thanks to @Cuzz1369 for all of his work on the d852 device tree.
Thanks to everyone who I have not mentioned yet...hard to keep track of XDA names and hangout names
Team Codefire for root.
TWRP for their awesome recovery.
Change Log & Other info
Personal Disclaimer:
I am the CM12 device maintainer for D850 so thought I would make this for the D852 users. It should be on par with the CM12 for AT&T G3.
I do not have this device in hand so bugs may take longer to resolve.
Whatever donations I get from this will go towards device so I can have one in hand to build with. If you happen to have a d852/5 for a fair deal then maybe we can work something out...
Bugs:
For proper technique on reporting bugs:
Read THIS and THIS.
When reporting a bug be as specific as possible, make sure you can replicate the issue coming from a clean install and that no other apps are causing the issue. Do not have any modifications done to the Android system besides the installation of GApps with out any other tweaks applied or apps installed. Provide a logcat if possible and make sure you are reporting on the latest build. This will make my job of trying to squash bugs a lot easier.
First! Thx u.. Cant wait to see the official name tag
What is the difference betweeen your build and Manups4e one?
Both are for D855.
Thanks
When i listen to music over bluetooth when i turn up the volume on the phone it gets very loud on the stereo. Blowing my Speakers up.. Common aosp bug?
Sent from my LG-D855 using XDA Free mobile app
pulcinella75 said:
What is the difference betweeen your build and Manups4e one?
Both are for D855.
Thanks
Click to expand...
Click to collapse
Not sure since I never ran it. I was asked to start making nightly ROMs for the D855 so I am... If it is causing any issues then I can just drop it. I am part of the group of devs working on the G3 device tree so I am looking to finalize the hardware side so we can push the device tree to CM.
Mennooo said:
When i listen to music over bluetooth when i turn up the volume on the phone it gets very loud on the stereo. Blowing my Speakers up.. Common aosp bug?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Have not noticed it but will look into it.
Please do NOT drop it, @AndroidUser00110001, I beg you!
Having an actual device maintainer here offering his time and work is awesome!
tobitege said:
Please do NOT drop it, @AndroidUser00110001, I beg you!
Having an actual device maintainer here offering his time and work is awesome!
Click to expand...
Click to collapse
Thanks...It's all good
Will have today's build up in about an hour.
I was not asking you to drop it. Only asking what are differences.
If it is a step towards official CM you are very welcome.
Yikes, out of thanks for today... @AndroidUser00110001 try this: 8DN66510WB1214140
tobitege said:
Please do NOT drop it, @AndroidUser00110001, I beg you!
Having an actual device maintainer here offering his time and work is awesome!
Click to expand...
Click to collapse
I will second this
Looking forward to see future updates.
Not sure if its a coincidence but is 00110001=1?
Helloworld294 said:
Not sure if its a coincidence but is 00110001=1?
Click to expand...
Click to collapse
It is
I am building for you guys so don't worry. I got a donation from a D855 user so now I am obligated too I would have anyways...
My machine is building today's version now. Will be up in an hour or so.
Is anyone having trouble seeing 5G WiFi networks?
what Device sources are you using?
Any chance of getting magnetic sensor to work for circle cover and other flip covers?
AndroidUser00110001 said:
Is anyone having trouble seeing 5G WiFi networks?
Click to expand...
Click to collapse
Nope, i see mine But i got problem with BT sound blowing my Speakers up.
Sent from my LG-D855 using XDA Free mobile app
bunny0007 said:
Any chance of getting magnetic sensor to work for circle cover and other flip covers?
Click to expand...
Click to collapse
Does it not work now? I thought it was being worked on, maybe the commit has not been merged yet. Will look into it.
Mennooo said:
Nope, i see mine But i got problem with BT sound blowing my Speakers up.
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Does the volume start too loud?
Mennooo said:
Nope, i see mine But i got problem with BT sound blowing my Speakers up.
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
when you start turning it up about 3/4 volume the volume start normal and then cranks up stupidly high lol
AndroidUser00110001 said:
Does it not work now? I thought it was being worked on, maybe the commit has not been merged yet. Will look into it.
Does the volume start too loud?
Click to expand...
Click to collapse
If i higher the volume over ~70% on the phone the volume is rising even if i lower it again so i have to turn it off. And the sound aint nice, its cracky and sounds aweful when it goes up. It was the same on liquidsmooth and ive tried it with my car, home stereo and a bluetooth speaker. All the same.
Sent from my LG-D855 using XDA Free mobile app
i'm just opening the first work form me.... after a lot of work and 10 times building with alpha testing versions ... and upgrading my laptop with more 8GB of RAM
Now the BETA version which almost everything works on Android 7.0
backup, wipe, flash and enjoy!
some known bugs like camera use another app... tell me..
Download:
https://www.androidfilehost.com/?fid=24727369092694064
Next Update will be here : ..
gapps:
http://opengapps.org/#
Android Version android-7.0.0_r6 (NRD90U)
Sources:
CM14
Kernel will be uploaded to my github and other device files.
G+ Community
Screenshots
Difference between this and Seraph's?
Thx...
More than one fingerprint possible to setup?
Thanks for your work. But I think you need to better organize your thread. The form is not good.
I think you need also to post your kernel source.
AllHailTony said:
Difference between this and Seraph's?
Click to expand...
Click to collapse
yes everyone did his work and his repos some maybe i had bug or he have that i dont or he dont
vergilbt said:
Thx...
More than one fingerprint possible to setup?
Click to expand...
Click to collapse
youre welcome.... in the future...
Yousvel said:
Thanks for your work. But I think you need to better organize your thread. The form is not good.
I think you need also to post your kernel source.
Click to expand...
Click to collapse
i will update and clean my thread ... thanks
Dont be so judgemental people. This guy tried to bring some Nougat love to us and instead got all the hate. I dont think asking what is the differences between this ROM and Seraph08's ROM is appropriate. But I do agree when posting ROM it is nice to have some info ahead of time
I can't believe fingerprint drama is still exist but hey! God gave us 10 fingers on the hands and not just 1
I always wonder what people hide in their phones that make them add more then 1 finger print It better be some hot girls nude photos
But I am not here to judge. Just being silly flashaholic :highfive: :silly: :victory:
Thanks for the ROM @sycolon
To register multiple fingerprints on any CM14 builds (I am using Grarak's build & have tried it on my own build):
1. Setup phone with 1 finger print
2. Go to Settings->Security to add additional fingerprints
3. When prompted to scan your finger, DO NOT PUT YOUR FINGER ON THE SENSOR - LONG PRESS THE FINGER PRINT ON THE SCREEN
4. It will prompt you to asking you to scan the finger print
5. Now place the finger on the scanner and it works!
Noticed battery/notification lights can't be changed to anything other than stock colors.. No errors, just doesn't change. Used multiple builds.. Likely known, just throwing it out there.
hackworks said:
To register multiple fingerprints on any CM14 builds (I am using Grarak's build & have tried it on my own build):
1. Setup phone with 1 finger print
2. Go to Settings->Security to add additional fingerprints
3. When prompted to scan your finger, DO NOT PUT YOUR FINGER ON THE SENSOR - LONG PRESS THE FINGER PRINT ON THE SCREEN
4. It will prompt you to asking you to scan the finger print
5. Now place the finger on the scanner and it works!
Click to expand...
Click to collapse
You are absolutely right...
Your workaround is working fine
sycolon said:
yes everyone did his work and his repos some maybe i had bug or he have that i dont or he dont
Click to expand...
Click to collapse
I didn't understand a single bit of what you said
is google now on tap working?
VxIA0NGXXV said:
is google now on tap working?
Click to expand...
Click to collapse
Yes it works.
Dev, the camera does not work, it says it is impossible to connect, or use by another app, or error opening the driver(camera fv-5). And function to swap the "back" button and the "review" is reset after a reboot.
setcon said:
Yes it works.
Dev, the camera does not work, it says it is impossible to connect, or use by another app, or error opening the driver(camera fv-5). And function to swap the "back" button and the "review" is reset after a reboot.
Click to expand...
Click to collapse
I'm on grarak's build 14.09. Goolge cam works, but not video with 4k. For that I'm using Footej Cam too.
network drop bug still exist? i am on mokee marshmallow rom i had tried many ROM and almost every ROM has network drop issue please tell me if anyone already has flashed this ROM i need to know....sorry if i hurt anyone by asking questions
Sent from my ONE A2003 using XDA-Developers mobile app
binoysankar said:
I didn't understand a single bit of what you said
Click to expand...
Click to collapse
He means seraph may be having some bugs and he may have some bugs. They may be common or different.
pk-air said:
I dont think asking what is the differences between this ROM and Seraph08's ROM is appropriate.
Click to expand...
Click to collapse
I totally agree with you that all developers should get love and not hate since their efforts make our lives better, but please excuse me, how on Earth is asking for information inappropriate? Asking someone for information is what differentiates us from the apes.
I know XDA have rules prohibiting "Is A or B better?" questions, but it's perfectly normal to ask what the objective differences between the ROMs are, especially since many devs don't provide this info in the OP. For example, if one ROM has working GPS and the other ROM doesn't, that is perfectly neutral and objective information.
With all my humble respect to all developers, I think it's much more inappropriate to publish ROMs on XDA (=public domain) without listing the known bugs in the OP, and taking the "flash-and-see-for-yourself"-approach.
If you, as a developer, choose to use a public domain like XDA to publish your work, please be transparent and take 5 minutes of your time to honestly list all your achievements and failures.
If you choose not to, you have no right to be mad at people asking those questions over and over and over again.
And imho this applies to all devs, including the current one as well as @Seraph08 as well as any other %username%. All I'm asking for is honesty and transparency, and I truly believe with all my heart that's not asking for too much.
I remember back in the days of Android 2 this was an unwritten code all devs on XDA went by.
But then competition got high and someone discovered he'd get more community creds if he kept quiet about his failures...
I always wonder what people hide in their phones that make them add more then 1 finger print It better be some hot girls nude photos
Click to expand...
Click to collapse
I think you misunderstood the concept of adding additional fingerprints The more FPs you add, the more fingers you can use to unlock the phone, which makes phone easier to unlock. If you have 10 FPs added, you can unlock your phone with any of them, not by using them all xD
Sent from my OnePlus 2 using Tapatalk
if you repo sync right now and build with grarak sources (it's clear you are using graraks sources..) you'll get broken ril and wifi.. dunno why
zsk.khan said:
network drop bug still exist? i am on mokee marshmallow rom i had tried many ROM and almost every ROM has network drop issue please tell me if anyone already has flashed this ROM i need to know....sorry if i hurt anyone by asking questions
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
I had these drops with the older builds. But with grarak's build from 14. sept. I have no drops anymore.
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.