yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 47th_Ronin:
No issues like that here
[Samsung Galaxy Nexus] wastedlife:
Need to hold both volume keys and power button while turning it on to get into fastboot(if you only hold volume down you get Odin). From there, you can use the volume keys to select recovery and hit the power to launch it. If your recovery is hosed, you can use fastboot commands to flash it via your computer. If you still need help, this isn't really the thread for it, should be in q&a. Can also pm me if you want and I'll get back to you when I get a chance.
[Samsung Galaxy Nexus] abezzilla99:
Didn't know it wasn't working with past builds. I used it on 4.2 and decided to try it again now and it worked just fine, maybe even better than when I used it in the past.
[Samsung Galaxy Nexus] kmcrane:
Just got the g2 yesterday.. 9.5 hours of screen on time and I'm at 49% battery life. I never should have waited!
[Samsung Galaxy Nexus] Sheetzie03:
Ooh yes it us. That's the first thing I noticed. So weird it wasn't working prior and not all of a sudden on 1-30 it works, crazy. Was extremely happy about that because xlouder is SO much a must on everyone rom, every dev should add it in to their rom. Ha

Oh yeah, I also enjoy CMetal and how it runs on my phone, I hope it will be updated soon.

Thank u as always Metal

Sent from my Galaxy Nexus

---------- Post added at 05:08 AM ---------- Previous post was at 05:03 AM ----------

You prefer that kernel over mpokang or dirty v?

Surprising

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] heXacode:
Anybody have Bluetooth issues? Paired it up with multiple devices/units (i.e. truck, soundfreaq, gogroove, etc) and they all pair fine but there is no sound on any of them.
[Samsung Galaxy Nexus] DevVorteX:
I've always had similar issues since 4.3

I've worked out a fix, but I've only applied it to shiny's aosp rom so far.

I'll be pulling down omnimetal to test a build with my fix included. If all goes well, I'll share the info with metal and let him decide to include it or not in the official builds.
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4328678]metalspring[/MENTION]

I read a while ago that you were thinking of building something else and was wondering if you had seen this?

http://xdaforums.com/nexus-4/orig-development/mod-multirom-v21c-t2472295

It's for other nexus devices but might be worth a look for gnex variants.

Searching the various threads for it finds nothing useful for porting information specifically for gnex, of course tapatalk search function sucks...

Idk if it's even feasible or not but its a sweet idea nevertheless.
[Samsung Galaxy Nexus] heXacode:
We have something similar but its done with Grakernel (kernel) in Developer section of GNex. The one you're showing looks like a much better version of boot manager and easier to use than Grakernel.

This would definitely be something nice to have for our VZW GNex. I used the Boot Manager app (abandoned) a lot when it used to work.

I vote we get this ported ASAP!
[Samsung Galaxy Nexus] abezzilla99:
I was talking about misledz sound mod. I use mpokang kernel.
[Samsung Galaxy Nexus] Sheetzie03:
I was too lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] abezzilla99:
I haven't tried with anything but my moga pocket controller but I have tried with every cmetal and omnibuild and my phone doesn't even see the controller to pair with. I have no idea what the problem is.
[Samsung Galaxy Nexus] 47th_Ronin:
Yes however, from my rudimentary perusal of the threads it is indicated that one is able to have as many ROMs as one can fit on the sd card and each with its own kernel etc....

Apparently there are two ways to accomplish this, one is chiefly via an app and the other is manually but as I just recently stumbled upon this I'm not certain of the differences in methodologies.

In theory it would be fascinating to be able to actually run a ROM from a different device altogether.

However, if it were feasible on the journeyman (or perhaps more apropos)

advanced user level without need of adb or PC via cable to setup and henceforth run/switch amongst ROMs it would be revolutionary.

Actually, even with needing to adb/shell or otherwise connect to pc it would still be a phenomenal accomplishment.

But again to reiterate;

I am not even vaguely familiar with either the methodology nor the implementation of the aforementioned modification.
[Samsung Galaxy Nexus] heXacode:
[MENTION=2882716]abezzilla99[/MENTION] your issue is a controller device. My issue is streaming music with no audio. I've fixed the issue finally when I narrowed the culprit down to one of my apps using Bluetooth as a remote controller for the Soundfreaq BT unit. It blocked all audio except from the app itself.

I do remember your issue though. Could you refresh my memory and let me know if you've fully wiped before flashing and tested the controller?

Does the controller require an app to route the BT to the moga?

Why not test other BT devices/units to rule out BT being the culprit? That would narrow it down to it being the moga as the issue.

Since you said your device doesn't even see the moga then the moga isn't allowing itself into discovery mode. Have you tested the moga on another android device? If you don't have another I would take it to a VZW store and just test it on one of their display devices to see if it even comes up on the phone.

Lastly, does it come with instructions? Have you read troubleshooting or visited the moga site/forum to see if there are similar problems other users are sharing like you?

I know it's a lot of questions but when things go wrong for me I look at every single angle of the problem (even if it isn't related) to track down the issue and solve it.

Did you watch the video of it in action linked on the OP's first post? You can just use a USB/OTG to do it all without hogging up all your SD space.

Also, not sure if that dev is the main creator of it or a porter but reading the whole thread for info or just ask him all the info we'll need to get it over here.

I should be getting a new laptop in the next month so I will be cracking down to learn this stuff and get my arse going to join this development.
[Samsung Galaxy Nexus] abezzilla99:
It does use the moga app to connect with the controller. I don't have any other bluetooth devices to test with right now but I will try the controller with someone else phone later today. Also I always wipe everything before flashing new roms and mods.
[Samsung Galaxy Nexus] heXacode:
Yeah try pairing with that persons phone and see what happens. If it still doesn't then its an issue with the moga. I'm sifting through Google search results for similar issues you have and see what I can come up with.

Edit: could you link me to the moga app you're using?
[Samsung Galaxy Nexus] abezzilla99:
Cool, thanks man!

Edit: I just tried to pair my gnex with a jawbone jambox and it doesn't find the speaker either.
[Samsung Galaxy Nexus] hexto:
Tried downloading it but it says it's no longer available. Anyone have a mirror? I need my camera. Everything else works perfect
[Samsung Galaxy Nexus] heXacode:
Instructions and interesting comment board about growing problems with connections...

https://m.facebook.com/notes/mogaan...commonly-asked-moga-questions/372536852828428

Also, when you go into Bluetooth settings are you hitting the Search for devices button?

Your jawbone jambox's BT discovery has to be on before hitting Search for Devices on the GNex. I find it rather odd you're not seeing anything show up on the Bluetooth pairing selection.
[Samsung Galaxy Nexus] midnightdevil66:
Decided to join the 4.4 crowd. Flashed this ROM today. Wow! Gotta say it's great so far. Had a blip with camera where it said it couldn't connect but a reboot fixed that. Thanks for your work.
[Samsung Galaxy Nexus] abezzilla99:
Wow I'm embarrassed to say this but I changed the batteries in my moga and that fixed my problem. Before the lights would still come on the controller but wouldn't be seen by my phone. After changing the batteries it works just fine. Thanks for your help though.
[Samsung Galaxy Nexus] heXacode:
About time lol. If you have any other BT issues just post here and we'll help figure it out.
[Samsung Galaxy Nexus] hexto:
Anyone else having issues playing videos? Videos I recorded on my phone are choppy and YouTube videos all say they can't played.
[Samsung Galaxy Nexus] cmoG530:
More than likely the kernel. If it's SuperRam, then that is why. You'll have to switch to the BigMem version of Dirty_V instead, for reliable YouTube playback.
[Samsung Galaxy Nexus] kinfolk248:
Every since JB what's with the ram/kernel issue on the gnex? In ICS we didn't have these issues. Anyone knowledgeable on the subject?
[Samsung Galaxy Nexus] metalspring:
What do you mean?
[Samsung Galaxy Nexus] metalspring:
Btw kernel related issues should be fixed by next build, plus hopefully adding in better network speed indicator options (probably more options than any other version available), omniswitch (somewhat similar to pie but you'll have to try it yourselves), hopefully even better performance, audio theme support, and viper4android app preinstalled (not enabled or set up, you'll have to do that) http://xdaforums.com/showthread.php?t=2191223

Also including the option to use the old version of fast charge with default kernel and adding my custom colors back

New build probably sometime tomorrow since I'm finally going to try doing a build with each of the 3 major optimized toolchains (linaro, sabermod, and codefirex) to see which performs better (currently builds use linaro 4.8)
[Samsung Galaxy Nexus] kinfolk248:
Video playback issues, recording issues. I don't remember such problems back on ICS, what happened to the code or whatever? I've been out of the loop for a while, I used to be on top of things back in my heyday...
[Samsung Galaxy Nexus] metalspring:
It's mostly from kernels that free up some of the extra ram usually reserved for video playback and recording ( which is why the gnex has 1gb of ram but the total amount the user can actually use is far less)

Most kernels that do free up extra ram use the safer ASRAM (additional safe ram, which is about 50MB of ram and doesn't really have any negative effect)

However some use extra patches to free up even more ram ("Superram" kernels) which can effect video playback and breaks 1080p video recording
[Samsung Galaxy Nexus] clnzx2:
Sounds awesome. Any chance of throwing in a blackout option that makes holo backgrounds black?

Also thanks for lock screen notifications it got me back to this wonderful ROM
[Samsung Galaxy Nexus] metalspring:
Check out the open commits in Omni's gerrit, they are working on some type of theming option, I think they are working on exactly what you are talking about lol
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4328678]metalspring[/MENTION]

Just wondering if you'd seen this and any thoughts?
[Samsung Galaxy Nexus] hexto:
Thanks. Flashed Dirty V and it fixed the videos and camera
[Samsung Galaxy Nexus] kinfolk248:
But didn't Google say, "android 4.4 kitkat will improve memory/ram management and reduce system requirements" or some ish like that...? Lol
[Samsung Galaxy Nexus] misterk267:
Anyone else have the quick settings labels disappear and only come back after a reboot?
[Samsung Galaxy Nexus] hexto:
Ha! I couldn't figure out what was different about my tiles. That's it except they're all gone on mine. No labels
[Samsung Galaxy Nexus] clnzx2:
Same here
[Samsung Galaxy Nexus] wastedlife:
Mine has been doing it since at least the 1/22 build.
[Samsung Galaxy Nexus] metalspring:
test builds up to compare linaro vs sabermod vs codefirex toolchains, also a few more features added in

Please let me know which seems to perform best without any extra issues and be warned I havent even tested these builds myself, also its advisable to switch kernels as the included one has logcat disabled (just a config mistake) to be able to provide logs if needed

And lastly, hopefully 3 more builds will go up there soon, testing Link time optimization, graphite optimizations and another build that combines both

:) enjoy testing

OmniMetal-toro-TESTS

Also future test builds will also be in that location
[Samsung Galaxy Nexus] @jmorosky:
[MENTION=4328678]metalspring[/MENTION] I never had to reflash gapps when I was flashing a new version of CMetal. Is this the case with OmniMetal?

Sent from my OmniMetal 20140130 DirtyV4

Sent from my OmniMetal 20140202 DirtyV5
[Samsung Galaxy Nexus] metalspring:
I think the backup function is in the gapps zips themselves so they should work, but I've never tried (I always clean flash to make sure there are no issues with the current build before uploading regular builds)

Also for those asking why certain features aren't included, just know I've cherry picked basically everything that fully (or at least mostly) works from Omni's gerrit, if a feature isn't included then it's most likely because omni hasn't gotten it working or building right yet
[Samsung Galaxy Nexus] clnzx2:
How about poly optimization?
[Samsung Galaxy Nexus] metalspring:
I wish, but that's way too complicated for me lol, it requires switching to building basically everything with clang 3.5 instead of how it's normally built with GCC (this is what linaro/sabermod, etc are) and a few things with the standard clang. It would require tons of extra commits, reconfiguring my build setup and would take far more work then I can really do lol

To compare, link time optimization is just setting 2 compiler flags (cflags), and disabling those cflags for some parts of code that do not work with LTO (bionic, ART, and dalvik), graphite is similar but with 3 extra cflags

Btw, even though LTO doesn't work on ART, dalvik or bionic code, there should still be enough it works on to see some difference
[Samsung Galaxy Nexus] clnzx2:
Didn't realize it was that complicated just figured I would ask since code fire x uses it. Looking forward to your fully optimized build. Thanks for all your hard work
[Samsung Galaxy Nexus] metalspring:
The Codefirex team are experts at optimization, they've done way more with optimization than any rom has ever done (including vanir, liquid and probably even the linaro build team)

Speaking of which, I'm uploading a build make with link time optimization, and one with graphite optimizations- I havent had time to test these yet so be warned, they might have major issues or not even boot (the LTO build is more likely to work since I've done the same thing with cm in the past)

Later will be a the build combining both :)
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4328678]metalspring[/MENTION]

Dude you are smply bad a$$...
[Samsung Galaxy Nexus] gohamstergo:
Unfortunately I dont have time to risk flashing untested builds, but Im looking forward to the next final version!
[Samsung Galaxy Nexus] heXacode:
I was able to test one build before I fell asleep at the TWRP screen lol. Tested CodefireExperiment build and it didn't boot on DirtyV6 kernel. Tried DirtyV5 SR and Linaro versions. Both got to welcome screen then bootlooped.
[Samsung Galaxy Nexus] 47th_Ronin:
I flashed codefirex w/out gapps and it booted fine until i touched the location toggle which made it reboot and hang at omni logo.
[Samsung Galaxy Nexus] metalspring:
apparently the codefirex toolchain has something extra you need to add for it to work properly lol

I removed it from the tests folder since it doesnt work right
[Samsung Galaxy Nexus] hexto:
My MMS isn't working. Says it sent but people get blank texts or it just doesn't send. I'm on 1/30 with Dirty V5 kernel. Anyone else?
[Samsung Galaxy Nexus] RXG9:
I'm on the 1/11/14 build of this ROM with pa minimal gapps and I can't seem to find some SMS apps in the play store, such as chomp SMS and handcent. Is anyone having this problem? How can I fix it? Should I use different gapps?
[Samsung Galaxy Nexus] 47th_Ronin:
Holy crap Batman!!!!!

All I can say is....

OOOOoooooo Graphite....
[Samsung Galaxy Nexus] hexto:
Can anyone say if the builds allow downloading Evolve SMS or Textra SMS from Play Store? Currently both say they are incompatible
[Samsung Galaxy Nexus] Sheetzie03:
Iv had similar issues finding and DL some of the SMS apps as well...wth

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Not sure what's up with the device incompatibility, I have no idea why it's any different on omni vs other roms, it's one of those things I'm looking into
[Samsung Galaxy Nexus] metalspring:
Did you try the graphite build? Does it have any issues?

I just found vanir tried it a long time ago and gave it up because of too many issues, things may have changed or those issues aren't present on the galaxy nexus but on other devices
[Samsung Galaxy Nexus] metalspring:
Oh and btw, what it is this I see? Lol

Note the omni version and kernel version ;)
[Samsung Galaxy Nexus] heXacode:
Check cache partition and see if anything is affecting how the play store sees what apps the phone can download/not downloaded by size.

It is possible that Omni may have not discovered cache partition limitation. This is just a wild guess and possibly why the Play Store filters what gets stored in the cache partition and whatever crosses the threshold will not appear or say it is incompatible.
[Samsung Galaxy Nexus] metalspring:
Speaking of partitions, I finally figured out what was messing with my builds falling to create the final rom zip...

In some update, Ubuntu decided to either just resize or split the /tmp directory to .5 GB, which meant that if anything else wrote to /tmp while I was building then python would run out of space to store the files while making the zip (damn you Ubuntu). Now I just solved it by making /tmp the 1GB it used to be :)
[Samsung Galaxy Nexus] 47th_Ronin:
Running since yesterday and it's freaking smooth as a baby's butt...

No issues running mpokang sr kernel and nexus louder mod.

Around lunch time I'll clean flash LTO build and report back. But I'm dammed impressed with graphite.

Thanks!
[Samsung Galaxy Nexus] metalspring:
Did you try any benchmark tests? If they don't show any real improvement then it's possible that the graphite cflags aren't being applied for some reason
[Samsung Galaxy Nexus] metalspring:
btw, build with both graphite and link time optimization finally done and uploading now

Please note- You MUST flash a kernel with that build, something apparently wasnt right in the config
[Samsung Galaxy Nexus] buhohitr:
So the kernel is not included? flash rom then flash kernel then bootup?
[Samsung Galaxy Nexus] metalspring:
there is a kernel included, but something wasnt right in the config so if you dont flash a different kernel then you get stuck on a black screen between the google boot logo and the boot animation

No worries, I know a little bit about kernels and know how to fix it in the future :)
[Samsung Galaxy Nexus] cujo6801:
Downloading 2/5 test build

Now will let you know..

sent from the DOG pound
[Samsung Galaxy Nexus] jbr05ki:
What kernel do you recommend [MENTION=4328678]metalspring[/MENTION]?
[Samsung Galaxy Nexus] cujo6801:
Wow....

This suckers fast

Using Mpo SR.

Anything else I should try for you...

sent from the DOG pound
[Samsung Galaxy Nexus] buhohitr:
Just aware that some of the kernels are not OC. mopank kernel, by default is OC to 1400, so yeah,,,, it's all done by the kernel. I'm mopank kernel on a bunch of roms like Liquidsmooth etc.. and I already got 13K+(nothing new for me here). I believe if you drop it down to 1200, you should get around 11k+.
[Samsung Galaxy Nexus] midnightdevil66:
I have the same issue.

Via Toro Tapatalk
[Samsung Galaxy Nexus] ABN85:
What's mopank kernel? I've never heard of that one. Got a link?
[Samsung Galaxy Nexus] cmoG530:
Check the Galaxy Nexus forum (aka Maguro)...it's there.
[Samsung Galaxy Nexus] metalspring:
New build up now-

OmniMetal-toro

major changes-

Link time optimization and graphite optimizations

Increasing ringtone volume option

Fast scroll added to manage apps screen

Download speed added in notifications

New, Improved network stats options

Improved data connectivity (thanks to [MENTION=5354353]DevVorteX[/MENTION] and baldwinguy)

Dirtyv kernel updated to v6, with my custom colors and a few presets changed (note- bug with interactive governor, use dyninteractive or ondemandx instead)

Added Viper4Android app preinstalled (you still have to set it up)

New original audio themes setting (see here for available themes)
[Samsung Galaxy Nexus] bluerez79:
Is this very different from the test build yesterday ? That test build is absolutely amazing
[Samsung Galaxy Nexus] metalspring:
It shouldn't be, I just added in new things from omni nightly source and cherry-picked a couple other features, still pretty darn fast ;)
[Samsung Galaxy Nexus] bluerez79:
Omni switch keeps getting killed. Is this normal or is there a way around this?
[Samsung Galaxy Nexus] metalspring:
Which build? The 02/06 one or an older version?
[Samsung Galaxy Nexus] bluerez79:
The test build that I got I think yesterday
[Samsung Galaxy Nexus] metalspring:
It should be fixed now, I updated to the latest changes in omni sources and one thing was a fix for omniswitch getting killed
[Samsung Galaxy Nexus] cujo6801:
Also I was able to turn off Pocket Mod in the new building is well

sent from the DOG pound

---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------

Plus two reboot trying to use this talk to text...

sent from the DOG pound
[Samsung Galaxy Nexus] metalspring:
Not sure what you mean by the first part but I think the second one is from the graphite optimizations :(

I think that's one reason vanir removed them and never messed with them afterwards

Although I can try to get a logcat of what's causing the reboot and disable the graphite optimizations there and see if it helps
[Samsung Galaxy Nexus] 47th_Ronin:
Been on the LTO Graphite build since yesterday and ive not had any issues with reboots or omni switch.

Running latest smityV6 test and slim minimal gapps on clean flash with nexus louder mod and thats about it.

Only thing ive really added is osm0sis and franco dev team vm and io scripts to init.d

Going to flash today's build later and check it out after I nandroid ofc.
[Samsung Galaxy Nexus] furiyk:
Eeks, so is 2/6 stable to flash or should I wait for the next?
[Samsung Galaxy Nexus] metalspring:
For the most part, yes. I ran a similar build all day yesterday (just didn't have the extra features which shouldn't effect stability at all). I just don't use speak to text so I didn't catch that little issue.
[Samsung Galaxy Nexus] qendadar:
I don't use speech to text... But been running 2/6 and mpok sr for most of the morning and no issues so far. Smooth as butter.
[Samsung Galaxy Nexus] cujo6801:
Sorry for not making it clear on the test build I was unable to turn off Pocket Mode it stayed on no matter what I did.

on the new build I can turn it off

sent from the DOG pound
[Samsung Galaxy Nexus] furiyk:
Ok that's great I don't use text to speech so I'll be flashing this soon :)
[Samsung Galaxy Nexus] otter34:
Is the issue with speak to text resolved with this latest build?
[Samsung Galaxy Nexus] bluerez79:
Great. Thanks checking out new bold build this evening
[Samsung Galaxy Nexus] metalspring:
It should be by next build, which will probably be this weekend
[Samsung Galaxy Nexus] RXG9:
Will the SMS app incompatibility problem be addressed in the next build? I'm using 1/11/14 build which has this problem.
[Samsung Galaxy Nexus] abezzilla99:
So speech to text doesn't work on the newest build but other voice stuff works right? like voice search and google now?
[Samsung Galaxy Nexus] EAK128:
Text to speech is working fine on my phone on the latest build in fact I just used it to type this message.

Also it is running fast and smooth and didn't have to change a thing, just minor kernel tweaks.
[Samsung Galaxy Nexus] cujo6801:
It only happened to me twice in the beginning and has not happened since

sent from the DOG pound
[Samsung Galaxy Nexus] misterk267:
IO scripts? That sounds interesting, do you have a link?
[Samsung Galaxy Nexus] jbr05ki:
What's this OmniSwitch y'all speak of and how do I activate it? Been trying to find it and only see pictures of it in action. Thanks!