yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] dibblebill:
I think Dirty Unicorns does, but it's built on an Omni base

Sent from my Nexus 10
[Nexus 10 Android Development] ashwin1234:
Thanks [MENTION=4672837]dibblebill[/MENTION], I decided to reflash your 30th Dec build, now gravity is working fine again. I hope you don't feel offended by my post earlier, It was directed towards the Omni team. You on the other hand, are doing an AWESOME job with this ROM!! Thanks for all the hours you put into this!
[Nexus 10 Android Development] dibblebill:
None taken :)

I'm an advocate of "TRY ALL THE ROMS" until you find one that fits your needs. I'll never be angry someone stops using Omni. Honestly, I was surprised anyone used it as I originally began these builds for just me and decided "ah what the hell, I'll upload it". Right now, repo sync hangs on m7att packages, so I'm not sure what's going on there. Once I figure out and fix that, I'll be able to begin working on something I've been thinking of doing on the side.

Also, I noticed my 0105 build has Apollo. That's been fixed in the next one. *grumpyface*
[Nexus 10 Android Development] Dovigoldberger:
Did anyone add a restricted user successfully? I get setup force closed when I enter into that profile
[Nexus 10 Android Development] cien12:
I am not 100% sure, but is it possible that DSP Manager requires Apollo to work correctly.

Without it, the settings in DSP seems to have no influence.

Edit:

I have installed the apollo separtately. But DSP Manager nontheless does't work system-wide for me. DSP Manager can only manage the sound form apollo with my Nexus 10.

Very strange.

I need a possibillity to adjust the complete system-wide sound of all apps, especially the media transfered by bluetooth to my amp.
[Nexus 10 Android Development] dibblebill:
I'll test it out today.

As for DSP, that's odd as it's a Omni source package. Try Viper4Android

Sent from my HTC One with OmniROM

Edit: Same thing. Then, SystemUI crashes and app permissions for it stop working. I'm at work right now, so in-depth investigation won't happen until tonight.
[Nexus 10 Android Development] cien12:
Very strange.

Even I try (DSP, Viper4Android ...), I'm not able to adjust the Bluetooth Sound. Adjusting the headphone sound works at least with apollo.
[Nexus 10 Android Development] dibblebill:
Even specifically using V4A's Bluetooth and Headset selections?
[Nexus 10 Android Development] cien12:
Yes. I play with all settings for hours.

With the built-in equalizer in Power-Amp I can modify the bluetooth sound.

But with apps like TuneIn or ES (for Network-playback) and DSP or V4A - no chance!

Does it work for you?

Maybe there are limitations to some apps with DSP, but I thought this settings are "system-master-settings"
[Nexus 10 Android Development] dibblebill:
I used to use V4A with my Galaxy Victory and bluetooth in my car, and it made a difference. I'll put some music on my Nexus 10 tonight, and test it on the way to work in the morning.
[Nexus 10 Android Development] cien12:
Oh, thank you very much this will be very nice. If it doesn't work for you or someone else, I can stop troubleshooting ;).

I hope it isn't a big deal for you and it won't take to much time.

This problem isn't a great thing. In any case your Rom is the best I have ever tried!
[Nexus 10 Android Development] dibblebill:
No problem at all

Sent from my HTC One with Tempest
[Nexus 10 Android Development] LuHe:
I just noticed the follwing bug when there are two user accounts:

If the main user has an unlock pattern (or other security) for the lock screen and the secondary user uses the device the unlock pattern of the first user is in the lock screen.

The secondary user sees his own background etc. and must enter the security code of the first user, regardless of his own settings.

If I click on the first user and then back to the other one the correct security mechanism is displayed.

EDIT: Seems to be a bug of Active Display. Works again correctly when AD is disabled.
[Nexus 10 Android Development] bflatmajor:
question

Is this ROM stable enough to used as a daily driver or not yet?
[Nexus 10 Android Development] abdel12345:
My bad deleted thought this was nexus 5 omni

Please press the thanks button if I help you.
[Nexus 10 Android Development] Bingoig11:
Yes it is.

It works great.
[Nexus 10 Android Development] dibblebill:
I hope to have a new build soon. Working out issues that m7att is causing.

Yes, it's stable, also thanks for hte pointers. I have AD disabled and have restricted user issues, I'll try to find out what's going on.
[Nexus 10 Android Development] dibblebill:
Test device: Nexus 10

App Used: Play Music

Result: V4A XHiFi affects playback via speakers with "Phone Speakers" setti g

Car tested: 2012 Volkswagen Jetta TDI Premium w/ Navigation

Apps: Same as above

Result: Headset/Bluetooth V4A settings have no effect, but "Phone Speakers" did.

Sent from my Nexus 10
[Nexus 10 Android Development] cien12:
Thank you very much for your test. So I will test V4A again.

Pity that it don't work complete. It would be nice to have various settings for different speakers.
[Nexus 10 Android Development] mazubo:
For people running this rom for a week or so...how do you find the stability of the multi window feature? Thanks!
[Nexus 10 Android Development] Mr_Jay_jay:
Nothing new!!

Naw I think it was an isolated issue.. I've been using it just to maybe replicate it but nothing. I haven't had any issues so far. like u said multi-window is a bit wonky... but nothing major... I've had nothing new to report, I have a request though is it too hard to add Halo to this? Per app PPI? just asking... tablet it's been great so far!!! I'm loving the multi-window!!!!
[Nexus 10 Android Development] dibblebill:
I'll look into per-app PPI, but from what I'm reading in the Omni forums and threads and discussions, HALO breaks MultiWindow and vice versa.

New build up!

30th October

-Synced latest sources (even though build number says 10/26?)
[Nexus 10 Android Development] scanno:
Did you do a make clean?
[Nexus 10 Android Development] dibblebill:
Nope. I'll probably do another build tonight with a make clean. My desktop's WiFi is giving me strange issues on Ubuntu :crying:
[Nexus 10 Android Development] Mr_Jay_jay:
That's fine I much rather have multi-window than halo.. if per app PPI is possible great, I don't know what else can be added to this, I mean besides the little bugs this rom its awesome!! Thanks for everything!
[Nexus 10 Android Development] AJ Bryant:
You should put the Xposed Installer.apk and GravityBox.apk (module) in your ROM. It's my first time using it and it has a lot of cool features like Expanded Desktop, Pie Controls, Quick Settings Tiles settings, transparency of status bar, etc. Also, you should keep Apex Launcher.
[Nexus 10 Android Development] dibblebill:
Apex Launcher is on possibly indefinite hold. What's going on is every time you flash the zip, unless you export your Apex settings, it'll reset your Apex settings. Even if you back them up, it'll forget and lose your widgets. Until I can figure out how to write the backup scripts (still learning) to save those, its on indefinite hold unless I can figure out how to convince it to put it in /data/app/

I don't use XPosed but I'll look into what it takes to include it in the ROM. Right now, I just got an ethernet extender since Ubuntu hates my wireless card with a passion- recyncing for a new 4.3 build and sitting on my hands waiting for Android 4.4 blobs for the manta, so I can build it with KitKat.

My repo's imploded when I added PPI, so for now, I'll keep that on ab ack burner- it seems to hate multiwindow.
[Nexus 10 Android Development] abdel12345:
[MENTION=4672837]dibblebill[/MENTION] can u check ur pm. thanks.
[Nexus 10 Android Development] dibblebill:
Responded. Feel free to PM me again if you want more details about other ROM's I've tried.

3rd November

-Synced latest sources, clean build
[Nexus 10 Android Development] AJ Bryant:
For as long as I've used Apex, I've notice that it never restores widgets when Restoring desktop data so I think that's normal. But I'll stop bothering you with requests because I know this kind of stuff isn't easy. I'm struggling to build a clean music player app (Apollo alternative) in Eclipse.

P.S. If anyone knows about building apps (specifically music players), help would be appreciated. :)
[Nexus 10 Android Development] dibblebill:
I don't know much about building apps from scratch, so you might want to ask in the developer forum. As far as requests, I'm an Apex lover. Its a problem I'm revisiting- I'm examining other ROM's that haveb ackup scripts, and I will eventually figure it out and get it working. My primary task atm is getting 4.4 running on Manta.
[Nexus 10 Android Development] dibblebill:
5th November

-Synced latest sources

-Last 4.3 build, for better or for worse attempting to build 4.4 for Manta
[Nexus 10 Android Development] Mr_Jay_jay:
Hey [MENTION=4672837]dibblebill[/MENTION] will u be keeping the multi-window on 4.4??
[Nexus 10 Android Development] dibblebill:
I'll be trying, as well as trying again to get Apex pre-installed. Per-App PPI seems to conflict entirely with multi-window. I had a build working, but as soon as I re-added Side-By-Side Apps (more accurate of a name than MultiWindow), it stopped building again.

Right now, I've got the 4.4 sources, but its not building due to lack of kernel. Additionally, SlimKat's kernel seems to have some deep incompatibility in which it will not build or sync with that when I experimented. So just going to have to wait. For now, my latest build works and seems mostly stable so it may be a week or two until I have a new build up.
[Nexus 10 Android Development] dibblebill:
If you get that built, I'll test it for you :) Hell, if I like it, I might even swap APollo for it (with your permission)
[Nexus 10 Android Development] dibblebill:
Building a 4.4 ROM on 4.3 binaries and kernel is just too hacky and unreliable for me, in my opinion, both in build and usage. I'll be not building any more in 4.3 or 4.4 until we get a stock 4.4 kernel source and binaries from Samsung/Google, and then I'll move the project forward with a new 4.4 build.

It's not dead or forgotten. ;)
[Nexus 10 Android Development] cwalker29:
I flash this rom and lost root. Tried to install supersu so far nothing. Why did I lose root?
[Nexus 10 Android Development] dibblebill:
Which nightly did you flash?

Sent from my Nexus 10
[Nexus 10 Android Development] cwalker29:
4.3.1-20131105-manta-tempest
[Nexus 10 Android Development] dibblebill:
I normally flash the SuperSU 2.6 package from recovery... I'll test this with a stock kernel in a bit and test and get back to you
[Nexus 10 Android Development] newellj79:
Omni gerrit question... When things become verified does that mean they will appear in the next nightly?
[Nexus 10 Android Development] _Raziel666:
They have to appear here in order to be in the next nightly: https://gerrit.omnirom.org/#/q/status:merged,n,z

(and of course, they have to appear there before the nightlies start building)
[Nexus 10 Android Development] cien12:
Very strange.

I installed V4A second time and played around with the "Phone Speaker" settings.

As you wrote already, this setting impact to the bluetooth sound also.

After this I tried again the bluetooth settings, and from now this separate setting works as well.

I don't know why it works - but I'm satisfied.

The Omnirom DSP Manager still doesn't work.
[Nexus 10 Android Development] dibblebill:
Good to know. Just for reference's sake, what kind of car are you using it with, if your Bluetooth system in the car is stock? If its not stock, what type of stereo system?

First off, I'd like to apologize for the slowing down of the builds. I've just been real busy lately. Plan to get back to a regulary schedule (more than 1 build per week). Linaro for Omni is still a no-go but I might be able to work it out. Been trying to look through Linaro's source and figure out WHAT exactly it does.
[Nexus 10 Android Development] cien12:
I don't use it in car.

I use a Logitech bluetooth transmitter (see link below) to connect the N10 wireless to my home amplifier.

I think it has the simplest SBC A2DP stereo protocol (because of the cheap price), but I have no technical specifications.

http://www.amazon.com/Logitech-Wireless-Speaker-Adapter-Bluetooth/dp/B004VM1T5S/ref=sr_1_6?ie=UTF8&qid=1389626458&sr=8-6&keywords=bluetooth+transmitter
[Nexus 10 Android Development] dibblebill:
That's good to know. Just trying to get an idea of what's going on

Sent from my HTC One with OmniROM Tempest
[Nexus 10 Android Development] AJ Bryant:
Can you please make a minimal variant of OmniROM with MultiWindow support? I ask this because I've downloaded the Omni nightly 1/15/2014 for Manta and I really enjoy it but it lacks multi window (needs to be cherry picked I guess). Not everyone wants/needs the extra apps that come with your Omni. No disrespect intended. Stock Omni with multiwindow support would be sweet.
[Nexus 10 Android Development] scanno:
If you want i can post my weekly builds. I am including multi-window in my builds. Oh and my build is the standard omni build with the multi-window commit cherry picked

Verstuurd vanaf mijn Nexus 10 met Tapatalk
[Nexus 10 Android Development] AJ Bryant:
Alright, I'll give that a try.

I realized that dibblebill's Omni uses Aroma and I have options of what I want to install. Sorry for the little rant dibblebill lol. Good work, just not familiar with Aroma.
[Nexus 10 Android Development] dibblebill:
Give scanno's a shot, if you want, or check out AROMA. In the second or third install option, select "Category 4" instead of "Category 5".

No offense taken at ALL. I merely included apps that I normally have to reinstall on every nightly update, and since some wanted a baseline w/o them, I included only core enhancements like 3DSammy's scripts with the base install. This nightly still has Apollo, but that's due to my oversight. I'm working on a new nightly tonight, but mostly just Omni syncs since they've added features.
[Nexus 10 Android Development] scanno:
Here you are: http://www.mediafire.com/?d2v2o2n63y63oxb

Verstuurd vanaf mijn Xperia T met Tapatalk
[Nexus 10 Android Development] saryu:
Hi, i flashed this ROM yesterday on my nexus 10 and it stuck on google logo.

I've wiped data, cache, everything need to be done before installing new ROM

Any clue?
[Nexus 10 Android Development] dibblebill:
Did you factory reset, too? What TWRP version are you using? That's unusual.

Currently assembling AROMA for my newest build, solved my repository issues. Expect it tonight or early tomorrow (for me, anyway- EST)
[Nexus 10 Android Development] dibblebill:
16th January

-All sources updated

-MultiWindow cherrypicked to latest

-Apollo removed (for real)
[Nexus 10 Android Development] scanno:
Just for your information. If you want to enable Omni Torch, I have uploaded a commit to gerrit that includes OmniTorch and adds the needed overlay : https://gerrit.omnirom.org/#/c/4889/

Verstuurd vanaf mijn Xperia T met Tapatalk
[Nexus 10 Android Development] dibblebill:
I'll cherry-pick that on my next build. Spotted AROMA errors in both the manta and m7att builds I want to fix, as well as figure out why it says the build date is still 0105 in settings.
[Nexus 10 Android Development] scanno:
Do you make clean builds or incremental builds?

Verstuurd vanaf mijn Xperia T met Tapatalk
[Nexus 10 Android Development] dibblebill:
I normally clean out the out directory, but this time I did a brunch over my preexisting 'out' folder.
[Nexus 10 Android Development] scanno:
When I have such a problem, it is usually because of not doing a make clean.

Verstuurd vanaf mijn Xperia T met Tapatalk
[Nexus 10 Android Development] dibblebill:
I'll do that tonight. I was able to repo sync and cherrypick that commit before I left for work, but I can't afford the power bill to run the desktop all day ;) I'll have it build tonight
[Nexus 10 Android Development] bflatmajor:
possible bug

I enabled the functionality to display the network speed indicator in the status bar and initially it worked fine.

I turned the tablet off for the night and turned it back on in the morning and the network speed indicator does not appear.

The box is checked to display it but its not showing in the status bar.
[Nexus 10 Android Development] dibblebill:
Try disabling/re-enabling it. I have this issue on my HTC One as well.
[Nexus 10 Android Development] bflatmajor:
Did that and still nothing.
[Nexus 10 Android Development] dibblebill:
Can you get me a logcat? I'll be home to look into it later

Sent from my HTC One with OmniROM Tempest
[Nexus 10 Android Development] newellj79:
Anybody notice any new features? None that I see, but still stable as hell!
[Nexus 10 Android Development] dibblebill:
I looked and looked on both devices and found none- I normally post them in my "new build" announcements- new features I find.
[Nexus 10 Android Development] dibblebill:
17th January

-All sources synced

-Added OmniTorch to Manta

-Apollo removed (FINALLY)
[Nexus 10 Android Development] saryu:
turns out my recovery is outdated.. i'm sorry to trouble you, it all good and run perfectly now.. Thanks.
[Nexus 10 Android Development] dibblebill:
No trouble at all. That's what I'm here for :) the direct TV guy. Did changing the SELinux setting work?

Sent from my HTC One with OmniROM Tempest
[Nexus 10 Android Development] 3DSammy:
dibblebill,

See this interesting development with V4A. It is an easy addition to Tempest.

AuSSiELaMbChOpS - "Once the addon.d script is installed the v4a driver and audio conf settings will be retained when flashing a rom update etc"

The file is called "91-v4a.sh" (see attachment). The attachment needs to be unzipped. Sorry but ".sh" files are invalid as attachements.

I manually added the script file to your the 0117 Tempest and reflashed per normal (ROM and Gapps). Flashing included dalvik/cache wipe and V4A had already been installed/configured.

The first time you flash Tempest, "91-v4a.sh" gets added to "/system/addon.d" but does not get run so you still need to install the V4A driver. This is because of the bug in the addon.d backup/restore that you and I have previously discussed. The second time you flash the V4A driver and settings are preserved saving the manual install and extra reboot.

If a user manually adds the "91-v4a.sh" script to their "/system/addon.d" directory they will save themselves the slight hassle of doing/waiting for a second flash.

Currently with the Aroma settings restore capability of Tempest and Famigo, when I flash updates, all I need to do after a rebooting is install the V4A driver then reboot again. It would be nice to eliminate the extra reboot. Not a huge deal but an improvement none the less.

Just a thought.
[Nexus 10 Android Development] cien12:
+1

This would be nice!
[Nexus 10 Android Development] dibblebill:
I agree. I'll implement it in my next build

Sent from my HTC One with OmniROM Tempest
[Nexus 10 Android Development] 3DSammy:
FYI - V4A has just issued new release ViPER4Android FX: v2.3.2.0
[Nexus 10 Android Development] AJ Bryant:
What is this 'William@Droidbuilder' kernel that you use? It has amazing battery life (though the N10 charges extra slow). Do you have a 2012 Nexus 7 version of this kernel?
[Nexus 10 Android Development] dibblebill:
Stock OmniROM kernel (for now ;) )

Sent from my Nexus 10
[Nexus 10 Android Development] 3DSammy:
A couple of things:

1) SuperSu has a new release v1.91 (changelog)

2) Here is a different addon.d script that restores the V4A driver and *.conf files between ROM updates. It is also by a different dev. This one is a more complex script, but includes support for multiple versions of V4A but more significantly adds XHiFi support. dt192: ViPER4Android and XHiFi backup and restore script. I tested it with the last Tempest release and it works as advertised. I would use this one instead of the first one I posted.

I previously stated that the scripts preserved V4A settings but I was wrong it is the related *.conf files that are restored. Your V4A settings (profiles) are in user data storage and were never being deleted during a flash update.

---------- Post added at 10:21 AM ---------- Previous post was at 10:04 AM ----------

Just a few general questions for Tempest users.

1) Do you use the "Multi-View" feature that's included with Tempest?

a) Never

b) At least once a week

c) Everyday

2) Is Tempest your daily driver and if so why?

I'm curious as I moved to this ROM from "4.3.1 Purity/Trintity Ten" because it was 4.4.x OMNI based and I was interested in OMNI's feature plans specifically Multi-View and Multi-workspace. Now that Tempest has become my daily driver, I've only used "Multi-View" to prove that it worked but the rock solid stability of this ROM and dibblebill's openess to including new features keeps me here.
[Nexus 10 Android Development] anhtin:
no, i changed it, worked for the first time, then happened again. So i decied to uninstall in once and for all!! :P
[Nexus 10 Android Development] 3DSammy:
Those of you that use Onandroid to perform nandroid backups, may be interested in this /system/addon.d script which preserves Onandroid and its support files across a ROM flash update.

With a rooted device and a file browser with R/W access to "/system" you can manually add the script to "/system/addon.d". For details see: "Preserve Onandroid across a ROM flash update script".

With this script and the similar one for V4A I no longer need to remember do any manual activities after updating Tempest. I am not suggesting that this script be added to Tempest as I have no idea how many users have Onandroid installed or use apps such as OBackup that rely on Onandroid.
[Nexus 10 Android Development] dibblebill:
I almost NEVER use MultiView myself :D Anyone else see the new Omniblog re:Split Screen? I'm excited. That being said, expect a new build shortly with updated scripts and (hopefully) I'll track down more of these pesky typo's in the AROMA menus... Also updated side-apps. Still working on my side experiment, it keeps breaking things.
[Nexus 10 Android Development] newellj79:
I'm excited to try the new multi window to. I may a run a build for one to play with tomorrow unless u beat me to it. Also I know u were trying to get omnibus to build with linaro. Maybe u could talk to the Dev of this ROM, he has it running flawlessly.

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

[ROM] [4.4.2] OmniMetal [01-11-2014] (Linaro Omni rom)
[Nexus 10 Android Development] dibblebill:
Expect a new build in 2-3 days. I want to see if a new version of SplitView drops, and to try to get Linaro running.
[Nexus 10 Android Development] mazubo:
Awesome! Can't wait :D
[Nexus 10 Android Development] maxal:
+1
[Nexus 10 Android Development] wwwpuntoit:
Linaro ! Linaro! Linaro!
[Nexus 10 Android Development] harvey186:
yes, we all want it, and I think dibblebill will do his very best to release a new version soon:)
[Nexus 10 Android Development] dibblebill:
Build is compiling now. Gotta finish this and my m7att build (gotta have the new stuff on my phone, too ;) ). No Linaro this time, but I'll be focusing my Space Engineers and Skyrim time this week instead ong etting Linaro working. I didn't get a PM back from the other guy so I'll work it out on my own as well as figure out how to get my damn github repo's to commit... I'd like to be able to post code i modify to my own repo's.
[Nexus 10 Android Development] dibblebill:
26th January

-Updated V4A, SuperSU

-Added V4A driver preservation scripts

-Updated latest Omni sources

-Updated MultiWindow patches
[Nexus 10 Android Development] Terry.666:
Coming from 4.2.2 do I have to do something specific before I flash the ROM?

Like change bootloader or something, as I did in my SGS4?
[Nexus 10 Android Development] dibblebill:
Make sure you have the latest TWRP or CWM recovery.

Sent from my HTC One with OmniROM Tempest
[Nexus 10 Android Development] Terry.666:
THANK YOU!

I will... Just finished d/l the ROM...:laugh: