yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
Btw omni build for toro is up

they do have some features ahead of cm but they are also behind in a lot too, also I highly suggest flashing a different kernel (the stock one is kinda slow)

You will also need to flash supersu since it does not come prerooted

Enjoy :)

Omnirom-toro-test
[Samsung Galaxy Nexus] justen7723:
I think you need to change Google search.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] Txwolf1980:
Downloading now, thanks
[Samsung Galaxy Nexus] cujo6801:
Any navbar mods ?

Like in cMetal..

Its a must for me

sent from the DOG pound
[Samsung Galaxy Nexus] Txwolf1980:
The n7 2013 doesn't have any, yet. Exposed will let you use them, with gravity box, though.
[Samsung Galaxy Nexus] cujo6801:
Thanks....

Love me some exposed...

sent from the DOG pound
[Samsung Galaxy Nexus] metalspring:
nope, that is one thing they are missing

But they do have active display, native screen recording (hold volume up and power buttons to start and stop)

plus network speed indicator, memory (ram) circle indicator and a few other goodies

However google sign in and mobile network settings do not work properly (mobile network settings has the same issue the last cm build did)
[Samsung Galaxy Nexus] snowcraig:
I tried that, can't seem to make it work. I haven't had much luck with x posed.
[Samsung Galaxy Nexus] metalspring:
Btw, I think navbar customization will be possible in next build... the commits are in gerrit, just not merged

Remember the omni rom build now is just a test build (try to test as much as you can :P)

Also, to help decide if building omni rom would be better, feel free to look through their gerrit for things that could possibly be added in

(if you dont get what some commits do, dont worry about them lol)

Just look under the open commits

https://gerrit.omnirom.org/#/q/status:open+branch:android-4.4,n,z
[Samsung Galaxy Nexus] Cyrix2k:
Has anyone else had issues with the panoramic picture feature? It takes a panorama just fine, but the camera displays a black/blank screen when I select it making it impossible to know what you're capturing. I'm running the cMetal-11-20131202-Linaro-fixed-toro 4.4 build.
[Samsung Galaxy Nexus] jrk190:
Sweet! With mobile network, active display, and multi window, I'll be set. Does it have pocket mode like carbon though? I've never used omni before.
[Samsung Galaxy Nexus] metalspring:
unfortunately that is one of the issues still left to fix on 4.4 for the gnex
[Samsung Galaxy Nexus] jrk190:
Followed you on github! When I have free time I'll brush up on my development skills and see if I can help contribute!
[Samsung Galaxy Nexus] metalspring:
Lol, I dont use github that much since I could never figure out how to get my sources to track upstream but the kernel tuna, device tuna, device toro and device toroplus should be 99% set up to work with omni rom (the only things that could really be added are the rest of the repos needed to build anything for the gnex)
[Samsung Galaxy Nexus] justen7723:
I had to reinstall busybox to get xposed to work. Are u installing the xposed beta? And make sure you reboot in between EVERYTHING you do with xposed.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] snowcraig:
I got it, I started over, rebooted after each step basically, and now I have auto-rotate, fricking sweet!
[Samsung Galaxy Nexus] misterk267:
Nova launcher supports that feature I believe.
[Samsung Galaxy Nexus] Txwolf1980:
So far, the only issue I've seen is the whole having to reboot to get data, after initial boot. That, and the data issue already mentioned.

I am showing pocket mode on the active notifications. But,as metalspring indicated, it seems to be nonfunctional. I'm restoring apps now, so I'll be able to see if there are any conflicts on native, then xposed

Edit. Restored my apps, and I'm getting serious transition and opening lag, on both stock launcher and action.

Once I get into the app itself, it smooths out just fine.

Anyone else getting this one?
[Samsung Galaxy Nexus] klobkelosh:
This fixes panorama on other gnex builds: http://d-h.st/GB2
[Samsung Galaxy Nexus] Cyrix2k:
That fixed it, thanks!

And thanks to the developer for this great rom! It's been running smoothly & trouble free aside from the pano problems.
[Samsung Galaxy Nexus] jbr05ki:
using Voice+ i'm getting sms in triplicates. Also, is there a way to have sms sent with my phone number and not my google Voice number but retain the back up aspect of Google Voice? Thanks!
[Samsung Galaxy Nexus] elliot2112:
Is the askp kernel that comes with the ROM the same as the one linked in op?
[Samsung Galaxy Nexus] metalspring:
Try going into developer settings and changing the default animation scales (all 3 of them) to .5 or .75, for some reason google made the 1x super slow lol

You mean in the cm rom? The latest cm rom I built uses askp milestone 1 (codename Forza)

In the omni rom build its just the cm kernel lol
[Samsung Galaxy Nexus] Txwolf1980:
That was the first thing I tried.

It was phase beam that was doing it. I changed the gradient to green.

I clean flashed, and set everything back up, one thing at a time. The last was wallpaper (which I didn't catch, because I changed it in the middle of setting other crap up). As soon as I did, the phone went completely glitchy. Changing it back to a static, it fixed itself
[Samsung Galaxy Nexus] metalspring:
Hmm, I know exactly what the issue is then...

There was one change that involved the phasebeam wallpaper scrolling that needed to be taken out since it relied on a cm commit that omni rom didnt have

It even specifically said it disabled phasebeam scrolling because it caused lag on the gnex lol

However, 1 I didnt think it would be that bad and 2 I needed to keep this as close to 100% stock omni source for a proper test

It should be a relatively easy fix for future builds
[Samsung Galaxy Nexus] pattyboi:):
hmm...interesting,....you say future builds..are we going to see "cOmni" ?;)
[Samsung Galaxy Nexus] Txwolf1980:
So, does this mean you're looking seriously at building it on a nightly (ish) basis? If so, have you made a decision on maintainer vs going unofficial?

Side observation. I just got off the phone, and realized that I lost days during call (a la early builds). I'm assuming you've already run into this; but I thought I'd throw it out, just in case.
[Samsung Galaxy Nexus] slosrtnick:
Does anybody have a link to supersu flashable zip for omni ROM version? I don't want to flash the wrong one.

Thanks

Nick
[Samsung Galaxy Nexus] justen7723:
http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jrk190:
Hey Metal, I'm trying to get into development... I'll need to set up the repos and download the source when I get home, but I'd love to help you develop. I'm just learning though, so your expertise is appreciated.
[Samsung Galaxy Nexus] metalspring:
It depends, the one thing I dont like about omni rom is they dont have a lot of features in open commits (basically testing phases)

I actually like doing cherry picks lol but it also means they might not have many more features coming up for awhile

I'm still testing other sources too, like right now I have vanir source just about ready to try a build, plus I have a few things set up in preparation for testing carbon rom
[Samsung Galaxy Nexus] metalspring:
It would be hard to do my builds as I have no idea how to get my sources to track upstream so keeping them updated on github would be tough

If you wanted to just try building though, you could ask about being the maintainer for omni rom for toro and toroplus (device sources dont usually update all that often and the ones I have on github are all set up for omni rom, although you might need to make a couple easy changes)
[Samsung Galaxy Nexus] MBQ_:
git remote add <remote name> <remote url>

(git fetch cm https://github.com/CyanogenMod/android_packages_apps_Settings)

git fetch <remote name>

(git fetch cm)

git merge <branch>/<local branch>

(git merge cm-11.0/4.4)

git push origin <local branch>

(git push origin 4.4)

:)
[Samsung Galaxy Nexus] metalspring:
Thanks, now I know why most rom devs dont put up all their source on github... that would be a ton of work for every single repo lol

Btw, any idea why vanir hasnt merged the commit to fix the webview graphics yet? seems odd they just skip over something like that

http://review.cyanogenmod.org/#/c/54291/

speaking of which I did notice something interesting they were working on in omni rom gerrit- it looks like they are trying to find a way to force the old webview as an alternative to the chromium one
[Samsung Galaxy Nexus] Txwolf1980:
To what end?
[Samsung Galaxy Nexus] metalspring:
You mean being able to use the old webview instead? It should help with the lag in certain apps that rely on webview like the aosp browser

Although the graphical glitches might be fixed with the chromium webview (the new one in 4.4) the fix causes lag on our phones

(try comparing aosp browser performance on 4.4 vs 4.3)
[Samsung Galaxy Nexus] metalspring:
btw, I'm doing a vanir build now with the commit to fix the browser graphical errors now

However considering I'm using linaro toolchain and the stock optimization vanir uses is -O3, I have a feeling it will error out pretty quickly or things will break, but its worth a try lol

Although, since they have been known to use linaro in the past they might already have all the patches needed for it to work (cross your fingers lol)
[Samsung Galaxy Nexus] Txwolf1980:
OK. I hadn't noticed, since I'm generally on chrome, beyond opening browser long enough to sign in, and making sure it works.

I'm guessing hacking the old webview to work us more efficient than trying to optimize the chromium webview?
[Samsung Galaxy Nexus] fen0m:
The only browser I can get to work without glitches on 4.4 vanir is firefox, but it's worth it for the performance and battery life in getting on vanirs kernel.

Also art is broken still on vanir.
[Samsung Galaxy Nexus] metalspring:
I did try telling them that the 4.8 toolchains broke ART but oh well lol

also the glitches are because they are missing the commit to fix it (read a few posts above)

Both should be fixed in my build if i can get it to compile
[Samsung Galaxy Nexus] ABN85:
Any chance you could add custom carrier labels? Saw in the Gummy 4.4 thread that they have it. I know it's not a big deal but I hate seeing Verizon Wireless on my phone.

Also, is it too much to hope that immersive mode will disappear and expanded desktop with PIE will make a comeback?

Awesome work on this ROM. Can't believe how smooth it is.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] execute_method:
I too want pie back. Operation is a fluid motion vs. slide & tap with immersive mode. I refuse to use it.
[Samsung Galaxy Nexus] AirBoss24K:
This is the first 4.4 ROM I haven't experienced random reboots or freezes on. Notably, in the last 24 hours, Google Search crashed out of nowhere maybe 3 or 4 times (most of these in the first few hours, probably due to setup), but this is greatly preferred over a reboot or having to pull the battery because it just literally starts back up again within seconds.

Other than that, everything runs smoothly, I get a lock with GPS, and have no complaints about the battery life. Today I was off the charger for roughly 15 hours. Racked up 3 hours of screen time and an hour of talk time on my extended 3800mAh battery. :highfive: I'm a juice junkie. Even considering a larger battery I saw on Amazon recently lol.

Thanks!

Oh, and notably I'm looking forward to that fix for webview being implemented! Those black boxes are avoidable, but it would be nice not having to worry about them.
[Samsung Galaxy Nexus] metalspring:
I will definitely get that cherry picked for todays build lol
[Samsung Galaxy Nexus] metalspring:
I did try github but cant quite figure it out :P

But anyway those 2 directories I have are exactly the same as CM, most of what i've changed is in the kernel (switch to dhackers kernel + linaro build fixes), the prebuilts/gcc/linux-x86/arm/ (replace aosp toolchains in favor of linaro ones) and the /build directory (mostly cflags for more optimization, and to point to linaro toolchains)

And of course the cherry picks lol

speaking of github, trying to get it worked mucked up my repo so i have to resync a bunch to fix it so it will be awhile before I can get a new build up (still later today though)

On another note, I plan on looking into these sabermod toolchains i've been hearing about

I see them included in a lot of roms but cant find any real info on them :(
[Samsung Galaxy Nexus] jonstrong:
Apophis9283 has been using sabermod building his unofficial AOKP roms, and would likely share info with you. Was on XDA until recently. Now on droid-hive:

http://droid-hive.com/index.php?/topic/2385-[Rom]-[Toro]-[Unofficial-Aokp]-[Sabermod-4.9-&--03-Optimizations]-[11.16.13]-[4.3.1]
[Samsung Galaxy Nexus] jsgraphicart:
I really hope it does. Good news to wake up too. :good:
[Samsung Galaxy Nexus] justen7723:
It fixes it.... I dirty flashed dhackers 11/21 build and stock browser works great, but the downside is dhackers build still breaks root with ART enabled so I lost root for now.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jsgraphicart:
Good news (other than your loss of root). I cant wait for metalspring to pull that from CM. Its the one thing keeping me from using Google now to search for anything.
[Samsung Galaxy Nexus] Enter The Nexus:
Thank you based Metalspring.
[Samsung Galaxy Nexus] ironfisted:
[MENTION=4328678]metalspring[/MENTION] idk if anyone has noticed but WiFi needs to be toggled or need to go into WiFi menu to reconnect to WiFi after going out of range. I thought it was a build.prop edit to fix but unsure.
[Samsung Galaxy Nexus] justen7723:
Ya I'm not to worried about it. I could flash supersu, update the binary, blah blah. but I'll just wait for today and dirty flash and be all set after that.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] jsgraphicart:
I'll check again when I am connected to a wifi connection. But I dont remember having this issue.
[Samsung Galaxy Nexus] metalspring:
I got some info on it from tiny4579, i guess its at least closer to aosp toolchain so maybe using it will allow the build to be more optimized than normal but still not break ART

Next build will use sabermod 4.7 gcc (if it doesnt need a ton of extras to work) as a test

so if anyone clean flashes, try enabling ART to see if it will work then

Still syncing back up

trying to make it go as fast as possible (hello repo sync -f -j32 lol)

going to give an estimate of getting a build out around 3-4pm eastern time (my pc takes about 3 hours for a full clean build)
[Samsung Galaxy Nexus] t1.8matt:
I've been having this problem on CM11 build also. Not a big deal though since all you have to do is open Wi-Fi settings.
[Samsung Galaxy Nexus] thetakerfan:
Same. I didn't seem to have the problem on the AOSP ROMS but most have moved over to CM and the ones I've tried all seem to do it. I remember it having earlier (in 4.2 or 4.3) as well and eventually being fixed, just dont remember the details.
[Samsung Galaxy Nexus] jsgraphicart:
Me, at work, patiently waiting for the next build... :)
[Samsung Galaxy Nexus] palosjr:
You and I both...
[Samsung Galaxy Nexus] metalspring:
lol, might be awhile...

while repo and git are great normally they can be a real pain in the @$$ if you do something to mess it up

Trying to get it fixed and synced up but now my wifi is having issues so I'm stuck tethering my phone for internet (and weak 4g here)

(note to self, make sure to copy entire working directory somewhere as a backup)
[Samsung Galaxy Nexus] MBQ_:
[MENTION=4328678]metalspring[/MENTION]

Create a repo 'device_samsung_tuna'

open up your terminal, cd to wherever

git clone github.com/yourUsername/theRepository.git

Transfer the files over from your folder (don't copy the .git folder into the cloned repo

git add -A .

git commit -am "Your commit message with quotes"

git branch newBranch

git push origin newBranch

That should do it. :)
[Samsung Galaxy Nexus] jsgraphicart:
One of the other devs here found this thread in the Nexus 5 forums and said it worked for the Galaxy Nexus. It replaces the stock dialer with the google dialer. If anyone is curious enough to try it out, here is the link:

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

I havent tried it out yet but I'm going to in a bit. Its a flashable zip but all it contains is 3 apk files. I may just do it put them where they need to go manually. I'll report back.

WARNING: The thread says if it doesnt work, you may have to wipe data due to multiple phone force closing notifications. May want to backup first.

EDIT: Just flashed it and didnt work. I'm going to try and manually move them to where they need to go now.
[Samsung Galaxy Nexus] Sheetzie03:
It worked fine for me

Make sure you used deodexed

I tried odexed first and it didn't work until I flashed deo

♦ToroNex-KK'd
[Samsung Galaxy Nexus] ABN85:
Or if there were a way to choose between immersive mode and expanded w/PIE to make everyone happy it would be great. For me PIE is so much simpler and better looking. Even if something like LMT Launcher works with immersive mode, it would do me no good cuz I like my PIE at the bottom my screen.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rubber soul:
What do you mean by "fix for mobile network settings for toro?" Does this mean there are no data dropout issues with this ROM that seem to effect 4.3 builds?
[Samsung Galaxy Nexus] execute_method:
AFAIK, the fix you speak of is for proper network mode setting when switching from 3g to lte in the settings menu.

It does not address the radio issues that have been present since 4.3.I live in a low lte saturation area and frequently jump from lte to evdo and often to affiliate towers. I can attest with great certainty that there ARE still radio issues that will likely never be fixed, as Verizon likely won't release a radio update.

I will also say that those in lte saturated areas will probably say they have no problems, because of probability. They usually jump lte to lte, which works fine, and may occasionally jump lte to 3g, which works sometimes.

Hope that helps.
[Samsung Galaxy Nexus] rubber soul:
Thanks a bunch for the clarification. I guess I'll go to CM10.1 or something because these signal drops are really messing with my day-to-day usage of the phone.
[Samsung Galaxy Nexus] execute_method:
Yeah, I know what you mean. If you're dead set on sticking with 4.2, you should try bigbrother1984's rubik rom. It's available on goo.im and is a very nicely optimized build of pa. I've been considering going back to it...
[Samsung Galaxy Nexus] ABN85:
I drive a truck in the oilfields of South Texas, a place where AT&T is king and Verizon has little to no coverage in most areas except for when I'm lucky enough to get up to San Antonio and get 4G. 4.3 gave me serious data problems, wouldn't switch over, had to reboot to regain signal or would just drop signal in good coverage areas for no reason. Every 4.3.1 ROM I tried didn't have that problem. And this 4.4 ROM (the only one I've tried) doesn't have problems either. The data is better on this ROM than on 4.3.1 for me. I drop signal where I should, pick it back up where I should without a reboot and switch between 1X/3G/4G with no problems.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] execute_method:
What radios are you using. Even after updating my prl I have trouble with 3g/4g transitions on EVERY rom I've tried from 4.3 onward. Although I definitely agree that it's gotten a bit better with 4.4, otherwise I would have gone back to 4.2. I especially have issues on affiliate towers. I've tried a few different radios and when I went to 4.4, I even did a full factory restore.

Unfortunately, your case is not the same for all of us. It could be towers, it could be hardware differences (it's been suspected before that the gnex had some hardware differences even within the same rev.), or something different altogether.

I'll try to get a log next time it happens, which for me is every day in certain spots during my commute.
[Samsung Galaxy Nexus] Meltdown03:
After syncing the repo for Omni, what is the next step to building it since they don't have toro as a device. I'm new at building so take it slow or to PM if necessary. Lol.. According to their tutorial, I have to fork from another build.
[Samsung Galaxy Nexus] staticx57:
Maybe it has to do with how the 3G TLE switch is a one way affair. Currently stuck on 3G only, won't toggle back to lte
[Samsung Galaxy Nexus] ABN85:
I can't remember the exact version number of the radios, they're the ones that come in the latest factory image. I've never manually updated the PRL on this phone. The only time I ever have was when I called customer support for my Thunderbolt with data issues, the rep told me to dial *228 and it fried my SIM card and I had to go get another one. The rep at the store told me never to do that on a 4G phone.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] justen7723:
Just check about phone, baseband version. Latest is fk01/fk02.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] ABN85:
Yep, those are the ones I'm running.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] execute_method:
Same radios here. Also, as far as an updated prl, I've had tech support send one ota and I've had limited success with a battery pull and sim card removal for about 3 minutes.
[Samsung Galaxy Nexus] Unzitron:
Did you dial *#*#4636#*#* to get to the phone settings and set the prl correctly? It should look like this...
[Samsung Galaxy Nexus] execute_method:
You can't set prl from the testing menu. You may be referring to the network mode (ie. GSM/CDMA auto (prl)).
[Samsung Galaxy Nexus] zombran75:
Awesome ROM! Everything is working fine. Have not seen glitches yet. Just excited to see what u add next. Good work
[Samsung Galaxy Nexus] Unzitron:
I guess I was...

Sent from my Kit Kat Nexus
[Samsung Galaxy Nexus] metalspring:
A few updates on cm

1 good thing and 1 possibly bad thing

good thing- they finally merged the fix for mobile network settings for toro (after I revived the discussion on it lol)

http://review.cyanogenmod.org/#/c/53131/

possibly bad thing- they want to disable ART on all but eng builds (unofficial and official nightlies are userdebug, eng is mostly for developers)

http://review.cyanogenmod.org/#/c/55609/
[Samsung Galaxy Nexus] jrk190:
That is a bad thing... Art is smooth as can be right now.. But as long as mobile is fixed, I'd be fine with that.
[Samsung Galaxy Nexus] palosjr:
Honestly, I don't see what the big deal is with ART. I get that it is a new runtime and people are excited to use it, but I have had zero problems with this ROM (any build) and I am running without ART. This thing flies, it never lags, it looks good and is solid enough to use as a daily driver.
[Samsung Galaxy Nexus] metalspring:
True, but another part of it is cm wanting to remove it since they see it as "dangerous".

It would open up the possibilities of them removing other things they deem "dangerous" such as superuser, long press back to kill app, allowing apps from unknown sources to be installed and who knows what else

And besides, wouldnt you rather have to option to choose than have them decide it for you?

Also more good news- it looks like aosp and linaro are trying to get 4.8 toolchains working with ART :)

https://android-review.googlesource.com/#/q/status:open+project:platform/art,n,z
[Samsung Galaxy Nexus] palosjr:
Valid points. It kind of defeats teh "open" platform that Android and CM are. The last thing we want/need is for CM source to be controlled the way Verizon controls things...
[Samsung Galaxy Nexus] abezzilla99:
Any chance of getting the cool scrolling animation options from the mokee rom? I think it is a gsm only rom but I haven't checked. To see what I'm talking about take a look at the video in this thread around the 1:40 mark.

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