yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] O.G:
I think there is no benefit. I root my devices to become more controle of the System. The only benefit between root and no root is, you cant crash the system by delete ore costemise youre system settings. But if you dont touch areas where you dont know what to do, you cant destroy anything . At last its youre choice, but i would like to have root.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
This is a very known issue. [MENTION=5604178]zwliew[/MENTION] has been working on a fix for a while, but since he has his personal stuff, it's not done yet. The best thing is wait until it gets fixed.

---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------

can't you just wait, like, a third of a second? :confused:
[Galaxy S 4 i9505 Original Android Development] charm-:
Hi.

How is it possible to flash/install stweaks on this ROM? I tried downloading it from the play store but it says no kernel support. Is it possible just to flash another kernel while having this ROM? And what kernel will work?

Thanks a lot!
[Galaxy S 4 i9505 Original Android Development] Catscratch:
Nope.

If you want sTweaks. Try optimized CM13 located in the forums here. It comes with another kernel.
[Galaxy S 4 i9505 Original Android Development] brkn:
Hey, I hope I am not getting cruzified, but anyone know what the current state of this build is compared to the optimized version regarding stability and battery life.
[Galaxy S 4 i9505 Original Android Development] Catscratch:
You may ask, of course.

I compared this CM13 with stable-3 of optimized CM13.

See here: http://xdaforums.com/galaxy-s4/i950...enmod-13-0-t3334475/post68550555#post68550555

The result was, that I still use non-optimized CM13 because of better performance and battery life. Maybe things changed in stable-4. I don't know.
[Galaxy S 4 i9505 Original Android Development] brkn:
Thank you.

I am thinking about switching to the non-optimized CM13, because the changes done seem to be too severe. At least I feel like making changes on system level affect the stability more than they should, compared to what I am reading on other custom roms or rooted devices.
[Galaxy S 4 i9505 Original Android Development] A838:
[MENTION=5604178]zwliew[/MENTION] While trying to build cm 14, config_ui_blur is causing a problem with my build at device/Samsung/jf-common/overlay/frameworks/base/core/res/res/values/config.xml of the source. There is a note on the line causing a problem saying I need additional hardware specific code. Where could I obtain this, if you know? I would be very happy if somebody could help.

Thank you.

I don't know who to ask, and I know this is the wrong thread, but I think people don't like to be disturbed on pm.
[Galaxy S 4 i9505 Original Android Development] rrapidsharre:
Local contacts gone!

Hi, I installed OptimizedCM-13-20160806-jflte-Aroma-STABLE2 and open_gapps-arm-6.0-stock-20161015

everything is working just fine but

1) I miss gallery stock app

2) I cannot add contacts to my local storage (phone itself), I only have google account option

Can anybody tell me how to enable local storage, I do not want to add contacts to my google account.

Thanks
[Galaxy S 4 i9505 Original Android Development] echo_21:
Please post your question in the corrrect thread

xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-optimized-cyanogenmod-13-0-t3334475
[Galaxy S 4 i9505 Original Android Development] rrapidsharre:
I am sorry for the mistake and thank you
[Galaxy S 4 i9505 Original Android Development] Mrkblo:
Just a heads-up for those going from Official CM13 to OptCM13, miracast functions in OptCM13 are broken (at least in the Stable4 build). You'll get video through your wireless display, but no audio. I've tested Official CM13, Slim6 and WizCyan roms, all of them work without issues with my device (a LG Smart TV), with both image and audio going through the TV. With OptCM13, the image is sent to the TV but audio remains going through the phone speakers, which to me is a deal breaker as I constantly use my TV to listen to music. I have warned the dev, but it doesn't seem like it's ever going to be fixed as OptCM14 builds are already out of the kitchen.
[Galaxy S 4 i9505 Original Android Development] kxymm:
How are the battery life in the last cm13 ROM? Is better of a optimized?
[Galaxy S 4 i9505 Original Android Development] zwliew:
The build fix (actually simply a partial revert) has been merged. Resync and rebuild.

Do take note that you'll need this SELinux patch in order to boot: http://review.cyanogenmod.org/#/c/158323/
[Galaxy S 4 i9505 Original Android Development] A838:
Unfortunately, still getting errors.

Make leaves kernel directory, then says dtb not enabled kernel modules not enabled, the stops the build.
[Galaxy S 4 i9505 Original Android Development] worms:
I'm the only one with stock clock crashing?

I also tried to remove with titanium and then install from playstore.

No way, it will no install from playstore.
[Galaxy S 4 i9505 Original Android Development] Hemuli:
cm-13.0-20161022-NIGHTLY-jfltexx.zip download seems to be corrupted since the file size is only ~100 MB and the checksums don't match.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
+1

Confirmed both https://download.cyanogenmod.org/?device=jfltexx and https://www.cmxlog.com/13/jfltexx have 2016-10-22 corrupted file ... :(
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Since you've mentioned this build, I got to say: man, this was probably the build with the most commits related to jf kernel that I've ever seen. If I've counted correctly, there has been 66 commits (well, 65 commits and one revert) related to F2FS. Amazing work, [MENTION=5604178]zwliew[/MENTION]! Thanks for your work, I really appreciate it.

About the zip, yes, it is corrupted. Maybe wait another day to get a new build, I think.
[Galaxy S 4 i9505 Original Android Development] Hemuli:
They share the same link so no wonder they both have it corrupted. ;)
[Galaxy S 4 i9505 Original Android Development] Plonkyplonk:
Speaking of this, has anyone tried f2fs with encryption and adopted storage and latest twrp?
[Galaxy S 4 i9505 Original Android Development] zwliew:
I'm running exactly that configuration on CM 14. It's quite likely it works fine on CM 13 as well.

There are some VoIP patches otw that could fix the VoIP issues. I just haven't fully reviewed the patches and verified them.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Yes its not just a corrupted copy ... its the original :cool:
[Galaxy S 4 i9505 Original Android Development] KelvinM21:
U have cm14?!
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Good evening every1 :)

2 questions:

1. Does any1 know if CM13 works with MicroG? And if yes, anything attention should be payed to?

2. Is there any more Snapshot incoming for CM13?

Thanks :)
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
Uuuh, yes, he's one of the devs behind CM14 for jflte, what did you expect??
[Galaxy S 4 i9505 Original Android Development] subscope:
Hey guys i am thinking return to stock cm13 :) I would like to know first if camera bug disconnection was already solved and what the most stable version rom (less bugs)? thank you :)
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Any of the last builds is stable, just pick one ;)
[Galaxy S 4 i9505 Original Android Development] subscope:
I flashed 21/10 build cause 22/10 is corrupt :S let's boot it now eheh thank you for your respond :)
[Galaxy S 4 i9505 Original Android Development] side:
hey [MENTION=5604178]zwliew[/MENTION]

reverting those commits:

https://github.com/JDCTeam/android_...mmit/5376f38eaf0db3d874b53614a268a3e73dc4cdb8

https://github.com/JDCTeam/android_...mmit/a9e0743b37fc8c612c133ceacce6337d27392a47

https://github.com/JDCTeam/android_...mmit/ae6a794748ba456c98bec6992256da6f9fd508d6

https://github.com/JDCTeam/android_...mmit/1e10ffc31736d12ddc830e4d612172c88126149b

gave me stabler camera.check them if u want.i didnt spend time to fix the commits cuz i am working on cm14.

Cheers mate : )

i havent stopped optcm13.final version is coming in next week....miracast is fixed too.
[Galaxy S 4 i9505 Original Android Development] psys-saiz:
I am running that configuration for several months now (except twrp, version 3.0.2 does not work for me, v3.0.0 works but iirc not reliably from the cmupdater).

I am running 20161015-nightly. (Couldn't get 22s yet due to file-corruption, weird that this just happened coincidentally with the dirty cow-fix.)
[Galaxy S 4 i9505 Original Android Development] aviallon:
Thanks a lot !

Wow man, that was fast !

In how many month do you think that cm14 nightlies will be out for jfltexx ?

(btw, can you please give me your build procedure for jfltexx, a one that never fails... i'm having several issues with archlinux, like a succesful clean build that doesn't boot...)

Have a good day, and I thank you for what you're doing !
[Galaxy S 4 i9505 Original Android Development] charm-:
I'm on cm12.1 snapshot and on Alucard kernel, they work great. If I update to cm13 nightlies will the kernel remain or it will be switched with the cyanogenmode one?
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
It'll be swiched.
[Galaxy S 4 i9505 Original Android Development] robertogl:
[MENTION=5604178]zwliew[/MENTION] can i ask you news about Cyanogen 14.1? Not release date (of course), but i've seen that there are commits on cyanogen 14.1. Will cm14 be abandoned in favor of 14.1?
[Galaxy S 4 i9505 Original Android Development] Hemuli:
Is there a way to lower mic gain for recording in a loud environment (e.g., live music or rehearsals)? I'm using Voice Recorded by Splend Apps, which lets me select Camera microphone as the audio source. The sound recorded is surprisingly high quality stereo sound, but it gets distorted at earbud volumes. I've read that some phones have an autogain feature, which can be disabled to avoid distortion. I still want the phone to remain usable as a phone so the changes should be quickly reversible or only affect the selected audio source. This seems to be a common problem for Android phones.

E: Probably something in /etc/mixer_paths.xml?

E2: I set ADC4 Volume and ADC3 Volume values from 3 to 1 under camcorder-mic. Distortion disappeared in my headphone micing tests, but this is not a proper environment. I assume that setting the value to 0 would disable audio completely and the DEC values under 100 cannot cause any distortion. (Is this correct?)
[Galaxy S 4 i9505 Original Android Development] Mastroaldo70:
Hello guys, but only happens to me, I can not to download the "cm-13.0-20161022-NIGHTLY" firm and there is no other update .....

I ask you something, I need a good app to record phone calls, received and outgoing. That functions automatically, have no visible icons. I tried ACR, but does not satisfy me ...

Possibly for free ...
[Galaxy S 4 i9505 Original Android Development] sjamie:
Although it is not free, this is the app you want for flawless recording capabilities.

https://play.google.com/store/apps/details?id=com.skvalex.callrecorder
[Galaxy S 4 i9505 Original Android Development] zwliew:
You should be able to build and boot fine with just these 2 patches: http://review.cyanogenmod.org/#/c/167358/ and http://review.cyanogenmod.org/#/c/167359/

Yeah. I'm trying out CM 14.1 as we speak.

Although Android 7.1.0 is exclusive to the Pixels, nothing is stopping CM from getting a taste of that new Nougat release :)

The build servers were down for a while. Either install the 21st build, or the upcoming nightly.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
cm-13.0-20161027-NIGHTLY-jfltexx.zip is up and it is not corrupted, yay!
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I thought Google is going to release 7.1 for all devices.

I know the one that comes with the Pixel is a modified version specially made for it, similar to what Samsung and other OEM are doing, but I'm pretty sure 7.1 will be publicly available to anyone who wants to use it.

The dev preview for the Nexus devices is already out. So it take it from that that it won't be exclusive to the Pixel.
[Galaxy S 4 i9505 Original Android Development] ts_firehawk:
I think he meant that currently 7.1 is exclusive and we may get some Pixel-like features when it gets avaliable.
[Galaxy S 4 i9505 Original Android Development] robertogl:
We have sources, so it is available for everyone. Technically OEMs could get before nexus...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] side:
pink screen is usually occured by kernel panic.provide your last_kmsg please
[Galaxy S 4 i9505 Original Android Development] zwliew:
The current 7.1 release is exclusive to Pixel. Google won't certify any other devices released on it.
[Galaxy S 4 i9505 Original Android Development] robertogl:
Oh I didn't know, thanks...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] adrisouto96:
I have a problem when receiving a call. When I put the phone on my ear, screen turns off, but when I remove the phone from my ear, screen doesn't turn on and my phone seems to be freezed. The only way I have to turn the screen on is to remove battery and reboot the phone. This also happens with Telegram audios.

¿can you help me? Thanks
[Galaxy S 4 i9505 Original Android Development] walttheboss:
You need to fix/clean your proximity sensor. Very normal problem. NOT related to the ROM.

Install proximity fix app and try.

If not the look on YouTube on cleaning s4 proximity sensor.
[Galaxy S 4 i9505 Original Android Development] Chris_k:
I'm in my 4'th week on this ROM and I love it! But there is a problem with Bluetooth... When i connect to my car's infotainment system (or any other BT handsfree-device for that matter) the in-call sound disappears... People can not hear me, and I cannot hear them... This problem is only fixed by rebooting the phone, and will appear again the very instant I connect to a BT-handsfree again.. This problem does not apply if i connect a Bluetooth unit that only streams sound/music - it seems to manifest when connecting BT-units that utilize the "phone" functions...

I've tried the phone with three different HF-sets so I'm certain that the HF-units are OK (they all work on other phones, and did work on my S4 when i ran stock ROM)... I'm sure that this issue has been reported or discussed in the threads other 300 pages, but does anyone have a fix on this? I really need a working Bluetooth...
[Galaxy S 4 i9505 Original Android Development] Chris_k:
Yes, GT-I9505... I live in Norway, so I downloaded the jfltexx from the get.cm site (that's the version we have here)... I'm not on the latest nightly though, I'm running latest snapshot (cm-13.0-20160820) - could that be the reason? (I've been avoiding nightlies and try to keep to the more stable builds)...
[Galaxy S 4 i9505 Original Android Development] Mittaa:
I'm not a heavy BT user, but in general nightlies is stable.

You could make a backup of your current rom (TWRP) and then try to flash latest nightly :good:
[Galaxy S 4 i9505 Original Android Development] 1nf1nity:
So the latest update (cm-13.0-20161102-NIGHTLY) has in change log, commit with such description "Merge "DO NOT MERGE: disable tests that fail on some devices (Hammerhead)" into marshmallow-cts-dev"

So should it be merged or not ? :D
[Galaxy S 4 i9505 Original Android Development] ricardo404:
S4 locking and turns off after some time loading the battery

After last nightly (cm-13.0-20161029), while charging the battery, a few hours later, when I'll see if s4 is loaded, he is locked and buttons also lockeds, forcing me to take the battery out and reboot. I have already installed the last nightly but the error still continues. Someone with the same problem?
[Galaxy S 4 i9505 Original Android Development] Chris_k:
Thanks :) I'll try to flash the latest nightly and see if the phone behaves better ;)
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Is there any info about what's up with the build servers?
[Galaxy S 4 i9505 Original Android Development] Mittaa:
It think we have some failed builds and some timeouts (1½ hour) ...

http://jenkins.cyanogenmod.com/job/android/buildTimeTrend
[Galaxy S 4 i9505 Original Android Development] michiel1995:
Bluetooth audio volume

Hi Folks,

I've been running CM13 since last week, and I experienced a minor bug with bluetooth.

When the volume slider hits the middle it drops the volume to the minimum,

It's hard to explain so i've made an awesome paint art of it.

Anyone else experienced this issue?

I had it both with the latest snapshot and the latest nightly clean installed.

[IMG="Volume slider"]http://i.imgur.com/EJecH7T.png[/IMG]
[Galaxy S 4 i9505 Original Android Development] robertogl:
@zwliew , just a question: considering that cm14.1 nightly are starting for a lot of devices (not i9505), are you still on jfltexx, or have you switched to redmi 3s? It's just a question, so i can know if i should wait for official CyanogenMod or switch to optimized :)
[Galaxy S 4 i9505 Original Android Development] zwliew:
I'm mainly working on the Redmi 3S now, but I'll try to get the rest of the issues on jfltexx ironed out by the end of the week. If all goes well, expect 14.1 nightlies maybe, next week?
[Galaxy S 4 i9505 Original Android Development] robertogl:
Thanks :) No rush anyway, we can wait (well, i can...). I was only asking, so i know that we'll have official nightly ;)
[Galaxy S 4 i9505 Original Android Development] side:
Even if we don't have official nightlies, I am still here mate. ;)

Respect and love to zwliew
[Galaxy S 4 i9505 Original Android Development] robertogl:
Oh I know, S4 community is still alive ;)

Thanks to everyone working on it!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] A838:
I built cm14.1!

After a lot of persistence (there's not so many guides for building on mac)

View attachment 3932322

I finally did it.

It feels so good.

The difference between the one I cooked and JDC's is that this is from basically all cyanogenmod sources.

[MENTION=5604178]zwliew[/MENTION] did a lot of work on this rom, and I don't want to offend his work, so I will probably wait for him to upload, if he feels its right. (I know this contradicts what I just said, but if you PM me tomorrow I may send a link!)

EDIT: RIP me stuck at s4 logo ;(
[Galaxy S 4 i9505 Original Android Development] portaleus:
Yup, big thanks to [MENTION=5604178]zwliew[/MENTION] for his work on S4!
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
Great job!!!

Could you please post a guide how to do it? I have a fast MBP, and I would like to try it...
[Galaxy S 4 i9505 Original Android Development] francwalter:
Having the 14.1 in front of our doors, is the 13 nightlies dead? Or are there still some updates after the last nightly from Nov. 2?

Sorry if this has been asked and I didnt find.

frank
[Galaxy S 4 i9505 Original Android Development] robertogl:
Cm13 is now updated every week and not every night.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] zwliew:
I don't mind people releasing unofficial builds in this thread. :)

Also, to get it to boot, you need this WIP SELinux commit on Gerrit: https://review.cyanogenmod.org/#/c/167358
[Galaxy S 4 i9505 Original Android Development] Mitsch79:
Says who? At the moment there are no builds cause there are sources missing. Which makes jenkins abort the build process.
[Galaxy S 4 i9505 Original Android Development] glarage:
Hello,

I think, robertogl refere to this commit= https://review.cyanogenmod.org/#/c/169115/3/cm-build-targets
[Galaxy S 4 i9505 Original Android Development] robertogl:
Exactly.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] A838:
I have used "repopick -f 167358 167359" every time after a sync, and checked my local repository, to make sure that the command did what it should.

Unfortunately it still doesn't boot :(

Is there anything you could recommend I do? I can't see any obvious errors in the terminal.

If you have no clue as to why its not working, probably because I'm building on Mac.:p

P.S. I have cleaned built again, and I'll try to re-clean-flash
[Galaxy S 4 i9505 Original Android Development] side:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_jf-common refs/changes/58/167358/6 && git cherry-pick FETCH_HEAD

This should be enough.

not booting.......whats ur device tree ? u need both jf-common and jflte trees from CM github.

do you have the proprietary blobs ? (vendor/samsung)

That project is not coming from CM github but from themuppets's one :)

https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-14.1

also,always make clobber after sepolicy changes
[Galaxy S 4 i9505 Original Android Development] A838:
I think I have done all of that, but I will try using the alternative fetch command

EDIT: I put "<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />" into my roomservice.xml file, then synced and built it, is that correct? My build didn't work without it so I think it was right.
[Galaxy S 4 i9505 Original Android Development] A838:
[MENTION=5604178]zwliew[/MENTION] [MENTION=5968293]side[/MENTION] My device tree looks like View attachment 3934042

sepolicy folder :

local manifest:View attachment roomservice.xml

when I build I do

cd /Volumes/build/android/system
repo sync
. build/envsetup.sh
repopick -f 167358 167359
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server
brunch jfltexx

I have tried replacing repopick with

git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_samsung_jf-common refs/changes/58/167358/6 && git cherry-pick FETCH_HEAD

, but I don't think that makes a difference and I always delete the out folder before I build, although I have tried make clobber. Could there be a problem with my environment, even though I can successfully build, do you think? Are there any other things I need to have in my source, as I still can't boot(flashing the zip below)?

zip output using what I said above: cm-14.1-20161111-UNOFFICIAL-jfltexx.zip (md5) (this doesn't work for me)

:) thank you for helping so far, and I would really appreciate some more if you can offer it

I got a working build after fetching https://review.cyanogenmod.org/#/c/170402/ (setting selinux to permissive) I'll upload my build soon and I'll try to write a macos 10.12 Sierra guide too.
[Galaxy S 4 i9505 Original Android Development] KelvinM21:
Does that zip rom work?
[Galaxy S 4 i9505 Original Android Development] wurstherpes:
Don't work it stucks on black screen "Samsung Logo"
[Galaxy S 4 i9505 Original Android Development] geo741:
can we dirtyflash updates?
[Galaxy S 4 i9505 Original Android Development] jhonlouieuno:
Yes.
[Galaxy S 4 i9505 Original Android Development] Heathered:
Little offtopic,

I have one question, where CM13 keep values of screen brightness settings? On earlier Android versions this can be visible in build.prop...
[Galaxy S 4 i9505 Original Android Development] :
Slow charging problem

Message slow charging appears.

I measured it and its charging with 0.3A

Tried different chargers, everywhere this value.

Tried the chargers with different phone, there they work normally with 1,5-2,0 A.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Cable is important too! http://lifehacker.com/cables-can-significantly-impact-the-charging-speed-of-y-1532784722

Try with another cable :good:
[Galaxy S 4 i9505 Original Android Development] firenx:
Yep cable was my issue, had a cheap dollar store cable and my phone was Charing slooooow, spent $20 on a quality cable and now it charges fast :)
[Galaxy S 4 i9505 Original Android Development] Mittaa:
IMO it's best to use original cables from Samsung, because it´s very hard to find cables with proper specifications.

Even shops specialized in cables often don't know the difference between cables they sell.