yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] GtrCraft:
After trying for a day this the error I get:

frameworks/opt/net/ims/src/java/com/android/ims/internal/ImsCallSession.java:925: error: ImsCallSession.IImsCallSessionListenerProxy is not abstract and does not override abstract method callSessionMultipartyStateChanged(IImsCallSession,boolean) in IImsCallSessionListener

private class IImsCallSessionListenerProxy extends IImsCallSessionListener.Stub {

^

frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java:803: error: ImsManager.ImsRegistrationListenerProxy is not abstract and does not override abstract method registrationDisconnected(ImsReasonInfo) in IImsRegistrationListener

private class ImsRegistrationListenerProxy extends IImsRegistrationListener.Stub {

^

frameworks/opt/net/ims/src/java/com/android/ims/ImsManager.java:828: error: method does not override or implement a method from a supertype

[MENTION=439709]override[/MENTION]

^

frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java:358: error: method updateCallForward in interface IImsUt cannot be applied to given types;

int id = miUt.updateCallForward(action, condition, number, timeSeconds);

^

required: int,int,String,int,int

found: int,int,String,int

reason: actual and formal argument lists differ in length

frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java:385: error: method updateCallWaiting in interface IImsUt cannot be applied to given types;

int id = miUt.updateCallWaiting(enable);

^

required: boolean,int

found: boolean

reason: actual and formal argument lists differ in length

Note: frameworks/opt/net/ims/src/java/com/android/ims/ImsUt.java uses unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

5 errors

make: *** [out/target/common/obj/JAVA_LIBRARIES/ims-common_intermediates/classes-full-debug.jar] Fout 41

Maybe someone can tell me what's wrong
[Nexus 7 Android Development] zephiK:
I'm not back, I'm still on break. It's a maintenance release, nothing more than that.

I've closed down the manifest for the time being.

AOSP has a compilation error. All you have to do is use a previous branch, but even then there's no point because I didn't update the sources nor am I going to until I make a full return.
[Nexus 7 Android Development] googleygoggles:
You forgot to delete system32.

I'm not helping am I?
[Nexus 7 Android Development] GtrCraft:
Ok, I will wait. I hope the rest can
[Nexus 7 Android Development] pointman_12:
[MENTION=5293805]GtrCraft[/MENTION]

appreciate you trying to keep us up to date...I'm still following the thread...06/22 build is working so I'm happy...
[Nexus 7 Android Development] GtrCraft:
There is a newer build couple pages back I think
[Nexus 7 Android Development] mirkuma:
Nice ROM, best from 5.1.1 I tried. Only problem is that MX Player, don't work properly (movies skips, freeze and auto restart in the middle of time in hardware and software decoder mode).

Seems to be kernel or ROM related as google stock 5.1.1. works fine with latest MX Player.

Can anyone else confirm this MX player behaivor (try to play movie at least 5+ min if problem occurs).

Edit:

For now I have changed from MX to VLC, but also VLC only works in software decoding mode (but not with hardware decoder mode), but at least without problem.
[Nexus 7 Android Development] pointman_12:
[MENTION=5293805]GtrCraft[/MENTION]

I have that one installed...runs great...

[MENTION=4665850]mirkuma[/MENTION]

did you install the codec for the tegra 3 processor?...I tried mx player...seems to run fine...I ran a 4+ min video and not one stutter...
[Nexus 7 Android Development] mirkuma:
Yes all codecs installed tegra3 + including audio ac3 codec.

Happens on xvid and mp4 formats.

For me it forks for a first few minutes, but then problems start to occur.
[Nexus 7 Android Development] GtrCraft:
Don't have that issue, do a clean flash with stock kernel
[Nexus 7 Android Development] mirkuma:
It was clean flash. I'm not sure about kernel (shouldn’t be kernel flashed automatically within Rom flash?)

I was before on DirtyUnicorns ROM and then clean flash to Chroma. I didn't flash any kernel manually by myself.

Will check in the evening which kernel is actually running at the moment.

In case that kernel is the problem:

It there any way to flash via TWRP just official google kernel from 5.1.1, as I have all configured now and don't want to start from scratch? If yes, can someone provide link to the stock kernel.

Thank you.
[Nexus 7 Android Development] GtrCraft:
Extract the boot.img from the rom zip and flash it with TWRP
[Nexus 7 Android Development] mirkuma:
Will try that and report back.

Thank you.
[Nexus 7 Android Development] Miracle1980:
I noticed that the Nexus 7 3g link is not working anymore. Could you please upload it again?
[Nexus 7 Android Development] Yash9060:
BUG

System ui crashes when i set ring target to kill app and use that function .

Clean install and recommended gapps

thanks
[Nexus 7 Android Development] mirkuma:
Apologies to all. After flashing stock kernel I was in bootloop. It seems that In a "flash fever" I have actually flashed XenonHD ROM with iceandfire Kernel after trying Chroma ROM.

So my problems were not Chroma ROM related. :eek:

But thank you for instructions how to flash kernel separately.

Moderator can delete my posts from this tread, sorry again for wrong post.
[Nexus 7 Android Development] GtrCraft:
Update:

Took me a while to figure out but I got a new build for you guys. The build is now fully 5.1.1_r5 (r6-r8 is only for nexus 7 2013 and nexus 6)

Rom:

https://www.androidfilehost.com/?fid=24052804347777088

Changelog (everything except build update as stated above):

https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE/edit
[Nexus 7 Android Development] Godfather13:
Hello,

Fresh installation with the today update => system UI is crashing at the end of the installation, cannot continu the installation process :(
[Nexus 7 Android Development] frikakwa:
No problem here, all is running fine and smooth! Check your gapps...
[Nexus 7 Android Development] Godfather13:
Performed installation with June release and same gapps => its works well
[Nexus 7 Android Development] frikakwa:
Did you try to format system + format cache + format dalvik cache + format data?
[Nexus 7 Android Development] PatrickMac:
Can confirm the systemui bug after a clean install
[Nexus 7 Android Development] GtrCraft:
Try to clean flash older build and dirty flash this one over it
[Nexus 7 Android Development] ThurstonX:
Thanks for the new build. Everything seemed to go fine, until I got to Settings. I tested most, but when I tap "Sound & notification" I get the following error:

"Unfortunately, Settings has stopped."

100% repeatable. Every other option in the Device section works fine, as do most if not all of the other settings options. If I use the volume rocker to get the drop down menu, I can adjust the Notification volume, and use the down 'v' to get and adjust all three volumes.

FWIW, I dirty flashed over my clean install of chroma_grouper-ota-2015-06-22. Previously, the Notification volume adjustment under the "Sound & notification" options was grayed out.
[Nexus 7 Android Development] frikakwa:
[MENTION=4925283]ThurstonX[/MENTION]: same on mine... FC when clicking on "Sound and notification"! I'm pretty sure [MENTION=1978554]zephiK[/MENTION] can help b/c we already had this on N5 build a long time ago! ;)
[Nexus 7 Android Development] pincher65:
at me also

unfortunately doesn't help
[Nexus 7 Android Development] GtrCraft:
I'm making a new build so be patient pls
[Nexus 7 Android Development] GtrCraft:
Update

FC´s for notifications and sounds fixed and fully up to date with the changelog

Rom:

https://www.androidfilehost.com/?fid=24052804347777675

Changelog:

https://docs.google.com/document/d/1c7wNrT0khaipv-M0Z35OPQ8sxPHO-e9-Rk945fo4iJE/edit
[Nexus 7 Android Development] frikakwa:
You man are the best: no more FC! Great work! Thanks a million! :good:
[Nexus 7 Android Development] ThurstonX:
Dirty flashed and everything's looking good after a cursory go 'round Settings. Thanks a lot for the quick fix :)
[Nexus 7 Android Development] GtrCraft:
Thanks button? :p
[Nexus 7 Android Development] ThurstonX:
My bad! Hooked you up. I blame too much multi-tasking, not enough coffee... yet :D
[Nexus 7 Android Development] webdroidmt:
Thanks for keeping up the Chroma builds as well as your other contributions to grouper.

Your efforts are pure and definitely not minimal. ;) :D

Thanks man,

Mike T
[Nexus 7 Android Development] PatrickMac:
Clean flash still results in systemui FC. will try dirty flash now
[Nexus 7 Android Development] GtrCraft:
Are you using a custom kernel? And which gapps and mods do you use?
[Nexus 7 Android Development] PatrickMac:
I'm using M-Kernel and Slim Gapps. No other mods

M-Kernel works fine with the 22.06 release and on other ROM's as well.

But maybe that is the cause of the systemui bug. Even after dirty flashing the FC occurs.
[Nexus 7 Android Development] decky006:
Hi.

I still get the systemui crash. Tried clean and dirty flash. I am using the tk gapps from last week.

Which gapps are people using to get it to work? I can try again.
[Nexus 7 Android Development] GtrCraft:
I use that latest tk gapps, and M kernel is probably part of the problem. Try to flash without anything else. And also use the latest TWRP
[Nexus 7 Android Development] PatrickMac:
Hm, I'm on F2FS data +cache, so M kernel is a must.
[Nexus 7 Android Development] GtrCraft:
Franco kernel or go back to ext4, there is no benifit anymore really
[Nexus 7 Android Development] sroma1980:
Dirty flash over previous build. Using franco kernel and is running great. No problems so far. Good work
[Nexus 7 Android Development] ThurstonX:
I dirty flashed, adding tk_gapps and M-Kernel (a77) to the same TWRP install procedure, and everything seems to be running fine. I suppose I would have seen the SystemUI FC if it were going to be a problem. Using ext4, not F2FS.
[Nexus 7 Android Development] PatrickMac:
Ok then. It seems this ROM doesn't support F2FS anymore.
[Nexus 7 Android Development] TenBelowZero:
Sorry, seems like it's not working for me.

Tried everything I could reasonably think of.

TWRP 2.8.6.0 / 2.8.7.0, BaNkS-Gapps / TK-Gapps, M-Kernel / Franco / Stock., clean install / dirty flash (07-20 over 06-22).

Chroma 06-22 always running smoothly, 07-20 always crashing with SystemUI FCs.

Think I'll stay with 06-22 for now, maybe do some research when I've got more time.
[Nexus 7 Android Development] pincher65:
at me too, twrp 2.8.7.0/TK Gapps 17.07/ all stock/ no mod.
[Nexus 7 Android Development] GtrCraft:
F2FS?

---------- Post added at 11:26 AM ---------- Previous post was at 11:26 AM ----------

It never supported it
[Nexus 7 Android Development] pincher65:
No, ext4
[Nexus 7 Android Development] PatrickMac:
Well something has changed. Because I can run the June build with F2FS without an issue, but the new one seems to have a problem with F2FS
[Nexus 7 Android Development] GtrCraft:
That it worked doesn't mean it was supported
[Nexus 7 Android Development] TenBelowZero:
I'm on ext4 too, never tried f2fs.

I've literally tried every combination of ROM, kernel, recovery, GApps, clean and dirty flash I could think of,

always the same result: Chroma 06-22 booting up and working well, 07-20 crashing SystemUI.

No idea what else to try.
[Nexus 7 Android Development] GtrCraft:
Maybe flash the factory image, or redownload the rom. Only 2 of you users got it which is quite weird
[Nexus 7 Android Development] PatrickMac:
It is weird indeed. I just switched to ext4 to test the behaviour and it still results in a FC after the intial boot. I just flashed the ROM.zip (redownloaded it to be sure) with tk's latest pico gapps and supersu. TWRP version is 2.8.7.0

I have absolutely no idea what the issue is here...
[Nexus 7 Android Development] decky006:
I can't get it to work either. Sticking with 22/6 version which is great anyway.
[Nexus 7 Android Development] PatrickMac:
[MENTION=5293805]GtrCraft[/MENTION]

I even went so far and flashed the stock image and then tried it again on ext4. I'm sorry, but it seems obvious that the build has some kind of error.
[Nexus 7 Android Development] GtrCraft:
Well I am typing from that very same build. Provide a logcat and maybe then I can figure it out. But the majority has no issue except you 2
[Nexus 7 Android Development] PatrickMac:
It is not just 2 people with the problem.

I will try to get you that log
[Nexus 7 Android Development] 1haumann1:
No fc at all here

system - ext4

data & cache - f2fs

keep calm and have a Nexus :D
[Nexus 7 Android Development] TenBelowZero:
Yeah, but the crowd is growing . . .

I've downloaded the zip file from two different mirrors, the file is identical on byte level.

But to flash the factory image might be an option.

I'm getting suspicious - could it be that all of you guys having trouble with Chroma 07-20 have been using M-Kernel before?
[Nexus 7 Android Development] GtrCraft:
Can somebody with the issue please first flash the 29-06 build and then the 20-07 build?
[Nexus 7 Android Development] buffal0b1ll:
Thanks for grouper Chroma. I didn't think it got better than Rastapop, but Chroma seems faster so far.

Tried to go with f2fs data and cache on a couple clean chroma flashes, but I had mysterious insufficient space errors after booting even though 12gb was available. I had to make a backdoor to get an f2fs data instance that I could download to sdcard card on working (installed ROM all ext4, completed welcome setup, nandroid data partition to OTG, format cache and data to f2fs, flash Franco, restore data only nandroid).

Anyhow, it was like solving a Rubik's cube, and I'm more than happy.

Thx again ;)﻿

---------- Post added at 10:46 PM ---------- Previous post was at 10:35 PM ----------

I disabled playstore when I ran TiBU restores because it kept force closing every few seconds. Enabled after TiBU was done, cleared playstore app data, and alls well. 4/4 banks BTW.

Skipping Wi-Fi on Welcome screens and getting to it later got around the checking connections forever Gapps issue too.
[Nexus 7 Android Development] sykopompos:
First I'm heading of the camera not connecting

That's a known bug in aosp, I have the fix for it for ages, just keep forgetting to fix it ?
[Nexus 7 Android Development] buffal0b1ll:
A working camera would be swell indeed, but on grouper all the cameras good for is taking nose hair close ups anyhow.
[Nexus 7 Android Development] suku_patel_22:
Thanks

Grouper is used by my 2 year old son and he loves firing up the camera and making weird faces :). So pretty important for me

Sent from the sixth dimension.
[Nexus 7 Android Development] sykopompos:
Didn't know the camera wasn't working.

I don't have any of the tablets so I gotta rely on feedback from testers and it was never mentioned that it wasn't working ?

I'm gonna be working on grouper/tilapia and manta tomorrow
[Nexus 7 Android Development] buffal0b1ll:
I'm 90% sure the sideloaded Google Camera was working on 4/2 build. On 4/4 and 4/5 it crashes on first launch, and tries to open on second try, but hangs. Same behavior if I try to put the Nexus 7 Camera Official launcher app out in front of it (a fix that worked on a previous ROM I used).

Edit: Here's a log http://dl.dropboxusercontent.com/1/view/1ft5k4yar2lytas/2015-04-06-23-16-53camera.txt

---------- Post added at 11:28 PM ---------- Previous post was at 11:10 PM ----------

Do the ART mods in 4/5 make the already xplosive xposed super alpha even more xplosive? I heard they don't play nice. I got it working with Minmin guard on 4/2 chroma, but I clean flashed on 4/4 and haven't tried xplodes again yet.
[Nexus 7 Android Development] webdroidmt:
Camera is working for me. I downloaded A Better Camera from PS which works just fine. I also sideloaded a Camera2 app from another 5.1 rom which works with the N7 camera launcher from PS.

As others mentioned, I had problems with Google Play Store force closing with the 4/4 Banks gapps, installed the 3/28 Banks gapps and had no issues.

Great rom!

EDIT: Sorry guys, it was A Better Camera app, not Open Camera app. I was confusing the Open Camera app with another device. Too many devices and too many rom flashes. LOL Although, I just sideloaded Open Camera on my N7 and that works too.

Thanks,

Mike T
[Nexus 7 Android Development] sykopompos:
I don't even know what those xplosive xposed things are, I wouldn't recommend using the xposed port for 5.1 since it doesn't seem to play nice even though it shouldn't effect it because they play fine on 5.0.x together fine
[Nexus 7 Android Development] SkOrPn:
Well I got the device storage space fixed but it took longer than I expected. I had to flash the stock recovery and do a factory reset from there. I had thought factory resets from Android, or twrp or from fastboot mode would have worked but the 7 or so times I tried today would not fix it. Only the stock recovery got my sdcard back normal. Thankfully I made a twrp backup of this wonderful ROM and restored it successfully.

Let this be a lesson, sometimes only the stock recovery can fix things. Lol it took me a while to remember how to do a factory reset in the stock recovery as its been two years since I last seen that thing. Hahaha
[Nexus 7 Android Development] decky006:
The cameramx app works OK for me. This ROM is excellent so far.
[Nexus 7 Android Development] ravencrown2000:
System Format

Question, before I proceed, Do I have to change to system format from f2fs to ext2?

Thanks
[Nexus 7 Android Development] HaRdC0r3:
Ext4 not 2...please correct me if I'm wrong.
[Nexus 7 Android Development] ravencrown2000:
Thanks my friend, because I was thinking of retaining the f2fs format as it is giving my n7 a better performance, its too bad that this rom doesn't support f2fs, but according to one of the post on first page, you can still use f2fs format for cache and data but they never mention about the system
[Nexus 7 Android Development] frikakwa:
Using f2fs on data and cache is enough for having a good performance. No need to format system to f2fs!

Chroma + Franco 82 + f2fs = better than ever! ;)
[Nexus 7 Android Development] nmugurel2003:
Have you find any workaround for the navbar issue yet?
[Nexus 7 Android Development] GasperP:
What do you do, to have f2fs?

Sent from my Nexus 7 WiFi
[Nexus 7 Android Development] buffal0b1ll:
What ^^ he ^^'said in post above.

With Franco r82, a f2fs compatible, kernel you can use any ROM with f2fs on data and cache partitions. Leave system formatted as ext4 as the ROM is not build for all-f2fs. In theory, only cache and data are written to so they are the only partitions that really benefit from f2fs anyway.

If you run into any trouble, I posted a workaround for f2fs and insufficient space errors a page or two

back.

---------- Post added at 08:29 AM ---------- Previous post was at 08:25 AM ----------

I fixed the storage space issue by formatting data partition back and forth between f2fs and ext4 in TWRP. Flashed chroma as all-ext4, confirmed I could download to the sdcard after setup, made a nandroid of data partition to OTG, went back to f2fs on data and cache, restored nandroid. BAM. Works great.
[Nexus 7 Android Development] ravencrown2000:
Thanks Guys for all the comment with regards to f2fs, i try this, I used to format all the partitions in f2fs
[Nexus 7 Android Development] GtrCraft:
Can this be happening because of a bug in Chroma?
[Nexus 7 Android Development] striker59:
Play Store was working until I used Titanium to restore a couple apps. Then I was getting notification the store has stopped. Since I'm a first time user I did a factory restore, Play Store worked so I got a few apps I knew I would need then ran Titanium again and wham store stopped. I froze it with Titanium and if I need an app I look for a direct download using Chrome.
[Nexus 7 Android Development] PatrickMac:
I can't describe how surprised I am. As I rebooted to take the logcat it finally did boot without any errors.

I even tried it again on F2FS and it works, too.

No idea what happened, I didn't do anything different this time. Just weird.
[Nexus 7 Android Development] TenBelowZero:
06-29 doesn't work for me either.

I tried clean flash and dirty flash over 06-22, it also crashes with SystemUI FC.

I must admit I started investigations only after I couldn't get 07-20 to work,

so there may have been side effects, though I did a few full wipes.

06-22 however working well with different kernels and gapps.
[Nexus 7 Android Development] GtrCraft:
What the ****? I am really confused now

---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------

Try to take a logcat, or someone else with the issue
[Nexus 7 Android Development] PatrickMac:
Yeah, me too. I'm sorry I couldn't give you that log though.

Maybe someone else can do it.
[Nexus 7 Android Development] GtrCraft:
Ok, I know what the FC is causing. The flashlight toggle in quicksettings or navbar...

You can change the quick settings in the 06-22 build and then dirty flash to the latest build. I should work then.

I am trying to fix it but my knowledge is not very big with this stuff so I don't know if I can
[Nexus 7 Android Development] GtrCraft:
Update

With the help of N7 2013 maintainer [MENTION=4217103]zaclimon[/MENTION], I fixed the systemui fc at startup (due to torch/flashlight commits)

Also I saw that franco kernel is still the kernel for this rom (I thought it was stock/google), do you guys want franco or stock/google kernel in future builds?

ROM:

https://www.androidfilehost.com/?fid=24052804347779625
[Nexus 7 Android Development] ThurstonX:
Thanks again. re: the kernel, I'll just end up flashing M-Kernel, so whichever.
[Nexus 7 Android Development] Harpratap:
I don't know about others, but with f2fs+Franco Kernel it corrupts the internal memory for me. I have experienced it twice on franco's kernel, few others have reported the same. So maybe staying stock would be better IMO.

Will the franco kernel (if included) be updated one or the same in his original thread for grouper?

Thanks for the ROm though! :D
[Nexus 7 Android Development] GtrCraft:
That's a known issue with franco, so don't use f2fs with it. It's the same one
[Nexus 7 Android Development] TenBelowZero:
Good news, thanks a lot for the new build, for your time and commitment.

As for the kernel, I think it doesn't really matter whether you include stock or franco.

Those of us who prefer a different kernel will flash that one anyway.

For me, the kernel of choice would be m-kernel, but that's just because I got accustomed to it over time.
[Nexus 7 Android Development] steviemch:
Regarding the kernel, I'd personally prefer stock, that way I can flash whatever I want. With Franco you always have to flash stock, then the kernel of your choice which is unnecessary IMO.

Yeah it's not the end of the world, but still a minor annoyance.

sent by neural subspace transceiver node.
[Nexus 7 Android Development] kmcrane:
Stock kernel. I flash M as well.

Sent from my XDA Free mobile app
[Nexus 7 Android Development] sykopompos:
Ahhh, those obnoxious needed changes for the nav ring customization, I remember them all too well and had thought about modifying them out so those commits wouldn't be need.
[Nexus 7 Android Development] GtrCraft:
Believe me, I miss frank on grouper sometimes. All those customizations and conflicts...
[Nexus 7 Android Development] sykopompos:
That's why I never took Frank farther with features beyond the basics.

I just don't like merging features into my code since I don't like dealing with all the headaches and hassles of them.

That's why I teamed up with zephik on chroma before, let him deal with the features and I could continue working on the bottom end of it.

The community in a whole wasn't ready to work with advancing certain things because then you got into the headache of having to work compatibly with other things.

I'll stick with Frank these days because I'm free to do what I want then and users expect it