yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] reas0n:
Important infos:

I was saying for a few times that I will pause, will build less often, but I didn't. But now I need to be confident. Working on it, and not only that, have eaten my life, also my grades in uni got poorer, I can't leave myself like that. Sorry. Now I get few exams soon and I'm out-of-date with studing. I need to get a life, take a rest, get up-to-date with school.. Then I hope I will come back again.

BUT, if someone wants to continue, improve Vivid, please go ahead, I'd appreciate it. Hope You won't get angry guys. Cheers. I'll leave that thread open, because as I said, I should come back.
[Nexus 5 Android Development] ekowanz:
Good luck with your study reas0n..
[Nexus 5 Android Development] big_bum:
96 hours of uptime, no problems. The phone feels a little sluggish in Chrome, but I hope I'll fix this issue by adding KSM in the kernel in the following days.
[Nexus 5 Android Development] Hormesis:
Working super well for me too, no problems with the latest build thus far.
[Nexus 5 Android Development] big_bum:
As I promised.

- includes KSM and it's tuned for battery life, while still delivering the performance it should

- 2 updates/fixes from CAF for cpu-boost driver

- one update for interactive governor

- cherry-picked the famous i2c@19.2Mhz commit, and also dropped some other things to 19.2MHz

- optimized readahead by doing byte-shifting operations

- enabled deferred resume for mmc core

- built with fstrict-aliasing (Will revert if [MENTION=3371513]reas0n[/MENTION] wants to have it reverted in the kernel too, not only in the ROM)

All these are cherry-picks. Enjoy and send me a dmesg/last_kmsg if there are any problems.

The kernel can be downloaded from my FTP, the filename is kernel breaks data connection, removed or from this post. (It's not a flashable zip so please don't try to flash it and complain afterwards. Just unzip the archive and flash the .img)

(PS: Tapatalk can't handle FTP links)

EDIT: See this post for a kernel that fixes data issues.
[Nexus 5 Android Development] pianistaPL:
Is this f2fs compatible?
[Nexus 5 Android Development] big_bum:
I think reas0n fixed f2fs a few versions ago, so it should work if it was working in the previous version of the ROM.
[Nexus 5 Android Development] ekowanz:
Can i use this for previous caf rom?
[Nexus 5 Android Development] big_bum:
Nope. It won't boot. If we switch branches again, I'll add the changes to that kernel too, but until then you can just it in AOSP only.
[Nexus 5 Android Development] dekefake:
[MENTION=3371513]reas0n[/MENTION] how did you do to add f2fs support for /data and /cache into your rom ? I'm building too, and i would like to bring that to my build.

Thanks
[Nexus 5 Android Development] reas0n:
Thanks mate for working on it. I'm studing high-level math crap, not a easy time..

Btw, I was curious so I moved to official CM CAF, and realised, that battery is significantly poorer here :confused: I think LTO actually does something
[Nexus 5 Android Development] big_bum:
Here in AOSP?

Can you test the latest kernel? I remember CAF had the i2c@19.2MHz, our kernel didn't had it until yesterday.
[Nexus 5 Android Development] Hormesis:
I've been testing the kernel since last night, and have run into one problem: my mobile data connection keeps dying. The strange thing is that my phone still says I'm connected to LTE, but nothing will load. A full reboot of the phone fixes this for about 10 seconds, and then it stops working again. WiFi remains unaffected.
[Nexus 5 Android Development] big_bum:
I noticed that too a few minutes ago.

Trying to fix it, give me ~20 minutes.

I guess it's fixed now.

[MENTION=5722049]Hormesis[/MENTION], try the attached kernel, or look in my FTP for the fixed one. (Filename is boot-Vivid-29_04_2014.img)

(It's not a flashable zip so please don't try to flash it and complain afterwards. Just unzip the archive and flash the .img)
[Nexus 5 Android Development] Hormesis:
I can confirm that this update fixes the data problem. :)
[Nexus 5 Android Development] reas0n:
My exams went pretty bad.. Also I will need to write one again, because I didn't pass... Things don't look good for now... Sorry.
[Nexus 5 Android Development] minhajlk:
Sorry to hear that and you don't need to apologies for anything, you did a great job bringing this ROM to us. You should concentrated on your studies and get through the paper again. We will wait till then and good luck with your studies and exam.
[Nexus 5 Android Development] big_bum:
Don't worry [MENTION=3371513]reas0n[/MENTION], you haven't been a real student until you haven't failed one exam. :P If you need some advice about college life, give me a PM.

Anyway, I will still continue to work on Vivid, but I don't have much time right now.

I'll be freer in June, but if you can tell me how to merge things from upstream and push them to the repo, then build the ROM, I'll gladly do it.

So, who wants to be my guineea pig? (changelog: https://github.com/VividROM/android...d38fab7798369fe09fcd70eb8a...VividROM:cm-12.1)

Not a flashable zip, unzip and flash the image with fastboot/Flashify/etc.
[Nexus 5 Android Development] marioemp2k7:
The kernel is good, but don't we also need to tinker with the rom so we can really benefit from the CAF audio upgrades?

Also, could you please re-add Fast Charge to the Vivid kernel?

Thanks a lot for all your efforts!
[Nexus 5 Android Development] big_bum:
I think you might be right about the ROM tinkering? You could use the audio libs from a CAF ROM and see if that works. I used a hack in Kitkat with my older kernel in which I used non-CAF libs since the kernel wasn't CAF. I guess you could copy the libs from a CAF ROM and replace non-CAF with CAF versions. (It's basically the same hack, only reverted, see the links for filenames, but don't use those libs since they are from AOSP KitKat).

I'll look into fast-charge option tomorrow, maybe.

EDIT: here you go, fastcharge from faux. Not a flashable zip.
[Nexus 5 Android Development] marioemp2k7:
I finally managed to extract the needed audio files from the latest hammerheadcaf system.new.dat. I copied the files, set 644 permissions and rebooted.

The CAF audio files are a little bigger but work fine so all's well :) .
[Nexus 5 Android Development] big_bum:
I've made a build with the repos synced on 12th May. Nothing else, just updates and fixes from upstream (CM).

I'll upload it somewhere if [MENTION=3371513]reas0n[/MENTION] is OK with this.
[Nexus 5 Android Development] reas0n:
I think I may come back soon, but before releasing anything I'll need to detect the bugs which existed.
[Nexus 5 Android Development] socioteq:
Build system is still good. let me know when you're ready , or if you're going with azure this time
[Nexus 5 Android Development] MikeFoxclaw:
So we're going back to CAF base?
[Nexus 5 Android Development] reas0n:
No Azure for me :(

Of course yes.
[Nexus 5 Android Development] Kagath:
Thanks reas0n i'm so happy because i think the CAF version is for me really the best :D

I can't wait for a new build !

Thank you for everything you've done and all that you will..

Do you think you're going to integrate the work you did on the AOSP version ?
[Nexus 5 Android Development] reas0n:
there shouldn't be any problems.
[Nexus 5 Android Development] socioteq:
Awe that sucks. I figured that would probably be the case though...Well anyway, I'll be plan B! Do you want to keep using Ubuntu 14.10 for now? or should I be upgrading to 15.04?

Also I'm almost done with my neonatal orientation, so It's probably good timing. This month has been ROUGH, I've been doing a lot of Excel work for my department and it has kept my computer pretty heavily in use. Can't wait to get started again :good::good:
[Nexus 5 Android Development] big_bum:
I can build on my machine, but I can't provide access to it. Building takes around 2-2.5 hours.

But the best way to build is with a VPS, I guess. Take a look at the offers from digitalocean.
[Nexus 5 Android Development] socioteq:
That's nice and all but we don't have consistent donors, so those costs would come directly out of our pockets. I can provide access to my octacore 4ghz for free, so without cloud servers that's probably the best bet. Any other ideas (that would require little to no cost) are welcome, but remember, WE PO NIGGA!!

Edit: we aren't broke, we are actually poor. Thank you for clarifying this for me [MENTION=4857170]big_bum[/MENTION] ... Somehow I feel more depressed about being poor though ;D
[Nexus 5 Android Development] big_bum:
We're not broke, we just can't afford 'things'.

EDIT: [MENTION=2484358]socioteq[/MENTION] at least we have each other. And a Nexus :victory: :laugh:
[Nexus 5 Android Development] socioteq:
A quick note to everyone interested: we'll be getting off of the ground and starting work on this project again in the near and immediate future. [MENTION=727550]reason[/MENTION] is finishing up his focus on his personal stuff, but we will hopefully have a team of 3 [MENTION=727550]reason[/MENTION], [MENTION=4857170]big_bum[/MENTION] and myself working together to make this the most optimized version of cm12.1 available for our device.

Any ideas on what can be done are always welcome, but as always remember that these changes will only come at the discretion of [MENTION=727550]reason[/MENTION].

Were all very excited to get started again

I hope you all have your game faces on!
[Nexus 5 Android Development] big_bum:
I already started to work on the CAF kernel a few days ago. (https://github.com/StefanescuCristian/hammerhead/commits/cm-caf)

I'll try to build with GCC 5.1.0 and see if something breaks (it shouldn't).

We also need to see if we stay with mpd or change to an in-kernel hotplugger. (I really like mpd, actually)
[Nexus 5 Android Development] socioteq:
Nice. Actually, from what [MENTION=727550]reason[/MENTION] has said before, he was interested in staying with MPDecision because it was better optimized for CAF. I haven't heard much from him, so I'm guessing he is just finishing up... but from what I remember him telling me, that was the reason he stayed with MPD in the last builds that we did.
[Nexus 5 Android Development] big_bum:
I actually think we have a stupid bug that only occurs when MPD is disabled. I need to test more, and I don't want to speak too soon, but it occured when I disabled MPD, so I guess we should stick with MPD.
[Nexus 5 Android Development] CommanderDuplex:
any news ? :)
[Nexus 5 Android Development] big_bum:
I haven't heard anything from reas0n from some time.

It's not the end of this project, don't worry.
[Nexus 5 Android Development] reas0n:
Yes, I'm still alive. ;) I have a session very soon, I have good marks again. I'll be free from July (I'll start working in IT firm, but that won't take a lot time I suppose), soooo I think I will come back and maybe add the support for Motorola Moto E too. The base will be CAF, of course.
[Nexus 5 Android Development] buru898:
:good:
[Nexus 5 Android Development] forresthopkinsa:
So is this ROM still working fine?
[Nexus 5 Android Development] reas0n:
sorry, but I have a work now and I don't have the time for continue this ROM..
[Nexus 5 Android Development] mchlbenner:
Should be closed then!
[Nexus 5 Android Development] matt4321:
Thread closed as per OP request.

Forum moderator,

Matt
[Nexus 5 Android Development] neobuddy89:
In his CAF builds, he uses Qualcomm's mpdecision.

Chaos kernel uses MSM Hotplug driver.

This driver has 80% logic designed by myfluxi.

Rest 20% is improvements done by me and [MENTION=2376110]dorimanx[/MENTION].
[Nexus 5 Android Development] reas0n:
Uploading done, enjoy and test the freaking F2FS :P

EDIT: whoooops! I think F2FS on system will still not work. We need permissive SELinux. I think I may have to release a flashable kernel like in OptiPop to do this.
[Nexus 5 Android Development] maddes1402:
Which is strange for me tbh. When I change hotplugging to mpdecision in synapse the phone becomes pretty laggy. I usually preferred mpdecision in the past because although I'm really pleased and impressed for all your custom solutions I had the best results in battery life and smoothness when I used the Qualcomm way [emoji15].

Regards, Matt
[Nexus 5 Android Development] neobuddy89:
Well, mpdecision of Cyanogenmod (AOSP and CAF) is different!!!

mpdecision of Stock ROMs provides boost of 5 seconds. This is required since CPU Boost driver is not present.

mpdecision of CM is without any boost.

You can increase CPU boost driver's input boost ms and check if that helps.
[Nexus 5 Android Development] maddes1402:
Thanks! Yes, I forgot about that! But it's really odd. I found out that when I uses mpdecision with your kernel and increase input boost the phone is all the time just running on one core.
[Nexus 5 Android Development] Pretoriano80:
Just my opinion here but F2FS on /system is an overkill because F2FS strong point is in Random Writing (/system is not mounted in R/W) so it makes sense to use it on /Data (and maybe /Cache) partition.

I did lots of benchmarks with F2FS and only speed improvement i have seen was in Random Write, sequential read/write scores were the same or sometimes even lower than Ext4.
[Nexus 5 Android Development] sparksco:
Well it's worth a test ROM I suppose to see if it fixes it. Unless you can track down what part of the source that is affected. It could be virtually anything.

Edit: you beat me to it lol
[Nexus 5 Android Development] reas0n:
I know about that, I personally use it on data and cache :cowboy: It's all about to make it working!

lol

[MENTION=321148]alsheron[/MENTION] did the latest build (16/02) fix Your issue?
[Nexus 5 Android Development] sparksco:
The ROM will almost always format system partition to ext4 because there's a command in the updater-script to format it to ext4. Unless you use the busybox rm -rf hack in the updater-script.
[Nexus 5 Android Development] reas0n:
So... I beat You to it, part two? :p

https://github.com/VividROM/android...a1624a5/tools/releasetools/edify_generator.py

I'm compiling right now the ROM with rebased F2FS, ETA ~1h, then we will know if it will finally work or not.

(time to use prebuilt chromium for faster compiling, lol)
[Nexus 5 Android Development] sparksco:
Yes but it's not necessary as someone pointed out for system... updater-script doesn't touch the data or cache already.
[Nexus 5 Android Development] reas0n:
Yup, and if it won't work, I think I'll give up. But I hope it will, because now the code is cleaner than before (fstab etc)
[Nexus 5 Android Development] stevew84:
Why oh why do I get System.UI force closes on each CM12 based ROM? I have three devices each having the same issue when changing around the Nav buttons. There are even some cases where right after I get past the login, i get a crash and have to reboot...but the crash still comes back time and time again.

I've been told it could be app related, but when ONLY flashing the ROM, what else can cause the FC? Again this is across multiple devices.
[Nexus 5 Android Development] reas0n:
Odex? You need a deodexed ROM dude :p I will see what I can do.

Btw, AFAIK odex = performance, deodex = modifications. So think once again and choose Your destiny
[Nexus 5 Android Development] stevew84:
Not sure why it seems to be unique to me, though. There is another CM ROM, the one with the extras or whatever it's called in the development forum, and probably one other.

I can run Optipop, CrDroid, Res Remix, Blisspop...etc.
[Nexus 5 Android Development] sparksco:
Could also be data corruption on external sdcard... I've had weird issues in the past like this and the only way to fix it is to format all data on internal and external SD. Also are you using the Google restore option? This can restore system settings across devices and ROMs which is why I never use that option when I set up a clean wiped ROM...
[Nexus 5 Android Development] stevew84:
Really? Happens on the N5, G3 and new Moto X.

Whenever I do a clean install I never use Google to restore/backup anything. I use titanium backup but that wouldn't cause any issues if I can't even restore those apps in the first place.
[Nexus 5 Android Development] reas0n:
hmm, why? because i put in this ROM all internal optimizations/changes available, and it's based on CAF, there are only three CAF roms for hammerhead: myfluxi's vanilla CM, Nameless ROM (pretty much vanilla + interface addons) and mine.

Actually u gave me a one thing to add, I think I can check this out. We will see, if it will affect battery life.

Oh, and it slowly becomes a CM-based ROM, not CM ROM ;) I think the only thing which is CM in my ROM is bootanimation and File Manager lol. Of course I'll add the interface features soon, but the base is the most important for me.
[Nexus 5 Android Development] reas0n:
Update about F2FS on /system:

1. It will be very complicated to make it work without flashing additional things.

2. We would have to sacrifice SELinux (from Enforcing to Permissive) ---> the near zero improvement of /system on F2FS is not worth it.

So the decision is, I'll just leave the automount for /data and /cache only. It's better to install ROM+Gapps(+UKM if someone wants Synapse) than install all those ones + this one, this one... + have to install older TWRP.

EDIT: That's what I prepare for next 1-2 builds:

-deodex

-own bootanimation, no more Cid!

-final cleanup from CyanogenMod things

-try to find out the Spotify audio issues(?)

-anything nice I'd found

So the first "milestone" release is near ;)
[Nexus 5 Android Development] halfbytecode:
I have actually never understood why SELinux in enforcing mode, does not go along with F2FS. Could you please elaborate?
[Nexus 5 Android Development] reas0n:
I was trying to find anything, but failed..

Anyway, SELinux is all about security. I think it just doesn't allow to mod the /system partition and that's all.. If I find something interesting, I'll tell.

Building a new ROM right now!

EDIT: the build is up:

[17/02]

-compiled with disabled DEXPREOPT ( [MENTION=3085842]stevew84[/MENTION] pls test )

-took back Enforcing SELinux ==> F2FS automount for /data and /cache only (safety over useless optimization)

-ro.sf.lcd_density=400 by default (now it looks way better!)

-wifi.supplicant_scan_interval=400 by default (seems to be more reasonable)

In next build probably there will be no new boot animation (had some problems with pngs, nah)

JUSTANOTHEREDIT: Yay, fixed the bootanimation! I hope it will work lol.

ANDANOTHERONE: I think it's time to make a real use of CM Performance Profiles. More info soon ;)

ANDTHELASTONE: Strict Aliasing is coming back ;)
[Nexus 5 Android Development] willybarca:
looking really good, thanx
[Nexus 5 Android Development] reas0n:
Update:

1. There were absolutely no issues with Spotify audio - don't use Viper4Android (software rendering, really? caf-audio is better!) and You're safe

2. CM's way with bootanimations is very complicated.. I feel like I'll just try to use default AOSP bootanimation (if I port it)

3. As I said before - Strict Aliasing comes back now, it didn't cause audio issues.

4. The next build will be a milestone, from then I'll care about interface a little ;) Optimizations are done, I deleted and added what I wanted.

Please tell me, what features from other ROMs are interesting and You'd like to have it here.

Cheers.
[Nexus 5 Android Development] sparksco:
Selinux enforcing just makes your device more secure. Yes it prevents writing to system but also does other things like protect you from apps doing malicious things.

Source: http://threatpost.com/android-5-0-lollipop-upgrades-encryption-application-control/109115

"You can authorize apps with high-level permissions and deep down they’re being granted a lot more access than necessary. With SE Android, Google is expanding and getting more fine-grained controls and containment."
[Nexus 5 Android Development] reas0n:
Great explanation as always, thanks! :cowboy:

Btw, does anybody use Doze? (Active Display like in Motorola, or whatever). I find it really useless on LCD.

I think I'm going to at least disable it by default...
[Nexus 5 Android Development] maddes1402:
Personally I can't live without viper4android and Spotify. But I've never had a problem with this rom. You have so much more options to optimize the sound to your personal taste. With audiofx you feel well...naked? ?

But sorry... Don't wanna be too much offtopic.

Concerning active display I have the same opinion that it's not needed on our kind of display
[Nexus 5 Android Development] reas0n:
Actually V4A can work with caf-audio, but it needs additional build.prop lines, i think a lot of ppl forget about it... I'll add it to OP soon.

To do before milestone build:

-disable Doze by default (done)

-take off the rest of CM 'signs' (Contributors, CM Version...)

-do sth with bootanimation (CM mechanism is pretty complicated, I need only a bootanimation for hammerhead)

After milestone build (requested):

- network traffic at status bar

- animation speed seekbar

- disabled CM Weather by default

mine:

- lcd density settings

- clear recents button in navbar(?)

-make CM Performance Profiles more useful... or just throw them away.

About that CM Performance Profiles thing.. I see some people are talking about some micro lags, it may be like that (personally I don't feel it...) because Chaos kernel (in good way) compromise performance and battery life (proof? I get 6h screen-on time). I plan to make Performance Mode more useful. The settings will be kinda similar to default (who uses performance CPU gov, rly...), but with some tweaks to make the phone 100% smooth.
[Nexus 5 Android Development] halfbytecode:
I have tried to find more about it, but have not been able to either. I'm thinking that once the system partition is setup, using F2FS and OS is installed, and SELinux kicks in at boot, there should not be any issue caused by the enforcing mode. It should be able to "guard" the system partition.

Continued below.

This was a good article. It gave me an interesting piece of information about SELinux, which is that it was brought more into the kernel in Lollipop.

I have previously read that F2FS support is not complete for Android, and is being worked on. May be the issue with F2FS and SELinux enforcing mode, lies in the not yet complete F2FS support.

I really have a hard time believing there would be an issue with a file system and SELinux.
[Nexus 5 Android Development] sparksco:
Well Linux runs on ext4 by default and seandroid is a port of selinux. Samsung made F2FS but not selinux? Selinux is in sorts a type of encryption tested on ext4 file systems...
[Nexus 5 Android Development] halfbytecode:
I should have looked at SELinux code, to clear up my doubts actually. After reading your post, I looked more into F2FS and SELinux.

[MENTION=3371513]reas0n[/MENTION] It appears there was a patch pushed to Linux 3.11 kernel, for adding SELinux support to F2FS. link: https://lkml.org/lkml/2013/6/7/39

I think it adds more plausibility to the reason I mentioned having read about previously. (absence of or incomplete SELinux support in F2FS code used in Android, so far)
[Nexus 5 Android Development] choihanoh:
wow

very smooth fast... good Thanks

wife..

sys / ex4

cache/ f2fs

data/f2fs
[Nexus 5 Android Development] reas0n:
[MENTION=4589869]halfbytecode[/MENTION] But we still need some hacks with e.g. edify to format /system and I remember it wasn't working (CM had changed sth). Because it's brings about zero improvement, let's just leave it for now. I'll take care about it sometime.
[Nexus 5 Android Development] montydrei:
Having an odd issue. When in landscape mode, the navigation bar buttons get...misplaced? and I can't click any buttons. Here's a screenshot:

[IMG="Vivid ROM 17/02 landscape navbar bug"]http://i.imgur.com/wHeRA3nl.png[/IMG]

I originally clean-flashed the 13/02 build, then I dirty-flashed 17/02. I only noticed this issue now on this build because I normally never use landscape mode. An app forced landscape mode, and that's when I first saw it today.