CyanogenMod 13 for Galaxy S6

[Sebaxakerhtc]

can anyone post the latest update for S6 Edge? Where do i find the latest update ?

No updates. Just one build

 

[Deidaron]

someone posted this build here "cm-13.0-20160316-UNOFFICIAL-zerofltexx" and in the download section of cm13 is only this one " cm-13.0-20151221-UNOFFICIAL-zeroltexx.zip " so its obviously not up to date here.

So my question was where do i find the latest builds?

 

[denNorske]

someone posted this build here "cm-13.0-20160316-UNOFFICIAL-zerofltexx" and in the download section of cm13 is only this one " cm-13.0-20151221-UNOFFICIAL-zeroltexx.zip " so its obviously not up to date here.

So my question was where do i find the latest builds?

http://forum.xda-developers.com/showthread.php?p=65790066

It was posted here, it's not an official build, just a "preview" or so.

 

[Sebaxakerhtc]

So my question was where do i find the latest builds?

Answer:
For S6 edge just one build - cm-13.0-20151221-UNOFFICIAL-zeroltexx.zip

Else:

New Build for G920F/I (With latest updates and commits):

https://drive.google.com/file/d/0B16RSdsieBV9V1FKRURuRzhJWWs/view?usp=sharing

 

[AlexisXDA]

someone posted this build here "cm-13.0-20160316-UNOFFICIAL-zerofltexx" and in the download section of cm13 is only this one " cm-13.0-20151221-UNOFFICIAL-zeroltexx.zip " so its obviously not up to date here.

So my question was where do i find the latest builds?

Search in the thread

Inviato dal mio SM-G920F utilizzando Tapatalk

 

[MetalPhoenix45]

Look, I'm not trying to be rude, but please tell me if you're actually working on the rom.
I not know how to do what you do, and I know it's hard, but I have seen other threads that never finished from 2 years ago, so please give my a sign that you are still working on this if you can.

Just go to their github, not so hard man.

Sent from my SM-G920T using Tapatalk

 

[Astrubale]

Look, I'm not trying to be rude, but please tell me if you're actually working on the rom.
I not know how to do what you do, and I know it's hard, but I have seen other threads that never finished from 2 years ago, so please give my a sign that you are still working on this if you can.

Read the thread. They are actually working on this rom and some day ago they fixed the in call, and now there're working on camera.

 

[weedeater84]

damn, cant wait for stable build for our s6...
so strange that samsung's flagship and maybe the best phone ever,
not getting support.
any idea about stable build? when??
tnx for devs anyway, for they hard work

 

[nadejo]

Read the thread. They are actually working on this rom and some day ago they fixed the in call, and now there're working on camera.

is there any incall fix commit yet? i could not find any. ( i dont mean that older audio routing commit of the 16.3. build )

 

[Astrubale]

damn, cant wait for stable build for our s6...
so strange that samsung's flagship and maybe the best phone ever,
not getting support.
any idea about stable build? when??
tnx for devs anyway, for they hard work

Don't ask for eta please, that's spam and this post doesn't help the developers.

 

[nadejo]

so since its the weeknd, i will reinstall this rom and try to share some error logs here. i will reffer to the 920f 16.3. build.

 

[Fusseldieb]

What's the main problem for the camera? Sources that are missing to make the "driver" work? Which sources will be useful? Maybe I can try to e-mail Samsung about it, various times a day.

 

[nadejo]

I dont know why but whatsapp can suddenly play audio through the call speaker by blocking the sensors.
These are the logs the second one is the moment the sound comes out of the callspeaker

03-26 23:16:54.346 3473 4157 I MediaFocusControl: AudioFocus requestAudioFocus() from [email protected]@f2c6748 req=3flags=0x0

03-26 23:16:56.945 3473 4157 I MediaFocusControl: AudioFocus abandonAudioFocus() from [email protected]@f2c6748

Edit: Found this

03-26 23:24:42.647 3473 5024 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.dialer/.DialtactsActivity (has extras)} from uid 10081 on display 0

03-26 23:24:59.261 3473 4020 I ActivityManager: Killing 6931:com.android.dialer/u0a8 (adj 11): remove task

03-26 23:24:59.363 3473 5025 I WindowState: WIN DEATH: Window{d058654 u0 com.android.dialer/com.android.dialer.DialtactsActivity}

03-26 23:27:51.268 3473 5024 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.dialer/.DialtactsActivity (has extras)} from uid 10081 on display 0

03-26 23:27:51.339 3473 4157 I ActivityManager: Start proc 9158:com.android.dialer/u0a8 for activity com.android.dialer/.DialtactsActivity

03-26 23:27:51.495 9158 9158 W System : ClassLoader referenced unknown path: /system/priv-app/Dialer/lib/arm64

03-26 23:28:37.592 3473 5023 I ActivityManager: START u0 {cmp=com.android.dialer/.settings.DialerSettingsActivity} from uid 10008 on display 0

03-26 23:34:34.129 8947 9001 W PackageParser: No actions in intent filter at /system/priv-app/Dialer/Dialer.apk Binary XML file line #192


Found this line in the androidmanifest.xml file in dialer.apk
<receiver name=".interactions.UndemoteOutgoingCallReceiver">

Why should we recive outgoing calls. And how is that even possible
Edit: got it nothong wrong there

Also found this in the same file
<receiver name="com.android.incallui.NotificationBroadcastReceiver" exported="false">

And why is there also a line that, im sure, should not contain the name qualcomm?
<uses-library name="com.qualcomm.qti.smartsearch">

Is it possible that the dialer.apk isnt ment to work properly on exynos devices at all?

 

[hillbeast]

What's the main problem for the camera? Sources that are missing to make the "driver" work? Which sources will be useful? Maybe I can try to e-mail Samsung about it, various times a day.

Missing documentation and source code is what is missing. Samsung won't ever give it to you, no matter how much you ask. People have been asking since the Galaxy S2 for documention for their flagship phone and chipsets. Nothing has improved. It won't start now, and no amount of Change.org petitions will help either.

 

[synescu]

I've gotten a few PMs about the build environment, so I'm adding to my previous post. If you need any more help, you should probably poke around a more general AOSP/CM dev thread The CM Developer wiki is also a decent resource.

Follow this tutorial to set up your Linux build environment for MM: https://source.android.com/source/initializing.html

I also had to install Maven:

sudo apt-get install mvn

Initialize using the CM 13 branch:

repo init -u https://github.com/CyanogenMod/android.git -b cm-13.0

NOTE: many of the gerrit commits in the quote have already been merged, so you'll have to check cm-gerrit directly for any new changes

NOTE 2: I'm finding that the local_manifests files seem to behave inconsistently sometimes. I've had to go through each cm.dependencies file in each project and manually add it to roomservice.xml.

I " AM THE ONLY ONE that after a successfully compile nat getting a flashable zip? my out directory its like this
[email protected]:~/cm/system/out/target/product/zerofltexx$ ls
android-info.txt gen ota_temp recovery.id
boot.img install previous_build_config.mk recovery.img
clean_steps.mk installed-files.txt ramdisk.img root
data kernel ramdisk-recovery.cpio symbols
fake_packages obj ramdisk-recovery.img system
file_contexts obj_arm recovery system.img

 

[Trafalgar Square]

I " AM THE ONLY ONE that after a successfully compile nat getting a flashable zip? my out directory its like this
[email protected]:~/cm/system/out/target/product/zerofltexx$ ls
android-info.txt gen ota_temp recovery.id
boot.img install previous_build_config.mk recovery.img
clean_steps.mk installed-files.txt ramdisk.img root
data kernel ramdisk-recovery.cpio symbols
fake_packages obj ramdisk-recovery.img system
file_contexts obj_arm recovery system.img

Please a picture of terminal.
Did you see "make completed successfully **.**.**"?

 

[synescu]

Please a picture of terminal.
Did you see "make completed successfully **.**.**"?

Yes make coplited successfully .unfortunately I closed my terminal window

Sent from my SM-G925F using Tapatalk

 

[Trafalgar Square]

Yes make coplited successfully .unfortunately I closed my terminal window

Sent from my SM-G925F using Tapatalk

Lol.
There should be a ZIP. Start the compile again. Without make clean.

 

[synescu]

Lol.
There should be a ZIP. Start the compile again. Without make clean.

using prebuilt boot.img from BOOTABLE_IMAGES...
  running:  openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
  running:  java -Xmx2048m -jar /home/dece-bal/cm/system/out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpELL1Kn /home/dece-bal/cm/system/out/target/product/zerofltexx/cm_zerofltexx-ota-b169de9af5.zip
done.
Package Complete: /home/dece-bal/cm/system/out/target/product/zerofltexx/cm-13.0-20160328-UNOFFICIAL-zerofltexx.zip
make: Leaving directory '/home/dece-bal/cm/system'

#### make completed successfully (21:37 (mm:ss)) ####

this time I' have a zip

 

[sawdoctor]

Thread cleaned, please don't ask for eta's its against xda rules. Everyone else just use the RP button please and we'll deal with it

Regards
Moderation Team