yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] hospital349:
I PM'd Synergy via the codefireX website regarding the rasbean/mofic commits and his response was:

"For the most part I've been ignoring xda and focusing on these forums (though I've been busy the past few days with real life). We have all optimization commits that raspbean jelly have in their dalvik, and then some since we're quite a ways ahead (release vs master).

Mainly been focusing on finding and fixing the app permissions issue before focusing on everything else. I do however have a few WIP projects for performance that are working out quite well, such as a repo that adds compatibility symbols to prebuilts to allow booting with my gcc 4.8 toolchain (running on a few test devices already)."

This'll be worth the wait for sure. :)
[Nexus 4 Original Android Development] hospital349:
Multi-user Support was just added, according to the latest Bitbucket commits. Great news! :good:
[Nexus 4 Original Android Development] Godaemon:
Meaning ? Ty

Via NeXuS 4 / xda-developers app
[Nexus 4 Original Android Development] gagdude:
You will have multi user support in the next build :p
[Nexus 4 Original Android Development] the1onewolf:
Evenly/Equally Tattered Asses/***H*l*s
[Nexus 4 Original Android Development] fairyshacker:
yeah !! ask when S20 will be out :P
[Nexus 4 Original Android Development] offenberg:
My body is ready.
[Nexus 4 Original Android Development] ultma75:
Update from the codefirex website.

"The project is not dead for those wondering. We have been working on review.codefirex.com/T1 . If anyone has ideas pertaining to this issue, please let us know. Thank you."
[Nexus 4 Original Android Development] :
HOLY ****! I read "this project is now dead" at first. My heart skipped a beat or two.
[Nexus 4 Original Android Development] gagdude:
lol so did I
[Nexus 4 Original Android Development] met4ller:
I' m not accusing nobody, simply IMHO .

I can't wait more than 1 month for a working update (after 4 bad updates), so in few days I must change ROM (also due to some lag never saw first, probably for the time that i have this rom installed).

I would found another slim (always with lockscreen rings) and fast with long battery autonomy: which i should choose?

thx
[Nexus 4 Original Android Development] Artius89:
Give a shot to liquismooth. I'm using it waiting for the next update of codefire.
[Nexus 4 Original Android Development] hospital349:
You'll be back. They always come back. :)
[Nexus 4 Original Android Development] met4ller:
sorry, I'm different from normal ROM users, I don' t like to flash every month a rom... Firstful for every setting that I must re-apply ( I'm sad that Titanium can only save 2-3 settings like WPA passwords, and not every settings).

I prefer to stay on the best one.. and for me this is the rom who has updates and, as written first, stability and long battery use.

Oviously, if a rom start to lag, i try to do wipe cache and dalvik cache (as yesterday with this one), but in the past I discovered that the usage of a ROM , with time it forcely slow (for a lot of reasons), and also I can' t wait some improovements - above all I haven' t an old phone, but the "best/fresh" now. :cool:
[Nexus 4 Original Android Development] tgtoys:
Just use SR15, it works perfect with no issues.
[Nexus 4 Original Android Development] eep2378:
Except for nav bar settings resetting and some root inconsistencies ;):D

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] kptnk:
Yes the wait seems long for us who love CFX.....but i really do not agree with your statement "after 4 bad updates..." ; some issues remain, yes, but others have been sorted out, and the Rom improved on others aspects.

Anyway, you have plenty of choices...
[Nexus 4 Original Android Development] met4ller:
I already use sr15 and it's well, I was talking about updates.

sr15 was my first, wonderful rom for n4. but i can't write "the best one", cause i didn't try another roms. I am simply bored about watching this thread without concrete news on the stable one.

I wrote "bad" cause I red a lot of bad opinions on those sr in my italian big forum on android,even though all improovements that were made...:good:
[Nexus 4 Original Android Development] hospital349:
Rome wasn't built overnight.

Masterpieces aren't built in a day.

SR20 isn't built in a month, though I'm sure it'll be worth the wait.

If you're bored, go flash another ROM and come back when the release is ready. The 'concrete information' is technically there for you to read. Just visit their Bitbucket. Team codefireX have made hundreds, upon hundreds of commits over the last month and if you take the time to browse through them, you'll see that they're hard at work, perfecting greatness.

I'd rather experience an epic ROM release with numerous improvements, fixes and optimizations, than something that isn't going to make much of an impact on the ROM community. I believe that's why they're making us wait. I believe that the next release is going to be lightyears ahead of other ROMs in regards to performance and optimizations.

Not forgetting AOSP OpenMaster, which technically means that when Google release KLP (Android 5.0), the team won't need to rebase/redo the ROM. So whilst other devs are busy trying to fix their ROMs to make them work with 5.0, TeamcfX will be drinking whisky and smoking cigars. :cowboy:

I really believe that they've made the right choice in making this huge commitment, as it'll will pay off in the long run. :good:
[Nexus 4 Original Android Development] kptnk:
FYI CFX are not alone to fight the issues encountered by merging Open Master : Team Vanir have as well recently merged, and they are currently facing the exact same issu than CFX with Su.

So we can assume they'll help each others, as they are great devs. It is as well reasonable to think Koush will reply to them and help by making Su "accept" this new branch.....

Anyway, better wait for the best than everyday flashfest ! :)
[Nexus 4 Original Android Development] hospital349:
Looks as if cfX will be accompanied with a newly built Kernel.

"forked from https://bitbucket.org/rlasalle15/gee_mako. Based on faux123's mako kernel with 3.4.y lk merged in and aosp kernel/common android-3.4 merged in. A project between rlasalle15 and synergydev.
[Nexus 4 Original Android Development] :
Are other kernels not going to work?
[Nexus 4 Original Android Development] Vangelis13:
What makes you say that?? Other than the latest cm thing, all kernels work on all roms on the n4.
[Nexus 4 Original Android Development] hospital349:
All kernels will work with future releases. The team just built a kernel to cater specifically for their needs. You'll always be able to flash a new Kernel over it, if you want to switch.
[Nexus 4 Original Android Development] Smallsmx3:
Been thinking about trying this rom...... I see there are bugs.... Anything major with sr 19
[Nexus 4 Original Android Development] hospital349:
Yeah, bugs are crawling in SR19. Try SR15, it's fast and rockstable. :)
[Nexus 4 Original Android Development] Smallsmx3:
I guess ill wait until 20 drops
[Nexus 4 Original Android Development] _frog hair:
Trying to be om topic here..Lol. Is there a way to make titanium backup work with this ROM. I did a full wipe before install. Seems like the right permissions are needed some how.. Cant figure it out?

Edited due to bad spelling.

Sent from the stars using a paranoid old Nexus 4.
[Nexus 4 Original Android Development] hospital349:
SR19 has issues regarding Security Settings & SU Permissions, (as I recall). Titanium Backup works with SR15.
[Nexus 4 Original Android Development] ChongoDroid:
You can create a flashable backup zip and flash it in recovery after your first boot.

Only workaround I found for restoring apps with tibu.

Sent from my Nexus 4
[Nexus 4 Original Android Development] _frog hair:
Oh yeah.. Didnt think of that cheers mate.. So guys -sr15 is the choice untill sr20 drops?

Sent from the stars using a paranoid old Nexus 4.
[Nexus 4 Original Android Development] Smallsmx3:
Where can i find 15? All i can find is 17 and 19
[Nexus 4 Original Android Development] offenberg:
http://downloads.codefi.re/synergy/codefireX-Mako/
[Nexus 4 Original Android Development] Smallsmx3:
Found it
[Nexus 4 Original Android Development] offenberg:
Good for you :) SR15 is my daily. I'm sure you won't be disappointed.
[Nexus 4 Original Android Development] Smallsmx3:
Stock kernel? And is this a CM based rom?
[Nexus 4 Original Android Development] hospital349:
Nope. It's an AOSP ROM. Well, I always thought that it was... with AOSP OpenMaster and all?

Can somebody clarify this? :silly:
[Nexus 4 Original Android Development] offenberg:
Its build from custom aosp source.
[Nexus 4 Original Android Development] jarjar124:
Does sr15 have the recent app lag?
[Nexus 4 Original Android Development] Smallsmx3:
OK... trying it out for today.... Came from rasbean so far so good.
[Nexus 4 Original Android Development] offenberg:
No.
[Nexus 4 Original Android Development] Smallsmx3:
Any idea how to stop long press on the home key to go to default instead of going to recents menu
[Nexus 4 Original Android Development] offenberg:
You can change long press action in cfx settings. But not to launch the Navigation ring
[Nexus 4 Original Android Development] Smallsmx3:
I did that long press is set to empty
[Nexus 4 Original Android Development] folkg:
I just set my long press to go home.
[Nexus 4 Original Android Development] tgtoys:
In the changelog, SR19 points out that "Bluetooth is really fixed"...what was fixed exactly? Is this referring to the 4.2 bug? I have a MetaWatch and still have many, many problems with bluetooth, wondering if that should theoretically be fixed with SR19+? Any more info/details would be great.
[Nexus 4 Original Android Development] hospital349:
Bluetooth was broken, caused by most recent developments, when the cfX development team began working on the OpenMaster project. It was fixed in the most recent built. However, I wouldn't thoroughly recommend using it, as SR19 has a few bugs that will be solved in the up-and-coming release.

For now, I would recommend flashing SR15. It's completely functional without bugs, (as it's a pre-OpenMaster release). It's totally stable and I'm sure you'll enjoy it. :good:
[Nexus 4 Original Android Development] Adnan008:
omfg 4.2.2.2.2.2.2.2.2.2.2 (not a typo) what the hell is that :silly:
[Nexus 4 Original Android Development] hospital349:
This explains it. :)
[Nexus 4 Original Android Development] :
Not true from what I recall. Didn°t sr15 have the navbar bug already?
[Nexus 4 Original Android Development] hospital349:
I'm not experiencing any NavBar issues in the slightest. I'm currently using SR15. :)
[Nexus 4 Original Android Development] rlaw:
You wouldn't notice if you leave navbar size at stock.
[Nexus 4 Original Android Development] hospital349:
Ahh, that'll be what that is then. :cyclops:

Cheers for clearing things up, corndude & rlaw. :good:
[Nexus 4 Original Android Development] tgtoys:
Thanks. I've been running SR15 for weeks and love it, just wanted to clarify if the Bluetooth fix was regarding the android bug or an sfx bug.
[Nexus 4 Original Android Development] hsrn:
the next rom i flash will be this one.

but i wait for the next release to show up.

and i hope it will be built with 4.8.0 toolchain.
[Nexus 4 Original Android Development] Smallsmx3:
Why? Do our phones transform into little robots? I notice no huge real world improvements between the tool chains. I also don't ever benchmark any of the roms i flash. I'm not going to lie sr15 is really fluid as it stands.
[Nexus 4 Original Android Development] Logi_Ca1:
They are just going nuts over Sabermod which is the first to use 4.8. From what I heard it's blazing fast. I will see for myself later.
[Nexus 4 Original Android Development] :
**** there really are roms that use 4.8?
[Nexus 4 Original Android Development] ctfrommn:
Only Sabermod AFAIK
[Nexus 4 Original Android Development] Logi_Ca1:
Sure. This one:

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

If you have been going to the trinity thread that's all they talk about nowadays :p
[Nexus 4 Original Android Development] :
Sorry I'm not quite up to date here. Why do they talk about it in trinity if the only kernel that has it is the one that comes with sabremod?

edit: I don't know what sabremod you guys are talking about but the one that i just loaded (rc3) is running 3.4.
[Nexus 4 Original Android Development] Logi_Ca1:
Have you been to the Trinity thread? Half the talk there is off topic. I'm not judging btw. That's the atmosphere that the topic creator wants. :p
[Nexus 4 Original Android Development] ctfrommn:
Cause we talk about all things Android and all things interesting over there :D
[Nexus 4 Original Android Development] Vangelis13:
Right now we're analysing the Chechnyans btw.
[Nexus 4 Original Android Development] hospital349:
For those who are interested, Synergy merged Linaro GCC 4.8 toolchain about a week ago. Check HERE for more details. :)
[Nexus 4 Original Android Development] nivlac978:
I've been on sr15 longer than any other rom I've ever used, ever. But my flashing finger is getting itchy.
[Nexus 4 Original Android Development] Smallsmx3:
Su issues is what's holding up sr20?
[Nexus 4 Original Android Development] ultma75:
Yes, syngery might have found a perm workaround but they are still implementating it and test. Might work or not will keep y'all updated
[Nexus 4 Original Android Development] Smallsmx3:
Sweet that's exciting to hear.. Thanks for the update
[Nexus 4 Original Android Development] pawan1993:
The kernel in SabreMod is still compiled using the 4.7 toolchain. By the way I think what you're talking about being 3.4 is the Linux kernel version. All ROM's use 3.4 right now as Google haven't merged anything newer yet which we'll probably see in Key Lime Pie. The toolchain is what they use to compile their stuff with.
[Nexus 4 Original Android Development] Smallsmx3:
Any exciting news this week
[Nexus 4 Original Android Development] kptnk:
Is it a question or an affirmation ?
[Nexus 4 Original Android Development] Smallsmx3:
Maybe both. Just no movement in this thread is all. I think i came late to the party and waiting for the next release.
[Nexus 4 Original Android Development] :
Yeah, would be cool to actually here how things are looking out right now...
[Nexus 4 Original Android Development] met4ller:
Hi guys, at the end i m still with this rom :)

But now i must change for a reason : slimport doesn t work!! :(

Any SURE developement on this rom in the near future?!?

Maybe with sr20?! If yes, i ll wait till this coming out (If it Will not takes 2other months !!!!!! ;) :D

Inviato dal mio missile N4
[Nexus 4 Original Android Development] hospital349:
I noticed a whole bunch of commits, labeled: "Revert to partial release state", under numerous repositories. I don't want to jump the gun, but I believe this is a positive indication that the team are readying a release.

Let us prey. :D
[Nexus 4 Original Android Development] offenberg:
My body is so ready
[Nexus 4 Original Android Development] ilamaan:
Is there an option to change DPI per app in this ROM?

Thanks!
[Nexus 4 Original Android Development] :
Not that I know of.
[Nexus 4 Original Android Development] Smallsmx3:
I thought when patches are reverted it means they are causing issues?
[Nexus 4 Original Android Development] hospital349:
I don't think that's the case for every situation. Check out their Bitbucket for yourself: https://bitbucket.org/codefirex

I think they may've removed/changed sections of their repositories for development purposes and now they're beginning to push the original sources back in. Commits haven't stopped all morning. They just keep coming. It's definitely a good sign, though as I mentioned in my previous post, 'I don't want to jump the gun, but...' :good:
[Nexus 4 Original Android Development] Smallsmx3:
Yeah i don't know what any of that means. I see a new build and i flash it. :) but it's good that there is a lot of work being done.

I flashed sr 19 3 days ago and have not had any issues. Had an fc or two but all seems stable
[Nexus 4 Original Android Development] ultma75:
Syngery and the team were reviewing commits all night, possible release soon but they are also moving host from bit bucket to another gerrit host.
[Nexus 4 Original Android Development] tlongren:
I thought bitbucket was git and mercurial. Irrelevant to this thread really. Do you know where they're moving the code to? I'd love to see them on Github, as that's where I spend most of my time.
[Nexus 4 Original Android Development] ultma75:
He said he is moving it slowly away from bit bucket and its self hosted.

Accidentally thanked you lol
[Nexus 4 Original Android Development] tlongren:
Accidentally, right. But my post was so helpful. :D I "accidentally" thanked you too. Am interested to see what kind of web interface their new self-hosted version control system will have (if any).
[Nexus 4 Original Android Development] kptnk:
It seems all these reverted commits were mainly caused by the persistent SU Permissions issue :

Synergy : "For now I'm moving back all the main repos back to be somewhat release based while still using master icu, master/caf webkit chromium v8, and some libcore/dalvik master changes. I'm going to hold onto these in separate branches to work on however."

Go there to see discussion about this problem between Synergy and DHO (Team Vanir dev who's facing the same issue with SU after haveing merged with Matser too) :

http://review.codefirex.com/T1

So, it is safe to think there will be soon a release, but without main Master merges, or with a SU workaround...let's wait :)
[Nexus 4 Original Android Development] ultma75:
From what I've read I think they are going to do a 4.2.2-r1.2 build with a new kernel but I believe without master merge.
[Nexus 4 Original Android Development] hospital349:
I just browsed the conversations on Phabricator regarding the latest reverts. I respect Synergy's decision to push a working release and then work on the remaining issues, separate from SR20. It's impressive that the team has taken the project as far as they have. I'm sure that they'll have OpenMaster all figured out in due time, though it must be a tedious ballache trying to iron out the remaining bugs. Especially because they've been at the same issue for weeks on end. It's definitely no easy task. I'm no developer, but I understand that much.

Psyc'd for the new release, whenever it appears. It's going to be tits! :D
[Nexus 4 Original Android Development] Connor Baker:
The teats indeed.
[Nexus 4 Original Android Development] Smallsmx3:
Sweet. Not really stoked about custom kernel though. I like the stock with color tweaks
[Nexus 4 Original Android Development] Connor Baker:
I've been running nightly builds I compiled, and I think that the color is really good.
[Nexus 4 Original Android Development] ctfrommn:
Will that kernel work on regular 4.2.2 Roms? If so, care to share it?
[Nexus 4 Original Android Development] Smallsmx3:
Nightly? Wanna share :eek:

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

Nightly? Want to share? I'm sure I'm not the only one interested
[Nexus 4 Original Android Development] Connor Baker:
Ok. Here's the thing. Recently, some changes were made to the kernel causing the Mako to not boot. So, the only working build I have is from 4/19/13. I'm not going to post it, as that would be rude. If you want it (the build, I am not going to repackage the kernel right now), PM me.

Connor Baker
[Nexus 4 Original Android Development] kptnk:
That makes me very curious and wondering :

Post 358

http://xdaforums.com/showthread.php?t=2043095&page=36

Coming from the lead dev of Team Eos....:confused:.....

OK that's for the N7, but if things change for CFX there, it will definitly here too i guess....Maybe that's a mutual poject EOS/CFX....

Or, i'm not Sherlok Holmes, and I'm all wrong....:p
[Nexus 4 Original Android Development] ultma75:
Well bigrushdog said he was bored of EoS

So he joined cfx now
[Nexus 4 Original Android Development] kptnk:
Ok then, bad for Eos, good for Cfx....
[Nexus 4 Original Android Development] Jackones:
There's a new nightly out, but still Security-FC...:p
[Nexus 4 Original Android Development] OCmylife:
He`s missing the keymasterfiles. The same error happend in trailblazers build, but not in tuckleberries build or when I self compiled CM10.1.
[Nexus 4 Original Android Development] offenberg:
Thanks. It works.
[Nexus 4 Original Android Development] Smallsmx3:
So this needs to be flashed after the nightly?
[Nexus 4 Original Android Development] offenberg:
You need to push them to vendor/firmware
[Nexus 4 Original Android Development] copi:
hi guys

does in the latest nightly has nx gesture feature from team eos? considering the join of bigrushdog to codeX team.. thank u
[Nexus 4 Original Android Development] Jackones:
Could someone create a flashable zip. I'm on my phone right now so i can't push them via adb

Thanks a lot!
[Nexus 4 Original Android Development] ctfrommn:
That would explain why when using the kernel my battery drained from 100-0 in 6 hrs and stating keystore as the reason.
[Nexus 4 Original Android Development] offenberg:
I used a file explorer. Root explorer to be exact.

Facebook doesn't load. Anyone?
[Nexus 4 Original Android Development] ceejay83:
So latest nightly is still buggy?
[Nexus 4 Original Android Development] offenberg:
I restored my backup. But Facebook was my only issue.
[Nexus 4 Original Android Development] Smallsmx3:
Yeah FB it's messed. Ill wait till the next sR
[Nexus 4 Original Android Development] hol17:
Facebook application or webpage?
[Nexus 4 Original Android Development] Smallsmx3:
App
[Nexus 4 Original Android Development] hospital349:
How's the new nightly folks? - I've been away for the day, so I'm unable to flash right away, though I'm intrigued. Are there noticeable differences? Bugs to report? (Apart from the Facebook one, of course.)
[Nexus 4 Original Android Development] ceejay83:
Wasn't on it long enough only played around with the settings. Seems like there aren't any new features compared to sr15. Also it's not compatible with xlouder mod, kept getting hot reboots
[Nexus 4 Original Android Development] offenberg:
Restored my SR15. I didn't notice anything new or different in the nightly. Only that its not stable for daily.
[Nexus 4 Original Android Development] try2:
I think that answers what questions I had too. Thanks for the heads up.
[Nexus 4 Original Android Development] imzkng:
ROM runs well after adding the keymaster files. One problem, Google Play Music force closes when launched.
[Nexus 4 Original Android Development] synergye:
fixed the security settings fc for good now. That upload was actually also accidental, lol. Ran the wrong script when I went to do a personal build (cron jobs and scripts are how the nightlies usually get done). Sorry about that guys...but at least you know that progress is being made ;). SELInux was being such a ***** that we went back to partial release repos with a lot of master parts with progress we made while working off master. Actually just did a build with the best performance we've had in a build yet.

A release will come soon, just need to make sure that it will give the SR prefix it's true meaning back - Everything's even going through review now. Also holding off on nightlies (and accidental script execution) until the stable release. We also have a few new guys contributing to cfx who are doing killer jobs and working their asses off as well :)
[Nexus 4 Original Android Development] hdorius:
sorry wrong thread
[Nexus 4 Original Android Development] ceejay83:
You really gotta quote it? We can clearly see it
[Nexus 4 Original Android Development] hdorius:
Sorry,wrong thread...lol..I want to post in Desire Hd forum,I'm drunk maybe...:banghead:
[Nexus 4 Original Android Development] :
Omg this is awesome. Finally some news. Feel like a child on christmas. <3 you cfx guys
[Nexus 4 Original Android Development] JmPTaz09:
http://forums.derkernel.com/index.php/topic,47.0.html?PHPSESSID=859ca8c6568288938996a0aa2f5f8259
[Nexus 4 Original Android Development] vineet381:
Thank you, do I have to use cpu governor like set cpu with this?