yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] eurohunter:
Just wondering. Now that development for CM 13 has ended, which version of CM would be the most appropriate to install? The latest snapshot (10/13), the latest official CM nightly, or the unofficial version posted by haggertk?
[Samsung Galaxy S 5 Unified Development] Saber:
Unofficial CM13 is the best choice, it's the newest out of the three.
[Samsung Galaxy S 5 Unified Development] Lieutenantdaan:
Using 5 Nov nightly with xposed without any issues, try latest unofficial if xposed is not required
[Samsung Galaxy S 5 Unified Development] j1gga84:
You can also use latest unofficial with Xposed v87 that fixes the bootloop ;)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Where do I find the unofficial new builds? If they're by haggertk, I figured there would be a thread about it.
[Samsung Galaxy S 5 Unified Development] j1gga84:
Check this out:

http://xdaforums.com/showthread.php?p=69589353

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] Lieutenantdaan:
Great

Going to try it
[Samsung Galaxy S 5 Unified Development] ezantera:
Is there a way to have lockscreen like in touchwiz. Pattern lock and notifications on first screen.

Now i need to swipe then enter pattern, or pattern first without even a clock.
[Samsung Galaxy S 5 Unified Development] Qawnman:
Directly show pattern view

In lock screen options?
[Samsung Galaxy S 5 Unified Development] Triviox:
I need use "suhide 0.55" from Chainfire to pass Safetynet with Root / Xposed, and it dont work in Android 7; can please someone share with me the last CM13 nigth? In downloads web i only see CM14 nigth links :(

Thanks!
[Samsung Galaxy S 5 Unified Development] Qawnman:
Go back a few pages haggert posted a build with Nov security patches
[Samsung Galaxy S 5 Unified Development] Triviox:
Thanks bro, but i see others said that had problems with xposed (i had xposed systemless to passs safetynet); for that reason im try search the last official CM13 version ('casue works xposed), or other unnonffical where xposed works.

Thanks! :)
[Samsung Galaxy S 5 Unified Development] LGaljo:
I made unofficial build of cm-13.0, link to my dropbox.

There are no changes to repos in this build!

[MENTION=2693412]haggertk[/MENTION], if you don't like it, I can remove it :)
[Samsung Galaxy S 5 Unified Development] ezantera:
Directly show pattery removes weather and clock from first screen. In touchwiz I can see pattern, weather and clock directly on first screen. See screenshot.
[Samsung Galaxy S 5 Unified Development] Triviox:
Cant open it.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Xposed 87 works with the Unofficial build a few posts back. Unless someone saved a copy for the specific device you have, that's your only option

Sent from my SM-G900R4 (klteusc) running CM13 11.13.16 with xposed
[Samsung Galaxy S 5 Unified Development] gboros:
+1

Could you please post the link again?

When you say there is no changes to repo, you mean it is just synced with cm sources, just like nightlys?

Thanks!
[Samsung Galaxy S 5 Unified Development] LGaljo:
Sure :)

Now fixed
[MENTION=4635364]Triviox[/MENTION]
[Samsung Galaxy S 5 Unified Development] j1gga84:
What are the differences in this build compared to [MENTION=2693412]haggertk[/MENTION] 's latest unofficial?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
Removed as I duplicated the reply
[Samsung Galaxy S 5 Unified Development] LGaljo:
None, only repos are synced with upstream changes.
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
Hmm.. I am a bit confused rn, I was about to update CM 13 to CM14.1 via OTA but I do not know if I am going to install 7.1 gapps or do the ota update first then install 7.1 gapps.
[Samsung Galaxy S 5 Unified Development] shirioko:
why not both at the same time?
[Samsung Galaxy S 5 Unified Development] haggertk:
You can use OTA to download, but don't click on the install button. The OTA downloader will save it to /sdcard/cmupdater

Make sure you have both the cm14.1 zip and the gapps 7.1 arm 32 bit zip both downloaded to somewhere. After you have everything downloaded, reboot into recovery.

- install cm14.1 zip. Do not reboot now.

- install gapps zip

- wipe cache/dalvik

- reboot system
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
But how about the 6.0 gapps?
[Samsung Galaxy S 5 Unified Development] Behemoth1702:
Ignore. They are replaced by the 7.1 gapps.
[Samsung Galaxy S 5 Unified Development] Mendoka:
So... I saw on CM13 g900* topic and the rom had the same problem. So someone give it an option to reolve the nfc problem, that you can find here (don't worry. is very simple):

Enviado de meu SM-G900M usando Tapatalk

---------- Post added at 06:47 PM ---------- Previous post was at 06:41 PM ----------

Oh, man! Sorry. Wrong topic. D:

I'm confused using Tapatalk. -_-

Enviado de meu SM-G900M usando Tapatalk
[Samsung Galaxy S 5 Unified Development] ikzouhetnietweten:
anyone has the november nightlys of cm13? latest they have at cyanogenmod is of october. tnx.
[Samsung Galaxy S 5 Unified Development] phalkon30:
See link above. From November 12th,but I don't think there has been much cm13 development since then anyway. This at least has some security fixes

Sent from my SM-G900R4 (klteusc) running CM13 11.13.16 with xposed
[Samsung Galaxy S 5 Unified Development] haggertk:
The December ASB was released today. Once the AOSP drop happens and the changes are merged I'll spin another set of unofficial builds.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
Thank you !!!!
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
Well won't install CM 14.1 for now but I do have a another question. Well I will make a backup for CM 13 because I want to go back to stock rom so I could unlock my carrier. But I do not know if I will be losing 6.0 gapps or not once I go back to CM 13. So the question is... Will I be losing 6.0 Gapps even if I am going to restore from a TWRP backup (cm 13)? Also another question.... what should I backup before going back to stock rom?
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
it's stable.
[Samsung Galaxy S 5 Unified Development] phalkon30:
I really don't think there are any, it's very stable if you use the latest nightly posted this page (or a page back). Ignore the original post, he no longer maintains any if that info, and the cm website only has outdated snapshots.

Sent from my SM-G900R4 (klteusc) running CM13 11.13.16 with xposed
[Samsung Galaxy S 5 Unified Development] vedko:
TWRP makes a backup in a form of partition images, so everything on a particular partition will be backed up. That includes GAPPS.

As for which partitions to back up, system, data and boot should do.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
stable

i havn't found any issues so far

runs great on my daily driver SM-G900F
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
Okay. Thank you!!!

Also what should I wipe? So I can go to the stock rom.

EDIT:

Nevermind. I got it.
[Samsung Galaxy S 5 Unified Development] j1gga84:
https://android.googlesource.com/platform/cts/+/android-6.0.1_r77 ;)

Regards
[Samsung Galaxy S 5 Unified Development] kshanowski:
Are you patching all updates (critical/high/low) or only critical? I've found this post

https://thealaskalinuxuser.wordpress.com/2016/08/29/how-to-manually-update-your-custom-rom-source-code-with-security-updates/

about patching by hand step by step and only critical updates. What is your methodology? Do you have some resources you could share to help me patching cm with security updates? Thank you for your work.
[Samsung Galaxy S 5 Unified Development] haggertk:
Actually, CM doesn't spend a lot of time deciding which specific vulnerabilities to patch or not. Each month, when an ASB is released, a new proper release tag has to be identified. This isn't always the greatest value of "X.Y.Z_rN" in the Google naming scheme. The highest value _rN might be branched from an older point and may have an older patch release than some lesser value of N. /shrug

Once the "correct" release tag is identified then the fun work begins. CM has forked a number of repositories from AOSP. Since we're talking cm-13.0 here, I'll use that example. Looking at the manifest, there are AOSP repositories and CM repositories. Some of the CM ones are CM's alone, so that isn't an issue, but others are forked. For every forked repository, someone begins to merge in the latest changes. Once all of those merges are complete and pushed upstream, then the revision identifier in the manifest is updated -- this will change what is pulled from the non-forked AOSP repositories. This is the commit that, when merged, will signify that cm-13.0 source is up to the new patch level: https://review.cyanogenmod.org/#/c/175834/. I do almost none of this ^.

But that's only part of the battle. The ASB also notes a ton of CVEs that are found in the kernel and blobs. We cannot do anything about blobs -- that's up to the vendor and they may not always even update the blobs if they do push a release that updates the patch level.

As far as the kernel goes, we keep a tracking spreadsheet that is updated to contain the new kernel CVEs. Then it is up to each device (kernel really, in this case) maintainer to assess the CVE and determine if the patch needs to be added to his/her kernel. Some of the CVEs are only relevant to newer kernels and some don't have patches written yet for older ones, but the logic is essentially:

if (hasVulnerability && patchExists)
patchIt()

The good thing is that almost all of the kernels can take the same patch, so we place a link in the spreadsheet to the "proper" patch. These all come from upstream. Each maintainer marks when his/her kernel has incorporated that patch. There is logic in the spreadsheet to highlight how far behind one maintainer is as something of a public shaming (where public == the rest of the maintainers) of who hasn't done their job. I do have to do this ^ part.

So you see, CM doesn't spend a lot of time looking at the criticality of findings (read: CVSS scores or similar), we rely on Google to assess that. For the most part, if Google patched it, we patch it.
[Samsung Galaxy S 5 Unified Development] kshanowski:
Thank you, that sounds complicated. Anyway, there is some policy of cm I don't understand. Why after releasing cm 14 officially there is only old snapshot of cm 13 available, and for updates I have to did a long xda thread and luckly find your post with 'unofficial' build. As I understand releasing this updates is not simple and time consuming and a lot of people will never know about any updates.
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
I got a question. Will I lose the custom recovery if I go downgrade to 5.1.1 with ODIN?
[Samsung Galaxy S 5 Unified Development] vedko:
I'm not sure, never actually restored my phone to stock. But my guess would be that it rewrites audio the recovery partition.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
Yes
[Samsung Galaxy S 5 Unified Development] haggertk:
For those curious about Google release tag versioning, please read the commentary in this abandoned commit: https://review.cyanogenmod.org/#/c/175809/

So yes, r77 is not the droid you are looking for...
[Samsung Galaxy S 5 Unified Development] j1gga84:
Thanks for clarification ;)

So I guess it is the same with r75 and r76 or which patch does include the December security fixes?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Samsung Galaxy S 5 Unified Development] haggertk:
By all appearances, Google hasn't dropped a release tag with a Dec security patch level. Heck, these don't even exist:

https://android.googlesource.com/platform/build/+/refs/tags/android-6.0.1_r75

https://android.googlesource.com/platform/build/+/refs/tags/android-6.0.1_r76

¯\_(ツ)_/¯
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
I'm confused ...

So no cm13 Dezember unoffical build ?
[Samsung Galaxy S 5 Unified Development] rhyzan:
There will be no build as far as CM13 is concerned. The Devs have moved on to CM14. 1
[Samsung Galaxy S 5 Unified Development] omgbossis21:
I can throw out some unofficial builds for cms upstream changes and another if some new security patches are released. My wife is on a bit older cm13 build anyway and I was going to compile this week anyway, I'll just start the build before I leave the house. Let's leave haggertk to focus on his cm14 builds that seem to be going great, thanks for your hard work and time!
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
I know but haggertk mentioned, he would spill anohter unoffical, once the updates are there

Great ! thank you

i want to stay on my daily drive cm 13 as long as possible, once haggertk's awesome on cm14.1 is more stable, i'll move
[Samsung Galaxy S 5 Unified Development] omgbossis21:
I dirty flashed cm14 over top cm13 flashing the new gapps at the same time. Cm14 was very stable and had themes been implemented already I would of stayed with it.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
OK i will give it try wiht the next nightly !

THX :good:
[Samsung Galaxy S 5 Unified Development] KidKnowsTech:
K.. Thanks!!

So I unlocked my phone that is on 5.1.1 with Z3X Tool.. It was a success also upgraded to 6.0.1 and installed TWRP. But I want to go back to CM13 without losing my unlock thru restoring from backup ( my cm 13 backup ). So the question is.. do I lose the sim unlock if I restore with CM 13 Backup?
[Samsung Galaxy S 5 Unified Development] KappaDelaJulio:
Does anyone of you have the last official nightly of CM13 for KLTE?
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
unoffical build from [MENTION=2693412]haggertk[/MENTION] with Nov security updates can be found here

https://www.androidfilehost.com/?w=files&flid=128776
[Samsung Galaxy S 5 Unified Development] KappaDelaJulio:
Does this have the latest changes of cm13?
[Samsung Galaxy S 5 Unified Development] Behemoth1702:
Your answer is in the post you're quoting.

Jesus man this forum. People come here and all they say is "gimme!" without any kind words around that. And when they get what they want they dont even say thanks, they want the next thing.

Work on your manners!

Regarding OP: guys I have this issue that I never had before (on my i9300) and would be very happy if anyone who had the same experience would chime in on this.

I am running the latest unofficial nightly from this thread.

Taking photos (snap camera hdr, open camera, stock camera, storage is my external sd card) stops working after a few, quick shots. The app hangs for ~20 seconds. I use quickpic as my gallery and monitoring CPU usage I see that after every pic the processes "external storage" and "quickpic:service" peak. I have a 64gb class 10 micro sd card formatted in FAT32.

When I go into gallery apps (stock or quickPic) right after I take the pic - the pic is not there, only a grey placeholder. After 5secs or so I finally see the picture after refreshing the view. Deleting pictures one by one also does not work fluidly. I hit delete on a pic and it's still in the gallery for 3-5 seconds. Deleting multiple pictures one by one in a row freezes the gallery app.

So yeah, media handling is being weird on me. How can I test this better to find the cause? Would a catlog after this happening help?

Thank you a lot for all the hard work and I hope we can find out what's happening here.

Have a great day!
[Samsung Galaxy S 5 Unified Development] omgbossis21:
My Ubuntu virtual drive just completely crashed on me so I'm creating a new one. Probably for the best as I created this on something besides VMware and transferred it over. Now I'll be able to take advantage of my video card and video ram among other things. Bear with me as I get my environment setup once again.
[Samsung Galaxy S 5 Unified Development] haggertk:
There isn't a new AOSP release tag, but CM merged the Dec security fixes today. I kicked off unofficial cm-13.0 for all western variants. I'll post when they are uploaded.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
You beat me to it lol. Just finished setting up and syncing with CM and was about to start builds. Should of started fresh when I went to VMware, much smoother with its build and finally 1080p with capability of seeing both monitors!
[Samsung Galaxy S 5 Unified Development] haggertk:
Everything with the exception of kltevzw is uploaded (that's still uploading). Pick the device of your choice:

https://www.androidfilehost.com/?w=files&flid=52843

Let me know if any of you want a chn/chnduo/kdi -- I can build them, they just aren't commonly requested.
[Samsung Galaxy S 5 Unified Development] Drhedphuk:
Many thanks [MENTION=2693412]haggertk[/MENTION] greatly appreciated.
[Samsung Galaxy S 5 Unified Development] kshanowski:
Great, thx! Are there any chances for 05 December fixes or they are included in this one? Thank you once again.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Hmm. Well my builds crash since I update to the latest version. Its a maven error and debugging it using mvn clean install -x points to java. Of course this newer version uses java 8 and debug shows maven knows that. I tried to enable experimental java 8 in place of 7 so I'll try tonight and see what happens. Hate to reinstall just to go back to 14.
[Samsung Galaxy S 5 Unified Development] haggertk:
Are you sure you aren't getting bit by the maven certificate issue? See last comment here: https://review.cyanogenmod.org/#/c/174025/

I'm pretty sure the maven cert is half broken. Of course, nothing is going to get fixed in that area until after cm becomes $NEW_THING and is on new infrastructure.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
That's exactly it as it fails at the gello.apk! I've always stuck to the older version bc it worked but the little voice in the back of my head suggested I take the update! Thanks so much, if I hadn't found that I would of had to do it all again lol.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
No
[Samsung Galaxy S 5 Unified Development] ezantera:
Is cm14 so much better that cm13 needs to be flushed in toilet?

:eek:
[Samsung Galaxy S 5 Unified Development] phalkon30:
They do that to save resources so they're not building roms nobody uses.

But cm14 is the bomb! Unless you need themes or get annoyed by rotation bug, it's worth upgrading

Sent from my SM-G900R4 (klteusc) running CM14 12.18.16
[Samsung Galaxy S 5 Unified Development] Bluefreak1988:
Hey!

Since yesterday I can't open the recent app switcher.

In "Settings -> Buttons" it doesn't matter which button I define for this function, the recent app switcher doesn't appear.

So the problem is not a single button itself, it's a software function error.

I cleaned cache and dalvik as well. Nothing changed.

What else can I do? Or did I just deactivate something without recognizing it?

Built: CM13-20161105-nightly-klte

Best regards!
[Samsung Galaxy S 5 Unified Development] phalkon30:
If you don't know what changed to break it, try dirty flashing your rom again and see if it's fixed

Sent from my SM-G900R4 (klteusc) running CM14 12.18.16
[Samsung Galaxy S 5 Unified Development] mattnin:
Is USB audio not working on CM13? I am running the last official snapshot and trying a FIIO K1 DAC and it's not working :( It works fine on my LGG4 on CM13.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
question regarding the CM shutdown

will the CM13 be "ported" to lineage OS as well ?
[Samsung Galaxy S 5 Unified Development] haggertk:
The entire source, including all branches, has been cloned to LineageOS github repositories. There were some (few) devices still going cm-13.0 development, so rebranding might be applied to the cm-13.0 branches. Cyngn Inc. were the ones patching cm-13.0 with ASB fixes, so it's unclear if anyone will still do that. Development on cm-13.0 was nearly dead as it was.

At a bare minimum, the source will still be buildable.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
OK thanks,

lets hope we get LO 14.1 stable soon, than cm 13 is not needed anymore
[Samsung Galaxy S 5 Unified Development] zazolo:
hi everybody

I run one of the latest cm 13 versions on my g900f

everything is working fine, I have only a little problem with sd card management

if I try to write files using any file explorer, at the end of the process (which seems to go fine) i cannot access to the memory card. I then need to restart and find that files are the same as previous (folders and files I copied aren't anywhere).

same thing if I connect the phone to a pc, when I disconnect it, sd card is not mounted anymore

I was waiting for a stable 14.1 to upgrade

now I see lineageOS, should I install it instead?
[Samsung Galaxy S 5 Unified Development] martinisok:
Hi I'm running official cm13 is there a way to fix the big txt on this notification?
[Samsung Galaxy S 5 Unified Development] mattnin:
Is USB audio working for anyone? I just tried connecting to a DAC, no dice... I'll see if I can make it work!
[Samsung Galaxy S 5 Unified Development] romyg:
PSA: if your still using cm13, make sure you turn off Privacy-Cyanogenmod statistics-Stats collection. I was having long wakelocks and battery drain due to this. Likely it's an issue with the cm servers no longer accepting stats...
[Samsung Galaxy S 5 Unified Development] phalkon30:
I'm running cm14, had that enabled too! Thanks for the heads up

Sent from my SM-G900R4 (klteusc) running CM14 12.18.16
[Samsung Galaxy S 5 Unified Development] FirebirdDE:
I've just tried compiling my own Lineage 13.0 for klte using the vendor files from [MENTION=2693412]haggertk[/MENTION]'s latest cm13 build; both using the latest revisions from the m/cm-13.0 branch and the revisions that were most recent when the latest inofficial build was released. In both cases, after installing the rom, the first boot proceeds fine until the "Starting apps" message and then hangs, with logcat reporting over and over that

ServiceManager: Waiting for service media.audio_policy...
AudioSystem: AudioPolicyService not published, waiting...

Mediaserver shows up in the process list, and if I manually hack logcat output into mediaserver's startup function, it appears that it is actually stuck starting CameraService.

My aim is to eventually integrate the patches from the latest security bulletin manually, but I'm already stuck at this stage. Did anyone experience a similar problem?
[Samsung Galaxy S 5 Unified Development] Sudhakar@12345:
I build it total adding themuppets vendor files without any problems. If you want, I can upload it later. But flashing on your own risk. I can't give any support.
[Samsung Galaxy S 5 Unified Development] FirebirdDE:
Thanks. I'd prefer to use my own build - no offense meant, but using unofficial builds by someone whom I don't know kind of defeats the purpose of integrating the latest security patches :) But I'd appreciate if you could tell me when you did the repo sync you've based your build on?! It'd be a great improvement if I'd have a code base that is known to work for others. (At least I'd know for sure that there's an issue on my end then.)
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Did you pull blobs off your phone? TheMuppets host them for a variety of phones I use them for most my builds as well.
[Samsung Galaxy S 5 Unified Development] Sudhakar@12345:
Kein Problem :)

I used this repo: github.com/LineageOS/android.git -b cm-13.0

and this is my roomservice.xml:

I used theMuppets Blobs, didn't use extractfiles.sh
[Samsung Galaxy S 5 Unified Development] dasGrillrippchen:
Is there any way to re-enable cmroot for apps in developer settings? Someone patched it out of the sources and on my own build it is missing now. I don't want supersu...
[Samsung Galaxy S 5 Unified Development] haggertk:
export WITH_SU=true environment variable before compiling.

This is explained in the commit. As is the fact that we will soon have an official su add-on zip.
[Samsung Galaxy S 5 Unified Development] dasGrillrippchen:
Thank you very much. I will try later :)
[Samsung Galaxy S 5 Unified Development] gboros:
Is someone still building Cm13? If so, cares to share?

Thanks!