yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] AMDPOWERFIST:
it's the newest, I would assume it's the better of the ones out for any 4.4.1+ ROM
[Galaxy S 4 i9505 Original Android Development] 00raq00:
Flash another (compatible with ART) gapps
[Galaxy S 4 i9505 Original Android Development] jmjviana:
The camera is working fine in this ROM. The only downside is not having an option to save photos to the external sd card.

ART is not working well. If that happens you can shutdown the phone and try to boot again. After like 15 seconds the phone will pass the Samsung logo and boot. But after that many apps will have FC while on ART. At least that's what happened with me.

Enviado do meu i9505 usando o Tapatalk
[Galaxy S 4 i9505 Original Android Development] kewinh0727:
[MENTION=2385005]invisiblek[/MENTION]

what is changed in your latest gapps 20131208 :) art compatible? please explain :) or is it recomended to use PA gapps 0 day kk 4.4

since it is art compatible :)
[Galaxy S 4 i9505 Original Android Development] respider:
yes I don't use CM on s4 because of camera as well. stock image quality is much better unfortunately
[Galaxy S 4 i9505 Original Android Development] maharu567:
This rom has multi window feature?
[Galaxy S 4 i9505 Original Android Development] Klyupp:
No. It doesn't.
[Galaxy S 4 i9505 Original Android Development] c2s.vdg:
HDR is not working for me also... Everything else working OK so far... Sweet!
[Galaxy S 4 i9505 Original Android Development] Neuron:
Aand, please an ubiased opinion, am i better of with this one or unofficial noobdev?
[Galaxy S 4 i9505 Original Android Development] Mittaa:
What about "Snap Camera" ?
[Galaxy S 4 i9505 Original Android Development] dajumper:
I hope cm is also updating to 4.4.2 lol
[Galaxy S 4 i9505 Original Android Development] 1902:
You can try both :good: :D i prefer official CM because of the stable updates and the huge team of Devs behind it.
[Galaxy S 4 i9505 Original Android Development] jd1001:
Great

Running CM11 the last day or so with the KT kernel. I don't have any bugs to report at all. Thanks for the hard work :laugh:
[Galaxy S 4 i9505 Original Android Development] maysider:
is photosphere included?

thx
[Galaxy S 4 i9505 Original Android Development] jd1001:
Works fine for me ;)
[Galaxy S 4 i9505 Original Android Development] fjuniper:
Thanks, I will see what I can find, otherwise, I think I am going to give this a try when I have some time: http://xdaforums.com/showthread.php?t=2557353
[Galaxy S 4 i9505 Original Android Development] Nathanabrahams:
I'm installing for first time coming from stock and I get status 7 error when flashing .... Any help ?
[Galaxy S 4 i9505 Original Android Development] islipfd19:
Working good so far on jfltexxx
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
How about flashing latest cwm recovery instead the one from philz?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
im always having problems with philz, since it came out for our S4, always coming back to cwm

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
+1

I still don't get why people prefer philz over official cwm...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Sounds good. Couldn't find it at http://www.cmxlog.com/jflte/ ... so I take it from Jenkins :good:
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
the options man, so many options,yet the basic function(flashing) doesnt always work...
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Who cares about those options (who gives a &#@ about a custom background in recovery) when basic functions are buggy...

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] zeus85:
Basic functions are flawless in philz recovery its not about background or theme settings it extra options that give it the edge over original cwm original has failed me several times and philz recovery has worked flawlessly he is a good dev its a matter of preference so show respect
[Galaxy S 4 i9505 Original Android Development] !crazy:
The point is almost every user complaining is on philz recovery. It really doesn't matter if he is a good dev or not. No one is degrading him.

I'm using TWRP since I got the phone, and never had an issue. It doesn't mean someone else didn't have it.

Software changes, old bugs go away, new ones appear... In this case, with our phone, it is so that people who use original CWM or TWRP usually have no problems.
[Galaxy S 4 i9505 Original Android Development] zeus85:
Fair enough just giving every dev a fighting chance as iv never had a problem with philz recovery
[Galaxy S 4 i9505 Original Android Development] Mittaa:
[MENTION=2385005]invisiblek[/MENTION]

Will we get jflte changelogs from http://www.cmxlog.com/ in future?
[Galaxy S 4 i9505 Original Android Development] !crazy:
This is bad... CM kernel is not able to use C3 low power state 'POWER_COLLAPSE', and that's the best one for saving battery.

This is too bad since everything else what I care about works great.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
You aren't hearing from all the users who *don't* have issues with PhilZ.

I, for one, have never had any problems with PhilZ.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] mickyw1980:
Ive never had any issue with philz recovery either ☺
[Galaxy S 4 i9505 Original Android Development] !crazy:
Ok, so just continue to use it then? You are not the first one who reported that it works for you. Actually every time someone has a problem with recovery, and it is philz, someone reports it works for him.

No one is against your favorite recovery. People only recommend other ones, and that in specific context. What's wrong with that?
[Galaxy S 4 i9505 Original Android Development] sh4z:
Alarm wigging out still in latest nightly (flashes uncontrollably)

20140217,

On the Topic of recovery, using PhilZ and not experiencing any major issues. Backup restore, flash and reboot are all working. What more do you need? :3 as long as it works for you.

Sorry for off-topic :rolleyes:

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] mbc663:
So lets turn this thread into a recovery debate. WHO CARES
[Galaxy S 4 i9505 Original Android Development] vedko:
Well, I don't think they're morons. Building mobile security policy for large companies (read 100000+ employees) is though and there will always be somebody who is not happy; while in the discussion about root on Android such people are very vocal because they mostly know what they're talking about and they're geeks.

When the root got prohibited in the company I work for at the beginning of this year, there was a fierce internal discussion (which I actually started). And in the end I had to admit that if I was the CIO I'd do the same - with the rooted population week below 1% (although still good couple of thousands of people), it's simply not worth the risk (of losing my well paid job).

In my opinion, although the diversity of Android beings a lot of benefits, it's not that appreciated when it comes to managing the corporate security policy.

Luckily, I'm not forced to use company SW on my (company owned) phone, so could decide not to use it and keep the root, at least four now
[Galaxy S 4 i9505 Original Android Development] Moz007:
I tried Play Store Fixes Xposed but it didn't work, i tried to modified Build.prop too...

Still incompatible...

This is wierd because i can download GTA III and Vice City and i have this game legally so why i can't download San Andreas ?!
[Galaxy S 4 i9505 Original Android Development] feraay:
Becouse its not supported with aosp Roms .... Go on stock Rom buy it backup it flash cm replay the backup and all good^^

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
Only thing which makes sense in your post IMHO is that is not worth or risk.

Everything else is just blah, blah. We should discuss the concrete implementation of security and software, and then see if the solution is really 'secure' and if it really brings something except money in pocket of managers, and ego satisfaction to some dumb admins.

In my experience the bigger the company the more of crazy things happen there. Owners have almost nothing to do with the work done, have no influence on how the things are then, and if they decide something then without expertise needed.

For example they forbid administration access on laptops, while they do not restrict how that person connects on the network at home, in hotels etc.

Totally retarded and useless. While 5 year old kid can get administration rights on Windows (or whatever.) they let people connect to open, non encrypted WiFi networks.

Of course I don't have to have right, I'm speaking just from my experience, and of others I know.

What it makes sense is not to let workers to play with phones, because they can brick them. But that's a bit different story. Flashing CM on some well supported devices is pretty safe nowadays.
[Galaxy S 4 i9505 Original Android Development] vedko:
Well, I agree with you (almost;) completely. My point is there are always at least 2 sides of every story. And if I were the CIO (even very knowledgeable one), I'd have to explain my decisions to the CEO's etc. - and here when you mention antything like "root", "admin access" etc. combined with "access to company data", the red light starts flashing all around in the their mind. And then facts and reasoning don't help. I'm not saying it's right or I like it, but merely that this is the reality we're living in.

I also very well know that the security features in CM are superior to most of the stock rom's - well, would I install CM on all 100000 company phones then? No, as it's simply not possible, feasible, cost effective etc.

And btw.: flashing CM is never safe - the disclaimer of every CM thread is there for a reason.

EDiIT: I just realised that I'm getting off-topic and with this, I'm finishing this discussion, at least on my end.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Ever heard someone hard bricked phone by flashing, already tried reliable build? If something happens then there was anyway something not right with the phone. There are other things which can happen, but it happens so rarely... Well, yeah, at least South Korea decided to forbid the stupid behavior of Samsung to install, non removable **** on their phones. So at least, hopefully, we will be able to remove all that bloat without root. I can handle TW, but not thousands of useless libs and software floating around in memory.
[Galaxy S 4 i9505 Original Android Development] byobodybag:
Same here, camera crashing upon opening. Using the 0218 nightly.
[Galaxy S 4 i9505 Original Android Development] fjuniper:
I am guessing we work for the same company! No root after 31st January, following an acquisition? I am not trying to get around xxxx300, just have a ROM I like, without root.
[Galaxy S 4 i9505 Original Android Development] jmjviana:
Does someone know where I can find smiles to the default SMS app? I don't want to use other apps.

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] vedko:
Oh, yes, that's it. I'm currently waiting to be cut off. As for the ROM, CM is probably not they way here. If I had to go this way, I'd probably go for Google Edition ROM. I didn't like the 4.4, too much Google around, plus it still had some issues last time I checked. But the 4.3 was/is rock solid and fast.
[Galaxy S 4 i9505 Original Android Development] Moz007:
There is no hack or somethings else ? :confused:
[Galaxy S 4 i9505 Original Android Development] feraay:
The hack is to buy it in stock and backup it ^^

Dont know something else but this works

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Moz007:
Oo... it's not possible to change a value in build.prop or something else to simulate a touchwiz rom ? :(
[Galaxy S 4 i9505 Original Android Development] Marcet:
On bluetooth contact sync issue...

I'm able to sync carddav contacts, but not activesync ones. Bug or normal?
[Galaxy S 4 i9505 Original Android Development] Mittaa:
CyanDelta & Jenkins changelog isn't in sync with old jfltexx changelog and I can't find any changelog for new unified on http://www.cmxlog.com/11/jflte/ :confused:

Did I miss something? :o
[Galaxy S 4 i9505 Original Android Development] jmjviana:
http://changelog.bbqdroid.org/#/jflte/next

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Thanks :good:

But still a bit strange that number of changes between 18. and 19. nightly varies:

CyanDelta shows 3 changes

bbqdroid.org shows 2 changes

Jenkins shows 5 changes
[Galaxy S 4 i9505 Original Android Development] BillGoss:
It's no longer a feature of Messaging app. But the AOSP and Google keyboards have emoticons present all the time.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
Can anybody test the built in voip client/function of the dialer app? I tried with the "fritz.box" from avm, don´t know whether it´s a known router in other countrys than germany, but it can not connect. The App from the manufactor is working great, so it has to be a problem of the dialer app.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Could someone please check value of /sys/devices/system/cpu/cpu0/cpuidle/state3/usage?

With CM kernel the C3 power collapse state is not utilized, and I was not able to enable it. Want to know if this is an issue with my installation, or is really the problem with CM kernel.

Most other kernels have working C3 state on my phone, with the difference I have to enable it on some, some have it turned on per default, but I'm not so sure any more about default value.
[Galaxy S 4 i9505 Original Android Development] Milamber:
For some reason CyanDelta hasnt pulled down an update in two days?
[Galaxy S 4 i9505 Original Android Development] geomax45:
CM went to a unified build, and I think you need to download the latest version and flash manually. After that, the update service should work. I'm on jflte, and went that route successfully.
[Galaxy S 4 i9505 Original Android Development] AMDPOWERFIST:
So these are the 2 new links for JFLTEXX - which are now JFLTE - is that right?

http://download.cyanogenmod.org/?device=jflte&type=nightly

http://www.cmxlog.com/11/jflte/
[Galaxy S 4 i9505 Original Android Development] Milamber:
Yep
[Galaxy S 4 i9505 Original Android Development] nommy:
Mine is 29406, whatever that means :confused:
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Mine is 828538 so not sure if that's going to help anything? ?
[Galaxy S 4 i9505 Original Android Development] !crazy:
It help me : ). Now I know that I have some issues with my installation. Whenever I flash CM, and leave stock kernel C3 state is not active, what means the processor is not using it's deepest power saving state. For other people is working, and that's great.

[MENTION=3301208]nommy[/MENTION], I am not sure what number represents, probably the number of miliseconds spent in the C3 state. The bigger the number the better : ). It increases with the time.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
CyanDelta & CMUpdate are still blind when it comes to new unified nightly? :eek:

Edit

LOL CMUpdate got it, and CyanDelta should get it shortly after :)
[Galaxy S 4 i9505 Original Android Development] !crazy:
[MENTION=3301208]nommy[/MENTION]

@ gadgetuk99

Which governors are you on? It seems that my issue is only present with interactive, which is default. After I switch to ondemand, C3 starts being utilized.
[Galaxy S 4 i9505 Original Android Development] nommy:
I am on interactive.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Same interactive

And using power save profile
[Galaxy S 4 i9505 Original Android Development] !crazy:
Thanks for the answer. My phone seriously doesn't like some settings, and something is messed up, and I'm unable to figure out where and what. At least some configurations, which I would anyway use, work well.

Regarding performance profiles, I am not sure if they do much besides switching governors and mpdecision on and off.

Power save profile should set governor to conservative.
[Galaxy S 4 i9505 Original Android Development] Moz007:
I don't know if it's voluntary, but I'm unable to access the task bar from a game in full screen now. :S
[Galaxy S 4 i9505 Original Android Development] themetatron:
I have 0. Interactive. And ondemand give 0. No matter the setup it sticks at 0.
[Galaxy S 4 i9505 Original Android Development] !crazy:
That is not good. It is not the end of the world too, but as I mentioned, it is a sign that your CPU is not using its deepest/best low power state. It is one of the very nice features of this phone, and if it works properly, one can even try running performance without killing battery. I did, and it was ok. The reason I switched is because in some scenarios it drains a bit more battery, and I anyway tweak governors toward performance so I got the same (almost, can't notice the difference.) from other governors.

I had strange results with CM stock kernel. First it worked when I switched to ondemand, then after I tried performance (before it had worked with performance gov too, now it hadn't.) and went back to ondemand, and it stopped working with ondemand too. Have no idea what is going on.

Anyway with other kernels I don't have such problem (but have some others : )). The kernel my phone likes the best, it looks like, is Efficient kernel. Most of new tweaked governors do not worked well, cause freezes etc, except on Efficient and intelliactive from faux. It is not that I have to run new gov, I quite like interactive, pegasusq (there is no kernel for this phone and AOSP with nice enhanced implementation, and it crashes my phone allways), on demand and performance. But intelliactive seems like a nice tweak and it works fine.

C3 state is working here with all governors. So my advice to you, is either try changing governor, or kernel.
[Galaxy S 4 i9505 Original Android Development] themetatron:
I've seen you ask this question a couple times, and now I wish I had replied earlier. I just thought this was normal battery and performance. CM for awhile had such a great kernel, that I stopped using faux when I had my galaxy nexus. Switched to efficientkernel and using their settings with ktweaker. Now shows 1900. Thanks.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Maybe it is not the CM kernel in question, it seems for most people it works well.

Regarding battery, I'm not sure you'll notice significant battery performance improvements, since these are influenced by many factors, like screen, background apps, and if your CPU was able to go off, and use other C states, the difference should not be significant.

But I never tried using my phone for longer time without C3 state enabled, so I cannot actually know :) really.

You could report if you notice any significant difference regarding battery / performance, that would be great.
[Galaxy S 4 i9505 Original Android Development] punchpunch:
:confused:

With the new unified rom, signal is little bad. Which modem should i use in Germany for D2? Thanks
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
Cyanogenmod doesn´t touch the RIL, Modem and so the new release shouldn´t make a difference for your signal. i am also in Germany and everything is wokring flawlessly.

But nevertheless: Because Cyanogenmod doesn´t touc hthe modem i update it by myself, so i always use the newest one. You can find modem threads here on xda for updating, but for the new modems you need the new bootloader which comes with the original 4.3 Touchwiz Rom.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Hi Guys,

i got with cm-11-20140219 and cm-11-20140220 NIGHTLY a problem, the GS4 dont go in deep sleep..

i investigate and the problem is ssp_wake_lock :(

someone else have this issue?

thanks
[Galaxy S 4 i9505 Original Android Development] punchpunch:
XXUEML6 works pretty fine:good:
[Galaxy S 4 i9505 Original Android Development] mxn-:
How to set it so it plays music via USB?
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
No, battery is all good here.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Thanks for the reply..

ok battery is good, but do you got this wakelock? the phone go normally in deep sleep?

Can you please check this?

Thanks
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
No wakelocks for me (without deep sleep and with wakelocks i wouldn´t get a normal battery usage).
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
thanks :good:
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Why is my SElinux 'strict' since a few nightlies? :/

Gesendet von meinem unknown mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] EnormoDerClown:
SELINUX is implemented in the kernel. So Ktoonz, your kernel dev, has implemented it. Or you are trying the stock which has implemented it too.
[Galaxy S 4 i9505 Original Android Development] !crazy:
I am not sure if that's the wake lock I was having problems with, about an year ago, on my i9305. I just googled and found this http://searchcode.com/codesearch/view/26282226

ssp.h header, which is about sensors, and gyroscope is also mentioned inside. What makes me thinks, that's the same wake lock I had problems with.

Maybe the bug has still not been resolved. It is not the bad one because it happens only after hot reboot.

When you notice the issue again, try rebooting and see if that helped. I think it will.
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
Hi,

thanks really kind :good:

sorry but im finish my daily thanks.
[Galaxy S 4 i9505 Original Android Development] boulder96:
If you are talking about outputting sound via a USB DAC, you need an OTG cable.

1. Attach the OTG cable to the USB device, and then connect it to the phone.

2. Start music player app.

3. Profit

Note: Not all USB DACs and music player works. USB audio also depends on the kernel you are using. If the stock CM kernel does not work, you can always try other kernels available.

So far, Apollo, Poweramp and Neutron Music player works with USB DACs

From Headfi: http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/4110

Or if you don't mind spending a couple of dollars:
[Galaxy S 4 i9505 Original Android Development] !crazy:
Wasn't more simple to try different kernel, reflash the ROM, reboot, or something...
[Galaxy S 4 i9505 Original Android Development] tanoxxx:
i make this and some others test:

i flashed a cooked Samsung JB and i maked the ADC Test, the Sensor Working correctly, the phone go in Deep Sleep and i havent the ssp_wake_lock, all seems work perfectly..

i Clean flashed also the omni-4.4.2-20140220-jfltexx-NIGHTLY and i got the same issue, phone cant go in deep sleep and ssp_wake_lock

i restored also a my old nandroid backup of CM11, "2013-12-16.10.35.09_11-20131214-NIGHTLY-jfltexx", and i dont got any problem...

I think there is some problem with the latest versions of CM11 and similar rom, but nobody noticed that?

Please [MENTION=918582]guys[/MENTION], can you check this?

http://xdaforums.com/showpost.php?p=50507029&postcount=1840

thanks
[Galaxy S 4 i9505 Original Android Development] Moz007:
Is it working for you ?
[Galaxy S 4 i9505 Original Android Development] fjuniper:
That reminds me, can anyone recommend a sensor checking app - my daughter thinks my new i9595 has a problem (based on playing DroidJump!)? Thanks.