yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] vt0r:
Binaries and shared libraries built for AOSP pre-5.0 won't run or load unless they were explicitly compiled with the -fPIE option. Unfortunately, not only is OpenSSH one of them, but it doesn't look like there are currently plans to add it back. I don't have much (any) spare time these days, but I'll see if I can get it built with the NDK and/or Christopher's Linaro. No promises, of course.
[Galaxy S 4 i9505 Original Android Development] benjamen50:
Is getril app even reliable? I've tried this app before and it screwed up the modem / RIL firmware on my samsung and i had to reflash the modem / ril to a working one through recovery.

If you can't get the rom to install and boot on your phone successfully. My advice is wait until the rom becomes stable enough.
[Galaxy S 4 i9505 Original Android Development] Lurninn:
Well, I flashed: CM12, Gapps 5.0, SuperSU succesfully

After that i installed the GetRIL app and pressed the "Download & Install RIL" .. it downloaded something, but i didn't do ANYTHING with the RIL files that you posted ( No idea if i was supposed to.. ) When i tried calling myself i could just see the call!

Besided that:

Awesome, much better than first build. Everything works lots smoother IMO.

Sound is working, 3G is working, I'm not going back ;) :good:
[Galaxy S 4 i9505 Original Android Development] Triscuit:
The ROM is running perfectly. Flashed with TWRP 2.8.0.1
[Galaxy S 4 i9505 Original Android Development] nadejo:
this happens when you change from f2fs back to ext4 and forget to wipe the internal sd.

go to recovery and wipe cache system and factory reset(data and internal sd) using ext4 and reflash the rom. thats all
[Galaxy S 4 i9505 Original Android Development] rboy28:
I can confirm that the GetRIL app fixes the issue with incoming calls.

I9505 jfltexx
[Galaxy S 4 i9505 Original Android Development] Sulaimanshariff:
there were root instructions in the op dont find em anymore can anybody help me out with that flashed succesfully:D
[Galaxy S 4 i9505 Original Android Development] angelcalibur:
What happen if we convert the rom with ktoonez tools to instal it on a ALL-F2FS (means /system /data and /cache) ?
[Galaxy S 4 i9505 Original Android Development] Lurninn:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Just Flash this in TWRP
[Galaxy S 4 i9505 Original Android Development] Sulaimanshariff:
thanks a lot but is thr i way i can disable touchkey lights and editing build.prop to get nav keys will work?:D
[Galaxy S 4 i9505 Original Android Development] edzamber:
Here is a flashable Patch with RIL Libs for i9505 ;)

http://www.mediafire.com/?imtb1lc19hmh4pw
[Galaxy S 4 i9505 Original Android Development] jd1001:
Do I just flash that after rom and gapps?
[Galaxy S 4 i9505 Original Android Development] nadejo:
it might work because the kernel of this rom boots beyond the i9505 boot screen when all is on f2fs but it is a endles bootloop. converting the rom might solve it. i didnt test it my self . try it out and if you want and tell us if it worked for you.
[Galaxy S 4 i9505 Original Android Development] michelino.chionchio:
It seems that incoming calls works perfectly here, without GetRIL.

GT-I9505

Carrier 3 Italia (if it's can bu useful)
[Galaxy S 4 i9505 Original Android Development] edzamber:
After Rom or after Gapps as you want.
[Galaxy S 4 i9505 Original Android Development] Yoz182:
Okay

Rom + Gapps + SuperSu flashed with TWRP 2.8.1.0 , installed GetRil and Titanium Backup via PlayStore.

Everything is ok for daily use.

For those who have problems with Titanium Backup, just reboot phone and it works !

Thanks for this rom, I'm happy to see Lollipop !
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
RIL problem now is just how libril is implemented. Fixed on this morning by the way. :)

exFAT is fixed, now fixing F2FS

EDIT: exFAT binaries are unstable, I decided to remove it for now, probably will be fully working in the next build :)
[Galaxy S 4 i9505 Original Android Development] kipue:
Guys, anyone got an issue with not being able to install apps?

At my first boot, no problem but now I cannot press the install button.

I remember it happened to me because of a root version issue but I'm up to date with beta 2.27 and I got the problem, anybody got the solution?

EDIT :

I had installed "Lux" application, and that was the reason -.-

Anyhow, fixed!
[Galaxy S 4 i9505 Original Android Development] jd1001:
Gapps Issue

Hey guys, I know this has been mentioned before but is there any way using CWM to avoid status 6 error when flashing Gapps? I know I could use TWRP but I really don't want to. Is that my only choice? Thank you.
[Galaxy S 4 i9505 Original Android Development] Sulaimanshariff:
ROMs super smooth wish wouldn't get option to enable virtual keys had to edit BP and also to disable touch key lights very annoying thanks a ton again keep up the good work[emoji8]
[Galaxy S 4 i9505 Original Android Development] jd1001:
Edit: Flashed latest Gapps without issue.
[Galaxy S 4 i9505 Original Android Development] TLK3:
There are far better options. JuiceSSH, for example.
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
In MoKee ROM 4.4 there are bin SSH, and SSH in terminal. It is very usefull.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Maybe open source is important to him, as it should be to everyone (just my opinion.).

But on the other side android community is definitely not the one who really cares about it. Even the most popular super user application is not open source and no one cares.

---------- Post added at 05:51 PM ---------- Previous post was at 05:47 PM ----------

No, one doesn't really have to reboot. Killing a process or two will do the job. Not able to check the names b/c u am not running lollipop and don't even have the camera issue with latest cm 11 builds, so cannot test, what would be important. But I was always able to restart some camera and/or media relevant processes and to get my camera back (to resolve cannot connect to camera issue).

---------- Post added at 05:55 PM ---------- Previous post was at 05:51 PM ----------

Snap camera has a terrible issue with light sensors or something. All videos made in low light are just terrible, terrible. Only if one uses default settings the issue doesn't have to appear, but can. Using default settings is not an option b/c one has to check 'skip preview frames' or similar option in order to get 30 fps in videos. When you do that, try recording video under low light, and you'll see what I'm talking about. Stock AOSP camera works thousands times better in this regard.
[Galaxy S 4 i9505 Original Android Development] Accraze:
Will you add theme engine in the next update?
[Galaxy S 4 i9505 Original Android Development] osmar.menezes:
http://download.cyanogenmod.org/?device=jfltexx

http://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-nightlies-qcom-intl-t2999570
[Galaxy S 4 i9505 Original Android Development] s3icc0:
what is the point? this is custom build thread
[Galaxy S 4 i9505 Original Android Development] rascal0pl:
Hi, I have a question, is there any way to manual set (in terminal for example) mic sensitivity below 20 (in stweaks 20 is minimum).

I had S3 (i9300) and I was able to set mic sensitivity to 1 in boeffla app (and I had perfect sound in videos). It is very important to me, because when I recording our concerts in loud environment, there are serious sound distortions :(

[MENTION=5464206]AntaresOne[/MENTION] [MENTION=2199706]Alucard24[/MENTION]
[Galaxy S 4 i9505 Original Android Development] s3icc0:
you will have to use terminal each time you would like to change the value (and also not to forget to recovery the last kernel profile from stweaks or change it back using terminal).

the vcalues you would like to change are following:

General mic gain

/sys/kernel/sound_control/gpl_mic_gain

Camera mic gain

/sys/kernel/sound_control/gpl_cam_mic_gain

Headset mic gain

/sys/kernel/sound_control/gpl_headset_mic_gain

use this formula in terminal emulator to change (example for value of 1):

su
echo 1 >/sys/kernel/sound_control/gpl_mic_gain

etc... for any value you need to change

not sure if the minimal level can be dangerous but rather dont go over the maximum given by stweaks - you would risk serious damage to you microphone or audio circuits

I know this maybe belongs more to the kernel thread, but anyway if you found a limit in STweaks and you want to try more/less (remember it may be very dangerous for the phone) you can find your value path like this:
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
[MENTION=5464206]AntaresOne[/MENTION] Can we have the separate volume controls show when using the volume rocker buttons? I can see that it has been added to the official ROM in the last update. Really good work on this Rom and looking forward to the next update.
[Galaxy S 4 i9505 Original Android Development] vagaBond07:
This ROM is amazing! Tons of feature, good as daily driver and smooth as butter!
[Galaxy S 4 i9505 Original Android Development] brunodu91:
[MENTION=367519]antares[/MENTION]

I love this rom, it's better than official for me, because, more stable and more advanced than cm12 official.

Could you integrated the settings option for clock status bar position?

Thx in advance
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I've put a small fix here for my theme... Say me if it's better!
[Galaxy S 4 i9505 Original Android Development] NZgeek:
If you're cone from another ROM, you need to make sure you've done a complete wipe. This means that you have to wipe /system, /cache and /data. It's safe to leave your internal storage (/data/media) as it is.

When you've done that, flash the ROM and GApps.

Warning: wiping /data will remove all of your apps and settings.

The general rule is that if you're switching between ROMs, you need to do this full wipe. If you're upgrading to a newer build of the same ROM then you can do a dirty flash. When you're on the new ROM, if you're using something like Titanium Backup to restore your apps and data, only restore user apps and their data. Do not restore any system apps or system data!
[Galaxy S 4 i9505 Original Android Development] Magnusmarshall:
Very smooth rom.

Works perfectly so far with the exception of the distortion when speaker volume high.

Not a huge fan of the lollipop white background but that's cosmetic and easily gotten around.
[Galaxy S 4 i9505 Original Android Development] matraca:
Fantastic ROM,super smooth

Bugs so far: Bluetooth not connecting, unable to send MMS, hold back to kill not working. Keep up the good work :)

Edit: hold back to kill is working but even in the shortest touch and hold delay it takes a good 3 seconds
[Galaxy S 4 i9505 Original Android Development] fjuniper:
I accidentally dirty flashed this ROM over a CM11 nightly (meant to full wipe but forgot) and it works pretty well! I have noticed a couple of spontaneous reboots (not complaining - I should have wiped) but have been happily using it since Friday. Battery life hasn't been great but wifi and bluetooth work fine - will do a full wipe and install as soon as the next Optimised build is available. Waiting patiently ...
[Galaxy S 4 i9505 Original Android Development] benjamen50:
I'm quite surprised that you managed to dirty flash over a CM11 build without issues, I couldn't get mine to boot.
[Galaxy S 4 i9505 Original Android Development] clshores:
As a Sprint jfltespr owner I would just like to have an official build to install. I am super happy with this version for sure but would love to try out vanilla CM12 in an official form. There is a euroskank CM12 for jfltespr which is as good as it gets right now and is updated every few days..
[Galaxy S 4 i9505 Original Android Development] NingaR:
Long Time no See Sir. [MENTION=5464206]AntaresOne[/MENTION]
[Galaxy S 4 i9505 Original Android Development] fjuniper:
Not as surprised as me! I was expecting to be reverting to the backup I had just taken.
[Galaxy S 4 i9505 Original Android Development] FeWoR:
Screen colors correction

Hello,

it seems that nobody wrote about the great screen colors correction feature on GPU tab of Stweaks.

Finally no more a warm-white screen!!!

I just played with settings and it seems that setting red tint to 46 it's quite ok.

Bye,

FeW
[Galaxy S 4 i9505 Original Android Development] Magnusmarshall:
Is it just me or are the battery calculations way off when you install the rom?

Two hours left at 87 percent when you basically doing nothing seem and power drain seemed awfully fast for checking setting..no phone calls no videos or games.

In 20 min to loose 13 percent seem a little off at that type of usage.
[Galaxy S 4 i9505 Original Android Development] Kushan02:
did you clean flash if yes then your battery might need a calibration download a so called battery calibration from the market charge your phone till 100% them open calibration app and click calibrate and remember you should be rooted then remove the charger and use the phone till it shutdowns automatically so battery is almost 0% ( dont overuse your phone to shut it down use it normally as you would ) then connect your charger let the phone boot and dont use your phone till its charged to 100%.

This process will recalibrate the battery.

Hope this helps.

Hit thanks if it helped.
[Galaxy S 4 i9505 Original Android Development] munichsfinest:
It will get back to normal after 1 or 2 battery cycles, as usual. Forget battery calibration and other myths [emoji6] it just deletes your battery stats.
[Galaxy S 4 i9505 Original Android Development] mulletcutter:
Battery calibration app? Why not just delete batterystats.bin. cuz it does nothing. Does nothing for your battery. Why do people still tell people this? Bet you use a task killer.
[Galaxy S 4 i9505 Original Android Development] r_t_f_m:
Dirty flashing CM12 NIGHTLY

I've flashed cm-12-20150121-NIGHTLY-jfltexx.zip , no issue.

Flashing back (dirty) with this ROM (11/1/2015) will result in no boot.

Re-flashing again with cm-12-20150121-NIGHTLY-jfltexx.zip will work but you'll

be stuck with official nightly , for now at least, or you'll have to do a clean flash.

On both ROMs , camera is freezing if you start using front camera.
[Galaxy S 4 i9505 Original Android Development] gkkovacs:
Issues with 11/01 release (disabled NuPlayer):

- Proximity sensor during calls is not working (Play store app Proximity Fix does help for some time, then problem appears again)

- Camera is unstable (using Camera FV-5 which is much better, but sometimes even that app can't connect to camera)

- Call volumes are way too high

- Never seen LTE work (anyone ever used it under CM12 ?)

- Bluetooth is somewhat unstable

Some Stweaks advice for fellow ROM users:

- I have undervolted the CPU, lowest freq to 0.800, all others -0.075, it helps tremendously with battery life

- I have undervolted the GPU, -50000 for all freqs, less heat and better battery life

- Alucard governor with alucard hotplug driver is great for performance and battery (tested some others, no need to change)

- I have changed the OOM memory management level to low (screen on) and low (screen off), helps with Lollipop app kills

- Decreased swappiness to 20, dirty ratio to 25 and 20 (background)

I am looking forward to testing a new build - will we see weekly builds [MENTION=5464206]AntaresOne[/MENTION] or what is the plan?
[Galaxy S 4 i9505 Original Android Development] Heke120:
I can confirm all of them:good:
[Galaxy S 4 i9505 Original Android Development] andreiav:
I don't have any of the problems you mentioned. Everything working great for me. :confused:

And yes, I have LTE. Although sometimes it's not as quick to switch from H+ to LTE as KitKat was, I still have stable LTE.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
- I don't feel problems with proximity sensor - will pay more attention to that

- Camera's unstable - YES

- Call volumes - for me are OK, but I have irregular issues when changing volume - it seems like the phone thinks is in different state and is changing wrong volume (BT / Media / Ring / In-Call ... )

- LTE works OK (had a chance to test 800/900 and 2600 MHz networks - all fine)

- BT for me in my car is OK - sometimes it has problem to reconnect when I turn it off after leaving my car and going back - then I have to reboot. If I left it active I have no problems.

STweaks

- I am not a fan of undervolting, but will check your levels and see if I have similar feeling

- Alucard governor + hotplug is a MUST

- I stopped tweaking RAM time ago, but will try your settings, it makes sence as the system for me is usually max 400MB :)
[Galaxy S 4 i9505 Original Android Development] kofe:
1. Proximity sensor never failed me on CM12. Maybe it's a hardware issue. Try cleaning the sensor. Search a lil bit on xda, it's been written how to.

2. I am using snap camera and i've never had the can't connect camera error

3. See screenshot

4. What do u mean? I've only used it with my car, and it's working fine so far.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
The camera issues are not only connected with the problem you mentioned (I never had it on CM212 as well), but if you are using it too much you will see it takes time to focus and after certain number of pictures it stop working so best way is to remove camera from memory and start over - which takes time and the ability to take quick pictures is gone - then for me it is better to take my DSLR camera ...
[Galaxy S 4 i9505 Original Android Development] darkvoid_66:
There as been a lots of bugs fixed in the official fltexx nightlies.

Especial after cm-12-20150118-NIGHTLY-jfltexx.zip where some CM crash bugs were fixed.

Will this ROM be re-based on those soon?
[Galaxy S 4 i9505 Original Android Development] ahoslc:
Been really quiet I see the dev has not touched hit GIt Hub in a week or 2 everything ok?
[Galaxy S 4 i9505 Original Android Development] knuckles1978:
I might actually try the official build, and just come back to this one once Antares has had the chance to build a new ROM. Maybe he's busy with CM Official. He's the maintainer for official now isn't he..

2 weeks is quite a long time in nightlies, but having said that, there's not much at all wrong with this ROM. It's absolutely daily driver material. I'd need to check if the dark theme would be usable on the official, because that'd be a deal breaker for me, even as a short term solution.

Hmm, I'm not quite sure what to do. [emoji46] hehe
[Galaxy S 4 i9505 Original Android Development] Magnusmarshall:
Two weeks may be a long time for nighties but in terms of our daily life's its minimal.

Also the rom quite solid as is so we are not really hurting waiting for a major bug fix.

Now that said what would be the expected battery use just listing to music for a hour and a half.

Nothing else including wifi or blurtooth used during this time.

Beginning to expect my battery on the way out or a got a bad flash.
[Galaxy S 4 i9505 Original Android Development] TLK3:
I'm guessing AntaresOne has been more focused on CM12 since he's the official maintainer. Releases were fairly consistent until then.

I'd switch over if CM12 had F2FS support. Converting everything back to ext4 is such a pain, especially with my 64GB external SD. But at this point I'm seriously considering it. Bluetooth and memory issues are driving me insane.
[Galaxy S 4 i9505 Original Android Development] archerymodz:
F2fs has started to make some appearances in the official change logs.
[Galaxy S 4 i9505 Original Android Development] TLK3:
After searching around on Google I found an article that says F2FS works as long as /cache is not formatted using it. Don't know how accurate that information is, but I'm going to give it a shot. Finally finished mirroring my external SD with GoodSync (love that app) in case I decide to jump back to ext4. I'll post results if F2FS works.
[Galaxy S 4 i9505 Original Android Development] planetf1:
It will be interesting to see a comparison between this optimised build and current nighties.

I'm guessing this one here may be a little bit more stable to begin with, in part due to the citations kernel, and also cherry picking.. But longer term official may be the way to go.

Not switching yet but interesting to watch and great to have the choice. Official cm12 is great to pull in more users
[Galaxy S 4 i9505 Original Android Development] killed2:
I formatted the Cache from f2fs to Ext4 and installed the Nightly after a Full Wipe. CM did boot but told that the encryption did fail. I never used that feature, so i think it was a read error.
[Galaxy S 4 i9505 Original Android Development] ben.ormrod.90:
Was it useable
[Galaxy S 4 i9505 Original Android Development] killed2:
No, absolutely not. FC's all the time, it was hard to reboot the phone.
[Galaxy S 4 i9505 Original Android Development] iyahman:
Deleted
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
Just curious. Can your computer read the f2fs now on your 64?
[Galaxy S 4 i9505 Original Android Development] TLK3:
Same issue. It does read my external SD which is f2fs, so at least I don't have to convert that.

---------- Post added at 12:46 AM ---------- Previous post was at 12:43 AM ----------

Yeah, through USB. If no ROM installed I just boot into recovery and mount the card. Not the greatest option but it works for what I need.
[Galaxy S 4 i9505 Original Android Development] giorgiosandros:
- noticed lockscreen not responding after a few hours of usage.

I really hope [MENTION=5464206]AntaresOne[/MENTION] continues this project!

This is the best lollipop ROM atm, battery running all day :victory:
[Galaxy S 4 i9505 Original Android Development] s3icc0:
lockscreen reaponding after .... all the time

check your apps
[Galaxy S 4 i9505 Original Android Development] giorgiosandros:
.. Was not sharing it ... for fun. :)

Always full wipe, and have no crazy lockscreen apps.

Alucard kernel.
[Galaxy S 4 i9505 Original Android Development] iyahman:
if someone want i share with you a fresh compiled pure cm12 with f2fs support on /data and /cache.

no need to have custom kernel.

so you need to have

/system ext4

/data f2fs

/cache f2fs

https://drive.google.com/folderview?id=0B982P6f27W6oOHdyRTlDdWxac00&usp=sharing
[Galaxy S 4 i9505 Original Android Development] Heke120:
+1

Is it too much to ask to make /system f2fs too?
[Galaxy S 4 i9505 Original Android Development] TheMattMercy:
In addition to my front camera not working (still an issue, even though my post in this thread was deleted), Google Music and ViperFX keep crashing - the music will continue to play, but it's just annoying to get popups all the time. Also, the bluetooth connection will sometimes disconnect, and sometimes "Bluetooth share" will quit working. I didn't have those issues until this ROM.
[Galaxy S 4 i9505 Original Android Development] LuigiC6:
May want to do a fresh install. No issues with front camera, play music or bluetooth here.
[Galaxy S 4 i9505 Original Android Development] TheMattMercy:
Tried that, fixed nothing. I can't seem to recreate the Bluetooth or music issue atm, but it happens at my job so I'll be sure to upload a logcat then.

In the meantime, here is my logcat for the camera issue... I suspect it might have something to do with drivers/modems/bootloaders and this ROM being incompatible, but I know hardly anything about that... and no-one wants to help me in the general help thread...
[Galaxy S 4 i9505 Original Android Development] woooson:
Bluetooth share fcing is common but it works fine just annoying
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Exactly DSA...

I'm back guys, just not in the mood to develop from the last two weeks but there are things that I must do without losing time

I'm building an update, I will try to keep at least 1 (or even 2) build/week since there's another project under development, my own apps for Android, and bad things with my personal life that make me very sad... :(

I'm very sorry for the absence on XDA/Hangouts