yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] firephoenixctk:
So my observations running this for a few days on dirty and clean flash version 02/07/15.

I notice when you pull down the quick settings sometimes there is lag.

If you set a profile and change all notifications to 0 but change the ring mode to normal. You will still get notifications however if you set an alarm and set it to the lowest volume but mark ring mode as mute you will not hear the alarm. This has changed since last builds as alarm would ring regardless.

Even though I have set a recurring daily alarm, when I dismiss it in the morning it will not set automatically for the next day I have to set it again.

When waking from sleep to type in my lock screen pin it's more responsive than the last build.

Battery life is better than previous version.

System is smoother and less jerky than previous versions.
[Galaxy S 4 i9505 Original Android Development] rvnieuwh:
After getting home from work yesterday I noticed my phone was turned off.

No problem so far. Things can happen.

But after turning on the phone all my (several) WiFi Access Point passwords were gone.

At home and at work.

Known issue?!
[Galaxy S 4 i9505 Original Android Development] Kippy51:
OK, sim works in another phone, so it's not the sim. But here you say you have two providers, but NOT your provider! That should be in the list. Like I said before, maybe your antenna became bad/loose and your receiving only very strong providers (?).

You wrote it yourself: let someone take it apart and have a look! Good luck!
[Galaxy S 4 i9505 Original Android Development] :
How are you setting ring to mute? Should press volume then press none until next alarm.
[Galaxy S 4 i9505 Original Android Development] firephoenixctk:
I am setting this via system profiles 'Ring Mode' . It worked fine in the previous build. Don't know if this is how CM want to implement this now.
[Galaxy S 4 i9505 Original Android Development] HardOnChairs:
Has anyone used Google Cardboard with this rom? I've never had problems before with the 4.4.4 CM but now it's like Cardboard thinks my screen is different than it really is and the images are set too far apart. I have even made my own profile for my cardboard, but it conforms to all the regular measurements and like I said, worked with other roms.
[Galaxy S 4 i9505 Original Android Development] Lennyz1988:
Yes it's a known bug. When your battery gets flat or you get some other hard crash it loses wifi passwords somehow.
[Galaxy S 4 i9505 Original Android Development] rvnieuwh:
Bedankt :good:
[Galaxy S 4 i9505 Original Android Development] raffmann:
After almost one week of using the last version I am very satisfied with this rom. No bugs have encountered. My only complain about it is the overheating problem.. I am sure that it can be resolved with some tweaks for the kernel. Can anyone recommend me some stweaks settings that will reduce the heat?
[Galaxy S 4 i9505 Original Android Development] skezza:
Actually, I had a similar but equally annoying issue with the alarm app (funny that the standard disclaimer has about the alarm app failing almost as a joke). When I sleep'd the alarm, rather than adding 10 minutes on, it actually reset the alarm to the next day, so it would say in the notification:

"Sleep until 6:20" tomorrow basically.

Very annoying.
[Galaxy S 4 i9505 Original Android Development] Pelanes:
Hi, I've tested the last version 20150701 for some days, and I agree that this version have solved many of the previous rom problems. At least, all the big lag-stuck-black-screen problems are solved. Now apps and system works fine as expected, there are no black screens, and the biggest lag problems are eliminated. Battery life is also ultra-improved, no problems of darin battery during idle or aireplain mode. Good, and thank you team!

I also still experienced device overheating and minor lag problems opening system status bar. But these are very small problems compared to the awful previous rom.
[Galaxy S 4 i9505 Original Android Development] FernBch:
Actually it means Priority Interruption mode is active. What that means is only a priority item will cause the phone to ring, etc during a certain period of time. You can set how it works in settings>sounds>interruptions. I have mine set so only the phone ringer is active while I sleep. I get no email, messaging, etc notification sounds during that time. The only sound you cannot control is the alarm clock when set as it is always treated as a priority interruption.
[Galaxy S 4 i9505 Original Android Development] alexcochifu:
Great ROM... Pretty functional and smooth!! Just one question... is anyone else having a constant crash? it says "Unfortunatedly, bluetooth share has stopped"

And wifi turns off and it takes a reboot for them both to work.... bluetooth and wifi

thanks!
[Galaxy S 4 i9505 Original Android Development] Epicanis:
Oh, THAT "black screen" problem...

Oh, *this* is the "black screen" problem people have been mentioning? I've gotten that a few times, too.

My phone is still configured with no password and just the default "swipe up to unlock" gesture - I haven't been paying much attention to the black screen because I've found that the "swipe up" gesture still works (and turns the screen on when I do it).

If you've got your lockscreen set up to unlock via some sort of gesture that you can do "blind" without actually seeing the screen, give it a try. (If I am in a position to try it next time it happens, I'll see if I can shine a light on the screen and see if I can tell if the backlight just isn't coming on or if the screen's not being updated at all).
[Galaxy S 4 i9505 Original Android Development] r0ckarong:
I had the same problem, navigate to the apps manager and "Clear Data" for the "Bluetooth Share" application. That solved it for me. The same topic was addressed earlier in the thread so please use the search function next time.
[Galaxy S 4 i9505 Original Android Development] smashtie:
Did a clean wipe to upgrade to the Jul 1 build. I still get the bluetooth crash. I managed to pull a tombstone, attached below. Hope this illuminates, [MENTION=5464206]AntaresOne[/MENTION] - I love this ROM so much apart from the bluetooth crash. If you need any logcats, or any other testing/fiddling, let me know.
[Galaxy S 4 i9505 Original Android Development] Drady:
Tombstone?
[Galaxy S 4 i9505 Original Android Development] Morkovich:
Core dump printing after a crash..
[Galaxy S 4 i9505 Original Android Development] finneginsfast:
For some reason the taper wallpaper app seems my phone into a bootloop. Won't stop till I reinstall the rom. Tried several times in clean flashes but still get the same result. Anyone have any idea why or can confirm this behavior one way or the other?
[Galaxy S 4 i9505 Original Android Development] Pinco125:
Hi, about the latest version, for me everithing is good and fast, except for a bug related to phone calls:

When I am using the phone and the screen is on, if I receive a call the vibration starts but i can't do anything, after that the message "dialer has stopped working" appears. In contrast, if the screen is off, when there is an incoming call it turns on correctly and shows the name of the caller and I can answer.
[Galaxy S 4 i9505 Original Android Development] jtash01:
I was able to get it working by reflashing an OD2 TW ROM. The ROM allowed me to update the PRL's and profiles's of the phone. I then reflashed the 701 JDC optimized ROM and get LTE working.
[Galaxy S 4 i9505 Original Android Development] tibaland:
for some reason, whatspp showing to me im recording audios to 1:20 but, only recording 30, 35 secs... what im suppose to do!?

I already changed to awesome player
[Galaxy S 4 i9505 Original Android Development] measel:
Anyone able to use AFWall+ with this build?

I just found out that the firewall was the reason for a wifi connection issue I was having. Wifi didn't connect automatically when mobile data was active:

http://xdaforums.com/showthread.php?p=61420719
[Galaxy S 4 i9505 Original Android Development] stackz07:
I'm seeing mixed solutions for wiping cache to fix bluetooth problems. What is the exact procedure here to get bluetooth stable?
[Galaxy S 4 i9505 Original Android Development] 1weener:
Have you cleared data for BT Share in apps, and Dalvik cache?

---------- Post added at 03:06 AM ---------- Previous post was at 03:04 AM ----------

Not a problem with this ROM... try a re-flash...
[Galaxy S 4 i9505 Original Android Development] skezza:
There isn't. Bluetooth isn't stable. Period. Works for some, doesn't for others. In my case, while I was able to get stable performance while bluetooth was connected (not achievable in the earlier builds, almost guaranteed to cause a crash), I was never able to get Bluetooth call functionality with my car head unit unless I disabled media audio, which I didn't want to do really.

What are the symptons? If you're getting lockups, then you might be able to fix those, but if your issues are like mine, bad luck i'm afraid.

---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------

Very strange bug. Are you restoring call logs using TitaniumBackup? I'd clear the Dialer cache and data.
[Galaxy S 4 i9505 Original Android Development] eTaurus:
For me only a re-flash worked, without wiping anything. Just flash and reboot.

I think I started with the 25/5 build, have been dirty flashing ever since and do not have any of the problems reported here. Ok, the black lock screen issue is there but with either patience or the knowledge that the screen is responding despite it being black it is not really that much of a problem. My phone overheats with bad mobile signal or maybe with heavy usage of mobile data.

I love this ROM and I'm going to stick with it.
[Galaxy S 4 i9505 Original Android Development] flypaper49:
my Camera isnt working correct.

I can make pictures an take videos.

but when i want to watch the videos there are only pixels. sound is okay but no video :(

tied some other video apps /camera apps.

still the same :(
[Galaxy S 4 i9505 Original Android Development] smashtie:
I had to flash a current bootloader, modem and non-HLOS to get my camera to work correctly with 5.1.1. Until then I could use the viewfinder, but clicking to take a picture caused an error. Doesn't sound *exactly* like your issue, but maybe worth a try.
[Galaxy S 4 i9505 Original Android Development] fryandlaurie:
Hi, I had similar problem when my phone went to sleep for long periods over night and had some success with the following settings:

- first of all a recommendation by AntaresOne himself:

"Check that energy saving is not enabled by default: Settings->Battery->press overflow menu->threshold->put "never". "

Of course, this only helps if you do not have your phone hooked up to a charger over night.

- then there is a setting in Settings->Battery above the battery level history/prognosis diagram called "battery mode" (at least I hope that's what it is called in English. I switched to performance mode and now I get all kinds of notifications over night.

It did not - however - fix the smart watch disconnects over night. I have configured my phone to stay unlocked while connected to the smart watch and every morning, without fail, I have to re-enter my password. This might be an issue of Bluetooth 4.0 Low Energy or the smartwatch firmware, though
[Galaxy S 4 i9505 Original Android Development] measel:
Logs flooded with rild errors

1) Radio errors

@AntaresOne

On a clean system my radio logs get flooded with 'rild' errors. Is that something we have to look out for?

07-09 13:18:58.676 D/RIL-QMI ( 231): qmuxd: TX message on fd=17, to qmux_client_id=0, len=56
07-09 13:18:58.676 E/RILD ( 225): QmiUnsolicitedCallback: msgId(81)
07-09 13:18:58.676 E/RILD ( 225): ReceiveMessage: svc(NAS), msg(0x51:QMI_NAS_SIG_INFO_IND), indi(1), size(56), err(0)
07-09 13:18:58.676 E/RILD ( 225): IsConsideredRegistered: Cache hit 1
07-09 13:18:58.676 E/RILD ( 225): need sig info-1, need err rate-0
07-09 13:18:58.676 E/RILD ( 225): Request for Signal Info
07-09 13:18:58.676 E/RILD ( 225): SendMessage: svc(NAS), msg(0x4F:QMI_NAS_GET_SIG_INFO), sync(1), internal(1), size(0)
07-09 13:18:58.676 D/RIL-QMI ( 231): qmuxd: RX 47 bytes on fd=17 from qmux_client_id=0
07-09 13:18:58.676 D/RIL-QMI ( 231): [SMDPORT] >> BEFORE, Write SMD Port [fd = 10] [msg_len = 13]
07-09 13:18:58.676 D/RIL-QMI ( 231): [SMDPORT] << AFTER, Write SMD Port [rc = 0]
07-09 13:18:58.696 D/RIL-QMI ( 231): qmuxd: TX message on fd=17, to qmux_client_id=0, len=68
07-09 13:18:58.696 E/RILD ( 225): ReceiveMessage: svc(NAS), msg(0x4F:QMI_NAS_GET_SIG_INFO), indi(0), size(68), err(0)
07-09 13:18:58.696 E/RILD ( 225): Result(0), Error(0)
07-09 13:18:58.696 E/RILD ( 225): Signal Strength: [3, 99, -1, -1, -1, -1, -1, -1, 30, 82, 9, 140, -1, 2147483647]
07-09 13:18:58.696 E/RILD ( 225): GLNET-MGR: evt(201)
07-09 13:18:58.696 E/RILD ( 225): NET-MGR: EVENT_NETWORK_SIGNAL_STRENGTH
07-09 13:18:58.696 E/RILD ( 225): OnNetworkSignalStrength() - mSignalBar: 3
07-09 13:18:58.696 D/DefaultPhoneNotifier( 1085): notifySignalStrength: mRegistry=com.android.internal.telephony.ITelephonyRegistry$Stub$Proxy@1c2c0916 ss=SignalStrength: 99 -1 -120 -160 -120 -1 -1 30 -82 -9 140 -1 2147483647 gsm|lte sender=Handler (com.android.internal.telephony.gsm.GSMPhone) {348d2bec}

2) Auditd

This is another error that floods my logs:

07-09 13:29:00.903 I/auditd (14256): Starting up
07-09 13:29:00.913 E/auditd (14256): Failed on audit_set_pid with error: Protocol not supported
07-09 13:29:00.913 I/auditd (14256): Exiting

3) AFWall+

I just tried AFWall+ on a fresh system and still have the error I was talking about earlier. (Look here) See attached log.

Anyone an idea if I have to change a setting or something to get the firewall to work correctly?
[Galaxy S 4 i9505 Original Android Development] fryandlaurie:
Just wanted to give some more feedback on the July 1st release. With people mostly reporting errors in this thread it might create a wrong impression.

I have no issues whatsoever but I obviously do not go on an in-depth testing spree through all features after every install. It's just day to day use without problems.

I had cleaned/wiped/formatted everything before installing the first release of this optimized build. As an intermediary step I installed the official Touchwiz Lollipop version. Initially this was to get the official boot loader and modem but when I booted the first time I was prompted to update the camera firmware. Having flashed the latest firmware for the camera might be one of the reasons my camera works without problems.

I used F2FS format for the three standard partitions, not for SD card though. From then on it was all dirty flashes (setting up everything after a wipe takes ages, at least a full working day, so I ignored AntaresOne recommendation for a clean install of the July 1st release)

I flashed the XXUHOF2 modem and bootloader a few days ago when I realized that as of July 4th it is the officially released version for i9505 in Germany. Did not break anything but also did not improve anything I could notice.

I can vouch for bluetooth functionality as I am a heavy user of bluetooth: smartwatch connection, audio headsets and handsfree and media streaming in the car.

I can confirm reports that the phone seems to be getting hotter with heavy use, during navigation for example. This is compared to the same usage pattern with official CM11.

Overall, battery life is great, better than the aforementioned use with official CM11.

I did not change any settings in STweaks.

This is the best android experience I have had with any phone, no contest!
[Galaxy S 4 i9505 Original Android Development] Pinco125:
It seems that the problem is connected with the fact that I've disabled heads-up notifications. With the option enabled, all works well.

Can somebody else check if it is a common problem? Thanks :)

(nothing restored, clean flash)
[Galaxy S 4 i9505 Original Android Development] Blackbat007:
I've got SIM lock enabled and get prompted for my SIM PIN twice on every boot. Is this a known bug with the build? It's in the latest 01/07 build, and the previous one. Not sure before that, but it's never done it with the CM12.1 nightlies.
[Galaxy S 4 i9505 Original Android Development] benjamen50:
IMO the heat up when using GPS for example on google maps is normal.
[Galaxy S 4 i9505 Original Android Development] stengr:
I came from may24 build. Battery life is almost 2x worse. 3.5 screen vs 6 hours may build. Airplane+wifi only. Full wipe.

Problems with all firewalls like afwall or orwall. Stweaks stoped working like i mentioned in prevouos post. Cant even compare this build to may24
[Galaxy S 4 i9505 Original Android Development] fmehdi:
Battery drain in airplane mode with the last build
[Galaxy S 4 i9505 Original Android Development] :
I don't use airplane mode no more. Battery save + no notifications till next alarm mostly. You're unlucky if you lose more than 3% battery. I can live with that.
[Galaxy S 4 i9505 Original Android Development] v00d007:
The setting for vibration intensity doesnt persist after full reboot.

The network meter is still too tiny to be read easily. (0701 build)
[Galaxy S 4 i9505 Original Android Development] Liam0o:
Are you using Stweaks to set vibration strength not the setting built in to CM?
[Galaxy S 4 i9505 Original Android Development] TessellatedGuy:
Hello, Im new here so II'll cut right to the chase....(Yeah Im a newbie too)

So um First of all wanna appreciate your hard work and frequent improvements BUT there is an issue which I have been facing lately in the 20150701 version of this rom. Stweaks doesn't work anymore, it just says "no kernel support" and I have checked if my kernel was official too. I have tried rebooting and reflashing the rom but no luck, what could be the reason?:rolleyes:
[Galaxy S 4 i9505 Original Android Development] fryandlaurie:
The heat up is definitely normal, no disagreement there. But compared to the exact same use case ( running google or other navigation app while being linked to the entertainment system in my car) with CM11 it seems more pronounced. As long as everything works I am not worried about that, though. I only mentioned it to confirm other reports in this thread.
[Galaxy S 4 i9505 Original Android Development] Liam0o:
Have you made sure that root is enabled in developer options? That's the most likely cause, if that still doesn't work try flashing supersu from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip and opening stweaks again
[Galaxy S 4 i9505 Original Android Development] TessellatedGuy:
Wow, flashing superSU actually fixed it quick! Can't imagine why the options in developer menu don't work for STweaks. I think decon needs to fix this, or maybe it's just me? Thanks so much for the help bro. Now I can get back to tweaking...... :good:

---------- Post added at 07:47 PM ---------- Previous post was at 07:42 PM ----------

Decon=Devcon but my fingers≠keyboard:silly:
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I do not use SuperSU and integrated root on CM works perfectly with Stweaks... maybe you do not answer correctly to Privacy Guard pop-up and so you deny root access to the app...
[Galaxy S 4 i9505 Original Android Development] TessellatedGuy:
Nope, I had granted it permission and even checked "remember my choice". Totally rom issue.
[Galaxy S 4 i9505 Original Android Development] firephoenixctk:
Yeah i had this issue with a clean install of the integrated root. Installed superSU and it went fine
[Galaxy S 4 i9505 Original Android Development] tibaland:
i used whatsapp to send a video to a friend, while recording a video camera and caught the mobile reset and is in infinite boot , you have something to do without having to reinstall the ROM ?
[Galaxy S 4 i9505 Original Android Development] :
You should make backups in TWRP or CWM while it's stable. Takes minutes to restore then.
[Galaxy S 4 i9505 Original Android Development] tibaland:
i tryed but when i restaure he back to bootloop
[Galaxy S 4 i9505 Original Android Development] ramsankar83:
Used an earlier version for a while! Is there a camera app that is as-good-as or closer to the Samsung camera? Tried open camera app etc. but photos at lowlight are bad compared to stock samsung ROMs camera. Please let me know.
[Galaxy S 4 i9505 Original Android Development] v00d007:
No, I don't use Stweaks at all. The settings slider is still in the same position, but the strength's always back to def value. Have to touch the slider at least once to get a lower value working again.
[Galaxy S 4 i9505 Original Android Development] :
I assume you don't mean you tried backing up and restoring after you had the problems :D

You may need to reflash bootloader/modem if clean flash of rom doesn't work either.
[Galaxy S 4 i9505 Original Android Development] gkkovacs:
Hey [MENTION=5464206]AntaresOne[/MENTION]

Have been testing your 0701 build for more than a week now (dirty flash). Unfortunately I had several strong lags (most often when using both Facebook app and Chrome, both memory hogs), also had wakeup problems (especially during calls), but not as severe as before, phone was able to recover from them in a few seconds without reboot.

I am using interactive governor, intelliactive hotplug, touch boost set to 1566 MHz and default OOM levels.

Still it seems there is a serious memory management issue, and I don't really understand why my LG G-Pad 8.3 (same Snapdragon 600, 2GB RAM, also running CM12.1) has none of these issues, it's nice and smooth all around. Are these issues (slow wakeup and strong lags) present in vanilla CM 12.1?
[Galaxy S 4 i9505 Original Android Development] hisomraj:
i had this issue many times. The phone becomes hot and wont reboot. It will shut down. Switch off the phone for 3-4 hrs and reboot. If it still does not then only option is reflash the ROM. I had done it 2 times
[Galaxy S 4 i9505 Original Android Development] Trevy81:
Use cameraMX

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] dave_p_b:
Had the same problem as you after I disabled heads up notifications. With screen on I could see the call notification at the top of the screen but couldn't press the answer button. Then the dialer would fc and phone reboot.

Like you I enabled heads up notifications and I can answer calls properly now.
[Galaxy S 4 i9505 Original Android Development] :
This is answered like 1000 times
[Galaxy S 4 i9505 Original Android Development] olskar:
I share the same experience as you. I am very satisified except the big lags, sometimes the phone almost freezes due to what I guess is memory leaks of some kind.

I am also running CM12.1 on a LG pad with great results and no lags, also running it on devices with far worse hardware than the I9505, but no lag there.
[Galaxy S 4 i9505 Original Android Development] Lennyz1988:
You cannot ask for help when you didn't even do a clean flash. The OP clearly states that you should do a clean flash on this build. Do that first before asking for help.
[Galaxy S 4 i9505 Original Android Development] mswal2846:
+1
[Galaxy S 4 i9505 Original Android Development] kubapl66:
Oh crap, sorry

Sent from my Galaxy S4
[Galaxy S 4 i9505 Original Android Development] churchey360:
No contacts force close for me. I just can't use STweaks because it says no kernel support
[Galaxy S 4 i9505 Original Android Development] Yousvel:
Device-related issues: sound *may* have random issues

[MENTION=5464206]AntaresOne[/MENTION]: Is this sound in general or playing music?
[Galaxy S 4 i9505 Original Android Development] churchey360:
I get a force close when i use the back button to exit the CyanogenMod easter egg (flappy bird game)

I'll use CatLog to try to capture it to see what causes the force close.
[Galaxy S 4 i9505 Original Android Development] robertogl:
I've also this problem on Lollipop, but the memory if free. I mean, i've 800mb of free ram, but every app is reloaded seconds after being used...