yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] billington.mark:
Ive had issues ever since the kernel got updates post M9. Have to reset my phone each time i get in my car for bluetooth to connect. M9 is fine. Very annoying!

I dip my toe in every so often to see if its been fixed but nothing so far.
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
Any bugs on 27.08 Nightly?

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Not sure if was just me but ir blaster didn't seem to work with it, so I'm back on 26 th at present
[Galaxy S 4 i9505 Original Android Development] nommy:
They changed something how to control the IR-LED. It's in this commit: http://review.cyanogenmod.org/#/c/71263/

If you are using Smart Remote, just email the developer (colortigerapps@gmail.com) and tell them, you are now using the latest nightly. They will change something on their server and it will work again.
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
I try now newest nightly + Newest GoogyMax Kernel. Runs good for 30min :thumbup::D

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] :
With CM11 Galaxy S4 lost an important feature, too:

Moving apps to sd

Could you implement it to CM11?
[Galaxy S 4 i9505 Original Android Development] Kmailknopf:
+1 this is sooo important

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] jumpers:
app2SD is not realy a need (but sometimes well), the thing that use the most place, is the obb files. i have 2.62gb obb files, without my big games. :( (i use foldermount to move it to my µSD)
[Galaxy S 4 i9505 Original Android Development] !crazy:
I have issue with latest few nightlies and procesor C3 states. It looks like the cpu doesn't take advantage of this state, what increases battery consumption a bit.

Could any if you (again) check if you get 0 like this?

cat /sys/devices/system/cpu/cpu0/cpuidle/state3/usage

---------- Post added at 02:29 PM ---------- Previous post was at 02:06 PM ----------

Just noticed that I'm not able to make a call over Bluetooth by using commands in my car. If I use the phone, then connection works and I'm able to use car speakers. Also contract list takes much longer to transfer, and it fails sometimes...
[Galaxy S 4 i9505 Original Android Development] drewsky208:
This is the most useless waste of space that a message can have. Stop doing this!

1) This thread is for Cyanogenmod! If you change the kernel, it is no longer Cyanogenmod. Go post your happy faces to that kernel's thread.

2) Since the current bugs in the nighlys are *in* the kernel, you are doing the community no good bcause you aren't testing the code in question.

Again: if you install blah blah kernel then DON'T POST HERE.
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Oh great so stay on 26 th nightly now till/if app gets updated, I have emailed support for my remote controller app 'zappir' see what they say about it.
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
As far I can see you're wasting much more space than he is. Don't like it? PM him! Nevertheless his information IS useful for many around here (not me anyway because I'm using CM stock).
[Galaxy S 4 i9505 Original Android Development] riksterinto:
If you just did a fresh install, this happens sometimes. Change the connection to 2.4, connect and the disconnect and change connection to 5 only and connect. A couple reboots usually helps too.
[Galaxy S 4 i9505 Original Android Development] Aqua1ung:
Back on the CM bandwagon

Howdy guys. Been a long-time user of DanVDH's GE-based ROM (for my ATT i337), however that one's got some issues that don't seem to get fixed anytime soon. Thinkin' of getting back on the CM bandwagon, so I need to ask some questions:

(a) is this ROM reasonably stable for daily use (as of end of August 2014)?

(b) does it have any major known-and-acknowledged issues?

(c) has anyone managed to flash it using TWRP's recovery?

Many thanks!

AT&T i337
[Galaxy S 4 i9505 Original Android Development] vedko:
Before somebody shoots you down here, nice and calm advice: read the last 10-15, maybe 20 pages.
[Galaxy S 4 i9505 Original Android Development] Aqua1ung:
Thank you. As you can imagine, had I had time to read a good chunk of the posts here I would not have asked the question :) . I happen to know that many XDA users are quite touchy, so just so we do not clutter this thread any further and avoid irritating the good XDA folks, whoever feels like answering my questions,should do that via PM.

Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] lauterm:
I don't have any problems with TWRP 2.7.1.0.
[Galaxy S 4 i9505 Original Android Development] Aqua1ung:
One more question: is this ROM already lokied? Or should I flash loki-doki afterwards? (Please assume that I will not be using CWM recovery.)
[Galaxy S 4 i9505 Original Android Development] lauterm:
I think it auto-lokis based on the device it is installing on. I always keep a copy of the loki-doki flash handy, but I've never had to use it installing jflte CM builds on my i337 using TWRP.
[Galaxy S 4 i9505 Original Android Development] themetatron:
This has been happening forever to me. Different kernels don't have the issue, only stock cm kernel. Never stopped happening, I just gave up on the extra step of flashing a specific kernel every couple days. Always 0.
[Galaxy S 4 i9505 Original Android Development] Cusa:
There's a commit in the next nightly that improves battery life. Awesome! :thumbup:

review.cyanogenmod.org/#/c/70170/
[Galaxy S 4 i9505 Original Android Development] pod0087:
Haha tried this but thanks. The network is seen by the phone, it just can't connect :(
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
or just use the "search" button for this thread. those questions asked many times recently already.

anyhow for me

a) i use as my daily driver, but some nightly IR not work

b) goto a)

c) use search button, some use twrp no problem, but then if u have problems use Philz Touch, never had any problems with Philz
[Galaxy S 4 i9505 Original Android Development] Bananmos:
I'm still having the problem that my phone is losing connection to the mobile network after I turn the screen off. When it's on it won't reconnect. I'm using M9 now and it works fine

Is anyone else having this problem?
[Galaxy S 4 i9505 Original Android Development] Dathaeus:
WiFi Bandwidth Severly Limited on Comast/Xfinity Modem

• My wifi gets only 22ms ping/3.5mbps down/12mbps up on my Xfinity modem I got a few months ago

• I get well over this at other homes with wifi

• I used to get over 20mbps down with my old Comcast modem

• I got only 2-3mbps even on the nightly version from a few months ago, so the new update hasnt affected this

• Comcast was just here again and replaced every line possible to the high speed coaxials, and said modem was fine and all tests checked out with flying colors

• I get 10ms ping/55down/12up on my direct ethernet connected PC

• I get 12ms ping/50down/10up on my laptop (wifi)

So basically it seems ONLY when my phone is using my Comcast Xfinity modem wifi it causes these problems with low downstream bandwidth.

Any ideas?
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
You asked exactly this already here:

http://xdaforums.com/showthread.php?p=55097388#post55097388

And if no one answers, no one got an idea...
[Galaxy S 4 i9505 Original Android Development] sronweb:
Then it might be a problem in the new Xfinity modem, not in the CM rom?

Have you tested Sammy stock rom?

PS: just tested with my Fritz router and I got around 50-58 Mbps in upload and 33-40 Mbps in download to the phone.
[Galaxy S 4 i9505 Original Android Development] Dathaeus:
I figured if it were the modem then it would not let me laptop go 50mbps, unless somehow a modem's wifi can limit the bandwidth for a cell but not a laptop?

I havent tried Sammy stock, I wanted to eliminate any other obvious or simpler solutions before I go experimenting with other ROMs. But I guess with your testing with another S4 and same ROM here, it cant be the ROM or the phone.
[Galaxy S 4 i9505 Original Android Development] jcasares:
(a) I use it for heavy work and some gaming but with some builds I wish I wasn't using it. You have to be careful. If you want stability go for a stable build (not always an M release).

(b) In my case I have some flickering but that's it. I workaround it with a development option that's supposed not so good to have but it's better than having flickering. Some people are not affected by this so you might be lucky. The rest in the current build I'm using is working properly. Newer ones have problems with Bluetooth, WiFi and Radio among the most prominent.

(c) just use CWM or Philz already. :P

I'm now on 20140802 that is quite stable for my standards. Some people use a couple of days later ones but I believe after the 20140808 where the kernel was changed the stability was lost. You will have to wait for them to make it stable again but might take a while. So, use a release previous to that date.
[Galaxy S 4 i9505 Original Android Development] Jacopo97:
I'm the only one who get about 10 freezes during the day with this rom? I also have mic problems only with Whats App with every build I tried.

Please be patient reading my "english" :o:o
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
i don't have any freezes.

also i have no flickering.
[Galaxy S 4 i9505 Original Android Development] sqapg5:
Whatsapp issues

I have recently rooted and installed this ROM. Whatsapp do not work on mobile network but however when i am connected on WIFI.. Whatsapp can work. Anyone face such issues?
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Just tested on mobile network for whatsapp works fine on today's nightly 8/30
[Galaxy S 4 i9505 Original Android Development] sqapg5:
I realized that i had to switch to a different APN.. and now its all working fine... hope it helps those whom are suffering from apps not connecting etc...
[Galaxy S 4 i9505 Original Android Development] !crazy:
Latest nightly 0806 works great. Not only in that regard, but it feels very smooth and stable in general.

In regard to C3 states, just take care that no app has 'apply settings after boot' to which mess with C States (like faux clock or whatever.). mpdecision has to be on for default kernel for C States to work properly!
[Galaxy S 4 i9505 Original Android Development] HetsHumbucker:
Same here but only when I'm on 3g. With 2g only everything works fine...
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
ya i have also mentioned before in previous posts many many times, the APN values of default CM rom are not always correct/latest, for each region. people should check APN first, if they r not connecting properly or getting correct speeds.
[Galaxy S 4 i9505 Original Android Development] Cusa:
I'm getting disconnected from the WiFi every few hours. Anybody else getting this?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
nope. all wifi ok here.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
:confused:
[Galaxy S 4 i9505 Original Android Development] !crazy:
Sorry, my bad. I meant the yesterday's build (30th of August).

But the one from 6th of Aug is actually even more rock solid, stable, and I have recommended it over latest milestone build.
[Galaxy S 4 i9505 Original Android Development] Stransky:
Hi

On 08/30 CM stock kernal w/dalvik and having sleep problem. When phone goes into deep sleep I cannot waken it without holding the power button to shut down and rebooting. Has anyone had this and if so, know how to cure the problem.

Oldbarzo
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I have the same configuration you wrote: no problems on wake (also with proximity wake function, so just opening the flip cover). I don't know how to "cure" your issue, sorry.

EDIT: did you use a transparent protection cover for the display?
[Galaxy S 4 i9505 Original Android Development] Stransky:
Hi

Thanks for the reply.

No transparent protection for display and also have proximity wake function.

Have been having this problem for the last few nightlies. Switched to Slimkat ROM last couple of days and it did not have the problem, so appears to be CM related.

Stransky
[Galaxy S 4 i9505 Original Android Development] ste22032:
Hi guys, what is CM home.apk on /system/priv-app? Is it safe to remove? Thanks :)
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
i don't have that problem at all.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Nightly 31/8 Pulsing LED on boot :eek:

After boot it just continues ... forever :cyclops:

Plugged in charger and enabled "LED on charge" finally stopped this unnecessary LED pulse ...
[Galaxy S 4 i9505 Original Android Development] HetsHumbucker:
Searching in settings shows an option 'prevent accidental wake up' in display section, but when I tap it there is nothing like that. I know it was here before a month ago... 29/8 nightly
[Galaxy S 4 i9505 Original Android Development] rodrigoger:
Led is crazy in last nightly (2014-08-31) with custom kernel. Using alucard it works fine.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
On active calls the lockscreen icon is suddenly visible since the last 2 or 3 nightlies. It lies above the call screen and gives you the option to accept the call or reject it, although the call is already running. When trying to select the red "end call / reject call" icon, it sends an error message. Call can then only be ended through the pulldown menu.

This is how it looks like

The mentioned error says < The process "com.android.incallui" has been terminated. >

Running nightly 30.08. currently. Everything stock.
[Galaxy S 4 i9505 Original Android Development] LuigiC6:
Wipe your cache.
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
Tried that a few times already, also tried reflashing.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
It is not related to cache... it appear also if the screen goes off (for proximity detection)... this problem has appeared with proximity wake functioning... before it was working as it should.
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
Well the Screenshot I posted was created from the phone lying in front of me, calling a random number. The call screen opens like that, display doesn't go off or black from being toggled by the proximity sensor. But I agree, it probably has something to do with recent changes on the sensor behavior.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
All can be... but to replicate 100% the problem, is enought that you receive a call, than answer and put the phone near the hear... when you move away, the screen goes on and it is blocked as you reported... I enabled the power button to answer/close the call, so I bypassed the problem, waiting for the fix obviously...

EDIT: but you are right... just after a call opening the screen result blocked as your screen...
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
Of course I'm right! ;) but thanks for confirming the bug

[Edit:]

Seems to be fixed on nightly 31.08. already. Yey ;)
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Uhm... I have nightly of today 31.08, but it is still present!! Infact there are no commits on cyano review about this issue...
[Galaxy S 4 i9505 Original Android Development] MetalPainis:
Hm. I can just say, I flashed 31.08. (from cyandelta) 10 minutes ago, the first thing I tried afterwards was if the issue still exsists. And it doesn't. Yet... ;)
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree LED is a bit annoying 831 nightly...ur trick set "LED on charge" plug in charger stopped it. good tip.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I made a complete clean install with 31.08 nightly... and the issue is still there... do not know why for you is gone... let's see...
[Galaxy S 4 i9505 Original Android Development] overkillZ:
I havent been active on the s4 xda in a while so sorry if the question has already been answared.. but.. Is there any fix for the camera problem? The camera wont start uintil a reboot.
[Galaxy S 4 i9505 Original Android Development] rodrigoger:
Led is OK at 2014-09-01 nightly version.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Yeah, if you have read the changelog the boot pulsing led commit got reverted. Seems like they readd it again if they got it working properly.

L
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Unfortunately, BlueTooth still works very unreliable in this build. Sometimes pairing works, sometimes not. Sometimes the hardware key on my "headset" (car) works, sometimes not.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Updated the brand new clean install to latest 01.09 nightly and call screen blocking is still present... receiving a call you can answer (or deny) with the slider, speak with caller person, than if you check the screen you still found the slider that block any action... only way is set power button to close the call... really annoying...
[Galaxy S 4 i9505 Original Android Development] !crazy:
Don't know what are you talking about. Camera works and starts fine.

Have you tried cleaning data and cache of the camera and gallery app under system settings, device, apps, all, and if that doesn't work remove the two apps, flash the latest nightly, and recent gaps package (without Google camera, but in nit sure any more about this. Before I had problems with it, but nowadays everything seems to work fine. I even have Google camera app, but from the play store, and it works well.).
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Don't seem to have that problem here I'm on latest nightly 09/01 I get a call like always slide to unlock talk and hang up like normal
[Galaxy S 4 i9505 Original Android Development] betelgeuse74:
Bluetooth has been very unreliable since the start of CM11. I also have issues with connectivity.

I hope developers will start to focus on BT stack. For me it's a important feature.
[Galaxy S 4 i9505 Original Android Development] !crazy:
It wasn't unreliable for me it is only that some features were / actually still are missing. Like contact list sync in a car.

The real instability issues started with the last nightlies, at the beginning of this month. IIRC it was still working well in the nightly build made on 6th of Aug.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
[SOLVED]... it is and xposed setting!!

I found it: it is xposed setting of "Integration with resources link" or how it is called in english... it is the last setting of setting menu... by disabling it the incallui has become normal... hope it helps other users until xposed framework will receive the update/fix...
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Disabled resource hooks is what is last in settings in xposed, mines Unchecked if this is what you mean?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Yes... enable it to disable integration with resources... than go to Framework and press Install/Update... reboot... this what I've done and solved.

EDIT: it partially solved... if the screen goes off, it appear again after screen on... s**t...
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
But mine works fine without it enabled
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Nothing to do... after screen off it appear again... so NOT SOLVED!!

EDIT: I have another info... if I close the flip cover, it appens again... if I just put the phone near the hear, it works... I try 3 times and seems related to flip cover (proximity wake) function... can someone test this and confirm? Thanks...

EDIT 2: info for [MENTION=2385005]invisiblek[/MENTION] Re-tested and seems 100% related to flip cover closing... to test I switched on the phone with opened cover. Than I made a call (and the screen is ok)... put the hand over the proximity and screen goes correctly off, remove the hand and screen still ok... I put the hand 10 times and the screen after ON still perfectly working... as soon I closed the flip cover and opened, on the screen appear the slider and complete interaction with the call page is forbidden... after the slider appear once, the screen continuously is "broken"... need a reboot to fix... I hope this situation can be replicated by everyone, because it will guide the devs to search the problem and put the right fix...
[Galaxy S 4 i9505 Original Android Development] lauterm:
Make sure HDR is off. The option is there, but I don't think it works yet.
[Galaxy S 4 i9505 Original Android Development] munkyvirus:
Is IR working in the latest nightly? I would test, but I'm using F2FS
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
not for me. 901 nightly. (default kernel. w ART.)
[Galaxy S 4 i9505 Original Android Development] munkyvirus:
Thanks, mate, I'll keep tabs on the changelogs then
[Galaxy S 4 i9505 Original Android Development] HetsHumbucker:
For me it's working perfectly with smart remote. The devs need to change your configuration back to standard if you had them changed to work with custom roms
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Ir working for me using zappir on alternative setting in settings on latest 09/01
[Galaxy S 4 i9505 Original Android Development] 78Staff:
9/01 nightly, stock kernel, ART, JTLFE -

LED issue corrected, but as already mentioned BT unreliable - I actually can't get it to stay on for more than a few seconds. Don't use IR, can't comment on that one. M9 still going strong...
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Maybe, tomorrow it is better with bluetooth:

http://review.cyanogenmod.org/#/c/71357/
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I think tomorrow build will fix a lot of stuff... probably also incall blocking stuff with wrong slider... finger crossed... let's see...

EDIT: probably this is the fix to the issue on incallScreen... http://review.cyanogenmod.org/#/c/71039/
[Galaxy S 4 i9505 Original Android Development] drumex:
Hi! Which kernel recommended on Snapshot M9? Alucard 2.0.7d?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Wrong thread... ask in Alucard thread... anyway v2.7.1 AOSP
[Galaxy S 4 i9505 Original Android Development] drumex:
Ok... Sorry... If someone is interested Alucard kernel is ok for snapshot..
[Galaxy S 4 i9505 Original Android Development] smeroni68:
We know... it is based on old kernel sources so it is stable as the other custom kernels available... close OT

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] BobbyHill:
Sometime a few weeks back I started experiencing a problem with the carrier becoming unavailable if I switch between towers. If I'm at home or my regular office that's like a mile away, I have no trouble. But if I go to the other office in the next little town over, boom! It says no mobile network. If I reboot the phone it comes back on and is on the network again.

I know the M9 release works ok, but sometime within a couple weeks after that it's kaput. Just tried the latest nightly and I get the same behavior. Anyone else having this problem?

I'm using the sgh-919 on T-Mobile USA network.
[Galaxy S 4 i9505 Original Android Development] a103:
Are you on latest baseband NB4? Haven't had such issue.
[Galaxy S 4 i9505 Original Android Development] BobbyHill:
Baseband version

M919UVUAMDL

I take it this is an older one? The only thing I've really done since I got this phone when it was first released was root it and start installing CM roms when they became available.

Have you got a link handy for updating whatever else needs updating?