yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] zephiK:
That's all on Syko to compile you guys a new build. Sorry about that.

Yes they would, assuming that Syko compiles it using ubertc and not gcc.
[Nexus 10 Android Development] jsgraphicart:
Anyone else having WiFi issues? It wasn't like this all the time but lately, my tablet can't seem to find anything on my network. For example, it has a hard time finding my chromecast. I also use perfect viewer to read comics that are on my computer but the connection seems to get lost and my tablet can't see them anymore. Sometimes YouTube just stops in the middle of a video as well. I have internet but things seem to load slower than usual. I know its not my WiFi because my phone is on the same network and it has no issues with any of this. Anyone have any ideas? Maybe I need to flash the latest radios from the 5.1.1 factory image? I will probably try that next. But any other suggestions are welcome.

EDIT: Ok, tablets don't have radios to flash. lol. I'll keep trying other stuff
[Nexus 10 Android Development] AccuNeal:
Tablets do have radios. Here is a link to the N10 binary for Broadcom radios:

https://developers.google.com/android/nexus/drivers#mantalmy47v
[Nexus 10 Android Development] jsgraphicart:
I figure Wi-Fi would be a radio. Just didn't see it in the factory image. Thanks. I'll try this out
[Nexus 10 Android Development] endriuss:
Thank you!!! This is impressive!
[Nexus 10 Android Development] InfinitiGuy:
How would one use these radios?
[Nexus 10 Android Development] jsgraphicart:
After reading more about it, I found the binaries are more for developers. With my issue, I ended up doing a full factory reset with the Google images
[Nexus 10 Android Development] redandr:
Would be great to see the privacy options from other Chroma roms also here for N10 in the next release :)
[Nexus 10 Android Development] aLPaSLaN07:
Did factory reset. Then flashed the zips in the order of OP. When I boot it says "Unfortunetaly setup wizard has stopped" infinitely..

Edit: Appearantly , Gapps package zip was corrupted. Always check MD5 :)
[Nexus 10 Android Development] sl2222:
No 5.1.1 r2 for manta yet huh?
[Nexus 10 Android Development] tathagatab:
For some time now, my battery has been discharging in fits and starts -- staying at one level for some time and then jumping down three or four percentage points at once. I've been seeing this for about the same time I've had this ROM installed.

So is it the ROM, or is it my aging battery? Anyone else here seeing the same?
[Nexus 10 Android Development] tathagatab:
[MENTION=1978554]zephiK[/MENTION] [MENTION=1050103]sykopompos[/MENTION]

Hey guys,

Does LMY48B bring anything new for our device? Are we going to see a release based on that?

Thanks & cheers.
[Nexus 10 Android Development] zephiK:
I haven't been visiting the tablet threads for awhile as I'm done with finals and have been enjoying my time off.

In regards to the state of tablet support on Nexus devices, unfortunately, I will be discontinuing support for the Nexus 10 for the time being.

Sykopompos isn't around and I haven't been able to get in touch with him for almost two weeks now and I have no plans to blind build for Nexus 10.

The Nexus 10 device is quite old and is not being sold. The download counts for Chroma on the Nexus 10 also don't justify the amount of time / resources that is being spent for compiling for the device.

Sometime this week, I will make Chroma's manifest available to the public so anybody can compile Chroma and continue unofficial support for the Nexus 10.

If a user wishes to be a maintainer for Chroma on the Nexus 10, then be my guest and I will update the OP with a link of your unofficial build. I don't have the device so I will need other people to test the unofficial build, the build will also be required to leave Chroma intact the way it is and not include any additional features that is not included with my ROM. The only thing you would be able to change are the device specific commits and proprietary binaries.
[Nexus 10 Android Development] damngood98:
i understand your decision but i do have to disagree about the download counts being insignificant...over 500 is quite surprising...but alas, all good things come to and end, it was just too short lived
[Nexus 10 Android Development] zephiK:
Over 500 for a ROM that hasn't been updated for over a month without any bugs, when you compare the numbers to other devices that are supported (N4/N5/N6).

It is a very small number, not to mention the amount of resources that is used to compile ROMs for other devices. I do this in my spare time and supporting for devices that I don't have any passion towards (no offense to N10) as it was Syko's idea to build for non-N6 is a chore for me. I do this for free so the time we put into leaving our computers on while it's compiling pretty much stops us from doing anything else as it will lag our machines.

I don't have a lot of money so it's not like I can rent/purchase a server to build Chroma compared to the other popular ROMs who can push nightly releases for 5+ devices every night. I'm building this on my local machine, and I don't get many donations (if I do, it's not from N10). At the end of the day, a ROM is just like a business in a way... it's supply meets demand and the demand for N10 isn't here and Sykopompos was the one compiling for N10. I already picked up N4/N5 because Chroma is wanted there by a large enough # of users. I'm not saying that I need donations to build for N10 but tablet development in general just isn't there when we compare it to phones.

If that isn't good enough then I apologize on behalf of Sykopompos on bringing Chroma to the N10 and tablets. It was his idea and I don't want to blame Syko so that wouldn't be fair either. I just hope that opening up the manifest will remedy things up as anyone will be able to compile Chroma. I'll open up the manifest sometime this week when I have the time to update the manifest / organize everything. Anybody who wishes to compile Chroma for N10 can do so and can continue going at it. The ROM base itself will continue being developed on, just the device specific / proprietary binaries / compilation won't be supported by me.

Hopefully someone picks it up, if not then.. best of luck with N10 and other ROMs.
[Nexus 10 Android Development] hawkstwelve:
Thank you for bringing the support that you did to the N10. Chroma is one of the most stable ROMs we got on manta, which ain't a lot, and I can completely understand your disinterest in continuing development without the device or the downloads to support it. That being said, I am thoroughly looking forward to you making your manifest public as I plan on doing my own personal builds for Chroma on the N10 and will share if there is enough demand and everything goes right. I would not share without your consent, of course.

At any rate, thanks to both you and syko for getting this project started for manta!
[Nexus 10 Android Development] sfobrien:
zephiK,

I just recently discovered this ROM. Loaded it up, runs great. Just wanted to say thanks before you moved on.
[Nexus 10 Android Development] zephiK:
Anybody can compile it and share it to other users in this thread, it doesn't matter :)

I won't provide support on how to compile Chroma though, that's all for the user to do. I need to update my sources on the organization repository before I make the manifest public.

If you do build for the N10 and want it added to the OP post. The following conditions would have to be met,

- No alterations of the source code (in other words, don't add features that YOU want into Chroma). The only repositories you're allowed to modify are the device trees and proprietary vendor repositories. If you wish to add something to the source, then ask me. The device specific and vendor repositories are available on the rom git but may be outdated.

- The build must boot and work as intended (obviously)

If you compile a build and share it among the thread then that's fine but if it's to be added to OP then those two conditions must be met
[Nexus 10 Android Development] zephiK:
So it looks like the manifest is good to go and has been compiled successfully by two of my testers.

https://github.com/Chroma-Aosp/chroma_manifest -- have at it and compile a Chroma N10 build for the community :)
[Nexus 10 Android Development] hawkstwelve:
Here is the link for my unofficial, beta Chroma build.

LINK PULLED. New build coming in the next 20 mins with Bluetooth & Sound working.

Bluetooth is not working correctly, or at all really. But I'm 99% sure I know the fix and will have a new build hopefully on Mon/Tues as it's my son's 2nd birthday tomorrow.. Otherwise, completely stock Chroma and I haven't come across anything else not working. That being said, this is beta for the next day or two so let me know of any other issue you come across. I flashed with banks dynamic gapps. Also, all credit goes to zephik and sykopompos for creating/maintaining chroma.
[Nexus 10 Android Development] Nicholas1994:
Sound not working (

Also fc when i try to access sound settings
[Nexus 10 Android Development] hawkstwelve:
Sound and bluetooth fixed in next build. Uploading to AFH now. :good:
[Nexus 10 Android Development] sykopompos:
I was gonna mention the sound part when I saw you compiled it last night because there was a derp in the vendor tree and never got around to fixing it and would just manually add the missing sound files in manually then make otapackage again to make the dat
[Nexus 10 Android Development] hawkstwelve:
Yeah I just ended up using different device/vendor trees than what was on Chroma github. Too lazy last night to add it manually.

---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------

OK, so both bluetooth and sound should be fixed in this build. The only bug I am still seeing is sound settings still force closes. I will take a closer look at that tonight. Other than that, haven't seen any other bugs. Just let me know if you come across any.

https://www.androidfilehost.com/?fid=23991606952612800
[Nexus 10 Android Development] zephiK:
Just throwing it out there if the Sound & notifications setting FCs it's because you're missing a LED notification commit in the overlay. The fix is to add

<!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveBatteryLed">true</bool>

at the bottom of overlay/frameworks/base/core/res/res/values/config.xml in device/samsung/manta/.

I've updated the device specific repository to include this fix, https://github.com/Chroma-Aosp/android_device_samsung_manta/commits/lp5.1 -- update to that device specific tree and then it'll work without FCs.

If enough people confirm that [MENTION=5307852]hawkstwelve[/MENTION] 's unofficial build works other than the FC, I will update OP when he adds the fix that I mentioned above. I don't own a Nexus 10 so I can't test it myself.

Thanks hawk for compiling. And you can use different trees for vendor, they're not updated properly to 5.1.1 -- the ones I'd recommend would be https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/manta
[Nexus 10 Android Development] hawkstwelve:
Thanks for that fix. I have updated my working directory and compiled a new build. From what I can tell bluetooth, sound, and FC's have all been fixed. I will post a link here for everyone once it gets done uploading to AFH. :good:
[Nexus 10 Android Development] stunned:
I don't really use bluetooth but just curious is this solved?
[Nexus 10 Android Development] hawkstwelve:
OK everyone... this build should have EVERYTHING fixed (bluetooth, sound, force close in sound settings). Please just let me know if there is anything else you guys find. As far as syncing with the fitbit, I'm not sure, as I don't have one. It syncs just fine with my Samsung Soundbar if that means anything. Feel free to test it and let me know.

https://www.androidfilehost.com/?fid=23991606952612940
[Nexus 10 Android Development] stunned:
This is pre-rooted now?
[Nexus 10 Android Development] hawkstwelve:
Yes, SuperSU is included in the zip and nothing needs to be changed in developer settings for it to work.
[Nexus 10 Android Development] zephiK:
SuperSU has been added to the ROM for awhile now.

I'll update OP.
[Nexus 10 Android Development] drewski_1:
Thanks. I'll give it a whirl.

Soundbar sounds like regular BT, like connecting to a headset.

BT Low Energy (LE) is another part of BT. It doesn't need to go through the normal pairing process.

I'll let you know how it goes, but as a reference its working fine on Lolipopalooza ROM so maybe something that can be cherry picked?

Sent from my Nexus 10
[Nexus 10 Android Development] stunned:
Everything seems to run fine and smoothly. :good: I don't have any BT devices though to test bluetooth
[Nexus 10 Android Development] bbubelis:
Working as advertised

Thank you for the updated ROM. Everything is functioning as expected.
[Nexus 10 Android Development] sl2222:
Just dirty flashed from the last chroma manta rom. I think it was 4-22

All seems to work except the play store just opens and closes. no FC just opening and closing.

That was with the Banks dynamic L 5-27

Then wiped dalvik and cache and tried flashing a gapps minimal dated 5-04 that was working on the 4-22 rom but got the same result.

So unfortunately I need to do a full wipe I guess.

Much thanks to hawkstwelve for keeping manta alive on chroma!
[Nexus 10 Android Development] stunned:
Yes, I had same problems and had to do a clean install as well.
[Nexus 10 Android Development] shuli81:
Hi [MENTION=1978554]zephiK[/MENTION] and [MENTION=5307852]hawkstwelve[/MENTION]

Thanks for keeping this alive for us.

Is this ROM compatible with Google Web view add-on from tk gapps:

http://xdaforums.com/showthread.php?p=60921686
[Nexus 10 Android Development] hawkstwelve:
No idea as I have never tried to flash those gapps/add-on package. Make a backup and give it a try, that's the best way to figure out if X, Y, Z add-on/package/app works on any ROM.
[Nexus 10 Android Development] zephiK:
You mean Android WebView? Yeah, the ROM has support for Android WebView since the latest build.

https://github.com/Chroma-Aosp/andr...mmit/042b1c8858cafd86257269ce50620b88205fca0e
[Nexus 10 Android Development] tathagatab:
[MENTION=5307852]hawkstwelve[/MENTION]

I tried flashing your ROM, but it failed every time, with the error "could not unmount system; no such partition". Tried this 3 or 4 times, with same result. Had to go back to the previous image. What could be the problem?

I checked the md5, and it's OK.
[Nexus 10 Android Development] hawkstwelve:
It says that during flash but ignore it and continue with flashing gapps and booting back into system. It will boot/work no problem. If it still doesn't boot, grab an adb logcat and let me know.
[Nexus 10 Android Development] goksar:
the actual download link refers to "chroma_manta-ota-2015-05-31(2).zip" - is this a full rom or just an ota update?? thank you!
[Nexus 10 Android Development] endriuss:
This is a full rom but you can use this as an update of previous version o rom as well. I personaly did a dirty flash without any single issue.
[Nexus 10 Android Development] zephiK:
It's always full ROM, there are no incremental otas.
[Nexus 10 Android Development] Izeltokatl:
So I'm pretty sure this may just be my device, but is anyone else getting severe lag from the last few releases? I've done a full wipe and it still comes to a crawl. I have done the ftrim fix but it only helps briefly.
[Nexus 10 Android Development] Sage:
I had a simliar issue had to manually format system... then i could flash. (make sure you have a backup!)
[Nexus 10 Android Development] zephiK:
06/05 stable is out. [MENTION=5307852]hawkstwelve[/MENTION] I'll be updating sources soon.

Edit: updated for 06/05, just update sources & compile :)
[Nexus 10 Android Development] hawkstwelve:
Alright guys, thanks to [MENTION=1978554]zephiK[/MENTION] for updating the sources. I am syncing right now, then I will compile. Should have a build out for you guys later tonight.
[Nexus 10 Android Development] zephiK:
I updated the manifest with the N10 proprietary binaries you used.

[MENTION=5307852]hawkstwelve[/MENTION] please use the official device tree, https://github.com/Chroma-Aosp/android_device_samsung_manta/commits/lp5.1 I reworked it just now.
[Nexus 10 Android Development] hawkstwelve:
[MENTION=1978554]zephiK[/MENTION] I have been, that device tree on github is for a different ROM.

Sorry about not getting this out to you guys last night - ran into a couple issues. All is good now. Latest Chroma build:

Download
[Nexus 10 Android Development] zephiK:
Oh yeah btw, I messed up the manifest. I'll fix it up now. Accidentally put -release as the branch name.

Ahhh, I gotcha. Question does USBOTG work after the commit I added in yesterday?
[Nexus 10 Android Development] hawkstwelve:
Ah yeah I noticed that. Vendor for shamu was giving me issues too. I think the branch "5.1" should be "lp5.1" but I could be wrong. Also, I don't have a USBOTG cable so I couldn't tell you. Will someone chip in and let zephiK know if that works on the latest build?
[Nexus 10 Android Development] zephiK:
Ahh yeah thanks for pointing that out, I'll fix it right now as well. I pushed the new vendors I use for shamu last night and forgot to swap it in the manifest.
[Nexus 10 Android Development] tathagatab:
[MENTION=1978554]zephiK[/MENTION] [MENTION=5307852]hawkstwelve[/MENTION]

Hi,

Thanks for the fine upload. Everything feels snappier, especially the gesture-typing with trails. The new keyboard is a definite improvement. Was it introduced by Google with LMY48B, or is it Chroma-specific? Anyway, it's seriously better than the last one.

To answer your question, yes usb-otg is working out of the box - great work!

But may I suggest an improvement? On a couple of other AOSP-based ROMs, there's a persistent entry showing the mounted device in the drop-down notifications list. The entry can be further expanded downwards to reveal the unmount option. I guess they got the idea from the stickmount app, maybe. It's very convenient.

On Chroma, when I plug in the drive, I get a brief flash of a notification saying "preparing usb storage for mounting" or some such, and then it's gone (too quickly to read). So when removing the device I have to open settings, go to storage, scroll down to the usb section, and click unmount. Or do it manually in the terminal. Might this be changed?

Thanks & regards.
[Nexus 10 Android Development] zephiK:
The updated keyboard was included awhile ago but the Nexus 10 ROM was never updated with the latest Chroma sources. It's from Chroma, all of the Lollipop builds from Google have been minor changes and nothing significant.

This ROM is meant to be minimal and lightweight, the inclusion of USB OTG is a device specific addition so no I won't add a notification that it's preparing. The USBOTG commit is to have support for it, but if you want the full solution then yeah use StickMount.
[Nexus 10 Android Development] drewski_1:
Just got around to backing up and flashing this ROM . . . 6/6 build

Happy to report that BT LE is working AOK and my fitbit syncs with no issues! Great work [MENTION=5307852]hawkstwelve[/MENTION] & [MENTION=1978554]zephiK[/MENTION] :good:

Does Chroma still not play nice with the Alpha Xposed?
[Nexus 10 Android Development] hawkstwelve:
Good to hear everything's working well. As far as alpha xposed, I've honestly never found the use for it with all the features included in ROMs nowadays. But I would say anything alpha is risky business if you want to stay away from bugs.
[Nexus 10 Android Development] Beaster:
I am giving this ROM a try. Coming from OMNI...

Thank you for your work. Will report back if any issues are encounter!
[Nexus 10 Android Development] zephiK:
This thread is so quiet!

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 10 Android Development] tathagatab:
This 06/06 ROM is so good that maybe no one has anything to say.

I can say for myself that the only thing that still irks me a little bit is the initial blip of the display after booting.

And now you say you've made it even cleaner. I'm afraid the thread is going to get quieter still :)
[Nexus 10 Android Development] stunned:
Great!

I read some random G+ comment and got impression that the new build doesn't have extended desktop? I think it is a must for N10 because the device is mainly used in landscape. It gives so much more space for web browsing in Chrome etc.
[Nexus 10 Android Development] UK_Wildcats_Fans:
We know that the N10 is not one of your devices, and we are simply waiting patiently for the builds. We can also follow Chroma development from all the posts (and BS) from the N6 thread. For me personally, as long as my N10 is reasonably stable then I am happy.
[Nexus 10 Android Development] SFG:
Thanks zephik. Enjoying your ROM on both my n6 and n10. Glad there's still development for this perfectly fine tablet.
[Nexus 10 Android Development] zephiK:
Yup its pretty annoying when people come in the thread and not read before posting or simply making demands otherwise they'll go another ROM.

One of the reasons why developers are such stressed people :p

The manifest / sources will be updated for next build (or a build after that) for when the rewrite is more complete.
[Nexus 10 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 10 Android Development] tathagatab:
Thanks!

Can we have a changelog?
[Nexus 10 Android Development] zephiK:
They're in the changelog in OP.
[Nexus 10 Android Development] beekay201:
Hi,

Why am I getting "Storage space running out" and "Make sure you have 250MB free and restart" after flashing this+banks gapps?

Was on KK. Flashed stock LMY47V through flash-all.sh. Flashed TWRP 2.8.6.0. Flashed Chroma+gapps. No user installed apps. Got the above errors.

Any ideas?
[Nexus 10 Android Development] hawkstwelve:
Alright guys I am syncing the sources now and will start a build after. Thanks to zephiK for updating. Hopefully will have a build out to you guys late tonight, if not, tomorrow morning.

[MENTION=1978554]zephiK[/MENTION] Syncing isn't finishing right so I took a look at your manifest. I think the branch name for chroma vendor is off. It should be "lp5.1" instead of "lollipop", I think. Although I tried syncing with that change and it's still stalling out. I'll try and compare more from github to manifest and see if there is anything else that's funky. Understandable after a re-write.
[Nexus 10 Android Development] zephiK:
Ah you're correct, I'll fix up that.

/vendor/chroma should be lp5.1 branch and not on lollipop branch. Let me know if you see anything out of the ordinary.

The lollipop branch is kept for reference purposes.
[Nexus 10 Android Development] tathagatab:
Stock lollipop does that. See if you can find a fix here: http://xdaforums.com/showthread.php?t=3029605
[Nexus 10 Android Development] hawkstwelve:
Something is still causing it to hang. Just not quite sure what it is. I compared the updated repos on github to those in the manifest and didn't see anything that looked off but for some reason I can't get the sync to finish, even after fixing the tcp issue that can sometimes come up. I did notice you host the packages_services_Telecomm on your github now, but manifest was still pulling it from google source code. Not sure if that was intentional or not.

Not quite sure why I can't get it to finish syncing. Just stalls at 99%.
[Nexus 10 Android Development] zephiK:
You're right about Telecomm. Sorry about the mess on my manifest.

[MENTION=5293805]GtrCraft[/MENTION] also tells me that frameworks_av was missing. I forked the folder and it should be good now. I hope.