yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Hi,

CM camera working without problems here. Im on M9 with dalvik. Save pictures to interal and external storage is no problem

Give "Clear Data" and "Clear Cache" of camera apps a try
[Galaxy S 4 i9505 Original Android Development] Annunneo:
I just dirtied M9 over M8 and my camera is working fine as well.
[Galaxy S 4 i9505 Original Android Development] petrus764:
This is a known hardware issue for the S4, dust penetrates the phone and gets all over the proximity sensor, I've had mine in for repair for this twice, and it's still not good.

Samsung keeps tweaking the values in their firmwares for when the screen should turn back on to counter this design flaw. CM and other AOSP roms uses the default AOSP values, and as such is more prone to black screen while in a call. Not really CMs fault since it's samsungs ****ty design that's the culprit.

Not sure if you can easily tweak these values in CM.

For more info, just google galaxy s4 dust proximity sensor.
[Galaxy S 4 i9505 Original Android Development] DeezNotes:
Proximity Sensor Fix

This is correct. The default values don't work with our phones. I went to the stock GPE rom and had the same issue. Below is the fix with easier to understand explanations (the details I found in other posts were confusing).

In terminal/adb:

get root

$ su

change to the folder that has the sensor files

# cd /sys/devices/virtual/sensors/proximity_sensor

the next command will show you the value of your sensor. run it with your finger over the sensor (should be 255) and with your finger not over the sensor (can be around 37 - 45).. each phone is different. my guess is a value over 50 means it's dirty and you should blow compressed air into the earpiece.i ran this command a few times just to see what the values were in different lighting.

# cat state

the next two commands will reset your proximity sensor, then set it to auto detect, respectively

# echo 0 > prox_cal
# echo 1 > prox_cal
[Galaxy S 4 i9505 Original Android Development] toeterbaas:
Bought an s4 after my mi3.

First thing i did was kicking touchwiz off it :)

Cyano is sooooo good .

Its always the best you can have !
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
The sensor is fine as works ok on dalvik , but that's why I was saying about on Art,I did have a problem before but cleared it with using a vacuum cleaner on suck and been working fine since, and still works with my proximity sensor app.so know it's not that
[Galaxy S 4 i9505 Original Android Development] vedko:
I cannot comment on ART, but since M8 the proximity sensor works flawlessly on Dalvik. I had previously problems with black screen in calls but it went away without me doing any dust blowing/vacuuming.
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
I really don't understand why everybody keeps talking about ART on this thread. CyanogenMod don't support and don't advise it, xposed is still waiting for stable ART releases, till then only Dalvik is supported. Why do you insist on this subject?

Any of you tried another kernel (like Alucard)? Did you changed simple things like window and transition animation scale to 0.5x? These two simple things have a much bigger impact on performance than ART and are potentially bug free.

Finally, M9 is amazingly stable. Camera is working just fine (still I prefer Snap).
[Galaxy S 4 i9505 Original Android Development] a103:
Spot On [emoji106]

Sent from my "Personalized Galaxy S4"
[Galaxy S 4 i9505 Original Android Development] !crazy:
The same could also be said for custom kernels.

While pointing the fact that art is not supported by the CM team, you recommend custom kernel?

Let's think about it a bit. Art is going to replace dalvik in CM, this is only a matter of time and 99% sure.

Art has also made a significant progress, and nowadays works much better than before (my personal experience.). Freezes/flickering are mainly related to something else, and they happen with dalvik too. The issue is definitely related to different particular apps, and maybe to graphics, scheduler and who knows, but this doesn't matter now. That being said I don't encourage people to switch to art at the moment.

CM will never switch to alucard kernel, supports only it's own, and CM kernel is quite underrated.

It is better to learn some basic of kernel tweaking, than to switch and flash kernels every now and than, only because the real important difference is they have few different values set for governors/schedulers. I am not saying it is stupid to flash custom kernels and that is always wrong, makes no sense, but very often one can get the same result with the stock, by only changing few values.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
Another thing that CyanogenMod don't support is using any kernel except the one that comes as part of the CM package. There's a very good reason for this: the third party kernels can't be guaranteed to be 100% compatible with a given build, and this makes troubleshooting all that more difficult.

Yet despite this, it's all too common for people in this thread to discuss (and even advocate the use of) third party kernels. The amount of noise in this thread due to ART is far less than what's caused by talk about third party kernels, or by things that aren't related to CM all.

Xposed aren't supporting ART yet because the relevant code hasn't stabilised. The module has to hook deep into the framework code, and there's no use making a public release if the targeted code is likely to see breaking changes. They already have a working prototype, so it's not like the problem is technological.

Also, changing window and animation scale will have an effect on perceived performance (how fast you phone feels like it's running), but should have little or no effect on real issues like battery life. ART does being some real performance benefits, which is why Android L is dropping Dalvik completely.

And even though the CM team don't support it, it's important that some people use ART. If there are apps that don't work well on ART, those problems should be found and reported on before Android L becomes widespread.
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
But the linux version of the CM kernel still is 3.4.0 while others have 3.4.98 or 3.4.101 already...
[Galaxy S 4 i9505 Original Android Development] fazi78:
Have the same if this help you :)

Any idea how to fix?

Cheers
[Galaxy S 4 i9505 Original Android Development] aznkenshin:
I can't press "Allow" when being prompted to allow/deny an app from superuser access. I'm on 8/4. Anyone else?

To replicate:

1. Download an app that requires SU, like Wakelock Detector

2. Get prompted Allow/Deny for SU.

3. Try pressing Allow.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Someone knows why in last builds' Camera app there's 12.8 MPX maximum resolution instead of 13 MPX as before? I haven't look changes in sources yet
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I have a strange issue listening to music using the monthly 9.

Whenever I try to go to another track using the headset keys or the buttons on the lock screen nothing happens. But then a few minutes later all I did happens then :o

L
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
And another really important reason to add:

The CM kernel does use strict mode on SELINUX mode. That means much more security on your apps.

Some other kernels even have no SELINUX mode on!
[Galaxy S 4 i9505 Original Android Development] Danvdh:
any important code has been cherrypicked from all those later versions, this does not matter
[Galaxy S 4 i9505 Original Android Development] !crazy:
What do you mean by SELINUX mode on? They run in permissive mode or don't have SELinux at all? If second, which kernel is that, I'll switch to it immediately.
[Galaxy S 4 i9505 Original Android Development] Jacopo97:
Guys I have a problem by the first nightly i installed on my sgs4. My MIC is very bad, but the strange thing is that is bad only on whatsapp's registrations. Don't know why, i tried different nightlies and snapshots but the problem persist. Does anyone have the same problem? How can i solve? Thanks
[Galaxy S 4 i9505 Original Android Development] sancho_panzer:
He means SElinux enforcing mode, the default mode on CM kernel, is the best option for privacy. The final frase I think it's a typo, he meant no SElinux at all.
[Galaxy S 4 i9505 Original Android Development] lolloilbello:
Mm... I need more informations for example, the device's color ( gold, black, white ) and your favorite color... Cause if your favorite color is black and your device is white, it feels your regret... Btw try with Wa Plus maybe it'll resolve your problem ;)
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree with this part. I am on ART and feel its much better than Dalvik performance-wise, and agree its important we continue testing with ART.
[Galaxy S 4 i9505 Original Android Development] Pikezer1337:
Is anyone experiencing wifi problems where it just won't turn on. It seems to be random but there are times where I turn wifi off and I can't turn it back on.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
for me, i had alot of flickering before with many nighlies. it went away after i did wipe data /factory reset, wipe cache, wipe Dalvik and then reflashed nightly. no flickering after.
[Galaxy S 4 i9505 Original Android Development] :
Does infrared works on AOSP roms? I have tried CM 11 M8 and SlimKat stable 6 and infrared not working with app Smart Remote, also tried another apps for remote and not working... on stock 4.4.2 infrared was working
[Galaxy S 4 i9505 Original Android Development] DeezNotes:
Just tested it. Works for me.
[Galaxy S 4 i9505 Original Android Development] :
Which app? And what rom/kernel kombination?
[Galaxy S 4 i9505 Original Android Development] SilentEYE:
I am sorry. The phone is running in enforcing mode on nightly builds.
[Galaxy S 4 i9505 Original Android Development] dee7er:
Can't find my pictures...

Can anyone help me? I can't find the pictures I took with my S4 when I want to copy them on my computer, although I can see them in the gallery on my phone as well as in the folder.

When I plug in my phone to the computer and go to DCIM>Camera I just can find old pictures I took with the STOCK ROM but not the ones I took with CM11... (all are stored on SD-Card)
[Galaxy S 4 i9505 Original Android Development] nadejo:
the latest nightly is a ****ed up file, fix please
[Galaxy S 4 i9505 Original Android Development] rohail6:
Hey guys I've been running M7, M8 and now M9 and even now I haven't found a "Display Settings"option to change the saturation of the screen. I'm running jflte on an S4 Google Edition. Any help will be greatly appreciated.
[Galaxy S 4 i9505 Original Android Development] a103:
Because there isn't such option in CM yet.
[Galaxy S 4 i9505 Original Android Development] rohail6:
My friend running CM on his Note 2 has that option.
[Galaxy S 4 i9505 Original Android Development] a103:
I'm seeing "Proximity Wake Up" as an option in Settings - Display & Lights. Can anyone help me understand how to use it or how it works? Thanks
[Galaxy S 4 i9505 Original Android Development] !crazy:
As I understood it, that option should only help display to stay off in some strange situations (have no idea which ones) by using proximity sensor.

For example something could try to wake up the screen, and with that option on, first the proximity sensor will be checked, and if it reports something is really near, like when phone is in a pocket, display will stay off.

---------- Post added at 04:30 PM ---------- Previous post was at 03:55 PM ----------

In latest nightly the option is called 'prevent accidental wakeup', what definitely makes more sense.
[Galaxy S 4 i9505 Original Android Development] agentdeep:
I tried sideloading this on GT-I9515, boots successfully but cannot setup my phone because touch is not working.

Hoping for support on I9515 in the future release.
[Galaxy S 4 i9505 Original Android Development] exynoss:
This option will be helpful for those whose phone screen is auto on in pants pockets like me. I have to drive bike so when my legs bend then pocket also becomes so tight then phone unlock button automatically pressed so many times.
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
I'm glad i read this. I had no idea of this new (is it new ?) option.

Very helpful indeed. :good:

Thank you.
[Galaxy S 4 i9505 Original Android Development] exynoss:
Yes its new in cm but already available long ago in miui roms.
[Galaxy S 4 i9505 Original Android Development] HetsHumbucker:
So what would one expect? I expect the exact thing you described: covering proximity sensor and trying to switch on screen should result in screen not turning on. Yet, it does... and additionally creates a wakelock until switching that option off and reboot
[Galaxy S 4 i9505 Original Android Development] Beefheart:
Same here. I vaguely recall reading something about lowering the clock speed of the GPU as a temporary fix. Perhaps someone can confirm this?

Yup, the ability to alter the mDNIe mode is something that was available on previous releases of CM on older devices (it was definitely on my S2 for example). Perhaps it's something they have decided isn't needed on the S4 or it hasn't been implemented yet. This is something I would be interested in seeing.

http://xdaforums.com/showthread.php?t=2675721

I found that but it's back in March, I'm not sure if it will still be compatible.
[Galaxy S 4 i9505 Original Android Development] dee7er:
Can anyone help me with the problem of not finding my taken photos on a pc?
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
This is not a problem of this ROM and should go to a general Q+A thread.
[Galaxy S 4 i9505 Original Android Development] nommy:
Same here.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
Hi everyone, I know it's offtopic. But:

I recieved a OnePlus One invite, which I won't claim as mine anymore, because it simply came too late. I'll wait what Google brings with Android L, and what the manufacturer are doing next spring. So whoever here wants one and is the fastest, here's the link to claim the invite:

https://account.oneplus.net/invite/claim/WDLZ-LSHW-OXP0-KICE

L
[Galaxy S 4 i9505 Original Android Development] jaumesala:
Hi I've just installed this rom and it's amazing super fast.

But I found that mobile it's too hot. Anyone have the same problem?

Do you reduce cpu max freq?

With gobernador and planificador do you use?

Really thank you!!!
[Galaxy S 4 i9505 Original Android Development] Beefheart:
It's more than likely the media scanner going through your storage. Eventually it will stop.
[Galaxy S 4 i9505 Original Android Development] andreiav:
Give the kernel a day or two to settle. I doubt it will persist afterwards.

Otherwise, try a different kernel. I had a great experience with alucard.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] ench18:
Hey guys.. Just wanted to ask if any of you are using the newest (cm-11-20140806-NIGHTLY)? Just wanted to get some input about it. Cheers guys! :)
[Galaxy S 4 i9505 Original Android Development] riksterinto:
I tried updating to the 8/6 nightly and I couldn't get data over mobile. Shows I'm connected to LTE in status. APN appears correct but i can't browse or do anything the net. Wi-Fi works fine. Making calls is also not an issue. Just data.

I flashed the 8/1 nightly over it and mobile data works fine again. Anyone else experience mobile data issues on the 8/6 nightly?
[Galaxy S 4 i9505 Original Android Development] Beefheart:
I notice a lot of people talking about flashing builds over builds. Is there any reason you're not using CyanDelta? I've been using it for a couple of weeks now and it works perfectly with an average zip size of between 10 and 15mb. Fantastic program.
[Galaxy S 4 i9505 Original Android Development] LuigiC6:
I had a similar issue yesterday. Data was working the whole day, then it randomly stopped around 9pm. Still said I was connected, but I had to restart and turn airplane mode on and off every now and then to make it work again.
[Galaxy S 4 i9505 Original Android Development] ench18:
I've seen that on Google Play about a week ago. Read the reviews and saw your post now. I'll give it go. :good: Thanks man. :D
[Galaxy S 4 i9505 Original Android Development] rohail6:
Thanks buddy. It works. But my only gripe is that this Movie mode seems a bit out of date. My brother has an S4 running TW and after the update recently Movie Mode looks even better. Don't you think CM should actually work on this I mean reviewers make such a huge deal about the saturation and I'm personally in love with Movie Mode (Now called Cinema Mode). Is there a way I can request this feature for the next Monthly?
[Galaxy S 4 i9505 Original Android Development] soza971:
Sorry for the off topic but anyone Know an app to sync facebook contact?
[Galaxy S 4 i9505 Original Android Development] dee7er:
Is it normal, that my ringtone is only repeated once and then just vibration is activated?
[Galaxy S 4 i9505 Original Android Development] Synergy510:
This works for me, also gives me high quality pictures of my contacts
[Galaxy S 4 i9505 Original Android Development] exynoss:
After applying theme ringtone and notification sound has changed to default after reboot
[Galaxy S 4 i9505 Original Android Development] Cozmos23:
Having some big freezes on M9 build. And also FCS on different apps.

Using Dalvik

was a clean install
[Galaxy S 4 i9505 Original Android Development] invisiblek:
FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
[Galaxy S 4 i9505 Original Android Development] agentdeep:
Please add support for jfvelte GT-I9515 :)
[Galaxy S 4 i9505 Original Android Development] NZgeek:
You can guarantee that even though people have been warned, there will still be posts here saying "I flashed the latest nightly with [whatever] kernel and it won't boot. Please help."

For those I this thread that do bother reading everything, please tell the non-readers that the problem is with their kernel being out of date, not a bug in CM, and that they should go to their kernel's thread for support.
[Galaxy S 4 i9505 Original Android Development] :
Will the new kernel fix infrared?
[Galaxy S 4 i9505 Original Android Development] feraay:
IR Sensor still working since day one...

What is your Problem?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] !crazy:
You are late a bit. They changed the name of that option few days ago, and they did it with a reason.

First name was ambiguous in that it could be interpreted like the wake up feature which is using the proximity sensor.

My opinion at least.
[Galaxy S 4 i9505 Original Android Development] :
Which app are u using?
[Galaxy S 4 i9505 Original Android Development] nommy:
Did you really read the post I quoted?

The option "prevent accidental wake-up" does nothing than create a wake-lock.

It should prevent the screen to be switched on if the phone is for example in a pocket. But if I cover the proximity sensor while the screen is off and then press home, the screen switches on and can even be unlocked.

In addition to that, a wake-lock will be created until I turn that option off and reboot the phone.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
Does this unified recovery have LOKI support for ATT and Verizon users?

Also, shouldn't the OP be updated?
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
Agree. Too many times people don't bother read just a few previous posts or use thread search button.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Yes I have, and my reaction is related to its first part, a 'question' 'what would one expect? '.

If the options doesn't work well for him, or you because of bug, or whatever, is completely different issue than one I commented on. He quoted my post, where I just said the first name choosen for the options was ambiguous, it was not clear if the options should wake up device, or help in keeping the screen off.

These are nightlies, the feature is new, so it is not unexpected at all if that doesn't work well, or at all.
[Galaxy S 4 i9505 Original Android Development] Milamber:
Has anyone been able to encrypt their device?
[Galaxy S 4 i9505 Original Android Development] !crazy:
Regarding the rest of your post, about the possible bug, I can confirm that covering the sensor, and pressing the home button does turn the screen on. On the other side I haven't noticed any wakelock running, so no need to reboot.
[Galaxy S 4 i9505 Original Android Development] themetatron:
[MENTION=2385005]invisiblek[/MENTION] still need to update recovery with that zip, if we allow "update cm recovery" in developer options?

Edit: found my version in /sdcard/clockworkmod/.recovery_version
[Galaxy S 4 i9505 Original Android Development] mooyaart:
Do you know if the next M build will be the same?

Thanks
[Galaxy S 4 i9505 Original Android Development] sronweb:
+1. Same experience for me.
[Galaxy S 4 i9505 Original Android Development] nommy:
Anyone else having issues with GPS on today's nightly?

I can see 22 satellites but can't get a fix.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Dr.No.pt:
When you mean "today's nightly", you mean 06/08 build right ?

No nightly yesterday or today.
[Galaxy S 4 i9505 Original Android Development] nommy:
No, I mean 08/08 build. Look at cmupdater in settings - about phone.

Don't know why it does not show up on the websites.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Beefheart:
Strange. There is no update available yet in CyanDelta on my phone and, more importantly, nor is there any listed update in the unified nightlies at this time (http://download.cyanogenmod.org/?device=jflte&type=nightly). I'm unsure where CMUpdater got the 8th of August nightly from.
[Galaxy S 4 i9505 Original Android Development] nommy:
Yup, I attached a screenshot to my previous post.

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] M-M-C:
the 20140808 is now listed, but strangely i cant install it. im running the 20140806 right now but when i try to update i get the error "this rom is for jflte, your device is jfltexx" *confused*

i thought the different versions of cm got unified, and i installed the previous version without problem...

/edit
[Galaxy S 4 i9505 Original Android Development] Mittaa:
CMUpdate from within Setting do show 8/8 nightly, and I'm able to download update.

But TWRP refuse updating due to wrong device: "Update jflte doesn't match device jfltexx" ... what !
[Galaxy S 4 i9505 Original Android Development] rodrigoger:
Look at this guys. 2014-08-08 nightly can only be flashed with this recovery above-mentioned . Perhaps in the future, TWRP team do something about it.

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Is it possible to restore TWRP backups with this CWM recovery?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
The update should also be flashable with the current twrp. You could try either to remove the identify check from the updater-script or to replace the build.prop of your system with the one of the new zip before you flash the update.

L
[Galaxy S 4 i9505 Original Android Development] gadgetuk99:
Ir blaster not working on today's 08/08 ? As worked yesterday I use zappir, also had several RR's since install.

Gone back to 0804 for now
[Galaxy S 4 i9505 Original Android Development] djsky2011:
Noise suppression on the mic doesn't work. Sound is distorted when speaking into mic