yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ghaston:
It worked fine with stock. I clean installed this rom 2 times, same bug happened. Anyways, I somehow fixed the issue by installing SaberMod kernel.
[Galaxy S 4 i9505 Original Android Development] FernBch:
Strange, for me this build has been very crisp, clean, and smooth.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Slimbus overclock for better audio quality

This could be the fix for our sound problems. [MENTION=4899086]alucard_24[/MENTION] Could you check out the saber mod kernel and use some of their optimalisations?
[Galaxy S 4 i9505 Original Android Development] yfben:
Thank you for your effort and work.

Im waiting for the new release since yesterday night.

Iam checking the page every 10 minutes ;)
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
[MENTION=5464206]AntaresOne[/MENTION]: I've flashed the October 9th build and battery drain is a lot higher. My battery was at 96% I think and look at how much it's drop with so little screen on time:

This is a drop of over 30% in 25 minutes which is over 1% per minute. This is too much. Any idea what the cause could be? I did a dirty flash btw.
[Galaxy S 4 i9505 Original Android Development] der_Kief:
Cannot confirm this !

I also flashed October 9th build an battery drain is almost the same as with August 17th build.
[Galaxy S 4 i9505 Original Android Development] verossi:
[MENTION=5464206]AntaresOne[/MENTION],

Could you confirm whether Call Forwarding is working? I suspect that in the CM also isn't working!

Regards,
[Galaxy S 4 i9505 Original Android Development] myawan:
In Italian:

'When' is equivalent to 'Quando'............When? Quando?

'We are waiting' is equivalent to 'siamo in attesa'..........We are waiting! siamo in attesa!

lolzzzzz............please don't accuse me of asking for ETA, this post is for general knowledge. :)
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
There is an early version of the new build you could flash if you look at Antares post a few pages back..

I am really exited for the new release too but I will wait for it to be published. :cyclops:

Should be any day now.
[Galaxy S 4 i9505 Original Android Development] ttakacs:
What are your kernel settings? Did you overclock or are the kernel defaults overclocked?
[Galaxy S 4 i9505 Original Android Development] wpyh:
Well, maybe your post got buried under all the chatter, or maybe you didn't explicitly tell AntaresOne that you wanted to help with graphics?
[Galaxy S 4 i9505 Original Android Development] electrolt:
Hey, i came from TW rom and threre was an option with wanam xposed to set symbols on keyboard.

Can I do it here as well ?
[Galaxy S 4 i9505 Original Android Development] a103:
No. Wanam xposed is only for TW ROM.
[Galaxy S 4 i9505 Original Android Development] electrolt:
I know that wanam only for TW, but any other ways also ?
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Alucard's kernel can not be overclocked, you can only edit (on cpu) the governors, voltage, clockspeed (between 384 and 1890), hotplug and values that has to do with steppings.

I changed 3 or 4 values with hotplug and it has no to little stutters (maybe 2 times in 30 minutes).

---------- Post added at 06:13 PM ---------- Previous post was at 06:11 PM ----------

Other keyboard?
[Galaxy S 4 i9505 Original Android Development] FernBch:
Once the next Public Release is ready it will be announced here.

Because there were a few kernel changes you should wipe davlik cache, cache, and system as a minimum. A clean flash is recommended. Flash the ROM, the latest Gapps from the link in the OP (I recommend the micro), wipe cache/davlik cache again, then reboot. I did a clean install and have seen as much as 30+ hours with 3-5 hours SOT.

I can't say when, but it is coming and will be announced here when it is. Other than that all I can say is patience my friends.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
... I've given an ultimatum to Mattia... he is perfectioning ToolBox... but this evening we must go... if not, I'll come to his house and kill him!! [emoji41]

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] rosseloh:
It's not just him, and it seems to be just this rom (I haven't tested with anything else other than stock, though). But this is a brand new phone as of a couple weeks ago, and once you can get it to turn on, the digitizer works fine. It's maybe a 50% success rate when you wake it up.

I have not made any changes apart from flashing the rom in the first place. Everything was wiped, multiple times. Micro opengapps (installed because I thought it might help with the bluetooth fc), everything else is as it comes in the rom. The issue was seen right away after the flash, before I had a chance to get any apps installed. (How much any of that helps you narrow it down, I don't know. Let me know if there's any data you want).

For what it's worth it doesn't only happen on pressing buttons; it also happens when the phone is woken up by an incoming call, which is about the only time that it's really annoying (the rest of the time you just turn the screen off and try again).

I'll see how it goes with the new version once the official build comes out.
[Galaxy S 4 i9505 Original Android Development] mafsi:
How about TK gapps?

Why you recommend micro. I.m using pico gapps. Pico is not good?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
This because we try testing all with the same package... to avoid strange situation related to variety of gapps... and we suggest what we used...

This doesn't means other gapps are not ok.

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
My phone turned off while plugged in while watching a YouTube video. Probably because the battery drain is higher that the rate at which it is being charged. I don't know what has changed in the October 9th build but I'm getting terrible battery life. This incident happened AFTER I re-flashed the ROM with a cache, dalvik cache, system and preload wipe. I got good battery life on the August 17th build.
[Galaxy S 4 i9505 Original Android Development] FernBch:
Very true. If you search through the thread you will find some reported issues with things like BT share, Google Play Services, etc. Some used other packages and had no issues, some had to reflash with a different package. We try to use the same package when testing to make it easier to sort out issues. Less variables = less to sort out when looking for what is wrong.

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

I would start with BBS and see what is using the most and go from there.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] mafsi:
I see. Thanks a lot!
[Galaxy S 4 i9505 Original Android Development] ttakacs:
I am using your Alucard settings (from post #6525). What settings are you using in the Saber kernel?
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
Check my updated profile in my signature.

I haven't tested the saber kernel, I'm not even sure with what app you can change values, but it could fix stuttering problems. Now I've no problems, just sometimes random battery drain

Batterylife seems okay

11,5h on which 5h is screen on time (20 minutes of heavy IR usage, I code arduino stuff with an IR sensor), have 18% left now.
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
Here are my kernel wakelocks. Any idea what's wrong?

My battery life is absolutely terrible with the October 9th build. It's like melting butter. Absolutely atrocious. I had good battery life with the 17th August build. Oh and one more thing, while I was at university, my phone randomly rebooted and it did the optimizing apps thing again. Since then I have re-flashed the ROM with cache, dalvik cache, system and preload wipe and I flashed the pico variant of Open GApps (I used pico for the August build also and got good battery life). [MENTION=5464206]AntaresOne[/MENTION] and other devs: Any idea what's wrong? The battery life is not even slightly worse, it's a lot worse.
[Galaxy S 4 i9505 Original Android Development] biazoto:
Kernel wakelock seems ok... Look at partial wakelocks and alarms section too

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] FernBch:
Also look at the CPU states and see if it is entering deep sleep or not. I ran the same build (clean flash) and hit 30+ hours battery with 4+ hrs SOT.
[Galaxy S 4 i9505 Original Android Development] der_Kief:
Is Mattia still alive ? ;)
[Galaxy S 4 i9505 Original Android Development] s3icc0:
Well I personally prefer last perfect build before you guys will work on Android 6 :) btw are the sources released yet?
[Galaxy S 4 i9505 Original Android Development] eTaurus:
+1

Take your time! If it really is the last build before you start working on Android 6 it has to be free of all bugs that affect every day use.

And please, [MENTION=3545504]smeroni68[/MENTION] , do not kill Mattia or anyone in JDC team, your work is awesome. [emoji106]
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Thanks for your patience... we will support LP roms until December anyway, but the focus now is already on MM...

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] benjamen50:
I don't know why this rom won't boot, Do I have to do a factory reset? I went from 07 August to 09 October rom. (Not sure if these are the correct dates)

Edit: NVM got it to boot.
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
Did you do a clean flash or a dirty flash? Also, what exactly is the problem you're having? If the CyanogenMod animation has frozen, force shut down your phone and then turn it back on. That's happened to me and a forced manual reboot worked for me.
[Galaxy S 4 i9505 Original Android Development] der_Kief:
i'm running Oct. 09 build for two days now (clean install). Everything is running good so far and overall i'm happy.

But there are two things which are very annoying to me:

- every now and then i have some stutter/lag with differnet apps. Mainly noticeable when scrolling within the apps.

Tried differnt kernel settings (e.g. I/O Sched. TCP Congestion ....) but didnt found a viable solution (any further suggestions?)

- Screen On delay (2-3 sec) on incoming calls (i thought this is fixed within newer versions!?)
[Galaxy S 4 i9505 Original Android Development] benjamen50:
Yeah, Cyanogenmod animation frozen, fixed it by doing forced manual reboot like you said.
[Galaxy S 4 i9505 Original Android Development] electrolt:
YEAH AGREE with screen delay
[Galaxy S 4 i9505 Original Android Development] Gerxp:
I see people talking about oct 9 version. Where is the downloadlink?
[Galaxy S 4 i9505 Original Android Development] baudbox:
Here it is > http://xdaforums.com/showpost.php?p=63357292&postcount=6514
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
Guys relax..

You decided not to wait and install an early version of the ROM..

So don't complain about bugs!

Just wait for the oficial release and believe in it.
[Galaxy S 4 i9505 Original Android Development] Chopperpilot:
really looking forward for the next release!

+1
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
I disagree. Bugs should be mentioned in case they have not been fixed since the October 9th build. Don't you want the next release to be bug-free?
[Galaxy S 4 i9505 Original Android Development] PePeMoke:
You read this right?
[Galaxy S 4 i9505 Original Android Development] Pedantic_Android_User:
I still disagree. If there are any bugs, the developers should know in case they have not been fixed. Don't you think?
[Galaxy S 4 i9505 Original Android Development] der_Kief:
+1

[MENTION=6633801]PePeMoke[/MENTION]

Korinthenkacker :p
[Galaxy S 4 i9505 Original Android Development] -Ric-:
If the developer said he is not interested in bug reports of a version he didn't officially release just respect it. Wait until he actually releases something stable and that he's happy releasing and then you can report whatever you find.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
the 9th oct build was not meant to be public and they posted that build with a warning - just for the impatient users - the flashaholics, they very probably know about all of these bugs so not needed to post it here and probably they will refuse to read such input - you still have the august build as the last official - post bugs from that build
[Galaxy S 4 i9505 Original Android Development] der_Kief:
.... and if this bugs are not reported and the devs do not know about them and than they release a new public version .... you are the first ones which are crying :p
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
[MENTION=5464206]AntaresOne[/MENTION] It seems that the rom has issues with playing .aac files, in this case whatsapp voice notes.

On whatsapp it crashes about 2 seconds before the voice note ends and the same using a music player (in this case I got this error that I've neven seen)

The files aren't corrupted, they all work fine on my pc.

I could provide logs, but I don't think you're interested in them as I use xposed, but this also happens without xposed, it exsists since I think one of the first builds (I can not remember)
[Galaxy S 4 i9505 Original Android Development] FernBch:
He can't kill me, I am way too far away!! Lol

When the link was posted to the Oct 9 build it was clearly stated it is a test build and not to report bugs. Flash at your own risk. When the builds are worked on internally we have a defined set of conditions to go by. It makes it more simple to find and fix bugs with the ROM itself.

Other things that are proven and known to cause issues are some Gapps packages (especially older ones), third party apps (such as Xposed), and anything that modifies system files. It has also been requested that if you modify any system files not to report bugs. You modified a system file, the team cannot fix that. These things are all beyond the control of the team and some are impossible to guard against.

As for Gapps packages, yes you can use one of your choice. We only suggest the open micro because that is the one everyone uses to test with. There are too many versions out there and to test for several days with each one would slow development so badly updates would never come.

As for flashing, many times a dirty flash will do just fine. Sometimes a clean flash may be recommended (but not required). When it is there are valid reasons. Sometimes a major code change would and dirty flashing could run the risk of an issue because of some "leftover" item that would be otherwise recreated after a clean flash. If clean flashing was recommended and you didn't, that is not the team's fault.

Another item to note is STweaks. It modifies system files, if you have tweaked undo them first and go from there. Things like undervolting and such can wreak havoc.

For many bugs one must start with only the ROM and see how it behaves, then start installing apps and testing one at a time. It can be very time consuming and frustrating. Even more so once you consider not everyone uses the same apps or combination of apps. Some app creators do excellent work and the apps they create are awesome and trouble free, while others are not.

One such example is an issue I had with the August 17 build and the Oct 9 test build. The battery drain was horrible. Previously I easily could go an average of 18-20 hours with normal to above normal usage, it dropped to 8-9 max under the same conditions. Using BBS and the one app at a time method it turned out that Avast updated the anti theft app and broke something in it. Once I removed it I was back to 20 hours battery plus. On lighter times I can get 36 hours plus easily.

In short, we are only human and do strive to do our best. Beyond that please be patient with the team. This is done for YOU for Free. If you want to donate it is always welcomed with a big THANKS and and open heart. But it is never required.
[Galaxy S 4 i9505 Original Android Development] rtg2:
Oh man, I certainly cannot wait for a new build. My phone's barely usable these days (probably my fault from many misc tweaks etc!). I just had a couple of questions ahead of a new version / fresh rebuild:

- With the Mini/Pico GApps recommended - does this mean that more of the "standard" GApps that many users install, that aren't in these small packages, go into the User partition rather than System? Result being that the System partition sits there gloating with lots of free space, while the User area gets full even quicker? Due to lack of space, I've moved a lot of apps to SD (built-in functionality, nothing fancy) and I'm sure this doesn't help with strange problems...

- Second question relates to my major issue at the moment. I've not captured logs for this yet but wondering if anyone has seen this / might know a possible reason: it seems that when the phone switches from WiFi onto Mobile Data (and vice-versa) the whole phone comes to standstill for some amount of minutes. Unresponsive screen/UI, Spotify glitches/stops etc. Pretty much makes the phone useless when I'm on the go! Am on the latest I9505XXUHOH2 Radio/Bootloader since 5-6 weeks ago, and have possibly had the issue for almost that long (been too busy to really diagnose). Could this be related, or something else?

Have been desperately waiting for an acceptable Flagship phone to be released by someone (> 1080p, Wireless charging, Android Pay, USB-C, decent size battery, > 32GB storage+SD or > 64GB internal, OK-to-Good camera, not too phablet-sizey), but after the disappointment of the Nexus 6P release (can't believe Google let that ugly thing come out with their name) I've gone for an interim solution with a Pre-order for the Sony Z5 Premium. Now just counting down until then by nursing this beaten up old 9505 along... One more Clean Flash left in me I think...
[Galaxy S 4 i9505 Original Android Development] FernBch:
Gapps normally go to /system regardless of install method. Unless I am mistaken the general thought is the install script in the package is where things get screwy. The important parts are in the smaller packages and I just update/install all apps from Google Play.

Not sure about your WiFi/data issue but I know at least some have been addressed for the next build.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Have you try AOSP rom? Give it a chance...

Inviato dal mio GT-I9505 su OptimizedCM 12.1 (JDC)
[Galaxy S 4 i9505 Original Android Development] amandreamartino:
+1

Had this problem in CM nightly too.
[Galaxy S 4 i9505 Original Android Development] rtg2:
I would have, but I've been holding on with the lure of a new "Optimised" version for a while :) My luck over the last year with this ROM (5.0 and 5.1) has been that a new build comes out just after I do a clean flash!
[Galaxy S 4 i9505 Original Android Development] mooyaart:
Hurry up and do a clean flash then ;)
[Galaxy S 4 i9505 Original Android Development] .Ejekt:
I feel like after a month or so on the ROM my performance dips considerably. Speed and responsiveness stay the same, but bugs start creeping out. This time, over the past few days, I've started noticing a lot of data/WiFi related issues. Typically this is fixed by toggling airplane mode or rebooting my device once or twice. However, more recently it seems that when WiFi or data starts acting up I actually get logged out of any app that I have open at the time. It's strange, but there's definitely a sense of entropy for me with every iteration of this ROM.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Call a terminal and issue:

su -c fstrim -v /cache && fstrim -v /data

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] .Ejekt:
Just throw this entire line into terminal?

I get:

fstrim: FITRIM: Invalid argument
[Galaxy S 4 i9505 Original Android Development] NZgeek:
You're correct about installing any GApps that weren't in the zip file. These are installed as regular apps and go into /data rather than /system.

Installing these apps into /system doesn't necessarily mean that you're saving space on /data, however. Any app updates get downloaded to /data, and live there in addition to the older copy in /system. The only way around this is to move the update to /system, or to install a newer GApps package.
[Galaxy S 4 i9505 Original Android Development] Strephon Alkhalikoi:
Issue the commands separately, thus...

su -c fstrim -v /cache
su -c fstrim -v /data

It should then work.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
^up and everyone else here:

I'm preparing the build environment to build a new public release, this one will include a lot of changes and it's the biggest update ever, clean installation is not mandatory but strongly adviced. If you get errors which should not be inside please make a clean install before reporting, thank you for the collaboration
[Galaxy S 4 i9505 Original Android Development] Jared20098:
I was one of the original Oct. 9th testers, and unfortunately I did encounter a few problems after using the build for a few days. I got a random freeze 2 times (one opening the Steam app loading content, and another when I got out of an app, I forgot which one), I got a stuttering audio issue, although with only one song, and that's pretty much it from what I remember.

Although this is a test build, so all of it will most likely be fixed when AntaresOne releases the final version of the build!
[Galaxy S 4 i9505 Original Android Development] subwars:
That update on the op, you're just teasing us all.
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi AntaresOne ! Good news ! As clean install is not mandatory, will it be possible to update from the build of july, last one installable via Multirom ?
[Galaxy S 4 i9505 Original Android Development] krGemini:
By writing "Strongly Advised" and that too in BOLD font, he meant to say it is near to mandatory.
[Galaxy S 4 i9505 Original Android Development] stephendt0:
Sounds like it just hasn't been updated. Considering I just got a LG G Watch R, bluetooth issues are probably a deal breaker for me :( Will keep an eye out for when builds are more stable.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I have no issues with bluetooth. I can connect to any device and send files. It is worth a try
[Galaxy S 4 i9505 Original Android Development] stephendt0:
Nah, I'll wait. Not worth the potential hassle. It's not like I desperately need 12.1, but performance improvements would be nice.
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
If you have time, try dual boot this rom. It is easy to do, it just takes some time to set up the rom once installed. I recommend this rom because it is fast, smooth and the batterylife is not that bad.
[Galaxy S 4 i9505 Original Android Development] raffmann:
Battery life is not that bad!?!! For me is the best. I get usually 4.30h of sot and i am using my phone a lot. Whatsapp, youtube, browsing...
[Galaxy S 4 i9505 Original Android Development] devilyuri:
Instead the battery decreased of 5% during the night

With plane mode and power save mode :/
[Galaxy S 4 i9505 Original Android Development] a103:
It shouldn't happen, cause I've been using supersu on all AOSP lollipop ROMs. I've used supersu 2.46
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
Hi antaresone.

Im future official cm12.1 continue use F2FS or not? Thanks
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Official CM support /data and /cache on F2FS...