yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9506 Android Development] solk2:
Call recording fixed in recent builds. But I don't think that supersu or superuser make difference to activate this in 3rd party apps. And as I remember they hardcoded call recording so that can't be overriden by system property. And it is disabled for Germany so the only way is to override it in device tree overlay in build time. This don't affect 3rd party apps though. So If you want I can enable call recording for Germany in stock Dialer or you can use some 3rd party app.
[Galaxy S 4 i9506 Android Development] solk2:
For now userspace RIL libs is from I9506XXUCNH2. So you better use this one. Also bootloader doesn't allow update of modem if status is set to Custom. To workaround this you need to flash stock ROM with this modem, wipe, run it for a couple of minutes and then flash one more time. At least I could update my modem only this way.

Also try to force 2G or 3G and try calls and messages. Just I don't have nor 3G nor LTE in my country so can't test it.
[Galaxy S 4 i9506 Android Development] neumann:
It would be great, if you could enable it for Germany.
[Galaxy S 4 i9506 Android Development] TechTune:
:(

http://xdaforums.com/galaxy-s4/help/help-i9506-network-rom-cm11-install-t2873115
[Galaxy S 4 i9506 Android Development] solk2:
So when you flashed stock ROM last time. Did hidden partition flashed or not? And which baseband is shown in settings?
[Galaxy S 4 i9506 Android Development] colorian:
Very glad to see this! Absolutely no reason at all why Cyanogen could "forget" to develop CM11 for the i9506 themselves, but they do. That's where this user's initiative comes in!

Works flawlessly so far, have installed it this afternoon. I'll report back with anything I might find.

Are there still things up for testing? I'm all in for contributing to the development of this ROM!
[Galaxy S 4 i9506 Android Development] TechTune:
I've been having problems with fail on hidden. The solution was to flash 4.4.2 NG3 with pit file from this post, http://xdaforums.com/showthread.php?t=2529064 and checked 'Re-partition'. The baseband is stock.

Think the problem is in the root procedure, I did something wrong, but I have no idea what.

M
[Galaxy S 4 i9506 Android Development] solk2:
Flip cover fixed in todays build.
[Galaxy S 4 i9506 Android Development] Kiryo24:
Nice work. Stable and nothing bad to say. Few Battery drain issues what i solved with greenify, denying google services wakeup rights and putting processor profile to ondemand but i noticed after reboot profile goes back to interactive "remember after reboot" checked or not.

Thank you for this port :)

[Edit] well now after few boots it seems to stay put but almoast every time before it went back to interactive and im sure i checked box.

Ps. Im on CM-11-20140905 build
[Galaxy S 4 i9506 Android Development] DualJoe:
Confirmed. Now tell me how to turn it off, lol. Just in case it fires up unintentionally or something. :) Maybe its quite cool indeed. Will give my home button some rest...

Do you know how it actually works? I cannot fool it by holding different things on the glass or any other attempts. It just works with the flip case indeed. Is there a permanent magnet or something in the covers?

Edit: Its a magnet indeed. Guess i have to test my GPS quality with closed cover. I hope it doesn't interfere.

http://forums.androidcentral.com/samsung-galaxy-note-3/357610-how-do-s-view-covers-work.html

Edit2: Hmm, first time ever i had battery drain. Over night it pulled from 30% to 0% and shut off. Maybe something's wrong with PowerHAL. It constantly pollutes the log. But i had it in previously releases as well without problems.

09-13 10:47:53.848 E/QCOM PowerHAL(770): Failed to acquire lock.
[Galaxy S 4 i9506 Android Development] mubeen_94:
Can we dual boot CM11 with TouchWiz 4.4 ROM? If yes, then how? Because I wish to test this CM rom without losing my current data on TouchWiz ROM

Edit: Okay I searched on YouTube and found a solution in the form of ROMSwitcher, but it is a tried and tested formula on the i9500. I will try it later. I just want to know if it is a safe means of flashing?
[Galaxy S 4 i9506 Android Development] diegodu27:
[MENTION=5291759]solk2[/MENTION] none of temasek builts work, they dont even boot, can you do something about it ?
[Galaxy S 4 i9506 Android Development] pille1:
It works perfect!!!

But I have encountered a minor bug : I can't upload pics to Instagram... :(
[Galaxy S 4 i9506 Android Development] DualJoe:
Drain for the second time. No one else experiencing that? Drain is assigned to 'Android OS'. Didn't happen on last image (from a week ago or so). Current build is 'cm-11-20140912-UNOFFICIAL-ks01lte.zip'.

Maybe its the flip cover. Will test that...

Edit: Rather looks like disabling the airplane mode.
[Galaxy S 4 i9506 Android Development] mubeen_94:
I think I will be opting to dual boot between TouchWiz 4.4 and CM11 using this method - http://xdaforums.com/showthread.php?t=2447534
[Galaxy S 4 i9506 Android Development] pille1:
[MENTION=5291759]solk2[/MENTION] can you try porting Paranoid or temasek for our device? I would be FANTASTIC
[Galaxy S 4 i9506 Android Development] Kiryo24:
Have you tried hard reset and clearing cache?
[Galaxy S 4 i9506 Android Development] colorian:
After a few days of testing (I installed the nightly from Sept. 10th), I've come to a few conclusions:

- WiFi works remarkably better on this ROM than on the Stock ROM. I'm around 10 meters away from my router in-doors through several walls and a floor up. Stock ROM had problems keeping a stable connection whereas this ROM has no trouble at all and keeps the connection fast and stable. Very, very remarkable!

- Battery seems to last remarkably longer than on Stock ROM even though I'm a "heavy user".

- The drops in battery percentage are highly irregular. Sometimes I can do 2 hours with one percent, at times it drops 10 percents in a few minutes. This sounds very much like a calibration issue, but I already recalibrated the battery to no avail... I might try again next time I see possibility to discharge and charge the battery all at once.

That's it for now. All in all a major improvement over the stock 'ROM' by Samsung...
[Galaxy S 4 i9506 Android Development] colorian:
In fact, one more thing I noticed earlier, but forgot: the unlock screen is always unresponsive for the first 0.5 - 1 seconds after turning on the device, meaning I cannot turn on the device and immediately swipe right to unlock. Is this intended behavior?
[Galaxy S 4 i9506 Android Development] memoryeffect:
My phone doesn't have this issue, maybe a clean install will solve it?
[Galaxy S 4 i9506 Android Development] colorian:
That's a possibility!

I might try that once I've done a full Titanium Backup.

I realised just now, but it could be due to the fact that I use ART instead of Dalvik.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
I changed to ART a week ago. I feel it has given better performance and battery life.
[Galaxy S 4 i9506 Android Development] mubeen_94:
How did you manage to change to ART? Could you tell me?
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Settings -> About phone -> tap Build number until it says Developer options have been enabled.

Go back to settings, browse down until you see "Select runtime". Pick "Use ART".
[Galaxy S 4 i9506 Android Development] mubeen_94:
I tried it sir, but I cannot find the Select runtime option in my device's developer settings.......is my devuce not supported yet? What should i do?
[Galaxy S 4 i9506 Android Development] stxfreak:
i thought cm doesnt support art?
[Galaxy S 4 i9506 Android Development] awicks:
If you try to change it to ART, a warning message pops up stating "ART is not officially supported by CyanogenMod as it is highly experimental and has the potential to cause instability, crashes, data loss or prevent the proper boot of your device. Visit [Introducing ART] for more information"

Andy
[Galaxy S 4 i9506 Android Development] mubeen_94:
Okay so I've been using the latest nightly since yesterday.........I managed to change the runtime to ART, so far no problems, everything works fine, no battery drain issues, no unlock screen delays, absolutely zero qualms.........great job solk2, the only problem lies with the camera, I absolutely loved the Sammy Camera and its modes, ah why don't we have it here........anyways its an absolute gem of a ROM
[Galaxy S 4 i9506 Android Development] pille1:
We Will never have sammy camera on cm and other roms because stock TouchWiz camera has all kinds of proprietary software driving it. That software is built into different parts of the rom and requires the TouchWiz framework to run.

Also you can try lenovo camera or snap camera hdr ;)
[Galaxy S 4 i9506 Android Development] mubeen_94:
Yeah I tried them, but didnt find them as interesting as Sammy's.........its a pity that we can't have it on any custom ROM. Camera was my main concern, so unfortunately I have to revert back to Stock TouchWiz and leave this beautiful ROM.........:(
[Galaxy S 4 i9506 Android Development] DualJoe:
What exactly is the Samsung Camera capable of what we don't have in 3rd party ones? I've seen high fps (60fps, 90fps) in cm camera but didn't test it yet. The 'scene modes' are not working at all here. 'Nightmode' is quite useful to improve quality on static scenes.

When i disable 'airplane mode' and switch it back on deep-sleep is dead (battery drain). I just use 2G/3G rarely anyway but its a greater bug nevertheless. Mpdecision/governors/dividers are not working properly. I guess there's a race condition or something. Touchboost locks at somewhat around 1.5GHz. Probably way too high. Maybe shouldn't even be enabled at all.
[Galaxy S 4 i9506 Android Development] solk2:
Will look into this. I just don't turn on airplane mode. So didn't noticed this bug. Anyway todays build eaten only 1% (WiFi, Mobile on, BT off, gapps location history turned off) while I was sleeping comparing to 8% before. There was bug with display init.

Mabe i'll can get my hands on camera now.
[Galaxy S 4 i9506 Android Development] solk2:
Don't have time to maintain two kernel. Not to mention two ROM. So sorry. Maybe this will change in future.
[Galaxy S 4 i9506 Android Development] awicks:
Whatsapp error

I am receiving the Whatsapp error informing me that my phone date is inaccurate. I had this occurring back in June, but then it stopped for a while until recently.

I did a fresh install of cm-11-20140828 last week and then updated via CM Updater to cm-11-20140918 today. The error appears a couple of times after booting.

Any ideas?
[Galaxy S 4 i9506 Android Development] solk2:
Fixed in next nightly. Forgot to update time_daemon.
[Galaxy S 4 i9506 Android Development] DualJoe:
Will this fix the timezone bug as well? Whenever i boot up the phone in airplane mode the clock is shifted by some hours until NTP/Internet kicks in. I think you once said its qcom specific and all these devices are affected. That timeshift might break the MX Player preview cache here regularly that is kinda annoying, but i'm not sure.
[Galaxy S 4 i9506 Android Development] solk2:
Don't know. Maybe. Try turning ofF setting timezone from network and set it manually.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Is it possible to retain the installed system font? I use rom toolbox pro for changing the font from default. Installing a nightly update restores the default font. Not a big deal for me to install my font again but just curious :)
[Galaxy S 4 i9506 Android Development] DualJoe:
Add them to a /system/addon.d script. Something like this (/system/ prefix is omitted):

[...]
cat <<EOF
fonts/AndroidClock.ttf
fonts/AndroidClock_Highlight.ttf
EOF
}
[...]
[Galaxy S 4 i9506 Android Development] neumann:
I updated from M8 to M10 and don't have any problems so far. I'm glad to see call recording enabled. Recording works, but I can only hear my own voice. I also tried:

setprop persist.call_recording.src 4

But it didn't work. Any advice what I can do?
[Galaxy S 4 i9506 Android Development] solk2:
Try nighties. Call recording fix could be not included into SNAPSHOT.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Weird thing. When receiving a call, the network disappears completely and no call comes through. Then a couple of seconds the bars come back, but there's no call through. Tried this with 3 different phone numbers.

Also when calling out, when pressing the call button, it calls but loses the network again and says "out of service area". But then the call comes through at the other end while the call at my end has disconnected due to the out of service area error message.

Turning airplane mode off and on + rebooting phone worked so that I was able to call properly. But couldn't call again or receive a call.

Rebooting fixed the issue again, but still can't receive calls. It seems a bit random, but there's definitely something wrong.

And this is with M8 from yesterday.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
I upgraded to M10 in hopes of it fixing the problem, but that wasn't the case.

Then I got android.phone and android.acore process force closing messages at rate that I couldn't do anything with the phone. Only option was to try wiping the cache in recovery which didn't help and I ended up factory reseting the phone.

I installed a July version to my phone and this fixed the problem. All calls worked fine again.

I then decided to test again by installing the latest update and the problem returned. So I think it's safe to assume that there's something wrong. These problems started after the 18th M8 update.

---------- Post added at 01:38 PM ---------- Previous post was at 01:19 PM ----------

Same happened with September 12th update. Will try again with the July 23rd update.

---------- Post added at 01:49 PM ---------- Previous post was at 01:38 PM ----------

Did a factory reset in recovery and installed July 23rd update. Tried calling multiple times both ways. No problems!
[Galaxy S 4 i9506 Android Development] solk2:
Going official. Device included today in cm upstream.
[Galaxy S 4 i9506 Android Development] mubeen_94:
Now thats something great to hear. Well done [MENTION=5291759]solk2[/MENTION]
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
So I may have located the problem. Installing the 20140906 nightly works just fine. It may be that the 20140907 call recording change that caused the problem?
[Galaxy S 4 i9506 Android Development] DualJoe:
Doesn't matter. It seems it doesn't even honor the 'automatic/date/time/timezone' settings at all. It always syncs the clock when going online.

Date with airplane mode booted is always "29.01.2014 - 19:56 GMT+1".
[Galaxy S 4 i9506 Android Development] solk2:
Time fix included in latest nighties. Or you can just download time_daemon from themuppets and replace it yourself.
[Galaxy S 4 i9506 Android Development] solk2:
There was some transition when this patch was included in cm upstream. Try later builds.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
As I mentioned earlier, I tried three (20140918 M8, 20140918 M10 and 20140912 M8) of the later builds, but had the same problem. Only when I went to early September, the problem got fixed.
[Galaxy S 4 i9506 Android Development] arter97:
Tell me you're joking.
[Galaxy S 4 i9506 Android Development] awicks:
I have just installed M10 over 20140918 and received constant UI and system force errors. Flashed 0918 back over the top and all seems well!
[Galaxy S 4 i9506 Android Development] leo_bsb:
I had the same issue, M10 didn't work for me.
[Galaxy S 4 i9506 Android Development] solk2:
Thats coz basicly your are downgrading. It needs fuul wipe.
[Galaxy S 4 i9506 Android Development] solk2:
Nope. Its there. Muppets, gerrit and so on.
[Galaxy S 4 i9506 Android Development] awicks:
How is it a down grade going from 0918 to M10? I thought that the M10 was a later release?

Does that mean that if I am running nightlies I shouldn't use the snapshot releases?
[Galaxy S 4 i9506 Android Development] solk2:
That depends from which nightly you are installing snapshot. If you had installed 20140831 nightly and then snapshot then you won't need wipe.
[Galaxy S 4 i9506 Android Development] awicks:
Is there any way of knowing whether it is safe to flash a snapshot release over a particular nightly?
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
I downloaded the M10 package, made a made a factory reset in recovery and installed the M10, but it still says I've M8 unofficial installed.

I also tried installing a July version first and then M10, but it's the same thing.

This all seems very confusing right now :D
[Galaxy S 4 i9506 Android Development] stxfreak:
I'm on 0910 and no matter how I flash m10 the phone reboots, tells me some services shut down and goes into bootloop :(
[Galaxy S 4 i9506 Android Development] DualJoe:
Try retriggering dexopt by clearing dalvik-cache in recovery. Make sure it kicks in at bootup as some recoveries might be buggy and don't really clear the cache. You know its working when apps get counted up at bootup. If this doesn't help you might have data corruption due to improper shutdown/crash. If things like 'packages.xml' get corrupted there's nothing but a factory reset (clear /data).
[Galaxy S 4 i9506 Android Development] Kiryo24:
Same here. Also no New updates show up
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
That could be because of the official status, but I've no idea how to get the official ones. I've checked CM website, the get.cm installer and nothing.

In my opinion the transition could have been a bit smoother and handled better. Now there's just a lot of confusion and the latest build causing problems with the phones. Not that other builds haven't and it's been pretty steady for weeks, but at least the latter builds could have been taken down in order to avoid problems and confusion.
[Galaxy S 4 i9506 Android Development] solk2:
I'll upload tomorrow new builds that I have on my phone and known to work. And check snapshots. And I really don't know when official builds will start showing. I'll ask their administration about that.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Also there's something weird going on. My battery level has been at 48% since the installation. For 6 hours now.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Now it dropped down to 47%. 8 hours. Screen time's only 25 minutes but still. Wifi's been on the whole time, as has the mobile network signal. GSam says 1% used in 3h 26m.
[Galaxy S 4 i9506 Android Development] solk2:
So what's wrong? I have same.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Just surprising that's all. I've never heard a smartphone use 1% in 8 hours. Or even 2% in 8 hours. That would mean a battery life of over 2 weeks :D
[Galaxy S 4 i9506 Android Development] leo_bsb:
No, I have Sep/18th nightly installed and can't install the M10 snapshot without phone force close with errors.

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

I just searched for our i9506 at CM official devices list and there is no release for it.
[Galaxy S 4 i9506 Android Development] awicks:
sol2k previously explained that the M10 release is based on code taken prior to the 0918 nightly. As such, you are trying to install an older version by flashing the M10 release.
[Galaxy S 4 i9506 Android Development] davidl1983:
Get.cm

I have been following this thread for quite a while now. I really appreciate the effort put into it, but never dared to make the jump. Worried about the void of warranty (utterly destroyed my HD2 and S2 by installing countless different roms). I got more interested when I saw that it became official yesterday. Will I be able to use the automated Get.cm when it finally hits the upstream, or do I have to manually flash Clockwork and the rom to get it onto my device?

Sorry for such a basic questions, but been out of the xda-game for a long while...
[Galaxy S 4 i9506 Android Development] DualJoe:
Time daemon working properly. Good work, Solk2.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
20140922 popped up in nightlies. Attempted to upgrade to it, but it just didn't boot anymore. Gave the SGS logo, but when the CM logo is supposed to show up, nothing happened. Had to do a factory reset via recovery and install a July version (the latest I got on SD card) to make it work again.

But I was already all wiped out so doesn't matter how many times I have to do this right now :)

Got a two week old Titanium Backup waiting to be restored when it seems good to resume daily usage of one version.
[Galaxy S 4 i9506 Android Development] davidl1983:
CM11 10M snapshot

Seems like people having problem with the last build, is it ok to flash the rom from the download link or should I wait for an update?
[Galaxy S 4 i9506 Android Development] solk2:
Didn't checked snapshot yet. Will rebuild it tomorrow.
[Galaxy S 4 i9506 Android Development] solk2:
There was some problems. Now there is working version. At least its working well on my phone.
[Galaxy S 4 i9506 Android Development] leo_bsb:
I just bricked my phone with the 22092014 nightly.

I can't enter recovery or boot, all I have is a black screen.

I can enter download mode but I already tried two different .md5 recovery files and they didn't solve the issue.
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Not a brick if you can enter download mode :)

I had the black screen too and thought for a moment that I bricked it. Just hold volume up, home button and power button down until it boots to recovery.

---------- Post added at 08:21 PM ---------- Previous post was at 08:03 PM ----------

I deleted the old downloads and re-downloaded the 20140922 unofficial, but it just keeps giving the black screen after booting from the recovery update.
[Galaxy S 4 i9506 Android Development] DualJoe:
No problems here with 20140918 or 20140922.

[MENTION=5024661]TonskuDaigle[/MENTION]:

Format /system before installing the rom (in recovery). The /system/addon.d folder keeps files alive on purpose. Then do a 'factory reset' (wipe /data without /sdcard).
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
This may be a moronic question, but how do you format system? I found "format /system" in Mounts and Storage menu.

Also was there a download location for the roms or do we have to use the Cyanogenmod Updates menu in Settings while a rom is installed?
[Galaxy S 4 i9506 Android Development] DualJoe:
Yes, "format /system" should be fine.

http://getcm.solk.org.ua/_builds/ks01lte
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Alright so this is what I'm doing now.

1) Downloaded the cm-11-20140922-UNOFFICIAL-ks01lte.zip to my SD card.

2) Downloaded GApps mini and stock to my SD card. Just because I can't decide which one to install yet.

3) Entered recovery and did a format /system via Mounts and Storage menu.

4) Went back to main menu and did a Wipe data/factory reset.

5) Install the rom zip from my SD card.

6) Install GApps mini from SD card.

7) "Reboot system now" from main menu.

*drumroll*

1) I get the Samsung Galaxy S4 boot screen.

2) A slight "electro beam" like flash on the screen when the Cyanogenmod logo should appear and the screen goes black. Nothing happens.

3) I press power button, nothing. I hold it until something happens, the phone boots, but number 2 happens again.

4) I hold volume up+menu+power buttons down for a few seconds, phone reboots to recovery.
[Galaxy S 4 i9506 Android Development] DualJoe:
Format, install again but omit GApps for now. Maybe that's the culprit.

What was the last stock rom you had installed before going to CM? 4.3 or 4.4?
[Galaxy S 4 i9506 Android Development] TonskuDaigle:
Formatted, wiped data, installed 20140922, reboot. Same black screen appears.

I reckon it was 4.3. It's been quite a while so I can't really be 100% sure. I remember when I got it in March, I did a stock upgrade from 4.2 to 4.3. Not sure I ever did 4.4. Always been playing with the custom ro...

Hold on. I think they may have upgraded it for me at the warranty service. They changed the chipset.