yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] HippoMan:
Putting "Chroma" into the ROM name?

This is a small request:

Could the ROM name be changed to somehow contain the word "Chroma"?

When I do TWRP backups, they get named similarly to this: 2015-06-08--12-39-16_LMY48B

This gets confusing after a while, because I'm not sure if the backup is for Chroma or something else. Other ROMs seem to have their names embedded somehow, and this shows up in the backup names.

Anyway, this is very, very minor. Just a "nice to have".

.​
[Nexus 7 (2013) Android Development] Mujib@r:
You can edit backup names right within TWRP before you make them. You can also edit the file name after the fact.
[Nexus 7 (2013) Android Development] HippoMan:
I know I can edit in TWRP. It's just another step that I have to remember to do. Also, TWRP doesn't let me simply enter a string like "Chroma" in the middle of the existing name. TWRP seems to make me retype the entire name.

But as I mentioned, this is very minor, and that's why I named my request as nothing more than a "nice to have".

.​
[Nexus 7 (2013) Android Development] zephiK:
That's TWRP related, you can rename the backup before you actually do the backup.
[Nexus 7 (2013) Android Development] HippoMan:
Yes, but in TWRP, I can't change the default name by simply inserting "Chroma" within the longer name. I'd have to retype the entire name in TWRP when renaming.

But like I said, this is a very minor thing, and I can certainly live without the bundle being renamed.

.​
[Nexus 7 (2013) Android Development] msalg89:
This ROM is BEAST!
[Nexus 7 (2013) Android Development] quickdraw86:
Not really, you could delete the name, type chroma, then tap the "+date" on the right hand side of the screen... TWRP does 2 digit day and month, and 4 digit year. Like you said, not a big deal, but thought you may be unaware that you could quickly add the date that way.
[Nexus 7 (2013) Android Development] creeve4:
[MENTION=1978554]zephiK[/MENTION] check this commit to GravityBox. It may help you get the Media Volume Control working for tablets.
[Nexus 7 (2013) Android Development] HippoMan:
I wasn't aware of that, and thank you!

.​
[Nexus 7 (2013) Android Development] portezbie:
The last time I updated this rom I flashed the newest gapps with the link you provided and I started getting all sorts of problems related to the gapps, like google play wouldn't open.

When I update to the newest version of Chroma, should I flash the new gapps as well, or is that just for people doing a fresh install?

Thank you.
[Nexus 7 (2013) Android Development] Jagoflax:
Hi, I've installed the ROM but when it boots, it ask me "To start Android, enter your password", I've never set any password on it. I've done all the steps when flashing it. What is happening here? I never seen this before... :(

------------------------------------------------------------------------------------------------

SOLVED! Flashing arter97 kernel did the trick. Should be somethig related with F2FS. I was so afraid.. I bough it last week :o
[Nexus 7 (2013) Android Development] talk2nate:
OK so I'm in a pickle..love love love this rom! BUT :( I can't rotate the screen.. Any ideas?
[Nexus 7 (2013) Android Development] Emalasto:
I had to bc I had an older version of them. If I were you, I would flash the newest ones regardless.
[Nexus 7 (2013) Android Development] rpmfc36:
New BaNkS gapps.

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 7 (2013) Android Development] W@r10ck:
Hi guys, is tap to wake enabled on this rom? Or if not, anyone knows how? Currently downloading the ROM. Lastly gapps from Flo is also compatible with DEB right? Thanks
[Nexus 7 (2013) Android Development] rpmfc36:
No it's not, you need to flash a custom kernel that supports it. Yes, gapps are compatible.

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 7 (2013) Android Development] W@r10ck:
Ok I think I messed up my device hopefully its not bricked. I was trying to follow this http://xdaforums.com/showthread.php?t=2382051 to root my device and then it get stucked to google logo. Ive tried http://xdaforums.com/showthread.php?t=2380913 and this http://xdaforums.com/showthread.php?t=1907796 but it doesnt work. Now I just want to try flash/sideload back to 5.1.1 Lollipop. Has anyone encountered this before? I have nexus 7 2013 LTE ver

Edit: Im able to boot back to life (whew) now my problem is to root this baby in which I followed this guide https://www.youtube.com/watch?v=XM3CBtAaoWU&index=1&list=PL2UDTxRzjyJZ4zU5hRvFmA8IFifXHOZiH which started my problem lol.. anyone can suggest an easier way to root.
[Nexus 7 (2013) Android Development] hamma:
Maybe Nexus Root Toolkit from Wug: http://www.wugfresh.com/
[Nexus 7 (2013) Android Development] W@r10ck:
Thanks, I'll try this out but in the meantime I'll try not to root my device as it feels snappier and faster after a fresh install of the stock image but I'll definitely try this out and this rom ones ive decided to root again.Thanks [emoji1]
[Nexus 7 (2013) Android Development] portezbie:
Is it safe to dirty flash this?
[Nexus 7 (2013) Android Development] rpmfc36:
Sure.

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 7 (2013) Android Development] portezbie:
First I flashed the newest version of chroma. Worked fine. then I tried the new gapps. Gave me errors about google play services and the play store wouldn't open. Maybe it is just my device, but these gapps only seem to work properly on a clean install.
[Nexus 7 (2013) Android Development] vanga83:
I had that issue, too. What I noticed was because I had the pre-dynamic banks gapps already installed first before this update and when I flashed the newer dynamic gapps, it gave me Google Play errors and the Play Store was gone. Like you said, clean install will work with no issues if you want to flash the newer dynamic banks gapps.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Obviously up to you, but worked for me...
[Nexus 7 (2013) Android Development] zephiK:
I'll be updating the manifest and sources sometime later this week for builders to compile for N7 2012/N7 2013/N10.

Spent 1 week on rewriting Chroma from scratch for a better build to clean out the bugs that users were encountering.
[Nexus 7 (2013) Android Development] andy_rose:
Looking forward to the new rebuilt rom. Running it on my mako, and it is great!
[Nexus 7 (2013) Android Development] zephiK:
Just an update, going to keep working on Chroma rewrite before I push the sources up to Chroma-Aosp git.

So it'll be available for next build (or 2 builds), depends on how complete it is.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks for keeping us informed....
[Nexus 7 (2013) Android Development] 2LoWw7:
Anyone have Viper4android working on this ROM? I have it installed but won't process!
[Nexus 7 (2013) Android Development] fordmanck:
Did you change selinux to permissive?
[Nexus 7 (2013) Android Development] 2LoWw7:
Yep!
[Nexus 7 (2013) Android Development] fordmanck:
How about disabling Nuplayer?
[Nexus 7 (2013) Android Development] 2LoWw7:
Yes, changed to use Awesome player. Also, a side issue I'm having is using the Screen Cast is not working for me. Worked perfect with Stock Android before I flashed this ROM. Any help there as well?

Edit: Dirty flash fixed Screen Cast problem! :)
[Nexus 7 (2013) Android Development] brightjh01:
Thanks for fyi.
[Nexus 7 (2013) Android Development] zephiK:
Unofficial builders,

Sources should be updated for the new rewrite, feel free to build and resync.

You'll most likely have to rebuild from scratch as it is a rewrite.
[Nexus 7 (2013) Android Development] zaclimon:
Only the repos have been changed so far so there isn't any changes from a manifest perspective right?
[Nexus 7 (2013) Android Development] zephiK:
I made the new rom rewrite be inline with the previous manifest.

You just have to repo sync.

Full wipe will be required.

Edit: Fixed an error that was in the manifest. /vendor/chroma should be lp5.1 branch not lollipop

Edit 2: fixed another problem 4:13 pm eastern 06/21.
[Nexus 7 (2013) Android Development] zaclimon:
Update time (rewrite edition)

[MENTION=1978554]zephiK[/MENTION] You might want to revert that e2fsprogs commit you pushed in the manifest. Flo do need it in order to be built. :p (Well because you deleted that repo as well in your source, I just took it from the CM one)

As for you guys, here I leave a build based on the latest rewrite.

Flo: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/chroma_flo-ota-2015-06-21.zip

Deb: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/Deb/chroma_deb-ota-2015-06-21.zip

Gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps

As per zephiK instructions, it might be best to start out from a clean flash, though I believe you can be fine even though it was made on a dirty one.

Enjoy!! :)
[Nexus 7 (2013) Android Development] SHABBYLEA:
You are a star...also thanks to zephik...

Thanks...
[Nexus 7 (2013) Android Development] zephiK:
Dirty flash is not allowed and I highly suggest not doing it. The ROM is rewritten from scratch and will cause problems.

A clean wipe is absolutely required.
[Nexus 7 (2013) Android Development] MatVekk:
I come from Rom euphoria and other Rom. but this is the best. always smooth. Battery infinite. Thank you.

Inviato dal mio Nexus 5 Cataclysm 5.1.1
[Nexus 7 (2013) Android Development] andy_rose:
The layers manager app is updated and the activity name has changed. So it can't be launched from settings until the rom have that change included.
[Nexus 7 (2013) Android Development] zephiK:
New layers manager update changes it back to how it was before. Just update layers manager and then it will work.
[Nexus 7 (2013) Android Development] Mujib@r:
To confirm, Layers Manager v4.1 fixes settings FC problem. If updating from old version (pre-4.0), first uninstall app, then reinstall from Play Store.
[Nexus 7 (2013) Android Development] rydebaas:
Where a change dpi menu on setting-display ? Bad update on 21 june ??
[Nexus 7 (2013) Android Development] travster119:
You have to use an app from now on because the DPI changer in settings was unstable and just caused problems I'm pretty sure.
[Nexus 7 (2013) Android Development] zephiK:
It caused boot loops for those who changed their DPI. It wasn't worth having when you can install a <1MB app or change it via build prop or whatever way you want to change it.

_r5 fully merged.
[Nexus 7 (2013) Android Development] 777.300:
Latest version running almost perfectly.

I only having a small problem.

Running latest version, Franco Kernel and did a clean install.

Since installation the Notification of Battery Widget Reborn does not stick.

After installation of the app the battery percentage is shown in the upper LH corner.

After a few minutes the notification disappears and can only be brought back by stopping the app and restarting it.

I reinstalled the app, no cure.

Did not had this strange behavior before and on my N5 with Chroma it is working fine.

Just a small glitch, no big deal but it is strange.

Hope to find a solution for it.

Thanks for the great work on this ROM, really loving it.

Ps used the priority switch under app notifications and the battery percentage stay in view now.
[Nexus 7 (2013) Android Development] Tex99:
Thank you for this rom it s great :) I use it also on n5

The only option that doesn t work is "volume rocker wake" when the device is in deep sleep. Anyone else ? I know that this option doesn t work well with many tablets when they go into deep sleep. it seems to me that theDarkDefender (simpleaosp team) had found a fix for it.

Thanks again
[Nexus 7 (2013) Android Development] quickdraw86:
Same here. Vol. Down wakes my device consistently if pressed just after screen off, but won't wake the device at all after it is left idle long enough to enter deep sleep. Fortunately, there will likely be an update soon, as 5.1.1_r5 was released some time ago.

Fantastic ROM though, and very small issue, will continue to run chroma anyway.
[Nexus 7 (2013) Android Development] zaclimon:
Wussup everyone? New update incoming. :p It is based upon [MENTION=1978554]zephiK[/MENTION] recent merge of the 5.1.1_r5 tag.

28/06:

Download:

Flo: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/chroma_flo-ota-2015-06-28.zip

Deb: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/Deb/chroma_deb-ota-2015-06-28.zip

Gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Changelog: https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE

Also, [MENTION=4845088]Tex99[/MENTION] and [MENTION=4471805]quickdraw86[/MENTION], TheDarkDefender as a fix disabled the volume wake because it wasn't working very nicely with tablets. See the commit here.

Enjoy! :)
[Nexus 7 (2013) Android Development] zephiK:
That commit was already included with Chroma a month ago ;) https://github.com/Chroma-Aosp/andr...mmit/189a5cf4e1d903eab9df8cdf9d91cedfedb25d11

updated OP.
[Nexus 7 (2013) Android Development] SHABBYLEA:
Thanks all for your work...

Cheers....
[Nexus 7 (2013) Android Development] quickdraw86:
Thanks for the information, and the builds of course, latest runs great so far.
[Nexus 7 (2013) Android Development] andy_rose:
[MENTION=4217103]zaclimon[/MENTION], I see there's yet another chroma update out today with some cool changes like slim launcher.
[Nexus 7 (2013) Android Development] zaclimon:
I won't be able to do anything until tonight because of work. :/

(and I just updated yesterday, Dat timing)

Envoyé de mon Nexus 7 WiFi en utilisant Tapatalk
[Nexus 7 (2013) Android Development] andy_rose:
No stress, I can wait ☺☺
[Nexus 7 (2013) Android Development] zephiK:
No you can't ;)

Kidding of course :p
[Nexus 7 (2013) Android Development] scottx .:
Why did you change the device name from Nexus 7 to Nexus 7 WiFi? To screw things up that look for it in build.prop? So many rom devs do senseless edits like this. Seen it time and time again. Like when you boot instead of saying Android is upgrading its been changed to Chroma for no reason. Quit vanity editing.

Really not cool IMO.
[Nexus 7 (2013) Android Development] zaclimon:
Never really knew why it is like this. I do remember that I had this issue once for my app because it was checking for the device model instead of the device name but oh well.

I will change this for 30/06. (Sorry guys to delay it, I had some FC's when trying out this build, related to sepolicy)
[Nexus 7 (2013) Android Development] zephiK:
If you're really going to get upset because of a string update. You should also know that, I dont have ANYTHING to do with the unofficial builds.

If you're going to get upset over a developer's work when developers don't owe you anything then I highly suggest for you to make your owm ROM or move along to another ROM that is more suited to your needs.

I'm getting really annoyed at the lack of respect that is going around not only in Chroma threads but the overall "modding / rom / kernel" scene.
[Nexus 7 (2013) Android Development] JNewms:
You are highly critical of ROM developers, and their decision making. You tell them what they should or shouldn't do, and have a very entitled air about you. It's a few free ROM, you don't pay the dev's salary. Basically you are in absolutely no position to make demands of scold a developed for the decisions they make on THEIR ROMs. If you think you can do so much better, and have all the right answers, them go compile your own builds and develop on them.
[Nexus 7 (2013) Android Development] quickdraw86:
I agree on the bit about the modding scene. I think it's a symptom of it being very easy (toolkits, one-clicks) to root and unlock devices these days. Back in the adb/command line days, users in general had more respect for their devs. After all, most devs probably do this as a hobby, and, unfortunately, a lot of great projects and developers are gone due to an overly demanding and hugely unappreciative user base. You could always go strictly g+, and kick out the rudest, but that seems like it would decrease views and users overall... Just my opinion.
[Nexus 7 (2013) Android Development] zaclimon:
Geez why are you guys so willing to fight over...

I understand why such a modification was made but make it senseless is a bit harsh. (Now that I took a look more throughly at the post)

I always put this link to remind some that they are on XDA not as customers but as developers! They come here expecting to understand how stuff works and contribute to the community

http://xdaforums.com/showpost.php?p=2031989&postcount=45

Take a look guys if you haven't so and [MENTION=1978554]zephiK[/MENTION] didn't you say it was your rom? In this case you shouldn't mind these comments am I right? XD

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 7 (2013) Android Development] mbl1979:
Great, now they are trolling chroma for Nexus 7. I guess the ROM is getting that popular . I for one am loving chroma ROM and have nothing bad to say. Zac you doing good man keep it up.
[Nexus 7 (2013) Android Development] dadymon53:
Troll alert!
[Nexus 7 (2013) Android Development] dragontology:
Best solution would be to get a build.prop editor (ROM Toolbox has this, but it may be overkill if that's all you need) and then adjust this cosmetic string on your own. The developer is not your house elf.

It isn't a valid complaint, but I can see the motivation. Google Play does look at build.prop for compatibility, but it doesn't look at the friendly name, it looks at the code name or whatever. In our case, flo. A developer might be unwise to change that, if I understand things the way I think I do. But the friendly name? Meh. Besides, it helps differentiate it.
[Nexus 7 (2013) Android Development] zaclimon:
Heck, it could even be changed in the zip but I forgot that with Lollipop, there is this block based stuff which makes it a little more painful to make a rather simple change XD. Though, as I said, I will change that for today's build. (repo syncing at the moment) :p
[Nexus 7 (2013) Android Development] SHABBYLEA:
Spot on...
[Nexus 7 (2013) Android Development] Traxex_:
Nova Launcher keeps crashing for me even after a clean flash :/

Had no problems with earlier builds.
[Nexus 7 (2013) Android Development] quickdraw86:
I use nova too. I fresh flashed the latest chroma, restored nova app+data from TiBu, and moved nova to /system/app. I don't have any FC issues, but you might try a fresh installation of nova from the play store, and a fresh set up of nova. It's possible that if you restored nova settings via nova backup that the backup you restored was corrupt, same goes for app backups made with an app like TiBu or ROM manager.
[Nexus 7 (2013) Android Development] TonyStark R.I.P.:
Good day to you all.

Per the request of zephiK, please read and understand the following​

We (moderators) have been called to this thread way to many times for issues regarding OT (Off Topic).

So you say to yourself what's OT mean in a Dev thread

OT is anything that is un related directly to the development of this ROM.

Again you say So where do I post if I need help with an issue

You first search the thread to be sure it hasn't already been mentioned and fixed.

You post here with explicit description of issue AND POST A LOGCAT!

You post to the Q&A found here. This is where 99% of all conversation should take place

So you're thinking everything I say is important:eek: There are way to many of you that believe this to be the case. You are wrong. The only important comments made in this thread are posted clearly with ROM issues (this does not include in which you've added to your setup)

Bottom line is this. From here on anything deemed non Development, which could have been posted in Q&A, will simply be removed.
[Nexus 7 (2013) Android Development] zaclimon:
Canada day update

Hi guys, first of all, my bad that I have to push an update this late. Had to deal with issues coming from the Torch patches that zephiK merged lately. It is based upon the 29/06 build. A later one based on 01/07 will come later (don't ask for ETA's...)

01/07:

Download:

Flo: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/chroma_flo-ota-2015-07-01.zip

Deb: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/Deb/chroma_deb-ota-2015-07-01.zip

Gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Changelog: https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE/edit?usp=sharing

Enjoy!! :)
[Nexus 7 (2013) Android Development] rpmfc36:
Unfortunately, seems like the next build will be the last one for now. ?

From zephik's N5 thread:

Changelog: https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE

Download: https://www.androidfilehost.com/?fid=24052804347767667

Last build, going to take a break from development. Enjoy the last bits that I was working on.

Enviado do meu Nexus 7 através de Tapatalk
[Nexus 7 (2013) Android Development] HippoMan:
Thanks VERY much to zephiK for ALL his great work!!

... and I just want to point out that the download link, above, points to a hammerhead release, not flo.

.​
[Nexus 7 (2013) Android Development] NickDoughty:
Getting a "unfortunately, setup wizard has stopped" on boot after install. Retried install a couple of times and same result....anybody?
[Nexus 7 (2013) Android Development] busventinc:
https://basketbuild.com/devs/zaclimon/flo/Chroma
[Nexus 7 (2013) Android Development] dnle71:
Ambient display is not working ?
[Nexus 7 (2013) Android Development] arby80:
I was having this problem then downloaded the 07/01 Build and everything is working.
[Nexus 7 (2013) Android Development] Traxex_:
I can't disable quick pulldown in settings, it still works on the right side.
[Nexus 7 (2013) Android Development] andy_rose:
Looking forward to the build based on 1 july build :)
[Nexus 7 (2013) Android Development] zaclimon:
Tomorrow. :p
[Nexus 7 (2013) Android Development] SHABBYLEA:
Excellent...?
[Nexus 7 (2013) Android Development] zaclimon:
Hi guys, some might have waited for it since last week but I decided to delay it because it wouldn't make much sense to release a build, then another right after considering I don't have much time to compile these days. Without any other due, here it is.

08/07:

Flo: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/chroma_flo-ota-2015-07-08.zip

Deb: https://basketbuild.com/filedl/devs?dev=zaclimon&dl=zaclimon/flo/Chroma/Deb/chroma_deb-ota-2015-07-09.zip

Gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Changelog: https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE/edit?usp=sharing

Looks like it will be the last build in a while as zephiK is currently on break.

Enjoy!! :)
[Nexus 7 (2013) Android Development] rpmfc36:
Maybe not, [MENTION=1978554]zephiK[/MENTION] is back on business on N6 and N5 threads. ?

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 7 (2013) Android Development] zaclimon:
He's still on break but he wanted to get a maintenance build out because an r8 tag has been released for 5.1.1. I'll get those out tomorrow for ya. :p

EDIT: Sometimes between today and tomorrow as I always get weird errors...
[Nexus 7 (2013) Android Development] MattDN93:
I know posting thanks here is unnecessary, but this is the first ROM I flashed on my N7 2013 since I bought it,which was a week after its launch, I've been trying to resist the ROM life on a Nexus but I don't regret pulling the trigger with this ROM. Thanks for the regular build updates, also!
[Nexus 7 (2013) Android Development] zaclimon:
Sorry to be a party pooper everyone, but I can't get chroma to build after the update to r8. I have an error related to frameworks_opt_net_ims but I can't seem to fix it.

I've reached zephik regarding this issue. Though, he pretty got mad and said that he didn't care about unofficial builds and removed the manifest again. (even though the error do happen with official devices...)

Have somebody successfully been able to compile a build since the last chroma update?

Envoyé de mon Nexus 7 en utilisant Tapatalk